Current Server Time: 01:40 (Central Europe)

#apertus IRC Channel Logs

2017/05/31

Timezone: UTC


01:03
slikdigit
joined the channel
03:56
anuditverma
joined the channel
05:17
slikdigit
left the channel
07:52
pusle
joined the channel
08:03
BAndiT1983|away
changed nick to: BAndiT1983
08:16
anuditverma
Hi BAndiT1983
08:27
anuditverma
How's my development repo's dir structure should look ? Should it be similar to axiom_beta_control_daemon repo ?
08:27
anuditverma
I am importing schema file https://github.com/apertus-open-source-cinema/axiom-beta-rest-interface/blob/develop/API/client.go#L7
08:28
anuditverma
So I think I need to replicate the structure as well
09:03
se6astian|away
changed nick to: se6astian
09:26
dimaursu16
joined the channel
09:26
dimaursu16
left the channel
09:26
dimaursu16
joined the channel
09:46
BAndiT1983
hi anuditverma, sorry working from home this week, so had a couple of telephone conferences and wasn't looking at IRC
09:46
BAndiT1983
your structure should stay like it is for now
09:47
BAndiT1983
i've created GoAPI folder in axiom_beta_daemon project, where client.go should be placed later, and other related files also
09:47
BAndiT1983
this has to be done manually for now
09:48
BAndiT1983
have you checked out the latest version of beta-software repo? there are some fixes and additions for the build of Go and C++
09:49
niculescu_vlad
joined the channel
09:52
anuditverma
Thanks and yes I saw the fixes
09:54
BAndiT1983
alright, try to build the new version, purge the build folder first to ensure clean start
09:55
BAndiT1983
put client.go into GoAPI folder, so CMakeLists.txt finds it, everything should be prepared without further intervention. at least it was on my system yesterday
09:56
BAndiT1983
if the build is "successful" and you get just Go errors, then you can start with fixing it, first one is the inverted definition of struct on line 10, then follows line 23
10:01
fredy_
joined the channel
10:01
illwieckz
left the channel
10:01
fredy
left the channel
10:01
fredy_
changed nick to: fredy
10:03
Bertl_zZ
changed nick to: Bertl
10:03
Bertl
morning folks!
10:05
anuditverma
Bandit, I am getting this https://pastebin.com/YbGZimGD
10:06
anuditverma
I copied client.go into GoAPI after git cloning
10:06
anuditverma
and then started the build process
10:06
illwieckz
joined the channel
10:10
BAndiT1983
anuditverma: have you cleared your build folder?
10:10
pusle
left the channel
10:10
BAndiT1983
CMake should create /src/Schema folder structure in it
10:11
anuditverma
ok let me check
10:11
anuditverma
There is a dir AxiomDaemon and axiom_daemon_generated.h file in Schema
10:12
BAndiT1983
and have you copied client.go to GoAPI in axiom_beta_control_daemon
10:12
anuditverma
yes
10:12
BAndiT1983
so they are generated
10:13
BAndiT1983
but your build tells me otherwise, it says: no buildable Go source files in /home/anudit/beta-software/axiom_beta_control_daemon/build/GoAPI
10:13
BAndiT1983
GoAPI/CMakeFiles/GoAPI.dir/build.make:61: recipe for target 'GoAPI' failed
10:14
anuditverma
let me try it again, I guess I copied it in a wrong dir
10:19
niculescu_vlad_
joined the channel
10:20
anuditverma
I see what happened, I need to build first then copy the file
10:20
BAndiT1983
?
10:20
BAndiT1983
you have to copy it before the build everything else does not make sense otherwise
10:21
BAndiT1983
later it will be merged into the main project
10:21
anuditverma
I copied it into axiom_beta_control_daemon/GoAPI and not into /home/anudit/beta-software/axiom_beta_control_daemon/build/GoAPI
10:21
BAndiT1983
that's why you have to copy it, to replicate the finished state
10:21
BAndiT1983
???
10:22
BAndiT1983
the first folder is right
10:22
BAndiT1983
you should never copy anything to the build folder, NEVER
10:22
anuditverma
there are two GoAPI folders
10:22
anuditverma
okay
10:22
BAndiT1983
we are working only with the source folder
10:22
BAndiT1983
maybe you need clean checkout
10:22
BAndiT1983
purge your local axiom_beta_daemon folder and get a fresh copy
10:23
anuditverma
Ok I am upto date now
10:23
niculescu_vlad_
left the channel
10:24
anuditverma
this file client.go is present in API dir right ? that I need to copy ?
10:25
BAndiT1983
API dir should only have 3 files which belong to C++: CMakeLists, Client.h and ClientExample.cpp
10:25
BAndiT1983
your client.go file should e present in the new GoAPI folder
10:25
anuditverma
yes there are 3 files
10:26
anuditverma
ok
10:26
BAndiT1983
there is also a CMae script which looks for it
10:26
BAndiT1983
*Cmake
10:26
BAndiT1983
*CMake
10:27
anuditverma
I have put my client.go into GoAPI
10:27
BAndiT1983
try to build
10:29
BAndiT1983
and in the mean time i will check what C++ does complain about
10:30
pusle
joined the channel
10:30
anuditverma
after everything : https://pastebin.com/JLG1PkPk
10:34
BAndiT1983
i've found a small bug in CMakeLists of C++ client, will commit it in a moment
10:34
anuditverma
cool, I will get back to my client.go
10:35
BAndiT1983
done, try it now, only Go errors should be there
10:35
anuditverma
ok
10:43
anuditverma
Bandit, https://pastebin.com/nbPzdh2B
10:44
sebix
joined the channel
10:46
BAndiT1983
what have i told you yesterday?
10:47
BAndiT1983
you should kick thee wrong includes out of your file
10:47
BAndiT1983
new ones should look like ->
10:47
BAndiT1983
import ( "fmt" "net" "Schema/AxiomDaemon" flatbuffers "github.com/google/flatbuffers/go")
10:47
BAndiT1983
argh, new lines were removed by clipboard, but you get the idea
10:48
anuditverma
on it
10:50
anuditverma
https://github.com/apertus-open-source-cinema/axiom-beta-rest-interface/commit/f10af4fd1a31047031798835e0532c747e51d7d9 ?
10:52
BAndiT1983
looks correct
10:52
BAndiT1983
another hint -> type Client struct {
10:55
BAndiT1983
ah, you forgot flatbuffers before "github...
10:55
BAndiT1983
look at my paste
10:57
anuditverma
https://github.com/apertus-open-source-cinema/axiom-beta-rest-interface/commit/33120af9c08fc28ab951b5c7b14b436f92d64179
10:57
BAndiT1983
yes, good start
10:57
BAndiT1983
but you said you need more directions
10:57
anuditverma
Yes !
10:57
BAndiT1983
have you looked at the reference i've posted in the issue about sockets?
10:58
anuditverma
Yes I checked it
10:58
BAndiT1983
have you got a connection to the socket?
10:59
BAndiT1983
you should comment everything out in the Client struct first, as it's C++ code and not related to Go, just use it as reference and remove it later
11:00
BAndiT1983
after that you should start to implement SetupSocket() method to get a connection
11:01
BAndiT1983
i will do it in parallel, so i can help when problems occur
11:02
anuditverma
thanks, let me try it first by myself I will ping you here or send a mail
11:03
BAndiT1983
no problem, it's your task, i'm just the safety net
11:03
BAndiT1983
;)
11:04
anuditverma
I think I got the right direction :) , was bit confused before
11:05
BAndiT1983
argh, but Go is just confusing for me, as im used to C/C++, C# and Java
11:05
BAndiT1983
especially method declaration is awkward and happens outside the struct (class)
11:06
anuditverma
yes that was my problem first, but I will get a hang of it
11:09
anuditverma
I still need to code and implement socket, after completing it, how can I test for connection ?
11:10
BAndiT1983
debugger, breakpoint in server.h at line 84
11:10
BAndiT1983
check out what ClientExample is sending
11:11
BAndiT1983
for other test possibilities we have to think of something more comfortable
11:11
anuditverma
cool
11:13
anuditverma
I think I should re-try the build after those corrections
11:23
anuditverma
right, I am getting Go related errors now
11:25
BAndiT1983
removed most code in my version, so i can build it from clean base, progressing well, now i will try to connect to scket
11:25
BAndiT1983
*socket
11:44
BAndiT1983
anuditverma: i've moved the build location to the main folder, as it was building in th GoAPI sub-folder there
11:44
BAndiT1983
now it should produce go_client executable, name can be changed later
12:05
BAndiT1983
anuditverma: connected to socket, crashing at the moment on dameon side, but at least i know what the caveats in golang are
12:05
BAndiT1983
you should use "unixgram" as protocol
12:05
BAndiT1983
net.Dial("unixgram", "/tmp/axiom_daemon")
12:55
niculescu_vlad
left the channel
13:29
anuditverma
left the channel
13:37
anuditverma
joined the channel
14:25
se6astian
changed nick to: se6astian|away
14:31
anuditverma
Bandit, thanks for the leads, I will try it now
14:39
BAndiT1983
no problem
14:39
BAndiT1983
i'll add flatbuffers schema in my version, so i can test the communication
14:43
se6astian|away
changed nick to: se6astian
15:13
sebix
left the channel
15:15
jucar
joined the channel
15:16
se6astian
changed nick to: se6astian|away
15:20
slikdigit
joined the channel
16:12
jucar
left the channel
16:29
slikdigit
left the channel
16:32
champika
joined the channel
17:02
__m__
Hej @anuditverma, hej @BAndiT1983
17:02
anuditverma
Hello
17:02
__m__
Everything fine?
17:04
anuditverma
Yes, there were few things so I have been clearing them with help from Bandit today
17:04
__m__
great
17:05
RexOrCine
left the channel
17:07
__m__
Let's take a look at the schedule, shall we?
17:07
anuditverma
I see https://github.com/apertus-open-source-cinema/beta-software/blob/master/axiom_beta_control_daemon/API/ClientExample.cpp sends few parameters like Gain, ADC range etc
17:07
anuditverma
oh ok sure, lets do that first
17:07
__m__
We have officially entered coding period
17:08
anuditverma
Right
17:08
__m__
What do you say about community bonding period? Everything fine? Did you reach your goals?
17:09
anuditverma
Ah not completely satisfied but at the near end, it seems fine, now next I can work on my client file as scheduled
17:10
Bertl
off for now ... bbl
17:11
Bertl
changed nick to: Bertl_oO
17:12
anuditverma
There were few times I was having some troubles in Go, but now I have a steady pace
17:13
__m__
Ok, that was to be expected. Good to hear you had your troubles, they are necessary to get better :D
17:13
anuditverma
So all in all it's good now
17:13
__m__
Great
17:13
anuditverma
:)
17:14
__m__
I added all issues of the coding period to github
17:14
BAndiT1983
evening
17:14
__m__
Is there anything you need help with at the moment, which you are not discussing with bandit already?
17:15
__m__
Hej there
17:15
BAndiT1983
was debugging, forgot about IRC
17:16
BAndiT1983
golang is driving me mad, but partially it's the fault of flatbuffers generator
17:16
anuditverma
Yes about those, I have 2 issues remaining, "improving go lang" and "docker usage", So I would keep the former one open for sometime and later one is for next week I guess
17:16
BAndiT1983
what is the goal of docker one?
17:17
anuditverma
according to description "Building a basic client app in Go that would be utilized to test the REST API interface throughout the project"
17:17
__m__
Docker usage was planned for week 1 of June, but it is ok for me if you do it next week
17:17
BAndiT1983
so what is the goal of docker?
17:17
__m__
Building the code in a docker process, write a Dockerfile for production
17:17
BAndiT1983
i see
17:20
anuditverma
about the ClientExample.cpp, for testing, testBuf, gain and ADCRange are used
17:20
__m__
Containerization helps us keeping boundaries
17:20
champika
left the channel
17:20
anuditverma
So for initial testing these would be used in Client.go as well ?
17:22
__m__
I would say yes
17:22
__m__
It is a good starting point in my opinion
17:22
BAndiT1983
using it at the moment, but it should be restructured later
17:22
anuditverma
okay
17:22
BAndiT1983
so we have client.go which contains client "class" and some controll application, like ClientExample
17:24
se6astian|away
changed nick to: se6astian
17:29
champika
joined the channel
17:33
__m__
@anuditverma , you know about what @BAndiT1983 is referring to? Everything clear?
17:34
__m__
*everything evident?
17:34
BAndiT1983
does bandit know what bandit is referring to? ;)
17:34
__m__
I hope so :D
17:35
BAndiT1983
__m__: you should manage the docker part, know a bit about it, but not enough
17:35
anuditverma
yes I got it
17:35
BAndiT1983
if it's necessary, then it should be set up early
17:36
__m__
Anudit wants to do it next week, that's fine for me
17:36
se6astian
changed nick to: se6astian|away
17:37
__m__
@anuditverma, shall I prepare the docker sceleton or do you want to try it alone first?
17:37
__m__
*skeleton
17:38
anuditverma
I want to try it first
17:39
__m__
Alright
17:39
__m__
That's your starting point: https://hub.docker.com/_/golang/
17:39
__m__
Anything else?
17:40
anuditverma
Nope
17:40
__m__
@BAndiT1983 ?
17:41
__m__
If not, I suggest we meet next week (!) same day, same time. Is that ok for everyone?
17:41
BAndiT1983
no, not from my side
17:41
anuditverma
Bandit would you be available tomorrow as well ?
17:41
BAndiT1983
yes, the time is ok
17:41
anuditverma
Yes, timings are fine
17:41
BAndiT1983
i think yes, just have to change the location again at some point in time, but it wouldn't last long as i do customer care and have to be near my laptop for that
17:42
anuditverma
ok great
17:42
__m__
Ok, great, so we meet next Wednesday at 4pm UTC. See you!
17:43
BAndiT1983
bye
17:43
BAndiT1983
also nice instructions -> https://blog.docker.com/2016/09/docker-golang/
17:43
anuditverma
Thanks to both !
17:46
champika
left the channel
17:52
davidak
joined the channel
17:53
BAndiT1983
anuditverma: we need an investigation about strong typing of flatbuffers generated files for Go
17:54
BAndiT1983
if i do it by hand, it works somehow, but the generated files don't have any, so i have to use int for type when passing to some method
17:55
BAndiT1983
it's about enums
17:55
anuditverma
may some sort of type casting is needed then, if it so
17:55
anuditverma
*be
17:56
BAndiT1983
no, not casting
17:56
BAndiT1983
i want to define methods which take strong typed arguments
17:56
BAndiT1983
otherwise one could insert anything and that's not the goal
17:57
BAndiT1983
e.g. it should have something like that at the begining of the file, below package -> Mode.go -> type Mode int
18:01
anuditverma
will this help https://google.github.io/flatbuffers/flatbuffers_grammar.html ?
18:02
BAndiT1983
how should it help? the problem lies in the generator
18:02
BAndiT1983
have to ask in the isues if flatbuffers
18:02
BAndiT1983
*issues
18:03
BAndiT1983
the schema works fro C++, but Go one is problematic
18:03
BAndiT1983
just take a look at the generated content
18:03
anuditverma
oh ok I thought it has something to do with declaration
18:03
anuditverma
ok
18:08
davidak
left the channel
18:09
slikdigit
joined the channel
18:18
BAndiT1983
added new issue for FB, let's see what the guys will say about it -> https://github.com/google/flatbuffers/issues/4333
18:20
anuditverma
great
18:20
anuditverma
left the channel
18:20
BAndiT1983
we will see if it is great or dumb
18:20
anuditverma
joined the channel
18:21
anuditverma
Let's hope it gets fixed :P
18:22
anuditverma
FB version ?
18:22
anuditverma
flatbuffers
18:22
anuditverma
?
18:23
BAndiT1983
yes, flatbuffers
18:25
BAndiT1983
i could fix it also, but i want to hear the opinion of the people who have developed it
18:26
BAndiT1983
maybe i'm missing something and it's already possible
18:26
BAndiT1983
just wait and see
18:26
anuditverma
The bot hasn't replied yet :P
18:39
anuditverma
we should probably add that issue is for a gsoc project, may be then their developers would add/label it on a fast track :D
18:42
BAndiT1983
maybe, let's wait a day or 2
18:42
BAndiT1983
what are you using for Go development?
18:45
BAndiT1983
if noone replies, then i will try to add new option for FB compiler and also the handling in Go generator, afterwards create a pull request, then it should be more important for the guys
18:47
anuditverma
Not using any ide or plugin for Go
18:47
anuditverma
any recommendations ?
18:47
BAndiT1983
i would suggest Visual Studio Code with Go plugin/s
18:47
anuditverma
okay
18:47
BAndiT1983
i even set GOPATH, so it uses the generated schema files, so i can develop with less errors
18:47
BAndiT1983
it builds when saving
18:48
BAndiT1983
and tells me when errors or warnings occur
18:48
anuditverma
I see it's available for linux as well
18:48
anuditverma
cool
18:48
anuditverma
Thanks
18:48
BAndiT1983
i'm developing under linux as the camera uses also ArchLinux
18:49
BAndiT1983
otherwise i wouldn't tell you about the IDE if it were not available for it
18:50
anuditverma
I read "Visual" so a Microsoft product, that's why I said so :P
18:50
anuditverma
I will try it
18:50
BAndiT1983
hey, worked with VS on daily base in former company, one of the best IDEs
18:51
BAndiT1983
QtCreator is still missing features, CLion also
18:51
anuditverma
oo I see, cool
18:51
BAndiT1983
Eclipse is a piece of slow junk
18:53
anuditverma
installed VS
18:55
BAndiT1983
you can install Go extensions, there are just 1 or 2 which are usable
18:55
BAndiT1983
afterwards you can open user settings with ctrl+, or similar, or even look usersettings up with ctrl+shift+p and type user settings to get the command
18:55
BAndiT1983
then place following there -> https://pastebin.com/Jyi8LaLx
18:56
BAndiT1983
just adjust the path for your build path
18:56
BAndiT1983
afterwards it should find the generated files and only mark the real errors in your code
19:10
anuditverma
I have updated the settings
19:11
anuditverma
how it find those files ? I need to manually add the workspace ?
19:11
anuditverma
*would
19:17
zaiwr4
joined the channel
19:18
zaiwr4
left the channel
19:38
anuditverma
Bandit, bye for now, I will see you tomorrow, goodnight
19:39
anuditverma
left the channel
19:39
niculescu_vlad
joined the channel
00:09
slikdigit
left the channel
00:25
BAndiT1983
changed nick to: BAndiT1983|away
00:26
intracube
changed nick to: intracube_afk