Integrate EIA 923 ER

Overview
Closes #3677.
What problem does this address?
Adds the new EIA 923 ER data.
What did you change?
1. Added the DOI for the new data.
2. Updated all the package_data files to reflect the ER data files.
3. Fixed a quirk in the core_eia923__monthly_generation_fuel_nuclear table that was causing the out_eia923__generation_fuel_combined table to fail
ValueError: Found inhomogeneous non-data cols while aggregating nuclear generation. Non-data cols: ['fuel_type_code_aer', 'fuel_type_code_pudl', 'data_maturity']

The failure was caused byNone values in the fuel_type_code_aer column in the core_eia923__monthly_generation_fuel_nuclear table. This was tripping a ValueError in the creation of the out_eia923__generation_fuel_combined table:
gfn_gb = core_eia923__monthly_generation_fuel_nuclear.groupby(primary_key)
# Ensure that all non-data columns are homogeneous within groups
if gfn_gb[non_data_cols].nunique().ne(1).any(axis=None):
    raise ValueError(
        "Found inhomogeneous non-data cols while aggregating nuclear generation. "
        f"Non-data cols: {non_data_cols}"
    )

I added a line to the transform function for core_eia923__monthly_generation_fuel_nuclear that converted any None values to NUC (so long as the energy_source_code was NUC) and that fixed the problem.
4. Update min-max rows validation test.
There are some newly harvested plant_id-year combos that add rows to the plants_eia860 and boil_eia860 tables.
5. Update release notes.
Testing
How did you make sure this worked? How can a reviewer verify this?
# To-do list
- [x] If updating analyses or data processing functions: make sure to update or write data validation tests (e.g.,  `test_minmax_rows()`)
- [x] Update the [release notes](../docs/release_notes.rst): reference the PR and related issues.
- [ ] Ensure docs build, unit & integration tests, and test coverage pass locally with `make pytest-coverage` (otherwise the merge queue may reject your PR)
- [x] Review the PR yourself and call out any questions or issues you have
- [x] For minor ETL changes or data additions, once `make pytest-coverage` passes, make sure you have a fresh full PUDL DB downloaded locally, materialize new/changed assets and all their downstream assets and [run relevant data validation tests](https://catalystcoop-pudl.readthedocs.io/en/latest/dev/testing.html#data-validation) using `pytest` and `--live-dbs`.
- [ ] For significant ETL, data coverage or analysis changes, once `make pytest-coverage` passes, ensure the full ETL runs locally and [run data validation tests](https://catalystcoop-pudl.readthedocs.io/en/latest/dev/testing.html#data-validation) using `make pytest-validate` (a ~10 hour run). If you can't run this locally, run the `build-deploy-pudl` GitHub Action (or ask someone with permissions to). Then, check the logs on the `#pudl-deployments` Slack channel or `gs://builds.catalyst.coop`.

Getting a foreign key failure and I'm bad at debugging them so soliciting advice from @e-belfer
Ran pytest test/integration --live-dbs
FAILED test/integration/etl_test.py::test_pudl_engine - pudl.etl.check_foreign_keys.ForeignKeyErrors: Foreign key error for table: _out_eia__yearly_generators -- core_eia860__scd_generators (plant_id_eia, gener...
FAILED test/integration/record_linkage_test.py::test_classify_plants_ferc1 - mlflow.exceptions.MlflowException: Detected out-of-date database schema (found version 867495a8f9d4, but expected 5b0e9adcef9c).

        The order assets are loaded into the database will not satisfy foreign key
        constraints so we can't enable foreign key constraints. However, we can
        check for foreign key failures once all of the data has been loaded into
        the database using the `foreign_key_check` and `foreign_key_list` PRAGMAs.

        You can learn more about the PRAGMAs in the `SQLite docs
        <https://www.sqlite.org/pragma.html#pragma_foreign_key_check>`__.

        Raises:
            ForeignKeyErrors: if data in the database violate foreign key constraints.
        """
        logger.info(f"Running foreign key check on {engine.url} database.")
        with engine.begin() as con:
            fk_errors = pd.read_sql_query("PRAGMA foreign_key_check;", con)

        if not fk_errors.empty:
            # Merge in the actual FK descriptions
            tables_with_fk_errors = fk_errors.table.unique().tolist()
            table_foreign_keys = pd.concat(
                [_get_fk_list(engine, table) for table in tables_with_fk_errors]
            )

            fk_errors_with_keys = fk_errors.merge(
                table_foreign_keys,
                how="left",
                on=["parent", "fkid", "table"],
                validate="m:1",
            )

            errors = []
            # For each foreign key error, raise a ForeignKeyError
            for (
                table_name,
                parent_name,
                parent_fk,
            ), parent_fk_df in fk_errors_with_keys.groupby(["table", "parent", "fk"]):
                errors.append(
                    ForeignKeyError(
                        child_table=table_name,
                        parent_table=parent_name,
                        foreign_key=parent_fk,
                        rowids=parent_fk_df["rowid"].values,
                    )
                )
>           raise ForeignKeyErrors(errors)
E           pudl.etl.check_foreign_keys.ForeignKeyErrors: Foreign key error for table: _out_eia__yearly_generators -- core_eia860__scd_generators (plant_id_eia, generator_id, report_date) -- on rows [551972<PHONE_NUMBER>42]
E
E           Foreign key error for table: out_eia923__boiler_fuel -- core_eia__entity_boilers (plant_id_eia, boiler_id) -- on rows [1623953 1623954 1623955 1623956 1623957 1623958 1623959 1623960 1623961
E            1623962 1623963 1623964 1674125 1674126 1674127 1674128 1674129 1674130
E            1674131 1674132 1674133 1674134 1674135 1674136]
E
E           Foreign key error for table: out_eia923__generation -- core_eia__entity_generators (plant_id_eia, generator_id) -- on rows [699155<PHONE_NUMBER>57<PHONE_NUMBER>59<PHONE_NUMBER>61<PHONE_NUMBER>63 699164
E<PHONE_NUMBER>66<PHONE_NUMBER>68<PHONE_NUMBER>70<PHONE_NUMBER>72<PHONE_NUMBER>74
E<PHONE_NUMBER>76<PHONE_NUMBER>78]
E
E           Foreign key error for table: out_eia923__monthly_boiler_fuel -- core_eia__entity_boilers (plant_id_eia, boiler_id) -- on rows [   3277    3278    3279    3280    3281    3282    3283    3284    3285
E               3286    3287    3288 1284764 1284765 1284766 1284767 1284768 1284769
E            1284770 1284771 1284772 1284773 1284774 1284775]
E
E           Foreign key error for table: out_eia923__monthly_generation -- core_eia__entity_generators (plant_id_eia, generator_id) -- on rows [278918<PHONE_NUMBER>20<PHONE_NUMBER>22<PHONE_NUMBER>24<PHONE_NUMBER>26 278927
E<PHONE_NUMBER>29<PHONE_NUMBER>31<PHONE_NUMBER>33<PHONE_NUMBER>35<PHONE_NUMBER>37
E<PHONE_NUMBER>39<PHONE_NUMBER>41]
E
E           Foreign key error for table: out_eia923__yearly_boiler_fuel -- core_eia860__scd_boilers (plant_id_eia, boiler_id, report_date) -- on rows [   255   4514   8238   8248   8724   8734  17623  17633  19272  19282
E             23724  23735  33302  33312  33322  34710  38477  38488  39061  39071
E             39081  39091  39101  39111  49496  51398  51409  52200  52211  52446
E             52720  52932  54028  54038  54048  54058  54172  54182  54791  54801
E             58259  58305  58316  60418  60428  60438  60448  60487  68513  68523
E             68560  68571  68598  68609  70423  70433  70443  70453  71269  71279
E             71289  71299  72062  72073  72916  72927  72967  76523  76533  76543
E             76553  76760  76770  76876  76886  76896  77081  79161  79166  80854
E             80864  80872  80882  80892  81843  82239  82246  82253  82260  84023
E             84034  84072  84083  84223  84234  84245  86620  86858  86869  86880
E             86891  86994  87004  87009  87019  91352  91377  93163  93167  96705
E             96716  96727  96738  96817  96827  96836  96846  96992  97003  99500
E             99511<PHONE_NUMBER>65<PHONE_NUMBER>51<PHONE_NUMBER>14<PHONE_NUMBER>88 104499
E<PHONE_NUMBER>75<PHONE_NUMBER>47<PHONE_NUMBER>66<PHONE_NUMBER>02<PHONE_NUMBER>25
E<PHONE_NUMBER>42<PHONE_NUMBER>11<PHONE_NUMBER>31<PHONE_NUMBER>14<PHONE_NUMBER>95
E<PHONE_NUMBER>13<PHONE_NUMBER>17<PHONE_NUMBER>37<PHONE_NUMBER>30<PHONE_NUMBER>16
E<PHONE_NUMBER>36<PHONE_NUMBER>99<PHONE_NUMBER>09<PHONE_NUMBER>24<PHONE_NUMBER>96
E<PHONE_NUMBER>65<PHONE_NUMBER>23<PHONE_NUMBER>43<PHONE_NUMBER>63<PHONE_NUMBER>65
E<PHONE_NUMBER>25<PHONE_NUMBER>45<PHONE_NUMBER>95<PHONE_NUMBER>56<PHONE_NUMBER>21
E<PHONE_NUMBER>96<PHONE_NUMBER>07<PHONE_NUMBER>24<PHONE_NUMBER>56<PHONE_NUMBER>26
E<PHONE_NUMBER>21<PHONE_NUMBER>15<PHONE_NUMBER>25<PHONE_NUMBER>58<PHONE_NUMBER>68
E<PHONE_NUMBER>04<PHONE_NUMBER>12<PHONE_NUMBER>21<PHONE_NUMBER>34<PHONE_NUMBER>42]
E
E           Foreign key error for table: out_eia923__yearly_generation -- core_eia860__scd_generators (plant_id_eia, generator_id, report_date) -- on rows [57446]
E
E           Foreign key error for table: out_eia__yearly_boilers -- core_eia860__scd_boilers (plant_id_eia, boiler_id, report_date) -- on rows [80129 80327 80513 80535 80922 80990 81153 81553 81554 81555 81604 81818
E            81860 81861 81862 82277 82362 82401 82417 82435 82446 82505 82506 82513
E            82514 82537 82538 82646 82649 82705 82706 82709 82891 82893 82895 82933
E            82934 82935 82936 82965 82966 83000 83044 83045 83163 83164 83174 83175
E            83181 83182 83183 83191 83240 83280 83281 83282 83311 83325 83326 83377
E            83379 83384 83451 83458 83459 83465 83466 83578 83580 83624 83625 83729
E            83730 83734 83735 83740 83741 83836 83837 83883 83886 83915 83940 83941
E            83944 84013 84014 84042 84043 84062 84075 84106 84107 84108 84126 84127
E            84131 84132 84134 84147 84148 84232 84240 84241 84271 84284 84297 84314
E            84315 84500 84505 84506 84566 84567 84568 84569 84570 84571 84572 84580
E            85144 85195 85196 85218 85234 85235 85273 85321 85339 85340 85375 85376
E            85377 85378 85433 85434 85527 85536 85551 85552 85588 85589 85615 85616
E            85617 85752 85753 85754 85765 85766 85767 85768 85769 85770 85771 85772
E            85805 86568 87628]

src/pudl/etl/check_foreign_keys.py:208: ForeignKeyErrors

The mer_fuel_type_code column from the energy_storage table is kind of annoying. It was previously aer_fuel_type_code which stands for Annual Energy Review as opposed to Monthly Energy Review. Im not exactly sure what this means in the context of this table. Maybe it's the fuel type taken from the most recent monthly review? as opposed to annual? I'm tempted to lump it in with the aer_fuel_type_code because it feels silly for them to be separate columns. But, at the same time, it is sort of different?

The mer_fuel_type_code column from the energy_storage and generation_fuel tables is kind of annoying. It was previously aer_fuel_type_code which stands for Annual Energy Review as opposed to Monthly Energy Review. Im not exactly sure what this means in the context of this table. Maybe it's the fuel type taken from the most recent monthly review as opposed to annual review? I'm tempted to lump it in with the aer_fuel_type_codecolumn because it feels silly for them to be separate. But, at the same time, it is sort of different? What do you think?

I was wondering if this is just an ER thing, but it's not. It's because AER has been suspended: https://www.eia.gov/totalenergy/data/annual/
The AER fuel type code from 2022 ER data is defined as this in the EIA metadata:

A partial aggregation of the reported fuel type codes into larger categories used by EIA in, for example, the Annual Energy Review (AER).Two or three letter alphanumeric.  See the Fuel Code table (Table 5), below:

The 2023 MER fuel type code is defined as this in the EIA metadata:

A partial aggregation of the reported fuel type codes into larger categories used by EIA in, for example, the Monthly Energy Review (MER).Two or three letter alphanumeric.  See the Fuel Code table (Table 5), below:

Do you feel confident that the categories themselves haven't changed, and do you know if the fuel type codes in MER and AER are the same? If so, I think we could combine these and just say "in the Monthly Energy Reviews or the former Annual Energy Reviews" in the field description, and possibly consider renaming the column towards mer?

Do you feel confident that the categories themselves haven't changed, and do you know if the fuel type codes in MER and AER are the same? If so, I think we could combine these and just say "in the Monthly Energy Reviews or the former Annual Energy Reviews" in the field description, and possibly consider renaming the column towards mer?

The fuel type codes are the same, and I'm almost positive the categories haven't changed. I'll change the description.

I'm getting a really weird alembic error when I try and upgrade the column names to have the suffix _mer instead of _aer. All is fine until I update the core_eia__codes_fuel_types_aer code table. For some reason when I change that to _mer (there are three instances of that -- one in CODE_METADATA in codes/metadata.py and two in RESOURCE_METADATA in metadata/resources/eia.py.
After I run alembic revision --autogenerate I get the following code:
"""AER to MER x2

Revision ID: 9625b1bd89e3
Revises: 08901b7bc357
Create Date: 2024-07-19 12:12:51.592927

"""
from alembic import op
import sqlalchemy as sa

# revision identifiers, used by Alembic.
revision = '9625b1bd89e3'
down_revision = '08901b7bc357'
branch_labels = None
depends_on = None

def upgrade() -> None:
    # ### commands auto generated by Alembic - please adjust! ###
    op.create_table('core_eia__codes_fuel_types_mer',
    sa.Column('code', sa.Text(), nullable=False, comment='Originally reported short code.'),
    sa.Column('description', sa.Text(), nullable=True, comment='Long human-readable description of the meaning of a code/label.'),
    sa.PrimaryKeyConstraint('code', name=op.f('pk_core_eia__codes_fuel_types_mer'))
    )
    op.drop_table('core_eia__codes_fuel_types_aer')
    with op.batch_alter_table('core_eia923__monthly_generation_fuel', schema=None) as batch_op:
        batch_op.drop_constraint('fk_core_eia923__monthly_generation_fuel_fuel_type_code_mer_core_eia__codes_fuel_types_aer', type_='foreignkey')
        batch_op.create_foreign_key(batch_op.f('fk_core_eia923__monthly_generation_fuel_fuel_type_code_mer_core_eia__codes_fuel_types_mer'), 'core_eia__codes_fuel_types_mer', ['fuel_type_code_mer'], ['code'])

    with op.batch_alter_table('core_eia923__monthly_generation_fuel_nuclear', schema=None) as batch_op:
        batch_op.drop_constraint('fk_core_eia923__monthly_generation_fuel_nuclear_fuel_type_code_mer_core_eia__codes_fuel_types_aer', type_='foreignkey')
        batch_op.create_foreign_key(batch_op.f('fk_core_eia923__monthly_generation_fuel_nuclear_fuel_type_code_mer_core_eia__codes_fuel_types_mer'), 'core_eia__codes_fuel_types_mer', ['fuel_type_code_mer'], ['code'])

    with op.batch_alter_table('out_eia923__generation_fuel_combined', schema=None) as batch_op:
        batch_op.drop_constraint('fk_out_eia923__generation_fuel_combined_fuel_type_code_mer_core_eia__codes_fuel_types_aer', type_='foreignkey')
        batch_op.create_foreign_key(batch_op.f('fk_out_eia923__generation_fuel_combined_fuel_type_code_mer_core_eia__codes_fuel_types_mer'), 'core_eia__codes_fuel_types_mer', ['fuel_type_code_mer'], ['code'])

    # ### end Alembic commands ###

def downgrade() -> None:
    # ### commands auto generated by Alembic - please adjust! ###
    with op.batch_alter_table('out_eia923__generation_fuel_combined', schema=None) as batch_op:
        batch_op.drop_constraint(batch_op.f('fk_out_eia923__generation_fuel_combined_fuel_type_code_mer_core_eia__codes_fuel_types_mer'), type_='foreignkey')
        batch_op.create_foreign_key('fk_out_eia923__generation_fuel_combined_fuel_type_code_mer_core_eia__codes_fuel_types_aer', 'core_eia__codes_fuel_types_aer', ['fuel_type_code_mer'], ['code'])

    with op.batch_alter_table('core_eia923__monthly_generation_fuel_nuclear', schema=None) as batch_op:
        batch_op.drop_constraint(batch_op.f('fk_core_eia923__monthly_generation_fuel_nuclear_fuel_type_code_mer_core_eia__codes_fuel_types_mer'), type_='foreignkey')
        batch_op.create_foreign_key('fk_core_eia923__monthly_generation_fuel_nuclear_fuel_type_code_mer_core_eia__codes_fuel_types_aer', 'core_eia__codes_fuel_types_aer', ['fuel_type_code_mer'], ['code'])

    with op.batch_alter_table('core_eia923__monthly_generation_fuel', schema=None) as batch_op:
        batch_op.drop_constraint(batch_op.f('fk_core_eia923__monthly_generation_fuel_fuel_type_code_mer_core_eia__codes_fuel_types_mer'), type_='foreignkey')
        batch_op.create_foreign_key('fk_core_eia923__monthly_generation_fuel_fuel_type_code_mer_core_eia__codes_fuel_types_aer', 'core_eia__codes_fuel_types_aer', ['fuel_type_code_mer'], ['code'])

    op.create_table('core_eia__codes_fuel_types_aer',
    sa.Column('code', sa.TEXT(), nullable=False),
    sa.Column('description', sa.TEXT(), nullable=True),
    sa.PrimaryKeyConstraint('code', name='pk_core_eia__codes_fuel_types_aer')
    )
    op.drop_table('core_eia__codes_fuel_types_mer')
    # ### end Alembic commands ###

However, when I run alembic upgrade head I get the following error:
INFO  [root] alembic config.sqlalchemy.url: sqlite:////Users/austensharpe/Desktop/pudl_workspace/pudl_output/pudl.sqlite
Traceback (most recent call last):
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/bin/alembic", line 10, in <module>
    sys.exit(main())
             ^^^^^^
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/alembic/config.py", line 636, in main
    CommandLine(prog=prog).main(argv=argv)
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/alembic/config.py", line 626, in main
    self.run_cmd(cfg, options)
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/alembic/config.py", line 603, in run_cmd
    fn(
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/alembic/command.py", line 406, in upgrade
    script.run_env()
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/alembic/script/base.py", line 582, in run_env
    util.load_python_file(self.dir, "env.py")
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/alembic/util/pyfiles.py", line 95, in load_python_file
    module = load_module_py(module_id, path)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/alembic/util/pyfiles.py", line 113, in load_module_py
    spec.loader.exec_module(module)  # type: ignore
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap_external>", line 995, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/Users/austensharpe/Desktop/Repos/pudl/migrations/env.py", line 81, in <module>
    run_migrations_online()
  File "/Users/austensharpe/Desktop/Repos/pudl/migrations/env.py", line 75, in run_migrations_online
    context.run_migrations()
  File "<string>", line 8, in run_migrations
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/alembic/runtime/environment.py", line 946, in run_migrations
    self.get_context().run_migrations(**kw)
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/alembic/runtime/migration.py", line 628, in run_migrations
    step.migration_fn(**kw)
  File "/Users/austensharpe/Desktop/Repos/pudl/migrations/versions/9625b1bd89e3_aer_to_mer_x2.py", line 27, in upgrade
    with op.batch_alter_table('core_eia923__monthly_generation_fuel', schema=None) as batch_op:
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/contextlib.py", line 144, in __exit__
    next(self.gen)
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/alembic/operations/base.py", line 398, in batch_alter_table
    impl.flush()
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/alembic/operations/batch.py", line 142, in flush
    existing_table = Table(
                     ^^^^^^
  File "<string>", line 2, in __new__
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned
    return fn(*args, **kwargs)  # type: ignore[no-any-return]
           ^^^^^^^^^^^^^^^^^^^
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/sql/schema.py", line 432, in __new__
    return cls._new(*args, **kw)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/sql/schema.py", line 486, in _new
    with util.safe_reraise():
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__
    raise exc_value.with_traceback(exc_tb)
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/sql/schema.py", line 482, in _new
    table.__init__(name, metadata, *args, _no_init=False, **kw)
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/sql/schema.py", line 862, in __init__
    self._autoload(
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/sql/schema.py", line 894, in _autoload
    conn_insp.reflect_table(
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/engine/reflection.py", line 1570, in reflect_table
    self._reflect_fk(
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/engine/reflection.py", line 1768, in _reflect_fk
    sa_schema.Table(
  File "<string>", line 2, in __new__
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/util/deprecations.py", line 281, in warned
    return fn(*args, **kwargs)  # type: ignore[no-any-return]
           ^^^^^^^^^^^^^^^^^^^
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/sql/schema.py", line 432, in __new__
    return cls._new(*args, **kw)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/sql/schema.py", line 486, in _new
    with util.safe_reraise():
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__
    raise exc_value.with_traceback(exc_tb)
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/sql/schema.py", line 482, in _new
    table.__init__(name, metadata, *args, _no_init=False, **kw)
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/sql/schema.py", line 862, in __init__
    self._autoload(
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/sql/schema.py", line 894, in _autoload
    conn_insp.reflect_table(
  File "/Users/austensharpe/mambaforge/envs/pudl-dev/lib/python3.12/site-packages/sqlalchemy/engine/reflection.py", line 1538, in reflect_table
    raise exc.NoSuchTableError(table_name)
sqlalchemy.exc.NoSuchTableError: core_eia__codes_fuel_types_aer

Does your current PUDL DB contain a table named core_eia__codes_fuel_types_aer?

Does your current PUDL DB contain a table named core_eia__codes_fuel_types_aer?

It does, but when I run alembic upgrade head it switches the name to core_eia__codes_fuel_types_mer and then fails and shows me the above error. So the upgrade doesn't work, but the table name gets changed.

What have you already tried to fix it?

I was able to resolve the alembic issue. Searching through the code base, I'm not seeing any reference to fuel_types_mer and I suspect that's probably the way to go -- it's been fuel_type_aer for many years, and if all the codes are the same and things are in flux with the AER/MER/AEO etc. then retroactively changing all the past years of data to say "MER" seems a little weird or premature.

I did a full ETL locally and ran the validation tests overnight and got some row count discrepancies:
FAILED test/validate/eia_test.py::test_minmax_rows[eia_raw-bga_eia860-151860-151860-151860] - ValueError: bga_eia860: found 153487 rows, expected 151860. Off by 1.071%, allowed margin of 0.000%
FAILED test/validate/eia_test.py::test_minmax_rows[eia_annual-bga_eia860-151860-151860-151860] - ValueError: bga_eia860: found 153487 rows, expected 151860. Off by 1.071%, allowed margin of 0.000%
FAILED test/validate/eia_test.py::test_minmax_rows[eia_annual-gen_eia923-None-5494698-459691] - ValueError: gen_eia923: found 459711 rows, expected 459691. Off by 0.004%, allowed margin of 0.000%
FAILED test/validate/mcoe_test.py::test_minmax_rows_mcoe[eia_annual-hr_by_unit-406067-33946] - ValueError: hr_by_unit: found 34258 rows, expected 33946. Off by 0.919%, allowed margin of 0.000%
FAILED test/validate/mcoe_test.py::test_minmax_rows_mcoe[eia_annual-hr_by_gen-634378-52978] - ValueError: hr_by_gen: found 53530 rows, expected 52978. Off by 1.042%, allowed margin of 0.000%
FAILED test/validate/mcoe_test.py::test_minmax_rows_mcoe[eia_annual-fuel_cost-634378-52978] - ValueError: fuel_cost: found 53530 rows, expected 52978. Off by 1.042%, allowed margin of 0.000%
FAILED test/validate/eia_test.py::test_minmax_rows[eia_monthly-bga_eia860-151860-151860-151860] - ValueError: bga_eia860: found 153487 rows, expected 151860. Off by 1.071%, allowed margin of 0.000%
FAILED test/validate/mcoe_test.py::test_minmax_rows_mcoe[eia_annual-capacity_factor-5494698-459691] - ValueError: capacity_factor: found 459711 rows, expected 459691. Off by 0.004%, allowed margin of 0.000%
FAILED test/validate/mcoe_test.py::test_minmax_rows_mcoe[eia_annual-mcoe-5495136-459726] - ValueError: mcoe: found 459746 rows, expected 459726. Off by 0.004%, allowed margin of 0.000%
FAILED test/validate/eia_test.py::test_minmax_rows[eia_monthly-gen_eia923-None-5494698-459691] - ValueError: gen_eia923: found 5494932 rows, expected 5494698. Off by 0.004%, allowed margin of 0.000%
FAILED test/validate/mcoe_test.py::test_minmax_rows_mcoe[eia_monthly-mcoe-5495136-459726] - ValueError: mcoe: found 5495370 rows, expected 5495136. Off by 0.004%, allowed margin of 0.000%
FAILED test/validate/mcoe_test.py::test_minmax_rows_mcoe[eia_monthly-hr_by_unit-406067-33946] - ValueError: hr_by_unit: found 409787 rows, expected 406067. Off by 0.916%, allowed margin of 0.000%
FAILED test/validate/mcoe_test.py::test_minmax_rows_mcoe[eia_monthly-hr_by_gen-634378-52978] - ValueError: hr_by_gen: found 640960 rows, expected 634378. Off by 1.038%, allowed margin of 0.000%
FAILED test/validate/mcoe_test.py::test_minmax_rows_mcoe[eia_monthly-fuel_cost-634378-52978] - ValueError: fuel_cost: found 640960 rows, expected 634378. Off by 1.038%, allowed margin of 0.000%
FAILED test/validate/mcoe_test.py::test_minmax_rows_mcoe[eia_monthly-capacity_factor-5494698-459691] - ValueError: capacity_factor: found 5494932 rows, expected 5494698. Off by 0.004%, allowed margin of 0.000%

(also the FK constraints failed, but that's a FERC-714 problem that came from another branch)

@zaneselvans I don't think things are a bit in flux, it's been superseded entirely by MER.

I took a closer look at the energy_source_code (raw col: reported_fuel_type_code) and fuel_type_code_aer / _mer columns. fuel_type_code_aer is an aggregation of energy_source_code with one exception. energy_source_code will report WAT for hydro and fuel_type_code_aer will report either HYC or HPS for conventional vs. pumped storage. For this reason I kept both columns in the final table.
I changed the _aer suffix to _agg instead of _mer. I also wiped the alembic migrations because I kept running into the same error as above. Confirmed this decision with @e-belfer.


WoWs Info 1.7 (Seven)

The first release of the Flutter rework. It should be a rewrite of what we have live now with minimal changes. We should discuss on whether we should update the UI. We can unify the version of iOS and Android in this update.
These features will be included:

[ ] #73 @Zehui-He @YixunQuan
[x] Ships
[x] Ship filter
[ ] Ship wiki

[x] Similar ships
[x] Similar ship charts
[ ] Upgrades
[ ] Toggle between ships in detail page

[ ] Commander skills
[ ] WoWs RS

[ ] Add consumables (radar, sonar and more)
[ ] Use AP instead of PR for team score

[ ] Clan search
[ ] Clan info
[ ] Player search
[ ] Player achievements
[ ] Player charts improvement
[ ] Player ships
[ ] Player overview
[ ] Update navigation bar
[ ] #67
[ ] #72 major roadblock

We can add some updated UIs in, but we can do it in a later release like 1.8.

This is now moved to https://github.com/wowsinfo/react-native-app/issues/1


Issue connecting to ES Found

I am trying to integrate ES Found and Hadoop with this Hive create table definition below:
CREATE EXTERNAL TABLE es_event ( ... )
STORED BY 'org.elasticsearch.hadoop.hive.EsStorageHandler'
TBLPROPERTIES('es.resource' = 'test',
'es.index.auto.create' = 'true',
'es.nodes' = 'found-host:9200';

However I am always getting EsHadoopInvalidRequest: null every time I attempt to connect to the ES cluster and get the data. Looking closer to the code itself, it seems that the error is caused by 404 Not Found response when the library attempts to hit the ES API oddly by using the IP address instead of the provided host name?
Manually hitting the same address (ie. x.x.x.x:9200) on the browser returns with the error like:
{"ok":false,"message":"Unknown cluster."}
which I expected to return this instead:
{
  "status" : 200,
  "name" : "instance-0000000000",
  "cluster_name" : "xxx",
  "version" : {
    "number" : "1.7.5",
    "build_hash" : "xxx",
    "build_timestamp" : "2016-02-02T09:55:30Z",
    "build_snapshot" : false,
    "lucene_version" : "4.10.4"
  },
  "tagline" : "You Know, for Search"
}

Any idea what causes this issue? Perhaps there is a setting that I missed?
Thanks for the support.

Found the cause of this issue. Apparently there is a method SettingsUtils.resolveHostToIpIfNecessary() that transforms the provided host URL as ip address. This remote ip is then used by the lib to make http request to the remote cluster.
Making http request to Found using this ip address AND without the host header returns 404.
Can you explain why this logic is required?

I am sure the issue is that on the Found side they use a single routing layer that routers for multiple clusters. They use the cluster id that would be in the host header to route to the correct elasticsearch instances themselves.
If the client needs to do the lookup, I think adding the Host header would fix this I believe.
Anyone find another way in the meantime?

The issue of resolving the hostname to IPs has been fixed in master - if not set it will default to true (convert) for non-wan scenarios, false otherwise.
I've just ran another test against Found/Cloud without any issues. Can you please try the dev build?

Thanks @costin, just tried the new dev build and I can confirm that it is now working. Cheers.

@dennyriadi Thanks for reporting and sorry for the inconvenience.
Cheers,


Implement basic ACLINT support for the MTIMER register

Replace the timer defined in the emu_state_t structure, which originally compared with the instruction counter and triggered software timer interrupts, with the MTIMER memory-mapped peripheral. For each HART (currently only one), there is an MTIMECMP register connected to the MTIMER device.
Additionally, use the TIMER Extension to program the clock for scheduling the next timer event.
static inline sbi_ret_t handle_sbi_ecall_TIMER(vm_t *vm, int32_t fid)
{
    emu_state_t *data = PRIV(vm);
    switch (fid) {
    case SBI_TIMER__SET_TIMER:
        data->aclint.mtimecmp = (((uint64_t) vm->x_regs[RV_R_A1])) << 32 |
                                (uint64_t) vm->x_regs[RV_R_A0];
        return (sbi_ret_t){SBI_SUCCESS, 0};
    default:
        return (sbi_ret_t){SBI_ERR_NOT_SUPPORTED, 0};
    }
}

Replacing timer with MTIMER perpheral also triggers timer interrupts normally.
Clarify that the MTIMER peripheral can also trigger timer interrupts within a scheduled period by monitoring /proc/interrupts reveals an increase in timer interrupts triggered by riscv-timer:
  1:        595  SiFive PLIC   1 Edge      ttyS0
  2:         19  SiFive PLIC   3 Edge      virtio1
  3:          0  SiFive PLIC   2 Edge      virtio0
  5:      58985  RISC-V INTC   5 Edge      riscv-timer
...
  1:        610  SiFive PLIC   1 Edge      ttyS0
  2:         19  SiFive PLIC   3 Edge      virtio1
  3:          0  SiFive PLIC   2 Edge      virtio0
  5:      59196  RISC-V INTC   5 Edge      riscv-timer
...
  1:        625  SiFive PLIC   1 Edge      ttyS0
  2:         19  SiFive PLIC   3 Edge      virtio1
  3:          0  SiFive PLIC   2 Edge      virtio0
  5:      59296  RISC-V INTC   5 Edge      riscv-timer

I would like to ask @ranvd for reviewing and collaborating.

Replace the timer defined in the emu_state_t structure, which originally compared with the instruction counter and triggered software timer interrupts, with the MTIMER memory-mapped peripheral. For each HART (currently only one), there is an MTIMECMP register connected to the MTIMER device.
Additionally, use the TIMER Extension to program the clock for scheduling the next timer event.

Could you provide some information on the approach used to validate ACLINT/MTIMER?

I'll take a look soon and maybe verify with virtio-gpu to see if there exists any potential problems.

Replace the timer defined in the emu_state_t structure, which originally compared with the instruction counter and triggered software timer interrupts, with the MTIMER memory-mapped peripheral. For each HART (currently only one), there is an MTIMECMP register connected to the MTIMER device.
Additionally, use the TIMER Extension to program the clock for scheduling the next timer event.

Could you provide some information on the approach used to validate ACLINT/MTIMER?

Replacing timer with MTIMER perpheral also triggers timer interrupts normally.
Clarify that the MTIMER peripheral can also trigger timer interrupts within a scheduled period by monitoring /proc/interrupts reveals an increase in timer interrupts triggered by riscv-timer:
  1:        595  SiFive PLIC   1 Edge      ttyS0
  2:         19  SiFive PLIC   3 Edge      virtio1
  3:          0  SiFive PLIC   2 Edge      virtio0
  5:      58985  RISC-V INTC   5 Edge      riscv-timer
...
  1:        610  SiFive PLIC   1 Edge      ttyS0
  2:         19  SiFive PLIC   3 Edge      virtio1
  3:          0  SiFive PLIC   2 Edge      virtio0
  5:      59196  RISC-V INTC   5 Edge      riscv-timer
...
  1:        625  SiFive PLIC   1 Edge      ttyS0
  2:         19  SiFive PLIC   3 Edge      virtio1
  3:          0  SiFive PLIC   2 Edge      virtio0
  5:      59296  RISC-V INTC   5 Edge      riscv-timer

Clarify that the MTIMER peripheral can also trigger timer interrupts within a scheduled period by monitoring /proc/interrupts reveals an increase in timer interrupts triggered by riscv-timer:
  1:        595  SiFive PLIC   1 Edge      ttyS0
  2:         19  SiFive PLIC   3 Edge      virtio1
  3:          0  SiFive PLIC   2 Edge      virtio0
  5:      58985  RISC-V INTC   5 Edge      riscv-timer
...
  1:        610  SiFive PLIC   1 Edge      ttyS0
  2:         19  SiFive PLIC   3 Edge      virtio1
  3:          0  SiFive PLIC   2 Edge      virtio0
  5:      59196  RISC-V INTC   5 Edge      riscv-timer
...
  1:        625  SiFive PLIC   1 Edge      ttyS0
  2:         19  SiFive PLIC   3 Edge      virtio1
  3:          0  SiFive PLIC   2 Edge      virtio0
  5:      59296  RISC-V INTC   5 Edge      riscv-timer

The above should appear in git commit messages for future reference purpose.

If this pull request is ready for reviewing, use git rebase -i to squash and rework the git commit message. Then, request the reviewers via GitHub website.

I defer @ranvd for confirmation.

Related pull request: #46

After correcting the error above, the kernel gets stuck after logging out [ 0.010981] clint: registering percpu irq failed [-16]. This error may occur in my implementation as well. I'm still figuring out the reason.

If CONFIG_RISCV_M_MODE is not enable, RV_IRQ_SOFT and RV_IRQ_TIMER default to supervisor level interrupts IRQ_S_SOFT (1) and IRQ_S_TIMER (5). However, in the device tree, the CLINT IRQ numbers are set to 3 and 7, which can trigger invalid hardware interrupts:
[    0.002716] clint: clint@4400000: invalid irq 0 (hwirq 3)
[    0.003920] Failed to initialize '/soc@F0000000/clint@4400000': -19

To resolve this, directly set CLINT IRQ number with 1 and 5 for supervior software and timer interrupt:
clint0: clint@4400000 {
    #interrupt-cells = <1>;
    compatible = "sifive,clint0";
    reg = <0x4400000 0x000C000>;
    interrupts-extended = <&cpu0_intc 1 &cpu0_intc 5>;
};

However, this setup triggers the following warning:
[    0.007611] genirq: Flags mismatch irq 5. 00004400 (clint-timer) vs. 00004400 (riscv-timer)

This indicates that both clint-timer and riscv-timer are reporting the same set of flags 0x00004400 (IRQF_PERCPU | IRQF_NO_SUSPEND) for IRQ 5. riscv-timer is managed by the riscv,cpu-intc interrupt controller and should not be altered.
Does it make sense to prioritize adding M-mode privilege levels support for semu first?

Does it make sense to prioritize adding M-mode privilege levels support for semu first?

Yes, M-mode is the highest privilege mode and controls all physical resources and interrupts. Could you check with @ranvd  to confirm if there might be any overlapping efforts with pull request #46 ?

So, according to the clues above, I suggest not implementing M-mode for semu since semu already support SBI for the Linux kernel.

I agree with the previous discussion. The /drivers/clocksource/timer-clint.c file provides supporting evidence:
...
 * Most of the M-mode (i.e. NoMMU) RISC-V systems usually have a
 * CLINT MMIO timer device.
...

Additionally, riscv-timer.c mentions:
...
 * All RISC-V systems have a timer attached to every hart.  These timers can
 * either be read from the "time" and "timeh" CSRs, and can use the SBI to
 * setup events, or directly accessed using MMIO registers.
...

As this PR overlaps with PR #46, it should be closed. I will create a new PR to implement time CSR for generating software timer interrupts, originally triggered by instruction count:
if (vm.insn_count > emu.timer)
    vm.sip |= RV_INT_STI_BIT;
else
    vm.sip &= ~RV_INT_STI_BIT;

This new feature can be integrated after PR #46 is complete.


KAFKA-17655: Add example of changing the e2e image name

As title.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

I modified the property default_jdk in file ducker-ak, and now the jdk version is 11

But I started up the docker with command: TC_PATHS="tests/kafkatest/tests/streams tests/kafkatest/tests/tools" image_name="ducker-ak-openjdk-8" bash tests/docker/run_tests.sh.   The image_name was specified as 8
Then I observed the docker containers:

The image was still 8, and the env image_name took effect.


Fix zsh completion for project and tag names containing spaces

This fixes a bug where project and tag names containing spaces were split on the spaces and completed as separate entities.  For example, given the project name "one two three", zsh would complete "one", "two", and "three" separately.  Typing
watson start o<tab>

would expand to
watson start one

but now correctly expands to
watson start one\ two\ three

Great :+1: !
Do you know if there is a way to have it between quotes instead?

If you type a quote first, it will complete without the backslashes and close the quote, e.g.
watson start 'o<tab>  ->  watson start 'one two three'

I don't know of a way to make it always use quotes, but zsh has so many options, maybe there is something...

Ok, sounds fair enough :) . Thank you for your contribution!


Add support for building with Java 11

Closes #60

Coverage remained the same at 93.223% when pulling 211673e9941cfe8b6468ec2162d4b21227a79b2c on joschi:java-11 into 62190f791a072de017923febf2dbd9a497f88614 on Unleash:master.

Thanks :D


Finalize Docker setup to support pipeline process & display of visualization

Ensure the Docker configuration is complete in its support for all required libraries, as well as serving of the visualization.

I'd like to confirm that the Docker image we've built supports all of the pipeline process dependencies, and is able to handle serving of the viz tools.
@bpben I think in the last meeting you mentioned the xgboost library, and that its dependencies may be tricky to satisfy. If I'm able to run the /src/models/train_model.py script, is that a good indication that the environment is sufficient?
@alicefeng for the viz - should historical_crash_map.py be added to the pipeline process? I've setup apache in the Docker image to serve the viz locally, and I assume once this script is run then the html file(s) just load local resources, or is there more to it?
Additionally, I'd also like to understand what the resistance points are in Docker being used consistently while developing the project. I've probably done a bad job of explaining this previously, but the big advantages to using Docker are portability and reproducibility. Especially when we get to the stage of deploying the project into a hosted environment, we want to avoid the "it works on my machine" problem, as well as be able to part out the different parts of the project into containers of single responsibility. If anyone has specific problems with using Docker please post a comment and we can work to resolve them, thanks.
@j-t-t @andhint

That's great news! Good to hear it's working.  My sense is that Docker make sense at each checkpoint in the project, but figuring out how to make Docker work on certain elements when it's still unclear whether those elements are going to be in the final product seems like it might be wasted effort.  But I totally agree that making Docker work with the various components of this v1 release makes sense.

@terryf82 Yes, historical_crash_map.py should be added to the pipeline process.  That script is needed to generate the datasets displayed in the viz.  One other tweak that will need to be implemented is a way for the viz to figure out what city needs to be displayed in the map.  Currently the lat/long is hardcoded so I need to change that to be more flexible.
As for Docker, my only issue with it has been that I keep forgetting what are the commands I need to type to use it. ^_^


Account impersonating

Add feature for impersonating accounts on a forked devnet.
Hardhat docs:

https://hardhat.org/hardhat-network/docs/reference#hardhat_impersonateaccount

Additional context from anvil docs:
anvil_impersonateAccount Send transactions impersonating an externally owned account or contract.
anvil_stopImpersonatingAccount Stops impersonating an account or contract if previously set with anvil_impersonateAccount
To investigate further:
anvil_autoImpersonateAccount Accepts true to enable auto impersonation of accounts, and false to disable it. When enabled, any transaction’s sender will be automatically impersonated. Same as anvil_impersonateAccount.

Transactions sent via account that is impersonated will cost less in terms of gas units. This is because validation step will be skipped


CP001: Missing Update in device

In the new update methods of the handler (to/from device), seems that the case where buffer contents are updated with other buffer contents is missing.

#12  fixes this


Rule documentation link does not work with lower case code

When trying to load a specific rule's documentation page using a the lower case letter for that rule (e.g. https://docs.astral.sh/ruff/rules/f401), I get a 404 - Not Found.
After loading the page once using an uppercase letter instead (which does work), if I then try it again with the lowercase, my browser (Firefox) automatically corrects the lowercase to the uppercase and the site does load.
It might be nice to make the mirror work immediately in a case insensitive manner.

Yeah, I noticed this last week and I was wondering if this should be allowed because the rule selection wouldn't allow lowercase either (select = ["f401"] doesn't work). The same argument can be applied to rule names as well as it only works with lower case names so https://docs.astral.sh/ruff/rules/Unused-Import doesn't work.

What would be the argument not to allow it?
I guess formally you're right that it's an "invalid" rule code, but I don't think there's any level of confusion of what is intended when a user inputs a rule code with a lower case letter.
I find it convenient to type the rule code without worrying about the capitalization, and have now a few times been surprised as to why it doesnt always work (until I discovered that it'll only work if I've been on that page before).


Customize the name of the service-worker file?

Hello,
I'm wondering if it may be possible to customize the name of the generated service worker.
I have some libraries that require an specific service worker name

To change this directly, you'd need access to the underlying webpack configuration to do that, which is only possible with create-react-app if you eject.
Alternatively, after the c-r-a build process completes you could attempt to run an additional command that would rename the generated service worker file, but I'm not sure what the best way to automate that would be.
(Which libraries are you using that require a specific service worker name, by the way?)

(Which libraries are you using that require a specific service worker name, by the way?)

firebase FCM will automatically try to register a service worker with the name firebase-messaging-sw.js. Trying to change the name after build should be doable with a bash script on a postbuild script. Thanks.

You can use FCM with an existing top-level service worker; I believe you need to call importScripts() from that top-level service worker (like the one generated in c-r-a) to pull in the FCM code, and then something with:

https://firebase.google.com/docs/reference/js/firebase.messaging.Messaging#gettoken
https://firebase.google.com/docs/cloud-messaging/js/receive#web-v8

to pass through the registration info? I'm not 100% sure of all the steps, but it is possible.

Yes, you can get the registration object and pass it down to the getToken method and it will use that service worker. However, that means that I will have to handle the registration and keep the correct reference somewhere.
While this is not very problematic but I am not using the PWA template, which means that I don't have the registration scripts and that stuff. But that is just the smallest problem, the main problem is that it is too early for my project to be cached by a service worker and all the problems that has. I want every release to reach all my users as soon as possible.
All I wanted from CRA was to compile my SW from typescript and bundle the proper imports into the file (i18n and some libs that I may need) without any caching, but seems that such thing is not possible.
I tried deactivating the caching according to docs and the generated SW is still huge, I don't understand what it includes.

You don't have to use the c-r-a template for PWAs in that case. You can just create your own bare-bones service worker file containing whatever you want and... I am not actually sure how to tell c-r-a to compile it, but that's more of a question for the c-r-a project itself. But once you have the service worker compiled, it can be registered from your main web app via navigator.serviceWorker.register('my-sw.js').
Using this PWA template is optional, and intended for folks who do want that Workbox-based precaching, which does require deep integration with your underlying webpack build.


Explain recommendation for one reader per partition per consumer group

The doc makes this statement without supporting it: "It is recommended that there is only one active receiver on a partition per consumer group"
I believe the issue is this: Within a single partition, each reader will receive all of the messages. If you have 2 readers on the same partition, then you will be processing duplicate messages. You will need to handle this in your code which may not be trivial. However it's a valid approach in some scenarios.

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

ID: 71adf8e4-a51b-d20d-39e1-fd7551bc94b9
Version Independent ID: 3d26fbc0-b6ae-e0ca-089f-e4966c19ef22
Content: Azure Event Hubs features overview
Content Source: articles/event-hubs/event-hubs-features.md
Service: event-hubs
GitHub Login: @sethmanheim
Microsoft Alias: sethm

@MikeWasson Hey Mike, thanks for the feedback. As I understand it, GitHub issues are for external folks, and internal people should just use PRs. Is that your understanding as well?

@MikeWasson No don't worry, I'll take this one, but I won't tell Tyson. :-)

@vasivara-MSFT Please assign to @ShubhaVijayasarathy.

@MikeWasson - Thank you. I have updated the article.
@vasivara-MSFT - #please-close


containerd cve fix for release-2.4

Signed-off-by: Xiangjing Li<EMAIL_ADDRESS>https://github.com/stolostron/backlog/issues/19513
The github.com/containerd/containerd pkg is required to upgrade to V1.5.9 for fixing the CVE.  But there is a broken change in the V1.5.9. As the result,  all its dependent packages such as helm.sh/helm/v3,  k8s.io/api, sigs.k8s.io/controller-runtime  are required to upgrade

/test test-unit

/test test-unit


Update WindowsBuild.md

Update rules for the Windows build after CMake 3.15 upgrade.  This simplifies the rules, relies on the export targets and removes the unnecessary variables.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please smoke test


griddata docstring doesn't make any sense

The docstring for griddata refers to many different integers:
D, n, ndim, M:
Interpolate unstructured D-dimensional data.

Parameters
----------
points : ndarray of floats, shape (n, D)
    Data point coordinates. Can either be an array of
    shape (n, D), or a tuple of `ndim` arrays.
values : ndarray of float or complex, shape (n,)
    Data values.
xi : ndarray of float, shape (M, D)
    Points at which to interpolate data.

The only one that is defined is D, so users have no idea what the others are.
Furthermore the example provided contradicts the docstring as xi is passed as a tuple but the docstring says it must be a ndarray.

The integers are defined by the shapes of the input arrays.

The xi description needs to be extended though, looks like it can be both 2-D ndarray or tuple of 1-D arrays.

I wish to work on this . Will be sending the PR.

Some clarification probably still needed.

@pv can you explain more?


Broken markdown cells in .dib notebooks

Describe the bug
It seems that yesterday the .net interactive tool updated causing markdown blocks to not be recognized. After loading a .dib file it shows the markdown cells as code cells with #!markdown as the first line.
Steps to reproduce:

Create new .dib notebook file
Add a markdown cell and enter some text
Save the notebook
Close and reopen the notebook. The markdown cell is now parsed as a code cell with #!markdown as the first line.

Please complete the following:
Which version of .NET Interactive are you using? There are a few ways to find this out:

OS

[x] Windows 10
[ ] macOS
[ ] Linux (Please specify distro)
[ ] iOS
[ ] Android

Browser

[ ] Chrome
[ ] Edge
[ ] Firefox
[ ] Safari

Frontend

[ ] Jupyter Notebook
[ ] Jupyter Lab
[ ] nteract
[x] Visual Studio Code
[ ] Visual Studio Code Insiders
[ ] Other (please specify)

I just opened a notebook, .NET Interactive updated and everything broke. As you say, the code and markdown aren't respecting the section markers.

I also just tried rolling back, that didn't work! Bah.

Interestingly, if I create a new notebook, it works fine until I save it, then it instantly breaks.

I have exactly the same problem. Before launching, I have to repartition the cells to make it work. After reopening, everything is reset again and does not work (

Yeah I just found that if I start a new workbook, the top markdown cell gets saved as code. If change it back to markdown, and clear the #!markdown tag, it works. The underlying file doesn't seem to change though, so weird.

We just published extension version 1.0.2459010 which addresses this issue.


Update stings.xml (values-fr) - May 19, 2020 ver.

Some translations may be oddly long. I will correct them once I see what they look like in the app.

I just saw the new update (line 109). Sorry I published the translation before that.
The French translation would be:
Pack d'icônes %d


Fixes announcement banner color for dark themes

Fixes an issue mentioned on https://github.com/napari/docs/pull/332#issuecomment-1906694584
Until this is incorporated in a new napari-sphinx-theme release, a temporary fix is in https://github.com/psobolewskiPhD/napari-docs/pull/10

My wife tested the other PR in dark mode firefox, windows and it looks good, so approving here too!


⚠ File access (beta) has degraded performance

In 8941f83, File access (beta) (https://beta.fyle.uk/file/fish) experienced degraded performance:

HTTP code: 200
Response time: 2648 ms

Resolved: File access (beta) performance has improved in 827084c.


Is it possible to trigger enterprise workflow and wait?

I want to trigger a enterprise github workflow from a non enterprise github workflow. Is there any way I can do this?
As I saw here, I will not be able to provide any github_server_url
- uses<EMAIL_ADDRESS>  with:
    owner: keithconvictional
    repo: myrepo
    github_token: ${{ secrets.GITHUB_PERSONAL_ACCESS_TOKEN }}
    workflow_file_name: main.yml
    ref: release-branch
    wait_interval: 10
    inputs: '{}'
    propagate_failure: false
    trigger_workflow: true
    wait_workflow: true

https://github.com/convictional/trigger-workflow-and-wait/commit/c7162ad4f3e376ce16d1f274c5edcf7068df808c

@LakshmiRavali Were you able to achive your requirement ?

(see morapet's comment)


fix arg parsing

fire CLIs installed as package not script. e.g.
# -*- coding: utf-8 -*-
import re
import sys
from shot import shot
if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])
    sys.exit(shot())

this means the default action is always run.
possible solutions
either:

change script to run python shot.py
switch to argparse etc so shot() parses args

Hacky fix locally
#!/bin/bash
# use python installed by formula, to run script installed by formula, pass all args from bash to python with `$@`
/home/linuxbrew/.linuxbrew/Cellar/shot/0.1.0/libexec/bin/python /home/linuxbrew/.linuxbrew/Cellar/shot/0.1.0/libexec/lib/python3.9/site-packages/shot.py $@

Closed by 7c27754ceb32216955f373e116789c9f322b9110
First fix using method 1. change script to run python shot.py
https://engineering.innovid.com/distributing-command-line-tools-with-homebrew-d03e795cadc8
Possibly second fix in next version of shot: add main function same as osxdocker.


Installation via OLM in specific namespace fails

Describe the bug
Following the steps https://enmasse.io/documentation/master/openshift/#assembly-installing-configuring-olm-messaging to deploy enmasse via OLM in a specific namespace leads into a failed installation of the operator and the error shown is unable to adopt APIService
To Reproduce
Follow the steps https://enmasse.io/documentation/master/openshift/#assembly-installing-configuring-olm-messaging
Expected behavior
enmasse successfully installed in namespace enmasse-infra via OLM

@famartinrh Could you share some more of the following details:

Which OpenShift version
Which EnMasse version
Where do you see the error shown?

Following the documentation, installing via the UI, the operator installs in the custom namespace as expected for me on OpenShift 4.2, EnMasse 0.30.1.

@famartinrh on master, I was able to install doing the following:

oc scale deployment community-operators -n openshift-marketplace --replicas=0
Apply the following file (to openshift-marketplace):

apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: enmasse-source
  namespace: openshift-marketplace
  labels:
    app: enmasse
spec:
  displayName: EnMasse Operator Source
  image: quay.io/enmasse/olm-manifest:latest
  publisher: enmasse
  sourceType: grpc

Create the subscription in the UI pointing to the enmasse-infra namespace. The created subscription looks like this:

kind: Subscription
metadata:
  creationTimestamp: "2019-11-20T09:50:10Z"
  generation: 1
  name: enmasse
  namespace: enmasse-infra
  resourceVersion: "540315"
  selfLink: /apis/operators.coreos.com/v1alpha1/namespaces/enmasse-infra/subscriptions/enmasse
  uid: 2411999c-0b7b-11ea-82eb-52fdfc072182
spec:
  channel: alpha
  installPlanApproval: Automatic
  name: enmasse
  source: enmasse-source
  sourceNamespace: openshift-marketplace
  startingCSV: enmasse.999.999.999
status:
  catalogHealth:
  - catalogSourceRef:
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      name: certified-operators
      namespace: openshift-marketplace
      resourceVersion: "539942"
      uid: 33d5cb4b-faf1-11e9-a63f-525400d602f2
    healthy: true
    lastUpdated: "2019-11-20T09:50:10Z"
  - catalogSourceRef:
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      name: community-operators
      namespace: openshift-marketplace
      resourceVersion: "540103"
      uid: caed6ec4-0b7a-11ea-82eb-52fdfc072182
    healthy: true
    lastUpdated: "2019-11-20T09:50:10Z"
  - catalogSourceRef:
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      name: enmasse-source
      namespace: openshift-marketplace
      resourceVersion: "539945"
      uid: e91c6818-0b7a-11ea-82eb-52fdfc072182
    healthy: true
    lastUpdated: "2019-11-20T09:50:10Z"
  - catalogSourceRef:
      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      name: redhat-operators
      namespace: openshift-marketplace
      resourceVersion: "539944"
      uid: 328dd704-faf1-11e9-a63f-525400d602f2
    healthy: true
    lastUpdated: "2019-11-20T09:50:10Z"
  conditions:
  - lastTransitionTime: "2019-11-20T09:50:10Z"
    message: all available catalogsources are healthy
    reason: AllCatalogSourcesHealthy
    status: "False"
    type: CatalogSourcesUnhealthy
  currentCSV: enmasse.999.999.999
  installPlanRef:
    apiVersion: operators.coreos.com/v1alpha1
    kind: InstallPlan
    name: install-t5h94
    namespace: enmasse-infra
    resourceVersion: "540163"
    uid: 24205771-0b7b-11ea-82eb-52fdfc072182
  installedCSV: enmasse.999.999.999
  installplan:
    apiVersion: operators.coreos.com/v1alpha1
    kind: InstallPlan
    name: install-t5h94
    uuid: 24205771-0b7b-11ea-82eb-52fdfc072182
  lastUpdated: "2019-11-20T09:50:17Z"
  state: AtLatestKnown

Howerver, I did notice an issue with fsGroup being set on address-space-controller preventing it to start up, but it is unrelated to the issue you were seeing I think.

Hey @lulf sorry for the delay in response, many thanks for the hints.
Yes I'm using master and testing on ocp 4.2 and CRC, well actually I'm using whatever is pushed in quay.io/enmasse/olm-manifest:latest which should be more or less master .
The error unable to adopt APIService was because of my mistake, env wasn't clean from previous tests (CRDs remaining,...).
Apart from that, following your steps I'm able to install the operator too, and address-space-controler isn't deployed, it's weird because the deployment stays with 0 of 1 pods and no pods are created, the same happens with standard-authservice, happens both in ocp4 and CRC.
And regarding install into a specific namespace using only the CLI I found the missing piece to make it work, before appliying the subscription an operatorgroup resource is needed in enmasse-infra namespace:
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  name: enmasse-infra-group
  namespace: enmasse-infra
spec:
  targetNamespaces:
  - enmasse-infra

with this the operator gets deployed, the error with address-space-controller not being deployed remains

Related to the error I'm having with address-space-controller deployment not spawning pods, my bad not investigating any further, the error can be seen in the associated replica set which show the error Error creating: pods "address-space-controller-7487678b76-" is forbidden: unable to validate against any security context constraint: [fsGroup: Invalid value: []int64{1000}: 1000 is not an allowed group]
This happens installing current master via OLM into a specific namespace

@famartinrh Yes, this is fixed in #3482

oh @lulf didn't look like it would change the fsGroup value to any other so I though that PR wasn't going to fix this

@famartinrh The problem is that the fsGroup was applied to the address-space-controller, which was wrong. It should only be applied to standard-authservice. Another PR is required to ensure that it is applied/not applied to brokers though.

#2714

@famartinrh Closable?

yes


modal service not set

I seem to have everything referenced correctly but get the js error 'Configuration Error: modal service not set' whenever I call a line such as:
this.modal.prompt().title(title).body(body).okBtn(okButton).open();
Could be how I am using the library but for now we are just testing it out  We are using commonJS if that may be somehow related to the issue.
My bootstrap line looks like:
bootstrap(RootComponent, [HTTP_PROVIDERS, provide(ModalConfig, { useValue: new ModalConfig('sm', true, 81) })]);
Any other configuration I'm missing to overcome the 'modal service not set'?

@kvgros
Configuration Error: modal service not set comes from ModalAwarePreset.ts
See here
This is related to using the Fluent API to open a modal.
Basically what happens is that along the process of constructing a preset (so you could use the fluent API) the modal is set internally, this is so you wouldn't have to do:
// in class constructor:private modal: Modal
modal.alert()
    .modal(this.modal)
    .title('Hello World')
    .body('In Angular 2')
    .open();

The preset must have a reference to the "Modal" instance so it can fire open.
ModalAwarePreset.ts is just a base class, the actual modal assignment happens in OneButtonPreset which is a concrete preset.
It gets a modal as a value in the constructor....
When you call modal.prompt() this get invoked:
prompt(): OneButtonPreset {
        return new OneButtonPreset(this, <any>{ isBlocking: true, keyboard: null });
    }

So, the first param in the ctor for OneButtonPreset is this which is the instance of Modal so the error is very strange...
Is there any change you are importing direct files instead of the entry file?

stale, closing...


[Req] Add unit/e2e test with MSW

Dear @oedotme,
really appreciate your works, whether it is possible to add vitest (MSW) and cypress to this template? it'd be helpful to replace CRA template with this.
thanks

Hey @sprabowo, thanks for the suggestion and apologize for the late reply.
I've been using Playwright for both end-to-end and unit tests and it works very well. I've set it up with this repo, here's the reference commit 17c869a


Accents misbehavior between native and WASM

Thanks in advance for your bug report!

[X] Have you reproduced issue in safe mode?
[X] Have you used the debugging guide to try to resolve the issue?
[X] Have you checked our FAQs to make sure your question isn't answered there?
[X] Does your issue already exist?
[X] Have you checked you are on the latest release of Pulsar?

What happened?
Accents and other UTF-8 characters get wrong
Which OS does this happen on?
🐧 Debian based (Linux Mint, Ubuntu, etc.)
OS details
Ubuntu 20.04
Which CPU architecture are you running this on?
64-bit(x86_64)
What steps are needed to reproduce this?
Type something like "ÁÁÁááá" (or copy-paste this on the editor)
Call UNDO
Call REDO

Additional Information:
No response

If I could guess, I think it's on the snapshot functionality. But it's guesswork only for now, probably some misbehavior in the conversion between WASM and C++


Bump sigstore/sigstore to HEAD

Summary
This PR bumps the sigstore/sigstore version to pull commit 9c0e2e247545c329544bf32170729d20b386a25c fixes a race in assignments in the TUF client needed to run concurrent signing operations.
cc @imjasonh @asraa
Signed-off-by: Adolfo García Veytia (Puerco<EMAIL_ADDRESS>Ticket Link
Ref: https://github.com/sigstore/cosign/pull/1992#issuecomment-1154619316
Follow-up to https://github.com/sigstore/sigstore/pull/503 https://github.com/sigstore/cosign/pull/1866
Release Note
NONE

Codecov Report

Merging #1995 (d0be5b7) into main (25b4d5e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1995   +/-   ##
=======================================
  Coverage   26.21%   26.21%
=======================================
  Files         127      127
  Lines        7407     7407
=======================================
  Hits         1942     1942
  Misses       5210     5210
  Partials      255      255

Continue to review full report at Codecov.

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


App crashing sometimes when dismissing the pop up

Hi guys, is anyone also experiencing an intermittent crash that happens when the pop up is being dismissed?
Stack Trace
Crashed: com.apple.main-thread
0  NEPAB                          0x511ee4 FullscreenPopup.getModifier() + 218 (FullscreenPopup.swift:218)
1  NEPAB                          0x5117b8 closure #1 in FullscreenPopup.constructPopup() + 184 (FullscreenPopup.swift:184)
2  SwiftUI                        0x1008578 OUTLINED_FUNCTION_5 + 352
3  NEPAB                          0x5107c0 FullscreenPopup.constructPopup() + 187 (FullscreenPopup.swift:187)
4  NEPAB                          0x51097c closure #2 in FullscreenPopup.main(content:) + 161 (FullscreenPopup.swift:161)
5  SwiftUI                        0x19fcebc OUTLINED_FUNCTION_35 + 144
6  NEPAB                          0x50fa84 FullscreenPopup.main(content:) + 159 (FullscreenPopup.swift:159)
7  NEPAB                          0x50e8e0 FullscreenPopup.body(content:) + 126 (FullscreenPopup.swift:126)
8  SwiftUI                        0x100cc0 OUTLINED_FUNCTION_2 + 9928
9  SwiftUI                        0x191fb2c OUTLINED_FUNCTION_0 + 13488
10 SwiftUI                        0x191f6a4 OUTLINED_FUNCTION_0 + 12328
11 SwiftUI                        0x1327b0c __swift_allocate_boxed_opaque_existential_1Tm + 268
12 AttributeGraph                 0xb854 AG::Graph::UpdateStack::update() + 512
13 AttributeGraph                 0x2504 AG::Graph::update_attribute(AG::data::ptr<AG::Node>, unsigned int) + 424
14 AttributeGraph                 0xcf58 AG::Subgraph::update(unsigned int) + 848
15 SwiftUI                        0x1794988 OUTLINED_FUNCTION_2 + 14264
16 SwiftUI                        0x1795e84 OUTLINED_FUNCTION_2 + 19636
17 SwiftUI                        0xe0a418 OUTLINED_FUNCTION_15 + 43180
18 SwiftUI                        0x187de24 OUTLINED_FUNCTION_2 + 14484
19 SwiftUI                        0x187c33c OUTLINED_FUNCTION_2 + 7596
20 SwiftUI                        0xe014cc OUTLINED_FUNCTION_15 + 6496
21 SwiftUI                        0x1795e4c OUTLINED_FUNCTION_2 + 19580
22 SwiftUI                        0x1795d38 OUTLINED_FUNCTION_2 + 19304
23 SwiftUI                        0x115c268 OUTLINED_FUNCTION_11 + 40
24 SwiftUI                        0x7523b8 OUTLINED_FUNCTION_4 + 34420
25 SwiftUI                        0x752324 OUTLINED_FUNCTION_4 + 34272
26 SwiftUI                        0x752450 OUTLINED_FUNCTION_4 + 34572
27 CoreFoundation                 0x35a2c __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36
28 CoreFoundation                 0x34434 __CFRunLoopDoObservers + 548
29 CoreFoundation                 0x33b50 __CFRunLoopRun + 1028
30 CoreFoundation                 0x33668 CFRunLoopRunSpecific + 608
31 GraphicsServices               0x35ec GSEventRunModal + 164
32 UIKitCore                      0x22c2b4 -[UIApplication _run] + 888
33 UIKitCore                      0x22b8f0 UIApplicationMain + 340
34 SwiftUI                        0x11620fc OUTLINED_FUNCTION_31 + 604
35 SwiftUI                        0x1161f40 OUTLINED_FUNCTION_31 + 160
36 SwiftUI                        0xdd3868 OUTLINED_FUNCTION_26 + 2196
37 NEPAB                          0x843c main + 12 (ParentApp.swift:12)
38 ???                            0x1d9116dcc (Missing)

Hey @raphaeloliveira, please provide full minimal compilable example and make sure the issue reproduces on this minimal example. Have a nice day

It's been a while, so I'll close this one for now. Please feel free to reopen if you are still having the issue. Please be sure to attach minimal compilable reproducible example. Have a nice day!


Yandex SearchControl not works

Firstly, it has a strange position. At what layer it is? How can I drive it's sizing?

While searching something even only one time I'm always getting the next error

It is working. Just use proper api key.
We do not define position of yandex 'native' controls. You can use ymaps api for that.
Or it may be possible via css.


Client does not Receive Initial Position Update

Client requests positions of all the other clients on join game room.
https://github.com/valkyrienyanko/Unity-ENet-Model/blob/f38cab7529867091a4b2fedf20769a2ba9560f56/Client/Assets/Workspace/Scripts/Network/Client.cs#L220
Server accepts packet and proceeds to send position update of all clients as requested.
https://github.com/valkyrienyanko/Unity-ENet-Model/blob/f38cab7529867091a4b2fedf20769a2ba9560f56/Server/Server.cs#L224-L229
The issue resides here, the client does not seem to receive the initial position update at all. No Debug.Log gets fired.
https://github.com/valkyrienyanko/Unity-ENet-Model/blob/f38cab7529867091a4b2fedf20769a2ba9560f56/Client/Assets/Workspace/Scripts/Network/Client.cs#L162-L193

b1f7ebc9f24424d7c495130c74ba7e408ef2aef4


Client does not handle failed txs

After sending a request that ended with an out of gas error:
(mech-py3.10) david@XPS13:/tmp/mech$ mechx interact "write a short poem" 6 --key ~/ethereum_private_key.txt --tool openai-gpt-3.5-turbo --chain-config gnosis --confirm on-chain
Chain configuration: gnosis
Sending request...
Prompt uploaded: https://gateway.autonolas.tech/ipfs/f01701220f47c53331ec0fe34e4ed95614253caeeec8bdd012d9ddd0350d7a5f508b02b00
Transaction sent: https://gnosisscan.io/tx/0x316dc61917e9ee2940f41e29c71ace6012415ae38e9943958e3768f1b32d3b5c
Waiting for transaction receipt...

Addressed on #46


Compress old archived data

Today we do not compress the archived data.
Some ideas:

Concatenated all the hours in a single day.
Compress the single day data - (have options for different compression formats and compression levels)
Create metadata file that marks the lines numbers of each hour in a day.

@ivan-stankov-golang could you check this task and eventually add Gzip and Zstandard compression?
We should be able to specify the compression type and compression level.

Hello @ivan-stankov-golang
A clarification about:

Create metadata file that marks the lines numbers of each hour in a day.

When we create the archive we will concatenate the concatenate all the files in one large file. When doing this we should create an additional metadata file that marks the lines in the large file that contain each hour.
Below is an example:
Let's suppose that:

1st hour of the day has 10 lines.
2nd hour of the day has 50 lines.
3rd hour of the day has 85 lines.
...

Let's suppose that we are archiving all the hours for 21st of September 2023.
Then should have a metadata file: 2023-09-21-parts-meta.txt
Inside this file we could have the following content:
1,1,10
2,11,60
3,61,145
...
```


JavaScript heap out of memory errors after upgrading spfx 1.10. -> 1.14

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

SPFx version  1.14x (current) before upgrade (1.10x)
Node.js version  14.20.0(current) before upgrade (10.22.0)

Describe the bug / error
Upgraded spfx from 1.10(node 10.22.0) to 1.14(node version - 14.20.0) and started seeing this in my project. I have successfully upgraded the webpart components and did not face any such issue. But for the spfx extensions we are not able to bundle it, it is throwing JavaScript heap out of memory error.
Error on running gulp bundle --ship:
[07:29:01] Error - [tslint] <--- Last few GCs --->
[4648:000001BF13A02360]    13153 ms: Scavenge 1284.5 (1317.5) -> 1284.5 (1317.5) MB, 131.1 / 0.0 ms  (average mu = 1.000
[07:29:01] Error - [tslint] , current mu = 1.000) allocation failure
[4648:000001BF13A02360]    16119 ms: Mark-sweep 1877.5 (1910.6) -> 1835.4 (1872.9) MB, 1033.1 / 0.1 ms  (+ 9.0 ms in 8 steps since start of marking, biggest step 1.5 ms, walltime since start of marking 7136 ms) (average mu = 0.930, current mu = 0.930) all
<--- JS stacktrace --->
FATAL ERROR: invalid array length Allocation failed - JavaScript heap out of memory
[07:29:01] Error - [tslint] 1: 00007FF697A95E4F napi_wrap+133327
2: 00007FF697A2F446 DSA_meth_get_fla
[07:29:01] Error - [tslint] gs+63062
3: 00007FF697A302DD node::OnFatalError+301
4: 00007FF6983141FE v8::Isolate::ReportExternalAllocationLimitReached+94
5: 00007FF6982F8FED v8::SharedArrayBuffer::Externalize+781
6: 00007FF6981A27EC v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1516
7: 00007FF6981C739F v8::internal::Factory::NewUninitializedFixedArray+111
8: 00007FF69808C4F0 v8::Object::GetIsolate+7280
9: 00007FF697F15B27 v8::internal::interpreter::JumpTableTargetOffsets::iterator::operator=+170247
10: 00007FF69839F62D v8::internal::SetupIsolateDelegate::SetupHeap+474253
11: 000003E71B86B573
Package.json
{
"name": "i-portal-policy-page-command-extension",
"version": "0.0.1",
"private": true,
"main": "lib/index.js",
"scripts": {
"build": "gulp bundle",
"clean": "gulp clean",
"test": "gulp test"
},
"dependencies": {
"@microsoft/decorators": "^1.11.0",
"@microsoft/sp-core-library": "^1.12.1",
"@microsoft/sp-dialog": "^1.11.0",
"@microsoft/sp-listview-extensibility": "^1.11.0",
"@microsoft/sp-office-ui-fabric-core": "^1.14.0",
"@pnp/sp": "^2.5.0",
"@pnp/sp-commonjs": "^2.5.0",
"exceljs": "^4.2.1",
"lodash": "^4.17.21",
"log4js": "^6.3.0",
"office-ui-fabric-react": "^7.174.1",
"pwc-rni-independenceportal-spo-library": "1.0.92",
"sp-pnp-js": "^3.0.10",
"xlsx": "^0.17.0"
},
"devDependencies": {
<EMAIL_ADDRESS>"0.4.47",
"@microsoft/sp-build-web": "1.14.0",
"@microsoft/sp-module-interfaces": "1.14.0",
"@microsoft/sp-tslint-rules": "1.14.0",
"@types/es6-promise": "0.0.33",
"@types/webpack-env": "1.13.1",
"ajv": "~5.2.2",
"gulp": "4.0.2"
}
}
tslint.json
{
"extends"<EMAIL_ADDRESS>"rules": {
"class-name": false,
"export-name": false,
"forin": false,
"label-position": false,
"member-access": true,
"no-arg": false,
"no-console": false,
"no-construct": false,
"no-duplicate-variable": true,
"no-eval": false,
"no-function-expression": true,
"no-internal-module": true,
"no-shadowed-variable": false,
"no-switch-case-fall-through": true,
"no-unnecessary-semicolons": true,
"no-unused-expression": true,
"no-use-before-declare": true,
"no-with-statement": true,
"semicolon": true,
"trailing-comma": true,
"typedef": false,
"typedef-whitespace": false,
"use-named-parameter": true,
"variable-name": false,
"whitespace": false,
"no-reserved-keywords":true
}
}
tsconfig.json
{
"extends"<EMAIL_ADDRESS>"compilerOptions": {
"target": "es5",
"forceConsistentCasingInFileNames": true,
"module": "esnext",
"moduleResolution": "node",
"jsx": "react",
"declaration": true,
"sourceMap": true,
"experimentalDecorators": true,
"skipLibCheck": true,
"outDir": "lib",
"inlineSources": false,
"strictNullChecks": false,
"noUnusedLocals": false,
"typeRoots": [
"./node_modules/@types",
"./node_modules/@microsoft"
],
"types": [
"es6-promise",
"webpack-env"
],
"lib": [
"es6",
"es5",
"dom",
"es2015.collection",
"es2015.promise"
]
},
"include": [
"src//*.ts",
"src//*.tsx"
],
"exclude": []
}
However on running, gulp bundle --max_old_space_size=8192 --ship
we are not getting the error anymore but is this route sustainable, that is our apprehension. Please help us with this problem
Steps to reproduce
1.Upgraded spfx to 1.14x by running the command: m365 spfx project upgrade --toVersion 1.14.0 --output md > "upgrade-report.md"
2. deleted node modules,did gulp clean, npm install, gulp bundle --ship --> got the error
Expected behavior
we expected the bundle to run successfully

@tista-chatterjee - your package.json seems not completely right.
We recommend using exact versions of the packages.
In your case you have this:
"@microsoft/decorators": "^1.11.0",
"@microsoft/sp-core-library": "^1.12.1",
"@microsoft/sp-dialog": "^1.11.0",
"@microsoft/sp-listview-extensibility": "^1.11.0",
"@microsoft/sp-office-ui-fabric-core": "^1.14.0",

It means that you will actually load 1.15.2.
But in devDependencies you have exact versions 1.14.0.
It leads to mismatch.
Please, double-check the upgrade steps generated by the CLI and modify your output.
Please, let us know if the error exists after the fixes.


Added sorting based on event end time

Closes: #20

The only event in the deployed database with an end date greater than the currrent time is feaured as you can see in the screenshot....
@Yash-Ainapure please look into me PRs :)

@Yash-Ainapure @yashksaini-coder @Gauravtb2253 please merge the pr as only a day remains in the GSSOC

@Yash-Ainapure @yashksaini-coder @Gauravtb2253 please merge the pr as only a day remains in the GSSOC...
At this its a request please dont let my work go waste 🙏

@Yash-Ainapure @yashksaini-coder @Gauravtb2253 please merge the pr as only a day remains in the GSSOC... At this its a request please dont let my work go waste 🙏

I am really sorry for late.
thanks for your contribution.


Align with croissant

At least map to corresponding values
https://github.com/mlcommons/croissant

May also suggest developing a way to generate Croissant with LinkML


Deployment environment with Terraform

This adds the ability to deploy an environment for e2e with Terraform.
It adds the environment runner, and the ability to create a SOCKS tunnel
to the instance using SSH to run the check against the environment.
I implemented the environment for the OpenStack check, and SOCKS first
instead of regular tunnel because the OpenStack check talks to several
endpoints.
To test, you need to download a GCP credentials files and set the
TF_VAR_account_json environment variable.

Just as a general comment for now:
What takes the most time in here is to run the openstack script. One improvement could be to create a terraform managed "base image" which we can keep on google cloud and reuse for tests. Keeping the image on gcloud costs $0.085/GB/month
This would mean to refactor a bit the terraform plan to have separates "module". One for creating and storing the image, one for creating the VM. And then only destroy the module for the VM. What's your thoughts on this?

Looks like I can't make it work anymore with latest commits:

ddev test fails after setting up the environment because it can't find the correct folder for the ssh_key file.
ddev env check fails because the agent in the container does not have the config to use the socks proxy.


Build binary releases for windows

Pre-built binary packages like this are useful for quickly exploring and learning about the substrate node. Create packages targeting Windows as well.
An exe or msi installer would probably be a reasonable way to distribute the software.
This is a focused spinoff of #2534 .
cc @amaurymartiny @TriplEight

Before an exe or msi installer, just a simple binary would be enough imo.

Could you please move all your 3 issues into one issue and just make a bullet list. We don't need so many redundant issues.

I created three separate issues based on I've opened this issue https://github.com/paritytech/substrate/issues/2818
I hope there will be a best practice for fast-forwarding the blockchain during testing.
System::set_block_number(System::block_number() + 1); is not sufficient if any of your runtime uses on_initialize or on_finalize.
I'm fine with either approach.

I created three separate issues based on https://github.com/paritytech/substrate/issues/2534#issuecomment-498822374
I'm fine with either approach.

I know that you created 3 separate issues, but we don't want to spam the issue tracker.


Install Infinispan operator

Closes #411

I've moved the script to provision/infinispan but it still installs the operator when the cluster is created.


v9 compatibility check

Please check if it works fine with concrete version 9. And mark it as version 9 compatible.
You may add a note on the README.md

Fixed with https://github.com/concrete5cojp/c5j_ratings/pull/15


Add support for i.redd.it

Coverage remained the same at 97.331% when pulling 69a5eb7d638b1e9a6a61385c4e0435514c32e11d on i.redd.it into 8ddc9d927bb58f22222abd9fb00fe30abc9ef1cb on master.


Support for HTTPs URL

User Story
As a developer I want to generate HTTPs URLs So that I can keep the visitors of my website safe from cyber attacks.
Acceptance Criteria

[ ] It should expose a secure flag for HTTPs URL creation.
[ ] It should generate a HTTPs URL with some default predefined configurations and the URL should work.
[ ] It should redirect a user hitting the HTTP version of the URL to the HTTPs one.

Links

Feature Request: #2191
Related issue: #2191

/kind user-story

/area url


permission fix for 2.1 cluster-manager-admin

Signed-off-by: randybrunopiverger<EMAIL_ADDRESS>regarding: open-cluster-management/backlog#11596

/retest

@Randy424 Can you please recreate PR again, this time directly on the release-2.1 branch? When you rebase to switch it to release-2.1 it makes our tests very unhappy.

@zkayyali812 Sorry about that Zach, will do. For some reason my VsCode keeps dropping the PR on main. Not sure why, but I'll try again manually.


toastr.clear($toast, { force: true }) not in version 2.1.0?

Hi all,
This is a great project!
But I wanted to say I had quite a headache trying to mimic the behavior of "Add button to force clearing a toast, ignoring focus" from your example site, because it wasn't until I dug deep down into the code that I realized the toastr.js 2.1.0 that I got from npm doesn't support the force option like the toastr.js on the example site does.
So I'm assuming the example site uses pre-release code?  If so it might cause new users fewer headaches if make the site use only the current release.
Thanks!
Andy

Hey @jedwards1211 - thanks for the input, that's good feedback.
You're correct in your understanding that the demo and repo includes code that hasn't been pushed out to the CDNs yet.
We'll look into ways to make this a bit clearer in the future.

Thanks for taking the time to read it.
-Andy
On Sat, Jan 31, 2015, at 11:30 AM, Tim Ferrell wrote:

Hey @jedwards1211[1] - thanks for the input, that's good feedback.

You're correct in your understanding that the demo and repo includes
code that hasn't been pushed out to the CDNs yet.

We'll look into ways to make this a bit clearer in the future.

— Reply to this email directly or view it on GitHub[2].

Links:

https://github.com/jedwards1211
https://github.com/CodeSeven/toastr/issues/243#issuecomment-72327117


Typo

Challenge http://www.freecodecamp.com/challenges/waypoint-create-bootstrap-wells has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
The first test case has a typo. The text "div class="col-xs-6"> elements" shouldn't have the '>' character.

I can work on this

@psteger thanks for pointing this out!

Please review the Guidelines for Contributing, thank you!.


Background tasks with activeOnStart:false shouldn't show problems if beginsPattern isn't matched

Currently, background tasks where activeOnStart is false emits problems into the Problems pane, even if beginsPattern is not matched by the output. If begin/end patterns do match, then problems are shown immediately after the matching line(s) is output. But if they begin pattern doesn't match, then problems are still shown-- albeit after a few-second delay.
I assume that this behavior is intentional as a fallback if begin/end patterns are missing. But if begin/end pattens are preset but incorrect (which will often be the case when building or troubleshooting task configs) then this behavior makes is really hard to debug the begin/end patterns because you don't know if they're working or not.
Furthermore, the problems that show up in this case cannot be removed until you close and re-open VSCode.  This means you can't tell the difference between a successful iteration of task config and left-over problems from the previous task run. If you're building a new task config, you might need 50+ iterations before getting the all the regexes right. Each iteration requires closing VSCode, reopening VSCode, re-opening the workspace, and re-running the task.  This is incredibly frustrating.
Instead of the current behavior, I suggest that VSCode should not emit any problems if all the following conditions are satisfied:

isBackground is true
activeOnStart is false
beginsPattern is present (truthy)
beginsPattern is not matched by the task output

Changing this behavior would make it clear whether a begin/end pattern pair is working or not, because if it's not working then no problems will show up in the problems pane.
BTW if you want to see the current behavior with a test repo, here are repro steps:

git clone https://github.com/justingrant/problem-matcher-cra.git
cd problem-matcher-cra
break the beginsPattern in tasks.json, e.g. by replacing "^" with "^xxxxx" at the start of the beginsPattern regex
run the npm start task using the Debug->Run Task... menu

Expected: no problems shown in the Problems pane (because beginsPattern doesn't match anything)
Actual: after a few-second delay, one problem is shown

Now press CMD+C (or Ctrl+C on Windows) to quit the task.
Break the beginsPattern in some other way, e.g. by changing "xxxxx" to "yyyyy". This simulates the normal, iterative process of building a problem matcher where you try different regxes until you get the right ones.
Go to App.tsx and comment out this line of code:

const eslintWillComplain = 'foo';

Save that file.

Expected: no errors shown in the Problems pane (because we just commented out the only line of code that was causing a problem)
Actual: the old problem persists, even though we've fixed the problem in code.
Once that persistent problem is shown, there's no way to get rid of it without closing and reopening VSCode or by running a working version of the task config, which you won't have because you generally only run into this problem when you don't (yet) have a working version of task config!

BTW I just added a demo repo and repro steps to the original request, so you can see the problem live in action in a simplified repo.

Thank you for the very detailed issue!


Deprecation warning from npm install

Hi,
I'm getting the following warning:
deprecated<EMAIL_ADDRESS>Custom ALPHABET bug fixed in v7.0.2
This might not be a breaking bug, but maybe consider upgrading the bignumber dependency?

Go

Hi, thanks for your advice!
We only import Bignumber from @0xproject/utils, and we removed this<EMAIL_ADDRESS>dependence at 0.3.1.


Add plan validation to detect duplicate VM target names.

While validating VMs, determine the effective target VM name and set a condition when the effective target name will be a duplicate.  This can happen when migrating different VMs with the same name but in different folders or DC.

Already implemented.


Auth Exploit

While only an issue if anyone wanted to actually use this in production you appear to suffer from at least one of two Mangos/Trinitycore authentication exploits that I know of. One was fixed in this commit https://github.com/TrinityCore/TrinityCore/commit/14abd1f5875d8c8e98ac9c76789d8b439008eba2 . This exploit allowed arbitrary authentication by abusing the faulty SRP6 implementation in Mangos/Trinitycore that did not ensure that all 3 "safeguards" were implemented, which you can read about here.
Most specifically the check for "The host will abort if it detects that A == 0 (mod N)." Not doing so allows for authentication to occur even when the client produces an invalid private key x.

Although there is no real net code you're right about including it for the sake of completeness and if anyone may attempt to use this as a base for something else.
Thanks for letting me know!


Fix CI

The CI on main is broken for a couple of reasons.
First we were not running the e2e tests systematically for each PRs and this PR fixes that.
Then we had some extra result overwriting ({ overwrite: true }) which was generating false positives.
We removed them but since the e2e tests weren't run on the PR, main started to fail.
To PR contains two fixes:

Add support for the origin property in shaders
Align for the box property in <Box /> with its JavaScript counterpart

I think these two fixes should be clearly separated in two pull requests since they aren't related - Would that be ok to fix before I review/approve?


Boot 1.4 Upgrade

Consider upgrading to Boot 1.4 whenever it's released.

I ran some tests against boot 1.4 and Tomcat 8.5.4. All checks out. Startup time is much faster with the embedded tomcat.


Merge pull request #3 from amarandon/master

Update from base

Coverage remained the same at 48.39% when pulling f280c3a578fcce15d494281e217f0893e6fab9aa on fgirault:thsf into 9db763a0a9bddf47c4a91ba5d0fdde908b044911 on amarandon:thsf.


discoverygo parsing error

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.08.19. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[X] I've verified and I assure that I'm running youtube-dl 2016.08.19

Before submitting an issue make sure you have:

[X] At least skimmed through README and most notably FAQ and BUGS sections
[X] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[X] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
E:\>youtube-dl http://www.discoverygo.com/the-presidents-gatekeepers/a-powerful-fraternity --verbose
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['http://www.discoverygo.com/the-presidents-gatekeepers/a-powerful-fraternity', '--verbose']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2016.08.19
[debug] Python version 3.4.4 - Windows-10-10.0.10586
[debug] exe versions: ffmpeg N-72383-g7206b94, ffprobe N-72383-g7206b94, rtmpdump 2.4
[debug] Proxy map: {}
[DiscoveryGo] a-powerful-fraternity: Downloading webpage
ERROR: An extractor error has occurred. (caused by KeyError('stream',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\extractor\common.py", line 347, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\extractor\discoverygo.py", line 56, in _real_extract
KeyError: 'stream'
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\extractor\common.py", line 347, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\extractor\discoverygo.py", line 56, in _real_extract
KeyError: 'stream'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\YoutubeDL.py", line 691, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\extractor\common.py", line 353, in extract
youtube_dl.utils.ExtractorError: An extractor error has occurred. (caused by KeyError('stream',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

E:\>youtube-dl https://www.animalplanetgo.com/north-woods-law/long-shot/ --verbose
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['https://www.animalplanetgo.com/north-woods-law/long-shot/', '--verbose']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2016.08.19
[debug] Python version 3.4.4 - Windows-10-10.0.10586
[debug] exe versions: ffmpeg N-72383-g7206b94, ffprobe N-72383-g7206b94, rtmpdump 2.4
[debug] Proxy map: {}
[DiscoveryGo] long-shot: Downloading webpage
ERROR: An extractor error has occurred. (caused by KeyError('stream',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\extractor\common.py", line 347, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\extractor\discoverygo.py", line 56, in _real_extract
KeyError: 'stream'
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\extractor\common.py", line 347, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\extractor\discoverygo.py", line 56, in _real_extract
KeyError: 'stream'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\YoutubeDL.py", line 691, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpppfzkhrf\build\youtube_dl\extractor\common.py", line 353, in extract
youtube_dl.utils.ExtractorError: An extractor error has occurred. (caused by KeyError('stream',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.animalplanetgo.com/north-woods-law/long-shot/
Single video: http://www.discoverygo.com/the-presidents-gatekeepers/a-powerful-fraternity

Description of your issue, suggested solution and other information

SIGN IN WITH YOUR TV PROVIDER
You’re just a few clicks away from the show you want to watch. Please sign in with your TV provider to watch this episode and other great programs.

it works with --cookies option:
youtube-dl -o '%(season)s/%(episode_number)s - %(title)s.%(ext)s' --cookies ~/cookies.txt https://www.ahctvgo.com/codes-and-conspiracies/founding-fathers/
[DiscoveryGo] founding-fathers: Downloading webpage
[DiscoveryGo] founding-fathers: Downloading m3u8 information
WARNING: ar subtitles not available for 55b690e76b66d1ea0a2f9633
[info] Writing video subtitles to: Season 2/1 - Founding Fathers.en.vtt
[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 270
[download] Destination: Season 2/1 - Founding Fathers.mp4
[download]  10.0% of ~1.01GiB at 301.72KiB/s ETA 34:00

Thank you!
This is the first time I have ever gotten a cookies file to work.

I hate to comment on an old closed issue, but I am clueless on how to get the cookie info for discoverygo, or really any cookie.

@dare2
I use Chrome, so these are the instructions for Chrome.

Install https://chrome.google.com/webstore/detail/cookiestxt/njabckikapfpffapmjgojcnbfjonfjfg?hl=en-US to get the cookies.txt for discoverygo.com
Play the video you want in Chrome, making sure you are logged into your provider.
Click the cookies.txt icon in the Chrome toolbar.  It looks like this:  http://i.imgur.com/wE7Kuhh.png
Copy the contents of the window to a text file. Mine is called cookies-DISCGO.txt
Use this command line to download the show:  youtube-dl.exe --restrict-filenames --continue --no-check-certificate --verbose --cookies e:\cookies-DISCGO.txt -o Bering.Sea.Gold.S07E04.mp4 https://www.discoverygo.com/bering-sea-gold/double-jeopardy/

Thank you, I found that blurb on my own, and got it to work. I had just come in here to edit/delete my comment. :)