CloudFlare and flexible SSL

Hi,
Have you by any chance tested your new SSL support with a combination of a self-signed certificate on the server and cloud flare set up with full (not strict) SSL?

No. I didn't check that. I hope simply changing the SSL config to "full" it'll work.

I can confirm that a self-signed certificate uploaded using mup works perfectly well with ClouFlare's "Full SSL" mode.

Awesome.
On 2015 පෙබ 16, සඳුදා at ප.ව. 7.09 timothyarmes<EMAIL_ADDRESS>wrote:

Closed #263 https://github.com/arunoda/meteor-up/issues/263.
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/263#event-236317304.


Provide predictable ordering of validation summary messages and @Html.Display() / @Html.Editor() properties

to ensure a predictable order using MVC once #964 is fixed, users must annotate all model properties with [Display(Order=x)].  this may be too high a bar but unfortunately type.GetRuntimeProperties() and related Reflection methods do not guarantee a predictable or even a stable ordering.
recent decision was to split this issue from #964 and to determine what guarantees exist for the type.GetRuntimeProperties() return value.  then, if no guarantees exist (as MSDN implies), ask for one or add something (perhaps not based on PropertyName) to MVC.
details and history
see also the StackOverflow discussion of Reflection ordering as well as the linked MSDN documentation.
in #964:

MVC 5.2 does not provide a predictable property order when displaying / editing a complex object or filling in the @Html.ValidationSummary(). We could do a bit better here and sort by Order then by PropertyName.

in PR #1866:

I'm not sure I quite follow the reasoning for adding ordering by Name, is it the same behavior as MVC5? Can you illustrate the benefit?

--

we had an offline discussion (sorry, not sure who all was there) where we agreed to make the property order predictable. today, it's possible for the HTML Html.DisplayFor(...) (for example) generates to change between CLR or Roslyn builds. with this fix in place, the UI will remain consistent no matter how the runtime and compiler choose to order properties.
MVC 5 does not provide such a predictable property order. the offline discussion basically supported my comment in #964:

We could do a bit better here and sort by Order then by PropertyName.

Please work with the Roslyn and CLR folks to verify if:

Is the order consistent if you use the same compiler and same code.
Is the order the definition order if you have a simple POCO.
Can the order change at runtime

Too big a surprise for those used to @Html.DisplayFor() and so on spitting out fields in the order they placed properties in the original class.


Make back button locking also prevent escape key

To be resolved by MC

Menuchanger will add a feature to prevent cancelling (ie there will still be a code change needed here)


rename variable names

Purpose

...
rename variable names

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Install ansible

$ pip install ansible[azure]

[Optional] Install ansible role

$ ansible-galaxy install Azure.azure_preview_modules
$ pip install -r ~/.ansible/roles/Azure.azure_preview_modules/files/requirements-azure.txt

Get the sample playbook

git clone https://github.com/Azure-Samples/ansible-playbooks.git
cd ansible-playbooks
git checkout [branch-name]

Test the code

ansible-playbook <filename>.yml

What to Check
Verify that the playbook is successfully run.
Other Information

@yungezz

@yungezz Could you help to confirm whether this PR is merged or needs further review? Thanks!

@yungezz

@yungezz


Fix several issues with resolving function connection string

Ran tests locally with both the __fullyQualifiedNamespace setup as well as an explicit connectionstring with SharedAccessToken and simple URI-only

Great, thanks!


Implement Bootstrap Collapse

http://getbootstrap.com/javascript/#collapse

We already support Hide/Show effects. This is not required.


"Main module of program is empty: nothing will happen when it is run" warning when running xunit tests on .net core.

Please provide a succinct description of the issue.
Repro steps
Create a test directory then from command line

dotnet new xunit -lang F#

dotnet add package xUnit

dotnet restore

dotnet test

Expected behavior
Run the tests without warnings.
Actual behavior
It generates a warning, Main module of program is empty: nothing will happen when it is run
Here's my output
C:\...\Documents\Projects\xunit_test>dotnet test
Build started, please wait...
C:\Users\onur.gumus\Documents\Projects\xunit_test\Tests.fs(8,22): warning FS0988: Main module of program is empty: nothing will happen when
it is run [C:\Users\onur.gumus\Documents\Projects\xunit_test\xunit_test.fsproj]
Build completed.

Test run for C:\Users\onur.gumus\Documents\Projects\xunit_test\bin\Debug\netcoreapp1.1\xunit_test.dll(.NETCoreApp,Version=v1.1)
Microsoft (R) Test Execution Command Line Tool Version <IP_ADDRESS>
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
[xUnit.net 00:00:01.0591665]   Discovering: xunit_test
[xUnit.net 00:00:01.1484271]   Discovered:  xunit_test
[xUnit.net 00:00:01.1898693]   Starting:    xunit_test
[xUnit.net 00:00:01.2949161]   Finished:    xunit_test

Total tests: 1. Passed: 1. Failed: 0. Skipped: 0.
Test Run Successful.
Test execution time: 2.0677 Seconds

Known workarounds
No
Related information
Windows with dotnet version 1.0.1 SDK version 1.1.0

this a problem with the template, netcore test projects are all console apps, and F# console apps need a function with [<EntryPoint>]
this is all you need to make the warning go away
[<EntryPoint>]
let main argv = 0

cc @enricosada

@OnurGumus it's like @cloudRoutine say, and is tracked in https://github.com/dotnet/netcorecli-fsc/issues/79
@KevinRansom this can be closed, the update of xunit/mstest templates is tracked in the referenced issue


Use the mobile version of the full-screen player in a with larger screen

Description
#163
https://github.com/deluan/navidrome/issues/520
Expect Api Name

<ReactJkMusicPlayer mobileMediaQuery="(max-width: 1024px)" />

https://github.com/lijinke666/react-music-player#bulb-customize-mobile-media-query


Is Azure RBAC based on OAuth2.0?

[Enter feedback here]
The documentation describes Azure RBAC quite well. However, I wonder, what is the relation between Azure RBAC, OAuth2.0, and Microsoft Identity platform?
What does it actually mean when some security principal (i.e., a user, or an app) is assigned, let's say, the VM Reader permission?
Does it just mean that, when I want to access some information about VMs, I will need to get a proper access token (and in my request, I will ask for something like "VM_reader" scope), and then, the returned access token will contain all the permission that the "VM Reader" role contains? And, I would get this access token, only because my security principal on Azure has been assigned with the VM Role before I tried to get this access. Is my understanding correct?
I think that it would make sense to explain that on the Docs, because currently it all sound very high level, and it raises questions - how does it actually work?

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

ID: 1e21d4b9-f574-e01d-8676-fb23d6a4ab67
Version Independent ID: 85e74a1b-3bb3-8bdd-8fca-38256c8a46c1
Content: What is Azure role-based access control (Azure RBAC)?
Content Source: articles/role-based-access-control/overview.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

Thanks for the feedback! We are currently investigating and will update you shortly.

Hi @marcinjahn
Thanks for your feedback. We've added an item to our backlog to enhance this area in the docs. Let us know if you have any additional feedback.
thanks


Bots who are silent in Matrix should be silent in Discord

I don't know if this is possible on the Discord side, but some bots in Matrix know not to make noise or create a notification for the user. The Matrix GitLab bot creates a message for every commit, issue comment, etc and it's great on the Matrix side because the info is there if you go looking, but it doesn't notify anyone. It does seem to notify people on the Discord side, though, which is a little more information than people want.
Is it possible to check if the message comes from a bot and send it silently into Discord?
Thank you!

as of #316 that isn't the case anymore (so newest on develop branch). Thanks for reporting, though!


Investigate why text is sometimes cropped off bottom of wildfire charts

We are not sure what conditions cause this, but sometimes the wildfire charts show up with a scroll bar and the footer text cropped off. The wildfire charts are using a slightly larger height (600px vs 500px) than other charts. Does this need to be increased even more?

These charts will likely go through some large revisions soon and we may not have so many items listed in the legend. This could end up being a non-issue if so.

Never mind! This was solved by a browser hard-refresh.

This happened to me, too. Re-opening!

This issue is related to the fact that we are using a slightly taller chart height for the wildfire charts to accommodate the very long legend (5 models * 3 scenarios + 5-model-average * 3 scenarios). The footer positioning and whitespace is relative to the height of the chart, so we would need to tinker with the math that calculates footer offsets and margins to prevent this bug from occurring at different browser resolutions.
#238 modifies the wildfire charts to use fewer models, which eliminates the need for these charts to have a taller height. If we decide to stick with the 5-model-average + 2 models approach for the wildfire charts, this ticket can be closed.

I think it's safe to close this ticket for now, but it's good to be aware of the issue and we may well need to address it in the future when showing charts with many models.


from twitterscraper import query_tweets

I am trying to run the code from twitterscraper import query_tweets from Jupyter through acanonda but having this error:
ConnectionError: ('Connection aborted.', ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None))
Please help.

i have the same issue

i have the same issue as well. anyone help please

You are right Altimis, i tried everything but in colab and even anaconda i could not find solution of this 'cannot import name 'query_tweets' from partially initialized module 'twitterscraper' '


[explorer] Dump actions.json for best candidates

Previously we were generating a best_X.c and best_X.cfg for each
best candidate, which doesn't allow to easily re-use the found
implementation e.g. in the debugger.  The tlcli rebuild command was
introduced for this purpose, and can extract a replay file from the
eventlog.
However, evenlogs these days tend to be quite large, and it may not be
desirable to keep them for runs which don't need specific performance
analysis.  Hence, this patch changes the mechanism for dumping best
candidates: now a directory best_X is created, with the generated code
in code.c; the loop tree in code.cfg; and the replay in
actions.json (not unlike the format used for errors, which also
contain extra files about the error).

Previously we were generating a best_X.c and best_X.cfg for each
best candidate, which doesn't allow to easily re-use the found
implementation e.g. in the debugger. The tlcli rebuild command was
introduced for this purpose, and can extract a replay file from the
eventlog.
However, evenlogs these days tend to be quite large, and it may not be

eventlogs

desirable to keep them for runs which don't need specific performance
analysis. Hence, this patch changes the mechanism for dumping best
candidates: now a directory best_X is created, with the generated code
in code.c; the loop tree in code.cfg; and the replay in
actions.json (not unlike the format used for errors, which also
contain extra files about the error).


Remove lint and re-render recipe

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

@jakirkham This seems to fix the issue you were seeing in #8, do you want to include those changes in your PR or work from this one.

Excellent. LGTM 👍

Maybe we can @aebrahim if he remembers why python was missing from the build dependencies here.

