profile
viewpoint
Matthew Gabeler-Lee mgabeler-lee-6rs

mgabeler-lee-6rs/nodejs-pubsub 1

Node.js client for Google Cloud Pub/Sub: Ingest event streams from anywhere, at any scale, for simple, reliable, real-time stream analytics.

6RiverSystems/pubsub-emulator-docker 0

A Docker image for running the Google Cloud PubSub emulator

mgabeler-lee-6rs/DefinitelyTyped 0

The repository for high quality TypeScript type definitions.

mgabeler-lee-6rs/grpc-node-issue-1347 0

repro attempt for https://github.com/grpc/grpc-node/issues/1347

mgabeler-lee-6rs/lb4-rest-filter 0

Demo of https://github.com/strongloop/loopback-connector-rest/issues/136

mgabeler-lee-6rs/loopback-datasource-juggler 0

Connect Loopback to various Data Sources

mgabeler-lee-6rs/loopback-next 0

LoopBack makes it easy to build modern API applications that require complex integrations.

mgabeler-lee-6rs/mkdirp-promise 0

Promise version of mkdirp

mgabeler-lee-6rs/rush-busted 0

Test/demo repo for various rush bugs

delete branch 6RiverSystems/rush-monorepo-boilerplate

delete branch : master

delete time in 16 hours

create barnch6RiverSystems/rush-monorepo-boilerplate

branch : main

created branch time in 16 hours

Pull request review comment6RiverSystems/github-default-branch

Fix/replacements contract

 const replaceAll = require("string.prototype.replaceall");  const ls = util.promisify(fs.readdir); -module.exports = async function (-  owner,-  repo,-  old,-  target,-  octokit,-  isVerbose,-  isDryRun,-) {-  const files = (await ls(`${__dirname}/../replacements`)).filter((f) => f.endsWith('.js'));+module.exports = async function (context) {

options?

tonygaetani

comment created time in 18 hours

started6RiverSystems/github-default-branch

started time in 3 days

issue commentgrantila/fetch-h2

Not working node v14.2.0

Anyone have insight on what nodejs commits broke/fixed this so we can request them to be reverted in / backported to 12.x?

sharper

comment created time in 4 days

issue commentcli/cli

Allow editing the commit message when squash-merging a PR

I'd like to be able to edit the commit message for all merges, not just squash ones.

My use case: I want/need my merge commits to have a conventional commit format to support semrel automation

g0tsimid

comment created time in 17 days

issue commentstrongloop/loopback-next

Juggler stores null objects as string "null" instead of value null in relational datasources

I should also call out the test case in the sample repo, storing nulls as the string know prevents actually being able to locate those records with queries, not to mention making it impossible to write good database constraints, for example checking if a column is no based on the value of another column

mgabeler-lee-6rs

comment created time in 22 days

issue commentstrongloop/loopback-next

Juggler stores null objects as string "null" instead of value null in relational datasources

For non object properties, nulls are stored as SQL NULL. Object properties stored as JSON should be consistent with this.

Also, SQL NULL values are returned as null, not undefined as you suggest, at least with the PostgreSQL connector.

Also also, storing SQL NULL is far more idiomatic, and more efficient (e.g. PostgreSQL just keeps a bitmap of the null/not-null columns in a row, so storing NULL takes zero bytes), not to mention interoperable.

mgabeler-lee-6rs

comment created time in 22 days

create barnchmgabeler-lee-6rs/loopback-next

branch : issue/5764

created branch time in 24 days

issue openedstrongloop/loopback-next

Juggler tries to store null objects as string "null" instead of value null

Note: this is actually a bug in strongloop/loopback-datasource-juggler, but the issue template there specifically instructs to report the issue here when working with LB4, so ...

Steps to reproduce

  • Create an entity type with an Object property
  • Map this to a JSON/JSONB column in PostgreSQL
    • This bug is visible if you map it to a textual column in any other DB too I think
  • Make the property & column accept NULL values
  • Try to save a instance with this property as null

Current Behavior

Juggler sees it is an object column and unconditionally uses JSON.stringify to prepare the value for the database: https://github.com/strongloop/loopback-datasource-juggler/blob/master/lib/dao.js#L183

Expected Behavior

null in JS/TS land should become NULL in the database, not a not-null value containing the string or JSON value null.

Put another way, if you save null, it should show up when you do a select ... where column is null.

Link to reproduction sandbox

WIP

Additional information

  • node version info: linux x64 10.17.0
  • dependency info: using rush so suggested command doesn't work, but ...
    • "@loopback/repository": "2.4.0"
    • loopback-datasource-juggler: 4.21.2

Related Issues

Haven't found any yet

created time in 24 days

issue commentmicrosoft/vscode

"Server returned 404" when trying to install different versions of extensions in VS Code

This is now working for me for some extensions, but not all. Not sure if this is a CDN issue or what?

luabud

comment created time in 24 days

issue commentMermade/oas-kit

HTTP2 simple test fails and hangs with node 12.17.0 & 12.18.0

package-lock.json is not published, it's only relevant when developing speccy. In our use case, we install speccy within our package as a devDependency as if it were a library, and use it as part of our CI workflow's linting step. But even if you did npm i -g speccy, the package-lock.json would still not be used due to it not being part of published packages. There is a separate npm-shrinkwrap.json (https://docs.npmjs.com/cli/shrinkwrap) that can apply dependency locks in a published package, but Speccy doesn't seem to use that.

mgabeler-lee-6rs

comment created time in 24 days

issue commentMermade/oas-kit

HTTP2 simple test fails and hangs with node 12.17.0 & 12.18.0

Speccy is, as far as I can tell, unmaintained so will never take a new version of oas-kit

Speccy uses caret versions, so if a new version of oas-kit publishes that is compatible with it, it likely will get picked up on a fresh npm install

so if that's your use-case you'll need to migrate to oas-kit's boast or spectral anyway.

Was looking around for alternatives to speccy because of this, at first glance boast looks like it might fit our needs, thanks for the pointers :+1:

mgabeler-lee-6rs

comment created time in 24 days

issue openedMermade/oas-kit

HTTP2 simple test fails and hangs with node 12.17.0 & 12.18.0

Checklist

  • [ ] Resolver issue

Detailed Description

With node 12.17.0 or 12.18.0:

$ npm test
...
  101 passing (2s)
  1 failing

  1) HTTP2 tests
       simple
         should match expected output:
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/mgl/3psrc/oas-kit/test/http2.test.js)
      at listOnTimeout (internal/timers.js:549:17)
      at processTimers (internal/timers.js:492:7)

and it hangs at this point, at least for a while.

Passes on 12.16.3

Other stuff

This is basically #223 again, but for the versions of node listed as supported, and is actively broken. One can have node LTS security fixes, or a working version of this package, but not both right now. That prior issue suggested 14.1.0 is where it broke and 14.3.0 fixed it, but didn't manage to identify an actual root cause change in either of those versions. I'd happily champion requesting a bugfix be backported to 12.x, but my node internals fu is not strong enough to identify which one is the problem there. I'm hoping someone here can help there.

See also wework/speccy#422

created time in 24 days

issue commentgoogleapis/nodejs-pubsub

Should be possible to nack a message for delayed redelivery

To save folks that come here and are about to ask the question I was going to of "how": #1029

From some UTSL: it looks like the basic answer is "use subscription.setMetadata, there is a retryPolicy member in there".

mgabeler-lee-6rs

comment created time in 25 days

issue commenthisco/http2-client

Tests hang

Possibly also related: https://github.com/grantila/fetch-h2/issues/104

stefan-guggisberg

comment created time in a month

issue commentwework/speccy

Hangs resolving external references with NodeJS >= 12.17.0

Addendum, root cause may be related to https://github.com/grantila/fetch-h2/issues/104 as well

mgabeler-lee-6rs

comment created time in a month

issue openedwework/speccy

Hangs resolving external references with NodeJS >= 12.17.0

Detailed description

When running with NodeJS 12.17.0 or higher, speccy (esp. speccy lint) hangs when attempting to resolve external resources that come over HTTP/2.

Context

This renders speccy unusable by my team in our efforts to track NodeJS LTS releases.

I believe this is caused by https://github.com/hisco/http2-client/issues/26#issuecomment-644445967 -- not strictly speccy's fault, but speccy is dramatically affected.

Possible implementation

Not sure if speccy folks could help fix this issue in the underlying libraries, or adjust to a different HTTP/2 client library

Your environment

  • Node Version: 12.x (via nodenv)
  • Operating system and version: Linux (Debian) and macOS (various recent releases)

Demo file: note that the fact that the referenced URL is a 404 doesn't matter, because the nature of this bug is such that speccy and its dependencies never see the response anyways. It does matter that example.com serves HTTP/2.

openapi: 3.0.2
components:
  x:
    $ref: 'https://example.com/invalid.yaml'

Install node 12.17.0 or higher and just run npx speccy lint --verbose demo.yaml, or to see the full trace details, NODE_OPTIONS=--trace-tls NODE_DEBUG='*' npx speccy lint --verbose demo.yaml

created time in a month

issue commenthisco/http2-client

Tests hang

I ran into a similar issue that I believe has the same root cause. In my case, speccy (https://github.com/wework/speccy) hangs when it is trying to download external references from servers that support HTTP/2.

I was able to bisect this to having been introduced in nodejs 12.17.0.

I ran with lots of node trace/debug stuff enabled, and comparing the succeeding and failing logs, I suspect that this was introduced by https://github.com/nodejs/node/pull/32958, but that's hard for me to verify.


Some snippets of debug traces (NODE_OPTIONS=--trace-tls NODE_DEBUG=*) from where they start differing (note: this is a speccy lint run, but the code that's running at this point is from this package). This starts just after the certificate exchange.

Working with 12.16.3:

TLS 301274: client onhandshakedone
TLS 301274: client _finishInit handle? true alpn h2 servername <snip>
TLS 301274: client emit secureConnect. authorized: true
HTTP2 301274: Http2Session client: setting up session handle
HTTP2 301274: Http2Session client: sending settings
HTTP2 301274: Http2Session client: submitting settings
HTTP2 301274: Http2Session client: created
HTTP2 301274: Http2Session client: initiating request
HTTP2 301274: Http2Session client: connected, initializing request
STREAM 301274: resume
(node:301274) Warning: Setting the NODE_DEBUG environment variable to 'http2' can expose sensitive data (such as passwords, tokens and authentication headers) in the resulting log.
HTTP2 301274: Http2Stream 1 [Http2Session client]: _final shutting down
STREAM 301274: resume false
STREAM 301274: read 0
STREAM 301274: need readable false
STREAM 301274: length less than watermark true
STREAM 301274: do read
STREAM 301274: flow true
STREAM 301274: read undefined
STREAM 301274: need readable true
STREAM 301274: length less than watermark true
STREAM 301274: reading or ended false
Sent Record
Header:
  Version = TLS 1.2 (0x303)
  Content Type = ApplicationData (23)
  Length = 162
  Inner Content Type = ApplicationData (23)
Received Record
Header:
  Version = TLS 1.2 (0x303)
  Content Type = ApplicationData (23)
  Length = 545
  Inner Content Type = Handshake (22)
    NewSessionTicket, Length=260
        ticket_lifetime_hint=172800
        ticket_age_add=858443592
        ticket_nonce (len=1): 00
        ticket (len=242): <snip>
        extensions, length = 4
          extension_type=UNKNOWN(27242), length=0

    NewSessionTicket, Length=260
        ticket_lifetime_hint=172800
        ticket_age_add=2125917300
        ticket_nonce (len=1): 01
        ticket (len=242): <snip>
        extensions, length = 4
          extension_type=UNKNOWN(27242), length=0

Received Record
Header:
  Version = TLS 1.2 (0x303)
  Content Type = ApplicationData (23)
  Length = 57
  Inner Content Type = ApplicationData (23)
Sent Record
Header:
  Version = TLS 1.2 (0x303)
  Content Type = ApplicationData (23)
  Length = 26
  Inner Content Type = ApplicationData (23)
Received Record
Header:
  Version = TLS 1.2 (0x303)
  Content Type = ApplicationData (23)
  Length = 26
  Inner Content Type = ApplicationData (23)
HTTP2 301274: Http2Session client: settings received
Received Record
Header:
  Version = TLS 1.2 (0x303)
  Content Type = ApplicationData (23)
  Length = 172
  Inner Content Type = ApplicationData (23)
HTTP2 301274: Http2Stream 1 [Http2Session client]: headers received
HTTP2 301274: Http2Stream 1 [Http2Session client]: emitting stream 'response' event

The response finishes from here.

Failing with 12.17.0:

TLS 301302: client onhandshakedone
TLS 301302: client _finishInit handle? true alpn h2 servername <snip>
TLS 301302: client emit secureConnect. authorized: true
HTTP2 301302: Http2Session client: created
HTTP2 301302: Http2Session client: initiating request
STREAM 301302: resume
(node:301302) Warning: Setting the NODE_DEBUG environment variable to 'http2' can expose sensitive data (such as passwords, tokens and authentication headers) in the resulting log.
STREAM 301302: resume false
STREAM 301302: read 0
STREAM 301302: need readable false
STREAM 301302: length less than watermark true
STREAM 301302: do read
STREAM 301302: flow true
STREAM 301302: read undefined
STREAM 301302: need readable true
STREAM 301302: length less than watermark true
STREAM 301302: reading or ended false
Received Record
Header:
  Version = TLS 1.2 (0x303)
  Content Type = ApplicationData (23)
  Length = 545
  Inner Content Type = Handshake (22)
    NewSessionTicket, Length=260
        ticket_lifetime_hint=172800
        ticket_age_add=169979864
        ticket_nonce (len=1): 00
        ticket (len=242): <snip>
        extensions, length = 4
          extension_type=UNKNOWN(43690), length=0

    NewSessionTicket, Length=260
        ticket_lifetime_hint=172800
        ticket_age_add=1669237012
        ticket_nonce (len=1): 01
        ticket (len=242): <snip>
        extensions, length = 4
          extension_type=UNKNOWN(43690), length=0

Received Record
Header:
  Version = TLS 1.2 (0x303)
  Content Type = ApplicationData (23)
  Length = 57
  Inner Content Type = ApplicationData (23)
STREAM 301302: readableAddChunk <Buffer <snip>>
STREAM 301302: emitReadable true false
STREAM 301302: emitReadable null
STREAM 301302: emitReadable_ false 40 false
STREAM 301302: flow null
STREAM 301302: maybeReadMore read 0
STREAM 301302: read 0
STREAM 301302: need readable true
STREAM 301302: length less than watermark true
STREAM 301302: do read
NET 301302: _read

The app hangs from here.

stefan-guggisberg

comment created time in a month

issue commenthashicorp/vscode-terraform

Shouldn't try to start the language server for non-terraform workspaces

Is there a way to use this extension just for the syntax highlighting?

And code formatting? Running terraform format doesn't require the language server, but with the new release, if the language server fails to initialize, code formatting doesn't work.

mgabeler-lee-6rs

comment created time in a month

issue commenthashicorp/vscode-terraform

Shouldn't try to start the language server for non-terraform workspaces

I guess I do have some .tf files buried deep within one of the repos in my multi-repo workspace. But it complains about a different repo (the first one in the workspace).

Also, even if I do do terraform init ... it still complains. But I think that is covered by e.g. #366 and others

mgabeler-lee-6rs

comment created time in a month

issue commentmicrosoft/vscode

"Server returned 404" when trying to install different versions of extensions in VS Code

I'm seeing this error with vscode 1.45.1 and 1.46.0 (Linux Debian amd64) with all extensions.

Running under code --verbose, I get the attached log snippet (I trimmed everything before I hit the "install another version" and after it reported the "404" error. Spot checking the URLs it says it hits I'm not getting any 404s in my browser, so not sure where the error is coming from.

try-get-go-versions.log

luabud

comment created time in a month

issue closedhashicorp/vscode-terraform

Instructions for installing older versions do not work due to extension id change

The README recommends installing an old version for support of Terraform < 0.12, however the instructions provided do not work.

The change of the extension identity means you cannot downgrade the extension any more, so once you upgrade, you're stuck.

Can the .vsix files for old versions be attached to the GitHub releases perhaps so they can be side-loaded?

closed time in a month

mgabeler-lee-6rs

issue commenthashicorp/vscode-terraform

Instructions for installing older versions do not work due to extension id change

Nevermind, I think this is https://github.com/microsoft/vscode/issues/99699 instead ... no less frustrating for it however... this extension went from "handy" to "completely unusable" with the 2.0 release for me :sob:

mgabeler-lee-6rs

comment created time in a month

issue openedhashicorp/vscode-terraform

Instructions for installing older versions do not work due to extension id change

The README recommends installing an old version for support of Terraform < 0.12, however the instructions provided do not work.

The change of the extension identity means you cannot downgrade the extension any more, so once you upgrade, you're stuck.

Can the .vsix files for old versions be attached to the GitHub releases perhaps so they can be side-loaded?

created time in a month

issue openedhashicorp/vscode-terraform

Shouldn't try to start the language server for non-terraform workspaces

I use several vscode workspaces. Only one of them has any terraform files.

Having this extension tell me to run terraform init in every non-terraform workspace/repo is ... quite annoying.

Yes, it's possible to disable it per workspace, but ... that is not normal for language extensions in my experience with vscode (or any other editor/IDE). The C++ tooling doesn't pop up notification toasts that it failed to compile my non-existent C++ code every time I open a TypeScript or Go workspace, for example.

created time in a month

push event6RiverSystems/rush-monorepo-boilerplate

Matthew Gabeler-Lee

commit sha 6865336a5d1613d4b25dff53d9696c0073719dec

fix: lint

view details

push time in 2 months

delete branch 6RiverSystems/blackboard

delete branch : fix/security

delete time in 2 months

push event6RiverSystems/blackboard

Matthew Gabeler-Lee

commit sha 004a9a9af40383ab9ab8e096bc598438ea38cb1e

fix: npm audit fix --force

view details

Matthew Gabeler-Lee

commit sha 99b98fe3c5dddc52c52e810a2e929ef49c10dcf8

fix: Update AllTheThings

view details

Matthew Gabeler-Lee

commit sha bbfee39503d654ebe0adecc31bf16530dbc765dc

fix: node 10 in circle too

view details

Matthew Gabeler-Lee

commit sha 12fccc74313c2cbdea204f48a83b55a9108e3ba3

fix: aargh

view details

Matthew Gabeler-Lee

commit sha 74d14b54a475298a5c4ce0556d4591df00907623

fix: Really `npm update` All. The. Things.

view details

Matthew Gabeler-Lee

commit sha 0efbd63b3df83d9862604cfeb54305ebf752cb77

fix: Merge pull request #16 from 6RiverSystems/fix/security fix: npm audit fix --force (CUR-69)

view details

push time in 2 months

pull request comment6RiverSystems/blackboard

fix: npm audit fix --force (CUR-69)

import order comes from our new eslint config, which I did update

mgabeler-lee-6rs

comment created time in 2 months

pull request comment6RiverSystems/blackboard

fix: npm audit fix --force (CUR-69)

I didn't update some things "all the way", e.g. I stopped typescript at the version the WFM uses right now because Paranoid

mgabeler-lee-6rs

comment created time in 2 months

push event6RiverSystems/blackboard

Matthew Gabeler-Lee

commit sha 74d14b54a475298a5c4ce0556d4591df00907623

fix: Really `npm update` All. The. Things.

view details

push time in 2 months

push event6RiverSystems/blackboard

Matthew Gabeler-Lee

commit sha 12fccc74313c2cbdea204f48a83b55a9108e3ba3

fix: aargh

view details

push time in 2 months

push event6RiverSystems/blackboard

Matthew Gabeler-Lee

commit sha bbfee39503d654ebe0adecc31bf16530dbc765dc

fix: node 10 in circle too

view details

push time in 2 months

pull request comment6RiverSystems/blackboard

fix: npm audit fix --force (CUR-69)

Well, that end up being a baby yak shave ... ended up updating eslint, typescript, and node too...

mgabeler-lee-6rs

comment created time in 2 months

push event6RiverSystems/blackboard

Matthew Gabeler-Lee

commit sha 99b98fe3c5dddc52c52e810a2e929ef49c10dcf8

fix: Update AllTheThings

view details

push time in 2 months

PR opened 6RiverSystems/blackboard

fix: npm audit fix --force
+1149 -239

0 comment

2 changed files

pr created time in 2 months

create barnch6RiverSystems/blackboard

branch : fix/security

created branch time in 2 months

issue commentmicrosoft/tslib

__createBinding assumes exports are readonly

Same issue as #102

dwieeb

comment created time in 2 months

issue commenttypeorm/typeorm

Cannot set property EntityManager of #<Object> which has only a getter

tslib updated which is exposing a pre-existing issue with double-exporting symbols:

  • https://github.com/typeorm/typeorm/blob/master/src/index.ts#L105
  • https://github.com/typeorm/typeorm/blob/master/src/index.ts#L141

TSLib behavior change and other folks having problems with it have been reported there:

  • https://github.com/microsoft/tslib/issues/103
  • https://github.com/microsoft/tslib/issues/102
AuspeXeu

comment created time in 2 months

issue commentlogdna/logdna-cli

SSOLogin Broken

Installing the latest debian package using the instructions in the READM still delivers version 1.2.3, and there are no linux packages in the releases page for newer versions, so ... not verifiable at this time.

FWIW, I also don't use the CLI any more, as I've found it unsuitable to my needs, though this ticket is not the place to go into that :)

mgabeler-lee-6rs

comment created time in 2 months

issue commentfwupd/missing-firmware-lenovo-thinkpad

Lenovo P330 BIOS 1.0.0.81 Changes UEFI Boot Order

I don't believe there is anything fwupd can do about BIOS bugs like this

Certainly :) Just wasn't clear where the right place was to report issues with the capsules themselves. I had hoped fwupd.org would have some info, at least for capsules like this that come from LVFS, but didn't find any.

Hadn't occurred to me that the "missing" firmware project would also take reports for "buggy" firmware updates :)

mgabeler-lee-6rs

comment created time in 2 months

issue openedfwupd/missing-firmware-lenovo-thinkpad

Lenovo P330 BIOS 1.0.0.81 Changes UEFI Boot Order

Describe the bug Installing https://fwupd.org/lvfs/devices/com.lenovo.P330.BIOS.firmware version 1.0.0.81 (which reports in fwupdmgr as 0.1.81 for some reason?) changed my UEFI boot order, causing my system to no longer boot into Linux, but into remnants of a Windows 10 boot loader (all that was left was its UEFI bootloader bits, none of Windows or its recovery partitions were left, so of course if failed to boot, and then powered off the system after a few seconds).

Steps to Reproduce

  • Have a leftover windows bootloader entry after replacing OEM shipped Windows with Linux
  • Have linux set to boot by default for a year or so (this was not a fresh installation)
  • Install the firmware update
  • Watch as your system tries to boot into a non-existent windows installation
  • Furiously try to remember what the keyboard key is to enter BIOS setup, as the BIOS generally fails to get the monitor active before it stops showing you those keys
  • Realize that the BIOS can't change the UEFI order?!
  • Try to remember what the custom boot key is so you can boot into Linux that way and delete the last remaining bits of the broken windows installation and use efibootmgr to get rid of it for good

Expected behavior Installing BIOS/firmware updates should not change the device/OS the computer boots by default.

fwupd version information Please provide the version of the daemon and client.

$ fwupdmgr --version
client version:	1.3.9
compile-time dependency versions
	gusb:	0.3.4
	efivar:	37
daemon version:	1.3.9

Please note how you installed it (apt, dnf, pacman, source, etc): apt, from Debian Bullseye

fwupd device information Please provide the output of the fwupd devices recognized in your system.

$ fwupdmgr get-devices --show-all-devices
30D1CTO1WW
│
├─Intel AMT [unprovisioned]:
│     Device ID:           e2623122c99d58220498aacbfcfdb1baebbae3c5
│     Summary:             Hardware and firmware technology for remote out-of-band management
│     Current version:     12.0.6.1120
│     Bootloader Version:  12.0.6.1120
│     Vendor:              Intel Corporation
│     GUID:                2800f812-b7b4-2d4b-aca8-46e0ff65814c
│     Device Flags:        • Internal device
│   
├─Intel Management Engine:
│     Device ID:           f7d2d252d773165f82be0b53ea8c1a83d2cf800b
│     Current version:     12.0.6.1120
│     Minimum Version:     12.0.6.1120
│     Vendor:              DMI:LENOVO
│     GUID:                5b92717b-2cad-4a96-a13b-9d65781df8bf
│     Device Flags:        • Internal device
│                          • Updatable
│                          • Requires AC power
│                          • Needs a reboot after installation
│                          • Device is usable for the duration of the update
│   
├─SAMSUNG MZVLB512HAJQ-000L7:
│     Device ID:           71b677ca0f1bc2c5b804fa1d59e52064ce589293
│     Summary:             NVM Express Solid State Drive
│     Current version:     5L2QEXA7
│     Vendor:              Samsung Electronics Co Ltd (NVME:0x144D)
│     Serial Number:       S3TNNX0M732756
│     GUIDs:               6e54c992-d302-59ab-b454-2d26ddd63e6d ← NVME\VEN_144D&DEV_A808&REV_00
│                          47335265-a509-51f7-841e-1c94911af66b ← NVME\VEN_144D&DEV_A808
│                          79d6cfae-a5a2-5936-9248-5aebd23480f7 ← SAMSUNG MZVLB512HAJQ-000L7
│     Device Flags:        • Internal device
│                          • Updatable
│                          • Requires AC power
│                          • Supported on remote server
│                          • Needs a reboot after installation
│                          • Device is usable for the duration of the update
│   
├─System Firmware:
│     Device ID:           6e864c667487be72acb296349910341def0b4594
│     Current version:     0.1.81
│     Minimum Version:     0.1.81
│     Vendor:              LENOVO (DMI:LENOVO)
│     GUID:                6bfea39f-87d3-4be0-9afb-39c8632dea45
│     Device Flags:        • Internal device
│                          • Updatable
│                          • Requires AC power
│                          • Supported on remote server
│                          • Needs a reboot after installation
│                          • Cryptographic hash verification is available
│                          • Device is usable for the duration of the update
│   
├─TPM:
│     Device ID:           c6a80ac3a22083423992a3cb15018989f37834d6
│     Current version:     7.63.13.6400
│     Vendor:              Infineon (TPM:IFX)
│     GUIDs:               ff71992e-52f7-5eea-94ef-883e56e034c6 ← system-tpm
│                          5eebb112-75ad-5536-b173-a11eb3399402 ← TPM\VEN_IFX&DEV_0000
│                          ddf995da-1b32-5a8a-bc1b-8d5af4b38b51 ← TPM\VEN_IFX&MOD_SLB9670
│                          6d81ab63-db2e-50ac-934f-6be9accf5e02 ← TPM\VEN_IFX&DEV_0000&VER_2.0
│                          301555de-680d-5ddc-b995-7553fc9138f1 ← TPM\VEN_IFX&MOD_SLB9670&VER_2.0
│     Device Flags:        • Internal device
│   
├─UHD Graphics 630 (Desktop 9 Series):
│     Device ID:           bbbf1ce3d1cf15550c3760b354592040292415bb
│     Current version:     02
│     Vendor:              Intel Corporation (PCI:0x8086)
│     GUIDs:               e9ceb7d8-e213-5ec4-8805-6330d894b317 ← PCI\VEN_8086&DEV_3E98&REV_02
│                          8655a49b-b4b2-54ff-a6c6-06009dd64f13 ← PCI\VEN_8086&DEV_3E98
│     Device Flags:        • Internal device
│                          • Cryptographic hash verification is available
│   
└─Unifying Receiver:
      Device ID:           4588a84d1cfa1ddb273e9df28f6a44927e9b4e99
      Summary:             A miniaturised USB wireless receiver
      Current version:     RQR12.10_B0032
      Bootloader Version:  BOT01.02_B0015
      Vendor:              USB:0x046D
      Install Duration:    30 seconds
      GUIDs:               9d131a0c-a606-580f-8eda-80587250b8d6
                           fcf55bf5-767b-51ce-9c17-f6f538c4ee9f ← HIDRAW\VEN_046D&DEV_C52B&REV_00
                           279ed287-3607-549e-bacc-f873bb9838c4 ← HIDRAW\VEN_046D&DEV_C52B
      Device Flags:        • Updatable
                           • Supported on remote server
    

System UEFI configuration Please provide the output of the following commands:

$ efibootmgr -v
$ sudo efibootmgr -v
BootCurrent: 000B
Timeout: 1 seconds
BootOrder: 000B,0008,0009,000C,000D
Boot0008* UEFI: PXE IPV4 Intel(R) Ethernet Connection (7) I219-LM	PciRoot(0x0)/Pci(0x1f,0x6)/MAC(00d86197098e,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0009* UEFI: PXE IPV6 Intel(R) Ethernet Connection (7) I219-LM	PciRoot(0x0)/Pci(0x1f,0x6)/MAC(00d86197098e,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot000B* debian	HD(1,GPT,f8af0d70-2560-4808-bcb3-843386c46cc7,0x800,0x82000)/File(\EFI\DEBIAN\GRUBX64.EFI)..BO
Boot000C* Generic Usb Device	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot000D* CD/DVD Device	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
$ efivar -l | grep fw
# nothing

Additional questions

  • Operating system and version: Debian Bullseye
  • Have you tried rebooting? Yes
  • Is this a regression? Compared to prior Lenovo update packages, yes. This is probably the 5th or 6th update I have installed on this system. No prior update did this to me.
  • Are you using an NVMe disk? Yes
  • Is secure boot enabled? No

created time in 2 months

issue openedfwupd/fwupd

Lenovo P330 BIOS 1.0.0.81 Changes UEFI Boot Order

Describe the bug Installing https://fwupd.org/lvfs/devices/com.lenovo.P330.BIOS.firmware version 1.0.0.81 (which reports in fwupdmgr as 0.1.81 for some reason?) changed my UEFI boot order, causing my system to no longer boot into Linux, but into remnants of a Windows 10 boot loader (all that was left was its UEFI bootloader bits, none of Windows or its recovery partitions were left, so of course if failed to boot, and then powered off the system after a few seconds).

Steps to Reproduce

  • Have a leftover windows bootloader entry after replacing OEM shipped Windows with Linux
  • Have linux set to boot by default for a year or so (this was not a fresh installation)
  • Install the firmware update
  • Watch as your system tries to boot into a non-existent windows installation
  • Furiously try to remember what the keyboard key is to enter BIOS setup, as the BIOS generally fails to get the monitor active before it stops showing you those keys
  • Realize that the BIOS can't change the UEFI order?!
  • Try to remember what the custom boot key is so you can boot into Linux that way and delete the last remaining bits of the broken windows installation and use efibootmgr to get rid of it for good

Expected behavior Installing BIOS/firmware updates should not change the device/OS the computer boots by default.

fwupd version information Please provide the version of the daemon and client.

$ fwupdmgr --version
client version:	1.3.9
compile-time dependency versions
	gusb:	0.3.4
	efivar:	37
daemon version:	1.3.9

Please note how you installed it (apt, dnf, pacman, source, etc): apt, from Debian Bullseye

fwupd device information Please provide the output of the fwupd devices recognized in your system.

$ fwupdmgr get-devices --show-all-devices
30D1CTO1WW
│
├─Intel AMT [unprovisioned]:
│     Device ID:           e2623122c99d58220498aacbfcfdb1baebbae3c5
│     Summary:             Hardware and firmware technology for remote out-of-band management
│     Current version:     12.0.6.1120
│     Bootloader Version:  12.0.6.1120
│     Vendor:              Intel Corporation
│     GUID:                2800f812-b7b4-2d4b-aca8-46e0ff65814c
│     Device Flags:        • Internal device
│   
├─Intel Management Engine:
│     Device ID:           f7d2d252d773165f82be0b53ea8c1a83d2cf800b
│     Current version:     12.0.6.1120
│     Minimum Version:     12.0.6.1120
│     Vendor:              DMI:LENOVO
│     GUID:                5b92717b-2cad-4a96-a13b-9d65781df8bf
│     Device Flags:        • Internal device
│                          • Updatable
│                          • Requires AC power
│                          • Needs a reboot after installation
│                          • Device is usable for the duration of the update
│   
├─SAMSUNG MZVLB512HAJQ-000L7:
│     Device ID:           71b677ca0f1bc2c5b804fa1d59e52064ce589293
│     Summary:             NVM Express Solid State Drive
│     Current version:     5L2QEXA7
│     Vendor:              Samsung Electronics Co Ltd (NVME:0x144D)
│     Serial Number:       S3TNNX0M732756
│     GUIDs:               6e54c992-d302-59ab-b454-2d26ddd63e6d ← NVME\VEN_144D&DEV_A808&REV_00
│                          47335265-a509-51f7-841e-1c94911af66b ← NVME\VEN_144D&DEV_A808
│                          79d6cfae-a5a2-5936-9248-5aebd23480f7 ← SAMSUNG MZVLB512HAJQ-000L7
│     Device Flags:        • Internal device
│                          • Updatable
│                          • Requires AC power
│                          • Supported on remote server
│                          • Needs a reboot after installation
│                          • Device is usable for the duration of the update
│   
├─System Firmware:
│     Device ID:           6e864c667487be72acb296349910341def0b4594
│     Current version:     0.1.81
│     Minimum Version:     0.1.81
│     Vendor:              LENOVO (DMI:LENOVO)
│     GUID:                6bfea39f-87d3-4be0-9afb-39c8632dea45
│     Device Flags:        • Internal device
│                          • Updatable
│                          • Requires AC power
│                          • Supported on remote server
│                          • Needs a reboot after installation
│                          • Cryptographic hash verification is available
│                          • Device is usable for the duration of the update
│   
├─TPM:
│     Device ID:           c6a80ac3a22083423992a3cb15018989f37834d6
│     Current version:     7.63.13.6400
│     Vendor:              Infineon (TPM:IFX)
│     GUIDs:               ff71992e-52f7-5eea-94ef-883e56e034c6 ← system-tpm
│                          5eebb112-75ad-5536-b173-a11eb3399402 ← TPM\VEN_IFX&DEV_0000
│                          ddf995da-1b32-5a8a-bc1b-8d5af4b38b51 ← TPM\VEN_IFX&MOD_SLB9670
│                          6d81ab63-db2e-50ac-934f-6be9accf5e02 ← TPM\VEN_IFX&DEV_0000&VER_2.0
│                          301555de-680d-5ddc-b995-7553fc9138f1 ← TPM\VEN_IFX&MOD_SLB9670&VER_2.0
│     Device Flags:        • Internal device
│   
├─UHD Graphics 630 (Desktop 9 Series):
│     Device ID:           bbbf1ce3d1cf15550c3760b354592040292415bb
│     Current version:     02
│     Vendor:              Intel Corporation (PCI:0x8086)
│     GUIDs:               e9ceb7d8-e213-5ec4-8805-6330d894b317 ← PCI\VEN_8086&DEV_3E98&REV_02
│                          8655a49b-b4b2-54ff-a6c6-06009dd64f13 ← PCI\VEN_8086&DEV_3E98
│     Device Flags:        • Internal device
│                          • Cryptographic hash verification is available
│   
└─Unifying Receiver:
      Device ID:           4588a84d1cfa1ddb273e9df28f6a44927e9b4e99
      Summary:             A miniaturised USB wireless receiver
      Current version:     RQR12.10_B0032
      Bootloader Version:  BOT01.02_B0015
      Vendor:              USB:0x046D
      Install Duration:    30 seconds
      GUIDs:               9d131a0c-a606-580f-8eda-80587250b8d6
                           fcf55bf5-767b-51ce-9c17-f6f538c4ee9f ← HIDRAW\VEN_046D&DEV_C52B&REV_00
                           279ed287-3607-549e-bacc-f873bb9838c4 ← HIDRAW\VEN_046D&DEV_C52B
      Device Flags:        • Updatable
                           • Supported on remote server
    

System UEFI configuration Please provide the output of the following commands:

$ efibootmgr -v
$ sudo efibootmgr -v
BootCurrent: 000B
Timeout: 1 seconds
BootOrder: 000B,0008,0009,000C,000D
Boot0008* UEFI: PXE IPV4 Intel(R) Ethernet Connection (7) I219-LM	PciRoot(0x0)/Pci(0x1f,0x6)/MAC(00d86197098e,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0009* UEFI: PXE IPV6 Intel(R) Ethernet Connection (7) I219-LM	PciRoot(0x0)/Pci(0x1f,0x6)/MAC(00d86197098e,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot000B* debian	HD(1,GPT,f8af0d70-2560-4808-bcb3-843386c46cc7,0x800,0x82000)/File(\EFI\DEBIAN\GRUBX64.EFI)..BO
Boot000C* Generic Usb Device	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot000D* CD/DVD Device	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
$ efivar -l | grep fw
# nothing

Additional questions

  • Operating system and version: Debian Bullseye
  • Have you tried rebooting? Yes
  • Is this a regression? Compared to prior Lenovo update packages, yes. This is probably the 5th or 6th update I have installed on this system. No prior update did this to me.
  • Are you using an NVMe disk? Yes
  • Is secure boot enabled? No

created time in 2 months

push event6RiverSystems/rush-monorepo-boilerplate

Matthew Gabeler-Lee

commit sha 745589665c283c9a3acb472bcd807412f81435b0

fix: make sure convertModelsToSchemas fails on errors, even if it can't log them

view details

push time in 2 months

issue commentmicrosoft/rushstack

[rush] pnpm install error with github dependency

This looks like the same thing I filed on #1749 which @sachinjoseph started working on in #1759

KevinGrandon

comment created time in 3 months

issue closedgrpc/grpc-node

PubSub authentication failure when upgrading from 0.7.6 to 0.7.7

Problem description

A service of ours (running in GKE) using the @google-cloud/pubsub client, version 1.3.0, recently got updated from 0.7.6 to 0.7.7 of @grpc/grpc-js, which is pulled in by google-gax. With that update, and no other changes to the service (including other dependencies!), we went from a properly running service to one that always fails to authenticate with this error:

Error: 16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project. (mfp=null)
    Error: 16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.
        at Object.callErrorFromStatus (/usr/lib/node_modules/@sixriver/mfp-communicator/node_modules/@grpc/grpc-js/build/src/call.js:30:26)
        at Object.onReceiveStatus (/usr/lib/node_modules/@sixriver/mfp-communicator/node_modules/@grpc/grpc-js/build/src/client.js:174:52)
        at Object.onReceiveStatus (/usr/lib/node_modules/@sixriver/mfp-communicator/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:340:141)
        at Object.onReceiveStatus (/usr/lib/node_modules/@sixriver/mfp-communicator/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:303:181)
        at Http2CallStream.outputStatus (/usr/lib/node_modules/@sixriver/mfp-communicator/node_modules/@grpc/grpc-js/build/src/call-stream.js:114:27)
        at Http2CallStream.maybeOutputStatus (/usr/lib/node_modules/@sixriver/mfp-communicator/node_modules/@grpc/grpc-js/build/src/call-stream.js:153:22)
        at Http2CallStream.endCall (/usr/lib/node_modules/@sixriver/mfp-communicator/node_modules/@grpc/grpc-js/build/src/call-stream.js:140:18)
        at Http2CallStream.handleTrailers (/usr/lib/node_modules/@sixriver/mfp-communicator/node_modules/@grpc/grpc-js/build/src/call-stream.js:262:14)
        at ClientHttp2Stream.emit (events.js:198:13)
        at emit (internal/http2/core.js:236:8)

This service authenticates by pulling in service account credentials from disk.

Reproduction steps

  • Install @google-cloud/pubsub in an app
  • Configure the app to authenticate with service credentials
  • Try to publish messages to a topic
  • Works when @grpc/grpc-js is forced to be 0.7.6, fails with above error when it picks up 0.7.7

Working to see if I can generate a more directly testable repro setup.

Environment

  • OS name, version and architecture: Linux
  • Node version: 10.16.2
  • Node installation method: Debian package from nodesource.com
  • If applicable, compiler version: Unknown
  • Package name and version @grpc/grpc-js version 0.7.7 viagoogle-gax via @google-cloud/pubsub

Additional context

FYI @tonygaetani if you can add any additional context or logs you captured would be useful

closed time in 3 months

mgabeler-lee-6rs

issue commentgrpc/grpc-node

PubSub authentication failure when upgrading from 0.7.6 to 0.7.7

I've confirmed that 0.7.9 fixes this issue for us, so closing this ticket, many thanks again :grinning:

mgabeler-lee-6rs

comment created time in 3 months

more