Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Console View

Legend:   Passed Failed Warnings Failed Again Running Exception Offline No data

Mitchell Stokes
Merge branch 'master' into deploy-ng
rdb
Separate out Python compat hacks from py_panda.h into py_compat.h
Mitchell Stokes
deploy-ng: Add initial support for creating .app bundles for macOS

The actual bundling is currently commented out in the bottom of
build_apps.build_runtimes(). Generating the .app was tested from a Linux
host and looks mostly correct upon a visual inspection of the contents.
However, no testing was done for actually running the .app on macOS,
which is why it is commented out. This was also not tested on Python 2.

There are also some TODO comments that need to be addressed.
deflected
Loader: Fixed crash when canceling async loading of model

        - Clean up the _loader after we clean up the requests,
        not before that

Signed-off-by: deflected <deflected@users.noreply.github.com>
Mitchell Stokes
deploy-ng: Error if both gui_apps and console_apps is empty
rdb
Implement awaitable thread-safe future for async operations

This introduces AsyncFuture as a new base class of AsyncTask.  It's modelled after asyncio's Future class, except that it is thread-safe and you can use result() to block the current thread waiting for the future to finish (of course this is not necessary for use with coroutines).

AsyncFuture should be used for any operation that finishes in the future, to get the benefit of awaitability within coroutines as well as a standard interface for querying status and results of the operation as well as cancelling it.  As such, it's been implemented in various places, including texture.prepare() and win.trigger_copy().

Note that AsyncFuture is intended to be used *once*; it cannot be used more than once.  As an example of how this works, tex.prepare() will return the same future as long as the prepare isn't complete, but when it is done, subsequent calls to tex.prepare() will return a new future.
rdb
deploy-ng: implement getting executable path on Linux and macOS
Mitchell Stokes
Merge branch 'master' into deploy-ng
rdb
deploy-ng: new extensible blob format with PRC configurability
Mitchell Stokes
deploy-ng: Add libbz2, libz, and liblzma to the manylinux1 ignore list
deflected
ShowBase: Fixed crash when want-render2dp is False

        - Fixed crash in ShowBase when want-render2dp setting
        is set to 0(False).

Signed-off-by: deflected <deflected@users.noreply.github.com>
Mitchell Stokes
Merge branch 'master' into deploy-ng
rdb
makewheel: use platform from build
rdb
Fix assertion when rendering bounding volumes (broken since 6f8b379)
Mitchell Stokes
deploy-ng: Rename some options

  * include_paths -> include_patterns
  * exclude_paths -> exclude_patterns
  * deploy_platforms -> platforms
Mitchell Stokes
deploy-ng: Pass build_apps commands to build_scripts

This allows build_scripts to access configuration.
rdb
interrogate: more improvements to seq/map wrappers
Gets rid of properties defined as both MAKE_SEQ_PROPERTY/MAKE_MAP_PROPERTY, which are just a bad idea. Instead, adds a way for map properties to define a separate "keys" interface.

Fixes: #203
deflected
ShowBase: Minor fixes over aspect ratio and size calculations

        - Do not take into accound SBS if it is not enabled
        - Always return value for getSize()
        - Properly handle SBS for window-events
        - Redo positioning of aspect2d(p) markers exactly as
        they are created when adjusting aspect ratio

Signed-off-by: deflected <deflected@users.noreply.github.com>
rdb
Fix support for pickling NodePaths (broken in 1b1d80c)

Fixes: #199
Mitchell Stokes
deploy-ng: Use callbacks for build_scripts
rdb
interrogate: more improvements to seq/map wrappers
Gets rid of properties defined as both MAKE_SEQ_PROPERTY/MAKE_MAP_PROPERTY, which are just a bad idea. Instead, adds a way for map properties to define a separate "keys" interface.

Fixes: #203
Mitchell Stokes
deploy-ng: Add a mechanism to FreezeTool for "hidden" imports

For now we have hooks for PyTest and pkg_resources.
rdb
makepanda: look for vorbis library without _static suffix

Fixes: #202
rdb
Compile fix for macOS build

[skip ci]
rdb
Fix compile errors
rdb
interrogate: more improvements to seq/map wrappers
Gets rid of properties defined as both MAKE_SEQ_PROPERTY/MAKE_MAP_PROPERTY, which are just a bad idea. Instead, adds a way for map properties to define a separate "keys" interface.

Fixes: #203
rdb
Fix priority argument ignored in NodePath::set_shader_input
rdb
display: also avoid getting more than 24 color bits if 0 were requested

See issue #197
Younguk Kim
Add HAVE_PYTHON macro to build without python
Mitchell Stokes
deploy-ng: Add files to build application out of the unit tests

This will be a good way to make sure everything in the tests work under
a frozen environment.

NOTE: The application builds and runs, but no tests are collected. We
still need to figure out how we want to handle tests. Freeze them all
and modify test collection? Add py/test files to the build directory and
try to run them?
Mitchell Stokes
deploy-ng: Remove check for non-empty platforms list in build_apps::finalize_options()

This is actually a supported use-case (we fall back to the Panda3D
platform when no platforms are listed).
rdb
Implement awaitable thread-safe future for async operations

This introduces AsyncFuture as a new base class of AsyncTask.  It's modelled after asyncio's Future class, except that it is thread-safe and you can use result() to block the current thread waiting for the future to finish (of course this is not necessary for use with coroutines).

AsyncFuture should be used for any operation that finishes in the future, to get the benefit of awaitability within coroutines as well as a standard interface for querying status and results of the operation as well as cancelling it.  As such, it's been implemented in various places, including texture.prepare() and win.trigger_copy().

Note that AsyncFuture is intended to be used *once*; it cannot be used more than once.  As an example of how this works, tex.prepare() will return the same future as long as the prepare isn't complete, but when it is done, subsequent calls to tex.prepare() will return a new future.
rdb
Don't include dlmalloc_src.cxx in interrogate

Fixes: #200
rdb
Implement awaitable thread-safe future for async operations

This introduces AsyncFuture as a new base class of AsyncTask.  It's modelled after asyncio's Future class, except that it is thread-safe and you can use result() to block the current thread waiting for the future to finish (of course this is not necessary for use with coroutines).

AsyncFuture should be used for any operation that finishes in the future, to get the benefit of awaitability within coroutines as well as a standard interface for querying status and results of the operation as well as cancelling it.  As such, it's been implemented in various places, including texture.prepare() and win.trigger_copy().

Note that AsyncFuture is intended to be used *once*; it cannot be used more than once.  As an example of how this works, tex.prepare() will return the same future as long as the prepare isn't complete, but when it is done, subsequent calls to tex.prepare() will return a new future.
rdb
interrogate: clean py_panda.h; use macros to access Dtool_PyInstDef
rdb
interrogate: pass "args" tuple to function that takes PyObject *args
Mitchell Stokes
deploy-ng: Lock tests app to pytest 3.2.0

pytest 3.3.0 brings in a pluggy dependency that cannot be satisfied with
wheels.
rdb
interrogate: more improvements to seq/map wrappers
Gets rid of properties defined as both MAKE_SEQ_PROPERTY/MAKE_MAP_PROPERTY, which are just a bad idea. Instead, adds a way for map properties to define a separate "keys" interface.

Fixes: #203
Mitchell Stokes
deploy-ng: Remove unused build_apps.copy_paths
Mitchell Stokes
deploy-ng: Rename build_scripts to file_handlers