- For several modules, added exception trace information to improve
error logging in case of any exception
- Patch added for CegoQueryCache::addEntry, getNumUsed added to
search loop to find appropriate slot. This avoids some needless
assignments, since used entries cannot be assigned.
- Patch added CegoQueryCache::invalidate. For main loop, a delay
has been added, to give other threads the chance to claim the lock
December 02, 2024
We (Qt upstream) have released Qt 6.8.1 today. As a patch release,
Qt 6.8.1 does not introduce new features but contains more than 550 bug
fixes, security updates, and other improvements on top of Qt 6.8.0
release. See more information about the most important changes and bug
fixes from the Qt 6.8.1 release note.
Announcement: https://www.qt.io/blog/qt-6.8.1-released
Release note: https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.8.1/release-note.md
We (kde@) skipped shipping Qt 6.8.0 due to waiting for a compatible
version of PyQt to be released, but here are the announcements and
release notes from Qt 6.8.0.
Announcement: https://www.qt.io/blog/qt-6.8-released
Release note: https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/6.8.0/release-note.md
PySide6: Update to 6.8.0.2
PySide6 and its related components have been updated alongside the Qt
release for compatibility. Older versions will not build with Qt 6.8.x.
Announcement: https://www.qt.io/blog/qt-for-python-release-6.8
PyQt6: Update to 6.8.0
This release also introduces x11-toolkits/py-qt6-graphs, python bindings
for the Qt Graphs module. As with PySide6, older versions of PyQt6 will
not build with Qt 6.8.x.
Support tools like py-sip and py-qtbuilder have also been updated to their
latest versions.
Announcement: https://www.riverbankcomputing.com/news/PyQt_v6.8.0_Released
Special thanks to Kenneth Raplee for testing and to SponiX for providing
access to build hardware!
PR: 283290
Exp-run by: antoine (x2)
Active Record connects classes to relational database tables to establish an
almost zero-configuration persistence layer for applications. The library
provides a base class that, when subclassed, sets up a mapping between the new
class and an existing table in the database. In the context of an application,
these classes are commonly referred to as models. Models can also be connected
to other models; this is done by defining associations.
Active Record relies heavily on naming in that it uses class and association
names to establish mappings between respective database tables and foreign key
columns. Although these mappings can be defined explicitly, it's recommended to
follow naming conventions, especially when getting started with the library.
Active Model provides a known set of interfaces for usage in model classes. They
allow for Action Pack helpers to interact with non-Active Record models, for
example. Active Model also helps with building custom ORMs for use outside of
the Rails framework.
Active Model provides a default module that implements the basic API required to
integrate with Action Pack out of the box: ActiveModel::API.
- Patch for CegoFunction added.
For methods getReturnType, getReturnTypeLen and evelFieldValue
the following has been added : If proc object is getting used by
useObject, the following getProcedure call must be catched for
exception to unuse the object since _pProc is stiil null and the
object so is not unused by cleanup
Björn Lemke
Muhammad Moinur Rahman
Ruslan Makhmatkhanov
Yuri Victorovich
Oleksii Samorukov
Jochen Neumeister
Yasuhiro Kimura
Älven
Palle Girgensohn
Miroslav Lachman
Jesús Daniel Colmenares Oviedo
Jason E. Hale
Po-Chuan Hsieh
Jose Alonso Cardenas Marquez
Rene Ladan