is it possible to get questions answered here

I have a few startup type questions.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c07e57dc-526f-9479-4695-de7d8f06eb9a
Version Independent ID: 8226ed72-69b2-3c93-a931-218bd11cf9c8
Content: Get started with ASP.NET Core Blazor
Content Source: aspnetcore/blazor/get-started.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @FatWaterAudio ... We only work on the docs here. We don't have the staffing to provide product support. If you have a problem with a topic, a suggestion, or spot a topic bug, we work on those sorts of doc-related issues here.
It's best for general development questions for Blazor to ask on a support channel, such as ...

Stack Overflow
ASP.NET Core Slack
ASP.NET Gitter

... either the Slack or the Gitter chat rooms will instantly put you in touch with other devs who can answer general questions. If you need to show a lot of code or get into the weeds on a challenging problem, then SO is best, where you can post a full problem/question.
Having said that tho ...... if you feel that the topic isn't answering an obvious question ...... for sure it's best for you to say what you think we're missing. We use these issues for improvement ideas and suggestions. If the doc is fine tho and it's just a general development or product question, use a support channel :point_up:. I'll leave this open for a sec to give you a chance to respond.

Ok ... well said...thank you
My specific question is
In the tutorial at step 6 immediately after creating the app, the instruction says to press ctrl+F5 to start the app....
This doesn’t actually work.. I have noticed this behavior in other tutorials on other topics as well.
The environment seems not respond to F5 or ctrl+F5 until after one or more of the documents in the solution are opened... F5 or ctrl+F5 is not even populated as a choice in the Debug menu until a document is opened.
Soooo... the question becomes ... is that behavior expected and correct ?  .... or do I have an environment variable that needs attention.
I come from an embedded systems / bare metal background.
Thanks
Jim Collins
Fatwater Audio
425-212-8756 (text is best)
From: Luke Latham<EMAIL_ADDRESS>Sent: Monday, May 25, 2020 12:22 PM
To: dotnet/AspNetCore.Docs<EMAIL_ADDRESS>Cc: FatWaterAudio<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [dotnet/AspNetCore.Docs] is it possible to get questions answered here (#18474)
Hello @FatWaterAudio https://github.com/FatWaterAudio  ... We only work on the docs here. We don't have the staffing to provide product support. If you have a problem with a topic, a suggestion, or spot a topic bug, we work on those sorts of doc-related issues here.
It's best for general development questions for Blazor to ask on a support channel, such as ...

Stack Overflow https://stackoverflow.com/questions/tagged/blazor
ASP.NET Core Slack http://tattoocoder.com/aspnet-slack-sign-up/
ASP.NET Gitter https://gitter.im/aspnet/Blazor

... either the Slack or the Gitter chat rooms will instantly put you in touch with other devs who can answer general questions. If you need to show a lot of code or get into the weeds on a challenging problem, then SO is best, where you can post a full problem/question.
Having said that tho ...... if you feel that the topic isn't answering an obvious question ...... for sure it's best for you to say what you think we're missing. We use these issues for improvement ideas and suggestions. If the doc is fine tho and it's just a general development or product question, use a support channel ☝. I'll leave this open for a sec to give you a chance to respond.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/dotnet/AspNetCore.Docs/issues/18474#issuecomment-633691379 , or unsubscribe https://github.com/notifications/unsubscribe-auth/APWGDD7WXWMNEX7UZB2COY3RTLAOTANCNFSM4NJWPFGQ .

In Visual Studio's latest version, that should work. If you're using VS latest (version 16.6) and that gesture isn't working, then use the Report a Problem gesture within VS, which will open an internal issue for the VS team. They'll get back to you. Don't worry ... your issue doesn't vaporize into a black hole. :smile: If that doesn't lead to a resolution, then open an issue for the product unit at ...
https://github.com/dotnet/aspnetcore/issues

Hum 🤔 ... that is strange. I just checked here, and it doesn't work as you say. Let me get back to you.

Hummmmm ... normally when Build is checked in Build > Configuration Manger, it should build and run with F5.
Let me check the option for this. It may have changed in the settings.

Well ... you got me. I've been spending a lot of time in VS Code these days, so I didn't notice when this changed. Idk if it's a VS bug or there's a known gotcha on this.
Let's ping @mkArtakMSFT for a tip ... F5/Ctrl+F5 don't seem to immediately work when a project is immediately opened or created. As @FatWaterAudio points out here, we tell devs to create the new Blazor project and F5 to run it. I've tried it with an existing sample and new project created in VS.

I think I figured it out in my case ... my keyboard FN keys weren't active. When I activated them, F5 started to work. Check your keyboard @FatWaterAudio to see if that's the cause there.

Not sure what context you are speaking of with regard to inactive FN keys... they seem to work as expected  when I write C# ..where do I look to check this?
I am using VS2019 ..recently updated to latest. Win7 SP1. Plenty of mem/drive space/speed
Thanks
Jim Collins
Fatwater Audio
425-212-8756 (text is best)
From: Luke Latham<EMAIL_ADDRESS>Sent: Monday, May 25, 2020 1:11 PM
To: dotnet/AspNetCore.Docs<EMAIL_ADDRESS>Cc: FatWaterAudio<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [dotnet/AspNetCore.Docs] is it possible to get questions answered here (#18474)
I think I figured it out in my case ... my keyboard FN keys weren't active. When I activated them, F5 started to work. Check your keyboard @FatWaterAudio https://github.com/FatWaterAudio  to see if that's the cause there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/dotnet/AspNetCore.Docs/issues/18474#issuecomment-633703176 , or unsubscribe https://github.com/notifications/unsubscribe-auth/APWGDD3MR3RPH7WUVU4JOILRTLGDXANCNFSM4NJWPFGQ .

I use a Microsoft Ergonomic Keyboard, which has an F Lock FN lock key. I must have tapped it inadvertently recently and knocked out the normal use of my function keys.
If a similar problem doesn't explain your behavior there, I'm not sure what to suggest other than filing a report with the VS team using the Report a Problem feature within VS.

To be clear ... this issue only matters to me if it is systemic in some way.... i.e. environment variables etc...  that might affect other compile/debug/test activities... If this is simply a quirk in the IDE, I can easily work around it.
Thanks
Jim Collins
Fatwater Audio
425-212-8756 (text is best)
From: Luke Latham<EMAIL_ADDRESS>Sent: Monday, May 25, 2020 1:11 PM
To: dotnet/AspNetCore.Docs<EMAIL_ADDRESS>Cc: FatWaterAudio<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [dotnet/AspNetCore.Docs] is it possible to get questions answered here (#18474)
I think I figured it out in my case ... my keyboard FN keys weren't active. When I activated them, F5 started to work. Check your keyboard @FatWaterAudio https://github.com/FatWaterAudio  to see if that's the cause there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/dotnet/AspNetCore.Docs/issues/18474#issuecomment-633703176 , or unsubscribe https://github.com/notifications/unsubscribe-auth/APWGDD3MR3RPH7WUVU4JOILRTLGDXANCNFSM4NJWPFGQ .

I'm not aware of any env var that would cause F5 not to work ... or any other machine/local config.
This the kind of question that a chat ... Gitter or Slack ... might be able to help you sort out. Devs there have a great deal of experience, and you'll probably bump into someone who can help.

Outside of that, try the Report a Problem process. I bet the VS team support folks get this question regularly, and they might have a quick solution for you.

I'm going to close because this isn't actionable for the doc AFAICT. I think it's more of an IDE problem. This is the first time that I've seen feedback about F5 not working. I'll keep an :ear: open for more remarks in this vein. If it becomes a regular issue from devs, then we'll probably need to address it somehow.

K ... thx ... gonna try not to worry about.    As I said, its only a problem if it is a symptom of something larger
Thanks
Jim Collins
Fatwater Audio
425-212-8756 (text is best)
From: Luke Latham<EMAIL_ADDRESS>Sent: Monday, May 25, 2020 1:32 PM
To: dotnet/AspNetCore.Docs<EMAIL_ADDRESS>Cc: FatWaterAudio<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [dotnet/AspNetCore.Docs] is it possible to get questions answered here (#18474)
I'm going to close because this isn't actionable for the doc AFAICT. I think it's more of an IDE problem. This is the first time that I've seen feedback about F5 not working. I'll keep an 👂 open for more remarks in this vein. If it becomes a regular issue from devs, then we'll probably need to address it somehow.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/dotnet/AspNetCore.Docs/issues/18474#issuecomment-633708296 , or unsubscribe https://github.com/notifications/unsubscribe-auth/APWGDD3BBBABX6XV62575ITRTLIUJANCNFSM4NJWPFGQ .


Highlighting Values with Negative Numbers

First off thanks for the great plugin and all the work that goes into it.
My scenario/question:
There is a field with an existing negative number (for example -3). A user highlights that field and input3 the number 4. In my codepen setup the resulting output in the field is -4. Can anyone recommend the best way to make that behavior result in  an output that show just 4?
In other words, if a user highlights the whole field with a negative sign, and types over it, I'd like that negative sign to disappear. In my codepen I have two different fields that do this, one is a numeric and one is a decimal. They both behave the same way in this codepen, but I'd like to change them if possible to lose the minus sign when a user highlights and types over the field.

Add a link to a codepen, jsfiddle or other example page which shows the problem
https://codepen.io/BrendanLentz/pen/dygrVBj?editors=1010
OS: MacOS Ventura 13.3.1 (a)
Browser: Brave  1.50.114
Inputmask version: 5.0.7

@RobinHerbots
Thank you for your quick reply.
Yes I have tried with 5.0.8. I just switched the codepen above to using 5.0.8. When I use 5.0.8, it fixes the problem for the second field in the codepen, the one with this input mask:
$("#two").inputmask(   'decimal',   {     max: 5,     min: -5,     digits:1,     radixPoint: '.',     groupSeparator: ',',   });
but it doesn't have any effect on the first field, the one with this input mask:
$("#one").inputmask(   'numeric',   {     digits:0,     groupSeparator: ','   });
So, in other words, in version 5.0.8, field #two works but field #one doesn't. Whereas in version 5.0.7 they both don't work. Any thoughts on that?

@blentz100 ,
Have a try with 5.0.9-beta.21


fix: fix i18n import

Fix (restore) incorrect aliased import introduced by #580 which no longer imports translations in the domain error.
This leads the web-faucet (in prod) to display this (for almost all errors):

Codecov Report

Merging #589 (1665e0e) into main (62ac492) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #589   +/-   ##
=======================================
  Coverage   96.73%   96.73%
=======================================
  Files          74       74
  Lines         950      950
  Branches      146      146
=======================================
  Hits          919      919
  Misses         29       29
  Partials        2        2

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@lolottetheclash @fredericvilcot to be tested carrefully.

:tada: This PR is included in version 2.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add documentation for Whiteboard Sharing

Additional documentation explaining who can share a Whiteboard during one to one calls involving users from different tenants.

Learn Build status updates of commit 3da4e49:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/whiteboard/manage-sharing-organizations.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit bf13593:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/whiteboard/manage-sharing-organizations.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 2682098:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/whiteboard/manage-sharing-organizations.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@chuckedmonson can you route this to the correct person?

Learn Build status updates of commit 5e6b547:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/whiteboard/manage-sharing-organizations.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Encoding::UndefinedConversionError ("\x9F" from ASCII-8BIT to UTF-8):

Hi, I've got this error:
Encoding::UndefinedConversionError ("\x9F" from ASCII-8BIT to UTF-8):
				passbook = Passbook::PKPass.new json 				passbook.addFiles [Rails.root.join('certificates/icon.png'), Rails.root.join('certificates/icon@2x.png')] 				gen_pass = passbook.file 				send_file(gen_pass.path, type: 'application/vnd.apple.pkpass', disposition: 'attachment', filename: "pass.pkpass")
What I do wrong?
Rais 6, ruby 2.7.1

I'm encountering this too.  I think it's related to Ruby 2.7.1
This thread seems to diagnose it pretty thoroughly and links to a confirmed bug in Ruby 2.7.
I haven't found a resolution yet, but thought I'd leave those here for now.

https://github.com/clutch-holdings/passbook/commit/1a7c42b1f291fa39ff53e93be6c00c13362c97e7
^ this fork fixes that issue for me

Found somebody solution?

As mentioned above.
`module Passbook
class PKPass
 def file(options = {})
  options[:file_name] ||= 'pass.pkpass'
  temp_file = Tempfile.new(options[:file_name])
  temp_file.binmode
  temp_file.write self.stream.string
  temp_file.close
  temp_file
end

end
end`


Moving silx source to a src sub-folder

Since the silx folder is in the root of the repository, it is loaded first when running something from there.
We have the bootstrap.py script to mitigate that, but this is not enough under some circumstances, e.g., when using subprocess (see PR #3356 for example).
Keep the source in a src sub-directory would avoid that.
matplotlib is using this with a lib sub-directory (https://github.com/matplotlib/matplotlib/tree/master/lib)

Unless someone wants to discuss this, I want to do it right after next release.


[IC3 ACS Telco Messaging Front-end ] API Review

New API Review meeting has been requested.
Service Name: IC3 ACS Telco Messaging Front-end
Review Created By: Farhad Jabiyev
Review Date: 10/23/2024 09:00 AM PT
Release Plan:
PR:
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: Not Provided
Description: Transition of Opt Out Management API feature from Private to Public Preview stage. Api contains three endpoints:

Check - Check if recipient number is opted out from sender
Add - Opt out receiver nuber from sender
Remove - Opt in receiver number to sender

Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Meeting updated by Farhad Jabiyev
Service Name: IC3 ACS Telco Messaging Front-end
Review Created By: Farhad Jabiyev
Review Date: 11/06/2024 09:00 AM PT
Release Plan:
PR:
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: Not Provided
Description: Transition of Opt Out Management API feature from Private to Public Preview stage. Api contains three endpoints:

Check - Check if recipient number is opted out from sender
Add - Opt out receiver nuber from sender
Remove - Opt in receiver number to sender

Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Meeting updated by Pavlo Hermanov
Service Name: IC3 ACS Telco Messaging Front-end
Review Created By: Farhad Jabiyev
Review Date: 11/06/2024 09:00 AM PT
Release Plan:
PR: https://github.com/Azure/azure-rest-api-specs/pull/31359
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: Not Provided
Description: Transition of Opt Out Management API feature from Private to Public Preview stage. Api contains three endpoints:

Check - Check if recipient number is opted out from sender
Add - Opt out receiver nuber from sender
Remove - Opt in receiver number to sender

Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Meeting updated by Pavlo Hermanov
Service Name: IC3 ACS Telco Messaging Front-end
Review Created By: Farhad Jabiyev
Review Date: 11/06/2024 09:00 AM PT
Release Plan:
PR: https://github.com/Azure/azure-rest-api-specs/pull/31359
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: here
Description: Transition of Opt Out Management API feature from Private to Public Preview stage. Api contains three endpoints:

Check - Check if recipient number is opted out from sender
Add - Opt out receiver nuber from sender
Remove - Opt in receiver number to sender

Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Meeting updated by Pavlo Hermanov
Service Name: IC3 ACS Telco Messaging Front-end
Review Created By: Farhad Jabiyev
Review Date: 11/06/2024 09:00 AM PT
Release Plan:
PR: https://github.com/Azure/azure-rest-api-specs/pull/31359
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: here
Description: Transition of Opt Out Management API feature from Private to Public Preview stage. Api contains three endpoints:

Check - Check if recipient number is opted out from sender
Add - Opt out receiver nuber from sender
Remove - Opt in receiver number to sender

Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Notes from API Review 11/6/24

Should use PUT to create resources and not use the "action pattern" URL (with a ":")

This is actually like a "batch create"

Do you need the httpStatusCode if you have the errorMessage ?

This pattern already exists

Code should be a string that identifies the error.
Add errorMessage to the examples
Do you need "isOptOut" in the response elements of :remove ?
Should add error response "default" on all operations

This looks good for preview.


Alternative articles flavors

This PR implements two alternatives segmentation flavors:

article/light: Segment the document into header and body, and extract only title, authors, dois, and publication date if available, leaving everything else in the body.
article/light-ref: Segment the document into header, body and references, and extract only title, authors, dois, and publication date if available, leaving everything else in the body.

The article's body is then composed by two paragraphs:

The first paragraph contains leftover from the header, since the extraction may be sparse, this avoids to miss data
The second paragraph contains the full body

The PR #1151 was tested in this PR.

coverage: 40.572% (-0.2%) from 40.739%
when pulling f7cbf76201f7044a1d88be94799c40cb394c08f7 on feature/segmentation-light
into 01745c06b1cb836bdc560a08427d9530effb4148 on flavor.

I added end to end evaluation score for the new flavors: https://github.com/kermitt2/grobid/pull/1202/commits/c09aba1dea3c5a356736ce5b66597aec8b95f05f
The scores are limited to the title, authors, first authors for the header and citations (as in the grobid normal processing) to make sure we don't introduce regressions (we shouldn't but we never know) 🙂

here the updated documentation page with all the evaluation


Feature: Delete object button

Describe your feature or enhancement suggestion
A button to delete objects, such as operations and pathways
To be honest, I'm not sure why it isn't in the program.
Describe a concrete use case

nvm im blind

I'm actually working on an update where the delete button makes an appearance in the top toolbar :) In the meantime you can also press the delete or backspace key to remove a node.


Unexpected exception: list index out of range. (from logs)

Describe the bug
I just seen this log in the settings/logs suggesting to open an issue. Not sure how it affects the functionality of the integration.
To Reproduce
Steps to reproduce the behaviour:

Go to 'settings/system'
Click on 'logs'
Scroll down to 'the error'
See error

Expected behaviour
Not sure
Screenshots
See logs further down
Version
1.0.3 (latest)
Debug log
Enable debug logging by following the instructions here
Logger: custom_components.hildebrandglow_dcc.sensor
Source: custom_components/hildebrandglow_dcc/sensor.py:186
integration: Hildebrand Glow (DCC) ([documentation](https://github.com/HandyHat/ha-hildebrandglow-dcc), [issues](https://github.com/HandyHat/ha-hildebrandglow-dcc/issues))
First occurred: 1:05:10 AM (34 occurrences)
Last logged: 5:05:10 AM
Unexpected exception: list index out of range. Please open an issue

Traceback (most recent call last):
  File "/config/custom_components/hildebrandglow_dcc/sensor.py", line 186, in daily_data
    v = readings[0][1].value
        ~~~~~~~~^^^
IndexError: list index out of range

Additional context
Add any other context about the problem here.

I am getting the same error
2024-08-16 03:30:08.318 ERROR (MainThread) [custom_components.hildebrandglow_dcc.sensor] Unexpected exception: list index out of range. Please open an issue
Traceback (most recent call last):
File "/config/custom_components/hildebrandglow_dcc/sensor.py", line 183, in daily_data
return readings[0][1].value
~~~~~~~~^^^
IndexError: list index out of range

also seeing this:
Logger: custom_components.hildebrandglow_dcc.sensor
Source: custom_components/hildebrandglow_dcc/sensor.py:183
integration: Hildebrand Glow (DCC) (documentation, issues)
First occurred: 01:09:04 (31 occurrences)
Last logged: 03:39:04
Unexpected exception: list index out of range. Please open an issue
Traceback (most recent call last):
File "/config/custom_components/hildebrandglow_dcc/sensor.py", line 183, in daily_data
return readings[0][1].value
~~~~~~~~^^^
IndexError: list index out of range

same Traceback (most recent call last):
File "/config/custom_components/hildebrandglow_dcc/sensor.py", line 183, in daily_data
return readings[0][1].value
~~~~~~~~^^^
IndexError: list index out of range

I'm editing the sensor.py file.
try:
readings = await hass.async_add_executor_job(
resource.get_readings, t_from, t_to, "P1D", "sum", True
)
_LOGGER.debug("Successfully got daily usage for resource id %s", resource.id)
if readings and len(readings) > 0 and len(readings[0]) > 1:
return readings[0][1].value
else:
_LOGGER.warning("No readings available or unexpected data format")
except requests.Timeout as ex:
_LOGGER.error("Timeout: %s", ex)
except requests.exceptions.ConnectionError as ex:
_LOGGER.error("Cannot connect: %s", ex)
Can't use the RuntimeError exception from the library as it's not a subclass of Exception
except Exception as ex:  # pylint: disable=broad-except
if "Request failed" in str(ex):
_LOGGER.warning(
"Non-200 Status Code. The Glow API may be experiencing issues"
)
else:
_LOGGER.exception("Unexpected exception: %s. Please open an issue", ex)
return None
This code adds a check to ensure readings is not empty and has the expected structure before accessing its elements. This should prevent the IndexError from occurring.  Trying it now. Could be a work around

Also here...
Unexpected exception: list index out of range. Please open an issue
Traceback (most recent call last):
File "/config/custom_components/hildebrandglow_dcc/sensor.py", line 196, in daily_data
v = readings[0][1].value
~~~~~~~~^^^
IndexError: list index out of range

This error originated from a custom integration.
Logger: custom_components.hildebrandglow_dcc.sensor
Source: custom_components/hildebrandglow_dcc/sensor.py:183
integration: Hildebrand Glow (DCC) (documentation, issues)
First occurred: 01:06:43 (6 occurrences)
Last logged: 01:31:43
Unexpected exception: list index out of range. Please open an issue
Traceback (most recent call last):
File "/config/custom_components/hildebrandglow_dcc/sensor.py", line 183, in daily_data
return readings[0][1].value
~~~~~~~~^^^
IndexError: list index out of range

I'm getting the same error on two new installations of this integration (for two different GlowMarkt accounts).
Unsure if this error is the reason that I'm not seeing the same data being pulled through to HA as I'm seeing in the Bright App.

The solution is here, fixed it for me:
https://github.com/HandyHat/ha-hildebrandglow-dcc/issues/396#issuecomment-2038364754
Hope the mainainer can merge it.


"Disable Internet Explorer 11 as a standalone browser" Policy Setting Not Available in 20H2 ADMX

Good afternoon. The "Disable Internet Explorer 11 as a standalone browser" Policy setting is not available in 20H2 ADMX. I've downloaded and searched through the ADML file. However, it is present in the 21H1 ADMX hosted by MS.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b557e6ee-bb46-7b9c-108b-c78829c6d8b4
Version Independent ID: dd39c398-eb44-ab64-69ee-d860147072df
Content: Disable Internet Explorer 11
Content Source: edgeenterprise/edge-ie-disable-ie11.md
Product: microsoft-edge
GitHub Login: @dan-wesley
Microsoft Alias: shisub

@USCloud-EricWilborn Hi! For 20H2 machines, specific Windows Updates is required.  Please see our documentation for more info:  https://docs.microsoft.com/en-us/deployedge/edge-ie-disable-ie11#prerequisites
Let us know if you are still having an issue after updating.  Thanks!

Closing issue, there has been no reply.


fix: fully qualify pickup min/max datetimes

Languages like Golang can't deserialize the min/max datetime of a Pickup unless it is fully qualified. We fix this here.

This date gets overwritten locally by each CL anyway since it constantly needs to be incremented. Why don't we just remove it from the fixture altogether?

@nwithan8 because the fixtures must conform to the schema of the data in question. If we remove it, it will blow up in the same way as what this PR is fixing.


[META] Allow sponsoring?

Hi! I really like the approach that Bruno wants to go and I switched from Insomnia already as their software got really buggy with 8.X. and also because they are introducing all the forced sync functionalities.
Some companies have a way to sponsor open-source projects with GitHub sponsors. Maybe there would be some interest if this project would support it!

Hey @max-wittig !
Yes, I will open-up for Github Sponsors as well as Corporate Sponsors.
Too tied up at the moment with development.

@max-wittig https://github.com/sponsors/helloanoop
Would you like to close this issue?

@helloanoop  However, it is strange. We don't have sponsor button here

Even though we have the funding file setup correctly https://github.com/usebruno/bruno/blob/bc70bba0b614c8e190cd704f0e5893bfd9cd3198/.github/FUNDING.yml#L1

Thanks @azzamsa !
It appears to be a github issue

Closing this issue.
Sponsor link is: https://github.com/sponsors/helloanoop


Implement SimplePage and pages API endpoint

This adds a simple page model with 3 areas and markdown/callout info/callout alert components.
Published content can be accessed via API.
Note, this does not include:

API authentication
API endpoints for draft content

@teneightfive you can check it now ;-)


execute the required PHPUnit version in CI builds

:+1: thanks!

Oh, you were too fast. :/ I was just pushing a better commit message. :D

Anyway, for further reference: https://github.com/sebastianbergmann/phpunit/issues/1882#issuecomment-144650815

Ah didn't check the PR time (just woke up). I'm glad someone is pushing the versions up a notch.

It's not such a big deal. :)


Update error network response handling

Details:

handle fatal errors, non-200
207 multi-status, at least one error in the body
200, may have warnings in the body

New error format:
"errors" : [
   {
      "type": "namespacedErrorCode",
      "status": 503,
      "title": "The service is temporarily unable to serve this request. Please try again later."
    }
  ]

New warning format:
"warnings": [
    {
      "type": "namespacedErrorCode",
      "status": 200,
      "title": "A warning occurred while calling the service.",
      "report": {
        "cause": {
          "message": "Cannot read related id...",
          "code": 202
        }
      }
    }
  ]

Will pick this up and begin progress once https://github.com/adobe/aepsdk-edge-ios/pull/103 lands.

Part of https://github.com/adobe/aepsdk-edge-ios/issues/125

Part of https://github.com/adobe/aepsdk-edge-ios/issues/125


Added missing IsWBFluidEnabled Parameter

Added missing IsWBFluidEnabled Parameter from documentation to enable or disable Whiteboard per the Microsoft documentation
https://support.microsoft.com/en-us/office/enable-microsoft-whiteboard-on-onedrive-for-business-2fae9707-0c9b-42f8-a85f-9628b698ac82

Docs Build status updates of commit 452bdab:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a1d4f7f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@get-itips

Gentle reminder @get-itips

Gentle reminder @get-itips

Author @FaganSC  needs to apply suggestion

@FaganSC Gentle reminder. Please implement the suggested changes. Thanks

Docs Build status updates of commit abbf9fe:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit e37ae79:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@get-itips

@tiburd Please merge this PR. Thanks.

Docs Build status updates of commit d97c86c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


'oneOf' support

An implementation of 'oneOf' using generated deserializers.  This change is no where near complete, but it does show a way that support could be added for this operator.  Any input on this would be appreciated.
Current issues:

Annotators do not have access to the RuleFactory or current Schema.  These were added to the method for annotating fields.
Widens the responsibility of annotators, since code is being generated in the annotator now.
No support for objects.
No support for validating that value actually matches an option's schema.
What to do if none match?

This now works for string and integer with Jackson2 and Gson.

@joelittlejohn I am curios about your thoughts on this.  I am not happy with the way this is structured yet, but it does show that I am going to end up basically writing a validator to support oneOf.  Is this something the project wants to take on?

@ctrimble So far, I have been very, very reticent to implement (or get close to implementing) a validator as part of this project. It's not the goal of this project to validate data, only to help Java engineers create a structure that can hold their data with minimal fuss. JSR-303/349 was a quick win, but again, it's just annotations (more metadata for the Java world) and not a validator.
I'd be loathe to go down this route as I think validation is best handled by another library. Integrating this would also put a big burden on the maintenance of this project and make its goals less clear. It concerns me when libraries sprawl too far, and I think validation is best done at the raw JSON level by a schema validation library.
What do you think?

I am also hesitant to get validation involved in the project.  This is why I took pause after implementing these first two types.  It became clear that I would end up with a validator, or at least something close.
Unfortunately, validation is at the heart of the JSON Schema 'oneOf' key word.  Because of it's definition, binding and validation are linked.  It seems like users are running head long into this.  I have been avoiding it, but I will be forced to deal with it at some point.
I had considered trying to leverage the JSR-303/349, since this would bring some consistence to things.  After considering it, there were some real issues.  We need to validate before we bind, not the other way around.  Also, having to inject validators into the deserialization pipelines may make using the project to difficult.
As far as an external validation library goes, it will definitely need to work on the raw JSON form for both Gson and Jackson.  I am only aware of one option for Java, and that is fge's json-schema-validator.  That project is only draft 3 and seems to have stagnated.  Perhaps the correct thing to do is create a separate validator and leverage it from jsonschema2pojo.

As a stop gap, should a PR get created that just bails out to a generic type when a oneOf, anyOf or allOf is encountered?

I think exploring your stop-gap solution of using a 'generic' type is the best option. It may also make sense to this only in the limited cases where Jackson's polymorphic deserialization can be leveraged (i.e. the cases where some explicit indicator can be added to the JSON).

Closing since this is not the direction the project wants to go with oneOf support.

Just read the end of this discussion. Regarding validation - including that into the project would be a bonus as far as I'm concerned. But I see you point that it might extend the responsibilities too far - especially when dealing with several different deserializers.
If you look at protobufs, they are effectively doing both and a JSON system that behaves the same way is something I'd want available to me
fge's project is ok, but it's very large - it increased an Android app by about 2.7MB! It does support draft4 though - you might have missed than.
regarding oneOf, I agree that it really is tied up with validation - I'm becoming more tempted to suggest it is removed from draft v5. Almost exactly the same behaviour can be accomplished by using named properties for each of the schemas in your oneOf and also using maxProperties/minProperties = 1.
e.g.:
{
    oneOf : [
        $ref : schema1,
        $ref : schema2,
        $ref : schema3
    ]
}

becomes:
{
    properties:
    {
        firstThing: { $ref : schema1 },
        secondThing: { $ref : schema2 },
        thirdThing: { $ref : schema3 }
    },
    maxProperties : 1,
    minProperties : 1
}

This is actually how I would prefer it was equated to in this library, but it would again require validation.


dploy - git diff - bad object

Hi,
I have an error when I try to deploy my project :
dploy stage
Connecting to stage...
Checking revisions...
Checking diffs between [6c40f361380f9d0983ac24b71de0fd0369c50074] > [060c2eeaa06cbc12d38d771c4ad6498532bff937]
An error occurred when retrieving the 'git diff --name-status 6c40f361380f9d0983ac24b71de0fd0369c50074 060c2eeaa06cbc12d38d771c4ad6498532bff937' { [Error: Command failed: /bin/sh -c git diff --name-status 6c40f361380f9d0983ac24b71de0fd0369c50074 060c2eeaa06cbc12d38d771c4ad6498532bff937
fatal: bad object 6c40f361380f9d0983ac24b71de0fd0369c50074
]
  killed: false,
  code: 128,
  signal: null,
  cmd: '/bin/sh -c git diff --name-status 6c40f361380f9d0983ac24b71de0fd0369c50074 060c2eeaa06cbc12d38d771c4ad6498532bff937' }

If I remove the .rev on the server, it works correctly but tries to upload all the project again and I don't want that, I'd like to upload only modified files.
Anyone has a solution ?
Thanks a lot

Seems like when doing git push --force which drops the previous commit, this it will happen

Is there any solution fot this?


Windows Defender triggered by "Virus:Win32/Neshta.A" upon setup of Bulk Crap?

Once I installed this software, and it was doing its configuration, I got tons of microsoft defender warnings popping up on safe files:

From that, to a lot of my gaming *.exe files. Any idea why this program is triggering Defender? Other files include eg, GTA 5 exe launcher.

Don't want to bring bad news but looks like your PC is very infected, I suggest downloading and running MalwareBytes at the very least before using it for anything important. You might want to later change any passwords you entered while it was still infected too.
BCU looks at a lot of folders and files to build its application list. Windows Defender only scans files when they are accessed, so that's why it finds the viruses only after you run BCU. There's most likely even more of them that didn't get found yet.


Cross compile with custom engine.

This is a placeholder issue to track hover build and cross compile changes discussed in #128.
Proposal:
List of steps.

Add custom toolchain and target support.
Add support for build flags. (example: glfw gles2 and wayland tags)
Add local engine support, therefore providing own artifacts for the embedder.
Add sanity and error checking.
Refactor.
Probably add support for toolkits other then glfw or direct usage of FB, so it can run without a heavy x11 or wayland. (Note: This should be a different change, it's mentioned here to ensure it's known as it affects the build command. An idea would be to add a --driver flags, which tells the build which manager should be used (sdl, glfw, directfb or wayland etc..)

Proposed arguments
- target  <arch><sub>-<vendor>-<sys>-<abi>
Description: Describes the target as a triplet.
Format: The triple has the general format <arch><sub>-<vendor>-<sys>-<abi> where:

arch = x86_64, i386, arm, thumb, mips, etc.
sub = for ex. on ARM: v5, v6m, v7a, v7m, etc.
vendor = pc, apple, nvidia, ibm, etc.
sys = none, linux, win32, darwin, cuda, etc.
abi = eabi, gnu, android, macho, elf, etc.

Use case: Whenever the target triple is given it can describe the target system and the compiler/linker setup needed. Therefor adding ability to run it on any system.
(Disclaimer: It's up to the developer to make sure he is able to compile to the target and that target is a valid system for flutter to use. Eg: libdl, libpthread, librt, libm must be present for flutter engine.)
Example values: armv7-linux-gnueabi, armv7-linux-gnueabihf, x86_64-linux-eabi
Behavior: By default, if no other options given, it will translate the value given to GOOS, GOARCH, GOARM and validate it (not all permutations are valid), if the base set or host os does not support it should warn the user to specify the docker flag.
If the toolchain arguments is given, this will specify the gcc/g++ (might be clang or other compilers) to use.
An example would be:

/path/to/toolchain/bin/gcc is used when toolchain is provided but no target is set.
/path/to/toolchain/bin/${target}-gcc is used when toolchain and target is provided.

- toolchain  path/to/toolchain
Description: Describes the CC used by go.
Format: Absolute path.
Use case: Adding custom toolchains for custom target systems.
Example values: /opt/gcc-linaro-4.9.4-2017.01-x86_64_arm-linux-gnueabi
Behavior: By default it does set CC to a gcc/g++/clang etc found in path + /bin/gcc, if target is specified it would suffix the target triple to the gcc binary, as it would be  path + /bin/arm-linux-gnueabi-gcc, if the compiler is presented in the environment it might be skipped.
(Disclaimer: if the toolchain path is set, and it is desired to use a sysroot with it, it's up to the developer to either compile the toolchain with support for it, or set the compile flags with-sysroot)
- cflags/cxxflags
Description: Adds CFLAGS/CXXFLAGS to the compilation steps
Format: Any supported flags by the compiler.
Use case: It might be needed if the target needs custom flags, an example would be nacl which requires some flags to use, an other would be the runtime set or std set to use.
Example values: --sysroot=/path/to/sysroot --std=c90
Behavior: By default this should not be used, but custom targets might require this.
- ldflags
Description: Adds LDFLAGS to the linker steps
Format: Any supported flags by the linker.
Use case: It might be needed if the target needs custom flags, as an example setting a custom rpath, or for other use cases where the system would have example glfw already installed and the user would rather use that then the compiled one.
Example values: -rpath,/lib/
Behavior: By default this should not be used, but custom targets might require this.
- local-engine-path /engine/src
Description: Describes the path for the local engine setup for use.
Format: Absolute path.
Use case: When we want to target a custom target, it requires the flutter_engine to be built for that target as well. Therefore it can be linked to the binary.
Example values: /engine/src ${FLUTTER_ROOT}/../engine/src
Behavior: It would use the artifact from this directory, it comes with a pair arguments -local-engine to narrow down which build the user wants, since the flutter tool requires the engine built for the host (host_debug, host_debug_unopt, host_release, host_release_jit) to be present for bundling. It should point only to the engine src, by default as flutter/engine states it's a peer directory to flutter so we could assume that. Otherwise hover might have a new command to support the whole local engine setup. I'll write about it later in the discussion.
- local-engine host_debug_unopt
Description: Describes which artifact directory should be used.
Format: Sub path name for the out directory.
Use case: When we want to target a custom target, it requires the flutter_engine to be built for that target as well. Therefore it can be linked to the binary.
Example values: host_debug_unopt, linux_release_jit
Behavior: It should specify which artifact directory will be used, it contains all the necessary files for the embedder to work. Including the engine library, icu and headers.
- tags gles2
Description: As far as we depend on glfw at the moment it's not mandatory to have this. It would allow to specify build tags for later use cases.
Format: Space separated strings.
Use case: An example use case is when we would like to target a system with specific requirements, like it should use OpenGL ES 2, and use Wayland. This is for now a specific mention for glfw. SDL does this at runtime. Custom drivers might need it or not.
Example values: gles3 wayland
Behavior: It propagates down build tags for dependencies and for our own ones.
- output /path/to/output
Description: A path for the output binary and assets to land in.
Format: Absolute or relative path.
Use case: Since we might have different targets, we might need a different output directory. And don't want to pollute the working dir.
Example values: ../custom-output
Behavior: It should create the given folder and copy the necessary assets (icu, engine) to it, and build the flutter bundle to this folder. This folder should be used as a cache, if it already contains the engine or icu, it matches the artifact directory given then we should not call any copy or recompile step. Recompile steps might be involved when the local engine changes.
Proposed sanity checks.

We should make sure that only supported variant are passed and let the user know about the miss-configuration. An example would be requesting an host_debug engine, and giving a target triple which does not reflect the host (Running on linux, and using mingw).
We should make sure that the requested engine exists in the engine path. And let the user know if it's not.
We should make sure all arguments involving path exists.
We should make sure that the local engine matches the flutter tool, so it would run with the built flutter assets. Flutter tool has an engine version described in bin/internal/engine.version.
We should notify the user if he is missing any dependencies (example: for glfw x11 packages)

Proposed refactor on high level.

We should make sure to have an option to use multiply flutter tools at the same time, therefor i would propose to move all external command calls to it's own.
We should make sure to separate the actual build steps and arguments parsing, allowing further arguments to added without touching the actual build function. As there might be arguments which does not require any build steps, more like changing environment variables for the current session etc.
We should make sure that all the cross compile steps are separated from the main build. As one might extend on the other it should not be taken as a single step.
We should make sure these are callable within code and not just CLI commands.

Other notes:

Checking out the flutter engine might be a hassle for newcomers, we could add this step for them,
we could use depot tools, and flutter tool to create an unmanaged local engine, with the revision specified by the tool, making sure about version parity.

I'll extend this in the following days and rewrite some parts, so this is a subject to change by itself and by other inputs from you.

@jld3103 Can you please make sure that this is labeled correctly?
And could you please do a quick review? I'll revisit this after i have some free time.

I'd like to know more about how docker is involved in cross-compiling and how the current targets on desktop are defined then. Do you also plan to make targets like RPI "standard" (so that you don't have to specify the arguments every time)? Also adding something like a "profiles" config file for custom defined targets would be good.
Moving from the current hover structure to the one you're proposing is a lot of effort, but it will be wortwhile.

Lets separate these for a moment, i'll call it "hover compile".
So running hover build, without any arguments is a sure host compilation requiring no cross compile steps, but it will go trough the hover compile, so we can support local engines.
Calling "hover build linux/arm" would load the "linux/arm" preset, a good list of those are fyne-cross, as they are simple and need only small adjustments (like linux/arm should be split, to armhf and armel). Which would then call hover compile with the preset containing all the above arguments defined.
So flow wise:

run hover build as normal

if first argument (OS atm) is given, that would be a preset.

if that preset differs from the host we would do the docker step
* within docker we call hover compile with the preset arguments
else we build on the host machine with preset

else if target is provided and arguments fulfill a hover compile

then we call hover compile on host

else build default host
Sorry for the style, its md. :)

We can probably create a "build config / presets" with predefined setups, so the users can easily target what they want, and decide if they want to use their host machine or docker to do the build.
That would involve presets for osx, windows, rpi, linux in general and many others later on or custom ones. See the list below for more examples.
As for the docker part goes, it would not involve go-cross, and instead we would provide a base image, and run hover within the docker container :)
by a preset list we could go for something like fyne:
darwin/amd64
darwin/386
linux/amd64
linux/386
linux/arm
linux/armhf
linux/arm64
windows/amd64
windows/386
android/amd64
android/386
android/arm
android/arm64
And could add wasm with more effort to that list, or nacl, tizen etc :)
So an overview:

Create a base docker image, just like fyne did
Based on the selected preset, install the compiler and dependencies in an intermediate build container
Within docker, invoke hover compile (hover compile --target thiscomesfrompreset --cflags ... --ldflags ... etc)

Then hover compile could be used with docker (and for CI) and for dev on host machine as well without docker.
So command wise:
hover build presetName would invoke the docker build only if the host is not as the same as the target, and docker build would invoke hover compile :) (but of course inside a container)
I hope it makes sense.

Regarding the docker base image @GeertJohan created an PR for a new docker approach that uses a single image that we define

Also I created a PR for AOT that currently only works on linux, but would be needed for your changes I guess.

Also I created a PR for AOT that currently only works on linux, but would be needed for your changes I guess.

Nice!

Regarding the docker base image @GeertJohan created an PR for a new docker approach that uses a single image that we define

Nice! ill add some comments regarding deps so it could be used by this!

Also we are currently using https://github.com/flutter-rs/engine-builds as libflutter_engine sources for AOT (and also could use them for JIT). Adding our predefined targets to the automatic builds would be nice for other users, because instead of compiling the engine themselves they could download the prebuilt engines.

Also we are currently using https://github.com/flutter-rs/engine-builds as libflutter_engine sources for AOT (and also could use them for JIT). Adding our predefined targets to the automatic builds would be nice for other users, because instead of compiling the engine themselves they could download the prebuilt engines.

For the default set thats fine, i dont want to change the setup for that, just adding the option for users to use local engine :)
non of these arguments should be required, regarding prebuilts, these should be ok.
If the user does not define a local engine path and name then these artifacts should be used.
The flow os somewhat similiar to flutter build bundle.

@fourscience any news? Since you last wrote a lot of things have changed in hover. We finally have better Docker cross-compiling support. I'd recommend to make yourself familiar with the new hover features to further discuss the progress on this issue.

@fourscience any news? Since you last wrote a lot of things have changed in hover. We finally have better Docker cross-compiling support. I'd recommend to make yourself familiar with the new hover features to further discuss the progress on this issue.

Hello, yes and no :)
Still making progress in my free time, i saw the changes and actually following up on them, im able to cross compile with a followig setup:

compiled clang to armv7 eabi (sf)
compiled binutils to armv7 eabi
compiled flutter engine for armv7 eabi

same works for darwin
using the cc above with the engine for go
works fine, what i was struggeling with is glfw go has somewhat a restricted protocol setup :)
ill post an update when its somewhat stable
for the following targets:

rpi
webos
tizen

Im still on quite far of having a feature ready setup, at the moment what is left to do besides the basic setup is a more proper configuration for linker, compiler, assembler steps and a pr against go glfw :)
Feel free to close this issue if needed as the changes takes place in hover anyway.
A quick note on this is more of an advanced use case simplified down, as this can be achived by hand, so its somewhat targets developers who intend to use go and flutter on devices which are not common targets like the rpi or smart devices.
I hope when its done it can be used within the docker setup as well with an ease.
I can share a gist if needed with the changes i made for an early preview if anyone interested in it.

Could you upload your code on a new branch in your hover fork? Then we could see the progress as you work on it. And this issue should be kept open.

I am not a specific developer, so I am not familiar with the specific implementation methods.
But now Flutter has some third-party arm implementations
For example, this
https://github.com/sony/flutter-elinux
What I want to ask is, is it possible to combine this project and complete the construction of arm/arm64
Or refer to its implementation direction.
This project should appear after all the above conclusions


feat(docs): Add more info on how to structure the TypedData

Description
When signing data using Ethers.js signer._signTypedData function, we SHOULD not include the EIP712Domain property inside types object as Ethers.js already do it for us. Doing so will cause an exception when calling the signTypedData/ signTypedDataAsync functions.
// bad code

const domain = {
  // ...props
} as const
const types = {
  EIP712Domain: [
      { name: 'name', type: 'string' },
      { name: 'version', type: 'string' }
  ],
  VerifyMessage: [
    { name: 'message', type: 'string' },
    { name: 'wallet', type: 'address' }
  ]
} as const
const value = {
  // ...props
} as const

// good code

const domain = {
  // ...props
} as const
const types = {
  VerifyMessage: [
    { name: 'message', type: 'string' },
    { name: 'wallet', type: 'address' }
  ]
} as const
const value = {
  // ...props
} as const

I think this information should be explicitly included in the docs.
Additional Information

[x] I read the contributing docs (if this is your first contribution)

Your ENS/address: N/A

Thoughts on just omitting the EIP712Domain attribute internally before we send it over to ethers? Means that we still stick to EIP-712 as well as still being interoperable w/ recoverTypedSignature and other utils.

@jxom Since I don't know Wagmi's internals, I'm not sure what the best approach would be. I think the notice in the documentation should be enough.

Closing in favor of #1437. Thanks for the PR!


Some fixes for issue #325

https://github.com/lk-geimfari/mimesis/issues/325#issuecomment-352356998

@duckyou I'll do a full review a little later and if it's okay - I'll merge it.
P.S Don't forget to add yourself to CONTRIBUTORS.md.

@duckyou So, there one big problem. I think that testing all methods with seed is too painful and hard to maintain. We cant write two different tests for one method every time when we create new methods. I suggest removing this tests. We can test seed only using BaseProvider, i.e in file test_base.py if seed works for it, it will mean that seed works for all subclasses of BaseProvider:
@pytest.fixture
def seeded_base():
    return BaseProvider(seed=42)

def test_base_with_seed(seeded_base):
    result = seeded_base.random.randint(1, 10)
    assert result == 2

What should be done: Remove all the tests which were added and replace them with the code above.

