You are here

Feed aggregator

"Egy modern 64k intro és a mögötte rejlő technológiák"

HUP.hu - 2021, May 12 - 13:52

Szokásostól eltérően péntek 19:00-tól online meetup, Gargaj (@conspiracyhu) mesél nekünk: Tiszta Lappal - Egy modern 64k intro és a mögötte rejlő technológiák https://t.co/JUnpBQGAKq

— H.A.C.K. Budapest (@hackerspacebp) May 12, 2021

A Hackerspace Budapest Online meetupja 2021. május 14-én a fenti témában:

Categories: Informatika

NomadBSD 130R-20210508

HUP.hu - 2021, May 12 - 09:50

We're happy to announce a new release of NomadBSD. This is the first version based on FreeBSD 13. Find the release notes on our website: https://t.co/orp3CcqZw5

— NomadBSD (@NomadBSD) May 11, 2021

Megjelent a NomadBSD első FreeBSD 13-ra épülő kiadása.

Változások az v1.4 óta:

Categories: Informatika

Érkezik a linuxos eBPF Windowsra

HUP.hu - 2021, May 12 - 07:56

We're working on bringing eBPF to Windows: https://t.co/DFm0zVHee4

— Mark Russinovich (@markrussinovich) May 10, 2021

Mark Russinovich jelentette be a Twitteren minap, hogy érkezik a linuxos világból ismert eBPF Windowsra. Mi az az eBPF?

eBPF is a revolutionary technology that can run sandboxed programs in the Linux kernel without changing kernel source code or loading kernel modules.
Categories: Informatika

Forráskóddal együtt megjelent a 7-Zip 21.02 Alpha

HUP.hu - 2021, May 11 - 09:10

Nemrég megjelent a 7-Zip archiváló első hivatalos linuxos kiadása. Akkor kritikaként fogalmazódott meg, hogy nem volt elérhető a forráskódja. Most megjelent a 21.02-es verzió alpha kiadása, amivel forráskódcsomag is érkezett:

Újdonságok:

Categories: Informatika

DragonFly BSD 6.0

HUP.hu - 2021, May 11 - 08:02

DragonFly 6.0 is out!: DragoFly 6.0 is tagged and ready for download. There's ISO images and of c... https://t.co/7ZnPzEjM7n

— DragonFly BSD (@dragonflybsd) May 10, 2021

A DragonFly BSD projekt kiadta a DragonFly BSD 6.0-s kiadását. Telepítéshez elérhetők ISO lemezképfájlok, illetve upgrade is végezhető meglevő telepítésen a kiadási oldalon található instrukciók alapján.

Főbb változások:

Categories: Informatika

FreeDOS 1.3 RC4

HUP.hu - 2021, May 11 - 07:42

Have you tried the new FreeDOS 1.3 RC4? It's great!

Let's take a look:https://t.co/LmysSWPLj5

— FreeDOS (@FreeDOS_Project) May 10, 2021

Tesztelhető a FreeDOS 1.3 negyedik kiadásra jelölt verziója.

Categories: Informatika

OpenIndiana Hipster 2021.04

HUP.hu - 2021, May 10 - 15:55

OpenIndiana Hipster 2021.04 - https://t.co/IuXNWDQnO6 pic.twitter.com/zSEyqgL6rP

— HUP (@huphu) May 10, 2021

Megjelent az OpenSolaris folytatásának tekinthető, iilumos alapokra építkező OpenIndiana legújabb kiadása, az OpenIndiana Hipster 2021.04:

Categories: Informatika

Linus Torvalds: Linux 5.13-rc1

HUP.hu - 2021, May 10 - 15:44

5.13-rc1: mainline Version: 5.13-rc1 (mainline) Released: 2021-05-09 Source: linux-5.13-rc1.tar.gz Patch: full https://t.co/92ScQXt9Ou #linux #kernel

— Linux Kernel Releases (@LinuxKReleases) May 9, 2021

Eltelt két hét az 5.12-es kernel kiadása óta, így a beolvasztási időablak (merge window) bezárult, ráléptünk az -rc kernelek szegélyezte stabilizációs útra, amelynek a végcélja várhatóan a hetedik -rc kiadását követő 5.13-as kernelkiadás lesz. Részletek Linus bejelentésében.

Categories: Informatika

Elsődleges számítógépemben ... fizikai memória (RAM) található

HUP.hu - 2021, May 10 - 14:34

Nem telefonom, nem okostelefon, nem tablet. Desktop PC, laptop, notebook ... Válaszd a legközelebb eső opciót!

Categories: Informatika

Freespire 7.5

HUP.hu - 2021, May 10 - 14:20

Today we have released Freespire 7.5 for our great community of users. A lot of work has been put into this release to make it a fantastic FOSS desktop @rjdohnert @LinspireLinux @akai11nj #freespire #opensource #Linux #unix #debian #ubuntu #linuxdesktophttps://t.co/mi7T4rdH8M pic.twitter.com/ZaAzgQGeqO

— Freespire (@FreespireOSS) May 9, 2021

Megjelent az Linspire-leszármazott Linux disztribúció, a Freespire 7.5-ös kiadása.

Főbb jellemzői:

Categories: Informatika

VLC 3.0.13

HUP.hu - 2021, May 10 - 11:51

VLC 3.0.13 is out!
Very minor release fixing some HLS, VP9, WebVTT and TS streams. It adds NFSv4 and improves Windows rendering and bluray playback.
Finally, it fixes concerning security issues.https://t.co/TLiWxOyDsL
Security Bulletin: https://t.co/YgrA0FlANq

— VideoLAN (@videolan) May 10, 2021

Nagyon kicsi kiadás, NFSv4 támogatás, némi HLS, VP9, WebVTT és TS stream javítás, valamint biztonsági javítás kapott helyet benne:

Categories: Informatika

Mennyire vagy elégedett a fizetéseddel?

HUP.hu - 2021, May 10 - 10:58

Korábbi szavazás apropóján felmerült, hogy mennyire is vagyunk elégedettek a fizetéseinkkel? Ennek felmérésére egy komolyabb kérdőívre lenne szükség, hogy mérhető legyen az összes fizetést befolyásoló tényező. Sajnos a HUP nem támogat ilyent, így elsőre egyszerűbb formában vizsgálnám meg a kérdést. Példának okáért, mi az összefüggés a munkavállaló képzettsége és a fizetésével való elégedettsége között?

Categories: Informatika

PostgreSQL Weekly News - May 9, 2021

PostreSQL.org - 2021, May 10 - 02:00
PostgreSQL Weekly News - May 9, 2021

Person of the week: https://postgresql.life/post/dave_page/

PostgreSQL Product News

pgBackRest 2.33, a backup and restore system for PostgreSQL, released. https://pgbackrest.org/release.html#2.33

pg_probackup 2.4.15, a utility to manage backup and recovery of PostgreSQL database clusters, released. https://github.com/postgrespro/pg_probackup/releases/tag/2.4.15

PostgreSQL Jobs for May

https://archives.postgresql.org/pgsql-jobs/2021-05/

PostgreSQL in the News

Planet PostgreSQL: https://planet.postgresql.org/

PostgreSQL Weekly News is brought to you this week by David Fetter

Submit news and announcements by Sunday at 3:00pm PST8PDT to david@fetter.org.

Applied Patches

Alexander Korotkov pushed:

Amit Kapila pushed:

Peter Eisentraut pushed:

