-
Change in xep-0060: https://xmpp.org/extensions/xep-0060.html#revision-history-v1.20.0
Version 1.20.0 (2021-06-08) Add integer-or-max datatype to use with Data Forms Validation.
with following description:
Data Forms Validation Datatypes Registry Submission
<datatype> <name>integer-or-max</name> <desc> Datatype used for text-single fields where the accepted value is either an integer or the string "max". </desc> <doc>XEP-0060</doc> </datatype>
-
-
This is not a bug on the server side, but I've added this feature anyway as it is a good to have. According to XEP-0060, clients should not use
max
as a value forpubsub#max_items
field, unless PubSub component (or even node) advertiseshttp://jabber.org/protocol/pubsub#config-node-max
feature. I think this issue should also be reported to the client developer. -
Revied and merged.
Issue reported: https://codeberg.org/moxxy/moxxy/issues/248
-
Failed TTS-NG test
testSupportAdvertisement
:java.lang.AssertionError: org.testng.AssertJUnit.fail(AssertJUnit.java:65) org.testng.AssertJUnit.assertTrue(AssertJUnit.java:23) org.testng.AssertJUnit.assertTrue(AssertJUnit.java:33) tigase.tests.pubsub.TestPubSub.testSupportAdvertisement(TestPubSub.java:99) java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.base/java.lang.reflect.Method.invoke(Method.java:568) org.testng.internal.invokers.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:135) org.testng.internal.invokers.TestInvoker.invokeMethod(TestInvoker.java:673) org.testng.internal.invokers.TestInvoker.invokeTestMethod(TestInvoker.java:220) org.testng.internal.invokers.MethodRunner.runInSequence(MethodRunner.java:50) org.testng.internal.invokers.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:945) org.testng.internal.invokers.TestInvoker.invokeTestMethods(TestInvoker.java:193) org.testng.internal.invokers.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146) org.testng.internal.invokers.TestMethodWorker.run(TestMethodWorker.java:128) java.base/java.util.ArrayList.forEach(ArrayList.java:1511) org.testng.TestRunner.privateRun(TestRunner.java:808) org.testng.TestRunner.run(TestRunner.java:603) org.testng.SuiteRunner.runTest(SuiteRunner.java:429) org.testng.SuiteRunner.runSequentially(SuiteRunner.java:423) org.testng.SuiteRunner.privateRun(SuiteRunner.java:383) org.testng.SuiteRunner.run(SuiteRunner.java:326) org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:95) org.testng.TestNG.runSuitesSequentially(TestNG.java:1249) org.testng.TestNG.runSuitesLocally(TestNG.java:1169) org.testng.TestNG.runSuites(TestNG.java:1092) org.testng.TestNG.run(TestNG.java:1060) org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:283) org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:75) org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:120) org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384) org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345) org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126) org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
Type |
Task
|
Priority |
Normal
|
Assignee | |
Version |
tigase-server-8.4.0
|
Iterations
-
tigase-server-8.4.0 Closed
Issue Votes (0)
When testing moxxy client I got an error that it's not possible to establish OMEMO encryption and it resulted in following exception on our side: