Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / Motiva-AI/clj-sqs-extended issues and pull requests

#130 - feat: [sc-13385] Fix clj-sqs-extended regression

Pull Request - State: closed - Opened by Quantisan about 2 years ago - 1 comment

#129 - Refactor/replace cheshire json

Pull Request - State: closed - Opened by Quantisan over 3 years ago

#128 - use pipeline-transit library for transit ser/de

Pull Request - State: closed - Opened by Quantisan over 3 years ago

#127 - CircleCI continuous deployment is broken

Issue - State: open - Opened by Quantisan almost 4 years ago

#126 - forward_action_service worker is stuck

Pull Request - State: closed - Opened by Quantisan almost 4 years ago - 1 comment

#125 - Refactor/receive loop tests remove side effect

Pull Request - State: closed - Opened by Quantisan almost 4 years ago - 1 comment

#124 - Refactor/receive loop side effects alternate

Pull Request - State: closed - Opened by Quantisan almost 4 years ago

#123 - use day8/lein-git-inject for project versioning

Pull Request - State: closed - Opened by Quantisan almost 4 years ago

#122 - Refactor/receive to channel

Pull Request - State: closed - Opened by Quantisan almost 4 years ago - 1 comment

#121 - receive/receive-loop bundles business logic and side-effects together. Separate the two for SRP.

Issue - State: closed - Opened by Quantisan almost 4 years ago
Labels: refactor

#120 - Refactor/test fixtures

Pull Request - State: closed - Opened by Quantisan almost 4 years ago

#119 - clj-sqs-ext should use a single client object to share http connections

Pull Request - State: closed - Opened by Quantisan almost 4 years ago - 1 comment

#118 - clj-sqs-ext should not receive message until there is an available handler process

Pull Request - State: closed - Opened by Quantisan about 4 years ago

#117 - clj-sqs-ext should not receive message until there is an available handler process

Pull Request - State: closed - Opened by Quantisan about 4 years ago

#116 - clj-sqs-ext should not receive message until there is an available handler process

Pull Request - State: closed - Opened by Quantisan about 4 years ago

#115 - SQS.deleteMessage sometimes fail because: The receipt handle has expired

Pull Request - State: closed - Opened by Quantisan about 4 years ago

#114 - SQS.deleteMessage sometimes fail because: The receipt handle has expired

Pull Request - State: closed - Opened by Quantisan about 4 years ago

#113 - Refactor/delete message dont have to hold the whole message

Pull Request - State: closed - Opened by Quantisan about 4 years ago

#112 - use a single client object

Issue - State: closed - Opened by Quantisan about 4 years ago

#111 - wrap sqs/delete-message! in a async/thread

Pull Request - State: closed - Opened by Quantisan about 4 years ago

#110 - clj-sqs-ext is stopping loop on SQS 500 error

Pull Request - State: closed - Opened by Quantisan about 4 years ago

#109 - Add integration test in clj-sqs-ext to test with SQS S3

Pull Request - State: closed - Opened by Quantisan about 4 years ago

#108 - circleci login to docker hub

Pull Request - State: closed - Opened by Quantisan about 4 years ago

#107 - fix test for multiple handle queues running

Pull Request - State: closed - Opened by Quantisan about 4 years ago

#106 - messages from SQS takes at least 20 seconds to get processed

Issue - State: closed - Opened by Quantisan about 4 years ago

#105 - Refactor/receive messages run inside go

Pull Request - State: closed - Opened by Quantisan about 4 years ago

#104 - Issue 99/handlers getting jammed 2

Pull Request - State: closed - Opened by Quantisan about 4 years ago

#103 - Messages without format attribute can be received correctly

Pull Request - State: closed - Opened by ghost about 4 years ago

#102 - There's too much implementation coupling between test and source

Issue - State: closed - Opened by Quantisan over 4 years ago

#101 - Refactor receive-loop to not rely on statefulness (i.e. the external atom)

Pull Request - State: closed - Opened by Quantisan over 4 years ago - 1 comment

#100 - Rewrite receive-to-channel

Pull Request - State: closed - Opened by Quantisan over 4 years ago

#99 - when too many different handle-queues are running, something gets stuck and the handler-fns don't run properly

Issue - State: closed - Opened by Quantisan over 4 years ago - 10 comments
Labels: bug

#98 - Test/add integration test with live aws queues

Pull Request - State: closed - Opened by Quantisan over 4 years ago

#97 - ReceiveMessageRequest set message attribute names properly

Pull Request - State: closed - Opened by Quantisan over 4 years ago

#96 - Add a test for setting and getting message attribute

Issue - State: closed - Opened by Quantisan over 4 years ago

#95 - SQS message attributes do not appear to be received

Issue - State: closed - Opened by Quantisan over 4 years ago
Labels: bug

#94 - receive-message defaults to max wait-time-in-seconds as recommended by AWS

Pull Request - State: closed - Opened by Quantisan over 4 years ago

#93 - we should use long polling by default as recommended by AWS

Issue - State: closed - Opened by Quantisan over 4 years ago

#92 - Issue 91/handle nil message

Pull Request - State: closed - Opened by Quantisan over 4 years ago - 1 comment

#91 - receive-loop is crashing without giving a reason

Issue - State: closed - Opened by Quantisan over 4 years ago - 2 comments
Labels: bug

#90 - Issue 88/support joda datetime serde

Pull Request - State: closed - Opened by Quantisan over 4 years ago

#89 - Allow client to define ser/de writers and readers so we don't need to hardcode custom classes in this library

Issue - State: open - Opened by Quantisan over 4 years ago
Labels: enhancement

#88 - Support org.joda.time.DateTime ser/de

Issue - State: closed - Opened by Quantisan over 4 years ago

#87 - Removed obsolete sleeps in fixtures

Pull Request - State: closed - Opened by ghost over 4 years ago

#86 - Fixed Timing problem between returned stop-fn and with-...-queue fixtures

Pull Request - State: closed - Opened by ghost over 4 years ago - 1 comment
Labels: invalid

#85 - Discussion about how to solve some timing issues

Pull Request - State: closed - Opened by ghost over 4 years ago - 4 comments

#84 - Refactor/serde publicize transit utils

Pull Request - State: closed - Opened by Quantisan over 4 years ago

#83 - Replace sleeps with wait-for

Pull Request - State: closed - Opened by ghost over 4 years ago - 1 comment

#82 - Prove that messages really get deleted when using auto-delete true

Pull Request - State: closed - Opened by ghost over 4 years ago

#81 - Include format setting in the attribute data of SQS messages

Pull Request - State: closed - Opened by ghost over 4 years ago

#80 - Preserve all meta information when declaring convenience functions in core ns

Pull Request - State: closed - Opened by ghost over 4 years ago

#79 - Verify messages get resent after visibility-timeout has been reached and auto-delete is false

Pull Request - State: closed - Opened by ghost over 4 years ago

#78 - Add ser/de format option to use :nippy for performance

Issue - State: open - Opened by Quantisan over 4 years ago
Labels: enhancement

#77 - Document the keys returned by `handle-queue`

Pull Request - State: closed - Opened by ghost over 4 years ago

#76 - localstack host not known when taking shortcut via lein test :all

Issue - State: open - Opened by ghost over 4 years ago
Labels: enhancement

#75 - handle-queue should not set default values for aws-config

Pull Request - State: closed - Opened by ghost over 4 years ago

#74 - default format should be set to JSON to maximize compatibility

Issue - State: closed - Opened by Quantisan over 4 years ago

#73 - format setting should be included in the attribute data of a message

Issue - State: closed - Opened by Quantisan over 4 years ago
Labels: enhancement

#72 - handle-queue prints a single line info log

Pull Request - State: closed - Opened by Quantisan over 4 years ago

#71 - Issue 70/sqs endpoint not seem to be passing host correctly

Pull Request - State: closed - Opened by Quantisan over 4 years ago - 1 comment

#70 - create-queue doesn't seem to be using sqs-endpoint from aws-config

Issue - State: closed - Opened by Quantisan over 4 years ago - 1 comment
Labels: bug

#69 - core api functions should take aws config map

Pull Request - State: closed - Opened by ghost over 4 years ago - 1 comment

#68 - we're redeclaring a few fns in core from internal.sqs, but we're losing the docstring in the process

Issue - State: closed - Opened by Quantisan over 4 years ago

#67 - update send-fifo-message to parse group-id to string internally

Pull Request - State: closed - Opened by Quantisan over 4 years ago

#66 - send-fifo-message requires a string for group-id, but we can loosen that by (str) the argument

Issue - State: closed - Opened by Quantisan over 4 years ago

#65 - handle queue returns only message body

Pull Request - State: closed - Opened by ghost over 4 years ago - 1 comment

#64 - sqs functions should take queue url instead of queue name

Pull Request - State: closed - Opened by ghost over 4 years ago

