Indent lines

Description
When you open the file explorer, it can sometimes be hard to determine the level of nesting for each of the files display. It would be great if there was indent lines displayed to help you determine that.

Lines showing the tree structure were removed from NERDTree nine years ago (commit eac3214), long before I took over support for it. I can only guess as to why, but Martin may have liked the cleaner look of the triangles and no lines. I have no plans to reintroduce the lines, because I think they clutter the display.
You can, however, simulate them to a certain extent with some clever syntax rules. Save the following text to your vim setup. Pay attention to the file's name and path:
~/.vim/after/syntax/nerdtree.vim
" This block displays every other leading space in the NERDTree buffer as
" a vertical bar. It works only if your vim has the +conceal feature
" turned on, and this file must be saved as ~/.vim/after/syntax/nerdtree.vim
" to work properly.

if has("conceal")
    syntax clear NERDTreeOpenable
    syntax clear NERDTreeClosable
    let s:dirArrows = escape(g:NERDTreeDirArrowCollapsible, '~]\-').escape(g:NERDTreeDirArrowExpandable, '~]\-')
    exec 'syntax match MarkIndents #\(  \)\{-}\zs \ze \(  \)*\(['.s:dirArrows.' ] \)\?'.g:NERDTreeNodeDelimiter.'# containedin=ALL conceal cchar=|'
endif

It will display every other leading space as a vertical bar, like so:

You will need to pull the latest version of NERDTree, and nerdtree-buffer-ops if you use it.

vim-devicons is another NERDTree plugin, and it sets conceallevel=3, which may cause the above snippet to not work, depending on the order in which they statements are called. If you are using it, you can create an issue there and reference this one.

This is great, thank you!

Could this be like a configurable setting? I would like to activate it too, and at the same time I wish this persists in my vimrc so I can easily replicate my environment on a different pc and such...
Thanks
PS: I could implement it and do PR but I need some hints how to do it

Could this be like a configurable setting? I would like to activate it too, and at the same time I wish this persists in my vimrc so I can easily replicate my environment on a different pc and such...
Thanks
PS: I could implement it and do PR but I need some hints how to do it

@alexnix No, as stated above, I won't reintroduce the lines into NERDTree. As far as your vim configuration goes, don't try to put every setup statement into your vimrc file. Your config can, and should, contain multiple files in several folders. The files in the different folders are sourced at the appropriate time or for specific purposes, and using the folders makes your config simpler than trying to accomplish that in a single vimrc file. Take a look at my Neovim setup for an example of how to do it. With it being in Github, replicating my vim environment is as simple as cloning the repo on a new machine.

@alexnix No, as stated above, I won't reintroduce the lines into NERDTree. As far as your vim configuration goes, don't try to put every setup statement into your vimrc file. Your config can, and should, contain multiple files in several folders. The files in the different folders are sourced at the appropriate time or for specific purposes, and using the folders makes your config simpler than trying to accomplish that in a single vimrc file. Take a look at my Neovim setup for an example of how to do it. With it being in Github, replicating my vim environment is as simple as cloning the repo on a new machine.


dontenv-cli not escaping dollar sign correctly

Environment
"dotenv-cli": "^5.0.0" (installed as dev dependency, not globally)
Mac OSX 11.1
I'm finding that this tool is incorrectly escaping the $ character when it's referencing a variable in a file that has been run with source.
Steps to Reproduce
Create a new file ~/.envTest file with the following:
export TEST_VAR="default\$default"

Run
$ npx dotenv -e ~/.envTest -- printenv TEST_VAR
default$default
$ source ~/.envTest
$ npx dotenv -e ~/.envTest -- printenv TEST_VAR
default
$ printenv TEST_VAR
default$default

This issue is forcing me to use a separate environment variable file that I don't source in order to allow this to work for my use case that requires the dotenv cli.

This is probably a bug in dotenv itself or in dotenv-expand


Support for tvOS

With the new Apple TV, the support for tvOS would be great. :)

Yes, please add tvOS support.

Support for Apple TV is the latest build.


Omnisharp support for CompactFramework

Environment data
dotnet --info output:
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.14393
OS Platform: Windows
RID:         win10-x64
Additional env data:

VisualStudio 2008 with ServicePacks
SDK to support WindowsMobile projects

VS Code version: 1.8.1
C# Extension version: 1.6.2
Steps to reproduce
I have solution where two projects target CompactFramework .net3.5.  (UI for WindowsMobile and WindowsCE). When I open solution - VSCode is unable to process these two projects. Other (not CF) are fine.
Visual Studio 2008 has no problems with compiling. Also I can successfully compile solution from CMD.exe with msbuild command
Expected  behavior
Process projects targeting CompactFramework and enable all goodnes
Actual behavior
Currentlu OmpniSharp outputs:
Microsoft.Build.Exceptions.InvalidProjectFileException: The imported project   "C:\Users\Piotr\.vscode\extensions\ms-vscode.csharp-1.6.2\bin\omnisharp\msbuild\Microsoft.CompactFramework.CSharp.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.

Support for legacy compact framework projects isn't going to be added for C# in VS Code. You should continue using Visual Studio 2008.

Only one question ...
I just opened the same solution in Sublime with omnisharp and funny thing ... I can navigate between types using F12, I also can find usages of given class etc..... this seems to be impossible with visual studio code.
Why is that?

It's likely due to the fact that Sublime Text is using an older version of OmniSharp which uses the MSBuild that is installed globally. With VS 2017, MSBuild is no longer installed globally and OmniSharp must carry a copy of MSBuild with it. Getting it to work with the CompactFramework may just be a matter of setting some MSBuild environment variables.


feat: add the release storage interface

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., design docs, usage docs, etc.:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.1%) to 55.041%

Files with Coverage Reduction
New Missed Lines
%

pkg/engine/operation/parser/parser.go
3
79.27%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
8658

Relevant Lines:
15730

💛  - Coveralls


add throttling to tg send

telegram can return  Error while sending message: Too Many Requests: retry after 41 error: 429

current tg limits 20 messages per minute


No tabs open leaves large blank space for tab bar on Ubuntu / Gnome Shell

OS version and name: Ubuntu 16.10 / Gnome Shell
Hyper.app version: 0.8.3
Link of a Gist with the contents of your .hyper.js: Is Fresh Install
Relevent information from devtools N/A
The issue is reproducible in vanilla Hyper.app: Is Vanilla

Issue
When I have no tabs open (i.e. a freshly loaded terminal with a prompt), there is a huge black void at the top of the screen where the tabs would otherwise be.
This should probably disappear when there are no tabs.

@antony  Friendly ping: This require a picture

I think theyre just talking about this:

Not exactly huge, but noticable.

Same on MacOS!

Hey there, please try again with the new Hyper v2 release and open a new issue if the problem stills exists. Thank you!


Create portable_settings.txt before install to persist as file, not dir

Currently if you install heidisql, the persist happens as a dir and it causes errors in the app (it will crash trying to write to portable_settings.txt).

Use check for persist_dir rather, then always creating that file
https://github.com/lukesampson/scoop-extras/blob/a84b257fd9636d02295b48c3fd32826487ca9bd3/bucket/aida64extreme.json#L10-L15

Is there a PR or a motion to improve some of the tooling out of the box with Scoop? I ask because there are too many undocumented "correct" ways to do things.
If we want to persist a file, isn't it better to just provide an option to the package to persist a file explicitly?
There is no mention here that persisting by default creates dirs: https://github.com/lukesampson/scoop/wiki/Persistent-data
Then when you run into the "dir" issue, you think OK, lets check the source: https://github.com/lukesampson/scoop/blob/master/lib/install.ps1 which has a nice comment:
# we don't have neither source nor target data! we need to crate an empty target,
# but we can't make a judgement that the data should be a file or directory...
# so we create a directory by default. to avoid this, use pre_install
# to create the source file before persisting (DON'T use post_install)

Then you see scripts like https://github.com/lukesampson/scoop-extras/blob/master/bucket/wiztree.json do it a way, so ok, you go that way.
If we had more sane tooling, we could enable more people to create higher quality packages from the start instead of a back and forth each time.
Anyways, I will make the change, just wanted to say that tooling in a package manager gives power to the people :)

Actually, you can leave it there, the persist logic will check if there is already target in persist_dir. And it will override the source when the app updates.

But if you do not check for it and create all the time, it will be duplicated. If you have large files / folders, you take much more space than you need.
For example. I experienced this while persisting folder, which is about 8GB on default. It's isos files on enterprise E2B build, and when you persist it you will take these 8GB for original and different size (persisted from before, which is usually bigger as you add more ISOs, now about ~100GB for all windows ISOs and partition images). So persist check is needed to save space (in this case deleting not creating, if there are already persited files).


Redirect can't work in IOS, but it works in Anriod.

What happened?

Please use the issue template.


Slack: cannot copy images from right-click context menu

Expected Behavior
Clicking "copy image" on the right-click context menu on a full-screen image copies the image to the OS pasteboard.
Current Behavior
Clicking "copy image" on the right-click context menu on a full-screen image does not copy anything to the OS pasteboard.
Steps to Reproduce

Open any Slack service and find an image post.
Click the image once to make it fill the Slack window.
Right-click the image.
Click "copy image".

Context
I keep trying to share images from Slack to my family on Whatsapp, but no luck.
Your Environment

Franz Version used: 5.0.0-beta.16.762
Operating System and version: macOS 10.13.3

Note that this bug does not exist in Whatsapp, nor does it exist using the Slack web client in Chrome.

This is not an issue with Slack specifically, it's an issue with all services I've used in Franz. I'm running Slack, Whatsapp Web and Discord, and it works on neither of them.

Franz Version: 5.0.0-beta.16
Operating System(s): macOS 10.13.3 (17D47)

This one is crucial.

It seems copying breaks entirely sometimes. I have to restart Franz to restore copy functionality.

I would really like this functionality.


Update composer.json for laravel 5.5

this needs to be a major version unless you want composer to be able to install 5.4 and 5.5

Codecov Report

Merging #84 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #84   +/-   ##
=======================================
  Coverage   76.12%   76.12%
=======================================
  Files          15       15
  Lines         356      356
=======================================
  Hits          271      271
  Misses         85       85

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 186bd39...50331f8. Read the comment docs.


Add a style guide for SQL code

:tada: see https://inbo.github.io/tutorials/tutorials/sql_styleguide/, coordinated by @fredericpiesschaert :+1: . Closing here!

Very nice guide @fredericpiesschaert! It seems I follow the guide almost completely, except that I always indent:
SELECT
    t.field1
  , t.field2
FROM
  table1 as t
WHERE
  1 = 1
  AND field1 = "something"

Rather than:
SELECT t.field1
  , t.field2
FROM table1 as t
WHERE 1 = 1
  AND field1 = "something"

Is the first version used often and/or recommended?


Getting started guide doc issue.

I have a question about step 4.
4 - Add the domains to the hosts files.
<IP_ADDRESS>  project-1.test
<IP_ADDRESS>  project-2.test

It's not all together clear to me what hosts file needs to be updated. The hosts file in the nginx container or the host machine?
Thanks for all of your work on this project it's pretty awesome!

It's on your host system. And there will be your nginx (or another http server) in the container, listening.


bash file type not resolved correctly for shfmt

First of all thank you for the great plugin particularly after null-ls having been archived! I ran into the same issue mentioned in #379 with bash (change it into sh in formatters_by_ft does the trick). I think it's a bit misleading to use language names instead of file extensions in the README example if that's not intended. However, if that is the best practice, shouldn't there be a table to maintain the mappings which I didn't find? Seems the lang_to_ext is for formatter injected particularly. It's not the default table. If there is such a table mapping, could anyone enlighten me where is it?

After a bit of research it seems it follows the filetype api of Neovim, which returns sh instead of bash for bash scripts if not forcing the bash file type manually fyi. The examples in README are correct e.g. :set ft? in a python file returns python.


When hovering over an Achievment, its name and description should be shown

Done with push: "Achievements added, without the disabling"


Bad Decompilation of List Traversal

Describe the bug
When the assembly is traversing a list structure that is in the process of clearing itself, the C code produced is, in this case, missing the assignment to (and usage of) the temporary variable in the loop and consequently looses the correct interpretation.
To Reproduce
Steps to reproduce the behavior:

Use the included xml from the "Debug Function Decompilation" facility.
Look at the decompilation
See error

Expected behavior
More correct decompiler generated code.
Screenshots
If applicable, add screenshots to help explain your problem.

Attachments
Zipped XML from the "Debug Function Decompilation" facility.
FreeGMemList.zip
Environment (please complete the following information):

OS: Windows 10 (20H2)
Java Version: 11.0.8
Ghidra Version: 9.1.2 & commit 3c683ae770cf495deb32588202b00b88e125a4a4c

Additional context
This is from a 16-bit Protected Mode Windows NE DLL.

Nothing's changed and we're now at Ghidra 11.3!  Is there any hope???


Upgrade strategy for data-plane review

Relate to #468, #501 #503
There are three major rules we want to have:

Upgrade subordinate before principle on the same machine to avoid bug: #468
Merge principle & subordinate applications upgrade into hypervisor.
The upgrade order shouldn't be broken in any situation.

We need to go through all the data plane applications to make sure upgrade strategy for all of them and apply to COU.

These three issues have been resolved, so I am closing this discussion.


[Windows]: cannot start due to 'export' command

While I was away at the conference I mostly worked from my laptop (M1 Mac)
Now that I'm back I tried some of the latest changes on Windows, and ran into this error from the typical workflow
npm ci
npm start

(from fresh environment of course), resulting in
vite v4.1.4 building for production...
transforming (245) node_modules\sweetalert2\src\utils\dom\renderers\renderCloseButton.jsUse of eval in "node_modules/lottie-web/build/player/lottie.js" is strongly discouraged as it poses security risks and may cause issues with minification.
✓ 250 modules transformed.
dist/index.js  2,790.21 kB │ gzip: 458.98 kB
'export' is not recognized as an internal or external command,
operable program or batch file.

Got it. This is unrelated to Vite and, instead, is triggered by the start command:
npm run build && export ENABLE_CORS=false && npm run start:electron

I'm trying to toggle between enabled and disabled Cross-Origin Resource Sharing (CORS) when using npm start vs npm dev. However, it looks like export XXX is only supported in UNIX shells.
Do you know of other ways to set this environment variable per command-line call? Otherwise, it wouldn't be terrible always to have it enabled / configurable from a .env file—though it doesn't need to be enabled when the Flask server is run with Electron.

Do you know of other ways to set this environment variable per command-line call? Otherwise, it wouldn't be terrible always to have it enabled / configurable from a .env file

The simplest way would likely be separate npm commands for windows, since it's only me that uses it


error with --no-cache in composer 1.9

This may or may not be an actual issue. But composer 1.9 now comes with a --no-cache global option which I tried to use for installing prestissimo in docker so that I don't have to call composer clear-cache afterwards. I understand the 2 are different but I thought perhaps prestissimo won't do anything yet when it's first installed (excuse my lack of understanding of how composer plugins work).
composer global require --no-cache hirak/prestissimo -v gives
/app # composer global require --no-cache hirak/prestissimo -v                                                                                Changed current directory to /tmp
Using version ^0.3.9 for hirak/prestissimo
./composer.json has been created
Loading composer repositories with package information
Updating dependencies (including require-dev)
Dependency resolution completed in 0.000 seconds
Analyzed 75 packages to resolve dependencies
Analyzed 46 rules to resolve dependencies
Package operations: 1 install, 0 updates, 0 removals                                                                                Installs: hirak/prestissimo:0.3.9
  - Installing hirak/prestissimo (0.3.9): Downloading (100%)
 Extracting archivePlugin installation failed, rolling back
  - Removing hirak/prestissimo (0.3.9)

Installation failed, deleting ./composer.json.

  [ErrorException]
  mkdir(): Not a directory

Exception trace:                                                                                () at /tmp/vendor/hirak/prestissimo/src/CopyRequest.php:103
Composer\Util\ErrorHandler::handle() at n/a:n/a                                                                                mkdir() at /tmp/vendor/hirak/prestissimo/src/CopyRequest.php:103
Hirak\Prestissimo\CopyRequest->createDir() at /tmp/vendor/hirak/prestissimo/src/CopyRequest.php:89
Hirak\Prestissimo\CopyRequest->setDestination() at /tmp/vendor/hirak/prestissimo/src/CopyRequest.php:39
Hirak\Prestissimo\CopyRequest->__construct() at /tmp/vendor/hirak/prestissimo/src/ParallelizedComposerRepository.php:26
Hirak\Prestissimo\ParallelizedComposerRepository->preloadProviderListings() at /tmp/vendor/hirak/prestissimo/src/ParallelizedComposerRepository.php:39
Hirak\Prestissimo\ParallelizedComposerRepository->prefetch() at /tmp/vendor/hirak/prestissimo/src/Plugin.php:150
Hirak\Prestissimo\Plugin->prefetchComposerRepositories() at /tmp/vendor/hirak/prestissimo/src/Plugin.php:82
Hirak\Prestissimo\Plugin->activate() at phar:///usr/bin/composer/src/Composer/Plugin/PluginManager.php:237
Composer\Plugin\PluginManager->addPlugin() at phar:///usr/bin/composer/src/Composer/Plugin/PluginManager.php:206
Composer\Plugin\PluginManager->registerPackage() at phar:///usr/bin/composer/src/Composer/Installer/PluginInstaller.php:62
Composer\Installer\PluginInstaller->install() at phar:///usr/bin/composer/src/Composer/Installer/InstallationManager.php:173
Composer\Installer\InstallationManager->install() at phar:///usr/bin/composer/src/Composer/Installer/InstallationManager.php:160
Composer\Installer\InstallationManager->execute() at phar:///usr/bin/composer/src/Composer/Installer.php:597
Composer\Installer->doInstall() at phar:///usr/bin/composer/src/Composer/Installer.php:229
Composer\Installer->run() at phar:///usr/bin/composer/src/Composer/Command/RequireCommand.php:218
Composer\Command\RequireCommand->doUpdate() at phar:///usr/bin/composer/src/Composer/Command/RequireCommand.php:175
Composer\Command\RequireCommand->execute() at phar:///usr/bin/composer/vendor/symfony/console/Command/Command.php:245
Symfony\Component\Console\Command\Command->run() at phar:///usr/bin/composer/vendor/symfony/console/Application.php:835
Symfony\Component\Console\Application->doRunCommand() at phar:///usr/bin/composer/vendor/symfony/console/Application.php:185
Symfony\Component\Console\Application->doRun() at phar:///usr/bin/composer/src/Composer/Console/Application.php:267
Composer\Console\Application->doRun() at phar:///usr/bin/composer/vendor/symfony/console/Application.php:117
Symfony\Component\Console\Application->run() at phar:///usr/bin/composer/src/Composer/Console/Application.php:106
Composer\Console\Application->run() at phar:///usr/bin/composer/src/Composer/Command/GlobalCommand.php:101
Composer\Command\GlobalCommand->run() at phar:///usr/bin/composer/vendor/symfony/console/Application.php:835
Symfony\Component\Console\Application->doRunCommand() at phar:///usr/bin/composer/vendor/symfony/console/Application.php:185
Symfony\Component\Console\Application->doRun() at phar:///usr/bin/composer/src/Composer/Console/Application.php:267
Composer\Console\Application->doRun() at phar:///usr/bin/composer/vendor/symfony/console/Application.php:117
Symfony\Component\Console\Application->run() at phar:///usr/bin/composer/src/Composer/Console/Application.php:106
Composer\Console\Application->run() at phar:///usr/bin/composer/bin/composer:61
require() at /usr/bin/composer:24

Works fine without the --no-cache option. Then trying to install any package with the --no-cache option produces the same error which kind of makes sense as prestissimo relies on a cache directory. I guess a more friendly behavior is to fall back to normal composer if cache is disabled. But it's not a biggie.
The question is whether the cache directory is a hard requirement for installing prestissimo for the first time?

I'm having the same issue after upgrading to composer 1.9.0.

Dependency resolution completed in 0.001 seconds

  [ErrorException]
  mkdir(): Not a directory

Exception trace:
 () at /tmp/vendor/hirak/prestissimo/src/CopyRequest.php:103
 Composer\Util\ErrorHandler::handle() at n/a:n/a
 mkdir() at /tmp/vendor/hirak/prestissimo/src/CopyRequest.php:103
 Hirak\Prestissimo\CopyRequest->createDir() at /tmp/vendor/hirak/prestissimo/src/CopyRequest.php:89
 Hirak\Prestissimo\CopyRequest->setDestination() at /tmp/vendor/hirak/prestissimo/src/CopyRequest.php:39
 Hirak\Prestissimo\CopyRequest->__construct() at /tmp/vendor/hirak/prestissimo/src/Prefetcher.php:83
 Hirak\Prestissimo\Prefetcher->fetchAllFromOperations() at /tmp/vendor/hirak/prestissimo/src/Plugin.php:168
 Hirak\Prestissimo\Plugin->onPostDependenciesSolving() at n/a:n/a
 call_user_func() at phar:///usr/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php:176
 Composer\EventDispatcher\EventDispatcher->doDispatch() at phar:///usr/bin/composer/src/Composer/EventDispatcher/EventDispatcher.php:135
 Composer\EventDispatcher\EventDispatcher->dispatchInstallerEvent() at phar:///usr/bin/composer/src/Composer/Installer.php:491
 Composer\Installer->doInstall() at phar:///usr/bin/composer/src/Composer/Installer.php:229
 Composer\Installer->run() at phar:///usr/bin/composer/src/Composer/Command/InstallCommand.php:122
 Composer\Command\InstallCommand->execute() at phar:///usr/bin/composer/vendor/symfony/console/Command/Command.php:245
 Symfony\Component\Console\Command\Command->run() at phar:///usr/bin/composer/vendor/symfony/console/Application.php:835
 Symfony\Component\Console\Application->doRunCommand() at phar:///usr/bin/composer/vendor/symfony/console/Application.php:185
 Symfony\Component\Console\Application->doRun() at phar:///usr/bin/composer/src/Composer/Console/Application.php:267
 Composer\Console\Application->doRun() at phar:///usr/bin/composer/vendor/symfony/console/Application.php:117
 Symfony\Component\Console\Application->run() at phar:///usr/bin/composer/src/Composer/Console/Application.php:106
 Composer\Console\Application->run() at phar:///usr/bin/composer/bin/composer:61
 require() at /usr/bin/composer:24

It's somehow a standard behavior due to composer documentation "Disables the use of the cache directory. Same as setting the COMPOSER_CACHE_DIR env var to /dev/null", prestissimo relies on composer cache dir even when it's run with no cache, and I debugged it via composer github source code, and it failed at prestissimo class in root CopyRequest.php method createDir, line 103
 private function createDir($fileName)
    {
        $targetdir = dirname($fileName);
        if (!file_exists($targetdir)) {
            if (!mkdir($targetdir, 0775, true)) {
                throw new FetchException(
                    'The file could not be written to ' . $fileName
                );
            }
        }
    }

target dir is in case of supplying --no-cache param set to '/dev/null/something/long/path'

sometimes even dependencies have bugs, and if you then force using always the same, then you have a sort of problem if those with the same version number

@FantomX1 so installing other packages even without Prestissimo installed can also fail with --no-cache for similar reasons? I guess it's better to just clear cache afterwards then? Or was this about bugs due to prior cached packages?
Any reason to want to prefer --no-cache at least for Dockerfiles where it really shouldn't make much of a difference/hassle?

@polarathene , I wanted to know, if the bug was not only in cache, as on cacheless docker Continuous Integration reverting dependencies to older composer.lock did help, but it did not help at my composer caching local docker. It my sound like, if revert composer.lock did not help, erasing cache would not help either as it would have save version number,  but I believe lot of developers dont increase version number with each git commit, so the very same versions might behave differently at different times. Actually erasing cache did help me. I don't think also other dependencies must have this issue, firstly I just think majority of dependencies don't utilize cache, this is not necesarilly prestissimo's bug, but a bug in contract which composer introduced in new version, perhaps didn;t realize some dependency might utilize internal composer cache core.

The question is this: can we decide on one solution, and I would be happy to fix it.
@hirak what do you think about it?

The same problem!

One option here is when checking --no-cache instead of not using cache (as this is the core solution of prestissimo). Create a temporary folder instead to be used as cache.
For what it seems, Prestissimo downloads in parallel all packages and then lets composer install them from cache.
Not sure if feasible as it would need to overwrite the --no-cache flag to use a tmp folder and use cache again, but would be a nice solution instead of disabling this package.

Same having this issue

Subscribing.

Alright, so the fix here https://github.com/hirak/prestissimo/pull/214/files works as expected. I applied manually and worked. Though it may be better that PR gets other review then merged. Since this is a blocker

A workaround is also using a command 'composer clear-cache' however it might be not very desired, as it affects the global state, not just the currently running command.

Hi,
Any progress on this issue?
Have a nice day.


Update FAQ: Min system requirements

EN follows .... stand by

This is all about iOS, I thought again about it and maybe it would be better placed in this FAQ entry: https://www.coronawarn.app/de/faq/#ios135?

EN
UPDATE 8 February 2021
As of February 5, 2021, only the Corona-Warn-App (CWA) versions 1.5 and later are supported. For this reason, users with older versions will receive a notification to update their app accordingly. This applies to both iOS and Android. At the same time, however, certain minimum requirements apply to the operating system: Android at least 6.0 and iOS at least 13.7.
iOS users who have previously used iOS 13.5, for example, must now update the operating system to at least iOS 13.7 in order to continue using the CWA. Only then the technically correct function of the app be ensured.
Please update your iOS version first. Older smartphones, such as the iPhone SE, 6S or 6S Plus, also support the latest iOS operating system. This allows you to upgrade your iPhone to at least iOS 13.7. For security reasons, however, you should keep your iPhone up-to-date, as Apple also regularly fixes minor security vulnerabilities with the updates. You can do this on your iPhone under Settings - General - Software Update.
Subsequently, please update the Corona-Warn-App. The Corona-Warn-App must also be installed at least in version 1.5. Version 1.11 is already available.
Starting with CWA version 1.12, the older iPhone models iPhone 5s, iPhone 6, iPhone 6 Plus are also supported. These devices must be upgraded to iOS version 12.5 or 12.5.1.
The following table is for an overview:

@Ein-Tim hm, would aso be a place where to publish it, however it also mentions "Android". Maybe a link in https://www.coronawarn.app/de/faq/#ios135 to this article about minimum requirements in general.

@dsarkar
Yes, please include a link in https://www.coronawarn.app/de/faq/#ios135 👍

EN

DE

@MikeMcC399 Many many thanks!

@dsarkar
I just skimmed through the changed articles and they now look good. 👍
The only open point is about the forced update on Android (currently forced update to 1.0.4, not 1.5).
Of course it is quite possible to have a support policy which says the minimum supported level is 1.5 for Android (and iOS) and that this policy is not strictly enforced through a forced update. It just means that if a user reports a problem with a version less than 1.5 then the response will be to please update first, then come back if the problem still occurs.

@MikeMcC399
Thanks again for the incredible thorough proofreading.

The only open point is about the forced update on Android (currently forced update to 1.0.4, not 1.5).

Yes, we are waiting for some feedback. My understanding is that in any case, in the very near future it will be min req. 1.5.1 for Android and 1.5.3 for iOS.

@dsarkar

Thanks again for the incredible thorough proofreading.

You are very welcome! 🙂 Thank you also for incorporating the changes I suggested!

The only open point is about the forced update on Android (currently forced update to 1.0.4, not 1.5).

Yes, we are waiting for some feedback. My understanding is that in any case, in the very near future it will be min req. 1.5.1 for Android and 1.5.3 for iOS.

That would make a lot of sense.

Unfortunately the tables do not render well on a mobile device and this information probably needs to be displayed in a different way.
You can see what it looks like on a mobile device if you reduce the browser on a desktop / laptop to its minimum width.
BTW: This also affects the table https://www.coronawarn.app/en/faq/#interoperability_countries

@dsarkar
To optimize the display on the browser of a mobile device the table needs to be transformed into plain text. The table is just too wide for a mobile device. Do you agree? Do you want me to propose some text for this?
Also I assume that this PR will not be merged until after 1.12 is released. Is the release still planned for tomorrow Feb 10, 2021?

@MikeMcC399

To optimize the display on the browser of a mobile device the table needs to be transformed into plain text. The table is just too wide for a mobile device. Do you agree? Do you want me to propose some text for this?

Yes, I did not check, but I thought that we might run into a problem there. If you want to propose a text a will be happily integrating this into the FAQ. Thanks!

Also I assume that this PR will not be merged until after 1.12 is released. Is the release still planned for tomorrow Feb 10, 2021?

The blog post says so at least. https://www.coronawarn.app/en/blog/2021-02-04-cwa-1-12-announcement/

@MikeMcC399 Just got feedback. Min req. version CWA
iOS 1.5.3
Android 1.0.4

@MikeMcC399
here on GitHub no impact visible. However, in AppStore, there were a few complaints on iOS, and apparently via email more about Android. Based on the impact it was decided for the moment:
iOS 1.5.3
Android 1.0.4

@dsarkar
Here is a suggestion to replace the table. It is not a 1:1 replacement, however it attempts to summarize the important information. Whilst I was writing this, I thought it would be good to update and simplify en/faq/#ENF_version so I will submit an issue, then a PR for this.

en/faq/#minimum_requirements
iOS - Minimum operating system requirements
The minimum operating system level for iPhone 5s, iPhone 6 and iPhone 6 Plus devices is iOS 12.5. For all other iOS devices the minimum is iOS 13.7. These versions of the iOS operating system include the necessary v2 Apple Exposure Notification Framework.
Android - Minimum operating system requirements
The minimum operating system level for all Android devices is version 6 of Android. In addition, the device must have Google Play services installed, with a minimum version 1.5 of the Google Exposure Notification System (ENS). See en/faq/#ENF_version for instructions about how to find out which version of ENS is installed.

