I am trying to run the reactive-microservices example provided on TypeSafe website.
I am using Ubuntu 14.04. I ran sudo docker-compose up in one terminal window. It was successful.
And then in another terminal window I ran sbt runAll. It gives me the following warning and is stuck on it.
[WARN] [02/14/2016 00:21:25.826] [btc-users-akka.actor.default-dispatcher-3] [akka.tcp://btc-users#127.0.0.1:2551/user/$b] Requesting ticker failed because Received fatal alert: internal_error to https://market.bitbay.pl/API/Public/BTCUSD/ticker.json
What is this and how do I get rid of this issue?
In Data Fecther I changed the URL
from: //private val url = "https://market.bitbay.pl/API/Public/BTCUSD/ticker.json"
to: private val url = "https://bitbay.net/API/Public/BTCUSD/ticker.json"
and now it works...
[info] [DEBUG] [03/23/2016 11:36:45.875] [btc-users-akka.actor.default-dispatcher-3] [akka.tcp://btc-users#127.0.0.1:2551/user/$b] Broadcasting ticker Ticker(430,430,430,387.01,429.99,414.83,430,0.1602558)
[info] [DEBUG] [03/23/2016 11:36:46.917] [btc-users-akka.actor.default-dispatcher-3] [akka.tcp://btc-users#127.0.0.1:2551/user/$b] Broadcasting ticker Ticker(430,430,430,387.01,429.99,414.83,430,0.1602558)
[info] [DEBUG] [03/23/2016 11:36:47.925] [btc-users-akka.actor.default-dispatcher-14] [akka.tcp://btc-users#127.0.0.1:2551/user/$b] Broadcasting ticker Ticker(430,430,430,387.01,429.99,414.83,430,0.1602558)
[info] [DEBUG] [03/23/2016 11:36:48.947] [btc-users-akka.actor.default-dispatcher-3] [akka.tcp://btc-users#127.0.0.1:2551/user/$b] Broadcasting ticker Ticker(430,430,430,387.01,429.99,414.83,430,0.1602558)
Related
So I get error messages like this printed to the console from Socket.io:
[2023-02-09 17:53:43] [info] asio async_resolve error: asio.system:11001 (No such host is known.)
[2023-02-09 17:53:43] [info] Error getting remote endpoint: asio.system:10009 (The file handle supplied is not valid.)
[2023-02-09 17:53:43] [error] handle_connect error: No such host is known.
[2023-02-09 17:53:43] [info] asio async_shutdown error: asio.ssl:336462100 (uninitialized)
I just need to hide them from the console but cannot figure out how to do it. I've tried using off_error, set logs quiet, and try/catch but none worked.
Does anyone know how to solve this?
i have a problem with I was not able to get rid of for the past days.
My goal is to start an automated test, for an app that is already downloaded on the device, from my Mac on my iPhone.
I started with installing:
Node.js
Java JDK & JAVA_HOME variable
Appium & Appium inspector
Xcode & Xcode Command Line Tools
Appium driver (xcuitest & UIAutomation)
In the next step in entered my Desired Capabilities in the Appium inspector:
platformName : ios
appium:platformVersion : 16.1
appium:deviceName: iPhone 11 pro
appium:bundleId :
appium:automationName : XCUITest
appium:udid: <udid from my devic
appium:xCodeOrgId :
appium:xCodeSigningId : iPhone Developer
After entering these information I moved on and opened the WebDriverAgent.xcodeproj and signed in with my free Developer Account (Apple ID) and assigned a Team to WebDriverAgentLib, WebDriverAgentRunner, all Integrationtests and the IntegrationApp. The Firestone worked but the last three failed with the Error:
Failed to create provisioning Profile. The app ID "com.facebook.WebDriverAgentRuner" can not be registered to your development team. Change your bunde identifier to a unique String to try again.
and
No profiles for 'com.facebook.WebDriverAgentRunner' were found. Xcode couldn't find any iOS App Development provisioning profiles matching 'com.facebook.WebDriverAgentRunner'.
After reviewing the Problem I came up with following a few tutorials without any luck.
I tried to create a profiling Profile, but most ways I found were with the free version or just wouldn't work.
So i changed the bundle identifiers, even though it's not a beautiful solution and was able to trust the computer and install an app with Xcode.
But when I try to start a session with Appium inspector after I started the Appium server in Visual Studio Code it still fails with the Error:
In Appium inspector:
Error
Failed to create session. An unknown server-side error occurred while processing the command. Original error: Unable to launch WebDriverAgent because of xcodebuild failure: xcodebuild failed with code 65 xcodebuild error message: . Make sure you follow the tutorial at https://github.com/appium/appium-xcuitest-driver/blob/master/docs/real-device-config.md. Try to remove the WebDriverAgentRunner application from the device if it is installed and reboot the device.
In Visual Studio Code:
[debug] [XCUITestDriver#f4dc (e98a8edb)] Matched '/status' to command name 'getStatus'
[debug] [XCUITestDriver#f4dc (e98a8edb)] Proxying [GET /status] to [GET http://127.0.0.1:8100/status] with no body
[debug] [iProxy#00008030:8100] Connection was refused to port 8100
[XCUITestDriver#f4dc (e98a8edb)] socket hang up
[Xcode] xcodebuild exited with code '65' and signal 'null'
[debug] [XCUITestDriver#f4dc (e98a8edb)] Event 'wdaStartFailed' logged at 1674136358245 (14:52:38 GMT+0100 (Mitteleuropäische Normalzeit))
[debug] [XCUITestDriver#f4dc (e98a8edb)] Unable to launch WebDriverAgent because of xcodebuild failure: xcodebuild failed with code 65
[debug] [XCUITestDriver#f4dc (e98a8edb)] xcodebuild error message:
[debug] [XCUITestDriver#f4dc (e98a8edb)] . Make sure you follow the tutorial at https://github.com/appium/appium-xcuitest-driver/blob/master/docs/real-device-config.md. Try to remove the WebDriverAgentRunner application from the device if it is installed and reboot the device.
[XCUITestDriver#f4dc (e98a8edb)] Quitting and uninstalling WebDriverAgent
[XCUITestDriver#f4dc (e98a8edb)] Shutting down sub-processes
[debug] [WebDriverAgent] Successfully reset '/Users/k.steffens/.appium/node_modules/appium-xcuitest-driver/node_modules/appium-webdriveragent/WebDriverAgent.xcodeproj/project.pbxproj' with bundle id 'com.facebook.WebDriverAgentRunner'
[debug] [XCUITestDriver#f4dc (e98a8edb)] No WDAs on the device.
[XCUITestDriver#f4dc (e98a8edb)] {}
[DevCon Factory] Releasing connections for 00008030-0005298C0C45802E device on any port number
[DevCon Factory] Found cached connections to release: ["00008030-0005298C0C45802E:8100"]
[DevCon Factory] Releasing the listener for '00008030-0005298C0C45802E:8100'
[debug] [iProxy#00008030:8100] Closing the connection
[debug] [DevCon Factory] Cached connections count: 0
[debug] [XCUITestDriver#f4dc (e98a8edb)] Not clearing log files. U`clearSystemFiles` capability to turn on.
[iProxy#00008030:8100] The connection has been closed
[debug] [AppiumDriver#567d] Event 'newSessionStarted' logged at 1674136358629 (14:52:38 GMT+0100 (Mitteleuropäische Normalzeit))
[debug] [AppiumDriver#567d] Encountered internal error running command: Error: Unable to launch WebDriverAgent because of xcodebuild failure: xcodebuild failed with code 65
[debug] [AppiumDriver#567d] xcodebuild error message:
[debug] [AppiumDriver#567d] . Make sure you follow the tutorial at https://github.com/appium/appium-xcuitest-driver/blob/master/docs/real-device-config.md. Try to remove the WebDriverAgentRunner application from the device if it is installed and reboot the device.
[debug] [AppiumDriver#567d] at quitAndUninstall (/Users/k.steffens/.appium/node_modules/appium-xcuitest-driver/lib/driver.js:584:15)
[debug] [AppiumDriver#567d] at /Users/k.steffens/.appium/node_modules/appium-xcuitest-driver/lib/driver.js:619:11
[debug] [AppiumDriver#567d] at wrapped (/Users/k.steffens/.appium/node_modules/appium-xcuitest-driver/node_modules/asyncbox/lib/asyncbox.js:95:13)
[debug] [AppiumDriver#567d] at retry (/Users/k.steffens/.appium/node_modules/appium-xcuitest-driver/node_modules/asyncbox/lib/asyncbox.js:68:13)
[debug] [AppiumDriver#567d] at retryInterval (/Users/k.steffens/.appium/node_modules/appium-xcuitest-driver/node_modules/asyncbox/lib/asyncbox.js:105:10)
[debug] [AppiumDriver#567d] at /Users/k.steffens/.appium/node_modules/appium-xcuitest-driver/lib/driver.js:599:7
[HTTP] <-- POST /session 500 14443 ms - 1398
[HTTP]
After this try I even tried to add the bootstrapPath as a desired Capability and the agentPath as a desired Capability, with no luck.
But the error changed a little:
Failed to create session. An unknown server-side error occurred while processing the command. Original error: Unable to launch WebDriverAgent because of xcodebuild failure: xcodebuild failed with code 66 xcodebuild error message: . Make sure you follow the tutorial at https://github.com/appium/appium-xcuitest-driver/blob/master/docs/real-device-config.md. Try to remove the WebDriverAgentRunner application from the device if it is installed and reboot the device.
Is there something I'm doing wrong, or is there better way to do automated testing on real iOS devices?
I would be very happy if you could help me out.
kind regards,
henry
When using Xdebug directly from VSCode using one of two PHP extension (xdebug.php-debug, devsense.phptools-vscode) for debugging everything works as expected. But I have a shared environment where an Apache/PHP/Xdebug setup/instance is to be used by multiple developers.
With both extension everything works well when being used directly receiving the Xdebug connection. I have a breakpoint at the last line of code and although the whole HTML content was completely sent by PHP the browser it is still waiting to do anything - although ob_end_flush() (output buffering) was already called. Stepping over the last line of code the HTML content arrives at the browser. The Xdebug log is finishing in the same way.
[Step Debug] -> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" command="run" transaction_id="14" status="stopping" reason="ok"></response>
...
[Step Debug] -> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="https://xdebug.org/dbgp/xdebug" command="stop" transaction_id="22" status="stopped" reason="ok"></response>
When I now set this up using DBGp proxy the two PHP extension behave different. One is blocking the HTML output forever for all request been started and if I kill the apache processes I get a proxy log
21:01:28.652 [warn] [server] Handler response error: Error reading response: Error reading length: EOF
21:01:28.652 [info] [server] Closing server connection from 127.0.0.1:60104
21:01:28.653 [warn] [server] Handler response error: Error reading response: Error reading length: EOF
21:01:28.653 [info] [server] Closing server connection from 127.0.0.1:35422
21:01:28.653 [warn] [server] Handler response error: Error reading response: Error reading length: EOF
21:01:28.653 [info] [server] Closing server connection from 127.0.0.1:43594
21:01:28.653 [warn] [server] Handler response error: Error reading response: Error reading length: EOF
21:01:28.653 [info] [server] Closing server connection from 127.0.0.1:56398
21:01:28.659 [warn] [server] Handler response error: Error reading response: Error reading length: EOF
21:01:28.659 [info] [server] Closing server connection from 127.0.0.1:40030
while the other is delivering the HTML output and says in the proxy log the same moment
22:02:02.316 [warn] [server] Handler response error: Error reading response: Error reading length: EOF
22:02:02.317 [info] [server] Closing server connection from 127.0.0.1:33160
In both cases the Xdebug log says the same: status stopped, reason ok.
So I wonder whether the way the request seems to completely end in both cases reading an EOF and closing the server connection is really a warning because it's unexpected or whether this is the normal behaviour. And then of course it's an issue of the one PHP extension seeming not to tell the proxy and server they can end their connection (I assume this is the client's job which here is the proxy).
I checked all configuration options from Xdebug, the VSCode PHP extension and DBGp proxy to increase logging but I could not find out more than what I have described above. I tried setting the connection either via the VSCode extension or manually issuing echo -e "proxyinit -p 39001 -k jni-vscode -m 1\0" | nc 127.0.0.1 9001 with no success. The EOF warning stays and for the devsense.phptools-vscode plugin there is no php output to the browser. If anyone has a clue why I would appreciate a hint.
Thanks,
Jürgen
PS: Killing dbgpProxy makes apache deliver all the content with access_log entry showing it took 3064 seconds to fulfill the request.
I'm trying to start JMeter from Yandex.Tank in Yandex Cloud instance, based on Ubuntu 18.
Installed JMeter here: /home/tank/apache-jmeter-5.2.1/bin/jmeter
If I run JMeter using this path it starts successfully:
/home/tank/apache-jmeter-5.2.1/bin/jmeter -n -t ReloadTest.jmx -l result-1.jtl -e -o ./result-1
When I run yandex-tank, there is an error message:
[ERROR] Test interrupted:
<type 'exceptions.RuntimeError'>: Unable to access to JMeter executable file or it does not exist:
/home/tank/apache-jmeter-5.2.1/bin/jmeter
load.yaml:
phantom:
enabled: false
jmeter:
enabled: true
jmx: ReloadTest.jmx
buffered_seconds: 10
jmeter_path: /home/tank/apache-jmeter-5.2.1/bin/jmeter
jmeter_ver: 5.2
ext_log: all
overload:
enabled: true
package: yandextank.plugins.DataUploader
token_file: "token.txt"
Tried this, without success:
chmod +x /home/tank/apache-jmeter-5.2.1/bin/jmeter
chmod 777 /home/tank/apache-jmeter-5.2.1/bin/jmeter
I cannot reproduce your issue using latest YandexTank 1.12.8.1, you might want to update your current installation using pip like:
pip install https://api.github.com/repos/yandex/yandex-tank/tarball/master
If will still be experiencing problems - run YandexTank with -v command-line argument, it should produce more verbose debug messages so you will be able to figure out where the problem lives
2020-03-16 09:45:38,960 [DEBUG] yandextank.core.tankcore tankcore.py:267 Starting <yandextank.plugins.JMeter.plugin.Plugin object at 0x7fe01d57a090>
2020-03-16 09:45:38,968 [INFO] yandextank.plugins.JMeter.plugin plugin.py:119 Starting /home/tank/apache-jmeter-5.2.1/bin/jmeter with arguments: ['/home/tank/apache-jmeter-5.2.1/bin/jmeter', '-n', '-t', '/modified_s7ZsHU.jmx', '-j', '/logs/2020-03-16_09-45-22.748390/jmeter_0vPrFi.log', '-Jjmeter.save.saveservice.default_delimiter=\\t', '-Jjmeter.save.saveservice.connect_time=true']
2020-03-16 09:45:50,632 [WARNING] yandextank.plugins.JMeter.plugin plugin.py:188 JMeter UDP port wasn't discovered
2020-03-16 09:45:50,635 [INFO] yandextank.core.tankcore tankcore.py:271 Plugin <yandextank.plugins.JMeter.plugin.Plugin object at 0x7fe01d57a090> required 11.666250 seconds to start
2020-03-16 09:45:50,637 [DEBUG] yandextank.core.tankcore tankcore.py:267 Starting <yandextank.plugins.RCAssert.plugin.Plugin object at 0x7fe01d5059d0>
2020-03-16 09:45:50,640 [INFO] yandextank.core.tankcore tankcore.py:271 Plugin <yandextank.plugins.RCAssert.plugin.Plugin object at 0x7fe01d5059d0> required 0.000021 seconds to start
2020-03-16 09:45:50,647 [DEBUG] yandextank.core.tankcore tankcore.py:267 Starting <yandextank.plugins.Telegraf.plugin.Plugin object at 0x7fe01d505110>
2020-03-16 09:45:50,650 [DEBUG] yandextank.plugins.Telegraf.plugin plugin.py:62 load_start_time = 1584351950.65
2020-03-16 09:45:50,655 [INFO] yandextank.core.tankcore tankcore.py:271 Plugin <yandextank.plugins.Telegraf.plugin.Plugin object at 0x7fe01d505110> required 0.005424 seconds to start
2020-03-16 09:45:50,659 [DEBUG] yandextank.core.tankcore tankcore.py:267 Starting <yandextank.plugins.ResourceCheck.plugin.Plugin object at 0x7fe01d505c50>
2020-03-16 09:45:50,664 [INFO] yandextank.core.tankcore tankcore.py:271 Plugin <yandextank.plugins.ResourceCheck.plugin.Plugin object at 0x7fe01d505c50> required 0.000014 seconds to start
2020-03-16 09:45:50,666 [INFO] yandextank.core.tankcore tankcore.py:279 Waiting for test to finish...
You can also try to change the ownership of the whole JMeter folder to the tank user like:
chown -R tank /home/tank/apache-jmeter-5.2.1
And finally, you can consider switching to Taurus tool which better supports JMeter and is capable of automatically downloading JMeter with plugins so you won't have to worry about installing JMeter. Check out Navigating your First Steps Using Taurus article for more details.
I have downloaded spark-1.4.1.tgz, unzipped it.
Now, when i try to build as follows, it gets stuck:
$ ./sbt/sbt assembly
Invoking 'build/sbt assembly' now
[info] Loading project definition...
[warn] Multiple resolvers having different access mechanism configured with same name 'sbt-plugin-releases'.
...
[info] Resolving org.eclipse.jetty#jetty-parent;18
[error] Server access Error: Connection reset url=http://download.eclipse.org/jgit/maven/org/eclipse/jetty/jetty-parent/18/jetty-parent-18.jar
[error] Server access Error: Server redirected too many times (20) url=http://scalasbt.artifactoryonline.com/scalasbt/sbt-plugin-releases/org.eclipse.jetty.orbit/jetty-orbit/1/jars/jetty-orbit.jar
The build gets stuck at this point. Am i missing any configuration/libraries?
You have a network connectivity issue and probably need to retry.