Fsch contains a parse error

fsch contains a parse error

www.linuxquestions.org › questions › debian-26 › [solved]-what-in-my-et. This is the case, even when the corresponding blob object has been included on Note that the error message issued by the config parser is still present. I have a self-hosted gitlab instance and suddenly one of my projects #435] ERROR --: xxx/xxx: Could not fsck repository: dangling blob. fsch contains a parse error

Thematic video

How to Fix Wordpress Parse Error : Syntax Error unexpected ' ' in wp-includes/ functions.php

Fsch contains a parse error - theme

nested] 31+ messages in thread
*Re: [PATCH] fsck: check skiplist for object in fsck_blob() 2018-07-11 19:31 ` Ramsay Jones@ 2018-07-13 19:37 ` Ramsay Jones 2018-07-13 19:41 ` Jeff King 2018-07-13 19:38 ` Jeff King1 sibling, 1 reply; 31+ messages in thread From: Ramsay Jones @ 2018-07-13 19:37 UTC (permalink / raw) To: Jeff King; +Cc: Junio C Hamano, Jason, GIT Mailing-list On 11/07/18 20:31, Ramsay Jones wrote: > On 07/07/18 02:32, Jeff King wrote: [snip] >> Hmm, we seem to have "info" these days, so maybe that would do what I >> want. I.e., I wonder if the patch below does everything we'd want. It's >> late here and I probably won't get back to this until Monday, but you >> may want to play with it in the meantime. > > Sorry, I've been busy with other things and have not had the > time to try the patch below (still trying to catch up with > the mailing-list emails!). > >> diff --git a/fsck.c b/fsck.c >> index 48e7e36869..0b0003055e 100644 >> --- a/fsck.c >> +++ b/fsck.;-) > > Sorry for not testing the patch. OK, so I found some time to test this tonight. It is not good news (assuming that I haven't messed up the testing, of course). :( On top of 'pu' (@9026cfc855), I reverted commit d4c5675233 ("fsck: silence stderr when parsing .gitmodules", 2018-06-28) and added the patch given below. Unfortunately, the final test fails, thus: $ cd t $ ./t7415-submodule-names.sh ok 1 - check names ok 2 - create innocent subrepo ok 3 - submodule add refuses invalid names ok 4 - add evil submodule ok 5 - add other submodule ok 6 - clone evil superproject ok 7 - fsck detects evil superproject ok 8 - transfer.fsckObjects detects evil superproject (unpack) ok 9 - transfer.fsckObjects detects evil superproject (index) ok 10 - create oddly ordered pack ok 11 - transfer.fsckObjects handles odd pack (unpack) ok 12 - transfer.fsckObjects handles odd pack (index) ok 13 - index-pack --strict works for non-repo pack ok 14 - fsck detects symlinked .gitmodules file ok 15 - fsck detects non-blob .gitmodules ok 16 - fsck detects corrupt .gitmodules ok 17 - push warns about corrupt .gitmodules not ok 18 - push rejects corrupt .gitmodules (policy) # # rm -rf dst.git && # git init --bare dst.git && # git -C dst.git config transfer.fsckObjects true && # git -C dst.git config fsck.gitmodulesParse error && # test_must_fail git -C corrupt push ../dst.git HEAD 2>output && # grep gitmodulesParse output && # test_i18ngrep ! "bad config" output # # failed 1 among 18 test(s) 1..18 $ i.e. the test_must_fail doesn't! ;-) I have to go out now, but I will hopefully take a look at this again tomorrow. (Do the test additions look OK?) ATB, Ramsay Jones -- >8 -- Subject: [PATCH] WIP: try jeff's last patch Signed-off-by: Ramsay Jones <[email protected]> --- fsck.c

To copy a file from a source on the router to a destination on the router, specify a source locationnode-id and a destination locationnode-id. To copy the file to all nodes, use the locationall keywords.

In the alias syntax for the ftp:, rcp:, and tftp: keywords, the location is either an IP address or a hostname. The filename is specified relative to the directory used for file transfers.

When no alias is specified, the networking device looks for a file in the current directory. To view the current directory, enter the pwd command.


Note


During processing of the copy command, you might see the “C” character. For all files being copied, “C” indicates that the copy process is taking place. The entire copying process might take several minutes and differs from protocol to protocol and from network to network.


Table 1 describes the network protocols supported by Cisco IOS XR software.

Prefix

