Create a tag specifically for bots, separeted from cheating players.

A clear and concise description of what the problem is.
As discussed in the tool's discord, some users have objections to using this tool against human cheaters because they might not be cheating at the moment. Also, even when desired, kicking a cheater as soon as it enters might be hard in some situations, specially if the cheater protests, which does not happen with bots.
Describe the solution you'd like

Separate "cheaters" into "cheaters" and "bots", where cheaters will only contain human players.
It needs to be decided if legacy "cheater" entries will now be moved to "bot" or if they will stay in "cheater".
For the official playerlist: there will be the need to manually reclassify each entry, which will probably take a long time if done passively (by pazer changing the tag when he encounters that cheater in particular)
Will there be a need for a warning when the user first starts the program after the update?
A setting to control the behavior of the new "cheater" tag to accommodate the philosophy of each user would be nice, how would that look like?

Describe alternatives you've considered
I've also considered doing away with the "exploiter" tag, as most users barely use it and I don't see exploits as a big issue currently.
I've made a separate thread to discuss this change here: #257
Please, don't hesitate to discuss this extensively, as it feels like a big change

From a ideological standpoint I am against any separation in treatment between human cheaters and automated cheaters. You don't get to join back to a community server because your cheats are supposedly off.
From a practical standpoint this should probably be done. The way this should be done is just replace the existing Exploiter tag with Human Cheater. There is a use case for dealing with them in a different way since they often deny allegations and will try to weasel out of a kick.
The worst possible answer to this would be to remove human cheaters from the official list.  By that argument GitHub shouldn't have issues, Google shouldn't do images, email shouldn't do attachments, and HTML5 wouldn't exist. Dealing with human cheaters is well within the theme of TF2BD and this functionality should remain. The only real difference between bots and human cheaters is that human cheaters are marginally more intelligent.

From a ideological standpoint I am against any separation in treatment between human cheaters and automated cheaters. You don't get to join back to a community server because your cheats are supposedly off.
From a practical standpoint this should probably be done. The way this should be done is just replace the existing Exploiter tag with Human Cheater. There is a use case for dealing with them in a different way since they often deny allegations and will try to weasel out of a kick.
The worst possible answer to this would be to remove human cheaters from the official list.  By that argument GitHub shouldn't have issues, Google shouldn't do images, email shouldn't do attachments, and HTML5 wouldn't exist. Dealing with human cheaters is well within the theme of TF2BD and this functionality should remain. The only real difference between bots and human cheaters is that human cheaters are marginally more intelligent.

I can agree that cheaters and bots should be treated equally, as nearly every cheater will have made an account specifically for cheating. Thus, it doesn't make sense for that account to not get kicked suddenly. However, I believe it would be useful to distinguish them anyways in playerlists, so I support adding a bot tag.
Since existing "cheater" playerlist entries could be a bot or a human, this could be kept as a generic tag, and a new tag for human cheaters could be added. Maybe in the UI display this as Generic Cheater or Cheater/Bot. This would allow for flexibility with existing local lists.
From what I understand, exploiter refers to stuff like building a teleporter in the enemy spawn. Do we really need to mark people for that? I would suggest dropping it entirely, however that may be done, but it doesn't hurt much to keep it, either.

I can agree that cheaters and bots should be treated equally, as nearly every cheater will have made an account specifically for cheating. Thus, it doesn't make sense for that account to not get kicked suddenly. However, I believe it would be useful to distinguish them anyways in playerlists, so I support adding a bot tag.
Since existing "cheater" playerlist entries could be a bot or a human, this could be kept as a generic tag, and a new tag for human cheaters could be added. Maybe in the UI display this as Generic Cheater or Cheater/Bot. This would allow for flexibility with existing local lists.
From what I understand, exploiter refers to stuff like building a teleporter in the enemy spawn. Do we really need to mark people for that? I would suggest dropping it entirely, however that may be done, but it doesn't hurt much to keep it, either.

i completely disagree, i think adding more tags make it more complicated than it needs to be

i completely disagree, i think adding more tags make it more complicated than it needs to be

I wonder if the current functionality should remain default, but via Settings, you can choose to distinguish all cheaters from human cheaters.
By default, Cheater and Human Cheater will be treated exactly the same: as a generic Cheater. And you can only mark people as a Cheater. But by flicking the right switch, you get to use and see the additional tag.
Keeps the program simple, until simple isn't enough.

I wonder if the current functionality should remain default, but via Settings, you can choose to distinguish all cheaters from human cheaters.
By default, Cheater and Human Cheater will be treated exactly the same: as a generic Cheater. And you can only mark people as a Cheater. But by flicking the right switch, you get to use and see the additional tag.
Keeps the program simple, until simple isn't enough.

By default, Cheater and Human Cheater will be treated exactly the same: as a generic Cheater. And you can only mark people as a Cheater. But by flicking the right switch, you get to use and see the additional tag.

This might get very messy to manage. If a person starts using the program without the distinction and then wants to make the switch after already having marked a bunch of accounts as generic cheater then he/she would have to start re categorizing them once she sees them in-game again.
In my opinion, the best way to go about this is to convert all legacy cheater to legacy cheater´ and only use it for compatibility with older lists, and always have cheaterandbotin the UI, then have a setting about what to do withcheaterswhilelegacy cheater` retains the legacy behavour. The options might be:

chat warning for both teams
chat warning for enemies and kick for teammates
kick for teammates
nothing
This way, old tags will be gradually moved to the new ones by manually retagging them, but people starting now will not have to deal with this if they switch stance towards human cheaters one way or the other.

Also, I personally prefer the naming used here as opposed to the ones cited above, but this is a minor point as all of them are descriptive enough.

By default, Cheater and Human Cheater will be treated exactly the same: as a generic Cheater. And you can only mark people as a Cheater. But by flicking the right switch, you get to use and see the additional tag.

This might get very messy to manage. If a person starts using the program without the distinction and then wants to make the switch after already having marked a bunch of accounts as generic cheater then he/she would have to start re categorizing them once she sees them in-game again.
In my opinion, the best way to go about this is to convert all legacy cheater to legacy cheater´ and only use it for compatibility with older lists, and always have cheaterandbotin the UI, then have a setting about what to do withcheaterswhilelegacy cheater` retains the legacy behavour. The options might be:

chat warning for both teams
chat warning for enemies and kick for teammates
kick for teammates
nothing
This way, old tags will be gradually moved to the new ones by manually retagging them, but people starting now will not have to deal with this if they switch stance towards human cheaters one way or the other.

Also, I personally prefer the naming used here as opposed to the ones cited above, but this is a minor point as all of them are descriptive enough.

Something else that needs discussion is how to go about updating rulesets for automatic tagging. Since older versions of the tool still in use will not understand the new tags, updating the ruleset will break it on older versions. So a legacy rulesets might have to be put in place to cater to them until only a small portion of the user base is not in the newer version.
This process might be expedited by making this change in a major version like 1.3 or something.

Something else that needs discussion is how to go about updating rulesets for automatic tagging. Since older versions of the tool still in use will not understand the new tags, updating the ruleset will break it on older versions. So a legacy rulesets might have to be put in place to cater to them until only a small portion of the user base is not in the newer version.
This process might be expedited by making this change in a major version like 1.3 or something.

I believe adding new tags will require a schema update. Older versions of the tool would probably display some sort of error when lists update to the new version. That should prompt users to update, so maintaining list compatibility with older versions of the tool shouldn't be necessary.

I believe adding new tags will require a schema update. Older versions of the tool would probably display some sort of error when lists update to the new version. That should prompt users to update, so maintaining list compatibility with older versions of the tool shouldn't be necessary.

My view is that there should be a distinction between a human cheater and a bot. I use this tool to kick bots, I don't really need the tool to auto kick human cheaters as it is easy enough to do that manually. In addition to that, I see no point in trying to auto kick a human cheater as in many cases the vote will fail. People won't just vote yes just because a random player on the server says he is cheating. I had to disable this tool when it tried to kick a real player with 2k hours in TF2 and the vote failed. I played with him for 30 minutes and he played different classes etc.  He was hitting a lot of headshots with sniper + spy but no one accused him of cheating.
At the very least I should be able to disable the auto kick for specific players on the official list so I don't have to disable it entirely.

Its really hard and unreliable to destinguish bots from real humans automatically so i think its a useless option

I use this tool to kick bots, I don't really need the tool to auto kick human cheaters as it is easy enough to do that manually. In addition to that, I see no point in trying to auto kick a human cheater as in many cases the vote will fail.
I agree, the benefit from having human cheater as an option is basically that you are aware that they have cheated in the past from the moment they join the server, and can react however you would like to. In my experience, using VC to say that I've played with the cheater in the past and know he is cheating usually works, even if the player protests.

I had to disable this tool when it tried to kick a real player with 2k hours in TF2 and the vote failed. I played with him for 30 minutes and he played different classes etc. He was hitting a lot of headshots with sniper + spy but no one accused him of cheating.

Yea, them not cheating at that moment doesn't mean they have not cheated, but you being suspicious is understandable since it was Pazer that marked the player, not you yourself. This goes into what was originally discussed in the discord server about the official list requiring a trust in the maintainer that some players do not have, and in that case they can always disable the list.

At the very least I should be able to disable the auto kick for specific players on the official list so I don't have to disable it entirely.

I agree, unmarking a STEAMID is useful if used sparingly and it's not currently an option.

In my experience, using VC to say that I've played with the cheater in the past and know he is cheating usually works, even if the player protests.

Do you say this even when you haven't played with the player? When they were added to list by pazer and you don't know why.

This goes into what was originally discussed in the discord server about the official list requiring a trust in the maintainer that some players do not have, and in that case they can always disable the list.

I didn't realize you could disable the official list and just use your own list. Do you just remove it from the cfg folder? I thought it just redownloaded it when you launched the tool.

Do you say this even when you haven't played with the player? When they were added to list by pazer and you don't know why.

Since I live in a different region, I never encounter manual marks from the official playerlist. However, if you hover over the player in the tool's playerlist you can see what file the mark is coming from.

I didn't realize you could disable the official list and just use your own list. Do you just remove it from the cfg folder? I thought it just redownloaded when you launched the tool.

Annoyingly you have to leave the file blank instead of deleting it. This should probably be changed
I think it's best keep other questions like that to the tool's discord so this discussion doesn't get too offtopic


Issue with billing and shipping address defaulting to US

When going through the checkout with a UK customer I could see that the address kept defaulting to US. I have found an issue in the code that I will submit a fix for. It is currently using:
/packages/community_store/single_pages/checkout.php
in_array($country, $billingCountries)
in_array($country, $shippingCountries)

