golem: 1.0.27 -> 1.1.0

Diff: https://github.com/golemcloud/golem/compare/refs/tags/v1.0.27...v1.1.0
Changelog: https://github.com/golemcloud/golem/releases/tag/v1.1.0

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@GaetanLepage  sorry to ping you again, but can you take a look at this one as well, added myself as maintainer now


Cannot build the ndk immediately after cloning the repo

Expected behavior
When I clone the application, I can run make build and build all the .so files
Observed behavior
I get the following stack trace
FAILURE: Build failed with an exception.

* Where:
Build file '/Users/maltz/Documents/workspace/bugsnag-android-ndk/build.gradle' line: 41

* What went wrong:
A problem occurred evaluating root project 'bugsnag-android-ndk'.
> Unable to generate signature for '/Users/maltz/Documents/workspace/bugsnag-android-ndk/ndk/build/outputs/aar/ndk-release.aar' as no signatory is available to sign

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

* Get more help at https://help.gradle.org

BUILD FAILED in 1s
make: *** [build] Error 1

Steps to reproduce
Clone repository, run make build
Version
1.1.2
Additional information
Nope!
Can't comment on Issues?
Some users have been unable to comment on Github issues when an adblocker extension is enabled.
We recommend temporarily disabling the extension, or if that fails, contacting<EMAIL_ADDRESS>

@maltzj sorry for the delay on this. This is down to the Gradle signing plugin being unable to find signing information. You can find further information here, but essentially you'll need to generate a key pair and add the following information to ~/.gradle/gradle.properties:
signing.keyId=
signing.password=
signing.secretKeyRingFile=/Users/<user>/.gnupg/secring.gpg

I'm leaving this issue open for now as we either need to document this, or only apply the signing plugin when making a release.


initial commit for generic proxy stats

Commit Message: initial commit for generic proxy stats
Additional Description: N.A.
Risk Level: Low
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

run the ci/do_ci.sh format should will fix your format error.

@wbpcode don't forget to tag as waiting please! :-)
/wait on comments

/retest

could you merge the main and repush the branch? I think the CI is broken and you may need to kick it.

closed #27801


Binding Parameter Validation Expressions

We should consider extending the syntax we have in place now for binding parameters (e.g. {age}) to allow declarative validations to also be specified (e.g. {age:int}). This would be similar to ASP.NET route parameter validation expressions (see here).
This would allow people to put declarative rules in place and error early with meaningful errors when chaining bindings together. E.g. if a QueueTrigger is bound to a Table input binding, the binding template for TableAttribute.Filter might be Age gt {age:int} and Location eq '{location:alpha}'. This will give errors earlier, rather than failing in the storage layer due to type mismatch error.
This might be even more useful in output binding scenarios, where you want to ensure data is sanitized before being stored (e.g. blob path components, document IDs, etc.)

This issue is replaced by https://github.com/Azure/azure-webjobs-sdk/issues/980, so closing this. If we do that work, Functions could build on that foundation to add a declarative trigger binding data validation model.


feat(broadcastQueryClient): experimental support for tab/window syncing

This PR relies on #1792

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add files via upload

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
What did you learn from the changes you have made?
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
How were these changes tested?
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended

A2: Incomplete
You have submitted an old version of the assignment. The dataset we used is Miles per Gallon, please upload the latest version and submit the assignment as soon as possible. Thanks

A2: Incomplete
You have submitted an old version of the assignment. The dataset we used is Miles per Gallon, please upload the latest version and submit the assignment as soon as possible. Thanks

A2: Incomplete
You have submitted an old version of the assignment. The dataset we used is Miles per Gallon, please upload the latest version and submit the assignment as soon as possible. Thanks

Hi, assignment completed and completed pull request.  TY

A2: Complete
Q3: I would examine the following " numeric_predictors = mpg_train[column_names] " . Think of which numeric predictors we are interested in keeping to fit in the linear model. Thus which of the 8 predictors are numeric predictors of interest.
Q4: As opposed to using "np.mean" I would recommend using 'mean_squared_error"  function from the library you are calling


golang: replace deprecated ioutil package references

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

Remove and replace references to deprecated ioutil package.
https://pkg.go.dev/io/ioutil
"Deprecated: As of Go 1.16, the same functionality is now provided by package io or package os, and those implementations should be preferred in new code."
Change Log

Remove all references in .go files of io/ioutil package
Replace with their corresponding implementation io and os package, specifically:
ioutil.ReadDir -> os.ReadDir
ioutil.ReadFile -> os.ReadFile
ioutil.WriteFile -> os.WriteFile
ioutil.Discard -> io.Discard
ioutil.ReadAll -> io.ReadAll

Does this affect the toolchain?

NO
Test Methodology

Searched through our github repo to find all the files using this package
Used a golang code editor

@neha170 The only interesting one to test here is ReadDir as it has a different return type, the rest are completely the same as per linked documentation. I'll look into it and update the description and PR if needed

Updated description with testing methodology.


Can you support tronprotocol?

Hello，I am a block chain development enthusiasts.
Recently, I found tronprotocol support smart contract right now.
Do you have plan to support tronprotocol in your project?
The tronprotocol url is below:
https://github.com/tronprotocol/java-tron

We have no plan to support tronprotocol.  If you'd like to contribute supporting it,  we appreciate it.

Since the support is not planned in the foreseeable future, I'm closing this thread.


Policies for the EKS CIS  Rules

Any idea , where can we find the policies related/similar to the below rules:

Ensure that the cluster-admin role is only used where required
Minimize wildcards use in roles and clusterroles

I wanted to have a policy for 3. Minimize access to create pods	, for which I could tweak this:
https://kyverno.io/policies/other/block_updates_deletes/
But could not find policies/related to 1 & 2. Any leads would be helpful.
Thanks in advance.

The CIS benchmarks are Kubernetes cluster best practices/configurations and not really policy opportunities in most cases. Kyverno can be used to assist in these regards, but you still have to define what you want in your environment. So for item number one, what does "where required" mean for you? Similar with two.

Closing if nothing further.


[master] support ubuntu22

Signed-off-by: wngzhe<EMAIL_ADDRESS>issue:
https://github.ibm.com/zvc/planning/issues/10324
code change :
support ubuntu22 deploy

@SeanHQF @bjhuangr  please help review


Update munit, munit-scalacheck to 0.7.14

Updates

org.scalameta:munit
org.scalameta:munit-scalacheck

from 0.7.13 to 0.7.14.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta" } ]

labels: test-library-update, semver-patch

Codecov Report

Merging #347 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #347   +/-   ##
=======================================
  Coverage   62.84%   62.84%
=======================================
  Files          38       38
  Lines        1281     1281
  Branches        8        5    -3
=======================================
  Hits          805      805
  Misses        476      476

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 171b873...29fef1a. Read the comment docs.


Sharp drop in analytics with 1.7.8 release

We've seen a sharp drop in the analytics returned by 1.7.8. We need to either:

root cause the issue and apply a fix, or
understand the drop as incorrect analytics before.

May be related to https://github.com/flutter/flutter/pull/34179.

Fix for https://github.com/flutter/flutter/pull/34179 landed here https://github.com/flutter/flutter/pull/36208
A larger culprit is probably failing to send analytics when killed by a signal. The fix for that landed here: https://github.com/flutter/flutter/pull/36490
When these changes hit dev we should start getting some signal indicating whether these fixes are sufficient, or if there is some other problem.

We're currently waiting on a dev release to validate that the fixes are sufficient. If so, we can close the issue

@jonahwilliams We have had a dev release now, what is the conclusion?

Early signals indicate that this may be fixed. dev/1.8.3 is recording ~3x run commands per user over dev/1.8.2. I will close this, and we can open a new issue if the numbers don't totally recover.


Add List of Popular YouTube Channels

I can contribute

Hey , I am willing to work on this issue . You may assign this under hacktoberfest 2022 tag.


Implement basic status tab, resolves #70

Description
Implement basic status tab showing basic player information such as fuel and ship integrity. Also a basic "profile picture" is shown also in ASCII.
Alternate Designs
N/A
Benefits
N/A
Possible Drawbacks
N/A
Applicable Issues
#70

Codecov Report

Merging #80 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #80   +/-   ##
=======================================
  Coverage   97.27%   97.27%
=======================================
  Files           3        3
  Lines         147      147
=======================================
  Hits          143      143
  Misses          4        4

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3414738...8757001. Read the comment docs.


add _TZE200_9yapgbuv to TuyaTempHumiditySensorVar03

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.551%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
6791

Relevant Lines:
8128

💛  - Coveralls

Nice! Did you test if this change works for that new sensor (using a custom quirk for example)?

Yes, I have two of two devices in my Home Assistant setup, where I patched
the file with the file I submitted. Humidity and temperature work.
On Mon, Jan 16, 2023 at 4:18 PM TheJulianJES @.***>
wrote:

Nice! Did you test if this change works for that new sensor (using a
custom quirk for example)?
—
Reply to this email directly, view it on GitHub
https://github.com/zigpy/zha-device-handlers/pull/2105#issuecomment-1384203109,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARJPHA6M447E7EEDTILRMKTWSVREDANCNFSM6AAAAAAT43CILQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Codecov Report
Base: 83.55% // Head: 83.55% // No change to project coverage :thumbsup:

Coverage data is based on head (2d7e5b2) compared to base (1891e3f).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev    #2105   +/-   ##
=======================================
  Coverage   83.55%   83.55%
=======================================
  Files         252      252
  Lines        8128     8128
=======================================
  Hits         6791     6791
  Misses       1337     1337

Impacted Files
Coverage Δ

