Closed tapaswenipathak closed 5 years ago
@tapaswenipathak Hey shall I work on this
Sure, go for it!
On Thu, May 9, 2019 at 10:09 AM Keshav Gupta notifications@github.com wrote:
Hi @devevignesh or @tapaswenipathak can I work upon this?
Sure! I review PRs on FCFS.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
-- Tapasweni
@tapaswenipathak as pr is based on FCFS(mentioned by you above) can i also try this?
On Thu, 9 May 2019, 3:54 p.m. Sourabh Pruthi, notifications@github.com wrote:
@tapaswenipathak https://github.com/tapaswenipathak when I do npm i list-theme it fails. The Theme repo of which you have provided the link isn't available as npm package
Run npm install && npm link
inside the repository. Yesterday I showed a
fix in a call. @mridubhatnagar, can you guide him?
—
You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tapaswenipathak/Photography-Competitions/issues/6#issuecomment-490847710, or mute the thread https://github.com/notifications/unsubscribe-auth/AA7TVIX6ZJW2KVKJELZ5MKTPUP3V7ANCNFSM4HK2P6YQ .
@tapaswenipathak
i have modified the table a bit .
On Fri, May 10, 2019 at 1:58 PM Sourabh Pruthi notifications@github.com wrote:
@tapaswenipathak
I don't see any photography competitions.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
-- Tapasweni
Add the code formatting, I can't read the error seems like npm error. Run a local heroku deployment. If you get stuck, feel free setting a call https://calendly.com/tapaswenipathak, please spend time before calling. On Fri, May 10, 2019 at 5:55 PM Sourabh Pruthi notifications@github.com wrote:
i tried it to deploy to heroku but i got the error
019-05-10T11:46:07.702724+00:00 app[api]: Release v2 created by user sourabhpruthi10@gmail.com 2019-05-10T11:46:07.702724+00:00 app[api]: Enable Logplex by user sourabhpruthi10@gmail.com 2019-05-10T11:46:07.600395+00:00 app[api]: Release v1 created by user sourabhpruthi10@gmail.com 2019-05-10T11:46:07.600395+00:00 app[api]: Initial release by user sourabhpruthi10@gmail.com 2019-05-10T11:52:06.000000+00:00 app[api]: Build started by user sourabhpruthi10@gmail.com 2019-05-10T11:52:48.111474+00:00 app[api]: Deploy 75a962ca by user sourabhpruthi10@gmail.com 2019-05-10T11:52:48.111474+00:00 app[api]: Release v3 created by user sourabhpruthi10@gmail.com 2019-05-10T11:52:48.129940+00:00 app[api]: Scaled to web@1:Free by user sourabhpruthi10@gmail.com 2019-05-10T11:52:50.789167+00:00 heroku[web.1]: Starting process with command npm start 2019-05-10T11:52:51.000000+00:00 app[api]: Build succeeded 2019-05-10T11:52:52.650108+00:00 heroku[web.1]: State changed from starting to crashed 2019-05-10T11:52:52.655598+00:00 heroku[web.1]: State changed from crashed to starting 2019-05-10T11:52:52.631188+00:00 heroku[web.1]: Process exited with status 1 2019-05-10T11:52:52.570383+00:00 app[web.1]: 2019-05-10T11:52:52.570399+00:00 app[web.1]: > list-theme@1.0.0 start /app 2019-05-10T11:52:52.570402+00:00 app[web.1]: > gulp watch 2019-05-10T11:52:52.570404+00:00 app[web.1]: 2019-05-10T11:52:52.576064+00:00 app[web.1]: sh: 1: gulp: not found 2019-05-10T11:52:52.579711+00:00 app[web.1]: npm ERR! file sh 2019-05-10T11:52:52.579951+00:00 app[web.1]: npm ERR! code ELIFECYCLE 2019-05-10T11:52:52.580114+00:00 app[web.1]: npm ERR! errno ENOENT 2019-05-10T11:52:52.580269+00:00 app[web.1]: npm ERR! syscall spawn 2019-05-10T11:52:52.581243+00:00 app[web.1]: npm ERR! list-theme@1.0.0 start: gulp watch 2019-05-10T11:52:52.581352+00:00 app[web.1]: npm ERR! spawn ENOENT 2019-05-10T11:52:52.581548+00:00 app[web.1]: npm ERR! 2019-05-10T11:52:52.581667+00:00 app[web.1]: npm ERR! Failed at the list-theme@1.0.0 start script. 2019-05-10T11:52:52.581775+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 2019-05-10T11:52:52.589444+00:00 app[web.1]: 2019-05-10T11:52:52.589587+00:00 app[web.1]: npm ERR! A complete log of this run can be found in: 2019-05-10T11:52:52.589753+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2019-05-10T11_52_52_583Z-debug.log 2019-05-10T11:52:55.197042+00:00 heroku[web.1]: Starting process with command npm start 2019-05-10T11:52:57.204585+00:00 heroku[web.1]: State changed from starting to crashed 2019-05-10T11:52:57.185596+00:00 heroku[web.1]: Process exited with status 1 2019-05-10T11:52:57.118974+00:00 app[web.1]: 2019-05-10T11:52:57.118989+00:00 app[web.1]: > list-theme@1.0.0 start /app 2019-05-10T11:52:57.118990+00:00 app[web.1]: > gulp watch 2019-05-10T11:52:57.118991+00:00 app[web.1]: 2019-05-10T11:52:57.123571+00:00 app[web.1]: sh: 1: gulp: not found 2019-05-10T11:52:57.127150+00:00 app[web.1]: npm ERR! file sh 2019-05-10T11:52:57.127348+00:00 app[web.1]: npm ERR! code ELIFECYCLE 2019-05-10T11:52:57.127505+00:00 app[web.1]: npm ERR! errno ENOENT 2019-05-10T11:52:57.127639+00:00 app[web.1]: npm ERR! syscall spawn 2019-05-10T11:52:57.128602+00:00 app[web.1]: npm ERR! list-theme@1.0.0 start: gulp watch 2019-05-10T11:52:57.128711+00:00 app[web.1]: npm ERR! spawn ENOENT 2019-05-10T11:52:57.128894+00:00 app[web.1]: npm ERR! 2019-05-10T11:52:57.129051+00:00 app[web.1]: npm ERR! Failed at the list-theme@1.0.0 start script. 2019-05-10T11:52:57.129158+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 2019-05-10T11:52:57.135176+00:00 app[web.1]: 2019-05-10T11:52:57.135321+00:00 app[web.1]: npm ERR! A complete log of this run can be found in: 2019-05-10T11:52:57.135409+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2019-05-10T11_52_57_130Z-debug.log 2019-05-10T11:53:25.759007+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=opensourceintern.herokuapp.com request_id=4822bb6f-5dae-49e4-bb3f-642d29c5dd53 fwd="157.36.222.170" dyno= connect= service= status=503 bytes= protocol=https 2019-05-10T11:53:26.282346+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=opensourceintern.herokuapp.com request_id=8ee6dbd2-9241-43aa-852b-eb3f0c215cdf fwd="157.36.222.170" dyno= connect= service= status=503 bytes= protocol=https
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
-- Tapasweni
On Fri, May 10, 2019 at 1:58 PM Sourabh Pruthi @.***> wrote: @tapaswenipathak I don't see any photography competitions. … — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread. -- Tapasweni
in the screenshot is the table showing the photography competition not visible? .actually i have added the table from index.html to theme index.html
@tapaswenipathak
2019-05-11T05:20:34.622845+00:00 heroku[web.1]: State changed from starting to crashed
2019-05-11T05:20:34.532086+00:00 app[web.1]:
2019-05-11T05:20:34.532104+00:00 app[web.1]: > list-theme@1.0.0 start /app
2019-05-11T05:20:34.532105+00:00 app[web.1]: > gulp watch
2019-05-11T05:20:34.532106+00:00 app[web.1]:
2019-05-11T05:20:34.542777+00:00 app[web.1]: sh: 1: gulp: not found
2019-05-11T05:20:34.546391+00:00 app[web.1]: npm ERR! file sh
2019-05-11T05:20:34.546611+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2019-05-11T05:20:34.546770+00:00 app[web.1]: npm ERR! errno ENOENT
2019-05-11T05:20:34.546923+00:00 app[web.1]: npm ERR! syscall spawn
2019-05-11T05:20:34.547917+00:00 app[web.1]: npm ERR! list-theme@1.0.0 start: gulp watch
2019-05-11T05:20:34.548036+00:00 app[web.1]: npm ERR! spawn ENOENT
2019-05-11T05:20:34.548241+00:00 app[web.1]: npm ERR!
2019-05-11T05:20:34.548361+00:00 app[web.1]: npm ERR! Failed at the list-theme@1.0.0 start script.
2019-05-11T05:20:34.548468+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2019-05-11T05:20:34.557296+00:00 app[web.1]:
2019-05-11T05:20:34.557452+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2019-05-11T05:20:34.557536+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2019-05-11T05_20_34_549Z-debug.log
2019-05-11T05:20:34.604948+00:00 heroku[web.1]: Process exited with status 1
i think this error is because of gulp because it is installed as dev dependencies and in heroku it is not able to find gulp so according to me we need to change start script
@tapaswenipathak ^^^
The repository has theme merged, closing.
I have added a theme.
npm i list-theme
.