Skip to content

Updated configuration docs and added 1.x -> 2.x migration doc#1403

Merged
stevenengler merged 4 commits intoshadow:devfrom
stevenengler:docs
Jun 4, 2021
Merged

Updated configuration docs and added 1.x -> 2.x migration doc#1403
stevenengler merged 4 commits intoshadow:devfrom
stevenengler:docs

Conversation

@stevenengler
Copy link
Copy Markdown
Contributor

No description provided.

@stevenengler stevenengler added Type: Enhancement New functionality or improved design Component: Documentation In-repository documentation, under docs/ labels Jun 4, 2021
@stevenengler stevenengler self-assigned this Jun 4, 2021
@stevenengler stevenengler requested a review from sporksmith June 4, 2021 20:58
@stevenengler stevenengler enabled auto-merge June 4, 2021 21:02
@codecov
Copy link
Copy Markdown

codecov bot commented Jun 4, 2021

Codecov Report

Merging #1403 (5f0f31c) into dev (28754a9) will increase coverage by 0.00%.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##              dev    #1403   +/-   ##
=======================================
  Coverage   54.11%   54.12%           
=======================================
  Files         138      138           
  Lines       20438    20438           
  Branches     5164     5164           
=======================================
+ Hits        11061    11062    +1     
+ Misses       6463     6462    -1     
  Partials     2914     2914           
Flag Coverage Δ
tests 54.12% <ø> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
src/main/host/thread_ptrace.c 49.50% <0.00%> (+0.16%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1ea9fa0...5f0f31c. Read the comment docs.

When encountering a tag/attribute that is not supported by the new format, these scripts will either:

1. Copy it to the new file anyways. When attempting to use this new file with Shadow, Shadow will raise an error for this unexpected field.
2. Ignore it and output a warning.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What determines which action is taken? Is 2. only for "whitelisted" attributes that we've deemed safe to drop? Or is it controlled by a command-line argument to the conversion script? Or...?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, the ones that are dropped are ones that we should be able to drop (such as the preload attribute since Shadow now finds the shim automatically), or options that don't have anywhere to go in the new format (such as the plugin startsymbol option since we removed the plugin list). Another example is the topology graph prefer_direct_paths attribute which was moved to the shadow config file. If you convert only the topology it removes the attribute and gives a warning, but if you convert a shadow config that includes an inline topology, it automatically moves the attribute to the shadow config instead.

So the actual rules are kind of messy, which is why I added the comment "These scripts are intended to aid in converting to the new formats, and you should manually compare the original file to the new converted file to make sure it includes all of the options you expect". I don't expect these scripts to be used very often so hopefully this isn't a big deal.

@stevenengler stevenengler merged commit 8e4b858 into shadow:dev Jun 4, 2021
@stevenengler stevenengler deleted the docs branch June 4, 2021 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Component: Documentation In-repository documentation, under docs/ Type: Enhancement New functionality or improved design

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants