Make drop_last configurable in data loaders

Is your feature request related to a problem? Please describe.
A common gotcha with SCVI, etc. is encountering the following error in BatchNorm1D
Expected more than 1 value per channel when training, input size torch.Size([1, 128])

when the dimension of the data is such that the last minibatch has size 1. See for example #221, #426, #2214, #2314.
The previously accepted solutions have been to change the batch_size parameter to some value such that there is no batch of size 1.
However, this is not so easily accomplished for models like scvi.external.SOLO, where the actual training data size is not easily computed from the original data size unless one knows the technical details or follows the code very closely.
Describe the solution you'd like
The simplest solution to the problem would be to configure the training/validation data loaders with drop_last=True, since it is only the last batch that could have size 1.
Right now, this argument is hard-coded
https://github.com/scverse/scvi-tools/blob/9b5f5537ff5f8f1066e6a6170c4d5e6660b56793/scvi/dataloaders/_data_splitting.py#L488
Changing the default would eliminate a commonly occurring and confusing error.
As an alternative, making it configurable via a keyword argument would provide a simpler solution to users who encounter the problem.

Hi, thanks for the suggestion. Unfortunately, we aren't planning on changing the default value of drop_last because of backwards compatibility. However, we do currently allow users to pass in this argument via datasplitter_kwargs (see here), which will be passed in to the AnnDataLoader constructor. Let me know if this works for you.

Closing as the issue is addressed

Hi, this issue doesn't solve yet, since in the latest version, it still make drop_last as false, then I cannot assign it as true...
https://github.com/scverse/scvi-tools/blob/95f2e1d2fa921c6433a04e257d844280ba0c25e5/scvi/dataloaders/_data_splitting.py#L145

Hi @martinkim0, where can we pass drop_last=True in the SCVI model? It doesn't work if I pass it to model.train() or when setting up or initiating the model. I am having the same issue @aksarkar mentioned above with an scvi.external.SOLO model, where I can't tell what the minibatch size is (the number of cells in the batch % 128 is not 1). Thanks!

After reading a bit more, I tried passing drop_last=True into scvi.external.SOLO.train via datasplitter_kwargs like so:
datasplitter_dict = {
  "drop_last": True
}
scvi.external.SOLO.train(solobatch, early_stopping = False,datasplitter_kwargs=datasplitter_dict)

and I get the following error:
TypeError: scvi.dataloaders._data_splitting.DataSplitter() got multiple values for keyword argument 'batch_size'.
I think this means drop_last=False is still hard-coded, no?

I am stuck exactly where @schroeme is right now as well. Just trying to pass datasplitter_kwargs={"drop_last":True}.

Hi @martinkim0, I'm having this issue too (I can't seem to find a place to add drop_last=True). The link you posted for datasplitter kwargs seems to be broken. Thanks!

Hi, I will push a fix later today. Sorry for the issues reported here. Please reopen issues when posting in closed issues. It is otherwise difficult to track these.

Thanks so much!


fix(update-balances): Switching from Blockbook to Electrumx

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


forceAtlas2 adjustSizes setting

At #L525 in forceAtlas2 worker, the adjustSizes setting is tested, but the two arms of the condition lead to the same code:
https://github.com/jacomyal/sigma.js/blob/c49589f2419ca98542fd21b82b926dea21bb9fef/plugins/sigma.layout.forceAtlas2/worker.js#L527-L534
https://github.com/jacomyal/sigma.js/blob/c49589f2419ca98542fd21b82b926dea21bb9fef/plugins/sigma.layout.forceAtlas2/worker.js#L545-L552
What is the intended behavior? See also #1109

The issue here is that anticollision cannot really work with repulsion approximation through barnes-hut regions. So yes one of the branch is maybe pointless and could be simplified. The whole anti-collision scheme of the algorithm is seldom used as people tend to apply anti-collision separately at the end of FA2 since it could slow down or even hamper convergence in some cases.


Sitemap.resource array reversed when building

This is a really odd one, I've tried to debug as best I can but I can't find the issue. I'm building a sitemap.resource array for some page navigation for a portfolio. So using the code below...
<% work_pages = sitemap.resources.select{|p| p.data.type == "work-item" } %>

  <% work_pages.each_with_index do |p, index| %>
    <% if p.url == current_page.url %>
      <% next_page = work_pages[index+1]  %>
      <% prev_page = work_pages[index-1] %>

<%= link_to("Prev «", prev_page.url) unless index == 0 %>

<%= link_to("Next »", next_page.url) unless index == work_pages.size - 1 %>

    <% end %>
  <% end %>

I'm dynamically generating these pages using the following code and adding some front matter to the layout template to only pull through those pages.
data.work_items.clients.each_with_index do |client, index|
  proxy "/work/#{client.url}.html", "/work-item.html", locals: {
    client: client
  }, :ignore => true
end

This works fine in development but when I build the site the array gets reversed in order. I'm currently having to hack it to reverse it in build.
<% if development? %>
  <% work_pages = sitemap.resources.select{|p| p.data.type == "work-item" } %>
<% elsif build? %>
  <% work_pages = sitemap.resources.select{|p| p.data.type == "work-item" }.reverse %>
<% end %>

Any ideas? My source code is available at https://github.com/thisiscapra/thisiscapra.com

Can you post the .yml file as well?

Oh, never mind. I'll look in to it.

Ah, okay, I know what this is.
The sitemap has no specific order, anything can add, remove or reposition anything else in the sitemap. In build, there is probably additional sitemap manipulators running and rearranging things.
You should sort the result of select to make sure it maintains the order you want.

Ah okay, I'll give that a try. Thanks for looking into it, I thought I was going mad! Out of interest is there an easy way to sort by the current data yml order?

Order? The items in the sitemap are references to file paths usually. Do you have a list of resources elsewhere in yaml? In that case you could take that yaml array, and map it to individual sitemap resources and that would have the correct order.


Don't scale/zoom image larger than the original image if no larger image provided

The last image in the example (the antelope) should serve as a good test case.

On third thought, I don't think this a use case for this library. If you want to zoom image, you're going to get a zoomed image -- the fact that you didn't provide a higher-res photo initially or as the zoomImage doesn't concern us.


Deleting the vapor-3 branch

I think we're done with it by now @finestructure? Should I delete it?

Fine by me!

Done.


⚠ Jenkins Plugins Artifactory has degraded performance

In 10ff73f, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1512 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 7c08943.


Add library dependencies to platformio.ini

The file platformio.inialready contains information on the framework required to build a project. If it is missing, platformio offers to automatically install it. However, if the same project requires a library already known to the platformio library manager, the following manual steps are necessary:

Build using "platformio run" and examine output for missing library
Perform library ID search using "platformio lib search"
Use "platformio lib install ID" to install library
Repeat from step 1

I propose adding a new statement to platformio.ini that allow to specify required libraries in the form
require-libs = ID1 [, ID2 [, ..]]
instructing platformio to check if one or more of the required libs are missing and if so, suggest to automatically install them before proceeding the build.

Yes, declaring library depedencies is a great feature in npm.
Sent from my Windows Phone

From<EMAIL_ADDRESS>Sent: ý3/ý22/ý2015 15:57
To<EMAIL_ADDRESS>Subject: [platformio] Add library dependencies to platformio.ini (#134)
The file platformio.inialready contains information on the framework required to build a project. If it is missing, platformio offers to automatically install it. However, if the same project requires a library already known to the platformio library manager, the following manual steps are necessary:

Build using "platformio run" and examine output for missing library
Perform library ID search using "platformio lib search"
Use "platformio lib install ID" to install library
Repeat from step 1

I propose adding a new statement to platformio.ini that allow to specify required libraries in the form
require-libs = ID1 [, ID2 [, ..]]
instructing platformio to check if one or more of the required libs are missing and if so, suggest to automatically install them before proceeding the build.
—
Reply to this email directly or view it on GitHubhttps://github.com/ivankravets/platformio/issues/134.

I don't have any objections :) How about to name this option like deplibs?

Sounds good to me :smiley:


Add rextendr use case to integration tests

The current integration tests test whether we can use extendr code in an R package, but they don't test whether we can call rust_source() or rust_function() from rextendr. I think we should add such a test, to make sure we don't accidentally break rextendr down the road.
cc @Ilia-Kosenkov

PR #173 introduced a new CI step that duplicates R CMD check procedure also for the latest version of {rextendr}.
{rextendr}'s dynamically-generated rust libraries are linked to the dev version of extendr-api that is tested by the CI.
This solution ensures that only one {rextendr} test codebase exists, and that any new features added to and tested by {rextendr}  are also automatically tested by extendr CI.


[Look&Feel] Consistency and density improvements

Description
This PR applies the following Look & Feel density and consistency improvements:

Use small context menus
Use empty buttons for navigational buttons
Use primary buttons only for primary calls for action
Standardize paragraph font size (15.75px next theme / 14px V7 theme)
Use semantic headers (H1s on main pages, H2s on modals/flyouts)
Using small tabs
Use small padding on popovers

This PR, along with #2079, should mean all of the Look & Feel pattern guidances are applied to the Security Dashboards plugin.
Category
Enhancement
Why these changes are required?
UX
Screenshots
Context Menus
Removed popover padding from context menu

Scope
Before
After

Tenant Actions

External Button
Note that the external button component was changed from a smallButton to a smallButtonEmpty component, and is responsible for all the changes below:

Scope
Before
After

External Button: Getting Started

External Button: Permission

External Button: Map Users

Primary Buttons

Scope
Before
After

Getting Started

Getting Started

Paragraph Size

Scope
Before
After

Audit Log

Internal User

Roles: Duplicate

Roles: Map

Headers

Scope
Before
After

Audit Logs

Audit Logs: Settings

Authentication

Get Started

Internal User: Create

Internal User: List

Permission

Roles: Create

Roles: List

Roles: Map

Roles: Role Page

Tenancy

Modals

Scope
Before
After

Account: Reset

Account: Select

Account: View

Account: View

Configuration

Delete

Expression

Tenant: Default

Tenant: Edit

Tenant: Save

Tabs

Scope
Before
After

Role View

Tenants

Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

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

@danieldong51 can you do us a huge favor and address cypress failures on the workflows in this repo and in FTR? For example I see a following error originating from FTR:
  1) Audit logs page
       should load Audit logs page properly:
     AssertionError: Timed out retrying after 60000ms: Expected to find content: 'Audit logging' within the selector: 'h3' but never did.
      at Context.eval (http://localhost:5601/__cypress/tests?p=cypress/integration/plugins/security/audit_log_spec.js:172:10)

Similarly, for your PRs in other repos, we may want to update these to make sure 2.17 release goes smoothly

@danieldong51 looks like the CI issues within this repo are fixed. Can we open a draft PR in the FTR and we can continue to address those/after the build succeeds? Once that PR is linked here I feel good about merging thanks!

@danieldong51 looks like the CI issues within this repo are fixed. Can we open a draft PR in the FTR and we can continue to address those/after the build succeeds? Once that PR is linked here I feel good about merging thanks!

Yes, I just opened one here!

Changes look good. Thank you @danieldong51 for taking time to upload screenshots. One question I have is to understand "Use primary buttons only for primary calls for action". Does it mean the design is reserved only for calls like Submit, Delete, etc. If yes, this change will make the buttons, without the boundary, look like href links. Is this expected?

I believe that buttons that are navigational should be turned into empty / text buttons, so that is expected. I am waiting on review from the Look&Feel team to make sure these buttons are navigational @virajsanghvi.

I would revert this one (going from primary action to just a secondary link seems like a big dropdoff). As its the cta of the workflow, I think keeping it as-is is safer

Similarly, can we keep these as is: I think they're the main CTA for these steps (Agree not ideal having multiple CTAs on same page, but I'd rather have a designer make a call here and not sure anyone has bandwidth):