The feedstock was generated by conda-forge/staged-recipes#141 during which the Python dependency was moved from build to run in commit 73bc95.  Before that move the build was failing in Python 3.5 but worked with the change.  Looking at this now it seems as if the important part was to have python as a run dependency, not necessarily removing it as a build dependency.
For the build itself python is not required but conda smithy requires it to render the matrix which is required in order the build for all three VC versions.

I think it was in there originally. Not sure why it was removed (I don't
think I even removed it).
On May 16, 2016 07:38, "Jonathan J. Helmus"<EMAIL_ADDRESS>wrote:

The feedstock was generated by conda-forge/staged-recipes#141
https://github.com/conda-forge/staged-recipes/pull/141 during which the
Python dependency was moved from build to run in commit 73bc95
https://github.com/conda-forge/staged-recipes/pull/141/commits/73bc95b628fb471e3da0e4d1b43c8a338f0c193a.
Before that move the build was failing in Python 3.5
https://ci.appveyor.com/project/conda-forge/staged-recipes/build/1.0.222
but worked with the change
https://ci.appveyor.com/project/conda-forge/staged-recipes/build/1.0.232.
Looking at this now it seems as if the important part was to have python as
a run dependency, not necessarily removing it as a build dependency.
For the build itself python is not required but conda smithy requires it
to render the matrix which is required in order the build for all three VC
versions.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/conda-forge/glpk-feedstock/pull/9#issuecomment-219441723

Sounds like this sounds good to everyone. Going to go ahead and merge.


ContentNode.hasRole() always returns false if multiple roles are present on a node.

ContentNode.hasRole() unfortunately maps to role? which returns true if the given string exactly matches the role attribute.
Instead it should map to has_role? which returns true if the given role is part of the attribute.

As odd as it seems, role? is intended to check if the role attribute is set and optionally if the whole role value equals the value passed in. has_role? would definitely be the method you want to map to.

Yes, I somehow missed this as the tests go well if there's at most one role;-)
Fixed with https://github.com/asciidoctor/asciidoctorj/commit/6b5e6ea22b7c1cc36a515d2d24f12f3fd1f47b6d


Change VAT Report Type fields from Option to Enum

Could you change following fields to Enum "VAT Report Configuration"?
"VAT Report Config. Code" in Table "VAT Statement Report Line",
"VAT Report Type" in Table "VAT Report Archive".

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


solve internationalization problems when using ctk dicom widget with languages other than english

the modifications below aim to solve the internationalization problem when people who want to use different language to display information when using CTK DICOM Library
the details are described as below:
1、ctkDicomTableView
add a new private member QLabel to store the internal use of queryTableName, use the original QLabel  just to display the table view's caption on ui.
add function setDisplayText to set the table view's caption on ui
add a function applyHeaderTextList to supply a way to use different language formating the table column title
2、ctkDICOMQueryRetrieveWidget
set the ctkDICOMQuery Parameters with QApplication::translate() result to solve the internationalization problem
3、ctkDICOMServerNodeWidget
modify addServerNode function to set the table widget column title with QApplication::translate() result to solve the internationalization problem
modify readSettings function to set the default server node parameters with QApplication::translate() result to solve the internationalization problem
4、ctkDICOMTableManager
modify init function, add function call of setDisplayText to patientsTable,studiesTable and seriesTable to format the table view caption with different language

@pieper request changes have been modified

@pieper all request have been finished

We have received grant funding for translation of Slicer to French and Spanish, so we would like to revive and integrate this pull request. We'll set up crowdsourcing translation on Weblate.
One change that I would consider making is to generate one single .ts file for entire CTK instead of one .ts file for each component (ctkDICOM2, ctkDICOMQueryRetrieve, etc.). Having less .ts files would make managament of translations a bit easier: we would have one .ts file for each major component (Slicer, CTK, and for each extension, about a total of 100) for each language - a total of 1000-2000 files. If we had a .ts file for each component then we could end up with tens of thousands of very small .ts files.
@pieper @mhdiop @nolden

Yes, now that we have some resources more experience with the translation options we can revisit this code and get it merged.
@nolden let us know if there are considerations for internationalization of MITK we should take into account for this.

@pieper Thanks! :) Nothing to consider regarding i18n and MITK.

Closing.
This pull request was superseded by:

https://github.com/commontk/CTK/pull/1068
https://github.com/commontk/CTK/pull/1077


src/qt/sidechaindepositdialog.cpp Refactor deposit code

See:
void SidechainDepositDialog::on_pushButtonDeposit_clicked()
Refactor - move logic to a function and out of the button slot

Accidentally hit enter and submitted this blank! Fixed now


Do you have some inference in this repo?

Hi, thanks for your repo, very clean. Can you provide some inference in this? Thanks very much!

@antran-mespitech  Please check the last push on this repo you will find a pretrained model in Japanese.


Add support for TAP Tables

In many of the test that people write, there is also a codecoverage aspect. So while using something like nyc with ava it returns a table of codecov at the end, which currently isn't included in the HTML.
TAP Output
# sorts » sort by quality score
ok 1 - sorts » sort by quality score
# sorts » sort by jobs per driver
ok 2 - sorts » sort by jobs per driver
# filters » module:vsl/filters~byStatus - status
ok 3 - filters » module:vsl/filters~byStatus - status
# filters » module:vsl/filters~byPostcodesInclusion - both postcodes served
ok 4 - filters » module:vsl/filters~byPostcodesInclusion - both postcodes served
# filters » module:vsl/filters~byPostcodesInclusion - pickup served
ok 5 - filters » module:vsl/filters~byPostcodesInclusion - pickup served
# filters » module:vsl/filters~byPostcodesInclusion - delivery served
ok 6 - filters » module:vsl/filters~byPostcodesInclusion - delivery served
# filters » module:vsl/filters~byPostcodesExclusion - none served
ok 7 - filters » module:vsl/filters~byPostcodesExclusion - none served
# filters » module:vsl/filters~byPostcodesInclusion - pickup not served
ok 8 - filters » module:vsl/filters~byPostcodesInclusion - pickup not served
# filters » postcode exclusion - delivery exclusion
ok 9 - filters » postcode exclusion - delivery exclusion
# filters » volume - no range defined
ok 10 - filters » volume - no range defined
# filters » volume - only min

1..10
# tests 10
# pass 10
# fail 0

------------|----------|----------|----------|----------|----------------|
File        |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
------------|----------|----------|----------|----------|----------------|
All files   |      100 |      100 |      100 |      100 |                |
 filters.js |      100 |      100 |      100 |      100 |                |
 runner.js  |      100 |      100 |      100 |      100 |                |
 sorts.js   |      100 |      100 |      100 |      100 |                |
------------|----------|----------|----------|----------|----------------|

tap-that-html output
Tests: 10
Passed: 10
Failed: 0
1: OK - sorts » sort by quality score
2: OK - sorts » sort by jobs per driver
3: OK - filters » module:vsl/filters~byStatus - status
4: OK - filters » module:vsl/filters~byPostcodesInclusion - both postcodes served
5: OK - filters » module:vsl/filters~byPostcodesInclusion - pickup served
6: OK - filters » module:vsl/filters~byPostcodesInclusion - delivery served
7: OK - filters » module:vsl/filters~byPostcodesExclusion - none served
8: OK - filters » module:vsl/filters~byPostcodesInclusion - pickup not served
9: OK - filters » postcode exclusion - delivery exclusion
10: OK - filters » volume - no range defined

As for the implementation aspect. Since you're anyways using a monospace font, I don't think there will be any formatting issues. And you wouldn't have to use any HTML for tables either, it could be a simple text block.
As for the color scheme, you can use what is simply outputted in the terminal.

Though I'd say color is just a visual enhancement so it can wait. Adding the table would be grand!


Use BuildService on Gradle 6.1+

In order to support Gradle's upcoming configuration cache feature
(formerly known as "instant execution"), we no longer use static state
and a build listener to clear it, but rely on a BuildService instead.

Superseded by #28


[CI] Add Travis CI conf for ROS Kinetic.

You may or may not have been using CI (Continuous Integration) somewhere internally, but AFAICT on your public repo there's no trait for that, so goes this PR. CI is IMHO a way to go to avoid many problems including buildfarm hassles like https://github.com/ros/rosdistro/pull/16449 ;)!
ROS offers a few different ways to simplify setting up CI. In this PR, I'm suggesting industrial_ci (admittedly I'm one of the authors&maintainers). It's a set of scripts for CI on ROS. The simple config file in this PR enables CI to run on Travis CI for this repo, including ROS pre-release test that is recommended for packages released on ROS buildfarm.
Contrary to its name, it works for any ROS packages as well, not limited to "industrial" pkgs.
If this looks good, can any admin enable Travis for this repo at https://travis-ci.org/profile/CPFL?

If you're curious how the CI result looks, I've run CI jobs on my fork against current HEAD https://github.com/130s/Autoware/pull/1 and here's CI result. Looks like all CI jobs failed due to various issues.
How to interpret the CI result per each PR on your repo may be a little tricky for now, as I found a WIP ticket https://github.com/CPFL/Autoware/issues/766 where more packages are getting ready to be released so that CI might not pass unless all in-progress work gets done.

It's totally up to the maintainers to use which CI tool, how to configure the detail, how to utilize the CI result etc. Just fyi that we as in industrial_ci maintainers have been very active in responding to questions and enhancement requests over a few years.

@130s thanks for the PR. We in fact do not have an internal CI (other than 50+ developers building regularly on their work stations) and that is a major problem indeed which we are aware of.
However the problem is also not to setup a CI script (we could and are trying to do so on ROS buildfarm https://github.com/ros/rosdistro/pull/16449) but we need to make packages releasable as per #766 first.
So I would for now not accept this PR as I certainly do not need another CI server screaming at me for something I know very very well that we need to fix.
But I would happily accept help for making the Autoware packages releasable.
@130s since I already have you here - can you comment how industrial_ci is different from ROS buildfarm?

@130s I hope I didnt drive you away. Did you see my Q:

can you comment how industrial_ci is different from ROS buildfarm?

@dejanpan That makes sense and like I mentioned I knew y'all have your priority.

since I already have you here - can you comment how industrial_ci is different from ROS buildfarm?

That's on my todo stack and requires some more thoughts. I'll probably respond to that question by answering this thread or even more particularly, by editing this wiki page. In a nutshell the one provided by ros.org is the official so you're definitely encouraged to use that one. But I found that it doesn't cover everything, and requires rather a complicated setting. So usually I recommend using both ros.org and industrial_ci (which I normally do).


Failed install on Apple silicon

LocalAI version:
Most recent as of this report
Environment, CPU architecture, OS, and Version:

Describe the bug
Running the installer from the official documentation fails for macOS running ARM64 fails at this part:
cd llama.cpp && mkdir -p build && cd build && cmake ..  -DLLAMA_METAL=OFF && cmake --build . --config Release
To Reproduce
Follow these steps on an M2 max mbp
Expected behavior
A successful install
Logs
Full error:
-- The C compiler identification is AppleClang <IP_ADDRESS>00040
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00040
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Accelerate framework found
-- CMAKE_SYSTEM_PROCESSOR: arm64
-- ARM detected
-- Performing Test COMPILER_SUPPORTS_FP16_FORMAT_I3E
-- Performing Test COMPILER_SUPPORTS_FP16_FORMAT_I3E - Failed
CMake Error at examples/grpc-server/CMakeLists.txt:13 (find_package):
  Could not find a package configuration file provided by "Protobuf" with any
  of the following names:

    ProtobufConfig.cmake
    protobuf-config.cmake

  Add the installation prefix of "Protobuf" to CMAKE_PREFIX_PATH or set
  "Protobuf_DIR" to a directory containing one of the above files.  If
  "Protobuf" provides a separate development package or SDK, be sure it has
  been installed.

-- Configuring incomplete, errors occurred!
make[1]: *** [grpc-server] Error 1
make: *** [backend/cpp/llama/grpc-server] Error 2

Please check this comment https://github.com/mudler/LocalAI/issues/1197#issuecomment-1779573484

I was able to solve it by linking protoc again.
brew link protobuf
make clean
make BUILD_TYPE=metal build

make BUILD_TYPE=metal build

Thanks mate. The original issue was solved by relinking protobuf but then it failed at another point for me after following the steps in #1197
Still not managed a successful install though as I described in detail here
Always ends up like this:

Is it succeed to build? It is ok we get the Warning while the building process.

Is it succeed to build? It is ok we get the Warning while the building process.

No.
I've never managed to get the build to get past this point. It always just seems to stop at this point and never progress.

Bumped into this after clearing #1315. Attaching output from my terminal at time of error and some screenshots for context of where this occurs in the build.
Dump of text in image:
Found Threads: TRUE
CMAKE_SYSTEM_PROCESSOR: aarch64
ARM detected
Performing Test COMPILER_SUPPORTS_FP16_FORMAT_I3E
-- Performing Test COMPILER_SUPPORTS_FP16_FORMAT_I3E - Failed
CMake Error at examples/grpc-server/CMakelists.txt:26 (find_package):
Found package configuration file:

/usr/local/lib/cmake/protobuf/protobuf-config.cmake

but it set Protobuf_FOUND to FALSE so package "Protobuf" is considered to
be NOT FOUND. Reason given by package:

The following imported targets are referenced, but are missing:
absl::absl_check absl::absl_log absl::die_if_null absl::log_initialize

-- Configuring incomplete, errors occurred!
See also "/build/backend/cpp/llama/llama.cpp/build/CMakeFiles/CMakeOutput.log

See also "/build/backend/cpp/llama/llama.cpp/build/CMakeFiles/CMakeError.log"
make[1]: xxx [Makefile:49: grpc-server] Error 1

make[1]: Leaving directory '/build/backend/cpp/llama’
make: *xx [Makefile:436: backend/cpp/llama/grpc-server] Error 2

failed to solve: process "/bin/sh -c make build" did not complete successfully: exi
t code: 2

LocalAI on via # took 18m24s

Screenshot of error:

Where error occurred in build:

Environment:
Fedora Linux Asahi Remix 39 on M2

Took me a while to get back to the error using make and not Docker but I eventually did and it was the same error OP saw which I worked around by:
BUILD_GRPC_FOR_BACKEND_LLAMA=on make backed/cpp/llama/grpc-server

And then rerunning the build target. After that I was able to run the build.

Took me a while to get back to the error using make and not Docker but I eventually did and it was the same error OP saw which I worked around by:
BUILD_GRPC_FOR_BACKEND_LLAMA=on make backed/cpp/llama/grpc-server
And then rerunning the build target. After that I was able to start the server.

Took me a while to get back to the error using make and not Docker but I eventually did and it was the same error OP saw which I worked around by:
BUILD_GRPC_FOR_BACKEND_LLAMA=on make backed/cpp/llama/grpc-server

And then rerunning the build target. After that I was able to start the server.

@NinjAiBot my output looks just like yours, and it's working for me—I just followed the next steps in Example: Build on mac to download ggml-gpt4all-j.bin and ask it how it was. Try it! Thanks @renzo4web for the brew link protobuf step which fixed the build for me.

Just used LM-Studio instead. Was the easiest way to spin up a server to chat to a model which is what I needed to do


Update bitflags minimum version to 1.0.4

Currently, this crate requests a version compatible with 1.0.1, but uses the bitflags macro in 2018 style which wasn't supported until bitflags 1.0.4. While running cargo update or starting a new project would bypass the issue, older projects updating their dependencies will see build errors from this crate being unable to find __bitflags. Specifically, I got 41 errors between cannot find macro `__bitflags!` in this scope and various undefined structures defined within bitflags.
Essentially, x86_64 already depends on 1.0.4, but claims to be able to work with 1.0.1 when it really can't.

Good catch, thanks a lot for the report!
I pushed a fix in https://github.com/rust-osdev/x86_64/commit/e0d776e1eb1b0fdb48c97b9975d20ac70629c063 and also published a new version to crates.io (0.5.4).


Pulled latest git code today, error upon launch

Expected Behavior
It shouldn't error out.
Actual Behavior
It pukes on an error sayinig "main.py : 'bool' object has not attribute 'split"

I tried restarting the Swarm UI again and this time it just hung up entirely on the Comfy backend startup
Steps to Reproduce
have previous version on your system , then run update-windows.bat, then try running Swarm UI
Debug Logs
2024-10-21 19:38:25.637 [Init] === SwarmUI v<IP_ADDRESS> Starting at 2024-10-21 19:38:25 ===
2024-10-21 19:38:25.671 [Init] Prepping extension: SwarmUI.Builtin_ScorersExtension.ScorersExtension...
2024-10-21 19:38:25.672 [Init] Prepping extension: SwarmUI.Builtin_ImageBatchToolExtension.ImageBatchToolExtension...
2024-10-21 19:38:25.673 [Init] Prepping extension: SwarmUI.Builtin_GridGeneratorExtension.GridGeneratorExtension...
2024-10-21 19:38:25.674 [Init] Prepping extension: SwarmUI.Builtin_DynamicThresholding.DynamicThresholdingExtension...
2024-10-21 19:38:25.674 [Init] Prepping extension: SwarmUI.Builtin_ComfyUIBackend.ComfyUIBackendExtension...
2024-10-21 19:38:25.675 [Init] Prepping extension: SwarmUI.Builtin_AutoWebUIExtension.AutoWebUIBackendExtension...
2024-10-21 19:38:25.705 [Init] Parsing command line...
2024-10-21 19:38:25.706 [Init] Loading settings file...
2024-10-21 19:38:25.720 [Init] Re-saving settings file...
2024-10-21 19:38:25.737 [Init] Applying command line settings...
2024-10-21 19:38:25.758 [Init] Prepping options...
2024-10-21 19:38:25.853 [Init] CPU Cores: 16 | RAM: 31.91 GiB total, 18.49 GiB available, 128.00 GiB virtual, 96.09 GiB swap
2024-10-21 19:38:25.854 [Init] GPU 0: NVIDIA GeForce RTX 3090 | Temp 42C | Util 42% GPU, 25% Memory | VRAM 24.00 GiB total, 22.74 GiB free, 1.01 GiB used
2024-10-21 19:38:25.863 [Init] Loading models list...
2024-10-21 19:38:25.895 [Init] Loading backends...
2024-10-21 19:38:25.896 [Init] Loading backends from file...
2024-10-21 19:38:25.898 [Init] Prepping API...
2024-10-21 19:38:25.899 [Init] Initializing backend #0 - ComfyUI Self-Starting...
2024-10-21 19:38:25.900 [Init] Prepping webserver...
2024-10-21 19:38:25.902 [Init] Backend request handler loop ready...
2024-10-21 19:38:26.001 [Init] Scan for web extensions...
2024-10-21 19:38:26.003 [Init] Readying extensions for launch...
2024-10-21 19:38:26.003 [Init] Launching server...
2024-10-21 19:38:26.004 [Init] Starting webserver on http://<IP_ADDRESS>:7801
2024-10-21 19:38:26.403 [Init] Current git commit marked as date 2024-10-20 09:20:20
2024-10-21 19:38:26.423 [Init] Swarm is up to date! You have version <IP_ADDRESS>, and 0.9.3-Beta is the latest.
2024-10-21 19:38:26.424 [Init] Program is running.
2024-10-21 19:38:26.934 [Init] Launch web browser...
2024-10-21 19:38:27.440 [Info] Creating new admin session 'local' for <IP_ADDRESS>
2024-10-21 19:38:27.442 [Init] Self-Start ComfyUI-0 on port 7821 is loading...
2024-10-21 19:38:32.544 [Warning] [ComfyUI-0/STDERR] Traceback (most recent call last):
Other
No response

Here are debug logs when it crashes:
2024-10-21 19:41:03.907 [Init] GPU 0: NVIDIA GeForce RTX 3090 | Temp 43C | Util 13% GPU, 18% Memory | VRAM 24.00 GiB total, 22.70 GiB free, 1.05 GiB used
2024-10-21 19:41:03.920 [Init] Loading models list...
2024-10-21 19:41:03.952 [Init] Loading backends...
2024-10-21 19:41:03.953 [Init] Loading backends from file...
2024-10-21 19:41:03.956 [Init] Prepping API...
2024-10-21 19:41:03.957 [Init] Initializing backend #0 - ComfyUI Self-Starting...
2024-10-21 19:41:03.958 [Init] Prepping webserver...
2024-10-21 19:41:03.960 [Init] Backend request handler loop ready...
2024-10-21 19:41:04.055 [Init] Scan for web extensions...
2024-10-21 19:41:04.058 [Init] Readying extensions for launch...
2024-10-21 19:41:04.059 [Init] Launching server...
2024-10-21 19:41:04.059 [Init] Starting webserver on http://<IP_ADDRESS>:7801
2024-10-21 19:41:04.325 [Init] Swarm is up to date! You have version <IP_ADDRESS>, and 0.9.3-Beta is the latest.
2024-10-21 19:41:04.326 [Init] Program is running.
2024-10-21 19:41:04.835 [Init] Launch web browser...
2024-10-21 19:41:05.318 [Info] Creating new admin session 'local' for <IP_ADDRESS>
2024-10-21 19:41:05.340 [Init] Self-Start ComfyUI-0 on port 7821 is loading...
2024-10-21 19:41:10.523 [Warning] [ComfyUI-0/STDERR] Traceback (most recent call last):
2024-10-21 19:41:10.524 [Warning] [ComfyUI-0/STDERR]   File "C:\SwarmUI\SwarmUI\dlbackend\comfy\ComfyUI\main.py", line 225, in
2024-10-21 19:41:10.525 [Warning] [ComfyUI-0/STDERR]     load_extra_path_config(config_path)
2024-10-21 19:41:10.525 [Warning] [ComfyUI-0/STDERR]   File "C:\SwarmUI\SwarmUI\dlbackend\comfy\ComfyUI\main.py", line 190, in load_extra_path_config
2024-10-21 19:41:10.526 [Warning] [ComfyUI-0/STDERR]     for y in conf[x].split("\n"):
2024-10-21 19:41:10.527 [Warning] [ComfyUI-0/STDERR]              ^^^^^^^^^^^^^
2024-10-21 19:41:10.528 [Warning] [ComfyUI-0/STDERR] AttributeError: 'bool' object has no attribute 'split'
2024-10-21 19:41:10.928 [Info] Self-Start ComfyUI-0 unexpectedly exited (if something failed, change setting LogLevel to Debug to see why!)
2024-10-21 19:41:10.929 [Info] Self-Start ComfyUI-0 had errors before shutdown:
[ComfyUI-0/STDERR] Total VRAM 24575 MB, total RAM 32672 MB
[ComfyUI-0/STDERR] pytorch version: 2.3.1+cu121
[ComfyUI-0/STDERR] Set vram state to: NORMAL_VRAM
[ComfyUI-0/STDERR] Device: cuda:0 NVIDIA GeForce RTX 3090 : cudaMallocAsync
[ComfyUI-0/STDERR] Using pytorch cross attention
[ComfyUI-0/STDERR] [Prompt Server] web root: C:\SwarmUI\SwarmUI\dlbackend\comfy\ComfyUI\web_custom_versions\Comfy-Org_ComfyUI_frontend\1.2.47
[ComfyUI-0/STDERR] Traceback (most recent call last):
[ComfyUI-0/STDERR]   File "C:\SwarmUI\SwarmUI\dlbackend\comfy\ComfyUI\main.py", line 225, in
[ComfyUI-0/STDERR]     load_extra_path_config(config_path)
[ComfyUI-0/STDERR]   File "C:\SwarmUI\SwarmUI\dlbackend\comfy\ComfyUI\main.py", line 190, in load_extra_path_config
[ComfyUI-0/STDERR]     for y in conf[x].split("\n"):
[ComfyUI-0/STDERR]              ^^^^^^^^^^^^^
[ComfyUI-0/STDERR] AttributeError: 'bool' object has no attribute 'split'

Going back to git version commit/896f8321c8bbf2342177e9b73add587a3b7acda1 and it runs properly again


Remove all upper bounds

They prevent downstream from upgrading their dependencies when they want, without requiring hyperx to also update its own.

Yeah that would be a good idea, this just starting causing me problems too today :)

Can you show specific problems, e.g. cargo update errors or the like? I haven't been updating so I might be missing something.
The bounds are there for default "x.y.z" := "~x.y.z" as well, just implicit (which as you might have noticed, I'm not a huge fan of).

In the Cargo ecosystem, "1" means ">=1, <2".
Cargo will allow only 1 version per major version, so you can't have httparse 1.3 and httparse 1.4 in a single project.
That means that when bumping from hyper 0.14.5 (which depends on httparse 1.3) to hyper 0.14.6 (which depends on httparse 1.4), cargo will return this error:
error: failed to select a version for `httparse`.
    ... required by package `hyperx v1.3.0`
    ... which is depended on by `hyper-bump-issue v0.1.0 (/Users/nox/src/hyper-bump-issue)`
versions that meet the requirements `>=1.0, <1.4` are: 1.3.6, 1.3.5, 1.3.4, 1.3.3, 1.3.2, 1.3.1, 1.3.0, 1.2.5, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2.0, 1.1.2, 1.1.1, 1.1.0, 1.0.0

all possible versions conflict with previously selected packages.

  previously selected package `httparse v1.4.0`
    ... which is depended on by `hyper v0.14.6`
    ... which is depended on by `hyper-bump-issue v0.1.0 (/Users/nox/src/hyper-bump-issue)`

failed to select a version for `httparse` which could resolve this conflict

You can reproduce that with this manifest:
[package]
name = "hyper-bump-issue"
version = "0.1.0"
authors = ["Anthony Ramine<EMAIL_ADDRESS>edition = "2018"

[dependencies]
hyper = "0.14.6"
hyperx = "1.3"

Maybe you confused the case of depending on a 0.y crate and the case of depending on an 1.y crate. Cargo considers that the left-most non-zero digit is the major version, so 1.2.0 is compatible with 1.1.0, and 0.1.2 is compatible with 0.1.1, but 0.2.0 is not compatible with 0.1.0.
See this:

This guide uses the terms "major" and "minor" assuming this relates to a "1.0.0" release or later. Initial development releases starting with "0.y.z" can treat changes in "y" as a major release, and "z" as a minor release. "0.0.z" releases are always major changes. This is because Cargo uses the convention that only changes in the left-most non-zero component are considered incompatible.

Thanks for the specific error. Note I'm aware of the cargo/Semver behavior. This project favors these (above shown) kinds of failure over unexpected breakage in a new httparse minor (for example, unplanned MSRV upgrades).
I'm looking at it now, and wish github actions CI scheduled runs wouldn't be disabled if the project hasn't had updates in a while (also reviving those).
Will probably close this in favor of your #34  and release accordingly.

That specific error right now is literally unavoidable, while an unplanned MSRV upgrade can alway be recovered by a downgrade of the dependency, which is then recorded in the project's lockfile and thus doesn't happen again. IMO you should reconsider that policy, and file issues upstream on your own dependencies when they increase the MSRV (if they even have a MSRV policy).

Note that by this you favor regular breakage whenever any of the dependencies get updates over the unlikely breakage that could happen from a minor version update (and which would really be a bug).
Unrelated, MSVR is not a real cargo concept at this point and generally updating the minimum supported Rust version is not considered a breaking change by the Rust ecosystem. Handling this different here (just like in the other maybe dozen crates like e.g. byteorder) causes additional burden on all users.

Note that hyper introduced a hard httparse 1.5.0 dependency in a patch release 1.4.6 of hyper?!  That should have been released as hyper 0.15.0 IMO, but that project prefers to risk breakage (e.g. unplanned MSRV increases, regressions) than to force downstream to explicitly upgrade, which is neither in the spirit of Semver (of a broadly used crate that should be, or be treated like ≥1.x.y), nor particularly economical.
Users and downstream public crate maintainers are welcome to there own opinions though, clearly I can't stop them! 😃

With all due respect @dekellum, you are wrong here.
Hyper released 0.14.6 which includes a bump of its dependency httparse from 1.3.6 to 1.4.0. That's completely correct according to the semver interpretation used by cargo and crates.io.
httparse 1.4.0 is compatible with 1.3.6, so it can be bumped in a minor bump from 0.14.5 to 0.14.6 in hyper, because as I mentioned above, when x is 0, then the actual major version becomes y, and thus z is both used for patch-level and minor updates.

the semver interpretation

(emphasis mine)
…vs my opinion and interpretation (and how this and some related crates are release managed): its minimally a smell, and frequently a liability to release a minor version dependency increase in a patch release.
For example, though it may not be found an actual issue here (subject to CI, TBD): it is considered by the community, a moderate or compromise stance to at least bump the minor (y of x.y.z) version for MSRV increases of any kind.  Requiring a new minor release dependency, and doing so in a patch release is asking for trouble and attempting to have it both ways, which is a false imperative.
If you'd like to think of it this way, by using explicit constraints, I've set a "snare" which hyper tripped 16 hours ago with release 0.14.6 and I will resolve (probably via #34) in some few hours more.  The practical outcome for my and other projects that use hyperx and check in a working real (not via your hypothetical Cargo.toml) Cargo.lock file, is that the upgrade to hyper 0.14.6 (and httparse 1.4.0) simply fails to happen until I explicitly resolve it with a hyperx release (probably a patch, but testing will determine that).
Again, you are welcome to your own opinions and public crate release practices!  Fork this and release your own "hyper-y" crate if you'd like!

Well, "that project prefers to risk breakage than to force downstream to explicitly upgrade" is an extremely loaded opinion, almost implying that that project's maintainers aren't doing their job correctly. Furthermore, "that project" is literally hyper, your most important upstream dependency.

Oh, I'm not just implying that "that project's maintainers aren't doing their job correctly" and I'm saying that explicitly. Now probably, in practical terms, the maintainer simply has different goals than mine.  We can agree to disagree and have been for a while now!

Actually #32 may be the final solution, in this case. I'm going to review the other behind dependencies first though.

Also for the record hyperx does not directly depend on hyper crate!  (See README, "eXtraction") Obviously, many hyperx consumers will have a direct or indirect dependency on hyper as well.

Dissing the maintainers of the crate from which you extracted code and simply added a letter to the name is not the most charitable thing I've seen on the Internet. Anyway, I'm done here.

For any subsequent readers, since I'm accused of lacking "charity" here, see #1 for background, and note it was not my preference that hyper originally dropped its typed header module in a minor release, without any practical replacement for at least 6 months.  (An odd move for such a core crate, at the very least.)
The meritocracy finds that hyperx is still broadly in use, and I've managed to modernize it since, in several practical ways without destroying the original compatibility.  You are all very welcome to use the work (or not) subject to its generous FOSS licenses!

Can you show specific problems, e.g. cargo update errors

error: failed to select a version for `httparse`.
    ... required by package `hyperx v1.0.0`
    ... which is depended on by `hubcaps v0.6.0`
    ... which is depended on by `ui v0.1.0 (/Users/shep/Projects/integer32/playground/ui)`
versions that meet the requirements `>=1.0, <1.4` are: 1.3.6, 1.3.5, 1.3.4, 1.3.3, 1.3.2, 1.3.1, 1.3.0, 1.2.5, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2.0, 1.1.2, 1.1.1, 1.1.0, 1.0.0

all possible versions conflict with previously selected packages.

  previously selected package `httparse v1.4.0`
    ... which is depended on by `hyper v0.14.11`
    ... which is depended on by `ui v0.1.0 (/Users/shep/Projects/integer32/playground/ui)`

failed to select a version for `httparse` which could resolve this conflict


Error adding entities for domain select and switch

Description
When installing the new version 4.0.2, I received 2 errors in the logs
Error adding entities for domain select with platform tapo_control
Error while setting up tapo_control platform for select
ValueError: Entity cannot be None

Error adding entities for domain switch with platform tapo_control
Error while setting up tapo_control platform for switch
ValueError: Entity cannot be None

Reproduction Steps

Update to 4.0.2
Reboot Home Assistant (2022.10.04)
Validate Logs

Expected behavior
No errors
If applicable, add error logs.
Logger: homeassistant.components.select
Source: helpers/entity_platform.py:482
Integration: Select ([documentation](https://www.home-assistant.io/integrations/select), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+select%22))

Error adding entities for domain select with platform tapo_control
Error while setting up tapo_control platform for select
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 428, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 482, in _async_add_entity
    raise ValueError("Entity cannot be None")
ValueError: Entity cannot be None

Logger: homeassistant.components.switch
Source: helpers/entity_platform.py:482
Integration: Switch ([documentation](https://www.home-assistant.io/integrations/switch), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+switch%22))

Error adding entities for domain switch with platform tapo_control
Error while setting up tapo_control platform for switch
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 428, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 482, in _async_add_entity
    raise ValueError("Entity cannot be None")
ValueError: Entity cannot be None

Device Firmware
1.1.15 Build 211130 Rel.15378n(5553)
Using stream component
Yes
Does camera work via official integrations?
N/A
Camera has all attributes filled out in developer tools
Yes
HASS Environment
HassOS 9.2
Search for similar issues
Yes
Additional information
I tried removing all the entities and the same issue occurs when using 4.0.2.
When rolling back to 3.7.2, no issues.

Hello,
what camera do you have?

@JurajNyiri ,
Camera: Tapo C100
On my Tapo app or in Home Assistant Options ?

In Home Assistant by going to Devices, searching for Tapo, selecting your camera and clicking on 1 Device.

I probably found the bug, working on a fix.

Should be fixed in 4.0.3.
Please let me know if it is.

Thank you! One more fix incoming for buttons for movement, if camera does not support them they will not be created.

Yes I saw that and they are now greyed out.
Thanks


MM-37456 "Threads" item in the sidebar should not scroll

Summary
Makes the "Threads" item in the sidebar as fixed.
Ticket Link
https://mattermost.atlassian.net/browse/MM-37456
Device Information
This PR was tested on: iOS 14.5, iPhone 12 Simulator, Android 11 Pixel XL emulator
Screenshots
https://user-images.githubusercontent.com/3680799/127208468-cff3d0e5-e99c-4da9-b27b-d7b0323d01d1.mp4
Release Note
NONE

@anurag6713 tests failed

Building app in separate branch.

Thanks @anurag6713 Looks good, I'll let Matthew have a pass first before approving.
One question - Threads item seems a bit wide, is this intended?

@matthewbirtch .. removed 8px.

One question - Threads item seems a bit wide, is this intended?
Thank you @jgilliam17. Styling is same as the channels item in the list. We are reusing the same styles as the rest of them.

Building app in separate branch.

Looks good @anurag6713 based on the screenshots. Will do one last look at the new build and then I'll approve

Cherry pick is scheduled.


Electricity production from waste incinerator is included in must-run CHP entry in merit order table

I noticed that the electricity produced by the waste incinerator (not the waste CHP) is included in the must-run CHP entry in the merit order table. There seem to be two issues with this waste incinerator:

it takes part in the merit order calculation as

- merit_order.type = must_run
- merit_order.group = industry_chp

it is part of the must_run_electricity_production group, which is why it is displayed under the must-run entry in the merit order table.

Long story short, should the waste incinerator be must-run, @AlexanderWirtz or @ChaelKruip ? Or is it dispatchable?

It should be dispatchable, but with baseload marginal costs. :-)

We can ask Albert Bloem how this works?

@AlexanderWirtz  has Albert Bloem been asked? Or is there any update on wether waste incinerators are must-runs or dispatchables?

Funny, I think @jorisberkhout was the last one to talk to Albert Bloem about this.

Closing, fixed with recent heat update


purpose/setting of device_url in configuration.yaml?

I just updated to the latest picframe version, but am unsure of how (or if) to set the variable device_url which is found in the mqtt section of configuration.yaml.  I have use_http set to True.  The comment says to set device_url to the "picframe config page"; is this http://[IP of raspberry pi on my local network]:9000?  How is device_url  being used?  At the moment, I just have it set to the null string, and it seems to be working fine with Home Assistant and on its own.  Thanks for clarifying!  --Jeff

Hi @jeffalperin,
have a look at https://developers.home-assistant.io/blog/2021/10/26/config-entity/ .
You find the device_url in home assistant, if you open picframe's device configuration panel. Click on "visit device".

In simple words device_url is the url you use to open picframe's webpage.


silence "maybe uninitialized" warnings

The compiler doesn't fully understand the code blocks that precede the usage of variables in conditions and thus it thinks it could be uninitialized. Silence the warnings with an explicit initialization.

updated

Integrated. Thanks @sharkcz for the patches!


Chain RichText with pluralization

Describe the bug
I couldn't find in the documentation if this is possible... I need to chain the RichText and pluralization features.
This is the expected result, with pluralization and bold text:
singular:

plural:

The configuration I'd tried:
  "resultTitle(rich)": {
    "one": "{bold({count} ativo)} encontrado",
    "other": "{bold({count} ativos)} encontrados"
  }

The method generated:
String resultTitle({required num rich, required Object count}) => (_root._cardinalResolver ?? PluralResolvers.cardinal('pt'))(rich,
		one: '{bold($count ativo)} encontrado',
		other: '{bold($count ativos)} encontrados',
	);
//....

'search.resultTitle': ({required num rich, required Object count}) => (_root._cardinalResolver ?? PluralResolvers.cardinal('pt'))(rich,
   one: '{bold($count ativo)} encontrado',
   other: '{bold($count ativos)} encontrados',
),

The build_runner couldn't generate the code in a way that this two features work together.

Combining pluralization and rich text is currently not possible

Combining plural+rich text is now possible. You can try it out using v3.0.0-dev.0. I will release a stable release soon.

In your example, it will probably look like this:
"resultTitle(rich)": {
  "one": "{n} {bold(ativo)} encontrado",
  "other": "{n} {bold(ativos)} encontrados"
}

Then you can write your own builder util and call it twice:
TextSpan boldBuilder(Object content) {
  return TextSpan(
    text: content.toString(),
    style: const TextStyle(fontWeight: FontWeight.bold),
  );
}

Text.rich(t.resultTitle(
  n: n,
  nBuilder: boldBuilder,
  bold: boldBuilder,
));


[key reuse] Eager checks

cc/ @mattjj, @froystig
~Test failures are due to the fact that many of our tests reuse keys!~
~Test failures caused by key reuse are now addressed via explicit calls to reuse_key: remaining test failures are due to us breaking cacheing when key reuse is enabled.~
Tests pass!

OK, we're not going all the way to C++ dispatch here, but the current state of things should be pretty safe:

Everything is guarded by the jax_enable_key_reuse_checks flag, which is False by default (except in JAX tests)
The JIT fast path is only avoided when this flag is True and the JIT-compiled has typed keys as inputs or outputs
The key reuse signature is generated within cache_miss (via _create_pjit_jaxpr) whenever the flag is enabled, and uses weakref_lru_cache to avoid potential recomputation.

I think this makes the change safe to merge for now, with the understanding that eventually we'll move the main logic to C++ before enabling this by default.


Assertion failed when calling WavUtility.FromAudioClip(audioClip)

I encounter 2 failed assertion when calling WavUtility.FromAudioClip(audioClip):

Assertion failed: Unexpected AudioClip to wav subchunk2 size: 12925440 == 6462720
Assertion failed: Unexpected AudioClip to wav format byte count: 12925484 == 6462764

The file is saved successfully afterward using File.WriteAllBytes, and can be opened normally.
Please check if these assertions are correct.

I found the same error related the wrong value of subchunk2 and wavSize.

I think the assertions are making an assumption that it is either a stereo / mono recording. Hence if you divide 2 you get the expected value. The script needs improved multi-channel support.

WriteFileData
-   float[] data = new float[audioClip.samples * audioClip.channels];
+   float[] data = new float[audioClip.samples];
fixed it for me


testimonial added

What is the change?
Testimonial section added .
Related issue?
close: #342
How was it tested?
I have tested it in my local system .
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelines while contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Did you lint your code before making the Pull Request?
[x] Have you made corresponding changes to the documentation?
[x] Your submission doesn't break any existing feature.
[x] Have you tested the code before submission?

Screenshots or Video:
Add a screenshot or demo video if appropriate.
https://user-images.githubusercontent.com/67833077/115153432-7b0cb880-a093-11eb-8efd-23ed197886dd.mp4

@Pranav016  Please review my PR . Why the test is failing ?
I have added the frontend part and schema . I was not able to create routing of testimonial to home page .

@Pranav016 I am not able to render the testimonial  to home page  .
As when somebody add the testimonial then it should reflect on home page .
I am not to add dynamically ejs part .

@Pranav016 I am not able to render the testimonial to home page .
As when somebody add the testimonial then it should reflect on home page .
I am not to add dynamically ejs part .

I think one solution to that could be

we only display 3-4 testimonials on the home page carousel but there is a testimonials wall/ page where any new testimonial added will be displayed.

Even though its not hard to update/ add the testimonials in the carousel( I think you implemented a carousel right?) but having 100 testimonials in a carousel doesn't make sense, 3-4 are fine..
Also can you add another demo video if possible because I couldn't see the carousel correctly in this video ^
might be some changes required in that too..

Okay @Pranav016  I will do that .

@Pranav016  First  I have created a testimonial section . There is button of add a testimonial . If the user click on it , It will first check if user is authenticated or not . If not then it will be redirected to log in page . Otherwise it will open Write the testimonial page .
There is a form which has input for views of user . I have done it till this .
So basically other person has to create a schema and save the data in database the render it on home page .
You can use a for loop which will render last  testimonials .

@Pranav016  is it okay now or need some changes .

@Pranav016  I am busy in my college work . I will make make the changes tomorrow .
Sorry .

@Pranav016 I am busy in my college work . I will make make the changes tomorrow .
Sorry .

👍

@Pranav016 I will do it today .

@Pranav016  Please  review my PR .

/level3/

https://user-images.githubusercontent.com/67833077/116190773-d9e3c900-a748-11eb-83bb-f70e1289ec4f.mp4

Daily.Journal.-.Google.Chrome.2021-04-27.11-05-38.mp4

neither the heading nor the button should move, only testimonials should move in the carousel

okay @Pranav016

https://user-images.githubusercontent.com/67833077/116194036-e7e81880-a74d-11eb-89e8-203f919b65a5.mp4

@Pranav016  if you can help me how squash commits ?

@Pranav016 if you can help me how squash commits ?

https://github.com/ALPHAVIO/ToDoist/pull/6
check a comment on this one..
In this HEAD~3 just replace 3 with the no of commits you are squashing

@Pranav016  something like this is showing up and also there are  some conflicts in other file .

You should have rebased your branch before squashing, that's what it's saying..

Get your code approved in this branch then make a new PR with that code with 2-3 commits for merging..
Don't worry about squashing rn as soon as your code gets approved

okay @Pranav016

@Pranav016 is it okay now ?

if then can i open another PR ?

closing this PR


Helm Chart version mismatch between postgres and redis

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Steps to Reproduce

With values.yaml containing

postgresql:
  enabled: true
redis:
  enabled: true

and the default versions from Chart.yaml
dependencies:
  - name: postgresql
    version: "12.1.*"
    repository: https://charts.bitnami.com/bitnami
    condition: postgresql.enabled
  - name: redis
    version: "18.5.*"
    repository: https://charts.bitnami.com/bitnami
    condition: redis.enabled

helm upgrade --install
results in
Error: UPGRADE FAILED: template: cvat/charts/redis/templates/master/service.yaml:12:14: executing "cvat/charts/redis/templates/master/service.yaml" at <include "common.labels.standard" (dict "customLabels" .Values.commonLabels "context" $)>: error calling include: template: cvat/charts/postgresql/charts/common/templates/_labels.tpl:6:27: executing "common.labels.standard" at <include "common.names.name" .>: error calling include: template: cvat/charts/postgresql/charts/common/templates/_names.tpl:6:18: executing "common.names.name" at <.Chart.Name>: nil pointer evaluating interface {}.Name
Chart.lock
dependencies:
- name: postgresql
  repository: https://charts.bitnami.com/bitnami
  version: 12.1.15
- name: nuclio
  repository: https://nuclio.github.io/nuclio/charts
  version: 0.12.1
- name: vector
  repository: https://helm.vector.dev
  version: 0.19.2
- name: clickhouse
  repository: https://charts.bitnami.com/bitnami
  version: 4.1.16
- name: grafana
  repository: https://grafana.github.io/helm-charts
  version: 6.60.6
- name: traefik
  repository: https://helm.traefik.io/traefik
  version: 25.0.0
- name: redis
  repository: https://charts.bitnami.com/bitnami
  version: 18.5.0
digest: sha256:f2002bbe6d04d607b81b373991c1a05ec533e3da5edbc92b5d082d23d50656ca
generated: "2024-02-07T16:46:49.280424046+01:00"

Expected Behavior
Helm installation should run successfully
Possible Solution
upgrade postgres version in Chart.yaml
dependencies:
  - name: postgresql
    version: "12.9.0"
    repository: https://charts.bitnami.com/bitnami
    condition: postgresql.enabled

as suggest in this issue resolves the issue.
Chart.lock now looks like this
dependencies:
- name: postgresql
  repository: https://charts.bitnami.com/bitnami
  version: 12.9.0
- name: nuclio
  repository: https://nuclio.github.io/nuclio/charts
  version: 0.12.1
- name: vector
  repository: https://helm.vector.dev
  version: 0.19.2
- name: clickhouse
  repository: https://charts.bitnami.com/bitnami
  version: 4.1.16
- name: grafana
  repository: https://grafana.github.io/helm-charts
  version: 6.60.6
- name: traefik
  repository: https://helm.traefik.io/traefik
  version: 25.0.0
- name: redis
  repository: https://charts.bitnami.com/bitnami
  version: 18.5.0
digest: sha256:21c9226320b0d6112468d18c0d4be7117c17e82f83801fab2fcb691f430c657c
generated: "2024-02-07T16:17:50.197680436+01:00"

for the redis Chart.lock we get
dependencies:
- name: common
  repository: oci://registry-1.docker.io/bitnamicharts
  version: 2.13.3
digest: sha256:9a971689db0c66ea95ac2e911c05014c2b96c6077c991131ff84f2982f88fb83
generated: "2023-10-19T12:32:36.790999138Z"

and postgres Chart.lock
dependencies:
- name: common
  repository: oci://registry-1.docker.io/bitnamicharts
  version: 2.9.0
digest: sha256:416ad278a896f0e9b51d5305bef5d875c7cca6fbb64b75e1f131b04763e2aff9
generated: "2023-08-22T14:27:37.862238+02:00"

These versions of common seem to be more compatible.
Context
No response
Environment
No response

"Charts bitnami/postgresql:12.5.6 and bitnami/redis:17.17.1 are using incompatible versions of bitnami/common. The issue can be fixed by updating the bitnami/postgresql chart to a version later than 12.9.0.
Edit: Version 2.9.0 of bitnami/common was indeed backward-compatible (https://github.com/bitnami/charts/pull/18154). The issue appears to be with Helm handling conflicting dependencies.
In this case, redis:18.2.0 uses bitnami/common:2.13.3, while postgresql:12.5.6 uses bitnami/common:2.8.0. IMO, expected behavior should be that Helm should prioritise bitnami/common:2.13.3 over 2.8.0, because it is the latest under the same major."
taken from https://github.com/bitnami/charts/issues/20504

Hi @nmanovic This issue is due to unmatched versions of common sub charts in Postgres, Redis. I have separately installed common chart as sub dependency, and tested. I have faced no issues then. Please assign this issue to me.


Publish valence_nbt v0.5.0

The uploaded crate version is missing serde support from v5.0

I've just published valence_nbt v0.5


feat: add soft navigations to Browser-Agent loader

Add the Soft Navigations limited preview feature to the default Browser Agent loader accessible via NPM.

Overview

Related Issue(s)
https://new-relic.atlassian.net/browse/NR-305645

Testing

NPM test checking for features? Existing tests cover API and a couple features.
I guess do we need any assurances here?

Yeah i think thats fair. I'll update that


Add entityId to secrets, keys, and certificates

Per https://github.com/Azure/azure-sdk-for-net/issues/28564, this can be closed since the feature was cut from planning.


Fix J2Predictor.from_tle for non-epoch dates

Fix #65.

Coverage decreased (-0.02%) to 94.431% when pulling d1524a0b591a47129912b227c050647144c62d17 on Juanlu001:fix-j2-from-tle into f47ae93f0cfc666beb91d1d736e3c6fccc4513a5 on satellogic:master.

Closing this in favor of a new PR with several fixes, #69.


MistralAI python client package

What's the name of the python package? Or do you have to clone this repository to be able to use the MistralAI python client?

Should be mistralai I think: https://pypi.org/project/mistralai/

yeah I think it has to be in the README file imo #5

For sure!

Hi, sorry for the confusion on this.
You can simply use pip install mistralai in any environment such as conda or venv.
You only require the poetry dependencies when building the package from source.
Thanks!


BUG: Better error when samples.tsv is malformed

Now it's difficult for beginner users, and I've seen it happen many timtes.

I guess people were working in an old version. These checks seem quite elaborate already, and should catch plently.

some extra checks are added in configuration.smk of branch replicates.
The biggest issue (i think) is that the assert messages are drowned by the traceback.
we could set sys.tracebacklimit = 0 at the start of configuration.smk, and set sys.tracebacklimit = 1 at the end?

Isn't the message all the way at the bottom anyways? So that shouldn't matter?

It shouldn't. But reading errors can be challenging.
According to this SO post, assert shouldn't be used for these checks. That would explain why the message contains both traceback and message.
Either way, I'm OK leaving it as-is for now.

Yeah you should raise errors, but thats a lot of typing :angel:


Common: add tests for subprojects other than Scala Common Enrich to .travis.yml

Good idea! How easy do you think this will be to do?

It shouldn't be too hard - we just need to publishLocal CommonEnrich before we do the tests for projects which have it as a dependency. I can't think of any other obstacles at the moment...

Moving back since I think there's enough in r73 already.

this is done, closing


Run ant setup then ant run

This make's it a bit clearer to people who don't know Java or how to use Ant.

Thanks for the suggestion. We have added this information as part of the 1.2.0 release.


Unable to show WordPress feeds

Hi,
I am unable to show WordPress feed:
from these websites:

https://marketinginasia.com/
https://thelitmovement.com/

Possible to advice

Try adding https://marketinginasia.com/feed/ and https://thelitmovement.com/feed/

Try adding https://marketinginasia.com/feed/ and https://thelitmovement.com/feed/


Food for thought use cases: Github Actions :octocat:

I've been working on the implementation of DevSecOps Platforms and I think I came up with a Github Action that can execute the models... Obviously:

You must have Github Action Runners powered by GPUs
You can implement pretty much anything with the model given you have the file-system and the containers to implement a business logic

I have embedded the server and the pull of the models in caches to try to speed up the process

The intent is to use any model for Source-code, Software Engineering, Cloud, etc...

Just food for thought...

NOTES: I still have problems of #676 and #1072 for this reason, I build a data container with the models (docker image digests) and push them to a docker registry so that I can by-pass the 403 with a cached version of the models...

🧠 Select a Model

🏃♂ Running

🔢 Results

This is super cool. I'm excited to try it with the new GitHub Actions with GPU runners when they become available. I'll close this if it's okay, since I don't know if there are any action items to solve it


Fix etcd backend with prefix /

This PR fixes etcd backend.
It also adds integration tests for etcd & Consul ( ͡° ͜ʖ ͡°)
/cc @tboerger
Signed-off-by: Emile Vauge<EMAIL_ADDRESS>

LGTM :+1:
Thanks!

LGTM 🐸


Insufficient balance HELP

Insufficient balance even carrying out trade with BNB balance to pay fees.
What do I do to work?

Same problem here didn’t find any solution yet

please make sure you own some BNB to pay for the fees.


How to change current user to current employee

I have a model called Employee and i want pundit to authorize access to it but it displays an error
undefined local variable or method `current_user'. I know it calls current_user for the policies and I need your help on how to change it to call 'current_employee'.

It's in the README https://github.com/elabs/pundit#customize-pundit-user


[MENFORCER-490] Remove unused dependency

ITs passed locally so this doesn't appear to be needed.
If it is needed we'll need to figure out how to properly exclude this from the dependency analyzer

There is an extraArtifact options for maven-invoker-plugin ...
eventually dependency has an impact on module order


[Feature Request:] any plan to support mqtt protocol?

Contact Details
<EMAIL_ADDRESS>Is your feature request related to a problem? Please describe.
any plan to support mqtt protocol , mqtt protocol is used a lot in the iot.
thanks for your backend support.
Original Thread
No response
Describe the solution you'd like to see

support mqtt
like Wireshark ,we can add  lua script to add more protocol support.

Provide additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@OnlyPiglet we usually consider adding support for new protocols based on demand. If you'd like to become a design partner for MQTT or the second topic (Lua scripting option), please reach out to me on Slack.


only wallpaper shows up and console shows flutter error in 200804

tested the latest release (as of 17th august 2020) on a qemu virtual machine (using virt-manager gui). the os boots into desktop showing only wallpaper and tty1 showing the error as attached herein.

What wallpaper? dahliaOS Linux shows a fallback black and white dahliaOS logo, or (in 200804) a snow capped mountain.

What wallpaper? dahliaOS Linux shows a fallback black and white dahliaOS logo (if pangolin does not start), or (in 200804) a snow capped mountain if pangolin is able to start.

got the snow capped mountain but nothing else. i thought the console messages might help tell why

@diabolic-preacher qemu doesn't scale dahlia properly, you might have to scroll down to see the taskbar

@diabolic-preacher qemu doesn't scale dahlia properly, you might have to scroll down to see the taskbar

thanks for pointing that out. it is a really nice ui and i hope more dev happens on it. closing the issue here.


Include seconds in log timestamps

Currently, log timestamps only show the minutes.
To improve this, we should modify the logging system to include the seconds in the log timestamps.

I think we have seconds already:
"time":"2023-11-16T18:18:08Z"

Not in the colorful stdout log:

@b00f okay, I will fix it.


[PE-D][Tester C] Sync Command UI Bug

Sync command successfully removes meeting but does not reflect in the GUI immediately. There is a need to click on the specific contact in the list for the GUI to refresh.

Labels: severity.Medium type.FunctionalityBug
original: dexter-sim/ped#7

Is this a bug? should we fix this? solution: change how sync is done currently and change it to go through set person


[WIP] feat(default-theme): Add newsletter subscription

Work on this PR will be continued after backend fixes
Changes
closes #1756

Checklist

[ ] the list of features is updated (if it's a feature and it's relevant)
[ ] I followed contributing guidelines

@mdanilowicz  do we have an issue which blocks us here to link between repositories? available maybe here: https://issues.shopware.com


[SPARK-1855] Local checkpointing

Certain use cases of Spark involve RDDs with long lineages that must be truncated periodically (e.g. GraphX). The existing way of doing it is through rdd.checkpoint(), which is expensive because it writes to HDFS. This patch provides an alternative to truncate lineages cheaply without providing the same level of fault tolerance.
Local checkpointing writes checkpointed data to the local file system through the block manager. It is much faster than replicating to a reliable storage and provides the same semantics as long as executors do not fail. It is accessible through a new operator rdd.localCheckpoint() and leaves the old one unchanged. Users may even decide to combine the two and call the reliable one less frequently.
The bulk of this patch involves refactoring the checkpointing interface to accept custom implementations of checkpointing. Design doc.

Merged build triggered.

Merged build started.

Test build #36749 has started for   PR 7279 at commit 1324d25.

Test build #36749 has finished for   PR 7279 at commit 1324d25.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

This is very cool PR.

Thank you @witgo. :)

Merged build triggered.

Merged build started.

Test build #36756 has started for   PR 7279 at commit 6602052.

Test build #36756 has finished for   PR 7279 at commit 6602052.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36761 has started for   PR 7279 at commit d980757.

Test build #36761 has finished for   PR 7279 at commit d980757.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36815 has started for   PR 7279 at commit ee8e85e.

Test build #36815 has finished for   PR 7279 at commit ee8e85e.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36820 has started for   PR 7279 at commit 125af6f.

Merged build triggered.

Merged build started.

Test build #36826 has started for   PR 7279 at commit 03f3126.

Test build #36826 has finished for   PR 7279 at commit 03f3126.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #36836 has started for   PR 7279 at commit 3d4a717.

Test build #36836 has finished for   PR 7279 at commit 3d4a717.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #36820 has finished for   PR 7279 at commit 125af6f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36882 has started for   PR 7279 at commit 5da18c7.

Test build #36882 has finished for   PR 7279 at commit 5da18c7.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Test build #36885 has started for   PR 7279 at commit c449b38.

Merged build finished. Test FAILed.

Test build #1017 has started for   PR 7279 at commit c449b38.

Test build #1018 has started for   PR 7279 at commit c449b38.

Test build #1017 has finished for   PR 7279 at commit c449b38.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #36885 has finished for   PR 7279 at commit c449b38.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test build #1018 has finished for   PR 7279 at commit c449b38.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build triggered.

Merged build started.

Test build #37169 has started for   PR 7279 at commit db70dc2.

Test build #37169 timed out     for PR 7279 at commit db70dc2     after a configured wait of 175m.

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #37204 has started for   PR 7279 at commit db70dc2.

Test build #37204 timed out     for PR 7279 at commit db70dc2     after a configured wait of 175m.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #37306 has started for   PR 7279 at commit 4eb6eb1.

Test build #37306 has finished for   PR 7279 at commit 4eb6eb1.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class Exchange(newPartitioning: Partitioning, child: SparkPlan) extends UnaryNode

Merged build finished. Test PASSed.

@tdas can you start looking at this?

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Test build #1079 has started for   PR 7279 at commit a92657d.

Test build #1080 has started for   PR 7279 at commit a92657d.

Test build #1081 has started for   PR 7279 at commit a92657d.

Test build #1080 has finished for   PR 7279 at commit a92657d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #1081 has finished for   PR 7279 at commit a92657d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #1079 has finished for   PR 7279 at commit a92657d.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #1089 has started for   PR 7279 at commit a92657d.

Test build #1091 has started for   PR 7279 at commit a92657d.

Test build #1091 has finished for   PR 7279 at commit a92657d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #1089 has finished for   PR 7279 at commit a92657d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build triggered.

Merged build started.

Test build #37549 has started for   PR 7279 at commit f5be0f3.

Test build #37549 has finished for   PR 7279 at commit f5be0f3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #37568 has started for   PR 7279 at commit e908a42.

Test build #37568 has finished for   PR 7279 at commit e908a42.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Hi all, I spent some time benchmarking the performance improvements of this feature. I ran the following on a 4-node m1.xlarge cluster with 6 executors, each with 4g of memory. The numbers reported here are the median over 10 runs.
Micro-benchmark. Checkpoint a ~700MB input RDD

normal checkpoint: 9337ms
local checkpoint: 1599ms
improvement: 82.9%

Macro-benchmark. Run EM LDA on a ~235MB file on HDFS

--maxIterations = 20
--checkpointInterval = 2
--k = 10
normal checkpoint: 96078ms
local checkpoint: 79592ms
improvement: 17.2%

The performance improvement in LDA is not as dramatic as the micro benchmark. This is because the majority of time is spent on actual computation rather than checkpointing.

This is a very good performance for ML.    I will test this feature on cloudml/zen

Merged build triggered.

@witgo super cool! I'd be interested to hear back from your benchmark results.
@tdas I believe I addressed all of your comments. Please have another look.

Merged build started.

Test build #38622 has started for   PR 7279 at commit c2e111b.

Test build #38622 has finished for   PR 7279 at commit c2e111b.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  case class RequestExecutors(
class RFormula(override val uid: String) extends Estimator[RFormulaModel] with RFormulaBase

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #38652 has started for   PR 7279 at commit 3b7dc6a.

Test build #38652 has finished for   PR 7279 at commit 3b7dc6a.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38722 has started for   PR 7279 at commit ab003a3.

Test build #38722 has finished for   PR 7279 at commit ab003a3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Ping @tdas can you do a final sign-off?

I did a pass. And there is one critical question that is not clear to me -- how does the LocalCheckpointRDDData.doCheckpoint() work in a distributed manner.

OK, I fixed the concern with the local doCheckpoint(). That was a good catch.

Merged build triggered.

Merged build started.

Test build #39406 has started for   PR 7279 at commit 3be5aea.

Test build #39406 has finished for   PR 7279 at commit 3be5aea.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
      class SpecificSafeProjection extends $
case class FromUTCTimestamp(left: Expression, right: Expression)
case class ToUTCTimestamp(left: Expression, right: Expression)
case class DateDiff(endDate: Expression, startDate: Expression)
case class InitCap(child: Expression) extends UnaryExpression with ImplicitCastInputTypes

Merged build finished. Test FAILed.

retest this please

Test build #1281 has started for   PR 7279 at commit 3be5aea.

Test build #1282 has started for   PR 7279 at commit 3be5aea.

Merged build triggered.

Merged build started.

Test build #39442 has started for   PR 7279 at commit 3be5aea.

Test build #1282 has finished for   PR 7279 at commit 3be5aea.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #1281 has finished for   PR 7279 at commit 3be5aea.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #39442 has finished for   PR 7279 at commit 3be5aea.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #39466 has started for   PR 7279 at commit 34bc059.

Test build #1284 has started for   PR 7279 at commit 34bc059.

Test build #1285 has started for   PR 7279 at commit 34bc059.

Test build #1286 has started for   PR 7279 at commit 34bc059.

Test build #1284 has finished for   PR 7279 at commit 34bc059.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class JavaKMeansExample
 class FreqSequence[Item](val sequence: Array[Array[Item]], val freq: Long) extends Serializable
class PrefixSpanModel[Item](val freqSequences: RDD[PrefixSpan.FreqSequence[Item]])
      class SpecificSafeProjection extends $
case class FromUTCTimestamp(left: Expression, right: Expression)
case class ToUTCTimestamp(left: Expression, right: Expression)
case class DateDiff(endDate: Expression, startDate: Expression)
case class InitCap(child: Expression) extends UnaryExpression with ImplicitCastInputTypes
public final class UnsafeKVExternalSorter

Test build #1285 has finished for   PR 7279 at commit 34bc059.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
 class FreqSequence[Item](val sequence: Array[Array[Item]], val freq: Long) extends Serializable
class PrefixSpanModel[Item](val freqSequences: RDD[PrefixSpan.FreqSequence[Item]])
public final class UnsafeKVExternalSorter

Test build #39466 has finished for   PR 7279 at commit 34bc059.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test build #1286 has finished for   PR 7279 at commit 34bc059.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build triggered.

Merged build started.

Test build #1300 has started for   PR 7279 at commit 34bc059.

Test build #39495 has started for   PR 7279 at commit 729600f.

Test build #1301 has started for   PR 7279 at commit 729600f.

Test build #1302 has started for   PR 7279 at commit 729600f.

Test build #39495 has finished for   PR 7279 at commit 729600f.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  case class RequestExecutors(appId: String, requestedTotal: Int)
  case class KillExecutors(appId: String, executorIds: Seq[String])
public class JavaKMeansExample
 class FreqSequence[Item](val sequence: Array[Array[Item]], val freq: Long) extends Serializable
class PrefixSpanModel[Item](val freqSequences: RDD[PrefixSpan.FreqSequence[Item]])
      class SpecificSafeProjection extends $
case class FromUTCTimestamp(left: Expression, right: Expression)
case class ToUTCTimestamp(left: Expression, right: Expression)
case class DateDiff(endDate: Expression, startDate: Expression)
case class InitCap(child: Expression) extends UnaryExpression with ImplicitCastInputTypes
public final class UnsafeKVExternalSorter

Merged build finished. Test FAILed.

Test build #1301 has finished for   PR 7279 at commit 729600f.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #1300 has finished for   PR 7279 at commit 34bc059.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #1302 timed out     for PR 7279 at commit 729600f     after a configured wait of 175m.

retest this please

Merged build triggered.

Merged build started.

Test build #39536 has started for   PR 7279 at commit 729600f.

Test build #39536 has finished for   PR 7279 at commit 729600f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test build #1304 has started for   PR 7279 at commit 729600f.

Test build #1304 has finished for   PR 7279 at commit 729600f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

@tdas good to go?

Yep, LGTM. Merging this to master. Great patch!! Thanks!


sonnet via litellm proxy

          Thanks. I have installed it and will try it out.

I think I have an issue, though. I launch it like this:
aider --model-metadata-file ~/claude_3_5_sonnet.json --model openai/claude-3-5-sonnet

It uses a Sonnet 3.5 model, hosted on AWS, running through a LiteLLM proxy. So this gives it an OpenAI API, but the model is Anthropic. We have a metadata file (below) that controls how it behaves. However now, I don't think this is working anymore.
Metadata file:
{
    "claude-3-5-sonnet": {
        "max_tokens": 4096,
        "max_input_tokens": 200000,
        "max_output_tokens": 4096,
        "input_cost_per_token": 0.000003,
        "output_cost_per_token": 0.000015,
        "litellm_provider": "anthropic",
        "mode": "chat",
        "supports_function_calling": true,
        "supports_vision": true,
        "tool_use_system_prompt_tokens": 159,
        "supports_assistant_prefill": true
    }
}

And the warning on startup:
Model openai/claude-3-5-sonnet: Unknown context window size and costs, using sane
defaults.
Did you mean one of these?
- anthropic/claude-3-5-sonnet
- claude-3-5-sonnet
For more info, see: https://aider.chat/docs/llms/warnings.html

Has something changed in this area?
Originally posted by @efunneko in https://github.com/paul-gauthier/aider/issues/1223#issuecomment-2322157670

@efunneko
I think you may want to do change your metadata file to be like this. The key should match the model, so openai/claude-3-5-sonnet. And maybe you want "litellm_provider": "openai" not anthropic.
Hard for me to know for sure, given this is a custom setup.
{
    "openai/claude-3-5-sonnet": {
        "max_tokens": 4096,
        "max_input_tokens": 200000,
        "max_output_tokens": 4096,
        "input_cost_per_token": 0.000003,
        "output_cost_per_token": 0.000015,
        "litellm_provider": "openai",
        "mode": "chat",
        "supports_function_calling": true,
        "supports_vision": true,
        "tool_use_system_prompt_tokens": 159,
        "supports_assistant_prefill": true
    }
}

Thanks for your suggestions. It turns out that the key in the file seems to work with and without the "openai/" prefix, but the litellm_provider needs to be set to openai.
One question I still have is whether I am missing out on any Sonnet specific optimizations in aider if it thinks I am using openai but really am using sonnet?

You will need to make sure your model settings and model metadata reflect the values for Sonnet. See aider/models.py for details on how Sonnet's settings are configured.
https://aider.chat/docs/config/adv-model-settings.html

I'm going to close this issue for now, but feel free to add a comment here and I will re-open. Or feel free to file a new issue any time.


Correct database deletion logic

Right now the databases are deleted (if they are not to be persisted) when the __del__ method is invoked, which is incorrect.

Fixed in 42a4ddf36f6c7a170169ba5fa8d3cf5eccd274ae


New version: IGGInc.Doomsday version 1.0.23

Pull request has been created with komac v2.1.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

This package installs and launches normally on a Windows 10 VM.


Add spin-up capabilities for ClimaAtmos simulations

For many climate simulations, it is necessary to run a simulation for multiple turn-over times before a statistically stationary state is reached and a usable start-up condition is achieved. For high resolution simulations, this start-up phase can be expensive. It is generally desirable to start the spin-up simulation at a lower resolution and gradually increase the resolution to the target resolution.
### Tasks
- [ ] Add capability to refine each spectral element into (4) spectral elements to help speedup spin-up simulations

cc: @charleskawczynski @cmbengue @tapios

Yes, this will be a useful capability to have. Before you get started on it, can you please estimate how long it'll take to build this?

Would it be easier if we add the capability for reading initial condition from a netcdf file and interpolate? If we do this we won't be constrained by the resolution (both horizontal and vertical).

Would it be easier if we add the capability for reading initial condition from a netcdf file and interpolate? If we do this we won't be constrained by the resolution (both horizontal and vertical).

ClimaUtilities provides capabilities to accomplish this non-conservatively (using InterpolationsRegridder--multi-linear interpolation), or conservatively with the same vertical levels as the file (using TempestRegridder).

I think interpolating the state / cache is fine, but I think we should still have a way to compute the local geometry given the types of previous data with the new resolution. This way, we don't have errors in mass/energy transport on restarted simulations.

Would it be easier if we add the capability for reading initial condition from a netcdf file and interpolate? If we do this we won't be constrained by the resolution (both horizontal and vertical).

The plan is to write the restart data to the new (finer) grid.


Dispatching an action from middleware results in a strange behavior

I'm asking this question on SO, but nobody ask me. I'm not sure that it's a bug, but behavior is very strange for me.
If it's works as expected, can you please explain me, why.
Here is a code:
const middlewareOne = store => next => action => {
        console.log('Middleware one recived action', action.type)
        switch (action.type) {
          case 'A':
            return next({ type: 'B' })
          default:
            return next(action)
        }
      }

const middlewareTwo = store => next => action => {
  console.log('Middleware two recived action', action.type)
  switch (action.type) {
      case 'B':
          store.dispatch({ type: 'D' })
          return next({ type: 'C' })
      default:
          return next(action)
  }
}

function reducer(state, action)
  console.log('Reducer received action', action.type)
      return state
}

I have actions A, B, C, and D, two middlewares, and reducer. First middleware receives action A and produces action B by calling next() function.
Second middleware receives action B and produces action C, and, dispatches an action D.
As I understand, there is nothing wrong with dispatching actions from middleware, but the result was very surprising for me.
Here is a console output for this code
Middleware one receive action A
Middleware two receive action B
Middleware one receive action D
Middleware two receive action D
Reducer received action D
Reducer received action C

So, what I except: As I know, next() function passes the action to the next middleware or to the reducer if there are no middlewares in the chain, but dispatch puts action to the beginning of the pipeline (all middlewares and finally, the reducer). So, with that idea in mind, I think that action C will be reduced at first (since it's already in the middlewares pipeline), and only after that middlewares start to processing action D, but the result is completely opposite.
@markerikson I saw a lot of helpful messages from you over the internet, maybe you can help with that. Thanks in advice.
Best regards, Vitaly Sulimov.

Dispatching is synchronous, so if you dispatch before calling next that will be processed fully before returning to the original call site and proceeding to the next middleware. The result here is entirely expected.


[MODFISTO-511] - Update script to avoid duplication issue

Purpose

https://folio-org.atlassian.net/browse/MODFISTO-511
Approach

use jsonb_set to avoid duplication
make sql script produce the same result after multiple run

Previously

correct calculation should be like this

after run script


[4.4-dev] Metal render incorrectly renders label font colors

Tested versions

Reproducible in 4.4-dev 1 and 2, on macOS and iOS

System information
macOS & iOS - Metal (Mobile & Forward+) v4.4.dev2.official [97ef3c837]
Issue description
Using the new renderer, labels are using a black font color for default state and only change color in hover and selected states.
Applies to both Mobile and Forward+, on macOS and iOS.
Metal (mobile):

Vulkan (mobile):

Steps to reproduce

Load 4.4-dev1 or later on macOS using default rendering devices.

Minimal reproduction project (MRP)
Any project.

Do you have font LCD antialiasing enabled?

Ah yes. Considering I opened #93606 I probably should have thought to check :joy:
Works OK on grayscale both in editor and in game.

#97217 closes this issue


Package Requested

[X] I would like someone else to build the manifest.
[X] I would like help so I can submit the manifest.
[X] I have performed a search and couldn't find this package.
[X] I have checked that the installer for this package is not a standalone or portable executable or a .zip file
[ ] I think there is a new version available and I have provided the URL.

Please provide the following information
Current Package Identifier: GNURadio.GNURadio
Not sure if the url went 404 recently, but as of now it is
https://github.com/gnuradio/gnuradio
https://wiki.gnuradio.org/index.php/InstallingGR#Windows

The link works for me:

Just found the issue... Firefox insisted on doing HTTPS which the webpage does not support...


[AIRFLOW-274] Add XCom functionality to GoogleCloudStorageDownloadOperator

Dear Airflow Maintainers,
Please accept this PR that addresses the following issues:
[AIRFLOW-274]: I have updated GoogleCloudStorageDownloadOperator so that it has the option to store the downloaded file's contents in an XCom instead of saving to disk. It now also takes filename as an optional argument instead of a required argument, so it is not necessary to save to disk if you do not need to.
Testing Done: I ran a DAG that relies on this functionality and it ran correctly.

[Current coverage][cc-pull] is 64.08%

Merging [#1618][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master      #1618   diff @@
==========================================
  Files           121        121
  Lines          8462       8462
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           5423       5423
  Misses         3039       3039
  Partials          0          0

Powered by Codecov. Last updated by [7f6d877...c7bf362][cc-compare]
[cc-base-branch]: https://codecov.io/gh/apache/incubator-airflow/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/apache/incubator-airflow/compare/7f6d877409175cf5b0049406d808030d58dcdb24...c7bf3628ac16d925ab3c80434918a1e35b894339
[cc-pull]: https://codecov.io/gh/apache/incubator-airflow/pull/1618?src=pr

Rest looks good. Two nits:

Please open a JIRA: https://issues.apache.org/jira/browse/AIRFLOW
Can you please rename the PR to include [AIRFLOW-XXX], that matches the ticket number of the JIRA you opened.

Done and done.

In addition: dont forget to squash your commits, provide a proper commit message and an imperative title. If you can provide some tests.

LGTM! Merged

Nice! A future extension might be to make the key a templated field.

@jlowin good point. Should be pretty trivial to add (just a one liner, right?)

@jlowin @criccomini Not super familiar with how templated fields are implemented. Is there anything to do besides adding it to the list in template_fields = ('bucket','object','filename',)?

Nope, that's it.