refactor the getMaxResource method

As mentioned in #1161, put the getMaxResource refactor into a separate PR.
The new getMaxRequiredResource will find the max requirement for cpu, ram and disk from all the required container resources.
MesosScheduler and AuroraScheduler will use the new method to decide their resource allocation to each container.

👍

LGTM
@avflor and @ashvina you were also doing some similar refactors lately. Would you please review.

@nlu90 @billonahill The change looks good to me. The only difference is that in the original code Aurora takes only memory into account when computing the max resources whereas Mesos considers all the resources. I think it is more correct to use all resources as done in this PR.

@avflor yeah, as we discussed in a previous refactor PR #1079 to take cpus and disks into consideration.

@nlu90 - if everything looks good, can you merge it?

The change looks good to me. It would be great if someone could provide some clarity on the question I posted above.


Argument kptij_lst is ignored when building pbc GDF integrals

Specifying kptij_lst is useful, e.g., when considering k-point symmetry where the number of integrals needed for SCF calculations can be reduced by the order of the group.

Hi Xing,
Does it mean that by specifying kptij_lst, the h5 file of GDF can also be reduced?
Will it be possible to provide a more detailed example here?

For mean field calculations, yes. Suppose (ki, kj) is related with (ki', kj') by a rotation, then the corresponding eris can be transformed from one to the other by some unitary transformation. So there is no need to compute GDF for (ki', kj'). Though the trade-off is that you need to do addition integral transformations. But I assume the transformations should be less expensive than GDF.

It sounds great. I ever tried to perform some slab in PySCF. Then the GDF step will generate h5 file up to 2.5 TB with szv basis set. If we want larger and more reliable dzvp or even tzvp basis set, the h5 file would even be more than 10TB, which is extremely beyond the reach of the machine I am using...

@fishjojo , thanks for noticing this! Has it been resolved now?


[beta] Show AuthorCredit on hover and focus

Reused the AuthorCredit component that was already there, except added @rachelnabors as default values. Now uses sr-only class by default and not-sr-only when illustration is hovered or focused.
Pending (?)

Haven't gone through every illustration to validate which ones should be credited to who.
Havne't touched the Diagram component (yet)

Screenshots

nice, thank you for kicking this off!
a few suggestions:

let's move it to the top of the image rather than the bottom
can you style it a bit more like a tooltip pill? i'll ask @lebo to actually "tailwind it up" so it's nbd if you'd rather not

@gaearon I've moved it to the top, but I need to think a bit more about the tooltip suggestion. For a11y, tooltips typically require the "trigger" element to be focusable. We could make the illustrations focusable, but then focusable elements require a role and an accessible name. 🤔

merged via https://github.com/reactjs/reactjs.org/pull/5188. thank you!


Error creating a db migration

Fresh installation with the below steps on win11 / dotnet 8
dotnet tool install --global Spark.CLI
spark install
spark new MyApp
...

Then tried to create a migration and get some ambiguous output,

$ spark make migration x

Creating a new migration

Could not execute because the specified command or file was not found.
Possible reasons for this include:
  * You misspelled a built-in dotnet command.
  * You intended to execute a .NET program, but dotnet-ef does not exist.
  * You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH.

--------------------------------------------------------------------------------------------
Spark migration x created

traced it down to a missing dotnet tool.
dotnet tool install --global dotnet-ef


Fix doesn't work with Ruby < 2.4

Issue
Closes #5
Changes

Use =~ instead of match? for investigating env['HTTP_HOST']

Note
Ruby 2.4 introduced String#match? method which returns true/false instead of the match data and it would be better to use the method if we do not support Ruby < 2.4.  Another solution is just using /.../ =~ env['HTTP_POST'].
See https://github.com/fphilipe/xipio/pull/4#discussion_r151167542

Thanks! New version released.

Thanks! Appreciate your efficient work!


Geolocation / getCurrentPosition takes ~2 mins to return

import 'dart:async';
import 'dart:html' as dom;

Future main() async {
    final dom.Geolocation geo = dom.window.navigator.geolocation;

    final stopwatch = new Stopwatch();

    print("Request current location...");
    stopwatch.start();

    final dom.Geoposition position = await geo.getCurrentPosition();
    stopwatch.stop();

    print("getCurrentPosition took: ${stopwatch.elapsedMilliseconds}ms");
    print("Lat: ${position.coords.latitude}, Long: ${position.coords.longitude}");
}

Output:
Request current location...
getCurrentPosition took: 108961ms
Lat: 47.432350799999995, Long: 12.2150032

This happens if I make the request more the once. It is relatively fast for the first request but takes forever for all other requests
Dart 1.24.3
Version 65.0.3325.181

Hmmm - maybe it's related to this Chrome bug: https://bugs.chromium.org/p/chromium/issues/detail?id=820945&can=2&start=0&num=100&q=geolocation&colspec=ID

Closing as un-actionable. We're limited by what the browser is doing here...


Attempt #2 at fixing a bad link in a comment.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: geeknoid
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS [geeknoid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
dc3a73194d3e9fd7aae9d92befa167e2e0a3f349
link
/test e2e-simpleTests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-simpleTests


[HOLD for payment 2023-07-17] [$1000] Dev: Console error appears when opening Workspace Members Page

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

Action Performed:

Go to Settings -> Workspaces
Select any workspace -> Members
Refresh the app

Note: without refresh also it can be reproducible.
Expected Result:
No console error
Actual Result:
Error appearing: Warning: Failed prop type: Invalid prop option.keyForList of type number supplied to OptionRow, expected string.
Workaround:
Unknown
Platforms:

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

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

Version Number: n/a
Reproducible in staging?: n/a
Reproducible in production?: n/a
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
Console error on invite member.webm
Expensify/Expensify Issue URL:
Issue reported by: @daordonez11
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687887087153099
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~013423b04ca2e860f4
Upwork Job ID:<PHONE_NUMBER>150136832
Last Price Increase: 2023-06-30

Proposal
Please re-state the problem that we are trying to solve in this issue.
Dev: Console error appears when opening Workspace Members Page
What is the root cause of that problem?
https://github.com/Expensify/App/blob/53e4154143052649ed7b2b8df302cd1744f31f67/src/pages/workspace/WorkspaceMembersPage.js#L336
Here, item.accountID type is number.
But
https://github.com/Expensify/App/blob/53e4154143052649ed7b2b8df302cd1744f31f67/src/components/optionPropTypes.js#L32
keyForList type should be string.
What changes do you think we should make in order to solve the problem?
Convert item.accountID to string type.
https://github.com/Expensify/App/blob/53e4154143052649ed7b2b8df302cd1744f31f67/src/pages/workspace/WorkspaceMembersPage.js#L336
After change:
keyForList: `${item.accountID}`

What alternative solutions did you explore? (Optional)
N/A

Dupe of https://github.com/Expensify/App/issues/21611

@Santhosh-Sellavel @maddylewis plz check this
comment   once.

@Pujan92 I've checked your comment and @maddylewis's too here. As it's triaged, made external, and ready to move forward let's handle it here.
@maddylewis We need to award reporting bonus to @Pujan92 only as they reported it first!

Considering the proposal from the other issue as well
@Pujan92's proposal LGTM!
C+ Reviewed
🎀 👀 🎀

This is a straightforward issue. A couple of proposals suggest making the passed prop with different ways to make it a string So I went selecting the first one and @allroundexperts suggests adding another type to the number of the propTypes That's a good option too, but I don't see any necessity here. Preferably the type String should be good enough for now.
I'll let you take the final call here @Li357, thanks!

Agree we should stick with just a string proptype, and I prefer an explicit coercion with String than string interpolation. @Pujan92 all yours!

Someone should review this offer! @Pujan92 should get the report offer as well! Mine was later.

@daordonez11 Yes it was sent accidentally, sorry for the confusion. Please reject as the offer was made in error.
cc: @maddylewis Update @Pujan92 as reported, thanks!

@Santhosh-Sellavel @Li357 PR is ready for review!

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x]  [@Santhosh-Sellavel] The PR that introduced the bug has been identified. Link to the PR:
[x]  [@Santhosh-Sellavel] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/21237/files#r1265665581
[x]  [@Santhosh-Sellavel] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: Should be caught based on checklist
[x]  [@Santhosh-Sellavel] Determine if we should create a regression test for this bug. N/A
[x]  [@Santhosh-Sellavel] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again. N/A
[x]  [@maddylewis] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

We don't need a separate regression test here, as we used to look for console errors normally!
cc: @Li357 Let me know if differ on any of the above, thanks!

Requested payment on ND!

Approved 1500 for Santhosh on ND

is someone able to confirm the following payments were processed:

@Santhosh-Sellavel ($1500 paid via NewDot)
@Pujan92 ($1500 auto payment via Upwork)
@daordonez11 ($250 reporting bonus auto payment via Upwork)

once those are all set i believe we can close this issue - thanks!

@maddylewis  I rejected reporting, finally @Pujan92 himself did the first report as well.

So, @Pujan92 is owed an additional $250?

Yeah! I think @Pujan92 total is 1750. He has a bonus for urgency and reporting!

@Pujan92 ($1500 auto payment via Upwork)

@maddylewis I think I am yet to receive this. Could you plz check once on it?

[ ] Sent $1500 offer to @Pujan92
[ ] Sent $250 offer to @daordonez11

@maddylewis Ill reject the 250! Remember it is 1750 for @Pujan92

oh, i see. i thought you were both getting reporting bonuses for this one. I've sent $1750 to @Pujan92 - so i think we're all set here!

Yup it's all clear! I always wanna keep things straight 🫡


[RFC] make requirement-check a bin resource

This PR makes symfony requirements checker available via bin/symfony_requirements.

