I have installed Rocket.chat (server and client ) on my Mac for development. Everything appears correctly installed I20170624-15:51:27.314(1)? ➔ System ➔ startup
I20170624-15:51:27.315(1)? ➔ +-----------------------------------------------+
I20170624-15:51:27.316(1)? ➔ | SERVER RUNNING |
I20170624-15:51:27.317(1)? ➔ +-----------------------------------------------+
I20170624-15:51:27.318(1)? ➔ | |
I20170624-15:51:27.319(1)? ➔ | Rocket.Chat Version: 0.57.0-develop |
I20170624-15:51:27.320(1)? ➔ | NodeJS Version: 4.8.3 - x64 |
I20170624-15:51:27.320(1)? ➔ | Platform: darwin |
I20170624-15:51:27.321(1)? ➔ | Process Port: 27271 |
I20170624-15:51:27.321(1)? ➔ | Site URL: http://localhost:3000/ |
I20170624-15:51:27.322(1)? ➔ | ReplicaSet OpLog: Enabled |
I20170624-15:51:27.322(1)? ➔ | Commit Hash: b34e081123 |
I20170624-15:51:27.323(1)? ➔ | Commit Branch: develop |
I20170624-15:51:27.323(1)? ➔ | |
I20170624-15:51:27.324(1)? ➔ +-----------------------------------------------+
However connecting to localhost:3000 either through the browser or through the client, the screen is blank and the progress dots keeps whirling forever. There is also no log from the server. I am not getting to see the login screen. I can use curl however.
I'm not sure about this problem since there is not much info on the question (checking your browser for errors would be a good idea), but there are things you can try:
Updating to the latest develop version;
Doing a meteor npm install before running meteor;
Doing a reset on your local database using the meteor reset command;
Related
ITNOA
I have visual studio 2022 and install some android sdk like below
PS C:\Program Files (x86)\Android\android-sdk\cmdline-tools\7.0\bin> .\sdkmanager.bat --list_installed
Installed packages:=====================] 100% Fetch remote repository...
Path | Version | Description | Location
------- | ------- | ------- | -------
build-tools;32.0.0 | 32.0.0 | Android SDK Build-Tools 32 | build-tools\32.0.0
build-tools;33.0.0 | 33.0.0 | Android SDK Build-Tools 33 | build-tools\33.0.0
emulator | 31.3.14 | Android Emulator | emulator
extras;android;m2repository | 47.0.0 | Android Support Repository | extras\android\m2repository
extras;intel;Hardware_Accelerated_Execution_Manager | 7.6.5 | Intel x86 Emulator Accelerator (HAXM installer) | extras\intel\Hardware_Accelerated_Execution_Manager
ndk-bundle | 20.1.5948944 | NDK | ndk-bundle
patcher;v4 | 1 | SDK Patch Applier v4 | patcher\v4
platform-tools | 33.0.2 | Android SDK Platform-Tools 33.0.2 | platform-tools
platforms;android-28 | 6 | Android SDK Platform 28, rev 6 | platforms\android-28
platforms;android-29 | 5 | Android SDK Platform 29, rev 5 | platforms\android-29
platforms;android-31 | 1 | Android SDK Platform 31 | platforms\android-31
platforms;android-33 | 1 | Android SDK Platform 33 | platforms\android-33
system-images;android-28;default;x86_64 | 4 | Intel x86 Atom_64 System Image | system-images\android-28\default\x86_64
system-images;android-29;default;x86_64 | 8 | Intel x86 Atom_64 System Image | system-images\android-29\default\x86_64
system-images;android-31;default;arm64-v8a | 3 | ARM 64 v8a System Image | system-images\android-31\default\arm64-v8a
system-images;android-31;default;x86_64 | 3 | Intel x86 Atom_64 System Image | system-images\android-31\default\x86_64
system-images;android-31;google_apis_playstore;x86_64 | 9 | Google Play Intel x86 Atom_64 System Image | system-images\android-31\google_apis_playstore\x86_64
system-images;android-33;google_apis;x86_64 | 5 | Google APIs Intel x86 Atom_64 System Image | system-images\android-33\google_apis\x86_64
and my Android Device Manager like below
but my problem is As you can see in qemu-system-x86_64.exe is not responding , when I try to start one of android device, my qemu-system is not responding, and I do not know how to resolve this problem
Note:
As you can see in https://stackoverflow.com/a/69789845/1539100, the michael #michael says, for resolving this issue, I must disable HyperV, but I need HyperV, and I can not disable it, so I can not try #michael solution, please provide a solution that works alongside of HyperV
Sometimes Android Device Manager, get below errors
Device error: WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
WARNING | unexpected '-prop' value ('monodroid.avdname=pixel_5_-_api_31'), only 'qemu.' properties are supported
WARNING | unexpected '-prop' value ('emu.uuid=5cd6ab71-b279-40b1-b2d0-f506a0f87649'), only 'qemu.' properties are supported
dsound: Could not initialize DirectSoundCapture
dsound: Reason: No sound driver is available for use, or the given GUID is not a valid DirectSound device ID
WARNING | ** No gRPC protection active, consider launching with the -grpc-use-jwt flag.**
I run "C:\Program Files (x86)\Android\android-sdk\emulator\emulator-check.exe" accel and below log is printed
accel:
0
Please disable Hyper-V before using the Android Emulator. Start a command prompt as Administrator, run 'bcdedit /set hypervisorlaunchtype off', reboot.WHPX (10.0.22621) is installed and usable.
accel
and my systeminfo is like below
C:\Users\sooro>systeminfo
Host Name: SSOROOSH-PC
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.22621 N/A Build 22621
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
Registered Organization:
Product ID: 00331-10000-00001-AA598
Original Install Date: 11/10/2022, 12:10:44 AM
System Boot Time: 12/22/2022, 11:01:09 AM
System Manufacturer: ASUS
System Model: System Product Name
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 151 Stepping 2 GenuineIntel ~3400 Mhz
BIOS Version: American Megatrends Inc. 1720, 8/12/2022
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume13
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
I need HyperV on my system. How to resolve this issue?
thanks
As you can see in https://developercommunity.visualstudio.com/t/qemu-system-not-responding/10233039#T-N10258374 , Microsoft says this is a Bug and fixed internally, and pending release
So I'm just trying to get a project set up using JDK 15 / SBT 1.5.4 / Scala 2.13.6 all of which have been installed via brew on MacOS.
However before I even attempt to build via intellij etc. I'm unable to connect to the sbt shell via a normal terminal.
[info] welcome to sbt 1.5.4 (AdoptOpenJDK Java 15.0.2)
[info] loading global plugins from /Users/user/.sbt/1.0/plugins
[warn] Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore? (default: r)
Exception in thread "Thread-0" java.lang.NoClassDefFoundError: Could not initialize class com.swoval.runtime.ShutdownHooks
at com.swoval.runtime.ShutdownHooks$1.run(ShutdownHooks.java:25)
I've tried reinstalling all three dependancies a few times and cleared the cache but still nothing. I'm guessing something isn't configured right because it's unable to even connect to the shell.
Thanks!
EDIT: I've just followed the install steps on the sbt docs and the only requirements are JDK 11 or 8 and sbt itself. I've removed scala / JDK15 and re-downloaded JDK 11 via SDK-man this time and i'm still having the same issue.
EDIT 2: I've removed the .sbt directory and reinitiased and now sbt command is showing more output, hopefully this helps a little more.
java.lang.NoClassDefFoundError: Could not initialize class com.swoval.runtime.ShutdownHooks
at com.swoval.runtime.NativeLoader.loadPackaged(NativeLoader.java:143)
at com.swoval.runtime.NativeLoader.loadPackaged(NativeLoader.java:174)
at com.swoval.files.apple.FileEventMonitorImpl.<clinit>(FileEventMonitors.java:127)
at com.swoval.files.apple.FileEventMonitors.get(FileEventMonitors.java:47)
at com.swoval.files.ApplePathWatcher.<init>(ApplePathWatcher.java:258)
at com.swoval.files.ApplePathWatcher.<init>(ApplePathWatcher.java:194)
at com.swoval.files.ApplePathWatchers.get(ApplePathWatcher.java:331)
at com.swoval.files.PathWatchers.get(PathWatchers.java:84)
at com.swoval.files.FileTreeRepositories.get(FileTreeRepositories.java:64)
at com.swoval.files.FileTreeRepositories.get(FileTreeRepositories.java:32)
at sbt.internal.nio.FileTreeRepositoryImpl.<init>(FileTreeRepositoryImpl.scala:46)
at sbt.internal.nio.FileTreeRepository$.default(FileTreeRepository.scala:40)
at sbt.BuiltinCommands$.$anonfun$setupGlobalFileTreeRepository$1(Main.scala:985)
at sbt.BuiltinCommands$.$anonfun$doLoadProject$5(Main.scala:974)
at sbt.Project$.setProject(Project.scala:501)
at sbt.BuiltinCommands$.doLoadProject(Main.scala:974)
at sbt.BuiltinCommands$.$anonfun$loadProjectImpl$2(Main.scala:912)
at sbt.Command$.$anonfun$applyEffect$4(Command.scala:150)
at sbt.Command$.$anonfun$applyEffect$2(Command.scala:145)
at sbt.Command$.process(Command.scala:189)
at sbt.MainLoop$.$anonfun$processCommand$5(MainLoop.scala:245)
at scala.Option.getOrElse(Option.scala:189)
at sbt.MainLoop$.process$1(MainLoop.scala:245)
at sbt.MainLoop$.processCommand(MainLoop.scala:278)
at sbt.MainLoop$.$anonfun$next$5(MainLoop.scala:163)
at sbt.State$StateOpsImpl$.runCmd$1(State.scala:289)
at sbt.State$StateOpsImpl$.process$extension(State.scala:325)
at sbt.MainLoop$.$anonfun$next$4(MainLoop.scala:163)
at sbt.internal.util.ErrorHandling$.wideConvert(ErrorHandling.scala:23)
at sbt.MainLoop$.next(MainLoop.scala:163)
at sbt.MainLoop$.run(MainLoop.scala:144)
at sbt.MainLoop$.$anonfun$runWithNewLog$1(MainLoop.scala:119)
at sbt.io.Using.apply(Using.scala:27)
at sbt.MainLoop$.runWithNewLog(MainLoop.scala:112)
at sbt.MainLoop$.runAndClearLast(MainLoop.scala:66)
at sbt.MainLoop$.runLoggedLoop(MainLoop.scala:51)
at sbt.MainLoop$.runLogged(MainLoop.scala:42)
at sbt.StandardMain$.runManaged(Main.scala:218)
at sbt.xMain$.$anonfun$run$11(Main.scala:133)
at scala.util.DynamicVariable.withValue(DynamicVariable.scala:62)
at scala.Console$.withIn(Console.scala:230)
at sbt.internal.util.Terminal$.withIn(Terminal.scala:560)
at sbt.internal.util.Terminal$.$anonfun$withStreams$1(Terminal.scala:350)
at scala.util.DynamicVariable.withValue(DynamicVariable.scala:62)
at scala.Console$.withOut(Console.scala:167)
at sbt.internal.util.Terminal$.$anonfun$withOut$2(Terminal.scala:550)
at scala.util.DynamicVariable.withValue(DynamicVariable.scala:62)
at scala.Console$.withErr(Console.scala:196)
at sbt.internal.util.Terminal$.withOut(Terminal.scala:550)
at sbt.internal.util.Terminal$.withStreams(Terminal.scala:350)
at sbt.xMain$.withStreams$1(Main.scala:87)
at sbt.xMain$.run(Main.scala:121)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at sbt.internal.XMainConfiguration.run(XMainConfiguration.java:56)
at sbt.xMain.run(Main.scala:46)
at xsbt.boot.Launch$.$anonfun$run$1(Launch.scala:149)
at xsbt.boot.Launch$.withContextLoader(Launch.scala:176)
at xsbt.boot.Launch$.run(Launch.scala:149)
at xsbt.boot.Launch$.$anonfun$apply$1(Launch.scala:44)
at xsbt.boot.Launch$.launch(Launch.scala:159)
at xsbt.boot.Launch$.apply(Launch.scala:44)
at xsbt.boot.Launch$.apply(Launch.scala:21)
at xsbt.boot.Boot$.runImpl(Boot.scala:78)
at xsbt.boot.Boot$.run(Boot.scala:73)
at xsbt.boot.Boot$.main(Boot.scala:21)
at xsbt.boot.Boot.main(Boot.scala)
[error] java.lang.NoClassDefFoundError: Could not initialize class com.swoval.runtime.ShutdownHooks
[error] Use 'last' for the full log.
[warn] Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore? (default: r)
Exception in thread "Thread-0" java.lang.NoClassDefFoundError: Could not initialize class com.swoval.runtime.ShutdownHooks
at com.swoval.runtime.ShutdownHooks$1.run(ShutdownHooks.java:25)
EDIT3: Tried creating a new user and just downloading sbt and still getting the same issue. Will attempt completely removing Java as it seems to be the culprit and reinstalling.
Similar to Boris's suggestion the issue lied in the installation version of Java.
There are two versions for AdoptOpenJDK, .j9 an .hs as seen below if you are using sdk-man as a package manager:
AdoptOpenJDK | >>> | 16.0.1.j9 | adpt | installed | 16.0.1.j9-adpt
| | 16.0.1.hs | adpt | | 16.0.1.hs-adpt
| | 11.0.11.j9 | adpt | | 11.0.11.j9-adpt
| | 11.0.11.hs | adpt | | 11.0.11.hs-adpt
For some reason the OpenJDK version .hs-adpt shows this issue for every version but the .j9-adpt version works fine.
TLDR: Install the .j9-adpt version of Java that you need otherwise .hs-adpt is not working for me with sbt version 1.5.4.
I assume the reason - you are using wrong Java JDK for Mac OS with M1 chip. You need to install proper Java JDK version, I use sdkman for that.
Install sdk man:
curl -s "https://get.sdkman.io" | bash
source "$HOME/.sdkman/bin/sdkman-init.sh"
set up sdk man to not use rosetta2_compatbile versions:
vim .sdkman/etc/config
and set sdkman_rosetta2_compatbile=false
choose java JDK from the list:
sdk list java
================================================================================
Available Java Versions
================================================================================
Vendor | Use | Version | Dist | Status | Identifier
--------------------------------------------------------------------------------
Azul Zulu | | 16.0.1 | zulu | | 16.0.1-zulu
| | 11.0.11 | zulu | | 11.0.11-zulu
| | 8.0.292 | zulu | | 8.0.292-zulu
BellSoft | | 16.0.1 | librca | | 16.0.1-librca
| | 11.0.11 | librca | | 11.0.11-librca
| | 8.0.292 | librca | | 8.0.292-librca
Java.net | | 18.ea.3 | open | | 18.ea.3-open
| | 18.ea.2 | open | | 18.ea.2-open
| | 18.ea.1 | open | | 18.ea.1-open
| | 17.ea.28 | open | | 17.ea.28-open
| | 17.ea.27 | open | | 17.ea.27-open
| | 17.ea.26 | open | | 17.ea.26-open
| | 17.ea.25 | open | | 17.ea.25-open
================================================================================
and install it using command sdk install java IDENTIFIER, i.e.:
sdk install java 16.0.1-zulu
I need HELP
I have two major errors in creating my first substraste chain (cf. https://substrate.dev/docs/en/tutorials/create-your-first-substrate-chain/setup)
Error in Installing the Front-End Template
~/Bureau/ETH-BIT/substrate/substrate-front-end-template$ ls LICENSE
package.json public README.md src yarn.lock
pclf#ubuntu:~/Bureau/ETH-BIT/substrate/substrate-front-end-template$
yarn install
ERROR: [Errno 2] No such file or directory: 'install'
Error in compiling Substrate
cargo build --release
error: failed to run custom build command for node-template-runtime v2.0.0 (/home/pclf/Bureau/ETH-BIT/substrate/substrate-node-template/runtime)
Caused by: process didn't exit successfully:
/home/pclf/Bureau/ETH-BIT/substrate/substrate-node-template/target/release/build/node-template-runtime-663c8dc25926c960/build-script-build
(exit code: 1) --- stdout Executing build command: "rustup" "run"
"nightly" "cargo" "rustc" "--target=wasm32-unknown-unknown"
"--manifest-path=/home/pclf/Bureau/ETH-BIT/substrate/substrate-node-template/target/release/wbuild/node-template-runtime/Cargo.toml" "--color=always" "--release"
--- stderr
Compiling wasm-build-runner-impl v1.0.0 (/home/pclf/Bureau/ETH-BIT/substrate/substrate-node-template/target/release/wbuild-runner/node-template-runtime4021631938540302808)
Finished release [optimized] target(s) in 7.49s
Running /home/pclf/Bureau/ETH-BIT/substrate/substrate-node-template/target/release/wbuild-runner/node-template-runtime4021631938540302808/target/x86_64-unknown-linux-gnu/release/wasm-build-runner-impl
Compiling sp-arithmetic v2.0.0
Compiling sp-io v2.0.0
Compiling sp-inherents v2.0.0
Compiling frame-metadata v12.0.0
Compiling sp-finality-tracker v2.0.0 error[E0282]: type annotations needed
--> /home/pclf/.cargo/registry/src/github.com-1ecc6299db9ec823/sp-arithmetic-2.0.0/src/fixed_point.rs:541:9
| 541 | let accuracy = P::ACCURACY.saturated_into();
| ^^^^^^^^ consider giving accuracy a type ... 1595 | / implement_fixed!( 1596 | | FixedI64,
1597 | | test_fixed_i64, 1598 | | i64, ... | 1601 | |
"Fixed Point 64 bits signed, range = [-9223372036.854775808,
9223372036.854775807]", 1602 | | );
| |__- in this macro invocation
|
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
error[E0282]: type annotations needed
--> /home/pclf/.cargo/registry/src/github.com-1ecc6299db9ec823/sp-arithmetic-2.0.0/src/fixed_point.rs:541:9
| 541 | let accuracy = P::ACCURACY.saturated_into();
| ^^^^^^^^ consider giving accuracy a type ... 1604 | / implement_fixed!( 1605 | | FixedI128,
1606 | | test_fixed_i128, 1607 | | i128, ... | 1611 |
| [-170141183460469231731.687303715884105728,
170141183460469231731.687303715884105727]_", 1612 | | );
| |__- in this macro invocation
|
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
error[E0282]: type annotations needed
--> /home/pclf/.cargo/registry/src/github.com-1ecc6299db9ec823/sp-arithmetic-2.0.0/src/fixed_point.rs:541:9
| 541 | let accuracy = P::ACCURACY.saturated_into();
| ^^^^^^^^ consider giving accuracy a type ... 1614 | / implement_fixed!( 1615 | | FixedU128,
1616 | | test_fixed_u128, 1617 | | u128, ... | 1621 |
| [0.000000000000000000,
340282366920938463463.374607431768211455]_", 1622 | | );
| |__- in this macro invocation
|
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
error: aborting due to 3 previous errors
For more information about this error, try rustc --explain E0282.
error: could not compile sp-arithmetic
error: build failed
You can just run yarn in the front end template directory, it will work. But where is the "Is LICENCE public" message coming from? You shouldn't see that. Did you clone the substrate-front-end-template repo or just create the directory? The exact process is:
clone it with git clone https://github.com/substrate-developer-hub/substrate-front-end-template
enter folder with cd substrate-front-end-template
run yarn
As for the Substrate compilation error, please downgrade your nightly to an older version, it happens due to a bug in Rust. Here is how to do that:
rustup uninstall nightly
rustup install nightly-2020-10-01
rustup target add wasm32-unknown-unknown --toolchain nightly-2020-10-01
First thing first solve the Substrate compiling first.
run this scrip
https://github.com/substrate-developer-hub/substrate-node-template/blob/master/scripts/init.sh
When you get the node up and running then start using frontend.
When trying to install my application as an osgi bundle with the install command in karaf on the command line, everything seems fine. When I then type start (id) everything still seems fine, but my application does not seem to accept requests. When I then type log:display, I get this:
2016-04-20 13:49:38,251 | INFO | Thread-19 | bundle | 37 - org.apache.aries.spifly.dynamic.bundle - 1.0.1 | Bundle Considered for SPI providers: oms-integrations
2016-04-20 13:49:38,251 | INFO | Thread-19 | bundle | 37 - org.apache.aries.spifly.dynamic.bundle - 1.0.1 | No 'SPI-Provider' Manifest header. Skipping bundle: oms-integrations
I'm new and I have no clue what this means ("No 'SPI-Provider' Manifest header.") or how to solve it?
This is not a problem. It just means that you have Aries spi-fly installed. It scans all bundles for this header and enhances the ones with the header to be able to use the ServiceLoader in OSGi. If you do not use ServiceLoader then you can safely ignore these messages.
You can also configure this logger to WARN to suppress the messsages.
I'm developing a blog using jekyll and up until now I was very happy with it.
But as I make more posts the regeneration times are getting ridiculous (3-4 minutes). It's just not feasible to wait that long every time you make a change.
Specs:
Ruby 2.2.1
Jekyll 2.5.3
markdown: kramdown
highlighter: pygments
permalink:pretty
Working on a cloud service (Cloud9) with 2 GB of RAM
Not a lot of posts (~10), but I do use a lot of data (10 MB of json files in the "_data" folder, 14 MB of images in "img" folder)
Total size of the "_site" folder is 40 MB
Is it a normal thing with these specifications?
I've updated to Jekyll 3.0 to try incremental regeneration, but it didn't help in my case.
Any ideas?
Thanks!
Willem
Run jekyll serve --profile on your site and check what is taking more time to render. It should output a table that looks something like this.
Filename | Count | Bytes | Time
----------------------------------------------------------------------+-------+----------+------
_layouts/compress.html | 73 | 1649.86K | 1.526
_layouts/default.html | 72 | 1874.79K | 0.445
_layouts/post.html | 58 | 980.02K | 0.307
_posts/2015-12-10-how-to-create-and-host-a-website-on-github-pages.md | 1 | 9.36K | 0.294
feed.xml | 1 | 34.74K | 0.105
_includes/prev-next.html | 58 | 39.17K | 0.053
sitemap.xml | 1 | 19.90K | 0.035
_pages/archive.md | 1 | 28.98K | 0.035
_posts/2017-02-15-jekyll-sort-filters.md | 1 | 16.09K | 0.019
_includes/ga_data_fetch.html | 58 | 41.77K | 0.018
_includes/disqus-script.html | 58 | 30.89K | 0.018
_pages/tags.html | 1 | 14.97K | 0.015
That should give you a fair idea on where the problem exists.
Now while making changes to the site, if you want to render only the changed files then use jekyll serve --incremental or jekyll serve -I.
Incremental build still has some issues that the Jekyll team is working on.
A handy option to render only the latest post that you are writing would be jekyll serve --watch --limit_posts 1. This has saved me a lot of time while writing new posts.
There are a few options
Use --incremental on jekyll build or serve but use with caution
Use --profile on jekyll build to get an output of where time is used up
You could also have different config.yml files where you might include only draft posts for development and not for production.
Consider restructuring your development environment
Development folder with _posts containing just a sample
Production folder with your live set of _posts
copy you dev content over prior to production build
The profiling was showing nothing to worry about, but I was still getting 2-3 seconds regeneration times with a simple one page website.
I used a super simple Gemfile
source 'https://rubygems.org'
ruby "2.4.2"
gem "jekyll", "~> 3.6.2"
Then called bundle install again.
After that, regeneration times were back under 1 second.