@duckyou You are probably already tired of making corrections, but we must support the simplicity of the project and its tests. If you do not want to do this, then I understand you and I will do it myself. Thanks!

@lk-geimfari

@duckyou So, there one big problem. I think that testing all methods with seed is too painful and hard to maintain. We cant write two different tests for one method every time when we create new methods. I suggest removing this tests. We can test seed only using BaseProvider.

I partly agree. Two different tests for one method is awful design... my bad =(
But write tests only for BaseProvider also bad decision. Heres eg:
https://github.com/lk-geimfari/mimesis/pull/327/commits/53e19b8db4eda89d7c595dbc568b9566243ec2f1#diff-fb2e53700ab7e63642efe387f905686a
    def words(self, quantity: int = 5) -> list:
        # Here is issue... some times normal words returnes in random order
        words = self._data['words'].get('normal')
        # Heres fix... when seed seted, its sorted words
        if self.seed:
            words = sorted(words)
        words_list = [self.random.choice(words) for _ in range(quantity)]
        return words_list

IMHO Seed tests should be for each method. I recommend merge seed tests with its basic.

@duckyou So, the situation with the previous PR was repeated here (not without my help). I'll create a new branch and applied your changes in this branch, but partially to better understanding what is happens.

@duckyou I'll do it tomorrow, but for now, we'll leave it as it at that. Do not change anything, please.

This PR was merged partially, as I said in our discussion.


[Installation]: System missing some CUDA libraries/not linked properly?

Your current environment
The output of `python collect_env.py`

Traceback (most recent call last):
  File "/home/shxjames/llm-eval/collect_env.py", line 15, in <module>
    from vllm.envs import environment_variables
  File "/home/shxjames/.conda/envs/inference/lib/python3.10/site-packages/vllm/__init__.py", line 3, in <module>
    from vllm.engine.arg_utils import AsyncEngineArgs, EngineArgs
  File "/home/shxjames/.conda/envs/inference/lib/python3.10/site-packages/vllm/engine/arg_utils.py", line 8, in <module>
    import torch
  File "/home/shxjames/.conda/envs/inference/lib/python3.10/site-packages/torch/__init__.py", line 367, in <module>
    from torch._C import *  # noqa: F403
ImportError: /home/shxjames/.conda/envs/inference/lib/python3.10/site-packages/torch/lib/../../nvidia/cusparse/lib/libcusparse.so.12: undefined symbol: __nvJitLinkComplete_12_4, version libnvJitLink.so.12

How you are installing vllm
conda create -n inference python=3.10 -y
conda activate inference
pip install vllm

Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

Same exact error when importing vllm library.

Your machine has cuda runtime < 12.4 and torch 2.5 uses 12.4 bindings by default. Just run the following to install vllm with the 12.1 torch wheels:
pip install vllm --extra-index-url https://download.pytorch.org/whl/cu121


Refactor dataprep multimedia2text

Description
Refactor dataprep multimedia2text

audio2text is duplicated with asr
video2audio is simple, can be moved to the preparation stage in the example DocSum
reduce the number of microservices to save resources
use ffmpeg to handle faster video2audio operation (also leverage Gaudi acceleration in the future)

Issues
na
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[x] Breaking change (fix or feature that would break existing design and interface)
[ ] Others (enhancement, documentation, validation, etc.)

Dependencies
na
Tests
na

Hello @MSCetin37, we need to refactor the multimedia2text component and the relevant example DocSum. Firstly thanks for your previous contribution of multimedia2text. After rechecking your code, we find that the audio2text is mostly duplicated with the existing ASR component and the video2audio can be replaced with a simple ffmpeg command of the conversion from video to audio. By rechecking DocSum, the only example that requires this multimedia2text functionality, we find that we can basically refactor the logics simply like following:
    def add_remote_service(self):
        asr = MicroService(
            name="asr",
            host=ASR_SERVICE_HOST_IP,
            port=ASR_SERVICE_PORT,
            endpoint="/v1/audio/transcriptions",
            use_remote_service=True,
            service_type=ServiceType.ASR,
        )

        llm = MicroService(
            name="llm",
            host=LLM_SERVICE_HOST_IP,
            port=LLM_SERVICE_PORT,
            endpoint="/v1/chat/docsum",
            use_remote_service=True,
            service_type=ServiceType.LLM,
        )

        self.megaservice.add(asr).add(llm)
        self.megaservice.flow_to(asr, llm)

    async def handle_request(self, request: Request, files: List[UploadFile] = File(default=None)):
### 1. if file is audio, do the megaservice.schedule
### 2. if file is video, do a simple 'ffmpeg -i input_video.mp4 -q:a 0 -map a input_video.mp3', and do the megaservice.schedule
### 3. if file is text, skip the ASR node in the runtime graph, and do megaservice.schedule

This will have following advantages:

remove the duplicate part of audio2text
move the video2audio to the preparation stage in the example DocSum
reduce the number of microservices to save resources
use ffmpeg to handle faster video2audio operation (also leverage Gaudi acceleration in the future)

I will later open a PR for this on the GenAIExample side, and if @MSCetin37 you have any suggestions, please don't hesitate to tell me!

Here is the relevant refactor PR https://github.com/opea-project/GenAIExamples/pull/1286 in examples.

Thanks for letting me know regarding the next phase of implementation. I have a few concerns:
> * Remove the duplicate part of audio2text

The response of the ASR does not align with the input of the LLM service. That was the reason why we implemented the audio2text service, which rearranges the response of the Whisper service so the results can be used as input to the LLM service. You might need to implement this logic inside the async function.

> * Move the video2audio to the preparation stage in the example DocSum

Video2audio is a simple service and might not require a dedicated service. However, we were planning to use this service for other examples as well, such as the MultiModal Q&A example.

My overall thoughts are that implementing a service (similar to multimedia2text) that can convert any data domain to a targeted domain will simplify and expand the scope of the implementations in OPEA.
For example:

Video to audio
Audio to text
Text to audio (speech)
PDF/doc to audio (speech)
etc.

Hi @MSCetin37 ,

The response of the ASR does not align with the input of the LLM service. That was the reason why we implemented the audio2text service, which rearranges the response of the Whisper service so the results can be used as input to the LLM service. You might need to implement this logic inside the async function or multimedia2text service.

Yes as you may notice, we leverage the align_input in megaservice to align the inputs. https://github.com/opea-project/GenAIExamples/blob/main/DocSum/docsum.py#L35 is an example.

Video2audio is a simple service and might not require a dedicated service. However, we were planning to use this service for other examples as well, such as the MultiModal Q&A example.

Sure however I think video2audio is super lightweight and can be easily replaced with ffmpeg -i input_video.mp4 -q:a 0 -map a input_video.mp3. Also separate it out as a standalone microservice does not really improve the pipeline (it does not need to be scaled-out), but just increase the latency and occupy hardware resources. In https://github.com/opea-project/GenAIExamples/pull/1286/files#diff-53767fc53b41e36c885b4416f3bbedebedae4f26be0ce616668ef368818fa3eeR47 I just replace the original functionalities with the very simple implementation.

My overall thoughts are that implementing a service (similar to multimedia2text) that can convert any data domain to a targeted domain will simplify and expand the scope of the implementations in OPEA.

I agree with you if what you mean is to add a multimedia2text component, which serves like a wrapper (or controller) to access existing whisper(asr)/speecht5(tts)/video2audio(local ffmpeg or moviepy conversion) etc, even other multimedia related functionalities. And I think it would be good for the future MultiModal Q&A. The name can also not to be exactly "multimedia2text", but something else (multimediaprocessing?).
Currently there are some refactoring work that I have to do this week. So do you agree we just keep it simple now? The hard requirements is that dataprep should not contain audio2text and video2audio. I will do the change based on our current design and later I will sync with you about adding a new component "multimedia2text" (the scope and its name), following the new controller https://github.com/opea-project/GenAIComps/blob/refactor_comps/comps/cores/common/component.py#L11 logics. Do you think this is reasonable?

Sounds good to me.


How do I debug 400 errors?

Summary
Currently Amplitude  in my project returns 400 errors and the only way I know about this is because I have Sentry set up, but the Amplitude SDK does not print or provide any useful info about the errors. I tried setting logLevel: .DEBUG but it didn't change anything.
How do I get some meaningful debug info like http responses from Amplitude so I can handle them?

Hi @DataGreed - we're planning on improving logging in a future release, but I've improved some of the logging in http client so you can at least debug any issues you're seeing. Please try branch https://github.com/amplitude/Amplitude-Swift/tree/AMP-109939-improve-http-logging, or wait for a release in a few days.

This was released in 1.9.3


Create GitHub issue and pull request templates

Currently we don't GitHub issue and pull request templates. It would be great to add them to help Delta users report issues and contribute code.
Template examples:

https://github.com/apache/spark/blob/master/.github/PULL_REQUEST_TEMPLATE
https://github.com/netty/netty/tree/4.1/.github
https://github.com/line/armeria/blob/master/.github/PULL_REQUEST_TEMPLATE.md

@zsxwing
Is it possible to help out with this issue? I am still a beginner.

@zsxwing
Okay thank you for the guidance! Let me get to it.

@zsxwing
I have done research on a few pull request templates. Please share with me your thoughts on this PR. You can find my pull request in this PR. In the meantime, I'll work on the issue template.
Reference:

https://gitlab.com/autowarefoundation/autoware.auto/AutowareAuto/-/merge_requests/1346#notes-for-reviewer
https://github.com/autowarefoundation/autoware.universe/blob/tier4/proposal/.github/PULL_REQUEST_TEMPLATE.md?fbclid=IwAR3QTvDiHb88yT_UqQmf5z7aiOQNaudPi1Sh-p4zrefs6yvjbqw8OFKbL4o
https://github.com/line/armeria/blob/master/.github/PULL_REQUEST_TEMPLATE.md
https://github.com/netty/netty/blob/4.1/.github/ISSUE_TEMPLATE.md
https://github.com/apache/spark/blob/master/.github/PULL_REQUEST_TEMPLATE


use fPIC so crossguid can be added to another library

Will this work on windows? Maybe should use the cmake syntax instead?
set_property(TARGET crossguid PROPERTY POSITION_INDEPENDENT_CODE ON)

I can't test this change on other platforms but if there is an alternative that preserves compatibility and allows the library to link with another library that would be perfect.


Invalid props.style key NativeBase

node, npm, react-native, react and native-base version
"native-base": "^2.7.2",
"react": "16.4.2",
"react-native": "0.56.0",
Actual behaviour
When I am trying to use "Content" component I'm getting a error:

Code
  render () {
    return (
      <Content/>
    )
  }

Info

Is the bug present in both iOS and Android or in any one of them?
I've checked only on Android.

I couldn't reproduce it via initialed project too. But, my project has the problem after updating RN and others packages. I'll try to move my project in new initialed project. If I found out something I'll let you know.

I'm also getting this error in iOS and Android. Not had chance to investigate it yet.

@mpcarr can you try ChillkroeteTTS's comment https://github.com/GeekyAnts/NativeBase/issues/2157#issuecomment-413144027

Closing this tomorrow in case of no response

Didn't work for me

I removed node modules, changed to v2.7.1 in package.json, installed and warnings went away. Then upgraded back to 2.7.2. Currently no invalid prop warnings.

no solution worked for me ....

same issue here, changed to v2.7.1 and still have this issue!

this issue also happened to me on v2.7.0 when using react-navigation

I'm having the same issue, tried to downgrade to v2.7.1 but warning won't go away.

I am also receiving this error. On version 2.7.2

I cannot reproduce this issue. So whoever facing this issue, could put it on snack or github, I can then look into this
Also try try installing node_modules again by clearing lock files, cache etc

I also got this error on v2.7.2 and v2.7.1 even I tried to remove node_modules and did npm install again on v.2.7.1 already.

this error appears on win cli thanks to react-native 0.56 :|

@SupriyaKalghatgi  - I was playing with an example react-native app and saw this warning. Here's a link to my fork where I see the issue: https://github.com/dpwilhelmsen/react-native-shop-ui. I haven't had the opportunity to narrow it down yet but hopefully it'll let you reproduce the issue.

still having this issue

Not sure if I'm getting the same issue, but basically I have
      <Text style={editMode && {opacity: 1}}>dfdfd</Text>

This gives me that same error I think it's due to the "opacity" on the Text.
However, if I switch to react native Text, no error....


fix incorrect usage of emoji/table.json without aliases

There is a bug introduced in commit 7f033d33fea4f6361d1905c9368c2e984dde2a50. When using emoji/table.json, you have to consider emoji/aliases.json as well, otherwise you'll get such an error in many cases when a user tries to reference an emoji by alias:
TypeError: Cannot read property 'image' of undefined
    at Object.exports.buildEmoji (/opt/nodebb/node_modules/nodebb-plugin-emoji/build/lib/parse.js:61:15)
    at parse (/opt/nodebb/node_modules/nodebb-plugin-reactions/library.js:14:21)

This PR adds correct usage of aliases based on this similar code in nodebb-plugin-emoji.
It is tested and deployed in production on this forum.

Thanks @artch


Support for frame-ancestors

🌱 Feature Request
Is your feature request related to a problem? Please describe.
A clear and concise description of what you want and what your use case is.
I'm looking to set the CSP frame-ancestors header: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors
as such:
Content-Security-Policy: frame-ancestors 'self' https://www.example.org;

Describe the solution you'd like
A clear and concise description of what you want to happen.
I would like to be able to set in the configuration a key value such as...
frameAncestors: "'self' https://www.example.org"

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I'm currently doing this...
    headers: async () => [
      {
        source: '/(.*)',
        headers: [
          ...createSecureHeaders(),
          {
            key: 'Content-Security-Policy',
            value: "frame-ancestors 'self' *.liveperson.net;",
          },
        ]
      },
    ],

Documentation, Adoption, Migration Strategy
If you can, explain how users will be able to use this and how it might be documented. Maybe a mock-up?
Additional context
Add any other context or screenshots about the feature request here.

[ ] I've tried to find similar issues and pull requests
[x] I would like to work on this feature 💪🏻

Sorry if it's premature but I've raised a PR as #46

This will be released v2.2.0.
#41 #46


OnBeforeAction and OnAfterAction not working

Hi,
I've made a page extension for page 5725 Nonstock Item Card.
On the page extension I've added the code below to modify the Create Item action.
This is not working.
If I try the same with the Substitutions action it does work.
The difference is that the Substitutions action as a RunObject specified and the Create Item Action has a OnAction trigger.
Is this a bug?
       modify("&Create Item")         {             trigger OnBeforeAction();             begin                 Message('Before');             end;             trigger OnAfterAction();             begin                 Message('after');             end;         }

The server does not support it for now. See #942.


Modify image fetching to reduce instance start time

Recorded operation fetch image takes 1-2 secs due to internet access. This could be avoided since most users don't need (or want) the latest nightly build.
Many options, but first thought is:
A flag to specify "download latest" (ie. current behaviour), and default behaviour is to use currently cached image.

I think this is effectively what labels have become. You can add a label to your one true version, and then not download unless you really want to. This is how CI images work now.


Bug in filtering when using OR and grouping expressions with parentheses

Hi Meilisearch,
I found a bug when filtering using OR  while i am grouping expressions with parentheses.
When i have a OR in my options query it looks to that OR and not any more to the other AND filters.
See my screenshot with the query and the filters:
Search on: 'test'
Options: [filters] => "branche" = "32" AND ("gender" = "male" OR "gender" = "female")
)
Result found:
 Array
                (
                    [id] => 1
                    [firstname] => Test name
                    [middlename] =>
                    [lastname] => Lastname test
                    [gender] => female
                    [branche] => 39
)

Se the result above. Branche 39 shouldend be in the result.
I also find out that it does not matter where my OR is. This bug is also shown when i put the OR in the begin of the query.

I'm looking into it


SVG opacity conflicts with attributify opacity=""

SVG can use opacity="0.7" means opacity: 70%.
It also will parsed by unocss as opacity: 0.007 means opacity: 0.7%.
<svg class="waves" viewBox="0 24 150 28" preserveAspectRatio="none" shape-rendering="auto">
  <defs>
    <path id="gentle-wave" d="M-160 44c30 0 58-18 88-18s 58 18 88 18 58-18 88-18 58 18 88 18 v44h-352z" fill="var(--yun-c-cloud)" />
  </defs>
  <g class="parallax">
    <use xlink:href="#gentle-wave" x="48" y="0" opacity="0.7" />
    <use xlink:href="#gentle-wave" x="48" y="7" />
  </g>
</svg>

I also encountered some false positives in SVGs
Playground
In the playground above, it extracts some margins from path's d attribute and fill attributes.
fill and opacity issues can be fixed temporarily by adding those attributes to ignoreAttributes:
presetAttributify({ignoreAttributes: ['placeholder', 'fill', 'opacity']})

But this will ignore these attributes in other places too, not just SVGs. And d attribute issue is still there.
In my opinion, we should have some special handling for SVGs.
fill and opacity issues can be fixed here:
https://github.com/unocss/unocss/blob/507303bfb5f1f5280eeda265c712875bf1c31f56/packages/preset-attributify/src/extractor.ts#L23
d issue can be fixed here:
https://github.com/unocss/unocss/blob/507303bfb5f1f5280eeda265c712875bf1c31f56/packages/core/src/extractors/split.ts#L8
My suggested solution is to remove these attributes from the code using regex.

Not sure if this comment (still) applies here: https://github.com/unocss/unocss/issues/205#issuecomment-985330309

Not sure if this comment (still) applies here: #205 (comment)

Thanks. It's a good idea to add namespaces to avoid confusion between unocss and svg attributes.
Unfortunately, this does not prevent svg's inherent properties from being parsed by unocss.
As @sibbng says, we should remove unocss parsing of svg attributes.
But regular expression is really hard for me.


Error when there is a non-image file in LevelSprite folder.

[2019-07-03 00:15:10.856] [Log] [debug] <Path> Loading resource at : Workspace/teddy/Sprites/LevelSprites/.DS_Store
Failed to load image "Workspace/teddy/Sprites/LevelSprites/.DS_Store". Reason: Image not of any known type, or corrupt
<<Error>>[ObEngine.System.Path.CantFindResource]@obe::System::Path::loadResource : Can't find Resource at Sprites/LevelSprites/.DS_Store
libc++abi.dylib: terminating with uncaught exception of type std::runtime_error: <<Error>>[ObEngine.System.Path.CantFindResource]@obe::System::Path::loadResource : Can't find Resource at Sprites/LevelSprites/.DS_Store

Fixed in https://github.com/Sygmei/ObEngine/commit/0be74b76e7951bb5bbfac2b97d5d4e75a46b0d0f


