I get the following error when importing an SVN repository to git with svn2git:
fatal: EOF in data (285 bytes remaining)
Does anyone know what this error means?
This is caused by a segmentation fault, there is a branch/tag/ in your repository that is causing it to core.
To get the core files you will need to enable cores:
Uncomment this line in /etc/security/limits.conf
soft core unlimited
Run svn2git, it may take up to 2 hours to get the segmentation fault. Install gdb:
yum install gdb
Analyse the core:
gdb svn2git/svn-all-fast-export core.NNNN
Get a back trace, type:
bt
You should see the branch/tag which caused problems in the back trace. Exclude the branch from processing by updating your ruleset:
match /branches/broken_branch_name
end match
See issue opened with owner of svn2git here:
https://github.com/svn-all-fast-export/svn2git/issues/26
Or even easier, pstack <pid of svn2git> and you will see where it is stuck, then Ctrl + C, add the dud branch to your rule set and start svn2git again.
Related
I am doing the Pintos project on the side to learn more about operating systems. I had tons of devops trouble at first with it not running well on an 18.04 Ubuntu droplet. I am now running it on the VirtualBox image that UCCS tells students to download for pintos.
I finished project 1 and started to map out my solution to project 2. Following the instructions to create a file I ran
pintos-mkdisk filesys.dsk --filesys-size=2
pintos -- -f -q
but am getting error
Kernel PANIC at ../../threads/vaddr.h:87 in vtop(): assertion
`is_kernel_vaddr (vaddr)' failed.
I then tried running make check (all the tests). They are all failing for the same reason.
Am I missing something? Is there something I need to implement to fix this? I reread the instructions and didnt see anything?
Would appreciate help!
Thanks
I had a similar problem. My code for Project 1 ran fine, but I could not format the filesystem for Project 2.
The failure for me came from the following call chain:
thread_init() -> ... -> thread_schedule_tail() -> process_activate() -> pagedir_activate() -> vtop()
The problem is that init_page_dir is still NULL when pagedir_activate() is called. init_page_dir should have been initialized in paging_init() but this is called after thread_init().
The root cause was that my scheduler was being called too early, i.e. before the call to thread_start(). The reason for my problem was that I had built in a call to thread_yield() upon completion of every call to lock_release() which makes sense from a priority donation standpoint. Unfortunately, locks are used prior to the scheduler being ready! To fix this, I installed a flag called threading_started that bails in the first line of my thread_block() and thread_yield() functions if thread_start() has not yet been called.
Good luck!
I want to install phabricator-extensions-Sprint for phabricator. I followed the installation below:
To install the Sprint extension:
update your phabricator and libphutil to HEAD run git clone
https://github.com/wikimedia/phabricator-extensions-Sprint.git
/srv/phab/libext/sprint from the /srv/phab/phabricator/bin directory
run:
./config set load-libraries '{"sprint":"/srv/phab/libext/sprint/src"}'
But when I ran the Sprint in Application, I received the bug:
>>> UNRECOVERABLE FATAL ERROR <<<
Call to undefined method SprintListController::buildApplicationPage()
/opt/phabricator/libext/sprint/src/controller/SprintListController.php:46
┻━┻ ︵ ¯\_(ツ)_/¯ ︵ ┻━┻
I have to tried to do adding_new_classes but not effected.
Please help.
Sprint extension was recently broken by this commit in Phabricator:
https://secure.phabricator.com/rP2201c65eb73fb99b8625bea45c273d262f2c289f#19bb764c
The quick fix is to restore removed buildApplicationPage method by putting it into src/controller/SprintListController.php, it will fix the bug you describe.
However using Sprint extension looks like a questionable choice in the long run, given the problems discussed here:
https://phabricator.wikimedia.org/T90906
I am new Shogun user,besides, this is my first time to use SVN.(I think the problem is SVN not Shogun)
those are the environment what I use:
Windows 10
Shogun 4.0.0
TortoiseSVN-1.9.3.27038-x64-svn-1.9.3;
VisualSVN-5.1.3;
VisualSVN-Server-3.5.1-x64;
VS 2013
Now I am in trouble when I want to get started an simple example of Shogun(copy in Documentation) as follow:
#include <shogun/base/init.h>
using namespace shogun;
int main(int argc, char** argv)
{
init_shogun();
exit_shogun();
return 0;
}
then, I try to compile it in Vs 2013, it tell me:
1> Generating version header
3> Building Custom Rule E:/shogun/CMakeLists.txt
3> CMake does not need to re-run because E:\shogun-configure\CMakeFiles\generate.stamp is up-to-date.
3> Creating directories for 'MSIntTypes'
3> Performing download step (SVN checkout) for 'MSIntTypes'
3> svn: E170013: Unable to connect to a repository at URL ' http://msinttypes.googlecode.com/svn/trunk '
3> svn: E175012: Connection timed out
3> C:\ProgramFiles(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(170,5): error MSB6006:
"cmd.exe" has exited. code is 1.
Then, I considerd that maybe some problems with SVN, I try to checkout some respositories:
At first, I try to checkout an respositories what I create myself:'_http://burningbear:8443/!/#new_rep', it can be checkout normally.
Then I try to chekout the respository:'_http ://msinttypes.googlecode.com/svn/trunk', but the Tortoise just not responding for a long time, then it reply me that:
Command: Checkout from _http://msinttypes.googlecode.com/svn/trunk, revision HEAD, Fully recursive, Externals included
Error: Unable to connect to a repository at URL
Error: '_http://msinttypes.googlecode.com/svn/trunk'
Error: Error running context: 你的主机中的软件中止了一个已建立的连接。(what I use is Chinese,it means "the software in your host stop an connected connection")
In China, We can not access googlecode unless we use VPN, so I change the server, to enable Proxy Server, the following is my setting:
Server address: 127.0.0.1
Port: 8087
Then I try to checkout again as:
When I check out _http://msinttypes.googlecode.com/svn/trunk
Checkout from _http://msinttypes.googlecode.com/svn/trunk, revision HEAD, Fully recursive, Externals included
Unable to connect to a repository at URL'_http://msinttypes.googlecode.com/svn/trunk'
The HTTP method 'OPTIONS' is not allowed on '/svn/trunk'
When I update the repositories what I have checkout before(URL is :_http://burningbear:8443/!/#new_rep). It move slowly, I spend about half hour, SVN tell me: "2 kBytes transferred in 20 minutes and 2 seconds"
Command: Update
Updating: E:\test2
Error: Unable to connect to a repository at URL 'https://burningbear:8443/svn/new_rep'
Error: Connection timed out
Completed!:
Now, I don't know what's the problem. It take me several days and I still can not solve it. Please help me! Thank you in advanced!
(I can not post more than 2 links now, so all of URL above I add an '_' mark before 'http')
Currently there's no way to compile natively shogun on Windows unfortunately. Although your problem seems to be unrelated, and it fails with svn, which is weird because the official repo of the shogun is using git: http://github.com/shogun-toolbox/shogun/
worked on the weekend on the native Windows support of shogun, you can find it in the feature/windows branch of the official repository: https://github.com/shogun-toolbox/shogun/tree/feature/windows
UPDATE: the feature branch has been merged into develop branch. from now on shogun can be compiled on windows natively.
Google Code is not available anymore: http://msinttypes.googlecode.com/svn/trunk. That's why the tool fails to access googlecode.com.
make wthis this manual
http://wireless.kernel.org/en/users/Documentation/hostapd
with this config file
interface=wlan2
bridge=br0
driver=nl80211
ssid=SupaAP
country_code=RU
hw_mode=g
channel=5
preamble=1
macaddr_acl=0
auth_algs=1
logger_syslog=-1
logger_syslog_level=3
logger_stdout=-1
logger_stdout_level=2
ignore_broadcast_ssid=0
ieee80211n=1
ht_capab=[SHORT-GI-20][RX-STBC1]
wmm_enabled=1
and i have error
oot#Cubian:/home/cubie/wif/hostapd-2.1/hostapd# ./hostapd /etc/hostapd/hostapd.conf
Configuration file: /etc/hostapd/hostapd.conf
Line 16: unknown configuration item 'ieee80211n'
Line 17: unknown configuration item 'ht_capab'
2 errors found in configuration file '/etc/hostapd/hostapd.conf'
Failed to set up interface with /etc/hostapd/hostapd.conf
Failed to initialize interfac
in old version i dont have thsi error
It appears that the problem is that hostapd 2.1 is now treating an error it had differently.
This is reproducible on Ubuntu desktop versions, as the resource (WLAN) is busy.
If one turns off the programs that are accessing the resource, hostapd has a chance to grab it and work.
In Ubuntu desktop 14.04 beta, a solution is to turn off the programs that are using the wlan in question.
This worked for me:
sudo nmcli nm wifi off
sudo rfkill unblock wlan
then hostapd can start normally from command line. Of course, if you want hostapd to start on boot you must insure that the network manager is not grabbing the resource ahead of time.
SOLVED
in compile conf i uncomment string
CONFIG_IEEE80211N=y
I have found this link explaining the cause of the error and how to solve it.
https://bugs.archlinux.org/task/20269
Also I have found this other link http://blog.mirjamali.com/en/IT/Linux/hostapd which I followed and it is working with me check the configuration part.
My OS is ubuntu 12.4
start your hostapd with
hostapd -dd /etc/hostapd/hostapd.conf
you will get more information for diagnostics. In which old version you did not get the error? Did you update hostapd? Or changed your wifi adapter? which distri you are using?
http://hostap.epitest.fi/cgit/hostap/plain/hostapd/hostapd.conf
there is written how the ieee80211n settings are. for me i cant see an error.
if you remove the both lines, the ap is starting correctly?
When trying to commit to my SVN repository, I got the following error:
Working copy 'Z:\prace-pj\projects\other\CopyRT' locked.
So I run the clean up command and then the commit succeeded, but at the end of the response message, there was the following error:
Error bumping revisions post-commit (details follow):
disk I/O error, executing statement 'RELEASE s11'
Now when I try to e.g. update the repository, it says that it is stil locked. When I clean up and try to update again, I get an error like this:
disk I/O error, executing statement 'RELEASE s2'
sqlite: disk I/O error
What should I do to fix this?
For others reference, I just had this same error and found that one of my log files was taking up all my space (and could not write to the HDD because there was no free space).
Run (to make sure you have enough disk space)
df -h
Then I just needed to run:
svn cleanup
This resolved the error for me.
have you tried:
svn unlock --force path/to/workingcopy
? Seems it can be pointed at a url if the problem is in the repository itself... I've only used an unlock operation via the tortoise gui before, but I assume it just wraps the svn command anyway.
hope that helps