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: egg layer x forwarded for #768

Merged
merged 4 commits into from
Dec 26, 2020
Merged

Conversation

echosoar
Copy link
Member

@echosoar echosoar commented Dec 17, 2020

fixed: #761

@gitpod-io
Copy link

gitpod-io bot commented Dec 17, 2020

@codecov-io
Copy link

codecov-io commented Dec 17, 2020

Codecov Report

Merging #768 (1f7d78c) into 2.x (ee77af5) will decrease coverage by 0.01%.
The diff coverage is 50.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##              2.x     #768      +/-   ##
==========================================
- Coverage   86.48%   86.47%   -0.02%     
==========================================
  Files         144      144              
  Lines        5904     5906       +2     
  Branches     1092     1093       +1     
==========================================
+ Hits         5106     5107       +1     
- Misses        766      767       +1     
  Partials       32       32              
Impacted Files Coverage Δ
packages-serverless/egg-layer/index.js 85.36% <50.00%> (-1.82%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ee77af5...1f7d78c. Read the comment docs.

@czy88840616 czy88840616 changed the title Fix/egg layer x forwarded for fix: egg layer x forwarded for Dec 26, 2020
@czy88840616 czy88840616 merged commit 568379f into 2.x Dec 26, 2020
@czy88840616 czy88840616 deleted the fix/egg-layer-X-Forwarded-For branch December 26, 2020 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants