profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/Daniel15/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Daniel Lo Nigro Daniel15 @Facebook Palo Alto, CA https://d.sb/ Senior Frontend Developer @facebook. C# / .NET fan. @dotnet-foundation member. Australian 🇦🇺

babel/babel-standalone 805

:video_game: Now located in the Babel repo! Standalone build of Babel for use in non-Node.js environments, including browsers.

Daniel15/BuildSize 49

Automatically track the size of your build artifacts

babel/babel-standalone-bower 9

Bower build of babel-standalone. See https://github.com/Daniel15/babel-standalone

Daniel15/AjaXplorer-Azure 1

Plugin for AjaXPlorer that allows browsing of Windows Azure Blob Storage

Daniel15/Banshee-StatusUpdater 1

Show your currently playing music in your Telepathy / Empathy status

DanBuild/babel-standalone-TEST 0

Standalone build of Babel for use in non-Node.js environments, including browsers. Similar to the (now deprecated) babel-browser.

Daniel15/511php 0

A library for accessing 511.org's Transit Trip Planner from PHP

Daniel15/acme-dns 0

Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.

Daniel15/acme.sh 0

A pure Unix shell script implementing ACME client protocol

Daniel15/ajax-solr 0

A JavaScript framework for creating user interfaces to Solr.

issue commentreactjs/React.NET

ReactSiteConfiguration.Configuration.MaxEngines recommended engines

You have a leak somewhere, the default should be fine for most applications.

We have seen this before with the v8 engine, the cause is unclear. You may have better luck with the ChakraCore engine.

Disabling pooling will also work but has worse performance..

On Fri, May 7, 2021 at 03:56, debrouwernele ***@***.***> wrote:

Hi,

What is the recommended setting for MaxEngines? At the moment this is our configuration: JsEngineSwitcher.Current.DefaultEngineName = V8JsEngine.EngineName; JsEngineSwitcher.Current.EngineFactories.AddV8(); ReactSiteConfiguration.Configuration.MaxEngines = 35; ReactSiteConfiguration.Configuration.ReuseJavaScriptEngines = true;

On production we had the following error: JSPool.Exceptions.JsPoolExhaustedException. There's an average of 40.000 page views per day.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/reactjs/React.NET/issues/1253, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHGCFV7QMGRHUC2ADNHKRLTMOTMFANCNFSM44JKK4PQ .

debrouwernele

comment created time in 38 minutes

release RollingVersions/RollingVersions

rollingversions@3.0.0

released time in an hour

startedCaravanaCloud/Anonymouse

started time in an hour

issue openedreactjs/React.NET

ReactSiteConfiguration.Configuration.MaxEngines recommended engines

Hi,

What is the recommended setting for MaxEngines? At the moment this is our configuration: JsEngineSwitcher.Current.DefaultEngineName = V8JsEngine.EngineName; JsEngineSwitcher.Current.EngineFactories.AddV8(); ReactSiteConfiguration.Configuration.MaxEngines = 35; ReactSiteConfiguration.Configuration.ReuseJavaScriptEngines = true;

On production we had the following error: JSPool.Exceptions.JsPoolExhaustedException. There's an average of 40.000 page views per day.

created time in 2 hours

fork cloudpage/dnstools

Source code for dnstools.ws - DNS lookups, pings, and traceroutes from 20 locations worldwide

https://dnstools.ws/

fork in 4 hours

startedqntm/hatetris

started time in 10 hours

startedgoogle/zx

started time in 10 hours

create barnchyarnpkg/website

branch : dependabot/npm_and_yarn/ua-parser-js-0.7.28

created branch time in 12 hours

PR opened yarnpkg/website

Bump ua-parser-js from 0.7.18 to 0.7.28

Bumps ua-parser-js from 0.7.18 to 0.7.28. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/faisalman/ua-parser-js/commit/1d3c98a10c23915046a362c4e3b3b503fb40d611"><code>1d3c98a</code></a> Revert breaking fix <a href="https://github-redirect.dependabot.com/faisalman/ua-parser-js/issues/279">#279</a> and release as 0.7.28</li> <li><a href="https://github.com/faisalman/ua-parser-js/commit/535f11bd2403910f29dabe6f90adb014ad016747"><code>535f11b</code></a> Delete redundant code</li> <li><a href="https://github.com/faisalman/ua-parser-js/commit/642c0399e831e27c5c86c3b7afee02e876250d01"><code>642c039</code></a> Fix <a href="https://github-redirect.dependabot.com/faisalman/ua-parser-js/issues/492">#492</a> LG TV WebOS detection</li> <li><a href="https://github.com/faisalman/ua-parser-js/commit/3edacddb2474429c55fa39d1e6222d50bbf9266f"><code>3edacdd</code></a> Merge branch 'master' into develop</li> <li><a href="https://github.com/faisalman/ua-parser-js/commit/acc0b91ff5defa2ca9a722874e27277879292907"><code>acc0b91</code></a> Update contributor list</li> <li><a href="https://github.com/faisalman/ua-parser-js/commit/f726dcd1ae4fea51e99b8ca574a1be51fbd70e1a"><code>f726dcd</code></a> Merge branch 'master' into develop</li> <li><a href="https://github.com/faisalman/ua-parser-js/commit/383ca587ef9b8daffcf652ac39fc9b8f3708572e"><code>383ca58</code></a> More test for tablet devices</li> <li><a href="https://github.com/faisalman/ua-parser-js/commit/7c8aa435b26cb14537423cd5fe4ce077e0661db2"><code>7c8aa43</code></a> Minor rearrangement</li> <li><a href="https://github.com/faisalman/ua-parser-js/commit/09aa9105dc370ded9275f70eae1f4eb67394966c"><code>09aa910</code></a> Add new device & browser: Tesla</li> <li><a href="https://github.com/faisalman/ua-parser-js/commit/557cc2198d88068892eec6b61f2b2f4fe6e96314"><code>557cc21</code></a> More test for latest phones with unique form factor (fold/flip/qwerty/swivel)</li> <li>Additional commits viewable in <a href="https://github.com/faisalman/ua-parser-js/compare/0.7.18...0.7.28">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+3 -2

0 comment

1 changed file

pr created time in 12 hours

issue commentaspnet/Announcements

Actions returning IAsyncEnumerable<> are no longer buffered by MVC when using System.Text.Json

Please use https://github.com/dotnet/aspnetcore/issues/32483 for questions and further discussion.

pranavkm

comment created time in 12 hours

issue openedaspnet/Announcements

Actions returning IAsyncEnumerable<> are no longer buffered by MVC when using System.Text.Json

Actions returning IAsyncEnumerable<> are no longer buffered by MVC when using System.Text.Json

In 5.0, MVC added support for output formatting IAsyncEnumerable<> types by buffering the sequence in memory and formatting the buffered collection. In 6.0, when formatting using System.Text.Json, IAsyncEnumerable<> instances are no longer buffered by MVC, instead relying on the support for these types added to System.Text.Json.

In most cases, the absence of buffering would not be observed by the application. However, some scenarios may have inadvertently relied on the buffering semantics to correctly serialize. For instance, returning an IAsyncEnumerable<> that is backed by a EF query on a type with lazy loaded properties might result in concurrent query execution which might be unsupported by the provider.

This change does not affect output formatting using Newtonsoft.Json, or with XML-based formatters

Version introduced

6.0-preview4

Old behavior

IAsyncEnumerable<> instances returned from an MVC action as a value to be formatted using ObjectResult, or a JsonResult would be buffered before being serialized as synchronous collection.

New behavior

When formatting using System.Text.Json, IAsyncEnumerable<> instances are no longer buffered by MVC.

Reason for change

System.Text.Json added support for streaming IAsyncEnumerable<> types. This allows for a smaller memory footprint during serialization.

Recommended action

If your application requires buffering, consider manually buffering the async enumerable:

// Before
public IActionResult Get()
{
    return Ok(dbContext.Blogs);
}

// After
public async Task<IActionResult> Get()
{
    return Ok(await dbContext.Blogs.ToListAsync());
}

Category

ASP.NET

Affected APIs

"Not detectable via API analysis"

<!-- Do not modify anything below this line -->


Issue metadata

  • Issue type: breaking-change

created time in 12 hours

PR opened reactjs/React.NET

Bump lodash from 4.17.19 to 4.17.21 in /src/React.Core

Bumps lodash from 4.17.19 to 4.17.21. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/f299b52f39486275a9e6483b60a410e06520c538"><code>f299b52</code></a> Bump to v4.17.21</li> <li><a href="https://github.com/lodash/lodash/commit/c4847ebe7d14540bb28a8b932a9ce1b9ecbfee1a"><code>c4847eb</code></a> Improve performance of <code>toNumber</code>, <code>trim</code> and <code>trimEnd</code> on large input strings</li> <li><a href="https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c"><code>3469357</code></a> Prevent command injection through <code>_.template</code>'s <code>variable</code> option</li> <li><a href="https://github.com/lodash/lodash/commit/ded9bc66583ed0b4e3b7dc906206d40757b4a90a"><code>ded9bc6</code></a> Bump to v4.17.20.</li> <li><a href="https://github.com/lodash/lodash/commit/63150ef7645ac07961b63a86490f419f356429aa"><code>63150ef</code></a> Documentation fixes.</li> <li><a href="https://github.com/lodash/lodash/commit/00f0f62a979d2f5fa0287c06eae70cf9a62d8794"><code>00f0f62</code></a> test.js: Remove trailing comma.</li> <li><a href="https://github.com/lodash/lodash/commit/846e434c7a5b5692c55ebf5715ed677b70a32389"><code>846e434</code></a> Temporarily use a custom fork of <code>lodash-cli</code>.</li> <li><a href="https://github.com/lodash/lodash/commit/5d046f39cbd27f573914768e3b36eeefcc4f1229"><code>5d046f3</code></a> Re-enable Travis tests on <code>4.17</code> branch.</li> <li><a href="https://github.com/lodash/lodash/commit/aa816b36d402a1ad9385142ce7188f17dae514fd"><code>aa816b3</code></a> Remove <code>/npm-package</code>.</li> <li>See full diff in <a href="https://github.com/lodash/lodash/compare/4.17.19...4.17.21">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~bnjmnt4n">bnjmnt4n</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+3 -3

0 comment

1 changed file

pr created time in 14 hours

startedvolojs/create-template

started time in 15 hours

startedKikobeats/cacheable-response

started time in 21 hours

startedmantinedev/mantine

started time in 21 hours

startedCircleCI-Public/aws-ecr-orb

started time in a day

startedkjagiello/diagwiz

started time in a day

startedphase1geo/Minder

started time in a day

startedgaphor/gaphor

started time in a day

startedNiGhTTraX/strong-mock

started time in a day