Describe the bug
Apparently since the update of Zowe Explorer to version 1.10.0, or since the VS Code version upgrade to 1.50.x, a warning window is displayed when VS Code is launched concerning access to a function.
To Reproduce
Steps to reproduce the behavior:
Screenshots
Desktop (please complete the following information):
Additional context
N/A
Solved by erasing all preferences about Zowe Explorer in settings.json.....
Having also problems on profiles...
Does the order in which the settings are declared in the settings.json file matter?
The parameters had been manually re-sorted for educational purposes. In particular, the "persistence" parameter was not at the start of the listing of the properties of "Zowe-xx-Persistent" objects.
Before:
"Zowe-DS-Persistent": {
"favorites": [
"[TMVS]: J070188.PUBLIC.COBOL.SRCELIB{pds}"
],
"fileHistory": [
"[TMVS]: J070188.PUBLIC.COBOL.JCL($CB6CO)",
"[TMVS]: J070188.PUBLIC.COBOL.JCL($$TEST)",
"[TMVS]: J070188.PUBLIC.COBOL.SRCELIB(AJ5074K)",
"[TMVS]: J070188.PUBLIC.COBOL.SRCELIB(COB0C7)",
"[TMVS]: J070188.PUBLIC.COBOL.SRCELIB(UTICV8)",
"[TMVS]: J070188.PUBLIC.COBOL.PARMLIB(CB6PROD)",
"[TMVS]: J070188.PUBLIC.COBOL.PARMLIB(CB6TEST)",
"[TMVS]: J070188.PUBLIC.COBOL.PARMLIB(CB6BAT)",
"[TMVS]: J070188.PUBLIC.COBOL.JCL($CB4)",
"[TMVS]: J070188.PUBLIC.COBOL.SRCELIB(TEST1147)"
],
"history": [],
"persistence": true,
"recall": [],
"searchHistory": [
"J070188.PUBLIC.COBOL.**",
"J070188.USER.**"
],
"sessions": [
"TMVS",
"TMVSML"
]
},
"Zowe-Jobs-Persistent": {
"favorites": [],
"history": [],
"searchHistory": [
"Owner:J070188 Prefix:J070188*",
"Owner:J005365 Prefix:J005365*"
],
"sessions": [
"TMVS"
],
"persistence": true
},
"Zowe-Temp-Folder-Location": {
"folderPath": "D:\\DVLT\\DepotsGIT\\Temp"
},
"Zowe-USS-Persistent": {
"favorites": [],
"fileHistory": [],
"history": [],
"persistence": true,
"searchHistory": [
"/u/J070188"
],
"sessions": [
"TMVS"
]
}
After:
"Zowe-DS-Persistent": {
"persistence": true,
"favorites": [],
"history": [],
"sessions": [
"TMVS"
],
"fileHistory": [
"[TMVS]: J070188.PUBLIC.COBOL.SRCELIB($COMPARE)"
],
"recall": [],
"searchHistory": [
"J070188.PUBLIC.COBOL.**"
]
},
"Zowe-Jobs-Persistent": {
"persistence": true,
"favorites": [],
"history": [],
"sessions": [
"TMVS"
],
"searchHistory": []
},
"Zowe-Temp-Folder-Location": {
"folderPath": "D:\\DVLT\\DepotsGIT\\Temp"
},
"Zowe-USS-Persistent": {
"persistence": true,
"favorites": [],
"history": [],
"sessions": [
"TMVS"
],
"fileHistory": [],
"searchHistory": []
}
Adding to #1000 .
The error is repeated every time you start VS Code and blocks the use of Zowe Explorer.
Solution:
Zowe Explorer extension redetects default profiles and declares them automatically in settings.json.
Zowe Explorer works ... until the next restart of VS Code.
The problem is caused by the existence of a base profile declared by default.
Removing the default base profile permanently eliminates the problem.
How can I find where this settings.json file is?
@mpettis You can access settings.json here:

Or, go to File >> Preferences >> Settings, then locate Zowe Explorer Settings in the list on the left, and click Edit in settings.json under one of the categories on the right:

@zdmullen I think this was fixed in PR #993, I will look into it...
@katelynienaber, any update on this?
@zdmullen This is resolved. The initialization was hanging during getCliProfileManager but we added an if() so now if you are missing a certain type of profile you can still start the extension.
I tested if it works when the base folder is completely missing, and when the folder is present but doesn't contain any default.yaml file.
This could also fix issue #1067...but their post is so vague, they could be referring to any kind of error during init.
Thank you for investigating this @katelynienaber.
@FALLAI-Denis Can we close this issue?
Issue seems to be resolved