Changes look good. Thank you @danieldong51 for taking time to upload screenshots. One question I have is to understand "Use primary buttons only for primary calls for action". Does it mean the design is reserved only for calls like Submit, Delete, etc. If yes, this change will make the buttons, without the boundary, look like href links. Is this expected?

I believe that buttons that are navigational should be turned into empty / text buttons, so that is expected. I am waiting on review from the Look&Feel team to make sure these buttons are navigational @virajsanghvi.

It is subjective. Ideally there's only a single primary button/cta on a page/surface. For purely navigational buttons, ones that aren't necessarily helping customers complete an action or save a form, the guidance is to use an empty button/link. But again, subjective, and as page owners, if you think any of these aren't the right treatment, it's fine to request no change here. You will be having reviews with UX and they can point out if any changes are necessary (they are stretched thin atm otherwise I'd just ask now).

I would revert this one (going from primary action to just a secondary link seems like a big dropdoff). As its the cta of the workflow, I think keeping it as-is is safer
Similarly, can we keep these as is: I think they're the main CTA for these steps (Agree not ideal having multiple CTAs on same page, but I'd rather have a designer make a call here and not sure anyone has bandwidth):

Reverted external button component and primary button instances changes.


remove spring default qos-enable

What is the purpose of the change
fix 12779
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

fix https://github.com/apache/dubbo/issues/12779 make this propertis load first so that spring boot config default will not configed

In order to fix #12779, we should remove the hard code of qos-enable=true when parsing spring proeprties.

In order to fix #12779, we should remove the hard code of qos-enable=true when parsing spring proeprties.

But where can we set default true value when user doesn't set qos-enable

In order to fix #12779, we should remove the hard code of qos-enable=true when parsing spring proeprties.

if we let dubbo.properties load before application.yml，the default value will not set

In order to fix #12779, we should remove the hard code of qos-enable=true when parsing spring proeprties.

if we let dubbo.properties load before application.yml，the default value will not set

This is a breaking change, and if it can only fix qos-enable is not worthable. We should fix it in application.yml.

org.apache.dubbo.spring.boot.env.DubboDefaultPropertiesEnvironmentPostProcessor#createDefaultProperties

but the other  spring default props also not valid in dubbo.properties  such as dubbo.config.multiple, because the application.yml is load before dubbo.properties @AlbumenJ

Please also fix test cases

Codecov Report

Merging #12861 (0445ec7) into 3.2 (ceae48e) will decrease coverage by 0.34%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                3.2   #12861      +/-   ##
============================================
- Coverage     69.81%   69.47%   -0.34%
+ Complexity      341        2     -339
============================================
  Files          3523     1648    -1875
  Lines        167515    68371   -99144
  Branches      28043     9989   -18054
============================================
- Hits         116953    47503   -69450
+ Misses        40473    16285   -24188
+ Partials      10089     4583    -5506

see 1898 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


automatically remove users no longer on the server from events when the event is interacted with

the member information was being cached by the bot, so it didn't recognize the member had left


⚠ Bofrost.es has degraded performance

In 96b2ca0, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1835 ms

Resolved: Bofrost.es performance has improved in 995866e after 14 minutes.


Missing aws CLI in homeroom image

Lab 2.2

Can we remove the dependency by switching to a raw CURL command?


NPE when trying to add null Map or List claims

Description
I'm getting a NullPointerException in JWTCreator#validateClaim(List<?>) and  JWTCreator#validateClaim(Map<?, ?>) methods when trying to add a null map or list claim.
At the same time, JWTCreator#addClaim(String, Object), that would be called after validation, accepts null values and deletes a claim in this case.
I guess, validation can be performed only on not-null maps and lists.
Please, excuse me for wasting your time if it's an expected behavior.
Reproduction
Code sample for List:
JWT.create()
    .withClaim("listClaim", (List<String>) null)
    .sign(Algorithm.HMAC256("MySecret"));

Code sample for Map:
JWT.create()
    .withClaim("mapClaim", (Map<String, ?>) null)
    .sign(Algorithm.HMAC256("MySecret"));

👋 Thanks for reaching out. I think those 2 methods should keep the behavior of the other withClaim methods. This is, whenever a key is non-null but the value is null, remove that key from the final claims set.
I'll move it to the backlog.

We should be able to release this next week. Thanks


Failed to Render

Tried deploying a .NET 5 Application to App Service and got the following error

Pipeline provisioning job failed with error: 'Error=Failed to render: Evaluation error: Helper 'beginsWith' called with wrong number of arguments, needed 5 but got 0 Current node: Expr{Path:Path{Original:'beginsWith', Pos:3}, Pos:0}, Message=Mustache parsing failed'

No other errors in logs
Here is a repo to test
https://github.com/isaacrlevin/.NET-Conf-Demos/tree/main/AppService

Hey @isaacrlevin ,
After providing the Github PAT, when it gives a list of pipeline templates, which one did you choose?

ASP.NET web app to App Service

@isaacrlevin, thanks a lot for your patience. The issue has now been fixed.


Filed to generate class based on enum

Failed to generate
schema:
type UserUpdateNotification {
  title: String
  body: String!
  class: UserUpdateNotificationClass!
  reference_nr: String
}

enum UserUpdateNotificationClass {
  success
  error
  info
}

output:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile (default-compile) on project ***: Compilation failure [ERROR] /***/client/UserUpdateNotification.java:[99,81] getClass() in com.***.client.UserUpdateNotification cannot override getClass() in java.lang.Object [ERROR]   overridden method is final

Arg, yes.
As the schema has a ´class´ attribute, the code generates a ´getClass()´ method.
I'll correct that, by protecting standard Object's ´_getXxxx()´ methods, by replacing them by ´getXxxx()´.
In the meanwhile, you can (if possible) rename the ´class´ attribute by ´_class´ or ´class2´.
Étienne

thats part of a predefined schema provided by a resource supplier
we are not allowed to modify, just have to get "as is" and build a backend client
in the moment GraphQL server feeds data to numerous GUI frontends and any changes forbidden
is there any way to avoid such exceptional case in generator codebase?

Hello,
There is only one getter that could generate this error, for the class attribute.
The generated methods getClass and setClass are now generated as get_Class and set_Class .
This correction is available in the new release: 2.3.2
Etienne

works!
many thanks!


emails: Fix outdated email references and typo.

Some small clean-ups related to recent onboarding and demo organization email changes.

Updates any "day1" or "day2" references to previous names for onboaring emails
Fixes a typo in the email confirmation for demo organization owners.

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Looks good -- that "typo" in the second commit was a merge ordering issue; 4544eb4576b0f1244916be66ffe609ad4f71965a was merged while 91b40a45fe916f72bc6664ed219f04871b0d52d1 was still under development.


Deprecate download flag (useGlobalNode)

Deprecate download flag and introduce useGlobalNode instead. If this is true, then it will use global installed node (that is in path) instead of downloading node.

I like this plugin because it means that my project only depends on Java being installed; with the Gradle wrapper, Gradle will download and update itself, while this plugin handles downloading/updating NodeJS.
If you work with a team of developers, then these features are handy because it means that the whole team is always using the same version the toolchain, which makes it easier to reproduce problems. Using system-installed software increases the likelihood of "Works on my machine" which can be difficult to track down.
Deprecations should generally only be done when you have a suitable replacement - in this case download and useGlobalNode do different things, and therefore the latter is not a replacement for the former. It would perhaps be better to recommend useGlobalNode (if that is your preference), without deprecating download.

Sorry, did not see this comment before now. Yes, I know, 8 months later :-) You are absolutely right. Will not deprecate download, but will default set this to true in the 1.0 release. Starting to write a migration guide of breaking changes here: https://github.com/srs/gradle-node-plugin/wiki/Migration-Guide


Is there a way to set quality?

Is there a way to force what quality of video is downloaded?

Hi,
As of now, the script selects the best stream available, but it would be a great feature to support!


Add content to file

In this project, I add validations to my models and have create specs for them.

Hi @obed300
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that has linters errors. Kindly fix all linters errors
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


move TaskRoleArn out of ContainerDefinitions #2

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

After applying this fix, I was able to get the pipeline to succeed, and to move forward with the workshop3 lab.
Note: I had to delete manually the broken prod-iridium-service stack, as CodePipeline was not propagating the service.yml modification from the staging step.


Reached better test coverage on mycollections exercises.

Added tests on linkedList enlarge and hashmap enlarge. Added tests for linked list(only parent class was tested before).

OK :)


fixes decorator

Codecov Report

Merging #4 into master will increase coverage by 13.63%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           master       #4       +/-   ##
===========================================
+ Coverage   83.33%   96.96%   +13.63%
===========================================
  Files           1        1
  Lines          36       33        -3
  Branches        3        3
===========================================
+ Hits           30       32        +2
+ Misses          4        0        -4
+ Partials        2        1        -1

Flag
Coverage Δ

#backend
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pydantic_webargs/__init__.py
96.96% <100.00%> (+13.63%)
:arrow_up:


v0.8.9_20: Slider bar for opacity of non-selected bubbles , is not functional

SEVERITY:  Major
MODULE: Bubble map chart
Platform:

Windows 7 / Chrome 46.0
MAC / Chrome 46.0

RELEASE: Develop
STEPS TO REPRODUCE:

Navigate to the URL : http://static.gapminderdev.org/vizabi/develop/preview/bubblemap.html
Bubble map chart will be loaded.
Click Expand
Select a country bubble
A slider bar for opacity of non-selected bubbles is shown under ‘Find’ option
Drag the slider ball from that slider bar to change the opacity of non-selected bubbles
Note that Slider bar for opacity of non-selected bubbles, is not functional

ACTUAL RESULTS:
Slider bar for opacity of non-selected bubbles, is not functional
EXPECTED RESULTS:
Slider bar for opacity of non-selected bubbles should be functional
SCREENSHOT:

the event listener is missing (see bubble chart for example)


UI Improvement - Mismatch status

Could this be due to hard-coded string? You should create a mapping of display string value to some integer value corresponding to each status. This may give you the flexibility to later added support to other languages. This way the back end mapping never need to be change.

Closing this as unrelated to contract.


⚠ Bofrost.es has degraded performance

In 8fad1f4, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1512 ms

Resolved: Bofrost.es performance has improved in 9970de7 after 7 minutes.


More examples please

I'm raising this as a documentation issue.
I want to use Haskell or something Haskell-like, to write segments of code that will run in the browser, and work with existing JavaScript code.
This is basically “The JavaScript problem” mentioned in the "The refreshing simplicity of compiling Formality to anything" article.
I like the examples in Graham Hutton's "Programming in Haskell, second edition" book.
I've been able to implement Hutton's "Binary string transmitter" example in chapter 7 of his book, using Ramda, without too much difficulty.
Most functions require just one line of code.
The Haskell code from the book is available here.
See transmit.hs .
I'm now trying to implement the same example using Formality, but am finding it much more difficult.
Is there a tutorial with some pointers on manually converting Haskell to Formality, or on correspondences between the two?
Do you plan to implement additional Haskell-like functions on top of the Formality base, such as those found in the Hutton example(s)?
Could someone implement a few simple applications, perhaps including the above-mentioned "Binary string transmitter" example, or others that are out there in the Haskell universe?
I like what I've seen of Formality so far.
Ken

Hi! Thanks so much for your question!
We're currently working hard to finalize the Formality language specification by implementing Formality in itself. This is going to change a lot of things, so we're holding off on writing documentation and examples until that's done. I really like the Graham Hutton book a lot and am planning on writing a tutorial for Formality in that style.
However, since I don't want to leave you hanging, I'll walk you through how you could do transmit.hs in the current Formality. Just be advised that lots of this stuff is going to change.
So my first pass was to try to just directly translate the conversions functions:
import Base#

Bit : Type; Number

bin2int(xs: List(Bit)) : Number
  fold(__ 0, (x,y) => x + (2 * y) xs)

int2bin(x: Number) : List(Bit)
  let x = x >>> 0
  if x === 0 then nil(_)
  else cons(_ (x % 2), int2bin(x \ 2))

But there are a couple weird things about this. First, since Number is just JavaScript's number, we have to do the weird >>> 0 thing to get the division function (yes, that's a \ not a /, it's from a bad/temporary parsing hack and we're changing it) to do the right thing.
We think Number is going to go away as a Formality-Core primitive in Formality 1.0, but we'll have Word for integers and Double for floating point on the front-end language. Haven't totally decided yet, stay tuned.
Anyway, my second approach on transmit.fm was to use Formality's Bits bitstream type for some type-safety:
T Bits
| be
| b0(pred : Bits)
| b1(pred : Bits)

This let me write encode by turning Chars (which are just Numbers) into continuations:
encodeChar(x : Char) : Bits -> Bits
  let x = x >>> 0
  if x === 0 then b0
  else
    if (x % 2) === 0
    then (y) => b0(encodeChar(x \ 2)(y))
    else (y) => b1(encodeChar(x \ 2)(y))

encode(x : String) : Bits
  case x
  | nil  => be
  | cons => encodeChar(x.head)(encode(x.tail))

Then for decode we need some library functions that weren't implemented yet:
bits_to_number(x : Bits) : Number
  case x
  | be => 0
  | b0 => 0 + (bits_to_number(x.pred) << 1)
  | b1 => 1 + (bits_to_number(x.pred) << 1)

bits_to_number(x : Bits) : Number
  case x
  | be => 0
  | b0 => 0 + (bits_to_number(x.pred) << 1)
  | b1 => 1 + (bits_to_number(x.pred) << 1)

bits.take(n : Number, x : Bits) : Bits
  let n = n >>> 0
  if n === 0 then be
  else
    case x
    | be => be
    | b0 => b0(bits.take(n - 1, x.pred))
    | b1 => b1(bits.take(n - 1, x.pred))

bits.drop(n : Number, x : Bits) : Bits
  let n = n >>> 0
  if n === 0 then x
  else
    case x
    | be => be
    | b0 => bits.drop(n - 1, x.pred)
    | b1 => bits.drop(n - 1, x.pred)

chop8(x : Bits) : List(Bits)
  case x
  | be => nil(_)
  | b0 => cons(_ bits.take(8, x), chop8(bits.drop(8,x)))
  | b1 => cons(_ bits.take(8, x), chop8(bits.drop(8,x)))

decode(x : Bits) : String
  map(__ bits_to_number, chop8(x))

And finally a main for testing:
main : String
  decode(encode("foobar"))

To test, we can do:
$ fm -d transmit
"foobar"

Now for an exercise:
I have deliberately left a bug in the above example which you can see with
main : String
  decode(encode("ba;dddd"))

$ fm -d transmit
"ba;2222"

Eternal fame and glory if you can figure out why this happens and want to post the fix here.
In any event, I'll push the correct version to Base.fm when I add the String -> Bits library functions in the next day or two.

Excellent! I'll watch for the updates to Base.fm.

Looks like @MaiaVictor beat me to it on https://github.com/moonad/Base.fm/blob/42fac6a19ae87dd46adf9176531118ceb2967948/String.fm
My solution to the transmit.fm bug is here: https://gist.github.com/johnchandlerburnham/efeccd2c038ce975813e34c9ca46777d

I played around with @johnchandlerburnham gist. I had to change the imports. It worked for me with Formality-Lang v0.1.252
My updated gist is here
Thank you.

Yeah, looks like you used my solution gist. The original bug was with
encodeChar(x : Char) : Bits -> Bits
  let x = x >>> 0
  if x === 0 then b0
  else
    if (x % 2) === 0
    then (y) => b0(encodeChar(x \ 2)(y))
    else (y) => b1(encodeChar(x \ 2)(y))

This needed the bits to be padded in groups of 8 so the correct version is
encodeChar(len : Number, x : Number) : Bits -> Bits
  let x = x >>> 0
  if x === 0 then
    if len > 1 then (y) => b0(encodeChar(len - 1, x)(y))
    else b0
  else
    if (x % 2) === 0
    then (y) => b0(encodeChar(len - 1, x \ 2)(y))
    else (y) => b1(encodeChar(len - 1, x \ 2)(y))

Formality was refactored, we're making a new documentation!


Interacting with a toolbar item  triggers updates for all the other items

🐛 Bug report
Current behavior
Interacting with a toolbar item or menu item (also inside toolbar) triggers updates for all the other items.
Steps to reproduce the bug

Open sandbox: https://codesandbox.io/s/reakit-menu-with-tooltip-4wbml?from-embed
Remove any line
See console logs

Expected behavior
I'll expect to just update the button that the user is interacting.
Since the api requires to pass useToolbarState and useMenuState to all items I guess this is expected if is tracking the last focused element, current focused element, values etc...
So I'm not sure if this is a real issue or the intended / expected behavior :confused:
Environment
Please, run the command below inside your project directory.
$ npx envinfo --system --binaries --browsers --npmPackages "{react*,reakit*}"

Environment:
  OS:  Linux 4.15
  Node:  10.15.3
  Yarn:  1.19.1
  npm:  6.12.0
  Watchman:  Not Found
  Xcode:  N/A
  Android Studio:  Not Found

Thanks for opening the issue! That's the intended behavior, but maybe we can trigger updates only on the relevant components (the one that is losing focus and the one that is receiving focus).
But I'm not sure if the added check would be faster than just rendering the component. We need some automated performance test. Related to #429


Restructuring the current project architecture

Currently, we have all the files in the major folder i.e. securetea folder itself.
A better way to organize would to be group the commons in a separate folder.
For example, the following structure:
securetea/
    |__lib/
          |__notif/
                |__ __init__.py
                |__secureTeaTwitter.py
                |__secureTeaTwilio.py
                |__secureTeaTelegram.py
                |__secureTeaSlack.py
   |__args/
         |__arguments.py
         |__args_helper.py
  |__ __init__.py
  |__common.py
  |__core.py
  |__logger.py
  |__configurations.py

As per the roadmap, other features like Firewall, IDS, Intelligent Log Montioring, AntiVirus can all be added to the securetea/lib folder, by creating respective folders.
If yes, I would like to work on this.

@rejahrehim Any thoughts on this? Shall this be worked upon?

@abhisharma404 You can work on this


Fix Visual Studio 2017 Compilation on v2.0.9

Thanks so much! Wish I had seen this earlier but it has been fixed in the meantime; it is the strangest thing that this works. :-)


remove default test from test list

so garbled test commands don't accidentally trigger actual tests. Should not affect the tests that automatically run upon making a pull request

The bot should react to the post with a :confused: . I'm trying to find an example in old PRs.


Guard against spaces being null in recent-apps component

@irfanhabib I tweaked this to cover the core issue, if it looks good to you we can merge

LGTM


a bit unrelated but can someone provide creative solution to this?

i'm trying to break down the header and body and method from
ctx *app.RequestContext
so that i can transfer by other protocol instead of http which is a bit more heavy than... redis or grpc etc.
does anyone know how i can distill down the ctx of method, header and body and transfer over the wire with grpc BUT not the whole http header stuff?
e.g. "Content-Method" : GET <- this i would like to transfer as GET in int16 (2 bytes)
is there a way to make all these information reduced and NOT be in http header etc? coz http header overhead is high.
anyone has any creative solution? to transfer http header through grpc or redis pub/sub
is this all or is there more?
https://www.aisangam.com/blog/wp-content/uploads/2019/10/HTTPRequestMessageFormat.png

you can use break point to debug and read some document about hertz
，i  think use break point to debug is a good idea.


Ng-repeat with search filter brings back the items from other div or "first:bag"

 Search by Outward Code: <input type="text" ng-model="search.Name">

{{owc.Name}} {{owc.Country}}

Make sure to check out the documentation on GitHub!

When I drag an element from ng-repeat dive to the below bag and search again it fetches the records from that div back into ng-repeat div.

Yes and I would say it´s right.
With the change of the filter the ng-repeat will be rerendered. With that code snippet you aren´t changing the outWardCodes Array by drag&drop.
What I think you want is the dragula-model synchronisation
Search by Outward Code: <input type="text" ng-model="search">

{{owc}}

Make sure to check out the documentation on GitHub!

Have a look to this plnkr where I ve corrected your snippet: http://plnkr.co/edit/bKNeo9cyKyjY3GpJcIhY?p=preview
Greetings, Daniel

Again thanks. It works like a charm. :+1:

Currently you cannot drag item while the list is filtered. dragula becomes confused with the array index.
In the plunker example you can try to search for "t" and then drag and drop "them" from list. You will notice, that "Explore" will be moved instead.

+1

+1
Any help would be appreciated


WIP: Remove main-free.css which is not actually shipped in dist

remove non packed main.css from throwing errors when using custom admin pages.

Description

Related Issues

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add new "tunnel backer ports" patch to OVS image

We backport this patch to OVS 2.13.0:
https://github.com/openvswitch/ovs/commit/7cc77b301f80a63cd4893198d82be0eef303f731
It reduces down time for inter-Node traffic (overlay mode) when the
Agent Pod is restarted, by ensuring that the tunnel ports don't get
deleted on exit.

/test-e2e

/test-e2e


ESP-IDF installation is too convoluted (IDFGH-11746)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.3-dev-1043-g8c9e29898f
Operating System used.
macOS
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
What is the expected behavior?
Ideally, there should be a single folder on my system containing all things related to espressif. If IDF is a product, it should be a subfolder within it. It would be nice if .espessif folder wasn't hidden so it's easier to find by the user if needed.
What is the actual behavior?
Installing IDF creates two interelated directories on my system, ~/esp/esp-idf and ~/.espressif. The first is an actual git repo, whereas the second one isn't. It's unclear why there's a separation between the two installed folders. Both folders contain a tools subdirectory with different types of functions. From the looks of it, it appears the repo is intended to setup the environment.
Steps to reproduce.

Step
Step
Step
...

Build or installation Logs.
No response
More Information.
No response

Hi @Joebeazelman,
We made an attempt to explain the purpose of the .espressif directory in this section of the programming guide: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/tools/idf-tools.html
The separation between the two directories — the git repo itself and the "downloadable tools" directory is intentional. Downloadable tools (toolchains, debugging tolls) are typically large archives which are not well suited for being stored in git. At the same time, they change less often than IDF does. It is often possible to use the same version of the tool in multiple versions of IDF, so such a separate tools directory also serves the purpose of not storing multiple copies of the same toolchain even if you have multiple copies of IDF.
Anyway, if you prefer to keep all Espressif-related folders under the same directory, you can. If IDF_TOOLS_PATH environment variable is set, IDF installation scripts will store downloadable tools under that directory, rather than in ~/.espressif. You can set IDF_TOOLS_PATH globally (in your she'll profile script, for example) to the desired location.


Simple Sidre Examples

Summary
Adds some simple Sidre examples in response to a user request.
Resolves #188

Thanks for adding these examples @gzagaris.
Please update your sidre_read function for the external data as described in my comment.

Done.


Patch app issue

When I try and patch Gorilla tag mod I'm getting this message.  Any idea what is wrong?  Also, why does it mention beat saber?

You've enabled the "Disable VR Requirement" option. That option is only intended to work with Beat Saber installations.


keep original image size in preview.

Hi, ran across this and trying it out. Thanks!
Using it for one image to test,
If I choose a small image height x width the preview displays/fills the entire preview area. This could make it blurry.
I may find this, but thought I'd give a quick ask,
Is there a way to keep the original image size in the preview area? Get the original image dimensions?
Thanks much! Appreciate it.
Didn't see this in the notes.
Best,

Hi there - thanks for checking out the project.
I see what you're saying about not forcing an image that's smaller than the image preview pane to stretch to fill it.
Luckily I think the fix for this should be pretty simple. The image is stretching because of the background-size: cover; property set on the .custom-file-container__image-preview. How about you add the following code to your stylesheet so it overwrites the repo's style.
.custom-file-container__image-preview {
  background-size: contain;

  /* You may want to add this too because the background of the image-preview container is set to a white color. */
  background-color: #eee;
}

Try that and let me know how it goes.

Hi, much thanks for the note back. Welcome!
background-size: contain; will scale the uploaded image preview up so that each side is as large as possible while not exceeding the length of the corresponding side of the container. So if you are using this for one image and the container is 400px by 400px; Then the image will be scaled to that as well. Or if 200px by 300px then the image will be scaled to 200px by 200px. If the image is smaller than the container's smallest bounding side, it's likely to still scale up/blurry to fill to the length of that side.
The preview pane for use with one image would either need to shrink to fit the image size or the image would need to ignore the container size if the container size is fixed. And be centered.
Optimally a preview image for use with one uploaded image would be the size of the original image/keep it's dimensions unless larger than the container. Note: this isn't a problem with multiple files but only when using it on the single image upload. As the multiple creates really small preview images already.
But when using it for the one image upload/preview and using either background-size: cover; or background-size: contain; will still scale a smaller image size up to the preview container size/blurry/lose it's original size.
Anywho looks promising but we've gone in another direction, with something created in house.
Best,
-C

Hey yea I definitely hear what you're saying. In the future we'll take a look at keeping the smaller images at their uploaded size. Thanks for the feedback and good luck!

You as well! Fun project. Always good to see people working in the community and sharing. Best, -C


Suggestion support for specific version manager files

I have looked around in the docs but I have not found any mentions of this, but it would be a nice to add support for version managers files
Examples:

.nvmrc docs | code
.python-version

vfox has its own version management file, .tool-versions. It is the same as and compatible with asdf.

vfox will create a .tool-versions file to record SDK version you use when use vfox use -p <sdk-name> command.

I did read that on the docs!
I just meant it would be a cool opt-in feature, as per the projects that use those files would remain "less" compatible with vfox

I did read that on the docs! I just meant it would be a cool opt-in feature, as per the projects that use those files would remain "less" compatible with vfox

Ok, I get what you meant now. To accomplish this, we need to add a new hook for the plugin, which is called when using the vfox use command.

That would be brilliant!

I did read that on the docs! I just meant it would be a cool opt-in feature, as per the projects that use those files would remain "less" compatible with vfox

Ok, I get what you meant now. To accomplish this, we need to add a new hook for the plugin, which is called when using the vfox use command.

This would be great! Can we expect that .node-version also will be supported?
PS: I just discovered this package, and I am already in love with it!

I did read that on the docs! I just meant it would be a cool opt-in feature, as per the projects that use those files would remain "less" compatible with vfox

Ok, I get what you meant now. To accomplish this, we need to add a new hook for the plugin, which is called when using the vfox use command.

This would be great! Can we expect that .node-version also will be supported?

If .nvmrc is OK, then .node-version is totally OK! But it's just a work in progress.

PS: I just discovered this package, and I am already in love with it!

Thanks!


Test to make sure that everything renders in doc_safer.py

Well, we have a unit test for this, so I'm going to close it.


Test against rails 7.1

I.... don't know why CI is failing this way only on 7.1, it looks like the db reset isn't creating tables?

Hey, @segiddins! I spent some time digging into the CI failures with some co-workers. The solution is not totally nailed down yet, but we're on the right track. It appears there may be an issue with how the table(s) are being created. Like you noticed, dummy:db:reset isn't doing what it should be doing. When we ran the commands separately, dummy:db:drop dummy:db:create dummy:db:migrate, we had more success.
There's still some issue with the migration generation, but again, feeling like the solution is on its way.
Hope to unblock you within the next week. :)

