Yakyak: Continuous Connecting

[wastefulox]

I'm getting the connecting screen but can go no further. Here are the error logs when I run it from the console:

➜  yakyak ./yakyak 
hconnect
reconnecting 0
resolving proxy http://plus.google.com
resolving proxy https://plus.google.com
resolved proxy DIRECT
resolved proxy DIRECT
connect_failed TypeError: Cannot read property 'length' of undefined
    at /opt/yakyak/resources/app/node_modules/hangupsjs/lib/init.js:125:21
    at _fulfilled (/opt/yakyak/resources/app/node_modules/q/q.js:854:54)
    at /opt/yakyak/resources/app/node_modules/q/q.js:883:30
    at Promise.promise.promiseDispatch (/opt/yakyak/resources/app/node_modules/q/q.js:816:13)
    at /opt/yakyak/resources/app/node_modules/q/q.js:570:49
    at runSingle (/opt/yakyak/resources/app/node_modules/q/q.js:137:13)
    at flush (/opt/yakyak/resources/app/node_modules/q/q.js:125:13)
    at process._tickCallback (internal/process/next_tick.js:61:11)
error connecting TypeError: Cannot read property 'length' of undefined
    at /opt/yakyak/resources/app/node_modules/hangupsjs/lib/init.js:125:21
    at _fulfilled (/opt/yakyak/resources/app/node_modules/q/q.js:854:54)
    at /opt/yakyak/resources/app/node_modules/q/q.js:883:30
    at Promise.promise.promiseDispatch (/opt/yakyak/resources/app/node_modules/q/q.js:816:13)
    at /opt/yakyak/resources/app/node_modules/q/q.js:570:49
    at runSingle (/opt/yakyak/resources/app/node_modules/q/q.js:137:13)
    at flush (/opt/yakyak/resources/app/node_modules/q/q.js:125:13)
    at process._tickCallback (internal/process/next_tick.js:61:11)

I am running this on Ubuntu 18.04. I see this happened before on 1.4.0_beta3 and I tried your fix (deleting the node files and rebuilding them via NPM) but I get an error on running the npm run gulp command.

➜  app sudo npm run gulp

> [email protected] gulp /opt/yakyak/resources/app
> gulp

[07:26:16] No gulpfile found
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] gulp: `gulp`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] gulp script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/mat/.npm/_logs/2018-10-25T11_26_16_115Z-debug.log`

[fxalgrain]

I was looking to open the same ticket ^^
I have the same issue on macOS Mojave

[ZargEzey]

I used the patches posted here by HomerSP:

https://github.com/yakyak/hangupsjs/pull/104

Until new release is released it brings back all functionality.

[plessbd]

For anyone else trying to use the patches from yakyak/hangupsjs#104

if you go into the app directory and wherever hangupsjs is you need to run the following commands

for mac (adjust for whatever system you are on) AFTER YOU EDIT THE FILES / APPLY THE PATCH

cd /Applications/YakYak.app/Contents/Resources/app/node_modules/hangupsjs
rm -rf lib/*
npm i

this will rebuild the lib files from the coffee files.

[fulltrucker]

@plessbd thanks for this... it was the 'missing' part of all this for me. I manually edited the hangups coffee files, deleted everything in the lib directory, then ran npm i in the Terminal in that directory. Restarted YakYak and A.) it connects and B.) all my conversations are there. Thanks!

[britcey]

Maybe I'm the only one who didn't know, but you can generate a patch file from the PR:

https://github.com/yakyak/hangupsjs/pull/104.patch (which redirects to)

https://patch-diff.githubusercontent.com/raw/yakyak/hangupsjs/pull/104.patch

then, in /Applications/YakYak.app/Contents/Resources/app/node_modules/hangupsjs (or wherever):

patch -p1 < 104.patch
(or whatever you named the patch file)

Then rebuild the lib files, as above.

[wowthatisrandom]

@britcey appreciate the tip on the patch. working for me as well

[fxalgrain]

Thanks a lot, @britcey & @plessbd
It's working well from me now

And by the way, thanks a lot to all YakYak contributors

[jimmynash]

Small note, if you aren't on the latest release these steps might not work. I had to update to the 1.5.2 before the patch and rebuild steps worked.

[x-tk]

Any ideas on the issue with below when patching? I made sure I was at 1.5.2.

patching file src/client.coffee
Hunk #1 FAILED at 88.
Hunk #2 succeeded at 509 with fuzz 2 (offset 28 lines).
1 out of 2 hunks FAILED -- saving rejects to file src/client.coffee.rej
patching file src/init.coffee
Hunk #1 FAILED at 72.
1 out of 1 hunk FAILED -- saving rejects to file src/init.coffee.rej
can't find file to patch at input line 80
Perhaps you used the wrong -p or --strip option?

The text leading up to this was:

|
|From 00fe738a36bf2244ba9b7b87dc1270d404ada438 Mon Sep 17 00:00:00 2001
|From: Mathias Tillman <master.[email protected]>
|Date: Thu, 25 Oct 2018 01:57:04 +0200
|Subject: [PATCH 2/3] Fix tests to reflect the new ids.
|
|---
| test/body.html | 5 ++---
| test/test-initparsebody.coffee | 1 -
| 2 files changed, 2 insertions(+), 4 deletions(-)
|
|diff --git a/test/body.html b/test/body.html
|index 8107881..db988f7 100644
|--- a/test/body.html

|+++ b/test/body.html

File to patch:

[zanthorn]

Any ideas on the issue with below when patching? I made sure I was at 1.5.2.

patching file src/client.coffee

Hunk #1 FAILED at 88.
Hunk #2 succeeded at 509 with fuzz 2 (offset 28 lines).
1 out of 2 hunks FAILED -- saving rejects to file src/client.coffee.rej
patching file src/init.coffee
Hunk #1 FAILED at 72.
1 out of 1 hunk FAILED -- saving rejects to file src/init.coffee.rej
can't find file to patch at input line 80
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:

|

|From 00fe738a36bf2244ba9b7b87dc1270d404ada438 Mon Sep 17 00:00:00 2001
|From: Mathias Tillman <[email protected]>
|Date: Thu, 25 Oct 2018 01:57:04 +0200
|Subject: [PATCH 2/3] Fix tests to reflect the new ids.
|
|---
| test/body.html | 5 ++---
| test/test-initparsebody.coffee | 1 -
| 2 files changed, 2 insertions(+), 4 deletions(-)
|
|diff --git a/test/body.html b/test/body.html
|index 8107881..db988f7 100644
|--- a/test/body.html
|+++ b/test/body.html
File to patch:

Make sure you are using the pre-release version 1.5.2, I had the same thing until I upgraded.

[Neuroxiide]

Can someone dumb this down for me lol. I dont know how to edit code and all that jazz but I use this program for work Mon-Fri 8:00am to 5:00pm. so right now im hurting without it. i dont even mind letting someone teamview me or something i just need help :(

[Setitie]

Yes I'm the same as Neuroxiide, use it on a windows machine at work as GH sucks by itself.

[Bukimari]

Many many thanks @plessbd and @britcey this is what I needed! Everything is working like it should.
@Neuroxiide @Setitie that depends on your system. You want to download the patch file that @britcey linked and run the commands they've provided in their comments:

cd /Applications/YakYak.app/Contents/Resources/app/node_modules/hangupsjs
(or wherever your YakYak file location is)
Download patch file from https://github.com/yakyak/hangupsjs/pull/104.patch
patch -p1 < 104.patch
rm -rf lib/*
npm i

If you don't have much experience with a terminal it might be easiest to wait until they update the main branch with the patch. (Also Windows may require specific tools, not sure on that side)

[peppermintesse]

Sorry to sound like a noob, but... I was able to follow along until I got to:

npm i

I get

-bash: npm: command not found

Is npm something I need to download and install separately?

[ztoben]

@peppermintesse, yes you will need node installed.

[peppermintesse]

Muchas gracias! :)

Edit: Got node installed, completed the patch process, connecting worked like a charm. Thanks for your guidance.

[Setitie]

I saved a copy of 104.patch to the hangupsjs lib folder but not sure which file I update with: patch -p1 < 104.patch

[ztoben]

@Setitie, not in the lib folder. In the root hangupsjs folder.

[Setitie]

I saved it there 2 as well. Which file do I update with patch -p1 < 104.patch?

[fulltrucker]

@Setitie running the patch command in the terminal, while in the correct directory, will update the correct files. The 'which file to update' information is contained in the patch file itself, if I am not mistaken.

[Setitie]

Is that something that can me done in windows 7?

[fulltrucker]

Is that something that can me done in windows 7?

Sorry, I'm only familiar with Mac systems and (to a lesser degree) Unix systems. These systems have a built-in command line application (commonly referred to as Terminal) where you can navigate your file directory structure and run commands, applications, etc. While I'm sure it exists for Windows, I'm not expert. Additionally, if you don't have experience with command line on your machine, it's probably not likely that you'll have the software required to 'compile' the application once it's been patched. This would be the npm i part of the instructions, @ztoben referred to that as node.

TL;DR -- it sounds like you may need to wait for a new release to get these changes.

[plessbd]

@Setitie @Neuroxiide I dont think you will be able to easily use patch, but I would assume you can install node (which comes with npm) from https://nodejs.org/en/download/

you will have to manually edit the files but should them be able to run npm

I will see if I can figure out how to do this on windows...

[Setitie]

Thank you plessbd and everyone else who is helping us noobs with this. I for one appreciate the help.

[ztoben]

I uploaded the fixed files to gists here:

• client.js
• init.js

Just place them both in the lib folder and override the existing files.

[robertdwilson]

THIS WORKED!
THANK YOU THANK YOU THANK YOU!!!

[Setitie]

Thank you for your help. Much appreciated.

[Neuroxiide]

That worked. The Noobs Thank You!!! greatly appreciated.

[cron410]

Fix by @ztoben didn't work for Yakyak on Win10 x64

[Window Title]
Error

[Main Instruction]
A JavaScript error occurred in the main process

[Content]
Uncaught Exception:
Error: Cannot find module 'tough-cookie-file-store'
    at Module._resolveFilename (module.js:485:15)
    at Function.Module._resolveFilename (C:\yakyak-1.5.1-win32-x64\yakyak-win32-x64\resources\electron.asar\common\reset-search-paths.js:35:12)
    at Function.Module._load (module.js:437:25)
    at Module.require (module.js:513:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (C:\yakyak-1.5.1-win32-x64\yakyak-win32-x64\resources\app\node_modules\hangupsjs\lib\client.js:10:21)
    at Object.<anonymous> (C:\yakyak-1.5.1-win32-x64\yakyak-win32-x64\resources\app\node_modules\hangupsjs\lib\client.js:541:4)
    at Object.<anonymous> (C:\yakyak-1.5.1-win32-x64\yakyak-win32-x64\resources\app\node_modules\hangupsjs\lib\client.js:543:3)
    at Module._compile (module.js:569:30)
    at Object.Module._extensions..js (module.js:580:10)

[OK]

[ztoben]

@cron410: yeah, I only have access to a mac right now so I couldn't test on windows. If you do the build steps yourself does it work?

[brianjcohen]

I got the same output as @cron410 on Linux (replacing the files only -- no build steps).

[cron410]

@ztoben sorry I don't have access to install stuff on this work computer. I can run portable apps like Yakyak somehow.

[antimuffin]

Has anyone found a workaround for this on Windows 10?

[nabrahamson]

For anyone else trying to use the patches from yakyak/hangupsjs#104

if you go into the app directory and wherever hangupsjs is you need to run the following commands

for mac (adjust for whatever system you are on) AFTER YOU EDIT THE FILES / APPLY THE PATCH

cd /Applications/YakYak.app/Contents/Resources/app/node_modules/hangupsjs
rm -rf lib/*
npm i

this will rebuild the lib files from the coffee files.

In case it doesn't rebuild the lib files, run
npm run prepublish
In that directory.

[psouza4]

Fix by @ztoben didn't work for Yakyak on Win10 x64

[Window Title]
Error

[Main Instruction]
A JavaScript error occurred in the main process

[Content]
Uncaught Exception:
Error: Cannot find module 'tough-cookie-file-store'
    at Module._resolveFilename (module.js:485:15)
    at Function.Module._resolveFilename (C:\yakyak-1.5.1-win32-x64\yakyak-win32-x64\resources\electron.asar\common\reset-search-paths.js:35:12)
    at Function.Module._load (module.js:437:25)
    at Module.require (module.js:513:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (C:\yakyak-1.5.1-win32-x64\yakyak-win32-x64\resources\app\node_modules\hangupsjs\lib\client.js:10:21)
    at Object.<anonymous> (C:\yakyak-1.5.1-win32-x64\yakyak-win32-x64\resources\app\node_modules\hangupsjs\lib\client.js:541:4)
    at Object.<anonymous> (C:\yakyak-1.5.1-win32-x64\yakyak-win32-x64\resources\app\node_modules\hangupsjs\lib\client.js:543:3)
    at Module._compile (module.js:569:30)
    at Object.Module._extensions..js (module.js:580:10)

[OK]

Worked for me on Win10 Pro x64. thanks @ztoben ! The users in the pull request thread were rude and condescending, glad someone's providing meaningful content. Thumbs up

[Gedrean]

Fix by @ztoben didn't work for Yakyak on Win10 x64

That's odd, looking at your output it seems maybe a corrupt version?

I just applied the patches by @ztoben and they worked for me. Win10 x64 Pro

(( EDIT: Here is a link to the page I reference below, from @ztoben's post: https://gist.github.com/ztoben/41bd68f893f46fc055f52bbacbee30d2 ))

Here's my steps:
I started by copying my YakYak folder to another location along with any shortcuts to that version of it, and renaming the exe and directory so that it broke any new shortcut searches.
I then extracted a brand-new YakYak 1.5.2 x64 zip, renamed the folder to YakYak, and located it in my custom C:\Apps directory (for manually installed apps).
I downloaded the ZIP file created on @ztoben's linked page (up at the top, download zip).
I extracted that, opened the folder, and moved out client.js and init.js, and put them in to (your base directory may change somewhat):

C:\Apps\YakYak\resources\appnode_modules\hangupsjslib

And I replaced the existing files.

I opened a brand new YakYak instance after making sure all previous instances were gone in task manager.

YakYak took a few extra seconds to launch and paint the window (I presume due to a new requirement to sync instead of auto-grabbing conversations through the conv_status), and then displayed all of my conversations and all chat history.

--
Hope this helps someone.

[Gedrean]

Worked for me on Win10 Pro x64. thanks @ztoben ! The users in the pull request thread were rude and condescending, glad someone's providing meaningful content. Thumbs up

Pull requests, by nature, aren't for technical support, they're for devs and subdevs to submit code and test that it works and compile from. If you don't know how to use a pull request, you're expected to post an issue and maybe in there request that someone provide compiled files...

Admittedly devs can be pretty rude about stuff and it's sad that that's the case, but to them it's just that someone was in there cluttering up their tool by asking for support, and that can be very frustrating and irritating.

[blackroseMD1]

Hope this helps someone.

This worked perfectly for me. Thank you!

[Bukimari]

I got the same output as @cron410 on Linux (replacing the files only -- no build steps).

@brianjcohen I'm on Arch and the commands in my previous comment worked perfectly, do you get any errors when running those? Make sure to change the file directory in the commands to where yours is installed (ie. mine's under ~/.config/yakyak-client/resources/apps/node_modules/hangupsjs)

[cron410]

I was able to resolve the issue on my Win 8.1 x32 home computer like everyone else by saving the client.js and init.js files over the current release files. I'll have to download again when I get to work tomorrow. Thanks for the help!

[juanfcocontreras]

Fix by @ztoben didn't work for Yakyak on Win10 x64

[Window Title]
Error

[Main Instruction]
A JavaScript error occurred in the main process

[Content]
Uncaught Exception:
Error: Cannot find module 'tough-cookie-file-store'
    at Module._resolveFilename (module.js:485:15)
    at Function.Module._resolveFilename (C:\yakyak-1.5.1-win32-x64\yakyak-win32-x64\resources\electron.asar\common\reset-search-paths.js:35:12)
    at Function.Module._load (module.js:437:25)
    at Module.require (module.js:513:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (C:\yakyak-1.5.1-win32-x64\yakyak-win32-x64\resources\app\node_modules\hangupsjs\lib\client.js:10:21)
    at Object.<anonymous> (C:\yakyak-1.5.1-win32-x64\yakyak-win32-x64\resources\app\node_modules\hangupsjs\lib\client.js:541:4)
    at Object.<anonymous> (C:\yakyak-1.5.1-win32-x64\yakyak-win32-x64\resources\app\node_modules\hangupsjs\lib\client.js:543:3)
    at Module._compile (module.js:569:30)
    at Object.Module._extensions..js (module.js:580:10)

[OK]

This error happens when you try to patch latest release (files are for pre-release version). You should try to patch pre-release version (1.5.2).

[beruic]

So, since this patch works, why is there no version 1.5.3 with it applied yet?

[ztoben]

@beruic, https://github.com/yakyak/hangupsjs/pull/104 needs to be merged first. Not sure who's in charge of reviewing PRs.

[Neuroxiide]

Just wanted to throw this out There, I have Windows 10 64-bit and patched
worked. (Replacing the Files).

On Fri, Oct 26, 2018 at 8:10 AM Zach Toben [e-mail] wrote:

@beruic https://github.com/beruic, yakyak/hangupsjs#104
https://github.com/yakyak/hangupsjs/pull/104 needs to be merged first.
Not sure who's in charge of reviewing PRs.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yakyak/yakyak/issues/981#issuecomment-433386634, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AqaZbEN_yu1Doek9fl5oStHlgqv_XeKsks5uovuwgaJpZM4X6FFI
.

>

Matt Brunk

Agency: DLW

Office: 850-724-1220

Cell: 850-381-7232

[email protected]

Available 24/7!

After hours and weekends call cell

Colossians 3:23 (ESV)

Whatever you do, work heartily, as for the Lord and not for men

* Please call or email me once you are empty with an ETA to the
shipper. Please call or email me when you arrive & depart from each stop.
Call me ASAP if any delays! Thank you :) *

*ATTN ALL HAZMAT LOADS: Please make sure you are compliant before leaving
any Shipping facility. If Shipper is saying they do not have placards,
please call me immediately so we can get this resolved. If shipper says
they do not have a BOL, Please call me with a fax # or an email for the
shipper and I will get the bills sent over. A Landstar BOL will not suffice
for the receiver. If bills are incorrect, call me right away with the issue
and I will work on getting it resolved. *

*EMPTY TOTES: Make sure units are always double stacked and nozzle to
nozzle. If shipper tries loading a tote with residue in it, please call me
immediately. Only load empty units. *

*DETENTION: Please notify me once you have been at consignee for going on 2
hours. I will then notify the customer to put in a request to begin
detention. MAKE SURE YOU GET IN/OUT TIMES SIGNED ON BILLS. *

NO TOUCH: Most of my freight is no touch. If you are being asked to assist
in load/unload, call me immediately. You will not receive any payment for
assisting unless I have cleared it with the customer before hand. Sit
tight, I will call you back and advise of the situation once I have spoken
to the customer rep.

SKIPPED STOPS: If any stops are missed or skipped, a rate cut for that
stop will be issued.

BILLING: Avoid any issues with billing. Landstar will hold payment if
they cannot read the BOL, please ensure the ink is dark enough for Landstar
to accept it. If there is more than 1 page, please fax in additional pages
to Landstar, they will not accept if it is missing pages (2 of 3), (3 of
3), etc.

*Thank you!! Please never hesitate to call me day or night with concerns. *

*This email (including any attachments) is covered by the Electronic
Communications Privacy Act 18USC2520-2521. It is confidential and may be
legally privileged. If you are not the intended recipient you are hereby
notified that any retention, dissemination, distribution, or copying of
this communication is strictly prohibited. Please reply to the sender if
you have received the message in error and then delete it. *

[KusioST]

Hello

I also have problem with start YakYak. I change client.js and init.js but I get:

[sp823]

How are people getting 1.5.2? The latest pre-built binaries are 1.5.1. I tried the fix and I get an error on start - assuming that is because I'm on 1.5.1 (Windows).

[Bukimari]

How are people getting 1.5.2? The latest pre-built binaries are 1.5.1. I tried the fix and I get an error on start - assuming that is because I'm on 1.5.1 (Windows).

It's a pre-release, here you go.
EDIT: You may give it a few minutes, @averissimo is rebuilding it right now to fix the errors.

[sp823]

Patch works with 1.5.2 - thanks.

[averissimo]

This is fixed in v1.5.2 that was just updated and released -- major thanks to contributors of this pull request: https://github.com/yakyak/hangupsjs/pull/104

Please report back if you guys have problems

[patefoniq]

I uploaded the fixed files to gists here:

* [client.js](https://gist.github.com/ztoben/41bd68f893f46fc055f52bbacbee30d2#file-client-js)

* [init.js](https://gist.github.com/ztoben/41bd68f893f46fc055f52bbacbee30d2#file-init-js)

Just place them both in the lib folder and override the existing files.

With the version 1.5.2 of yak-yak, these files solve the problem. Thank you.

[KusioST]

I forget to write what i use Windows 10 Pro x64. This version: https://github.com/yakyak/yakyak/releases/tag/v1.5.2
works.

Thanks for help.

[beruic]

FYI: Snap is not updated yet.