-
### Feature Description
We recently decided to move to a new issue tracker but the git repository is full of numeric issue tracker numbers, like `#1012`.
In order to distinguish, in history, between…
-
## Description Set the context.
This app is used in a clinical context, which mean patient names are usually saved in full. However, some legal names containing non-alphanumeric characters are not all…
-
I think it would make more sense to change our current mito haplogroup field to two separate drop downs and an alphanumeric field because it does not accurately reflect the haplogroup data we get. We …
-
```
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 …
-
```
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 …
-
```
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…
-
```
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 …