Skip to content

Initial PR#1

Merged
4 commits merged into
gooddata:masterfrom
lupko:master
Aug 5, 2021
Merged

Initial PR#1
4 commits merged into
gooddata:masterfrom
lupko:master

Conversation

@lupko

@lupko lupko commented Aug 5, 2021

Copy link
Copy Markdown
Contributor
  • xfer from personal private repo

@ghost

ghost commented Aug 5, 2021

Copy link
Copy Markdown

Build succeeded (check pipeline).

@ghost

ghost commented Aug 5, 2021

Copy link
Copy Markdown

Build succeeded (check pipeline).

@jaceksan jaceksan added the merge label Aug 5, 2021
@yenkins

yenkins commented Aug 5, 2021

Copy link
Copy Markdown

Sonar scan result

More detail, see in https://sonarqube-gate.intgdc.com/dashboard?id=gooddata-python-sdk-gate-PR1

To scan for vulnerabilities in dependencies and run unit tests (to get coverage report in sonar) please comment your PR with 'extended check sonar'.

@ghost ghost removed the merge label Aug 5, 2021
@ghost ghost merged commit 90b73f6 into gooddata:master Aug 5, 2021
@ghost

ghost commented Aug 5, 2021

Copy link
Copy Markdown

jaceksan added a commit to jaceksan/gooddata-python-sdk that referenced this pull request Mar 25, 2022
jaceksan added a commit to jaceksan/gooddata-python-sdk that referenced this pull request Mar 25, 2022
jaceksan added a commit to jaceksan/gooddata-python-sdk that referenced this pull request Mar 29, 2022
jaceksan added a commit to jaceksan/gooddata-python-sdk that referenced this pull request Mar 29, 2022
jaceksan added a commit to jaceksan/gooddata-python-sdk that referenced this pull request Mar 29, 2022
jaceksan added a commit to jaceksan/gooddata-python-sdk that referenced this pull request Apr 19, 2022
jaceksan added a commit to jaceksan/gooddata-python-sdk that referenced this pull request Apr 19, 2022
jaceksan added a commit to jaceksan/gooddata-python-sdk that referenced this pull request Apr 28, 2022
hkad98 referenced this pull request in hkad98/gooddata-python-sdk Aug 22, 2023
Prepare for productisation
Tomkess added a commit that referenced this pull request Jun 22, 2026
…-up routing

#1 max_clarification_turns: default was 20 (caused 462s timeout on GPT
conv-002). Now defaults to 3, exposed as --max-clarification-turns CLI flag
threaded through RunConfig -> run_agentic_items -> run_agentic_conversation.

#2 skill_routing leniency for follow-up turns: turn 0 requires explicit
set_skills (strict); turns 1+ check output_present only — the model carries
skill state from the prior turn, consistent with ToolSandbox milestone
evaluation and COMPASS conversation-level scoring. TurnResult gains turn_index
field; skill_success property branches on it.

JIRA: TRIVIAL
risk: nonprod
This pull request was closed.
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.

3 participants