profile
viewpoint
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 777

: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

Daniel15/cache 1

Cache library for Kohana 3

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

issue commentyarnpkg/yarn

Yarn Debian key expiry date updated (EXPKEYSIG 23E7166788B63E1E)

Thanks @alexcdot! That command relies on package repository maintainers uploading their public keys to the Ubuntu keyserver, but most do, so it's usually not an issue :)

Daniel15

comment created time in a day

push eventDaniel15/dnstools

Daniel Lo Nigro

commit sha 0fc8518c1300e70d2eb3d4665d9f52d65cfd9195

Consistently use either IPv4 or IPv6 for pings. Closes #30

view details

push time in a day

issue closedDaniel15/dnstools

Consistently use either IPv4 or IPv6

When "Any" is selected and you ping a host with both IPv4 and IPv6, it seems pretty random which protocol will be used - Some workers use IPv4 while others use IPv6. We should probably consistently prioritise IPv6 over IPv4.

closed time in a day

Daniel15

push eventDaniel15/dnstools

Daniel Lo Nigro

commit sha d6cdcf78712aeb377868a69b052b60d9d36a289a

Embed just the chevron icon rather than the whole Octicons package.

view details

Daniel Lo Nigro

commit sha 265f05c5206f9d3615bac3dcd4a6bbcf85b45c40

Embed common country flags directly as React components

view details

push time in 2 days

delete branch Daniel15/disconnect-tracking-protection

delete branch : patch-1

delete time in 4 days

issue commentmasonr/yet-another-bench-script

Replace dd with fio?

Thank you @masonr! This is great :D

Daniel15

comment created time in 5 days

pull request commentreactjs/React.NET

Add support for webpack app manifest

I wonder if we should reuse the asset-manifest.json parsing I wrote for WebpackTag: https://github.com/Daniel15/WebpackTag/blob/master/src/WebpackTag/AssetParsers/AssetManifestParser.cs. I didn't really design it to be reusable outside of that library though...

dustinsoftware

comment created time in 7 days

issue commentyarnpkg/berry

[Bug] `yarn set version berry` writes absolute (non-portable) path into .yarnrc.yml

Should we move this issue to the 1.x repo?

cspotcode

comment created time in 8 days

CommitCommentEvent

issue openedyarnpkg/berry

[Feature] Merge Yarn v1 and v2 sites?

  • [x] I'd be willing to implement this feature
  • [ ] This feature can already be implemented through a plugin

Now that it seems like Yarn v1 and v2 will coexist side-by-side, perhaps we should consider merging/unifying the two sites together. A lot of the core concepts and commands are the same across both versions. We can highlight what's changed between v1 and v2

created time in 11 days

issue commentdotnet/runtime

.NET Core 3.0 RTM Freeze on Ubuntu 16.04 OpenVZ

@am11 I'm glad you found the workaround useful :)

For what it's worth, for https://dnstools.ws/ I'm deploying this workaround to all servers as part of an Ansible playbook:

- name: Temporary hack for https://github.com/dotnet/coreclr/issues/27955
  get_url:
    url: https://d.ls/dotnet/bugs/libcoreclr-27955-workaround.so
    dest: /usr/local/lib/libcoreclr-27955-workaround.so
    mode: "0755"
    checksum: sha256:be021161c98f69367745cd7d821b8175b6466eb5fa5921ecee3dcb6f9ff8f150

https://github.com/Daniel15/dnstools/blob/ab2fbd4202530722e6587f3813a0deb5f228e723/ansible/roles/dnstools-worker/tasks/main.yml#L63-L70

Then in my systemd file I have:

# Workaround for https://github.com/dotnet/coreclr/issues/27955
Environment=LD_PRELOAD=/usr/local/lib/libcoreclr-27955-workaround.so

https://github.com/Daniel15/dnstools/blob/master/src/DnsTools.Worker/deployment/dnstools-worker.service#L15

303248153

comment created time in 12 days

issue commentyarnpkg/yarn

yarn install script has issues when running in dash

Would you like to submit a PR to fix this?

interone-ms

comment created time in 13 days

issue closedyarnpkg/yarn

yarn-chocolatey #86 failed

Build 'yarn-chocolatey' is failing!

Last 50 lines of build output:

Started by upstream project "yarn-version" build number 100
originally caused by:
 Started by user Daniel Lo Nigro
Running as SYSTEM
Building on master in workspace C:\Program Files (x86)\Jenkins\workspace\yarn-chocolatey
No credentials specified
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/yarnpkg/yarn.git # timeout=10
Fetching upstream changes from https://github.com/yarnpkg/yarn.git
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/yarnpkg/yarn.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse "origin/master^{commit}" # timeout=10
Checking out Revision 989a74067420f370fa575a59624ed258334f90d1 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 989a74067420f370fa575a59624ed258334f90d1 # timeout=10
FATAL: Could not checkout 989a74067420f370fa575a59624ed258334f90d1
hudson.plugins.git.GitException: Command "git checkout -f 989a74067420f370fa575a59624ed258334f90d1" returned status code 1:
stdout: 
stderr: error: unable to create file __tests__/fixtures/install/install-update-auth-invalid-cache-integrity/.yarn-cache/v6/npm-safe-buffer-5.1.1-893312af69b2123def71f57889001671eeb2c853-integrity/node_modules/safe-buffer/.yarn-metadata.json: Filename too long
Previous HEAD position was ac04da8d 1.22.0-0
HEAD is now at 989a7406 1.23.0-0

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$900(CliGitAPIImpl.java:81)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2627)
Caused: hudson.plugins.git.GitException: Could not checkout 989a74067420f370fa575a59624ed258334f90d1
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2651)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1228)
	at hudson.scm.SCM.checkout(SCM.java:504)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
	at hudson.model.Run.execute(Run.java:1815)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:429)

Changes since last successful build: No changes No changes No changes No changes No changes

View full output

cc @Daniel15

closed time in 13 days

DanBuild

issue closedyarnpkg/yarn

Error releasing v1.22.0

An error was encountered while processing the CircleCI release build of v1.22.0:

Build #36802 in wrong status (failed), expected "success". Not releasing it.

Re-running the build on CircleCI might fix it. Click "Rebuild" on this page to trigger a rebuild

Full logs: https://release.yarnpkg.com/log/release_circleci

cc @Daniel15 @arcanis

closed time in 13 days

DanBuild

issue closedyarnpkg/yarn

Error releasing v1.22.0

An error was encountered while processing the CircleCI release build of v1.22.0:

Build #36803 in wrong status (failed), expected "success". Not releasing it.

Re-running the build on CircleCI might fix it. Click "Rebuild" on this page to trigger a rebuild

Full logs: https://release.yarnpkg.com/log/release_circleci

cc @Daniel15 @arcanis

closed time in 13 days

DanBuild

issue closedyarnpkg/yarn

Error releasing v1.22.0

An error was encountered while processing the CircleCI release build of v1.22.0:

Client error: `POST https://build.dan.cx/job/yarn-version/buildWithParameters` resulted in a `403 No valid crumb was included in the request` response:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 403 No valid crumb was in (truncated...)


Response:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 403 No valid crumb was included in the request</title>
</head>
<body><h2>HTTP ERROR 403</h2>
<p>Problem accessing /job/yarn-version/buildWithParameters. Reason:
<pre>    No valid crumb was included in the request</pre></p><hr><a href="http://eclipse.org/jetty">Powered by Jetty:// 9.4.z-SNAPSHOT</a><hr/>

</body>
</html>

Re-running the build on CircleCI might fix it. Click "Rebuild" on this page to trigger a rebuild

Full logs: https://release.yarnpkg.com/log/release_circleci

cc @Daniel15 @arcanis

closed time in 13 days

DanBuild

issue commentyarnpkg/yarn

Error releasing v1.22.0

Completed

DanBuild

comment created time in 13 days

issue commentyarnpkg/yarn

Error releasing v1.22.0