#63 - Calling stop-fn from handle-queue returns some useful info. Note the keys returned in docstring of `handle-queue` so it's not hidden.

Issue - State: closed - Opened by Quantisan over 4 years ago

#62 - handle-queue should return only the body of the message to the receive-channel

Issue - State: closed - Opened by Quantisan over 4 years ago - 1 comment

#61 - Logs should preferably be single-line for easier parsing in log search

Issue - State: closed - Opened by Quantisan over 4 years ago

#60 - handle-queue should not set default values for aws-config

Issue - State: closed - Opened by Quantisan over 4 years ago

#59 - core api functions should take aws-config map directly instead of expecting sqs-client

Issue - State: closed - Opened by Quantisan over 4 years ago - 2 comments

#58 - Refactor/first integration

Pull Request - State: closed - Opened by Quantisan over 4 years ago

#57 - sqs functions should take queue-url instead of queue-name

Issue - State: closed - Opened by Quantisan over 4 years ago - 1 comment

#56 - Readme example should work out of the box

Pull Request - State: closed - Opened by ghost over 4 years ago
Labels: enhancement

#55 - creds should use Amazonica-like keys for familiarity

Pull Request - State: closed - Opened by ghost over 4 years ago
Labels: enhancement

#54 - `num-handler-threads` is now `number-of-handler-threads`

Pull Request - State: closed - Opened by ghost over 4 years ago
Labels: enhancement

#53 - Linted project with clj-kondo

Pull Request - State: closed - Opened by ghost over 4 years ago
Labels: enhancement

#52 - `num-handler-threads` key should be renamed `number-of-handler-threads` for clarity

Issue - State: closed - Opened by Quantisan over 4 years ago
Labels: good first issue

#51 - creds should use Amazonica-like keys for familiarity

Issue - State: closed - Opened by Quantisan over 4 years ago
Labels: good first issue

#50 - Update readme

Pull Request - State: closed - Opened by Quantisan over 4 years ago

#49 - Readme example should work out of the box for someone that wants to give this library a try

Issue - State: closed - Opened by Quantisan over 4 years ago
Labels: good first issue

#48 - Deploy to clojars

Pull Request - State: closed - Opened by Quantisan over 4 years ago

#46 - check that when auto-delete=false, and visibility-timeout has passed, that the message would be sent again

Issue - State: closed - Opened by Quantisan over 4 years ago - 1 comment
Labels: enhancement

#45 - test that done-fn is doing its job when :auto-delete = false

Issue - State: closed - Opened by Quantisan over 4 years ago - 3 comments

#44 - Replace sleeps with wait-for

Issue - State: open - Opened by ghost over 4 years ago - 1 comment
Labels: enhancement

#43 - Improve usage of restart-loop

Pull Request - State: closed - Opened by ghost over 4 years ago - 2 comments

#39 - Improve restart-loop usage

Issue - State: closed - Opened by ghost over 4 years ago
Labels: enhancement

#37 - Improve Namespace Layout

Issue - State: closed - Opened by ghost over 4 years ago
Labels: enhancement

#34 - Milestone 2: Refactor core functions

Issue - State: closed - Opened by ghost over 4 years ago
Labels: enhancement

#33 - Milestone 2: Extend Core Tests

Issue - State: closed - Opened by ghost over 4 years ago
Labels: enhancement

#32 - Feature: Fallback to pure-SQS (without use of S3) somehow

Issue - State: closed - Opened by Quantisan over 4 years ago - 3 comments
Labels: enhancement

#31 - Milestone 2 code review A

Issue - State: closed - Opened by Quantisan over 4 years ago

#27 - Timing problem between returned stop-fn and with-...-queue fixtures

Issue - State: closed - Opened by ghost over 4 years ago
Labels: enhancement

#24 - Environment values don't get pulled in for testing

Issue - State: closed - Opened by ghost over 4 years ago
Labels: bug

#17 - Fix reading from idle queue

Issue - State: closed - Opened by ghost over 4 years ago
Labels: bug

#16 - Fix previously overlooked minor things

Issue - State: closed - Opened by ghost over 4 years ago
Labels: enhancement

#15 - Restructure core ns

Issue - State: closed - Opened by ghost over 4 years ago
Labels: enhancement

#14 - deduplication-id missing on send-fifo-message

Issue - State: closed - Opened by ghost over 4 years ago
Labels: enhancement

#13 - Fixture Improvement

Issue - State: closed - Opened by ghost over 4 years ago - 1 comment
Labels: enhancement