system-wide installation did not deploy external build extensions correctly

Description:
After #143 and #144 were fixed, I run unit tests:

there were many failed items
failed message is different from the environment prepared by

(system-wide)
python setup.py install

and
(locally)
python setup.py build_ext --inplace

Steps to reproduce this issue:

fetch the latest source code (make sure it is merged the branch for #143 and #144)
build the code system-wide or locally
run unit tests by

python -c 'import solvcon as sc; sc.test()'

Expected result
only unit tests related to EC2 failed
Actual result
failure message of system-wide build[1]
Traceback (most recent call last):
  File "/home/tai271828/work-my-projs/solvcon/test-160302-systemwide/solvcon/dependency.py", line 80, in import_module_may_fail
    mod = importlib.import_module(modname, package)
  File "/home/tai271828/anaconda/lib/python3.5/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 986, in _gcd_import
  File "<frozen importlib._bootstrap>", line 969, in _find_and_load
  File "<frozen importlib._bootstrap>", line 956, in _find_and_load_unlocked
ImportError: No module named 'solvcon.mesh'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/tai271828/work-my-projs/solvcon/test-160302-systemwide/solvcon/dependency.py", line 52, in resolve_name
    name = importlib._resolve_name(name[level:], package, level)
AttributeError: module 'importlib' has no attribute '_resolve_name'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/tai271828/work-my-projs/solvcon/test-160302-systemwide/solvcon/__init__.py", line 91, in <module>
    from .block import Block
  File "/home/tai271828/work-my-projs/solvcon/test-160302-systemwide/solvcon/block.py", line 49, in <module>
    from . import boundcond
  File "/home/tai271828/work-my-projs/solvcon/test-160302-systemwide/solvcon/boundcond.py", line 47, in <module>
    dependency.import_module_may_fail('.mesh')
  File "/home/tai271828/work-my-projs/solvcon/test-160302-systemwide/solvcon/dependency.py", line 87, in import_module_may_fail
    name = resolve_name(modname, package)
  File "/home/tai271828/work-my-projs/solvcon/test-160302-systemwide/solvcon/dependency.py", line 54, in resolve_name
    name = importlib.util.resolve_name(name, package)
AttributeError: module 'importlib' has no attribute 'util'

failure message of local build:
full log
http://paste.ubuntu.com/15265010/
please note there is something like[2]:
OSError: /tmp/tmpaa95o1r5/gmsh.msh not produced by gmsh command line, stdout:
b"gmsh: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by gmsh)\n"

misc:
[1] this looks like python 2 and 3 compatibility issue and is expected to be fixed already?
[2] this might be relevant to OS type. got to figure out the glib used by my host os (Ubuntu trusty)

See https://github.com/solvcon/solvcon/blob/f19670b16fe99103833e680131bfbe67a2db54c7/solvcon/dependency.py#L51 .  In Python 2 there is importlib._resolve_name(), but in Python 3 it's importlib.util.resolve_name().  It's weird to see both failures at the same time.  Perhaps your Python installation is messed up?

thanks for the comment. it is so clear. let me check.

for system-wide build, please note the error message
ImportError: No module named 'solvcon.mesh'

so I noted there is no mesh.cpython-35m-x86_64-linux-gnu.so so the program stopped.
That is,
python setup.py install
did not build the mesh library?

Try python setup.py build_ext --inplace and then install.  This is about distutil, which should be traced into.

setup.py build_ext --inplace and then install (by python setup.py install)
could reproduce the 'GLIBCXX_3.4.20 not found' issue.
besides, on my system
└──╼ strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_DEBUG_MESSAGE_LENGTH

so it is a system-specific issue indeed.
Two solutions are expected:

use a new libstdc++.so - re-compile libstdc++.so with newer source or install newer libstdc++.so binary directly.
use system gmsh instead of the one conda provides (this issue was reported with gmsh provided by conda environment)

by removing the gmsh provided by conda environment and using the gmsh provided by my system, the GLIBCXX issue went away. Here are the gmsh version I used and unit test result:
gmsh version
conda provides: 2.8.4
my Ubuntu Trusty uses: 2.8.3+dfsg-4ubuntu2
unit test result:
python -c 'import solvcon as sc; sc.test()'
.........................................................................................................................................SSS/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:324: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_<IP_ADDRESS>.blk'>
  meta = bio.read_meta()
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:326: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_<IP_ADDRESS>.blk'>
  blkl = bio.load()
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:342: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_<IP_ADDRESS>.blk'>
  meta = bio.read_meta()
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:344: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_<IP_ADDRESS>.blk'>
  blkl = bio.load()
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:361: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.1.blk'>
  meta = bio.read_meta()
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:363: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.1.blk'>
  blkl = bio.load()
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:379: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.1.blk'>
  meta = bio.read_meta()
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:381: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.1.blk'>
  blkl = bio.load()
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:300: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.7_bz2.blk'>
  'oblique_0.0.7_bz2.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:296: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.7_gz.blk'>
  'oblique_0.0.7_gz.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:292: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.7.blk'>
  'oblique_0.0.7.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:312: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.7_bz2.blk'>
  'sample_0.0.7_bz2.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:308: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.7_gz.blk'>
  'sample_0.0.7_gz.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:304: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.7.blk'>
  'sample_0.0.7.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:154: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_<IP_ADDRESS>_bz2.blk'>
  'oblique_<IP_ADDRESS>_bz2.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:150: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_<IP_ADDRESS>_gz.blk'>
  'oblique_<IP_ADDRESS>_gz.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:146: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_<IP_ADDRESS>.blk'>
  'oblique_<IP_ADDRESS>.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:166: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_<IP_ADDRESS>_bz2.blk'>
  'sample_<IP_ADDRESS>_bz2.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:162: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_<IP_ADDRESS>_gz.blk'>
  'sample_<IP_ADDRESS>_gz.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:158: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_<IP_ADDRESS>.blk'>
  'sample_<IP_ADDRESS>.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:223: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.1_bz2.blk'>
  'oblique_0.0.1_bz2.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:219: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.1_gz.blk'>
  'oblique_0.0.1_gz.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:215: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.1.blk'>
  'oblique_0.0.1.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:235: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.1_bz2.blk'>
  'sample_0.0.1_bz2.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:231: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.1_gz.blk'>
  'sample_0.0.1_gz.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:227: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.1.blk'>
  'sample_0.0.1.blk', 'rb'))
................................................................................../home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_neutral.py:58: DeprecationWarning: Please use assertTrue instead.
  self.assert_((blk.fccls[exfcs,1] < 0).all())
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_neutral.py:63: DeprecationWarning: Please use assertTrue instead.
  self.assert_(icl in ecls)
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_neutral.py:65: DeprecationWarning: Please use assertTrue instead.
  self.assert_(icl in ocls)
../home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_neutral.py:24: DeprecationWarning: Please use assertTrue instead.
  '[Neutral (Example): 60 nodes, 116 elements, 1 groups, 2 bcs]')
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_neutral.py:26: DeprecationWarning: Please use assertTrue instead.
  '[Group #1(fluid): 116 elements]')
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_neutral.py:28: DeprecationWarning: Please use assertTrue instead.
  '[BC "element_side.1": 14 entries with 0 values]')
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_neutral.py:30: DeprecationWarning: Please use assertTrue instead.
  '[BC "node.2": 16 entries with 0 values]')
.........
----------------------------------------------------------------------
Ran 254 tests in 5.045s

OK (SKIP=3)

There is a mismatch of test numbers between in-place built SOLVCON and installed SOLVCON.  I didn’t figure out why.  Before we fix it I suggest to run nose in-place (build SOLVCON using python setup.py build_ext --inplace).  The resource warnings should also be fixed.  I’ve cleaned all of them in the in-place version.
The conda Gmsh package was built on Debian stretch:
$ cat /etc/debian_version
8.3
$ strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_3.4.20
GLIBCXX_DEBUG_MESSAGE_LENGTH
I think we should build it on a more solid host to avoid this problem.

