Improve load time of POP

At the moment, it takes > 20 seconds to load a POP on the iPad - during load, a half-rendered page is shown. This is the entry-point for the demo, so it's important to speed this up considerably.

@lauraluiz how do want we measure the page speed?
Can we pic a POP (a category?) and write how much time it takes now?

Currently addressed by improving images. Please @rzenner let us know when the images and fixed and it needs to be adapted in Sunrise.

Duplicated in https://github.com/commercetools/commercetools-sunrise-java-demo/issues/5
Let's keep the other one for this issue.


Profile Pic does not auto scale for different avatar types

@alisaad673 pls test further and expand the issue

It should be doable to compute the head bounding box and then zoom the camera back.
We already effectively do this triangle math for the decapitation feature.


Convert Brush to Polygon: Graham Scan

Today i tested the Graham Algorithm to calculate a convex hull from drawn lines using this package:
https://www.npmjs.com/package/graham_scan
It was very easy to implement and i made a test in the drawing layer:

I pretty like the result from the test. The black shape is the area I was drawing with a brush and the red line is the calculated polygon.
The polygon in the test is smaller that the black area because I didn't take the stroke width of the black line into account.
@markus2330 we can discuss my findings on monday but whats your first impression if you look at the screenshot?

with "curvy" areas its not working that well because then also big areas that are not colored are included in the polygon

@danielsteinkogler
I found an interesting library for alpha shapes (wikipedia): alpha-shape
It looks like it can create "concave hulls" but requires fiddling with the alpha value.
Example:

Here is another one for concave hulls: Hull.js

@chr-schr that looks very very nice


K8s integration with IAM Role

When running aws eks update-kubeconfig with --role-arn new entry created under .kube/config. which contains the following:
- name: arn:aws:eks:eu-west-1:123456789:cluster/xxx
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - --region
      - eu-west-1
      - eks
      - get-token
      - --cluster-name
      - yyy
      - --role
      - arn:aws:iam::123456789:role/admin
      command: aws

Any kubectl command or IDE for k8s failed to run due to the fact that alias aws="aws-mfa-secure session" contains a space, this caused the kubeconfig to fail the command.
My question is -

Do you have any workaround?
Can you add another command to skip the session usage? ( e.g aws-mfa-secure without the session )

Should be used like this:
- name: arn:aws:eks:eu-west-1:123456789:cluster/xxx
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - session
      - --region
      - eu-west-1
      - eks
      - get-token
      - --cluster-name
      - yyy
      - --role
      - arn:aws:iam::123456789:role/admin
      command: aws-mfa-secure

as the alias is blocking somehow the passing of the additional needed arguments

till will require everyone that using EKS + aws-mfa-secure to update the kube/config manually. I'd like to avoid it and use the aws command.

@tongueroo  any estimation here?

No estimate. Will consider and review PRs. No sweat either way of course 👍


Where is convertor export?

Is there not supposed to be a convertor export?

Hello,
You're right. I'm going to publish a new version today, so you can use it with the new version!
Sorry for the delay

Thanks, I thought i was losing my mind. Can't wait to drop cronstrue undeeded 1mb package.

So sorry for the delay 😞
But the new release is live v3.1.0!


[Bug]: Elasticsearch: Incorrectly detected OSS image

Module
Elasticsearch
Testcontainers version
1.19.8
Using the latest Testcontainers version?
Yes
Host OS
Windows
Host Arch
amd64
Docker version
Client:
 Version:           26.1.0-rd
 API version:       1.44 (downgraded from 1.45)
 Go version:        go1.21.9
 Git commit:        cca8e72
 Built:             Tue Apr 23 16:26:59 2024
 OS/Arch:           windows/amd64
 Context:           default

Server:
 Engine:
  Version:          25.0.5
  API version:      1.44 (minimum version 1.24)
  Go version:       go1.21.10
  Git commit:       e63daec8672d77ac0b2b5c262ef525c7cf17fd20
  Built:            Sun May 12 07:25:43 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.7.10
  GitCommit:        4e1fe7492b9df85914c389d1f15a3ceedbb280ac
 runc:
  Version:          1.1.12
  GitCommit:        51d5e94601ceffbbd85688df1c928ecccbfa4685
 docker-init:
  Version:          0.19.0
  GitCommit:

What happened?
We are currently trying to use Azure Container registry (ACR) to serve as a pull through cache for Docker images. That one has quite some  limitations (e.g.: https://github.com/Azure/acr/issues/599#issuecomment-1751689962), forcing us to configure the Elasticsearch Testcontainer like this (please note the library/ prefix):
            elasticsearchContainer = new ElasticsearchContainer(
                DockerImageName.parse("library/elasticsearch")
                    .asCompatibleSubstituteFor("docker.elastic.co/elasticsearch/elasticsearch")
                    .withTag("8.10.4")

            )

This one fails, as it claims it tries to use the OSS version of Elasticsearch while activating a password, even though it is not true (it is not the OSS image...)  + I override this anyway with asCompatibleSubstituteFor
Relevant log output
2024-07-05T13:50:43.285Z  INFO 422 --- [dataview] [           main] ContainersSpringContextCustomizerFactory : Warming up the elastic database
2024-07-05T13:50:43.287Z  WARN 422 --- [dataview] [           main] o.t.e.ElasticsearchContainer             : library/elasticsearch is not supported anymore after 7.10.2. Please switch to docker.elastic.co/elasticsearch/elasticsearch
2024-07-05T13:50:43.332Z ERROR 422 --- [dataview] [           main] o.s.boot.SpringApplication               : Application run failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'de.mt.dataview.config.ElasticsearchTestContainer': You can not activate security on Elastic OSS Image. Please switch to the default distribution

Additional Information
Seems like the detection for isOss is could be improved  - or maybe removed as it seems marked deprecated anyway...
https://github.com/testcontainers/testcontainers-java/blob/b4b1c2022d540177ada794b028c99fba5daeba1f/modules/elasticsearch/src/main/java/org/testcontainers/elasticsearch/ElasticsearchContainer.java#L108-L117

Hi, I think the code should be
elasticsearchContainer = new ElasticsearchContainer(
     DockerImageName.parse("myregistry.azurecr.io/docker.io/library/elasticsearch")
        .asCompatibleSubstituteFor("docker.elastic.co/elasticsearch/elasticsearch")
        .withTag("8.10.4")
)

We do have the host name written into
testcontainers.properties file in our classpath via hub.image.name.prefix property as explained in https://java.testcontainers.org/features/image_name_substitution/
That's why we don't mention it explicitly in our Java code.


Embeddings cache regression (^h^h^h confusion)

I just updated to commit 72439bfc8391814ad0b933534cc8c37dc9101de7 but it seems like there is a regression?

The TTL is 60 minutes but it seems like it's requesting a series of embeddings for each query.
Ok, so I uninstalled it, then reinstalled it, in case my chrome storage options got in a wonky state somehow.
It's then not showing the connection indicator (which I was /was/ seeing at first!) for the model 404

So, back to the embeddings, I've removed/installed. Once I select a model in options hopefully we are good?
Response:

Lots of embeddings (long page):

Hrmmm, it definitely seems like it's calling the embedding endpoint many times for each query. I could have sworn you were caching, that's what the TTL means, right!?
Oh, it's not cached when isHighlightedContent:
          chrome.runtime.sendMessage({
            prompt: prompt,
            skipRAG: false,
            chunkSize: config.chunkSize,
            chunkOverlap: config.chunkOverlap,
            url: activeTabUrl.toString(),
            skipCache: isHighlightedContent,
            imageURLs: imageURLs,
          });

Based on:
const getHighlightedContent = (): string => {
  const selection = window.getSelection();
  return selection ? selection.toString().trim() : "";
};

Oh, I see! I guess it's a bit complicated to use the cache easily, eh?
Hrmmmmmm, hhere's other optimizations you could do, but compared to creating completely new embeddings a simple linear search over the highlighted string to see if it contains any of the chunks that would otherwise be returned by the configured parser (i.e. "canonical" chunks?) ?

A few comments...

My thinking behind skipping the cache when highlighted content is selected is that a typical use case would be to highlight "smaller" chunks of text on a page that didn't already have a dedicated content parser (e.g. an infrequently visited site). In this case, embedding should be quick and a user would likely move on to highlight a different part of the page, which means the previous chunk doesn't need to be cached.
It's still possible that a user "selects all" content (ctrl+a). In this case, vector search is still valuable.
I've updated the search logic to use a combination of cosine similarity and keyword fuzziness search.
The UI/UX doesn't give any indication that the cache is skipped when highlighted content is parsed. I can make some quick improvements here (e.g. documentation + messaging in app)

The UI/UX doesn't give any indication that the cache is skipped when highlighted content is parsed

I haven't thought about this thoroughly. That said, my instinct is that you could/should cache embeddings depending upon the size of the selection (@see still possible that a user "selects all" and even other large selection cases)
The issue was a legit logging of my experiences. I really thought there was a regression, and it wasn't until I rummaged around in the code that I discovered what was happening.
Bypassing the cache is probably the sort of behaviour that many would find reasonable in its simplicity, provided they knew what has happening.
Which is to say, yeah, some kind of indication would help!


[rewrite] Make it easier to require streams

Description:
(Feature request)
I enjoy using mithril's streams outside of web app development, and currently in order to just import m.prop-like functionality into a project, something like this is required:
const log = console.error.bind(console);
const Stream = require('mithril/util/stream')(log);
const stream = Stream.stream;
stream.combine = Stream.combine;
// ... etc

It would be nice to instead be able to do something like this:
const stream = require('mithril/stream');

This is a dupe of https://github.com/lhorie/mithril.js/issues/1132
Would you mind sending in a PR for this? I figure we might as well start doing #1132 from somewhere


Fix links to the documentation.

Description
Fixes links to the documentation on readthedocs.io.
Where has this been tested?
n/a
Possible Drawbacks
n/a

This change is

Hi,
Thanks for pointing it out, but we already fix those links, so I'm going to close this PR.
Regards


the app can't running

I packed my app, but I can't run it on my phone, and I don't see anything, so can you give me a full, functioning code, including javascript call python and python call javascript? Thank you.

The project has retired, I decided to go full java development due to performance issues


Adds Picker Reset functionality

Fixes #25291. Tests to be added later.

Some notes from review (also cc @matthew-carroll)

Have separate controller types for timer and date time
Soft deprecate the initial countdown duration / datetime value and move them to the controller
Move manipulations of the countdown / datetime value to the controller
Start with the timer controller in first PR

@xster @jslavitz here it what I was trying to say in the meeting.
We were talking about AnimationControllers and a StopwatchController and I was explaining that these two artifacts, despite having similar names, are completely different.
An AnimationController implies the existence of an entire visual system.  A StopwatchController does not.
For example, a StopwatchController API might be:
start()
pause()
reset()
Those methods say nothing about the visual representation of the given stopwatch.  In fact, that controller would be equally applicable for a background stopwatch that has no visual representation.
So a StopwatchController might utilize AnimationControllers as an implementation detail, but we should not conceptually tie the two together.
Does that make sense?

Makes sense. I agree.

@jslavitz for some reason I can't seem to locate the comment I made about whether or not this controller makes sense for this use-case, so I'll follow up here.
I think you mentioned that this behavior wouldn't be possible without a controller, but I was wondering why the same behavior would not be achievable by leverage onUpdateWidget() to check for changes to a given Duration?

From the PR description:

tests to be added later

Please write complete tests up front.  https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#write-test-find-bug

@jslavitz I noticed that you re-requested a review.  My primary question/concern is still the previous comment I posted.  I'm still not clear as to why a controller is the right solution here if all we're doing is setting and changing UI properties.

On controller vs didUpdateWidget (I think that's the alternative you're asking), going with a controller should be right. Otherwise, you're giving in a value to seed the UI state via a Widget instance but the UI state source of truth is no longer coming from Widgets once you change it (unlike say CupertinoSwitch which doesn't change until you setState again after a callback, but that approach would look weird here since this scrolls).
Since Widgets rebuilds all the time, you can't just check if didUpdateWidget matches the current value in the State, you'd have to check whether didUpdateWidget matches the originally given value. In general, level triggered events are better than edge triggered events.

Thanks for working through all this. We'll close this PR for now and we'll pick it up from your branch.


STI (rebase #393) and Immutable option

Rebases #393.
Adds an immutable option to allow a resource to be read only. Allows an STI base resource to return a heterogeneous collection, but not modify the collection.

Looks good now - thanks @lgebhardt :shipit:


can you update a license?

Hi. This work is great, can you please update the license? Otherwise, no one can use it.

Added


Connection Refused

Python 2 & 3 releases (python2 --version and python3 --version):
Whatever comes with Raspbian Lite

Description of problem:
When i try to authorize Google stuff, I'm brought to a website that asks me to Allow google's api (i think). When I click allow, nothing happens. I'm brought to a grey page that simply says connection refused. picture here - https://dl.dropboxusercontent.com/s/zfuir6sri5hcxms/chrome_2017-05-12_22-54-50.png

![chrome_2017-05-12_22-54-50 1](https://cloud.githubusercontent.com/assets/15090661/26021978/b53dff72-3766-11e7-9ea2-13cfbf54b6f2.png)

Expected:
to authorize.

Steps to reproduce:

attempt to authenticate with google
click allow
look at connection refused page.

Traceback (if applicable):

Additional info:
I have a raspberry pi 3 that has nothing else but Assistant Pi on it.

hi, please provide more information - is it sure the google auth or is it the amazon authorization? please paste the lines that came before this in your terminal and provide the url you are trying to open.
Sidenote: I'm re-writing AssistantPi right now, as I was experiencing some painful bugs. Better wait a few days for the new release.

I had to start the authorization manually.
pi@raspberrypi:~ $ /opt/AlexaPi/env/bin/python -m googlesamples.assistant.auth_helpers --client-secrets /home/pi/Downloads/client_secret.json
Please visit this URL to authorize this application: https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=1071494548268-9bf77r8k5kkd3hts6jpij5h62hdreqh3.apps.googleusercontent.com&redirect_uri=http%3A%2F%2Flocalhost%3A8080%2F&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fassistant-sdk-prototype&state=cnfplcb0wjZqT7CCo9bN9QOzzSDr17&access_type=offline

I can open the link without problems, no "Connection refused" - maybe you could try to disable your Adblocker or try another Browser.

I did disable my firewall. I'll try another browser

i disabled my firewall and tried 3 different browsers. I still get connection refused.

I formatted and reinstalled at least 6 times. everytime, connection refused.

It has nothing to do with AssistantPi that you can't open Google's Auth link, there's something about your setup/network... plz try open the link on another computer, on your phone or any other device that has a Browser - I can't help you with this

i have tried on 3 different networks. still happens. wtf? please reopen issue. not my networks.

Seriously, I can't help here. The link you've posted works fine:

Additionally, I haven't altered the Authorization with Google API, it's 100% the same as in the SDK. If you can't get it to work, please file an issue in Google's Assistant SDK Repository.

Ok thanks!
On May 14, 2017 6:13 PM, "Martin"<EMAIL_ADDRESS>wrote:

Seriously, I can't help here. The link
https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=1071494548268-9bf77r8k5kkd3hts6jpij5h62hdreqh3.apps.googleusercontent.com&redirect_uri=http%3A%2F%2Flocalhost%3A8080%2F&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fassistant-sdk-prototype&state=cnfplcb0wjZqT7CCo9bN9QOzzSDr17&access_type=offline
you've posted works fine:
[image: g.jpg] https://postimg.org/image/4iza23xu1/
Additionally, I haven't altered the Authorization with Google API, it's
100% the same as in the SDK. If you can't get it to work, please file an
issue in Google's Assistant SDK Repository
https://github.com/googlesamples/assistant-sdk-python.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/xtools-at/AssistantPi/issues/6#issuecomment-301343591,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOZD5X_DErqbOzC2CvQrCp3yBgBYYid3ks5r53yhgaJpZM4NZ8QX
.


405 Client Error: Method Not Allowed for url:

Hi After starting my bot with the simple:
from mattermost_bot.bot import Bot
if __name__ == "__main__":     Bot().run()
I get the following:
Traceback (most recent call last):   File "C:/Users/user/IdeaProjects/mattermost_bot/mattermost_bot-master/mattermost_bot/main.py", line 5, in <module>     Bot().run()   File "C:\Software\Python\lib\site-packages\mattermost_bot\bot.py", line 27, in __init__     settings.SSL_VERIFY   File "C:\Software\Python\lib\site-packages\mattermost_bot\mattermost.py", line 154, in __init__     self.login(team, email, password)   File "C:\Software\Python\lib\site-packages\mattermost_bot\mattermost.py", line 158, in login     self.user = self.api.login(team, email, password)   File "C:\Software\Python\lib\site-packages\mattermost_bot\mattermost.py", line 51, in login     p.raise_for_status()   File "C:\Software\Python\lib\site-packages\requests\models.py", line 935, in raise_for_status     raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 405 Client Error: Method Not Allowed for url: https://*****/****/users/login

What version of Mattermost are you running?
If it is newer consider trying mmpy_bot we started with this both and updated to support API4 and a few other fixes and enhancements. As far as I know this project is EOLed.


Loading intellisense status stuck/tsserver using more than 100% of CPU

Does this issue occur when all extensions are disabled?: Yes

Version: 1.79.2 (Universal)
Commit: 695af097c7bd098fbf017ce3ac85e09bbc5dda06
Date: 2023-06-14T08:58:52.392Z
Electron: 22.5.7
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.2.0

System info: MacBook Pro with an M1 chip and 32GB ram, currently on macOS Ventura Version 13.1

Whenever I open VSCode, the 'Loading IntelliSense Status' never finishes. It occasionally works for a short while after restarting VSCode, but the issue always re-appears while using VSCode:

Every once in a blue moon I also get the error message that 'the JS/TS language service crashed 5 times in the last 5 minutes':

The issue is visible in the activity monitor, where 'Code Helper (Plugin)' uses more than 100% of the CPU:

Executing the command ps aux | grep 11913 to find which process is causing issues provides me with the following output:
ottosornas       11913 163.1  9.3<PHONE_NUMBER> 3120256   ??  R    10:36AM   1:49.37 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) --ms-enable-electron-run-as-node --max-old-space-size=3072 /Users/ottosornas/{path-to-current-project}/node_modules/typescript/lib/tsserver.js --useInferredProjectPerProjectRoot --enableTelemetry --cancellationPipeName /var/folders/f4/2rc8k2hs1xn6gdz3wc_8wnbc0000gn/T/vscode-typescript501/aef985add7ae3d86f643/tscancellation-d6d3e144acebc1f2eb2f.tmp* --locale en --noGetErrOnBackgroundUpdate --validateDefaultNpmLocation --useNodeIpc
ottosornas       12021   0.0  0.0 408626880   1296 s000  S+   10:37AM   0:00.00 grep 11913

Sample here of this activity can be found here: Sample of Code Helper (Plugin).txt
So it seems tsserver.js is crashing/getting stuck, which in turn makes VSCode basically unusable.
Things I've tried based on other forum threads (nothing works for me):

Upgraded VSCode
Made a clean re-install of VSCode
Disabled all extensions
Re-cloned the repository
Re-installed all node_modules
Opened the repo with Visual Studio Code - Insiders and all extensions disabled
Changed typescript version to Workspace version instead of VS Code version
Disabled settings sync
Deleted the typescript cache under Library/Caches
Upgraded typescript version
Added node_modules to "files.exclude" in the settings.json-file
Installed JavaScript and TypeScript Nightly

Can you share a project which causes this issue?

I had the same problem in my TypeScript project and tried the above solution, but it also didn't work. However, I wondered which code this problem occurred since I wrote it. Then I found code that used the wrong type even if it didn't generate an error.  Please check your code before and after when this problem occurred.

@mjbvz It's a work related repository, so I can't share it publicly. Can I share it in some other way?
@Cookie-gg I've tried to convert all complex types to any to see if there was some circular reference going on - but it did not help. What was the issue you discovered? Maybe I have something similar in my code base.

Update: we have been using i18n for translations in our project, and in the past we have suspected that there might have been some performance issues with its typing. With version 23.0 the i18n-team also released some performance fixes related to typescript (we have been using version 22.4.9). This made me look into the versions of our other npm packages, and I noticed that we had quite a few outdated ones. Most notably we were still using react-native v0.69.9.
I decided to initialize a completely new repository using the latest react-native version (since updating react-native on a live project is an absolute nightmare), and thereafter copy all source code over from our old repository and reinstall all npm packages using the latest versions.
I can neither confirm nor deny that i18n was the culprit of our performance related issue - but the issue disappeared after I manually migrated our code to a new repository and updated every single npm package. It is quite easy to check for outdated npm packages using npm-check-packages - so if someone runs into a similar issue in the future, at least try this tool out.
It would have been nice to pinpoint where issue actually came from, but I'll close the issue since I've managed to resolve it.

This is an ongoing issue for the last 2 years. It would be nice if someone from the core team finally had a look into it.

@abalam666 I also tried to ignore 90% of my files using exclude in tsconfig and vsconfig, but it didn't solve the issue for me personally. Still no idea what caused the issues for my project, so I'm all for a verbose debug mode. 🤷♂


Wasim

Updates to CSS file, 2x2 grid and add images

Accidentally sent to main, resending to staging.


[Monitor OpenTelemetry] Update Statsbeat Instrumentation Mapping

Packages impacted by this PR
@azure/monitor-opentelemetry
Describe the problem that is addressed by this PR
We should have a mapping for 128 that is reserved for console instrumentation. This PR resolves that open instrumentation value.
Checklists

[x] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[x] Added a changelog (if necessary)

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


Fresh

Hello

Hello. Are you having an issue with the action? I did just update Application Inspector to .NET 6.0 and had not made the needed change here.  That has been done and it should now be working.

Not enough information.


are non-dis.gd discord domains relevant?

For example, http://watchanimeattheoffice.com which is linked just under "Battery Heat" in this article. It's currently a redirect to https://discord.com, and I'm sure I've noticed other domains like this in the past.
P.S. thank you for maintaining this list! It's been a helpful resource for grabbing discord's short links for their support, trust and safety, etc.

https://printer.discord.com is another - it currently has a presence in the list in the form of https://dis.gd/wumpus, but doesn't have an entry itself.

Hi there!
Thanks for the request, however I think keeping this list for keeping track of, and easily finding dis.gd links, might be for the best..?
And I know that there are currently LOTS of dis.gd links that I have missed - I've just simply not had the time to add them in as they arrived, heh
Cheers,
Hero