de/faq/#minimum_requirements
iOS - Mindestvoraussetzungen für das Betriebssystem
Für die Geräte iPhone 5s, iPhone 6 bzw. iPhone 6 Plus wird mindestens iOS Version 12.5 benötigt. Alle anderen iOS-Geräte benötigen mindestens iOS Version 13.7.
Android - Mindestvoraussetzungen für das Betriebssystem
Alle Android-Geräte benötigen mindestens Version 6 (Marshmallow) des Android-Betriebssystems. Zusätzlich muss das Gerät die Google Play-Dienste mit einer Mindestversion 1.5 des Google COVID-19-Benachrichtigungssystems installiert haben.  However, in AppStore, there were a few complaints on iOS, and apparently via email more about Android. Based on the impact it was decided for the moment:
iOS 1.5.3
Android 1.0.4

Many thanks for this information! Do we know what problems were caused by setting a higher minimum version?

@MikeMcC399 Thanks. LGTM. The table is nicer, but not appropriate for mobile devices.

Many thanks for this information! Do we know what problems were caused by setting a higher minimum version?

@MikeMcC399 Regarding Android: My understanding is that there was no real technical problem, but that some users prefer for some reason not to update to higher versions.

@MikeMcC399 Actually I just learned there was a problem (I dont know the nature of the problem), will be fixed. And then min Android req will be 1.5.1