The tarball (https://github.com/yarnpkg/yarn/releases/download/v1.22.0/yarn-v1.22.0.tar.gz) looks fine and that's what we publish to npm, so I'll try just run the update-npm.sh script locally.

DanBuild

comment created time in 13 days

issue commentyarnpkg/yarn

Error releasing v1.22.0

Promote to stable isn't working as the release is missing from npm. The release is missing from npm because the CircleCI build failed so it didn't complete the release process. I'm re-running the failed tests on CircleCI to see if that works to fix it.

DanBuild

comment created time in 13 days

issue commentyarnpkg/yarn

Error releasing v1.22.0

The "promote to stable" button doesn't appear until the site shows the new RC version... Netlify is still building it. I'll click it once available.

DanBuild

comment created time in 13 days

issue commentyarnpkg/yarn

Error releasing v1.22.0

@arcanis Did you want to bump this from RC to stable? I imagine we probably won't release RC versions of Yarn v1 any more, and everything will be stable releases.

DanBuild

comment created time in 13 days

issue commentyarnpkg/yarn

Error releasing v1.22.0

@arcanis I manually kicked off the build which seemed to work.

I think our scripts are broken because of this change in a Jenkins update:

CSRF tokens (crumbs) are now only valid for the web session they were created in to limit the impact of attackers obtaining them. Scripts that obtain a crumb using the /crumbIssuer/api URL will now fail to perform actions protected from CSRF unless the scripts retain the web session ID in subsequent requests. Scripts could instead use an API token, which has not required a CSRF token (crumb) since Jenkins 2.96. To disable this improvement you can set the system property hudson.security.csrf.DefaultCrumbIssuer.EXCLUDE_SESSION_ID to true. Alternatively, you can install the Strict Crumb Issuer Plugin which provides more options to customize the crumb validation. It allows excluding the web session ID from the validation criteria, and instead e.g. replacing it with time-based expiration for similar (or even better) protection from CSRF.

from https://jenkins.io/doc/upgrade-guide/2.176/#SECURITY-626 and https://github.com/spinnaker/spinnaker/issues/2067

We can probably move this to GitHub Actions now that it exists (there wasn't really anything similar when we built out this infra), but for now I'll just try out that plugin mentioned in the Jenkins docs, or figure out how to switch it to use an API token.

DanBuild

comment created time in 13 days

delete branch yarnpkg/website

delete branch : Daniel15-patch-1

delete time in 14 days

push eventyarnpkg/website

Daniel Lo Nigro

commit sha 2fb465d64dbf0193a4e18c06edf5091d0a08cd36

Add redirects from old subdomains (#1043)

view details

push time in 14 days

PR merged yarnpkg/website

Add redirects from old subdomains
+6 -0

1 comment

1 changed file

Daniel15

pr closed time in 14 days

issue closedyarnpkg/website

Translated Page is 404 on https://classic.yarnpkg.com

Translated pages are 404.

Examples

  • https://classic.yarnpkg.com/ja/
  • https://classic.yarnpkg.com/fr/

Reproduce Steps

  1. Visit https://classic.yarnpkg.com/lang/en/
  2. Select translated page on the menu

image

  1. Got 404 Not found

📝 Notes

Probably, This issue is related with " Site redirecting to /lang/en/ instead of /en/ #1031 "

closed time in 14 days

azu

issue commentyarnpkg/website

Translated Page is 404 on https://classic.yarnpkg.com

This should be OK now.

azu

comment created time in 14 days

push eventyarnpkg/website

Daniel Lo Nigro

commit sha 166c0c295a938306511df9c1e0f597950705e7ab

Mention in readme that this is the Yarn v1 site

view details

push time in 14 days

PR opened yarnpkg/website

Add redirects from old subdomains
+6 -0

0 comment

1 changed file

pr created time in 14 days

create barnchyarnpkg/website

branch : Daniel15-patch-1

created branch time in 14 days

issue commentyarnpkg/website

Translated Page is 404 on https://classic.yarnpkg.com

I'll look into this.

azu

comment created time in 14 days

pull request commentyarnpkg/berry

Add Windows installer

Yeah, I agree! I'm planning on submitting a PR to update the "installation" page on the Yarn v2 site to incorporate the Yarn v1 installation instructions, which would include a link to the Windows installer.

Daniel15

comment created time in 14 days

issue commentyarnpkg/yarn

GPG error: https://dl.yarnpkg.com/debian stable InRelease NO_PUBKEY E074D16EB6FF4DE3

Yes, this is currently mentioned in #7866 which is (temporarily) pinned in the repo.

boscowitch

comment created time in 15 days

issue commentmultinet-app/multinet-deploy

Builds will fail as GPG keys expire and are rotated

I'm really sorry about the Yarn key... I've been meaning to create a keyring package and stick it in the Yarn Debian repo but it's fairly low on my list of priorities. Nobody has given any guidance on how to do so, and I haven't had time to research it myself.

JackWilb

comment created time in 15 days

issue closedgrpc/grpc-dotnet

Connection timeout

Is there a way to specify a connection timeout? For example, fail if it takes longer than 5 seconds to connect to a server, but if it does connect within that time frame, allow the call to take longer?

I have a use case where some gRPC services may sporadically not be available, and it seems like the client sits for a long time waiting to connect. Some of these legit calls could take 30-40 seconds which is fine, but I want to fail the request if the connection isn't established within a few seconds.

closed time in 15 days

Daniel15

issue commentgrpc/grpc-dotnet

Connection timeout

Yeah, this is fine, thanks!

Daniel15

comment created time in 15 days

issue commentyarnpkg/yarn

Installation Problem: Add latest.zip because on Windows, we can't install several yarn with the MSI installer

I just added a latest.js redirect: https://classic.yarnpkg.com/latest.js

Although, I'd recommend hard-coding the version number so you always use the same one. You can use this URL: https://classic.yarnpkg.com/downloads/1.12.1/yarn-1.12.1.js

A-312

comment created time in 15 days

push eventyarnpkg/website

Daniel Lo Nigro

commit sha 022c548a431d9208809e03375a645053f0bad84e

Add /latest.js redirect

view details

push time in 15 days

issue commentyarnpkg/yarn

Docker build failed to update nodejs12.x with error in yarn to be installed globally

You should probably be using the Yarn Debian package in Docker (assuming you're using a Debian-based Docker image)

NirajCricket

comment created time in 15 days

pull request commentyarnpkg/yarn

Fix contributing link

@NoriSte The domain has already been changed... I might set up a 301 redirect from legacy. to classic. at some point. Currently both domains still work.

NoriSte

comment created time in 15 days

issue commentnikolaik/docker-python-nodejs

Update old yarn gpg key

I think I posted this issue of the maintainer's repo 🤔

Oops, sorry, I thought you posted this in the Yarn repo. Sorry! 😅

tlttnz2018

comment created time in 16 days

issue commentyarnpkg/yarn

Installation Problem: Add latest.zip because on Windows, we can't install several yarn with the MSI installer

Another option is to download the JS file. You can execute that directly using Node.js.

Yet another option is to extract the MSI using msiexec (eg. see https://thebackroomtech.com/2007/08/23/howto-extract-files-from-a-msi-file-using-the-windows-command-line/)

A-312

comment created time in 16 days

CommitCommentEvent

issue commentnikolaik/docker-python-nodejs

Update old yarn gpg key

You'll have to get whoever maintains the Docker image to update the GPG key.

tlttnz2018

comment created time in 16 days

issue commentyarnpkg/yarn

Installing Yarn on Ubuntu 18.04.1 LTS gives invalid signature error. Possible expired key?

I extended the expiry a few weeks ago, but you need to manually update it since I haven't configured it to auto update yet. See #7841

Hates

comment created time in 16 days

issue commentyarnpkg/yarn

Installation Problem: Yarn

Yeah this sounds like your Node.js version is extremely old.

KomalDhanwani

comment created time in 16 days

issue commentyarnpkg/yarn

Installation Problem: Add latest.zip because on Windows, we can't install several yarn with the MSI installer

We have a tarball (latest.tar.gz); can you use that?

A-312

comment created time in 16 days

issue commentyarnpkg/yarn

Yarn Debian key expiry date updated (EXPKEYSIG 23E7166788B63E1E)

@dario23 Yeah, that's what I've been meaning to do, however I just haven't gotten around to it. I think I could add a yarn-keyring package to our repo, add it as a dependency of the yarn package (to ensure everyone has it), and then update that package whenever we change the key.

Daniel15

comment created time in 16 days

issue openedyarnpkg/yarn

Yarn Debian key expiry date updated (EXPKEYSIG 23E7166788B63E1E)

If you see an error like this:

The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging yarn@dan.cx

Or like this:

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging yarn@dan.cx W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging yarn@dan.cx

It means that you still have an older version of the GPG key used to sign Yarn releases. The expiry date for this key was extended from 2020 to 2021. To get the updated key, run this:

curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -

This will likely be automated in the future.

created time in 17 days

issue commentyarnpkg/yarn

BAD signature from "Yarn Packaging"

This usually happens when the download fails for some reason. I'd be happy to review a PR that makes the install script more resilient (eg. retry the download a few times)

mscott5861

comment created time in 17 days

PR opened gatsbyjs/gatsby

Adjust Windows-specific notice about 0.0.0.0:8000

Technically, 0.0.0.0 is a non-routable IP, so it's not even supposed to work. Always using either localhost or the network IP is the best thing to do on every OS, not just on Windows.

+1 -1

0 comment

1 changed file

pr created time in 17 days

create barnchgatsbyjs/gatsby

branch : Daniel15-patch-1

created branch time in 17 days

PR closed Daniel15/yarn-berry

Add Windows installer
+221 -5

0 comment

10 changed files

Daniel15

pr closed time in 17 days

PR opened yarnpkg/berry

Reviewers
Update site domains

Replaces legacy.yarnpkg.com to classic.yarnpkg.com as per the discussion in #766:

The Yarn Classic documentation will be moved once again to be hosted at classic.yarnpkg.com

Replaces next.yarnpkg.com with yarnpkg.com now that the v2 site is the default one.

References #766

+97 -97

0 comment

26 changed files

pr created time in 17 days

create barnchDaniel15/yarn-berry

branch : domains

created branch time in 17 days

push eventDaniel15/yarn-berry

Avraham Ostreicher

commit sha 18cbcbcfd2463c36a5b794013a2b72b83e8ce111

Handle duplicate dependencies by `yarn add` (#428) * Fix typo in prompt * Handle duplicate dependencies by `add` command * Styles & tests * Bumps the right versions

view details

Sebastian Silbermann

commit sha 0f0a4e5dfcff195f0175303e3362adba40b65368

feat(set version): Miscellaneous changes (#432) * fix(set version): yarn-yarn-sources -> yarn-sources * feat(set version): Only fetch latest commit * fix: yarn version check

view details

Maël Nison

commit sha 436e11c5ad007484c2c949614691807945ecfbcc

Fixes virtual package generation (#433) * wip * Fixes an invalid virtual package generation when using both peers and devs * Bumps the versions

view details

Maël Nison

commit sha 196cc9d1119b350b12747e2987f2ed40c78ad8b5

Prevents the same file from appearing twice in the list (#434)

view details

Maël Nison

commit sha a244e67b7ddeff591daf6c5f85956f4a9d8bb08c

Mael/lazy imports (#436) * wip * Implements lazy imports

view details

Sebastian Silbermann

commit sha 1078375e76ce2a1250f89c26760838f045ebbac5

feat(resolve): Accept any workspace version in workspace:* (#437) * test: Add failing test for workspace:* and alpha versions * feat: workspace:* matches literally any version * fix: yarn version check * Typo

view details

Maël Nison

commit sha 50c12629a7dcf6014b16ca68e996cf574d411b63

Fixes master

view details

Maël Nison

commit sha 22fa2f75cdacf60a847614680528cc55c27c7644

Fixes publishing scoped packages to third-party registries (#439) * Allows explicitly pass both the registry and the ident * Bumps the versions

view details

Maël Nison

commit sha 98a5eb15674481cb60755d797c8b2f2f33a6f7b9

Starts reworking the release workflow

view details

Maël Nison

commit sha 063546fbbf97d885a415e058e3a5df19cd66a789

Checks that everything can prepack before publishing

view details

Maël Nison

commit sha 919dea641d485df741571557cb335c7c2721256b

Releasing 7 new packages | Package name | Version | | --- | --- | | `@yarnpkg/plugin-essentials` | `2.0.0-rc.3` | | `@yarnpkg/plugin-npm` | `2.0.0-rc.2` | | `@yarnpkg/plugin-npm-cli` | `2.0.0-rc.2` | | `@yarnpkg/plugin-version` | `2.0.0-rc.3` | | `@yarnpkg/builder` | `2.0.0-rc.4` | | `@yarnpkg/cli` | `2.0.0-rc.4` | | `@yarnpkg/core` | `2.0.0-rc.5` |

view details

Maël Nison

commit sha 2023430e7922360a4ff2923de793cdfa547d0fdc

Improves the release-build script

view details

Maël Nison

commit sha ede8b5e032caed9806a976d8eecc574881e0f400

Publish on both registries

view details

Maël Nison

commit sha 1731d37bcd159715de03c9748c15ccb399f4b8b8

Removes the release workflow for now

view details

Maël Nison

commit sha e9bd55d795926b2338c01ff258e5f463f58699fe

Fixes the release script

view details

Maël Nison

commit sha ee82f666f6dea2ff307c2546441e6a9073876d7c

Fixes the lockfile

view details

Maël Nison

commit sha e4ec980eaecec738473a5c377e34fb729c865567

Adds a shebang to yarnpkg/builder (#440) * Adds a shebang to the builder binaries * Bump its version

view details

Maël Nison

commit sha aa159685ca4080027b716fdccccfed31d9ab1ab2

Adds the Next workflow (#442) * Adds the Next workflow * Uses tee * Returns the configuration

view details

Maël Nison

commit sha e27dae2cb6eb0fbd3efeaf5d6c076178536ecfdf

Update README.md

view details

Maël Nison

commit sha 8b3b6f18afbe60ea7e5661a1e4cd028f33e7dc6d

Updates the bundles

view details

push time in 17 days

pull request commentreactjs/React.NET

Add Node JS engine support

I think this closes #971

dustinsoftware

comment created time in 18 days

issue commentreactjs/React.NET

See if we can use Jering.Javascript.NodeJS

#1021

Daniel15

comment created time in 18 days

pull request commentreactjs/React.NET

Add Node JS engine support

Good idea! I wonder if we could add script debugging too, in the future.

dustinsoftware

comment created time in 18 days

Pull request review commentreactjs/React.NET

Add Node JS engine support

+using System;+using System.Reflection;++namespace React+{+	/// <summary>+	/// The wrapper for the Node engine+	/// </summary>+	public interface INodeJsEngine+	{+		string Name { get; }+		string Version { get; }++		bool HasVariable(string uSER_SCRIPTS_LOADED_KEY);

Is it intentional that u is lowercase? 🤔

dustinsoftware

comment created time in 18 days

issue commentreactjs/React.NET

Dictionary get serialized as camel case

what do you think about moving to System.Text.Json ?

I imagine quite a few users would be customizing the Json.NET settings at the moment, so I think this would have to be opt-in.

Also, does it work for older .NET Framework versions too, or is it just part of newer .NET Core versions?

knyzorg

comment created time in 19 days

issue commentDaniel15/Website

Redesign site

CSS grid: https://gedd.ski/post/article-grid-layout/

Daniel15

comment created time in 19 days

startedgaul/awesome-ld-preload

started time in 20 days

startedmicrosoft/ApplicationInspector

started time in 20 days

issue openedgoogle/ngx_brotli

Debian installation instructions

Would be good to have this on a wiki... In @eustas's fork I sent a PR to add some basic instructions in the README (https://github.com/eustas/ngx_brotli/pull/34) but it seems like that's not present in this repo. Would you like instructions in the repo, or would you prefer some docs somewhere?

# Get this source code
cd /usr/local/src
git clone git@github.com:google/ngx_brotli.git

# Get the Nginx Debian package source code
cd /usr/local/src/
apt source nginx
cd nginx-1.x.x

# Find the ./configure line Nginx was compiled with
nginx -V

# Call `./configure` with the arguments from "configure arguments:" output above, **except** for the `--add-dynamic-module` ones, and append `--add-dynamic-module=../ngx_brotli` to the end
./configure --with-cc-opt='-g -O2 ....................... --add-dynamic-module=../ngx_brotli

# Build and copy build modules to the right place
make modules
cp objs/ngx_http_brotli_filter_module.so /usr/local/lib/nginx/modules/
cp objs/ngx_http_brotli_static_module.so /usr/local/lib/nginx/modules/

Enable by adding to /etc/nginx/modules-enabled/brotli-static.conf:

load_module /usr/local/lib/nginx/modules/ngx_http_brotli_filter_module.so;
load_module /usr/local/lib/nginx/modules/ngx_http_brotli_static_module.so;

created time in 21 days

issue commentzloirock/core-js

Please remove the post install script

well considering he was committing on a almost daily basis then went silent 12 days ago i would imagine this project just died. here's to hoping babel or someone else takes this over. he sounded like a real winner

@ljmerza just because a project hasn't received commits in two weeks doesn't mean it's dead. People have commitments other than open source work that doesn't make them any money. Also, there is such a thing as a project being 'complete'. Some projects go years between major updates, and that's fine. In fact, often I much prefer libraries that are stable and move slowly.

pronebird

comment created time in 21 days

issue commentyarnpkg/yarn

GitHub API rate limit exceeded when `yarn policies set-version ^1`

Something we could do to avoid the GitHub API rate limits is periodically scrape the version list from the GitHub API and stick it somewhere else (eg. in a file on the Yarn site). I could write a script to do that as part of the release tooling, or we could have a GitHub Action to do it (if it's possible to schedule them)

manrueda

comment created time in 22 days

issue commentyarnpkg/yarn

yarn-chocolatey #82 failed

I don't think I ever fixed the build server so we'll end up seeing another task like this again if anyone ever pushes a new Yarn 1.x build.

DanBuild

comment created time in 22 days

issue commentyarnpkg/yarn

yarn-chocolatey #82 failed

Thanks for closing this @olingern - I never got a chance to look into fixing it :(

DanBuild

comment created time in 22 days

issue commentyarnpkg/berry

[Bug] Package details page on site shows 404 before rendering

cc @Haroenv

Daniel15

comment created time in 22 days

issue openedyarnpkg/berry

[Bug] Package details page on site shows 404 before rendering

  • [x] I'd be willing to implement a fix

Describe the bug

When you hit a package permalink on the new site, it shows a 404 error briefly, before rendering the correct page

To Reproduce

Go to https://yarnpkg.com/package/react

Screenshots

First shows: image

But then a bit later, shows the correct page: image

created time in 22 days

push eventyarnpkg/release-infra

Daniel Lo Nigro

commit sha 239d19265d76ae8e369983962c490e8fb601d7a5

Redirect yarn.pm/name to non-legacy site

view details

push time in 22 days

issue commentyarnpkg/website

Site redirecting to /lang/en/ instead of /en/

Actually I just realised that the package listing DOES exist on the new site, just without the /en/ in the URL. I'll update the redirect to go to the non-/en/ version instead.

Daniel15

comment created time in 22 days

issue commentyarnpkg/website

Site redirecting to /lang/en/ instead of /en/

@arye-dov-eidelman - Thanks for the report. I think that's due to some bad redirects on the new site. It's redirecting:

  • https://yarn.pm/react
  • https://yarnpkg.com/en/package/react
  • https://legacy.yarnpkg.com/lang/en/package/react
  • https://legacy.yarnpkg.com/en/lang/en/package/react

The new site shouldn't be inserting /lang/ in the URL. I submitted https://github.com/yarnpkg/berry/pull/802 to fix that.

I also updated yarn.pm to go directly to the legacy site, bypassing the broken redirect on the 'new' site (https://github.com/yarnpkg/release-infra/commit/667c9a44142bdf7a4611ec8b8885e0276b0284c8) which should fix it.

Daniel15

comment created time in 22 days

push eventyarnpkg/release-infra

Daniel Lo Nigro

commit sha 667c9a44142bdf7a4611ec8b8885e0276b0284c8

Directly redirect yarn.fyi and yarn.pm to legacy site

view details

push time in 22 days

PR opened yarnpkg/berry

Remove /lang/ from redirect URLs

/lang/ shouldn't be user-facing, and actually breaks some URLs.

References #1031 (-ish)

+22 -22

0 comment

1 changed file

pr created time in 22 days

create barnchyarnpkg/berry

branch : Daniel15-patch-1

created branch time in 22 days

issue openedreact-spring/react-spring

Animation is smooth on desktop but slow on Chrome Android

🤓 Question

I have an animation that works fine on desktop Firefox and Chrome, but can be quite slow on mobile (tested in Chrome on Android).

To repro, go to https://dnstools.ws/lookup/example.com/A/, wait for it to load, then click the little expand icon to the left of any of the location names.

The code is here: https://github.com/Daniel15/dnstools/blob/master/src/DnsTools.Web/ClientApp/src/components/ExpandTransition.tsx https://github.com/Daniel15/dnstools/blob/master/src/DnsTools.Web/ClientApp/src/components/DnsLookupWorkerResult.tsx#L97

I thought it might be because I'm animating the height of the element, which causes a repaint. However, my code was inspired by the "treeview" example in the react-spring docs (https://codesandbox.io/s/lp80n9z7v9?from-embed), and that example is nice and smooth. I want mine to be smooth like that! Also I tried changing the animation to only do opacity (for testing purposes), and even then it was a bit laggy on mobile.

Any ideas what I'm doing wrong here?

created time in 23 days

push eventDaniel15/dnstools

Daniel Lo Nigro

commit sha 4b19c9fc6806dee9f1cac6fd2cdc90f788945441

Animate DNS lookup referral expand/collapse

view details

Daniel Lo Nigro

commit sha 2ca0df8cf569d62f16547a87b546b15c5025922b

- Small optimizations to DNS expand animation - Only show third column (server name) on large screens

view details

push time in 23 days

issue commentprimer/octicons

Improve tree shaking friendliness

Just noticed today that adding a single Octicons icon to my app increases its bundle size by 68 KB :/

image

Are there any plans to support tree shaking?

shawnbot

comment created time in 23 days

issue commentyarnpkg/berry

[Feature] Release yarn v2 under a different name

Now I will search for a way to lock yarn to a specific version, kinda ironic.

@logaretm You can use policies set-version to lock down the Yarn version per-project, as mentioned above. You commit the Yarn JS file to the repo and then Yarn commands will use that version instead of the global one. If you're using a Docker image, the Yarn version should already be locked down based on a tag of the image.

brentvatne

comment created time in 23 days

issue commentreact-spring/react-spring

TypeScript: Property does not exist on 'AnimatedValue<Pick<OverwriteKeys<....>>

@aleclarson Is v9 beta stable? I usually try to avoid using beta software in prod. Seems like there's a pretty large increase in bundle size, too (ref https://bundlephobia.com/result?p=react-spring@8.0.27)

Daniel15

comment created time in 23 days

issue openedreact-spring/react-spring

TypeScript: Property does not exist on 'AnimatedValue<Pick<OverwriteKeys<....>>

🐛 Bug Report

This code:

const {height, opacity} = useSpring({
  from: {height: 0, opacity: 0},
  to: {
    height: isExpanded ? dimensions.height : 0,
    opacity: isExpanded ? 1 : 0,
  },
});

works fine at runtime, but produces this TypeScript error:

Property 'height' does not exist on type 'AnimatedValue<Pick<OverwriteKeys<{ from: { height: 0; opacity: 0; }; to: { height: number; opacity: number; }; 
}, CSSProperties>, never>>'

To Reproduce

Save above code in a .tsx file.

Expected behavior

This works fine at runtime, so the TypeScript definitions should be fine with it too.

Environment

  • react-spring v8.0.27
  • react v16.10.2

created time in 23 days

issue commentDaniel15/dnstools

Support performing DNS lookups across all workers

Implemented now

Daniel15

comment created time in 23 days

push eventDaniel15/dnstools

Daniel Lo Nigro

commit sha 3e1f85ceb494386bb8679a3afe5ac7e905ff500e

Remove 'coming soon' notice for multi-location DNS lookups

view details

push time in 23 days

push eventDaniel15/dnstools

Daniel Lo Nigro

commit sha 50c9689605ab0ebecdecc79009e3ebc96a8e2bb2

Allow selecting multiple locations for DNS lookups, and select all by default.

view details

push time in 23 days

push eventDaniel15/dnstools

Daniel Lo Nigro

commit sha aeac7add3e2f4e57546e7b71f59304c768552995

Move timeout to config and bump to 10 seconds

view details

Daniel Lo Nigro

commit sha dd490bc8ddb610331a1d35e6a04db221e329c23d

Allow expanding per-worker DNS lookup results inline

view details

Daniel Lo Nigro

commit sha f03bdef2c911159413adb32b5dc2eb8b6a41a982

Allow selecting multiple locations for DNS lookups, and select all by default.

view details

push time in 23 days

issue commentyarnpkg/berry

[Feature] Automatically create `ypx` as alias to `yarn dlx`

@arcanis It should be possible to do this for any system-wide Yarn installations though, right?

bondz

comment created time in 24 days

issue commentyarnpkg/berry

[Feature] Release yarn v2 under a different name

It would be nice to have a separate (temporary) package with the yarn binary renamed to berry, maybe under @yarnpkg/berry, to allow both Yarn 1 and 2 installed and usable at the same time

This will definitely be the case for the non-npm installation methods (Debian/Ubuntu package, Windows installer, Chocolatey and Homebrew), but it could be a good idea for the npm package too.

brentvatne

comment created time in 24 days

issue commentyarnpkg/berry

[Feature] Release yarn v2 under a different name

@Cretezy FWIW you can specify Yarn version per-project by using yarn policies set-version and committing the Yarn version to the repo. If you do that, the local version overrides the globally installed version. https://legacy.yarnpkg.com/en/docs/cli/policies/

brentvatne

comment created time in 24 days

issue closedDaniel15/dnstools

Migrate DNS traversal from PHP to C#

This should make it quite a bit faster, as the queries can be parallelised

closed time in 25 days

Daniel15

issue closedDaniel15/dnstools

Reduce timeout on gRPC calls

closed time in 25 days

Daniel15

PR opened yarnpkg/berry

Add note about installation methods

Don't want people to think that these are gone forever.

+2 -0

0 comment

1 changed file

pr created time in 25 days

create barnchyarnpkg/berry

branch : Daniel15-patch-1

created branch time in 25 days

startedDaniel15/wedding-site

started time in 25 days

push eventDaniel15/dnstools

Daniel Lo Nigro

commit sha 19e285728bf9babc43996f6fad82ceb03a9e007d

Move timeout to config and bump to 10 seconds

view details

push time in a month

push eventDaniel15/dnstools

Daniel Lo Nigro

commit sha 975ed1120160c8a916b1490ce5e010990c067dae

Add missing change from 7d15db1c5ce09e94ea6df1f37544658b410102c0

view details

push time in a month

push eventDaniel15/dnstools

Daniel Lo Nigro

commit sha 7d15db1c5ce09e94ea6df1f37544658b410102c0

Basic implementation of multi-server DNS lookups. UI still needs some more work.

view details

Daniel Lo Nigro

commit sha 2508ddc09078b3c457e76c4ca285e5b3b9197956

Use three-second timeout for connecting to workers

view details

push time in a month

IssuesEvent
more