On Mar 4, 2016, at 12:39 AM, Taihsiang Ho<EMAIL_ADDRESS>wrote:
by removing the gmsh provided by conda environment and using the gmsh provided by my system, the GLIBCXX issue went away. Here are the gmsh version I used and unit test result:
gmsh version
conda provides: 2.8.4
my Ubuntu Trusty uses: 2.8.3+dfsg-4ubuntu2
unit test result:
python -c 'import solvcon as sc; sc.test()'
.........................................................................................................................................SSS/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:324: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_<IP_ADDRESS>.blk'>
meta = bio.read_meta()
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:326: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_<IP_ADDRESS>.blk'>
blkl = bio.load()
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:342: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_<IP_ADDRESS>.blk'>
meta = bio.read_meta()
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:344: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_<IP_ADDRESS>.blk'>
blkl = bio.load()
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:361: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.1.blk'>
meta = bio.read_meta()
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:363: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.1.blk'>
blkl = bio.load()
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:379: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.1.blk'>
meta = bio.read_meta()
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:381: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.1.blk'>
blkl = bio.load()
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:300: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.7_bz2.blk'>
'oblique_0.0.7_bz2.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:296: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.7_gz.blk'>
'oblique_0.0.7_gz.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:292: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.7.blk'>
'oblique_0.0.7.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:312: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.7_bz2.blk'>
'sample_0.0.7_bz2.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:308: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.7_gz.blk'>
'sample_0.0.7_gz.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:304: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.7.blk'>
'sample_0.0.7.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:154: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_<IP_ADDRESS>_bz2.blk'>
'oblique_<IP_ADDRESS>_bz2.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:150: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_<IP_ADDRESS>_gz.blk'>
'oblique_<IP_ADDRESS>_gz.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:146: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_<IP_ADDRESS>.blk'>
'oblique_<IP_ADDRESS>.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:166: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_<IP_ADDRESS>_bz2.blk'>
'sample_<IP_ADDRESS>_bz2.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:162: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_<IP_ADDRESS>_gz.blk'>
'sample_<IP_ADDRESS>_gz.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:158: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_<IP_ADDRESS>.blk'>
'sample_<IP_ADDRESS>.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:223: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.1_bz2.blk'>
'oblique_0.0.1_bz2.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:219: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.1_gz.blk'>
'oblique_0.0.1_gz.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:215: ResourceWarning: unclosed file <_io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/oblique_0.0.1.blk'>
'oblique_0.0.1.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:235: ResourceWarning: unclosed file <io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.1_bz2.blk'>
'sample_0.0.1_bz2.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:231: ResourceWarning: unclosed file <io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.1_gz.blk'>
'sample_0.0.1_gz.blk', 'rb'))
./home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_block.py:227: ResourceWarning: unclosed file <io.BufferedReader name='/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/test/data/sample_0.0.1.blk'>
'sample_0.0.1.blk', 'rb'))
................................................................................../home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_neutral.py:58: DeprecationWarning: Please use assertTrue instead.
self.assert((blk.fccls[exfcs,1] < 0).all())
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_neutral.py:63: DeprecationWarning: Please use assertTrue instead.
self.assert(icl in ecls)
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_neutral.py:65: DeprecationWarning: Please use assertTrue instead.
self.assert(icl in ocls)
../home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_neutral.py:24: DeprecationWarning: Please use assertTrue instead.
'[Neutral (Example): 60 nodes, 116 elements, 1 groups, 2 bcs]')
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_neutral.py:26: DeprecationWarning: Please use assertTrue instead.
'[Group #1(fluid): 116 elements]')
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_neutral.py:28: DeprecationWarning: Please use assertTrue instead.
'[BC "element_side.1": 14 entries with 0 values]')
/home/tai271828/work-my-projects/solvcon/solvcon.160303.build.test/solvcon/io/tests/test_neutral.py:30: DeprecationWarning: Please use assertTrue instead.
'[BC "node.2": 16 entries with 0 values]')
.........
Ran 254 tests in 5.045s
OK (SKIP=3)
—
Reply to this email directly or view it on GitHub https://github.com/solvcon/solvcon/issues/145#issuecomment-191844410.

--
Yung-Yu Chen
http://yyc.solvcon.net/
+886 (99) 129 4763

There is a mismatch of test numbers between in-place built SOLVCON and installed SOLVCON.  I didn’t figure out why.  Before we fix it I suggest to run nose in-place (build SOLVCON using python setup.py build_ext --inplace).  The resource warnings should also be fixed.  I’ve cleaned all of them in the in-place version.
The conda Gmsh package was built on Debian stretch:
$ cat /etc/debian_version
8.3
$ strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_3.4.20
GLIBCXX_DEBUG_MESSAGE_LENGTH

I think we should build it on a more solid host to avoid this problem.

For test number issue, I filed #146 to trace the issue. Please update relevant study on #146.

This issue has not been touched for a while and things may change. I try to reproduce this issue with the latest SOLVCON and the inconsistency between system-wide and local installation is still there.
The nosetests --with-doctest result of system-wide installation
Ran 242 tests in 2.435s

FAILED (SKIP=3, errors=100, failures=32)

And The nosetests --with-doctest result of local installation
.................................................................................................................................................................................................................................................................................................................................................................SSS
----------------------------------------------------------------------
Ran 356 tests in 3.903s

OK (SKIP=3)

The missing extension module in installation is fixed with https://github.com/solvcon/solvcon/commit/ed8c95bcdf31c986c0b1239f6db21784d40ced16 .  The difference in number of tests is intentional, as explained in issue #146 .
The code is in master branch.  I am closing this issue.  If there's any problem please reopen.


Determine what the dashboard will look like

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/306
Originally created by @bencodezen on 2019-01-18 17:15:29

We need to decide the basic look and feel for the dashboard

View 4 previous comments from the original issue on GitLab


added FAQs again

Recloned and added FAQs again.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65a51a5c85c506352036d902--harness-developer.netlify.app


SA1412 code fix does not preserve DependentUpon solution items

Items marked as DependentUpon are removed when the original file is removed.
Found this when fixing an EntityFramework migration.

I basically had to revert changes to each .csproj after applying this code fix. Several other bugs are filed for it as well.

Blocked on dotnet/roslyn#4767.


learning schedule

Hi,
Can you kindly offer the solver_ofnet_bsdsownership.prototxt? With my pytorch-implementation, I reproduced your AP scores but always get 3% drop on ODS and OIS which is quite annoying. Thank you very much!

Hi,
Here is the solver.
`net: "train_val_ofnet_bsdsownership.prototxt"
test_iter: 0
test_interval: 1000000
lr for fine-tuning should be lower than when starting from scratch
debug_info: true
base_lr: 0.00003
lr_policy: "step"
gamma: 0.1
iterate for a larger batch
clip_gradients:100000
iter_size: 1
stepsize should also be lower, as we're closer to being done
stepsize: 4000
display: 20
max_iter: 10000
momentum: 0.9
weight_decay: 0.0002
snapshot: 2000
snapshot_prefix: "../snapshots/ofnet_bsdsownership"
uncomment the following to default to CPU mode solving
solver_mode: CPU
`
Best

Hi,
Here is the solver_ofnet_bsdsownership.prototxt.
net: "train_val_ofnet_bsdsownership.prototxt"
test_iter: 0
test_interval: 1000000
# lr for fine-tuning should be lower than when starting from scratch
# debug_info: true
base_lr: 0.00003
lr_policy: "step"
gamma: 0.1
# iterate for a larger batch
# clip_gradients:100000
iter_size: 1
# stepsize should also be lower, as we're closer to being done
stepsize: 4000
display: 20
max_iter: 10000
momentum: 0.9
weight_decay: 0.0002
snapshot: 2000
snapshot_prefix: "../snapshots/ofnet_bsdsownership"
# uncomment the following to default to CPU mode solving
# solver_mode: CPU

Best


INJECTING ON LINUX

I have followed this guide: Linux Installation guide
But it doesnt explain how to inject the cheat at all. the last command is: make -j $(nproc --all)
and that only builds the cheat for me. Any information would help thank you

Just attach with gdb

switch to windows, profit

Nvm I did it

Thanks for the support

Would be nice if you explained how you injected it, instead of leaving it off at "Nvm I did it"


Implement Recipe Edit (without versioning)

Implement a basic recipe edit interface - either live edit or save-at-once

https://github.com/switzerb/CookBook/pull/57


Can't locate API module structure `security2_module' symbol is undefined

Hai,
been trying to setup modsecurity in AWS AMI
following Compilation Recipe for AWS the only different is i specify a prefix and sysconfdir
[root@ip- work]# ./configure --sysconfdir=/etc --prefix=/usr
its the only different from the setup
my current os-system
[root@ip- work]# cat /etc/issue
Amazon Linux AMI release 2017.03
Kernel \r on an \m

httpd version
[root@ip- work]# httpd -v
Server version: Apache/2.4.25 (Amazon)
Server built:   Jan 19 2017 16:55:49

after finish compiling
[root@ip- work]# ls /usr/lib/ | grep -i modsec
libmodsecurity.a
libmodsecurity.la
libmodsecurity.so
libmodsecurity.so.3
libmodsecurity.so.3.0.0

my configuration is just simple, after make and make install i then link the following file above which is libmodsecurity.so.3.0.0 to /etc/httpd/modules/ as mod_security2.so
[root@ip- lib]# ln -s $PWD/libmodsecurity.so.3.0.0 /etc/httpd/modules/mod_security2.so
[root@ip- lib]# ls -l /etc/httpd/modules/ | grep -i sec
lrwxrwxrwx 1 root root     32 Jul 25 11:32 mod_security2.so -> /usr/lib/libmodsecurity.so.3.0.0

create httpd module configuration for modsecurity
[root@ip- conf.modules.d]# cat 00-modsecurity.conf
LoadModule security2_module modules/mod_security2.so

now when i try to start the httpd it failed like this
[root@ip- conf.modules.d]# /etc/init.d/httpd start
Starting httpd: httpd: Syntax error on line 56 of /etc/httpd/conf/httpd.conf: Syntax error on line 1 of /etc/httpd/conf.modules.d/00-modsecurity.conf: Can't locate API module structure `security2_module' in file /etc/httpd/modules/mod_security2.so: /etc/httpd/modules/mod_security2.so: undefined symbol: security2_module
                                                           [FAILED]

now see security2_module symbol is undefined and it said can't locate API module structure.
i've been using modsecurity before on debian jessie with Apache/2.4.10 with the same LoadModule configuration with no issue like this.
are the name of the module is now different in branch v3/master ?
the power of google now useless i've been searching for two hour now
a kind help/advice would be really helpful, thanks.

i ended up switch back to branch v2/master
[root@ip- modsec]# git branch
* v2/master

with same module config
[root@ip- conf.modules.d]# cat 00-modsecurity.conf
LoadModule security2_module modules/mod_security2.so

starting and listing httpd module
[root@ip- modsec]# /etc/init.d/httpd start
Starting httpd:                                            [  OK  ]
[root@ip- modsec]# httpd -M | grep -i sec
 security2_module (shared)