zhaquirks/tuya/ts0601_sensor.py
100.00% <ø> (ø)

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

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

Related issue:
https://github.com/zigpy/zha-device-handlers/issues/1918

I was going to point the diference between those same 2 issues.
Thank you @marktimmerman-dev  for taking the trouble to create a PR and contribute to the library.


          -----------------------------
               .OMMMMo           OS: macOS 13.2.1 22D68 arm64
               OMMM0,            Host: Mac14,9
     .;loddo:' loolloddol;.      Kernel: 22.3.0
   cKMMMMMMMMMMNWMMMMMMMMMM0:    Uptime: 14 hours, 5 mins
 .KMMMMMMMMMMMMMMMMMMMMMMMWd.    Packages: 43 (brew)
 XMMMMMMMMMMMMMMMMMMMMMMMX.      Shell: zsh 5.8.1
;MMMMMMMMMMMMMMMMMMMMMMMM:       Resolution: 1352x878@2x
:MMMMMMMMMMMMMMMMMMMMMMMM:       DE: Aqua
.MMMMMMMMMMMMMMMMMMMMMMMMX.      WM: yabai
 kMMMMMMMMMMMMMMMMMMMMMMMMWd.    Terminal: WarpTerminal
 .XMMMMMMMMMMMMMMMMMMMMMMMMMMk   CPU: Apple M2 Pro
  .XMMMMMMMMMMMMMMMMMMMMMMMMK.   GPU: Apple M2 Pro
    kMMMMMMMMMMMMMMMMMMMMMMd     Memory: 3660MiB / 32768MiB
     ;KMMMMMMMWXXWMMMMMMMk.
       .cooc,.    .,coo:.

borders do not work properly on Ventura, just disable them.

Or make normal window border transparent. I was using it like that from the start and wasn't even aware of that bug.

Borders have been removed in the latest release (v6.0.0) (#1889) because of multiple issues present in both Ventura and Sonoma.


ST_Transform Inverting XY

I have a shapefile in EPSG: 3857, when I use ST_Transform to reproject to 4326, the XY values appear to be flipped. But Geopandas seems to output the correct data
Here is duckdb

and here is with geopandas

and here is the source EPSG info

am i missing something?

Hi! EPSG:4326 is standardized to mandate a latitude/longitude axis order, compared to 3857 that is lon/lat, which is why it flips. We are probably going to change this in the future, but for now you can pass "always_xy := true" to ST_Transform as a third optional argument to force xy convention.

When passing that flag, I get "Binder Error: No function matches the given name and argument types"  or with using the ODBC connection

i've tried always_xy=True,  always_xy:=True, 'always_xy=True', and 'always_xy:=True'


fix features and add ci

ok, tested on https://github.com/axodotdev/axoproject/pull/13 and it compiles and tests pass so gonna cut the point release now


Py 312 support

Adds python 3.12 to CI and noxfile to run tests against latest version.
All tests pass, neede to bump pytest version which also includes 3.12 support.

There is a speeling error in the ci.yml, which is causing 3.12 tests to fail.


Archive (methods) features

Hi,
Any chance the archive methods (getArchive, getArchiveInformation, putArchive) on the ContainerManager will receive some extra code to parse the reponse from the Docker API?
According to the Docker API documentation it returns a TAR STREAM but I'm just testing to read a simple text file in a container. When I read out the contents it prepends a file header (I think) with filename along with the contents of the file. So not sure how to parse it correctly.
Maybe someone can show me a way to run things like cat text.txt and save that in a variable, that would be fine to.
Thanks!

Done in 2.0


Working but live capture is pixelated.

Thanks for your work. Updated to Swift 3 / iOS 10 and all is working.
The pixelation is coming from  FaceObscurationFilter but is this all the app is meant to do? Anything you point the camera at is pixelated so where does the Face Detector come into play?

Same here :(

Thanks to both of you - I'm aware of the issue and will fix it as soon as I get some spare time!

@tysun @jacktuck This should now be working. Thank you for finding it! 😃


WHY IS WSL TAKING SO MUCH SPACE

Windows Version
Win 11
WSL Version
I DONT KNOW
Are you using WSL 1 or WSL 2?

[x] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
No response
Other Software
WHY DOES WSL TAKE 300 GB? ?????

Repro Steps
WHY DOES WSL TAKE 300 GB? ?????

WHY DOES WSL TAKE 300 GB? ?????

WHY DOES WSL TAKE 300 GB? ?????

WHY DOES WSL TAKE 300 GB? ?????

Expected Behavior
WHY DOES WSL TAKE 300 GB? ?????

WHY DOES WSL TAKE 300 GB? ?????

WHY DOES WSL TAKE 300 GB? ?????

WHY DOES WSL TAKE 300 GB? ?????

Actual Behavior
WHY DOES WSL TAKE 300 GB? ?????

WHY DOES WSL TAKE 300 GB? ?????

WHY DOES WSL TAKE 300 GB? ?????

WHY DOES WSL TAKE 300 GB? ?????

Diagnostic Logs
WHY DOES WSL TAKE 300 GB? ?????

WHY DOES WSL TAKE 300 GB? ?????

WHY DOES WSL TAKE 300 GB? ?????

WHY DOES WSL TAKE 300 GB? ?????


Update smoke tests to run in parallel

We should be able to run ctest in parallel with the -j flag. Currently our smoke tests are preventing us from doing that.

We have parallelized the portions of the tests that we can. Closing.


[efr32] Is MBEDTLS_SSL_MAX_CONTENT_LEN correct?

Hi all, browsing the code I saw that MBEDTLS_SSL_MAX_CONTENT_LEN is defined as 768 for the efr32 platform, here:
https://github.com/openthread/openthread/blob/968440da34c1f569035e9338dd4bef7fcb970adb/examples/platforms/efr32/src/mbedtls_config.h#L13-L17
However, in the generic OpenThread mbedTLS config file, MBEDTLS_SSL_MAX_CONTENT_LEN is defined conditionally as 768 or 900, depending on OPENTHREAD_CONFIG_COAP_SECURE_API_ENABLE, here:
https://github.com/openthread/openthread/blob/c00cb8a4c4f6e2a619770ffbb4abfd0f36a7fdc2/third_party/mbedtls/mbedtls-config.h#L127-L131
Is the efr32 config file correct?

@dismirlian - thanks for finding this.  This does indeed look to be a bug.  Feel free to submit a PR with the fix.  Should be just including the same logic from the generic OpenThread mbedTLS config file in the efr32 platform specific version,

@romacdon, just a thought... can't we rely on the generic config file for all the common logic and required modules, and only use the efr32-specific file for the efr32-specific acceleration configs? I think this is how it was done on the efr32 platform before #5666 (see MBEDTLS_USER_CONFIG_FILE).

@dismirlian I believe there were some issues that we encountered when we initially tried that but I will have to defer to @lmnotran for the details. It could be that the issues we hit are no longer relevant and we could go back to the approach that use to be in place and that you are recommending we use again now.

Hi @dismirlian - To give you some context behind the switch from efr32-mbedtls-config.h to mbedtls_autogen_config.h, one of the changes we made when updating to Gecko SDK v3.0 (GSDK) was switching from the built-in mbedtls distribution to the mbedtls distribution that's included in the GSDK.
Part of this change involved switching to the auto-generated mbedtls_autogen_config.h files we have today. These autogen'd files are taken directly from a project generated by using Simplicity Studio 5 and are unmodified to allow for newer versions to be generated and dropped in with ease. This is especially prudent because, eventually, we'd like to get rid of these manually generated files and have the config generation done as part of the build process.
As a consequence of taking the mbedtls_autogen_config.h files whole and unmodified, there are a lot of redefined macros between efr32mg12/src/crypto/mbedtls_autogen_config.h, for example, and the built-in generic mbedtls config file.
Per your suggestion, we could create a new efr32-mbedtls-config.h that only contains efr32-specific acceleration configs, but that may make it more labor-intensive to pull in mbedtls config updates as opposed to importing the autogen'd files whole.
For now, I can just fix examples/platforms/efr32/src/mbedtls_config.h to have the same conditionally defined MBEDTLS_SSL_MAX_CONTENT_LEN as third_party/mbedtls/mbedtls-config.h
Any thoughts or concerns?

Hi @lmnotran, thanks for the extra context; the reason for this is clear now. My only concern is that the efr32 platform will have to manually keep up with the changes in the default/generic OT mbedTLS config file.

@dismirlian That's a completely valid concern. I don't expect this to be too much of a problem since it doesn't look like the default mbedTLS config file isn't changed very frequently https://github.com/openthread/openthread/commits/master/third_party/mbedtls/mbedtls-config.h


SIGSEGV in org.hibernate.engine.spi.CollectionKey

Please provide a brief summary of the bug
The bug manifests itself some time after the application is launched in the Tomcat servlet container.
Please provide steps to reproduce where possible
Ready to reproduce if necessary and send the necessary data.
Expected Results
No crash
Actual Results
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x00007f24aaccc0a0, pid=87934, tid=88033
JRE version: OpenJDK Runtime Environment Temurin-11.0.12+7 (11.0.12+7) (build 11.0.12+7)
Java VM: OpenJDK 64-Bit Server VM Temurin-11.0.12+7 (11.0.12+7, mixed mode, tiered, compressed oops, parallel gc, linux-amd64)
Problematic frame:
J 21973 c1 org.hibernate.engine.spi.CollectionKey.(Lorg/hibernate/persister/collection/CollectionPersister;Ljava/io/Serializable;)V (38 bytes) @ 0x00007f24aaccc0a0 [0x00007f24aaccc060+0x0000000000000040]
What Java Version are you using?
OpenJDK Runtime Environment Temurin-11.0.12+7 (build 11.0.12+7)
What is your operating system and platform?
Ubuntu 20.04.5 LTS, x64
How did you install Java?
Binary archive, tar.gz.
Did it work before?
This worked before updating the OS version from 18.04 to 20.04.

Did you test with other Java versions?
No

Relevant log output
No response

dup of #654


pint does not parse well unit with exponents

Some units consists of multiple set of parenthesis, with exponents -1 (e.g. next line). However they are not parsed correctly by pint.
https://github.com/DocOtak/gsw-xarray/blob/08a13415e0993ae2b76991d956b569c239d842a6/gsw_xarray/_attributes.py#L651
import cf_xarray.units  # must be imported before pint_xarray
import pint_xarray
from pint_xarray import unit_registry as ureg

ureg('(kg/m^3)*(g/kg)^-1')

outputs (what we want):
1.0 kilogram2/(gram meter3)

but without the star
ureg('(kg/m^3)(g/kg)^-1')

output
1.0 meter3/gram

I opened an issue in pint about this: https://github.com/hgrecco/pint/issues/1730. In the meantime, we should replace these unit with either a '*' between the parenthesis, or with an extra set of parenthesis.
Any opinion on which solution we should implement?

cc @keewis @aulemahal

Maybe (kg/m^3)/(g/kg) and just avoid the exponent?
udunits2 thinks all these options are equal to 1000 m^-3 kg i.e. cancels the g/kg to scaling constant.

So I confirm that this is an issue from pint, that was already described (https://github.com/hgrecco/pint/issues/1485). The take home message for us is that we should not use parenthesis without the * sign outside of them.


Migration instructions

I'm curious what a migration should look to set up my database (psql) for use with  Timex.Ecto.DateTimeWithTimezone, there has been some commentary on this issue (https://github.com/bitwalker/timex/issues/133) about it and I've used something similar.
Is there a better way to do this?

I should mention I'm using something like this, which I'm personally very happy with:
defmodule ShadyCorner.Repo.Migrations.CatTz do
  use Ecto.Migration

  def change do
    execute """
    CREATE TYPE datetimetz AS (
    dt timestamptz,
    tz varchar
    );
    """

    alter table(:catdog) do
      add :birth_tz, :datetimetz
    end
  end
end

@pmyjavec That's exactly how I would do it :)


add ubuntu script

https://github.com/glenpike/npm-g_nosudo

https://github.com/robbyrussell/oh-my-zsh

https://nodesource.com/blog/nodejs-v012-iojs-and-the-nodesource-linux-repositories


Lacks PHP v8.1 compatibility

PHP v8.1 (currently a release candidate) deprecates several parameter types and throws warnings such as Deprecated: preg_split(): Passing null to parameter #3 ($limit) of type int is deprecated in PHP-CSS-Parser\lib\Sabberworm\CSS\Parsing\ParserState.php on line 285

@dleffler We currently unfortunately cannot run the unit tests with PHP 8.1 yet. Would you be willing to list all problems you encounter with PHP 8.1? Then I can take a look. Thanks!

Hi @oliverklee !
Since this PR is merged can we expect new release?  (to used with pelago/emogrifier)

Yes, I’ll do a release shortly. I wasn’t sure whether @oliverklee was through with all the planned refactorings which I wanted to wait for before releasing but it seems like now is a good time.

No, I'm not through with my planned refactorings/cleanup/fixes. None of those should block a release, though. So please go ahead, @sabberworm! Thanks!

Hi @sabberworm! Do you have updates by any chance when new version will be released ?

@xmav version 8.4.0 is now out.


Take first component of X-Forwarded-{Proto,Host}

Apache will add comma separated components to X-Forwarded-{For,Host,Proto} if the header already exists,
i.e. if there are multiple reverse proxies. Apache docs: http://httpd.apache.org/docs/2.4/mod/mod_proxy.html#x-headers
Fixes issue #5

This failed several tests, I've applied a version that fixes the error here.


how do i uninstall?

Run Roblox Studio’s regular launcher and it’ll overwrite the mod manager’s changes.


BT disconnects as soon as ./robot.sh is started

Hello!
As stated above I now try to control the robot via Bluetooth. I use a Thinkpad X201T (xubuntu 18.04.4) with built-in BT in order to connect to the ev3. As soon as I start the robot.sh via the ssh shell and type in the correct password for sudo, the terminal becomes irresponsive and the connection breaks. I have already tried to launch it several times without any luck. Every time the BT connection breaks down on me, making it impossible to close the control loop. Launching it with USB connected works fine and keeps the robot connected. Do you have any idea what could provoke this kind of behaviour when connected to BT? What type of connection with what hardware have you used while testing the NCS?
Thank you for your quick and helpful responses in the past! :)
Greetings

Hi Jmller,
The problem comes from this command in robot.sh
rmmod legoev3_bluetooth 2>/dev/null,
which is introduced to reduce the CPU load of the robot. You can remove this line and the connection will be maintained.
I only have one remark about your setup. By using a BT connection instead of a Wi-Fi or Ethernet, the risk is that the communication latency increases and the robot cannot be controlled over the network. In order to be controlled the robot requires 35ms round-trip delay!
Good luck!


Add a method for the user to select the currently displayed language

Once localization support is added, the user will need a method to see what languages are available and select what language that user would like to use.
There is support added upstream already to introduce a toggle button group into the upstream settings page component.

Is this upstream component sufficient?
Should there be a means to set an initial default language?  For example if an organization speaks Spanish by default, perhaps then Spanish could be set as a default language in one of the app config files (app-config.local.yaml etc...)

Part of #502

A selector control was added to Backstage 1.18:

There's a couple enhancements though to improve the usability that I can see:

currently this selector only appears to show and have access to the strings supplied in the configuration but perhaps there's a way to also provide translated strings for these fields.
I'm not sure this is the best control to use, especially if the full language name is shown for each language and there's more than two languages, this area will overflow or wrap.  A select control could be a better fit.

Lots of languages looks like:

I think most likely the above isn't going to be a problem, at least in the short term.  It'd be good though to suggest improving the selector so that it displays language names instead of using country codes.


Writing Contribution Guidelines

Contribution Guidelines guidelines file helps project contributors to do the work, file defined at <project_root>/CONTRIBUTING.md

Task:

[x] #4
[ ] #5
[ ] #6
[x] #7
[ ] #8

Also

Structure guide
use emojis & Gifs ( for good readability )

💡 for better markdown structure use markdown lint
vscode:  Marketplace install

Anyone is welcome to contribute to these tasks
make changes only in the Development branch

for reference:
https://github.com/atom/atom/blob/master/CONTRIBUTING.md
https://github.com/rails/rails/blob/main/CONTRIBUTING.md

Ill take care of 1'st task

Nice Readme by the way 👏

👌


Update/boundary click watcher multiple ignore class

💬 Description

Updates <BoundaryClickWatcher /> to accept multiple classes in the ignoreClass prop.
Updates the README
Adds class to "Remove due date" action, to be targeted by ignoreClass in the related PR.

👫 Related PRs (optional)
https://github.com/gathercontent/app/pull/2258
✅ Checklist

[ ] Tests written
[ ] Browser tested
[ ] Added to documentation
[ ] Added to storybook

 [12] Status Dropdown closed when due date set & Due Date Dropdown Positions of Screen


Missing splitText on Text node

Hello!
Thanks for this amazing package!
I just miss the Text.splitText method.
In the meantime, I'm using this naive implementation :
dom.Text.prototype.splitText = function (offset) {
  const [start, end] = (() => {
    if (offset <= 0) return ['', this.data];
    if (offset >= this.data.length) return [this.data, ''];
    return [
      this.data.substring(0, offset),
      this.data.substring(offset),
    ];
  })();

  const newNode = dom.document.createTextNode(end);
  this.parentNode.insertBefore(newNode, this.nextSibling);
  this.data = start;
  return newNode;
};

Thanks.

why not filing a PR instead? I don't mind naive implementations as long as not obtrusive for the fast-path use case and working reasonably well (and code-covered, of course).

not enough interest in this, closing until PR available.


Extra leading newline from the --help output

Hey,
I find formatting the quasiquoted usage string as follows to be aesthetically pleasing, but it seems to result in an extra leading newline when doing --help:
usage = [Docopt.docopt|
Usage: foo [options] <file>
|]

How about skipping that leading newline when reading it in?
Thanks!

@moll Sorry for the long radio silence!
I agree, that is an annoying part of that quasiquoter. This is fixed in v<IP_ADDRESS>, which I just uploaded. Cheers!

Yay. Thanks!


docs: mobile sidebar fix

What is it?

[ ] Feature / enhancement
[ ] Bug
[x] Docs / tests

Description

fixes #2499 (screenshot 1)
textual representation of theme toggle to match other links in the mobile menu (screenshot 2)
adjusted position of close button on mobile view (screenshot 3)
aligned toolkit icon sizes and hover effects on dark and light mode on desktop (screenshot 4)
replaced legacy className usag

Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

Screenshots

awesome job, thanks!


Test action

🤖 Hi  @liwuqingxin, thanks for your issue! We will look into it shortly.
Please send an email to<EMAIL_ADDRESS>to tell us your toolspeed account. We will extend your plan for three months.


Thanks!

Thanks for making this. I was about to finally roll up my sleeves and deal with this and it was already done. Appreciate it!

@JoeDuncko, thanks from me as well! Got from 9340 likes to 2152. Spotify connect should also be a lot more responsive when playing my likes (didn't try yet).

Glad it was helpful!


[FLINK-36124][connectors][aws]Make S3RecoverableFsDataOutputStream.sync not to close the stream

What is the purpose of the change
At the moment S3RecoverableFsDataOutputStream.sync closing the stream and all upcoming write operations fail consistently with the following exception:
java.io.IOException: Stream closed.

at org.apache.flink.core.fs.RefCountedFileWithStream.requireOpened(RefCountedFileWithStream.java:72)
at org.apache.flink.core.fs.RefCountedFileWithStream.write(RefCountedFileWithStream.java:52)
at org.apache.flink.core.fs.RefCountedBufferingFileStream.flush(RefCountedBufferingFileStream.java:104)
at org.apache.flink.core.fs.RefCountedBufferingFileStream.write(RefCountedBufferingFileStream.java:87)
at org.apache.flink.fs.s3.common.writer.S3RecoverableFsDataOutputStream.write(S3RecoverableFsDataOutputStream.java:112)
at java.base/java.io.OutputStream.write(OutputStream.java:122)

In this PR instead of closing the file creating a new and uploading the old content.
Brief change log
Made S3RecoverableFsDataOutputStream.sync not to close the stream.
Verifying this change
Adopted the existing unit test.
Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

cc @dannycranmer @hlteoh37

Thanks for the root cause and fix @gaborgsomogyi !
nit: I think we should rename the commit as [filesystem][s3] instead of connectors! Because this can impact other code using the filesystem here.

Done.

Just resolved the conflict.

@flinkbot run azure

Thanks for the fix @gaborgsomogyi!
As I tried to understand the problem we have here, I checked the history of what happened here before and why. The previous change that was made S3RecoverableFsDataOutputStream#sync() done in FLINK-28513. The error msg. there states:
S3RecoverableFsDataOutputStream cannot sync state to S3. Use persist() to create a persistent recoverable intermediate point.

If we check the persist() implementation, it will upload the local part to S3, but will not enforce closure of that local part file, neither will commit the snapshotted state. IIUC committing is crucial inside sync(), because it is a void method, so if we would simply call persist() inside, we would lose the S3Recoverable object it returns, and the ability to resume correctly in case of a failure. So without changing the interfaces, it is necessary to commit here and make sure we have a consistent state before we leave the sync() method and release the lock.
Based on these conclusions, if the current solution performs good based according to the actual usage, the fix itself LGTM.

@flinkbot run azure

Just rebased to latest master.


Add asyncWrite Combine functions

Fixes #6953.
Prototype API for async writes via combine. Incidentally, doing this through Combine only seems to have revealed the cleanest way to add this feature:
The challenges of async write are:

Users can pass anything into a block, even if we offer a convenient and obvious API for them to be passing in their ThreadConfined types
We have no way of discerning the block's capture list, so attempting to freeze/thaw via that route is untenable, bar doing gnarly memory magic that would likely break with each new swift version.

IMO, because Combine already has a fairly unique DSL/UX, the guidelines of how to use the API will be clearer. More specifically, the way objects are passed/mapped through combine's Publishers lends itself well to an API like this.
realm.asyncWrite(on: queueA, intObject, boolObject) { realm, intObject, boolObject in
    intObject.intCol = 42
    boolObject.boolCol = true
}.combineWrite(on: queueB, listObject.double, stringObject) { realm, doubleList, stringObject in
    doubleList.append(42.42)
    stringObject.stringCol = "foo"
}.sink(receiveCompletion: { completion in
    if case .failure(let error) = completion {
        print(error.localizedDescription)
    }
}, receiveValue: { (write1, write2) in
    let (intObject, boolObject) = write1
    let (doubleList, stringObject) = write2
    assert(intObject.intCol == 42)
    assert(boolObject.boolCol == true)
    assert(doubleList.first == 42.42)
    assert(stringObject.stringCol == "foo")
}).store(in: cancellables)

The added test testAsyncWrite shows the functionality in action.
cc @ianpward @astigsen

How about naming the method writeAsync() instead of asyncWrite()? Just for pedagogical reasons. It would be nice if it showed up as an option on autocompletion every time someone tries to do a write().

I've updated this PR to use the Swift 5.5 toolchain. I've removed the Combine integration that I previously proposed. What we have now (in 5.5) is fairly different but significantly cleaner that was users currently have to do for concurrent programming with Realm.
Consider the example I added to AsyncTest/main.swift:
@available(macOS 9999, *)
@objcMembers class Vegetable: Object {
    dynamic var _id = ObjectId.generate()
    dynamic var chopped = false

    override class func primaryKey() -> String? {
        "_id"
    }

    class func chop(@RealmSendable vegetable: Vegetable) async throws {
        print("Task \(Task.current!.hashValue): Vegetable \(vegetable._id) starts chop")
        vegetable.chopped = true
        Thread.sleep(forTimeInterval: 2)
        print("Vegetable \(vegetable._id) ends chop")
        return
    }
}

@available(macOS 9999, *)
@objcMembers class Meat: Object {
    dynamic var _id = ObjectId.generate()
    dynamic var marinated = false

    class func marinateMeat(@RealmSendable meat: Meat) async throws {
        print("Task \(Task.current!.hashValue): Marinate meat \(meat._id) starts")
        meat.marinated = true
        Thread.sleep(forTimeInterval: 2)
        print("Task \(Task.current!.hashValue): Marinate meat \(meat._id) ends")
    }
}

@available(macOS 9999, *)
@objcMembers class Dish: Object {
    dynamic var meat: Meat?
    dynamic var veggies = List<Vegetable>()
    dynamic var cooked = false

    convenience init(meat: Meat, veggies: [Vegetable]) {
        self.init()
        self.meat = meat
        self.veggies.append(objectsIn: veggies)
    }
}

@available(macOS 9999, *)
@objcMembers class Oven: Object {
    dynamic var _id = ObjectId.generate()
    dynamic var preheated = false
    dynamic var isCooking = false

    override class func primaryKey() -> String? {
        "_id"
    }

    class func preheat(@RealmSendable oven: Oven) async throws {
        print("Task \(Task.current!.hashValue): Oven \(oven._id) preheat starts")
        oven.preheated = true
        Thread.sleep(forTimeInterval: 2)
        print("Oven \(oven._id) preheat ends")
    }

    func cook(@RealmSendable dish: Dish) async throws {
        isCooking = true
        print("Task \(Task.current!.hashValue): Oven \(_id) cook starts")
        dish.cooked = true
        Thread.sleep(forTimeInterval: 2)
        print("Task \(Task.current!.hashValue): Oven \(_id) cook ends")
        isCooking = false
    }
}

@Sendable func gatherRawVeggies() async throws -> [Vegetable] {
    let realm = AsyncRealm()
    let onion = Vegetable()
    let shallot = Vegetable()
    try await realm.write {
        realm.add(onion)
        realm.add(shallot)
    }
    return [onion, shallot]
}

@Sendable func chopVegetables(_ vegetables: [Vegetable]) async throws {
    for veggie in try await gatherRawVeggies() {
        try await Vegetable.chop(vegetable: veggie)
    }
}

@Sendable func makeDinner() async throws -> Dish {
    let realm = try Realm()

    let oven = Oven()
    let meat = Meat()

    // async write and await
    try await realm.asyncWrite {
        realm.add(meat)
        realm.add(oven)
    }

    let veggies = try await gatherRawVeggies()

    try await Meat.marinateMeat(meat: meat)
    try await Oven.preheat(oven: oven)

    try await chopVegetables(veggies)

    let dish = Dish(meat: meat, veggies: veggies)

    try realm.write {
        realm.add(dish)
    }

    try await oven.cook(dish: dish)
    // async write and forget
    detachWrite(to: oven) { oven in
        oven.preheated = false
    }
    return dish
}

@Sendable
func main() async throws {
    let dishes = try await withThrowingTaskGroup(of: Dish.self) { group -> [Dish] in
        var dishes: [Dish] = []

        // cook two dinners in parallel
        group.spawn {
            try await makeDinner()
        }
        group.spawn {
            try await makeDinner()
        }
        // collect the dinners when complete
        for try await dish in group { // (2)
            dishes.append(dish)
        }

        return dishes
    }

    print("Bon Appetit!: \(dishes)")
}

Note that the @available(macOS 9999, *) is temporary, and @Sendable on the methods is because they are global.
How do the async class methods on the models work?
They are automatically being wrapped in write transactions by the @RealmSendable property wrapper.
@RealmSendable begins a write transaction on init and commits it on deinit. This all happens under the hood so the user doesn’t have to do anything.
Having propertyWrappers for function parameters is a huge boon for us. This will be incredibly handy with projections as well, and lines up nicely as we ask users to place their business logic onto their models/projections.
This takes pressure off the "stray async write" use case:
// async write and forget
detachWrite(to: oven) { oven in
    oven.preheated = false
}

With Swift 5.5, we still cannot achieve a great syntax for this. However, encouraging users to move the business logic to @RealmSendable async write methods yields a clean cut way for users to asynchronously write to Realm.


Add section on blueprint in "UI Design"

With blueprint-compiler being widely adopted by GNOME devs, it would be nice to see a mention for it in the section!

Sounds good!
I'll prepare a PR.


Better guidance / usage for initial data

After migrating to add a new collection, for example, initial data won't be re-run. Which is right.
But how do you initialize data into new stores?

Probably the right thing to do here is provide a full-powered EntityStore to migrations, so they can do any logic they want.


Add some Mergify config

Add Mergify (https://mergify.io/) to the repo.
When I’m writing posts, I typically put them in a PR (e.g. #153), and I want them to be merged when Travis goes green – if this works, they should be automatically merged (and thus posted) without any more work from me.

Bah. I can’t see a way to say “I don’t care about reviews”.


bibliography: update bib file

This PR updates the bib file for the MEI bibliography with the latest articles of "International Journal on Digital Libraries"

Thanks!


chore(test): use test marbles for filter operator spec

Try covering #390. Hope this is sufficient and adhere to contributions guidelines.
Could not find tests from RxJS3/4 for filter.

Maybe this test cases can be adopted for filter?

@kwonoj indeed ! Forgot about the where alias.

I may have to wait for #402 to backport some of those tests.

Merged with 4bbd4a5... thank you @jinroh!


xatlas: Sync with upstream ec707faea

https://github.com/jpcy/xatlas/commit/ec707faeac3b95e6b416076a9509718cce105b6a

Cherry-picked for 3.5.


Issue setting future territories to false in itunes connect

New Issue Checklist

[X] Updated fastlane to the latest version
[X] I read the Contribution Guidelines
[X] I read docs.fastlane.tools
[X] I searched for existing GitHub issues

Issue Description
I am currently trying to use spaceship to set the new territories field (so that it will make the app automatically available in all future App Store territories). But I find that the correct value doesn't get respected when we submit into itunes connect.
For instance, if in itunes connect, this checkbox for the "New Territories" is set to true, and in space ship, I set it to false, it doesn't get reflected in itunes connect. It seems to always default to true, unless it wasn't selected in itunes connect in the first place.
The code I am trying to run is:
availability = app.availability
availability.include_future_territories = false
availability = Spaceship::Tunes::Availability.from_territories(langCodes)
availability = app.update_availability!(availability)
Note that langCodes is an array containing the language codes
Is this simply being called incorrectly or am I missing something?
Thanks!
Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.

Here is the output of fastlane env:
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.6

Ruby
2.0.0

Bundler?
false

Git
git version 2.11.0 (Apple Git-81)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.12.6 (16G29)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib

OpenSSL Version
OpenSSL 0.9.8zc 19 Mar 2015

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.3.3

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane gems

Gem
Version
Update-Status

fastlane
2.49.0
💥 Check failed

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
1.5.1

CFPropertyList
2.3.5

colored2
3.1.2

nanaimo
0.2.3

xcodeproj
1.4.4

rouge
2.0.7

xcpretty
0.2.8

terminal-notifier
1.8.0

unicode-display_width
1.2.1

terminal-table
1.8.0

plist
3.3.0

public_suffix
2.0.5

addressable
2.5.1

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.5

excon
0.55.0

faraday
0.12.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.0

gh_inspector
1.0.3

uber
0.0.15

declarative
0.0.9

declarative-option
0.1.0

representable
3.0.4

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

little-plugger
1.1.4

multi_json
1.12.1

logging
2.2.2

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.12.0

json
1.7.7

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.1

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.1

bundler
1.15.0

faraday_middleware
<IP_ADDRESS>

claide
1.0.2

generated on: 2017-08-25

@enozero I am experiencing the same issue, can you help here?

I'll take a look here and see what I can find

Hey everyone, I have just tried to reproduce this with my own app and everything is working as expected for me. Given that Apple changes things around all the time, could you all give this a shot and see if it's still an issue? If so, could you please share some reproduction steps as detailed as possible so we can test it out on our end? Thanks!! 👍  🚀


Add missing path_display to file metadata

This field can be seen in the documentation but is not present in the corresponding Go struct. This PR adds it in.

thanks!


Create convert_hipchat_data.

I am breaking this into several commits to make it easier to back out thing where we may have decisions, or where it might be convenient for cribbing in future conversions, but each commit, including the first commit, is atomic to the best of my knowledge.

I believe I've addressed your first round of feedback, @timabbott, and I also added a commit to auto-subscribe users to public streams, which I discussed on chat with @rishig.
There's still more work to do here, but the current commits should be merge-able.

Looks reasonable, merged, thanks @showell!
I think a good next step here is to look at whether HipChat's API has a way to get at which users are subscribed to which rooms (so that users could provide that data or the relevant API keys as a separate argument); that seems like the essential bit we need to make the import experience pretty reasonable.  (We have to do something similar with Slack import to get email addresses for users).

@rheaparekh I think you'll definitely enjoy reading this and thinking about code deduplication for it.


Tech: eventing massive updates for version 2.0.0

BREAKING CHANGE:

ESLBasePopup statechange events replaced with a separate (before:)show/hide
ESLBaseElement no longer contains eventNs and $$fireNs methods
Whole popups based component system no longer use event namespaces
transitionend event of ESLPanel replaced with after:show/after:hide
statechange event of ESLTrigger replaced with change:active

:tada: This PR is included in version 2.0.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


nits: missing copyright owner

https://github.com/abdolence/firestore-rs/blob/7df51d418c94dcd7a9c9b07534ebef5bb73e1e28/LICENSE#L189

Hey, that's just appendix with the template provided by the original license. To be explicit for compliance reasons authors either add copyrights based on the template on each file which could be a bit noisy or have it separately with the source code. What I did with COPYRIGHT.md file now.


data

Hello, I encountered an error while executing the following command

After executing your command, the original dataset can be downloaded, but when executing the command
  semantic = ['https://www.robots.ox.ac.uk/~shuaic/NeFeS2024/Cambridge_semantic.zip']，
the data is incomplete.

The original dataset had 5 scenarios, but this compressed file only contains 4
The downloaded and decompressed file is shown in the picture

Ah, I think you are right. Thanks for the question. Apologize for my negligence.
Since in our paper, we only compared four scenes to align with previous works. I don't remember if I have actually run GreatCourt semantic map.
For now, maybe you could comment out this line so there is no bug: https://github.com/ActiveVisionLab/NeFeS/blob/f954c5fc6d844eb81e01c02236e0706c32e19e85/data/setup_cambridge.py#L16
When I get home today, I could try to see if I can find GreatCourt semantic maps and fix the script issue.

Thank you for your answer


Compression

Codecov Report

Merging #237 into master will decrease coverage by 0.07%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##           master     #237      +/-   ##
==========================================
- Coverage   92.61%   92.53%   -0.08%
==========================================
  Files          41       41
  Lines        1922     1943      +21
==========================================
+ Hits         1780     1798      +18
- Misses         96       97       +1
- Partials       46       48       +2

Impacted Files
Coverage Δ

dataflow/req.go
84.23% <50.00%> (-0.15%)
:arrow_down:

dataflow/dataflow.go
94.21% <100.00%> (+0.12%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d58f429...e7ccbdf. Read the comment docs.


Allow subscriber message retention policy to be customised

Create overrideable protected function that the implementing action can use to change message retention behaviour. Implementing in such away gives implementer a lot of control with limited overhead in the abstract class. Default behaviour remains unchanged
Alternative to https://github.com/BehaviorTree/BehaviorTree.ROS2/pull/42

@facontidavide is this alternative ok. is very little overhead and i think no real added complexity

Closing in favour of #54


Grid - revisit column width / flex configs

The current handling of grid column widths is non-ideal, specifically in that there is no easy way to use the (what seems like it should be the most common) width config and have that applied as specified as the starting width in pixels.
I believe this is due to our current workaround to support a flex config, where we translate flex into a "really big width" and then are calling sizeColumnsToFit() on the grid API to have it do...something...with regard to relative column sizing that kind of looks like flex.
You can use fixedWidth, but that prevents interactive column resizing which is non-intuitive and could easily be frustrating/confusing to users. (Ideally fixedWidth would be reserved for special / structural columns, like those with glyphs where there is truly no need / desire to resize.)
If we assume that flex is still important (and I think it is), we might need to look at a deeper approach to adding flex support: e.g. evaluate the grid size, read and subtract the width of non-flex columns, and then compute widths for flex columns based on their flex values / remaining overall grid width (with additional handling for min/max width).  I am sure there are subtleties and this is likely tricky to get right - for instance I've never been too clear on how we handle/consider a flex column that's been manually resized. But I don't think the current setup is going to work for us and the grid is such a core component we need to get it right.

Started digging into this. Looking at the source of sizeColumnsToFit, I noticed a prop called suppressSizeToFit. It appears that if we set this to true on the column along with a width prop we achieve the desired width on render without preventing an interactive resize.

Adding @gportela85 to this ticket - would like to review when we can with the testing tool you setup, Don, ensure the goals of the ticket are clear, and get Gil started on an attempt at custom implementation for flex support.

Adding John.  As per #389, this is a priority that he is working on as well.


OpenSAP contribution in Python

Hello
it seems to be this is a great initiative,
I would be interested in setting up a common "hands-on" project.
I've open a repo about creating an API for OpenSAP certification.
We could set up together an step by step Python tutorial for https://developers.sap.com related to webscrap the https://open.sap.com/courses page, get the title of the courses then provide an API, maybe through Flask in order to provide a list of the available courses and certification as well as from the https://people.sap.com profile and to feed the various LMS platform (successfactor, workday etc ...)
please see : Github repository
The target could be something similar to traning certification validity list with API endpoint. Let's ask @jung-thomas and @qmacro their interest or the person in charge to start such an initiative.
Regards
Amaury

Hi @AmauryVanEspen,
tanks for reaching out. Sounds like an interesting idea. However, right now i can't commit to participate. I currently need to get the OpenSAP Python introduction finished (i.e. this course). Furthermore, I need to finalize the S/4HANA course book I'm working on. After that (spring  next year) I would be open for new projects.
Christian


Error Not Displayed During Video Playback; Player Stuck in Loading State

When attempting to play a video stream using the ModernPlayer package, if an error occurs during playback, the error is not displayed to the user. Instead, the player remains stuck in a loading state indefinitely.
To Reproduce
Steps to reproduce the behavior:
Go to the application using the ModernPlayer package.
Use the following video stream URL: http://<IP_ADDRESS>:80/dvb-gw/output/5/shabelle-tv.
Attempt to play the video.
If an error occurs, observe that the video player remains in a loading state without displaying any error message.
Expected behavior
When an error occurs during video playback, a clear and concise error message should be displayed to the user instead of the player remaining stuck in a loading state.
Smartphone (please complete the following information):
Device: Android Emulator
OS: Android API 33 (android-x64 emulator)
Browser: N/A
Version: Pixel 3a XL
Additional context
The issue is observed consistently with the provided stream URL. The emulator used is "Pixel 3a XL API 33 (android-x64 emulator)". The problem might be related to how ModernPlayer handles errors during video playback.

#10 Same Issue

i have solution play from youtybe and solution also for get all quality for youtube contact me on whatsapp :971557474526


DXE-4473 Error exporting property. Saving terraform files. Executing template: rules_v2024-10-21. Range can't iterate over

I have a bug with the export-property command when exporting rule format 2024-10-21.
The output is:
Fetching property www.something.com [OK]
Fetching group  [OK]
Fetching property version  [OK]
Fetching property rules  [OK]
Fetching product name  [OK]
Fetching hostnames  [OK]
Fetching activation details  [OK]
Saving TF configurations  [FAIL]
Error exporting property: saving terraform project files: executing template: rules_v2024-10-21.tmpl:
template: rules_v2024-10-21.tmpl:9347:20: executing "queryStringParameter" at <$v>:
range can't iterate over api.blah.something.com

I have some match criteria that uses an array of strings for match values. This is from the downloaded rules JSON:
"criteria": [
    {
        "name": "queryStringParameter",
        "options": {
            "parameterName": "host",
            "matchOperator": "IS_ONE_OF",
            "values": "api.blah.something.com",
            "matchWildcardName": false,
            "matchCaseSensitiveName": true,
            "matchWildcardValue": false,
            "matchCaseSensitiveValue": true,
            "escapeValue": false
        }
    }
],

Strangely, I have similar blocks of JSON in the export that have a single array item, but include it as an array of strings rather than just a string:
"criteria": [
    {
        "name": "queryStringParameter",
        "options": {
            "parameterName": "host",
            "matchOperator": "IS_ONE_OF",
            "values": [
                "api.blah.something.com",
            ],
            "matchWildcardName": false,
            "matchCaseSensitiveName": true,
            "matchWildcardValue": false,
            "matchCaseSensitiveValue": true,
            "escapeValue": false
        }
    }
],

Hi @glenthomas
I was able to reproduce it. We will inform you about progress.
BR,
Lukasz

Hello Lukasz, please let me know if there are any suitable workarounds as I would like to continue with my work ASAP. Thanks.

Hi @glenthomas,
You can open your property in UI and save it there even without any changes. It should covert this problematic element to array of strings.
BR,
Lukasz

Hello @lsadlon, to confirm, are you saying that I can:

Edit a new version of the property in the Control Center.
Save the version without any changes.
Export using cli-terraform

and it will now work? So somebody has fixed the values attribute so that it is always a list of strings?

...I have just tried this and am still getting the same error.

Hi @glenthomas,
So problem is that cli-terraform while exporting data expect values attribute to be list of strings. Other way you can fix it is using API (e.g. Postman) https://techdocs.akamai.com/property-mgr/reference/put-property-version-rules and update your rules accordingly.
BR,
Lukasz

Hi @glenthomas,
To be honest from error message that you get I cannot tell you what is wrong, but it looks there is something wrong with request itself, rather than rules.
BR,
Lukasz


feat: Handling Panics in HashNode Method

Problem
The HashNode method of the NMT may potentially cause a panic if it receives invalid or malformed inputs (as mentioned by @evan-forbes in this comment https://github.com/celestiaorg/nmt/pull/102#discussion_r1110338821). For example, if the left or right children do not conform to the namespace hash format, meaning their length is less than the namespace ID size, or if the relation between the left and right children namespace range is invalid. If an invalid node is sent to a light node, it can result in a crash.
It is important to note that returning an error from this method is not possible as it would violate the interface it is intended to fulfill i.e., NodeHasher and Hash.
Acceptance Criteria
This issue is to implement proper error handling mechanism  for HashNode.

Reopening this issue as it is not completely resolved.
As mentioned in the last relevant PR i.e., https://github.com/celestiaorg/nmt/pull/113, to avoid situations in which light clients may panic, we need to integrate the node validity checks into the proof verification and construction and return error for invalid inputs. Also, as per conversation with @evan-forbes, we also decided to change the signature of the HashNode and HashLeaf to return errors for invalid inputs instead of panic. All these require some refactoring. Once done, we can close this issue.


Add update article for editors

This offers a button for updating an article on the /x-journal/manage/archive/article/x/ page

Editors and authors of the article may update the article.

@mdlincoln added tooltip with description of what buttons do.
let me know if this satisfies the requested change ya


mmap() failed: Cannot allocate memory size: 603979776 offset: 0

Bugs
When file size was grown almost 1 GB, data can't save and return this message mmap() failed: Cannot allocate memory size: 603979776 offset: 0  I tried two way shouldCompactOnLaunch strategy and wrapping reads in autoreleasepool. But, it can't solve that problem.
Goals
I'd like to save some data which are an image created by user and text attributes into realm file.
(I'm using only realm database)
Expected Results
I expect that data can save into Realm file.
Actual Results
I can't save data and return that error mmap() failed: Cannot allocate memory size: 603979776 offset: 0
This message is changed depend on iPhone device. I think it happen when file size is almost 1 GB.

iPhone 5S : mmap() failed: Cannot allocate memory size: 603979776 offset: 0
iPhone 7 plus : mmap() failed: Cannot allocate memory size: 903979776 offset: 0

Steps to Reproduce
When I try to save an Image user created and several text attribute information, if that file size is almost 1GB,  Realm file can't save that data and return "map() failed: Cannot allocate memory size: 603979776 offset: 0" This message.
Code Sample
//AppDelegate.swift
DispatchQueue.global().async {
            autoreleasepool {
                var realmConfiguration = Realm.Configuration(shouldCompactOnLaunch: { totalBytes, usedBytes in

                    let oneHundredMB = 100 * 1024 * 1024
                    return (totalBytes > oneHundredMB) && (Double(usedBytes) / Double(totalBytes)) < 0.5
                })
                    realmConfiguration.schemaVersion = SQRealmSchemeVersion
                    realmConfiguration.migrationBlock = SQRealmMigrator.realmMigrationBlock
                    realmConfiguration.fileURL = FileManager.default.containerURL(forSecurityApplicationGroupIdentifier: SQExtensionAppGroupIdentifier)!.appendingPathComponent("spark_quote.realm")
                do {
                    _ = try Realm(configuration: realmConfiguration)
                } catch {
                    print(error)
                }
                    Realm.Configuration.defaultConfiguration = realmConfiguration
            }

This code is problem code.
DispatchQueue.global().async {
                        autoreleasepool {
                            do {
                                var quote : SQQuote!

                                var configuration: Realm.Configuration = Realm.Configuration()
                                configuration.schemaVersion = SQRealmSchemeVersion
                                configuration.migrationBlock = SQRealmMigrator.realmMigrationBlock
                                configuration.fileURL = FileManager.default.containerURL(forSecurityApplicationGroupIdentifier: SQExtensionAppGroupIdentifier)!.appendingPathComponent("spark_quote.realm")
                                Realm.Configuration.defaultConfiguration = configuration
                                let realm = try Realm(configuration: configuration)

                                if self.currentQuoteType == .myPhoto && self.selectedMyPhotoImage != #imageLiteral(resourceName: "bg_myphoto_mainphoto") {
                                    quote = SQQuote(text: text, backgroundImage: nil, quoteImage: quoteImage, saveOrigianlImage: true)
                                }else {
                                    quote = SQQuote(text: text, backgroundImage: nil, quoteImage: quoteImage, saveOrigianlImage: false)
                                }

                                **realm.beginWrite()
                                realm.add(quote)
                                try realm.commitWrite()**

                            }
                            catch let error as NSError {
                                self.presentErrorAlert(message: "Error occupied. \(error.localizedDescription)")
                            }
                        }

Version of Realm and Tooling
Realm framework version: 3.7.6
Xcode version: 9.4.1 (9F2000)
iOS/OSX version: iOS 10.2.1 and 11.4.1

We had exact same issue. For us, we found, that we did not delete some relations.
...
let projects List<Project>
...

When we delete entity, it does not clean List data from Realm, they keep to be there, until we hit Cannot allocate memory limit.
See StackOverFlow for actual memory limits per device.

How to fix this?

@HonzaMac Thank you for reply. In your case, when you delete object, it didn't delete all clearly. So this problem came from that. is it right?
@imhafeez I didn't fix yet 😢 But, I got some hint. Some time, this problem is happened and some time this problem is not happened. I think it's depend on device memory condition. So I will try to change realm architecture, if device memory condition is okay.
I'm not sure that is solution. If it work, I will comment about it in here.

@LucyJeong  Please update then. Because it is effecting our customers with random crashes.
It didn't happen on launch. mostly it happen while using the App
Thanks

We did several fixes, one I already mention (we introduced cascade delete for Realm)
Second is to use compactOnLaunch option when instantiating Realm configuration. (if you do a lot deletes & inserts, Realm keeps old objects in DB even if there is no reference to them)
Third option would be for us to make sure that every operation is in autorelease block. (not implemented yet)

@HonzaMac Thank you for comments :) I guess I can do only three way you mentioned to solve for this problem. I tried to same way. thanks :)


Updater topic name can be remapped via CMAKE

closes https://github.com/micro-ROS/micro_ros_diagnostics/issues/19
@norro I took the liberty of creating a PR with what we discussed.

[ ] Update documentation

Codecov Report

Merging #32 (e2be6b9) into master (c1a9f53) will decrease coverage by 0.49%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
- Coverage   39.02%   38.52%   -0.50%
==========================================
  Files           2        2
  Lines         123      122       -1
  Branches       19       19
==========================================
- Hits           48       47       -1
  Misses         61       61
  Partials       14       14

Impacted Files
Coverage Δ

..._diagnostic_updater/micro_ros_diagnostic_updater.c
71.21% <ø> (-0.43%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c1a9f53...e2be6b9. Read the comment docs.

If it's okay with you, I could try to cover both (bridge and updater) on this PR.

@norro This PR is ready for review (Still needs documentation updates)
What I did is to

remove the FQDN from the topics in the bridge

`/diagnostics` -> `diagnostics`
`/diagnostucs_uros` -> `diagnostics`

added arguments to the launch file to be able to modify the namespace as well as to remap the topics.
Made the hardcoded topic on the updater to be configurable via CMakeLists

Let me know what you think

@norro this PR is ready

@norro friendly ping. I can't merge until you remove your "changes requested" :)


Generate with chat template

This adds the option of applying a chat template such as those found in GGUF files to the prompt before generating tokens. This is a suggestion as I couldn't find a way of doing this in the code today.

Hey @lesters thanks for the pull request! This was indeed not possible, so it's a nice addition.
In general it's best to align the C++ code as close to the llama.cpp server code as possible since that way it's easier to maintain in the long term. I think there the chat template is loaded once when initializing a model (so via ModelParameters instead of InferenceParameters). Do you think it's necessary to be able to change the template for each inference?
However, the server has a separate endpoint for chat completions, which the Java binding doesn't have. So to still be able to choose for each inference whether to use the chat template, I think using something like your PARAM_USE_CHAT_TEMPLATE is the way to go.
I will review the PR in more detail tomorrow.

Thanks, @kherud. I think you are right, this is probably better as a part of ModelParameters - as you most likely don't want to change this much for each inference. I'll make the change.

Looks good to me, thanks for the work.


Rebuild for pugixml114 redux

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Trying to take over #11
Closes #11

@cboulay @tstenner should be good go merge here! (FYI I want this so that liblsl is compatible with VTK 9.3 that just came out, e.g. here).

Yeah it's really just two lines changed by me (stdlib line and c++11 line) the rest is from #11 so should be good to go

IIRC 1.16.2 uses C++14 features, but maybe it was just C++11 feature that were not fully supported by the compilers at the time. Then again I think it is overridden in the CMakeLists.txt, so it shouldn't break anything.

Then again I think it is overridden in the CMakeLists.txt, so it shouldn't break anything.

Looks a commit June 12 2023 removed a conditional based on MSVC_VERSION that probably changed it from being set only on Windows to having it be set on all systems, and 1.16.2 came out May 27, 2023 -- that could explain why we need to set something here, and suggests it could be removed once >1.16.2 lands.
But in any case yes one of you two just needs to click the green button now!


Detect if beacon ranging is on or off

I'm trying to conditionally trigger startRangingBeaconsInRegion only if it is not currently ranging, to avoid the device event emitter listening and logging two different ranging attempts.
Is it possible to detect whether or not ranging is on or off (for a given region)?

Hey @s2t2, sorry if I've been late but I just released a new beta version of this library on npm: react-native-beacons-android 2.0.0-beta.1.
In this new version you should be able to achieve what you're asking by calling Beacons.beaconsAndroid.getMonitoredRegions().
The getMonitoredRegions function returns a promise that resolves an array of the currently monitored regions. If the returned array has a length of 0 then you're not ranging.
Example:
const rangedRegions = await Beacons.getRangedRegions()
const isRanging = rangedRegions.length > 0

Let me know if it works... it is still in beta 👍

Sounds good!
On Aug 9, 2016 7:51 AM, "Matteo Mazzarolo"<EMAIL_ADDRESS>wrote:

Hey @s2t2 https://github.com/s2t2, sorry if I've been late but I just
released a new beta version of this library on npm: react-native-beacons-android
2.0.0-beta.1.
In this new version you should be able to achieve what you're asking by
calling Beacons.beaconsAndroid.getMonitoredRegions().
The getMonitoredRegions function returns a promise that resolves an array
of the currently monitored regions. If the returned array has a length of 0
then you're not ranging.
Example:
const rangedRegions = await Beacons.getRangedRegions()const isRanging = rangedRegions.length > 0
Let me know if it works... it is still in beta 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mmazzarolo/react-native-beacons-android/issues/17#issuecomment-238530138,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABRGp5OESIkzia1r3LLhmLWq3fSdW6UDks5qeGm4gaJpZM4JXXcY
.

@s2t2, your feedback would be appreciated here. Thank you ;)


The route will load if query or params get updated

I have routes as follows:
products?limit=100
When the limit updates, I make an api request which grabs 100 records (or however many the limit is set to). I need to do this on the route data transition step.
When updating the query on the route state, the state would update but not the route itself. The route would only update if the path changes which isn't ideal when you rely on query or params.
This fixes that - not sure if you want to merge this but thought I'd make a pull request anyway as I'm quite new to this.
Cheers!

I have exactly the same issue with vue-router-sync and I believe that this PR is reasonable (but it isn't yet merged for some reasons and I can't understand why).
Maybe I miss something and proposed changes will break something?

Thanks for the PR - navigation triggered by mutating the route was actually not a good way to handle this, just call $router.go() is more appropriate.


Ambiguous error message when incorrect argument is specified

$ bin/regtool -a 0x12345678 -w 0x123

Must specify 0 non-flags

Usage:  <--read|> <--write=value|> <--fwrite=value|> <--help|-h> --address=value

  Required flags:
    --address=value=value     The register to read from or write to

  Optional flags:
    --read                    Reads a single 32-bit value from the address
                              provided
    --write=value=value       Writes the specified value as a 32-bit
                              hexidecimal number to the address provided
    --fwrite=value=value      Write multiple values as 32-bit integers from the
                              file specified to the address provided
    --help/-h                 Print usage and options information

Closed with PR https://github.com/drali/sargs/pull/21


Add support for switches in homekit controller

Description:
This PR adds support for on/off switches on homekit_controller platform as per issue https://github.com/home-assistant/home-assistant/issues/17544
Related issue (if applicable): fixes #17544
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
N/A
Example entry for configuration.yaml (if applicable):
N/A
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

N/A Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

N/A New dependencies have been added to the REQUIREMENTS variable (example).
N/A New dependencies are only imported inside functions that use them (example).
N/A New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
N/A New files were added to .coveragerc.

If the code does not interact with devices:

N/A Tests have been added to verify that the new code works.

Solution works well! I guess it's pretty straight-forward and can be merged.

CC @mjg59


Errors and hanging when using multiple reprojected ImageStatic in OL6

Describe the bug
Previously mistaken for problems related to https://github.com/openlayers/openlayers/issues/9397 but it's now apparent there is an issue even when using as few as 6 reprojected ImageStatic layers.
To Reproduce
If you simply open the example https://codesandbox.io/s/reprojectionimage-lcxcq and click the zoom in button a few times the map appears to hang.  Nothing appears in the sandbox console but browser console shows error.

Restarting and zooming out and in again on Spain some of the layers don't respond while others do.

Maybe related to #9578.

The same image without reprojection is error free when repeated 120 times, slightly slow but still usable, and no errors logged.  Increasing to 160 causes Chrome "Aw, Snap!"

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

It's still an issue in beta 11.  Works OK with 4 images, 5 or more and the problems start,


EnsureStorageExists fails on subsequent calls if an index name is greater than 63 chars

If the combination of a class name and property cause an index identifier to be greater than 63 characters, the index id will be silently truncated during creation by the Postgresql database the first time it is added.
Then, if EnsureStorageExists(Type documentType) is called again for this type, it will always fail because it is attempting to delete and recreate the index but does not account for the actual truncated index name.
-- Marten.Storage.DocumentTable
CREATE INDEX mt_doc_longenoughnametocauseidtruncation_idx_why_would_you_name_something_this_long ON public.mt_doc_longenoughnametocauseidtruncation ((CAST(data ->> 'WhyWouldYouNameSomethingThisLong' as uuid)));
-- Marten.Storage.DocumentTable
drop index concurrently if exists public.mt_doc_longenoughnametocauseidtruncation_idx_why_would_you_name;
Npgsql.PostgresException : 42P07: relation "mt_doc_longenoughnametocauseidtruncation_idx_why_would_you_name" already exists

@barryhagan I'm gonna finesse this one a little bit just today. All I'm doing is adding an assertion on the name lengths so it'll blow up if you go over your namedatalength. I'll add an ancillary issue to make sure that all db object names can be modified for 2.7.0 soon-ish


Edited summary

Added the description of this class.

Docs Build status updates of commit 21e1b29:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint-server/xml/Microsoft.SharePoint/SPException.xml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


🐞[Bug]: Improve the UI of "about" section footer by fixing the "send message" option.

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
The "Send Message" section has the text area for the message much smaller than its other components like Name , email.
I intend to fix this by improving the UI of this specific part.
Expected behavior
The text area for the message box should be much larger for a user friendly experience. It will make the users frame their message much concisely.
Add ScreenShots

What browsers are you seeing the problem on?
Brave , Chrome
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

already done


Can no longer push to the repo

I tried pushing to the repo today and I got this error:

Did something change recently wrt access via personal access tokens? This is an org-wide setting.

Ok, sounds like you changed something which is now preventing me from pushing.
I just accepted your invitation to CHIPS Alliance org, however, that has not solved the problem.

Karol advised switching to SSH to push to the repo and this method works.


correctly respect exif orientation of thumbnailed images

Currently when thumbnailing jpegs etc. the orientation in the exif information of the images is ignores. This PR fixes that, using https://github.com/disintegration/imageorient

Wow, didn't see that piece of code at all. Will work on fixing that instead 👍

Or we can think about using that library to decrease complexity of the media repo and remove the custom exif code - thoughts?

Unmaintained and unpopular libraries are not my favourite, and neither is dragging in dependencies that don't need to be here.

@turt2live found the actual fix, it was a simple typo in the exif orientation logic. Force-pushed the new PR here, a new review would be great!


Test PR D - Make buttonSuccessBR red

This is a dummy PR as part of testing https://github.com/Expensify/Expensify.cash/pull/3216. It will soon be reverted.
QA Steps
Verify that this PR has been reverted. Hit Split Bill or Request Money, then enter a value on the Request Money page. The Next button should be green, not red.

:warning: :warning: Heads up! This pull request has the CP Staging label. :warning: :warning:
Merging it will cause it to be immediately deployed to staging, even if the open StagingDeployCash deploy checklist is locked.

🚀 Deployed to staging in version: 1.0.61-8🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production in version: 1.0.62-0🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Chrome crashes on pnpm install task

Describe the bug
Open https://stackblitz.com/~/github.com/ukrbublik/react-awesome-query-builder in Chrome.
Initial task pnpm i && pnpm run leads to Chrome tab crash
Link to the blitz that caused the error
https://stackblitz.com/~/github.com/ukrbublik/react-awesome-query-builder
Steps to reproduce

Go to  https://stackblitz.com/~/github.com/ukrbublik/react-awesome-query-builder in Chrome
Chrome tab crashes with "Aw, Snap!" message. Error code: 5

Clearing cache and all data does not help
Expected behavior
No crash.
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform
Version = 1.84.0
Hash = 499be3932f50ab06349575b1c9042f95bc072a8b
WebContainer = 41692973

Browser name  = Chrome
Full version  = <IP_ADDRESS>
Major version = 126
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 120119164,
  "usedJSHeapSize": 94810620,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}

Additional context
No crash in Firefox

Im getting the same error with my repo. I cannot understand how can fix.


Message bubbles too small, text truncated

Hello,
My message bubbles are too small and the text gets truncated after just a few words. Do I need to include a bubble text size delegate method? This is the second project that I've used JSQMessages in and I didn't have this problem last time. That was in Objective C and I have moved to Swift.
Also, the input text view does not clear automatically after pressing the Send button. Do I have to do that too?
And, for some reason, I cannot get a back button or dismiss button on my MessagesViewController after trying all kinds of things to get a left bar button on the navigation item. The controller is brought up through a Show segue.
I have a demo on Weds so I would appreciate any help you could give me. Happy Holidays to all.

Anybody? anybody?

I think folks are on holiday instead of waiting around to help you, or hoping you'll take the time to look through old issues for your solutions. You can use the is:closed tag on the search field to see them, or clear the is:open tag.
There is no textSize delegate, it is calculated from the text. You may not be setting unique hash values, or If you are changing the value of your text bubbles any time after they are first loaded you may need to invalidate the collection (shown here in ObjC)
    JSQMessagesCollectionViewFlowLayoutInvalidationContext *context = [JSQMessagesCollectionViewFlowLayoutInvalidationContext context];
     context.invalidateFlowLayoutMessagesCache = YES;
     [self.collectionView.collectionViewLayout invalidateLayoutWithContext:context];
     [self.collectionView reloadData];

To clear the input text, you probably want finishSendingMessageAnimated, or clear it yourself from
inputToolbar.contentView.textView
The missing back button is not a problem with the JSQ view controller, it's probably something about the way you are doing it in your Swift code. Check your constraints and scroll insets, verify that you have a nav controller, try setting the buttons programmatically to see if they show up, set a breakpoint and use the 3d view debugger to see if your nav bar is hidden under something, try using a placeholder / dummy UIViewController to verify that your segue is correct.

Thanks Eli, I appreciate the advice, sorry to sound impatient. ;) I wish I was on holiday.....

Thanks for the answer @eliburke ! Much appreciated! :christmas_tree: :smile:


Fix class name in reports

Can you elaborate on what this fixes? What was observed before and what is observed afterwards?

Sorry.  Using current minitest, reports don't report the test class, they list Minitest::Result.  Or, reports look like:
Minitest::Result#test_add_classification_incorrect_number_of_arguments_one = 0.65 s = .
Minitest::Result#test_get_classification_value_string = 0.68 s = .
Minitest::Result#test_get_classification_value_incorrect_number_of_arguments_zero = 0.68 s = .

After the patch, they look like:
TC_Sketchup_Image#test_explode = 0.04 s = .
TC_Sketchup_Image#test_explode_incorrect_number_of_arguments_one = 0.03 s = .
TC_Sketchup_Image#test_image_rep_too_many_arguments = 0.03 s = .

Thanks, Greg
Note: Below I've attached a script (su_gem.rb.txt, rename su_gem.rb) that allow one to easily perform Gem operations from the SU console.  See notes in file.  Four issues:

Gems that require compiling normally shell out to another Ruby instance.  Since SU does not include 'ruby.exe', they cannot be build / installed.

Some gems add binary files (Puma, Rake, RubyGems, Thin, etc) that can be used from the command line.  I haven't checked to see how these install, as sometimes that requires UI action from the user.

--user-install can be done, but, at present, SU cannot access the folder.  I do have a patch for that if anyone's interested.

Not required, but I would recommend updating RubyGems, which does involve a few steps.

For a RubyGems command reference, see here.
su_gem.rb.txt

Will this patch impact older version of Minitest?

Will this patch impact older version of Minitest?

Yes.  Sorry.
I just checked in 2016 with 5.4.3.  Long story, but Minitest doesn't tag the repo with versions, so checking things version by version is a PITA.  The Result class was added in v5, so I assumed 5.4.3 had the klass attribute.  It does not.  I'll update the PR...
Greg

Closing in favor of #217


Storybook stories for Input components

I created this PR but didn't write any of the code. I'm allowing myself to review it and approve it.


Use resources "name" instead of playing with "id"

With the renaming made in the agent, it is now possible/easier to just
use the name instead of playing around with trimming the id or the name.
Also update to latest commit of ui-services required by Update DS.

Merged #702
The itests aren't passing but that is another issue entirely.


Populate payment details during wallet import

This PR fixes an issue where after importing some wallets into the repository the HDPayment details are missing.

We should also consider whether we should include transactions at all when importing wallets. It would be safer to let them sync from the block store.


If your machine's time is set to 15 mins into the future, nexd will fail to login

Describe the bug
If your machine's time is set to 15 mins into the future, nexd will fail to login.  It will get an error similar to:
dist/nexd --service-url https://qa.nexodus.io/
{"level":"info","ts":"2023-09-18T18:24:47.692-0400","caller":"nexd/main.go:108","msg":"Starting node agent with wireguard driver"}
Your device must be registered with Nexodus.
Your one-time code is: IOCQ-CVKT
Please open the following URL in your browser to sign in:
https://auth.qa.nexodus.io/realms/nexodus/device?user_code=IOCQ-CVKT
Authentication succeeded.
{"level":"warn","ts":"2023-09-18T18:24:58.088-0400","caller":"nexodus/nexodus.go:409","msg":"client api error - retrying: oidc: token is expired (Token Expiry: 2023-09-18 18:13:13 -0400 EDT)"}

How to Reproduce
change your machines time to be 15 mins in the future.
Expected Behavior
Nexd should eith cope with machine times that are wrong, or it should provide a better error message so the user knows that his machine time is incorrect.
Deployment Environment
No response
Additional Context
No response

The apiserver could provide what it thinks the current time is so that the client can detect this invalid time condition.


vi script

Can you quickly tell me which model this is supposed to be exactly?
How private/global are the latents?

Can you quickly tell me which model this is supposed to be exactly?
How private/global are the latents?

This is the model with only one scalar as global variational parameters.

Where are the others?
On Tue, Apr 27, 2021 at 7:46 AM Yuanqing Wang @.***>
wrote:

Can you quickly tell me which model this is supposed to be exactly?
How private/global are the latents?
This is the model with only one scalar as global variational parameters.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/yuanqing-wang/stag/pull/4#issuecomment-827664256, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKWCLYGPXIZXL6TIJGZ4MLTK3E55ANCNFSM424T74BQ
.

Hello?
On Tue, Apr 27, 2021 at 7:56 AM Theofanis Karaletsos <
@.***> wrote:

Where are the others?
On Tue, Apr 27, 2021 at 7:46 AM Yuanqing Wang @.***>
wrote:

Can you quickly tell me which model this is supposed to be exactly?
How private/global are the latents?
This is the model with only one scalar as global variational parameters.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/yuanqing-wang/stag/pull/4#issuecomment-827664256,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKWCLYGPXIZXL6TIJGZ4MLTK3E55ANCNFSM424T74BQ
.

name: STAG_VI(R)
parameters: mu \in R(1); log_sigma \in R(1)
sampling: sample two numbers for each feature, each edge, and each graph


Delete user information in database before deleting auth account

To keep the db clean, as re-creating an account with the same information will assign it to a new uid.

Seems OK, but sometimes the i18n preference path is recreated sometime within the deletion workflow.

i18n re-writing was a dodgy case where db was init'd from user change. It's only needed to init it upon user action in the preferences.