@segiddins I need to clean up my own PR's commit message and all before I merge it (https://github.com/thoughtbot/clearance/pull/998) but I've rebased your changes on top here so now we can see those pretty pretty green lights.

Amazing, thanks so much for the help @sej3506! Super excited to get this into RubyGems.org

@sej3506 i think you might've force-pushed over my last commit or two

@segiddins I sincerely apologize. I definitely should not have been force pushing (especially on someone else's branch). If you have the commits locally still, you can add them to the branch using this method.
If you do not have them locally anymore, I can add them back manually using the information here and here.

All good! I added it back

@sej3506 I think this should be ready to merge & release whenever y'all are ready!

if it's not too much of a hassle, a release with this would be :100: 🙇🏻♂

@sej3506 anything I can help with to get release done?

@segiddins @simi Sorry for the delay on this release. It's out now!


Collections Filters Visual QA Fixes

Collections Filters Visual QA Fixes

Adds a border in the filter modals to indicate separation between list row items and the modal header
Adds a top border to the apply button to indicate separation between Apply button and list row items
Removes "double" border between list row items
Increases the tappable area for the close and back icons with hitSlop property

#trivial

:ceiling-cat: the fixed height looks a little too high, which is to say that the title + back button are no longer appear vertically centred.
Also, unrelated to this PR, but I just noticed that the borders on the filter list items are duplicated, so they're slightly too thick wherever two list items meet.

It seems like these changes fix the issues-- but it does seem like a lot of custom CSS. Would it be possible to use StackableBorderBox (from palette) here to fix the border issues?

It throws some compile errors and I'm not sure why, posted in the MX channel to see if there's a known issue with it. I don't see any uses of it in the app when I search for it, so not sure if that is because devs aren't aware of it or if there's some other underlying issue.

It seems like these changes fix the issues-- but it does seem like a lot of custom CSS. Would it be possible to use StackableBorderBox (from palette) here to fix the border issues?

It throws some compile errors and I'm not sure why, posted in the MX channel to see if there's a known issue with it. I don't see any uses of it in the app when I search for it, so not sure if that is because devs aren't aware of it or if there's some other underlying issue.

MX just followed up, the TLDR is that it doesn't work because it uses CSS pseudo-selectors under the hood! https://artsy.slack.com/archives/CN8S32FJR/p1588186364077400


Not Saving Stacks

Hi,
I may have done this wrong. On a 12.3.1 mac and launched WyldCard with gradle run. <- There are no instructions on how to actually build.
One it was running, all was amazing, and although it looked like I could save, it didn't, and wouldn't quit.
Amazing work btw!

Hi,
I may have done this wrong. On a 12.3.1 mac and launched WyldCard with gradle run. <- There are no instructions on how to actually build.
One it was running, all was amazing, and although it looked like I could save, it didn't, and wouldn't quit.
Amazing work btw!

Hi @everythingability, glad you had a successful run.
As far as building information, you can find it herehttps://github.com/defano/wyldcard/blob/master/doc/BUILDING.md.
It appears to be a bug with the default stack.  A workaround until it is fixed, is to do a "Save Stack As..." and then reopen the stack when you launch again. It will always open the default in-memory stack, and there is currently no concept of a Home stack or "previous" stack.
@defano has done an amazing work, indeed!
Hope this helps,
Carl, WyldCard contributor

@ooper-zz When I mentioned the build instructions, what I meant was at no point does it say... type...
> gradle build
> gradle run

I've only got glancing experience of Java (coding in Processing) so I had to Google how to get it running... I did but many might not. You've probably woken a few nostalgic old farts like me who haven't used Gradle :-)
One of the best/weirdest features of HyperCard that you never had to save anything. Any chance of that? Maybe as an option - but it really was an amazing feature.

I see. Glad to see you figured it out. As for the auto-save, I agree.  Saving a stack was one of the features that made Hypercard stand out from the crowd, albeit not your standard document-based applications.  We can technically do it in Java, as there are plenty of time-tested options for caching, but I will let @defano chime in on his take from a roadmap and priority perspective.


There are no commands defined in the "propel" namespace.

I have installed it using this command: composer require willdurand/propel-typehintable-behavior
After running php bin/console propel:build
I get this error:
[Symfony\Component\Console\Exception\CommandNotFoundException]
There are no commands defined in the "propel" namespace.

What can I do about it?

I have same problem

I Also have it. No answer yet

Are you sure you need propel? I guess you are using Doctrine.

:-( same issue for me

I have done something different I think, I don't remember if I have solved it. But maybe someone will help for others which have this problem.


SiloLinearPoolFactory address update

Description
Updated the address and start block for the SiloLinearPoolFactory
Type of change

[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 not work as expected)
[ ] Dependency changes
[ ] Code refactor / cleanup
[ ] Documentation or wording changes
[ ] Other

Checklist:

[x] I have performed a self-review of my own code
[x] I have requested at least 1 review (If the PR is significant enough, use best judgement here)
[x] I have commented my code where relevant, particularly in hard-to-understand areas

dev -> master

[ ] I have checked that all beta deployments have synced
[ ] I have checked that the earliest block in the polygon pruned deployment is block, date/time

[ ] The earliest block is more than 24 hours old

[ ] I have checked that core metrics are the same in the beta and production deployments

Merges to dev

[ ] I have checked that the graft base is not a pruned deployment

As discussed at Rabico today, putting this on hold until new create2 factories are deployed


Add walk flag or improve the enter-claim one

I would like a method to COMPLETELY deny entry to a claim. Many mods does teleporting in some hacky ways that aren't blocked by GP right now, because it acts like a barrier instead a blocker. Would be nice if GP checks for walking over a claim instead only check when you're entering it, so if the person is already there, he would be teleported to the border of a claim, just like GriefPreventionPlus does.

What about the teleport related flags? I know Blood was going to do something related to ./home teleporting you to a border, rather than a point inside the claim if you aren't trusted. Might be possible to use the same system here


npm install now fails on windows

verbose installOne cb<EMAIL_ADDRESS>ERR<EMAIL_ADDRESS>install: make
ERR! cmd "/c" "make" failed with 1
ERR!
ERR! Failed at the<EMAIL_ADDRESS>install script.
ERR! This is most likely a problem with the node-proxy package,
ERR! not with npm itself.
ERR! Tell the author that this fails on your system:
ERR!     make
ERR! You can get their info via:
ERR!     npm owner ls node-proxy
ERR! There is likely additional logging output above.
ERR!
ERR! System Windows_NT 5.1.2600
ERR! command "C:\node\\node.exe" "C:\node\node_modules\npm\bin\npm-cli.js" "install" "now"
ERR! cwd C:\node
ERR! node -v v0.6.1
ERR! npm -v 1.0.105
ERR! code ELIFECYCLE
verbose exit [ 1, true ]

Please read the error message.
ERR! Failed at the<EMAIL_ADDRESS>install script.
ERR! This is most likely a problem with the node-proxy package,
ERR! not with npm itself.


cfturnstile component does not exist

In your README you describe how to use the cfturnstile.
<cfturnstile
      :sitekey="sitekey"
      @verify="verify"
    />

However, this compoment is not what you are importing. Did you mean Turnstile?

You are correct, this is a typo and <cfturnstile> is a typo. Will fix later.


Help with logging

I am trying to get started with logging and making no progress.  What am I missing? I am new to logging, and am going by examples that I have found. Code below. Comment shows error
#r "sdk:Microsoft.NET.Sdk.Web"

#r "nuget: Microsoft.Extensions.Logging, 7.0.0"
#r "nuget: Microsoft.Extensions.Logging.Console, 7.0.0"

using Microsoft.AspNetCore.Builder;
using Microsoft.Extensions.Logging;

var app = WebApplication.Create();

Log.Logger = new LoggerConfiguration()
    .MinimumLevel.Debug()
    .WriteTo.File("logs.txt", rollingInterval: RollingInterval.Day)
    .CreateLogger();

// compile error: The name 'Log' does not exist in the current context

app.MapGet("/", () => "Hello world");

app.Run("http://localhost:5178");

Answering my own question. It's a Serilog thing, and adding a reference to Serilog fixed it


Implement permessage-deflate extension

Might not be the best implementation..

I have processed only Binary, Text and Continuation frames in incoming frames
Processed all the outgoing frames

Using websocket-extensions is gonna make it easier to hook any extension in here!
I have tested it against a permessage-deflate server.

I would want to see this load tested (very high load like 32k clients per server) if at all possible.  About 12 months ago we tried to run perMessageDeflate using the ws module but it tanked the server side performance.  We decided not to pursue pmd as we couldn't get the cpu resource usage under control with a very busy server.  We run msgpack over binary frames which gives us typically about a 20-30% reduction in ota bandwidth with little or no client/server performance hit


There is no way to tell pkg_tar to not change mtime of the packaged files.

When pkg_tar mtime attribute is not set (or set to its default value -1) I expected the packaged files to retain their original mtime within the archive. Unfortunately it looks like their mtime is set to Jan 1st 1970 (or Jan 1st 2000 depending on portable_mtime attribute). I could not find a way to make pkg_tar to preserve the files mtime.

Strawman proposal:

pkg_tar should no long auto-unfurl tarballs, and we will not implement a change for that legacy behavior
add pkg_unfurl which takes tar or zip srcs and returns a provider that specifes the unwrapping of each, with options to

strip_prefix
add a new prefix
change owners
preserve mtimes
the other kinds of stuff that pkg_files might do.

Or maybe it just does the virtual unfurl with ability to preserve mtimes and then pkg_files will to do the rest.

I'm sorry, what is auto-unfurl tarballs? You do what with what?

Note from eng meeting. This is probably a dup of the pkg_expand issue.


Send mobile version to unleash so we can filter users on a specific version

Related to https://github.com/HathorNetwork/hathor-wallet-mobile/issues/404

Fixed in https://github.com/HathorNetwork/hathor-wallet-mobile/pull/417


Workbench Integration

This PR introduces Workbench Integration where you can preview a demo Nova application directly inside your package using composer run serve.

Hi @crynobone
Thank you! 🚀

Hi @crynobone
I just noticed that the serve composer script timeout after 300 seconds, which is the composer's default process timeout.
The Orchestra\Testbench\Foundation\Console\ServeCommand may disable the process timeout if composer/composer is installed.
if (
    class_exists(ComposerConfig::class, false)
    && method_exists(ComposerConfig::class, 'disableProcessTimeout') // @phpstan-ignore-line
) {
    ComposerConfig::disableProcessTimeout();
}

We may disable the process timeout directly in the scripts section as described in the composer config documentation
{
  "scripts": {
    "post-autoload-dump": [
      "@prepare",
      "@dusk:install-chromedriver"
    ],
    "clear": "@php vendor/bin/testbench package:purge-skeleton --ansi",
    "prepare": "@php vendor/bin/testbench package:discover --ansi",
    "dusk:install-chromedriver": "@php vendor/bin/dusk-updater detect --auto-update --ansi",
    "build": "@php vendor/bin/testbench workbench:build --ansi",
    "serve": [
+    "Composer\\Config::disableProcessTimeout",
      "@build",
      "@php vendor/bin/testbench serve"
    ]
}

https://github.com/orchestral/testbench-core/blob/8.x/src/Foundation/Console/ServeCommand.php#L23-L28


FILE UPLOAD ISSUE

Hi,
I am using this project in my current healthcare exchange, everything is working fine except I am facing issue when I add File Upload functionality. I am getting following error. Please guys help me out to resolve this critical problem.
{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"diagnostics": "Unsupported Media Type"
}
]
}

I need more information regarding how you do file upload. POSTing Binaries to Spark has been tested and should work.

Hi,
Thank you for your prompt response.I am using the latest of Spark version 1.5.14 and .Net core version 6.0
I have a simple controller to upload files using the [FromForm] attribute as shown below.
[HttpPost, DisableRequestSizeLimit]
        public async Task<ApiResponse> UploadFile
( [FromForm] IFormFile formFile )
        {

            // Removed my code
            return null;

        }
Postman CURL script to use this method is.
curl --location --request POST 'https://localhost:44364/api/Document'
--header 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJqdGkiOiI1NzYzZWQyYjQ0MGI0OTk4OWJlNGY1NjQyNGVkYzFlYiIsImh0dHA6Ly9zY2hlbWFzLnhtbHNvYXAub3JnL3dzLzIwMDUvMDUvaWRlbnRpdHkvY2xhaW1zL25hbWUiOiJqYW1pbGFrMjJAeWFob28uY29tIiwiZXhwIjoxODIyNzE3NzA5LCJpc3MiOiJYZWxsZSIsImF1ZCI6IlhlbGxlIn0.acSOpS1LHJSzgFxJXoQBnYAMicLSsNzWJZQBLeKR4s4'
--header 'Content-Type: multipart/form-data'
--form 'File=@"/F:/DCIM/105APPLE/IMG_5008.JPG"'
--form 'CreatedBy="9b12d575-a29a-436d-8677-c88997327a4f"'
--form 'DocumentType="Workbook"'
but when I submit the form I am getting an unsupported media type error.
I hope you got my issue, please help me out.
Thanks

The code you are sharing do not have any relevance to FHIR APIs so I suspect there is some lack of understanding on how to interact with FHIR APIs
You can try the following curl command against my official test server. Create a text file called test.txt with some random content and run the following command:
curl --request POST --data-binary<EMAIL_ADDRESS>https://spark.incendi.no/fhir/Binary

I recommend that you take a look at the examples I've put up, like this one: https://github.com/incendilabs/spark-example

Hi,
Thank you again for the prompt response. Well I know there is a Binary resource where we can store all sorts of documents in binary format which is perfectly fine and it is working at my end as well, I don't have issues with it.
My client wanted to store all their documents in Mongo GridFS, For that purpose I created a separate controller to store and retrieve Documents in GridFS.
For more information I can share my complete project so you would have a clear understanding of my problem and it would help you help me out to resolve this issue.
Here is the complete project, please fill the MongoDB connection string inside appsettings.json.
https://github.com/lumisoftllc/MongoFhir
Below is the curl script to upload files in GridFS.
curl --location --request POST 'https://localhost:44364/api/Document'
--form 'File=@"/F:/DCIM/105APPLE/IMG_5008.JPG"'
--form 'CreatedBy="9b12d575-a29a-436d-8677-c88997327a4f"'
--form 'DocumentType="Workbook"'
Thanks

Hi,
Please guys I am wailing for the response.

We are overriding the formatters in the MVC pipeline which then interferes with your API at api/Document. The easiest way to get this to work is to move your DocumentController into a separate project. Then you will have one endpoint (project 1) which is pure FHIR APIs and another endpoint (project 2) where you can add your own APIs like the DocumentController API.

Hi!
Thank you so much for the prompt response.
Well my task is to use the same end point for both Fhir and other custom controllers.
Anyhow I have achieved this behavior by sending the files in base64 and then converting into stream and store in GridFS.
Despite that, I appreciate your team for working on this amazing project.

Thanks for saying that @LumiProj, that's appreciated


Generating background-color utilities doesn't output the correct value (CSS variable ignored)

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
The documentation says the following:
@import "bootstrap/scss/functions";
@import "bootstrap/scss/variables";
@import "bootstrap/scss/maps";
@import "bootstrap/scss/mixins";
@import "bootstrap/scss/utilities";

$all-colors: map-merge-multiple($blues);

$utilities: map-merge(
  $utilities,
  (
    "background-color": map-merge(
      map-get($utilities, "background-color"),
      (
        values: map-merge(
          map-get(map-get($utilities, "background-color"), "values"),
          (
            $all-colors
          ),
        ),
      ),
    ),
  )
);

@import "bootstrap/scss/utilities/api";

Output is:
.bg-blue-100 {
  --bs-bg-opacity: 1;
  background-color: #cfe2ff !important;
}

But expected output should really be:
.bg-blue-100 {
  --bs-bg-opacity: 1;
  background-color: rgba(var(--bs-blue-100-rgb), var(--bs-bg-opacity)) !important;
}

This is an issue because when doing this, it doesn't work, opacity isn't taken into account.

What am I missing here?
Reduced test cases
I haven't been able to set up a Codepen for this but will try to provide a dedicated repo as soon as possible.
What operating system(s) are you seeing the problem on?
macOS
What browser(s) are you seeing the problem on?
Chrome, Firefox
What version of Bootstrap are you using?
v5.2.2

For those, you'll need to use the right functions that we use ourselves to convert the hex values to red, green, blue so we can consume them in a CSS variable. For example, from _maps.scss using rgba-css-var() in map-loop():
$utilities-bg: map-merge(
  $utilities-colors,
  (
    "black": to-rgb($black),
    "white": to-rgb($white),
    "body": to-rgb($body-bg)
  )
) !default;
$utilities-bg-colors: map-loop($utilities-bg, rgba-css-var, "$key", "bg") !default;


GH-CLI: migrate-repo command with the source in GH

Need to include support for different PAT for source and target


Block diagram: make feature text readable

White text on the dark red should be more readable than the black.

@nbdd0121 let me know what that readability tool is you were talking about. Hopefully this will resolve it.

https://webaim.org/resources/contrastchecker/


Update php version constraint

We wont know if the package will break in the future. This way we can get ahead by allowing specific versions of PHP.

@tobscure the tests pass. Only Scrutinizer which can't find the travis output.

:+1:

This shouldn't be done in a patch release, because composer will just resolve the patch release one before this one for other php versions...


JSON decoding is very slow

After updating the perf harness to measure JSON encoding and decoding, I found some troubling results. Run 100 times for a message with 100 int32 fields:
"Encode JSON" took 0.025 sec
"Populate message fields" took 0.000 sec
"Encode binary" took 0.004 sec
"Decode JSON" took 12.800 sec
"Test equality" took 0.000 sec
"Decode binary" took 0.009 sec
----
Total execution time: 12.840 sec

A glance at the call trace shows that we're spending most of that time in ProtobufJSONScanner.next(), with much of that time being charged to Character.init(_builtinExtendedGraphemeCluster:utf8CodeUnit:isASCII).
I spent the past couple hours digging into the scanner and came up with the following results:

Initializing Character values seems to be expensive, especially in tight loops. There are probably penalties there from all the details of Unicode correctness that that type provides. By working with the string's unicodeScalars view instead, I was able to get rid of a significant amount of overhead, without sacrificing correctness.
Building up strings character-by-character (or even scalar-by-scalar) is also expensive. Instead of using iterators and appending, I maintain indices that I advance and take slices, which can be converted back to strings as a contiguous unit much more cheaply.

The result: JSON decoding of 100 messages with 100 int32 fields went down from 12.8 sec to 0.023 ms—a roughly 550x improvement.
I finessed some of the edge cases that weren't being exercised by the perf harness (I didn't worry about Unicode escape sequences, surrogates, and such) so that I could focus on speeding up the common cases, but putting those edge cases back shouldn't penalize those common cases too much. I also focused solely on the scanner side of things; there may be gains within the parser itself that I haven't explored yet, as well.
I'll keep working on this and get a PR out in the next few days, hopefully.