just before i finally given up and switching to branch v2, i set the configuration to
LoadModule security3_module modules/mod_security3.so i assume because i did compile v3/master branch but its still failed and won't load the module.

Hi @johnmckinght,
Version 3 demands two different components: The library and the connector. You have installed the library. The connector is available here:

https://github.com/SpiderLabs/ModSecurity-apache


install-plugins.sh: Some plugins failed to download! Not downloaded: credentials

I'm getting always the same error when I try to build a Dockerfile with some predefined plugins.
For example, you can try the Dockerfile example from the documentation:
FROM jenkins
RUN /usr/local/bin/install-plugins.sh docker-slaves github-branch-source:1.8

If I check the log, I see the following error:
Failed to download plugin: credentials or credentials-plugin
I get the same error if I try do install cloudbees-folder plugin.
It seems some kind of problem to download crendentials plugin (and cloudbees-folder). But if I go to the plugin url https://updates.jenkins.io/download/plugins/credentials/ I don't see any issue...

if all fail to download you probably have a dns issue

It not seems a dns issue. Only credentials download fails (well, and also cloudbees-folder plugin). I've tried from a different network and I got the same problem :-S.
The Dockerfile (from the documentation with predefined plugins) is working for you?
Here you are a full log:
Step 2/2 : RUN /usr/local/bin/install-plugins.sh docker-slaves github-branch-source:1.8
 ---> Running in dd7bc8970498
Creating initial locks...
Analyzing war...
Downloading plugins...
Downloading plugin: docker-slaves from https://updates.jenkins.io/download/plugins/docker-slaves/latest/docker-slaves.hpi
Downloading plugin: github-branch-source from https://updates.jenkins.io/download/plugins/github-branch-source/1.8/github-branch-source.hpi
 > github-branch-source depends on github-api:1.75,github:1.14.0,credentials:1.22,scm-api:1.2,git:2.3
Downloading plugin: github-api from https://updates.jenkins.io/download/plugins/github-api/latest/github-api.hpi
Downloading plugin: github from https://updates.jenkins.io/download/plugins/github/latest/github.hpi
Downloading plugin: credentials from https://updates.jenkins.io/download/plugins/credentials/latest/credentials.hpi
Downloading plugin: scm-api from https://updates.jenkins.io/download/plugins/scm-api/latest/scm-api.hpi
Downloading plugin: git from https://updates.jenkins.io/download/plugins/git/latest/git.hpi
 > docker-slaves depends on workflow-support:2.2;resolution:=optional,docker-commons:1.3.1,durable-task:1.12;resolution:=optional,workflow-step-ap
i:2.3;resolution:=optional
Skipping optional dependency workflow-support
Skipping optional dependency durable-task
Downloading plugin: docker-commons from https://updates.jenkins.io/download/plugins/docker-commons/latest/docker-commons.hpi
Skipping optional dependency workflow-step-api
Downloading plugin: credentials-plugin from https://updates.jenkins.io/download/plugins/credentials-plugin/latest/credentials-plugin.hpi
 > docker-commons depends on credentials:1.22,icon-shim:1.0.3,authentication-tokens:1.1
Downloading plugin: icon-shim from https://updates.jenkins.io/download/plugins/icon-shim/latest/icon-shim.hpi
Downloading plugin: authentication-tokens from https://updates.jenkins.io/download/plugins/authentication-tokens/latest/authentication-tokens.hpi
 > github depends on credentials:2.1.8,git:2.4.0,github-api:1.80,plain-credentials:1.1,scm-api:2.0.3,token-macro:1.11
Downloading plugin: plain-credentials from https://updates.jenkins.io/download/plugins/plain-credentials/latest/plain-credentials.hpi
Downloading plugin: token-macro from https://updates.jenkins.io/download/plugins/token-macro/latest/token-macro.hpi
Failed to download plugin: credentials or credentials-plugin
 > git depends on workflow-scm-step:1.14.2,credentials:2.1.8,git-client:2.1.0,mailer:1.18,matrix-project:1.7.1,promoted-builds:2.27;res[1506/1990]
tional,scm-api:2.0.3,ssh-credentials:1.12,token-macro:1.12.1;resolution:=optional,parameterized-trigger:2.4;resolution:=optional
Downloading plugin: workflow-scm-step from https://updates.jenkins.io/download/plugins/workflow-scm-step/latest/workflow-scm-step.hpi
Downloading plugin: git-client from https://updates.jenkins.io/download/plugins/git-client/latest/git-client.hpi
Downloading plugin: mailer from https://updates.jenkins.io/download/plugins/mailer/latest/mailer.hpi
Skipping optional dependency promoted-builds
Downloading plugin: matrix-project from https://updates.jenkins.io/download/plugins/matrix-project/latest/matrix-project.hpi
Skipping optional dependency token-macro
Downloading plugin: ssh-credentials from https://updates.jenkins.io/download/plugins/ssh-credentials/latest/ssh-credentials.hpi
Skipping optional dependency parameterized-trigger
 > authentication-tokens depends on credentials:1.22
 > plain-credentials depends on credentials:2.1.5
 > workflow-scm-step depends on workflow-step-api:1.15
Downloading plugin: workflow-step-api from https://updates.jenkins.io/download/plugins/workflow-step-api/latest/workflow-step-api.hpi
 > ssh-credentials depends on credentials:2.1.0
 > mailer depends on display-url-api:1.0
Downloading plugin: display-url-api from https://updates.jenkins.io/download/plugins/display-url-api/latest/display-url-api.hpi
 > matrix-project depends on junit:1.2,script-security:1.13
Downloading plugin: junit from https://updates.jenkins.io/download/plugins/junit/latest/junit.hpi
Downloading plugin: script-security from https://updates.jenkins.io/download/plugins/script-security/latest/script-security.hpi
 > git-client depends on ssh-credentials:1.12,structs:1.5
Downloading plugin: structs from https://updates.jenkins.io/download/plugins/structs/latest/structs.hpi
 > workflow-step-api depends on structs:1.5
 > display-url-api depends on junit:1.19
 > junit depends on structs:1.2

WAR bundled plugins:

Installed plugins:
authentication-tokens:1.3
display-url-api:1.1.1                                                                                [1475/1990]
docker-commons:1.6
docker-slaves:1.0.6
git-client:2.2.1
git:3.0.5
github-api:1.84
github-branch-source:1.8
github:1.26.0
icon-shim:2.0.3
junit:1.20
mailer:1.19
matrix-project:1.8
plain-credentials:1.4
scm-api:2.0.7
script-security:1.26
ssh-credentials:1.13
structs:1.6
token-macro:2.0
workflow-scm-step:2.3
workflow-step-api:2.9
Some plugins failed to download! Not downloaded: credentials
The command '/bin/sh -c /usr/local/bin/install-plugins.sh docker-slaves github-branch-source:1.8' returned a non-zero code: 1

Sorry, now it works. It suppose it was some network issue... (although I tried it from different network and dns server 0_o)