Tom Lane pushed:

  • Fix performance issue in new regex match-all detection code. Commit 824bf7190 introduced a new search of the NFAs generated by regex compilation. I failed to think hard about the performance characteristics of that search, with the predictable outcome that it's bad: weird regexes can trigger exponential search time. Worse, there's no check-for-interrupt in that code, so you can't even cancel the query if this happens. Fix by introducing memo-ization of the search results, so that any one NFA state need be examined in detail just once. This potentially uses a lot of memory, but we can bound the memory usage by putting a limit on the number of states for which we'll try to prove match-all-ness. That is sane because we already have a limit (DUPINF) on the maximum finite string length that a matchall regex can match; and patterns that involve much more than DUPINF states would probably exceed that limit anyway. Also, rearrange the logic so that we check the basic is-the-graph- all-RAINBOW-arcs property before we start the recursive search to determine path lengths. This will ensure that we fall out quickly whenever the NFA couldn't possibly be matchall. Also stick in a check-for-interrupt, just in case these measures don't completely eliminate the risk of slowness. Discussion: https://postgr.es/m/3483895.1619898362@sss.pgh.pa.us https://git.postgresql.org/pg/commitdiff/f68970e33f4dc48094c24c78c452ad730ae9ae12

  • Disable cache clobber to avoid breaking postgres_fdw termination test. Commit 93f414614 improved a pre-existing test case so that it would show whether or not termination of the "remote" worker process happened. This soon exposed that, when debug_invalidate_system_caches_always (nee CLOBBER_CACHE_ALWAYS) is enabled, no such termination occurs. That's because cache invalidation forces postgres_fdw connections to be dropped at end of transaction, so that there's no worker to terminate. There's a race condition as to whether the worker will manage to get out of the BackendStatusArray before we look, but at least on buildfarm member hyrax, it's failed twice in two attempts. Rather than re-lobotomizing the test, let's fix this by transiently disabling debug_invalidate_system_caches_always. (Hooray for that being just a GUC nowadays, rather than a compile-time option.) If this proves not to be enough to make the test stable, we can do the other thing instead. Discussion: https://postgr.es/m/3854538.1620081771@sss.pgh.pa.us https://git.postgresql.org/pg/commitdiff/1273a15bf91fa322915e32d3b6dc6ec916397268

  • Doc: improve and centralize the documentation for OID alias types. Previously, a lot of information about type regclass existed only in the discussion of the sequence functions. Maybe that made sense in the beginning, because I think originally those were the only functions taking regclass. But it doesn't make sense anymore. Move that material to the "Object Identifier Types" section in datatype.sgml, generalize it to talk about the other reg* types as well, and add more examples. Per bug #16991 from Federico Caselli. Discussion: https://postgr.es/m/16991-bcaeaafa17e0a723@postgresql.org https://git.postgresql.org/pg/commitdiff/f33a178a34809a2bae7a5f4c00984d87771f4204

  • Doc: update RELEASE_CHANGES checklist. Update checklist to reflect current practice: The platform-specific FAQ files are long gone. We've never routinely updated the libbind code we borrowed, either, and there seems no reason to start now. Explain current practice of running pgindent twice per cycle. Discussion: https://postgr.es/m/4038398.1620238684@sss.pgh.pa.us https://git.postgresql.org/pg/commitdiff/e8ce68b0b9ae2757c6153a88bf869904d2d5ac0b

  • Doc: trivial wording adjustment. Improve self-referential foreign key example, per suggestion from David Johnston. Discussion: https://postgr.es/m/CAKFQuwZTke7+HUn4YUGqu2+gAPi4Cy18TXMrg_Z5nADkxfPNMw@mail.gmail.com https://git.postgresql.org/pg/commitdiff/c38cadc0907a8d071b043b2b32b83efa09db38ea

  • Doc: copy-editing for debug_invalidate_system_caches_always description. I came to fix "useful only useful", but the more I looked at the text the more things I thought could be improved. https://git.postgresql.org/pg/commitdiff/f9b809e7fbe36cd3fe1ce33edb277288a31da386

  • Sync guc.c and postgresql.conf.sample with the SGML docs. It seems that various people have moved GUCs around in the config.sgml listing without bothering to make the code agree. Ensure that the config_group codes assigned to GUCs match where they are listed in config.sgml. Likewise ensure that postgresql.conf.sample lists GUCs in the same sub-section and same ordering as they appear in config.sgml. (I've got some doubts about some of these choices, but for the purposes of this patch, we'll treat config.sgml as gospel.) Notably, this requires adding a WAL_RECOVERY config_group value, because 1d257577e didn't. As long as we're renumbering that enum anyway, let's take out the values corresponding to major groups that are divided into sub-groups. No GUC should be assigned to the major group itself, so those values just create a temptation to do the wrong thing, while adding work for translators. In passing, adjust the short_desc strings for PRESET_OPTIONS GUCs to uniformly use the phrasing "Shows XYZ.", removing the impression some of these strings left that you can set the value. While some of these errors are old, no back-patch, as changing the contents of the pg_settings view in stable branches seems more likely to be seen as a compatibility break than anything helpful. Bharath Rupireddy, Justin Pryzby, Tom Lane Discussion: https://postgr.es/m/16997-ff16127f6e0d1390@postgresql.org Discussion: https://postgr.es/m/20210413123139.GE6091@telsasoft.com https://git.postgresql.org/pg/commitdiff/a55a98477b690dedb9b4368d7e5710c8e7fa534e

