[2.0] Migrate user models to the new app

NOTE: Must merge #1339 SEPARATELY before this PR so that migrations work correctly!
🛠 Changelog

See title.
Old migrations will remain in place until everything is moved to not break the django migration system.
Should follow this guide (the short way).
Note: User migrations must come before all other migrations so that migration dependencies can be put in the correct order.

🧪 Test plan

Automated tests

🚧 Dependencies

None

🎫 Tickets

TILA-3547

Merged #1341, #1342, #1343, #1344, #1345, #1346, #1347, #1348, #1363, #1364, #1365, #1367 & #1369 to this PR so that they can be merged to main together.

/ff


Mac OS X support for the Python interface

I've made the following changes:

Argument lists for most calls were set in a "argtype" attribute which
is wrong. The correct attribute name is "argtypes".
Added support to load the Mac OS X dynamic library.
Modified the Python 3 version of the library to also be compatible
with Python 2, so that a single file can be used on both.

"argtype" wrong? I understood it was automaticly detected. Anyway it is better to be explicit.
Great!
So if I replace MediaInfoDLL.py by MediaInfoDLL3.py and HowToUse_Dll.py by HowToUse_Dll3.py, it is OK (both Python 2 and Python 3 can use any of the files), without regression, right? I tested myself but I prefer to be sure I do nothing wrong.

"argtype" wrong? I understood it was automaticly detected. Anyway it is better to be explicit.

Yeah, on the Mac "argtype" does not give any errors, but ctypes ignores it and goes with the default of all arguments being 32-bit ints. Things fail pretty epicly :)

So if I replace MediaInfoDLL.py by MediaInfoDLL3.py and HowToUse_Dll.py by HowToUse_Dll3.py

Yes, that was my intention. I did not remove the Python 2 version to not break people that is already using it (such as the python-mediainfodll ubuntu pkg), but you can now use the version 3 code on both versions of Python.
Thanks for the prompt handling!

Things fail pretty epicly.

Ouch. Weird that it works well on Linux and Window.
hum... actually, doing the diff of MediaInfoDLL.py and MediaInfoDLL3.py, I see a comment:
"#We should use -1 the same way, but it fails on 64-bit"
so it was working but not so well :).

I did not remove the Python 2 version to not break people that is already using it

The issue is definitely legacy programs, I don't see how I could avoid to keep duplicate content.
Please review https://github.com/MediaArea/MediaInfoLib/pull/49, is it OK from your point of view? (I tested on Windows but I prefer someone else double-checks)


Camera properties

The default camera does not appear in the object browser.

Hi @user1713952
The default camera is actually not edittable and its added on initialization only if there is none available on the project.
I migth add a default camera to the default scene teplate, would this be better?
Cumps

I was thinking that this could help also for the case of the 2D mode referenced here. It is very convenient to have access to all the elements of the scene from the browser


Added support for deleting values within keys

Coverage decreased (-0.5%) to 73.256% when pulling a309d09ac3cf1b73ecfb733dcaa912cc2b432434 on delvalue into b6b5788d0b53934b979b24942506ed4d805fe020 on master.


Do plugin work on activation, only defer adding endpoint until after_initialize

In trying to get the redirect endpoint to register successfully, I moved everything in the plugin to after_initialize.  This doesn't work, since plugin#activate! expects all resources like scripts, styles and auth_providers to be registered synchronously.  This fixes that up so that only the endpoint is deferred.

selfie, tested manually


Add py310

