Requests from machine accounts no longer include user information (no AuthToken)

Tokens are need to track ownership of projects. This information is no longer included in requests. For machine accounts, the user object is now empty.

I am surprised that they were previously included. Machine apps inherently are not users, so I would expect the user object to be empty.
The token for the machine apps looks like this to me
{
  "iss": "https://crbm.auth0.com/",
  "sub": "5BRH4SlefREz7YRRuUeEo9tNf9HP9k2f@clients",
  "aud": "api.biosimulations.org",
  "iat":<PHONE_NUMBER>,
  "exp":<PHONE_NUMBER>,
  "azp": "5BRH4SlefREz7YRRuUeEo9tNf9HP9k2f",
  "scope": "read:Projects update:Projects create:Projects",
  "gty": "client-credentials",
  "permissions": [
    "read:Projects",
    "update:Projects",
    "create:Projects"
  ]
}

A user identity token would look similar, but potentially contain additional metadata.  The "sub" claim provides the unique identity of the user and/or machine client.

Are you specifically talking about the  `User` decorator in auth library?

I'm referring to the @Req decorator and the user attribute of Request. This previously had tokens for both users and machine accounts. Now it only has tokens for users.
import { Req } from '@nestjs/common';
import { Request } from 'express';

Can you point me to the code where this is happening?

This is marked in the comment in https://github.com/biosimulations/biosimulations/pull/3629
https://github.com/biosimulations/biosimulations/blob/d3258aaca6342f324e4e68aca59f9dcabc286bf5/apps/api/src/simulation-run/simulation-run.controller.ts#L232-L237
This is how I'm submitting requests for simulation runs with requests to publish the run upon its successful completion:
import json
import requests
import subprocess

client_id = '...'
client_secret = '...'

response2 = requests.post('https://crbm.auth0.com/oauth/token', json={
    'client_id': client_id,
    'client_secret': client_secret,
    'audience': 'api.biosimulations.org',
    "grant_type": "client_credentials",
})
response2.raise_for_status()
response_data = response2.json()
auth = response_data['token_type'] + ' ' + response_data['access_token']

run = {
    'name': 'Kockout of gene A',
    'simulator': 'tellurium',
    'simulatorVersion': '2.2.1',
    'cpus': 1,
    'memory': 8,
    'maxTime': 20,
    'envVars': [],
    'purpose': 'other',
    'email'<EMAIL_ADDRESS>    'url': 'https://github.com/biosimulators/Biosimulators_test_suite/raw/dev/examples/sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint-continuous.omex',
    'projectId': 'test',
}

response = requests.post('http://localhost:3333/runs', json=run, headers={'Authentication': auth})
response.raise_for_status()

The name of the HTTP header in the request is incorrect. It should be "authorization" not "authentication"
The URL to get the token is auth.biosimulations.org/oauth/token. While the endpoint you used is an alias, this affects the 'iss' claim on the token, which can cause auth to fail sometimes.

I had that before; that didn't work either.

I am able to use an m2m token (biomodels) to connect to the run endpoint and log the correctly received token .
There may be some issues with your config file.  The issuer, audience and domain must match to token

Yeah, I figured that out. I hadn't changed it to api.biosimulations.org.

The user attribute is fine.


fetch-yarn-deps: Fix handling of scoped packages

Description of changes
I ran into an issue with a lockfile entry of the form "@org/somepack@file:vendor/orgpacks/somepack/assets". fetch-yarn-deps would crash, because it would not detect @file:... and just blindly access pkg.resolved, which was not present.
Things done
Diagnosed and fixed the bug, added a test to avoid regressions in the future.

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@ofborg build gitmoji-cli marp

@ofborg build gitmoji-cli marp

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2716

@lilyinstarlight maybe this is worth your attention before 23.11.

@ofborg eval
@ofborg build prefetch-yarn-deps prefetch-yarn-deps.tests
Requesting a fresh eval and also fetcher test build, since this eval is a bit stale and because the commit message uses fetch-yarn-deps instead of prefetch-yarn-deps, ofborg doesn't build the tests

Ofborg failed because fetcher should probably set SSL_CERT_FILE like the others, now that #257513 was merged and Node.js no longer uses the built-in ones... (and this probably means all yarn fetchers are failing/unreproducible FODs right now...)
I'll open a separate PR to fix that since it is orthogonal to this PR

I've opened #269061 to fix the fetcher failures


Using /deep/ throws error and does not compile

body /deep/ {
	font-family: 'Lato', 'Helvetica', sans-serif;
}

throws the following error:
[gulp-sass] /Users/jeshuamaxey/app/public/css/src/base/typography:1: error: invalid top-level expression

I'm using gulp-sass v0.7.1
This is a syntax used for styling elements in the Shadow DOM. Compiling with sass (Sass 3.3.0.rc.5 (Maptastic Maple)) on the command line throws no error. This bug is similar in vein to #58.

Surely this issue should remain open and be fixed? I'd rather use this so as to remove Ruby as a development dependency but can't.


Some Problem

Hello, I made a mistake when I used the demo example data set you provided for training, could you give me some advice? Thank you very much!

Sorry for the delayed reply. It seems like the shape of input depth to the depth loss is not correct, you can check the shape of the two inputs to make sure they have the shape like [H, W].

@seulqxq , hi you solved it?   I also met this error
it comes from this two line:

obviously, mono_dep.shape is (1, 480, 640)   and   render_pkg["render_dep"].shape is (480, 640), they just miss a dimension.
I am not clear why the author has to do like that.
@wrld  hi,  about the two loss function:pearson_depth_loss and local_pearson_loss,
I modify them like below:
Am I right?

@NNsauce Your revision is right. This bug has been fixed, thank you for your comments.


fix http progress

Codecov Report

Merging #390 (8ecd132) into main (0d6cf35) will decrease coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #390      +/-   ##
==========================================
- Coverage   95.90%   95.83%   -0.07%
==========================================
  Files          57       57
  Lines        4077     4081       +4
==========================================
+ Hits         3910     3911       +1
- Misses        121      123       +2
- Partials       46       47       +1

Impacted Files
Coverage Δ

dtmutil/db.go
100.00% <ø> (ø)

client/workflow/rpc.go
100.00% <100.00%> (ø)

dtmsvr/api_http.go
92.24% <100.00%> (ø)

dtmsvr/storage/boltdb/boltdb.go
96.10% <0.00%> (-0.73%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


fix: embed version from the VERSION file

this PR prevents errors like: "open VERSION: no such file or directoryCurrent version:", which currently happen after #1.

it is the inevitable side-effect of the program looking for the VERSION file in $PWD, which it most probably does not find if you just go install it.
now no matter whether go run-ning or go install-ing the program, the version would be embedded inside the application automatically.

@wULLSnpAXbWZGYDYyhWTKKspEQoaYxXyhoisqHf , ah nice, yeah the way I solved this was a bit dirty.
Thanks so much for your contributions again, I will play around with this a bit and will create a new release probably in a few weeks.


Improve display of multi-line brand name

Before

After

To be honest, I don't like it. Looks to squashed to me. Handing this over to @filamentphp/design

To be honest, I don't like it. Looks to squashed to me. Handing this over to @filamentphp/design

Maybe it needs line-height:1.1 if it's too tight, but reason for the change was because the gap between the lines was greater than the gap above/below which looks bad.

1.2 line height looks ok to me, but still feels crowded.

I think this is really getting into the territory where this use case would be best handled by the existing blade logo overrides. Then the dev can tweak any way they need to.
Personally, not thinking this really needs to be something core needs to worry about.
@danharrin if you do want to handle it I would go with an explicit 1.2 line height.

@awcodes is leading-5 ok? (1.25)

I'd say that's fine too.


Adding New Solution: 0572-subtree-of-another-tree.js

File(s) Modified: 0572-subtree-of-another-tree.js
Language(s) Used: JavaScript
Submission URL: https://leetcode.com/problems/subtree-of-another-tree/submissions/1066408776/

Important
Please make sure the file name is lowercase and a duplicate file does not already exist before merging.

@salvillalon45 Thanks for your contribution 👍


Inconsistency in organizations filters

https://landportal.org/organizations
The filters that appears for a registered person and an anonymous user are different (and it should be the same)

also: amount of results is different (anony: 1752; authenticated: 1776 results)


Fix link in generic-host.md

Hello @AmitIG ... Use the published doc at ...
https://docs.microsoft.com/aspnet/core/fundamentals/host/generic-host
... not the GH version (i.e., not the markdown file on GH). In the published doc, the relative link for that resource ends up pointing to ...
https://docs.microsoft.com/dotnet/core/extensions/generic-host

ok thanks!


Element type is invalid: expected a string but got: object

Getting this error with:
"react": "^15.2.1",
"react-native": "^0.29.2",
"react-native-linear-gradient": "^1.5.12"

Error:
Element type is invalid: expected a string (for build in components) or a class/function (for composite components) but got: object. Check the render method.
By the looks of things this module is no longer supported which is a shame since its so great I use it in almost every project. The more they update React Native, the more modules become incompatible and most are not updated accordingly.

var LinearGradient = require('react-native-linear-gradient').default;

Yes that was it, I tried to use it with the old code just before the readme was updated here with the new usage. Thanks.


how to ignore missing response content-type header warnings

Hi,
I am testing a REST service that have responses that do not have a content-type header.
I get this warning:
com.jayway.restassured.internal.RequestSpecificationImpl$RestAssuredHttpBuilder parseResponse WARNING: Could not parse content-type: Response does not have a content-type header
I am expecting to have no content-type in the header.
Is there a way to ignore this warning?
I don't want it to pollute my results.
i have tried:
.then()             .contentType(isEmptyOrNullString())
to no avail.
Thanks

This warning is a remnant from the HTTPBuilder fork many years ago and you're right that it shouldn't be there. I've now deployed a new snapshot that should address this issue. Please try version 3.0.1-SNAPSHOT after having added the following Maven repository:
<repositories>
        <repository>
            <id>sonatype</id>
            <url>https://oss.sonatype.org/content/repositories/snapshots/</url>
            <snapshots />
        </repository>
</repositories>

thanks for that,
excuse my ignorance but should i then change my rest-assured dependancies to version 3.0.1-SNAPSHOT?
for example:
<dependency>     <groupId>com.jayway.restassured</groupId>     <artifactId>rest-assured</artifactId>     <version>3.0.1-SNAPSHOT</version> </dependency>
after of course adding the repository as you mentioned.
I get dependancy 3.0.1-SNAPSHOT not found.
thanks again.

Group id is now io.rest-assured, see release notes


Do not use styled-components inside of UserReactDOM.render

Moved checkered background stuff out of users render
Do not use styled-components inside in the users render

It seems that the light transparent bg isn't being applied quite right (see asymetry between top and bottom):

@andrejak should be fixed now. I forgot about the router logs. I moved them out of the checkered containers


problems with creating  EMBEDDEDLIST with next types: date, datetime, decimal

OrientDB Version, operating system, or hardware.

v2.2.11

Operating System

[ ] Linux
[ ] MacOSX
[x] Windows
[ ] Other Unix
[ ] Other, name?

Hi.
I have problems when I create EMBEDDEDLISTs with next types: date, datetime, decimal
Steps to reproduce the problem
orientdb {db=test}> create class eml
Class created successfully. Total classes in database now: 12.
orientdb {db=test}> create property eml.eml embeddedlist date
Property created successfully with id=1
orientdb {db=test}> create property eml.emldt embeddedlist datetime
Property created successfully with id=2.
orientdb {db=test}> create property eml.f embeddedlist float
Property created successfully with id=3.
orientdb {db=test}> create property eml.de embeddedlist Decimal
Property created successfully with id=4.
orientdb {db=test}> insert into eml content {"f":[5.1,3.1]}
Inserted record 'eml#21:0{f:[2]} v1' in 0,017000 sec(s).
orientdb {db=test}> select from eml
+----+-----+------+---------+
|#   |@RID |@CLASS|f        |
+----+-----+------+---------+
|0   |#21:0|eml   |[5.1,3.1]|
+----+-----+------+---------+
1 item(s) found. Query executed in 0.003 sec(s).
orientdb {db=test}> insert into eml content {"eml":["2016-10-09","2016-10-11"]}
Error: com.orientechnologies.orient.core.exception.ODatabaseException: Error during saving of record with rid #23:-1        DB name="test"
Error: com.orientechnologies.orient.core.exception.ODatabaseException: Error on saving record in cluster #23
DB name="test"
Error: java.lang.ClassCastException: java.lang.String cannot be cast to java.util.Date
orientdb {db=test}> insert into eml content {"emldt":["2016-10-09 15:15:00","2016-10-11 10:10:00"]}
Error: com.orientechnologies.orient.core.exception.ODatabaseException: Error during saving of record with rid #24:-1        DB name="test"
Error: com.orientechnologies.orient.core.exception.ODatabaseException: Error on saving record in cluster #24
DB name="test"
Error: java.lang.ClassCastException: java.lang.String cannot be cast to java.util.Date
orientdb {db=test}> insert into eml content {"de":[5.1,3.1]}
Error: com.orientechnologies.orient.core.exception.ODatabaseException: Error during saving of record with rid #21:-1        DB name="test"
Error: com.orientechnologies.orient.core.exception.ODatabaseException: Error on saving record in cluster #21
DB name="test"
Error: java.lang.ClassCastException: java.lang.Double cannot be cast to java.math.BigDecimal
But if I create property embedded with link on this class, I can insert new record
orientdb {db=test}> create property eml.emClass embedded eml
Property created successfully with id=6.
orientdb {db=test}> insert into eml content {"emClass":{"@type":"d","@class":"eml","de":[5.1,3.1],"emldt":["2016-10-09 15:15:00","2016-10-11 10:10:00"
], "eml":["2016-10-09","2016-10-11"] }}
Inserted record 'eml#21:1{emClass:eml{de:[2],emldt:[2],eml:[2]}} v1' in 0,021000 sec(s).
orientdb {db=test}> select from eml
+----+-----+------+---------+-----------------------------+
|#   |@RID |@CLASS|f        |emClass                      |
+----+-----+------+---------+-----------------------------+
|0   |#21:0|eml   |[5.1,3.1]|                             |
|1   |#21:1|eml   |         |eml{de:[2],emldt:[2],eml:[2]}|
+----+-----+------+---------+-----------------------------+
2 item(s) found. Query executed in 0.003 sec(s).

hi @Ivanov-Yuriy,
I just tryed the last released hotfix:2.2.12 and this seems already fixed, can you try to upgrate to te last hotfix ?
Regards

Hi @tglman
I checked latest hotfix 2.2.12. It works great. Thank you


Bugfix for duplicated requests in Mocket._requests.

Coverage decreased (-0.2%) to 99.184% when pulling a449ab1473594f7c3a498f0bc76fd93e5ff6e32f on duplicated-requests into baa383fb9a3fa7edcd6d58bd5d8d636b559a9e5b on master.


update for uyn

Hello @devih-21
Thanks a lot for checking out the project!
However, you don't really need to create a PR on this repo to get this running. You can create a link directly in your fork and host your changes in there.
I'm closing this PR, but please feel free to comment/reach out if you need any help. 🙂


reduce our dependency to the STL in public headers

Nice!  Engine pulls in ExternalContext which pulls in  so we should perhaps add an exception for that, or a FIXME.


Integrate attribute path to the flakeref.

The idea here is that appending #.... to the flake ref will parse .... into an attribute path.

Sounds good!

Could you please give some examples of how making this app attr-path aware would be used so I can add appropriate tests.
I'm going by the model used in nixos-rebuild, where they regex for a pattern that has just one # (the splitter) and no double-quotes.

Other PRs have put in groundwork for this, feature. This work is out of date.


feat: improve text color in Dark mode

🙋 Feature Request
The Color.Success value does not change when switching to Dark mode. Text is rather unreadable.
🤔 Expected Behavior
Would expect it to change to a brighter color, to make it more readable in Dark mode.
😯 Current Behavior
<FluentLabel>This is good readable text</FluentLabel>
<FluentLabel<EMAIL_ADDRESS>text is unreadable in dark mode.</FluentLabel>

In normal Light mode, everything is good:

Switching to Dark mode, the Color.Success value does not change at all, I can barely read the green text:

💁 Possible Solution
Update the --success variable to CSS color: forestgreen in Dark mode (one should not have to dwelve into DesignTokens and changing the entire color palette for this). This is definently a step up from the current behavior and matches the Color.Error tone and readability.

Although both could be improved further by using color: limegreen and color: orangered for their Dark mode values:

🔦 Context
PS! One cannot use<EMAIL_ADDRESS>with FluentLabel, because the property CustomColor does not exist. Either add it or write in the FluentLabel documentation, to use the Style property with CSS color: somecolor if you want to apply custom color.

Using the FluentDesignTheme component to switch to Dark mode.

PS! One cannot use<EMAIL_ADDRESS>with FluentLabel, because the property CustomColor does not exist. Either add it or write in the FluentLabel documentation, to use the Style property with CSS color: somecolor if you want to apply custom color.

We are looking at adding it to label for the next version. In the meantime an update to the docs should suffice. We do take PR's you know. Care to contribute?

Added CustomColor implementation. See PR mentioned above.

In case someone actually wants a solution/workaround to the problem stated.
In my MainLayout.razor I have the FluentDesignTheme element (at the top), including a FluentProfileMenu from where I can change theme and color.
I added an OnLuminanceChanged event:
<FluentDesignTheme<EMAIL_ADDRESS><EMAIL_ADDRESS>StorageName="theme" OnLuminanceChanged="this.OnLuminanceChanged" />

@code
{
    private bool isDark = false;

    public DesignThemeModes ThemeMode { get; set; }
    public OfficeColor? OfficeColor { get; set; }

    private void OnLuminanceChanged(LuminanceChangedEventArgs arg)
    {
        this.isDark = arg.IsDark;
    }
}

And then I added in the same file (right below FluentDesignTheme), to override the values:
@if (this.isDark)
{

}

Followed by the rest of the page code:

        <NavMenu />

            <FluentProfileMenu ... />

            @Body


Inventory option to close inventory

[ ] Inventory option to close inventory when the item is clicked.

This will be implemented with version 3.0.0


Poposal: Introducing a composer-plugin for OIDplus projects.

Goal(s):

Composer Plugin:
Install OIDplus Plugins by just $ composer require vendor/example-oidplus-plugin into the correct path.
Other tasks (e.g. installer-/update scripts...)...?

Example/Test
To get an basic example we take the plugin wich is very small and unfinished yet, already living in (registry.frdl.de):
plugins/frdl/adminPages/io4
To git: https://github.com/frdl/oidplus-io4-bridge-plugin
The only addition to get the thing work for this plugin is to add 2 entries to a composer.json (type and extra.installer-name):
{
    "name": "frdl/oidplus-io4-bridge-plugin",
    "type": "oiplus-plugin-admin-pages",
    "description": "Bridge from OIDplus to Webfat/IO4",
    "keywords": ["oiplus", "io4"],
    "license":  ["MIT"],
    "autoload" : {
        "classmap" : ["OIDplusPagePublicIO4.class.php"]
    },
    "extra" : {
        "installer-name" : "io4"
    }
}

We install it into the test-instance https://test-ra.weid.info/ with a composer.json file as published here: https://test-ra.weid.info/composer-json.php
Result: The git repository of the plugin lives in the root directory of the package but is installed to the correct OIDplus plugin-path by composer:  plugins/frdl/adminPages/io4
Long story short:

https://getcomposer.org/doc/articles/custom-installers.md
https://github.com/oomphinc/composer-installers-extender

Ggf. können noch einige der ganzen path-definitionen aus dem root composer.json entfernt werden, da sie vom composer-plugin ge-merged werden...
Muss getestet werden (entsprechen z.B. der autoloader-settings und der initial packages/classes...

Ich habe mal roave/security-advisories hinzugefügt und es hat eine Warnung für firebase/php-jwt ausgegeben, deshlab habe ich in der Testinstanz firebase/php-jwt >=6 aktualisiert!

@danielmarschall  Du könntest probieren, ob Du das ganze schlanker hinbekommst, z.B, ausgehend von https://github.com/oomphinc/composer-installers-extender
Das sind im wesentlichen die OIDplus Pfade:
 "installer-paths": {
			"vendor/{$vendor}/{$name}/":             [
				"type:library",
				"type:project"
			],

			"plugins/{$vendor}/publicPages/{$name}/":              [
				"type:oiplus-plugin-public-pages"
			],
			"plugins/{$vendor}/raPages/{$name}/": [
				"type:oiplus-plugin-ra-pages"
			],
			"plugins/{$vendor}/adminPages/{$name}/":             [
				"type:oiplus-plugin-admin-pages"
			],
			"plugins/{$vendor}/auth/{$name}/": [
				"type:oiplus-plugin-auth"
			],
			"plugins/{$vendor}/database/{$name}/": [
				"type:oiplus-plugin-database"
			],
			"plugins/{$vendor}/sqlSlang/{$name}/": [
				"type:oiplus-plugin-sql-slang"
			],
			"plugins/{$vendor}/logger/{$name}/": [
				"type:oiplus-plugin-logger"
			],
			"plugins/{$vendor}/objectTypes/{$name}/": [
				"type:oiplus-plugin-object-types"
			],
			"plugins/{$vendor}/language/{$name}/": [
				"type:oiplus-plugin-language"
			],
			"plugins/{$vendor}/design/{$name}/": [
				"type:oiplus-plugin-design"
			],
			"plugins/{$vendor}/captcha/{$name}/": [
				"type:oiplus-plugin-captcha"
			]
		}

No problem.
As the suggested solution works by only adding one composer.json file, someone could

use this optionaly as there is nothing to change on the existing plugins
this makes only sense in development context

One use case would be that plugins can require plugins and solve the dublicate class files problem.
However, I close this issue.

composer läuft z.b. auch als .PHAR(?). Setting 2. habe ich nur einmal kurz getestet, da habe ich keine Erfahrung.

WebGUI 👍  should be there for endusers (can be wrapped around commands/api/cli...)

If you think that composer as phar can be called on a shared web hosting, maybe your composer plugin can be wrapped with a WebGUI. So why do you close the ticket?

sorry, I reopen the issue.
Composer can be used definitly on shared hosting, yes (if .PHAR or exec or something is available.
I tested it successfully before, by file_get_contents the phar "manually" and execute the composer scripts.
Also some classes of composer can be used independently.
But also yes, it is important to seperate the install dev from production/enduser.
Finally, as at this point there are only two significant entries in the composer.json a WebGUI can parse it and copy the plugins into the correct dirs manually without composer.
...die Möglichkeiten sind vielfältig... ich plädiere in der Regel dafür die Installers/Setups vom App-System zu separieren.


[SPARK-34878][SQL][TESTS] Check actual sizes of year-month and day-time intervals

What changes were proposed in this pull request?
As we have suport the year-month and day-time intervals.  Add the test actual size of year-month and day-time intervals type
Why are the changes needed?
Just add test
Does this PR introduce any user-facing change?
No
How was this patch tested?
./dev/scalastyle
run test for "ColumnTypeSuite"

Can one of the admins verify this patch?

@Peng-Lei The added objects can be used in SPARK-35243

Thank you very much，It seems that you have found a task for me. Thanks again

+1, LGTM. Merging to master.
Thank you, @Peng-Lei .


Add TechSmith community triplets

Add windows/mac static-release triplets.
Remove .gitignore hack for our triplets and move them into a TechSmith subfolder inside of triplets/community

x64-windows-static-release is already there. We didn't add it.
https://github.com/TechSmith/vcpkg/blob/addTechSmithCommunityTriplets/triplets/community/x64-windows-static-release.cmake


add default aes to keystore..

Description
Describe the changes or additions included in this PR.
Test plan
How did you test the new or updated feature?

Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

[ ] Protocol:
[ ] Nodes (Validators and Full nodes):
[ ] Indexer:
[ ] JSON-RPC:
[ ] GraphQL:
[ ] CLI:
[ ] Rust SDK:

there are some cases, we don't want to display the base64 directly in the files, [not security enough], by add the default aes-encode, developers can compile the bin files with their own encrypto password, so instead of save base64 content , I think aes-encode content with user-custom aes-128 result is more reasonble. in fact, similar cases exist in the config files, network.yaml, fullnode.yaml, all the key-pair currently only save as base-64, but key-pairs content is less used in normal developer, but cli-key tool is widly use for dapps develoers in their server for deploy dapps.

there are some cases, we don't want to display the base64 directly in the files, [not security enough], by add the default aes-encode, developers can compile the bin files with their own encrypto password, so instead of save base64 content , I think aes-encode content with user-custom aes-128 result is more reasonble. in fact, similar cases exist in the config files, network.yaml, fullnode.yaml, all the key-pair currently only save as base-64, but key-pairs content is less used in normal developer, but cli-key tool is widly use for dapps develoers in their server for deploy dapps.

i generally like the direction but there are few details that worth going through standardization. Do you want to submit to SIP as well? It will be a greats place to elaborate the motivation, test plans and some choices around prefix etc for the broader community for feedback.
thanks for the contribution!

in fact I have code already change the config and yaml files, but with more changes to nodeConfig Struct, I was thinking make 2 merge to fix these. Your comment of making a SIP is quite good, So I try one , https://github.com/sui-foundation/sips/pull/21,

Yes, there was a relate merge in sui project, https://github.com/MystenLabs/sui/pull/17384, the develop suggest me to submit a sip


Second order derivaties for Pooling operations

Fixes #6143
Fixes #6294
This is still not a complete. I wanted to know whether this is the correct way?
I ran the following code and it worked without any error.
If it is correct, then I will add the same for avg_pool too.
In [1]: import tensorflow as tf
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcublas.so.7.5 locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcudnn.so.4 locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcufft.so.7.5 locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcuda.so.1 locally
I tensorflow/stream_executor/dso_loader.cc:128] successfully opened CUDA library libcurand.so.7.5 locally

In [2]: x = tf.placeholder(tf.float32, shape=[1, 4, 4, 1])

In [3]: y = tf.nn.max_pool(x, ksize=[1, 2, 2, 1], strides=[1, 2, 2, 1], padding='VALID')

In [4]: dy = tf.gradients(y, x)

In [5]: ddy = tf.gradients(dy, x)

Can one of the admins verify this patch?

Jenkins, test this please!

I have added tests and AvgPoolGrad op. MaxPoolGrad tests are passing but AvgPoolGrad tests are failing. I have added a comment above which might explain why it is failing. @vrv what do you think?

The operation is not implemented correctly. If tests are passing, it is only because linear pooling operations are involved which results in all zeros and ones. We need to write a custom gpu kernel for max pool grad grad. Similarly, custom cpu c++ function needs to be implemented. See theano gpu implementation for reference - https://github.com/Theano/Theano/pull/5159. For average pool grad grad, no custom kernel is needed and we can just reuse average pooling.
As I am familiar with theano, I can pick up this pull request fairly easily and add support for max pool grad grad to tensorflow if @AnishShah doesn't mind.

@aam-at Okay. Sure. Please tag me in the PR too if it's okay. I would like to learn how you did it.
Thanks!

@aam-at Also, I would like to know what is wrong?
For the max pool operation, the gradient is passed to the one who has the maximum value inside the kernel window. So, the second order derivative should be zero. This is kind of like ReLUs, isn't it? Can you please explain? It would help me understand better. :)

Can one of the admins verify this patch?

Gradient of max pooling does not always output ones. It will pass top gradients gz which correspond to the location of maximum values in the input x. If you have only linear operations, then gz is ones and gx is also ones then. But this is not true in general.
Gradient of the gradient needs to pass gradient of the top input gradient ggx which correspond to the locations of maximum values in the input x.
For diagram of gradient of max pooling operation, you can look up Zeiler's paper on deconvolutional networks (they have diagram for unpooling which is just basically backward pass of max pooling). Gradient of the gradient is a bit more confusing to show using diagram.

@aam-at Thanks for the explanation. Looking forward to your PR. Please mark me too. :)


rolling and main branches are not in sync

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
Same as https://github.com/autowarefoundation/autoware_adapi_msgs/issues/56
Expected behavior
Same as https://github.com/autowarefoundation/autoware_adapi_msgs/issues/56
Actual behavior
Same as https://github.com/autowarefoundation/autoware_adapi_msgs/issues/56
Steps to reproduce
Same as https://github.com/autowarefoundation/autoware_adapi_msgs/issues/56
Versions
No response
Possible causes
No response
Additional context
No response

@youtalk @isamu-takagi I just tried and I can't force-push to main for this repository, I don't even have write access

Fixed, thanks @xmfcx and @mitsudome-r


[release-0.19] Change log for release-0.19.11

Cherry-picked from https://github.com/aws/eks-anywhere/pull/8841

/approve
/lgtm


Update Histogram docs in MetricsRegistry

Those 2 methods are passing a true boolean for the biased parameter. Changed the docs to reflect how the Histogram is constructed.
I don't know if you prefer the default to be a non-biased Histogram, changing the passed parameter instead of the docs.

Awesome, thanks!


changing level physics bug

on level transition had a crash with the following message:
Error
states/gameState.lua:114: A body has escaped Memoizer!
Traceback
[C]: in function 'destroy'
states/gameState.lua:114: in function 'loadMap'
states/gameState.lua:259: in function 'checkNewLevelPoints'
states/gameState.lua:246: in function 'update'
[C]: in function 'xpcall'

I put in a collectgarbage() imediately after destroying the physics world and ran through the game several times and didn't run into this again. The error occurs on trying to use a physics body or fixture that doesn't exist anymore so looks like this is picking them all up now. I may have just been getting lucky though, will need to keep an eye out.


[bug] Unhandled Promise Rejection for $TEMP: path not allowed on the configured scope

Describe the bug
The problem occurs when opening a file from the BaseDirectory.Temp . Other directories work.
I tried different configurations, the only one that works is a wildcard.
   "fs": {
        "readFile": true,
        "scope": [
          "$TEMP/test.txt",
          "$TEMP/*/**",
          "$TEMP/**",
          "$TEMP/*",
          "$TEMP/",
          "$TEMP",
          "**", // <- wildcard is the only one that works
      }

 readBinaryFile(fileNameInputEl.value, { dir: BaseDirectory.Temp }).then(
      (data) => {
        console.log(data)
      }
    )

Reproduction
I created a repository for reproduction: https://github.com/gormlabenz/tauri-temp-bug

Add "$TEMP/**" to scope

 "fs": {
        "readFile": true,
        "scope": [
          "$TEMP/**",
        ]
      }

Open file from 'BaseDirectory.Temp'

    readBinaryFile(filename, { dir: BaseDirectory.Temp }).then(
      (data) => {
        console.log(data)
      }
    )

Expected behavior
Shouldn't fail when opening file from BaseDirectory.Temp
Platform and versions
Environment
› OS: Mac OS 13.1.0 X64
› Node.js: 16.15.0
› npm: 9.3.1
› pnpm: 7.27.0
› yarn: 1.22.19
› rustup: 1.25.1
› rustc: 1.63.0
› cargo: 1.63.0
› Rust toolchain: stable-x86_64-apple-darwin
Packages
› @tauri-apps/cli [NPM]: 1.2.3
Stack trace
[Error] Unhandled Promise Rejection: path not allowed on the configured scope: /var/folders/8s/xvw_7jh940d8n4cmn3wj5n8w0000gn/T/test.txt
	promiseEmptyOnRejected
	promiseReactionJob

Additional context
No response

I have the same problem
scope:
{
    "$TEMP/AMCL",
    "$TEMP/AMCL/**"
}

code:
const tempDir = await resolve(await tempdir(), 'AMCL')
if (!(await exists(tempDir))) await createDir(tempDir)

error:
Uncaught (in promise) path not allowed on the configured scope: C:\Users\zhenxin\AppData\Local\Temp\AMCL

tauri info:
Environment
  › OS: Windows 10.0.22621 X64
  › Webview2: 110.0.1587.56
  › MSVC:
      - Visual Studio ���ɹ��� 2022
  › Node.js: 18.13.0
  › npm: Not installed!
  › pnpm: 7.27.1
  › yarn: Not installed!
  › rustup: 1.25.2
  › rustc: 1.67.1
  › cargo: 1.67.1
  › Rust toolchain: stable-x86_64-pc-windows-msvc

Packages
  › @tauri-apps/cli [NPM]: 1.2.3
  › @tauri-apps/api [NPM]: tauri-apps
  › tauri [RUST]: 1.2.4,
  › tauri-build [RUST]: 1.2.1,
  › tao [RUST]: 0.15.8,
  › wry [RUST]: 0.23.4,

App
  › framework: Vue.js
  › bundler: Vite

App directory structure
  ├─ .git
  ├─ .github
  ├─ .vscode
  ├─ dist
  ├─ node_modules
  ├─ public
  ├─ scripts
  ├─ src
  └─ src-tauri

I'm sure the problem happens because on MacO std::env::temp_dir() returns path starting with /var, but /var is a symbolic link to /private/var. I took a look at the source code and I don't see any canonicalization of paths parsed from config. But we canonicalize paths received from API. The tokenizer then compares /var/... to /private/var/.., which of course is not a match.
Can someone confirm whether the /var is always a symlink? If so, should it canonicalize every path parsed from the configuration, or just TEMP? I was facing the same issue so I can try to fix this bug, if someone confirms the /var symlink.

I have the same issue on windows.
None of the following work only wildcard does.
`
"fs": {
"readFile": true,
"writeFile": true,
"createDir": true,
"exists": true,
"scope": [
"$TEMP//*",
"$TEMP/"
]
}
// example code that throws error
import { tempdir } from '@tauri-apps/api/os';
import { getName } from '@tauri-apps/api/app';
import { createDir } from "@tauri-apps/api/fs";
const tmpDir:string = await tempdir();
const appName:string = await getName();
const tmpDirPath:string = await join(tmpDir, appName);
await createDir(tmpDirPath);
 path not allowed on the configured scope: C:\Users\my_user\AppData\Local\Temp\appName

`
Is there atleast a workournd for this other than using wildcard and exposing the whole filesystem?

I am using macOS as well, and the same issue is troubling me.

Also ran into this trying to write a temp file:
await fs.writeBinaryFile(name, contents, {
  dir: fs.BaseDirectory.Temp,
});

Gives
[2024-04-18][06:16:23][ERROR][log@http://localhost:1420/node_modules/.cache/.vite/deps/tauri-plugin-log.js:18:20] [ChatInput] Failed to write file path not allowed on the configured scope: /var/folders/y1/960q4z0x7h992hvtm995pk9w0000gn/T/Screenshot 2024-04-12 at 20.17.34.png

Any idea if this can be patched?

Confirmed on mac OS 14.3.1, /var is linked to private/var.

Take a look at the source code
https://github.com/tauri-apps/tauri/blob/caddd5bdd877e587e6d1a2787cba96d435549ad3/core/tauri/src/scope/fs.rs#L68-L85
When adding a permission pattern, it will try to canonicalize the path only on Windows.
https://github.com/tauri-apps/tauri/blob/caddd5bdd877e587e6d1a2787cba96d435549ad3/core/tauri/src/scope/fs.rs#L229-L236
When checking permissions, the first time called writeFile will work, because the file does not exist, it will check the path directly, but when calling writeFile  again with the same path, because the file exists, it will canonicalize the path then checking the canonicalized path, which doesn't work.


Missing config.sh in /tmp in jenkins 2.3+ version

+ cat
+ chmod +x /tmp/init.sh
+ exec /tmp/init.sh
+ export CONFIG=/tmp/config.sh
+ [ ! -f /tmp/config.sh ]
+ echo No config, sleeping for 1 second
No config, sleeping for 1 second
+ sleep 1
+ [ ! -f /tmp/config.sh ]
+ echo No config, sleeping for 1 second
No config, sleeping for 1 second
+ sleep 1
+ [ ! -f /tmp/config.sh ]
+ echo No config, sleeping for 1 second
No config, sleeping for 1 second
+ sleep 1
+ [ ! -f /tmp/config.sh ]
+ echo No config, sleeping for 1 second
No config, sleeping for 1 second
+ sleep 1
+ [ ! -f /tmp/config.sh ]
+ echo No config, sleeping for 1 second
No config, sleeping for 1 second
+ sleep 1
+ [ ! -f /tmp/config.sh ]
+ echo No config, sleeping for 1 second
No config, sleeping for 1 second
+ sleep 1
+ [ ! -f /tmp/config.sh ]
+ echo No config, sleeping for 1 second
No config, sleeping for 1 second
+ sleep 1
+ [ ! -f /tmp/config.sh ]
+ echo No config, sleeping for 1 second
No config, sleeping for 1 second
+ sleep 1
+ [ ! -f /tmp/config.sh ]
+ echo No config, sleeping for 1 second
No config, sleeping for 1 second
+ sleep 1
+ [ ! -f /tmp/config.sh ]
+ echo No config, sleeping for 1 second
No config, sleeping for 1 second
+ sleep 1
+ [ ! -f /tmp/config.sh ]
+ echo No config, sleeping for 1 second
No config, sleeping for 1 second
+ sleep 1
+ [ ! -f /tmp/config.sh ]
+ echo No config, sleeping for 1 second
No config, sleeping for 1 second
+ sleep 1
+ [ ! -f /tmp/config.sh ]
+ echo No config, sleeping for 1 second
No config, sleeping for 1 second

Container is not able to connect back to jenkins. By looking into it, I found that the config.sh is missing.
Is it something that I have to configure from my side. I have checked all the settings and configuration .
YAD plugin version - 0.2.0
Jenkins version - 2.308
PS: The same setup is working in another jenkins with version 2.249.2

no, file will be placed into container automatically and contain settings required for connection. If it's missing then something failed in start up process

How can I check where it went wrong, because the same setup is working on another jenkins master

everything should be in jenkins log


Running toolbox outside of vagrant environment

Done! Now is possible to install and use the toolbox in an osx and linux environments.


Enhancement Request - Display GPT-based Job Descriptions as Pipeline RecommendationsEnhancement Request - Display GPT-based Job Descriptions as Pipeline Recommendations

As a user of the job search feature on GitHub, I would like to suggest an enhancement to the user interface (UI) that would display GPT-based job descriptions as recommendations for running the pipeline of job searches.
Currently, the job search feature on GitHub provides users with a list of job postings based on their search criteria. While this is helpful, it would be even more beneficial if the UI could leverage GPT (Generative Pre-trained Transformer) technology to generate job descriptions that align with the user's search preferences.
By incorporating GPT-based job descriptions into the UI, users would have access to more comprehensive and tailored recommendations for their job search pipeline. This would enable them to make more informed decisions about which jobs to pursue and increase their chances of finding the right opportunities.
The proposed enhancement would involve integrating GPT models into the existing job search algorithm. These models would analyze the user's resume to generate job descriptions that closely match their requirements. The UI would then display these GPT-based job descriptions alongside the regular job postings, providing users with a broader range of options to consider.
Ideally, it would be two categories of job descriptions:

Lateral moves
Moving up in title

MUST RETURN JSON OBJECT

I am interested in doing this, if you could guide me
what I have understood is
we need to add a feature that enables users to opt for GPT powered job description matching with their profiles
So we might need to implement few UI Changes, ask users for their openai api key maybe, but not by default, and integrate this optional function in pipeline.
Correct?

@AtharvaJadhav7 - my recommendation is to do this in two fold.

We would need to use the Open AI GPT embeddings module to take the resume.txt and convert it to a string of numbers.  Here is a link for how to create GPT embeddings from text.

We would need to create embeddings for all of the job descriptions in the database of jobs, making sure not to create embeddings if they have been created before (to save money on GPT API calls).

Once we have the embeddings from resume.txt (from step 1) and embeddings for all job descriptions in the sqlite database, we would need to refactor the text_similarity.py which right now uses word2vec, we would remove the word2vec and do the cosine similarity between the resume embeddings and each job description embeddings.

NOTE: because we are doing several things with text we also need to create a class called TextAnalysis.py that takes in the text and does what we do in the extract_salary.py and creates an embedding from the text as well. We can expand on this new TextAnalysis.py class latter
You can take it one step at a time, and for example create a function that takes in text and outputs GPT embeddings and have that be the first method in the TextAnalysis.py class, then do steps 1-3 above, then finally add the code from extract_salary.py into the TextAnalysis.py class as well.
I hope this is clear

Also for the OPEN_API_KEY, we can just add it to the .env-template as a placeholder, and update the installation docs to include a second key that needs to be added, right now we have the RAPID_API_KEY in the docs, we would just need to add to the docs the new OPEN_API_KEY in there so people know

Also I feel like #69 is closely related to this and includes the updating of the UI to accept resumes

we can also use huggingface transformer library to use gpt model, rather that using api?


Probability calculator

Given a problem it will calculate the probability and will also provide the stepwise solution to the user.
Please assign this to me

Feel free to ask your doubts, if any
Deadline 22 March,2021 (11:59 PM IST)

Okay sir

Sir, I have designed a probability calculator but it can calculate the probability of drawing a card given the number of copies in your deck, the number of cards in your deck, and the number of cards you are drawing.

Can you show steps for the same?

No sir.

@sairish2001 @arpit456jain kindly assign me this issue under lgm-soc.

@Khushi-agarwal go ahead
Dead line 27 june


Crash after Unity logo in Oculus Quest

Short description
I want to run the OverlayBrowserDemo on Oculus Quest 2.
But the app crashes after the Unity logo is displayed.
Steps to reproduce

Clone this repository and open the UnityProject in Unity
Set Build Settings > Platform to Android
Set Build Settings > Texture Compression to ASTC
Click Switch Platform
Uncheck Player Settings > Player > Other Settings > Auto Graphics API
Check Project Settings > XR Plug-in Management > Plug-in Providers > Oculus
Add Scenes/OverlayBrowserDemo to Build Settings > Scenes In Build
Install Android Logcat in Package Manager (To see Quest's log)
Build And Run

Expected result
The app launches in the Quest and I'll be able to see the browser.
Actual result
The app crashes and exits after the Unity logo is displayed.
Logcat shows the error log: log.txt
Additional context

I updated the Oculus Integration but it did not help
Disabling OverlayBrowserView will launch the app without crashing

Platform information
OS: Windows 10
HMD: Oculus Quest 2
Unity: 2019.4.14f1

I have solved this issue.
I repraced UnityProject/Assets/Plugin/Android/geckoview-armeabi-v7a-70.0.20191022130254.aar with geckoview-armeabi-v7a-80.0.20200818235255.aar(download here) and it works fine!

Ohhh shoot that was my fault, I updated the plugin to work with the geckoview v80 library but didn't replace the geckoview library in the plugin directory! Thanks for figuring that out, if you want to submit a PR to update that you're welcome to or I'll get around to it in the next couple days.

Weird how it worked on the Oculus Go after I updated the plugin and tested it...

Thank you for the awesome project!


PUB-1612

JIRA link
https://tools.hmcts.net/jira/browse/PUB-1612
Change description
Re-added blob explorer from hackathon. Also trying to see if pipeline can be overridden at all.
Added timeline dependency to give us a nicer look at e2e outputs.
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Just spotted we also need route tests adding and functional tests.
Done now :)


Missing Local Storage Operator

I think that the Local Storage Operator is missing. I am unable to find it on the MarketPlace as per the OKD documentation here: https://docs.okd.io/latest/storage/persistent_storage/persistent-storage-local.html
Thank you so much for your help. :)

This would be awesome. Meanwhile I'm linking this one for people who just want to testdrive it, without using it in production systems: https://github.com/openshift/local-storage-operator/blob/master/docs/deploy-with-olm.md#create-and-subscribe-to-the-local-storage-catalog

This would be awesome. Meanwhile I'm linking this one for people who just want to testdrive it, without using it in production systems: https://github.com/openshift/local-storage-operator/blob/master/docs/deploy-with-olm.md#create-and-subscribe-to-the-local-storage-catalog


Clean up image src files in tts

Synchronize the card image files with those used in the shiny app. Easiest to do this is overwriting the filenames and identifiers in the save file.
Once this is done, card data such as card name, vp or cost can readily be tagged onto individual cards by editing the save file.

Image files harmonized for villains, heroes, henchmen and masterminds.
Not done:
Transformed heroes
Out of scope as not present in app:
Horrors
Ambitions
Twists
Strikes
Wounds
Bystanders


[Teams] Copy/Pasted email addresses from Outlook app sent from teams are not accessible from bot

Issue
When a user copy an email from outlook desktop application and paste it to MS Teams, the email address is not accessible from bot.
Expected behavior
Bot should be able to access the email address pasted on MS Teams
How to reproduce

Copy an email from Outlook desktop application:

Paste email onto a private message to the bot on MS Teams:

Check the message received in the bot does not contain the email address

{
  "text": "GAVALDA Yasmina ",
  "textFormat": "plain",
  "type": "message",
  "timestamp": "2020-02-06T12:31:35.5977294Z",
  "localTimestamp": "2020-02-06T13:31:35.5977294+01:00",
  "entities": [{ "locale": "en-GB", "country": "GB", "platform": "Mac", "type": "clientInfo" }],
  "textLocale": "en-GB",
  "sourceEvent": { "tenant": { "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" } },
  "attachments": [],
  "address": {
    "id": "1580992295582",
    "channelId": "msteams",
    "user": {
      "id": "29:1LCMqBdwgwSnBTHnBQuJ2VnM4vE8BJ1dSU-H1-2WS3K1S_rof3cBIbDtuU7C-04y3Asmm22Cv27ugTaw_qFlN9g",
      "name": "GAVALDA Yasmina",
      "aadObjectId": "f67fda16-4520-4766-af42-502a9cd18b21"
    },
    "conversation": {
      "conversationType": "personal",
      "tenantId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
      "id": "a:1K2e1KIquIQgQmbcMVrzgpR3Gc7GL-QPtmudiqFxAn0HqAYvkLa6W3RxbJqpEej4J76gPsZbxmbdrEQFXT575c4-J_HsVSlRv6lC5FPnrj4rc-XUJDc4-7kLfPTYApm-h"
    },
    "bot": { "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "name": "XXXXXXXXXX" },
    "serviceUrl": "https://smba.trafficmanager.net/emea/"
  },
  "source": "msteams",
  "agent": "botbuilder",
  "user": {
    "id": "29:1LCMqBdwgwSnBTHnBQuJ2VnM4vE8BJ1dSU-H1-2WS3K1S_rof3cBIbDtuU7C-04y3Asmm22Cv27ugTaw_qFlN9g",
    "name": "GAVALDA Yasmina",
    "aadObjectId": "f67fda16-4520-4766-af42-502a9cd18b21"
  }
}

Note that if the user writes a text with the email copy/pasted from outlook, bot receives the text but not the email address:

{
  "text": "Hello! My email is GAVALDA Yasmina ",
  "textFormat": "plain",
  "type": "message",
  "timestamp": "2020-02-06T14:04:25.6353549Z",
  "localTimestamp": "2020-02-06T15:04:25.6353549+01:00",
  "entities": [{ "locale": "en-GB", "country": "GB", "platform": "Mac", "type": "clientInfo" }],
  "textLocale": "en-GB",
  "sourceEvent": { "tenant": { "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" } },
  "attachments": [],
  "address": {
    "id": "1580997865585",
    "channelId": "msteams",
    "user": {
      "id": "29:1LCMqBdwgwSnBTHnBQuJ2VnM4vE8BJ1dSU-H1-2WS3K1S_rof3cBIbDtuU7C-04y3Asmm22Cv27ugTaw_qFlN9g",
      "name": "GAVALDA Yasmina",
      "aadObjectId": "f67fda16-4520-4766-af42-502a9cd18b21"
    },
    "conversation": {
      "conversationType": "personal",
      "tenantId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
      "id": "a:1K2e1KIquIQgQmbcMVrzgpR3Gc7GL-QPtmudiqFxAn0HqAYvkLa6W3RxbJqpEej4J76gPsZbxmbdrEQFXT575c4-J_HsVSlRv6lC5FPnrj4rc-XUJDc4-7kLfPTYApm-h"
    },
    "bot": { "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "name": "XXXXXXXXXX" },
    "serviceUrl": "https://smba.trafficmanager.net/emea/"
  },
  "source": "msteams",
  "agent": "botbuilder",
  "user": {
    "id": "29:1LCMqBdwgwSnBTHnBQuJ2VnM4vE8BJ1dSU-H1-2WS3K1S_rof3cBIbDtuU7C-04y3Asmm22Cv27ugTaw_qFlN9g",
    "name": "GAVALDA Yasmina",
    "aadObjectId": "f67fda16-4520-4766-af42-502a9cd18b21"
  }
}

Hi @yasminagavalda - this probably has to do with the angle brackets being interpreted as markup. Have you tried pasting an email address without the angle brackets?
Also, the format of your activities makes it look like you're using the v3 Node SDK. While the activity schema has remained unchanged, it's possible that the transformations applied by that SDK have removed some information from the activity. Would you consider migrating to v4?

Hi @v-kydela, I have tried to write the same text with angle brackets and it arrives to the bot. And I have copy/pasted the same text from another app or text editor and it arrives to the bot too. The issue only exists when I copy/paste from the Outlook app.
We started this bot with v3 and it is almost finished, so we can’t migrate to v4 now. I will consider the v4 for the next bots.

@yasminagavalda - That's interesting. The problem I'm able to reproduce on Teams for Windows is that nothing contained in angle brackets gets sent to the bot, so there's nothing the bot can do to recover the information regardless of what SDK you're using.
@billbliss
@clearab
Can you have a look at this? It appears to be a Teams bug.

I think this is a regression because it used to work, and it should work. We've filed a bug. I think Kyle is right, it doesn't matter what version of the SDK you use (I wouldn't think it would). It also happens on the iOS client so this is likely a service regression.

I was able to repro from the Teams client with any text enclosed in angle brackets, not just e-mail addresses. Mine is dump C# echo bot v4.x.

It does not happen from the WebChat test.
It does not happen in a human-to-human Teams conversation.
So I guess it is in the Teams channel, indeed.

Hi @billbliss,
Is there any news about this bug?

@Wajeed-msft can you take a look while Bill is oof?

@yasminagavalda  - We found this as a regression Bug, we have opened a bug for this, will get back to you once fix will be rolled out

Closed because bug has been filed and been tracked elsewhere. If there are any additional issues, please re-open or file a new issue. Thanks!

Updates: This has been fixed and deployed. Please let us know if you are still facing this issue.

Updates: This has been fixed and deployed. Please let us know if you are still facing this issue.

@Wajeed : The issue is still there only difference is when I copy and paste any piece from one of the replies of Teams Bot itself then it doesnt work.
Example: I have a welcome message in my bot, where I show an example how to proceed. If I copy the text from the example and paste in my chat, my bot doesnt take that as input and restarts the conversation from again rendering the Welcome message.
If I type that example then it works. I also tried copying and pasting from outside application like notepad and  it works. It doesnt work only if I copy the text from Teams Bot reply. Please check


change_date column is dropped since powerdns 4.2.0

Hello together,
with the upgrade from powerdns 4.1 to 4.2, there are two schema-updates for the mysql-database (https://github.com/PowerDNS/pdns/blob/master/modules/gmysqlbackend/4.1.0_to_4.2.0_schema.mysql.sql).
The drop of the column "change_date" leads to several PHP-Errors in the records.php-File:
AH01071: Got error 'PHP message: Slim Application Error:\nType: PDOException\nCode: 42S22\nMessage: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'change_date' in 'field list'\nFile: /var/www/pdnsmanager2/backend/operations/Records.php\nLine: 180\nTrace: #0 /var/www/pdnsmanager2/backend/operations/Records.php(180):  [...]
I bypassed this errors by manually inserting this column again, but I think, pdnsmanager should be edited to get along with the acutal schema of powerdns 👍
thanks and best regards,
Markus

I had the same issue. Ended up adding change_data column back just like you did, but I agree that this should be updated in pdnsmanager.


Redirect to requestor

This function abstracts away the query parameter returned to the requestor via the redirect. It is very similar to redirectToAccessManagementUi, which is already part of the API, except it's meant for the access management app to call in order to redirect users to the client requesting access with the grant VC IRI.
Note that returning the VC IRI, and not the VC value, is not consistent with the current behaviour, but it is the behaviour we actually desire. The redirection from the requestor to the access management will be fixed in a different PR, and functions abstracting the interaction with query params will be added too.
Open question for reviewers: should redirecting always return a never resolving promise, or should it do so only in the browser ? In this case, it would make sense that the redirect callback provided in Node would be async, and redirecting would return the result of that callback.
Checklist

[X] All acceptance criteria are met.
[x] Relevant documentation, if any, has been written/updated.
[x] The changelog has been updated, if applicable.
[x] New functions/types have been exported in index.ts, if applicable.
[X] Commits in this PR are minimal and have descriptive commit messages.

Open question for reviewers: should redirecting always return a never resolving promise, or should it do so only in the browser?

I would generally avoid never resolving promises. But I don't know enough about how the reasons for it to happen in that way in the browser to express a very educated opinion.

In this case, it makes sure people don't rely on something to happen based on a race condition. Setting window.location doesn't redirect instantly, some client-side code may still be executed before redirection. Which means if the promise resolves, it would be possible to write
await redirectToAccessManagementUi(...)
doSomething();

and face bugs where doSomething is sometimes called, sometimes not. redirectToAccessManagementUi never resolving enforces that no code is executed beyond this point, as intended by the redirection.

I'm actually wondering whether those functions actually make sense in the node server context?

I think they do: essentially, both these functions are just an abstraction layer on top of a redirection with a couple of query parameters. If it is relevant to provide this abstraction in the browser, I would argue it should also be provided in Node. The access requestor/access management app may be client-side or server-side apps, the only difference from our point of view being the redirection mechanism, which is native to the browser and framework-specific in Node.


BODY has unexpected field(s)

Hello,
Message template 'components' param contains unexpected field(s)
component of type BODY has unexpected field(s)
code_expiration_minutes, add_security_recommendation
When creating a Template the above fields are unexpected.
Kind Regards,
Rainer

Hi Rainer, thanks for the feedback!
These two field should sit inside TemplateMessageComponentObject instead, will publish a fix soon

Published version 1.0.2, should solve the issue


when chat with marketplace bot ，happen error

{"detail":"Internal Server Error: 1 validation error for BotModel\nrepo_name\n Input should be a valid string [type=string_type, input_value=None, input_type=NoneType]\n For further information visit https://errors.pydantic.dev/2.9/v/string_type"}

The issue has been resolved. Thank you for your feedback.


[BEAM-7746] Cleanup historical DnFnRunner-as-Receiver cruft.

This could be a clean alternative to https://github.com/apache/beam/pull/10784

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

LGTM.  I checked it out and ran mypy and did not see any new issues pop up.

Run PreCommit

retest this please

Run Python PreCommit


Fix EElixir for snippet

Typo in the snippet, should be a $ so that the variable jumping works properly

thanks!


MSAL not returning control back to application after login failure

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.27.0
Wrapper Library
MSAL React (@azure/msal-react)
Wrapper Library Version
1.4.2
Description
We are migrating from adal-> msal and using MSAL react npm package for the same.
A sample code usage -
<Router basename={process.env.TENANT_BASENAME}>
<MsalProvider instance={AuthenticationUtil.getMSALInstance()}>
 <MsalAuthenticationTemplate
   interactionType={InteractionType.Redirect}
   authenticationRequest={loginRequest}
    errorComponent={Error}
 >
  <Switch>
   <Route path="/" component={component1}/>
   ...
   </Switch>
 </MsalAuthenticationTemplate>
</MsalProvider>
</Router>

For a happy use case where user has access, it works fine but for alternate use case where user does NOT have access, it gets stuck on the login screen that says, 'Trouble Signing you in'.

Now this is valid scenario mentioned here but then we would like to show the custom page or message when this 'access denied' scenario occurs. And the problem seems like the control is still at 'login.microsoft.com' page and not our calling application. I enabled verbose logging and it confirms msal:loginStart event is fired but not msal:loginFailure

Is there a way to get back to our application/site after this scenario happens?
We want to show a custom page with instructions on how to get access and not this generic page.
I am passing errorComponent in <MsalAuthenticationTemplate>  but that doesn't seem to work for this.
MSAL Configuration
{
    auth: {
        clientId,
        authority: endpoint,
        postLogoutRedirectUri: process.env.POSTLOGOUTREDIRECTURI,
    },
    cache: {
        cacheLocation: process.env.CACHELOCATION,
    },
    system: {
        loggerOptions: {
            loggerCallback: (
                level: LogLevel,
                message: string,
                containsPii: boolean
            ): void => {
                if (containsPii) {
                    return;
                }
                switch (level) {
                    case LogLevel.Error:
                        console.error(message);
                        return;
                    case LogLevel.Info:
                        console.info(message);
                        return;
                    case LogLevel.Verbose:
                        console.debug(message);
                        return;
                    case LogLevel.Warning:
                        console.warn(message);
                        return;
                }
            },
            piiLoggingEnabled: false,
        },
        windowHashTimeout: 60000,
        iframeHashTimeout: 6000,
        loadFrameTimeout: 0,
        asyncPopups: false,
    },
};

Relevant Code Snippets
No response
Identity Provider
Azure AD / MSA
Source
Internal (Microsoft)

@waykolep The service team does not relay this error back to MSAL and hence the application cannot be redirected or the error handled. I can check with them if this is a scenario they support.


How to set core number?

@qiaochen Hi, thank you for your help, I think I have almost done it. However, I used a shared server and the administrator found I used too many cores and kill my process. And the server has no GPU and it spends hours in the following step:
def expBaseAE(adata, exp_metrics):
    n_cells, n_genes = adata.X.shape
    in_dim = n_genes
    z_dim = args.z_dim
    h_dim = args.h_dim

    model = get_baseline_AE(in_dim, z_dim, h_dim).to(device)
    model = main_AE(args, model, save_name=f"baseAE_{args.model_name}")
    model.eval()
    with torch.no_grad():
        x = model.encoder(tensor_x)
        s = model.encoder(tensor_s)
        u = model.encoder(tensor_u)

        v = estimate_ld_velocity(s, u, device=device).cpu().numpy()
        x = x.cpu().numpy()
        s = s.cpu().numpy()
        u = u.cpu().numpy()

    adata = new_adata(adata, x, s, u, v, g_basis=args.nb_g_src)
    scv.tl.velocity_graph(adata, vkey='new_velocity')

    scv.pl.velocity_embedding_stream(adata, vkey="new_velocity", basis='X_umap', color='leiden',
                                    title="Baseline AutoEncoder",
                                    )
    scv.tl.velocity_confidence(adata, vkey='new_velocity')
    exp_metrics['Baseline AutoEncoder'] = evaluate(adata, cluster_edges, 'leiden', "new_velocity")

expBaseAE(adata, exp_metrics)

Train Epoch: 100/20000 	Loss: 58.325161
Train Epoch: 200/20000 	Loss: 58.139397
Train Epoch: 300/20000 	Loss: 57.977493
Train Epoch: 400/20000 	Loss: 57.829357
Train Epoch: 500/20000 	Loss: 57.699886
Train Epoch: 600/20000 	Loss: 57.579666
Train Epoch: 700/20000 	Loss: 57.464165
Train Epoch: 800/20000 	Loss: 57.350796
Train Epoch: 900/20000 	Loss: 57.239578

Could you point out how can I set the cores without GPU?
Thank you very much~~

torch.set_num_threads(20)


Add course choice validation on sibling status

Context
This PR must be merged after https://github.com/DFE-Digital/apply-for-teacher-training/pull/8596
Currently, a database unique index on ApplicationChoice table prevents the creation of a record with the same application_form_id and course_option_id.

Duplicate application is one which is made on the same application form to the same course.

This constraint is preventing a candidate from reapplying to a course.
With Continuous Applications, we want to allow Candidates to reapply to the same course on the same application form if any previous applications on the application form to the same CourseOption have a "reapplyable" status. The reapplyable statuses are

rejected
cancelled
withdrawn
declined
offer_withdrawn

Changes proposed in this pull request

Add application level validations on the ApplicationChoice model which prevent a duplicate application WRT reapply status on siblings.

Guidance to review

Consider the differences beteween ReapplyValidator and the CourseSelectionValidator. Offer suggestions on how they might share behaviour.

Link to Trello card
Trello Ticket
Things to check

[x] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] If this code adds a column to the DB, decide whether it needs to be in analytics yml file or analytics blocklist
[x] API release notes have been updated if necessary
[x] If it adds a significant user-facing change, is it documented in the CHANGELOG?
[x] Required environment variables have been updated added to the Azure KeyVault

 CA: Allow candidates to reapply for previously unsuccessful choices


failed database version upgrade

Winter CMS Build
1.2
PHP Version
8.1
Database engine
PostgreSQL
Plugins installed
Builder
Issue description
I changed the column (e.g. drop) AND change name of table and tried to apply this upgrade to other system.
But i have some view which forbid to apply patch - but the name of table was changed. This shouldn't work like this. All or nothing. If it break - it should be still old name of table.
Steps to replicate
Changed the column (e.g. drop) AND change name of table and tried to apply this upgrade to other system.
Workaround
I have to change manually name of table and apply patch again

I have been unable to replicate this with the latest version of the Builder plugin. Please feel free to re-open if the issue persists.


validated_by does not correlate with any element in actual

Describe the bug
Not able to create fivetran_connector_fingerprints.  Would love to know what the proper way to obtain the hash is.  Also is the public_key supposed to be the fivetran public key or the ssh host key for the instance?
To Reproduce
get_ssh_key_hash.sh
#!/bin/bash
HASH=$(ssh-keygen -lf ssh_host_key.pub | awk '{print $2}' | awk -F: '{print $2}')
echo -n "{\"hash\": \"${HASH}\"}"

fivetran.tf
data "fivetran_connector_fingerprints" "connector_fingerprints" {
    id = var.connector_id
}

data "external" "output_hash" {
  program = ["bash", "${path.module}/scripts/get_ssh_key_hash.sh"]
}

resource "fivetran_connector_fingerprints" "approved_fingerprints" {
    connector_id = var.connector_id
    fingerprint {
        hash = data.external.output_hash.result["hash"]
        public_key=data.aws_ssm_parameter.user_public_key["fivetran"].value
    }
}

Expected behavior
Should be able to create an approved connector fingerprint
Logs & Output
 Error: Provider produced inconsistent result after apply
│
│ When applying changes to
│ fivetran_connector_fingerprints.approved_fingerprints, provider
│ "provider[\"registry.terraform.io/fivetran/fivetran\"]" produced an
│ unexpected new value: .fingerprint: planned set element
│ cty.ObjectVal(map[string]cty.Value{"hash":cty.StringVal("<<REDACTED>>"),
│ "public_key":cty.StringVal("ssh-rsa
│ <<REDACTED>>"), "validated_by":cty.UnknownVal(cty.String),
│ "validated_date":cty.UnknownVal(cty.String)}) does not correlate with any
│ element in actual.
│
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.

Plugin version:
1.3.2
Additional context
None

Full debug output:
fivetran_connector_fingerprints.approved_fingerprints: Creating...
2024-10-10T18:48:26.320-0400 [INFO]  Starting apply for fivetran_connector_fingerprints.approved_fingerprints
2024-10-10T18:48:26.320-0400 [DEBUG] fivetran_connector_fingerprints.approved_fingerprints: applying the planned Create change
2024-10-10T18:48:26.551-0400 [DEBUG] provider.terraform-provider-fivetran_v1.3.2: Value switched to prior value due to semantic equality logic: @module=sdk.framework tf_provider_addr=registry.terraform.io/fivetran/fivetran tf_rpc=ApplyResourceChange @caller=github.com/hashicorp/terraform-plugin-framework@v1.8.0/internal/fwschemadata/value_semantic_equality.go:87 tf_attribute_path=connector_id tf_req_id=99aec47c-12c1-924c-42eb-d84cd7d1c977 tf_resource_type=fivetran_connector_fingerprints timestamp=2024-10-10T18:48:26.551-0400
2024-10-10T18:48:26.552-0400 [DEBUG] provider.terraform-provider-fivetran_v1.3.2: Value switched to prior value due to semantic equality logic: tf_resource_type=fivetran_connector_fingerprints @caller=github.com/hashicorp/terraform-plugin-framework@v1.8.0/internal/fwschemadata/value_semantic_equality.go:87 @module=sdk.framework tf_attribute_path="fingerprint[Value({\"hash\":\"<<REDACTED>>\",\"public_key\":\"\\"ssh-rsa <<REDACTED>> \\n\\"\n\",\"validated_by\":\"Data Infrastructure\",\"validated_date\":\"2024-10-10T22:48:26.434Z\"})].hash" tf_provider_addr=registry.terraform.io/fivetran/fivetran tf_req_id=99aec47c-12c1-924c-42eb-d84cd7d1c977 tf_rpc=ApplyResourceChange timestamp=2024-10-10T18:48:26.551-0400
2024-10-10T18:48:26.553-0400 [DEBUG] State storage *remote.State declined to persist a state snapshot
2024-10-10T18:48:26.553-0400 [ERROR] vertex "fivetran_connector_fingerprints.approved_fingerprints" error: Provider produced inconsistent result after apply

Confirmed it exists in 1.3.1 as well.

I discovered via Support ticket to Fivetran that this is actually a dead end.  They don't provide you a way to obtain the values that you would need to supply to this resource in the first place.  The expected way to approve a fingerprint is to pause the connector, turn on autotrust of the fingerprints, swap the instance, then run setup tests so it trusts it, then turn off autotrust and unpause the connector.  I will update if I come up with some semi-graceful way to do this in the context of Terraform.

Ended up going with the Fivetran Proxy agent instead.  Looks like ssh tunnels aren't really the recommended path anyways.
Used the following in my user data template with an autoscaling group:
user_data.tpl
export HVR_HOME=/home/fivetran/hvr_home
export HVR_CONFIG=/home/fivetran/hvr_config
export HVR_TMP=/home/fivetran/hvr_tmp

PATH=$PATH:$HVR_HOME/bin

cat << EOF > /home/fivetran/.profile
export HVR_HOME=/home/fivetran/hvr_home
export HVR_CONFIG=/home/fivetran/hvr_config
export HVR_TMP=/home/fivetran/hvr_tmp
export PATH=$PATH:$HVR_HOME/bin
EOF

umask 022
mkdir $HVR_HOME
cd $HVR_HOME

aws s3 sync s3://${bucket}/agent/ .
EXECUTABLE=$(ls *.tar.gz)
tar xzf $EXECUTABLE

mkdir -p /home/fivetran/hvr_config/proxy

cp fivetran-config.json /home/fivetran/hvr_config/proxy/proxyagent.conf

sudo cat << EOF > /etc/systemd/system/fivetran_proxy.service
[unit]
Description=Fivetran Proxy Agent

[Service]

Type=simple

ExecStart=/home/fivetran/hvr_home/jre/bin/java -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/home/fivetran/hvr_config/proxy/ -jar /home/fivetran/hvr_home/proxy/proxyagent.jar /home/fivetran/hvr_config/proxy/proxyagent.conf

# Restart this service to after a crash
Restart=always

# The number of seconds to wait before attempting a restart
RestartSec=5s

[Install]
WantedBy=multi-user.target
EOF

sudo systemctl enable fivetran_proxy.service
sudo systemctl start fivetran_proxy.service
sudo systemctl status fivetran_proxy.service

Closing since the bug is no longer relevant to my use case.


New usage should be recommended in messages

Expected behavior
When we give a message to the user for running a command, it should be the new usage.
Actual behavior

Run specifications with "gauge specs/" message to be changed. This occurs in the initialization of a project

The check updates message should be updated. This occurs during gauge run and when there are updates.

Version
Gauge version: 0.9.0.nightly-2017-06-28

Plugins
-------
csharp (0.10.1)
html-report (4.0.1.nightly-2017-06-27)
java (0.6.5.nightly-2017-06-28)
ruby (0.4.1)
spectacle (0.1.2)
xml-report (0.2.0)

gauge update -c still gives the old usage in the message
csharp    		0.10.1    	Run 'gauge --update csharp'

gauge --docs abc still prints the old usage
[DEPRECATED] This usage will be removed soon. Run gauge help --legacy for more info.
Error starting plugin abc. Failed to get plugin.json. Plugin abc is not installed. To install, run gauge --install abc.

Templates will not be fixed till we can ensure that users of old version of gauge are not affected. New commands are not available prior to gauge 0.9.0.


Inscription preview missing from send form

A user reported

The inscription preview also appears missing from the send form, which may be another formatting issue?

When I check this in version 6.47.0 it looks normal for some ordinals such as a transfer inscription:

but not for others (image, for example a runestone)

Possibly related to #5824

I took a quick look at this and it indeed does show previews of some inscriptions but not of others:
https://github.com/user-attachments/assets/a58b37d2-0c3e-406a-871c-b6e9c0ee331f


Owntracks missing from integrations panel

Home Assistant release with the issue:

82.1
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io
Component/platform:

Owntracks
Description of problem:
Owntracks not showing in integrations panel within the configuration screen
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

It was not available as integration in 0.82. It was released in 0.83

@arsaboo is correct. Closing.


Use an unambiguous date format

You currently use mm/dd/yyyy

while this make sense in the US, for the vast majority of the world it is wrong

source: https://en.wikipedia.org/wiki/Date_format_by_country
I would like to suggest moving to yyyy/mm/dd or yyyy mmm dd. since both are unambiguous irrespective of country
I know some people will suggest region detection and localisation. I would prefer this option was not taken. the reason being people regularly move between multiple different devices, multiple different server in diff locals, and multiple diff MS sites/pages. localisation will not consistently solve the problem.

Failed to submit internal item.

#log-request @ShevaDas

#log-suggestion @ShevaDas

Failed to submit internal item.

#log-suggestion @ShevaDas

Failed to submit internal item.

#log-suggestion @ShevaDas

Failed to submit internal item.

#log-suggestion @ShevaDas

🚀 ATTENTION: Internal request logged.

@SimonCropp thanks for the feedback! I'll discuss it with the team and get back to you.

@ShevaDas thanks

I feel like this is well-known, but as I don't see it in the comments: ISO 8601 solved this problem a long time ago. YYYY-MM-DD format all around the world.

Just to clarify, Docs currently changes the date format based on the user locale (see images). I'm investigating if we can use ISO 8601 for clarity, but our current solution does take different date formats used around the world into account.

Just to clarify, Docs currently changes the date format based on the user locale (see images). I'm investigating if we can use ISO 8601 for clarity, but our current solution does take different date formats used around the world into account.

that may be the case. unfortunately that is not consistent over all websites, let alone all MS websites. so whenever someone see a 1/12/yyyy there is no way they can tell if this is one of the sites that localises dates.

I agree with @SimonCropp.
It would be fine to have localized dates for non-technical content (commercial, media, educational, etc.) But in the technical world, where nearly everybody should used to having solutions to disambiguate data (like a date format), it seems like a real step backward to purposely introduce a known ambiguity in the format just to suit an aesthetic.
At the very least, please provide an alternate title that either displays the date in a localized and unambiguous full-form (like "Monday, September 21, 2018"), else put the ISO 8601 version as the alternate title.

@ShevaDas

Just to clarify, Docs currently changes the date format based on the user locale (see images).

As far as I can tell, it does not. It changes based on the language which I selected, not based on the locale configured on my computer.
And considering that en-US always contains the best content, many users (including me), prefer to use the en-US version of docs, even though they're not used to the US date format.

Wondering why you closed it? I still thought it was a good idea.

Figured if it hadn’t been actioned in 9 months, then it prob never would be


Doubt about Mustache specification

Hi, right now unused variables are replaced by an empty string:
use Template::Mustache;
Template::Mustache.render('{{bar}} {{foo}}', {foo=>"d"}) # will print ' d'

Is there a way to disable this? Or is not possible? It would be extremely helpful to concatenate renders without replacing all variables at the same time.

I thought lambdas could work but they cannot...
use Template::Mustache;

say Template::Mustache.render(
  '{{#wrapped}} {{name}} is awesome. {{/wrapped}}'
, {wrapped => -> $text { $text }});

It sounds like you would want to use Inheritance, with several levels. For example, this spec test.
If would be possible to make a pragma to leave variables in place of they are not defined in the context. That's definitely not how mustache is designed, but it's a sensible and easy feature to add.
I'd rather use the Inheritance feature though, if I'm right that it would be a better fit for what you're ultimately trying to do.

I do not see how Inheritance with several levels can solve this. What I want is to generate the menu only once, to avoid replacing it with each HTML file generated. At this moment, I have implemented this behavior with two renders:

the first one generates four different templates (each one with a different menu).
the second renders the rest of the data using one of the previous templates.

The problem is that the first render replaces all unused variables by an empty string, so the second render does nothing. I think if I use partials or inheritance, all menu data will have to be replaced with each HTML file, so it will take the same time. With these two renders, I reduce the generation time around 400 seconds.
You can see the changes in this commit: https://github.com/Raku/Documentable/commit/b683b7a9cf21c060988c67a50e8bc52179374118.
Now my question is, can I get that behavior with Inheritance?

I didn't get to trying your scenario with inheritance, but I did implement the pragma. It's not merged to master yet, but you can try it out in the keep-undef-pragma branch.

Oh, that was fast. Thanks a lot, @softmoth, it's a great help to have this feature :).

I've committed this to master and released it to CPAN as version 1.2.2.


[FEATURE][POI MAP] Add zoomand center options

Summary
The goal for this PR is to add zoomand centerin the options prop
(Internal for Opendatasoft only) Associated Shortcut ticket: sc-43528.
Changes
Fix a behavior where the map bbox was updated when a change in options. Did the same thing for the center prop.In Map.svelte the bbox and center given to mapRender change only their value change not their reference.
Maybe we can factorize this code into something like const freshCenter = useFreshValue(center, comparaisonCallback)
Breaking Changes
none
Changelog
/
Open discussion
/
To be tested
/
Review checklist

[x] Description is complete
[x] Commits respect the Conventional Commits Specification
[x] 2 reviewers (1 if trivial)
[ ] Tests coverage has improved
[ ] Code is ready for a release on NPM

The whole concept seems pretty good. I'm really in favor of factoring the zoom/bbox reactivity into its own thing.
As for exposing zoom/center separately or as one prop, it's a bit stylistic… I kinda prefer the first, but the second is flatter. Honestly, doesn't make that much differenc.

I used jumpTo in https://github.com/opendatasoft/ods-dataviz-sdk/pull/194/commits/8ef37e99d79a4b5143a69473fe795226d121f473


UART RTT devicetree & async support

Switches instantiation of the uart_rtt driver from Kconfig symbols to devicetree nodes.
Adds CONFIG_UART_ASYNC_API support to the driver, which eliminates hard faults when the RTT backend is used with async functions. Because asynchronous reception is not possible, only the TX path is implemented.
There are no in tree users of the previous CONFIG_UART_RTT_* symbols, so there are no tests validating the new behavior. The commit message contains an example of the devicetree nodes required to instantiate driver instances.

What is the real benefit of this? RTT is not a hardware device, it is purely software.

What is the real benefit of this? RTT is not a hardware device, it is purely software.

The benefit is that it allows the use of RTT in chosen and alias nodes.
I agree that the implementation is pure software, but it is pretending to be a hardware device, and therefore is seems reasonable (to me at least) to specify in devicetree.

I would still like a discussion on if this really is the right solution here.
I often find myself enabling the RTT console as a pure software configuration change while debugging. It would be quite bothersome to have to edit the devicetree for this to work. Is there any way we could support both methods? After all, this is pure software functionality.

I often find myself enabling the RTT console as a pure software configuration change while debugging. It would be quite bothersome to have to edit the devicetree for this to work. Is there any way we could support both methods? After all, this is pure software functionality.

My understanding is that changes to the uart_rtt driver are completely independent of the RTT console. log_backend_rtt.c calls the SEGGER functions directly, as does the char_out function provided to printk in rtt_console.c. This PR therefore shouldn't change anything about enabling RTT for debug.

@galak @carlescufi any chance of another review, hoping to get this into 2.4

I think there is a zephyr policy that code must be somehow validated in the tree (compiled). Is it used somewhere?

uart_rtt was previously not used anywhere in tree. I can whip up a sample application.

I think there is a zephyr policy that code must be somehow validated in the tree (compiled). Is it used somewhere?

Pretty sure the testcase I added will compile for the 'qemu_cortex_m0' platform at least. (It does locally for me)

don't you need overlay which will configure uart rtt?

don't you need overlay which will configure uart rtt?

Thats the segger_rtt.overlay

Thats the segger_rtt.overlay

somehow i missed that.


Turn on source maps.

Right now Atlas is not built with source maps which makes debugging Atlas bugs more difficult then necessary. Turn on source maps in Webpack to make debugging easier.

Fixed by: https://github.com/DigitalRiver/react-atlas/tree/0.1.0-rc, we can close this issue when that branch is merged to master.


Failed to connect to get.helm.sh port 443: Connection refused

Trying to download in Windows
helm-v3.5.2-linux-amd64.tar.gzFailed - Network error

Trying to install helm in Ubuntu
 curl https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 11248  100 11248    0     0  21222      0 --:--:-- --:--:-- --:--:-- 21222
Error: unknown flag: --template
Helm v3.5.2 is available. Changing from version .
Downloading https://get.helm.sh/helm-v3.5.2-linux-amd64.tar.gz
curl: (7) Failed to connect to get.helm.sh port 443: Connection refused
Failed to install helm
        For support, go to https://github.com/helm/helm.

In my code. It's ok. Please retry it.

@Dmdv Are you still experiencing the issue? I am unable to reproduce.

Closing as resolved until disproven otherwise. Likely just a flaky network error.


Change feature type names in RecordData

The feature types in RecordData (FixedLenFeature, FixedLenSequenceFeature, and VarLenFeature) are directly borrowed from TensorFlow and might cause confusion for PyTorch users. Based on my discussion with @AvinashBukkittu yesterday, we think it might be worthy to also introduce a set of aliases for these types, and use them in the examples.
Here's the meaning behind each feature type, and what happens when we collate such features:

FixedLenFeature are tensor features that have a fixed shape. These features are stacked together (torch.stack(features, dim=0)) while collating.
FixedLenSequenceFeature represent a list of tensor features such that each list element have the same fixed shape. These features are padded and batched (tx.data.padded_batch(features)) while collating.
VarLenFeature can be tensors of any shape, or other objects that are not tensors. These features are simply put into a list (list(features)) while collating.

I think we can rename the feature types to either:

describe the object types of the input features...

tensor, tensor_seq, and any/other.

... or, describe how they're collated.

tensor, pad_tensor, and list.

But yeah, any suggestions are welcome.

Also, for the feature_original_types format:
https://github.com/asyml/texar-pytorch/blob/43967ee238a5da2e996f4f71644a940a86cad009/texar/torch/data/data/record_data.py#L444-L470
Since VarLenFeature can be any object, it does not really make sense to ask the user to write a dtype. Maybe we can also accept None here.

The feature types in RecordData (FixedLenFeature, FixedLenSequenceFeature, and VarLenFeature)

These are called feature_len_type in the doc
https://github.com/asyml/texar-pytorch/blob/43967ee238a5da2e996f4f71644a940a86cad009/texar/torch/data/data/record_data.py#L455
Are we going to change the name too? The overall field name feature_original_types could also affect the naming here. If it's kept not changed, the naming based on describe how they're collated is probably not suitable

If these names are only for indicating the shapes, I think sth like "FixedLen*" or "FixedShape*" is probably more explicit than "tensor" (which does not necessary have fixed shapes)?

I guess these original names are more intuitive to previous TF users, but they might be confusing for a PyTorch-only user in several aspects:

In TF, the dataset can only contain tensors, while this is not the case for PyTorch. Fixed*Feature would assume the data are all tensors, but it is not reflected in the naming.
There's no clear distinction between FixedLenSequenceFeature and VarLenFeature. In TF we'd use a None-dimension to indicate a non-fixed dimension size, but there's no such counterpart in PyTorch.

Indeed the name tensor by itself is not good enough. How about these:

stacked_tensor, padded_tensor, list
The advantages of these names would be:

They're explicit about whether the type must be a tensor.
They indicate how the features are collated.
They're much shorter to write.

A quick question: if a feature is a single int (e.g., a label), would stacked_tensor be used? -- If so, would it be a bit confusing for PyTorch users cuz for them, if I'm correct, int is not a tensor?
I'm good with the new naming, the thing is that if we use it, the name feature_original_types should also be changed, cuz stacked_tensor indicates the type after processing (e.g., collating) instead of the original type.

If the feature is a single int, stacked_tensor could be used. Internally np.stack is called, so as long as arguments are acceptable by np.stack, they can be used. But either way, np.stack will always return a NumPy ndarray, so the collated output is guaranteed to be a tensor.
I think feature_original_types is still acceptable, because these can still be interpreted as the (more abstract) types of the feature. What might needs change is the name feature_len_type: we could just change it to feature_type.

Yes, they are still "types" of the feature, but not "original". Perhaps we can rename it as feature_types, and feature_len_type as feature_shape_type?
For stacked_tensor, would fixed_shape_tensor clearer?
Either way, it's important to add in the doc what common types each "feature_type" can handle. For example, stacked_tensor is for single scalar, fixed shape features, etc

I see. It makes more sense to call it feature_types instead of features_original_types, but this breaks compatibility with Texar-TF. What I wanted to achieve is that previous code that uses features_original_types and **Feature can still work (or maybe gradually deprecate them), but we encourage new code to use this different set of names.
If we decide on this set of names, which describes types of collated results, then I think it might be better to name this as feature_collate_method or something along the lines. Also, I think it's not really appropriate to use fixed_shape_tensor since it describes individual examples more, and is not as explicit compared to stacked_tensor.

My two cents on this is the following

feature_types is more elegant than feature_original_types. We can mark feature_original_types as deprecated but still support it? Similarly, feature_shape_type is more explicit than feature_len_type (This naming change won't really affect our code base as we pass in a list, we just have to update the documentation)

I like the following mapping
FixedLenFeature -> stacked_tensor
FixedLenSequenceFeature -> stacked_padded_tensor (If you feel this is verbose, padded_tensor is good)
VarLenFeature -> list

feature_collate_method sounds good to me.
For other parts, I think Avinash made a good summarization.

Cool, then I'll make a PR correspondingly.


Sort-AppFoldersByDependencies throws PropertyNotFoundException if one of the app.json files does not have a dependencies property

Hi NavContainerHelper contributors,
I ran into the issue that Sort-AppFoldersByDependencies throws an exception, if one of my apps does not have a dependencies property in the app.json file.
That is, targeting BC16, I have replaced the dependencies on the Base and System Application with the application property in the app.json file in my 'main' app.
I was able to easily resolve this adding an empty list to the app.json file:
"dependencies": [],

I am reporting it here anyway, because it might be good to have it fixed, as others might run into it as well.

Thanks, will have a look.

Fixed in <IP_ADDRESS> and <IP_ADDRESS>


Decide which Web Components to provide in v1.0

@ChristophBo May add your ideas here in conversation.

Duplicate of #2