* update hosted-git-info version
* add npmrc and update yarn lock
* we were hitting an issue with eslint getting updated, I think it's with eslint >= 8.31.0
* attempt to fix cfs and get from our feed without updating versions
* try without hosted-git-info resolution
* revert to base
* updating yarnpkg to our feed
* add comment to npmrc
* Update CONTRIBUTING.md
* Update .npmrc
Co-authored-by: Garrett Campbell <86264750+gcampbell-msft@users.noreply.github.com>
---------
Co-authored-by: Garrett Campbell <gcampbell@microsoft.com>
Co-authored-by: Garrett Campbell <86264750+gcampbell-msft@users.noreply.github.com>
* xml2js cg
* update tests as well
* try update partial
* switch kit?
* ninja is added to path so it should work, still investigating
* update action version with same tool versions
* changes to test
* test output
* more testing
* test macos-13
* remove logging
* remove logging
* try explicit macos-14
* go back to macos-13
* remove static version of vscode
* need to use 13
* comment
* fix binary dir
* fixes the issue, but more testing and possible improvement to come
* set expandedPreset.binaryDir if already set too
* properly update caches, ensure we correctly store cached presets
* remove some unnecessary comments
* fix linter errors
* update envOverride with expandedPreset env
* update the changelog
* update parent environment when never
* In short, with our recent updates, we are attempting to expand every
string in the environment. This isn't a problem in most cases, but it
exposed a bug in certain linux distros that use aliasing (environment
variables).
Therefore, we should be wiser about what we attempt to expand and only
expand the presets environment variables the user has in their files.
To do this, we need to be smarter about what we save in our cache and
update by reference.
* updated the other presets so they dont always have to reexpand configure preset. when they do, use plusIncludes which has the dev env cached if its been expanded before. also include the inherited parent envs
* Fix environment expansion so we don't expand unnecessary variables - don't save the process.env or parent environment to the environment field of the cache.
* Don't re-expand configure presets in the associated build/test/etc presets.
* Fix expansion reporting issues with reporting an invalid config preset, and changing for each loop to a traditional for loop to make sure we dont have async issues with reporting.
* fix validation bug for not being able to find a null config preset
---------
Co-authored-by: Garrett Campbell <gcampbell@microsoft.com>
* fix
* analyze user presets first because it's the base if it exists
* more updates to fix include files and telemetry, still needs work and testing
* ensure telemetry and other uses of 'all..Presets' is right
* more fixes
* ensure we don't duplicate cmakepresets in userpresets includes
* remove unnecessary return
* unionWith consistency
* add test
Fixes#3854. Support for watching multiple paths (cmakepresets.json/cmakeuserpresets.json/include files) was broken due to a Chokidar bug. Created a wrapper class to handle this scenario.
* try to convert release pipeline to yaml
* ensure trigger
* fix variable expansion
* specify name specifically
* add release and fix powershell setup
* fix name
* uncomment vsce task
* only do release pipeline on release branch
* only allow rel branch for release
* enable trigger always, we can rely on manual verification
* Making configure precondition handler return a boolean helps to differentiate the successful recovery cases
* Fix pre-condition handler prototype errors in tests
* Experiment with prototypes to fix linter errors
* Add setting for building whole build dir when clean configure
* Remove anything related to deleteBuildDirOnCleanConfigure since it's in a different PR. Keep proper promise<bool> prototype for pre-configure handler return and fix appropriately compilation and lint errors in tests.
* Forgot one file to remove deleteBuildDirOnCleanConfigure from
* Remove forgotten comment
* Add changelog entry
* remove changes not needed
* removing more bad changes
* add logic to regenerate the driver after selecting cmakelists
* remove unused imports
* keep sanity check in _beforeConfigureOrBuild
* only ensure we set the variable so that on retry, it works
* switch return
* erroneous update
* fix
---------
Co-authored-by: Garrett Campbell <gcampbell@microsoft.com>
Co-authored-by: Garrett Campbell <86264750+gcampbell-msft@users.noreply.github.com>
* Fix GitHub 1401, diagnostics relative to workspace folder
- relative diagnostics files are searched in build_dir and src_dir,
first existing file is returned
- defaults to old behavior : `path.resolve(build_dir, file)`
- `resolveDiagnostics` has been made async to not slow down IDE when
testing files
* update ChangeLog for #1401
* fix relative file resolution diagnostics test
- diagnostics paths always use POSIX separators (see `normalizePath` in
[src/util.ts](src/util.ts))
---------
Co-authored-by: Sylvain Fargier <sylvain.fargier@cern.ch>
Co-authored-by: Garrett Campbell <86264750+gcampbell-msft@users.noreply.github.com>
dependabot[bot]
Paul
Garrett Campbell
Fatima Qarni
CSIGS@microsoft.com
Garrett Campbell
Sinem Akinci
Sean McManus
moyo1997
Andreea Isac
fargies