sassoftware / ci360-download-client-python Goto Github PK

Pandas 2.0 which was released as GA in April removed the error_bad_lines parameter from read_csv. The function readResetRange uses this parameter which generates an error when calling due to the api change in Pandas. The function needs to be changed to remove the error_bad_lines argument.

Current workaround is to set pandas==1.5.2 when installing.

Hi,

I'm working with this client to download Discover data, but I'm having problems choosing a good delimiter, there is a way to quote the text fields?

thanks,

Marcos.

There's an error on line 949 of discover.py:

CI360 DISCOVER Download API (V0.9) - last updated 23 Mar 2020Traceback (most recent call last):
  File "discover.py", line 949, in <module>
    headers = {'authorization': "Bearer "+bytes.decode(token),'cache-control': "no-cache"}
TypeError: descriptor 'decode' for 'bytes' objects doesn't apply to a 'str' object

In the latest version of PyJwt module, the return type of jwt.encode has changed to a str type instead of bytes. See changelog here:
https://pyjwt.readthedocs.io/en/latest/changelog.html#improve-typings.

Not sure whether you want to test the type to accommodate earlier versions of PyJwt, but the simple fix is changing the line to:
headers = {'authorization': "Bearer "+ token,'cache-control': "no-cache"}

Hi,

While trying to run the agent, our customer got an error:

error executing <function getSchema at 0x7feabe96a660>

exception HTTPSConnectionPool(host='ci-360-deployment-prod-eu-west-1.s3.eu-west-1.amazonaws.com', port=443): Max retries exceeded with url: /CodeDeploy/release/pipeline/Infra/mkt-infra-orchestration/0.0.1-2789b65/discover/metadata/detail_schema_v4.json?X-Amz-Security-Token= (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992)')))

The certifi module is up to date. I was verifying the issue and I'm not sure if I have to modify the agent's code or if it its a problem with VM/proxy configuration. Have you ever encoutered a similar problem?

Best regards,
Kamil Kmieć