{"thread":{"id":"58388","subject":"[PATCH] t1800: correct test to handle Cygwin","startedAt":"2022-09-01T17:58:03Z","lastAt":"2022-09-15T08:52:08Z","messageCount":10,"participants":["Adam Dinwoodie","Junio C Hamano","Đoàn Trần Công Danh","Johannes Schindelin","rsbecker@nexbridge.com"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"462477","messageId":"20220901173942.abolcr4aa5gixncm@lucy.dinwoodie.org","threadId":"58388","inReplyTo":null,"subject":"[PATCH] t1800: correct test to handle Cygwin","fromName":"Adam Dinwoodie","fromEmail":"adam@dinwoodie.org","sentAt":"2022-09-01T17:39:42Z","receivedAt":"2022-09-01T17:58:03Z","isPatch":true,"sender":{"key":"adam@dinwoodie.org","avatar":"https://avatars.githubusercontent.com/u/1397507?v=4"},"body":"On Cygwin, when failing to spawn a process using start_command, Git\noutputs the same error as on Linux systems, rather than using the\nGIT_WINDOWS_NATIVE-specific error output. The WINDOWS test prerequisite\nis set in both Cygwin and native Windows environments, which means it's\nnot appropriate to use to anticipate the error output from\nstart_command. Instead, use the MINGW test prerequisite, which is only\nset for Git in native Windows environments, and not for Cygwin.\n\nSigned-off-by: Adam Dinwoodie \n---\n\nThe job of setting Cygwin up to get Git CI builds, either as part of the\nmain CI builds or as something using separate automation, is rapidly\nrising up my when-I-have-the-time to-do list...\n\n t/t1800-hook.sh | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/t/t1800-hook.sh b/t/t1800-hook.sh\nindex 64096adac7..fae8b2faf9 100755\n--- a/t/t1800-hook.sh\n+++ b/t/t1800-hook.sh\n@@ -159,7 +159,7 @@ test_expect_success 'git hook run a hook with a bad shebang' '\n \t# TODO: We should emit the same (or at least a more similar)\n \t# error on Windows and !Windows. See the OS-specific code in\n \t# start_command()\n-\tif test_have_prereq !WINDOWS\n+\tif test_have_prereq !MINGW\n \tthen\n \t\tcat >expect <<-\\EOF\n \t\tfatal: cannot run bad-hooks/test-hook: ...\n-- \n2.37.2\n"},{"id":"462480","messageId":"xmqqedwv9c9f.fsf@gitster.g","threadId":"58388","inReplyTo":"20220901173942.abolcr4aa5gixncm@lucy.dinwoodie.org","subject":"Re: [PATCH] t1800: correct test to handle Cygwin","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-09-01T18:32:12Z","receivedAt":"2022-09-01T18:32:17Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Adam Dinwoodie writes:\n\n> On Cygwin, when failing to spawn a process using start_command, Git\n> outputs the same error as on Linux systems, rather than using the\n> GIT_WINDOWS_NATIVE-specific error output. The WINDOWS test prerequisite\n> is set in both Cygwin and native Windows environments, which means it's\n> not appropriate to use to anticipate the error output from\n> start_command. Instead, use the MINGW test prerequisite, which is only\n> set for Git in native Windows environments, and not for Cygwin.\n>\n> Signed-off-by: Adam Dinwoodie \n> ---\n>\n> The job of setting Cygwin up to get Git CI builds, either as part of the\n> main CI builds or as something using separate automation, is rapidly\n> rising up my when-I-have-the-time to-do list...\n\nI added a few who probably are more familiar with Windows situation\nthan those already CC'ed.\n\nA quick grep in the test directory\n\n $ git grep '\\\" t\n\nhits this one and t7450-bad-git-dotfiles.sh and nothing else, but\nwe do have quite a many hits of \"test_have_prereq !MINGW,!CYGWIN\".\n\nI guess it depends on how common various \"glitches\" MINGW and CYGWIN\nprerequistes are trying to cover, but I am wondering if we are\nhelped by having three (i.e. MINGW, CYGWIN, and WINDOWS)\nprerequisites, or does WINDOWS as a separate prerequisite\ncontributes more to the confusion (and if so, if it is a good idea\nto remove and use only MINGW and CYGWIN prerequistes).\n\nOne possible roadblock is that it is not easy to express \"MINGW or\nCYGWIN\" in the prerequisite syntax and WINDOWS prerequisite is an\neasy way to fill that gap.\n\nIn any case, thanks for a fix. Will queue.\n\n> t/t1800-hook.sh | 2 +-\n> 1 file changed, 1 insertion(+), 1 deletion(-)\n>\n> diff --git a/t/t1800-hook.sh b/t/t1800-hook.sh\n> index 64096adac7..fae8b2faf9 100755\n> --- a/t/t1800-hook.sh\n> +++ b/t/t1800-hook.sh\n> @@ -159,7 +159,7 @@ test_expect_success 'git hook run a hook with a bad shebang' '\n> \t# TODO: We should emit the same (or at least a more similar)\n> \t# error on Windows and !Windows. See the OS-specific code in\n> \t# start_command()\n> -\tif test_have_prereq !WINDOWS\n> +\tif test_have_prereq !MINGW\n> \tthen\n> \t\tcat >expect <<-\\EOF\n> \t\tfatal: cannot run bad-hooks/test-hook: ...\n"},{"id":"462501","messageId":"YxFinAJ2NeKiHaS8@danh.dev","threadId":"58388","inReplyTo":"xmqqedwv9c9f.fsf@gitster.g","subject":"Re: [PATCH] t1800: correct test to handle Cygwin","fromName":"Đoàn Trần Công Danh","fromEmail":"congdanhqx@gmail.com","sentAt":"2022-09-02T01:55:40Z","receivedAt":"2022-09-02T01:55:50Z","isPatch":true,"sender":{"key":"congdanhqx@gmail.com","avatar":"https://avatars.githubusercontent.com/u/42673067?v=4"},"body":"On 2022-09-01 11:32:12-0700, Junio C Hamano wrote:\n> In any case, thanks for a fix. Will queue.\n> \n> > t/t1800-hook.sh | 2 +-\n> > 1 file changed, 1 insertion(+), 1 deletion(-)\n> >\n> > diff --git a/t/t1800-hook.sh b/t/t1800-hook.sh\n> > index 64096adac7..fae8b2faf9 100755\n> > --- a/t/t1800-hook.sh\n> > +++ b/t/t1800-hook.sh\n> > @@ -159,7 +159,7 @@ test_expect_success 'git hook run a hook with a bad shebang' '\n> > \t# TODO: We should emit the same (or at least a more similar)\n> > \t# error on Windows and !Windows. See the OS-specific code in\n\nPlease also change the comment here too.\nI'm not sure what should be put in the comment here, though.\nMaybe on MINGW and other platforms?\n\n> > \t# start_command()\n> > -\tif test_have_prereq !WINDOWS\n> > +\tif test_have_prereq !MINGW\n> > \tthen\n> > \t\tcat >expect <<-\\EOF\n> > \t\tfatal: cannot run bad-hooks/test-hook: ...\n\n-- \nDanh\n"},{"id":"462524","messageId":"4s7o04s9-3052-rqq6-584n-978p9758p580@tzk.qr","threadId":"58388","inReplyTo":"20220901173942.abolcr4aa5gixncm@lucy.dinwoodie.org","subject":"Re: [PATCH] t1800: correct test to handle Cygwin","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2022-09-02T12:22:41Z","receivedAt":"2022-09-02T12:27:17Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Adam,\n\nOn Thu, 1 Sep 2022, Adam Dinwoodie wrote:\n\n> On Cygwin, when failing to spawn a process using start_command, Git\n> outputs the same error as on Linux systems, rather than using the\n> GIT_WINDOWS_NATIVE-specific error output.\n\nGiven this explanation, I would have expected...\n\n> The WINDOWS test prerequisite is set in both Cygwin and native Windows\n> environments, which means it's not appropriate to use to anticipate the\n> error output from start_command. Instead, use the MINGW test\n> prerequisite, which is only set for Git in native Windows environments,\n> and not for Cygwin.\n>\n> Signed-off-by: Adam Dinwoodie \n> ---\n>\n> The job of setting Cygwin up to get Git CI builds, either as part of the\n> main CI builds or as something using separate automation, is rapidly\n> rising up my when-I-have-the-time to-do list...\n>\n> t/t1800-hook.sh | 2 +-\n> 1 file changed, 1 insertion(+), 1 deletion(-)\n>\n> diff --git a/t/t1800-hook.sh b/t/t1800-hook.sh\n> index 64096adac7..fae8b2faf9 100755\n> --- a/t/t1800-hook.sh\n> +++ b/t/t1800-hook.sh\n> @@ -159,7 +159,7 @@ test_expect_success 'git hook run a hook with a bad shebang' '\n> \t# TODO: We should emit the same (or at least a more similar)\n> \t# error on Windows and !Windows. See the OS-specific code in\n> \t# start_command()\n> -\tif test_have_prereq !WINDOWS\n> +\tif test_have_prereq !MINGW\n\n... this to be `test_have_prereq !WINDOWS || test_have_prereq CYGWIN`\ninstead.\n\nAt least it is my understanding that Cygwin is the special case of the\nspecial case that is Windows.\n\nThat is, if most scenarios on Windows were behaving like Cygwin and the\nmingw-w64 build was the odd duck, I would understand to restrict this only\nto MINGW. But I think it is the other way around: with Cygwin, _despite_\nbeing on Windows, we see this Linux-like behavior.\n\nCiao,\nDscho\n\n> \tthen\n> \t\tcat >expect <<-\\EOF\n> \t\tfatal: cannot run bad-hooks/test-hook: ...\n> --\n> 2.37.2\n>\n"},{"id":"462759","messageId":"xmqqy1uusyez.fsf@gitster.g","threadId":"58388","inReplyTo":"4s7o04s9-3052-rqq6-584n-978p9758p580@tzk.qr","subject":"Re: [PATCH] t1800: correct test to handle Cygwin","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-09-07T20:49:08Z","receivedAt":"2022-09-07T20:49:12Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin writes:\n\n>> @@ -159,7 +159,7 @@ test_expect_success 'git hook run a hook with a bad shebang' '\n>> \t# TODO: We should emit the same (or at least a more similar)\n>> \t# error on Windows and !Windows. See the OS-specific code in\n>> \t# start_command()\n>> -\tif test_have_prereq !WINDOWS\n>> +\tif test_have_prereq !MINGW\n>\n> ... this to be `test_have_prereq !WINDOWS || test_have_prereq CYGWIN`\n> instead.\n\nMy understanding is that there are CYGWIN and MINGW prereqs that are\nmutually exclusive (if you are on MINGW you cannot be on CYGWIN and\nvice versa), and WINDOWS is a short-hand for \"we are either on MINGW\nor CYGWIN\", and I am not sure if it clarifies anything to rewrite\n\"we do not want to be on MINGW to run these tests\" to \"anything non\nWindows is fine, by the way, CYGWIN is also OK\".\n\nIf we are planning to add another variant that falls into umbrella\nWINDOWS that is not CYGWIN, and that new variant falls short of the\nrequirement of the tests in this script just like MINGW does, then\nthe suggested rewrite does make quite a lot of sense. There would\nbe not just two but more variants in Windows family, and if Cygwin\nis the odd man out, then the rewritten one would convey that more\nclearly. But with only two, as long as everybody understands what\nMINGW is, I think \"this part does not work on MINGW\" is more concise\nand clear.\n\nAs Đoàn Trần Công Danh pointed out, the TODO: comment may need to be\nupdated. For future-proofing, perhaps \"a more similar) error on all\nplatforms.\" would be appropriate.\n\nThanks.\n"},{"id":"462761","messageId":"001301d8c2fc$78dc4bc0$6a94e340$@nexbridge.com","threadId":"58388","inReplyTo":"xmqqy1uusyez.fsf@gitster.g","subject":"RE: [PATCH] t1800: correct test to handle Cygwin","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2022-09-07T20:57:35Z","receivedAt":"2022-09-07T20:58:09Z","isPatch":true,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On September 7, 2022 4:49 PM, Junio C Hamano wrote:\n>Johannes Schindelin writes:\n>\n>>> @@ -159,7 +159,7 @@ test_expect_success 'git hook run a hook with a bad\n>shebang' '\n>>> \t# TODO: We should emit the same (or at least a more similar)\n>>> \t# error on Windows and !Windows. See the OS-specific code in\n>>> \t# start_command()\n>>> -\tif test_have_prereq !WINDOWS\n>>> +\tif test_have_prereq !MINGW\n>>\n>> ... this to be `test_have_prereq !WINDOWS || test_have_prereq CYGWIN`\n>> instead.\n>\n>My understanding is that there are CYGWIN and MINGW prereqs that are\n>mutually exclusive (if you are on MINGW you cannot be on CYGWIN and vice\n>versa), and WINDOWS is a short-hand for \"we are either on MINGW or CYGWIN\",\n>and I am not sure if it clarifies anything to rewrite \"we do not want to be on\n>MINGW to run these tests\" to \"anything non Windows is fine, by the way,\n>CYGWIN is also OK\".\n>\n>If we are planning to add another variant that falls into umbrella WINDOWS that is\n>not CYGWIN, and that new variant falls short of the requirement of the tests in\n>this script just like MINGW does, then the suggested rewrite does make quite a lot\n>of sense. There would be not just two but more variants in Windows family, and if\n>Cygwin is the odd man out, then the rewritten one would convey that more\n>clearly. But with only two, as long as everybody understands what MINGW is, I\n>think \"this part does not work on MINGW\" is more concise and clear.\n>\n>As Đoàn Trần Công Danh pointed out, the TODO: comment may need to be\n>updated. For future-proofing, perhaps \"a more similar) error on all platforms.\"\n>would be appropriate.\n\nI think this is the same as I reported under [BUG] t1800: Fails for error text comparison, which somehow Outlook associated with a different thread. NonStop has the same issue with error messages not being consistent across platforms.\n\n-Randall\n\n"},{"id":"463003","messageId":"CA+kUOa=DP6c417ZXXtxsJuyqJgpLZeAyr4URQPtMs0JhH1zVWQ@mail.gmail.com","threadId":"58388","inReplyTo":"xmqqy1uusyez.fsf@gitster.g","subject":"Re: [PATCH] t1800: correct test to handle Cygwin","fromName":"Adam Dinwoodie","fromEmail":"adam@dinwoodie.org","sentAt":"2022-09-13T21:08:10Z","receivedAt":"2022-09-13T21:08:47Z","isPatch":true,"sender":{"key":"adam@dinwoodie.org","avatar":"https://avatars.githubusercontent.com/u/1397507?v=4"},"body":"On Wed, 7 Sept 2022 at 21:49, Junio C Hamano wrote:\n>\n> Johannes Schindelin writes:\n>\n> >> @@ -159,7 +159,7 @@ test_expect_success 'git hook run a hook with a bad shebang' '\n> >> # TODO: We should emit the same (or at least a more similar)\n> >> # error on Windows and !Windows. See the OS-specific code in\n> >> # start_command()\n> >> - if test_have_prereq !WINDOWS\n> >> + if test_have_prereq !MINGW\n> >\n> > ... this to be `test_have_prereq !WINDOWS || test_have_prereq CYGWIN`\n> > instead.\n>\n> My understanding is that there are CYGWIN and MINGW prereqs that are\n> mutually exclusive (if you are on MINGW you cannot be on CYGWIN and\n> vice versa), and WINDOWS is a short-hand for \"we are either on MINGW\n> or CYGWIN\", and I am not sure if it clarifies anything to rewrite\n> \"we do not want to be on MINGW to run these tests\" to \"anything non\n> Windows is fine, by the way, CYGWIN is also OK\".\n>\n> If we are planning to add another variant that falls into umbrella\n> WINDOWS that is not CYGWIN, and that new variant falls short of the\n> requirement of the tests in this script just like MINGW does, then\n> the suggested rewrite does make quite a lot of sense. There would\n> be not just two but more variants in Windows family, and if Cygwin\n> is the odd man out, then the rewritten one would convey that more\n> clearly. But with only two, as long as everybody understands what\n> MINGW is, I think \"this part does not work on MINGW\" is more concise\n> and clear.\n\nThis is definitely how I was thinking about things. I've no particular\nobjection to taking some other approach, but until/unless there are a\nwider variety of Windows variants, it seems like doing so would cause\nmore confusion, not less.\n\nThe only caveat is the \"as long as everybody understands what MINGW\nis\" part. This is well beyond the scope of this small patch, but I\nthink \"MINGW\" is probably needlessly opaque these days. It makes sense\ngiven the history of Git for Windows, but it's not a term many people\nare likely to be familiar with unless they've already been playing\naround with the MinGW/Cygwin environments, and I'm not sure that's a\nuseful prerequisite for folk to be able to contribute to Git. I'm not\nsure what a better solution here might be; maybe retire \"MINGW\" and\nredefine \"WINDOWS\" to take its place, with current uses of \"WINDOWS\"\nbeing replaced with \"WINDOWS || CYGWIN\"?\n\n> As Đoàn Trần Công Danh pointed out, the TODO: comment may need to be\n> updated. For future-proofing, perhaps \"a more similar) error on all\n> platforms.\" would be appropriate.\n\nI'll respin with some updated comments shortly…\n"},{"id":"463004","messageId":"xmqq8rmn7ydk.fsf@gitster.g","threadId":"58388","inReplyTo":"CA+kUOa=DP6c417ZXXtxsJuyqJgpLZeAyr4URQPtMs0JhH1zVWQ@mail.gmail.com","subject":"Re: [PATCH] t1800: correct test to handle Cygwin","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-09-13T21:33:43Z","receivedAt":"2022-09-13T21:33:50Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Adam Dinwoodie writes:\n\n> ... It makes sense\n> given the history of Git for Windows, but it's not a term many people\n> are likely to be familiar with unless they've already been playing\n> around with the MinGW/Cygwin environments, and I'm not sure that's a\n> useful prerequisite for folk to be able to contribute to Git. I'm not\n> sure what a better solution here might be; maybe retire \"MINGW\" and\n> redefine \"WINDOWS\" to take its place, with current uses of \"WINDOWS\"\n> being replaced with \"WINDOWS || CYGWIN\"?\n\nIt sounds more like \"the world would've could've been a better place\nif we did X\", which is too late. As a non-Windows person, I think\nthe current approach is OK that assumes that those who write and\nread to understand our tests can answer the question: \"You're on\nWindows? There are MINGW or CYGWIN, which one do you have?\"\n\n>> As Đoàn Trần Công Danh pointed out, the TODO: comment may need to be\n>> updated. For future-proofing, perhaps \"a more similar) error on all\n>> platforms.\" would be appropriate.\n>\n> I'll respin with some updated comments shortly…\n\nThanks.\n"},{"id":"463034","messageId":"20220915075717.425673-1-adam@dinwoodie.org","threadId":"58388","inReplyTo":"20220901173942.abolcr4aa5gixncm@lucy.dinwoodie.org","subject":"[PATCH v2] t1800: correct test to handle Cygwin","fromName":"Adam Dinwoodie","fromEmail":"adam@dinwoodie.org","sentAt":"2022-09-15T07:57:17Z","receivedAt":"2022-09-15T07:57:26Z","isPatch":true,"sender":{"key":"adam@dinwoodie.org","avatar":"https://avatars.githubusercontent.com/u/1397507?v=4"},"body":"On Cygwin, when failing to spawn a process using start_command, Git\noutputs the same error as on Linux systems, rather than using the\nGIT_WINDOWS_NATIVE-specific error output. The WINDOWS test prerequisite\nis set in both Cygwin and native Windows environments, which means it's\nnot appropriate to use to anticipate the error output from\nstart_command. Instead, use the MINGW test prerequisite, which is only\nset for Git in native Windows environments, and not for Cygwin.\n\nSigned-off-by: Adam Dinwoodie \nHelped-by: Đoàn Trần Công Danh \n---\n\nWith apologies to folk receiving this multiple times; it looks like my\nSMTP setup was causing problems for some servers, and while the mails\nseemed to be arriving with me, they didn't seem to be appearing at\nhttps://public-inbox.org/git/?q=t1800\n\n t/t1800-hook.sh | 6 +++---\n 1 file changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/t/t1800-hook.sh b/t/t1800-hook.sh\nindex 64096adac7..43fcb7c0bf 100755\n--- a/t/t1800-hook.sh\n+++ b/t/t1800-hook.sh\n@@ -157,9 +157,9 @@ test_expect_success 'git hook run a hook with a bad shebang' '\n \twrite_script bad-hooks/test-hook \"/bad/path/no/spaces\" expect <<-\\EOF\n \t\tfatal: cannot run bad-hooks/test-hook: ...\n-- \n2.34.1\n\n"},{"id":"463035","messageId":"002001d8c8e0$617c5f80$24751e80$@nexbridge.com","threadId":"58388","inReplyTo":"20220915075717.425673-1-adam@dinwoodie.org","subject":"RE: [PATCH v2] t1800: correct test to handle Cygwin","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2022-09-15T08:51:38Z","receivedAt":"2022-09-15T08:52:08Z","isPatch":true,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On September 15, 2022 3:57 AM, Adam Dinwoodie wrote:\n>On Cygwin, when failing to spawn a process using start_command, Git outputs the\n>same error as on Linux systems, rather than using the GIT_WINDOWS_NATIVE-\n>specific error output. The WINDOWS test prerequisite is set in both Cygwin and\n>native Windows environments, which means it's not appropriate to use to\n>anticipate the error output from start_command. Instead, use the MINGW test\n>prerequisite, which is only set for Git in native Windows environments, and not for\n>Cygwin.\n>\n>Signed-off-by: Adam Dinwoodie \n>Helped-by: Đoàn Trần Công Danh \n>---\n>\n>With apologies to folk receiving this multiple times; it looks like my SMTP setup\n>was causing problems for some servers, and while the mails seemed to be arriving\n>with me, they didn't seem to be appearing at\n>https://public-inbox.org/git/?q=t1800\n>\n> t/t1800-hook.sh | 6 +++---\n> 1 file changed, 3 insertions(+), 3 deletions(-)\n>\n>diff --git a/t/t1800-hook.sh b/t/t1800-hook.sh index 64096adac7..43fcb7c0bf\n>100755\n>--- a/t/t1800-hook.sh\n>+++ b/t/t1800-hook.sh\n>@@ -157,9 +157,9 @@ test_expect_success 'git hook run a hook with a bad\n>shebang' '\n> \twrite_script bad-hooks/test-hook \"/bad/path/no/spaces\" \n> \t# TODO: We should emit the same (or at least a more similar)\n>-\t# error on Windows and !Windows. See the OS-specific code in\n>-\t# start_command()\n>-\tif test_have_prereq !WINDOWS\n>+\t# error on MINGW (essentially Git for Windows) and all other\n>+\t# platforms.. See the OS-specific code in start_command()\n>+\tif test_have_prereq !MINGW\n> \tthen\n> \t\tcat >expect <<-\\EOF\n> \t\tfatal: cannot run bad-hooks/test-hook: ...\n>--\n>2.34.1\n\nI am not convinced this will solve the problem on NonStop where EPERM is reported instead of ENOENT. Apparently EPERM is allowed by POSIX, so text comparison of error messages are not going to work anyway.\n\n"}]}