and should be using:
array_key_exists($country, $billingCountries)
array_key_exists($country, $shippingCountries)

Will create PR for this....

I've pulled this update from your master branch, in case there's a bit more time involved testing that branch


Add a Dismiss button in CSS Grid Layout error modal

cc @malx122

No longer relevant, Launcher now uses juicy-tile-table which works in all browsers.


Allow to enable extended error codes

It would be great if there was a way to enable extended error codes in SQLite to diagnose issues. See https://www.sqlite.org/c3ref/extended_result_codes.html and https://www.sqlite.org/c3ref/errcode.html

As far as I can tell, this would be a breaking change?
Happy to do it one day but just want to check 🙂

How so?


Allow issue numbers as scope

I'd like to use issue numbers (like #1) as scope but according to https://www.conventionalcommits.org/ this is not valid, so this is not a bug report.
Would it be a good addition to add an option to allow everything as a scope?

For context:

A scope MAY be provided after a type. A scope MUST consist of a noun describing a section of the codebase surrounded by parenthesis, e.g., fix(parser):

They have also started on a grammar.  git-conventional was updated to mostly match the grammar, e.g. see scope's parser.
That said, I would recommend not abusing the fact that we can't validate the semantics of your scope.  The scope is meant to convey a specific type of context that issue numbers do not.

Also, if there is a specific problem you've had with having a commit parsed, please open a bug report with the reproduction case


Wrong short date tranlation for locale tr

Describe the bug
According to Turkish Language Association.
Translations are wrong for short versions of Monday and Saturday in Turkish.
Case -> Pts and Cts.
Expected behavior
Monday : Pzt instead of Pts
Saturday: Cmt instead of Cts
Screenshots

Does the changes on this PR #5756 fix the problem?

@DiegoBousfield Yes.


Quantity of columns are limited!!

Summary of problem or feature request
I've noticed that only 8 columns I can list. I spent lot of time guessing why I was getting an "Ajax error" when the rest of the sections are working perfectly with the same syntax.
I delete a column into the view and it is working.
I would like to know where can I change that limitation.
Thank you

Windows 10
PHP 7.0
Laravel 5.5
Laravel-Datatables 8

I currently use 15 columns, so I doubt there is a hardcoded limit of how many cols you can see.

This might be a browser issue specifically IE. Try using POST on your ajax request.


Modify form variables

In some pull request comment thread, @gdmcbain had a good idea of using 'dataclass-type approach' for the additional form variables.
https://github.com/kinnala/scikit-fem/pull/24#issuecomment-410960587
I think something like this should be implemented. I'm not happy about adding attrs-dependency though if it's not used in more than one place.
It should be evaluated whether attrs is a reasonable dependency (= is used for more than one thing) or whether a custom approach is better.

Although ‘reasons to prefer attrs over Data Classes’ have been given by the authors of the former, I've just taken a look at the dataclasses added to the Standard Library in 3.7 and they seem to have all the features that I use.  However, as scikit-fem is currently at 3.6, as is the popular Anaconda Distribution, it might be too early to require that.  One approach is simply to wait till 3.7 is more widely adopted; shouldn't be too long, I wouldn't think.
The closest thing available in the Standard Library before 3.7 was typing.NamedTuple.  Indeed, I was using these before I heard about attrs.  They would probably suffice here too I think.  I might attempt that in a branch.
Although I haven't looked into the scikit-fem internals here, it also occurs to me that the implementation might not really matter insofar as consistency of the interface is concerned so long as the w argument has attributes w.x, w.h, w.n, &c., since the user just accesses these in writing linear and bilinear forms and w itself is by default and usually defined behind the scenes in the default_parameters method of InteriorBasis or FacetBasis.  Thus, because of duck-typing, it wouldn't matter if today default_parameters returned a typing.NamedTuple and tomorrow a dataclasses.dataclass and the user wouldn't notice (unless of course they were still using 3.6).  Further, the assembly module could use typing.NamedTuple in default_parameters and a 3.7 user overriding it by explicitly passing w to assembly.asm could pass in a dataclasses.dataclass and all would be well, so long as both had required attributes x, h, n, or some combination thereof.

Actually with w as a typing.NamedTuple, it's possible to access the self.global_coordinates() as either w.x or x[0]; not that backward-compatibility need necessarily be too much of a concern at v. 0.1.7.


REST API

Having a REST API would be useful to anyone seeking to obtain raw data, rather than having to scrape the site. I'm personally interested in the data to see how various voting systems would affect the outcome.

NB: An API would also be great to submit ballots!


DIGEQ-56 Respondent view rich text form field

What
This PR creates a RichTextField that enables an Author to create
a text box in their questionnaire to inform a respondent.
We've added a new convertor to jsonforms and created a whitelist
approach to HTML tags based on the python bleach package.
This commit also creates a folder for test fixtures so that we can
create a range of new survey examples without having to have the
strings inline in the test files.
The requirements have been updated and will require a rebuild of
our downstream docker images.
We created a custom widget for displaying a text block.
How to test

Create a new environment, a new survey and questionnaire with a RichTextBox.
Add some html tags to that box, including script and similar tags.
Save the questionnaire.
View in the Survey runner.
The expected output is that only allowed print styles (bold, italic, underline) should be allowed to be rendered and not the script example.

Who can test
Anyone but @dhilton or @LJBabbage

All good but underlining doesn't work. Thinking about it underlined text is usually interpreted by a user as a hyperlink so it's probably a good thing it doesn't work, might want to revisit the story.
:+1:


Convert UDS writers to use UnixDatagram instead of UnixStream

https://github.com/tshlabs/cadence/pull/86 used the wrong UDS protocol. This PR uses the correct protocol along with some cleanup.
Fixes https://github.com/tshlabs/cadence/issues/88

Please let me know if you'd like me to convert the TODO into a GitHub Issue.

Looks good. Rebase to a single commit and I'll merge. Thanks!

Nm, I did the merge + rebase

Thanks! Could you do a cargo release with this added in?

It'll be a little while before I'm ready to do the next release.


Support bzr repositories + add a "name" field.

Hello,
we're starting to use this tool for our codebase but we're using bzr as a VCS.
This pull request adds support for bzr repositories (via the json configuration) and adds also an optional field called "name" that allows a different name to be displayed in the HTML page, this is due to the fact that bazaar branches have weird names that might be misleading, for example we have repo1/releases/2015-02 and repo2/releases/2015-02 and Hound's default behavior is to show only the latest part of the url (in this case "2015-02" which is not that helpful).
Feel free to merge if you're interested.

I don't really like the name option, since that's kind of the purpose of the key in the config. I'd prefer if we just had the JS use that by default instead of the last portion of the URL. For example, you can have something like:
{
    "dbpath" : "data",
    "repos" : {
        "ThisIsjQuery" : {
            "url" : "https://www.github.com/jQuery/jQuery.git"
        }
    }
}

Right now Hound will show "jQuery" in the UI next to search results, but it should probably show "ThisIsjQuery". This way you can customize the name of the repo there and we don't need another element in the config to do so.
Can you make this change as part of this PR?

Of course, but I won't be able to do that until monday :smile:

Closing this PR in favor of a new one.


Update microsoft-defined-bluetooth-hci-commands-and-events.md

Corrected the flags to align with the current HLK validation and meaning defined in headers.

Thanks for the PR Frank!


Put a code sample at the top of the documentation

Would be helpful for starting our with the API.

Will do as part of tutorial/quickstart push.


Solving issue of "streaming link decryption is not working"

Problem
The streaming link decyption method is not working , because the key you are using is not correct.
Possible solution
I explored other repos too but none of their keys are correct. I also saw that the repo consumet is using to decrypt the link is not correct as well
Alternatives
I suggest to write your own function/script to extract those keys perfectly without depending on other's repo
Suggested solution
You can implement this logic, currently this is working fine
function matchingKey(value, script) {
  const regex = new RegExp(`,${value}=((?:0x)?([0-9a-fA-F]+))`);
  const match = script.match(regex);
  if (match) {
    return match[1].replace(/^0x/, "");
  } else {
    throw new ErrorLoadingException("Failed to match the key");
  }
}
function getKeys(script) {
  const regex =
    /case\s*0x[0-9a-f]+:(?![^;]*=partKey)\s*\w+\s*=\s*(\w+)\s*,\s*\w+\s*=\s*(\w+);/g;
  const matches = script.matchAll(regex);
  const indexPairs = Array.from(matches, (match) => {
    const matchKey1 = matchingKey(match[1], script);
    const matchKey2 = matchingKey(match[2], script);
    try {
      return [parseInt(matchKey1, 16), parseInt(matchKey2, 16)];
    } catch (e) {
      return [];
    }
  }).filter((pair) => pair.length > 0);
  return indexPairs;
}
const script = await axios.get('https://rapid-cloud.co/js/player/prod/e6-player-v2.min.js');
console.log(getKeys(script.data))

Expected Output
[ [ 36,6 ] , [ 90,7 ] , [ 118 , 7 ] ]
let me know if it works

@itzzzme hey thank you so much for sharing this info. I'll try it out sometime and see how it goes.

@ghoshRitesh12 , sure , it works for both rapid-cloud and megacloud server so you can implement this for both server

@itzzzme Thank you so much for this ❤


Subscription model

Represents a User's subscription to hackathons within a specific geographic location

Belongs_to User, required: true
Address: string
Latitude: float
Longitude: float
Aasm_state: subscribed, unsubscribed
Timestamps (created_at & updated_at)

Subscriptions should be unique with respect to the following:

User
Parsed location (city, state, county)

Any duplicate subscription requests should be idempotent, and respond with a success

Handled by https://github.com/hackclub/hackathons-backend/pull/54


WFS Provider

Describe the bug
I am not able to create a wfsprovider from latest version 4.0.0-beta.8
WfsProvider method with URI parameter raises System.NullReferenceException: 'Object reference not set to an instance of an object.'
on calling InitAsync() method
To Reproduce
Steps to reproduce the behavior:

Create a WFSProvidere with

Call .InitAsync() method on the WFSProvider instance.
Handle the exception
See the error

Expected behavior
System.NullReferenceException: 'Object reference not set to an instance of an object.'
Screenshots

Desktop (please complete the following information):

Windows 11
4.0.0-beta.8

Smartphone (please complete the following information):

Windows Application

You should use WfsProvider.CreateAsync ... and WmsProvider.CreateAsync ... because Constructors cannot be asynchronous this methods initialize the wfs and wms provider asynchronous because a http call is involved.

Ok, now i've tried this code:
        protected async override void OnAppearing()
        {
            base.OnAppearing();

            mapView.Map = await CreateMapAsync();

            Mapsui.Widgets.ScaleBar.ScaleBarWidget scale = new Mapsui.Widgets.ScaleBar.ScaleBarWidget(mapView.Map)
            {
                TextAlignment = Alignment.Center,
                HorizontalAlignment = HorizontalAlignment.Center,
                VerticalAlignment = VerticalAlignment.Top
            };
            mapView.Map.Widgets.Add(scale);
        }

        public static async Task<Mapsui.Map> CreateMapAsync()
        {
            var map = new Mapsui.Map { CRS = "EPSG:3857" };
            map.Layers.Add(await CreateLayerAsync());
            return map;
        }

        public static async Task<ILayer> CreateLayerAsync()
        {
            return new ImageLayer("mainmap") { DataSource = await CreateWmsProviderAsync() };
        }

        private static async Task<WmsProvider> CreateWmsProviderAsync()
        {
            const string wmsUrl = "http://sgi2.isprambiente.it/arcgis/services/raster/igm25k_lazio_wgs/ImageServer/WMSServer?service=wms&request=getCapabilities&version=1.3.0";
            var provider = await WmsProvider.CreateAsync(wmsUrl, persistentCache: null);
            provider.ContinueOnError = true;
            provider.TimeOut = 20000;
            provider.CRS = "EPSG:3857";
            provider.AddLayer("igm25k_lazio_wgs");
            provider.SetImageFormat((provider.OutputFormats)[0]);
            return provider;
        }

I obtain the following error:
System.ApplicationException: 'Could not download capabilities'

I would try https instead of http.

I corrected the above code and tried again but nothing changes.
It should be noted that if I launch the link in the browser the capabilities xml file is loaded correctly.

I fixed here a WMSProvider Bug too.
https://github.com/Mapsui/Mapsui/pull/2007
The wms Http request was missing service=wms // newer wms service complain about it. older seem to not care.

this line sets the image format to
provider.SetImageFormat((provider.OutputFormats)[0]);
I think this is a missing case that needs to be handled in BitmapHelper.LoadBitmap
image/tiff

Because without the Style = RasterStyle() mapsui does not know how to render the imagelayer

This has caused confusion before. We need to improve it. The behavior needs to be consistent for all styles though.

I would suggest that The ImageLayer has RasterStyle set as default. So it would work out of the box. But still be customizable.

I've tried the code suggested by inforithmics without success:
`
    protected async override void OnAppearing()
    {
        base.OnAppearing();

        mapView.Map = await CreateMapAsync();
    }

    public async Task<Map> CreateMapAsync()
    {
        var map = new Map {
            CRS = "EPSG:3857"
        };

        Mapsui.Widgets.ScaleBar.ScaleBarWidget scale = new Mapsui.Widgets.ScaleBar.ScaleBarWidget(mapView.Map)
        {
            TextAlignment = Alignment.Center,
            HorizontalAlignment = HorizontalAlignment.Center,
            VerticalAlignment = VerticalAlignment.Top
        };
        map.Widgets.Add(scale);

        map.Layers.Add(await CreateLayerAsync());
        return map;
    }

    public static async Task<ILayer> CreateLayerAsync()
    {
        return new ImageLayer("mainmap")
        {
            DataSource = await CreateWmsProviderAsync(),
            Style = new RasterStyle()
        };
    }

    private static async Task<WmsProvider> CreateWmsProviderAsync()
    {
        const string wmsUrl = "https://sgi2.isprambiente.it/arcgis/services/raster/igm25k_lazio_wgs/ImageServer/WMSServer?service=wms&request=getCapabilities&version=1.3.0";
        var provider = await WmsProvider.CreateAsync(wmsUrl, persistentCache: null);
        provider.ContinueOnError = true;
        provider.TimeOut = 20000;
        provider.CRS = "EPSG:3857";
        provider.AddLayer("igm25k_lazio_wgs");
        provider.SetImageFormat((provider.OutputFormats)[1]);
        return provider;
    }

`
Note that EPSG:3857 is not contained in the xml capabilities.
There are only: CRS:84, EPSG:4326, EPSG:0 (what does it mean?).
May be this the problem?
Thank you.

You should use EPSG:4326 and use a projection provider

Mapsui Projection.
https://mapsui.com/documentation/projections.html

There is something special about this wms service. Because in the sample I created here it still does not get the right data. My guess it fetches the wrong coordinates. But still investigating.
https://github.com/Mapsui/Mapsui/pull/2008

Thank you for info.
I've made another test with this server (Spain orthophoto):
https://www.ign.es/wms-inspire/pnoa-ma?service=wms&request=getCapabilities
the layer is:
OI.OrthoimageCoverage
Test 1: map CRS: EPSG:3857, CRS provider: EPSG:3857 => it works fine
Test 2: map CRS: EPSG:3857, CRS provider: EPSG:4326 => map is shown but scale is wrong and perhaps coordinates
Test 3: map CRS: EPSG:4326, CRS provider: EPSG:4326 => as above
May be test 2 needs implementing Mapsui projection as inforithmics said.
Why test 3 doesn't work?
Thank you.

The wms server you are using is an Archivs server. Maybe you can use mapsui.Archie's to fetch the data.

Sorry but I'm a bit confused.
Where do you know that the server is Archivs (or Archie)?
I've never heard of it before.
In other environments (eg: OpenLayers) it is a WMS server like any other.

Auto correction error I meant ArcGis

How do you know it's an ArcGIS server?
Is there any documentation or examples on Masui.ArcGIS?

It's only a guess because it has arcgis in it's url.

Thank you. I'll try it.
However it responds with a classic XSD WMS version 1.3.0.
In OpenLayers the provider used for both my examples is the same (ol.source.TileWMS).

The ArcGIS WMS is supposed to follow the OGC standard. It can always be a bit different but I would expect the implementation is correct. It probably works correctly in a QGIS client as well.

It is the crs: with EPSG:4326 the axis are changed.
see:
https://github.com/Mapsui/Mapsui/issues/1925#issuecomment-1493411132

The "DPI", "MAP_RESOLUTION" and "FORMAT_OPTIONS" parameters are not actually needed.
So both link are identical except the order of the coordinates.
I know post #1925, I reported this issue but I thought the release candidate version fixed it.
I've tried the following code:
`
    protected async override void OnAppearing()
    {
        base.OnAppearing();

        mapView.Map = await CreateMapAsync();
    }

    public async Task<Map> CreateMapAsync()
    {
        var map = new Map {
            CRS = "EPSG:3857"
        };

        Mapsui.Widgets.ScaleBar.ScaleBarWidget scale = new Mapsui.Widgets.ScaleBar.ScaleBarWidget(mapView.Map)
        {
            TextAlignment = Alignment.Center,
            HorizontalAlignment = HorizontalAlignment.Center,
            VerticalAlignment = VerticalAlignment.Top
        };
        map.Widgets.Add(scale);

        map.Layers.Add(await CreateLayerAsync());
        return map;
    }

    public static async Task<ILayer> CreateLayerAsync()
    {
        return new ImageLayer("mainmap")
        {
            DataSource = await CreateWmsProviderAsync(),
            Style = new RasterStyle(),
            Attribution = new Hyperlink() {
                Text = "attributions"
            }
        };
    }

    private static async Task<WmsProvider> CreateWmsProviderAsync()
    {
        const string wmsUrl = "https://sgi2.isprambiente.it/arcgis/services/raster/igm25k_lazio_wgs/ImageServer/WMSServer?service=wms&request=getCapabilities&version=1.3.0";
        var provider = await WmsProvider.CreateAsync(wmsUrl, persistentCache: null);
        provider.ContinueOnError = true;
        provider.TimeOut = 20000;
        provider.CRS = "CRS:84";
        provider.AddLayer("igm25k_lazio_wgs");
        provider.SetImageFormat((provider.OutputFormats)[1]);
        return provider;
    }
}

`
The map is shown but there is an error on scale and coordinates. Zoom flickers.

I've tried this server also but the map isn't shown:
https://geoportale.regione.lazio.it/geoserver/ows?service=wms&request=getCapabilities&version=1.3.0
layer: "geonode:ctr_5k_retiled"
However, it should be considered that not all services have CRS:84.

I saw that there is a ProjectionProvider missing in Mapsui I'll add it to in the pull request.

After the pull request with the fixes goes on this sample should work now.
using Mapsui.Cache;
using Mapsui.Layers;
using Mapsui.Providers.Wms;
using System.Threading.Tasks;
using Mapsui.Nts.Extensions;
using Mapsui.Providers;
using Mapsui.Styles;
using NetTopologySuite.Geometries;

namespace Mapsui.Samples.Common.Maps.DataFormats;

public class WmsProjectionSample : ISample
{
    public string Name => " 6 WMS Projection";
    public string Category => "Data Formats";
    public static IUrlPersistentCache? DefaultCache { get; set; }

    public async Task<Map> CreateMapAsync()
    {
        var map = new Mapsui.Map
        {
            CRS = "EPSG:3857",
        };

        // The WMS request needs a CRS
        map.Layers.Add(await CreateLayerAsync());
        return map;
    }

    public static async Task<ILayer> CreateLayerAsync()
    {
        var dataSource = new ProjectingProvider(await CreateWmsProviderAsync())
        {
            CRS = "EPSG:3857"
        };

        return new ImageLayer("mainmap")
        {
            DataSource = dataSource,
            Style = new RasterStyle()
        };
    }

    private static async Task<WmsProvider> CreateWmsProviderAsync()
    {
        const string wmsUrl = "https://sgi2.isprambiente.it/arcgis/services/raster/igm25k_lazio_wgs/ImageServer/WMSServer?service=wms&request=getCapabilities&version=1.3.0";
        var provider = await WmsProvider.CreateAsync(wmsUrl, persistentCache: DefaultCache);
        provider.ContinueOnError = true;
        provider.TimeOut = 20000;
        provider.CRS = "EPSG:4326";
        provider.AddLayer("igm25k_lazio_wgs");
        provider.SetImageFormat((provider.OutputFormats)[1]);
        return provider;
    }
}

I've tried this code:
`
using System.Threading.Tasks;
using Xamarin.Forms;
using Mapsui;
using Mapsui.Layers;
using Mapsui.Providers.Wms;
using Mapsui.Extensions;
using Mapsui.Widgets;
using Mapsui.Styles;
using Mapsui.Cache;
using System.ComponentModel;
using Mapsui.Projections;
using System.Collections.Generic;

namespace OkMap.Views
{
	public partial class Maps : ContentPage
	{
		public static IUrlPersistentCache DefaultCache { get; set; }

		public  Maps()
		{
			InitializeComponent();
		}

		protected async override void OnAppearing()
		{
			base.OnAppearing();

			mapView.Map = await CreateMapAsync();
			mapView.Map.Navigator.ViewportChanged += mapView_ViewPortChanged;
		}

		public async Task<Map> CreateMapAsync()
		{
			var map = new Map {
				CRS = "EPSG:3857"
			};

			Mapsui.Widgets.ScaleBar.ScaleBarWidget scale = new Mapsui.Widgets.ScaleBar.ScaleBarWidget(mapView.Map)
			{
				TextAlignment = Alignment.Center,
				HorizontalAlignment = HorizontalAlignment.Center,
				VerticalAlignment = VerticalAlignment.Top
			};
			map.Widgets.Add(scale);

			map.Layers.Add(await CreateLayerAsync());
			return map;
		}

		public static async Task<ILayer> CreateLayerAsync()
		{
			return new ImageLayer("mainmap")
			{
				DataSource = await CreateWmsProviderAsync(),
				Style = new RasterStyle(),
				Attribution = new Hyperlink() {
					Text = "attributions"
				}
			};
		}

		private static async Task<WmsProvider> CreateWmsProviderAsync()
		{
			const string wmsUrl = "https://sgi2.isprambiente.it/arcgis/services/raster/igm25k_lazio_wgs/ImageServer/WMSServer?service=wms&request=getCapabilities&version=1.3.0";
			//const string wmsUrl = "https://geoportale.regione.lazio.it/geoserver/ows?service=wms&request=getCapabilities&version=1.3.0";
			//const string wmsUrl = "https://www.ign.es/wms-inspire/pnoa-ma?service=wms&request=getCapabilities";

			var provider = await WmsProvider.CreateAsync(wmsUrl, persistentCache: DefaultCache);
			provider.ContinueOnError = true;
			provider.TimeOut = 20000;
			provider.CRS = "EPSG:4326";

			provider.AddLayer("igm25k_lazio_wgs");
			//provider.AddLayer("geonode:ctr_5k_retiled");
			//provider.AddLayer("OI.OrthoimageCoverage");

			provider.SetImageFormat((provider.OutputFormats)[1]);
			return provider;
		}

		private void mapView_ViewPortChanged(object sender, PropertyChangedEventArgs propertyChangedEventArgs)
		{
			(double lon, double lat) mapCenter = SphericalMercator.ToLonLat(mapView.Map.Navigator.Viewport.CenterX, mapView.Map.Navigator.Viewport.CenterY);

			Device.BeginInvokeOnMainThread(() => {
				lblCoordinates.Text = mapView.Map.Navigator.Viewport.CenterY.ToString() + " " + mapView.Map.Navigator.Viewport.CenterX.ToString() + " " + GetZoom().ToString();
			});
		}

		private int GetZoom()
		{
			IReadOnlyList<double> resolutions = mapView.Map.Navigator.Resolutions;
			for (int i = 0; i <= resolutions.Count - 1; i++)
			{
				if (mapView.Map.Navigator.Viewport.Resolution >= resolutions[i])
					return i + 1;
			}
			return resolutions.Count;
		}
	}
}

`
1- Shown scale is wrong
2- Map in streched horizzontally (grid is formed by rectangle and not by square)
3- This statement mapView.Map.Navigator.Resolutions return zero length array
I downloaded the latest version 4.0.0-rc.2.
What am I doing wrong?
Thank you.

I'm not followed the whole discussion, so I might be wrong.
If you read this info, and compare it with your last code, then I fear, that you try to fit EPSG:4326 tiles in a EPSG:3857 map, which, with my understanding, doesn't work.

I know the difference between datum and projection and between EPSG.4326 and EPSG:3857.
Based on Mapsui official documentation (see below), I thought Mapsui was able to convert between these two systems.
However even if I crete the map with EPSG:4326 CRS the problem remains the same.
Supported coordinate systems (CRSes)
Out of the box Mapsui only supports the projection between two coordinate systems.

EPSG:4326 or lat/lon, or WGS84. GPS coordinates are in lat/lon
EPSG:3857 or SphericalMercator, or WebMercator, PseudoMercator. This is the coordinate system used in the maps of google and openstreetmap.

Yes, Mapsui knows both, but I could not find any conversion from one format to another. What you could do is convert coordinates from one of these projections to Mapsui and vice versa. But there isn't a conversion of raster data.

However even if the CRS of the map and the CRS of the provider are the same, there are problems about map scale and map resolutions.

My fixes are not yet in 4.0.0-rc.2. so they should be in the next rc or release.  The Resolutions property I have to investigate why this is 0 length.

I've made new tests with 4.0.0-rc.3 version.
The issue doesn't seem solved (no map was shown).
I've tryed these servers with EPSG:3857:
https://www.ign.es/wms-inspire/pnoa-ma?service=wms&request=getCapabilities
layer: OI.OrthoimageCoverage
https://wms.geo.admin.ch?service=wms&request=getCapabilities
layer: ch.swisstopo.pixelkarte-farbe
I also tried these servers with EPSG:4326:
https://sgi2.isprambiente.it/arcgis/services/raster/igm25k_lazio_wgs/ImageServer/WMSServer?service=wms&request=getCapabilities
layer: igm25k_lazio_wgs
https://geoportale.regione.lazio.it/geoserver/ows?service=wms&request=getCapabilities
layer: geonode:ctr_5k_retiled
The first seems works but:

Scale is wrong
Map is streched horizontally
Coordinates seems wrong
The zoom level cannot be determined

Is it possible to manage at least these CRS? (the most important)
EPSG:3857, EPSG:4326, CRS:84

 public async Task<Map> CreateMapAsync()
    {
        var map = new Mapsui.Map
        {
            CRS = "EPSG:3857",
        };

        // The WMS request needs a CRS
        map.Layers.Add(await CreateLayerAsync());
        return map;
    }

    public static async Task<ILayer> CreateLayerAsync()
    {
        var dataSource = new ProjectingProvider(await CreateWmsProviderAsync())
        {
            CRS = "EPSG:3857"
        };

        return new ImageLayer("mainmap")
        {
            DataSource = dataSource,
            Style = new RasterStyle()
        };
    }

    private static async Task<WmsProvider> CreateWmsProviderAsync()
    {
        const string wmsUrl = "https://sgi2.isprambiente.it/arcgis/services/raster/igm25k_lazio_wgs/ImageServer/WMSServer?service=wms&request=getCapabilities&version=1.3.0";
        var provider = await WmsProvider.CreateAsync(wmsUrl, persistentCache: DefaultCache);
        provider.ContinueOnError = true;
        provider.TimeOut = 20000;
        provider.CRS = "EPSG:4326";
        provider.AddLayer("igm25k_lazio_wgs");
        provider.SetImageFormat((provider.OutputFormats)[1]);
        return provider;
    }

This Code works (is the sample that the map displays). A Projection Provider needs to be used so that the WmsCalls are projected from EPSG:4326 to EPSG:3857 and the projection needs to be set on the map

Could be a Bug
Needs Mapsui.Extensions and the DotSpatial Projections. (Should know EPSG:6706) (Projection / Shapefile with Projection)
Does not work because this is not a Tiled Wms Layer, You have to convert the WMS To Tiled. (Data Formats/ 4 WMS called tiled)

Thank you very much.
Is it possible to speculate when the release 4 will be released?

I think this will take some time but with this link a mapsui version with the fixes can be downloaded and then with a local nuget package folder used.
<configuration>
  <config>
    <add key="globalPackagesFolder" value="C:\path\to\custom\folder" />
  </config>
</configuration>

https://github.com/Mapsui/Mapsui/suites/13681044682/artifacts/756030684

Many thanks!

Two question.

These files https://github.com/Mapsui/Mapsui/suites/13681044682/artifacts/756030684 are evergreen or where it's possible to download the latest versions?
Which is the file where i should put these tags?

<configuration>
  <config>
    <add key="local" value="C:\path\to\custom\folder" />
  </config>
</configuration>

Thank you!

you can add a nuget.config file.
with following content.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
    <add key="local-packages" value="path/to/your/local/package/folder" />
  </packageSources>
</configuration>

Ok, thank you!

Answered and fixed with https://github.com/Mapsui/Mapsui/pull/2073


Investigate using Apache Arrow (or other interchange formats)

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2616
Originally created by @tayloramurphy on 2021-03-01 12:25:03

As mentioned in https://news.ycombinator.com/item?id=26284253#26300348, it would be interesting to see how the Singer Spec could evolve to support other interchange formats such as Apache Arrow.

Supporting Apache Arrow as an interchange format (streaming Schemas and RecordBatches from tap to target) would be incredibly cool. I suspect this would allow a lot more flexibility with types and almost certainly a higher throughput. Especially as some taps and targets should be able to leverage ADBC (https://github.com/apache/arrow-adbc). Is there still interest in investigating this further?


Implement service monitoring support for java-openliberty and add timeoutSeconds for readinessProbe

Following https://github.com/appsody/appsody-operator/pull/125, the Appsody operator supports creating service monitor if there is a spec.monitoring entry in the app-deploy.yaml file. The only requirement to utilise this is a label field, like so:
apiVersion: appsody.dev/v1beta1
kind: AppsodyApplication
metadata:
  name: example-appsodyapplication
spec:
  ....
  monitoring:
    endpoints:
    - basicAuth:
        password:
          key: password
          name: pass
        username:
          key: username
          name: user
      interval: 5s
      tlsConfig:
        insecureSkipVerify: true
    labels:
      k8s-app: APPSODY_PROJECT_NAME

We introduced this functionality for Python Flask, Node.js-Express, and Node.js-functions but it would be nice to see this for the Open Liberty stack also.
Currently, we also see a Knative error if a stack uses the readinessProbe and timeoutSeconds is not defined.
Describe the solution you'd like
Add a new field (monitoring) to the app-deploy file underneath spec. The java-microprofile stack has authenticated endpoints and therefore requires a basicAuth field also.
Also add a new field, timeoutSeconds under the readinessProbe and assign it an appropriate value e.g. 1.
Additional context
Example PR to implement service monitor support into a stack: https://github.com/appsody/stacks/pull/419/files
Note: The PR above is for a stack without an authenticated endpoint, see: https://github.com/appsody/appsody-operator/pull/125 for a more suitable approach for microprofile.

Though this issue hasn't been solved in the java-microprofile stack, relabeling to the java-openliberty stack, which is where we would prioritize a solution if we decide to fix this.

Thanks @scottkurz - I've updated the issue title and description :)

@arthurdm  correct me if I'm wrong and you see a need here... but I think this is a moot point now that we've switched to the Open Liberty operator.  Closing.

I think we can resolve this issue with doc showing how to add a service monitor to the app-config.yaml. We actually show how to do this already here: https://developer.ibm.com/tutorials/configure-an-observable-microservice-with-appsody-openshift-open-liberty/
My concern with adding this to the default app-deploy.yaml is that it requires SSL to be enabled in the deployment which we are choosing not to do by default. Instead, we are adding doc in our readme on how to enable the HTTPS port and configure user credentials via ENV vars from a Secret. (#750 )
Other than the above doc, we can also add a section to our readme on how to enable a Service Monitor after SSL is enabled.


get_email Command not have EmailReplyParser in get_email.py line26

The email_reply_parser.EmailReplyParser is gone.

What version are you using? I have 0.5.9 from https://github.com/zapier/email-reply-parser and it works fine.

Thanks.  I lost the email-reply-parse package in my python lib, It's work fine when I install that package.

Ok cool! Let me know if you have any other problems, I'll close it for now.


Demo?

Please, could you give us a link where we could see a demo of this project?
Thanks.

An Example app is included in the repo, and a GIF of the same in action is in the ReadMe.


volume: add fsync threshold

Volume server count how many object has been written,
if the number of objects is bigger than threshold, sync the kernel cache.
===
给volume server加了启动参数fsyncThreshold，volume每写fsyncThreshold个对象，执行一次fsync。

this fsync is for the store, but since there are many volume files, you may need a counter for each volume file.
My original thinking is to improve API and allow the write request to do a fsync. I am still debating which approach is better.

how about adding a flush command to volume servers for a particular volume?

fsync would flush all kernel cache, so it might make no sense to flush a particular volume.

fsync would flush all kernel cache, so it might make no sense to flush a particular volume.

This commit used v.dataFile.Sync() and is volume specific.
https://golang.org/pkg/os/#File.Sync

Added https://github.com/chrislusf/seaweedfs/commit/e4af63a721f62c280596f626302b64729baeaee9 to accept fsync=true requests


Refactor/dry home

Made reusable variables in home.dart Obx. This will result in cleaner code and better performance

This is a continuation of #134. Please merge that before merging this


Background tasks check at app init

Problem
Background tasks experienced recent changes, and some side-effects may cause useless upload files to be kept locally forever or "transient" data to be forgotten.
Proposed solution
At app init time, we should re-sync the background tasks with their related temporary data.

Can you elaborate a bit about temporary data? Are you referring the local SQLite DB?

Can you elaborate a bit about temporary data? Is this something the OS of the device store?

@achintya-7 It's more like app internal logic about background tasks. If I were you I wouldn't start this one: a lot of time for understanding first all the stuff about "our" background tasks, and then coding something that nobody sees or cares about.

Typical case: #3774.


Winter Mine Entrance

@Yulife You forgot to make a texture for the mine entrance in the winter block.

Going to close this, I had a look at the winter mine in winter. Currently while the textures are nice. It doesn't look right with the overlays and the blocks. So I am thinking, I am just going to leave the winter mine for now. I will still have better loot drops in winter. And honestly, I would actually like it to have it's own theme, with some ice floors and own mobs, so when I do add it. It will be it's own dimension not the existing one. If I'm going to do it, I want to do it right. And not just reskinning the current one in winter.


Reproducible builds with docker

This PR implements reproducible builds of the inference server using Docker.
This also makes the images way lighter, which should help with user experience when downloading from dockerhub.
Docker helps a lot with reproducibility since the build environment should always be the same. Furthermore, the rust toolchain version, gcc version, SGX libs versions and rust dependencies are pinned.
Steps before merging

[x] The RUNNING.md file is supposed to replace the current instructions in README.md. We may want to move this guide into the readme itself.
[x] There are ssh id_rsa/known_hosts instructions in the dockerfile. We should remove them once the repositories are public, as ssh won't be needed anymore.
[x] I have not tested whether hardware mode is working. I don't have access to SGX hardware to test that.

Future work

[ ] CI/CD integration with automatic publish to dockerhub
[x] Building is slow: this can be solved using docker caching and cargo dependency caching. This will help with CI times too.
[x] Default (unsafe) tls keys embeded in the image, so that running locally is simpler. We may want to crash in production mode if these keys are used since they are unsafe (as they are public in the dockerhub image)

I have addressed the steps before merging, this should be ready for review.
I also have implemented cargo caching using Buildkit (which is the new version of the docker image builder) – this should help with compilation times.
You now need to build the image using:
DOCKER_BUILDKIT=1 docker build --target software -t mithrilsecuritysas/blindai-server-sim:latest . -f ./docker/build.dockerfile

All good. Will be merged today, after we reflect the changes in the documentation.


Added new badges, fixed grammary in README.md and DEVELOPER.md #hackt…

Added new badges, fixed grammary in README.md and DEVELOPER.md #hacktoberfest

Added new badges, fixed grammary in README.md and DEVELOPER.md #hacktoberfest

Dear @oleg-nenashev,
Yes. sure I understand your point concerning the needs of availability of these badges.

Dear @oleg-nenashev,
Sorry for the radio silence, I was removed unnecessary badges.
Thank you for your collaboration.

Thanks!


Update replica graph

Closes #2063

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/8e73eec2f72e5ad7f9b54c1af108c4726c045673/


Fix: Remove v6 adapted and fix scaler issues

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (a86cd4e) 84.83% compared to head (33c213f) 84.92%.
Report is 1 commits behind head on main.

Files
Patch %
Lines

bluecellulab/circuit/circuit_access.py
57.14%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #109      +/-   ##
==========================================
+ Coverage   84.83%   84.92%   +0.08%
==========================================
  Files          76       76
  Lines        5275     5272       -3
==========================================
+ Hits         4475     4477       +2
+ Misses        800      795       -5

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


Layout specification for error pages

Hi there. I want my error page to have a layout separate from the default site layout. It seems to use the default layout by default. I've tried to specify layout directly in layouts/error.vue script section, but it doesn't seem to work.

The 0.10 release it out ✋


Avalanche Subnet with Cairo VM

Description
Build a subnet using Cairo Virtual Machine.
Resources

Create a Subnet with a Custom Virtual Machine

Hello, porting CairoVM to Avalanche is a great idea. Especially with acmp77, validators who want Layer 1 CairoVMs on the Avalanche network might be motivated to stake AVAX. However, the above document is for Subnet EVM.
Avalanche has prepared an SDK called HyperSDK to accelerate the development of custom VMs like this. I believe this is currently the fastest way to accomplish this for Avalanche.
Blog: https://www.avax.network/blog/introducing-hypersdk-a-foundation-for-the-fastest-blockchains-of-the-future
Repo: https://github.com/ava-labs/hypersdk

Hello, porting CairoVM to Avalanche is a great idea. Especially with acmp77, validators who want Layer 1 CairoVMs on the Avalanche network could set up their own Layer 1 without staking AVAX. However, the above document is for Subnet EVM.
Avalanche has prepared an SDK called HyperSDK to accelerate the development of such custom VMs. I believe this is currently the fastest way to accomplish this for Avalanche.
Blog: https://www.avax.network/blog/introducing-hypersdk-a-foundation-for-the-fastest-blockchains-of-the-future Repo: https://github.com/ava-labs/hypersdk

Thank you!


Support chef-solo users databag

This change lets chef-solo to run the openvpn::users recipe, it uses the databag and data_bag and data_bag_item as a replacement for the chef-server search function.
I couldn't manually test that I didn't break the chef-server function. Would very much appreciate if other users could test it or direct me into how to test it myself.

It appears that the latest version of the cookbook supports using the chef-solo-search cookbook.
However, I'd advise users of Chef Solo who want to use data bag / search features to look into Chef Client's local mode.
https://www.chef.io/blog/2014/06/24/from-solo-to-zero-migrating-to-chef-client-local-mode/


MasterRenderer refactor

Remove unused BaseRenderer base class.
Move implementation to private implementation.

Fixed and rebased

Thanks!


Date functions missing in lovelace

Any idea why some date functions seem to be marked as missing entities?

This is happening since the last upgrade, but I have no idea where to look for this...

Are these helpers? I am seeing many helpers marked as missing in version 0.6.5 and HA Core 11.2

I've tested the latest version a bit. WM does not trigger for occurrences like this:
parseInt((Date.now() - Date.parse(x)) / 3600000);
However, if you create a variable named date and use it as date.something, WM will consider it as a date entity.
If this is your case, the solution could be to rename the variable so that it differs from "date".

seeing a related issue on event
can this be added here, on would you require a separate issue tracker for it.
Ive renamed variables to non reserved words for some of the events, but there is an actual event that is still triggering the Watchman logic

@Mariusthvdb  It seems that event should be removed from parsing as they cannot have persistent states

Fix is available in 0.7.0 beta, can be downloaded via HACS.

Yep, date was added as a platform in recent version along with a few helpers. @h3llrais3r @jhemak could you provide a snippet of Lovelace code which triggers WM? Thanks in advance.
As a temporary workaround date can be added to ignored items in WM config.

So it's probably coming from this part?
If I rename the variable, it should also be fixed, right?
PS: Thanks for the fix anyway!

Reopen the issue to increase its visibility to users.


Chef Infra Server WebUI Key

:nut_and_bolt: Description: What code changed, and why?
A section has been added to add the WebUI Key to the Chef Infra Server Documentation.
:chains: Related Resources
Jira Issue Link: #STALWART-77
:white_check_mark: Checklist
All PRs must tick these:

[x] I have read the CONTRIBUTING document.
[x] All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

[x] Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
[x] Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
[x] Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
[x] Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
[x] Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

The object screenshots need to replaced since there are changes made to the server details section


Nuxt Compatibilty 4 Glob error

Hi,
Hope you well.
Been getting this on all Nuxt 4 builds. Any clues?
#15 149.6 PWA v0.21.0
#15 149.6 mode      generateSW
#15 149.6 precache  3 entries (0.21 KiB)
#15 149.6 files generated
#15 149.6   ../.output/public/sw.js
#15 149.6   ../.output/public/workbox-4723e66c.js
#15 149.6 warnings
#15 149.6   One of the glob patterns doesn't match any files. Please remove or fix the following: {
#15 149.6   "globDirectory": "/app/.output/public",
#15 149.6   "globPattern": "**/_payload.json",
#15 149.6   "globIgnores": [
#15 149.6     "**/node_modules/**/*",
#15 149.6     "sw.js",
#15 149.6     "workbox-*.js"
#15 149.6   ]
#15 149.6 }

what's your pwa configuration?


hyperion switch not working

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.25.0
Python release (python3 --version):
python3.4
Component/platform:
hyperion
Description of problem:
switch.hyperion do not work anymore
Expected:
switch working
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):
http://hastebin.com/igekomunec.vhdl
Additional info:
: CC @schneefux

You need to update to a version that includes this patch, which was merged 19 days ago.


Testing should be opt in

Now that there appears to be a class of Integrators who will be using libspdm as a real library and who don't care about running its unit and fuzz testing (for example https://github.com/altera-opensource/verifier), we should make testing opt in when CMake is invoked; ie -DTEST=On.

we can make it default off.
we need add to readme.
we need check CI.


wait-for-services script

closes #44
Also factors out all sleep calls, and their attendant race conditions.
I tried adding a symlink to false as /etc/service/cron/check, and the test correctly failed.

@phusion ?

I've proposed a couple patches to sv-check behavior that reduces the wait-for-services script to simply sv check /etc/service/* again. I'm not entirely hopeful that they will be merged though.
I've started upstream discusion here:

<EMAIL_ADDRESS><EMAIL_ADDRESS>

Sorry, I haven't had time to look at this yet. I'm pretty preoccupied with other projects. But I promise you I will look at it eventually.

Thanks Hongli!
No worries.
--phone is hard.
On Feb 10, 2015 12:06 PM, "Hongli Lai"<EMAIL_ADDRESS>wrote:

Sorry, I haven't had time to look at this yet. I'm pretty preoccupied with
other projects. But I promise you I will look at it eventually.
—
Reply to this email directly or view it on GitHub
https://github.com/phusion/baseimage-docker/pull/192#issuecomment-73773362
.

@bukzor This PR has merge conflicts, please resolve those conflicts and let me know so I can merge your changes in! :)

Full disclosure: I don't plan to spend time on this.
On Sun, Mar 19, 2017 at 12:42 AM Travis Rowland<EMAIL_ADDRESS>wrote:

@Theaxiom requested changes on this pull request.
@bukzor https://github.com/bukzor This PR has merge conflicts, please
resolve those conflicts and let me know so I can merge your changes in! :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phusion/baseimage-docker/pull/192#pullrequestreview-27741978,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAnFSITnRAjbjftf9gfrODubRTG7ytACks5rnNx_gaJpZM4Db0jR
.

@bukzor Thank you for letting me know, I will see what I can do regarding your PR. I am trying to get as much of these PR's and Issues resolved as I can. :)

Can you explain what did you originally wanted to achieve here? What do you mean by "wait for services"? Wait for all services to be started and up? Or wait for a specific service to be running?
What makes it even more tricky is that some services need some proper time to actually initialise even after being "up".
For example, the only proper way to check if PostgreSQL is actually running properly is something like this (100% custom for PostgreSQL):
until su - postgres -c '/usr/lib/postgresql/9.5/bin/pg_ctl status -D /data/pgsql/9.5' | grep 'pg_ctl: server is running '
do
    echo
    echo "....waiting for PostgreSQL to start"
    sleep 1
done
sleep 3
echo "PostgreSQL started"


Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:
https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/hombach/ioBroker.go-e-charger

[ ] [E301] Tests on Travis-ci.org are broken. Please fix.

I have also found warnings that may be fixed if possible.

[ ] [W400] Cannot find "go-e-charger" in latest repository

Thanks,
your automatic adapter checker.
P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Thanks, that all bugs have been fixed.

Thanks, that all bugs have been fixed.


Collection does not watch/recreate the pipeline documents

When a Collection is created, the manifests are retrieved from the archive and deployed, but are not watched. Deletion of an individual object of the Collection will not be recreated until the controller is restarted.
https://github.com/kabanero-io/kabanero-operator/blob/master/pkg/controller/collection/collection_controller.go#L619
Related
https://github.com/kabanero-io/kabanero-operator/issues/99

closing, delivered and merged


Add ability to inject schema registry client in encoder and decoder

Injecting the client will make testing easier with mocked clients

Anyone interested in reviewing/approving?


test_retention: Quick fix for the remaining test failure.

test_cross_realm_messages_archiving_two_realm_expired doesn't run the
code path patched in commit 3d1aa98b2ea344fba7fbb2373a37d4cf30f53e08i,
so it can still fail. We apply the analogical change in the test as
the cited commit.

CircleCI refuses to run tests when I push commits anymore :(


Refactor get changes

Hi,
This is a medium refactor for remove the double call to the atomic operation for get wal changes, the last commit is the one with more changes but that is just a code cleanup, all the required logic is on the first two commits, I haven't seen a big performance change but i think it still make sense merge it.
another thing, for make the refactor work i had to change this assert: 379257b#diff-4da6f88c14ce4d0fafc152774eeb7508L195 but it may hide a bigger problem, not due to the refactor, it seems that in some cases we lock an release in a not a balanced way, or is better say we load and lock the same page twice doing: lock,lock,release,release causing that assert to fail, this shouldn't be an issue because it happen only for new pages, that exist only in the current thread local, so no concurrency issues, but i would keep an aye on this.
all the rest should be strait forward, let me know if this make sense for you.

Thank you for patch :-)


Add missing state and error wrappers

Remove some unnecessary pylint exceptions
Add a missing UNKNOWN EV charger component state
Return UNKNOWN instead of UNSPECIFIED for unknown states
Wrap missing component errors
Wrap missing component states
Unify the style with the new wrappers
Update release notes
Prepare release notes for the v0.4.0 release

I will release v0.4.0 after this is merged.

Enabled auto-merge.

To speed up things I accepted the suggestion to improve the wording for the UNKNOWN estates and added a from_pb method to ErrorLevel. I disabled auto-merge because I need to squash the fixup once I get a LGTM.

Actually I'm leaving the auto-merge enabled. Since the fixup commit is not signed-of-by, the automerge won't happen until I squash the commits, so if I get an approval I can squash, force-push and the PR will be queued if the resulting diff doesn't change, so it won't require a second approval after the squashing.

Fixes look good to me,  can approve once squashed.

You can have another look if you want, but the only that could be messed up is the split of the commits, as long as the resulting diff is the same, the approval still stands.


Add gax support for entity annotations.

Towards #2753
This adds support for EntityAnnotation types of detection.
Face, Safe Search and Image Properties is what's left.
Also, system tests have use_gax set for detection types that don't yet have from_pb defined.

@dhermes I updated the system tests and I think I addressed most of your feedback.
LMKWYT

Re:

But len(images) > 1 is an error. I realize it returns None, I'm saying that we should be more defensive / have clearer assumptions.

How about this?
if len(images) == 1:
    return Annotations.from_api_repr(images[0])
elif len(images) > 1:
    raise ValueError('Multiple image processing is not yet supported.')

Squashed with NotImplementedError update.

Travis is green, merging.


Creation of unintentional, buggy regions

Bug description:
Hi all, I have encountered a problem while working with this library which I believe might be a bug. While creating regions, there seems to be an issue with creation of regions that can be called rogue. I am attaching a video of how the unintended behaviour occurs. You can view the ID of the region that is being clicked on in the console on the right side.
https://github.com/katspaugh/wavesurfer.js/assets/66988314/43b5deef-376b-45a5-8f71-4ff8ef7fafb1
You can see how the regions break into two while creating them. I have used a region-click event to check the region.id of the regions so created. When a region breaks into two, the first half of the region does not seem to have an ID which makes removal of that region impossible unless I restart the program (by refreshing the webpage).
You can see how I click on Clear All Regions at the end but somehow, those rogue regions do not seem to go away. Even when I click on those regions to view their ID, nothing appears in the console.
Environment:

Browser: Chrome
Version: v7.7.9, imported from: import WaveSurfer from<EMAIL_ADDRESS>
Minimal code snippet:
Regions get created by dragging:
wsRegions.enableDragSelection({
    color: 'rgba(0,120,0,0.3)',
});

Region click code:
wsRegions.on('region-clicked', (region) => {
    console.log(region.id);
});

Clearing all regions code:
function clearAllMaps(){
    wsRegions.clearRegions();
}

Expected result:
Regions shouldn't be breaking into two for intended use.
Obtained result:
Region created split into two.
PS: Do let me know if I can make any clarifications, it's my first time opening an issue on GitHub. Thank you!

I wasn't able to reproduce this in Chrome (mac/touchpad) in this example: https://wavesurfer.xyz/examples/?regions.js
Is there any additional code that you added that might affect it? Can you make a reproducible example on codepen?

hey @katspaugh. I have around 800 lines of code that I have used to create an entire application using the library. Could it be that I am trying to overwork the regions plugin? This issue is not reproducible all the time btw. Not sure why this is occuring, because I've started to face this issue only a few days ago and I have not made any changes to the code. Please let me know what I can do to further clarify the issue?

A few days ago there was a refactoring of the draggable function, so it may well be a regression. The problem is I don't know how to reproduce it.
Could you try going back to v7.7.6 and seeing if the bug goes away?

i just tried all versions of 7.7.x, and the bug is replicable in every version.

Is your app available on some URL?

noo i have not deployed it yet :/

I was able to reproduce the bug on https://wavesurfer.xyz/examples/?regions.js   when I try to create several regions quickly (I've just removed the code that generates the predefined regions)
I'm on Ubuntu using Chrome with a mouse.
https://github.com/katspaugh/wavesurfer.js/assets/32324822/9dd98044-e418-4bc1-9d40-44abcb41ec41

@VaysseRobin @ManimMadhav can you reproduce it with this example? https://wavesurfer.xyz/examples/?064352f48990781f8e5328ed18f4301b (wavesurfer version prior to the draggable refactoring)

No @katspaugh , I can't reproduce the error here in the link you have provided.
However, I can reproduce the error in the link @VaysseRobin shared earlier.

I can't reproduce it either in this older version.

Good, thank you both! I'll revert the refactoring then.

I can reproduce this error in my code though, while using version 7.7.6.

I have the same problem. (Ubuntu + chrome v123 + mouse)
I removed package-lock.json, node_modules, and set "wavesurfer.js": "7.7.6".
Run npm i, and the problem's gone.

Thanks for confirming @leyiang, I’ll revert the commit that caused this.

Could you guys try on this branch? https://revert-draggable.wavesurfer-js.pages.dev/#regions.js

Could you guys try on this branch? https://revert-draggable.wavesurfer-js.pages.dev/#regions.js

