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

chore(github): Add bug and feature issue templates #2

Merged
merged 1 commit into from
Jul 3, 2020

Conversation

chenjunbiao
Copy link
Contributor

Bug issue template, Feature issue template

Bug  issue template, Feature issue template
@fanweixiao fanweixiao changed the title feat(*): Add bug and feature issue templates chore(github): Add bug and feature issue templates Jul 3, 2020
@fanweixiao fanweixiao merged commit 67e9c23 into master Jul 3, 2020
@fanweixiao fanweixiao deleted the feat/issue-templates branch July 3, 2020 10:52
xiaojian-hong referenced this pull request in xiaojian-hong/yomo Aug 16, 2022
* feat(mesh): support zipper communication

* add edge-mesh example

* refactor: add specific source/flow/sink for mesh example

* remove bin files in mesh example folder

* chore(deps): bump github.com/yomorun/yomo from 1.2.520 to 1.3.0
fanweixiao added a commit that referenced this pull request Mar 6, 2024
## Related Docs: 

- https://ai.google.dev/docs/gemini_api_overview
- https://ai.google.dev/docs/function_calling

## How to use this provider

```yaml
bridge:
  ai:
    server:
      addr: localhost:8000
      provider: gemini

    providers:
      gemini:
        api_key: <your-api-key>
```

## Be careful that

1. The data format describes in api doc is different from actual api.
These can be found from the unit tests.
2. You can not set your function with `-` as this will break your api
response. Google will drop characters of the function name in its
response. So, I have to check this `-`, and replace to `_` if it
presence.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants