I get this error when trying to import a repository: APPLICATION ERROR #plugin_SourceViewVC_run_svn shell_exec() failed to execute Subversion. Please use the "Back" button in your web browser to return to the previous page....

Setup: OS: Window Server 2016 (VPS) MantisBT version: 2.6 Database: Sql Server 2014 Express PHP: 7.1.9

Settings made in Source plugin configuration UI: SVN: Path to binary: C:\csvn\bin SVN: Command Arguments: Empty SVN: Trust All SSL certifcates: True SVN: Use Windows Start : True (tried both)

Trying to create Mantis-SVN-WebSVN(v2.3.3) installation. Every link to WebSVN creates unrendered template pages. In this patch I changed the url's from 'websvn/action.php?path=&repo=' form to 'websvn/repo/path?op=' form At least for now it works. The only link that works not as expected is 'url_changeset' - it should create the link in form '?op=comp&compare[]=${PATH}@${REV-1}&compare[]=${PATH}@${REV}' - right now it gives link to repository snapshot at specific revision.

Changed the descriptorspec for the stderr pipe to 'w' (it was 'a' but this seems only applicable when streaming to a file, not a pipe) Reversed the order in which the stderr and stdout pipes are read to get around an apparent bug in the proc_open

APPLICATION ERROR #401

Database query failed. Error received from database was #1292: Incorrect datetime value: '2012-12-04T11:11:04Z' for column 'timestamp' at row 1 for the query: INSERT INTO mantis_plugin_Source_changeset_table ( repo_id, revision, parent, branch, user_id, timestamp, author, message, info, ported, author_email, committer, committer_email, committer_id ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ).

Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.

Maybe Github API has been changed.

Import data (either latest or everything) fails. The reason is that (at present) list of all commits can't be gotten from "https://api.google.com/repos/user/repo/commits/". The last slash should be removed, i.e. the right url for list of all commits is "https://api.google.com/repos/user/repo/commits".

Tiny change in code could fix it.

Hey guys,

I'm not sure I understand what parameters to set in Update Repository view on Mantis.

What exactly should I specify in GitHub Application Client ID ? Should I create new OAuth app in https://github.com/settings/applications ? If yes, what call back url I'm supposed to specify ?

Thanks.

When fixing bugs, a not is added in public state, and this is hard coded.

I just hard coded it to private for my needs, but it would be nice to have this either use the default for adding bug notes, or eventually have it configurable through a new variable.

Installed everything, went through that insane setup process https://github.com/mantisbt-plugins/source-integration/blob/master/docs/CONFIGURING.SourceGithub.md Very last section "Import Everything" Retrieving master ... failed (Not Found).

Typical.

How do I fix this?

Why cant you just use webhooks?

We use using subversion (Collabnet Edge and with ViewVC) hosted on a Windows/IIS server, and MantisBT (ver 2.5) hosted on an Apache server, and want to hook up MantisBT to svn. Purpose: When a developer commits a change to svn, MantisBT should be notified and the ticket updated. We have installed the source integration plugins (Source, SourceSVN, and SourceViewVC). When configuring the Source plugin, there is a function "Create repository", but I do no not want to create a new repo but link to an existing. Grateful for any tips, have googled around without success.

Hi, I've installed the plugins on my Mantis and tried to integrate with GitHub. But I get the following error when importing data on a repository.

APPLICATION ERROR #401 Database query failed. Error received from database was #1048: Column 'revision' cannot be null for the query: INSERT INTO mantis_plugin_Source_changeset_table ( repo_id, revision, parent, branch, user_id, timestamp, author, message, info, ported, author_email, committer, committer_email, committer_id ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ).

Any help will be appreciated.

Thanks

[1]In contrast to plugin_lang_get/lang_get the paired plugin_lang_get_defaulted/lang_get_defaulted don't fallback to 'english' if a string isn't found for the current language. As I take some responsibility for that (eb25dfb), I suggest to replace plugin_lang_get_defaulted( $t_key, $t_key, t_vcs->basename ) with plugin_lang_get( $t_key, $t_vcs->basename ) [2]I would have preferred to change the underlying core lang_get_defaulted but a straightforward:

function lang_get_defaulted( $p_string, $p_default = null, $p_lang = null ) {
	$t_lang = $p_lang;

	if( null === $t_lang ) {
		$t_lang = lang_get_current();
	}

	# Now we'll make sure that the requested language is loaded
	lang_ensure_loaded( $t_lang );

	$t_string = lang_get( $p_string, $t_lang );
	if ( !is_blank( $t_string ) ) {
		return $t_string;
	} else {
		if( null === $p_default ) {
			return $p_string;
		} else {
			return $p_default;
		}
	}
}

Has some ugly drawbacks: [2.1]Two calls to plugin localized strings into core(?) [2.2]Empty label resolved to a php-page(?) And there might be others.

@dregad No probs with a PR for [1], but how to proceed with [2.x]? Currently all this probs got drawn into the kitchen sink.

Our SVN instance is configured using svn+ssh:// protocol; everyone connects using a public key. We use virtual users - everyone specifies the same linux user on the svn server, and the authorized_keys file on the server automatically maps the private key used to log in to the appropriate user using the --tunnel-user option. Normally, from the command line, we would use something like "svn checkout svn+ssh://SVN_USER@DOMAIN_NAME/project/trunk". On the web server, I've created a virtual user for Apache's user with read-only access to svn; using "sudo -u www-data svn ls SVN_PATH/@, I get a working listing of the remote repository, so mantis should work with it. I've tried configuring the URL similarly in SourceSVN, and get the error listed below. I've also tried omitting the user, and specifying it in the "svn user" section (leaving the password blank since we use keys), and that also fails (with a different less informative error).

I'm guessing that this isn't working because this is a fairly niche use of svn (we do this so we can have the repository externally available for remote work, without having to worry about credentials being guessed; normal user/password authentication is disabled), and to simplify deployment scripts on remote servers that pull from svn.

I've modified mantis a few times to fix issues and extend it, and am proficient in linux administration tasks, and am a senior full-stack software developer, so I'm ok with making code changes to make this work, but I wanted to see if anyone else had tried with a configuration like this, and I just don't have it set up correctly, or had pointers on where to start looking in the plugin to make this work right.

Error message when I try to use Import Latest Data, or Import Everything; happens immediately (I've replaced our svn user with SVN_USER below, and our domain name with DOMAIN_NAME):

APPLICATION ERROR #plugin_SourceSVN_svn_cmd

Subversion execution returned an error: "svn: E205000: Try 'svn help info' for more information svn: E205000: Syntax error parsing peg revision 'DOMAIN_NAME'; did you mean 'svn+ssh://SVN_USER@DOMAIN_NAME@'?". Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems >were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new >section.

I've a repo with 22 branches and obviously this is greater than Gitlab default -> 20. Please add at least add '&per_page=50' or may be '&per_page=100' when building the uri in the following function public function import_full( $p_repo ) {

# Always pull back full list of repos
$t_repoid = $p_repo->info['hub_repoid'];
$t_uri = $this->api_uri( $p_repo, "projects/$t_repoid/repository/branches" );

# My silly FIX !!! - fmancardi
$t_uri .= '&per_page=50';

may be there is a better solution. And maybe this '&per_page=xx' need to be added to other REST API call

Best regards

The Webhook delivery results in an HTTP 200 return code, but the response is actually a MantisBT error page: INTERNAL APPLICATION ERROR

Delivering the payload with $g_show_detailed_errors = ON; yields additional information

Client error: `GET https://api.github.com/rate_limit?per_page=100` resulted in a `401 Unauthorized` response:
{
"message": "Bad credentials",
"documentation_url": "https://docs.github.com/rest"
}

Stack trace

0	.../vendor/guzzlehttp/guzzle/src/Middleware.php	65	GuzzleHttp\Exception\RequestException	::	create	-
1	.../vendor/guzzlehttp/promises/src/Promise.php	204	GuzzleHttp\Middleware	::	GuzzleHttp\{closure}	-
2	.../vendor/guzzlehttp/promises/src/Promise.php	153	GuzzleHttp\Promise\Promise	::	callHandler	-
3	.../vendor/guzzlehttp/promises/src/TaskQueue.php	48	GuzzleHttp\Promise\Promise	::	GuzzleHttp\Promise\{closure}	-
4	.../vendor/guzzlehttp/promises/src/Promise.php	248	GuzzleHttp\Promise\TaskQueue	->	run	-
5	.../vendor/guzzlehttp/promises/src/Promise.php	224	GuzzleHttp\Promise\Promise	->	invokeWaitFn	-
6	.../vendor/guzzlehttp/promises/src/Promise.php	269	GuzzleHttp\Promise\Promise	->	waitIfPending	-
7	.../vendor/guzzlehttp/promises/src/Promise.php	226	GuzzleHttp\Promise\Promise	->	invokeWaitList	-
8	.../vendor/guzzlehttp/promises/src/Promise.php	62	GuzzleHttp\Promise\Promise	->	waitIfPending	-
9	.../vendor/guzzlehttp/guzzle/src/Client.php	182	GuzzleHttp\Promise\Promise	->	wait	-
10	.../vendor/guzzlehttp/guzzle/src/Client.php	95	GuzzleHttp\Client	->	request	-
11	.../plugins/SourceGithub/SourceGithub.php	506	GuzzleHttp\Client	->	__call	-
12	.../plugins/SourceGithub/SourceGithub.php	546	SourceGithubPlugin	->	api_get	-
13	.../plugins/SourceGithub/SourceGithub.php	720	SourceGithubPlugin	->	api_json_url	-
14	.../plugins/SourceGithub/SourceGithub.php	639	SourceGithubPlugin	->	import_commits	-
15	.../plugins/Source/Source.API.php	524	SourceGithubPlugin	->	commit	-
16	.../plugins/source-integration/Source/pages/checkin.php	86	SourceVCSWrapper	->	__call	-
17	.../plugin.php	74	-	-	include	<string>'/srv/plugins/source-integration/Source/pages/checkin.php'

The Guzzle RequestException should be caught and reported as a meaningful error.

Current use of print_small_button() generates a complex GET URL showing the form security token. It would be better to use print_form_button() so the token is handled as hidden form parameter.

Moreover multiple tokens are generated (one per issue), which is not efficient,

I'm currently trying to tune regular expressions for my repo and I found out that I cannot reparse commits for the whole repo, only do full import again. It would be nice to have such kind of button which will:

• Go for each commit in the repo
• Apply regexps to find linked issues
• Unlink not-found issues and link new ones

Maybe bullet about unlinking could be optional and available as parameter...