[turborepo] ETXTBSY with Docker on node 20.3.0

What version of Turborepo are you using?
1.10.3
What package manager are you using / does the bug impact?
Yarn v2/v3 (node_modules linker only)
What operating system are you using?
Mac
Describe the Bug
Going to leave this here for others in case they run into it. It appears our docker builds started failing recently.
It could be an upstream issue with Node.
Rolling back to node 20.2.0 works.
Aka, instead of FROM node:alpine AS builder using FROM node:20.2.0-alpine AS builder works.
#13 [builder 5/7] RUN yarn global add turbo
#13 sha256:3bc7ac6f39a70e2fe26f94cc70e4b64dec5eb57f4d4bc7c2077b3700807945f1
#13 0.367 yarn global v1.22.19
#13 0.409 [1/4] Resolving packages...
#13 0.698 [2/4] Fetching packages...
#13 2.550 [3/4] Linking dependencies...
#13 2.601 [4/4] Building fresh packages...
#13 2.668 error /usr/local/share/.config/yarn/global/node_modules/turbo: Command failed.
#13 2.668 Exit code: 1
#13 2.668 Command: node install.js
#13 2.668 Arguments:
#13 2.668 Directory: /usr/local/share/.config/yarn/global/node_modules/turbo
#13 2.668 Output:
#13 2.668 node:internal/errors:496
#13 2.668     ErrorCaptureStackTrace(err);
#13 2.668     ^
#13 2.668
#13 2.668 <ref *1> Error: spawnSync node ETXTBSY
#13 2.668     at Object.spawnSync (node:internal/child_process:1117:20)
#13 2.668     at spawnSync (node:child_process:871:24)
#13 2.668     at Object.execFileSync (node:child_process:914:15)
#13 2.668     at validateBinaryVersion (/usr/local/share/.config/yarn/global/node_modules/turbo/install.js:28:6)
#13 2.668     at /usr/local/share/.config/yarn/global/node_modules/turbo/install.js:314:7 {
#13 2.668   errno: -26,
#13 2.668   code: 'ETXTBSY',
#13 2.668   syscall: 'spawnSync node',
#13 2.668   path: 'node',
#13 2.668   spawnargs: [
#13 2.668     '/usr/local/share/.config/yarn/global/node_modules/turbo/bin/turbo',
#13 2.668     '--version',
#13 2.668     '--skip-infer'
#13 2.668   ],
#13 2.668   error: [Circular *1],
#13 2.668   status: null,
#13 2.668   signal: null,
#13 2.668   output: null,
#13 2.668   pid: 0,
#13 2.668   stdout: null,
#13 2.668   stderr: null
#13 2.668 }
#13 2.668
#13 2.668 Node.js v20.3.0
#13 2.668 info Visit https://yarnpkg.com/en/docs/cli/global for documentation about this command.
#13 ERROR: executor failed running [/bin/sh -c yarn global add turbo]: exit code: 1

Expected Behavior
No error.
To Reproduce
Dockerfile with:
FROM node:20.3.0-alpine AS builder
RUN apk add --no-cache libc6-compat
RUN apk update
# Set working directory
WORKDIR /app
RUN yarn global add turbo

Reproduction Repo
No response

Upstream bug: https://github.com/nodejs/node/issues/48444

Thanks for the report. Am I correct in saying this is a wider nodejs issue rather than a turbo-specific problem?

Indeed it's a nodejs issue, so you can close it (either now or when it's fixed upstream) - I opened it here because Turbo specifically documents Docker usage, and I ran into this issue just here for now. I thought others would appreciate quickly finding a workaround.
I don't think it's actionable from Turbo's side.

The report is useful for others and for documentations sake so thanks for taking the time. I will close this now.

I got the same problem on my ci/cd pipeline - but it wasn't relevant to docker.
I leave it here because Google directed me to this thread.
I had the following error:
Turborepo did not find the correct binary for your platform.

We will attempt to install it now.

Installation has succeeded.

/mnt/data/jenkins/workspace/***/node_modules/turbo/bin/turbo:273

  throw e;

  ^

<ref *1> Error: spawnSync /mnt/data/jenkins/workspace/***/node_modules/turbo/node_modules/turbo-linux-64/bin/turbo ETXTBSY

My problem, I had two parallel tasks that run turbo run lint and turbo run test,
They basically raced on installing the correct binary, and locking the file.. the other tried to override the file,
The way that I solved it, was to run the following command before I ran in parallel the rest of the turbo commands
    sh """
    npx turbo --help
    """


fork object properties

In immu immutable arrays can be forked using methods like push, which is handy. For objects there are no such methods. Has it ever been considered to introduce methods to support operations like the following? Or would this increase the size of the library to such a degree that it is no longer tiny?
var oldImmu = immu({ foo: 'bar' });
var newImmu = oldImmu.set('foo', 42);
newImmu = oldImmu.rm('foo');
newImmu = oldImmu.set('hello', 'world');
newImmu = oldImmu.set('hello', [1, 2, 3]); // the array will be made immutable
newImmu = newImmu.set('hello', newImmu.hello.push(4)); // newImmu.hello.length == 4

That's an interesting concept. I was trying to avoid replicating the Map/Set interface. But this would help with memory footprint.
I wonder if immu could be extensible and we could make a wrapper over immu with this interface. Thoughts?

That could be done, of course, using the ToJS function, but integration would mean that it can share more code with the logic that is already in immu.

I'm still not sold on adding more functionality to this package. I'd still LOVE to see a package that wraps immu with the set/get/rm methods you recommended.
I'm going to close for now and we can reopen if this becomes a bigger problem in the future.

+1 for the ability to fork objects. Right now I do
let tmp = old.toJS() tmp.a.b.c = d let new = immu(tmp)
which kind of defeats the purpose in my use case. For now I will go with seamless-immutable but would prefer using immu (performance is outstanding).

