Codename One Windows Phone Build Fail - windows-phone-8

I'm experiencing problems while building my Codename One project for Windows Phone.
I've had 3 attempts: 2 failed and 1 was stuck on a build phase for more than an hour and I decided to cancel it.
I've downloaded error logs for both failed attempts (files were more than 60M and I've noticed it too late, so sorry for using your server's bandwidth). Here is the extract (files sizes are more than 60M) from the last error log (2f361a99-589d-4e29-9e6d-14d22b1cacc3-1453240937030-error.txt/Tue Jan 19 2016 23:46:42 GMT+0200 (FLE Standard Time)):
Executing: java -Xmx1024m -jar win_xmlvm.jar --in=C:\Users\Shai\AppData\Local\Temp\build6825805865501307423xxx\classes --resource=C:\Users\Shai\AppData\Local\Temp\build6825805865501307423xxx\ApplicationCN1\ApplicationCN1\res/ --out=C:\Users\Shai\AppData\Local\Temp\build6825805865501307423xxx\ApplicationCN1\ApplicationCN1\src --target=csharp --app-name=ApplicationCN1 [01/19/16 23:47:19.038] ERROR: Couldn't create node for com.codename1.impl.ImplementationFactory
[01/19/16 23:47:19.038] ERROR: Couldn't create node for com.codename1.impl.ImplementationFactory
...classes...
...lots of warnings about hidden inherited members...
"C:\Users\Shai\AppData\Local\Temp\build6825805865501307423xxx\ApplicationCN1\ApplicationCN1.sln" (default target) (1) ->
"C:\Users\Shai\AppData\Local\Temp\build6825805865501307423xxx\ApplicationCN1\ApplicationCN1\ApplicationCN1.csproj" (default target) (2) ->
(CoreCompile target) ->
src\com\yyy\yyy\DialogForm.cs(1133,5): error CS1511: Keyword 'base' is not available in a static method [C:\Users\Shai\AppData\Local\Temp\build6825805865501307423xxx\ApplicationCN1\ApplicationCN1\ApplicationCN1.csproj]
130875 Warning(s)
1 Error(s)
Time Elapsed 00:07:44.77
My configuration:
Windows 7 SP1 x64;
Java SE Development Kit 7 Update 45 (64-bit);
Eclipse IDE for Java Developers, Version: Luna Service Release 2 (4.4.2), Build id: 20150219-0600;
Plugin: CodenameOneFeature 1.0.0.201511241324;
Contents of my codenameone_settings.properties:
#
#Mon Jan 18 16:05:13 EET 2016
codename1.vendor=yyy
codename1.displayName=yyy
codename1.icon=icon.png
codename1.languageLevel=5
codename1.secondaryTitle=yyy
codename1.version=0.4
codename1.mainName=ApplicationCN1
codename1.ios.certificatePassword=
codename1.rim.signtoolDb=
libVersion=97
codename1.ios.certificate=
codename1.arg.j2me.nativeThemeConst=3
codename1.arg.ios.add_libs=CFNetwork.framework
codename1.arg.android.debug=false
codename1.arg.android.release=true
codename1.j2me.nativeTheme=
codename1.rim.signtoolCsk=
codename1.rim.certificatePassword=
codename1.ios.provision=
codename1.packageName=com.yyy.yyy
What am I doing wrong?

You probably have a field or method named base and our old XMLVM based backend isn't smart enough to deal with that (reserved word in C#).
Just rename that for now and also look at the project size.
We are currently working on a rewrite of the Windows Phone VM/port so this and many other issues won't exist when we are done. Since its almost a complete rewrite (we will probably base it in part on the community port) this might take a while to deliver.

Related

Couchbase Java SDK times out with BUCKET_NOT_AVAILABLE

I am doing a lookup operation Couchbase Java SDK 3.0.9 which looks like this:
// Set up
bucket = cluster.bucket("my_bucket")
collection = bucket.defaultCollection()
// Look up operation
val specs = listOf(LookupInSpecStandard.get("hash"))
collection.lookupIn(id, specs)
The error I get is BUCKET_NOT_AVAILABLE. Here are is the full message:
com.couchbase.client.core.error.UnambiguousTimeoutException: SubdocGetRequest, Reason: TIMEOUT {"cancelled":true,"completed":true,"coreId":"0xdb7f8e4800000003","idempotent":true,"reason":"TIMEOUT","requestId":608806,"requestType":"SubdocGetRequest","retried":39,"retryReasons":["BUCKET_NOT_AVAILABLE"],"service":{"bucket":"export","collection":"_default","documentId":"export:main","opaque":"0xcfefb","scope":"_default","type":"kv"},"timeoutMs":15000,"timings":{"totalMicros":15008977}}
The strange part is that this code hasn't been touched for months and the lookup broke out of a sudden. The CB cluster is working fine. Its version is
Enterprise Edition 6.5.1 build 6299.
Do you have any ideas what might have gone wrong?
Note that in Couchbase Java SDK 3.x, the Cluster::bucket method returns instantly, and continues opening a bucket in the background. So the first operation you perform - a lookupIn here - needs to wait for that resource opening to complete before it can proceed. It looks like it took a little longer to access the Couchbase bucket than usual and you got a timeout.
I recommend using the Bucket::waitUntilReady method after opening a bucket, to block until the resource opening is complete:
bucket = cluster.bucket("my_bucket")
bucket.waitUntilReady(Duration.ofMinutes(1));
This problem can occur because of firewall. You need to allow these ports.
Client-to-node
Unencrypted: 8091-8097, 9140 [3], 11210
Encrypted: 11207, 18091-18095, 18096, 18097
You can check more from below
https://docs.couchbase.com/server/current/install/install-ports.html#_footnotedef_2

CreateFile failed with 5

I'm using win xp Professional x64 Edition and I'm trying to send message to Windows Message Service like using net send. I'm using mailslot:
LPCTSTR SlotName = TEXT("\\\\.\\mailslot\\messngr");
hFile = CreateFile(SlotName,
GENERIC_WRITE | GENERIC_READ,
FILE_SHARE_WRITE | FILE_SHARE_READ,
(LPSECURITY_ATTRIBUTES)NULL,
CREATE_ALWAYS,
FILE_ATTRIBUTE_NORMAL,
(HANDLE)NULL);
and after launching it, I got error 5 from GetLastError() in CreateFile. I don't know how to fix it. I gave all VM permission, I turned message service ofc, and I can open it to be notpad like others suggested in: CreateFile() Failed With GetLastError() = 5. I tried many flags, but it didn't change anything. Any guess?
Like it says in the mailslot documentation, only the process that created the mailslot can read from it. Mailslots are one-way communication.
Remove the request for read access.

Parity error, Stage 3 block verification failed

