feat(core): add SCA exemption field

Type of Change

[ ] Bugfix
[x] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

To skip authorization, SCA exemption field is added to the transaction to flag it from authentication for frictionless flow for the user.
The field is passed during the request and accept 2 values: low_value and, transaction_risk_analysis

Additional Changes

[x] This PR modifies the API contract
Add a new field in payment request

{
    "psd2_sca_exemption_type": "low_value",
}

[x] This PR modifies the database schema
Add a new field to the payment intent table: psd2_sca_exemption_type
[ ] This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Tested through postman:

Create a MCA (Cybersource):
Create a /payment call

{
    "amount": 499,
    "currency": "USD",
    // "confirm": true,
    "capture_method": "automatic",
    "customer_id": "test_rec7",
    "email"<EMAIL_ADDRESS>    "request_external_three_ds_authentication": true,
    "customer_acceptance": {
        "acceptance_type": "online"
    },
    "payment_method": "card",
    "payment_method_type": "credit",
    "payment_method_data": {
        "card": {
            "card_number": "4242424242424242",
            "card_exp_month": "03",
            "card_exp_year": "2030",
            "card_holder_name": "Test",
            "card_cvc": "737"
        }
    },
    "billing": {
        "address": {
            "city": "test",
            "country": "US",
            "line1": "here is some \n there is some \n none is some? \n ",
            "line2": "there",
            "line3": "anywhere",
            "zip": "560095",
            "state": "Washington",
            "first_name": "One",
            "last_name": "Last"
        },
        "phone": {
            "number": "1234567890",
            "country_code": "+1"
        },
        "email"<EMAIL_ADDRESS>    },
     "psd2_sca_exemption_type": "low_value",
    "authentication_type": "no_three_ds"
}

psd2_sca_exemption_type field should be present in the payment_intent table against the generated payment_id

Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed the submitted code
[ ] I added unit tests for my changes where possible

@Sakilmostak Can you add this in cypress

@Sakilmostak Can you add this in cypress

Since this change does not reflect in response and is specific to connector, cypress test is not being added because there is no parameter to test on.


Can't find path when removing diagonals to force a X, Y movement

Using A star from this library and I want my points to find the objective while only moving on the X, Y coords but for whatever reason it can not find the location at all. Been trying to debug this and I'm fairly stumped and I can't find any reason that's wrong with my setup because as soon as I add diagonals everything works as intended as quite fast but I can not have diagonal movements.
impl BaseMap for WorldMap {
        let mut exits = SmallVec::new();
        let x = idx as i32 % self.width as i32;
        let y = idx as i32 / self.width as i32;
        let w = self.width as usize;

        // Cardinal directions
        if self.is_exit_valid(idx, x - 1, y) {
            exits.push((idx - 1, 1.0))
        };
        if self.is_exit_valid(idx, x + 1, y) {
            exits.push((idx + 1, 1.0))
        };
        if self.is_exit_valid(idx, x, y - 1) {
            exits.push((idx - w, 1.0))
        };
        if self.is_exit_valid(idx, x, y + 1) {
            exits.push((idx + w, 1.0))
        };

        exits
   }

    fn get_pathing_distance(&self, idx1: usize, idx2: usize) -> f32 {
        let (x1, y1, _z1) = self.idx_to_xyz(idx1);
        let (x2, y2, _z2) = self.idx_to_xyz(idx2);
        let p1 = Point::new(x1, y1);
        let p2 = Point::new(x2, y2);
        // Should maybe be manhattan since thats the way the rivers move.
        bracket_lib::prelude::DistanceAlg::Manhattan.distance2d(p1, p2)
    }
}

impl Map {
    // snip
    fn is_exit_valid(&self, idx: usize, x: i32, y: i32) -> bool {
        !(x < 1 || x > WIDTH - 1 || y < 1 || y > HEIGHT - 1)
    }
}

To the point on the map, if with nothing to effectively stop it (in my case a height map from 0 -> 1, but even removing those rules its not working), it just will struggle to pathfind to it.
Does the algo require diagonals or this may potentially be a bug of some sort?
I'll keep digging into what's causing this odd issue but, if this is known, or the setup for the above is required, let me know.
Now oddly enough, it'll find a bunch of short paths with no problems at all:
Finding path from x294, y911 to x294, y909
Finding path from x296, y905 to x297, y904
Finding path from x297, y901 to x296, y900
Finding path from x294, y900 to x294, y898
Finding path from x291, y897 to x289, y897
Finding path from x284, y893 to x280, y897
Finding path from x278, y899 to x278, y901
Finding path from x277, y902 to x253, y932

But then it'll just hang on one for many minutes, I guess until timeout. Its is getting fed valid outputs. The map is 1024x1024. I'm wondering if for whatever reason its checking out some section of the map thoroughly instead of checking right beside it. Though, from my understanding, it absolutely shouldn't.
What I understand is that it just keeps adding to the closed_list and its possible that it isn't even possible to get to that location for whatever reason. There shouldn't be anything preventing it however.
Oddly enough its always this particular coordinate which doesn't look anything unusual:
x277, y902 to x253, y932
Another example:
Finding path from x912, y640 to x912, y643
Trying x912, y640
Trying x911, y640
Trying x910, y640
Trying x910, y641
Trying x909, y640
Trying x910, y642
Trying x909, y641
Trying x910, y643
Trying x909, y642
Trying x908, y640
Trying x910, y644
Trying x908, y641
Trying x909, y643
Trying x908, y642
Trying x910, y645
Trying x909, y644
Trying x908, y639
Trying x907, y640
Trying x908, y643
Trying x907, y641
Trying x909, y645
Trying x910, y646
Trying x907, y642
Trying x908, y644
Trying x907, y643
Trying x908, y638
Trying x907, y639
Trying x906, y640
Trying x909, y646
Trying x910, y647
Trying x908, y645
. . . + few hundred more.

With just the simple pathing restrictions, why is having difficulty moving just 3 y values down?

I updated to 0.8.1 and I reduced a radius, I believe it may have just been the selection process rejection candidates, and the amount it was producing... I'm weirded out but I think the latest update may have fixed something.


Avoid timezone query on create connection when not needed

This aims to prevent this query to append if we use the timezone specified in configuration.

But it skips to query version()
 if (serverVersion == null) {
            serverVersion = "";
        }

AFAIK it needs to implement lazy evaluation of the version?

Looking at the code, it does need the version for one call.
I will add the possibility to specify the version too.
if (connection.getServerVersion().compareTo("1.1.54237") > 0) {             query = new StringBuilder(                 "SELECT database, table, name, type, default_kind as default_type, default_expression, comment ");         } else {             query = new StringBuilder(                 "SELECT database, table, name, type, default_type, default_expression, NULL AS comment ");         }

@den-crane Sorry I don't see which test fails. mvn test returns an unrelated NPE for me. How can I run them?

@nicolasblaye https://github.com/ClickHouse/clickhouse-jdbc/blob/master/clickhouse-jdbc/src/test/java/ru/yandex/clickhouse/integration/StreamSQLTest.java#L265
Some tests use getServerVersion() to make a decision does it need to run or not. Now they just skipped.

@den-crane As far as I know, my last two commits should make so version is still fetched by default via a select. It shouldn't change the test no?

OK then.  I did not check the last commit.

Thanks for the pull request @nicolasblaye. It's one-time query for connection initialization, with trivial overhead IMO. Would you mind to share the problem you're trying to resolve here? From what I saw, disabling the query may help for unit testing, plus it will slightly increase throughput.
By the way, I changed target branch to develop. Could you check the build break as well as merge conflict so that we can merge?

It's true that it's a small query, but we misconfigured our connection creation so we spam this query way too much (over a million time a day). Obviously, I am also fixing our connection creation issue but I figured I could also add that to the driver to avoid unnecessary (albeit very small) requests.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Won't merge this pull request as this has been addressed in new JDBC driver. When serverTimeZone and serverVersion are specified, the driver will no longer issue the query on creating connection.


Update NPM Package

Update NPM Package - still using old prop-type

confirmed getting same error ...

until he updates the package on npm, just use yarn add https://github.com/SiDevesh/React-Native-Material-Cards or npm install --save https://github.com/SiDevesh/React-Native-Material-Cards


OSX Icon corrupt and green?

Similar to this issue #22
There seems to be an issue with the macOS icon. I believe it to be corrupted, since I can't view it in any application that should be able to edit an .icns file.
Corrupted Icon set

Correct Icon set

Here is a icon set I made from a wiki .svg fie. Maybe this will correct it.
tomboy-ng.icns.zip
Let me know if you need more help on this.

Thanks xypd, I will happily admit I struggled with the Mac icons although whats there now does look OK on my one mac test platform (and aging Powerbook I purchased on eBay).
Did you make those icons yourself and have you clarified the license applicable ?
I do need tomboy-ng's icon to look different to the Tomboy one so maybe the yellow is not a good idea ?
I am away camping right now so won't be on line very often for another week .....
Davo

Hey David, I didn't make them. I simply complied them into an iconset for the .icns format.
How different do you need? These were taking directly from the tomboy wiki page as an svg then convert to png, then complied.
I can help with new icons if you give me the requirements.
Have fun camping!! The internet will still be here :D.
Thanks for checking in.

OK xypd, maybe we can deal with this first ?  I have an ageing Powerbook running Sierra that I use to do the only Mac test I do.  And on it, the icons show up fine so I am somewhat puzzled why they don't for you.
But that would be due to my very low level of experience with macs !
Now, on my system, I see my (pretty ugly) green icon firstly on the dmg file. Then when you open the dmg file, same image is shown next to the Application Folder. Once you drag the icon into the application folder, again you see my green icon there (its an application bundle).
Now, which one of those places don't you see it ?  Or don't you see it anywhere ?
My guess you are using a different screen resolution to me and and my icon set does not contain the right sized icons......
Davo

Did you make those icons yourself and have you clarified the license applicable ?

I used these sources for the icons, Link to svg , and link to wiki page of icon. Then made the .scrn file locally.

I do need tomboy-ng's icon to look different to the Tomboy one so maybe the yellow is not a good idea ?

So we can use the one they made at all? Would just changing the color be enough? For example I could just change the colors of the original icon so it look different. Or do we need to make one completely from scratch?

OK xypd, maybe we can deal with this first ? I have an ageing Powerbook running Sierra that I use to do the only Mac test I do. And on it, the icons show up fine so I am somewhat puzzled why they don't for you.

They do should up as your green icon without a problem. I was just under the impression that it was just a temporary icon and you would updated it later with the original app icon. But perhaps this was mistaken thinking on my part. But it does appear that ng is missing some sizes which means they will most likely look a bit blurry on retina/High DPI Mac screens.

Now, which one of those places don't you see it ? Or don't you see it anywhere ?

I can see the green icon in most places. But in the first post it shows that it's missing in 5 places. I think one of those is missing in file> about menu. Also in the mount installer image directory as well.

OK, now that is interesting !
On my powerbook, the two you show as having default icons use my (not very attractive) green icons.  As you say, thats probably because of the issue that my icon package is missing some resolutions. And I am missing some platforms to test on !
I really like your idea of making a green version of the original Tomboy icon. I (clearly) don't know enough to do that, if you could do it for me, that would be great !
Given that the original is on wikipedia under LGLP, we are sure free to use it here. And, tomboy-ng does have the blessing of the Tomboy author (or at least those still around).
I plan to get a new release out in the next few days, be magic if you could help before then but if thats too soon, then the release after that will be fine.
Thanks for your help.
Davo

I can help out with this. I'll see if I can maybe make new one though :D. If I run out of time then I can just colorize the original one. Do you need me to give them to you in the .icns format?

Yes please, its the converting to icns thats an issue for me.
I also use a set of png 16x16 22x22 24x24 32x32 48x48 256x256 so if you could suppy those native that would be great. But in can generate them myself if you you give me the svg.....

Just a heads up, I haven't begun to work on the icons. Please don't wait for them if your planning a release soon. So other work need to be completed first. But have it on my list of todos.

No worries xypd, I'll go ahead with the release and will mention the Mac icons as a 'known issue'.
Thanks
Davo

Good news I finally put in time on the icons. @davidbannon please have a look and tell me what you think good or bad :).
I made a version as you requested in green. But also took the liberty to make a complete new version too.
And anyone else feel free to chime in.

Wow, nice work xypd, nice work indeed.
Sorry I have not responded earlier, traveling in some remote places and internet access is just not there sometimes.
I don't have my Mac with me so cannot test but I don't expect any testing would be necessary (or, given me not seeing the problem you are addressing, useful).  So, its a case of choosing what ever looks the most appropriate ?
Your Ver.A through to Ver.E ?  Are they all part of a set or are you suggesting we choose of of them ?  I really like the ones with the pen rather than just the blank pad, its more Tomboy style.
I'd also need a Volume icon for the Mac, I have a crude drive drawing over the icon at present, it sucks !
Thank xypd !

Thanks @davidbannon, glade you like them. No worries about the time. We all have lives :D.
I think the color version with the pen is the ideal version.
Let me break down what I was thinking and see if this is something you're interested in.
We could take the opportunity to update all the icons for all platforms

Would need all the sizes and format for windows, Mac and Linux
We can use one of the outlined version for black and white specific, like the menubar or similar
We could also make some dynamic vers that can show stuff like updating, syncing, or errors. Though I’m not sure how this can work on the back end. Just a thought.
I would probably say though that the icon vers without the pen could work better for menu and small 16x16 uses.

Lastly, are we in agreement that the green vers of the original is not ideal and should be shelfed?
Looking forward to seeing these in the wild.

Hello XYPD, long time since I followed this up !
Are you still keen to play ?  I sure would like to update the icons if possible. I am just now rushing to get a new version out, now that I am finally home and can again test on Windows and Mac. I would like to get a new release out rather quickly, a lot of mainly bug fixes have built up while I was away. Major new feature is support for non-english versions, but at least one important bug fix....

No worries. And yeah I'm still would love for these icons be used.
Should I fork this and try to replace them where ever I find the green icon referenced?
Could be good practice :).
I found icons in these dir or areas:

https://github.com/tomboy-notes/tomboy-ng/blob/master/tomboy-ng/Tomboy_NG.ico
https://github.com/tomboy-notes/tomboy-ng/tree/master/glyphs

Are there more some place else?

Hmm, not sure about doing a pull request. I might be better manually putting them into the IDE, some processing happens there, unsure what....

Yeah, makes sense. I guess I have a number of competing issues -
I want to retain that link to Tomboy, there really is nothing original in tomboy-ng, its all its presentation ideas comes from Tomboy.
But since Tomboy was made, GUI have changed a lot, while I need the very low res SystemTray icon, we also need to use some 256x256 and what looks good in 16x16 often looks doppy at higher res. You clearly know lots more than me about such things.
A black and white one for the dark theme people is a great idea I am not sure I can change some of them dynamically, will need to do some experimenting. Windows is hard, images embedded in binary, the SystemTray icon is loaded at design time, will have to experiment there too.
Sizes and files needed
On Linux, the advice I got was to have a set of icons, 16x16 to 256x256 but I suspect that all that is loaded is the 48x48. Only way to be sure is, perhaps, strace. But clearly, it will also depend a bit on the end users screen resolution. But that won't help on the Mac or Windows.....
Lets assume I need 16x16, 22x22, 24x24, 32,32, 48x48 and 256x256 for linux.
I need the icns file for Mac, and a separate volume icns one too. Looks like my Mac build script only uses the existing ICNS files, so you can change all of that just with new ICNS files.
From memory, all I need on windows is the application icon and System tray icon. 48x48 and 16x16 but I am not sure.
If you make be a black and white set too, I'll experiment with trying to switch to them at run time for Dark Theme. Think its easy on Linux, no idea on the Mac, hard on Windows.....
Which one to use ?
 And from your recent post, seem to scale OK too (?). Your colour changed Tomboy one has the advantage of looking like the regional and being green continuing a tomboy-ng tradition.
Davo

Hey Davo,
Made some time for some updates. Please let me know if you have issues and need new versions. Hopefully everything works with out any problems.
I'm providing the following, full color, black and white versions:

Linux

16, 22, 24, 32, 64, 128, 256, 512

Mac icns

16, 32, 64, 128, 256, 512, 1024

Windows

16, 32, 48, 64, 128, 256, 512

For the linux and Window batches, you can simply use what you need. for the Mac version I've included the .icns in the zip files.
Full_color.zip
White.zip
Black.zip
tomboyNG.svg.zip

Right !
I have merged your pull request, looks great. Nice to emphasis the cross platform look.
I need to put the icons in via my IDE, would like to look into selecting particular ones at run time so look better on (eg) dark themes. The black or white ones clearly targeted at Mac. Interesting ....

I have checked in code using the updated icons. Wow, it does look good. I have, so far, used only the coloured ones, the yellow pad.  I think you intend the black and while ones for the tray icon on the Mac ?  Do all Macs use a black background to the trayicon bar ?  I have code working that lets me load an alternative (to the default coloured) icon at startup but uncertain how I can be sure its appropriate.  I did not find the black or white ones very 'safe' on the various Linux desktops I tried. Even with dark themes the yellow coloured tray icon looked better. To my uneducated eye.
Thoughts ?

Intrusion here from a Linux user: these are reallly nice icons! I have always liked the yellow pads because I think the original Post-Its were yellow only (nothing to do with original Tomboy). However, even the redesigned green is quite sharp.
I have never been a fan of B&W icons, and would note that for the visually impaired colour can be an aid. However, if this is a particular Mac style and can be kept for it rather than Linux . . . .

You should see the coloured one in use !
Maybe I need to cut a 0.25a ?  Maybe after we get to bottom of a few other issues mentioned in other threads....
Anyway, thanks xypd, cool !
Davo

I'm very excited to see them in action and glade you guys like them. And you're very welcome Davo, happy to contribute.
As for the B&W vers., my use case thoughts as following.

Color icon is standard default on all platforms.
The white would be use only on darkmode or user selected
The black vers would be for user (maybe only Mac) that want a BW icon to match the other black and white ones provided by apple in the menubar(aka, menu tray).

I don't think the BW icon should be used for anything other than menu try. I design them mainly for sizes from maybe 16-32px
So I can see you adding a option in the settings maybe via a drop down that lets the user select the color they want to manually. Some might complain about having to change it, but I personally enjoy this option versus none.
aguador, no intrusion I appreciate your and others input into this.
Since everyone has different taste and needs I do think use of the BW vers should be an choice so people like you who don't particularly like them doesn't need to use them. But also allows this who want a limited amount of colors on the screen distracting them can use the BW vers. (ex designers, video editors, etc).
To your comment on about visually impaired, it funny I actually thought that the simple design and higher contrast would be helpful ... think mobile phone top menu area (signal, carrier, battery etc). But I can also image if you have a bunch of icons another BW one could be harder to see vs a colored one. However if we can choose the icon we want, then I think this will not be an issue.
Additionally, if possible it could give us the opportunity to add color to indicate apps state. So red could mean issue/unsaved, yellow could be syncing, green could be backed up ... etc. These are just ideas that popped in my head :D.
Of course I will need to review how it actually works in use and make adjustment if needed. So Davo if you want to compile a beta vers and make it available to me (or everyone) so I can try it out, that could be helpful.
cheers

