Work with 3rd-party frameworks

Hi,
Can I add 3rd-party frameworks to Embed Frameworks build phase & Embedded Binaries target section?

@rock88 Yes just add it to the list of files to be included and Xcake will add it for you

@jcampbell05 Thanks for answer!
I did it:
target.include_files << "Carthage/Build/iOS/Alamofire.framework"
But Alamofire.framework added only to Link Binary with Libraries, not to Embed Frameworks

@rock88  Ah, sorry I mis understood. I guess I'll have to expose a way of adding it to that phase.

We've exposed a new embed DSL in 0.8.8

How does the embed DSL work?

After some hunting, I found creating a block like this does the job.
target.copy_files_build_phase "Embed Frameworks" do |phase|
    phase.files = ["Carthage/Build/iOS/PromiseKit.framework"]
    phase.destination = :frameworks
    phase.code_sign = true
end

Would it be alright for me to try and roll up my sleeves and document some of these features in a way that's somewhat easier to discover?

Yes please


FOUNDATIONS: Typography

[ ] Investigate type size in interactive controls and buttons

[ ] Investigate type size in interactive controls and buttons


GH-3007: Ensure version specific Jackson classes are shaded

Rationale for this change
The current jar contains version specific classes under META-INF/versions/... with unshaded package names. This leads to clashes with jackson and thus classpath duplicates. This is a major problem in many major projects right now (e.g. Spark).
What changes are included in this PR?
Ensure these classes are shaded.
Are these changes tested?
Are there any user-facing changes?

Closes #3007

cc @wgtmac hey this is a pretty big issue for us. It is preventing us from taking other fixes. There might be a smarter way to do this but just wanted to kick this off - thanks 😄

@gszadovszky @Fokko Could you please help review this? Thanks!

@ted-jenks, have you tried this one?
Otherwise, I am fine with the current solution. My only fear is we'll forget to update with the new java versions. It would be nice if we could handle it with some automatism.

@gszadovszky I agree having the automation would be much better, but I cannot get that to work. When using <Multi-Release> the jar still have the unshaded classes. I think that the use of the relocations doesn't agree with it somehow? Not sure since it isn't really documented. The approach in this PR does work though.

Would it be possible to get a minor release of this? It is kinda dangerous to use the current release with anything that has a different jackson version.

@gszadovszky @Fokko @wgtmac any updates on this? sorry for pushing it is just blocking us taking some fixes right now.

@gszadovszky @Fokko @wgtmac 🙏🏻 would be super helpful to get this through

Sorry, @ted-jenks, I was on vacation. I've quickly checked the content of the jenkins jars on my local maven repo and found the following versions in META-INF/versions:
9, 11, 17, 19, and 21. Maybe, we should simply list every available java release here to be sure?
Unfortunately, I don't have time to manage a release currently. Maybe bring this up on the dev list after this PR went in.

@gszadovszky Thank you, I addressed your comment. (I work with Ted). https://github.com/apache/parquet-java/pull/3017/ . This is blocking us

For the next release, I think we can discuss on the dev@parquet ML. It may be the time to directly release 1.15.0 instead of 1.14.x

Closing this one in favor of #3017


Stopped running "final_logging"

This may be related to #157 but I don't want to make assumptions.
A different job (chr20) appears to be complete (it has finished delocalization) but appears to still be running because the "final_logging" could not be found (but still had an exit status of 0!?).
done: false
metadata:
  '@type': type.googleapis.com/google.genomics.v2alpha1.Metadata
  createTime: '2019-05-22T16:35:10.783867Z'
  events:
  - description: |-
      Stopped running "final_logging": environment: line 18: log_info: command not found
      environment: line 18: log_info: command not found
      environment: line 18: log_info: command not found
    details:
      '@type': type.googleapis.com/google.genomics.v2alpha1.ContainerStoppedEvent
      actionId: 8
      exitStatus: 0
      stderr: |
        environment: line 18: log_info: command not found
        environment: line 18: log_info: command not found
        environment: line 18: log_info: command not found
    timestamp: '2019-05-22T23:41:44.276607Z'
  - description: Started running "final_logging"
    details:
      '@type': type.googleapis.com/google.genomics.v2alpha1.ContainerStartedEvent
      actionId: 8
      ipAddress: ''
      portMappings: {}
    timestamp: '2019-05-22T23:41:39.647535Z'
  - description: Stopped running "delocalization"
    details:
      '@type': type.googleapis.com/google.genomics.v2alpha1.ContainerStoppedEvent
      actionId: 7
      exitStatus: 0
      stderr: ''
    timestamp: '2019-05-22T23:41:38.546159Z'

I should add that the gcp VM itself is still running / has not been terminated.

Thanks for reporting the problem.
The log_info problem was introduced in d3269e53a3dd68063a94b474fc1efd4825130259 and would be for all dsub jobs.
The problem of the VM continuing to run should be unrelated. You'll see the same error message in the underlying operation for all of your dsub jobs.
If the VM continues to run, you will likely need to terminate it manually and report the problem to Google.

Sounds good. Let's close this, then?

We'll close this issue when we've pushed out a fix for the failure of final_logging.
Thanks!

Good news - it eventually recognized that it was done and exited. The output file appears correct as well.

Sounds like this is fixed in f7f0ed4 if I read the release notes correctly?

Yes!


What is the principle of smv function and how does it work

Why can smv() calculate the duty cycle of SVPWM? I can't understand the working principle of this function. Do you have any reference materials to share?
The function is located in   >>   motorcontrol/Core/Src/foc.c
`void svm(float v_max, float u, float v, float w, float *dtc_u, float *dtc_v, float dtc_w){
/ Space Vector Modulation
u,v,w amplitude = v_bus for full modulation depth */
float v_offset = (fminf3(u, v, w) + fmaxf3(u, v, w))*0.5f;
float v_midpoint = .5f*(DTC_MAX+DTC_MIN);

*dtc_u = fast_fminf(fast_fmaxf((.5f*(u -v_offset)*OVERMODULATION/v_max + v_midpoint ), DTC_MIN), DTC_MAX);
*dtc_v = fast_fminf(fast_fmaxf((.5f*(v -v_offset)*OVERMODULATION/v_max + v_midpoint ), DTC_MIN), DTC_MAX);
*dtc_w = fast_fminf(fast_fmaxf((.5f*(w -v_offset)*OVERMODULATION/v_max + v_midpoint ), DTC_MIN), DTC_MAX);

}`

This is the simplest implementation of SVM.
This Microchip guide has good explanations of different SVM techniques, including this one:
https://microchipdeveloper.com/mct5001:start
https://microchipdeveloper.com/mct5001:which-zsm-is-best

I see. Thank you very much！！


RC3 issue to launch

Hi,
i've used the old version and had success.

IRPMmon version of 2017 works fine.
I'm now trying to used you latest version RC3.
But when I run the gui I get this

How to know which port it's listening to ?
If I click ok, I get in the Gui, but cannot select any drivers.
In CmdLine I get the following error
C:\Program Files\IRPMon\x64>irpmonc --input=D:\.\IRPMon
[INFO]: 10 parsers loaded
[INFO]:   EAParser (version 1.0.0)
[INFO]:   Hexer (version 1.0.0)
[INFO]:   KbdClass (version 1.0.0)
[INFO]:   PipesParser (version 1.0.0)
[INFO]:   MouClass (version 1.0.0)
[INFO]:   PipesParser (version 1.0.0)
[INFO]:   PnPDevCaps (version 1.0.0)
[INFO]:   PnPIDs (version 1.0.0)
[INFO]:   PnPInterface (version 1.0.0)
[INFO]:   SecDescs (version 1.0.0)
[INFO]:
[ERROR]: Unable to initialize IRPMon library: 2
My environment in a VM of Win10 x64 1903, running on a ESX host.
Regards

If you are not doing remote monitoring you should not use the network option. Instead IRPMon should connect directly to the driver.
If you don't have a "Device" tab between "None" and "Network" it can be because you haven't started IPRMon with administrative rights.


AOT compile fails

When I try to compile in AOT or --prod, the build fails with
ERROR in Unexpected value 'undefined' exported by the module 'TreeDiagramModule in .../node_modules/angular2-tree-diagram/angular2-tree-diagram.d.ts'
If I remove the --prod flag or the --aot flag, compilation goes through and everything works as expected.
How can I make this work?

Thanks for report. I'll look into it at weekend.03.02.2020, 17:15, "Abishek Goda" notifications@github.com:When I try to compile in AOT or --prod, the build fails with
ERROR in Unexpected value 'undefined' exported by the module 'TreeDiagramModule in .../node_modules/angular2-tree-diagram/angular2-tree-diagram.d.ts'
If I remove the --prod flag or the --aot flag, compilation goes through and everything works as expected.
How can I make this work?
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.
-- С уважением,Артём

I'am facing the same problem when trying do a production build.
Are there any leads on this issue?

Sorry guys, I forgot about it. I'll look into it today.On Feb 13, 2020 17:12, PrathameshAware<EMAIL_ADDRESS>wrote:I'am facing the same problem when trying do a production build.
Are there any leads on this issue?
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.

I updated the lib to angular 9 version and published it to npm. If you use source then you should run npm run build-lib first.

@artbelikov I updated to latest 1.2.0 version, but this is not solving the issue. Now I am getting few extra errors in addition to the last line after running ng build --prod

Impossibru. Okay, I'll try again today.

Well there is two points.
I have not encountered any errors upon building with --prod.
It is a common latest problem.
Try to update to the latest typescript/angular.
https://github.com/storybookjs/storybook/issues/9463

@artbelikov Well I tried upgrading from angular 8 to 9. Used typescript 3.7.2 and all various kinds of combination.
This are my dependencies in package.json after reverting back to angular 8
"dependencies": {     "@angular/animations": "^8.2.14",     "@angular/cdk": "^9.0.0",     "@angular/common": "~8.2.14",     "@angular/compiler": "~8.2.14",     "@angular/flex-layout": "^8.0.0-beta.27",     "@angular/forms": "~8.2.14",     "@angular/material": "^9.0.0",     "@angular/platform-browser": "~8.2.14",     "@angular/platform-browser-dynamic": "~8.2.14",     "@angular/router": "~8.2.14",     "@pxblue/themes": "^2.1.0",     "@syncfusion/ej2-angular-base": "^17.4.39",     "@syncfusion/ej2-angular-inputs": "^17.2.47",     "angular-csv-ext": "^1.0.2",     "angular-user-idle": "^2.2.1",     "angular2-tree-diagram": "1.2.0",     "core-js": "^2.5.4",     "crypto-js": "^3.1.9-1",     "highcharts": "^8.0.0",     "highcharts-angular": "^2.4.0",     "lodash": "^4.17.15",     "moment": "^2.24.0",     "ngx-daterangepicker-material": "^2.1.11",     "ngx-select-dropdown": "^1.3.0",     "ngx-toastr": "^10.2.0",     "rxjs": "~6.5.4",     "tslib": "^1.9.0",     "underscore": "^1.9.1",     "zipcode-to-timezone": "0.0.9",     "zone.js": "~0.9.1"   },   "devDependencies": {     "@angular-builders/jest": "^8.3.2",     "@angular-devkit/build-angular": "~0.803.21",     "@angular/cli": "~9.0.2",     "@angular/core": "~9.0.1",     "@angular/compiler-cli": "~8.2.14",     "@angular/language-service": "~8.2.14",     "@types/jasmine": "~2.8.8",     "@types/jasminewd2": "~2.0.3",     "@types/jest": "^25.1.2",     "@types/node": "^8.9.5",     "codelyzer": "^5.0.1",     "jasmine-core": "~2.99.1",     "jasmine-spec-reporter": "~4.2.1",     "jest": "^25.1.0",     "node-sass": "^4.13.0",     "protractor": "~5.4.0",     "ts-node": "~7.0.0",     "tslint": "~5.11.0",     "typescript": "3.5.3"   }
I tried angular2-tree-diagram with versions 1.1.0, 1.1.1 and latest 1.2.0 and each time I am getting consistent error on prod build only for TreeDiagramModule

Sorry for troubling again.

Maybe it will be faster for you to use sources. Cos I have full time job and cant support librarry very often. Go see how it builds demo page, see if there is any difference with your project.

I think I might have got what's the issue was:
I tried ng build --prod on source files and got below error -

Seems like TreeDiagramModule was incorrectly referenced. It should be
import { TreeDiagramModule } from 'projects/ng-tree-diagram/src/lib';

I think I might have got what's the issue was:
I tried ng build --prod on source files and got below error -

Seems like TreeDiagramModule was incorrectly referenced. It should be
import { TreeDiagramModule } from 'projects/ng-tree-diagram/src/lib';

Seems like the versions till 1.1.1 didn't support AOT (and thus prod build).
After upgrading my app to Angular 9 and using 1.2.0 everything is working fine.
Thanks and cheers @artbelikov ! 👍 😄


Authentication is required. error

Hi,
I can start the server and play on my local machine and do ngrok. But when i tried to deploy to giantswarm at the end of the process it gives this error. how can I solve this?
.....
....
Successfully built f7b9049acfc6
docker push registry.giantswarm.io/sayginburak/ogar
The push refers to a repository [registry.giantswarm.io/sayginburak/ogar] (len: 1)
Sending image list
FATA[0002] Authentication is required.
make: *** [docker-push] Error 1

Hello sayginburak,
sorry for the delay. You have to login to the registry with your docker client separately. Just do the following:
docker login https://registry.giantswarm.io
Username: <giantswarm username>
Email: <canbeempty>
Password: <password>

Afterwards you should be able to push. You can find more information here: https://docs.giantswarm.io/reference/registry/

@sayginburak double checking that you have a Giant Swarm account, correct? If not, I can address that for you.

Yes, I have a Giant Swarm account. I have already logged in to swarm. I did it again, but same error. Full output is here, I think this is not a login problem.
docker build -t registry.giantswarm.io/sayginburak/ogar .
Sending build context to Docker daemon 563.2 kB
Sending build context to Docker daemon
Step 0 : FROM google/nodejs
---> d579dbe02fb7
Step 1 : WORKDIR /Ogar
---> Using cache
---> c5acb67bbee2
Step 2 : RUN apt-get install git -y
---> Using cache
---> cd18a320a8ac
Step 3 : RUN git clone git://github.com/sayginburak/Ogar4.git Ogar
---> Using cache
---> bfe156707ac0
Step 4 : RUN npm install ./Ogar
---> Using cache
---> d828f213f5fc
Step 5 : RUN npm install ws
---> Using cache
---> d91ea5535a68
Step 6 : EXPOSE 443
---> Using cache
---> f1d4981f176e
Step 7 : ENTRYPOINT /nodejs/bin/node Ogar/index.js --game 0
---> Using cache
---> 59c14dc57b2b
Successfully built 59c14dc57b2b
docker push registry.giantswarm.io/sayginburak/ogar
The push refers to a repository [registry.giantswarm.io/sayginburak/ogar] (len: 1)
Sending image list
FATA[0004] Authentication is required.
make: *** [docker-push] Error 1

Hey,
random thought: Does your password have a questionmark? A colleague reported some problems with such a password and the registry, but I didn't have time to look into it.
Also, please check that the giantswarm registry is listed in your ~/.dockercfg.

Stephan

I have logged in with "swarm login" command. Now I tried the "docker login https://registry.giantswarm.io" and It worked. Thanks guys.

Great to hear! Hope you are back to eating dots.

Thanks for the feedback. I have created an internal ticket to make the process here more smoothly. :cake:


[ADAP-1064] [Bug] AWS IAM Assumed Role Authentication Issue in dbt-redshift with Serverless Redshift

Is this a new bug in dbt-redshift?

[X] I believe this is a new bug in dbt-redshift
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
When attempting to use an AWS IAM Assumed Role for authentication in dbt-redshift, the process fails. This issue does not occur when using AWS IAM User credentials. The expected behavior is for dbt-redshift to successfully authenticate using both IAM User and Assumed Role credentials. The failure with Assumed Role presents an obstacle in environments where Assumed Roles are a mandatory security practice.
Expected Behavior
Expected dbt-redshift to authenticate seamlessly with AWS Redshift using IAM Assumed Role credentials, similar to its functioning with IAM User credentials
Steps To Reproduce
Steps To Reproduce

AWS Configuration:

Set up the AWS configuration file (~/.aws/config):[profile myprofile]
region = us-west-2
role_arn = arn:aws:iam::123456789012:role/myredshiftrole
source_profile = mysourceprofile

dbt Profile Setup:

Configure the dbt profile in ~/.dbt/profiles.yml:dbt_project:
  outputs:
    dev:
      host: "serverless-redshift-cluster-host"
      user: "db_user"
      dbname: "db_name"
      port: 5439
      schema: public
      threads: 1
      type: redshift
      method: iam
  target: dev

Executing dbt Command:

Run the command: dbt build, targeting a model that connects to a serverless Redshift.

It is important to note that this issue specifically occurs with serverless Redshift.
Relevant log output
15:40:04  Running with dbt=1.7.3
15:40:04  Registered adapter: redshift=1.7.0
15:40:04  Unable to do partial parsing because env vars used in profiles.yml have changed
15:40:05  Found 1 model, 1 source, 0 exposures, 0 metrics, 455 macros, 0 groups, 0 semantic models
15:40:05
15:40:17  Concurrency: 1 threads (target='dev')
15:40:17
15:40:17  1 of 1 START sql table model public.last_100_users ............................. [RUN]
15:40:19  1 of 1 ERROR creating sql table model public.last_100_users .................... [ERROR in 2.91s]
15:40:22
15:40:22  Finished running 1 table model in 0 hours 0 minutes and 16.74 seconds (16.74s).
15:40:22
15:40:22  Completed with 1 error and 0 warnings:
15:40:22
15:40:22    Database Error in model model (models/staging/model.sql)
  permission denied for relation raw_model
  compiled Code at target/run/dbt_transformation/models/staging/model.sql

Environment
- OS:Mac OS 14.1.2
- Python: 3.9.16
- dbt-core: 1.7.3
- dbt-redshift: 1.7.0

Additional Context
No response

Moving the ticket up the queue!

@nbphuoc @sgahr sorry that you're not getting what you want from the new IAM auth options. To clarify, does assumed role auth work today for non-serverless clusters?
@jiezhen-chen pointed us to https://github.com/aws/amazon-redshift-python-driver/issues/192 in which someone was able to get assumed role working by calling sts_client.assume_role() before connecting. Ostensibly, something like this would need to happen within dbt-redshift to officially support assumed role auth. For that reason, we've changed this issue a "bug" to an "enhancement".
I'm also going to add the "help wanted" label, because while we'd love to support this feature, we don't currently have the bandwidth to address this.

when you run select * from pg_user;, you should see some user name like IAMR:myredshiftrole.
Then you should do GRANT permission to user IAMR:myredshiftrole.
The error you preset here like 'permission denied for relation raw_model'. It just saying your user in redshift no permission to that table.

This was added via https://github.com/dbt-labs/dbt-redshift/pull/781
Can be tested locally via install from source, should land in 1.9


Play a random album from an artist

Especially for audiobooks and radioplays, it would be nice to have something like "play an (random) album from {artist}".

I thought this is the default behavior when I play an artist?!?

It's not a single track if I recall correctly, it's the artists top tracks. So there's no way to play a single random track.

I see! then it definitive makes sense!


System theme doesn't resolved to light or dark in SSR

Describe the bug
If you set system theme on Settings page. It resolves in system in SSR. This means mismatch rendering on client.
To Reproduce
Steps to reproduce the behavior:

Go to /users/settings
Set system for theme in appearance section
Go to any goal page
See className error in console

Expected behavior
No errors.
Desktop (please complete the following information):

OS: MacOS
Browser: chrome

Impossible to reproduce


Hide cdpSession.send Actions in Playwright Test UI

Is your feature request related to a problem? Please describe.
After adding in Chromatic's Playwright test fixture, we now get a wall of cdpSession.send actions that we must dig through to find the relevant actions being run in a test.
Describe the solution you'd like
We would like these actions to be filtered out to reduce the noise when developing and debugging tests through Playwright's UI.
Describe alternatives you've considered
Based on this issue which asks for generic filtering of actions, I'm not sure you can do anything on your end at the moment.
I'm not sure what other alternatives there would be.
Additional context
Here are some screenshots showing with and without the fixture added.

With

Without

@chmmpagne this seems to be mostly resolved in https://github.com/microsoft/playwright/releases/tag/v1.46.0


How do I generate a list of true and predicted labels after calling ImageClassifier.create() ?

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
None
OS Platform and Distribution
Windows 10
Python Version
3.10
MediaPipe Model Maker version
No response
Task name (e.g. Image classification, Gesture recognition etc.)
Image Classification
Describe the actual behavior
ImageClassifier.create() and model.evaluate() implemented, but need only provides metrics for overall data
Describe the expected behaviour
Breakdown of true and predicted labels for each element in test dataset
Standalone code/steps you may have used to try to get what you need
model = image_classifier.ImageClassifier.create(
    train_data = train_data,
    validation_data = validation_data,
    options=options,
)

loss, acc = model.evaluate(test_data)
print(f'Test loss:{loss}, Test accuracy:{acc}')

import tensorflow as tf

metric_functions = model._metric_functions + [tf.keras.metrics.F1Score(),
 tf.keras.metrics.Precision(),
 tf.keras.metrics.Recall()]

model._model.compile(
    optimizer=model._optimizer,
    loss=model._loss_function,
    metrics=metric_functions,
 )

metrics = model.evaluate(test_data)
print(metrics)

Other info / Complete Logs
No response

Would like output in the format:

image
predicted_label
true_label

img1
dog
cat

img2
cat
cat

Hi there,
Any update on this?

Update?

Hi @Tess314,
Sorry about the delay. You will need to use model.predict to get the predicted_labels. Were you able to resolve the issue in https://github.com/google/mediapipe/issues/4930? That should get you the predicted_labels column, and true_label column will come from the dataset itself.

Hi @Tess314,
Let's continue the discussion in #4930. Please update with what is unclear and I will try to help. Just fyi, our team is quite small so we don't have the bandwidth to write detailed custom code for every user request. We can help answer questions, and have open sourced our codebase so users can look into how our stack is implemented and modify code if needed. Most of our codebase is backed by Tensorflow, so that is a good starting point to get familiar with the Model Maker code stack.


[1602] sentry is not receiving exceptions

Context
Sentry is not capturing exceptions since the upgrade from raven to sentry https://github.com/DFE-Digital/register-trainee-teachers/pull/748
Changes proposed in this pull request
Add sentry-ruby gem.
Add initializer with minimal config (including commit hash mapping)
Guidance to review

 Sentry is not receiving exceptions


improve pool loading

Summary by CodeRabbit

New Features

Enhanced efficiency of token data retrieval in the app, improving performance during asynchronous operations.
Introduced a caching mechanism for Uniswap fee percentages to reduce redundant network calls.

Bug Fixes

Streamlined fetching of token addresses, reducing delays in data acquisition.

error building up


Add instructions for running on single GPU

Description
Our code is designed to run on machines with 8 GPUs.
Add instructions for running on single GPU machine to make it easier to  debug / develop.

We'll just incorporate this into the FAQs.


Provide docker image and docs how to use it

Hi,
Could you please provide ready-to-use docker image and documentation how to use kubemarine with that docker image
I have managed to build, and figure out how to do that, but that took time.
docker run \
--mount type=bind,source="$PWD",target="$PWD",readonly \
--mount type=bind,source="$HOME/.ssh",target=/home/root/.ssh,readonly \
kubemarine install -c runner/cluster.yaml

where /home/root/.ssh is used inside  runner/cluster.yaml the following way:
node_defaults:
  keyfile: "/home/root/.ssh/my.key"
  username: "centos"

Hi, as for docker image, there are publushed here https://github.com/Netcracker/KubeMarine/pkgs/container/kubemarine in regular manner.
And as for documentation  yes, looks like we have a gap here. Will make an update. Thank you

Pls use https://github.com/Netcracker/KubeMarine#kubemarine-docker-installation


Error Handling for pvc creation from copysnapshot

PR Submission checklist
Error Handing for PVC Creation from Copysnapshot
GitHub Issues
List the GitHub issues impacted by this PR:

GitHub Issue #

https://github.com/dell/csm/issues/749

Common PR Checklist:

[X] Have you made sure that the code compiles?

[X] Have you maintained backward compatibility

Description of your changes:
Taken the Response from the OneFS, checking the weather response as success state as false, which means copy snapshot is failed. and collecting error messages from response JSON
In Failed case

In Success Case

Please remove all the Ip's from result screenshots . Please do run round of unit test with your changes.

Removed the  Ip's from result screenshots and run the make unit-test and it success

Please remove all the Ip's from result screenshots . Please do run round of unit test with your changes.

addressed


The generator's response is actually inconsistent

What version of Elysia.JS is running?
1.1.4
What platform is your computer?
Darwin 23.5.0 arm64 arm
What steps can reproduce the bug?
server.ts:
import Elysia from "elysia";

export const app = new Elysia().post("/stream", async function* () {
  yield {hello: "world"};
  yield {hello: "world"};
  yield {hello: "world"};
});

app.listen(2345);

client.ts:
import { treaty } from "@elysiajs/eden";
import type { app } from ".";

const client = treaty<typeof app>("http://localhost:2345");

const { data, error } = await client.stream.post();
if (!data) throw error;

for await (let item of data) {
  console.log(item, typeof item);
}

What is the expected behavior?
% bun run client.ts
{
  hello: "world",
} object
{
  hello: "world",
} object
{
  hello: "world",
} object

What do you see instead?
% bun run client.ts
{"hello":"world"}{"hello":"world"} string
{
  hello: "world",
} object

Additional information
Sometimes numeric responses are merged together into a single number, and sometimes json obejct responses are merged into a single string. The same goes for non-asynchronous.

will be fixed by #743 and https://github.com/elysiajs/eden/pull/114

will be fixed by #743 and elysiajs/eden#114

@remorses A similar problem occurs in response to new ReadableStream(), which I solved by adding an await delay(0) after each controller.enqueue()

@SaltyAom When I sleep before each yield, it prevents objects from sticking into strings, do you think this is a bug in Bun?
import Elysia from "elysia";

export const server = new Elysia().post("/stream", async function* () {
  yield { hello: "world" };
  await Bun.sleep(0);
  yield { hello: "world" };
  await Bun.sleep(0);
  yield { hello: "world" };
});


[WIP] Transform mode for image layer

Description
This builds on #3577 and starts enabling some of the functionality in the Qt-viewer. The main points are:

This implements a "transform" mode for the image layer
Keybindings are hooked up to allow zooming with "space" and fixed aspect ratio scaling with "shift"
A lot of errors related to nD-images are fixed

There are still quite a few rough edges, especially around nD-images, but I thought it might be a good point to get some feedback about what expected behavior with nD-images is (which kind of makes my head explode).
Type of change

[x] New feature (non-breaking change which adds functionality)

[x] This change requires a documentation update

References

How has this been tested?
I think this passes most tests, for some reason some tests on my machine always fail. I think there also should be some tests for the new behaviors.
Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

This is so awesome! Just gave it a play with. Two minor things are

it would be great if the corners of the box had a white fill and then changed to blue on hover. i believe we do that in our other layers (can come later if a pain)
it would be nice to have a "reset" shortcut, maybe cmd+shift+R

I think we can probably get this in now for image as is. I think it would be nice to extend to labels asap (which is basically the same as image). We could extend to all layers too, but that can maybe come later

There are still quite a few rough edges, especially around nD-images, but I thought it might be a good point to get some feedback about what expected behavior with nD-images is (which kind of makes my head explode).

I didn't notice any aside from after rotation - which is a known limitation. Everything seemed to make sense to me, maybe @alisterburt or @brisvag can check this out with some more real world data.
Code implementation looks very good too. I can take a finer look when it's ready, but I didn't see anything major off.
This will be so awesome for folks doing affine registration cc @jni @GenevieveBuckley!!

I think we can probably get this in now for image as is. I think it would be nice to extend to labels asap (which is basically the same as image). We could extend to all layers too, but that can maybe come later

Actually, I was wondering how people would feel about moving the mode property into the base layer (together with the Mode-enum). This way the same code could be reused for all layers.

* it would be nice to have a "reset" shortcut, maybe cmd+shift+R

Yes, a keyboard shortcut would be nice. I was thinking "Esc" or "Backspace", but not sure if they are already taken. I also thought it would be neat if right-clicking the transform-mode icon would show a context menu with an option to "Reset Transform". I have not looked into how to implement it.

* it would be great if the corners of the box had a white fill and then changed to blue on hover. i believe we do that in our other layers (can come later if a pain)

That would be nice as well as appropriate cursors. I think I saw a PR recently that implemented a custom cursor

Actually, I was wondering how people would feel about moving the mode property into the base layer (together with the Mode-enum). This way the same code could be reused for all layers.

Yes, I'd be fine with that. Thoughts @jni @tlambert03? I think it has been discussed elsewhere too. We can decide later if we want to expose the resize button on every layer controls in the GUI

Yes, a keyboard shortcut would be nice. I was thinking "Esc" or "Backspace", but not sure if they are already taken.

Yeah, they are in some layers. I think I still prefer cmd-shift-r as I see this is a reset (like an undo), whereas I see esc/ backspace as stopping an action or exiting something

I also thought it would be neat if right-clicking the transform-mode icon would show a context menu with an option to "Reset Transform". I have not looked into how to implement it.

Yeah we could do that, though I think that should be it's own PR. We don't expose any layer specific context menu items from the canvas yet I think. If we do this I think we might want to leverage some of the context machinery that @tlambert03 has been working on for right clicking in the layer list. We could actually add this to the layer list context menu right away. Still maybe best to do in a small followup PR, but that should be very easy

That would be nice as well as appropriate cursors. I think I saw a PR recently that implemented a custom cursor

Yes agreed - perfect

Actually, I was wondering how people would feel about moving the mode property into the base layer (together with the Mode-enum). This way the same code could be reused for all layers.

Yes, I'd be fine with that. Thoughts @jni @tlambert03? I think it has been discussed elsewhere too

I'd be ok with that.  I'm slightly less sure about the new mode buttons at the top of the image layer controls in the Gui.  Precious space...

I also thought it would be neat if right-clicking the transform-mode icon would show a context menu with an option to "Reset Transform". I have not looked into how to implement it.

I think we're getting close to a place where a Layer menu (in the main menu at the top) would be appropriate.  (And also close(r) to a global command palette).  This seems very well suited to those things as well

I'd be ok with that. I'm slightly less sure about the new mode buttons at the top of the image layer controls in the Gui. Precious space...

Yeah, we could get this PR in without the button first, and then decide on button in the followup PR. I am a little nervous about that as well, but don't want to hold this up for a lengthy design debate

I think we're getting close to a place where a Layer menu (in the main menu at the top) would be appropriate.

Yeah that could be cool too

I'd be ok with that. I'm slightly less sure about the new mode buttons at the top of the image layer controls in the Gui. Precious space...

If the transform works consistently across all layers, how about putting the button for it into the layerlist:

If the transform works consistently across all layers, how about putting the button for it into the layerlist:

That looks cool! Once nice thing could then be to adjust the transforms simultaneously for all selected layers. That could be super helpful if aligning multiple channels. Curious what others think here too - but it makes sense to me!!

* I assume we want the interaction box to update when `Layer.affine` is modified. That doesn't seem to happen yet. Is that as simple as connecting an event to make the interaction box overlay update? Or are there some unknowns/risks?

No, should be as simple as that. In my mind, the transform property of the interaction box and the affine property of the layers should be linked, i. e. the controller listens for changes in both and then updates the other one.

* The graphical design choices are non-trivial, so I think we should either find a way to get this in without graphically exposing the functionality, or get a little design feedback (e.g. in a community meeting).

Maybe the way to go is to remove the UI elements for now so that the transform mode can only be accessed by setting .mode of the layer to 'transform'. I'll be happy to demo this in a community meeting. Actually there are some other elements I would like to demo that I think are super important to make this an efficient registration system.

I think are super important to make this an efficient registration system.

I'd love to hear more about that in the meeting.
Another way to expose this functionality in the GUI (that I've seen in the past) is to have a whole sub-panel to control affine transform parameter values (e.g. a spin box for translate for each dimension). But given we have the API and a Python console embedded in napari, I don't think we need something like that and the extra complexity/design that goes with it.

Old related issue: #299.

Just had a look through the code, it looks like it's coming along nicely. It seems like you've dropped the qt stuff for now as we agreed.
Changes mostly look good. We can try and get this PR in now for "Image" only but I think we'll want to extend this mode to other layers too - but we can do that in a followup PR.
@jojoelfe are there more changes you'd still like to make here or is it ready for re-review?

There are are a few things I am still working on, which maybe could go in a future PR:

Making sure that updating the affine of the image layer also updates the interaction box: This mostly comes down to making sure that the controller connects to the affine event of the right layer and disconnects at the right time.
Preserve transform of non-displayed dimensions: For this I think I need a new function in the transform class. Would it be better to open a separate PR or add it to this PR?
Keyboard shortcut to reset transform

I should be able to get this done over the upcoming holidays, but if you want to review and merge right now I would be fine with that, too.

Thanks for the update - all this sounds good @jojoelfe, and some of the make sense in this PR I think. There's no rush, so if you want to do another round that would be great and we can check in then.

I think this is ready now for a review. The remaining issue on my end is a bug, where the box behaves like 'Shift' is pressed, which is probably related to #2893 and #2714 .
It probably would good to double-check the behavior in nD. At the moment when the layer is rotated in two dimension, after switching to other dimensions not all slices contain data and the displayed slice changes when the layer is translated. That probably does make some sense, but it is confusing because the displayed slice is no longer determined by the sliders at the bottom.

Also, I am using for now 'Ctrl-Shift-A' to start and stop align/transform mode and 'Ctr-Shift-R' to reset the affine transform of the active layer.

There are no events in the Affine instance, so this isn't something you could easily without some significant changes there. So I don't think you should do anything here, but it's worth thinking about in the longer term.

hmm yeah, we might need to make an issue on that one and followup in a new PR.

I understand that this is because pan and zoom are intimately connected. In general, I think we will need to modify the mode/callback management machinery a bit so that it's possible to have multiple callbacks attached in a given mode. Separating pan/zoom or expanding this machinery would definitely be beyond the scope of this PR though and I don't think this should block us moving forward here - this is high value stuff we should aim to get in peoples hands :)

yeah, good points. also maybe something for a followup
thanks both for the reviews!!

Thanks for the reviews, I think I addressed everything. @andy-sweet maybe you can check if you agree with everything?
I'm quite confused as to why the tests are failing. They succeed locally, but are failing in CI on a line that is not in the code...

Ok i think this is all done now, thanks for the work @jojoelfe and reviews @andy-sweet!!


Disabling vsync does not work on surfaces who doesn't support immediate mode

So as the title already states, a fix for this is using the MAILBOX mode if available.
I slightly modified the code in swapchain.cpp:
static VkPresentModeKHR ChooseSwapPresentMode(const std::vector<VkPresentModeKHR>& availablePresentModes, const std::vector<VkPresentModeKHR>& desiredModes)     {         for (auto& desiredMode : desiredModes)         {             for (const auto& availablePresentMode : availablePresentModes)             {                 if (desiredMode == availablePresentMode)                     return desiredMode;             }         }         if (availablePresentModes.size() > 0) return availablePresentModes[0];         else return VK_PRESENT_MODE_FIFO_KHR;     }
And using it this way:
std::vector<VkPresentModeKHR> desiredModes;         if (m_vsyncEnabled)             desiredModes = { VK_PRESENT_MODE_FIFO_KHR };         else              desiredModes = { VK_PRESENT_MODE_MAILBOX_KHR, VK_PRESENT_MODE_IMMEDIATE_KHR };         auto presentMode = ChooseSwapPresentMode(m_swapchainSupport.presentModes, desiredModes);         // Determine the total number of images required.         uint32_t imageCount = m_swapchainSupport.capabilities.minImageCount + 1;         if (presentMode == VK_PRESENT_MODE_MAILBOX_KHR) // Try to use tripple buffering with mailbox mode             imageCount = 3;
Unfortunately i have no idea how i can make a pull request, otherwise i would have done it. Sorry!

What platform and hardware are you using?

Windows 10 with the NVIDIA Geforce GTX 1070

I'll try to reproduce on my end as this seems like it could be a bug in NVIDIA's driver when using FIFO mode.

Thanks soconne,
i have another question. Is it possible to use the validation layers effectively when using vez? I have them enabled, but because vez is built as an dll i guess they are not working properly.

If you enable the validation layers the same way they’re enabled in the examples it should work.  I’ve had problems with them when installing a new Vulkan SDK over an existing version.  Uninstalling all Vulkan SDKs and then reinstalling only the latest has fixed the issue for me in the past.

Nope they doesn't work for me, even though i reinstalled 3x with different versions.
I had VezFramebufferCreateInfo.layers set to 0, which i spent several hours of debugging trying to figure out what's wrong... xD

VK_PRESENT_MODE_FIFO_RELAXED_KHR  does not disable vsync. As far as i understand it, it stills waits for every vsync cycle to update the screen, but with the exception if there's not an image in the queue, meaning the application might be too slow, a new request will be displayed immediately.
In my opinion the VK_PRESENT_MODE_MAILBOX_KHR is the best mode (with tripple buffering) anyway on desktop. If vsync is disabled please make sure this mode is used.

Rather than explicitly exposing a minimum image count in the API, I have added the tripleBuffer field to VezSwapchainCreateInfo.  I have also fixed the issue where MAILBOX was not being used for disabled vsync.  Let me know if this fixes your issue.

Thanks and yea i think it would if you would have been commited the header file (Swapchain.h) aswell xD I checked the commit, you just changed Swapchain.cpp ;-)
// Offtopic
How long do you think it will take to add suport for individual ubo/ssbo members? I'm at a point where i really need it, otherwise i can't continue. I`ll do it myself if you have no time, but of course i prefer an official solution. :-)

VEZ.h was missing from the commit.  It's now in.


issue with db_create

hello my name is yoav and i am from the Haifa Reali robotics team.
i tried to download the interop server on another computer and i have encountered an issue. when running the command :
 sudo ./interop-server.sh create_db
i get an error :
Creating server_interop-server_run ... done
2022-06-13 10:52:11,330: __main__: INFO: Health Check
2022-06-13 10:52:11,331: __main__: INFO: Checking postgres...
2022-06-13 10:52:26,382: __main__: INFO: Checking postgres...
2022-06-13 10:52:41,469: __main__: INFO: Checking postgres...
2022-06-13 10:52:56,542: __main__: INFO: Checking postgres...
2022-06-13 10:53:11,622: __main__: INFO: Checking postgres...
Traceback (most recent call last):
  File "./healthcheck.py", line 63, in <module>
    main()
  File "./healthcheck.py", line 57, in main
    check_postgres(args.postgres_host, args.postgres_user)
  File "/usr/local/lib/python3.8/dist-packages/retrying.py", line 49, in wrapped_f
    return Retrying(*dargs, **dkw).call(f, *args, **kw)
  File "/usr/local/lib/python3.8/dist-packages/retrying.py", line 212, in call
    raise attempt.get()
  File "/usr/local/lib/python3.8/dist-packages/retrying.py", line 247, in get
    six.reraise(self.value[0], self.value[1], self.value[2])
  File "/usr/lib/python3/dist-packages/six.py", line 703, in reraise
    raise value
  File "/usr/local/lib/python3.8/dist-packages/retrying.py", line 200, in call
    attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
  File "./healthcheck.py", line 21, in check_postgres
    subprocess.check_call(
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['pg_isready', '-q', '-h', 'interop-db', '-U', 'postgres']' returned non-zero exit status 2.
ERROR: 1

what should i do?

i fixed the issue


Documentation needed for quantum_cond_entr

https://github.com/cvxpy/cvxpy/blob/14124e110fc1efe0e1cfac1be8414ad9109969ff/cvxpy/atoms/quantum_cond_entr.py#L12-L20
@aryamanjeendgar this atom is not properly documented. It also fails silently if sys is neither 0 nor 1. Please fix.

Ping @aryamanjeendgar


Saving and previewing flex-pages does not work on Windows

When flex-pages are enabled, saving and previewing pages does not work.

Info
Windows 10 x64
PHP v7.4.0 (on built in server)
Grav v1.7.0-rc.2
Admin v1.10.0-rc.2
All tests were performed on a clean installation.

This is a duplicate of issue https://github.com/getgrav/grav/issues/2736

I believe this is also related to #2773

Yep, in Grav v1.7.0-rc.3 this problem is fixed.


[DRAFT] AMI builder using Packer

Description
Create packer config files (.hcl) to create custom AMI. Includes other files that installed on AMI and needed for OpenSearch nodes to bootstrap.
Issues Resolved
#11
Check List

[ ] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Need to close this as this PR is not accepting new commits after repository was changed from private to public.


Branding typography

fix #134
fix #125
fix #124
fix #123
fix #122
The new typography was introduced by https://github.com/src-d/sourced-ui/pull/106, but some days later it was reverted by https://github.com/src-d/sourced-ui/pull/128, so its changes were rollbacked.
Original changes made by https://github.com/src-d/sourced-ui/pull/106 were: 555765c25772120e699ef00164e622739a524304 450de62cee59cb1e01f453e98ded99c40e2a6559 43ba635032dabf0970c378425ec64572357a2807 a20fde3579c84f0aaf4c16943203facc85ea33ae ec5d9ed75e77bc37e786cb2a95763e19bf07ca0f 0414d65ee72f4dd9156f063459d5805938d02a74
After being reverted, an extra commit was applied on top of those ones: abb3431bd47b98bf6a6551f3a2a3069de9964672 to address the problems described by #125 #124 #123 #122
As requested by #134, I took the old work and applied on top of the current master in order to validate and merge it.

click to see more details of how the previous commits were rearranged on top of `master`
1. I took all the old six commits from above and rebase-squashed them into: d8b774bd
2. And then applied abb3431bd47b98bf6a6551f3a2a3069de9964672 → c828320a on top, to fix the described problems.
3. Create this PR with the new two commits, containing the old and outdated commits.

Some screenshots testing it over the current sourced v0.14.0-beta.5
Old view:

New view:

New collaboration dashboard:

Let me know if I should do any other testing, please.

plz this one as well https://github.com/src-d/sourced-ui/issues/113
also try to click on dropdowns and other stuff on charts creation page to makes sure nothing is broken there

according to screenshot, #114 and #118 aren't fixed, right?

according to screenshot, #114 and #118 aren't fixed, right?

No @smacker , we talked about this and we agreed that chart fixing with be easily taken care by you. Can you confirm, please?

@ricardobaeta
as it is described in #114 apparently it isn't easily fixable on our side, my initial guess was wrong.
#113 is important. As I described in the comment it prevents modifying/creating a chart with a long title. And it's not always possible (for example on my laptop) to make the browser window bigger to workaround the problem. In pre-redesign, similar issue exists but much less bad. The chart also gets moved down but x-axis is still visible.

@smacker please have in mind @dpordomingo comment on #113.

David said exactly the same what I did in the comment above but in more words:

bug exists in master too
solution is Long title s...

I think we should not block the typography redesign by issues that are already happening in current master or are not caused by that redesign itself.
Considering that:

#113 (On chart edit page a chart isn't visible fully) → not caused by the redesign, more details, and possible workaround at https://github.com/src-d/sourced-ui/issues/113#issuecomment-504024504
#114 (Tables overflow the chart container) → already addressed by 2e1a31e
#118 (Summary chart overflow) → not a css issue but a dashboard layout problem (solved by #129).

My proposal for this PR:

test it deeply with latest sourced-ce and our two available dashboards.

Confirm that already known regressions are solved:

#114 (Tables overflow the chart container)
#125 (Top menu looks incorrect)
#124 (Close button is not clickable)
#123 (Incorrect table headers)
#122 (Buttons looks like wrong)

Perform an extra sanity check

dropdowns, chart creation section, uast... and such

Merge
Do not block for non regressions:

#113 (On chart edit page a chart isn't visible fully)
#118 (Summary chart overflow)

@dpordomingo agreed.

Let's rebase on master and check with new charts. For the rest looks like everybody agrees it's good to go already and we can merge.

I rebased over current master,
built a new image and tried it with new sourced,
confirmed that all blockers described by (2) at https://github.com/src-d/sourced-ui/pull/139#issuecomment-504033936 are still solved,
quick sanity check (3) confirming that there are not huge outages in:

our current 3 dashboards,
chart creation,
dashboard creation and reordering charts
running queries in SQL Lab
viewing UASTs

imo this is ready again to be considered as good to go.

Since https://github.com/src-d/sourced-ui/pull/142 was made on top of this one, you might prefer to deeply test the other one, and approve this one if #142 pass your tests :D

I leave here, per @smacker requirement, some screenshots showing how blocker issues were solved, and how the new UI looks like if this and https://github.com/src-d/sourced-ui/pull/142 are merged.
#125 (Top menu looks incorrect)
#122 (Buttons looks like wrong)

#124 (popups with not clickable close button)

#123 (Incorrect table headers)

Collaborative dashboard

Overview dashboard
#114 (Tables overflow the chart container)

Welcome dashboard

Chart creation

Bblfsh tab

SQL Lab

@dpordomingo @smacker @carlosms I've just noticed that the Title on the Welcome Dashboard is not using Source Sans Pro.
On the welcome dashboard markdown files we have:
.dashboard-markdown .dashboard-component.dashboard-component-chart-holder h1 {
    margin-top: 24px;
    margin-bottom: 24px;
    line-height: 1.6;
    font-size: 30px;
    font-weight: bold;

And we just need to add:
font-family: Source Sans Pro, Helvetica Neue, Arial, sans-serif;

Before:

After:

I see the UAST tab changes some of the global styles. I have only noticed it in the top-right "New" button, it gets bigger. But there might be other places:

Why don't we fix #118 in this PR too @dpordomingo? I mean editing the chart height in the dashboard json.

I've noticed the sql lab results table now has an extra outer scrollbar. See before:

And after:

I've found a missing change in button height. In this case it's a minor thing, but it means there might be other places where buttons are not consistent.
Before:

After:

Looking great. :)
Regarding the inconsistencies at @carlosms has shown… @dpordomingo @ricardobaeta would this be something that we would fix/avoid by figuring out the puzzle with the "global variables" (i.e. being able to properly set/propagate styles top-down) first?

jfyi

extra outer scrollbar

I experienced this before (not sure if with current sourced-ui or the one based on previous superset 0.32)

Also as can be seen in the previous comment https://github.com/src-d/sourced-ui/pull/139#issuecomment-506671899, the UAST button inside the results table now overlaps one row with the next one, and does not look as neat.

Do we want to release the branding once we can guarantee that it has 0 errors? or do we assume that there can be small issues to be solved in an iterative process?
I understood that it was accepted that some parts could be addressed separately as long as it would not impact heavily in the UX. I assume that we considered it because it was agreed that the benefits of having a rebranded site, are higher than the costs of having some dangling elements, pending to be adapted.
Do the arisen issues cause more damage, than the benefit of the rebranding as this PR and https://github.com/src-d/sourced-ui/pull/142 propose?
For sure I'm not saying that we should not fix any small problem we find, nor they're not important, nor we should not deeply review the design. What I think is that we should consider if those issues impact more to the user than the benefit of merging and then continue improving in shorter iterations.
Once said that, let's consider each reported issue:

[ ] #183(UAST tab changes some global styles)
[ ] #186 (UAST buttons in result tables has no margins)
[ ] #118 (Summary chart overflow)

we could change dashboards charts in this PR, but I think it would be better if done in a separate PR #187. Why? I think it's better to separate theming PR from dashboards (e.g. since this PR increase the fonts, we could also consider increasing other charts, and not only this one, like proposed by https://github.com/src-d/sourced-ui/issues/162)

[ ] #184 (Extra outer scrollbar in SQL lab results)

that problem already exists in srcd/sourced-ui:v0.3.0-rc.1 as described in the issue.

[ ] #185 (Buttons does not keep the size on action)

the problem appears now in two axes, but it was previously happening in one because x-axis should not change on action.

Should we block this PR until we deeply review this redesign to ensure there is no other issue like the ones reported above? Are we going to exhaustively review all the PRs addressing the rebranding? Or are we only doing sanity checks before merging, and considering the rebranding as something that will be done iteratively?


Can you add a proper readme and a guide on how to use this ?

I will add a getting started with a simple walk through.
Thanks for bringing it up :)

@Fullstak-nl Thanks and it'll be really helpful for people using this plugin.  I installed the plugin and configured medusa-config.js with the code snippet you provided (removed unnecessary values as follows). I set up POSTMARK_SERVER_API with postmark server API token, POSTMARK_FROM with my postmark email and POSTMARK_ORDER_PLACED with the relevant template id in postmark. But still it does not send the email. Anything else to configure ?
{
    resolve: `medusa-plugin-postmark`,
    options: {
      server_api: process.env.POSTMARK_SERVER_API,
      from: process.env.POSTMARK_FROM,
      events: {
        order: {
          placed: process.env.POSTMARK_ORDER_PLACED || null,
          canceled: process.env.POSTMARK_ORDER_CANCELED || null,
          shipment_created: process.env.POSTMARK_ORDER_SHIPMENT_CREATED || null,
        },
        customer: {
          created: process.env.POSTMARK_CUSTOMER_CREATED || null,
          password_reset: process.env.POSTMARK_CUSTOMER_PASSWORD_RESET || null,
        },
        user: {
          password_reset: process.env.POSTMARK_USER_PASSWORD_RESET || null,
        },
      },
      default_data: {
        // ... default data to be passed to the email template
        product_url: process.env.POSTMARK_PRODUCT_URL || "",
        product_name: process.env.POSTMARK_PRODUCT_NAME || "",
        company_name: process.env.POSTMARK_COMPANY_NAME || "",
        company_address: process.env.POSTMARK_COMPANY_ADDRESS || "",
      },
    },
  },

Do you run redis for the events?
And did you set the correct template id for your email?
POSTMARK_ORDER_PLACED needs to be set to a postmark template that will be sent when an order is placed.

@Fullstak-nl I did not run a redis. Thought they have an event bus for development purposes. Is it required to run a redis ? I set up the template id correctly

I noticed events are not fired sometimes when redis isnt used.
Could you please check with redis enabled?

You are most welcome :)


[Select] Form Control examples that contain Select do not pass WAVE accessibility for labels

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
Using wave on the Select component examples has the error on all select fields
Missing form label
A form control does not have a corresponding label.
I was finally able to fix the issue like this
<FormControl sx={{ minWidth: 120 }}>
  <InputLabel id={'label-for-category'} htmlFor={'category-select-input-id'}>Category</InputLabel>
  <Select
    label={'Category'}
    labelId={'label-for-category'}
    id={'category-select'}
    value={state.category}
    inputProps={{'id': 'category-select-input-id'}}
    onChange={(event) => handleChange(event, 'category')}
  >
    <MenuItem value={''}>
      None
    </MenuItem>
    <MenuItem value={10}>School</MenuItem>
    <MenuItem value={20}>Work</MenuItem>
    <MenuItem value={30}>Vacation</MenuItem>
  </Select>
</FormControl>

Where I needed to add an htmlFor to the label and add the associated id to the inputProps of the Select
The only select examples that do not have this error are the native examples because they have aria-label on them.
Expected behavior 🤔
Examples to pass WAVE when on the bottom of the page there are directions on how to pass accessibility but these in fact don't work for the form Control label. Removing them actually doesn't add any errors.
Steps to reproduce 🕹
Steps:

Go to Select component model example page
Run Wave

Context 🔦
Proper examples for accessibility
Your environment 🌎

`npx @mui/envinfo`
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

The reason is that the id prop isn't broadcasted down to InputComponent (from here).
When using the native prop, the id would be broadcasted down to the select element and associated with the label. But it might lead to other issues:

The list items are rendered as a li with menuitem role instead of option element —> not able to open the menu 🤦🏽♂
There’re new issues that are kind of similar to the original issue...

How come there hasn't been any movement on this issue? Does the mui project not care about accessibility?
Judging from @luchn49 's comment it doesn't seem to be a documentation issue only, but a fundamental design problem.
As my project wants (and needs) to take accessibility seriously, such issues really cause a big pain for us, as we rely heavily on mui components.

Any update on this issue on July 2024 ??

Are there any updates on this issue? I am still encountering this problem in MUI V6.1.6.

I agree would love to know how to fix this so we can get make our compliance office happy

I think I have found a solution that is not included in the documentation.
For example this is the basic select provided in the documentation. If you use WAVE to test you will get the alert of Missin form label and orphaned label.
<FormControl fullWidth>
  <InputLabel id="demo-simple-select-label">Age</InputLabel>
  <Select
    labelId="demo-simple-select-label"
    id="demo-simple-select"
    value={age}
    label="Age"
    onChange={handleChange}
  >
    <MenuItem value={10}>Ten</MenuItem>
    <MenuItem value={20}>Twenty</MenuItem>
    <MenuItem value={30}>Thirty</MenuItem>
  </Select>
</FormControl>

Instead of adding the id as stated in the documentation you can use inputProps to add the
 inputProps="demo-simple-select"
and on the inputLabel component add the following
htmlFor="demo-simple-select"
The final component looks like the following and it seems to make WAVE happen. Let me know if anyone has any thoughts.
<FormControl fullWidth>
   <InputLabel htmlFor="demo-simple-select" id="demo-simple-select-label"> Age </InputLabel>
     <Select
       labelId="demo-simple-select-label"
       value={age}
       label="Age"
       inputProps={{ id: "demo-simple-select" }}
       onChange={handleChange}
    >
       <MenuItem value={10}>Ten</MenuItem>
       <MenuItem value={20}>Twenty</MenuItem>
       <MenuItem value={30}>Thirty</MenuItem>
    </Select>
</FormControl>;

@guillenjs
Sounds good for me (with a color defined in style={{ }} ) into InputLabel -> 100% accessibility in Lighthouse Report
👏


Week 3: Telemetry Dashboard(Sunbird UCI)

Project
Telemetry Dashboard
Changes
Week 3 updates

@Apoorvgarg-creator Please review it.


Treat JSON string parsing as a special case

consumeStructure should be simple with no knowledge of the special
requirements for string parsing. We'll handle it directly in parseString
instead.

@swift-ci please test


Any class type is consider a subtype of a generic indexer

Am I missing something, or is this a case where flow's analysis is unsound?
function test<T>(input: {[string]: T}) {}

class Foo {
  n: number;
  b: boolean;
}

test(new Foo);

https://flow.org/try/#0GYVwdgxgLglg9mABFApgZygHgCoD4AUMYADiFAFyIDeA2hgE5EDmAupdgL4CU1HAUHwgAbAIZo0iAGJw41PokRhKYEAFsARinoBueYnWV1MoShFhd-Pqgz4wKAO5SZXbUA
When Foo is an equivalent object type, it's (correctly) an error:
function test<T>(input: {[string]: T}) {}

type Foo = {
  n: number;
  b: boolean;
}

const foo: Foo = {n: 0, b: true};
test(foo);

https://flow.org/try/#0GYVwdgxgLglg9mABFApgZygHgCoD4AUMYADiFAFyIDeA2hgE5EDmAupdgL4CU1HAUHygBPYikQAxOHEQBean0SIwlMCAC2AIxT0A3AsQbKGqQBsUAQzB7+fCAgyJgUypOlyqyxAAYANAcpQ9CAoHHqoGPhOcFw6QA

To more obviously see why it's problematic, the first case was reduced from something similar to:
function eachValue<T>(input: {[string]: T}, fn: (T) => void) {
  for (const k in input) {
    fn(input[k]);
  }
}

class Foo {
  n: number;
  b: boolean;
}

eachValue(new Foo, (n: number) => {});

https://flow.org/try/#0GYVwdgxgLglg9mABAUwIYQBYDVUBsTIA8AKgHwAUMYADiFAFyIDeA2gM5QBOVA5gLqNiAXwA0iYGEbliASkQBeUogBucGABM5TAFCJxcTonIQEHRAGtEVKzTpbde8WEq2oLc3xkBuB0O1-tCFxUNjZEADE4OGYHSUQwEABbACNkTh89ZMZkqNw0MB8AtEwcfGRyMGQAdwiosQrGBJS0uUVmIW8gA

Simpler example:
class Foo {
  n: number;
}

var x: { [string]: string } = new Foo;

It seems that class properties are simply ignored, the same with interface.

They are both banned now.


Fix errors in preliminary user types

remove reference to constructor argument in index
maybe remove by name, because that one should no longer exist

done in experimental


Resolution correction

640x512 is standard 50Hz PAL resolution however the demo appears to be running at 60Hz (480i) - I have corrected the resolution to be 640x448 as per standard 60Hz PS2 games (not 640x480, 640x448 for overscan compensation). This may free up a little more VRAM (40,000 less pixels after all) and probably yield marginally better performance?

Thank you so much for this PR and your recommandations (#18) !


AzureResourceManager: Adding Private postgres db support for Artifactory and Xray templates

PR Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Title of the PR starts with installer/product name (e.g. [ansible/artifactory])
[ ] CHANGELOG.md updated
[ ] Variables and other changes are documented in the README.md

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

This solution has been deprecated.


chore(weekly): add blog post for 11th week of ‘24

Closes packit/agile#501

@mfocko can we merge this?

@mfocko can we merge this?

yup… I had a feeling I forgot about it /o