Skip to content

Releases: OnShift/turbogears

V1.0.11.12

01 Apr 14:26
a49b504
Compare
Choose a tag to compare

Bug Fix: Assume encoding defaults to kid template assume encoding by default for widgets

v1.0.11.11

06 Feb 17:11
4da710b
Compare
Choose a tag to compare
  • Remove header injection vulnerability on redirect
  • Actually bump the version in the file.

v1.0.11.10 - enable profiling only with special environment variable

10 May 18:48
b5420cb
Compare
Choose a tag to compare

This release will start profiling in disabled mode unless TURBOGEARS_PROFILER_ACTIVATE=True is added to the environment.

v1.0.11.9 - adding debug and cache trace tool

04 May 15:27
f3d3ac9
Compare
Choose a tag to compare

adding debug and cache trace tool

  • DEBUG will allow RPDB trace on a separate thread
  • CACHE will dump all the objects presently pointed to by SQLObject cache

v1.0.11.8

13 Apr 17:08
c503937
Compare
Choose a tag to compare

Pinning psutils==5.4.3

v1.0.11.7 - add pympler to turbogears for memory use analysis

27 Mar 21:14
dab6a54
Compare
Choose a tag to compare

Now a command can be passed to turbogears memory profiler through FIFO in order to turn on pympler profiling for individual end points.

v1.0.11.6 - added safety for turning multiple processes on and off

16 Mar 14:24
885decd
Compare
Choose a tag to compare

In previous version if the memory profiler was running long in an ON position and a web server decided to bring a new process on line, the new process would default to OFF position. With toggling you would end up with new process being set in the opposite direction to the remainder of the processes. This made toggling unsafe and had to be replaced with definitive value setting with a named pipe per running process.

v1.0.11.5 - create mechanism to exclude entire packages from memory profiling

09 Mar 17:54
b3d9df3
Compare
Choose a tag to compare

The issue is that decorators for our bazman REST end point do not respond favorably to memory profiling. Somehow interaction with memory profiler consistently corrupts data on request and causes obscure REST errors. In order to be able to exclude memory profiling from entire packages I added a mechanism that allows user to import a single variable at init.py for the package and prevent every method decorated with @expose() to be permanently excluded from memory profiling.

v1.0.11.4 - added explicit omit memory profile flag

08 Mar 16:37
6866f96
Compare
Choose a tag to compare
Merge pull request #10 from ilyaGotfryd/NT-76-togglable-memory-profil…

v1.0.11.3 - correction of logging exception handler

02 Mar 15:39
585e855
Compare
Choose a tag to compare

Corrected logging exception handler for memory profiler.
Added fleunt-logger not to rely on it being deployed for our main product.