Error occuring during the running of cml file #57478

Alimiji · 2023-06-07T20:56:49Z

Alimiji
Jun 7, 2023

Hi everyone,

Hi everyone,
I need your help please. This is the error that occurs:

{"code":"ERR_INVALID_URL","input":"\r\n<title>400 Bad Request</title>\r\n\r\n

400 Bad Request

\r\n

cloudflare\r\n\r\n\r\n","level":"error","message":"Invalid URL","stack":"TypeError [ERR_INVALID_URL]: Invalid URL\n at new NodeError (node:internal/errors:399:5)\n at new URL (node:internal/url:560:13)\n at uriParam (/usr/local/lib/node_modules/@dvcorg/cml/src/utils.js:151:15)\n at watermarkUri (/usr/local/lib/node_modules/@dvcorg/cml/src/utils.js:142:10)\n at CML.publish (/usr/local/lib/node_modules/@dvcorg/cml/src/cml.js:330:13)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async visitor (/usr/local/lib/node_modules/@dvcorg/cml/src/cml.js:229:24)\n at async Promise.all (index 0)\n at async publishLocalFiles (/usr/local/lib/node_modules/@dvcorg/cml/src/cml.js:242:7)"}
Error: Process completed with exit code 1.

My CML code is:

name: CML & DVC
on: [push]
jobs:
train-and-report:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-python@v4
with:
python-version: '3.8.16'
- uses: iterative/setup-cml@v1
- uses: iterative/setup-dvc@v1
- name: Train model
run: |
pip install -r requirements.txt
python model.py
- name: Create CML report
env:
REPO_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
echo '## Data Summary' >> report.md
python -c "import pandas as pd; df = pd.read_csv('Data/Incidents_metro.csv'); print(df.head(10))" >> report.md
echo '## Column Histogram' >> report.md
python -c "import pandas as pd; import matplotlib.pyplot as plt; df = pd.read_csv('Data/Incidents_metro.csv'); df.hist(figsize=(10, 10)); plt.savefig('histogram.png')"
if [ -f histogram.png ]; then
echo 'Histogram image created successfully.'
else
echo 'Histogram image creation failed.'
exit 1
fi
echo '' >> report.md
cml comment create report.md

A suggestion...(optional)

No response

Pipe-Vash · 2023-06-30T16:38:14Z

Pipe-Vash
Jun 30, 2023

I am having a similar problem. In my case is:

{"code":"ERR_INVALID_URL","input":"<html>\r\n<head><title>400 Bad Request</title></head>\r\n<body>\r\n<center><h1>400 Bad Request</h1></center>\r\n<hr><center>cloudflare</center>\r\n</body>\r\n</html>\r\n","level":"error","message":"Invalid URL","stack":"TypeError [ERR_INVALID_URL]: Invalid URL\n at new NodeError (node:internal/errors:399:5)\n at new URL (node:internal/url:560:13)\n at uriParam (/usr/local/lib/node_modules/@dvcorg/cml/src/utils.js:149:15)\n at watermarkUri (/usr/local/lib/node_modules/@dvcorg/cml/src/utils.js:140:10)\n at CML.publish (/usr/local/lib/node_modules/@dvcorg/cml/src/cml.js:349:13)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async visitor (/usr/local/lib/node_modules/@dvcorg/cml/src/cml.js:247:26)\n at async Promise.all (index 0)\n at async publishLocalFiles (/usr/local/lib/node_modules/@dvcorg/cml/src/cml.js:261:7)"} Error: Process completed with exit code 1.

While my .yaml is the following:
`
name: Continuous Training
on:
push:
branches:
- workflow_continuous_training
schedule:
- cron: '0 */6 * * *'
workflow_dispatch:
inputs:
reason:
description: Why to run this?
required: false
default: running CT
jobs:
continuous-training:
runs-on: ubuntu-latest
steps:
- name: Checkout Repo
uses: actions/checkout@v2
- uses: iterative/setup-dvc@v1
- name: Set up Python 3.8
uses: actions/setup-python@v2
with:
python-version: 3.8

  - name: Train model
    env:
      SERVICE_ACCOUNT_KEY: ${{ secrets.SERVICE_ACCOUNT_KEY }}
    run: |
      pip3 install virtualenv
      virtualenv venv
      source venv/bin/activate
      pip install -r src/requirements.txt
      export GOOGLE_APPLICATION_CREDENTIALS=$(python utilities/setter.py)
      dvc pull model/model.pkl.dvc -r model-track
      dvc unprotect model/model.pkl
      dvc repro -f 
      echo "Training Completed"
      dvc add model/model.pkl -r model-track --to-remote
      dvc push model/model.pkl.dvc -r model-track
  - name: Commit .dvc file changes
    run: |
      git config --local user.email "pipe.vash@gmail.com"
      git config --local user.name "github-actions[bot]"
      git add model/model.pkl.dvc
      git commit -m "Updating model serialization"
  - uses: ad-m/github-push-action@master
    with:
        github_token: ${{ secrets.GITHUB_TOKEN }}
        branch: ${{ github.ref }}
  - uses: iterative/setup-cml@v1
  - name: Push metrics
    env:
      REPO_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    run: |
      cat report.txt >> report.md
      echo '![](./prediction_behavior.png "Prediction Behavior")' >> report.md
      cml comment create report.md

`

I have tried with different methods, but none of them works. Any help would be welcomed

0 replies

hwang9u · 2023-07-05T04:36:54Z

hwang9u
Jul 5, 2023

@Alimiji @Pipe-Vash

Hi :)
I had same problem and I resolved it!
First, I added node version (I think this didn't solve the error directly)
Second, I made new github token and named "TOKEN".
Because Github told me that "GITHUB_" should not be included in the token name.
So I changed secrets.GITHUB_TOKEN -> secrets.TOKEN and resolved it finally!
I hope this helps you!!!

2 replies

luyangliuable Oct 9, 2023

For the TOKEN did you put down your PAT as your secret?

GuillermoSainz07 Nov 9, 2024

thanks, this really solved my problem!!

samus-aran · 2023-08-01T13:34:37Z

samus-aran
Aug 1, 2023
Maintainer

Welcome to the GitHub Community, @Alimiji, we're happy you're here! You are more likely to get a useful response if you are posting your question(s) in the applicable category and are explicit about what your project entails--giving a few more details might help someone give you a nudge in the right direction. I've gone ahead and moved it for you. Good luck!e

0 replies

rushabhcodes · 2023-08-02T18:07:54Z

rushabhcodes
Aug 2, 2023

A "400 Bad Request" error is an HTTP status code that indicates the server could not understand the request sent by the client, often due to malformed or invalid syntax. This error typically occurs when there's an issue with the request sent to a web server, such as missing or incorrect parameters, headers, or data.

Here are some common reasons and solutions for encountering a "400 Bad Request" error:

Malformed URL: Ensure that the URL you are accessing is properly formatted, and there are no typos or special characters that could be causing issues.
Missing or invalid request parameters: Check if the required parameters for the request are present and have the correct format. If there are optional parameters, make sure they are provided correctly.
Invalid headers: Verify that any custom headers you're using are spelled correctly and are in the correct format.
Request content issue: If you're sending data with the request (e.g., in the case of a POST request), make sure the data is properly formatted and matches the expected structure.
Request size limit: Some servers may impose size limits on incoming requests. If your request is too large, it could result in a "400 Bad Request" error. Check if there are any size restrictions and try reducing the request size if necessary.
Cookies and caching: Sometimes, issues with cookies or cached data can lead to this error. Clear your browser's cache and cookies and try again.
Browser extensions: Certain browser extensions or plugins may interfere with the request, causing a "400 Bad Request" error. Try accessing the URL in an incognito/private browsing window to rule out any extension-related issues.
Server-side issues: Although less likely, the problem could also be on the server-side. The server might not be configured correctly to handle the request, or there could be a bug in the server code.

If you are the developer of the web application, you can check the server logs for more detailed information about the specific reason for the "400 Bad Request" error. Examining the logs can help you pinpoint the issue and fix it accordingly.

If the error persists and you are not in control of the server or application, you may want to reach out to the website's support team or the developers responsible for maintaining the service to report the issue and seek assistance.

0 replies

SAMIULLAH-KALHORO-DEV · 2023-08-05T11:31:42Z

SAMIULLAH-KALHORO-DEV
Aug 5, 2023

The error message you provided indicates that there was an issue with the URL or the request made to the server. The server responded with a "400 Bad Request" status code, indicating that the request was malformed or invalid in some way.

This error can occur for various reasons, such as:

Invalid URL: The URL used to make the request might be incorrect or improperly formatted.
Missing Required Data: The request may be missing some required data or parameters.
Invalid HTTP Method: The HTTP method used in the request (GET, POST, etc.) might not be supported or appropriate for the particular URL.
Authentication/Authorization Issues: The server may require authentication, and the request does not include the necessary credentials.
Server-Side Issue: There might be an issue on the server side that is causing the error.

To resolve this issue, you can try the following steps:

Double-check the URL: Make sure the URL you are trying to access is correct and properly formatted. Check for any typos or missing parts.
Check Request Parameters: If your request includes parameters or data, ensure that they are provided correctly.
Use the Appropriate HTTP Method: Verify that you are using the correct HTTP method (GET, POST, etc.) for the specific endpoint.
Check for Authentication/Authorization: If the server requires authentication, make sure to include the necessary credentials in your request.
Retry the Request: Sometimes, a temporary issue on the server can cause a "400 Bad Request" error. Retry the request after some time to see if the problem persists.

If you continue to encounter the error, there may be specific details in the server's response that could provide more insights into the issue. Checking the server logs or contacting the server administrators might be helpful in diagnosing the problem further.

0 replies

ajsalkp · 2024-03-27T10:52:22Z

ajsalkp
Mar 27, 2024

me also facing similar issue with cml . anybody can help on this issue?

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitHub Community

Error occuring during the running of cml file #57478

Uh oh!

{{title}}

Uh oh!

Replies: 6 comments 2 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Error occuring during the running of cml file #57478

Uh oh!

Hi everyone,

Hi everyone, I need your help please. This is the error that occurs:

{"code":"ERR_INVALID_URL","input":"\r\n<title>400 Bad Request</title>\r\n\r\n

400 Bad Request

A suggestion...(optional)

Replies: 6 comments · 2 replies

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

samus-aran Aug 1, 2023 Maintainer

Uh oh!

Uh oh!

Uh oh!

Hi everyone,
I need your help please. This is the error that occurs:

Replies: 6 comments 2 replies

samus-aran
Aug 1, 2023
Maintainer