error  install while installing on windows

I using anaconda3 with python 3.5.
(dl) C:\Users\wit\universe>pip install -e .
Obtaining file:///C:/Users/wit/universe
Collecting autobahn (from universe==0.20.2)
  Using cached autobahn-0.17.0-py2.py3-none-any.whl
Collecting docker-py==1.10.3 (from universe==0.20.2)
  Using cached docker_py-1.10.3-py2.py3-none-any.whl
Collecting fastzbarlight>=0.0.13 (from universe==0.20.2)
  Using cached fastzbarlight-0.0.13.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "c:\users\wit\appdata\local\temp\pip-build-kt2ovr\fastzbarlight\setup.py", line 49, in <module>
        proc = subprocess.Popen(['ld', '-liconv'], stderr=subprocess.PIPE)
      File "c:\users\wit\anaconda3\envs\dl\lib\subprocess.py", line 711, in __init__
        errread, errwrite)
      File "c:\users\wit\anaconda3\envs\dl\lib\subprocess.py", line 959, in _execute_child
        startupinfo)
    WindowsError: [Error 2] The system cannot find the file specified

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in c:\users\wit\appdata\local\temp\pip-build-kt2ovr\fastzbarlight\

I already try install fastzbarlight manually but got another error.
(tf) C:\Users\wit\Downloads\dist\fastzbarlight-0.0.4>python setup.py install
running install
running bdist_egg
running egg_info
writing src\fastzbarlight.egg-info\PKG-INFO
writing dependency_links to src\fastzbarlight.egg-info\dependency_links.txt
writing top-level names to src\fastzbarlight.egg-info\top_level.txt
writing requirements to src\fastzbarlight.egg-info\requires.txt
reading manifest file 'src\fastzbarlight.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no directories found matching 'src\zbarlight'
no previously-included directories found matching 'docs'
no previously-included directories found matching 'tests'
warning: no previously-included files matching '.py[cod]' found anywhere in distribution
warning: no previously-included files matching '__pycache__' found anywhere in distribution
warning: no previously-included files matching '.so' found anywhere in distribution
warning: no previously-included files found matching 'Makefile'
warning: no previously-included files found matching 'requirements-dev.txt'
warning: no previously-included files found matching 'tox.ini'
writing manifest file 'src\fastzbarlight.egg-info\SOURCES.txt'
installing library code to build\bdist.win-amd64\egg
running install_lib
running build_py
running build_ext
building 'fastzbarlight._zbarlight' extension
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\x86_amd64\cl.exe /c /nologo /Ox /W3 /GL /DNDEBUG /MD -Isrc/fastzbarlight/vendor/zbar-0.10/include -IC:\Users\wit\Anaconda3\envs\tf\include -IC:\Users\wit\Anaconda3\envs\tf\include "-IC:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.10240.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\include\um" "-IC:\Program Files (x86)\Windows Kits\8.1\include\shared" "-IC:\Program Files (x86)\Windows Kits\8.1\include\um" "-IC:\Program Files (x86)\Windows Kits\8.1\include\winrt" /Tcsrc/fastzbarlight/_zbarlight.c /Fobuild\temp.win-amd64-3.5\Release\src/fastzbarlight/_zbarlight.obj -std=c99 -fPIC
cl : Command line warning D9002 : ignoring unknown option '-std=c99'
cl : Command line warning D9002 : ignoring unknown option '-fPIC'
_zbarlight.c
src/fastzbarlight/_zbarlight.c(71): warning C4244: 'function': conversion from 'Py_ssize_t' to 'unsigned long', possible loss of data
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\x86_amd64\link.exe /nologo /INCREMENTAL:NO /LTCG /DLL /MANIFEST:EMBED,ID=2 /MANIFESTUAC:NO /LIBPATH:C:\Users\wit\Anaconda3\envs\tf\libs /LIBPATH:C:\Users\wit\Anaconda3\envs\tf\PCbuild\amd64 "/LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\LIB\amd64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.10240.0\ucrt\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\lib\um\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\8.1\lib\winv6.3\um\x64" /EXPORT:PyInit__zbarlight build\temp.win-amd64-3.5\Release\src/fastzbarlight/_zbarlight.obj /OUT:build\lib.win-amd64-3.5\fastzbarlight\_zbarlight.cp35-win_amd64.pyd /IMPLIB:build\temp.win-amd64-3.5\Release\src/fastzbarlight\_zbarlight.cp35-win_amd64.lib src/fastzbarlight/vendor/zbar-0.10/zbar/.libs/libzbar.a
src/fastzbarlight/vendor/zbar-0.10/zbar/.libs/libzbar.a : warning LNK4003: invalid library format; library ignored
   Creating library build\temp.win-amd64-3.5\Release\src/fastzbarlight\_zbarlight.cp35-win_amd64.lib and object build\temp.win-amd64-3.5\Release\src/fastzbarlight\_zbarlight.cp35-win_amd64.exp
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_image_set_data
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_image_destroy
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_symbol_get_data
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_parse_config
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_image_create
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_image_scanner_set_config
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_image_scanner_create
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_image_scanner_destroy
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_symbol_next
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_version
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_image_set_format
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_symbol_get_data_length
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_image_set_size
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_image_first_symbol
_zbarlight.obj : error LNK2001: unresolved external symbol zbar_scan_image
build\lib.win-amd64-3.5\fastzbarlight\_zbarlight.cp35-win_amd64.pyd : fatal error LNK1120: 15 unresolved externals
error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\x86_amd64\\link.exe' failed with exit status 1120

We don't provide support for Windows currently. I think it should be possible to get there with a small amount of effort, if you or anyone else wants to do the work. The relevant package needing fixing is here: https://github.com/openai/zbarlight

I had taken a look on how to make it work on windows but I was so excited so I decided to install ubuntu and successfully install and get it running. I will go back to making it work on windows later.
Thank You

@wit543 Let me know if you do get the Windows version running.

@wit543 Let me know if you do get the Windows version running.

Did someone find a fix to the issues regarding installation of zbarlight on windows?

I've tried
conda install twisted ujson websocket
pip install txaio websocket

and commenting
# import fastzbarlight

because from what I've guessed, fastzbarlight is actually optional and is only needed for QR code purposes in QRCodeMetadataDecoder class.
But then I had error with importing go_vncdriver . I haven't really tried installing go_vncdriver, because pip said it needs Go installed. So, maybe the problem is not only with fastzbarlight.

@JhottMaster  I haven't figure it out how to install zbarlight on windows.

Did someone find a fix to the issues regarding installation of zbarlight on windows?

I had a crack at getting universe working on my work laptop (which is Windows 10) and I ran into similar challenges that @rilut highlighted. Both fastzbarlight and go-vncdriver are non-essential if you don't mind a performance decrease. I added some logic to bypass fastzbarlight imports on Windows systems, and go_vncdriver can be skipped by setting the UNIVERSE_VNCDRIVER environment variable to, say, 'libvnc'. Happy to put these into a PR.
However, even when you get universe working, the basic examples in the test cases fail because atari-py doesn't build in Windows (see https://github.com/openai/atari-py/issues/5).
Overall it feels like an uphill battle, not so much because of the cross-platform compatibility of the python code, but the native dependencies that require compilation from source, thus requiring build tools. Admittedly I'm not very experienced with python on Windows so these issues may all be surmountable, but based on this comment thread there doesn't seem to be much community appetite to make it happen.
I had a much better Windows experience just running the universe agent itself in a docker container, as per https://github.com/openai/universe/blob/master/doc/remotes.rst#agents-inside-docker, and after a couple of tweaks to the Dockerfile, the tests ran fine:
docker run --rm -it --network=host -v /var/run/docker.sock:/var/run/docker.sock universe pytest
and I was also able to shell in and run the basic duskdrive example, including connect my VNC client and watch.
How does everyone feel about this being the canonical way to run universe on Windows, at least for now? I could update the main readme to point Windows users to the "agents inside docker" approach

