-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minor updates to prepare for internal mirror #1
Merged
heyealex
merged 1 commit into
GoogleCloudPlatform:develop
from
heyealex:prep-for-mirror
Oct 13, 2021
Merged
Minor updates to prepare for internal mirror #1
heyealex
merged 1 commit into
GoogleCloudPlatform:develop
from
heyealex:prep-for-mirror
Oct 13, 2021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Moved templates from their own directory to within reswriter as is required by internal embed tooling and removed a test that is not properly self-contained.
cboneti
approved these changes
Oct 13, 2021
6 tasks
heyealex
pushed a commit
that referenced
this pull request
Apr 27, 2022
Rebase from upstream/develop
tpdownes
pushed a commit
that referenced
this pull request
May 6, 2022
- hpc-cluster-intel: Create an Intel cluster with 10 c2-standard-60 nodes using a custom OS image that has Intel oneAPI packages. - custom-image-intel-oneapi: Custom OS image blueprint for Intel oneAPI packages. - slurm-clck-job: Slurm job file requests 4 nodes for 1 hour and executes clck benchmark dgemm.
6 tasks
mr0re1
added a commit
that referenced
this pull request
Oct 26, 2023
* Augment expression parsing error with position; * Remove `YAML parsing error: ` prefix. ```yaml vars: project_id: $(6 + 4) # Case #1 hello: ((world+)) # Case #2 ``` ```sh YAML parsing error: only traversal expressions are supported, got "6 + 4" YAML parsing error: :0,6-6: Missing expression; Expected the start of an expression, but found the end of the file. Case #1 Error: only traversal expressions are supported, got "6 + 4" 2: project_id: $(6 + 4) Case #2 Error: :0,6-6: Missing expression; Expected the start of an expression, but found the end of the file. 2: hello: ((world+)) ```
max-nag
referenced
this pull request
in max-nag/hpc-toolkit
Oct 27, 2023
) * Augment expression parsing error with position; * Remove `YAML parsing error: ` prefix. ```yaml vars: project_id: $(6 + 4) # Case #1 hello: ((world+)) # Case GoogleCloudPlatform#2 ``` ```sh YAML parsing error: only traversal expressions are supported, got "6 + 4" YAML parsing error: :0,6-6: Missing expression; Expected the start of an expression, but found the end of the file. Case #1 Error: only traversal expressions are supported, got "6 + 4" 2: project_id: $(6 + 4) Case GoogleCloudPlatform#2 Error: :0,6-6: Missing expression; Expected the start of an expression, but found the end of the file. 2: hello: ((world+)) ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Moved templates from their own directory to within reswriter as is
required by internal embed tooling and removed a test that is not
properly self-contained.