-
Official names may contain "/" characters such as "s/o" representing "son of". Current app does not allow non-alphanumeric characters in the names
![Screenshot 2022-04-16 at 2.55.40 PM.png](https://…
-
Use "ᚓᚐᚋᚒᚄ"
Rationale: Non-alphanumeric characters are allowed, and therefore application should be able to render them
Perhaps limit the attribute to alphanumeric characters (like in tags)
![imag…
-
Use "ᚓᚐᚋᚒᚄ"
Rationale: Non-alphanumeric characters are allowed, and therefore application should be able to render them
Perhaps limit the attribute to alphanumeric characters (like in tags)
![image…
-
Use "ᚓᚐᚋᚒᚄ"
Rationale: Non-alphanumeric characters are allowed, and therefore application should be able to render them
Perhaps limit the attribute to alphanumeric characters (like in tags)
![imag…
-
Use "ᚓᚐᚋᚒᚄ"
Rationale: Non-alphanumeric characters are allowed, and therefore application should be able to render them
Perhaps limit the attribute to alphanumeric characters (like in tags)
![image…
-
```
What steps will reproduce the problem?
1.create a simple protobuf message, message CharTest{required string a=1}
2.create a protobuf instance, with a=
3. CharTest m CharTest.newBuilder().setA("my.…
-
```
What steps will reproduce the problem?
1.create a simple protobuf message, message CharTest{required string a=1}
2.create a protobuf instance, with a=
3. CharTest m CharTest.newBuilder().setA("my.…
-
```
What steps will reproduce the problem?
1. Send through an IPSMGW an SIP/SMS with source address set to alphanumeric
TON, see the attached trace.
2. Boghe client shows the originator address as 37…
-
```
OAuth for AppEngine for one, returns an authorization token with a '/'.
GenerateSignatureBase() does not url encode this parameter, and the access
token request fails as a result.
The correct …
-
```
OAuth for AppEngine for one, returns an authorization token with a '/'.
GenerateSignatureBase() does not url encode this parameter, and the access
token request fails as a result.
The correct …