EVbox BusinessLine Hub/Satelite

Hi, i'm testing at moment to use this OCPP integration with homeassistant. We have four EVbox BusinessLine chargers. One of them is the Hub and the others are "satelites". I can only configure the hub to connect to a specific OCPP platform. The integration recognised 4 connectors but i'm not able to control them individualy. Do you have a solution?
Thanks!

There was a pull request regarding multiple connectors: https://github.com/lbbrhzn/ocpp/pull/803 But as it seems the former reporter vanished. Right now this addin does not allow control of multiple connectors.

i've been working on better support for multiple chargers and multiple connectors... work in progress.


VPG reward shift

Related to https://github.com/openai/spinningup/issues/67
This simple fix works well for me, but I'm not confident about VPGBuffer.finish_path which seems to append the last reward again.
rews = np.append(self.rew_buf[path_slice], last_val)
This make rews longer than the previous slice and the rest of the buffers related to same trajectory.
Is that intended? Why ?
Does the slice below throw away the extra element ?
self.ret_buf[path_slice] = core.discount_cumsum(rews, self.gamma)[:-1]

Fixed in latest version.


Adding docker birthday party event

@ChrisChinchilla if you want to include a picture of the cake or the event you went to, that would be awesome

Added and ack


Subscriptions

Not sure how much work this is to implement but support for graphql-js compatible subscriptions (maybe with an experimental flag or something?) would be super-useful and really appreciated.
I (very foolishly) assumed libgraphqlparser would support subscriptions when we started building on top of it. Now we've got a whole ruby GraphQL DSL built and nowhere to subscribe :(
Related Conversations:

https://github.com/Shopify/graphql-parser/pull/8
https://github.com/facebook/graphql/pull/109

Does the attached commit work for you? Seems legit from the tests I added, but I would like to have other eyes on it before I merge it to master.

The graphql-parser gem seems to have an issue with this branch. I'm not a C++ person, any idea what's going on here:
Installing graphql-parser 0.0.2 with native extensions

Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

    /Users/robgilson/.rbenv/versions/2.2.2/bin/ruby -r ./siteconf20160429-11555-1e20m4.rb extconf.rb
checking for main() in -lgraphqlparser... yes
creating Makefile

make "DESTDIR=" clean

make "DESTDIR="
compiling graphql_parser.c
compiling graphql_ruby.c
graphql_ruby.c:514:18: warning: implicit declaration of function 'GraphQLAstArrayValue_get_values_size' is invalid in C99 [-Wimplicit-function-declaration]
  return INT2FIX(GraphQLAstArrayValue_get_values_size(node));
                 ^
/Users/robgilson/.rbenv/versions/2.2.2/include/ruby-2.2.0/ruby/ruby.h:234:30: note: expanded from macro 'INT2FIX'
#define INT2FIX(i) (((VALUE)(i))<<1 | FIXNUM_FLAG)
                             ^
graphql_ruby.c:889:7: error: no member named 'visit_array_value' in 'struct GraphQLAstVisitorCallbacks'; did you mean 'visit_float_value'?
  cbs.visit_array_value = visit_array_value;
      ^~~~~~~~~~~~~~~~~
      visit_float_value
/usr/local/include/graphqlparser/c/GraphQLAstVisitor.h:38:26: note: 'visit_float_value' declared here
  FOR_EACH_CONCRETE_TYPE(FUNC_MEMBER)
                         ^
/usr/local/include/graphqlparser/c/GraphQLAstForEachConcreteType.h:21:28: note: expanded from macro 'FOR_EACH_CONCRETE_TYPE'
MACRO(IntValue, int_value) \
                           ^
/usr/local/include/graphqlparser/c/GraphQLAstVisitor.h:26:29: note: expanded from macro 'FUNC_MEMBER'
  visit_##snake_type##_func visit_##snake_type; \
                            ^
<scratch space>:68:1: note: expanded from here
visit_float_value
^
graphql_ruby.c:889:25: warning: incompatible pointer types assigning to 'visit_float_value_func' (aka 'int (*)(const struct GraphQLAstFloatValue *, void *)') from 'int (const struct GraphQLAstArrayValue *, void *)' [-Wincompatible-pointer-types]
  cbs.visit_array_value = visit_array_value;
                        ^ ~~~~~~~~~~~~~~~~~
graphql_ruby.c:890:7: error: no member named 'end_visit_array_value' in 'struct GraphQLAstVisitorCallbacks'; did you mean 'end_visit_float_value'?
  cbs.end_visit_array_value = end_visit_array_value;
      ^~~~~~~~~~~~~~~~~~~~~
      end_visit_float_value
/usr/local/include/graphqlparser/c/GraphQLAstVisitor.h:38:26: note: 'end_visit_float_value' declared here
  FOR_EACH_CONCRETE_TYPE(FUNC_MEMBER)
                         ^
/usr/local/include/graphqlparser/c/GraphQLAstForEachConcreteType.h:21:28: note: expanded from macro 'FOR_EACH_CONCRETE_TYPE'
MACRO(IntValue, int_value) \
                           ^
/usr/local/include/graphqlparser/c/GraphQLAstVisitor.h:27:33: note: expanded from macro 'FUNC_MEMBER'
  end_visit_##snake_type##_func end_visit_##snake_type;
                                ^
<scratch space>:71:1: note: expanded from here
end_visit_float_value
^
graphql_ruby.c:890:29: warning: incompatible pointer types assigning to 'end_visit_float_value_func' (aka 'void (*)(const struct GraphQLAstFloatValue *, void *)') from 'void (const struct GraphQLAstArrayValue *, void *)' [-Wincompatible-pointer-types]
  cbs.end_visit_array_value = end_visit_array_value;
                            ^ ~~~~~~~~~~~~~~~~~~~~~
3 warnings and 2 errors generated.
make: *** [graphql_ruby.o] Error 1

make failed, exit code 2

Gem files will remain installed in /Users/robgilson/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/graphql-parser-0.0.2 for inspection.
Results logged to /Users/robgilson/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/extensions/x86_64-darwin-15/2.2.0-static/graphql-parser-0.0.2/gem_make.out

Looks like the graphql-parser gem hasn't been updated to be compatible with this API-breaking change on master (which corrects an API difference from graphql-js): 5b836547c2887387e5db15a844a48fa4fd9bcbf8
That's probably because I haven't cut a versioned release since making that change. I'll fix that, though I'd prefer to include subscription support rather than do a point release just for that.
To fix it in graphql-parser, you probably just need to change array_value to list_value.

I also had to change GraphQLAstArrayValue to GraphQLAstListValue locally. Here are the find/replace commands I used, in the graphql-parser directory:
perl -p -i -e 's|array_value|list_value|g' $(git grep -l array_value)
perl -p -i -e 's|ArrayValue|ListValue|g' $(git grep -l ArrayValue)
Hope this helps!

I've set up a fork of graphql-parser with your changes and added test for subscriptions but it isn't passing yet. Not sure why:
https://github.com/D1plo1d/graphql-parser/tree/feature/subscriptions
You can run the tests with: bundle install & rake compile & rake test

Nm, typos strike again! Totally works :)

w00t! Thanks @swolchok!


Double Click Close Tab Patch

This Patch introduces the function of double-clicking to close tabs for Thorium through a custom flag.

@gz83 Made changes and uploaded files seperately.


Page refresh infinitely after adding chat feature

Hi ,
I am building  a chat app with sso authentication. it is refreshing infinitely.
Sample code.
import streamlit as st
import os
from msal_streamlit_authentication import msal_authentication

# App title
st.title('Ops Chatbot')

login_token = msal_authentication(
    auth={
        "clientId": "asdsadasdasdasd",
        "authority": "https://login.microsoftonline.com/asdsadasdasdasd",
        "redirectUri": "/auth-response",
        "postLogoutRedirectUri": "/"
    },
    cache={
        "cacheLocation": "sessionStorage",
        "storeAuthStateInCookie": False
    },
    login_request={
       # "scopes": ["aaaaaaa-bbbb-cccc-dddd-eeeeeeeeeee/.default"]
    },
    login_button_text="Login", # Optional, defaults to "Login"
    logout_button_text="Logout", # Optional, defaults to "Logout"
    html_id="html_id_for_button", # Optional, defaults to None. Corresponds to HTML id.
    key=1)

if login_token != None:
    username = login_token["account"]["username"]
    st.sidebar.write(f"Welcome {username}")
    # instanciate a 0365-python account to manipulate mailbox
    login_token['refresh_token'] = ''  # this is requiered as it is not defined by msal_streamlit_authentication
    prompt = st.chat_input("Say something")
    if prompt:
        st.write(f"User has sent the following prompt: {prompt}")

else:
    st.error("Login failure : please login ...")

``

If it helps, I changed the code like below and it worked
username = login_token["account"]["username"]
st.sidebar.write(f"Welcome {username}")
# instanciate a 0365-python account to manipulate mailbox
login_token['refresh_token'] = ''  # this is requiered as it is not defined by msal_streamlit_authentication
prompt = st.chat_input("Say something", disable=not login_token)
if prompt:
    st.write(f"User has sent the following prompt: {prompt}")


View source code could route to repo overview?

Not sure how this would work, esp from the user's perspective, but it seems silly to have an "View Source Code" that opens the project in SafariVC when we have a native thingy too. Maybe just open that RepoVC there instead?

Once we have code browsing ya
Sent with GitHawk


Delete containers/terracotta-server directory

The terracotta information that is there is outdated, contains many issues, and cannot be supported by terracotta R&D. It SHOULD NOT BE USED IN ANY CASE.

BigMemory official docker images and doc: https://containers.softwareag.com/products/bigmemorymax-server

Terracotta DB official docker images and doc: https://containers.softwareag.com/products/terracotta-server

Helm charts and other doc and links: https://github.softwareag.com/Terracotta/

The locations above are official Docker images deployed and supported by Terracotta R&D.
Ref: https://itrac.eur.ad.sag/browse/TAB-8504

@mathieucarbou, we have deleted docker builder parts. Can we close this pull request?

@mathieucarbou, we have deleted docker builder parts. Can we close this pull request?

No, the templates were not deleted. I have rebased this PR, please see the diff.


Plugin Start Error

Not sure if I am not setting this up correctly but this is what I get after plugin installation and restarting the HomeBridge Service.
(node:1488) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1) (node:1488) UnhandledPromiseRejectionWarning: HTTPError: Response code 404 (Not Found)     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/homebridge-samsungtv-control/node_modules/got/dist/source/as-promise.js:118:31)     at processTicksAndRejections (internal/process/task_queues.js:97:5) (node:1488) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

How did you install homebridge and the plugin itself?

@gradyhouston can you tell me which app you use to control the tv from your iPhone?

The SmartThings app (not the classic version). I can open the app and see my TVs in it and when connecting the TVs to that app, it pops up the "allow/deny" option. It doesn't allow me to control them, just pair/connect with them.


Adding chunk size option to fetchPools functionality

At the moment we could possibly be discarding a chunk of pools that are not broken which could cause issues if the pool of interest is within the chunk.
One possible investigation is to figure out how to narrow down a chunk.
Not a priority for now as we investigate source of issue with poolQuery


Update ProblemList_openjdk17.txt

Fix #3004

Grinder for testing: https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/1707/

I already did @sophia-guo

@King-kay there may be other changes merged. Looks like there are still conflicts.


Add support for non schema json object

Hey guys,
Been looking to use the connector for our use case and we encoutered an issue when using it with a
JsonConverter with no schema.
https://github.com/aiven/http-connector-for-apache-kafka/blob/main/src/main/java/io/aiven/kafka/connect/http/converter/RecordValueConverter.java
only supports String or Struct but the object we got was a Hashmap.
I'm going to see if I can sort it myself and open a pull request if I do.

@Uriende Thank you for the contribution.


fix travis-ci test

fix #855
the test for cliframework still needs to be updated otherwise php 7.2 will broke the ci test since phpunit 5.7 won't support php 7.2.

Coverage increased (+0.5%) to 51.621% when pulling 0f4a5da154344c38ff78e5055c0e34d17bfd2ab1 on bugfix/phpunit into 117627ed32a1e29799fc05ff6f4ccc4cfe812033 on master.

Coverage increased (+0.5%) to 51.621% when pulling 0f4a5da154344c38ff78e5055c0e34d17bfd2ab1 on bugfix/phpunit into 117627ed32a1e29799fc05ff6f4ccc4cfe812033 on master.

Coverage increased (+0.5%) to 51.621% when pulling 0f4a5da154344c38ff78e5055c0e34d17bfd2ab1 on bugfix/phpunit into 117627ed32a1e29799fc05ff6f4ccc4cfe812033 on master.

Coverage increased (+0.5%) to 51.621% when pulling 0f4a5da154344c38ff78e5055c0e34d17bfd2ab1 on bugfix/phpunit into 117627ed32a1e29799fc05ff6f4ccc4cfe812033 on master.

Coverage increased (+0.5%) to 51.621% when pulling 0f4a5da154344c38ff78e5055c0e34d17bfd2ab1 on bugfix/phpunit into 117627ed32a1e29799fc05ff6f4ccc4cfe812033 on master.


We notified community members about upcoming changes.

Not three months ago. It's not as if I have been waiting for this PR to be merged. I stopped waiting about two days after it went ignored.

I'm pretty sure Arsen told everyone about upcoming changes already in December. Check the #wiki channel on the OSDev Discord (of which you were a member at the time).

I am unable to access that Discord server.

You were able to at the time. In any case, this PR wouldn't have been able to be merged as is anyways, even at the time.
Btw, it's our loss not merging the PR, don't interpret this as us thinking you are obliged  to modify the PR. I for one, was not particularly keen on merging this as is.

indeed. thank you for your contribution, even if it didn't pan out


chore(deps): update nx monorepo to v19 (major)

This PR contains the following updates:

Package
Type
Update
Change

@angular-devkit/build-angular
devDependencies
major
18.2.12 -> 19.0.0

@angular-devkit/core
devDependencies
major
18.2.12 -> 19.0.0

@angular-devkit/schematics
devDependencies
major
18.2.12 -> 19.0.0

@angular/animations (source)
dependencies
major
18.2.12 -> 19.0.0

@angular/animations (source)
peerDependencies
major
18.2.12 -> 19.0.0

@angular/cdk
dependencies
major
18.2.13 -> 19.0.0

@angular/cdk
peerDependencies
major
18.2.13 -> 19.0.0

@angular/cli
devDependencies
major
18.2.12 -> 19.0.0

@angular/common (source)
overrides
major
^18.0.2 -> ^19.0.0

@angular/common (source)
dependencies
major
18.2.12 -> 19.0.0

@angular/common (source)
peerDependencies
major
^18.0.0 -> ^18.0.0 || ^19.0.0

@angular/common (source)
peerDependencies
major
^18.2.0 -> ^18.2.0 || ^19.0.0

@angular/common (source)
peerDependencies
major
18.2.12 -> 19.0.0

@angular/compiler (source)
dependencies
major
18.2.12 -> 19.0.0

@angular/compiler-cli (source)
devDependencies
major
18.2.12 -> 19.0.0

@angular/core (source)
overrides
major
^18.0.2 -> ^19.0.0

@angular/core (source)
dependencies
major
18.2.12 -> 19.0.0

@angular/core (source)
peerDependencies
major
^18.0.0 -> ^18.0.0 || ^19.0.0

@angular/core (source)
peerDependencies
major
^18.2.0 -> ^18.2.0 || ^19.0.0

@angular/core (source)
peerDependencies
major
18.2.12 -> 19.0.0

@angular/elements (source)
dependencies
major
18.2.12 -> 19.0.0

@angular/forms (source)
dependencies
major
18.2.12 -> 19.0.0

@angular/forms (source)
peerDependencies
major
18.2.12 -> 19.0.0

@angular/forms (source)
peerDependencies
major
^18.0.0 -> ^18.0.0 || ^19.0.0

@angular/forms (source)
peerDependencies
major
^18.0.2 -> ^18.0.2 || ^19.0.0

@angular/language-service (source)
devDependencies
major
18.2.12 -> 19.0.0

@angular/material
dependencies
major
18.2.13 -> 19.0.0

@angular/material
peerDependencies
major
18.2.13 -> 19.0.0

@angular/material
peerDependencies
major
^18.0.0 -> ^18.0.0 || ^19.0.0

@angular/material
peerDependencies
major
^18.0.2 -> ^18.0.2 || ^19.0.0

@angular/platform-browser (source)
overrides
major
^18.0.2 -> ^19.0.0

@angular/platform-browser (source)
dependencies
major
18.2.12 -> 19.0.0

@angular/platform-browser (source)
peerDependencies
major
18.2.12 -> 19.0.0

@angular/platform-browser-dynamic (source)
overrides
major
^18.0.2 -> ^19.0.0

@angular/platform-browser-dynamic (source)
dependencies
major
18.2.12 -> 19.0.0

@angular/platform-server (source)
dependencies
major
18.2.12 -> 19.0.0

@angular/platform-server (source)
peerDependencies
major
18.2.12 -> 19.0.0

@angular/router (source)
overrides
major
^18.0.2 -> ^19.0.0

@angular/router (source)
dependencies
major
18.2.12 -> 19.0.0

@angular/router (source)
peerDependencies
major
18.2.12 -> 19.0.0

@angular/router (source)
peerDependencies
major
^18.0.0 -> ^18.0.0 || ^19.0.0

@angular/router (source)
peerDependencies
major
^18.0.2 -> ^18.0.2 || ^19.0.0

@angular/service-worker (source)
dependencies
major
18.2.12 -> 19.0.0

@schematics/angular
devDependencies
major
18.2.12 -> 19.0.0

ng-packagr
devDependencies
major
18.2.1 -> 19.0.0

[!WARNING]
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

angular/angular-cli (@angular-devkit/build-angular)
v19.0.0
Compare Source
Breaking Changes
@schematics/angular

The app-shell schematic is no longer compatible with Webpack-based builders.

@angular-devkit/build-angular

The browserTarget option has been removed from the DevServer and ExtractI18n builders. buildTarget is to be used instead.

Protractor is no longer supported.
Protractor was marked end-of-life in August 2023 (see https://protractortest.org/). Projects still relying on Protractor should consider migrating to another E2E testing framework, several support solid migration paths from Protractor.

https://angular.dev/tools/cli/end-to-end
https://blog.angular.dev/the-state-of-end-to-end-testing-with-angular-d175f751cb9c

@angular-devkit/core

The deprecated fileBuffer function is no longer available. Update your code to use stringToFileBuffer instead to maintain compatibility.
Note: that this change does not affect application developers.

@angular/build

The @angular/localize/init polyfill will no longer be added automatically to projects. To prevent runtime issues, ensure that this polyfill is manually included in the "polyfills" section of your "angular.json" file if your application relies on Angular localization features.

@angular/ssr

The CommonEngine API now needs to be imported from @angular/ssr/node.
Before
import { CommonEngine } from '@angular/ssr';

After
import { CommonEngine } from '@angular/ssr/node';

@angular-devkit/schematics-cli

Commit
Type
Description

37693c40e
feat
add package manager option to blank schematic

@schematics/angular

Commit
Type
Description

a381a3db1
feat
add option to export component as default

755f3a07f
feat
add option to setup new workspace or application as zoneless mode

cfca5442e
feat
integrate withEventReplay() in provideClientHydration for new SSR apps

292a4b7c2
feat
update app-shell and ssr schematics to adopt new Server Rendering API

b1504c3bc
fix
component spec with export default

4b4e000dd
fix
don't show server routing prompt when using browser builder

4e2a5fe15
fix
enable opt-in for new @angular/ssr feature

fcf7443d6
fix
explicitly set standalone:false

7992218a9
fix
remove declaration and sourceMap from default tsconfig

9e6ab1bf2
fix
use default import for express

@angular/cli

Commit
Type
Description

201b60e1d
feat
handle string key/value pairs, e.g. --define

b847d4460
fix
recommend optional application update migration during v19 update

f249e7e85
perf
enable Node.js compile code cache when available

ecc107d83
perf
enable Node.js compile code cache when available

@angular-devkit/architect

Commit
Type
Description

78f76485f
feat
merge object options from CLI

@angular-devkit/build-angular

Commit
Type
Description

0a4ef3026
feat
karma-coverage w/ app builder

dcbdca85c
feat
karma+esbuild+watch

54594b5ab
feat
support karma with esbuild

ea5ae68da
fix
bring back style tags in browser builder

476f94f51
fix
fix --watch regression in karma

25d928b4f
fix
fix hanging terminal when browser-sync is not installed

2ec877dd0
fix
handle basename collisions

ab6e19e1f
fix
handle main field

43e7aae22
fix
remove double-watch in karma

1e37b5939
fix
serve assets

9d7613db9
fix
zone.js/testing + karma + esbuild

e40384e63
refactor
remove deprecated browserTarget

62877bdf2
refactor
remove Protractor builder and schematics

@angular-devkit/core

Commit
Type
Description

0d8a1006d
refactor
remove deprecated fileBuffer function in favor of stringToFileBuffer

@angular/build

Commit
Type
Description

b6951f448
feat
add sass to stylePreprocessorOptions in application builder

efb434136
feat
Auto-CSP support as a part of angular.json schema

816e3cb86
feat
enable component stylesheet hot replacement by default

3b00fc908
feat
introduce outputMode option to the application builder

7d883a152
feat
introduce ssr.experimentalPlatform option

c48d6947e
feat
set development/production condition

f63072668
feat
utilize ssr.entry during prerendering to enable access to local API routes

bbc290133
feat
utilize ssr.entry in Vite dev-server when available

5a7a2925b
fix
add missing redirect in SSR manifest

06e5176c2
fix
add warning when --prerendering or --app-shell are no-ops

ecaf870b5
fix
always clear dev-server error overlay on non-error result

f8677f6a9
fix
always record component style usage for HMR updates

099e477a8
fix
avoid hashing development external component stylesheets

3602bbb77
fix
avoid overwriting inline style bundling additional results

71534aadc
fix
check referenced files against native file paths

fed31e064
fix
correctly use dev-server hmr option to control stylesheet hot replacement

b86bb080e
fix
disable dev-server websocket when live reload is disabled

7c50ba9e2
fix
ensure index.csr.html is always generated when prerendering or SSR are enabled

efb2232df
fix
ensure accurate content size in server asset metadata

18a8584ea
fix
ensure SVG template URLs are considered templates with external stylesheets

7502fee28
fix
Exclude known --import from execArgv when spawning workers

2551df533
fix
fully disable component style HMR in JIT mode

c41529cc1
fix
handle APP_BASE_HREF correctly in prerendered routes

87a90afd4
fix
incomplete string escaping or encoding

1bb68ba68
fix
move lmdb to optionalDependencies

a995c8ea6
fix
prevent prerendering of catch-all routes

1654acf0f
fix
relax constraints on external stylesheet component id

0d4558ea5
fix
set ngServerMode during vite prebundling

55d7f01b6
fix
simplify disabling server features with --no-server via command line

cf0228b82
fix
skip wildcard routes from being listed as prerendered routes

af52fb49b
fix
synchronize import/export conditions between bundler and TypeScript

6c618d495
fix
update logic to support both internal and external SSR middlewares

bfa8fec9b
fix
use named export reqHandler for server.ts request handling

c8e1521a2
fix
workaround Vite CSS ShadowDOM hot replacement

d6a34034d
refactor
remove automatic addition of @angular/localize/init polyfill and related warnings

@angular/ssr

Commit
Type
Description

92209dd2e
feat
add createRequestHandler and createNodeRequestHandler utilities

41fb2ed86
feat
Add getHeaders Method to AngularAppEngine and AngularNodeAppEngine for handling pages static headers

f346ee8a8
feat
add isMainModule function

d66aaa3ca
feat
add server routing configuration API

bca568389
feat
dynamic route resolution using Angular router

30c25bf68
feat
export AngularAppEngine as public API

455b5700c
feat
expose writeResponseToNodeResponse and createWebRequestFromNodeRequest in public API

9692a9054
feat
improve handling of aborted requests in AngularServerApp

576ff604c
feat
introduce AngularNodeAppEngine API for Node.js integration

3c9697a8c
feat
introduce new hybrid rendering API

4b09887a9
feat
move CommonEngine API to /node entry-point

d43180af5
fix
add missing peer dependency on @angular/platform-server

74b3e2d51
fix
add validation to prevent use of provideServerRoutesConfig in browser context

2640bf7a6
fix
correct route extraction and error handling

44077f54e
fix
designate package as side-effect free

df4e1d360
fix
enable serving of prerendered pages in the App Engine

0793c78cf
fix
ensure wildcard RenderMode is applied when no Angular routes are defined

65b6e75a5
fix
export RESPONSE_INIT, REQUEST, and REQUEST_CONTEXT tokens

4ecf63a77
fix
export PrerenderFallback

50df63196
fix
improve handling of route mismatches between Angular server routes and Angular router

3cf7a5223
fix
initialize the DI tokens with null to avoid requiring them to be set to optional

85df4011b
fix
resolve bootstrap is not a function error

e9c9e4995
fix
resolve circular dependency issue from main.server.js reference in manifest

64c52521d
fix
show error when multiple routes are set with RenderMode.AppShell

280ebbda4
fix
support for HTTP/2 request/response handling

fb05e7f0a
fix
use wildcard server route configuration on the '/' route when the app router is empty

12ff37adb
perf
cache generated inline CSS for HTML

1d70e3b46
perf
cache resolved entry-points

f460b91d4
perf
integrate ETags for prerendered pages

e52ae7f6f
perf
prevent potential stampede in entry-points cache

angular/angular (@angular/animations)
v19.0.0
Compare Source
Breaking Changes
compiler

this.foo property reads no longer refer to template context variables. If you intended to read the template variable, do not use this..

core

Angular directives, components and pipes are now standalone by default.

Specify standalone: false for declarations that are currently declared in @NgModules.
ng update for v19 will take care of this automatically.

TypeScript versions less than 5.5 are no longer supported.

Timing changes for effect API (in developer preview):

effects which are triggered outside of change detection run as part of
the change detection process instead of as a microtask. Depending on the
specifics of application/test setup, this can result in them executing
earlier or later (or requiring additional test steps to trigger; see below
examples).

effects which are triggered during change detection (e.g. by input
signals) run earlier, before the component's template.

ExperimentalPendingTasks has been renamed to PendingTasks.

The autoDetect feature of ComponentFixture will now
attach the fixture to the ApplicationRef. As a result, errors during
automatic change detection of the fixture be reported to the ErrorHandler.
This change may cause custom error handlers to observe new failures that were previously unreported.

createComponent will now render default fallback with empty projectableNodes.

When passing an empty array to projectableNodes in the createComponent API, the default fallback content
of the ng-content will be rendered if present. To prevent rendering the default content, pass document.createTextNode('') as a projectableNode.

// The first ng-content will render the default fallback content if present
createComponent(MyComponent. { projectableNodes: [[], [secondNode]] });

// To prevent projecting the default fallback content:
createComponent(MyComponent. { projectableNodes: [[document.createTextNode('')], [secondNode]] });

Errors that are thrown during ApplicationRef.tick
will now be rethrown when using TestBed. These errors should be
resolved by ensuring the test environment is set up correctly to
complete change detection successfully. There are two alternatives to
catch the errors:

Instead of waiting for automatic change detection to happen, trigger
it synchronously and expect the error. For example, a jasmine test
could write expect(() => TestBed.inject(ApplicationRef).tick()).toThrow()
TestBed will reject any outstanding ComponentFixture.whenStable promises. A jasmine test,
for example, could write expectAsync(fixture.whenStable()).toBeRejected().

As a last resort, you can configure errors to not be rethrown by
setting rethrowApplicationErrors to false in TestBed.configureTestingModule.

The timers that are used for zone coalescing and hybrid
mode scheduling (which schedules an application state synchronization
when changes happen outside the Angular zone) will now run in the zone
above Angular rather than the root zone. This will mostly affect tests
which use fakeAsync: these timers will now be visible to fakeAsync
and can be affected by tick or flush.

The deprecated factories property in KeyValueDiffers has been removed.

elements

as part of switching away from custom CD behavior to the
hybrid scheduler, timing of change detection around custom elements has
changed subtly. These changes make elements more efficient, but can cause
tests which encoded assumptions about how or when elements would be checked
to require updating.

localize

The name option in the ng add @localize`` schematic has been removed in favor of the project option.

platform-browser

The deprecated BrowserModule.withServerTransition method has been removed. Please use the APP_ID DI token to set the application id instead.

router

The Router.errorHandler property has been removed.
Adding an error handler should be configured in either
withNavigationErrorHandler with provideRouter or the errorHandler
property in the extra options of RouterModule.forRoot. In addition,
the error handler cannot be used to change the return value of the
router navigation promise or prevent it from rejecting. Instead, if you
want to prevent the promise from rejecting, use resolveNavigationPromiseOnError.
The return type of the Resolve interface now includes
RedirectCommand.

common

Commit
Type
Description

24c6373820
feat
add optional rounded transform support in cloudinary image loader (#55364)

50f08e6c4b
feat
automatically use sizes auto in NgOptimizedImage (#57479)

13c13067bc
feat
disable keyvalue sorting using null compareFn (#57487)

compiler

Commit
Type
Description

a2e4ee0cb3
feat
add diagnostic for unused standalone imports (#57605)

0c9d721ac1
feat
add support for the typeof keyword in template expressions. (#58183)

09f589f000
fix
this.a should always refer to class property a (#55183)

98804fd4be
fix
add more specific matcher for hydrate never block (#58360)

b25121ee4a
fix
avoid having to duplicate core environment (#58444)

560282aa9b
fix
control flow nodes with root at the end projected incorrectly (#58607)

2be161d015
fix
fix :host parsing in pseudo-selectors (#58681)

806a61b5a6
fix
fix multiline selectors (#58681)

a3cb530d84
fix
handle typeof expressions in serializer (#58217)

ba4340875a
fix
ignore placeholder-only i18n messages (#58154)

e5d3abb298
fix
resolve :host:host-context(.foo) (#58681)

80f56954ce
fix
transform chained pseudo-selectors (#58681)

compiler-cli

Commit
Type
Description

d9687f43dd
feat
'strictStandalone' flag enforces standalone (#57935)

9e87593055
feat
ensure template style elements are preprocessed as inline styles (#57429)

231e6ff6ca
feat
generate the HMR replacement module (#58205)

dbe612f2cd
fix
disable standalone by default on older versions of Angular (#58405)

d4d76ead80
fix
do not fail fatal when references to non-existent module are discovered (#58515)

33fe252c58
fix
do not report unused declarations coming from an imported array (#57940)

fb44323c51
fix
incorrectly generating relative file paths on case-insensitive platforms (#58150)

22cd6869ef
fix
make the unused imports diagnostic easier to read (#58468)

9bbb01c85e
fix
report individual diagnostics for unused imports (#58589)

4716c3b966
perf
reduce duplicate component style resolution (#57502)

core

Commit
Type
Description

6ea8e1e9aa
feat
Add a schematics to migrate to standalone: false. (#57643)

3ebe6b4ad4
feat
Add async run method on ExperimentalPendingTasks (#56546)

69fc5ae922
feat
Add incremental hydration public api (#58249)

8ebbae88ca
feat
Add rxjs operator prevent app stability until an event (#56533)

19edf2c057
feat
add syntactic sugar for initializers (#53152)

c93b510f9b
feat
allow passing undefined without needing to include it in the type argument of input (#57621)

ab25a192ba
feat
allow running output migration on a subset of paths (#58299)

fc59e2a7b7
feat
change effect() execution timing & no-op allowSignalWrites (#57874)

8bcc663a53
feat
drop support for TypeScript 5.4 (#57577)

18d8d44b1f
feat
experimental resource() API for async dependencies (#58255)

9762b24b5e
feat
experimental impl of rxResource() (#58255)

6b8c494d05
feat
flipping the default value for standalone to true (#58169)

e6e5d29e83
feat
initial version of the output migration (#57604)

be2e49639b
feat
introduce afterRenderEffect (#57549)

ec386e7f12
feat
introduce debugName optional arg to framework signal functions (#57073)

8311f00faa
feat
introduce the reactive linkedSignal (#58189)

1b1519224d
feat
mark input, output and model APIs as stable (#57804)

a7eff3ffaa
feat
mark signal-based query APIs as stable (#57921)

a1f229850a
feat
migrate ExperimentalPendingTasks to PendingTasks (#57533)

3f1e7ab6ae
feat
promote outputFromObservable & outputToObservable to stable. (#58214)

97c44a1d6c
feat
Promote takeUntilDestroyed to stable. (#58200)

e5adf92965
feat
stabilize @let syntax (#57813)

b063468027
feat
support TypeScript 5.6 (#57424)

819ff034ce
feat
treat directives, pipes, components as  by default (#58229)

ee426c62f0
fix
allow signal write error (#57973)

c095679f92
fix
avoid breaking change with apps using rxjs 6.x (#58341)

71ee81af2c
fix
clean up event contract once hydration is done (#58174)

f03d274e87
fix
ComponentFixture autoDetect feature works like production (#55228)

950a5540f1
fix
Ensure the ViewContext is retained after closure minification (#57903)

7b1e5be20b
fix
fallback to default ng-content with empty projectable nodes. (#57480)

0300dd2e18
fix
Fix fixture.detectChanges with autoDetect disabled and zoneless (#57416)

5fe57d4fbb
fix
fixes issues with control flow and incremental hydration (#58644)

51933ef5a6
fix
prevent errors on contract cleanup (#58614)

fd7716440b
fix
Prevents trying to trigger incremental hydration on CSR (#58366)

656b5d3e78
fix
Re-assign error codes to be within core bounds (<1000) (#53455)

6e0af6dbbb
fix
resolve forward-referenced host directives during directive matching (#58492)

468d3fb9b1
fix
rethrow errors during ApplicationRef.tick in TestBed (#57200)

226a67dabb
fix
Schedulers run in zone above Angular rather than root (#57553)

97fb86d331
perf
set encapsulation to None for empty component styles (#57130)

c15ec36bd1
refactor
remove deprecated factories Property in KeyValueDiffers (#58064)

elements

Commit
Type
Description

fe5c4e086a
fix
support output()-shaped outputs (#57535)

0cebfd7462
fix
switch to ComponentRef.setInput & remove custom scheduler (#56728)

forms

Commit
Type
Description

[3e7d724037](https://redirect.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

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

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
(node:3434) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:3435) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:3422) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use `node --trace-deprecation ...` to show where the warning was created)
    Skipping migration for project angular-examples-cdk. Unable to determine 'tsconfig.json' file in workspace config.
    Skipping migration for project bacteria-game-remote-cdk. Unable to determine 'tsconfig.json' file in workspace config.
    Skipping migration for project fourier-analysis-remote-cdk. Unable to determine 'tsconfig.json' file in workspace config.
nx migrate [packageAndVersion]

Creates a migrations file or runs migrations from the migrations file.
  - Migrate packages and create migrations.json (e.g., nx migrate @nx/workspace@latest)
  - Run migrations (e.g., nx migrate --run-migrations=migrations.json). Use flag --if-exists to run migrations only if the migrations file exists.

Positionals:
  packageAndVersion  The target package and version (e.g, @nx/workspace@16.0.0).  [string]

Options:
      --help                      Show help  [boolean]
      --version                   Show version number  [boolean]
      --verbose                   Prints additional information about the commands (e.g., stack traces).  [boolean]
      --runMigrations             Execute migrations from a file (when the file isn't provided, execute migrations from migrations.json).  [string]
      --ifExists                  Run migrations only if the migrations file exists, if not continues successfully.  [boolean] [default: false]
      --from                      Use the provided versions for packages instead of the ones installed in node_modules (e.g., --from="@nx/react@16.0.0,@nx/js@16.0.0").  [string]
      --to                        Use the provided versions for packages instead of the ones calculated by the migrator (e.g., --to="@nx/react@16.0.0,@nx/js@16.0.0").  [string]
  -C, --createCommits             Automatically create a git commit after each migration runs.  [boolean] [default: false]
      --commitPrefix              Commit prefix to apply to the commit for each migration, when --create-commits is enabled.  [string] [default: "chore: [nx migration] "]
      --interactive               Enable prompts to confirm whether to collect optional package updates and migrations.  [boolean] [default: false]
      --excludeAppliedMigrations  Exclude migrations that should have been applied on previous updates. To be used with --from.  [boolean] [default: false]

Examples:
  migrate latest                                                           Update all Nx plugins to "latest". This will generate migrations.json
  migrate 9.0.0                                                            Update all Nx plugins to "9.0.0". This will generate migrations.json
  migrate<EMAIL_ADDRESS>--from="@nx/workspace@8.0.0<EMAIL_ADDRESS>Update @nx/workspace and generate the list of migrations starting with version 8.0.0 of @nx/workspace and @nx/node, regardless of what is installed locally
  migrate<EMAIL_ADDRESS>--to="@nx/react@9.0.1<EMAIL_ADDRESS>   Update @nx/workspace to "9.0.0". If it tries to update @nx/react or @nx/angular, use version "9.0.1"
  migrate<EMAIL_ADDRESS>                                         Update another-package to "12.0.0". This will update other packages and will generate migrations.json file
  migrate latest --interactive                                             Collect package updates and migrations in interactive mode. In this mode, the user will be prompted whether to apply any optional package update and migration
  migrate latest<EMAIL_ADDRESS>--exclude-applied-migrations             Collect package updates and migrations starting with version 14.5.0 of "nx" (and Nx first-party plugins), regardless of what is installed locally, while excluding migrations that should have been applied on previous updates
  migrate --run-migrations=migrations.json                                 Run migrations from the provided migrations.json file. You can modify migrations.json and run this command many times
  migrate --run-migrations --create-commits                                Create a dedicated commit for each successfully completed migration. You can customize the prefix used for each commit by additionally setting --commit-prefix="PREFIX_HERE "

Find more information and examples at https://nx.dev/nx/migrate

Error: Command failed: npx nx _migrate --run-migrations --if-exists
    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:888:11)
    at execSync (node:child_process:960:15)
    at runNxSync (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/utils/child-process.js:28:34)
    at runLocalMigrate (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/migrate.js:1057:39)
    at Object.runMigration (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/migrate.js:1080:9)
    at Object.handler (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/command-object.js:13:68) {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 3369,
  stdout: null,
  stderr: null
}
nx migrate [packageAndVersion]

Creates a migrations file or runs migrations from the migrations file.
  - Migrate packages and create migrations.json (e.g., nx migrate @nx/workspace@latest)
  - Run migrations (e.g., nx migrate --run-migrations=migrations.json). Use flag --if-exists to run migrations only if the migrations file exists.

Positionals:
  packageAndVersion  The target package and version (e.g, @nx/workspace@16.0.0).  [string]

Options:
      --help                      Show help  [boolean]
      --version                   Show version number  [boolean]
      --verbose                   Prints additional information about the commands (e.g., stack traces).  [boolean]
      --runMigrations             Execute migrations from a file (when the file isn't provided, execute migrations from migrations.json).  [string]
      --ifExists                  Run migrations only if the migrations file exists, if not continues successfully.  [boolean] [default: false]
      --from                      Use the provided versions for packages instead of the ones installed in node_modules (e.g., --from="@nx/react@16.0.0,@nx/js@16.0.0").  [string]
      --to                        Use the provided versions for packages instead of the ones calculated by the migrator (e.g., --to="@nx/react@16.0.0,@nx/js@16.0.0").  [string]
  -C, --createCommits             Automatically create a git commit after each migration runs.  [boolean] [default: false]
      --commitPrefix              Commit prefix to apply to the commit for each migration, when --create-commits is enabled.  [string] [default: "chore: [nx migration] "]
      --interactive               Enable prompts to confirm whether to collect optional package updates and migrations.  [boolean] [default: false]
      --excludeAppliedMigrations  Exclude migrations that should have been applied on previous updates. To be used with --from.  [boolean] [default: false]

Examples:
  migrate latest                                                           Update all Nx plugins to "latest". This will generate migrations.json
  migrate 9.0.0                                                            Update all Nx plugins to "9.0.0". This will generate migrations.json
  migrate<EMAIL_ADDRESS>--from="@nx/workspace@8.0.0<EMAIL_ADDRESS>Update @nx/workspace and generate the list of migrations starting with version 8.0.0 of @nx/workspace and @nx/node, regardless of what is installed locally
  migrate<EMAIL_ADDRESS>--to="@nx/react@9.0.1<EMAIL_ADDRESS>   Update @nx/workspace to "9.0.0". If it tries to update @nx/react or @nx/angular, use version "9.0.1"
  migrate<EMAIL_ADDRESS>                                         Update another-package to "12.0.0". This will update other packages and will generate migrations.json file
  migrate latest --interactive                                             Collect package updates and migrations in interactive mode. In this mode, the user will be prompted whether to apply any optional package update and migration
  migrate latest<EMAIL_ADDRESS>--exclude-applied-migrations             Collect package updates and migrations starting with version 14.5.0 of "nx" (and Nx first-party plugins), regardless of what is installed locally, while excluding migrations that should have been applied on previous updates
  migrate --run-migrations=migrations.json                                 Run migrations from the provided migrations.json file. You can modify migrations.json and run this command many times
  migrate --run-migrations --create-commits                                Create a dedicated commit for each successfully completed migration. You can customize the prefix used for each commit by additionally setting --commit-prefix="PREFIX_HERE "

Find more information and examples at https://nx.dev/nx/migrate

Error: Command failed: /tmp/tmp-3219-eEqjRLOob5N7/node_modules/.bin/nx _migrate --run-migrations --if-exists
    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:888:11)
    at execSync (node:child_process:960:15)
    at Object.runMigration (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/migrate.js:1073:42)
    at Object.handler (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/command-object.js:13:68) {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 3266,
  stdout: null,
  stderr: null
}

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
(node:4932) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:4921) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:4934) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use `node --trace-deprecation ...` to show where the warning was created)
    Cannot update project "angular-examples" to use the application builder. Only "@angular-devkit/build-angular:browser-esbuild" and "@angular-devkit/build-angular:browser" can be automatically migrated.
    Cannot update project "bacteria-game-remote" to use the application builder. Only "@angular-devkit/build-angular:browser-esbuild" and "@angular-devkit/build-angular:browser" can be automatically migrated.
    Cannot update project "fourier-analysis-remote" to use the application builder. Only "@angular-devkit/build-angular:browser-esbuild" and "@angular-devkit/build-angular:browser" can be automatically migrated.
    Cannot update project "rollapolla-analog" to use the application builder. Only "@angular-devkit/build-angular:browser-esbuild" and "@angular-devkit/build-angular:browser" can be automatically migrated.
    Cannot update project "shader-examples-remote" to use the application builder. Only "@angular-devkit/build-angular:browser-esbuild" and "@angular-devkit/build-angular:browser" can be automatically migrated.
nx migrate [packageAndVersion]

Creates a migrations file or runs migrations from the migrations file.
  - Migrate packages and create migrations.json (e.g., nx migrate @nx/workspace@latest)
  - Run migrations (e.g., nx migrate --run-migrations=migrations.json). Use flag --if-exists to run migrations only if the migrations file exists.

Positionals:
  packageAndVersion  The target package and version (e.g, @nx/workspace@16.0.0).  [string]

Options:
      --help                      Show help  [boolean]
      --version                   Show version number  [boolean]
      --verbose                   Prints additional information about the commands (e.g., stack traces).  [boolean]
      --runMigrations             Execute migrations from a file (when the file isn't provided, execute migrations from migrations.json).  [string]
      --ifExists                  Run migrations only if the migrations file exists, if not continues successfully.  [boolean] [default: false]
      --from                      Use the provided versions for packages instead of the ones installed in node_modules (e.g., --from="@nx/react@16.0.0,@nx/js@16.0.0").  [string]
      --to                        Use the provided versions for packages instead of the ones calculated by the migrator (e.g., --to="@nx/react@16.0.0,@nx/js@16.0.0").  [string]
  -C, --createCommits             Automatically create a git commit after each migration runs.  [boolean] [default: false]
      --commitPrefix              Commit prefix to apply to the commit for each migration, when --create-commits is enabled.  [string] [default: "chore: [nx migration] "]
      --interactive               Enable prompts to confirm whether to collect optional package updates and migrations.  [boolean] [default: false]
      --excludeAppliedMigrations  Exclude migrations that should have been applied on previous updates. To be used with --from.  [boolean] [default: false]

Examples:
  migrate latest                                                           Update all Nx plugins to "latest". This will generate migrations.json
  migrate 9.0.0                                                            Update all Nx plugins to "9.0.0". This will generate migrations.json
  migrate<EMAIL_ADDRESS>--from="@nx/workspace@8.0.0<EMAIL_ADDRESS>Update @nx/workspace and generate the list of migrations starting with version 8.0.0 of @nx/workspace and @nx/node, regardless of what is installed locally
  migrate<EMAIL_ADDRESS>--to="@nx/react@9.0.1<EMAIL_ADDRESS>   Update @nx/workspace to "9.0.0". If it tries to update @nx/react or @nx/angular, use version "9.0.1"
  migrate<EMAIL_ADDRESS>                                         Update another-package to "12.0.0". This will update other packages and will generate migrations.json file
  migrate latest --interactive                                             Collect package updates and migrations in interactive mode. In this mode, the user will be prompted whether to apply any optional package update and migration
  migrate latest<EMAIL_ADDRESS>--exclude-applied-migrations             Collect package updates and migrations starting with version 14.5.0 of "nx" (and Nx first-party plugins), regardless of what is installed locally, while excluding migrations that should have been applied on previous updates
  migrate --run-migrations=migrations.json                                 Run migrations from the provided migrations.json file. You can modify migrations.json and run this command many times
  migrate --run-migrations --create-commits                                Create a dedicated commit for each successfully completed migration. You can customize the prefix used for each commit by additionally setting --commit-prefix="PREFIX_HERE "

Find more information and examples at https://nx.dev/nx/migrate

Error: Command failed: npx nx _migrate --run-migrations --if-exists
    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:888:11)
    at execSync (node:child_process:960:15)
    at runNxSync (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/utils/child-process.js:28:34)
    at runLocalMigrate (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/migrate.js:1057:39)
    at Object.runMigration (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/migrate.js:1080:9)
    at Object.handler (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/command-object.js:13:68) {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 4868,
  stdout: null,
  stderr: null
}
nx migrate [packageAndVersion]

Creates a migrations file or runs migrations from the migrations file.
  - Migrate packages and create migrations.json (e.g., nx migrate @nx/workspace@latest)
  - Run migrations (e.g., nx migrate --run-migrations=migrations.json). Use flag --if-exists to run migrations only if the migrations file exists.

Positionals:
  packageAndVersion  The target package and version (e.g, @nx/workspace@16.0.0).  [string]

Options:
      --help                      Show help  [boolean]
      --version                   Show version number  [boolean]
      --verbose                   Prints additional information about the commands (e.g., stack traces).  [boolean]
      --runMigrations             Execute migrations from a file (when the file isn't provided, execute migrations from migrations.json).  [string]
      --ifExists                  Run migrations only if the migrations file exists, if not continues successfully.  [boolean] [default: false]
      --from                      Use the provided versions for packages instead of the ones installed in node_modules (e.g., --from="@nx/react@16.0.0,@nx/js@16.0.0").  [string]
      --to                        Use the provided versions for packages instead of the ones calculated by the migrator (e.g., --to="@nx/react@16.0.0,@nx/js@16.0.0").  [string]
  -C, --createCommits             Automatically create a git commit after each migration runs.  [boolean] [default: false]
      --commitPrefix              Commit prefix to apply to the commit for each migration, when --create-commits is enabled.  [string] [default: "chore: [nx migration] "]
      --interactive               Enable prompts to confirm whether to collect optional package updates and migrations.  [boolean] [default: false]
      --excludeAppliedMigrations  Exclude migrations that should have been applied on previous updates. To be used with --from.  [boolean] [default: false]

Examples:
  migrate latest                                                           Update all Nx plugins to "latest". This will generate migrations.json
  migrate 9.0.0                                                            Update all Nx plugins to "9.0.0". This will generate migrations.json
  migrate<EMAIL_ADDRESS>--from="@nx/workspace@8.0.0<EMAIL_ADDRESS>Update @nx/workspace and generate the list of migrations starting with version 8.0.0 of @nx/workspace and @nx/node, regardless of what is installed locally
  migrate<EMAIL_ADDRESS>--to="@nx/react@9.0.1<EMAIL_ADDRESS>   Update @nx/workspace to "9.0.0". If it tries to update @nx/react or @nx/angular, use version "9.0.1"
  migrate<EMAIL_ADDRESS>                                         Update another-package to "12.0.0". This will update other packages and will generate migrations.json file
  migrate latest --interactive                                             Collect package updates and migrations in interactive mode. In this mode, the user will be prompted whether to apply any optional package update and migration
  migrate latest<EMAIL_ADDRESS>--exclude-applied-migrations             Collect package updates and migrations starting with version 14.5.0 of "nx" (and Nx first-party plugins), regardless of what is installed locally, while excluding migrations that should have been applied on previous updates
  migrate --run-migrations=migrations.json                                 Run migrations from the provided migrations.json file. You can modify migrations.json and run this command many times
  migrate --run-migrations --create-commits                                Create a dedicated commit for each successfully completed migration. You can customize the prefix used for each commit by additionally setting --commit-prefix="PREFIX_HERE "

Find more information and examples at https://nx.dev/nx/migrate

Error: Command failed: /tmp/tmp-4717-468FeWXLDTrt/node_modules/.bin/nx _migrate --run-migrations --if-exists
    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:888:11)
    at execSync (node:child_process:960:15)
    at Object.runMigration (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/migrate.js:1073:42)
    at Object.handler (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/command-object.js:13:68) {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 4764,
  stdout: null,
  stderr: null
}

File name: package.json
Command failed: npx --no-install nx run-many --target=lint --all --parallel --fix
(node:6728) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use `node --trace-deprecation ...` to show where the warning was created)

File name: package.json
Command failed: npx --no-install nx run-many --target=lint --all --parallel --fix

File name: package.json
Command failed: npx --no-install nx migrate --run-migrations --if-exists
    Skipping migration for project angular-examples-cdk. Unable to determine 'tsconfig.json' file in workspace config.
    Skipping migration for project bacteria-game-remote-cdk. Unable to determine 'tsconfig.json' file in workspace config.
    Skipping migration for project fourier-analysis-remote-cdk. Unable to determine 'tsconfig.json' file in workspace config.
nx migrate [packageAndVersion]

Creates a migrations file or runs migrations from the migrations file.
  - Migrate packages and create migrations.json (e.g., nx migrate @nx/workspace@latest)
  - Run migrations (e.g., nx migrate --run-migrations=migrations.json). Use flag --if-exists to run migrations only if the migrations file exists.

Positionals:
  packageAndVersion  The target package and version (e.g, @nx/workspace@16.0.0).  [string]

Options:
      --help                      Show help  [boolean]
      --version                   Show version number  [boolean]
      --verbose                   Prints additional information about the commands (e.g., stack traces).  [boolean]
      --runMigrations             Execute migrations from a file (when the file isn't provided, execute migrations from migrations.json).  [string]
      --ifExists                  Run migrations only if the migrations file exists, if not continues successfully.  [boolean] [default: false]
      --from                      Use the provided versions for packages instead of the ones installed in node_modules (e.g., --from="@nx/react@16.0.0,@nx/js@16.0.0").  [string]
      --to                        Use the provided versions for packages instead of the ones calculated by the migrator (e.g., --to="@nx/react@16.0.0,@nx/js@16.0.0").  [string]
  -C, --createCommits             Automatically create a git commit after each migration runs.  [boolean] [default: false]
      --commitPrefix              Commit prefix to apply to the commit for each migration, when --create-commits is enabled.  [string] [default: "chore: [nx migration] "]
      --interactive               Enable prompts to confirm whether to collect optional package updates and migrations.  [boolean] [default: false]
      --excludeAppliedMigrations  Exclude migrations that should have been applied on previous updates. To be used with --from.  [boolean] [default: false]

Examples:
  migrate latest                                                           Update all Nx plugins to "latest". This will generate migrations.json
  migrate 9.0.0                                                            Update all Nx plugins to "9.0.0". This will generate migrations.json
  migrate<EMAIL_ADDRESS>--from="@nx/workspace@8.0.0<EMAIL_ADDRESS>Update @nx/workspace and generate the list of migrations starting with version 8.0.0 of @nx/workspace and @nx/node, regardless of what is installed locally
  migrate<EMAIL_ADDRESS>--to="@nx/react@9.0.1<EMAIL_ADDRESS>   Update @nx/workspace to "9.0.0". If it tries to update @nx/react or @nx/angular, use version "9.0.1"
  migrate<EMAIL_ADDRESS>                                         Update another-package to "12.0.0". This will update other packages and will generate migrations.json file
  migrate latest --interactive                                             Collect package updates and migrations in interactive mode. In this mode, the user will be prompted whether to apply any optional package update and migration
  migrate latest<EMAIL_ADDRESS>--exclude-applied-migrations             Collect package updates and migrations starting with version 14.5.0 of "nx" (and Nx first-party plugins), regardless of what is installed locally, while excluding migrations that should have been applied on previous updates
  migrate --run-migrations=migrations.json                                 Run migrations from the provided migrations.json file. You can modify migrations.json and run this command many times
  migrate --run-migrations --create-commits                                Create a dedicated commit for each successfully completed migration. You can customize the prefix used for each commit by additionally setting --commit-prefix="PREFIX_HERE "

Find more information and examples at https://nx.dev/nx/migrate

Error: Command failed: npx nx _migrate --run-migrations --if-exists
    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:888:11)
    at execSync (node:child_process:960:15)
    at runNxSync (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/utils/child-process.js:28:34)
    at runLocalMigrate (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/migrate.js:1057:39)
    at Object.runMigration (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/migrate.js:1080:9)
    at Object.handler (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/command-object.js:13:68) {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 9605,
  stdout: null,
  stderr: null
}
nx migrate [packageAndVersion]

Creates a migrations file or runs migrations from the migrations file.
  - Migrate packages and create migrations.json (e.g., nx migrate @nx/workspace@latest)
  - Run migrations (e.g., nx migrate --run-migrations=migrations.json). Use flag --if-exists to run migrations only if the migrations file exists.

Positionals:
  packageAndVersion  The target package and version (e.g, @nx/workspace@16.0.0).  [string]

Options:
      --help                      Show help  [boolean]
      --version                   Show version number  [boolean]
      --verbose                   Prints additional information about the commands (e.g., stack traces).  [boolean]
      --runMigrations             Execute migrations from a file (when the file isn't provided, execute migrations from migrations.json).  [string]
      --ifExists                  Run migrations only if the migrations file exists, if not continues successfully.  [boolean] [default: false]
      --from                      Use the provided versions for packages instead of the ones installed in node_modules (e.g., --from="@nx/react@16.0.0,@nx/js@16.0.0").  [string]
      --to                        Use the provided versions for packages instead of the ones calculated by the migrator (e.g., --to="@nx/react@16.0.0,@nx/js@16.0.0").  [string]
  -C, --createCommits             Automatically create a git commit after each migration runs.  [boolean] [default: false]
      --commitPrefix              Commit prefix to apply to the commit for each migration, when --create-commits is enabled.  [string] [default: "chore: [nx migration] "]
      --interactive               Enable prompts to confirm whether to collect optional package updates and migrations.  [boolean] [default: false]
      --excludeAppliedMigrations  Exclude migrations that should have been applied on previous updates. To be used with --from.  [boolean] [default: false]

Examples:
  migrate latest                                                           Update all Nx plugins to "latest". This will generate migrations.json
  migrate 9.0.0                                                            Update all Nx plugins to "9.0.0". This will generate migrations.json
  migrate<EMAIL_ADDRESS>--from="@nx/workspace@8.0.0<EMAIL_ADDRESS>Update @nx/workspace and generate the list of migrations starting with version 8.0.0 of @nx/workspace and @nx/node, regardless of what is installed locally
  migrate<EMAIL_ADDRESS>--to="@nx/react@9.0.1<EMAIL_ADDRESS>   Update @nx/workspace to "9.0.0". If it tries to update @nx/react or @nx/angular, use version "9.0.1"
  migrate<EMAIL_ADDRESS>                                         Update another-package to "12.0.0". This will update other packages and will generate migrations.json file
  migrate latest --interactive                                             Collect package updates and migrations in interactive mode. In this mode, the user will be prompted whether to apply any optional package update and migration
  migrate latest<EMAIL_ADDRESS>--exclude-applied-migrations             Collect package updates and migrations starting with version 14.5.0 of "nx" (and Nx first-party plugins), regardless of what is installed locally, while excluding migrations that should have been applied on previous updates
  migrate --run-migrations=migrations.json                                 Run migrations from the provided migrations.json file. You can modify migrations.json and run this command many times
  migrate --run-migrations --create-commits                                Create a dedicated commit for each successfully completed migration. You can customize the prefix used for each commit by additionally setting --commit-prefix="PREFIX_HERE "

Find more information and examples at https://nx.dev/nx/migrate

Error: Command failed: /tmp/tmp-9455-Kn0SVTBfNpAf/node_modules/.bin/nx _migrate --run-migrations --if-exists
    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:888:11)
    at execSync (node:child_process:960:15)
    at Object.runMigration (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/migrate.js:1073:42)
    at Object.handler (/tmp/renovate/repos/github/WolfSoko/wol-sok-mono/node_modules/nx/src/command-line/migrate/command-object.js:13:68) {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 9502,
  stdout: null,
  stderr: null
}

File name: package.json
Command failed: npx --no-install nx run-many --target=lint --all --parallel --fix


feat: Support multiple clients in the same process

What type of pull request is this?

[x] Non-breaking code change
[ ] Breaking code change
[ ] Documentation change/addition
[ ] Tests change

Description

This PR potentially fixes #290. It achieves this by making all objects that callback subclass a CallbackObject which allows the binding to be passed during initialisation. The client now also stores a copy of CallbackObject rather than modifying the original, resolving the problem where clients were overwriting eachothers callbacks.
A known issue with this solution is Tasks. Tasks dont hook themselves into the client, and are instead just methods that get called periodically by asyncio. Due to this, they cannot be bound in the same way as other callbacks, such as commands and listeners. The only solutions I can come up with for this, would be breaking, which the PR goes out of its way to attempt to avoid. As such they have not been modified
Changes

Impliment CallbackObject
Make Listner, Command, PrefixedCommand subclass CallbackObject
Use CallbackObject binding rather than wrap_partial

Checklist

[x] I've formatted my code with Black
[x] I've ensured my code works on Python 3.10.x
[x] I've tested my code

Regarding Tasks, if you choose to use tasks and mutliple clients in one process, you will need to move your tasks to an extension to ensure correct binding


Codecs package

I think I've gotten this to the level that I am willing to PR this, at any case.
For text encodings, I have tried to implement all WHATWG encodings, plus some more, partly though not entirely to attain near‑parity with the labels for text encodings supported by Python (though ISO-2022-CN, ISO-2022-CN-EXT and IBM-1364 are additional to that). The text encodings not supported are unicode-escape, raw-unicode-escape, idna and punycode (while Punycode may be important for URLs, it is very confusing and I have no real motivation to try to understand it). Additionally, x-mac-korean and x-mac-japanese labels are not supported (Python recognises them, but only as aliases to euc-kr and shift_jis respectively).
I have generally tried to follow WHATWG where applicable, but deviating in places where strictly following WHATWG seemed non-sensible for a non-browser (e.g. I'm allowing encoding to HKSCS when the HKSCS label is used) or otherwise inconsistent (e.g. I'm pedantising nil-effect escape sequences (not only adjacent ones) in ISO-2022-JP, and excluding the HKSCS additions following, not only preceding, the Big5-ETEN range when encoding to Big5). This does mean the behaviour for certain labels is not exactly the same as Python's; for instance, shift_jis, ms-kanji and windows-31j all refer to the Microsoft version per WHATWG, as opposed to Python associating them with the UTC mapping, Microsoft version and nothing, respectively. For the most part, the WHATWG behaviour is more sensible in practice, given the behaviour of other, non-Python, implementations.
This does not quite exactly match Python in API respects either, in that (for example) the registration of codec lookup is very different as a differing design decision, there is no support for stream readers / stream writers (yet), and the .encode and .decode methods on strings are not changed (the existing ones are actually used, on valid substrings, by the UTF-8 codec). But when just using codecs.encode and codecs.decode, or even codecs.lookup to get incremental classes, and not making any assumptions about the object returned/accepted by getstate/setstate, it should match Python behaviour in API terms.
Binary-to-text encodings (namely Base64 and Quoted-Printable, and a "Base64UU" which is used in chunks by uuencode, but is not itself uuencode) I have actually implemented with backward semantics (and prefixed labels with inverse-): being created with decode and parsed with encode, so as to try and allow decode to be consistently bytes→str and encode to be consistently str→bytes. Python actually had some problems with its less type-consistent approach causing problems in contexts where externally supplied encoding labels may occur, eventually having to explicitly mark codecs that were not text encodings (e.g. were binary-to-text or compression codecs) to exclude them from the string-method/bytes-method versions of encode and decode, so I think this is somewhat justified, despite being in some ways more confusing. That being said, the jury is still out to a certain extent since they tend to ignore the error mode in favour of just raising the exception, since a binary-to-text encoding cannot necessarily recover from an unrecognised or invalid sequences in the same way that a text encoding can.

I think it might be best to not commit the generated files, as they amount to a few megabytes of space and the generator isn't as slow as it was earlier in the project - dbdata takes about 7 seconds (we have a test suite that takes longer), sbencs is under 1s.
I'd also like to squash the branch before merging.

I believe Github has an enablable feature to squash-merge PRs, which tends to be cleaner than trying to squash them before merging in my experience.

Yes, it's an option I have in the merge menu.

Right, so with the generated files excluded, that saves 3.0 MiB from dbdata.krk and a much smaller 85.9 KiB from sbencs.krk.
It is worth noting that if I drop ISO-2022-CN-EXT, I could save a further 1.3 MiB (that would involve deleting dbextra_data_7bit_cnext.krk, and line 8 and lines 1263–1280 from dbextra.krk). I had included it for completeness; however, ISO-2022-CN-EXT is often left unsupported due to being rarely used and requiring a quite large number of mapping tables compared to the other 7-bit ISO 2022 profiles, hence I've kept the tables which only ISO-2022-CN-EXT uses in a separate file.


Transformer encoder API + get_model API + BERT

Description
This PR contains the following changes related to transformer, and they are ready for review:

expose transformer encoder related APIs as public APIs
include pre-trained transformer model in the get_model API
refactor transformer building blocks,  such that they can be reused for BERT

This PR also contains WIP changes for BERT, including:

BERT building blocks
TSVDataset and BERT data preprocessing script
BERT fine-tuning script

Checklist
Essentials

[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@sxjscience @szhengac @leezu @cgraywang @szha

I would recommend splitting this pr into multiple ones. The current pr looks too cumbersome to maintain.

LGTM. Currently there's some problems with the doctest. I'll approve once that's fixed.

Also, we need to make sure that the existing pretrained model can be loaded and perform the testing correctly.

Job PR-409/22 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-409/22/index.html

@szhengac Yes. I loaded the same model in the transformer notebook for inference and got exactly the same loss and bleu score.

Job PR-409/27 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-409/27/index.html


Unexpected behavior with image slider on iPad (iOS 7 & 8)

On iOS 7 & 8 tablet devices, the slider seems to load successfully but then displays undesired behavior after some number of slides. Live examples: https://discoverymap.com/mad-river-valley-vt and https://discoverymap.com/coastal-new-brunswick-canada

[  http://jsfiddle.net/n63co3pt/  ]
use this jsfiddle to reproduce your bug:
http://jsfiddle.net/n63co3pt/
we will likely close your issue without it.

Steps to reproduce the problem

Create slider with image assets, as above
Load in IOS browser
Watch for weird display behavior

What is the expected behaviour?
Expected: slider works as it does on Android Chrome and desktop.

What is observed behaviour?
After some number of slides (three, in the case of https://www.discoverymap.com/mad-river-valley-vt), a large empty space appears below the slider, pushing additiona conetnt further down the page.

More Details

iOS 7 & 8 tablets
jQuery 1.11, Slick 1.4 and 1.6

I am also seeing a similar issue isolated to iOS devices (iOS 10) but in my case it seems to push everything up off the page out of view.

Did anyone ever find a fix for this?

Any updates on this?

Any updates on this? I'm having the same problem. (ios 12.5.4 and ios14)


Program terminated due to an unrecoverable SEH exception

When running the pre-relaese version 2.37.0 I encountered the following exception.

librealsense
2.37.0 RELEASE

OS
Windows

Intel RealSense Viewer / Depth Quality Tool has crashed with the following error message:

Program terminated due to an unrecoverable SEH exception:
Illegal CPU instruction!
Possibly newer CPU architecture is required

DEV1.txt

Hi @gmaajid   Your kindly provided log has the following details about your computer's CPU:
Intel Core i7 3930K
Sandy Bridge-E
Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz
Sandy Bridge-E architecture is very old, being launched in late 2011.  Even the original RealSense camera in 2014 required a Haswell CPU that was 2 architecture generations newer than Sandy Bridge.  (Sandy Bridge > Ivy Bridge > Haswell).  Although RealSense 400 Series cameras (if that is what you are using) are meant to work with any Intel CPU, there may be a limit to that in terms of processors that are excessively aged.
Have you been able to successfully run the RealSense Viewer on any previous RealSense SDK versions such as the slightly older 2.36.0 (which is a stable version of the RealSense SDK rather than a pre-release).
https://github.com/IntelRealSense/librealsense/releases/tag/v2.36.0

Here is some data on CPU requirements -

RealSense Viewer bundled inside SDK installer requires Skylake architecture CPU (since it includes OpenVINO and OpenVINO requires AVX instruction set)
Rest of the SDK, including depth quality tool or the standalone viewer you can download from the site should work on more or less any x86 and Arm CPUs, just slower. Another factor is OpenGL 3.0 and GLSL 1.3 compatibility via graphics driver.

I tried 2.36.0  and got the same exception. I can't use an older build since I'm working with the L515 Lidar sensor and I don't think it's supported by older SDKs.
Thanks for the information. I'll try a machine with a newer CPU when using the RealSense Viewer. It's good to know the rest of the SDK should function on older machines.
I'll close this issue since this issue is expected behavior.

Hi @gmaajid
Please let us know if you were able to run standalone viewer and feel free to reopen / open new issue if you encounter any problem

I think a lot of people have these problems. Six year old i7 CPUs run just fine and this specific CPU generation requirement isn't listed anywhere as far as I can tell. You should seriously consider only loading the OpenVINO component if requirements are met and or show a more appropriate message and update the requirements for the SDK.


Start a request (from the website) page

Adding as this is something we've discussed wanted to deliver, but don't have down in issues.
As we know, this page can functionally be similar to the plugin and request pages. However, there might be some significant UI differences. My concern for this page is how we handle things if the paper / dataset is already availiable.

Would the the request from the website require a users email address? Is the Button capable of having a request submitted through a form, searched, and then emailed that day if it is indeed available? I'm not sure how the tech works for the request on the website.

Simply, yes, it is now.
On Sun, 9 Oct 2016 at 19:49 chealsye<EMAIL_ADDRESS>wrote:

Would the the request from the website require a users email address? Is
the Button capable of having a request submitted through a form, searched,
and then emailed that day if it is indeed available? I'm not sure how the
tech works for the request on the website.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OAButton/backend/issues/268#issuecomment-252504628,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEuWZ2XYCc4-yvFKlpt7rScXx3EgPgLzks5qyTc_gaJpZM4KOsOj
.

I don't think there is particular copy needed for this, is there? There is a functional new request page now, and I will add to it a check to see if already available or already requested, and where either is true, a statement saying so with a redirect link is all that is needed.

I imagine some copy on what a request is on this page might be helpful, as well as supporting copy with the text entry fields to ensure we're getting good data.

OK, that can be added to the new request page at any time.
On Mon, Oct 10, 2016 at 1:26 PM, Joseph McArthur<EMAIL_ADDRESS>wrote:

I imagine some copy on what a request is on this page might be helpful, as
well as supporting copy with the text entry fields to ensure we're getting
good data.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/OAButton/backend/issues/268#issuecomment-252604105,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAuXCBNQraEzYuHg3NFTu97UeMidAgznks5qyi78gaJpZM4KOsOj
.

The request via the website pages currently look like this:

These are my suggestions - bring down the boxes from the top bar, use a more neutral color, new copy:

If it is possible to allow users to sign up without needing to click through to another page. If not then just remove email and send them to the sign up page.


build(scan): enable trivy scan ingestion-base

Enable trivy scan ingestion-base
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Created different PR for that https://github.com/datahub-project/datahub/pull/7390. Merging this.


Card should render when a browser autocompletes the credit card

when I use browser autocomplete, card number can not format.

This is indeed a bug that should be fixed!

Is this possibly related to my recent post (https://github.com/jessepollak/card/issues/245) about losing the rendered image when the form validation fail and the page reloads? When the validation fails and the page reloads the values are still input into the fields but the card isn't re-rendered until a key press is detected.
Is there a way to force the image to reload from JS when the page is reloaded via ajax?


Preload integrations

This may/may not be feasible. If this slows things down too much, then it probably isn't the best idea.
Whatever is done, this would probably need to be done in a webworker, or at the very least async.

First answer here http://stackoverflow.com/questions/4891029/preload-iframe

This may be even better http://www.aaronpeters.nl/blog/iframe-loading-techniques-performance?>

To note, this could be done for only the iframes initially in view, or directly after a search is performed. This way, the likely targets will be preloaded.


Error on reading permissions when using docker v3.0.0

Issue
I received the following error when watching local file changes while running under docker v3.0.0:
Exception in thread Thread-1:
Traceback (most recent call last):
  File "c:\anwendungen\python36-32\lib\threading.py", line 916, in _bootstrap_inner
    self.run()
  File "c:\anwendungen\python36-32\lib\site-packages\watchdog\observers\api.py", line 199, in run
    self.dispatch_events(self.event_queue, self.timeout)
  File "c:\anwendungen\python36-32\lib\site-packages\watchdog\observers\api.py", line 368, in dispatch_events
    handler.dispatch(event)
  File "c:\anwendungen\python36-32\lib\site-packages\watchdog\events.py", line 454, in dispatch
    _method_map[event_type](event)
  File "c:\anwendungen\python36-32\lib\site-packages\docker_volume_watcher\container_notifier.py", line 49, in __change_handler
    self.notify(absolute_path)
  File "c:\anwendungen\python36-32\lib\site-packages\docker_volume_watcher\container_notifier.py", line 66, in notify
    permissions = permissions.decode('utf-8').strip()
AttributeError: 'ExecResult' object has no attribute 'decode'

Docker version (pip show docker):
Name: docker
Version: 3.0.0
Summary: A Python library for the Docker Engine API.
Home-page: https://github.com/docker/docker-py
Author: Joffrey F
Author-email<EMAIL_ADDRESS>License: Apache License 2.0
Location: c:\anwendungen\python36-32\lib\site-packages
Requires: websocket-client, pypiwin32, docker-pycreds, six, requests

Solution
Calling output on permissions solves the issue for docker >=3.0.0.
docker_volume_watcher (https://github.com/merofeev/docker-windows-volume-watcher/blob/master/docker_volume_watcher/container_notifier.py#L66)
...
 permissions = self.container.exec_run(
                ['stat', '-c', '%a', absolute_path], privileged=True)
            permissions = permissions.output.decode('utf-8').strip()
            response = self.container.exec_run(
                ['chmod', permissions, absolute_path], privileged=True)
...

The cause seems to be that the output of exec_run changed to an ExecResult instead of a string with the version bump to 3.0.0: https://github.com/docker/docker-py/blob/05d34ed1fbaa8233a4cf51a0f52b67aef99a9521/docker/models/containers.py#L129.
Ideally, permissions is checked for its type before calling decode on it.

@merofeev I created this issue with @RolandMay and just noticed that it is a duplicate of #8. Let me know if we can help by creating a PR.

Hi @ArneZsng , @RolandMay !
Thanks for suggesting the solution and sorry for delay with response (I'm currently on vacation).
If you could contribute PR, this will be great! If you decide to do it let me suggest a few things:

To avoid type checking of value returned by exec_run we can set minimum version of docker package to 3.0.0 in both requirements.txt and setup.py
I think we also should check exit code returned by exec_run and show some warning message to user in case we failed to execute chmod or stat

Should be fixed by #10


Integration of ros_maps_to_pedsim for ROS map conversion

This PR addresses #38 and follows from the discussion there.

added the package ros_maps_to_pedsim as submodule in 3rdparty,
added a reference to the package in the README.md
added an extra ROS param to sim_visualizer to change wall_marker_scale. The default of the wall_marker_scale param is left to 1.0m for compatibility with the rest of the codebase.

This is cool, over in my fork, I have a simple executable to convert pedsim scenario files into ros png/yaml files.
This is even better since writing the scenario files are harder than creating maps! :-) :+1:


"Wrong answer" error in Jupyter cells lesson of Data Analysis with Python course

The correct answer for the question: Which cells are responsible for rich display? is Markdown Cells.
But it erroneously accepts "Code Cells" as the correct answer.
To reproduce the bug, go to below link and select the correct answer to the question.
link

From https://readthedocs.org/projects/jupyter-notebook/downloads/pdf/latest/:
Code cells:
... The output is not limited to text, with many other possible forms of output are also possible, including matplotlib figures and HTML tables(as used, for example, in the pandas data analysis package). This is known as IPython’s rich display capability
Markdown cells:
You can document the computational process in a literate way, alternating descriptive text with code, using rich text ...
I watched the video at 2x and I didn't hear a mention of 'rich display' or 'rich text' - although, I may have just missed it.
By the definitions above, code cells sort of seems correct? but I am guessing that markdown has more capabilities for display - I'm not sure - and I'm not sure of the question creators intention here. The video does mention that markdown is used to make it look "pretty". Perhaps we could change the question to "What type of cells are used to make your reports look pretty?" and then use markdown as the answer.

I am not a fan of this question at all. What about changing it to be:

What are the three main types of Jupyter Notebook Cell?

A - Code, MarkDown, and Python
B - Code, MarkDown, and Raw
C - MarkDown, Python, and Raw

I'm fine with that @Sky020. What do you think @yaseen221?

But I think the correct answer to that question(rich text) should be Markdown Cells.

To clarify, the question asks about rich display, not rich text. Which, according to what Tom quoted, would be code cells.
That being said, I completely agree that there's too much room for confusion here. For now, I suggest moving forward with @ShaunSHamilton's approach. Because this is a text change, I'll go ahead and open it up to first timers.

Can I work on this?
Since this is first time I'm contributing. Can you please help me?
Do I need to change the question and options like this?

What are the three main types of Jupyter Notebook Cell?

A - Code, MarkDown, and Python
B - Code, MarkDown, and Raw
C - MarkDown, Python, and Raw

Do I need to change the question and options like this?

@GJ-16 Yes, the questions here: https://github.com/freeCodeCamp/freeCodeCamp/blob/master/curriculum/challenges/english/08-data-analysis-with-python/data-analysis-with-python-course/jupyter-notebooks-cells.md
Need to be changed to the above. Be sure to read the Contributors Docs, if you have not already 👍

I'm a first time contributor as well. Can I modify it please? @GJ-16

Actually i started.


Loader need to cache paused container

See https://github.com/microsoft/FluidFramework/blob/master/packages/loader/container-loader/src/loader.ts#L290
While container that is never resumed should not be cached, today's mainstream scenarios all start with paused container, and later on it is unpaused. We do not reuse such container in copy/paste scenarios today, which results in substantial hit in perf (loading another instance of same thing).
More info in this discussion

Closing because this seems the same as #4489

Closing because this seems the same as #4489


Ensure constraint_and_index_reconstructor is actually called

constraint_and_index_reconstructor was not used correctly in
import_measures, because although it was called and yielded, the result
was never iterated over.  This PR changes it to be called and used as a
context manager, which was the original intention.
Although this code is exercised in tests, this bug was not detected,
because a test asserted that an empty list (the list of calls) was
greater than zero.  This returns True in Python 2 (where comparing
values of different types is allowed) but raises a TypeError in Python
3.  (Additionally, the wrong thing was being patched.)
This PR fixes the code and the tests to reflect the intended behaviour,
but before merging we should decide whether this is what we actually
want, as we have survived without it for a long time.

Yuck! Subtle bug!
As the comment says, it's an optimisation. For a large table like MeasureValues it can be much faster to re-create an index from scratch than do lots of inserts.
I don't know what the potential speedup is in this case. I do seem to recall that Measures is one of the things that takes the longest.  It's a bit of a tricky call: on the one hand, we manage fine without it; on the other hand, the quicker an import finishes, the better for catching odd problems etc.
My instinct is that we should keep this in - the context manager itself works as it's used elsewhere (in the views code) so it doesn't feel like much of a risk to introduce it for the first time here, and the potential win is useful for the reasons above.  I guess without benchmarking there's also a risk it actually worsening performance: do we have data about how long each import step takes somewhere, so we can monitor it?


Bug: PostgreSQL DataConnector should support connecting to servers with TLS configured

Describe the bug
Connecting to a PostgreSQL server with TLS configured does not work.
To Reproduce
Sign up for a PostgreSQL server from Neon. Try to connect to it via the PostgreSQL Data Connector. Observe the time out issue that occurs when the connection cannot be made.
Expected behavior
The connection works.
We hard-code the NoTls option here: https://github.com/spiceai/spiceai/blob/trunk/crates/db_connection_pool/src/postgrespool.rs#L66

Spoke to @y-f-u who has agreed to take this forward


HIVE-12270: Add DBTokenStore support to HS2 delegation token (Chaoyu …

…Tang, reviewed by Szehon Ho)

Attempt to merge HIVE-12270
Tried to regenerate the Thrift classes using the current branch version 0.9.0 but had too many issues doing so, so regenerated using current version on the Apache master 0.9.3.  Anyway should be backward compatible.


Multiple merges in single commit breaks commit graph

Gitea version (or commit ref): 1.7.6
Git version:
Operating system: Centos
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[X] No
[ ] Not relevant

Log gist:

Description
When more that one branch is merged as part of a single commit, the text output of "git log --graph" appears something like the following:
* | | b9783c0c2
* | | c6c684cd7
| | *-------.   f91f7549e  Interesting commit
| | |\ \ \ \ \
| | | | | | | * 57759c11a
| | | | | | | * 9f1924f08
The parsing of the graph in public/vendor/plugins/gitgraph/gitgraph.js does not handle the "-" characters properly, resulting in an error that prevents display of commits subsequent to the line with the merge.
At line 391, changing:
					color = flows[colomnIndex].color;
to:
				if (colomn === "-") {
					currentRow.splice(colomnIndex + 1, 1);
					color = flows[colomnIndex+1].color;
				}
				else {
					color = flows[colomnIndex].color;
				}
Corrects the display, in our repository, but I am unsure of any side effects, particularly with the flows array.
Screenshots

it should probably needs to be tested with latest gitgraph.js and if still not working reported upstream

I originally tested with a copy of gitgraph.js after the the fix for #3382 so I will open one under bluef/gitgraph.js


Routing fixed

Description
Routing for contact , contributor and other page fixed which doesn't exist in page folder
Issue number : #441

Motivation and Context
So that users can route to desired pages
How Has This Been Tested?
Through google
Screenshots (if appropriate)

Types of changes

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

Checklist:

[x ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

@dinxsh sir please check it's been a week


Zoom box persists with DOM renderer

With #2690 (which looks very nice) we now magically get a drag-zoom box.  However, the zoom box persists after being rendered.  This can be reproduced by opening the simple example with the DOM renderer and shift-dragging to zoom in.
Since we now have a working zoom box with the Canvas renderer, a partially working one with the DOM renderer, and nothing with the WebGL renderer, I still think we'd be better off using a simple DOM element for the box.
My main arguments:

we could have it working consistently, everywhere, right now
nobody is going to guess how to restyle the box (see https://github.com/openlayers/ol3/issues/1583#issuecomment-34094420)
there is no reason to require that people bring in all of the vector rendering code to draw a box on the map

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

Fixed with #4278.


Device discovery crashes upon invalid device response

At the moment, device discovery seems to tightly expect devices to follow the standard.
Though I've seen stuff like:

Random sections of the xml missing
The device just responding with nothing (xml is just empty string)

At the moment, these things crash the application - mostly in unwrap() calls.
Would it be possible to have the library catch and ignore these cases?

The one I saw the most was literally an empty string. The location endpoint on the device just returned a body of 0 bytes.


Add facilities for unit and functional tests

There was already 1 unit test in place.  The existing functional tests are being moved to scripts for consistency with other projects.
One new functional test has been added to test the mt_bench_branch generator as a starting example
I've included basic tests for mt_bench and mmlu.  Which already found two issues:

mmlu_branch was using self.tasks instead of the number of results calculating the wrong average
Not specifying max_workers for mt_bench resulted in an error when it should have defaulted

the other would be it'd be nice to add a badge for this new workflow similar to what is done for the CLI here: https://github.com/instructlab/instructlab/blob/main/README.md?plain=1#L4

Done!


Individual experience form page

Is your feature request related to a specific problem?
We need a form for editing a privacy experience
Describe the solution you'd like

Notices are not linked to experiences in the backend, so we may need to separately query for the notice based on the experience. For example:
Clicking on a privacy experience row of "California" / "Overlay" means we should query for notices with regions=[us_ca] and displayed_in_overlay=true

For all forms

Location section (no editing in v1)

If the experience has any "opt in" notices

Banner text section: title + description
Banner actions section: link label, confirmation button, reject button
Copy for overlay

@allisonking to continue filling this out as questions are answered. currently some confusion around what happens when there are multiple privacy notices "linked" to an experience but they have different consent mechanisms
Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context

moving to done


Enhance the subscriptions section with advanced content creator support options

The Issue
This is just an idea. Feel free to dismiss it.
It is related to #1396 and #1397. My idea is to add options to make subscriptions view section to enable the app users to support the content creators with various types of LBC donations.
There could be a separate sub-menu under "Subscriptions" where the users could set:

fixed or monthly LBC amount they wish to spend
to distribute that amount to creators they subscribe to based on the new content pieces they make or equally
or even an option to distribute that amount to any claim user viewed

My graphics editing skills are at plankton level.
Screenshots

Thanks for filing this Lav. Definitely a much needed feature and would most likely require some API work on our side to enable this.


Update userguide

The user guide says "You’ll probably want to install a backend as well" and refers you to the zebra backend.
There it says to update your .taxirc file, which at that point does not yet exist. So I created it.
Running taxi update with a partial .taxirc file will cause an error (attached).
You can just update the doc to say to run taxi update first.

Things should be better with 4.2 user docs. Let me know if it's still not clear.