Hi,

I personally use some script which simulate data e.g. writing to a MQTT topic.

But I think a data source (Pipeline element) for nontechnical users are useful 
especially at the beginning of a project.
E.g. to test connections to the field or to evaluate some pipeline ideas  
without having  external data sources.
Is there currently an alternative source for data?

Greetings,
Stefan



-----Ursprüngliche Nachricht-----
Von: Florian Micklich <[email protected]>
Gesendet: Mittwoch, 9. November 2022 12:42
An: [email protected]
Betreff: Re: sources-vehicle-simulator:0.71.0-SNAPSHOT error

Hi Philipp,

yes we can remove it.
I am looking anyway for some movement data, we could use via adapter.

But it needs to be removed also in the docker-compose.full.yml here [1].
and have to rebuild the download source here [2].

I can remove it and push it if you want (after I created a jira ticket) but not 
sure how to replace the download source.

Greetings
Florian


[1] 
https://github.com/apache/incubator-streampipes/blob/dev/installer/compose/docker-compose.full.yml
[2] https://streampipes.apache.org/download


Am Mittwoch, dem 09.11.2022 um 08:14 +0000 schrieb Philipp Zehnder:
> Hi Florian,<br>
>
> that is a good point. We currently do not build this image
> anymore.<br> The goal is to gradually remove the sources docker images
> and use adapters instead.<br>
>
> Therefore, I suggest to remove the sources-vehicle-simulator from the
> CLI as well.<br> What do you think?<br>
>
> Cheers,<br>
> Philipp<br>
>
> Von: Florian Micklich
> <[[email protected]](mailto:[email protected])><br>
> Datum: Montag, 7. November 2022 um 16:59<br>
> An: dev
> <[[email protected]](mailto:[email protected])><br>
> Betreff: sources-vehicle-simulator:0.71.0-SNAPSHOT error<br> Hi
> all,<br>
>
> i tried to run the full installer via CLI and got following error
> message during image pull of the sources-vehicle-simulator.<br> Is
> this known?<br>
>
>
>
> ```<br>
>  ⠿ sources-vehicle-simulator Error
> 2.2s<br> Error response from daemon: manifest for
> apachestreampipes/sources-vehicle-simulator:0.71.0-SNAPSHOT not found:
> manifest unknown: manifest unknown<br> ```<br>
>
> Greetings<br>
> Florian<br>








SEEBURGER AG            Vorstand/SEEBURGER Executive Board:
Sitz der Gesellschaft/Registered Office:                Axel Haas, Michael 
Kleeberg, Axel Otto, Dr. Martin Kuntz, Matthias Feßenbecker
Edisonstr. 1
D-75015 Bretten         Vorsitzende des Aufsichtsrats/Chairperson of the 
SEEBURGER Supervisory Board:
Tel.: 07252 / 96 - 0            Prof. Dr. Simone Zeuchner
Fax: 07252 / 96 - 2222
Internet: http://www.seeburger.de               Registergericht/Commercial 
Register:
e-mail: [email protected]               HRB 240708 Mannheim


Dieses E-Mail ist nur für den Empfänger bestimmt, an den es gerichtet ist und 
kann vertrauliches bzw. unter das Berufsgeheimnis fallendes Material enthalten. 
Jegliche darin enthaltene Ansicht oder Meinungsäußerung ist die des Autors und 
stellt nicht notwendigerweise die Ansicht oder Meinung der SEEBURGER AG dar. 
Sind Sie nicht der Empfänger, so haben Sie diese E-Mail irrtümlich erhalten und 
jegliche Verwendung, Veröffentlichung, Weiterleitung, Abschrift oder jeglicher 
Druck dieser E-Mail ist strengstens untersagt. Weder die SEEBURGER AG noch der 
Absender (Obermeier. Stefan) übernehmen die Haftung für Viren; es obliegt Ihrer 
Verantwortung, die E-Mail und deren Anhänge auf Viren zu prüfen.


This email is intended only for the recipient(s) to whom it is addressed. This 
email may contain confidential material that may be protected by professional 
secrecy. Any fact or opinion contained, or expression of the material herein, 
does not necessarily reflect that of SEEBURGER AG. If you are not the addressee 
or if you have received this email in error, any use, publication or 
distribution including forwarding, copying or printing is strictly prohibited. 
Neither SEEBURGER AG, nor the sender (Obermeier. Stefan) accept liability for 
viruses; it is your responsibility to check this email and its attachments for 
viruses.

Reply via email to