@dsarkar
I have just submitted #865 to update the information about the Google Exposure Notifications System (ENS). This is just for completeness of the reference information. In fact these days there are no general issues about the version of ENS. If the device has an Internet connection then it will automatically get updated to the latest version of ENS because Google carries out a silent install / update of Google Play services. The last time I tried this out, after having done a factory reset on a device it took 7 seconds to get the latest version installed when connected via WiFi.
We're not seeing any major bugs in ENS any more so even if a device does not have the latest version, but only the previously released version, which is perhaps a few weeks older, there still should be no problem.
Will you go ahead with this PR now that CWA 1.12 has been announced as released (see https://www.coronawarn.app/en/blog/2021-02-10-corona-warn-app-version-1-12/)?

@MikeMcC399

Diese Versionen des iOS-Betriebssystems beinhalten auch die benötigte v2 Apple Exposure Notification Framework.

"die Framework", because of "die Arbeit" is a possibility how to derive the article, however, it seems to me that "das Framework" is more commonly used. What do you think?

remove table
"The following table provides an overview:",
"DeviceOperating SystemMinimumOperating SystemRecommendedExposure Notification SystemCWAMinimumCWAPreferrediPhone 5siPhone 6iPhone 6 PlusiOS 12.5iOS 12.5.1v2 ENF (included in iOS)Futurerelease1.12Futurerelease1.12iPhone SEiPhone 6siPhone 6s Plusand newer modelsiOS 13.7iOS 14.4v2 ENF (included in iOS)1.51.11AndroidAndroid 6latest from device vendorcurrent Google Play services1.51.11",

add @MikeMcC399 suggestions. https://github.com/corona-warn-app/cwa-website/pull/852#issuecomment-775944636

@dsarkar "das Framework" sounds better

I think I probably meant to write the following, and shortened it too much:
... auch die benötigte Version v2 des Apple Exposure Notification Frameworks.
So also change the English version to match:
... necessary v2 version of the Apple Exposure Notification Framework.

rearrange
"As of February 5, 2021, only the Corona-Warn-App (CWA) versions 1.5 and later are supported. For this reason, users with older versions will receive a notification to update their app accordingly. This applies to both iOS and Android. At the same time, however, certain minimum requirements apply to the operating system: Android at least 6.0 and iOS at least 13.7.",
"iOS users who have previously used iOS 13.5, for example, must now update the iOS operating system to at least iOS 13.7 in order to continue using the CWA. Only then can the technically correct operation of the app be ensured.",
"Please update your iOS version first. Older smartphones, such as the iPhone SE, 6S or 6S Plus, also support the latest iOS operating system. This allows you to upgrade your iPhone to at least iOS 13.7. For security reasons, however, you should keep your iPhone up-to-date, as Apple also regularly fixes minor security vulnerabilities with the updates. You can do this on your iPhone under Settings - General - Software Update.Subsequently, please update the Corona-Warn-App. The Corona-Warn-App must also be installed at least in version 1.5. Version 1.11 is already available.",
"Starting with CWA version 1.12, the older iPhone models iPhone 5s, iPhone 6 and iPhone 6 Plus are also supported. These devices must be upgraded to iOS version 12.5 or 12.5.1.",

Android is not set to min 1.5.1, so I moved the part about forced system updates to iOS

@dsarkar
write 1st generation instead of 1. generation for English text
https://en.wikipedia.org/wiki/IPhone_SE_(1st_generation)
This is a complex subject for iOS and the explanation is very readable and understandable.
For both iOS and Android the text looks good!

@Ein-Tim @MikeMcC399 thanks for the feedback and all the input.
I am having second thoughts now.
It might look just cleaner the following way:

in the minimum_required article only @MikeMcC399 's text: https://github.com/corona-warn-app/cwa-website/pull/852#issuecomment-775944636
and then as suggested earlier by @Ein-Tim move this part to the ios135 article:

@dsarkar
Your idea to simplify and split sounds good.
I edited the changes I proposed into https://github.com/corona-warn-app/cwa-website/pull/852#issuecomment-775944636 to make it easier.
(When you finally merge this PR, could you please use squash and merge if possible, to keep the commits in the master branch to a minimum? I easily get lost in git! 😉 So that would help. See
https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request.)

move this to ios135
"As of February 5, 2021, only the Corona-Warn-App (CWA) versions 1.5.3 and later are supported. For this reason, users with older versions will receive a notification to update their app accordingly. iOS users who have previously used iOS 13.5 and CWA version 1.3, for example, must now update the iOS operating system to at least iOS 13.7 in order to continue using the CWA. Only then can the technically correct operation of the app be ensured.",
"Please update your iOS version first. Older smartphones, such as the iPhone SE, 6S or 6S Plus, also support the latest iOS operating system. This allows you to upgrade your iPhone to at least iOS 13.7. For security reasons, however, you should keep your iPhone up-to-date (currently iOS 14.4), as Apple also regularly fixes minor security vulnerabilities with the updates. You can do this on your iPhone under Settings - General - Software Update.Subsequently, please update the Corona-Warn-App. The Corona-Warn-App must also be installed at least in version 1.5.3. The version 1.12.1 is already available.",

@dsarkar
It would be good to get something published today to update
https://www.coronawarn.app/en/faq/#minimum_requirements
https://www.coronawarn.app/de/faq/#minimum_requirements
I just got a push notification from the Bundesregierung App "Corona-Warn-App nun auch für ältere Smartphones"
https://www.bundesregierung.de/breg-de/such/update-cwa-1852448.

EN

removed:
                        "
Seit dem 5.  Aus diesem Grund erhalten Nutzer mit älteren Versionen einen Hinweis, ihre App entsprechend zu aktualisieren. Dies gilt sowohl für iOS als auch Android.  Nur in diesem Fall kann eine technisch korrekte Funktion der App sichergestellt werden.",
                        "

Bitte führen Sie zunächst ein Update Ihrer iOS-Version durch. Auch ältere Smartphones, wie bspw. das iPhone SE, 6S oder 6S Plus unterstützen das neueste iOS Betriebssystem. Sie können Ihr iPhone somit mindestens auf iOS 13.7 aktualisieren. Aus Sicherheitsgründen sollten Sie Ihr iPhone immer aktuell halten, da Apple auch regelmäßig kleinere Sicherheitslücken mit den Updates behebt. Sie können dies auf Ihrem iPhone unter Einstellungen – Allgemein – Softwareupdate durchführen.

Im Anschluss aktualisieren Sie bitte die Corona-Warn-App. Die Corona-Warn-App muss zudem mindestens in der Version 1.5 installiert sein. Inzwischen ist bereits Version 1.11 verfügbar. Wir bitten Sie daher, Ihre Corona-Warn-App zu aktualisieren.

",
                        "Ab der CWA Version 1.12 werden zusätzlich auch die ältere iPhone Modelle iPhone 5s, iPhone 6, bzw. iPhone 6 Plus unterstützt. Diese Geräte müssen auf die iOS Version 12.5 bzw. 12.5.1 aktualisiert werden.",
                        "Die folgende Tabelle dient zur Übersicht:",
                        "

Gerät	Betriebssytem
Minimum	Betriebssytem
Empfohlen	Exposure Notification System	CWA
Minimum	CWA
Empfohlen

iPhone 5s
iPhone 6
iPhone 6 Plus	iOS 12.5	iOS 12.5.1	v2 ENF (inbegriffen in iOS)	Zukünftige
Version
1.12	Zukünftige
Version
1.12

iPhone SE
iPhone 6s
iPhone 6s Plus
und neuere Modelle	iOS 13.7	iOS 14.4	v2 ENF (inbegriffen in iOS)	1.5	1.11

Android	Android 6	neueste Version vom Gerätehersteller	aktuelle Google Play services	1.5	1.11

",

DE

Okay, to late, but this was just a small thing, I think it's okay 👍
Thanks!

@Ein-Tim So sorry. Merges already.

maybe the more precise wording would be API 2. Need to look into it.

@dsarkar
No problem at all! You are doing so great work here, and really a huge thanks for including the community like this! ❤

@dsarkar
https://www.coronawarn.app/en/faq/#minimum_requirements
https://www.coronawarn.app/de/faq/#minimum_requirements
[Apple/iOS]: Why is iOS 13.7 a minimum requirement?
links to #no_risk_update
That doesn't look right.
The blog links are absolute, where they would be better as relative, but that is not so important.

@MikeMcC399

The blog links are absolute, where they would be better as relative, but that is not so important.

Thanks for the hint. Fixed.

@dsarkar

The blog links are absolute, where they would be better as relative, but that is not so important.

Thanks for the hint. Fixed.

Very good! It is noticeable if you test using npm because all the links should be going to the localhost copy not to the production website.


Customizing tooltips?

Is there a way to customize the information that appears when someone hovers over an annotation within any of the tracks? It looks like the example on the github page displays additional information (e.g. the source, the secondary structure type, etc.), and see there are a lot of optional attributes that can be included inRcsbFvTrackDataElementInterface, but don't know how to actually include it and get it to appear. I've looked through the CodePens, and none of them seem to have examples of how to do this.

Hi @duyentnguyen! Sorry about my late response. Currently, it is not possible to customize from the outside. I need to refactor the popups method with a better design. The file https://github.com/rcsb/rcsb-saguaro/blob/master/src/RcsbBoard/RcsbTooltip/RcsbTooltipManager.ts contains the logic of how popups are generated from a RcsbFvTrackDataElementInterface. The popups can be configured for individual elements using these fields
{                 name: "Name",                 provenanceName: "ProvenanceName",                 provenanceColor: "green",                 begin: 50,                 end: 80,                 source: "Source",                 sourceId: "SourceId",                 oriBegin: 70,                 oriEnd: 100 }
Please, let me know if you have any question.

Thanks so much for your response! For my use case, I think it's enough (for now) that I'm able to add extra information using the fields you listed above. Thank you for providing this as a resource!! Will close the issue out, too.


feat: add errorformatter

Closes #
✅ Checklist

[ ] I have followed every step in the contributing guide (updated 2022-10-06).
[ ] The PR title follows the convention we established conventional-commit
[ ] I performed a functional test on my final commit

Changelog
[Short description of what has changed]

Screenshots
[Screenshots]
💯

Love it, we should add docs for this too before merging

Good shout! What do you think would be the best docs for this?

Inferring errors
By default, tRPC sets up an error formatter that let's you infer your Zod Errors if you get validation errors on the backend.
Example usage:
function MyComponent() {
  const mutation = api.post.create.useMutation();

  return (
    <form>
      <input name="title" />
      {mutation.error?.data?.zodError?.fieldErrors.title && (

          {mutation.error.data.zodError.fieldErrors.title}

      )}
    </form>
  );
}

Or do you have a better idea?

Looks good to me

Love it, we should add docs for this too before merging

Good shout! What do you think would be the best docs for this?
Inferring errors
By default, tRPC sets up an error formatter that let's you infer your Zod Errors if you get validation errors on the backend.
Example usage:
function MyComponent() {
  const mutation = api.post.create.useMutation();

  return (
    <form>
      <input name="title" />
      {mutation.error?.data?.zodError?.fieldErrors.title ? (

          {mutation.error.data.zodError.fieldErrors.title}

      ) : null}

      ...
    </form>
  );
}

Or do you have a better idea?

docs text should be "lets" instead of "let's"
everything else looks really good.
realized while reading this pr that maybe some of the text in trpc.ts could be made a bit easier to understand overall, but thats for another pr

I think we can merge this now

Has anyone run into the scenario where you are updating a resource and so need a data payload but also an id to actually find the resource update:
so the function would look something like this:
update: protectedProcedure.input(z.object({ id: z.string(), data: customSchemaForResource })).mutation(..

now when using the errorFormatter/flatten thing from zod, any errors within the data schema validator get flattened into a "data" key, and so on the frontend you dont know which field caused the error.
What are peoples practices for handling this?

Has anyone run into the scenario where you are updating a resource and so need a data payload but also an id to actually find the resource update, the function would look something like this:
update: protectedProcedure.input(z.object({ id: z.string(), data: customSchemaForResource })).mutation(..

now when using the errorFormatter/flatten thing from zod, any errors within the data schema validator get flattened into a "data" key, and so on the frontend you dont know which field caused the error.
What are peoples practices for handling this?

What do you mean? The current formatter would return this if you send a number instead of a string to the default query on a fresh app:
{
  "formErrors": [],
  "fieldErrors": {
    "text": [
      "Expected string, received number"
    ]
  }
}

so you have your fieldErrors with the fields that failed

Just curious wow would you structure your trpc input when updating a "todo", for example? as you'll need an ID of some sort and then the actual data to update, do you just put the ID alongside all the fields that are being updated?

Yea probably, i had some procedure recently which posted a review on a product which was something like
create: protectedProcedure
  .input(z.object({
    productId: z.string(),
    text: z.string().min(10),
    rating: z.number().min(0).max(5),
  })
  .mutation(...)

Ah I see...
Something like this:
export const exampleRouter = createTRPCRouter({
  hello: publicProcedure
    .input(
      z.object({
        id: z.string(),
        data: z.object({
          text: z.string().min(3),
        }),
      })
    )
    .query(({ input }) => {
      return {
        greeting: `Hello ${input.data.text}`,
      };
    }),
});

would return an error like this if some field within the data object is invalid:
{
  "formErrors": [],
  "fieldErrors": {
    "data": [
      "String must contain at least 3 character(s)"
    ]
  }
}

Hmm... not sure if you can write a better error formatter to handle that form of input structure

Yeah exactly, I edited my previous comment showing a workaround ill go for as I really dont wana write my own formatter :P

The .format() (instead of .flatten()) method on zodErrors give you something like this:
{
  "_errors": [],
  "id": {
    "_errors": [
      "Expected string, received number"
    ]
  },
  "data": {
    "_errors": [],
    "text": {
      "_errors": [
        "String must contain at least 3 character(s)"
      ]
    }
  }
}

which you could probably work with to make it work for your usecase


[Minespoiler] Issue: Mineweeper tweaks don't work in split messages

When a game is too big to send it in one message it is splitted in multiple messages. But the tweaks (right clicking to flag as bomb, revealing all fields next to revealed zeros) only work in the first of those messages.

Remove line 314

I already answered you on discord but to make it clear to everyone who reads this:
It is not that simple. It adds some more functionality but I do not really want to do things halfway. That is why I am not doing that. You can edit the plugin for yourself and remove the lines but I won't publish that as a fix.

Closing because the plugin is abandoned


[Models][UX]: Design Icon for ArgoCD Component - Application Set

Description
Meshery is a powerful platform that contains over 200 integrations for managing cloud-native applications. MeshMap is an extension of Meshery that visually represents these integrations and components. Currently, most of the icons used in MeshMap have the default shape of a circle. However, to improve visual clarity and consistency, we need to design custom icons for MeshMap components.
Desired Behavior
A new Icon for  Application Set needs to be created. This issue calls for a volunteer to draft a new Icon.
Instructions for Designing a Component Icon

Create two versions of the icon one is white and another one is colored
Provide the icon in SVG format
Make a PR after adding the icon inside the new-icon folder present in the meshery repository
Make sure the icon for the component is different from the Model icon

How to check whether the icon you designed is the same as the Model icon or any other component icon?

Go to the playground -> search for the component you are trying to design an icon for and check whether the icon that you are designing is already present for another component or not if not then you can make a PR.
If you don't have access to Playground then you have to fill out a signup and get verified before you access the Playground by the time you get access, you can go to integrations page in layer5.io site and search for the component and see whether an icon is already present or not.

Contributor Guides and Handbook

MeshModel Repository
🖥 MeshModel Overview
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

@ritiksaxena124 , can you please assign this issue to me. I would like to work on this

@Rex739 @vishalvivekm
Kindly provide fb for this:


add hydrateDefaultViewState RPC method

Adds experimental rpc method, as part of default view creation refactoring.

Also adds a method to iModelDb to query for all spatially located models of an iModel, moving the logic from the custom view state creator file over.

This is one half of the refactoring for default view creation.

This is one half of the refactoring for default view creation.

Please elaborate what the other half is

This is one half of the refactoring for default view creation.

Please elaborate what the other half is

I'll be updating the createDefaultView() in ViewCreator3d to use the new rpc method, and may add a method to SpatialViewState to support that

"experimental rpc method" suggests you may want to remove it based on the outcome of the experiment, but that's not really an option with rpc interfaces used by apps.
Is there a github issue describing the proposed refactoring/experiment and motivations thereof?

"experimental rpc method" suggests you may want to remove it based on the outcome of the experiment, but that's not really an option with rpc interfaces used by apps.
Is there a github issue describing the proposed refactoring/experiment and motivations thereof?

Yes... I've just linked an opened issue from our private backlog

Me, @nick4598 and @wgoehrig dove into the root of the problem and figured out the reason the serialization is inconsistent is because of the possibility that URI encoding may not happen.
From the backend side, we don't know for sure if a fetch() (or other HTTP clients) will URI encode the query parameters of a URL before the request is sent.
On the frontend side, some web browsers will automatically URI encode requests for you, but that's not guaranteed either. And we don't know how previous browser versions behavior work then.
All of this comes down to inconsistency, when making a request. Our RPC system verifies if a request is base64 encoded , but if the request is URI encoded on top of that, it will fail. However, it never will, because of the URLSearchParams.get()  in the line above - which will automatically decode values for you. This example below shows the functionality available in web browsers:
let url = new URL("https://example.com?foo=1&bar=2");
let params = new URLSearchParams(url.search);

// Add a third parameter.
params.set("baz", "=="); // auto encoded
params.toString(); // "foo=1&bar=2&baz=%3D%3D"
params.get("baz"); // Outputs "==" - auto decoded

So in other words, our RPC system implicitly handles URI encoding/decoding, but it is not easy to determine that - the official MDN documentation doesn't mention anything about it either. Perhaps it would be better for an RPC rewrite to explicitly handle that?
My solution to the root problem is to have my backend service URI encode my parameter to ensure consistency, and I can close this PR, knowing the changes in this PR are not needed to do what I need to.


Use multiple dotnet test runs

Running dotnet test on the full iqsharp.sln results in memory allocations accumulating to more than 6 GB, which can occasionally cause the CI build agents to run out of memory.
I haven't yet found an obvious way to release the memory being allocated by each test after it finishes. My suspicion is that each test is reloading all required assemblies (such as those from Microsoft.Quantum.Standard, etc.) and the memory from the previous load of many of those assemblies is not being freed.
To prevent build failures in the meantime, this change simply breaks the test run into several separate invocations of dotnet test. With this change, the maximum memory usage is only around 3 GB (which occurs during the IQSharpEngine tests).

Not sure if this might work, but looking at your hypothesis of the cause, I was wondering if running a dotnet build and then passing --no-build to dotnet test might help? Or is the logger output being accumulated part of the reason (I doubt that, but throwing it out there)?

Not sure if this might work, but looking at your hypothesis of the cause, I was wondering if running a dotnet build and then passing --no-build to dotnet test might help? Or is the logger output being accumulated part of the reason (I doubt that, but throwing it out there)?

The invocation of dotnet test is already using --no-build here. It really seems to be a problem with the code itself. Each test constructs a new copy of the various IQ# components and loads any required packages into memory. When the next test starts, much that memory apparently is not released. Each test causes the process to allocate more and more memory, and it's not until the dotnet test run is complete that the process is terminated and all of the memory is released.

Not sure if this might work, but looking at your hypothesis of the cause, I was wondering if running a dotnet build and then passing --no-build to dotnet test might help? Or is the logger output being accumulated part of the reason (I doubt that, but throwing it out there)?

The invocation of dotnet test is already using --no-build here. It really seems to be a problem with the code itself. Each test constructs a new copy of the various IQ# components and loads any required packages into memory. When the next test starts, much of that memory apparently is not released. Each test causes the process to allocate more and more memory, and it's not until the dotnet test run is complete that the process is terminated and all of the memory is released.

Yea, in that case, I'm not too sure if there's a flag or option to force memory to be released between tests. Your solution looks like the most straightforward way to tackle this problem. 👍
Is there a way that you're choosing which classes to pass in as arguments vs those to be run together (at the end)? I'm guessing those 3 classes are the biggest ones?
To @anpaz-msft's point, would it make sense to automate it a bit by breaking it up by namespaces instead of passing them in as arguments and automatically retrieve the list of test namespaces (i.e. Tests.IQSharp.{...})?

Is there a way that you're choosing which classes to pass in as arguments vs those to be run together (at the end)? I'm guessing those 3 classes are the biggest ones?

Yes, it's sort of arbitrary, I just chose substrings of class names that reasonably break up the tests into large chunks.

would it make sense to automate it a bit by breaking it up by namespaces instead of passing them in as arguments and automatically retrieve the list of test namespaces (i.e. Tests.IQSharp.{...})?

That would be a more robust way of doing it, yes. But I mean, ideally we wouldn't do any of this at all... the tests should all be able to run sequentially in one process, and the fact that the memory doesn't get released properly is likely a real bug in IQ# that should be fixed. In that sense this is just a hacky workaround that should be removed when #224 is fixed, so I wouldn't want to invest too much time into this.


GH-2829 Optimized observations in Changeset

GitHub issue resolved: #2829
Briefly describe the changes proposed in this PR:

new POJO class for keeping observations
conversion to old StatementPattern for legacy code

PR Author Checklist (see the contributor guidelines for more details):

[x] my pull request is self-contained
[ ] I've added tests for the changes I made
[x] I've applied code formatting (you can use mvn process-resources to format from the command line)
[ ] I've squashed my commits down to one or a few meaningful commits
[x] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change
[x] every commit has been signed off

The changeset could actually use a more optimized datastructure for storing observations.
Since we allow observations with nulls, we know that "null, rdf:type, null" overlaps with "ex:pete, rdf:type, foaf:Person, ex:graph1". Don't really know what this datastructure would would be.

We use less memory.

Less memory usage also means less GC. So technically it's also faster.

Was also debating making the observations set synchronized. With the ShaclSail we do do parallel reads from a single connection.


output being logged to two different files?

Here's my grunt-forever config:
forever: {
        main: {
                options: {
                        index: "index.js",
                        logDir: ".",
                        logFile: "output.txt",
                        errFile: "error.txt"
                }
        }
}

The "output.txt" file is being written, but also the default "out.log" file is being written. Why both? How do I stop the default file from being created and written to?

Hello @getify,
forever has 3 different log files (described in the CLI options https://github.com/foreverjs/forever/blob/master/README.md): OUTFILE, LOGFILE, and ERRFILE.
The "out.log" file you see being generated is the OUTFILE, while the "output.txt" file specified is the LOGFILE.
I believe the additional log file was a recent change to forever, and this PR for grunt-forever added support for the additional file: https://github.com/bustardcelly/grunt-forever/commit/2e03bcf253760fae39e1416921c8fb9ed77a9ec6
if you specify an outFile option in your grunt-forever task config, it should dump to whatever specified file and the "out.log" will not be generated.

I believe the additional log file was a recent change to forever, and this PR for grunt-forever added support for the additional file: 2e03bcf

I would suggest that this new outFile option should be added to this grunt-forever's README. ;-)

Also, your current documentation says:

logFile string
File stdout is logged into, defaults to 'out.log'.

Seems like that is inaccurate compared to your code. logFile is "log.log", outFile is "out.log".

And, is there no option for me to tell grunt-forever to not set one or more of these options? If I use forever itself, and I don't put one of those options in, I believe its default behavior is to not set them. So it's strange that grunt-forever forces me to specify all 3.
I think most would assume, like me, that omitting one from my grunt-forever config should be the same thing as not having it passed to forever at all.

issues added. thank you for the suggestions :)
https://github.com/bustardcelly/grunt-forever/issues/33
https://github.com/bustardcelly/grunt-forever/issues/34

Thanks! :)


fix sendfile usage in uv_fs_copyfile

sendfile doesn't necessarily copy all data from source to destination. It's possible that the process receives a signal or similar things happen during the copying. In this case sendfile will return less than statsbuf.st_size, but not -1. And at least on linux it will also copy at most  0x7ffff000 bytes at each call.
Quote from man 2 sendfile:

If  the transfer was successful, the number of bytes written to out_fd is returned.  Note that a successful call to sendfile() may write fewer bytes than requested; the caller should be prepared to retry the call if there were unsent bytes.

Things I didn't touch, because they are unrelated to the problem, but still looks dubious to me:

All calls to uv_fs_req_cleanup are unnecessary.
Passing req->loop as first parameter is misleading. req->loop shouldn't be touch inside a work thread, passing NULL instead of req->loop would be less confusing.

cc @cjihrig - the req->loop usage indeed looks wrong.

CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/413/
Seemed mostly good.

@santigimeno do you want to land this as is? If you think we need to handle things differently on linux, you could submit a follow up PR.

Word on the street is that this fixes #1517.

All green CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/436/ 💚

Landed in https://github.com/libuv/libuv/commit/dff7ebe4f0bac1fdbcd6dec9eec72882597c78ca. Thanks!

Sorry for the late response.
I think adding a test in test-fs-copyfile.c copying a large file would be nice. If the test takes too long the TEST_ENTRY_CUSTOM macro with a expanded timeout could be used.

Oh, I see you already landed. I'll try to submit a PR with the test.

Sorry @santigimeno... we just missed each other on this one :-)
FWIW, there is a test for a larger file already, but it's not huge because of timeout issues. If you want to handle that, that would great.


Learning Apps: MNIST Fashion

I added a section to learning_apps for the new MNIST dataset.

Nice!


How to make the text under the health bar invisible?

Describe your problem here.
I am trying to make the score text invisible but it does not work
I used setProperty('scoreTxt.visible',false)and setvar('scoreTxt.visible',false)
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No, i didnt

Are you running the code under onCreate, if so change it to onCreatePost
setvar isn't a function

Are you running the code under onCreate, if so change it to onCreatePost

setvar isn't a function

i am running on onCreate

So change it

So change it

Ok, thanks for the help


PERMISSIONS.ANDROID.ACCESS_BACKGROUND_LOCATION not triggering a prompt

Bug report

Summary
PERMISSIONS.ANDROID.ACCESS_BACKGROUND_LOCATION not triggering a prompt

Environment info

react-native info output:
(node:8124) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
System:
    OS: macOS 11.2.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 329.77 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 14.15.5 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.14.11 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    Android SDK:
      API Levels: 29, 30
      Build Tools: 29.0.2, 30.0.3
      System Images: android-30 | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.1 AI-201.87<IP_ADDRESS>42882
    Xcode: 12.4/12D4e - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_282 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: ^0.63.4 => 0.63.4
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Library version: 3.0.0
Steps to reproduce

fresh install app or reset all permissions to "ask"
request for background permission

Describe what you expected to happen:
to get a prompt
Reproducible sample code
const requestBackgroundLocationPermissions = () => {
  const permissionsKey = Platform.OS === 'ios' ? PERMISSIONS.IOS.LOCATION_ALWAYS : PERMISSIONS.ANDROID.ACCESS_BACKGROUND_LOCATION;
  Permissions.request(permissionsKey).then((response: PermissionStatus) => {
    console.log('response', response) // denied

  })
  .catch((err: any) => console.log(err));
};

https://developer.android.com/reference/android/Manifest.permission#ACCESS_BACKGROUND_LOCATION
You have to request ACCESS_COARSE_LOCATION or ACCESS_FINE_LOCATION too.
try this:
const permissionsKeys =
  Platform.OS === 'ios'
    ? [PERMISSIONS.IOS.LOCATION_ALWAYS]
    : [PERMISSIONS.ANDROID.ACCESS_BACKGROUND_LOCATION, PERMISSIONS.ANDROID.ACCESS_FINE_LOCATION]; // or ACCESS_COARSE_LOCATION
Permissions.requestMultiple(permissionsKeys).then((response: PermissionStatus) => {
  console.log('response', response)

})

@naru200 is right. It's weird, but it's the official API 🤷🏻♂

@naru200 is this really working for you to open prompt for PERMISSIONS.ANDROID.ACCESS_BACKGROUND_LOCATION?
When tired to request for both ACCESS_BACKGROUND_LOCATION and ACCESS_FINE_LOCATION nothing is happening.

@zoontek Is this issue resolved, I request both PERMISSIONS.ANDROID.ACCESS_BACKGROUND_LOCATION and PERMISSIONS.ANDROID.ACCESS_FINE_LOCATION, but still nothing show on Android 11.
Is anything I missed :( ?


PyPI packaging

Configure for easy installation through pypi.
This requires:

[x] MANIFEST.in
[x] Changes to setup.py

After some evaluation, it was determined that ReQUIAM_csv does not need to be pip installable since much of it is part of development and requires a cloned copy of the repository. This issue and the related PR (#52) will be marked as won't fix and closed


Fleece should not include LinqBridge for a .NET 4.5 project

When installing Fleece in a .NET 4.5 project, LinqBridge should not show up as dependency. This is related to #140. //cc @mausch
The test project to reproduce is here:
https://github.com/ctaggart/Paket09x/commits/master

https://www.nuget.org/packages/ReadOnlyCollectionExtensions/

With it added as a dependency, you get warnings like this:

because it includes implementations of System.Action and System.Func

I'm just getting started with Paket and having this problem in version <IP_ADDRESS>. The problematic package for me is https://www.nuget.org/packages/Cassette/ , it's choking on the Iesi.Collections dependency even though it's a .NET 4.5 project.
I only ran paket convert-from-nuget, then fixed a couple minor issues with incorrectly named packages, then paket install, do I need to do anything else?
@ctaggart have you opened another issue about this? I can't seem to find it.

What's the concrete error?
What's your dependencies file?
On Jan 29, 2015 1:12 PM, "Mauricio Scheffer"<EMAIL_ADDRESS>wrote:

I'm just getting started with Paket and having this problem in version
<IP_ADDRESS>. The problematic package for me is
https://www.nuget.org/packages/Cassette/ , it's choking on the
Iesi.Collections dependency even though it's a .NET 4.5 project.
I only ran paket convert-from-nuget, then fixed a couple minor issues
with incorrectly named packages, then paket install, do I need to do
anything else?
@ctaggart https://github.com/ctaggart have you opened another issue
about this? I can't seem to find it.
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/307#issuecomment-72014427.

The exact error is (when running paket install):
  Can't resolve:
    - Iesi.Collections <  4.0
       - from Cassette 2.4.2
 Please try to relax some conditions.

This project has a huge list of dependencies, but the problem seems to be that NHibernate <IP_ADDRESS>00 requires Iesi.Collections (≥ 4.0 && < 5.0) and this conflicts with Cassette's requirement of Iesi.Collections (< 4.0) (which only applies to .NET 3.5 and therefore should be ignored for this particular project).
Let me know if that's enough or you want a more precise repro.
Cheers

Mhm. I reopened https://github.com/fsprojects/Paket/issues/322 - this could
help.
The exact error is (when running paket install):
Can't resolve:
- Iesi.Collections <  4.0
- from Cassette 2.4.2
Please try to relax some conditions.
This project has a huge list of dependencies, but the problem seems to be
that NHibernate <IP_ADDRESS>00
https://www.nuget.org/packages/NHibernate/<IP_ADDRESS>00 requires
Iesi.Collections (≥ 4.0 && < 5.0) and this conflicts with Cassette's
requirement of Iesi.Collections (< 4.0) (which only applies to .NET 3.5 and
therefore should be ignored for this particular project).
Let me know if that's enough or you want a more precise repro.
Cheers
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/307#issuecomment-72055504.

I now understand the issue. I'll try to come up with a solution.

as a workaround add
nuget Iesi.Collections == <IP_ADDRESS>00

to your dependencies file. This will force the version.

Thanks, that workaround did the trick. I just have to be careful with paket simplify until this is fixed, as it removes that versioning constraint from the dependencies file (or is that a separate issue?)

Yes. I'm working on a better solution. Internally we already have
everything to say: just don't care about net35. But this is not part of the
dependencies file yet
On Jan 30, 2015 3:27 PM, "Mauricio Scheffer"<EMAIL_ADDRESS>wrote:

Thanks, that workaround did the trick. I just have to be careful with paket
simplify until this is fixed, as it removes that versioning constraint
from the dependencies file (or is that a separate issue?)
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/307#issuecomment-72208679.


Update sbt-site to 1.3.3

Updates com.typesafe.sbt:sbt-site from 1.3.2 to 1.3.3.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a nice day!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [{ groupId = "com.typesafe.sbt", artifactId = "sbt-site" }]

labels: semver-patch

Codecov Report

Merging #20 into master will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff          @@
##           master   #20   +/-   ##
====================================
  Coverage      50%   50%
====================================
  Files           1     1
  Lines          68    68
  Branches        4     4
====================================
  Hits           34    34
  Misses         34    34

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dec62e4...97133b4. Read the comment docs.


Improving the way hosting works

Codecov Report

Merging #160 into master will decrease coverage by 4.53%.
The diff coverage is 57.14%.

@@            Coverage Diff             @@
##           master     #160      +/-   ##
==========================================
- Coverage    34.8%   30.26%   -4.54%
==========================================
  Files         118      114       -4
  Lines        4617     4229     -388
==========================================
- Hits         1607     1280     -327
+ Misses       3010     2949      -61


Again bug with scroll bar and modal

Hi,
I reported this bug a few years ago and it came back to happen. Open this website http://empresasite.com.br/ and click on the CONTATO link at the top right. You will see the scrollbars will not show up and the modal will be shown not centered.

Sure Here you have  it : https://jsfiddle.net/ca0rovs3/478/
I hope this is what you need 😄


Execution failed for task ':app:compileDebugJavaWithJavac'. error plz help

C:\Users\Home\Desktop\all same\flutter-unity-view-widget-master\flutter-unity-view-widget-master\example\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java:17: error: package com.rexraphael.flutterunitywidget does not exist
com.rexraphael.flutterunitywidget.FlutterUnityWidgetPlugin.registerWith(shimPluginRegistry.registrarFor("com.rexraphael.flutterunitywidget.FlutterUnityWidgetPlugin"));
^
1 error
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 3s
Finished with error: Gradle task assembleDebug failed with exit code 1
flutter run -v log:-
C:\Users\Home\Desktop\all same\flutter-unity-view-widget-master\flutter-unity-view-widget-master\example>flutter run -v
[  +29 ms] executing: [C:\Program Files\flutter] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +91 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 0b8abb4724aa590dd0f429683339b1e045a1594d
[        ] executing: [C:\Program Files\flutter] git describe --match v*.. --first-parent --long --tags
[  +76 ms] Exit code 0 from: git describe --match v*.. --first-parent --long --tags
[        ] v1.12.13+hotfix.8-0-g0b8abb472
[   +7 ms] executing: [C:\Program Files\flutter] git rev-parse --abbrev-ref --symbolic @{u}
[  +62 ms] Exit code 128 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] fatal: HEAD does not point to a branch
[  +15 ms] executing: [C:\Program Files\flutter] git rev-parse --abbrev-ref HEAD
[  +59 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] HEAD
[  +85 ms] executing: C:\Users\Home\AppData\Local\Android\Sdk\platform-tools\adb.exe devices -l
[  +35 ms] Exit code 0 from: C:\Users\Home\AppData\Local\Android\Sdk\platform-tools\adb.exe devices -l
[        ] List of devices attached
32111c8f0604           device product:tissot model:Mi_A1 device:tissot_sprout transport_id:18
[  +18 ms] C:\Users\Home\AppData\Local\Android\Sdk\platform-tools\adb.exe -s 32111c8f0604 shell getprop
[ +119 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +8 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +4 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +53 ms] Found plugin flutter_unity_widget at C:\Program Files\flutter.pub-cache\hosted\pub.dartlang.org\flutter_unity_widget-0.1.6+8
[ +174 ms] Found plugin flutter_unity_widget at C:\Program Files\flutter.pub-cache\hosted\pub.dartlang.org\flutter_unity_widget-0.1.6+8
[  +83 ms] Generating C:\Users\Home\Desktop\all
same\flutter-unity-view-widget-master\flutter-unity-view-widget-master\example\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[  +68 ms] ro.hardware = qcom
[  +46 ms] Launching lib\main.dart on Mi A1 in debug mode...
[  +17 ms] executing: C:\Users\Home\AppData\Local\Android\Sdk\platform-tools\adb.exe -s 32111c8f0604 shell -x logcat -v time -t 1
[  +80 ms] Exit code 0 from: C:\Users\Home\AppData\Local\Android\Sdk\platform-tools\adb.exe -s 32111c8f0604 shell -x logcat -v time -t 1
[        ] --------- beginning of main
07-20 16:16:49.072 W/Settings( 6940): Setting preferred_network_mode has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
[   +6 ms] executing: C:\Users\Home\AppData\Local\Android\Sdk\platform-tools\adb.exe version
[   +2 ms] executing: C:\Users\Home\AppData\Local\Android\Sdk\platform-tools\adb.exe -s 32111c8f0604 logcat -v time -T 07-20 16:16:49.072
[  +46 ms] Android Debug Bridge version 1.0.41
Version 29.0.5-5949299
Installed as C:\Users\Home\AppData\Local\Android\Sdk\platform-tools\adb.exe
[   +5 ms] executing: C:\Users\Home\AppData\Local\Android\Sdk\platform-tools\adb.exe start-server
[  +39 ms] Building APK
[  +22 ms] Running Gradle task 'assembleDebug'...
[   +3 ms] gradle.properties already sets android.enableR8
[   +6 ms] Using gradle from C:\Users\Home\Desktop\all same\flutter-unity-view-widget-master\flutter-unity-view-widget-master\example\android\gradlew.bat.
[  +15 ms] executing: C:\Program Files\Android\Android Studio1\jre\bin\java -version
[ +166 ms] Exit code 0 from: C:\Program Files\Android\Android Studio1\jre\bin\java -version
[   +1 ms] openjdk version "1.8.0_242-release"
OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
OpenJDK 64-Bit Server VM (build 25.242-b01, mixed mode)
[   +3 ms] executing: C:\Program Files\Android\Android Studio1\jre\bin\java -version
[ +161 ms] Exit code 0 from: C:\Program Files\Android\Android Studio1\jre\bin\java -version
[   +1 ms] openjdk version "1.8.0_242-release"
OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
OpenJDK 64-Bit Server VM (build 25.242-b01, mixed mode)
[   +5 ms] executing: [C:\Users\Home\Desktop\all same\flutter-unity-view-widget-master\flutter-unity-view-widget-master\example\android] C:\Users\Home\Desktop\all
same\flutter-unity-view-widget-master\flutter-unity-view-widget-master\example\android\gradlew.bat -Pverbose=true -Ptarget=C:\Users\Home\Desktop\all
same\flutter-unity-view-widget-master\flutter-unity-view-widget-master\example\lib\main.dart -Ptrack-widget-creation=true -Pfilesystem-scheme=org-dartlang-root
-Ptarget-platform=android-arm64 assembleDebug
[+2822 ms] > Task :app:compileFlutterBuildDebug UP-TO-DATE
[   +1 ms] > Task :app:packLibsflutterBuildDebug UP-TO-DATE
[        ] > Task :app:preBuild UP-TO-DATE
[        ] > Task :app:preDebugBuild UP-TO-DATE
[        ] > Task :UnityExport:preBuild UP-TO-DATE
[   +1 ms] > Task :UnityExport:preDebugBuild UP-TO-DATE
[        ] > Task :UnityExport:compileDebugAidl NO-SOURCE
[        ] > Task :app:compileDebugAidl NO-SOURCE
[  +72 ms] > Task :UnityExport:packageDebugRenderscript NO-SOURCE
[   +3 ms] > Task :app:compileDebugRenderscript NO-SOURCE
[   +8 ms] > Task :app:checkDebugManifest UP-TO-DATE
[        ] > Task :app:generateDebugBuildConfig UP-TO-DATE
[  +87 ms] > Task :app:cleanMergeDebugAssets
[   +2 ms] > Task :app:mergeDebugShaders UP-TO-DATE
[   +6 ms] > Task :app:compileDebugShaders UP-TO-DATE
[        ] > Task :app:generateDebugAssets UP-TO-DATE
[   +1 ms] > Task :UnityExport:mergeDebugShaders UP-TO-DATE
[   +6 ms] > Task :UnityExport:compileDebugShaders UP-TO-DATE
[        ] > Task :UnityExport:generateDebugAssets UP-TO-DATE
[        ] > Task :UnityExport:packageDebugAssets UP-TO-DATE
[ +154 ms] > Task :app:mergeDebugAssets
[ +430 ms] > Task :app:copyFlutterAssetsDebug
[   +3 ms] > Task :app:mainApkListPersistenceDebug UP-TO-DATE
[   +1 ms] > Task :app:generateDebugResValues UP-TO-DATE
[        ] > Task :app:generateDebugResources UP-TO-DATE
[        ] > Task :UnityExport:compileDebugRenderscript NO-SOURCE
[        ] > Task :UnityExport:generateDebugResValues UP-TO-DATE
[        ] > Task :UnityExport:generateDebugResources UP-TO-DATE
[        ] > Task :UnityExport:packageDebugResources UP-TO-DATE
[        ] > Task :app:mergeDebugResources UP-TO-DATE
[        ] > Task :app:createDebugCompatibleScreenManifests UP-TO-DATE
[        ] > Task :UnityExport:checkDebugManifest UP-TO-DATE
[        ] > Task :UnityExport:processDebugManifest UP-TO-DATE
[        ] > Task :app:processDebugManifest UP-TO-DATE
[ +217 ms] > Task :UnityExport:parseDebugLibraryResources UP-TO-DATE
[ +124 ms] > Task :UnityExport:generateDebugRFile UP-TO-DATE
[   +1 ms] > Task :app:processDebugResources UP-TO-DATE
[   +1 ms] > Task :UnityExport:generateDebugBuildConfig UP-TO-DATE
[        ] > Task :UnityExport:javaPreCompileDebug UP-TO-DATE
[        ] > Task :UnityExport:compileDebugJavaWithJavac UP-TO-DATE
[   +1 ms] > Task :UnityExport:bundleLibCompileDebug UP-TO-DATE
[   +1 ms] > Task :app:compileDebugKotlin UP-TO-DATE
[        ] > Task :app:javaPreCompileDebug UP-TO-DATE
[ +135 ms] > Task :app:compileDebugJavaWithJavac FAILED
[   +4 ms] C:\Users\Home\Desktop\all
same\flutter-unity-view-widget-master\flutter-unity-view-widget-master\example\android\app\src\main\java\i
o\flutter\plugins\GeneratedPluginRegistrant.java:17: error: package
com.rexraphael.flutterunitywidget does not exist
[   +3 ms]       com.rexraphael.flutterunitywidget.FlutterUnityWidgetPlugin.registerWith(shimPluginRegistry.registrarFor("com.rexraphael.flutterunitywidget.FlutterUnityWidgetPlugin"));
[   +1 ms]                                        ^
[        ] 1 error
[        ] FAILURE: Build failed with an exception.
[   +1 ms] * What went wrong:
[        ] Execution failed for task ':app:compileDebugJavaWithJavac'.
[        ] > Compilation failed; see the compiler error output for details.
[        ] * Try:
[        ] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
[   +2 ms] * Get more help at https://help.gradle.org
[   +1 ms] BUILD FAILED in 3s
[   +1 ms] 31 actionable tasks: 4 executed, 27 up-to-date
[ +780 ms] Running Gradle task 'assembleDebug'... (completed in 5.3s)
[   +8 ms] "flutter run" took 6,270ms.
Gradle task assembleDebug failed with exit code 1
#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      buildGradleApp (package:flutter_tools/src/android/gradle.dart:387:7)

#2      _AndroidBuilderImpl.buildApk (package:flutter_tools/src/android/android_builder.dart:97:13)
#3      AndroidDevice.startApp (package:flutter_tools/src/android/android_device.dart:522:28)

#4      FlutterDevice.runHot (package:flutter_tools/src/resident_runner.dart:450:54)
#5      _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:73:64)
#6      _rootRunUnary (dart:async/zone.dart:1134:38)
#7      _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#8      _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#9      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#10     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#11     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#12     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#13     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#14     ApplicationPackageFactory.getPackageForPlatform (package:flutter_tools/src/application_package.dart)
#15     _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:73:64)
#16     _rootRunUnary (dart:async/zone.dart:1134:38)
#17     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#18     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#19     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#20     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#21     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#22     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#23     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#24     AndroidApk.fromAndroidProject (package:flutter_tools/src/application_package.dart)
#25     _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:73:64)
#26     _rootRunUnary (dart:async/zone.dart:1134:38)
#27     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#28     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#29     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#30     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#31     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#32     Future._asyncComplete. (dart:async/future_impl.dart:554:7)
#33     _rootRun (dart:async/zone.dart:1126:13)
#34     _CustomZone.run (dart:async/zone.dart:1023:19)
#35     _CustomZone.runGuarded (dart:async/zone.dart:925:7)
#36     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:965:23)
#37     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#38     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:
Gradle | Search for Help with Gradle
[Photo]
5)
#39     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#40     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:175:5)
flutter doctor log:-
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel unknown, v1.12.13+hotfix.8, on Microsoft Windows [Version 10.0.18363.900], locale en-IN)
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[√] Android Studio (version 4.0)
[!] VS Code (version 1.44.2)
X Flutter extension not installed; install from
https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[√] Connected device (1 available)

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 26s
Exception: Gradle task assembleDebug failed with exit code 1

I have the same issue, I can't figure it out. I followed the tutorial step by step multiple times with the example folder and get this error each time...

I just fix this error buy moving the unity-classes.jar (UnityExport/lib) to folder unity-classes.
I found this solution here : #162
Also : https://www.youtube.com/watch?v=exNPmv_7--Q at 3:55
Now I can run the app but it crash when I want to open WithARkitScreen() using the router like the exemple ...

please use the new build script :)


added RTF

Pull Request Template

Added the RTF reading function in utils.py
Changed README.md to add RTF extension
Added sample RTF file to assets

Issue no. - #82
Self Check(Tick After Making pull Request)

[ ] One Change in one Pull Request
[x] I am following clean code and Documentation and my code is well linted with flake8.

Join Us on Discord:- https://discord.gg/JfbK3bS

I have not updated the "CHANGELOG.md" file. Will it be done by you or shall I do it? @codeperfectplus


external_storage: update to rusoto 0.34

Signed-off-by: Yi Wu<EMAIL_ADDRESS>What have you changed?
update rusoto (aws lib) to 0.34, which provides IAM support. It changes a few API to use newer futures/tokio version. Update accordingly.
Fixes #7096
What is the type of the changes?
Improvement, Engineering
How is the PR tested?
build
Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No
Does this PR affect tidb-ansible?
No
Refer to a related PR or issue link (optional)
Benchmark result if necessary (optional)
Any examples? (optional)

/release

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

LGTM.
I've got some changes to remove the Sync requirements on the reader, but let's defer that refactoring later.

How do you remove the Sync requirement?

@yiwu-arbug by reimplementing that FramedRead, where the replacement itself holds the Mutex.

(This was written before #6675 so some restriction (e.g. reusing the buffer) can be relaxed. The try_lock() should be replaced by get_mut().)
/// Wrapper of an `AsyncRead` instance, exposed as a `Sync` `Stream` of `Bytes`.
pub struct AsyncReadAsSyncStreamOfBytes<R> {
    // we need this Mutex to ensure the type is Sync (provided R is Send).
    // this is because rocksdb::SequentialFile is *not* Sync
    // (according to the documentation it cannot be Sync either,
    // requiring "external synchronization".)
    reader: Mutex<R>,
    // we use this member to ensure every call to `poll_next()` reuse the same
    // buffer.
    buf: Vec<u8>,
}

impl<R> AsyncReadAsSyncStreamOfBytes<R> {
    pub fn with_capacity(reader: R, capacity: usize) -> Self {
        Self {
            reader: Mutex::new(reader),
            buf: vec![0; capacity],
        }
    }
}

impl<R: AsyncRead + Unpin> Stream for AsyncReadAsSyncStreamOfBytes<R> {
    type Item = io::Result<Bytes>;

    fn poll_next(self: Pin<&mut Self>, cx: &mut Context<'_>) -> Poll<Option<Self::Item>> {
        let this = self.get_mut();
        let mut reader = match this.reader.try_lock() {
            Ok(guard) => guard,
            Err(TryLockError::WouldBlock) => return Poll::Pending,
            Err(TryLockError::Poisoned(poison)) => panic!("cannot acquire lock: {}", poison),
        };

        let read_size = Pin::new(&mut *reader).poll_read(cx, &mut this.buf);
        drop(reader);

        match read_size {
            Poll::Pending => Poll::Pending,
            Poll::Ready(Err(e)) => Poll::Ready(Some(Err(e))),
            Poll::Ready(Ok(0)) => Poll::Ready(None),
            Poll::Ready(Ok(n)) => Poll::Ready(Some(Ok(Bytes::copy_from_slice(&this.buf[..n])))),
        }
    }
}

@yiwu-arbug by reimplementing that FramedRead, where the replacement itself holds the Mutex.

I thought about it but hesitate to do so. It adds maintenance cost by having more code. I think requiring Sync is good for now.