Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 04 21:35
    akpuvvada closed #518
  • Nov 28 14:35
    akpuvvada edited #518
  • Nov 28 14:35
    akpuvvada edited #518
  • Nov 28 14:34
    akpuvvada opened #518
  • Nov 25 17:08
    mellistibco assigned #290
  • Nov 25 17:08
    mellistibco closed #395
  • Nov 25 17:07
    mellistibco edited #395
  • Nov 25 17:07
    mellistibco closed #238
  • Nov 25 16:56
    mellistibco edited #395
  • Nov 25 16:56
    mellistibco edited #395
  • Nov 25 16:54
    mellistibco closed #299
  • Nov 25 16:53
    mellistibco closed #327
  • Nov 25 16:52
    mellistibco closed #183
  • Nov 25 16:51
    mellistibco closed #203
  • Nov 25 16:51
    mellistibco closed #215
  • Nov 25 16:50
    mellistibco milestoned #215
  • Nov 25 16:50
    mellistibco demilestoned #215
  • Nov 25 16:49
    mellistibco closed #481
  • Nov 25 16:48
    mellistibco closed #221
  • Nov 25 16:41
    mellistibco assigned #513
obloquy
@obloquy
In Flogo rules there is a quite active branch called 'store' which seems to be adding a Redis backing store to the rule engine. Is there a rough timeframe for merging that with master?
Aaron Chipper
@aaronchipper

In Flogo rules there is a quite active branch called 'store' which seems to be adding a Redis backing store to the rule engine. Is there a rough timeframe for merging that with master?

+1 for this - I'd love to see that as well.

Matt Ellis
@mellistibco
@jpark800
sivagtibco
@sivagtibco
@alexandrev powershell i tried but not worked.. :(
Alexandre Vazquez
@alexandrev
ouch @sivagtibco , could you share the output you've got and the steps done?
sivagtibco
@sivagtibco
PS C:\code\FLOGO\cli\commands\healthcheckgvapp\bin> $Env:FLOGO_APP_PROPS_OVERRIDE="C:\Code\FLOGO\props.json"
PS C:\code\FLOGO\cli\commands\healthcheckgvapp\bin> .\healthcheckgvapp.exe
2019-06-20T23:40:09.197-0700 INFO [flogo.engine] - Starting app [ healthcheckgvapp ] with version [ 0.0.1 ]
2019-06-20T23:40:09.198-0700 INFO [flogo.engine] - Engine Starting...
2019-06-20T23:40:09.198-0700 INFO [flogo.engine] - Starting Services...
2019-06-20T23:40:09.198-0700 INFO [flogo] - ActionRunner Service: Started
2019-06-20T23:40:09.198-0700 INFO [flogo.engine] - Started Services
2019-06-20T23:40:09.198-0700 INFO [flogo.engine] - Starting Application...
2019-06-20T23:40:09.199-0700 INFO [flogo] - Starting Triggers...
2019-06-20T23:40:09.202-0700 ERROR [flogo] - Trigger [ receive_http_message ]: Error Starting
github.com/project-flogo/core/support/log.(*zapLoggerImpl).Errorf
C:/Users/sganise/go/pkg/mod/github.com/project-flogo/core@v0.9.2/support/log/zap.go:65
github.com/project-flogo/core/support/managed.Start
C:/Users/sganise/go/pkg/mod/github.com/project-flogo/core@v0.9.2/support/managed/managed.go:64
github.com/project-flogo/core/app.(*App).Start
C:/Users/sganise/go/pkg/mod/github.com/project-flogo/core@v0.9.2/app/app.go:178
github.com/project-flogo/core/engine.(*engineImpl).Start
C:/Users/sganise/go/pkg/mod/github.com/project-flogo/core@v0.9.2/engine/engineimpl.go:169
github.com/project-flogo/core/engine.RunEngine
C:/Users/sganise/go/pkg/mod/github.com/project-flogo/core@v0.9.2/engine/engine.go:38
main.main
C:/Code/FLOGO/cli/commands/healthcheckgvapp/src/main.go:49
runtime.main
c:/go/src/runtime/proc.go:200
2019-06-20T23:40:09.203-0700 ERROR [flogo] - error starting Trigger[receive_http_message] : listen tcp :8002: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.
github.com/project-flogo/core/support/log.(*zapLoggerImpl).Error
C:/Users/sganise/go/pkg/mod/github.com/project-flogo/core@v0.9.2/support/log/zap.go:43
github.com/project-flogo/core/engine.RunEngine
C:/Users/sganise/go/pkg/mod/github.com/project-flogo/core@v0.9.2/engine/engine.go:40
main.main
C:/Code/FLOGO/cli/commands/healthcheckgvapp/src/main.go:49
runtime.main
c:/go/src/runtime/proc.go:200
Failed to start engine: error starting Trigger[receive_http_message] : listen tcp :8002: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.
where as in the json i had given 8002 port but i am trying to update this port in the config with 8003
{ "port": 8003 }
as it is still checking the one i had given in my actual app (as 8002) it is failing ( another app already running on 002)
Alexandre Vazquez
@alexandrev
can you share the app code and props file by mail so I can check at my end?
sivagtibco
@sivagtibco
can i attach a file here?
Alexandre Vazquez
@alexandrev
not sure..
sivagtibco
@sivagtibco
@alexandrev is this tibco.com?
i can send a mail
Alexandre Vazquez
@alexandrev
hi @sivagtibco I'm able to reproduce it
with 0.9.0
I have two issues guys. a) not able to update to 0.9.2 ... do you know why ? I'm doing the go get -u .... but still in 0.9.0
b) can anyone test if override props still works? I'm able to do it in FE but not in OSS
Samip Kothari
@skothari-tibco
May be flogo update github.com/project-flogo/core. I checked the override, you are correct it doesn’t work. Currently I have a workaround and we can fix it eventually. For work around just add _ "github.com/project-flogo/core/app/propertyresolver” in the import of src/main.go and make sure you have set the env variable FLOGO_APP_PROPS_JSON.
Abram Van Der Geest
@abramvandergeest
Hi all, we just created a new channel for ml related questions: https://gitter.im/project-flogo/developers
so come on by if you have questions or if you are interested in ml
and the link is actually: https://gitter.im/project-flogo/Ml
Matt Ellis
@mellistibco
@skothari-tibco not eventually :) Can we fix that now?
Samip Kothari
@skothari-tibco
@mellistibco sure thing.
Matt Ellis
@mellistibco
Thanks
Frank Martinez
@fm-tibco
to use the json property override resolve, you can also add github.com/project-flogo/core/app/propertyresolver to the imports section of your flogo.json
when you do a flogo build, it should add that to your imports.go
@mellistibco do you remember why we don’t import that by default?
Matt Ellis
@mellistibco
🤔 I think we decided that there was no reason if it wasn’t going to be used but I suppose we need either provide some config to add it in the ui or some cli cmd perhaps? Maybe a build arg switch?
sivagtibco
@sivagtibco
i tried to add github.com/project-flogo/core/app/propertyresolver and try to get my property from json still it i am not getting from external prop
Vijay Nalawade
@vijaynalawade
@sivagtibco : how are you running your app? What env vars have you set?
You need set both FLOGO_APP_PROPS_JSON=</path/to/json> FLOGO_APP_PROPS_RESOLVERS=json
Mario Torre
@mtorre-iot
How can I programatically write a script to add my triggers/activities to the flogo Web docker? ?I want to find a way to install my developments on the running flogo docker after I start it.
Leon Stigter
@retgits
You could use the APIs that Flogo Web exposes to do that, though they aren't very well documented. I've built a simple Go app that helps me backup and restore my Flogo apps, which you could use as a starting point to build the same for adding activities. https://github.com/retgits/flogowebhelper
A second option is to build a docker image containing the imports you want to add already. In my dockerfiles repo, there is a folder for Flogo Web (https://github.com/retgits/dockerfiles/tree/master/flogoweb) that contains a Dockerfile and an imports.go that I use to build a new docker container. The imports.go contains all the activities that are important to me, and it saves me a bit of time when starting a new container from scratch
Mario Torre
@mtorre-iot
Thanks @retgits ! this was exactly was I looking for. However, I am getting an error because most of the activities listed in imports.go are not in the flogo original container. I am getting this error: " error: imports.go:15:2: cannot find package "github.com/TIBCOSoftware/flogo-contrib/activity/channel" in any of:
/tmp/flogo-web/build/server/local/engines/flogo-web/src/flogo-web/vendor/github.com/TIBCOSoftware/flogo-contrib/activity/channel (vendor tree)
/usr/local/go/src/github.com/TIBCOSoftware/flogo-contrib/activity/channel (from $GOROOT)
/tmp/flogo-web/build/server/local/engines/flogo-web/src/github.com/TIBCOSoftware/flogo-contrib/activity/channel (from $GOPATH)"
Leon Stigter
@retgits
Hmm 🤔 that’s intriguing as those activities are from Flogo itself... it’s been a while since I’ve used the Web UI so it might be some things have changed. @fcastill have the imports for Flogo Web changed? As in do they need to exist in a different location?
Mario Torre
@mtorre-iot
@retgits I pulled the lastest version of flogo docker and the errors are gone. But I am still struggling - how I make my new docker to contain my contributions?
Leon Stigter
@retgits
If you add your import paths to the “imports.go” file and build a new docker container that would automatically add them
Fabián Castillo
@fcastill
you could also install the activities/triggers through the CLI, which is what the webui does under the covers. Here’s a sample Dockerfile for it: https://gist.github.com/fcastill/25680aae4bac25e854c46fb3126b30a2
Mario Torre
@mtorre-iot
@retgits Great idea - thank you! I guest I am still learning about docker and containers. Cheers!
@fcastill Very useful. Now I get it - thank you!
Leon Stigter
@retgits
@mtorre-iot no problem 😁 we’re here to help!
Alessandro Chimera
@achimera
Hi all, I’ve developed a new activity that captures a picture using a Webcam. It relies on OpenCV and uses https://github.com/hybridgroup/gocv . The issue I have when I execute the binary is that I have the following error:
2019-06-27T09:44:14.044+0200 DEBUG [flogo.activity.actreturn] - Mappings: map[image:=$webcam_1.image status:=$webcam_1.status] Failed to create engine: error unmarshalling flow: unable to find a 'webcam_1’ resolver
I can’t figure out where the problem could be. My activity is available here: https://github.com/achimera/flogo/tree/master/activity/webcam
and the related Flogo flow is attached, named f1_webcam.json
Thanks for any help!
Samip Kothari
@skothari-tibco
The issue seems to be with the flow. I have edited the it.
Alessandro Chimera
@achimera
@skothari-tibco thanks, thanks, thanks!!! It works now :tada: