This commit adds main audits to the default list of reported metrics …

…for multi run. Unfortunately, my skills in node js are limited and I can not fix the problem with the metrics in multi run in another way (In multi run in latest release available only default metrics and you can not choose any else). Please, push it to the sitespeed ASAP.

Hi @MaximSergeichik I don't think this will work. The page summary name space is kept for the summary of each run, so median/pX. And by default the aggregation in Graphite is 10 min (as we have in our default Graphite setup), so if you do multiple runs and push the data into the same bucket, only the latest value will be kept. To keep these metric I think the metrics needs to live under another namespace, so that you can setup different rules for it in Graphite.

Hi @soulgalore,
I push metrics into InfluxDB, and when I tested the solution which were suggested aggregated metrics were added to the InfluxDB as a few series like it happens with the scores when lighthouse configured to make multiple runs. Proof you can find in attached screens.


feat: Add unique_id output of the lambda role

Description
Added unique_id output of the created lambda role.
Motivation and Context
We have s3 bucket policies that use the unique role id to restrict access to specific roles. This make sure I can create the lambda role with the module instead of creating the role separately or using a data resource to get the required variable.
Breaking Changes
Doesn't break anything as far as I am aware.
How Has This Been Tested?

[ ] I have tested and validated these changes using one or more of the provided examples/* projects
Applied this using terraform 13.4 and 1.0 and used the output of this feature

Thanks, @pglagerweij for the PR!


failed to start on centos 6.5

/home/rscott/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rsb-gol-0.4.1/lib/rsb/gol/cli.rb:53:in ioctl': Invalid argument (Errno::EINVAL) 	from /home/rscott/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rsb-gol-0.4.1/lib/rsb/gol/cli.rb:53:in screen_size'
from /home/rscott/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rsb-gol-0.4.1/lib/rsb/gol/cli.rb:14:in start' 	from /home/rscott/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor/command.rb:27:in run'
from /home/rscott/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in invoke_command' 	from /home/rscott/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor.rb:359:in dispatch'
from /home/rscott/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor/base.rb:440:in start' 	from /home/rscott/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rsb-gol-0.4.1/exe/gol:5:in <top (required)>'
from /home/rscott/.rbenv/versions/2.2.2/bin/gol:23:in load' 	from /home/rscott/.rbenv/versions/2.2.2/bin/gol:23:in '

replaced terminal size code with highline gem


Code change request - IF wrapper

We are trying to port a popular NAV add-on to an extension, and are hitting a number of roadblocks.  Here's the latest one...
We would like to request a small code change to the GetDimensionSet function in Codeunit 408.  There is currently a line in that function for:
    TempDimSetEntry.INSERT;

We need this changed to:
    IF TempDimSetEntry.INSERT THEN;

Basically, this call is preventing our functionality from working.  We have logic that populates dimension value(s) based on OTHER dimension values.  Because our logic may have already triggered the addition of another dimension value to the dimension set, the INSERT above is erroring out because the record already exists.  In the NAV version of our product we made the code change above and it works great...but of course we have no way to do that in an extension.

I found a way to work around this...but it's a bit ugly.  It would be cleaner with my suggested change, but if you don't want to make the change i'll be okay.

If you found a workaround, we would prefer to prioritize other issues for which there are no workarounds yet. Thank you for reporting! If this comes up again at a later time, please log again and we'll look more closely into it.


Change CrateSearchContext to not extend SearchContext

Most of the SearchContext properties were unused - pulling in a lot of
dependencies that are not required.

Current coverage is 81.22% (diff: 100%)

Merging #4556 into master will increase coverage by 0.02%

@@             master      #4556   diff @@
==========================================
  Files          1296       1296
  Lines         44176      44110    -66
  Methods           0          0
  Messages          0          0
  Branches       7021       7015     -6
==========================================
- Hits          35872      35830    -42
+ Misses         5612       5577    -35
- Partials       2692       2703    +11

Powered by Codecov.


Update _index.md

Update to Appstore/Marketplace  release notes for release on 24th March.

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


[DM-5637] Update README.md and remove unused dependency.

Update README.md and remove unused dependency.
modified:   README.md
modified:   setup.py

Don't forget to mention the auth token stuff.


Allow repository authors to set a default branch name.

I left the default as master for now, since we haven't worked through all the likely assumptions in other tools.

nice, thanks!


[WIP] Add copyright acknowledgements

This is not ready for merge!
Draft fixing the attribution with assistance of licensecheck (fixes #99 ).
Notices and licenses should not only be contained in the node package, but also send to each end-user in whose browser JSO is executed. This way it is easy for JSO users (i.e. those who distribute JSO from a server) to comply with the licence conditions.
Needs some feedback (@rcombs, @TFSThiagoBR98).

Is there a better way to include the copyright and license notices than prepending it all to subtitles-octopus.js?
I'm not sure about the copyright notice granularity, perhaps it would be better to be coarser and merge same licence copyright notices per project?
licensecheck isn't always correct or able to determine the license (afaict the info for the currently included sources isn't wrong though missing a dual licensing). What to do about those non/mis-detections?
What to do about files missing a copyright notice? (currently this check is partially overwritten, otherwise it fails)
Is everyone ok with requiring licensecheck for the build? Or would including a static, manually updated notice-text be preferable?
It would be good, if someone could check that the way the attribution is done is actually correct de jure;
same for the LGPL-3.0-or-later tag in package.json

If anyone else also already looked into this: Are there other tools to detect copyright and licence than licensecheck? How do they compare in accuracy, coverage and availability in repos?
Btw,  src/unbrotli.js is Apache-2.0 licenced, requiring redistribution of the full text of Apache-2.0. Afaict there currently is no copy of Apache-2.0 inside the repo and with this it only is in build/license_fullnotice.
If anyone of the JSO maintainers wants to take this over to speed it up or because of better licence-copyright-knowledge, fell free to do so.

Is there a better way to include the copyright and license notices than prepending it all to subtitles-octopus.js?

I think simply include a license header point to build/license_fullnotice file in subtitle-octopus.js might be enough.

It would be good, if someone could check that the way the attribution is done is actually correct de jure;
same for the LGPL-3.0-or-later tag in package.json

The license in package.json must include all licenses used in this project, using SPDX expressions, see an example

If anyone else also already looked into this: Are there other tools to detect copyright and licence than licensecheck? How do they compare in accuracy, coverage and availability in repos?

In a quick search, I found this project https://github.com/licensee/licensee, I don't know if it's better than licensecheck, but its used by Github.

I think simply include a license header point to build/license_fullnotice file in subtitle-octopus.js might be enough.

How would build/license_fullnotice be distributed in both the npm package and to end-users watching subs with JSO?
Also _fullnotice only has the license notice or full texts not the copyright notices crediting the people whose work is being used, so it alone is not sufficient.

In a quick search, I found this project https://github.com/licensee/licensee

Apart from having extra ruby dependeciey and afaik being packaged nowhere, at first glance this appears to only categorise LICENSE files, not copyright notices and licenses headers inside source files.

The license in package.json must include all licenses used in this project, using SPDX expressions, see an example

The reasoning for LGPL-3.0-or-later is, that to my knowledge (ianal and so) the effective total license for the binary is LGPL-3.0+ as everything else could be (implicitly) relicensed to it without violating or dropping any prior terms. But then again, eg Apache-2.0 requires redistribution of its license text — I don't know how this plays with the implicit relicensing I assumed.
While I only see examples of dual-licensing (or not and) in the linked examples, I guess listing all would be safer (but more complicated to figure out for users).

New version:

Copyright notices are no longer connected to individual source files, only licence and project
Afaict this should be fine, but ianal. This made the copyright acknowledgments more compact.
Split NTP and NTP~disclaimer; they are basically identical just the warranty disclaimer is more verbose in the latter, but to be safe both full texts are now included. (SPDX doesn't have an identifier for NTP~disclaimer, it only knows about NTP and NTP-0, yet another variant)
package.json now lists all licences with SPDX (using NTP for NTP~disclaimer)
Added info about SPDX-names to full notices (somewhat confusingly Harfbuzz itself and Debian call Harfbuzz' licence Old MIT/MIT~old, but SPDX and Fedora refer to it as MIT-Modern-Variant)
excluded mroe paths for licensecheck

Personally (and assuming it is legally fine), I'm content with the copyright+license acknowledgement itself now. It could be further compressed by merging copyright notices from the same person but different years, but I'm not sure that's worth the effort (consider that sometimes a single copyright notices also lists multiple people).
Remaining issues:

some minor cleanup
is there a better way to distribute the notices than merging into subtitlesoctopus.js?
add (separate) Apache-2.0 licence to repo or prominently point to build/license_fullnotices to satisfy src/unbrotli.js
needs review

@TheOneric I've reviewed here, looks good, but:

is there a better way to distribute the notices than merging into subtitlesoctopus.js?

Include the full text license make the file 3.5x bigger than before, i think its better to only include the copyright notices and a link to each license.

add (separate) Apache-2.0 licence to repo or prominently point to build/license_fullnotices to satisfy src/unbrotli.js

We can move unbrotli.js to its own folder in lib and include the Apache License copy there, also include a point to it in the main LICENSE file

Resulted file: subtitles-octopus.txt

Include the full text license make the file 3.5x bigger than before, i think its better to only include the copyright notices and a link to each license.

No. As written before some (most, actually) license require redistribution of the full license text together with the distributed binaries or source. Of the licences used in JSO, only FTL allows a shorter notices with a link t othe full text for binary (but not source!) distribution; as you may have noted this is also the only licence to do exactly this as per the introductory comment of license_fullnotice:
# The following section contains the full license text or
# where permitted a shorter notice for all works contained
# in JavascriptSubtitlesOctopus listed above

The full texts must be included.
Also while the relative size increase of just subtitles-octopus.js is large, the absolute increase compared to the absolute size of the worker binaries is marginal.

Now to explain why a separate file is no good (in itself) and why the subtitles-octopus.js-preamble is also not ideal either:
As hinted in this pr's first post, there are two distribution processes here that we want to take into account.
The first one is us distributing the binaries as an npm-package and via GitHub-build-artifacts. For this step including a separate  copyright file (and perhaps even separate files for each licence) would be fine, as all who receive the binaries also recieve the copyright file and it is easy to notice.
However, the second step is distribution from the server's of those who incorporated JSO into their webpages/webapps/… . Just like before, the full texts must be distributed alongside the binaries. Separate licence and copyright files from the npm-package will never get send to the end user, so if this were to be the only thing we do we'd set up all JSO users to commit copyright violations.
subtitles-octopus.js is iiuc a prerequisite to obtain any other binaries, therefore prepending the notices and license text to this file is the easiest way to ensure the text gets distributed to all end users in this second distribution step as well. But though easy the notices are now less discoverable in the package of the first step. Discoverability in the second distribution step is innately hard, so I'm not sure we can do much better there.
If possible, we could in theory also make sure a seperate copyright file gets send to the end-users, but that would even harder to discover and connect to JSO htan merging into the js file as now (consider: one would need to monitor the net request from the webpage, notices that there's a copyright file loaded (but never shown on the site itself) and then figure out which f iles got requested together with it).
From my limited knowledge about how JSO integration works, it appears to me like prepending to subtitles-octopus.js is the best approach for the second distribution step, but there might be other, better possibilities I'm not aware of.
However, for the first distribution-step (and the source distribution of unbrotli.js) this prepending is suboptimal as the notice is hard to discover. We could eg also include an additional seperate notices, prominently placed in the npm- and GH-packages and our repo to deal with this. This standalone notice would only be distributed in the first but not the second step; in the second step only the still present subtitles-octopus.js-preamble would be distributed to end-users. This is however also not ideal as it duplicates the notices.

We can move unbrotli.js to its own folder in lib and include the Apache License copy there

Where does unbrotli.js even come from? The brotli-submodule also has a JavaScript subdir which we aren't currently using (and which borks out licensecheck's copyright notice detection). If with putting it into its own subfolder you mean using a submodule to also allow us to easily update it in the future, then this sounds good. If it just remains a regular static file however, I don't see which benefit there is in a separate subfolder just for this one file. There aren't many files in src/ to begin with.
Can you elaborate on what you're intending?

also include a point to it in the main LICENSE file

If with “main LICENSE file” you mean LICENSE in the repo's root, then there's no need for that I think.

Where does unbrotli.js even come from?
I don't remember why i used this file, but it works with brotli submodule copy with a little mod in decode.js.

We can remove unbrotli.js file and use the Brotli submodule implementation

I don't remember why i used this [src/unbrotli.js] file, but it works with brotli submodule copy with a little mod in decode.js.
We can remove unbrotli.js file and use the Brotli submodule implementation

The minified javascript implemntation (lib/brotli/js__/decode.min.js) bugs licensecheck's copyright notice detection, instead using a chunk of code as the "copyright holder", if you want to change it this way, make sure to not use this (emscripten can do its own minisation anayway)  and adjust LIB_LICENSES_FINDOPT_brotli in Makefile to not exclude anything contained in the build, but still exclude the buggy file.
Though, since we already use the brotli C library, why not use this via WASM¹ instead of yet another brotli implementation, this time in pure JS?
Either way, if desired, this should be done separately as it is out of scope for this pr.

1: Ofc, there's the "fun" disparity with JS using native endianess, but WASM for some reason requiring Little-Endian for its types, but since this only decompresses files byte per byte iinm, this shouldn't be a problem here, or is it?

Rebased after the brotli change and excluded the unused decode.min.js which borks the copyright detection.
Also bumped JSO's copyright year.


Delete old devices

Is there some way to add delete option for devices/sensors?
For example Im replace normal PIR sensor with PIRCAM and remove PIR sensor from AX PRO. But on home assistant this sensor is still visible as device:

For example some integrations have option to delete device:

Thanks.

I will take a look how other integrations does that. I see MQTT has that functionality, but if the device is not tracked by the system i dont know if it will work correctly.
Anyway posibility is for example https://github.com/brettonw/Remove-Home-Assistant-Device as workaround.


bump version to 2.1.9

What was changed

forgot to bump the version in package.json in #724
Why?

Checklist

Closes

How was this tested:

Any docs updates needed?

done in #726


Input componest is not passing down the JSX attribute inputMode.

Feature Request
Implement inputMode on Input Component
Problem description
I have a input component that needs to be typed as text, but is limited to receive only numbers and a specific set of symbols, I can manage all this very well so far but when a user (mobile) clicks to edit this input the alphabetical keyboard pops up.
I've tried adding patterns, didn't work.
Proposed solution
Simplest solution I've came with is to make this component accept a prop just like props.type (as it already does), so it can pass down this attribute to
MVP
First time I try this kind of stuff, but i think you might get the idea.
https://github.com/Semantic-Org/Semantic-UI-React/compare/master...HcDuller:patch-1

This is already supported:
<Input inputMode="numeric" placeholder="Search..." />

Will produce:
<div class="ui input">
  <input type="text" inputmode="numeric" placeholder="Search..." />
</div>


Nuitka uses old version of python files

Dear all,
could you tell me how to clean the cache of Nuitka?
I installed Nuitka in my CI system but it somehow caches the python files. I want to clean the cache and use everytime the new files.
I don´t care if this makes the process slower.
Thank you in advance!

One if not the most glaring missing features is actually using of a caching for the python things, but once I do, I surely will add an option for it. Or are you saying you have evidence of it using old files? Then I would love to have a reproducer.

Lack of feedback


Build against Java 17, 18, 19

Since we've upgraded main to Spring Boot 3 and Java 17, we also need to include Java 18 and Java 19 in Github actions builds.

Hi @maciejwalkowiak,
Can I get this issue?

@mcruzdev go for it!

Hi @maciejwalkowiak,

There are just version 17 and 19 on sdkman version 5.16.0

@mcruzdev makes sense! Let's skip 18. I think this PR would be ready for review then, right?

I opened the PR #550, thank you :)

Closed in #550
Thanks @mcruzdev!


Proposal to add awesome-db-tools

https://github.com/mgramin/awesome-db-tools
This is a list of database tools (ide, cli, managing, monitoring, migrations, modellers, visualization etc)
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Either fullwidth or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.
Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of sub-lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

Please go through the checklist one-by-one. I really like the checklist and we are still working on getting our awesome-bpm list ready.
Seeing https://github.com/mgramin/awesome-db-tools/commits/master, the list is not around for 30 days. This is the first item on the above checklist.
I would propose that you close this PR, go through the list point by point an reopen the request as soon as you feel all points are followed.

I apologize for my inattention when reading the checklist. Thank you for the clarification. When the project matures, I will check the checklist again and make a new corrected PR.

I created new pull request - https://github.com/sindresorhus/awesome/pull/1336


Can someone provide compiled version?

I've set up GitHub actions, now DLLs for Windows are built automatically. Release


ref(*): refactor kubectl to a package

Closing for now.  I will rebase and open a new pull request.


Provide isolate id for rpc request to ensure they are run on correct (UI) thread.

This works together with https://github.com/flutter/engine/pull/5263 and goes towards fixing flutter/flutter#17434

This coincides with a significant regression in some benchmarks. e.g.,
hot_mode_dev_cycle_linux__benchmark
hotReloadMillisecondsToFrame

https://github.com/flutter/flutter/issues/17705

cc @tvolkert Interesting side-note regarding your investigations: this coincides with a massive improvement on the hot restart benchmark. Maybe this PR changed the accounting?


[Doc] python example Part uploadImage correction

just a small correction to the python example.

Thanks for the fix!


Apple Match-O Linker Error when building on iOS

After running the followings commands:

npm install
react-native link react-native-svg
The xcode projects throws an "Apple Match-O Linker Error" error message.
My package.json uses:
react-native: "0.45.1"
react-native-svg: "5.2.0"
react: "16.0.0-alpha12"

The problem appears when using react-native link for the react-native-svg folder, I can build when I unlink that very same folder.
Any help would be appreciated.

In Link Binary with Library, try removing the -tvOS.a file. Thats what I did and got it to build

I am having this same issue. @alexwasner can you be a little bit more specific on your solution? I don't understand... THX!

@ansierras in the build phases of your project, open Link Binary With Libraries, select libRNSVG-tvOS.a and click - to remove it.

Perfect. This solved the problem for me! :D

duplicated with: #387

Undefined symbols for architecture x86_64:
"OBJC_CLASS$_FBSDKHashtag", referenced from:
objc-class-ref in libRCTFBSDK.a(RCTConvert+FBSDKSharingContent.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
I don't have -tvOS.a file in the binary list, so how i can resolve this error ?

while building react-native project in xcode following errors are occured,
clang: error: unknown argument: '-no_deduplicate'
clang: error: no such file or directory: '/Users/pradeepkrish/Library/Developer/Xcode/DerivedData/projectname-bcvkbiqlzwpsqadbqmrlcqgqzvzz/Build/Intermediates.noindex/projectname.build/Debug-iphonesimulator/InnovaZones.build/Objects-normal/x86_64/InnovaZones_lto.o'
clang: error: no such file or directory: '2'
clang: error: no such file or directory: '/Users/pradeepkrish/Library/Developer/Xcode/DerivedData/projectname-bcvkbiqlzwpsqadbqmrlcqgqzvzz/Build/Intermediates.noindex/projectname.build/Debug-iphonesimulator/projectname.build/Objects-normal/x86_64/projectname_dependency_info.dat'
how can i solve this.Any suggestion?

@OssamaZ I am not having any libRNSVG-tvOS.a in the link library. I am having libRNSVG.a only. Any help?

https://stackoverflow.com/questions/39545880/apple-mach-o-linker-ditto-error-xcode-8


Missing closing brace in code example

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@codyborn : Thanks for your contribution to the Azure documentation! The author, @arramac, has been notified to review your proposed change.

thanks you @codyborn

#sign-off


unixPB: Add gcc9 for Dragonwell

Signed-off-by: Stewart X Addison<EMAIL_ADDRESS>
[x] commit message has one of the standard prefixes
[ ] FAQ.md updated if appropriate
[ ] other documentation is changed or added (if applicable)
[x] playbook changes run through VPC or QPC (if you have access) - VPC / QPC VPC / QPC - Final VPC on all three CentOS
[ ] inventory changes, ensure bastillion is updated accordingly

@sxa  Thanks.

Now I am testing with joeylee97/dragonwell_centos7_gcc9_build_image.
The dockerfile is
FROM adoptopenjdk/centos7_build_image

RUN yum update -y
RUN yum groupinstall "Development Tools" -y
RUN yum install wget -y
RUN curl -O https://ftp.gnu.org/gnu/gcc/gcc-9.2.0/gcc-9.2.0.tar.gz
RUN tar xzf gcc-9.2.0.tar.gz
WORKDIR /gcc-9.2.0
RUN ./contrib/download_prerequisites
WORKDIR /
RUN mkdir gcc-build
WORKDIR /gcc-build
RUN ../gcc-9.2.0/configure                           \
    --enable-shared                                  \
    --enable-threads=posix                           \
    --enable-__cxa_atexit                            \
    --enable-clocale=gnu                             \
    --disable-multilib                               \
    --enable-languages=all                           \
    --prefix=/usr/local/gcc-9.2.0/
RUN make -j 4

@sxa Thanks.
Do we need to sync with openjdk-build/build-farm/platform-specific-configurations/linux.sh?
like
if [ -r /usr/local/gcc/bin/gcc-9.3.0/bin/gcc ]; then
  export PATH=/usr/local/gcc/bin/gcc-9.3.0/bin:$PATH
  [ -r /usr/local/gcc/bin/gcc-9.2.0 ] && export CC=/usr/local/gcc/bin/gcc-9.2.0
  [ -r /usr/local/gcc/bin/g++-9.2.0 ] && export CXX=/usr/local/gcc/bin/g++-9.2.0
  export LD_LIBRARY_PATH=/usr/local/gcc/lib64:/usr/local/gcc/lib
elif [ -r /usr/local/gcc/bin/gcc-7.5 ]; then
  export PATH=/usr/local/gcc/bin:$PATH
  [ -r /usr/local/gcc/bin/gcc-7.5 ] && export CC=/usr/local/gcc/bin/gcc-7.5
  [ -r /usr/local/gcc/bin/g++-7.5 ] && export CXX=/usr/local/gcc/bin/g++-7.5
  export LD_LIBRARY_PATH=/usr/local/gcc/lib64:/usr/local/gcc/lib
elif [ -r /usr/bin/gcc-7 ]; then
  [ -r /usr/bin/gcc-7 ] && export CC=/usr/bin/gcc-7
  [ -r /usr/bin/g++-7 ] && export CXX=/usr/bin/g++-7
fi

Also, could we publish it to adopt image registry?

It will to go live, but so far I've been unable to build successfully with the new gcc level

@sxa Thanks.
Do we need to sync with openjdk-build/build-farm/platform-specific-configurations/linux.sh?
like
if [ -r /usr/local/gcc/bin/gcc-9.3.0/bin/gcc ]; then
  export PATH=/usr/local/gcc/bin/gcc-9.3.0/bin:$PATH
  [ -r /usr/local/gcc/bin/gcc-9.2.0 ] && export CC=/usr/local/gcc/bin/gcc-9.2.0
  [ -r /usr/local/gcc/bin/g++-9.2.0 ] && export CXX=/usr/local/gcc/bin/g++-9.2.0
  export LD_LIBRARY_PATH=/usr/local/gcc/lib64:/usr/local/gcc/lib
elif [ -r /usr/local/gcc/bin/gcc-7.5 ]; then
  export PATH=/usr/local/gcc/bin:$PATH
  [ -r /usr/local/gcc/bin/gcc-7.5 ] && export CC=/usr/local/gcc/bin/gcc-7.5
  [ -r /usr/local/gcc/bin/g++-7.5 ] && export CXX=/usr/local/gcc/bin/g++-7.5
  export LD_LIBRARY_PATH=/usr/local/gcc/lib64:/usr/local/gcc/lib
elif [ -r /usr/bin/gcc-7 ]; then
  [ -r /usr/bin/gcc-7 ] && export CC=/usr/bin/gcc-7
  [ -r /usr/bin/g++-7 ] && export CXX=/usr/bin/g++-7
fi

Also, could we publish it to adopt image registry?

It will to go live, but so far I've been unable to build successfully with the new gcc level

We did some changes including:
https://github.com/alibaba/dragonwell11/commit/9d0ad338f3b65f6d0c3ae7ba5c4811200cf84ade
https://github.com/alibaba/dragonwell11/commit/1e5ace979799a10e24e08ae0a65b1c68c6fdcc17

Hmmmm Mac Os X brew running on a solaris node?

Hmmmm Mac Os X brew running on a solaris node?

Sorry - what's that comment in relation to?

The Vagrant Playbook checker failed.

The Vagrant Playbook checker failed.

Not sure why - this doesn't affect Solaris or macos, but the brew thing is from the check defined in https://github.com/AdoptOpenJDK/openjdk-infrastructure/blob/master/.github/workflows/build_vagrant.yml

The Vagrant Playbook checker failed.

Not sure why - this doesn't affect Solaris or macos, but the brew thing is from the check defined in https://github.com/AdoptOpenJDK/openjdk-infrastructure/blob/master/.github/workflows/build_vagrant.yml

This is actually fixed, you just need to rebase.

Solaris check now passing @karianna

This seems to have worked based on running it on a real machine outside a docker container: https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-linux-x64-dragonwell/157/console

I'm not entirely sure why, but every time I use GCC9 on aarch64 to compile dragonwell (started with 9.3, then moved to 9.2) I get compilation failures starting with:
./test/hotspot/jtreg/compiler/calls/common/libCallsNative.c:44:22: error: base operand of ‘->’ has non-pointer type ‘JNIEnv’ {aka ‘JNIEnv_’}
   44 |   jclass cls = (*env)->GetObjectClass(env, self);
      |                      ^~

and failures in in check_code.o and AccessController.o. No such problems with 7.5.
Adding this info here so I can return to it on Monday


[MM-12582 & MM-12745] Migrate PostActions.handleNewPost to redux actions

Summary
Migrate PostActions.handleNewPost to redux actions.
Affected Areas:
Receiving new post via websocket, send ephemeral post.
@DHaussermann @lindy65 May I request for your smoke tests? This could be tested by:

sending /leave command at reply thread --> should see ephemeral post that such command is not supported on thread view
at-mention a user that's not member of a channel --> should see ephemeral post to add that use to a channel
have 2 users on different browser, viewing different channel or team.  If user A post, user B should see dot (*) on team name if it's posted on different team, or see a mention badge if it's a at-mention.

Ticket Link
Jira ticket: MM-12582 && MM-12745
Checklist

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit and component tests passed
[x] Added or updated unit tests (required for all new features)

@enahum I've created post_utils where I put other functions not necessarily exported but only for the purpose of being tested individually.

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).

Thanks @saturninoabril
I've tested the PR:

The ephemeral message for /leave in the RHS is showing

above the post in the center channel
between the parent post and reply in the RHS

at-mentioning a user who is not in the channel is behaving as expected with ephemeral post in correct place and I am able to add the user to the channel from the ephemeral post

For

have 2 users on different browser, viewing different channel or team. If user A post, user B should see dot (*) on team name if it's posted on different team, or see a mention badge if it's a at-mention.

This is working as expected if I message in a private or public channel.  However, this is not working if I make a direct message post to the user (but expect this may be related to the "add member" issue that is broken on master right now?)

Thanks @lindy65!
For no. 3 above, Lindy and I agreed that the issue is on DM channel creation (which is a known issue on master) and not on posting to DM channel.  Posting to DM/GM channels work as expected - bolded channel name on LHS or with mention badge on new post receive or on user at-mention, respectively.
This is now ready for dev review.

For 1) above, Saturn and I did some further testing on the ephemeral message and it's now being placed correctly below the parent post/reply.

As this was inconsistent testing on the same spinmint from yesterday to today, Saturn and I have agreed that it's something to watch out for in the future but code for that was not touched by this PR.

Spinmint test server destroyed


TypeError: mix.extend is not a function

mix.extend('polyfill', new Polyfill());
show error when command run " npm run watch "
webpack.mix.js :
let mix = require('laravel-mix');
require('laravel-mix-polyfill');
mix.js('resources/assets/js/app.js', 'public/js')
.sass('resources/assets/sass/app.scss', 'public/css')
.polyfill({
enabled: true,
useBuiltIns: "usage",
targets: {"firefox": "50", "ie": 11}
});

@Dev-El-badry what version of Laravel Mix are you using?

"devDependencies": {
    "axios": "^0.17",
    "cross-env": "^5.1",
    "jquery": "^3.5.1",
    "laravel-mix": "^1.0",
    "lodash": "^4.17.4",
    "vue": "^2.5.7"
},

SOLVED  !!
Update my version laravel-mix to the latest version and it SOLVED


Sqlsrv PDO driver from Microsoft

Uses the Sqlsrv PDO driver from Microsoft tested it using SQL Server 2005 Express. Related issue Issue #165.

Has anyone found a solution to this, or was it just abandoned because it was getting messy? If it's the latter, I'd like to take a swing at getting this working.

Has anyone found a solution to this, or was it just abandoned because it was getting messy? If it's the latter, I'd like to take a swing at getting this working.

I had time to fix it, you can see it modified in my repository
https://github.com/mohamadmulhem/php-activerecord
It is working well with MS SQL Server 2012 & 2014


Subscribe topic of Stream Collection with WebSocket.

This PR solves issue #290.
Note: This PR needs #293 #292 personium/personium-lib-common#42 personium/personium-lib-common#43.

This PR needs personium/personium-lib-common#45 too.


added @availability attribute to async functions

Hello, its me again...with some changes that are related to the previous PR (#85).
 Apparently, with MacOS (unlike Linux), it's not enough to wrap these async features in #if compiler(...), they need to be specified as compatible with  >= MacOS v12 with the @available attribute.
This PR repairs build errors for MacOS users running Swift 5.5 or newer.

Apparently, with MacOS (unlike Linux), it's not enough to wrap these async features in #if compiler(...), they need to be specified as compatible with >= MacOS v12 with the @available attribute.
This PR repairs build errors for MacOS users running Swift 5.5 or newer.

These checks do slightly different things, compile is a "ignore this code completely in Swift 4, <=5.4" where it would be invalid syntax and the compiler won't even understand it.
Availability is a runtime check for the platform running the compiled version. In some cases, compiler features require the platform or runtime support and require a minimum platform version. For consumers of Commander who are targetting macOS 12 amungst others are able to rely on async in all platforms. Whereas if you're building a piece of software using Commander and supporting macOS 11 and others, then you can only use async Commander optionally on newer platforms (using availability checks) and handle fallback for older platforms. I'd imagine most people using async Commander are likely going to opt for increasing their minimum platform target, but there are still going to be use-cases for people who do not want to drop support for older platforms and remain using sync-Commander.


Rolling machine in Alpha 1.1.7

I try to set the rolling machine，but even if it's same to what the holo projector displays，it's still unsuccessful。

What direction is the controller facing?  Is it facing away from the input hatches?
if so, when you right click it, where does the red X appear?

@zmaster587 Oh，the face must be correct……I‘m wrong。
But I think machines should have more correct faces。

What do you mean by more correct faces?

@zmaster587 I mean,now the correct controller facing has only one,or mistake will happen,so I hope the facing of machine shouldn't decide if the setting of machine is right--see Woot by ipsis,the facing of the mob factory must be right,it will trouble players.

Due to the way structures are handled the result could be ambiguous depending on the direction a machine is facing.  EX: Trying to build machine A and B next to each other, both machines have similar configurations, forming machine A may use machine B's blocks preventing machine B from forming.
The holo projector should be indicating the front of the machine, however I see in the screenshot there it is not. I'll see if i can figure out why


Make sure that common login providers work

[x] Facebook
[x] Google
[x] Twitter
[x] Yahoo
[x] Github
[x] Okta
[x] Firefox Accounts

Closing in favour of opening individual issues for other providers.


Add predictor collection route

Closes #40

Codecov Report

Merging #41 into master will increase coverage by 0.26%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #41      +/-   ##
==========================================
+ Coverage   93.76%   94.02%   +0.26%
==========================================
  Files          16       16
  Lines         433      452      +19
==========================================
+ Hits          406      425      +19
  Misses         27       27

Impacted Files
Coverage Δ

tests/test_predictor.py
100% <100%> (ø)
:arrow_up:

pyns/models/predictor.py
100% <100%> (ø)
: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 4320d74...0677e86. Read the comment docs.

Codecov Report

Merging #41 into master will increase coverage by 0.26%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #41      +/-   ##
==========================================
+ Coverage   93.76%   94.02%   +0.26%
==========================================
  Files          16       16
  Lines         433      452      +19
==========================================
+ Hits          406      425      +19
  Misses         27       27

Impacted Files
Coverage Δ

tests/test_predictor.py
100% <100%> (ø)
:arrow_up:

pyns/models/predictor.py
100% <100%> (ø)
: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 4320d74...0677e86. Read the comment docs.


[RFC]: quant llm from alpindale

Motivation.
Higher throughput und memory savings are always cool 😎
I think that could be integrated very easily, what do you think about it's design ?
Proposed Change.
https://github.com/PygmalionAI/aphrodite-engine/commit/73177656ed75ec880a409640ef2b9a8043cf96a8
Feedback Period.
No response
CC List.
No response
Any Other Things.
No response
Before submitting a new issue...

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

https://github.com/vllm-project/vllm/pull/8751


Add computation and retrieval of batch feature statistics

What this PR does / why we need it:
This PR adds support for retrieval of batch statistics over data ingested into a feast warehouse store, as proposed in M2 of the Feature Validation RFC.
Note that it deviates from the RFC in the following ways:

Statistics are computed using SQL. This is because TFDV is unfortunately, only available in python, and Multi-SDK connectors for Beam is still a work in progress. Computing the statistics using SQL will be the compromise until either TFDV is available in Java, or cross-language execution is supported.
Statistics can only be computed over a single feature-set at a time. This is mostly to reduce complexity in implementation. Since datasets are unable to span multiple feature sets, it makes sense to have this restriction in place.

This is a bit of a chonky PR, and the code itself requires a bit of cleaning up, hence the WIP status, but refer to the attached notebook for how this implementation looks like for a user of Feast.
Does this PR introduce a user-facing change?:

- Adds GetFeatureStatistics to the CoreService
- Adds get_statistics method to the client in the python SDK

Will try to review it tomorrow morning @zhilingc

I made a first run through.
The only big thing that stands out is the duplication between entity level statistics and feature level statistics. I'll think about how we can simplify this implementation because as written it is a lot of scary to merge this in.
Other than that I am finding it a bit slow going to review the PR because some of the methods require comments. I'd rather not ding the methods and ask for JavaDocs or comments, so would you mind just giving the PR a scan through and adding them? It would be especially useful for StatsService.java as well as the model fields.

I'll talk about the data model first because that is the most important part to get right now.
Assumptions

Entities are primarily used as keys
Features are primarily used as values in the context of models. Our users care more about statistics on features than on entities.
Features need references (like feature references).
Entities need references, but these references are different from features.
Entities will also be treated differently in the future (See #405). Constraints on features and constraints on entities are different. Entities will be reused and features must be unique by name.
Nothing prevents a user from ingesting entity data as a feature.

Thoughts

Although there is a use case for having entity level statistics, I don't think it warrants the amount of code we'd need to maintain here.
There are pre-existing problems with the data model that should be solved now before 0.5 is released. Normally that would happen in a separate PR, but we can also reuse this PR if that is easier for you.
One of the problems that I see is the fact that Field and its inheritence adds complexity without any real value.
The second is that there is a coupling between the references of features and entities that I don't think should exist.
Lastly, and this is definitely out of scope for your work, is that the source table is hardcoded to Kafka (thanks for the reminder @mrzzy . Will add a separate issue for that.)

Recommendation

Remove Field and its inheritance
Keep FieldId but rename it to FeatureReference
Have Feature reference FeatureReference as its primary key
Create an EntityReference (for the time being this can be the same as FeatureReference)
Keep FeatureStatistics and have it reference FeatureReference
Remove EntityStatistics completely as well as statistics methods on Entity.

cc @ches @Yanson

@woop

Features are primarily used as values in the context of models. Our users care more about statistics on features than on entities.
Although there is a use case for having entity level statistics, I don't think it warrants the amount of code we'd need to maintain here.

I think that’s a very strong assumption to make.
I’ve been back and forth about entity statistics the past few weeks; my first iteration only involved feature statistics, but i ended up adding support for entity statistics later because i think it is something that is truly valuable to users, for checking id distributions and bounds, etc. I don’t think it’s
To your point:

Nothing prevents a user from ingesting entity data as a feature.

This doesn’t make sense when you consider the user experience. Do they double-up on entity columns so that they can be ingested as features JUST to retrieve statistics? Do they ingest it as a separate dataset?

One of the problems that I see is the fact that Field and its inheritance adds complexity without any real value.

I’m not sure what sort of complexity you mean here. I think if we do have statistics for entities it’s a lot easier to maintain compatibility with TFDV fields with inheritance, which is the main reason why the class was introduced in the first place. Additional fields that differ between features and entities can be defined in their concrete classes.

The second is that there is a coupling between the references of features and entities that I don't think should exist.

Do you mean the fact that they use the same object? I guess it’s fine to separate them for the sake of forward compatibility…

Have Feature reference FeatureReference as its primary key
Do you mean have FeatureReference as a distinct entity and have feature sets, features and statistics reference that entity? I’m not sure if that’s the best idea.

Keep FeatureStatistics and have it reference FeatureReference
FeatureReference is part of the definition of Feature and FeatureStatistics cannot form a relation directly to it. To be exact, with the current implementation, the table definition for Features looks like:

-- Table Definition ----------------------------------------------

CREATE TABLE feature (
    feature_set character varying(255),
    name character varying(255),
    project character varying(255),
    version integer,
    bool_domain bytea,
    domain character varying(255),
    float_domain bytea,
    group_presence bytea,
    image_domain bytea,
    int_domain bytea,
    mid_domain bytea,
    natural_language_domain bytea,
    presence bytea,
    shape bytea,
    string_domain bytea,
    struct_domain bytea,
    time_domain bytea,
    time_of_day_domain bytea,
    type character varying(255),
    url_domain bytea,
    value_count bytea,
    CONSTRAINT feature_pkey PRIMARY KEY (feature_set, name, project, version)
);

And FeatureStatistics has the following constraint:
    CONSTRAINT fksrjnxx9em2xg2cqgd6ifm4lll FOREIGN KEY (feature_set, name, project, version) REFERENCES feature(feature_set, name, project, version)

Ok, I polled a few data scientists and they acknowledged that there is no need to have entity statistics except for occasional once-off checks, which can be done directly to the db anyway. I'll remove the entity statistics - but does that mean i remove the entity field schemas introduced in #438 as well?

I’ve been back and forth about entity statistics the past few weeks; my first iteration only involved feature statistics, but i ended up adding support for entity statistics later because i think it is something that is truly valuable to users, for checking id distributions and bounds, etc. I don’t think it’s

I think your sentence cut off there.
I agree that entity statistics are very useful, don't get me wrong, which is why we wanted them in the first place.
What doesn't line up for me is this implementation. As it stands, Feast does not support entity statistics. If I am forced to choose between having only feature statistics and merging in all of this code then I will definitely chose the former.
However, the idea case is that we can cleanly support entity statistics.

This doesn’t make sense when you consider the user experience. Do they double-up on entity columns so that they can be ingested as features JUST to retrieve statistics? Do they ingest it as a separate dataset?

My point here is that we can add feature statistics safely and support it properly without immediately supporting entity statistics. If users really want a work-around to get an idea of entity statistics then they can ingest them as features, which means adding additional columns. That would not be something we would officially support, and they don't lose anything over what they have today.
Duplicating this code for both entities and features is after all tech debt. Another Feast engineer will have to clean this up later. I would rather solve this properly or scope it down.

I’m not sure what sort of complexity you mean here. I think if we do have statistics for entities it’s a lot easier to maintain compatibility with TFDV fields with inheritance, which is the main reason why the class was introduced in the first place. Additional fields that differ between features and entities can be defined in their concrete classes.

I stand corrected.

Do you mean the fact that they use the same object? I guess it’s fine to separate them for the sake of forward compatibility…

Yes. Their constraints are distinct.

Do you mean have FeatureReference as a distinct entity and have feature sets, features and statistics reference that entity? I’m not sure if that’s the best idea.

Exactly how it is right now for FieldId, but it's just FeatureReference. Entity doesn't reference FeatureReference. It doesn't have to be a distinct entity, it can be an embeddedId.

FeatureReference is part of the definition of Feature and FeatureStatistics cannot form a relation directly to it. To be exact, with the current implementation, the table definition for Features looks like:

The table definition you are showing me is exactly what I want. It's a foreign key based on multiple foreign columns on the feature reference (name, feature_set, project, version). I guess it just comes down to a naming difference (FieldId -> FeatureReference).

It's very clear that our existing data model is wrong because it forces your statistics design to be split between features and entities. Statistics are ultimately about data, and the only common concepts in our data layer is the Field.

So our options are
1. Map statistics to Fields instead of Entities and Features.
This does make sense at the level of feature statistics. Features map to data through fields. Entities map to data through fields. Statistics occur on the data/field.
The problem with our current Field is that the parent child relationship of fields to features and entities doesn't work. Field as a means of sharing common Java fields through inheritance makes sense, but Fields shouldn't be the parents of Entities and Features because Entities don't share an identity with a Field. Each Field in a FeatureRow is unique, and that Field, even if its an Entity, has a different identity for each Feature Set.
One way to make this work is invert the relationship between Feature/Entity and Field to one that is consistent with FeatureRow.proto

Fields have an identity (FieldRef) and a table.
Feature set has a single collection of Fields (instead of Features and Entities). This creates a many to many mapping between Feature Set and Field
A Field can then be configured to be one of two types, Entity or a Feature.
Fields that have a Feature type don't have an external identity. They share an identity with the Field, FieldRef. There may or may not be a Feature table that references this Field table. Not sure if it's necessary.
Fields that have an Entity type reference an external Entity. Meaning an Entity has a table. These entities can occur in multiple Feature Sets. This might be out of scope for your PR though.
Statistics is successfully de-duplicated and only reference a Field

2. Replace Field with Feature
The thing with Proposal (1) is that the identity of Field will probably be FieldId/FieldRef which is 100% identical to FeatureRef. That raises the question of what differentiates these two (Field/Feature). Do we really need FieldId and FeatureRef?
If we want to treat all Fields as Features (generating statistics or feeding them into models), then we could simplify the data model by replacing Field with Feature in proposal 1. That removes the duplication between FieldId and FeatureRef.
3. Just remove Field
The final proposal is the one I gave you previously. We remove Field and keep Entities and Features separate and allow statistics only on Features. This is the smallest cut that we can make right now, since the data model doesn't dramatically change.
Ok, so there you have three proposals and my logic behind it. Please come up with a solution

The issue with (1) is that features were split to be distinct from entities because while they're currently mostly congruent to each other, that won't be the case in the future.
I'll do as you suggested in (3), but does that mean i remove the entity field schemas introduced in #438 as well?

The issue with (1) is that features were split to be distinct from entities because while they're currently mostly congruent to each other, that won't be the case in the future.

Ok, how does (1) prevent that? All of the options keep entities and features disconnected.

I'll do as you suggested in (3), but does that mean i remove the entity field schemas introduced in #438 as well?

You would need to remove entity schemas yes. I am fine with going for (3), but I would still like to hear your thoughts on what I wrote above.

Questions

Do we have or can we add a multiple day (time) statistics aggregation test?
Do we have a definitive list of statistics that we provide users?
Do we have a list of statistics that they lose when they do aggregation?
Are we testing that the results contain the above statistics?
One of the biggest pains with our current bigquery storage implementation is that failures don't bubble up to the user. Can we also test that our exceptions bubble up? Especially if there is a problem with BigQuery configuration.
Is there a test for the force refresh?
Is there a test for the user providing no dataset/time range or providing both?

Do we have or can we add a multiple day (time) statistics aggregation test?

Added to the end to end tests.

Do we have a definitive list of statistics that we provide users?
Do we have a list of statistics that they lose when they do aggregation?

All in the gitbook documentation already. See the table at the bottom of the page.

Are we testing that the results contain the above statistics?

Yes, in the end to end test.

One of the biggest pains with our current bigquery storage implementation is that failures don't bubble up to the user. Can we also test that our exceptions bubble up? Especially if there is a problem with BigQuery configuration.

The grpc method catches all exceptions, so it will be bubbled up. I've tested this personally.

Is there a test for the force refresh?

No, i've only tested this locally. I can add the unit test, but it will take time.

Is there a test for the user providing no dataset/time range or providing both?

Added.

/test test-end-to-end

/ok-to-test

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end

/test test-end-to-end

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

Would it be feasible to break this pull request up into a few somehow? At a first glance there's a lot that I think is generally beneficial independent of the feature addition of batch statistics, like entity/domain model additions and updates like Entity, feature and entity references, etc.
I have little doubt that the batch statistics feature addition in itself will necessarily be a large PR no matter how we slice it, but I see the 5,000 line diffstat here and my spirits get deflated that I will need to reserve the majority of a weekend to it sometime in the next few weeks, by which point it will be merged (which is totally fine, just that it feels like a drag to bring people back to it later if there are questions & comments).

Some products alternate technical and feature releases, starting to feel Feast 0.5 could be split on its two roadmap categories that way… speaking from the perspective of someone who will upgrade a deployment at some point (i.e. merging down a branch), the scope is getting pretty huge (and that's not including this, #554, or #533 yet). It's great work, it's just creating some anxiety for me about the effort and risks of upgrading.
Anyway, I'm off topic for this PR, I'll take this elsewhere…

@ches That's fair. I'll do what I can.

Some products alternate technical and feature releases, starting to feel Feast 0.5 could be split on its two roadmap categories that way

Yea the scope of 0.5 has increased a lot, which is partly good and bad. By splitting do you mean based on the existing master branch versus the additional functionality we are introducing with open PRs, or would you move out some functionality also merged into master?
My intuition is to put our efforts towards making 0.5 as stable and well tested as possible, so we would probably deploy it side by side and migrate folks over slowly. I would want to include all breaking changes for that matter. I think its possible to have 0.5 and 0.6 be technical and feature releases, but we probably will roll up to 0.6 quite quickly, which means we won't have much time to maintain the 0.5 branch.


[SSL: KRB5_S_TKT_NYV] unexpected eof while reading (_ssl.c:2570)

Run    bash scripts/run.sh --train       an error in your environment

I am not able to reproduce your error.
Did you follow all the instructions to create/setup the Python environment and download the data/weights?


Track path in std::io::Error errors

Describe the feature
std:io::Error doesn't track the path that lead to the error. Because of that, we have a bunch of custom IO errors across the codebase, see e.g. https://github.com/paradigmxyz/reth/pull/3324.
We need to introduce a wrapper for such fallible std::fs methods, and use it across the codebase, propagating the error.
Reference implementation from Foundry: https://github.com/foundry-rs/foundry/pull/2053
Additional context
No response

closed via #3367


Test the parameter loading and all the levels --> unit tests!

I've implemented the Unit tests need, there are in #41. Closing this for now.


Hello Team I am facing following issue

Error invoking remote method 'send-http-request': Error: write EPROTO 55633544:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:....\third_party\boringssl\src\ssl\tls_record.cc:242:

I had this issue when I had multiple env variables with the same name configured even if one was disabled. Just make a new env.

Hey @arullpm06, I'm closing this issue as stale. Please open a new issue if the bug still persists.


Test Issue created at Thu, 03 Jun 2021 11:00:03 GMT

Test issue body  Thu, 03 Jun 2021 11:00:03 GMT

Comment on issue at Thu, 03 Jun 2021 11:00:07 GMT


added gfg folder and all possible strings of a string

Related Issue
Solved issue number: #[issue number that will be closed through this PR]
issue: #302
Describe the changes you've made
A clear and concise description of what you have done to successfully close your assigned issue. Any new files? or anything you feel to let us know!
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
A clear and concise description of it.
Added java code that finds out all possible substrings of a string
Language used for coding
Mention the language you have used for coding here.
Java
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] New and existing unit tests pass locally with my changes.

All Possible Substrings of A String <- this should be your folder name. Remove "-" from folder name.


Fix balance calculation formula

[x] Showing negative token balance in transaction screen
[x] Applying ED incorrectly for local tokens

Version test: http://<IP_ADDRESS>:8900/s/mfbJzqprqtnpzBL
Validation passed with checklist of the new transferable fomulas


Where is http-multiswitch

The npm page for homebridge-http-multiswitch links here, but despite the description of the repo referring to http, this is for UDP.
Where is the http version you made, Id love to get the code for it.
Thanks!
Edit: I can see in the commit history that you changed the project to be UDP. Which commit would you suggest using for stable http-multiswitch functionality, as described in npm? https://www.npmjs.com/package/homebridge-http-multiswitch

you are right... it changed by mistake. I'll bring it back shortly

@dermotos it's done:
https://github.com/nitaybz/homebridge-udp-multiswitch


Bazel build/test on Windows

This is my attempt to address https://github.com/DataDog/dd-trace-cpp/issues/84.
Bazel can build and test this code using Visual Studio 2022 Community Edition on Windows 10.
I have yet to check whether Envoy can build this code on Windows, because I can't get Envoy to build on Windows in any case. Something about a missing header in quiche.
See the commit messages for lists of the changes. We'll want to go through the changes in person to discuss alternatives.
Finally, we'll want to add a Windows bazel build/test to CircleCI. Otherwise it'll break immediately. It looks like it's possible with CircleCI's Windows "orb," but I have yet to try it. Ideally, Visual Studio is already installed; then we can install "chocolatey," then choco install bazelisk, and then go to town in powershell. None of that is here.

I booted up my Windows machine again this morning.
bazelisk build --subcommands dd_trace_cpp printed a lot of information. For example, here's one compiler invocation:
# Configuration: 308244673dcfff942bac53deb0add1f990177841812fbc4375ad833de86fdd78
# Execution platform: @@local_config_platform//:host
SUBCOMMAND: # //:dd_trace_cpp [action 'Compiling src/datadog/tags.cpp', configuration: 308244673dcfff942bac53deb0add1f990177841812fbc4375ad833de86fdd78, execution platform: @@local_config_platform//:host, mnemonic: CppCompile]
cd /d C:/users/mathm/_bazel_mathm/gfzrazm3/execroot/_main
  SET INCLUDE=C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.38.33130\include;C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.38.33130\ATLMFC\include;C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include;C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt;C:\Program Files (x86)\Windows Kits\10\\include\10.0.22621.0\\um;C:\Program Files (x86)\Windows Kits\10\\include\10.0.22621.0\\shared;C:\Program Files (x86)\Windows Kits\10\\include\10.0.22621.0\\winrt;C:\Program Files (x86)\Windows Kits\10\\include\10.0.22621.0\\cppwinrt
    SET PATH=C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.38.33130\bin\HostX64\x64;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\VC\VCPackages;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer;C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\bin\Roslyn;C:\Program Files\Microsoft Visual Studio\2022\Community\Team Tools\Performance Tools\x64;C:\Program Files\Microsoft Visual Studio\2022\Community\Team Tools\Performance Tools;C:\Program Files\Microsoft Visual Studio\2022\Community\Team Tools\DiagnosticsHub\Collector;C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\\x64;C:\Program Files (x86)\Windows Kits\10\bin\\x64;C:\Program Files\Microsoft Visual Studio\2022\Community\\MSBuild\Current\Bin\amd64;C:\Windows\Microsoft.NET\Framework64\v4.0.30319;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\Tools\;;C:\Windows\system32;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\VC\Linux\bin\ConnectionManagerExe;C:\Program Files\Microsoft Visual Studio\2022\Community\VC\vcpkg
    SET PWD=/proc/self/cwd
    SET RUNFILES_MANIFEST_ONLY=1
    SET TEMP=C:\Users\MathM\AppData\Local\Temp
    SET TMP=C:\Users\MathM\AppData\Local\Temp
    SET VSLANG=1033
  C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.38.33130\bin\HostX64\x64\cl.exe @bazel-out/x64_windows-fastbuild/bin/_objs/dd_trace_cpp/tags.obj.params``

Looking at the last line, that's my local cl.exe given arguments (parameters) from a file bazel-out/x64_windows-fastbuild/bin/_objs/dd_trace_cpp/tags.obj.params.
Here's getting the content of the file:
PS C:\users\mathm\src\dd-trace-cpp> cat bazel-out/x64_windows-fastbuild/bin/_objs/dd_trace_cpp/tags.obj.params
/nologo
/DCOMPILER_MSVC
/DNOMINMAX
/D_WIN32_WINNT=0x0601
/D_CRT_SECURE_NO_DEPRECATE
/D_CRT_SECURE_NO_WARNINGS
/bigobj
/Zm500
/EHsc
/wd4351
/wd4291
/wd4250
/wd4996
/I.
/Ibazel-out/x64_windows-fastbuild/bin
/Iexternal/com_google_absl
/Ibazel-out/x64_windows-fastbuild/bin/external/com_google_absl
/Ibazel-out/x64_windows-fastbuild/bin/_virtual_includes/dd_trace_cpp
/D__CLANG_SUPPORT_DYN_ANNOTATION__
/showIncludes
/MD
/Od
/Z7
/wd4117
-D__DATE__=\"redacted\"
-D__TIMESTAMP__=\"redacted\"
-D__TIME__=\"redacted\"
/std:c++17
/DDD_USE_ABSEIL_FOR_ENVOY
/Fobazel-out/x64_windows-fastbuild/bin/_objs/dd_trace_cpp/tags.obj
/c
src/datadog/tags.cpp

Maybe it's those /wd...x flags. They suppress warnings. Ah, but your compiler was emitting errors, so still a mystery. That first warning (4351) is missing from Microsoft's documentation, so maybe those are more about bugged warnings than about diagnostic preferences. Just a guess.
If I run the compiler without arguments, it prints its version:
PS C:\users\mathm\src\dd-trace-cpp> C:\'Program Files'\'Microsoft Visual Studio'\2022\Community\VC\Tools\MSVC\14.38.33130\bin\HostX64\x64\cl.exe
Microsoft (R) C/C++ Optimizing Compiler Version 19.38.33133 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

usage: cl [ option... ] filename... [ /link linkoption... ]

There are no other versions installed:
PS C:\users\mathm\src\dd-trace-cpp> ls C:\'Program Files'\'Microsoft Visual Studio'\2022\Community\VC\Tools\MSVC\

    Directory: C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----          1/6/2024   1:21 PM                14.38.33130

PS C:\users\mathm\src\dd-trace-cpp>

Windows info:
Edition	Windows 10 Home
Version	22H2
Installed on	9/8/2020
OS build	19045.3803
Experience	Windows Feature Experience Pack 1000.19053.1000.0

System info:
Device name	DESKTOP-K678O5O
Processor	Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz   3.60 GHz
Installed RAM	16.0 GB
Device ID	B3AB65F5-79E3-4627-A8D7-998FF68433CB
Product ID	00325-81869-51316-AAOEM
System type	64-bit operating system, x64-based processor
Pen and touch	No pen or touch input is available for this display

Bazel info:
PS C:\users\mathm\src\dd-trace-cpp> bazelisk version
Bazelisk version: v1.19.0
Build label: 7.0.0
Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer
Build time: Mon Dec 11 16:54:12 2023<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>
PS C:\users\mathm\src\dd-trace-cpp>

Visual Studio info:

Just for the record, we already talk about it on Slack. We have a similar Windows setup. The difference is that bazel build uses abseil and {abseil string_view iterator is a const char*](https://github.com/abseil/abseil-cpp/blob/6d21df714aa6a2ab2fc4029ca71dcff2daa03ca1/absl/strings/string_view.h#L170-L173).

Et voila!
Still remaining:

Use std::getenv and _putenv on Windows, instead of {Get,Set}EnvironmentVariable.
Figure out how to convey -DDD_USE_ABSEIL_FOR_ENVOY to Envoy when Envoy builds this library with Bazel.

We could put it as part of copts in BUILD.bazel, but then I don't know how to disable it for other kinds of builds. Right now I'm using two different .bazelrc files.

Figure out how to build Envoy on Windows, so that we can test enabling the Datadog tracer in Envoy.

Soon™

Consider integrating the trace_sampler_config.cpp bug fix into main.


Lower SQL queries for interactives list page

Fixes #846

You can open the Django Debug Toolbar to see the time taken and number of SQL queries. It's gone from 137 queries to 4 queries.

You can open the Django Debug Toolbar to see the time taken and number of SQL queries. It's gone from 137 queries to 4 queries.

Confirmed uses 4 queries

And confirmed that it used to use 137 queries. Good, reapproved


1.9 API reference page 404s, doesn't redirect

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
Visiting 1.9 API reference page returns 404. Users Googling for an API reference are likely get a result for this page.
Proposed Solution:
Redirect to the API reference landing page or some other relevant page
Page to Update:
Redirects page

Hi! Can I help out with this issue?

/assign


Tab Screen Not Rendering After Updating RN Reanimated to v2.9.1

Replicated issue as  previously raised here
Current Behavior
There are two tabs and using Tabs.ScrollView to render tab-view components.
In RN Reanimated v2.2.3, the contents are displayed correctly. But after updating to v2.9.1, they are no longer rendering and following error pops up:
Warning: Cannot update a component (`Unknown`) while rendering a different component (`Unknown`). To locate the bad setState() call inside `Unknown`, follow the stack trace as described in https://reactjs.org/link/setstate-in-render
in Unknown
    in RCTView (at View.js:32)
    in View (at ScrollView.js:1674)
    in RCTScrollView (at ScrollView.js:1792)
    in ScrollView (at ScrollView.js:1818)
    in ScrollView (at createAnimatedComponent.tsx:682)
    in AnimatedComponent(ScrollView) (at createAnimatedComponent.tsx:693)
    in Unknown
    in Unknown
    in Unknown (at TabHOC/index.js:24)
    in Tab (at TabsHOC/index.js:19)
    in RCTView (at View.js:32)
    in View (at createAnimatedComponent.tsx:682)
    in AnimatedComponent(View) (at createAnimatedComponent.tsx:693)
    in Unknown (created by Lazy)
    in Lazy (created by CellRenderer)
    in RCTView (at View.js:32)
    in View (at VirtualizedList.js:2073)
    in VirtualizedListCellContextProvider (at VirtualizedList.js:2088)
    in CellRenderer (at VirtualizedList.js:814)
    in AndroidHorizontalScrollContentView (at ScrollView.js:1674)
    in AndroidHorizontalScrollView (at ScrollView.js:1792)
    in ScrollView (at ScrollView.js:1818)
    in ScrollView (at VirtualizedList.js:1268)
    in VirtualizedListContextProvider (at VirtualizedList.js:1100)
    in VirtualizedList (at FlatList.js:645)
    in FlatList (at createAnimatedComponent.tsx:682)
    in AnimatedComponent(FlatList) (at createAnimatedComponent.tsx:693)
    in Unknown
    in RCTView (at View.js:32)
    in View (at createAnimatedComponent.tsx:6
    ...

Basically, TabHOC component renders tab views dynamically in Tabs.Container. See the code below:
...
const CustomTabs = memo(props => {

    const renderTabViews = React.useCallback(() => React,Children.toArray(props.children).map((child, index) => (
        <Tabs.Tab
            key={index}
            ...
        >
                <Tabs.ScrollView>
                    {child}
                </Tabs.ScrollView>
        </Tabs.Tab>
    )), [children]);

    return (
        <Tabs.Container
            lazy
            initialTabName={props.initialTabName}
            renderHeader={props.renderHeader}
            renderTabBar={renderTabBar}
            onIndexChange={props.onIndexChange}
        >
            {renderTabViews()}
        </Tabs.Container>
    );
});

export default CustomTabs;

And here are dependencies with their versions I'm using:
    "react": "17.0.2",
    "react-native": "0.66.1",
    "react-native-collapsible-tab-view": "^4.5.2",
    "react-native-gesture-handler": "^2.5.0",
    "react-native-reanimated": "^2.9.1",
    "react-native-safe-area-context": "^4.3.1",
    "react-native-screens": "^3.15.0",

Try using version 5, it's published under the @rc version tag. The currently released version has problems with reanimated 2.9.1

@andreialecu Thank you for your response.
I installed RC version. The built was successful but got an error of unavailable dependency module react-native-pager-view in node_modules/ during app installation.
It is indeed not installed. Should I fork, pull and add it?

It's a peer dependency, you need to install it yourself. Read the README in the root of the repository.

Oh. I see. The doc got updated in June. I had it installed with old command.
Right, I install and check it then.


fix: updated deps

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Suggestion: Add a wiki to the Github project

A wiki would allow us to share useful tags.
For example, I just made a label for each teleport tablet and scroll, since some of the default ones don't indicate where they lead, (i.e. Kharyrll > Canifis)

In case this doesn't happen for a while, here's that teleport list:
APE,19631
ARCES,19613
ARD,8011
BARB,24955
BARWS,19629
BTLFRT,22949
BRIMH,11745
CAMLT,8010
CANIFIS,12779
CATH,24961
DIGST,12403
DRAY,19615
EDGE,12781
FAL,8009
FELDP,12404
FENK,19621
FISH,24959
HARM,19625
HOSID,19651
HOUSE,8013
ICE P,24963
ICE M,12780
IORW,12410
KEY,13249
KHAZ,24957
LUMB,8008
LUMYD,12642
LUNAR,12405
MIND,19617
MOON,24949
MORT,12406
MOS,12411
NARD,12402
OURA,24951
PEST,12407
PISC,12408
POLL,11743
PRIF,23771
RELK,11744
RIM,11741
SALVE,19619
SENN,12782
TAI,12409
TAVR,11742
TRAIL,25087
TROLL,11747
VARR,8007
VOLC,21541
WATCH,8012
WATER,24953
WATSON,23387
W ARD,19623
WILD19,12776
WILD23,12777
WILD31,19627
WILD33,24251
WILD40,21802
WILD45,12778
WILD47,12775
YAN,11746
ZUL,12938

Missing Kourend castle teleport (tablet) and Civitas illa fortis tablet as they are not listed in OSRSBox yet.


fix: update how window is being calculated

Background
There are two main concerns which were being found as part of the onboarding of window v3. The following is the list of the concerns and details for each.
Unexpected behavior on monthly window
There are cases where certain dates are not covered. The currently known occurrences are on March and April, with configs:
size: 1M
delay: 1d
truncate_to: M

Given an event time 2024 March 25 4:52 UTC the result will be:
start_time: 2024-01-29T00:00:00Z
end_time: 2024-02-29T00:00:00Z

And if the event time is 2024 April 25 4:52 UTC the result will be:
start_time: 2024-03-02T00:00:00Z
end_time: 2024-03-31T00:00:00Z

As can be checked, 2024-03-01 is not in any of the above.
Possible multi-meaning delay for wider user
The usage of delay in window v3 can introduce confusion to the wider user. While delay in this context is about the shifting of window, some can interpret it as a delay in processing.
PR Changes
This PR is to address the above concerns. For the first one, the mechanism of calculating the window is updated. And for the second, replacement of delay to be shift_by.

This PR requires this other PR to be merged first.


Unable to Remove a Study with Variants in the "Studies" View

Behavior seen :
When we want to delete a study whom have variants directly on the view  "studies" (listing page of all studies) we don't have the proposition to delete also children's variants. So we get an 403 error.

We can only delete the study by exploring it and chose delete on the right top menu. And here we have the proposition to delete also children.
Expected Outcome:
The user should have the ability to delete a study with variants directly from the "Studies" view, with a prompt to also delete its child variants, as is available in the Exploration view.

Il faudrait déplacer la boîte de dialogue


Remove "R API is in beta" message from docsite

This should be done in the same github release that has the R API 1.0.0 release

Completed


Modgeons just crashes on launch, without an error, if a mod has an invalid polymod_meta.json file

Fixed! Now it shows a popup if the _polymod_metadata.json file isn't a valid JSON file. Thanks!


Fix compatibility with PHP 7.4 by removing curly brace usage

Curly brace syntax for accessing array elements and string offsets has been deprecated in PHP 7.4

Thanks for this fix, @danez .  I'm going to release a new 3.x version with this fix today.

Thanks


Add setting to hide the use of LBC

Is your feature request related to a problem? Please describe.
Some people don't want to deal with LBC at all. They think it's a distraction, and may be off-putting to absolute beginners to the platform. For example, https://odysee.com/@FraserValleyRoseFarm:e/OdyseeAdvice:6
Describe the solution you'd like
One suggestion is to hide everything about LBC manipulation. To publish a video obviously the user needs to have at least a small amount of LBC in the wallet. So to start publishing, he or she needs to make a one-time payment of $5 to fund the wallet. At the current price of 0.03 USD/LBC, this would be around 166 LBC, which is enough to publish hundreds of videos.
This amount of LBC will remain hidden, and won't be shown to the user. At the same time, the user won't be able to tip or support with LBC, only cash.
In this situation, Odysee will completely manage the wallet of the user. If the user publishes something (or creates a repost or playlist) Odysee will use a default and small bid value (0.01 LBC) to make sure the initial funding amount is sufficient to publish thousands of videos without running out of LBC.
A checkbox in the settings will activate the advanced mode, giving the user full control of the wallet, as it is today.
Additional context
Some things need to be thought out with this system, because if the user decides to use the basic mode with no LBC interaction, how would the user handle things like tips made to his or her wallet? Are those funds simply locked there? It could be a significant amount. Does this option imply that they no longer are eligible to receive tips and view rewards in LBC?
How would they handle synchronized videos from Youtube? Creators could fund their wallets depending on the number of videos that they have, say $5 for up to 100 videos, $10 for up to 1000 videos, $15 for up to 2500 videos, etc.
Also, since the videos would be published with a fixed and small bid (0.01 LBC), the videos would not be able to trend in the algorithm, as they would be displaced by videos that have a manual bid amount larger than the minimum.

We don't plan to do something like this anytime soon.


Missing symbols in visibleSymbols() inside LetExpression

Description:
$Title
Steps to reproduce:
When we try to get completions at the cursor in following code snippets, we variables x2, and x3 are not tracked in visibleSymbols()
function test1(float x) returns float =>
    let float x2 = x+x, float x3 = x*x in <cursor>;

function test2(float x) returns float {
    return let float x2 = x*x in <cursor>;
}

Affected Versions:
SL beta4

Duplication #33236


Console breaks when requesting to select all scopes when authorizing an API

Describe the issue:
When authorizing an API if you click on "select all" quickly then the console breaks.
https://github.com/wso2/product-is/assets/11583571/37c36887-2b44-4188-ba8c-c706dc05d7ea
The following log was printed in the browser console;
vendor.e8765700.js?7df61e6030514e56:205 TypeError: Cannot read properties of undefined (reading 'length')
    at x (vendor.e8765700.js?7df61e6030514e56:2:782783)
    at vendor.e8765700.js?7df61e6030514e56:2:792745
    at ko (vendor.e8765700.js?7df61e6030514e56:205:5080994)
    at bc (vendor.e8765700.js?7df61e6030514e56:205:5091053)
    at ks (vendor.e8765700.js?7df61e6030514e56:205:5139896)
    at gl (vendor.e8765700.js?7df61e6030514e56:205:5127001)
    at pl (vendor.e8765700.js?7df61e6030514e56:205:5126929)
    at ml (vendor.e8765700.js?7df61e6030514e56:205:5126792)
    at al (vendor.e8765700.js?7df61e6030514e56:205:5123933)
    at Pr (vendor.e8765700.js?7df61e6030514e56:205:5064835)

How to reproduce:
In an application try to perform adding authorized scopes to an API. After selecting the API need to quickly click on select all. It was seen that this issue is reproduced when I clicked on "select all" before the api would respond with the available scopes for the API. Note that I tried this out in a hosted setup where there is a normal delay in getting api responses unlike a local setup.
Expected behavior:

Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: IS7-beta-6-snapshot (hosted setup)

Optional Fields
Related issues:

Suggested labels:

Verified in the latest build.
https://github.com/wso2/product-is/assets/41533942/af26ea8c-5c03-4250-a104-6eaf927ca87b


blob lease client

move constexpr int32_t InfiniteLeaseDuration to blob lease client

move std::string CreateUniqueLeaseId(); to blob lease client


Add shape_idx to CollisionObject2D mouse_entered signal

See proposal for discussion

Great job, thank you!

Feel free to open a 3.x pull request if it can be done in a backwards-compatible way :slightly_smiling_face:

I don't think I'll be up for it -- looking forward for a transition to a stable 4.0 :)


Investigate whether the DDO can be used to capture user information

hahnrob created the following on Sep 24:
User Story

As a [user role below]:
IBM.com Developer

I need to:
understand whether the digitalData object is a reliable source for user information

so that I can:
utilize the data when developing the Locale Selector application

Additional information

Initial DDO documentation: https://ibm.ent.box.com/notes/527242249585
Should consider multiple methods for fetching various data from the data object (e.g. user's language)

Acceptance criteria

[ ] Service class available in the @carbon/ibmdotcom-services package
[ ] User information must be available for all DGC adopter pages
[ ] Generated JSDoc in living documentation
[ ] Minimum 80% unit test coverage

Original issue: https://github.ibm.com/webstandards/digital-design/issues/1756

On Oct 02, Jeff-Chew commented:
We have decided to use the existing logic in Northstar to fetch the location/language information for the user.


Samsung is NOT worst

Hey,
I have a big problem. I am linking to dontkillmyapp.com from my Android app.
My app has over 5 million downloads, so I have some experience.
I have noticed that actually Samsung devices work best, they have the least problems and I also recommend them whenever someone asks. I am also using a Samsung Galaxy S22 Ultra myself. I have never experienced any issues. All apps keep running.
But you have listed Samsung as worst.
I can confirm that I get the most mails from users using Xiaomi and Huawei complaining that the app stops working in the background. In that regard your library is right.
But Samsung needs to be moved down from the top.
Users thinking that they have a better device than getting Samsung, but it's not true..
Thank you,
Tim K.

Hello Tim, big thanks for your feedback on this. I agree that Samsung is not the worst in terms of non-standard killing practices, but because of its market share it is definitely one of the biggest headaches for devs IMHO. It seems everything works as expected unless users let the system move your app to the list of sleeping apps when background processing basically stops for the app. Maybe you as an experienced user can see when this is happening, can properly decipher the notification which precedes this but most users out there won't. For instance for me as an alarm clock app maintainer this is major problem. When users do not use the app fro few days their alarm won't trigger at the next day and users have abosolutely no idea why. This "extension" to the AOSP adaptive battery mechanism is IMHO really harmful. Maybe you could comment on this mechanism as I'm not familiar with all details on how is this implemented with latest Samsung versions, but we are still seeing this feedback. On the other hand I agree that Xiaomi, Huawei and 1+ are more problematic, but luckily with a much smaller market share which makes them less of a problem for devs..

Hello Tim, big thanks for your feedback on this. I agree that Samsung is
not the worst in terms of non-standard killing practices, but because of
its market share it is definitely one of the biggest headaches for devs
IMHO. It seems everything works as expected unless users let the system
move your app to the list of sleeping apps when background processing
basically stops for the app. Maybe you as an experienced user can see when
this is happening, can properly decipher the notification which precedes
this but most users out there won't. For instance for me as an alarm clock
app maintainer this is major problem. When users do not use the app fro few
days their alarm won't trigger at the next day and users have abosolutely
no idea why. This "extension" to the AOSP adaptive battery mechanism is
IMHO really harmful. Maybe you could comment on this mechanism as I'm not
familiar with all details on how is this implemented with latest Samsung
versions, but we are still seeing this feedback. On the other hand I agree
that Xiaomi, Huawei and 1+ are more problematic, but luckily with a much
smaller market share which makes them less of a problem for devs..
Thank you.
Best regards,
Petr

P.S. Sorry for my brevity or longer response time. I'm handling hundreds of
emails daily and I try hard to respond to most of them in the best way I
can. Just let me know if you need more details, please.
On Mon, Jan 15, 2024 at 12:25 PM T1mmyK0 @.***> wrote:

Hey,
I have a big problem. I am linking to dontkillmyapp.com from my Android
app.
My app has over 5 million downloads, so I have some experience.
I have noticed that actually Samsung devices work best, they have the
least problems and I also recommend them whenever someone asks. I am also
using a Samsung Galaxy S22 Ultra myself. I have never experienced any
issues. All apps keep running.
But you have listed Samsung as worst.
I can confirm that I get the most mails from users using Xiaomi and Huawei
complaining that the app stops working in the background. In that regard
your library is right.
But Samsung needs to be moved down from the top.
Users thinking that they have a better device than getting Samsung, but
it's not true..
Thank you,
Tim K.
—
Reply to this email directly, view it on GitHub
https://github.com/urbandroid-team/dont-kill-my-app/issues/804, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIPQZ4S42EQKQZW642UKFDYOUG33AVCNFSM6AAAAABB3DS436VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA4DCOBTGI3DGNY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hello Tim, on our support, Samsung still takes twice as many reports as the other vendors (the last year). This might be because they have a bigger market share, but I cannot agree with "Samsung is the best" in terms of background restrictions.
The restrictions are there and enabled by default. On most phones, they are hidden all over the place and users have trouble finding them in the layout.
Moving Samsung from the first position is fair, but we are still too far from marking Samsung as the best vendor for background management.

Yes, Samsung has this sleep mode for apps not being used for a while. But I think this is less of a problem. Because you need to not open an app for multiple months for it to get stopped. And once you wonder why it isn't working anymore, you will open it manually and it will work again. Also, app developers can easily warn users. On Samsung devices changing this setting manually definitely works.
On Xiaomi and Huawei devices, users need to change multiple settings and they regularly tell me that changing these settings doesn't really do anything.
Also, on these devices an app will stop working from the first day on. Users will always think it's the apps fault. If it gets stopped after a few months of not being used, most users will notice that it's not the app, but their device settings.
Same with messenger apps which you open regularly anyways. I have a friend using Huawei. She doesn't get Signal notification. We contact her, but she doesn't even notice. On Samsung you basically never experience issues with a messenger.
Where are your website visitors from?
I think it depends heavily on the countries. In Europe most will probably use Samsung.
But I have a lot of users from poorer countries like Brazil, Mexico, Indonesia and India. They are using Xiaomi and Huawei a lot which is a huge problem.
I think Xiaomi comes right after Samsung in terms of market share in those countries.

If you have alarms, calendars, or other time-sensitive events, you cannot rely on remembering to open the app actively every 3 days so the system won't suspend it in the background.
If there is a need to warn users, that the system may kill the app sometime in the future without warning, then the phone deserves a bad rating. The users should not be forced to dig deep into the settings to make sure the system won't decide to kill their apps.
Why does not the system warn the users "This app does not seem to be used, do you want to suspend it?"...
Samsung also reverts the settings, that were already toggled by the users - this has been reported many times.
If the app stops working, the users will ALWAYS blame the app. Half of the issues we are dealing with start with "after using the app for x years, it suddenly stopped working" (typically a 1* review).
I moved Samsung to the 4th position, but until Samsung stops putting so many restrictions under different names and in different places in the settings, we don't want to give it a better rating.

Hello Tim, not sure if this period is a months on S22, but definitely on some Samsung devices this period is as short as 3 days.. So imagine an alarm clock app not being used on the weekend and one additional day and whoops you won't get woken up next day. From our personal experience at least half of app killing issues reported on our support are from Samsung. If you want some more exact measures, we have results from our benchmarking app DontKillMyApp and half of scores under 10% are from Samsung devices. I do not expect users would leave the benchmark up for 1 month before they run the bechmark. Anyway, me are changing the order of the top app killers slightly we this is what we have felt for a longer tiem as well that the current order is not completely right.. For various reasons it is tiem for Xiaomi to get 5/5 as in recent updates they are even killing accessibility servces! And Samsung maybe really does not deserve to be at spot one, even from our data it seems it causes most trouble to devs..

Thank you, that's totally fine. Samsung still has issues. I get a little annoyed by the unused app stopping as well. But definitely Xiaomi and Huawei needs to be ranked worse. I can explain this further if you like.
 This is bad for any app that needs to do something for the user. And then users also tell me the app stops after midnight. Biggest problem is that Xiaomi and Huawei don't even start the app correctly in the wakeup phase again. Samsung does that.
Let me also explain what app I have. Its an auto reply app which replies to notifications. So it uses the notification listener service. My app technically cannot start its service. It can only let it start by the system. It's directly connected to the notification access permission. So users open the setting and see that my app is enabled there. But the service isn't running in the background. Even with my app open in the foreground. Xiaomi and Huawei just don't start it again after stopping it. Users need to revoke the permission and grant it again to make it work. And with their bad Autostart setting not even a device restart helps. Their software is so bad that they cannot even differ between normal app services and services that are connected to triggers like notifications. My app service actually isn't running permanently. It only needs to run for a very short time after a notification is received. The same problem with accessibility services as you already told. Killing such services just doesn't make any sense at all :/


[FEATURE] Stitching after making prediction

Dear all,
I wanted to make a prediction on the 3D stack, and I found that the stitching method works better than do_3D. However, I would like to use a different diameter for different 2D slices. Is there any option to perform that?
A workaround could be to predict 2D images one by one with specified diameter and then stitch them. How can I do it using Cellpose?
At the top of the 3D stack, where the fluorescent intensity is dimmer, fewer pixels are expected to be detected as a mask.

I re-trained the "cyto3" model using GUI, but it seems to me that the model doesn't take the intensity values into consideration. I guess that it's because of normalization. To make a prediction, I have tried:
masks_stitched, flows_stitched, styles_stitched = model.eval(imgs[0],
                                                        diameter=150, channels=[0,0], do_3D=False, stitch_threshold=0.5,
                                                            normalize={"normalize": True, "norm3D": True} )

normalize=False gave a poor results.
I found that reducing the diameter could solve my problem.
Thank you so much for your time. I would greatly appreciate any feedback on improving the model.
Best regards.
Vien Che

you can normalize first and then loop:
from cellpose import transforms, utils

# normalize in 3d
imgs_norm = transforms.normalize99(imgs, downsample=True)

for i in range(len(imgs)):
    masks[i] = model.eval(imgs[i], diameter=diameter[i],...)

masks_stitched = utils.stitch3D(masks, stitch_threshold=0.5)

training in the GUI, as you've inferred, always normalizes each slice. alternatively you can train in the API and normalize all the slices together, and then turn off normalization in train.train_seg


Log spam  Unregistered ConfiguredFeature

This is just one. The log spam is almost non-stop.
https://hastebin.com/huyahuteno.makefile

This has been fixed as of Version 1.3.


chore: add types to package.json

Codecov Report

Merging #1904 (4c7e7c5) into main (7a7750b) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main    #1904   +/-   ##
=======================================
  Coverage   87.12%   87.12%
=======================================
  Files          83       83
  Lines        9052     9052
  Branches      537      537
=======================================
  Hits         7887     7887
  Misses       1165     1165