Picture uploaded not being saved

Subject: Picture uploaded not being saved
Description:
Uploaded a profile pic
Results:
once I exit the edit profile section, the picture is not visible anymore
Backend version: develop-7291678f
Frontend version: develop-7291678f
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.54 Safari/537.36 Edg/95.0.1020.40
Page: https://app.couchers.org/profile/edit
User: andrei_petrescu (2772)

Forwarded to support


Add a check for packed tensors for convolution solvers

Some solvers allow non-packed tensor inputs while others don't. This PR adds a check to the ones that don't support.

@CAHEK7 , @iq136boy : I have removed the checks from CK 3D grouped convolution and naive convolution solvers, but for the rest, I'm not sure of the support myself.

Could you re-enable two winograd solvers as well?

@amberhassaan

@CAHEK7 Do we have a list of solvers that support non-packed tensors? I would recommend to disable solvers that we are not sure if they support non-packed tensors or not. And only enable the solvers if they passed the non-packed tensors tests.

Please assume that all old solvers do not support non-packed tensors. Even if Winograd seems supporting them, enabling the feature require investigations and testing.

@amberhassaan could you resolve the last round of review opinions above? We will let CI run once and then merge. Thanks!

@amberhassaan could you resolve the last round of review opinions above? We will let CI run once and then merge. Thanks!

@junliume : I have addressed all the comments. Please merge if CI passes.

Let's keep all the curly braced in this PR like they are, add appropriate clang-format rule, apply it and forget about this problem forever. I see no point to spend any time to review codestyle if it can be checked and applied automatically.

Let's keep all the curly braced in this PR like they are, add appropriate clang-format rule, apply it and forget about this problem forever. I see no point to spend any time to review codestyle if it can be checked and applied automatically.

I agree with this, formatting issues should never be part of a PR discussion since these checks can be automated.


Accessibility issue due to aria-label

Adding aria-label does announce it to screen readers but the container element on which the tooltip is shown, the text of that button for example won't be announced as shown in https://kazzkiq.github.io/balloon.css/ the text Hover me is not announced since the aria-label now just has the tooltip text which is an accessibility issue.
ideally, first, the button content should be announced and then the tooltip content.
For the accessibility, role tooltip should be added to the tooltip so screen readers announce it as tooltip but since it uses pseudo-element so won't be possible.

@kazzkiq should we have both aria-label and data-balloon so the content is announced via aria-label and tooltip is visible via data-balloon?
Ideally, the tooltip should close on pressing the escape key as well so is there any way I can achieve that by adding an attribute to the tooltips if i add an event listener?

@ad1992

the tooltip should close on pressing the escape key as well so is there any way I can achieve that by adding an attribute to the tooltips if I add an event listener?

Why should we close the tooltip on escape?
The escape should be active for things that require an explicit action to open (like click).
For hover and focus, we shouldn't have an escape handler. Is the escape control mentioned on the accessibility spec?

should we have both aria-label and data-balloon so the content is announced via aria-label and tooltip is visible via data-balloon

Even if you use data-balloon you can't announce the text inside the data-balloon attribute. As the CSS based tooltip libraries use pseudo-elements for adding tooltip, you can't add role="tooltip" on them. So that's why the best way is to use aria-label for tooltips.

Ideally, first, the button content should be announced, and then the tooltip content.

There are in general two use cases for tooltips.

The element is for visual (icons/shapes), and the tooltip you add is to define what the element does. In this case you don't need anything to be announced from the element. Ideally, we should repeat the information in element and tooltip if not required.

The element has text and the tooltip is a further description of that element. In such a case, the issue you mentioned will happen. But it can be fixed by incorporating button text in the tooltip itself.

@ad1992

the tooltip should close on pressing the escape key as well so is there any way I can achieve that by adding an attribute to the tooltips if I add an event listener?

Why should we close the tooltip on escape?
The escape should be active for things that require an explicit action to open (like click).

As per the guidelines When additional content is triggered on pointer hover or on keyboard focus, that additional content MUST be visually perceived and MUST be dismissible hence If the content obscures or replaces other content, it should be dismissed via keyboard without moving mouse hover or keyboard focus - such as by pressing the Escape key.

For hover and focus, we shouldn't have an escape handler. Is the escape control mentioned on the accessibility spec?

should we have both aria-label and data-balloon so the content is announced via aria-label and tooltip is visible via data-balloon

Even if you use data-balloon you can't announce the text inside the data-balloon attribute. As the CSS based tooltip libraries use pseudo-elements for adding tooltip, you can't add role="tooltip" on them. So that's why the best way is to use aria-label for tooltips.

Yep, that's what I tried mentioning above and hence sadly CSS tooltips will have some limitations when it comes to Accessibility.

Ideally, first, the button content should be announced, and then the tooltip content.

There are in general two use cases for tooltips.

The element is for visual (icons/shapes), and the tooltip you add is to define what the element does. In this case, you don't need anything to be announced from the element.
The element has text and the tooltip is a further description of that element. In such a case, the issue you mentioned will happen. But it can be fixed by incorporating button text in the tooltip itself.

Yep, I was talking about the 2nd case. I have tried incorporating the button text to the tooltip and it won't be a good user experience if we incorporate all the data to aria-label when it comes to using screen reader especially and also for sighted users the content will look repetitive which is again not a good experience.

I believe using aria-description instead of aria-label would help. I gave this a quick try, and while the button styles/tooltips break (due to the [aria-label] selectors and content: attr(aria-label)), the screen reader (VoiceOver on Mac for me) reads first the button text, and then the tooltip text.
This also appears to be more in-line with what WAI-ARIA recommends. Their guidance assumes that the tooltip is in a separate element and recommends using aria-describedby to link the button with the tooltip element. aria-description allows this to happen all in one element.
I'm going to play around with this a bit more, and open a PR if it works. I'll also need to ensure backwards compatibility with [aria-label], as this would be a major breaking change if both aren't supported.

Hmmm actually, aria-description may not (yet) be a viable option. According to the MDN page on aria-description:

Note: aria-description is still in W3C Editor's Draft for ARIA 1.3. For the time being, continue to use aria-describedby, which has been supported since ARIA 1.1.

Looking at caniuse.com, browser support only seems to be for Chrome and Edge at the moment.
For what it is worth, I do have a draft pull request for aria-description support (while also maintaining aria-label support). I also tested this with Chrome, FireFox, and Safari (despite lack of indicated browser support for the latter two) with VoiceOver, and it reads these as I would expect them to (ex from the demo, "Hover me, what's up?"), so this does seem to be an improvement.
However, I would be nervous moving to a not-yet-supported feature of two major browsers, so I'll leave it to the maintainers' judgement as to whether this is a wise move, and I'll move the linked PR to 'open' if so.


[🐞] onPost not working properly

Which component is affected?
Qwik Runtime
Describe the bug
I am doing onPost and expect it too redirect. but this is not redirecting for some unclear reason.
Here is how i am using the method:
// in the routes folder

export const onPost: RequestHandler = async (requestEvent) => {
  const data = await serverNotes();
  data.notes = [
    ...data.notes,
    { id: (data.notes.length + 1).toString(), title: "", text: "" }
  ];
  throw requestEvent.redirect(302, `/dashboard/`);
  throw requestEvent.redirect(302, `/dashboard/notes/${data.notes.length}`);
}

export const factoryFetch = async (method: "DELETE" | "PUT" | "POST", id: string | undefined) => {
  const response = await fetch(`/dashboard/notes/`, {
    method: method,
    headers: {
      "Content-Type": "application/json",
    },
    redirect: "follow", // manual, *follow, error
    body: JSON.stringify({ id: id }),
  });
  return response
}

export const fetchPost = async () => {
  return factoryFetch("POST", undefined)
}

// this code in the component i want to call it from
import { fetchPost } from "~/<your path>";

<p class="text-4xl font-semibold text-sky-950/70 [text-wrap:balance] w-fit">
  Your Next Great Idea Starts Here
</p>
<Button onClick$={async () => {
  await fetchPost();
}}>
  New note
</Button>

Reproduction
https://github.com/barel-mishal/onPostIssue
Steps to reproduce
Run after cloning the project.
npm install  npm start
System Info
System:
    OS: macOS 14.4
    CPU: (8) arm64 Apple M2
    Memory: 111.81 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 21.7.1 - /opt/homebrew/bin/node
    npm: 10.5.0 - /opt/homebrew/bin/npm
    bun: 1.0.30 - ~/.bun/bin/bun
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 123.0.6312.107
    Safari: 17.4
  npmPackages:
    @builder.io/qwik: ^1.5.2 => 1.5.2
    @builder.io/qwik-city: ^1.5.2 => 1.5.2
    undici: * => 6.12.0
    vite: ^5.1.6 => 5.2.8

Additional Information
click on the button you will never go to posty
Hope it will be fixed soon I use this pattren a lot

@gioboa are you working for ?

@JerryWu1234 nope, you can take it if you want

@JerryWu1234 nope, you can take it if you want

Could you offer more detail what I have to do? thanks

throw requestEvent.redirect it's not working correctly inside the code above.
Am I understanding correctly @barel-mishal ?

@gioboa

https://github.com/JerryWu1234/qwik/blob/a9b200527aaf4a83407ab83fc9b2709aac4a801e/packages/qwik-city/src/runtime/src/use-endpoint.ts#L36
I have dug into this for a while.
first of all, accord to above code.
if you want to redirect when using fetch, it seems like it only can be done within fetch .
So this problem occurs because this request is made by using fetch, not from browser.
@gioboa
Please point out if there is any wrong

@gioboa  @

@JerryWu1234 I never looked into that code so I have not clue about it, I'm so sorry 😢

I feel this isn't a bug..


[Task] Base query adapter

Synchronous queries

Data, error, loading

Asynchronous queries

I'm not quite sure what I was targeting when I opened this issue but I think it's all complete and I have new task issues to create that better describe where I'm at.


Clarified instructions for Pairwise algorithm

Added an example to further clarify the directions in the "Pairwise" algorithm, per issue #16800 https://github.com/freeCodeCamp/freeCodeCamp/issues/16800

Pre-Submission Checklist

[X] Your pull request targets the staging branch of freeCodeCamp.
[X] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[X] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[X] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[ ] Tested changes locally.
[ ] Addressed currently open issue (replace XXXXX with an issue no in next line)

Closes #16800
Description

Added an example to further clarify the desired behavior for the Pairwise algorithm challenge

Not I problem! I've made the change. Let me know if there's anything else needed.

@willimsbw I will be approving this PR. Thank you for your contribution. Happy Coding !


Add Omit, Pick

I don't think that it's possible to write pick / omit combinators, because you don't have access to the initial struct definition for the struct decoder.
However, I plan on moving the struct combinators for StructM into their own file, src / struct.  Though they are intended to be used solely with StructM, they can also include omit and pick in there for ease of use, and others potentially.
This will allow patterns like:
import * as s from 'schemata-ts/struct'
import * as S from 'schemata-ts/Schemata'

const DomainObjectBase = s.defineStruct({
   a: s.required(S.String),
  ssn: s.optional(S.String),
  some_snake_prop: pipe(s.optional(S.Natural), s.mapTo("someCamelProp"))
})

const DomainObject = S.StructM(DomainObjectBase)

$ExpectType:
// SchemaExt<
//   { a: string; ssn?: string | undefined; some_snake_prop?: Natural | undefined },
//   { a: string; ssn?: string | undefined; someCamelProp?: Natural | undefined }
// >

const SafeDomainObject = S.StructM(pipe(DomainObjectBase, s.omit("ssn")))

// $ExpectType:
// SchemaExt<
//  { a: string; some_snake_prop?: Natural | undefined },
//  { a: string; someCamelProp?: Natural | undefined }
// >


VSCode crashes when opening a folder

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

VS Code Version: 1.94
OS Version: Ubuntu 24.04

Steps to Reproduce:

Open Visual Studio Code.
Try to open any folder via File > Open Folder... or from the terminal (code /path/to/folder).
VSCode crashes immediately.

Expected Behavior:
The folder should open in VSCode without issues.
Actual Behavior:
VSCode crashes and closes unexpectedly without any UI error message.
Additional Information:

I ran VSCode with --verbose, and this error was consistently shown:

[1006/143507.204610:ERROR:process_memory_range.cc(75)] read out of range

I tried the following troubleshooting steps, but the issue persists:

Resetting VSCode configuration by deleting the .config/Code folder.
Reinstalling VSCode via both Snap and the official .deb package.
Running VSCode with sudo to check for permission issues.
Disabling all extensions (code --disable-extensions).
Disabling hardware acceleration.

Downgrading to version 1.93.1 fixed the issue completely.

The issue only occurs when opening folders. Opening individual files works as expected.

Let me know if further logs or system information are needed.

Probably a duplicate of https://github.com/microsoft/vscode/issues/230454

Hi, I managed to open a folder through the terminal, I typed: code path/to/project-root and enter.
With that, my project folder opened in vscode

Hello,
I have the same problem doing this.
I think my problem comes from the versions installed with snap.
If you installed it with the .deb, it is likely that you did not encounter the problem.

/duplicate


ReferenceCountHelper junit tests for GEODE-656

ReferenceCountHelper junit tests for GEODE-656

looks good; I will pull it in


Provide tests for shtest

The shtest test runner needs itself to be tested. The scope of this task is to provide tests for some of the basic functionality, e.g., after creating a sample structure of (fake) test cases:

have a test that gets shtest gather and run tests from a (fake) test module;
have a test that gets shtest run a single test from a (fake) test module;
have a test that gets shtest gather and run tests from a directory with two (fake) test modules.

Merged to main; closing.


Draw a box around margin when editing a component

Currently only padding is taken into consideration. Adding margin would likely mean some custom math and rewriting the current preview logic.

The current solution is good enough.


Can no longer authenticate

Been using Colab over the last year and using the following code to access image catalogues. I am running this off my personal google account and not sure what is going on?
# Trigger the authentication flow
ee.Authenticate()

# Initialize the library
ee.Initialize()

However, recently i keep getting the error below
WARNING:googleapiclient.http:Encountered 403 Forbidden with reason "PERMISSION_DENIED"
HttpError                                 Traceback (most recent call last)
/usr/local/lib/python3.10/dist-packages/ee/data.py in _execute_cloud_call(call, num_retries)
378   try:
--> 379     return call.execute(num_retries=num_retries)
380   except googleapiclient.errors.HttpError as e:
7 frames
HttpError: <HttpError 403 when requesting https://earthengine.googleapis.com/v1/projects/earthengine-legacy/algorithms?prettyPrint=false&alt=json returned "Google Earth Engine API has not been used in project<PHONE_NUMBER>47 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/earthengine.googleapis.com/overview?project=522309567947 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.". Details: "[{'@type': 'type.googleapis.com/google.rpc.Help', 'links': [{'description': 'Google developers console API activation', 'url': 'https://console.developers.google.com/apis/api/earthengine.googleapis.com/overview?project=522309567947'}]}, {'@type': 'type.googleapis.com/google.rpc.ErrorInfo', 'reason': 'SERVICE_DISABLED', 'domain': 'googleapis.com', 'metadata': {'consumer': 'projects/522309567947', 'service': 'earthengine.googleapis.com'}}]">
During handling of the above exception, another exception occurred:
EEException                               Traceback (most recent call last)
/usr/local/lib/python3.10/dist-packages/ee/data.py in _execute_cloud_call(call, num_retries)
379     return call.execute(num_retries=num_retries)
380   except googleapiclient.errors.HttpError as e:
--> 381     raise _translate_cloud_exception(e)  # pylint: disable=raise-missing-from
382
383
EEException: Google Earth Engine API has not been used in project<PHONE_NUMBER>47 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/earthengine.googleapis.com/overview?project=522309567947 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.

Thanks for the reply but still somewhat confused.
So for colab examples now i need to create a project for each one? even if it is a demo script or examples from github https://colab.research.google.com/github/google/earthengine-community/blob/master/tutorials/detecting-changes-in-sentinel-1-imagery-pt-1/index.ipynb#scrollTo=XeFsiSp2aDL6?
I created a project and tried it again but still having issues
ee.Authenticate()
ee.Initialize(project = 'Cloud Based Oil Detection')

HttpError                                 Traceback (most recent call last)
/usr/local/lib/python3.10/dist-packages/ee/data.py in _execute_cloud_call(call, num_retries)
382   try:
--> 383     return call.execute(num_retries=num_retries)
384   except googleapiclient.errors.HttpError as e:
7 frames
HttpError: <HttpError 400 when requesting https://earthengine.googleapis.com/v1/projects/Cloud Based Oil Detection/algorithms?prettyPrint=false&alt=json returned "Project 'projects/Cloud Based Oil Detection' not found or deleted.". Details: "[{'@type': 'type.googleapis.com/google.rpc.ErrorInfo', 'reason': 'USER_PROJECT_DENIED', 'domain': 'googleapis.com', 'metadata': {'service': 'earthengine.googleapis.com', 'consumer': 'projects/Cloud Based Oil Detection'}}]">
During handling of the above exception, another exception occurred:
EEException                               Traceback (most recent call last)
/usr/local/lib/python3.10/dist-packages/ee/data.py in _execute_cloud_call(call, num_retries)
383     return call.execute(num_retries=num_retries)
384   except googleapiclient.errors.HttpError as e:
--> 385     raise _translate_cloud_exception(e)  # pylint: disable=raise-missing-from
386
387
EEException: Project 'projects/Cloud Based Oil Detection' not found or deleted.

Earth Engine computation is run through a Cloud project. You only need a single Cloud project that is Earth Engine enabled. For example, my primary project ID is 'ee-braaten'. I use it in the JavaScript Code Editor and in any Colab notebook that I'm using Earth Engine. No need for a separate project for each Notebook - it is a one-time setup.
It looks like you are providing the Project name, but it needs to be the Project ID. See the distinction here: https://cloud.google.com/resource-manager/docs/creating-managing-projects

Closing this thread as it is off-topic (not related to contents of the repository). For help with general Earth Engine errors, please see this help guide for routing the issue.
In this case, a good resource is the Earth Engine Developer Forum. There is a current thread on the auth issue, for example.


Email forwarding

I don't think this is the intention of the project, but wanted to throw an idea out there.
Amazon SES is one of the more economic production SMTP services, but it doesn't offer an interface for seeing which emails are sent to who, at what time, with what contents - that's why projects like SES Dashboard exist.
Mailpit could provide all that context for a production app, but forward along the email to SES for deliverability. Too out of scope? Thanks!

@jimafisk Are you meaning that Mailpit would act as a form of transparent caching proxy for email, so it would route it through and store a copy?

Yes exactly. Not suggesting to completely change the direction of the project, trapping emails during development is very useful. Just wondering if it could provide additional capabilities for a prod environment to be an "invisible" layer between your app and SES to log the sent email info?

Thanks for the explanation. I'll give this some consideration (adding a setting of sorts for an SMTP relay) ~ though I'm a bit hesitant / cautious as something like this could then be used to illegally monitor routed email too. In saying that there are potentially already other existing ways to send duplicate copies of all mail to multiple hosts (I know you can do it by injecting always_bcc=.... into postfix's config), which in turn would also solve your requirement.

For our usecase we only need one "release SMTP", so command line option would be sufficient.

Would be nice to have a button in interface that could send email to another email address via some SMTP sender or web sending such as Mailgun/Sendgrid.
It would be useful to allow seeing how the email may appear in some specific email clients such as Outlook/Gmail/Apple and on Mobile device whilst still acting as a catch-all/trap for development servers.

I haven't started any coding for this yet, other than thinking about the most suitable implementation that will (hopefully) satisfy most use-cases. Currently my thinking is this:

An runtime flag to set a single SMTP "relay server" configuration file. Whilst I'm sure some would like to relay via third-party APIs such as Mailgun or Sendgrid, the truth is there are too many different services to maintain, and most (if not all) support SMTP too. I also don't want to spend my time debugging different services.
A runtime flag to automatically relay all received mails (ie: proxy). This would relay all emails to their original recipient(s) as they are received. There would be zero fault tolerance, so if the relay SMTP server was down or rejects the message for whatever reason, the relayed message would be lost (the error would be logged and the original mail would still be stored in Mailpit though). I do not want to implement a "postfix clone" to handle retries, rejections etc. Mailpit was never designed to be implemented in production as a "caching proxy", so if it is flooded with emails, then it will flood the relaying SMTP with emails too.
If an SMTP relay configuration was provided during startup, the UI would have a button (per email) to release an email. This would default to the original To, Cc & Bcc values, but would allow you to change that before confirming sending.

A point worth noting is that relaying messages would alter somewhat the original mail headers (even if it is slightly), and potentially affect any present DKIM / SFP authentication depending on what relay SMTP is used and whether that aligns. There is no way to avoid this as that's exactly what DKIM / SFP authentication is designed to protect against.

Found this from the past, thanks for your consideration.

Mailpit does not have the ability to release emails (relay them to another SMTP). I have no plans to add this either.
https://github.com/axllent/mailpit/issues/15

Agree, SendGrid SMTP for example is well documented so totally fine to just configure the credentials in env vars probably.
https://docs.sendgrid.com/for-developers/sending-email/getting-started-smtp
User: YXBpa2V5 Base64 Encoded username of "apikey"
Pass: YourApiKey Base64 Encoded
Host: smtp.sendgrid.net
Port: SendGrid accepts unencrypted and TLS connections on ports 25, 587, & 2525. You can also connect via SSL on port 465. Many hosting providers and ISPs block port 25 as a default practice. (AWS does as well if I recall).

That makes sense on altering the headers slightly, a real server should be used anyway with something like mxtoolbox to check DKIM/SPF, Mostly curious about testing visually in various email clients and mobile clients manually. Something like https://www.litmus.com/email-testing/ peeks my curiosity but for most projects I only have a couple clients I'm worried about as sometimes styling/buttons come out wrong or other email clients muddle with or strip content, it's normally possible to switch them over to SendGrid temporarily just to check but one of the KEY reasons to use a service such as MailPit is that it traps the emails from development servers so they don't get sent to real addresses/inboxes by accident...
Great stuff thanks

that would be greatly appreciated!

@axllent I've put in some work on these features https://github.com/patramsey/mailpit/tree/release-messages in this branch. I can create a PR if it makes sense.

@patramsey Thank you. I have taken a quick look and it is actually quite similar to what I originally started doing several weeks ago (but gave up on temporarily). There is a lot more involved in this task to get it working, and also several related complications when it comes to auto-releasing messages - so I have much more to do, and several structural changes to make first. No need for a PR at this stage thanks, but please leave your branch as-is as it is handy for me to refer to when I do get around to restarting this. Email forwarding is definitely still on my radar, in fact it is the next big thing on my list, however I need to make some of the smaller changes first :+1:

@axllent for sure, I'm happy to assist with the complications around auto-releasing messages if you'd like.
I could separate the explicit release via the UI into a different branch from the auto release if that is useful. Maybe the changes you are envisioning don't impact that code path? The explicit release is the feature I'm most interested in and excited about. Our team will then be able to use Mailpit as a replacement for Mailhog!

Thank you for the offer @patramsey, but please hold off as there's a good chance I won't merge it, as it'll be more work to undo/redo things as it will be simply to write it the way I have in mind. I understand your urgency for wanting this, but you will just have to be a bit more patient.

Would love to see this feature implemented.
I recently created ddev-mailpit to intergrate Mailpit into a DDEV project.
The feature discussed in this issue would help bring feature-parity with Mailhog (DDEV's default mail debugger) and maybe help replace it.

Despite my earlier comment about month-end release, I ended up completing this today (due to bad weather) and and have released it with v1.6.0.
This includes both the ability to "release" a message via the Web UI/API, as well as the original request "proxy" incoming mails automatically to a SMTP server. I have created a wiki page to provide some additional documentation regarding the configuration file and the subtle differences between both options.
I'll close this issue given that there are now too many comments to constructively deal with feedback / issues with the new features. Any issues should be reported via a new Github issue, thanks. PS: I will still be away for a few days so responses will be delayed. Have fun!


feat: 3594 - expand/collapse for packagings components

New files:

edit_new_packagings_component.dart: Edit display of a single ProductPackaging component.
edit_new_packagings_helper.dart: Helper about packaging component edition. Useful with controllers.

Impacted file:

edit_new_packagings.dart: refactored using new classes EditNewPackagingsComponent and EditNewPackagingsHelper

What

Now there's an expand/collapse feature on the new edit packagings page.
Existing components are collapsed by default.
New ("just added") components are expanded by default.
Some refactoring in this PR, as the main file was getting too big and too confusing.

Screenshot
New landing page, with all components collapsed:

Part of

#3594

Thank you @AshAman999 @teolemon for the review!


Remove path to Python in .bat files

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] 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.

xref: https://github.com/conda-forge/qgis-feedstock/pull/86
#63 didn't fix the issue of the build path being embedded in the .bat files. This is another attempt and it simply removes the path from the Python command so it can be found in any environment. Any better suggestions of how to fix Windows properly greatly received!

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.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you but ran into some issues, please ping conda-forge/core for further assistance.

Thanks @gillins!


Seqcol comparison api generic version - using low level reflection libraries

In this PR, we'll try to make the comparison API more generic and flexible regarding the sequence collections inputs.
Not all seqCol objects will have the same set of attributes, however some attributes are required.

I think we no longer need this PR.


Allow the user to select a model

Implement argparse for handling command line options
Add --model option to allow specifying the model name (default: gpt-4)
Update send_error_to_gpt4 function to accept model_name as a parameter
Rename send_error_to_gpt4 function to send_error_to_gpt

addresses #2, #3 and partially addresses #5

Thank you! I'd actually already reworked to use Fire for arguments, I've pushed that now. I'll fix the new conflicts and merge your other changes


Proposal - October 2022 website refresh

Summary:
This tracks a website refresh to be reviewed by STC to improve user experience and increase clickthrough rates (CTR) to our top calls to action
Calls to action:
I believe our prioritized goals and CTAs are

Get started [with Dapr CLI and quickstarts]
Learn about Dapr features, technology, and case studies to gain confidence [via docs and deep links]
Learn about the Dapr Community [the community around meetings, GH, discord and more is itself a feature]

Key challenges:

Site does not have analytics for most links, so we are flying blind mostly around what users are clicking on or bouncing from #65
Testimonials links has very small CTR = 0.1%.  I believe Testimonials verbiage feels like marketing.
The hero of Dapr is the set of best practice APIs/building blocks, but this is too far below the fold
We don't show code anywhere to attract real devs.  this still has a CTO or architect feel to it

Proposed changes:

fix lack of telemetry.  PR #64
-- design changes -- happy to A/B test--
rename Testimonials to Case Studies (more like Kubernetes.io)
Add a new tab for Community
Remove topmost button for Get started in favor of one in the middle of page, making room for community
move up the API and building block blurb
Remove the noisy animation under "Build connected distributed applications faster"
Consider adding a more prominent Case Studies teaser section that loops through logos + quotes.  Keep simple badges above the fold however.

Completed for Oct


Latest release breaks scriptcs in Vs Code and Visual Studio 2015

We used to get OmniSharp running for .csx files in Visual Studio Code by providing an empty project.json file. Thus has been working for a LONG time now.
With the latest release it throws the following error.
[ERROR:Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware] An unhandled exception has occurred: Must be able aggregate the response to spread them out across all plugins for /currentfilemembersastree
Another option is to debug scripts in VS using a project that scriptcs sets up for us
:openvs "somescript.csx"

This also stopped working although I am not sure about the relation between VS 2015 and OmniSharp in this case.
Nevertheless, downgrading to beta13 solved the issue, at least for VS Code.
I had to specify the path to OmniSharp in the workspace settings
{
    "omnisharp.path": "C:/omnisharp-win-x64-net451"
}

The problem (or rather not problem, just the cause of this situation) is that VS Code will use .NET Core version of omnisharp which has no scripting support at the moment.
If you manually point to Desktop CLR / Mono build of omnisharp using omnisharp.path, it's gonna work again (no need to downgrade to beta13, latest works too).

Okay, how would such a configuration look like?
The strange thing is that intellisense for .csx files stopped working for me yesterday in Visual Studio 2015.
I did update the .Net Core tooling stuff. Is that related somehow?

just download latest desktop build from here and unzip somewhere
Then go to File > Preferences > User Settings and point to your newly unzipped omnisharp executable:
// Place your settings in this file to overwrite the default settings
{
    "omnisharp.path": "c:\\code\\omnisharp\\OmniSharp.exe"
}

Nice. Any suggestion on why is is broken in Visual Studio 2015 too?. Might be off-topic here though :)

sorry, no idea at the moment - but please open an issue scriptcs repo


Jump Search in JavaScript

Jump Search
Idea is to implement the Jump Search algorithm in Javascript
Have you read the Contributing Guidelines on Pull Requests?
Yes

/assign


Show battery status

Hi,
First: compliments for this plugin. It's beter than the HomeKit integration from Tado.
I have configured all 9 Todo thermostats and everything is working. The only thing is that I can not see the battery status. In the Home app it is not there. In the Eve app it shows always 100%. Is there a way in this plugin to show the actual battery status?

Same problem here. Battery accessory doesn't show in Home.app MacOS nor iOS and although it does show in Homebridge, it is always 100%.
Would be useful if it could be seen in Home.app and was accurate, but as it is, might as well disable it.


feat: add new commands, remove deprecated

bugfixes with targets that have : in them
toplevel targets are also now completed.
I also have a whole host of tweaks at https://github.com/forivall/nx-completion/tree/cleanup, let me know if you'd be open to that as a PR too.

Thanks for the improvements @forivall!

I also have a whole host of tweaks at https://github.com/forivall/nx-completion/tree/cleanup, let me know if you'd be open to that as a PR too.

Go ahead, open it!


Consider using HTTP keep-alive in fetch calls

I noticed in https://github.com/Flagsmith/flagsmith-nodejs-client/blob/main/flagsmith-core.js that no custom agent with keep-alive is configured. I believe this means that (despite always connecting to the same host) with every fetch call, a DNS lookup is done, a connection is opened, and a TLS handshake is performed.
It might be worth considering implementing this for improved performance of the SDK.

@kyle-ssg we were also thinking it might be possible to do either DNS pre-fetching or SSL warming as well if the HTTP client allows it

I should add there may be considerations here in the infrastructure side. You might want to consider your idle timeouts and the maximum number of connections your web-server has configured.

Understood RE keep-alive.

@kyle-ssg we were also thinking it might be possible to do either DNS pre-fetching or SSL warming as well if the HTTP client allows it

I'd imagine people would construct an instance of Flagsmith outside of requests/functions. With that being the case, wouldn't that already be essentially done as part of the first request in local evaluation?

I should add there may be considerations here in the infrastructure side. You might want to consider your idle timeouts and the maximum number of connections your web-server has configured.

Considering this, what do we thing about adding an optional agent as part of the Flagsmith class properties.
Example:
const agentOptions: AgentOptions = { keepAlive: true, keepAliveMsecs: 6000 };
const httpAgent = new http.Agent(agentOptions);
const httpsAgent = new https.Agent(agentOptions);
const agent = (_parsedURL:URL) => _parsedURL.protocol == 'http:' ? httpAgent : httpsAgent;

....

const flagsmith = new Flagsmith({
    environmentKey,
    agent,
    ...
});

I did the latter but realised actually the ability to supply a custom agent would allow for proxy support, so I think we'll go with that.
const agent = require('https-proxy-agent');
const flagsmith = new Flagsmith({
    environmentKey,
    agent,
    ...
});

https://github.com/Flagsmith/flagsmith-nodejs-client/blob/main/examples/custom-fetch-agent/src/api/index.js


Dockerfile Missing Version in Name When Copying jar File

Describe the bug
Trying to migrate a CloudFoundry application to Kubernetes with the Gradle and Cloud Foundry transformer. The Dockerfile that gets generated does not reference the jar file built by Gradle properly. It is missing the version. In my specific example, the Dockerfile tries a COPY with COPY --from=spring-music-buildstage /app/build/libs/spring-music.jar . when Gradle actually builds /app/build/libs/spring-music-1.0.jar as it references the version from gradle.properties.
To Reproduce
Steps to reproduce the behavior:

Git clone spring-music
git clone https://github.com/cloudfoundry-samples/spring-music
Plan a Migration
move2kube plan -s spring-music
Transform
move2kube transform

Expected behavior
The Dockerfile to reference the correct jar file name. It is leaving out the version of the jar file being built.
Desktop (please complete the following information):

OS: Ubuntu 22.04
Version v0.3.3

Additional context
Here is the full Dockerfile (minus the comments):
FROM registry.access.redhat.com/ubi8/ubi:latest AS spring-music-buildstage
RUN yum install -y java-17-openjdk-devel

WORKDIR /app

# copy everything, including child modules to do a build using the parent build.gradle
COPY . .
COPY gradlew .
COPY gradle gradle

RUN ./gradlew clean assemble

FROM registry.access.redhat.com/ubi8/ubi-minimal:latest
ENV PORT 8080
RUN microdnf update && microdnf install --nodocs java-17-openjdk-devel && microdnf clean all
COPY --from=spring-music-buildstage /app/build/libs/spring-music.jar .
EXPOSE 8080
CMD ["java", "-jar", "spring-music.jar"]

Thanks @jacobmammoliti for the issue.
@HarikrishnanBalagopal can you please take a look at this issue. We are most probably not using the gradle.properties file yet. We might need to add it.

@jacobmammoliti Yeah we were not looking at gradle.properties for the version. Have made a PR to fix that.
Let us know if we should be looking for more things inside the gradle.properties file.
The new Dockerfiles we generate have the version in the JAR filename.
$ cat Dockerfile.buildstage
#   Copyright IBM Corporation 2021
#
#   Licensed under the Apache License, Version 2.0 (the "License");
#   you may not use this file except in compliance with the License.
#   You may obtain a copy of the License at
#
#        http://www.apache.org/licenses/LICENSE-2.0
#
#   Unless required by applicable law or agreed to in writing, software
#   distributed under the License is distributed on an "AS IS" BASIS,
#   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
#   See the License for the specific language governing permissions and
#   limitations under the License.

FROM registry.access.redhat.com/ubi8/ubi:latest AS spring-music-buildstage
RUN yum install -y java-1.8.0-openjdk-devel

WORKDIR /app

# copy everything, including child modules to do a build using the parent build.gradle
COPY . .
COPY gradlew .
COPY gradle gradle

RUN ./gradlew clean assemble

ibm-macbook-pro:source user$ cat Dockerfile
#   Copyright IBM Corporation 2021
#
#   Licensed under the Apache License, Version 2.0 (the "License");
#   you may not use this file except in compliance with the License.
#   You may obtain a copy of the License at
#
#        http://www.apache.org/licenses/LICENSE-2.0
#
#   Unless required by applicable law or agreed to in writing, software
#   distributed under the License is distributed on an "AS IS" BASIS,
#   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
#   See the License for the specific language governing permissions and
#   limitations under the License.

FROM registry.access.redhat.com/ubi8/ubi-minimal:latest
ENV PORT 8080
RUN microdnf update && microdnf install --nodocs java-1.8.0-openjdk-devel && microdnf clean all
COPY --from=spring-music-buildstage /app/build/libs/spring-music-1.0.jar .
EXPOSE 8080
CMD ["java", "-jar", "spring-music-1.0.jar"]

and tested building and running those Dockerfiles:
$ ./builddockerimages.sh
building image spring-music-buildstage
[+] Building 3.5s (12/12) FINISHED
 => [internal] load build definition from Dockerfile.buildstage                                                                                0.0s
 => => transferring dockerfile: 950B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for registry.access.redhat.com/ubi8/ubi:latest                                                                                3.4s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 1.23MB                                                                                0.0s
 => [1/7] FROM registry.access.redhat.com/ubi8/ubi:latest@sha256:8b002ccba444981ba32cab7d9454414da920218bd13f5b3f276978d577cd966f                                                                                0.0s
 => CACHED [2/7] RUN yum install -y java-1.8.0-openjdk-devel                                                                                0.0s
 => CACHED [3/7] WORKDIR /app                                                                                0.0s
 => CACHED [4/7] COPY . .                                                                                0.0s
 => CACHED [5/7] COPY gradlew .                                                                                0.0s
 => CACHED [6/7] COPY gradle gradle                                                                                0.0s
 => CACHED [7/7] RUN ./gradlew clean assemble                                                                                0.0s
 => exporting to image                                                                                0.0s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:90c25056ba1f53f6dc57fcafe6e0ca31dcfede547c3cdd0a65d546b8d97d22c1                                                                                0.0s
 => => naming to docker.io/library/spring-music-buildstage                                                                                0.0s

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
/Users/user/temp/tbug-m2k-857/t8/myproject
building image spring-music
[+] Building 1.6s (8/8) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 943B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for registry.access.redhat.com/ubi8/ubi-minimal:latest                                                                                1.5s
 => FROM docker.io/library/spring-music-buildstage:latest                                                                                0.0s
 => [stage-0 1/3] FROM registry.access.redhat.com/ubi8/ubi-minimal:latest@sha256:9a9149dbba8dc5a961dfec460018c245b49da0f52e9934e1a70dd4d42f9fc5b7                                                                                0.0s
 => CACHED [stage-0 2/3] RUN microdnf update && microdnf install --nodocs java-1.8.0-openjdk-devel && microdnf clean all                                                                                0.0s
 => CACHED [stage-0 3/3] COPY --from=spring-music-buildstage /app/build/libs/spring-music-1.0.jar .                                                                                0.0s
 => exporting to image                                                                                0.0s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:b3e92093784187b3e4f8e56b771aa8868d239fd49e1cb7e6d1c5bc1be3a45689                                                                                0.0s
 => => naming to docker.io/library/spring-music                                                                                0.0s

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
/Users/user/temp/tbug-m2k-857/t8/myproject
done

$ docker run --rm -it -p 8080:8080 spring-music

  .   ____          _            __ _ _
 /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
 \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
  '  |____| .__|_| |_|_| |_\__, | / / / /
 =========|_|==============|___/=/_/_/_/
 :: Spring Boot ::                (v2.6.7)

2022-09-05 15:15:07.153  INFO 1 --- [           main] .m.c.SpringApplicationContextInitializer : Found services
2022-09-05 15:15:07.159  INFO 1 --- [           main] o.c.samples.music.Application            : Starting Application using Java 1.8.0_342 on f851ffb2ff1f with PID 1 (/spring-music-1.0.jar started by root in /)
2022-09-05 15:15:07.160  INFO 1 --- [           main] o.c.samples.music.Application            : No active profile set, falling back to 1 default profile: "default"
2022-09-05 15:15:08.091  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode!
2022-09-05 15:15:08.093  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode.
2022-09-05 15:15:08.299  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 196 ms. Found 1 JPA repository interfaces.
2022-09-05 15:15:08.917  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
2022-09-05 15:15:08.932  INFO 1 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2022-09-05 15:15:08.932  INFO 1 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.62]
2022-09-05 15:15:09.015  INFO 1 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2022-09-05 15:15:09.015  INFO 1 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 1806 ms
2022-09-05 15:15:09.269  INFO 1 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2022-09-05 15:15:09.458  INFO 1 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Start completed.
2022-09-05 15:15:09.510  INFO 1 --- [           main] o.hibernate.jpa.internal.util.LogHelper  : HHH000204: Processing PersistenceUnitInfo [name: default]
2022-09-05 15:15:09.572  INFO 1 --- [           main] org.hibernate.Version                    : HHH000412: Hibernate ORM core version 5.6.8.Final
2022-09-05 15:15:09.770  INFO 1 --- [           main] o.hibernate.annotations.common.Version   : HCANN000001: Hibernate Commons Annotations {5.1.2.Final}
2022-09-05 15:15:09.924  INFO 1 --- [           main] org.hibernate.dialect.Dialect            : HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
2022-09-05 15:15:10.623  INFO 1 --- [           main] o.h.e.t.j.p.i.JtaPlatformInitiator       : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
2022-09-05 15:15:10.632  INFO 1 --- [           main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'
2022-09-05 15:15:10.893  WARN 1 --- [           main] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
2022-09-05 15:15:11.060  INFO 1 --- [           main] o.s.b.a.w.s.WelcomePageHandlerMapping    : Adding welcome page: class path resource [static/index.html]
2022-09-05 15:15:11.300  INFO 1 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 13 endpoint(s) beneath base path '/actuator'
2022-09-05 15:15:11.344  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8080 (http) with context path ''
2022-09-05 15:15:11.358  INFO 1 --- [           main] o.c.samples.music.Application            : Started Application in 4.637 seconds (JVM running for 5.242)
2022-09-05 15:15:16.919  INFO 1 --- [nio-8080-exec-1] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring DispatcherServlet 'dispatcherServlet'
2022-09-05 15:15:16.919  INFO 1 --- [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet        : Initializing Servlet 'dispatcherServlet'
2022-09-05 15:15:16.922  INFO 1 --- [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet        : Completed initialization in 2 ms


community server 5.21.0 cannot start with apoc 5.21.0 enabled

Expected Behavior (Mandatory)
Neo4j community server 5.21.0 installed on Windows Server 2016.
Expecting running neo4j service normally with apoc enabled.
Actual Behavior (Mandatory)
An error occurs and server cannot start.
The error says, "Unable to set up injection for procedure Xml, the field apocConfig has type class apoc.ApocConfig which is not a known injectable component."
When running without apoc, server works normally. (both neo4j browser and bolt work normally)
How to Reproduce the Problem
Steps (Mandatory)

Instart Neo4j community server 5.21.0 on Windows Server 2016
Copy apoc-core-5.21.0-core.jar from labs folder to plugins folder
Start server

Specifications (Mandatory)
Currently used versions
Versions

OS: Windows Server 2016
Neo4j: 5.21.0
Neo4j-Apoc: 5.21.0
JDK: openjdk-17.0.2

Full stacktraces are here:
2024-07-04 09:22:11.200+0000 ERROR [o.n.g.f.DatabaseManagementServiceFactory] Error starting Neo4j database server at D:\neo4j_db\data\databases
org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.procedure.impl.GlobalProceduresRegistry@2d258eff' was successfully initialized
, but failed to start. Please see the attached cause exception "Unable to set up injection for procedure Xml, the field apocConfig has type c lass apoc.ApocConfig which is not a known injectable component.".
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:364) ~[neo4j-common-5.21.0.jar:5.21.0]
at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:91) ~[neo4j-common-5.21.0.jar:5.21.0]
at org.neo4j.graphdb.facade.DatabaseManagementServiceFactory.startDatabaseServer(DatabaseManagementServiceFactory.java:271) [neo4j-5.21.0.
jar:5.21.0]
at org.neo4j.graphdb.facade.DatabaseManagementServiceFactory.build(DatabaseManagementServiceFactory.java:215) [neo4j-5.21.0.jar:5.21.0]
at org.neo4j.server.CommunityBootstrapper.createNeo(CommunityBootstrapper.java:38) [neo4j-5.21.0.jar:5.21.0]
at org.neo4j.server.NeoBootstrapper.start(NeoBootstrapper.java:184) [neo4j-5.21.0.jar:5.21.0]
at org.neo4j.server.BlockingBootstrapper.start(BlockingBootstrapper.java:46) [neo4j-5.21.0.jar:5.21.0]
at org.neo4j.server.NeoBootstrapper.start(NeoBootstrapper.java:99) [neo4j-5.21.0.jar:5.21.0]
at org.neo4j.server.CommunityEntryPoint.start(CommunityEntryPoint.java:42) [neo4j-5.21.0.jar:5.21.0]
Caused by: org.neo4j.kernel.api.exceptions.ComponentInjectionException: Unable to set up injection for procedure Xml, the field apocConfig has
type class apoc.ApocConfig which is not a known injectable component.
at org.neo4j.procedure.impl.FieldInjections.createInjector(FieldInjections.java:92) ~[neo4j-procedure-5.21.0.jar:5.21.0]
at org.neo4j.procedure.impl.FieldInjections.setters(FieldInjections.java:74) ~[neo4j-procedure-5.21.0.jar:5.21.0]
at org.neo4j.procedure.impl.ProcedureCompiler.compileProcedure(ProcedureCompiler.java:288) ~[neo4j-procedure-5.21.0.jar:5.21.0]
at org.neo4j.procedure.impl.ProcedureCompiler.compileProcedure(ProcedureCompiler.java:242) ~[neo4j-procedure-5.21.0.jar:5.21.0]
at org.neo4j.procedure.impl.ProcedureJarLoader.loadProceduresFromDir(ProcedureJarLoader.java:89) ~[neo4j-procedure-5.21.0.jar:5.21.0]
at org.neo4j.procedure.impl.GlobalProceduresRegistry.unguardedLoadFromDisk(GlobalProceduresRegistry.java:240) ~[neo4j-procedure-5.21.0.jar
:5.21.0]
at org.neo4j.procedure.impl.GlobalProceduresRegistry.start(GlobalProceduresRegistry.java:209) ~[neo4j-procedure-5.21.0.jar:5.21.0]
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:347) ~[neo4j-common-5.21.0.jar:5.21.0]
... 8 more

After reviewing system requirements, I replaced openjdk17 with oraclejdk21. And now it's working normally with apoc enabled.
So this is just a jdk issue. Sorry for disturbing, should read manuals carefully.
Reference:
https://neo4j.com/docs/operations-manual/current/installation/requirements/

For cloud environments, and server-based, on-premise environments:

Operating System
Supported JDK

Windows Server 2016, 2019, 2022
OracleJDK 17, ZuluJDK 17


Add scrollContent to modal

Added scrollContent to allow for the inner modal content to be scrollable so that it works the same as screen/slideOver but uses the variable modal widths.

@danharrin, you didn't port this over to 3.x, did you?

I did, but I can revert it

I reverted only in v3

I reverted only in v3

Yeah, but as the API will not exist in 3.x, might as well mark it as deprecated in 2.x now.


Find additional data sources for pretraining

Link below datasets which can be used for data pretraining and data augmentation
Comment about quality and how they can complement the main dataset we use
https://github.com/ieee8023/covid-chestxray-dataset

@williamFalcon mentioned some Xray dataset (probably just classification but still good for training backbone)

lets have augmentation separate #6

Some additional x-ray datasets. Different task, but similar modality

MIMIC-CXR
CheXpert
NIH ChestXRay

One more

Before submitting more, please check if it is not already in torchxrayvision repo.
See the datasets there.
https://github.com/mlmed/torchxrayvision/blob/master/torchxrayvision/datasets.py


Update Settings “general”

Automatically generated by Netlify CMS

👷 Deploy Preview for axamusic processing.

Name
Link

🔨 Latest commit
90543a1b376478095de675a5c2be745c16c9446a

🔍 Latest deploy log
https://app.netlify.com/sites/axamusic/deploys/65ceecd6eb49cf0008e7c685


Brackets won't start on Mac / El Capitan

Hello, I have one really persistent issue with brackets on Mac. Brackets won't start no matter what I do. It only loads  main panel and stays there. I have tried to uninstall it, tried a version without Extract and nothing helps. Is there any chance to fix this since Brackets has become my main programming editor?

This happens to me too. Probably because of El Capita. Also, notice the menu bar with the old, pre-Yosemite look.
I actually managed to use it for a while before this happened. Still, the menu bar had that look already and Cmd+F was causing it to toggle fullscreen mode, which is quite frustrating as you can imagine

The Yosemite-look thing has been fixed in the latest brackets-shell which is shipping with 1.5. very soon, however I think is that this is the first time of someone reporting Brackets not working at all on El Capitan.

Are others seeing this behavior? I don't have El Capitan yet so I can't test it myself.

I have El Capitan updated from Yosemite, and Brackets works for me.

Updated to El Capitan this morning. Brackets is hanging on start

For those having problems, have you tried clearing out the cache folder? (Backup the stuff before deleting them though).

I got it working by removing the cef_data folder, brackets.json and state.json

Clearing Cache didn't help.

I have tried to update Chrome today and with Chrome update, Brackets worked as well on El Capitan.

Closing as this issue seems to be fixed.
Workaround- Clear cache + Chrome Update.
Please feel free to reopen if needed.

I'm having the same problem as well.
El Capitan fresh install and Brackets won't start. Tried everything mentioned here but it also don't help. @Vlasterx, by any chance was the whole OS becoming non-responsive when you were having the issue with Brackets? For me, everything works fine until I try to run Brackets, and then non of the apps would work. It seems to be a bigger problem than just Brackets, definitely Apple has screwed something up, but just wanted to confirm whether you were getting the same behavior I'm getting right now.

@meGenius - It also happened to me just after upgrade, but I was unable to start anything related to Chrome or Chromium. Clearing cache didn't help, but I got an idea to uninstall both Brackets and Chrome, then downloaded new version of Chrome, which worked and then installed Brackets, which also worked. Try it as well and if you succeed, post it here as well for people with similar problems.

Well, @Vlasterx, I actually decided to reinstall the whole OS X thing. I couldn't use Adobe Illustrator as well, so I thought let's just get rid of this altogether. I reinstalled OS X 10.11 and now everything is fine. Note that so far I didn't try to install Chrome as my primary browser is always been FireFox and I install Chrome only for testing purposes. I'm not sure if installing Chrome will break Brackets again thus I'm not gonna do this for now.

me preguta siempre por abrir el programa como si fuese la primera vez, cada vez q lo abro

Aptana ist better!

Hello, I have the same problems. Starting Brackets leaves me with grey window and the app stucks, even CMD-Q doesn't work anymore.
I tried all mentioned here but nothing works.
Has anyone a solution?

Running OS X 10.11.2El Capitan and facing no problems with Brackets.
A clean install of Brackets should help fix the problem.

I have the same problem with Brackets 1.12 on macOS Hight Sierra. It just stopped working. I did't do updates and did't install new applications. I have a gray screen and the menu responds only to closing  and minimizing the window. I was trying to remove the new version of the old version, clean up the cache and even updated the system again. Still not working. Please, help.

Sry for reply after all those years. Came by (google search) with same problem and just wanted to leave my fix: in my case there was a problem with the local folder synced (Sourcetree) at the moment i started the update. Had same issues as described here. Workaround was to close Sourcetree and all open folders. After i've done that, brackets started as supposed.


Error: t: expand table, got nil

Steps to reproduce
Use sumneko_lua language server, put the cursor on sign_define of the following lua code, execute lua vim.lsp.buf.signature_help():
vim.fn.sign_define("LspDiagnosticsSignError", { text = "E" })

Expected behavior
No errors occur.
Actual behavior

Additional information
Put the cursor between the parentheses and execute lua vim.lsp.buf.signature_help(), no  errors occur.

The fix has solved the problem, thanks.


Fixed "IsAbstract" for interfaces, traits, enums and final classes

Fixed \Arkitect\Expression\ForClasses\IsAbstract because:

interfaces can not be abstract
traits can not be abstract
enums can not be abstract
final classes can not be abstract

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.19%. Comparing base (b78ecce) to head (00dd134).
Report is 3 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##               main     #425   +/-   ##
=========================================
  Coverage     94.19%   94.19%
- Complexity      582      586    +4
=========================================
  Files            69       69
  Lines          1533     1534    +1
=========================================
+ Hits           1444     1445    +1
  Misses           89       89

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Hi @sebastianstucke87 can you please fix red checks?

Note that with this change, IsAbstract will now identify interface, trait, enum and final all as abstract classes.

interfaces can not be abstract

