mrutkows commented on pull request #482:
URL: https://github.com/apache/openwhisk-website/pull/482#issuecomment-847248216


   > > @Yiyiyimu OK, so i used https protocol with a personal access token and 
was able to push my suggested commit... All that remains is to figure out why 
the embedded image does not render the entire 2016-2021 graph, but still only 
renders 2016.
   > 
   > There are situations that the graph was captured and stored before it got 
fully rendered, and I just fixed this issue yesterday. It seems CDN cached the 
wrong image and I'll do the forced flush right now.
   
   Just flushed the local image cache again (Chrome and Mozilla both same 
behavior) and appears the page timed out watiing for the image so it displyaed 
a URL (link):
   
   <img width="851" alt="Screen Shot 2021-05-24 at 1 30 22 PM" 
src="https://user-images.githubusercontent.com/7816715/119391809-72139600-bc94-11eb-96a1-b39bcb12102a.png";>
   
   Clicking the link the website shows a blank graph:
   
   <img width="1364" alt="Screen Shot 2021-05-24 at 1 32 41 PM" 
src="https://user-images.githubusercontent.com/7816715/119391870-8c4d7400-bc94-11eb-9745-c000be811a1e.png";>
   
   forced a reloa of that page 
(https://www.apiseven.com/en/contributor-graph?chart=contributorOverTime&repo=apache/apisix)
 and the full graph appeared:
   
   <img width="833" alt="Screen Shot 2021-05-24 at 1 34 15 PM" 
src="https://user-images.githubusercontent.com/7816715/119392011-c3238a00-bc94-11eb-9128-eb7d56e5d259.png";>
   
   Returned to the OW website page and it now shows the full graph!  Yay!
   <img width="860" alt="Screen Shot 2021-05-24 at 1 35 02 PM" 
src="https://user-images.githubusercontent.com/7816715/119392146-f5cd8280-bc94-11eb-8343-98647455c4f8.png";>
   
   
   Is there a way to solve that timeout and the manual refresh steps?
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to