Allow an item's proj:epsg to be a list

I have a STAC item with assets that have three different CRSs. I've included a proj:epsg for each asset but I would like to include a list of the three CRSs at the item level proj:epsg, which I am unable to do as proj:epsg only accepts a number. My workaround is to use null, but this is not ideal.
Here's an example item:
{
  "type": "Feature",
  "stac_version": "1.0.0",
  "id": "S5_09537_5435_20070531",
  "properties": {
    "eo:bands": [
      {
        "name": "B1",
        "common_name": "green",
        "description": "Green: 500-590nm",
        "center_wavelength": 0.545,
        "full_width_half_max": 0.09
      },
      {
        "name": "B2",
        "common_name": "red",
        "description": "Red: 610-680 nm",
        "center_wavelength": 0.645,
        "full_width_half_max": 0.07
      },
      {
        "name": "B3",
        "common_name": "nir",
        "description": "Near Infrared: 780-890 nm",
        "center_wavelength": 0.835,
        "full_width_half_max": 0.11
      },
      {
        "name": "B4",
        "common_name": "swir16",
        "description": "ShortWave Infrared: 1580-1750 nm",
        "center_wavelength": 1.665,
        "full_width_half_max": 0.17
      },
      {
        "name": "pan",
        "common_name": "pan",
        "description": "Panchromatic: 480-710 nm",
        "center_wavelength": 0.595,
        "full_width_half_max": 0.23
      }
    ],
    "proj:epsg": null,
    "datetime": "2007-05-31T00:00:00Z"
  },
  "geometry": {
    "type": "Polygon",
    "coordinates": [
      [
        [
          -96.23144200000002,
          54.4236535
        ],
        [
          -95.9265732,
          54.931383899999986
        ],
        [
          -95.0028628,
          54.7423039
        ],
        [
          -95.3181138,
          54.235432800000034
        ],
        [
          -96.23144200000002,
          54.4236535
        ]
      ]
    ]
  },
  "links": [
    {
      "rel": "collection",
      "href": "/media/jvrt/extradrive1/gdrive_spark/202106_spot/canada_spot5_orthoimages/collection.json",
      "type": "application/json"
    },
    {
      "rel": "root",
      "href": "/media/jvrt/extradrive1/gdrive_spark/202106_spot/catalog.json",
      "type": "application/json"
    },
    {
      "rel": "parent",
      "href": "/media/jvrt/extradrive1/gdrive_spark/202106_spot/canada_spot5_orthoimages/S5_2007/catalog.json",
      "type": "application/json"
    },
    {
      "rel": "self",
      "href": "/media/jvrt/extradrive1/gdrive_spark/202106_spot/canada_spot5_orthoimages/S5_2007/S5_09537_5435_20070531/S5_09537_5435_20070531.json",
      "type": "application/json"
    }
  ],
  "assets": {
    "m20_lcc00": {
      "href": "http://ftp.geogratis.gc.ca/pub/nrcan_rncan/image/spot/geobase_orthoimages/s5_09537_5435_20070531/s5_09537_5435_20070531_m20_lcc00.zip",
      "type": "application/zip",
      "title": "m20_lcc00",
      "description": "Multi-band imagery in EPSG:3979",
      "gsd": 20.0,
      "proj:epsg": 3979,
      "roles": [
        "data"
      ]
    },
    "m20_utm14": {
      "href": "http://ftp.geogratis.gc.ca/pub/nrcan_rncan/image/spot/geobase_orthoimages/s5_09537_5435_20070531/s5_09537_5435_20070531_m20_utm14.zip",
      "type": "application/zip",
      "title": "m20_utm14",
      "description": "Multi-band imagery in EPSG:26914",
      "gsd": 20.0,
      "proj:epsg": 26914,
      "roles": [
        "data"
      ]
    },
    "m20_utm15": {
      "href": "http://ftp.geogratis.gc.ca/pub/nrcan_rncan/image/spot/geobase_orthoimages/s5_09537_5435_20070531/s5_09537_5435_20070531_m20_utm15.zip",
      "type": "application/zip",
      "title": "m20_utm15",
      "description": "Multi-band imagery in EPSG:26915",
      "gsd": 20.0,
      "proj:epsg": 26915,
      "roles": [
        "data"
      ]
    },
    "p10_lcc00": {
      "href": "http://ftp.geogratis.gc.ca/pub/nrcan_rncan/image/spot/geobase_orthoimages/s5_09537_5435_20070531/s5_09537_5435_20070531_p10_lcc00.zip",
      "type": "application/zip",
      "title": "p10_lcc00",
      "description": "Panchromatic imagery in EPSG:3979",
      "gsd": 10.0,
      "proj:epsg": 3979,
      "roles": [
        "data"
      ]
    },
    "p10_utm14": {
      "href": "http://ftp.geogratis.gc.ca/pub/nrcan_rncan/image/spot/geobase_orthoimages/s5_09537_5435_20070531/s5_09537_5435_20070531_p10_utm14.zip",
      "type": "application/zip",
      "title": "p10_utm14",
      "description": "Panchromatic imagery in EPSG:26914",
      "gsd": 10.0,
      "proj:epsg": 26914,
      "roles": [
        "data"
      ]
    },
    "p10_utm15": {
      "href": "http://ftp.geogratis.gc.ca/pub/nrcan_rncan/image/spot/geobase_orthoimages/s5_09537_5435_20070531/s5_09537_5435_20070531_p10_utm15.zip",
      "type": "application/zip",
      "title": "p10_utm15",
      "description": "Panchromatic imagery in EPSG:26915",
      "gsd": 10.0,
      "proj:epsg": 26915,
      "roles": [
        "data"
      ]
    },
    "thumbnail": {
      "href": "/media/jvrt/extradrive1/gdrive_spark/202106_spot/canada_spot5_orthoimages/S5_2007/S5_09537_5435_20070531/s5_09537_5435_20070531_tn.jpg",
      "type": "image/jpeg",
      "roles": [
        "thumbnail"
      ]
    },
    "B4": {
      "href": "/media/jvrt/extradrive1/gdrive_spark/202106_spot/canada_spot5_orthoimages/S5_2007/S5_09537_5435_20070531/s5_09537_5435_20070531_m20_4_utm14_cog.tif",
      "type": "image/tiff; application=geotiff; profile=cloud-optimized",
      "title": "B4",
      "eo:bands": [
        {
          "name": "B4",
          "common_name": "swir16",
          "description": "ShortWave Infrared: 1580-1750 nm",
          "center_wavelength": 1.665,
          "full_width_half_max": 0.17
        }
      ],
      "proj:epsg": 26914,
      "proj:transform": [
        20.0,
        0.0,
        679560.0,
        0.0,
        -20.0,
        6091580.0,
        0.0,
        0.0,
        1.0
      ],
      "proj:bbox": [
        679560.0,
        6015900.0,
        757320.0,
        6091580.0
      ],
      "proj:wkt2": "PROJCS[\"NAD83 / UTM zone 14N\",GEOGCS[\"NAD83\",DATUM[\"North_American_Datum_1983\",SPHEROID[\"GRS 1980\",6378137,298.257222101,AUTHORITY[\"EPSG\",\"7019\"]],AUTHORITY[\"EPSG\",\"6269\"]],PRIMEM[\"Greenwich\",0,AUTHORITY[\"EPSG\",\"8901\"]],UNIT[\"degree\",0.0174532925199433,AUTHORITY[\"EPSG\",\"9122\"]],AUTHORITY[\"EPSG\",\"4269\"]],PROJECTION[\"Transverse_Mercator\"],PARAMETER[\"latitude_of_origin\",0],PARAMETER[\"central_meridian\",-99],PARAMETER[\"scale_factor\",0.9996],PARAMETER[\"false_easting\",500000],PARAMETER[\"false_northing\",0],UNIT[\"metre\",1,AUTHORITY[\"EPSG\",\"9001\"]],AXIS[\"Easting\",EAST],AXIS[\"Northing\",NORTH],AUTHORITY[\"EPSG\",\"26914\"]]",
      "gsd": 20.0,
      "roles": [
        "data"
      ]
    },
    "B2": {
      "href": "/media/jvrt/extradrive1/gdrive_spark/202106_spot/canada_spot5_orthoimages/S5_2007/S5_09537_5435_20070531/s5_09537_5435_20070531_m20_2_utm14_cog.tif",
      "type": "image/tiff; application=geotiff; profile=cloud-optimized",
      "title": "B2",
      "eo:bands": [
        {
          "name": "B2",
          "common_name": "red",
          "description": "Red: 610-680 nm",
          "center_wavelength": 0.645,
          "full_width_half_max": 0.07
        }
      ],
      "proj:epsg": 26914,
      "proj:transform": [
        20.0,
        0.0,
        679560.0,
        0.0,
        -20.0,
        6091580.0,
        0.0,
        0.0,
        1.0
      ],
      "proj:bbox": [
        679560.0,
        6015900.0,
        757320.0,
        6091580.0
      ],
      "proj:wkt2": "PROJCS[\"NAD83 / UTM zone 14N\",GEOGCS[\"NAD83\",DATUM[\"North_American_Datum_1983\",SPHEROID[\"GRS 1980\",6378137,298.257222101,AUTHORITY[\"EPSG\",\"7019\"]],AUTHORITY[\"EPSG\",\"6269\"]],PRIMEM[\"Greenwich\",0,AUTHORITY[\"EPSG\",\"8901\"]],UNIT[\"degree\",0.0174532925199433,AUTHORITY[\"EPSG\",\"9122\"]],AUTHORITY[\"EPSG\",\"4269\"]],PROJECTION[\"Transverse_Mercator\"],PARAMETER[\"latitude_of_origin\",0],PARAMETER[\"central_meridian\",-99],PARAMETER[\"scale_factor\",0.9996],PARAMETER[\"false_easting\",500000],PARAMETER[\"false_northing\",0],UNIT[\"metre\",1,AUTHORITY[\"EPSG\",\"9001\"]],AXIS[\"Easting\",EAST],AXIS[\"Northing\",NORTH],AUTHORITY[\"EPSG\",\"26914\"]]",
      "gsd": 20.0,
      "roles": [
        "data"
      ]
    },
    "B3": {
      "href": "/media/jvrt/extradrive1/gdrive_spark/202106_spot/canada_spot5_orthoimages/S5_2007/S5_09537_5435_20070531/s5_09537_5435_20070531_m20_3_utm14_cog.tif",
      "type": "image/tiff; application=geotiff; profile=cloud-optimized",
      "title": "B3",
      "eo:bands": [
        {
          "name": "B3",
          "common_name": "nir",
          "description": "Near Infrared: 780-890 nm",
          "center_wavelength": 0.835,
          "full_width_half_max": 0.11
        }
      ],
      "proj:epsg": 26914,
      "proj:transform": [
        20.0,
        0.0,
        679560.0,
        0.0,
        -20.0,
        6091580.0,
        0.0,
        0.0,
        1.0
      ],
      "proj:bbox": [
        679560.0,
        6015900.0,
        757320.0,
        6091580.0
      ],
      "proj:wkt2": "PROJCS[\"NAD83 / UTM zone 14N\",GEOGCS[\"NAD83\",DATUM[\"North_American_Datum_1983\",SPHEROID[\"GRS 1980\",6378137,298.257222101,AUTHORITY[\"EPSG\",\"7019\"]],AUTHORITY[\"EPSG\",\"6269\"]],PRIMEM[\"Greenwich\",0,AUTHORITY[\"EPSG\",\"8901\"]],UNIT[\"degree\",0.0174532925199433,AUTHORITY[\"EPSG\",\"9122\"]],AUTHORITY[\"EPSG\",\"4269\"]],PROJECTION[\"Transverse_Mercator\"],PARAMETER[\"latitude_of_origin\",0],PARAMETER[\"central_meridian\",-99],PARAMETER[\"scale_factor\",0.9996],PARAMETER[\"false_easting\",500000],PARAMETER[\"false_northing\",0],UNIT[\"metre\",1,AUTHORITY[\"EPSG\",\"9001\"]],AXIS[\"Easting\",EAST],AXIS[\"Northing\",NORTH],AUTHORITY[\"EPSG\",\"26914\"]]",
      "gsd": 20.0,
      "roles": [
        "data"
      ]
    },
    "B1": {
      "href": "/media/jvrt/extradrive1/gdrive_spark/202106_spot/canada_spot5_orthoimages/S5_2007/S5_09537_5435_20070531/s5_09537_5435_20070531_m20_1_utm14_cog.tif",
      "type": "image/tiff; application=geotiff; profile=cloud-optimized",
      "title": "B1",
      "eo:bands": [
        {
          "name": "B1",
          "common_name": "green",
          "description": "Green: 500-590nm",
          "center_wavelength": 0.545,
          "full_width_half_max": 0.09
        }
      ],
      "proj:epsg": 26914,
      "proj:transform": [
        20.0,
        0.0,
        679560.0,
        0.0,
        -20.0,
        6091580.0,
        0.0,
        0.0,
        1.0
      ],
      "proj:bbox": [
        679560.0,
        6015900.0,
        757320.0,
        6091580.0
      ],
      "proj:wkt2": "PROJCS[\"NAD83 / UTM zone 14N\",GEOGCS[\"NAD83\",DATUM[\"North_American_Datum_1983\",SPHEROID[\"GRS 1980\",6378137,298.257222101,AUTHORITY[\"EPSG\",\"7019\"]],AUTHORITY[\"EPSG\",\"6269\"]],PRIMEM[\"Greenwich\",0,AUTHORITY[\"EPSG\",\"8901\"]],UNIT[\"degree\",0.0174532925199433,AUTHORITY[\"EPSG\",\"9122\"]],AUTHORITY[\"EPSG\",\"4269\"]],PROJECTION[\"Transverse_Mercator\"],PARAMETER[\"latitude_of_origin\",0],PARAMETER[\"central_meridian\",-99],PARAMETER[\"scale_factor\",0.9996],PARAMETER[\"false_easting\",500000],PARAMETER[\"false_northing\",0],UNIT[\"metre\",1,AUTHORITY[\"EPSG\",\"9001\"]],AXIS[\"Easting\",EAST],AXIS[\"Northing\",NORTH],AUTHORITY[\"EPSG\",\"26914\"]]",
      "gsd": 20.0,
      "roles": [
        "data"
      ]
    },
    "pan": {
      "href": "/media/jvrt/extradrive1/gdrive_spark/202106_spot/canada_spot5_orthoimages/S5_2007/S5_09537_5435_20070531/s5_09537_5435_20070531_p10_1_utm14_cog.tif",
      "type": "image/tiff; application=geotiff; profile=cloud-optimized",
      "title": "pan",
      "eo:bands": [
        {
          "name": "pan",
          "common_name": "pan",
          "description": "Panchromatic: 480-710 nm",
          "center_wavelength": 0.595,
          "full_width_half_max": 0.23
        }
      ],
      "proj:epsg": 26914,
      "proj:transform": [
        10.0,
        0.0,
        679560.0,
        0.0,
        -10.0,
        6091580.0,
        0.0,
        0.0,
        1.0
      ],
      "proj:bbox": [
        679560.0,
        6015900.0,
        757320.0,
        6091580.0
      ],
      "proj:wkt2": "PROJCS[\"NAD83 / UTM zone 14N\",GEOGCS[\"NAD83\",DATUM[\"North_American_Datum_1983\",SPHEROID[\"GRS 1980\",6378137,298.257222101,AUTHORITY[\"EPSG\",\"7019\"]],AUTHORITY[\"EPSG\",\"6269\"]],PRIMEM[\"Greenwich\",0,AUTHORITY[\"EPSG\",\"8901\"]],UNIT[\"degree\",0.0174532925199433,AUTHORITY[\"EPSG\",\"9122\"]],AUTHORITY[\"EPSG\",\"4269\"]],PROJECTION[\"Transverse_Mercator\"],PARAMETER[\"latitude_of_origin\",0],PARAMETER[\"central_meridian\",-99],PARAMETER[\"scale_factor\",0.9996],PARAMETER[\"false_easting\",500000],PARAMETER[\"false_northing\",0],UNIT[\"metre\",1,AUTHORITY[\"EPSG\",\"9001\"]],AXIS[\"Easting\",EAST],AXIS[\"Northing\",NORTH],AUTHORITY[\"EPSG\",\"26914\"]]",
      "gsd": 10.0,
      "roles": [
        "data"
      ]
    }
  },
  "bbox": [
    -96.23144200000002,
    54.235432800000034,
    -95.0028628,
    54.931383899999986
  ],
  "stac_extensions": [
    "https://stac-extensions.github.io/eo/v1.0.0/schema.json",
    "https://stac-extensions.github.io/projection/v1.0.0/schema.json"
  ],
  "collection": "canada_spot5_orthoimages"
}

What's the use-case for specifying multiple EPSGs at the item level instead of just iterating through the assets and collecting the EPSGs in a set?

In this case you just wouldn't specify proj:epsg code at all in the Item, although you could specify a list of EPSG in the summaries block of the Collection.

@gadomski The set would be held at the collection level? If so, that's the solution I went with, as @matthewhanson suggests.
I don't know how often this will crop up - it may just be an edge case from the way the stactools-packages/spot data is held, where each image tile is provided in multiple projections, each with a different use. It could be worth mentioning the best practise in the stac-extensions/projection docs if it's something either of you think is common enough to warrant it. I'm happy to do that.

It could be worth mentioning the best practise in the stac-extensions/projection docs if it's something either of you think is common enough to warrant it. I'm happy to do that.

Great! Maybe something like:

If an Item has Assets in more than one coordinate reference system, use the projection extension to set coordinate reference system information on each Asset, not on the Item itself. It is strongly recommended to include all coordianate reference systems in the Item's Collection summaries.

Proposed with slight modifications in https://github.com/stac-extensions/projection/compare/main...jamesvrt:patch-1


All settings are repeated multiple times

When I try to edit the settings there are only two options, but they are each repeated 8 times. See the attached screenshot.

I forgot to add literally one line :smile:. It sould be fixed in the next update.
Thanks for pointing it out.

This should be fix by now.


IA-1022 Lqas/IM send country to api

Changes

modify getLqasIm to take a countryId param and pass it through the query
adapt query hooks accordingly
pass country param to all components using query hooks
api.py: only loop through forms from country that was passed through request
Campaigns select box: adapt loading prop to be active on isFetching

Nothing blocking. Just noticed you spread the country id everywhere. In this case redux can be a good solution.

Don't say that word 😉. Context api would work just as well, and  with way less boilerplate 😁


Add service name uri validation in cloud_controller

Once create a service that name has a invalid uri, we cannot delete the service.
$ vmc create-service redis "[test]"
Creating Service: OK
$ vmc delete-service "[test]"
Deleting service test: Cannot access target (bad URI: http://api.cloudfoundry.com/services/[test])
This patch fix the problem to validate service name uri before provisioning.

Thanks for pointing this out.  We're not sure if we are going to take this or not though.  We are going to look at fixing VMC and the CC to uri encode/decode the service name parameter as an alternative.  We're going to leave this open for the moment though.
Thanks


Add EditorConfig

I would advise you to use EditorConfig. Thanks :)

The repository has some coding rule conflicts. I think these also should be fixed.
Indent size
2 spaces
https://github.com/RogueException/Discord.Net/blob/9979a027d54c355fb344eee975ded1ed67a6d291/src/Discord.Net/Discord.Net.nuspec#L2-L4
4 spaces
https://github.com/RogueException/Discord.Net/blob/9979a027d54c355fb344eee975ded1ed67a6d291/src/Discord.Net/Discord.Net.nuspec#L14-L16
Indent character
space
https://github.com/RogueException/Discord.Net/blob/9979a027d54c355fb344eee975ded1ed67a6d291/docs/guides/commands/samples/groups.cs#L3-L5
character tabulation
https://github.com/RogueException/Discord.Net/blob/9979a027d54c355fb344eee975ded1ed67a6d291/docs/guides/commands/samples/module.cs#L3-L5
Two lines of if block
without newline
https://github.com/RogueException/Discord.Net/blob/9979a027d54c355fb344eee975ded1ed67a6d291/docs/guides/voice/samples/joining_audio.cs#L6
with newline
https://github.com/RogueException/Discord.Net/blob/9979a027d54c355fb344eee975ded1ed67a6d291/src/Discord.Net.Commands/CommandParser.cs#L47-L51
One line of method
block
https://github.com/RogueException/Discord.Net/blob/9979a027d54c355fb344eee975ded1ed67a6d291/src/Discord.Net.DebugTools/UnstableRestClient.cs#L149-L152
block with an if block
https://github.com/RogueException/Discord.Net/blob/9979a027d54c355fb344eee975ded1ed67a6d291/src/Discord.Net.Core/Format.cs#L18-L24
inline with ternary operator
https://github.com/RogueException/Discord.Net/blob/9979a027d54c355fb344eee975ded1ed67a6d291/src/Discord.Net.Core/CDN.cs#L7-L8


Fix issue where wrong layout would be used when launched in small window

Resolved / Related Issues
Items resolved / related issues by this PR.

Closes #5801

Details of Changes
Add details of changes here.

Manually check and invoke visual states in main page on loaded
Fix issue where tab would not be selected when invoked with arguments (attempt 3)
fix issue where base section of accent colored icons would be invisible when using hc mode

Validation
How did you test these changes?

[x] Built and ran the app
[ ] Tested the changes for accessibility

Screenshots (optional)
Add screenshots here.

Thank you!


Hover mode saving issue - dev

Hello again !
Thanks a lot for your continuous improvements ! The new tools on the dev plugin are very useful and the next ones look very promising !
I just wanted to point out a strange behaviour of the Hover mode you may be already aware of : whenever it is enabled, saving a feature requires to disable hover mode, otherwise the saved feature is the last one prompted by the Hover mode, overwriting the segmented zone formed by the addition of a FG point. Here is a capture to better understand what I am trying to depict
https://github.com/coolzhao/Geo-SAM/assets/120014072/8265b853-2a2a-421a-b11b-4f44f453a20f

My previous comment was about the bug at the end of your video. Regarding your description, the hover mode currently only provides a preview for the prompt to help you make a better prompt selection. Only the prompt after clicking the mouse will be truly recorded. The bug at the end of the video seems to be triggered when no prompt is provided during saving. In addition to that, we have provided keyboard shortcuts for commonly used buttons. When you hover your mouse over a button, there will be a tooltip with text. Using keyboard shortcuts will be more convenient.

Thanks for your answer ! Yes the use of shortcuts should be more convenient


Develop

Maybe one need to check parallelization of Band::solve_for_kset after I moved here this code from K_set::find_eigen_states

Maybe one need to check parallelization of Band::solve_for_kset after I moved here this code from K_set::find_eigen_states. But it seems to be working well as before


Please upgrade to JSDOM 13.2

In<EMAIL_ADDRESS>the JSDOM 11.5.1 is referenced. But that version does not support mutationObserver. The latest JSDOM 13.2.0 does support mutationObserver.
In the past we had to rely on:

solution 1
solution 2

Reference to mutation observer in JSDOM
many tnx in advance

We cannot currently do this, see e.g. https://github.com/facebook/jest/pull/7763 for details. jest-environment-jsdom-thirteen (see comment in the linked PR) might be a better workaround for you.

tnx for your swift reply.
Closing this issue


create discord events for homeworks and tests

1 week before test
2 days before homework
In same listener: send message with event link in class channel
In another listener: send reminder on day before
To think about: add a custom role for event notifications?

Depends #9


Release new version

Would be awesome to have new version with fastify 4 support!

Happy to, but I am not sure what should be changed to support it. Or do you mean just to bump the version and release a 3.0.0.

You are already running tests on v4, so if they are passing, it should be good.

Thanks for checking :smile: Going to close this issue then if this is not for just releasing a version.

It is specifically for releasing a version. Is there any timeline for doing so?

oh sorry, my misunderstanding then. I could

https://github.com/gkampitakis/fastify-custom-healthcheck/commit/a242dc20a297d8f7b4fbfd3681bdc3faa5b16093 Done :tada:


Fork

Hey spiderneo, was the fork just to get rid of the deprecated warning on compile? Or were you having an issue. We've just seen iPad errors where the time picker doesn't show for landscape mode.

Hi Stevenpack,
No i had real errors, i don't recall the version of Ipad.
But that's why i fork it, not just for warning ;)


Unable to build using --prod flag. Indeterminable error returned during UglifyJs process.

Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [ ] new
- [x] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

Node: 8.11.1
Npm: 5.6.0
Angular Cli: 6.1.5
Repro steps

Building with --prod, e.g. ng build --prod returns an error:
ERROR in main.55704d1fa620b76d62c5.js from UglifyJs
Unexpected token: punc ()) [main.55704d1fa620b76d62c5.js:75494,2]

As per #5741 I attempted to troubleshoot this issue by adding the --source-map flag, e.g. ng build --prod --source-map and the build is successful, with no errors reported. As the output has been Uglified I am unable to find the line number that is being referenced to determine the cause of this problem.
Why is it that the build would be successful with the --source-map flag added? Is this normal behaviour?
The log given by the failure

As above.
Desired functionality

Build should be successful.
Mention any other details that might be useful

Seems to be related to #5741 but I am not sure how identify the problem to resolve this issue.
Any help will be greatly appreciated!

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

Closing as no repro has been provided.


[MODEL EVALUATION REQUEST] Phi-3-mini-4k-instruct-dansk

Model ID
emillykkejensen/Phi-3-mini-4k-instruct-dansk
Model type
Decoder model (e.g., GPT)
Model languages

[X] Danish
[x] Swedish
[x] Norwegian (Bokmål or Nynorsk)
[ ] Icelandic
[ ] Faroese
[ ] German
[ ] Dutch
[ ] English

Merged model
Not a merged model

This requires Phi3 to be supported in vLLM. This vLLM PR merged that functionality into main, so waiting for the next release to benchmark it.

Live now!
https://scandeval.com/danish-nlg/


add function to calculate tx digest

Thank you for working on this and sorry for the late review. I made two improvements based on this PR in https://github.com/MystenLabs/sui/pull/6384

add end to end test to make sure the logic on TS side is always in sync with Rust
add the getTransactionDigest method to the SignerWithProvider Class


Update meshmodel docs

Notes for Reviewers
This PR fixes #
Signed commits

[ ] Yes, I signed my commits.

🚀 Preview for commit da98dac908ca15ca9293ef2a8916e4fe06c86989 at: https://64b65175d67cc24465644297--meshery-docs-preview.netlify.app

@Boombag0607 FYI


Debug console switcher doesn't do anything

Debug two things
Open the debug console dropdown, select a different session
Nothing happens

Same thing for me, although I'm using the compound debug target here:
https://github.com/Microsoft/vscode-extension-samples/blob/master/lsp-sample/.vscode/launch.json#L38-L43

Switch to "Launch Client"
Click "Terminal"
Click "Debug Console"
🐛 Target is back to "Attach to Server"

Thanks for reporting and for self-hosting!


Allowlist.json file example and usage

Having a hard time getting the allowlist.json file to work. Keep getting the user has not been invited message when connecting. Can we please add some example of how to set this up properly? Format of the allowlist.json and usage with the right environment variables.
Is ALLOW_LIST_USERS a comma separated xuids,  uuids? or usernames?

I should probably update the section heading, but this is the description and example:
https://github.com/itzg/docker-minecraft-bedrock-server#whitelist

I think the wiki page that you reference might have to be updated.  Does the allowlist.json still use UUID's for users, or just XBox Gamertags?

The new section link is https://github.com/itzg/docker-minecraft-bedrock-server/tree/master#allowlist
As for ALLOW_LIST_USERS it is a list of Xbox gamer tags.

Here what worked for me, sample allowlist.json
[
  {
    "name": "XBOX USERNAME",
    "xuid": "xuid gotten from website below"
  },
  ....
]

To get xuid, look at: https://cxkes.me/xbox/xuid
Type xbox username and copy the XUID (DEC) given. This value is what you use in the allowlist.json xuid field.

There are ways Minecraft has automated the creation of the allowlist.json file. You just have to enter the console command "allowlist add " and it will automatically add the xuid to the file when a player with the matching gamertag joins. It's all outlined in the "bedrock_srver_how_to.html" file as of writing this.

Good point @racecarburton . That could be utilized by running the commands this way https://github.com/itzg/docker-minecraft-bedrock-server/tree/master#executing-server-commands
Being able to pre-assign those users on a freshly created container is also useful, but gets into this challenge of finding those XUIDs to assign.


SharedCacheCredential should allow specifying client ID

This is needed for calling Microsoft Graph

This appears to be resolved - ClientId can be specified in SharedTokenCacheCredentialOptions


Migrated creation date?

When I run the sample migration-utils, I do not see a premis:hasDateCreatedByApplication. Is the README wrong or the code? Or should I be looking somewhere else?

I see it now, thank you @ruebot!


Restore system backup gives problem

Environment

Xcode version: 11.3.1
Firebase SDK version: 6.14.0
Firebase Component: FirebaseRemoteConfig
Component version: 4.4.6

Description
I having an app with integrated Firebase remote config. I take a backup of all application and restore it again in the same iPhone/other iPhone. After the restoring backup, Firebase remote config is stopped working until the reinstall app again from AppStore, So some depended functions are not working in the live app.
The app is working normally after reinstalling from AppStore.
Getting error from Firebase Remote config is The operation couldn't be completed. (com.google.remoteconfig.ErrorDomain error 8003.)
Same issue on stackoverflow
Steps to reproduce:

Run app (remote config fetched success)
Backup ios system
Restore backup ios system
Run app (remote config gives 0 keys)

We are also experiencing this problem, any updates here? We have some key app feature relying on a valid remote config.

@Goseong, I'm sorry to hear if this issue is negatively affecting your users. I have made a follow up internally, and we'll inform you as soon as we have an update.

Hi all, this issue has been fixed in the latest release of SDK as shown here. Feel free to comment here if you're still experiencing an issue on restoring your backup, and we'll reopen this thread to continue investigating it.

Great, thank you for the work!


"This Team" list is now blank in version 2.0

Hi there,
I just applied the update 2.0 you worked hard on, but now the "This Team" tab/list is empty and I can no longer see all the members of my team without having to pin them. Is there a way to bring it back?

Working on it now

TeamLink_2_0_0_1_managed.zip
@slickspidey - can you check this works for you.  There was a filtering error on the buttons.

TeamLink_2_0_0_1_managed.zip
@slickspidey - can you check this works for you. There was a filtering error on the buttons.

@stuartridout that fixed it! Thank you!
Btw, is there a way to display all members of my team in the "This Team" list? It is currently capped at 100 rows, but I have more than 100 team members. I attempted to change the number of rows in the code, but it remains at 100 rows.

TeamLink_2_0_0_2_managed.zip
Could you try this version please to see if that fixes it.  It should work up to 999 team members now.

Hi @stuartridout, I just installed it but now it's showing significantly fewer members than before. Previously, the list would display team members with names starting from "A" to "T", but now it is only showing members from "A" to "N".

How many team members are there in the Team?

TeamLink_2_0_0_3_managed.zip
Let's try again @slickspidey ... for some strange reason I had restricted the results to the first 90.

@stuartridout I have a team of 117 people right now. We can see everyone now, that's perfect! Thank you!
I am trying to use MS Power BI to create a table that displays the office presence status of employees in my organization, as recorded in the "cr599_presence" table in MS Dataverse. However, the table is showing inflated numbers for some employees and I am not sure why. I am trying to show a count of the unique presence entries for each staff member, but some are showing more than the expected 5 entries for a week. Can you help me understand why this is happening or how to correctly show the count of presence entries for each employee? I have included an image for reference.

Can you raise a new issue for this one.
Thanks


Add access to preferences

Pull Request Test Coverage Report for Build 12

3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 7:
0.0%

Covered Lines:
76

Relevant Lines:
76

💛  - Coveralls


remove gdal dependency from the get hsi script

Worked on creating a file with only the functions needed for (1) extracting the hsi data from the h5 and (2) get solar/sensor angles for calculating topographic and bidirectional scattering correction. This is also solving #41


release: v0.17.2

Coverage increased (+0.03%) to 86.576% when pulling 41d0e721f3af7a2a9f731f773791dfd86a985264 on lnielsen:rel-v0.17.2 into e4dffbab54a1da773440d802fceeb5221de86d69 on inveniosoftware:master.


Update release notes for v3.1.0

Description

Update release notes to reflect v3.1.0 release
Motivation and Context

There's been a fair amount of change in the repo since the last release, thought it would be good to make a new release
Checklist:

[x] My change requires a change to the documentation or CHANGELOG.
[x] I have updated the documentation/CHANGELOG accordingly.
[x] I have created a feature (non-master) branch for my PR.

Do we want to mention something about the flushing-interval default change in https://github.com/pusher/oauth2_proxy/pull/23?

I can put something under important notes, any idea what we should say?

Streamed responses will now be flushed every 1 second by default. Previously streamed responses were flushed only when the buffer was full. To retain the old behaviour set --flush-interval=0.

Yeah that sounds good. Would also add a link to the PR for further reference.


Hellow, how can i set my crop size

What do you mean?

Set a size like 800x600, no more no less for example

Yes you can with
.setMinCropResultSize(800,600)
.setMaxCropResultSize(800,600)


Launch & Login Screen

launch logo
ic launcher
splash background
login BG
font replaced by Open Sans and respective files changed
font colors
button colors
changed sign up btn content
Description
LEARNER-XXXX
Add a description of your changes here.
Notes

Example: Use example.sandbox.edx.org to test against
Example: This PR will not address x,y, and z, because of a, b, and c.
Example: Feature is behind a flag
Example: Why I didn't add any tests

Testing

[ ] i18n
[ ] RTL
[ ] safecommit shows 0 violations
[ ] Unit, integration, acceptance tests as appropriate
[ ] Analytics
[ ] Performance
[ ] Database migrations are backwards-compatible

Thanks for the pull request, @ishtiaqshaheer-kognoz! I've created OSPR-5958 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.
:warning: We can't start reviewing your pull request until you've submitted a     signed contributor agreement     or indicated your institutional affiliation. Please see the CONTRIBUTING     file for more information.

@ishtiaqshaheer-kognoz Thank you for the contribution! Once you have signed our Contributor Agreement and it has been processed, you will receive a confirmation via email from our Legal team. We then will be able to review this and all your future code contributions.

@ishtiaqshaheer-kognoz Even though your pull request wasn’t merged, please take a moment  to answer a two question survey so we can improve your experience in the future.


Can you tell me how to switch node:crypto to crypto-js implementation?

I want to port this API to ArkTs, but ArkTs cannot use node:crypto.

In case you haven't fixed the issue, you can set globalThis.crypto to something implementing the webcrypto API (or just the getRandomValues method which is the only one used here).


"Login with web wallet" shouldn't redirect to web wallet if wallet available as extension or in parent frames

Today I have faced this on https://develop.aggregator.z52da5wt.xyz/meet

The Superhero extension was initialized and able to sign JWT challenge. After pressing "Login with web wallet" I have been redirected to web wallet:

To fix this, I'm proposing

to run aepp wallet detector (from sdk) right after page loads
when the user clicks "Login with web wallet":

use wallet if wallet detector found one
redirect to web wallet otherwise

to run aepp wallet detector (from sdk) right after page loads

already implemented in first version
I just hide that button at all if wallet was found. Please check the commit above.

On tip_button.test.league.aeternity.org button seems disappeared, but I can't check it for sure because I don't have moderator rights


Missing parent: [GO term] histone H3K36 methyltransferase activity

GO term ID and label for which you request a new superclass

GO:0046975 | histone H3K36 methyltransferase activity

New superclass (parent) suggested
GO:0018024 | histone lysine N-methyltransferase activity

according to the defs

Also added this parent to the other H3Knumber activities (K27, K37, K4, K56, K79, andK9)
Done

Hi,
just wondering of this is a good axis of classification - with @colinlog we wanted to remove the classification by amino acid, to only keep by histones. Specifically, we have two axes of classification for 'histone methyltransferase activity':
by residue:
'histone arginine N-methyltransferase activity'
'histone glutamine N-methyltransferase activity'
'histone lysine N-methyltransferase activity'
by histone:
'histone H2A methyltransferase activity'
'histone H3 methyltransferase activity'
'histone H4 methyltransferase activity'
We wanted to remove the classification by residue. Is that OK for you?
(Note that we have the same issue for kinase activity; not all modifications have these 2 axes)
Thanks, Pascale

Then methyltransferases would be different from all of the other modifiers, and we would lose specificity
e.g.
SPAC29B12.02c | set2 | histone lysine H3-K36 methyltransferase Set2
SPCC297.04c | set7 | histone lysine H3-K37 methyltransferase Set7
SPCC306.04c | set1 | histone lysine H3-K4 methyltransferase Set1
SPBC428.08c | clr4 | histone lysine H3-K9 methyltransferase Clr4
SPCC4B3.12 | set9 | histone lysine H4-K20 methyltransferase Set9
This would make modelling more difficult.
I thought we decided years ago that we would model histones in a residue-specific way so that we could capture the histone code. I and the specific modified residues are important for the recruitment of effectors of specific downstream pathways. I don't know how I would do this otherwise.
What is the rationale?