@jllado - you're not crazy, this happens to me every few times I build a container. I just think Jenkins has some really poor mirrors that are often not in sync. I'll get 404s and other errors when doing the build on various plugins frequently :(

@jllado - you're not crazy, this happens to me every few times I build a container. I just think Jenkins has some really poor mirrors that are often not in sync. I'll get 404s and other errors when doing the build on various plugins frequently :(

This still seems the case in 2019.

I was getting this error and found I'd accidentally capitalized the plugin name in the dockerfile. Couldn't download "Cppcheck.hpi" because it was "cppcheck.hpi".

Same thing happening here in 2020! I am running this Docker build from a docker-compose command from Ansible inside a docker container (for testing). I've never had this problem when just building the Docker image without the in-between pieces, though.

Same thing happend to me right now. If it was run-condition.hpi or something like that, it is working now.

Same thing happening here in 2020! I am running this Docker build from a docker-compose command from Ansible inside a docker container (for testing). I've never had this problem when just building the Docker image without the in-between pieces, though.

Update: I determined that one of the plugins had a typo in the version. After fixing that - no issues.

I had problem that requested version file did not exist in that path. But then, I literally seen it become online between refreshes. Probably mirroring takes more time than expected.

https://issues.jenkins.io/browse/INFRA-2322


Copy to clipboard functionality lost

With the old version of the site, you could click the boxes and it would copy that value to clipboard - kind of the point of a utility site like this.  Could this be re-instated?

Hey, @wesbos, thank you for bringing this to our attention, it must have slipped through during the development. We will place this on our backlog!

awesome thank you!

PR'd this

I really miss this functionality. I keep pressing Ctrl C out of habit, only to realise that that obviously doesn't work.


Add support to read and write more values via library and command line

This patch adds support to read and write the RTC. Documentation has been taken from:
https://www.img4.cz/i4wifi/attach/StoItem/7124/MODBUS-Protocol-v25.pdf
This change has been tested on my EPEVER Tracer2210AN.
This will also close #20 .

I have updated this PR to contain support for two more values I've needed to set on my MPPT today.
With this change we can now also write battery capacity and battery temperature compensation coefficient via library and command line.
This will also close #19 .
@rosswarren Let me know if you like the way this is done. I am open for suggestions on other ways to implement this.

Thank you for the contribution, and for testing on your device! I will merge this now.


fix: typo in header

Good day!
We are really enjoying your work with bindings for Clipper2. Here are some typos we found during development.
You are also welcome to see our fork and fetch some ideas if you need :)
Good luck!

Woops, thanks for this! Glad that you are finding it useful. :+1:


Implementation of ext_blake2_256_enumerated_trie_root

Description of the Change
Implementation of the aforementioned extension method and required by it refactor of the Trie, which is mostly just splitting PolkadotTrieDb on PolkadotTrie, which contains the data structure logic, and PolkadotTrieDb, which is in charge of persistency.
NOTE: There are a lot of lines in git diff but only because if this separation, actually there's not much new code.

Benefits
We will have ext_blake2_256_enumerated_trie_root.

Possible Drawbacks
None.

Usage Examples or Tests
Provided in the code.

Alternate Designs
There are in Polkadot JS and Substrate, but comparison of the produced hash was complicated by differences in implementations and is not done currently.

Codecov Report

Merging #144 into master will increase coverage by 0.5%.
The diff coverage is 70.42%.

@@            Coverage Diff            @@
##           master     #144     +/-   ##
=========================================
+ Coverage   72.59%   73.09%   +0.5%
=========================================
  Files         281      287      +6
  Lines        7492     7531     +39
  Branches     3797     3842     +45
=========================================
+ Hits         5439     5505     +66
+ Misses       1061     1026     -35
- Partials      992     1000      +8

Impacted Files
Coverage Δ

test/testutil/storage/polkadot_trie_db_printer.hpp
0% <ø> (ø)
:arrow_up:

...storage/trie/polkadot_trie_db/polkadot_trie_db.hpp
100% <ø> (ø)
:arrow_up:

...rage/trie/polkadot_trie_db/polkadot_trie_batch.hpp
100% <ø> (ø)
:arrow_up:

...e/storage/trie/polkadot_trie_db/polkadot_codec.cpp
77.19% <100%> (ø)
:arrow_up:

test/core/extensions/storage_extension_test.cpp
95.68% <100%> (+0.79%)
:arrow_up:

test/testutil/storage/in_memory_storage.hpp
100% <100%> (ø)

...re/storage/trie/polkadot_trie_db/polkadot_trie.hpp
100% <100%> (ø)

test/testutil/storage/in_memory_batch.hpp
18.75% <18.75%> (ø)

test/testutil/storage/in_memory_storage.cpp
42.1% <42.1%> (ø)

...rage/trie/polkadot_trie_db/polkadot_trie_batch.cpp
83.33% <53.84%> (-2.39%)
:arrow_down:

... and 16 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 73a1c2c...6376bc8. Read the comment docs.


Using menu to choose what the MC replies

I'm rather new to github, and i think this is probably an issue with my understanding of the framework rather then the framework itself  but i hope that i'm not misusing the issues section here.
label jumptomessages:
    #$ open_gc_directly(mc_abigail_gc)
    show screen phone_contacts
    phone discussion mc_abigail_gc:
        menu:
            "Yeah.":
                $ abigailrep =- 1
                $ ghostedabigaildm = True
                "mc" "Yeah"

            "Yeah i got home just fine, hbu?":
                "mc" "Yeah i got home just fine, hbu?"
                "abigail" "So did i!
    "..."
    phone end discussion

The label is jumped to when a phone logo is clicked, it opens directly to the messages (the mc_abigail_gc despite it being commented out) but it send's both of the menu options with no menu prompt beforehand. I'm sorry if this is a bother!

you don't need the show screen phone_contacts. it's done automatically by the phone discussion statement.
and yes this is normal behavior. the menu is inside the phone (you can click on Yeah. and Yeah i got home blah blah). it's not the same as the regular menu statement

you don't need the show screen phone_contacts. it's done automatically by the phone discussion statement.
and yes this is normal behavior. the menu is inside the phone (you can click on Yeah. and Yeah i got home blah blah). it's not the same as the regular menu statement

However when i do click the imagebutton, despite removing the show screen, it just automatically advances, and send's both menu options without displaying a choice to the player.
https://github.com/Elckarow/Better-EMR-Phone/assets/153170004/23dc1b1c-f911-4c07-b93f-376dd8764e17
i've attached a screen recording to demonstrate

yes. you can click on them.

yes. you can click on them.

Oh indeed! I didn't realize because of their color but yep, my bad. Merci pour ton temps!

pas de soucis


hi, i re-implement conformer based on your project, when i train conformer with ctc loss on chinese dataset, loss is fluctuating

hi， thanks to your peoject, i re-implement conformer for tf.1.15. When i train it with ctc loss on 1000-h chinese audio dataset, the loss is fluctuating and could not decline.
the conv-sampling is 3-layer conv2d with 144 filters and kernel_size=3, reduction_factor=4
the conformer is just like the bert-base but with relative position encoding using t-5
the optimizer is adam-with-weight-decay, params are default as bert-base
.
could you help me with this?

you can use adam to try it again.


Cleanup unused images

Description
Cleanup unused images
Type of change

Documentation update

Testing steps
N/A
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
Patch has no changes to coverable lines.
:loudspeaker: Thoughts on this report? Let us know!.


Make bundle of examples

Just needs a bit of tweaking I think.

@Integral could you take this next?

Yes, i could. No problems.

Thanks. We need that for the release. To have all examples at substance.io/examples

We could close this issue. Last question, do we need to expose this example? https://github.com/substance/examples/tree/devel/isolated-nodes

Nope. I was just having this to extract the smaller examples.
Let's drop it tomorrow.

I think this issue can be closed, as it is working.
We need to adapt it to latest changes but that's ok.


show "version `GLIBC_2.29' not found" after Release v1.0.0-alpha.29

I am using Debian GNU/Linux 10 (buster). When I install helium-gateway-v1.0.0-alpha.27-raspi_64.deb and helium-gateway-v1.0.0-alpha.28-raspi_64.deb. It works well. But after helium-gateway-v1.0.0-alpha.29-raspi_64.deb, it shows
helium_gateway: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by helium_gateway)

Even if I rollback to v1.0.0-alpha.27, it will update to 1.0.0~alpha.31 automatically and show the same error message.
I don't know why you upgrade the dependency clib version, that is a big change and not a good choice for an embedded system.

It's part of a build system upgrade, not intentional. There's no good way to roll that back afaict, but if you know a way I'd love to know

It's part of a build system upgrade, not intentional. There's no good way to roll that back afaict, but if you know a way I'd love to know

In general, Helium should maintain a fixed libc version if there are no specific reason. The original design idea is that device to update automatically, but automatic update should not force the device to upgrade the whole system. This is unreasonable for embedded systems.
The best solution is to roll back the old build environment, or use static-linking to generate the executable. Otherwise, any device will not be able to run helium_gateway after updated via Helium server.

It's part of a build system upgrade, not intentional. There's no good way to roll that back afaict, but if you know a way I'd love to know

In general, Helium should maintain a fixed libc version if there are no specific reason. Once libc is upgraded, it usually means a system-wide upgrade. I can imagine that Helium release .deb for different platforms so that those platforms can be updated automatically. But automatic update should not force the device to upgrade the whole system. This is unreasonable for embedded systems.
The best solution is to roll back the old build environment, or use static-linking to generate the executable. Otherwise, any device will not be able to run helium_gateway after updated via Helium server.
If Helium still wants to keep the new build system and use the same build process, then I think all platform maintainers will be forced to stop using automatic upgrades and build binaries from source. They also need to design their own upgrade procedure.

I understand all the arguments.. If we don't want to hold back toolchain upgrades which really help with performance and stability, what are our options? I'm looking for help, not reasons to go to the past

It's part of a build system upgrade, not intentional. There's no good way to roll that back afaict, but if you know a way I'd love to know

In general, Helium should maintain a fixed libc version if there are no specific reason. Once libc is upgraded, it usually means a system-wide upgrade. I can imagine that Helium release .deb for different platforms so that those platforms can be updated automatically. But automatic update should not force the device to upgrade the whole system. This is unreasonable for embedded systems.
The best solution is to roll back the old build environment, or use static-linking to generate the executable. Otherwise, any device will not be able to run helium_gateway after updated via Helium server.
If Helium still wants to keep the new build system and use the same build process, then I think all platform maintainers will be forced to stop using automatic upgrades and build binaries from source. They also need to design their own upgrade procedure.

I understand all the arguments.. If we don't want to hold back toolchain upgrades which really help with performance and stability, what are our options? I'm looking for help, not reasons to go to the past

I already said that using static linking is an option at the moment. Maybe you can provide a binary for both ways of linking. Or let the platform provider handle the upgrade by themself.

It's part of a build system upgrade, not intentional. There's no good way to roll that back afaict, but if you know a way I'd love to know

In general, Helium should maintain a fixed libc version if there are no specific reason. Once libc is upgraded, it usually means a system-wide upgrade. I can imagine that Helium release .deb for different platforms so that those platforms can be updated automatically. But automatic update should not force the device to upgrade the whole system. This is unreasonable for embedded systems.
The best solution is to roll back the old build environment, or use static-linking to generate the executable. Otherwise, any device will not be able to run helium_gateway after updated via Helium server.
If Helium still wants to keep the new build system and use the same build process, then I think all platform maintainers will be forced to stop using automatic upgrades and build binaries from source. They also need to design their own upgrade procedure.

I understand all the arguments.. If we don't want to hold back toolchain upgrades which really help with performance and stability, what are our options? I'm looking for help, not reasons to go to the past

I already said that using static linking is an option at the moment. Maybe you can provide a binary for both ways of linking. Or let the platform provider handle the upgrade by themself.

who is the platform provider in your case?

I believe all debian 10 buster based OS would have the same problem.
Debian 11 bullseye upgrade the glibc for all arches (in this case it is aarch64),
so dynamic compiled binary on Debian 11 will not run on Debian 10.

It's part of a build system upgrade, not intentional. There's no good way to roll that back afaict, but if you know a way I'd love to know

In general, Helium should maintain a fixed libc version if there are no specific reason. Once libc is upgraded, it usually means a system-wide upgrade. I can imagine that Helium release .deb for different platforms so that those platforms can be updated automatically. But automatic update should not force the device to upgrade the whole system. This is unreasonable for embedded systems.
The best solution is to roll back the old build environment, or use static-linking to generate the executable. Otherwise, any device will not be able to run helium_gateway after updated via Helium server.
If Helium still wants to keep the new build system and use the same build process, then I think all platform maintainers will be forced to stop using automatic upgrades and build binaries from source. They also need to design their own upgrade procedure.

I understand all the arguments.. If we don't want to hold back toolchain upgrades which really help with performance and stability, what are our options? I'm looking for help, not reasons to go to the past

I already said that using static linking is an option at the moment. Maybe you can provide a binary for both ways of linking. Or let the platform provider handle the upgrade by themself.

who is the platform provider in your case?

A platform provider is a manufacturer or maker that uses the same hardware as raspi_64, caldigit, tektelic, freedomfi, etc. in the README.me table.

I believe all debian 10 buster based OS would have the same problem. Debian 11 bullseye upgrade the glibc for all arches (in this case it is aarch64), so dynamic compiled binary on Debian 11 will not run on Debian 10.

When we developing fullhostpot, we have been using Debian 10 buster, and we use the same SDK for lighthotspot. Everything worked fine until gateway-v1.0.0-alpha.29.
Updating glibc is a big change for any embedded system. Maybe we've passed some hardware audit before, and some software has been in use for a while. Updating glibc means that there is a lot of software that needs to be recompiled and tested.

I understand.. want to provide a PR that makes the raspi Debian builds a musl target instead of a dynamic target? The binary size will get bigger but I think it may remove the glibc dependencies

@andrewintw With the simplification on the main branch of no packaged releases for this repo, and target triplet based builds, I hope it's clearer that a maker could pick up a binary build from here but the build is really just there to ensure it works on a given target triplet without trying to be the definitive binary release for any given complete platform. A maker should probably build their own binary and roll it into their own upgrade packaging (which is going to be needed anyway).
Foundation approval for a given piece of hardware is based on gateway-mfr-rs which does require the public repo to produce a binary for validation that can run on the target hardware. This may mean that repository will need fixes to make sure the built and released gateway_mfr binary works on your target
Does that make sense?

With #363 the -gnu builds are all musl builds now so hopefully that helps with static builds


Create view for Garage creation and update

@mesyamaureen Maybe you would like to take over this issue?

yes, I'd like to take over this issue

For your information, part of this issue is being discussed in

#285

This issue is implemented on this branch in the forked repo.
Update (01.12.2024):

[x] implemented temporary view for the garage before final decision on reusable component for the modal is decided.
[x] implemented new api connections on the service
[x] implemented component class for the garage view
[ ] test if all apis transfer the right data from backend
[ ] implement unit test cases
[ ] do e2e tests


Able to find the window element but unable to click on it

In the app there are five buttons , each with same attributes but different Name.
Four of them works perfectly fine .
one button is recognised by the winappdriver(tried to get the values by providing the attributes, it gives 100% correct result) but when trying to click the button it can't do that.
Tried to get the element by setting co-ordinates, from parent, providing sleep() , etc. None of them helped.
Help is required.
Close_Button_attributes.txt

ritusenleo Please provice code example, stacktrace and WinAppDriver log


Add Support for different stack protector options

Currently, the Zephyr project only supports the -fstack-protector-all option for stack protection. To better tune memory footprint and security requirements, it is necessary to add support for other stack protector options such as,

-fstack-protector,
-fstack-protector-strong, and
-fstack-protector-explicit.

Rationale:

Memory Footprint: Different stack protector options provide varying levels of protection, which can help optimize the memory usage for different applications. For instance, -fstack-protector-all adds stack protection to all functions regardless of their vulnerability, that increases memory footprint significantly, while -fstack-protector/ -fstack-protector-strong provides a more balanced approach by protecting functions with certain characteristics.
Security Requirements: Allowing more granular control over stack protection can help meet diverse security needs. For example, -fstack-protector-explicit allows developers to manually specify which functions should be protected, offering a tailored security approach.

Proposed Changes:

Build System Modifications:

Update the CMake build scripts to accept new stack protector options.
Introduce configuration options in Kconfig to select the desired stack protector level.
Ensure compatibility with different compiler versions and platforms supported by Zephyr.

Codebase Adjustments:

Modify the compiler flags in the build system to include the selected stack protector option.
Implement conditional compilation to apply the appropriate stack protector based on the configuration.

Documentation Updates:

Update the Zephyr documentation to include detailed descriptions of each stack protector option.
Provide guidelines on how to select the appropriate stack protector based on application requirements.
Include examples demonstrating the impact of different stack protector options on memory usage and security.

Testing and Validation:

Develop unit tests to verify the correct application of each stack protector option.
Perform regression testing to ensure that the new options do not introduce any issues.
Conduct performance benchmarking to evaluate the impact of different stack protector options on memory footprint and execution time.

@vujjuri It makes sense to me.


Centralize learn screenshots

To avoid duplicating screenshots for each translated language, the screenshots inside the en folder must be moved to a shared media folder outside the language specific content.

Target mapping: docs/media/loc/en
1 level sub-folders reflecting top-level folders in en/
Preserve current filename but update paths.

This allows us to introduce localized screenshots in other languages in the future.
Discarded alternatives

Copy images to the language specific content folders but map to the same destination as en media with docfx.json
Use relative paths pointing from no/ to en/**media/. Involves updating 264 paths in each translated language. However, this has the risk of being overwritten in future translations and will most likely have to be repeated.

Shouldn't docs/media/en and docs/media/no be enough nesting?


Add selected cards to groups

If a user selects a valid combination of cards and then taps on a group, those cards should be added to the specified group

Resolved by 4247f0e


prevent accidental removal of photo URL

This PR fixes two issues with updateProfile() at once

defaulting to null for display name and photo url will unset the value when set
photoUrl was not used on Android

Thanks for this!


adds date input to dialog_content directive

For readonly forms, datepicker switches to a disabled input field rather than a datepicker input.  This allows us to apply ng-disabled to the input, aligning the expected behavior of the field with other inputs.

@AllenBW Please rebase and push again

yep, doing this presently!
On Tue, Oct 20, 2015 at 12:51 PM, Oleg Barenboim<EMAIL_ADDRESS>wrote:

@AllenBW https://github.com/AllenBW Please rebase and push again
—
Reply to this email directly or view it on GitHub
https://github.com/ManageIQ/manageiq/pull/4990#issuecomment-149646267.


Use build matrix for GitHub Actions builds

This allows us to add tests for the final Compose file.
CC @wael-sadek.

Done now.


Image not displaying after converting from HTML

I hardcoded a string that has html elements like this (only an img displayed as a figure)

and displayed it in mui-rte using defaultValue={cState}, but it only showed up as an empty figure (an empty square/rectangle).
The figure, upon clicking, will display the Media component, with the registered width & height, but no url.
I checked the ContentState using convertToRaw for converting issues but it does contain the same contentBlocks & entityMap of the coded value, so that might not be an issue.
I can insert a picture & convert it to html with no problem.

The editor uses a custom block (Media) to render the image (img), the problem is the src property is not being found on your editor state.

the problem is the src property is not being found on your editor state.

Can you please explain this further?
Because I thought converting the html using the pictured methods would have included the ### src property.

I believe the problem is that the src property is not being saved in the data for the block (Media). Currently the editor saves this properties (src, width, etc.) on the data of the block.

hey, @niuware, I'm having the same issue, I was trying to load the HTML with this library as well as based on the example but it didn't work for both cases. Not sure how to map the Media block in order to add src property into the data object. Do you have some suggestions?

@patrykkarny @ThongDoo I ran into this issue, too. You need to add a src key/value to the promise response for insertAtomicBlockAsync. The url value doesn't appear to translate into anything as html.


e2e: configure the self-hosted runner to run multiple tests in parallel

As the self-hosted runner is a big one maybe we can try to configure it to be able to run multiple tests at the same time?

A better approach will be tested in #482, so this issue could be closed.


Allow users to configure visible widgets

Problem: initial idea of separating widgets into workflow specific frontstages is not adopted by product teams, which leads to excessive amount of widgets in a single frontstage.
Possible solution: allow users to configure visible widgets.

Related feature request: https://github.com/iTwin/appui/issues/350


clojure-mode 5.6.1

Created with brew bump-formula-pr.

This repo is going to leave the Homebrew org, so it's been disconnected from Jenkins and bottles aren't being created. Could you remove the bottle block?


Dual-Stack VIP

I am trying to setup kube-vip as dual-stack.  I've attempted to run a second instance of Kube-vip by duplicating the yaml and adjusting all of the names to kube-vip6-ds and setting the address to an IPv6 address.  The containers will not start due to this error in the pods.
msg="listen:listen tcp :2112: bind: address already in use\n"
I see the port in use as *:2112 which indicates to me that the process binds on v4 for some internal communications.  Would it be possible to have that process listen on a tcp6 socket when it detects an IPv6 address?
Alternatively, simply allow there to be both a v4 and v6 address assigned at the same time.

That is the Prometheus server. We setup two instances of kube-vip and made sure to change the port from 2112 to something else. That allows you to run several instances

@MikeZappa87 Thanks for the tip.
I am going to leave this open, because I think it should still be easier than having to build two instances.

@MikeZappa87 I started looking into how to adjust the promethus port, but am not finding the flag/env var.  How did you change it?

Below is the avaliable commands.
Usage:
kube-vip [command]
Available Commands:
help        Help about any command
kubeadm     Kubeadm functions
manager     Start the kube-vip manager
manifest    Manifest functions
sample      Generate a Sample configuration
service     Start the Virtual IP / Load balancer as a service within a Kubernetes cluster
start       Start the Virtual IP / Load balancer
version     Version and Release information about the Kubernetes Virtual IP Server
Flags:
--addPeersToLB                  Add raft peers to the load-balancer (default true)
--address string                an address (IP or DNS name) to use as a VIP
--annotations string            Set Node annotations prefix for parsing
--arp                           Enable Arp for Vip changes
--bgp                           This will enable BGP support within kube-vip
--bgpRouterID string            The routerID for the bgp server
--bgppeers strings              Comma seperated BGP Peer, format: address:as:password:multihop
--cidr string                   The CIDR range for the virtual IP address (default "32")
--controlplane                  Enable HA for control plane, hybrid mode
--ddns                          use Dynamic DNS + DHCP to allocate VIP for address
-h, --help                          help for kube-vip
--interface string              Name of the interface to bind to
--lbBackEndPort int             A port that all backends may be using (optional) (default 6444)
--lbBindToVip                   Bind example load balancer to VIP (default true)
--lbEnable                      Enable a load-balancer on the VIP
--lbName string                 The name of a load balancer instance (default "Kubeadm Load Balancer")
--lbPort int                    Port that load balancer will expose on (default 6443)
--lbType string                 Type of load balancer instance (TCP/HTTP) (default "tcp")
--leaderElection                Use the Kubernetes leader election mechanism for clustering
--leaseDuration int             Length of time a Kubernetes leader lease can be held for (default 5)
--leaseRenewDuration int        Length of time a Kubernetes leader can attempt to renew its lease (default 3)
--leaseRetry int                Number of times the host will retry to hold a lease (default 1)
--localAS uint32                The local AS number for the bgp server (default 65000)
--log uint32                    Set the level of logging (default 4)
--metal                         This will use the Equinix Metal API (requires the token ENV) to update the EIP <-> VIP
--metalKey string               The API token for authenticating with the Equinix Metal API
--metalProject string           The name of project already created within Equinix Metal
--metalProjectID string         The ID of project already created within Equinix Metal
--multihop                      This will enable BGP multihop support
-n, --namespace string              The configuration map defined within the cluster (default "kube-system")
--peerAS uint32                 The AS number for a BGP peer (default 65000)
--peerAddress string            The address of a BGP peer
--peerPass string               The md5 password for a BGP peer
--port int                      listen port for the VIP (default 6443)
--promethuesHTTPServer string   Host and port used to expose Promethues metrics via an HTTP server (default ":2112")
--provider-config string        The path to a provider configuration
--services                      Enable Kubernetes services, hybrid mode
--sourceIF string               The source interface for bgp peering (not to be used with sourceIP)
--sourceIP string               The source address for bgp peering (not to be used with sourceIF)
--startAsLeader                 Start this instance as the cluster leader
--vip string                    The Virtual IP address
In the pod yaml:
containers:
- args:
- manager
- --promethuesHTTPServer=:{PortGoesHere}
You probably could set it up with --promethuesHTTPServer={IpAddress:Port} as well

Thank you very much.  Worked like a champ.  i really appreciate your help with this.

Worth comparing notes:
https://github.com/metallb/metallb/issues/698
https://github.com/metallb/metallb/pulls/1065

Can this be closed or would it make sense to add some docs to -> https://github.com/kube-vip/website

Can this be closed or would it make sense to add some docs to -> https://github.com/kube-vip/website

It probably would make sense to be added to the docs to prevent further issues from being opened, once complete this issue should be closed?

Can this really considered solved? Sounds more like a workaround.
If the only thing preventing us from using dual-stack vip is the prometheus port, is it possible to add --disable-prometheus instead?

That is a good point, the code change looks minimal

Yeah can do that..

https://github.com/kube-vip/kube-vip/pull/417

Prometheus port can either be changed or disabled.


optimize some descriptions for swarm nodes.md

optimize some descriptions for swarm nodes.md

:metal: thanks again! LGTM


Update PA branch to 1.1

Signed-off-by: Sruti Parthiban<EMAIL_ADDRESS>Description
Change to use the 1.1 branch of PA in the 1.1 manifest file.
Issues Resolved
[List any issues this PR will resolve]
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #415 (61038aa) into main (49ee171) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #415   +/-   ##
=======================================
  Coverage   59.04%   59.04%
=======================================
  Files          38       38
  Lines        1111     1111
=======================================
  Hits          656      656
  Misses        455      455

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 49ee171...61038aa. Read the comment docs.


Build ODB API version 0.10.3

keyword_ODB_API_OPS_build_compile_link_library   |    by<EMAIL_ADDRESS>
ODB API consists of:

library dealing with the new ODB2/ODA format
the "odb" and "odb_migrator" executables
the python interface

The ODB API library is used during the building of OPS32.0.0. Also during OPS32.0.0 build an ODB API Fortran source file is compiled and linked.
This ticket describes in detail how to build the ECMWF ODB API package (version 0.10.3).

Issue migrated from trac:216 at 2024-01-31 18:18:19 +1100

<EMAIL_ADDRESS>commented

** Here's a brief explanation of how ODB API is used in OPS building as described by David Davies **
Thu 23/07/2015 11:17 PM
The ODB versions used are 1.0.0 for ODB (with some modifications) and ODB API 0.10.3. They are not the same thing; I don't know if they will every be combined. The ODB package contains the code for the original ODB format, including the Fortran interface, the backend, the SQL - C converted and various scripts like odbdup, odbless, odbsql for command line usage. The changes I made were for porting purposes, nothing functional, I can send you those changes if you like. We build it inline with the code but you don't have to do that if it is easier to generate a separate installation and link that, it is up to you. The ODB API package contains the libraries for dealing with the new ODB2/ODA format, the odb and odb_migrator executables and the python interface. We handle this by building the installation separately and linking to it rather than building it inline except there is a single Fortran file for interfacing with Fortran programs, we build that file only as part of the OPS build (as it is compiler dependent whereas the library is not).
There has recently be an ODB API 0.10.5 released. I haven't tried it yet. It seems that eckit has been removed from it but is still required; they haven't released that as a separate library yet. It seems that the only way to build ODB API 0.10.5 at the moment is to build ODB API 0.10.3 as well and make the ODB API 0.10.5 install use the 0.10.3 version of eckit.
Let me know if you need me to send anything.
David Davies From: Jin Lee<EMAIL_ADDRESS>Sent: 23 July 2015 13:45 To: Davies, David Cc: Susan Rennie Subject: RE: obtaining OPS source - OPS31.0.0 [SEC=UNCLASSIFIED]
Hi David,
After receiving Adam's email about the availability of OPS32.0.0 on the shared repository (hooray!) I have started working on creating FCM make config files for our site. With ODB sources there's a couple of references to Met Office internal repositories (in common/core.cfg):
$odb_rev # 89 $odb_api_rev 184
Perhaps this is a good opportunity for us to use the same ODB code that Met Office uses. Can you please tell me what ODB version $odb_rev=89 corresponds to?
About ODB API: I thought ODB API's were part of ODB source (?) Do we ask for ODB API's from ECMWF? If that's the case do you mind telling me what version of ODB API $odb_api_rev=184 corresponds to?
Thank you.
Regards,
Jin

<EMAIL_ADDRESS>commented

odb api version 0.10.3 has been compiled and installed on raijin, and is available for linking with ops32 for testing of ODBcreate.
module load odbapi/0.10.3
the following env settings and options are use in the building of odbapi/0.10.3
module use ~access/modules
module unload netcdf intel-cc intel-fc intel-mpi
module del openmpi
module load cmake
#module load netcdf/4.1.3
module load netcdf/3.6.3
module load intel-cc/<IP_ADDRESS>
module load intel-fc/<IP_ADDRESS>
module load intel-mpi/<IP_ADDRESS>
module unload python/2.7.6-matplotlib
module load odb/1.0.0
cmake ../..
-DCMAKE_BUILD_TYPE=production
-DCMAKE_PREFIX_PATH=$PYTHON_BASE
-DCMAKE_C_COMPILER=/apps/intel-ct/cc-wrapper/icc
-DCMAKE_CXX_COMPILER=/apps/intel-ct/cc-wrapper/icpc
-DCMAKE_Fortran_COMPILER=/apps/intel-ct/fc-wrapper/ifort
-DCMAKE_INSTALL_PREFIX=/projects/access/apps/odb/odbapi/0.10.3
-DFORTRAN_LIBRARIES="-L$INTEL_FC_ROOT/lib/intel64 -lifcore -lifport -liomp5"
-DCMAKE_C_FLAGS="-nofor_main"
-DODB_PATH=$ODB_ROOT
-DECKIT_SOURCE=$SRC/eckit
-DBUILD_SHARED_LIBS=ON
-DENABLE_MIGRATOR=ON
-DENABLE_FORTRAN=ON
-DENABLE_PYTHON=ON
-DBISON_EXECUTABLE=/usr/bin/bison
-DSWIG_EXECUTABLE=/usr/bin/swig

<EMAIL_ADDRESS>changed owner from jtl548 to ttl548

<EMAIL_ADDRESS>changed status from new to assigned

<EMAIL_ADDRESS>commented

Ticket Summary


Neo4jStatement should signal when unsupported operations are called

There are a couple of operations in java.sql.Statement which are not supported by Neoj4Statement, for example addBatch(String) or executeBatch(). This may be obvious for experienced users of Neo4j (I assume that inserting a batch doesn't make sense in Neo4j ?!).
However, if one is not aware of this behavior, using this methods will cause hard to find bugs. I propose to write a warning to the log or even better throw an UnsupportedOperationException whenever one of the methods which are currently not implemented is called.

In order to improve the writing performance, hope to achieve "addBatch and executeBatch" as quickly as possible.thanks.

#35 has been merged so this issue can be closed.


WIP: Include both v2 and v3 flags in etcdctl vars

WIP as untested, just wanted it off my PC before I forgot about it :)

We should also consider how to setup variable ETCDCTL_API=<version>, 2 or 3

We should also consider how to setup variable ETCDCTL_API=, 2 or 3

Yea, I actually started that, and then realised it might cause you pain in the datastore migration PR, so left it for now


Scrolling through workspaces does not work for me

arch linux
wayland 1.19.0-1
sway 1:1.5.1-1
waybar 0.9.5-2
"sway/workspaces": {
    "enable-bar-scroll":true
},

What could be the reason?

Oh, rookie mistake, a second section with:
"sway/workspaces": {
"all-outputs": false,
"disable-scroll": true,
"format": "{name}"
},
Error corrected and everything works...


Proposal: add support for sqlite

in redmine instruction page, sqlite can be used as the database, do we have any plan adding support for SQLite3?

Do we have a plan?  No.  If you want to give it a shot, go for it.

I think in general its not a bad idea to even default to sqllite for running this in smaller environments.

Made a branch for sqlite support.  Still needs backup/restore support.
https://github.com/sameersbn/docker-redmine/tree/sqlite3

And documentation

just made similar change in a pull request... :), wish I was quicker.

https://github.com/sameersbn/docker-redmine/pull/352

@brother-fu  Woops.  Lets see if we can take the better parts of each implementation.

Pushed another commit to fixup some things.  Still missing backup/restore functionality.
https://github.com/sameersbn/docker-redmine/commit/1af24f7363aab6175ddcaede997070cb3863dc00

Was there any further development?
I would be very interested, but I don't want to be trapped in a dead branch.
Thanks!

@mcondarelli I have not had time to work on this further.  If you could implement the backup/restore commands.  And verify it all worked.  I'd be happy to merge it.

Task list:

implement the backup/restore commands
update the documentation
Create example docker-compose file

I installed the sqlite branch, and it seemed to work, but plugin installation (plantuml) fails badly:

The plugin you linked doesn't support redmine 4.1 so I switched to this fork of it and the plugin migrate no longer failed. Though I'm not sure why.
https://github.com/hitsoft-redmine/plantuml

Note: I've merged the recent changes in master into the sqlite3 branch

Thanks.
I'll give it a spin tomorrow (and I will try to understand what went wrong, beside the trivial check).
Side question: what is the advised way to install Java (and, possibly, dot) in the Container?
Doing a apt install openjdk-8-jre-headless in the running container (docker exec -it synology_redmine bash) works, but it will be lost if container is recreated, which, sooner or later will happen.
Hand-modifying Dockerfile doesn't look as the right solution, or is it?
TiA!

Check the read me. There is a pre and post install script that gets run.
Alternatively you would normal create a dockerfile which starts from the
published image and just adds your changes. But this branch hasnt been
published since no one had tested it and its missing the backup/restore
feature.
On Mon, Jun 8, 2020, 5:25 PM Mauro Condarelli<EMAIL_ADDRESS>wrote:

Thanks.
I'll give it a spin tomorrow (and I will try to understand what went
wrong, beside the trivial check).
Side question: what is the advised way to install Java (and, possibly, dot)
in the Container?
Doing a apt install openjdk-8-jre-headless in the running container (docker
exec -it synology_redmine bash) works, but it will be lost if container
is recreated, which, sooner or later will happen.
Hand-modifying Dockerfile doesn't look as the right solution, or is it?
TiA!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sameersbn/docker-redmine/issues/350#issuecomment-640895653,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABK2RGK7N7FE7LAZCI6KJCDRVVJK3ANCNFSM4FNHIBAQ
.

Continuing here because this has nothing to do with #428.
I am successfully porting using the following script (I always script things to be able to repeat exactly the same path):
#!/bin/bash
set -e
set -x

here=$(pwd)
cd ..

#migrate database
data=$(pwd)/data
if [ ! -d $data ]
then
  dir=/tmp/rb_dir
  mkdir $data $data/plugins $data/files $data/dotfiles
  bkf=$(ls -1 $here/*_redmine_backup.tar)
  if [ -f $bkf ]
  then
    [ -d $dir ] && rm -r $dir
    mkdir $dir
    pushd $dir
      tar xf $bkf
      zcat database.sql.gz | $here/mysql2sqlite - | sqlite3 db.sqlite3
    popd
    pushd $data
      mv $dir/db.sqlite3 .
      tar xf $dir/files.tar -C files
      tar xf $dir/dotfiles.tar.gz -C dotfiles
    popd
    migrate="doit"
  fi
fi
#end migrate database

#setup plugins
pushd $data/plugins

#setup plugin plantuml
[ -d jre ] || tar xzf $here/openjre-8u41-b04-linux-x64-14_jan_2020.tar.gz
if [ ! -d plantuml ]
then
  git clone https://github.com/hitsoft-redmine/plantuml.git
  pushd plantuml
  cp $here/plantuml.jar .
  cat <<'EOF' >plantuml
#!/bin/bash
here=$(dirname $(readlink --canonicalize $0))
JAVA=/home/redmine/data/plugins/jre
export classpath=${JAVA}
${JAVA}/bin/java -Djava.io.tmpdir=/var/tmp -Djava.awt.headless=true -jar ${here}/plantuml.jar ${@}
EOF
  popd
fi
#end setup plugin plantuml

#setup plugin redmine_dmsf
if [ ! -d redmine_dmsf ]
then
  git clone https://github.com/danmunn/redmine_dmsf.git
  chmod -R ugo+w redmine_dmsf
  sed -i '/dalli/ s/$/,  "~> 2.7.0"/' redmine_dmsf/Gemfile
  cat >>pre-install.sh <<EOF
chown -Rc www-data:www-data /var/www
chmod ugo+w /var/www
EOF
  chmod +x pre-install.sh
fi
#end setup plugin redmine_dmsf

#setup plugin redmine_knowlwdgebase
##[ -d redmine_knowledgebase ] || git clone https://github.com/alexbevi/redmine_knowledgebase.git
#end setup plugin redmine_knowlwdgebase

#end setup plugins

popd

docker images | grep -q '^sqlite-redmine' \
    || docker build --tag sqlite-redmine .

options="  --name=sqlite-redmine \
           --env=TZ=Europe/Rome \
           --env=DB_ADAPTER=sqlite3 \
           --env=DB_NAME=db.sqlite3 \
           --env=REDMINE_PORT=10083 \
           --env=REDMINE_HTTPS=false \
           --env=REDMINE_RELATIVE_URL_ROOT= \
           --env=REDMINE_SECRET_TOKEN= \
           --env=REDMINE_SUDO_MODE_ENABLED=false \
           --env=REDMINE_SUDO_MODE_TIMEOUT=15 \
           --env=REDMINE_CONCURRENT_UPLOADS=2 \
           --env=REDMINE_BACKUP_SCHEDULE= \
           --env=REDMINE_BACKUP_EXPIRY= \
           --env=REDMINE_BACKUP_TIME= \
           --env=SMTP_ENABLED=false \
           --env=SMTP_METHOD=smtp \
           --env=SMTP_DOMAIN=example.org \
           --env=SMTP_HOST=smtp.gmail.com \
           --env=SMTP_PORT=587 \
<EMAIL_ADDRESS>\
           --env=SMTP_PASS=password \
           --env=SMTP_STARTTLS=true \
           --env=SMTP_AUTHENTICATION=:login \
           --env=IMAP_ENABLED=true \
           --env=IMAP_HOST=imap.gmail.com \
           --env=IMAP_PORT=993 \
<EMAIL_ADDRESS>\
           --env=IMAP_PASS=pasword \
           --env=IMAP_SSL=true \
           --env=IMAP_INTERVAL=30 \
           --env=NGINX_MAX_UPLOAD_SIZE=100m \
           --volume=$data:/home/redmine/data \
           --volume=$data/log:/var/log/redmine/redmine \
           --publish=10083:80"

if [ -n "$migrate" ]
then
  docker run -it --rm $options sqlite-redmine app:rake db:migrate
  docker run -it --rm $options sqlite-redmine app:rake redmine:plugins:migrate
fi
docker run -it --rm $options sqlite-redmine

This file sits in a directory inside docker-redmine containing also other stuff:
1594058713_redmine_backup.tar                   Backup produced by Redmine 3.3.10.stable / Mysql2
mysql2sqlite                                    From: https://github.com/dumblob/mysql2sqlite (note: MUST use mawk!)
openjre-8u41-b04-linux-x64-14_jan_2020.tar.gz   Needed by plantuml
plantuml.jar                                    From: http://sourceforge.net/projects/plantuml/files/plantuml.jar/download
start-sqlite3.sh                                The script above

Tomorrow I'll test backup/restore features (hopefully I'll find some time ;) )

FYI: I unpacked _redmine_backup.tar to temporary directories
rb_dir is from old installation (3.3.10.stable / Mysql2) and rb_dir2 is from new installation (4.1.1.stable / SQLite):
mcon@cinderella:/tmp$ file rb_dir*/*
rb_dir2/backup_information.yml: ASCII text
rb_dir2/database.sql.gz:        gzip compressed data, was "database.sql", last modified: Thu Jul  9 21:38:48 2020, from Unix, original size modulo 2^32 324412379
rb_dir2/dotfiles.tar.gz:        gzip compressed data, last modified: Thu Jul  9 21:38:56 2020, from Unix, original size modulo 2^32 40960
rb_dir2/files.tar:              POSIX tar archive (GNU)
rb_dir2/plugins.tar.gz:         gzip compressed data, last modified: Thu Jul  9 21:38:56 2020, from Unix, original size modulo 2^32 227962880 gzip compressed data, unknown method, has CRC, extra field, has comment, encrypted, from FAT filesystem (MS-DOS, OS/2, NT), original size modulo 2^32 227962880
rb_dir2/themes.tar.gz:          gzip compressed data, last modified: Thu Jul  9 21:39:02 2020, from Unix, original size modulo 2^32 10240
rb_dir/backup_information.yml:  ASCII text
rb_dir/database.sql.gz:         gzip compressed data, was "database.sql", last modified: Mon Jul  6 18:04:48 2020, from Unix, original size modulo 2^32 278106313
rb_dir/dotfiles.tar.gz:         POSIX tar archive (GNU)
rb_dir/files.tar:               POSIX tar archive (GNU)
rb_dir/plugins.tar.gz:          POSIX tar archive (GNU)
rb_dir/themes.tar.gz:           POSIX tar archive (GNU)

Note that "old" backup was taken on a Synology NAS, using their own specific version of sameersbn/docker-redmine and I don't know if it was modified or just repackaged.
If You think I should do further testing just let me know.
What is the recommended way to use backups?
Can I start a clean (empty data) installation as: docker run --name sqlite-redmine -it --rm [OPTIONS] sameersbn/redmine:4.1.1-3 app:backup:restore and hope to have all my data preserved (possibly on a brand new server)?

Hmm, its likely I fixed the tar compression sometime since 3.3.10, it
sounds vaguely familiar...
Yes I would hope the backup could be used on a fresh install to get the
server back up and running.
On Thu, Jul 9, 2020 at 6:01 PM Mauro Condarelli<EMAIL_ADDRESS>wrote:

FYI: I unpacked _redmine_backup.tar to temporary directories
rb_dir is from old installation (3.3.10.stable / Mysql2) and rb_dir2 is
from new installation (4.1.1.stable / SQLite):
mcon@cinderella:/tmp$ file rb_dir*/*
rb_dir2/backup_information.yml: ASCII text
rb_dir2/database.sql.gz:        gzip compressed data, was "database.sql", last modified: Thu Jul  9 21:38:48 2020, from Unix, original size modulo 2^32 324412379
rb_dir2/dotfiles.tar.gz:        gzip compressed data, last modified: Thu Jul  9 21:38:56 2020, from Unix, original size modulo 2^32 40960
rb_dir2/files.tar:              POSIX tar archive (GNU)
rb_dir2/plugins.tar.gz:         gzip compressed data, last modified: Thu Jul  9 21:38:56 2020, from Unix, original size modulo 2^32 227962880 gzip compressed data, unknown method, has CRC, extra field, has comment, encrypted, from FAT filesystem (MS-DOS, OS/2, NT), original size modulo 2^32 227962880
rb_dir2/themes.tar.gz:          gzip compressed data, last modified: Thu Jul  9 21:39:02 2020, from Unix, original size modulo 2^32 10240
rb_dir/backup_information.yml:  ASCII text
rb_dir/database.sql.gz:         gzip compressed data, was "database.sql", last modified: Mon Jul  6 18:04:48 2020, from Unix, original size modulo 2^32 278106313
rb_dir/dotfiles.tar.gz:         POSIX tar archive (GNU)
rb_dir/files.tar:               POSIX tar archive (GNU)
rb_dir/plugins.tar.gz:          POSIX tar archive (GNU)
rb_dir/themes.tar.gz:           POSIX tar archive (GNU)
Note that "old" backup was taken on a Synology NAS, using their own
specific version of sameersbn/docker-redmine and I don't know if it was
modified or just repackaged.
If You think I should do further testing just let me know.
What is the recommended way to use backups?
Can I start a clean (empty data) installation as: docker run --name
sqlite-redmine -it --rm [OPTIONS] sameersbn/redmine:4.1.1-3
app:backup:restore and hope to have all my data preserved (possibly on a
brand new server)?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sameersbn/docker-redmine/issues/350#issuecomment-656372224,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABK2RGPALVJTYIZHN6HFCVLR2Y437ANCNFSM4FNHIBAQ
.

--
Jonathan Cormier
Software Engineer
Voice:<PHONE_NUMBER> x222
http://www.CriticalLink.com http://www.criticallink.com/
6712 Brooklawn Parkway, Syracuse, NY 13211
https://www.linkedin.com/company/critical-link-llc
https://twitter.com/Critical_Link

I can confirm backup/restore is working correctly with SQLite.
Diff is really minimal:
diff --git a/assets/runtime/functions b/assets/runtime/functions
index 1096868..e11e55c 100644
--- a/assets/runtime/functions
+++ b/assets/runtime/functions
@@ -525,7 +525,8 @@ backup_dump_database() {
         ${database_production_database} > ${config_default_backup_storage_path}/database.sql
       ;;
     sqlite3)
-      echo "TODO"
+      echo "Dumping SQLite database ${database_production_database}..."
+      sqlite3 ${database_production_database} .dump > ${config_default_backup_storage_path}/database.sql
       ;;
   esac
   chown ${REDMINE_USER}: ${config_default_backup_storage_path}/database.sql
@@ -646,7 +647,9 @@ backup_restore_database() {
           ${database_production_database}
       ;;
     sqlite3)
-      echo "TODO"
+      echo "Restoring SQLite database..."
+      gzip -dc ${config_default_backup_storage_path}/database.sql.gz | \
+        sqlite3 ${database_production_database}
       ;;
     *)
       echo "Database type ${database_production_adapter} not supported."

This is still working with no adverse effect.
Is there any hope to have the branch merged back in master?

Alright, I added your changes. And merged in the sqlite branch.

Should be available when 4.1.1-4 finish building


Unable to change email if PowEmailConfirmation is not used

Hello! I detected this in 1.0.7, now I have upgraded to 1.0.19 and the issue still happens:
I'm using Pow with these extensions: extensions: [PowResetPassword, PowPersistentSession]
Notice I'm not using PowEmailConfirmation. Users can sign up and log in just fine, but if they edit their accounts and change the email address, they're told everything is fine but the email is not changed.
From the logs I see that a new email confirmation is generated, but the confirmation email is not sent.
If I use the PowEmailConfirmation extension then users can change their email after they confirm by clicking the link sent.
Proposed fix:
If the PowEmailConfirmation extension is not used, then the users should be able to change their email without confirming it (that is, only the current password would be needed).
Alternative fix:
Being able to use the PowEmailConfirmation extension only on email change, but not on sign up.

I assume you have set your app up with PowEmailConfirmation originally and then removed it again? You'll need to remove it from your  User schema module as well, otherwise the PowEmailConfirmation changeset kicks in.
The email_confirmation_token, email_confirmed_at and unconfirmed_email fields only gets added if you had PowEmailConfirmation enabled, and the changeset will only kick in if PowEmailConfirmation is still enabled.

Ah! That was it, of course! I had removed the extension from the config but forgot to remove it from the User schema as well. 🤦♂
Thanks! 😃


adding support for specifying rule import paths

to: @airbnb/streamalert-maintainers
cc:
size: small|medium|large
resolves #
Background
Currently based largely on changes in #689, this enables specifying arbitrary paths from within which to import rule and matcher files.
Changes

Adding rule_locations and matcher_locations options to global config (see Up for Disucssion below for more info).
Moving rule import logic to the stream_alert.shared.rule module so it is decoupled from the lambda handler code.
Calling the import code from within the new RulesEngine class, which will load the various paths in the config.
Updating stream_alert_cli/test.py to remove the formerly required import stream_alert.rule_processor.main line to force rule loading out of band.
Updating message in a NameError that was improperly formatting output.

Up for Discussion

Naming convention for the rule_locations - I've currently put this under a general category in the global.json config but I'm not 100% in love with that. Any ideas?
We could now support 'global' rules as well as having rules specific to clusters (in the cluster's rule processor config). This could actually result in a slight optimization. There are surely clusters we have now that use 'matchers' to restrict on environment when we could just restrict what rules are loaded for a given environment.

Testing
Migrating rule loading unit tests to the stream_alert_shared/test_rule.py tests file.
Removing parts of TestRulesEngine that were not actually doing anything.

Coverage remained the same at 96.311% when pulling 79deb822711452b86c78396f02eca19febced95b on ryandeivert-rule-rework-with-path-import into 1e99914089ad471e5a94739db2331a42d9676793 on ryandeivert-rule-rework.


Add recent release dates in a skos:historyNote

Closes #1017.

Date of 13.0.0 might need to change if release slips.