[x] SymfonyRequirements are normal autoloadable classes in this bundle
[ ] bin/symfony_requirements uses the bundle classes so that the requirement check is always up-to-date. this way we get rid of the installRequirementsFile composer hook. the hook was ugly because it was overwriting files in the user project although they might have been modified by users.
[ ] make requirement checking reusable / extendable, see symfony/symfony-standard#715
[x] we do not have to bother where to put the SymfonyRequirements.php file in the standard edition (does neither fit in app nor var)
[ ] users should not have app/SymfonyRequirements.php and app/check.php in their source control because it does not belong there
[ ] bin/symfony_requirements should still be executable with PHP 5.2 and give error message
[ ] bin/symfony_requirements should still be executable with without vendors and give error message by just having a copy of it already in the standard-edition
[ ] maybe expose requirements check as custom composer command, see http://seld.be/notes/composer-1-0-alpha9

I think we can close this one since https://github.com/sensiolabs/SensioDistributionBundle/pull/118 is doing the job, right?

#118 is not related to this PR.

But the description starts with "This PR makes symfony requirements checker available via bin/symfony_requirements", and it seems that we can already do that.
Is the to-do list still accurate?
Thanks!

It's about making the requirements check a composer bin script which is installed with composer like phpunit etc. Not the manual copy logic that is currently in place.

@Tobion Ok, will you have time to finish this PR?

Not at the moment. But it doesn't seem that high of a priority anyway as nobody commented on the RFC yet.

@Tobion thank you for proposing this, it's very interesting. I'd like to share some thought about your description considering you wrote it 3 years ago:

SymfonyRequirements are normal autoloadable classes in this bundle

Today that does not seem true. I guess this is about not relying on autoload (thus composer install) for symfony-standard.

bin/symfony_requirements uses the bundle classes so that the requirement check is always up-to-date. this way we get rid of the installRequirementsFile composer hook. the hook was ugly because it was overwriting files in the user project although they might have been modified by users.

There are now comments at the beginning of the compiled files explaining that one should not override them.
And clearly, this should not be encouraged. The hook only copy files in the right places and this is good to handle dynamic changes and configuration.
As said in inline comment, the hook may copy the file in the bundle directly instead but I fail to see how we can get rid of the hook to handle it.

make requirement checking reusable / extendable, see symfony/symfony-standard#715

The SymfonyRequirements.php classes are extendable for anyone requiring the file directly from the bundle and the composer script uses protected methods.
Does not look so difficult to me to extend it already. What more can be done without using autoloading?

we do not have to bother where to put the SymfonyRequirements.php file in the standard edition (does neither fit in app nor var)

This where I agree, using the composer symlink would allow to keep generated stuff in the bundle.

users should not have app/SymfonyRequirements.php and app/check.php in their source control because it does not belong there

They belong there if one wants to extend them, don't they?

bin/symfony_requirements should still be executable with PHP 5.2 and give error message

New features go in master now and I suggest to support 5.3 as only minimum until symfony 2.8 EOL.

bin/symfony_requirements should still be executable with without vendors and give error message by just having a copy of it already in the standard-edition

This is the tricky part. Using autoloading would allow to proper file for requirements and better extendibility. I'm not sure we should care about running requirements before composer install. On the contrary, making the composer run mandatory would kind of ease stuff.

maybe expose requirements check as custom composer command, see http://seld.be/notes/composer-1-0-alpha9

I think this is up to dev to use this feature in their project. Having a composer script in a bundle like this makes much more sense. Perhaps in symfony-standard this would be worth it.

Closing as this got solved with https://github.com/symfony/requirements-checker and https://github.com/symfony/recipes/tree/master/symfony/requirements-checker


1.19.2 Update for Create 0.5g

Hi there,
I was playing with this mod and it's dependencies on the latest version until I updated to Create 0.5g on 1.19.2 when that released. After this, turrets on moving contraptions would cause a crash whenever they tried to play the sound of that spell, by updating the dependencies in gradle this has been fixed for my world at least.
I formatted the gradle.properties and build.gradle for easy future updating and matched the forge version to the Ars Nouveau and Create version. I also removed a log message that spammed console whenever a turret was using source on a contraption.
Thanks for the great compatibility mod.

Thanks!


Transformed commands aren't registered if dto is in the same file

Describe the bug
Transformed commands are not registered with the bot if the dto is in the same file as the command.
To Reproduce

Start with the command sample
Create new transformed command test.command.ts (see source code below)
run npm build and npm start
type !deploy in discord

export class TestDto {
  @Param({
    name: 'song',
    description:
      'Name or URL of song/playlist. Could be from (Youtube, Spotify, SoundCloud)',
    required: true,
  })
  song: string;
}

@Command({
  name: 'test',
  description: 'Plays a song',
})
@UsePipes(TransformPipe)
export class TestCommand implements DiscordTransformedCommand<TestDto> {
  handler(@Payload() dto: TestDto, interaction: CommandInteraction): void {
    console.log('DTO', dto);
    console.log('Interaction', interaction);
  }
}

Expected behavior
Both the test command and the play command should be registered
Desktop (please complete the following information):

OS: Win11
Node: v16.13.0
@discord-nestjs/common: 2.0.7
@discord-nestjs/core: 2.1.5

Thanks for report! Fixed in next version


[FLINK-8828] [stream, dataset, scala] Introduce collect method

What is the purpose of the change
A collect function is a method that takes a Partial Function as its parameter and applies it to all the elements in the collection to create a new collection which satisfies the Partial Function. It makes certain things nicer to express
Brief change log

added collect method on scala dataset and datastream api

Verifying this change
It seems to be hard to find a place where this could be tested in isolation, suggestions welcome
Does this pull request potentially affect one of the following parts:

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

Documentation

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

need to add to java API as well

I'm closing this as "Abandoned", since there is no more activity and the code base has moved on quite a bit. Please re-open this if you feel otherwise and work should continue.


[8.x] Update conditionals for Collection and LazyCollection contains methods

A small fix from my previous PR.
When calling the following:
$collection = collect([1, 2, 3, 4, 5]);

$collection->doesntContain(function ($value, $key) {
    return $value < 5;
});

A TypeError is returned by the method because the operator and value values are carried over to the contains method, therefore func_num_args() is equal to 3 instead of 1.
I've updated the conditionals so that it checks that the operator and value values are null instead and now the method works as expected.
Sorry bout that!

Eh, that's different behavior than func_num_args. I'll need to adjust doesntContain.

Fixing now.


Switches to current convention for export

as well as allowing testing of other form container components

Did we figure out why this was failing?

Right now it's looking like a timeout error. Re-running tests.


What is the state of this repo ?

@alfonsogarciacaro I just took a look at the repo and it's looks like some part are with Fable 1.0, others with Fable 0.7
Also, I don't really understand the samples directory or the idea behind the main project. I mean the src folder is empty.
ping @majorgreys  who was trying to use this repo to learn Fable and Electron.

Yeah, this repo needs some love. My plan is to move the bindings to fable-import and rename this as samples-electron, but I'm not sure if I'll be able to do it before FableConf 😕

No problem, I can give it a try.
I will create a basic PR and we will be able to start working from there.


Document Differences between sVim

Would like to see a comparison between vimari and sVim on README.

Hi @bhagyas.
If you want to do a comparison you are welcome to do so, but if you're asking for someone else to do it I don't think you'll have any luck. It's a very specific request and I think you can quickly get an overview of what the two extensions can do by looking at the documentation.
Right now it looks like sVim only supports Safari v11 and below which I guess is a big difference.


Tags feature is not working in the global section of SAM template

Based on the Link expecting tags to be supported in the global section but it is not working
Status:
FAILED - Transform AWS::Serverless-2016-10-31 failed with: Invalid Serverless Application Specification document. Number of errors found: 18. Resource with id [abcd] is invalid. Type of property 'Tags' is invalid.

@ramanganapathy Can you please supply the relevant snippets to help aid us in understanding what your template looks like? The Globals section is probably enough but feel free to add extra context if you feel it may be useful.

`---
AWSTemplateFormatVersion: 2010-09-09
Transform: 'AWS::Serverless-2016-10-31'
Parameters:
SecurityGroupIds:
Type: ListAWS::EC2::SecurityGroup::Id
SubnetIds:
Type: ListAWS::EC2::Subnet::Id
Globals:
Api:
MethodSettings: [{
"LoggingLevel": "INFO",
"MetricsEnabled": True,
"DataTraceEnabled": True,
"ResourcePath": /*,
"HttpMethod": *,
}]
Function:
Runtime: java8
VpcConfig:
SecurityGroupIds: !Ref SecurityGroupIds
SubnetIds: !Ref SubnetIds
MemorySize: 1536
CodeUri: ./
Tracing: Active
AutoPublishAlias: live
Tags:
-
Key: AppCodeTag
Value: Testing
Resources:
GetGreeting
Type: AWS::Serverless::Function
Properties:
Handler: com.test.handler.GetGreetingHandler
Role:  arn:aws:iam::xxxxxxxxxxx
Events:
GetEvent:
Type: Api
StageName: Prod
Properties:
Path: /api/greet
Method: get
`

@ramanganapathy This is an issue with your template. You are defining tags following the CloudFormation Documentation not SAM. SAM has a simplification of how you define Tags for resources and will produce the correct 'vanilla' CloudFormation. Here is an example from our docs and the property is explained here.
For you example, you should be defining Tags like below. We will turn it into what you have currently and add it to the SAM generated Lambda Function Resource:
Tags:
      AppCodeTag: Testing

Thank you very much. Working great as expected.
On a side note when deploying through SAM if I specify stage (mystage) then I see three stages created. They are Stage, Prod and mystage. Also I dont find a way to remove unwanted stages that come default. I saw some similar issues around this topic. Is there a fix available for this

@ramanganapathy Unfortunately no. There is no solution yet to remove the extra Stage. Follow #191 for updates.
I am closing this issue for now because your question is answered


Fix 182

Resolves #182
This is a one-line change in actual web app code. The only other changes are:

A fairly involved test case to catch the bug caught in #182
changing the tests to run with py.test (because it's just better)
some insignificant commit history that got it while troubleshooting a Heroku problem.

cc @MattHJensen


python38Packages.PyChromecast: 9.3.1 -> 9.4.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.PyChromecast is: "Library for Python to communicate with the Google Chromecast"
meta.homepage for python38Packages.PyChromecast is: "https://github.com/home-assistant-libs/pychromecast"
meta.changelog for python38Packages.PyChromecast is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 9.4.0 with grep in /nix/store/paib41wxrx8g2g7b6g47c9677aq2lqhw-python3.8-PyChromecast-9.4.0

found 9.4.0 in filename of file in /nix/store/paib41wxrx8g2g7b6g47c9677aq2lqhw-python3.8-PyChromecast-9.4.0

Rebuild report (if merged into master) (click to expand)

9 total rebuild path(s)

5 package rebuild(s)

5 x86_64-linux rebuild(s)
4 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
gnomecast
home-assistant
mkchromecast
python38Packages.PyChromecast
python39Packages.PyChromecast

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/paib41wxrx8g2g7b6g47c9677aq2lqhw-python3.8-PyChromecast-9.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.PyChromecast https://github.com/r-ryantm/nixpkgs/archive/76e868c4e4781e653365af41e79aa82eafdc198d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/paib41wxrx8g2g7b6g47c9677aq2lqhw-python3.8-PyChromecast-9.4.0
ls -la /nix/store/paib41wxrx8g2g7b6g47c9677aq2lqhw-python3.8-PyChromecast-9.4.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

home-assistant

4 packages built:

gnomecast
mkchromecast
python38Packages.PyChromecast
python39Packages.PyChromecast

Maintainer pings
cc @abbradar for testing.

Breaks home-assistant:
FAILED tests/components/cast/test_home_assistant_cast.py::test_service_show_view[pyloop]

Updated to 10.1.1 in https://github.com/NixOS/nixpkgs/pull/147366


No longer working

I set it up and its working at first then it suddenly stopped working

Can you please provide more information so I can check? For e.g. The forked repository, site url, etc.

The PWA is now working but it is not popping up for add to home screen
instead I will have to click the menu button at the top corner of my
browser to be able to install it.
Website: https://www.eclecticstreams.com.ng
GitHub: EclecticStreams/blogger-pwa-github
On Thu, Feb 22, 2024, 16:42 Deo Kumar @.***> wrote:

Can you please provide more information so I can check? For e.g. The
forked repository, site url, etc.
—
Reply to this email directly, view it on GitHub
https://github.com/kumardeo/blogger-pwa-github/issues/3#issuecomment-1959719079,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFYHHQ45RGQMJBGFWOSIIHLYU5RQFAVCNFSM6AAAAABDR7AA7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJZG4YTSMBXHE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Looks like the manifest.json you changed is invalid json. Please make sure that json is valid, so that browser can parse it.
https://github.com/eclecticStreams/blogger-pwa-github/blob/7f6e326615e7b82fb5e69f61d05505f048e05fb9/app/manifest.json#L10-L12
You forgot to add a comma (,) after categories array.

There are multiple issues in the manifest.json file, you need to add comma after the handle_links:
https://github.com/eclecticStreams/blogger-pwa-github/blob/ad0780ea0345b980f55439be553070d59464c484/app/manifest.json#L149
You can validate your json here: https://jsonlint.com
After validating your json, commit the changes and clear cache of the site in browser.

I will check everything again and add the appropriate commas.
I'm add all those code because I want to package it to APK
On Fri, Feb 23, 2024, 14:39 Deo Kumar @.***> wrote:

There are multiple issues in the manifest.json file, you need to add comma
after the handle_links:
https://github.com/eclecticStreams/blogger-pwa-github/blob/ad0780ea0345b980f55439be553070d59464c484/app/manifest.json#L149
You can validate your json here: https://jsonlint.com
After validating your json, commit the changes and clear cache of the site
in browser.
—
Reply to this email directly, view it on GitHub
https://github.com/kumardeo/blogger-pwa-github/issues/3#issuecomment-1961345297,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFYHHQY5N4O566FURBSVXUTYVCLYHAVCNFSM6AAAAABDR7AA7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRRGM2DKMRZG4
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

I've added all the necessary commas and it's now showing in
https://www.eclecticstreams.com.ng/app/manifest.json
I presume it's now valid.
I still have some questions.

How do I make use of the notification, is it that it will automatically
notify all my PWA user when I send via one signal?
How do I prompt user to install our app or add to home screen?
How do I add offline support to my PWA?

On Sat, Feb 24, 2024, 18:41 Eclectic Data Plug @.***>
wrote:

I will check everything again and add the appropriate commas.
I'm add all those code because I want to package it to APK
On Fri, Feb 23, 2024, 14:39 Deo Kumar @.***> wrote:

There are multiple issues in the manifest.json file, you need to add
comma after the handle_links:
https://github.com/eclecticStreams/blogger-pwa-github/blob/ad0780ea0345b980f55439be553070d59464c484/app/manifest.json#L149
You can validate your json here: https://jsonlint.com
After validating your json, commit the changes and clear cache of the
site in browser.
—
Reply to this email directly, view it on GitHub
https://github.com/kumardeo/blogger-pwa-github/issues/3#issuecomment-1961345297,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFYHHQY5N4O566FURBSVXUTYVCLYHAVCNFSM6AAAAABDR7AA7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRRGM2DKMRZG4
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

You forgot one step in the tutorial, where you have to add the following in the head section:
<script async="true" defer="true" src="/app/pwa.js" type="module"></script>

Go through the post one more time and make sure you did everything as stated in the post.

Reply my messages please
On Monday, February 26, 2024, Eclectic Data Plug @.***>
wrote:

I've seen so many code on your site I want to add to my blogger website
and it's all requesting me to paste css code over the skin.
Won't it affect each other if I add another css code over it
On Monday, February 26, 2024, Eclectic Data Plug <
@.***> wrote:

I've added it already.
Or how do I identify if I'm using amp template or non amp template
On Sunday, February 25, 2024, Deo Kumar @.***> wrote:

You forgot one step in the tutorial, where you have to add the following
in the head section:

Go through the post one more time and make sure you did everything as
stated in the post.
—
Reply to this email directly, view it on GitHub
https://github.com/kumardeo/blogger-pwa-github/issues/3#issuecomment-1962802281,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFYHHQYDQFAMQECMB6BJRR3YVKXSTAVCNFSM6AAAAABDR7AA7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRSHAYDEMRYGE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

I visited your site, you are missing with things like adding the javascript (for non amp template). Once you load the pwa.js, service workers will be registered which allows you to send background notifications, offline page, app installation popup, etc.
A success info is logged by the javascript on successful registration. After making sure you did everything in tutorial, check the browser console for logs.

do you mean this section? if yes ive added it already
On Wed, Feb 28, 2024 at 8:27 PM Deo Kumar @.***> wrote:

I visited your site, you are missing with things like adding the
javascript (for non amp template). Once you load the pwa.js, service
workers will be registered which allows you to send background
notifications, offline page, app installation popup, etc.
A success info is logged by the javascript on successful registration.
After making sure you did everything in tutorial, check the browser console
for logs.
—
Reply to this email directly, view it on GitHub
https://github.com/kumardeo/blogger-pwa-github/issues/3#issuecomment-1969695002,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFYHHQYDW2SO724YAZWAWVDYVYXR3AVCNFSM6AAAAABDR7AA7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRZGY4TKMBQGI
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

reply this also
On Mon, Feb 26, 2024 at 1:33 PM Eclectic Data Plug <
@.***> wrote:

I've seen so many code on your site I want to add to my blogger website
and it's all requesting me to paste css code over the skin.
Won't it affect each other if I add another css code over it
On Monday, February 26, 2024, Eclectic Data Plug <
@.***> wrote:

I've added it already.
Or how do I identify if I'm using amp template or non amp template
On Sunday, February 25, 2024, Deo Kumar @.***> wrote:

You forgot one step in the tutorial, where you have to add the following
in the head section:

Go through the post one more time and make sure you did everything as
stated in the post.
—
Reply to this email directly, view it on GitHub
https://github.com/kumardeo/blogger-pwa-github/issues/3#issuecomment-1962802281,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFYHHQYDQFAMQECMB6BJRR3YVKXSTAVCNFSM6AAAAABDR7AA7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRSHAYDEMRYGE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

The installation popup now appears. Please check it.
Confirm it if you are able to see the pop-up or 'Install app' button instead of 'Add to Homescreen'.

Yes. I changed it from above the  to above the .
Thanks
On Thursday, February 29, 2024, Deo Kumar @.***> wrote:

The installation popup now appears. Please check it.
Confirm it if you are able to see the pop-up or 'Install app' button
instead of 'Add to Homescreen'.
20240229_135940.jpg (view on web)
https://github.com/kumardeo/blogger-pwa-github/assets/86065483/e5d597fb-ce2f-4db8-9676-c04ccd200266
—
Reply to this email directly, view it on GitHub
https://github.com/kumardeo/blogger-pwa-github/issues/3#issuecomment-1970651221,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFYHHQ7GMF6BUAUBY2QHEPDYV3TURAVCNFSM6AAAAABDR7AA7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQGY2TCMRSGE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

I've seen so many code on your site I want to add to my blogger website and
it's all requesting me to paste css code over the skin.
it won't affect each other if I add another css code over it
On Thursday, February 29, 2024, Deo Kumar @.***> wrote:

The installation popup now appears. Please check it.
Confirm it if you are able to see the pop-up or 'Install app' button
instead of 'Add to Homescreen'.
20240229_135940.jpg (view on web)
https://github.com/kumardeo/blogger-pwa-github/assets/86065483/e5d597fb-ce2f-4db8-9676-c04ccd200266
—
Reply to this email directly, view it on GitHub
https://github.com/kumardeo/blogger-pwa-github/issues/3#issuecomment-1970651221,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFYHHQ7GMF6BUAUBY2QHEPDYV3TURAVCNFSM6AAAAABDR7AA7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQGY2TCMRSGE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Closing issue since PWA is working as expected.

Ok, thanks for the update.
On Thu, Feb 29, 2024, 15:09 Deo Kumar @.***> wrote:

Closing issue since PWA is working as expected.
—
Reply to this email directly, view it on GitHub
https://github.com/kumardeo/blogger-pwa-github/issues/3#issuecomment-1971222480,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFYHHQ7W6IGNFCKF2W7XIIDYV43ABAVCNFSM6AAAAABDR7AA7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZRGIZDENBYGA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Small fix for unhandled exceptions during net.connect issue

Fixed it

I try to publish a new version on npm in the next hours

Thank you! That's a great library!


Preprocessor refactor

This PR addressed #1224 by greatly simplifying how stream parameters can be renamed and how stream preprocessing is implemented (when necessary).
The rename suggestion from that issue has been implemented exactly as suggested but after discussion with @philippjfr and @jbednar, it was decided that we don't really need explicit preprocessor hooks. Instead, the streams that require it can implement the preprocess method (which occurs before stream renaming) so transform the stream values as necessary.
I would still like a better name than rename and although I personally like remap more, I know this isn't the majority opinion. Consider
PositionXY(rename={'x':'x1', 'y':'y1'}, x=2)

and
PositionXY(remap={'x':'x1', 'y':'y1'}, x=2)

I feel the latter conveys the idea that x will be called x1 on the output better. Any other suggestions?
Action items:

[x] Remove old preprocessor system
[x] Offer new simplified means of preprocessing streams
[x]  Implement rename constructor argument and method
[x] Update PlotSize stream with a preprocess method
[x] Add unit tests
[x] Update tutorials Edit: postponed till a later PR

After some discussion, we decided to rename the preprocess method to transform and have it set the transformed parameters in the update method. The PlotSize stream now implements scaling based on this approach.

I will update the tutorial material once I've finished going through DynamicMap. The tests should pass and this PR is ready for review.

Looks good, just update/add some docstrings.

Updated as suggested. Tests are passing for Python 2.7 and the Python 3 tests should pass soon,

The pr build just passed on the commit before I added the docstrings. I think it is ready to merge.

Merging.


Module 'url_launcher' not found when building app in Xcode

I'm trying to build my Flutter app in Xcode but I get a "module 'url_launcher' not found" error every time.

I'm opening the Runner.xcworkspace file and starting the build. After a few seconds, I get that error.
I've tried flutter clean, pod install, pod update, pod repo update, removing the podfiles and creating new ones,... nothing seems to work. I did however notice that when I run flutter clean, then flutter pub get, and then pod install, it installs Flutter and url_launcher but with very early version numbers:

Also, when I manually start an IOS simulator and run my project from VSCode, it does successfully build the app and install / run it on the simulator.
To test it yourself,  you can clone my project from here: https://github.com/MrBananaPants/StarTracker

[✓] Flutter (Channel stable, 1.22.6, on macOS 11.2.2 20D80 darwin-arm, locale
    en-BE)
    • Flutter version 1.22.6 at /Users/joranvancoillie/tools/flutter
    • Framework revision 9b2d32b605 (5 weeks ago), 2021-01-22 14:36:39 -0800
    • Engine revision 2f0af37152
    • Dart version 2.10.5

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/joranvancoillie/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin installed
    • Dart plugin version 201.9317
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[!] Connected device
    ! No devices available

! Doctor found issues in 1 category.

Hi @MrBananaPants
First, make sure you're executing flutter build ios before Xcode and target the same IOS in Xcode and Podfile, you're targeting iOS 12 in Xcode, iOS 9 in Podfile (not sure if that's the cause, just noticed), and then build from Xcode
Changing iOS target from 12 to 9 (match Podifle) and applied my own stream ID, flutter build ios and Xcode archive is successful in your project

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.6, on macOS 11.2.2 20D80 darwin-x64, locale en-GB)
    • Flutter version 1.22.6 at /Users/tahatesser/Code/flutter_stable
    • Framework revision 9b2d32b605 (5 weeks ago), 2021-01-22 14:36:39 -0800
    • Engine revision 2f0af37152
    • Dart version 2.10.5
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, set ANDROID_SDK_ROOT to that location.
      You may also want to add it to your PATH environment variable.
[!] Xcode - develop for iOS and macOS (Xcode 12.4)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    ✗ CocoaPods not installed.
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To install:
        sudo gem install cocoapods
[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
[✓] VS Code (version 1.53.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.19.0
[✓] Connected device (1 available)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E • ios • iOS 14.4
! Doctor found issues in 3 categories.

Hi, I ran flutter build ios and tried to build it from Xcode afterwards but got the same error. The targeting error is fixed now because Xcode suggested the changes:

Hi @MrBananaPants
As mentioned in https://github.com/flutter/flutter/issues/76860#issuecomment-786696773, I can build your project with those minor changes. The problem might in your pod cache
Run these in the ios directory of your project
rm -rf Pods
rm -rf Podfile.lock
rm -rf ~/.pub-cache/hosted/pub.dartlang.org/
pod cache clean --all
flutter clean
flutter pub get
pod repo update

Thank you

@TahaTesser I ran all those commands but still get the same module not found error. A friend of mine who also tried to build the repository through Xcode also got the same error.

@MrBananaPants looks like you are on apple silicone. Try run app from terminal flutter run

@densa Yes I am on Apple Silicone. Using flutter run, I am able to run my project on an IOS simulator but it doesn't work when building it through Xcode. However, it did work a week or so ago through Xcode and a friend of mine who has an Intel MacBook Air also gets the same module not found error so it's not related to Apple Silicone.

Hi @MrBananaPants
Can you please try flutter pub cache repair  and flutter clean then run the app
Thank you

@TahaTesser I've also tried that. Still the same error in Xcode.

Hi @densa
Are you SURE you'e opening Runner.xcworkspace and not Runner.xcodeproj?

Yes, I'm 100% sure
On Tue, 2 Mar 2021, 12:38 Taha Tesser<EMAIL_ADDRESS>wrote:

Hi @densa https://github.com/densa
Are you SURE you'e opening Runner.xcworkspace and not Runner.xcodeproj?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/76860#issuecomment-788844595,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ434NXPMU2CWUUOZXRWLZTTBTE35ANCNFSM4YINSRCQ
.

I think you got error because when you run from Xcode it trying build for arm64 but can't. if you look into flutter run script you will see that they add -arch x86_64 param
https://github.com/flutter/flutter/blob/74d58105d1563e130ff196eac0f195def8214b10/packages/flutter_tools/lib/src/ios/mac.dart#L253

@MrBananaPants
Can you please try the above solution https://github.com/flutter/flutter/issues/76860#issuecomment-788849444
Thanks

@TahaTesser how do I tried that solution? it's just a line of code I can't execute in the terminal.

@MrBananaPants you can try this https://github.com/flutter/flutter/issues/64502#issuecomment-759165857

@densa I tried it but it still gave me the same error.

Hi @MrBananaPants
Finally, glad you solved it, I don't have M1 so I wasn't able to verify this, closing as a duplicate of https://github.com/flutter/flutter/issues/64502#issuecomment-759165857
Thank you

i am stuck at this last few hours!
It builds properly on simulaor ..builds error in iphone 8..i did everything entioned above! nothing solved it!
any help!!
• Flutter version 2.3.0-17.0.pre.121 a
• Dart version 2.14.0
• Xcode 12.5, Build version 12E262
• CocoaPods version 1.10.1
MacBook Pro (Retina, 13-inch, Late 2013)

Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Permission Denied to Config, along with response error "Yes" and then flatlining.

Your OS (including version) where you are running AlexaPi:
NOOVA 2.4.5, Rasbian

Your hardware platform and model you are running on:
Raspberry Pi 3

Python release (python2 --version):
Python 2.7

Description of problem:
Only prompted response during debugging and not while running when status is active. More often than not the only response is a "Yes" and then nothing in the debugging more. While trying to figure out the issue I can not access the configurations page it just prompts "permission denied". Any advice?
Problem-relevant config.yaml entries:
config entries restricted

Additional info:
Here is the status update when running considering I can't access the configs
● AlexaPi.service - Alexa client for all your devices
   Loaded: loaded (/usr/lib/systemd/system/AlexaPi.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2018-02-15 18:48:40 UTC; 40s ago
     Docs: https://github.com/alexa-pi/AlexaPi/wiki
 Main PID: 2029 (python)
   CGroup: /system.slice/AlexaPi.service
           ├─2029 /usr/bin/python /opt/AlexaPi/src/main.py --daemon
           └─2041 /usr/bin/pulseaudio --start --log-target=syslog

Feb 15 18:48:44 raspberrypi python[2029]: ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer returned error: No such file or d
Feb 15 18:48:44 raspberrypi python[2029]: ALSA lib conf.c:4996:(snd_config_expand) Args evaluate error: No such file or directory
Feb 15 18:48:44 raspberrypi python[2029]: ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM bluealsa
Feb 15 18:48:44 raspberrypi python[2029]: ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave
Feb 15 18:48:44 raspberrypi python[2029]: connect(2) call to /tmp/jack-999/default/jack_0 failed (err=No such file or directory)
Feb 15 18:48:44 raspberrypi python[2029]: attempt to connect to server failed
Feb 15 18:48:45 raspberrypi python[2029]: INFO: Checking Internet Connection ...
Feb 15 18:48:45 raspberrypi python[2029]: INFO: Connection OK
Feb 15 18:48:45 raspberrypi python[2029]: INFO: AVS token: Requesting a new one
Feb 15 18:48:46 raspberrypi python[2029]: INFO: AVS token: Obtained successfully

In your security profile on the amazon developer page add both http and https links into your allowed origins and allowed return urls. Http links are needed for authentication while https links are needed for alexa to not just ignore your commands

Thanks, that solved one of the problems. I'm no longer getting the errors in my status but she still won't respond when actively and I can still not access my configuration file. Any suggestions?

You have to setup your audio PCMs:
List them with aplay -L and change it in the config:
output: "alsa"
output_device: "plughw:YOURDEVICE"

On Rapsberry Pi, you may have to follow this (with SoX, not VLC at the end)

Due to a large number of issues, this one is going to be closed because we think your problem is solved.
If you still have any problem, please feel free to re-open it!


Cannot apply entries in single node cluster

Related to #68 - when developing locally, it's common to test with a single node cluster. It seems the commit index is never incremented; perhaps I mis-configured something? Looking through the code, though, it seems like it's behaving as expected: we increment the commit index only when receiving append entries request, which the leader obviously doesn't send to itself. I think this could be solved by using the leader's own index to calculate the quorum.
Did I miss something or is this the intended behaviour?
EDIT: as a side note, using the leader's own match index when computing quorum has a nice side effect of allowing the append to the local log to be asynchronous, i.e. we can start replicating before the entry has been appended to the local log (this is described in section 10.2.1 in the original thesis)

Closing this as PR #71 fixed this issue


release procedure update / twine check / Project pre-registration is no longer required

$ python setup.py register sdist bdist_wheel --universal
running register
running egg_info
creating semver.egg-info
writing semver.egg-info/PKG-INFO
writing dependency_links to semver.egg-info/dependency_links.txt
writing entry points to semver.egg-info/entry_points.txt
writing top-level names to semver.egg-info/top_level.txt
writing manifest file 'semver.egg-info/SOURCES.txt'
reading manifest file 'semver.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'semver.egg-info/SOURCES.txt'
running check
warning: Check: This command has been deprecated. Use `twine check` instead: https://packaging.python.org/guides/making-a-pypi-friendly-readme#validating-restructuredtext-markup

The project's long description is valid RST.
Registering semver to https://upload.pypi.org/legacy/
Server response (410): Project pre-registration is no longer required or supported, upload your files instead.
WARNING: Registering is deprecated, use twine to upload instead (https://pypi.org/p/twine/)
running sdist
creating semver-2.9.0
creating semver-2.9.0/semver.egg-info
copying files to semver-2.9.0...
copying LICENSE.txt -> semver-2.9.0
copying MANIFEST.in -> semver-2.9.0
copying README.rst -> semver-2.9.0
copying semver.py -> semver-2.9.0
copying setup.cfg -> semver-2.9.0
copying setup.py -> semver-2.9.0
copying test_semver.py -> semver-2.9.0
copying semver.egg-info/PKG-INFO -> semver-2.9.0/semver.egg-info
copying semver.egg-info/SOURCES.txt -> semver-2.9.0/semver.egg-info
copying semver.egg-info/dependency_links.txt -> semver-2.9.0/semver.egg-info
copying semver.egg-info/entry_points.txt -> semver-2.9.0/semver.egg-info
copying semver.egg-info/top_level.txt -> semver-2.9.0/semver.egg-info
Writing semver-2.9.0/setup.cfg
creating dist
Creating tar archive
removing 'semver-2.9.0' (and everything under it)
running bdist_wheel
running build
running build_py
creating build
creating build/lib
copying semver.py -> build/lib
installing to build/bdist.macosx-10.9-x86_64/wheel
running install
running install_lib
creating build/bdist.macosx-10.9-x86_64
creating build/bdist.macosx-10.9-x86_64/wheel
copying build/lib/semver.py -> build/bdist.macosx-10.9-x86_64/wheel
running install_egg_info
Copying semver.egg-info to build/bdist.macosx-10.9-x86_64/wheel/semver-2.9.0-py3.7.egg-info
running install_scripts
adding license file "LICENSE.txt" (matched pattern "LICEN[CS]E*")
creating build/bdist.macosx-10.9-x86_64/wheel/semver-2.9.0.dist-info/WHEEL
creating 'dist/semver-2.9.0-py2.py3-none-any.whl' and adding 'build/bdist.macosx-10.9-x86_64/wheel' to it
adding 'semver.py'
adding 'semver-2.9.0.dist-info/LICENSE.txt'
adding 'semver-2.9.0.dist-info/METADATA'
adding 'semver-2.9.0.dist-info/WHEEL'
adding 'semver-2.9.0.dist-info/entry_points.txt'
adding 'semver-2.9.0.dist-info/top_level.txt'
adding 'semver-2.9.0.dist-info/RECORD'
removing build/bdist.macosx-10.9-x86_64/wheel
(base) ✔ ~/github/scls19fr/python-semver [master|✔]
16:18 $ twine upload dist/*
Uploading distributions to https://upload.pypi.org/legacy/
Uploading semver-2.9.0-py2.py3-none-any.whl
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 16.8k/16.8k [00:02<00:00, 7.29kB/s]
Uploading semver-2.9.0.tar.gz
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 20.8k/20.8k [00:01<00:00, 12.7kB/s]

Hi @scls19fr probably you know that already, but I couldn't find semver on PyPI anymore. Wasn't it on https://test.pypi.org/project/semver/ ?

I think, this is already solved with the new(?) setup.cfg/pyproject.toml that was introduced some ago (probably in commit cbd4335f).
I close this issue for the time being. If you have concerns or further ideas, just reopen it and we can discuss the details. :slightly_smiling_face:
Many thanks!


Casos de uso 01 y 03

clase Jugador

Codecov Report
Patch coverage: 57.14% and project coverage change: -52.64 :warning:

Comparison is base (a8997be) 100.00% compared to head (0fbb203) 47.36%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@               Coverage Diff               @@
##             entrega1       #4       +/-   ##
===============================================
- Coverage      100.00%   47.36%   -52.64%
- Complexity          5       10        +5
===============================================
  Files               2        6        +4
  Lines              10       38       +28
===============================================
+ Hits               10       18        +8
- Misses              0       19       +19
- Partials            0        1        +1

Impacted Files
Coverage Δ

src/main/java/edu/fiuba/algo3/Jugador.java
53.84% <53.84%> (ø)

...du/fiuba/algo3/NoDisponeDeSuficientesCreditos.java
100.00% <100.00%> (ø)

... and 2 files with indirect coverage changes

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


”Vrata” is listed in the drop-down menu

Description:
"Vrata" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Vrata" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Vrata, MEHEDINȚI (Vrata)".


feat: using workload identity federation

Is your feature request related to a problem? Please describe.
The current implementation relies on long lived credentials from google cloud.
Describe the solution you'd like
We could use Workload Identity federation described https://cloud.google.com/iam/docs/workload-identity-federation-with-other-clouds
Describe alternatives you've considered
None
Additional context
None

I can see it's already implemented 😅


Tyler bird patch 1

I tried to use your Library with ESP32 but there were error "error: ISO C++ forbids declaration of 'begin' with no type [-fpermissive]"
this can be solved by adding void as function return parameter in .cpp and .h

Thanks!


Remove iceberg-presto-runtime that is no longer used.

Fixes #256 and fixes #160.

I guess this fixes #160  too.

What jar presto should include as a dependency?

@vrozov, engines typically depend on iceberg-core, plus add-on modules like iceberg-parquet or iceberg-orc. It is unusual to have a dependency like this one, since the code for Presto integration is in Presto (instead of in Iceberg like iceberg-spark).

I don't think that Presto will be able to use iceberg-core dependency directly due to the dependency on a different guava (and likely incompatible) version. It will also likely require iceberg-hive and won't be able to use it either due to the incompatible hive version. I guess either iceberg or presto (or any other project that adds iceberg support) will have to create 'runtime' uber/shade jar. In case it is done in iceberg, the same does not need to be repeated in any other projects that may be interested in supporting iceberg.

@vrozov . Presto provides an SPI mechanism to load connectors. All jars that a connector needs are loaded in a separate classloader so there's complete classpath isolation between Presto and  its plugins (connectors) https://prestodb.github.io/docs/current/develop/spi-overview.html

@rdsr I am aware of the Presto SPI mechanism for plugins. Problem is that it will not help as the issue is with the version conflicts within a plugin classloader, not across different plugins.

@vrozov, Iceberg depends on an older version of Hive, but the calls we use are provided by newer versions. Hive provides backward compatibility on those calls. Projects like Presto can depend on Iceberg and use version management to update the version that is actually used.
Guava is similar. We want to depend on a new version, but only use calls that are compatible with most versions of Guava.

@rdblue Unfortunately it is not the case and Hive does not provide backward compatibility (and is not required based on semver). The signature of HiveMetaStoreClient changed from HiveConf to Configuration in 3.x and there is no backward-compatible constructor that takes HiveConf in 3.x.
The same for guava. In the long run, it is not possible to provide a guarantee that nobody introduces the usage of an incompatible class or method. The only way to play safely is to shade guava due to it's wide acceptance and limited backward compatibility in early versions.

@vrozov, good to know about the HiveMetaStoreClient constructor. We can update the constructor call to work in both 1.2.1 and 3.x variants. Sounds like the justification for Guava is that this could happen with that library as well. I agree with that, and we can either avoid calls that are problematic or use reflection for shims.
Either way, I'm not sure that it is necessary to create a shaded Presto runtime library. On #256, I asked whether Presto actually used this and the answer was no. If Presto needs one, we can add it back. Otherwise, I think we should publish normal dependencies and let Presto handle their transitive dependencies. If there is a problem, we are flexible and can work with that community to fix it.

@rdblue Presto does not use iceberg libraries as Presto still does not support iceberg. There is an open PR to add such support and, I guess, the question is whether the PR uses iceberg-presto-runtime or iceberg-api, iceberg-core and other iceberg libraries directly. Indeed, the PR does not use iceberg-presto-runtime and my educated guess (that is based on adding iceberg support to presto  on a private fork where I did not use iceberg-presto-runtime either) is that this was done due to a wrong shading in iceberg-presto-runtime (there is a large number of classes that are included into iceberg-presto-runtime without being relocated, causing conflicts with presto own dependencies).
I still don't see anything in the PR that would solve HiveMetaStoreClient backward compatibility issue (note that there may be more incompatibilities in hive, just that it breaks on the very first call to hive), but I may be missing something. Possibly @electrum can clarify how hive version conflict is resolved in the PR.
Yes, while it is possible to resolve all such conflicts one by one after they are discovered (and likely they won't be discovered till it blows up during run-time) or it can be solved all in once by shading and creating uber run-time jar. Another option is to use something similar to animal-sniffer-maven-plugin to ensure API compatibility, but I don't know if gradle provides such ability.

If you'd like to create a generic runtime Jar that shades and relocates dependencies, that would be great. It doesn't need to be specific to Presto, though.

@vrozov Presto does not use any of the metastore code from the Iceberg library. Instead, it uses its existing metastore code from the Hive connector which already has config that fits with Presto, handles Kerberos security, allows alternate metastore implementations such as Glue, etc. The same is true for other Iceberg code including file reading and writing.

@electrum Problem is not whether presto uses the hive metastore code from the iceberg. Problem is that iceberg uses the hive metastore 1.x API and it is not compatible with hive 3.x API that presto provides at runtime.

@vrozov It doesn’t matter because Presto doesn’t use that code. The classes aren’t referenced at runtime.
BTW, just to clarify, the Presto engine doesn’t provide anything metastore or Hive related at runtime. The Iceberg plugin (like all plugins) is loaded in an isolated class loader and has complete control over all of its dependencies and versions. It is choosing to reuse code and dependencies from the Hive plugin.

@electrum What classes are not referenced at runtime? Iceberg org.apache.iceberg.hive.HiveClientPool has compile time dependency on  org.apache.hadoop.hive.metastore.HiveMetaStoreClient and at run-time it is provided by io.prestosql.hive:hive-apache. What do I miss here?

BTW, just to clarify, the Presto engine doesn’t provide anything metastore or Hive related at runtime. The Iceberg plugin (like all plugins) is loaded in an isolated class loader and has complete control over all of its dependencies and versions. It is choosing to reuse code and dependencies from the Hive plugin.

I am aware of the Presto SPI mechanism for plugins. Problem is that it will not help as the issue is with the version conflicts within a plugin classloader, not across different plugins.

HiveClientPool and related are not used in Presto. You can see the code: https://github.com/prestosql/presto/pull/1067

[Presto] uses its existing metastore code from the Hive connector which already has config that fits with Presto, handles Kerberos security, allows alternate metastore implementations such as Glue, etc.

@electrum, how did you add Glue support for Iceberg? Is that something that we should support in this repository so that Spark can read/write tables tracked in Glue? It would be great to be able to reuse what you guys already have done here.

@rdblue The Presto way is likely too complex for the Iceberg library, especially given that it only uses a few metastore calls, but I can share how it works.
Presto has a HiveMetastore interface that uses its own model objects such as Table. Glue implements the interface directly as GlueMetastore using the AWS SDK for Java.
Presto also has a ThriftMetastore interface that uses the generated libthrift classes such as org.apache.hadoop.hive.metastore.api.Table from the Apache Hive dependency (except for table and column statistics classes which don't exist in Hive). The implementation ThriftHiveMetastore handles retry and JMX statistics collection, maps Thrift exceptions into Presto exceptions, and some other basic mapping including null to Optional.
Thrift implements HiveMetastore using BridgingHiveMetastore which translates to the ThriftMetastore interface and converts the model objects using ThriftMetastoreUtil.
Iceberg needs a smaller number of methods, but the complexity comes from the model objects. Doing a generic conversion from org.apache.hadoop.hive.metastore.api.Table to  com.amazonaws.services.glue.model.Table seems feasible, since the structures are very similar, but much of the code would go unused (e.g., Iceberg doesn't use Hive partitioning or bucketing). It might be cleaner to duplicate the logic at a higher level using the AWS Glue client directly.

@electrum The PR has 46 files added/modified, and the only relevant to the discussion in this thread class is io.prestosql.iceberg.HiveTableOperations, so it was quite easy to miss that file. Anyway, would not it be better to change iceberg org.apache.iceberg.hive.HiveTableOperations to allow Presto/Drill/Spark to provide it's own Hive metastore client, instead of re-implementing that class in Presto, especially that BaseMetastoreTableOperations that HiveTableOperations extends is not part of the iceberg api library?

@vrozov I considered that, but the problem is, what would the metastore client API look like? As explained in the previous comment, the Presto HiveMetastore interface uses Presto model objects. Trying to write an adapter layer would likely be more complicated and more code than the ~200 lines of the current HiveTableOperations class.
More generally, I don't agree that trying to use the same code everywhere is the always the best choice. One of the big advantages of Iceberg is that it's designed to be an open standard with a specification. You need multiple implementations (and compliance tests) to keep the specification honest.
As for BaseMetastoreTableOperations, I agree that extending it is problematic (as is subclassing in general). At this point, very little code is used from it, and its design forces some strangeness on the Presto subclass, so it's probably best if the Presto code inlines it.

@electrum, thanks for the explanation. How do you implement the table lock operation for Glue? Is that supported directly in the AWS SDK? If so, we should probably add an iceberg-glue module to support it from Spark.


Meeting Time

The google form of meeting（With Ta）:
https://docs.google.com/spreadsheets/d/16qtcvIdymJGY1c4LTGQZ-NT-5nSBUM7hSVy-uZkoDws/edit#gid=0
Eric from NRC biweekly:
Oct 19th from 11 am to 12 pm.
Nov 2th from 11 am to 12 pm.
Daniel biweekly:
October 12, 1:00pm-1:30pm
October 26, 1:00pm-1:30pm
Rough timeline:
10.30: Milestone one- Title, Headers and Subheaders
11.15: MileStone two- Images
11.30: MileStone three- Translations
Questions:
Oct 19th (for Eric) :
Milestone 1:Title, Headers and Subheaders
Does it need to be stored in the back-end/database?
Headers and subheaders are already editable, but there is not any test about this feature. Do we need to add any test cases?
Is the editable page title feature working now?
Milestone 2
same as 1(back-end)
image format and size
Milestone 3:
Should we use a third-party translation API? Is there a recommended translation API?

Questions for 3rd meeting:

How to make the read-along web component rerender?
Is it possible to pass a base64 image to the <graphics/> node?
Is it appropriate to upload images to the front-end assets folder?


WIP: Closes #604: Re-enable E1120

For now I am just opening this to see which tests fail. Then I'll make those tests pass.

@AlexeyKurakin do you know how I should fix this failure in examples/nips17_adversarial_competition/eval_infra/validation_tool/validate_and_copy_submissions.py?
On line 174 it has metadata = self.base_validator.validate_submission(local_path). The call needs to pass in a second argument, submission_type. But we get submission_type out of metadata so it's not available to pass yet.
Also, there are two similarly named files: examples/nips17_adversarial_competition/eval_infra/validation_tool/validate_submission_lib.py and   examples/nips17_adversarial_competition/dev_toolkit/validation_tool/validate_submission_lib.py. The other one doesn't require a submission_type argument.

I was able to fix it by renaming file: https://github.com/tensorflow/cleverhans/pull/709


[service] Run MoveOS as a server

Run MoveOS as a server.

Run MoveOS in a thread( or Actor?)
Communicate with MoveOS through messages
Provide a command to start the server, mos server ?

mos client is only for MoveOS，and mos is party of Rooch，so I think mos server is appropriate

MoveOS server should be a thread，when MoveOS handles message，it genrate an actor or channel is ok

mos is an abbreviation for MoveOS.
mos server provide a local move execution runtime for the developer.
Developers' usage steps can be imagined as follows:

Create a new Move project: Use the mos new command to create a new Move project with the necessary files and directories.

Write Move code: Write the Move source code for your dapp using your preferred text editor or Move development environment.

Build and test the Move bytecode: Use the mos build and mos test commands to compile the Move source code into bytecode and run tests to ensure that your code functions as expected.

Start a server process: Use the mos server command to start the server process.

Deploy the Move bytecode: Use the mos deploy command to deploy the Move bytecode to the MoveOS and make your dapp available for use.

Execute a Move function: Use the mos run command to execute a Move function in the server.

mos server should start a server process in local.
mos deploy can deploy the Move bytecode in local mos server if don't specific server, also can deploy to specified server address(e.g. Rooch Server).
mos run is similar to mos deploy, it needs to support default local and specified server addresses

I'd like to work on this.

I'd like to work on this.

As discussed at the last community developer meeting, We decided to make MoveOS to a pure library, and the command-line tool should be rooch.
Like:
rooch move new
rooch move build
rooch move test
rooch server
rooch move deploy
rooch move run

I'd like to work on this.

As discussed at the last community developer meeting, We decided to make MoveOS to a pure library, and the command-line tool should be rooch.
Like:
rooch move new
rooch move build
rooch move test
rooch server
rooch move deploy
rooch move run

Ok, I'll wait for #34 .


Unify multiplatform targets into named groups

This gives us more control over what targets are built for which parts of the codebase based on their type.
The big change is the drop of MacOS targets which were wholly unused. They will likely return at some point, along with new targets for common modules as well as for Compose UI, and this new grouping will make that easy to do.
Before:
$ gw build --dry-run | grep -c SKIPPED
7469

After:
$ gw build --dry-run | grep -c SKIPPED
6405

Refs #361

[x] CHANGELOG.md's "Unreleased" section has been updated, if applicable.

This is like half of what I actually want to build but I'm sick of waffling so this is a small step in that direction.


[Bug] Can tap through scanner screen on iOS

BUG REPORTS WITHOUT PROVIDING THESE INFORMATIONS WILL BE CLOSED DIRECTLY. DON'T REMOVE THE SECTIONS!
Describe the bug
On iOS I can tap through scanner screen. Android works fine.
To Reproduce
Steps to reproduce the behavior:

Open barcode scanner.
Tap on tapable widget underneath it.

Expected behavior
I shouldn't be able to tap through.
Screenshots
https://take.ms/wMyuR
Logs
N/A
Environment (please complete the following information):

[X] iOS: Tested on iPhone XR with iOS 13.4.1
[X] Emulator/Simulator: iPhone SE (1st generation).
Version of barcode_scan: 3.0.1 (reproduced in earlier versions as well).
Output of flutter --version:

Flutter 1.16.3 • channel unknown • unknown source
Framework • revision be3a4b37b3 (6 weeks ago) • 2020-03-26 18:08:05 -0700
Engine • revision b2bdeb3f0f
Tools • Dart 2.8.0 (build 2.8.0-dev.17.0 1402e8e1a4)

Additional context
N/A

This is happening here too. Any ideas on how to fix it?

It's still don't work for me too, Any news about this issue?

Ex: You have a textfield in screens. Then you turn on scanner. Scanner will overlap textfield. You can focus textfield through scanner although textfield invisible


Update virtual-network-injection-resources.md

Fixed a minor typo in the subnet notes here.

@dlepow
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


[Type checker] Compute correct contextual substitutions for local generics

When applying generic arguments to a local generic type within a generic
function, ensure that we correctly produce the contextual substitutions from
the generic function. Fixed with Pavel, who painstakingly tracked down
the bogus substitution.
Fixes SR-9954 / rdar://problem/48223824.

@swift-ci please smoke test and merge


Upgrade to npe2

This pull request upgrades napari-crop to the npe2 plugin engine.

Thanks for this @tdmorello! I haven't dived into npe2 yet. I heard that npe2 doesn't support menus. Do you know if the plugin still shows up in the Tools - Menu?

It does not!
I might close this for now before I troubleshoot. I am more interested in seeing the dask/zarr and multiscale abilities before upgrade to npe2.


Beta docs restructure planning chapter

I restructured almost all of the "Planning the new deployment chapter" except for the "Network" section because I felt that this PR was getting too big.
Jiri and Fabricio: Let me know if this PR is too big, and I'll create smaller ones in the future. And of course, please add your feedback to the PR if you see any errors.
Peer reviewers (writers): Please follow the peer review checklist: https://docs.google.com/document/d/1hxKJdhGNqSOTg6WrbYjJaQIWDu7x5cl2QRYJ7G0HFt8/edit

Based on the Adoption Peer Review Checklist (Beta), this looks good to me.


Deadline button

requesting pull request for issue 202 and issue 251 : create deadline button and set color on hover


Support dynamic endpoint options

I am working with a GraphQL API that requires authorization with a token (authorization header option passed with each request). With each session the token changes, and I have to manually update it in graphql.config.json. I have not yet found a way to pass e.g. process.env.ACCESS_TOKEN, but maybe there is some way to achieve that? If not, then it would be great to have node env variables to override at least headers in graphql.config.json, although it may not be possible, because the app and the plugin work in separate node environments...

So far the only thing that works for me is a node script updating the auth header in graphql.config.json on app start.

+1

See remote-schema-introspection for how v2 of the plugin supports this use case. You can specific API tokens via environment variables in the .graphqlconfig file as described in the  graphql-config documentation.
If you'd like to help test v2 the releases are found at https://github.com/jimkyndemeyer/js-graphql-intellij-plugin/releases
Best regards,
Jim.


WIP: GPU support for sheath-bc in stix miniapp

@mlstowell @christinamigliore
This PR adds the GPU support for the computation of the sheath boundary condition.

Some build errors from Travis CI that need to be resolved on this branch:
In file included from cold_plasma_dielectric_coefs.cpp:12:0:
cold_plasma_dielectric_coefs.hpp: In constructor ‘mfem::plasma::SheathImpedance::SheathImpedance(const mfem::ParGridFunction&, const mfem::BlockVector&, const mfem::BlockVector&, const mfem::BlockVector&, const mfem::ParFiniteElementSpace&, const mfem::ParFiniteElementSpace&, double, const mfem::Vector&, const mfem::Vector&, bool)’:
cold_plasma_dielectric_coefs.hpp:167:19: error: ‘mfem::plasma::SheathImpedance::masses_’ will be initialized after [-Werror=reorder]
    const Vector & masses_;
                   ^~~~~~~
cold_plasma_dielectric_coefs.hpp:157:9: error:   ‘bool mfem::plasma::SheathImpedance::realPart_’ [-Werror=reorder]
    bool realPart_;
         ^~~~~~~~~
cold_plasma_dielectric_coefs.cpp:443:1: error:   when initialized here [-Werror=reorder]
 SheathImpedance::SheathImpedance(const ParGridFunction & B,
 ^~~~~~~~~~~~~~~
cc1plus: all warnings being treated as errors
makefile:54: recipe for target 'cold_plasma_dielectric_coefs.o' failed
make[1]: *** [cold_plasma_dielectric_coefs.o] Error 1
make[1]: Leaving directory '/home/travis/build/mfem/mfem/miniapps/plasma'
makefile:430: recipe for target 'miniapps/plasma' failed
make: *** [miniapps/plasma] Error 2


Update OWNERS_ALIASES

What is changed and how it works?

Issue Number: Ref #17004

What's Changed:
add `zhangjinpeng87` into alias: `sig-critical-approvers-config-src` to approval tikv storage parts.

Related changes

[ ] PR to update pingcap/docs/pingcap/docs-cn:
[x] Need to cherry-pick to the release branch

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[x] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Release note

None

/cherry-pick release-8.2
/cherry-pick release-8.1
/cherry-pick release-7.5
/cherry-pick release-7.1
/cherry-pick release-6.5
/cherry-pick release-6.1

/cc  @kevin-xianliu @cfzjywxk @easonn7
PTAL

/hold
wait for more LGTMs.

/unhold
It's ready to merge.

/ok-to-test


View config not found

"react": "^16.3.0",
"react-native": "0.54.4",

I get this error when running:
<FastImage source={{ uri }} resizeMode={FastImage.resizeMode.contain} />

+1

+1

+1

i installed it using pod and it's working fine now.

Probably it's a linker error. I unlinked and linked the FastImage library in Xcode again, and it worked.

So instead of running react-native link you can set up it manually for now to get it to work.

getting this error, but only sometimes (ios). Seems to work fine. But in the release I keep seeing it from time to time. Sometimes during initial load of the app, but also happens when app is already loaded, using FastImage successfully and suddenly this happens (we get crash reports)
"react-native": "0.59.3",
"react-native-fast-image": "^5.2.0",


Updated ansible docs links to 2.4

Updated links to two Ansible 2.4 docs.
Docs issue: https://issues.redhat.com/browse/HCCDOC-1420
RHCLOUD issue: https://issues.redhat.com/browse/RHCLOUD-27973
Can you please merge when possible? Thank you @Hyperkid123 @ryelo @karelhala :)

/ok-t-test

/ok-to-test


button shadow

Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like.
The buttons required shadows so I provided them to make them look more immersive.
Application Version
v1.2.2
Screenshots

Additional information
No response

#147


Empty Postman json file

Hello.
The output for this api.php file is empty:
<?php

use Illuminate\Support\Facades\Route;
use App\Http\Controllers\AuthController;
use App\Http\Controllers\TeamController;
use App\Http\Controllers\ThemeController;
use App\Http\Controllers\PluginController;
use App\Http\Controllers\CompanyController;
use App\Http\Controllers\ProjectController;
use App\Models\ProjectCollaborationRequestTeam;
use App\Models\ProjectCollaborationRequestUser;
use App\Http\Controllers\ProjectBillingController;
use App\Http\Controllers\UserController;
use App\Http\Controllers\FeedbackController;
use App\Http\Controllers\AdminLoginController;
use App\Models\ProjectCollaborationRequestCompany;

/*
|--------------------------------------------------------------------------
| API Routes
|--------------------------------------------------------------------------
|
| Here is where you can register API routes for your applica    tion. These
| routes are loaded by the RouteServiceProvider within a group which
| is assigned the "api" middleware group. Enjoy building your API!
|
*/

Route::middleware('guest:api')->group(function() {
    Route::post('/login', [AuthController::class, 'login']);
    Route::get('/login', [AuthController::class, 'login']);
    Route::post('/register', [AuthController::class, 'register']);
    Route::post('/authOtp', [AuthController::class, 'authOtp']);
    Route::post('/checkuser', [AuthController::class, 'checkUser']);
    Route::post('updatePassword', [AuthController::class, 'updatePassword']); // login user session details
    Route::post('deleteUser', [AuthController::class, 'deleteUser']); // delete user

    //admin login
    Route::post('/admin/login', [AdminLoginController::class, 'login']);

});

Route::middleware([
    'auth:api',
    'bindings',
])->group(function() {
    // all routes will be POST, PUT, PATCH, DELETE
    //for get auth user details
    Route::get('/getUserDetails', function () {
        return auth()->user();
    });
    Route::post('/updateUserDetails',[AuthController::class, 'updateUserDetails']);
    Route::post('/addConnecterJson', [ProjectController::class, 'addConnecterJson']);
    Route::patch('updatePackageList/{plugin?}/{version?}', [PluginController::class, 'updatePackageList']);
    Route::delete('deletePackageList/{plugin}',[PluginController::class,'deletePackageList']);

    // company routes
    Route::put('/company', [CompanyController::class, 'put']); // add
    Route::patch('/company/{company}', [CompanyController::class, 'patch']); // update
    Route::delete('/company/{company}', [CompanyController::class, 'delete']); // delete

    // company user routes
    Route::put('/company/{company}/user/{user}', [CompanyController::class, 'putUser']); // add company user
    Route::patch('/company/{company}/user/{user}', [CompanyController::class, 'patchUser']); // update company user (for permissions)
    Route::delete('/company/{company}/user/{user}', [CompanyController::class, 'deleteUser']); // delete company user

    // team routes
    Route::post('/company/{company}/teams', [TeamController::class, 'index']); // show all company teams
    Route::post('/teams', [TeamController::class, 'index']); // show all teams (of the user)

    Route::put('/company/{company}/team', [TeamController::class, 'put']); // add team
    Route::patch('/team/{team}', [TeamController::class, 'patch']); // update team
    Route::delete('/team/{team}', [TeamController::class, 'delete']); // delete team

    // team user routes
    Route::put('/team/{team}/user/{user}', [TeamController::class, 'putUser']); // add team user
    Route::patch('/team/{team}/user/{user}', [TeamController::class, 'patchUser']); // update team user (for permissions)
    Route::delete('/team/{team}/user/{user}', [TeamController::class, 'deleteUser']); // delete team user

    // project routes
    Route::post('/project/{project}', [ProjectController::class, 'index']); // show project
    Route::post('/projects', [ProjectController::class, 'indexAll']); // show all projects (of the user)

    Route::put('/team/{team}/project', [ProjectController::class, 'put']); // add project
    Route::patch('/project/{project}', [ProjectController::class, 'patch']); // update project
    Route::delete('/project/{project}', [ProjectController::class, 'delete']); // delete project

    Route::put('/project/{project}/user/{user}', [ProjectCollaborationRequestUser::class, 'put']); // send collaboration request to user
    Route::patch('/project/{project}/user/{user}', [ProjectCollaborationRequestUser::class, 'patch']); // modify the collaboration request sent to the user

    Route::put('/project/{project}/team/{team}', [ProjectCollaborationRequestTeam::class, 'put']); // send collaboration request to team
    Route::patch('/project/{project}/team/{team}', [ProjectCollaborationRequestTeam::class, 'patch']); // modify the collaboration request sent to the team

    Route::put('/project/{project}/company/{company}', [ProjectCollaborationRequestCompany::class, 'put']); // send collaboration request to company
    Route::patch('/project/{project}/company/{company}',  [ProjectCollaborationRequestCompany::class, 'patch']); // modify the collaboration request sent to the company

    // project plugin routes
    Route::patch('/project/{project}/plugins', [ProjectController::class, 'syncPlugins']); // sync project plugins with this list
    Route::post('projects/user', [ProjectController::class, 'syncUserplugins']); // sync project user with this list
    Route::post('projects/environment', [ProjectController::class, 'updateComposerJson']); // add and update the composer json in the database.

    Route::post('composer/addqueue', [PluginController::class, 'addQueue']); // add composer queue in the project

    Route::post('plugins/user', [PluginController::class, 'getUserPlugins']); // this plugin list for the list users
    Route::post('plugins/addremove', [PluginController::class, 'addRemoveUserPlugins']); // add remove plugin list for the list users
    Route::post('plugins/session', [PluginController::class, 'userSession']); // login user session details
    Route::post('plugins/sessionStore', [PluginController::class, 'userSessionStore']); // login user session details

        Route::patch('/project/{project}/plugin/{plugin}')->scopeBindings(); // update project plugin

    //project billing routes
    Route::post('/project/{project}/billing', [ProjectBillingController::class, 'index']);

    // user routes
    Route::post('/user/{user}/projects', [UserController::class, 'projects']); // show all the projects this user has access to
    Route::post('/user/{user}',[UserController::class,'index']);

    Route::post('/projectPlugins', [PluginController::class, 'projectPlugins']);

    Route::post('/feebackform', [FeedbackController::class, 'feebackform']);

    //get Plugin data by type
    Route::post('/getPluginData', [PluginController::class, 'getPluginData']);

    Route::post('/getEnvByProject', [ProjectController::class, 'getEnvByProject']);

    // get package List
    Route::post('/packageList', [PluginController::class, 'packageList']);

});

Route::post('/plugins', [PluginController::class, 'index']);
Route::post('/allplugins', [PluginController::class, 'allPlugins']);
Route::post('/allVersion', [PluginController::class, 'allVersions']);

Route::post('/themes', [ThemeController::class, 'index']);

@valentinceaprazaru please reformat your post to make it easier to read and give more details than just "it's empty".

I fixed the formatting for you, but we could do with some more information. Does it generate the file with nothing at all? Is there something in the file like the collection information but no requests?

Hello,
Thank you for being proactive. Here is the output of a file that i get after running the command of export.
{
    "variable": [
        {
            "key": "base_url",
            "value": "https:\/\/api.fusepress.co.test"
        }
    ],
    "info": {
        "name": "2023_09_01_093111_fuse_press_collection.json",
        "schema": "https:\/\/schema.getpostman.com\/json\/collection\/v2.1.0\/collection.json"
    },
    "item": [],
    "event": []
}

Would a composer.json file help you with the debug?
`
{
"name": "laravel/laravel",
"type": "project",
"description": "The Laravel Framework.",
"keywords": [
"framework",
"laravel"
],
"license": "MIT",
"require": {
"php": "^7.4|^8.0",
"ext-json": "*",
"filament/filament": "^2.0",
"fruitcake/laravel-cors": "^2.0",
"guzzlehttp/guzzle": "^7.0.1",
"laravel/framework": "^8.54",
"laravel/passport": "^10.1",
"laravel/tinker": "^2.5",
"laravel/ui": "^3.3",
"spatie/laravel-permission": "^5.1"
},
"require-dev": {
"andreaselia/laravel-api-to-postman": "^1.15",
"doctrine/dbal": "^3.6",
"facade/ignition": "^2.5",
"fakerphp/faker": "^1.9.1",
"laravel/sail": "^1.0.1",
"mockery/mockery": "^1.4.4",
"nunomaduro/collision": "^5.10",
"phpunit/phpunit": "^9.5.8"
},
"autoload": {
"psr-4": {
"App\": "app/",
"Database\Factories\": "database/factories/",
"Database\Seeders\": "database/seeders/"
}
},
"autoload-dev": {
"psr-4": {
"Tests\": "tests/"
}
},
"scripts": {
"post-autoload-dump": [
"Illuminate\Foundation\ComposerScripts::postAutoloadDump",
"@php artisan package:discover --ansi"
],
"post-update-cmd": [
"@php artisan vendor:publish --tag=laravel-assets --ansi",
"@php artisan filament:upgrade"
],
"post-root-package-install": [
"@php -r "file_exists('.env') || copy('.env.example', '.env');""
],
"post-create-project-cmd": [
"@php artisan key:generate --ansi"
],
"clear-all": [
"composer dumpautoload -o",
"@php artisan clear-compiled",
"@php artisan cache:clear",
"@php artisan route:clear",
"@php artisan view:clear",
"@php artisan config:clear"
],
"cache-all": [
"@php artisan config:cache",
"@php artisan route:cache"
]
},
"extra": {
"laravel": {
"dont-discover": []
}
},
"config": {
"optimize-autoloader": true,
"preferred-install": "dist",
"sort-packages": true
},
"minimum-stability": "dev",
"prefer-stable": true
}
`

@valentinceaprazaru I think this might be down to your routes not having a name attached to them.
Example:
Route::get('/getUserDetails', function () {
    return auth()->user();
})->name('getUserDetails');

Route::post('/updateUserDetails',[AuthController::class, 'updateUserDetails'])->name('updateUserDetails');

I have added only the routes you posted as the example.
Then i have cached the new api.php routes but the resulting json file was still empty.

I have moved the routes from api.php to web.php file.
Then i have cached the new routes and tried to export to the Postman json. The output was still empty.
What else should i try?

Could you create a minimum reproducible api.php file please? Remove all but 1 route and see if that exports, making sure it has a name.
Did you change the api-postman.php config file at all?


Feature/simplify

Description
Adds simplify method that simplifies the condition with already existing context.
Tasks

[x] add more tests
[x] add docs
[x] add examples
[x] update readme

Test Coverage

[x] unit

Looking good, nice clean up!
For the documentation, we can drop the @return statements, and the types e.g.: {Context} ... these were for JSDoc, but this repo uses now the TSDoc
  /**
   * Evaluate in the given context.
   * @param {Context} ctx
   * @return {Result}
   *

  /**
   * Evaluate in the given context.
   * @param ctx
   *

or, where there is no additional intel for a param >>

/**

Evaluate in the given context.

This PR is getting bigger and bigger =(

Looks good to me.  This PR introduces a public interface method simplify, which seems reasonable.
David, good to merge and deploy?

Looks good not,but let's not forgot about the "changelog.md" and packages version bump:
https://docs.google.com/document/d/19LtdshUTZPLfuYkDv-qYnlObs5J2FaRGEYbLZTGt7UU

Sure, I was going to ask you about this now. The process is that I update everything (changelog and version) in this branch and then merge and deploy from master?

Looks good not,but let's not forgot about the "changelog.md" and packages version bump:
https://docs.google.com/document/d/19LtdshUTZPLfuYkDv-qYnlObs5J2FaRGEYbLZTGt7UU

Sure, I was going to ask you about this now. The process is that I update everything (changelog and version) in this branch and then merge and deploy from master?

Yeah, as this really represents a feature which is immediately released, it make sense to bump the package here, and update the changelog accordingly.

Looks good not,but let's not forgot about the "changelog.md" and packages version bump:
https://docs.google.com/document/d/19LtdshUTZPLfuYkDv-qYnlObs5J2FaRGEYbLZTGt7UU

Sure, I was going to ask you about this now. The process is that I update everything (changelog and version) in this branch and then merge and deploy from master?

Yeah, as this really represents a feature which is immediately released, it make sense to bump the package here, and update the changelog accordingly.

new version: 1.3.0
It this a minor version bump for you too?

Looks good not,but let's not forgot about the "changelog.md" and packages version bump:
https://docs.google.com/document/d/19LtdshUTZPLfuYkDv-qYnlObs5J2FaRGEYbLZTGt7UU

Sure, I was going to ask you about this now. The process is that I update everything (changelog and version) in this branch and then merge and deploy from master?

Yeah, as this really represents a feature which is immediately released, it make sense to bump the package here, and update the changelog accordingly.

new version: 1.3.0
It this a minor version bump for you too?

1.3.0 sounds appropriate, as this is really a new "bigger" feature.