Wireframe

@shaomeng, @sgpearse , I've created a new renderer to display a variable's mesh as a wireframe. I did this mainly because I needed it to debug the 3D grid classes that I'm working on, but also because it's a useful feature. Per our discussion please help test this PR before I merge it. Thanks!

Is the resolution correct?
In the following screenshot, the Refinement level menu shows "22x20x4", but the wireframes have only 3 planes.

The color mapping isn't responding to user changes.
In the following screenshot, the color map has only 2 colors, while the frames have a good transition between 2 different colors.

Can we somehow pin this commit to the wiki to have as a reference for adding renderers?

There are compiler warnings observed:
Platform: cisl-vapor.
/home/shaomeng/Git/VAPOR-git-src/lib/render/Renderer.cpp:591:34: warning: ‘Tuy’ may be used uninitialized in this function [-Wmaybe-uninitialized]
Tuy -= _textObject->getHeight();
^
/home/shaomeng/Git/VAPOR-git-src/lib/render/Renderer.cpp:592:35: warning: ‘Tlx’ may be used uninitialized in this function [-Wmaybe-uninitialized]
double coords[] = {Tlx, Tuy, 0.f};
/home/shaomeng/Git/VAPOR-git-src/lib/wasp/Compressor.cpp:824:13: warning: ‘L’ may be used uninitialized in this function [-Wmaybe-uninitialized]
delete [] L;
^
/home/shaomeng/Git/VAPOR-git-src/apps/tiff2geotiff/tiff2geotiff.cpp:259:38: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result]
fscanf( tfw, "%lf", pixsize + 0 );
^
/home/shaomeng/Git/VAPOR-git-src/apps/tiff2geotiff/tiff2geotiff.cpp:260:33: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result]
fscanf( tfw, "%lf", &y_rot );
^
/home/shaomeng/Git/VAPOR-git-src/apps/tiff2geotiff/tiff2geotiff.cpp:261:33: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result]
fscanf( tfw, "%lf", &x_rot );
^
/home/shaomeng/Git/VAPOR-git-src/apps/tiff2geotiff/tiff2geotiff.cpp:262:38: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result]
fscanf( tfw, "%lf", pixsize + 1 );
^
/home/shaomeng/Git/VAPOR-git-src/apps/tiff2geotiff/tiff2geotiff.cpp:263:32: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result]
fscanf( tfw, "%lf", &xoff );
^
/home/shaomeng/Git/VAPOR-git-src/apps/tiff2geotiff/tiff2geotiff.cpp:264:32: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result]
fscanf( tfw, "%lf", &yoff );
^

@clyne The earlier reported issues seem still there. Also, I've observed a few compiler warnings that we should address. Not sure if these warnings are introduced by this particular PR or not...

These warnings were not created by this branch. They’ve always been there.
jc

On Jun 19, 2018, at 10:54 AM, Samuel Li<EMAIL_ADDRESS>wrote:
There are compiler warnings observed:
Platform: cisl-vapor.
/home/shaomeng/Git/VAPOR-git-src/lib/render/Renderer.cpp:591:34: warning: ‘Tuy’ may be used uninitialized in this function [-Wmaybe-uninitialized]
Tuy -= _textObject->getHeight();
^
/home/shaomeng/Git/VAPOR-git-src/lib/render/Renderer.cpp:592:35: warning: ‘Tlx’ may be used uninitialized in this function [-Wmaybe-uninitialized]
double coords[] = {Tlx, Tuy, 0.f};
/home/shaomeng/Git/VAPOR-git-src/lib/wasp/Compressor.cpp:824:13: warning: ‘L’ may be used uninitialized in this function [-Wmaybe-uninitialized]
delete [] L;
^
/home/shaomeng/Git/VAPOR-git-src/apps/tiff2geotiff/tiff2geotiff.cpp:259:38: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result]
fscanf( tfw, "%lf", pixsize + 0 );
^
/home/shaomeng/Git/VAPOR-git-src/apps/tiff2geotiff/tiff2geotiff.cpp:260:33: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result]
fscanf( tfw, "%lf", &y_rot );
^
/home/shaomeng/Git/VAPOR-git-src/apps/tiff2geotiff/tiff2geotiff.cpp:261:33: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result]
fscanf( tfw, "%lf", &x_rot );
^
/home/shaomeng/Git/VAPOR-git-src/apps/tiff2geotiff/tiff2geotiff.cpp:262:38: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result]
fscanf( tfw, "%lf", pixsize + 1 );
^
/home/shaomeng/Git/VAPOR-git-src/apps/tiff2geotiff/tiff2geotiff.cpp:263:32: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result]
fscanf( tfw, "%lf", &xoff );
^
/home/shaomeng/Git/VAPOR-git-src/apps/tiff2geotiff/tiff2geotiff.cpp:264:32: warning: ignoring return value of ‘int fscanf(FILE*, const char*, ...)’, declared with attribute warn_unused_result [-Wunused-result]
fscanf( tfw, "%lf", &yoff );
^
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

John Clyne
National Center for Atmospheric Research
303.497.1236 (w),<PHONE_NUMBER> (c)
<EMAIL_ADDRESS>

My bad. I forgot to push to the remote. Should be there now.
jc

On Jun 19, 2018, at 10:57 AM, Samuel Li<EMAIL_ADDRESS>wrote:
@clyne The earlier reported issues seem still there. Also, I've observed a few compiler warnings that we should address. Not sure if these warnings are introduced by this particular PR or not...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

John Clyne
National Center for Atmospheric Research
303.497.1236 (w),<PHONE_NUMBER> (c)
<EMAIL_ADDRESS>

Question 1 and Bug 1 are resolved now.
We need to come up with a consensus on when compiler warnings are to be addressed. I'd advocate at the time before merging to master, e.g., now.

On Jun 19, 2018, at 11:39 AM, Samuel Li<EMAIL_ADDRESS>wrote:
• Question 1 and Bug 1 are resolved now.

Good deal.

• We need to come up with a consensus on when compiler warnings are to be addressed. I'd advocate at the time before merging to master, e.g., now.

I agree in the case that the compiler warnings were introduced in the PR, but in this case they were extant. Moreover, they’re not even in files modified by the PR.
jc

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

John Clyne
National Center for Atmospheric Research
303.497.1236 (w),<PHONE_NUMBER> (c)
<EMAIL_ADDRESS>


DO NOT USE THE BOT THESE DAYS! HIGHLY POSSIBLE TO BE BANNED!!!!!!!!!!

For those that have been banned, it seems many others (that aren't hacking) are being banned too, all within the last 10 hours.
Examples:

https://steamcommunity.com/app/578080/discussions/1/1697169163399711488/
https://fragbite.com/pubg/news/42261/professional-pubg-player-jeemzz-banned--updated
https://steamcommunity.com/app/578080/discussions/1/1697169163399472164/
https://steamcommunity.com/app/578080/discussions/1/1697169163398932733/
http://steamcommunity.com/app/578080/discussions/1/1697169163400255784/
https://steamcommunity.com/app/578080/discussions/1/1698294337772770745/?ctp=1

Response to a pro player getting banned: "There is a big misunderstanding here. The account was not banned because of player reports. It was falsely banned by one of our new measures which we will fix soon."
PUBG Added on a Tweet: "If you feel you were incorrectly banned please submit an appeal on our support website -https://support.playbattlegrounds.com/ "
If we all send appeals, hopefully they will realize that they banned the innocent.

The detection algorithm mainly targets the advertising bot accounts - whose ID contains contact to the aimbot sellers, broadcasting audio CMs in the public channel in the game lobby and quit on plane.
The feature targeted might be staying in one game for too short or being online for too long.
To distinguish from them, try showing some proof of recent game activities (screenshots, screencasts or online database logs).

To follow, I found out that the banned accounts have a same pattern: they quited on the plane for too many matches. This is why the other account I used for bp farming was not banned.

已经被BAN，暂时别用了

Response from PUBG Support
It seems very automated and looks like no real investigation really took place :(
Hello Survivor,
Thank you for writing to PUBG Support.
It looks like you are seeing a restriction error message on the account.
We understand that this may be a very frustrating experience.However, please understand that a restriction is placed because we have determined that there was a violation of our terms and services.
Please note that even without having any programs specifically for “hacking/cheating” there are other programs or actions that can violate our Rules of Conduct and cause a permanent restriction.

Software that bypasses the services in the game
Programs that alter the game in any way (even if it is not for cheating)
Cheats, macros, etc. for other games and not for PUBG is still a violation of the game’s services

Having purchases, low KPD, short gameplay time, etc. does not exclude any accounts from restrictions.
We can assure you that the account was blocked because there was a violation discovered on the account. We apologize but we cannot provide any specifics on the details of the violation.
We have also implemented a 24 hour investigation period to ensure that there are no false bans. Therefore, we do not accept any requests for rechecking account restrictions. However, we also constantly check our systems for false bans and if found, we correct any issues internally.
We ask for your understanding of this situation.We will continue our work to make sure that no erroneous restrictions are made and continue creating a fair gaming environment for all BATTLEGROUNDS players.
Please let us know if you have any other feedback, questions or comments. I'll be happy to assist you in any way I can.

... and if you reply to this autoreply it will auto warn you possibilities of a forever ban if you keep replying

yup. Its not like 100 year ban and perma ban makes much difference anyway

Well, as i understood you will not be unbanned? Or are doing some research to prove you innocent?

I got only this from battleye.com(

I followed up with an email stating i wanted them to do a better investigation but then they responded saying pretty much the same stuff, overall expressing their anticheat is flawless. I will never be unbanned and forever have a ban on my clean steam account :( steamcommunity.com/Id/sillysam)

@Falubii I see you have contacted battle eye directly, please let us know how that goes as I contacted PUBG support.

I have been unbanned. I don't know why but i think its because my friend sent them an email for me too.

Lol, how did you do that??!?!?!

I was unbanned too, sry for Russian, it was said that i was unbanned

It's actually quite funny. I was telling my friend about the ban after I showed you guys my chat with the support. My friend supported me and decided to express his feelings to PUBG support too. He talked about how "Sam (me) got a lucky shot just before he got banned" (even though there is no lucky shot) and then bam!

@Falubii wanna play :D

Do you guys have any idea why are we unbanned ?

@didonik You too? well i think it was mistake, they could upgrade anti cheat and he failed and banned everyone for our bot actions

So is it safe to use the bot now as you got unbanned?

@Falubii I don't really think it was a mistake. @wavyjetski  Idk.

That's intresting.  and they might update their terms and services(I don't know how does that work)

https://www.reddit.com/r/PUBATTLEGROUNDS/comments/8bet6k/80bots_in_eu_fpp_games_jumping_and_proneing/
They will be targeting this.

80 bot in 1 game is just too much. Probably because of that they will target all the afk bots.

Just a question. When everyone was using the 0328 version, did you guys use a lot of the derank option or just mainly farming? Because I used a lot of the derank before I got banned.

I was using for farming.

We should have suggested you to jump off the plane, and quit until landed. Didn't know the ban would come though.


chore: lint commit retrigger

this commit is intended to retrigger the lint-commit workflow if anything in the PR changes: title, body, reopen, etc.
Right now it only runs when the PR is opened and needs to be manually retriggered after the PR title changes.

AAAND it's working! yay

🚀

I have a struggle understanding why it still fails, but it does retrigger.

Yeah it expects the format of the commit to be something like the below, I don't plan on it being a blocker for merging but could be fun to have pretty commits:
feat: something something
fix: something something
chore: something something

Oh and it also looks at previous commits, saw that your last one was correct

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Need to press F5/F6 twice on 3.0.3

I sometimes need to press F5 or F6 twice to run the project or scene with 3.0.3.

OS?...

I've experienced the same issue with 3.1.dev.
couldn't figure out reproduce steps yet.

I'm on Ubuntu 18.04.

What happens the first time you press the button? (i.e. nothing, debugger disconnected message, something else?)

Nothing, the output tab remains empty if I've cleared it.

well, this is a fun one... ;)

I have the same issue on Linux Mint 18.3. Not sure if this is related but F5 causes a window or desktop refresh (even though it's not listed in Mint's desktop shortcuts as far as I can see). Perhaps the first press of F5 is intercepted by the OS and refreshing the window? Pure guesswork.

I can reproduce it too on Mageia 6 x86_64 (Linux) with 3.0.4-stable. I'll see if I can bisect.

Can't reproduce it with a debug build (scons p=x11 -j2) of the 3.0.3-stable tag, now testing release_debug.
Tested so far:

3.0.2-stable official build (GCC 7, LTO, release_debug): No bug
3.0.3-stable official build (GCC 8(?), LTO, release_debug): Bug (different buildsystem than 3.0.2 and earlier)
3.0.4-stable official build (GCC 8(?), LTO, release_debug): Bug
3.0.3-stable custom build (GCC 5, no LTO, debug): No bug

I could reproduce it with a custom build of 3.0.3-stable with target=release_debug, so the problem comes from that option.

The regression is caused by 28ab60422d648d43d219186ea0ecffce1645188f in the master branch (7563c17113790fe66a816c781001791bd571ef3c in the 3.0 branch). CC @robfram

Still reproducible on my machine:
Godot versions:  godot 3.1 ebd14a7 and all 3.x versions target=release_debug
OS: Xubuntu 16.04.5 LTS 4.4.0-135-lowlatency
PC: Core i5-750, Nvidia GTX 750 Ti proprietary drivers 390.77
Not reproduced on second machine:
OS: Xubuntu 16.04.5 LTS 4.4.0-135-generic
PC: Pentium 4 (old), Nvidia GTX 260 latest proprietary drivers

With target=debug work as expected.


Update samples after breaking changes

Some examples in README and .code-samples.meilisearch.yaml are invalid after the latest breaking changes

I'm updating them! :)

Fixed by https://github.com/meilisearch/meilisearch-dart/pull/322


ci: update semantic lint workflow to use npx script

Proposed behaviour

Replaces action used in workflow that lints commit messages with call to run the npx commitlint script from dependencies
Bumps dependency:   "@commitlint/config-conventional": "^13.1.0",
Current behaviour

Uses external action to lint commits
Checklist

[ ] Release notes (Conventional Commits)
[ ] Unit tests
[ ] Readme updated

Additional context

Testing instructions

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


bugfix/BaseDeltaState_python_wrapper

Description
This PR corrects the bug in the python wrapper for the BaseDeltaStates, i.e. the delta_var.setter was incorrectly set to delta_mu.setter
Changes Made

pytagi/nn/data_struct.py

Note for Reviewers
I needed to use the setter for BaseDeltaStates in canari so I found this bug

@lhnguyen102 I have a question, I used cuda by setting net.to_device("cuda") so I assume that net.input_delta_z_buffer is located in GPU's memory. Then I want to modify net.input_delta_z_buffer in python before using net.backward(). I use the setter net.input_delta_z_buffer.delta_mu = new_value to modify the value. My question is that will the new value for net.input_delta_z_buffer.delta_mu be updated automatically on GPU or do I need to do any extra step? Thanks

@van-dai-vuong Thanks for spotting the bug. Regarding your question, I've tried it before. If it does not work, a better and safe way to do so is to implement a setter for those values in Sequential.cpp e.g., set_delta_mu_var(const std::vector<float> &mu, const std::vector<float> &var)  and bind this function to python. We've done something similar for autoencoder here

@lhnguyen102 thanks. I tested it does not work. So I will implement a setter in sequential.cpp as you instructed in the incoming PR.


Using a custom seccomp profile with docker run

Output of docker version:
Docker version 1.12.0, build 8eab29e

Output of docker info:
Containers: 6
 Running: 1
 Paused: 0
 Stopped: 5
Images: 21
Server Version: 1.12.0
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 66
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor
Kernel Version: 3.16.0-38-generic
Operating System: Ubuntu 14.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.457 GiB
Name: eonSpider
ID: 6LEI:EF5I:CR2Q:BGHC:CRSV:NXLQ:NDGE:3RGH:OY7N:EML3:FYO5:FLSM
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Username: eon01
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
localhost
Steps to reproduce the issue:
I would like to test using a custom seccomp profile
docker run --rm -it --security-opt seccomp=default.json hello-world

The default.json file is the same here: https://github.com/docker/docker/blob/master/profiles/seccomp/default.json
Describe the results you received:
docker run --rm -it --security-opt seccomp=default.json hello-world

docker: Error response from daemon: linux seccomp: seccomp profiles are not supported on this daemon, you cannot specify a custom seccomp profile.

Seccomp is not currently supported on Ubuntu 14.04, because the shipped libseccomp library is too old, sorry.

There is another issue here https://github.com/docker/docker/issues/22870 - I am going to close this one as it is outside our control. I want to do something about it if possible, but it is quite difficult unless the fixes are backported by Ubuntu.


Issuing credits to Mick

Issue 1000 credits to @mickm3n.

 Follow up
On Wednesday, 28-Feb-24 17:52:21 UTC by Gov4Git dev
Issued 1000 credits to member @mickm3n.


Get-DbaRegisteredServer, fixes #3529

Type of Change

[x] Bug fix (non-breaking change, fixes #3529)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[x] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[x] Adding code coverage to existing functionality
[x] Pester test is included
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Fix the bug. A sidecase in how the logic works never considered passing an -ExcludeGroup without an -IncludeGroup, and root servers were left out. Slapped in a regr test to make it never happen again

thanks to you both!


Base layer selection

Implement an option to switch between some predefined base layers.

@smit1678 Could you you provide me with a list of base layers?
For each one, a name and the url is needed.

I think the first three would be:

OpenStreetMap (current Mapbox layer)
OpenStreetMap Standard
Mapbox Satellite

Do we want to include:

Bing?
Humanitarian Data Model?

For future would be the OAM layer (not developed yet of course).

@smit1678 Can I get tile urls for those?

OSM Standard: http://a.tile.openstreetmap.org/{z}/{x}/{y}.png, usage policy here
Mapbox Satellite: https://api.mapbox.com/styles/v1/hot/civicyccw00bv2io77zqq401h/tiles/256/{z}/{x}/{y}?access_token=pk.eyJ1IjoiaG90IiwiYSI6ImNpdmlkM2lkMDAwYTAydXBnNXFkd2EwemsifQ.KPrUb_mKlPmHCR6LNrSihQ

done via https://github.com/hotosm/oam-browser/pull/176


Update project documentation and website

The project documentation and website at http://rdf4j.org/ will need to be updated to reflect the changes from Sesame to RDF4J. In particular, we'll need:

[ ] remove logo
[ ] rename "(OpenRDF) Sesame" to "(Eclipse) RDF4J"
[ ] remove obsolete copyright notices
[ ] update documentation to use new package names, project names, etc.

Instead of updating the current site, we will migrate to a new (Wordpress-based) site. I am currently prepping this.

New WP site is up and running at http://new.rdf4j.org/ , but not yet publicly visible. If you want to help out authoring the content and migrating stuff from the old site, ping me and I'll provide you with a login.

Site is mostly done. We'll keep the old site in the air on a different subdomain so we can link back to old Sesame documentation if needed. As soon as the subdomain config has been set up I'll activate the new site.

@aschwarte10 @damyan-ognyanov @ansell , everyone else, can I get some eyeballs and feedback on the new website please? I've made the site publicly visible at http://new.rdf4j.org/ . Keen to hear any feedback you have, including mistakes, missing info, or anything else.
As soon as I have an OK I'll reconfigure the DNS and we can go live.

I couldn't see any glaring mistakes on reading through it.
It may be useful to add a Maven POM and a Gradle dependency example to the download page which references the latest version, so it is a simple copy-paste to add the full RDF4J library to either Maven/Gradle as necessary, for those that do not want to pick and choose between the modules that they are sure they need.
Once a release happens, pointing to search.maven.org on the downloads page may be preferable to the Sonatype repository.
It may also be useful to delay the website until RDF4J-2.0-M1 is actually released, as not everyone will be aware of how to access the snapshots. Could add the details of how to get access to the sonatype snapshots repository on the download page if you want to advertise that as a method of people getting access to nightly builds, even if only until M1 is released.

Good idea on the POM, I'll take a look at that. Of course, I do plan to point to Maven Central once release is done (the link to sonatype is purely for snapshot builds).
As for waiting until 2.0-M1 is out: I'm trying to push things forward here, and make it clear in everybody's mind that Sesame is a closed chapter, and we're committed to RDF4J now. But perhaps you are right and we should do the M1 release at the same time as launching the new site. We're about ready to do the release anyway, so it will only be a few days one way or the other.

We are waiting for a slight reconfiguration at the callimachus end (so that the old site can be reached at archive.rdf4j.org once we switch). Once that is done we can go live and publish the first milestone.
If there is a hiccup with the reconfig I'll go ahead with switching anyway - it just means that the old site will be (temporarily, until the config is sorted out) unavailable.


Allow to pass llm_client object

As discussed in discord, added ability to build llm_client externally and to pass it, instead of creating llm_client object in each class. This way we can open more people to construct their own llm_clients and use them. Also its possible to change some default in classes, like used model in OpenAI etc.

@zewelor @technicalpickles Okay -- can I suggest something to make these changes manageable?
Can we make this PR simply converting the previous llm:, llm_api_key: pattern to llm: llm_object and revert the builder pattern?

I've removed buil method. Please take a look now if its ok.

@zewelor Sorry -- one last thing: Do you think it's better if the name of the param is just llm: instead of llm_client:?

@andreibondarev Yes, changed llm_client to llm everywhere. I hope now its ok.

LGTM, nice job @zewelor!


[ask] Subscribe topic without create client

How to subscribe to certain topics directly without using MQTT Client anymore?
As for publishing messages, I can use
server. Publish(topic, payload, false, 0)

Are you suggesting that you want to subscribe to topics directly on the Mochi broker side? Why would there be a need to subscribe to topics on the server? If you have such a requirement, you can create your own hook plugin and handle the messages you want to subscribe to within the OnPublish() interface of the hook.

I have such a need for an application I am developing, including to monitor the health status of microservices.
Hahaha, the hook seems to fit, I didn't think of it before, thanks for the suggestion.


Can't run the sample how to solve it?

Severity	Code	Description	Project	File	Line	Column	Suppression State
Error	CS0006	Metadata file 'C:\microsoft-graph-comms-samples-master (6)\microsoft-graph-comms-samples-master\Samples\Common\Sample.Common\bin\Debug\net461\Sample.Common.dll' could not be found	IncidentBot	C:\microsoft-graph-comms-samples-master (6)\microsoft-graph-comms-samples-master\Samples\BetaSamples\RemoteMediaSamples\IncidentBot\CSC	1	1	Active

Severity	Code	Description	Project	File	Line	Column	Suppression State
Error	NETSDK1004	Assets file 'C:\microsoft-graph-comms-samples-master (6)\microsoft-graph-comms-samples-master\Samples\Common\Sample.Common\obj\project.assets.json' not found. Run a NuGet package restore to generate this file.	Sample.Common	C:\Program Files\dotnet\sdk\2.1.509\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets	198	5

Severity	Code	Description	Project	File	Line	Column	Suppression State
Error	NETSDK1004	Assets file 'C:\microsoft-graph-comms-samples-master (6)\microsoft-graph-comms-samples-master\Samples\Common\Sample.Common\obj\project.assets.json' not found. Run a NuGet package restore to generate this file.	Sample.Common	C:\Program Files\dotnet\sdk\2.1.509\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets	198	5

Can anyone help me with this?

You should be able to resolve this with a dotnet restore:

Tools -> NuGet Package Manager -> Package Manager Console
Navigate to the directory containing the .sln file you're trying to build
Run dotnet restore - if there is more than on .sln file in the folder then you can give the command the path as it's first argument (dotnet restore .\MyProj.sln)


AGC v.2024-05-01-preview

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

[!NOTE]
As of January 2024 there is no PR assignee. This is expected. See https://aka.ms/azsdk/pr-arm-review.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Click here to see the details of Step 1, Breaking Changes review
If you are in purview of Step 1 of the diagram, follow the Breaking Changes review process.
IMPORTANT! This applies even if you believe your PR was mislabeled, for any reason, including tool failure.

Click here to see the details of Step 2, ARM review
See https://aka.ms/azsdk/pr-arm-review.

 Click here to see the diagram footnotes
Diagram footnotes
[1] See ARM review queue (for PR merge queues, see [2]).
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[x] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with PR workflow diagram Step 2 (ARM review), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Please fix the failing checks that are labelled as Required.

Please fix the failing checks that are labelled as Required.

Which checks are you referring to in particular?

#suppress "@azure-tools/typespec-azure-core/documentation-required" "MUST fix in next update"

isnt it the next update now?

Refers to: specification/servicenetworking/ServiceNetworking.Management/main.tsp:179 in a30e08a. [](commit_id = a30e08af4c66f30d45b59f2a28c8e063fc25c6a7, deletion_comment = False)

/azp run

Doesn't seem really ready for ARM review yet, in terms of the tooling checks working - those tools are kind of relied on to help with the review and be sure there are no breaking changes etc before ARM review.

Doesn't seem really ready for ARM review yet, in terms of the tooling checks working - those tools are kind of relied on to help with the review and be sure there are no breaking changes etc before ARM review.

@TimLovellSmith Some of the validation errors are taking me in circles. Resolving them brings up other errors and resolving those brings me back to the initial error. One of these errors is the type spec validation (tsv) which suggests removing an example reference when I run it. Removing that example reference from the spec causes the oav-example validation to fail.
Please suggest how I can resolve this problem.

Doesn't seem really ready for ARM review yet, in terms of the tooling checks working - those tools are kind of relied on to help with the review and be sure there are no breaking changes etc before ARM review.

@TimLovellSmith Some of the validation errors are taking me in circles. Resolving them brings up other errors and resolving those brings me back to the initial error. One of these errors is the type spec validation (tsv) which suggests removing an example reference when I run it. Removing that example reference from the spec causes the oav-example validation to fail.
Please suggest how I can resolve this problem.

What is the oav-example validation failure?

Doesn't seem really ready for ARM review yet, in terms of the tooling checks working - those tools are kind of relied on to help with the review and be sure there are no breaking changes etc before ARM review.

@TimLovellSmith Some of the validation errors are taking me in circles. Resolving them brings up other errors and resolving those brings me back to the initial error. One of these errors is the type spec validation (tsv) which suggests removing an example reference when I run it. Removing that example reference from the spec causes the oav-example validation to fail.
Please suggest how I can resolve this problem.

What is the oav-example validation failure?
Here's the error I get:

Doesn't seem really ready for ARM review yet, in terms of the tooling checks working - those tools are kind of relied on to help with the review and be sure there are no breaking changes etc before ARM review.

@TimLovellSmith Some of the validation errors are taking me in circles. Resolving them brings up other errors and resolving those brings me back to the initial error. One of these errors is the type spec validation (tsv) which suggests removing an example reference when I run it. Removing that example reference from the spec causes the oav-example validation to fail.
Please suggest how I can resolve this problem.

What is the oav-example validation failure?
@madhura-np Here's the error I get:

The bug I see right now.  These need to match:
  "operationId": "SecurityPoliciesInterface_GetByTrafficController",

https://github.com/Azure/azure-rest-api-specs/pull/28726/files#diff-06b5ba1d2c9e7ae79a42423fd3ecccd188bb7c3a40442c0f7ea3fb8567157db0R3
        "operationId": "SecurityPoliciesInterface_ListByTrafficController",

https://github.com/Azure/azure-rest-api-specs/pull/28726/files#diff-4b158b271991b24b3ea84a5eae7ba60365e492d86c420405f5777c7e00e58fa7R1047

@raych1: The spec author believes the failure in azure-sdk-go is a false positive.  Can you please take a look?

@malpaniHMC , pls refer to my comment above to fix the readme problems which causes the Go SDK generation failures.

@mikeharder @raych1  thank you that solved the validation errors!

Please get a breaking changes approval from Azure Breaking Changes Reviewers<EMAIL_ADDRESS>and ARM can review the changes afterwards. Once you have the approval, please remove the "ARMChangesRequested" label from the PR to make the PR visible to the ARM reviewers.

/azp run

@ArmReviewer. I approve adding the Version-Approved-Bugfix and BreakingChange-Approved-BugFix

/pr RequestMerge

/azp run


msaa-renderpass.rs example should clear to blue but instead has a transparent background

When running the msaa-renderpass.rs example, the resulting image is not cleared with blue as expected. Instead, the resulting .png has a transparent background.
Interestingly, the red triangle seems to have a faint outline where the red has been mixed with blue in the multi-sampling process, almost as if only the areas behind the geometry were cleared blue.
Here is the image that is produced when I run the msaa-renderpass.rs example:

I tried applying the same msaa technique to the triangle.rs example but got the same result.
I should note that clear works fine in the regular triangle.rs example, the problem only seems to arise with this MSAA technique.
cc @rukai

Here is the output of vulkaninfo in case it helps.

Thanks for the issue.
I can reproduce this when setting the physical device to Intel(R) HD Graphics 620 (Kaby Lake GT2).
When using AMD RADV ICELAND (LLVM 7.0.0) on the same laptop the issue does not occur.
At this point I think its much more likely for this to be a vulkano issue than a driver issue.

I'm also getting this on mac0s and ubuntu both with Intel(R) HD Graphics 6000 (Broadwell GT3)

A couple of notes (I'm pretty new to this so it might not be relevant).
If you lower the alpha in the example to 0.1 and enable alpha blending you get this:

And with alpha at 0.1 and without blending you get:

I was wondering if something is causing the background not to be put back

@rukai out of curiosity, do you also run into this issue in your PF_Sandbox project when using your Intel(R) HD Graphics 620 (Kaby Lake GT2)?
I watched the video you have up for PF_Sandbox the other day btw, looks like a lot of fun! I grew up playing smash, can definitely feel the inspiration :)

Yeah PF Sandbox works fine on Intel(R) HD Graphics 620 (Kaby Lake GT2)
I do have problems with the AMD device though. The characters don't render unless the resolution is really small.
Thanks!

@rukai oh right, as in clearing works fine in PF Sandbox? Are you sure that you don't just happen to be clearing to black and are seeing the default swapchain colour or something like that? What if you clear to a different colour?
@freesig ahh nice find, at least we can confirm it must be something in vulkano now. That example will be handy to A/B with.

Actually I was wrong the bug is present in saschas example aswell. So maybe it is a driver bug?


directives do not perform correct in Angular 7.0.0

i try to use Material<7.2.0> directive  in Angular 7.0.0
use the mat-card example:
Simple Card
and i also import the prebuild-theme
but i found that there's no class="mat-card" generated in this directive
then i append this class by my self ,but there's still lose some css style which should be generated by the
MatCard directive (selector: mat-card  export:matCard);
so my question is : is this the issue of Angular's version? should it will be alright under lower angular version?

You're supposed to use mat-card as an element. There are some code samples in our documentation.


x/net/http2/hpack: optimize constantTimeStringCompare

hpack's constantTimeStringCompare shows up in profiles as slow.
Investigate optimizing it.
/cc @jeffallen @tombergan

"Optimize" like in "call it less" or like in "make it faster"? If uglier code is fine, unrolling the loop gives a nice boost (at least on amd64):
ConstantTimeStringCompare/3-4     6.20ns ± 1%  8.53ns ± 0%  +37.48%  (p=0.000 n=7+8)
ConstantTimeStringCompare/4-4     7.17ns ± 0%  7.55ns ± 0%   +5.32%  (p=0.001 n=7+7)
ConstantTimeStringCompare/16-4    18.9ns ± 0%   7.6ns ± 0%  -59.99%  (p=0.000 n=7+8)
ConstantTimeStringCompare/64-4    66.2ns ± 0%  18.5ns ± 1%  -72.07%  (p=0.000 n=8+8)
ConstantTimeStringCompare/256-4    212ns ± 0%    61ns ± 1%  -71.06%  (p=0.000 n=7+8)
ConstantTimeStringCompare/1024-4   804ns ± 1%   229ns ± 0%  -71.50%  (p=0.000 n=8+8)

"Optimize" like in "call it less" or like in "make it faster"?

Either/both?

How long are typical inputs to constantTimeStringCompare?
For long strings pseudo-simd can help:
x:= a[0] | a[1] << 8 ..  //should compile to single bound check + machine-word sizedload
y:= b[0]...
z |= x^y
However code will be different for little and big endian, and won't work on architectures requiring aligned loads. It will also be quite ugly. Alternatively unsafe (or even asm) can be used.
In any case representative benchmarks are needed as a first step.

Inputs are HTTP header values, so typically less than 100 bytes. (The longest would probably be some random UUID/hex-looking session identifier.)

@tombergan, are you able to share a histogram of HTTP header value sizes from the Flywheel data?
I tried looking at https://telemetry.mozilla.org/ too but don't see it.

I'm not sure why constant time string comparison is needed in the first place. RFC 7541 does not mention a need for this AFAICT. I couldn't find any reported vulnerabilities after a quick search. It seems like staticTable could be implemented as a map rather than an array. I looked at the source code for two other HTTP2 implementations. Neither appears to use constant-time string comparisons:

nghttp2
Chrome

/cc @tatsuhiro-t who originally wrote the code, thoughts?

There was a statement regarding prevention of timing attacks, but it was removed.
See https://github.com/http2/http2-spec/commit/f4ec4e3f0d17459a8af9eb80645ad0c1d6520972

Thanks for digging that up. In that case, I think it's safe to remove the constant-time string comparison entirely.

SGTM. Sent you a CL.

I think it was removed because Never Indexed has been introduced for the sensitive header fields.


Getting an error when trying to kill the app while the keyboard is opened.

Steps to Reproduce

1 - Launch the default Flutter app ( the counter app).
2 - Add TextFormField only for the class.
3 - open the Keyboard and then try to exit/ kill the app.
Expected results:
Exiting the app without an error.
Actual results:
The app is being disconnected but with an error.

Logs
[EventDeferring] - [UIScene (EventDeferring) _eventDeferringManager]: No viable event deferring manager found for scene, returning nil: <_UIKeyboardWindowScene: 0x147352500>
[EventDeferring] - [UIScene (EventDeferring) _eventDeferringManager]: No viable event
deferring manager found for scene, returning nil: <_UIKeyboardWindowScene: 0×147352500>
No windows have a root view controller, cannot save application state

Flutter doctor -v
  [✓] Flutter (Channel stable, 3.3.9, on macOS 13.0.1 22A400 darwin-arm, locale en-LB)

   • Flutter version 3.3.9 on channel stable at
    /Users/hassanyassin/Desktop/Flutter/Development/Tools/flutter
   • Upstream repository https://github.com/flutter/flutter.git
   • Framework revision b8f7f1f986 (9 days ago), 2022-11-23 06:43:51 +0900
   • Engine revision 8f2221fbef
   • Dart version 2.18.5
   • DevTools version 2.15.0

  [✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
  • Android SDK at /Users/hassanyassin/Library/Android/sdk
  • Platform android-33, build-tools 33.0.0
  • Java binary at: /Applications/Android
    Studio.app/Contents/jre/Contents/Home/bin/java
  • Java version OpenJDK Runtime Environment (build
    11.0.13+0-b1751.21-8125866)
  • All Android licenses accepted.

  [✓] Xcode - develop for iOS and macOS (Xcode 14.1)
  • Xcode at /Applications/Xcode.app/Contents/Developer
  • Build 14B47b
  • CocoaPods version 1.11.3

  [✓] Chrome - develop for the web
  • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

  [✓] Android Studio (version 2021.3)
  • Android Studio at /Applications/Android Studio.app/Contents
  • Flutter plugin can be installed from:
    🔨 https://plugins.jetbrains.com/plugin/9212-flutter
  • Dart plugin can be installed from:
    🔨 https://plugins.jetbrains.com/plugin/6351-dart
  • Java version OpenJDK Runtime Environment (build
    11.0.13+0-b1751.21-8125866)

  [✓] Connected device (4 available)
   • iPhone X (mobile)          • 08f6d5d4e6ac65273a8757fc2424f2f593e6ca56 •
     ios            • iOS 16.1.1 20B101
   • iPhone 14 Pro Max (mobile) • B6B4CDD3-90C8-451E-B16D-563A2EF56E5F     •
     ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-1 (simulator)
  • macOS (desktop)            • macos                                    •
   darwin-arm64   • macOS 13.0.1 22A400 darwin-arm
  • Chrome (web)               • chrome                                   •
   web-javascript • Google Chrome 108.0.5359.71

  [✓] HTTP Host Availability
  • All required HTTP hosts are available

  • No issues found!

// Tested on iPhone X (Real device), iOS version 16.1.1
https://user-images.githubusercontent.com/94860683/205061843-103bf90f-bf56-4a76-aaa0-ac904c1e9e5f.mov

I see some messages in my console when I follow the steps outlined above.
Labeling for further insight from the team.
Launching lib/main.dart on Nexus in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: X8NNQ9CYL2
Xcode build done.                                           14.6s
Successfully load keyboard extensions
[EventDeferring] -[UIScene(EventDeferring) _eventDeferringManager]: No viable event deferring manager found for scene, returning nil: <_UIKeyboardWindowScene: 0x10388fcc0>
[EventDeferring] -[UIScene(EventDeferring) _eventDeferringManager]: No viable event deferring manager found for scene, returning nil: <_UIKeyboardWindowScene: 0x10388fcc0>
No windows have a root view controller, cannot save application state
Lost connection to device.

Exited.

code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            TextFormField(),
            const Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.headline4,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel stable, 3.3.9, on macOS 13.0.1 22A400 darwin-arm, locale en-GB)
    • Flutter version 3.3.9 on channel stable at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b8f7f1f986 (13 days ago), 2022-11-23 06:43:51 +0900
    • Engine revision 8f2221fbef
    • Dart version 2.18.5
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio
    • Android Studio at /Applications/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[!] Android Studio
    • Android Studio at /Applications/Android Studio Preview 2.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] Android Studio (version 2021.3)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] Android Studio (version 2021.3)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9014738/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] VS Code (version 1.73.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.54.0

[✓] Connected device (5 available)
    • M2007J20CG (mobile)    • 5dd3be00                             • android-arm64  • Android 12 (API 31)
    • Nexus (mobile)         • 00008020-001875E83A38002E            • ios            • iOS 16.1.2 20B110
    • iPhone 14 Pro (mobile) • 4F72110C-F38B-4CF9-93C4-4D6042148D28 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-1 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 13.0.1 22A400 darwin-arm
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 108.0.5359.94

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 2 categories.

[!] Flutter (Channel master, 3.7.0-2.0.pre.38, on macOS 13.0.1 22A400 darwin-arm64, locale en-GB)
    • Flutter version 3.7.0-2.0.pre.38 on channel master at /Users/nexus/dev/sdks/flutters
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18534a8e4c (11 hours ago), 2022-12-04 17:44:35 -0500
    • Engine revision 359a0a979a
    • Dart version 2.19.0 (build 2.19.0-444.0.dev)
    • DevTools version 2.20.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio
    • Android Studio at /Applications/Android Studio Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[!] Android Studio
    • Android Studio at /Applications/Android Studio Preview 2.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] Android Studio (version 2021.3)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] Android Studio (version 2021.3)
    • Android Studio at /Users/nexus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9014738/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] VS Code (version 1.73.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.54.0

[✓] Connected device (5 available)
    • M2007J20CG (mobile)    • 5dd3be00                             • android-arm64  • Android 12 (API 31)
    • Nexus (mobile)         • 00008020-001875E83A38002E            • ios            • iOS 16.1.2 20B110
    • iPhone 14 Pro (mobile) • 4F72110C-F38B-4CF9-93C4-4D6042148D28 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-1 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 13.0.1 22A400 darwin-arm64
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 108.0.5359.94

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 3 categories

This doesn't seem to emanate from the engine and does seem benign. Perhaps we should filter these out in the tool.

Perhaps we should filter these out in the tool.

That sounds difficult, these kinds of logs are moving targets and we'll never match all of them without being too aggressive and possibly filtering out useful messages.


Catch malformed python and ES validation scenarios

I don't want to stuff too many tasks into one ticket so this is split off of #431

Hi Esty, is https://github.com/MI-DPLA/combine/issues/434 goal to display (currently hidden) validation errors for python and ES?
So the errors are happening but aren't currently displayed?


The new STM32H743VIT6 can be included as the variant px4fmu-v5-pro

ST has released its most powerful processor STM32H7. The core clock speed can be up to 400MHz plus 2MB flash and 1MB ram. According to ST，the programming architecture of H7 will exactly be the same with F7. That is to say the ISR configuration and PIN would be consistent. So a suggestion is that some tiny revisions be added based on the px4fmu-v5，which supports the clock speed and ram size. Then just test H7 to see if it is OK for programming with existing NuttX RTOS for stm32f7.

We have already dev boards and will bring them up starting next week.

good idea

@LorenzMeier  Hi Lorenz, we have started the design of STM32H7 autopilot. We will mail you one once finished

@LorenzMeier  Hi Lorenz, Nice to see you. We have finished the H7 autopilot board. Should I mail you one for test?

@zarathustr Could you drop me an email on<EMAIL_ADDRESS>I can then send you the shipping address.


[Bug] Some manga chapters are missing

Device information

Tachiyomi version: <IP_ADDRESS>
Android phone & version: Redmi note 4 running Custom Rom - Android 10

Steps to reproduce
Search for the desired manga and opening it
Expected behavior
List of all chapters of the manga should be shown
Actual behavior
Some chapters are missing (Some showing no chapters)
Other details
Manga like One punch man is showing NO Chapters, while some like Solo Levelling has some of the chapters missing.
All Chapters of the manga can be found in the MangaDex Website (English version)....
Please fix this Issue...

By the way Love the App, Cool Design..

All Chapters of the manga can be found in the MangaDex Website (English version)....
Except they can't

OPM had all its english chapters removed a few weeks ago.  There are no english chapters on MangaDex.

As for Solo leveling it is also missing those chapters you mentioned.  Those were originally scanned by JB and they left MangaDex over a year ago.

Also fyi this is why i added the merge function.  To attempt to fill in missing or removed chapters


[$500] [Distance] - Map does not zoom out to show the entire route when the map window is reduced

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Issue found when executing PR https://github.com/Expensify/App/pull/26591
Action Performed:

Go to staging.new.expensify.com
Go to + > Request money > Distance
Add a start (1 Telegraph Hill Blvd) and finish point (88 Kearny St. San Francisco)
Click Add stop

Expected Result:
The map zooms out to show the entire route when the map window is reduced
Actual Result:
The map does not zoom out to show the entire route when the map window is reduced.
On Android app, the map zooms out automatically
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome
[ ] MacOS / Desktop

Version Number: 1.3.63-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/1c3129c0-9a22-40cd-b9e0-2d2c32810e35
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01d3c0d2628f023ef1
Upwork Job ID:<PHONE_NUMBER>165142016
Last Price Increase: 2023-09-18

So the issue here is that on New.Dot (non-Android), you add a 3rd stop and the green line disappears and the map zooms out, almost in preparation for you to add that 3rd stop:

Whereas in Android it doesn't - the line remains and doesn't really zoom.

Ok, I updated my Android app and can confirm that this is an app only issue - Chrome is fine, and follows New.Dot (web) behaviours.

@lanitochka17 can you clarify what you expect the behaviour to be? Should we be seeing a green line or not?

Here's another regression (?) @hayata-suenaga and @situchan - it looks like the Android app shows a green line when adding a 3rd location, whereas Android Chrome and Web do not.

@hayata-suenaga it doesn't look like a job was created when the External label was added so re-added. Also, I wanted to confirm that this isn't an issue on Android? From my initial testing, it seems like it could be an issue on the Android app too.

Thank you for reapplying the label 🙇 And thank you for testing on Android

Proposal
Please re-state the problem that we are trying to solve in this issue.
Map does not zoom out to show entire route when the map window is reduced, and the route re-renders when the map is resized.
What is the root cause of that problem?
This is actually being caused by the route being cleared whenever a stop is added to the transaction. This creates a brief moment where the direction coordinate passed to the map is null, which causes it to clear, and then re-render when the route is eventually recalculated.
What changes do you think we should make in order to solve the problem?
Solution 1
Do not clear the route when a stop is added to the transaction. Instead check if there are at least 2 validated waypoints before clearing the route.
Solution 2
If there at least 2 validated waypoints in DistanceRequest but directionCoordinates is null, do not update the prop. Otherwise only update the directionCoordinates prop if there is only one waypoint and the route calculation is null.
What alternative solutions did you explore? (Optional)
None.

@akinwale thanks for the proposal.

the map does not automatically readjust the bounds on web as it does on the native iOS and Android platforms

Can we try to fix this in upstream (mapbox web sdk)?

It looks like this is something that we're meant to implement ourselves when using Mapbox on the web, not exactly an issue. For the web, Mapbox GL JS is the underlying Mapbox implementation used.
Here are some of the issues related to what we're trying to achieve.
https://github.com/mapbox/mapbox-gl-js/issues/2090 - from 2016.
https://github.com/mapbox/mapbox-gl-js/issues/8920 - from 2019.
https://github.com/mapbox/mapbox-gl-js/issues/11004 - the most recent I could find from 2021.
The consensus seems that if the map container is resized, you have to call the map.resize() method first before performing any new operations on the map.
I use a boolean state variable to track whether or not to call the fitBounds method since the state update is done afterwards. Trying to call fitBounds in the map resize event handler (mapRef.on('resize', ...) does not work as expected since it seems the map resize operation is not complete at that point.

As this won't be most likely fixed in upstream, need to test proposed solution of local fix.

As this won't be most likely fixed in upstream, need to test proposed solution of local fix.

The route refresh issue is fixed in https://github.com/Expensify/App/pull/27496. So only the bounds functionality needs to be tested here.
Also, it looks like map resize will be added to https://github.com/Expensify/App/issues/26540 so it makes sense to wait for the PR on that to be merged before we proceed here because it makes use of a ResizeObserver to trigger map.resize.

@situchan https://github.com/Expensify/App/pull/27574 has been merged and deployed to staging, so I think we can move forward here.

I think we can wait a bit more to hit production. I hope that won't happen but revert case due to regression.

Interesting that we have to call resize every time the map size changes...
by the way, why are we waiting on this PR?

Interesting that we have to call resize every time the map size changes...
by the way, why are we waiting on this PR?

It implements calling map.resize() using the ResizeObserver which is also done in my proposal. I recommended waiting for it to be merged to avoid a duplication of effort. I feel like we can move forward at this point, but we can also wait for the regression tests to be complete according to @situchan's recommendation.

yes let's wait for the PR to be deployed to production

@situchan https://github.com/Expensify/App/pull/27574 has been deployed to production.

I'm currently on a bad internet connection, but I tested this (v 73-0 Chrome) and think this is now fixed? I'm seeing the map points properly move now cc @hayata-suenaga @situchan

@jliexpensify The steps to reproduce have changed since the Add Stop behaviour has been modified. It can be reproduced if the browser window is vertically resized, of if the map is resized due to a change in responsive layout.

@akinwale
The issue seems like to be still present
https://github.com/Expensify/App/assets/98560306/c744c9d3-29e2-41e6-b273-be897a1e353c

@akinwale
The issue seems like to be still present

Looks like it. The changes in my proposal should still work in this case. We can move forward when @situchan is ready.

ah I somehow thought the PR is already deployed to production 😓

Issue not reproducible during KI retests. (First week)

Issue not reproducible during KI retests. (First week)

The reproduction steps have changed.

Hmm so what's happening here? Are we waiting on @situchan to do something? Going off this comment.

@akinwale can you update your proposal based on latest codebase? So remove deprecated solutions and update demo video to reflect browser resizing instead of adding new route.

@akinwale can you update your proposal based on latest codebase? So remove deprecated solutions and update demo video to reflect browser resizing instead of adding new route.

@situchan Updated the proposal and demo video.

Issue not reproducible during KI retests. (Second week)

Issue not reproducible during KI retests. (First week)

The reproduction steps have changed.

@mvtglobally Did you follow the new reproduction steps?

@hayata-suenaga are steps updated in the original top report? Or it's in the comments?
We usually follow the original report steps only.

@akinwale or @situchan can you find the latest test steps? 🙇

@akinwale or @situchan can you find the latest test steps? 🙇

Launch Expensify.
Open the global create menu and select Request money.
Select the Distance tab if it is not already selected.
Add the Start (1 Telegraph Hill Blvd) and Finish (88 Kearny St. San Francisco) waypoints.
Resize the browser window vertically by either reducing or increasing the height of the window.

thank you so much @akinwale!
I updated the original top report with the test steps above. @mvtglobally please retest again 🙇

Issue is not reproduced with provided steps here https://github.com/Expensify/App/issues/26724#issuecomment-1748145650
https://github.com/Expensify/App/assets/93399543/1ac0afcf-0318-4e44-8fa8-b7cf5a592d54

@hayata-suenaga From the test video above, it looks like the map now has a fixed height which doesn't change. Is this intentional? If so, then this issue is no longer relevant.

@hayata-suenaga From the test video above, it looks like the map now has a fixed height which doesn't change. Is this intentional? If so, then this issue is no longer relevant.

No, it will be fixed in https://github.com/Expensify/App/issues/28911.
I think we need to put this on hold until https://github.com/Expensify/App/pull/28922 is merged.

Changing to Weekly as it's on HOLD

I'm taking this over for Hayata as decided here (internally) in Slack. Sounds like we're holding for Fix map preview not extended to full view right now which makes sense.

I updated this issue to be held on the issue that PR fixes ^ since we usually hold on the issue rather than the PR.

Issue not reproducible during KI retests. (Third week)

So longer on HOLD. @jliexpensify would you please test if it's still reproducible?

So longer on HOLD. @jliexpensify would you please test if it's still reproducible?

Still reproducible on the latest main branch.

Tested on Staging v1.3.88-3:
https://github.com/Expensify/App/assets/30815269/150c4fba-ed26-4254-ba6e-529c49354bf0
This is the same as Android (Chrome) and Android app - the map auto-zooms out.
@akinwale can you share a video?

@jliexpensify The steps to reproduce have changed.
Context: https://github.com/Expensify/App/issues/26724#issuecomment-1732826149
Video: https://github.com/Expensify/App/issues/26724#issuecomment-1734676514
Updated steps: https://github.com/Expensify/App/issues/26724#issuecomment-1748145650

Ah sorry @akinwale - here's a re-test with the new steps
https://github.com/Expensify/App/assets/30815269/78263363-96ef-4f59-bfb8-1b23485028af
Let me know if I've reproduced this incorrectly!

@jliexpensify Looks like it's not as noticeable as it was previously. Can you try to manually zoom in on the map using your mouse wheel and then resize the browser window to see if it adjusts?

Looks like no adjustment if zoomed in:
https://github.com/Expensify/App/assets/30815269/114ede95-fe09-4060-a08b-b7d8eab6497c

Looks like no adjustment if zoomed in:

Yeah, so we'll still need to fix that if it's considered worth fixing.
cc @neil-marcellini

I don't think it's a problem if it doesn't adjust while zoomed. I remember that at one point we considered making the map non-interactive on this page, but I'm not passionate about it. I don't see any problems now, so I think we can close this. Do you agree @jliexpensify?

Yeah, I agree - I don't think it's a huge deal. Closing!

Should https://github.com/Expensify/App/issues/29469 be closed as well?

Thanks @situchan , left a comment in that other GH!


Pathway Component v2

Redesigned Pathway component and added new functionality. Can now delete and edit pathways and it all persists with local storage.
Pathways page:

Edit dialog - before edit:

Edit dialog - changes made:

Pathways page - after edit:

Full fuctionality:
https://github.com/UMLCloudComputing/UniPath.io/assets/81245965/f7ac712d-248c-4a06-9c03-78033a571b5e

bruh ill fix the conflicts tomorrow


About --ckpt /path/to/model.pth

May I ask where the path to pre-trained model  is ？

May I ask what pre-traine model you are using

@Lin-xuejuan-an Hey, Did you find a solution? I'm not able to main_linear.py file. I am getting missing key error (mismatch architecture). Basically, a wrong pre-trained model.


runtime: sporadic memory allocation issues when sufficiently large dependencies are brought in by a program that sets memory rlimits

Go version
go version go1.22.6 linux/amd64
Output of go env in your module/workspace:
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/akalenyu/.cache/go-build'
GOENV='/home/akalenyu/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/akalenyu/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/akalenyu/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/usr/local/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.22.6'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/home/akalenyu/Work/kubernetes/go.mod'
GOWORK='/home/akalenyu/Work/kubernetes/go.work'
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build3633518003=/tmp/go-build -gno-record-gcc-switches'

What did you do?

No sporadic ENOMEM

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

If a program runs out of memory, it can't continue.  1G is not going to be enough for a large program.  What are you suggesting that we do here?

I am suggesting that something leaks, since it's very unlikely that simple program would run out of 1G of memory

I don't think it's unlikely at all.  You are limiting the size of virtual memory, but the program itself takes up virtual memory.

Hmm, the core dump size is also nowhere near 1G. What am I missing here?
ls -sh ./virt-chroot.core
136M ./virt-chroot.core

The Go runtime reserves large portions of address space, see https://go.dev/doc/gc-guide#A_note_about_virtual_memory. RLIMIT_AS is not a good way to limit the memory of Go programs.
cc @mknyszek

The Go runtime reserves large portions of address space, see https://go.dev/doc/gc-guide#A_note_about_virtual_memory. RLIMIT_AS is not a good way to limit the memory of Go programs.
cc @mknyszek

Thank you! this link is super useful.
From a quick search I see that we have no better options unfortunately, since SetMemoryLimit is a soft limit
and we're kind of looking at protecting against malicious usage of a binary out of our control.

RLIMIT_AS is about address space reservation, not actually committed memory. I see 24 mappings that are larger than 50 megabytes. The address space limit is already exceeded at the time of the syscall.Rlimit call. Linux does not return failure in this case. The limit is still applied, but future allocation (actually: address space reservation) from the kernel will fail. But there is still plenty of unused Go heap, so most of the time, the program succeeds. There's probably some heap expansion heuristic that kicks in very rarely, and that produces the sporadic failure. But in truth, the process is in a bad state during every run.

Thank you. I am assuming those come from the "sufficiently large dependencies"
but I am particularly interested in 2 mmaps for 512Mi that IIUC already exceed the disclaimers in https://go.dev/doc/gc-guide#A_note_about_virtual_memory

If you are running on Linux, I recommend using a memory cgroup to limit memory use of an application. Memory cgroups measure actual memory usage more precisely and aren't quite so trivially circumvented (RLIMIT_AS is immediately circumvented by fork()).

If you are running on Linux, I recommend using a memory cgroup to limit memory use of an application. Memory cgroups measure actual memory usage more precisely and aren't quite so trivially circumvented (RLIMIT_AS is immediately circumvented by fork()).

So we follow up on the Setrlimit call with a syscall.Exec, so it should not be circumvented.
I am thinking the same about cgroups being our best bet, but, if we don't, I guess we could do some nasty things with a short cgo func that calls setrlimit and execve directly

Related Issues and Documentation

cmd/go: "runtime: cannot allocate memory" in workspaces with many non go files #54226 (closed)
cmd/link: fatal error: runtime: out of memory #26132 (closed)
debug/pe: fatal error: runtime: out of memory on NewFile #43827
fatal error: out of memory #13728 (closed)
runtime: fatal error: sweep increased allocation count (With go get) #19029 (closed)
cmd/compile: runs out of memory allocating 12k + items in a map at init, works as literal map #13554 (closed)
runtime: `cannot allocate memory` testing `x/sys/unix` on linux-386-stretch #52576 (closed)
runtime: crash in memory allocator running gomvpkg #17892 (closed)
runtime: huge page fragmentation on Linux leads to out of memory #12233 (closed)
x/tools/gopls: cannot handle large files #33003 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Ah, do you actually want to apply the rlimit to a (non-Go) process you are exec'ing to? I think there is reasonable room for a proposal to add rlimits to https://pkg.go.dev/syscall#SysProcAttr so that os.StartProcess / os/exec could set rlimits for the child process.

Note that at least on Linux you can also do that by executing the process via the prlimit command.

So playing around a bit with this new finding, I am getting larger VSS numbers in the core dump than I was expecting. I acknowledge that I might be doing something terribly wrong, but, would 1.4Gi be expected with the below program?
package main

import (
	"fmt"

	"net/http"
)

func main() {
	fmt.Println(http.Client{})
	panic("test")
}

$ eu-readelf -l reprducer-cgo-pthread.core | awk '{sz=strtonum($6); if (sz > 50 * 1024 * 1024) {print sz}}' | awk '{n += $1}; END{print n}'
1505267712


"Apps using Google Cloud Messaging" is empty

It just shows a white screen. I have WhatsApp installed which uses GCM, so it should definitely show up in the list. I didn't see any errors/warnings in logcat.
Let me know if there's any way to help with this.
microG Services Core Version 0.2.4-g63fd64f
UnifiedNlp 1.6.7-1-g38acecd

The apps are registered at installation phase, so every app installed before microG will not work.

That seems pretty annyoing. Is this something that could be fixed in the code?

I'm not sure but you can just install microG before any other app.
For now just reinstall the apps.

I would also add that the problem is not restricted to microG but happens with the official Google Play Services too, if those apps have been installed before GApps themselves. The issue also occurs when restoring apps using Titanium Backup. They will not be registered for GCM unless a complete reinstallation takes place (deleting data does not help).

I forgot to mention this, but GCM works fine with WhatsApp. The only problem is that the list of GCM apps in microG Settings is empty.

I have Signal and it appears in the list, I don't know what it can be.
Try to check if it happens only with WhatsApp.

For me, even after a reinstall with adb install -r, Signal is not appearing in the list.

@Nutomic I have tested two apps (Skype and KakaoTalk) and they only appeared after a full reinstallation. Reinstallation using Titanium Backup did not work. I had to uninstall and reinstall them from scratch (from Play Store).

I managed to get signal into this list. I had to reregister to the server: Signal > Settings > Advanced > Signal messages and calls.


[docs] Demo MultipleSelect crashes

[ ] I have searched for similar issues in this repository and believe that this is not a duplicate.

Steps to reproduce

Visit https://mui-com.translate.goog/material-ui/react-select/?_x_tr_sl=en&_x_tr_tl=pt&_x_tr_hl=pt-BR&_x_tr_pto=sc&_x_tr_hist=true
??
demo MultipleSelect crashes

Your environment

Tech
Version

Version
v5.15.16

Netlify deploy
https://663569f01a66560008a89f54--material-ui-docs.netlify.app

Browser
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36

Search keywords:

I can't reproduce it here: https://mui-com.translate.goog/material-ui/react-select/?_x_tr_sl=en&_x_tr_tl=pt&_x_tr_hl=pt-BR&_x_tr_pto=sc&_x_tr_hist=true#default. Can you provide a video reproduction?


Camera is stretched

Hello,
I have created a layout on android with a simple menu of 50dp and under a "surfaceview" where I used the library of qr reader to read the qr code, only that the camera is stretched, I also tried to enter 50 dp margin to surface view to keep the spaces, but nothing has changed, how can I solve this problem?
I used version 2.1.2 of the library
Preview:

Have you checked out the sample app? Does the issue occur in the sample app too?
Can you create a simple implementation reporducing the issue for me to debug?
Thank you

My code is the same as the demo, I enter the code below:
`package eu.followine.followine;
import android.Manifest;
import android.content.Context;
import android.content.Intent;
import android.content.SharedPreferences;
import android.content.pm.PackageManager;
import android.content.res.Resources;
import android.graphics.Point;
import android.location.Location;
import android.location.LocationListener;
import android.location.LocationManager;
import android.net.ConnectivityManager;
import android.net.NetworkInfo;
import android.support.design.widget.NavigationView;
import android.support.v4.app.ActivityCompat;
import android.support.v4.widget.DrawerLayout;
import android.support.v7.app.AppCompatActivity;
import android.os.Bundle;
import android.util.Log;
import android.util.TypedValue;
import android.view.Display;
import android.view.Gravity;
import android.view.MenuItem;
import android.view.SurfaceView;
import android.view.View;
import android.widget.ImageButton;
import com.loopj.android.http.AsyncHttpClient;
import com.loopj.android.http.AsyncHttpResponseHandler;
import com.loopj.android.http.RequestParams;
import org.json.JSONException;
import org.json.JSONObject;
import java.io.IOException;
import java.io.UnsupportedEncodingException;
import cz.msebera.android.httpclient.Header;
import github.nisrulz.qreader.QRDataListener;
import github.nisrulz.qreader.QREader;
public class Main extends AppCompatActivity {
private SurfaceView mySurfaceView;
private QREader qrEader;
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.main);
    final DrawerLayout mDrawerLayout = findViewById(R.id.drawer_layout);
    mySurfaceView = (SurfaceView) findViewById(R.id.camera_view);
    qrEader = new QREader.Builder(this, mySurfaceView, new QRDataListener() {
        @Override
        public void onDetected(final String data) {

        }
    }).facing(QREader.BACK_CAM)
            .enableAutofocus(true)
            .height(mySurfaceView.getHeight())
            .width(mySurfaceView.getWidth())
            .build();

}

@Override
protected void onStart() {
    super.onStart();
    qrEader.start();
}

@Override
protected void onResume() {
    super.onResume();

    qrEader.initAndStart(mySurfaceView);
    isCheck = 0;
}

@Override
protected void onPause() {
    super.onPause();

    qrEader.releaseAndCleanup();
}

}
`
And this is the xml:
`
<android.support.v4.widget.DrawerLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
android:id="@+id/drawer_layout"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:fitsSystemWindows="true">
<FrameLayout
    android:id="@+id/content_frame"
    android:layout_width="match_parent"
    android:layout_height="match_parent" >

    <android.support.v7.widget.Toolbar
        android:id="@+id/toolbar"
        android:layout_width="match_parent"
        android:layout_height="?attr/actionBarSize"
<EMAIL_ADDRESS>/>

    <RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
        android:layout_width="match_parent"
        android:layout_height="match_parent">

        <include
            android:id="@+id/menu"
            layout="@layout/menu"
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
            android:layout_alignParentStart="true"
            android:layout_alignParentTop="true" />

        <SurfaceView
            android:id="@+id/camera_view"
            android:layout_width="match_parent"
            android:layout_height="match_parent"
            android:layout_below="@id/menu"
            android:layout_weight="1" />

    </RelativeLayout>
</FrameLayout>

<android.support.design.widget.NavigationView
android:id="@+id/nav_view"
android:layout_width="wrap_content"
android:layout_height="match_parent"
android:layout_gravity="start"
android:fitsSystemWindows="true"
app:menu="@menu/drawer_view"/>

</android.support.v4.widget.DrawerLayout>`
PS: Menu height is 50dp

Any news? please help me

What happens if you remove android:layout_weight="1" from your SurfaceView?

However, if the QREader is built in onCreate or onResume, the final size of the SurfaceView in which the camera preview is shown may not be calculated yet.
There are several issues at play here:

The QREader.Builder requires the width and height of the size to be defined at the time the QREader is built. QREader assumes (=requires) that QREader.initAndStart(SurfaceView surfaceView) is called before the mentioned final size is calculated, so for example on onResume which makes it impossible to supply the correct size calculated from a ViewTreeObserver.OnGlobalLayoutListener to the builder
Because of the above, the QREader must be created in onCreate or latest in onResume, that the camera permission must already been granted in the activity / fragment in which the class is used. (The sample app "solves" this by restarting the activity when. Obviously, this solution is not applicable for everyone)
The size as set in the builder is just the requested preview size which means that there is no guarantee that the camera shoves bitmaps onto the SurfaceView in exactly that size. Due to the nature how a SurfaceView works, IIRC, the source bitmap is stretched onto the view. To solve this, one has to manually recalculate the bounds of the bitmap to simulate/reimplement a ScaleType.CENTER_CROP as seen for ImageViews.

No, I do not have an example (it is not open source), but I can roughly lay it out for you:
Let's say the camera preview is for some reason a square, while the surface view is a 1:2 (portrait) rectangle. One trick to make the camera picture appear non-skewed is to make the surface view itself have the same aspect ratio as the camera picture (in this case, a square) by modifying its margins (and ensuring the parent view clips to bounds, which is the default though anyway).
To achieve something like CENTER_CROP, set negative margins so that width - horizontal margins / (height - vertical margins) = desired aspect ratio, which is 1 in this case.
To achieve something like CENTER_INSIDE, use positive margins.
For the example of the square and the portrait, you would set a negative horizontal margin for CENTER_CROP or a positive vertical margin for CENTER_INSIDE.


testchange runtime filter test's checker

Proposed changes
Issue Number: close #xxx
Problem summary
change runtime filter test's checker from String... colNames to Set<Pair<String, String>> colNames
Checklist(Required)

Does it affect the original behavior:

[x] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[x] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[x] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

redundant, close


update userTopBids hook to use latest endpoint

Noticed user top bids hook couldn't filter by collection set, so updating it to use the latest endpoint

Sorry that this has been here for a little while, needed to spend a bit of time to see the diff between the different versions (v2 -> v4). Here's the summary:
Request Changes:

Ability to filter by contractSetId
Ability to filter by collectionSetId
Ability to specify excludeEOA
Increased the limit maximum to 100 from 20
Response Changes:
Price object is now standardized (BREAKING)
Floor ask Price is now standardized (BREAKING)
Last sale price is now standardized (BREAKING)
Collection Floor ask sale price is now standardized (BREAKING)

I think now that this has been documented we can release this.


PolylineGeometryUpdater crashes when there is no globe

Forum post:
https://groups.google.com/d/msg/cesium-dev/UboMKwwn8Xk/noMUrTS7CQAJ
This line crashes if there is no globe:
https://github.com/AnalyticalGraphicsInc/cesium/blob/master/Source/DataSources/PolylineGeometryUpdater.js#L519
This assignment should be delayed until update and only done if followSurface is true.  Otherwise generateCartesianArcOptions is unused.

Fixed in https://github.com/AnalyticalGraphicsInc/cesium/pull/5413


Fixed #30231 -- Fixed admin filter horizontal/vertical verbose_name generation.

Ticket #30231, and follows #11282
I've added three more tests to the previous version of this patch. This gives a total of 4 tests for the 4 changes in the JS. As the tests are identical I've used subtest to save a significant amount of repetition.
The comments on the previous PR suggested exploring using an existing model. I've managed to do this but needed to change one of the existing models slightly while not breaking any of the existing tests.
Hopefully, less typo's today 🙈

buildbot, test on selenium.

buildbot, test on selenium.

Hi @carltongibson

When a Model has a field with primary_key=True and the Admin has an Inline ...

i.e. If we remove the primary_key there do we still have a reproduce/regression test for the original issue? 🧐
It might be that we just need to add the new models. (Thought: It seems like there's a lot of them… surely one of 'em would work — but perhaps not. 😀 — Don't spend forever here!)

This was the best I could come up with on the existing models, but I'll have another look. It's a good call on changing the model. My observation & learning here is that I need to be really aware of the knock-on impact of changes, and the work it causes for others. That is, the ROI of checking the impact of a model change is likely not worth it vs 'just' adding another model if there isn't a straight forward solution.

buildbot, test on selenium.

Ok -- I think this is ready for another review. I couldn't find a suitable model that exists so I've reverted to the standalone models, and stripped them back to the must have items only. I've also updated the tests, I hope these are slightly more readable while still maintaining a similar level of test coverage.

buildbot, test on selenium.

buildbot, test on selenium.

@smithdc1 @carltongibson  Added tests crash in the headless mode:
Traceback (most recent call last):
  File "/home/jenkins/workspace/django-selenium/database/sqlite3/label/bionic/python/python3.9/tests/admin_inlines/tests.py", line 1382, in test_inlines_verbose_name
    self.assertEqual(chosen.text, 'CHOSEN ATTENDANT')
AssertionError: '' != 'CHOSEN ATTENDANT'
+ CHOSEN ATTENDANT

It's probably a separate CSS issue on small screens (800px), see screenshots:

headless:

"normal":

Looks like a regression following the introduction of the sidebar.
I'll write up more complete notes into a new ticket later (I'm not sure what a fix would look like) and submit a patch to fix the current failing test.
I'm also really not sure what I missed here, I thought I had seen the selenium tests passing? What did I get wrong here?

I'll write up more complete notes into a new ticket later (I'm not sure what a fix would look like) and submit a patch to fix the current failing test.

Thanks :+1:

I'm also really not sure what I missed here, I thought I had seen the selenium tests passing? What did I get wrong here?

Nothing. We run selenium tests in headless mode only in the main build (see django-selenium) not for every PR (see pull-requests-selenium).


TST: pin numba for Travis/sparse

Should address 1 of the 2 CI failures outlined in #11460

the pydata/sparse master branch only
requires numba>=0.45, so let's pin
to numba==0.45 to avoid bleeding
edge numba's NumPy version requirements
that are causing Travis CI failures

cc @hameerabbasi
Hopefully pip doesn't try to upgrade numba if the base requirement for pydata/sparse is set from a previous install---I believe that is the normal behavior, but CI will tell us soon enough...

Would a point release with >= 0.45 help?

CI is using sparse-0.9.1, which it seems already has >= 0.45. I just meant that in the worst possible case if we did pull in the master branch the pin would still be valid. If you bump the minimum  at some point in the future we can deal with that when it happens I think?

@hameerabbasi numba failures look real---how confident are we that 0.45 is sufficient for pydata/sparse + SciPy master + other things pinned?

A similar error was recently reported in numba: https://github.com/numba/numba/issues/3932
It looks like @stuartarchibald never had access to reproducer there. Perhaps they will have a suggestion---perhaps 0.45 is too old, but we can use something not-quite bleeding edge for now so that the NumPy requirement isn't too new.

I see, NumPy 1.18 requires Numba 0.46. I'll update that in master.

Trying numba 0.46 now

Failed for same reason, now 0.47

CI is all green for the first time in quite a while, so self-merging simple/single-line testing adjustment here.

@tylerjereddy @hameerabbasi if Numba is at fault here/if there are any problems with Numba please could you open ticket(s) on the issue tracker https://github.com/numba/numba/issues, many thanks.
@tylerjereddy please could you point me to the error that looks like https://github.com/numba/numba/issues/3932 ? This is a known bug, for which we now have two potential fixes but both need a fundamental Numba intermediate representation change. I'd like to make sure that you aren't seeing something new :) Thanks!

Found the versioning related problem build logs... e.g. https://github.com/scipy/scipy/pull/11459 with https://travis-ci.org/scipy/scipy/jobs/645156696#L1237, is from Numba dropping support for NumPy < 1.15 in Numba versions >= 0.48. https://groups.google.com/a/continuum.io/forum/#!topic/numba-users/FkgzhvAA4lU


Allow to accept sync function for PlainOption/orElseAsync

We close this once by https://github.com/option-t/option-t/issues/1683#issuecomment-1456004819.
We'll reopen this when we conclude about #1683.
If you have some opinions, please comment to #1683


python3Packages.rasterio: 1.1.5 → 1.2.6

Motivation for this change
Changelog
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 123589 at debff1d0 run on aarch64-linux 1

2 packages failed to build:

python38Packages.rasterio
python39Packages.rasterio

1 suggestion:

warning: unused-argument
Unused argument: packaging.
Near pkgs/development/python-modules/rasterio/default.nix:4:22:
  |
4 | , pytest, pytestcov, packaging, hypothesis, boto3
  |                      ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

@GrahamcOfBorg build python38Packages.rasterio

Updated in #128806


[in-process] Enabling lld in-process

Reasons:

[#19] "Using statically linked lld leads to segmentation fault" is fixed by rL314108
Testing is done: ocl conformance 1.2

Change rL314108 with a fix in lld just arrived, corresponding changes in make files are in place. Tested on both builds: internal and open source.


UofT-DSI | Algorithms and Data Structures - Assignment 2

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

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

A2 complete


SqsTemplate receiving messages but @SQSListener not on Spring Boot 3.1.5

Type: Bug
Component: SQS

Describe the bug
When using Spring Boot 3.1.5 alongside spring-cloud-aws-starter-sqs 3.0.2 and Spring Cloud 2022.0.4, I can pull messages from SQS using SqsTemplate, but not passively receive them when applying @SQSListener to a groovy 4.0.15 method
Sample
------Bean configs--------
@Configuration(proxyBeanMethods = false)
@Slf4j
class Config{
    @Bean
    @Primary
    SqsAsyncClient sqsAsyncClient() {
        return SqsAsyncClient
                .builder()
                .credentialsProvider(DefaultCredentialsProvider.create())
                .region(Region.of("us-east-1"))
                .build()
    }

    @Bean
    SqsMessageListenerContainerFactory<Object> defaultSqsListenerContainerFactory(SqsAsyncClient sqsAsyncClient) {
        return SqsMessageListenerContainerFactory
                .builder()
                .sqsAsyncClient(sqsAsyncClient)
                .configure {
                    it
                            .acknowledgementMode(AcknowledgementMode.ON_SUCCESS)
                }
                .build()
    }

    @Bean
    SqsAsyncOperations template(SqsAsyncClient sqsAsyncClient) {
        return SqsTemplate.newAsyncTemplate(sqsAsyncClient)
    }
}

------ListenedMethod-------
@Component
@RefreshScope
class QueueListener {
    @SqsListener(queueNames = ['queueName'])
    void receiveMessage(MyPojo message) {
        log.info("message from queue: $message")
    }
}

------Working sqsTemplate Usage-------
@RestController
class TestController {

    @Autowired
    SqsAsyncOperations template

    @GetMapping(path = "/test")
    ResponseEntity pull() {
        Optional<Message<MyPojo>> result = template.receiveAsync("queueName", MyPojo).get()
        return ResponseEntity.ok(result)
    }
}

Thanks beforehand!

@jsierra-dyna can you publish complete project that reproduces this problem? It may be a version problem, configuration problem, Groovy problem and I don't think i'll come up with exactly the same setup as yours

@maciejwalkowiak  Thank you for your prompt answer!
You can see a project that reproduces what is described here.
https://github.com/jsierra-dyna/TestListener
Thanks again!

Upon further inspection, this was a problem caused by a misconfiguration on my side, so I am closing this issue.


Font Request: Geist Sans/Mono Variable

Font Name

Geist Sans Variable
Geist Mono Variable

Link to font source
https://github.com/vercel/geist-font
Link to font license
https://github.com/vercel/geist-font/blob/main/LICENSE.txt
Additional context
Geist Sans/Mono currently only available in non-variable version, while variable version does exist.

We currently don't support the manual addition of variable fonts. We'll need to wait for the addition of Geist via Google Fonts (https://github.com/google/fonts/issues/6922) for the variable variants to be uploaded.


Fix/refactor to use clouscraper

This PR changes the calls made from the exloit classes from using requests to cloudscraper.
This PR also adds a single session initialization per exploit instead of every method.

This PR changes the calls made from the exloit classes from using requests to cloudscraper.

Can u pls explain the purpose of the change ?

Needs a MUCH better description to review the PR @ErebusZ .