feat: Restake deactivated gauge warnings and modal (WIP)

Description
Alerts warning users about being staked into a deactivated pool gauge. Also, a modal which guides them to 1. Unstake 2. Stake in preferential gauge.
Type of change

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

How should this be tested?
TBC
Visual context
TBC
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have requested at least 2 reviews (If the PR is significant enough, use best judgement here)
[ ] I have commented my code where relevant, particularly in hard-to-understand areas
[ ] If package-lock.json has changes, it was intentional.
[ ] The base of this PR is master if hotfix, develop if not

Outdated


Tutorial updates

Updated version of the airbnb tutorial with missing code and commands. I think all the code in the tutorial should be working now. I added comments to the ssg manual edit file, to make it clearer which lines were added.

@Olajumoke01 is looking good: I just made some minor suggestions. Also, if you still have them, it would be nice to add the complete config.yaml and airbnb_generators.py files to the tutorial.

@Olajumoke01 is looking good: I just made some minor suggestions. Also, if you still have them, it would be nice to add the complete config.yaml and airbnb_generators.py files to the tutorial.

Hey Carlos, Do you mean add them near to the end of the tutorial as an example or as separate files somewhere?

@Olajumoke01 is looking good: I just made some minor suggestions. Also, if you still have them, it would be nice to add the complete config.yaml and airbnb_generators.py files to the tutorial.

Hey @cptanalatrist, Do you mean add them near to the end of the tutorial as an example or as separate files somewhere?

@Olajumoke01 is looking good: I just made some minor suggestions. Also, if you still have them, it would be nice to add the complete config.yaml and airbnb_generators.py files to the tutorial.

Hey @cptanalatrist, Do you mean add them near to the end of the tutorial as an example or as separate files somewhere?

Maybe you can add the files to the airbnb folder, and later add a paragraph at the end of the tutorial that goes: ``The complete files generated as part of this tutorial are available at this location.

only one thing:

[ ] move pre-commit dep from an extra to the dev group


Request: offer context menu on folders too, and not just on files

As the title says.
It's easier to apply it on the folder of the drawables, instead of finding which files are the newest.

Has been fixed in 3.5.5


Question - capturing SYSPRINT to a permanent PDS member

We have some post-build processing that relies on the assembler and linkedit listing to be stored in their own PDS members.
I do not want to change the current store of the complete SYSPRINT in HFS but I also want to capture the SYSPRINT from the assembly step and send it to ${hlq}.asmout(${member}) and capture the SYSPRINT from the linkedit step and send it to ${hlq}.linkout(${member})
It does not look like copytoPDS will allow me to copy a z/os temp file to a z/OS dataset so adding a copytoPDS in each step will not work. If I add a copytoPDS after the copytoHFS in each step I will get the appended listing
I am open to all ideas.
thanks

Hi @rsjrny ,
You don't need to consider to upload the sysprint again. You only need to change the current temporary allocations to a "real" dataset.
Here is a sample for this:
https://github.com/IBM/dbb-zappbuild/compare/develop...dennis-behm:dbb-zappbuild:storeListinginDataset?expand=1

Thanks @dennis-behm,
just what the doctor ordered


Stuck with personnal data

When using simple_parser.py and filepath,x1,y1,x2,y2,class_name on each line of a file correctly, the train script get stuck at "Starting training, epoch 1/50".
Note that I changed these two lines:
train_samples_per_epoch = 2000 -> len(train_imgs)
nb_val_samples = 500 -> len(val_imgs)
Do you have any idea why this might occur? Any special format required on the images (no different width height among images or anything else) ?

I get the exact same thing on gpu. On cpu the code works fine. There must bet something else. I'm actually thinking is due to some of the arguments in the fit_generator. For instance, the queue or the nb_worker.

Hi,
Thanks for the report. Looking through the code, it seems like this can happen if the objects are very different from the size of the anchors. I'm currently refactoring the entire generator procedure which should fix the issue, and bring the results more in line with the faster-RCNN algorithm.
There is no restrictions on image size. Images are resized to have their smallest side have 600 pixels. However, very small objects cannot be detected (the ROI pooling operates on a layer that has a stride of 16 pixels).
I should have an update out during the week.

@yhenon thanks a lot for the update

@yhenon will this work with images that are 32x32 or 128x128? Also should one use Keras 2.0 or 1.xx verision with this. I personally have not made the leap to 2.0 yet due to all the little annoying syntax changes since I am currently in the middle of some projects.

@pGit1 it works with keras 1.x.x on cpu. As for the image sizes I highly doubt it. It uses resnet50 as model so you need images of size no smaller than 197x197.

I'm going to go ahead and close this since the issue is old. I've pushed an update that should fix things. It also monitors the performance of both the RPN and the classifier, so you can get an idea of where things fail.