I don't believe a rule is needed for this, because this is something PHP already disallows.
At best, I believe the rule could become...
- if ($theClass->isAbstract() || $theClass->isInterface() || $theClass->isTrait() || $theClass->isEnum()
-            || $theClass->isFinal()) {
+ if ($theClass->isAbstract() && !$theClass->isInterface() && !$theClass->isTrait() && !$theClass->isEnum()
+            && !$theClass->isFinal()) {

... but it should be redundant because if ::isAbstract() is true then all other states must be false.


Running three D430 on Coral Dev Board

Required Info

Camera Model
{ D400 }

Firmware Version
<IP_ADDRESS>

Operating System & Version
Mendel Linux

Kernel Version (Linux Only)
4.14.98-imx

Platform
Coral Dev Board

SDK Version
2.45.0

Language
Python

Segment
Robotics

Issue Description
Hey everybody,
I'm not sure if this is the right place but I thought maybe somebody had the same problem or some idea. I'm currently trying to connect three D430 + D4 vision boards to a coral dev board through one USB-C hub. Unfortunately I can't make it work as I either receive a segmentation fault (most of the times), a "Frame did not arrive within 5000" (sometimes) or it can't even find all cameras (disconnect solves that).
I've created a little test script to check if the cameras work:
import pyrealsense2 as rs
import numpy as np
import argparse
import cv2
import time

def parse_inputs():
    parser = argparse.ArgumentParser()
    parser.add_argument('--width',
                        default=848,
                        type=int,
                        help='width of stream')
    parser.add_argument('--height',
                        default=480,
                        type=int,
                        help='height of stream')
    parser.add_argument('--frame_rate',
                        default=30,
                        type=int,
                        help='frame rate of stream')
    parser.add_argument('--frames',
                        default=100,
                        type=int,
                        help='number of frames for the streaming test')

    return parser.parse_args()

def find_cameras(ctx):
    cameras = []
    devices = ctx.devices

    for dev in devices:
        name = dev.get_info(rs.camera_info.name)
        serial_number = dev.get_info(rs.camera_info.serial_number)

        cameras.append({'name': name, 'serial_number': serial_number})

    return cameras

def init_cameras(cameras, width, height, frame_rate):
    pipelines = {}

    for cam in cameras:
        serial_number = cam['serial_number']
        name = cam['name']

        pipe = rs.pipeline()
        cfg = rs.config()
        cfg.enable_device(serial_number)

        cfg.enable_stream(rs.stream.infrared,
                          width=width,
                          height=height,
                          format=rs.format.y8,
                          framerate=frame_rate)

        cfg.enable_stream(rs.stream.depth,
                          width=width,
                          height=height,
                          format=rs.format.z16,
                          framerate=frame_rate)

        profile = pipe.start(cfg)
        depth_scale = (
                profile.get_device().first_depth_sensor().get_depth_scale())

        cam['depth_scale'] = depth_scale

        pipelines[serial_number] = {'pipe': pipe, 'camera': cam}

    return pipelines

def test_stream(pipelines, nr_frames):

    colorizer = rs.colorizer()

    durations = []

    for i in range(nr_frames):

        start_time = time.time()

        for serial_number, camera_data in pipelines.items():
            name = camera_data['camera']['name']
            pipe = camera_data['pipe']
            depth_scale = camera_data['camera']['depth_scale']

            frames = pipe.wait_for_frames()

            color_frame = frames.get_infrared_frame()

            depth_frame = frames.get_depth_frame()

            color = np.asanyarray(color_frame.get_data())
            color = cv2.cvtColor(color, cv2.COLOR_GRAY2RGB)

            depth_frame_color = np.asanyarray(
                colorizer.colorize(depth_frame).get_data())

            depth_frame = np.asanyarray(depth_frame.get_data())
            depth_frame = depth_frame * depth_scale

        end_time = time.time()

        durations.append(end_time - start_time)

    return 1/(sum(durations)/len(durations))

def main():
    args = parse_inputs()

    context = rs.context()

    cameras = find_cameras(context)
    print("Starting Intel Camera Test")
    print("-----------------------------------------------")

    print("Input Args")
    print(args)

    print("-----------------------------------------------")

    print(f"found {len(cameras)} camera(s)")
    print(f"camera details: {cameras}")

    pipelines = init_cameras(cameras, args.width, args.height, args.frame_rate)

    print(f"initialized {len(pipelines.keys())} camera(s)")

    print("-----------------------------------------------")

    print(f"Starting streaming test for {args.frames} frames")
    fps = test_stream(pipelines, args.frames)
    print("Finished streaming test")
    print(f"Average streaming FPS: {fps}")

if __name__ == "__main__":
    main()

The things that I've check so far:

Check USB-C hug: The USB-C Hub can handle the bandwidth and power as I can run the same script from my laptop without a problem.
Reduce resolution: I've tried to lower the resolution to 640x360 but that does not lead to any improvements unfortunately.
Lower frame-rate: Lowered it to 6 FPS but similar to reduced resolution.

I'm a bit lost now as I don't really know what to do to make it work. Unfortunately we have to run all cameras through one USB-C 3.0 port. Any ideas on what to try?

Quick thought: Could it be related to the build process? I'm building the library from source with the following flags:
cmake ../ -DBUILD_PYTHON_BINDINGS:bool=true -DFORCE_RSUSB_BACKEND:bool=true -DBUILD_WITH_CUDA:bool=false -DBUILD_GRAPHICAL_EXAMPLES:bool=false -DCMAKE_BUILD_TYPE=release

Hi @brunovollmer  I would recommend beginning investigation of the issue at the exotic Linux and kernel versions that the board is using.  As the board does not have Ubuntu or a commonly used kernel, there may be a conflict between those elements and librealsense.
Ordinarily you could test for this by using the -DFORCE_RSUSB_BACKEND:bool=true method that you applied, as this method is not dependent on Linux versions or kernel versions and does not require kernel patching.  An RSUSB build is suited to single-camera applications rather than multiple camera though.  Does the librealsense build work if only one D430 camera is attached to the Coral board?

Hey @MartyG-RealSense,
if one or two are connected it works fine when the -DFORCE_RSUSB_BACKEND:bool=true is activated. I tried it without and I get the following error now:

Traceback (most recent call last):
  File "scripts/test_cameras.py", line 187, in <module>
    main()
  File "scripts/test_cameras.py", line 174, in main
    pipelines = init_cameras(cameras, args.width, args.height, args.frame_rate)
  File "scripts/test_cameras.py", line 88, in init_cameras
    profile = pipe.start(cfg)
RuntimeError:
Failed to resolve the request:
	Format: Z16, width: 848, height: 480
	Format: Y8, width: 848, height: 480

Into:
	Formats:
	 Z16
	 Y8

And strangely it only detects two cameras.

Are all three cameras active simultaneously?  When using multiple cameras at the same time, the specification of the computing board that the cameras are being used with can have a bearing on how many cameras it will support.  For example, a Raspberry Pi or an original Up Board would be suited to one camera, whilst a more powerful Up Squared board could handle two cameras.  Whilst a 2018 Intel seminar suggested an Intel Core i7 processor for 4 cameras attached to the same computer.

Looking at the Failed to resolve the request error though, you might get that error if the camera connection was being identified as USB 2.1 and the FPS had been set at 15 or 30, as 848x480 would support 6 or 10 FPS in USB 2 mode.

They are connected through USB-3.0. Regarding the one question before: Yes they are supposed to run at the same time.

And the cameras are all attached to a USB hub on the USB 3 port of the Coral?

Yes

It's always the same that is not detected.

Do all three cameras have the same firmware version?

Yes. All have version: "<IP_ADDRESS>"

Are the serial numbers of the cameras being detected automatically or are you manually providing the serial numbers in the script?  If you are putting the serial numbers in the script as pre-programmed values, is the serial number of the camera that is never detected confirmed as correct?

I'm using this code snippet to detect the cameras:
def find_cameras(ctx):
    cameras = []
    devices = ctx.devices

    for dev in devices:
        name = dev.get_info(rs.camera_info.name)
        serial_number = dev.get_info(rs.camera_info.serial_number)

        cameras.append({'name': name, 'serial_number': serial_number})

    return cameras

It may be useful to test the cameras with a multiple camera Python project that a RealSense user contributed at the link below to determine whether the third-camera issue is occurring because of your script or because of the Coral board.
https://github.com/ivomarvan/samples_and_experiments/tree/master/Multiple_realsense_cameras

So the same script works on your laptop with the same hub, but the hub is connected to the laptop instead (suggesting that the code is fine and the hub is fine).  Is this correct please?

Yes that is correct!

Not if I compile librealsense without rusb support

There was a past case in which another Coral board user had the same experience with 'frame didn't arrive' errors even when using a powered USB hub and manually patching the kernel instead of using RSUSB.  There was not a clear solution at the end of that particlar case.
https://community.intel.com/t5/Items-with-no-label/What-kernel-patches-and-features-are-needed-to-run-Realsense/m-p/654379
Another Coral user in a later case who was using RSUSB posted a guide of advice for what had worked for them to resolve problems.
https://github.com/IntelRealSense/librealsense/issues/7646#issuecomment-717985404

I used #7646 to initially setup our system and it runs great with one or two cameras. My main problem is related to the fact that it won't work once a third camera is connected.

You could try swapping the USB cable of the third camera with another of the cameras to eliminate the possibility that the Coral board has a conflict with a particular USB cable (even though it works fine on the laptop).

So the version that was built without RUSB support does not seem to work at all on the dev board.
Problems are:

can't find all cameras no matter if i switch cables
for the cameras it finds it can't start the streams

The version with RUSB support still suffers from the mentioned problems above.

So the Coral cannot detect the third camera even if you use the lsusb Linux command when your application is not running to simply check whether the camera is detectable on its USB port?

That is the weird thing. It does find the cameras. Output of lsusb:
Bus 002 Device 007: ID 8086:0b4b Intel Corp.
Bus 002 Device 006: ID 8086:0ad4 Intel Corp.
Bus 002 Device 003: ID 8086:0ad4 Intel Corp.
Bus 002 Device 002: ID 2109:0815 VIA Labs, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:2815 VIA Labs, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It might be useful test to print the serial numbers of the detected cameras to ensure that one of the serial numbers is not being duplicated instead of its own unique serial being read.

Also, I checked the ID numbers from the lsusb list against the list of RealSense model ID numbers (PIDs).  They should all be D430 models, yes?  0ad4 (of which there are two) is D430, but 0b4b corresponds to D430i (an IMU-equipped model), which may be a mis-identification if it is definitely a D430 board.

No so one of them is an D430i that's true

Another thing I realized is that only connecting three but not using all of them leads to problem. So if I connect all three but only initialize two it won't work. I get more and more the feeling the problem is not related to the actual bandwidth but some USB connectivity issue of the coral dev board.

D430i is very rarely seen on these forums.  The few cases involving them typically involve a D435i camera whose internal RGB sensor is not being detected, causing the firmware to identify the camera as a D430i.
My understanding is that a difference between RealSense models that have an IMU and those that do not is that the IMU-equipped models are treated as HID devices.
https://github.com/IntelRealSense/librealsense/issues/3803
So if you only have 2 cameras connected and one of them is the one that usually does not work, that suggests that the problem is with simply having three cameras, not that there is a fault with a particular camera.

@MartyG-RealSense Do you think this problem could be solved by building the library without RUSB support and patching the kernel somehow?

Or is there any expert on that matter in the librealsense team that I could talk to?

You could try building the SDK from source with the V4L2 backend (no RSUSB) by using the CMake build flag -DFORCE_LIBUVC=OFF
Alternatively, as Mendel is apparently a lightweight derivative of Debian, i wonder whether the Debian package method of installing librealsense could work with Mendel instead of building from source code.
https://coral.googlesource.com/docs/+/refs/heads/master/ReadMe.md
https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md

Tried the built with -DFORCE_LIBUVC=off and had the same problems:

not all cameras are found anymore (can't find the d430i)
those cameras that are found cannot be initialized due to failed to resolve request (checked and librealsense recognizes them as usb 3.2)

Okay, thanks for the update.  Do you plan to try the Debian package method, please?

Oh yes, the packages at the distribution_linux.md page are for x86 / x64 processors.  I do apologize.  There are Debian packages at the Nvidia Jetson installation page that are designed for Arm, though you may encounter similar problems with using those with Mendel.
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_jetson.md

Hi @brunovollmer  Do you require further assistance with this case, please?  Thanks!

Hi @MartyG-RealSense. The current working solution is to run the three cameras over two cables which seems to work fine. From my further research it seems that the native mendel usb driver only supports yuv format which is not supported by the d430 cameras and if I built intelrealsense wiht RUSB support three cameras don't work. That's why I think we will stick with the two cable solution. But nevertheless if anybody has any idea how to make the RUSB version work we are more than open to ideas

Thanks very much @brunovollmer for the update about your success with a two-cable setup!
RSUSB has the limitation of being suited to single-camera applications rather than multi-camera (like patched kernel builds are), so it is difficult to see how that limitation could be circumvented.  You can find more information about this by visiting the comment linked to below and scrolling down to the section headed What are the advantages and disadvantages of using libuvc vs patched kernel modules?
https://github.com/IntelRealSense/librealsense/issues/5212#issuecomment-552184604

I've read this specific post earlier and do see your point. What just irritates me a bit is that everything works flawless with two cameras and I don't really see the reason at the moment why it would fail with three cameras.

I performed further research into multicam with RSUSB.  Apparently in subsequent months after the libuvc vs patched kernel information, a fix was added to the SDK in 2.35.2 to provide multicam support under RSUSB.  I knew improvements to multicam were added in 2.35.2 but had not realized that they also addressed RSUSB.
https://github.com/IntelRealSense/librealsense/issues/5828#issuecomment-642968201
https://github.com/IntelRealSense/librealsense/pull/6467
A RealSense user in https://github.com/IntelRealSense/librealsense/issues/5828#issuecomment-588208971 found that it was possible for them to use six cameras under RSUSB but they had to reduce resolution to do so.

hi @brunovollmer  Do you require further assistance with this case, please?  Thanks!

Hey @MartyG-RealSense. Sorry for the late reply. I was in holidays. Unfortunately did I already try to lower the resolution or frame rate. But the problem already appears when initializing.

It may be worth testing your cameras with the multiple_realsense_caeras.py multicam viewer project in the link below that a RealSense user created.  This would help to demonstrate whether there is something in your own project script that is affecting detection of all cameras.
https://github.com/ivomarvan/samples_and_experiments/tree/master/Multiple_realsense_cameras

Hi @brunovollmer  Do you require further assistance with this case, please?  Thanks!

I think so far I have not been able to make it work with only one hub. I might come back to this issue later but for now I will work on other things. Thanks for the help!

Thanks very much for the update, @brunovollmer - please do feel free to ask questions on this forum whenever you need to.  Good luck!


Touch Selection Color + New App Tag

Added two features :

Change the color of touch selection - from settings activity.
'NEW' is displayed on apps that were installed upto an hour ago. Changed model.App, created a new field saving installDate. This really helps find apps when you freshly install from playstore. Also added switch to remove this tag in the settings activity. TODO: In the next update, track openCount of each app and remove 'NEW' tag only after it is opened, and it was say installed upto 24 hours ago.

Hi @CreaRo,
I like the ideas here but I have a few comments / suggestions:

Changing the touch selection colour is a nice idea, but the touch selection needs to be the same colour as the overall colorAccent. It will most likely be difficult to change themes for different widgets, but if you can find a way I will definitely consider merging.

The new app tag is a neat idea. But I would prefer to try a more subtle design. I would love the type of design that iOS uses - a small dot (use colorAccent) to the left of the app name:

Please use hungarian notation for all member variables (eg. installDate -> mInstallDate) and put all Strings in strings.xml (eg. "NEW!")

Thanks!

Thanks for the suggestions, @nicholasrout!

The colorAccent (or any other theme defined color) can't be changed at runtime. There is a workaround solution though. Instead of using R.color.colorAccent everywhere, create another Theme.class in the util package and reference all colors from there. Would that be fine with you? I strongly suggest we add this, as some people may want to change the selection color because of their background!
Sure. The small dot really does look sleek! Since we're not displaying the app names in the zoomed out view, I've set the dots to the left bottom of the app icon. Let me know if that's fine. Also, I've added a database storing number of times each app is opened. Currently, its purpose is to remove the dot once a new app is opened. Also, this could later be used to sort apps by usage/frequency.

I've pushed the changes. Let me know.


Your environment

Software
Version(s)

redux-form
8.3.6

redux
4.0.5

react-redux
7.2.0

react
16.13.1

react-dom
16.13.1

node
v12.14.1

npm if using
6.13.4

yarn if using

flow if using

typescript if using

Browser
Chrome

Operating System
Mac 10.14.6

Steps to reproduce
I downloaded the Material UI example from here https://redux-form.com/8.3.0/examples/material-ui/
Then I updated all my packages (as my project has newer version of react and material UI).
Inspect with redux tools.
Enter text into a text field (e.g: firstName)
@@redux-form/START_ASYNC_VALIDATION is trigged every-time a new character is entered.
Here is a sandbox of the project https://codesandbox.io/s/redux-form-material-ui-updated-8sos2?file=/package.json:141-312
Expected behaviour
I expect that when I change values in the form (e.g type a new character into the firstName field) only the change action (@@redux-form/CHANGE) is run. Then async validation action (@@redux-form/START_ASYNC_VALIDATION) is run when I blur a field. This is how original demo behaves (https://redux-form.com/8.3.0/examples/material-ui/).
Actual behaviour
Action @@redux-form/START_ASYNC_VALIDATION is triggered every-time I change a field.
Any help greatly appreciated.
Thanks,
Simon

ah I found the property asyncBlurFields which I guess is new since the example?
export default reduxForm({
form: 'MaterialUiForm',
validate,
asyncValidate,
asyncBlurFields: ["email"],
})(MaterialUiForm);


0.15.0 Export issue - detectAllFaces missing

Looks like export failed.  Happy to test new version as needed.

Also, missing is detectSingleFace

Apparently an issue with export * notation picking up the entire directory instead of the index file. Not sure why some exports get lost this way though. Fix incoming...

Should be resolved in 0.15.1.


Using Jekyll's inbuilt sass/scss compiler

Jekyll comes with its own built-in sass/scss compiler. Which also combines multiple @import source files into one css file, and also minifies and compresses the css file. Github Pages has built-in support of this sass-compiler.
Is there a way to start using the Jekyll's scss compiler it instead recompiling the scss files using node.js and npm every time the stylesheets needs to be changed.
http://markdotto.com/2014/09/25/sass-and-jekyll/
https://jekyllrb.com/docs/assets/#sassscss

Yes and no. The theme could absolutely use Jekyll's built-in support for Sass and process main.scss that way, but there's a few tradeoffs.
The big one is I've decided to write the CSS without vendor prefixes and let tools like Autoprefixer handle them. It leaves you with cleaner code and is one less thing to maintain as browsers continue to evolve and update.
The problem is you either need a Jekyll plugin (not supported with GitHub Pages) to run the CSS through Autoprefixer or have an extra build step outside of Jekyll (what I've done) that does it for you.
If your site is targeting modern browsers than piping the CSS through Autoprefixer is probably not something you need to worry about. In that case you could easily reorganize the .scss partials into folders Jekyll looks for and configure Sass there.
I'm hoping that the Jekyll Assets plugin eventually gets whitelisted for GitHub Pages and then I can switch to that since it supports Autoprefixer... among other things.

Here's an example using Minimal Mistakes with the Jekyll Assets plugin Michael mentioned:
https://github.com/jhabdas/habd.as/
There're a few NPM deps in the manifest still, but none are required for dev. Note this asset pipeline is not as efficient as the Minimal Mistakes built-in default, but it does eliminate the need for multiple registries or even a Node env for that matter. Not GH Pages friendly.

I was off-topic, sorry!


Adds update option to plugin command

[ ] https://github.com/kubernetes/helm/issues/2385: Added update option to plugin command to update an existing plugin

Thanks and great job @sushilkm!


Out of no where latest commit close window on console open stops working

Out of no where the code stopped working for the window to close when console opens no code has been changed really strange bug

For security reasons I shall not say how to still open dev tools but now more ways have been blocked


NULL generations for different options

NULLs that are used to generate the results are only used with a single set of results. need to be able to access NULLs generated by different options to be able to compare different methods properly. this is also problematic in the UI where the results are generated using a single set of NULLs regardless of the options chosen

Not every option is affected equally by this. For instance geeq score factor is added after comparison with the NULLS while multifunctionality directly factors into the initial score, therefore effecting NULL distribution


Use storage package for Prometheus remote read

This PR converts the Prometheus remote read endpoint to use the storage package, rather than the InfluxQL query engine.
This results in a number of improvements in performance and efficiency.
The PR also fixes a bug in the storage package, where regex expressions were not being properly handled for storage requests.
Finally it adds some higher-level end-to-end tests in the tests package.

During a run of megacheck the following issues were discovered:
/tmp/245856118/src/github.com/influxdata/influxdb/prometheus/converters.go:285:6: func condFromMatchers is unused (U1000)

During a run of megacheck the following issues were discovered:
/tmp/841687576/src/github.com/influxdata/influxdb/prometheus/converters.go:285:6: func condFromMatchers is unused (U1000)

@stuartcarnie feedback addressed.


minute_step, round to the nearest time without remainder

First of all thank you for the great card!
Problem

Suggested feature / solution
Currently if I have for example 15:24 as a time and minute_step=15 in the config, if I press "ᐱ" button it will change time to 15:39, then to 15:54, 16:09, etc. Instead as an option I'd like to have it first changed to 15:30, then to to 15:45, 16:00, etc. So to have after each interaction minutes without remainder.
Additional context

I don't have a lot of time to work on the card for now, but like the idea.
In case anyone want's to give it a try and open a PR, here's how I would go about it briefly:

add an option round: true. Defaults to false.
pass option to TimeUnit
implement in TimeUnit's setValue


Get started / implement workspace-part

My User Story for the next sprint (21.6 - 1.7.):
As a developer I want to get started implementing the webapi. I want to use my previously created python-project to setup a webservice. In the next sprint I want to finish a usable Service for the workspace part of the api. It doesn't have to be production-ready but to be usable for the purpose of uploading, updating and fetching workspaces as bagits.
AC: A service which can be run and which is able to accept, update and deliver workspaces according to the webapi-spec.
Links:
Repo: https://github.com/joschrew/ocrd-webapi-implementation
API-Spec:
swagger:   https://app.swaggerhub.com/apis/kba/ocr-d_web_api/0.0.1
raw:           https://github.com/OCR-D/spec/blob/master/openapi.yml

I noticed that the webapi did not define an endpoint to download a workspace

There is though, GET /workspace/{workspace-id} will return a previously uploaded/registered workspace. Or do you mean something different?

GET /workspace/{workspace-id} (link: https://app.swaggerhub.com/apis/kba/ocr-d_web_api/0.0.1#/workspace/getWorkspaces) "only" returns id and static description no data (Unless I'm misunderstanding). So users can see if a workspace/it's id is available, not fetch the data of the workspace like images, mets etc.

Oh, right, there's the content negotiation missing. I would expect
curl -H Accept:application/json /workspace/{workspace-id}

to return the description but
curl -H Accept:application/vnd.ocrd+zip /workspace/{workspace-id}

to return the workspace itself. I'll have a look how that is modelled in OpenAPI


Only fullscreen?

There is only one problem with your library.
What if I just want to lock a specific ViewController with the ProgressHUD?
E.g.: If I have a TabBarController that I can navigate through the tabs.
Currently your library only supports showing in fullscreen mode, locking all the windows bellow it.
Do you think that supporting presentation in a ViewController based root would be a good idea?
If yes, I'm thinking about creating a pull request.
:)

@andersonlucasg3
Full screen is the current specification.
But I feel that a case like you should be considered.
I was planning to change code in the near future (After about one week).
Your suggestion would be considered then.
Are you okay with this ??

Yes, I'm ok with that.
I'll contribute if you're ok.
As soon as I can, I'll make a pull request adding support to ViewController based presentation.
Thanks.

Hey, @andersonlucasg3 !
KRProgressHUD ver.3.0 is available ;)
ShowOn(_ viewController:) method was Implemented.
(https://github.com/krimpedance/KRProgressHUD/blob/master/KRProgressHUD/Classes/KRProgressHUD.swift#L246)
I hope I can be of any help to you :)
Thanks.

@andersonlucasg3
This is closed because there is no response.


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


UI Testing Robolectric Issue

Error
When trying to do automated UI tests with Robolectric I get this error:
java.lang.IllegalAccessError: tried to access class kotlin.jvm.internal.DefaultConstructorMarker from class androidx.appcompat.widget.MaterialRecyclerViewPopupWindow$Companion
This is caused by MaterialRecyclerViewPopupWindow being in the androidx namespace so Robolectric does its bytecode magic on it.
Fix:
Don't put MaterialRecyclerViewPopupWindow in the androidx namespace.
Workaround:
Use a custom RobolectricTestRunner
 * https://github.com/robolectric/robolectric/issues/4340
 *
 * https://github.com/zawadz88/MaterialPopupMenu/blob/master/material-popup-menu/src/main/java/androidx/appcompat/widget/MaterialRecyclerViewPopupWindow.kt
 * MaterialRecyclerViewPopupWindow uses the androidx namespace, so Robolectric tries to instrument it, which doesn't turn out well.
 */
class CustomRobolectricTestRunner(testClass: Class<*>?, injector: Injector) : RobolectricTestRunner(testClass) {
    private var androidConfigurer: AndroidConfigurer = injector.getInstance(AndroidConfigurer::class.java)

    @Suppress("unused")
    constructor(testClass: Class<*>?): this(testClass, defaultInjector().build())

    override fun createClassLoaderConfig(method: FrameworkMethod?): InstrumentationConfiguration {
        val configuration: ConfigurationStrategy.Configuration = (method as RobolectricFrameworkMethod).configuration
        val config: Config = configuration.get(Config::class.java)

        val builder = Builder(super.createClassLoaderConfig(method))
        builder.doNotInstrumentClass("androidx.appcompat.widget.MaterialRecyclerViewPopupWindow\$Companion")
        androidConfigurer.configure(builder, interceptors)
        androidConfigurer.withConfig(builder, config)
        return builder.build()
    }
}

Thanks for submitting this issue and a workaround!
I'm not sure if I can move the package. If remember correctly it was needed to access some package-private resources.
I'll have a look if this can be fixed by other means though!

I didn't look into the details too much, other than "bytecode instrumentation magic".
But now that I'm thinking about it, all you might need to tweak the companion object a bit so the instrumentation works.

Hi @JamesRoome,
This should be now fixed in 4.1.0.
Thanks for reporting this and providing a lot of info to fix the issue!

Yes is works, happy to delete my CustomRobolectricTestRunner!
Thanks for the quick fix.


webpack bundling issue

See https://easyrtc.com/forums/viewthread/36/ for details.

Resolved at the forum.


Added other url's the game is played on

Tbh I kinda like that it isn't on these URLs as it makes it possible to go into it without disabling the script.

While it makes sense why one would like it, it could also provide trouble for others unfortunately.


Ensure existence of message fields in checksum specification

The parameters of a checksum specification should be verified. A checksum specification referring to non-existing message fields should be rejected.
Example
The following specification should be rejected, as Foo, Bar and Baz are not defined:
package Test is

   type Message is
      message
         Checksum : Opaque
            with Size => 8
            if Checksum'Valid_Checksum;
      end message with
         Checksum => (Checksum => (Foo'First .. Bar'Last, Baz));

end Test;

We do detect that Baz is undefined now:
Parsing test.rflx
Processing Test
test.rflx:9:59: model: error: unknown field "Baz" referenced in definition of checksum "Checksum"

However, Foo and Bar are still not detected.