@alexanderharm The idea with the immu is not to replace something like immutable or mori or freezer. It's mainly a way to ensure you don't mutate objects without having to wrap them in an immutable data structure (like Immutable's Map or List).
I am VERY open to write help methods to compose with immu like immu-set, immu-remove. BUT, the basic idea is that you would treat an immu object like a raw object, keeping it purely JS.
Does that help clarify it?


Show more friendly info to users

Plugin name and version:  azure-maven-archetypes: 1.15
Info should match expression '[A-Za-z0-9_-.]+'  that are very unfriendly to users

We could just set the regex pattern in archetype-metadata and the message was shown by maven archetype, it's difficult for us to change the infos.

Put into bakclog


Raise hand (un)equipped events on container insert/remove

About the PR

Applying an ElectroJr/Sr design suggestion : drop/unequip handshould work more like inventory does, where it just raises unequip events automatically whenever anything is removed from the container so actions list prediction on client can be accurate.
That fixes sidebar icons duplication, notably for magboots (fixes # 13408).
There's still multiple client reconciliation on a single pickup/drop, but it's now working as intended (as far as i can tell from my local testing).
Alongside the usual maintainers, requesting @ElectroJr review if/when they have some spare time to make sure it was what they had in mind.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

I've been wondering the same for these broadcast, waited for your approval.
Requested changes done.

Doesn't seem to fully fix the magboot issue, so I removed the CL

It didn't appeared in local testing, but i guess the misprediction is worse on a live server.
Thanks for removing the CL.


Add AWS Route 53 DNS plugin

New DNS validation plugin for AWS Route 53.

Nice work!
The CI build is erroring out on the following message though:
Metadata file '..\packages\AWSSDK.Route<IP_ADDRESS>.4\analyzers\dotnet\cs\AWSSDK.Route53.CodeAnalysis.dll' could not be found
Can you look into that?

Removed AWS code analyzer. Now CI build fails with another issue.

Yes but I think those are unrelated to your changes. I will do a proper code review later and hope to integrate the PR sometime next week.

Everything in the code looked fine to me, so I merged it in and updated the build script to create the .zip package for distribution. I would appreciate if you could pull the build from AppVeyor and test if the right assemblies are included and it's all working: https://ci.appveyor.com/project/WouterTinus/win-acme-s8t9q/builds/23643902/artifacts
It's great to see AWS support by the way, thanks for taking the time to make and share this code with the rest of us!

Just checked with AppVeyor build. It works!

Hi, my apologies if this isn't the correct place to post this!
@ivanstus Thank you for creating this validation plugin! I've been doing this with batch files and AWS CLI for some time! I do have a couple of questions however.
Firstly, I've managed to get it installed, however there was no documentation. Could some documentation be made on how to install these validation plugins?
Second, I'm wondering how renewal works? Has the application cached my AWS credentials for renewal? Has it saved them to a file somewhere? Will I need to provide them again at renewal?
Thanks again :)

There is a little bit of documentation here for future reference:
https://github.com/PKISharp/win-acme/wiki/DNS-validation-plugins#route53
As you suspected, the credentials are stored in a file and will be reused for future renewals.

No credentials stored when using IAM role.


Update main.tf

What does this PR do?
🛑 Please open an issue first to discuss any significant work and flesh out details/direction - we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

Motivation

Resolves #

More

[ ] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
[ ] Yes, I have added a new example under examples to support my PR
[ ] Yes, I have created another PR for add-ons under add-ons repo (if applicable)
[ ] Yes, I have updated the docs for this feature
[ ] Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs require a new example and/or doc page. In general:

Use an existing example when possible to demonstrate a new addons usage
A new docs page under docs/add-ons/* is required for new a new addon

For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

thank you but we won't be making this change at this time. Next time, please start with an issue and we can discuss the problem we are trying to solve for and potential solutions before a PR


Support for geodesic lines

Hello, as a new feature it would be great if the library would support drawing geodesic lines that follow the curvature of the Earth. Especially useful when connecting two very distant places. In this case, a straight line does not look good. Would be great to have a flag so we can choose between these two line styles. Thanks!

I implemented it via turf-arc. But there are some bugs when crossing the dateline.

Wow, thanks Stephan! It's sad they have bugs, maybe there is some other lib
which does it properly.
Anyway, no rush, for now I can easily live with straight lines :)
On Tue, 4 Sep 2018 at 16:52, Stephan Georg<EMAIL_ADDRESS>wrote:

I implemented it via turf-arc
https://github.com/stepankuzmin/turf-arc#readme. But there are some
bugs when crossing the dateline.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/StephanGeorg/staticmaps/issues/15#issuecomment-418260055,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AgkFW1dfkSO1puWHZ-DXxnoQ37sM6q5Iks5uXiMZgaJpZM4WW6Kc
.

--
Regards/Pozdrawiam,
Łukasz Szkup

No, it's more a mathematical thing than a software bug. In the meantime you can calculate the geodesic path and add the coordinates as a polyline.


Update tapir with libraries that cause dependency conflicts

Hello,
I stumbled upon this template after reading the job posting and the coding challenge for backend engineers. I submitted my application and I wanted to go ahead and try the challenge by using this template, which I liked, just for fun :). My first step was to update the dependencies to the latest stable release, but some of them weren't as simple as just bumping the version number like tapir. After I managed to make it compile and pass the tests I thought that it might be useful. So here is the PR.
Happy to amend things if something is not according to standards or guidelines.
Cheers!

Thank you for all these updates @rolang 🙏


Add install directive for dbc file

Resolves issue #17 by adding an install directive for the dbc file.

Looks like there is an issue in the CircleCI configuration
The following packages have unmet dependencies:
 ros-kinetic-kvaser-interface : Depends: kvaser-canlib-dev but it is not installable
E: Unable to correct problems, you have held broken packages.
ERROR: the following rosdeps failed to install
  apt: command [apt-get install -y ros-kinetic-kvaser-interface] failed
Exited with code 1

@msmcconnell - Yeah, that was a change that was made to kvaser_interface. Sorry about that. I'll put in an MR to fix it. I'm trying to bug NewEagle to give this repo some love.

Closed in favor of #41


Fix breaking import issue #2880

Description
Please include a brief summary of the change.
Type of change

[ ] Chore (non-breaking change that addresses non-functional tasks, maintenance, or code quality improvements)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Associated Issues
For Linear issues: Closes APKT-xxx
For GH issues: closes #2880
Showcase (Optional)
If there is a UI change include the screenshots with before and after state.
If new feature is being introduced, include the link to demo recording.
Checklist

[X] Code in this PR is covered by automated tests (Unit tests, E2E tests)
[X] My changes generate no new warnings
[X] I have reviewed my own code
[X] I have filled out all required sections
[x] I have tested my changes on the preview link
[ ] Approver of this PR confirms that the changes are tested on the preview link

Hey @pelle Thank you for coming up with a solution to this! We also recently realized this issue and already merged our improvements for it #3036.
While the with will work for the newest Node.JS versions, it'll be still broken for old Node.js users. assert is replaced with with on the new versions. So it's still problematic to use. You can find more info on our PR.
Best


Payload too large

Sending large follow lists seems to break the relay

Related issue: https://github.com/CodyTseng/nostr-relay-tray/issues/8
Yeah, it currently does not accept events larger than 128k. This issue will be resolved soon.


Fix PyTorch Optuna test

Will close #1250 and close #1248

Tests pass, failures in building static dashboards and Tests/ Combine failed due to github outages.


Category Action Plugins

Proposal: Category Action Plugins
Author: Matt Martz <@sivel>
Date: 2017/02/28

Status: New
Proposal type: core design
Targeted Release: 2.4
Associated PR: N/A
Estimated time to implement: days to weeks

Motivation
We often have a need to apply very similar action plugins to a category or "class" of modules, most specifically, network modules.
If we had a mechanism to load an action plugin for a category of modules, we could reduce code, and make it easier to impact a whole category of modules.
Problems
What problems exist that this proposal will solve?

Reduce duplicated code in action plugins
Make it easier for a group of modules to share action plugin code, for pulling in runtime info and injecting it into the category of modules

Solution proposal
This is a still a little fuzzy.  My immediate idea involves a somewhat fundamental change in the way that the plugin loaders work.  I'd really love to start passing around objects, that contain much more data.
But in the end, we would need to have a way, to map a module, to a category, either by utilizing the path based categories we have now, or by embedding categories into the modules. The plugin loaders, potentially those for modules/action plugins, could be merged, with methods or properties describing module location and action plugin location if such a thing exists.
In any case, to simplify that, if we could just have a way to determine what "category" a module was in, we could search for the associated action plugin for that category.  This would be a fallback likely, preferring an exact match first, eventually falling back to "normal".  1) specific, 2) category, 3) normal
Dependencies (optional)
N/A
Testing (optional)
Tests would be good
Documentation (optional)
Documentation would be good
Anything else?
A real implementation? I'm 100% sure I am not thinking of something.

So I was toying with a possible implementation, based on the current 'name matching' with fallbacks, so each action plugin could declare a list of 'criteria' to be run against the modules:
self.criteria = ( "name.matches('eol_.*) or path.endswith('cloud/eol')", "other stuff: )
then in executor we can 👍
 if module.name in action_plugins:
    # use action plugin of same name
else:
     for action in action_plugins:
         if action.criteria(module):
               #use matched action plugin
               break
      else:
            # use normal handler

I think that is roughly equivalent to my idea.  Effectively I was thinking of using the module hierarchy to provide action plugins.
Something like network/ios/ios_command.py would look for an ios_command action plugin, then ios and then network and then all the way back to normal.

I like the fallback mechanism, how does it sound to also consume criteria from module metadata ?
i.e. not just hardcoding the path of category selection, but to also allow a module developer to inject its own behaviour.

My biggest concern with metadata, is I'm not a huge fan of what I will refer to as introspection, we are having to inspect code to see how to run that code.  It's not exactly efficient, and I know we do things like this already, I just wish we didn't.

I'm in favor of sub packages for plugins that have deps that don't fall into the same set of deps as 'ansible'.
ie, ansible-plugins-filters-jmespath as subpackage, with a dep on python-jmespath.
I would make that subpackage include the plugin code, as opposed to just being a deps-only package.
Plugin loader exists so that can be possible, so might as well use it. That also opens the door for letting distros choose to not include/build some subpackage if they can't provide the deps. I am thinking primarily about 'pycrypto' vs 'cryptography' as the example here, though that is currently not isolated to plugins, but
it could be. (See https://github.com/ansible/ansible/pull/25084 for reference)
The main 'ansible' package could 'suggest' ansible-plugins-filters-jmespath, but shouldn't require it. At least if the intention is to provide a path for user to not require 'python-jmespath' for 'ansible' install.

@rcarrillocruz also with module metadata you are inverting the normal execution handling (executor > action > module) to (executor > module > action > module?) ... I really don't think this is something we should allow.

Agreed, probably default to current action plugin resolving behaviour, and have a toggle in config that allows module-side setting ?

I don't think that having a toggle is wise.  then you split the platform.  Here's modules that work with Ansible-toggle-set-to-true  and here's modules that work with Ansible-toggle-set-to-false.  But they don't mix.
I think inverting the handling is the inevitable consequence of wanting this feature.  So if we decide we don't want the feature, we should discard it.  If we do want it, then we have to acknowledge that it is the module calling the shots here, not the action plugin.
Out present hardcoded thing already inverts the relationship -- the module name is a form of metadata that the module is control of, not the action plugin.  This goes slightly further, though -- right now the controller side has a hardcoded mapping of metadata=network:  network_action_plugin.  This proposal would allow that mapping to be drawn by the modules as well as simply the categorization.
We could make something in between, mapping is created and expanded upon controller side by the action plugins.  Then the modules say they need a certain action_feature in order to run.
Example Setup
normal action plugin has a field that says:
action_handler: "*"

bigip action plugin has a field that says:
action_handler: "bigip"

bigip_template module has in its metadata:
{ "metadata_version":  "1.2",
  "action_handler": "bigip"
}

poorly_written plugin has in its metadata:

{ "metadata_version": "1.2",
"action_handler": "nope_does_not_exist"
}
Running module with action_handler: handled on the controller side

Running ansible -m bigip_template will lookup the metadata for the bigip_template module.
Ansible will see the action_handler of bigip
Ansible will read the metadata for the action plugins
Ansible will use the metadata to construct a map of action_handler fields to action handlers
Ansible will load the bigip action plugin because it registered itself as the bigip action_handler.
Ansible will run the bigip_template module via the bigip action plugin

Running module with action_handler: not handled on the controller side

Running  ansible -m poorly_written will lookup the metadata for the poorly_written module.
Ansible will see the action_handler of bigip
Ansible will not find an action_handler for nope_does_not_exist
Ansible will error, unable to run the module

Running module with no specified action_handler

Running ansible -m ping will lookup the metadata for the ping module
Ansible will see no action_handler
Ansible will find the action_handler for "*" is normal
Ansible will run the ping plugin via the normal action handler.

I think I said this in the meeting but recording it here too. I'm against the criteria idea.  It introduces complexity where it isn't needed.


Docker Volume Size

This is a question: AFAIK currently 'docker volume' does not support  volume size option. Are there any plans to (or is it already ongoing) to incorporate it into a next release.
Thanks,
Alex

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see CONTRIBUTING.md.
You don't have to include this information if this is a feature request
(This is an automated, informational response)

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

There are no plans to add quota support to the default ("local") volume driver. I don't think we want to add to many options to the default driver, but this should be achievable with a volume-driver plugin.

Thanks for the prompt reply. I understand that it should be achievable with a volume-driver. I am using REX-Ray, and using REX-Rey in conjunction with ScaleIO + Apache Mesos + Mesos containerizer, I can supply volume size + IOPS + thin or thick (all via Mesos DVDI). However, I cannot supply the same parameters if I use docker containerizer. This is a major pain, because we plan to deploy Postgres + Mongo on Docker containers, and I cannot provide desired volume size.

But if the default driver had a size option, it would still need to be passed on by Docker containerizer ?

@akamalov AFAIK, docker volume create  provide interface to pass driver specific options. I think if your volume-driver plugin has quota support , you can provide desired volume size with --opt=map[] option in your docker volume create cli, something like docker volume create -d YOUR_DRIVER -o volume.size=10G, it's depend on your volume-driver implementation

as @coolljt0725 said you can pass "--opt size 10" to docker volume according to http://rexray.readthedocs.org/en/stable/#rex-ray-with-docker

Sorry, I have to reformulate my question: Will it be possible to have docker run command and provide docker volume options ? As per previous replies (thanks so much), I can get  away with docker volume create and pass the options to ScaleIO. However, when I am submitting a container to be spawn up from Marathon, I have to provide options that will work with docker run command. Here is my conversation with REX-Ray engineer:
https://github.com/emccode/rexray/issues/283
Thanks!!!
Alex

No, we most likely won't be adding that as an option; these options can vary between volumes, and having even more options in the -v flag will make up for a really bad/complicated UX.
When running from the command-line, using a sub-shell should do the trick, but I don't know how that translates to containerizer;
docker run \
  -v $(docker volume create --name=myvolume --driver=foo --opt bar=baz):/foo \
  -v $(docker volume create --name=other --driver=other --opt baz=foo):/bar

Hmmm...the environment is ran from Marathon. Here is a sample JSON file that is used to spawn up a container in conjunction with REX-Ray:
{
        "id": "mongodb5",
        "container": {
                "docker": {
                        "image": "tutum/mongodb:3.2",
                        "network": "BRIDGE",
                        "portMappings": [{
                                        "containerPort": 27017,
                                        "hostPort": 37017,
                                        "protocol": "tcp"
                                }, {
                                        "containerPort": 28017,
                                        "hostPort": 38017,
                                        "protocol": "tcp"
                                }

                        ],
                        "parameters": [{
                                "key": "volume-driver",
                                "value": "rexray"
                        }, {
                                "key": "volume",
                                "value": "mongo005:/data/db"
                        }, {
                                "key": "env","value": "MONGODB_PASS=XXXXXXX"
                       }]
                }
        },
        "cpus": 0.2,
        "mem": 128.0,
        "instances": 1,
        "constraints": [
                ["hostname", "UNIQUE"]
        ]
}

Tried to nest the command, such as:
"value": "$(docker volume create --name=mongotest --opt size 10):/data/db"
However, REX-Ray already does do "volume create" directive based on values in "parameters" section. So, it didn't work...
With Mesos DVDI, I can  specify the following settings:
"env": {
  "DVDI_VOLUME_NAME": "testing",
  "DVDI_VOLUME_DRIVER": "platform1",
  "DVDI_VOLUME_OPTS": "size=5,iops=150,volumetype=io1,newfstype=ext4,overwritefs=false",
  "DVDI_VOLUME_NAME1": "testing2",
  "DVDI_VOLUME_DRIVER1": "platform2",
  "DVDI_VOLUME_OPTS1": "size=6,volumetype=gp2,newfstype=xfs,overwritefs=true"
}

...all within the same JSON file and volume automatically created of assigned size and mounted
:(
Alex

@akamalov We won't support volume opts on docker run or docker create


Logic App Workflow and Integration Account Snippet

Snippet for Logic App workflow was creating Integration Account, and there was no snippet for Integration Account.

[x] I have a snippet that is either a single, generic resource or multi resource that uses parent-child syntax
[x] I have checked that there is not an equivalent snippet already submitted
[x] I have used camelCasing unless I have a justification to use another casing style
[x] I have placeholders values that correspond to their property names (e.g. dnsPrefix: 'dnsPrefix'), unless it's a property that MUST be changed or parameterized in order to deploy. In that case, I use 'REQUIRED' e.g. keyData
[x] I have my symbolic name as the first tab stop ($1) in the snippet. e.g. res-aks-cluster.bicep
[x] I have a resource name property equal to "name"

A suggestion - perhaps we could incliude in snippet json(loadTextContent('{placeholder}')) for loading LogicApp definition from file?

@miqm - I thought this is a simple fix, but I cannot get the tests working.

Complains about missing file
main.combined.bicep is always generated incorrectly

I am not sure what I am doing wrong.

@rajyraman It's not you, seems like for snippet tests runner is trying to load the file and not ignore it. It needs to be changes/fixed, I'll create issue for it and see what can be done.

@miqm -  I can't believe that I could not see the missing '} 🤦. I am now getting this error.

Thank you fixing the underlying issue. I will test it with your PR.

Hey @rajyraman, both issues you've been experiencing are fixed, please rebase and try now.

@rajyraman - would you mind enabling "Allow edits from maintainers" for this PR, and I'll push the fixes for your tests.

@anthony-c-martin - It seems to be already enabled.


Ignore 2 tfsec warnings

what

Ignore 2 tfsec warnings

why

We are okay with the CIDR block on the NAT instance's egress being <IP_ADDRESS>/0
We are okay with the the NAT instance having a public IP address (?)

references

/test all

Going to go ahead and merge this and cut a new release. There was some discussion in Slack about whether it is the right choice to do this for an individual tool like tfsec. We can back it out if it becomes necessary.


Update Roll to Foundry VTT V9.233

documentation for _classifyStringTerm changed
new getter isDeterministic
default for async in the options for evaluate changed to true
simulate is now async
small changes to render (docs of return value)
deprecated _rolled and MATH_PROXY removed

I'm not seeing any doc changes, for _classifyStringTerm


Docs: Check --read-data-subset explenation confusing.

In the check docs, the explenation for --read-data-subset was indefinitely confusing for me. I wouldn't of understood it without examining the examples.
I don't have any better wording for it, but I think there should be.

Closing this as it will be fixed in #2476 soon.


Optimize preparing TypedArray data for creating constant operand

This PR is to address the improvement performance of Building Graph when executing model tests on https://github.com/webmachinelearning/webnn/issues/402.
@Honry @huningxin PTAL, thanks.

Thanks for reviewing. Let's merge it.


Slack invite

Hey Ben! I want to add you to F7 developers and contributors Slack channel! Could you email me at<EMAIL_ADDRESS>and I will send you invite
P.S. sorry for the issue, don't know how to contact you directly 😊

@nolimits4web - I'd love to join! I just sent you an e-mail.


git-lfs version fails if called in the root directory

git-lfs version fails on Windows (using git-bash) and OS X if called in the root directory.
Versions tested:
1.4.1

Steps to reproduce:
cd / && git-lfs version

Output:
panic: Error trying to init LocalStorage: mkdir lfs: permission denied

goroutine 1 [running]:
panic(0x377740, 0xc420102920)
       	/usr/local/Cellar/go/1.7/libexec/src/runtime/panic.go:500 +0x1a1
github.com/github/git-lfs/localstorage.ResolveDirs()
       	/private/tmp/git-lfs-20160826-6787-1o15v20/git-lfs-1.4.1/src/github.com/github/git-lfs/localstorage/currentstore.go:39 +0x4c3
github.com/github/git-lfs/commands.resolveLocalStorage(0xc420123d40, 0x5f2ae0, 0x0, 0x0)
       	/private/tmp/git-lfs-20160826-6787-1o15v20/git-lfs-1.4.1/src/github.com/github/git-lfs/commands/commands.go:342 +0x14
github.com/github/git-lfs/vendor/github.com/spf13/cobra.(*Command).execute(0xc420123d40, 0x5f2ae0, 0x0, 0x0, 0xc420123d40, 0x5f2ae0)
       	/private/tmp/git-lfs-20160826-6787-1o15v20/git-lfs-1.4.1/src/github.com/github/git-lfs/vendor/github.com/spf13/cobra/command.go:474 +0x255
github.com/github/git-lfs/vendor/github.com/spf13/cobra.(*Command).Execute(0xc4200f64e0, 0xc42004fed0, 0x1)
       	/private/tmp/git-lfs-20160826-6787-1o15v20/git-lfs-1.4.1/src/github.com/github/git-lfs/vendor/github.com/spf13/cobra/command.go:551 +0x380
github.com/github/git-lfs/commands.Run()
       	/private/tmp/git-lfs-20160826-6787-1o15v20/git-lfs-1.4.1/src/github.com/github/git-lfs/commands/commands.go:70 +0x180
main.main()
       	/private/tmp/git-lfs-20160826-6787-1o15v20/git-lfs-1.4.1/git-lfs.go:33 +0x111

I think the problem was introduce here:
https://github.com/github/git-lfs/pull/1226
/cc @sinbad

I think this is the same core issue as https://github.com/github/git-lfs/issues/1431, in that version does not need to resolve the local storage dirs.
I could fix this right now:
diff --git a/commands/command_version.go b/commands/command_version.go
index d588566..180d313 100644
--- a/commands/command_version.go
+++ b/commands/command_version.go
@@ -20,9 +20,8 @@ func versionCommand(cmd *cobra.Command, args []string) {
 func init() {
        RegisterSubcommand(func() *cobra.Command {
                cmd := &cobra.Command{
-                       Use:    "version",
-                       PreRun: resolveLocalStorage,
-                       Run:    versionCommand,
+                       Use: "version",
+                       Run: versionCommand,
                }

                cmd.Flags().BoolVarP(&lovesComics, "comics", "c", false, "easter egg")

However @technoweenie will already be changing this code as part of #1495 so I'll put a note there instead.

I just observed something in addition:
git lfs version seems to create a lfs directories (containing objects and tmp) in whatever directory you invoke the call.

Yeah, that's the core of it - the fix I've proposed above will resolve that.

That's a good fix (that I'll take care of in #1495), but I wonder if we should worry about the panic from running localstorage.ResolveDirs() on /.

It's deliberate in the code:
	if err != nil {
		panic(fmt.Sprintf("Error trying to init LocalStorage: %s", err))
	}

Do you mean it shouldn't be a panic & just an error message instead?

I think we should still bail out of running LFS if we can't initialize LocalStorage (and we wanted to), but it doesn't need to be a panic 👍

Fixed in #1495:
$ cd /
$ git lfs version
git-lfs/1.4.1 (GitHub; darwin amd64; go 1.7; git a06acca)

Also, tweaking the error message in #1499.


program for binary search tree in cpp

hello @tornado-12  I can  add program to implement binary search tree in cpp for this repository.

Okay @Mayank-100 please add you files in folder c++/ data structures

can i take this issue??

If the issue is still open can I complete it ?

hey, Can i work on this issue ?

@dag2104 you can start working on this issue

I will start working straight away


sensors in NE

Tauana called today, her gateway has is sending spotty data, she will restart next time she visits the farm.

Tauana called today after she had reset the nodes and gateways. The gateway was still not connecting to the tech dashboard, and the last time it sent data is 5/23. There was no timestamp update from when she reset the system.
I ran through the typical diagnostics and everything sounds like it should be in good working order, but nothing shows up. Could it possibly be a cell reception issue? Doesn't the gateway need a certain amount of strength to send data?
I told her that others were having similar issues and that someone (possibly @elhenriq) would follow-up with her in the morning.

Yes, this is definitely because of cell connection issues, don't have a clear path to follow to fix this, the same thing is happening in multiple locations. Need @alondrathompson opinion on this.

@ethansweep This does sound like a cellular reception issue. If you feel comfortable, either you or Esleyther could walk her through using the cellular scouting mode to verify. Otherwise, have her check the SD card to make sure that the gateway is receiving data from the nodes. If not, have her connect to each node and to check the data.


[BE] return stripe error in displayable format while creating customer

Coverage increased (+0.4%) to 91.951% when pulling c0078c527e019937d36abdc92b4731ec0fb4a088 on feature/stripe-error into 9e2c60bd8d2a051742e17d50234fffff375ac545 on master.

Coverage increased (+0.4%) to 91.951% when pulling 496091293a2046def1efcc8cbb5bfa46de43f416 on feature/stripe-error into 9e2c60bd8d2a051742e17d50234fffff375ac545 on master.


Research libraries for Python App GUI.

Kivy
Pros

Extensive video guides exist on youtube
Great for small-scale projects and styling UI
Does not require internet connection
Supports Windows, MacOS, IOS, and Android

Cons

Can have a steep learning curve
Not the best option for mobile UI applications
Requires PyInstaller to convert to executable (will trigger Windows virus warning)

Tkinter
Pros

Simple and easy to build UI
Already built-in to standard Python Library
Extensive documentation and video guides exist
Supports Windows and MacOS

Cons

Requires serious effort to style (like the HTML of UI styling)
Limited limited library of features
No built-in UI designer
Requires PyInstaller to convert to executable (will trigger Windows virus warning)
Does not support mobile device UI

Qt (pyQt6 or pyside6)
Pros

Powerful UI designing capabilities
Supports Windows, MacOS, IOS, and Android
Has UI designer capabilities (able to drag and drop widgets and features)

Cons

Seamless integration to IOS and Android UI will be more difficult than Kivy (either option is still difficult)
Requires PyInstaller to convert to executable (will trigger Windows virus warning)
Steep learning curve

Electron
Pros

Can integrate with existing web development to build a desktop application (i.e. Discord)
Supports Windows and MacOS
Extensive documentation and video guides exist on par with Kivy
Essentially a browser and server in one

Cons

Can be awkward to build a web app that only runs for desktop purposes
Hardware resource intensive
Large package size and boot-up time


Refactor forms and permissions

Short description

I refactored both the backend and the frontend of the forms and added more fine-graded permissions
Proposed changes

Centralized CSS for form fields

Add @tailwindcss/forms plugin for decent base styling
Put additional styling in the stylesheet
Remove duplicated css classes in html code
Make form styling more consistent

Add support for staff and non-staff roles

Add dedicated Role model with one to one mapping to django.contrib.auth.models.Group
Add boolean field staff_role

Refactor forms

Set additional instance attributes in CustomModelForm

Refactor Permissions

Use more fine-graded permissions for all models
Use inbuilt permissions where possible
Check for permissions instead of superuser/staff status

Resolved issues

Fixes (partially): #172
Fixes: #684
Fixes: #696
Fixes: #729

I'm aware that this PR cannot be reviewed in detail. But I suggest to do a superficial review and merge this PR soon anyway instead of leaving it open for weeks until somebody finds the time to check it extensively...

One way to let tests succeed is to extend the permissions of our test user with the role "management" by adding to src/cms/fixtures/roles.json
But I wonder why circleci is not detecting this permission problem thinking

Actually, the management role on this branch has this permission already, but unfortunately permissions are changing their ids each time the database changes, so for now there is no way of persisting these in an existing database.
To fix the permissions on your machine locally, you have to execute ./dev-tools/prune_database.sh before loading the new roles fixture. In the future, this problem will be fixed by resolving issue #748.


Typo in docs

Minor typo in docs

Does this PR need a docs update or release note?

[X] :white_check_mark: Yes, it's included
[ ] :clock1: Yes, but in a later PR
[ ] :no_entry: No

Type of change

[ ] :sunflower: Feature
[ ] :bug: Bugfix
[ ] :world_map: Documentation
[ ] :robot: Supportability/Tests
[ ] :computer: CI/Deployment
[ ] :broom: Tech Debt/Cleanup

Issue(s)

#

Test Plan

[ ] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

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


Azure SDK Review - [Introduction to Cognitive Services Computer Vision API]

New SDK Review meeting has been requested.
Service Name: Cognitive Services Computer Vision API
Review Created By: Darren Cohen
Review Date: 11/06/2023 06:05 AM PT
Hero Scenarios Link: here
Architecture Diagram Link: Not Provided
Core Concepts Doc Link: Not Provided
APIView Links:
Description: Review new SDK for Image Analysis
Detailed meeting information and documents provided can be accessed here

Meeting updated by Darren Cohen
Service Name: Cognitive Services Computer Vision API
Review Created By: Darren Cohen
Review Date: 11/06/2023 01:05 PM PT
Hero Scenarios Link: here
Architecture Diagram Link: Not Provided
Core Concepts Doc Link: Not Provided
APIView Links:
Description: Review new SDK for Image Analysis
Detailed meeting information and documents provided can be accessed here

Meeting updated by Darren Cohen
Service Name: Cognitive Services Computer Vision API
Review Created By: Darren Cohen
Review Date: 11/06/2023 01:05 PM PT
Hero Scenarios Link: here
Architecture Diagram Link: Not Provided
Core Concepts Doc Link: Not Provided
APIView Links:
Description: Review new SDK for Image Analysis
Detailed meeting information and documents provided can be accessed here

Meeting updated by Darren Cohen
Service Name: Cognitive Services Computer Vision API
Review Created By: Darren Cohen
Review Date: 11/06/2023 01:05 PM PT
Hero Scenarios Link: here
Architecture Diagram Link: Not Provided
Core Concepts Doc Link: Not Provided
APIView Links: Java, Python,
Description: Review new SDK for Image Analysis. TypeSpec PR: https://github.com/Azure/azure-rest-api-specs/pull/26146
Detailed meeting information and documents provided can be accessed here

Meeting updated by Darren Cohen
Service Name: Cognitive Services Computer Vision API
Review Created By: Darren Cohen
Review Date: 11/06/2023 01:05 PM PT
Hero Scenarios Link: here
Architecture Diagram Link: Not Provided
Core Concepts Doc Link: Not Provided
APIView Links: Java, Python, .NET,
Description: Review new SDK for Image Analysis. TypeSpec PR: https://github.com/Azure/azure-rest-api-specs/pull/26146
Detailed meeting information and documents provided can be accessed here

Meeting updated by Darren Cohen
Service Name: Cognitive Services Computer Vision API
Review Created By: Darren Cohen
Review Date: 11/06/2023 01:05 PM PT
Hero Scenarios Link: here
Architecture Diagram Link: Not Provided
Core Concepts Doc Link: Not Provided
APIView Links: Java, Python, .NET, Javascript,
Description: Review new SDK for Image Analysis. TypeSpec PR: https://github.com/Azure/azure-rest-api-specs/pull/26146
Detailed meeting information and documents provided can be accessed here

Meeting updated by Darren Cohen
Service Name: Cognitive Services Computer Vision API
Review Created By: Darren Cohen
Review Date: 11/06/2023 01:05 PM PT
Hero Scenarios Link: here
Architecture Diagram Link: Not Provided
Core Concepts Doc Link: Not Provided
APIView Links: Java, Python, .NET, Javascript,
Description: Review new SDK for Image Analysis. TypeSpec PR: https://github.com/Azure/azure-rest-api-specs/pull/26146
Detailed meeting information and documents provided can be accessed here


remove special handling of inverse boolean flags

:warning: WIP :warning:
Closes https://github.com/erikhuda/thor/issues/417#issuecomment-45052020.
This is a superset of #473, removing all special handling of boolean flags generating/parsing the inverse. It certainly makes the behavior more straightforward (no magic flags), though I realize checks for "negative" flags (like options[:no_public] == true) become a little more confusing. Thoughts? Also, I'm new to this codebase, so while all tests are passing, would love another set of :eyes: to ensure I got everything.

I just ran into this when wrapping an AWS CLI command that had a --no-verify-ssl option. Thor ended up spitting out --no-verify-ssl and --no-no-verify-ssl.
In certain cases, it would be nice if there was a way to get both through a specified type (e.g. :magic_boolean).

See https://github.com/erikhuda/thor/pull/473#issuecomment-279279157


ARTEMIS-888 - default to false if header durable not set

https://issues.apache.org/jira/browse/ARTEMIS-888

These failures look unrelated


Go CDK

https://github.com/nimblehq/git-template/issues/??
What happened 👀
Describe the big picture of your changes here to communicate to the team why we should accept this pull request.
Insight 📝
Describe in details how to test the changes, which solution you tried but did not go with, referenced documentation is welcome as well.
Proof Of Work 📹
Show us the implementation: screenshots, gif, etc.

@junan should we move all files on this PR to /junan folder


tortoise: enable neutral votes

Motivation
If some smeshers fail to reach hare consensus in time they will vote for an empty layer. It causes long-running recovery and stalls the network for hours (it takes 6-10h every single time). Neutral votes will prevent such delays.
As we cannot use layer clock in tortoise (because of this dep https://github.com/spacemeshos/go-spacemesh/issues/3003) I pass last layer as a parameter to EncodeVotes method.
closes: https://github.com/spacemeshos/go-spacemesh/issues/3137
Changes

remove layer organizer, as tortoise should be able to accept hare results out of order
do not count votes from layers out of order by keeping track of decided layers
pass current layer as an option to EncodeVotes (previously BaseBallot) method. this way it doesn't affect vote counting and the global threshold. in later iteration we will remove this option and use last layer according to the clock

bors try

bors try

if current layer is 100, and layer 97 have not terminated, before we will only encode up to layer 96. with this PR, we will be able to encode abstain for layer 97, 98, and 99?

yes, exactly like that

bors try


Wordlists and requirements.txt not downloadable

The wordlist download links in the README don't lead to downloadable text files but to git-lfs pointers. After downloading, installing, and running git lfs fetch in a cloned repository, the command fails with the following message:
batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.
error: failed to fetch some objects from 'https://github.com/NorthwaveSecurity/wikiraider.git/info/lfs'

Furthermore, it seems that all text files in the repository are tracked by git-lfs, not just the wordlists. This includes requirements.txt, so the dependencies to run the program can't actually be installed.
If the wordlists are too large to store in git, it'd probably be better to make them available as zip files using the release feature of Github.

I've just fixed it by migrating to SharePoint. Check the updated readme for the download links.


the merge function doesn't work correctly when total lines of sorted files and the merged file not match

as I describe in title
when I tried to split a large csv file to small file, sort them and merge them to one, I found that each file has equality file size. but when I tried to sum number of lines of each file, the total number of line does not match the total line of merged file
total sorted files (this is correct) < total merged file (this is incorrect)
the merge function is ExternalMergeSorter.cs
private async Task MergeFiles(IReadOnlyList<string> sortedFiles, Stream target, CancellationToken cancellationToken)

Sorry, I don't remove the existing file before re-creating it again, so the whole content not change since the last fail run


Package publishing

We want to use GitHub Package(Maven) for other project in GitHub

https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry


Replace response content with icons

Purpose

Replaced Exploring and User Manual Model content with icons
Font-Awesome was included in the project
The alert in the response card was removed
Minor CSS fixes

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[x] Other... Please describe: UI

Try using this cdn link https://stackpath.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css

You removed the borders that were essential to identify what was the matching result type.
Additionally, for this scenario, I believe that it's better to use the local package. We need internet to consume the Cognitive Services APIs but as it's a demo, it's better to have everything locally to avoid external issues

I will close this one and create a new one to avoid loosing things with all the EOL conflicts and the removal of things that shouldn't be removed


Issue with connecting multiple provider container networks

Right now, to run multiple provider containers, we start the first provider container by network name, and then start the other providers by the name of the first provider container. This is probably unnecessary, and can be cleaned up in a way to start each provider with the network name.
However, after attempting this, only the first running provider container connected to the analyzer even though inspection of the network showed all provider containers connected.

Connecting the containers to the same network does work now, it's just done poorly. Bumping to 0.6


Socket Hang Up during CDP to Android Chrome over USB

Trying to run example to Android Chrome with following configuration, chrome is crashing in Mobile and I could see this trace.
{ Error: socket hang up
    at createHangUpError (_http_client.js:335:15)
    at Socket.socketOnEnd (_http_client.js:428:23)
    at Socket.emit (events.js:185:15)
    at endReadableNT (_stream_readable.js:1101:12)
    at process._tickCallback (internal/process/next_tick.js:114:19) code: 'ECONNRESET' }

I'm able to list, create or activate sessions but CDP() not working in seems.

Component
Version

Operating system
Windows

Node.js
9.8.0

Chrome/Chromium/...
Android 7.1.1 Chrome 65.0

chrome-remote-interface
0.25.5

Is Chrome running in a container? NO
Am I missing something here??

Well this is weird because you can list etc. so the endpoint is reachable. Try to navigate to http://localhost:9222 from your PC and click on a mobile tab to inspect it with DevTools. Does it work?

Yes, it's accessible. Also I can inspect using chrome remote devices. Only CDP() is not working, showing this trace only. I also tried enabling USB debugging in different modes.

That error basically means that the server killed the connection prematurely. You can try to manually establish a WebSocket connection to a mobile tab with wscat, like this:
$ wscat -c ws://localhost:9222/devtools/page/E01769528A12C255DF71685CE2CEF573
connected (press CTRL+C to quit)
> {"id": 1, "method": "Runtime.evaluate", "params": {"expression": "alert(1)"}}
< {"id":1,"result":{"result":{"type":"undefined"}}}

You can obtain the address by listing the remote tabs. You should see a message box popping on the mobile tab.

I tried this and I'm able to establish the connection using wscat and able to run the Json script.
But when I keep this connection open and execute the node file with only following code
const CDP = require('chrome-remote-interface'); CDP((client) => {     console.log(client) }).on('error', (err) => {     console.error(err); });
it again crashes the chrome in mobile and the wscat connection also shows disconnected :(

it again crashes the chrome in mobile and the wscat connection also shows disconnected :(

Oh, if there is a crash then this is probably a Chrome bug. I cannot try to reproduce this right now, I'll do it ASAP.

Alright.
Meanwhile, do you have information for minimum compatibility version of Android & Chrome, that you would have seen working?
I can limit my work till that version using emulators for time being.
Thanks for quick response and hope to hear soon.

Yes, I can confirm, it crashes mobile Chrome. In particular, it's fetching the protocol that triggers the crash. You can reproduce it with:
curl http://localhost:9222/json/protocol

This is definitely a Chrome bug that you should file here. Feel free to post the link here if you decide to do so.

Well I tried with version 63 and 64 also, similar behavior.
I raised a bug and here is the link here for tracking.
Thanks

Thanks, as a workaround you can set the local option to true I guess.

Thanks a ton, with { local: true }, I am able to make connection. 💯


Define the required environmental sounds

The enviromental music/sounds to be used were defined in the "Audio" section of our GDD.
GDD: https://docs.google.com/document/d/1iHbk6SjNvEBSYVCmc0KMylksYg6bwNcP/edit#heading=h.2ymiyeoplnaj


Don't Merge! PR real time test for source branch full build

OPS Build status updates of commit b333611:
:clock10: Full build: the average full build time is 6 min(s) 14 sec(s) This is based on the last 108 build(s) for this repository
:warning: This is a FULL build due to a configuration change (usually in openpublishing.publish.config.json and/or docfx.json). It is strongly suggested to merge this configuration change after the business hours, as it could impact the overall build performance of other PRs on the '.openpublishing.publish.config.json' branch. For more detailed info, please click here.

OPS Build status updates of commit b333611:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

docfx.json
:white_check_mark:Succeeded

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


019-11-09 00:27:33 ERROR (MainThread) [frontend.js.latest.201910251] http://nosuch:8123/community_plugin/lovelace-media-art-background/media-art-background.js:4:64 Uncaught TypeError: Cannot read property 'transition_opacity' of undefined

I installed from HAC and added the recommended into the raw config editor:
resources:
  - type: module
    url: /community_plugin/mini-media-player/mini-media-player-bundle.js
  - type: module
    url: /community_plugin/lovelace-media-art-background/media-art-background.js
title: Home
media_art_background:
  blur: 10px
  entities:
    - media_player.main
    - entity: media_player.snapcast
      image_attribute: entity_picture
      valid_states:
        - playing
  opacity: 0.5

Hmm, that's odd. I'm honestly not quite sure why that would happen.
What browser are you using?

Chromium Version 78.0.3904.87 (Developer Build) (64-bit)
Seems to have resolved itself, all working and the error is gone.
On Sat, Nov 9, 2019 at 7:31 AM Sylvia van Os<EMAIL_ADDRESS>wrote:

Hmm, that's odd. I'm honestly not quite sure why that would happen.
What browser are you using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TheLastProject/lovelace-media-art-background/issues/8?email_source=notifications&email_token=ADK4KGOPKNXLL6LSOMKISOLQS23SBA5CNFSM4JLD4CY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDUGGUA#issuecomment-552100688,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADK4KGNYGLI62HQUPGV3R3TQS23SBANCNFSM4JLD4CYQ
.

Weird. Well, glad it's working now at least!


response()->json() output lets loaded relations override properties.

Laravel Version: 5.7.27
PHP Version: 7.2.11
Database Driver & Version: Not relevant

Description:
When I load a relation on say the user model (doesn't matter), invoices for example, and then try to modify the users invoices (in my case filter out some unwanted results), the results of the filter are written to the user->invoices property/attribute, but the original relation results remain the same in the model, as expected.
When I try to return the $user object in this case, the JSON output overrides the invoices property/attribute with the previously loaded relation, thus returning all relations results instead of the filtered ones.
I'm not entirely sure if this is an actual bug, but it sure didn't do what I was expecting.
Steps To Reproduce:
Route::get('/test/{user}', function (User $user) {
    $user->load(['invoices']);

    $user->invoices = null;

    return response()->json([
        'user' => $user
        // the content of $user->invoices after this point is the relations loaded on the load call, not null.
    ]);
});

$user->invoices = null; only affects the model's $attributes property, but the relationships are stored in $relations.
Use setRelation() instead:
$user->setRelation('invoices', null);

Can you try the solution proposed above?

@staudenmeir @driesvints
I came to that conclusion as well, as I said in my description of the problem, the behavior on the model itself is as expected, however, when outputting the model as JSON, I would except that the property invoices has precedence over the relation invoices.

@staudenmeir @driesvints
This originates in Illuminate\Database\Eloquent\Model:1076 in the toArray method.
As you can see the relations are merged into the attributes array, causing the override.

It is because $this->invoices only references your actual relationship and not the state your model currently is in. You'll first need to save its state before continuing and/or either refresh it.

I don't think this issue should be closed just yet.
If the behavior of toArray is as intended, then the order/behaviour of getAttribute is inconsistent with toArray.
You see, when I dd $user->invoices before the response()->json() in my example above, I do get the null value.
This is because in Illuminate\Database\Eloquent\Concerns\HasAttributes in getAttribute, the existence of the attribute is checked, and if it exists that value is returned, only after that the relations existence is checked and returned if present.
So basically:
In getAttribute the attribute invoices has precedence (which is logical in my opinion).
In toArray the relation invoices has precedence.

I see your point, but I would argue that there shouldn't be a case where $attributes and $relations contain the same key. Relationships aren't really meant to be changed like this.


URL signing API

As reported on the mailing list, an API for signing segment URLs would be useful for those using Amazon S3 or CloudFront.
This can be done today with a subclass of shaka.dash.DashParser, but a simple API for this would be preferable.  Signing could be done with a more generic manifest-filtering API, but something that only processes segment URLs would be much easier to use.

Actually, I am not sure this makes sense anymore.  AWS recommends using signed cookies instead of signed urls when distributing content from cloudfront.  In this case, the shaka player would need to be able to support sending multiple cookie headers for the manifest, and segment urls.

We do support cookie authentication.  See the "Cookie Authentication" section of the "License Server Authentication" tutorial.  The filters in the tutorial are looking for license requests, but you could just as easily accept manifest and/or segment requests, too.
Should we go ahead and close this feature request, then?

Yeah I would say close it

Okay, thanks for your feedback.

@joeyparrish Is the suggested method above (editing manifest with pre-signed urls) the best way to achieve this at this time? I am attempting to load content from an S3 bucket that is not public, and believe I am running into a similar problem as discussed on the mailing list link above. I am pre-signing the link to the manifest, and feeding that into shaka-player, however when it attempts to load each segment it does not have access as the base urls from the manifest have not been pre-signed.

No.  In the year since this issue was closed, we've introduced asynchronous network filters (starting in v2.1, current release is v2.2.1), which are ideal for this type of authentication.  In short, you can delay a request while you fetch an authentication token, then attach the token and let the original request proceed.  There is a tutorial showing how this works:
https://shaka-player-demo.appspot.com/docs/api/tutorial-license-server-auth.html
You should skim through the tutorial to find the section which applies to your form of authentication: parameters, headers, or cookies, whichever is appropriate to your application.  Then pay special attention to the section called "Asynchronous Credentials", which will show how best to fetch auth tokens.
Although it is geared toward license server authentication, you can apply it to any requests, including segment or manifest requests.
Does that help?

Hey, sorry taking so long to get back to you. I think this could possibly work, but I need to dig into it more. Will be back if it doesn't! Thanks for the help! 😄


Brotli extension support

Stub for Brotli extension https://pecl.php.net/package/brotli, https://github.com/kjdev/php-ext-brotli
First time doing this, so hope everything is correct. Extension also has steam prefix compress.brotli and OB handler ob_brotli_handler, but I am unsure how to add them, if they can/should be added even. I am also not entirely sure about values for constants besides compression, since I do not see them in the extension's code itself, so I took them from https://brotli.org/encode.html and https://rcos.io/static/internal_docs/brotli_sys/index.html under assumption, that they would be the same.

@Simbiat Could you please update stubs map https://github.com/JetBrains/phpstorm-stubs?tab=readme-ov-file#how-to-update-stub-map and add appropriate folder name to \StubTests\TestData\Providers\Stubs\PhpCoreStubsProvider::$StubDirectoryMap under 'PECL' array? thank you!

What if I do not have docker? Or PHPUnit, for that matter, which is required for running tests. For the map, can I just run tests/Tools/generate-stub-map script using my local build of PHP?

For the map, can I just run tests/Tools/generate-stub-map script using my local build of PHP?

Yes, generally you can run scripts using local interpreter as well

Added updated map along with minor fixes for types


How do I find the values to put into my typings.json?

Description
I am trying to figure out how typings works and the examples that I've found do not explain how to derive/determine the (for lack of a better term) typings registry key for any particular package for which I need typings.
Example
{
   "ambientDependencies": {
      "es-shim": "registry:dt/es6-shim#0.31.2+20160317120654",
      "jasmine": "registry:dt/jasmine#2.2.0+20160412134438"
   }
}

It looks like the:
"registry:dt/es6-shim#0.31.2+20160317120654"
and
"registry:dt/jasmine#2.2.0+20160412134438"
specify the version of the component for which the typings would need to be retrieved... is this correct? and how does one go about determining what these values should be for any specific version of a package? and is there a correlation between the version number of a package (as registered via npm) and the version number of the typings for the package?
Version
1.2.0

You can get the tag part from typings info dt~jasmine --versions.
But you normally should not edit typings.json manually.

OK ... if I shouldn't edit typings.json manually, how should I create it?

@Neoheurist You can edit it by hand if needed. You can also create it by just creating an empty file or using typings init. However, writing dependencies by hand can be tedious. It's definitely easier to just do typings install --save.

Does typings install -save look at my package.json to determine the typings / typing versions that I need for my project and then it fills in the typings.json file?

No.

You probably want a feature more like this: https://github.com/typings/typings/issues/24.

A feature to do this for me would be great - but I'm still left with the question of how to determine that "registry:dt/es6-shim#0.31.2+20160317120654" corresponds to my     "es6-shim": "0.35.1", entry in my package.json "dependencies"... are there instructions somewhere to help me figure this out?

For dt~ it probably only get/show the latest. You can check other typings in registry to understand it better

The semver tag of the registry is the minimum compatible version with the library - so you've installed 0.31.2 which most likely compatible with 0.35.1.

Thanks for the information... but I'm still not sure "how" to determine the correct registry reference... instructions in the form of the following would be helpful to me (and my colleagues with whom I am working on a project with):

Start a new Typescript project (perhaps an Angular 2 project)

Within the project's package.json file add component dependencies to be loaded from npm
"dependencies": {
"@angular/common": "2.0.0-rc.2",
"@angular/compiler": "2.0.0-rc.2",
"@angular/core": "2.0.0-rc.2",
"@angular/http": "2.0.0-rc.2",
"@angular/platform-browser": "2.0.0-rc.2",
"@angular/platform-browser-dynamic": "2.0.0-rc.2",
"@angular/router": "2.0.0-rc.2",
"@angular/upgrade": "2.0.0-rc.2",
"angular2-in-memory-web-api": "0.0.12",
"bootstrap": "3.3.6",
"es6-shim": "0.35.1",
"reflect-metadata": "0.1.3",
"rxjs": "5.0.0-beta.6",
"systemjs": "0.19.31",
"zone.js": "0.6.12"
},

Determine which packages require typings by ... (? compiling and receiving typescript errors such as ? and ? and ?) --- in this case es6-shim requires typings...

Visit / search (some github or other locations) to find the typings for the packages that require typings. --- for es6-shim the typings are in [[some location]]

Determine the version of the typings that is needed using [[some procedure/rule]] --- for es6-shim 0.35.1 the version would be [[some version]].

Create an empty typings.json file using the typings init command.

Add an entry in the typings.json file for each package in the form "{component-name}": "registry:{registry source}/{component-name}#{X.Y.Z}+{Magic number}" --- where {component-name} corresponds to [[something]], and {registry source} is determined by [[some rules]], and {X.Y.Z} are matched up by semver where the highest semver in the typings repository that is less than or equal to the version of the package being used, and the {Magic number} can be found/computed by [[some location/rule]].

Use the 'typings install --savecommand to pull and store the required typings in thetypings` directory of your project.

If this type of step-by-step documentation exists somewhere, please point me to it... if it does not exist I'd be happy to write something up and contribute it back to your project... if I'm totally misunderstanding let me know (sometimes I get a bad mental model and it skews my thinking so that I can't see the obvious answer)

For 4-5 use typings search
For 7-8 use typings install <...>seetypings install -h`
You should not edit typings.json manually.

An attempt to succinctly illustrate the steps to get from package.json to typings.json
https://neoheurist.wordpress.com/2016/06/20/definitely-typed/

@autopulous That's a great write up.
A couple of clarifications - the only source that may require manual trial and error is DefinitelyTyped, all the rest are named by mirror in the Typings registry. When you find something that doesn't match (in the registry or DefinitelyTyped) feel free to make an issue, we should start improving this. The only other thing I'd mention is to not recommend postinstall. A lot of people try to use it but don't understand it, and it breaks a lot of people (it will run when someone installs your package, which Typings will fail if said user is having network trouble or behind a proxy). Rather, I'd recommend using the prepublish step.
On the not editing it manually, just like package.json some manual intervention is required (E.g. setting the main source output if you're changing it, setting some package setting), but it's much easier to let the tool handle it where possible (which is usually just installing packages).

@Neoheurist probably a little late, but I think I was looking at the same as you and this did the trick:
npm run typings -- install dt~jasmine --save --global
Change jasmine for your package name

i still not get it, but they say all my typing.json is deprecated, so i need to change those but how if not manually ???
idk what to do,

@KingGeneral Did you read the thread? The answer is in the comment directly above. Just run the install command: typings install dt~core-js --save --global.


docs(manual): write content for scheduler.md

Description: Write documentation content on Schedulers, for the docs site.
Related issue (if exists):
#1060, #1242

LGTM.  I'd also include the Virtual Time Scheduler as well as TestScheduler stuff in there as well as those are scheduler instances you can use.  I'd also add a little blurb as to why the schedulers are there such as enabling virtual time.  In addition, if we're going to have a section of testing, we should link to that along with any notion of a virtual time or test scheduler

I absolutely agree. The whole Virtual Time Scheduler story is not addressed in this PR but it'll get its own PR. One reason why VT Scheduler was not listed alongside asap, async and others is that currently even in the API they are not available under Rx.Scheduler.*.

@staltz I guess this is a question then for @trxcllnt then about having things like Scheduler.requestAnimationFrame and others here or are they in DOM specific documentation?

Hard to tell in which category things fit.

Merged with 9a9baac, thanks @staltz


Add VoiceOver support

Git is weird, so how about I make a PR to your fork, then you make a PR to the main repo?

Oof sorry wrong branch


Adding Content Trust

PR Summary
Adding Content Trust to Azure Container Registry.

Currently AKS doesn't supporting pulling signed images, but this is coming.  GH issue

PR Checklist

[ ] PR has a meaningful title
[ ] Summarized changes
[ ] This PR is ready to merge and is not Work in Progress
[ ] Link to a filed issue

The trailing whitespace changes are throwing me off 😨
But looks good. 👍
Can you put the new parameter into this configuration please, with a value of true?
https://github.com/Azure/Aks-Construction/blob/main/.github/workflows_dep/regressionparams/optimised-for-well-architected.json
It'll ensure that it gets included in regression tests, and that parameter file in particular is what gets used for the Well Architected Optimal configuration, which this feature supports.

Great, that's getting picking up nicely now 🏅


WebStorm debugging tool didn't work out-of-the-box

WebStorm is a great IDE
and i feel like many people also use this tool for debugging, if not Chrome Debugger Tool.
Basically, you can install JetBrain in Chrome Extension and then you can use this IDE for debugging.
However, with WebPack, we need source map file for debugging real file.
And with source map, look like JetBrain currently only work for this parameter in webpack config
devtoo: 'source-map'
I mean this line should change to the above config
https://github.com/mxstbr/react-boilerplate/blob/56eb5a0ec4aa691169ef427f3a0122fde5a5aa24/internals/webpack/webpack.dev.babel.js#L65
So it could make it work with JetBrain out-of-the-box
But i'm not sure what is the consequences, what do you think?

The choice of source-map settings was made for performance reasons see #541 and #411.
Having said that, WebStorm is a popular IDE, if you would like to submit a PR to add the necessary configuration to get WebStorm's debugger working with react-boilerplate, that would be a helpful addition.

I don't think we should enable that source map by default to be honest, since not everybody will use WebStorm, but this should definitely be added to the FAQ! :+1: Good catch @chaintan17!

if you would like to submit a PR to add the necessary configuration to get WebStorm's debugger working

@mxstbr @chaintan17 Oops, I meant to say "... add the necessary configuration to the docs to get...
My bad for not proofing 😦

i create pull request here https://github.com/mxstbr/react-boilerplate/pull/723

Done by the amazing @chaintan17 in #723!


Track all the entry points from Service Teams to the Azure SDK team

The goal of this issue is to figure out how to track how teams are finding the link to the application. The following places are likely:  Our wiki pages, once updated the Arch Board GitHub page, APEX wiki, Cloud Lifecycle launch criteria description, and word of mouth

the proposed solution is to add different parameters to link in different entries

We should start catalloging the specific places to make sure they are updated correctly

Agree.  I change the category to be 'Design', and Area to be ‘Documentation’.

We have added a question for this in the Release Planner survey: https://github.com/Azure/azure-sdk-tools/issues/5463


Need ability to get component pathing from driver URL

Today we have a custom hardcoded path for ODSP drivers to get component pathing from a driver URL (the opposite functionality of getAbsoluteUrl). We want to replace this with Framework native support. Either an interface on all resolvers that fulfills this contract ("resolveDataStore") or some other helper similar to what Loader.request() does to request the component path.
Related to the discussion here: https://github.com/microsoft/FluidFramework/issues/4169 which concluded we can use Loader.request() instead of needing this functionality. However, we are blocked on using Loader.request() because of container caching issues: https://github.com/microsoft/FluidFramework/issues/4489
@agarwal-navin @anthony-murphy @jatgarg
This is related to a core Fluid Framework scenario: Going from a Fluid resource URL to a Fluid object using the Loader object. Today without proper support for Loader.request (see #4489 and #4498), the only way for us to load a component is to parse out the component path from the URL separately using a SPO driver custom export and then call Loader.resolve() and Container.request(). This seems like one of the first promises that the Fluid Framework makes - that you can directly use the Loader object to load a Fluid object and should likely be fixed. :)

@leeviana Can you create a new issue describing the scenario that you're trying to address, and link these issues to the new uber-issue? That wasx we can better understand what you're doing and what changes are needed in the framework.

Yeah, I can do that, this one is the most fundamental of Framework capabilities, going from a URL to a Fluid component using the Loader. :P Do we need another issue or should I just edit this one to be more scenario oriented? Otherwise I don't think there's a need for this issue any longer if I create a duplicate.

Updated the issue with information about needing to go from a Fluid URL to a Fluid object using the Loader object.

@leeviana

Related to the discussion here: #4169 which concluded we can use Loader.request() instead of needing this functionality. However, we are blocked on using Loader.request() because of container caching issues: #4489

I'm a bit confused. Per #4169 the ultimate solution seems to be using Loader.request, which you're blocked on from #4489. This leads me to think that the issue here is a temporary solution? The fix for #4489 is scheduled for January; I'm not inclined to do anything temporary when a real fix is coming soon.

Is it confirmed that #4489 is happening in the January timeframe? If it is, then of course we should wait on it, but all I've seen so far is general discussion about what work could happen if someone wanted to do it and the January tag which doesn't mean much since issues just get rolled over from month to month. If it is happening sometime soonish then hopefully we won't need this, but this is a pretty core piece of Fluid functionality to leave broken for so long.

I am closing this as #4489 is the right solution.    @heliocliu for visibility about this dependency.

I am closing this as #4489 is the right solution.    @heliocliu for visibility about this dependency.

@anthony-murphy There seems to be quite a bit of confusion the over what is actually needed.  From reading all these thread.  It seems that #4489 should be sufficient to unblock @leeviana.   Is there addition capability that is fundamental in this area that is missing?

@anthony-murphy There seems to be quite a bit of confusion the over what is actually needed.  From reading all these thread.  It seems that #4489 should be sufficient to unblock @leeviana.   Is there addition capability that is fundamental in this area that is missing?

Yes, there might be other needs for generic component path parsing, but not ones that the core loader flows need right now. #4489 (and #4491) will directly enable us to get rid of componentPath logic entirely in our loading pipeline as intended by the Framework.

Yes, there might be other needs for generic component path parsing, but not ones that the core loader flows need right now. #4489 (and #4491) will directly enable us to get rid of componentPath logic entirely in our loading pipeline as intended by the Framework.

Since both #4489 and #4491 are closed, let's close this one for now. I think this is probably still an API reuse/need someone will need but for our specific loading scenario we avoid this problem with the resolution of those two bugs.


PLAT-11685: Garnet: Removed PanelSet samples

Issue
: We provided garnet/PanelManager and don't need garnet/PanelSet control.
So we need to remove the samples related with garnet/PanelSet.
Fix
: Removed the samples below

PanelSetDepthInMoveSample
PanelSetDepthtInDepthSample
PanelSetMoveInDepthSample
PanelSetMoveInMoveSample
PanelSetPanelSample
PageIndicatorSample

https://jira2.lgsvl.com/browse/PLAT-11685
Enyo-DCO-1.1-Signed-off-by: YB Sung<EMAIL_ADDRESS>

Okay.
Reviewed-By: Seungcheon Baek<EMAIL_ADDRESS>

It should be merged into PLAT-11357-Garnet-NewUX branch.


[image_picker] Permission error for camera picker on OnePlus 3 with Android 9 (API 28)

Steps to Reproduce

use basic example: https://github.com/flutter/plugins/tree/master/packages/image_picker/image_picker/example (image_picker: 0.8.3+1, commit: acc3202466a8b4c0b1bcb91fc1ce520c7b021e44)
Run on OnePlus 3 (ONEPLUS A3003), Android 9 (API 28)
Try to pick an image with the camera within the app
It will open camera to pick the image
Take an image
Confirm the image
Nothing more happens for the user (permission exception is thrown in the logs)
java.lang.SecurityException: Permission Denial: writing com.android.providers.media.MediaProvider uri content://media/external/file from pid=2662, uid=10227 requires android.permission.WRITE_EXTERNAL_STORAGE, or grantUriPermission()
when using the camera picker again you the following exception is thrown/shown:
PlatformException(already_active, Image picker is already active, null, null)

Expected results:
Camera picker works on OnePlus 3 and I can reuse the picker again.
Actual results:
Permission error on OnePlus 3 (ONEPLUS A3003) with Android 9 (API 28). The picker can not be used anymore after that, since it states in the logs, that is already in use. The app has to be restarted to use the picker again.

Logs
[   +1 ms] W/Binder  ( 2662): java.lang.SecurityException: Permission Denial: writing com.android.providers.media.MediaProvider uri content://media/external/file from pid=2662, uid=10227 requires android.permission.WRITE_EXTERNAL_STORAGE, or grantUriPermission()
[   +1 ms] W/Binder  ( 2662):   at android.os.Parcel.createException(Parcel.java:1950)
[        ] W/Binder  ( 2662):   at android.os.Parcel.readException(Parcel.java:1918)
[        ] W/Binder  ( 2662):   at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:183)
[        ] W/Binder  ( 2662):   at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
[        ] W/Binder  ( 2662):   at android.content.ContentProviderProxy.delete(ContentProviderNative.java:561)
[        ] W/Binder  ( 2662):   at android.content.ContentResolver.delete(ContentResolver.java:1813)
[        ] W/Binder  ( 2662):   at android.media.MediaScannerConnection$1.scanCompleted(MediaScannerConnection.java:83)
[        ] W/Binder  ( 2662):   at android.media.IMediaScannerListener$Stub.onTransact(IMediaScannerListener.java:61)
[        ] W/Binder  ( 2662):   at android.os.Binder.execTransact(Binder.java:752)

Analyzing example...
No issues found! (ran in 3.2s; 4 public members lack documentation)

[√] Flutter (Channel stable, 2.2.3, on Microsoft Windows [Version 10.0.19043.1110], locale de-AT)
    • Flutter version 2.2.3 at C:\sdk\flutter
    • Framework revision f4abaa0735 (5 weeks ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at C:\Users\USER\AppData\Local\Android\Sdk
    • Platform android-30, build-tools 30.0.0
    • ANDROID_HOME = C:\Users\USER\AppData\Local\Android\Sdk
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Android Studio (version 4.1.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] IntelliJ IDEA Ultimate Edition (version 2021.1)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2020.1.2
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart

[√] VS Code, 64-bit edition (version 1.58.2)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.24.0

[√] Connected device (3 available)
    • ONEPLUS A3003 (mobile) • 5b6fb83b • android-arm64  • Android 9 (API 28)
    • Chrome (web)           • chrome   • web-javascript • Google Chrome 92.0.4515.131
    • Edge (web)             • edge     • web-javascript • Microsoft Edge 91.0.864.64

• No issues found!

Hi @mangei
I just tried on Oneplus 8 (Android 11) on the latest package, has no issue. Given you specified this device, is the issue only this particular device? Can you please reproduce the Android 9 emulator or another physical Android 9 device?

I checked some more phones.
Worked:

Android 9 emulator
Fairphone 3, Android 10
OnePlus Nord, Android 11
Samsung Galaxy S9 (SM-G960F), Android 10, One UI 2.1

Did not work:

OnePlus 3, Android 8
OnePlus 3, Android 9
... I couldn't find another non-working phone yet.

Same problem on Meizu 16th android 8.1

@piuskamil which specific device do you have?

Same issue on One Plus 3T (A3010) with Android 9. Working on Xiaomi Redmi 4 with Android 6 and Xiaomi Mi A1 with Android 9.

I'm facing the same issue on my physical device. It crashes when picking from the gallery (tested device - Huawei Y6 ).
is there any solution for this issue?

I have the same problem on OnePlus 5 (A5000) with Android 9 (API 28), OxygenOS 9.0.8.

Logs
W/Binder  (32155): Caught a RuntimeException from the binder stub implementation.
W/Binder  (32155): java.lang.SecurityException: Permission Denial: writing com.android.providers.media.MediaProvider uri content://media/external/file from pid=32155, uid=10270 requires android.permission.WRITE_EXTERNAL_STORAGE, or grantUriPermission()
W/Binder  (32155):      at android.os.Parcel.createException(Parcel.java:1950)
W/Binder  (32155):      at android.os.Parcel.readException(Parcel.java:1918)
W/Binder  (32155):      at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:183)
W/Binder  (32155):      at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
W/Binder  (32155):      at android.content.ContentProviderProxy.delete(ContentProviderNative.java:561)
W/Binder  (32155):      at android.content.ContentResolver.delete(ContentResolver.java:1813)
W/Binder  (32155):      at android.media.MediaScannerConnection$1.scanCompleted(MediaScannerConnection.java:83)
W/Binder  (32155):      at android.media.IMediaScannerListener$Stub.onTransact(IMediaScannerListener.java:61)
W/Binder  (32155):      at android.os.Binder.execTransact(Binder.java:752)

flutter doctor -v
[✓] Flutter (Channel stable, 2.8.1, on Ubuntu 20.04 LTS <IP_ADDRESS>-microsoft-standard-WSL2, locale C.UTF-8)
    • Flutter version 2.8.1 at /home/zengraf/.asdf/installs/flutter/2.8.1-stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 77d935af4d (4 days ago), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /home/zengraf/android-sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_SDK_ROOT = /home/zengraf/android-sdk
    • Java binary at: /usr/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+8-Ubuntu-0ubuntu1.20.04)
    • All Android licenses accepted.

[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).

[✓] Connected device (1 available)
    • ONEPLUS A5000 (mobile) • <IP_ADDRESS>:5555 • android-arm64 • Android 9 (API 28)

I have the same problem with image_picker 0.8.4+4.
Alternatively, I'm using  images_picker: ^1.2.10. This is working.
But still, I would like to know the solution using image_picker 0.8.4+4.

same issue

did anyone solve this issue?

Same issue.
I tried to use the 'permission_handler' package to check permission on runtime, then the error was gone but the captured image is not returned from the 'image_picker' method of the image_picker package.
The issue is caused on OnePlus 5T, Android 8.1, the latest OS update.
Also, I tried to turn off additional settings of the camera like portrait mode, save location and etc, but this did not solve the issue.
Can't catch any log from this issue, but when I call 'pickImage' method again (after the first attempt), I get (already_active, Image picker is already active, null, null) error.
Please give any feedback on this issue.

I am facing issue of image picker issue on One Plus devices. did any one found the solution ?

same issue on meizu 16s, Android 9

same issue

Same issue here as well OP 3T and only if I am using camera, snap the picture. How can I at least capture null and throw modal or other info?

Same issue on MeiZu 16s, Android 9

@deeeznuds This isn't limitation of Android 9.  I have devices with Android 7, for instance Huaweit T3 tablet which works just fine.
What I have tested so far, once storage access is allowed:
      <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
      <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>

I can pick image from gallery just fine. So it's somewhere between that camera does not pass data back as callback.
I wonder would be possible (it is but where, how..) to capture exception and use image selection as fallback? - At least return error, instead of just getting stuck somewhere in between.

Any update on this issue?

No success so far, this is issue with core API and not plugins (from pub.dev) that are using it. A bit difficult to debug, as well. It's somethig for core team who knows Android inside-out as well.

I make some change hope this help
https://github.com/flutter/packages/pull/7516


keep NHWC format in file

The model reads the h5 file this way. As mentioned in my last pull request #42 ^^  Since the model reads the h5 file in NHWC as tensorflow does, the wh-tuple should be inverted for the h5dataset creation. Now it works as expected.

there are problems with return value if the lists are empty (end of dataset) and h5py if is_train is false. so in both predict and test mode.