I think it's the right approach. Mainly because while it's fine to use a
single machine for development and testing, actually getting an agent to
learn to do something useful requires several parallel workers running for
hours or days. Most of my learning runs involve 5-10 machines, and some
need 50. Deploying these large parallel operations is much easier under
Linux. Agent containers built for Docker are easy(ish) to deploy on a
Kubernetes cluster.
On Wed, Mar 29, 2017 at 11:14 PM, James Weakley<EMAIL_ADDRESS>wrote:

I had a crack at getting universe working on my work laptop (which is
Windows 10) and I ran into similar challenges that @rilut
https://github.com/rilut highlighted. Both fastzbarlight and
go-vncdriver are non-essential if you don't mind a performance decrease. I
added some logic to bypass fastzbarlight imports on Windows systems, and
go_vncdriver can be skipped by setting the UNIVERSE_VNCDRIVER environment
variable to, say, 'libvnc'. Happy to put these into a PR.
However, even when you get universe working, the basic examples in the
test cases fail because atari-py doesn't build in Windows (see
openai/atari-py#5 https://github.com/openai/atari-py/issues/5).
Overall it feels like an uphill battle, not so much because of the
cross-platform compatibility of the python code, but the native
dependencies that require compilation from source, thus requiring build
tools. Admittedly I'm not very experienced with python on Windows so these
issues may all be surmountable, but based on this comment thread there
doesn't seem to be much community appetite to make it happen.
I had a much better Windows experience just running the universe agent
itself in a docker container, as per https://github.com/openai/
universe/blob/master/doc/remotes.rst#agents-inside-docker, and after a couple
of tweaks to the Dockerfile
https://github.com/jamesweakley/universe/commit/7f0f3fc9e2abe690d9e10d96189d121024a5cd76,
the tests ran fine:
docker run --rm -it --network=host -v /var/run/docker.sock:/var/run/docker.sock
universe pytest
and I was also able to shell in and run the basic duskdrive example,
including connect my VNC client and watch.
How does everyone feel about this being the canonical way to run universe
on Windows, at least for now? I could update the main readme to point
Windows users to the "agents inside docker" approach
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openai/universe/issues/15#issuecomment-290312519, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AANZdMNgdHZT4f00dhxcFLWy4xZ-mKgVks5rq0gsgaJpZM4LErkF
.

--
Trevor Blackwell<EMAIL_ADDRESS>  650 776 7870

is it possible to compile the packages on linux and then export them back to windows as wheel files?

That wouldn't be possible because for Universal/Pure Python wheels, you can't include compiled extensions. So these would be platform wheels.
See https://packaging.python.org/distributing/#wheels

Is this done without Docker yet? I just did a 2 hour workshop and presentation on the use of TensorFlow with OpenAI Gym strictly in Windows. I can take a crack at doing the same for Universe if it hasn't been done.

That would be awesome.
Sent from my iPhone

On May 26, 2017, at 2:03 PM, bfrasure<EMAIL_ADDRESS>wrote:
Is this done without Docker yet? I just did a 2 hour workshop and presentation on the use of TensorFlow with OpenAI Gym strictly in Windows. I can take a crack at doing the same for Universe if it hasn't been done.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Anyone come up with a solution? I'm struggling to install on Windows 10 as of right now...

After 2 days of playing around I was able to get fastzbarlight-0.0.14 installed in Windows. Quite a workaround, and I haven't tested yet...
Sorry for writing a book here :)
:Install:
Python 2.7.14(x86)
MinGW
MS VC++ for Python 2.7
zbar for Windows
:Download - Extract:
fastzbarlight-0.0.14.tar.gz
zbar-1.10 Source
Pre-Compiled zbar(amd64) DLLs
Pre-Compiled zbar(amd64) LIB
Install all the packages above.
Place the Pre-Compiled zbar(amd64) LIB+DLL into the lib folder under the zbar for Windows installation path. Typically: C:\Program Files (x86)\ZBar\lib
Adjust %PATH%: + C:\Python27\bin;C:\MinGW\Bin;
First(after installing all packages above), update setuptools to latest version (36.6.0): python -m pip install setuptools --upgrade
Extract zbar-0.10.tar.bz2 source and modify Setup.py.
Add To Line 3:
from distutils.sysconfig import get_config_vars
Adjust ext_modules section adding library_dirs and include_dirs. Use the Windows pre-compiled libs/includes in the folder that you installed zbar for windows into. Typically: C:\Program Files (x86)\ZBar\
ext_modules = [
        Extension('zbar', [
                'zbarmodule.c',
                'enum.c',
                'exception.c',
                'symbol.c',
                'symbolset.c',
                'symboliter.c',
                'image.c',
                'processor.c',
                'imagescanner.c',
                'decoder.c',
                'scanner.c',
                ],
            libraries = [ 'zbar' ],
            library_dirs=['C:\Program Files (x86)\ZBar\lib'],
            include_dirs=[get_config_vars('INCLUDEDIR'), get_config_vars('INCLUDEPY'),'C:\Program Files (x86)\ZBar\include'],
        ),
    ],

Launch a VC++ for Python 2.7 command prompt and build/install zbar:
<|=E:\APPZ\Python 2.7\zbar-0.10=|>python .\setup.py install
running install
running build
running build_ext
running install_lib
running install_egg_info
Writing C:\Python27\Lib\site-packages\zbar-0.10-py2.7.egg-info

<|=E:\APPZ\Python 2.7\zbar-0.10=|>

Install: Python 2.7.14(x64)
Install Python 2.7.14-amd64 OVER your existing installation @ C:\Python27. If the installer thinks it is already installed, do a "repair". We need to compile fastzbarlight as x64 package.
Extract fastzbarlight-0.0.14.tar.gz and modify Setup.py.
Adjust ext_modules section and replace extra_compile_args + extra_link_args parameters to match below.
ext_modules=[
        Extension(
            name=str('fastzbarlight._zbarlight'),
            sources=[str('src/fastzbarlight/_zbarlight.c')],
            extra_compile_args=['/TC'],
            include_dirs=[os.path.join(os.path.dirname(__file__), 'src/fastzbarlight/vendor/zbar-0.10/include')],
            optional=os.environ.get('READTHEDOCS', False),  # Do not build on Read the Docs
            extra_link_args=['C:\Program Files (x86)\ZBar\lib\libzbar64-0.lib'],
            libraries=libraries,
        ),
    ],

