I've downloaded the Design automation sample from github https://github.com/Autodesk-Forge/learn.forge.designautomation/tree/nodejs
I followed the toturial to make it working locally,
my issue is after deploying the app to heroku and filled the secret data, every thing is working correctly except for the workitems request it fails with code 500 Internal Server Error and response:
{"diagnostic":"Failed to create a workitem"}
error screen shot
the error log file: https://mega.nz/file/b2Y3wTJD#FqyWubUvewk175j_Y75TfpwfkzZHNXhSH1Tt5NY4HPc
You need to update FORGE_WEBHOOK_URL to https://test-f-daa.herokuapp.com on Heroku as well, from the error log -
{"url":["Failed to create URL for 'undefined/api/forge/callback/designautomation?....
I followed a tutorial on how to make a multiplayer tetris game, here is the repo:
https://github.com/Leftier/tetris
It worked just fine on localhost so I tried to deploy it in heroku (https://tetrixtest.herokuapp.com/ --ASD to move Q/E to rotate) but I get the following error:
WebSocket connection to 'wss://tetrixtest.herokuapp.com/' failed: Error during WebSocket handshake: Unexpected response code: 200
while trying to create the webSocket in this line (connection-manager.js line 14):
this.conn = new WebSocket(`wss://${window.location.hostname}:${window.location.port}`)
I don't know much about webSockets,
at first I thought that heroku was not able to handle websockets but that wasn't the case so I tried using the link directly as an argument instead of reading it from the browser but still the same issue.
I would like some clues/hints about why does this happens, I searched in google and github, but I only found issues related to socket.io
For me the solution was to turn on "Session affinity" by running this command heroku features:enable http-session-affinity
More info at https://devcenter.heroku.com/articles/session-affinity
Session affinity, sometimes referred to as sticky sessions, is a
platform feature that associates all HTTP requests coming from an
end-user with a single application instance (web dyno).
I've been searching for a while now and I can't find the exact list of all fail to load error code/error description of google chrome.
I'm talking about this the highlighted text
Can someone give me a link?
I did some digging and I must admit, it's not easy to find a full exhaustive list of all (Chromium) networking error codes.
The full list of all Chromium error codes can be found in the file net_error_list.h:
https://cs.chromium.org/chromium/src/net/base/net_error_list.h
It looks like Google Chrome prepends ERR_ to all the codes listed in the above list.
However, error codes in XHR error responses are slightly different. These codes follow the format of the linux system file errno.h as defined by POSIX.1-2001, or C99:
http://man7.org/linux/man-pages/man3/errno.3.html
Finally, some common NodeJS errors have been listed at the NodeJS API Documentation:
https://nodejs.org/api/errors.html#errors_common_system_errors
I'd like to end this answer with a simple comparison example. The error of an operation timeout would be named as follows by the listed 'standards':
TIMED_OUT internally in Chromium.
ERR_TIMED_OUT displayed in Google Chrome.
ETIMEDOUT in the XHR error object (error.code).
Using your example:
CONNECTION_REFUSED -> internally in Chromium
ERR_CONNECTION_REFUSED -> displayed in Google Chrome
ECONNREFUSED -> in linux (POSIX.1) or network error stacks
By the way for only listing all error codes
USE :
chrome://network-errors/
It's about 220 in total as of now in chrome version (69.0.3497.100)
I have chromium Version 97.0.4692.71 (Official Build), snap (32 bit), on Description: Ubuntu 18.04.6 LTS. The problem was solved using the command in the terminal
chromium --no-sandbox
after that everything worked.
i've got a problem setting up my couchbase server on my new macbook.
I have installed Couchbase 3.0.1 and i am running OS X 10.10
I can login to the webconsole. But there it always tells me my server on 127.0.0.1 is down/pending. I can't get it to run properly.
I already checked the log, but can't get any idea out of it.
One error which appears again and again:
[stats:error,2014-10-31T10:06:11.844,ns_1#127.0.0.1:<0.2019.0>:stats_collector:handle_info:124]Exception in stats collector: {exit,
{{bad_return_value,
{stop,{error,couldnt_connect_to_memcached}}},
{gen_server,call,
['ns_memcached-obd_data',
{stats,<<>>},
180000]}},
[{gen_server,call,3,
[{file,"gen_server.erl"},{line,188}]},
{ns_memcached,do_call,3,
[{file,"src/ns_memcached.erl"},{line,1401}]},
{stats_collector,grab_all_stats,1,
[{file,"src/stats_collector.erl"},{line,84}]},
{stats_collector,handle_info,2,
[{file,"src/stats_collector.erl"},
{line,116}]},
{gen_server,handle_msg,5,
[{file,"gen_server.erl"},{line,604}]},
{proc_lib,init_p_do_apply,3,
[{file,"proc_lib.erl"},{line,239}]}]}
Anyone an idea how to solve my problem and get the server started?
Or is there any common known problem already?
I am trying to create a automated ftp log in script in Expect/TCL.
This is my script
spawn ftp 100.100.100.1
expect ".*:"
send "username"
expect ".*:"
send "password"
expect ".*>"
I get an error in Windows XP saying , it encountered an error and needs to close .
But same thing work on a windows 2000 .
Can anyone guide me .
Have you tried to launch your script with wish instead of tclsh? It might make a different.
Reference: http://wiki.tcl.tk/3548