I have a React App and I am trying to use react-player but I get this error:
Module parse failed: Unexpected token
I have 13 similar errors coming from: ReactPlayer.jsx, YouTube.jsx, Facebook.jsx, Twitch.jsx and so on. What can I do? Or an alternative for ReactPlayer?
I deployed the contract on another computer and it worked, and now on a new envirenment and account the NEAR dApp is failing; here is the code:
https://github.com/bobmakesmagics/Multi-Near-NFT-Minter
// Get blockchian state once on component load and wallet is connected:f
nft.nftSupply(wallet.accountId)
.then(setTotalSupply)
.catch(console)
Error: [-32700] Parse error: Failed parsing args: missing field
account_id"
before I make the RPC call I actually console.log the args.. and there you see the account_id not missing... so what's the problem?
I am having problems trying to deploy the rest server with persistence storage (mongo db) I ge this message when deploying the rest server:
docker logs -f rest
[2018-03-12 00:01:13] PM2 log: Launching in no daemon mode
[2018-03-12 00:01:14] PM2 log: Starting execution sequence in -fork mode- for app name:composer-rest-server id:0
[2018-03-12 00:01:14] PM2 log: App name:composer-rest-server id:0 online
WARNING: NODE_APP_INSTANCE value of '0' did not match any instance config file names.
WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode
Discovering types from business network definition ...
Connection fails: Error: Error trying to ping. Error: Error trying to query business network. Error: REQUEST_TIMEOUT
It will be retried for the next request.
Exception: Error: Error trying to ping. Error: Error trying to query business network. Error: REQUEST_TIMEOUT
Error: Error trying to ping. Error: Error trying to query business network. Error: REQUEST_TIMEOUT
at _checkRuntimeVersions.then.catch (/home/composer/.npm-global/lib/node_modules/composer-rest-server/node_modules/composer-connector-hlfv1/lib/hlfconnection.js:699:34)
at
at process._tickDomainCallback (internal/process/next_tick.js:228:7)
[2018-03-12 00:07:03] PM2 log: App [composer-rest-server] with id [0] and pid [14], exited with code [1] via signal [SIGINT]
I am using composer v.18
is there any work around to fix this error. when I run the composer-rest- server alone it work. but if I try to add the mongodb it does not work
I have a problem with the new version of composer. My chaincode worked fine with the 0.11, now with the 0.13, when I add an asset outside of a chaincode, I have the error:
Error: Missing id"
Of course, the ID is present in the new asset after the creation ;-)
When I put the analog code in a chaincode to add the asset, I have the following error:
Error: Error trying invoke business network. Error: chaincode error (status: 500, message: Error: Object with ID 'Resource {id=zzz.yyy.xxx.tttt#e60e56d92a6928d3f4d1c5bc9bb828c3fc0a292c26ccc35935c594ac0e160c28}' in collection with ID 'Asset:zzz.yyy.xxx.tttt' does not exist)
Here an extract of the code (nothing special)
return getAssetRegistry(NS + '.ttt')
.then(function (tttRegistry) {
// Create the asset
var ttt = factory.newResource(NS, 'ttt', '12345');
// Add new ttt
return tttRegistry.add(ttt)
.then(function () {
// Emit an event
The identity which plays the code is the default admin user
Perhaps, I found something in logs, but I don'y know how to interpret it
2017-09-26T20:09:39.841Z ERROR HLFConnectionManager :fabric-client() [client-utils.js]: sendPeersProposal - Promise is rejected: Error: chaincode error (status: 500, message: Error: The current identity must be activated (ACTIVATION_REQUIRED)) at /home/hyperledger/node_modules/grpc/src/node/src/client.js:554:15 {}$
2017-09-26T20:09:39.842Z ERROR HLFConnection :queryChainCode() {"message":"Error trying to query business network. Error: chaincode error (status: 500, message: Error: The current identity must be activated (ACTIVATION_REQUIRED))","stack":"Error: Error trying to query business network. Error: chaincode error (status: 500, message: Error: The current identity must be activated (ACTIVATION_REQUIRED))\n at channel.queryByChaincode.then.catch (/home/hyperledger/node_modules/composer-connector-hlfv1/lib/hlfconnection.js:754:34)"}$
2017-09-26T20:09:39.842Z ERROR HLFConnection :ping() {"message":"Error trying to ping. Error: Error trying to query business network. Error: chaincode error (status: 500, message: Error: The current identity must be activated (ACTIVATION_REQUIRED))","stack":"Error: Error trying to ping. Error: Error trying to query business network. Error: chaincode error (status: 500, message: Error: The current identity must be activated (ACTIVATION_REQUIRED))\n at _checkRuntimeVersions.then.catch (/home/hyperledger/node_modules/composer-connector-hlfv1/lib/hlfconnection.js:668:34)"}$
The only info I found is this post Hyperledger Composer:: Error: The current identity must be activated (ACTIVATION_REQUIRED) but, in my case, versions of composer and packages are the same
I can't understand what's happening since I upgrade from 0.11 to 0.13
Any idea?
I found where the problem comes from.
It is not a design problem or something wrong with the ACL.
In Composer 0.11, in an event, if you have a relationship to an asset, in your code, you can access directly to its fields
Behavior change in Composer 0.13, the relationship to an element is only a reference, you can not access directly to its fields
Worst, the error is not rised when you call the method factory.newRelationship(), it is rised when you call the method assetRegistry.add()
So be careful
This sounds more like an issue with the model - you are trying to create a resource which has a required field called id and you are not supplying a value for that field.
Do you have a stack trace you can include?
If the Default rule - "All resource:" should be set to "zzz.yyy.xxx.*"
Then deploy your newly updated network and try again.
I looked at many other similar questions, but none seem to work for me.
I am following this example: http://www.devglan.com/spring-boot/spring-websocket-integration-example-without-stomp
When, I tried this example alone, it is working perfectly. However, when I tried to integrate it with my main project, it seems to be giving the error: WebSocket connection to 'ws://localhost:8080/socket' failed: Error during WebSocket handshake: Unexpected response code: 404
I am just calling index.html directly in my main project.
I am unable to find the source of error.
Following are all the jars in my main project where error is generated:
classmate-1.3.3.jar
commons-io-1.3.2.jar
commons-net-3.6.jar
groovy-2.4.10.jar
hibernate-validator-5.3.5.Final.jar
jackson-annotations-2.8.0.jar
jackson-core-2.8.8.jar
jackson-databind-2.8.8.jar
javassist-3.21.0-GA.jar
jboss-logging-3.3.1.Final.jar
jcl-over-slf4j-1.7.25.jar
json-20140107.jar
jul-to-slf4j-1.7.25.jar
log4j-over-slf4j-1.7.25.jar
logback-classic-1.1.11.jar
logback-core-1.1.11.jar
ognl-3.0.8.jar
slf4j-api-1.7.25.jar
snakeyaml-1.17.jar
spring-aop-4.3.8.RELEASE.jar
spring-beans-4.3.8.RELEASE.jar
spring-boot-1.5.3.RELEASE.jar
spring-boot-autoconfigure-1.5.3.RELEASE.jar
spring-boot-devtools-1.5.3.RELEASE.jar
spring-boot-starter-1.5.3.RELEASE.jar
spring-boot-starter-logging-1.5.3.RELEASE.jar
spring-boot-starter-thymeleaf-1.5.3.RELEASE.jar
spring-boot-starter-tomcat-1.5.3.RELEASE.jar
spring-boot-starter-web-1.5.3.RELEASE.jar
spring-boot-starter-websocket-1.5.3.RELEASE.jar
spring-context-4.3.8.RELEASE.jar
spring-core-4.3.8.RELEASE.jar
spring-expression-4.3.8.RELEASE.jar
spring-messaging-4.3.8.RELEASE.jar
spring-web-4.3.8.RELEASE.jar
spring-webmvc-4.3.8.RELEASE.jar
spring-websocket-4.3.8.RELEASE.jar
thymeleaf-2.1.5.RELEASE.jar
thymeleaf-layout-dialect-1.4.0.jar
thymeleaf-spring4-2.1.5.RELEASE.jar
tomcat-embed-core-8.5.14.jar
tomcat-embed-el-8.5.14.jar
tomcat-embed-websocket-8.5.14.jar
unbescape-1.1.0.RELEASE.jar
validation-api-1.1.0.Final.jar