Launch a VC++ for Python 2.7 command prompt and build/install fastzbarlight-0.0.14:
running install
running bdist_egg
running egg_info
writing requirements to src\fastzbarlight.egg-info\requires.txt
writing src\fastzbarlight.egg-info\PKG-INFO
writing top-level names to src\fastzbarlight.egg-info\top_level.txt
writing dependency_links to src\fastzbarlight.egg-info\dependency_links.txt
reading manifest file 'src\fastzbarlight.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'src\fastzbarlight.egg-info\SOURCES.txt'
installing library code to build\bdist.win-amd64\egg
running install_lib
running build_py
running build_ext
creating build\bdist.win-amd64\egg
creating build\bdist.win-amd64\egg\fastzbarlight
copying build\lib.win-amd64-2.7\fastzbarlight\__init__.py -> build\bdist.win-amd64\egg\fastzbarlight
copying build\lib.win-amd64-2.7\fastzbarlight\package_data.txt -> build\bdist.win-amd64\egg\fastzbarlight
creating build\bdist.win-amd64\egg\fastzbarlight\vendor
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\Makefile -> build\bdist.win-amd64\egg\fastzbarlight\vendor
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10.tar.bz2.sha -> build\bdist.win-amd64\egg\fastzbarlight\vendor
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\COPYING -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\ChangeLog -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\HACKING -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\INSTALL -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\LICENSE -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\Makefile.am -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\Makefile.in -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\NEWS -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\README -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\README.windows -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\TODO -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\aclocal.m4 -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\config
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\config\compile -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\config
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\config\config.guess -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\config
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\config\config.rpath -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\config
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\config\config.sub -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\config
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\config\depcomp -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\config
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\config\install-sh -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\config
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\config\libtool.m4 -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\config
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\config\ltmain.sh -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\config
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\config\ltoptions.m4 -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\config
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\config\ltsugar.m4 -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\config
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\config\ltversion.m4 -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\config
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\config\lt~obsolete.m4 -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\config
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\config\missing -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\config
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\configure -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\configure.ac -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\doc\Makefile.am.inc -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc\api
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\doc\api\footer.html -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc\api
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\doc\doxygen.conf.in -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc\man
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\doc\man\man.stamp -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc\man
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\doc\man\zbarcam.1 -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc\man
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\doc\man\zbarimg.1 -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc\man
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\doc\manual.xml -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc\ref
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\doc\ref\commonoptions.xml -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc\ref
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\doc\ref\zbarcam.xml -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc\ref
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\doc\ref\zbarimg.xml -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc\ref
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\doc\reldate.xml -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\doc\style.xsl -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\doc\version.xml -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\doc
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\examples\barcode.png -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\examples\paginate.pl -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\examples\processor.pl -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\examples\processor.py -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\examples\read_one.pl -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\examples\read_one.py -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\examples\scan_image.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\examples\scan_image.cpp -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\examples\scan_image.pl -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\examples\scan_image.py -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\examples\scan_image.vcproj -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\examples\upcrpc.pl -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\examples\upcrpc.py -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\gtk
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\gtk\Makefile.am.inc -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\gtk
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\gtk\zbargtk.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\gtk
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\gtk\zbargtkprivate.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\gtk
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\gtk\zbarmarshal.list -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\gtk
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\Makefile.am.inc -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\config.h.in -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\zbar.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\zbar\Decoder.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\zbar\Exception.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\zbar\Image.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\zbar\ImageScanner.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\zbar\Processor.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\zbar\QZBar.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\zbar\QZBarImage.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\zbar\Scanner.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\zbar\Symbol.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\zbar\Video.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\zbar\Window.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\include\zbar\zbargtk.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\include\zbar
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\COPYING.LIB -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\Changes -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\MANIFEST -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\Makefile.PL -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\README -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\ZBar.pm -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\ZBar.xs -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\ZBar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\ZBar\Image.pod -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\ZBar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\ZBar\ImageScanner.pod -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\ZBar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\ZBar\Processor.pod -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\ZBar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\ZBar\Symbol.pod -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\ZBar
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\examples\paginate.pl -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\examples\processor.pl -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\examples\read_one.pl -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\examples
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\examples\scan_image.pl -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\examples
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\inc
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\inc\Devel
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\inc\Devel\CheckLib.pm -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\inc\Devel
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\ppport.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\t
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\t\Decoder.t -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\t
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\t\Image.t -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\t
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\t\Processor.t -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\t
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\t\Scanner.t -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\t
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\t\ZBar.t -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\t
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\t\barcode.png -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\t
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\t\pod-coverage.t -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\t
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\t\pod.t -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl\t
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\perl\typemap -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\perl
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\plugin
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\plugin\Makefile.am.inc -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\plugin
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\plugin\plugin.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\plugin
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\pygtk
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\pygtk\Makefile.am.inc -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\pygtk
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\pygtk\zbarpygtk.override -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\pygtk
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\pygtk\zbarpygtkmodule.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\pygtk
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\Makefile.am.inc -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\decoder.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\enum.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\exception.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\image.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\imagescanner.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\processor.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\scanner.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\symbol.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\symboliter.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\symbolset.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\test\barcode.png -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\test\test_zbar.py -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\zbarmodule.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\python\zbarmodule.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\qt
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\qt\Makefile.am.inc -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\qt
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\qt\QZBar.cpp -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\qt
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\qt\QZBarThread.cpp -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\qt
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\qt\QZBarThread.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\qt
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\Makefile.am.inc -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\barcodetest.py -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\dbg_scan.cpp -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\pdf417_encode.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\scan_video.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\test_convert.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\test_cpp.cpp -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\test_decode.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\test_gtk.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\test_images.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\test_images.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\test_jpeg.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\test_perl.pl -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\test_proc.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\test_pygtk.py -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\test_qt.cpp -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\test\test_video.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar-gtk.pc.in -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar-qt.pc.in -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar.ico -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar.nsi -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar.pc.in -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\Makefile.am.inc -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\config.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\convert.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\debug.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\decoder
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder\code128.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\decoder
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder\code128.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\decoder
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder\code39.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\decoder
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder\code39.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\decoder
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder\ean.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\decoder
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder\ean.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\decoder
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder\i25.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\decoder
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder\i25.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\decoder
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder\pdf417.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\decoder
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder\pdf417.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\decoder
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder\pdf417_hash.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\decoder
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder\qr_finder.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\decoder
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\decoder\qr_finder.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\decoder
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\error.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\error.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\event.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\image.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\image.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\img_scanner.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\img_scanner.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\jpeg.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\libzbar.rc -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\mutex.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\processor.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\processor.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\processor
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\processor\lock.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\processor
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\processor\null.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\processor
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\processor\posix.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\processor
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\processor\posix.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\processor
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\processor\win.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\processor
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\processor\x.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\processor
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\qrcode.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\qrcode
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\qrcode\bch15_5.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\qrcode
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\qrcode\bch15_5.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\qrcode
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\qrcode\binarize.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\qrcode
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\qrcode\binarize.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\qrcode
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\qrcode\isaac.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\qrcode
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\qrcode\isaac.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\qrcode
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\qrcode\qrdec.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\qrcode
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\qrcode\qrdec.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\qrcode
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\qrcode\qrdectxt.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\qrcode
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\qrcode\rs.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\qrcode
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\qrcode\rs.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\qrcode
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\qrcode\util.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\qrcode
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\qrcode\util.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\qrcode
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\refcnt.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\refcnt.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\scanner.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\svg.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\svg.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\symbol.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\symbol.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\thread.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\timer.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\video.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\video.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\video
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\video\null.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\video
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\video\v4l1.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\video
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\video\v4l2.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\video
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\video\vfw.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\video
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\window.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\window.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\window
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\window\dib.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\window
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\window\null.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\window
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\window\win.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\window
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\window\win.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\window
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\window\x.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\window
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\window\x.h -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\window
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\window\ximage.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\window
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbar\window\xv.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbar\window
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbarcam
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbarcam\Makefile.am.inc -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbarcam
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbarcam\zbarcam.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbarcam
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbarcam\zbarcam.rc -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbarcam
creating build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbarimg
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbarimg\Makefile.am.inc -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbarimg
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbarimg\zbarimg.c -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbarimg
copying build\lib.win-amd64-2.7\fastzbarlight\vendor\zbar-0.10\zbarimg\zbarimg.rc -> build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\zbarimg
copying build\lib.win-amd64-2.7\fastzbarlight\_zbarlight.pyd -> build\bdist.win-amd64\egg\fastzbarlight
byte-compiling build\bdist.win-amd64\egg\fastzbarlight\__init__.py to __init__.pyc
byte-compiling build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples\processor.py to processor.pyc
byte-compiling build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples\read_one.py to read_one.pyc
byte-compiling build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples\scan_image.py to scan_image.pyc
byte-compiling build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\examples\upcrpc.py to upcrpc.pyc
byte-compiling build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\python\test\test_zbar.py to test_zbar.pyc
byte-compiling build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test\barcodetest.py to barcodetest.pyc
byte-compiling build\bdist.win-amd64\egg\fastzbarlight\vendor\zbar-0.10\test\test_pygtk.py to test_pygtk.pyc
creating stub loader for fastzbarlight\_zbarlight.pyd
byte-compiling build\bdist.win-amd64\egg\fastzbarlight\_zbarlight.py to _zbarlight.pyc
creating build\bdist.win-amd64\egg\EGG-INFO
copying src\fastzbarlight.egg-info\PKG-INFO -> build\bdist.win-amd64\egg\EGG-INFO
copying src\fastzbarlight.egg-info\SOURCES.txt -> build\bdist.win-amd64\egg\EGG-INFO
copying src\fastzbarlight.egg-info\dependency_links.txt -> build\bdist.win-amd64\egg\EGG-INFO
copying src\fastzbarlight.egg-info\not-zip-safe -> build\bdist.win-amd64\egg\EGG-INFO
copying src\fastzbarlight.egg-info\requires.txt -> build\bdist.win-amd64\egg\EGG-INFO
copying src\fastzbarlight.egg-info\top_level.txt -> build\bdist.win-amd64\egg\EGG-INFO
writing build\bdist.win-amd64\egg\EGG-INFO\native_libs.txt
creating 'dist\fastzbarlight-0.0.14-py2.7-win-amd64.egg' and adding 'build\bdist.win-amd64\egg' to it
removing 'build\bdist.win-amd64\egg' (and everything under it)
Processing fastzbarlight-0.0.14-py2.7-win-amd64.egg
removing 'c:\python27\lib\site-packages\fastzbarlight-0.0.14-py2.7-win-amd64.egg' (and everything under it)
creating c:\python27\lib\site-packages\fastzbarlight-0.0.14-py2.7-win-amd64.egg
Extracting fastzbarlight-0.0.14-py2.7-win-amd64.egg to c:\python27\lib\site-packages
fastzbarlight 0.0.14 is already the active version in easy-install.pth

