Hi Pavindu, The attached image is not available. Probably because the emails going through the Apache mail servers don't support them. Can you host the image somewhere else and put a link instead?
Regarding the error you are facing, Nadeeshan who did the initial implementation of the UI will be able to help. I will have a look at it as well. Been busy these few days. Imesha On Fri, 2 Apr 2021 at 23:15, Pavindu Lakshan <pavindulaks...@gmail.com> wrote: > Hi Imesha, > > By following the instructions in the last email, I was able to view the > React.js dashboard homepage without any CORS errors. However, when > navigating to the `/product`, `/products` and `/productIngest` pages, the > dashboard fails to render the correct pages as expected. Instead, I see an > error like follows. > [image: oodt_react_mui_style_isssue.PNG] > > This error doesn't occur when "withStyle" HOC is removed from the exported > components, but then it affects the styles. I also opened a question on > StackOverflow <https://stackoverflow.com/q/66922317/8810941> asking for a > solution for this issue and still trying to fix that issue, because it's > essential to fix this issue in order to view what has already been done in > the OPSUI React.js dashboard. > > Regarding the proposal, there does exist such a functionality in the GSoC > dashboard as you mentioned. I will share the proposal soon once I am able > to solve the above-mentioned problem and fully view the existing features > in the React.js OPSUI dashboard. > > Thank you and best regards > Pavindu > > On Wed, Mar 31, 2021 at 7:43 AM Imesha Sudasingha <ime...@apache.org> > wrote: > >> Hi Pavindu, >> >> Great progress. This CORS issue is expected because we run React.Js on a >> separate port than the port where the REST APIs are running. Therefore, >> for >> the moment, try with using a CORS plugin for your browser. In the future, >> we have to support adding CORS configuration to the REST APIs. >> >> Regarding the proposal, around 2,3 years back, GSoC dashboard allowed >> uploading a link to your proposal and sharing it as a draft. Does that >> functionality exist now? >> >> Imesha >> >> On Tue, 30 Mar 2021 at 11:28, Pavindu Lakshan <pavindulaks...@gmail.com> >> wrote: >> >> > Hi Imesha, >> > >> > I was able to solve the issues mentioned in the last email. The issues >> in >> > the wifi driver of my computer had caused those. Managed to get the >> > React.js dashboard up and running as well, but still getting CORS issues >> > therefore OODT ingested files are not shown in the dashboard. >> > >> > I also hope to share my project proposal with you, as a Google doc, to >> get >> > your feedback on it. Can you let me know if it is okay to share it with >> > your personal Gmail address, or what process I should follow? >> > >> > Thank you >> > >> > Best regards >> > Pavindu Lakshan >> > >> > On Sat, Mar 27, 2021 at 9:08 PM Pavindu Lakshan < >> pavindulaks...@gmail.com> >> > wrote: >> > >> > > Hi Imesha, >> > > >> > > It took me several days to respond because of my university exams. >> > > However, I went through the articles you mentioned and they helped me >> to >> > > broaden my understanding of what Apache OODT is and its use cases. >> Thank >> > > you for that. >> > > >> > > Also, I cloned the repository, was able to get it up and running with >> > > Docker on a Windows machine and visited the existing OPS UI dashboard. >> > > Nevertheless, I faced the following problems and wasn't able to solve >> > them >> > > on my own. >> > > >> > > 1. When trying to ingest a txt file as mentioned in this medium >> article >> > > <https://faun.pub/apache-oodt-with-docker-84d32525c798>, I get the >> > > following error. >> > > >> > > *error:** ERROR: Failed to ingest product 'test.txt' : >> > > java.net.ConnectException: Connection refused (Connection refused)* >> > > *what I have tried up to now:* searched for a solution but none was >> > > found. Does this happen because I'm on Windows OS? >> > > *steps to reproduce:* Follow the medium article from the beginning and >> > > this error appears when trying out step 9. >> > > >> > > 2. I tried to view the React.js app by checking out to >> /react-components >> > > of the development branch. But when I tried to install NPM >> dependencies >> > in >> > > plugins, I get the below errors. >> > > >> > > *errors:* >> > > In OPSUI sample app: invalid json response body at >> > > https://registry.npmjs.org/@material-ui%2fstyles reason: Unexpected >> end >> > > of JSON input >> > > In oodt_wm_plugin: invalid json response body at >> > > https://registry.npmjs.org/@babel%2fpreset-env reason: Unexpected >> end of >> > > JSON input >> > > *what I have tried up to now:* clean npm cache, use --force and >> > > --legacy-peer-deps arguments, update dependencies in package.json to >> the >> > > latest. >> > > *steps to reproduce:* Clone the repo, switch to the development >> branch, >> > > move to react-components folder and try to install dependencies in >> each >> > > plugin with *npm install*. >> > > >> > > It would be a great help if you can provide me with suggestions to >> > > overcome these issues. >> > > >> > > Thanks and best regards >> > > Pavindu >> > > >> > > On Mon, Mar 22, 2021 at 12:12 PM Imesha Sudasingha < >> > > imesha.sudasin...@gmail.com> wrote: >> > > >> > >> Hi Pavindu, >> > >> >> > >> Thanks for your interest. In order to get started with OODT, you can >> > refer >> > >> to this [1] [2] article to get it up and running with Docker. >> > >> First, you will have to get some overall understanding of OODT. >> > Basically, >> > >> >> > >> 1. File manager - File ingestion and meta data extraction >> > >> 2. Workflow manager - Schedule and run workflows >> > >> 3. Crawler - Used to crawl directories and ingest files with file >> > manager >> > >> in bulk >> > >> 4. Resource Manager - Execute, monitor and track jobs, resources as a >> > >> whole >> > >> 5. OPSUI - OPSUI is like the management dashboard which shows status >> and >> > >> data of all those components. >> > >> >> > >> It's better if you have a look at the existing OPSUI (mentioned in >> > almost >> > >> all the docs) and then have a look at the React.js based novel UI. >> > >> Let us know if you have any questions. >> > >> >> > >> [1] https://medium.com/faun/apache-oodt-with-docker-84d32525c798 >> > >> [2] https://cwiki.apache.org/confluence/display/OODT/Getting+Started >> > >> >> > >> Cheers, >> > >> Imesha >> > >> >> > >> On Mon, 22 Mar 2021 at 07:22, Pavindu Lakshan < >> pavindulaks...@gmail.com >> > > >> > >> wrote: >> > >> >> > >> > Hello all, >> > >> > >> > >> > I'm Pavindu Lakshan, a final year undergraduate of the University >> of >> > >> > Moratuwa, who has working experience in Node.js and React.js. I >> would >> > >> like >> > >> > to work on this issue, Improving OPSUI React.js UI with advanced >> > >> > functionalities <https://issues.apache.org/jira/browse/OODT-1035>, >> > for >> > >> > GSoC >> > >> > 2021 since this involves the technologies that I'm most familiar >> with. >> > >> > >> > >> > For now, I have a very basic understanding of what OODT does, Also, >> > I'm >> > >> > going through the medium articles that Imesha had posted on the >> issue >> > >> and >> > >> > going to follow the official tutorial >> > >> > <https://cwiki.apache.org/confluence/display/OODT/Core+Tutorials>. >> > >> > >> > >> > Feedback and suggestions on my current learning path and future >> steps >> > >> that >> > >> > I should follow are highly appreciated. >> > >> > >> > >> > Thank you >> > >> > >> > >> > Best regards >> > >> > Pavindu Lakshan >> > >> > >> > >> >> > > >> > >> >
