? New translations for FirebaseUI for FlutterThe latest releaseof the FlutterFire libraries adds Spanish, French, and Arabic resource stringsto the Authentication UI widgets. There are also many other fixes in thisFlutterFire release, so be sure to upgrade.
? New Performance Monitoring dashboardThe Firebase Performance Monitoringdashboard nowhas completely updated metrics views and a brand new table where you can viewand sort performance traces for your apps. Performance data now also shows up within minutes, giving you much fasterinsight into how your users are experiencing your app.
The npm package @babel/runtime, which is depended on by most Meteorapps, introduced a breaking change in version 7.0.0-beta.56 with theremoval of the @babel/runtime/helpers/builtin directory. While thischange has clear benefits in the long term, in the short term it hasbeen disruptive for Meteor 1.7.0.x applications that accidentallyupdated to the latest version of @babel/runtime. Meteor 188.8.131.52 is apatch release that provides better warnings about this problem, andensures newly created Meteor applications do not use 7.0.0-beta.56.PR #10134
The accounts-facebook and facebook-oauth packages have been updated touse the v2.9 of the Facebook Graph API for the Login Dialog since the v2.2version will be deprecated by Facebook in July. There shouldn't be a problemregardless since Facebook simply rolls over to the next active version(v2.3, in this case) however this should assist in avoiding deprecationwarnings and should enable any new functionality which has become available.PR #8858
coll.insert() now uses a faster (but cryptographically insecure)algorithm to generate document IDs when called outside of a methodand an _id field is not explicitly passed. With this change, thereare no longer two algorithms used to generate documentIDs. Random.id() can still be used to generate cryptographicallysecure document IDs. #5161
04:02 pm (IST): Nvidia staff member confirmed that the issue where the sound disappears when connected to Bluetooth after the latest update is a known issue. And also provided a temporary workaround that the affected users can try.
The flatpak build is new and has known limitations, though it will likely provide faster updates, following GIMP releases closely. Therefore choose your installation medium according to your needs.
Among the visible fixes, this version improves the _destSize() variant, an advanced API which reverses the logic by targeting an a-priori compressed size and trying to shove as much data as possible into the target budget. The high compression variant LZ4_compress_HC_destSize() would miss some important opportunities in highly compressible data, resulting in less than optimal compression (detected by @hsiangkao). This is fixed in this version. Even the "fast" variant receives some gains (albeit very small).Also, the corresponding decompression function, LZ4_decompress_safe_partial(), officially supports a scenario where the input (compressed) size is unknown (but bounded), as long as the requested amount of data to regenerate is smaller or equal to the block's content. This function used to require the exact compressed size, and would sometimes support above scenario "by accident", but then could also break it by accident. This is now firmly controlled, documented and tested.
The decompress*_fast() variants have been moved into the deprecate section.While they offer slightly faster decompression speed (~+5%), they are also unprotected against malicious inputs, resulting in security liability. There are some limited cases where this property could prove acceptable (perfectly controlled environment, same producer / consumer), but in most cases, the risk is not worth the benefit.We want to discourage such usage as clearly as possible, by pushing the _fast() variant into deprecation area.For the time being, they will not yet generate deprecation warnings when invoked, to give time to existing applications to move towards decompress*_safe(). But this is the next stage, and is likely to happen in a future release.
Some social media sites have the potential for content posted there to spread virally over social networks. The term is an analogy to the concept of viral infections, which can spread rapidly from individual to individual. In a social media context, content or websites that are 'viral' (or which 'go viral') are those with a greater likelihood that users will re-share content posted (by another user) to their social network, leading to further sharing. In some cases, posts containing popular content or fast-breaking news have been rapidly shared and re-shared by a huge number of users.
All Project Reality: ARMA 2 versions require ARMA 2: Combined Operations with the latest ARMA 2: Operation Arrowhead v1.62 patch to be already installed. For detailed instructions on how to install, click here.
Collections are identified by a trailing slash to give a directory representation. You can also include a version number in the URI, e.g., /api/1.2/user/, so that a client can choose a suitable version, whereas /api/user/ uses the latest version. 2b1af7f3a8