Robert Haas pushed:

Bruce Momjian pushed:

Álvaro Herrera pushed:

Andres Freund pushed:

Peter Geoghegan pushed:

Thomas Munro pushed:

  • Revert per-index collation version tracking feature. Design problems were discovered in the handling of composite types and record types that would cause some relevant versions not to be recorded. Misgivings were also expressed about the use of the pg_depend catalog for this purpose. We're out of time for this release so we'll revert and try again. Commits reverted: 1bf946bd: Doc: Document known problem with Windows collation versions. cf002008: Remove no-longer-relevant test case. ef387bed: Fix bogus collation-version-recording logic. 0fb0a050: Hide internal error for pg_collation_actual_version(<bad OID>). ff942057: Suppress "warning: variable 'collcollate' set but not used". d50e3b1f: Fix assertion in collation version lookup. f24b1569: Rethink extraction of collation dependencies. 257836a7: Track collation versions for indexes. cd6f479e: Add pg_depend.refobjversion. 7d1297df: Remove pg_collation.collversion. Discussion: https://postgr.es/m/CA%2BhUKGLhj5t1fcjqAu8iD9B3ixJtsTNqyCCD4V0aTO9kAKAjjA%40mail.gmail.com https://git.postgresql.org/pg/commitdiff/ec48314708262d8ea6cdcb83f803fc83dd89e721

  • Doc: Update notes about libc collation versions. The per-index collation version tracking feature was reverted, but we still have the ability to ask Windows (352f6f2d) and FreeBSD (ca051d8b) for collation versions to store in pg_collation.collversion. So, from the reverted patch, take a few words of documentation about libc on all three supported OSes to replace the pre-existing note that mentioned only glibc. Discussion: https://postgr.es/m/CA%2BhUKGLhj5t1fcjqAu8iD9B3ixJtsTNqyCCD4V0aTO9kAKAjjA%40mail.gmail.com https://git.postgresql.org/pg/commitdiff/b65431ca5e12a475ba7cf68afb63edb070c2ce08

Tomáš Vondra pushed:

Andrew Dunstan pushed:

Michaël Paquier pushed:

David Rowley pushed:

  • Move memory accounting Asserts for Result Cache code. In 9eacee2e6, I included some code to verify the cache's memory tracking is correct by counting up the number of entries and the memory they use each time we evict something from the cache. Those values are then compared to the expected values using Assert. The problem is that this requires looping over the entire cache hash table each time we evict an entry from the cache. That can be pretty expensive, as noted by Pavel Stehule. Here we move this memory accounting checking code so that we only verify it on cassert builds once when shutting down the Result Cache node. Aside from the performance increase, this has two distinct advantages: 1) We do the memory checks at the last possible moment before destroying the cache. This means we'll now catch accounting problems that might sneak in after a cache eviction. 2) We now do the memory Assert checks when there were no cache evictions. This increases the coverage. One small disadvantage is that we'll now miss any memory tracking issues that somehow managed to resolve themselves by the end of execution. However, it seems to me that such a memory tracking problem would be quite unlikely, and likely somewhat less harmful if one were to exist. In passing, adjust the loop over the hash table to use the standard simplehash.h method of iteration. Reported-by: Pavel Stehule Discussion: https://postgr.es/m/CAFj8pRAzgoSkdEiqrKbT=7yG9FA5fjUAP3jmJywuDqYq6Ki5ug@mail.gmail.com https://git.postgresql.org/pg/commitdiff/92c4c269d24d016c19858a21347ff25a7de1f486
Pending Patches

Aleksander Alekseev sent in another revision of a patch to allow CustomScan nodes to signal projection support.

Melanie Plageman sent in another revision of a patch to avoid an immediate fsync for just-built indexes.

Dilip Kumar sent in two revisions of a patch to add TOAST compression method options.

Vigneshwaran C sent in four more revisions of a patch to identify missing publications from publisher during CREATE/ALTER SUBSCRIPTION.

Bertrand Drouvot sent in a patch to intended to fix a bug that manifested as pg_upgrade can result in early wraparound on databases with high transaction load by exactly copying the oldestXid limit from the source database.

Bertrand Drouvot sent in a patch to intended to fix a bug that manifested as orphaned dependencies by adding a new catalog snapshot is DirtyCatalogSnapshot controlled by a new UseDirtyCatalogSnapshot variable, and using it to check for in-flight dependencies and get the objects' description to generate the error messages.

Thomas Munro sent in another revision of a patch to add a new TAP test under src/test/recovery to run the standard regression tests with a streaming replica replaying the WAL. This provides a basic workout for WAL decoding and redo code.

Mark Dilger sent in two revisions of a patch to extend amcheck to check TOAST size and compression.

Jeff Davis sent in a patch to bound ItemPointers in table AMs in a way that other parts of the system expect.

Dilip Kumar and Kyotaro HORIGUCHI traded patches to intended to fix a bug that manifested as a race condition in recovery.

Craig Ringer sent in another revision of a patch to make Valgrind runs simpler with make USE_VALGRIND=1.

David Fetter sent in a patch to clarify some column descriptions in pg_constraint.

Vigneshwaran C sent in two more revisions of a patch to print the backtrace of a specified postgres process.

Craig Ringer sent in a patch to emit dummy statements for probes.d probes when disabled.

Jeff Davis sent in another revision of a patch to implement ALTER TABLE ... SET ACCESS METHOD.

Amit Langote sent in a patch to clarify the documentation of ALTER TABLE ... DETACH PARTITION CONCURRENTLY.

Etsuro Fujita sent in a patch to fix EXPLAIN ANALYZE for async capable nodes.

Etsuro Fujita sent in a patch to describe the way asynchronous execution works for FDWs.

Nitin Jadhav sent in a patch to implement list partitioning for multiple columns.

Yugo Nagata sent in another revision of a patch to implement incremental view maintenance.

Konstantin Knizhnik sent in another revision of a patch to remove unneeded self-joins.

Andrey Borodin sent in another revision of a patch to speed up GiST index builds.

Etsuro Fujita sent in a patch to fix an infelicity between inherited UPDATE/DELETE and async execution by modifying postgresPlanDirectModify() so that it clears the async-capable flag if it is set.

James Coleman sent in a patch to parallelize correlated subqueries that execute within each worker.

Jeff Janes sent in a patch to add configure cache checkpoints before fatal checks.

Hou Zhijie sent in another revision of a patch to fix EXPLAIN's information about FDW batch inserts.

Erik Rijkers and Alexander Korotkov traded patches to improve the example in JSON path queries to highlight what's actually happening.

Bruce Momjian sent in another revision of a patch to fix a misbehavior in interval arithmetic.

Hou Zhijie sent in a patch to fix a bug where there was an inaccurate error message when fdw batch_size was set to 0.

David Rowley sent in another revision of a patch to speed up NOT IN() with a set of Consts.

Andrew Dunstan sent in another revision of a patch to implement the JSON_TABLE part of SQL/JSON.

Andrew Dunstan sent in another revision of a patch to implement the functions from SQL/JSON.

Tom Lane sent in a patch to make a binary-coercible C function in order to reduce opr_sanity test's runtime under CLOBBER_CACHE_ALWAYS.

David Rowley sent in a patch to only validate resultcache memory on plan shutdown.

Vigneshwaran C sent in a patch to correct the data type for the logical replication message formats.

Categories: Informatika

Gyakorlatilag a windowsos verzióval azonos sebességgel fut a Cyberpunk 2077 Linuxon

HUP.hu - 2021, May 9 - 08:33

https://t.co/zeO2pd7TM7

99% of native perf in Cyberpunk 2077 from the graph at the end, not bad. Need to look at loading times, though.

— Pierre-Loup Griffais (@Plagman2) May 8, 2021

Ez derül ki Pierre-Loup Griffais, a Valve fejlesztőjének tweetjéből ...

Videó:

Categories: Informatika

Hamarosan érkezik a DragonFly BSD 6.0.0

HUP.hu - 2021, May 7 - 16:19

DragonFly 6.0 soon: There's only been one issue found in the release candidate so far. It's fi... https://t.co/SsppVsvIPw

— DragonFly BSD (@dragonflybsd) May 7, 2021
Categories: Informatika

[Video] Docker Compose élesben: mire figyelj?

HUP.hu - 2021, May 7 - 16:03

Gémes Tamás (Aggreg8.io)

A Dockert és a Docker-compose-t sokan használják microservice rendszerek fejlesztésére, hisz gyorsan összehuzalozhatók vele a különféle előrecsomagolt, akár Docker Hubról összeollózott szolgáltatások. De mi a teendő, ha a compose-t élesben akarjuk használni? Ha több környezetünk is van, developer, QA, UAT, production környezetek is? Hogyan kezeljük a környezetek közötti különbségeket, beleértve a különféle konfigurációkat, titkos kulcsokat, volume-okat? Hogyan érjük el, hogy a rendszerünk a lehető legkisebb leállással frissíthető legyen, figyelembe véve a startup és shutdown dependenciákat is? Hogyan tudunk különféle logging drivereket használni, logokat rotálni? Hogyan monitorozzuk a konténereket? Mi a helyzet, ha egy konténerünk leáll az éjszaka közepén? Hogyan érjük el, hogy egy túlszaladt konténer ne rántsa magával az egész szervert? A fejlesztői közösségben az elmúlt években azt már sokan elfogadták, hogy a Docker és a konténerek nem csak fejlesztésre, hanem éles üzemeltetésre is alkalmas eszközök. Az előadásban azt szeretném bemutatni, hogy nem szükséges mindjárt orkesztrációs technológiában gondolkodni élesen sem (pl. Kubernetes, Swarm). A Docker-compose egy középutas megoldásként rengeteg olyan eszközt ad a kezünkbe, amellyel infrastructure-as-code filozófia mentén egy közepesen bonyolult rendszert a Kubernetes komplexitás magunkra vétele nélkül is üzemeltethetünk. Állítom mindezt úgy, hogy startupunkban mind Kubernetest, mind Docker-compose-t használunk éles környezetek üzemeltetésére több éve.

Categories: Informatika

PHP 8.0.6 Released!

PHP.net - 2021, May 6 - 15:41
Categories: Informatika

PHP 7.4.19 Released!

PHP.net - 2021, May 6 - 12:12
Categories: Informatika

drupal 9.2.0-alpha1

Drupal.org - 2021, May 6 - 10:50

This is an alpha release for the next minor (feature) release of Drupal 9. Alphas are good testing targets for developers and site builders who are comfortable reporting (and where possible, fixing) their own bugs. Alpha releases are not recommended for non-technical users, nor for production websites. More information on alpha releases.

This minor release provides new improvements and functionality without breaking backward compatibility (BC) for public APIs. Note that there may be changes in internal APIs and experimental modules that require updates to contributed and custom modules and themes per Drupal core's backwards compatibility and experimental module policies.

Drupal 9.2.x contains new features, and should be the target for new site development. Drupal 8.9.x will continue to have security support until November 2021. Drupal 9.1.x will continue to have security support until December 2021. Security support for 9.0.x ends with the release of 9.2.0 on June 16.

Regardless of which version you choose now, features will only be added to Drupal 9 minor releases, so plan to adopt Drupal 9 this year so that you can easily update to Drupal 9.2 and later.

Beta testing program

The Drupal Association and the Drupal core maintainers are partnering with agencies and site owners in an official beta testing program for Drupal core minor releases. The program aims to identify and minimize regressions in minor releases. Participating in the program is a way to contribute to the Drupal project and will be credited accordingly.

Important update information Updating from Drupal 8

For information on updating from Drupal 8 to Drupal 9, see Upgrading a Drupal 8 site to Drupal 9.

Sites on 8.7 or earlier must update to either 8.8 or 8.9 before updating to Drupal 9 as all Drupal 8 update functions from before Drupal 8.8.0-rc1 were removed from Drupal 9. We recommend updating to 8.9.x, as well as updating all contributed modules, before updating to any Drupal 9 release.

Note: The migration paths from Drupal 6 and Drupal 7 to Drupal 9 will remain supported throughout Drupal 9's release cycle.

Upgrading from Drupal 7

Drupal 7 users can continue to migrate to Drupal 8.9, or 9.2 directly. The upgrade path for multilingual sites is stable in both Drupal 8 and 9.

