Commit Graph
3734 Commits
Author SHA1 Message Date
Krrish Dholakia a6968d06e6 fix(anthropic.py): fix anthropic prompt 2023-10-09 15:22:58 -07:00
ishaan-jaff ba754a07a3 (feat) add --cost as a flag to the proxy server cli 2023-10-09 15:05:17 -07:00
Krrish Dholakia 70720c255e bump: version 0.6.1 → 0.6.2 2023-10-09 15:03:44 -07:00
Krrish Dholakia 42e0d7cf68 fix(proxy_server): returns better error messages for invalid api errors 2023-10-09 15:03:44 -07:00
ishaan-jaff 262f874621 (feat) add cost tracking to proxy server 2023-10-09 14:51:37 -07:00
Krrish Dholakia a9f7a80e3d feat(proxy_cli.py): add max budget to proxy 2023-10-09 14:11:30 -07:00
ishaan-jaff 4e64f123ef (fix) api_base, api_version and api_key 2023-10-09 14:11:05 -07:00
ishaan-jaff 7587e8ce06 (fix) Bedrock test fix, stop tryin to read aws session token 2023-10-09 13:49:22 -07:00
ishaan-jaff 8d4c109171 (test) add async + non stream test for ollama 2023-10-09 13:47:08 -07:00
ishaan-jaff bf4ce08640 (fix) acompletion for ollama non streaing 2023-10-09 13:47:08 -07:00
Krish Dholakia 74c5e6f415 Updated config.yml 2023-10-09 13:40:20 -07:00
Krish Dholakia 4900f11570 Updated config.yml 2023-10-09 13:30:51 -07:00
Krrish Dholakia c74e4a3920 bump: version 0.6.0 → 0.6.1 2023-10-09 13:10:14 -07:00
Krrish Dholakia 4059f408d0 fix(proxy_cli): accept drop params and add_function_to_prompt 2023-10-09 13:10:07 -07:00
Krrish Dholakia 46bfeddfc7 docs(stream.md): fix async streaming tutorial 2023-10-09 11:47:49 -07:00
Krrish Dholakia c3e4c3e3f0 fix(proxy_server.py): add link to docs 2023-10-09 11:35:42 -07:00
Krrish Dholakia 3d809707c0 fix(proxy_cli.py): add drop params and add function to prompt in cli (complete issue)
https://github.com/BerriAI/litellm/issues/557
2023-10-09 11:33:45 -07:00
Krrish Dholakia 72ac4fe781 bump: version 0.5.6 → 0.6.0 2023-10-09 09:53:53 -07:00
Krrish Dholakia 704be9dcd1 feat(factory.py): option to add function details to prompt, if model doesn't support functions param 2023-10-09 09:53:53 -07:00
ishaan-jaff f6f7c0b891 (feat) add api_key, api_base, api_version to completion 2023-10-09 08:13:12 -07:00
Ishaan JaffandGitHub 14b6261f47 Merge pull request #560 from kylehh/add_custom_openai
Add custom_openai type in provider list
2023-10-09 07:15:19 -07:00
Ishaan JaffandGitHub 017d9367ca Merge pull request #562 from zhooda/main
Add support for passing external bedrock clients to completion
2023-10-09 07:12:56 -07:00
Zeeshan Hooda 112df4a19d (test) add bedrock existing client auth test 2023-10-09 03:39:40 -06:00
Zeeshan Hooda f735ca7e46 (docs) bedrock pass existing client to completion 2023-10-09 01:14:53 -06:00
Zeeshan Hooda 5f55b4a1ab (feat) bedrock pass client to completion 2023-10-09 00:51:58 -06:00
Kyle 22525d9333 Add custom_openai type in provider list 2023-10-08 21:20:10 -07:00
Ishaan JaffandGitHub 7add88a8b0 Merge pull request #558 from Sir-Photch/patch-1
Add `host` option to `run_server()`
2023-10-08 13:30:27 -07:00
Sir-PhotchandSir-Photch 708d61b207 make --test respect host and port 2023-10-08 20:42:49 +02:00
ChristophandGitHub 64c9795871 Add host cli parameter 2023-10-08 17:59:47 +00:00
Krrish Dholakia f7473638ce docs(set_keys.md): doc updates 2023-10-08 10:01:19 -07:00
Krrish Dholakia c48c6e9358 docs(set_keys.md): adds validate_environment function to docs 2023-10-08 10:00:56 -07:00
Krrish Dholakia a833e3f929 docs(proxy_server.md): adding /ollama_logs endpoint to docs 2023-10-07 20:38:19 -07:00
Krrish Dholakia a8c3871b02 ci(test_logging): need to rewrite test_logging to work in parallel testing 2023-10-07 19:18:09 -07:00
Krrish Dholakia 9ac3ff584c ci(test_logging): have a change to make circle ci run our testing 2023-10-07 18:33:24 -07:00
Krrish Dholakia 0fb95faa50 ci(config.yml): run all tests on circle ci 2023-10-07 18:28:25 -07:00
Krrish Dholakia 28a2e31ede ci(test_logging): running just this test on circle ci 2023-10-07 18:23:54 -07:00
Krrish Dholakia 9f118bb5db ci(test_logging): debugging circle ci 2023-10-07 18:19:55 -07:00
Krrish Dholakia 4b35f1b6bd ci(test_logging): testing why circle ci keeps failing this test 2023-10-07 18:16:32 -07:00
Krrish Dholakia 713d998680 aider: Added print working directory command before running pytest in CircleCI config.
# Aider chat conversation:

USER: what directory is pytest in?

ASSISTANT: The `pytest` command is typically installed in the `bin` directory of your Python environment. If you're using a virtual environment, it would be in the `bin` directory of that environment.

However, the location of the `pytest` command doesn't affect how
^C KeyboardInterrupt

USER: i mean the pytest command in the config.yml

ASSISTANT: The pytest command in the `.circleci/config.yml` file is being run in the `~/project` directory. This is specified by the `working_directory` key in the `local_testing` job.

When the `python -m pytest -vv test_logging.py --junitxml=test-results/junit.xml` command is run, it's being run in the `~/project` directory.

If `test_logging.py` is not in the `~/project` directory, you would need to provide the relative path to it from `~/project`. For example, if it's in a `tests` directory under `~/project`, you would use `tests/test_logging.py`.

USER: can you print the pwd before running the pytest?  # Run pytest and generate JUnit XML report
      - run:
          name: Run tests
          command: |
            python -m pytest -vv tests/test_logging.py --junitxml=test-results/junit.xml
          no_output_timeout: 30m

ASSISTANT: Sure, you can add a command to print the current working directory (pwd) before running the pytest command. Here's how you can do it:

```yaml
.circleci/config.yml
<<<<<<< HEAD
      # Run pytest and generate JUnit XML report
      - run:
          name: Run tests
          command: |
            python -m pytest -vv tests/test_logging.py --junitxml=test-results/junit.xml
          no_output_timeout: 30m
=======
      # Run pytest and generate JUnit XML report
      - run:
          name: Run tests
          command: |
            pwd
            python -m pytest -vv tests/test_logging.py --junitxml=test-results/junit.xml
          no_output_timeout: 30m
>>>>>>> updated
```

This change will print the current working directory before running the pytest command.
2023-10-07 18:14:35 -07:00
Krrish Dholakia cd8ae2ecf6 test(test_logging): add back more tests for circle ci 2023-10-07 18:11:03 -07:00
Krish Dholakia a871d85696 Updated config.yml 2023-10-07 18:06:07 -07:00
Krrish Dholakia 51663e5618 test(test_logging): commenting out all but one test to see if it works on circle ci 2023-10-07 18:02:23 -07:00
Krrish Dholakia 3a15425288 aider: Modified CircleCI configuration to run pytest only on test_logging.py
# Aider chat conversation:

USER: what does `python -m pytest -vv --junitxml=test-results/junit.xml` do?

ASSISTANT: This command runs the pytest testing tool for Python in a specific way. Here's a breakdown of what each part does:

- `python -m pytest`: This runs pytest as a module using the Python interpreter. Pytest is a testing framework that allows you to easily create small, simple tests, as well as complex, functional testing for applications and libraries.

- `-vv`: This is an option for pytest that increases verbosity. Pytest without any `-v` is silent except for failures. One `-v` makes it print the test function names, and `-vv` also prints the individual test cases within those functions.

- `--junitxml=test-results/junit.xml`: This is an option for pytest that tells it to generate a test report in the form of an XML file in the JUnit format. This is useful for integrating the test results into tools that understand JUnit test reports, like many continuous integration servers. The `test-results/junit.xml` part specifies the location and name of the report file to generate.

So, in summary, this command runs all the pytest tests in the current directory and its subdirectories, prints detailed output about what tests are being run and their results, and generates a JUnit-format XML report of the test results.

USER: `.circleci/config.yml`

ASSISTANT: I'm sorry, but your request is not clear. Could you please provide more details about what you want to do with the `.circleci/config.yml` file? Are there any specific changes you want to make or any issues you're facing with it?

USER: how do i modify the pytest to only run test_logging.py

ASSISTANT: To modify the pytest command to only run `test_logging.py`, you need to specify the file name in the command. Here is how you can do it:

```yaml
.circleci/config.yml
<<<<<<< HEAD
      - run:
          name: Run tests
          command: |
            python -m pytest -vv --junitxml=test-results/junit.xml
          no_output_timeout: 30m
=======
      - run:
          name: Run tests
          command: |
            python -m pytest -vv test_logging.py --junitxml=test-results/junit.xml
          no_output_timeout: 30m
>>>>>>> updated
```

This change will make pytest only run the tests in the `test_logging.py` file. If `test_logging.py` is not in the root directory, you should provide the relative path to it from the root directory. For example, if it's in a `tests` directory, you would use `tests/test_logging.py`.
2023-10-07 17:58:07 -07:00
Krrish Dholakia 10ad137b2e docs(telemetry): add telemetry to docs 2023-10-07 17:49:42 -07:00
Krish DholakiaandGitHub f2febff0bb Merge pull request #556 from AnderMendoza/main
Readme Update
2023-10-07 17:29:43 -07:00
Krrish Dholakia 51e5e2b8d5 docs(proxy_server): doc cleanup 2023-10-07 17:29:04 -07:00
ishaan-jaff 051b21b61f (feat) proxy_server display model list when user does not specify model 2023-10-07 17:19:02 -07:00
ishaan-jaff e987d31028 (feat+fix) proxy_cli max_tokens int, --test stream 2023-10-07 16:38:40 -07:00
Krrish Dholakia 212734f142 test(test_logging): adding print statements for debugging circle ci 2023-10-07 16:20:17 -07:00
ishaan-jaff f37e2d4f8f (test) add back tg ai streaming test 2023-10-07 16:15:54 -07:00