Could not find module `discourse-common/lib/icon-library` - Installation

link管理

链接快照平台

输入网页链接，自动生成快照
标签化管理网页链接

相关文章推荐

坏坏的莴苣 · 【日系RPG】NPC歼8：从路人娘到女魔王无 ...· 1 月前 ·

八块腹肌的烈酒 · 【粤澳同心 ...· 4 月前 ·

逃课的筷子 · 我的妈妈叫桂梅——张桂梅和她的177个儿女-新华网· 6 月前 ·

坚韧的乌冬面 · Java-forEach增强for循环是值传 ...· 7 月前 ·

冲动的登山鞋 · libcurl长连接高并发多线程 - ...· 10 月前 ·

Any idea How we can solve below error?
uncaught Error: Could not find module


   discourse-common/lib/icon-library

imported from `discourse/plugins/discourse-solved/discourse/initializers/extend-for-solved-button
[v1.9.0.beta1]

I am trying to follow
https://meta.discourse.org/t/use-old-commit-to-build-discourse/108028/2

But I am getting error any idea?

I, [2019-01-31T17:08:39.945102 #15]  INFO -- : > cd /var/www/discourse/plugins && mkdir -p plugins
I, [2019-01-31T17:08:39.950402 #15]  INFO -- :
I, [2019-01-31T17:08:39.950737 #15]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/docker_manager.git
Cloning into 'docker_manager'...
I, [2019-01-31T17:08:41.890949 #15]  INFO -- :
I, [2019-01-31T17:08:41.891630 #15]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-solved.git
Cloning into 'discourse-solved'...
I, [2019-01-31T17:08:43.344731 #15]  INFO -- :
I, [2019-01-31T17:08:43.345246 #15]  INFO -- : > cd /var/www/discourse/plugins && cd discourse-solved
I, [2019-01-31T17:08:43.349650 #15]  INFO -- :
I, [2019-01-31T17:08:43.350051 #15]  INFO -- : > cd /var/www/discourse/plugins && get reset --hard 7745adb6eb0c1d1b2a37c9441c3877b7eec087cd
sh: 1: get: not found
I, [2019-01-31T17:08:43.354172 #15]  INFO -- :
I, [2019-01-31T17:08:43.354702 #15]  INFO -- : Terminating async processes
I, [2019-01-31T17:08:43.354881 #15]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/10/bin/postmaster -D /etc/postgresql/10/main pid: 70
I, [2019-01-31T17:08:43.355271 #15]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 186
2019-01-31 17:08:43.355 UTC [70] LOG:  received fast shutdown request
186:signal-handler (1548954523) Received SIGTERM scheduling shutdown...

yes i found that but still have issue.

I, [2019-01-31T17:31:46.695638 #15]  INFO -- : > cd /var/www/discourse/plugins && cd discourse-solved
I, [2019-01-31T17:31:46.699054 #15]  INFO -- :
I, [2019-01-31T17:31:46.699228 #15]  INFO -- : > cd /var/www/discourse/plugins && git reset --hard 7745adb6eb0c1d1b2a37c9441c3877b7eec087cd
fatal: Could not parse object '7745adb6eb0c1d1b2a37c9441c3877b7eec087cd'.
I, [2019-01-31T17:31:46.728342 #15]  INFO -- :
I, [2019-01-31T17:31:46.728832 #15]  INFO -- : Terminating async processes
I, [2019-01-31T17:31:46.728916 #15]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/10/bin/postmaster -D /etc/postgresql/10/main pid: 70

esepjav:

cd /var/www/discourse/plugins && git reset --hard 7745adb6eb0c1d1b2a37c9441c3877b7eec087cd

that’s the wrong folder, you’ll want to do the git reset in the discourse-solved folder.

thanks. It is worked in staging but I can not test to see if problem with solved button is ok or not.
staging and production are in different version, I need to ask for downtime for production. please keep ticket open. thanks.