We should probably double check the string processing within the plugin also to see if there are easy speed up there also.

Great!  I have been meaning to dig into this myself.  I had also thought about working directly with the UTF8 bytes and doing a conversion to/from String at the boundaries.


Wierd differential behaviour with any non-4WD configuration.

When setting up a car, eDIFF_TYPE_LS_4WD works fine but any other, such as eDIFF_TYPE_LS_REARWD, seems to spin the rear wheels but the front ones are "braking" and wont rotate, even though I'm not applying any braking or handbrake input. This makes the car unable to move. I don't know if this is something I'm doing wrong, or a bug. Any clues? Thanks.

Hmm I tried other diff modes with my vehicle demo and they seem to work fine, so my guess is you are doing something wrong.
I do my vehicle setup here: Vehicle.kt, diff mode is set in line 183. It's kotlin not Java but maybe it helps.

Thanks for checking, Yes I am following your kotlin vehicle already, I guess I'll try again to find what I'm doing differently.

I found and fixed my problem, here it is for others who might try to do something similar to me.
At first, before I even added the vehicle part, I did rigidbody.setMass() to apply 1600kg to my car, but this caused it to glitch around badly, falling though the ground etc. So I just used a mass of 1 instead, which worked, because I thought mass is relative and I could just tweak the vehicle forces to make it behave the same. So somehow this didn't work well for physX internally, because the wheel's MOI was too big for the rear wheels to even turn the front wheels, and if set lower the front wheels would just slide. I'm guessing there's either some more parameters I didn't adjust for this 1kg car, or physX has some internal ones I can't change. Either way what I did to fix it was to use PxRigidBodyExt.setMassAndUpdateInertia(rigidbody,1600), after applying the shapes to the car, and now it works great.

Ah I think the inertia was your problem. As a tip: You should always set an inertia appropriate to mass (e.g. by using PxRigidBodyExt.setMassAndUpdateInertia(body, mass) you already mentioned). Without correct inertia, bodies will glitch heavily (not only vehicles, but all kinds of bodies).

Well my car seems to behave normally now, except the wheel friction which seems like it's on ice. I tried adjusting so many values to high amounts and nothing seems to work. I changed the surface material friction, the friction pair setTypePairFriction multiplier, setMLatStiffX and Y for the car tires, and they don't seem to make any change. I'm at a loss for where to look next.


preallocate slice

A further optimization to #228 by preallocating the required memory since it's known.
E2E tests in GM passing here, https://github.com/solo-io/gloo-mesh/pull/1418

/skip-changelog

/skip-changelog


Vulkan SDK release feature cut-off Friday May 19

LunarG is planning the next Vulkan SDK release.
A MoltenVK SDK release for this Vulkan SDK will be made Monday May 22.
MoltenVK PRs approved by Friday May 19 will be included in this release.
@cdavis5e @spnda @richard-lunarg @KarenGhavam-lunarG

MoltenVK version 1.2.4 released for Vulkan SDK 1.3.250.


Gigabit Speed test issue

Grafana shows a speed of about 600 Mb/s, which is far below my internet speed. When I run the speedtest from the Pi directly with the CLI from speedtest.net I get the promised ~1000 Mb/s. Where does the difference come from since both were done from the same device?
With the speedtest I did, it took a bit until the maximum speed was reached. Maybe that is the problem?

The problem is the Speedtest itself, you can read about it... I have the same problems..... It can't handle gigabit connection.

Maybe PR#475 can fix that?

I have tried it with Cloudflare as in PR#495, but it doesn't get any better. The error is probably not due to the speedtest, but rather to Docker or Prometheus.

Maybe check this out: https://ubidots.com/community/t/speedtest-cli-with-raspberry-pi-4-and-ubidots-for-gigabit-internet-testing/3044

I use https://pimylifeup.com/raspberry-pi-internet-speed-monitor/ with influxdb for the speedtest and let the rest of the functions continue to run via the docker container with prometheus.
This is how it works now and shows the correct values.

Are the results in the dashboard?

I mean the same dashboard of internet-pi

Yes, I connected Grafana from the internet-pi to influxdb and adjusted the dashboard. The data is now displayed on the internet-pi Grafana dashboard.

Great, I'll try to replicate it 😁

Confirmed working


RFE: change indication/mail rule/X-header

First - thanks, this is awesome.
Secondly - a small RFE... the little X that shows things is really indistinct... having even an option to make it pop more (say, changing color to red, yellow, whatever) would be really useful.
Even more greatness would be the ability to run a rule (as in preferences->rules) that would allow basically arbitrary actions (color, junk it, whatever)... I haven't looked into your code to see the magic under the hood, so not sure how possible that is (or even changing the color above, vis a vis mail APIs and such.)
Anyway, thanks again!

Just reread the description... putting in an X-header would be awesome, since you already strip content out.

Thanks for your input!

a small RFE... the little X that shows things is really indistinct

The ⓧ icon was intended to be quite subtle as to not look out of place with the rest of the Mail app using blues and greys (see #2 CC: @bitmanic). As an aside, I'm thinking about change the icon to maybe 👁 in line with similar extensions I've seen.

the ability to run a rule (as in preferences->rules) that would allow basically arbitrary actions (color, junk it, whatever)

What percentage of your emails don't show the blue or grey ⓧ icon? The issue with email nowadays is that nearly every single email includes some sort of tracker. I imagine the end result being that your rules would trigger and the majority of your emails end up coloured or in the junk. So I'm not sure if this would be a helpful feature.

putting in an X-header would be awesome, since you already strip content out.

This makes sense. I'll see if I can get around to this, thanks!

X-header would rock, thanks for the consideration.
As for what percent... well, what percent from friends (hopefully not much :)), from work (again!), from random folks... well, who knows.  From retailers and such, sure.  But to me it's not about the high-percent that have them, which is somewhat akin to asking what % is spam - 99%+?  But Of the ones that manage to get through your defenses... I'd personally love to be able to mark or flag any and all that have this if I wish.    For the amazons/etc of the world, sure, that's noise.
I've been aware of this forever, but am interested in seeing how pervasive it is in places where I wouldn't normally expect it... for instance, the alert from github on your response - "MailTrackerBlocker blocked a tracker from GitHub."  What?!?  I may be naive, but I didn't expect it.  And really, I didn't even see the alert until I went back while writing this.  A fine line between informative and invisible, or something like that.
You say (probably correctly) that most mail does have them... but it does seem that having control of how to present that to the end consumer is critical to better understanding.  Yes, you don't want to simply wash out everything in a big red smear.
But... wait a second... don't tell me.... Brutus, et tu?

Definitely. Trackers are definitely way more pervasive than I think a lot of people realize and moreover, just as easy for for everyone and their neighbour to implement. @dhh (who inspired this project) has been in the spotlight a lot over this very issue. I've had coworkers send me emails with trackers too. It's unbelievable. And so MailTrackerBlocker operates on this very premise of trackers being so prevalent that as you said, after the 10th email, any sort of flashy or overbearing UI indicator would end up being noise.
But I've been considering minor changes to the indicator. Perhaps something along the lines of Ugly Email where they have a 👁 icon on the Conversation List if a tracker is detected.

Your other points noted though for having options. Maybe I'll see if I can hook into the Rules with an extra condition for something like "Message has tracker". A summary/stats page like you said might be interesting too.

)

Yeah - great ideas, @zenfish!
@apparition47: if you would like me to generate any new assets related to this work, please let me know. I'm definitely interested in mocking up some summary/stat page concepts if and when you're ready to tackle that feature.

I'll second/third/fourth/whatever the request for an X-header.  I have filters that run in the delivery pipeline that do this.  It makes writing rules (without mucking with Mail to add new rules conditions).

I'll second/third/fourth/whatever the request for an X-header. I have filters that run in the delivery pipeline that do this (I operate my own mail server). It makes writing rules (without mucking with Mail to add new rules conditions) really easy.

Please see leggett/simplify-trackers/ruby.  I implemented a simple ruby filter that does exactly this.  See the README.md.

rules engine be packaged as a separate component

@caponecicero I like this idea. For your Ruby filter program, what does the email input/format look like? e.g. something standard like the eml files that come out of Mail with the headers and body?

You write:

@caponecicero I like this idea. For your Ruby filter program, what does the email input/format look like? e.g. something standard like the eml files that come out of Mail with the headers and body?

That's exactly right...  The input/output format is a mail message.  I put it into my delivery pipeline today to read the email from STDN, modify it in-place if necessary, and write the (possibly-modified) email to STDOUT (that's what sieve requires of filters).  If the message has trackers, they are all removed and a header called X-Blocked-Trackers is added to the message with a list of the names of the trackers that were blocked.


Per-entry permission verification

Per-entry permissioning currently is not planned for OrbitDB. But we might be able to accomplish it, using the capabilities approach and the smart contract access controller.
Suppose we store a data structure with roles associated on the blockchain. Concretely, we have a task, with roles associated, like a manager and a worker.
Suppose we also store the tasks in OrbitDB. Only the manager and worker should be able to edit the task. That is, the roles are defined on chain, and we would like to translate these roles into capabilities.
We could create a new capability per task: write-taskID, with the manager's and owner's keys in the array. In other words, our capabilities would include a lot of things like { 'write-<taskId' : [managerKey, workerKey] }.
The question is where to store and to create these new capabilities. We don't just want to store them directly on chain, as that will cost a lot.
I see two approaches.

The smart contract ACL uses an Orbit ACL to store capabilities
The smart contract ACL builds and stores the capabilities itself

I think this should now be addressed by both the OrbitDBAccessController and/or a custom AC. I would think a custom controller could be developed with various roles and canAppend could be used to evaluate these roles.
Closing for now as I think the latest AC functionality solves this problem but feel free to re-open if this functionality is still not achievable.


Empty post result triggers error result: 'Unexpected end of input at Object.parse'

I have hit an issue with the Http-Client when dealing with an empty result.
The post returns a blank 200 status upon success.  The http client triggers a catch on the promise.
Stack trace in error message:
"SyntaxError: Unexpected end of input at Object.parse (native) at HttpResponseMessage.get (http://localhost:9000/jspm_packages/npm/aurelia-http-client@1.0.0-beta.1.2.0/aurelia-http-client.js:205:34"
Below are the relevant response headers:
HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
Access-Control-Allow-Headers: Content-Type,Authorization
Access-Control-Allow-Methods: GET,POST,PATCH
Access-Control-Allow-Origin: *
Date: Thu, 14 Apr 2016 05:33:00 GMT
Content-Length: 0

I just modified the post method on the server to return some text 'Success' and this error cleared up.
So it looks like it is a genuine issue with handling empty results


Feature Request: SAP Note 2718300 Integration

We had a problem with a to long hostname by a customer.
It would be grate if this could be also checked in this role.
Description:
Physical and Virtual hostname length limitations
The length of SAPLOCALHOST is up to 13 characters and the length of SAPLOCALHOSTFULL, which is the FQDN can be longer than 13 characters. So basically:
It is acceptable to use a longer (e.g. 15 character) physical hostname for hosts running non-Netweaver services like HANA, SAPRouter, Data Services, BOBJ, SAP Web Dispatcher. (see Note 2074402)
A virtual hostname is not required for the systems listed in Point 1 above.
For all hosts running Netweaver, a physical hostname may be longer than 13 characters as long as there is:
a virtual hostname (i.e. SAPLOCALHOST) defined that is 13 characters or less and
the shorter virtual hostname is always the one referenced within SAP. (See Note 962955)

I assume yes, so I am closing this issue now.


TextField sets aria-labelledby in the wrong element

What RMWC Version are you using [major.minor.patch]:
6.1.3

Name your build system [Webpack, Rollup...]:
Webpack

Describe the bug with as much detail as possible:
The aria-labelledby attribute should be set in the input tag of the TextField, instead of its root (the label tag).

What happened, and what was supposed to happen:
After upgrading from version 5.7.2 to 6.1.3, all my testing-library tests involving the TextField started to fail. I've realized it was because the getByLabelText selector was not able to find the input elements. This is happenning because the aria-labelledby is not set in the input element (see MDC examples).

I also noticed that there is a kind of broken id in the input element itself and label.
As I see in specs https://www.w3.org/TR/wai-aria-practices-1.1/#naming_with_aria-labelledby aria-labelledby may reference several elements by ids split by space.
However, in @rmwc/textfield next code will generate kind of broken reference because ids used in aria-labelledby can't contain spaces to support multiple references
This code produces next snapshot
import {TextField} from '@rmwc/textfield'
import React from 'react'
import renderer from 'react-test-renderer'

test('TextField snapshot', () => {
  expect(
    renderer.create(<TextField label="Multiple words" />).toJSON(),
  ).toMatchSnapshot()
})

// Jest Snapshot v1, https://goo.gl/fbAQLP

exports[`TextField snapshot 1`] = `
<label
  aria-labelledby="textfield-Multiple words-label"
  className="mdc-text-field mdc-text-field--upgraded"
  onBlur={[Function]}
  onClick={[Function]}
  onFocus={[Function]}
  onKeyDown={[Function]}
  onKeyUp={[Function]}
  onMouseDown={[Function]}
  onMouseUp={[Function]}
  onTouchEnd={[Function]}
  onTouchStart={[Function]}
  style={Object {}}
>
  <span
    className="mdc-text-field__ripple"
  />
  <input
    className="mdc-text-field__input"
    onBlur={[Function]}
    onFocus={[Function]}
    onInput={[Function]}
    onMouseDown={[Function]}
    onTouchStart={[Function]}
    style={Object {}}
  />
  <span
    className="mdc-floating-label"
    id="textfield-Multiple words-label"
    onAnimationEnd={[Function]}
    style={Object {}}
  >
    Multiple words
  </span>
  <span
    className="mdc-line-ripple mdc-line-ripple--deactivating"
    onTransitionEnd={[Function]}
    style={
      Object {
        "transformOrigin": "0px center",
      }
    }
  />
</label>
`;

As you see, aria-labelledby has attribute value which might be interpreted in 2 different ways.
Because of this change, tests like the next one fails with the latest @testing-library/react
import {TextField} from '@rmwc/textfield'
import {render} from '@testing-library/react'
import React from 'react'

test('getByLabelText() multiple words', () => {
  const {getByLabelText} = render(<TextField label="Multiple words" />)
  expect(getByLabelText(/Multiple words/i)).toBeInTheDocument()
})

There are changes after which getByLabelText stopped working https://github.com/testing-library/dom-testing-library/pull/681


resolves #282: add default healthcheck to dockerfiles

I didn't see an approach using pg_isready when browsing through #282 and other proposed changes, but perhaps someone has already been down this route?
Probably someone will have input on the actual HEALTHCHECK settings to use (e.g. interval, timeout, retries) I can make any requested changes real quick (provided some intentional reason ;)
P.S. The readme told me to look over at https://hub.docker.com/_/postgres?tab=description info on contributing, I might be tired and completely overlooking it, but I didn't actually see anything. Hopefully I've set this up correctly, LMK if theres anything at all desired from a contributor perspective.

The postgres docs (and some 3rd party release notes) seem to imply that this is supported since 9.3, but the docs them self also list 9.3 as incompatible, nevertheless everything in this repos seems to be >=9.4 so seemingly we're good there.
Ref: https://www.postgresql.org/docs/9.3/app-pg-isready.html

Closing per docker-library HEALTHCHECK policy
See: https://github.com/docker-library/postgres/issues/282#issuecomment-558867369
Ref: https://github.com/docker-library/faq#healthcheck


How does one add an internal Test Flight tester using Pilot?

It seems by the pilot help documentation that pilot add only adds an external tester.  Can this be improved to be parameterized as follows? pilot add --internal or pilot add --external, maybe where external would be the default if no parameter is provided?

You can use --distribute_external to control this behavior.


fix(vllm): images and videos are base64 by default

Description
Images otherwise aren't passed by correctly and cannot be processed for multimodal
Notes for Reviewers
Part of  #3670
Signed commits

[ ] Yes, I signed my commits.

not hit by tests. merging


Appstudio update test-component-pac-gwnr

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-gwnr-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
13 seconds
clone-repository

✅ Succeeded
35 seconds
build-container

✅ Succeeded
16 seconds
deprecated-base-image-check

✅ Succeeded
58 seconds
clamav-scan

✅ Succeeded
12 seconds
clair-scan

✅ Succeeded
17 seconds
inspect-image

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
15 seconds
label-check

✅ Succeeded
16 seconds
optional-label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
8 seconds
show-summary

Pipelines as Code CI/test-component-pac-gwnr-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
13 seconds
clone-repository

✅ Succeeded
35 seconds
build-container

✅ Succeeded
17 seconds
inspect-image

✅ Succeeded
16 seconds
deprecated-base-image-check

✅ Succeeded
12 seconds
clair-scan

✅ Succeeded
58 seconds
clamav-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
15 seconds
label-check

✅ Succeeded
16 seconds
optional-label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
8 seconds
show-summary