@xypd Just tested an installation script with updated ng from Davo so got to see the new yellow icons. They are really slick. A great addition to ng.
The only tiny thing I noted was that on smaller icons (specifically my 30 pixel high panel on an 11,6" screen), the pencil does not stand out terribly well. Perhaps a slight change in tone or more shadow would give it better definition? I just glanced back at the icons and see that Tomboy had a brown pencil. Using the same/virtually the same colour with the changed position of the pencil might be the way to go. However, even with no change the icons are great.
(I just realised working on a Mac you have a greater screen resolution, so the contrast may be better. Those higher resolution screens are the one thing I really like about the Macs, although the laptops for the rest of us are finally starting to get a bit higher resolution.)
As far as the B&W icons, I did not mean to imply they should not be offered. They certainly have their place.

Cool that you tested it out! Glade your enjoying them.
Taking a quick look I can see how this could be an issue. Would you mine sharing a screenshot of what you're seeing? Also Should I assume you were talking about 32px, since I didn't make a 30px vers? If a 30px is needed it should be added since it can of course change the clarity of the icon at the wrong size.
When I get some time I can edit the icon to see if I can bring up the contrast on the pencil.
And appreciate you all views, so no worries on the BW comments. I didn't take them negatively, more I was trying to point out a use case for them.

My guess is aguador is referring to the system tray icon on Linux, I convert that to an ICO file from the 24x24 png.  I agree it does, perhaps lack definition because of its small size. Not sure if its worth having multiple master artworks to deal with the small ones. From memory, the kit includes 24x24, 22x22 and 16x16.  The larger ones do look better.

Once I can load it on my linux vm I can hopefully see. But only then can I assess if there are good solutions. For example creating new version with more contrast for maybe 32 and smaller.
But won't start anything of course until I see them on multiple platforms.
For example vers B row could be a go starting point. Or simply adding some darker highlights or shadows in the current version.

Here is a screenshot of the notification area on the panel:

It is 30px high, so whichever icon is used is adjusted to the height of the panel. The systems I have used normally default to around 40px high, but I use between 28 and 32 as I can see enough to select whatever I need with that.
The screenshot seems a bit sharper, which led me to play around. The difference is the viewing angle. My initial reaction was to seeing the icon on this small screen with the panel at the bottom and the computer, literally, in my lap. I just moved the panel to the top of the sreen and, even with the machine in my lap, I can see it more clearly. So my original comment is based on the worst case scenario: small screen, small panel, panel at the bottom and screen about as far away as practicable. Even under those conditions the icon works well, so it is not clear that any change is worth the effort.
PS As I think I mentioned to Davo once, the original, flat green icon always looked overpowering in the notification area. Here with the angle it fits better with the other icons, particularly the Pidgin (chat) icon next to it.

 Attached is a screenshot of aguador's and xypd's original 24x24 side by side. No scaling.

Yeah it looks much blurrier in aguador's vers.
I'm wondering if his settings are grabbing the 24 (or even the 16!) when it should probably use the 28 or 32 vers. Is there anyway to tell for sure?

No, I  am pretty sure he is refering to the the System Tray Icon and that is dealt with differently.  That Icon is assigned at build time, its not loaded dynamically (although I can if necessary). The general but vague advice is that it should be a 24x24 bitmap and is not scaled. But maybe his KDE is playing with it.

Ah, I see. Thanks for that info.

OK, this is done.  Thanks again xypd, its a huge improvement and one that was needed !
Davo


[Module Proposal]: Bicep Template for MongoDB- vCore

Have you checked this module does not already exist in the registry?
Yes
Why is the module needed?
Our team will be using this mongo Db for testing purpose.
Module path
storage/mongoDB-vCore
Describe the module
Create an Azure Cosmos DB for MongoDB vCore cluster by using a Bicep template.
https://learn.microsoft.com/en-us/azure/cosmos-db/mongodb/vcore/quickstart-bicep?tabs=azure-cli

Dear @schandnani , Azure Verified Modules (AVM) will become the single Microsoft standard for Bicep modules. Transitioning to AVM, requests for new features or bug fixes will need to be submitted against the appropriate AVM module via AVM Module Issues.
For bugs or new features with existing modules in the /modules directory of this repository, we encourage you to first try the AVM equivalent module if available and if the module is lacking any features, you can file an AVM Module Issue. If the module is not available yet, you can file a new AVM Module Proposal.
See this informational notice for more details on the upcoming changes.
Thank you for your understanding!


Event Delegation

We are a lot of event listeners to pages via the on() function: https://github.com/beercss/beercss/blob/acd6fe4e5aefd7c24fe4df30aa12e34f9ca92f90/src/cdn/beer.ts#L60
This works well for small pages. However, for larger pages, we could reduce memory usage by employing Event Delegation. Here is a good introduction to Event Delegation: https://www.w3docs.com/learn-javascript/javascript-events.html

We will close this issue by inactivity, fell free to reopen it.


install problem

I get an error when I try to load node @pizzaprogram/mcp-pcf-aio via manage pallete, this is the log  :
2022-11-03T12:22:30.070Z Install : @pizzaprogram/mcp-pcf-aio 2.3.8-20220907
2022-11-03T12:22:30.123Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict<EMAIL_ADDRESS>2022-11-03T12:22:31.767Z [err] npm
2022-11-03T12:22:31.769Z [err]
2022-11-03T12:22:31.770Z [err] WARN
2022-11-03T12:22:31.770Z [err]
2022-11-03T12:22:31.770Z [err] config
2022-11-03T12:22:31.770Z [err]  production Use --omit=dev instead.
2022-11-03T12:22:37.162Z [err] npm
2022-11-03T12:22:37.163Z [err] ERR!
2022-11-03T12:22:37.163Z [err] code 1
2022-11-03T12:22:37.164Z [err] npm ERR!
2022-11-03T12:22:37.164Z [err]  path
2022-11-03T12:22:37.165Z [err]  /config/node-red/node_modules/i2c-bus
2022-11-03T12:22:37.171Z [err] npm ERR!
2022-11-03T12:22:37.172Z [err]  command failed
2022-11-03T12:22:37.172Z [err] npm ERR!
2022-11-03T12:22:37.172Z [err] command sh -c node-gyp rebuild
2022-11-03T12:22:37.172Z [err] npm ERR!
2022-11-03T12:22:37.173Z [err]  gyp info it worked if it ends with ok
2022-11-03T12:22:37.173Z [err] npm ERR!
2022-11-03T12:22:37.173Z [err]  gyp info using<EMAIL_ADDRESS>2022-11-03T12:22:37.173Z [err] npm ERR! gyp info using<EMAIL_ADDRESS>| linux | arm64
2022-11-03T12:22:37.173Z [err] npm ERR! gyp ERR! find Python
2022-11-03T12:22:37.173Z [err] npm ERR!
2022-11-03T12:22:37.174Z [err]  gyp ERR! find Python checking Python explicitly set from command line or npm configuration
2022-11-03T12:22:37.174Z [err] npm ERR! gyp ERR! find Python - "--python=" or "npm config get python" is "/usr/bin/python3"
2022-11-03T12:22:37.174Z [err] npm ERR! gyp ERR! find Python - "/usr/bin/python3" is not in PATH or produced an error
2022-11-03T12:22:37.174Z [err] npm
2022-11-03T12:22:37.174Z [err] ERR! gyp ERR! find Python Python is not set from environment variable PYTHON
2022-11-03T12:22:37.174Z [err] npm ERR!
2022-11-03T12:22:37.174Z [err]  gyp ERR! find Python checking if "python3" can be used
2022-11-03T12:22:37.174Z [err] npm ERR! gyp ERR! find Python - "python3" is not in PATH or produced an error
2022-11-03T12:22:37.174Z [err] npm ERR! gyp ERR! find Python checking if "python" can be used
2022-11-03T12:22:37.174Z [err] npm
2022-11-03T12:22:37.174Z [err] ERR! gyp ERR! find Python - "python" is not in PATH or produced an error
2022-11-03T12:22:37.174Z [err] npm ERR!
2022-11-03T12:22:37.175Z [err]  gyp ERR! find Python
2022-11-03T12:22:37.175Z [err] npm ERR! gyp ERR! find Python **********************************************************
2022-11-03T12:22:37.175Z [err] npm ERR! gyp ERR! find Python You need to install the latest version of Python.
2022-11-03T12:22:37.175Z [err] npm ERR!
2022-11-03T12:22:37.175Z [err]  gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
2022-11-03T12:22:37.175Z [err] npm ERR!
2022-11-03T12:22:37.175Z [err]  gyp ERR! find Python you can try one of the following options:
2022-11-03T12:22:37.175Z [err] npm ERR! gyp ERR! find Python - Use the switch --python="/path/to/pythonexecutable"
2022-11-03T12:22:37.175Z [err] npm ERR! gyp ERR! find Python   (accepted by both node-gyp and npm)
2022-11-03T12:22:37.175Z [err] npm
2022-11-03T12:22:37.175Z [err] ERR! gyp ERR! find Python - Set the environment variable PYTHON
2022-11-03T12:22:37.175Z [err] npm ERR!
2022-11-03T12:22:37.175Z [err]  gyp ERR! find Python - Set the npm configuration variable python:
2022-11-03T12:22:37.175Z [err] npm ERR!
2022-11-03T12:22:37.175Z [err]  gyp ERR! find Python   npm config set python "/path/to/pythonexecutable"
2022-11-03T12:22:37.175Z [err] npm ERR! gyp ERR! find Python For more information consult the documentation at:
2022-11-03T12:22:37.176Z [err] npm ERR! gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
2022-11-03T12:22:37.176Z [err] npm
2022-11-03T12:22:37.176Z [err] ERR! gyp ERR! find Python **********************************************************
2022-11-03T12:22:37.176Z [err] npm ERR!
2022-11-03T12:22:37.176Z [err]  gyp ERR! find Python
2022-11-03T12:22:37.176Z [err] npm ERR!
2022-11-03T12:22:37.176Z [err]  gyp ERR! configure error
2022-11-03T12:22:37.176Z [err] npm ERR! gyp ERR! stack Error: Could not find any Python installation to use
2022-11-03T12:22:37.176Z [err] npm ERR! gyp ERR! stack     at PythonFinder.fail (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:330:47)
2022-11-03T12:22:37.176Z [err] npm ERR!
2022-11-03T12:22:37.176Z [err]  gyp ERR! stack     at PythonFinder.runChecks (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:159:21)
2022-11-03T12:22:37.176Z [err] npm ERR! gyp ERR! stack     at PythonFinder. (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:202:16)
2022-11-03T12:22:37.176Z [err] npm
2022-11-03T12:22:37.177Z [err]  ERR! gyp ERR! stack     at PythonFinder.execFileCallback (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:294:16)
2022-11-03T12:22:37.177Z [err] npm
2022-11-03T12:22:37.177Z [err] ERR! gyp ERR! stack     at exithandler (node:child_process:408:5)
2022-11-03T12:22:37.177Z [err] npm ERR!
2022-11-03T12:22:37.177Z [err]  gyp ERR! stack     at ChildProcess.errorhandler (node:child_process:420:5)
2022-11-03T12:22:37.177Z [err] npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
2022-11-03T12:22:37.177Z [err] npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
2022-11-03T12:22:37.177Z [err] npm
2022-11-03T12:22:37.177Z [err]  ERR! gyp ERR! stack     at onErrorNT (node:internal/child_process:478:16)
2022-11-03T12:22:37.177Z [err] npm
2022-11-03T12:22:37.177Z [err] ERR! gyp ERR! stack     at processTicksAndRejections (node:internal/process/task_queues:83:21)
2022-11-03T12:22:37.177Z [err] npm ERR!
2022-11-03T12:22:37.177Z [err]  gyp ERR! System Linux 5.15.61-v8
2022-11-03T12:22:37.177Z [err] npm ERR!
2022-11-03T12:22:37.177Z [err]  gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
2022-11-03T12:22:37.177Z [err] npm ERR! gyp ERR! cwd /config/node-red/node_modules/i2c-bus
2022-11-03T12:22:37.178Z [err] npm ERR! gyp ERR! node -v v16.17.1
2022-11-03T12:22:37.178Z [err] npm
2022-11-03T12:22:37.178Z [err] ERR! gyp ERR! node-gyp -v v9.0.0
2022-11-03T12:22:37.178Z [err] npm ERR!
2022-11-03T12:22:37.178Z [err]  gyp ERR! not ok
2022-11-03T12:22:37.185Z [err]
2022-11-03T12:22:37.185Z [err] npm ERR! A complete log of this run can be found in:
2022-11-03T12:22:37.186Z [err] npm ERR!     /root/.npm/_logs/2022-11-03T12_22_31_618Z-debug-0.log
2022-11-03T12:22:37.206Z rc=1

Other users could install it without any problem.
It seems that the "i2c" node (I'm calling as base of my node) could not be installed because of missing: python3 .
But I'm not sure.
I did not write the i2c node. You may ask the author... or check similar errors on that GitHub project. (See Readme for link)
PS: Please EDIT your comment and format the log as "code" !

Node Red v3.0.2 under Home assistant.
Which i2C node most i install ?

As I've already wrote above:
i2c Link is on the MAIN page, called "link ... " . https://github.com/fivdi/i2c-bus

obviously you did not read what I've answered
you still did not format your log to code.

Sorry, I'm new to github, so what do you mean with ' format your log to code' ?
To install the node I have to type: 'npm install i2c bus' Where do I type this, I only know how to load nodes via the management palette in node red.

The right method to install i2c node-red package is:

You need to open a Terminal on your Linux machine.
type or copy: npm install i2c-bus
press Enter, wait until it's finished
Restart node-red

Are you sure you are using a Linux? Not a Windows?
(I've just tried to install to a Win7 32-bit PC, and saw similar errors. First I needed to install Python, but that was not enough either, because then the i2c-bus install complained about errors like: no "Visual Studio" is present ... )

I've just realized yesterday:
Made in 2022 a big mistake:

did not upload my latest version [<IP_ADDRESS>20908] properly to here, nor to the NPM  ! :-1:
the one uploaded [v<IP_ADDRESS>20907] does not work at all.

You should try this version, which is an enhanced one:
https://flows.nodered.org/node/@joe-ab1do/mcp-pcf-aio
< OFF >
PS: Sorry for the very late response. The last 14 month was a nightmare for me, could not work on this project.


Cannot compile v3.17 on Gentoo

Description:
Had no problem compiling 2.76, but 3.17 produces several errors.
The (I hope) relevant parts of CMakeFiles/CMakeError.log:
Performing C++ SOURCE FILE Test HAVE_CXX_FLAG_WCXX14_COMPAT_PEDANTIC failed with the following output:
Change Dir: /tmp/nchat-3.17/cmakebuild/CMakeFiles/CMakeScratch/TryCompile-VX9uDE

Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_c81cb/fast && /usr/bin/gmake  -f CMakeFiles/cmTC_c81cb.dir/build.make CMakeFile
s/cmTC_c81cb.dir/build
gmake[1]: Entering directory '/tmp/nchat-3.17/cmakebuild/CMakeFiles/CMakeScratch/TryCompile-VX9uDE'
Building CXX object CMakeFiles/cmTC_c81cb.dir/src.cxx.o
/usr/bin/c++ -DHAVE_CXX_FLAG_WCXX14_COMPAT_PEDANTIC  -std=c++14 -fno-omit-frame-pointer -fno-exceptions -fno-rtti -ffunction-sections -fdata-sections -Wall -Wextra -Wimplicit-fallthrough=2 -Wpointer-arith -Wcast-qual -Wsign-compare -Wduplicated-branches -Wduplicated-cond -Walloc-zero -Wlogical-op -Wno-tautological-compare -Wpointer-arith -Wvla -Wnon-virtual-dtor -Wno-unused-parameter -Wconversion -Wno-sign-conversion -Wc++14-compat-pedantic   -Wc++14-compat-pedantic -std=gnu++14 -o CMakeFiles/cmTC_c81cb.dir/src.cxx.o -c /tmp/nchat-3.17/cmakebuild/CMakeFiles/CMakeScratch/TryCompile-VX9uDE/src.cxx
c++: error: unrecognized command-line option '-Wc++14-compat-pedantic'
c++: error: unrecognized command-line option '-Wc++14-compat-pedantic'
gmake[1]: *** [CMakeFiles/cmTC_c81cb.dir/build.make:78: CMakeFiles/cmTC_c81cb.dir/src.cxx.o] Error 1
gmake[1]: Leaving directory '/tmp/nchat-3.17/cmakebuild/CMakeFiles/CMakeScratch/TryCompile-VX9uDE'
gmake: *** [Makefile:127: cmTC_c81cb/fast] Error 2

Source file was:
int main() { return 0; }

Performing C++ SOURCE FILE Test HAVE_CXX_FLAG_WUNUSED_COMMAND_LINE_ARGUMENT failed with the following output:
Change Dir: /tmp/nchat-3.17/cmakebuild/CMakeFiles/CMakeScratch/TryCompile-KctSrU

[...]

c++: error: unrecognized command-line option '-Wunused-command-line-argument'; did you mean '-Wunused-dummy-argument'?

[...]

Performing C++ SOURCE FILE Test HAVE_CXX_FLAG_QUNUSED_ARGUMENTS failed with the following output:
Change Dir: /tmp/nchat-3.17/cmakebuild/CMakeFiles/CMakeScratch/TryCompile-eso4cu

[...]

c++: error: unrecognized command-line option '-Qunused-arguments'
c++: error: unrecognized command-line option '-Qunused-arguments'

[...]

Determining if the function cbreak exists in the /usr/lib64/libncursesw.so failed with the following output:
Change Dir: /tmp/nchat-3.17/cmakebuild/CMakeFiles/CMakeScratch/TryCompile-YCEhjc

[...]

Determining if the function nodelay exists in the /usr/lib64/libncursesw.so failed with the following output:
Change Dir: /tmp/nchat-3.17/cmakebuild/CMakeFiles/CMakeScratch/TryCompile-OiBKLg

I don't have much knowledge or experience with cmake, so apologies in advance if I missed something obvious.
How to reproduce it:
$ mkdir cmakebuild/
$ cd cmakebuild/
$ cmake ../

Environment:

Version: 3.1.7
OS / distro: Gentoo Linux

Hi @2011 - the output in CMakeFiles/CMakeError.log might not be that important. It's common for it to contain "errors" as cmake determines the capabilities of the compiler and toolchain.
Can I check what output you see on the terminal when running cmake? Ideally if you could share the entire output, running something like cmake .. &> log.txt and attaching log.txt here, it would be great. But it's possible that just the last output/error message would be sufficient.

Hi again - I tested on Gentoo amd64 LiveGUI USB Image 2023-03-07 and the cmake step runs fine here.
Btw, If you are building from an old git clone that you updated (git pull), you could try deleting old build files using:
git clean -ffdx

And then try build again. Generally it should be fine to update and building without cleaning, but there can sometimes be issues between versions when third-party libraries have been updated.

Hi @2011 - the output in CMakeFiles/CMakeError.log might not be that important. It's common for it to contain "errors" as cmake determines the capabilities of the compiler and toolchain.

I don't know cmake well enough to recognize non-fatal errors, but the  second gap (output in red that includes "Call Stack") led me to believe that something didn't work.

Can I check what output you see on the terminal when running cmake? Ideally if you could share the entire output, running something like cmake .. &> log.txt and attaching log.txt here, it would be great. But it's possible that just the last output/error message would be sufficient.

No problem (thanks for the quick reply).

Btw, If you are building from an old git clone that you updated (git pull), you could try deleting old build files using:

I downloaded the latetest release, and unpacked it in a net directory.
$ cmake ../
-- The CXX compiler identification is GNU 12.2.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Using build type 'Release' (default).

-- Found SQLite3: /usr/include (found version "3.40.1")
-- Performing Test HAVE_BUILTIN_ATOMIC
-- Performing Test HAVE_BUILTIN_ATOMIC - Success
-- Using built-in atomic.
-- The C compiler identification is GNU 12.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Could NOT find ccache (this is NOT an error)
-- Found OpenSSL: /usr/lib64/libcrypto.so (found version "1.1.1t")
-- Found OpenSSL: /usr/include /usr/lib64/libssl.so;/usr/lib64/libcrypto.so
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Performing Test HAVE_STD14
-- Performing Test HAVE_STD14 - Success
-- Performing Test HAVE_CXX_FLAG_WALL
-- Performing Test HAVE_CXX_FLAG_WALL - Success
-- Performing Test HAVE_CXX_FLAG_WEXTRA
-- Performing Test HAVE_CXX_FLAG_WEXTRA - Success
-- Performing Test HAVE_CXX_FLAG_WIMPLICIT_FALLTHROUGH_2
-- Performing Test HAVE_CXX_FLAG_WIMPLICIT_FALLTHROUGH_2 - Success
-- Performing Test HAVE_CXX_FLAG_WPOINTER_ARITH
-- Performing Test HAVE_CXX_FLAG_WPOINTER_ARITH - Success
-- Performing Test HAVE_CXX_FLAG_WCAST_QUAL
-- Performing Test HAVE_CXX_FLAG_WCAST_QUAL - Success
-- Performing Test HAVE_CXX_FLAG_WSIGN_COMPARE
-- Performing Test HAVE_CXX_FLAG_WSIGN_COMPARE - Success
-- Performing Test HAVE_CXX_FLAG_WDUPLICATED_BRANCHES
-- Performing Test HAVE_CXX_FLAG_WDUPLICATED_BRANCHES - Success
-- Performing Test HAVE_CXX_FLAG_WDUPLICATED_COND
-- Performing Test HAVE_CXX_FLAG_WDUPLICATED_COND - Success
-- Performing Test HAVE_CXX_FLAG_WALLOC_ZERO
-- Performing Test HAVE_CXX_FLAG_WALLOC_ZERO - Success
-- Performing Test HAVE_CXX_FLAG_WLOGICAL_OP
-- Performing Test HAVE_CXX_FLAG_WLOGICAL_OP - Success
-- Performing Test HAVE_CXX_FLAG_WTAUTOLOGICAL_COMPARE
-- Performing Test HAVE_CXX_FLAG_WTAUTOLOGICAL_COMPARE - Success
-- Performing Test HAVE_CXX_FLAG_WVLA
-- Performing Test HAVE_CXX_FLAG_WVLA - Success
-- Performing Test HAVE_CXX_FLAG_WNON_VIRTUAL_DTOR
-- Performing Test HAVE_CXX_FLAG_WNON_VIRTUAL_DTOR - Success
-- Performing Test HAVE_CXX_FLAG_WUNUSED_PARAMETER
-- Performing Test HAVE_CXX_FLAG_WUNUSED_PARAMETER - Success
-- Performing Test HAVE_CXX_FLAG_WCONVERSION
-- Performing Test HAVE_CXX_FLAG_WCONVERSION - Success
-- Performing Test HAVE_CXX_FLAG_WSIGN_CONVERSION
-- Performing Test HAVE_CXX_FLAG_WSIGN_CONVERSION - Success
-- Performing Test HAVE_CXX_FLAG_WCXX14_COMPAT_PEDANTIC
-- Performing Test HAVE_CXX_FLAG_WCXX14_COMPAT_PEDANTIC - Failed
-- Performing Test HAVE_CXX_FLAG_WDEPRECATED
-- Performing Test HAVE_CXX_FLAG_WDEPRECATED - Success
-- Performing Test HAVE_CXX_FLAG_WUNUSED_COMMAND_LINE_ARGUMENT
-- Performing Test HAVE_CXX_FLAG_WUNUSED_COMMAND_LINE_ARGUMENT - Failed
-- Performing Test HAVE_CXX_FLAG_QUNUSED_ARGUMENTS
-- Performing Test HAVE_CXX_FLAG_QUNUSED_ARGUMENTS - Failed
-- Performing Test HAVE_CXX_FLAG_WODR
-- Performing Test HAVE_CXX_FLAG_WODR - Success
-- Performing Test HAVE_CXX_FLAG_FLTO_ODR_TYPE_MERGING
-- Performing Test HAVE_CXX_FLAG_FLTO_ODR_TYPE_MERGING - Success
-- Performing Test HAVE_CXX_FLAG_WMAYBE_UNINITIALIZED
-- Performing Test HAVE_CXX_FLAG_WMAYBE_UNINITIALIZED - Success
-- Performing Test HAVE_CXX_FLAG_WREDUNDANT_MOVE
-- Performing Test HAVE_CXX_FLAG_WREDUNDANT_MOVE - Success
-- Performing Test HAVE_CXX_FLAG_WSTRINGOP_OVERFLOW
-- Performing Test HAVE_CXX_FLAG_WSTRINGOP_OVERFLOW - Success
CMake Error at lib/tgchat/ext/td/CMake/GetGitRevisionDescription.cmake:61 (file):
  file RELATIVE_PATH must be passed a full path to the file:
Call Stack (most recent call first):
  lib/tgchat/ext/td/CMakeLists.txt:156 (get_git_head_revision)

-- Git state:
-- Found ZLIB: /usr/lib64/libz.so (found version "1.2.13")
-- Found ZLIB: /usr/include /usr/lib64/libz.so
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success
-- Performing Test GNU_READLINE_FOUND
-- Performing Test GNU_READLINE_FOUND - Success
-- Found Readline: /usr/include
-- Found Readline: /usr/include /usr/lib64/libreadline.so
-- Performing Test USABLE_READLINE_FOUND
-- Performing Test USABLE_READLINE_FOUND - Success
-- Looking for include file xcb/xcb.h
-- Looking for include file xcb/xcb.h - found
-- Looking for include file png.h
-- Looking for include file png.h - found
-- Looking for cbreak in /usr/lib64/libncursesw.so
-- Looking for cbreak in /usr/lib64/libncursesw.so - not found
-- Looking for nodelay in /usr/lib64/libncursesw.so
-- Looking for nodelay in /usr/lib64/libncursesw.so - not found
-- Found Curses: /usr/lib64/libncursesw.so
-- Using fallback man dir: /usr/local/man
-- Configuring incomplete, errors occurred!
See also "/tmp/nchat-3.17/cmakebuild/CMakeFiles/CMakeOutput.log".
See also "/tmp/nchat-3.17/cmakebuild/CMakeFiles/CMakeError.log".

Thanks for providing the additional details 👍
Looks like there's an issue when building from a downloaded file archive (zip/tar), while if you use a git clone it builds fine. As a workaround you can try
git clone https://github.com/d99kris/nchat
It's the third-party library tdlib that now appears to need to be built from a git clone. I will look into fixing it.

This should be fixed in above commit. One can download latest master as a file archive from https://github.com/d99kris/nchat/archive/refs/heads/master.zip and extract and build it.
The fix will be included in the next release planned for end-March (the project is on a quarterly release cycle).
Thanks for reporting this! 👍  Let me know if you still encounter issues.


Automatic Unwanted DataDown Packets

Is this a bug or a feature request?
Bug or Feature Change as of update.
Recently Upgraded the LoRa App Server, Now finding that every DataUp is generating an automatic DataDown packet addressed to devices from the gateway. Have not changed LoRa Device Code or Setup. All features in LoRa device are off including ADR, we are using UnconfirmedDataUp, ABP joining.
Anyone know where this setting is or what we are missing to turn off?
What did you expect?
Expected No DownStream messages from gateway to device.
What happened?
Have UnconfirmedDataDown message every upstream report with DataDown now having ADR true, (ADR still false in DataUp). Also RXParamSetupReq and RXTimingSetupReq in frame option field in DataDown. This has only started once we updated LoRa Server. FOpt is Null in DataUp
What version are your using?
0.18.2 is our current version,
0.16.x was the previous version.
How can your issue be reproduced?
Should be clear to see. If not maybe different configs are used. Trying to stop DataDown's.
Could you share your log output?

This is more related to LoRa Server (https://github.com/brocaar/loraserver).
When your devices does not respond to the RXParamSetupReq and RXTimingSetupReq mac-commands, then this is probably an issue with your device. The network-server tries to update the device configuration to keep it in sync with your loraserver.toml file. However it expects an acknowledgement from the device. As it does not receive such acknowledgement, it is resent.

Moved to (https://github.com/brocaar/loraserver).
https://github.com/brocaar/loraserver/issues/318


Improve README Clarity and Formatting

PR Description
This PR enhances the clarity and formatting of the Classiq README file, ensuring that instructions and code examples are presented in a more accessible and professional manner. The modifications include grammatical corrections, consistent terminology, and improved structural organization for better readability.
Some Notes

[x] Please make sure that you placed the files in an appropriate folder.
[x] Ensure that the files have indicative names.
[x] Please note that Classiq runs automatic code linting, which may minorly alter some files.

[x] If you're familiar with pre-commit, you may run pre-commit install, and then at each commit, your files will be altered in a similar way.

@Nadav138 please review my PR based on your convenience.

Hello @UTSAVS26!
We appreciate your contribution!
Please rebase your branch and see the updated README file. It had older PRs that were merged, so your branch is currently conflicted. You may solve the conflicts or open a new PR from an updated branch.
Thanks again!


[0.9] binding allows dot notation but not bracket lookup

I can bind a variable inside the template using object.property but not object[property]

I think this one belongs to @kevinpschaaf or maybe @sorvell.

No near-term plans to support this.  Polymer 0.5 had a complex expression parser used for bindings that we have eliminated for simplicity and performance.  There are alternate patterns you can use today to achieve similar results that just require you to be more explicit.
If property in your example is actually static, right now just use object.property rather than object['property'].
If you wish property to be a string-typed variable to dereference on object and have the result re-evaluated when either object or property change, you can do this:
{{computeObjectProperty(object, property)}}
computeObjectProperty: function(object, property) {
  return object && object[property];
}

Closing, no immediate plans to add more complex expression binding.

There is an experimental 1.0-compatible opt-in version of PolymerExpressions on a branch here: https://github.com/Polymer/polymer-expressions/tree/2.0-preview
There are no plans to incorporate this into the core library.


Pass additional parameters when making PGO package

Pass additional parameters when making PGO package

Running a test build with this now.

k its fine. it's just the y2k22 bug now that I'm waiting on the upstream team to fix.


References not found because details were changed in Zotero

Will re insert the citations and build chapter to make sure it works. Console warning message below so I know which ones.
[WARNING] Citeproc: citation Zymoetz1_AMP.pdf not found
[WARNING] Citeproc: citation j_v_powelletal_GitxsanCanadian not found
[WARNING] Citeproc: citation tritonenvironmentalconsultantsltd.1998 not found
[WARNING] Citeproc: citation viveiros2011 not found

you could consider using citr - it seems like a much better option. I've stopped using the rmd source window. too glitchy and it kept recording bibtex entries that didn't match zotero

Good idea, I've also found visual mode to be quite buggy


Add .sst typeonly cli command for generation it in ci, to do typecheck

@joegearlesss isn't this the same as #5189?

@anaydotdev same! thanks


batch size limit?

what is the limit of the batch size? can we export 40k work item in one single export.

It's used to controll how many items are fetched at a time from Jira so no need to change that I would say. You can export many items but the services (Jira and Azure DevOps) have throttling so you may get degraded performance. I usually recommend migrating items in batches to be in control, one thing to be aware of then is to bucket all related items so you don't get into problems with missing links.
Good luck migrating!

@sgullluu The batch size is only used against the service apis to avoid fetchin data too eagerly. You have a good idea, I'll add it for the team to review. You can try to bucket exports using the JQL filter, for instance something like this matches items in a certain range:
project = scrum and id >SCRUM-10 and id <= SCRUM-20 order by id ASC


.headroom('destroy') isn't

I have (jQuery.)?headroom.js included in a common .js file loaded by all pages of a site, followed by a call to $(selector).headroom(options). All good, works great.
I then added a hero block above the main menu on the home page and needed to switch Headroom off specifically on that page. However, a simple call to $(selector).headroom('destroy') did not work. I tried to re-initialize with huge offset:
$(selector)
  .headroom('destroy')
  .headroom({offset: 100500})

to no avail. The destroy() method does not know anything about jQuery, so it does not remove jQuery data from the element and re-initlaization does not work.
I ended up with the following workaround:
$(selector)
  .headroom('destroy')
  .removeData('headroom')
  .headroom({offset: 100500})

but it looks dirty.

Hmm yeah, I see what you mean. I guess I'll have to intercept the destroy call in the jQuery plugin and do what you did with removeData. I think your approach is fine for now, or you can not use the jQuery plugin and use the standard API

Hello,
i re-open this issue, is there a way to destroy & relaunch headroom easily ? Once it is destroyed it's over ? ^^

@WickyNilliams this is a rather harsh decision, for me it is clear that if you make a wrapper you make all methods available through that wrapper. We now have to work around the problem ourselves, rather than the solution is made by the creator. You even close the bug without any doubt, but the bug is still there. I will try to make a pull request for it this week.
In the meanwhile i have a workaround that really works:
/**
 * Check if headroom is initialised before and kill it with fire!
 */
if($el.data('headroom')) {
    $el.data('headroom').destroy();
    $el.removeData('headroom');
}

This is possible because the jQuery wrapper assignes the Headroom object to data('headroom') and thus the .destroy() function is available through there. We destroy it, and then remove the headroom object from data. After this you can initialise headroom again.

You have a strange definition of harsh. And your tone isn't very polite. Remember open source authors are doing this in their free time, for no cost. Less of a sense of entitlement please.
I'd just advise, as I have before, using the raw Headroom object. It has a simple API, don't see any problem using it for more advanced cases like this

I'm not acting entitled, i presume that code is released with thought. Off-course there are always bugs and if those bugs are reported I, and with me many others, think they must not be ignored. At least leave the bug open just for someone who feels like pull requesting. If your opinion is to just use the raw Headroom object, then why not remove the jQuery(and other) wrappers all together?
I appreciate the effort others put in open source projects, and I apologise if I came over rather entitled or unpolite.

@bramsmulders thank you for your solution. one thing though, it fails to remove headroom--not-top when destroying if that class already exists.
However, looks like this issue is known:
https://github.com/WickyNilliams/headroom.js/pull/159

Never mentioned it here explicitly - but I fixed this bug.
@bramsmulders sorry for being a little uppity at the time, reading your comments back I think I misinterpreted your attitude!

Hi @WickyNilliams, thnx for the reply. I myself could have been less harsh in my initial response.

@bramsmulders I have updated my code which you had given. But nothing happened. I want to destroy headroom for iPhone landscape orientation when hamburger menu is open. Also remove that destroy option as soon as hamburger is close.


--assign-identity VS. --mi-system-assigned

The page said we needed to use '--assign-identity' when working with system-managed identity...
but I received a warning on pipelines that said:
WARNING: Argument 'assign_identity' has been deprecated and will be removed in a future release. Use '--mi-system-assigned' instead.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 19f647d0-36be-3633-03fa-eb5ad31169aa
Version Independent ID: 7476c99b-5867-2a21-62ed-8bd94e2b2b57
Content: az dt
Content Source: latest/docs-ref-autogen/dt.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

@wangzelin007 for awareness

Hi @rafaarcangel,
Can you try az dt create --dt-name ${{parameters.instanceName}} --resource-group ${{parameters.resourceGroup}} --location ${{parameters.region}} --mi-system-assigned?
Can you explain what exactly you mean by the page?
It would be even better if you can send the complete pipeline execution log.
You can click View raw log on the top right and copy the full log.

@Azure/azure-iot-cli-triage,
Maybe you should update the docs.

My pipeline runs successfully, with both commands. But there is a warning to change to 'new' my-system-assigned'.
This it's only a comment to update the documents you have on Microsoft, with the latest info:

https://learn.microsoft.com/en-us/azure/digital-twins/how-to-set-up-instance-cli -> section System-assigned identity command

Hi @rafaarcangel,
Thanks for your feedback, it has been routed to the azure-iot team.

Hi! I'm the author of the Azure Digital Twins document you mentioned above.
I've confirmed the parameter should be updated from --assign-identity to --mi-system-assigned, and made the update to this document (and in a few other spots) in this pull request: https://github.com/MicrosoftDocs/azure-docs-pr/pull/221769
This should resolve this issue. Thank you for helping us keep our docs up to date! :)

Closing issue as the doc has been updated for a while. If there are any other questions, feel free to create another issue


#1428: Updated Danish 'L' dateformat to use dots rather than slashes, aligning with article from DSN.

See argumentation at https://github.com/moment/moment/issues/1428#issuecomment-299046240
I kept the zero padding even though DSN says that it's "usually not requried," but it seems to be the way it's done in every other momentjs locale. This way l would give the DSN recommended output, while L would give one that's close, but has the zero padding. I don't think it would make sense to force those two to be the same. Input welcome if there is a better way to do this.
This is further complicated by the fact that DSN recommends three different formats, D.M.YYYY, D.M.YY and YYYY-MM-DD. I picked the one that is stated to be "traditional" with dots and full year specification.

@ichernev +1 - per discussion in that other ticket. We decided against it in the past but the Danes have convinced me that CLDR is just wrong here.

Will merge. If CLDR is wrong I guess it's wrong.


Prater logs - ATTESTATION_ERROR_PAST_EPOCH

Describe the bug
On Prater genesis with our extremely overloaded beacon seems to process block 2 (late) from somewhere (db, gossip?) and when processing it's attestations throws ATTESTATION_ERROR_PAST_EPOCH 178 times (all of them + some other block? note MAX_ATTESTATIONS=128). Is this error expected?
2021-03-23 15:18:42 [CHAIN]         verbose: Clock slot slot=93
2021-03-23 15:18:42 [CHAIN]           debug: Block pools:  pendingBlocks=0, currentSlot=93
2021-03-23 15:18:42 [CHAIN]         verbose: Block processed slot=2, root=0x629bd2acd1af7e70c0bc8a53bf28a6c3ca869106c23a4217c5bb03cdd8292690
2021-03-23 15:18:42 [CHAIN]         verbose: New chain head headSlot=2, headRoot=0x629bd2acd1af7e70c0bc8a53bf28a6c3ca869106c23a4217c5bb03cdd8292690
...
2021-03-23 15:18:42 [CHAIN]           debug: Attestation error code=ATTESTATION_ERROR_PAST_EPOCH, attestationEpoch=0, currentEpoch=2
Error: ATTESTATION_ERROR_PAST_EPOCH
    at validateAttestation (/root/lodestar/packages/lodestar/src/chain/attestation/validate.ts:39:11)
    at processAttestationJob (/root/lodestar/packages/lodestar/src/chain/attestation/processor.ts:44:5)
    at AttestationProcessor.processAttestationJob (/root/lodestar/packages/lodestar/src/chain/attestation/processor.ts:28:11)
    at fn (/root/lodestar/packages/lodestar/src/chain/eventHandlers.ts:238:42)
    at CompositeListTreeHandler.readOnlyMap (/root/lodestar/node_modules/@chainsafe/ssz/src/backings/tree/array.ts:347:19)
    at readOnlyMap (/root/lodestar/node_modules/@chainsafe/ssz/src/backings/readOnlyIterate.ts:25:43)
    at BeaconChain.onBlock (/root/lodestar/packages/lodestar/src/chain/eventHandlers.ts:237:10)
    at ChainEventEmitter.<anonymous> (/root/lodestar/packages/lodestar/src/chain/eventHandlers.ts:37:7)

Attestation queues have been changed to LIFO and https://github.com/ChainSafe/lodestar/pull/2876 will drop them if too overloaded


Update Mod to Support Enlightend Revamp

Enlightend just went through a massive revamp, leaving a lot of the foods added by this mod for compat with that, uncraftable.

Fixed in the latest version.


[Feature]: Please expose runToFrame() from sinon/fake_timers in @jest/fake-timers

🚀 Feature Proposal
Hi legends,
Could you please expose clock.runToFrame() from sinon/fake-timers in @jest/fake-timers? (@jest/fake-timers is mostly a re-export of sinon/fake-timers)

clock.runToFrame()
Advances the clock to the next frame, firing all scheduled animation frame callbacks, if any, for that frame as well as any other timers scheduled along the way.

Right now I am doing this workaround:
jest.advanceTimersByTime(16);

But this seems suboptimal as there is a bit of logic controlling how long the frame duration should be.
Motivation
I am looking to explicitly have a scheduled animation frame run in a test.
Example
// release the next animation frame
jest.runToFrame();

Pitch
It would be helpful to be able to use the runToFrame() to have more explicit control over animation frames

Yeah, happy to 🙂 Wanna send a PR?

Yep, can do

Pull request raised @SimenB


Add support for grouping conditions with and/or operators

In our project we would benefit from extra conditions for our Story's controls, to better match our more complex polymorphic component parameters.
Please check the new tests for example usage.

cc @tmeasday @shilman

Cc @kylegach

Nice work, @DiogoDoreto!
The API is as straightforward as I can imagine it being. I recommend that we only document one level of nesting, though, even if it's implemented recursively as it is here.
That said...

to better match our more complex polymorphic component parameters

I wonder if there's something better we could offer for this use case, that wouldn't require manually authoring a bunch of complex conditions. Whatever that is, it could likely be implemented as an auto-generation of this feature. So this PR is still valuable.

Thanks, @kylegach!
Regarding your last point, what we really thought about initially was to have the options of a control to be dynamic and based on the values of other controls. Since this was a major change from the current requirement of being statically defined we tried to avoid it. The current solution is to multiply the number of controls with pre-calculated options and predefined rules for visibility — where multiple conditions come in handy. And yes, we are autogenerating those :)

This would be great. Is anyone looking at this PR and going to see about merging it in?

Echoing that this would be fantastic. In our case, we're migrating from knobs to controls and finding control conditionals to be way too restrictive. While I like the idea here, I wonder if there would be yet more complex conditions that would require an escape hatch from the DSL here. This was brought up in https://github.com/storybookjs/storybook/issues/19135, where the suggestion was to allow developers to provide a function that would receive args and return true or false.
Is there a reason that couldn't also be added here, or done instead of this approach? I suspect it has to do with what @DiogoDoreto said:

Since this was a major change from the current requirement of being statically defined we tried to avoid it

Although I don't quite understand the requirement here or where it comes from?


Binding chromeless to Python

Is there anyway that I can bind chromeless to python ? I mean to say get chromeless to execute headless where as if we could bind the driver object of Selenium with chromeless to get the tests executed headless on chrome. Is that possible ? It would be great if we could do that because it is comapratively easier to run chrome headless on Mac through Canary but I havent made any success on running tests on headless on linux platform like CentOS or Ubuntu especially when running it on docker.

Not sure if I get you right but there're two Python projects which maybe interesting for you:
https://github.com/marty90/PyChromeDevTools
https://github.com/iiSeymour/chromote

thanks @githubixx sure will check it out once. Hope this would resolve the issue.

Still, it would be also great to have a Python binding to chromeless via the WebSocket/MQTT protocol.

@skion I've been playing around doing some transposition between original lib to python.
But I'm facing something reaaaaly dumb: for some reason, socket (from python) ensures your host is idna encode.... and I'm using aws labmda and hosts is not compatible in any way.
If you have any idea on how to handle it seems feasible!


The clean task does not report changes to VFS

The CachedPathSensitivityIntegrationTest tests fail on Windows (and the failure is masked by a VFS drop (see https://github.com/gradle/gradle/issues/11836#issuecomment-582619833) on macOS) because the clean builds in the middle of the tests do not properly report changes to the VFS.

cc: @gradle/build-cache

Note that it is not "the" clean task, but the way the ad-hoc clean task is added in CachedPathSensitivityIntegrationTest: https://github.com/gradle/gradle/blob/55f05f7d28b0c3cf66603895fce8ef768bee7222/subprojects/core/src/integTest/groovy/org/gradle/api/tasks/CachedPathSensitivityIntegrationTest.groovy#L34-L38
Replacing this task by applying the base plugin should fix the test.

Note that it is not "the" clean task, but the way the ad-hoc clean task is added in CachedPathSensitivityIntegrationTest:

OK. I added https://github.com/gradle/gradle/issues/12140 to handle this case better.


IN-1179 / IN-1184 / IN-1187 Annual report lodging details fixes

Purpose
IN-1179
IN-1184
IN-1187
Approach

Set bankstatementsreceived column values using rules in IN-1179
Fix bug when setting bankstatementdeadlinedate for IN-1184 (don't filter out '2' values in Further* columns)
Make date parsing more tolerant of bad data for IN-1187 (set bad values to null instead of accepting them as is)

Learning
n/a
Checklist

[ ] I have performed a self-review of my own code
[ ] I have done an adhoc run against preprod (only needed for high complexity PRs)
[ ] I have added relevant logging with appropriate levels to my code
[ ] I have updated documentation where relevant
[ ] I have added tests to prove my work
[ ] The product team have tested these changes

Hmm, not sure why @devkokov's review isn't good enough to allow me to merge.

Think he's not in the integrations team for some reason.


Vehicle Speed Calculator

Calculator Functions
I will be making a calculator which can be used for calculate the speed of a vehicle by taking inputs as distance travelled and time taken to travel the distance. The webpage will be responsive. I will be taking care of the SI units of sitsance, speed and time.
The technologies I will be using :

HTML
CSS
JavaScript

I will add the appropriate comments wherever necessary, so that it can be understood by each one.
Contribution Event
GSSOC22
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


fix: export controller component

Pull Request Template
Description
export Controller component

Codecov Report

Merging #117 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #117   +/-   ##
=======================================
  Coverage   50.39%   50.39%
=======================================
  Files         124      124
  Lines        1772     1772
=======================================
  Hits          893      893
  Misses        879      879

Impacted Files
Coverage Δ

...s/griffith/src/components/Controller/Controller.js
0% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 29355aa...401b2cc. Read the comment docs.


Code quality cleanup

This PR addresses the low-hanging fruit from Resharper warnings and suggestions. I've carefully reviewed every change to ensure it's correct and does not introduce breaking changes.

/azp run Steeltoe.All


Inconsistent assumptions over interface Netif

Tried to make main.ml, using a fresh install of Mirage on Ocaml 4.02.01 (fully up to date) on OS X.10.
Compilation unsuccessful after building 7 targets (0 cached) in 00:00:00.
make: *** [main.native] Error 10

There's a genuine clash here -- you should never be linking mirage-net-macosx (which provides a Mac Vmnet version of the Netif driver) with mirage-net-unix (which provides a tuntap Unix version of Netif) at the same time.
What's probably happening is that something is manually linking mirage-net-unix in, or otherwise pulling it in --Mort might be able to debug this in person better than me (i'm abroad atm)

On 15 Jul 2015, at 05:47, alistairfisher<EMAIL_ADDRESS>wrote:
Tried to make main.ml, using a fresh install of Mirage on Ocaml 4.02.01 (fully up to date) on OS X.10.  Compilation unsuccessful after building 7 targets (0 cached) in 00:00:00. make: *** [main.native] Error 10
—
Reply to this email directly or view it on GitHub https://github.com/mirage/mirage-net-macosx/issues/5.

Mort's in Nottingham today/tomorrow...
Alistair-- if you can point me to an online copy of the code in question, I
can take a quick look and see if anything obvious. In practice if you "opam
remove mirage-net-unix mirage-net-macosx" perhaps that will let you build
it for now?
On 15 July 2015 at 15:05, Anil Madhavapeddy<EMAIL_ADDRESS>wrote:

There's a genuine clash here -- you should never be linking
mirage-net-macosx (which provides a Mac Vmnet version of the Netif driver)
with mirage-net-unix (which provides a tuntap Unix version of Netif) at the
same time.
What's probably happening is that something is manually linking
mirage-net-unix in, or otherwise pulling it in --Mort might be able to
debug this in person better than me (i'm abroad atm)

On 15 Jul 2015, at 05:47, alistairfisher<EMAIL_ADDRESS>wrote:
Tried to make main.ml, using a fresh install of Mirage on Ocaml 4.02.01
(fully up to date) on OS X.10. Failed due to inconsistent assumptions, have
dumped the terminal output here.
findlib: [WARNING] Interface netif.cmi occurs in several directories:
/Users/alistair/.opam/4.02.1/lib/mirage-net-macosx,
/Users/alistair/.opam/4.02.1/lib/mirage-net-unix
ocamlfind ocamlc -c -g -annot -bin-annot -principal -thread
-strict-sequence -package tcpip.udp -package tcpip.ipv4-unix -package
tcpip.ethif-unix -package tcpip.dhcpv4 -package mirage-types.lwt -package
mirage-types -package mirage-net-macosx -package mirage-console.unix
-package mirage-clock-unix -package lwt -package ipaddr -package io-page
-package cstruct.syntax -package cstruct -package bytes -package lwt.syntax
-syntax camlp4o -o main.cmo main.ml findlib: [WARNING] Interface
netif.cmi occurs in several directories:
/Users/alistair/.opam/4.02.1/lib/mirage-net-macosx,
/Users/alistair/.opam/4.02.1/lib/mirage-net-unix
ocamlfind ocamlopt -c -g -annot -bin-annot -principal -thread
-strict-sequence -package tcpip.udp -package tcpip.ipv4-unix -package
tcpip.ethif-unix -package tcpip.dhcpv4 -package mirage-types.lwt -package
mirage-types -package mirage-net-macosx -package mirage-console.unix
-package mirage-clock-unix -package lwt -package ipaddr -package io-page
-package cstruct.syntax -package cstruct -package bytes -package lwt.syntax
-syntax camlp4o -o DHCPServer.cmx DHCPServer.ml findlib: [WARNING]
Interface netif.cmi occurs in several directories:
/Users/alistair/.opam/4.02.1/lib/mirage-net-macosx,
/Users/alistair/.opam/4.02.1/lib/mirage-net-unix
ocamlfind ocamlopt -c -g -annot -bin-annot -principal -thread
-strict-sequence -package tcpip.udp -package tcpip.ipv4-unix -package
tcpip.ethif-unix -package tcpip.dhcpv4 -package mirage-types.lwt -package
mirage-types -package mirage-net-macosx -package mirage-console.unix
-package mirage-clock-unix -package lwt -package ipaddr -package io-page
-package cstruct.syntax -package cstruct -package bytes -package lwt.syntax
-syntax camlp4o -o main.cmx main.ml findlib: [WARNING] Interface
netif.cmi occurs in several directories:
/Users/alistair/.opam/4.02.1/lib/mirage-net-macosx,
/Users/alistair/.opam/4.02.1/lib/mirage-net-unix
ocamlfind ocamlopt -g -linkpkg -linkpkg -thread -package tcpip.udp
-package tcpip.ipv4-unix -package tcpip.ethif-unix -package tcpip.dhcpv4
-package mirage-types.lwt -package mirage-types -package mirage-net-macosx
-package mirage-console.unix -package mirage-clock-unix -package lwt
-package ipaddr -package io-page -package cstruct.syntax -package cstruct
-package bytes -package lwt.syntax -syntax camlp4o DHCPServer.cmx main.cmx
-o main.native findlib: [WARNING] Interface netif.cmi occurs in several
directories: /Users/alistair/.opam/4.02.1/lib/mirage-net-macosx,
/Users/alistair/.opam/4.02.1/lib/mirage-net-unix File "none", line 1:
Error: Files main.cmx and
/Users/alistair/.opam/4.02.1/lib/mirage-net-macosx/mirage-net-macosx.cmxa
make inconsistent assumptions over interface Netif Command exited with code

Compilation unsuccessful after building 7 targets (0 cached) in
00:00:00. make: *** [main.native] Error 10

—
Reply to this email directly or view it on GitHub <
https://github.com/mirage/mirage-net-macosx/issues/5>.

—
Reply to this email directly or view it on GitHub
https://github.com/mirage/mirage-net-macosx/issues/5#issuecomment-121625575
.

--
Richard Mortier
<EMAIL_ADDRESS>

Alistair -- or mail<EMAIL_ADDRESS><EMAIL_ADDRESS>with the problem, as that'll help the wider developer base as well.  This error isn't an obvious one to debug if you havent seen it before.

On 15 Jul 2015, at 07:09, Richard Mortier<EMAIL_ADDRESS>wrote:
Mort's in Nottingham today/tomorrow...
Alistair-- if you can point me to an online copy of the code in question, I
can take a quick look and see if anything obvious. In practice if you "opam
remove mirage-net-unix mirage-net-macosx" perhaps that will let you build
it for now?
On 15 July 2015 at 15:05, Anil Madhavapeddy<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:

There's a genuine clash here -- you should never be linking
mirage-net-macosx (which provides a Mac Vmnet version of the Netif driver)
with mirage-net-unix (which provides a tuntap Unix version of Netif) at the
same time.
What's probably happening is that something is manually linking
mirage-net-unix in, or otherwise pulling it in --Mort might be able to
debug this in person better than me (i'm abroad atm)

On 15 Jul 2015, at 05:47, alistairfisher<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Tried to make main.ml, using a fresh install of Mirage on Ocaml 4.02.01
(fully up to date) on OS X.10. Failed due to inconsistent assumptions, have
dumped the terminal output here.
findlib: [WARNING] Interface netif.cmi occurs in several directories:
/Users/alistair/.opam/4.02.1/lib/mirage-net-macosx,
/Users/alistair/.opam/4.02.1/lib/mirage-net-unix
ocamlfind ocamlc -c -g -annot -bin-annot -principal -thread
-strict-sequence -package tcpip.udp -package tcpip.ipv4-unix -package
tcpip.ethif-unix -package tcpip.dhcpv4 -package mirage-types.lwt -package
mirage-types -package mirage-net-macosx -package mirage-console.unix
-package mirage-clock-unix -package lwt -package ipaddr -package io-page
-package cstruct.syntax -package cstruct -package bytes -package lwt.syntax
-syntax camlp4o -o main.cmo main.ml findlib: [WARNING] Interface
netif.cmi occurs in several directories:
/Users/alistair/.opam/4.02.1/lib/mirage-net-macosx,
/Users/alistair/.opam/4.02.1/lib/mirage-net-unix
ocamlfind ocamlopt -c -g -annot -bin-annot -principal -thread
-strict-sequence -package tcpip.udp -package tcpip.ipv4-unix -package
tcpip.ethif-unix -package tcpip.dhcpv4 -package mirage-types.lwt -package
mirage-types -package mirage-net-macosx -package mirage-console.unix
-package mirage-clock-unix -package lwt -package ipaddr -package io-page
-package cstruct.syntax -package cstruct -package bytes -package lwt.syntax
-syntax camlp4o -o DHCPServer.cmx DHCPServer.ml findlib: [WARNING]
Interface netif.cmi occurs in several directories:
/Users/alistair/.opam/4.02.1/lib/mirage-net-macosx,
/Users/alistair/.opam/4.02.1/lib/mirage-net-unix
ocamlfind ocamlopt -c -g -annot -bin-annot -principal -thread
-strict-sequence -package tcpip.udp -package tcpip.ipv4-unix -package
tcpip.ethif-unix -package tcpip.dhcpv4 -package mirage-types.lwt -package
mirage-types -package mirage-net-macosx -package mirage-console.unix
-package mirage-clock-unix -package lwt -package ipaddr -package io-page
-package cstruct.syntax -package cstruct -package bytes -package lwt.syntax
-syntax camlp4o -o main.cmx main.ml findlib: [WARNING] Interface
netif.cmi occurs in several directories:
/Users/alistair/.opam/4.02.1/lib/mirage-net-macosx,
/Users/alistair/.opam/4.02.1/lib/mirage-net-unix
ocamlfind ocamlopt -g -linkpkg -linkpkg -thread -package tcpip.udp
-package tcpip.ipv4-unix -package tcpip.ethif-unix -package tcpip.dhcpv4
-package mirage-types.lwt -package mirage-types -package mirage-net-macosx
-package mirage-console.unix -package mirage-clock-unix -package lwt
-package ipaddr -package io-page -package cstruct.syntax -package cstruct
-package bytes -package lwt.syntax -syntax camlp4o DHCPServer.cmx main.cmx
-o main.native findlib: [WARNING] Interface netif.cmi occurs in several
directories: /Users/alistair/.opam/4.02.1/lib/mirage-net-macosx,
/Users/alistair/.opam/4.02.1/lib/mirage-net-unix File "none", line 1:
Error: Files main.cmx and
/Users/alistair/.opam/4.02.1/lib/mirage-net-macosx/mirage-net-macosx.cmxa
make inconsistent assumptions over interface Netif Command exited with code

Compilation unsuccessful after building 7 targets (0 cached) in
00:00:00. make: *** [main.native] Error 10

—
Reply to this email directly or view it on GitHub <
https://github.com/mirage/mirage-net-macosx/issues/5 https://github.com/mirage/mirage-net-macosx/issues/5>.

—
Reply to this email directly or view it on GitHub
<https://github.com/mirage/mirage-net-macosx/issues/5#issuecomment-121625575 https://github.com/mirage/mirage-net-macosx/issues/5#issuecomment-121625575>
.

--
Richard Mortier
<EMAIL_ADDRESS><EMAIL_ADDRESS>—
Reply to this email directly or view it on GitHub https://github.com/mirage/mirage-net-macosx/issues/5#issuecomment-121626859.

I'm fairly sure I've isolated the error in the config file:

open Mirage
let main =
foreign "DHCPServer.Main" (console@->clock@->udpv4@->job)
let udp = direct_udp(default_ipv4(tap0)) <---here
let () =
(add_to_opam_packages, syntax)
add_to_ocamlfind_libraries(["tcpip.udp";"lwt";"tcpip.dhcpv4";"cstruct";"cstruct.syntax";"io-page";"bytes";"mirage-types";"ipaddr"]);
register "network" [
main $ default_console $ default_clock $ udp
]

I didn't realise that OS X didn't provide tap0, I believe it should be fixed if I just acquire my network implementation via netif instead.

That's the one!  MacOS X has something called "vmnet" which provides a builtin DHCP server for local services.  We built bindings to that instead of tuntap (which requires a kernel module and more messing around)

On 15 Jul 2015, at 07:27, alistairfisher<EMAIL_ADDRESS>wrote:
I'm fairly sure I've isolated the error in the config file:
open Mirage
let main =
foreign "DHCPServer.Main" (console@->clock@->udpv4@->job)
let udp = direct_udp(default_ipv4(tap0)) <---here
let () =
(add_to_opam_packages, syntax)
add_to_ocamlfind_libraries(["tcpip.udp";"lwt";"tcpip.dhcpv4";"cstruct";"cstruct.syntax";"io-page";"bytes";"mirage-types";"ipaddr"]);
register "network" [
main $ default_console $ default_clock $ udp
]
I didn't realise that OS X didn't provide tap0, I believe it should be fixed if I just acquire my network implementation via netif instead.
—
Reply to this email directly or view it on GitHub https://github.com/mirage/mirage-net-macosx/issues/5#issuecomment-121633309.


Redefine the unicode output condition for nanoserver for "more" function

Fix issue #2909
I haven't included a test case with this fix because

unicode issue is better to be judged by eye.
this issue only repros in a non-english windows system with ps running under cmd window. Our current test environment won't touch this scenario.

Thus, one time manual verification might be enough.
Summary of the issue:
Under non-english OS, if user start ps core under comandline and type "help ", the  output will be one character per line
Root cause of the issue:
Only Nano needs to use Unicode, but Windows and Linux need the default encoding. The way we judge if the current os is Nano server has been outdated.
Fix:
Update the condition we use to judge nano server.

I still would like to have a test for this fix. If it's really impossible, can you please at least have a screenshot to show the behavior difference before and after the fix?

Before the fix:

After the fix:

@daxian-dbw thanks! the comment has been resolved and the screenshots are attached.

@daxian-dbw resolved


[FEATURE] : Implementation of two way communication between PPL query and UI changes

Implementation of two way communication between PPL query and UI changes (features v1) according to #787
requirements -
On change of PPL query, UI of dimensions and metrics need to be updated and vice a versa.

This is implemented by Eric.


As a Developer, I WANT to add a drop down list, SO THAT the user can select the category of the best selling books to display

Acceptance Criteria:
GIVEN a drop down list with NYT best selling books categories
WHEN the user selects a category from the drop down list
THEN the best selling books will be displayed based on user selected criteria

functionality complete


Is there a way to extend the PauseBetweenStep?

Specifically, I noticed that some of your demos on Posh are fine except that at the end, when I'm trying to appreciate what the output actually looks like, it wraps and restarts too fast. E.g this one:
I don't know about you, but I need it to pause for 3 or 4 seconds more at the end, before it restarts. I think a good default might be to extend the length of the pause based on the length of the output...

@Jaykul I think that pauses need to be broken down into multiple types, and we might want to add a delay in line-by-line rendering.
I'd suggest we do a few things:

[ ] Pause for Different Times between Documentation Steps and Code Steps
[ ] Add a line-by-line delay in output (to control scroll speed)
[ ] Expose -Pause(s) in a Dictionary/PSObject parameter
[ ] Carry -Pause onto the Demo object

What do you think?
Would you like to take a quick crack?

@Jaykul added a -PauseBetweenLine(s) parameter that seems like the ticket.
Feel free to try and give your $0.02


Code change to add more details to parameter validation.

Adding checks to perform the validation as metioned on issues and display informative message to the user.

Codecov Report

Merging #7 into master will decrease coverage by 1.02%.
The diff coverage is 80.00%.

@@             Coverage Diff             @@
##            master       #7      +/-   ##
===========================================
- Coverage   100.00%   98.97%   -1.03%
===========================================
  Files            7        7
  Lines          185      195      +10
===========================================
+ Hits           185      193       +8
- Misses           0        2       +2

Impacted Files
Coverage Δ

asyncpgx/connection.py
95.55% <80.00%> (-4.45%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a3f86f0...7190f96. Read the comment docs.


Fix shape handling in nom_addGlobalDV

Purpose

This PR fixes the nom_addGlobalDV method in the MPhys wrapper so that it accepts scalar arguments to the value argument, just like the actual addGlobalDV method does. Previously this would fail because nom_addGlobalDV would try and evaluate len(value). The shape of the DV is now automatically extracted from the DV after it is added to the DVGeo object.
Also, I added a docstring because docs are nice.
Expected time until merged

1 week
Type of change

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (non-backwards-compatible fix or feature)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Documentation update
[ ] Maintenance update
[ ] Other (please describe)

Testing

Checklist

[x] I have run flake8 and black to make sure the Python code adheres to PEP-8 and is consistently formatted
[ ] I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
[ ] I have run unit and regression tests which pass locally with my changes
[ ] I have added new tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation

I have no idea what is going on with the docs build
WARNING: autodoc: failed to import class 'mphys.mphys_dvgeo.OM_DVGEOCOMP' from module 'pygeo'; the following exception was raised:
Traceback (most recent call last):
  File "/home/docs/checkouts/readthedocs.org/user_builds/mdolab-pygeo/envs/194/lib/python3.7/site-packages/sphinx/ext/autodoc/importer.py", line 58, in import_module
    return importlib.import_module(modname)
  File "/home/docs/checkouts/readthedocs.org/user_builds/mdolab-pygeo/envs/194/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/docs/checkouts/readthedocs.org/user_builds/mdolab-pygeo/checkouts/194/pygeo/mphys/__init__.py", line 1, in <module>
    from .mphys_dvgeo import OM_DVGEOCOMP
  File "/home/docs/checkouts/readthedocs.org/user_builds/mdolab-pygeo/checkouts/194/pygeo/mphys/mphys_dvgeo.py", line 4, in <module>
    import openmdao.api as om
  File "/home/docs/checkouts/readthedocs.org/user_builds/mdolab-pygeo/envs/194/lib/python3.7/site-packages/openmdao/api.py", line 20, in <module>
    from openmdao.components.exec_comp import ExecComp
  File "/home/docs/checkouts/readthedocs.org/user_builds/mdolab-pygeo/envs/194/lib/python3.7/site-packages/openmdao/components/exec_comp.py", line 1266, in <module>
    if Version(scipy.__version__) >= Version("1.5.0"):
  File "/home/docs/checkouts/readthedocs.org/user_builds/mdolab-pygeo/envs/194/lib/python3.7/site-packages/packaging/version.py", line 195, in __init__
    match = self._regex.search(version)
TypeError: expected string or bytes-like object

Seems to be missing the mphys module here https://github.com/mdolab/pygeo/blob/0e6b35609cd79eaa9c3f163ef90f0cf20352c7b1/doc/conf.py#L33

Oh nice, thanks for fixing that. This is ready to go now @bernardopacini @hajdik


Filter System

Closes #6

Ok all changes should be updated as per request. Wouldn't be a bad idea for you to go through and check that they are all in place how you would like them to be though.

Just added the ability for the user to specify if a word in the conditional filter needs to have a space in front of the word or not for the conditional filter to pick up on the word.

[ ] Update to use pathlib over os.path
[ ] Use str.translate over replace chains
[ ] Generalise 'word_found' logic to a single function
[ ] Remove useless commits
[ ] Invert logic for readability
[ ] Improve filtering in content_filter module

Non-English charaters
Non-printing charaters

[ ] Make content_filter comply with PEP8

Ok, so changes have been made now. I think that everything you wanted @mshaugh has been changed. If either of you two see anything I missed just tell me and I'll fix it. If you'd like anything else changed just tell me as well. Also sorry for the long delay. I've been busy and working on other stuff recently.

It's okay, we've been busy too. We still need to review Carberretta's infrastructure for the v2 release, so we'll review the changes after that's complete.

The feature has been added so that an automod action can be specified. The default action is just a warning but you can set an individual word to be a warn, kick, or ban when detected. Currently it is just a verbal warning but in the future this will integrate with the new moderation system for Carberretta v2 so that the warnings actually count and the kick and ban actually kick or ban the person. When the new moderation system is introduced, I can help with integrating the filter auto mod into it if needed/wanted.

I added a verbal warn action and the verbal warn action is now the default if an action is not provided. This will integrate into the new verbal/zero warn system for Carberretta in the future.

Superceded by #137.


🔔 Enable or disable notification

User can enable or disable notification (e.g. on completed torrent or when it starts)

Closed in 596c297


Settings of @changesets/read are incorrect and cause problems when using native esm

Affected Packages

pkg:@changesets/read
Problem

@changesets/read is not set as type: "module" currently, so dist/read.cjs.js will be used in native esm, but dist/read.cjs.prod.js is still wrapped into exports.default statement.
Proposed solution

Change dist/read.cjs.js like following:
'use strict';

if (process.env.NODE_ENV === "production") {
  module.exports = require("./read.cjs.prod.js").default;
} else {
  module.exports = require("./read.cjs.dev.js").default;
}

That would be nicer to migrate to type: "module" at the same time.

That's matching the declared interface. It's sort-of a node's problem that they have chosen to break compatibility with the existing tooling.
We'll be "fixing" this - but we can't say when exactly this will happen because it's a breaking change.

If you use exports field in package.json without any other changes, that would be still compatible for commonjs and native esm at same time.
{
  "exports": {
    "import": "xx.mjs", // notice `.mjs` is required
    "require": "xxx.js" // current commonjs entry
  }
}

No type: "module" required.

Unfortunately, to my great despair, this is not as easy. Right now you can use @changesets/read with ESM in node like this:
import read from '@changesets/read'

read.default()

After the proposed change the semantics would change and only this would be possible:
import read from '@changesets/read'

read()

So for existing users, this would classify as a breaking change.

I suppose no one will be using this pattern as it's just more rediculous than the original issue.
import read from '@changesets/read'

read.default()

Just ran into this, I was able to work around it via:
import _readChangesets from '@changesets/read'
// See https://github.com/changesets/changesets/issues/622
const readChangesets =
  _readChangesets.default as typeof import('@changesets/read/dist/declarations/src/index.js')['default']


How to make it works for cocoapods and vscode

I generated buildServer.json by following the steps in your blog https://wojciechkulik.pl/ios/the-complete-guide-to-ios-macos-development-in-neovim, but do not know how to make it works for cocoapods (xxx.xcworkspace which works in Xcode) and vscode. By the way, I use https://marketplace.visualstudio.com/items?itemName=sswg.swift-lang extension to start sourcekit-lsp.
{
	"name": "xcode build server",
	"version": "0.2",
	"bspVersion": "2.0",
	"languages": [
		"c",
		"cpp",
		"objective-c",
		"objective-cpp",
		"swift"
	],
	"argv": [
		"/usr/local/bin/xcode-build-server"
	],
	"workspace": "/Users/xxx/src/swift/iPush/iPush.xcworkspace",
	"build_root": "/Users/garden/Library/Developer/Xcode/DerivedData/iPush-dpxqkztzxzphizacjbclljrvvxvy",
	"scheme": "iPush",
	"kind": "xcode"
}

But I use VS Code, not vim. Forget it if you do not familiar with VSCode.

It should work out of the box if LSP is properly configured and buildServer.json is generated. Probably your LSP sets incorrectly root.
Here is my small guide to VS Code, you can check it out as well: https://wojciechkulik.pl/ios/how-to-develop-ios-and-macos-apps-in-other-ides-like-neovim-or-vs-code


Fail on wrong image name with two colons and no custom registry.

This PR makes the DockerImageName#assertValid method throw an exception if the image name contains more than one colon and there is no custom registry.
Tried to do as minimal impact as possible here and not bother with regexp because I think the naive way is the simplest solution
for the problem.
Fixes #5190

Thanks a lot for providing a PR that quickly 👍
Maybe we can take this as an opportunity, to align our validation with the Docker reference implementation (and thereby the spec). I have not checked in detail yet, but I think these parts of the reference implementatin should allow us to infer the format and align our implementation:

https://github.com/moby/moby/blob/085c6a98d54720e70b28354ccec6da9b1b9e7fcf/vendor/github.com/containerd/containerd/reference/docker/reference.go#L609
https://github.com/moby/moby/blob/085c6a98d54720e70b28354ccec6da9b1b9e7fcf/vendor/github.com/containerd/containerd/reference/docker/reference.go#L749


Update Controller.php

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
yes

Tests pass?
yes

Fixed issues

But why?
It only breaks the framework ...

Answer: It is very logical: SomeController, someAction

And Phalcon use that...

I think, do something, cause it works another way in other frameworks is a bad way. Moreover there is no any benefit. Not to mention the fact that it breaks all solutions based on yii2.