No module named 'edf'

installation seems to be done correctly, but python does not find edf module when trying to import edf! Any hint?!
running install running build running build_py creating build creating build/lib.macosx-10.12-x86_64-3.6 creating build/lib.macosx-10.12-x86_64-3.6/pyedfread copying pyedfread/__init__.py -> build/lib.macosx-10.12-x86_64-3.6/pyedfread copying pyedfread/edf.py -> build/lib.macosx-10.12-x86_64-3.6/pyedfread copying pyedfread/test.py -> build/lib.macosx-10.12-x86_64-3.6/pyedfread running build_ext cythoning pyedfread/edf_data.pyx to pyedfread/edf_data.c building 'pyedfread.edf_data' extension creating build/temp.macosx-10.12-x86_64-3.6 creating build/temp.macosx-10.12-x86_64-3.6/pyedfread clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/usr/local/lib/python3.6/site-packages/numpy/core/include -I/Library/Frameworks/edfapi.framework/Headers -I/usr/local/include -I/usr/local/opt/openssl/include -I/usr/local/opt/sqlite/include -I/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/include/python3.6m -c pyedfread/edf_data.c -o build/temp.macosx-10.12-x86_64-3.6/pyedfread/edf_data.o -w clang -bundle -undefined dynamic_lookup build/temp.macosx-10.12-x86_64-3.6/pyedfread/edf_data.o -L/usr/local/lib -L/usr/local/opt/openssl/lib -L/usr/local/opt/sqlite/lib -o build/lib.macosx-10.12-x86_64-3.6/pyedfread/edf_data.cpython-36m-darwin.so -F/Library/Frameworks/ -framework edfapi cythoning pyedfread/edfread.pyx to pyedfread/edfread.c building 'pyedfread.edfread' extension clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/usr/local/lib/python3.6/site-packages/numpy/core/include -I/Library/Frameworks/edfapi.framework/Headers -I/usr/local/include -I/usr/local/opt/openssl/include -I/usr/local/opt/sqlite/include -I/usr/local/Cellar/python3/3.6.1/Frameworks/Python.framework/Versions/3.6/include/python3.6m -c pyedfread/edfread.c -o build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o -w clang -bundle -undefined dynamic_lookup build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o -L/usr/local/lib -L/usr/local/opt/openssl/lib -L/usr/local/opt/sqlite/lib -o build/lib.macosx-10.12-x86_64-3.6/pyedfread/edfread.cpython-36m-darwin.so -F/Library/Frameworks/ -framework edfapi ld: warning: pointer not aligned at address 0x2CA4E (___pyx_string_tab + 7358 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2CA46 (___pyx_string_tab + 7350 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2CA2B (___pyx_string_tab + 7323 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2CA23 (___pyx_string_tab + 7315 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C9E5 (___pyx_string_tab + 7253 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C9DD (___pyx_string_tab + 7245 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C9C2 (___pyx_string_tab + 7218 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C9BA (___pyx_string_tab + 7210 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C99F (___pyx_string_tab + 7183 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C997 (___pyx_string_tab + 7175 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C959 (___pyx_string_tab + 7113 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C951 (___pyx_string_tab + 7105 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C936 (___pyx_string_tab + 7078 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C92E (___pyx_string_tab + 7070 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C913 (___pyx_string_tab + 7043 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C90B (___pyx_string_tab + 7035 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C8CD (___pyx_string_tab + 6973 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C8C5 (___pyx_string_tab + 6965 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C8AA (___pyx_string_tab + 6938 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C8A2 (___pyx_string_tab + 6930 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C887 (___pyx_string_tab + 6903 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C87F (___pyx_string_tab + 6895 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C841 (___pyx_string_tab + 6833 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C839 (___pyx_string_tab + 6825 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C81E (___pyx_string_tab + 6798 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C816 (___pyx_string_tab + 6790 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C7FB (___pyx_string_tab + 6763 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C7F3 (___pyx_string_tab + 6755 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C7B5 (___pyx_string_tab + 6693 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C7AD (___pyx_string_tab + 6685 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C792 (___pyx_string_tab + 6658 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C78A (___pyx_string_tab + 6650 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C76F (___pyx_string_tab + 6623 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C767 (___pyx_string_tab + 6615 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C729 (___pyx_string_tab + 6553 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C721 (___pyx_string_tab + 6545 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C706 (___pyx_string_tab + 6518 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C6FE (___pyx_string_tab + 6510 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C6E3 (___pyx_string_tab + 6483 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C6DB (___pyx_string_tab + 6475 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C69D (___pyx_string_tab + 6413 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C695 (___pyx_string_tab + 6405 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C67A (___pyx_string_tab + 6378 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C672 (___pyx_string_tab + 6370 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C657 (___pyx_string_tab + 6343 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C64F (___pyx_string_tab + 6335 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C611 (___pyx_string_tab + 6273 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C609 (___pyx_string_tab + 6265 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C5EE (___pyx_string_tab + 6238 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C5E6 (___pyx_string_tab + 6230 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C5CB (___pyx_string_tab + 6203 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C5C3 (___pyx_string_tab + 6195 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C585 (___pyx_string_tab + 6133 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C57D (___pyx_string_tab + 6125 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C562 (___pyx_string_tab + 6098 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C55A (___pyx_string_tab + 6090 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C53F (___pyx_string_tab + 6063 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C537 (___pyx_string_tab + 6055 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C4F9 (___pyx_string_tab + 5993 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C4F1 (___pyx_string_tab + 5985 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C4D6 (___pyx_string_tab + 5958 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C4CE (___pyx_string_tab + 5950 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C4B3 (___pyx_string_tab + 5923 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C4AB (___pyx_string_tab + 5915 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C46D (___pyx_string_tab + 5853 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C465 (___pyx_string_tab + 5845 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C44A (___pyx_string_tab + 5818 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C442 (___pyx_string_tab + 5810 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C427 (___pyx_string_tab + 5783 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C41F (___pyx_string_tab + 5775 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C3E1 (___pyx_string_tab + 5713 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C3D9 (___pyx_string_tab + 5705 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C3BE (___pyx_string_tab + 5678 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C3B6 (___pyx_string_tab + 5670 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C39B (___pyx_string_tab + 5643 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C393 (___pyx_string_tab + 5635 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C355 (___pyx_string_tab + 5573 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C34D (___pyx_string_tab + 5565 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C332 (___pyx_string_tab + 5538 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C32A (___pyx_string_tab + 5530 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C30F (___pyx_string_tab + 5503 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C307 (___pyx_string_tab + 5495 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C2C9 (___pyx_string_tab + 5433 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C2C1 (___pyx_string_tab + 5425 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C2A6 (___pyx_string_tab + 5398 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C29E (___pyx_string_tab + 5390 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C283 (___pyx_string_tab + 5363 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C27B (___pyx_string_tab + 5355 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C23D (___pyx_string_tab + 5293 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C235 (___pyx_string_tab + 5285 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C21A (___pyx_string_tab + 5258 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C212 (___pyx_string_tab + 5250 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C1F7 (___pyx_string_tab + 5223 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C1EF (___pyx_string_tab + 5215 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C1B1 (___pyx_string_tab + 5153 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C1A9 (___pyx_string_tab + 5145 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C18E (___pyx_string_tab + 5118 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C186 (___pyx_string_tab + 5110 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C16B (___pyx_string_tab + 5083 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C163 (___pyx_string_tab + 5075 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C125 (___pyx_string_tab + 5013 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C11D (___pyx_string_tab + 5005 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C102 (___pyx_string_tab + 4978 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C0FA (___pyx_string_tab + 4970 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C0DF (___pyx_string_tab + 4943 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C0D7 (___pyx_string_tab + 4935 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C099 (___pyx_string_tab + 4873 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C091 (___pyx_string_tab + 4865 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C076 (___pyx_string_tab + 4838 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C06E (___pyx_string_tab + 4830 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C053 (___pyx_string_tab + 4803 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C04B (___pyx_string_tab + 4795 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C00D (___pyx_string_tab + 4733 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2C005 (___pyx_string_tab + 4725 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BFEA (___pyx_string_tab + 4698 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BFE2 (___pyx_string_tab + 4690 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BFC7 (___pyx_string_tab + 4663 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BFBF (___pyx_string_tab + 4655 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BF81 (___pyx_string_tab + 4593 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BF79 (___pyx_string_tab + 4585 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BF5E (___pyx_string_tab + 4558 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BF56 (___pyx_string_tab + 4550 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BF3B (___pyx_string_tab + 4523 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BF33 (___pyx_string_tab + 4515 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BEF5 (___pyx_string_tab + 4453 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BEED (___pyx_string_tab + 4445 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BED2 (___pyx_string_tab + 4418 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BECA (___pyx_string_tab + 4410 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BEAF (___pyx_string_tab + 4383 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BEA7 (___pyx_string_tab + 4375 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BE69 (___pyx_string_tab + 4313 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BE61 (___pyx_string_tab + 4305 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BE46 (___pyx_string_tab + 4278 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BE3E (___pyx_string_tab + 4270 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BE23 (___pyx_string_tab + 4243 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BE1B (___pyx_string_tab + 4235 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BDDD (___pyx_string_tab + 4173 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BDD5 (___pyx_string_tab + 4165 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BDBA (___pyx_string_tab + 4138 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BDB2 (___pyx_string_tab + 4130 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BD97 (___pyx_string_tab + 4103 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BD8F (___pyx_string_tab + 4095 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BD51 (___pyx_string_tab + 4033 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BD49 (___pyx_string_tab + 4025 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BD2E (___pyx_string_tab + 3998 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BD26 (___pyx_string_tab + 3990 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BD0B (___pyx_string_tab + 3963 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BD03 (___pyx_string_tab + 3955 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BCC5 (___pyx_string_tab + 3893 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BCBD (___pyx_string_tab + 3885 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BCA2 (___pyx_string_tab + 3858 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BC9A (___pyx_string_tab + 3850 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BC7F (___pyx_string_tab + 3823 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BC77 (___pyx_string_tab + 3815 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BC39 (___pyx_string_tab + 3753 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BC31 (___pyx_string_tab + 3745 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BC16 (___pyx_string_tab + 3718 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BC0E (___pyx_string_tab + 3710 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BBF3 (___pyx_string_tab + 3683 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BBEB (___pyx_string_tab + 3675 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BBAD (___pyx_string_tab + 3613 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BBA5 (___pyx_string_tab + 3605 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BB8A (___pyx_string_tab + 3578 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BB82 (___pyx_string_tab + 3570 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BB67 (___pyx_string_tab + 3543 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BB5F (___pyx_string_tab + 3535 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BB21 (___pyx_string_tab + 3473 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BB19 (___pyx_string_tab + 3465 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BAFE (___pyx_string_tab + 3438 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BAF6 (___pyx_string_tab + 3430 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BADB (___pyx_string_tab + 3403 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BAD3 (___pyx_string_tab + 3395 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BA95 (___pyx_string_tab + 3333 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BA8D (___pyx_string_tab + 3325 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BA72 (___pyx_string_tab + 3298 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BA6A (___pyx_string_tab + 3290 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BA4F (___pyx_string_tab + 3263 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BA47 (___pyx_string_tab + 3255 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BA09 (___pyx_string_tab + 3193 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2BA01 (___pyx_string_tab + 3185 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B9E6 (___pyx_string_tab + 3158 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B9DE (___pyx_string_tab + 3150 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B9C3 (___pyx_string_tab + 3123 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B9BB (___pyx_string_tab + 3115 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B97D (___pyx_string_tab + 3053 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B975 (___pyx_string_tab + 3045 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B95A (___pyx_string_tab + 3018 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B952 (___pyx_string_tab + 3010 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B937 (___pyx_string_tab + 2983 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B92F (___pyx_string_tab + 2975 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B8F1 (___pyx_string_tab + 2913 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B8E9 (___pyx_string_tab + 2905 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B8CE (___pyx_string_tab + 2878 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B8C6 (___pyx_string_tab + 2870 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B8AB (___pyx_string_tab + 2843 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B8A3 (___pyx_string_tab + 2835 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B865 (___pyx_string_tab + 2773 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B85D (___pyx_string_tab + 2765 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B842 (___pyx_string_tab + 2738 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B83A (___pyx_string_tab + 2730 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B81F (___pyx_string_tab + 2703 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B817 (___pyx_string_tab + 2695 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B7D9 (___pyx_string_tab + 2633 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B7D1 (___pyx_string_tab + 2625 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B7B6 (___pyx_string_tab + 2598 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B7AE (___pyx_string_tab + 2590 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B793 (___pyx_string_tab + 2563 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B78B (___pyx_string_tab + 2555 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B74D (___pyx_string_tab + 2493 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B745 (___pyx_string_tab + 2485 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B72A (___pyx_string_tab + 2458 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B722 (___pyx_string_tab + 2450 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B707 (___pyx_string_tab + 2423 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B6FF (___pyx_string_tab + 2415 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B6C1 (___pyx_string_tab + 2353 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B6B9 (___pyx_string_tab + 2345 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B69E (___pyx_string_tab + 2318 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B696 (___pyx_string_tab + 2310 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B67B (___pyx_string_tab + 2283 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B673 (___pyx_string_tab + 2275 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B635 (___pyx_string_tab + 2213 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B62D (___pyx_string_tab + 2205 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B612 (___pyx_string_tab + 2178 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B60A (___pyx_string_tab + 2170 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B5EF (___pyx_string_tab + 2143 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B5E7 (___pyx_string_tab + 2135 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B5A9 (___pyx_string_tab + 2073 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B5A1 (___pyx_string_tab + 2065 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B586 (___pyx_string_tab + 2038 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B57E (___pyx_string_tab + 2030 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B563 (___pyx_string_tab + 2003 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B55B (___pyx_string_tab + 1995 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B51D (___pyx_string_tab + 1933 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B515 (___pyx_string_tab + 1925 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B4FA (___pyx_string_tab + 1898 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B4F2 (___pyx_string_tab + 1890 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B4D7 (___pyx_string_tab + 1863 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B4CF (___pyx_string_tab + 1855 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B491 (___pyx_string_tab + 1793 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B489 (___pyx_string_tab + 1785 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B46E (___pyx_string_tab + 1758 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B466 (___pyx_string_tab + 1750 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B44B (___pyx_string_tab + 1723 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B443 (___pyx_string_tab + 1715 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B405 (___pyx_string_tab + 1653 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B3FD (___pyx_string_tab + 1645 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B3E2 (___pyx_string_tab + 1618 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B3DA (___pyx_string_tab + 1610 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B3BF (___pyx_string_tab + 1583 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B3B7 (___pyx_string_tab + 1575 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B379 (___pyx_string_tab + 1513 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B371 (___pyx_string_tab + 1505 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B356 (___pyx_string_tab + 1478 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B34E (___pyx_string_tab + 1470 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B333 (___pyx_string_tab + 1443 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B32B (___pyx_string_tab + 1435 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B2ED (___pyx_string_tab + 1373 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B2E5 (___pyx_string_tab + 1365 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B2CA (___pyx_string_tab + 1338 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B2C2 (___pyx_string_tab + 1330 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B2A7 (___pyx_string_tab + 1303 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B29F (___pyx_string_tab + 1295 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B261 (___pyx_string_tab + 1233 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B259 (___pyx_string_tab + 1225 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B23E (___pyx_string_tab + 1198 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B236 (___pyx_string_tab + 1190 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B21B (___pyx_string_tab + 1163 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B213 (___pyx_string_tab + 1155 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B1D5 (___pyx_string_tab + 1093 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B1CD (___pyx_string_tab + 1085 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B1B2 (___pyx_string_tab + 1058 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B1AA (___pyx_string_tab + 1050 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B18F (___pyx_string_tab + 1023 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B187 (___pyx_string_tab + 1015 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B149 (___pyx_string_tab + 953 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B141 (___pyx_string_tab + 945 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B126 (___pyx_string_tab + 918 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B11E (___pyx_string_tab + 910 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B103 (___pyx_string_tab + 883 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B0FB (___pyx_string_tab + 875 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B0BD (___pyx_string_tab + 813 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B0B5 (___pyx_string_tab + 805 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B09A (___pyx_string_tab + 778 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B092 (___pyx_string_tab + 770 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B077 (___pyx_string_tab + 743 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B06F (___pyx_string_tab + 735 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B031 (___pyx_string_tab + 673 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B029 (___pyx_string_tab + 665 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B00E (___pyx_string_tab + 638 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2B006 (___pyx_string_tab + 630 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AFEB (___pyx_string_tab + 603 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AFE3 (___pyx_string_tab + 595 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AFA5 (___pyx_string_tab + 533 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AF9D (___pyx_string_tab + 525 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AF82 (___pyx_string_tab + 498 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AF7A (___pyx_string_tab + 490 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AF5F (___pyx_string_tab + 463 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AF57 (___pyx_string_tab + 455 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AF19 (___pyx_string_tab + 393 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AF11 (___pyx_string_tab + 385 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AEF6 (___pyx_string_tab + 358 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AEEE (___pyx_string_tab + 350 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AED3 (___pyx_string_tab + 323 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AECB (___pyx_string_tab + 315 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AE8D (___pyx_string_tab + 253 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AE85 (___pyx_string_tab + 245 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AE6A (___pyx_string_tab + 218 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AE62 (___pyx_string_tab + 210 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AE47 (___pyx_string_tab + 183 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AE3F (___pyx_string_tab + 175 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2AE01 (___pyx_string_tab + 113 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2ADF9 (___pyx_string_tab + 105 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2ADDE (___pyx_string_tab + 78 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2ADD6 (___pyx_string_tab + 70 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2ADBB (___pyx_string_tab + 43 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) ld: warning: pointer not aligned at address 0x2ADB3 (___pyx_string_tab + 35 from build/temp.macosx-10.12-x86_64-3.6/pyedfread/edfread.o) running build_scripts creating build/scripts-3.6 copying and adjusting pyedfread/read_edf -> build/scripts-3.6 changing mode of build/scripts-3.6/read_edf from 644 to 755 running install_lib copying build/lib.macosx-10.12-x86_64-3.6/pyedfread/edf_data.cpython-36m-darwin.so -> /usr/local/lib/python3.6/site-packages/pyedfread copying build/lib.macosx-10.12-x86_64-3.6/pyedfread/edfread.cpython-36m-darwin.so -> /usr/local/lib/python3.6/site-packages/pyedfread running install_scripts copying build/scripts-3.6/read_edf -> /usr/local/bin changing mode of /usr/local/bin/read_edf to 755 running install_egg_info Writing /usr/local/lib/python3.6/site-packages/pyedfread-0.1-py3.6.egg-info

I tried to reinstall again. Now I can 'import pyedfread' but still 'import edf' does not work!

Sorry for the long delay - I think this is a bug in the doc. Try running

from pyedfread import edf

and see if this works for you.

Thanks! Yes 'from pyedfread import edf' works.


Add JSON::JWT.decode_with_keys

Decode token given a array of keys [{:kid => ..., :key => ...}, ...].
Makes it possible to match kid in JOSE header to use correct key when there are
multiple public keys.

Required by nov/openid_connect#23

Probably refactoring JSON::JWK & JSON::JWK::Set is the best way for easy to read coding.
Let me try it first.
Thanks for your contribution!

This commit will allow you to give JSON::JWK::Set instance as public key on JSON::JWT.decode.
Isn't it wat you really expect?
https://github.com/nov/json-jwt/commit/a4f1fc5e3f06070690a6643e32e6146861ac5efa

Looks more sane than my attempt :+1: so no changes is need to openid_connect? but omniauth-openid-connect still need a change to use multiple keys right? i.e. https://github.com/jjbohn/omniauth-openid-connect/blob/master/lib/omniauth/strategies/openid_connect.rb#L128 public_key method needs to change config.public_keys.first to just config.jwks?

You're totally right.

Ok! ill test it later today or tomorrow and let you know. Big thanks!

Seems to work fine. Could you make a new release?
omniauth-openid-connect does not seems to depend on json-jwt directly, only on openid_connect. So what do you think would be best:
Add an explicit depend on new version of json-jwt for omniauth-openid-connect
Or
Update json-jwt version for openid_connect and then update openid_connect version for omniauth-openid-connect?

OK, I've just released json-jwt v1.2.1 with the above commit.
I've also released openid_connect v0.9.0 with gem dependency updates (not only json-jwt but also other my gems used in openid_connect gem https://github.com/nov/openid_connect/commit/14d9d5dff7e9dce43600597d1e5b24ad321e8364)
So omniauth_openid_connect doesn't need to specify json-jwt version, just update minimum openid_connect version to v0.9.0.

Very nice. Thanks for all the help!


A script directory collections for the repo ?

Hey there, this is an amazing project and am a big fan of it already !
Concerning this issue, it's not really a feature request, i was just wondering if it could not be a good idea to add to the repo, a scripts directory where everyone can share some nice custom script in it !
i have some "fun" scripts on my dotfiles for git stuffs, such as browsing for commits from a branch.
Usualy, this help me see what have been done on a branch from a repo !
And I mixed it with a custom branch of this repo.
In my ~/.config/gh-dash/config.yml :
keybindings:
  issues: []
  prs:
    - key: d
      command: >
        cd {{.RepoPath}} &&
        git checkout {{.HeadRefName}} &&
        git changes # which is a git alias

git changes calls these bash scripts functions :
#!/bin/bash

# for all git + fzf commands
GIT_FZF_DEFAULT_OPTS="
	$FZF_DEFAULT_OPTS
	--ansi
	--reverse
	--height=100%
	--bind shift-down:preview-down
	--bind shift-up:preview-up
	--bind pgdn:preview-page-down
	--bind pgup:preview-page-up
	--bind q:abort
	$GIT_FZF_DEFAULT_OPTS
"

git-fuzzy-log ()
{
	PREVIEW_COMMAND='f() {
		set -- $(echo -- "$@" | grep -o "[a-f0-9]\{7\}")
		[ $# -eq 0 ] || (
			git show --no-patch --color=always $1
			echo
			git show --stat --format="" --color=always $1 |
			while read line; do
				tput dim
				echo " $line" | sed "s/\x1B\[m/\x1B\[2m/g"
				tput sgr0
			done |
			tac | sed "1 a \ " | tac
		)
	}; f {}'

	ENTER_COMMAND='(grep -o "[a-f0-9]\{7\}" | head -1 |
		xargs -I % bash -ic "git-fuzzy-diff %^1 %") <<- "FZF-EOF"
		{}
		FZF-EOF'

	git log --graph --color=always --format="%C(auto)%h %s%d " | \
		fzf ${GIT_FZF_DEFAULT_OPTS} --no-sort --tiebreak=index \
		--preview "${PREVIEW_COMMAND}" --preview-window=top:15 \
		--bind "enter:execute:${ENTER_COMMAND}"
}

git-changes ()
{
	PREVIEW_COMMAND='f() {
		set -- $(echo -- "$@" | grep -o "[a-f0-9]\{7\}")
		[ $# -eq 0 ] || (
			git show --no-patch --color=always $1
			echo
			git show --stat --format="" --color=always $1 |
			while read line; do
				tput dim
				echo " $line" | sed "s/\x1B\[ m/\x1B\[2m/g"
				tput sgr0
			done |
			tac | sed "1 a \ " | tac
		)
	}; f {}'

	ENTER_COMMAND='(grep -o "[a-f0-9]\{7\}" | head -1 |
		xargs -I % bash -ic "git-fuzzy-diff %^1 %") <<- "FZF-EOF"
		{}
		FZF-EOF'

    git log origin..HEAD --no-merges  --graph --color=always --format="%C(auto)%h %s%d " | \
		fzf ${GIT_FZF_DEFAULT_OPTS} --no-sort --tiebreak=index \
		--preview "${PREVIEW_COMMAND}" --preview-window=top:15 \
		--bind "enter:execute:${ENTER_COMMAND}"
}

And with that I can :

browse/search commits title from a branch .
browse/search files changed from that branch.
browse changes for those files.

DEMO

These are awesome scripts :) Thanks for sharing. Are you aware of any projects that include something similar like this scripts folder you're suggesting?
I'm wondering what's the best way to include those.
If it's a really popular behavior, it can be integrated straight into gh-dash, in Go rather than in bash.

Are you aware of any projects that include something similar like this scripts folder you're suggesting?

Mhh, actually no 😄 , I was just proposing it as a "thing" for the community to share some nice script that can do multiple kind of things.

in Go rather than in bash
Totally agree too, for this specific behaviour of listing commits from a branch on a repo, and see what's inside, I can take the issue I try something.

I could link to a list of popular scripts, like the ones in your dotfile

yeah, on this repo or another specific repo like gh-dash-scripts for the community to share some interesting key-bindings scripts for PRs and issues, I think it could be great.


Update docker-kubectl image in cluster-api-provider-aws-app

Coming from https://github.com/giantswarm/roadmap/issues/1808
Update docker-kubectl image in cluster-api-provider-aws-app to the latest v1.24.x (same as vintage AWS MCs, one minor newer than CAPA MCs)

Should we update to the latest or latest of 1.24? @nprokopic @alex-dabija

https://github.com/giantswarm/cluster-api-provider-aws-app/pull/150

From here https://github.com/giantswarm/roadmap/issues/1808

Update docker-kubectl image in cluster-api-provider-aws-app to the latest v1.24.x (same as vintage AWS MCs, one minor newer than CAPA MCs)

That would be v1.24.9 I believe

Checked now upstream release notes, the latest v1.24.x is v1.24.10.

The logic to select which version to deploy is that the difference between kubectl and Kubernetes versions (on MC where kubectl is used to apply CRDs) should not be greater than 1.
On vintage AWS we are using v1.24.x and on CAPA we are still on v1.23.x (checked golem and grizzly), so the latest kubectl version that respects max version skew on both is v1.24.x.

@nprokopic Thank you very much for the clarification. But I am a bit confused about docker-kubectl. But, I am little bit confused, I tought that docker-kubectl is a repo on our end. That's why I used 1.24.4.

But I am a bit confused about docker-kubectl. But, I am little bit confused, I tought that docker-kubectl is a repo on our end. That's why I used 1.24.4.

I had same confusion few days ago for cluster-api-app :smile:
@fiunchinho updated cluster-api-app to use giantswarm/kubectl (built by regtagger, we always retag every upstream version) instead of giantswarm/docker-kubectl (coming from our repo, not always up-to-date) https://github.com/giantswarm/cluster-api-app/pull/82/files, I guess we can do the same here for cluster-api-provider-aws-app.
(left this same comment in the PR)

https://github.com/giantswarm/cluster-api-provider-aws-app/pull/150


APP-312: Storm data analytics demo server build failed: avro artifact not found

Can one of the admins verify this patch?

@kaa-leeroy test this please


Include total number of structures in API response

Based on a user feedback session with a beta user.
User requested:
"in the API response include a total number of structure that the model has found."
Notes:

Total number of structures is just the sum of count of structures in each class. But this was not clear to the user
An easy thing to include in the JSON response under "data_summary", and will provide a sanity check for users. Seems like a good idea.

The total number of structures is located in the data summary section of the data dictionary
 "data_summary": {
        "classA_pooled_prob_mean": 0.08,
        "classA_pooled_prob_std_dev": 0.58,
        "classA_total_count": 12,
        "classB_pooled_prob_mean": 0.65,
        "classB_pooled_prob_std_dev": 0.09,
        "classB_total_count": 24

A user provided feedback by Email and referenced this issue:

How many total structures are in that area (i.e. to calculate the proportion of Class A and/or Class B structures of the total)?

The total number of structures is located in the data summary section of the data dictionary

No, we are talking about the total number of structures in all classes.

Total structure count added to data dictionary
 "data_summary": {
        "classA_pooled_prob_mean": 0.08,
        "classA_pooled_prob_std_dev": 0.58,
        "classA_total_count": 12,
        "classB_pooled_prob_mean": 0.65,
        "classB_pooled_prob_std_dev": 0.09,
        "classB_total_count": 24
        "total_structure_count": 36


RGB Pins occupied by PSRAM

Describe the bug
My board uses pins 16, 4, 17 for builtin rgb led, but everytime i try to make a custom board for it, it keeps telling me that the pins are used by psram.
To Reproduce
Create a new board.json with this code in it:
"led": {
        "rgb": [
            {"pin": "LED0"},
            {"pin": "LED1"},
            {"pin": "LED2"}
        ]
    },

and run npm run build
Expected behavior
The system should build succesfully and I can flash the firmware to my board.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
The board is an ESP32-2432S028R.
This is the output of npm run build:
><EMAIL_ADDRESS>build
> npm run build:devicescript

><EMAIL_ADDRESS>build:devicescript
> devicescript build src/main.ts

using devs: v2.15.23, runtime: v2.15.23, node: v18.7.0 from C:\Users\hyper\Desktop\DeviceScript\testno2\testno2\node_modules\@devicescript\cli\built
C:\Users\hyper\Desktop\DeviceScript\testno2\testno2\boards\esp32_2432s028r.board.json(1): LED0=17 has 'psram' function
LED2=16 has 'psram' function

board.json file:
{
    "$schema": "https://raw.githubusercontent.com/microsoft/devicescript-esp32/main/boards/esp32deviceconfig.schema.json",
    "devName": "ESP32-2432S028R",
    "productId": "0x3462c836",
    "$description": "Bare ESP32 without any default functions for pins.",
    "archId": "esp32",
    "url": "https://www.espressif.com/en/products/socs/esp32",
    "pins": {
        "P35": 35,
        "P22": 22,
        "P21": 21,
        "P27": 27,
        "LED0": 17,
        "LED1": 4,
        "LED2": 16
    },
    "led": {
        "rgb": [
            {"pin": "LED0"},
            {"pin": "LED1"},
            {"pin": "LED2"}
        ]
    },
    "sd": {
        "pinCS": 5,
        "pinMISO": 19,
        "pinMOSI": 23,
        "pinSCK": 18
    }
}

@mmoskal any idea?

Right, 16 and 17 are used by PSRAM if PSRAM is installed. I assume your board doesn't have it. I guess we should have an option in the .board.json to disable PSRAM checking, however the board is unlikely to work very well anyways due to lack of a native USB interface.
From https://microsoft.github.io/devicescript/devices#implementation-status
The ESP32-C3 boards are best supported. The regular ESP32 (without -C3 or -S2) currently have issues with the USB connection (as it's handled by external chip). The ESP32-S2 has limited memory which makes it difficult to use TLS. The ESP32-S3 is very recent and largely untested.
The RP2040 should generally work, but TLS is not supported on Pico-W.


[Question] comment section

In an article, is its "comment section" referring to where it asks "Is this page helpful?"

Hello @rootsmusic - this section is the one where you can open GitHub issues as feedback.


Very long loading time since 2.0.4

Hi
Since 2.0.4 version, I have very long loading time in customizer 30+ seconds (both - load or update settings) Customizer settings panel is loading fine, but the site (theme) have this problem.
Using kirki as plugin and version 2.0.3 works fine.
Do you have anybody same problem?

Hi
Made some tests and loks like Kirki load the css styles many times... In the attachement is demo-theme from kirki. All styles are loaded more than 15x

Yep, can confirm this problem on backend and frontend as well. With Kirki 2.0.3 loading times are around 2secs with Kirki 2.0.4 they increasing massively to 20secs and up.

@x-bull @doitmax Can you guys please try using the develop branch and let me know if that fixes your issue?

The problem is fixed and the loading speed is better than in 2.0.3 :-). Hope you release this update as soon as possible
Good job

Excellent!
Yes, I'm just going through the tickets and looking for anything major.
I'll try to release this today. If not today then tomorrow :+1:
Closing this ticket.

@aristath checked it too and it is working now. No more delay when using Kirki :+1:


Getting 'cc1plus.exe: out of memory allocating 65536 bytes' in MinGW

I am trying to build using MinGW-w64 11.2.0 (and other recent versions) but sometimes getting this error in one of bindings C++ source file:
cc1plus.exe: out of memory allocating 65536 bytes
Already tried compile with parameters like: -ftrack-macro-expansion=0, -Wa,-mbig-obj, -Os, -O1, -O2.
Also tried to placing groups of bindings in multiple different C++ source files.
Nothing works.

How are you making the binding?
Try using the following method if you are currently binding everything for a single usertype at once in the usertype constructor.
auto bindings = sol::new_usertype<MyThing>("MyThing");

// Add bindings to the usertype afterwards one at a time
bindings["MyMethod1"] = &MyThing::MyMethod1;
bindings["MyMethod2"] = &MyThing::MyMethod2;
bindings["MyMethod3"] = &MyThing::MyMethod3;

I used to use all in single new_usertype call.
I will do more tests, but it seems to works now!
Thanks!


DOC: Remove duplicate "type" in alias documentation

Remove duplicate "type" in alias documentation.
PR Checklist

[X] No API changes were made (or the changes have been approved)
[X] No major design changes were made (or the changes have been approved)

Both ways may be correct; depends on how we read them? Would appreciate the input of some very strict voice on the technicalities or terms.
Maybe using "type type alias" was a sort of divergence of e.g. "ImageType type alias", appearances like the latter being much more frequent, over 400 hits.

I think this was a global substitution of "type typedef" to "type type alias" .  Your changes are good.


tests: mockito dependency updates due to breaking API changes

Description
mockito dependency breaks the all_plugins/tests check for github actions. It made a breaking change to the API which this PR resolves.
This PR affects auth, core, messaging & firestore packages.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Closing this PR in favour of the PR that branches of the NNBD Storage PR here: https://github.com/FirebaseExtended/flutterfire/pull/5013


time-slider & x-axis should be aligned and, timeline label overlap xis labels, nice

http://bit.ly/1aIDllF

See the mocks in this doc

aligning done, overlapping — not yet

overlap now done as well
http://bit.ly/1MmFYXA


Add zod.select

This adds zod.select as suggested in #2318.

😔

My current plan is to overload z.literal() with this functionality. It's a breaking change so it will land in Zod 4. But thanks for the PR!


@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/seed-isort-config-feedstock#3.


python3Packages.slackclient: 2.5.0 -> 2.9.3, python3Packages.slack-sdk: init at 3.3.0

Motivation for this change

Update slackclient to latest upstream release 2.9.3. This is the last release of slackclient.
The client was renamed to slack_sdk.
Update of errbot to 6.1.7 (https://github.com/errbotio/errbot/blob/master/CHANGES.rst#v617-2020-12-18) to fix the build issue

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 111964 run on x86_64-linux 1

1 package failed to build:

errbot

3 packages built:

python37Packages.slackclient
python38Packages.slackclient
python39Packages.slackclient

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111964 run on x86_64-linux 1

1 package failed to build and are new build failure:

errbot: log was empty

3 packages built:

python37Packages.slackclient
python38Packages.slackclient
python39Packages.slackclient

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111964 run on x86_64-darwin 1

3 packages built:

python37Packages.slackclient
python38Packages.slackclient
python39Packages.slackclient

Result of nixpkgs-review pr 111964 run on x86_64-linux 1

1 package marked as broken and skipped:

python39Packages.slack-sdk

1 package failed to build:

errbot

5 packages built:

python37Packages.slack-sdk
python37Packages.slackclient
python38Packages.slack-sdk
python38Packages.slackclient
python39Packages.slackclient

Result of nixpkgs-review pr 111964 run on x86_64-linux 1

1 package marked as broken and skipped:

python39Packages.slack-sdk

6 packages built:

errbot
python37Packages.slack-sdk
python37Packages.slackclient
python38Packages.slack-sdk
python38Packages.slackclient
python39Packages.slackclient

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111964 run on x86_64-linux 1

1 package marked as broken and skipped:

python39Packages.slack-sdk

6 packages built:

errbot
python37Packages.slack-sdk
python37Packages.slackclient
python38Packages.slack-sdk
python38Packages.slackclient
python39Packages.slackclient

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111964 run on x86_64-darwin 1

1 package marked as broken and skipped:

python39Packages.slack-sdk

5 packages failed to build and are new build failures:

python37Packages.slack-sdk: log https://termbin.com/fgvn
python37Packages.slackclient: log https://termbin.com/0qir
python38Packages.slack-sdk: log https://termbin.com/whda
python38Packages.slackclient: log https://termbin.com/n2rd
python39Packages.slackclient: log https://termbin.com/gdlp

Broken on Python 3.9 due to uvloop.
error: Package ‘python3.9-uvloop-0.14.0’ in /home/hexa/git/nixos/master/pkgs/development/python-modules/uvloop/default.nix:71 is marked as broken, refusing to evaluate.

Broken on Python 3.9 due to uvloop.

There is no ETA for Python 3.9 support of uvloop (https://github.com/MagicStack/uvloop/issues/365).

Result of nixpkgs-review pr 111964 run on x86_64-linux 1

7 packages built:

errbot
python37Packages.slack-sdk
python37Packages.slackclient
python38Packages.slack-sdk
python38Packages.slackclient
python39Packages.slack-sdk
python39Packages.slackclient

@fabaff is slackclient still being maintained? If not, we probably should introduce slack-sdk and remove slackclient.

slackclient is still maintained according to an upstream statement and needed by Home Assistant and Errbot for now. I hope that
Home Assistant and Errbot will migrate to slack-sdk in the near future.


Second level permutations

Built on top of second level api correction. still on development.

Maybe squash some commits. The history looks very long and verbose.

@bthirion The PR is ready for review. There are some apparently unrelated tests failing. They seem to be a numpy issue in Python 3.5.

This PR seems to be inactive now. I will close it tomorrow, since we are 6hrs ahead of US East Coast.
If any objections, let me know now.

@kchawla-pi Effectively I have not found time to work on this at the moment. I am okay closing this.

Thanks Martin. We can reopen this in future.


Generic Neural Net Example

→ Submit changes to the relevant branch 🌲
development
→ Description 📝

submitting a new feature 🆕

→ Screenshots 🖼

→ Relevant documentation 🌴
Added a simple Generic Neural Network example.
In the example, you can -

train a model
predict
save the model
load the model from local files
load the model by selecting .json and .bin files from file uploader

@joeyklee thank you for all of this amazing work! Just a quick note that I will be working on this for a few hours offline on a train ride today. I'll open a pull request here and in ml5-library if necessary. If there is anything you specifically want me to look at let me know! Otherwise I'll likely be working  on porting my "color classifier" example as well as creating a wekinator style "musical note" classifier example based on mouse position.


Update wording on Permissions modal

Permission string update (https://github.com/thundernest/addons-server/pull/77) now expose a Permissions modal. Which is great! However the wording refers to Firefox, which isn't correct. Easy fix.

Should be in src/olympia/addons/templates/addons/impala/details.html

Changing this string will break the entire paragraph in l10n. You can maybe search/replace Firefox/Thunderbird across all the languages as long as nobody's done something weird like translate "Firefox".

Hmm, that would probably work. I'm guessing we don't have an upstream translation project for ATN?

Hmm, that would probably work. I'm guessing we don't have an upstream translation project for ATN?

There's no translation project for ATN in Pontoon, no. There will need to be one for the new front-end.

Cool, just checking to see if I had to upstream the adjustments. 😄


Seed script creates future overdue reservations

The seed script generated this reservation:
#<Reservation id: 6, reserver_id: 9, checkout_handler_id: 25, checkin_handler_id: nil,
start_date: "2015-06-27", due_date: "2015-06-28", checked_out: "2015-06-27 04:00:00",
checked_in: nil, created_at: "2015-05-25 15:53:17", updated_at: "2015-05-25 15:53:17",
equipment_model_id: 2, equipment_item_id: 9,
notes: "Tofu PBR blog photo booth raw denim iPhone hoodie ...",
notes_unsent: true, times_renewed: nil, status: 3, overdue: true, flags: 1>

Somehow, this reservation is in the future, but has been checked out and flagged as overdue. This may or may not be related to #1229

This isn't really a bug as much as a consequence of the fact that the seed script sets the overdue flag independently of the start date (see here). Nonetheless, it could probably be fixed / refactored eventually.

Closed via #1567. @esoterik don't forget to link to this one in the CHANGLEOG as well.


fields for weights that should be added and how they should be sent to simbrief?

I don't know how simbrief api work I found some links about Aircraft integration.
Integration - AC Data?
{"mtow":171.961,"mlw":145.505,"mzfw":137.789,"oew":96.518}
Possible aircraft/layout options
The SimBrief API

mtow, mlw, mzfw would be probably same for a type (unless you want to reduce the certified weights) but having oew (operational empty weight) or dow (dry operating weight) would be nice ... By having these values we can produce more realistic flight plans with simbrief integration (at least the weights in the ofp will match the aircraft we use in the sim when configured correctly of course)

Anyway, MTOW is necessary because airports charge taxes with this parameter.

Also most of the time countries charge airspace usage fees according to mtow. So in feature versions maybe we can define Airport and/or ATC Charge expenses in phpvms by weight (as rw) who knows ;)

Also most of the time countries charge airspace usage fees according to mtow. So in feature versions maybe we can define Airport and/or ATC Charge expenses in phpvms by weight (as rw) who knows ;)

That would be ideal, tax per airport based in mtow/parking lot time/passengers... etc


Improve website design/look

Description
I would like to work on improving the website look/design. The current site can be made more appealing. I have some ideas in mind currently.
Screenshots
No response
Additional information
No response

@reveurguy you can start with a design if you want but dont code it till we finalize maybe you can go for figma and if approved I am up for redesign

@AvineshTripathi I'll make some changes by code only and submit a PR. Then we can discuss the changes for further work. This way suites me more than Figma.

I would also love to contribute in the website design

Hi @AvineshTripathi , I apologise for the long delay. Due to my university exams, I completely forgot about this involvement. However, I am now in the process of completing my exams, and by mid-June, I will be able to actively engage and provide my suggestions.
I would also like to discuss the possibility of developing a new website from scratch using modern technology such as Next.js. This approach seems highly viable and promising. By starting from scratch, we can leverage the benefits of Next.js to optimize the website's performance and speed. Additionally, incorporating UI and design changes will be much easier with a fresh foundation.
Basic information about the Next.js framework will be required, but since it is build upon React, contributors with knowledge of React will find it easy to use. To facilitate the onboarding process for new contributors, we will create comprehensive documentation that provides detailed guidance on the codebase and the Next.js framework.
While the new website would be in development, the current website would stay in usage.
Please let me know your thoughts on this approach and if you have any specific questions or concerns.
Let's discuss upon this further.

Hi @AvineshTripathi , I apologise for the long delay. Due to my university exams, I completely forgot about this involvement. However, I am now in the process of completing my exams, and by mid-June, I will be able to actively engage and provide my suggestions.
I would also like to discuss the possibility of developing a new website from scratch using modern technology such as Next.js. This approach seems highly viable and promising. By starting from scratch, we can leverage the benefits of Next.js to optimize the website's performance and speed. Additionally, incorporating UI and design changes will be much easier with a fresh foundation. Basic information about the Next.js framework will be required, but since it is build upon React, contributors with knowledge of React will find it easy to use. To facilitate the onboarding process for new contributors, we will create comprehensive documentation that provides detailed guidance on the codebase and the Next.js framework.
While the new website would be in development, the current website would stay in usage.
Please let me know your thoughts on this approach and if you have any specific questions or concerns. Let's discuss upon this further.

Hey @reveurguy , i'd suggest the same thing that @AvineshTripathi pointed out above! It would be much better if you could design your idea using Figma, because then we'll have something to show to Saiyam!
Once the design is approved, you may start working on that!
From the Kubesimplify community, we have @sanyamjain04 who is great at designing! maybe you two can collaborate


Simple Time Measurements

Description
Changes proposed in this pull request:

Simple log message for making it easier to identify slow test parts.

Related issue(s)

/test pre-kyma-environment-broker

/test pre-kyma-environment-broker

/test pre-kyma-environment-broker

/test pre-kyma-environment-broker


Expected behaviour when cookies are accepted or declined?

When using cookieconsent, what is the expected behaviour when a user accepts or declines? Obviously the popup notice itself gets hidden, but what happens in terms of the actual cookies themselves? Looking in the inspector, no cookies seem to be deleted?
I'm installing on a Wordpress site and there are a few essential cookies required to log the username etc, and wondering if the script should be clearing all cookies if permission is denied. Does anything happen 'out of the box' or do callbacks need to be set to disable/enable cookies?
The code on this page (https://cookieconsent.insites.com/documentation/disabling-cookies/) seems to suggest it is a manual process, but not sure entirely what the script is offering if it doesn't deal with this automatically?
Thanks

This plugin saves only a cookie named "cookieconsent_status" and it is your task to handle this value (allow, dismiss or deny) in your source code or with the callbacks. Depends on your compliance.
Example

@InsanityMeetsHH got it bang on 👍 There is some more info on this page. If you are struggling to understand the page, just re-open this issue and I'll be happy to help you out some more.


(Willing to PR) Expose more about Timeline, such as allowing to configure timestamp, just like what is exposed to Flutter C++ code

I am willing to PR for this :)
In flutter/engine we can report timeline events like:
    fml::tracing::TraceEventAsyncComplete(
        "flutter",                    // category
        "SceneDisplayLag",            // name
        raster_finish_time,           // begin_time
        latest_frame_target_time,     // end_time
        ...
    );

Or other sync or async or flow things. Most interestingly, we can report the time we choose, instead of always being forced as now.
This is very helpful feature. Hope I do not need to prove its helpfulness, because it is there and flutter/engine has already proved it by using it extensively :)

Potential implementation
I looked at how flutter/engine finally calls Dart timeline code. It uses Dart_TimelineEvent indeed. On the other hand, a Dart code using Timeline class will finally utilize DartTimelineEventHelpers::ReportTaskEvent.
Comparing their implementation, the (rough) solution is quite trivial:
void DartTimelineEventHelpers::ReportTaskEvent(TimelineEvent* event,
                                               int64_t id,
                                               intptr_t type,
                                               int64_t timestamp, // <---- ADDED, suppose we define negative as use-default
                                               char* name,
                                               char* args) {
  const int64_t start = timestamp < 0 ? OS::GetCurrentMonotonicMicrosForTimeline() : timestamp; // <----- MODIFIED, old code is unconditionally call `OS::GetCurrentMonotonicMicrosForTimeline()`
  ... same as before ...

There are several different underlying recorders, some of which do not take a timestamp as input and assume the event happens at the current time, such as Android's Systrace and Mac's Signpost. The exposure of a timestamp parameter is leftover plumbing from when the only recorder was Mojo, not a capability of the trace system.


Use cache default

Motivation and context

Change the default way of a task creating
How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[x] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

Coverage remained the same at 66.695% when pulling afe7abc2a42951845220affd30d1ab87c12c4d8c on mk/use_cache_default into 7543f5ef6f9eee9e26795b48ad8a8047093e6737 on develop.


DO NOT MERGE YET:  remove hardcoded drop of openshift plugin; config.xml fixes; readme u…

…pdates; update plugin version
@bparees @mfojtik these are various changes resulting from my working through the master/slave flow
Note: the ongoing dialogue with Dan Mace regarding deployment trigger behavior could still affect the build steps in the 3 sample jobs, based on what happens with our use of the automatic flag, but i wanted to get a working version that still has a reasonable ci/cd workflow ready.
I've also have had to bump the plugin version based on the fixes (as well as the introduction of the env var changes).  Once it is available on the jenkins update center we can move forward with merging once the review is complete.

The exchange with @ironcladlou reached a conclusion.  I confirmed with @bparees my interpretation that for the short term at least, we'll leverage automatic=true for the deployment config's related to our master/slave sample.
A copy/paste of the relevant piece from @ironcladlou :
So, I sublty misread the original report from Gabe and ALSO managed to
miss a subtle detail in the code, so let me try explaining this again.
The first (initial) deployment will be generated by resolving images
against any image triggers present regardless of the automatic flag,
by design. The deploymentConfig users create with image triggers don't
usually initially contain valid pullspecs. We resolve them once to get
the deployment started with the latest tag values defined in the
triggers. From that point forward, new image values for the tags will
only be resolved/updated if:

The referenced ImageStream tags change AND automatic=true, or
A configChange trigger is present and something in the
deploymentConfig template changes [1]

My note about the behavior of oc deploy --latest is still accurate:
images won't be resolved/updated in that case.
[1] This is what I think could be considered a bug; if there's a
template change that would normally trigger a new deployment, but the
image trigger is automatic=false, it might not make sense for images
to be resolved again.

updates pushed for the various typos and rewording form @bparees 's comment.  I'll rename the json files pending the answer to my request for clarification.

LGTM

@gabemontero @bparees still valid PR? Should have at least less horrifying title :-)

@mfojtik @bparees the files affected are not present in @mfojtik 's latest pull https://github.com/openshift/jenkins/pull/77 in the slave space .... agreed, this pull is no longer relevant.
Closing out.


path.resolve must be strings

Uncaught (in promise) TypeError: Arguments to path.resolve must be strings

@eldyvoon fixing this in the next update. thanks!

Fixed in https://github.com/gamell/fetch-base64/pull/5


build: delete source maps from prod build after Sentry upload

Allure Report
allure-report-publisher generated test report!

processReports: ✅ test report for c4743f5d

passed
failed
skipped
flaky
total
result

Total
32
0
4
0
36
✅


Add .archived and .unarchived scopes by default.

As the title says. Addresses #7.
This adds:

A base dependency: ActiveRecord
A development dependency: SQLite3
The .archived and .unarchived scopes, with tests to guarantee.

:dancers:

Deployed as 1.4.0


2128 course level migration

Context
Course subjects > subjects & level
Changes proposed in this pull request
Add new level attribute
Guidance to review
🚢
We already have a level attribute on course so the specs don't need updating.
Checklist

[x] Make sure all information from the Trello card is in here
[x] Attach to Trello card
[x] Rebased master
[x] Cleaned commit history
[x] Tested by running locally

 Add level field to course table

Rebased and fixed minor issues


Add ESM bundling with Rollup

Hey so as I said ESM is the way to go with Node.js modules nowadays and I finally got around copy-pasting my own Rollup bundling to this project. If there was some example setup I could have tested linking the built module locally but if you have some project that uses this, just yarn link in this repo and then yarn link prosemirror-docx in the other one and you should be able to test if the bundling works as it should.
I also added the --frozen-lockfile to the workflow. I've had problems with caching my yarn install properly but I'm not sure does this help. It's though more appropriate I think.

This is fantastic -- apparently lost the notification, sorry for the delay in getting back to you.
I will take a look in the next few days and hopefully get it out. Not my area of expertise at all. :)
Appreciate the help!!

This is fantastic -- apparently lost the notification, sorry for the delay in getting back to you.
I will take a look in the next few days and hopefully get it out. Not my area of expertise at all. :)
Appreciate the help!!

No problem at all, this bundling is in general quite arcane business and it does improve life quality if you don't need to get deep into it 😅.
Rollup works well with simple setups, the biggest problems I've had with it were due to using obscure combinations of old libraries, Svelte and pnpm. The ordering of the plugins then become quite essential. I've heard esbuild is the fastest bundler (unless Rome has somehow beaten it) but they sacrifice conveniency to some extent.


Chest build procedures need to be updated for newest Adafruit Datashield.

The latest Adafruit Datashield https://learn.adafruit.com/adafruit-data-logger-shield/shield-overview (see Prototyping Area section) has built-in voltage and gnd rails in the prototyping area that are reversed from the rail configuration used in the suit build procedures.  GND rail is toward the center of the board.  This means the wiring in that step of the chest build procedures needs to be reversed otherwise it creates a short and the SD CardInfo test will fail.  All other steps later in the chest build procedures that connect to the rails need to have red/black flipped.

This is how it needs to be wired to work correctly.


Draft: fix Time Shift join key

SUMMARY

A draft about Time Shift joined key issue, make it simple and let our life work and life easy.
Original PR at https://github.com/apache/superset/pull/24176
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Will cherry-pick this one, close it in community.

@zhaoyongjie is this fix needed upstream? Do you have a test case that shows the problem and is fixed by this?


Upgrade to at least Solidity 0.8.4

We are currently at ^0.8.0. Figure out if we should anchor it to a specific version.
Ref: https://github.com/code-423n4/2021-08-gravitybridge-findings/issues/45

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Yep, of course. Usually it's recommended to use a specific Solidity compiler version

Should we change the pragma to be ^0.8.4?

No, it should be 0.8.4. It still could not lock to a specific compiler version by using ^

Did we already address this @Hsiang-xxs? I feel like I saw this version used in a PR recently.

Yep, already fixed. Let's close this issue :)


Issue importing package on Windows

Incorrect environment variable retrieval.  Look at system type to identify whether to retrieve HOME vs HOMEPATH varaibles

Fixed in Version 0.1.3.dev3 (published), will be in next official release


fix(catalog): added fixed colors to the palette

If you ever need to use fixed colors in some parts of the catalog, this PR adds them to the palette.
It also sorts and prettify the keys of the materialColors object.

I will never get the titles right..

I will never get the titles right..

haha nw, sorry 😅
The catalog isn't really a "feature" of @material/web, but it'd be nice to call it out. I wish there was a "chore" or "note"/"misc" section for the changelog.


JavaScript/TypeScript support

I would love to be able to use this for my JavaScript/Typescript projects. If I'm not mistaken, the VSCode version of this plugin does, so I was surprised to find that this version only supports Java.
Thanks!

Me too. It would be nice to have TypeScript support for WebStorm/IntelliJ too.

Just FYI, you might find CyclomaticComplexity (published by JetBrains themselves) of interest; the README.md currently states:

Supported languages are C#, VB, JavaScript, TypeScript and C++.


Collab error

Hi i'm using the collab link from this repo but i get this error when i run it
/content/animatediff
2023-08-21 13:47:11.130301: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
loaded temporal unet's pretrained weights from /content/animatediff/models/StableDiffusion/unet ...
missing keys: 560;
unexpected keys: 0;
Temporal Module Parameters: 417.1376 M
current seed:<PHONE_NUMBER>0782582783
sampling dark shot, epic realistic, portrait of halo, sunglasses, blue eyes, tartan scarf, white hair by atey ghailan, by greg rutkowski, by greg tocchini, by james gilleard, by joe fenton, by kaethe butcher, gradient yellow, black, brown and magenta color scheme, grunge aesthetic!!! graffiti tag wall background, art by greg rutkowski and artgerm, soft cinematic light, adobe lightroom, photolab, hdr, intricate, highly detailed, depth of field, faded, neutral colors, hdr, muted colors, hyperdetailed, artstation, cinematic, warm lights, dramatic light, intricate details, complex background, rutkowski, teal and orange ...
Token indices sequence length is longer than the specified maximum sequence length for this model (139 > 77). Running this sequence through the model will result in indexing errors
The following part of your input was truncated because CLIP can only handle sequences up to 77 tokens: ['artgerm, soft cinematic light, adobe lightroom, photolab, hdr, intricate, highly detailed, depth of field, faded, neutral colors, hdr, muted colors, hyperdetailed, artstation, cinematic, warm lights, dramatic light, intricate details, complex background, rutkowski, teal and orange']
100% 25/25 [04:02<00:00,  9.68s/it]
100% 16/16 [00:06<00:00,  2.64it/s]
Traceback (most recent call last):
File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/content/animatediff/scripts/animate.py", line 159, in
main(args)
File "/content/animatediff/scripts/animate.py", line 137, in main
save_videos_grid(sample, f"{savedir}/sample/{sample_idx}-{prompt}.gif")
File "/content/animatediff/animatediff/utils/util.py", line 25, in save_videos_grid
imageio.mimsave(path, outputs, fps=fps)
File "/usr/local/lib/python3.10/dist-packages/imageio/v2.py", line 495, in mimwrite
return file.write(ims, is_batch=True, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/imageio/plugins/pillow.py", line 383, in write
raise TypeError(
TypeError: The keyword fps is no longer supported. Use duration(in ms) instead, e.g. fps=50 == duration=20 (1000 * 1/50).

Did you sort out?? If not here:
replace 'fps=8' with 'duration=125'  //in line: 13
and
'duration=duration' instead of 'fps=fps' //in line: 25
u can find both of these in '/content/animatediff/animatediff/utils/util.py'
do  this and it will work although it's not official so wait for the author fix

Thanks, it worked!