I tried it, and there were no issues. (at least for me)

I've published v7.7.11 with a fix.

uhh when will this version be available on unpkg.com?

Unpkg seems to have been having issues lately, you migth want to switch to some other CDN (there are some suggestions in https://github.com/katspaugh/wavesurfer.js/issues/3650).

have they not yet been updated with v7.7.11?
all of them still show the latest version as v7.7.10 for me.

My bad, the package wasn’t published properly. I’ve just published 7.7.11 for real.

thank you so much for this speedy fix @katspaugh!
it works great now :)


NT, KX, and MV Edits: Chapter 10

[ ] Add summary to chapter title, e.g. "Summary: Doing Distributed Data Science"
[ ] Create Parts, e.g. "Part 1: Lower-level tools: Cluster use and interaction with Python, MapReduce, and Spark" and "Part 2: Higher-level tools: Data mining, data ingestion, data flows, and machine learning."
[ ] Review major headers: Data Product Life Cycle, Machine Learning [or even Machine Learning Life Cycle?], and Conclusion
[ ] Clarify data product vs. data-driven app as a note, see: comment to reviewer.
[ ] Glossary
[ ] Shout out to Kostas and Marck as tech reviewers and remove blurb about early release in preface.
[ ] Check that figures list is up to date.

From Nicole:
Following up about the proper way to add Parts to Atlas. You may add Parts as separate files, and then organize the files in the Build list accordingly. You can put this in the separate AsciiDoc file for each Part:
[[unique_ID_goes_here]]
[part]
== part_title_goes_here

[partintro]
--

<Any introductory Part paragraphs go here.>

From Nicole:
Quick note on my comment regarding the logos in Fig. 10-4. Since these all appear to be logos for the open-source Apache products, I'm not too worried about their use in the figure (although please double check that they're all for Apache versions). It's when we get into company logos that we really want to avoid them.

[ ] NT edits
[ ] KX edits
[ ] MV edits

TOC:

Summary: Doing Distributed Data Science

Data Product Life Cycle

Data Lakes
Data Ingestion
Computational Data Stores

Relational Approaches: Hive
NoSQL Approaches: HBase

Machine Learning Life Cycle
Conclusion

Didn't see any comments in the MV PDF


3.2.7 tagged logging issue

Tried to do the patch upgrade from 3.2.6 to 3.2.7 and got an exception TypeError (no implicit conversion of Hash into String): in vendor/bundle/ruby/3.2.0/gems/activesupport-7.0.8/lib/active_support/tagged_logging.rb:32. Not really sure why it was getting it, but when I went back to the previous version of dalli (3.2.6, without the base64 dependency) the error went away. We are using memcached for our Rack::Attack configuration, and not for regular caching. (don't ask). If there is some other question, I can try to answer it.

@nroose Please see the discussion in #987


[Improvement] Add List and Map types to table/columns in Gravitino CLI

What would you like to be improved?
Add these types with datatype specifiers:

List(datatype)
Map(datatype,datatype)

How should we improve?
No response

@justinmclean  I’m interested in taking this on. I just have a couple of questions for clarification:

Could you explain how lists and maps are associated with length specifiers? 👀
Do we need to support nested types for lists (and map)?

I mistyped that, sorry. They are similar to a datatype with a length specifier but specify the datatype instead.
I wouldn't worry about nested types and handle that in another issue/PR.


Fix: Support null case in extractObjects

This allows null fields to be passed through the SDK

This change is

:tada: This PR is included in version 1.5.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


secrets in url / db uri

what do you think of having url / uri keywords added to masked_secrets as they often contains passwords for redis, postgresql etc or maybe have an option to not display some added keywords

I will replace password component of URLs with stars.
Custom keyword is a good idea too, for later ;)

let me know if it works for you

let me know if it works for you

yep, thats cool now in env var
redis://:********@backend_redis:6379


Add "on_error_resume_next" operator.

@victimsnino The office ReactiveX doc names the operator catch(), and RxCpp names it on_error_resume_next(). Shall we just use catch() for consistent naming with the doc?

@victimsnino The office ReactiveX doc names the operator catch(), and RxCpp names it on_error_resume_next(). Shall we just use catch() for consistent naming with the doc?

I offer to provide aliases for both ways to follow ReactiveX and RxCpp and the same time

I see. That makes sense. Let's keep using on_error_resume_next() though.


PieChart not rendering

Hey guys,
Firstly thanks for this work. Much appreciated.
I easily managed to display a Line chart without any issue. However within the same project I am trying to display a Pie chart but the canvas comes out empty when using css to set the width and height of the canvas it self.
import React from 'react';
const PieChart = require("react-chartjs").Pie;

class Example extends React.Component {
    constructor() {
        super();
    }

    render() {
        let data = [
            {color: "blue", label: "test1", value: 1},
            {color: "red", label: "test2", value: 2}
        ];

        return (
            <PieChart data={data} options={{animateRotate: true}}/>
        )
    }
}

export default Example;

The css:
canvas{
    width: 100% !important;
    height: auto !important;
}

The html generated:
<canvas height="300" width="600" style="width: 300px; height: 150px;"></canvas>

Am I doing something wrong or is there something to fix?
Cheers!

If i may make a suggestion .. If you want your chart to be of a particular size.. why don't you wrap it inside a div. Give some dimension to the div and render the chart with responsive property as true

@pankaj805 thanks for the hint. The css trick I've tried works fine for a LineChart hence my question. Anyway I ended up moving to plain Chart.js without this wrapper.
Thanks!

I have the same issue. I can successfully render a Line and Bar Chart, but I can't manage to display a Doughnut Chart.. code is exactly the same, and I don't get any error in console.
import React from 'react';
import { Doughnut } from 'react-chartjs';

export class DoughnutChart extends React.Component {

    render() {

        const data = {
            labels: [
                "Red",
                "Blue",
                "Yellow"
            ],
            datasets: [
                {
                    data: [300, 50, 100],
                    backgroundColor: [
                        "#FF6384",
                        "#36A2EB",
                        "#FFCE56"
                    ],
                    hoverBackgroundColor: [
                        "#FF6384",
                        "#36A2EB",
                        "#FFCE56"
                    ]
                }]
        };

        const options = {
            animation: {
                animateScale: true
            }
        };

        return <Doughnut data={data} options={options} width="600" height="250"/>
    }
}

any clue?

Switched to https://github.com/gor181/react-chartjs-2 that works like a charm with chartjs 2.4+


Changes to Developer Guides final day

Add list section, manual test cases for list and summarise for DG.
Remove Import section in UG as we are not using it anymore.
Update aboutus page to reflect our roles.

Codecov Report

Merging #294 (a782546) into master (876eab3) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #294   +/-   ##
=========================================
  Coverage     65.77%   65.77%
  Complexity      590      590
=========================================
  Files            90       90
  Lines          2092     2092
  Branches        244      244
=========================================
  Hits           1376     1376
  Misses          647      647
  Partials         69       69

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Error: Can't set headers after they are sent.

I put the error log here, since it is a little bit long
http://pastie.org/10945816
The reproduce codes app is here
https://github.com/Hongbo-Miao/zonejs-bug
It uses universal-starter, just added socket.io, see in second commit.
To see the error, npm start and open page http://localhost:3000/.
The app works with zone.js 0.6.21, and it shows the error starts from 0.6.22 and also shows in latest 0.6.26

I made a pull request to fix this issue, for now you can change your package.json to make zone.js reference to https://github.com/JiaLiPassion/zone.js.git to see the result.

This still occurs in 0.8.20.
I can't believe how old this issue is :)
My scenario, I have an SSR Response Service:
import { Injectable, Inject } from '@angular/core';

import { Response } from 'express';
import { RESPONSE } from '@nguniversal/express-engine';

@Injectable()
export class SsrResponseService {
  constructor(@Inject(RESPONSE) private response: Response) {}

  redirect(url: string, code?: number) {
    if (!!code) {
      return this.response.redirect(code, url);
    } else {
      return this.response.redirect(url);
    }
  }
}

Then, in a component, based on some logic, I might need to redirect the user:
this.responseService.redirect('/some-other-url', 301);

The redirect works, but the server logs:
Unhandled Promise rejection: Can't set headers after they are sent. ;
Zone: <root> ; Task: Promise.then ; Value: Error: Can't set headers after they are sent.

Full stack trace here
Any ETA on this fix?

Bump - same here

@mike-suggitt , @MrCroft , I don't think the Can't set headers after they are sent is zone.js error, it is just express http response error.

@MrCroft , sorry I am not familiar with SSR, you can ask at stackoverflow.

@JiaLiPassion actually, I remember that the headers were in fact being set. And the app worked fine. But I was just seeing that error in the log and it mentioned zone.js. Weird... Haven't been doing SSR recently.

@MrCroft, yeah, almost all the errors in angular will mention zone.js, so really very little error is really zone.js error.


Internal JavaScript [Class] of item [Example]

@camsong  I hope now its fine 😄

Close for now, please open a new PR if you are ready


MAINT: pybind11 win exclusion

Fixes #17644 (see detailed analysis over there..)

I confirmed locally that cibuildwheel --platform windows passes with pybind11 2.10.2 excluded, whereas we currently experience a segfault that is blocking the release process on Windows

I suspect we may be able to restrict the exclusion to Windows only in pyproject.toml, but I think I'm inclined to just keep the syntax simple there if folks are "ok" with this? This also assumes that pybind11 team agrees this is a bug on their end and that the next bug fix release will deal with the issue. I'll open an issue over there shortly.

this should also stop our Windows meson job from segfaulting for the same reason

I opened an upstream issue here: https://github.com/pybind/pybind11/issues/4420
Unfortunately I don't think I'll have the bandwidth to excise a minimum viable reproducer outside of SciPy for them, but hopefully this is more obvious for the pybind11 team.

CI is all green for the first time in a bit I think. I'll leave this open for at least a few hours given the time of year I think, there's no harm in releasing RC2 on Monday or Tuesday anyway.

Sorry if I missed it - but do we know why that version of pybind11 caused a problem?

@matthew-brett see https://github.com/scipy/scipy/issues/17644#issuecomment-1364537985. I don't understand what's wrong with that PR identified there, that would require actual debugging. Our pypocketfft code hasn't changed in a long time, and we've never had an issue with it before as far as I can remember.

Thanks for pointing that out - I had missed it - cross-referencing Tyler's Pybind issue here (as well as in the original issue):
https://github.com/pybind/pybind11/issues/4420


Add spanish translation for Native Descriptor Wallets-Andrew Chow

@BlueeeMoon can you branch off of master when adding new transcripts please? This is the incorrect commit history.


Add regex matching feature for restricted and default servers

Great work. Looks good, apologies for taking awhile to review.


Force pushes/rebases do not cancel ongoing builds

I've been encountering a pretty awful problem over the past few months. If PRs are rebased or force push'd to while a build is ongoing, the existing (and now out of date) job will continue to build. If several changes are force pushed in quick succession, you'll end up with a long build queue of builds which are going nowhere (this gets more painful if builds are long).
I wondered if anyone had any thoughts on a way to fix this? I'd guess ghprb would need to get notified of the force push somehow via hook to cancel existing builds for a PR, but I'm not sure such a hook exists.

I've not tried yet, but maybe this could help : http://blog.vincentpau.com/2012/08/02/cancel-obsolete-jenkins-queued-builds/

This actually works for us, you just have to add the Cancel build on update Trigger to the GH PR Builder configuration:

thx @MSch this works great! I don't know if it was recently added or if I missed it before but I think this issue can be closed.
@jasonmadigan can you confirm it works for you too ?

@MSch @mathroc excellent, I didn't know this existed!


.Net Core 3.1 version?

Hi, yes I know I can send SQL down through ExecuteSQLCommand. Your library is better, obviously. The source should compile with a change to .Net Standard 2.1 to be usable with core 3.1.
This is the price of doing something well: People want to continue using it!
Let me know if this is in the works, and thanks!

Hello, this library targets .NET Standard 2.1, you should be able to reference it from a .NET Core 3.1 project.

Am I missing something? Via Nuget.org, and Manage Nuget Packages in visual studio, I see 1.0.2, which lists as dependencies, .Net Standard 2.0. I also have pre-release checked to make sure I'm not missing a beta package. Pic link attached. Thanks in advance!
imgur link to pics

Sorry it targets .NET Standard 2.0 😅 but it can still be referenced from a .NET Core 3.1 library.

Thank you.


feat(ci): Add publish workflow to Github.

Followed this guide https://medium.com/@blackary/publishing-a-python-package-from-github-to-pypi-in-2024-a6fb8635d45d


Allow parameters to be defined only by schema references

This should allow for larger schemas to be defined in a more compact fashion - please see the swagger_helper and integration spec changes in the test-app.

I also made sure the new swagger.json validates OK. It does!

It'd be nice if there was a CONTRIBUTING.md that articulates how to run tests.

Can't remember when/how this was added but looks like this functionality is already available. Please checkout 1.5.0 and let me know

This does not appear to be working in 1.50 (sorry for the long delay on this).
...
path "/api/v3/addons/{uuid}" do
  let(:uuid) { addon.uuid }
  get "Get an add-on" do
    parameter(
      "$ref" => "parameters/uuid_path_param"
    )
...

yields the following error message:
2) V3 Addons API /api/v3/addons/{uuid} get Get an add-on by uuid. Herokai can see all add-ons. returns a 200 response
     Failure/Error: raise "Referenced parameter '#{ref}' must be defined" unless definitions && definitions[key]

     RuntimeError:
       Referenced parameter 'parameters/uuid_path_param' must be defined

This would be a useful feature and is supported by the swagger spec. Shall I rebase against 1.5.0 and re-issue or am I missing something?

How are you defining your referenced parameter in swagger_helper.rb? If you use a string instead of a symbol as the key, it will likely work. If you could confirm this, it would be very helpful?
parameters: {
  'uuid_path_param' => { ... }
}

Of course this is inconsistent with the other global metadata in swagger_helper and so I think it would be better to expect a symbol. So, I've updated the code in master. If you can confirm the above works, then I'll go ahead and publish the updated version so you can revert to the symbol approach.


Some warnings about typescript?

Hi, volkanceylan , Nice to see you again !

I use the 1.8 version typeScript when I created the project , Now I update my typeScript to 2.1 ，There have some warnings like the picture .  How can I sovle it ?

did you use the  upgrade checklist on #1342 ?

These are not warnings but hints from tslint. Create a tslint.json with braces, e.g. {}

I create a tslint.json in my proj , it works well !  No more hints ,    Thanks a lot !  Hope serenity more powerful !


China Wrong flag

Hong Kong, Macao and Taiwan are not part of the country, they are all part of Chinese territory.Hong Kong and Macau have returned to China,Now only Taiwan has not returned to China. But Taiwan is not a country, he is only part of Chinese territory.Please ask the person in charge to verify the situation and correct it.

I'm Chinese and I'll root for you if you submit a PR instead of complains. The community needs sth better than non-tech BS.

so I'm short.. what needs to be done?

@lipis Thanks for your attention!
In terms of Country Code (3 digit iso, 2 digit iso), everything is ok here.
For Hong Kong, Macao and Taiwan, they need to be separated from 'Countries'. There're 2 ways to do so in general, 1) use "Countries / Regions" instead of lone "Counties" as title wherever it appears. 2) append China in their names e.g. HongKong(China/PRC), Taiwan(ROC)
These are not an exact science and above is only my suggestion. Doing so is required for legit business in China (mainland basically).
Since it is an open source icon lib, I couldn't care less about these wordings, and I suggest you don't take it too seriously. Because there is no "fix" in this, especially for TW.

so in short.. what needs to be done?

@lipis Thank you for your attention
As @noru said, this is a solution. Thank you.

There are other non-country entities, like Puerto Rico(notice Independent is No), which is part of US.
In additional to @noru 's point 2, one reference for the names is the ISO 3166 above. For example, TW's short name is "Taiwan (Province of China)". However I don't find the country names shown on the project website in this repo, so I'm not sure how to create PR for those.
For point 1 (use "Countries / Regions"), how about creating a PR to change the README and index.html to start with?

@anton-bot
Don't flatter yourself, even there're people like you providing a good reason for such "campaign", they have better places other than here to spend their money.
"Political Reasons" is certainly a not welcoming thing in the community.

It's not about politics or any sides, yet it's about the matter of facts.
Some of them, including, but not limited to, Hong Kong, Macao, and Taiwan are not existing as countries in any aspect right now.
It is very true that the community does not need political bullshit. Also, legitimacy and logic are what we are pursuing here.

@anton-bot Sarcasm is very unnecessary. Thank you though.

@edwardfhsiao Not sure why I didn't create PR for the last part in my comment:

For point 1 (use "Countries / Regions"), how about creating a PR to change the README and index.html to start with?

Would you like to take over?

@anton-bot You don't even understand what I'm trying to say here. If one day, Honghong independent from the People's Republic of China, Taiwan independent from the Republic of China, then the title of "Countries" is legitimate. Being used here at the moment is just wrong.
Don't overthink, my statement is just about facts, not radical nationalism.

Hi, @lipis  @anton-bot
The terms of "Country" includes "Regions or Areas" just does not sound professional to me. That's my intention.
I'm not trying to imply any political issues whatsoever.


Fix table with null values

Is the 2nd "Report Title" is part of the pageHeader band, and we are on a new page :-)


Project Idea: HyperLogLog

For those still looking for a (team) project idea, HyperLogLog is an interesting probabilistic data structure that is worth studying.
https://chengweihu.com/hyperloglog/
It would benefit from a large dataset in an "online" setting, that is, live data with new datapoints arriving daily in real-time, a large historical dataset that would be expensive to re-run.
Examples:

a web crawl of something too specialized for google, like

"videos of people playing Minecraft"
photos of a large geographical feature like the Grand Canyon
anything that you might think would be useful for a specialized AI training set

ticket sales or visitor stats of a local museum or library

these are the most interesting datasets and require going outside of class to talk to the staffs
publicly-funded institutions which are paid by tax dollars and with a social good mission might be more amenable to collaborating with students on a school project

Your project will be to relate HyperLogLog to the introductory concepts we are learning in DSA, as well as code up an implementation in a programming language of your choice, run it on any dataset you choose, measure its performance and suitability, critique your implementation, and suggest opportunities for improvement.

A good explanation video
https://www.youtube.com/watch?v=lJYufx0bfpw&pp=ygUSZ29vZ2xlIGh5cGVybG9nbG9n

Doing your own web crawls for large datasets
https://commoncrawl.org/


curlconverter by default consider server root path for 'tree-sitter-bash.wasm' file

Dear Team,
Is there any way I could customize the path? Rather than considering the server root path (i.e http://<IP_ADDRESS>:8000/tree-sitter-bash.wasm) for 'tree-sitter-bash.wasm file, is there any possibility that I can specify my customized path? The thing is I don't want to serve that file from the server root path.

There is no way currently, you would have to fork the repo and change these two lines
https://github.com/curlconverter/curlconverter/blob/112ae7a14f32d84464712d302bb060b927687181/src/shell/webParser.ts#L7-L8
to something like
await Parser.init({
  locateFile(scriptName: string, scriptDirectory: string) {
    return '/some/other/path/tree-sitter.wasm';
  },
});
const Bash = await Parser.Language.load("/some/other/path/tree-sitter-bash.wasm");

The reason a way to pass these file names hasn't been implemented is so the normal usecase is simpler, you can just do
import * as curlconverter from 'curlconverter';

curlconverter.toPython('curl example.com');

instead of having to do
import * as curlconverterInit from 'curlconverter';

const curlconverter = curlconverterInit();

curlconverter.toPython('curl example.com');

and there's as little distinction between the native version of the library and the WASM version of the library, the only difference is just this line in package.json
https://github.com/curlconverter/curlconverter/blob/112ae7a14f32d84464712d302bb060b927687181/package.json#L80-L82

hi @verhovsky,
can you please tell me how much time will it take to get these changes reflected in the npm package. When do you plan to release these changes.
Thank You

I'm bumping an old issue here, but the way this is at the moment, it works fine if your website lives at the root of your domain (e.g: https://curlconverter.com ) but if your website lives in a subdirectory (e.g: https://username.github.io/my-static-site ) the library tries to load tree-sitter-bash.wasm from
https://username.github.io/tree-sitter-bash.wasm instead of
https://username.github.io/my-static-site/tree-sitter-bash.wasm
This makes it impossible to use the library in a site that is deployed to a subdirectory.
The other thing I noticed trying to use this in a browser is that although the docs say tree-sitter.wasm is also loaded from the root, that one seems to actually be loaded relative to the js file that tries to load it. So if my js bundle is https://username.github.io/my-static-site/js/app.js then tree-sitter.wasm will be loaded from https://username.github.io/my-static-site/js/tree-sitter.wasm
It would be useful if those two worked the same way, but the inconsistency is less of an issue.

#664, released as 4.10.1 made it consistent.