Missing text in doc

Issue description

It states:

Between 2023-06-12 and 2023-10-16 | A service key that can be used to connect managed services to SAP Cloud ALM for Operations monitoring applications was generated automatically.You can access it in the SAP BTP cockpit or in theLandscape Management app, as described in Managing Your Service Key.You only need to carry out these steps if you want to set up transport management, but you no longer have to configure your entitlements. **You can access it in the SAP BTP cockpit or in the**
-- | --
Missing the ending of the sentence.

Between 2023-06-12 and 2023-10-16
A service key that can be used to connect managed services to SAP Cloud ALM for Operations monitoring applications was generated automatically.
You can access it in the SAP BTP cockpit or in theLandscape Management app, as described in Managing Your Service Key.
You only need to carry out these steps if you want to set up transport management, but you no longer have to configure your entitlements. You can access it in the SAP BTP cockpit or in the <what comes next??>
Feedback Type (Optional)
spelling or grammar
Page Title on SAP Help Portal (prefilled)
Enabling SAP Cloud ALM API
Page URL on SAP Help Portal (prefilled)
https://help.sap.com/docs/cloud-alm/setup-administration/enabling-sap-cloud-alm-api?version=latest

Thank you!!  That was quick.
From: laurabranitsch @.>
Sent: Tuesday, February 6, 2024 10:36 AM
To: SAP-docs/cloud-alm-setup-admin-guide @.>
Cc: Augedahl, Paula @.>; Mention @.>
Subject: Re: [SAP-docs/cloud-alm-setup-admin-guide] Missing text in doc (Issue #18)
You don't often get email from<EMAIL_ADDRESS>Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
Hi @paugedahlhttps://github.com/paugedahl,
Thank you for catching that, I've corrected the sentence right away. The changes will be visible with the next content update.
Best regards,
Laura

Reply to this email directly, view it on GitHubhttps://github.com/SAP-docs/cloud-alm-setup-admin-guide/issues/18#issuecomment-1930280509, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BF6LTAIUOIKXVY2XK3RM6WLYSJLWBAVCNFSM6AAAAABC4JBKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZQGI4DANJQHE.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

https://people.sap.com/paula_augedahl
From: sap-doc-bot[bot] @.>
Sent: Tuesday, February 6, 2024 10:36 AM
To: SAP-docs/cloud-alm-setup-admin-guide @.>
Cc: Augedahl, Paula @.>; Mention @.>
Subject: Re: [SAP-docs/cloud-alm-setup-admin-guide] Missing text in doc (Issue #18)
You don't often get email from<EMAIL_ADDRESS>Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
Thank you for your valuable feedback contribution, @paugedahlhttps://github.com/paugedahl! So that we can recognize your contribution in SAP Communityhttps://github.com/SAP-docs/contribution-guidelines/blob/main/docs/recognition.md, please tell us your SAP Community profile URL in a reply to this comment; don't include any other text, just the URL on its own, like this:
https://people.sap.com/your-user-name
Thanks!

Reply to this email directly, view it on GitHubhttps://github.com/SAP-docs/cloud-alm-setup-admin-guide/issues/18#issuecomment-1930282089, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BF6LTAOBWBCREQ4GVHMX2FDYSJLXJAVCNFSM6AAAAABC4JBKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZQGI4DEMBYHE.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Stuck from 1 week

Describe the bug
teslamate show "asleep from 1 week and 4 hours", despite using the car on a daily basis
i have no information from one week. i have my car stucked in a gps location that is change many many times until now.
I no have any kind of informaton updated. Charge, trips, etc.
I tried to restart doker many times, i tried to sign out and re sign in, i tried to reset api changing my tesla account password, i tried to update to the last version 1.22.00
Any of those doesn't work.
Expected behavior
i don't know why happen. sometimes happened in the past that miss some trips, but i resolved with docker restart.
The only thing different is that I have been pending the tesla software update for a month which I only ran today, but teslamate hasn't worked for more than a week.
Relevant entries from the logs

teslamate_1  | 2021-04-06 18:38:35.075 [info] Migrations already up
teslamate_1  | 2021-04-06 18:38:37.888 [info] Version: 1.22.0
teslamate_1  | 2021-04-06 18:38:38.837 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (880.944 ms)
teslamate_1  | 2021-04-06 18:38:39.625 [info] POST https://owner-api.teslamotors.com/oauth/token -> 200 (787.492 ms)
teslamate_1  | 2021-04-06 18:38:39.627 [info] Refreshed api tokens
teslamate_1  | 2021-04-06 18:38:39.657 [info] Scheduling token refresh in 5 wk 5 d
teslamate_1  | 2021-04-06 18:38:39.670 [info] Running TeslaMateWeb.Endpoint with cowboy 2.8.0 at :::4000 (http)
teslamate_1  | 2021-04-06 18:38:39.672 [info] Access TeslaMateWeb.Endpoint at http://localhost
teslamate_1  | 2021-04-06 18:38:39.895 [info] Starting logger for '******'
teslamate_1  | 2021-04-06 18:38:39.914 [info] MQTT connection has been established
teslamate_1  | 2021-04-06 18:38:40.192 car_id=1 [info] Start / :asleep
teslamate_1  | 2021-04-06 18:38:41.432 [info] GET /
teslamate_1  | 2021-04-06 18:38:41.477 [info] Sent 200 in 44ms
teslamate_1  | 2021-04-06 18:38:54.641 [info] GET /
teslamate_1  | 2021-04-06 18:38:54.650 [info] Sent 200 in 8ms
teslamate_1  | 2021-04-06 18:39:01.549 [info] GET /
teslamate_1  | 2021-04-06 18:39:01.564 [info] Sent 200 in 14ms
teslamate_1  | 2021-04-06 18:39:01.586 [info] GET /
teslamate_1  | 2021-04-06 18:39:01.600 [info] Sent 200 in 14ms
teslamate_1  | 2021-04-06 18:39:14.890 [info] GET /
teslamate_1  | 2021-04-06 18:39:14.899 [info] Sent 200 in 8ms
teslamate_1  | 2021-04-06 18:39:21.477 [info] GET /
teslamate_1  | 2021-04-06 18:39:21.492 [info] Sent 200 in 15ms
teslamate_1  | 2021-04-06 18:39:30.541 [info] GET /
teslamate_1  | 2021-04-06 18:39:30.552 [info] Sent 200 in 11ms
teslamate_1  | 2021-04-06 18:39:35.519 [info] GET /
teslamate_1  | 2021-04-06 18:39:35.534 [info] Sent 200 in 14ms
teslamate_1  | 2021-04-06 18:39:42.716 [info] GET /
teslamate_1  | 2021-04-06 18:39:42.727 [info] Sent 200 in 11ms
teslamate_1  | 2021-04-06 18:39:42.798 [info] GET /
teslamate_1  | 2021-04-06 18:39:42.809 [info] Sent 200 in 11ms

Environment

TeslaMate version: 1.22.0
Type of installation: Docker
OS TeslaMate is installed on: QNAP 653 PRO
User OS & Browser:
Others:

Maybe the API tokens expired?  With v1.21.2 and subsequent releases, many changes were needed because Tesla changed the authentication. See the v1.21.2 release notes:

⚠ NOTE: Any previously stored API refresh tokens will no longer function, as Tesla has deprecated the existing authentication endpoint. Existing access tokens will continue to work until they expire. Eventually, a full login will be needed to obtain new refresh tokens.
To immediately obtain new tokens after upgrading, go to the TeslaMate settings page, sign out via the button at the bottom of the page and then sign in again.

In any case, the error cannot be narrowed down based on the logs. I would need the logs before you restarted.

I'll close this until more information is available.


Engine lifecycle and fork

Kindly explain the expected behavior from an engine when the application forks.
In case of an engine that uses system-wide resources and cannot work properly when duplicated (forked), is it possible to enforce/hint the application in any way to follow init-after-fork? Is there any guidelines for applications to perform fork and engine init in certain order?
For reference, Here is a difference in behavior of OpenSSL speed -multi application:

When using command line option to set engine, the speed application explicitly delays engine init until fork happens. The speed application doesn't call Engine_init() while parsing command line arguments. Below comment can be seen in code,

    /*
     * In a forked execution, an engine might need to be
     * initialised by each child process, not by the parent.
     * So store the name here and run setup_engine() later on.
     */

From this, can it be inferred that OpenSSL doesn't expect an engine to work across forks?

When using conf file to load engine, unlike above scenario, the engine is initialized in parent process while parsing conf file itself (part of openssl_init_crypto). Thus, while using speed -multi with conf file, the engine is not initialized in the child processes but only in the parent.

Considering an engine that cannot work across forks, what should be the way to go?

Marking as inactive, to be closed at the end of the 3.4 dev cycle, barring further input


Create demos that demonstrate usage inside different frameworks

Is your feature request related to a problem? Please describe.
The date of first release from this repo is May 09, 2018, Its almost 2 years now. I know all contributors might have worked with some limitations. but still it's a long time.
Here is my few suggestions to help developers to make their life easier.
Describe the solution you'd like
We can do following things to make developers life easier.
1st
Kindly release all completed components to 1.0 (production Ready) and then work for remaining so developer can start experimenting with it, right now what happens repo shows its not production ready so no one is trying to use it.
And it will also help them to get familiar with such new and powerful technology.
2nd
Add some examples in repo or in docs like how to use it with other frameworks like angular, react & vue. Which will help new developers to get started.
3rd
Add components from this repo so more developers can have an idea that what can be done with lit powered components.
4th
All this things will help them to build their own in house design system on top of this lit powered technology with this components so it will be very useful for small teams and for new developers also to get started.
So without delaying now all contributors of this repo are requested to release all completed components to V1.0. And now as per current situations with corona days and remote work it will also help developers to achieve more and faster
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@asyncLiz @e111077 @dfreedm @aomarks
Any consideration for this guys?

Hello, the reason we have not tagged this as 1.0 is because it is very much not ready for production. There are large scale refactors and changes coming very soon so it would not make sense to tag as 1.0 then make those changes.
Your second point can probably stand as a feature request on its own.
Third point includes components that are not related to Material Design, and this repository is to showcase our Material Design components not LitElement.

@e111077 ok, thanks for response.

There are large scale refactors and changes coming very soon

@e111077 Thanks for all the work you are doing on the components! Can you, by any chance elaborate a bit on the refactoring and changes coming soon? I believe a lot of developers are already depending on the Material Components and it would be nice to know whether we should expect fundamental changes?

There will be fundamental changes. Likely to custom element naming, package names, and repo location. Likely place we will live in is in the MDC repo at
https://github.com/material-components/material-components-web
Also large API changes to support deeper theming and future SSR integration (think start up state on every component be describable via declarative props). OS consumer-side SSR will be way later down the road; we are only starting with internal Google SSR and working our way to external from there.

There will be fundamental changes. Likely to custom element naming, package names, and repo location. Likely place we will live in is in the MDC repo at
https://github.com/material-components/material-components-web
Also large API changes to support deeper theming and future SSR integration (think start up state on every component be describable via declarative props). OS consumer-side SSR will be way later down the road; we are only starting with internal Google SSR and working our way to external from there.

@e111077 I think you guys should update Readme with roadmap so other developers can have some idea that what is going on and what's has been planned.
OR make new roadmap file and link it to readme, its ok if everything is with no ETA.
This will really help new developers to take decisions easily and also will help to keep patience from developer side. If roadmap is detailed and well explained then developers can start playing with such new, powerful and cutting edge technology like lit-html & lit-element also.
And can't you release first all components without SSR and production ready so developers can start their projects with that? Rest of the features you can develop later, not possible?
Because developer community is waiting from last few years for this.

There will be fundamental changes. Likely to custom element naming, package names, and repo location. Likely place we will live in is in the MDC repo at
https://github.com/material-components/material-components-web
Also large API changes to support deeper theming and future SSR integration (think start up state on every component be describable via declarative props). OS consumer-side SSR will be way later down the road; we are only starting with internal Google SSR and working our way to external from there.

Thanks a lot for more details! I appreciate the effort!!! As SSR seems to be a bigger thing on lit development too - do you have somewhere a desciption / youtube video / something that explains why SSR should be such a big thing for Web component implementations? I am not sure it is super clear why the server side pre-rendering is a benefit ...? and with the current functionality attrbutes of Array and Object types can already be delivered on the components - so I don't see why SSR eventually wouldn't be just delivering the components together with such attributes and properties set?

One main reason is that we went to build webcomponents that fit into anything anywhere which means any framework. Quite a lot of frameworks implement SSR which means that despite their code being in the client, sometimes it lives in the browser (see NEXT js for a real interesting mix of client and server). So if WCs want to live everywhere with 0 compromise, they must also find a way to live in the server.
The problem is that each SSR implementation is unique to its framework. Unlike client-side where they all rely on the same thing, the browser. This makes it a difficult problem and is reason why our progress has been slow. Therefore we are going with an internal google framework first which we think is likely the "hardest-case" scenario.

@e111077 thanks a lot for explaining - much appreciated!!!

Web component is supposed to be usable in any framework. But the readme only shows for plain HTML and javascript.
There is short guide: https://reactjs.org/docs/web-components.html on how to use web component.
Simply importing material-components-web-components in create-react-app
import '@material/mwc-button';
...
<mwc-button ..../>
works in development environment, which is great!
But building it to production environment fails to run with error:
(node:4556) UnhandledPromiseRejectionWarning:  node_modules/@material/mwc-button/mwc-button.js:1
import { __decorate } from "tslib";
^^^^^^
SyntaxError: Cannot use import statement outside a module
It seems create-react-app's webpack fails to build mwc-button module into the bundles.
Short README into how to include material-components-web-components in create-react-app will be good starting point for developer adoption of this module.

Thanks @e111077
Webpack was used to build for production. I only see Rollup in the readme to build for production. Is there instruction to build using Webpack for production?

IIRC the default config for webpack should already resolve modules inside the node_modules folder unlike rollup. Please refer to the module resolution documentation for webpack in case your resolve config has been customized:
https://webpack.js.org/concepts/module-resolution/#module-paths
https://webpack.js.org/configuration/resolve/

The date of first release from this repo is May 09, 2018, Its almost 2 years now. I know all contributors might have worked with some limitations. but still it's a long time.

Now 5 years later, can you believe it! Anyone else reading this probably also loves web components, and material design, and wishes Google has some big product using this to drive it forward. I think lack of web component adoption means this is a "nice to have".

Heya, I'm sorry about the frustration, I've felt the same for 5 years, you gotta believe me. I think a bit of history about our big corp experience can help put things into perspective; this repo was made at the announcement of Material 2.0. Objectives have shifted quite a lot since then. Since inception:

we were re-orged from Chrome to be under material design and had to align with their tech stack
leadership prioritized first party project requiring lots of rewrites for internal google stack alignment and degradation of our third party DX
those delays led to material 3 releasing before mwc 2.0 was in a better state
leadership requiring a material 3 implementation
design tokens not there yet due to the large scope and complexity of Material 3, so delays
leadership de-prioritized first party infrastructure

this is actually good
velocity has increased significantly
we spend time slashing out useless cruft
1.0 targeted 2-4ish sprints from now

layoffs and we've lost a few engineers :(

1.0 is targeted in 2-4 sprints from now, and Material 4 is not anywhere close to existing at all, but the messy rollout of Material 3 across google has brought the concerns we've had about migrations into perspective higher up the chain. Material 4 is expected to have a clearer migration path, and smaller scope ambition.
Please know that the engineers on this project have always been on the side of our users and have pushed for better third party DX, development speed, and prioritization every step of the way, but have had to deal with shifting direction from above. We're really proud of the huge amount of work we've been able to ship in just the last 4 months of 1st party deprioritization despite layoffs, and we think the library is finally starting to shape up, and so do our internal dogfooders. I hope you will too, especially once we free up headcount to work on docs + demos.
We've been hoping to include framework wrappers in this package starting with React using @lit-labs/react. There is a broader effort for FW integration in the core Lit side, but we might ship before those are ready. Additionally, WC integration on other FWs tends to be generally good, so wrappers may not be necessary, just examples.
Post 1.0 would include SSR support, but our 1.0 MVP is shipping all the components first to client-side and ship across ChromeOS for industry battle-testing.

@e111077, thanks a lot for the background info (that anyone monitoring this repo was kind of guessing). Putting it clearly into perspective is appreciated and somehow a relief.

Heya, I'm sorry about the frustration, I've felt the same for 5 years, you gotta believe me. I think a bit of history about our big corp experience can help put things into perspective; this repo was made at the announcement of Material 2.0. Objectives have shifted quite a lot since then. Since inception:

we were re-orged from Chrome to be under material design and had to align with their tech stack

leadership prioritized first party project requiring lots of rewrites for internal google stack alignment and degradation of our third party DX

those delays led to material 3 releasing before mwc 2.0 was in a better state

leadership requiring a material 3 implementation

design tokens not there yet due to the large scope and complexity of Material 3, so delays

leadership de-prioritized first party infrastructure

this is actually good
velocity has increased significantly
we spend time slashing out useless cruft
component completion targeted 4ish sprints from now

layoffs and we've lost a few engineers :(

Component completion is targeted in 4 sprints from now, and Material 4 is not anywhere close to existing at all, but the messy rollout of Material 3 across google has brought the concerns we've had about migrations into perspective higher up the chain. Material 4 is expected to have a clearer migration path, and smaller scope ambition.
Please know that the engineers on this project have always been on the side of our users and have pushed for better third party DX, development speed, and prioritization every step of the way, but have had to deal with shifting direction from above. We're really proud of the huge amount of work we've been able to ship in just the last 4 months of 1st party deprioritization despite layoffs, and we think the library is finally starting to shape up, and so do our internal dogfooders. I hope you will too, especially once we free up headcount to work on docs + demos.
We've been hoping to include framework wrappers in this package starting with React using @lit-labs/react. There is a broader effort for FW integration in the core Lit side, but we might ship before those are ready. Additionally, WC integration on other FWs tends to be generally good, so wrappers may not be necessary, just examples.
Post 1.0 would include SSR support, but our 1.0 MVP is shipping all the components first to client-side and ship across ChromeOS for industry battle-testing.

Very helpful context! Any chance you might have another update like this, now that it's been another 6 months? Thanks

1.0 Release date is set for September 25th. We are doing a concerted burndown of launch blockers which is a very slim list. Personal high confidence of hitting that date. In the meantime lots of breaking changes so that we don't have to do them post 1.0.
Take this as a preliminary meaning for 1.0. We will have an official blogpost somewhere by launch solidifying what is 1.0:

docs will be in the docs directory

usage docs

Breaking changes will be reduced and follow semver

We are currently considering on the team a major version release cadence of once or twice a year

the 1.0 components (in readme) will be reviewed by internal teams:

Passes Google Accessibility Review (GAR)
Passes formal design review

Components are lit-ssr compatible
Slower feature pace
Breaking change migrations will be internally considered

we work in a monorepo across google so we have to migrate everyone
if the migration is too hard for us, it's too hard for you, so each breaking feature will have a migration consideration and sometimes design doc

What is not in 1.0:

Official React / JSX wrappers
Components not on the list in README
material-web.dev readyness

has live demos + stories w/ knobs will be finished post launch

API / event docs

we need to integrate tooling to automate jsdoc + sass analysis -> Markdown because it's too much to keep up to date by hand

Framework integration docs (what this issue is about)

What not supported:

any modules in an internal directory
subclassing components

you can do it, but we will not consider breaking user subclasses breaking

piercing shadow DOM outside of recommended means

recommended

CSS custom props
provided CSS Shadow parts
inherited css properties

not recommended (if you do it you may be broken by our changes)

queryselectoring inside the shadow root
injecting styles into shadow root
subclassing to access DOM in shadow root

What is not in 1.0:\nOfficial React / JSX wrappers

@e111077 I have rendered MD Web components v1 successfully on WebCell v3 & DOM Renderer v2 without any extra JSX wrapper: EasyWebApp/material-cell#2

We (Grayhat) have created a demo for React, which is in-sync with this repository. It's in its early stages, we'd appreciate any help.
https://github.com/grayhatdevelopers/material-web-react


want to hook on page component js import error

nuxt page component js filename changes every time we use npm build
Considering deployment, for example, if a user uses our nuxt app and then we build and deploy new nuxt app, the user no longer be able to go to next page by SPA because the next page component js filename changes and no longer import and render. it's not good...

i would say one idea avoiding this problem is support for adding custom hook on page component js import error. (for example, refresh the browser)
any ideas ??

The hash of filename in calculated from content of component file, it will be changed only when content of file is changed.
In development, every change will lead to a dev rebuilding and hot-replacing and file will be replaced.
In production, every change should be deployed by rebuilding and restarting and users will access new files directly.
What are your specific operating steps ?

Thanks your response.
We use ECS (AWS) for operating Nuxt app.
So when deploying our new version app, the app is fully replaced.
So again, if there are some users that still use old version app when we switch old version app to new version app,  the users fail to go to next page by spa(nuxt-link tag) if the next page component js filename changes...
If our app should be deployed very frequently (for example, thousands in a day), many users will encounter to the problem. It’s very bad for UX...
Any solutions??

note: page components are imported dynamically (on SPA). so if the js file is 404, the nuxt app on client browser cannot render the next page and throw error.

/cc @Atinux @pi0

Hi @igtm
Indeed we may work on this issue to reload the app if the chunk is not found.

Our production facing this issue also when keep update to live server , load chunk fail 😣

Further discussion on https://github.com/nuxt/nuxt.js/issues/3389


Runtime Error: lightningcss module not found after deploying to Vercel

Describe the bug
I deployed an application with Tailwind CSS added to Vercel. While the deployment itself was successful, the following runtime error occurred:
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'lightningcss' imported from /var/task/build/brisa.config.js
    at packageResolve (node:internal/modules/esm/resolve:858:9)
    at moduleResolve (node:internal/modules/esm/resolve:931:18)
    at moduleResolveWithNodePath (node:internal/modules/esm/resolve:1173:14)
    at defaultResolve (node:internal/modules/esm/resolve:1216:79)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:542:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:510:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:239:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:96:40)
    at link (node:internal/modules/esm/module_job:95:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}
Node.js process exited with exit status: 1. The logs above can help with debugging the issue.

To Reproduce
Steps to reproduce the behavior:

Add the Vercel adapter (Reference: https://brisa.build/building-your-application/deploying/vercel)
Add Tailwind CSS (Reference: https://brisa.build/building-your-application/integrations/tailwind-css)
Deploy the application to Vercel.
A runtime error occurs.

The following repository reproduces the error:
keita-hino/brisa-tailwind-vercel-repro
Expected behavior
The application should run without any errors.
Screen recording

Thanks for the repo @keita-hino. The problem with lightningcss using Tailwind is that it cannot be compiled:
https://github.com/parcel-bundler/lightningcss/issues/701
So it is put as an external library.
As .vercel needs a standalone build without external dependencies for this reason it crashes. But it is incorrect on our part, what we should do is to put the external libraries inside the build.
As a workaround, if you move all the node_modules inside .vercel/output/functions/fn.func/build it would work, but of course this is not the way to proceed as copying all the modules makes the standalone build huge.

@keita-hino this is solved in 0.1.7-canary.1

@aralroca
Thank you for the quick fix!
I updated brisa and brisa-tailwindcss to 0.1.7-canary.1 and confirmed that the error has been resolved.
https://github.com/keita-hino/brisa-tailwind-vercel-repro/pull/1

Thanks for the confirmation @keita-hino


Refactor "xTests" into "x"

This canonicalizes the test package names. Summarily:

firrtlTests -> firrtl
firrtlTests.annotationTests -> firrtl.annotations
loggertests -> logger

This does not touch the structure of the old firrtlTests.
Fixes #970.
Merging this will likely introduce merge conflicts for all filed PRs that touch tests...

I think since its just cosmetic changes, it should be fine for existing PR's

Do you think it should be firrtlTests -> firrtl.tests? The main reason I ask is if we did some day publish the firrtl testing stuff for whatever reason, we probably don't want it to pollute the firrtl package?

Good thought, @jackkoenig. That hadn't occurred to me. That would then mean that there would be a tests package below every package node, e.g., the tests for x would be in x.tests while x.y.z would be in x.y.z.tests. That makes sense to me.

Closing this in favor of fine-grained packaging as needed.


Missing 1/jomega in calculation of Hx and Hy for Ez polarization

The computation of Hx and Hy from Ez are missing a 1/1j/omega prefactor. One consequence of this is that a subsequent Poynting vector calculation is incorrect.
I believe the issue occurs on the following lines:
https://github.com/twhughes/ceviche/blob/master/ceviche/fdfd.py#L248-L256
Though, I'm not sure exactly what is stored in info_dict and if omega is available there.

Note that you'll also need the 1/1j/omega when going from Hz -> Ex, Ey on the other polarization. These lines are here:
https://github.com/twhughes/ceviche/blob/master/ceviche/fdfd.py#L264-L281

Fixed in e369cc469c19eba574092da0108159522d2c9024


fix(OverlayViewCreator): position container after render

Sometimes, the width & height reported to the getPixelPositionOffset function are stale (from a previous render). This moves the _positionContainerElement method to the callback of the ReactDOM.render method to ensure React is done rendering before positioning the container.

Released v4.7.2.


Custom title and description of physical web notification

Hello, I want to push physical-web notifications for my sites created in Wix.com platform. However, doesn't matter what title and meta description I set up, all my physical web notifications shows up with the title and description from the homepage only. On Google search results or when the page is opened in the browser everything works great.
Homepage - https://www.digibeam.lt/
Site example I want to use for notifications - https://www.digibeam.lt/donutlab
Anyone have any ideas how to fix this?
Thank you!

Hey, does Wix let you control the Title / Description individually for each page?

How are you adjusting title for https://www.digibeam.lt/donutlab?
When I curl that page, it has <title>Digibeam</title>

When I visit that page, it looks like maybe you adjust title dynamically (with Javascript) after page load.  PWS is not currently able to detect this type of modification.

Thank you for replies. Yes I'm able to change page title and description (that show off on Google search results) on wix.com site editor - screenshot below.
https://s23.postimg.org/r55z1fo17/dnlb.jpg
When I Inspect the page I see the correct title and description that was set on wix.com - screenshots below.
https://s18.postimg.org/sy1v0zz15/dnlb1.jpg
https://s18.postimg.org/qurftbz89/dnlb2.jpg
However when I view-source:https://www.digibeam.lt/donutlab, only the homepage title and description shows up. Also, when I go to digibeam.lt/donutlab site I see the homepage title for a sec and then it suddenly changes to the one I've set in wix.com
Do you think I should contact Wix support for this issue? Or would it be possible to fix it by myself?

I am not familiar with Wix, so I cannot comment.  I will say that PWS currently will only use the initial page title as specified in the original HTML payload.  (This may change, but I wouldn't wait for it).
If there are other HTML tags that PWS should be looking at, specific to search engine indexing, I would be open to suggestions.  However, quickly looking at your page it looks like Wix is just dynamically updating page title after page load using javascript.
Perhaps you can find another section of the settings which is unrelated to SEO and related to page metadata?

Hi so just to clarify.  If I have an eddystone url beacon for physical web pointing to a page within a site, it will still show the meta data for the home page/main web settings or can it be controlled to show the meta data (header, description etc) from each page? thanks


Running debugger with yarn

I have a NodeJS project which I can start from command line with yarn start command. My package.json looks similar to this:
{
  "name": "projectname",
  "version": "0.0.1",
  "description": "",
  "author": "My Name",
  "license": "",
  "scripts": {
    "start": "yarn dev",
    "dev": "yarn stop && pm2 start pm2-dev.yaml && webpack-dev-server --progress",
    "prod": "yarn stop && yarn build && pm2 start pm2-prod.yaml",
    "build": "rimraf dist lib && babel src -d lib --ignore test.js && cross-env NODE_ENV=production webpack -p --progress",
    "stop": "rimraf logs/* && pm2 delete all || true"
  },
  "dependencies": {
    "body-parser": "~1.16.0",
    "ejs": "2.5.5",
    "express": "^4.14.1",
    "pg": "^6.1.2",
    "react": "^15.4.2",
    "redux": "^3.6.0",
  },
  "devDependencies": {
    "babel-cli": "^6.22.2",
    "cross-env": "^3.1.4",
    "eslint": "^3.13.0",
    "pm2": "^2.3.0",
    "redux-mock-store": "^1.2.2",
    "rimraf": "^2.5.4",
    "webpack": "^2.2.1",
    "webpack-dev-server": "^2.2.1"
  }
}

I am trying to start this project in debugging mode with Visual Studio Code but with almost no luck. I have defined my launch configuration in VS Code launch.json file like this:
{
  // Use IntelliSense to learn about possible Node.js debug attributes.
  // Hover to view descriptions of existing attributes.
  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "yarn",
      "runtimeExecutable": "yarn",
      "runtimeArgs": [
        "start"
      ],
      "port": 5858,
      "cwd": "${workspaceRoot}",
      "timeout": 10000
    }
  ]
}

The problem with this configuration is that it usually times-out because webpack-dev-server build is longer than 10 seconds. I can increase the timeout in my configuration, but I have noticed that VS Code results with a message Cannot connect to runtime process (timeout after 30000 ms). eventually, so I assume that this is not a good solution. Also, my breakpoints are ignored with this kind of config which tells me that I am definitely doing something wrong here.
This is the first time I am trying out Visual Studio Code and I usually don't use NodeJS, but I got this project with all these scripts in package.json already defined so I'm trying to adopt to it and therefore all the confusion about how to run it properly.
Can Visual Studio Code run a project like this with full debugging functionality at all, and if so, how should I configure my launch script?

VSCode Version: 1.9.1
OS Version: OS X 10.12.3

Potentially what you want to do is run the JS file that your yarn start configuration is pointing at. For example, in my configuration I had:
"start": {
      "command": "node bin/dev-server",
      "env": {
        "DEBUG": "app:*"
      }

Which I setup in the VS Code launch.json as:
{
      "type": "node",
      "request": "launch",
      "name": "Launch dev-server",
      "program": "${workspaceRoot}/bin/dev-server.js"
}

This might work for you too.

@bomb-on does your yarn "start" script really starts your program in debugging mode? If not, you will have to pass some debugging flags (e.g. what debugging port to use) in the "runtimeArguments".

My launch config:
    {
      "type": "node",
      "request": "launch",
      "name": "`yarn start`",
      "cwd": "${workspaceRoot}",
      "runtimeExecutable": "yarn",
      "runtimeArgs": [
        "start"
      ],
      "stopOnEntry": false
    },

Debug console output:
Debugging with legacy protocol because a runtime executable is set.
yarn --debug-brk=21203 start
yarn install v0.23.4
error `install` has been replaced with `add` to add new dependencies. Run "yarn add start" instead.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Why is it addeing --debug-brk=21203, which seems to be throwing off "yarn start"?

@Sequoia By default a launch config assumes the use of node.js-like runtimes which typically takes a --debug or --debug-brk argument to turn on debug mode.
If you want to prevent VS Code from doing that, just add a "port" attribute to your launch config. In this case VS Code assumes that the "runtimeExecutable" knows best how enable debug mode and it no longer adds--debug or --debug-brk arguments. On the other hand now VS Code needs to know what debug port is used. And for this you have to specify the debug port.
So in your case make sure that "yarn start" enables debug mode and set the debug port. Otherwise VS Code will try to attach without success.

https://github.com/eggjs/egg/issues/1052#issuecomment-308424839


Light laser

About the PR
RedMediumLaserWeak is a cursed name, doubly so because Medium laser is our higher damage version of standard RedLaser so it basically reads "weak strong laser"

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

This needs migrations

What does that mean, just leave the old hitscan prototype in too?

I have marked the migration


DCP-3656: Feature - Example React applications

This MR introduces the examples directory, which includes 2 React projects that show how the use-dcp-worker hook can be used in React applications. One is a simple app featuring a minimal implementation that just starts/stops a worker. The other is an advanced example that showcases the worker and state/statistics data structures that the hook provides. This example is useful to debug the worker hook and see how the Worker API interacts with the hook.
This is to be merged into the maintenance branch, or merged into main after the maintenance branch

@bryan-hoang Ive replaced the example apps with the Vite version


Preview not working, vscode Linux

About bug
The window preview not work, i did try Create Assets but not work.
When i open the http://<IP_ADDRESS>:8000/ in browser it show the Preview normally.
About Desktop
Host system: Linux Mint 21.1
Vscode: 1.83.1
Avalonia: 11.0.2
Extension: 0.0.20
Dotnet Version: 7.0.402
Preview in vscode:

Builded app:

Logs
2023-10-11 22:20:43.753 [info] Creating language service
2023-10-11 22:20:43.753 [info] Starting Avalonia Language Server...
2023-10-11 22:20:43.753 [info] [Trace - 22:20:43] Sending request 'initialize - (0)'.
2023-10-11 22:20:45.275 [info] [Trace - 22:20:45] Received response 'initialize - (0)' in 1527ms.
2023-10-11 22:20:45.276 [info] [Trace - 22:20:45] Sending notification 'initialized'.
2023-10-11 22:20:45.277 [info] [Trace - 22:20:45] Sending notification 'workspace/didChangeConfiguration'.
2023-10-11 22:20:45.361 [info] [Trace - 22:20:45] Received request 'client/registerCapability - (1)'.
2023-10-11 22:20:45.362 [info] [Trace - 22:20:45] Sending response 'client/registerCapability - (1)'. Processing request took 2ms
2023-10-11 22:20:45.362 [info] [Trace - 22:20:45] Sending notification 'textDocument/didOpen'.
2023-10-11 22:20:45.370 [info] [Trace - 22:20:45] Received request 'workspace/configuration - (2)'.
2023-10-11 22:20:45.371 [info] [Trace - 22:20:45] Sending response 'workspace/configuration - (2)'. Processing request took 0ms
2023-10-11 22:20:45.404 [info] [Trace - 22:20:45] Received request 'workspace/configuration - (3)'.
2023-10-11 22:20:45.404 [info] [Trace - 22:20:45] Sending response 'workspace/configuration - (3)'. Processing request took 1ms
2023-10-11 22:20:45.440 [info] [Trace - 22:20:45] Received request 'workspace/configuration - (4)'.
2023-10-11 22:20:45.440 [info] [Trace - 22:20:45] Sending response 'workspace/configuration - (4)'. Processing request took 1ms
2023-10-11 22:20:47.450 [info] [Trace - 22:20:47] Received notification 'window/logMessage'.
2023-10-11 22:20:47.450 [info] [Info  - 22:20:47] AvaloniaLanguageServer.Handlers.TextDocumentSyncHandler: ** DidOpenText: file:///home/gabriel/Projects/CSharp/HelloAvalonia/Hello%20Avalonia/MainWindow.axaml | Uri='file:///home/gabriel/Projects/CSharp/HelloAvalonia/Hello%20Avalonia/MainWindow.axaml'
2023-10-11 22:20:54.292 [info] Command avalonia.previewProcess, file:///home/gabriel/Projects/CSharp/HelloAvalonia/Hello%20Avalonia/MainWindow.axaml
2023-10-11 22:20:54.292 [info] PreviewServer.start /home/gabriel/Projects/CSharp/HelloAvalonia/Hello Avalonia/bin/Debug/net7.0/Hello Avalonia.dll
2023-10-11 22:20:54.301 [info] Previewer process started with args: exec,--runtimeconfig "/home/gabriel/Projects/CSharp/HelloAvalonia/Hello Avalonia/bin/Debug/net7.0/Hello Avalonia.runtimeconfig.json",--depsfile "/home/gabriel/Projects/CSharp/HelloAvalonia/Hello Avalonia/bin/Debug/net7.0/Hello Avalonia.deps.json" "/home/gabriel/.nuget/packages/avalonia/11.0.2/tools/netcoreapp2.0/designer/Avalonia.Designer.HostApp.dll",--method avalonia-remote,--transport tcp-bson://<IP_ADDRESS>:8001/,--method html,--html-url http://<IP_ADDRESS>:8000,"/home/gabriel/Projects/CSharp/HelloAvalonia/Hello Avalonia/bin/Debug/net7.0/Hello Avalonia.dll"
2023-10-11 22:20:54.301 [info] Preview server listening on port 8001
2023-10-11 22:20:54.303 [info] Show Preview to side: file:///home/gabriel/Projects/CSharp/HelloAvalonia/Hello%20Avalonia/MainWindow.axaml
2023-10-11 22:20:54.443 [info] Preview server connected on port 8001
2023-10-11 22:20:54.461 [info] Obtaining AppBuilder instance from Hello_Avalonia.Program

2023-10-11 22:20:54.478 [info] Initializing application in design mode

2023-10-11 22:20:54.527 [info] {"Uri":"http://<IP_ADDRESS>:8000/"}
2023-10-11 22:20:54.818 [info] Sending StartDesignerSessionMessage

2023-10-11 22:20:54.821 [info] {"SessionId":"c2b709f4-c47a-4bf9-a252-5f444c6ebb95"}
2023-10-11 22:20:54.821 [info] Start designer session message received.
2023-10-11 22:20:56.139 [info] {"Error":null,"Handle":null,"Exception":null}

Could you try restarting the VS Code? Do you see the same issue?
Can you share console output from Help -> Toggle Developer Tools, please? Keep it open before you open the previewer

Thanks a lot for sharing the logs
Looks like something specific to Mint, it's not loading the scripts in the previewer.

I am sorry you’re hitting these issues, I will get Mint on my machine to test it out.

Thank you very much, for help.

Other bug: auto complete, not work sometimes
I did try: Restart vscode, create assets, build project, click in Build the project

same there

@heartacker are you on Linux too? What flavour of Linux are you on? Could you share the logs from Avalonia Client from the output?

Other bug: auto complete, not work sometimes
I did try: Restart vscode, create assets, build project, click in Build the project

Same in Fedora 38, but downgrading to 0.0.18 solves both issues (code completion and previewer).

Same in Fedora 38, but downgrading to 0.0.18 solves both issues (code completion and previewer).

I am failing to reproduce it! However, what I noticed is that when you select Build the project for the second time it works. Could you confirm it's same for you?

Seems to have been fixed in #64 the issue was apparently not platform specific

Fixed in 0.0.25


Thin Blood makes Transfusion heal 2 even at 1 Transfusion

Noticed on Pomodorosan's Twitch stream.

Fixed in 1.2.0.


Update editorconfig so it helps enforce the trailing whitespace eslint rule

This addition to .editorconfig means that the trailing whitespace is automatically stripped for those of us that use it, which helps satisfy the eslint rule below (it is enabled for this project):
no-trailing-spaces: 2

Seems like a no-brainer!

I knew the project had an .editorconfig and found myself frantically hitting cmd+s waiting for the whitespace to trim automatically. Then it dawned on me...

Nice!


MIME4J-306 MimeUtil::unfold should group char appends

Calling repeatedly append requires ensuring the capacity amongst other.
Appends to the string builder can be done for all previous chars when a line delimiter is encountered, thus reducing the cost of the operation.
Gain: 66%
Before

After

I did run https://github.com/CodeIntelligenceTesting/jazzer for ~2h on this code sample without detecting defects for what it is worth...


Implement configure_raid support for boss card

Implement configure raid for boss card in assign_role.py
Find out boss controller for detecting physical disks
Added code in dracclient for configuring raid for boss card
Updated dracclient_raid.patch

I changed PR target branch from master to experimental_configure_raid-boss_card.


Add support for ANN algo for large scale retrieval

Cloud Spanner now has support for scalable approximate nearest neighbor retrieval. From my research, these are the steps to introduce support for it:

Make ANN a flag during the store init. It will control generated  DDL and SELECT statements.
For SELECT, use corresponding APPROXIMATE_XXX variant distance functions.
For DDL, when ANN is enabled, additionally run the CREATE VECTOR INDEX statement. Use the vector length hint (might be mandatory when creating the vector index anyway).

Thanks for filing this issue. I am working on it and should have some changes coming up.


Add download data for June 2018

Another pretty big jump (up 13% from May), with 727,069 downloads from 21,765 unique IPs.

Codecov Report

Merging #923 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #923   +/-   ##
=======================================
  Coverage   85.72%   85.72%
=======================================
  Files          76       76
  Lines        2459     2459
  Branches      157      157
=======================================
  Hits         2108     2108
  Misses        351      351

Continue to review full report at Codecov.

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


Fix potential panic in runtime initialization pointed out in PR #2024

Description
Our initial attempt at fixing #1945 had a race condition that may have lead to a panic. If a new component was registered while shutting down and flushing the pendingComponents channel, we would have attempted to write a closed channel and panicked.
Thanks to @yittg for noticing this issue and suggesting this fix (which is the one we should have gone with in the first place).
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-test

/ok-to-test

https://github.com/dapr/dapr/runs/1113922249
The bug is back (or we have a new failure with the same signature).
=== RUN   TestActorActivation/Actor_deactivates_due_to_timeout.
getting logs, the current time is 2020-09-14 19:09:18.126170878 +0000 UTC m=+89.393949657
    actor_activation_test.go:119:
        	Error Trace:	actor_activation_test.go:119
        	Error:      	Should be true
        	Test:       	TestActorActivation/Actor_deactivates_due_to_timeout.
=== RUN   TestActorActivation/Actor_does_not_deactivate_since_there_is_no_timeout.
    actor_activation_test.go:148:
        	Error Trace:	actor_activation_test.go:148
        	Error:      	Should be true
        	Test:       	TestActorActivation/Actor_does_not_deactivate_since_there_is_no_timeout.

Pulled the logs from the above, it looks like we did wait for all components correctly, but we got a connection refused while loading the component?
time="2020-09-14T19:07:57.692755555Z" level=info msg="application discovered on port 3000" app_id=actorapp instance=actorapp-54d4855b8-94qnt scope=dapr.runtime type=log ver=edge
time="2020-09-14T19:07:57.69390656Z" level=info msg="application configuration loaded" app_id=actorapp instance=actorapp-54d4855b8-94qnt scope=dapr.runtime type=log ver=edge
time="2020-09-14T19:07:57.69393606Z" level=info msg="Initialized name resolution to kubernetes" app_id=actorapp instance=actorapp-54d4855b8-94qnt scope=dapr.runtime type=log ver=edge
time="2020-09-14T19:07:57.695657968Z" level=info msg="component loaded. name: kubernetes, type: secretstores.kubernetes" app_id=actorapp instance=actorapp-54d4855b8-94qnt scope=dapr.runtime type=log ver=edge
time="2020-09-14T19:07:58.72292984Z" level=error msg="error from operator stream: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp <IP_ADDRESS>:80: connect: connection refused\"" app_id=actorapp instance=actorapp-54d4855b8-94qnt scope=dapr.runtime type=log ver=edge
time="2020-09-14T19:08:05.640019197Z" level=warning msg="failed to load components: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp <IP_ADDRESS>:80: connect: connection refused\"" app_id=actorapp instance=actorapp-54d4855b8-94qnt scope=dapr.runtime type=log ver=edge
time="2020-09-14T19:08:05.640063597Z" level=info msg="waiting for all outstanding components to be processed" app_id=actorapp instance=actorapp-54d4855b8-94qnt scope=dapr.runtime type=log ver=edge
time="2020-09-14T19:08:05.640090197Z" level=info msg="all outstanding components processed" app_id=actorapp instance=actorapp-54d4855b8-94qnt scope=dapr.runtime type=log ver=edge
time="2020-09-14T19:08:05.640119598Z" level=warning msg="actors: state store must be present to initialize the actor runtime" app_id=actorapp instance=actorapp-54d4855b8-94qnt scope=dapr.runtime.actor type=log ver=edge
time="2020-09-14T19:08:05.640180198Z" level=warning msg="failed to init actors: state store does not support transactions which actors require to save state - please see https://github.com/dapr/docs" app_id=actorapp instance=actorapp-54d4855b8-94qnt scope=dapr.runtime type=log ver=edge
stdout

/ok-to-test

Pulling more operator logs from above. Looks like the operator container was terminated about ~15s before the above tests failed.:
{"instance":"dapr-operator-bbd5db669-c2v4x","level":"info","msg":"log level set to: info","scope":"dapr.operator","time":"2020-09-14T19:07:26.402520746Z","type":"log","ver":"edge"}
{"instance":"dapr-operator-bbd5db669-c2v4x","level":"info","msg":"starting Dapr Operator -- version edge -- commit 7a4d10d","scope":"dapr.operator","time":"2020-09-14T19:07:26.405356061Z","type":"log","ver":"edge"}
{"instance":"dapr-operator-bbd5db669-c2v4x","level":"info","msg":"metrics server started on :9090/","scope":"dapr.metrics","time":"2020-09-14T19:07:26.404950359Z","type":"log","ver":"edge"}
{"instance":"dapr-operator-bbd5db669-c2v4x","level":"info","msg":"Dapr Operator is started","scope":"dapr.operator","time":"2020-09-14T19:07:26.812286936Z","type":"log","ver":"edge"}
I0914 19:07:26.812367 1 leaderelection.go:242] attempting to acquire leader lease dapr-tests/operator.dapr.io...
I0914 19:07:26.821238 1 leaderelection.go:252] successfully acquired lease dapr-tests/operator.dapr.io
{"instance":"dapr-operator-bbd5db669-c2v4x","level":"info","msg":"starting watch for certs on filesystem: /var/run/dapr/credentials","scope":"dapr.operator","time":"2020-09-14T19:07:27.013553362Z","type":"log","ver":"edge"}
{"instance":"dapr-operator-bbd5db669-c2v4x","level":"info","msg":"mTLS enabled, getting tls certificates","scope":"dapr.operator","time":"2020-09-14T19:07:27.01312016Z","type":"log","ver":"edge"}
{"instance":"dapr-operator-bbd5db669-c2v4x","level":"info","msg":"Received signal \"terminated\" beginning shutdown","scope":"dapr.signals","time":"2020-09-14T19:07:43.329753669Z","type":"log","ver":"edge"}
stdout

Ok, so the operator service getting restarted appears to be a separate issue, I will open up a new issue for it.

Hi @wcs1only, to make it completely synchronous, the components should be processed in place rather than putting back to channel after their dependencies ready.
https://github.com/dapr/dapr/blob/1660773c3da6740377f4440cae89dea93479c9f5/pkg/runtime/runtime.go#L1278-L1282

Hi @wcs1only, to make it completely synchronous, the components should be processed in place rather than putting back to channel after their dependencies ready.
https://github.com/dapr/dapr/blob/1660773c3da6740377f4440cae89dea93479c9f5/pkg/runtime/runtime.go#L1278-L1282

Nice catch, this would indeed be an issue. This should be reproducible in a test.

/ok-to-test


Don't mask everything as a ProcessingError

https://github.com/zendesk/ruby-kafka/blob/51dbfe2261817205415fc2ca8b9336dd115c73df/lib/kafka/consumer.rb#L202
This causes us a few headaches:

Every exception in Bugsnag has this class, so we can't Ignore, Fix, or Snooze independently
Our own outer rescue strategy (to tick metrics, silence expected issues, etc) can't just rescue what we want, it has to rescue this and check #cause

Is there a reason you're not re-raiseing the original exception?

There are several reasons:

I don't want to use a catch-all rescue in the async producer; it's important to be able to identify errors raised in the user code.
I need to be able to "decorate" the exceptions with the topic/partition/offset information in order to provide actionable information to operators.

Is it difficult to check #cause? You could simply do this:
case exception.cause
  when SomeError then "some error"
  when RuntimeError then "omg"
end

We extract the original exception when reporting exceptions to our tracking system and add the decorated info, e.g.
ErrorTracker.track(exception.cause, topic: exception.topic, partition: exception.partition, offset: exception.offset)

This works fine for us.

Thank you for the info, we will figure out one of the work-around options.


Depreciate this addon in favor of ember-froala-editor

Its been a year since there has been active development with this addon. I've been keeping the other "official" Froala editor Ember addon updated as changes are needed. The existence of both has caused some confusion on which to use. And looking at the npm download stats, the other has recently over-taken the lead. I'd suggest we do a few things;

[ ] npm deprecate ember-froala "ember-froala has been deprecated in favor of ember-froala-editor"
[ ] Add a note towards the top of the README about the deprecation
[ ] Publish one more version once Froala Editor 2.4.2 is out, so that the README makes it to npm and Ember Observer

Any thoughts / objections? I don't want to cause any hard feelings towards the original addon authors, just want to help clear up any confusion in the ember community/ecosystem.

Nope I figured that was always the plan once the numbers supported it.

Done.

Re-opening as the README update didn't make it to Ember Observer (changed after version 2.4.2 released).
@stefanneculai we'll need to have one more release once 2.4.3 is out.
Can one of your run the npm deprecate command? I don't have rights to publish ember-froala on npm.
npm deprecate ember-froala@">= 2.4.2" "ember-froala has been deprecated in favor of ember-froala-editor"

@stefanneculai or @artsmc can one of you publish 2.5.0 and run the deprecate command mentioned above? Then I think we're done here. :)


new Structure(structure) pattern

Constructing a data structure from another data structure is a common pattern in Java and even Javascript:
new Set(new Set([1, 2, 3]))  // {1, 2, 3}

Would you like to get a PR implementing it?

Hello @xamgore. JavaScript is a bit inconsistent on this particular point. new Array does not have the same semantics as new Set in this regard for instance. So I chose to implement this use case as the many static #.from methods you can find across the library. For instance you can:
MultiSet.from(new Set([1, 2, 3]));

I feel it covers the usecase quite nicely and does not overcomplicate the constructor implementations. What do you think?

A good example is Buffer class, it also has Buffer.from method and new Buffer has been deprecated since Node v10. I don't know the reasons, though.
Thank you for the fast response 😌, I will send a PR with DefaultMap.from then.

I don't remember why I skipped adding a #.from to the DefaultMap... Maybe there is some kind of conceptual problem with it you will stumble upon while implementing.  I'll wait for your PR then.


Chroma VectorStore document cannot be updated

System Info
Given how chroma results are converted to Documents, I don't think it's possible to update those documents  since the id is not stored,
Here is the current implementation
Would it make sense to add the id into the document metadata?
Who can help?
@jeffchuber
@claust
Information

[ ] The official example notebooks/scripts
[ ] My own modified scripts

Related Components

[ ] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[X] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
This is a design question rather than a bug. Any request such as similarity_search returns List[Document] but these documents don't contain the original chroma uuid.
Expected behavior
Some way to be able to change the metadata of a document and store the changes in chroma, even if it isn't part of the VectorStore interface.

@adieyal  - this would be great! it would also allow easy updates, deletions, etc.
@hwchase17 what are your thoughts?

Based on that comment, I think I was referring to user-ids - I didn't realise there was a difference.

@adieyal there are the ids the user provides to the database (for tracking purposes) and then chroma also generates a uuid for each embedding - https://github.com/chroma-core/chroma/blob/main/chromadb/db/clickhouse.py#L31
i think the user provided ids (in the langchain case, if not provided are autogenerated) make the most sense to store LangChain side


Rebar

i did all the steps but in amd software i cant enable rebar is this normal?

nvm i forgot to flash the patched bios how do i do that i have a generic dell mobo dell xps 8500


Remove on-type line formatter

This formatter is not used in JediLS or pylance.
If needed then this should be moved into LS and support on type formatting.

@luabud Should we add a news item for this? If yes, then can you provide the text, since this is a deprecation. My version:
"Deprecating on-type line formatter since it isn't used in newer Language servers".

You could remove the files from .eslintignore in this PR too since it's only about deleting stuff, although to be fair there's also src/client/activation/jedi.ts that needs to be linted 🤷

@callerin What do you mean? we don't plan on supporting this, since tools like black formatter or autopep8 don't provide a way to do this. If you want to you can make a feature request on pylance (here https://github.com/microsoft/pylance-release)


feat(revsets): Add roots, heads and children functions

This is a simple one: it just adds roots, heads and children functions to the revset evaluator. In particular, the addition of children() would allow the alias for git drop (as described here) to work via the git alias drop='!f() { git move -x "children($1)" -d "$1"^; git hide "$1"; }; f'
And heads and roots were just added while I was there. It felt like it could be handy to calculate the first commit in a stack (eg roots(stack())) and such.

Thank you. I also updated the revset wiki at https://github.com/arxanas/git-branchless/wiki/Reference:-Revsets


Remove sprintf third party library

This is part of the effort to move third party dependencies to npm (or remove ones that are unneeded like sprintf - https://github.com/CesiumGS/cesium/issues/9473
The changes here replace calls to sprintf with String.prototype.padStart(). This PR targets the npm staging branch because IE11 doesn't support this function.

Thanks @ebogo1!


In DB Lookup mediator, issue in downloading JAR library from server

Description:
When using the DBLookup mediator, for setting up database configuration there are two options to add JAR libraries. When using the get from server option, it shows the progress of the download in a popup window, but after that when try to test the connection, it  gives the message “Please download or browse driver”.

Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Fixed in the latest release

Fixed in the latest release


Error on unknown postcode could be improved

If a postcode is entered that is not recognised on e.g. https://www.gov.uk/report-pothole, the error message is “Please enter a valid full UK postcode.” (source https://github.com/alphagov/frontend/blob/master/app/views/root/_location_form.html.erb#L12)
Given there will always be brand new postcodes that have not yet entered the database, or worse if the database of postcodes has not been kept up to date, this error could read rather poorly to someone who knows full well they have entered a valid full UK postcode.
I would suggest something more friendly, along the lines of “we don't recognise your postcode” or “we can't find your postcode” with suggestions as to what could have gone wrong (mistyping, new/changed postcode, etc), putting the issue on the site rather than the user.

I've logged this issue it in the relevant improvement plan for local services.
As I said with #789 the best way to raise any future issues like this is through the "Is there anything wrong with this page?" link at the bottom of the page. Thanks for raising this though.


steam: add wrapper testing for libGL

Motivation for this change
Failing to set hardware.opengl.driSupport32Bit will lead to a
confusing error message about missing libGL.so.1 as described in #19518
Things done
We include a wrapper around the steam bin to test for working 32bit
opengl with glxinfo. When failing, we display a proper warning hinting
towards the option.

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Tested on local NixOS machine by activating/deactivating hardware.opengl.driSupport and hardware.opengl.driSupport32Bit. In all cases it gave the expected result:
[nix-shell:~/src/nixpkgs]$ steam
*** WARNING: Test for 32-bit libGL unsuccessful.
             This could mean you forgot to activate hardware.opengl.driSupport32Bit
cp: cannot create regular file '/home/user/.local/share/Steam/bootstrap.tar.xz': Permission denied
Running Steam on nixos 17.09.2476.53e6d671a96 64-bit
STEAM_RUNTIME has been set by the user to: /steamrt
Pins potentially out-of-date, rebuilding...
mkdir: cannot create directory ‘/nix/store/rcdiw6bpzdx4i3lqj4pyz546svjlqc96-steam-fhs/steamrt/pinned_libs_32’: Read-only file system
mkdir: cannot create directory ‘/nix/store/rcdiw6bpzdx4i3lqj4pyz546svjlqc96-steam-fhs/steamrt/pinned_libs_64’: Read-only file system
Error: You are missing the following 32-bit libraries, and Steam may not run:
libGL.so.1
Error:
You are missing the following 32-bit libraries, and Steam may not run:
libGL.so.1
Press enter to continue: ^C

While it would make Steam start, to make it actually work one would also need to enable hardware.pulseaudio.support32Bit. Also, if glxinfo doesn't run, we can make for sure that Steam won't start, so warning message could be worded more confidently. For example:
**
WARNING: Steam is not set up. Add the following options to /etc/nixos/configuration.nix
and then run `sudo nixos-rebuild switch`:
{
  hardware.opengl.driSupport32Bit = true;
  hardware.pulseaudio.support32Bit = true;
}
**

Also, Steam can be installed on other Linux distributions and not just NixOS. buildFHSUserEnv should propagate /etc/NIXOS and this message should only show up if that file is present.

@yegortimoshenko  checking for /host/etc/NIXOS causes the following assert to fail:
if [ -e /host/etc/NIXOS ]; then

sudo: /nix/store/3xsjm8rfpy0ysfjs1pcybj33fsigszgp-wrapper.c:203: main: Assertion `!(st.st_mode & S_ISUID) || (st.st_uid == geteuid())' failed.

Any pointers?
Also, the HEREDOC leads to ugly indentations; what's your preference here?

I'm not sure I understand why it fails: it works in underlying chrootenv:
$ ./chrootenv sh -c 'if [ -e /host/etc/NIXOS ]; then echo hi; fi'
hi

Also, the HEREDOC leads to ugly indentations; what's your preference here?

It's just less error-prone: for example, if someone were to add another line to message, with echo they would have to wrap it in echo "..." > /dev/stderr or something comparable, while with heredoc they would just add another line. It's ugly syntactically, but semantically it's much better, because it forms a single multi-line string, while echo presents itself as series of lines that only incidentally form a cohesive message.

Presumably, this is a bug in nixos/modules/security/wrappers/wrapper.c. But I don't understand why Steam has any business with setuid wrapper.

/cc @ixmatus

Maybe my build/test-environment was somehow tainted; I don't understand it either. I will dig into it tomorrow and try to get a proper and clean build.
As for the heredoc:
if [ x ]; then
  if [ y ]; then
    echo <<EOF >&2
This is ugly
And breaks indentation.
EOF
  fi
fi

I'm not reall happy with this.

Compare:
  wrapperScript = ''
    if [ -e /host/etc/NIXOS ]; then
      echo "**" >&2
      echo "WARNING: Steam is not set up. Add the following options to /etc/nixos/configuration.nix" >&2
      echo "and then run `sudo nixos-rebuild switch`:" >&2
      echo "{" >&2
      echo "hardware.opengl.driSupport32Bit = true;" >&2
      echo "hardware.pulseaudio.support32Bit = true;" >&2
      echo "}" >&2
      echo "**" >&2

and:
  wrapperScript = ''
    if [ -e /host/etc/NIXOS ]; then
      cat <<EOF >&2
**
WARNING: Steam is not set up.


Silver ingot issue

In 0.9.4 silver ingot can be smelled to the same ingot, without getting exp from this
I think the problem in tags, because in 0.9.3 it doesn't work
Here is the screenshot from the REI btw

Hello!
Thank you for raising this issue! I have found the problem, and it is indeed related to the tags.
I renamed the files wrongly, meaning silver ores and silver ingots switched places.
I will fix this as soon as possible in an upcoming update. Thanks for posting the issue!

There is a problem with electrum [alloy] too. The it's texture (and recipe of electrum irl) is gold+silver, but recipe used in your mod is a gold+zinc.

(Oh, and a little question: can i translate MythicMetalls to russian lang..?)

Yeah, feel free to make a translation. Submit it as a pull request or upload the file as an issue, and i will include it


fix: be correct so we don't burn from Zs

I caught too many Zs...
luckily the manual had something to say about this:

Unless stated otherwise, any overflow when manipulating integer values wrap around, according to the usual rules of two-complement arithmetic. (In other words, the actual result is the unique representable integer that is equal modulo 2n to the mathematical result, where n is the number of bits of the integer type.)

so here we are
UPDATE

I would be fine with just whatever saturating_add does, even if it doesn't match
I don't want to mimic weird overflow behavior

kyren has spoken.
UPDATE UPDATE
too many Zs spoiled the broth.

I would be fine with just whatever saturating_add does, even if it doesn't match
I don't want to mimic weird overflow behavior

kyren has spoken.

No, never mind, I was confused about what behavior I was seeing. After trying the tonumber("ZZZZZZZZZZZZZZZZZZZZZ", 36) example with varying number of Zs, you hit a maximum where any number of further Zs always returns -1.
This made me think that "oh, okay, obviously PUC-Rio Lua is computing the sum as an unsigned integer, doing saturating math on it, then converting it back to a signed integer, so it ends up as -1". This would be a silly behavior to mimic, and it seemed reasonable to instead max out at the signed max, rather than the unsigned max.
HOWEVER, that is not what is happening. As it states in the manual, overflowing integers wrap around. But then, how is tonumber("ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ", 36) == -1, as well as any increasing number of Zs?
Well, it turns out this operation has a fixed point...
((2^64 - 1) * 36 + 35) % (2^64) == 2^64 - 1
So, with this knowledge, wrapping math matches PUC-Rio Lua better, and we should do that.

This fixed point is obvious because, in modular arithmetic terms... this is (-1) * 36 + 35 == -1, which is not so strange! The coincidence is that mod(sum(35 * 36^n, n, 0, 31), 2^64) just so happens to land on -1, and once it lands here it stays here. I'm sure there is a deep numeric reason for this, but I'm too tired to go any deeper right now.

It's not that deep.
Okay, a repeating max digit (like 9999999... or ZZZZZZ....) is always (b^n - 1) for the base b and number of digits n.
We can rewrite this as...
(2 * b / 2)^n - 1
2^n * (b / 2)^n - 1
2^64 * 2^(n - 64) * (b / 2) ^ n - 1
So if b has any factor of two (b is even), and n is >= 64, then this equation is 2^64 *  - 1, which is congruent to -1 mod 2^64. 36 is factored as 332*2, so it has 2^2 as a factor, so the point at which tonumber("ZZZZZZ...", 36) becomes -1 is at 32 Zs.


Nv stream events pyfunc callbacks

@denisvmedyantsev
please update the benchmarks table before marking PR as ready to review.
please add to Jetson NX information on what power mode/core mode we are using when running performance benchmarks.


docs folder is being used instead of dist folder for viewing the live preview of the site in the development environment of the local machine

Related to another issue?
Yes, #1379 on Github in this repo.

Describe this issue

A' docs' folder is created when the make run command is executed in the local machine to see the development version.
The dist folder should be used ideally when the make run command is executed.
It needs to be investigated why the docs folder is being used instead of the dist folder when generating a live preview of the site.

Observed behavior
When the make run command is executed, the live preview site is in the docs folder.

Expected behavior
When the make run command is executed, the live preview site should be present in the dist folder instead.

Proposed solution
Solution #1

Investigate why the docs folder is being used instead of the dist folder. As a preliminary investigation, the Makefile can be a place to start.
Make the necessary changes in the Makefile file.
At the time of writing of this issue, it may have probably been included in the .gitignore file. If it is so, then perform the following steps:
a) Remove docs from .gitignore.
b) Also remove the associated comment in .gitignore.

Solution #2
According to this highlighted comment:

In config.toml file, I just need to change the path in line #8:
publishDir = "${new_path}"
Here new_path is the placeholder. Once I know the exact path, I will replace it here.

I would be happy to take up this issue.


Discourage (or stronger) @Null*arked from non-static members of generic classes

The current working decision (#43 #127) is to allow both @NullMarked and @NullUnmarked at the method/constructor/nested-class level.
The most troublesome negative consequence of that decision was stated here: an unprojected usage of a type variable might be null-marked or not independently of whether that type variable's bounds are null-marked or not, and this gets really hard for normal people to reason about.
Option 1:

We keep figuring it out until we can explain it really well (then we explain it really well).
We make sure the spec makes it unambiguous (it might already).
We make sure to cover various permutations in our conformance tests.

Option 2:

We say: look, don't put @Null*arked on a non-static member (field/method/inner-class) of a generic class; results may be undefined if you do. (Note we can't prevent them from doing it.)
We don't include these cases in our conformance tests, or optionally we test that an analyzer can report an don't-do-that

My observations in favor of 2:

having to avoid that case seems like no great loss to users
it eliminates the troublesome scenario above
I feel like if we have to have documentation explaining how to think about that weird scenario, it ends up making our whole product look more complicated.
I don't think 2 would close the door on doing 1 sometime later, perhaps even post-1.0.

 So I can see wanting to further marginalize it. At the same time, that scenario has to be handled by the underlying model anyway (and it is, and we have lots of sample inputs for cases like this), so we'd have to go out of our way to not respect the nullness information that users have provided us. Given that, I see a lot of reason to avoid discussing the scenario in any detail in our main docs, but I don't see reason to declare it to be undefined.
The typical ways of mixing specified and unspecified nullness are when a @NullMarked class uses a @NullUnmarked class or vice versa. But within a single class, there's the scenario you mention, plus the scenario of annotating only a type-parameter bound in @NullUnmarked code. For whatever we want to do for your scenario, we'd likely want to to do for that last case, as well. At that point, every type-variable usage would have specified nullness if and only if its type parameter's bound had specified nullness.
...wellllll... kind of... :( We can produce essentially the same scenario when a @NullMarked class uses a @NullUnmarked class (or vice versa):
@NullMarked
class Marked<T> {
  T get();

  Unmarked<T> unmarked;
}

class Unmarked<T> {
  T get();

  Marked<T> marked;
}

Inside Unnmarked, marked.get() returns "just T," but we don't know if T permits nullable type arguments or not. Similarly, inside Marked, unmarked.get() returns "maybe just T or maybe some projection of T," but we still know that T doesn't permit nullable type arguments.
Again, I agree very much with not pushing this kind of scenario into users' faces. But in cases in which we have enough nullness information to tell users about mismatches, I think we should tell them: If someone writes class ImmutableList<E extends @NonNull Object>, I think that person is asking us to produce errors for ImmutableList<@Nullable String>, even if that person hasn't annotated the rest of ImmutableList yet and even if that person couldn't stand at the whiteboard and derive all the information about expressions involving different usages of ImmutableList.
To oversimplify (but I hope only slightly): I think we have to say that, if you don't want to see nullness errors, then don't provide nullness information. I think it's fine to warn users that mixes of specified and unspecified nullness can be complex. But incremental adoption is perhaps the biggest "new" feature we're providing, and we have evidence from Kotlin that it's useful, even when people encounter scenarios like someMarked.unmarked.get().

The typical ways of mixing specified and unspecified nullness are when a @NullMarked class uses a @NullUnmarked class or vice versa. But within a single class, there's the scenario you mention, plus the scenario of annotating only a type-parameter bound in @NullUnmarked code. For whatever we want to do for your scenario, we'd likely want to to do for that last case, as well.

I've been chalking that part up to: "in null-unmarked code, a type variable usage (that isn't already unspec-bounded) that isn't being projected is automatically an 'unspec-projection'". And #248 is about whether that happens in one or both directions. Eh?

There's nothing we really need to do here

(I did the "discouraging" in #349 anyway.)


A too long blog title overlap the right content field in the backend

For the blog details in backend you're using white-space: nowrap;. I would recommend to wrap longer text parts because it looks better for my opinion.

Additional Information
OS: Debian Wheezy Linux version 7.8
Browser (64bit): Latest Chrome Canary, Firefox (stable) and Opera (stable)
Node Version: 0.12.2
Ghost Build Number: 0.6.4

Is this something that can be worked on? Looking to get my feet wet.

This has been resolved

yeah, i deleted my comment when i realized the related PR. thanks.
On Wed, Jun 24, 2015 at 10:35 AM, JohnONolan<EMAIL_ADDRESS>wrote:

This has been resolved
—
Reply to this email directly or view it on GitHub
https://github.com/TryGhost/Ghost/issues/5402#issuecomment-114949855.


Total number of bbox per class

Dear organizer,
As per information on GitHub, for task 1, the number of labels per class is as follows: 5511 (specularity), 1099 (saturation), 5015 (artifact), 658 (blur), 1532 (contrast), 2904 (bubbles), 437 (instrument). However, I found different numbers for the same (PhaseI: specularity (4074), saturation (511), artifact (1609), blur (327), contrast (686), bubbles (1738), instrument (407). If we consider both phase1 and phase2, the figures is as follows: specularity (7596), saturation (1733), artifact (8583), blur (1023), contrast (2430), bubbles (4420), instrument (499). I am just wondering if you can check and update the statistics. Thank you in advance.
Best wishes,

Azam.

Hi Azam,
I have double checked and combining both detection phases over 2192 files we have:
5096 - artifact,
675 - blur
3079 - bubbles
1558 - contrast
453 - instrument
1122 - saturation
5835 - specularity
My counting of phase I is the same as yours.
Phase II release breakdown by my counting is:
3487 - artifact,
348 - blur
1341 - bubbles
872 - contrast
46 - instrument
611 - saturation
1761 - specularity
If you are happy with these numbers I will update the github to reflect the revised countings.
Best,
Felix

Yes, you are correct, Felix. Thank you for your prompt reply.

thanks for confirming. I have updated to the corrected version.


Investigate election dates not scraped from props parser

If we wanted to scrape another site, it looks like we can match dates to ambiguous elections through this site: http://www.sos.ca.gov/elections/prior-elections/special-elections/


IntlBackslash mixed up with Backquote in VSCode web, MacOS, British keyboard layout

The keybindings are broken on MacOS for "`" & "§". You can see this by going to https://vscode.dev / https://github.dev on MacOS, opening the keyboard shortcut picker, clicking on a shortcut to edit & pressing both them keys.
Alternatively you can reproduce by pressing "CTRL+`", to open the terminal which doesn't work
ScanCode 106 (106 in enum) is detected as IntlBackslash (§) when it should be "`" https://github.com/microsoft/vscode/blob/5e2f5e57cb2d3a222d43de51541b0eda207914e8/src/vs/base/common/keyCodes.ts#L334.
This is with the British layout:

Hmm... this works for me, but I have a different issue. My keybindings from window tiling app stopped working entirely.

I think that's because vscode intercepts all keyboard shortcuts, COMMAND+SHIFT+B to toggle bookmarks bar also doesn't work

Just to add, I noticed this change after upgrading to the latest release.

In case this helps https://github.com/microsoft/vscode/wiki/Keybinding-Issues#summary

@roblourens is there a reason why it's broken in VSCode Web, but not on desktop? Setting keyboard.dispatch to keyCode fixes it, but it works with code on desktop

is there a reason why it's broken in VSCode Web

Yes, on the desktop we have a native node module which we use to detect the key mappings. On the web, we need to rely on web APIs, which are incomplete.

This is happening to me on desktop FWIW.
On Sun, Oct 23, 2022, 12:47 PM Alexandru Dima @.***>
wrote:

is there a reason why it's broken in VSCode Web
Yes, on the desktop we have a native node module which we use to detect
the key mappings. On the web, we need to rely on web APIs, which are
incomplete.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/163432#issuecomment-1288152431,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACUPVGTJXZSPVBEQWSLY6TWEVT2NANCNFSM6AAAAAARDK5H5U
.
You are receiving this because you commented.Message ID:
@.***>

Similar also happening on Android:
    |*| 【F1】 ("Command Palette") outright not responding.
    |*| 【Ctrl】 + 【A】 ("Select All") has no effect [1] while 【Ctrl】 + 【C】/【V】 ("Copy" / "Paste") would work.
    |*| 【Tab】 could not be trapped. (causes keyboard navigation)
    |*| And many more.
[1] Not happening in Chromium.

@fny @MasterInQuestion Keybindings are OS, browser and keyboard layout dependent, which means your problems are distinct from the OP. Please open a separate issue if you still have keybindings problems.

Chrome on MacOS with British layout

On native macos, it's broken for me in Firefox & Chrome in keyboard.dispatch: code setting it to keycode fixes it
It works in safari though

Issue for Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1755096

Found a newer bug on Chromium's side: https://bugs.chromium.org/p/chromium/issues/detail?id=1296783

Awesome, this should help us remove the patch.

Yep, I can confirm it's broken in both Firefox/Chrome with doing:
window.onkeydown = (e) => console.log("code:", e.code, "key:", e.key);

[ Quote alexdima @ CE 2022-12-06 21:27:18 UTC:
https://github.com/microsoft/vscode/issues/163432#issuecomment-1340028915
    Keybindings are OS, browser and keyboard layout dependent, which means you are running into problems which are distinct from the problem reported by the OP. ]
<^>    Fundamentally caused by identical cause. (key binding in default configuration in general broken across browsers)

Still broken on Chrome almost a year later.


[Helm Chart] Default "admin" security configs don't allow stream creation

As a user, I've provisioned SCDF via the latest helm-chart; however, with the default admin user credentials, I'm unable to create streams.
Acceptance:
The admin is a super-user equivalent account. It might be useful to map it to ROLE_CREATE role by default.

This is a core Data Flow problem, that's where the permission mapping is done.

This issue was moved to spring-cloud/spring-cloud-dataflow#2276


Add sysrsync to requirements.txt

Hi @tblock79 @RoyWiggins ,
I created this PR to include sysrsync library into the requirements.txt, as the UI was not initiated because of this missing library installed.

Thank you for pointing this out and submitting the PR!


DoF: Foreground Blurring

The current DepthOfFieldEffect implementation exhibits undesired visuals around the edges of foreground objects. This issue becomes more noticeable with larger bokeh scales and foreground CoC blur kernels.
The expected result is that the foreground gradually blurs into the background using the near CoC values. However, if the foreground is on top of the background (near CoC is close or adjacent to far CoC), the sharper foreground edges will overwrite the blurrier background. The following screenshot demonstrates the problem:

The foreground edges are sharper because the blur is tied to the CoC and gets weaker as it reaches the edges. This gradual decrease in blur strength is important to prevent color haloing, so introducing a flat minimum blur strength is not an option.
The problem can be solved by taking the background CoC values into consideration when blurring the foreground. If this information is blended with the foreground CoC data, the blur strength can be increased around the edges when foreground and background are next to or on top of each other.
The following screenshot shows an attempt at implementing this theory by using the sharp far CoC buffer:

Note how this approach produces other undesired artifacts which can be eliminated by using the blurred far CoC values from our near CoC buffer instead. The final implementation allows heavy blurring without exhibiting sharp colors around foreground objects:

I'll publish this fix after cleaning up the code.

For reference, the following screenshots show why soft foreground edges are so important:


how plot different method predict result in one image ?

like trajectory and error plot in one image

If you are refereing to translation and rotation error per segment length (ie. 100, 200, ..., 800m),
you will get the figure (stored in plot_error) after the evaluation

Yes， I mean ， If we have two or above method prediction result.  Could this tool plot different method curves in one figure.
like this ,it's not only ground truth with one method  to comparison. Contain two or above ~

I see now.  Unfortunately, this tool wasn't designed for comparing multiple results.
However, I believe only some simple modifications are required on the current tool  for the purpose.
I have a tool for plotting the last diagram but it wasn't in a well organized way.

Hello, could you tell me which paper the last figure came from? @fangxu622

Hello, could you tell me which paper the last figure came from? @fangxu622

@whyygug It's from the paper: "DeepVO: Towards end-to-end visual odometry with deep Recurrent Convolutional Neural Networks", Wang, Sen Clark, Ronald Wen, Hongkai Trigoni, Niki

did you solve this problem? Can you give me some suggestions? thanks!

did you solve this problem? Can you give me some suggestions?

did you solve this problem? Can you give me some suggestions? thanks!


Exam 2 Q10

You have a misscalculation in your formula for b. For the new centroid you divide by alpha * w_i + wb (the number of elements of the batch for the new cluster)

I had noticed a mistake there, but I thought it was
    new_c1 = (sum(cluster1)*len(cluster1)+alpha*w_c1*c1)/(len(cluster1)+(alpha*w_c1))
    new_c2 = (sum(cluster2)*len(cluster2)+alpha*w_c2*c2)/(len(cluster2)+(alpha*w_c2))

That I mulitplied by len(clusterX) here which I shouldn't have done. (And fixed since)
But the division already looks like what you wrote. So what do you mean?

Sorry, youre partially right. The error i saw was wrong, at least partially. First of all you use sum(cluster1), which should be the average of vector of all the new points per cluster. So you should divide that sum by the number of new points for each cluster. In my point of view that boils down to just taking the sum of vectors. I can only assume that he put it in the lectures as he did to improve readability. Than you get (0,2) as a result.

Yeah, I tried to do it with more detail to be closer to the lecture slides, but with no points in the second cluster that meant a divide by zero error and frankly, I couldn't be bothered.
Thanks for the feedback though it's good to see some people taking an interest in the notebooks


Manage missing mandatory fields

Manage missing mandatory fields by showing an error at the codegen stage.
For example, I save a test case with missing actions, pages and elements, like so:

When the test cases are parsed it should check that mandatory fields are present, and if any are not present codegen should stop at the end of the "Parsing" phase with the message "Parsing FAILED." and not move onto "Cleaning folder".
Errors should be shown in the codegen log for these, e.g:
Error: testFailures.tcase - Line 1, Action "Click" is missing "Element"
Error: testFailures.tcase - Line 2, Missing "Action"
Error: testFailures.tcase - Line 3, Action "Input" is missing "Page" and "Element"

Hi @brogreenmoon
Here is a proposed rules for the validations of the steps. Given that currently each step has 3 peices of info: Page, Element, and Data.

Action Clear: Requires Page and Element
Action Click: Requires Page and Element
Action Click Popup: Requires Page and Element
Action Close Popup: None
Action Delay: Requires Data - the miliseconds to delay
Action Go to Url: Requires Data - the URL
Action Input: Requires Page and Element
Action Input by Code : Requires Page and Element and Data
Action Run Code: Requires Data - the actual code to run
Action Select Option: Requires Page and Element and Data
Action Verify Attribute: Requires Page and Element and Data
Action Verify Has Text: Requires Page and Element and Data
Action Verify Has Value: Requires Page and Element and Data
Action Verify IsEditable: Requires Page and Element
Action Verify Is ReadOnly: Requires Page and Element
Action Verify IsVisible: Requires Page and Element
Action Verify Title: Requires Data
Action Verify Title Contains: Requires Data
Action Verify URL: Requires Data - The URL

This is working perfectly for test cases, but not for test routines.  For example:

gives:

Milestone v0.2.4 is already released, please move this ticket to other milestone

Hi @brogreenmoon
What are the new requirements/issues with this one?


Subsuper script

Has errors in TranslationRightPanel.
Please make sure to not raise a PR with compilation/runtime errors.


1. ByConity cluster information
There are 3 tso servers, 3 ByConity-Servers, 20 write-workers and 50 default-workers in my ByConity cluster.
2. Bucket CnchMergeTree table info:
I create a bucket CnchMergeTree, just like:
CREATE TABLE db_bucket.bucket0
(
    `id` Int32,
    `name` String,
    `age` UInt8,
    `age_group` UInt8,
	 ......
	`timestamp` DateTime
)
ENGINE = CnchMergeTree
PARTITION BY toDate(timestamp)
CLUSTER BY (id, toDate(timestamp)) INTO 50 BUCKETS SPLIT_NUMBER 100
ORDER BY id;

3. Load Data
I import more than 10 bilion rows of data in 1 partition to this Bucket CnchMergeTree.
ByConity write worker import between 100 thousand rows each time.
4.
It throws Exception
Exception: Code: 159, e.displayText() = DB::Exception: Get data from metastore reached timeout 60000ms. SOLSTATE: HY000 (version <IP_ADDRESS>) (from xx.xx.xx.x:xxx)
5. Probleam Analysis

There 10 billion rows of data in 1 partition of this table, I import 100 thousand rows each time.
There will be 100 thousand parts if this CnchMergeTree is not a bucket table.
If this CnchMergeTree table is a bucket table, the number of buckets will be enlarged. In my cluster there are more than 3 million parts.
It cost too much time when query metadata from FoundationDB.
It is different from number of bucket table and number of write-worker, so If we import 100 thousand to a bucket table, there will be 20 part because write-worker will bucket these data to 50 buckets.

中文描述：
a. default-worker: 50台机器,  write-worker是20台; 建表时分成50个桶
b. 数据导入每次10w条，有100亿的数据， 在不考虑分桶的情况下， 1个分区的数据会产生10w个part
c. 当数据有分桶，此时桶数会放大，在我们的环境中发现放大到了300w个part
d. 查询分桶表时，性能都耗在了元数据获取上, 报错都是获取元数据超时
e. 原因：part数过多，从FDB查的时候慢了
f. 采取了预分区的导入方式，但write-worker个数和bucket桶数不一致，导致预分桶失效了
g. 预分区时, 导入模块只支持单分桶键; 但byconity建表语句建了2个分桶键,也会失效

hi @zhaojintaozhao.

Usually timestamp is used for partition by, not for cluster by. It is highly suggested to only use cluster by id.
As you have a huge amount of data, you'd better improve from 100 thousand rows to 1 million rows for data importing each time.
After data is imported, the background merge is working to reduce the number of parts. So you can wait for a while to query the bucket table.

Usually timestamp is used for partition by, not for cluster by. It is highly suggested to only use cluster by id.
As you have a huge amount of data, you'd better improve from 100 thousand rows to 1 million rows for data importing each time.
After data is imported, the background merge is working to reduce the number of parts. So you can wait for a while to query the bucket table.

Hi @smmsmm1988 :
Is there any way to speed up the merge? There are 20 write-workers in my system. How should I adjust the parameters to speed up the merge?
Is there any way to speed up the merge? I have 20 write-workers in my system. How can I change the default merge parameters to speed up the bucket table merge?

Usually timestamp is used for partition by, not for cluster by. It is highly suggested to only use cluster by id.
As you have a huge amount of data, you'd better improve from 100 thousand rows to 1 million rows for data importing each time.
After data is imported, the background merge is working to reduce the number of parts. So you can wait for a while to query the bucket table.

Hi @smmsmm1988 :
Is there any way to speed up the merge? I have 20 write-workers in my system. How can I change the default merge parameters to speed up the bucket table merge?

try the following parameters:
enable_addition_bg_task = 1
cnch_merge_select_nonadjacent_parts = true
max_partition_for_multi_select = 7
max_addition_bg_task_num = max(1.5 * writer_worker_num * core_num_per_write_worker, 200)

@zhaojintaozhao did you try the parameters @smmsmm1988  suggested? Do you still have the issue?

@zhaojintaozhao did you try the parameters @smmsmm1988 suggested? Do you still have the issue?

Yes, after I used the parameters provided by @smmsmm1988, the problem was solved. Thank @smmsmm1988  very much.
And thank you.
So I close this issue.

This issue can be closed.


Add mutual authentication with self-signed certificate

Add support for mutual authentication in order to connect with OpenVPN client using self-signed certificates.
Explicitely state the authentication type: either 'federated-authentication' (with OKTA as SAML IdP)
or 'mutual-authentication' with self-signed certificates signed with aprovided private key.

Is this still something that should be added? As it's almost a year old by now...


Add Keys type alias and docs

Close #11
Hope this is fine!

Thanks for the PR! However I am sorry to say that after seeing this proposal, I am having second thoughts about this addition overall. Let me explain in detail.
Thinking from the perspective of a first time package user, it could be very confusing to see documentation that says "This thing could also have been like that but it is like this". Especially since the truth is that the package does make sure the keys are only mentioned once in the list. Thinking further in terms of the documentation, I don't think adding a type alias is a good idea. The type signatures are a very important part of the documentation on package.elm-lang.org. List Key communicates that it is a standard Elm list and can be used as such, while Keys can be anything, including an opaque custom type. Another thing is that I don't think the documentation needs to explain the technical part (complex to implement). That is not a concern for the package consumer.
I hope this makes sense to you. What do you think?

I'm good with this! Thank you for sharing your reflections on this. I agree 100%. You are taking great care in API design and documentation and that's what makes the ecosys so valuable.
Somebody who has a similar question will hopefully be lead here or #11 by the search engine of their choice :)


Python3.12

Checklist

[x ] Used a personal fork of the feedstock to propose changes
[x ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

This is blocked by https://github.com/conda-forge/root-feedstock/pull/237.


Buffer removes shapes when they are enclosed by other shapes

Expected behavior and actual behavior.
I have three polygons enclosed by four other polygons. When I buffer the union of these, some of the inner polygons disappear:

I expect the inner polygons to not disappear after applying buffer.
Steps to reproduce the problem.
import shapely
from shapely.geometry import MultiPolygon, Polygon
from shapely.ops import unary_union
import matplotlib.pyplot as plt

def plot_polygon(polygon, ax, color="black"):
    if isinstance(polygon, Polygon):
        ax.plot(*polygon.exterior.xy, c=color)
    elif isinstance(polygon, MultiPolygon):
        for p in polygon.geoms:
            ax.plot(*p.exterior.xy, c=color)
    else:
        assert False

def get_box_polygon(pos, dim):
    box = shapely.geometry.box(-dim[0] / 2, -dim[1] / 2, dim[0] / 2, dim[1] / 2)
    return shapely.affinity.translate(box, pos[0], pos[1])

obstacle_boxes = [
    get_box_polygon([0, -2], [4, 0.5]),  # outer 1
    get_box_polygon([0, 2], [4, 0.5]),  # outer 2
    get_box_polygon([2, 0], [0.5, 4]),  # outer 3
    get_box_polygon([-2, 0], [0.5, 4]),  # outer 4
    get_box_polygon([0, 0], [0.7, 0.5]),  # inner 1
    get_box_polygon([1, 0.3], [0.7, 0.5]),  # inner 2
    get_box_polygon([-1.3, 1.0], [0.7, 0.5]),  # inner 3
]

area = unary_union([box for box in obstacle_boxes])

fig = plt.figure()
for i, buf in enumerate([0.0, 0.1, 0.2]):
    ax = fig.add_subplot(131 + i)
    ax.set_aspect(1.0)
    ax.set_title(f"Buffer {buf}")
    plot_polygon(area.buffer(buf), ax)
plt.show()

Operating system
Manjaro Linux
Shapely version and provenance
Python 3.9.11
Shapely 1.8.2

Happy to know that I am not alone in getting issues with buffer. Just that I got an unusual extra inner hole instead #1405

This is actually not a bug in shapely, but an issue with the way I plot the polygons (ignored polygon.interiors). If plot_polygon is replaced like this it works:
def plot_polygon(polygon, ax, color="black"):
    if isinstance(polygon, Polygon):
        polygon = MultiPolygon([polygon])
    assert isinstance(polygon, MultiPolygon)

    for p in polygon.geoms:
        ax.plot(*p.exterior.xy, c=color)
        for interior in p.interiors:
            ax.plot(*interior.xy, c=color)