Does Corda node explorer work with Tokens?
I am able to connect to the the stockpaydividend coradapp via Corda node explorer.
Everything seems to be working fine except the Vault Explorer.
When clicking on the vault explorer, I get the following error.
Described type with descriptor net.corda:Ilpg7fRBQWWGmwpkEi3Mtg== was expected to be of type class
com.r3.corda.lib.tokens.contracts.types.TokenType but was class com.r3.corda.lib.tokens.contracts.types.TokenPointer
Thanks
Ideally yes the node explorer doesn't really care about the data types of what's used in flows or states or anything like that.
This looks like it MIGHT be a bug so if you haven't modified the CorDapp it would be worth making an issue on github.
link:
https://github.com/corda/node-explorer/issues/new
Related
I've read similar questions others have had in using FTDI (CDC Class) and WebUSB, however none of the suggested answers have worked for me.
I'm trying to communicate to an Arudino Mega via:
this.device_.selectConfiguration(1)
this.device_.claimInterface(0); // or this.device_.claimInterface(1);
but I get a DOMException.. and chrome://device-log shows the device in blue ("USB user").
I know Chrome must use an interface that is not bound or attached to Windows, however, the USBconfiguration shows 2 interfaces, both not claimed, and yet I can't claim either.
Despite trying to uninstall and use WinUsb.sys, Windows always loads the ftdiport.sys driver NOT WinUsb.sys. Not sure what could be the problem.
The two interfaces are listed as unclaimed because your page hasn't claimed them. Whether or not there is another application or driver on the system claiming the interface is not reflected in the API.
Fighting with Windows to not load ftdiport.sys may be a losing battle. I am working on implementing the Serial API in Chrome which should offer a better solution for this class of devices. Alternatively, have you tried installing the WinUSB driver with the Zadig tool?
Is it possible to use corda node-explorer for cordapps other than cash? Is there any open source project to visualise what's going on in the blockchain for my cordapp?
Node Explorer currently only works for the cash CorDapp.
I don't know of any other open source projects to visualise activity on Corda.
However, it would make for a great project to extend Node Explorer to include other CorDapps, the source is available here https://github.com/corda/corda/tree/master/tools
It is a long back question, but still want to update since someone may need this.
A Beta Release for Node-Explorer was released recently, whose key highlight is:
Node Explorer is able to point to your own CorDapps.
More details in here:
https://github.com/corda/node-explorer/releases
https://www.youtube.com/watch?v=cn2lhS8pjRs
I've been working on a game using Google VR in Unity3d and I recently updated my version of unity3d and the (built in) Google VR SDK to the latest version. After doing so the pre-launch report (automated testing on firebase) is showing crashes, during the unity splash screen, on 5 out of 6 devices.
This is the issue that is reported:
Issue: Crash of app uk.co.softkitty.puzzleroom running instrumentation ComponentInfo{com.google.android.apps.mtaas.crawler/android.support.test.runner.AndroidJUnitRunner}
Not very helpful, it looks like a generic unit test result if the app closes unexpectedly . I've looked through the logs and cant find anything unusual from my app or unity, but I did find something. It looks to me like this may be being caused by the test script itself:
10-27 01:54:54.494: I/ViewInteraction(19677): Performing 'single click' action on view (with class name: is "android.widget.ImageButton" and with id: uk.co.softkitty.puzzleroom:id/ui_back_button ...............
This to me, looks like the test runner is exploring the app UI and the first thing it does is click the "back" button. Which I would expect to close the app. I also tried using Firebase directly, which seemed to confirm it:
Firebase Activity Map
Does that seem likely that this is just a bug/red herring caused by changes to unity/GVR Or even firebase? Has anyone else experienced this?
I just don't want to release it if it really is crashing on so many devices!
Many Thanks
I asked Google Play Support about this and they got back to me.
They have confirmed that the issue is caused by a new crawler used by the Pre-Launch report. Details can be found here under the section "Pre-launch report versions"
They've escalated the issue and have also provided a workaround:
Sign in to your Play Console.
Select an app.
Select Release management > Pre-launch report > Settings.
In the “Pre-launch report version” section, move the Opt-out switch
to the right until it turns blue.
I haven't verified this yet but will mark as answer once I have.
Edit
I have tested this and all the tests pass again so this looks like a good solution for now.
We got this when uploading our APK as well. It started October 27th and crashed the following 4 days until we changed our setup. I couldn't see anything in our code base that should trigger this problem, so I wonder if it's related to changes on Google's side.
However, we did just did two changes and now everything's working again.
We added the following line to proguard-project.txt:
-keep class android.arch.** { *; }
I assume this was what fixed it.
At the same time we changed the compileSdkVersion and targetSdkVersion to 27 (and correspondingly all belonging support libs). For all I know they could have fixed it here too..
Edit:
To more directly answer your question: Yes, it does seem likely that this is just a bug/red herring, not on Unity's side, but in Firebase Test Lab or in Google's support lib. I tested the APK that failed the pre-launch tests and it worked just fine on my device.
I created a snapshot view using Rational ClearCase explorer.
After creating it, I set the config specs, environmental variables and later tried compiling my code and got an MVFS error which says:
Unable to determine if the current working directory is in MVFS - no such device or address
When I searched the IBM website for the sake of eliminating this error, I found out that a snapshot view does not use the MVFS !
Why am I getting this error when Snapshot view does not use MVFS?
When this issue got triggered: Actually in our project we were using a ClearCase (8.0.0.7 version). We never had problems when we tried to build our code on the 8.0.0.7 version. It was only after upgrading this version to 8.0.0.15 that the build issue has arisen. The legacy of both old and new ClearCases are baseClearcase
Some more specifications regarding the issue:
The server which we are using is a Windows 2003 server. I am creating a snapshot view in H drive (NTFS drive) as C drive is not available for use in our project, cleaning the previously built files by running the shell script clean_view.sh and then compiling our C code with the ClearCase command clearmake.exe all. Previously we used to follow the same procedure where build used to succeed, but now the same has become an issue.
This question is an extension to the question which I have asked previously. I am re-posting this question as a whole thing again in order to give more clarity about the issue and also for more number of ClearCase experts to chime-in. Kindly do not treat this as a duplicate one or force close it as my issue has not yet been resolved. Also please note that this is the first time I am working with ClearCase.
LINK FOR THE PREVIOUS QUESTION: MVFS error in a snapshot view
Recently there was a development in the solution of this issue !! We escalated this issue to IBM with the help of our client. They suggested us to use Dynamic views and we used them. To our surprise it was working fine and we are able to generate the executables. But the fact still remains that we are not able to use snapshot views !!
NOTE: This comment is just to share my knowledge and experience regarding this issue. :)
While a snapshot view isn't in the MVFS, clearmake has MVFS-specific functionality for build auditing.
You mentioned that the "H" drive contained the snapshot view, is H:
A local or network drive?
A drive letter created via SUBST? In this case, is the parent drive local?
Do builds in dynamic views still work?
Does the C drive exist? Is it remapped in a Terminal Server/Citrix environment?
A caveat: Windows Server 2003 is nearly a year past MICROSOFT'S end of extended support. I would recommend updating the server environment as soon as possible.
Truthfully, issues where a process fails, and the ONLY change is the ClearCase version are usually best handled by contacting IBM instead of using this venue. Not trying to shill or anything, but if it's a clearmake bug, it has to go there anyway...
Additional questions:
If the C: drive is inaccessible on the system, which is what "can't even get the properties" in the comment seems to infer, where is the OS installed? Where does %SYSTEMROOT% point?
If it worked on a different drive, what's different between those 2 drives (H: Failed and R: worked)
As per title, does anyone know why it freezes every 30 seconds?
I figured that it was some sort of timer with Google Maps but cant find any such reference.
To recreate, simply copy into a local file the full html + javascript from:
https://developers.google.com/maps/documentation/javascript/examples/map-simple
Open the local html file and then just move the map around and it will freeze within 30 seconds. Once it unfreezes, it works fine until 30 seconds have elapsed.
Seems to only happen in IE (i used version 11). Note that it doesnt freeze within the Google example page above.
Any help would be appreciated.
This appears to be an issue in the experimental version, currently 3.20.
See versioning in the Developer's Guide
Versioning
The Google Maps API team will regularly update this Javascript API with new features, bug fixes, and performance improvements. All API changes will be backwards-compatible, ensuring that if you launch an application using the currently documented interfaces, that application will continue to work without modification as the API is updated. (Note: experimental features, documented in the Experimental API Reference are not covered by this guarantee. Features that are experimental will be clearly labeled in the API documentation.)
Types of Versions
You can indicate which version of the API to load within your application by specifying it using the v parameter of the Maps Javascript API bootstrap request. Three options are supported:
The experimental version, specified with v=3.exp.
The release version, specified with v=3 or v=3.19.
A numbered version, specified with v=3.18.
If you do not explicitly specify a version, you will receive the experimental version by default. Google Maps API for Work customers who specify a client ID will receive the release version by default.
The experimental version
The experimental version — currently 3.20 — contains the latest features and bug fixes as they are made publicly available. Changes made to the experimental version are not guaranteed to be feature stable. We encourage you to regularly test your applications with the experimental version, which you can do by adding v=3.20 when loading the Maps API. If you like to live on the edge, you can add v=3.exp to always receive the current experimental version with all of its latest features.
I think it has something to do with the security settings (for local files).
Because I hosted the exact same file on github, and it seems to work fine. And the only difference between the two files are their storing location.
If you open the local file, it would says something like internet explorer restricted this webpage from running scripts or activex controls, so I would say it is the security settings for local files.
If you try to run the HTML from a local drive with developer tools on you get the error 'Invalid Argument', in the function below, then you hit f5 to continue and the map eventually renders. Hope this helps.
function dn(a,b){return a.setQuery=b}function en(a,b){return a.background=b}function fn(a,b){return a.tilt_changed=b}function gn(a,b){return a.bounds_changed=b}function hn(a,b){return a.getStatus=b}function jn(a,b){return a.getQuery=b}function kn(a,b){return a.projectionBounds_changed=b}function ln(a,b){return a.border=b}