Consider to add type converters

I'm researching Joi alternatives and found this lib.  Unfortunately there is little meaning in validation without type coercion. If value is checked to be an integer it should be possible to use this as an integer.
Not validate as string, then apply type convertion manually, then use. It breaks the whole purpose of declarativeness in validation: you'll end up with the second deeply-nested declarative object with the same keys, and different values describing type convertion rules (semantically the same, as you've already said you want an integer)...

I don't really understand the problem here, the numericality validator has an option called noStrings which rejects non numbers.
The reason I opted for supporting strings per default is that when you read values from a form you get them as strings.

I don't want to reject non-numbers. I want to get real native JS Number object (same with Date, etc.) after validation.
Sometimes you need to validate JSON object, coming from 3rd party source. It may easily contain non-string values.

I like the idea.
Version 0.8.0 will ship with a validate.cleanAttributes function that currently just removed unknown keys so I've already started doing some work to help you with this.
I could add a function that does type conversion for you (automatically when using promises as with the attribute cleaning).
The biggest problem would be how the syntax would look. I suppose most types could be inferred from the constraints but not all.
Perhaps the constraints could contain a new key called type that could be used in type conversion, how does this sound?

@ansman I wrote a validation library in Python and I considered to port in in JS, but I'm very out of time to do this. And of course I would prefer to reuse an existing and time-proven one.
There I implemented a pipeline of transformations. Imagine you need to get data from textarea where each line represents a phone number. We need to split the line, trim the whitespace and check against the format. If each line represented and age, it would require to make type coercion as well.
Of course you can also do this in a purely declarative, type-aware way which goes deeper to the algebra and crazy math but I'm not so strong in it so I needed a more practical and easy approach.
So I stayed with a pipelines of formatters and parsers.
Curious thing, I remember that sometimes I needed different set of formatters and parsers so maybe it's even quite impossible to make declaratively. Or there will be some limitations. Sorry for such broad phrases, I hope to continue this discussion, but I have to go now.

Check this https://github.com/ivan-kleshnin/paqforms/blob/master/paqforms/converters.py
This is OOP, of course now I would built it in a purely functional style but perhaps my words
will be easier to understand.

Intro
Ok, it's me again. I spent last days thinking and experimenting with validation and the final picture are getting clear to me.
JS community desperately needs an environment agnostic data validation library for JS.
As you truly mentioned in docs:

There are already many validation libraries out there today but most of them are very tightly coupled to a language or framework.

It's ridiculous, I mean we have to have a lot of competing solutions today. But, spent a lot of hours on search, I did find only 3 projects worth considering. Joi, TComb-Validation and this one.
TComb-Validation, being very interesting on itself, is a very specific beast and I'd like to exlude it from today's rant. So we have Joi and ValidateJS. Joi does not have two crucial components ValidateJS has: custom validators and async validators. Joi devs are not going to support second one at all, and first one are only planned (since 2014...). That being said Joi has 1200 stars against local 120 still... Not less important is that fact, that Joi is very very big, 2.5 Mib uncompressed, against 30 Kb of ValidateJS. So, IMO, Joi as a very overrated library, and ValidateJS is an underrated.
Validation is one of the only few areas which suppor code sharing between frontend and backend. We should be eager for such opportunities. They are, above all, one of the topmost marketing benefit of JS. That's why a lot of people, including me, asked Joi authors to reconsider their priorities. But as already said, Joi authors are very rejective to all requests outside of their own view.
A bit about myself. I wrote a big form validation and form building library once in Python (https://github.com/ivan-kleshnin/flask-paqforms).  But, at lest, I was there and I know a bit of that problems you're facing. And I still think I made it better than much more popular (mainstream) WTForms. By objective reasons... but who cares? Let's come back to JS.

... comment in progress

Outro
You can seriously cleanup validation library, decoupling questions of type onto separate lib. Validation will validate only one (or two with undefined) type than. Validation will mean "apply validation rules against passed value" not "convert and apply validation rules against resulting value". Single responsibility principle in action.
One question remains: how to incorporate errors from parsing step into validation layer resulting step.
I solved this in Paqforms by having the same inner error representation (Exceptions) (https://github.com/ivan-kleshnin/paqforms/blob/master/paqforms/fields.py#L205).
Both parsing step and inner doValidate functions can throw. There is one general catch to all of them.
Whether to keep original messages from Parsing layer or replace them with generic Parse failed / Validation failed is up to you. This is a secondary question comparing to all above, to let's skip this for now.

Outro
You can seriously cleanup validation library, decoupling questions of type onto separate lib. Validation will validate only one (or two with undefined) type then. Validation will mean "apply validation rules against passed value" not "convert and apply validation rules against resulting value". Single responsibility principle in action.
One question remains: how to incorporate errors from parsing step into validation layer result.
I solved this in Paqforms by having the same inner error representation (Exceptions) (https://github.com/ivan-kleshnin/paqforms/blob/master/paqforms/fields.py#L205).
Both parseXyz and inner doValidate functions can throw. There is one general catch wrapping them.
Whether to keep original messages from Parsing layer or replace them with generic Parse failed / Validation failed is up to you. This is a secondary question comparing to all above, to let's skip this for now.
I hope I put my thoughts clear enought. Final diagram to reiterate:

parse(formData) -> businessData, throws on user (input) errors.
Handle type errors.

validate(parse, businessData, [...options]) -> businessData, throws on user (input) errors.
Handle value errors.

format(businessData) -> formData, throws on programmer (data mismatch) error.

I agree that validation is complex task and should consist of 3 parts:

parsing (I call it as "pre validation filtering")
validation
formatting ("post validation filtering")

I think they are indivisible and should be described in one place.
Also some fields may be optional and have default value.
Validated object may have deep nesting.
Simplified example of validation in node.js:
var filter = require('validator');

var fromAndTo = {
    startTime: {
        $default:    function() { // value or function returning value
            return new Date();
        },
        $validators: {
            presence: true,
            datetime: true
        }
    },

    endTime: {
        $validators: {
            presence: true,
            datetime: true
        }
    },

    isTerminal: {
        $parsers: filter.toBoolean
    },

    address: {
        cityId: {
            $validators: {
                presence: true
            }
        },

        terminalId: {
            $validators: {
                presence: function(value, attributes) {
                	// I need way to get "from" or "to" property (first level property of "attributes")
                    return /* attributes.(from|to).isTerminal */;
                }
            }
        },

        value: {
            $parsers:    filter.trim,
            $validators: {
                presence: function(value, attributes) {
                    return /* !attributes.(from|to).isTerminal */;
                }
            }
        }
    },

    geo: {
        $validators: {
            presence: function(value, attributes) {
                return /* !attributes.(from|to).isTerminal */;
            }
        },

        latitude: {
            $validators: {
                presence:     true,
                numericality: {
                    greaterThanOrEqualTo: -90,
                    lessThanOrEqualTo:    90
                }
            }
        },

        longitude: {
            $validators: {
                presence:     true,
                numericality: {
                    greaterThanOrEqualTo: -180,
                    lessThanOrEqualTo:    180
                }
            }
        }
    },

    note: {
        $parsers: filter.trim
    }
};

var needValidate = {
    from: fromAndTo,
    to:   fromAndTo
};

parsing (I call it as "pre validation filtering")

validation
formatting ("post validation filtering")

Hi @Jokero! As parsing step can and often includes conversion from localized to universal format and formatting step vice versa includes conversion from universal to localized term filtering is really not so great as parsing / formatting.
Your API is 3-rd of the possible ways to organize this, yeah.

I think they are indivisible and should be described in one place.

Well, they can be decoupled into different libs but are indivisible if you talk in the sense of requirements.

I think this format is justified, but it is necessary to separate levels of abstraction.
1 level. Validate framework. Has config with special fields:
$default - default value,
$parsers, $validators, $formatters - arrays of functions that call in series by framework.
This can be asynchronous if return promise (framework wrap returns in q.when). Processing of these arrays is the same in all cases and is realised by unified library. The difference is that this functions return value in parsers and formatters and return boolean in validators (it is function's logic, not framework). Formatters may want to call in reverse order, as is done in AngularJS (why do that?).
2 level. Filters (parsers and formatters) and validators. Filters can include localization and others. Validate.js has library of basic filters and validators, but user can create customs. User determines which should return custom filters (f.e. convert empty strings to undefined). If someone need special bundle of filters or validators for your application. He can set it in default config for all requests/responses.
defaults.$parsers.push(emtyStringToUndfined);
defaults.date.$parsers.push(localToUTF);

$parsers, $validators, $formatters - arrays of functions that call in series by framework.

With chaining be ready to meet orner cases like "how to deal with a promise in second element if first and third calls were sync" and so on. I still think function composition is better.
No questions – no endless arguing about what is better.

Formatters may want to call in reverse order, as is done in AngularJS (why do that?).

Yeah, yeah – one of such questions. Piping is just not flexible enough.

Validate.js has library of basic filters and validators, but user can create customs.

Why to include such stuff in Validate.js? It should be a separate library cause all this parsing stuff may be reused in different areas. Like HTML data scraping for example. Same parsing issues.

@ivan-kleshnin, I reread your comments and realized that I initially didn't understand the meaning of formatting :smiley:
You mean:
form data -> parsing -> validation -> business data
form data <- formatting <- business data

And I:
form data -> parsing -> validation -> formatting (additional transformation if need) -> business data

I'm taking a look at validate.js for parsing the desiredCapabilities object which gets passed into Appium. This is a case of needing some pretty simple js object-validation, but isn't tied to web forms or anything like that (so I need to verify that a property is typeof 'string' and such). The proposal in this thread would probably be the ideal thing for us (we also need the filtering and parsing steps).
This also looks like a related project: https://github.com/molnarg/js-schema/

@Jokero aren't that diagrams equal just presented in different ways :smiley: ?

how to deal with a promise in second element if first and third calls were sync

Easy!
function chainEvaluator(filters, input) {
    return filters.reduce(function(previousPromise, currentFn, index, arr) {
        return previousPromise.then(function(value) {
           return currentFn(value);
        })
    }, q.when(filters.shift()(input)));
}

var fn1 = function(value) {return value + '-1'};
var fn2 = function(value) {return q.when(value + '-2')}; //return promise
var fn3 = function(value) {return value + '-3'};
var functionsArray = [fn1, fn2, fn3];

chainEvaluator(functionsArray, 'smth').then(function(result) {
    console.log(result);
});

Why include such stuff in Validate.js?

Because without basic validators no one will use the bare framework. I mean pristine, required etc. validators. Maybe toLowerCase etc. parsers/formatters. It will be separate library but validate.js will be uses it by default.

Because without basic validators no one will use the bare framework. I mean pristine, required etc. validators. Maybe toLowerCase etc. parsers/formatters. It will be separate library but validate.js will be uses it by default.

I'm for separate library as a dependency as well.
Anyway it's good to see that people are mostly agree here.
Details are details. The subject we discuss is crossplatform so I think it's quite important talk.

I'm for separate library as a dependency as well.

good.
@ansman What do you meen?

I don't really understand the problem you are talking about to be honest.
The scope of validate.js has been and will always be a fast, simple and easy way of validating a set of attributes against a set of constraints.
As it stands today there is a simple form parser, this is only because it's such a commonplace thing to do.
There is also a simple attribute cleaner for ease of use with promises.
I'm all for things such as Promises and Reactive programming which makes things like validation easy:
Promise.resolve(document.querySelector("form#signup"))
  .then(validate.collectFormValues) // This is the parsing step, could easily be replaced with another lib
  .then(function(formValues) { // This is validation, the core of validate.js
    return validate.async(formValues, constraints);
  })
  .then(api.signup)
  .then(handleSignupSuccess)
  .catch(ValidationError, handleValidationError) // This is formatting
  .catch(ServerError, handleServerError)
  .catch(handleGenericError);

I'm closing this due to inactivity but feel free to comment and I'll reopen it.


fix: remove yarn from dependencies

Summary
remove yarn from dependencies
Related
To resolve #97
Motivation
To prevent yarn from being bundled into consumer's node_modules
How is this tested?

yarn is not used anywhere in this repository
no part of the code in relies on yarn

yarn is used in the format and lint NPM commands.
That said, yarn should be a dev dependency, not a normal dependency.

ah.. I missed that somehow..
actually format and lint can still be run without yarn
What do you say we remove yarn entirely like this?:
     "scripts": {
         "test": "jest",
-        "format": "yarn prettier . --write",
+        "format": "prettier . --write",
-        "lint": "yarn prettier . --check",
+        "lint": "prettier . --check",
         "coverage": "npx c8 npx jest"
     },

Tested it will still run fine without yarn command.


Use PWA

this system is not oriented to websites, or at least not a traditional one, I think the best use for this is a Data-Driven application and to add another good technology why not use PWA?
this system like many others - without the internet - doesn't work, but using PWA we can check online device status in the background and allow or not further operations, another plus to PWA is that we can add some content pages to enrich the whole experience.
this can lead to two examples which have in common these 3 points

[ ] Add PWA Manifest
[ ] Load all assets needed
[ ] Check for network status

PWA example without Authentication

[ ] Add some content page
[ ] Add the RealFlow page which is active only if connection status = online

PWA example with Authentication

[ ] Add a Login page that can call an endpoint to get a token

[ ] If the token is valid and connection status is online

[ ] Go to the RealFlowR page

[ ] If the token is not valid and connection status is online

[ ] Go to a PWA login

Hi,
I agree with you, PWA has zero cost for configuration, but the real power are service worker and the possibility of being able to be upload in the store
My 2 cents
🖖

Hi,
I agree with you, PWA has zero cost for configuration, but the real power are service worker and the possibility of being able to be upload in the store
My 2 cents
🖖


Correction for raw affiliation Civil Engineering Toronto, Ontario, Canada, 2018; Department of Civil Engineering Ryerson University; Herat University, 2011 Herat, Afghanistan; Master of Applied Science, 2018

Correction needed for raw affiliation Civil Engineering Toronto, Ontario, Canada, 2018; Department of Civil Engineering Ryerson University; Herat University, 2011 Herat, Afghanistan; Master of Applied Science, 2018
raw_affiliation_name: Civil Engineering Toronto, Ontario, Canada, 2018; Department of Civil Engineering Ryerson University; Herat University, 2011 Herat, Afghanistan; Master of Applied Science, 2018
new_rors: 050zs3956;05g13zd79
previous_rors: 050zs3956
works_examples: W4255309222;W4235765633
contact: ecb3876e4eac2480f3910634cfd4d4a4:079fc3e1 @ ourresearch.org

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


Proxy Plugin: DNS Queries through Socks5 Proxy

Expected behaviour:
According to https://github.com/Flexget/Flexget/commit/9dd4e1c8b09e365c7af259b4f010c8c308c9287c#diff-e44affe1ab0e04fc4471a0fe6bfbb08a the proxy plugin should support socks5 and socks5h. Socks5 only uses the proxy for requests. Socks5h should also use the proxy for DNS lookups.
I would expect that I could use socks5h in the config and the DNS requests are routed through the proxy. This would mean that I could run flexget on an isolated network behind a socks5 proxy.
Actual behaviour:
Flexget does not recognize socks5h as proxy URL in the config. When using proxy: socks5h://proxy:9150 in my config file I get:
Path: /templates/global/proxy
Message: u'socks5h://proxy:9150' is not a u'url'

The requests go through the proxy when I use proxy: socks5://proxy:9150 in my config file but only if a dns lookup is possible without the socks5 proxy. The dns lookups are not tunneled through the proxy.
Steps to reproduce:

Try to use the proxy string in the config as mentioned above.

Build an environement with an isolated Flexget that only allows to use the socks5 proxy for internet access. I used a docker environement where I put a flexget container and socks5 proxy on an isolated network and in addition i put the socks5 proxy on the bridge network.

Config:
web_server: yes

templates:
    global:
        pathscrub: windows
        proxy: socks5://proxy:9150

tasks:
  Manual:
    proxy: socks5://proxy:9150
    rss: "https://example.com/rss-feed"

    thetvdb_lookup: yes
    if:
        - tvdb_ep_id == None: fail
    retry_failed:
        retry_time: 30 minutes
        retry_time_multiplier: 2
        max_retries: 10
    set:
        content_filename: "{{tvdb_series_name}} - {{tvdb_ep_id}}/{{tvdb_series_name}} - {{tvdb_ep_id}} - {{tvdb_ep_name|default('Unknown')}} - {{quality|upper}}"
        move_completed_path: /downloads/video/tv/{{tvdb_series_name}}/
    series:
      - lorum ipsum

    quality:
      - 1080p webdl h264
    deluge:
        host: deluge.torrent
        username: localclient
        password: password
        path: /downloads/downloading/

Log:

(click to expand)
[/tasks/Manual/proxy] u'socks5h://proxy:9150' is not a u'url'
Unable to download the RSS for task Manual (https://example.com/rss-feed): SOCKSHTTPSConnectionPool(host='example.com', port=443): Max retries exceeded with url: /rss-feed (Caused by NewConnectionError('<urllib3.contrib.socks.SOCKSHTTPSConnection object at 0x7f84c54360d0>: Failed to establish a new connection: [Errno -3] Try again',))

Additional information:

FlexGet version: 2.20.18
Python version: 2.7.14
urllib3: 1.24.1
Installation method: https://hub.docker.com/r/cpoppema/docker-flexget/
Using daemon (yes/no): yes

Thanks for the report. I've just pushed a fix so that those urls pass the config validation, should work properly in the next release.


Add support for put/patch/delete

Currently, Panda supports GETs and POSTs. You may see this inside sampleGatewayMapping.json.
Add support for PUTs and DELETEs. It will require changes inside RoutesTrees.
Add some endpoints to the /auxiliaryServices and to sampleGatewayMapping.json itself.
Make sure (by manual testing) it's working.

Will be done as a part of #11

partially solved with https://github.com/pandafolks/panda/pull/38

Solved with https://github.com/pandafolks/panda/pull/42


Using Ingress

With this project projectcontour.io incubating into CNCF, it will be nice for us to show the users about Ingress. This Ingress is based on envoy so the elements are just same as virtual service
@burrsutter  @lordofthejars  thoughts ??

We would like to keep the Minikube and Openshift experiences fairly close.  If you deploy the nginx based ingress to minikube (and nginx is the most popular solution) then the Ingress.yaml used is close to the Ingress.yaml used on OpenShift which generates a Route via ha-proxy.

@burrsutter are you saying we add it or not?? I quoted projectcontour because its part of CNCF and it understands kubernetes Ingress resource.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Burr Sutter<EMAIL_ADDRESS>Sent: Thursday, July 16, 2020 3:39:46 AM
To: redhat-developer-demos/kubernetes-tutorial<EMAIL_ADDRESS>Cc: Kamesh Sampath<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [redhat-developer-demos/kubernetes-tutorial] Using Ingress (#27)
We would like to keep the Minikube and Openshift experiences fairly close. If you deploy the nginx based ingress to minikube (and nginx is the most popular solution) then the Ingress.yaml used is close to the Ingress.yaml used on OpenShift which generates a Route via ha-proxy.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fredhat-developer-demos%2Fkubernetes-tutorial%2Fissues%2F27%23issuecomment-659040518&data=02|01||f15061ba173246e1b4d408d8290bc9dc|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637304477885443346&sdata=MdsA4ZcFNNgGqQ5hOBhXJk%2Fe3%2B%2FrI8FTpX5YQEA4wfE%3D&reserved=0, or unsubscribehttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAHHMIKZIEJKDK662Q6KH3TR3YSKVANCNFSM4O2V3S4Q&data=02|01||f15061ba173246e1b4d408d8290bc9dc|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637304477885453334&sdata=LsBy6wq2fOoHbgWLhISHMvX%2FmwySAddXDRZGpimyMuk%3D&reserved=0.

let's stick with nginx and its minikube add-on
https://kubernetes.io/docs/tasks/access-application-cluster/ingress-minikube/


BVAL-636 Mandating JavaFX extractors only in environments where JavaF…

…X is present
https://hibernate.atlassian.net/browse/BVAL-636

So, this makes the Oracle JDK a requirement to validate the TCK as we will need an environment where JavaFX is available to test this.
Agreed?

It makes JavaFX a requirement for running and passing the TCK. I think one
can install OpenJFX next to OpenJDK, so technically it doesn't require the
Oracle JDK. I've filed a BVTCK for keeping track of it.

Merged, thanks!


how can i get the data from the div tag?

can i get the data from the div tag?

Yes. I suggest using jquery to get the data and model it into a json object that you feed to alasql.


ST-Link won't connect

Any ideas? I have it all connected exactly as prescribed in the video..

we'll use the thread instead, no need to double up


TypeError: Cannot read property 'payments' of undefined on idempotency key violation

Incorrect exception is thrown by the library when idempotency key is violated. It seems like it attampts to parse error response as successful and fails since error response does not contain 'payments' attribute.

This is happening when creating a Payment and raiseOnIdempotencyConflict is set to false. I have an existing failed payment with the same Idempotency key. Looks like the library is meant to return existing payment in this case. However I am getting TypeError instead.

This should be fixed in the latest release https://github.com/gocardless/gocardless-nodejs/releases/tag/v2.1.0


Bug: await broker.publish do not waits actual message sends on Kafka(aiokafka)

Describe the bug
await broker.publish(....) do not wait for actual message send, even with enable_idempotence=True / acks='all'
I have fix for it.
so, this happend on Aiokafka, with  remote servers.  the reason is in faststream/kafka/publisher/producer.py
in
    @override
    async def publish(  # type: ignore[override]
        self,
        message: "SendableMessage",
        topic: str,
        *,
        correlation_id: str,
        key: Union[bytes, Any, None] = None,
        partition: Optional[int] = None,
        timestamp_ms: Optional[int] = None,
        headers: Optional[Dict[str, str]] = None,
        reply_to: str = "",
    ) -> None:
        """Publish a message to a topic."""
        message, content_type = encode_message(message)

        headers_to_send = {
            "content-type": content_type or "",
            "correlation_id": correlation_id,
            **(headers or {}),
        }

        if reply_to:
            headers_to_send["reply_to"] = headers_to_send.get(
                "reply_to",
                reply_to,
            )

        # should be send_and_wait here
        await self._producer.send(
            topic=topic,
            value=message,
            key=key,
            partition=partition,
            timestamp_ms=timestamp_ms,
            headers=[(i, (j or "").encode()) for i, j in headers_to_send.items()],
        )

there is a call to await self._producer.send and send is not actually waits for message deliver - it returns a furute (https://aiokafka.readthedocs.io/en/stable/_modules/aiokafka/producer/producer.html#AIOKafkaProducer.send)
here we should use send_and_wait instead (https://aiokafka.readthedocs.io/en/stable/_modules/aiokafka/producer/producer.html#AIOKafkaProducer.send_and_wait)
Could you please help me with pull request? thanks.
How to reproduce
Include source code:
import asyncio
from faststream import FastStream

# KAFKA_BOOTSTRAP_SERVERS - some remote cluster (not localhost)
broker = KafkaBroker( config('KAFKA_BOOTSTRAP_SERVERS'), security=security, enable_idempotence=True)

async def send_message():
    await broker.connect()
    await broker.publish([1,2,3], "msg_answer1")

    # it will work, if I add
    # await asyncio.sleep(5)

if __name__ == "__main__":
    asyncio.run(send_message())
...

Expected behavior
Expected: Message sent and then app closes
Observed behavior
App closes before actual message sent
Additional context
Provide any other relevant context or information about the problem here.

Thank you for the report! I funded the same behavior with Confluent, but was not sure, how it works
Now I see the problem and try to fix it soon

@zpl I created a draft PR alreat, but still not sure, which method should be used as a default one: should we wait for confirmation everytime or the current behavior should be the default one?

@Lancetnik , I think it should be send_and_wait for default. probably in some rare cases we can skip it for performance?
well, I think even with performance I prefer to use create_task instead of await. but I expect that send will actually send's a message.


Sound stops when application in background mode (IOS 11)

Info:
react-native 0.49.3
react-native-sound 0.10.4
xcode 9.0.1
Added capabilities to info.plist
<key>UIBackgroundModes</key> 	<array> 		<string>audio</string> 		<string>fetch</string> 		<string>remote-notification</string> 	</array>
Affected platforms
Appears only on IOS 11 (IOS 10 and below works as expected)
Code example
Sound.setCategory('Playback', true); sound = new Sound(url, undefined, error => {     if (error) {       console.log('error loading sound', error);       return;     }     sound.play(() => {     });   });
Steps to reproduce
Play sound and press home button
Result
Sound stops until application is not active
Expected result
Sound plays until end of the track even if app is not active or screen is locked

Sorry, issue has gone after full reinstall of node_modules and application.

So you just updated the info.plist and it started working?

I had the same issue (no sound in background).
I added the audio background permission... and it was not working.
I had to remove and reinstall the app.
Just to help people having such issue too :)


09/13/2018 01:30 : Create Pull Request for branch prTesting_2018091301 -> master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Download Broken - Gives AWS Cost Explorer

The download link is for a file called "Azure Costs Explorer - github" but actually downloads the AWS Costs Explorer - I think someone grabbed the uploaded the wrong QVF...

Fixed


Movies thumbnails not showing in calendar

Environment
Docker
Version
0.13.4
Describe the problem

Thumbnails of movies from radarr are not showing where thumbnails from sonarr show.
Logs
[DEPRECATED] Use `createWithEqualityFn` instead of `create` or use `useStoreWithEqualityFn` instead of `useStore`. They can be imported from 'zustand/traditional'. https://github.com/pmndrs/zustand/discussions/1937

 WARN  EXPERIMENTAL: You have disabled the edit mode. Modifications are no longer possible and any requests on the API will be dropped. If you want to disable this, unset the DISABLE_EDIT_MODE environment variable. This behaviour may be removed in future versions of Homarr

ℹ Requested frontend content of configuration 'default'

 WARN  EXPERIMENTAL: You have disabled the edit mode. Modifications are no longer possible and any requests on the API will be dropped. If you want to disable this, unset the DISABLE_EDIT_MODE environment variable. This behaviour may be removed in future versions of Homarr

 WARN  EXPERIMENTAL: You have disabled the edit mode. Modifications are no longer possible and any requests on the API will be dropped. If you want to disable this, unset the DISABLE_EDIT_MODE environment variable. This behaviour may be removed in future versions of Homarr

 WARN  EXPERIMENTAL: You have disabled the edit mode. Modifications are no longer possible and any requests on the API will be dropped. If you want to disable this, unset the DISABLE_EDIT_MODE environment variable. This behaviour may be removed in future versions of Homarr

 WARN  EXPERIMENTAL: You have disabled the edit mode. Modifications are no longer possible and any requests on the API will be dropped. If you want to disable this, unset the DISABLE_EDIT_MODE environment variable. This behaviour may be removed in future versions of Homarr

ℹ Requested frontend content of configuration 'default'

 WARN  EXPERIMENTAL: You have disabled the edit mode. Modifications are no longer possible and any requests on the API will be dropped. If you want to disable this, unset the DISABLE_EDIT_MODE environment variable. This behaviour may be removed in future versions of Homarr

 WARN  EXPERIMENTAL: You have disabled the edit mode. Modifications are no longer possible and any requests on the API will be dropped. If you want to disable this, unset the DISABLE_EDIT_MODE environment variable. This behaviour may be removed in future versions of Homarr

ℹ Requested frontend content of configuration 'default'

 WARN  EXPERIMENTAL: You have disabled the edit mode. Modifications are no longer possible and any requests on the API will be dropped. If you want to disable this, unset the DISABLE_EDIT_MODE environment variable. This behaviour may be removed in future versions of Homarr

ℹ Requested frontend content of configuration 'default'
ℹ Requested frontend content of configuration 'default'
ℹ Saving updated configuration of 'default' config.

 WARN  EXPERIMENTAL: You have disabled the edit mode. Modifications are no longer possible and any requests on the API will be dropped. If you want to disable this, unset the DISABLE_EDIT_MODE environment variable. This behaviour may be removed in future versions of Homarr

ℹ Requested frontend content of configuration 'default'
Error: 'sharp' is required to be installed in standalone mode for the image optimization to function correctly. Read more at: https://nextjs.org/docs/messages/sharp-missing-in-production```

<img width="422" alt="image" src="https://github.com/ajnart/homarr/assets/61882536/08fb091e-a2b4-4740-9138-54c2cd00528c">

### Context

_No response_

### Please tick the boxes

- [X] I confirm that I attached the proper logs
- [X] I've read the [docs](https://github.com/ajnart/homarr#readme)
- [X] I've checked for [duplicate issues](https://github.com/ajnart/homarr/issues)
- [X] I've tried to debug myself

Hi, do you run an AdBlocker? Please check the common troubleshooting steps for posters not loading:
https://homarr.dev/docs/community/faq#why-are-the-posters-in-my-calendar-not-loading

Hi, do you run an AdBlocker? Please check the common troubleshooting steps for posters not loading: https://homarr.dev/docs/community/faq#why-are-the-posters-in-my-calendar-not-loading

Hello, yes I do. I just tried disabling it and even using another browser with no extensions and it's the same problem

Hey, are you using radarr v5? If so that is not yet supported, but should be part of the next release.

In fact I am on v<IP_ADDRESS>27. Thanks !


Center Taskbar

Description of the new feature / enhancement
There are already some apps which can do that. But I think it would fit nicely with powertoys to be able to center the taskbar, which for ultra wide screens I think helps a lot. And than aswell be able to display each instace in its own icon instead of needing to have it group within one icon.
Scenario when this would be used?
It benefits me in everyday use during all my workflow.
Supporting information
https://github.com/ChrisAnd1998/TaskbarX

Windows 11 offers the flexibility to center the taskbar. Is there a particular use case that would require this functionality specifically for Windows 10?
The suggestion for separate icons for each app instance sounds reasonable. I believe there's already an existing issue # for this, but we'll still log this one in our suggested ideas milestone for now. Thanks!


no puedo seguir desde diaspora

Hola,
pasa algo raro no me deja seguir la cuenta<EMAIL_ADDRESS>desde joindiaspora.

Diaspora requires valid SSL certs.

Si puedo seguir desde diaspora a<EMAIL_ADDRESS>[cuenta normal]
<EMAIL_ADDRESS>[cuenta foro]

It is very difficult to troubleshoot something for which there is not an adequate description or supporting information. Was a webfinger attempted from joindiaspora to the Redmatrix channel and/or is the channel known on joindiaspora? Was a friend request sent? What do your site logs say about these events? What were the results in the UI and/or error messages on either side? Due to past history with Diaspora communications, we don't consider this to be a Redmatrix issue unless you can show that communication actually reached Redmatrix and that Redmatrix provided incorrect responses; and the lack of a valid SSL cert is the very first thing that needs fixing before we can troubleshoot it further. Unfortunately, if you present such an issue to Diaspora they will probably tell you that a) valid certs are required, and b) joindiaspora.com is a large pod that often has "federation issues" (in other words, communications randomly fail for no apparent reason).

Desde diaspora a Redmatrix funciona.

Cuenta normal.
Y desde redmatrix he agregado<EMAIL_ADDRESS>perfectamente.
Conexión mutua.  log  > http://text0.tk/1748
El problema:
Desde diaspora, no me deja seguir esta cuenta<EMAIL_ADDRESS>[forum]
Diaspora no la encuentra.

That's a known Diaspora bug which affects large pods more than small pods. If you keep attempting it, eventually it "might" work. I use the word "might" because Diaspora uses strict SSL checking and without a valid cert there's a good chance it will never work. So you can keep trying once a day. It has been known to take up to three weeks of trying before it works. If it still hasn't been recognised a month from now, it's probably because of the cert. Why it worked without a valid cert is unknown to me, as this is unsupported and has never worked before. In any event, this is not a redmatrix bug. The probe never made it to your redmatrix server. This is a Diaspora bug.


Upgrade to pydantic v2

Description:

Upgrade to using pydantic v2, dropping support for v1.
Closes #308
I originally intended for this change to incorporate support for both v1 and v2, but I don't see the point.
Indeed, v1 is (for now) kept in the pydantic library under a special v1 module - so another way of "upgrading" to support pydantic v2 would be to simply add this to the import statements from pydantic.
But using the new classes and updated system utilizes the underlying rust implementations for effeciency improvements, as well as ensures updated support for future v2 releases.
One thing I've come across now is pylint's inability to understand pydantic models' field values.
I suggest to switch out pylint usage with ruff instead. It is much faster, supports pydantic v2, but does not have the complete ruleset that exists in pylint, however. Using mypy helps a lot, though. For more information see here.
Type of change:

[ ] Bug fix.
[ ] New feature.
[ ] Documentation update.

Checklist for the reviewer:

This checklist should be used as a help for the reviewer.

[ ] Is the change limited to one issue?
[ ] Does this PR close the issue?
[ ] Is the code easy to read and understand?
[ ] Do all new feature have an accompanying new test?
[ ] Has the documentation been updated as necessary?

Codecov Report
Patch coverage: 84.93% and project coverage change: -1.09% :warning:

Comparison is base (5a4c5cb) 82.17% compared to head (1950dd5) 81.09%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #330      +/-   ##
==========================================
- Coverage   82.17%   81.09%   -1.09%
==========================================
  Files          44       44
  Lines        1212     1222      +10
==========================================
- Hits          996      991       -5
- Misses        216      231      +15

Flag
Coverage Δ

linux
81.09% <84.93%> (-1.00%)
:arrow_down:

linux-extra_libs
?

windows
?

windows-extra_libs
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

oteapi/strategies/download/https.py
92.00% <ø> (ø)

oteapi/strategies/transformation/celery_remote.py
82.05% <71.42%> (+0.47%)
:arrow_up:

oteapi/strategies/parse/postgres.py
80.95% <73.91%> (-5.42%)
:arrow_down:

oteapi/models/genericconfig.py
77.52% <77.58%> (-9.49%)
:arrow_down:

oteapi/strategies/parse/application_vnd_sqlite.py
93.61% <80.00%> (-1.94%)
:arrow_down:

oteapi/models/__init__.py
100.00% <100.00%> (ø)

oteapi/models/resourceconfig.py
100.00% <100.00%> (ø)

oteapi/models/secretconfig.py
100.00% <100.00%> (ø)

oteapi/models/triplestoreconfig.py
100.00% <100.00%> (ø)

oteapi/plugins/factories.py
97.43% <100.00%> (+0.13%)
:arrow_up:

... and 10 more

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

I'm getting second thoughts about completely dropping pydantic v1 support. But I'm afraid supporting both major versions will be an implementation nightmare with an extreme amount of conditional statements, which are essentially throw-away work, since once the majority of libraries have implemented support for pydantic v2, then all of that work should be reverted.

@daniel-sintef Would it be possible for you to review the parts affecting the postgres parser strategy? I have implemented quite a few changes here to support pydantic v2 as well as trying to "simplify" and minimize the code a bit.

@Treesarj I'll leave the major over-all review to you :)

(...) Do add the helper function I suggested unless the other reviewers have objections

If you meant this, then it's already added in bcb7101.

Please add in tests for values, clear & update for the generic config


animation of artwork details is messy

on artwork details page when the ipad is rotated the righthand column details float across the artwork in a white box, looks buggy

Pretty sure this has come up before, but searching issues came up empty.
Estimate: 1/2 day.


Browsers do not support \A or \Z, but rails recommends them

So translate to something close that the browser supports

@singpolyma can you please add a test for this change? :)

@lucasmazza test added


Enable "entering" a workspace shell

In the spirit of:

https://nixos.org/manual/nix/stable/command-ref/nix-shell.html
https://docs.python.org/3/library/venv.html#how-venvs-work

It would be great to provide our users with a way to "enter" a workspace from their shell.
This would make the tool available in their shell directly as a normal command.
Today, Shims provide this feature but they are installed system-wide (in the HOME user dir) instead of being scoped in each workspace.
Proposition
First thing we need to do is write a bash script that would be source-ed later because the wow process cannot change environment variables that would "outlives" it. That means, if we call std::set_env we just rewrite them for the life of the program, but we want our changes to be persisted in the user's shell.
Option 1: Add aliases
The script just add aliases.
Option 2: Binaries in a hidden file
We use the Shims (i.e. bash scripts that act as an alias to wow run) but we install them in a .wow/bin file in the workspace (instead of the HOME dir), then wow shell  would source the .wow/activate.

I actually think it wouldn't even work if we do it this way.
We would more likely need to run the user shell as a sub-process or let them source the activate 😒

We don't need to enter a shell because of the current behaviour of wow that fallbacks to skipping the shims when not in a workspace.


doc: Documentation issue in 'develop/west/basics'

Describe the bug
I'm still confused and unsure, what a "Workspace" in West/Zephyr means, after reading the documentation. Assume, I'm working on a local PC, working for different customers, developing Zephyr based firmware for the different customers.
Intuitively, I would create a git repository for every customer-project (using this term to not confuse this with west-project) and would add Zephyr as git submodule. So, every customer-project could have its different version of Zephyr.
https://docs.zephyrproject.org/latest/develop/west/workspaces.html#west-workspaces claims to describe the workspace concept in more details, but then starts to describe implementation details about projects.
So, what is a Workspace? When do I need one? How do I collaborate with others, using Workspaces? How are workspaces and projects related? What part of a workspace belongs into a git repository?
Maybe, this questions could be answered, if we are looking at build artifacts and versions? Assumes, I have a customer project with 3 different hex files, containing the firmware for 3 different microcontrollers. Each µC firmware uses Zephyr, but not necessary the very same version. There are a few source code libraries used by all firmwares and unit tests for that libraries running on the build PC. One additional artifact could be a zip file containing the 3 hex files.
And, of cause, I would use a CI for the official build and for that, I would need a minimum command line, that would build and run the unit tests and the zip file.
How would that map to West/Zephyr workspaces and projects?
Thanks in advance,
Torsten
Environment

Page: develop/west/basics
Version: main
SHA-1: 2cfdfad2e238f61aad0608ad35c2a6bb710f957e

Well, I've reported my Issue with the page. As a newbie with Zephyr, but plenty of experience in embedded SW development, I had really problems to gasp the basic concepts. Terms like "Workspace", "Project" etc. are very generic and are overloaded thousand times with different meanings and concepts. Describing these terms in a Zephyr context would probably had helped. I would have offered help to improve the documentation, but I still don't have a clear view as how to answer my questions from above.

There is no need to close it under any circumstances. This is a very convenient position - to write a complex product, “everything works for me, you all (insert definition).” I would like to receive an answer to the question posed.

The stale bot runs automatically, I will try to address this soon.


add an ix subcommand to sync the test corpus to local

The test corpus frequently changes, and running a complete ix test requires it in its entirety. Using ad-hoc tools to sync the corpus is easy, but annoying and inconsistent. It would be very straightforward to implement an ix sync-test-corpus command or some such to remove this hassle.

closed by 999054c


Propagate error to app

This PR is trying to propagate the errors from background by:

create a class JsonRpcProviderError to differentiate other errors
add try catch to every await function

Note:

Send request via Message to Background provider.
If fetch().json().error is present, create and throw a JsonRpcError with fetch().json().
Send the JsonRpcError.unwrap() error as a regular response to the Popup in Message.
ethers.js will detect the invalid value and trigger an error such as invalid BigNumberish value.


perf(rpc): improve gas price perf by skipping hash

we always have the latest hash, which makes it redundant to compute the hash on every gas price call.
this adds header_by_id and sealed_header_by_id functions

Codecov Report

Merging #2657 (a6c8a5b) into main (a0b6b20) will decrease coverage by 31.97%.
The diff coverage is 2.89%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##             main    #2657       +/-   ##
===========================================
- Coverage   71.47%   39.51%   -31.97%
===========================================
  Files         500      500
  Lines       64381    64439       +58
===========================================
- Hits        46019    25463    -20556
- Misses      18362    38976    +20614

Flag
Coverage Δ

integration-tests
?

unit-tests
39.51% <2.89%> (-26.92%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/blockchain-tree/src/shareable.rs
28.26% <0.00%> (-10.38%)
:arrow_down:

crates/interfaces/src/blockchain_tree.rs
61.53% <0.00%> (-20.28%)
:arrow_down:

crates/rpc/rpc/src/eth/gas_oracle.rs
3.07% <0.00%> (-27.46%)
:arrow_down:

crates/storage/provider/src/test_utils/mock.rs
7.76% <0.00%> (-19.30%)
:arrow_down:

crates/storage/provider/src/test_utils/noop.rs
2.28% <0.00%> (-31.45%)
:arrow_down:

crates/storage/provider/src/traits/block.rs
14.81% <0.00%> (-6.24%)
:arrow_down:

crates/storage/provider/src/providers/mod.rs
11.84% <5.00%> (-2.55%)
:arrow_down:

... and 298 files with indirect coverage changes


proposal: SendActivity should take a string or activity

To get a little close back to the simplicity we had with Reply() I'd like to propose that we let SendActivity() take either an Activity or a string. When a string is passed a new activity of type message will be composed and delivered.

I’m surprised that’s not there. I added that code not long ago, and tested it.
Not clear yet how it got removed.

From: Steven Ickman<EMAIL_ADDRESS>Sent: Sunday, March 4, 2018 12:10:08 PM
To: Microsoft/botbuilder-dotnet
Cc: Subscribed
Subject: [Microsoft/botbuilder-dotnet] proposal: SendActivity should take a string or activity (#245)
To get a little close back to the simplicity we had with Reply() I'd like to propose that we let SendActivity() take either an Activity or a string. When a string is passed a new activity of type message will be composed and delivered.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fbotbuilder-dotnet%2Fissues%2F245&data=04|01|cmullins%40microsoft.com|b88966fd2ebf4bebad1d08d5820bee98|72f988bf86f141af91ab2d7cd011db47|1|0|636557910116760026|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-2&sdata=h%2FJo8THQKLw4HfxAUgmsPzuorRMucCpzpJf5ZVO0o6U%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABHICTrgRjSw5RjUkplJHQHr9k1duGppks5tbEoggaJpZM4Sbelm&data=04|01|cmullins%40microsoft.com|b88966fd2ebf4bebad1d08d5820bee98|72f988bf86f141af91ab2d7cd011db47|1|0|636557910116760026|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-2&sdata=afznFm2KjB%2BWmMYSPW8TyWRiYWEVZpE9TWMgsowv1CU%3D&reserved=0.

I actually didn't look at the C# version of SendActivity(). The JS version I created doesn't support passing in a string yet but it feels like it should.

And to be clear I'm talking about at the BotContext level.  At the adapter level I think it should continue to speak raw activities because it needs to know the conversation reference info.

@cleemullins do you still have the code? If not I am happy to add this and raise a PR if it helps?

The code looks like it was moved into the BotFrameworkAdapter. I need to put a plan together for how to approach the Single Middleware refactoring this week, and this seems like part of that.

Just trying to do some tidying up where I can of any issues - this specific issue is handled by @cleemullins M2 branch and the ability to pass an activity or a string is present, so this will be resolved when that gets merged in.  Given that this was just a discussion point, not sure we need to keep this open?

This is done.  Current SendActivity takes either text or an IActivity.
Current SendActivities takes an array of IActivity to support batching.


POL-156 update azure readme

Description
update the Azure policies missing instructions for creds.
Issues Resolved
[List any existing issues this PR resolves]
Contribution Check List

[ ] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[ ] New functionality has been documented in CHANGELOG.MD

          2 Errors

:no_entry_sign:
compliance/azure/instances_without_fnm_agent/README.md:46: MD005 Inconsistent indentation for list items at the same level
compliance/azure/instances_without_fnm_agent/README.md:49: MD005 Inconsistent indentation for list items at the same level
compliance/azure/instances_without_fnm_agent/README.md:52: MD005 Inconsistent indentation for list items at the same level
compliance/azure/instances_without_fnm_agent/README.md:24: MD026 Trailing punctuation in header
compliance/azure/instances_without_fnm_agent/README.md:32: MD026 Trailing punctuation in header
compliance/azure/instances_without_fnm_agent/README.md:34: MD032 Lists should be surrounded by blank lines
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
operational/azure/vms_without_managed_disks/README.md:33: MD022 Headers should be surrounded by blank lines
operational/azure/vms_without_managed_disks/README.md:36: MD022 Headers should be surrounded by blank lines
operational/azure/vms_without_managed_disks/README.md:39: MD022 Headers should be surrounded by blank lines
operational/azure/vms_without_managed_disks/README.md:42: MD022 Headers should be surrounded by blank lines
operational/azure/vms_without_managed_disks/README.md:34: MD032 Lists should be surrounded by blank lines
operational/azure/vms_without_managed_disks/README.md:37: MD032 Lists should be surrounded by blank lines
operational/azure/vms_without_managed_disks/README.md:40: MD032 Lists should be surrounded by blank lines
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

  Generated by :no_entry_sign: Danger


Bot attaches images to messages without input

After asking any question, the bot will automatically edit the message and add an AI-generated image several minutes later. It seems to happen on all responses sent by the bot.

yeah. super annoying. hopefully this gets fixed.

You can disable it by setting "USE_EMBED" to false.

where would that option be?


dfs-cli 'kv get' does not show JSON kv content correctly due to bare " in non-quoted-field error

Describe the bug
I uploaded Kenya and Estonia maps and tried to see the data but JSON values are not shown correctly in dfs-cli.
To Reproduce
dfs@korrrba >>>pod ls
<Pod>:  korrrba_kenya_map_pod
<Pod>:  korrrba_estonia_map_pod
<Pod>:  FairMaps
<Shared Pod>:  map_sw
<Shared Pod>:  map-registry-7e1c3b67bb47
<Shared Pod>:  map_cz
<Shared Pod>:  map_slovenia
<Shared Pod>:  map_slovenia_1
<Shared Pod>:  map_belgium_1
<Shared Pod>:  map-registry-6389c467fcf4
<Shared Pod>:  map-registry-ad442a613c17
dfs@korrrba >>>pod open korrrba_kenya_map_pod
Please enter your password:
pod opened successfully
dfs@korrrba >>> korrrba_kenya_map_pod >> / > kv open kenya_map
kv store opened
dfs@korrrba >>> korrrba_kenya_map_pod >> / > kv get kenya_map 7_77_63
kv get:  line 1, column 1: bare " in non-quoted-field
dfs@korrrba >>> korrrba_kenya_map_pod >> / > kv get kenya_map 5_1_1
kv get:  line 1, column 1: bare " in non-quoted-field
dfs@korrrba >>> korrrba_kenya_map_pod >> / >

Expected behavior
kv get displays the JSON data correctly
Additional context
I already have a fix for this, will submit a small PR.

@tfius @darkobas2 does this issue look similar to https://github.com/fairDataSociety/fairOS-docs/issues/8?


Old content being animated, then replaced with new animation and content

Not sure how to go about fixing this. Is it a timing issue perhaps?
I have a pretty simple setup. I'm using Animate.css and SlideInRight for the animated content and FadeIn for the is-exiting animation.
The content fades out, as expected, but sometimes the same (ie. old) content is then slide in from the right, only to be replaced moments later by the correct, new, content sliding in from the right.
What do I need to tweak to make these transitions work correctly? Obviously I only want the slideInRight animation to fire once the new page content is actually loaded. What I can do about this? (Perhaps there's a way I can only fire the slideInRight from onEnd?)
Thanks.

use onProgress to hide the current content (e.g. opacity:0) or hide using Js or
even toggleClass ('hide')
CSS
.hide{visibility:hidden}
onProgress : {
    duration: 0, // Duration of the animations, if any.
    render: function (url, $container) {
        $('container').hide();
    }
},

Ah! Of course. That works great. Thanks soo much.

How to integrate smooth state.js with backbone.js to get the transition between view navigation.It will be very helpful for me to integrate transition in my app..
If you have any exmple code please share it

I have the same situation @balajiram, have you found a way?

@balajiram please open a new issue for your question.
@JohnnyWalkerDesign has this helped you out? Can this be closed?


Use shared.SnapshotDelimiter to split name components

Signed-off-by: Michael McCracken<EMAIL_ADDRESS>

Closing because @pcdummy 's upcoming branch removes storageForContainer, which seems fine to me.


Delete DirectMainProcessExtensionHostStarter and shared process setup

Once we get confidence in the launching of the extension host from the main process, clean up other implementations of IExtensionHostStarter.

Done.


Fix RoomCard styles

in my offense i couldn't test the component without putting it in Home.tsx with a dummy room data

It's only shown in debug mode


[WIP] Add a web interface for easy setup

Before we open TestNet, we need an easy to use, mobile-friendly web interface
so that first-timer can easily configure their node.
Additionally, we also want to provide a web interface for monitoring and administration.

Note: This uncovered a few issues with the configuration and the way we do things.
So I'm going to do a few refactor in the near future.
Additionally, there are still some issues with the interface itself:

It is not complete (the almost full design can be seen here.
The full design was missing a couple things we'll need to add (e.g. initial sync information);
We are missing assets (@bpalaggi  will contact the agency about this);
There is no feedback on user error: if the configuration is incorrect, the alert is quite useless;
There's a lot of hacky code to work around small differences;

Things we should do:

Clear up the configuration parsing so that optional things are really optional;
Directly write YAML on the JS side: this will make things so much simpler: we can just reuse our YAML parser and provide proper error handling, and we don't even have to load a file from disk;
Clean up the diet templates / CSS: there have been many iterations, and the code improved with my understanding of HTML/CSS/JS;
Add bootstrap here so the installation is self-sufficient (?);

Superseded by #1984


added proof that a square made of 2 hid's commutes

Sorry for taking so long to merge this, I've been swamped.


Cannot delete v2 files

SDK version: 3.0.4
Platform: Web (JS)
Whenever you try to delete a file using the deleteFile method, it throws the following error:
Cannot read properties of undefined (reading 'owner-account-pubkey')

That is when attempting to delete a file stored on a v2 storage account using the following method call:
deleteFile(account, url, 'v2')

Now, when trying to delete a file stored on a v1 storage account using the deleteFile method and passing the v2 version as the parameter as:
deleteFile(account, url, 'v2')

It throws the following error:
Invalid account discriminator

However, when trying setting the version to v1 as:
deleteFile(account, url, 'v1')

To further attempt to delete a file stored on a v1 storage account, the signature request pops up, and when approving it, the file gets successfully deleted, which makes sense as its a file stored on a v1 storage account.
What it's weird is that it worked with a signature request (not a transaction) and it's a v1 file, and v2 files are failing with either the v1 and v2 parameters.

This should be resolved!


[stm32f7] Fix RCC registers

Following #612, fix fields  in RCC for every F7 chips

Could you rebase this now that #612 is merged, please?

Could you rebase this now that #612 is merged, please?

This should be good to go.
Should I ping you when things are ready for others PRs to merge or you just don't have much time to look at them but get the notifications?

Thanks! I don't mind being pinged but do get the notifications; I've been on holiday the last week but I'm back today so will be going through these last couple of PRs in the next day or two.

ugh, bors seems to have gotten stuck?
bors cancel

bors r+


Parametrized tests?

I was checking out cargo test on metal and all non-f64 tests pass 🎉
Going forward, I think tests parametrized on dtype and Device (include/exclude via test params?) would make for a DRY yet granular foundation. I'm no expert in rust fixtures, but saw rstest and macro approaches.
Do you have any opinion on that?

Having trouble on windows ci with f64 as well. I'm developing on Ubuntu and that works fine.
For machine learning, I don't plan to use f64 but I thought it would be useful for general purpose computation. I was hoping to support 16 bit floats as well at some point, particularly bf16.
I thought about using macros to define the tests separately per type, that makes sense, I just neglected that for simplicity.
The main issue is that the tests should all pass, or fail. I'm not thrilled to have only partial support for certain things. Unless there's a fix I may decide to remove f64 for now.


Push Your ABAP Source Code from SAP BTP, ABAP Environment to a GitHub Repository using abapGit

Tutorials: https://developers.sap.com/tutorials/abap-environment-abapgit-transfer.html
Hello,
I recently revisited this tutorial and encountered a couple of additional screens that I don't recall seeing previously (Branch/package and folder logic selection). This could be specific to my repository, which is brand new, or it might indicate changes since the last time I completed this tutorial. If you confirm that there have been updates, I would be happy to create a pull request to include these new screens in the tutorial.
I look forward to your response.
Best regards,
Rafael

Hi @rcaziraghi ,
I tested this tutorial and the steps are still the same. Maybe you need to try it out again.
The respository I created is private.
If you still encounter issues, feel free to contact us again.
Best regards,
Merve


Flutter  3.22.0 version solving failed

In the new version of Flutter, pub get throws an error
Because json_schema2 >=2.0.2+9 <2.0.2+10 depends on rest_client ^2.1.5 and json_schema2 >=2.0.2+10 <2.0.2+11 depends on rest_client ^2.1.5+1, json_schema2 >=2.0.2+9 <2.0.2+11 requires rest_client ^2.1.5.
And because json_schema2 >=2.0.2+11 <2.0.2+12 depends on rest_client ^2.1.5+2, json_schema2 >=2.0.2+9 <2.0.2+12 requires rest_client ^2.1.5.
And because json_schema2 >=2.0.2+12 <2.0.2+13 depends on rest_client ^2.1.5+3 and json_schema2 >=2.0.2+13 <2.0.2+14 depends on rest_client ^2.1.5+4, json_schema2 >=2.0.2+9 <2.0.2+14 requires rest_client ^2.1.5.
And because json_schema2 >=2.0.2+14 <2.0.2+15 depends on rest_client ^2.1.5+5 and json_schema2 >=2.0.2+15 <2.0.2+16 depends on rest_client ^2.2.0, json_schema2 >=2.0.2+9 <2.0.2+16 requires rest_client ^2.1.5.
And because json_schema2 >=2.0.2+16 <2.0.2+17 depends on rest_client ^2.2.0+1 and json_schema2 >=2.0.2+17 <2.0.2+18 depends on rest_client ^2.2.0+2, json_schema2 >=2.0.2+9 <2.0.2+18 requires rest_client ^2.1.5.
And because json_schema2 >=2.0.2+18 <2.0.2+19 depends on rest_client ^2.2.0+3 and json_schema2 >=2.0.2+19 <2.0.2+20 depends on rest_client ^2.2.0+6, json_schema2 >=2.0.2+9 <2.0.2+20 requires rest_client ^2.1.5.
And because json_schema2 >=2.0.2+20 <2.0.2+21 depends on rest_client ^2.2.0+7 and json_schema2 >=2.0.2+21 <2.0.3+1 depends on rest_client ^2.2.0+8, json_schema2 >=2.0.2+9 <2.0.3+1 requires rest_client ^2.1.5.
And because json_schema2 >=2.0.3+1 <2.0.3+2 depends on rest_client ^2.2.1+1 and json_schema2 >=2.0.3+2 <2.0.3+3 depends on rest_client ^2.2.1+2, json_schema2 >=2.0.2+9 <2.0.3+3 requires rest_client ^2.1.5.
And because json_schema2 >=2.0.3+3 <2.0.3+4 depends on rest_client ^2.2.1+3 and json_schema2 >=2.0.3+4 <2.0.3+5 depends on rest_client ^2.2.1+4, json_schema2 >=2.0.2+9 <2.0.3+5 requires rest_client ^2.1.5.
And because json_schema2 >=2.0.3+5 <2.0.3+6 depends on rest_client ^2.2.1+5 and json_schema2 >=2.0.3+6 <2.0.3+7 depends on rest_client ^2.2.1+6, json_schema2 >=2.0.2+9 <2.0.3+7 requires rest_client ^2.1.5.
And because json_schema2 >=2.0.3+7 <2.0.4+1 depends on rest_client ^2.2.1+7 and json_schema2 >=2.0.4+1 <2.0.4+2 depends on rest_client ^2.2.1+8, json_schema2 >=2.0.2+9 <2.0.4+2 requires rest_client ^2.1.5.
And because json_schema2 >=2.0.4+4 <5.1.2 depends on rest_client ^2.2.1+11 and json_schema2 >=2.0.4+3 <2.0.4+4 depends on rest_client ^2.2.1+10, json_schema2 >=2.0.2+9 <2.0.4+2 or >=2.0.4+3 <5.1.2-∞ requires rest_client ^2.1.5.
And because json_schema2 >=2.0.4+2 <2.0.4+3 depends on rest_client ^2.2.1+9 and rest_client >=2.1.4+8 <2.2.1+11 depends on http ^0.13.5, json_schema2 >=2.0.2+9 <5.1.2 requires http ^0.13.5 or rest_client ^2.2.1+11.
Because no versions of polkadart match >0.4.3 <0.5.0 and polkadart 0.4.3 depends on http ^1.1.0, polkadart ^0.4.3 requires http ^1.1.0.
Thus, if polkadart ^0.4.3 and json_schema2 >=2.0.2+9 <5.1.2 then rest_client ^2.2.1+11.
And because substrate_metadata 1.2.0 depends on json_schema2 ^2.0.2+9, if polkadart ^0.4.3 and substrate_metadata 1.2.0 then rest_client ^2.2.1+11.
And because no versions of substrate_metadata match >1.2.0 <2.0.0 and rest_client >=2.2.1+10 depends on intl ^0.18.1, if polkadart ^0.4.3 and substrate_metadata ^1.2.0 then intl ^0.18.1.
And because taler depends on flutter_localizations from sdk which depends on intl 0.19.0, polkadart ^0.4.3 is incompatible with substrate_metadata ^1.2.0.
So, because taler depends on both polkadart ^0.4.3 and substrate_metadata ^1.2.0, version solving failed.
[✓] Flutter (Channel stable, 3.22.0, on macOS 14.4 23E214 darwin-arm64, locale en-RU)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.3)
[✓] VS Code (version 1.89.1)
[✓] Connected device (4 available)
! Error: Browsing on the local area network for iPhone. Ensure the device is unlocked and attached with a cable or associated with the same local area
network as this Mac.
The device must be opted into Developer Mode to connect wirelessly. (code -27)
! Error: Browsing on the local area network for Apple Watch — Степан. Ensure the device is unlocked and discoverable via Bluetooth. (code -27)
[✓] Network resources

I belive this could root cause for my error as well
➜  polkadart git:(main) ✗ dart run packages/polkadart_cli/bin/generate.dart
Unhandled exception:
ConfigException: Failed to extract config from the 'pubspec.yaml' file.
Can't find 'polkadart' section.
#0      new PubspecConfig.fromYAML (package:polkadart_cli/src/config/pubspec_config.dart:45:7)
#1      new PubspecConfig.fromPubspecFile (package:polkadart_cli/src/config/pubspec_config.dart:30:26)
#2      main (file:///Users/uddyami.agrawal/Raise/polkadart/packages/polkadart_cli/bin/generate.dart:52:32)
#3      _delayEntrypointInvocation.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:295:33)
#4      _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:184:12)

I don't have this problem on my stack.
polkadart depends on http ^1.1.0, while json_schema2 depends on http ^0.13.5 due to rest_client; these two versions of http are incompatible, indicating that json_schema2 is outdated.


i don't understand what happened

i don't understand what happened

You don't seem to have git in the PATH, a lot of flake stuff requires it

should i use flakes for install nixvim?

It is not required, we provide a compatibilty layer if you are not using flakes

@Zm94ZGV2 were you able to solve your problem ?


Support different footer_background_image for landscpe and portrait page orientation

Hi,
when I switch page orientation for individual pages (using [.landscape] and [.portrait]) I also want to set a new background image for that page(s).
The new image should respect the wider aspect without being scaled vertically like now.
Best would be in my opinion if it'd be possible to define different images in the theme yaml (e.g. footer_background_image as default and optionally footer_background_image_portrait and footer_background_image_landscape).
Thanks in advance
Thomas

We substitute attribute references in the target of the image macro (i.e., the image path). So what we could do is temporary define and attribute to represent the page orientation. Then, you could use this attribute reference in the image path so that you get the image that matches the layout.
For example:
footer:
  background-image: image:footer-bg-{current-page-layout}.png[]

wdyt?

Thank you for picking my issue.
Do I understand correctly that additionally to the switch of the page orientation an author has to set the attribute in the document?
I'm not sure if I would prefer that way as it would be redundant work.
What if you just look for files that end with '-portrait.png' or '-landscape.png' in addition to the default '*.png'. By convention over coding this would minimize the fault risk on the authors side and gives theme authors full control over their design.

Do I understand correctly that additionally to the switch of the page orientation an author has to set the attribute in the document?

No, it would be dynamic.

What if you just look for files that end with '-portrait.png' or '-landscape.png' in addition to the default '*.png'.

That feels like too much magic to me and is not how any other part of the converter works. It's better to require that it be a dynamic segment of the path.

Now then. I'm convinced you're much more familiar in all those mechanisms than I do.
I'm still in the beginning using this great authoring tool.
Would be great having a tiny working example for better understanding when you're done.
Greets
Thomas

Hi @mojavelinux ,
I spent some thoughts about your suggestion. I think now I understand it right ;-)
If I configure the image resource in the template as you suggested I only have to put two image files into the template directory:
1. footer-bg-portrait.png[]
2. footer-bg-landscape.png[]

When the converter recognizes {current-page-layout} in the resource definition it automatically replaces it according to the current page layout.
That would really be a perfect solution!
Sorry for my lack of understanding as of yesterday.
Greets
Thomas

Hi @mojavelinux ,
hoping you're well and in good health this times.
I tried this enhancement using v1.5.3 without success.
In my theme I've got footer_background_image: image:images/footerBackground-{page-layout}.png[] having two files in the directory images:

footerBackground-portrait.png
footerBackground-landscape.png

Building the PDF I got the following INFO message:
asciidoctor: WARN: footer background image not found or readable: /home/thucke/devJava/dokumentation/betriebskonzept/src/main/resources/themes/images/footerBackground-{page-layout}.png
What am I doing wrong?
Greets
Thomas

I tried this enhancement using v1.5.3 without success.

It's not available in 1.5.3. It has been solved in the upcoming 2.0.0 release.

Thank you. I  thought the merge was already in version 1.5.3.

If you would be willing to test master, that would ensure it's right when 2.0.0 is released. (Instructions in https://github.com/asciidoctor/asciidoctor-pdf/blob/master/CONTRIBUTING-CODE.adoc).


[BUG] Docker release build fails on branch-22.06

Describe the bug
Docker release build fails
"No module named pybind11_stubgen"
23 303.8 [152/161] Building stub for python module morpheus._lib.cudf_helpers...
#23 303.8 FAILED: morpheus/_lib/cudf_helpers/__init__.pyi /opt/conda/conda-bld/morpheus-split-22.04.00/work/build-conda/morpheus/_lib/cudf_helpers/__init__.pyi
#23 303.8 cd /opt/conda/conda-bld/morpheus-split-22.04.00/work/build-conda && /opt/conda/conda-bld/morpheus-split-22.04.00/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/bin/python3.8 -m pybind11_stubgen morpheus._lib.cudf_helpers --no-setup-py --log-level WARN -o ./ --root-module-suffix ""
#23 303.8 /opt/conda/conda-bld/morpheus-split-22.04.00/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/bin/python3.8: No module named pybind11_stubgen
#23 303.8 [153/161] Building stub for python module morpheus._lib.stages...
#23 303.8 FAILED: morpheus/_lib/stages/__init__.pyi /opt/conda/conda-bld/morpheus-split-22.04.00/work/build-conda/morpheus/_lib/stages/__init__.pyi
#23 303.8 cd /opt/conda/conda-bld/morpheus-split-22.04.00/work/build-conda && /opt/conda/conda-bld/morpheus-split-22.04.00/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/bin/python3.8 -m pybind11_stubgen morpheus._lib.stages --no-setup-py --log-level WARN -o ./ --root-module-suffix ""
#23 303.8 /opt/conda/conda-bld/morpheus-split-22.04.00/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/bin/python3.8: No module named pybind11_stubgen
#23 303.8 [154/161] Building stub for python module morpheus._lib.messages...
#23 303.8 FAILED: morpheus/_lib/messages/__init__.pyi /opt/conda/conda-bld/morpheus-split-22.04.00/work/build-conda/morpheus/_lib/messages/__init__.pyi
#23 303.8 cd /opt/conda/conda-bld/morpheus-split-22.04.00/work/build-conda && /opt/conda/conda-bld/morpheus-split-22.04.00/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/bin/python3.8 -m pybind11_stubgen morpheus._lib.messages --no-setup-py --log-level WARN -o ./ --root-module-suffix ""
#23 303.8 /opt/conda/conda-bld/morpheus-split-22.04.00/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/bin/python3.8: No module named pybind11_stubgen
#23 303.8 [155/161] Building stub for python module morpheus._lib.common...
#23 303.8 FAILED: morpheus/_lib/common/__init__.pyi /opt/conda/conda-bld/morpheus-split-22.04.00/work/build-conda/morpheus/_lib/common/__init__.pyi
#23 303.8 cd /opt/conda/conda-bld/morpheus-split-22.04.00/work/build-conda && /opt/conda/conda-bld/morpheus-split-22.04.00/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/bin/python3.8 -m pybind11_stubgen morpheus._lib.common --no-setup-py --log-level WARN -o ./ --root-module-suffix ""
#23 303.8 /opt/conda/conda-bld/morpheus-split-22.04.00/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/bin/python3.8: No module named pybind11_stubgen
#23 303.8 [156/161] Building stub for python module morpheus._lib.file_types...
#23 303.8 FAILED: morpheus/_lib/file_types/__init__.pyi /opt/conda/conda-bld/morpheus-split-22.04.00/work/build-conda/morpheus/_lib/file_types/__init__.pyi
#23 303.8 cd /opt/conda/conda-bld/morpheus-split-22.04.00/work/build-conda && /opt/conda/conda-bld/morpheus-split-22.04.00/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/bin/python3.8 -m pybind11_stubgen morpheus._lib.file_types --no-setup-py --log-level WARN -o ./ --root-module-suffix ""
#23 303.8 /opt/conda/conda-bld/morpheus-split-22.04.00/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/bin/python3.8: No module named pybind11_stubgen
#23 303.8 ninja: build stopped: subcommand failed.
#23 304.2 Traceback (most recent call last):
#23 304.2   File "/opt/conda/bin/conda-mambabuild", line 10, in <module>
#23 304.2     sys.exit(main())
#23 304.2   File "/opt/conda/lib/python3.8/site-packages/boa/cli/mambabuild.py", line 239, in main
#23 304.2     call_conda_build(action, config)
#23 304.2   File "/opt/conda/lib/python3.8/site-packages/boa/cli/mambabuild.py", line 211, in call_conda_build
#23 304.2     result = api.build(
#23 304.2   File "/opt/conda/lib/python3.8/site-packages/conda_build/api.py", line 186, in build
#23 304.2     return build_tree(
#23 304.2   File "/opt/conda/lib/python3.8/site-packages/conda_build/build.py", line 3088, in build_tree
#23 304.2     packages_from_this = build(metadata, stats,
#23 304.2   File "/opt/conda/lib/python3.8/site-packages/conda_build/build.py", line 2371, in build
#23 304.2     newly_built_packages = bundlers[pkg_type](output_d, m, env, stats)
#23 304.2   File "/opt/conda/lib/python3.8/site-packages/conda_build/build.py", line 1616, in bundle_conda
#23 304.2     utils.check_call_env(interpreter_and_args + [dest_file],
#23 304.2   File "/opt/conda/lib/python3.8/site-packages/conda_build/utils.py", line 410, in check_call_env
#23 304.2     return _func_defaulting_env_to_os_environ('call', *popenargs, **kwargs)
#23 304.2   File "/opt/conda/lib/python3.8/site-packages/conda_build/utils.py", line 390, in _func_defaulting_env_to_os_environ
#23 304.2     raise subprocess.CalledProcessError(proc.returncode, _args)
#23 304.2 subprocess.CalledProcessError: Command '['/usr/bin/bash', '-e', '/opt/conda/conda-bld/morpheus-split-22.04.00/work/morpheus_build.sh']' returned non-zero exit status 1.
------
error: failed to solve: executor failed running [/bin/bash -c source activate base &&    MORPHEUS_ROOT=/workspace CONDA_BLD_PATH=/opt/conda/conda-bld CONDA_ARGS="--no-test" ./ci/conda/recipes/run_conda_build.sh morpheus]: exit code: 1

Steps/Code to reproduce bug
 eval `ssh-agent -s`
 ssh-add
 ./docker/build_container_release.sh

Expected behavior
Successful docker image build.
Environment overview (please complete the following information)

Environment location: [Bare-metal]
Method of Morpheus build: [Docker from source]

Environment details
Please run and paste the output of the morpheus/scripts/print_env.sh script here, to gather any other relevant environment details
Additional context
Built at 36af32cc9c2954203a018755f0e59075078c318a

Closed by #164


rs2_transform_point_to_point

D435
Transform 3D coordinates relative to one sensor to 3D coordinates relative to another viewpoint */
python
color_point = rs.rs2_transform_point_to_point(depth_to_color_extrin, depth_point)
means
one sensor what it means from 3D depth point to 3D color point
is it possible to do other way around: 3D color point to 3D depth point
if yes how

As mentioned in the documentation, the function can transform from any viewpoint to any other viewpoint using the extrinsics between them. In your case, you'd want colot_to_depth_extrin, which can be obtained much the same way as the depth_to_color_extrin

but align is doing the same thing. I need to know the difference between align frame and  depth to color extrin

@scizors Align needs rs_transform_point_to_point but also need rs2_deproject_pixel_to_point and rs2_project_point_to_pixel
https://github.com/IntelRealSense/librealsense/blob/v2.24.0/src/proc/align.cpp#L35

@scizors Any other questions about this ticket? Looking forward to your reply. Thanks!

@scizors If no other questions will close it accordingly. Thanks!


High DPI enhancements of .NET 4.7 broke the layout

Windows 10 Creators Updates includes .NET 4.7, which introduced enhancements to high DPI and dynamic DPI support in Windows Forms.
For some reason, these changes have obviously broken layout of GNP. Investigation needed.

Looks like Patch Tuesday fixed it again. And it even looks crisper than ever.

Great news! I'm positive everyone appreciates you keeping tabs on it.


Replace FAX with iAPS in build workflow, instructions and Fastfile

Change file name from build_FAX.yml to build_iAPS.yml
Edit run-name: Build iAPS ${{ github.ref_name }}
--> displays branch name for Actions runs

Only superficial ?

Only superficial ?

Yes, these changes are only cosmetic, to rename from FAX to iAPS. It’s tested and works as expected. Also with current dev, the only known issue is a visual bug for selecting icons. You can still select, but the option are not shown.

The only thing to note is that the workflow file for building was renamed. You will only see it in the Actions tab in GitHub if it is in your default branch. So if someone wants to see this with dev, they CGM an change default to dev. Or wait until it’s in main. This is just how Actions work, you only see the workflows that are present in the default branch on your fork.


chore: require node > 14 for usage

We have already migrated HB to use Node 14 and also changed our nvmrc to use Node 14
This change would require users installing the agent to be on Node 14 to not throw errors when using incompatible APIs like fs/promises which is available only from Node 14.14

:broken_heart: Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2021-10-13T16:14:01.260+0000

Duration: 8 min 34 sec

Commit: 5997f5db0685ea48dc34ab7e3a7931f74baa1bd1

Test stats :test_tube:

Test
Results

Failed
5

Passed
131

Skipped
0

Total
136

Test errors
Expand to view the tests failures
Test / CLI screenshots with device emulation – CLI screenshots with device emulation

no error details
Expand to view the stacktrace
 Error: Failed: "Error SyntaxError: Unexpected end of JSON input could not parse data '{\"type\":\"screenshot/block\",\"_id\":\"71bb77ed1acf85f13f1e8a2ab3cf3401850f7b9d\",\"@timestamp\":1634142061320004.2,\"root_fields\":{\"os\":{\"platform\":\"linux\"},\"package\":{\"name\":\"@elastic/synthetics\",\"version\":\"1.0.0-beta.14\"}},\"blob\":\"/9j/2wBDAAYEBQYFBAYGBQYHBwYIChAKCgkJChQODwwQFxQYGBcUFhYaHSUfGhsjHBYWICwgIyYnKSopGR8tMC0oMCUoKSj/2wBDAQcHBwoIChMKChMoGhYaKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCj/wAARCAFyALQDASIAAhEBAxEB/8QAFQABAQAAAAAAAAAAAAAAAAAAAAj/xAAUEAEAAAAAAAAAAAAAAAAAAAAA/8QAFAEBAAAAAAAAAAAAAAAAAAAAAP/EABQRAQAAAAAAAAAAAAAAAAAAAAD/2gAMAwEAAhEDEQA/AKpAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA'"
    at Env.it (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-jasmine2/build/jasmineAsyncInstall.js:95:24)
    at it (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-jasmine2/build/jasmine/jasmineLight.js:100:21)
    at Suite.<anonymous> (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/__tests__/cli.test.ts:162:3)
    at addSpecsToSuite (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-jasmine2/build/jasmine/Env.js:444:51)
    at Env.describe (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-jasmine2/build/jasmine/Env.js:414:11)
    at describe (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-jasmine2/build/jasmine/jasmineLight.js:88:18)
    at Object.<anonymous> (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/__tests__/cli.test.ts:31:1)
    at Runtime._execModule (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-runtime/build/index.js:1299:24)
    at Runtime._loadModule (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-runtime/build/index.js:898:12)
    at Runtime.requireModule (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-runtime/build/index.js:746:10)

Test / network measure resource and transfer size – network measure resource and transfer size

no error details
Expand to view the stacktrace
 Error: expect(received).toMatchObject(expected)

- Expected  - 1
+ Received  + 1

@@ -4,11 +4,11 @@
    "method": "GET",
    "request": Any<Object>,
    "requestSentTime": Any<Number>,
    "response": Any<Object>,
    "responseReceivedTime": Any<Number>,
-   "status": 200,
+   "status": -1,
    "step": null,
    "timestamp": Any<Number>,
    "timings": Any<Object>,
    "type": "document",
    "url": "http://localhost:36997/index.html",
    at Object.<anonymous> (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/__tests__/plugins/network.test.ts:49:24)

Test / network not include data URL in network info – network not include data URL in network info

no error details
Expand to view the stacktrace
 Error: browser.newBrowserCDPSession: Target page, context or browser has been closedbrowser.newBrowserCDPSession: Target page, context or browser has been closed
    at Function.getUserAgent (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/src/core/gatherer.ts:66:44)
    at Function.setupDriver (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/src/core/gatherer.ts:56:33)
    at Object.<anonymous> (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/__tests__/plugins/network.test.ts:67:35)
    at Object.asyncJestTest (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-jasmine2/build/jasmineAsyncInstall.js:106:37)
    at /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-jasmine2/build/queueRunner.js:45:12
    at mapper (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-jasmine2/build/queueRunner.js:28:19)
    at /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-jasmine2/build/queueRunner.js:75:41

Test / network produce distinct events for redirects – network produce distinct events for redirects

no error details
Expand to view the stacktrace
 Error: browser.newBrowserCDPSession: Target page, context or browser has been closedbrowser.newBrowserCDPSession: Target page, context or browser has been closed
    at Function.getUserAgent (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/src/core/gatherer.ts:66:44)
    at Function.setupDriver (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/src/core/gatherer.ts:56:33)
    at Object.<anonymous> (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/__tests__/plugins/network.test.ts:78:35)
    at Object.asyncJestTest (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-jasmine2/build/jasmineAsyncInstall.js:106:37)
    at /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-jasmine2/build/queueRunner.js:45:12
    at mapper (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-jasmine2/build/queueRunner.js:28:19)
    at /var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/node_modules/jest-jasmine2/build/queueRunner.js:75:41

Test / network should capture network info – network should capture network info

no error details
Expand to view the stacktrace
 Error: response.securityDetails: Target page, context or browser has been closedresponse.securityDetails: Target page, context or browser has been closed
    at NetworkManager._onResponse (/var/lib/jenkins/workspace/nt-rum_elastic-synthetics_PR-397/src/github.com/elastic/synthetics/src/plugins/network.ts:142:39)

Steps errors
Expand to view the steps failures

Runs the tests

Took 1 min 2 sec . View more details here
Description: ./node_modules/.bin/jest --ci --reporters=default --reporters=jest-junit

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test


chore: update rector deps

"rector/rector": "2.0.0-rc1" to "rector/rector": "2.0.0-rc2" which fixed:
Problem 1
    - Root composer.json requires driftingly/rector-laravel 2.x-dev -> satisfiable by driftingly/rector-laravel[2.x-dev].
    - driftingly/rector-laravel 2.x-dev requires rector/rector ^2.0.0-rc2 -> found rector/rector[2.0.0-rc2, 2.0.0-rc3] but it conflicts with your root composer.json require (2.0.0-rc1).

Thanks for the contribution @mprince2k18 !


Enable build and install on macos

These are the things I had to do to make this work with macos 15.1 with homebrew dependencies.

MacOS support sounds so nice. Let me know when the PR gets ready to be reviewed.


Implement OAEP for RSA signature

From @izaera on February 12, 2014 7:23
Need to check what we are actually implementing (I think it's textbook RSA) and decide if it needs to be changed or enhanced in the future.
More info about RSA standards here: http://www.drdobbs.com/rsa-digital-signatures/184404605
and here: https://en.wikipedia.org/wiki/PKCS_1
Copied from original issue: izaera/cipher#59

@lionlin You can't yet, I'm afraid. This issue is the tracker to implement the feature and AFAIK, no one did it yet.

AsymmetricBlockCipher('RSA/OAEP') does not fail (although I think the RSA/OAEP implementation has issues), is this issue still open?

(Previous comment referring to https://github.com/PointyCastle/pointycastle/issues/177 )


Deleting test branch after the test

Current dependencies on/for this PR:

main

PR #33

PR #34   👈

This comment was auto-generated by Graphite.


Stable/1.8.19-fork

This fork avoids the urgent need to upgrade to django 1.11
Products and its versions:

Python 2.7.x
Instant Client <IP_ADDRESS>.0-1
cx-Oracle=6.4.1
Oracle 12c

Good afternoon.
Could you explain to me what was the problem with this fork? I changed only the .gitignore file (because of PyCharm) and one db/backends/oracle/base.py file.
Thank you.

@leonardotrp Could you explain what do you want to achieve? Django 1.8 is not supported for a long time.

@leonardotrp Could you explain what do you want to achieve? Django 1.8 is not supported for a long time.

Yes, I know. Is that the project I'm participating in still uses python 2.7 and django 1.8.x. For some problems I found with access to Oracle 12c (compatibility of Instant Client versions <IP_ADDRESS>.0-1 and cx-Oracle = 6.4.1), I had two options at that time: (1) upgrade to django 1.11 or (2) try to adapt only the db/backends/oracle/base.py file for my specific case. It was a very simple change.
Sorry for my mess. This was my first 'pull request' on GitHub.
Thanks.


Added 'add_fuel' command line option

Relatively new to both Rust and Wasmtime, so trying to just pick up a small first issue here.
PR to try a solution to Issue #3717
Currently just adds a "add_fuel" config option to the wasmtime API. I was taking a look and I think I might need to update this default value when the interpreter is instantiated:
    pub fn new(state: InterpreterState<'a>) -> Self {
        Self { state, fuel: None }
    }

to
    pub fn new(state: InterpreterState<'a>, fuel: Option<u64> = None) -> Self {
        Self { state, fuel: fuel }
    }

Don't currently have any test cases for the specific command line option just yet. Just wanted to check if I was on the right track.
CC: @fitzgen

You don't need to modify the clif interpreter at all here.
You want to add a call to https://docs.rs/wasmtime/latest/wasmtime/struct.Store.html#method.add_fuel somewhere around here: https://github.com/bytecodealliance/wasmtime/blob/main/src/commands/run.rs#L165

@fitzgen Thank you so much! That specific instantiation eluded me!
Thank you so much for being so patient and understanding, as well as holding my hand through this!

The only concern I could see from --fuel is the point where someone could call without --add-fuel to indicate that they want to '--consume-fuel' with 0 fuel.
I am not sure if there is a use case, but just thought I would mention it.

The only concern I could see from --fuel is the point where someone could call without --add-fuel to indicate that they want to --consume-fuel with 0 fuel.

In that case they would be able to do --fuel 0.

Once you commit these suggestions, I'll hit the merge button.

Or I guess github lets me add those suggestions as commits to your branch :)


add optional 'directoryExists' method to hosts to reduce amount of di…

…sk probings that are known to fail

:+1: