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

fix doc: pin jinja2 version, incompatible with current nbsphinx #1742

Merged
merged 1 commit into from
Mar 25, 2022

Conversation

dweindl
Copy link
Member

@dweindl dweindl commented Mar 25, 2022

@codecov
Copy link

codecov bot commented Mar 25, 2022

Codecov Report

Merging #1742 (6b7d737) into develop (fee0d5a) will increase coverage by 0.02%.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #1742      +/-   ##
===========================================
+ Coverage    77.87%   77.90%   +0.02%     
===========================================
  Files           73       73              
  Lines        11364    11364              
===========================================
+ Hits          8850     8853       +3     
+ Misses        2514     2511       -3     
Flag Coverage Δ
cpp 74.80% <ø> (+0.04%) ⬆️
petab 62.51% <ø> (ø)
python 68.20% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
src/solver_cvodes.cpp 69.53% <0.00%> (+0.18%) ⬆️
src/exception.cpp 80.64% <0.00%> (+6.45%) ⬆️

@dweindl dweindl requested a review from FFroehlich March 25, 2022 09:50
@sonarcloud
Copy link

sonarcloud bot commented Mar 25, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@dweindl dweindl merged commit 9b13330 into develop Mar 25, 2022
@dweindl dweindl deleted the fix_pin_jinja branch April 4, 2022 21:19
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

1 participant