Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Sep 22 19:20
    scala-steward opened #727
  • Sep 18 00:08
    scala-steward opened #726
  • Sep 16 00:28
    scala-steward opened #725
  • Sep 15 20:27
    paualarco closed #723
  • Sep 15 20:27
    paualarco closed #722
  • Sep 15 20:26
    paualarco closed #721
  • Sep 15 20:26
    paualarco closed #720
  • Sep 15 20:26
    paualarco closed #719
  • Sep 15 20:26
    paualarco closed #716
  • Sep 15 20:26
    paualarco closed #714
  • Sep 15 20:09
    paualarco closed #705
  • Sep 15 20:09
    paualarco closed #698
  • Sep 15 20:09
    paualarco closed #674
  • Sep 15 20:09
    paualarco closed #661
  • Sep 15 19:06

    paualarco on master

    Chore/fix sqs test (#724) * Bu… (compare)

  • Sep 15 19:06
    paualarco closed #724
  • Sep 15 19:05
    paualarco opened #724
  • Sep 15 18:41

    paualarco on fix-sqs-test

    Revert "Bumps localstack" This… (compare)

  • Sep 15 18:09

    paualarco on fix-sqs-test

    Fix sqs non existing queue test (compare)

  • Sep 15 13:02
    scala-steward opened #723
Pau Alarcón
@paualarco
hi @/all , created this channel to not mix content with the main one
for now will probably just the three of us
after speaking with @alexandru, we agree this project is on experimental phase, thing that should be very clear in the documentation
for now I will be focusing in improving the test coverage as well as refining existing connectors
Alexandru Nedelcu
@alexandru
👋 welcome
Pau Alarcón
@paualarco
👋🏻
Piotr Gawryś
@Avasil
Hello!
I added Richard, I think he was interested in using it/contributing
And he has been helping a lot with monix-bio recently
Pau Alarcón
@paualarco
cool :)
Richard
@Executioner1939
Hello :-). Thank you for adding me :-)
I would like to add a Google Cloud Storage module to monix-connect
I have been working with it a lot lately :-)
Alexandru Nedelcu
@alexandru
Nice 👍
Piotr Gawryś
@Avasil
I root for the project big time, I wanted something like it for a long time but I have never found time/energy to do it on top of my other contributions
Richard
@Executioner1939
This is basically the monix equivalent to alpakka https://doc.akka.io/docs/alpakka/current/index.html
Pau Alarcón
@paualarco
yeah that's it, the reason why I created the sub module Akka in which the idea was to use their implementations and converting to monix
but I think that bringing up the ActorSystem every time is not ideal, and better to have pure monix implementations that does not depends on it
Pau Alarcón
@paualarco
First PR! Removed references to cloriko and added sbt configurations (more info in the description).
Pau Alarcón
@paualarco
I am afraid I have no access to merge the reviewed PR 😯
Piotr Gawryś
@Avasil
Weird
try now @paualarco
Pau Alarcón
@paualarco
thank you @Avasil
Alexandru Nedelcu
@alexandru
@paualarco sorry, forgot to double check your permissions on that repo, I've made you admin on the monix-connect project
Pau Alarcón
@paualarco
No worries! thanks @alexandru
Pau Alarcón
@paualarco
I have created some issues and linked the to a milestone. See project status here: https://github.com/monix/monix-connect/projects/1
My changes to the alpakka AvroParquet connector were gladly accepted, in which it still have the constrain of only writing to parquet from Avro
Whereas the one in Monix Connect does not, that's why it is only called Parquet :)
Alexandru Nedelcu
@alexandru
Nice
Pau Alarcón
@paualarco
Hello guys! All the connectors have been refined and test coverage has been improved as well!
Still might be things to clean up yet, but I feel confident on start publishing the next software increments as well as getting used to the release process.
The documentation will still clearly indicating that the project is not yet stable.
What do you think? In case you do not have inconveniences it would be great to get some guidance on how to do so...
At the same time I could start migrating the documentation to a web version.
Piotr Gawryś
@Avasil
I can help with release, I don't remember initial setup (I think it is required to create a ticket somewhere to get Sonatype access to monix namespace?) but I should have old notes somewhere :D
Piotr Gawryś
@Avasil
I aggre it's a good idea to release 0.1.0, it can still be useful to people and it's a chance to get feedback. Consider setting up Mima and try to preserve bincompat in 0.1.x to get used to it but also not worry about upgrading to 0.2.0 soon. Treat it like an exercise until the project fully stabilizes.
Pau Alarcón
@paualarco
Sounds good! :) Okay will have that in mind, there is no rush indeed. Some feedback would be appreciated since now people can't even play with it.
Alexandru Nedelcu
@alexandru
We should grant @paualarco access for publishing on Sonatype for io.monix and let him be in charge of the release, to get accustomed to the process.
I don't remember exactly the procedure, but I think we should open a ticket on Sonatype or reuse an old one.
We have this issue on Sonatype, we could add a comment to it: https://issues.sonatype.org/browse/MVNCENTRAL-2890
@paualarco let me know your Sonatype username
Or create an account if you don't have one
And yes, publishing a 0.1.0 sounds like a good plan. Let it mature a little before declaring 1.0.0, because afterwards you have to worry about compatibility.
Pau Alarcón
@paualarco
Hey @alexandru, I've just created an account with username paualarco, but I can't access to the ticket link you sent.
And yes, that's the plan, to stay in 0.x for a while until being confident enough. Eventually I would notify the future intentions before hand in order to get your approval / opinion.
Alexandru Nedelcu
@alexandru
@paualarco no worries, I've made the request, will let you know when an admin at Sonatype replies
Alexandru Nedelcu
@alexandru
@paualarco got a confirmation, you can now publish on Sonatype under the io.monix organization