Add python 3.10
Remove python 3.7 (dask no longer supports it, and hasn't for the last six months)
Remove development.coiledhq.com
Bump the coiled-runtime version

Supersedes #56

I suspect this isn't what we want but we should follow up tomorrow.

more context at https://gitlab.com/coiled/cloud/-/issues/4990#note_1012030497

I will close this after what we talked in the soft-env meeting, for a summary see https://github.com/coiled/oss-engineering/issues/127#issuecomment-1171633431


Refreshing JWT (/jwt-refresh) does not give the user up to date (email, username ...)

Order of the steps to do :
Update the user [PUT] :

Query http://localhost:4000/users/1
JSON : {"id":1,"email":"mail@mail.tld","username":"test2"}
Headers : Authorization Bearer token

Generate and get a  New token : [POST]

Query http://localhost:4000/jwt-refresh
JSON : {"refresh_token":"1_227_EMeqEytKmCcGX_RQWfeQb0V9IY_w43viaXCcTNZOeKg"}
Headers : Authorization Bearer token

Problem
the user object contained in the PAYLOAD access_token is not up to date

In fact, I was able to reproduce this issue.
This happens beceause the funcion set_jwt_token defined in /app/misc/rodauth_main.rb is not called.


CSV field header: uniprot_id instead of uniprot_accession_number

@tvwillem  @bmesuere For consistency with the field header taxon_id I would recommend to rename the CSV field header uniprot_accession_number as uniprot_id. I guess this could also imply that later on the corresponding database column headers and names returned in the output of the web services might need to be replaced.
I already made use of the name unipept_id in the text I'm currently compiling for Toon's thesis, in which I'm discussing some use cases of the Unipept command line as an illustration on how to use the tools and a kind of benchmark to prove how usefull the API is in practice.
Original issue by @pdawyndt on Sat May 10 2014 at 19:05.
Closed by an unknown user on Sun May 11 2014 at 13:09.

Fixed in bcc8f38
Original comment by ghost on Sun May 11 2014 at 13:09.


improved anticrash + added noexplosion

also fixed gitignore and changed totem pop slightly to improve consistency and added everything to the readme so you dont have to

also fixed gitignore and changed totem pop slightly to improve consistency and added everything to the readme so you dont have to

Hello TaxEvasiqn,
Unfortunately I was able to location some flaws in your changes that may cause the config to not save properly. I will proceed to make these changes myself, but you will be credited!
Thank you for supporting the ClickCrystals community!


Update Readme For Searching Algorithim

Description
want to Add a explanation of Binary search to Readme of searching Algorithm Folder.
Domain
README
Type of Contribution
Addition
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of LearnCPP.

/assign


feat(storage): static files metrics

Similar to database metrics, we now record the following metrics for the snapshot provider: https://github.com/paradigmxyz/reth/blob/77b07b1e2b71e697e96c31d5b4c2007dea222671/crates/storage/provider/src/providers/snapshot/metrics.rs#L59-L66

test failure unrelated, it's a timeout -.-


No https - [closed]

In GitLab by @erdzan on May 14, 2020, 19:27
Merges noHttps -> master

In GitLab by @erdzan on May 14, 2020, 19:27
closed


$client->createAuthUrl() - append delegation=1

I try to generate login URL with this api client. I want to create application with Laravel with login by Branding Account.
`
$client = new Google_Client();
$client->setDeveloperKey("DEV_KEY");
$client->setClientId('CLIENTID');
$client->setScopes(array(
'https://www.googleapis.com/auth/plus.me',
'https://www.googleapis.com/auth/plus.login'
));
$client->setRedirectUri(route('google-callback')); // TODO

$auth_url = $client->createAuthUrl().'&delegation=1'; //OOOOOO here
return \Illuminate\Support\Facades\Redirect::to($auth_url);

`
But when i add delegation = 1, redirect to auth_url remove this parametr :/
What now? Can i Add it manualy? Or maybe it error in my Google App configuration (google + api is enabled)

This issue may no longer be relevant due to its age. If that is not the case let us know and we will re-open.


Nodes appear in pallette of a CE licensed install

Current Behavior
The Link Nodes appear in the pallette for projects using the new stack on a CE licensed platfrom.
This means that they can be added to the flow but when deployed this throws an error, because the node has not been registered in the runtime due to this check https://github.com/flowforge/flowforge-nr-project-nodes/blob/main/nodes/project-link.js#L4
The correct warning is shown in the node-red startup log:
09/08/2022 11:49:43 [warn] Project Link nodes require flowforge settings
However there is no such check to control the  RED.nodes.registerType` call in the html file
The nodes themselves are not functional and you cannot get the list of projects
Expected Behavior
Nodes should not appear in the palette
Steps To Reproduce
Deploy a new project in a CE licensed platform,
Environment

FlowForge version: 0.8.0
Node.js version: 16.16.0

Ah I missed this in the review. The code you link to should be throwing an error, not just logging one. Otherwise the runtime doesn't know there's a problem and allows the HTML to still be loaded into the editor.

Ah so if the js throws an error then  that will prevent the html from being parsed?

if the js throws an error then that will prevent the html from being parsed?

Correct


Migrate to new Image Entity

Is your feature request related to a problem? Please describe.
Home-Assistant 2023.7 added support for Image Entity...
https://www.home-assistant.io/blog/2023/07/05/release-20237/#image-entities
Describe the solution you'd like
Migrate from Camera entity to image entitty. Hopefully this will reduce complexity and allow for new cooler features going forward.

I looked into this, the main issue here is that the call to retrieve the image is not provided with the contextual dimensions. This would basically force the integration to always give back the highest resolution image without any cropping possibilities.  Also if I every get to implementing the retrieval of videos, this would probably not work with the image entity.
All in all, only downsides at the moment, but willing to revisit this once there is an nice use case.


Introduce 2.13

drop support for 2.10
introduce sbt-1.3.0-RC2

Related: https://github.com/dmurvihill/courier/issues/48

Any reason we can't leave 2.10 support in? I'm all for dropping 2.10 if it makes something easier for us but otherwise I'd rather not make a breaking change

get rid of a maintenance burden (keep the build working for 3 versions), compatibility in source code, etc.

Why SBT 1.3.0-RC2 as opposed to 1.3.3 or 1.4.0?

I'm not aware of those versions, to me, the most recent sbt version is 1.3.0-RC2

I thought about the 2.10 support and I still think that now is a great time to drop it. Publishing to Sonatype got better but it still a pain to publish multiple artifacts.
Furthermore, it's our only way as a community to move forward. If we keep maintaining old versions, people/compagnies won't see the need to move over. At this point, there should be absolutely no reason one can't move from 2.10 to something more recent.
If you want, you can review that again, I will merge and publish a release candidate by the end of the day if you haven't.


Terraform Bug (Variable scope writing)

Look at the terraform container work out if its better to rewrite slightly to handle variables properly. Sidecar logic allows names with dashes but regex checker does not.

this is resolved now


[Accordion Menu] not tabbable/keyboard navigatable

How can we reproduce this bug?

Tab through webpage tab sequence
focus will hit first item of accordian-menu, at which point, tab (and backwards tab/alt+tab) no longer work.
left/right arrow keys will open and close that first level item dropdown, however up/down arrows do not work, so keyboard can never access the submenu items, by either up/down or tab

What did you expect to happen?
functionality of keyboard should match the standard accordian. Aka, tab sequence should not be interrupted, and tab key should continue to navigate to the (other) visible links/focus points. up/down arrows should also enable user to navigate the menu items, in same manner that a user an do so in standard accordian.
Test case
http://foundation.zurb.com/sites/docs/accordion-menu.html
http://foundation.zurb.com/sites/docs/accordion.html

I will have  a look.

is the referenced issue claiming to fix this issue too? any idea when it might roll out?


Image transformation not working

Description
I'm trying to apply an image transformation (RoundedTransformation) but the resulting image is always square, even with a radius of 50.
Steps to Reproduce
Create a project using the templates available from Microsoft.
Add the nuget to the three projects (shared, iOS, Android).
Add this line before the Forms.Init(), at least for Android:
FFImageLoading.Forms.Platform.CachedImageRenderer.Init(true);
<f:CachedImage Aspect="AspectFill" DownsampleToViewSize="True" Source="{Binding ImageSource}" BitmapOptimizations="True" CacheType="Disk">
    <f:CachedImage.Transformations>
        <t:RoundedTransformation Radius="50"/>
    </f:CachedImage.Transformations>
</f:CachedImage>

This is inside a Sharpnado's HorizontalListView and DraggableViewCell. Also there's a custom frame with rounded corners as the parent of the image.
Expected Behavior
The image corners should be rounded.
Actual Behavior
Image loads with squared corners.
Basic Information

Version with issue: <IP_ADDRESS>2
Last known good version: n/a
Platform: Android

Screenshots
Screenshot

Check RoundedTransformation's WidthRatio / HeightRatio properties. Eg. specify 2:1

I'm sorry for taking so long to reply. I noticed that when using the Aspect="AspectFill", the image wont have its corner radius set.
Only when using the Aspect="AspectFit" that the corner radius will be respected.
I'm not sure if I'm doing something wrong. Would you mind taking a look at this sample project?
https://github.com/NickeManarin/Xamarin.Demos2
(Click on the button Test and later in Continue)
Currently is set to Aspect="AspectFit", but if changed to Aspect="AspectFill".
Also I noticed that when using AspectFit, the image looks kind of cropped, even if there's no crop transformation applied to.
I'm not sure if it's an issue with the CrossMedia captured image, the CachedImage element or anything else.

Hi, did you managed to take a look at the project?

Check RoundedTransformation's WidthRatio / HeightRatio properties. Eg. specify 2:1

Why we have to set those values? We just want to make rounded image :)
P.S. I've faced same issue - image transformation doesn't working :(


refactor admin module with mobx

Coverage remained the same at 87.662% when pulling 8baebd711e3fd9d229f168ba5fc64045eb46d9c3 on f237-mobx-users into a16812b03d2290abb5ee88f48e81b9785d1fc48b on master.


Enable let's encrypt certs

Hello,
Maybe I am completely missing something, but I can't seem to find any documentation on how to set up the dashboard container using the dockerfile to use  let's encrypt certificates.
Is this an implemented feature? If not, is it on the roadmap?
Thanks!

Hello!
This is only front-end source, which is not intended for deploying it in docker.
You can use https://github.com/markFieldman/open-balena-dashboard-backend for deploy self hosted server with proxying requests to your cloud.


DSI -Shell Assignment 1 completed

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
i used different shell script on the shell as cp, mkdir, ls  in order to comply with assignment
What did you learn from the changes you have made?
after a few tries I learned how to properly use this arguments in the shell script  to make the appropriate changes required
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
i thought of using just Gitbash, but visual code was the better option as it gave me a more neat view of my code
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
I had to tried several times the script and after few errors, the code i was using finally worked
How were these changes tested?
using the bash and change the script accordingly until it gave me the results required. I also tested the script on a separate directory to run the code and it worked properly
A reference to a related issue in your repository (if applicable)
Checklist

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

perfect!


[Workspace] Diagnose basename mismatch when overriding

... using local packages
rdar://problem/52263385 [SR-11032]: Package resolution fails when replacing remote dependency with local dependency
(cherry picked from commit d9c76ac0ab0b3a39dcd63ce4984be3b6e412545c)

@swift-ci smoke test


update image and mainApplicationFile

there is no a suitable image with tag "v2.4.5-gcs-prometheus"  in the registry gcr.io/spark-operator/spark
There is one suitable image with tag "v2.4.5-SNAPSHOT-gcs-prometheus". This image contains a jar file "/opt/spark/examples/jars/spark-examples_2.11-2.4.5-SNAPSHOT.jar" and the  file from yaml doesn't exist.
Set properly image and mainApplicationFile parameters.
Other solution might be change the image - tag name and jar file.

I'm gonna update the image.

Just pushed image gcr.io/spark-operator/spark:v2.4.5-gcs-prometheus.


Update tagline

Task/Issue URL: https://app.asana.com/0/1200204095367872/1208412577276170/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#5089  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @joshliebe and the rest of your teammates on  Graphite


Add support for pulling a docker image from a private docker registry

Description:
It would be great to have the feature which enables pulling the docker image from a private Docker registry.
https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

+1

Image pull secrets can be specified as
@kubernetes:Deployment{
imagePullSecrets: ["mysecret1","mysecret2"]
}


Cover Convertible RIs

https://aws.amazon.com/about-aws/whats-new/2016/09/amazon-ec2-convertible-reserved-instances-and-the-reserved-instance-regional-benefit/

In progress #132


@linkcode and @linkplain are not autocompleted in jsdoc comments

Does this issue occur when all extensions are disabled?: Yes

Version: 1.74.2
Commit: e8a3071ea4344d9d48ef8a4df2c097372b0c5161
Date: 2022-12-20T10:25:18.196Z
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Steps to Reproduce:

Create a new JavaScript file
Type the following:

/**
 * See {@li}
 */

Press ctrl + space to autocomplete while typing @li

For reference, I'm coming from https://github.com/microsoft/TypeScript/issues/52171

Ah, I was wrong about where that snippet comes from.
Easy PR to src/services/jsDoc.ts to add those to the jsDocTagNames list

Thanks! On it :)

Thanks @jespertheend!


Redis adapter

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

409 of 419 (97.61%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.7%) to 94.141%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

redis/transaction.go
78
79
98.73%

redis/settings.go
77
80
96.25%

redis/context.go
12
18
66.67%

Totals

Change from base Build<PHONE_NUMBER>:
1.7%

Covered Lines:
1205

Relevant Lines:
1280

💛  - Coveralls


Update "Hello Node.js" codelab to work well with Cloud Shell.

I walked through the codelab in Google Cloud Shell, there was a couple of things that didn't go smooth, so I'm improving the content here. Also add using --zone argument to two cluster commands, that's not Cloud Shell specific but just generally useful.

Awesome thanks!


feat: DEV chain spec

adds DEV as an optional chain spec to the cli's node command
closes #1280

Think this is not in scope right now. Will close for now and we can reinvestigate in the future what the config for a dev chain would be.


Avoid confusing network engineers

Make it unambiguous if the test is using IPv4 or IPv6.  Many engineers have baked in assumptions that are wrong for IPv6.   (This also requires client changes).

My understanding is that, if we're using IPv6, at least one of the two endpoints should be IPv6. It may be that the client is into an IPv4 cloud, the server is also into an IPv4 cloud, and that the two clouds are communicating via IPv6 using tunnelling, but I don't know how to address this case. Does my reasoning make sense, @mattmathis, or am I missing something?

I understand. I believe this is, in a way, more a UI issue though. Since, as you say, it's possible to infer whether it's v4 or v6, I believe we don't need to change the message we transfer but, rather, we just need to make sure that the client adds the v4/v6 information when required. Does it make sense?

So you would like "address family" to be a top-level attribute in the results instead of part of the (joinable) tcp-info dataset? Like min RTT and avg throughput are currently?

@mattmathis can you check whether the current data format looks good to you?

This issue refers to an old client that was embedded in the server.   Has been removed.


Is this project abandoned?

It seems that there is no commits for over a year. And no response to issues.
Is this project still living?
Can we use it on our recent project?

Let's call it "dormant". Probably after Scala 2.12 is out there will be some more activity. We'd be happy to help contributors though. You can give it a try on your project already, but you'd need to built it yourself.

Probably it just needs a much better name. Something sexier than wart but which echoes its provenance. "libido"? A neologism would be "abido".

By looking at the commit history it looks like the project has been revived. Indeed the 2.12 release looks like it was a turning point.

If everyone is just waiting around for Lightbend to do all the work on this, well, that might not happen. If there's anyone out there who wants to help respond to issues, review pull requests, be a maintainer, etc, please do. The lights are back on, now, certainly.
Competition is also welcome. Abide is partly a real project and partly just an idea and a demonstration of what Adriaan thinks the right approach for writing a semantically aware Scala linter is. (Namely, a plugin that runs after typer.)

The lights are back on, anyway.
If anyone is waiting for Lightbend to do all the work needed to make Abide into the premier Scala linter, that might not happen. Hopefully a community will form around this repo? Community participation is welcome with responding to issues, reviewing PRs, and so on.

new thread on this: https://contributors.scala-lang.org/t/whats-the-status-of-abide/609

So the new answer is, "It is now."

Reading the thread pointed out by Seth, it looks to me that Abide and ScalaFix aim two very different aims, despite their guts may look similar:

Abide aims warning/stopping/whatever compilation when undesirable code constructs are found;
Scalafix aims to transform acceptable 2.11 code into acceptable 2.12 and beyond.

From the perspective of someone willing to find undesirable code, ScalaFix looks like a tool which transform old undesirable code into brand new and shinny undesirable code.
From the list of "Rewrites" in the ScalaFix documentation... even from the list of planned "Rewrites"... I don't see a one which could be understood like...

As a developer, I want to get a compilation error when I've written code which does not conform to architectural patterns defined by group XYZ.

I think this is important. Big projects may define stringent rules which enforces the code to comply to certain architectural patterns. At this point in time, someone is not really interested on converting old code into new code... this may happen later... true!... but that person is only interested on getting compilation errors when the code does not follow the architectural patterns.
Thougths?

Scalafix aims to transform [...] code

I'm suggesting broadening Scalafix's aims.

I'd like a tool that transforms ichoran code into tpolecat code and back.

Scalafix has taken up the linting cause: http://scala-lang.org/blog/2017/09/11/scalafix-v0.5.html


Setup GA for the repo

Goals:

GitHub Action to do an automated check on every PR raised
Check would be of test cases, ESLint, Accessibility check (NPM packages)
Check on the Lighthouse score
GitHub Actions (GA) would execute on:

against every Pull request (PR)
before merging to Develop branch
before merging to the Main branch

Resources::
https://docs.github.com/en/actions/guides


Missing Code of Conduct File in Repository

Currently, the repository lacks a Code of Conduct file, which is an essential component for fostering a healthy and inclusive open-source community. A Code of Conduct serves as a guideline for expected behavior, ensuring that contributors and participants feel safe, respected, and valued within our community space.
Kindly assign me this issue, so i can work towards it under GSSOC 24

Already added
Feel free to create new issues and do the contribution


WIP: init graphql support

not like #12285 use gqlgen as frame
add two operations as init
query: viewer
mutation: createRepository

Up ? Do you need some help for this PR ?
I'm waiting a lot the support for GraphQL.
It is game changer.

Is it feasible for current Gitea code base?


All Python functions are annotated

Why?
This feature can have several benefits:

This will speed up pytype.
This will make typing less loose.

How?

Install pip install monkeytype, but do not add it to pyproject.toml. We'll use monkeytype to just generate types.
Install pip install flake8-annotations and add it to pyproject.toml in the [dev] section.
In the Makefile, change pyflakes . --disallow-untyped-defs.

Will this need to be assigned to an individual, or can I take a stab at it and make PR?

@Milksheyke Please, feel free to send a PR :) Thanks!

Installed repo and dev tools, but I'm unable to generate the database with monkeytype. At least not fully.
croissant/python/mlcroissant/mlcroissant/_src/operation_graph/execute.py", line 98, in build_record_set
    len(result) == 1
AssertionError: "GroupRecordSet(default)" should have one and only one predecessor. Got: 0.

execute_operations_in_streaming in mlcroissant/_src/operation_graph/execute.py is passing in a DiGraph while build_record_set is expecting a MultiDiGraph. I'm guessing that's where the assertion error is coming from.
Am I missing something here, or should we introduce some sort of default behavior to handle if a node lacks a predecessor?


unable to install turicreate in big sur

Big Sur has python 3.8.2 and turicreate kicks an error immediately on pip install:
`(venv) jeff@macbook-pro turicreate % pip install -U turicreate
Collecting turicreate
Using cached turicreate-6.4.tar.gz (1.9 kB)
Using legacy 'setup.py install' for turicreate, since package 'wheel' is not installed.
Installing collected packages: turicreate
Running setup.py install for turicreate ... error
ERROR: Command errored out with exit status 1:
command: /Users/jeff/Desktop/turicreate/venv/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/_l/ly_4c0ws1fvfkgs7ch8tshzc0000gn/T/pip-install-5vkauy_l/turicreate/setup.py'"'"'; file='"'"'/private/var/folders/_l/ly_4c0ws1fvfkgs7ch8tshzc0000gn/T/pip-install-5vkauy_l/turicreate/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /private/var/folders/_l/ly_4c0ws1fvfkgs7ch8tshzc0000gn/T/pip-record-390tkzpk/install-record.txt --single-version-externally-managed --compile --install-headers /Users/jeff/Desktop/turicreate/venv/include/site/python3.8/turicreate
cwd: /private/var/folders/_l/ly_4c0ws1fvfkgs7ch8tshzc0000gn/T/pip-install-5vkauy_l/turicreate/
Complete output (28 lines):
running install
        ==================================================================================
        TURICREATE ERROR

        If you see this message, pip install did not find an available binary package
        for your system.

        Supported Platforms:
            * macOS 10.12+ x86_64.
            * Linux x86_64 (including WSL on Windows 10).

        Support Python Versions:
            * 2.7
            * 3.5
            * 3.6
            * 3.7
            * 3.8

        Another possible cause of this error is an outdated pip version. Try:
            `pip install -U pip`

        ==================================================================================

----------------------------------------

ERROR: Command errored out with exit status 1: /Users/jeff/Desktop/turicreate/venv/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/_l/ly_4c0ws1fvfkgs7ch8tshzc0000gn/T/pip-install-5vkauy_l/turicreate/setup.py'"'"'; file='"'"'/private/var/folders/_l/ly_4c0ws1fvfkgs7ch8tshzc0000gn/T/pip-install-5vkauy_l/turicreate/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /private/var/folders/_l/ly_4c0ws1fvfkgs7ch8tshzc0000gn/T/pip-record-390tkzpk/install-record.txt --single-version-externally-managed --compile --install-headers /Users/jeff/Desktop/turicreate/venv/include/site/python3.8/turicreate Check the logs for full command output.`

This is a Python packaging issue: pypa/packaging#318. This issue should be resolved soon; there is a pull request to resolve the issue.
Let me know if you have any questions. I'll leave this issue open until the Python packaging issue is resolved.

I believe this has now been fixed in pypa.

Thanks @timmead. You're right this is now fixed.


Scaleset create_or_update doesn't include protected settings object

ext = VirtualMachineScaleSetExtension(...protected_settings=protected_settings...)
vmss.virtual_machine_profile.extension_profile.extensions.append(ext)
client.virtual_machine_scale_sets.create_or_update(resource_group_name, vmss_name, vmss)
Expected: vmss extension has its protected settings saved
Actual: protected settings are empty
Note: the extension is successfully added, but the protected settings are missing

Hi,
Not sure I get it, where are the protected settings missing? in the create_or_update return object?

It was missing from the return object, which I think is actually by design.  Our issue looks to be further upstream, so I will look to the service teams to resolve this issue instead.  Sorry for the false alarm.

No problem :)


Add LLVM assembly and TableGen definitions

Did the best I could with an ASCII interpretation of the LLVM wyvern.

I'm genuinely impressed.


Problem to read specific number using maatwebsite excel lib

I have a one excel sheet has one column with number format. and In that, I have facing the problem to read specific 0.56 number using maatwebsite excel. I am getting 0.5600000000000001 instead of 0.56 please help me asap

Thanks for submitting the ticket. Unfortunately the information you provided is incomplete. Before we can pick it up, please check (https://github.com/Maatwebsite/Laravel-Excel/blob/2.1/.github/ISSUE_TEMPLATE.md) and add the missing information.
To make processing of this ticket a lot easier, please make sure to check (https://laravel-excel.maatwebsite.nl/docs/2.1/getting-started/contributing) and double-check if you have filled in the issue template correctly. This will allow us to pick up your ticket more efficiently. Issues that follow the guidelines correctly will get priority over other issues.

How to read the raw cell value instead of the value formatted by excel. for example a value like "29169186239198200" will be formatted to "2.91692E+16".

@nouphaltklm please give us a bit more information (see issue template). Version 2.1 and 3.0 are too different to answer your question.

https://stackoverflow.com/questions/18905002/php-float-precision-inacurracy
Duplicate of #1420


redesign preflight check

What this PR does / why we need it: This PR redesigns the preflight check page.
From dashboard:

From initial install:

Which issue(s) this PR fixes:

Fixes # https://app.shortcut.com/replicated/story/69840/refresh-the-design-of-the-preflights-page-during-initial-install
Special notes for your reviewer:

Steps to reproduce

Does this PR introduce a user-facing change?

Refresh the design of the Preflights page

Does this PR require documentation?

NONE

this looks a lot better


xdg-desktop-portal-wlr: add slurp to the environment

Motivation for this change
fixes #121678
Things done

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

[x] NixOS
[ ] 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.

nixpkgs-review pr 121729

1 package built:
xdg-desktop-portal-wlr


Can't send messages in private threads

Can't send messages in private threads.
Should probably send an error to the user instead.
2023-06-26 21:25:30 INFO    controllers.guess         Sending RevealedEmbed
2023-06-26 21:25:31 ERROR   services.guesser_service  Unhandled exception while calling on_guesser_end_event
Traceback (most recent call last):
  File "/app/src/services/guesser_service.py", line 89, in end_guesser
    await event(guesser)
  File "/app/src/controllers/guess_controller.py", line 338, in on_guess_end
    await guesser.channel.send(embed=embed, file=file)
  File "/usr/local/lib/python3.10/site-packages/discord/abc.py", line 1561, in send
    data = await state.http.send_message(channel.id, params=params)
  File "/usr/local/lib/python3.10/site-packages/discord/http.py", line 738, in request
    raise Forbidden(response, data)
discord.errors.Forbidden: 403 Forbidden (error code: 50001): Missing Access

and private messages too


Support CSV

Why ExcelDataReader read csv need another method

ExcelDataReader read csv all string type defualt

Creating and Editing Services Available for Users in Bulk

CsvHelper
void Main()
{
	var records = new List<Foo>
	{
		new Foo { Id = 1, Name = "one" },
		new Foo { Id = 2, Name = "two" },
	};
	var path =  Path.Combine(Path.GetTempPath(),$"{Guid.NewGuid().ToString()}.csv");
	using (var writer = new StreamWriter(path))
	using (var csv = new CsvWriter(writer, CultureInfo.InvariantCulture))
	{
		csv.WriteRecords(records);
	}
	Console.WriteLine(path);
}

// You can define other methods, fields, classes and namespaces here
public class Foo
{
	public int Id { get; set; }
	public string Name { get; set; }
}

Id,Name
1,one
2,two

LibreOffice Calc

input : 0 & "\"; ,"
ouput : 0,"""; ,"

csvhelper " convert to  """"

System.IO.IOException : The process cannot access the file 'C:\Users\Wei\AppData\Local\Temp\c080ec8e-c38e-4971-be50-8663f312dbf6.csv' because it is being used by another process.

Lazy loading will meet if using stream it'll dipose before lazy loading, so system will show ``


Consider support for HTTP proxy authentication incl windows NTLM

Some CLI users are behind a corporate firewall requiring NTLM authentication. The current workaround for these users to allow connecting to public CloudFoundry instances such as IBM bluemix or pivotal PWS, it to install a local http proxy such as CNTLM which exposes a local http proxy without authentication support.
This has the following drawbacks:

requires a set up task by every CL user
local http proxy such as cntlm are sometimes unreliable and may interfere with CF CLI requests, in particular for high request rates over HTTP persistent connection, see bug 61 as an example

More details about NTLM authentication protocol
https://msdn.microsoft.com/en-us/library/ms789031(v=vs.110).aspx
https://msdn.microsoft.com/en-us/library/dd925287(v=office.12).aspx
This problem is not visible to cf users using UIs since most browsers support ntlm proxy authentication
https://www.chromium.org/developers/design-documents/http-authentication
https://support.mozilla.org/en-US/questions/926378 and detailed docs about network.automatic-ntlm-auth.allow-proxies
http://stackoverflow.com/questions/5541365/configure-ntlm-for-opera-and-safari-and-chrome
Potential fix steps:

add support for http proxy NTLM authentication to use current windows session. See curl -U option for inspiration. This could be enabled through a cf config enable_automatic_ntml_proxy_auth true command
add support for general http proxy authentication by specifying a proxy login/password (e.g. by a refinement of the HTTP_PROXY environment variable in the form of protocol://username:password@host:port/  through a common
http://curl.haxx.se/docs/manpage.html#--proxy-ntlm

Example NTLM go-lang lib https://github.com/ThomsonReutersEikon/go-ntlm
I realize this enhancement suggestion may be too specific to specific user base. Feel free to close the issue if you feel so.
Some background on rationale for some organizations to use NTLM authentication for outgoing internet access http proxies:

some industry sectors / countries have regulations that require to trace external internet traffic back to originated user accounts (e.g. SOX, or EU/FR laws)
some computers can be run by multiple user accounts, so host IP address/mac address is not authentifying user account who triggered outgoing internet traffic
rather than requesting every single users to provide a named login/password in an http proxy basic auth, some orgs rely on microsoft windows current user session to authenticate the user

Hi Guillaume,
I don't think it's too specific, but our backlog is long. We'd welcome a PR!
Regards,
Dies Koper

CLI team

Closing this feature request, priority will be managed in the tracker story (linked above).

CLI team

@gberche-orange thank you very much for reporting this issue and for mentioning the CNTLM workaround, too. Since the issue is still sitting there in Pivotal Tracker I went ahead and figured out how to use CNTLM to work around this issue for now. Thanks again!

Hey @dkoper, we at https://github.com/anynines started working on supporting HTTP proxy with NTLM authorization. We're currently working on a prototype for a customer.
Is there someone from your team we can discuss our PR with in the near future?
Or should we just use the GitHub PR mechanism and then discuss the prototype (naive implementation) how to proceed with the PR so it gets accepted?


Upgrade protobuf to 3.15.0-rc1

This pull request should just be merged but is just for testing.

@jtattermusch Would you mind adding the necessary tags to kick off the tests?

@acozzette There's now some automation around bumping this version. Update this line and then run tools/buildgen/generate_projects.sh.

You'll have to resolve the merge conflicts before the tests will run.

Thanks, @gnossen. I've now fixed the merge conflicts.

Oh sorry I missed your earlier comment, let me try that script.

C++ build error:
In file included from /var/local/git/grpc/third_party/protobuf/src/google/protobuf/any.pb.cc:4:
In file included from /var/local/git/grpc/third_party/protobuf/src/google/protobuf/any.pb.h:30:
/var/local/git/grpc/third_party/protobuf/src/google/protobuf/message.h:234:13: error: constexpr constructor never produces a constant expression [-Winvalid-constexpr]
  constexpr Message() {}
            ^
/var/local/git/grpc/third_party/protobuf/src/google/protobuf/message.h:234:13: note: non-literal type 'google::protobuf::MessageLite' cannot be used in a constant expression
/var/local/git/grpc/third_party/protobuf/src/google/protobuf/any.pb.cc:20:16: error: constexpr constructor never produces a constant expression [-Winvalid-constexpr]
constexpr Any::Any(
               ^
/var/local/git/grpc/third_party/protobuf/src/google/protobuf/any.pb.cc:20:16: note: non-literal type '::google::protobuf::Message' cannot be used in a constant expression
/var/local/git/grpc/third_party/protobuf/src/google/protobuf/any.pb.cc:26:13: error: constexpr constructor never produces a constant expression [-Winvalid-constexpr]
  constexpr AnyDefaultTypeInternal()
            ^
/var/local/git/grpc/third_party/protobuf/src/google/protobuf/any.pb.cc:27:7: note: non-literal type 'google::protobuf::Any' cannot be used in a constant expression
    : _instance(::PROTOBUF_NAMESPACE_ID::internal::ConstantInitialized{}) {}
      ^
[ 12%] Building C object third_party/boringssl-with-bazel/CMakeFiles/crypto.dir/src/crypto/x509/a_digest.c.o
3 errors generated.
third_party/protobuf/CMakeFiles/libprotobuf.dir/build.make:782: recipe for target 'third_party/protobuf/CMakeFiles/libprotobuf.dir/__/src/google/protobuf/any.pb.cc.o' failed
make[3]: *** [third_party/protobuf/CMakeFiles/libprotobuf.dir/__/src/google/protobuf/any.pb.cc.o] Error 1
CMakeFiles/Makefile2:32528: recipe for target 'third_party/protobuf/CMakeFiles/libprotobuf.dir/all' failed
make[2]: *** [third_party/protobuf/CMakeFiles/libprotobuf.dir/all] Error 2

https://source.cloud.google.com/results/invocations/224fef9b-389d-4d35-8834-13b7f8f827a8/targets/github%2Fgrpc%2Ftoplevel_run_tests_invocations%2Frun_tests_c%2B%2B_linux_dbg_native_x64_clang3.6_buildonly/tests

Ruby failure:
https://source.cloud.google.com/results/invocations/4a8f9191-98be-4b49-811c-9fe786e4e8d6/targets/github%2Fgrpc%2Frun_tests%2Fruby_macos_dbg_native%2Ftools%2Frun_tests%2Fhelper_scripts%2Frun_ruby.sh/tests
got echo response: grpc-ruby/1.37.0.dev grpc-c/15.0.0 (osx; chttp2)
  user agent header does not grow when the same channel args hash is used across multiple stubs

Failures:

  1) GRPC::BadStatus to_rpc_status does not raise when decoding a bad proto
     Failure/Error: expect(log_contents).to include "WARN  GRPC : #{error_desc}"

       expected " WARN  GRPC : parse error: to_rpc_status failed\n WARN  GRPC : <Google::Protobuf::ParseError> Error ...n `invoke'\n\t/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/exe/rspec:4:in `<main>'\n" to include "WARN  GRPC : <Google::Protobuf::ParseError> Error occurred during parsing: Invalid wire type"
       Diff:
       @@ -1,34 +1,67 @@
       -WARN  GRPC : <Google::Protobuf::ParseError> Error occurred during parsing: Invalid wire type
       + WARN  GRPC : parse error: to_rpc_status failed
       + WARN  GRPC : <Google::Protobuf::ParseError> Error occurred during parsing
       +	/Volumes/BuildData/tmpfs/src/github/grpc/workspace_ruby_macos_dbg_native/src/ruby/lib/grpc/google_rpc_status_utils.rb:37:in `decode'
       +	/Volumes/BuildData/tmpfs/src/github/grpc/workspace_ruby_macos_dbg_native/src/ruby/lib/grpc/google_rpc_status_utils.rb:37:in `extract_google_rpc_status'
       +	/Volumes/BuildData/tmpfs/src/github/grpc/workspace_ruby_macos_dbg_native/src/ruby/lib/grpc/errors.rb:70:in `to_rpc_status'
       +	/Volumes/BuildData/tmpfs/src/github/grpc/workspace_ruby_macos_dbg_native/src/ruby/spec/errors_spec.rb:130:in `block (3 levels) in <top (required)>'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:262:in `instance_exec'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:262:in `block in run'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:508:in `block in with_around_and_singleton_context_hooks'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:465:in `block in with_around_example_hooks'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/hooks.rb:486:in `block in run'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/hooks.rb:624:in `run_around_example_hooks_for'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/hooks.rb:486:in `run'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:465:in `with_around_example_hooks'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:508:in `with_around_and_singleton_context_hooks'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:259:in `run'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:644:in `block in run_examples'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:640:in `map'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:640:in `run_examples'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:606:in `run'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:607:in `block in run'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:607:in `map'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:607:in `run'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:121:in `block (3 levels) in run_specs'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:121:in `map'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:121:in `block (2 levels) in run_specs'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/configuration.rb:2067:in `with_suite_hooks'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:116:in `block in run_specs'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/reporter.rb:74:in `report'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:115:in `run_specs'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:89:in `run'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:71:in `run'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:45:in `invoke'
       +	/Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/exe/rspec:4:in `<main>'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-support-3.10.2/lib/rspec/support.rb:102:in `block in <module:Support>'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-support-3.10.2/lib/rspec/support.rb:111:in `notify_failure'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-expectations-3.10.1/lib/rspec/expectations/fail_with.rb:35:in `fail_with'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-expectations-3.10.1/lib/rspec/expectations/handler.rb:38:in `handle_failure'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-expectations-3.10.1/lib/rspec/expectations/handler.rb:56:in `block in handle_matcher'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-expectations-3.10.1/lib/rspec/expectations/handler.rb:27:in `with_matcher'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-expectations-3.10.1/lib/rspec/expectations/handler.rb:48:in `handle_matcher'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-expectations-3.10.1/lib/rspec/expectations/expectation_target.rb:65:in `to'
     # ./src/ruby/spec/errors_spec.rb:139:in `block (3 levels) in <top (required)>'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:262:in `instance_exec'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:262:in `block in run'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:508:in `block in with_around_and_singleton_context_hooks'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:465:in `block in with_around_example_hooks'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/hooks.rb:486:in `block in run'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/hooks.rb:624:in `run_around_example_hooks_for'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/hooks.rb:486:in `run'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:465:in `with_around_example_hooks'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:508:in `with_around_and_singleton_context_hooks'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:259:in `run'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:644:in `block in run_examples'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:640:in `map'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:640:in `run_examples'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:606:in `run'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:607:in `block in run'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:607:in `map'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:607:in `run'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:121:in `block (3 levels) in run_specs'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:121:in `map'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:121:in `block (2 levels) in run_specs'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/configuration.rb:2067:in `with_suite_hooks'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:116:in `block in run_specs'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/reporter.rb:74:in `report'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:115:in `run_specs'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:89:in `run'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:71:in `run'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:45:in `invoke'
     # /Users/kbuilder/.rvm/gems/ruby-2.5.0/gems/rspec-core-3.10.1/exe/rspec:4:in `<main>'

Finished in 2.08 seconds (files took 0.49395 seconds to load)

python on windows:
C:\tools\msys64_win7\mingw64\bin\gcc.exe -mdll -O -Wall -DWIN32_LEAN_AND_MEAN=1 -DMS_WIN64=1 -I. -Igrpc_root -Igrpc_root\include -Ithird_party\protobuf\src -IC:\Python27\include -IC:\Python27\PC -c third_party\protobuf\src\google\protobuf\compiler\java\java_extension_lite.cc -o build\temp.win-amd64-2.7\Release\third_party\protobuf\src\google\protobuf\compiler\java\java_extension_lite.o -std=c++11 -D_ftime=_ftime64 -D_timeb=__timeb64 -D_hypot=hypot
In file included from third_party\protobuf\src/google/protobuf/descriptor.pb.h:23:0,
                 from third_party\protobuf\src\google\protobuf\compiler\js\js_generator.cc:36:
third_party\protobuf\src/google/protobuf/io/coded_stream.h:137:37: fatal error: endian.h: No such file or directory
 #include <endian.h>  // __BYTE_ORDER
                                     ^
compilation terminated.

objc:
/Volumes/BuildData/tmpfs/src/github/grpc/workspace_objc_macos_opt_native/test/cpp/ios/Pods/Target\ Support\ Files/RemoteTestCpp/RemoteTestCpp-prefix.pch -MMD -MT dependencies -MF /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fzhnkppkkmzsbwgphcrtztwjhxny/Build/Intermediates.noindex/Pods.build/Cronet-iphonesimulator/RemoteTestCpp.build/Objects-normal/x86_64/simple_messages.grpc.pb.d --serialize-diagnostics /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fzhnkppkkmzsbwgphcrtztwjhxny/Build/Intermediates.noindex/Pods.build/Cronet-iphonesimulator/RemoteTestCpp.build/Objects-normal/x86_64/simple_messages.grpc.pb.dia -c /Volumes/BuildData/tmpfs/src/github/grpTesting failed:
	This file was generated by a newer version of protoc which is
	Incompatible with your Protocol Buffer headers. Please update
	Your headers.
	Unknown type name 'PROTOBUF_PRAGMA_INIT_SEG'
	Expected unqualified-id
	No matching constructor for initialization of '::google::protobuf::internal::ArenaStringPtr'
	Constexpr constructor must initialize all members
	No matching constructor for initialization of 'grpc::testing::StringValue'
	Constexpr constructor must initialize all members
	No matching constructor for initialization of 'grpc::testing::StringValueDefaultTypeInternal'
	Cannot initialize a member subobject of type 'const char *' with an rvalue of type 'int'
	Cannot initialize a member subobject of type 'int' with an lvalue of type 'const char [45]'
	Cannot initialize a member subobject of type 'int' with an lvalue of type 'const ::google::protobuf::internal::MigrationSchema [3]'
	Cannot initialize a member subobject of type 'const google::protobuf::internal::MigrationSchema *' with an lvalue of type 'const ::google::protobuf::Message *const []'
	Cannot initialize a member subobject of type 'const google::protobuf::Message *const *' with an lvalue of type 'const ::google::protobuf::uint32 [16]'
	Cannot initialize a member subobject of type 'const google::protobuf::uint32 *' (aka 'const unsigned int *') with an lvalue of type '::google::protobuf::Metadata [3]'
	Cannot initialize a member subobject of type 'google::protobuf::Metadata *' with an lvalue of type 'const ::google::protobuf::EnumDescriptor **const'
	Cannot initialize a member subobject of type 'int' with an lvalue of type 'const ::google::protobuf::ServiceDescriptor **const'
	Use of undeclared identifier 'PROTOBUF_ATTRIBUTE_WEAK'
	Too many errors emitted, stopping now
	Testing cancelled because the build failed.

** TEST FAILED **

@lidizheng  since you're the release manager for this grpc release cycle, can you please work with @acozzette  to look into the issues exposed by this PR? The goal is to be able to upgrade to protobuf 3.15 release without any issues once it becomes available.

@acozzette Thanks for writing this PR up! Jan's comment summarized the failed build and logs, when you got a second, can you go through them to see if anything is trivially fixable. For harder issues, I can also help, and I'm available online/offline.

For the C++ build failure (constexpr constrcutors with parent class) on old compilers, based on Godbolt, it builds for clang 4.0.0+, with -std=c++11. I can't find which change in 4.0.0 release note fixed it (https://releases.llvm.org/4.0.1/tools/clang/ReleaseNotes.html). But we can bump up our minimum supported clang.

@lidizheng If we can end support for Clang 3.x then that would be great since that would solve the problem. Otherwise we might have to have some complicated ifdefs to handle older Clang versions.

Ad clang 3.6 and clang3.7 failures:   clang 3.x is pretty old by now. If it's older than 5 years, I think we can drop support for it (we normally support compiler versions released up to 5 years ago and newer),  but for that we would need to  update our portability test suite:
https://github.com/grpc/grpc/blob/711d1d7fe2da56896957e00fea12c84b6d1fa1e1/tools/run_tests/run_tests_matrix.py#L268 and setup clang tests for newer versions of clang).
https://github.com/grpc/grpc/blob/711d1d7fe2da56896957e00fea12c84b6d1fa1e1/tools/run_tests/run_tests.py#L490

@jtattermusch Clang 3.9.1 was released in December 2016, so it's not quite 5 years old yet. Is that OK or does that mean gRPC has to keep support for it until December 2021?

@jtattermusch Clang 3.9.1 was released in December 2016, so it's not quite 5 years old yet. Is that OK or does that mean gRPC has to keep support for it until December 2021?

I would be leaning toward dropping the support if that avoids dirty hacks. But it there is a reasonably easy to do proper fix, let's do that instead. Dropping clang 3.x support would ideally be done separately, not because we are pressured to that in order to be able to upgrade protobuf. Btw, what's the compiler support policy for protobuf - shouldn't clang 3.x be still supported?

I don't think we have an official compiler support policy, and in practice we have just been constrained by needing to support whatever gRPC supports. Unfortunately it sounds like there's not really an easy workaround but @sbenzaquen can probably say more.

We could use conditional compilation to add constexpr only when the compiler will support it.
The system will work if these constructors are not constexpr, but it will be less efficient (in binary size and startup cost).
We already have this case for versions of MSVC that don't do constant initialization, even though the spec says it should.
It does complicate the code. It would not be a dirty hack, it would be more like using a macro instead of spelling it constexpr directly.
I am not sure if this kind of conditional compilation would lead to ODR violations if different compilers are used for different parts of a binary. It most likely would. ie, if the proto library is prebuilt with/without constexpr and user code is built the other way.

I just merged https://github.com/grpc/grpc/pull/25443 and I'm going to restart the tests.  Now the clang3.x problem should go away, but other issues still need to be fixed.

Thanks, @jtattermusch. I am working on rc2 now and this should fix the Windows Python error. The Objective-C error looks like a mismatch between protoc and the protobuf runtime, so I think that might be a problem with the test setup. I haven't looked carefully at the Ruby failure yet but I think it might be easy to fix--it looks like the code is returning an error as expected but just doesn't have the exact error message the test expects. @haberman might know more about the Ruby test failure.

@acozzette It looks like you forgot to change Protobuf-C++.podspec, I think it's the root cause of the mismatch between protoc and the protobuf runtime.

@yulin-liang Oh thanks, I just pushed another commit to update the version there.

@acozzette Basic Tests C++ iOS still fails, here the error message:
Wed Feb 17 11:42:02 PST 2021 - [!] Error installing Protobuf-C++
Wed Feb 17 11:42:02 PST 2021 - [!] /usr/local/bin/git clone https://github.com/google/protobuf.git /var/folders/wv/_5q8c8j155g873yylt68nd4c0000gn/T/d20210217-5120-89p3hr --template= --single-branch --depth 1 --branch v3.15.0-rc1
Wed Feb 17 11:42:02 PST 2021 -
Wed Feb 17 11:42:02 PST 2021 - Cloning into '/var/folders/wv/_5q8c8j155g873yylt68nd4c0000gn/T/d20210217-5120-89p3hr'...
Wed Feb 17 11:42:02 PST 2021 - warning: Could not find remote branch v3.15.0-rc1 to clone.
Wed Feb 17 11:42:02 PST 2021 - fatal: Remote branch v3.15.0-rc1 not found in upstream origin

Looks like the tag name should be v3.15.0-rc1 instead of 3.15.0-rc1.

@yulin-liang Good catch, thanks! I added a v3.15.0-rc1 tag.

Remaining issues:
Sanity failures (both should be quite easy to fix)
https://source.cloud.google.com/results/invocations/bca59558-1c29-4b17-aa33-2e95791180c4/targets
Build issue on mac:
https://source.cloud.google.com/results/invocations/92317c37-6006-48bd-b83f-29c532424e44/log
Ruby tests seem broken:
https://source.cloud.google.com/results/invocations/7183090b-3072-4bed-9372-a10e7710baab/targets/github%2Fgrpc%2Frun_tests%2Fruby_macos_dbg_native%2Ftools%2Frun_tests%2Fhelper_scripts%2Frun_ruby.sh/tests

Would anyone on the gRPC team mind kicking off the tests again? I think most or all of the remaining issues should be fixed now.

@acozzette Can you take a look at the Sanity Checks? It needs a version update in podspec. The Ruby build failure looks like missing some Core files. Maybe re-run the tools/buildgen/generate_projects.sh script could fix the problem.

BTW, there is an update to fix the Ruby test https://github.com/grpc/grpc/pull/25507. When update this PR next time, we should probably sync with HEAD.

Looks like protobuf 3.15.2 has been released. @lidizheng  can you please create a PR to upgrade to that version? (and close this PR)

Thanks everyone for the investigating the problems. This PR can now be closed in favor of https://github.com/grpc/grpc/pull/25565


PlayerActivity content on landscape mode not easily accessible

Sometimes the content is not accessible and cannot be scrolled. See below image.

I have a proposal for this issue. Please look at the UI and video and let me know if a PR would be a good idea for this.
Thanks!

https://www.youtube.com/watch?v=oBQ7dVL_Q90

Nice - I like it. Some questions:

We'd want to control the number of columns based on the width of the grid, not the overall screen width (3 looks too tight here). I'd be nice if this could reuse the existing qualifiers somehow.
It'd be nice to cap the width of the profile info, i.e. on tablets half width might be too much.

Sounds good I will give it a try. I think I know how to achieve both.

Feature not available anymore


To add polling interval as a docker argument/config variable

Sometimes we need polling to be different than the default one and would be great to have it configurable at run time.

Sorry, found it


mame 0.178

version bump
build and install the latest man
remove inreplace for removing 64 suffix, just use rename install (no need for if block as 32-bit support was dropped earlier)

rom-tools should be bumped too

Exactly. I didn't have time to look at its changelog yet, but don't expect much change this time. Feel free to open a PR if interested.

Cool, I was just making sure you knew they get updated together since I saw the one PR and not the other.


Fixed the search count display text

The search control header bar on mobile wrapped poorly.
Before:

After:

Coverage remained the same at 95.216% when pulling 249f28aac6d968c93b17e4cd3e76fc010f3b6ab1 on cody-fix-search-count-display into 35724bd2cb071d94f6f66bce1dc2c086af266191 on main.


Warnings in Swift-Big-Number-Core.swift

lines 2282 and 2888
⚠ 'encodedOffset' is deprecated: encodedOffset has been deprecated as most common usage is incorrect. Use utf16Offset(in:) to achieve the same behavior.

You're welcome @twodayslate.
@Exey The issue can be closed.


[Bug]:

Bug Description
Bluetooth paired devices are not being displayed when typing the keyword "blue".
Relevant Screenshot

To Reproduce
No response
Debugging Log
[00:09:18.420] atop[Script Filter] Queuing argument '(null)'
[00:09:18.773] atop[Script Filter] Script with argv '(null)' finished
[00:09:18.776] ERROR: atop[Script Filter] Code 1: /Users/Username/Library/Application Support/Alfred/Alfred.alfredpreferences/workflows/user.workflow.52D64179-E064-42F0-9E3B-AD324CA51432/scripts/bluetooth-devices.js: execution error: Error: TypeError: undefined is not an object (evaluating 'allDevices.device_connected.forEach') (-2700)

Workflow Configuration

Checklist

[X] I have updated to the latest version of this workflow.
[X] I am using Alfred 5. (Older versions are not supported anymore.)

Could you attach a screenshot of your Bluetooth preferenes, where all your devices are listed? (you can blur out the device names, I just need to see the devices and the preferences)

Ah, I think I see where the problem lies.
Could you open the Terminal and run the following command:
system_profiler -json SPBluetoothDataType

and post here the output of that command?

023-07-31 11:31:21.027 system_profiler[14232:444263] SystemInfo-AccessoryFW - JBL T450BT: no firmware version info available
2023-07-31 11:31:21.029 system_profiler[14232:444263] SystemInfo-AccessoryFW - Pro: no firmware version info available
2023-07-31 11:31:21.029 system_profiler[14232:444263] SystemInfo-AccessoryFW from dict - SoundCore 2 = 0x011B
{
"SPBluetoothDataType" : [
{
"apple_bluetooth_version" : "8.0.5d7",
"device_title" : [
{
"JBL T450BT" : {
"device_addr" : "30-C0-1B-E8-3D-AE",
"device_classOfDevice" : "0x04 0x01 0x240404",
"device_core_spec" : "4.1",
"device_isconfigured" : "attrib_Yes",
"device_isconnected" : "attrib_No",
"device_ispaired" : "attrib_Yes",
"device_majorClassOfDevice_string" : "Audio",
"device_manufacturer" : "Unknown (0x7, 0x13B3)",
"device_minorClassOfDevice_string" : "Headset",
"device_services" : "AVRCP CT, A2DP Sink, HandsFree, AVRCP TG, Headset",
"device_supportsEDR" : "attrib_Yes",
"device_supportsESCO" : "attrib_Yes",
"device_supportsSSP" : "attrib_Yes"
}
},
{
"Pro" : {
"device_addr" : "26-93-53-39-8E-C9",
"device_classOfDevice" : "0x04 0x01 0x240404",
"device_core_spec" : "5.1",
"device_isconfigured" : "attrib_Yes",
"device_isconnected" : "attrib_No",
"device_ispaired" : "attrib_Yes",
"device_majorClassOfDevice_string" : "Audio",
"device_minorClassOfDevice_string" : "Headset",
"device_services" : "JL_A2DP, JL_HFP",
"device_supportsEDR" : "attrib_Yes",
"device_supportsESCO" : "attrib_Yes",
"device_supportsSSP" : "attrib_Yes"
}
},
{
"SoundCore 2" : {
"device_addr" : "08-EB-ED-A6-9B-0B",
"device_classOfDevice" : "0x04 0x01 0x240404",
"device_core_spec" : "4.2",
"device_fw_version" : "0x011B",
"device_isconfigured" : "attrib_Yes",
"device_isconnected" : "attrib_No",
"device_ispaired" : "attrib_Yes",
"device_majorClassOfDevice_string" : "Audio",
"device_minorClassOfDevice_string" : "Headset",
"device_productID" : "0x0500",
"device_services" : "AVRCP CT, A2DP Sink, HandsFree, AVRCP TG",
"device_supportsEDR" : "attrib_Yes",
"device_supportsESCO" : "attrib_Yes",
"device_supportsSSP" : "attrib_Yes",
"device_vendorID" : "0x099A"
}
}
],
"incoming_serial_ports_title" : [
{
"Bluetooth-Incoming-Port" : {
"device_authentication" : "attrib_No",
"device_channel" : "3"
}
}
],
"local_device_title" : {
"general_address" : "B8-E8-56-34-5F-13",
"general_autoseek_keyboard" : "attrib_On",
"general_autoseek_pointing" : "attrib_On",
"general_chipset" : "20702B0",
"general_connectable" : "attrib_Yes",
"general_device_class_composite" : "0x38010C",
"general_device_class_major" : "0x01",
"general_device_class_minor" : "0x03",
"general_discoverable" : "attrib_Off",
"general_fw_version" : "v150 c9319",
"general_hardware_transport" : "USB",
"general_hci_revision" : "0x2467",
"general_hci_version" : "4.0 (0x6)",
"general_lmp_subversion" : "0x4196",
"general_lmp_version" : "4.0 (0x6)",
"general_mfg" : "Broadcom",
"general_name" : "MacBook Pro",
"general_power" : "attrib_On",
"general_productID" : "0x8289",
"general_remoteWake" : "attrib_On",
"general_service_class" : "0x1C0",
"general_supports_handoff" : "attrib_Yes",
"general_supports_instantHotspot" : "attrib_Yes",
"general_supports_lowEnergy" : "attrib_Yes",
"general_type_complete_string" : "Mac Portable",
"general_type_major_string" : "Computer",
"general_vendorID" : "0x05AC"
},
"services_title" : [
{
"file_browsing_title" : {
"service_FTPRootFolder" : "~/Public",
"service_OBEXReceive" : "service_acceptAll",
"service_state" : "attrib_disabled"
}
},
{
"object_push_title" : {
"service_OBEXFolder" : "~/Downloads",
"service_OBEXHandle_Other" : "service_saveToLocation",
"service_OBEXReceive" : "service_acceptAll",
"service_state" : "attrib_disabled"
}
},
{
"internet_sharing_title" : {
"service_state" : "attrib_disabled"
}
}
]
}
]
}%

oh, okay, it looks like on your device, the output of the command looks totally different from mine, which I of course have not accounted for in the workflow.
Could you share your mac device model and your macOS version number?

macOS Big Sur
Version 11.7.9
MacBook Pro (Retina, 15-inch, Late 2013)

okay, version 1.0.9 should fix the problem: https://github.com/chrisgrieser/alfred-atop/releases/tag/1.0.9

Unfortunately, it's still showing an error.

ah, that's actually another problem on top of the existing problem.
Reason, is that my code is using some newer functions which were not yet available on older macOS versions.
I released version 1.0.10, which should avoid using that function: https://github.com/chrisgrieser/alfred-atop/releases/tag/1.0.9
Hopefully that fixes it. If not, I am afraid your macOS version is just too old to be supported, and you should update it if possible

OK, I installed 1.0.10 and unfortunately, still no joy. And unfortunately for me, my macOS is as up to date as it can be.
Thank you for your time and effort, I really appreciate it.

yeah, too bad! Hope the rest of the features still work fine :(

Oh, I just had an idea. Could you try 1.0.11?
https://github.com/chrisgrieser/alfred-atop/releases/tag/1.0.11

Yes! It works!

Well done, excellent job.
"Hope the rest of the features still work fine" - As far as I tried, all the other features work OK.
Thank you again, I appreciate it.


Visits service api

JIRA: link to jira ticket
Context:
What is the ticket about and why are we doing this change.
Changes
What are the various changes and what other modules do those changes effect.
This can be bullet point or sentence format.
Before and After UI (Required for UI-impacting PRs)
before: visit-service-new was not implemented in the api gateway
after: now it is and it's fully functional
Dev notes (Optional)

Specific technical changes that should be noted

Linked pull requests (Optional)

pull request link

Could you please add images to show that related UI sections are functioning? You appear to also be missing the link to the Jira ticket. It would be beneficial to add more details as to the changes that were done instead of just saying that now it's fully functional. An example would be a small explanation as to why you changed the Date to be split into various fields (year, month, day).


Multiple include during testing

PHP Fatal error:  Cannot redeclare is_active_menu() (previously declared in /xxx/app/Modules/Admin/helper.php:29) in /xxx/app/Modules/Admin/helper.php on line 29
include_once could solve the issue. Why do you use include here?

Hi,
your problem is not a multiple include (in fact every file is getting included once anyway).
Since the function in your helper files are in the same scope, you should either give them a unique name or check if there is already a function with the same name.
Laravel is doing the same thing in its helpers file. F.A.
if (! function_exists('array_add')) {
    /**
     * Add an element to an array using "dot" notation if it doesn't exist.
     *
     * @param  array   $array
     * @param  string  $key
     * @param  mixed   $value
     * @return array
     */
    function array_add($array, $key, $value)
    {
        return Arr::add($array, $key, $value);
    }
}

@Artem-Schander Thanks!!
I had a mess in    function_exists('xxx')


Allow FontInfo{,Base,Desired} to store a font name > 32 wch

Summary of the Pull Request
We now truncate the font name as it goes out to GDI APIs, in console API
servicing, and in the propsheet.
I attempted to defer truncating the font to as far up the stack as possible, so as to make FontInfo usable for the broadest set of cases.
PR Checklist

[x] Closes #602
[x] CLA signed
[x] Tests added/passed
[ ] Requires documentation to be updated
[x] I'm of the corefolk

Detailed Description of the Pull Request / Additional comments
There are a couple things I have questions about, actually. I know that Settings gets memset (memsat?) by the registry deserializer, and perhaps that's another place for us to tackle. Right now, this pull request enables fonts whose names are >= 32 characters in Windows Terminal only, but the underpinnings are there for conhost as well. We'd need to explicitly break at the API, or perhaps return a failure or log something to telemetry.

Should we log truncation at the API boundary to telemetry?
Should the "launch face name" get the same treatment as the face name in Settings?
Should we fix Settings here, or later?
TrueTypeFontList is built out of things in winconp, the private console header. That fills me with dread that those structures are used for interop -- so I didn't bubble these fixes all the way up through the "default font" list, even though nominally the font list is also unbounded strings.
Is unsigned int right for codepage? For width?

I left some comments about truncating font faces around, but they could be tantamount to noise.

I also tested with my font set to __DefaultTTFont__.

argh, I used the wrong browser profile to submit this PR

I think #2674 might be resolved or close to resolved with this too. Can you check that?

Closer, but not there yet. It's suppressed in two places, one of which still has some static wstrings (font, padding, starting directory, delimiters)

Should we log truncation at the API boundary to telemetry?

I think so, yes.

Should the "launch face name" get the same treatment as the face name in Settings?

I think so, yes.

Should we fix Settings here, or later?

Here if it's possible. I would love for conhost to get the benefits of this too.

TrueTypeFontList is built out of things in winconp, the private console header. That fills me with dread that those structures are used for interop -- so I didn't bubble these fixes all the way up through the "default font" list, even though nominally the font list is also unbounded strings.

It's not for interop. It was just shared between the conhost and propsheet code which used to live in different depots and were both written in just plain C. Now that both of them can use C++ and live in the same depot, you're welcome to bubble it the whole way through TrueTypeFontList (and half rewrite that bugger if you like to use modern collections and stuff). Or set it as a TODO for someone else to do.

Is unsigned int right for codepage? For width?

Int might be a bit too big for codepage. I think Codepage is actually an unsigned short. But I'm fine with unsigned int if that fits better in things.
I also think font weight is 100-900 so unsigned short might be more appropriately sized there too. (Width translated to weight via asking you what "width" was all about in Teams.)

Actually, on the telemetry front: we'll get a log and fail to service the API call when the font name is too long. Right now, there's no way to get a font name that's too long... so I'm going to tag this with #3123 as well.

/azp run

Okay, clearly I regressed this.

/azp run

I'm extremely confused/alarmed.
The selection tests were failing because the unique_ptr holding the Selection singleton at static file scope was being overwritten with 0x00000000FFFFFFFF. It then later failed the null check in Selection::Instance(), so that value was returned as the Selection instance.
Time travel tracing indicates that the constructor for CursorBlinker CONSOLE_INFORMATION::_blinker is writing to the same storage as the unique_ptr when it initializes the timer timeout to INFINITE.
Why do they share storage?

It turns out that there's an ODR violation! CONSOLE_INFORMATION changes size based on whether UNIT_TESTING is defined (VtIo got a new UNIT_TESTING-only member in #2525), and that gets rolled up into Host.unittest.lib. InteractivityBase.lib has a compile-time dependency on the layout of CONSOLE_INFORMATION, but InteractivityBase isn't built with a UNIT_TESTING variant. CI gets constructed in InteractivityBase, and as the linker can resolve the ODR violation in whatever way it sees fit it ends up choosing the shorter layout when packing in file-level statics.
This bug only exists in our tests. The fix in 83fcb6c moves the trampled global out of the way... but just fixes the symptom. :|
/cc @miniksa

Followup filed in #3170.


Add member match pre-built service

Purpose

$title

Related issue: https://github.com/wso2-enterprise/open-healthcare/issues/1553

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

same code is adding with https://github.com/wso2/open-healthcare-prebuilt-services/pull/85 .  hence closing


Multiple requests at the same time

Hi, is there any way to make the requests parallel and limit them?
I want to make a scraper for a image based website, however the cdn is pretty slow compared to the site itself, is there any way to implement the scraper and make it download images in parallel since they are slow to download?

+1 to this. Because the Stream implementation on Collector uses Unpin and static, it becomes awkward when using non-standard threads (e.g., within a scheduled task / recurring job). I believe there are ways to do it though, as long as you can pin the Collector to the same Pin<Box> as whatever thread you are calling it from. This is the specific error I'm getting now, if anyone has any ideas.
future cannot be sent between threads safely
the trait `std::marker::Send` is not implemented for `(dyn futures_util::Future<Output = Result<std::option::Option<std::string::String>, anyhow::Error>> + 'static)`
required for the cast from `[async block@src\main.rs:18:84: 36:6]` to the object type `dyn futures_util::Future<Output = ()> + std::marker::Send`
text_scraper.rs(62, 43): future is not `Send` as this value is used across an await

Specifically, it is failing here, which is in a different file:
collector.crawler_mut().visit(
    self.url.clone().to_string(),
);
// It is the await from `.next()` which causes this issue, because collector is manually pointed to the 'static thread
if let item = collector.next().await {
    return Ok(item.unwrap());
};
Err(Error::msg("No text found"))


Vulkan validation layer errors

v2024.1.26
i5-9500T
UHD Graphics 630
Vulkan version 1.3
.
.
.
struct Constants {
    float* stuff;
};
[[vk::push_constant]] Constants g_constants;

[shader("compute")] [numthreads(1, 1, 1)] void main() {
    g_constants.stuff[0] = 4;
 }

Compiling with:
slangc File.slang -target spirv -emit-spirv-directly -force-glsl-scalar-layout -capability GL_EXT_buffer_reference -o File.comp.spv -entry main;
This throws the following validation messages:
VUID-VkShaderModuleCreateInfo-pCode-08737(ERROR / SPEC): msgNum: -1520283006 - Validation Error: [ VUID-VkShaderModuleCreateInfo-pCode-08737 ] | MessageID = 0xa5625282 | vkCreateShaderModule(): pCreateInfo->pCode (spirv-val produced an error):
Structure id 28 decorated as Block for variable in PhysicalStorageBuffer storage class must follow relaxed storage buffer layout rules: member 1 is an improperly straddling vector at offset 12
  %Instance_natural = OpTypeStruct %v3float %v3float
. The Vulkan spec states: If pCode is a pointer to SPIR-V code, pCode must adhere to the validation rules described by the Validation Rules within a Module section of the SPIR-V Environment appendix (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkShaderModuleCreateInfo-pCode-08737)
    Objects: 0
VUID-VkShaderModuleCreateInfo-pCode-08740(ERROR / SPEC): msgNum: 115483881 - Validation Error: [ VUID-VkShaderModuleCreateInfo-pCode-08740 ] | MessageID = 0x6e224e9 | vkCreateShaderModule():  SPIR-V Capability VariablePointers was declared, but one of the following requirements is required (VkPhysicalDeviceVulkan11Features::variablePointers). The Vulkan spec states: If pCode is a pointer to SPIR-V code, and pCode declares any of the capabilities listed in the SPIR-V Environment appendix, one of the corresponding requirements must be satisfied (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkShaderModuleCreateInfo-pCode-08740)
    Objects: 0
VUID-VkShaderModuleCreateInfo-pCode-08740(ERROR / SPEC): msgNum: 115483881 - Validation Error: [ VUID-VkShaderModuleCreateInfo-pCode-08740 ] | MessageID = 0x6e224e9 | vkCreateShaderModule():  SPIR-V Capability PhysicalStorageBufferAddresses was declared, but one of the following requirements is required (VkPhysicalDeviceVulkan12Features::bufferDeviceAddress OR VkPhysicalDeviceBufferDeviceAddressFeaturesEXT::bufferDeviceAddress). The Vulkan spec states: If pCode is a pointer to SPIR-V code, and pCode declares any of the capabilities listed in the SPIR-V Environment appendix, one of the corresponding requirements must be satisfied (https://vulkan.lunarg.com/doc/view/1.3.283.0/windows/1.3-extensions/vkspec.html#VUID-VkShaderModuleCreateInfo-pCode-08740)

.
But compiler has -force-glsl-scalar-layout as a flag
And Vulkan13 features are enabled in the application side
.
.
.
.
Trying to check the resulting GLSL by compiling with:
slangc File.slang -target glsl -profile glsl_460 -force-glsl-scalar-layout -capability GL_EXT_buffer_reference -o File.comp.glsl -entry main;
This throws:
(0): internal error 99999: unexpected condition encountered in Slang compiler: unhandled type
.
.
.
.
All of the listed problems occur when the pointer is written to

You have to explicitly enable each of the required features before calling vkCreateDevice, for example:
    VkPhysicalDeviceVulkan12Features vulkan12Features = {
        .sType = VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_VULKAN_1_2_FEATURES,
        .pNext = &vulkan13Features,

        .uniformAndStorageBuffer8BitAccess = VK_TRUE,
        .shaderFloat16 = VK_TRUE,
        .shaderInt8 = VK_TRUE,

        .scalarBlockLayout = VK_TRUE,
        .bufferDeviceAddress = VK_TRUE,
    };
    VkPhysicalDeviceVulkan11Features vulkan11Features = {
        .sType = VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_VULKAN_1_1_FEATURES,
        .pNext = &vulkan12Features,

        .uniformAndStorageBuffer16BitAccess = VK_TRUE,
        .variablePointersStorageBuffer = VK_TRUE,
        .variablePointers = VK_TRUE,
    };
    VkDeviceCreateInfo createInfo = {
        .sType = VK_STRUCTURE_TYPE_DEVICE_CREATE_INFO,
        .pNext = &vulkan11Features,
    // ....

Oh, I see!
My apologies, it had nothing to do with Slang
Thank you!

Wait, sorry
That still does not explain the:
(0): internal error 99999: unexpected condition encountered in Slang compiler: unhandled type
issue when compiling to GLSL

I think that is because pointers are only supported in the SPIRV backend.

Ah, I see
That is all, thanks again!


Wrapping SafeAreaView creates a white gap between the navbar and status bar

To support iPhone X I am using SafeAreaView from 'react-native'. When wrapping the View that holds the NavigationBar and right under it some content, leaves me with a white gap that is 20 in height. Removing NavigationBar gives the outcome that is needed. Anyone came across this kind of issue?

When using the inspector on the gap it shows that the height 20 is coming from the package.

<SafeAreaView style={styles.container}>
                <Navbar
                    editMode={this.state.editMode}
                    imageSource={
                        strings.getLanguage() === 'en'
                            ? require('../../../assets/images/logos/wordmark_english.png')
                            : require('../../../assets/images/logos/ar_text_logo.png')
                    }
                    onPressFilter={this.onPressFilter.bind(this)}
                />
                <View style={styles.content}>
                    <PoolListView
                        refreshing={this.state.refresh}
                        refreshPools={this.refreshPools}
                        favourites={this.state.favourites}
                        pools={this.state.pools}
                        navigation={this.props.navigator}
                    />
                </View>
            </SafeAreaView>

Navbar is a custom component that just returns NavigationBar, it is not wrapped with any other View, it just returns NavigationBar. Here is the styles that I am using
const styles = StyleSheet.create({
    container: {
        flex: 1,
        backgroundColor: colors.softLavender,
    },
    content: {
        justifyContent: 'center',
        alignItems: 'center',
        marginBottom: 80,
        backgroundColor: colors.softLavender,
    },
    filterButton: {
        marginRight: 30,
        marginLeft: 30,
        marginTop: 0,
        justifyContent: 'center',
    },
    noPoolsContainer: {
        flex: 1,
        justifyContent: 'center',
        alignItems: 'center',
    },
    noPoolsText: {
        fontFamily: 'SSTArabic-Roman',
        textAlign: 'center',
        color: colors.black,
    },
});

EDIT
By removing the status bar style in styles.js the issue is fixed.

@qasimalbaqali  is using thischanges but nothing is happening

@deepak28 you can give backgroundColor to safeareaview to achieve this


Vulnerability roundup 93: postgresql-9.6.19: 2 advisories [8.8]

search, files

[ ] CVE-2018-1058 CVSSv3=8.8 (nixos-20.09, nixos-unstable)
[ ] CVE-2019-9193 CVSSv3=7.2 (nixos-20.09, nixos-unstable)

Scanned versions: nixos-20.09: ad3a5d5092e; nixos-unstable: 84d74ae9c9c.
Cc @danbst
Cc @globin
Cc @marsam
Cc @ocharles
Cc @thoughtpolice

9.6.20 fixed some CVEs, but none of the ones listed here.
They are al 2020 CVEs, so maybe they do close the vulnerabilities listed here, but got their own numbers.

9.6.20 fixed some CVEs, but none of the ones listed here.
They are al 2020 CVEs, so maybe they do close the vulnerabilities listed here, but got their own numbers.

CVE-2018-1058 was fixed in 9.6.8: https://www.postgresql.org/about/news/postgresql-103-968-9512-9417-and-9322-released-1834/.
CVE-2019-9193 isn't a vulnerability: https://www.postgresql.org/about/news/cve-2019-9193-not-a-security-vulnerability-1935/.

CVE-2018-1058 was fixed in 9.6.8: https://www.postgresql.org/about/news/postgresql-103-968-9512-9417-and-9322-released-1834/.
CVE-2019-9193 isn't a vulnerability: https://www.postgresql.org/about/news/cve-2019-9193-not-a-security-vulnerability-1935/.