Important changes for this release Changes to site-owner-managed files
  • The web.config file used by Microsoft's IIS server has been updated to remove unnecessary configuration. The commented out Erase HTTP_PROXY rule has been removed. PHP 7.3 and up is not vulnerable and this rule can be removed if you have enabled it.
Other
  • Drupal now uses PHPs built-in session generation. The change record details how custom and contributed code that relies on the session ID should be updated.
  • Configuration files with multi-line strings will be exported using Symfony's multi-line literal block formatting option, improving readability and diffs. This will mean a configuration diff the first time a configuration file is re-exported.
  • If you limit allowed extensions and want dangerous files to be uploaded and renamed, you must explicitly allow txt file uploads. This is mandated when configuring file fields through the user interface.
  • Views renamed the default display from "Master" to "Default". This does not affect existing Views, only ones created after this change. Additionally the setting to hide/show the default display had its machine name changed from ui.show.master_display to ui.show.default_display. Review the change record for more information.
  • Drupal's README now focuses on shepherding new contributors into the Drupal ecosystem and uses the Markdown format. The usage information previously contained in the README.txt file has been extracted to a newly created USAGE.txt file in the core directory. Sites that are using the drupal/core-composer-scaffold plugin to exclude README.txt should update their configuration to exclude README.md instead.
Dependency updates Deprecated, changed, and removed dependencies
  • The Goutte testing browser has been deprecated and replaced with a new mink driver client, using Guzzle. This should not require any changes to browser tests unless you are interacting with specific Goutte features. Review the change record on the Goutte driver replacement for more information.
  • Drupal has replaced the behat/mink-browserkit-driver dependency with friends-of-behat/mink-browserkit-driver for PHP 8 and Symfony 5 compatibility.
  • The tabbable library has been added to replace the functionality provided by for jQuery UI's:tabbable selector. A shim has been provided so all existing of uses of the :tabbable selector now use tabbable to query tabbable elements.
  • . See the change record for more information.

Added dependencies
  • The core/once library, a standalone library that offers the same benefits as core/jquery.once but without the jQuery dependency, has been added to Drupal core.
Updated dependencies
  • #3187025: Update dependencies for Drupal 9.2
    +------------------------------+---------+---------+
    | Production Changes | From | To |
    +------------------------------+---------+---------+
    | composer/semver | 3.2.2 | 3.2.4 |
    | egulias/email-validator | 2.1.22 | 2.1.24 |
    | laminas/laminas-stdlib | 3.3.0 | 3.3.1 |
    | symfony/console | v4.4.16 | v4.4.17 |
    | symfony/debug | v4.4.16 | v4.4.17 |
    | symfony/dependency-injection | v4.4.16 | v4.4.17 |
    | symfony/error-handler | v4.4.16 | v4.4.17 |
    | symfony/event-dispatcher | v4.4.16 | v4.4.17 |
    | symfony/http-foundation | v4.4.16 | v4.4.17 |
    | symfony/http-kernel | v4.4.16 | v4.4.17 |
    | symfony/process | v4.4.16 | v4.4.17 |
    | symfony/routing | v4.4.16 | v4.4.17 |
    | symfony/serializer | v4.4.16 | v4.4.17 |
    | symfony/translation | v4.4.16 | v4.4.17 |
    | symfony/validator | v4.4.16 | v4.4.17 |
    | symfony/yaml | v4.4.16 | v4.4.17 |
    +------------------------------+---------+---------+

    +------------------------------------+---------+---------+
    | Dev Changes | From | To |
    +------------------------------------+---------+---------+
    | composer/composer | 2.0.2 | 2.0.8 |
    | composer/spdx-licenses | 1.5.4 | 1.5.5 |
    | composer/xdebug-handler | 1.4.4 | 1.4.5 |
    | doctrine/instantiator | 1.3.1 | 1.4.0 |
    | drupal/coder | 8.3.10 | 8.3.11 |
    | easyrdf/easyrdf | 1.0.0 | 1.1.1 |
    | myclabs/deep-copy | 1.10.1 | 1.10.2 |
    | phar-io/manifest | 1.0.3 | 2.0.1 |
    | phar-io/version | 2.0.1 | 3.0.3 |
    | phpunit/php-code-coverage | 7.0.10 | 7.0.14 |
    | phpunit/php-file-iterator | 2.0.2 | 2.0.3 |
    | phpunit/php-timer | 2.1.2 | 2.1.3 |
    | phpunit/php-token-stream | 3.1.1 | 4.0.4 |
    | phpunit/phpunit | 8.5.8 | 8.5.13 |
    | sebastian/code-unit-reverse-lookup | 1.0.1 | 1.0.2 |
    | sebastian/comparator | 3.0.2 | 3.0.3 |
    | sebastian/diff | 3.0.2 | 3.0.3 |
    | sebastian/environment | 4.2.3 | 4.2.4 |
    | sebastian/exporter | 3.1.2 | 3.1.3 |
    | sebastian/global-state | 3.0.0 | 3.0.1 |
    | sebastian/object-enumerator | 3.0.3 | 3.0.4 |
    | sebastian/object-reflector | 1.1.1 | 1.1.2 |
    | sebastian/recursion-context | 3.0.0 | 3.0.1 |
    | sebastian/resource-operations | 2.0.1 | 2.0.2 |
    | sebastian/type | 1.1.3 | 1.1.4 |
    | seld/jsonlint | 1.8.2 | 1.8.3 |
    | sirbrillig/phpcs-variable-analysis | v2.9.0 | v2.10.0 |
    | symfony/browser-kit | v4.4.16 | v4.4.17 |
    | symfony/css-selector | v4.4.16 | v4.4.17 |
    | symfony/dom-crawler | v4.4.16 | v4.4.17 |
    | symfony/filesystem | v4.4.16 | v4.4.17 |
    | symfony/finder | v4.4.16 | v4.4.17 |
    | symfony/lock | v4.4.16 | v4.4.17 |
    +------------------------------------+---------+---------+

  • ChromeDriver has been updated from 86.0.0 to 87.0.5.
  • Modernizr has been updated to v3.11.7
  • Underscore.js has been updated to 1.13.1
