| - | - | | --- | --- | | Issue | There was a problem in the route parsing and regex replacement. For example, with the following route endpoints /api/builds/<str:name>/fonts/<str:font>.<str:format> the font and format are wrongly extracted, where the parameter SRGunmetal-Regular.fnt results in font: SRGunmetal-Regular.f and format: t. | | Dependencies | -- | | Decisions | Removed the . from the REPLACE_REGEX. All other routes with dots are working as supposed and the route mentiond above as well. | | Animated GIF | -- |

Newer features for client-side-rendering require the loading of "blob:" scripts for anti-aliasing purposes, this prevents browser from blocking the necessary requests.

Useful when dealing with non-JSON endpoints, such as file upload.

Based on https://github.com/hivesolutions/appier/blob/1470c427a760fb698e423bbbfdad53a29578279e/src/appier/model.py#L72

Issue: https://github.com/ripe-tech/ripe-compose/issues/68

This PR:

• adds an AMQPExchange class that abstracts a connection to a RabbitMQ exchange
• an exchange belongs to a cluster, not a single node; hence, this class accepts a list of broker URLs; if the connection to one fails, it attempts to connect to the rest; if all brokers fail, this class will attempt to reconnect forever (but such a catastrophic failure will likely require a cluster reset regardless)
• changes AMQPQueue class to accept an optional exchange name and routing key; if present, it binds the queue to that exchange using that routing key

Support for parsing and converting the kwargs of count function, similar to the logic present in find. This is required if we want to use the same filtering logic for counting as the one we have for listing.

This relates to the RIPE Tech issue of multiple state transitions.

For RIPE Tech, we will need to find the shortest path between two states and make all the in-between transitions. Instead of a bespoke solution for order states only, I thought it was better to generalize the issue at hand: finding the shortest path in the graph. Hence I decided to implement a simple Dijkstra. This will allow us to abstract that logic here and simply apply the transitions in RIPE Core. It will also work for future entities with their own states and state graphs (while a bespoke solution for Order statuses only would not).

I think this source makes sense to be added to the Appier codebase because a graph module and graph utilities by themselves are useful in many domains (maybe in the future in networking to find the shortest path between nodes).

The proposed and implemented API is:

import appier

# a list of edges which is a list of tuples
# where the first element is the source node
# the second element is the destination node
# the third element is the cost of the edge (defaults to 1)
# the fourth element indicates whether the edge is bidirectional or not (defaults to unidirectional)
edges = [
    ("A", "B"),
    ("A", "C", 6, True),
    ("B", "D"),
    ("C", "D"),
    ("D", "E", 10),
    ("D", "F", 15),
    ("E", "F", 6),
    ("E", "G", 2),
    ("F", "G", 6)
]
graph = appier.Graph()
graph.add_edges(edges)

path, cost = graph.dijkstra("A", "F")
assert(path == ['A', 'B', 'D', 'F'])
assert(cost == 17)

Initializing the graph can also be done by passing the edges as an argument:

graph = appier.Graph([
    ("A", "B"),
    ("A", "C", 6, True),
    ("B", "D"),
    ("C", "D"),
    ("D", "E", 10),
    ("D", "F", 15),
    ("E", "F", 6),
    ("E", "G", 2),
    ("F", "G", 6)
])

Issue:

Pymongo released version 4.0 on november 29 2021 and unlike the others version, this one doesn't event the patch number so as appier is assuming that pymongo will have a patch number, it fails to unpack that value and an error is thrown.

Replicating the issue:

Testing the fix:

| - | - | | --- | --- | | Issue | https://github.com/ripe-tech/ripe-id-mobile/issues/2#issuecomment-884831078
When providing an image with EXIF Orientation info, it was being ignored in the final image (after resize). | | Decisions | - Use PIL.ImageOps method exif_transpose that returns an image transposed according to its EXIF orientation tag. | | Screenshots | Original Image:

Before:

After:
|

Description

There seems to be no friendly way of extending an Appier session. In some contexts, it's desirable to be able to extend the session indefinitely.

Solution

The expiration date is being set when the session object is being created. This date can be changed only by accessing the internal property directly. Probably there should be an refresh() method to easily refresh the session's expiration date (current date + default timeout).

Also, in RedisSession values are being stored with SETEX, therefore they are deleted by Redis when the timeout is reached. To extend the session in RedisSession, the value's expiration date must be extended using the EXPIRE command to provide a new timeout.

Description

Calling new() on a model with relations causes an error like the following:

AttributeError

500 - 'module' object has no attribute 'Wishlist'
Traceback (most recent call last):
File "/repo.extra/appier/src/appier/base.py", line 803, in application_l
result = self.handle()
File "/repo.extra/appier/src/appier/base.py", line 931, in handle
else: result = self.route()
File "/repo.extra/appier/src/appier/base.py", line 1159, in route
else: return_v = method_i(*args, **kwargs)
File "/repo.extra/myswear/src/myswear/controllers/web/base.py", line 104, in do_signup
user = sadapters.models.User.new()
File "/repo.extra/appier/src/appier/model.py", line 354, in new
if fill: model = cls.fill(model)
File "/repo.extra/appier/src/appier/model.py", line 970, in fill
default = _type._default() if hasattr(_type, "_default") else default
File "/repo.extra/appier/src/appier/typesf.py", line 424, in _default
return cls(None)
File "/repo.extra/appier/src/appier/typesf.py", line 373, in __init__
self.__start__()
File "/repo.extra/appier/src/appier/typesf.py", line 417, in __start__
if is_reference: self._target = self.__class__._target()
File "/repo.extra/appier/src/appier/typesf.py", line 428, in _target
if is_reference: return getattr(common.base().APP.models_i, target)
AttributeError: 'module' object has no attribute 'Wishlist'

Previous implementation threw a KeyError.

This PR adds a unit test covering the no path case and changes it to return no path and infinity for the cost ([], INFINITY).

It also places INFINITY in a common place (defines.py) to be used both by tests and graph module code.

Description

It's important to have a mechanism that allows control of the number of requests per time unit. This will provide a way to control an unintentional (or intentional) DOS.

Implementation

Create a decorator appier.requests that receives the number of requests per minute allowed for the action method in the controller.

The implementation should take inspiration from PreflightPart.

Inspiration

• express-rate-limit - npm

Description

It should be possible by using code to gather the complete set of ACL tokens that are registered for the currently running application. This way it would be possible to list the complete set of possible permission for the running application context.

Implementation

Should be possible to use appier.get_tokens() to retrieve the complete set of ACL tokens and action methods (from controllers) associated with them.

Description

By using multicast UDP it would be possible to discover other services with the same INSTANCE values and start communicating with them for certain puposes.

Election system to determine the one that is considered the master.

For instance it should be possible to discover a configuration server that way, or for Ripe discover the proper composer instance in the current network and auto-configure it.

References

https://docs.mongodb.com/manual/core/replica-set-elections/

Description

It should be really cool to create a migration infra-structure like the one present in Migratore.

Description

The idea is to build an infra-structure that is agnostic from the underlying database manager used.

Description

Using a pool of threads and the Future based abstraction it should be possible to adapt the current data layer access to an async fashion.

PyMongo with callback support.

References

https://motor.readthedocs.io/en/latest/examples/callbacks-and-coroutines.html#with-coroutines

Description

Sometimes it's important to have a proper abstraction for a working unit inside an abstraction system.

Having per example a DownloadTask that allows the downloading of an HTTP based asset and that properly notifies any listening handler should be the aim of this operation.

Implementation

Create the Task class abstraction and then use the websocket infra-structure to make Appier Admin control all of these tasks.

There should be some co-relation between this Task class and the Future class.

References

socket.io chat example