| From: | Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: [pgAdmin4][Patch]: RM #3464 pgAdmin 4 won't start on windows |
| Date: | 2018-09-18 11:25:05 |
| Message-ID: | CANxoLDeyLrcAoMs38nN7XrEbdzNHX2fUP8Es+S01rzxjbhekWQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Tue, Sep 18, 2018 at 4:52 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> Hi
>
> On Tue, Sep 18, 2018 at 12:18 PM, Akshay Joshi <
> akshay(dot)joshi(at)enterprisedb(dot)com> wrote:
>
>> Hi Hackers,
>>
>> Recently we have added basic startup logs and because of that we came to
>> know that pgAdmin4 is not able to open the log file if the file path
>> contains Cyrillic alphabet or Special characters.
>> *fopen* fails to open the file, so I have used *_wfopen *for Windows
>> operating system.
>>
>> Attached is the patch to fix that issue. Please review it.
>>
>
> I assume this doesn't affect the address file or startup log? Only the
> Python log?
>
Yes. we have used *fopen* when we redirect the stderr to the Python log
file.
>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
--
*Akshay Joshi*
*Sr. Software Architect *
*Phone: +91 20-3058-9517Mobile: +91 976-788-8246*
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2018-09-18 14:08:36 | pgAdmin 4 commit: Ensure the runtime can startup properly if there are |
| Previous Message | Dave Page | 2018-09-18 11:22:21 | Re: [pgAdmin4][Patch]: RM #3464 pgAdmin 4 won't start on windows |