Changes to coding standards

The following coding standards checks have been enabled in core:

Drupal.Semantics.RemoteAddress Drupal.Classes.PropertyDeclaration Drupal.Commenting.DocComment.ParamGroup Generic.Formatting.DisallowMultipleStatements Squiz.WhiteSpace.ScopeKeywordSpacing Drupal.Commenting.DocCommentAlignment Drupal.Commenting.FunctionComment.ParamMissingDefinition Drupal.Commenting.FunctionComment.InvalidTypeHint Drupal.Commenting.FunctionComment.IncorrectTypeHint Drupal.Commenting.HookComment Drupal.Classes.UseGlobalClass Drupal.Commenting.DocComment.TagGroupSpacing Drupal.Commenting.DocComment.ShortFullStop Known issues

Search the issue queue for known issues.

All changes since 9.1.0

https://www.drupal.org/project/issues/search/drupal?project_issue_follow...

Release type: Bug fixesNew features
Categories: Informatika

pg_probackup 2.4.15 has been released

PostreSQL.org - 2021, May 6 - 02:00

New features:

  • Incremental backup now detects timeline switch automatically, using the replication protocol TIMELINE_HISTORY command. Proposed by Alex Ignatov
  • --no-validate and --no-sync flags are now usable in merge or retention merge operations.

Bugfixes:

  • Fix integer overflow of variable storing the offset of page header map. Reported by @sms1222
  • Fix broken backward compatibility for backups of versions 2.0.22, 2.0.24 and 2.0.25. Affected version: 2.4.10. Reported by @shab2
  • Do not delete invalid full backups within retention redundancy range. Reported by @triwada
  • Correctly handle backups with empty backup.control. Reported by Mikhail Grigorev
  • Empty WAL .history files are now handled correctly. Reported by Denis Podolsky
  • Do no report meaningless timestamp when deleting backup without valid "recovery-time" attribute. Reported by Roman Zharkov
  • Detect failure in WAL streaming correctly and report it as soon as possible. Reported by Yuri Kurenkov
  • Do sync and rename when writing to configuration file pg_probackup.conf
  • More robust parsing of tablespace_map content. Reported by Vasiliy Puchkov

pg_probackup is a utility to manage backup and recovery of PostgreSQL database cluster. It is designed to perform periodic full and incremental page-level backups of the PostgreSQL instance that enable you to restore the server in case of a failure.

Categories: Informatika

Pages

Theme by me