microsoft/TACO 192
Tools for Apache Cordova
Demonstrates Ace + Ionic. Source code for the live PhoneGap Day app.
Support libraries for xamarin-macios
Xamarin.iOS & Xamarin.Mac API documentation in ECMA XML format
MSLaguana/ai-third-party-patches 1
Node package providing additional integration with specific third-party packages
MSLaguana/ApplicationInsights-node.js 0
Microsoft Application Insights SDK for node.js
ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge
Mirror of Apache Cordova Windows
issue commentmicrosoft/ApplicationInsights-node.js
Duplicate telemetry (request, traces and dependencies )
1. Yes I can share sdk version appInsight Configuration.
//app insights config.
let appInsights = require("applicationinsights");
appInsights.setup("<instrumentation_key>")
.setAutoDependencyCorrelation(true)
.setAutoCollectRequests(true)
.setAutoCollectPerformance(true, true)
.setAutoCollectExceptions(true)
.setAutoCollectDependencies(true)
.setAutoCollectConsole(true)
.setUseDiskRetryCaching(true)
.setSendLiveMetrics(false)
.setDistributedTracingMode(appInsights.DistributedTracingModes.AI_AND_W3C)
.start();
//host.json
{
"logging": {
"fileLoggingMode": "always",
"logLevel": {
"default": "Information",
"Host.Results": "Error",
"Function": "Error",
"Host.Aggregator": "Trace"
}
}
}
Note: **codeless instrumentation key is not provided only host.json config is given.**
2. yes I am using automatic tracking and correlations. ref: https://github.com/Microsoft/ApplicationInsights-node.js/ apart from that I have a manual trace logs and exception logs.
// Default export wrapped with Application Insights FaaS context propagation
export default async function contextPropagatingHttpTrigger(context, req) {
// Start an AI Correlation Context using the provided Function context
const correlationContext = appInsights.startOperation(context, req);
// Wrap the Function runtime with correlationContext
return appInsights.wrapWithCorrelationContext(async () => {
const startTime = Date.now(); // Start trackRequest timer
// Run the Function
await httpTrigger(context, req);
appInsights.defaultClient.flush();
}, correlationContext)();
};
3. No, Complete trace logs, dependency and request all type logs twice, some times comos db sdk logs https version logs more than 2x time some times.
comment created time in 5 minutes
issue commentnodejs/build
@bdkjones Homebrew now has official support for Apple Silicon, and there is a Node 15 pre-built bottle available.
comment created time in 31 minutes
issue commentnodejs/build
Can anyone provide an update on the status of pre-built Universal binaries becoming available? The Apple Silicon thread on the TSC repo got locked. There are a few folks saying they were able to build node 15 from source if installed via Homebrew. Others have failed to build that way.
In short, it seems like there is no cohesive plan or timeline to get Universal Binaries shipped. (I'm sure SOMEONE has one, but it would be nice to get that stated publicly.)
comment created time in 2 hours
issue closednodejs/build
tap2junit fails on test input when tests time out
2:03:21 mkdir out/junit || true
12:03:21 tap2junit -i test.tap -o out/junit/test.xml
12:03:21 tap2junit -i cctest.tap -o out/junit/cctest.xml || true
12:03:21 rm -Rf out/Release/obj.target
12:03:21 [aix61-ppc64] $ /bin/sh -xe /tmp/jenkins5548162882024815593.sh
12:03:22 + mkdir out/junit
12:03:22 mkdir: 0653-358 Cannot create out/junit.
12:03:22 out/junit: Do not specify an existing file.
12:03:22 + true
12:03:22 + tap2junit -i test.tap -o out/junit/test.xml
12:03:27 Traceback (most recent call last):
12:03:27 File "/usr/bin/tap2junit", line 11, in <module>
12:03:27 sys.exit(main())
12:03:27 File "/opt/freeware/lib/python2.7/site-packages/tap2junit/__main__.py", line 44, in main
12:03:27 result = parse(os.path.splitext(args.input.name)[0], data)
12:03:27 File "/opt/freeware/lib/python2.7/site-packages/tap2junit/__main__.py", line 15, in parse
12:03:27 t = TestCase(test.description, None, test.yaml['duration_ms'])
12:03:27 TypeError: 'NoneType' object has no attribute '__getitem__'
- https://ci.nodejs.org/job/node-test-commit-aix/nodes=aix61-ppc64/23968/console
I sshed in and reproduced it on AIX, then copied the file to my laptop, ubuntu, and reproduced here. tap file is https://gist.github.com/c15ba6bd9ff7b529a7aa04fa176f068a
core/build (centos7-python-3.7 $% u=) % scp test-osuosl-aix61-ppc64_be-1:/home/iojs/issue.tap .
issue.tap 100% 185KB 1.3MB/s 00:00
core/build (centos7-python-3.7 $% u=) % pip install tap2junit
Collecting tap2junit
Downloading https://files.pythonhosted.org/packages/af/22/f8436b6d750114dd5047970ad878259edeafa89fac72b8dced476965c6d6/tap2junit-0.1.4.tar.gz
Collecting junit-xml (from tap2junit)
Downloading https://files.pythonhosted.org/packages/a6/2a/f8d5aab80bb31fcc789d0f2b34b49f08bd6121cd8798d2e37f416df2b9f8/junit-xml-1.8.tar.gz
Collecting yamlish (from tap2junit)
Downloading https://files.pythonhosted.org/packages/29/fd/d607e225d757aa2950abff9ba19145be3c72b74266fc48f3266ec7ba3087/yamlish-0.18.1-py2-none-any.whl
Requirement already satisfied: six in /home/sam/.local/lib/python2.7/site-packages (from junit-xml->tap2junit) (1.12.0)
Requirement already satisfied: PyYAML>=3.09 in /usr/lib/python2.7/dist-packages (from yamlish->tap2junit) (3.13)
Building wheels for collected packages: tap2junit, junit-xml
Running setup.py bdist_wheel for tap2junit ... done
Stored in directory: /home/sam/.cache/pip/wheels/12/a9/54/a5f8ed9d0adfc510303204543f743bac3fc3a1b236d4545b10
Running setup.py bdist_wheel for junit-xml ... done
Stored in directory: /home/sam/.cache/pip/wheels/c6/c5/65/5b166afb6eac87dc300368ec4d92f39502dd41cdc73056d49e
Successfully built tap2junit junit-xml
Installing collected packages: junit-xml, yamlish, tap2junit
The script tap2junit is installed in '/home/sam/.local/bin' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed junit-xml-1.8 tap2junit-0.1.4 yamlish-0.18.1
core/build (centos7-python-3.7 $% u=) % /home/sam/.local/bin/tap2junit -i issue.tap -o test.xml
Traceback (most recent call last):
File "/home/sam/.local/bin/tap2junit", line 10, in <module>
sys.exit(main())
File "/home/sam/.local/lib/python2.7/site-packages/tap2junit/__main__.py", line 44, in main
result = parse(os.path.splitext(args.input.name)[0], data)
File "/home/sam/.local/lib/python2.7/site-packages/tap2junit/__main__.py", line 15, in parse
t = TestCase(test.description, None, test.yaml['duration_ms'])
TypeError: 'NoneType' object has no attribute '__getitem__'
closed time in 4 hours
sam-githubdelete branch microsoft/ApplicationInsights-node.js
delete branch : fix/suppressed-spans
delete time in 7 hours
delete branch microsoft/ApplicationInsights-node.js
delete branch : hectorhdzg/context
delete time in 7 hours
delete branch microsoft/ApplicationInsights-node.js
delete branch : users/ramthi/resolveconflicts
delete time in 7 hours
delete branch microsoft/ApplicationInsights-node.js
delete branch : markwolff/revert-static-state
delete time in 7 hours
delete branch microsoft/ApplicationInsights-node.js
delete branch : markwolff/change-setup-overwrites
delete time in 7 hours
delete branch microsoft/ApplicationInsights-node.js
delete branch : markwolff/add-disable-correlation-envvar
delete time in 7 hours
delete branch microsoft/ApplicationInsights-node.js
delete branch : hectorhdzg/1_8_9_release
delete time in 7 hours
delete branch microsoft/ApplicationInsights-node.js
delete branch : hectorhdzg/requestprotocol
delete time in 7 hours
delete branch microsoft/ApplicationInsights-node.js
delete branch : feature/add-standard-metrics
delete time in 7 hours
delete branch microsoft/ApplicationInsights-node.js
delete branch : hectorhdzg/envelopeinterface
delete time in 7 hours
issue commentnodejs/build
Introduction: I'm John. How can I help?
Have we lost our opportunity to collaborate here? Or can we pick this up again?
comment created time in 8 hours
push eventmicrosoft/ApplicationInsights-node.js
commit sha 42cfda06b451c4fc8ec2d3487b47d245b5fa9e09
1.8.9 release (#718) * 1.8.9 release * Updating package.json
push time in 8 hours
PR merged microsoft/ApplicationInsights-node.js
pr closed time in 8 hours
created tagmicrosoft/ApplicationInsights-node.js
Microsoft Application Insights SDK for Node.js
created time in 8 hours
issue commentnodejs/build
citgm-smoker fails on test-ibm-rhel7-s390x-2 with "not found: npm" with npm 7.4.2
A folder.
comment created time in 9 hours
push eventmicrosoft/ApplicationInsights-node.js
commit sha aa283b4425e46f41b47ddf11f35882a5d201d9b0
Updating package.json
push time in 9 hours
issue commentnodejs/build
citgm-smoker fails on test-ibm-rhel7-s390x-2 with "not found: npm" with npm 7.4.2
Is /home/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker
itself an actual folder or is it a symlink?
comment created time in 9 hours
issue commentnodejs/build
citgm-smoker fails on test-ibm-rhel7-s390x-2 with "not found: npm" with npm 7.4.2
/cc @nodejs/npm as a heads up!
comment created time in 9 hours
issue commentnodejs/build
citgm-smoker fails on test-ibm-rhel7-s390x-2 with "not found: npm" with npm 7.4.2
FWIW with loglevel silly
we can see:
With https://github.com/nodejs/node/commit/1f287b04a20a9c69987703ff341d9c1085018238, https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2583/nodes=rhel7-s390x/console
19:11:35 npm timing idealTree:buildDeps Completed in 9024ms
19:11:35 npm timing idealTree:fixDepFlags Completed in 3ms
19:11:35 npm timing idealTree Completed in 9034ms
19:11:35 npm timing reify:loadTrees Completed in 9156ms
19:11:35 npm sill reify mark deleted [
19:11:35 npm sill reify '/data/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker/lib/node_modules/npm',
19:11:35 npm sill reify '/data/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker/lib/node_modules/.bin/npm',
19:11:35 npm sill reify '/data/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker/lib/node_modules/.bin/npx'
19:11:35 npm sill reify ]
19:11:35 npm timing reify:diffTrees Completed in 8ms
19:11:35 npm sill reify mark retired [
19:11:35 npm sill reify '/data/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker/lib/node_modules/npm',
19:11:35 npm sill reify '/data/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker/lib/node_modules/.bin/npm',
19:11:35 npm sill reify '/data/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker/lib/node_modules/.bin/npx'
19:11:35 npm sill reify ]
19:11:35 npm sill reify moves {
19:11:35 npm sill reify '/data/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker/lib/node_modules/npm': '/data/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker/lib/node_modules/.npm-XSSEkfPA',
19:11:35 npm sill reify '/data/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker/lib/node_modules/.bin/npm': '/data/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker/lib/node_modules/.bin/.npm-by5McUm2',
19:11:35 npm sill reify '/data/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker/lib/node_modules/.bin/npx': '/data/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker/lib/node_modules/.bin/.npx-80vfLtlW'
19:11:35 npm sill reify }
19:11:35 npm timing reify:retireShallow Completed in 4ms
19:11:35 npm timing reify:createSparse Completed in 23ms
whereas with https://github.com/nodejs/node/commit/f8ab632d56ea15c78b1dc5db1624109a2bf7b69b (commit before npm 7.4.2 update), https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2582/nodes=rhel7-s390x/consoleFull:
18:10:56 npm timing idealTree:buildDeps Completed in 7652ms
18:10:56 npm timing idealTree:fixDepFlags Completed in 3ms
18:10:56 npm timing idealTree Completed in 7662ms
18:10:56 npm timing reify:loadTrees Completed in 7778ms
18:10:56 npm timing reify:diffTrees Completed in 2ms
18:10:56 npm sill reify moves {}
18:10:56 npm timing reify:retireShallow Completed in 0ms
18:10:56 npm timing reify:createSparse Completed in 19ms
comment created time in 10 hours
issue commentnodejs/diagnostics
Node.js Diagnostics WorkGroup Meeting 2021-01-20
Yeah if the repo doesn't have a diag-agenda label yet, you can create a new one :)
comment created time in 10 hours
issue commentnodejs/diagnostics
Node.js Diagnostics WorkGroup Meeting 2021-01-20
@mmarchini There is not diag-agenda label in this repository. The automated tool will recognize?
comment created time in 10 hours
push eventmicrosoft/ApplicationInsights-node.js
commit sha bf3d2b940489a6be8054820c51f328d2211dbc24
build(deps): bump ini from 1.3.5 to 1.3.7 (#715) Bumps [ini](https://github.com/isaacs/ini) from 1.3.5 to 1.3.7. - [Release notes](https://github.com/isaacs/ini/releases) - [Commits](https://github.com/isaacs/ini/compare/v1.3.5...v1.3.7) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Hector Hernandez <39923391+hectorhdzg@users.noreply.github.com>
commit sha 2605117f3485487c510a46aa5679f12176ab6490
Http.createServer is missing the options variable (#629) * Release 1.4.0 (#531) * add live metrics (#494) * add QPS files; enablement not included * add tests; add qps ping retry walkback * add off by default config option for QPS * add qps test to ensure off by default * only construct qps when enabled * add qps Sender constants * add QuickPulseEnvelopeFactory * fix ts timer compile * add qps exception and trace error handling * refactor default live metrics test * make qps hostname configurable * fix node0 setTimeout error * add qps telemetrytype constants * move away from export enums for ts backcompat * add qps EventDocument,fix dependency duration * use envelope type in qps telemetryprocessor * send avg execution duration instead of last dur * add error logging for qps endpoint * add telemetry types, move qps config to qpssender * fix keying type issue in TelemetryType * fix wrong telemetrytype in qps conversion (#500) * bump version to 1.3.0 (#501) * bump version to 1.3.0 * add setSendLiveMetrics to README * livemetrics: add lastSendSucceeded to prevent permanent retries (#504) * add lastSendSucceeded to prevent permanent retries * add qps time constants, remove static class state * fix request averages being NaN * bump to 1.3.1 (#505) * update diagnostic-channel-publishers to 0.3.1 (#509) * update diagnostic-channel-publishers to 0.3.1 * updates for node12 compat * run functionals on node12 * only log extended duration QPS errors (#511) * only log extended duration QPS errors * refactor QPS error logging * cleanup QPS error logging * readme: document live metrics host config option * Fix typos in readme.md (#517) * parse nonstring request-context header (#521) * parse nonstring request-context header * refactor header parsing, add try/catch on fallback * move includeCorrelationHeader to Util * add node.js native metrics (#508) * release 1.3.0 (#502) * add live metrics (#494) * add QPS files; enablement not included * add tests; add qps ping retry walkback * add off by default config option for QPS * add qps test to ensure off by default * only construct qps when enabled * add qps Sender constants * add QuickPulseEnvelopeFactory * fix ts timer compile * add qps exception and trace error handling * refactor default live metrics test * make qps hostname configurable * fix node0 setTimeout error * add qps telemetrytype constants * move away from export enums for ts backcompat * add qps EventDocument,fix dependency duration * use envelope type in qps telemetryprocessor * send avg execution duration instead of last dur * add error logging for qps endpoint * add telemetry types, move qps config to qpssender * fix keying type issue in TelemetryType * fix wrong telemetrytype in qps conversion (#500) * bump version to 1.3.0 (#501) * bump version to 1.3.0 * add setSendLiveMetrics to README * add native metrics subscriber * mark native members of NativePerformance as static * remove segfault lib * update package.json * native: add throw tests * add refs to metrics * add config for enabling metrics, add heap metrics * report stdDev stats * rename custom metric names * fix native perf test * only run tests for node4+ * use node-pre-gyp native metrics * optionaldevdep for travis tests * simulate optionalDevDependency in travis * remove duped travis npm install * gate native metrics to node6+ * refactor extended metrics enablement * move extended metrics arg parsing to API * add info logging for when native module is loaded * docs: add extended metrics * add extended metrics build stage * use env var for travis extended metrics tests * test: modify test for non-installed case * tweak travis.yml * readme: comment out docs * ship mapfiles (#526) * ship mapfiles * tsconfig: inline TS in sourcemaps * qps: never change ping state on errors (#525) * qps: only pinging state for consecutive errors * qps: do not change state on errors * add w3c distributed tracing (#519) * add w3c distributed tracing * TraceParent/TraceState to Traceparent/Tracestate * traceparent lint errors * Rename rest of Tracestate/Traceparent * temp del * re-add Traceparent/Tracestate * tests: remove ambiguous url * refactor traceparent parsing in HttpRequestParser * add if guard on unneeded request parsing * trim traceparent header only once * disable qps only on consec errors * revert qps change * resolve merge conflicts * use enum for w3c enablement * remove dead code * move isValidW3CId to Util * create traceparent if tracestate exists * tests: add util import to httprequestparser * bump to 1.4.0 (#527) * docs: add w3c to readme (#528) * docs: add w3c to readme * docs: add default tracing mode * release 1.3.0 (#502) (#530) * add live metrics (#494) * add QPS files; enablement not included * add tests; add qps ping retry walkback * add off by default config option for QPS * add qps test to ensure off by default * only construct qps when enabled * add qps Sender constants * add QuickPulseEnvelopeFactory * fix ts timer compile * add qps exception and trace error handling * refactor default live metrics test * make qps hostname configurable * fix node0 setTimeout error * add qps telemetrytype constants * move away from export enums for ts backcompat * add qps EventDocument,fix dependency duration * use envelope type in qps telemetryprocessor * send avg execution duration instead of last dur * add error logging for qps endpoint * add telemetry types, move qps config to qpssender * fix keying type issue in TelemetryType * fix wrong telemetrytype in qps conversion (#500) * bump version to 1.3.0 (#501) * bump version to 1.3.0 * add setSendLiveMetrics to README * Http.createServer is missing the options variable * Add overload for non-options createserver * Temporary commit, should be ready? * Reverting unnecessary changes. updating overload logic * Reverting extra space Co-authored-by: Mark Wolff <Mark.Wolff@microsoft.com> Co-authored-by: Hector Hernandez <39923391+hectorhdzg@users.noreply.github.com> Co-authored-by: Xiao Li <lixiao900921@gmail.com> Co-authored-by: Hector Hernandez Guzman <hectorh@microsoft.com>
commit sha 9c4c97fbc20e72ebc0232f45f77297f556889cbb
Use request.protocol when available in automatic dependency collection (#720) * Use request.protocol when available in automatic dependency collection * Revert "Http.createServer is missing the options variable (#629)" This reverts commit 2605117f3485487c510a46aa5679f12176ab6490. * Revert "Revert "Http.createServer is missing the options variable (#629)"" This reverts commit 9a95598f9221aae50e865ebc68277fee61a05d29.
commit sha 76c4c203375549ec13963d6fcc6552994c6cf9b4
Merge branch 'develop' into hectorhdzg/1_8_9_release
push time in 11 hours
issue openednodejs/build
citgm-smoker fails on test-ibm-rhel7-s390x-2 with "not found: npm" with npm 7.4.2
Since the npm 7.4.2 update landed in Node.js (https://github.com/nodejs/node/pull/36953) the citgm-smoker
job has been failing on test-ibm-rhel7-s390x-2
with error:
error: failure | not found: npm
The citgm-smoker
job:
- Builds Node.js
- Installs the built Node.js into a clean (i.e. removed beforehand)
smoker
directory - Runs
npm install --prefix=/home/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker --global --loglevel=error citgm
to install citgm - Runs
citgm-all -J
Further investigation shows that although the symlinks for npm are in smoker/bin
the targets are not there:
[iojs@test-ibm-rhel7-s390x-2 smoker]$ ls -al
total 40
drwxr-xr-x 6 iojs iojs 4096 Jan 19 09:52 .
drwxr-xr-x 5 iojs iojs 4096 Jan 19 09:52 ..
drwxr-xr-x 2 iojs iojs 4096 Jan 19 09:52 bin
drwxr-xr-x 3 iojs iojs 4096 Jan 19 09:52 include
drwxr-xr-x 3 iojs iojs 4096 Jan 19 09:52 lib
-rw-r--r-- 1 iojs iojs 14690 Jan 19 09:52 report.xml
drwxr-xr-x 5 iojs iojs 4096 Jan 19 09:52 share
[iojs@test-ibm-rhel7-s390x-2 smoker]$ ls -al bin/
total 76664
drwxr-xr-x 2 iojs iojs 4096 Jan 19 09:52 .
drwxr-xr-x 6 iojs iojs 4096 Jan 19 09:52 ..
lrwxrwxrwx 1 iojs iojs 38 Jan 19 09:52 citgm -> ../lib/node_modules/citgm/bin/citgm.js
lrwxrwxrwx 1 iojs iojs 42 Jan 19 09:52 citgm-all -> ../lib/node_modules/citgm/bin/citgm-all.js
-rwxr-xr-x 1 iojs iojs 78492160 Jan 19 09:52 node
lrwxrwxrwx 1 iojs iojs 38 Jan 19 09:52 npm -> ../lib/node_modules/npm/bin/npm-cli.js
lrwxrwxrwx 1 iojs iojs 38 Jan 19 09:52 npx -> ../lib/node_modules/npm/bin/npx-cli.js
[iojs@test-ibm-rhel7-s390x-2 smoker]$ ls -al lib/node_modules/
total 16
drwxr-xr-x 4 iojs iojs 4096 Jan 19 09:52 .
drwxr-xr-x 3 iojs iojs 4096 Jan 19 09:52 ..
drwxr-xr-x 2 iojs iojs 4096 Jan 19 09:52 .bin
drwxr-xr-x 5 iojs iojs 4096 Jan 19 09:52 citgm
[iojs@test-ibm-rhel7-s390x-2 smoker]$
In fact the entire npm
directory is missing from smoker/lib/node_modules
. A look at the logs suggests npm has unexpectedly removed a lot of packages at the install citgm step:
e.g. https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2574/nodes=rhel7-s390x/console
14:52:40 + npm install --prefix=/home/iojs/build/workspace/citgm-smoker/nodes/rhel7-s390x/smoker --global --loglevel=error citgm
14:52:40
14:52:48 added 209 packages, removed 251 packages, and audited 210 packages in 8s
14:52:48
14:52:48 15 packages are looking for funding
14:52:48 run `npm fund` for details
14:52:48
14:52:48 found 0 vulnerabilities
Further investigation has revealed:
- Wiping out the workspace (effectively wiping the npm cache) and rebuilding has no effect (failure still persists).
- The failure is only observed on
test-ibm-rhel7-s390x-2
. It doesn't occur ontest-ibm-rhel7-s390x-1
,test-ibm-rhel7-s390x-4
or any of the other platforms. - The failure doesn't occur on
test-ibm-rhel7-s390x-2
when building the commit (https://github.com/nodejs/node/commit/f8ab632d56ea15c78b1dc5db1624109a2bf7b69b) immediately prior to the npm 7.4.2 update: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2582/nodes=rhel7-s390x/
Only occurring on test-ibm-rhel7-s390x-2
would suggest perhaps a machine specific issue but so far I've not been able to find an obvious difference between it and the other non-affected machines. As the problem only occurs on commits after the npm 7.4.2 update it could also be a regression in npm, but we're not seeing the problem elsewhere.
I'm going to take test-ibm-rhel7-s390x-2
offline temporarily.
cc @nodejs/releasers @nodejs/npm
created time in 11 hours
issue closednodejs/diagnostics
Node.js Diagnostics WorkGroup Meeting 2021-01-20
Time
UTC Wed 20-Jan-2021 17:30 (05:30 PM):
Timezone | Date/Time |
---|---|
US / Pacific | Wed 20-Jan-2021 09:30 (09:30 AM) |
US / Mountain | Wed 20-Jan-2021 10:30 (10:30 AM) |
US / Central | Wed 20-Jan-2021 11:30 (11:30 AM) |
US / Eastern | Wed 20-Jan-2021 12:30 (12:30 PM) |
EU / Western | Wed 20-Jan-2021 17:30 (05:30 PM) |
EU / Central | Wed 20-Jan-2021 18:30 (06:30 PM) |
EU / Eastern | Wed 20-Jan-2021 19:30 (07:30 PM) |
Moscow | Wed 20-Jan-2021 20:30 (08:30 PM) |
Chennai | Wed 20-Jan-2021 23:00 (11:00 PM) |
Hangzhou | Thu 21-Jan-2021 01:30 (01:30 AM) |
Tokyo | Thu 21-Jan-2021 02:30 (02:30 AM) |
Sydney | Thu 21-Jan-2021 04:30 (04:30 AM) |
Or in your local time:
- https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Diagnostics%20WorkGroup+Meeting+2021-01-20&iso=20210120T1730
- or https://www.wolframalpha.com/input/?i=05PM+UTC%2C+Jan+20%2C+2021+in+local+time
Links
- Minutes Google Doc: https://docs.google.com/document/d/1NM3yhvrs12TapOnjF5qSxFOcRaZ43uQh5nvPKTMrla8/edit
Agenda
Extracted from diag-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
Invited
- Diagnostics team: @nodejs/diagnostics
Observers/Guests
Notes
The agenda comes from issues labelled with diag-agenda
across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting
- link for participants: https://zoom.us/j/466707925
- For those who just want to watch:
- youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled
closed time in 11 hours
mhdawsonissue commentnodejs/diagnostics
Node.js Diagnostics WorkGroup Meeting 2021-01-20
Sorry, forgot to comment here. Yes, today was cancelled, let's talk in two weeks!
@RafaelGSS please add the diag-agenda
label to https://github.com/nodejs/node-inspect/pull/99 :)
comment created time in 11 hours