I have a test environment of Parity POA of with 5 nodes. 3 nodes are synchronizing with each other but 2 are not able to synchronize. I am getting following error in the logs of nodes not synchronizing;
2018-03-13 17:19:13 Stage 3 block verification failed for #427607 (62e9…9621)
Error: Block(TooManyUncles(OutOfBounds { min: None, max: Some(0), found: 1 }))
Anyone experiencing same problem?
In my case 2 nodes are using parity client version 1.8.10, and other 3 nodes are using parity client version 1.8.3.
Nodes with parity 1.8.10 are throwing the above error.
After looking for this issue, I found out that parity clients with version 1.8.4 and above has default value 0 for a parameter "maximumUncleCount".
Few blocks in my blockchain has uncle blocks (don't know the reason, why) which cannot be imported by nodes using parity 1.8.10 and they give the error.
For now I set the "maximumUncleCount" value to 2 in the nodes with parity 1.8.10 (in blockchain-spec.json file) and now they are synchronizing with no problem.
A maximumUncleCount = 0 is recommended in POA environments by parity. I am going to hard fork to use maximumUncleCount = 0 soon.
https://github.com/paritytech/parity/releases/tag/v1.8.4

How could I get a crash log from the future in the Google Dev Console?

Maybe I'm going crazy...
I got a crash log in the Google Dev Console:
5 Feb 02:42 on app version 10
Google Emulator (generic_x86), 4096MB RAM, Android 8.0
Report 1 of 1
java.lang.IllegalArgumentException:
at business.dots.android.collection.ui.detail.redeem.states.RxStateMachine.register (RxStateMachine.kt)
at business.dots.android.collection.ui.detail.redeem.states.UIState.<init> (UIState.kt:15)
at business.dots.android.collection.ui.detail.redeem.states.UIStateIncomplete.<init> (UIStateIncomplete.kt:9)
at business.dots.android.collection.ui.detail.redeem.RedeemFragment.onCreateView (RedeemFragment.kt:58)
at android.support.v4.app.Fragment.performCreateView (Fragment.java:2261)
at android.support.v4.app.FragmentManagerImpl.moveToState (FragmentManager.java:1419)
at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState (FragmentManager.java:1750)
at android.support.v4.app.FragmentManagerImpl.moveToState (FragmentManager.java:1819)
at android.support.v4.app.BackStackRecord.executeOps (BackStackRecord.java:797)
at android.support.v4.app.FragmentManagerImpl.executeOps (FragmentManager.java:2590)
at android.support.v4.app.FragmentManagerImpl.executeOpsTogether (FragmentManager.java:2377)
at android.support.v4.app.FragmentManagerImpl.removeRedundantOperationsAndExecute (FragmentManager.java:2332)
at android.support.v4.app.FragmentManagerImpl.execPendingActions (FragmentManager.java:2239)
at android.support.v4.app.FragmentManagerImpl$1.run (FragmentManager.java:700)
at android.os.Handler.handleCallback (Handler.java:789)
at android.os.Handler.dispatchMessage (Handler.java:98)
at android.os.Looper.loop (Looper.java:164)
at android.app.ActivityThread.main (ActivityThread.java:6541)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:240)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:767)
The thing is that app version 10 was released back in 2017.
As of now, the class RxStateMachine does not exist in the release version.
I introduced the class around the 5th of February but i never released a version including the class.
Even if Google had a time machine and this exception is from the future, this would not be possible since I would have to use the next version code (11) in order to release a new version^^
So my question is...how is that possible?
But maybe I'm going crazy...

mysql time out with cakephp acl create utility

The app I'm working with is well established and uses a pretty standard CakePHP ACL set up with the usual ACO/ARO tables. I usually use the cakephp console (./cake acl ....) to add acos when I create a new action in a controller, and as recently as last week I was doing this just fine for a new controller I'd created.
This morning however when running the console utility I get a very lengthy delay and eventually get (my company DB URL removed):
./cake acl create aco Statistics data
Warning: mysql_connect(): [2002] Operation timed out (trying to
connect via tcp://[db url]:3306) in
/dev/docs/cake/libs/model/datasources/dbo/dbo_mysql.php on line 552
Warning: mysql_connect(): Operation timed out in
/dev/docs/cake/libs/model/datasources/dbo/dbo_mysql.php on line 552
Warning: mysql_select_db() expects parameter 2 to be resource, boolean
given in /dev/docs/cake/libs/model/datasources/dbo/dbo_mysql.php on
line 558
Warning: mysql_get_server_info() expects parameter 1 to be resource,
boolean given in
/dev/docs/cake/libs/model/datasources/dbo/dbo_mysql.php on line 566
Warning: mysql_query() expects parameter 2 to be resource, boolean
given in /dev/docs/cake/libs/model/datasources/dbo/dbo_mysql.php on
line 600 Error: Missing database table 'aros' for model 'Aro'
There is no isse with load time when using the app from the browser, nor with using any of the other DB-intensive actions I created last week. This dev copy of the app does not use Cake's cacheing, so that's not the problem. Really just seems to be choking somewhere specifically in adding the new aco.
I'd think it were an issue with the DB server if not for the fact that it is otherwise responding fine in the app. Any ideas where in Cake's guts this sort of a misstep could occur?
For the one in a million chance that someone is in my position, remember that when working in a large instiution there are these little things called firewalls, and if you're going to run a cake console, you'd better be SSH'd on to the webserver to run your ACO commands or anything involving a connection to your database server, instead of being mapped on to a shared drive as I decided to do this week.