“ logger is not defined” on sfdx force:user:display output? [BUG]
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty{ margin-bottom:0;
}
up vote
2
down vote
favorite
I'm getting
ERROR: logger is not defined.
error after issuing sfdx force:user:display command.
What I'm trying to input is:
sfdx force:user:display
sfdx force:user:display -u username
It seems to work with --json parameter though.
What am I doing wrong? These commands are the same as examples in
https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_force_user.htm#cli_reference_display
I'm running sfdx-cli/6.40.0-384e0c6cf2 version.
salesforcedx salesforcedx-cli
add a comment |
up vote
2
down vote
favorite
I'm getting
ERROR: logger is not defined.
error after issuing sfdx force:user:display command.
What I'm trying to input is:
sfdx force:user:display
sfdx force:user:display -u username
It seems to work with --json parameter though.
What am I doing wrong? These commands are the same as examples in
https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_force_user.htm#cli_reference_display
I'm running sfdx-cli/6.40.0-384e0c6cf2 version.
salesforcedx salesforcedx-cli
getting this as well on force:user:display
– Eric
2 days ago
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I'm getting
ERROR: logger is not defined.
error after issuing sfdx force:user:display command.
What I'm trying to input is:
sfdx force:user:display
sfdx force:user:display -u username
It seems to work with --json parameter though.
What am I doing wrong? These commands are the same as examples in
https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_force_user.htm#cli_reference_display
I'm running sfdx-cli/6.40.0-384e0c6cf2 version.
salesforcedx salesforcedx-cli
I'm getting
ERROR: logger is not defined.
error after issuing sfdx force:user:display command.
What I'm trying to input is:
sfdx force:user:display
sfdx force:user:display -u username
It seems to work with --json parameter though.
What am I doing wrong? These commands are the same as examples in
https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_force_user.htm#cli_reference_display
I'm running sfdx-cli/6.40.0-384e0c6cf2 version.
salesforcedx salesforcedx-cli
salesforcedx salesforcedx-cli
edited 2 days ago
Eric
44.6k649113
44.6k649113
asked Nov 18 at 20:20
pkozuchowski
885
885
getting this as well on force:user:display
– Eric
2 days ago
add a comment |
getting this as well on force:user:display
– Eric
2 days ago
getting this as well on force:user:display
– Eric
2 days ago
getting this as well on force:user:display
– Eric
2 days ago
add a comment |
4 Answers
4
active
oldest
votes
up vote
4
down vote
This sounds like a bug in the CLI that you should report it via initiating the case .
You can see a better log in the logger file that will be stored in the $HOME/.sfdx/sfdx.log file .
The error that got generated is as below
{
"name": "sfdx",
"hostname": "Mohiths-MacBook-Air.local",
"pid": 16768,
"level": 50,
"msg": "[ false,n '{"message":"logger is not defined","status":1,"stack":"ReferenceError: logger is not defined\\n at UserDisplayCommand.getHumanSuccessMessage (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/lib/user/userDisplayCommand.js:86:9)\\n at _logSuccess (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/index.js:157:71)\\n at _notifyUsageDataCollection.then.then.then.then.then.then.then (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/index.js:455:9)\\n at tryCatcher (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/util.js:16:23)\\n at Promise._settlePromiseFromHandler (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:510:31)\\n at Promise._settlePromise (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:567:18)\\n at Promise._settlePromise0 (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:612:10)\\n at Promise._settlePromises (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:691:18)\\n at Async._drainQueue (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:138:16)\\n at Async._drainQueues (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:148:10)\\n at Immediate.Async.drainQueues (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:17:14)\\n at runCallback (timers.js:789:20)\\n at tryOnImmediate (timers.js:751:5)\\n at processImmediate [as _immediateCallback] (timers.js:722:5)","name":"ReferenceError","warnings":}' ]",
"time": "2018-11-18T20:56:36.478Z",
"v": 0
}
I'd just like to add I'm getting this error also however cannot find an sfdx.log. Also works for me when using --json
– Luke Bray
2 days ago
1
Maybe someone with premier support can log a case? This appears to be DX wide but they will just close it and point me to the forums if I submit it....
– Eric
2 days ago
1
I've pinged Wade Wenger on Twitter. Will raise a case later if he doesn't respond. FWIW "Apex" isn't even a topic option when reporting a bug with premier these days :(
– Matt Lacey♦
2 days ago
1
Response from Wade: "Team will look into this tomorrow. Thanks for sharing." Fingers crossed!
– Matt Lacey♦
yesterday
add a comment |
up vote
4
down vote
Thanks for reporting, I've filed a bug & we'll take a look.
-Kate (CLI Team)
New contributor
Thank you. Any advice on best route to submit outside of Salesforce support where they will just close the case. I would love to be able to report bugs and have them fixed
– Eric
yesterday
1
This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review
– Reshma
yesterday
1
A note for others seeing this in one of the review queues. Yes, it's technically not a stand-alone answer...but perhaps we can cut this employee of Salesforce a bit of slack.
– Derek F
yesterday
add a comment |
up vote
0
down vote
We have filed it as a bug and today we received response that it was fixed in 6.41. However, we still encounter same error.
add a comment |
up vote
-1
down vote
same here, we are also still experiencing this issue. here is the output i m seeing at my end.
Successfully created user "XXXXXXXXXXXXX" with ID [000000000000000] for org 000000000000000.
[15:55:56] You can see more details about this user by running "sfdx force:user:display -u user@asdfasdfasdfasdf.scratch".
[15:56:00] ERROR: INVALID_HEADER_TYPE.
[15:56:02] Process exited with code 137
New contributor
add a comment |
protected by David Reed 4 hours ago
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
This sounds like a bug in the CLI that you should report it via initiating the case .
You can see a better log in the logger file that will be stored in the $HOME/.sfdx/sfdx.log file .
The error that got generated is as below
{
"name": "sfdx",
"hostname": "Mohiths-MacBook-Air.local",
"pid": 16768,
"level": 50,
"msg": "[ false,n '{"message":"logger is not defined","status":1,"stack":"ReferenceError: logger is not defined\\n at UserDisplayCommand.getHumanSuccessMessage (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/lib/user/userDisplayCommand.js:86:9)\\n at _logSuccess (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/index.js:157:71)\\n at _notifyUsageDataCollection.then.then.then.then.then.then.then (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/index.js:455:9)\\n at tryCatcher (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/util.js:16:23)\\n at Promise._settlePromiseFromHandler (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:510:31)\\n at Promise._settlePromise (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:567:18)\\n at Promise._settlePromise0 (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:612:10)\\n at Promise._settlePromises (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:691:18)\\n at Async._drainQueue (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:138:16)\\n at Async._drainQueues (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:148:10)\\n at Immediate.Async.drainQueues (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:17:14)\\n at runCallback (timers.js:789:20)\\n at tryOnImmediate (timers.js:751:5)\\n at processImmediate [as _immediateCallback] (timers.js:722:5)","name":"ReferenceError","warnings":}' ]",
"time": "2018-11-18T20:56:36.478Z",
"v": 0
}
I'd just like to add I'm getting this error also however cannot find an sfdx.log. Also works for me when using --json
– Luke Bray
2 days ago
1
Maybe someone with premier support can log a case? This appears to be DX wide but they will just close it and point me to the forums if I submit it....
– Eric
2 days ago
1
I've pinged Wade Wenger on Twitter. Will raise a case later if he doesn't respond. FWIW "Apex" isn't even a topic option when reporting a bug with premier these days :(
– Matt Lacey♦
2 days ago
1
Response from Wade: "Team will look into this tomorrow. Thanks for sharing." Fingers crossed!
– Matt Lacey♦
yesterday
add a comment |
up vote
4
down vote
This sounds like a bug in the CLI that you should report it via initiating the case .
You can see a better log in the logger file that will be stored in the $HOME/.sfdx/sfdx.log file .
The error that got generated is as below
{
"name": "sfdx",
"hostname": "Mohiths-MacBook-Air.local",
"pid": 16768,
"level": 50,
"msg": "[ false,n '{"message":"logger is not defined","status":1,"stack":"ReferenceError: logger is not defined\\n at UserDisplayCommand.getHumanSuccessMessage (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/lib/user/userDisplayCommand.js:86:9)\\n at _logSuccess (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/index.js:157:71)\\n at _notifyUsageDataCollection.then.then.then.then.then.then.then (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/index.js:455:9)\\n at tryCatcher (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/util.js:16:23)\\n at Promise._settlePromiseFromHandler (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:510:31)\\n at Promise._settlePromise (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:567:18)\\n at Promise._settlePromise0 (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:612:10)\\n at Promise._settlePromises (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:691:18)\\n at Async._drainQueue (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:138:16)\\n at Async._drainQueues (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:148:10)\\n at Immediate.Async.drainQueues (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:17:14)\\n at runCallback (timers.js:789:20)\\n at tryOnImmediate (timers.js:751:5)\\n at processImmediate [as _immediateCallback] (timers.js:722:5)","name":"ReferenceError","warnings":}' ]",
"time": "2018-11-18T20:56:36.478Z",
"v": 0
}
I'd just like to add I'm getting this error also however cannot find an sfdx.log. Also works for me when using --json
– Luke Bray
2 days ago
1
Maybe someone with premier support can log a case? This appears to be DX wide but they will just close it and point me to the forums if I submit it....
– Eric
2 days ago
1
I've pinged Wade Wenger on Twitter. Will raise a case later if he doesn't respond. FWIW "Apex" isn't even a topic option when reporting a bug with premier these days :(
– Matt Lacey♦
2 days ago
1
Response from Wade: "Team will look into this tomorrow. Thanks for sharing." Fingers crossed!
– Matt Lacey♦
yesterday
add a comment |
up vote
4
down vote
up vote
4
down vote
This sounds like a bug in the CLI that you should report it via initiating the case .
You can see a better log in the logger file that will be stored in the $HOME/.sfdx/sfdx.log file .
The error that got generated is as below
{
"name": "sfdx",
"hostname": "Mohiths-MacBook-Air.local",
"pid": 16768,
"level": 50,
"msg": "[ false,n '{"message":"logger is not defined","status":1,"stack":"ReferenceError: logger is not defined\\n at UserDisplayCommand.getHumanSuccessMessage (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/lib/user/userDisplayCommand.js:86:9)\\n at _logSuccess (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/index.js:157:71)\\n at _notifyUsageDataCollection.then.then.then.then.then.then.then (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/index.js:455:9)\\n at tryCatcher (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/util.js:16:23)\\n at Promise._settlePromiseFromHandler (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:510:31)\\n at Promise._settlePromise (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:567:18)\\n at Promise._settlePromise0 (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:612:10)\\n at Promise._settlePromises (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:691:18)\\n at Async._drainQueue (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:138:16)\\n at Async._drainQueues (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:148:10)\\n at Immediate.Async.drainQueues (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:17:14)\\n at runCallback (timers.js:789:20)\\n at tryOnImmediate (timers.js:751:5)\\n at processImmediate [as _immediateCallback] (timers.js:722:5)","name":"ReferenceError","warnings":}' ]",
"time": "2018-11-18T20:56:36.478Z",
"v": 0
}
This sounds like a bug in the CLI that you should report it via initiating the case .
You can see a better log in the logger file that will be stored in the $HOME/.sfdx/sfdx.log file .
The error that got generated is as below
{
"name": "sfdx",
"hostname": "Mohiths-MacBook-Air.local",
"pid": 16768,
"level": 50,
"msg": "[ false,n '{"message":"logger is not defined","status":1,"stack":"ReferenceError: logger is not defined\\n at UserDisplayCommand.getHumanSuccessMessage (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/lib/user/userDisplayCommand.js:86:9)\\n at _logSuccess (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/index.js:157:71)\\n at _notifyUsageDataCollection.then.then.then.then.then.then.then (/Users/mohith/.local/share/sfdx/client/node_modules/salesforce-alm/dist/index.js:455:9)\\n at tryCatcher (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/util.js:16:23)\\n at Promise._settlePromiseFromHandler (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:510:31)\\n at Promise._settlePromise (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:567:18)\\n at Promise._settlePromise0 (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:612:10)\\n at Promise._settlePromises (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/promise.js:691:18)\\n at Async._drainQueue (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:138:16)\\n at Async._drainQueues (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:148:10)\\n at Immediate.Async.drainQueues (/Users/mohith/.local/share/sfdx/client/node_modules/bluebird/js/release/async.js:17:14)\\n at runCallback (timers.js:789:20)\\n at tryOnImmediate (timers.js:751:5)\\n at processImmediate [as _immediateCallback] (timers.js:722:5)","name":"ReferenceError","warnings":}' ]",
"time": "2018-11-18T20:56:36.478Z",
"v": 0
}
answered Nov 18 at 21:00
Mohith Shrivastava
58.8k794133
58.8k794133
I'd just like to add I'm getting this error also however cannot find an sfdx.log. Also works for me when using --json
– Luke Bray
2 days ago
1
Maybe someone with premier support can log a case? This appears to be DX wide but they will just close it and point me to the forums if I submit it....
– Eric
2 days ago
1
I've pinged Wade Wenger on Twitter. Will raise a case later if he doesn't respond. FWIW "Apex" isn't even a topic option when reporting a bug with premier these days :(
– Matt Lacey♦
2 days ago
1
Response from Wade: "Team will look into this tomorrow. Thanks for sharing." Fingers crossed!
– Matt Lacey♦
yesterday
add a comment |
I'd just like to add I'm getting this error also however cannot find an sfdx.log. Also works for me when using --json
– Luke Bray
2 days ago
1
Maybe someone with premier support can log a case? This appears to be DX wide but they will just close it and point me to the forums if I submit it....
– Eric
2 days ago
1
I've pinged Wade Wenger on Twitter. Will raise a case later if he doesn't respond. FWIW "Apex" isn't even a topic option when reporting a bug with premier these days :(
– Matt Lacey♦
2 days ago
1
Response from Wade: "Team will look into this tomorrow. Thanks for sharing." Fingers crossed!
– Matt Lacey♦
yesterday
I'd just like to add I'm getting this error also however cannot find an sfdx.log. Also works for me when using --json
– Luke Bray
2 days ago
I'd just like to add I'm getting this error also however cannot find an sfdx.log. Also works for me when using --json
– Luke Bray
2 days ago
1
1
Maybe someone with premier support can log a case? This appears to be DX wide but they will just close it and point me to the forums if I submit it....
– Eric
2 days ago
Maybe someone with premier support can log a case? This appears to be DX wide but they will just close it and point me to the forums if I submit it....
– Eric
2 days ago
1
1
I've pinged Wade Wenger on Twitter. Will raise a case later if he doesn't respond. FWIW "Apex" isn't even a topic option when reporting a bug with premier these days :(
– Matt Lacey♦
2 days ago
I've pinged Wade Wenger on Twitter. Will raise a case later if he doesn't respond. FWIW "Apex" isn't even a topic option when reporting a bug with premier these days :(
– Matt Lacey♦
2 days ago
1
1
Response from Wade: "Team will look into this tomorrow. Thanks for sharing." Fingers crossed!
– Matt Lacey♦
yesterday
Response from Wade: "Team will look into this tomorrow. Thanks for sharing." Fingers crossed!
– Matt Lacey♦
yesterday
add a comment |
up vote
4
down vote
Thanks for reporting, I've filed a bug & we'll take a look.
-Kate (CLI Team)
New contributor
Thank you. Any advice on best route to submit outside of Salesforce support where they will just close the case. I would love to be able to report bugs and have them fixed
– Eric
yesterday
1
This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review
– Reshma
yesterday
1
A note for others seeing this in one of the review queues. Yes, it's technically not a stand-alone answer...but perhaps we can cut this employee of Salesforce a bit of slack.
– Derek F
yesterday
add a comment |
up vote
4
down vote
Thanks for reporting, I've filed a bug & we'll take a look.
-Kate (CLI Team)
New contributor
Thank you. Any advice on best route to submit outside of Salesforce support where they will just close the case. I would love to be able to report bugs and have them fixed
– Eric
yesterday
1
This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review
– Reshma
yesterday
1
A note for others seeing this in one of the review queues. Yes, it's technically not a stand-alone answer...but perhaps we can cut this employee of Salesforce a bit of slack.
– Derek F
yesterday
add a comment |
up vote
4
down vote
up vote
4
down vote
Thanks for reporting, I've filed a bug & we'll take a look.
-Kate (CLI Team)
New contributor
Thanks for reporting, I've filed a bug & we'll take a look.
-Kate (CLI Team)
New contributor
New contributor
answered yesterday
kbierbaum
411
411
New contributor
New contributor
Thank you. Any advice on best route to submit outside of Salesforce support where they will just close the case. I would love to be able to report bugs and have them fixed
– Eric
yesterday
1
This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review
– Reshma
yesterday
1
A note for others seeing this in one of the review queues. Yes, it's technically not a stand-alone answer...but perhaps we can cut this employee of Salesforce a bit of slack.
– Derek F
yesterday
add a comment |
Thank you. Any advice on best route to submit outside of Salesforce support where they will just close the case. I would love to be able to report bugs and have them fixed
– Eric
yesterday
1
This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review
– Reshma
yesterday
1
A note for others seeing this in one of the review queues. Yes, it's technically not a stand-alone answer...but perhaps we can cut this employee of Salesforce a bit of slack.
– Derek F
yesterday
Thank you. Any advice on best route to submit outside of Salesforce support where they will just close the case. I would love to be able to report bugs and have them fixed
– Eric
yesterday
Thank you. Any advice on best route to submit outside of Salesforce support where they will just close the case. I would love to be able to report bugs and have them fixed
– Eric
yesterday
1
1
This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review
– Reshma
yesterday
This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review
– Reshma
yesterday
1
1
A note for others seeing this in one of the review queues. Yes, it's technically not a stand-alone answer...but perhaps we can cut this employee of Salesforce a bit of slack.
– Derek F
yesterday
A note for others seeing this in one of the review queues. Yes, it's technically not a stand-alone answer...but perhaps we can cut this employee of Salesforce a bit of slack.
– Derek F
yesterday
add a comment |
up vote
0
down vote
We have filed it as a bug and today we received response that it was fixed in 6.41. However, we still encounter same error.
add a comment |
up vote
0
down vote
We have filed it as a bug and today we received response that it was fixed in 6.41. However, we still encounter same error.
add a comment |
up vote
0
down vote
up vote
0
down vote
We have filed it as a bug and today we received response that it was fixed in 6.41. However, we still encounter same error.
We have filed it as a bug and today we received response that it was fixed in 6.41. However, we still encounter same error.
edited 8 hours ago
answered 9 hours ago
kvor
263
263
add a comment |
add a comment |
up vote
-1
down vote
same here, we are also still experiencing this issue. here is the output i m seeing at my end.
Successfully created user "XXXXXXXXXXXXX" with ID [000000000000000] for org 000000000000000.
[15:55:56] You can see more details about this user by running "sfdx force:user:display -u user@asdfasdfasdfasdf.scratch".
[15:56:00] ERROR: INVALID_HEADER_TYPE.
[15:56:02] Process exited with code 137
New contributor
add a comment |
up vote
-1
down vote
same here, we are also still experiencing this issue. here is the output i m seeing at my end.
Successfully created user "XXXXXXXXXXXXX" with ID [000000000000000] for org 000000000000000.
[15:55:56] You can see more details about this user by running "sfdx force:user:display -u user@asdfasdfasdfasdf.scratch".
[15:56:00] ERROR: INVALID_HEADER_TYPE.
[15:56:02] Process exited with code 137
New contributor
add a comment |
up vote
-1
down vote
up vote
-1
down vote
same here, we are also still experiencing this issue. here is the output i m seeing at my end.
Successfully created user "XXXXXXXXXXXXX" with ID [000000000000000] for org 000000000000000.
[15:55:56] You can see more details about this user by running "sfdx force:user:display -u user@asdfasdfasdfasdf.scratch".
[15:56:00] ERROR: INVALID_HEADER_TYPE.
[15:56:02] Process exited with code 137
New contributor
same here, we are also still experiencing this issue. here is the output i m seeing at my end.
Successfully created user "XXXXXXXXXXXXX" with ID [000000000000000] for org 000000000000000.
[15:55:56] You can see more details about this user by running "sfdx force:user:display -u user@asdfasdfasdfasdf.scratch".
[15:56:00] ERROR: INVALID_HEADER_TYPE.
[15:56:02] Process exited with code 137
New contributor
edited 4 hours ago
New contributor
answered 5 hours ago
Pankaj
11
11
New contributor
New contributor
add a comment |
add a comment |
protected by David Reed 4 hours ago
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
getting this as well on force:user:display
– Eric
2 days ago