Please add another example to README.md

Hi,
I've ported my fantasy console to sokol, if it's not too much trouble for you, could you please add it to the readme under section "Examples"?
diff --git a/README.md b/README.md
index d9ac024..f9366fb 100644
--- a/README.md
+++ b/README.md
@@ -24,6 +24,8 @@ cross-platform libraries for C and C++, written in C.

 - [Tiny 8-bit emulators](https://floooh.github.io/tiny8bit/)

+- [MEG-4](https://bztsrc.gitlab.io/meg4) a virtual fantasy console emulator in C89, ported to sokol
+
 - A 'single-file' [Pacman clone in C99](https://github.com/floooh/pacman.c/), also available in [Zig](https://github.com/floooh/pacman.zig/)

 - A [Minigolf game](https://mgerdes.github.io/minigolf.html) ([source](https://github.com/mgerdes/minigolf)).

I'm already linking back to your github repo in my readme, but if you would like any more attribution, please let me know!
Cheers,
bzt

Fixed! Thanks!


feat: Generate easier to read plural names (Fancy Pluralization).

Example: "Universitys" should now become "Universities".

Looks good - 2 points:
1 - I moved the docs from gh-pages to a subdir named docs. Could you add to the docs readme some docs about this feature please.
2 - src/utils/buildIndexFromPath.ts is where the main work is happening, could we get a small unit test on the pluralisation checks either by extracting the pluralisation from the file to its own helper or testing the whole buildIndexFromPath?

noice


Dev to main sync

Date:

Developer Name:

Issue Ticket Number

Description

Documentation Updated?

[ ] Yes
[ ] No

Under Feature Flag

[ ] Yes
[ ] No

Database Changes

[ ] Yes
[ ] No

Breaking Changes

[ ] Yes
[ ] No

Development Tested?

[ ] Yes
[ ] No

Screenshots

Screenshot 1

Test Coverage

Screenshot 1

Additional Notes

@Nikhil-Kumar1 Can you please verify your changes in staging and also update the description of this PR?

Issue Ticket Number

Closes #827

PR's going in this sync

#837

Screenshots

Screenshot 1
Tested in staging.
https://github.com/user-attachments/assets/7b8ed678-9b04-455a-a8c1-efea3052cb9c

@sahsisunny

Issue Ticket Number

Closes #823

PR's going in this sync

#826

Documentation Updated?

[ ] Yes
[x] No

Under Feature Flag

[ ] Yes
[x] No

Database Changes

[ ] Yes
[x] No

Breaking Changes

[ ] Yes
[x] No

Development Tested?

[x] Yes
[ ] No

Screenshots

Screenshot 1

https://github.com/user-attachments/assets/873630c5-6a49-4456-9fd1-387e05acfb74

Mobile View

cc: @sahsisunny


add a script to automate compilation

as title

Is the script working at the moment ? the very last step (triton build) errors out with /usr/bin/ld: cannot find -lz: No such file or directory, but zlib is installed in my environment.

Hi, tried it again today but compilation of ipex failed with:

no member named 'QXPU' in 'c10::QEngine'

[ 97%] Building CXX object csrc/gpu/CMakeFiles/intel-ext-pt-gpu.dir/aten/operators/SoftPlus.cpp.o
[ 97%] Building CXX object csrc/gpu/CMakeFiles/intel-ext-pt-gpu.dir/aten/operators/SoftShrink.cpp.o
[ 97%] Building CXX object csrc/gpu/CMakeFiles/intel-ext-pt-gpu.dir/aten/operators/SparseCsrTensorMath.cpp.o
/home/u103857/triton_compiler_2/intel-extension-for-pytorch/csrc/gpu/aten/operators/QConv_prepack.cpp:129:3: warning: use of function template name with no prior declaration in function call with explicit template arguments is a C++20 e
xtension [-Wc++20-extensions]
  register_prepack<2>(
  ^
/home/u103857/triton_compiler_2/intel-extension-for-pytorch/csrc/gpu/aten/operators/QConv_prepack.cpp:130:20: error: no member named 'QXPU' in 'c10::QEngine'
      at::QEngine::QXPU,
      ~~~~~~~~~~~~~^
/home/u103857/triton_compiler_2/intel-extension-for-pytorch/csrc/gpu/aten/operators/QConv_prepack.cpp:129:3: warning: use of function template name with no prior declaration in function call with explicit template arguments is a C++20 e
xtension [-Wc++20-extensions]
  register_prepack<2>(
  ^
/home/u103857/triton_compiler_2/intel-extension-for-pytorch/csrc/gpu/aten/operators/QConv_prepack.cpp:132:3: warning: use of function template name with no prior declaration in function call with explicit template arguments is a C++20 e
xtension [-Wc++20-extensions]
  register_prepack<3>(
  ^
/home/u103857/triton_compiler_2/intel-extension-for-pytorch/csrc/gpu/aten/operators/QConv_prepack.cpp:133:20: error: no member named 'QXPU' in 'c10::QEngine'
      at::QEngine::QXPU,
      ~~~~~~~~~~~~~^
/home/u103857/triton_compiler_2/intel-extension-for-pytorch/csrc/gpu/aten/operators/QConv_prepack.cpp:132:3: warning: use of function template name with no prior declaration in function call with explicit template arguments is a C++20 e
xtension [-Wc++20-extensions]
  register_prepack<3>(
  ^
/home/u103857/triton_compiler_2/intel-extension-for-pytorch/csrc/gpu/aten/operators/QConv_prepack.cpp:136:20: error: no member named 'QXPU' in 'c10::QEngine'
      at::QEngine::QXPU,
      ~~~~~~~~~~~~~^
4 warnings and 3 errors generated.
make[2]: *** [csrc/gpu/CMakeFiles/intel-ext-pt-gpu.dir/build.make:2721: csrc/gpu/CMakeFiles/intel-ext-pt-gpu.dir/aten/operators/QConv_prepack.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:594: csrc/gpu/CMakeFiles/intel-ext-pt-gpu.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

Can we close this PR? Is old and there is no recent activity.

Closing (see https://github.com/intel/intel-xpu-backend-for-triton/pull/83#issuecomment-1894090738).


[pt] Removed Weave Scope link

https://github.com/kubernetes/website/pull/47923/files

Thanks!
/approve


test(blocking): tests for blocking append

Although there are not many services having native implementations of blocking_write now, we still need to cover them.
(because append has been merged into write).

https://github.com/apache/incubator-opendal/blob/1bb63ab676293cb20cb90fbb177d58bd25340c8c/core/src/services/fs/writer.rs#L57-L68
For the service fs, doing append will go wrong definitely here if we enable atomic_write.

It's better to set a new test job for atomic_write.

Negative, this is a violation of our VISION. We can't add different test for services with different configure values.

For the service fs, doing append will go wrong definitely here if we enable atomic_write.

It's a bug. We should fix it from fs internal.


Please remove log4j.xml from the project

Please remove log4j.xml from the project. There is no reason for a project that's going to be included as a library into another one to define its own log4 file. If there are multiple log4 files the classloader will just choose one of them and.

sure this makes sense. Do you want to try and put up a PR for it?

https://github.com/edmunds/databricks-rest-client/pull/60

thanks!


Bug: Clearing search results with the "x" button does not reset search

When searching for workflows/tasks, if a user clears the search query the expected behavior is to refresh/reset the results (and this works if a user interacts with the text input (ie, deletes the string value) however if they click the "x" button to clear the input the results do not refresh.
Video: https://share.getcloudapp.com/BluGrALN

merged with https://github.com/flyteorg/flyteconsole/pull/564


bytes: Buffer.Reset() + .Write() yields incorrect contents

What version of Go are you using (go version)?

$ go version
1.14.2 playground

Does this issue reproduce with the latest release?
Yes
What did you do?
Call bytes.Buffer.Write(), then .Reset(), then .Write() again.
In main() below see /// uncomment this line to fix
https://play.golang.org/p/olAPV2gVXjY
What did you expect to see?
Buffer has only data written after .Reset().
What did you see instead?
Buffer has mix of data from before and after .Reset().

Temporarily closed for further debugging...


FEAT: create partial deposit instruction

Changes
Checklist

[ ] UAT
[ ] Passes final QA checks

Task linked: CU-1tf0dqf SCORE: Partial deposit after fleet already deposited


Fix loading screen & add extra validations during initial loading

fixes #106
improve the loading screen function

add checkpoints on permission to fileview and certification of users
change 'login' to 'landing'

fixes: tryCatch not prevent app from crashing and show proper loading screen

@rrchai thanks! This will be a pretty useful screen for users that don't have access. Can we have a message along the lines of
Looks like you don't have sufficient permissions for curation. Please contact your team and project administrators.

@ychae could you take a look if this makes sense from a user perspective?

@milen-sage Just to make sure I understand what this PR accomplishes:

Checks to see if the user is Certified on Synapse. If true, they'll continue to the data annotation process. If false, the user will be directed to go certify their account immediately after the loading screen.
Checks to see if the user has sufficient permissions to access the files and folders and projects necessary for curation. If true, the user continues on with the data annotation process. If false, the user is directed to contact someone to be granted the necessary permissions.

@rrchai I like the language that Milen suggested for the permissions issue. For the certification notification, could we say: It looks like you're not a Certified User on Synapse. Please follow these instructions (the link that you have) to become a Certified User. Once you're certified, return here and refresh this page.

@milen-sage To actually answer your question, if my understanding above in points 1 and 2 are correct, it seems like a great addition to improve usability and user experience!

Thanks for pointing out the distinction between the user access and user certification @ychae! This makes a lot of sense.
Agreed - this PR overall would avoid a lot of explanation and debugging we otherwise have to do w/ users.


LCFS - Analyst transfer recommendation to the director

Description:
Develop the analyst recommendation section on the view transfer page and the ability for the analyst to make a recommendation on a transfer.

'Analyst Recommendation to the Director' heading
'Recommend Record' and 'Recommend Refuse' radio buttons
'Recommend' button in the bottom right hand corner of the page
Clicking on the 'Recommend' button brings up a confirmation modal window
Clicking the cancel button in the modal window brings the user back to the view transfer screen
Clicking on the 'Recommend' button in the modal window (1) brings up a success message/alert/modal, (2) The user is returned to the transaction page, (3) The transaction row for the transfer is highlighted, and (4) the transfer status is changed to Recommended.
A transaction history record is saved to the database and visible in the UI when viewing the transfer: Recommended on [Month DD, YYYY] by [User] of [Organization]. This record is based on the IDIR user with the Government Analyst role that clicked the Recommend button.
This recommendation transaction history record is only visible to IDIR users
The comment free text field (government comments to organizations) is saved to the database, if there is a comment added (see card #261 for development of this feature).
The two radio buttons are no longer selectable; they are greyed out, with the single selection made
Success alert from Material UI: https://mui.com/material-ui/react-alert/
The transfer breadcrumb within the view page is updated to the Recommended state for IDIR users only; the transfer remains in the Submitted state for BCeID users

Data Validation & restrictions:

Only IDIR users with the Government Analyst role can make recommendations (select the radio buttons, click on the Recommend button)
Only one radio button can be selected (either Recommend Record or Recommend Refuse, but not both)
One of the radio buttons must be selected before the analyst can click on the Recommend button (greyed out until a recommendation is made)

Validation Messaging:
May be dependent on front-end vs. back-end validation:

Does not have the Government Analyst role (Recommend button): "The Government Analyst role is required to make a recommendation to the director."
Has not selected one of the radio buttons (Recommend button): "A recommendation is required before proceeding."

Wireframe: https://preview.uxpin.com/59145260c7d8cc48969ac79401cc03d84843c3d9#/pages/165001075/simulate/no-panels
Purpose and benefit to user:
Provides the necessary functionality for government users to make recommendations to the director
Acceptance Criteria:

[ ] Given I am a Government Analyst with IDIR access, when I navigate to the 'View Transfer' page, then I should see the 'Analyst Recommendation to the Director' heading with 'Recommend Record' and 'Recommend Refuse' radio buttons.
[ ] Given I am a Government Analyst and I select one of the recommendation radio buttons, when I click the 'Recommend' button, then a confirmation modal should appear.
[ ] Given I am on the confirmation modal, when I click the cancel button, then I should return to the 'View Transfer' page without any changes made.
[ ] Given I am on the confirmation modal and have made a selection, when I click the 'Recommend' button, then a success message should appear, the user should be redirected to the transaction page, the transaction row for the transfer should be highlighted, the transfer status should change to 'Recommended', and the radio buttons should become unselectable.
[ ] Given a recommendation has been made, when viewing the transfer, then a transaction history record showing the recommendation date, the recommending user, and the organization should be visible.
[ ] Given a comment has been added in the 'Comment' field, when a recommendation is made, then the comment should be saved to the database and be visible when viewing the transfer.
[ ] Given I am a user with the Government Analyst role, when I access the transfer page, then I should have the ability to make a recommendation, but this functionality should be restricted to users with the specified role.

Development Checklist:

[ ] Implement the UI for the 'Analyst Recommendation to the Director' section on the 'View Transfer' page.
[ ] Develop the backend logic to handle the recommendation selection, confirmation modal, success message, redirecting and updating the transaction page, saving transaction history, and saving comments.
[ ] Ensure data validation and restrictions are in place, such as role verification, radio button selection validation, and update the UI accordingly based on user actions.

Notes:

The category D checkbox will be handled in a different card.
The comments to the director feature will be handled in a different card.
The save button functionality will be handled in a different card.

Please ensure that all the elements of the acceptance criteria and development checklist are implemented as described, adhering to the project's coding and design standards.

Might hold off on closing this ticket until some of the missing components are completed, which are being handled in other cards:

Transaction history record, including visibility of record (IDIR only)
Director comments not saving (demo data)
Transaction row highlight

IDIR user with analyst role is missing 'Recommend Record' and 'Recommend Refuse' radio buttons when recommending a transfer. Please see screenshot:


Flaky OpenSSL e2e test

Observed on test run after merge to master where test had previously passed on fork.
=== RUN   TestPionOpenSSLE2ESimple/OpenSSLServer/TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
    e2e_test.go:158: clientMsg does not equal test message: Hello WorldHello WorldHello World Hello World
    e2e_test.go:200: Test timeout waiting for server shutdown

No master fails in last ~15 commits. Going to resolve


WebSockets refactoring with callbacks

Still a WIP for now, but feedback is welcome :)

oh I really like this interface :)

Finally I think this is ready to be reviewed

Awesome @acatinon, I've been taking a look this evening. It looks great so far, though I'm having some trouble verifying that the Nash subscriptions are working under the callback method. Could just be doing something dumb, will keep playing with it.

@Ejhfast I'm sure you have more important things to do, I will have a look tonight

@Ejhfast The Nash WS tests should be ok

Yes, looks good!  🎉 I was doing something dumb, typo in my code. Thanks for updating the tests, all good on my end to merge this.
Can do a later small PR to fix SubscriptionResponseWrapper once the nash client is updated.


Support using cargo make as library

Related to and closes #1110

@SamuelMarks amazing job thanks a lot. its actually something i wanted to do for a long time but didn't have the capacity so its great.
got few questions and also i see a test error. would love if you can take a look.

@sagiegurari Great to hear you're open to this PR!
Let me take a look at the failing test and see if I can't resolve.

@SamuelMarks your fixes solve the CI issue but i also merged #1109 which caused some merge conflicts. any chance you can resolve it so i'll push this? thanks

@sagiegurari Resolved that merge conflict, still some weirdness going with this logic:
https://github.com/sagiegurari/cargo-make/blob/0119754/src/lib/execution_plan.rs#L491-L498
Once resolved let's try and merge this quickly before more PRs come through! - As this PR changes the whole codebase, adding error handling &etc.

thanks. there are no PRs at the moment so i wouldn't worry about it.
as for the legacy task, i'm planning to remove it soon i hope.

Cool cool; no I mean 18 tests are failing because of that logic I linked. What do you want that logic to be? - Silent ignore? - Ignore but give a warning message? - Something else?

I'll review the updated code tomorrow. if it makes a fuzz, drop the legacy migration task from the codebase as i want to delete it anyway.

@SamuelMarks merging. thanks a lot

@SamuelMarks while merging it to master (and planning to release it), i saw that there is an unsafe block and its crashing in mac OS in the ci cd flow.
please take a look
https://github.com/sagiegurari/cargo-make/actions/runs/9970773762


Linear regressions containing null y coordinates fail to produce accu…

Linear regressions containing null y coordinates fail to produce accurate results due to the length of the data not matching the 'len' used to run the calculations. This is solved by introducing a variable 'nonNullLen' which is an incrementer to keep track of all participating data.
In fixing the above, I discovered a similar problem with r2, causing the test to fail on r2. In order to fix that, we create two new data arrays of the matching participating points.

Linear regressions containing null y coordinates fail to produce accurate results due to the length of the data not matching the 'len' used to run the calculations. This is solved by introducing a variable 'nonNullLen' which is an incrementer to keep track of all participating data.

I'm not sure I understand the hypothesis. Looking at the algorithm, it looks like null data points are included, but they are treated, effectively, as 0. So maybe the concern about filtering null values should happen outside of this library?

In order to have a predictive regression that will fill in blanks in the data, we should treat nulls as missing data to be filled in instead of implicitly 0 filling them. In its current state, there is no way to use trendlines predictively because of this implicit 0 fill.
Any 0 filling being done should happen outside the library. For example on a time series, we may want to treat nulls as 0, but in that case we should do the 0 filling on our side and pass in the pre 0 filled data.

Links to the issues I'm trying to solve:
https://github.com/Tom-Alexander/regression-js/issues/57
https://github.com/Tom-Alexander/regression-js/issues/18

I've decided to go ahead and merge this as is, leaving open the potential for reverting or improving in the future, since the use case I'm trying to solve for is time sensitive.


The watch button does show.

For some reason none of the buttons displayed in the demo/screenshots appear in my instance.
Demo Screenshot:

On my instance, none of those images appear.
Upload 01:

Upload 02:

Upload 03:

Any help would be appreciated!
I think that there must be something wrong with my setup.

Plex: Running on Synology NAS 01 | Access = FQDN
Movie Roulette: Running on a Synology NAS 02 | Access = FQDN
Client: AppleTV

All devices are on the same LAN and all are hardwired over ethernet cables.

Hi, yes, please disable Homepage Mode

@sahara101 Thank you!
I didn't realize that turning on the widget would change the setting for regular access.
Thanks for clarifying the Homepage widget usage.

One more question, is it possible to have two AppleTVs paired so that you can select which TV to play the movie to?
I only ask because I have paired two AppleTVs but I can only seem to use the most recently paired tv. Does this seem accurate or have I messed something else up?


Link on GoQuorum README is broken

Hi, the link on your GoQuorum README is broken. https://github.com/ConsenSys/quorum-dev-quickstart/blob/master/files/goquorum/README.md

Hi @rodion-lim-partior the readme here in the repo is intentional, its meant to be viewed when run from npm quorum-dev-quickstart which puts the readme in the right path when the templating is done

Hey @joshuafernandes, I didn't mean the path is broken. Your link to official docs is showing a 404 error. It should be without getting-started.

Gotcha, thankyou @rodion-lim-partior this is fixed now in v 0.0.77


Add swaphub

Fixes # .
Changes proposed in this pull request:

@riemiyazawa Sorry but we've changed the repository for the spaces can you make a PR here instead: https://github.com/bonustrack/snapshot-spaces ? Have a look here on the updated docs: https://docs.snapshot.page/guides/create-a-space I'm closing this PR for now feel free to reach our Discord for help.


d3-org-chart if children are more than 5 then display next line/row.

Hi, I am using d3-org-chart library in my react project. I have 18 children under parent node and I want to split the children as 5 per row. I have tried multiple times but it is not working.
I tried using layoutBinding property but it is not rendering the chart itself.
.layoutBinding(function(d: any) {
// Custom layout logic
const childrenPerRow = 4; // Number of children per row
if (d.children) {
d.children.forEach((child, index) => {
const row = Math.floor(index / childrenPerRow);
const col = index % childrenPerRow;
child.x = d.x + col * 100; // Adjust x position
child.y = d.y + row * 100;  // Adjust y position
});
}
return d;
})
onNodeClick it is not applying the new coordinates to chart.
chart.onNodeClick(function(d) {
const childrenPerRow = 4; // Set the number of children per row
if (d.children && d.children.length > childrenPerRow) {
d.children.forEach((child, index) => {
const row = Math.floor(index / childrenPerRow);
const col = index % childrenPerRow;
child.x = d.x + col * 100; // Adjust x position
child.y = d.y + row * 100;  // Adjust y position
});
chart.update(d);
}
});
Attached the image for your reference.

This library does not support that kind of layout

Thank @bumbeishvili for your response. Do you have any alternative suggestions for handling such scenarios? Appreciate your help on this because it is kind show stopper for us.


Thank you. I vaguely remember seeing the same error some time ago as well. Apparently, it is not sufficient to install it as part of the requirements file.


Add exon information to transcript IDs in Ensembl Controller

What?
This PR adds exon information to the current EnsemblTranscript model, called ExonRange:
ExonRange {
exonId (string): Exon id,
exonStart (integer): Start position of exon,
exonEnd (integer): End position of exon ,
rank (integer): Number of exon in transcript ,
strand (integer): Strand exon is on, -1 for - and 1 for +,
version (integer): Exon version
}

Why?
See issue #84
This PR includes:

Added model ExonRange to EnsemblTranscript Model
Documentation and transformation script to retrieve exon information from Ensembl and add it to the current transcript information file
Replacement of script that adds domains to transcript information file (add_nested_domain_to_ensembl_transcript.py) with a script that adds both domain and exon information to the transcript information file (add_domains_and_exon_information_to_ensembl_transcript.py). The previous script was replaced due to time it took to run. Replacement script can add the information in under a minute

Hi @dionnezaal ! Thanks so much for fixing this and explaining the PR so well. One thing I just discussed with @onursumer is that we want to move the data import stuff to https://github.com/genome-nexus/genome-nexus-importer. I'll try and get this done in the next couple of days. This PR would then prolly be split in two. I can help do that.
I like that you made add_domains_and_exon_information_to_ensembl_transcript.py so much faster. I took a look at why the apply function in pandas was so slow. Adding an index instead of using by column selection  made it way faster. Also noticed this bug: https://github.com/pandas-dev/pandas/issues/9466
The Java part exposing the exons looks good to me!
Might be good to add some tests for the data transformations. Do you have any thoughts on that? A few asserts would already go a long way

@inodb good idea to move the importer parts to a different repo, I had the same thought and had also discussed with @dionnezaal when finishing this PR. However, I think it would be best to try to merge this PR first and then split up the parts in your PR. So, I would like to propose the following:

@dionnezaal adds some tests for the python transformation step (Dionne: see unit tests we also have for validation scripts)
we merge this PR
@dionnezaal can help with any issues in subsequent PR (where the data loading step is moved to different repo) if necessary

@pieterlukasse @inodb I have added a simple unit test for the exon information transformation script which transforms a GFF file with data from two transcripts with exon information and checks if the output file is the same as the example.

Tested the whole solution and works really well :+1:

Split part of this to genome-nexus-importer https://github.com/genome-nexus/genome-nexus-importer/pull/3

Split the rest to #139


Update vscode-extensions.txt

added several extensions for Jupyter notebook support

Hi Stefan, sorry overlooked PR. Do I understand right, that these extensions are not installed with jupyter alone?

you're right, they're implicitly installed with the jupyter extension. i've looked, which extensions were installed in vscode, when playing with jupyter support and found these. therefore, i've put them in the plugin list. sorry, i was not aware of this. we can omit this PR. it should work either way.


find nested paragraphs

wikipedia rendering changes
Fixes Issue #27

I'll look at your PR later today when I get a chance. It does seem that Wikipedia has changed something in their rendering that breaks my HTML parsing. I just want a chance to test out your PR before I accept it.

Hi
Wikipedia is now using a lots of paragraphs.
I also created #29 , it merges the first 10 paragraphs to a list.
Feel free to drop my PR and fix it in other ways.

This isn't how I want to approach this. This falsely returns information from the sidebar, since this appears in HTML before the body. Let me examine the new structure of the pages and I'll figure out how to fix #27.


Add description field to permissions entity

It would be nice to "optionally" give a description to a permit previously created, not just the name, some kind of explanation.... :)

It looks like this is a duplicate of #154. Please, close this issue.

Yup, thank you :)


Smart Brillant Automotive

At comma.ai we are building openpilot, open-source software that can drive your car. Right now support includes Toyotas with TSS-P, the Honda Civic and CR-V (with Honda Sensing) and Acura ILX. In this post, I will describe how we built the Forward Collision Warning (FCW) system in openpilot. (note: the human was driving in all footage below)
Forward Collision Warning indicator on the dashboard
Our openpilot community also ported openpilot to a bunch of other cars, including a variety of Toyotas, Hondas, pre-autopilot Teslas and the Chevy Volt. This makes openpilot compatible with 5 out of the 10 most sold cars in the US in 2017. Currently, openpilot is a level 2 system and provides better lane keep assist and adaptive cruise control than the system that ships with the car. Also openpilot keeps improving with every update.
This makes openpilot compatible with 5 out of the 10 most sold cars in the US in 2017
Each week, our fleet of openpilot users sends back hundreds of hours of video paired with sensor data from their car and EON. We use this data to train our neural networks, create accurate maps and reverse engineer more CAN bus signals. But this data can be used for much more than learning how to drive.
Having access to all these miles of driving data enables us to quickly develop new algorithms. Using our infrastructure, we can simply run our algorithms on all historical data. We don’t need to deploy our software in ‘shadow mode’ and wait weeks for a result. This gives us very good estimates on how well our system behaves, how many warnings were generated and how many of those were false positives.
In short, you want to get a warning when you have to decelerate quickly in the near future. This can happen because the car in front of you starts braking suddenly, or when the driver is not paying attention and gets very close the other car. The FCW system will then sound loud beeps and show a sign on the dashboard. Warning the user early can greatly increase the time the user has to respond and avoid a collision. According to [Lee et al., 2002] an FCW system can reduce rear-end collission by up to 80.7%.
An FCW system can reduce rear-end collision by up to 80.7%.
When searching for events where an FCW should trigger, we look for a maneuver where the car brakes with deceleration of 3 m/s² for at least 1 second. With this level of braking you go from 65 mph to a full stop in about 10 seconds. On the other hand, every warning generated by the system which is not followed by at least 2 m/s² deceleration is considered a false positive.
During our search, we are interested in three types of events: an FCW followed by braking (true positive), FCW not followed by braking (false positive) and braking not preceded by an FCW (false negative).
We’d like to minimize the false negatives, while still being careful not to generate too many false positives. After too many false positives the user will not trust the system anymore, or worse: turn the system off. We decided that a ratio of 1 false positive per 2 true positives is acceptable.
To trigger an FCW at the right moment we need to predict if any hard braking is required in the near future. Luckily, for our Adaptive Cruise Control, we used model predictive control to build an advanced planner which calculates the desired speed trajectory for the next 10 seconds. This uses an optimization algorithm, based on radar and vision information of the lead car (e.g. relative position and speed) and speed and acceleration of your own car.
This optimization algorithm tries to keep the car out of the ‘danger zone’ of the lead car, while minimizing passenger discomfort by acceleration and jerk. This ‘danger zone’ is defined as the distance in which the driver has less than 1.8 seconds to avoid a collision if the lead car would suddenly start braking very hard. According to [Zhang, Antonsson & Grote 2006],1.8 seconds should give most drivers enough time to react
This optimization runs 20 times per second and generates a speed and acceleration trajectory. If this trajectory contains a deceleration that is significantly lower than our current deceleration, we know hard braking is required in the near future and it is time to warn the driver.
This optimization runs 20 times per second and generates a speed and acceleration trajectory.
However, just using this trajectory would generate a lot of false positives. There are a lot of situations where a human drivers enter the danger zone while this is still pretty safe. For example, this happens when the driver is about to change lanes. By running the algorithm on a lot of data we were able to come up with conditions to filter these false positives, while still keeping most of the useful warnings.
We ran our algorithm on a subset of our driving data since June 2017, about 6400 hours of driving. By changing parameters we found a tuning that resulted in 625 successful warnings and 246 false positives. There were 7531 false negatives, but most of those didn’t warrant an FCW (e.g. hard braking for a red light). This means our target of 1 false positive per 2 real warnings is reached and the system can be shipped.

Qualitative plot of false positives vs. events detected when increasing sensitivity
Of course, the development of the FCW system is not finished, because there are still situations where the system did not trigger a warning when it should have. By collecting more data and spending more time on this problem we can improve the performance over time.
Additionally, we could train a neural network based on raw camera images and feed this as an extra input to the FCW system. Alternatively we could train a net to decide whether to trigger an FCW based on the available metrics, instead of manually selecting the features for which we trigger.
However, data already shows the current system has the potential to improve the safety of our users. And unlike most of the systems built by car manufacturers, we have the ability to roll out over-the-air updates with system improvements.
Want to work on interesting problems like this? Check out our open positions. Also follow us on Twitter.


BUG: Title for Settings of Arrays

Describe The Bug:
The title of arrays for a plugin's settings appear to be using the config name and not the imposed title in the config.schema.json file.
To Reproduce:

Create an array of configuration settings associated with a configuration for a plugin.
Set the title of the entire array.
See that the title is choosing the specific configuration identifier for that setting addressed in the config.schema.json instead of the title provided in the config.schema.json file.

Expected behavior:
Expected to see the title instead of the identifier.
Logs:
There is no output in the logs for this issue, see the screenshots.
Screenshots:

Environment:

Node.js Version: v12.16.2
NPM Version: v6.14.6
Homebridge Version: 1.1.1
Homebridge Config UI X Version: v4.23.2
Operating System: macOS
Process Supervisor: launchd

any updates on this?

@oznu thanks 👍🏻👍🏻

a thanks from me too from my ocd point of view!


update-bundle: Use "verity" bundle format

The legacy "plain" RAUC format was deprecated. Switch to "verity".

I rebased the patch on top of main. It depends on this GitHub pull request https://github.com/rauc/meta-rauc-community/pull/93 which as been recently merged in branch kirkstone of layer meta-rauc-community/meta-rauc-raspberrypi.
Best regards, Leon

Thanks @leon-anavi , verified with existing IoT update jobs capabilities on latest kirkstone config.


[DO_NOT_MERGE]Test kafka deletion

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
Please review http://spark.apache.org/contributing.html before opening a pull request.

Test build #69280 has started for PR 16048 at commit 98f34d6.

Test build #69280 has finished for PR 16048 at commit 98f34d6.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69280/
Test FAILed.

Test build #69284 has started for PR 16048 at commit c90f38e.

Test build #69284 has finished for PR 16048 at commit c90f38e.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69284/
Test FAILed.

Test build #69309 has started for PR 16048 at commit 6abd7cf.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69309/
Test FAILed.

Test build #69311 has started for PR 16048 at commit fa313e5.

Test build #69311 has finished for PR 16048 at commit fa313e5.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69311/
Test FAILed.

Merged build finished. Test FAILed.

Test build #69339 has started for PR 16048 at commit 9ff2ed4.

Test build #69339 has finished for PR 16048 at commit 9ff2ed4.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69339/
Test FAILed.

retest this please

Test build #69345 has started for PR 16048 at commit 9ff2ed4.

Test build #69351 has started for PR 16048 at commit 27102eb.

Test build #69345 has finished for PR 16048 at commit 9ff2ed4.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69345/
Test FAILed.

Test build #69359 has started for PR 16048 at commit eaa4a73.

Test build #69351 has finished for PR 16048 at commit 27102eb.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69351/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69359/
Test FAILed.

retest this please

Test build #69390 has started for PR 16048 at commit eaa4a73.

Test build #69390 has finished for PR 16048 at commit eaa4a73.

This patch fails executing the dev/run-tests script.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69390/
Test FAILed.

retest this please

Test build #69391 has started for PR 16048 at commit eaa4a73.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69391/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

Test build #69421 has started for PR 16048 at commit eaa4a73.

Test build #69421 has finished for PR 16048 at commit eaa4a73.

This patch fails from timeout after a configured wait of `250m`.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69421/
Test FAILed.


disease.setId

The following code in PhenoPacketTest.java does not compile anymore as (I believe) setId has been renamed to setDiseaseId
private Disease getDisease() {
Disease disease = new Disease();
disease.setId("OMIM:101600");
disease.setLabel("Pfeiffer syndrome");
disease.setTypes(ImmutableList.of(OntologyClass.of("EFO:0000508", "genetic disorder")));
return disease;
}

Sorry disregard this, I had a namespace clash and all is well.


[Pull Request] Added capabilities to set myZone, use all constant zones and to handle a system with mix zones

name: Added capabilities to set myZone, use all constant zones and to handle a system with mix zones
about: Add improvements to homebridge-cmd4-AdvantageAir.
title: "[Pull Request]"
labels: new features
assignees: mitch7391

Added improvements to current cmd4-advantage plugin:

added capability to set myZone.
used all defined constant zones instead of using only the first constant zone.
added capability to handle correctly a system with a mixture of zones with and without temperature sensors.

Is your pull request related to a problem or a new feature? Please describe:

This pull request is to add improvements to the plugin.
Describe the solution you'd have implemented:

Modified AdvAir.sh to:

add a set of codes to read myZone from $myAirData and another set of codes to set myZone.

add a few line of codes to make myZone as priority, if it is defined, as temperature control for the Aircon system.

add a set of codes to scan through all constant zones and modified the logic such that at least the noOfConstants zones are opened at any one time to protect the Aircon system.

add logic such that if the zone to close is assigned as myZone, myZone will be re-assigned to another opened zone with temperature sensor before closing it. If the number of open zone is not more than noOfConstants or the opened zones are of noSensors zones, then a closed zone with temperature sensor will be opened (with priority to constant zones) and assigned it as myZone before closing the zone.

determine on-the-fly whether a zone is with or without temperature sensor so that a system with mixed zones can be handled correctly.  Since the zone with or without sensor is determined on-the-fly directly from $myAirData, the myAirConstants.txt cache file is no longer required, hence the codes and the function related to the creation of myAirConstants.txt is removed from AdvAir.sh.

Modified ConfigCreator.sh to allow the generation of config for myZone "Switch" accessories.

Modified CheckConfig.js to allow the checking of myZone.

Modified server.js to allow the checking of myZone.

Modified AirConServer.js to allow the update to myZone.

All unit tests were modified to reflect the removal of the use myAirConstants.txt file and added a few unit tests to test for myZone and the use of all constant zones.

Do your changes pass local testing:

[x] Yes

Additional context:

ConfigCreator.sh:
This new version of  ConfigCreator.sh will generate additional config for myZone "Switch" accessories if myZone is defined.
myZone is defined if its value in $myAirData is not 0.
If myZone is defined, only those zones with temperature sensors will have a myZone "Switch" accessory.  An example below shows all the 10 zones in this Aircon system has temperature sensors, hence there are 10 myZone "Switch" accessories.

You can set a zone to be myZone by pressing a myZone tile on Homekit.  Note that you cannot unset a myZone but you can do so by setting a new myZone.  There will be only one myZone allowed at any one time.
If the zone you set as myZone is a closed zone, it will be opened before assigning it as myZone.
Please note that myZone may not be avaliable to all system which has temperature sensors.  myZone is an optional feature which AdvanatageAir system installer can set it up during installation.
New version of AdvAir.sh is 100% compatible with the existing cmd4 configuration file:
Despite the removal of myAirConstants.txt cache file, this new version of AdvAir.sh is still 100% compatible with the existing cmd4 configuration created manually or generated with the previous version of ConfigCreator.
However, if your system has temperature sensors and has myZone defined, then you need to re-run ConfigCreator in order to make the myZone "Switch" accessories availiable in Homekit.

Hey Mitch, you are right, I have the 'myZone' switches grouped together initially, but the homekit in IOS16 has all the switches assigned the same name as the first one.  I guess that is a bug within Homekit with IOS16.
As such, in order to have each 'myZone' switch to have their own unique name, I have to make each 'myZone' a separate switch.
It works well for users who prefer the switches in a separate Homekit room called "myZone" as in my example.  For users who would prefer to have all the 'myZone' switches in one homekit tile, they can easily group all those switches together within Homekit.

I think it might do that do to it acting like a 'linkedType', I am pretty sure if we were to force it from a config point of view we would make one of them the main switch (and hence why the name assigns across all of them) and the rest would be 'linkedType'. Just a guess but happy to leave it as is and let users decide how they would to use it :)

we were to force it from a config point of view we would make one of them the main switch (and hence why the name assigns across all of them) and the rest would be 'linkedType'.

That is exactly what happened in IOS16.  All the accessories within the 'linkedType' adopt the name of the main one. It did not do that before I update to IOS16.
Many other accessories in my homekit which has mulitple swtches in one homekit tile has all the switches in it having the same name after the I updated to IOS16. So I have to rename each one painstakingly otherwise I won't know what function for each switch.
Please have a detail look into your "xiaomi roborock" homekit tile, you will find that all the switches in it are having the same name as the main one.


[URGENT] [BUG] Could not execute entrypoint stage 'client' due to errors, provided by 'iseelava'!

https://paste.gg/p/anonymous/6147bf7116d140bbb30a320afd1671b8
The launcher has updated. With that update, they made accessibility settings more accessible. This means that the first screen you see isn't the main menu. I don't know if this is related, but may help.

This is an issue with reimaginedmenus, not this mod.


top insets wrong value not same as safe area insets

Description
The insets value of top is showing wrong it is not same as useSafeAreaInsets some times it shows fine and some time when app is opened with killed state notificaion
Steps to reproduce
create new react native app install unistyles and safe area context match both insets value it will be different check in the repro
Snack or a link to a repository (optional)
https://github.com/dhruv-00/unistyles-repro
Unistyles version
2.5.1
React Native version
0.73.6
Platforms
Android
Engine
JSC
Architecture
Paper (old)

https://github.com/jpudysz/react-native-unistyles/assets/86352938/111398c6-db21-44a6-b6f8-9d

6f561ad6dd

Hello 👋
But what is the issue? That unistyles is not showing exact same values as safe-area-context?
On your example status bar is translucent or not? If not then indeed it's a bug, if it is then Unistyles reports correct value = 46.
What's your phone model / android version?
What's your setup, do you use expo? Do you use any windows flags?
If you want to me help I need a lot more details.
Also please take a look here: https://www.unistyl.es/reference/dimensions/#insets

the issue is that normally it is working fine but when the app is in killed state and I open it with notification then the top value is not proper.
In my main app the issue is coming when opening with notification
when I tried to create it with new reproducible example then it was already showing wrong value in the first time without notification opening
phone: OnPlus 12 / Android 14
react native cli

after setting status bar translucent

Ok, so you don't have satus bar translucent, and it happens only if you open the app from push notification?

yes exactly, and my main app is react-native 0.72.6
but in the reproducible example it is latest version but it is reproducible without opening the notification

Ok to sum it up:
Android 14 with RN 0.73, Unistyles 2.5.1, when you open fresh app you're receiving invalid top inset (but not always).
You're not using expo.
So the last question:
Did you modify anyhow window flags? Example is in the documentation posted above.

No I did not change any windows flags

Cool, thanks for the report. I'm a little bit surprised as Android 14 has a stable inset API. Maybe it's something about OnePlus

I will be able to get OnePlus with Android 14 on Tuesday (after Easter). I will debug it directly 🙏

@jpudysz 2.5.2 fixes this or it's unrelated?

It was not addressed specifically for this issue. I will debug this report tomorrow with OnePlus device 🙏

Hey @dhruv-00 can you check how it works with fresh release (2.5.2 )?

let me check I'll update you

Ok thanks for the tests. Tomorrow, I will setup deeplinking and try to repro it with OnePlus 🙏

Tested on OnePlus 9 Pro with Android 14.

Opening app from killed state with deeplinking:

npx uri-scheme open unistyles:// --android

Shows always top=0.

I was able to reproduce double reporting with:

 <StatusBar translucent />

 (NOBRIDGE) LOG  Bridgeless mode is enabled
 (NOBRIDGE) LOG  Running "bare" with {"rootTag":51,"initialProps":{},"fabric":true}
 (NOBRIDGE) LOG  UnistylesRuntime.insets: 0
 (NOBRIDGE) LOG  UnistylesRuntime.insets: 32

But it's because StatusBar is rendered in JSX, so it happends after first re-render.
Any other idea how can I test it?

On which react native version you are trying it?

0.74-rc.5 and 0.73.6 in your example

Tried your example with 0.72.6:

hmm, any ideas whats different in your app?

first one is with notification and second one is with uri scheme
https://github.com/jpudysz/react-native-unistyles/assets/86352938/942aee07-4b4c-4a01-8280-933a5d2cb8c5

Ok, so I need to setup Firebase project 🫡

Are there any steps by which I can debug this?
may be looking into any specific files.
which you think might be causing the issue.

You would need to debug kotlin files..
Let me firstly try with some push notification. I just hope I will be able to repro and isolate the issue

Reproduced!

That was extremely difficult to spot, but thanks to you, Unistyles can now properly initialize in headless mode.
The issue was that layout listeners were not being properly set when the app was initializing from headless mode, e.g. from a push notification. You should now receive the correct value.
Disclaimer:
Unistyles will emit two insets events when run in headless mode, but this should not be visible to the end user.
It's possible to emit a single event, but I need to refactor how the C++ module works, so most likely, this will be implemented in Unistyles 3.0.
I will release Unistyles 2.5.3 soon 🎉


Update CMIP3 data entries to align with ESGF

Description

CMIP3 data entries in recipes are specified in a way that is only compatible with the DKRZ data pool. For example, in https://github.com/ESMValGroup/ESMValTool/blob/main/esmvaltool/recipes/bock20jgr/recipe_bock20jgr_fig_1-4.yml#L242-L249, we have:
exp: 20c3m, frequency: mo, realm: atm
while the ESGF facets are:
exp: historical, frequency: mon, realm: atmos

Closes #3046

I have updated the recipes so it can work with ESGF and the data pool with have at NCI.
I suppose you will need to update the ones at DKRZ

Before you get started

[ ] ☝ Create an issue to discuss what you are going to do

Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

[ ] 🛠 This pull request has a descriptive title
[ ] 🛠 Code is written according to the code quality guidelines
[ ] 🛠 Documentation is available
[ ] 🛠 Tests run successfully
[ ] 🛠 The list of authors is up to date
[ ] 🛠 Any changed dependencies have been added or removed correctly
[ ] 🛠 All checks below this pull request were successful

New or updated recipe/diagnostic

[ ] 🧪 Recipe runs successfully
[ ] 🧪 Recipe is well documented
[ ] 🧪 Figure(s) and data look as expected from literature
[ ] 🛠 Provenance information has been added

To help with the number of pull requests:

🙏 We kindly ask you to review two other open pull requests in this repository

Hi @rbeucher ! Thanks for your PR.
I tried it with ESGF downloading and got the following error message:
ValueError: File ESGFFile:cmip3/CSIRO-QCCCE/csiro_mk3_0/historical/mon/atmos/run1/tas/v1/tas_A1.nc on hosts ['aims3.llnl.gov'] dates do not match a recognized pattern and time can not be read from the file
Have you tried the recipes with downloading form ESGF?

Yes I was gonna change that. Sorry.

Thanks @valeriupredoi . I think I need to be added as a contributor. I can't request a review from maintainers.

Not sure how to fix the issue. I will have to look closer at the file. The code does not seem to extract the time information from the file.

The problem with CMIP3 is that the time information is not part of the file name.

Thanks @valeriupredoi . I think I need to be added as a contributor. I can't request a review from maintainers.

OK I'll add you here if that's cool with @axel-lauer too, and Axel will send you the "welcome email" as well. Before I open the PR to add you to the contributors' list, could you pls tell me your institution that you wish to be affiliated with, and an ORCID number (if you has one) :beer:

Sure
Romain Beucher
ACCESS-NRI
0000-0003-3891-5444

cheers! Will start the procedures tomorrow :+1:

Welcome to the development team, @rbeucher!

for your consideration gents @axel-lauer @rbeucher https://github.com/ESMValGroup/ESMValTool/pull/3318

I am not completely sure what the status of this PR is, but my understanding is that it needs a bit more work? I'll bump it to the next milestone, but if I am wrong and this can essentially be merged as is, please let me know.

I too am cyrious about the status of this PR - would be a rather useful one to merge the sooner the better :+1: @mo-gill @ehogan would you guys be OK to create an M2.12 milestone please, so we can move stuff (hopefulyy not like this) to the next milestone? :beer:

create an M2.12 milestone please

I'm hoping i've done this correctly! :crossed_fingers: https://github.com/ESMValGroup/ESMValTool/milestone/15
Wasn't sure what the due date should be, or whether i should leave it blank for the time being? @valeriupredoi @ehogan

create an M2.12 milestone please

I'm hoping i've done this correctly! 🤞 https://github.com/ESMValGroup/ESMValTool/milestone/15
Wasn't sure what the due date should be, or whether i should leave it blank for the time being? @valeriupredoi @ehogan

We added the due date to the v2.11.0 milestone when we knew when we were doing the v2.11.0 release, so the next release manager will update the due date for the v2.12.0 milestone when they know when they are doing the release 👍

This is not ready to merge unfortunately.
I need to retrieve the time information which is not available via the file name ... Any suggestions @valeriupredoi ?

This is not ready to merge unfortunately. I need to retrieve the time information which is not available via the file name ... Any suggestions @valeriupredoi ?
I had a look too and if the files are local it works fine as long as it can find it and get the time information from the file but if it needs to download ESGF file it can't get the time information ... so would have to change in esmvalcore to download these types of files first?? or file name change on ESGF node?

Given the transition to CMIP7 and the diminishing likelihood of CMIP3 being supported on ESGF, I believe it is time to conclude this.


gcloud:deploy fails due to presence of Dockerfile in /tmp/ staging directory when app.yaml's runtime is "java"

Exactly as the title suggests, gcloud:deploy is failing for me because my java app is staged into a subdirectory of /tmp where it has an app.yaml and a Dockerfile generated for it.
The app.yaml:
runtime: java7
vm: True
module: 'mvnhello'
inbound_services:
- warmup
derived_file_type:
- java_precompiled
threadsafe: True
auto_id_policy: default
health_check:
  enable_health_check: True
api_version: '1.0'
handlers:
- url: (/.*)
  static_files: __static__\1
  upload: __NOT_USED__
  require_matching_file: True
  login: optional
...etc...

The Dockerfile:
FROM gcr.io/google_appengine/java-compat
ADD . /app

In this case, it seems generating "runtime: custom" would be more useful in this case, since the Dockerfile already takes care of the runtime by using gcr.io/google_appengine/java-compat as a base image.

The error:
[INFO] Beginning deployment...
[INFO] ERROR: (gcloud.preview.app.deploy) There is a Dockerfile in the current directory, and the runtime field in /tmp/1447436161590-0/app.yaml is currently set to [runtime: java7]. To use your Dockerfile to build a custom runtime, set the runtime field in /tmp/1447436161590-0/app.yaml to [runtime: custom]. To continue using the [java7] runtime, please omit the Dockerfile from this directory.
[ERROR] Error: gcloud app command with exit code : 1
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11.318s
[INFO] Finished at: Fri Nov 13 17:36:02 UTC 2015
[INFO] Final Memory: 15M/56M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.google.appengine:gcloud-maven-plugin:<IP_ADDRESS>.v20150804:deploy (default-cli) on project mavenHello: Error: gcloud app command exit code is: 1 -> [Help 1]

Please upgrade to plugin version
<IP_ADDRESS>.20151113
To see if this is better.
Ludo
On Nov 13, 2015 10:02 AM, "dt-rush"<EMAIL_ADDRESS>wrote:

The error:
[INFO] Beginning deployment...
[INFO] ERROR: (gcloud.preview.app.deploy) There is a Dockerfile in the current directory, and the runtime field in /tmp/1447436161590-0/app.yaml is currently set to [runtime: java7]. To use your Dockerfile to build a custom runtime, set the runtime field in /tmp/1447436161590-0/app.yaml to [runtime: custom]. To continue using the [java7] runtime, please omit the Dockerfile from this directory.
[ERROR] Error: gcloud app command with exit code : 1
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11.318s
[INFO] Finished at: Fri Nov 13 17:36:02 UTC 2015
[INFO] Final Memory: 15M/56M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.google.appengine:gcloud-maven-plugin:<IP_ADDRESS>.v20150804:deploy (default-cli) on project mavenHello: Error: gcloud app command exit code is: 1 -> [Help 1]
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-maven-plugin/issues/62#issuecomment-156502665
.

Hey Ludo,
This did indeed seem to fix the issue. I'm now stuck with what appears to be a generalized infrastructural issue with Managed VM deployment, having got past the original issue. It hangs after the following for a long time:
[INFO] Beginning deployment...
[INFO] Verifying that Managed VMs are enabled and ready.
[INFO]
[INFO] Provisioning remote build service.
[INFO] Copying certificates for secure access. You may be prompted to create an SSH keypair.
[INFO] Building and pushing image for module [mvnhello]
[INFO] -------------------------------------------------------------------- DOCKER BUILD OUTPUT --------------------------------------------------------------------
[INFO] Step 0 : FROM beta.gcr.io/google_appengine/java-compat
[INFO] ---> ed8fbbc37adc
[INFO] Step 1 : ADD . /app
[INFO] ---> 0fbb8032d7aa
[INFO] Removing intermediate container df981aa1d8f7
[INFO] Successfully built 0fbb8032d7aa
[INFO] -------------------------------------------------------------------------------------------------------------------------------------------------------------
[INFO]
[INFO] Deleted [https://www.googleapis.com/compute/v1/projects/triple-gem-8/zones/us-central1-f/instances/gae-builder-vm-20151113t202634].

After several minutes of this, it goes on to print the following lines:
[INFO] ERROR: gcloud crashed (ResponseNotReady):
[INFO]
[INFO] If you would like to report this issue, please run the following command:
[INFO]   gcloud feedback
[ERROR] Error: gcloud app command with exit code : 1
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11:59.584s
[INFO] Finished at: Fri Nov 13 20:38:22 UTC 2015
[INFO] Final Memory: 14M/56M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.google.appengine:gcloud-maven-plugin:<IP_ADDRESS>.v20151111:deploy (default-cli) on project mavenHello: Error: gcloud app command exit code is: 1 -> [Help 1]

It seems the ResponseNotReady is bubbling up from python's httplib.
It seems as though only somebody who could get into the deployment server / remote build server / some other Google infrastructure could explain and fix this weird error. I'm still unable to deploy a working Managed VM app, even though it appears VMs are provisioned.

Yes, this is different!

Any updates on this issue? I'm encountering the same thing

Which plugin version do you have in the pom.xml?
If it old, upgrade to a newer version <IP_ADDRESS>.v20151210
On Fri, Jan 15, 2016 at 11:40 AM, Jake Sanders<EMAIL_ADDRESS>wrote:

Any updates on this issue? I'm encountering the same thing
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-maven-plugin/issues/62#issuecomment-172063922
.


MUMUP-1926: Add google analytics tracking for sidebar events

Hopefully this will give us better insights into user behavior regarding the sidebar - whether people use it, how often they minimize it and maximize it, which links they are clicking in the navigation...
@timlevett, did I use your nifty pushGaEvent() function correctly? Is there a way I can test this locally?

:+1:

:+1:

This will fire GA events when users show and hide sidebar. But it won't tell us what state the sidebar is in when people render the page and don't touch it.  Should there be a fire-on-render event along the lines of
"pushGaEvent('Sidebar','Rendered', 'Expanded')"
"pushGaEvent('Sidebar','Rendered', 'Minimized')"
to give visibility into not just how much people change the state how, but what state it's in when people are using the portal?  Or that'll be too much events overload?

We are using this angular module in DoIT Number:
https://luisfarzati.github.io/angulartics/
It has handy element attributes for doing what you want.

@nblair - that may be nice if we decide to revamp the analytics module, which is very much out of scope of this little issue. ;) i'll backlog an issue as people seems bothered by our current approach.

Agreed with @timlevett. We can revisit angulartics if/when we're ready to revamp analytics.

It should work now.

1 fix in app-config.js, then I will thumb.

:+1:


[Dismiss] first attempt to support transparent background

I would be curious to know if this works with any type of ViewGroup (LinearLayout with vertical orientation for example)


Extremely slow workflow

If you request multiple screen widths, the workflow is built to resize the screen and take a screenshot for every element rather than take a screenshot at a size, and then pull all of the elements at that size, change the size and pull all of the elements again.

This does not seem to be fixed in the current version and seems to be the largest perf hit for our screenshot task.

Has anyone been able to work around this? For us, capturing 17 elements over 3 pages at 4 browser widths takes around 11 minutes.

With the new version we will only stitch screenshot if required (based on browser driver). Also once it is compatible with v4 of WebdriverIO you can run these processes in parallel which should speed up the process overall.


AUTO Terminate Medication Dispenses

Implement auto termination process according to spec

[x] Create WS logic
[x] Implement
[x] Deploy
[ ] Create test scenarios

Tested manually


Added the 'spo term set list' command solving #600

Added the 'spo term set list' command solving #600

Coverage remained the same at 100.0% when pulling f799f75dafa11128b6cdf0bdb88d978751b6e1ba on waldekmastykarz:list-term-set into 14cfca93437d863cb40c844396b6277114783064 on pnp:dev.

Merged manually


don't have armor trims to shine

version:
Minecraft 1.20.50
newb-x 15.21
don't have armor trims to shine

It's actually not supported for glow armor trim, however if you want something like that, there's a certain texture pack in mcpedl you can find.

It's actually not supported for glow armor trim, however if you want something like that, there's a certain texture pack in mcpedl you can find.

I know,thanks.


KAFKA-7353; Connect logs 'this' for anonymous inner classes

Replace 'this' reference in anonymous inner class logs to out class's 'this'
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ewencp, would you mind giving it a final review and merging? This modifies #3639, which was backported.


【Feature || Issue】miss method error

Describe the bug
[Error - 16:11:52] Request textDocument/documentSymbol failed.
  Message: Method not found.
  Code: -32601

Expected Behavior
success
Current Behavior
report err msg
Reproduction Steps
indexing ...

...

[Error - 16:11:52] Request textDocument/documentSymbol failed.
  Message: Method not found.
  Code: -32601
[Info  - 16:12:13] lsp.FileEvent{
    uri:     lsp.DocumentUri(file:///Users/xxx/product/main.v)
    typ: changed
}

Possible Solution
No response
Additional Information/Context
No response
Environment details (v doctor output)
V full version: V 0.3.5 da153aa.02c3825
OS: macos, macOS, 13.3.1, 22E772610a
Processor: 8 cpus, 64bit, little endian, Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz

getwd: /Users/xiusin/live-admin-server
vexe: /opt/v/v
vexe mtime: 2023-06-27 01:19:56

vroot: OK, value: /opt/v
VMODULES: OK, value: /Users/xiusin/.vmodules
VTMP: OK, value: /tmp/v_501

Git version: git version 2.23.0
Git vroot status: weekly.2023.23-140-g015ccc2a (27 commit(s) behind V master)
.git/config present: true

CC version: Apple clang version 14.0.0 (clang-14<IP_ADDRESS>)
thirdparty/tcc status: thirdparty-macos-amd64 46662e20-dirty

Editor name
vscode
v-analyzer Version
v-analyzer version 0.0.1-beta.1

VS Code Extension Version
No response

Indeed, should be fixed with latest commit!


fix: open all external links in new tabs

Fixes https://github.com/lenra-io/website/issues/68
We may accept this PR or fix the bug in backoffice that make us impossible to go back.

Nope ! This is not correct


Swiper seems doesn't read settings with webpack.

Swiper Version: 4.0.0-beta.4
Platform/Target and Browser Versions: macOS, Chrome Version 61.0.3163.100 (64-bit)

I'm using the swiper plugin with webpack 3.6.0, and the basic setup it works, but it seems that it doesn't accept any of defined settings (autoplay, pagination, etc..).
import 'bootstrap';
import Swiper from 'swiper';

(function () {

	$(document).ready(function () {
		sliderSetting();
	});

	function sliderSetting() {
		var swiper = new Swiper('.swiper-container', {
			pagination: '.swiper-pagination',
			paginationClickable: true,
			loop: true,
			autoplay: true,
			speed: 2500
		});
	}
}());

var path = require("path");
var webpack = require('webpack');

var config = {
	cache: true,
	watch: true,
	entry: [
		'./frontend/js/main.js'
	],
	output: {
		path: __dirname,
		filename: './ROOT/WEB-INF/classes/static/js/[name].js'
	},
	module: {
		loaders: [
			{
				test: /\.js$/,
				loaders: ['babel-loader?presets[]=es2015'],
				exclude: /(node_modules|bower_components)/
			},
			{
				test: /\.css$/,
				loader: 'style-loader!css-loader'
			}
		]
	},
	plugins: [
		new webpack.ProvidePlugin({
			$: 'jquery',
			jQuery: 'jquery',
			'window.jQuery': 'jquery',
			Popper: ['popper.js', 'default'],
			Util: "exports-loader?Util!bootstrap/js/dist/util",
			Dropdown: "exports-loader?Dropdown!bootstrap/js/dist/dropdown"
		})
	]
};

module.exports = config;

Refer to v4 demos, it has new API for modules, e.g. https://github.com/nolimits4web/Swiper/blob/v4/demos/02-responsive.html#L74-L79


History mode with frontend

Some goodies that in history mode.
https://stackoverflow.com/questions/25674013/advantages-disadvantages-of-html5-mode-vs-hash-mode-angularjs
And I think it's pretty low priority

Some links to achieve that
https://github.com/owais/django-webpack-loader
https://dev.to/saymy__name__/hooking-up-django-and-vue-js-19j3
https://alexiej.github.io/django-vue-graphql/#_5-add-vue-js-frontend


Error with Karma 6: No provider for "customFileHandlers"

🐞 Bug report
Command (mark with an x)

[x] test

Is this a regression?

Yes, the previous version in which this bug was not present was: with karma 5.x
Description
In Karma version 6 customFileHandlers is deprecated in favour of the middleware functionality.
See: https://github.com/karma-runner/karma/releases/tag/v6.0.0
🔬 Minimal Reproduction

🔥 Exception or Error

19 01 2021 09:14:56.495:ERROR [karma-server]: Server start failed on port 9876: Error: No provider for "customFileHandlers"! (Resolving: framework:@angular-devkit/build-angular -> customFileHandlers)

🌍 Your Environment

Angular CLI: 11.0.7
Node: 14.15.4
OS: darwin x64

Angular: 11.0.9
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
... service-worker
Ivy Workspace: Yes

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1100.6
@angular-devkit/build-angular   0.1100.7
@angular-devkit/core            11.0.6
@angular-devkit/schematics      11.0.7
@angular/cdk                    11.0.4
@angular/cli                    11.0.7
@angular/material               11.0.4
@schematics/angular             11.0.7
@schematics/update              0.1100.7
rxjs                            6.6.3
typescript                      4.0.5

Anything else relevant?
I am using https://github.com/just-jeb/angular-builders/tree/master/packages/custom-webpack to add a custom webpack to my tests.

This is expected as Karma 6 is not supported by in Angular CLI 11.0.
It will be supported in Angular CLI 11.1. See:
See: https://github.com/angular/angular-cli/pull/19784
You can try using the prerelease version by running:
ng update @angular/cli --next

This is expected as Karma 6 is not supported by in Angular CLI 11.0.
It will be supported in Angular CLI 11.1. See:
See: https://github.com/angular/angular-cli/pull/19784
You can try using the prerelease version by running:
ng update @angular/cli --next


Add Makefile target that verifies the root manifests are up-to-date

Add the verify target that ensures the root vendor and the root list
of YAML manifests are up-to-date on a per-PR basis.

/lgtm

/retest


Updated AudioInputManager and ViewController to read audio data appro…

…priate to the iOS documentation

Now cant import anything it's showing "PortAudio library not found" error while importing

Now cant import anything it's showing "PortAudio library not found" error while importing

Hi @Sanjay2802, is this occurring on the following branch from which I have raised PR?
branch - thumbarnirmal:master

Noo , i suppose

@thumbarnirmal Could you clarify what's the issue with the current code?
@Sanjay2802 The PortAudio library not found error occurs in Python's tflite-support package v0.4.0 on Linux. You can fix it by either:

Run sudo apt-get install libportaudio2
Use the nightly build of tflite-support (pip install tflite-support-nightly). The error is already fixed in master branch and will be release in the next version of tflite-support.

Hi @khanhlvg
The inputNode.installTap callback in AudioInputManager.swift file returns audio data in range of [100, 400] milliseconds. This is specified in the iOS documentation which can be checked in xcode. It is not specified in apple developer docs website.
When the audio data returned by installTap callback is converted and saved in pcmBuffer, the pcmBuffer will have only 400 ms of unique data. The same audio data is repeated to fill the pcmBuffer for 1 second. This can be checked by trying to match pcmBuffer array from index[0:399] and index[400:799].
Above explanation is based on the assumption that inputNode.installTap has buffersize which is greater than or equal to 400 ms. If, for example, buffer size is equivalent to 200 ms, same issue would occur, but data would repeat in pcmBuffer from index 200, 400 and so on.

When the audio data returned by installTap callback is converted and saved in pcmBuffer, the pcmBuffer will have only 400 ms of unique data. The same audio data is repeated to fill the pcmBuffer for 1 second. This can be checked by trying to match pcmBuffer array from index[0:399] and index[400:799].

For sake of brevity, I have mentioned time in milliseconds as indexing value in array. Actual array index would be calculated by multiplying the pcmBuffer's sampling rate with the time value.


ci: Add UI inputs for Update helm charts job, refactor and drop need for crds_asset_id

Description

Fix https://github.com/kubewarden/helm-charts/issues/307
Changes:

Add UI inputs when workflow triggered as workflow_dispatch.
Given that the values can come from repository_dispatch (other repos) or workflow_dispatch (UI button), add a new setvariables job, that sets its job outputs to the corresponding values obtained from the payload of the repository_dispatch or from the inputs of the workflow_dispatch.
It is needed to use job outputs as is the only way to pass values between jobs, as jobs are run in their own VM instances and don't share the env.
Make the following jobs depend on it with needs: setvariables.
The javascript script from actions/github-script cannot read job outputs. Hence, add a step that reads the needs.setvariables.outputs and creates env vars. Consume those env vars in js as process.env.foo.
refactor:  Calculate crds_asset_id by querying GH instead of passing it from the job.
refactor: Remove 2 repetitions of install_crds.sh, call update_cli/scripts/install_crds.sh.

Test
Major/minor release update run: https://github.com/viccuad/helm-charts/actions/runs/8263364335
Patch release update run: https://github.com/viccuad/helm-charts/actions/runs/8263508789/job/22605107087

Also, tested updatecli/scripts/install_crds.sh locally, with various /tmp/crds-{controller,audit-scanner}.tar.gz.

Additional Information
Tradeoff

Potential improvement
I don't like the added complexity created by adding the workflow_dispatch inputs, and needing to pass it to the js scripts via GH env vars, but it is what it is.
About the refactors, I'm happy splitting the commits in several PRs. I tested it altogether to save time. If they aren't wanted they can be dropped, or we can go with https://github.com/kubewarden/helm-charts/pull/399.

Updated input fields from review:


Re-add liblzma as an explicit dependancy on Linux

(NOTE: This was fixed before, but was incorrectly reverted in https://github.com/flutter/flutter/pull/78415)
Description
If this library is missing, builds fail with:
//lib64/liblzma.so.5: undefined reference to<EMAIL_ADDRESS>NOTE: Some distros have this library installed by default (such as Ubuntu), and some do not (such as Fedora 33+).
Related Issues
Resolves: https://github.com/canonical/flutter-snap/issues/17
Tests
I've updated the relative flutter-doctor tests.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Resolves: canonical/flutter-snap#17

If this issue only happens with the snap, then doesn't that mean that reverting it was correct? It's not clear to me what makes this different. Do we have a direct include of this somewhere?

Resolves: canonical/flutter-snap#17

If this issue only happens with the snap, then doesn't that mean that reverting it was correct? It's not clear to me what makes this different. Do we have a direct include of this somewhere?

I'm so sorry! You're right, this is only snap-specific. I got misled yesterday by errors from a crusty CMakeLists.txt: https://github.com/canonical/ubuntu-desktop-installer/commit/76ae8e5ee83e613321dfd41fa22c0a89fb8f561f
Thank you for being thorough as always @stuartmorgan!


Fix boundary selection issues

Fixes https://github.com/facebook/lexical/issues/1904. This was an interesting one. Logically, we were missing some selection resolution code around the handling of inline elements – but by fixing that, it also made it clear that some of the logic for handling links and character offset resolution was also a bit loose. This PR fixes that and adds a regression test to capture that main issue.

Impressive PR as usual. Seems like some E2E tests are genuine failures?

Somehow the CI is running for a very long time as playwright waits for an element to be visible to click on, retrying literally over 1000 times. We need to add a timeout somewhere - maybe in the workflow, as @fantactuka suggested, or somewhere in the playwright config (or both)


Node-gyp Installation Error

What's the problem with this?

@timcreative any suggestions?

Hello, @Moltivie ! Thanks for using our products ! Check if React is installed globally. If that doesn't work, the problem might be related to your npm/yarn version. Regards, Vlad.

Yes I got the same issue, It's look like react version. What is correct version will solve this issue.
Do you have version number ?

We removed deprecated deps/ plugins and now you should not get the error. If you still want to use the plugin version, try using npm --force install or npm --legacy-peer-deps install for now.


first cut of Windows secret store

@patrickxb The tests pass but I realize that if we ship this as-is, people will be prompted to log in again, leaving the unlocked file-based creds laying around, right? should we do something about that?

Can't you store the creds from the .ss file into the windows password manager, and then delete the .ss file?

I would do something like max suggested.  Create a secret store file via NewSecretStoreFile(g.Env.GetDataDir()), retrieve the secret from it, store it in the windows secret store, then clear the secret from SecretStoreFile.
I'm working on an improved secret store file in my current branch, so use RetrieveSecret and ClearSecret and don't mess with the files directly otherwise it won't work.

This looks good to me.  I think some real-world testing before this gets released would be a good idea to make sure the upgrade from file to wincred works and that starting from scratch works.

Is this available on all versions of windows?

These functions are Windows XP and later: https://msdn.microsoft.com/en-us/library/windows/desktop/aa374804(v=vs.85).aspx?f=255&MSPPError=-2147217396
@patrickxb What is an admin build exactly? devel tag? lack of production tag? I will make a production build off this branch right now and sanity check it.

Admin builds are the internal builds that we get daily.  I assume those happen for windows too?
You can check KEYBASE_FEATURES=admin via G.Env.GetFeatureFlags().

The admin/test channel builds are delivered per updater ID, which is set on the server side, and are not compiled or run any differently otherwise AFAIK, at least on Windows. Or if they're supposed to be, they're not now.
I see where the environment or configuration is checked for a string in the list of feature flags called "admin" in libkb/features.go, but no code calls FeatureFlags.Admin() - I will add a check for that though.
The problem with building just this branch in the test channel is that automatic daily builds off Master also go in there, so people will get updated back off of this build and not have their .ss files any more.

did something happen in git for this branch?  55 files changed...

I merged Master in, probably that was it. Stripped it back out for now.
Build is http://s3.amazonaws.com/prerelease.keybase.io/windows/Keybase_1.0.44-20180226115625%2B696302344.386.exe if anyone wants to try - works fine for me.

can I merge this?


Second order mesh, MFEM format vs VTK format

I have written a second order PUMI mesh to MFEM format then print it once using 'MFEM::Mesh::Print()' and once using 'MFEM::Mesh:PrintVTK()'.
The VTK format loaded in Paraview shows a second order mesh as expected, however the MFEM format  loaded in glvis shows a linear mesh as you can see in the attached snapshots.  The MFEM format do have the nodes section required for the higher order meshes.

MFEMformat.mesh.tar.gz

Press the 'o' key a few times to increase the sub-division factor. See README for more key commands, and the "3D data commands" section for some 3D specific keys.

That's a really nice mesh @KazemKamran :)


ModelGenerator has missing namespace import for Str class

I got the fatal error when generating model in PHP 7.0.33 using laravel-generator 5.5 branch.
Will provide the fix.

I suspect it was introduced in revision 1ff70059

Issue fixed


do not set Range header for initial call to get stderr

When stderr log file is 0 bytes and client sends a request with a Range header, server returns an error. This PR only adds the Range header when the cached stderr is not None or 0 bytes.

And one last comment, I think that since Genie supports ranged requests, we should probably support passing a range through the interface.  I would love to be able to do this:
print rj.stderr(-1000)

Or something similar


Feature: add previous flag values to hovertext

For current implementation
Within Augment_Snapshot(), will need to modify the output of Study_Assess() rather than the flat files created with StackSnapshots().

when you mouseover a cell, should show up to 5 previous flag values

e.g., Previous Flags:

snapshot date: value
snapshot date: value
snapshot date: value

update longitudinal data model/Augment_Snapshot() to support this

@andersonjake1988 - after some of the QTL reports that are higher in the backlog, let's team up on this one to add flag values to the <title> attribute so that it's accessible during mouseover.

Closing since the Overview_Table() function will need to be refactored after a custom JS table is created/finalized.


[FLINK-7784] [kafka-producer] Don't fail TwoPhaseCommitSinkFunction when failing to commit during job recovery

What is the purpose of the change
This makes it possible to configure the TwoPhaseCommitSinkFunction's behaviour w.r.t. transaction timeouts.
Brief change log

Introduce transaction timeouts to TwoPhaseCommitSinkFunction.
Timeout can be used to generate warnings if the transaction's age approaches the timeout.
If an exception is thrown during job recovery, the sink can be configured not to propagate the exception and instead log it on ERROR level.

Verifying this change
This change added tests and can be verified as follows:

Extended unit tests for TwoPhaseCommitSinkFunction to test added functionality
Manually verified the change by running a job with a FlinkKafka011Producer with checkpoint interval 27000 and transaction.timeout.ms = 30000. Warnings were generated correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@aljoscha

The changes look very good! @pnowojski could you please also have a look at this?

LGTM, thanks for the work @GJL. Merging this ..


Topic "Legacy Factories Replacement": Invalid (XML)View.create Setting

In the new documentation topic Legacy Factories Replacement, some of the samples snippets use invalid setting property ("view"). Additionally, a link to the corresponding API in each sample would be great so that readers don't have to search for that method explicitly in the API Reference page.
What is the expected result?

Valid setting name: view --> viewName in View.create as well as in XMLView.create
Link to the relevant API reference

Something like this:

Legacy, synchronous API
Modern API

var oView = sap.ui.view({
  viewName: "my.View",
  type: "XML"
});

sap.ui.require([
  "sap/ui/core/mvc/View"
], function(View) {
  View.create({
    viewName: "my.View",
    type: "XML"
  }).then(function(oView) { /*...*/ });
});

API Reference: sap.ui.core.mvc.View.create

Thanks for reporting this issue. We created a fix for it and it should be visible soon.

@svbender Thanks. I can see the fix now, but only the "Modern API" part.
In the "Legacy, synchronous API" part, however, the invalid setting "view" is left to be replaced.

It should be "viewName" instead of "view". See sap.ui.view, sap.ui.xmlview

@boghyon Thanks you.  It should be updated now!


Migration & Community: Research Sponsor User Programme

Program Q2-4
### Tasks
- [x] Create research approach/indicative requirements on participants to be signed-off by @shinytoyrobots  and shared with sponsor user tems [in progress, see comment 17/04]
- [x] Draft research brief & upload for research PMs tracking
- [x] Author repeating "experience of adoption" interview questions
- [x] Gather team feedback (devs for devs ect)
- [x] Create and share engagement memo and location for data storage for the sponsor user program
- [ ] Decide whether early May interviews used for pattern docs or community index
- [ ] Schedule early May interviews with Salt-assigned team member and interviewee
- [ ] Early May interviews and analysis (part 2 likley tracked by another ticket)

Inital ask to team leads to provide indication of who is in the team and how they contribute to the delivery of the product (at role or discipline level).
Propose 45 min interview with representative sample of team in early May.

Part 1: first 15 min of interviews will set a baseline for longitudinal data collection on the team's experience of adopting and using the design system.
Part 2:

Propose that Salt dev or developer assigned to sponsor team attend inital interview.
Additionally, propose that when our team engages with a sponsor user team they add a memo to file so we can collect this as "naturally occurring" data and draw on as a team.
Use of sponsor user teams in next two months will be

Team Call Updates
Parsa - April 17 - robin is scheduling calls with teams. Aim - consistent data collection

To what extent is the design system supporting their business deliverables, how closely aligned is SALTs delivery of components and patterns with their requirements

In Progress, Annia picking up. Robin to cover during time off

@parsakhan21 research work in progress - & catching up with Robin this afternoon on meetings w/ teams

created interview memo / template which is with Robin for review alongside brief

@zdxd hi zoe, did you ever receive feedback on this from Robin?
FYI @shinytoyrobots

yep Robin reviewed, protocols done, awaiting the org / kick of of meetings with sponsor users to start data collection

Hi @parsakhan21 what's the update on sponsor users?

Combining workstream with Designer-Developer workflows

Oct-2: Backlogged / sunset workstream in beginning Q3


configmap and serviceaccount for kube-dns

Extracted from https://github.com/kubernetes-incubator/kube-aws/issues/542
Although we've upgraded kube-dns to the latest 1.14.1 via #582, we're still missing (1)configmaps mounted as volumes and (2) serviceaccount for kube-dns.
Survey the upstream setups for those and adapt if necessary.
cc @c-knowles

What do we lose out on without this? At least RBAC won't work right?

I'm fixing a regression bug in TLS bootstrapping, and since TLS bootstrapping should go along with RBAC, I'm also attacking this in the same PR.

@mumoshu Does this permit usage of this feature?
http://blog.kubernetes.io/2017/04/configuring-private-dns-zones-upstream-nameservers-kubernetes.html

@mgreenwald-pm Yes, it should 👍 Just edit the kube-dns confgimap to add settings mentioned in the article.

@mumoshu Yes, thank you and it worked!


Feature: Add CancellationToken to Fetchinfo to abort Fetches WIP

Adding a CancellationToken to FetchInfo to abort Fetches. This is the second part to remove IDisposable from Map. Because then I can have a Central CancellationTokenSource and when this is aborted all fetches will stop. More than todays IAsyncDataFetchers. So when this is implemented The IDisposable can be removed.
This implementation isn't finished yet, I think there are other Places where I can add the CancellationToken to improve the abort.

I was thinking about System.Threading.Channels.Channel to replace the workers. It may still need a CancellationToken but it will probably work different.

The goals is to remove IDisposable from Map. How will this work eventually? The HttpCients still need to be disposed. I would think this first step is to make the ILayer not disposable.
My idea is to solve this with a central FetcherMachine which is not in the Layer but in the MapContol or the Map. But this is a big change with many complications which I want to work on myself.

My idea behind is this. There are two things that are done in the Map Dispose.

Disconnecting Events. (This is now handled with WeakEvents)
Aborting the Fetching of Data. (For this I planned to use the Cancellation Token).
The Dispose can now be removed (Because the Map Behaves now the same.

Further improvements like Central Fetcher, Channels, Disposing of HttpClients, ....
The Central Fetcher would simplify this massively. Maybe I have to Recreate the pull request with CancellationTokens on ly on AsyncData Fetch Functions.
Like
public interface IProvider
....
Task<IEnumerable<IFeature>> GetFeaturesAsync(FetchInfo fetchInfo);

I'll redoing this pull request


arm osx migration

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] 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.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi @xorg-libxtst this is ready to be merged. Thanks!

Fix #7

Thanks for the review @pkgw - it should be ready to go now.


no package lock

Description
see #124

the idea is that modules that installed through npm (libs, plugins, clis) should not have a package-lock.json. We took the decision (internally) to follow this principle for all aio plugins and libraries. The package-lock.json file is never included in published package, and while some locked dependencies might work for the local setup, there might have been a patch or minor update in the dependency tree that breaks the plugin when installed via npm (or via a parent module, e.g. aio-cli). And because there is a package-lock in the dev local setup, the breaking update in the dependency tree will not be noticed when developing. More details in this article: https://www.twilio.com/blog/lockfiles-nodejs. Hope this helps 🙂

Types of changes

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

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

some tests are failing not so sure why..

Will https://github.com/adobe/aio-cli-plugin-boilerplate/blob/master/.npmrc be updated? I guess I'm still not sure why if this decision was made it isn't documented somewhere "owned" by Adobe.

@justinedelson thanks good catch! 😄 https://github.com/adobe/aio-cli-plugin-boilerplate/pull/6


add shosushi resolver

close #27

Current coverage is 86.87%

Merging #115 into master will increase coverage by +0.56% as of 0370f67

@@            master    #115   diff @@
======================================
  Files           45      45
  Stmts         1067    1074     +7
  Branches       266     268     +2
  Methods          0       0
======================================
+ Hit            921     933    +12
- Partial         75      77     +2
+ Missed          71      64     -7

Review entire Coverage Diff as of 0370f67

Powered by Codecov. Updated on successful CI builds.


Simple Login page UI using flutter

A minimal login page made in flutter and is suited for beginners who are just starting out. Please assign this issue to me

@Shashank0271 you can start working

it's going to be a single page, not a whole UI bundle. Is that accepted ?

If you are creating login ui make sure you have signup and forget password ui as well

I want to make animated UI & for it.
Can you Please assign this issue to me.

if @Shashank0271 is not working on the issue. Then please assign it to me as I have already made the UI.

@tanmoy27112000  Sir I've completed the task.
Actually, I'm facing some difficulties during push & pull request.
Can you please guide me with it?


Array DC Power and DC-connected battery

For DC-connected batteries, the "Array DC power" output variable is the combined power of the battery and array, so it actually actually the DC power at the inverter input. It would be useful to show the array power and battery power as separate variables, or to rename the variable.
Results for DC-connected battery:

Same system, but AC-connected battery:

Also, variable names like "Electricity to grid from system" are confusing because the battery is part of the system, but the variable does not include electricity from the battery. However, there is not a good alternative to "system" that works for both PV Battery and Generic Battery configurations, and possible future implementations such as Wind Battery.

Fixed in https://github.com/NREL/ssc/commit/ce96913e5c228bb96b702211269a8d0c8efd571d


[refactor] payment service partial work

Codecov Report

:exclamation: No coverage uploaded for pull request base (enhancement/payment_service@20abce0). Click here to learn what that means.
The diff coverage is 11.45%.

@@                      Coverage Diff                       @@
##             enhancement/payment_service    #1194   +/-   ##
==============================================================
  Coverage                               ?   19.31%
==============================================================
  Files                                  ?      360
  Lines                                  ?    14619
  Branches                               ?     1302
==============================================================
  Hits                                   ?     2823
  Misses                                 ?    11438
  Partials                               ?      358

Impacted Files
Coverage Δ

.../mercadopago/android/px/core/PaymentProcessor.java
0% <ø> (ø)

...droid/px/internal/features/hooks/HookActivity.java
0% <ø> (ø)

...ago/android/px/internal/view/ComponentManager.java
0% <ø> (ø)

...ponents/payment_method/PaymentMethodComponent.java
47.05% <ø> (ø)

...m/mercadopago/android/px/internal/view/Button.java
25% <ø> (ø)

...s/review_and_confirm/ReviewAndConfirmActivity.java
0% <ø> (ø)

...android/px/internal/view/RecoverPaymentAction.java
50% <ø> (ø)

.../components/actions/ChangePaymentMethodAction.java
50% <ø> (ø)

...m/mercadopago/android/px/internal/view/Footer.java
18.75% <ø> (ø)

...nfirm/components/actions/ConfirmPaymentAction.java
0% <ø> (ø)

... and 37 more

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 20abce0...71b8d11. Read the comment docs.


[FEATURE] SyncVariableInstancerToCollection ... change _syncToCollectionKey to StringReference

Is your feature request related to a problem? Please describe.
Why is the _syncToCollectionKey a string and not using the StringReference? I find it more useful when syncing, to save my keys as constants, as my application expects specific keys when reading from collections. This might be useful for other people as well, and does not make Atoms more or less complex.
Describe the solution you'd like
Original:
private String _syncToCollectionKey = default;
Replace with:
private StringReference _syncToCollectionKey = default;
Additional context
I am creating a system that transfers data over virtual cables. The data is in the shape of Atoms Collections, and receivers verify that the data layout are compatible before attempting to read the data using the keys I have specified as Atoms String Constants.

I am also wondering why the _syncToCollectionKey is a string and not a StringReference. Had you any problems with your solution so far?