@@ -130,6 +130,9 @@ owl-bot copy-code --version
130
130
The key step is ` npm link ` , which will make the command available in you current
131
131
shell session.
132
132
133
+ If you get a permission denied error when running the command ` owl-bot ` , try
134
+ relinking owl-bot by running ` npm unlink -g ` and re-running the steps above.
135
+
133
136
## Run the script
134
137
The entrypoint script (` hermetic_build/library_generation/cli/entry_point.py ` )
135
138
allows you to generate a GAPIC repository with a given api definition (proto,
@@ -153,12 +156,14 @@ export path_to_repo="$(pwd)/google-cloud-java"
153
156
### Install the scripts
154
157
155
158
You can skip this step if you've installed the packages in [ Install package dependencies] ( #install-package-dependencies ) .
159
+ Use the ` --editable ` flag for your changes to take effect as soon as you modify any file inside
160
+ the package.
156
161
157
162
``` shell
158
163
python -m pip install --require-hashes -r hermetic_build/common/requirements.txt
159
- python -m pip install hermetic_build/common
164
+ python -m pip install --editable hermetic_build/common
160
165
python -m pip install --require-hashes -r hermetic_build/library_generation/requirements.txt
161
- python -m pip install hermetic_build/library_generation
166
+ python -m pip install --editable hermetic_build/library_generation
162
167
```
163
168
164
169
### Run the script
@@ -212,10 +217,19 @@ python hermetic_build/library_generation/cli/entry_point.py generate \
212
217
--api-definitions-path=/workspace/apis
213
218
```
214
219
215
- # Debug the library generation container
220
+ # Debugging tips
221
+ ## Debug the scripts
222
+ Especially on local setups, consider adding the ` xtrace ` (` set -x ` ) flag to
223
+ - ` hermetic_build/library_generation/generate_library.sh `
224
+ - ` hermetic_build/library_generation/utils/utilities.sh `
225
+
226
+ This will allow you to observe how the tools you prepared in ` ~/.library_generation ` are being used.
227
+
228
+
229
+ ## Debug the library generation container
216
230
If you are working on changing the way the containers are created, you may want
217
231
to inspect the containers to check the setup.
218
- It would be convenient in such case to have a text editor/viewer available.
232
+ It would be convenient in such case to have a text editor/viewer available.
219
233
You can achieve this by modifying the Dockerfile as follows:
220
234
221
235
``` dockerfile
0 commit comments