gitlab | Gitlab nodejs API Client | REST library

I had a similar problem with another module.

The solution I found was to update both node (to v16) and npm (to v8).

For Node, I used brew (but nvm should be OK).

For npm, I used what the official doc says :

npm install -g npm@latest

Seems to be a bug in ipykernel 6.9.0 - options that worked for me:

• upgrade to 6.9.1 (latest version as of 2022-02-22); e.g. via pip install ipykernel --upgrade
• downgrade to 6.8.0 (if upgrading messes with other dependencies you might have); e.g. via pip install ipykernel==6.8.0

You missed adding this in your eslint.json file.

After countless hours working on this, it seems that ultimately the issue was that our internal Web Application Firewall was blocking some part of the transfer of artefacts to the server, or the response back from it. With the WAF reconfigured not to block traffic from the machine running the GitLab Runner, the artefacts are successfully uploaded and the job succeeds.

This would have been significantly easier to diagnose if the logging from GitLab was better. As per my comment on this issue, it should be possible to see the content of the response from the GitLab server after uploading artefacts, even when the response code is 200.

What's strange - and made diagnosing the issue even harder - is that when I worked through the issue with the admin of our GitLab instance, digging through logs and running it in debug mode, the artefact upload process was uploading something successfully. We could see, for example, the GitLab Runner's log had been uploaded to the server. Clearly the WAF's blocking was selective and didn't block everything in both directions.

Use pure from Control.Functor.Linear instead, as well as the IO from System.IO.Linear, because contents of Prelude are simply not declared as linear.

Note that this even simpler example does not compile too:

As far as i experienced, the only way to disable this message is to set the config globally in the .gitconfig of the user running the gitlab-runner.

This can either be done on the underlying VM if you use the shell-runner or inside the used docker-image when using the docker-runner

Update

Altough it says global, the git-setting is user based. You'll have to set it as the same user that executes the gitlab-runner. Depending on the configuration, this might be gitlab-runner or a custom user on shell-runners or root when using the docker-executor.

TL;DR You are missing some resolvers. Your query resolvers are trying to do the job of the missing resolvers. Your resolvers must return data in the right shape.

In other words, your problems are with configuring Apollo Server's resolvers. Nothing Lambda-specific, as far as I can tell.

GraphQL doesn't know how to "resolve" an author's books, for instance. Add a Author {books(parent)} entry to Apollo Server's resolver map. The corresponding resolver function should return a list of book objects (i.e. [Books]), as your schema requires. Apollo's docs have a similar example you can adapt.

Here's a refactored author query, commented with the resolvers that will be called:

I faced the same problem today. Apparently there is some problem in the latest version of FARADAY, at the moment. I solved it this way: add manual installation of the previous version of the dependency to your .gitlab.yml, and everything will work. Have a nice day.

I took a look at the sample project you created.

When looking at the diff for the open MR, I am able to see the coverage visualization. Here is a screenshot of the coverage visualization in sample project MR.

If you're still having issues, it would be great if you could open a bug report and share more details about your browser settings, etc so we can identify the cause of your issue.