Name

Description

tftp:

Trivial File Transfer Protocol

is a simplified version of FTP that allows files to be transferred from one computer to another over a network, usually without the use of client authentication (for example, username and password).

ftp:

File Transfer Protocol

is an application protocol, part of the TCP/IP protocol stack, and is used for transferring files between network nodes. FTP requires a username and password.

rcp:

Remote Copy Protocol

The rcp protocol allows users to copy files to and from a file system residing on a remote host or server on the network. The rcp protocol uses TCP to ensure the reliable delivery of data. The rcp protocol downloads require a username.

Additional usage guidelines are in the following sections.

Some combinations of source and destination are invalid. Specifically, you cannot copy the following:


  • From a running configuration to a running configuration

  • From a network device to a network device (for example, copyftp:rcp:)

is a simplified version of FTP that allows files to be transferred from one computer to another over a network, usually without the use of client authentication (for example, username and password).

The syntax is as follows:

copytftp://hostname /ipaddress/directory-pathpie nametarget-device [location {node-id all}]

Example: RP/0/0/CPU0:router#
  • An “anonymous” username and password. The anonymous password is “[email protected] address,” where “ip address” is the IP address of the local networking device.

  • A password “[email protected]” formed by the networking device. The variable “username” is the username associated with the current session, “iosname” is the configured hostname, and “domain” is the domain of the networking device.

  • The username and password must be associated with an account on the FTP server. If you are writing to the network server, the FTP server must be properly configured to accept the FTP write request from the user on the networking device.

    If the network server has a directory structure, the configuration file or image is written to or copied from the directory associated with the username on the network server. For example, if the system image resides in the home directory of a user on the network server, specify the name of that user as the remote username.

    Refer to the documentation for your FTP server for more details.

    The rcp protocol requires a username upon each request. When you copy a configuration file or image between the networking device and an rcp server, the Cisco IOS XR software sends the first valid username in the following list:


    1. The remote username specified in the copy command, if one is specified.

    2. The username set by the rcpclientusername command, if the command is configured.

    3. The networking device hostname.

    For the rcp copy request to process successfully, an account must be defined on the network server for the remote username. If the network administrator of the destination server did not establish an account for the remote username, this command does not run successfully. If the network server has a directory structure, the configuration file or image is written to or copied from the directory associated with the remote username on the network server. For example, if the system image resides in the home directory of a user on the network server, specify the name of that user as the remote username.

    If you are writing to the network server, the rcp server must be properly configured to accept the rcp write request from the user on the networking device. For UNIX systems, add an entry to the .rhosts file for the remote user on the rcp server. Suppose the networking device contains the following configuration lines:

    hostname Rtr1 ip rcp remote-username User0

    If the IP address of the networking device translates to company.com, then the .rhosts file for User0 on the rcp server should contain the following line:

    company.com Rtr1

    See the documentation for your rcp server for more details.

    If you are using a personal computer as a file server, the computer must support remote shell (rsh) protocol.

    Use the xml-schema keyword to obtain the most up-to-date XML schemas (.xsd files) from the router. Using this keyword is useful to prevent the use of outdated schemas in the event that router software updates include schema updates. The tar ball file includes all active schema files. It does not include schemas that are activated by specific package installation envelopes (PIEs) if those PIEs are not installed and activated on the router.

    When you use the copy command to copy a configuration file to the running-config destination, the configuration in the file is applied to the running configuration of the system. This is a configuration operation. By default, the copy is carried out in a best-effort manner. This means that if some configuration lines from the file cannot be applied, the remaining configuration is still integrated into the system. In this case, a partial configuration is committed. When the atomic keyword is used, partial configurations are not committed. This means that even if one error occurs in the parsing or committing phase, no changes are made to the system. To view any errors when applying the configuration, use the showconfigurationfailed command.

    Task ID

    Task ID

    Operations

    filesystem

    execute

    Examples

    The following example shows how to copy a file from a FTP server to disk1:

    RP/0/0/CPU0:router#

    The following example shows how to copy a file from an rcp server to disk1:

    RP/0/0/CPU0:router#

    The following example shows how to copy a file from a TFTP server to disk1:

    RP/0/0/CPU0:router#

    Related Commands

    Command

    Description

    cd

    Changes the default directory or file system.

    dir

    Displays the contents of a file system.

    show configuration failed (config)

    Displays information about a configuration that failed during the last commit.