Installed c:\python27\lib\site-packages\fastzbarlight-0.0.14-py2.7-win-amd64.egg
Processing dependencies for fastzbarlight==0.0.14
Searching for Pillow==4.3.0
Best match: Pillow 4.3.0
Processing pillow-4.3.0-py2.7-win-amd64.egg
pillow 4.3.0 is already the active version in easy-install.pth
Installing enhancer.py script to C:\Python27\Scripts
Installing gifmaker.py script to C:\Python27\Scripts
Installing pildriver.py script to C:\Python27\Scripts
Installing pilfile.py script to C:\Python27\Scripts
Installing explode.py script to C:\Python27\Scripts
Installing thresholder.py script to C:\Python27\Scripts
Installing viewer.py script to C:\Python27\Scripts
Installing painter.py script to C:\Python27\Scripts
Installing player.py script to C:\Python27\Scripts
Installing pilconvert.py script to C:\Python27\Scripts
Installing pilprint.py script to C:\Python27\Scripts
Installing pilfont.py script to C:\Python27\Scripts

Using c:\python27\lib\site-packages\pillow-4.3.0-py2.7-win-amd64.egg
Searching for olefile==0.44
Best match: olefile 0.44
Processing olefile-0.44-py2.7.egg
olefile 0.44 is already the active version in easy-install.pth

Using c:\python27\lib\site-packages\olefile-0.44-py2.7.egg
Finished processing dependencies for fastzbarlight==0.0.14

Don't know how a 32-bit zbar package will act with a 64-bit fastzbarlight package...
next problem is getting go-vncdriver to compile on Windows :) Hope this helps someone.


Fix Integration Tests

Added createRequire to allow use of require statement in esModule context
Adjusted tsconfig in test folder to correctly resolve imported modules

Apologies, this was meant to be on a fork.


Issue 3: Progress Notifications Not Triggered at Thresholds and Delayed Data Persistence

Description:
During the execution, the expected progress notifications were not triggered when thresholds (either 1000 emails processed or every 30 minutes) were reached. Only the final notification was sent. Additionally, data was not persisted to MongoDB or updated in JSON until the end of the process, and memory cleanup did not occur periodically as expected. The lack of a progress bar suggests that task configuration may not be supporting concurrency or timely execution of intermediate steps.
Observed Behaviors:
•	No progress notifications sent at set thresholds.
•	JSON updates, MongoDB persistence, and memory cleanup occurred only at the end.
•	Progress bar did not appear.
Possible Causes:
1.	Single-Threaded Execution: If the program is running in a single-threaded manner while trying to handle multiple tasks (fetching, persisting, notifying), it may queue tasks sequentially, delaying intermediate steps (like JSON and MongoDB updates).
2.	Task Configuration Issue: If the program is improperly configured to send notifications only once at completion or lacks a specific task scheduler for intermediate steps, the thresholds (e.g., 1000 emails or 30 minutes) might not trigger.
3.	Blocking Operations or Resource Contention: If large data processing or network operations (like saving to MongoDB) block the main thread, this can delay or prevent intermediate steps, such as notifications or JSON updates, from executing until completion.
4.	Progress Bar and Logging Conflicts: The absence of a progress bar could indicate that logging and notification steps are not being triggered in a way that aligns with the email processing rate. This could also mean that there’s no check for notification conditions in the main processing loop.
5.	Variable Synchronization Issues: If variables that track email count or time are not updated synchronously with other tasks (e.g., due to timing delays or order of operations), the notifications might fail to reflect accurate counts or elapsed time.
6.	Concurrency and Memory Management: Without parallel processing, all tasks rely on a single queue, meaning that memory management (clearing processed data) might not occur until after all emails are processed.
7.	Code Execution Order: If JSON/MongoDB updates and memory cleanup are placed at the end of the processing loop rather than within it, these steps will only occur once all emails are fetched and processed.
Recommended Changes:
•	Eliminate Progress Bar: Unless parallel processing or multithreading can be implemented, removing the progress bar might simplify the program and help isolate where tasks are not being triggered.
•	Optimize Task Scheduler: Consider implementing a task scheduler or callback function that periodically checks for threshold conditions (like email count or elapsed time) and triggers notifications and persistence tasks as soon as they are met.
•	Separate Persistence and Notification: Refactor the code so that JSON updates, MongoDB persistence, and memory cleanup occur independently from email processing, based on thresholds rather than the end of processing.

Progress Notifications and Display Enhancement Needed
Current Status
After commit 54c1747, several related issues were fixed:

Email count tracking is now accurate
Final notifications show correct statistics
Data consistency between MongoDB and JSON is maintained
Time-based notifications (5-minute intervals) are implemented

Remaining Issues

Progress Bar Display

Progress bar implementation is not functioning
No visual feedback during processing
Need to investigate tqdm integration

Notification Thresholds

Email count threshold (1000 emails) notifications not implemented
Need to combine with existing time-based notifications

Data Persistence Timing

Need to verify intermediate data persistence
Potential optimization of MongoDB update frequency

Action Items

Fix progress bar display

Debug tqdm implementation
Ensure proper updates during processing

Implement email count threshold notifications

Add NOTIFICATION_THRESHOLD checks
Combine with time-based notifications

Verify intermediate data persistence

Add logging for MongoDB update timing
Optimize persistence frequency if needed

Notes

The recent fix (54c1747) addressed count accuracy but not display
Progress bar implementation is priority
Need testing with large datasets to verify notification behavior


Powered zombie spawner weirdness

Issue Description:
After a lenghty absence, let's say 8 hours, powered spawner bugs out. Drains energy, no spawns and weird bugged area appears nearby.
What happens:
Placed powered zombie spawner and used a dropkill setup. After relog no spawns appear and energy drains. Plenty of room. Nearby, usually below spawner a 2x2 area where you cannot place solid blocks appears. You can place water, punji sticks and sand IF you drop the sand in from above. If i move the spawner it works again. Bugged spawner has plenty of room, no excessive entities nearby and spawn checks are disabled. Otherwise default settings. I'm not sure but server reset seems to fix the bugged area and the spawner.
Alternatively i need to move the spawner everytime i wish to disconnect.
Using ftb utilities to keep area chunkloaded.
My theory is that this bugged block space is preventing monster spawns
What you expected to happen:
Spawner to keep spawning after relog.
Steps to reproduce:

Place spawner
Quit for a time, come back

...

Affected Versions (Do not use "latest"):

EnderIO:<IP_ADDRESS>_beta
EnderCore:<IP_ADDRESS>-beta
Minecraft: 1.10.2
Forge:<IP_ADDRESS>4

Your most recent log file where the issue was present:
[pastebin/gist/etc link here]

If you cannot place normal blocks somewhere that means there are mobs at the point. I'd guess there are enough invisible zombies there to prevent further spawns.

hmmh latest anomaly is 1x2 area above spawner .. maybe ill just fill it with sand and see what happens.

invisible, untouchable, unmovable, unkillable zombies, I'd say. I just don't know why they are bound to the spawner---we don't keep any references to the mobs we spawn.

Moving the spawner horisontally (maybe too little ) had no effect but when i moved it up about 6 blocks it started spawning again normally. Not a solution obviously but it's something atleast.

so maybe you just moved it out of range of the phantom mobs. That'd make sense.

This would be my guess too. First I tried /kill @e[type=Zombie] with no luck. Just got some 'Killed Zombie messages with no visible results and still no spawning. Can't guess on the number of invis zombies but it's strange that they had no effect on game performance and the check for entities number was disabled in config.

Just to double check; did you also set poweredSpawnerMaxNearbyEntities to 0 or just disable poweredSpawnerUseVanillaSpawChecks?

I don't think I'll find what's happening today. Next time it happens, could you please enable hitboxes (F3+B) and have a look for invisible zombies/baby zombies/chickens? Thx!

MaxNearbyEntities=0,MaxPlayerDistance=0 and vanilla checks false.  Tried the hitbox thing but saw nothing. First time this happened there was a number of chickens about on the ground, maybe left by baby zombies and I can't be sure but I seem to recall that after I killed those ( around 10 ) the spawner spawned 1 zombie once or twice.

https://t.gyazo.com/teams/airside/75d054f87f1650c78e4bc201da60bdd7.png
So I'm getting something similar and I'm wondering if it's related. That hole is where my spawner was. There's about 8 skeletons or so all stacked together. They take damage but when they're at about 4.5 health left they take no more damage. issuing a /kill says it kills a bunch of skeletons but these nerds remain.

I'm having the same issue as dualmoon on Infinity Lite 1.8.0 (Minecraft 1.10.2 with EnderIO 3.1.156, EnderCore <IP_ADDRESS>, and Forge <IP_ADDRESS>4).
It only seems to halt my skeleton and wither skeleton spawners, and it seems to exclusively occur with skeletons. They spawn inside of a block and enter this glitched state. Using '/kill' doesn't affect them, nor does attacking them. Using a soul vial captures the mob, but the entity remains bugged in place.

@EnragedRabisu Does the entity stay or are there multiple ones at the same location? (Reason for the question: I have code in the soul vial to make really, really sure captured entities don't stay around.)

The first time it happened, there were definitely a lot of them (So many that touching them shoved me away at high speeds), but I pulled out skeletons for several minutes with a pair of soul vials. Second time it looked like only one or two, but I still pulled several out.
I left my spawners running for a few minutes and left the area. I came back to this: https://imgur.com/a/orsxL
I seem to pull the same skeleton out of the 'pile' every time as well. This time it has an enchanted bow.
Notably, I removed my Skeleton spawner, so I can only assume it has something to do with the wither skeleton spawner I still have in there. For completion's sake, I also have slimes, enderman, witches, creepers, zombies, spiders, and blazes. I'll remove the wither skeleton spawner this time before I leave for class to try and narrow things down further.

Relates to #4362 prehaps?

My base instinct for the initial problem is actually a problem with FTB Utilities chunk loading. It's bugged to all hell, at least in the 1.10 FTB Beyond pack. I ran into a wide variety of issues. It seems like it's doing something that is improperly keeping chunks loaded which resulted in all sorts of machines bugging out. I ultimately just enabled Extra utilities chunk loading wards and disabled the FTB Utilities chunk loading.


[Bug]: Save button should be read-only if any of the required fields are left blank.

Is there an existing issue for this?

[X] I have searched the existing issues

Description
On the S3 datasource form, if the access key and the secret key fields are left blank, then also the save button is enabled.

Steps To Reproduce

Click to add a new S3 datasource
Leave access key and secret key fields as blank

Public Sample App
No response
Environment
Production
Issue video log
No response
Version
1.9.13

Related issue: https://github.com/appsmithorg/appsmith/issues/21088

is this issue still unresolved?

Closing it as it is not reproducible anymore on prod.


CMake Tools doesn't recognize CMakeLists.txt on Windows

Brief Issue Summary
On Windows, when configuring cmake through CMake Tools, the "You do not have a CMakeLists.txt" message appears even though the file does exist.
Expected:
The project configures
Apparent Behavior:
CMake Tools doesn't find the CMakeLists.txt
CMake Tools Log
[cms-client] Configuring using the "Ninja" CMake generator
[cms-client] Configuring using the "Ninja" CMake generator

Developer Tools Log
 INFO no standard startup: panel is active
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.211Z [debug] [rollbar] Updated Rollbar payload {"environment":"production","packageJSON":{"name":"cmake-tools","version":"1.1.1"},"client":{"code_version":"1.1.1"},"platform":"win32"}
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.439Z [debug] [kit] Reading kits file C:\Users\Justin\AppData\Roaming\CMakeTools\cmake-tools.json
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.440Z [debug] [kit] Not reading non-existent kits file: c:\Users\Justin\Documents\CPP\pitchfork\.vscode\cmake-kits.json
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.606Z [info] [kit] Successfully loaded 12 kits from C:\Users\Justin\AppData\Roaming\CMakeTools\cmake-tools.json
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.609Z [debug] [main] Safe constructing new CMakeTools instance
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.611Z [debug] [variant] Constructing VariantManager
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.613Z [debug] [main] Constructing new CMakeTools instance
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.615Z [debug] [main] Starting CMakeTools second-phase init
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.617Z [debug] [rollbar] Checking Rollbar permissions
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.625Z [debug] [rollbar] Rollbar enabled?  true
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.739Z [info] [variant] Loaded new set of variants
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.742Z [debug] [main] CMakeTools instance initialization complete.
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.743Z [debug] [main] Injecting new Kit into CMake driver
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.747Z [debug] [kit] Reading kits file C:\Users\Justin\AppData\Roaming\CMakeTools\cmake-tools.json
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.767Z [info] [kit] Successfully loaded 12 kits from C:\Users\Justin\AppData\Roaming\CMakeTools\cmake-tools.json
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.769Z [debug] [kit] Not reading non-existent kits file: c:\Users\Justin\Documents\CPP\pitchfork\.vscode\cmake-kits.json
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.771Z [debug] [rollbar] Updated Rollbar payload {"kit":{"name":"Visual Studio Community 2017 - amd64","visualStudio":"e3c5dd2b","visualStudioArchitecture":"amd64","preferredGenerator":{"name":"Visual Studio 15 2017","platform":"x64"}}}
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:19.771Z [debug] [main] Injecting new Kit into CMake driver
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] activating extension
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:22.349Z [debug] [extension] Configuring workspace on open  file:///c%3A/Users/Justin/Documents/CPP/pitchfork
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:22.351Z [debug] [main] Run configure
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:22.351Z [debug] [main] Saving open files before configure/build
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:22.795Z [debug] [main] Starting new CMake driver
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:22.796Z [debug] [main] Starting CMake driver
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:22.797Z [debug] [driver] CMakeDriver Kit set to Visual Studio Community 2017 - amd64
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:24.148Z [debug] [driver] Run _refreshExpansions
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:24.149Z [debug] [cms-driver] Run doRefreshExpansions
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:24.149Z [debug] [driver] Run _refreshExpansions cb
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:24.159Z [debug] [cms-client] Started new CMake Server instance with PID 6536
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:25.162Z [debug] [driver] Trying to detect generator supported by system
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:25.192Z [info] [cms-client] Configuring using the "Ninja" CMake generator
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:25.196Z [debug] [driver] Setting new variant , Emit debug information without performing optimizations
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:25.196Z [debug] [driver] Run _refreshExpansions
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:25.197Z [debug] [cms-driver] Run doRefreshExpansions
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:25.197Z [debug] [driver] Run _refreshExpansions cb
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:25.265Z [debug] [cms-client] Started new CMake Server instance with PID 3496
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:26.266Z [debug] [driver] Trying to detect generator supported by system
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:26.301Z [info] [cms-client] Configuring using the "Ninja" CMake generator
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:26.398Z [debug] [driver] Start configure
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:26.398Z [debug] [driver] Runnnig pre-configure checks and steps
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:272 [Extension Host] [CMakeTools] 2018-09-03T04:29:26.399Z [debug] [driver] No configuring: There is no  c:/users/justin/documents/cpp/pitchfork/cmakelists.txt
/C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2386 You do not have a CMakeLists.txt
t.onDidNotificationChange @ /C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:2386

Platform and Versions

Operating System: Windows
CMake Version: 3.12.1
VSCode Version: 1.26.1
CMake Tools Extension Version: 1.1.1
Compiler/Toolchain: Visual C++ 2017

Other Notes/Information
Clicking "Quickstart a new CMake project" fails with the message: "This workspace already contains a CMakeLists.txt!"
I'm guessing this has to do with the fact that Windows uses case insensitive file paths.

It's happening with the Pitchfork project, but not with other projects.

@Randshot I think I should try a fresh git clone to see if that fixes the issue.
I originally thought it had to do with case-insensitive paths, but then once I realized it worked with other projects, I no longer thought that.
Yes, I tried configuring from the terminal and it does work there.

Here's what I believe happened: I created the directory from the Windows Subsystem for Linux (WSL), even though it is a Windows folder. Windows automatically enables case sensitivity for files created from the WSL, meaning that the paths are actually case sensitive.
I verified it by running fsutil.exe:
C:\...\pitchfork>fsutil.exe file queryCaseSensitiveInfo .
Case sensitive attribute on C:\...\pitchfork is enabled.

Well, that's a weird edge case.
Now the question is how to best detect edge cases like these.
I guess we could run fsutil.exe on the workspace folder.

@Quincunx271 I think internally it is needed, for comparing paths and the like.
I have found this comment on an MSDN blog post:
Matt Waters
June 21, 2018 at 17:16
I used WSL for git with a legacy compiler that always expected case-insensitivity. I think it makes file names all lower or all upper case at some point. I checked out an old branch which deleted some directories. The legacy compiler failed due to case sensitivity. I had no idea about this feature.

Also, I did not just want to fix all new directories with fsutil. There were a lot of directories and I may have to change them on every checkout between branches.

In case people with similar issues find this blog post first (like I did), I will give how I fixed the issue. I had to create /etc/wsl.conf within WSL. The following lines were added:

[automount]
options = case=off

At least for me, I also had to restart my whole computer, not just WSL, to implement wsl.conf. Not sure why. The wsl.conf blog post just says to restart WSL, which didn’t work for me.

This might be a temporary solution? Don't know whether this will break applications on the Linux side though.

Yeah, the user turning off case sensitivity globallt with wsl.conf is an option, and it shouldn't break anything in Linux except for things which assume they can create colliding files.
My workaround was to turn off case sensitivity for the single project folder. Cmake Tools seems to interact fine if I do that

That's gross. There have been a few bugs opened related to path normalization. There's actually a change I have pending for the 1.1.2 release branch (uncommitted) that will change the way the ext does path normalization. It may or may not help with this situation. I just wish the Windows API gave a "canonicalize path" function.
Case-insensitive paths are a mistake.

OMG, per-directory case-sensitivity... Thank you so much for root-causing and sharing this, I would have never suspected something that insane.
Similar to the example above, I experienced this error in many random places:
CMake Error at foo\CMakeLists.txt:123 (ADD_SUBDIRECTORY):
  The source directory

    C:\Users\joe\Project\foo\bar\

  does not contain a CMakeLists.txt file.

This was happening in many random directories because I initially checked out Project in Windows and updated it later from Windows Subsystem for Linux. I promise I won't do that again.
WSL is generally awesome but the default way it uses this bug^H feature by default is really bad.
I found a recursive "repair" script in PowerShell there: https://stackoverflow.com/questions/51591091/apply-setcasesensitiveinfo-recursively-to-all-folders-and-subfolders
If you're reading this there's a good chance you've just been hit by this default WSL behaviour too hence you may prefer to start from a (tested!) repair script in shell:
time find -type d -exec /mnt/c/Windows/System32/fsutil.exe file queryCaseSensitiveInfo {} \; | awk '/is enabled/ { print $6 } ' |  while read -r; do /mnt/c/Windows/System32/fsutil.exe file setCaseSensitiveInfo "$REPLY" disable; done
As opposed to the PowerShell repair script above this shell version changes only the directories that need changing. This may or may not be faster, in any case it took only a few minutes on ~15000 directories which was fast enough for me.

@Quincunx271 does this still occur? I'm not sure if the 1.1.2 fixes changed the behavior here or not.

Sorry, I haven't gotten around to checking this yet. I'd have to make a project with case sensitivity to test it, and I haven't had much free time in the past few weeks.

AFAICT, this is solved.


CPU usage 100% on MacOS

ft is working very well for me. I'm using it daily. However, I recently noticed the macbook was a little warm, when I checked the ft process had one CPU core at 100%. Check the attached screenshot. I'm guessing this might be due to checking if the file was written very rapidly! Maybe there is a way to hook into file monitoring/watch services into macos instead ? or at least check less aggressively. Happy to test any debug builds.

Thanks Ahmed!
Yes it should definitely not use that much CPU. I'll look into it.
What protocol are you tunneling? Does the high CPU usage happen straight away, after a while, after a disconnect?

Oh!
I think I found the issue:
        public static void Wait(int ms)
        {
            if (RuntimeInformation.IsOSPlatform(OSPlatform.Linux))
            {
                Thread.Sleep(ms);
                return;
            }

            if (RuntimeInformation.IsOSPlatform(OSPlatform.Windows))
            {
                WindowsDelay.Wait(ms);
                return;
            }
        }

I'll fix it up tonight :)

This is now fixed in v2.2.1
Thanks Ahmed!


[Dummy] Support to provide advices

This is awesome!  Every line of code I get to delete is a joy!
Many thanks, @fcollonval

@fcollonval I've created a branch, LTS-Devel (Long Term Sustainable development) where I'm implementing your changes.  I'm currently getting hundreds of tsc errors, which just means I've screwed up a config file.  If push comes to shove I'll just delete and redo with cookiecutter.
Thanks again

@fcollonval I've merged your changes into a branch, and I will create a PR and ask you to review, if that is OK.  Before I do:

Are you willing?
Is there anything I can/should do to make the review easy on you?

I can't thank you enough for all the help you've given us, and I hesitate to ask for more, but I am hoping that the community will find our extension useful for things other than Galyleo.  We called it the "JupyterLab Universal Extension" because the idea was that all we (or anyone else) would have to do to plug in a new web-based editor was write a little glue code on the editor side (it's about 30 lines of code for Galyleo) and simply provide a settings file on the JupyterLab side.
We aren't there yet, but we are close.

1. Are you willing?

Sure I can take a look.

2. Is there anything I can/should do to make the review easy on you?

If you could set up a binder for the PR with an example of what to check, it will be great.

I have it up and running on our beta server, and so probably the easiest thing for you is for me just to give you an account on that (it's an enhanced JupyterHub).  All I need is a Google-recognized email address.  Is that OK?

All I need is a Google-recognized email address. Is that OK?

I sent you a PM on gitter.


ledisdb.com has expired

As can be seen by visiting ledisdb.com, the registration has expired.

oh, forget to renew 😭

Now it's https://ledisdb.io .


Option to disable discrete GPU

Summary
Atom will by default use any discrete GPU available. It used to be possible to disable this by launching it with --disable-gpu but Electron recently removed this feature and apps now have to explicitly call app.disableHardwareAcceleration() instead.
Motivation
Using the discrete GPU typically eats twice the battery as the integrated one, and turn laptops into furnaces.

Thanks for reaching out.
Electron will still pass along the --disable-gpu flag to Chromium when passed at the command line and Chromium still supports the --disable-gpu flag. The change you reference is a documentation change because it won't work when passed via appendSwitch(), a different mechanism than passing on the command-line.
I hope that helps!

@lee-dohm thanks for the quick answer.
However, passing --disable-gpu --disable-gpu-compositing to the latest version of Atom doesn’t prevent it from switching to the discrete GPU (whereas the “Disable Hardware Acceleration” setting in Chromium achieves exactly that).
It’s not clear to me how Atom passes those options to Electron so I don’t know where the problem lies —just that this is currently broken.
Cheers,
Julien.

Interesting, thanks!
@daviwil Would you mind looking into this?

If it help, I’m running the latest version of macOS Sierra on a MBP from 2010, and use https://github.com/codykrieger/gfxCardStatus to show switches from integrated to discrete.

Somewhat related: There are two reports about "text not showing in mini editors" and the only solution so far seems to open Atom with the --disable-gpu flag.

More information: on my newer (early 2013) MBP Atom keeps using the integrated GPU even without using the --disable-* flags.
How which GPU to use is chosen looks mysterious 😆

However, passing --disable-gpu --disable-gpu-compositing to the latest version of Atom doesn’t prevent it from switching to the discrete GPU (whereas the “Disable Hardware Acceleration” setting in Chromium achieves exactly that).

Actually, it has an effect!
/Applications/Atom.app$ ./Contents/MacOS/Atom

→ 2 processes use the discrete GPU: Atom and Atom Helper.
/Applications/Atom.app$ ./Contents/MacOS/Atom --disable-gpu --disable-gpu-compositing

→ Only 1 process uses the discrete GPU: Atom (Atom Helper does not).

Why are you calling the Atom executable from inside the .app package? There may be some things in atom.sh that help --disable-gpu to work?

I tried that already, but posted the “pure” command to show the problem is not caused by that wrapper script.
That a wrapper script could ever enable behaviors not supported by the binary it wraps never even touched my mind 😬

Hey @jcayzac, I'm running macOS High Sierra on a 2013 15" MBP and I don't see the NVidia GPU getting turned on when I launch Atom 1.29.0 or 1.30.0-beta2.  I'm judging this from using gfxCardStatus and watching for GPU changes when I launch Atom.
Is it possible that you're using a package that somehow causes the discrete GPU to be turned on?  Can you try running Atom in safe mode with atom --safe to see if the discrete GPU gets activated?

@daviwil Like I said in my previous comments I can’t reproduce the problem on my 2013 MBP either, it only happens on my 2010 MBP.
I’ll try launching in safe mode when I get home tonight (Japan time), thanks!

@daviwil I tried --safe in combination with other flags (--disable-gpu, --disable-gpu-compositing, --disable-direct-composition) but it still switches to using the discrete GPU on my 2010 MBP 😢
I find no difference with or without --safe. Passing --disable-gpu --disable-gpu-compositing still effectively disable the discrete GPU for all the Atom Helper processes but not for the main Atom one.

Given it only happens on my old MBP and that I can reproduce the problem with another Electron app (I just tested with Visual Studio Code and it's the exact same behavior), unless it relates to other problems experienced by more users I'd totally understand if you'd close this issue.

I have graphics issues with chrome/chromium/electron/atom on two Linux computers using different OS and graphics units. The browser engine does not seem to work well with some common graphics hardware drivers under Linux. All chromium-based programs I use (chrome/chromium/rambox) have a simple configuration option to turn off hardware acceleration. Atom has not, instead you have to go and modify globally installed package files on the system which get overwritten on the next update, or create some other script or shortcut. Can you maybe elaborate on why you don't want such a simple configuration option, as proposed in  #17699?

For support reasons, we don't want a configuration option that shows up in the Settings View that can be accidentally clicked that is essentially, "Make my performance bad". Having a command-line option, like we currently do, is a much better alternative. It is discoverable via the debugging documentation but not in a location where it can be accidentally enabled.

@lee-dohm Understood. Chrome etc. have an advanced settings dialog.

@lee-dohm I believe that setting in Chrome, as well as Electron’s command line option and Application API method, are all misnomers. What they do is to prevent the renderer to use low-level GPU renderers but every modern OS uses the GPU for its higher-level drawing APIs.
On macOS for instance those APIs are most-definitely backed by Metal, which guarantees top performance on the integrated GPU. I never noticed any bad performance issue when turning off that “hardware acceleration”, quite the opposite in fact if you factor in battery life, watts per hour and temperature.
That option would be less silly if its name were changed to “Disable direct low-level rendering” or something like that.

@jcayzac What you're describing has not been the experience that has been told to me by people who have used that flag on many systems. Perhaps you are right and they are the outlier and yours is the common case, but if we cannot exactly describe what the experience is that someone would have by changing a setting, there is even less reason to have it as an easily-accessible setting.

@lee-dohm fair enough!

I can't comment on other OS but for my part, it turns electron-based programs from unusable to usable without any notable difference in performance. I don't know how to blame, but I believe that the upstream Google devs apparently don't get along with the Linux graphics subsystem. It's the only framework I know that produces stripes and flickering artifacts in the menus on both my computers with Intel graphics (most frequently used hardware). There should be a low-level configuration for the electron framework.

This option can be very useful as a hidden/advanced one for people having GPU issues like #17094, who need a permanently disabled gpu acceleration.
There can be three ways to implement it and not go against @lee-dohm thesis about too-easy-accessible:

Easy-hack-way: Leave the implementation code in start.js but remove config schema change, this way option will only be displayed in settings if it is manually enabled by user by editing their config.cson, by doing so they confirm their intent.

Pros: easy, requires little changes
Cons: undocumented setting without schema

Hidden option support: add flag to schema so that it is not displayed by settings-view package

Pros: option will have schema
Cons: once enabled user will not see it anywhere other that settings.cson

Advanced option support: introduce more support into settings-view for options like this

Pros: schema, easier access for users
Cons: hardest to implement, requires interface changes

https://github.com/electron/electron/issues/13303 was closed since the right fix for « targeting » the integrated GPU would be to edit the blacklist maintained in the Chromium project.
Meanwhile, the only option for users of Chromium derivatives is to request that "no GPU" be used.
I’ve already moved on to IntelliJ, but I’d love being able to revert to using Atom if it offered an option to disable the GPU, even if that’s just on the command line…

MacBook Pro (15-inch, Early 2011)
I'm trying to disable using High Perf. GPU.

open /Applications/Atom.app/ --args --disable-gpu --ignore-gpu-blacklist

It doesn't work.
But for Google Chrome it works fine
open /Applications/Google\ Chrome.app/ --args --disable-gpu --ignore-gpu-blacklist

Waiting for any solution anyway.

@lee-dohm how do I disable using High Perf. GPU? Can I do something with Atom Init Script or pass any command line arguments?
My problem is the same:
Steps to Reproduce

MacBook Pro (15-inch, Early 2011)
I'm trying to disable using High Perf. GPU.

open /Applications/Atom.app/ --args --disable-gpu --ignore-gpu-blacklist

It doesn't work.
But for Google Chrome it works fine
open /Applications/Google\ Chrome.app/ --args --disable-gpu --ignore-gpu-blacklist

Expected behavior:
Use Intel HD Graphics 3000 to have low energy impact.
Actual behavior:
Atom uses High Perf. AMD Radeon HD 6490M having high energy impact.
Reproduces how often:
100%
Versions
atom --version
Atom    : 1.33.1
Electron: 2.0.16
Chrome  : 61.0.3163.100
Node    : 8.9.3
apm --version
apm  2.1.2
npm  6.2.0
node 8.9.3 x64
atom 1.33.1
python 2.7.15
git 2.20.1
OS: 64bit Mac OS X 10.13.6 17G4015

macOS' open command isn't the method for passing command line arguments to Atom. You should use the atom command directly. For more information, see the Atom Flight Manual instructions on installing Atom.

@lee-dohm same

Same issue here. Macbook Pro 2011. No matter what I do, then Atom will always use the discrete graphics card, which it in no way needs.
Kind of curious why Atom has ever introduced this to begin with? In what scenario is it needed?

@fjeddy please see my previous answer to why Atom uses the discrete GPU at https://github.com/atom/atom/issues/16247#issuecomment-345986985.

Hello, it's from the future. Any updates on this?

Upcoming versions of Atom will be using Electron 3, which according to electron/electron#13303 contains an updated GPU blacklist which should resolve some issues with the underlying Chromium engine forcing the usage of a discrete GPU despite the --disable-gpu flag.


'nother taphy overload?

say I want a version of taphy that provides an extra output (the transposed indexes) but works in the same way.. how would I do that without writing 4 extra versions?
ah, if only optional array arguments were possible! that would be adorable! to be able to omit the trig out array.. (wait, I'm not sure if they're really not?)

hbout I edit them all, adding the extra output. and then adding a wrapper that accepts only the usual outputs (and an extra one without the trigger out) and passes the inputs to a normal taphy, returning the requested outs, and leaving the rest

opcode Taphath, kk[]k[]k[], kk[]k[]k[]iOOOO
opcode Taphath, kk[]k[], kk[]k[]k[]iOOOO
opcode Taphath, kk[], kk[]k[]k[]iOOOO
maybe even:
opcode Taphath, k, kk[]k[]k[]iOOOO
oh mama! this is giving me evil ideas! I might even do something about the range arrays mess! (one range array version and one that provides arrays spaning the entire range and runs the opcode with them)

annoying though that it would still be copying those unused arrays in the wrapper opcode and doing all that useless computation

holy shit! I can do this to all of them! bohahahaha! imagine functional-syntax plugging them into each other like
Taphath(utBasemath(ktrig, fillarray(4,2,2,1)))

raving to free99 solves everything!
so I was silly when I implemented the overloads this way, yes it's technically more efficient in some cases, but I can save a whole lotta complexity (huge code is annoying and scary to make changes to)
keeping only one of the 4 current definitions (kfn with range arrays) and making small overloads for passing an ifn that calls the original with the given ifn stored in a kfn and returning its outputs. same goes for the arrays as described earlier. one definition taphy

I'm terrible at communicating what I mean!

why does this work?
kAS, kP[], kT[], kN[] Taphath kTrig, kNote, kGain, kQ, iScale

I don't have a no-range ifn version
yet the:
kAS, kP[], kT[], Taphath kTrig, kNote, kGain, kQ, iScale

yells about no entry

oh but I do! a k input will accept an i value! lol this stuff keeps you humble

because I don't have a kk[]k[] Taphath kk[]k[]k[]i version! (the min max arrays are still required (yeah, it seems I do need all the combinations.. it's still better than what I had before)
do I even need the ifn version?

just a no arrays version, a no index out one, and a neither version, and she's back. no need for ifn version, it's just a number and it will take an i-time and use it in the place of a k one

if I want a no trig version I can do it, it just needs to have 2 variants, one with the range arrays and one without

will play with her for some time before I merge

she gorgeous!


⚠ ClamAV has degraded performance

In 0c4b541, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 203 ms

Resolved: ClamAV performance has improved in 90fbf64.


feat: Make AsyncArrowWriter accepts AsyncFileWriter

Which issue does this PR close?
Closes https://github.com/apache/arrow-rs/issues/5738
Rationale for this change
This makes AsyncArrowWriter accepts AsyncFileWriter so users can save an extra copy if they have a writer that can accept Bytes directly.
What changes are included in this PR?
A bit change from the proposal but mainly the same.
Are there any user-facing changes?
AsyncArrowWriter now accepts AsyncFileWriter instead of AsyncWrite. But AsyncFileWriter has been implemented for all AsyncWrite, so existing code should be working as before. For example, all testing code is not touched :love_letter:
Maybe we can catch up the arrow 52's train? https://github.com/apache/arrow-rs/issues/5688

Hi @tustvold, PTAL. Thanks!

Thank you


Add pre-ci-bootstrap playbook

This playbooks will provide configuration needed
to run ci-bootstrap role
As a pull request owner and reviewers, I checked that:

[X] Appropriate testing is done and actually running
[X] Appropriate documentation exists and/or is up-to-date:

[X] README in the role
[X] Content of the docs/source is reflecting the changes

/hold
testing in test-project

/approve

testproject passing: https://review.rdoproject.org/zuul/build/49f7d8c568e34da4b5a96be06bf6480e

/hold cancel

/approve

/lgtm