@ValWood , I suppose you could get a PRO id for each specific proteoform and position and then use 'has output' for the activity annotation (say histone lysine methyltransferase activity has output specific id for H3-K9. Just a thought

I don't have a way to do has_output,  and this would be different from  the way we have been doing all of the other histone modifications for years.
We already request PRO Ids for  active forms  and for substrates. For example,
for example
[histone H3K9 methyltransferase activity]
clr4 has substrate hht1 (InitMet-/Ubiq:(K14)) involved in pericentric heterochromatin formation
(here the input to clf4 H3K9 methyltransferase is a hht already ubiquitinated on K14)
Nobody  uses has_output in extensions only has_input. This would add another level of complication because we already need to think about the active (modified) form of the entity itself and the modified form of the substrate without adding the output of the substrate (which would need to differentiated from the modified form of the input).
It seems to be making everything unnecessarily complicated, especially when the current system  works really well.

Q how would the uses find/query  the
histone lysine H3K37 methyltransferase
or the
histone H3K4 acetyltransferase activity
We already did the big clean up of removing the equivalent process terms, but these MF specificities are really useful for linking MF to the different specific BPs that they regulate or are part of.

Out of date. Amino acid classification will go.
Histone and residue will stay.


Dev Containers | Align line length between black and flake

Align line length between black and flake to 88 (black's default)

LGTM. Is 88 actually the right length?

I don't think there is an agreed upon right length in the Python community, but this is black's default: https://black.readthedocs.io/en/stable/the_black_code_style/current_style.html#line-length.


Use sass binary url from .npmrc if available

This PR adds the possibility to configure the sass-binary URL in the .npmrc configuration file (e.g.  sass_cdnurl=http://example.com/sass-binaries). This is also used the same way in PhantomJS by pointing the download URL to a mirror without having to set an environment variable manually.

Cool, that looks like something we've been looking for!

That's cool, but let's get at least naming consistent. #1143 is a nice attempt to document those.
Also in the implementation we should just wrap the names of all parameters with npm_config_ and looks them up in the environment.

Totally agree. I hope npm_config_sass_binary_site is ok as name. I'll also take care of the documentation and add it to this PR.
The second point I didn't really get. What's your idea there?

Firstly, thanks for your contribution @fh1ch, we appreciated.
Secondly, some house keep. I the future it's preferred you open an issue to discuss new features before implementing them. Odds are something similar has previously been discussed, or the team may already have plans in the area of interest.
With regards to configuration we do have plans for standardising on nodeSassConfig in package.json to address concerns we have about code portability. In this case however it doesn't preclude your proposed addition.

Specifically to this PR we currently support 3 ENV variable that affect the binary download and/or resolution process, BINARY_PATH, BINARY_SITE, and BINARY_NAME. This PR should add support for all these variables, as well test coverage for these new options.

I :cupid pull requests :)
@fh1ch check this out https://github.com/sass/node-sass/blob/master/scripts/build.js#L133-L136

we just transform the same string into the command line option and the environment variable name.

One just needs probably to stick ' || process.env['npm_config_' + subject]' somewhere to make it work as you propose.

we should just wrap the names of all parameters with npm_config_ and look them up in the environment.

@saper I also do not understand what we're accomplishing here. I assume you're referring to the following:

Any environment variables that start with npm_config_ will be interpreted as a configuration parameter. For example, putting npm_config_foo=bar in your environment will set the foo configuration parameter to bar. Any environment configurations that are not given a value will be given the value of true. Config values are case-insensitive, so NPM_CONFIG_FOO=bar will work the same.
Source - https://docs.npmjs.com/misc/config#environment-variables

This however isn't adding .npmrc support which I think is worth while.
We already support .npmrc for proxy settings so extending to the binary resolution make sense.

One just needs probably to stick || process.env['npm_config_' + subject] somewhere to make it work as you propose

I'm not sure I follow this reasoning. We already have support for the --sass-binary-site and sass-binary-path flags. The npmconf module should handle the npm config resolution process i.e. npm_conf_foo vs foo on .npmrc

I applied the .npmrc configuration possibility also to the other environment variables as proposed by @xzyfer. The're now also covered by documentation and runtime tests.

Amazing work! :heart_eyes:

Thank you very much, I'm really humbled :heart_eyes: I'm glad if I can help to bring this awesome project a bit forward.

If you're comfortable with git rebase I'd ask you to please squash these commits together

Use sass binary url from .npmrc if available
Adapted all variables to support aligned .npmrc parameters

and

Added runtime tests for .npmrc parameters
Refactored runtime unit test to follow new configuration schema

I the end there would be 3 commits

A commit adding .npmrc support
A commit updating the tests
A commit updating the docs

On Wed, 16 Sep 2015, Michael Mifsud wrote:

Use sass binary url from .npmrc if available
Adapted all variables to support aligned .npmrc parameters

and

Added runtime tests for .npmrc parameters
Refactored runtime unit test to follow new configuration schema

I the end there would be 3 commits

A commit adding .npmrc support
A commit updating the tests

I don't mind having those two together, so that we are 100% green
between commits.

No problem, I will quickly rebase that stuff as you two suggest it.

Presumably the existing test should still pass with the new functionality.
To be honest I'm fine squashing this all into 1 commit. It's all tightly related.

There are now only 3 commits. Should a rebase them all into 1?
Would make sense since Travis striked again :smile:

On Wed, 16 Sep 2015, Fabio Huser wrote:

There are now only 3 commits. Should a rebase them all into 1?
Would make sense since Travis striked again :smile:

I am just trying to quickly fix some bug in Travis tests
so I'd love more testing :)

On Wed, 16 Sep 2015, Fabio Huser wrote:
There are now only 3 commits. Should a rebase them all into 1?
Would make sense since Travis striked again :smile:
I am just trying to quickly fix some bug in Travis tests
so I'd love more testing :)

Good to now :smile: Are these 3 commits now ok for you or should I squash them all together?

On Wed, 16 Sep 2015, Fabio Huser wrote:

On Wed, 16 Sep 2015, Fabio Huser wrote:
There are now only 3 commits. Should a rebase them all into 1?
Would make sense since Travis striked again :smile:
I am just trying to quickly fix some bug in Travis tests
so I'd love more testing :)

Good to now :smile: Are these 3 commits now ok for you or should I squash them all together?

As they say those days, LGTM!

Awesome! Just tell me if I can help with something.

@fh1ch this is all good! Our plan is to ship in 3.4.0 hopefully next week.
The reason for 3.4.0 is that this is feature and by semver it should be a minor release.
The reason for not releasing 3.4.0 immediately is that we want to 3.4.0 to have LibSass 3.3.0-stable.
This is largely to help communicate to people which version of node-sass has which version of LibSass.
Also because LibSass follows pre 1.0.0 semver atm so 3.3 is actually a major version bump from 3.2.
We really appreciate your work and we're super keen to get it our the wild ASAP. We expect to have 3.4.0-beta out this week!

@xzyfer: Good to know, thanks :smile: It doesn't hurries for me so it's not that important in which release it gets. But it's nice to have libSass-3.3.0 in.
Thank you very much guys, it was a pleasure for me contributing to this project.


Add header_type to OTel documentation

Description
This pull request will add the ability to set the header_type for the opentelemetry plugin:
https://github.com/Kong/kong/pull/10620
To ensure the documentation remains in sync with the options available for plugins, this adds the header_type key to the config section showing its something that can be set.
Testing instructions
Netlify link: https://deploy-preview-5422--kongdocs.netlify.app/
Checklist

[N/A] Review label added
[N/A] PR pointed to correct branch -- I don't know when my PR will be merged and when/where it will be released, so pointing to main currently

I believe this should be rebased off release/gateway-3.3 now!

Something happened on the rebase, so closing this out and just started a new PR that was pointed directly at the proper branch: https://github.com/Kong/docs.konghq.com/pull/5431


Double Slider Widget

This addresses the request for a double handed slider #2006 . I also updated the widget gallery and the demo app.

[X] I have followed the instructions in the PR template

The widget is currently only working with f32. It is also not yet as neatly integrated into the ui-style as egui::Slider, there is no Value display yet and no text, suffix options.
Features:

dragging the two sliders.
pushing the next slider when they touch (separation_distance is configurable)

This looks great, but unfortunately I think this is a bit too niche to be included in default egui. I suggest making a 3rd party crate out of it instead, and then add it to https://github.com/emilk/egui/wiki/3rd-party-egui-crates so others can find it!

understood!
I published it as a third party crate.

@lucasmerlin can you also mention this in the wiki?

@hacknus the wiki is open to edit for anyone, feel free to add it yourself!


Gave website a simple look

Created the basic look for YourLife using BootStrap 5. Created a navigation bar, and footer. I also get rid of the form in the initial post and updated it with one that has all the necessary variables to be able to be plugged into some javascript to do the calculations for the Mifflin-St Jeor formula,.
I left the rest of the site empty as it basically just needs description as to what the formula does, and an explanation of it.
One thing to keep on mind when inserting descriptions about the formula is that I separated the form and the top part into different sections to be able to target different elements within their own section.
I used your guidelines for testing the code, and you should be able to run this fork the same way.

https://i.imgur.com/xJd3wNO.png


how to disable default log

default log like thie
{"pid":95116,"hostname":"sangalfreds-MacBook-Pro.local","level":30,"time":1483410690154,"msg":"request completed","res":{"statusCode":404,"header":"HTTP/1.1 404 Not Found\r\nDate: Tue, 03 Jan 2017 02:31:30 GMT\r\nConnection: close\r\nTransfer-Encoding: chunked\r\n\r\n"},"responseTime":22,"req":{"id":1,"method":"GET","url":"/all","headers":{"host":"<IP_ADDRESS>:53711","accept-encoding":"gzip, deflate","user-agent":"node-superagent/1.8.5","connection":"close"},"remoteAddress":"::ffff:<IP_ADDRESS>","remotePort":53724},"v":1}

i don't want see it when i run test

set the log level in your test to silent, see pino docs https://github.com/pinojs/pino/blob/master/docs/API.md#level

That page no longer exists

http://getpino.io/#/docs/api?id=loggerlevel-string-gettersetter

Any other way to disable this message? Setting the log level to silent completely stops the logs. I just need to hide this default log while keeping other logs


Getting ClassCastException while focusing at any field

Scenario tag ::
@61077    @expectedFieldShouldGetFocusedOnClickOfErrorMessage
Issue at step ::
Then I see expected field getting focused
Error:
java.lang.ClassCastException: class java.lang.Long cannot be cast to class java.lang.Double (java.lang.Long and java.lang.Double are in module java.base of loader
'bootstrap')

@ashwiniN1007 Is this issue fixed for you?

No, I am still facing the same issue.

@testing-blaze

@Naumansh  Is it fixed?

@onlyforcoding24 It is. Closing the issue.


Remove workaround on VSTS that is no longer needed

PR Summary
Remove workaround on VSTS that is no longer needed
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[x] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

I restarted appveyor & travis-ci builds for what looked like unrelated temporary errors.


Simplex stack variable analysis

Currently, our stack analysis is very naive. To improve the decompilation results, we need more advanced analysis. A good recipe is in one of Hex-Rays blog posts.
Implement something like this in RetDec and use it in other analyses as well - e.g. param/return.
@JurajHolub may implement a variant of this for the new x87 FPU stack analysis. So coordinate the efforts and possibly implement only one general analysis that could be specialized for different scenarios.

Related to #160.


Write SDS -  2.5 - Design UI for Product Management Screen

@all-contributors please add @yuhtnguyen for code, doc, review


[es-lint-plugin-lit-a11y] Problem with blank page in docs

Expected behaviour
A full description of how the a11y plugin works are expected
Actual Behaviour
Blank page

Additional context
https://open-wc.org/docs/linting/eslint-plugin-lit-a11y/
Here in the code -> https://github.com/open-wc/open-wc/blob/dd3a1b98b4f18259346eb293fe62ae74544ebe49/docs/docs/linting/eslint-plugin-lit-a11y/index.md
Docs web

This content can be found at: https://open-wc.org/docs/linting/eslint-plugin-lit-a11y/overview/

The page in question should contain a descriptive overview of what the plugin does, with links to the rules (maybe in a table)
I suggest we move the content of overview.md to that file, and add a redirect rule in netlify (and the sw?) to that page from /overview


Physical volume buttons on phone with apple remote app don't adjust volume on MRX 540

Describe Your Problem:
<!-- A clear and concise description of what problem you are trying to solve. -->
Hi Great plugin!
When using the Apple Remote in Control Center i used to be able to use the physical volume buttons on my phone to change the MRX540 volume.  That no longer works.  I xan hit the up and down button on the screen for the remote app. That works.  But the physical buttons no longer changes the volume on the receiver.
My suspicion is iOS17 or iOS17.01.  Just wanted to report this.
Everything else seems to work just fine.
Thanks again for this great plugin!

Logs:

Plugin Config:
        {
            "Host": "<IP_ADDRESS>",
            "Port": 14999,
            "PanelBrightness": true,
            "Zone1": {
                "Active": true,
                "Name": "MRX Zone 1",
                "Power": true,
                "Mute": true,
                "MultipleInputs": true,
                "ALM": true,
                "ARC": true,
                "Volume": true,
                "DolbyPostProcessing": true
            },
            "Zone2": {
                "Active": false,
                "Power": false,
                "Mute": false,
                "MultipleInputs": false,
                "Volume": false,
                "DolbyPostProcessing": false
            },
            "_bridge": {
                "username": "50:1E:2D:43:D6:44",
                "port": 51836
            },
            "platform": "AnthemReceiver"
        }

Screenshots:
Environment:

Plugin Version: 0.8.0
Homebridge Version: 1.6.1
Node.js Version: v20.3.0
NPM Version:
Operating System: Raspbian

Hi,
thank you for reporting this issue.
I did multiple tests on my production server and I was not able to reproduce this issue for the moment (iOS 17, Homebridge 1.6.1)
I was able to remove and pair the external television accessory without problems.
Physical volume buttons in control center remote are reporting proper events in Homebridge and to MRX740
Also tried adding the external television accessory on my devel server.
I can get the accessory to show up in Home App, but I don't get any remote in control center yet ...
(May be related to my internal MDNS config and not necessarily related to iOS 17)
Have you tried running Homebridge in Debug mode to check if plugin was receiving any commands from Homekit remote ?
Will try to further investigate on my side.

Interesting that it's not reproducible
I'll see if i can enable debug and pull logs.  Need to remember how to do all that but i'll figure it out.
It's strange that the up and down software buttons on the software remote work to change the receiver volume.
I would have guessed that if there was an issue with volume controls that this would also not work.  But go figure.
The play pause also mutes correctly and unmutes.
But when i click on the actual mute button in the remote that does not work.  But i never actually used that before i started seeing my issues. So don't know if the official mute button ever worked.

Interesting that it's not reproducible
I'll see if i can enable debug and pull logs.  Need to remember how to do all that but i'll figure it out.
It's strange that the up and down software buttons on the software remote work to change the receiver volume.
I would have guessed that if there was an issue with volume controls that this would also not work.  But go figure.
The play pause also mutes correctly and unmutes.
But when i click on the actual mute button in the remote that does not work.  But i never actually used that before i started seeing my issues. So don't know if the official mute button ever worked.

Home app Television accessory is created in Homebridge by configuring the 2 following services:
1- Televison service that manages the power button, input selector, control center remote buttons
2- TelevisionSpeaker service that manages the physical up and down buttons
Problem isolated to the TelevisionSpeaker service could explain your situation.
You can run Homebridge un debug mode with the -D flag in your console / terminal
If running Homebridge UI, do you see the following 2 accessories in your accessory page ?

Thanks for the explanation.
I do see both those icons in my accessories list within homebridge-ui.
They both work as expected. I can turn on and off the receiver and I can also adjust volume with the slider and mute and unmute.

Thanks for the explanation.
I do see both those icons in my accessories list within homebridge-ui.
They both work as expected. I can turn on and off the receiver and I can also adjust volume with the slider and mute and unmute.

I was thinking about your situation:
1- try to run the plugin in debug mode with -D flag to check if the plugin is registering any events from the up and down physical keys
2- For testing purposes, maybe try adding the power input external television accessory for zone 2 and check if you can get physical keys to work for zone 2.

thanks for thinking further about my case.
Latest update:
I got things to work this morning. I'm still not sure exactly what happened.
Right now i think somewhere along the way my homekit config may have gotten corrupted.
There were two updates in succession to iOS 17 then 17.01.
Something must of just gotten messed up somehow during those updates.
I just upgraded my phone and migrated to to the new phone and updated to 17.02.
I have the "controller" app that allows me to make backups of my homekit setup and noticed that it was not up to date.
The inputs + AML + Dolby modes were not synced correctly. I had to re-associate them all.
After that things seemed to work again!
I'll close the ticket for now. I'm still not sure how the messed up config happened.
I'll chalk it up to bad luck for now.
Next time it happens i'll try the debug option and provide some more info.
thanks again for the work on a great plug-in for this receiver. Amazing work.

Actually before closing out this ticket.
One suggestion based on a hunch for what may have caused my issues.
Would it be possible to make the Dolby modes, ALM modes and inputs have unique serial numbers? Maybe there are other accessories  that also don’t have unique serial numbers but I notice those three share the same one.
They all have the same serial numbers today and I think this causes issues with some HomeKit tools that can create HomeKit backups for example.
I’m wondering if maybe this may have caused the issue for me since I do use some other HomeKit tools like Controller, home+.

I will look into that.
I made the change for another plugin I wrote exactly for Homekit controller app backup concern.
ALM, Dolby and Input really are 1 accessory presenting multiple services. Serial number is bounded to the accessory.
I will check if I can get a unique serial number attached to the service rather than to the accessory.
I wonder why Homekit backup apps needs  unique serial numbers. Accessories and services are mainly identified with their uuid.

This is the message I get in the controller app.
Probably not very helpful to undertand exactly why though.

My mute, arc and power accessories in the home app show up as:
“ALM1B00432O139 ARC”
“ALM1B00432O139 Mute”
“ALM1B00432O139 Power”

My mute, arc and power accessories in the home app show up as:
“ALM1B00432O139 ARC”
“ALM1B00432O139 Mute”
“ALM1B00432O139 Power”

ARC, Mute and Power are all a single accessory containing a single service.
ALM, Input and Dolby are a single accessory containing multiple switch services sharing the same serial number.
Will try creating unique serial

My mute, arc, power, volume and brightness accessories in the home app show up as: “ALM1B00432O139 ARC” “ALM1B00432O139 Mute” “ALM1B00432O139 Power” “ALM1B00432O139 Volume” “ALM1B00432O139 Brightness”

ALM , Dolby and Input accessory were indeed sharing the same serial number.
Can you try installing beta version 0.8.1 tu see if it properly fixes the issue ?

Sure. Will give it a go and report back.

Looks good!
I see Unique serial numbers.
My remote volume (using physical volume buttons) still working as well.
I'm still not sure if the serial numbers not be unique was the cause to my issue earlier but probably still good to have this slight fix in.
Thanks for the support!


Dont_change_device for parameters in initialization

When I was running model training by Zero offload, to save the GPU memory I make the model weights initialized on CPU memory too by setting up deepspeed.zero.Init(remote_device="cpu", dtype=torch.half, enabled=False). Although the model weight is really initialized on CPU memory, but after deepspeed.initialzed(), the model still move to GPU memory. So I am wondering

in Zero offload (stage 3, offload to cpu/nvme) is it possible the weight of the model stay mainly on CPU memory/Nvme but only is loaded layer by layer to GPU memory?
I found in engine.py (actually it is called by deepspeed.initialize())  there is an argument dont_change_device (link)[https://github.com/microsoft/DeepSpeed/blob/4ae3a3da0dfd19d7ab7a76e7c742ac12f44fc1c0/deepspeed/runtime/engine.py#L1138-L1139] which controls whether or not the model weights is moved to GPU memory. But I also found no place to call dont_change_device. So my question is how to use dont_change_device and is it used to retain the model weight on CPU memory?

I'd like to set this option "dont_change_device" because deepspeed is calling the module.to()
which raises an error in transformers with my 4-bits model:
ValueError: `.to` is not supported for `4-bit` or `8-bit` models. Please use the
model as it is, since the model has already been set to the correct devices and
casted to the correct `dtype`.

s

I'd like to set this option "dont_change_device" because deepspeed is calling the module.to() which raises an error in transformers with my 4-bits model:
ValueError: `.to` is not supported for `4-bit` or `8-bit` models. Please use the
model as it is, since the model has already been set to the correct devices and
casted to the correct `dtype`.

Same issue for BitsAndBytes Llama3.1 70B Instruct 4bit model


Unhandled Rejection (Error)

Hi, While sh start.sh localhost were unable to detect as baseurl.
Unhandled Rejection (Error): could not detect network (event="noNetwork", code=NETWORK_ERROR, version=providers/5.4.1)
Logger.makeError
/workspace/pancakeswap-frontend-hardhat-testnet/src.ts/index.ts:213
Logger.throwError
/workspace/pancakeswap-frontend-hardhat-testnet/src.ts/index.ts:225
StaticJsonRpcProvider.<anonymous>
/workspace/pancakeswap-frontend-hardhat-testnet/src.ts/json-rpc-provider.ts:396
  393 | this.emit("debug", {
  394 |     action: "response",
  395 |     error: error,
> 396 |     request: request,
      | ^  397 |     provider: this
  398 | });
  399 | throw error;

Have you turned on the Hardhat network?

Yes, Hardhat network is running using sh serve.sh & Still I'm facing this issue.

Yes, Hardhat network is running using sh serve.sh & Still I'm facing this issue.

Do you run sh start.sh under node version 12?

Please make sure you run sh start.sh under the node version 12 after successfully deploying all the contract and let me know the result, thanks.

Please make sure you run sh start.sh under the node version 12 after successfully deploying all the contract(sh deploy.sh) and let me know the result, thanks.

same issue  here I tried to deploy in on testnet before launching it on mainnet


Allow arbitrary options to be configured.

What
Allow arbitrary options to be configured on the docker-compose commands.
Why
The options/flags available on docker-compose are changing rapidly and
allows the user to specify any options without the plugin being kept
up-to-date. Resolves #10.
Inspired by
https://stackoverflow.com/questions/30665816/docker-compose-vagrant-and-insecure-repository?rq=1#comment49395344_30665816

This is in version 0.0.8.


Get maxbits for compressed array

How do I retrieve the maxbits when I only have a compressed array? Is it possible, or do I have to store the value from maxbits_length?

The library is intentionally low-level. You are responsible for storing the bit width, but we provide examples :
https://github.com/lemire/simdcomp/blob/master/example.c#L41-L62

@lemire understood, thanks.


Fix gulp tasks for generator

I just update my repo of generator-node to add watch task https://github.com/yeoman/generator-node/issues/177
And when I try to run $ gulp some errors appeared.
Voilà my fixes for each error commit by commit.
Comments appreciated. Wait your go to squash commit.

Thanks, LGTM.

Thanks. Those commits are well separated, we'll merge as is :)


Cannot login to UAA

Using the following sample code:
#!/usr/bin/env ruby
require 'uaa'
token_issuer = CF::UAA::TokenIssuer.new("https://uaa.cloudfoundry.com", "vmc")
puts token_issuer.prompts.inspect
token = token_issuer.implicit_grant_with_creds(username: "<your_username>", password: "<your_password>")
token_info = TokenCoder.decode(token.info["access_token"], nil, nil, false) #token signature not verified
puts token_info["user_name"]

I replace the URL with the URL of my UAA in my working CF deployment. (Just http though,
token_issuer = CF::UAA::TokenIssuer.new("http://uaa.<myCFdomain>, "vmc")
token = token_issuer.implicit_grant_with_creds(username: "adminusername", password: "userpassword")
And I get this error:
/root/ruby/lib/ruby/gems/1.9.1/gems/cf-uaa-lib-2.1.0/lib/uaa/token_issuer.rb:142:in implicit_grant_with_creds': status 401 (CF::UAA::BadResponse) from buildsource.rb:7:in'

Am I using it wrong?
Also, I can't find actual user documentation for the lib itself. Where can I find it?

The error messages are not very helpful. The problem in your case, I believe is the client id that you have provided vmc. You have to use a client that is setup in your UAA. If you have not setup a client yet, you can do so using UAAC cli.
Also remember that the client you set should have implicit as one of its grant types.


App crashes when switching to Dark Mode

When I tried switching to dynamic theming light theme worked fine but when I changed to night theme the app crashed. The changes have not been commited just to keep the main branch clean. Will push the updated version to development tommorow.

Will try to pick this up asap

Will try to pick this up asap

I have already traced the isssue. I forgot to add respective values in themes.xml for dark mode

Fixed in ee5648d


Can't load java.lang.Thread

I'm trying to get doppio working in a browser. At the moment it throws an exception trying to load the java.lang.Thread class
Cannot read property 'throwNewException' of null    -   on line 340 of ClassLoader.ts
The webroot I'm using is at https://github.com/ianopolous/DoppioDemo

This is a reminder to me to have better error messages during JVM bootup...
The JVM loads the thread class first to mock a Thread object to bootstrap the JVM. It is failing to load the file, which means it cannot find java.lang.Thread on the classpath.
And it cannot find java.lang.Thread because the filesystem has an issue; /sys/vendor/java_home/lib/rt.jar exists in the index, but the filesystem cannot fetch it:
BrowserFS.BFSRequire('fs').readFileSync('/sys/vendor/java_home/lib/rt.jar')
xhr.ts:164 GET http://localhost:8080/doppio/vendor/java_home/lib/rt.jar 404 (Not Found)i @ xhr.ts:164b._requestFileSync @ XmlHttpRequest.ts:101b.openSync @ XmlHttpRequest.ts:267b.readFileSync @ XmlHttpRequest.ts:334b @ MountableFileSystem.ts:300a.readFileSync @ FS.ts:474function.e.(anonymous function).f.(anonymous function) @ node_fs.ts:19(anonymous function) @ VM872:1InjectedScript._evaluateOn @ (program):145InjectedScript._evaluateAndWrap @ (program):137InjectedScript.evaluate @ (program):118
MountableFileSystem.ts:303 Uncaught f {syscall: "", errno: 404, code: undefined, path: null, stack: "Error↵    at new f (http://localhost:8080/doppio/b…/browserfs.min.js:7:8011)↵    at <anonymous>:1:28"…}

It's typing to load http://localhost:8080/doppio/vendor/java_home/lib/rt.jar instead of http://localhost:8080/doppio/java_home/lib/rt.jar.
But the JVM isn't even trying to load that file, because the boot classpath is set to /sys/java_home/classes.
To fix these issues:

Regenerate listings.json by running the XmlHttpRequest file system's indexer in the doppio folder.
Use Doppio.VM.JVM.getDefaultOptions(doppioHomePath) (e.g. Doppio.VM.JVM.getDefaultOptions('/sys')) to construct the options to the JVM, extended with the classpath that you want for your programs.

That should fix the issue.

If I run the XHRIndexer in the doppio directory it outputs something with all values null. e.g. {"browserfs.min.js":null,"browserfs.min.js.map":null...

While weird, that's actually intentional. The XHRFS uses the JSON object directly as its index, with stats stored in each property, so storing it this way on disk prevents XHRFS from having to transform it at runtime. This was a huge performance gain when DoppioJVM did not support JAR files, and had an index with every individual class file in the Java Class Library!

Ah, I see. It is still failing to load Thread though with both those changes. The latest is at:
https://github.com/ianopolous/DoppioDemo
Have I missed something else?

Yes; it looks like the default options expect java_home to be in a vendor directory. Move java_home into vendor, regenerate listings, and it should work.

That fixed it! Thank you!

I've updated the getting started guide, and added an example application that can be built in a single command.


Updating the header

voting has been misspelled

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@ranganathg - thanks.


Update attu install helm.md#install attu while installing milvus

Thanks for your contribution, we'll verify this later.


fix 3 separate bugs in bitmapCountRange

I think these are all real, but let me know if I've just completely misunderstood how this is supposed to work. Hoping to get at least 2 reviews since we're pretty deep into the bowels here.
in order of the diff:

When the start and end of the range fall in the same word, special handling
is needed to "mask" off the beginning and end of the word simultaneously to
avoid counting bits at the beginning or end of the word that aren't in the
range.

i++ is needed at the end of the first partial word to avoid counting this
word in the next block.

the shift amount for right shifts is 64 - (end % 64) rather than just end
% 64. If end is (e.g.) 68, then 68 - 64 is 4 and we are only interested in the
first 4 bits of the word, so we must right shift by 60 bits, not 4 bits.

Coverage increased (+0.1%) to 66.85% when pulling fb4651cdb8092e1dfad3b0384b57d306ce351282 on jaffee:bitmapCountRange-bugs into 4a14e38ebeffe1a1a3f1a38069f21e7394e7032e on pilosa:master.

I just pushed another commit which corrects this based on my understanding that the least significant bit in one of a bitmap's 64 bit integers is the "zeroth" bit in that integer. So setting bit 0 sets the first integer in the bitmap to 1 rather than 2**63 as I had been thinking.

Coverage increased (+0.2%) to 66.915% when pulling c0ddbe0e3fba41573cc46ee510153ac3d6f5799a on jaffee:bitmapCountRange-bugs into 4a14e38ebeffe1a1a3f1a38069f21e7394e7032e on pilosa:master.

Coverage increased (+0.2%) to 66.884% when pulling a5918d01d9d41b6a2512d1eeba8aa7b60d8b6012 on jaffee:bitmapCountRange-bugs into 4a14e38ebeffe1a1a3f1a38069f21e7394e7032e on pilosa:master.

good call on that fix @travisturner - do you think we should just remove the branch entirely? simplify the code and avoid the branching instruction in what is probably the most common case - doing a bit of extra work when off == 64

@jaffee i suppose we could since that case isn't going to happen very often, and the performance hit we take is just a 64-bit shift. i'm not sure what the performance hit is for checking equality.

@jaffee before this gets merged we need to add the license header to the new .go file.

Coverage increased (+0.2%) to 66.905% when pulling 6b3b459659aedeae9fb6ba3dc9e05cf2ff0db454 on jaffee:bitmapCountRange-bugs into 4a14e38ebeffe1a1a3f1a38069f21e7394e7032e on pilosa:master.

Coverage increased (+0.2%) to 66.894% when pulling e90e1455db96773379ba6b74f07e4bee6dc4fe9f on jaffee:bitmapCountRange-bugs into 4a14e38ebeffe1a1a3f1a38069f21e7394e7032e on pilosa:master.


Remove Serialization Hooks in 1.20.1

to quote the dev on modfest discord

the mod is dead, FAPI has the features now
well the important one
custom ingredients

yeah I just tried... this is too confusing for me...

wait no it isn;t done

@walksanatora how important is this, and how much effort would it be? can you elaborate a bit on why we need to make this change?

well serhooks is no-longer being maintained (meaning we wold have to maintain)
and the features of serhooks has been moved into base fabric API. meaning that if we choose to maintain it we would have to work around/with the fabric API implementation. at which point we might as well just use the fabric API version anyways

so not important untill serhooks breaks


[zh]Update content/zh/docs/tasks/inject-data-application/define-command-argument-container.md

/lgtm
/approve

@kinzhi  Please try sign on https://github.com/kubernetes/website/issues/33477 for some tasks, rather than page by page syncing


Init changelog for 23.04 [skip ci]

command used to generate,
GITHUB_TOKEN=<PAT> scripts/generate-changelog --releases=23.02,23.04

initiate the changelog for review in advance.
We will put another PR to do final update for 23.04 changelog before RC build.

Below PRs have no correct roadmap setup,
NOTE: Merged Pull Requests w/o Project:
branch-23.04 #7222 Automatic conversion to shimplified directory structure  [databricks] https://github.com/NVIDIA/spark-rapids/pull/7222
branch-23.04 #7572 Enables spillable/unspillable state for RapidsBuffer and allow buffer sharing https://github.com/NVIDIA/spark-rapids/pull/7572
branch-23.04 #7621 Document GNU sed for macOS auto-copyrighter users [skip ci] https://github.com/NVIDIA/spark-rapids/pull/7621
branch-23.04 #7728 Fix estimatedNumBatches in case of OOM for Full Outer Join https://github.com/NVIDIA/spark-rapids/pull/7728
branch-23.04 #7734 Temporarily skip the test_parquet_read_ignore_missing on Databricks https://github.com/NVIDIA/spark-rapids/pull/7734
branch-23.04 #7787 Document a workaround to RuntimeException 'boom' [skip ci] https://github.com/NVIDIA/spark-rapids/pull/7787
branch-23.04 #7789 Update script for integration tests on Databricks [databricks] https://github.com/NVIDIA/spark-rapids/pull/7789
branch-23.04 #7839 Add reduced pom to dist jar in the packaging phase [databricks] https://github.com/NVIDIA/spark-rapids/pull/7839
branch-23.04 #7854 Optimize `regexp_extract*` by transpiling capture groups to non-capturing groups so that only the required capturing group is manifested https://github.com/NVIDIA/spark-rapids/pull/7854
branch-23.04 #8007 Fix leak where RapidsShuffleIterator for a completed task was kept alive https://github.com/NVIDIA/spark-rapids/pull/8007
branch-23.04 #8040 Fix device vector leak in RmmRetryIterator.splitSpillableInHalfByRows https://github.com/NVIDIA/spark-rapids/pull/8040
branch-23.04 #8070 Fixes closed RapidsShuffleHandleImpl leak in ShuffleBufferCatalog https://github.com/NVIDIA/spark-rapids/pull/8070
branch-23.04 #8071 Fix error in deploy script [skip ci] https://github.com/NVIDIA/spark-rapids/pull/8071
branch-23.04 #8076 Add in docs about RetryOOM [skip ci] https://github.com/NVIDIA/spark-rapids/pull/8076
branch-23.04 #8087 Add an FAQ entry on encryption support [skip ci] https://github.com/NVIDIA/spark-rapids/pull/8087

@sameerz @GaryShen2008 please help review the change, and adjust update to issues and PRs, I will re-generate later thanks!

Added roadmap to PRs and updated labels on issues.
cc: @mattahrens

I will do a final update before RC build tomorrow, thx

build


work-in-progress - several changes

One pull request for several changes, still work in progress

Tested on Centos7/8 and RHEL 7/8 - works fine for me... Ready to review & merge :-)
If someone need RHEL 7 oder RHEL 8 hetzner images, ping me...


Change callback function for Basic Authentication to verifyPassword

Add new callback support for verifyPassword
Create new constructor to take verifyPassword as parameter
Deprecate old constructor that takes userProfileLoader
Replace uses of 'as NSString' on macOS because of [SE-0083] https://github.com/apple/swift-evolution/blob/master/proposals/0083-remove-bridging-from-dynamic-casts.md

Please add tests for your new API.

@shmuelk All comments have been addressed.


if site-wide commenting/discussion is not enabled, but I enable it on a page, it shows up but does not work

When editing https://6.demo.plone.org I can enable discussion, and when I save I see a commenting box at the bottom of the page, and you can type in it and it gives the impression of being usable but it does not save the comment.

@sneridagh What should we do here. should we check it first and then show this component or we should remove this from page schema itself. Or We should allow the commenting even the site-wide commenting is not enable.
cc @tisto @davisagli @tkimnguyen

@tkimnguyen I'm confused -- the title of this issue says discussion was not enabled, but the description says it was. Also I don't remember the steps to enable discussion (and if I did, I would not be sure you did the same steps). Could you please update the issue with the steps to reproduce?

@davisagli I should have said in my original comment "When editing https://6.demo.plone.org/ I can enable discussion on a page"

I have so edited my original comment above

Just tested it on https://demo.plone.org/ ... still an issue. I enabled commenting on the front page (Plone Site content item), saved, then see a Comment box at the bottom but typing in it then pressing the -> button just makes my comment text disappear.

@tkimnguyen ok. I can reproduce it on the Plone Site but not on other pages. (All of them show the "enable discussion" field even when commenting is turned off sitewide, which seems like a separate issue)

I went looking but I guess Volto control panels don't show the sitewide commenting option that is in Classic UI https://classic.demo.plone.org/@@discussion-controlpanel


Redirect duplicate readme files

Redirecting duplicate files:
Redirect react tutorial -> https://github.com/aws-amplify/docs/blob/master/js/react.md
Redirect GraphQL tutorials -> https://github.com/aws-amplify/docs/blob/e02bd04e09cac735ddc2ee66a3141e2ce9663302/js/graphql.md
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@mlabieniec Fixed the paths.

@mlabieniec Made the requested changes.


[Merge]AddSupportInChangeFeedFetcher

Description:
Part of the effort of adding Merge support in Java SDK.
Added merge support in changeFeedFetcher. Most of the change are renaming.

API change check
API changes are not detected in this pull request.


Feature/webumenia 1440

Description
carousel / hero image style upgrade

unified handling of the background image
used img + src + srcset for responsive behaviour
resurrected slide detail
removed flickity - replaced by slick(which was already used at the artwork->detail page)

Fixes WEBUMENIA-1440
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] I have updated the CHANGELOG
[x] I have requested at least 1 reviewer for this PR
[ ] I have made corresponding changes to the documentation

Thanks for all the fixes. Most of my suggestions are very minor except this one: can you please move App\HasHeaderImageTrait to App\Traits\HasHeaderImage? I know it seems silly, but it is the standard for Laravel apps and I suspect it's causing some lookup/import issues right now.

Laravel's convention is using Concerns for traits and Contracts for interfaces -- we already got these namespaces in App.

Laravel's convention is using Concerns for traits and Contracts for interfaces

Hah! I stand corrected. I've seen `app/Traits/ this at Spatie and we used it for Register architektury, but @rastislav-chynoransky is right, the Laravel team is using a different convention.
I'd be up for moving this to Concerns.

Thanks for all the fixes. Most of my suggestions are very minor except this one: can you please move App\HasHeaderImageTrait to App\Traits\HasHeaderImage? I know it seems silly, but it is the standard for Laravel apps and I suspect it's causing some lookup/import issues right now.

@eronisko @igor-kamil please review and close asap.

Please resolve conflicts and I'll take one last look. In general, this is good imho.

@martin-havala could we please make a new branch (e.g. redesign) and merge this into it?


Memory: fix en pipeline for read ports

The enable signal on a read port is never used by treadle and thus this bug was never discovered. However, I am using it for my symbolic execution extension.
This fixes the fact that instead of creating a enable and a address pipeline the old code would create two address pipelines.
During the course of fixing this I merge the functions for read and write ports into one as their only difference was the latency which can be a function parameter.

In case anyone is wondering: the changes from readerName/writerName to name allowed me to keep the 120 character horizontal limit. name should not be ambiguous and in the case of a read/write port, it is actually more correct.


Remove DialogFlow entirely

We don't use this at all and don't seem to intend to, so it's not worth having in our codebase

Without Dialogflow:

with:

This is because the google-cloud-dialogflow library and its dependencies are big and have compiled parts.

Missed a mention in experience.py and the tables could be removed from the example.sql, though they should get dropped when the DB gets migrated at startup I think (to test, maybe)


[BUG] - ERROR: FFmpeg exited with code 1

I've an Raspberry Pi 3 B+that hosts Homebridge and installed plugin on it. Whenver I try to use livestream from Home app, it doesn't work and I get the message [Dafang] ERROR: FFmpeg exited with code 1 in the logs.
When I try to check the stream from another machine, it works just fine from VLC on Mac. You can see part of my configs below:
"cameraName": "Xiaomi Dafang",
                    "cameraRTSPStreamUrl": "rtsp://USERNAME:PASSWORD@<IP_ADDRESS>:8554/unicast",
                    "videoConfig": {
                        "source": "-rtsp_transport tcp -i rtsp://USERNAME:PASSWORD@<IP_ADDRESS>:8554/unicast",
                        "stillImageSource": "-rtsp_transport http -i rtsp://USERNAME:PASSWORD@<IP_ADDRESS>:8554/unicast -vframes 1 -r 1",
                        "maxStreams": 5,
                        "maxWidth": 1280,
                        "maxHeight": 720,
                        "maxFPS": 25,
                        "debug": true,
                        "audio": true
                    },

In addition, I have two more cameras which has Motioneyeos and Motioneye server running on same Raspberry Pi. I've them in my Homebridge as well with homebridge-camera-ffmpeg plugin and live stream for them is also working fine.
What might be wrong with my configurations? Do I need to enable/disable some services from Dafang web interface?

Same problem here (on a raspberry 4), I've the same problem. It worked once and after that I get only ' mpeg code 1' when I try to stream in homekit.

You will have to do "reset streaming" and it'll work again.
looks like there s bug somewhere.

Same issue here, reset streaming does not resolve the issue for me.

Same issue

Same issue too...

See the conclusion of #65

See the conclusion of #65

this one dos not work properly. By the way camera-ffmpeg working fine. May be plugin contributors cloud use https://www.npmjs.com/package/ffmpeg-for-homebridge dependency for using embedded ffmpeg inside this plugin? @sahilchaddha What do you think?

The conclusion of #65 was that homebridge-dafang is not up to date, and the only workaround at this point is to use homebridge-camera-ffmpeg with homebridge-defang-mqtt-republish, which does work. In fact, if you use "vcodec": "copy", you don't even need the MaxWidth/MaxHeight/FPS settings, as ffmpeg will simply pass-through whatever it gets from the camera. This saves considerable CPU.

Thanks @jlg89 , it works like you suggested.

I am still using Homebridge dafang despite it probably being abandoned forever, and I'm on the current version of homebridge and dafang hacks. After setting vcodec to copy, I'd say 9 times out of 10 if you get ffmpeg exited with code 1, it's related to audio.
The newest dafang hacks firmware seems to really screw things up. Some thing about the Web UI will make your settings go haywire.
I've been using my cameras in homebridge fine up until this morning. Some stopped streaming (exited with code 1 error), some worked.
I decided to give camera ffmpeg another try, but I got the same error. You can quickly turn off the sound from camera ffmpeg settings page, so I tried that. Streaming started to work again, so I went to the dafang hacks web ui, changed the audio format setting from "off" to "PCM" and it brought back streaming.
I'd like to eventually possibly switch to camera ffmpeg again but I need a better solution for saving video files. OR!! just get Aqara G2H cameras!


fixup chmgen release build on win32

Well if we really want to actively support building dlang.org on Windows, we should add a CI for it. See e.g. dlang/tools#269

No, we've abandoned doc builds on Windows, it's only the chm generation that's left.


chore(main): release 0.3.0

Auto generated release
0.3.0 (2024-12-10)
Features

add php language (#33) (b00b595)

Miscellaneous Chores

deps: bump clap from 4.5.21 to 4.5.23 (#76) (2df72f5)
deps: bump the docker-minor group with 2 updates (#75) (1549224)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.3.0
:sunflower:


Allow setting all env variables at runtime

Currently, we need to set the environment variables at build time. This is because Next.js includes them in the final bundle.
It would be better if we can build a generic Docker image, and inject the environment variables at runtime.
See this discussion which has a way of doing it.
I am working on a Home Assistant addon for Calendso, and I have successfully built and run the project using this method. The addon is still in the experimental stages, however, you can see an example of the relevant code. Here a variable is set with a dummy value during build time. Here the variable values are overwritten at runtime.

Do you have enough to do a pull request so that we can see the method in action?

@TheBestMoshe just wondering if you might have time to make a specific pull request with just the runtime injection workaround?

@krumware I began working on this, however, I'm not sure why it was not working for this repo.
This is what I have tried so far. However, it is not replacing the variables.

ok thanks for the diff! much easier to see it in action here. I'll see what I can debug

I have this working on my Home Assistant Add-on for Calendso
If you want to see a working example, you can clone the repo and checkout the cal.com-pinned-to-commit branch. Then do the following steps:
Create a file in the cal.com directory data/options.json with the following content:
{
    "database_url": "postgresql://postgres:postgres@postgres:5432/cal?schema=public",
    "base_url": "http://localhost:3000",
    "jwt_secret": "secret",
    "calendso_encryption_key": "ejfoewurf939r3"
}

and run:
docker-compose build
docker-compose up

Prisma Studio will be accessible at localhost:5555 so you can create a user. Calendso will be available at localhost:3000
To test the runtime variables were correctly set, go to the /event-types page and preview an event. If the event preview opens to the correct page, then the base_url in the config.json file is being set at runtime.
Note: The version of Calendso is pinned to an older commit, as I was unable to get it to build with newer commits as it had other errors.

ok thanks for the diff! much easier to see it in action here. I'll see what I can debug

The issue I was having was that it was not overwriting the dummy values. I think there is something wrong my find and replace code in start.sh

Thanks @TheBestMoshe, will get to this as soon as I can

this was resolved


List management - Contact cards

the names for relationship holders on both nation and proponent pages should have a contact card hoverstate

As a (type of user)
I want (goal)
so that (reason/ why/ value)
Acceptance Criteria
Scenario 1:
GIVEN ... (you or your condition)
WHEN ... (what you do)
THEN ... (what you see)
Scenario 2:
xxxxxx
Validation Rules?
(If yes, list here)
Screenshot
(Link above will always be the most up-to-date version.)

@djnunez-aot, this one is not working properly.
we have a specific implementation to show it - it should be reflected everywhere
please see video for the reference
Private Zenhub Video


Reject responses with explicit set-cookie header

This PR addresses the issue #1619 .
Proposed changes

reject response with explicit <<"set-cookie">> in headers

Could you take a look when you have time, @essen ? Thanks in advance.

Yes tests are fine like this, though since there's a crash you should also call ct_helper:ignore(M, F, A), before the crash, with MFA where the crash occurs. It will silence the expected crash.

@essen would you have any clue how we can test this on stream_trailers?
I tried adding this to resp_h.erl - inside of do(<<"stream_trailers">>, Req0, Opts).
<<"set_cookie">> ->
			ct_helper:ignore(cowboy_req, stream_trailers, 2),
			Req = cowboy_req:stream_reply(200, #{
				<<"trailer">> => <<"grpc-status">>
			}, Req0),
			%% The size should be larger than StreamSize and ConnSize
			cowboy_req:stream_body(<<0:80000000>>, nofin, Req),
			cowboy_req:stream_trailers(#{
				<<"set-cookie">> => <<"name=cormano">>
			}, Req),
			{ok, Req, Opts};

Then I tried something like this
do_trailers("resp/stream_trailers/set_cookie", Config)

It broke the test suite - I didn't even check the return
It breaks somewhere else it is also a badmatch.

Sometimes it can be difficult to test crashes. Some of the Cowboy tests trigger the crash but the test case has no way of confirming it happened. That's OK for the time being.
I will pick this up after I'm done with my current ticket. A quick look seems fine. Thank you!

Sometimes it can be difficult to test crashes. Some of the Cowboy tests trigger the crash but the test case has no way of confirming it happened. That's OK for the time being.
I will pick this up after I'm done with my current ticket. A quick look seems fine. Thank you!

Sounds good. Thanks for the help. Let me know if I can help with something.
I will look for another issue - would you have any suggestion?

Merged with a number of fixes, thank you!
Note that most of the tests were not testing the right crash as you copied test code that used bad arguments to trigger crashes and didn't update them.

Hi @essen! This pull request unfortunately breaks all Elixir projects that depend on Cowboy via Plug, since Plug manages the cookie headers by itself. Is there any chance this could be skipped by using a flag? Or alternatively, would you accept a pull request that adds set_resp_cookie(HeaderValue, Req :: cowboy_req:req()), so we can give the whole header value (which we have already accumulated and returned)? Thank you.

For now you can modify the Req object directly (basically doing what set_resp_cookie(HeaderValue, ...) would do).
Not sure this has to be in Cowboy but feel free to open a PR and let's gather feedback.

For future releases perhaps Plug can add Cowboy master to its CI? Maybe on a schedule, running every week. This would have catched this. I am working immediately on 2.12 and this will take a while (HTTP/3) so getting feedback before release would help.


Remove all license files of Apache 2.0 libs. And add a missing one.

Based on @WillemJiang 's comments in previous release votes, Apache 2.0 license files are not necessary.
I just removed them and found a missing one.
@hanahmily Please work on UI parts, and submit a new PR.

Coverage remained the same at 24.467% when pulling 417515c9ce9b2261c735f5b60624cebaa95c9515 on remove-asf-license-files-of-dependency into 1b74d1d8425e7630684543d43e606f0c8de6eff1 on master.

@WillemJiang These two license files have been added back. And add a new section in the main License file. Like this:


RISC-V: Enhancement for stack size to 16-bytes aligned at least

If enable CONFIG_PMP_STACK_GUARD, the stack size may not 16-bytes
aligned. Enhance this issue.
Signed-off-by: Shih-Wei Teng<EMAIL_ADDRESS>

@lindemer I update the description. Please help check if it is fine. Thanks!


[WIP] Support cupy.ndarray subclassing - Part 1 - Direct constructor call

(description follows later, let me run a full test to see if it doesn't break the current code)

/test full

/test mini

/test benchmark

/test benchmark

/test mini

I'm making renames from ndarray to ndarray_base and _ndarray to ndarray, but perhaps it won't be in time for beta3 release as it has a lot of lines changed. In such a case, please consider including commits so far to beta3, which passed the CI.


Update IETF build command

/cc @ronaldtse

Thanks @ryzokuken -- really appreciate it! (I made minor changes to the flags)


Huge pain migrating to {N} 3.4 with WebPack

Despite the slowness of the looong launch time and the slow navigation experiencing on the version 3.3, I decided to update to the latest version of Nativescript, embedding the famous Webpack, which apparently offers greats performance improvements.
To do so, I followed each one of the instructions here. This led me to have a new version of the application, getting webpack (which I didn't succeeded to get working on the previous version) and {N} 3.4.
As I am typing on my keyboard the so-used command to run the app on my device, I am full of hopes that the Nativescript Developer team found a way to get rid of all the problems that was happening before, when trying to integrate WebPack to an existing project.
Oh no I am in front of a big stack of errors about relative paths; thus I refactor all of my components' paths to stop seeing all these errors.
Now everything is clean, the app builds without any problem, it is now installed on my device. My application is now opening, that's wonderful it works like charm now, and oh wait, it just crashed ...
Perhaps just a bug, I try to restart the app, and it crash again ...
All my hopes fly away, I facing the same problems that with the previous nativescript version.
I am not going to let down so easily, so I try to get it running with all the optimized setting options I have found :
tns run android --bundle --env.aot --env.snapshot --env.uglify --env.report
Doing so the app is not even building, and shows other errors.
I have currently been struggling against an incalculable number of errors coming from everywhere, but I feel like stuck in quicksand. Every time I solve one, another is popping.
For example, I had errors about SDK licenses, about aot files excluded from tsconfig, about plugin dependencies, but nothing seems to be the final solution.
So I am here to request for your help because I am getting desperate getting my app running with all the benefits from webpack ...
Here is the latest error I am facing :
Running full build
Exception in thread "main" java.io.IOException: File already exists. This may lead to undesired behavior.
Please change the name of one of the extended classes.
File:/Users/me/Documents/nativescript_apps/myapp/platforms/android/app/src/main/java/com/tns/gen/java/lang/Object_frnal_ts_helpers_l58_c38__t.java Class:
        at org.nativescript.staticbindinggenerator.Generator.writeBindings(Generator.java:68)
        at org.nativescript.staticbindinggenerator.Main.main(Main.java:15)

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/me/Documents/nativescript_apps/myapp/platforms/android/build-tools/android-static-binding-generator/build.gradle' line: 284

* What went wrong:
Execution failed for task ':asbg:generateBindings'.
> Process 'command '/Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/bin/java'' finished with non-zero exit value 1

As before, if I launch tns run android, the app builds fine, but crashes on startup, and if I run tns run android --bundle --env.aot --env.snapshot --env.uglify --env.report I get this error.
I will appreciate any kind of help !

ok

Hi @TheOnlyMatt ,
i have same problem  (JAVA io.Exception) but when i start tns build android --bundle.
Any idea?

Hello @alexma01, did you try to remove and reinstall android platform ?


add libqt5gui5 for Debian

Please check:  https://packages.debian.org/search?keywords=libqt5gui5

+1


Add awsm.css

Added my own library built with SCSS, which everyone can use for creating their own blogs, homepages, etc.
Hope that everything is correct. If I missed something, feel free to point to it :-)

Hey 👋 Thank you for the PR Igor!
I think awesome-css is the better fit for awsm.css than awesome-sass. I suggest you send a PR to add awsm.css there instead 🙌

@tandavas, ah, okay. Thanks! :-)

@igoradamenko No problem! Good luck with your PR to awesome-css 😉


Shrine Image Compression

Is there a plugin for image compressing images as they are being uploaded?

No, but it's much better to do compressing yourself in the processing step, for example:
require "zip" # from the "ruby-zip" gem

class MyUploader < Shrine
  plugin :processing
  process(:store) do |io, context|
    zip_file = Tempfile.new(["compressed", ".zip"], binmode: true)
    Zip::OutputStream.write_buffer(zip_file) do |zip|
      zip.put_next_entry(io.original_filename)
      io.open { |file| zip.write(file.read(16*1024)) until file.eof? }
    end
    zip_file
  end
end

Note that, as per contribution guidelines, questions should be asked on the Shrine google group, GitHub issues should be used only for bug reports.