Skip to content
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

Change relative path to ydbmerrors to use src directory #161

Merged

Conversation

ChristopherEdwards
Copy link
Collaborator

@ChristopherEdwards ChristopherEdwards commented Feb 19, 2018

Final Release Note

The YDB_SOURCE_DIR cmake variable is used to get the path to ydbmerrors.h
instead of a hardcoded relative path. (#161)

Use the YDB_SOURCE_DIR cmake variable to get the path to ydbmerrors.h
instead of a hardcoded relative path
@ChristopherEdwards
Copy link
Collaborator Author

@nars1

@nars1 nars1 self-requested a review February 19, 2018 15:39
@nars1 nars1 added this to To Do in r1.20 via automation Feb 19, 2018
@nars1 nars1 added this to the r120 milestone Feb 19, 2018
@nars1 nars1 merged commit 3246ed8 into YottaDB:master Feb 19, 2018
r1.20 automation moved this from To Do to Done Feb 19, 2018
@ChristopherEdwards ChristopherEdwards deleted the fix-relative-path-ydbmerrors branch February 19, 2018 15:48
@shabiel
Copy link
Contributor

shabiel commented Feb 20, 2018 via email

nars1 pushed a commit to YottaDB/YDBDoc that referenced this pull request Jun 9, 2021
Continuous deployments work correctly as long as the pipeline passes.
Unfortunately, the pipeline is not currently passing, and fixing it is
not trivial. Here are the current errors, taken from
https://gitlab.com/jyn514/YDBDoc/-/jobs/791375698 and
https://gitlab.com/jyn514/YDBDoc/-/jobs/793823039:

```
Found invalid urls in /builds/jyn514/YDBDoc/target/AcculturationGuide/acculturation.html:
	Error fetching http://worldvista.org/AboutVistA: http://worldvista.org/AboutVistA: timed out
	Unexpected HTTP status fetching YottaDB/YDB#109: 429 Too Many Requests
	Unexpected HTTP status fetching YottaDB/YDB#161: 429 Too Many Requests
	Unexpected HTTP status fetching YottaDB/YDB#186: 429 Too Many Requests
	Unexpected HTTP status fetching YottaDB/YDB#188: 429 Too Many Requests
	Unexpected HTTP status fetching YottaDB/YDB#145: 429 Too Many Requests
```

Note that all these URLs exist, the only problem is that the pipeline is
rate-limited or the request times out. There are a few possible solutions:

- Don't check HTTP pages at all. This will catch fewer failures, but not have any spurious failures at all.
- Retry pages that fail. This will require upstream support in cargo-deadlinks
  (deadlinks/cargo-deadlinks#53). It will not
  help with rate-limits (since the retries will also count against the limit).

- Ignore failures in some websites. This requires upstream support
  (deadlinks/cargo-deadlinks#57). It will help with both issues.

- Add a GitHub token in the environment to increase the rate limit. This
  will not fix the issues with timeouts, but should fix the vast majority
  of other errors. Unfortunately, it also requires storing secrets in
  pipelines and having a dedicated GitHub account for this. GitLab has
  support for storing secret credentials, so this is feasible.

- Change some of the URLs to point to GitLab. This will help with the
  GitHub rate limits but not with the VistA timeout.

- Remove some URLs from the documentation. This is not a _good_ solution, but it is _a_ solution.

The change implemented here is to not check HTTP pages at all. If in the
future deadlinks has more support for retries, the check could be
re-enabled.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
r1.20
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

3 participants