Updates to Google Sheet

As reviewed in 05-July-2022 TWG call:

removed section value of 'sequencing' from agriculture | lib_layout
removed section column from packages sheet
food-farm environment | prod_label_claims (and ???): removed blank cell that nudged MIxS  and GH issue off to right
food-animal and animal feed|samp_transport_cont was erroneously ID'ed MIXS:0000755. Corrected to as MIXS:0001230-

@turbomam these all appear to be things that have been done already, please confirm that is the case, if so we can close this ticket.


AWX server needs to be moved before March 16th

A per Slack message from Ed at Equinix, our awx.adoptopenjdk.net server is on hardware that will be decomissioned  on March 16th, so we need a plan to move this over to another server.

We could either attempt a migration, or set up something from scratch. At the moment I am unable to provision new x64 machines through the Equinix portal to be able to set up a replacement, which is what Equinix had suggested. I am talking to Ed to see how we can move this forward. We do still have the old ansible.adoptopenjdk.net server which we could upgrade and replace with a new version.

Issue with project creation in our Account at Equinix raised with Equinix support.

New machine obtained and set up (required Equinix support to generate a new "Project" separate from the one we had)
Machine has been set up as per the previous one with one except - the github team login is not working so at the moment we can only log in with a locally defined user. That can be resolved later :-)
@Haroon-Khel will be using the new server to finalise #1910 for the new MacInCloud servers added in https://github.com/adoptium/infrastructure/pull/2494 :-)


[Testing] add apihub testing

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

Comparison is base (81fbbad) 61.83% compared to head (a76ead8) 61.83%.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #188   +/-   ##
========================================
  Coverage    61.83%   61.83%
========================================
  Files           56       56
  Lines         2780     2780
========================================
  Hits          1719     1719
  Misses        1061     1061

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


Status of node-token-validation?

Core Library
MSAL Node (@azure/msal-node)
Core Library Version
1.17.3
Wrapper Library
Not Applicable
Wrapper Library Version
NA
Public or Confidential Client?
Confidential
Description
I note https://github.com/AzureAD/microsoft-authentication-library-for-js/pull/5921 but am unsure of its implications.
We are currently using passport-azure-ad and have been waiting for node-token-validation to release before migrating. (i.e. in a similar position to the OP in this thread https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/4816, our own previous issue on this https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/3939 )
Could you confirm the status of node-token-validation please?
MSAL Configuration
No response
Relevant Code Snippets
No response
Identity Provider
Azure AD / MSA
Source
External (Customer)

@EmLauber Can you help here? @DevRCRun We have an alternative solution being built for token validation, hence we did stopped work on node-token-validation.  I will have @EmLauber update the status here.

Tagging in @jmprieur @jennyf19 for node token validation status.

bump

const jwt = require('jsonwebtoken');
const jwksClient = require("jwks-rsa");

app.use('/protected-endpoints*', async (req, res) => {

	const authHeader = req.headers.authorization;
	if (!authHeader) return res.sendStatus(401);
	const token = authHeader.split(' ')[1];

	try {

		const getSigningKey = async (header) => {
			return new Promise((resolve, reject) => {
				const client = jwksClient({
					jwksUri: `https://login.microsoftonline.com/${process.env.API_TENANTID}/discovery/v2.0/keys`,
				});

				client.getSigningKey(header.kid, (err, key) => {
					if (err) {
						reject(err);
					} else {
						const signingKey = key.publicKey || key.rsaPublicKey;
						resolve(signingKey);
					}
				});
			});
		};

		const decodedToken = jwt.decode(token, { complete: true });
		const header = decodedToken.header;
		const signingKey = await getSigningKey(header);
		const decoded = jwt.verify(token, signingKey);
		req.authInfo = decoded;

	} catch (err) {
		logger.error({error: err});
		res.sendStatus(401);
	}

});

What about this approach for validating and decoding tokens with node? The API needs a role or scope from the decoded token to proceed with the request.

@jmprieur Please let us know what library we should use for the new Node.js API projects to implement access token validation for authorization with Azure AD.

bump, this needs a real solution or at least a basic example of how to do it ourselves safely as right now we are just guessing

What is the status on providing a mechanism for token validation in this library? If it's not going to happen at all, I need to know that so my team can spend the time to figure out safely validating tokens ourselves. If it's going to happen soon, I need to know that so my team doesn't waste that time. I see that "passport-azure-ad" is recommended in the docs, but it is archived and no longer getting security updates, so I don't feel comfortable using it.
I thought that "@msal/node-token-validation" was a thing because it appeared in the online documentation until very recently, but now those docs are 404 and even the code has been removed from the repo.
This es extra frustrating because looking through all of the linked issues on this topic, it seems to have been a known issue since 2021, and the only thing worse than spending the time rolling our own token validation is going to be discovering that you have released a version with token validation after we have built our own.

@samschurter. We want to provide a node SDK validating tokens before June 2024. We don't have a good solution until.
I would not recommend validating your tokens yourselves, as there are a lot of things you could get wrong.
cc: @jennyf19

I ran my code example again (which came from looking at MSAL code) and it seems to serve a need of validating and decoding tokens.
I'm now looking for feedback from your team, along with potential educational guidance. Especially now that we're aware that the goal is to provide a solution before June 2024.
What are the issues with using jsonwebtoken to validate and decode tokens generated by MSAL clients?
Our API has a need to process requests based on scopes and/or roles from the token.

@jmprieur Thanks for coming back with the target date. The fact that we shouldn't do it ourselves in an ideal world was what prompted this thread and the ones that preceded it. I too had previously gone through the samples to get an idea of what might be necessary if we were to do it ourselves for an interim period.
Due to the suggested timescale we're now looking at what other modules might aid a suitable verification. I know auth0 have / sponsor a number of openid modules...
As @egm9078 has already asked, could you let us know what the problem has been using jsonwebtoken / jose / jwks-rsa etc? Do you see general problems with these implementations or is it more the integration with MSAL? If there is some sort of general problem you see with the way things are being done by those modules, such that you intend to roll your own, it'd be useful to open that up for discussion.

Is there any update on this?

npm WARN deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

The passport-azure-ad npm package was just deprecated here, and through that I was able to find this repo and this issue.
Also curious what options Azure B2C customers have for token validation in Node.js.

We have updated the deprecation notice of passport-azure-ad to now point to https://github.com/AzureAD/passport-azure-ad?tab=readme-ov-file#node-js-validation-replacement-for-passportjs. We are aware of the interest in a supported node token validation offering but don't yet have something available.

We want to provide a node SDK validating tokens before June 2024. We don't have a good solution until. I would not recommend validating your tokens yourselves, as there are a lot of things you could get wrong.

@jmprieur it's now June 2024; where do things stand here?

And again I find myself with another task where I'm refreshing my memory on protecting a NodeJS API with Entra.  I find myself on the sample https://github.com/Azure-Samples/ms-identity-javascript-tutorial/tree/main/3-Authorization-II/1-call-api and see ... passport.
I recall this issue, come and have a read of https://github.com/AzureAD/microsoft-identity-web/discussions/2405 to which I was not subscribed and see there has been little progress visible to us on the outside.
There appear at this point to be three separate issues:

Deprecating a module before a replacement is available.
Updating samples to reflect that they / elements of them are now deprecated. I realise with the size of the MS documentation estate that this is quite the labour, but it is exactly this size and complexity that makes it important to do.
Managing expectations. The question around third party modules has now been asked three times in this thread by three separate people. The latest post in the discussion is a solution using these modules. The lack of official response creates a vacuum.

You're making it really hard for those of us who try to suggest to junior developers to use official solutions / documentation until they have the expertise and the time to validate those of third parties.


Glayout TODO tasks

[ ] Include a More Extensive Header for Glayout Compiled Files
[ ] Review and enhance the content in the markdown files located in the rag_data folder.
[ ] Ensure all convo-related files are located in the components folder within the flow directory.
[ ] Include comprehensive comments throughout compiled code.

@chetanyagoyal @srpathen @arldai

Task 1 is being handled by #321


clearing the transcript when ‘next’ or ‘次’ has been said

https://github.com/okonomichiyaki/wanikani-voice-input/commit/fc6e415eb19131bd0ba9d06a90a02fdb942a172a


Adds --as-service flag for custom run commands

Can be used to disable the auto-naming and lack of port binding that
occurs by default when specifying a custom command.

:+1:


Separate pip installs

Looking for feedback on this approach. I haven't modified the PexPackager.package() yet. If you're ok with this approach I'm happy to modify the PexPackager as well.

Codecov Report
Base: 99.83% // Head: 99.79% // Decreases project coverage by -0.05% :warning:

Coverage data is based on head (cfcca71) compared to base (91bd2e8).
Patch coverage: 90.90% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
- Coverage   99.83%   99.79%   -0.05%
==========================================
  Files          13       13
  Lines        2421     2427       +6
==========================================
+ Hits         2417     2422       +5
- Misses          4        5       +1

Impacted Files
Coverage Δ

src/pickley/package.py
99.15% <80.00%> (-0.42%)
:arrow_down:

src/pickley/cli.py
99.43% <100.00%> (+<0.01%)
:arrow_up:

tests/test_ops.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Ship it! It's nice and simple, love it :)

I revved to minor version.


Creating groups on the fly

Hello,
The plugin is creating group on the fly even if i set share-if-unconfigured: true
So it totally nulify the option.
To be sure it wasnt a problem in my worlds.yml, i deleted it to get a fresh one.
So even if my worlds.yml is valid and i have share-if-unconfigured: true, the plugin keep creating me a new world for each new world i visit with multiverse.
Creating a new group on the fly for 'Santa_Hill'. Please double check your worlds.yml file configuration!
I am using spigot 1.13.2 and PWI perworldinventory-kt-2.2.1
Thanks

Could you post here your worlds'yml file contents?
And the groups are still created because PWI still saves the player's inventory on teleport. If for some reason down the road someone wants to switch that option, or the options relating to GameModes, we then still have all the data we need to handle everything.