Earlier this year, Elastic reignited the open-source licensing debate when it announced it would be changing its license model to better protect its open-source code. Over the last couple of years, a number of companies -- including Redis Labs, MongoDB, Cockroach Labs, and Confluent -- have been switching their open-source licenses to avoid what they … continue reading The post The battle of open-source licenses appeared first on SD Times.

Latest PECL Releases:skywalking 3.2.5 Fix the empty field bug in span refs for skywalking v6. mysqlnd_azure 1.0.3 - Remove the use of is_using_redirect flag. More strict validation and test cases with php built-in web server. rdkafka 4.0.3 BREAKING CHANGE: Since version 4.0, the client no longer polls for network events at shutdown (during object destructor). This behaviour didn't give enough control to the user in case of server issue, and could cause the script to hang while terminating. Starting from 4.0, programs MUST call flush() before shutting down, otherwise some messages and callbacks may be lost. Improvements Add partition check for offsetStore (#331, @nick-zh) Naming consistency for setting in tests (#339, @romainneutron) Bugfixes Fix headers containing null bytes (#338, @arnaud-lb, @dirx @nick-zh) Fix topic deconstruct for high level consumer (#333, @nick-zh) Documentation Fix doc example (#340, @Steveb-p) Remove outdated and duplicate examples (#341, @nick-zh) pq 2.1.7 * Fix PHP-7.4 compatibility zstd 0.8.0 - ztsd_uncompress may return a empty string oauth 2.0.5 * fix config.w32 (cmb) * fix 7.3 segfault (rlerdorf) * replace uint-uint32_t, ulong-zend_ulong (Jan-E) * handle cases where a passed in array might be a const (keyurdg) * Fix configure for recent cURL versions (cmb) * Bug #76722 cURL library headers not recognized on Debian 9 (js361014) gRPC 1.27.0 - gRPC Core 1.27.0 update mongodb 1.7.1 ** Bug * [PHPC-1551] - Building against system libraries fails couchbase 2.6.2 * fixed possible segfault in N1QL request * fixed windows build for PHP 7.4 * PCBC-646: Fixed issue with blank string decoding. mongodb 1.7.0 ** Bug * [PHPC-348] - Check for errors after calling bson_to_zval() * [PHPC-889] - BSON decoding errors for Javascript scopes only thrown at access time * [PHPC-1446] - Always enable TLS when any TLS option is specified * [PHPC-1453] - SRV record lookup fails if DNS response exceeds 1024 characters * [PHPC-1520] - Windows compiler warnings building extension with libmongocrypt * [PHPC-1526] - Forking session test has intermittent failures on SHARDED_CLUSTER_RS * [PHPC-1540] - Investigate segmentation fault when using keyVaultClient in AutoEncryptionOpts ** Epic [PHPC-1293] - Support Client-side Field Level Encryption (FLE) ** New Feature [PHPC-1230] - Support object cloning for BSON classes [PHPC-1462] - Support ability to pass hint to update [PHPC-1491] - Add ReadPreference::getModeString [PHPC-1496] - Support compiling with libmongocrypt [PHPC-1497] - Introduce new configure switch to use system libraries [PHPC-1498] - Handle autoEncryptionOpts in MongoDBDriverManager [PHPC-1499] - Add clientEncryption API [PHPC-1500] - Change serialisation of objects for client hash [PHPC-1539] - Create new exception classes for FLE ** Task [PHPC-952] - Refactor BSON type initiators for unserialization visitors [PHPC-1002] - Test regularly with C Driver release or release candidate [PHPC-1073] - Remove superfluous php_array_exists calls where possible [PHPC-1074] - Refactor php_phongo_bson_state struct initialization for debug output [PHPC-1269] - Document that BulkWrite instances may only be executed once [PHPC-1279] - Improve documentation for Cursor::isDead() [PHPC-1312] - Advise users to use 64-bit environments if possible [PHPC-1314] - Document that users may need to copy libsasl.dll to lib path for Windows installs [PHPC-1343] - Add test to catch inaccessible server when running tests [PHPC-1372] - Re-enable ARM64 builds in Evergreen matrix [PHPC-1424] - Inform users that mongodb.debug output contains sensitive information [PHPC-1426] - Update stubs for PhpStorm [PHPC-1430] - Deprecate obsolete driver options [PHPC-1438] - Expose more precise session state [PHPC-1445] - Make find commands for collecting libmongoc sources portable between Linux and macOS [PHPC-1449] - Resync bson-corpus array.json to fix duplicate test names [PHPC-1450] - Document rules by which TLS is implicitly enabled [PHPC-1461] - Remove Community zSeries From 4.0 testing [PHPC-1470] - Remove unnecessary timezone settings in tests [PHPC-1471] - Clean up reference handling in Javascript scope serialisation [PHPC-1472] - Prevent multiple exceptions from being thrown during manager serialisation [PHPC-1492] - Remove conditional EXPECTF patterns in UTCDateTime tests [PHPC-1532] - Document client-side encryption functionality [PHPC-1546] - Ensure Windows builds enable SASL and FLE ** Improvement [PHPC-870] - Consider using ZEND_HASH_FOREACH indirect macros for iteration [PHPC-966] - Explicitly initialize fields for internal class structs [PHPC-991] - Handle duplicates in URI options array [PHPC-1274] - Reset libmongoc client after forking to avoid interacting with parent resources in child processes [PHPC-1281] - Serialization support for ReadConcern, ReadPreference, and WriteConcern [PHPC-1284] - Driver session pools must be cleared after forking [PHPC-1347] - Do not allow empty string for replicaSet [PHPC-1391] - Prohibit starting a transaction for maxWireVersion < 7 [PHPC-1411] - Accept 64-bit integers for wTimeoutMS [PHPC-1418] - Test PHP 7.3 in Evergreen [PHPC-1439] - Expose transaction options on session object [PHPC-1459] - Add serialisation support for CursorId [PHPC-1521] - Only warn in config.w32 if SASL is enabled but not available [PHPC-1545] - Require object or array type for "kmsProviders" option

Of course, yes. With every plugin you install on your WordPress site, you are sure to slower down you website, even if that means a few milliseconds. However, the hard reality it, your WordPress site is nothing without plugins. In fact, WordPress sites can only co-exist with plugins by the side. But there are some common questions always asked here, How many plugins are actually required by my site? What will be the impact of too many plugins integrated with my site? To get the answer for above queries, you will surely need to read the entire discussion, and decide … Continue reading →Visit us at InstantShift.com

Brainstorm Blogpost ideas This is important. Why? Because it will elucidate two points: Do you have enough ideas for a blog article on this subject?... The post How To Ace Your Career As A Blogger appeared first on Web Development & Technology Resources.

Sergey Zhuk has a post to his site covering concurrency including some of the basic concepts and how promises and coroutines come in to play. What does concurrency mean? To put it simply, concurrency means the execution of multiple tasks over a period of time. PHP runs in a single thread, which means that at any given moment there is only one bit of PHP code that can be running. That may seem like a limitation, but it brings us a lot of freedom. We don't have to deal with all this complexity that comes with parallel programming and threaded environment. But at the same time, we have a different set of problems. We have to deal with concurrency. We have to manage and to coordinate it. He goes on to talk about parallel requests, cross-request needs and the requirement for coordination. He then covers the subject of promises, briefly defining it and giving an example of creating a basic promise in ReactPHP. Following this he talks about the other main topic of the article: using PHP generators along with parallel requests to only create the responses when yielded.

The complexity of today's distributed microservices applications makes it tough to track down the root cause when a problem occurs. The time-proven method of drilling down on monitoring dashboards and then digging into logs simply takes too long. Hunting through huge volumes of logs is tedious and interpreting them is difficult. It also requires an … continue reading The post Using GPT-3 for root cause incident summarization of incidents appeared first on SD Times.

Here are some advanced JavaScript techniques and tips all web developers should know. The post 6 Advanced JavaScript Concepts You Should Know appeared first on WebFX Blog.

Want to know which of the top blogging platforms you should consider using this year? Blogging is still one of the best ways to draw attention to your brand, generate thought leadership, and build your credibility. Research suggests that US internet users spend 3x more of their browsing time on blogs than on email. Additionally, […] The post Top Blogging Platforms Worth Considering in 2021 first appeared on Webdesigner Depot.

I love a good bug, especially ones that are initially hard to explain but then turn into forehead slapping moments - of course! There's a bug over on Github called Hysteresis effect on threadpool hill-climbing that is a super interesting read. Hill climbing is an algorithmic technique when you have a problem (a hill) and then you improve and improve (climb) until you have reached some maximum acceptable solution (reach the top). Sebastian, the OP of the bug, says there's a "Hysteresis effect" on the threadpool. "Hysteresis is the dependence of the state of a system on its history." Something weird is happening now because something happened before...but what was it? Sawtooth up and down graphs aren't THAT interesting...but look at the x-axis. This isn't showing minute by minute or even millisecond by millisecond ups and downs like you may have seen before. This x-axis uses months as its unit of measure. Read that again and drink it in. Things are cool in February until they are bad for weeks and then cool in March and it moves along a cycle. Not strictly the cycle of the moon but close. He's seeing the number of cores being used changing from month to month when using PortableThreadPool We have noticed a periodic pattern on the threadpool hill-climbing logic, which uses either n-cores or n-cores + 20 with an hysteresis effect that switches every 3-4 weeks. Did you know (I know because I'm old) that Windows 95, for a time, was unable to run longer than 49.7 days of runtime? If you ran it that long it would eventually crash! That's because there's 86M ms in a day, i.e. 1000 * 60 * 60 * 24 = 86,400,000 and 32 bits is 4,294,967,296 so 4,294,967,296 / 86,400,000 = 49.7102696 days! Kevin in the Github issues notes this as well: The whole period of square wave sounds an awful lot like it is around 49.7 days. That is how long it takes GetTickCount() to wrap around. On POSIX platforms the platform abstraction layer implements this, and the value returned for that is based not on uptime but on wall clock time, which matches with all machines changing on the same day. This 49.7 days number is well known as it's how long it take before GetTickCount() overflows/wraps. Kevin goes on to actually give the changeover dates which correspond to the graph! Thu Jan 14 2021 Sun Feb 07 2021 Thu Mar 04 2021 Mon Mar 29 2021 Fri Apr 23 2021 He then finds the code in PortableThreadPool.cs that explains the issue:private bool ShouldAdjustMaxWorkersActive(int currentTimeMs) { // We need to subtract by prior time because Environment.TickCount can wrap around, making a comparison of absolute times unreliable. int priorTime = Volatile.Read(ref _separated.priorCompletedWorkRequestsTime); int requiredInterval = _separated.nextCompletedWorkRequestsTime - priorTime; int elapsedInterval = currentTimeMs - priorTime; if (elapsedInterval >= requiredInterval) {... He says, and this is all Kevin: currentTimeMs is Environment.TickCount, which in this case happens to be negative. The if clause controls if the hill climbing is even run. _separated.priorCompletedWorkRequestsTime and _separated.nextCompletedWorkRequestsTime start out as zero on process start, and only get updated if the hill climbing code is run. Therefore, requiredInterval = 0 - 0 and elapsedInterval = negativeNumber - 0. This causes the if statement to becomeif (negativeNumber - 0 >= 0 - 0) which returns false, so the hill climbing code is not run, and therefore the variables never get updated, and remain zero. The native version of the thread pool code does all math with unsigned numbers which would avoid such a bug, and it's equivalent part is not even quite the same math in the first place. The easy fix here is probably to use unsigned arithmetic, but alternatively having the two fields get initialized to Environment.TickCount probably also work Back to me. Fabulous. The fix is to case the results to unsigned ints via (uint). Before:int requiredInterval = _separated.nextCompletedWorkRequestsTime - priorTime;int elapsedInterval = currentTimeMs - priorTime; After:uint requiredInterval = (uint)(_separated.nextCompletedWorkRequestsTime - priorTime);uint elapsedInterval = (uint)(currentTimeMs - priorTime); What an interesting and insidious bug! Bugs based on a time calculations can often show themselves later when view through a longer lens and scope of time...sometimes WAY longer than you'd expect. Sponsor: YugabyteDB is a distributed SQL database designed for resilience and scale. It is 100% open source, PostgreSQL-compatible, enterprise-grade, and runs across all clouds. Sign up and get a free t-shirt.(C) 2021 Scott Hanselman. All rights reserved.     

UserWay, an AI-powered web accessibility company, and ShortPoint, an intranet design software company, today announced their partnership in order to ensure SharePoint sites designed with ShortPoint are fully accessible and ADA compliant. UserWay's accessibility technology provides WCAG and ADA compliance for websites, resulting in a more accessible experience for blind and visually impared users as … continue reading The post SD Times news digest: UserWay and ShortPoint announce partnership; Code Ninjas and Microsoft MakeCode collaboration; SQLite 3.37 release appeared first on SD Times.