Re: [GSoC] current working status

2018-06-15 Thread Charles Cui
got it, i will resolve all these warnings. One wired thing when i set up CI is the docker image seems having a postgres version which conflicts with my test version. So, CI is broken now ,although tests pass at my local box. I will also figure this out. On Fri, Jun 15, 2018, 1:34 AM Aleksander Ale

Re: [GSoC] current working status

2018-06-15 Thread Aleksander Alekseeev
Hello Charles, > The repo currently can be build on my mac. You can check it out. > Also I am working on the CI config to monitor each commit. Tests pass on Arch Linux with PostgreSQL 11 and Ubuntu 16.04 with PostgreSQL 9.6. However there is a name conflict in case of PostgreSQL 11: https://afisk

Re: [GSoC] current working status

2018-06-14 Thread Charles Cui
Hi mentors, The repo currently can be build on my mac. You can check it out. Also I am working on the CI config to monitor each commit. Thanks 2018-06-14 8:29 GMT-07:00 Charles Cui : > good idea, will keep a feature branch, and set up ci. > > On Thu, Jun 14, 2018, 8:03 AM Aleksander Aleksee

Re: [GSoC] current working status

2018-06-14 Thread Charles Cui
good idea, will keep a feature branch, and set up ci. On Thu, Jun 14, 2018, 8:03 AM Aleksander Alekseeev < a.aleks...@postgrespro.ru> wrote: > Hello Charles, > > >I saw the list of errors you posted. That's because I have some new > > function implemented and pushed without testing(in order f

Re: [GSoC] current working status

2018-06-14 Thread Aleksander Alekseeev
Hello Charles, >I saw the list of errors you posted. That's because I have some new > function implemented and pushed without testing(in order forget my > change in local machine). > So you are saying it is best to keep each commit workable. Right? Ideally, yes. You can always create a separa

Re: [GSoC] current working status

2018-06-14 Thread Charles Cui
Hi Aleksander, I saw the list of errors you posted. That's because I have some new function implemented and pushed without testing(in order forget my change in local machine). So you are saying it is best to keep each commit workable. Right? Thanks Charles. 2018-06-14 1:41 GMT-07:00 Aleksande

Re: [GSoC] current working status

2018-06-14 Thread Aleksander Alekseeev
Hello Charles, >The first evaluation is coming. Here is my progress so far. During > the first stage of work, I have implemented the thrift binary > protocol as the format of postgresql plugin. Currently, the main > interface is byte. Users who use this plugin need to provide thrift > bytes to

[GSoC] current working status

2018-06-13 Thread Charles Cui
Hi mentors and hackers, The first evaluation is coming. Here is my progress so far. During the first stage of work, I have implemented the thrift binary protocol as the format of postgresql plugin. Currently, the main interface is byte. Users who use this plugin need to provide thrift bytes to