| Summary: | Create a JSON feed of all the projects a member company is currently contributing to | ||
|---|---|---|---|
| Product: | Community | Reporter: | Benjamin Cabé <contact> |
| Component: | API.eclipse.org | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | chris.guindon, denis.roy, ian.skerrett, wayne.beaton, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | stalebug | ||
|
Description
Benjamin Cabé
FWIW I would be surprised if itemis and IBM would be the only ones causing an issues. Looks like eg IBH systems is in the same situation It would seem a lot of the member links are not working. Oracle and SAP for instance. I am not sure what is going on here. I am currently working on an update for the membership pages and they load just fine on staging: http://staging.eclipse.org/membership/showMember.php?member_id=656 It seems that this was caused by too many Apache connections and our php-vm's couldn't fetch a JSON feed from the PMI. This should be fixed now. Looks good indeed, thanks Chris.
> It seems that this was caused by too many Apache connections and our
> php-vm's couldn't fetch a JSON feed from the PMI.
Why are membership pages fetching JSON from PMI?
(In reply to Denis Roy from comment #6) > > It seems that this was caused by too many Apache connections and our > > php-vm's couldn't fetch a JSON feed from the PMI. > > Why are membership pages fetching JSON from PMI? It's for the "Company XYZ is an Active Contributor to the following Project(s):" http://staging.eclipse.org/membership/showMember.php?member_id=656 We are currently doing the following: 1. We are fetching all the project id's from a specific company from the dashboard database. 2. For each project id, we are fetching a JSON feed from the PMI. From what I can see, we are only doing this for the full title of a project. We need a better way of handling this. I was going to open a new bug about this but I think we can use this one. Our current solution is problematic. The IBM profile is currently doing 40 requests to the PMI for one page load. Here's what I propose: 1. We need to create a new callback on the PMI that returns a JSON feed of every project for a specific company, instead of fetching a JSON file for each project. We could use projects.eclipse.org/json/member/[id]. The current URL for a project JSON feed is projects.eclipse.org/json/project/[id] 2. The PMI will be responsible of doing the request to the dashboard database to fetch all the project id's for a specific company. 2. Use this new JSON feed in my new membership class in eclipse.org-common https://git.eclipse.org/r/#/c/44619/ > 2. For each project id, we are fetching a JSON feed from the PMI.
Using a web service I presume?
Good grief!
(In reply to Christopher Guindon from comment #7) > Here's what I propose: > > 1. We need to create a new callback on the PMI that returns a JSON feed of > every project for a specific company, instead of fetching a JSON file for > each project. > > We could use projects.eclipse.org/json/member/[id]. The current URL for a > project JSON feed is projects.eclipse.org/json/project/[id] > > 2. The PMI will be responsible of doing the request to the dashboard > database to fetch all the project id's for a specific company. I have a patch ready for this: https://foundation.eclipse.org/r/#/c/148/ (In reply to Christopher Guindon from comment #9) > (In reply to Christopher Guindon from comment #7) > > > Here's what I propose: > > > > 1. We need to create a new callback on the PMI that returns a JSON feed of > > every project for a specific company, instead of fetching a JSON file for > > each project. > > > > We could use projects.eclipse.org/json/member/[id]. The current URL for a > > project JSON feed is projects.eclipse.org/json/project/[id] > > > > > 2. The PMI will be responsible of doing the request to the dashboard > > database to fetch all the project id's for a specific company. > > I have a patch ready for this: > https://foundation.eclipse.org/r/#/c/148/ This was committed. I updated my patch for the new membership class: https://git.eclipse.org/r/#/c/44619/1..2/classes/membership/membership.class.php This issue will be fixed once we roll out the new membership pages. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. Can we declare victory? I say yes we can. -M. |