I'm using Extjs-6. I created an app using sencha -sdk D:\xampp\htdocs\Lib\ext-premium-6.0.0\ext-6.0.0 generate app Prj1 D:\xampp\htdocs\ExtProjects\Workspace1\Prj1. I build the project with sencha app build and the theme result is as follow:
But When I build the project using sencha app watch the them result is as follow:
Why results are different?
I don't find any change in theme...For every two time you end up with new ExtJS 6 default Triton theme..
If you need to change theme then this is done by changing the extend property in “packages/local/my-classic-theme/package.json” from its default value as shown here:
"extend": "theme-neptune"
to
"extend": "theme-crisp"
UPDATED:
There is a bug related to sencha app build and sencha app watch.
You can see it at this thread at Sencha's Forum
OLD ANSWER:
For me it seems sencha app build does not update classic.json, so you have to execute sencha app watch.
I performed the following:
$ sencha app build development
Sencha Cmd v6.1.2.15
[INF] Using GPL version of Ext JS version 6.0.1.250 from /home/alfonso/git/goraexplorer/src/main/webapp/ext.
[INF] The implications of using GPL version can be found here (http://www.sencha.com/products/extjs/licensing).
[INF] Processing Build Descriptor : classic
[INF] Loading app json manifest...
[INF] Appending content to /home/alfonso/git/goraexplorer/src/main/webapp/bootstrap.js
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/classic.json
[INF] merging 258 input resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer/classic/resources
[INF] merged 0 resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer/classic/resources
[INF] merging 21 input resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer
[INF] merged 0 resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/sass/example/bootstrap.json
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/sass/example/bootstrap.js
[INF] Appending content to /home/alfonso/git/goraexplorer/src/main/webapp/bootstrap.js
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/classic.json
$ cd ..
$ cp -R webapp /tmp/webapp-build
$ sencha app watch
Sencha Cmd v6.1.2.15
[INF] Using GPL version of Ext JS version 6.0.1.250 from /home/alfonso/git/goraexplorer/src/main/webapp/ext.
[INF] The implications of using GPL version can be found here (http://www.sencha.com/products/extjs/licensing).
[INF] Processing Build Descriptor : classic
[INF] Starting server on port : 1841
[INF] Mapping http://localhost:1841/~cmd to /home/alfonso/bin/Sencha/Cmd/6.1.2.15...
[INF] Mapping http://localhost:1841/ to /home/alfonso/git/goraexplorer/src/main/webapp...
[INF] Application available at http://localhost:1841
[INF] Loading app json manifest...
[INF] Appending content to /home/alfonso/git/goraexplorer/src/main/webapp/bootstrap.js
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/classic.json
[INF] merging 258 input resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer/classic/resources
[INF] merged 0 resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer/classic/resources
[INF] merging 21 input resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer
[INF] merged 0 resources into /home/alfonso/git/goraexplorer/src/main/webapp/build/development/GoraExplorer
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/sass/example/bootstrap.json
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/sass/example/bootstrap.js
[INF] Appending content to /home/alfonso/git/goraexplorer/src/main/webapp/bootstrap.js
[INF] Writing content to /home/alfonso/git/goraexplorer/src/main/webapp/classic.json
[INF] Waiting for changes...
^C
$ cd ..
$ cp -R webapp /tmp/webapp-watch
$ diff -q -r /tmp/webapp-build /tmp/webapp-watch
Los archivos webapp-build/classic.json y webapp-watch/classic.json son distintos
(classic.json changed)
Here is the diff. As you can see, sencha app watch defines a "loadOrder" key that much probably is what makes the difference in your application:
You can check with the developer tools of the browser (F12) if it shows any error loading files.
Beware that if you execute sencha app build again, the changes in classic.json will be written wrongly again.
The real problem must be somewhere in the loader, but I think we can't fix it :/
Related
I'm using an ssh protocol to connect to a server(that I bought from a VPN seller) through a mac m1 terminal to pass filters in my country(Iran)
and it asks server password and connects to the server without any error.
I can pass filtered sites (googleapis.dev ---> that I need it, youtube,...)/ using safari or chrome
but...
when I want to access through the terminal I receive 403.
I don't know what to do.
any idea?
I think my terminal is not tunneled to the ssh server.
web sdk download 403 forbidden
downloading Ios tools
nezhadjavadali#alis-MacBook-Air ~ % flutter create my_app
Recreating project my_app...
Running "flutter pub get" in my_app...
Resolving dependencies in my_app...
collection 1.17.0 (1.17.1 available)
js 0.6.5 (0.6.7 available)
matcher 0.12.13 (0.12.14 available)
meta 1.8.0 (1.9.0 available)
path 1.8.2 (1.8.3 available)
test_api 0.4.16 (0.4.18 available)
Got dependencies in my_app!
Wrote 3 files.
All done!
You can find general documentation for Flutter at: https://docs.flutter.dev/
Detailed API documentation is available at: https://api.flutter.dev/
If you prefer video documentation, consider: https://www.youtube.com/c/flutterdev
In order to run your application, type:
$ cd my_app
$ flutter run
Your application code is in my_app/lib/main.dart.
nezhadjavadali#alis-MacBook-Air ~ % cd my_app
nezhadjavadali#alis-MacBook-Air my_app % flutter run
Downloading Web SDK... 1,010ms
Downloading Web SDK... 683ms
Failed to download https://storage.googleapis.com/flutter_infra_release/flutter/248290d6d50a1bf1a6a246544347c03acda867a5/flutter-web-sdk-darwin-x64.zip.
Ensure you have network connectivity and then try again.
Exception: 403
nezhadjavadali#alis-MacBook-Air my_app %
--------------------------------------------
nezhadjavadali#alis-MacBook-Air my_app % ping youtube.com
PING youtube.com (10.10.34.36): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
-------------------------------------------
I'm having a hard time to deploy this standard ecommerce project on Bluemix:
https://github.com/zallaricardo/ecommerce-devops
I've chosen to do it with git repository and automatic deploy through the Bluemix pipeline service. After successfully building and fixing a lot of misconfigurations, the root challenge seems to be write a correct version of the manifest.yml file for the project.
Without the manifest.yml file, the log shows the following error:
Downloading artifacts...DOWNLOAD SUCCESSFUL
Target: https://api.ng.bluemix.net
Updating app loja-virtual-devops in org pfc-devops / space Dev as [email account]...
OK
Uploading loja-virtual-devops...
Uploading app files from: /home/pipeline/d38f0184-33da-44da-ba16-4671b491988a
Uploading 384.1M, 1679 files
228.5M uploaded...
Done uploading
OK
Stopping app loja-virtual-devops in org pfc-devops / space Dev as [email account]...
OK
Starting app loja-virtual-devops in org pfc-devops / space Dev as[email account]...
-----> Downloaded app package (452M)
-----> Downloaded app buildpack cache (4.0K)
Staging failed: An application could not be detected by any available buildpack
FAILED
NoAppDetectedError
TIP: Buildpacks are detected when the "cf push" is executed from within the directory that contains the app source code.
Use 'cf buildpacks' to see a list of supported buildpacks.
Use 'cf logs loja-virtual-devops --recent' for more in depth log information.
And with the version of manifest which I believe * - I'm new on this manifests stuff* - to be ok and sufficient, the log shows:
Downloading artifacts...DOWNLOAD SUCCESSFUL
Target: https://api.ng.bluemix.net
FAILED
Error reading manifest file:
yaml: unmarshal errors:
line 2: cannot unmarshal !!seq into map[interface {}]interface {}
The manifest.yml file is currently written as follows:
---
- name: loja-virtual-devops
memory: 512M
buildpack: https://github.com/cloudfoundry/java-buildpack
domain: mybluemix.net
I'll sincerely appreciate any hint about how to fix the manifest for this application or another way to successfully deploy the project through Bluemix.
Try including the applications heading in your manifest.yml file.
example:
applications:
- name: appname
host: app_hostname
buildpack: java_buildpack
instances: 2
memory: 512M
disk_quota: 512M
path: .
I am using mod_zeropush to send push to offline users that are offline in xmpp/ejabberd it was working fine with ejabberd version 15.07 but when i updated my version it stopped working and not hitting this given url.
2016-05-12 14:07:57.107 [warning] <0.809.0>#gen_mod:validate_opts:288 module 'mod_zeropush' doesn't export mod_opt_type/1
2016-05-12 14:07:57.107 [warning] <0.809.0>#gen_mod:validate_opts:288 module 'mod_zeropush' doesn't export mod_opt_type/1
2016-05-12 14:07:57.107 [warning] <0.809.0>#gen_mod:validate_opts:288 module 'mod_zeropush' doesn't export mod_opt_type/1
These are warnings it shows before starting module.
Here is error log from ejabberd.log file
Please help me
Thanks
mod_zeropush does not support ejabberd 16.03 because it uses Fast XML instead of p1_xml so don't upgrade to 16.xx version stay with 15.xx
I'm trying to deploy an engine. I'm following the docs. So I:
create the app,
download the engine,
update the app name in engine.json,
build it: pio build --verbose,
then train: pio train --verbose.
Everything works, building completes successfully. However, training always fails with error:
[ERROR] [CreateWorkflow$] WorkflowConfig is empty. Quitting
I tried downloading another engine but the error is the same. There is nothing on the Internet about the WorkflowConfig. Does anyone have a clue what might be wrong?
I'm attaching pio.log contents below.
2015-07-07 07:20:06,128 INFO io.prediction.tools.console.Console$ [main] - Using existing engine manifest JSON at /home/vagrant/PredictionIO/mubuzz-similar-articles/manifest.json
2015-07-07 07:20:06,875 INFO org.elasticsearch.plugins [main] - [Jude the Entropic Man] loaded [], sites []
2015-07-07 07:20:07,706 INFO io.prediction.tools.Runner$ [main] - Submission command: /home/vagrant/PredictionIO/vendors/spark-1.3.1/bin/spark-submit --class io.prediction.workflow.CreateWorkflow --jars file:/home/vagrant/PredictionIO/mubuzz-similar-articles/target/scala-2.10/template-scala-parallel-similarproduct_2.10-0.1-SNAPSHOT.jar,file:/home/vagrant/PredictionIO/mubuzz-similar-articles/target/scala-2.10/template-scala-parallel-similarproduct-assembly-0.1-SNAPSHOT-deps.jar --files file:/home/vagrant/PredictionIO/conf/log4j.properties,file:/home/vagrant/PredictionIO/vendors/hbase-1.0.0/conf/hbase-site.xml --driver-class-path /home/vagrant/PredictionIO/conf:/home/vagrant/PredictionIO/vendors/hbase-1.0.0/conf file:/home/vagrant/PredictionIO/lib/pio-assembly-0.9.3.jar --engine-id sZTyLTTx277Kv58cgSQub4igE60DDagR --engine-version e7c5e07b70df531e8f7a92d278a16278c56d0581 --engine-variant file:/home/vagrant/PredictionIO/mubuzz-similar-articles/engine.json --verbosity 0 --verbose --json-extractor Both --env PIO_STORAGE_SOURCES_HBASE_TYPE=hbase,PIO_ENV_LOADED=1,PIO_STORAGE_REPOSITORIES_METADATA_NAME=pio_meta,PIO_FS_BASEDIR=/home/vagrant/.pio_store,PIO_STORAGE_SOURCES_HBASE_HOME=/home/vagrant/PredictionIO/vendors/hbase-1.0.0,PIO_HOME=/home/vagrant/PredictionIO,PIO_FS_ENGINESDIR=/home/vagrant/.pio_store/engines,PIO_STORAGE_SOURCES_LOCALFS_PATH=/home/vagrant/.pio_store/models,PIO_STORAGE_SOURCES_ELASTICSEARCH_TYPE=elasticsearch,PIO_STORAGE_REPOSITORIES_METADATA_SOURCE=ELASTICSEARCH,PIO_STORAGE_REPOSITORIES_MODELDATA_SOURCE=LOCALFS,PIO_STORAGE_REPOSITORIES_EVENTDATA_NAME=pio_event,PIO_STORAGE_SOURCES_ELASTICSEARCH_HOME=/home/vagrant/PredictionIO/vendors/elasticsearch-1.4.4,PIO_FS_TMPDIR=/home/vagrant/.pio_store/tmp,PIO_STORAGE_REPOSITORIES_MODELDATA_NAME=pio_model,PIO_STORAGE_REPOSITORIES_EVENTDATA_SOURCE=HBASE,PIO_CONF_DIR=/home/vagrant/PredictionIO/conf,PIO_STORAGE_SOURCES_LOCALFS_TYPE=localfs --verbose
2015-07-07 07:20:08,903 ERROR io.prediction.workflow.CreateWorkflow$ [main] - WorkflowConfig is empty. Quitting
This is a known issue, and fixed in the next release.
See the JIRA ticket, here: https://predictionio.atlassian.net/browse/PDIO-636
You just need to omit --verbose for now.
I recently tried to push one of the php examples on dotcloud and I got the error below. I am not sure how to get it to allocate the pseudo-terminal...
dotcloud push ramen ramen-on-dotcloud
# upload ramen-on-dotcloud ssh://dotcloud#uploader.dotcloud.com:443/ramen
# rsync
Pseudo-terminal will not be allocated because stdin is not a terminal.
building file list ... done
sent 141 bytes received 20 bytes 35.78 bytes/sec
total size is 55 speedup is 0.34
22:34:16 ---> Deploy of "ramen" scheduled for revision rsync-1339454056336 at 2012-06-11
22:34:16
22:34:17 ---> Building the application...
22:34:17 [www] Build started for revision rsync-1339454056336 (clean build)
22:34:18 [www] I am snapshotsworker_00/bob-2, and I will be your builder today.
22:34:21 [www] Build completed successfully. Compiled image size is 427KB
22:34:21 ---> Application build is done
22:34:21 ---> Initializing new services... (This may take a few minutes)
22:34:21 ---> Using default scaling for service www (1 instance(s)).
22:34:21 ---> No new services found
22:34:21 ---> All services have been initialized. Deploying code...
22:34:21 [www.0] Deploying build revision rsync-1339454056336...
22:34:25 [www.0] Running postinstall script...
22:34:27 [www.0] Launching...
22:34:28 [www.0] Waiting for the instance to become responsive...
22:34:28 [www.0] Re-routing traffic to the new build...
22:34:29 [www.0] Successfully deployed build revision rsync-1339454056336
22:34:29 ---> Deploy finished
22:34:29 ---> Application fully deployed
Deployment finished. Your application is available at the following URLs
www: http://ramen-l.dotcloud.com/
The pseudo-terminal message is informative. It does not indicate an error in this case.
Note that at the bottim it indicates
22:34:29 ---> Deploy finished
22:34:29 ---> Application fully deployed
Deployment finished. Your application is available at the following
URLs www: http://ramen-l.dotcloud.com/
so everything went fine.
/A