Error on deploy when specify Hadoop 3.1.1 version - via Terraform

When using Terraform, providing a clusterType of Hadoop with HDI Version 4.0 and componentVersion 3.1.1 fails with the following -- the only "version" accepted is "3.1" in the Terraform deployment.
Error: Error creating HDInsight Hadoop Cluster "scicoriahdicluster" (Resource Group "scicoria-hdp-cluster"): hdinsight.ClustersClient#Create: Failure sending request: StatusCode=400 -- Original Error: Code="BadRequest" Message="HDI Version'4.0' is not supported for clusterType 'Hadoop' and componentVersion '3.1.1'.,Invalid component version for HDInsight version: 4.0 cluster type: Hadoop"

This WORKS
resource "azurerm_hdinsight_hadoop_cluster" "hdpcluster" {
  name                = "${var.prefix}hdicluster"
  resource_group_name = azurerm_resource_group.hdpcluster.name
  location            = azurerm_resource_group.hdpcluster.location
  cluster_version     = "4.0"
  tier                = "Standard"

  component_version {
    hadoop = "3.1"
  }

This should work as the version 3.1.1 is what's documented on this page, but it fails with the error above:
resource "azurerm_hdinsight_hadoop_cluster" "hdpcluster" {
  name                = "${var.prefix}hdicluster"
  resource_group_name = azurerm_resource_group.hdpcluster.name
  location            = azurerm_resource_group.hdpcluster.location
  cluster_version     = "4.0"
  tier                = "Standard"

  component_version {
    hadoop = "3.1.1"
  }

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

ID: af6ae544-80bf-209a-9de5-63153fd47ab5
Version Independent ID: c70f7c14-6c10-a3e3-8593-8ec63b7fabe2
Content: Apache Hadoop components and versions - Azure HDInsight
Content Source: articles/hdinsight/hdinsight-component-versioning.md
Service: hdinsight
GitHub Login: @hrasheed-msft
Microsoft Alias: hrasheed

@cicorias  Thanks for bringing this to our attention. Your feedback  has been shared with the content owner for further review.

@cicorias Thanks for letting us know. The published Hadoop version of 3.1.1 is correct based on the version in production and is used to help customers distinguish the various patches and updates present on their clusters. At this time, Terraform is not one of our documented and supported deployment methods. I do not believe that any of our documented deployment methods such as Azure CLI, Powershell or the SDKs require this property "component_version", merely the cluster version. I have notified the product group to ensure that any APIs which are being hit by other deployment tools reflect the published component versions.

#please-close

you're closing this prematurely. Terraform is just calling the Resource Manager API with the data - the API Endpoint only accepts 3.1 for the value.
The DOC update change is to either clarify that as this affects anyone using the Go SDK which has a parameter "component_version"
This params object, used here: https://github.com/Azure/azure-sdk-for-go/blob/master/services/preview/hdinsight/mgmt/2018-06-01-preview/hdinsight/clusters.go#L49
Contains the structure: ClusterCreateProperties which contains ClusterDefinition which has ComponentVersion map[string]*string json:"componentVersion".

@cicorias Thank you for providing more detail on the issue. I better understand your concern. The purpose of this particular document is just to document the actual versions of software components present on the clusters, not to provide instructions on specific deployment scenarios.  If the situation is as you described, I would be more than happy to document it. But because this is a detailed issue regarding the HDInsight resource manager API, I think the best procedure would be to start by interfacing with the HDInsight product group directly. There may be other related issues which need to be documented as well. You could open an ICM (https://aka.ms/icm) or post to the HDInsight discussion group<EMAIL_ADDRESS>


Add support for setting room setpoint

Is your feature request related to a problem? Please describe.
I cannot set room temperature setpoint
Describe the solution you'd like
Set room temperature setpoint using "/heatingCircuits/hc1/temperatureRoomSetpoint"
Additional context
{
"id": "/heatingCircuits/hc1/temperatureRoomSetpoint",
"maxValue": 30.0,
"minValue": 5.0,
"recordable": 0,
"state": [
{
"off": 0.0
}
],
"type": "floatValue",
"unitOfMeasure": "C",
"value": 22.0,
"writeable": 1
},

I have verified setting room temperature with HC1 is ok with component version 0.7.0 and HA 0.105.0. Thanks!


Implement recent MilitaryOverlay schema changes in jmsml.config

After the team reviews the MilitaryOverlay schema on 11/10 & the final changes for 1.2 are made, we want to get whatever changes are necessary made to this repo to persist these (this was discussed here )
List of differences: https://github.com/Esri/joint-military-symbology-xml/compare/esri-implementation
that should be captured in this repo - mainly jmsml.config?
Here is a graphic depiction of the changes that need to be reconciled between the 2 versions:

Done in #242 .  The new Domain and Schema sample CSV files can now be used with the GDB automation GP tools to build a new GDB.  There will still be some minor differences between the JMSML export files and the Esri implementation export files, since the latter do not have the extra fields for supporting Subtype creation in GDB.
@csmoore , please test these new export CSV files and I will address any remaining issues when I return from vacation/holiday.

A GDB built with the GP tools, based on the #242 schema output can be found here: https://esri.box.com/s/g69907ppzeaix10both0az42uggo05dt

@abouffard - just to confirm before I start verifying this - there should be no differences between master and esri-implementation branches of the samples folder?

I looked at this and it is very close, just need to remove those extra quotes from the non-countycode csvs (this was previously requested at https://github.com/Esri/joint-military-symbology-xml/pull/242#discussion_r47088366 ) since this broke our original contract/convention we agreed upon in early 2015. Assigning back to @abouffard to implement this change before closing,

JMSML #248 removes those quotes from all but the actual country codes where embedded commas exist.  So the diff display you have above looks similar to what I have and is correct.

Removal of HostileOrEnemy domain
Addition of the Schema.ini to help support the domain assignments on subtypes
Double quotes removed from all the indicated amplifier CSVs

The military_feature_schemas folders should be identical.

Thanks for the update, looks good (and now behaves more like Excel csv which only adds the quotes if a cell actually has a comma).


Add sumologic source

Sumologic log platform
https://www.sumologic.com/
Reviewed with pylint and black

is there something that I can help to move this forward?
outside of the points left above for which I would like inputs too.


Code quality improvement idpmgt

-Removing plausible Critical, Major and Minor issues related to idpmgt Module based on SonarQube results.
-Updating Licence Headers.

Created a new pull request (https://github.com/wso2/carbon-identity/pull/373/commits), to segregate and separate the fixes only for idp-mgt module.The aforementioned, new pull request includes fixes for the suggested review comments in this pull request.

Closing as per comment above by Kasun, Refer PR #350 and #373 for the updates.


Large Numbers are being converted into scientific notation

From code plex
"Am I the only one experiencing this? I can't believe that.
I haven't seen any documentation on this issue.
I'm using version <IP_ADDRESS>. Everything else works fine.
If I do Save as from excel the number formats just fine.
When doing excelDataReader.AsDataSet I get a scientific notation number.
This number<PHONE_NUMBER>03960000 becomes this - 1.00E+17.
This is a complete deal breaker for me.
I like the library because it's fast and easy to use but if I can't resolve this I have to find another library to use.
Any info would be greatly appreciated.
Thanks."

Actually I think this is Excel's display of the number.  I have a utility that exports the dataset to a CSV file... if you open the CSV in Excel, it'll display with the "...+E" number until I double-click on that cell... but the CSV itself displays the number as it is...   When creating the CSV I just take the value from a datagridview cell and do a .ToString()...

I am having the same issue. Is there a solution?

Ah you doing ToString on a double as indicated above?
On 12 Feb 2015 18:30, "olivegarg"<EMAIL_ADDRESS>wrote:

I am having the same issue. Is there a solution?
--
Reply to this email directly or view it on GitHub
https://github.com/ExcelDataReader/ExcelDataReader/issues/39#issuecomment-74124636
.

For my purposes, I ended up having to use Excel's com to open the data and set all the column's formats to "Text".  (.opentext(...))  If this is what you are looking for I can list the code.... but my problem was only a  display issue in Excel.

This sounds like a formatting/rendering issue. Closing this and defering to #215


add sunrise / sunset to Location

In reference to changes in #93:
add the following functions to :py:class:Location``:
get_sunrise and get_sunset and deferred from these get_dayduration.
This helps filtering values, e.g. set night values to np.nan.

Probably a good idea, though it's not likely to happen as part of that PR. Are you aware of the get_sun_rise_set_transit function? It returns both sunrise and sunset. I'm less interested in get_dayduration since I think it's less likely to be used and it can easily be calculated if needed (though not totally opposed to it).
All that being said, I've found that filtering using zenith or elevation angle is usually a better approach.

I'm in need of this functionality, and am looking for opinions about implementation. I'd prefer methods attached to a PVsystem or Location object that mimic pyephem, e.g., Location.get_sunrise(date), Location.get_next_sunrise(datetime).
The current get_sun_rise_set_transit runs solarposition.spa and returns only sunrise, sunset and transit.  #316 describes some odd behavior of get_sun_rise_set_transit and ideas about fixing it.  Alternatively, we could request sunrise etc. from solarposition.spa (which is what get_sun_rise_set_transit is doing) or use solarposition.pyphem by adding a call to the appropriate method of the Sun object.
I'd like to avoid a workflow that calculates ephemeris twice, which seems to be the likely result if we add an independent get_sunrise function.
Thoughts?

couple of ideas

when I fixed the timezone bug in spa, I changed the SPA function code to SPA_ALL which calculates sunrise, sun-transit, and sunset times, so if it's not implemented in the numpy version of spa, you could use the NREL C version

I think sunrise/set is a perfect use for the analytical zenith function, just find where it equals zero, either using a solver, or by solving it analytically:
0 = np.arccos(
    np.cos(declination) * np.cos(latitude) * np.cos(hour_angle) +
    np.sin(declination) * np.sin(latitude)
)
1 = (np.cos(declination) * np.cos(latitude) * np.cos(hour_angle) +
     np.sin(declination) * np.sin(latitude))

so
np.cos(hour_angle) = ((1 - np.sin(declination)*np.sin(latitude)) /
                      np.cos(declination)*np.cos(latitude))

is that right?

Location still seems like an appropriate place for this functionality.
Sorry if I'm picking at a typo, but so we're all on the same page...

there is no solarposition.spa.
pvlib.solarposition.spa_python() and pvlib.solarposition.get_sun_rise_set_transit() each import pvlib.spa by calling pvlib.solarposition._spa_python_import(). This allows for optional numba support that would not be possible using the standard imports at the top of pvlib.solarposition.
pvlib.solarposition.get_sun_rise_set_transit is a wrapper around pvlib.spa.transit_sunrise_sunset.

I'd like to avoid a workflow that calculates ephemeris twice (once to get solar position, and again to get sunrise and sunset), which is what happens with the current get_sun_rise_set_transit.

I'm not sure how avoid two different functions because it seems that they do two different things. A function to calculate sunrise/sunset should accept a date and return a collection of datetimes. A function to calculate solar position should accept a datetime and return a collection of angles. I'm having a hard time thinking outside of this box.
In any case, the get_sun_rise_set_transit function could certainly be modified to use either pyephem or pvlib.spa or an analytical solution (controllable by a kwarg). We'd want to make the API consistent for all of the methods.

Silly me, sunset/rise is at zenith of pi/2 not zero, comments above corrected

Assuming it holds water, I'm curious how much more performant the above analytical solution might be. Perhaps it could be added as one of the how options to get_sun_rise_set_transit() as part of the proposed addition the to the Location API?

i guess it seems to work, if I compare it to the online spa calculator I get nearly the correct sunset times:
from datetime import datetime, delta
import numpy as np
import pytz
import pandas as pd

dt = pd.DatetimeIndex(start='2018-01-01 0:00:00',
                      end='2018-12-31 23:59:59',
                      freq='H').tz_localize('Etc/GMT+7')

lat, lon = 39.743, -105.178
latrad, lonrad = np.radians(lat), np.radians(lon)  # radians

eoq = equation_of_time_pvcdrom(dt.dayofyear)  # minutes
decl = declination_spencer71(dt.dayofyear)  # radians

def get_sunrise_angle(decl, latrad):
    return np.arccos(-np.tan(decl) * np.tan(latrad))

sr_angrad = get_sunrise_angle(decl, latrad) # radians
sr_ang = np.degrees(sr_angrad)

def local_hours(times, sr_ang, lon, eoq):
    timezone = times.tz.utcoffset(times).total_seconds() / 3600.
    return (sr_ang - lon - eoq/4.)/15. + 12. + timezone

lh = local_hours(dt, sr_ang, lon, eoq)

print(lh[0])
#16.69168401501784

print(timedelta(hours=lh[0]) +
    pytz.timezone('Etc/GMT+7').localize(datetime(2018, 1, 1, 0, 0, 0)))
#2018-01-01 16:41:30.062454-07:00

#from NREL MIDC SPA at (39.743, -105.178)
#Date,Time,sunrise,transit,sunset
#1/1/2018,0:00:00,7.364246,12.073578,16.785242

print(timedelta(hours=16.785242) +
    pytz.timezone('Etc/GMT+7').localize(datetime(2018, 1, 1, 0, 0, 0)))
#2018-01-01 16:47:06.871200-07:00

It's about 6 minute difference :frown:

Maybe I should've tried the other declination or eoq formulas?

Your formula matches the one in my Vignola book.  Maybe the SPA version gives you apparent zenith == 90?
On the rare occasions when I need sunrise/sunset times I usually have a time series of some sort I'm working with, and just interpolate the timestamp for apparent_zenith == 90.  But most of the time I'm happy filtering on apparent_zenith > 90.

Sorry if I'm picking at a typo, but so we're all on the same page...

You're not, and thanks.

pvlib.solarposition.spa_python() and pvlib.solarposition.get_sun_rise_set_transit() each import pvlib.spa by calling pvlib.solarposition._spa_python_import(). This allows for optional numba support that would not be possible using the standard imports at the top of pvlib.solarposition.

This is important and I had missed this.

pvlib.solarposition.get_sun_rise_set_transit is a wrapper around pvlib.spa.transit_sunrise_sunset.

Right.  Now that I look at the spa module it is clear that we won't calculate the ephemeris twice (which I had in mind when I was considering an earlier suggestion that sunrise/sunset are based on zenith, then mistakenly transposed that idea to the spa and pyephem functions).

I'm  not sure how avoid two different functions because it seems that they do two different things. A function to calculate sunrise/sunset should accept a date and return a collection of datetimes. A function to calculate solar position should accept a datetime and return a collection of angles. I'm having a hard time thinking outside of this box.

We're in the same box.

@adriesse I knew the analytical functions don't account for atmospheric refraction, I just didn't realize it would be so large. Visibly the largest difference in zenith to me appears at noon, but it makes sense that refraction would be larger when the angle is greatest, ie sunrise/sunset. Always learning, thanks! @cwhanse glad you can get what you need from spa


show this week

Is it possible to do something along the lines of hcl show this week with chronic?
For example, executing that on Wednesday would show you hours and tasks from Sunday - Wednesday.

Sorry, this is a duplicate of #15.


Investigate global indexing perf hit caused by China indexing

By introducing V3 indexing to China blob storage, and adding a dependency on this indexing to our global indexing pipeline, we have hurt perf significantly. We should investigate how we can correct this.

Experiment Notes:
https://microsoft.sharepoint.com/teams/NuGet/_layouts/OneNote.aspx?id=%2Fteams%2FNuGet%2FTeam%2FNugetServer%2FNugetServerTeamNote&wd=target%28Issues.one%7C609EE7E4-8366-4FAB-85DE-FA0ECD809891%2FInvestigations%20for%20the%20performance%20difference%20of%20the%20v3%20china%20pipeline%7C27225281-CC97-43FB-B794-E694471415C6%2F%29
onenote:https://microsoft.sharepoint.com/teams/NuGet/Team/NugetServer/NugetServerTeamNote/Issues.one#Investigations%20for%20the%20performance%20difference%20of%20the%20v3%20china%20pipeline%20vs%20north%20America%20pipeline&section-id={609EE7E4-8366-4FAB-85DE-FA0ECD809891}&page-id={27225281-CC97-43FB-B794-E694471415C6}&object-id={635C1162-6391-49BC-8C2E-EB5697420598}&12


Trouble to use php-redis

Hi Dave,
I'm using your docker-files and activate php-redis with PHP_ENABLE_REDIS=true on the environment. But if I'm login into bash and execute a php script i got the following error:
$ bin/console help
PHP Warning:  PHP Startup: Unable to load dynamic library 'redis.so' (tried: /usr/lib/php/20220829/redis.so (/usr/lib/php/20220829/redis.so: undefined symbol: igbinary_serialize), /usr/lib/php/20220829/redis.so.so (/usr/lib/php/20220829/redis.so.so: cannot open shared object file: No such file or directory)) in Unknown on line 0

Have you any idea?

Can you tell me what image tag you are using?

Hi Dave,
Dockerfile:
FROM tiredofit/nginx-php-fpm:debian-8.2

# additional ENV vars
ENV NODE_VERSION=20.5.1
ENV NVM_DIR=/root/.nvm

# Install NVM for node
RUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash
RUN . "$NVM_DIR/nvm.sh" \
    && nvm install ${NODE_VERSION}
RUN . "$NVM_DIR/nvm.sh" \
    && nvm use v${NODE_VERSION}
RUN . "$NVM_DIR/nvm.sh" \
    && nvm alias default v${NODE_VERSION}
ENV PATH="/root/.nvm/versions/node/v${NODE_VERSION}/bin/:${PATH}"

# Install npm and yarn
RUN curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -
RUN echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list
RUN apt update \
    && apt install vim nodejs yarn -y

RUN php-ext enable redis \
    && php-ext enable calendar \
    && php-ext enable zip

docker-compose.yml:
services:

  php:
    build: ./docker
    container_name: "${PROJECT_NAME}-app"
    labels:
      - "traefik.enable=true"
      - "traefik.docker.network=web"
      - "traefik.http.routers.${PROJECT_NAME}.rule=Host(`${PROJECT_NAME}.${DOMAIN_SUFFIX}`)"
    env_file:
      - ./.env
    ports:
      - "9003:9003"
    volumes:
      # Source code
      - ./app:/www/html
    networks:
      frivol:
      web:
        aliases:
          - "${PROJECT_NAME}.${DOMAIN_SUFFIX}"
networks:
  frivol:
    driver: bridge
  web:
    external: true

my .env:
PROJECT_NAME=admin
DOMAIN_SUFFIX=docker.localhost
TRAEFIK_PATH=../traefik

PHP_IDE_CONFIG="serverName=${PROJECT_NAME}.${DOMAIN_SUFFIX}"

NGINX_WEBROOT=/www/html/public
PHP_ENABLE_REDIS=true
PHP_ENABLE_IGBINARY=true
PHP_ENABLE_XDEBUG=true
PHP_MEMORY_LIMIT=2G
PHP_XDEBUG_MODE=develop
PHP_XDEBUG_CLIENT_HOST=host.docker.internal
PHP_XDEBUG_CLIENT_PORT=9003

OK, there is definitely something wrong here with the build system! I just pulled those images myself and found it's giving me 7.4.2 which is from February. 7.6.15 is the latest. I'm heading out for a few days into the woods, and will keep this as a TODO for when I return Monday. It should be a quick fix. In meantime, did you want to try this tag: 8.2-debian-bullseye - I believe this should give you immediate results. I'm going off this reference: https://hub.docker.com/r/tiredofit/nginx-php-fpm/tags


Discuss window size explicitly for rrs (and other families)

Using rrs as a rolling checksum (as opposed to hashing a fixed sequence of bytes) requires choosing a window size, which also appears in the definition of b(k, l) as l - k + 1. Of course applications may tweak this to suit their needs, but I think the spec would be clearer if it discussed window size explictly as a parameter for the rrs family -- or maybe once more hashes are covered there could be a general discussion of window size applying to all of them.

Yeah, we definitely need to specify the window size somewhere, though as you point out this could be a hash-independent thing.

This is in the spec now, so I'm going to close.


fix: pass proper env var to tracetesting Dockerfile

Changes
This PR fixes the CLI version in test/tracetesting/Dockerfile to use the env variable that was added as part of https://github.com/open-telemetry/opentelemetry-demo/pull/1239. This guarantees the use of the same image version for the tracetest server and CLI in the trace-based process.
Merge Requirements
For new features contributions please make sure you have completed the following
essential items:

[ ] CHANGELOG.md updated to document new feature additions
[ ] Appropriate documentation updates in the docs
[ ] Appropriate Helm chart updates in the helm-charts

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

hi @julianocosta89 and @mviitane ! talking with Tracetest team, we believe that this issue caused some of the problems that you had on https://github.com/open-telemetry/opentelemetry-demo/issues/1273.
@jorgeepc can you add an entry on the CHANGELOG with this change?


Implement Dark Theme Option for Enhanced User Experience

Many users prefer dark themes in applications due to various reasons such as reducing eye strain, improving visibility in low-light environments, and aesthetic preferences. Currently, our web app only offers a light theme, limiting user customization and potentially impacting user satisfaction.
Implement a dark theme option in the web app to provide users with a more customizable and comfortable viewing experience. This feature should include:
A toggle switch or setting in the user profile/preferences section to enable/disable the dark theme.
Consistent styling across all components and pages to ensure a seamless transition between light and dark themes.
Compatibility with all features and functionalities of the web app, ensuring no loss of usability or functionality in either theme mode.
Accessibility considerations, such as maintaining sufficient color contrast and readability in the dark theme.

Hi!

Is it not working from Settings? (Top corner right)


Lack of a descriptive enough hint in step 22 of building skyline project

Describe the Issue
In the hint below it ask to create a new variable, but it doesn't say where we have to add. A camper like me add variable in .bb2 which is normal we did same in .bb1, which cased confusion to a camper.
Affected Page
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-css-variables-by-building-a-city-skyline/step-22
Your code
.bb2 {
  width: 10%;
  height: 50%;
  --building-color2: #66cc99;
}

Expected behavior
Hint should clearly say where we have to add variable instead of Hint
You should give --building-color2 a value of #66cc99.
Screenshots

System

Device: [Desktop]
OS: [Windows 10]
Browser: [Chrome]
Version: [106.0.5249.119 ]

Additional context
No response

The step instructs where to add the other variable imo.

Create a new variable below the other one
There is only 1 variable in the code --building-color1 and it should be inferred that the other one goes right below it.

However, I still agree that the hint should be more meaningful in case someone misunderstood it.
Will add a new pr soon

We should change:

Create a new variable below the other one called --building-color2 and give it a value of #66cc99

To:

Create a new variable below your --building-color1 variable. Name your new variable --building-color2 and give it a value of #66cc99.


CookieAuthenticationHandler.RequestRefresh does not safeguard against ArgumentOutOfRangeException for DateTimeOffset.Add

https://github.com/aspnet/Security/blob/d0d72782745edc41c79c501ff2210058a4eadb46/src/Microsoft.AspNetCore.Authentication.Cookies/CookieAuthenticationHandler.cs#L88-L102
If the value of expiresUtc is very high (realistically, DateTimeOffset.MaxValue) then subtracting the value of issuedUtc to get the timeSpan results in timeSpan not being valid as an argument to Add: The added or subtracted value results in an un-representable DateTime. This prevents a developer from being to able to, say, set context.ShouldRenew = true from within OnValidatePrincipal and obtain the expected result of having the cookie renewed/refresh.

Closing because we don't feel this is important enough to fix. Hopefully the error gives a hint that some unusually large date is being used. If you feel this happened in some reasonably common case, we can take another look.

@Eilon this is the case when the cookie is set to ‘not expire’ — the framework uses MaxValue — but there are times where we would like to cause a renewal.

@tuespetre can you show more about what your app code would look like such that you would run into this? We took a look and everything we thought of we felt wouldn't be common.

I was wrong; we are setting the ExpiresUtc to DateTimeOffset.MaxValue (in the call to SignInAsync.)
MaxValue seems like the right way to say "This cookie should be considered non-perishable", but I suppose we could use DateTimeOffset.UtcNow.AddYears(500) to the same effect.

@tuespetre yeah that's what we were thinking too. I doubt any web browser that exists today will exist in 500 years 😄


What would the default ~/.config/meteor/config.json look like?

I like the way things are, I just want to make a few tweaks to a few things. What is the default config.json?

The default config would look something like this:
{
  "commitTitleCharLimit": 48,
  "messageTemplate": "@type(@scope): @message",
  "messageWithTicketTemplate": "@ticket(@scope): <@type> @message"
  "prefixes": [
    { "type":  "feat", "description":  "a new feature"},
    { "type":  "fix", "description":  "a bug fix"},
    { "type":  "bug", "description":  "introducing a bug"}
    ...
  ]
}

You can see the default prefixes here


mixing input types in one gallery

Is it possible to have different image types in one gallery?  For example have a link to a youtube video with a thumbnail next to an image link?

I see that you can write individual items to the gallery in the javascript function call.  It would be nicer if it could determine automatically from the HTML elements what type the gallery item has.


Async ORM

Is your feature request related to a problem? Please describe.
The current Tortoise ORM integration guide is handy, but obviously there's so much we could do to make the experience of using a DB in Bocadillo better if we had something more official.
Describe the solution you'd like
Build an official extension or something to allow users to use an ORM in the asynchronous context of Bocadillo without pain. It can (should?) require to install a separate package, but bootstrapping or configuration should be as automated as possible.
Describe alternatives you've considered

Build our own ORM: waste of time and energy considering
Keep it as is and loosely rely on a third-party ORM through mere advice: using a relational DB is common enough that we want it to become one of those carefully included batteries (although perhaps optional).

Additional context
https://github.com/tortoise/tortoise-orm

Various solutions are arising (Tortoise, orm). Since we already have how-to guides and tips on integrating with these in the docs, and considering how volatile the ecosystem is at the moment, I don't think we should focus on an official integration yet.


Astra UI component: Astra URL component is not validated on entry

The UI component for astra does not validate the connection URL on text entry.
When pasted in, the dialog should check if it is a legal URL before trying anything else. I accedental pasted in a token, and did not realise it until the "run" phase even though it clearly was not a URL
Version:
Starting Langflow v1.0.0a33...

Hey @zznate
Have you tried the new version yet? Please check it out and let me know if the issue persists.

@zznate
Thank you for your contribution! This issue will be closed. If you have any questions or encounter another problem, please open a new issue and we will be ready to assist you.


getting NPE when connection not connected

This happened because I didn't call connection.connect().
If it is possible, I suggest to improve the message in such case.
Here is the stacktrace:
Exception in thread "main" java.lang.NullPointerException
at com.github.mauricio.async.db.mysql.codec.MySQLConnectionHandler.com$github$mauricio$async$db$mysql$codec$MySQLConnectionHandler$$writeAndHandleError(MySQLConnectionHandler.scala:324)
at com.github.mauricio.async.db.mysql.codec.MySQLConnectionHandler.sendPreparedStatement(MySQLConnectionHandler.scala:208)
at com.github.mauricio.async.db.mysql.MySQLConnection.sendPreparedStatement(MySQLConnection.scala:241)

I merged a fix to the fork of jasync-sql: https://github.com/jasync-sql/jasync-sql/pull/14


[DRAFT!!] New features (v2.3.0-dev8)

THIS IS A DRAFT PR - DON'T MARK IT AS READY, PLEASE.

I'm currently working on new features, some of which are so big that they can't be in a minor 2.2.2 update...
I've added DependencyModule to deal with softdepends, one of which is now WorldGuard. It allows players to use additional features which won't work unless WorldGuard is installed - in that case nothing should go wrong, it's all done in a way that it shouldn't be a problem.
Another big change is driving on both blocks and slabs. The 'both' option is now default in config.
BE AWARE: This should NOT be merged until 2.2.1 is released. (I guess 2.2.1 is already ready to be released, isn't it?) Also, it should probably be developed in another branch (not master), because if critical bugs were to be found in 2.2.1, we would be able to fix them.

Please, do not mark as ready until 2.2.1 is released.

Please, do not mark as ready until 2.2.1 is released.

Added Vault soft-dependency and filling players' jerrycans.
Everything can be configured in config.yml, there are tons of options. I tried to add as many explanations as possible into config.yml, as well as tried to make them easy to understand, concise, and eloquent.
Players can fill their jerrycans by right-clicking levers/tripwire hooks (can be played with in config) on gas stations (WorldGuard needed). If they have Vault and enable it in the config, they may also be charged for filling up their jerrycans. The price can be adjusted as well.
There are also 2 new permissions: mtvehicles.filljerrycans to even be able to use this new feature (server owners can set that players needn't have this permission in the config) and mtvehicles.filljerrycansforfree which enables players not to pay for filling up jerry cans.
Note: I had to add quite a lot of messages and since I don't speak Spanish, nor Dutch, I used google translator... You guys may adjust that after pushing. 😜
Also, everything should be fail-proof, specific features, which depend on other plugins, are disabled if softdepends are not found. I have hopefully tested everything, haven't found any bugs (yet).

Why are you static abusing DependencyModule, no need to make a static method

I've changed quite a lot of code, it still needs to be tested. (I've quickly tried the WorldGuard flags and they seem to be working fine.)

Regions are no longer listed in config.yml, they are defined by custom flags instead - mtv-gasstation, mtv-place, mtv-enter, and mtv-pickup. (Everything should be explained in the config; later, we'll probably add it to the readme as well.)
Also, I have completely disabled WorldGuard as a soft-dependency in 1.12 because it is no longer supported by their developers and thus it doesn't use the latest API...
Lastly, I have rewritten the movement section (a bit). I guess it may be easier to maintain now. 1.12 movement is still vastly different though due to the old mechanics.

It should be ready for review.

I've edited all the movement files once again. The most of the code is now located in one abstract class, the version classes contain the NMS stuff...


Animas: Cap long running suspended basals after 5 days

We were capping scheduled basals after 5 days, but this logic wasn't applied correctly to suspended or final basals. This PR breaks out the functionality into its own validation function so it can be applied to all basal types.
Pinging @jebeck for review - BA has confirmed that it works with tester pump.

Linking Trello card for reference: https://trello.com/c/5Q1QHuWU

 <ux:0 dev:3 tst:2> [uploader] [animas] remaining work on Animas

Overall LGTM, just minor points re: naming and annotation code(s). 🚢


Link password turns into "not mandatory" for links with viewer permission

Describe the bug
Password is mandatory for public links in creation. But, if link has "Viewer" permission, it's allowed to remove the password and check the content without typing password.
Steps to reproduce

In web, create a link over an item adding the mandatory password that fulfills all criteria about uppercase, lowercase etc...
Open the link in other browser -> password is required
In web, go to the link description, click 3-dot-button -> Remove password is available, so click on it
Open the link in other browser -> password is NOT required

Actual behavior
Password is allowed to be removed from the link, whereas it is mandatory in link creation. Check the following video with the steps and the final result:
https://github.com/owncloud/ocis/assets/14894746/07a2da8f-a805-47d9-93df-864535335e89
Expected behavior
Password enforced is not allowed to be removed.
Setup
ownCloud Web UI 8.0.0-rc.1 index.html-MZztZoFM.mjs:1:449459
Infinite Scale 5.1.0-prealpha+f56cf085a Community
Additional context
This is reproducible in server returning the following capabilities:
"password": {
    "enforced": false,
    "enforced_for": {
           "read_only": true,
           "read_write": true,
           "read_write_delete": true,
           "upload_only": true
     }
}

password is enforced for every permission level, so, it should be never allowed to be removed from the link.

This is actually a feature called
„opt out of mandatory password for viewer links when you have the respective permission in the user role“

Opt out means „you can create the share only with a password but can remove it afterwards“

I did not know about this kind of exception, but this is not implemented in the android mobile client. If password is enforced via capabilities, is enforced for creation and edition cases with no exceptions. That means, web and other clients diverge in a behaviour that should be the same.
Should coordinate in order to align behaviours.


Add pagination functionality to the fetch_* methods

Okay so I see there are concerns about params my personal preference would have been either of these combinations
Either
fetch_accounts(page:1, page_size: 50)
OR
fetch_accounts(offset:0, limit: 50)
'limit' is still kind of vague and is related to the other flow which I believe can cause confusion in the usage because its widely used along with offset. and page_size seems more self-explanatory to me since it is right next to page number so tells the whole story like return the 2nd page and its size should be 50. Thoughts?

but then again in the response
'next': 'http://<IP_ADDRESS>/confirmation_blocks?limit=10&offset=10',
the keywords are these limit=10&offset=10 so it can be confusing there so it's a tricky situation.

Okay so I see there are concerns about params my personal preference would have been either of these combinations
Either
fetch_accounts(page:1, page_size: 50)
OR
fetch_accounts(offset:0, limit: 50)
'limit' is still kind of vague and is related to the other flow which I believe can cause confusion in the usage because its widely used along with offset. and page_size seems more self-explanatory to me since it is right next to page number so tells the whole story like return the 2nd page and its size should be 50. Thoughts?

Limit is used in the endpoint because it could return less results. With page_size we could think that this is the actual page size, which is wrong. Moreover, I would have used the same parameters as the endpoints (offset/limit) because page/page_size reduce the flexibility.
PS : Maybe we could also add a function "fetch_all_pages" for every functions ?

PS : Maybe we could also add a function "fetch_all_pages" for every functions ?

It sounds too cumbersome. I don't think users would like to fetch all pages. Let them choose the offset and limit to fetch which items they need

Lads let's vote for a decision in the slack channel :)


Wrap LINQ object array delegate thunk in a try/finally

This ensures we copy back byref args. It wasn't possible when this code was originally witten because the IL generator couldn't generate finallys.
Closes #2910.

CppCodeGen failing. System.Linq.Expressions\src\System\Linq\Expressions\Interpreter\LightCompiler.cs(1831,342): error G7DF253DA: expected unqualified-id

CppCodeGen failing

Sigh, forgot it runs here. It would have trouble with the throw as well.


Cannot get MQTT endpoint

Exported the FB data in chrome using C3C UFC Utility
api.http.send_message(
msg="Hello World!",
thread_id="8640928872641524",
)
Receving this error :
Cannot get MQTT endpoint
How I can solve this problem thank you

I will have a look at it

same


Charge_mode on/off fails

Don't work:
Charge_mode on: KO > need lowercase
Charge_mode off: KO > need lowercase
Hvac off: KO > never work
Work:
Hvac on: OK
Calendar_set: OK > Activ Cal
Charge_go: OK > Deactiv Cal
I think the problem with charge_mode is the upper case letters in the script.  if I put SCHEDULE_MODE or ALWAYS_CHARGING in lowercase, the script does not work.  But I think we have to send lowercase to Renault.  can you fix this problem?
Originally posted by @JeedHome44 in https://github.com/hacf-fr/hassRenaultZE/issues/83#issuecomment-739551495

Charge-mode issue is a bug on renault-api which will be fixed in the next release: hacf-fr/renault-api#87
Do you have some traces to show if the Renault servers accepted the bad values or if they were rejected?

@JeedHome44 renault-api is updated to v0.0.3.
Do you want to provide a PR to bump the renault-api version here ?

I made the other change by inference but I don't know how to do this one.  I let you do it.  😉

It's a good exercise for you also... for this you only need to update the manifest file:
https://github.com/hacf-fr/hassRenaultZE/blob/master/custom_components/renault/manifest.json

Ok i will test 😉

Close #88

You have to add comment on the PR to close the Issue (not a comment on the issue to close the PR)

like that?


buildImage() stream silently fails when build context is too large

Today I stumbled upon a problem where the buildImage() function would silently fail when the passed-in build context is too large.
Here's my call:
const stream = await docker.buildImage({ context }, { dockerfile, t })
return new Promise((resolve, reject) => {
  docker.modem.followProgress(stream, (err, res) => {
    if (err) {
      reject(err)
    }
    resolve(res)
  })
})

And the context is a path to a directory which has a bunch of files. In my case the context included a large node_modules directory.

Same issue here after updating to v3.
In my case the package-lock.json file was the large file.
@pmuensI suggest you use an older version for now

Could you give more details about this?
How so "too large"? Larger than what?

Is it only happening on v3.x?
Could be related to this: https://github.com/apocas/dockerode/pull/490

+1, had this for a package-lock.json of 308K and node_modules of 30K. Version 3.0.2.

I can verify that this issue is happening after upgrading to v3.x (working fine with 2.5.8). Not sure if it's related to big files or not but surely works after I remove the folder with big files in it. Otherwise it silently gets stuck. No output, no promise resolving, nothing.

Could someone test the branch https://github.com/apocas/dockerode/tree/debug-build against this?

@apocas
Same problem here.
With your branch (debug-build), the build worked correctly.

Humm so the issue was in the change of tar.pack.
I will revert it and publish.

https://github.com/apocas/dockerode/commit/bd5fd1867997f70180d8da6b57807a993c880ca8


Fix typo in fundamentals.md

I expcet that this pull request will be merged.

Thanks for the contribution!


[Enhancement]: Hide Floating Widget Funciton

Before Requesting

[X] I have searched the existing issues, and there is no existing issue for my feature request

What feature do you want?
Hi, any way to hide the floating widget, for me, I prefer hiden it and use the shortcuts to activate the function.
Could add a option to hide it ? thx.

As an alternative, would it be possible to show the widget only when it is fetching suggestions from Copilot, as a sort of status indicator, but hide it when it has nothing to display? That way, I don't get distracted by the grey blob but still know that Copilot is working.

As an alternative, would it be possible to show the widget only when it is fetching suggestions from Copilot, as a sort of status indicator, but hide it when it has nothing to display? That way, I don't get distracted by the grey blob but still know that Copilot is working.

It will be tracked in another issue #328
This issue will be closed.


Replace Ace Editor with Monaco Editor

Fixes #431.
This PR introduces the Monaco editor in replacement of the Ace Editor. At this stage for the PR, we are aiming for parity with the functionality previously provided by Ace, with the intention of increasing the functionality after this PR is merged.
Still to do:

[x] Support all prior configuration options.
[x] Re-implement all previous themes, or find suitable alternatives (see https://github.com/brijeshb42/monaco-themes)
[ ] Ensure code editor works in all current core locations (settings areas, CMS editor, Builder plugin)
[x] Try and figure out how to remove the automated loading of the Codicon font, as it's being implemented in the widget's CSS assets.

Changes:

Auto-completing tags preference is no longer available, as Monaco doesn't have this as an option.
Autocompletion and code snippets preferences are no longer available, as these are more contextual and will be implemented based on what is being edited in the editor.
Code folding is now a simple boolean.
The Crimson Editor theme has been dropped - I couldn't find a complete replica of this theme, and it looks too similar to other themes in the list.

@bennothommo what's the status of this?

When I last worked on this, I was having some dramas with the Markdown editor, since that also had to be converted to Monaco. I was hesitant to include another editor just for the Markdown editor, but if we can find a lean one, I'm happy to use that instead and keep Monaco for just the code editing (which it works amazingly with).

What's the problem with the markdown editor? Does it currently use ace?

Yeah it uses Ace currently. I feel keeping Ace around and introducing Monaco for the code editor might be too much "bloat".

I'm fine with having both if we can clearly identify all the locations we can remove Ace from as soon as we get a replacement for the usage of Ace in the markdown editor; that way at least it won't hold us up from getting the benefits of monaco and it'll be simple enough to remove Ace when we replace the markdown editor.
Any thoughts on that?


Add Land Mine activable item

Add support for one activable item, architecture will evolve with the next activable items (with need of actions for next/previous item).
Activate item action is linked to key R (player 0) and T (player 1) (keys to be changed, I used them because they don't change between qwerty/azerty).
Resolves: #198
Linked: #151

Codecov Report

Merging #200 (8fa7070) into master (befb589) will decrease coverage by 0.20%.
The diff coverage is 0.00%.

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


Long delay when playing from very large liked tracks playlist

Sadly, I still have to report a delay when trying to play from this list. How about reducing the number from 200 down to something like 32 or 64? (My 1680x1024 display shows 32 songs when maximized).
#78

I can make this variable configurable.

That's wonderful news, my fiend. Thanks again.

Should be configurable now with tracks_playback_limit. It is 50 by default so you may not need to configure.


rio-tiler incompatible with rasterio 1.0b2

It looks like the rasterio release from today is breaking rio-tiler's functionality on my geotifs (which used to work before): https://github.com/mapbox/rasterio/releases/tag/1.0b2 Here is the error:
/tmp/rio/.env/lib/python3.5/site-packages/rio_tiler/utils.py:162: RasterioDeprecationWarning: dst_crs will
 be removed after 1.0, use crs
  with WarpedVRT(source, **vrt_params) as vrt:

Traceback (most recent call last):
  File "/tmp/rio/tiler.py", line 49, in <module>
    main()
  File "/tmp/rio/tiler.py", line 41, in main
    data, _ = tiler.tile(args.path, x, y, z)
  File "/tmp/rio/.env/lib/python3.5/site-packages/rio_tiler/main.py", line 75, in tile
    nodata=nodata, alpha=alpha)
  File "/tmp/rio/.env/lib/python3.5/site-packages/rio_tiler/utils.py", line 168, in tile_read
    indexes=indexes)
  File "rasterio/_warp.pyx", line 979, in rasterio._warp.WarpedVRTReaderBase.read
ValueError: WarpedVRT does not permit boundless reads

Workaround
pip install 'rasterio==1.0b1' 'rio-tiler==1.0a7'

Small self-contained reproducible program
https://gist.github.com/daniel-j-h/69a967d63d833f74a123e2540bd146b9
Geotifs are from OpenAerialMap, e.g.
https://oin-hotosm.s3.amazonaws.com/5ac7745591b5310010e0d49a/0/5ac7745591b5310010e0d49b.tif
Let me know if I'm doing something wrong here or if this is an issue with rasterio.
cc @dnomadb @sgillies @vincentsarago

@daniel-j-h correct. I never intended Rasterio to be used like it was used in rio-tiler. Boundless reads from a warped VRT can't be supported by Rasterio in the future and I have revoked them intentionally.

https://github.com/mapbox/rio-tiler/pull/45 fix it, just need to make the tests pass.
I expected to have a new version of rio-tiler by EOD.
I'll force the rasterio version to be ==1.0b2 to make sure we don't cause this kind of trouble again ;-)

closed by https://github.com/mapbox/rio-tiler/pull/45 and https://github.com/mapbox/rio-tiler/pull/47


Fix components.opacity option (previously ignored)

Simple fix to ensure that setting components.opacity : false, hides the opacity selector (even if  lockOpacity : false,).

Whoops, yeah - that makes sense. The opacity prop got deconstructed one line above, I've quickly pushed that to this branch :)

I'll publish 1.2.1 later this day, you got covered some neat features / edge-cases :D


Smaller Package Wordlist

I would suggest having a smaller package that implements only English version or an initializer
this will make the bundle size smaller.
No need to require the whole package.

bip39 library has a pull request open right now that is similar to what you ask.
https://github.com/bitcoinjs/bip39/pull/98
branch is breakup
https://github.com/bitcoinjs/bip39/tree/breakup
So maybe use the method described in the README of that branch and copy over the breakup branch?
Just an idea.


Use symbolicmode.chmod to simplify chmod() code.

symbolicmode provides a chmod() method that can take symbolic or numeric permissions, so the function can be simplified.
Note, this depends on symbolicmode 2.x, because I decided (as I was reviewing the use here) that I had the order of the chmod arguments backwards, so I made the backwards-incompatible change and rolled the major version up because of that.

I'm sorry, I didn't intentionally ignore this -- it got lost in github email.


Add description

If a description isn't set the extension gets the inherited description from the parent pom:

If a description isn't set the extension gets the inherited description from the parent pom:

@holly-cummins it uses the description of the deployment artifact ? The runtime module has a description and thought it is enough. Should I add a description property to the META-INF/quarkus-extension.yaml file ?

If a description isn't set the extension gets the inherited description from the parent pom:

@holly-cummins it uses the description of the deployment artifact ? The runtime module has a description and thought it is enough. Should I add a description property to the META-INF/quarkus-extension.yaml file ?

Hm, interesting. I would have thought either the runtime module description or the parent module description would be enough. I just checked, and everywhere else in this repo the description is in the runtime module, and it works fine. So something else is going on.

@aloubyansky, sometimes you notice things I don't. Can you see why the CRT extension's description isn't making it into the registry, when the description for other extensions is? Looking at https://github.com/search?q=repo%3Aquarkiverse%2Fquarkus-amazon-services+<description>&type=code , the declaration for CRT looks similar in structure to the others. The description was added by Sébastien 6 months ago, so it's definitely been in a release since then.

https://code.quarkus.io/?extension-search=quarkus-amazon-crt shows the correct description, doesn't it?

https://code.quarkus.io/?extension-search=quarkus-amazon-crt shows the correct description, doesn't it?

You're right, it does. The extensions/all endpoint of the registry has the inherited description:
{
      "name": "Aws Crt",
      "description": "Parent POM for Quarkiverse projects that includes the default release and artifact publishing related\n    configuration",
      "metadata": {
        "scm-url": "https://github.com/quarkiverse/quarkus-amazon-services",
        "categories": [
          "data"
        ],
...

I wondered if code.quarkus.io could be getting the description from somewhere else, but some other extensions in there do show the parent pom:

And I've just checked https://repo1.maven.org/maven2/io/quarkiverse/amazonservices/quarkus-amazon-crt/3.0.1/, and the quarkus-extension.yaml file in there does show the correct description. So I guess this is a registry or registry upload issue.

Ahh, I think I see the issue. Or part of it, at least.
curl -X 'GET' \   'https://registry.quarkus.io/client/extensions/all' \   -H 'accept: application/json' gives this:
{
      "name": "Aws Crt",
      "description": "Parent POM for Quarkiverse projects that includes the default release and artifact publishing related\n    configuration",
      "metadata": {
...
      "artifact": "io.quarkiverse.amazonservices:quarkus-amazon-crt::jar:2.19.0",
      "origins": [
        "io.quarkus.platform:quarkus-amazon-services-bom-quarkus-platform-descriptor:quarkus-bom-quarkus-platform-descriptor:3.16.1:json:3.16.1"
      ]
    },
    ```

    But the version in maven central I was looking at was 3.0.1. So the registry doesn't have the latest versions, but, presumably, the quarkus platform does, and that's what code.quarkus.io is picking up.

It loos like a data processing issue in the registry. There is nothing to fix in this project.

It loos like a data processing issue in the registry. There is nothing to fix in this project.

I agree. I'll ask Guillaume to move the issue, but I need to figure out what project to move it to; it could be a registry problem, or a registry upload problem, or a release script problem.

How so? I don't see a description in the quarkus-extension.yaml either?

@gastaldi thinks this may be https://github.com/quarkusio/registry.quarkus.io/issues/205, and I agree. So instead of moving this, I'll close it as a duplicate of that issue. One difference is that https://github.com/quarkusio/registry.quarkus.io/issues/205 code.quarkus.io also has the wrong data, but the difference is that in 205 it's not a platform extension, so code.quarkus.io couldn't read from the platform json.


PRL-5356: CA Personal service by Court admin and bailiff- Welsh email

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/PRL-5356
Change description
This ticket is for creating the Welsh email notification to the applicant solicitor and providing access to court administrators to access the orders to be personally served by them or the court bailiff.
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ x] No

Creating new PR with updated master code


extern crate fails doc tests

If a doc test attempts to import any types declared in it's own crate, including the phrase extern crate anywhere in the code will cause the test to not compile, throwing a "unresolved import" error at the attempted import. For example, if we have struct Foo in crate bar, with the crate baz declared under dev_dependencies, these tests will all fail to compile
/// ```
/// extern crate baz;
/// use bar::Foo;
/// ```
pub struct Foo{}

/// ```
/// // The phrase "extern crate" breaks this!
/// use bar::Foo;
/// ```
pub struct Foo{}

/// ```
/// use bar::Foo;
/// let string = "extern crate";
/// ```
pub struct Foo{}

The following error log is given by cargo test:
running 1 test
test Foo_0 ... FAILED

failures:

---- Foo_0 stdout ----
        <anon>:2:9: 2:12 error: unresolved import `bar::Foo`. Maybe a missing `extern crate bar`? [E0432]
<anon>:2     use bar::Foo;
                 ^~~
error: aborting due to previous error(s)
thread 'Foo_0' panicked at 'Box<Any>', ../src/librustc\session/mod.rs:153
stack backtrace:
   0:         0x61cc34dc - strncmp
   1:         0x61cc2b5c - strncmp
   2:         0x61c84d6f - strncmp
   3:         0x67f193ba - strncmp
   4:         0x67f96c9b - strncmp
   5:         0x6ca6943d - strncmp
   6:         0x6ca6e301 - strncmp
   7:         0x661e3803 - strncmp
   8:         0x61caf9ba - strncmp
   9:         0x661e3bba - strncmp
  10:         0x61cc1209 - strncmp
  11:     0x7fff457f8101 - strncmp

failures:
    Foo_0

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured

Thanks for the report! I think this is actually an upstream rustdoc bug, could you open an issue there instead?

Sure. It's re-submitted here.

Thanks!


Restricted and Record Level Security: use ENUM instead of Strings or fields

As the subject

Deprecated old API and documented the new one under "Database Security"


use candle to train model in browser / Chrome / wasm32 ?

Is it possible to use candle to TRAIN a model in browser / Chrome / wasm32 ?
The use case is: say we are explaining MNIST / covnet -- I'd like to be able to have an interactive demo for trainining a MNIST classifier in webpage, doing the traininig
directly in browser.
Thanks!

Sure, the backprop/training part is independent from the backend and should work on any of them including the browser.

Thanks!


Question about plugins. Making sections

Good day everyone,
I would like to write a plugin which would allow me to have mark down such as the following...
++++Section 1++++

# This is section 1
It will be separated from section 2

++++Section 2++++

# This is section 2

And would like the end result to be something like this...
sections: [
    {
        name: "Section 1",
        content: "
This is section 1

It will be separated from section 2
"
    },
    {
        name: "Section 1",
        content:  "
This is section 2
"
    }
]

I have a few questions,
First is this realistic?
Are you aware of a plugin doing this already (couldn't find it via npm)
And If there isn't one could you point me in the right direction. I have a quick read through the api and it seems like its a bit tricky where I should plugin to.
Any tips are greatly appreciated, thanks!

Sorry, i don't see why your question can be related to this package.

I would like to build a plugin to do the above and was hoping you get suggest where I should tie in. I don’t see how that is not relevant but whatever.

@brenwell i don't see how this markup is related to markdown and how output data related to one produced by this package. Correct me, if i'm wrong. Also note, due time constrains i can not discuss too generic questions.


A way to specify options for all scripts in a package

Possibility:
{
  "*": {
    "dependencies": [
      "bootstrap"
    ],
    "packageLocks": [
      "yarn.lock"
    ]
  }
}

* is unlikely to collide with a real script name, but we should probably support an escaping scheme anyway, e.g. \* means the script literally called *.

This would be amazing, currently repeating pnpm-lock.yaml for every script is fragile and repetitive.


auto-contrast method does not work well with ggplot2 development version

Thanks so much for posting this - I've learned heaps :)
I've noticed that the auto-contrast method does not work well with ggplot2 development version. It works perfectly with version 3.4.3.
library(tidyverse)
#> Warning: package 'purrr' was built under R version 4.3.1

contrast <- function(colour) {
  out   <- rep("black", length(colour))
  light <- farver::get_channel(colour, "l", space = "hcl")
  out[light < 50] <- "white"
  out
}

autocontrast <- aes(colour = after_scale(contrast(fill)))

cors <- cor(mtcars)

# Melt matrix
df <- data.frame(
  col = colnames(cors)[as.vector(col(cors))],
  row = rownames(cors)[as.vector(row(cors))],
  value = as.vector(cors)
)

# Basic plot
p <- ggplot(df, aes(row, col, fill = value)) +
  geom_raster() +
  geom_text(aes(label = round(value, 2), !!!autocontrast)) +
  coord_equal()

p + scale_fill_viridis_c(direction =  1)

p + scale_fill_viridis_c(direction = -1)

Created on 2023-09-05 with reprex v2.0.2

Seems like an issue in ggplot2, the geom_raster() should have different colours instead of a single one.

Ah true, geom_tile works
Maybe raster needs numeric x and y


Migrate to single opencv-wasm

Good evening,
I've tried many different ways to use open-cv with electron and other frameworks - and every time, opencv4node just breaks all of the sudden.
I've come to conclusion - it is better to use a pre-compiled wasm version, which is already done in a package - https://www.npmjs.com/package/opencv-web
(it just needs to fix it's types)
Could you migrate the big api change done in this framework into a new opencvwasm4nodejs?
It will not have any issues with usage/installs that we currently have, and it will give you the satisfaction of finally making openCv whole again.

There are even docker files for opencv wasm build, the only thing missing are type support.
Used https://github.com/CezaryDanielNowak/fast-opencv-wasm to build latest opencv 4.10 and it did a great work building it even on windows ( needed to change path for the docker run, but otherwise completly seemless build expirience)
Sadly - provided auto-generated types ( custom script which basicly dumps keys and adds comments on top) does not yield any good types.
@UrielCh
Can you help with auto-generating types based on the sources, js and wasm file?

Hi,
I do not use the WASM version of OpenCV because it lacks many features, is slower, and does not support CUDA.
Currently, I am not using OpenCV for any active projects, as I need to find a real job before investing more time in open-source projects.
I'm currently working on some data conversion tools, LLM, and voice cloning API, so no computer vision right now.


Suggestion: polymorphic object and tuple member type references through literal types

(This seems to have some things in common with #6080 and is strongly related to #1295 but I don't believe it is a duplicate as this one is more general and includes generics and numeric/symbol literal types as well)
This would provide improved type safety for cases where an interface property is referenced through a string having a value that's known at compile time:
type MyType = { "ABC": number };
let x: MyType = { ABC: 42 };

const propName = "ABC"; // 'propName' received the literal type "ABC" (not string)
let y = x[propName]; // 'y' received the type MyType["ABC"] which resolved to 'number'

And with support for generic types added, this could work similarly, but resolve to an intermediate type of the form T[S] where T is an object type and S is a string literal type:
function func<T extends object>() {
	let x: T;
	const propName = "ABC"; // 'propName' received the literal type "ABC"
	let y = x[propName]; // 'y' would receive the type T["ABC"]
}

This could combine with readonly function parameters to provide an alternative solution for #1295 (which was actually where the idea began):
function getProperty<T extends object, S extends string>(obj: T, readonly propName: S): T[S] {
	return obj[propName];
}

// Here T resolves to { ABC: number }, S resolves to the literal type "ABC",
// and T[S] resolves to number
let x = getProperty({ABC: 42}, "ABC"); // Type of 'x' is number

// Here T resolves to { ABC: number }, S resolves to the literal type "CBA"
// and T[S] resolves to any
let x = getProperty({ABC: 42}, "CBA"); // Type of 'x' is any

// Here T resolves to { ABC: number }, S resolves to string
// and T[S] resolves to any
let x = getProperty({ABC: 42}, getRandomString()); // Type of 'x' is any

This may similarly extend to numeric literal types, for tuples:
type MyTupleType = [number, string, boolean];
let x: MyTupleType;
const index = 1; // 'index' received the literal type 1;

let y = x[index]; // 'y' received the type MyTupleType[1] which resolved to 'string'

And work with generic tuples as well:
function getTupleElement<T extends Array<any>, N extends number>(tuple: T, readonly index: N): T[N] {
	return tuple[index];
}

Same can be done with symbol literal types (haven't thought about that much though):
function getSymbolProperty<T extends object, S extends symbol>(obj: T, readonly sym: S): T[S] {
	return obj[sym];
}

duplicate of https://github.com/Microsoft/TypeScript/issues/6678

@mhegazy
#6678 does seem to cover some of the tuple aspect (which is only a small part of this), but this one also covers generic tuples as well:
function func<T extends Array<any>>(tuple: T) {
  const index = 1;
  return tuple[index]; // return type inferred as the polymorphic reference type T[1]
}

type MyTuple = [number, string, boolean];
let x: MyTuple = [12, "abcd", true];
let result = func(x); // type of 'result' is the type MyTuple[1] which resolves to string

this part would be https://github.com/Microsoft/TypeScript/issues/1295.
we have no way today of getting element type of an array.

@mhegazy
Please read this comment in #1295. This is an alternative solution the one originally proposed there and is different from it. The property specifier here is a type rather than a run-time entity.
The idea of a literal type is that it represents a value that is known at compile time. Since
const x = "ABC"

Receives the literal type `"ABC", I have reformulated the proposed solution to #1295 to reference a literal type instead of a parameter, i.e. instead of
function getProperty<T extends object>(obj: T, propName: string): T[propName] {
    return obj[propName];
}

I changed T[propName] to T[S] where S is a type that extends string:
function getProperty<T extends object, S extends string>(obj: T, readonly propName: S): T[S] {
    return obj[propName];
}

I'm using the fact that in case the parameter propName would receive a value that is known at compile time. The type S would be a literal string type and can be referenced in the expression T[S].
I have also generalized this to any position in the code (not just return types) and for numeric literals as well. Numeric referenced are not covered by #1295.
This issue is not a duplicate. It is about understanding the wider implications of this type of polymorphic references through literal types. I did not feel it was appropriate to continue posting about it there.

Seems like the whole discussion has been diverted to arguing whether this is a duplicate or not, and the actual content ignored. I'm sorry but this seems like a complete waste of time. I'll close it myself.

I did not intend to wast any one's time. sorry if i did. i believe i understand the proposal, and it seems to be there are two parts, 1. using the values of const initializes to get better type information, which seems to be tracked by #6678, and 2. the ability to talk about type of a property of a type. the proposal here seems to be a slight variation from #1295. as mentioned in https://github.com/Microsoft/TypeScript/issues/1295#issuecomment-96852169, we are open to accepting PRs for the general proposal, and we would be open to consider your proposed implementation approach as well.
one thing to note, there are no literal types for numbers, or symbols at the moment. so your proposal only works for string literal types.

@mhegazy
That's OK, I did not mean you were wasting my time, more like "it turned out it wasn't that much of a great idea to open a new issue and wasn't positively received, never mind". Sometimes in online conversations there could be some misunderstandings, so it could be one.
Anyway, the modification I proposed for #1295 could be seen as "minor" in the sense that it is still the same syntax and the general approach in relation to the problem presented is very similar (though it does require type parameter inference to be truly effective), but is different (perhaps not "fundamentally" different - that was probably an exaggeration) in the sense that the two cannot work together - either run-time entities are used as specifiers (e.g. T[propName]) or types (e.g. T[S]), having them both would create problems with name collisions etc. and would have somewhat ambiguous semantics.
The features this approach relies on weren't available or even proposed when #1295 was conceived. Things like string literal types and how they are applied to immutable run-time entities and the possibility of read-only function parameters (though I'm not sure if that has been decided on at this point).
There are also some interesting extensions that can be done with this, seemingly without significant effort as it relies on conventional inference mechanisms of the language. For example, as a complement to #6080 (or maybe as an application for #7722) it could support more complex scenarios like:
function getAnyOneOfTwoStrings() "a" | "b" {
    if (Math.random()) > 0.5
      return "a";
    else
      return "b";
}

function f<T extends object, S extends string>(obj: T, readonly str: S) {
  return obj[str];
}

let MyType = { a: number, b: string, c: boolean }
let x: MyType;

// T resolves to MyType, S resolves to "a" | "b"
// MyType["a" | "b"] resolves to number | string
let result = f(x, getAnyOneOfTwoStrings()); // type of result is number | string

This may be very difficult or even impossible to implement with the original proposal, but may come essentially "for free" with this slight modification.

I don't think the examples I gave so far were convincing enough to truly demonstrate the strength of this approach.
The previous example could still somehow (though not very elegantly) use type inference to "pull out" the possible list of literals even with the previous approach:
function func<T>(obj: T, propName: string): T[propName] {
	...
}

let x: "a" | "b;

func<T>({a: 123, b: "ABC"}, x);

I mean, even if this looks like a real 'stretch' or somewhat semantically inaccurate.
However there are some cases where there is no possible way to get any type information, as there isn't even a particular parameter to reference!
function func<T>(obj: T, getPropName: () => string): T[???]; // What would T reference here?

But when using the type as a specifier, this isn't really a problem, the existing machinery of type argument inference would easily infer it:
// No problem here:
function func<T extends object, S extends string>(obj: T, getPropName: () => S): T[S]

// T resolves to {a: number, b: string}, S resolves to "a" | "b"
// return type is {a: number, b: string}["a" | "b"] which resolves to  number | string
func({a: 123, b: "ABC"}, () => Math.random() > 0.5 ? "a" : "b");

This can be extended to arbitrarily complex expressions, as complex as type argument inference could support:
// No problem here as well:
function func<T extends object, S extends string>(obj: T, complexObject: { num: number, getPropName: () => S}): T[S]

// T resolves to {a: number, b: string}, S resolves to "a" | "b"
// return type is {a: number, b: string}["a" | "b"] which resolves to  number | string
func({a: 123, b: "ABC"}, { num: 123, nameCallback: () => Math.random() > 0.5 ? "a" : "b"});

Is this related to #6080?

@DanielRosenwasser
Yes, I have mentioned it may provide a solution to it but it goes much further than that. It also includes intermediate polymorphic expressions like T["a" | "b"], or even T[S] where both T and S are generic parameters, and T must extend object  and S must extend string. Also it describes similar functionality of for tuples, i.e. T[N] where T must extend Array<any> and N must extend number.

The request in the OP should be handled by the new keyof and T[K] operators introduced by https://github.com/Microsoft/TypeScript/pull/11929


App icon is missing

The app is without an icon in the menu in the dock and in the "About" window:
"Apps" menu

Dock

About Window

Well, after uninstalling the app and running flatpak repair and then installing it again, those icons are showing up.
I'll try installing the app in another machine later.

I installed the app in another Ubuntu machine and it's working fine.
I'm not sure why those icons were missing before.


flags not showing

I am getting the same issue. Can you please help solving it?

I have the same issue, what's the fix for that?!! any help is appreciated. Thanks

@jacky-ew @Dhara-Actonate @marwajomaa

What is your setup? Create React App? Next.js?
Could you try the workaround in https://github.com/patw0929/react-intl-tel-input/issues/371#issuecomment-921258881?

@jacky-ew @Dhara-Actonate @mariusandra
In my case:

Notice that the url source of background image is shown as '[object Module]'
This is caused by the url-loader.
You should modify your url-loader configuration with options below:
options: {
    esModule: false,
},

This will fix the issue in my case. Hope it will be helpful to you.

I have had to install url-loader https://www.npmjs.com/package/url-loader
This will fix the issue.

i just ran into this after upgrading react-scripts/webpack to ~v5. what works for me is following webpack asset-modules docs
{
    test: /\.png/,
    type: 'asset/resource'
}

Thanks @radelcom - that fixed my issue as well.
module: {       rules: [         {           test: /\.png/,           type: 'asset/resource',         }]}


Fix geojson geometry

Camden has provided geojson data in the geometry column in a CSV.
(e.g. {"type":"GeometryCollection","geometries":[{"type":"MultiPolygon","coordinates":[[[[-0.185209,51.54305],[-0.185199,51.543051],[-0.18518,51.543054],[-0.185155,51.543057],[-0.185128,51.543062],[-0.185098,51.543066],[-0.185064,51.543071]]]]})
Shapely.wkt.loads() cannot process data in this type and throws exception
This PR handles the exception by converting the code to required format i.e a valid WKT which shapely can process.
An issue with a message "invalid type geojson" is logged

Test added

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.04% :tada:

Comparison is base (821ec8e) 77.68% compared to head (bcdd2e2) 77.72%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #127      +/-   ##
==========================================
+ Coverage   77.68%   77.72%   +0.04%
==========================================
  Files          66       66
  Lines        3218     3224       +6
==========================================
+ Hits         2500     2506       +6
  Misses        718      718

Files Changed
Coverage Δ

digital_land/datatype/wkt.py
94.89% <100.00%> (+0.23%)
:arrow_up:

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


Add link to ARM version of the scaling tool

This article states it's for the classic WVD, it would be great if you could add a link to the ARM version of the same.
Thanks

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

ID: 0bd423d2-dba9-a2ef-5222-aeed7a064393
Version Independent ID: c07a6696-37fd-f026-c872-6c243dc45dcb
Content: Scale session hosts Azure Automation Windows Virtual Desktop (classic) - Azure
Content Source: articles/virtual-desktop/virtual-desktop-fall-2019/set-up-scaling-script.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

Thanks for the feedback! We are currently investigating and will update you shortly.

Here is the link for ARM: https://docs.microsoft.com/en-us/azure/virtual-desktop/set-up-scaling-script
The classic documentation is located as shown below whereas rest is ARM documentation:


KNNImage labels

I think it's "friendlier" to use strings for "labels" rather than numbers for "indices" for the training classes. This is my attempt to adjust this for the documentation.

This pull request is also includes all the changes from #16. Ooops. Closing and attempting to resubmit.


Feature/328 added profile picture in dev network and update readme

Purpose
Solution to Issue #328
Replace the nodes with Github profile pictures of the contributors in Active Developer Collaboration network and Developer Collaboration network and update Readme.
Proposed changes

Types of changes

[ ] Bugfix (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)
[x] Documentation Update (if none of the other choices apply)

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA
[x] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

Hey @smitsekhadiaa, I think your gif size is too big, which is not friendly to visitors who have a bad internet connection. Could you please compress it to a small gif?

Hey @smitsekhadiaa, I think your gif size is too big, which is not friendly to visitors who have a bad internet connection. Could you please compress it to a small gif?

yes i'll do it right now👍

And you can also zoom in the graph then record it to make it more clear in README~

yes sorry @tyn1998
i read your comment just now after making commits (of reducing the size of the gifs),
ill record it again and update it👍

Sorry, but I think the size is still too big for me.

oh okay @tyn1998
sorry,
I'll reduce it to KB's and then upload it

Try different Gif recorders. I'm using Gifox, which only supports MacOS.

Thank you @smitsekhadiaa, it looks great to me! Is this PR ready to be merged(squash merge)?

yes @tyn1998
I think it is ready to be merged👍

/approve


doc: Document how to increase operator's memory limits

This has been suggested by the operator-sdk developers. See also:
https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/subscription-config.md#resources
and:
https://sdk.operatorframework.io/docs/best-practices/managing-resources/

@sheriff-rh it would be nice to incorporate this into our documentation somehow

@mkumku for awareness, although this is just a doc change

/label qa-approved
this is only a change for upstream docs, no need to waste QE resources

/label qe-approved

lgtm! If you create a separate jira sub task and assign it to William Harris, he's up to speed on this PR and ready to go.

Unfortunately the related Jira is OCPBUGSM-39585 which can't have subtasks (it's a clone from BZ). I can file a different card for William though, I pinged him on slack.

@Vincent056 @mrogers950 @rhmdnd PTAL

LGTM!

The current version takes into account @Wiharris's suggestion. For some reason I didn't see the suggestion here in the GH UI, but I got an e-mail notification. Anyway, the suggestion was:
diff --git a/doc/usage.md b/doc/usage.md
index 37bd65a0..3162ed46 100644
--- a/doc/usage.md
+++ b/doc/usage.md
@@ -382,7 +382,7 @@ continue scheduling scans without a `PriorityClass`.
 ## Increasing operator's memory or CPU limits

 In some cases, the compliance-operator might require more memory than the default
-limits allow. If the operator had been installed via OLM (which is the case when
+limits allow. If the operator had been installed through OLM (which is the case when
 the operator is installed through the OCP Web Console), the best way is to set
 custom limits in the [Subscription object](https://github.com/operator-framework/operator-lifecycle-manager/blob/mas>

@rhmdnd can you re-add lgtm again, please?

/lgtm


docs(quickstart): add<EMAIL_ADDRESS>to package.json

Fix #571

What does this mean for plunker generation?

It does not affect plunkers. Zone is included in angular2-polyfills.js which we include, prebuilt, from the CDN.
It is needed for npm 3 though, as a peer dependency for angular and thus needs to be in the local package.json.

Closed by 9333db68e24


[FEATURE] Meta tags and React Helmet

Add proper meta tags for all pages with react helmet such as
<meta name="viewport" content="width=device-width, initial-scale=1.0">

merge #33


cilium: Replace use of integer ids with frontend address in service API

As was already marked deprecated for v1.14, this finally replaces the use of numerical service identifiers in the service API and cilium utility with the use of frontend addresses (<ip>:<port>:<protocol>(:<scope>)).
This hides the internal integer identifiers Cilium uses as the BPF map keys for service frontends which allows Cilium to reshuffle them when e.g. node's IP addresses change. It is also more ergonomic to use for standalone load-balancer purposes.
Usage example:
       root@838eb2c16285:/home/cilium# cilium service update --frontend <IP_ADDRESS>:80:TCP \
                                         --backends <IP_ADDRESS>:80 --k8s-node-port
       Creating new service "<IP_ADDRESS>:80:TCP"
       Added service with 1 backends
       root@838eb2c16285:/home/cilium# cilium service list
       Frontend          Service Type   Backend
       <IP_ADDRESS>:80:TCP   NodePort       1 => <IP_ADDRESS>:80 (active)

       root@838eb2c16285:/home/cilium# cilium service update --frontend <IP_ADDRESS>:80:TCP \
                                         --backends <IP_ADDRESS>:80,<IP_ADDRESS>:80 --k8s-node-port
       Creating new service "<IP_ADDRESS>:80:TCP"
       Added service with 2 backends

       root@838eb2c16285:/home/cilium# cilium service list
       Frontend          Service Type   Backend
       <IP_ADDRESS>:80:TCP   NodePort       1 => <IP_ADDRESS>:80 (active)
       <IP_ADDRESS>:80:TCP   NodePort       1 => <IP_ADDRESS>:80 (active)
                                        2 => <IP_ADDRESS>:80 (active)

       root@838eb2c16285:/home/cilium# cilium service delete <IP_ADDRESS>:80:TCP
       Service "<IP_ADDRESS>:80:TCP" deleted successfully

       root@838eb2c16285:/home/cilium# cilium service list
       Frontend          Service Type   Backend
       <IP_ADDRESS>:80:TCP   NodePort       1 => <IP_ADDRESS>:80 (active)

cilium: Replace the deprecated use of frontend integer identifiers with addresses in Cilium service REST API

/ci-l4lb

/ci-l4lb

/ci-l4lb

/test

This is currently blocked on the ability to restore the L4 protocol from the service map, which will be resolved by https://github.com/cilium/cilium/pull/29521.


updated goreleaser action version to v4.1.0

Codecov Report

Merging #476 (ddbe5dc) into main (73584f4) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #476   +/-   ##
=======================================
  Coverage   71.17%   71.17%
=======================================
  Files          11       11
  Lines        2054     2054
=======================================
  Hits         1462     1462
  Misses        489      489
  Partials      103      103

Continue to review full report in Codecov by Sentry.

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


Svelte Reactivity doesn't work (PeriodicTable)

https://github.com/basf/svelte-spectre/blob/a99c8555fadede467486b34591837e9e76ac7e4d/src/lib/components/PeriodicTable/PeriodicTable.svelte#L161
use  ES6 spread syntax:
selected = [...selected];

OK, I see here https://svelte.dev/tutorial/updating-arrays-and-objects:

...won't trigger reactivity on obj.foo.bar, unless you follow it up with obj = obj.


The extension no longer adds additional properties

The extension will add a constructor with properties but will no longer add additional properties.

I can confirm this issue. Doesn't work on multi-line arguments like mentioned above.

I created my own extension including this feature and many other.
If you want to give it a try: https://marketplace.visualstudio.com/items?itemName=kotfire.php-add-property

I cannot get it to work at all.  I have a public, protected and private property.  It does not work on any of them.  What is the key to using the extension?
I created a simple 'User' class.  I've tried it on the class itself, nothing.


Add patch_tool argument to npm_translate_lock

We encountered a bug with MacOS's implementation with patch, likely due to it being based on an ancient version of patch.
$ patch --version
patch 2.0-12u11-Apple

One downstream effect of patch being broken locally is that it leads to remote cache misses since our remote cache warming machines are using a non-broken implementation of patch.
This PR adds support for specifying a custom patch tool so that we can use a non-broken implementation.
Changes are visible to end-users: yes

Searched for relevant documentation and updated as needed: no
Breaking change (forces users to change their own code or config): no
Suggested release notes appear below: no

Test plan
Manual testing; please provide instructions so we can reproduce:

Add the following to MODULE.bazel:

http_file(
    name = "patch",
    executable = True,
    integrity = "sha256-0RgbIckQNYDwdh4kyrCgStgN3Dqj8XnnvIwOMJRRoks=",
    url = "https://cosmo.zip/pub/cosmos/bin/patch",
)

Pass the following argument to npm.npm_translate_lock

    patch_tool = "@patch//file:downloaded",

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.MichaelMitchell-at seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Hm, I don't understand why this isn't triggering our GitHub Actions CI. Is it rebased on a really old base commit?

Hm, I don't understand why this isn't triggering our GitHub Actions CI. Is it rebased on a really old base commit?

Oh right. I had this on top of v2.1.0 which is what we're still currently using. Let me rebase.


Home Assistant Custom Components

The custom components should not be part of the repository, they should be fetched during the ansible role execution.

Done!


cephfs: add stderr to mount function errors

Describe what this PR does
This commit appends stderr to error in both kernel and ceph-fuse mounter functions to better be able to debug
errors.
Signed-off-by: Rakshith R<EMAIL_ADDRESS>
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:

/retest ci/centos/<job-name>: retest the <job-name> after unrelated
failure (please report the failure too!)
/retest all: run this in case the CentOS CI failed to start/report any test
progress or results

/retest ci/centos/mini-e2e-helm/k8s-1.20

/retest ci/centos/mini-e2e-helm/k8s-1.20

/retest ci/centos/mini-e2e-helm/k8s-1.20

rook deploy failed.


Add context propagation on child workflow and continue as new

Pull Request Test Coverage Report for Build 217

11 of 11 (100.0%)  changed or added relevant lines in 2 files are covered.
68 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.02%) to 73.301%

Files with Coverage Reduction
New Missed Lines
%

internal/propagation.go
1
92.59%

internal/internal_task_pollers.go
4
72.43%

workflow/session.go
12
0.0%

internal/workflow.go
21
84.43%

internal/session.go
30
88.3%

Totals

Change from base Build 216:
-0.02%

Covered Lines:
8206

Relevant Lines:
11195

💛  - Coveralls

May be it is a time to add a unit test that relies on docker?

Yes, opened an issue for this #771


Bump: log4j 2.15.3 to 2.16.0

Disable JNDI by default. Require log4j2.enableJndi to be set to true to allow JNDI. Fixes LOG4J2-3208
Completely remove support for Message Lookups. Fixes LOG4J2-3211

Second Log4J Vuln found: https://www.zdnet.com/article/second-log4j-vulnerability-found-apache-log4j-2-16-0-released/

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Henri Cook seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing as already in pipeline.


WIP: Add bitbucket_server integration support

Failing - can't seem to specify url:
$ php ~/Desktop/platform.phar integration:add --url "https://sourcecode.jnj.com" --type bitbucket_server --username "SA-CPC-JAM-SVC-1" --token "******" --repository "ASX-NBFP/bodiless_starter" --build-pull-requests Y --pull-requests-clone-parent-data Y --fetch-branches Y --prune-branches Y
Warning: adding a 'bitbucket_server' integration will automatically synchronize code from the external Git repository.
This means it can overwrite all the code in your project.

Are you sure you want to continue? [y/N] y
The integration is invalid.

The following error was found:
url: Required

Fails similarly when using the prompts.

@wodenx apologies, the above should fix it


feat(migrations): allow specifying list of migrations

Ok, tests are green, let's merge this, will take a look at the typings later

I fixed it here: https://github.com/mikro-orm/mikro-orm/pull/744/commits/c380d99dd424935852c8883cda8db87ed59284c7

Hmm damn umzug and their mediocre typings...
node_modules/@mikro-orm/migrations/Migrator.d.ts:4:16 - error TS2665: Invalid module name in augmentation. Module 'umzug' resolves to an untyped module at '/usr/local/var/www/vision.gl/vision-api/node_modules/umzug/lib/index.js', which cannot be augmented.

4 declare module 'umzug' {
                 ~~~~~~~

Found 1 error.

What about that PR you made against definitely typed, is that merged already?

If you move that declare to it's own file it should work


feat(isolated-declarations): improve inferring the type of accessor

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#3751
#3750
#3749  👈
#3748
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Dunqing and the rest of your teammates on  Graphite


Udev event device matching

This just allows devices to not need to reconfigure themselves if they get a udev event not intended for them.
This should allow multiple DRM backends to share a wlr_udev.

I would prefer an approach where wlr_udev has the discretion over who gets events rather than everyone getting events and then deciding if they need them.
Something like wlr_udev_get_listener or wlr_udev_signal_add(int fd, struct wl_listener *listener)

Thanks!


Templates contain duplicate/redundant institution and scanner information

Looking at the example in pybids-reports, there is redundant information about the institution and scanner.

The data acquisition was performed in the , , .
MRI data were acquired using a UNKNOWN Tesla using a  system from ,
with serial number . The software version was .One run of   UNKNOwN SEQUENCE UNKNOwN SEQUENCE VARIANT single-echo
structural MRI data were collected (repetition time, TR= 2500.0 ms; flip angle, FA= 8°; echo time, TE= 2.9 ms;
field of view FOV= 256x256 mm; matrix size= 256x256; voxel size= 1x1x1 mm; UNKNOWN slices).
The data acquisition was performed in the , , .
MRI data were acquired using a UNKNOWN Tesla using a  system from ,
with serial number . The software version was .One run of   UNKNOwN SEQUENCE UNKNOwN SEQUENCE VARIANT single-echo
structural MRI data were collected (repetition time, TR= 2500.0 ms; flip angle, FA= 8°; echo time, TE= 2.9 ms;
field of view FOV= 256x256 mm; matrix size= 256x256; voxel size= 1x1x1 mm; UNKNOWN slices).
The data acquisition was performed in the , , .
MRI data were acquired using a UNKNOWN Tesla using a  system from ,
with serial number . The software version was .One run of  UNKNOwN SEQUENCE UNKNOwN SEQUENCE VARIANT
diffusion-weighted-imaging () data were collected (68 slices; repetition time, TR= 8400.0 ms; flip angle, FA= 90°;
echo time, TE= 90 ms; field of view FOV= 128x128 mm; matrix size= 64x64; voxel size= 2x2x2 mm; b-values of 0 and
1000 acquired; 64 diffusion directions;  ).

The relevant portion is:

The data acquisition was performed in the , , .
MRI data were acquired using a UNKNOWN Tesla using a  system from ,
with serial number .

yeah that's because the template for each MRI datatype will include the partials for institutions and scanner info.
https://github.com/bids-standard/bids-methods/blob/bdbd36a13a4364892183885dd82ab4cab046f71a/templates/anat.mustache#L1
https://github.com/bids-standard/bids-methods/blob/bdbd36a13a4364892183885dd82ab4cab046f71a/templates/dwi.mustache#L1
do you think that we should not include those in the templates and let the tools that use the templates decide if they want to include them for each MRI sequence or not?

That's what I was thinking. Optimally, pybids-reports would put them at the beginning of the session-level description, just once.

will refactor the templates.


Can sorting the diagnosis keys save space?

Your Question

Documentation File: solution_architecture.md
Line / Paragraph:

The possibility to identify temporary exposure keys belonging together (i.e. to the same user) is given, as they are posted together – resulting in them being in a sequential order in the database. To prevent this, the aggregated files will be shuffled, e.g. by using an ORDER BY RANDOM on the database side while fetching the data for the corresponding file. Alternatively, returning them in the lexicographic order of the RPIs (which are random) is a valid option as well.

Question: Did you test whether there is a payload size difference when considering ORDER BY RANDOM vs lexicographic order?

In a very simplified version of this problem I was able to save ~4% of payload size, which could add up if it holds true for the production data format.
import uuid
import gzip

DAYS = 14 # 1 key is stored per day per person
CASES = 6000 # number of people that have a positive result (sliding window of 14 days)
DIAGNOSIS_KEYS = DAYS * CASES

def main():
    keys = []
    for x in range(DIAGNOSIS_KEYS):
        keys.append(str(uuid.uuid4()))

    unsorted_keys = "\n".join(keys)
    sorted_keys = "\n".join(sorted(keys))

    with gzip.open("unsorted_keys.gz", "wt") as us:
        us.write(unsorted_keys)
    with gzip.open("sorted_keys.gz", "wt") as so:
        so.write(sorted_keys)

if __name__ == '__main__':
    main()

Thank you for your research! In practice, those diagnosis key will be part of a protocol buffer, which also contains metadata (see Figure 8), but I assume the effect remains.
A thing you might need to consider is that not all keys of a single day are put into a single package. When doing the test with a bath size of 500 cases, I was able to achieve ~2,5% savings on average. Still very good.
However, this question probably belongs to the cwa-server repository, where you can then also find the specific implementation. I'll still add a note to the architecture document.


Feature/add sg rule option

:white_check_mark: Aikido Security check OK. No new issues were introduced. 1 HIGH issue was solved. View details
Scan results for commit: 789c7b55745e65b76700233b2635dd44ce7a496f


Allow base scripts to run within a module loader

Hi,
So I can avoid multiple <script> includes, I'm adding base modules via Browserify (same principle for Webpack, Rollup etc) using this sort of syntax:
require('govuk/selection-buttons');
require('govuk/analytics/analytics');

Problem is, I've noticed a lot of the modules use this but that wrongly assumes this == window.
To resolve, this fork ensures all base modules attach to the window global for compatibility. I've also noticed use of root internally so I've further rolled this out to all modules for consistency.
These changes make no assumption that the GOVUK global variable exists. Some modules tested for this, some didn’t. Checks for this have now been tidied up.
This is a stepping-stone to a nice dependency-injected asynchonrous module future, without adding/removing properties on the window.GOVUK global.
Hope this helps.

I'm fine with this and it's something I've thought about before, good work!
The only reason I could think of to not want to do this is the fact that it slightly pollutes the commit history, but I think we'll be forced to do this at one point or another anyway.
👍  from me.

Thanks Theodor.
A further (future) approach could be to:

Convert each *.js base script to CommonJS module syntax
Add module.exports return values (or similar shim like UMD)
Keep the window.moduleName mechanism for backwards-compatibility

Perhaps I've got the ball rolling.

Hey @colinrotherham 👋
Thanks a lot for this PR 💃
I'm 👍  but have a few thought...
To reduce the amount of time you have to refer to root we could have it scoped inside the closure then reassign back to the window at the end?
(function (global) {
  var GOVUK = global.GOVUK || {};

  GOVUK.module = function () {};

  global.GOVUK = GOVUK;
})(window);

Thanks @nickcolley.
Yeah good idea, I've re-pushed my commit. I stuck with root as it was already a convention so didn't want to introduce anything new—now it’s global instead as suggested.
This way, the minifier can reduce the closure’s var GOVUK to var a or similar, saving a few more bytes in each base script. But, we could go further if needed, see below:
This suggestion
GOVUK.performance = GOVUK.performance || {};

GOVUK.performance.method1 = function() {
  /* Do something */
};

GOVUK.performance.method2 = function() {
  /* Do something else */
};

Future
function method1() {
  /* Do something */
};

function method2() {
  /* Do something else */
};

GOVUK.performance = {
  method1: method1,
  method1: method2
}

Which when minified reduces down nicely:
function b() {
  /* Do something */
};

function c() {
  /* Do something else */
};

a.performance = {
  method1: b,
  method1: c
}

We could do the same and remove Instance.prototype used throughout the other base scripts as it's not very minifier-friendly and makes quite a wordy output*.
This can be a starting point though, perhaps move the other suggestions to a couple of new issues?
*Unless you are actually making making thousands of instances (e.g. a canvas particle generator) and need the prototype tree to reduce memory usage.

👏  to moving towards more formal modules - i've been looking at something like UMD as part of de-rails-ing some of the existing JS dependencies, so this is a great step.

This can be a starting point though, perhaps move the other suggestions to a couple of new issues?

👍

A possible follow-up PR: we explicitly bind $ to global.jQuery in the core JS (e.g. stop-scrolling-at-footer.js) but not in the analytics files (e.g. download-link-tracker.js). This probably needs adding.


Separate build output from sources

This splits up the source of Acton from the built output, which goes in
the dist directory. Baking a release is then a simple operation of
taring up the dist directory.
When we invoke actonc, like for building tests, we do that in the dist
directory, thus producing output in that directory rather than mixed up
with the source code of Acton itself.
The release will be slightly slimmer, skipping certain .o files, .c
files etc that were previously included.

I'm going to merge this. Heads up @nordlander and @sydow, actonc has moved from the root dir into dist!


double clicking on an existing diagram does not open it

Reproduce:

double click on *.bpmn file

Problem

modeler opens but bpmn file not

Hint:

*.bpmn files are correctly associated with the modeler
Environment is Windows 10

Will be resolved via #189.


New updates

Hey,
Are there any plans releasing a new version of this browser?
The MacOS builds have some issues with certain websites and Google Sheets and are a few months old.

+1

Yes, a new release would be nice.

@petar-staynov @joeshae @TzunamiOSX New MacOS and SSE3 versions are out.

@Alex313031 Thank you so much!


Clustering trust_domain is broken due to api changes in tm.sys.application

@zancas
Issues:
Fixes #521
Problem:
The clustering module trust_domain.py is broken because the api changed
for tm.sys.applications to tm.sys.application. I will fix the issue and
submit the fix, and we'll have to spin another release to remedy this.
Analysis:
Modified the references to applications in trust_domain.py and reran the
clustering tests.
Tests:
Clustering tests passed locally.

Merging this change to fix clustering. Then I will bump the release and make a new release of sdk to v0.1.9