Twitter bot在Heroku上托管时返回“未定义”值，但在我的本地机器上运行良好

jvlzgdj9  于 2022-11-24  发布在  其他
关注(0)|答案(2)|浏览(139)

我有一个Twitter机器人，它可以发布股票交易的信息，每当我从VS Code运行这个机器人时，它都能正常工作，并发布我想要的值。现在我需要在Heroku上托管它，但当我这样做时，脚本执行发布的值最终会变成undefined、see image。priceModule和nameModule也会发生这种情况，我不明白为什么。它在本地工作得很好，有没有解决这个问题的办法？

索引.js

// MODULES
const rwClient = require("./TwitterClient.js");
const cronjob = require("cron").CronJob;
const priceModule = require("./price");
const nameModule = require("./name");

(async () => {

    // Async function that creates the Tweet
    const tweet = async () => {
        try {
            await rwClient.v2.tweet(
                "Name: " + await nameModule() + '\n' +
                "Amount Purchased: " + await priceModule() + '\n'
            );

        } catch (error) {
            console.error(error)
        }
    }

    console.log(
        "Name: " + await nameModule() + '\n' +
        "Amount Purchased: " + await priceModule() + '\n'
    );

    tweet();
    console.log("Tweet executed");

    // CronJob, executes every 6 hours
    const job = new cronjob("0 */4 * * *", () => {
        tweet();
        console.log("Next tweet executed");
    });

    job.start();
  
})();

名称模块.js

// MODULES
const puppeteer = require("puppeteer");

// Url where we get and scrape the data from
const url = "https://www.sec.gov/edgar/search/#/dateRange=30d&category=custom&forms=4";

let browser;
module.exports = () => (async () => {
  browser = await puppeteer.launch();
  const [page] = await browser.pages();
  const $ = (...args) => page.waitForSelector(...args);
  const text = async (...args) =>
    (await $(...args)).evaluate(el => el.textContent.trim());
  await page.goto(url, {waitUntil: "domcontentloaded"});
  await page.reload({waitUntil: "domcontentloaded"});
  const info = {
    secTableEN: await text(".table td.entity-name"),
    secTableFiled: await text(".table td.filed"),
    secTableLink: await text(".table td.filetype"),
  };

  return info.secTableEN;
})()
  .catch(err => console.error(err))
  .finally(() => browser?.close());

价格模块

// MODULES
const puppeteer = require("puppeteer");

// Url where we get and scrape the data from
const url = "https://www.sec.gov/edgar/search/#/dateRange=30d&category=custom&forms=4";

let browser;
module.exports = () => (async () => {
    browser = await puppeteer.launch();
    const [page] = await browser.pages();
    const ua = "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36";
    await page.setUserAgent(ua);
    await page.goto(url, {waitUntil: "domcontentloaded", timeout: 0});
    await page.reload({waitUntil: "domcontentloaded"});
    const responseP = page.waitForResponse(res =>
      res.status() === 200 && res.url().endsWith(".xml")
    );
    const a = await page.waitForSelector(".filetype .preview-file");
    await a.click();
    const html = await (await responseP).text();
    await page.evaluate(html => document.body.outerHTML = html, html);
    const price = await page.$$eval(".FormText", els =>
      els.find(e => e.textContent.trim() === "$")
        .parentNode
        .textContent
        .trim()
    );

    return price;

  })()
    .catch(err => console.error(err))
    .finally(() => browser?.close());

来自Heroku的活动日志

2022-11-15T12:44:00.060455+00:00 app[worker.1]:     at ChromeLauncher.executablePath (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:166:25)
2022-11-15T12:44:00.060455+00:00 app[worker.1]:     at ChromeLauncher.launch (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:70:37)
2022-11-15T12:44:00.060455+00:00 app[worker.1]:     at async /app/numShares.js:9:15
2022-11-15T12:44:00.060456+00:00 app[worker.1]:     at async CJ.<anonymous> (/app/index.js:39:46)
2022-11-15T12:44:00.060711+00:00 app[worker.1]: Error: Could not find Chromium (rev. 1056772). This can occur if either
2022-11-15T12:44:00.060711+00:00 app[worker.1]:  1. you did not perform an installation before running the script (e.g. `npm install`) or
2022-11-15T12:44:00.060711+00:00 app[worker.1]:  2. your cache path is incorrectly configured (which is: /app/.cache/puppeteer).
2022-11-15T12:44:00.060712+00:00 app[worker.1]: For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
2022-11-15T12:44:00.060712+00:00 app[worker.1]:     at ChromeLauncher.resolveExecutablePath (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:120:27)
2022-11-15T12:44:00.060712+00:00 app[worker.1]:     at ChromeLauncher.executablePath (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:166:25)
2022-11-15T12:44:00.060713+00:00 app[worker.1]:     at ChromeLauncher.launch (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:70:37)
2022-11-15T12:44:00.060713+00:00 app[worker.1]:     at async /app/price.js:9:15
2022-11-15T12:44:00.060713+00:00 app[worker.1]:     at async CJ.<anonymous> (/app/index.js:39:66)
2022-11-15T12:44:00.060953+00:00 app[worker.1]: Error: Could not find Chromium (rev. 1056772). This can occur if either
2022-11-15T12:44:00.060954+00:00 app[worker.1]:  1. you did not perform an installation before running the script (e.g. `npm install`) or
2022-11-15T12:44:00.060954+00:00 app[worker.1]:  2. your cache path is incorrectly configured (which is: /app/.cache/puppeteer).
2022-11-15T12:44:00.060954+00:00 app[worker.1]: For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
2022-11-15T12:44:00.060954+00:00 app[worker.1]:     at ChromeLauncher.resolveExecutablePath (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:120:27)
2022-11-15T12:44:00.060955+00:00 app[worker.1]:     at ChromeLauncher.executablePath (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:166:25)
2022-11-15T12:44:00.060955+00:00 app[worker.1]:     at ChromeLauncher.launch (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:70:37)
2022-11-15T12:44:00.060955+00:00 app[worker.1]:     at async /app/stock.js:9:15
2022-11-15T12:44:00.060955+00:00 app[worker.1]:     at async CJ.<anonymous> (/app/index.js:40:30)
2022-11-15T12:44:00.061194+00:00 app[worker.1]: Error: Could not find Chromium (rev. 1056772). This can occur if either
2022-11-15T12:44:00.061195+00:00 app[worker.1]:  1. you did not perform an installation before running the script (e.g. `npm install`) or
2022-11-15T12:44:00.061195+00:00 app[worker.1]:  2. your cache path is incorrectly configured (which is: /app/.cache/puppeteer).
2022-11-15T12:44:00.061195+00:00 app[worker.1]: For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
2022-11-15T12:44:00.061195+00:00 app[worker.1]:     at ChromeLauncher.resolveExecutablePath (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:120:27)
2022-11-15T12:44:00.061196+00:00 app[worker.1]:     at ChromeLauncher.executablePath (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:166:25)
2022-11-15T12:44:00.061196+00:00 app[worker.1]:     at ChromeLauncher.launch (/app/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:70:37)
2022-11-15T12:44:00.061196+00:00 app[worker.1]:     at async /app/date.js:9:13
2022-11-15T12:44:00.061197+00:00 app[worker.1]:     at async CJ.<anonymous> (/app/index.js:41:28)
2022-11-15T12:44:00.061227+00:00 app[worker.1]: New insider trade! (form 4 filed)
2022-11-15T12:44:00.061227+00:00 app[worker.1]: 
2022-11-15T12:44:00.061228+00:00 app[worker.1]: undefined bought undefined shares at $undefined
2022-11-15T12:44:00.061228+00:00 app[worker.1]: 
2022-11-15T12:44:00.061228+00:00 app[worker.1]: Amount Purchased: $NaN
2022-11-15T12:44:00.061229+00:00 app[worker.1]: Stock: undefined
2022-11-15T12:44:00.061229+00:00 app[worker.1]: Date: undefined
2022-11-15T12:44:00.061229+00:00 app[worker.1]: 
2022-11-15T12:44:01.000000+00:00 app[api]: Build started by user jojoamankwa@gmail.com
2022-11-15T12:44:38.942638+00:00 app[api]: Release v8 created by user jojoamankwa@gmail.com
2022-11-15T12:44:38.942638+00:00 app[api]: Deploy 2db65223 by user jojoamankwa@gmail.com
2022-11-15T12:44:40.624181+00:00 heroku[worker.1]: Restarting
2022-11-15T12:44:40.626042+00:00 heroku[worker.1]: State changed from up to starting
2022-11-15T12:44:39.000000+00:00 app[api]: Build succeeded
2022-11-15T12:44:41.596325+00:00 heroku[worker.1]: Stopping all processes with SIGTERM
2022-11-15T12:44:41.950594+00:00 heroku[worker.1]: Process exited with status 143
2022-11-15T12:44:44.285628+00:00 heroku[worker.1]: Starting process with command `node index.js`
2022-11-15T12:44:45.072715+00:00 heroku[worker.1]: State changed from starting to up
2022-11-15T12:44:53.176410+00:00 heroku[worker.1]: Restarting
2022-11-15T12:44:53.191437+00:00 heroku[worker.1]: State changed from up to starting
2022-11-15T12:44:54.322495+00:00 heroku[worker.1]: Stopping all processes with SIGTERM
2022-11-15T12:44:54.589561+00:00 heroku[worker.1]: Process exited with status 143
2022-11-15T12:44:55.711588+00:00 heroku[worker.1]: Starting process with command `node index.js`
2022-11-15T12:44:56.492554+00:00 heroku[worker.1]: State changed from starting to up
heroku

2条答案

按热度按时间
h9vpoimq

h9vpoimq1#

鉴于Chris对SEC条款和服务的认真阅读，我建议使用不同的API。Alphavantage看起来是一个很好的、简单的、免费的API，可以满足您的需求：
https://www.alphavantage.co/
干杯！干杯！

赞(0）分享  回复(0）举报  2022-11-24
5m1hhzi4

5m1hhzi42#

正如日志中明确指出的那样-这不是twitter bot的问题，而是puppeteer over Heroku的问题
为什么？因为puppeteer是一个复杂的模块，在安装过程中需要定制构建。您的托管机器比您的本地机器受到的限制（在权限方面）要多得多--这就是为什么您不能真正从您自己的机器上找出问题所在
幸运的是，Heroku和puppeteer都是常用的解决方案，这就是为什么有一个名为puppeteer-heroku-buildpack的构建包可以做到这一点。
我建议您遵循these steps并给予一下

编辑：

从您的日志中也可以看出chrome没有正确配置。请注意，使用Heroku需要一些配置（它不是chrome headless buildpack），可以在here中找到
确保执行所有这些先决条件，然后才安装puppeteer

赞(0）分享  回复(0）举报  2022-11-24
我来回答

相关问题

    查看更多

    热门标签

    更多
    JavaquerypythonNode开发语言requestUtil数据库Table后端算法LoggerMessageElementParser

    最新问答

    更多
    • 蜀ICP备2022004421号-2 NULL123 https://www.null123.com © All rights reserved
    • 本站内容来源互联网,如果侵犯您的权益请联系我们删除, 联系方式：448109455@qq.com