Spring clean 🌼

There are many CCISS-related and CCISS-tangential repos out there. We need to delete those that are no longer relevant and potentially centralize those that are (e.g. as git submodules to bcgov/CISS
List of repos to check

[x] bcgov/Build_WNA_BGC_model - checked and added as submodule to bcgov/CCISS
[x] whmacken/Build_USA_BEC - checked and added as submodule to bcgov/CCISS
[x] kdaust/BC_HexGrid - checked and added as submodule to bcgov/CCISS
[x] whmacken/CCISS_Portfolio_Dataset_Alignment - checked and added as submodule to bcgov/CCISS
[x] whmacken/CCISS_Reporter - checked and added as submodule to bcgov/CCISS
[x] bcgov/CCISS_spatial - see https://github.com/bcgov/CCISS/issues/23#issuecomment-2070879254
[x] bcgov/CCISS_ShinyApp - see https://github.com/bcgov/CCISS/issues/23#issuecomment-2070879254
[x] bcgov/ccsummary-cciss - see https://github.com/bcgov/CCISS/issues/23#issuecomment-2070879254

@whmacken and @kdaust please add other repos that need to be checked to the list above

Please note that the following repos have all been re-created in bcgov and can be deleted.

FLNRO-Smithers-Research/Build_WNA_BGC_model
whmacken/Build_USA_BEC
kdaust/BC_HexGrid
whmacken/CCISS_Portfolio_Dataset_Alignment
whmacken/CCISS_Reporter

@whmacken can you please delete the repos above ☝ ?

bcgov/CCISS_spatial - is/was an attempt at interacting with and processing CCISS maps on the fly from the database
bcgov/ccsummary-cciss - is an obsolete repo that can be deleted.
bcgov/CCISS_ShinyApp - currently has two apps in it that will need to be separated into two independent Shiny App repos.

Other repos that may be involved in CCISS workflow(s) and need to be checked for relevance and whether they need to be moved to bcgov or deleted.

[ ] https://github.com/kdaust/EdatopicReview - potentially related to CCISS
[ ] https://github.com/whmacken/aSMR_X_rSMR
[ ] https://github.com/whmacken/SIBEC_Modelled - very much under development, potentially related to CCISS
[ ] https://github.com/whmacken/CCISS_Webtool - old app; can be deleted
[ ] https://github.com/FLNRO-Smithers-Research/BGC-Climate-Summaries - probably old.
[ ] https://github.com/FLNRO-Smithers-Research/PortfolioKiri
[ ] https://github.com/FLNRO-Smithers-Research/BGC_Climates_Shiny - pulled into a tab of ByBEC
[ ] https://github.com/FLNRO-Smithers-Research/BigBECmodel
[ ] https://github.com/FLNRO-Smithers-Research/ByBecApp - old (can be deleted) moved to https://github.com/bcgov/byBEC_shiny
[ ] https://github.com/bcgov/byBEC_shiny
[ ] https://github.com/FLNRO-Smithers-Research/Feasibility_RasterMaps - potentially involved/relevant? Might have been superceeded by more current code.

As preparation for our next sprint, checking with @whmacken, @cmahony and @kdaust if this issue has been fully dealt with and can be closed :)


&str and &[u8] should implement IntoAsciiString

Just like &str implements Into<String>.
This would involve copying the string, but would allow writing APIs as:
fn foo<S: IntoAsciiString>(s: S) {
    let s = s.into_ascii_string();
    ....
}

etc, and have those work seamlessly with string and bytestring literals.

Thanks!


New-SSHRemotePortForward not portforwarding

I saw a old issue which has not been responded to so have created a new one, when calling New-SSHRemotePortForward it throws a error
New-SSHRemotePortForward -LocalAdress <IP_ADDRESS> -LocalPort 1337 -RemoteAddress <IP_ADDRESS> -RemotePort 3389 -Index 0
Throws error
Write-Verbose : Cannot bind argument to parameter 'Message' because it is null.
At C:\Program Files\WindowsPowerShell\Modules\Posh-SSH\2.2\Posh-SSH.psm1:2704 char:31
+                 Write-Verbose $session.index
+                               ~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Write-Verbose], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.WriteVerboseCommand
`New-SSHRemotePortForward -LocalAdress <IP_ADDRESS> -LocalPort 1337 -RemoteAddress <IP_ADDRESS> -RemotePort 3389 -sshSession $CurrentSession

Throws error
Exception calling "Start" with "0" argument(s): "Port forwarding for '<IP_ADDRESS>' port '3389' failed to start."
At C:\Program Files\WindowsPowerShell\Modules\Posh-SSH\2.2\Posh-SSH.psm1:2724 char:17
+                 $SSHFWP.start()
+                 ~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : SshException

Note: I can portforward in a batch script and in git bash, issue is just when using this
Powershell version: 5.1.18362.752
Posh-ssh version: 2.2 from PSGallery
OS: Windows 10

No problem, seems there is an issue with the underlying library. I may remove this cmdlet since dev on the library is so low which has impacted module releases as a consequence.

On Oct 1, 2020, at 12:47 PM, dav101<EMAIL_ADDRESS>wrote:
I saw a old issue https://github.com/darkoperator/Posh-SSH/issues/192 which has not been responded to so have created a new one, when calling New-SSHRemotePortForward it throws a error
New-SSHRemotePortForward -LocalAdress <IP_ADDRESS> -LocalPort 1337 -RemoteAddress <IP_ADDRESS> -RemotePort 3389 -Index 0
Throws error
Write-Verbose : Cannot bind argument to parameter 'Message' because it is null.
At C:\Program Files\WindowsPowerShell\Modules\Posh-SSH\2.2\Posh-SSH.psm1:2704 char:31

            Write-Verbose $session.index

                          ~~~~~~~~~~~~~~

CategoryInfo          : InvalidData: (:) [Write-Verbose], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.WriteVerboseCommand
`New-SSHRemotePortForward -LocalAdress <IP_ADDRESS> -LocalPort 1337 -RemoteAddress <IP_ADDRESS> -RemotePort 3389 -sshSession $CurrentSession
Throws error

Exception calling "Start" with "0" argument(s): "Port forwarding for '<IP_ADDRESS>' port '3389' failed to start."
At C:\Program Files\WindowsPowerShell\Modules\Posh-SSH\2.2\Posh-SSH.psm1:2724 char:17

            $SSHFWP.start()

            ~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
FullyQualifiedErrorId : SshException
Note: I can portforward in a batch script and in git bash, issue is just when using this

Powershell version: 5.1.18362.752
Posh-ssh version: 2.2 from PSGallery
OS: Windows 10
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/darkoperator/Posh-SSH/issues/348, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAD7IHX7Z7AER3QCGHIY2ZTSISXDLANCNFSM4SAVPT5Q.

Hi,
you can easily fix it by changing the index to SessionId:
        foreach($session in $Global:SshSessions)
        {
            Write-Verbose $session.SessionId
            if ($session.SessionId -eq $Index)
            {
                # Add the forward port object to the session
                Write-Verbose "Adding Forward Port Configuration to session $Index"
                $session.session.AddForwardedPort($SSHFWP)
                Write-Verbose "Starting the Port Forward."
                $SSHFWP.start()
                Write-Verbose "Forwarding has been started."
            }
        }


Ask for sharing code of xTAM module

congratulations for great job
for the easy apply to many other experiments on multitask learning, can you provide the independent code of xTAM module?
for example: given x (B, C, H, W), y (B, C, H, W) are features of semantic and depth respectively, how I can build xTAM(x, y)?

Thank you for your interest, I will see if I can work on a refactor for a dedicated xTAM class.


Fix validation test for epacamd_eia_test

I tried running the ETL and I got a foreign key error. I did some investigating and I think this has to do with the boiler_id. There are a lot of rows of the crosswalk where plant_id_eia is not NA and boiler_id is NA. Would this have an effect on the foreign key relationship between those tables?

Re: the FK errors. I think if the harvesting sees (plant_id_eia, boiler_id) in the columns, then it will try and harvest the values it sees in those columns for inclusion in the boiler entity table, and it will also assume that there should be an FK relationship between those columns and the boiler table, which is correct. I'd think it would ignore NA values in both of those cases, but maybe it doesn't? It seems like this would have come up in other tables too.
If necessary you can tell it to ignore some of the automatically generated FK relationships in the resource (table) definition.

Fixed the validation test for test/validate/epacamd_eia_test.py

Now the issue is the min-max row tests.
I looked at the EIA annual plants 860 table which was one of the tables that failed. It appears that the table resulting from the failed build has two less rows than the table resulting from the successful build (Sept 15th).
The rows that show up in the working build table are:

2022-01-01 | 62844 | Cranberry Point Energy Storage
2022-01-01 | 64835 | Silver Queen Wind Farm

I did some more digging and found out that beyond missing rows, there are 7946 rows that differ between the two tables. I looked at an example (2022-01-01 | 195) and see that the only difference is in the plant_name_eia field. The working build table says Narrows (AR) and the failed build table says Narrows.
Because the failed build actually has fewer rows than the working build, I don' think this is a harvesting issue. I'm also pretty sure that the harvesting happens before the glue tables are ever processed.
`

Re: the FK errors. I think if the harvesting sees (plant_id_eia, boiler_id) in the columns, then it will try and harvest the values it sees in those columns for inclusion in the boiler entity table, and it will also assume that there should be an FK relationship between those columns and the boiler table, which is correct. I'd think it would ignore NA values in both of those cases, but maybe it doesn't? It seems like this would have come up in other tables too.
If necessary you can tell it to ignore some of the automatically generated FK relationships in the resource (table) definition.

Foreign key problems were related to my local errors

The only thing done to dev between the 15th and the fail was some documentation updates and, and the re-addition of the epacamd_eia analysis module used by Greg. There is no output table attached to the analysis module, it's just some useful functions to restructure the crosswalk and calculate sub-plants.

The ~8000 rows that are different maybe that could just be a small number of plants for which the most common plant name changed due to values that were harvested from the crosswalk?
Also plant_name_eia should be in the plants_entity_eia table, not the plants_eia860 table. What differences do you see between those two tables (not using the output functions)

The ~8000 rows that are different maybe that could just be a small number of plants for which the most common plant name changed due to values that were harvested from the crosswalk?

If I'm not mistaken, the harvesting process is outlined in the eia.py transform module which gets called in the _etl_eia() function in the etl.py module which happens before (and therefore seperate from) _etl_glue() which processes the crosswalk table.
from the etl() function in etl.py
    if datasets.get("ferc1", False):
        sqlite_dfs.update(_etl_ferc1(datasets["ferc1"], pudl_settings))
    if datasets.get("eia", False):
        sqlite_dfs.update(_etl_eia(datasets["eia"], ds_kwargs))
    if datasets.get("glue", False):
        sqlite_dfs.update(
            _etl_glue(datasets["glue"], ds_kwargs, sqlite_dfs, datasets["eia"])
        )

The build outputs from Sept. 15th would have reflected anything that got merged into dev on September 14th (that was successful).
If the first failed build was the one that happened the night of Sept. 15/16th, that would have been from anything merged into dev on Sept. 15th.  So what happened on the 15th?

If the first failed build was the one that happened the night of Sept. 15/16th, that would have been from anything merged into dev on Sept. 15th. So what happened on the 15th?

I thought the last successful build was from the 15th? Does that mean morning of the 15ths?

The last successful build outputs have a date of September 15th. The builds start at 1am and typically run until 5-6am, Mountain time, or 12-1pm UTC, which is what the GCP dates are in:
 843649024  2022-09-15T12:27:02Z  gs://intake.catalyst.coop/dev/censusdp1tract.sqlite
 761257984  2022-09-15T12:27:04Z  gs://intake.catalyst.coop/dev/ferc1.sqlite
5110330869  2022-09-15T12:28:59Z  gs://intake.catalyst.coop/dev/hourly_emissions_epacems.parquet
 702459904  2022-09-15T12:27:01Z  gs://intake.catalyst.coop/dev/pudl.sqlite

Also plant_name_eia should be in the plants_entity_eia table, not the plants_eia860 table. What differences do you see between those two tables (not using the output functions)

Ok I tried the same thing but with the the plants_eia860 table from the db (not the output tables) and the tables are the same....

Ok I tried the same thing but with the the plants_eia860 table from the db (not the output tables) and the tables are the same....

You said what was different was plant_name_eia and that field is in plants_entity_eia so that is the table to compare between the two DBs if you're looking for plant name discrepancies
This command (executed with dev checked out) will show all the commits that came into dev on 2022-09-15 -- it's just the crosswalk PR.
git log --first-parent --since 2022-09-14 --until 2022-09-15

So what happened on the 15th?

I updated the screenshot above to show the commits from the 15th

--since 2022-09-14 --until 2022-09-15

Wouldn't that be the 14th?

Nope. I just ran it.

You said what was different was plant_name_eia and that field is in plants_entity_eia so that is the table to compare between the two DBs if you're looking for plant name discrepancies

Those tables are also the same.

Okay so if you compare pre & post failure pudl_out.plants_eia860() dataframes you find differences in plant_name_eia
But if you compare pre and post failure plants_entity_eia tables straight from the database, you find that they are identical?

64835

Neither of the missing plant_id_eia rows 64835 , 62844 are in the crosswalk either.

So the only thing that you're concerned about now is understanding why the addition of the epacamd_eia crosswalk table seems to have affected the contents of the plants_eia860 table?

So the only thing that you're concerned about now is understanding why the addition of the epacamd_eia crosswalk table seems to have affected the contents of the plants_eia860 table?

That was just one example, there were other EIA tables that were affected (failed)

Okay so in general the concern is that adding the crosswalk table seems to have affected other EIA tables, and that seems weird / wrong?

Can you diff all of the tables between these two databases you have and identify the differences?

#1692 did modify more than 30 files so... it does seem like there could be some impacts in there. I will look over the changes.

Here's a record of the differences for the plants_eia860 table from the db:

plant_id_eia: 10012 | report_year: 2002 & 2001--> ferc_cogen_status goes from FALSE to None
plant_id_eia: 10012 | report_year: 2002 & 2001--> ferc_exempt_wholesale_generator goes from FALSE to None
plant_id_eia: 10012 | report_year: 2002 & 2001--> ferc_small_power_producer_docket_no goes from 86-501-000 to None
plant_id_eia: 10012 | report_year: 2002 & 2001--> ferc_small_power_producer  goes from TRUE to None
plant_id_eia: 7549 | report_year: 2002 & 2001--> ferc_cogen_status goes from FALSE to None
plant_id_eia: 7549 | report_year: 2002 & 2001--> ferc_exempt_wholesale_generator goes from FALSE to None
plant_id_eia: 7549 | report_year: 2002 & 2001--> ferc_small_power_producer  goes from FALSE to None

Looking back over the PR, the only thing that seems like it might have effects all over the EIA data is the re-write of the leading-zero fixer function. It does look like the new function should be doing the same thing as the old function, but it's notoriously easy to mess up regular expressions.
What is the extent of the differences between the two builds? If it's just a couple of extra rows, or a half dozen individual fields for a couple of random plants 20 years ago, then that doesn't seem scary and we should probably just update the expected number of records.
If there are thousands of rows in multiple tables where the contents have changed as you said above, that seems more concerning. Is that really happening?

I adjusted the row count to account for the -2 rows in each of the pu_eia860, plants_eia860, and utils_eia860 tables. I still don't know why this is happening.
In case we want to revisit this later (and maybe add some regression analysis), I took stock of the types of columns that are changing in the plants_eia860 output table.
There are 2 fewer rows in the current table (than in the version before adding the epacamd_eia crosswalk from PR #1692). There are also 3974 rows (out of 185071 or 185069 rows--depending on whether you compare the old or new version) that differ between the two tables.
The following table shows, for the plants_eia860 output table, what column data has changed. It compares the 3974 rows that differ between the tables to see which columns (represented as the index here) are the culprits.

count shows the total number of rows
unique shows the column contains disperate data (1=no, 2=yes)
freq shows the number of times that column values from miss-matched rows are the same
pct shows the percent of times this column is responsible for the discrepancy between rows in the two versions of the output table

count
unique
freq
pct

plant_name_eia
3974
2
2981
24.9874

city
3974
1
3974
0

county
3974
1
3974
0

latitude
3974
1
3974
0

longitude
3974
2
2975
25.1384

state
3974
1
3974
0

street_address
3974
1
3974
0

zip_code
3974
1
3974
0

timezone
3974
2
3879
2.39054

ash_impoundment
3974
1
3974
0

ash_impoundment_lined
3974
1
3974
0

ash_impoundment_status
3974
1
3974
0

balancing_authority_code_eia
3974
1
3974
0

balancing_authority_name_eia
3974
1
3974
0

datum
3974
1
3974
0

energy_storage
3974
1
3974
0

ferc_cogen_docket_no
3974
1
3974
0

ferc_cogen_status
3974
2
3970
0.100654

ferc_exempt_wholesale_generator_docket_no
3974
1
3974
0

ferc_exempt_wholesale_generator
3974
2
3970
0.100654

ferc_small_power_producer_docket_no
3974
2
3972
0.0503271

ferc_small_power_producer
3974
2
3970
0.100654

ferc_qualifying_facility_docket_no
3974
1
3974
0

grid_voltage_1_kv
3974
1
3974
0

grid_voltage_2_kv
3974
1
3974
0

grid_voltage_3_kv
3974
1
3974
0

iso_rto_code
3974
1
3974
0

liquefied_natural_gas_storage
3974
1
3974
0

natural_gas_local_distribution_company
3974
1
3974
0

natural_gas_storage
3974
1
3974
0

natural_gas_pipeline_name_1
3974
1
3974
0

natural_gas_pipeline_name_2
3974
1
3974
0

natural_gas_pipeline_name_3
3974
1
3974
0

nerc_region
3974
1
3974
0

net_metering
3974
1
3974
0

pipeline_notes
3974
1
3974
0

primary_purpose_id_naics
3974
1
3974
0

regulatory_status_code
3974
1
3974
0

reporting_frequency_code
3974
1
3974
0

sector_id_eia
3974
1
3974
0

sector_name_eia
3974
1
3974
0

service_area
3974
1
3974
0

transmission_distribution_owner_id
3974
1
3974
0

transmission_distribution_owner_name
3974
1
3974
0

transmission_distribution_owner_state
3974
1
3974
0

utility_id_eia
3974
1
3974
0

water_source
3974
1
3974
0

data_maturity
3974
1
3974
0

plant_id_pudl
3974
1
3974
0

utility_name_eia
3974
1
3974
0

utility_id_pudl
3974
1
3974
0

balancing_authority_code_eia_consistent_rate
3974
1
3974
0


When using a boolean to set visibilities on a page field, this only works for the first record you open, the second record is still visible/invisible based on the previous value

Describe the bug
When using a boolean to set visibilities op a page field, this only works for the first record you open, the second record is still visible/invisible based on the previous value
To Reproduce
If the first letter of a project starts with the G, the visibility of the 2 fields should be set to true.
This works for the first record with a G that I open. If I open another record where the No. starts with another letter the visibility is set to false but still shows the fields.
AL Code to reproduce the issue
trigger OnOpenPage()
begin
    ActivateFields;
end;

local procedure ActivateFields()
begin
    FirstLetterProjectNo := Text.CopyStr("No.", 1, 1);
    if FirstLetterProjectNo = 'G' then
        FirstLetterGBoolean := true
    else
        FirstLetterGBoolean := false;
end;

Also tried this in the OnAfterGetRecord()
Expected behavior
Make the fields (in)visible based on the current value and not the first value.
As seen on the screenshot below I first opened a project that starts with G, after that, I opened a project that starts with F, I expect the 2 fields ("Gekoppeld project" and "Project omschrijving") to be invisible now.
Screenshots

5. Versions:

AL Language: v6.1.381323
Business Central: v. 16.0.11240.12076

You need to update the boolean in OnAfterGetRecord(), so that it is set for every record... you are only currently doing it for the first one in OnOpenPage(), so of course that'll happen! This is not new, rather ancient behaviour.
Also, on a Card, you'll need to put those fields in a Group and set Visible on it, not on the fields directly - not that we can see whatever you're currently doing.

@dtkb I also tried the OnAfterGetRecord(), same issue.

You probably need to show a minimal complete example for MS to be able to diagnose it

You probably need to show a minimal complete example for MS to be able to diagnose it

What is incomplete?

You don't show nearly any of the page definition, e.g. what table it's on, how the fields are declared, how their visibility is controlled, etc.
Doing that in OnOpenPage() definitely seems wrong to me. If it still doesn't work after setting the boolean in OnAfterGetRecord() (or OnAfterGetCurrRecord(), but that shouldn't be needed), then something subtle is wrong, and people need info to figure it out.

        field("Project Description"; "Project Description")
        {
            ApplicationArea = all;
            Visible = FirstLetterGBoolean;

Hello,
have you tried to set the InDataSet attributes?
Normally it should work with the attribute.
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods/devenv-indataset-attribute

Dynamic visibility does not work directly on page fields. You need to put the field in question into a new field group and assign the Visible property to the group instead.
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-visible-property#dynamic-visibility-of-controls

Cheers @jthoerner-tso and @NKarolak I will try this soon!

I said that already too...

Also, on a Card, you'll need to put those fields in a Group and set Visible on it, not on the fields directly - not that we can see whatever you're currently doing.

I said that already too...

Also, on a Card, you'll need to put those fields in a Group and set Visible on it, not on the fields directly - not that we can see whatever you're currently doing.

Please be salty somewhere else.

Sorry, I didn't remember that, so deleted my silly comment.

Closing the issue as it seems a resolution was found within the community. The issue was outside of the scope of this repository.


feat(plugins) Syncing plugin version to the Kong version

Summary
With almost all Kong plugins bundled inside Kong itself we want to
remove customer confusion by syncing all plugin versions to the Kong
version. This allows users to:

Refer to the Kong version when reporting plugin issues, instead of
having to look up the plugin version.
Update our plugin documentation to be Kong version centric instead
of plugin version centric starting in Kong 3.0
Developers no longer need to remember to update the plugin version
when making bundled plugin changes.
Simplify changelog management by only having 1 changelog for Kong

I suggest looking at and reviewing each commit individually as quite a few files were touched. I also deleted old unecessary files (rockspec, changelog, license).
Full changelog

Sync every plugin version to the Kong version

Issue reference
FT-2775

NTS: check the /meta endpoint and see if it includes plugin versions

We do not return plugin version info on the / endpoint, just loaded_plugins list and available_on_server plugins

this looks like an extremely dangerous thing to do. The same plugin will report a different version on the next version of Kong. I'm not the expert on this but I think it will break all compatibilty checks between CP and DP when upgrading.
The version belongs to the plugin (it's plugin meta-data) and hence should be set there, never depend dynamically on the Kong version.
I think the better approach would be to update the plugin versions, hardcoded, not dynamic!, to the version of Kong in which they were shipped. Albeit that might defeat the purpose of this PR to reduce customer confusion.
my 2cts.
Ping @mikefero @hbagdi @RobSerafini

this looks like an extremely dangerous thing to do. The same plugin will report a different version on the next version of Kong. I'm not the expert on this but I think it will break all compatibility checks between CP and DP when upgrading.

Version compatibility between the CP and DP currently use the Kong Gateway version and disregard plugin version; we went that route because we knew what features were bundled in each version of the gateway which simplified the logic quite a bit. With that stated we really should clean up the compatibility layer @tyler-ball to remove unnecessary checks that this PR creates in that layer (see check_configuration_version as one example).

I think the better approach would be to update the plugin versions, hardcoded, not dynamic!, to the version of Kong in which they were shipped. Albeit that might defeat the purpose of this PR to reduce customer confusion.

Are you suggesting doing this at release time? That is doable as well, but I think the end result would be the same. From the version compatibility standpoint this shouldn't cause any issues there, but does need to be thoroughly tested before merging this in.

Are you suggesting doing this at release time?

I'd suggest that at release time we update all UPDATED plugins to match the new Kong version, so anything that didn't change, doesn't get updated. Especially the dynamic link to the Kong version makes me very uncomfortable, because why wouldn't we simply remove the plugin version field from the code in that case?

Version compatibility between the CP and DP currently use the Kong Gateway version and disregard plugin version

That is ignoring the custom plugins? We have folks running dozens of custom plugins on a single dataplane...

because why wouldn't we simply remove the plugin version field from the code in that case?
I'm also in favor of this. I had the same conclusion and investigated doing it at one point. I don't remember exactly why I didn't go that route - I don't remember what reads the plugin version. I think I also wanted to introduce less risk. But I am in favor of removing the version entirely in the future

I love the tags cloud on this PR 😄 .
For attendees of this PR, do we have agreed on the path for this PR? Do we want to put this in 3.0?

@fffonion yes, we would like this PR in 3.0.
@hbagdi Can you comment about the following points, raised by @Tieske :

the VERSION constant in plugins should move into schema.lua I think, so Koko can also access it.
if the version is in the schema, the schema can also be the place where we add the version-conversion logic (since that is "simple Lua", whereas the handler.lua will probably pull in everything-but-the-kitchen-sink, which won't work in Koko)

As discussed offline, moving the VERSION to another file wont help.


support s390x

Describe the bug
Cannot deploy to s390x.
Using the default installation results in
[root@vance-test-services benchmark-operator]# make deploy

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
make: *** [Makefile:128: kustomize] Error

Using the helm deployment, results in the following in the redis-master pod:
1 line
standard_init_linux.go:228: exec user process caused: exec format error

To Reproduce
Steps to reproduce the behavior:

Create a cluster on s390x architecture.
Try either the default  or helm installation.
Errors as described above.

Expected behavior
Profit.
Related issues
Here we see support for ppc64le added: https://github.com/cloud-bulldozer/benchmark-operator/issues/649

This is still relevant.


store.query question

@tstirrat et al. - This may be simple but I couldnt find in the documentation.
I am using the following:
    let filterText = this.get('filterText');
    return this.store.query('company', {
      name: filterText
    });

If filterText is "rub"  I want to return both of the following:
...name: "scrub brush"
...name: "rubbermaid"
As is it only returns the second but not the first.
Is this doable with EmberFire?  Also, a way to do a case insensitive query?
BTW the recent improvements to emberfire are fantastic!!! Great work.
Brendan

Unfortunately, we don't have a way to do a "like" style queries that match substrings. For that, and case insensitive queries, you might want to try some type of indexer such as ElasticSearch.
Also, your query syntax is incorrect. The only properties that are accepted in the query hash are orderBy, limitToFirst, startAt, endAt, and equalTo. These map to the underlying Firebase query methods.
From the docs:

... combine orderBy with limitToFirst, startAt, endAt, and equalTo to construct more complex queries. See the EmberFire API docs and documentation on Firebase's querying methods for more details.

Thanks for the reply @tstirrat

Also, your query syntax is incorrect.

This is really strange because this syntax 100% works the exact way I wrote it above and effectively works as an autocomplete.
However, it is case sensitive and it has to start with whatever the value is ("rub" in my example).
Is this a surprise that it actually works? Is this a "bug" and not a "feature"?

@tstirrat - I see now what it is doing. The syntax above is actually just pulling down ALL and then doing the filter client side. Weird.
Is there any documentation on debugging Firebase connections in the browser? Checking the frames in chrome isn't the most user friendly.

I was very surprised to see it partially working, figured there might be some sort of client side filtering.
Re: the debugging connections: turn on debug logging: Firebase.enableLogging(true, true). Note that this is on the Firebase class, not on the ref

Yeah this should be closed. @tstirrat, I came up with a creative approach to the autocomplete problem (without using Elastisearch) that may be helpful for others in the same position. Any place I should write it up?

I'd be interested, in here is fine. Or if it's better suited, maybe as a series of gists.

Here is the GIST to my workaround of the case insensitive, partial string search for an autocomplete: https://gist.github.com/brendanoh/79921203529ab9a57cb3


The type check of BinaryTree's 'has' function  incorrect

Describe the bug
expect(tree.has(tree.get(4), node => node.key)).toBe(false); The type check needs to bring an error
To Reproduce
tree.add(1);
tree.add(2);
tree.add(3);
expect(tree.has(1)).toBe(true);
expect(tree.has(2)).toBe(true);
expect(tree.has(3)).toBe(true);
expect(tree.has(4)).toBe(false);
expect(tree.has(tree.get(4), node => node.key)).toBe(false);

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

In v1.39.3, we have fixed this


Repeating targets with the same name

I have a list of items, and each one has a link to click to edit it. I am using stimulus to make the edit "modal" form visible when they click that edit link. The id of what is going to be edited is present as an id= on the corresponding link tag of the list
So, the edit link looks like this:
  content#edit" data-target="content.editBtn" id="<%= url_for(content) %>")>Edit
And the idea is that the content#edit action in the stimulus controller examines the  and locates the id of it and uses that to edit the right row.
However the problem I am having is, I think, that as a result all the rows of this list have a data-target with the same name and the wrong one (the first one?) gets bound to the target..
However if I wanted to make each data-target different by e.g. appending the id to it, now I have a long list of targets in the controller.js so that doesn't make sense.
Phew, I hope you followed that. What's the right way to handle?

I think you may want each row to have its own controller? Then the click would go to that controller. Alternatively you could look for the right target by walking up the chain from the event’s target, but that feels a bit dirty.
There may be more idiomatic ways though, I don’t have a ton of Stimulus experience.

I considered each row with its own controller, but that seems quite ugly. Similarly is having a duplicate of the modal form with each row, also quite ugly.
The problem as I see it for the example that you link to is that the data-target is the same for each row. It would seem that this would confuse the controller, unless the data-action that triggers is tied to the particular (duplicated) instance of the data-controller, and somehow the context that is established resolves to the particular corresponding data-target.
I should try that if you think that's the right way to go.

I solved it but it seems I have to leave Stimulus in order to be able to address the html for the modal form. If you want I will explain it here. This is not an issue with stimulus per-se. Either there's a way to do this within Stimulus, or it's fine to sometime use old fashioned querySelector etc to address a bit of html. If there's a better way to do this, I'd love to hear it.

Closing in favor of discussing on https://discourse.stimulusjs.org. Feel free to start a new thread.


add redis client features, generate mock and add a unit test for logger

Introduce redis functions:
- Incr IncrBy
- Decr DecrBy
- Exists
- Expire
Generated Mock for ddb.SimpleRepository
Added an unit test for mon.Logger, that tests context with fields

looks good


Update first-web-api.md

There's alot of customer confusion on this. After my routing PR merges, I'll add links to routing.

@scottaddie  removed scaffolded
The ASP.NET Core scaffolded item templates for:
True for non-scaffolded too.


Improve verse indexing speed

This reduces the time to build TSKe on my machine from 15 minutes to 2.5 minutes (and makes the progress grow more linearly), and is therefore a great time saver when testing :)
The generated index files do not change.

Great idea!


Text alignment off in  form element

Using Bootstrap 4.0.0 beta, the text alignment in a select box seems to be off. You can't see the difference between a g and q.
Bootstrap 4.0.0 beta
Codepen: https://codepen.io/anon/pen/KvGQeo

With Bootstrap 4.0.0 alpha 6, everything looked fine.
Bootstrap 4.0.0 alpha 6
Codepen: https://codepen.io/anon/pen/XaxZBO

OS: Windows 10
Browser: Chrome 60

could specify browser+version and os?
i do not see mentioned behaviour

Oops, forgot to add that. I've added it to the post (Chrome 10, Windows 10).

no problems on macOS 10.12.5 with chrome 60
beta

only noticible difference is that the font changes
in alpha it just says sans-serif, in the beta is uses the system fonts
could that be whats causing it?

That is the only difference I could make out as well, so that could be the issue.

Duplicate of #23347.


docker hub?

Hi! Can you create an image in docker hub? My server doesnt have docker compose built in and I tried using my laptop but it has a different architecture (ARM vs x86). :(

hi you can try docker pull b1n4ryj4n/koreader-sync

Thanks! It works! :)

Btw. This is another question thats why I closed the issue. Have you been able to sync highlights and notes? Also, have you found a way to keep track of what books you have read? Thanks!

Have you been able to sync highlights and notes?

Sry i wont use koreader to highlighting stuff or taking notes

Also, have you found a way to keep track of what books you have read?

Sadly not an optimal way. I use git (selfhosted gitea) for now until i find some good alternative. Basically two branches:

"main" = all books i have
"koreader" = all books (without finished ones)


ESP32 Build is broken, Does not enumerate

Operating System
Linux
INFO_UF2.TXT
TinyUF2 Bootloader 0.11.0-13-g9796a54 - tinyusb (0.12.0-203-ga4cfd1c69)
Model: Unexpected Maker TinyS3
Board-ID: ESP32S3-TinyS3-01
Date: Nov  8 2022
What happened ?
ESP32 build worked fine until mid november, since then it is broken, it does not enumerate. Maybe it is cause by updated docker image for esp-idf.  The image used by the workflow is repressive/idf:release-v4.4 which may have been updated at that time... last updated 5 days ago!
How to reproduce ?
I am testing on unexpectedmaker tinys3 board! Here are the last working and first non-working builds that I found!
(Nov 9) unexpectedmaker_tiny3  boots fine
https://github.com/adafruit/tinyuf2/actions/runs/3424066037
(Nov 15) couple of commits later it does not enumerate
https://github.com/adafruit/tinyuf2/actions/runs/3466891115
Can anyone try to reproduce the issue? What could be wrong?
Debug Log
No response
Screenshots
No response

I just tested it with the unexpectedmaker pros3 board as well, same thing happens. The builds after Nov15 do not enumerate, the LED stays RED!

Confirmed on tinys3, it is boot looping
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd0108,len:0x1644
load:0x403b6000,len:0xe7c
load:0x403ba000,len:0x3248
entry 0x403b6334
␛[0;32mI (25) boot: ESP-IDF v4.4.3-145-g76caa64286 2nd stage bootloader␛[0m
␛[0;32mI (25) boot: compile time 02:29:08␛[0m
␛[0;32mI (25) boot: chip revision: 0␛[0m
␛[0;32mI (28) qio_mode: Enabling default flash chip QIO␛[0m
␛[0;32mI (33) boot.esp32s3: Boot SPI Speed : 80MHz␛[0m
␛[0;32mI (38) boot.esp32s3: SPI Mode       : QIO␛[0m
␛[0;32mI (43) boot.esp32s3: SPI Flash Size : 8MB␛[0m
␛[0;32mI (47) boot: Enabling RNG early entropy source...␛[0m
␛[0;32mI (53) boot: Partition Table:␛[0m
␛[0;32mI (56) boot: ## Label            Usage          Type ST Offset   Length␛[0m
␛[0;32mI (64) boot:  0 nvs              WiFi data        01 02 00009000 00005000␛[0m
␛[0;32mI (71) boot:  1 otadata          OTA data         01 00 0000e000 00002000␛[0m
␛[0;32mI (79) boot:  2 ota_0            OTA app          00 10 00010000 00200000␛[0m
␛[0;32mI (86) boot:  3 ota_1            OTA app          00 11 00210000 00200000␛[0m
␛[0;32mI (93) boot:  4 uf2              factory app      00 00 00410000 00040000␛[0m
␛[0;32mI (101) boot:  5 ffat             Unknown data     01 81 00450000 003b0000␛[0m
␛[0;32mI (109) boot: End of partition table␛[0m
␛[0;32mI (113) boot: Defaulting to factory image␛[0m
␛[0;32mI (117) esp_image: segment 0: paddr=00410020 vaddr=3c020020 size=044c4h ( 17604) map␛[0m
␛[0;32mI (129) esp_image: segment 1: paddr=004144ec vaddr=3fc90620 size=01dcch (  7628) load␛[0m
␛[0;32mI (136) esp_image: segment 2: paddr=004162c0 vaddr=40374000 size=09d58h ( 40280) load␛[0m
␛[0;32mI (151) esp_image: segment 3: paddr=00420020 vaddr=42000020 size=13d00h ( 81152) map␛[0m
␛[0;32mI (164) esp_image: segment 4: paddr=00433d28 vaddr=4037dd58 size=028bch ( 10428) load␛[0m
␛[0;32mI (176) boot: Loaded app from partition at offset 0x410000␛[0m
␛[0;32mI (176) boot: Disabling RNG early entropy source...␛[0m
␛[0;32mI (188) cpu_start: Pro cpu up.␛[0m
␛[0;32mI (188) cpu_start: Starting app cpu, entry point is 0x40374d6c␛[0m
␛[0;32mI (0) cpu_start: App cpu up.␛[0m
␛[0;32mI (202) cpu_start: Pro cpu start user code␛[0m
␛[0;32mI (202) cpu_start: cpu freq: 160000000␛[0m
␛[0;32mI (202) cpu_start: Application information:␛[0m
␛[0;32mI (205) cpu_start: Project name:     tinyuf2␛[0m
␛[0;32mI (210) cpu_start: App version:      0.11.0-15-g1777d44␛[0m
␛[0;32mI (215) cpu_start: Compile time:     Nov 15 2022 02:29:04␛[0m
␛[0;32mI (222) cpu_start: ELF file SHA256:  30b5c0ed93c53172...␛[0m
␛[0;32mI (228) cpu_start: ESP-IDF:          v4.4.3-145-g76caa64286␛[0m
␛[0;32mI (234) heap_init: Initializing. RAM available for dynamic allocation:␛[0m
␛[0;32mI (241) heap_init: At 3FCA5AC8 len 00043C48 (271 KiB): D/IRAM␛[0m
␛[0;32mI (252) heap_init: At 3FCE9710 len 00005724 (21 KiB): STACK/DRAM␛[0m
␛[0;32mI (254) heap_init: At 3FCF0000 len 00008000 (32 KiB): DRAM␛[0m
␛[0;32mI (260) heap_init: At 600FE000 len 00002000 (8 KiB): RTCRAM␛[0m
␛[0;32mI (267) spi_flash: detected chip: gd␛[0m
␛[0;32mI (271) spi_flash: flash io: qio␛[0m
␛[0;32mI (275) sleep: Configure to isolate all GPIO pins in sleep state␛[0m
␛[0;32mI (281) sleep: Enable automatic switching of GPIO sleep configuration␛[0m
␛[0;32mI (289) cpu_start: Starting scheduler on PRO CPU.␛[0m
␛[0;32mI (0) cpu_start: Starting scheduler on APP CPU.␛[0m
␛[0;32mI (309) gpio: GPIO[17]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0 ␛[0m

assert failed: 0x4037c261

Backtrace: 0x403756a2:0x3fc90f40 0x40379b45:0x3fc90f60 0x4037eada:0x3fc90f80 0x4037c261:0x3fc90fc0 0x4037a4c8:0x3fc90fe0 0x4200147d:0x3fc91010 0x420024b9:0x3fc91050 0x42002541:0x3fc91090 0x420063bf:0x3fc910d0 0x40376491:0x3fc91110 0x42012f93:0x3fcf3f70 0x420071e2:0x3fcf3f90 0x4037ab94:0x3fcf3fb0

ELF file SHA256: 30b5c0ed93c53172

Rebooting...
␀�ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
... loop forever```

It looks like an issue that affects the tinyuf2 & Actions infrastructure only.
Manual builds ( self-hosted or hosted by Codespace ) are still doing good to me.

I checked the assert address, it wasn't really helpful...
spinlock_acquire at /opt/esp/idf/components/esp_hw_support/include/soc/spinlock.h:75
(inlined by) xPortEnterCriticalTimeout at /opt/esp/idf/components/freertos/port/xtensa/port.c:293

see also the full backtrace:
0x403756b2: panic_abort at /opt/esp/idf/components/esp_system/panic.c:408

0x40379b71: esp_system_abort at /opt/esp/idf/components/esp_system/esp_system.c:128

0x4037edfe: __assert_func at /opt/esp/idf/components/newlib/assert.c:47

0x4037c28d: spinlock_acquire at /opt/esp/idf/components/esp_hw_support/include/soc/spinlock.h:75
 (inlined by) xPortEnterCriticalTimeout at /opt/esp/idf/components/freertos/port/xtensa/port.c:293

0x4037a4f4: vPortEnterCritical at /opt/esp/idf/components/freertos/port/xtensa/include/freertos/portmacro.h:578
 (inlined by) xQueueGenericSendFromISR at /opt/esp/idf/components/freertos/queue.c:1082

0x420026d1: dcd_event_handler at ??:?

0x42006763: _dcd_int_handler at dcd_esp32sx.c:?

0x403764bd: _xt_lowint1 at /opt/esp/idf/components/freertos/port/xtensa/xtensa_vectors.S:1114

0x42012c63: cpu_ll_waiti at /opt/esp/idf/components/hal/esp32s3/include/hal/cpu_ll.h:182
 (inlined by) esp_pm_impl_waiti at /opt/esp/idf/components/esp_pm/pm_impl.c:837

0x4200763e: esp_vApplicationIdleHook at /opt/esp/idf/components/esp_system/freertos_hooks.c:63

0x4037abc0: prvIdleTask at /opt/esp/idf/components/freertos/tasks.c:3987

I am pretty sure nothing wrong with the source, the most likely culprit is still the idf docker image... Is there a way to get in touch with the espressif developers?

The following is from my ESP32-S3-DevKitC1-N32R8V. I've been struggling to get just about any UF2 implementation onto this device.
I've tried:

Flashing pre-compiled binaries with the latest esptool.py (v4.4).
Flashing with esptool.py (v3.2) under lib/esp-idf.

These are the commands that gets me the closest to a running device. The one difference from the ports/espressif/README.md is that the bootloader.bin starts at 0x0 instead of 0x1000.
tinyuf2.bin
esptool.py --chip esp32s3 -p /dev/ttyACM0 -b 460800 --before=default_reset --after=hard_reset write_flash --flash_mode dio --flash_freq 80m --flash_size detect 0x0 bootloader.bin 0x8000 partition-table.bin 0xe000 ota_data_initial.bin 0x2d0000 tinyuf2.bin
Show output
esptool.py v4.4
Serial port /dev/ttyACM0
Connecting...
Chip is ESP32-S3 (revision v0.1)
Features: WiFi, BLE
Crystal is 40MHz
MAC: 68:b6:b3:3d:7a:88
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
WARNING: Flasher stub doesn't fully support flash size larger than 16MB, in case of failure use --no-stub.
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00000000 to 0x00005fff...
Flash will be erased from 0x00410000 to 0x00434fff...
Compressed 3072 bytes to 136...
Wrote 3072 bytes (136 compressed) at 0x00008000 in 0.0 seconds (effective 927.1 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 31...
Wrote 8192 bytes (31 compressed) at 0x0000e000 in 0.1 seconds (effective 1213.7 kbit/s)...
Hash of data verified.
Warning: Image file at 0x0 is protected with a hash checksum, so not changing the flash size setting. Use the --flash_size=keep option instead of --flash_size=32MB in order to remove this warning, or use the --dont-append-digest option for the elf2image command in order to generate an image file without a hash checksum
Compressed 22256 bytes to 14038...
Wrote 22256 bytes (14038 compressed) at 0x00000000 in 0.2 seconds (effective 902.3 kbit/s)...
Hash of data verified.
Compressed 149248 bytes to 94705...
Wrote 149248 bytes (94705 compressed) at 0x00410000 in 0.9 seconds (effective 1367.9 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

combined.bin
esptool.py --chip esp32s3 -p /dev/ttyACM0 -b 460800 --before=default_reset --after=hard_reset write_flash --flash_mode dio --flash_freq 80m --flash_size detect 0x0 combined.bin
Show output
esptool.py v4.4
Serial port /dev/ttyACM0
Connecting...
Chip is ESP32-S3 (revision v0.1)
Features: WiFi, BLE
Crystal is 40MHz
MAC: 68:b6:b3:3d:7a:88
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
WARNING: Flasher stub doesn't fully support flash size larger than 16MB, in case of failure use --no-stub.
Flash will be erased from 0x00000000 to 0x00434fff...
Warning: Image file at 0x0 is protected with a hash checksum, so not changing the flash size setting. Use the --flash_size=keep option instead of --flash_size=32MB in order to remove this warning, or use the --dont-append-digest option for the elf2image command in order to generate an image file without a hash checksum
Compressed 4409088 bytes to 114796...
Wrote 4409088 bytes (114796 compressed) at 0x00000000 in 20.9 seconds (effective 1688.6 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

UART
Both flashing methods result in identical output.
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40375378
SPIWP:0xee
Octal Flash Mode Enabled
For OPI Flash, Use Default Flash Boot Mode
mode:SLOW_RD, clock div:1
load:0x3fcd0108,len:0x15ec
load:0x403b6000,len:0xdb8
load:0x403ba000,len:0x31c8
entry 0x403b6318
I (37) boot: ESP-IDF v4.4.2-378-g9269a536ac 2nd stage bootloader
I (38) boot: compile time 11:36:36
I (38) boot: chip revision: 0
I (41) qio_mode: Enabling default flash chip QIO
E (46) qio_mode: Failed to set QIE bit, not enabling QIO mode
I (52) boot.esp32s3: Boot SPI Speed : 80MHz
I (57) boot.esp32s3: SPI Mode       : SLOW READ
I (62) boot.esp32s3: SPI Flash Size : 8MB
I (67) boot: Enabling RNG early entropy source...
I (72) boot: Partition Table:
I (76) boot: ## Label            Usage          Type ST Offset   Length
I (83) boot:  0 nvs              WiFi data        01 02 00009000 00005000
I (91) boot:  1 otadata          OTA data         01 00 0000e000 00002000
I (98) boot:  2 ota_0            OTA app          00 10 00010000 00200000
I (106) boot:  3 ota_1            OTA app          00 11 00210000 00200000
I (113) boot:  4 uf2              factory app      00 00 00410000 00040000
I (121) boot:  5 ffat             Unknown data     01 81 00450000 003b0000
I (128) boot: End of partition table
I (133) boot: Defaulting to factory image
I (137) esp_image: segment 0: paddr=00410020 vaddr=3c020020 size=03dcch ( 15820) map
I (150) esp_image: segment 1: paddr=00413df4 vaddr=3fc90150 size=01c4ch (  7244) load
I (156) esp_image: segment 2: paddr=00415a48 vaddr=40374000 size=0a5d0h ( 42448) load
I (174) esp_image: segment 3: paddr=00420020 vaddr=42000020 size=1347ch ( 78972) map
I (193) esp_image: segment 4: paddr=004334a4 vaddr=4037e5d0 size=01b7ch (  7036) load
I (196) esp_image: segment 5: paddr=00435028 vaddr=50000000 size=00010h (    16) load
I (204) boot: Loaded app from partition at offset 0x410000
I (205) boot: Disabling RNG early entropy source...
I (222) cpu_start: Pro cpu up.
I (222) cpu_start: Starting app cpu, entry point is 0x40374d14
I (195) cpu_start: App cpu up.
I (237) cpu_start: Pro cpu start user code
I (237) cpu_start: cpu freq: 160000000
I (237) cpu_start: Application information:
I (239) cpu_start: Project name:     tinyuf2
I (244) cpu_start: App version:      0.11.0
I (249) cpu_start: Compile time:     Oct 17 2022 11:36:31
I (255) cpu_start: ELF file SHA256:  148a4f7802a8f23d...
I (261) cpu_start: ESP-IDF:          v4.4.2-378-g9269a536ac
I (268) heap_init: Initializing. RAM available for dynamic allocation:
I (275) heap_init: At 3FCA5478 len 00044298 (272 KiB): D/IRAM
I (281) heap_init: At 3FCE9710 len 00005724 (21 KiB): STACK/DRAM
I (288) heap_init: At 3FCF0000 len 00008000 (32 KiB): DRAM
I (294) heap_init: At 600FE000 len 00002000 (8 KiB): RTCRAM
I (301) spi_flash: detected chip: mxic
                                      W (305) spi_flash: Detected flash size > 16 MB, but access beyond 16 MB is not supported for this flash model yet.
          I (316) spi_flash: flash io: qio

assert failed: 0x42006b45

Backtrace: 0x4037564a:0x3fceb250 0x40379991:0x3fceb270 0x4037e926:0x3fceb290 0x42006b45:0x3fceb2d0 0x40374ff5:0x3fceb310 0x403bb410:0x3fceb340 0x403bb879:0x3fceb380 0x403b63c2:0x3fceb4b0 0x40045c01:0x3fceb570 |<-CORRUPTED

ELF file SHA256: 148a4f7802a8f23d

Rebooting...

ESP32-S3-DevKitC1-N32R8V (WROOM-2)
Setup
My next approach was to compile from source. I started by defining a new board with the associated files. In this instance, I defined it as espressif_esp32s3_devkitc_1-1 and under it, I included the following files.
partitions-32MB.csv
# ESP-IDF Partition Table
# Name,   Type, SubType, Offset,  Size, Flags
# bootloader.bin,,          0x1000, 32K
# partition table,,         0x8000, 4K
nvs,      data, nvs,      0x9000,  20K,
otadata,  data, ota,      0xe000,  8K,
ota_0,    0,    ota_0,   0x10000,  2048K,
ota_1,    0,    ota_1,  0x210000,  2048K,
uf2,      app,  factory,0x410000,  256K,
ffat,     data, fat,    0x450000,  28352K,

sdkconfig
# Board Specific Config

# Partition Table
CONFIG_PARTITION_TABLE_CUSTOM_FILENAME="partitions-32MB.csv"

# Serial flasher config
CONFIG_ESPTOOLPY_FLASHSIZE_32MB=y

board.h
I have seen a few comments that on the WROOM-2, the Neopixel pin is GPIO38 instead of GPIO48.
# Apply board specific content here
set(IDF_TARGET "esp32s3")
/*
 * The MIT License (MIT)
 *
 * Copyright (c) 2020 Ha Thach (tinyusb.org) for Adafruit Industries
 *
 * Permission is hereby granted, free of charge, to any person obtaining a copy
 * of this software and associated documentation files (the "Software"), to deal
 * in the Software without restriction, including without limitation the rights
 * to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 * copies of the Software, and to permit persons to whom the Software is
 * furnished to do so, subject to the following conditions:
 *
 * The above copyright notice and this permission notice shall be included in
 * all copies or substantial portions of the Software.
 *
 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 * THE SOFTWARE.
 */

#ifndef ESPRESSIF_S3_DEVKITC_H_
#define ESPRESSIF_S3_DEVKITC_H_

//--------------------------------------------------------------------+
// Button
//--------------------------------------------------------------------+

// Enter UF2 mode if GPIO is pressed while 2nd stage bootloader indicator
// is on e.g RGB = Purple. If it is GPIO0, user should not hold this while
// reset since that will instead run the 1st stage ROM bootloader
#define PIN_BUTTON_UF2        0

// GPIO that implement 1-bit memory with RC components which hold the
// pin value long enough for double reset detection.
// #define PIN_DOUBLE_RESET_RC

//--------------------------------------------------------------------+
// LED
//--------------------------------------------------------------------+

// GPIO connected to Neopixel data
#define NEOPIXEL_PIN          38

// Brightness percentage from 1 to 255
#define NEOPIXEL_BRIGHTNESS   0x10

// Number of neopixels
#define NEOPIXEL_NUMBER       1

// LED for indicator
// If not defined neopixel will be use for flash writing instead
// #define LED_PIN               42
// #define LED_STATE_ON          1

//--------------------------------------------------------------------+
// USB UF2
//--------------------------------------------------------------------+

#define USB_VID           0x239A
#define USB_PID           0x00A5    // TODO temporarily shared with S2 saola wrover
#define USB_MANUFACTURER  "Espressif"
#define USB_PRODUCT       "ESP32S3 DevKitC 1"

#define UF2_PRODUCT_NAME  USB_MANUFACTURER " " USB_PRODUCT
#define UF2_BOARD_ID      "ESP32S3-DevKitC-v1.1"
#define UF2_VOLUME_LABEL  "S3DKC1BOOT"
#define UF2_INDEX_URL     "https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/hw-reference/esp32s3/user-guide-devkitc-1.html"

#endif
# Board Specific Config

# Partition Table
CONFIG_PARTITION_TABLE_CUSTOM_FILENAME="partitions-32MB.csv"

# Serial flasher config
CONFIG_ESPTOOLPY_FLASHSIZE_32MB=y

Compile
When I tried to compile I ran into issues generating the partitions tables. esptool.py (v3.2-dev) does not support flash sizes higher than 16.
make BOARD=espressif_esp32s3_devkitc_1-1 all
Show output
idf.py -B_build/espressif_esp32s3_devkitc_1-1 -DBOARD=espressif_esp32s3_devkitc_1-1 build
Executing action: all (aliases: build)
Running ninja in directory /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1
Executing "ninja all"...
[0/1] Re-running CMake...-- Building ESP-IDF components for target esp32s3
-- Project sdkconfig file /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1/sdkconfig
Loading defaults file /home/rgrizzell/tinyuf2/ports/espressif/sdkconfig.defaults...
/home/rgrizzell/tinyuf2/ports/espressif/sdkconfig.defaults:21 CONFIG_FLASHMODE_QIO was replaced with CONFIG_ESPTOOLPY_FLASHMODE_QIO
Loading defaults file /home/rgrizzell/tinyuf2/ports/espressif/boards/espressif_esp32s3_devkitc_1-1/sdkconfig...
 Contents:" && /usr/bin/cmake -E echo "*******************************************************************************" && /home/rwgrizzell/.espressif/python_env/idf5.0_py3.10_env/bin/python /home/rgrizzell/tinyuf2/lib/esp-idf/components/partition_table/gen_esp32part.py -q --offset 0x8000 --flash-size 2MB -- /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1/partition_table/partition-table.bin && /usr/bin/cmake -E echo "*******************************************************************************"
Partitions tables occupies 32.0MB of flash (33554432 bytes) which does not fit in configured flash size 2MB. Change the flash size in menuconfig under the 'Serial Flasher Config' menu.
[37/917] Building C object esp-idf/mbedtls/mbedtls/library/CMakeFiles/mbedcrypto.dir/bignum.c.objninja: build stopped: subcommand failed.
ninja failed with exit code 1, output of the command is in the /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1/log/idf_py_stderr_output_748177 and /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1/log/idf_py_stdout_output_748177
make: *** [Makefile:31: all] Error 2

I then updated the esp-idf submodule to v5.0 (which updates esptool.py to v4.4), the Serial Flasher then supports 32MB, recognizing the variables set in sdkconfig. Confirmed by running: idf.py menuconfig -DBOARD=espressif_esp32s3_devkitc_1-1
Show output
idf.py -B_build/espressif_esp32s3_devkitc_1-1 -DBOARD=espressif_esp32s3_devkitc_1-1 build
Executing action: all (aliases: build)
Running cmake in directory /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1
Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 -DBOARD=espressif_esp32s3_devkitc_1-1 -DCCACHE_ENABLE=0 /home/rgrizzell/tinyuf2/ports/espressif"...
-- Found Git: /usr/bin/git (found version "2.34.1")
-- The C compiler identification is GNU 11.2.0
-- The CXX compiler identification is GNU 11.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /home/rgrizzell/.espressif/tools/xtensa-esp32s3-elf/esp-2022r1-11.2.0/xtensa-esp32s3-elf/bin/xtensa-esp32s3-elf-gcc
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /home/rgrizzell/.espressif/tools/xtensa-esp32s3-elf/esp-2022r1-11.2.0/xtensa-esp32s3-elf/bin/xtensa-esp32s3-elf-gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /home/rgrizzell/.espressif/tools/xtensa-esp32s3-elf/esp-2022r1-11.2.0/xtensa-esp32s3-elf/bin/xtensa-esp32s3-elf-g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Building ESP-IDF components for target esp32s3
-- Project sdkconfig file /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1/sdkconfig
Loading defaults file /home/rgrizzell/tinyuf2/ports/espressif/sdkconfig.defaults...
/home/rgrizzell/tinyuf2/ports/espressif/sdkconfig.defaults:21 CONFIG_FLASHMODE_QIO was replaced with CONFIG_ESPTOOLPY_FLASHMODE_QIO
Loading defaults file /home/rgrizzell/tinyuf2/ports/espressif/boards/espressif_esp32s3_devkitc_1-1/sdkconfig...
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of time_t
-- Check size of time_t - done
-- Found Python3: /home/rgrizzell/.espressif/python_env/idf5.0_py3.10_env/bin/python (found version "3.10.6") found components: Interpreter
-- Performing Test C_COMPILER_SUPPORTS_WFORMAT_SIGNEDNESS
-- Performing Test C_COMPILER_SUPPORTS_WFORMAT_SIGNEDNESS - Success
-- App "tinyuf2" version: 0.11.0-dirty
-- Adding linker script /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1/esp-idf/esp_system/ld/memory.ld
-- Adding linker script /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_system/ld/esp32s3/sections.ld.in
-- Adding linker script /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_rom/esp32s3/ld/esp32s3.rom.ld
-- Adding linker script /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_rom/esp32s3/ld/esp32s3.rom.api.ld
-- Adding linker script /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_rom/esp32s3/ld/esp32s3.rom.libgcc.ld
-- Adding linker script /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_rom/esp32s3/ld/esp32s3.rom.newlib.ld
-- Adding linker script /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_rom/esp32s3/ld/esp32s3.rom.version.ld
-- Adding linker script /home/rgrizzell/tinyuf2/lib/esp-idf/components/soc/esp32s3/ld/esp32s3.peripherals.ld
-- Components: app_trace app_update boards bootloader bootloader_support bt cmock console cxx driver efuse esp-tls esp_adc esp_app_format esp_common esp_eth esp_event esp_gdbstub esp_hid esp_http_client esp_http_server esp_https_ota esp_https_server esp_hw_support esp_lcd esp_local_ctrl esp_netif esp_partition esp_phy esp_pm esp_psram esp_ringbuf esp_rom esp_system esp_timer esp_wifi espcoredump esptool_py fatfs freertos hal heap http_parser idf_test ieee802154 json lcd led_strip log lwip mbedtls mqtt newlib nvs_flash openthread partition_table perfmon protobuf-c protocomm pthread sdmmc soc spi_flash spiffs src tcp_transport touch_element ulp unity usb vfs wear_levelling wifi_provisioning wpa_supplicant xtensa
-- Component paths: /home/rgrizzell/tinyuf2/lib/esp-idf/components/app_trace /home/rgrizzell/tinyuf2/lib/esp-idf/components/app_update /home/rgrizzell/tinyuf2/ports/espressif/boards /home/rgrizzell/tinyuf2/ports/espressif/components/bootloader /home/rgrizzell/tinyuf2/lib/esp-idf/components/bootloader_support /home/rgrizzell/tinyuf2/lib/esp-idf/components/bt /home/rgrizzell/tinyuf2/lib/esp-idf/components/cmock /home/rgrizzell/tinyuf2/lib/esp-idf/components/console /home/rgrizzell/tinyuf2/lib/esp-idf/components/cxx /home/rgrizzell/tinyuf2/lib/esp-idf/components/driver /home/rgrizzell/tinyuf2/lib/esp-idf/components/efuse /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp-tls /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_adc /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_app_format /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_common /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_eth /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_event /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_gdbstub /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_hid /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_http_client /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_http_server /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_https_ota /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_https_server /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_hw_support /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_lcd /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_local_ctrl /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_netif /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_partition /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_phy /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_pm /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_psram /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_ringbuf /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_rom /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_system /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_timer /home/rgrizzell/tinyuf2/lib/esp-idf/components/esp_wifi /home/rgrizzell/tinyuf2/lib/esp-idf/components/espcoredump /home/rgrizzell/tinyuf2/lib/esp-idf/components/esptool_py /home/rgrizzell/tinyuf2/lib/esp-idf/components/fatfs /home/rgrizzell/tinyuf2/lib/esp-idf/components/freertos /home/rgrizzell/tinyuf2/lib/esp-idf/components/hal /home/rgrizzell/tinyuf2/lib/esp-idf/components/heap /home/rgrizzell/tinyuf2/lib/esp-idf/components/http_parser /home/rgrizzell/tinyuf2/lib/esp-idf/components/idf_test /home/rgrizzell/tinyuf2/lib/esp-idf/components/ieee802154 /home/rgrizzell/tinyuf2/lib/esp-idf/components/json /home/rgrizzell/tinyuf2/ports/espressif/components/lcd /home/rgrizzell/tinyuf2/ports/espressif/components/led_strip /home/rgrizzell/tinyuf2/lib/esp-idf/components/log /home/rgrizzell/tinyuf2/lib/esp-idf/components/lwip /home/rgrizzell/tinyuf2/lib/esp-idf/components/mbedtls /home/rgrizzell/tinyuf2/lib/esp-idf/components/mqtt /home/rgrizzell/tinyuf2/lib/esp-idf/components/newlib /home/rgrizzell/tinyuf2/lib/esp-idf/components/nvs_flash /home/rgrizzell/tinyuf2/lib/esp-idf/components/openthread /home/rgrizzell/tinyuf2/lib/esp-idf/components/partition_table /home/rgrizzell/tinyuf2/lib/esp-idf/components/perfmon /home/rgrizzell/tinyuf2/lib/esp-idf/components/protobuf-c /home/rgrizzell/tinyuf2/lib/esp-idf/components/protocomm /home/rgrizzell/tinyuf2/lib/esp-idf/components/pthread /home/rgrizzell/tinyuf2/lib/esp-idf/components/sdmmc /home/rgrizzell/tinyuf2/lib/esp-idf/components/soc /home/rgrizzell/tinyuf2/lib/esp-idf/components/spi_flash /home/rgrizzell/tinyuf2/lib/esp-idf/components/spiffs /home/rgrizzell/tinyuf2/src /home/rgrizzell/tinyuf2/lib/esp-idf/components/tcp_transport /home/rgrizzell/tinyuf2/lib/esp-idf/components/touch_element /home/rgrizzell/tinyuf2/lib/esp-idf/components/ulp /home/rgrizzell/tinyuf2/lib/esp-idf/components/unity /home/rgrizzell/tinyuf2/lib/esp-idf/components/usb /home/rgrizzell/tinyuf2/lib/esp-idf/components/vfs /home/rgrizzell/tinyuf2/lib/esp-idf/components/wear_levelling /home/rgrizzell/tinyuf2/lib/esp-idf/components/wifi_provisioning /home/rgrizzell/tinyuf2/lib/esp-idf/components/wpa_supplicant /home/rgrizzell/tinyuf2/lib/esp-idf/components/xtensa
-- Configuring done
-- Generating done
-- Build files have been written to: /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1
Running ninja in directory /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1
Executing "ninja all"...
[28/917] Generating ../../partition_table/partition-table.binPartition table binary generated. Contents:
*******************************************************************************
# ESP-IDF Partition Table
# Name, Type, SubType, Offset, Size, Flags
nvs,data,nvs,0x9000,20K,
otadata,data,ota,0xe000,8K,
ota_0,app,ota_0,0x10000,2M,
ota_1,app,ota_1,0x210000,2M,
uf2,app,factory,0x410000,256K,
ffat,data,fat,0x450000,28352K,
*******************************************************************************
[398/917] Performing configure step for 'bootloader'FAILED: bootloader-prefix/src/bootloader-stamp/bootloader-configure /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1/bootloader-prefix/src/bootloader-stamp/bootloader-configure
cd /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1/bootloader && /usr/bin/cmake -DSDKCONFIG=/home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1/sdkconfig -DIDF_PATH=/home/rgrizzell/tinyuf2/lib/esp-idf -DIDF_TARGET=esp32s3 -DPYTHON_DEPS_CHECKED=1 -DPYTHON=/home/rgrizzell/.espressif/python_env/idf5.0_py3.10_env/bin/python -DEXTRA_COMPONENT_DIRS=/home/rgrizzell/tinyuf2/ports/espressif/components/bootloader -DPROJECT_SOURCE_DIR=/home/rgrizzell/tinyuf2/ports/espressif -DBOARD=espressif_esp32s3_devkitc_1-1 -DLEGACY_INCLUDE_COMMON_HEADERS= -GNinja /home/rgrizzell/tinyuf2/ports/espressif/components/bootloader/subproject && /usr/bin/cmake -E touch /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1/bootloader-prefix/src/bootloader-stamp/bootloader-configure
-- Found Git: /usr/bin/git (found version "2.34.1")
CMake Error at /home/rgrizzell/tinyuf2/lib/esp-idf/tools/cmake/project.cmake:243 (message):
  Directory specified in EXTRA_COMPONENT_DIRS doesn't exist:
  /home/rgrizzell/tinyuf2/ports/espressif/bootloader_components
Call Stack (most recent call first):
  /home/rgrizzell/tinyuf2/lib/esp-idf/tools/cmake/project.cmake:327 (__project_init)
  CMakeLists.txt:59 (project)

-- Configuring incomplete, errors occurred!
[431/917] Building CXX object esp-idf/nvs_flash/CMakeFiles/__idf_nvs_flash.dir/src/nvs_storage.cpp.objninja: build stopped: subcommand failed.
ninja failed with exit code 1, output of the command is in the /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1/log/idf_py_stderr_output_799291 and /home/rgrizzell/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1-1/log/idf_py_stdout_output_799291
make: *** [Makefile:31: all] Error 2

At this point, it seems there are some breaking changes between ESP-IDF v4.4 and v5.0.

Migrating to V5.0 would be the best but also the most effort in my opinion. In the meanwhile I contacted espressif support directly, hopefully they can help us out!

I don't have any unexpected maker boards to test this with. Can you confirm this issue on one of Adafruit or Espressif following boards:

'adafruit_feather_esp32s3'
'adafruit_feather_esp32s3_nopsram'
'adafruit_feather_esp32s3_reverse_tft'
'adafruit_feather_esp32s3_tft'
'adafruit_qtpy_esp32s3'
'espressif_esp32s3_box'
'espressif_esp32s3_devkitc_1'
'espressif_esp32s3_devkitm_1'

I have built tinyuf2 for the espressif_esp32s3_box from master and it does work.

I changed the sdkconfig.defaults file as follows
# Compatibility options
#CONFIG_FLASHMODE_QIO=y
CONFIG_FLASHMODE_DIO=y

And built for the espressif_esp32s3_devkitc_1 and the unexpectedmaker_feathers3 and both worked.
I don't have time tonight to further test and i have made a lot of test changes. Will relclone the repository tomorrow and see if this all still works.

@skieast it was reported earlier that there is nothing wrong with self-hosted builds.
The original issue report is about regression of Actions build since November 15th.
https://github.com/adafruit/tinyuf2/actions/runs/3469908233
The build deploys certain 'artefacts' that don't boot on an actual ESP32-Sx hardware.

I don't have any unexpected maker boards to test this with. Can you confirm this issue on one of Adafruit or Espressif following boards:

'adafruit_feather_esp32s3'
'adafruit_feather_esp32s3_nopsram'
'adafruit_feather_esp32s3_tft'
'adafruit_qtpy_esp32s3'
'espressif_esp32s3_devkitc_1'
'espressif_esp32s3_devkitm_1'

@hathach in order to reproduce the issue, please, try to boot a firmware binary from 'Artifacts' section of this page: https://github.com/adafruit/tinyuf2/actions/runs/3469908233
on any of the boards from your list.

@skieast it was reported earlier that there is nothing wrong with self-hosted builds.
The original issue report is about regression of Actions build since November 15th. https://github.com/adafruit/tinyuf2/actions/runs/3469908233 The build deploys certain 'artifacts' that don't boot on an actual ESP32-Sx hardware.

Don't think this is the same issue as the one you are referencing.  I only use self-hosted builds and can confirm that building for some esp32s3 boards does not work and results in a bootloop. Changing the flashmode in sdkconfig to DIO for the builds in question appears to fix this. I had planned to look at this again today to confirm.  I have several of the boards in question so can test.

Just recloned the repository, rebooted my laptop and did builds for the espressif_esp32s3_box,  espressif_esp32s3_devkitc_1 (32mb flash), unexpectedmaker_tinys3, and unexpectedmaker_feathers3 . All flashed and booted with an enumerated drive. Using Linux to build and test.  I had an issue with the espressif_esp32s3_devkitc_1 but I bvelieve that was due to the 32mb flash and that its octal. Changing the sdkconfig file to include the line
CONFIG_FLASHMODE_DIO=y
for that board fixed that.  So can't see what the original issues was. Or why it didnt work for me when i first tried it.

CONFIG_FLASHMODE_DIO=y did not help for me, it still bootloops on the TinyS3 compatible targets... (Build using GitHub Actions, idf:release_v4.4)

Just recloned the repository, rebooted my laptop and did builds for the espressif_esp32s3_box, espressif_esp32s3_devkitc_1 (32mb flash), unexpectedmaker_tinys3, and unexpectedmaker_feathers3 . All flashed and booted with an enumerated drive. Using Linux to build and test. I had an issue with the espressif_esp32s3_devkitc_1 but I bvelieve that was due to the 32mb flash and that its octal. Changing the sdkconfig file to include the line CONFIG_FLASHMODE_DIO=y for that board fixed that. So can't see what the original issues was. Or why it didnt work for me when i first tried it.

This worked for me! 👍🏼
make BOARD=espressif_esp32s3_devkitc_1 all
make BOARD=espressif_esp32s3_devkitc_1 flash
Output
idf.py -B_build/espressif_esp32s3_devkitc_1 -DBOARD=espressif_esp32s3_devkitc_1  flash
Executing action: flash
Serial port /dev/ttyUSB0
/dev/ttyUSB0 failed to connect: [Errno 16] could not open port /dev/ttyUSB0: [Errno 16] Device or resource busy: '/dev/ttyUSB0'
Serial port /dev/ttyACM0
Connecting...
Detecting chip type... ESP32-S3
Running ninja in directory /home/rwgrizzell/Projects/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1
Executing "ninja flash"...
[1/5] cd /home/rwgrizzell/Projects/tinyuf2/ports/espressif/_build/esp...inyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1/tinyuf2.bin
tinyuf2.bin binary size 0x24420 bytes. Smallest app partition is 0x40000 bytes. 0x1bbe0 bytes (43%) free.
[2/5] Performing build step for 'bootloader'
[1/1] cd /home/rwgrizzell/Projects/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1/bootloader/esp-idf/esptool_py && /home/rwgrizzell/.espressif/python_env/idf4.4_py3.10_env/bin/python /home/rwgrizzell/Projects/tinyuf2/lib/esp-idf/components/partition_table/check_sizes.py --offset 0x8000 bootloader 0x0 /home/rwgrizzell/Projects/tinyuf2/ports/espressif/_build/espressif_esp32s3_devkitc_1/bootloader/bootloader.bin
Bootloader binary size 0x4ec0 bytes. 0x3140 bytes (38%) free.
[2/3] cd /home/rwgrizzell/Projects/tinyuf2/lib/esp-idf/components/esp...jects/tinyuf2/lib/esp-idf/components/esptool_py/run_serial_tool.cmake
esptool.py esp32s3 -p /dev/ttyACM0 -b 460800 --before=default_reset --after=hard_reset write_flash --flash_mode dio --flash_freq 80m --flash_size 8MB 0x0 bootloader/bootloader.bin 0x410000 tinyuf2.bin 0x8000 partition_table/partition-table.bin 0xe000 ota_data_initial.bin
esptool.py v3.2-dev
Serial port /dev/ttyACM0
Connecting...
Chip is ESP32-S3
Features: WiFi, BLE
Crystal is 40MHz
MAC: 68:b6:b3:3d:7a:88
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Flash will be erased from 0x00000000 to 0x00004fff...
Flash will be erased from 0x00410000 to 0x00434fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Compressed 20160 bytes to 12799...
Writing at 0x00000000... (100 %)
Wrote 20160 bytes (12799 compressed) at 0x00000000 in 0.2 seconds (effective 726.4 kbit/s)...
Hash of data verified.
Compressed 148512 bytes to 94405...
Writing at 0x00410000... (16 %)
Writing at 0x00418a3c... (33 %)
Writing at 0x0041e12f... (50 %)
Writing at 0x00424fac... (66 %)
Writing at 0x0042ac5b... (83 %)
Writing at 0x0043012e... (100 %)
Wrote 148512 bytes (94405 compressed) at 0x00410000 in 1.2 seconds (effective 1032.2 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 136...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (136 compressed) at 0x00008000 in 0.0 seconds (effective 770.3 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 31...
Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (31 compressed) at 0x0000e000 in 0.1 seconds (effective 1019.1 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
Done

I've got full use of the 32MB of flash. 💯
$ df -h /media/rwgrizzell/S3DKC1BOOT/
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda         32M  4.1M   28M  13% /media/rgrizzell/S3DKC1BOOT

At this point I feel comfortable enough to say that issues with the ESP32-S3-DevKitC-1-N16R8V and ESP32-S3-DevKitC-1-N32R8V are separate from the reportedly broken builds in this thread.

At this point I feel comfortable enough to say that issues with the ESP32-S3-DevKitC-1-N16R8V and ESP32-S3-DevKitC-1-N32R8V are separate from the reportedly broken builds in this thread.

Agreed.

I don't have any unexpected maker boards to test this with. Can you confirm this issue on one of Adafruit or Espressif following boards:

'adafruit_feather_esp32s3'
'adafruit_feather_esp32s3_nopsram'
'adafruit_feather_esp32s3_tft'
'adafruit_qtpy_esp32s3'
'espressif_esp32s3_devkitc_1'
'espressif_esp32s3_devkitm_1'

@hathach in order to reproduce the issue, please, try to boot a firmware binary from 'Artifacts' section of this page: https://github.com/adafruit/tinyuf2/actions/runs/3469908233 on any of the boards from your list.

so far, this issue is only reproduced on tinyS3 board. I haven't seen any one confirmed it with one of above list yet.

I think the issue may be with the docker image of the esp-idf being used
run: docker run --rm -v $PWD:/project -w /project espressif/idf:release-v4.4  /bin/bash -c "git config --global --add safe.directory /project && make -C ports/espressif/ BOARD=${{ matrix.board }} all self-update copy-artifact"

When i try to build locally using the current release-v4.4 for the TinyS3 it does not work.
If I build locally using the version of esp-idf included in the tinyuf2 repository it does work.

So I built a new docker image for the esp-idf that uses the correct commit. Modified my fork to use this docker image.  The artifacts for the tinys3 and feathers3 both enumerate now.  I did not test any other boards.
Docker hub repo, image is v4.4-tinyuf2 : https://hub.docker.com/repository/docker/6lhasacoi/idf-custom
Fork and branch to use this image: https://github.com/skieast/tinyuf2/tree/test-workflow
Artifacts from last push: https://github.com/skieast/tinyuf2/actions/runs/3783255645
I have almost no knowledge of docker but managed to get something that worked.

@skieast thank you for your effort creating the custom docker image, I just tested it and it works for my custom (TinyS3 compatible) esp32s3 boards! What next? Should we try to convince espressif to host this image on their official docker hub? Maybe adafruit?

@SukuWc thanks for trying this and confirming that it works, at least for you and me, Now it's up to @hathach to decide on how to proceed. If this is the route to follow (custom docker image) then on some official docker hub repository I think.  Or someone can find out why the 4.4 release bootloops with the esp32s3.

I also looked briefly at hosting the image at Github Packages repository which supports Docker images (amongst others). I didn't get all the permissions right to push my local image but it should work.  This would then allow the idf-custom Docker image to be hosted in the github tinyuf2 reposity. Or maybe its the adafruit account. Smarter brains will know.
https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry

Custom docker image will not be accepted. If docker image is the issue, you should report it to espressif for them to fix. If it is the tinyuf2 we should fix it here. Though I don't have the boards with this issue, therefore pr is welcome

It's an image created using espressif tools designed to get an image at a defined commit.  In this case the esp-idf in the tinyuf2 repository is at commit bbe2a1bf34.   The docker idf image used in the github workflow is v4.4. This image changes as espressif updates that version.  So you will get times where it may work depending on what espressif has committed to that image.
In any case thanks for looking at the research.

I have tested modifying the .github/workflows/build_esp32.yml to use the espressif/idf:v4.4.3 idf image. In this case the artifacts do enumerate on the boards I tested.
unexpectedmaker_feathers3
unexpectedmaker_tinys3
espressif_esp32s3_box

The artifacts I pulled from the master branch built a week ago did not work on the above board.
Perhaps this is an acceptable solution.
 git diff master                                                                          Mon Jan  2 17:09:50 2023
diff --git a/.github/workflows/build_esp32.yml b/.github/workflows/build_esp32.yml
index e14093db..18cdf7a7 100644
--- a/.github/workflows/build_esp32.yml
+++ b/.github/workflows/build_esp32.yml
@@ -99,7 +99,7 @@ jobs:
       run: echo BIN_PATH=ports/espressif/_bin/${{ matrix.board }} >> $GITHUB_ENV

     - name: Build
-      run: docker run --rm -v $PWD:/project -w /project espressif/idf:release-v4.4  /bin/bash -c "git config --global --add safe.directory /project && make -C ports/espressif/ BOARD=${{ matrix.board }} all self-update copy-artifact"
+      run: docker run --rm -v $PWD:/project -w /project espressif/idf:v4.4.3  /bin/bash -c "git config --global --add safe.directory /project && make -C ports/espressif/ BOARD=${{ matrix.board }} all self-update copy-artifact"

     - uses: actions/upload-artifact@v3
       with:

thank you @skieast for testing this out, temporarily switch to v4.4.3 (released 2 months ago), seems like the latest v4.4 (released 2 weeks ago) indeed is the troublesome one.

I have release 0.12.0 please try it out to see if that works for you.


Make the --key argument optional

The refactoring work in commit 72eaa85ebe15d3953f697476a592d9b0d94d5662
reverted the recent change to the --key argument and made it a required
argument.  Make --key a hidden, optional argument again.

That's a good point.  I'll do that now.

Closing and reopening a new pull request that makes both arguments hidden.


Emulator: PANIC: Broken AVD system path. Check your ANDROID_SDK_ROOT value [C:\android]!

Hi. I'm trying to open emulator on android studio.
but somehow it isn't working...
오후 9:28	* daemon not running; starting now at tcp:5037
오후 9:28	* daemon started successfully
오후 9:28	Emulator: PANIC: Broken AVD system path. Check your ANDROID_SDK_ROOT value [C:\android]!
오후 9:28	Emulator: Process finished with exit code 1
This is what I got from event log

Logs
C:\Users\김수영>echo $ANDROID_HOME
$ANDROID_HOME

C:\Users\김수영>flutter emulators --create --name Pixel-test
Emulator 'Pixel-test' created successfully.

C:\Users\김수영>flutter emulators --launch Pixel-test

Sending crash report to Google.
Crash report sent (report ID:<PHONE_NUMBER>c0a82a)
Oops; flutter has exited unexpectedly.

Crash report written to C:\Users\김수영\flutter_01.log;
please let us know at https://github.com/flutter/flutter/issues.

#0      RunResult.throwException (package:flutter_tools/src/base/process.dart:141:5)
#1      _DefaultProcessUtils.run (package:flutter_tools/src/base/process.dart:275:19)
<asynchronous suspension>
#2      AndroidEmulator.launch (package:flutter_tools/src/android/android_emulator.dart:52:52)
#3      EmulatorsCommand._launchEmulator (package:flutter_tools/src/commands/emulators.dart:74:31)
<asynchronous suspension>
#4      EmulatorsCommand.runCommand (package:flutter_tools/src/commands/emulators.dart:47:13)
#5      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:615:18)
#6      _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:73:64)
#7      _rootRunUnary (dart:async/zone.dart:1134:38)
#8      _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#9      _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#10     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#11     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#12     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#13     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:554:7)
#14     _rootRun (dart:async/zone.dart:1126:13)
#15     _CustomZone.run (dart:async/zone.dart:1023:19)
#16     _CustomZone.runGuarded (dart:async/zone.dart:925:7)
#17     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:965:23)
#18     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#19     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#20     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#21     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:175:5)

C:\Users\김수영>echo $ANDROID_HOME && flutter doctor -v
$ANDROID_HOME
[√] Flutter (Channel stable, v1.12.13+hotfix.5, on Microsoft Windows [Version 10.0.18362.535], locale ko-KR)
    • Flutter version 1.12.13+hotfix.5 at C:\Users\김수영\flutter
    • Framework revision 27321ebbad (10 days ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\android
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = C:\android
    • ANDROID_SDK_ROOT = C:\android
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 42.1.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] VS Code (version 1.41.1)
    • VS Code at C:\Users\김수영\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.7.1

[!] Connected device
    ! No devices available

flutter_01.log
This is log file from crash report

Try to recreate an other avd and retry to launch it...

@JonathanMonga
you mean create another one in avd manager?
it isn't working either....

Hi @sy8044
the emulator doesn't show up in your doctor either,
could you please double-check the steps to create an emulator in the docs
thank you

@sy8044 : I had the same issue on Mac and fixed it by correcting the ANDROID_HOME environment variable. Correcting ANDROID_SDK_ROOT environment variable won't fix the problem so this seems to be a bug in Android's error messaging.
This ANDROID_HOME fix was originally suggested by https://blog.csdn.net/qq_44257240/article/details/99060873.


react-field-toggle sample - Updated to v. 1.3.0

Q
A

Bug fix?
no

New feature?
no

New sample?
no

Related issues?
no

What's in this Pull Request?
Updated the react-field-toggle sample to v. 1.3.0

thx Giuliano, appreciated.


[Docs] Replace UI screenshots in Prototype Implementation Page

Describe your problem(s)
The screenshots in "Creating a Prototype API with Mock Payload Generated Inline Scripts" doc page are outdated and should be replaced with the screenshots taken from the new UIs.
Doc link - https://apim.docs.wso2.com/en/4.0.0-dev/design/prototype-api/create-a-mock-api-with-an-inline-script/

The inline scripts provided in the doc are also outdated. We need to update them too.
The instructions to modify the inline scripts are not clear enough (not clear what part to replace) in 6 and 7 points in Step 1. Need reword them clearly mentioning which parts to be replaced and which parts to be kept. It's good to provide a complete example with the full script without editing and after manually editing.
https://apim.docs.wso2.com/en/4.0.0-dev/design/prototype-api/create-a-mock-api-with-an-inline-script/#step-1-create-a-prototype-api-with-mock-response-payloads


Feature/no mimic assign

improve distrib mule ship-specific debug log filename
add assignSrc param to travel mule to allow him to work without being assigned
hardcode assignSrc=false in order.assist.xml (mimic patch)

@Vectorial1024 this change in conjunction with the other PR merged today adds a new assignSrc param to both travel and distrib mule compared to the currently released versions

addresses #143 and #141

Aight, will check them out this weekend. Will also make it such that assignSrc is false when ppl are assigning to other ships to form CivFleets, in line with the other PRs.


fix: typo in engine save

Nice ODM! I noticed a copy paste typo in the AIOEngine.save and SyncEngine.save methods which is fixed in this PR.

Closing due to inactivity


Enhance usage instructions for API

In the View API backend page, there is a "View usage instructions" button. Pressing the button opens the following instructions:
"Make API calls to:
[automatically filled request URL]
Note: you may need to use your API Key, found on your profile page."
Based on feedback through the APIKA support channel, there is a need to enhance these instructions.
Optimally, the instructions should include the parameter of using API key (api_key) in the request coupled with the user's actual API key.
As a minimum, the instruction could include how to use API key in request (i.e. the parameter api_key).
Refer also to bug report #606.

Verified on latest develop version.
Still have issue while calling API. Usage instructions could be more explanatory, providing URL that includes user API key.
Reported bugs:
https://github.com/apinf/api-umbrella-dashboard/issues/606
https://github.com/apinf/api-umbrella-dashboard/issues/758

@frenchbread Will you take this task? Brylie can give you some guidance, if needed.

@bajiat Self-assigned

PR #801.
Looks like:


Update dependency to polkadot-v0.9.26 branch

As topic, upstream was updated to v0.9.26.

https://github.com/litentry/tee-worker/pull/10
solved.


Set to max extent of child?

Is there a way to set the max extent of the bottom sheet to the height of the child?

This is the issue I'm hoping to address with your package https://github.com/flutter/flutter/issues/41599.


<EMAIL_ADDRESS>decompress error

❯ scoop update; scoop cache rm picpick;
Updating Scoop...
Updating 'extras' bucket...
Updating 'java' bucket...
Updating 'main' bucket...
Updating 'nerd-fonts' bucket...
Scoop was updated successfully!
Deleted: 0 files, 0 B
❯ scoop install picpick
WARN  Scoop uses 'aria2c' for multi-connection downloads.
WARN  Should it cause issues, run 'scoop config aria2-enabled false' to disable it.
WARN  To disable this warning, run 'scoop config aria2-warning-enabled false'.
Installing 'picpick' (7.2.5) [64bit] from extras bucket
Starting download with aria2 ...
Download: Download Results:
Download: gid   |stat|avg speed  |path/URI
Download: ======+====+===========+=======================================================
Download: 067286|OK  |   2.2MiB/s|D:/scoop/cache/picpick#7.2.5#https_www.picpick.org_releases_7.2.5_picpick_portable.zip
Download: Status Legend:
Download: (OK):download completed.
Checking hash of picpick_portable.zip ... ok.
Extracting picpick_portable.zip ... ERROR Exit code was 2!
Failed to extract files from D:\scoop\apps\picpick\7.2.5\picpick_portable.zip.
Log file:
D:\scoop\apps\picpick\7.2.5\7zip.log
Please try again or create a new issue by using the following link and paste your console output:
https://github.com/ScoopInstaller/Extras/issues/new?title=picpick%407.2.5%3A+decompress+error

Duplicate of #12287


add march newsletter

Change-type: minor
Signed-off-by: Lizzie Epton<EMAIL_ADDRESS>

@balena-ci I self-certify!


Issues with tasks containing spaces/parentheses/etc

See https://groups.google.com/forum/#!topic/luigi-user/TWwAtynX7Qc
and #125

I'm closing this issue.

[x] It has been inactive for +4 months.
[ ] It's not about luigi core, so not as many users are affected about this.
[ ] The change seems quite big, it's unlikely to be sporadically picked up.
[ ] The owner haven't responded or disappeared.
[ ] I don't understand what this issue is about.
[ ] There exists a reasonable workaround for this.
[ ] We need to check if this hasn't been fixed by now (for old issues).
[ ] This is kind of by design and not a bug.
[ ] Resolving this would probably add a lot of complexity.

Every open issue adds some clutter, and we try to make the issues fewer and make it easier for new collaborators to find. Currently we try to close any issue that meets the first checkbox + one other.
Feel free to reopen this issue at any point if you have the intent to continue to work this. :)

Task names containing spaces/parentheses/etc? I suppose it was in the old days with cowboy serialization. That's fixed now. :)


Location list window may open a wrong file

Describe the bug
Location list window may open a wrong file.
To Reproduce
Detailed steps to reproduce the behavior:

Create 001.txt with the following content
foo
bar
Create 002.txt with the following content
bar
foo
Start vim and run ":lgrep -Hrn foo .", then press Enter to go back to vim
Run ":lopen", switch to the location list window, move cursor to the last location entry and type Enter to open it
Run ":set switchbuf=newtab"
CTRL_W+j to switch to the location list window, move cursor to the first location entry and type Enter to open it in a new tab
Run ":lopen", type Enter to open the first location entry

Expected behavior
Cursor moves back to the first window of the 2nd tab, as it already shows the buffer for the first location entry.
Actual behavior
The 2nd location entry is opened in a new tab.
Environment (please complete the following information):

Vim version: 8.2.3159
OS: Debian 10
Terminal: xfce64-terminal

Analysis done so far
It seems the cause is that copy_loclist() in src/quickfix.c doesn't ensure to_qfl->qt_ptr pointing to the location entry specified by to_qfl->index.

submitted #8566 to solve this issue.


IB Python API

So Interactive Brokers now offers a native Python API:
https://www.interactivebrokers.com.au/en/index.php?f=5061&ns=T&nhf=T
I have a stack of code written for an IBPriceHandler, but nothing yet for IBExecutionHandler. Shall we swap from SWIG based implementation to full python?
Getting off of SWIG means one less dependancy for the testing suite (also the swig implementation needs to be manually installed because of version differences between github & pypi).
PS sorry for disappearing for a while there! Had some burnout to fend off

FWIW - I also spent quite a bit of time playing with the SWIG version.  There are some challenges in copying and using the underlying SWIG objects passed back and forth (Contract, Order, ComboLegs, etc).  I think as you get deeper in using the IB API for trading, getting account data, etc you will benefit from having native python API.
I spent an hour or so going through the code, and it seems they've used the same approach as the other versions.  Not 100% feature complete on version 973 yet, but cursory glance shows all the features on the stable release are available.
If I get a chance to play with it here in near future, will share.  I am glad they have a native python version now.

Will be very interesting for options contracts, as you allude to.
Seems like it might be best to go that way then!

Hi Ryan, good to hear from you again!
I agree with you in that the native client is clearly the way forward. Not having an extra dependency (specifically regarding the version differences you mention above) would also be beneficial.
I made some suggestions regarding the implementation on the Slack #general channel this morning - let me know what you think.
Mike.

Closing as work has been started on a pull request


whisper caveats file

http://localhost:8080/HapiServer/hapi/info?id=C3_CQ_WHI_CAVEATS
returns no timetags, but instead a time range.

I've made it so that the start time of the time range is used.  This will probably change.


fix(deps): update terraform ibm to latest for the da solution

This PR contains the following updates:

Package
Type
Update
Change

ibm (source)
required_provider
minor
1.62.0 -> 1.63.0

Release Notes

IBM-Cloud/terraform-provider-ibm (ibm)
v1.63.0
Compare Source
Features

Support for Virtual Private Cloud

Datasources

ibm_is_reservation
ibm_is_bare_metal_server_network_attachment
ibm_is_bare_metal_server_network_attachments
ibm_is_instance_network_attachment
ibm_is_instance_network_attachments
ibm_is_virtual_network_interface_floating_ip
ibm_is_virtual_network_interface_floating_ips
ibm_is_virtual_network_interface_ip
ibm_is_virtual_network_interface_ips

Resources

ibm_is_reservation
ibm_is_reservation_activate
ibm_is_bare_metal_server_network_attachment
ibm_is_instance_network_attachment
ibm_is_virtual_network_interface
ibm_is_virtual_network_interface_floating_ip
ibm_is_virtual_network_interface_ip

Support for Power Instance

Datasources

ibm_pi_instance_snapshot

Support for Event Notification

Datasources

ibm_en_email_template
ibm_en_email_templates
ibm_en_destination_custom_sms
ibm_en_subscription_custom_sms
ibm_en_integration_cos

Resources

ibm_en_email_template
ibm_en_destination_custom_sms
ibm_en_subscription_custom_sms
ibm_en_integration_cos

Enhancements

Added new region eu-fr2 (5073)
Update Forcenew instance fields (5025)
Event Notifications: enabled private endpoint (4989)
Adding OpenPages as part of UX030 (5051)
add vpe_service_endpoint_url output (5129)
Remove old deprecated features from terraform (5049)
Remove deprecated Secrets Manager data sources (5126)
Add Power VMRM (4994)
Remove references for creating free clusters, no longer supported (4987)
fix: CIS - added deafult value for min_tls_version (5136)
fix: add vpe_service_endpoint_url output (5129)
Secrets manager custom password generation policy (5134)
deprecate(is-lb-listener-redirect): Deprecate lb listener https redirect (5140)
Support for virtual network interfaces across instance, bare metal servers, instance templates, shares (5112)
new feature "monitoring_enabled" for Project service (5120)
feat(Catalog Management): update platform go sdk version, remove old catalog fields (5145)
SCC eu-es update (5135)
handle host_id in waitForHostAttachment (5152)
Add IBMi Software License field to power instance (5082)
Add CRN attribute to power workspace (5107)
fix(IAM Policy Management): Update check for authorization policy subject (5144)
Remove CF auth to avoid delay of 60s for nothing (5162)
adds tags support for is_ssh_key(s) datasource (5175)
Added support for identifier in ibm_resource_instance (5147)

BugFixes

Fix Satellite Locations recreation when updating, remove forcenew, add computed and applyonce
(5090)
updated is_images document (5088)
reordered reservation on instance to avoid update and length check on templates (5141)
fix(share-operations) : File shares operations and doc fixes (5139)
Satellite Storage API Fix and Updated ODF Documentation (5143)
fix(bare metal server) : fixed allow to float and ips issue (5146)
fix(lb-and-routing-table) : Fix routing table and lbs datasource (5149)
unable to perform plan/apply after a project config is approved or deployed (5158)
OpenShift Data Foundation Example Fix (5157)
Add detach volumes in docs (5128)
fix docs and added force new on vni (5156)
Fix the spelling of IBM i in documentation and strings (5171)
Fix handling of service credentials secrets in secrets list data source (5173)
fix(Catalog Management): fix cm validation resource panic (5172)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

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

GitHub release
v1.1.10

Your semantic-release bot :package::rocket: