Can we set addEqualityFilter for enum with readonly

I want to  set addEqualityFilter  for enum with readonly values.Is it possible in serenity?

What does it mean enum with readOnly values??

I want to load data  by default set  value from dropdown.and in my case the dropdown I want to use is enum type.
for ex.in dropdown I have multiple options  like accepted,pending,checked etc. and I want to Load only pending results.
Can u guide me how to do this using addEqualityFilter

I think you are trying set initial value of an enum filter editor:

AddEqualityFilter<EnumEditor>(Fields.MyEnum,
                options: new EnumEditorOptions { EnumKey = "ABC" },
                init: e =>
                    {
                        e.Value = ((int)TheEnum.SomeValue).ToString()
                    });


🌐 Add German translation for docs/de/docs/reference/staticfiles.md

← reference/encoders.md (#10840)
→ reference/templating.md (#10842)
German translation progress

📝 Docs preview for commit ed44f7ffc9852aae4bce4d87f0bec63d4754f1f4 at: https://5c98b53d.fastapitiangolo.pages.dev

📝 Docs preview for commit 0a847aa464f7333932176387f767dd49c14e3590 at: https://a3cbbe3f.fastapitiangolo.pages.dev

Awesome @nilslindemann! :rocket:
As you are the champion of German translations and you have done so many, and with so much attention to detail, I'm gonna go ahead and merge this. :tada:
If others see things that could be improved later, we can check that in new PRs. :nerd_face:


Blog post on ways to use Ansible and Docker together.

My draft-in-progress of a blog post about the ways that you can use Ansible and Docker together. I still have the most important bits left to write -- insert a 90's-era Geocities "under construction" .gif here. :wrench: Early feedback would be awesome :grin:
Meta information
Mini bio:

Ash is a software developer on Rackspace's Developer Experience team. His interests include programming languages, continuous deployment, and plugging things into other things (we had to cover all the wall sockets).

Social media contact info:
Twitter: @smashwilson
GitHub: @smashwilson
Remaining Work

[x] Document using Ansible to ship Docker containers.
[x] Some kind of conclusion.
[x] Include an image of a cow somewhere (I'm pretty sure that's in the Ansible EULA somewhere)
[ ] Come up with a better title. Any ideas?
[x] Correct the post date with the actual publish date.

@catlook, @rgbkrk: I think the content here is ready for review, if either or both of you are so inclined :smile:
I'm all ears for a better title, too, and any cow and/or shipping container pictures that anyone has up their sleeves.

Maybe?

on it!!
-- Cat Lookabaugh, Information Developer
Rackspace Hosting - the #1 Managed Cloud Company
Developer Relations Group
Office:<PHONE_NUMBER>   Cell:<PHONE_NUMBER>
<EMAIL_ADDRESS>We should not write so that it is possible for the reader to understand us, but so that it is impossible for him to misunderstand us. - Quintilian, rhetorician (c. 35-100)
Harmony + Learner + Responsibility + Context + Intellection + Arranger + Consistency + Relator + Input + Analytical
From: Ash Wilson <notifications<EMAIL_ADDRESS>Reply-To: "rackerlabs/developer.rackspace.com" <reply<EMAIL_ADDRESS>Date: Friday, April 24, 2015 3:16 PM
To: "rackerlabs/developer.rackspace.com" <developer.rackspace.com<EMAIL_ADDRESS>Cc: Cat Lookabaugh <cat.lookabaugh<EMAIL_ADDRESS>Subject: Re: [developer.rackspace.com] [wip] Blog post on ways to use Ansible and Docker together. (#1130)
Maybe?
[cow-shipping]https://cloud.githubusercontent.com/assets/17565/7327694/2a95895c-ea9d-11e4-9302-cd0b4d0b38ce.jpg

Reply to this email directly or view it on GitHubhttps://github.com/rackerlabs/developer.rackspace.com/pull/1130#issuecomment-96051992.

All done.  let me know if you have any questions!
-- Cat Lookabaugh, Information Developer
Rackspace Hosting - the #1 Managed Cloud Company
Developer Relations Group
Office:<PHONE_NUMBER>   Cell:<PHONE_NUMBER>
<EMAIL_ADDRESS>We should not write so that it is possible for the reader to understand us, but so that it is impossible for him to misunderstand us. - Quintilian, rhetorician (c. 35-100)
Harmony + Learner + Responsibility + Context + Intellection + Arranger + Consistency + Relator + Input + Analytical
From: Ash Wilson <notifications<EMAIL_ADDRESS>Reply-To: "rackerlabs/developer.rackspace.com" <reply<EMAIL_ADDRESS>Date: Friday, April 24, 2015 3:09 PM
To: "rackerlabs/developer.rackspace.com" <developer.rackspace.com<EMAIL_ADDRESS>Cc: Cat Lookabaugh <cat.lookabaugh<EMAIL_ADDRESS>Subject: Re: [developer.rackspace.com] [wip] Blog post on ways to use Ansible and Docker together. (#1130)
@catlookhttps://github.com/catlook, @rgbkrkhttps://github.com/rgbkrk: I think the content here is ready for review, if either or both of you are so inclined [:smile:]
I'm all ears for a better title, too, and any cow and/or shipping container pictures that anyone has up their sleeves.

Reply to this email directly or view it on GitHubhttps://github.com/rackerlabs/developer.rackspace.com/pull/1130#issuecomment-96049895.

Oh my gosh, that cow on a boat is great. That's a perfect Ansible and Docker image.
I'm assuming you searched "container cow" too?

Wonderful to have content like this Ash. Side note: it's not unreasonable to link the PRs that brought in some of the new Docker stuff.

Thanks so much, both of you :bow: I'll work in your changes on Monday and hopefully we can :shipit: then :grin:

The only thing left to do is come up with a better title, maybe. I couldn't think of anything else so meh!
Think this is ready to ship?

We can get this into the "cdn" release today if you're down @smashwilson

The best :cow2: awards will be given to the author of this PR.


Error when ng serve

Good day ,
i just follow the instruction how to run locally but this is the result
please help.
ERROR in<EMAIL_ADDRESS>(73,13): Subsequent variable declarations must have the same type.  Variable 'require' must be of type 'any', but here has type 'NodeRequire'.
ERROR in D:/Files/myGitHub/covalent/src/universal-app/battle-royale.ts (6,53): Cannot find module './dist/aot/combat-training/combat-training.ngfactory'.
webpack: Failed to compile.
Thanks

Are you building off develop or our latest release beta.6?

This happened because of some recent commits we have, will be fixed soon.

This has been fixed now

I clone it again and its ok now. thanks alot
On Fri, Aug 11, 2017 at 8:55 AM, Ed Morales<EMAIL_ADDRESS>wrote:

Closed #806 https://github.com/Teradata/covalent/issues/806.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Teradata/covalent/issues/806#event-1201939584, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AD8Zh5MAf9rcshUUIjXVY09X4b4DMWz9ks5sW6aIgaJpZM4OzKU2
.


useOpenTelemetry does not end spans after execution

Describe the bug
The useOpenTelemetry plug-in does not end tracer spans after execution.
To Reproduce
import { createServer } from 'graphql-yoga';
import { useOpenTelemetry } from '@envelop/opentelemetry';

const server = createServer({
  typeDefs: /* GraphQL */ `
    type Query {
      greetings: String!
    }
  `,
  resolvers: {
    Query: {
      greetings: () => 'Hello World!',
    },
  },
  plugins: [useOpenTelemetry()],
});
server.start();

Expected behavior
Execution spans to be exported to the console.
Environment:

OS: Linux codespaces_8fc9e5 5.4.0-1064-azure
@envelop/opentelemetry: 2.0.0
NodeJS: v14.17.6

Additional context
I have fixed the issue (and added basic tests for verify only this behaviour) in a fork here (I can submit a draft PR).

I have created a draft PR #1193 which includes the fix.

Fixed in<EMAIL_ADDRESS>🎉

Thanks @dotansimha.


Rails 5.2.7

Upgrade all gems.
Responds to this High Severity Dependabot Alert, https://github.com/MushroomObserver/mushroom-observer/security/dependabot/8
Updates all gems -- regardless whether needed for a response to that Alert.
There is no manual test.

Coverage remained the same at 93.029% when pulling 3fc3796af4bb8b24940be2715b6ef11185318f5b on rails-5-2-7 into a1c43e9df9bd9bf675e872f71564388641d692e2 on master.


Fix typos in environment warning

On travis; we see:
You might still need to set your ENV variables inside ofconfig/app_environment_variables.rb Take a look atconfig/app_environment_variables.rb.example. Raise an issue onOpenFarms GitHub page if you still cant get it working. If youare seeing this from within your CI or production server, you canignore this message. Make sure you set your ENV vars, though.
Which reads a bit funny

Coverage remained the same at 99.347% when pulling 0c3b55d581dba6b2b2323f7eb1c2bc965771d212 on CloCkWeRX:typos into 018987d4307305e6aefece1f6d26f32a088c1365 on openfarmcc:master.


 Is the plan to give the chaplain the ability to speak with ghosts as in some versions of SS13, or is that considered overpowered?

no that isn't planned in any capacity at least not as a result of this PR

will conflict with actiontities whenever smug finishes that

speak of the devil

blease

fixed for actiontities

I feel like the action icon should change when you are/arent listening for better UX


Document how to pull data from platform.sh

We use Platform.sh in a mulitapp architecture. This means that we have several Drupal sites in one project, they are not multisites.
In order to achieve this there is a main repositories that uses git submodules to point to the actual Drupal repositories. Because of this there are a few steps that required for us that may not be required for more standard installs.
In the tugboat repository settings we need an environment variable for the platform cli it must be named PLATFORMSH_CLI_TOKEN
Instructions for generating the token: https://docs.platform.sh/development/cli/api-tokens.html
In the php service init command we install the platform.sh cli:
# Install platform cli
- curl -fsS https://platform.sh/cli/installer | php

In the php service update command we grab the database.
- /root/.platformsh/bin/platform --project=${PROJECT_ID} --environment=${BRANCH} --app=${APP} --relationship=${DATABASE} db:dump --gzip
- vendor/bin/drush sql-drop -y
- zcat ${PROJECT_ID}--${BRANCH}-${CUSTOMER_ID}--mariadb--${APP}--dump.sql.gz | mysql --host=mysql -u tugboat -ptugboat tugboat
- rm ${PROJECT_ID}--${BRANCH}-${CUSTOMER_ID}--mariadb--${APP}--dump.sql.gz

${PROJECT_ID} is the id of the project you can see it in the url when you are on the platform dashboard looking at the project.
${BRANCH} is the branch/environment you want to pull the database from usually main or master.
${APP} is the name of the app defined in .platform.app.yaml
${DATABASE} is the name of the database relationship in .platform.app.yaml
${CUSTOMER_ID} can be found in the default urls that platform provides each project.
I also assume mariadb in the string depends on the service you use for your database, but I only have mariadb on platform.
We do not need the typical mysql update command that is there by default.


Show 'Editable Children' and 'Load as Placeholder' context menu options for multi-node selections

Partially addresses godotengine/godot-proposals#581.
Makes 'Editable Children' and ‘Load as Placeholder’ options available in the scene tree dock context menu for multi-node selections.
If multiple nodes are selected, some with the setting enabled and some without, the user is asked to make them all editable/placeholders, or all not.

If the selection contains any node for which an option would not be applicable, the option will not appear in the menu.
Notes/Questions
Context menus don't support indeterminate checkboxes, so only shows a check if all selected nodes are enabled.
User can be shown enable/disable placeholders prompt, then disable editable children prompt back-to-back. Is this ok?

Don't show options if child and ancestor selected (selection size != full_selection size), to avoid potentially confusing behaviour.
move tree update out of loops. With a couple hundred nodes, operation time goes from >1 sec to immediate.

rebased.
change "Load as Placeholder" and "Editable Children" in dialogs to "use_placeholder" and "editable_instance" to match existing dialog.

I rebased and fixed merge conflict locally, but I'm not sure now if I should go back to "Load as Placeholder" and "Editable Children" in dialogs? In master there's a dialog that says
Disabling "editable_instance" will cause all properties of the node to be reverted to their default.
and another that says
Enabling "Load as Placeholder" will disable "Editable Children" and cause all properties of the node to be reverted to their default.
so it's not clear which example I should follow. (fwiw I think the presentation in the latter is better and presumably what's intended.)

Rebased, and decided on "Load as Placeholder" and "Editable Children".

Rebased.

Title case for buttons.

though not a fan of the added code complexity .-.

I agree, some of these methods can be simplified and paths for single and multi selection can be mostly unified. It should also help to reduce the number of errors. That said, I think we can still merge it as is (once fixed up), and do a clean up later. Stuff like _tool_selected should probably be split into more manageable blocks anyway (and this is true for a lot of our codebase).

'those' -> 'selected', earlier profile_allow_editing check.


Patch 8.2.1297 breaks s:function call for sourcing kana/vim-arpeggio setup

Describe the bug
Bisected to patch 8.2.1297. Seemingly throws the <SID>work function in https://github.com/kana/vim-arpeggio/raw/master/autoload/arpeggio.vim into an infinite loop.
To Reproduce
git clone https://github.com/kana/vim-arpeggio ~/.vim/pack/keyboard/opt/vim-arpeggio

cat > vimrc <<'EOF'
set nocp
function! s:source_cfg()
  source arpeggio.vim
endfunction
call s:source_cfg()
EOF

cat > arpeggio.vim <<'EOF'
packadd vim-arpeggio
Arpeggio inoremap jk <ESC>
EOF

vim -u vimrc

" enter insert mode
" leave insert mode by chording 'j' and 'k'
" vim freezes: Ctrl+C

Fix:
cat > vimrc <<'EOF'
set nocp
source arpeggio.vim
EOF

The call s:source_cfg() makes all the difference.
Expected behavior
kana/vim-arpeggio escape chord exits insert mode.
Screenshots

Environment (please complete the following information):

Vim version: 8.2.1297+
OS: macOS 10.15.6
Terminal: iTerm2

Can you dig up more information about where something goes wrong?  E.g. is the problem with the s:SID variable?

Fixed pending https://github.com/kana/vim-arpeggio/pull/31.

Can you dig up more information about where something goes wrong? E.g. is the problem with the s:SID variable?

I don't know whether it's a bug, but I can reduce the issue to this:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    let lines =<< trim END
        vim9script
        def Rhs(): string
            return s:SID .. 'j'
        enddef
        def SID(): string
            return expand('<sfile>')->matchstr('<SNR>\zs\d\+\ze_')
        enddef
        let SID = "\<SNR>" .. s:SID() .. '_'
        imap <expr> j <sid>Rhs()
        ino <sid>j j
    END
    writefile(lines, '/tmp/t.vim')
    def Source()
      so /tmp/t.vim
    enddef
    Source()
EOF
)

It doesn't require any plugin.
On 8.2.1296, if you press j in insert mode, Vim just inserts j.
On 8.2.1297, if you press j in insert mode, Vim expands the recursive mapping indefinitely; this one:
imap <expr> j <sid>Rhs()

Fixed pending kana/vim-arpeggio#31.

Even if the current issue is fixed, your code will still not work as expected, because of another bug in the arpeggio plugin:
https://github.com/kana/vim-arpeggio/blob/5d73721898d2bb669ead417b4d3370921ce7c3cf/autoload/arpeggio.vim#L267
It assumes that the first script ID in the stack of function calls is the one where s:SID() is defined; that's not necessarily true.  The last script ID is the one where s:SID is defined; not the first.
Here is a patch which should fix the bug:
diff --git a/autoload/arpeggio.vim b/autoload/arpeggio.vim
index 3e14315..68c26aa 100644
--- a/autoload/arpeggio.vim
+++ b/autoload/arpeggio.vim
@@ -264,7 +264,7 @@ endfunction

 " Misc.  "{{{1
 function! s:SID()  "{{{2
-  return matchstr(expand('<sfile>'), '<SNR>\zs\d\+\ze_')
+  return matchstr(expand('<sfile>'), '<SNR>\zs\d\+\ze_SID$')
 endfunction
 let s:SID = "\<SNR>" . s:SID() . '_'


[BUG] WhenActivated of a shown View and ViewModel is not called when in ViewModelViewHost

Describe the bug
When using ViewModelViewHost, the WhenActivated of a View and ViewModel not called and also the Compositedisposable is not disposed.
This basically renders the  ViewModelViewHost useless in Xamarin Forms.
Steps To Reproduce
Provide the steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
When working with ViewModelViewHost the WhenActivated should be called when the view becomes visible and the Compositedisposable should be disposed when the view is not visible anymore.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment(please complete the following information):
Xamarin Forms.  Android, iOS, UWP.
Additional context
It works in WPF.

Does this depend on:
[UWP, Android, iOS] Added better life cycle events #3214
https://github.com/xamarin/Xamarin.Forms/pull/3214
and
[Enhancement] Add better life cycle events #2210
https://github.com/xamarin/Xamarin.Forms/issues/2210
?

There is currently a bug in Xamarin.Forms on iOS that Xamararin is aware of.  They actually have the lifecycle method implemented in the wrong place for iOS.  Kent wrote a blog on it .
If you have a reproduction repository it would make it a lot easier to diagnose if it is ReactiveUI or a downstream dependency.

The xamarin group have started working on it recently https://github.com/xamarin/Xamarin.Forms/pull/3214

xamarin/Xamarin.Forms#3214

#3214 is closed

It is closed.  Doesn't look like the work is actually completed.
https://github.com/xamarin/Xamarin.Forms/pull/3214#issuecomment-487943808

Right. Looks like we have to subscribe on this one:
https://github.com/xamarin/Xamarin.Forms/issues/2210


Cannot add the HTTP + Webhook trigger or actions

The instructions mention "In Visual Studio Code, on the designer, add the HTTP + Webhook trigger or action".  I cannot seem to find the webhook trigger or action in the VS Code designer, whereas I can find almost all other trigger and actions in it. The only way I can build a webhook is by going to the Azure portal.
Is this a mistake (and there is no webhook in the VS Code designer), or an error in my setup? I can't find any information about this.
Cheers,
sandokan

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: cbdd9c30-1bc1-7af6-158d-f65ad23f45b7
Version Independent ID: c8828014-4369-ead5-2d05-8c3e823fc93e
Content: Create Standard workflows in single-tenant Azure Logic Apps with Visual Studio Code - Azure Logic Apps
Content Source: articles/logic-apps/create-single-tenant-workflows-visual-studio-code.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

@sandokanfirst
Thanks for your feedback! We will investigate and update as appropriate.

@sandokanfirst Thanks for reaching out. MicrosoftDocs Github issue is mainly related to the document issue. For any other issue I would recommend you to create a thread on the forums - Microsoft Q&A or Stack Overflow
As the issue is regarding the VS Code logic app extension, I will suggest you to reach out to the team on the Logic App VS Code extension repro here: https://github.com/Azure/LogicAppsUX
Right now, in extension UI we don't have the HTTP + webhook trigger. Feel free to reach out to the team for the feature request.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

The thing is that indeed, as you say "in extension UI we don't have the HTTP + webhook trigger". So this seems to me to be a documentation issue. Of course I could make a feature request, but I feel this is not necessary.
What needs to happen in my view is that the reference to the webhook action and trigger can be removed. Instead, instruct the user to do what is already described as a fallback option. As it says, "To make the prompt reappear, at your project's root level, open the local.settings.json file's shortcut menu, and select Configure Webhook Redirect Endpoint. The prompt now appears so you can provide the forwarding URL." If 'reappear' is replaced with 'appear' everything is hunky dory. You don't need the webhook trigger or action in the designer - I've just tested my application and it works perfectly.


Php debugger

Please how can I get rid on the php debugger that shows at the bottom of the page

You can simply remove the package "barryvdh/laravel-debugbar" from composer.json file and then reinstall your packages (remove the line that contains barryvdh/laravel-debugbar and then run composer update)


Fix/score precision

close: #25

It looks good! The only change I would like to ask for is if you can add a feature that enables/disables the changes, as this kinda changes the Redis representation of the queue id, and I think it might make it incompatible with the js version.
If you do that I will merge and publish


Travis CI should execute also all pytest tests

Travis shows failing pytest tests for this PR, which is actually the purpose of this PR.
If merged after #59 is merged, the tests should be OK again.

Thank you!


Issue with City states

When using the CQUI addon in conjuction with the "Yet (not) Another Maps Pack" - the most subscribed pack on the steam workshop - I cannot add envoys to city states.  I can also only see one city in the list at a time which appears to be the most recently met one, and even this I cannot add any envoys to.
Start any game and discover multiple city states.  Earn an envoy and try to add it.
More than one city state should appear in the list, and should be able to increase the number of envoys present.
I have some LUA logs requested by the other addon developer - https://pastebin.com/BMUx4URL
I have tried several iterations of various games, the addons work when used singly but not when used together.

Can you upload a savegame for me? The log alone isn't enough for us to help.

Thanks for your reply.  Please see attached.  Several city states have been met, but I can only interact with one on the Envoy screen.  I am showing as having 23 envoys to send, but cant place any.
Disabling CQUI & reloading the game allows me to place the envoys.
The map is a very large map (from the "Yet (not) ANother Maps Pack" addon) so may take a while to load.
Thanks
SEONDEOK 151 1860 AD.zip

I don't always explain myself properly, hopefully the attached screenshot will show it better - Hong Kong clearly visible near my land, the send envoys screen showing only Kabul.  The 1 envoy I h ave there is from meeting it first and not having had one placed.  The shot also shows 23 envoys available for placement.

(Possible) Duplicate of #355

@jigbim889 for the time being, you can refer to my answer here


Polar chart: why are labels on the x-axis?

When building a polar chart, I expected each sector's label to be placed around the pie as in the following picture:

Instead, my charts have labels running along the bottom border and vertical gridlines:

I'm having trouble figuring out how to fix this. Can anyone help?  Here is my options object:
let options = {
    title:{text:title},
    scale: {
        display:false,
        ticks:{
            callback:(e)=>{return this.parser(e)},
            min:0,
        },
        pointLabels:{
            callback:(e)=>'Difficulty: '+e
        },
        lineArc:true,
        gridLines:{
            display:false,
        }
    },
    legend: {
        display: true,
        position:'bottom',
    },
};

As you can see, I've tried options.scale.display=false and options.scale.gridLines.display=false to no avail. These only removed the concentric circles that overlay the chart.

@RoxKilly can you post a fiddle with this?

@etimberg  When I couldn't replicate it in plunkr with the options above, I looked deeper at my class that receives chart config and instantiates the chart, and  found that the problem was the default options set by that class to all charts (for any option not provided by the consuming class). These default options include:
scales: {
    xAxes: [{
        barPercentage:1,
        categoryPercentage:0.9
    }]
}

Since the options for this particular chart (from my opening post) don't overwrite the defaults, the defaults were included before the chart was created. I assumed that since options.scales aren't used to configure pie, doughnut and polar area charts, these options would be ignored for these chart types. I was mistaken.
It may be a good idea for the library to silently unset options that are not meant to be used before generating the chart; alternatively, throwing errors when unsupported options are used would also be helpful. Either would reduce unexpected behavior.
Thanks for making the fiddle suggestion; it was helpful.

Good idea about either removing or ignoring these config options. I've tagged as an enhancement :smile:

Nice. Turns out I only solved part of my problem. Is it possible to actually make the labels appear around the chart as in my first image from the OP? These would be the values from data.labels; the same that appear in the legend.

This is somewhat currently achievable. The radar chart uses the same scale with these lines draw. I think you could get away with trying the following, but I think it will cause more problems. This may require work on our end to configure the scale with a new way to display these.
options: {
  scale: {
    lineArc: false // changes the scale between two modes. Is true for the polar area chart
  }
}

Thanks. For future reference to anyone who wanted to accomplish the same thing, I'm attaching an image of the effect of options.scale.lineArc=false on a polarArea chart as of v2.1.6

It does put the labels around the chart, but on the corners rather than the base of the sectors as in my first OP image.  I'll be going back to lineArc=true.
@etimberg  Thanks for your help.

@RoxKilly Where you able to get the labels around the chart and on the base of the sectors as in your first image? How are you doing it?


Asp.Net Core DNX 4.5.1 and 5.0

Hi.
Is there a goal when MongoDb Synk will be full avaliable to asp.net core?
Thanks!!!

Hi! This should have been published a week ago via #9 but it looks like there's a problem with CI. Looking into it now.

Fixed, this is out now.

Thank you so much!!!


Is there a way to treat modals like a carousel?

I'm looking for a way to open multiple modals, then use previous/next buttons to navigate through them.
Is there a simple way to do this with Vex?

The demo on vex's website has something like a carousel: http://github.hubspot.com/vex/docs/welcome/, but functions by basically opening a lot of dialogs, and moving through them one by one.
For custom navigation (forward/back), I think you would need to build your own functionality on top of vex, that could open and close dialogs as the user navigates through them.

Yeah, I saw that and checked out the code. There didn't seem to be a simple way to go back, though.
Thanks for the response.


resolves matt-kruse/alexa-app#105

Coverage remained the same at 86.545% when pulling 73943d6cc984f12a4d81a68625a108b3ca135434 on trayburn:audio-player-events into 7b996699b55d9340844e695c654e9d71d2381fec on matt-kruse:master.

Note these in the build, I think from #104.

Coverage remained the same at 86.545% when pulling 84f2604955638f0146d8311ae2ea509c8b945c2a on trayburn:audio-player-events into 7b996699b55d9340844e695c654e9d71d2381fec on matt-kruse:master.

There we go, it was just a path issue with my new test files since I'm writing on a Windows box.  Should be good to go now.

I'll merge this.


LocalMAP can cause an infinite loop

I have eagerly jumped on the opportunity to test out LocalMAP and to read the accompanying paper. Another very stimulating paper and congratulations to everyone involved.
I have managed to make LocalMAP with default parameters hang indefinitely on several datasets, including the 20NG dataset provided in the data folder of this repo (among others, COIL-100 was also affected).
Although I strongly doubt this bit matters, in the interest of full reproducibility, I grab the .npy file this way (after installing httpx):
from io import BytesIO

import httpx
import numpy as np
from pacmap import pacmap

url = "https://github.com/YingfanWang/PaCMAP/raw/master/data/20NG.npy"

response = httpx.get(url, follow_redirects=True, timeout=10)
response.raise_for_status()

ng20 = np.load(BytesIO(response.content))

And then I am able to reliably (but not 100% of the time) cause LocalMAP to hang indefinitely like this:
localmap = pacmap.LocalMAP(random_state=1337)
ng20_localmap = localmap.fit_transform(ng20)

I think the lack of complete reproducibility might be due to threading issues in the new LocalMAP routines: even when the run completes successfully, costs diverge after the first 200 iterations between runs using a fresh kernel and a fixed seed. I am using numba 0.60.0 and python 3.12.8 on WSL and the frequency of the hanging seems highly dependent on the random_state value.
At any rate, the hanging occurs in sample_FP_nearby, and is almost certainly due to the logic here:
https://github.com/YingfanWang/PaCMAP/blob/803b6cc7fd911c12dc37eb9af1b93cdd9f822a71/source/pacmap/pacmap.py#L1129-L1132
where an infinite loop will occur if none of the candidate distances exceed low_dist_thres. FWIW one solution would be to fill result with -1, set the while loop to terminate after a fixed number of iterations or failures, and then continue in the FP loop in pacmap_grad_nearby_recip_sqrt if j == -1. This fixes the problem for all the datasets I tried it on without affecting other datasets.

Thank you for your interest in our work! I suspect the problem is due to the mismatch between v0.7.4, which is the previous version we used in the work, versus v0.7.6 in the current main branch. We're actively investigating this issue. Since this issue is LocalMAP-specific, I've also created a mirror in the LocalMAP repo and we will post our further response there.

We've done some investigation on this issue and we managed to reproduce this error on our machines.

The piece of code you mentioned is the culprit for the infinite loop, and @williamsyy has pushed a hotfix on the LocalMAP repo to fix this issue. The new version will re-use the old FP pairs in case the sampling fail after certain number of rounds.
The issue seems to be related with hardware specifications as well as other factors such as the random seeds. We didn't implement deterministic features for the LocalMAP, so there might be some randomness in the output due to pair sampling. On our experiment bench, we encountered less "bad" random seeds and didn't reproduce the divergence of the loss, either with Python 3.11 or 3.12. However, we found a larger amount of "bad" random seeds when running on an older machine. I suspect this is the reason that this problem was ignored during our experiments.

I've tested on the latest master and LocalMAP now completes with all datasets I have tried.
Many thanks for such fast work. Happy holidays.


Trezor AQUA claim work around no longer working around ;-(

Hi Vincent I am very grateful for your work around. Unfortunately its stopped working it hangs at the waiting for wallet stage when signing the first submission..
Generate XDR, enter XDR, sign - waiting for wallet. Indefinitely. If you need screenshots happy to provide.

Hi,
This is a known issue with trezor-connect and the latest stellar sdk.
The fixes have been pushed on trezor side, it looks like it's almost ready to be published.
After that the stellar laboratory will be updated and then you will be able to sign with the lab.
In the meantime, if you have other ways to sign your transactions this should work.
For reference, here is the trezor PR that should solve the issue (i.e. contains the fix):
https://github.com/trezor/trezor-suite/pull/9755

Thank you so much for all you do Vinamogit! If it wasn't for you, I would have never been able to claim a single airdrop. Unfortunately, the stellar lab hasn't been working for months now. When I try to sign the transaction, I get the error: "Invalid parameter "signer/key" (= undefined): Expected union value" and sadly, the stellar lab still doesn't seem to have resolved the Trezor issue. Could you please check to see if maybe the problem is on my end, or do you also experience the same error? Thank you so much for your attention.

Hi,
This workaround should be deprecated now since Trezor added the ability to claim claimable balances directly.
If you want to claim some Aqua airdrop you should go to aqua.network and use the "stellar laboratory" login type and follow the procedure.
I hope this should work now.

This workaround should be deprecated now since Trezor added the ability to claim claimable balances directly.

Hmm, at least with my Trezor One this still doesn't work since it locks up when trying to sign the claim transaction from aqua.network/account, like it always used to do when trying to sign claiming transactions. Trezor Suite shows it has the latest firmware installed (which is 1.12.1 from 15th March 2023, so it obviously will not contain any recent bugfix).
I'm currently running into the same issue as @felixlucid. Might need to find some other way to sign then, or try with a Trezor Model T.


Foresee SSD cannot wake up after sleep

I have two Redmibook 14 EE, one is Samsung SSD, and the other is Forestee s50af512gb SSD. Foresee SSD cannot wake up after sleep. Any suggestions?

Hello! What version of mac OS are you using?

Hello! What version of mac OS are you using?

Hello! What version of mac OS are you using?

macOS 12.4, This problem occasionally occurs in Samsung SSD.

Unfortunately, I don't know exactly what the problem might be. In general, I recommend installing mac OS big sur due to sleep problems and Bluetooth on Monterey. If you were using Mac OS Big sur, I would send you a test build, which I use myself on an ongoing basis, but the problem is that it is not intended for new versions (there are no kexes, I did not add them)

Thank you！ I'll try it.


Draw and modify interaction need to accept geometry layout

The draw and modify interactions create new point geometries.  The interactions need to be configured with a geometry layout in order to be used with anything but XY layouts.

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

I think you're right, @drnextgis

@ahocevar I've made a PR to fix that. Please review.


Running the cube example on windows crashes with a D3D compile error

Cloning and running the cube example locally (modifying it to use the DX12 backend by adding Some(rend3::types::Backend::Dx12) to the create_iad call) crashes when running it
Here's the error:
[ERROR wgpu_core::validation] Unexpected varying type: Array { base: [4], size: Constant([7]), stride: 4 }
[ERROR wgpu::backend::direct] wgpu error: Validation Error

    Caused by:
        In Device::create_render_pipeline
          note: label = `depth opaque prepass`
        Internal error in VERTEX shader: D3DCompile error (0x80004005): C:\Source\rend3\depth pass vert(47,12-17): error X3003: redefinition of 'VertexOutput_main::member'

For the time being I can use the default (Vulkan) backend but that spams a lot of wgpu_hal errors into the terminal

Thanks for the report!
This particular validation error has been fixed in the latest naga/wgpu-hal so make sure both are up to date: cargo update. Unfortunately once you hit that, you'll hit another D3D compile error. This one I know about but haven't yet reported to naga. Will use this issue as a tracking issue for that.
The vulkan validation errors might also be solved by updating. If it isn't solved, make sure your validation layers are up to date. If it still reports an issue, file a new issue.

Ah sorry, I realized I had patched to a git version of wgpu but never removed it. I'll remove that in my next PR tonight. The d3d error for context:
    Caused by:
        In Device::create_render_pipeline
          note: label = `opaque pass`
        Internal error in FRAGMENT shader: D3DCompile error (0x80004005): C:\Users\conno\Programming\rend3\forward pass frag(463,30-37): error X3004: undeclared identifier '_expr388'

Yup, you're totally right, after running cargo update and updating to the newest version of rend3 I'm now running into exactly that error message.
Switching back to the Vulkan backend I'm getting these errors:
[ERROR wgpu_hal::vulkan::instance] GENERAL [Loader Message (0x0)]
        Failed to open dynamic library "C:\ProgramData\obs-studio-hook\.\graphics-hook32.dll" with error 193
[ERROR wgpu_hal::vulkan::instance]      objects: (type: INSTANCE, hndl: 0x2c1ec089f30, name: ?)
[ERROR wgpu_core::validation] Unexpected varying type: Array { base: [4], size: Constant([8]), stride: 4 }
[ERROR wgpu_core::validation] Unexpected varying type: Array { base: [4], size: Constant([5]), stride: 4 }

The first message (i.e the Failed to open dynamic library ...) is most definitely my "fault" (RTSS did some weird shenanigans), but I'm not sure if the others are also my faults or not, but at least that's all of them

Are those errors fatal? If not they look expected. The first and second are the same problem (loading the obs layer failed for some reason), and the last two are known problems with glslc (it generates code that touches a builtin that I don't actually use, and webgpu doesn't support)

Their not fatal, the application just keeps on trucking

Filed https://github.com/gfx-rs/naga/issues/1358


Command Palette Doesn't Show up

Environment
Microsoft Windows [Version 10.0.19041.329]
Windows Terminal version (if applicable): 1.1.2021.0
Steps to reproduce

Add    { "command": "commandPalette", "keys": ["ctrl+shift+p"] }   to the keybindings

Expected behavior

Command Palette shows up

Actual behavior

^P gets printed on the terminal -->> Command Palette Does not show up.
In fact, Command Palette does not seem to be working for any key combinations ( I tried shift+P, ctrl+p, etc)

The Command Palette isn't in 1.1, it's in Windows Terminal Preview currently, version 1.2


Support packing from explicit list

I needed the ability to pack from an explicit list instead of every loose snapshots to support parallel builds.
This adds --snapshots-from and --snapshots0-from to mirror the design of store's --files-from and --files0-from
My Rust is, well.. rusty so hopefully this is ok :)
Fixes #100

Thanks for the review, I've made the requested changes and ran cargo fmt and cargo clippy.

That should take care of all the feedback!

Please document the newly added options here:
https://github.com/elfshaker/elfshaker/blob/main/docs/users/usage.md#pack-loose-snapshots

Please document the newly added options here: https://github.com/elfshaker/elfshaker/blob/main/docs/users/usage.md#pack-loose-snapshots

Tracked https://github.com/elfshaker/elfshaker/issues/105, help appreciated.


Making cli install relative to node_modules

This PR should address #255 and make the install relative to the node_modules folder either globally or locally. The only caveat when using as a dependency and calling through yarn or npx is that process.cwd() will default to the package.json  root folder.
The uninstall script has been removed as binaries will be handled by npm and .azurefunctions should only hold config after this change.

@nelak,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@nelak sorry for the long delay, I missed the notification on this PR and never checked.
Can you change the target branch to core instead of master?

@ahmelsayed Next time I'll tag you then
I'm thinking the next change would be to add some kind of progress indicator as installing may take a while on slower connections and you are left without any feedback of what's going on


Similarity search title and vector

The current Python demo creates embeddings for both the title and content, but only uses the content vector for searching.
https://github.com/Azure/cognitive-search-vector-pr/blob/main/demo-python/code/azure-search-vector-python-sample.ipynb
Logically looking at the code the field fields it suggests that it would be possible to search multiple vectors. This however does not seem to be the case, and it returns an error if you attempt to pass a comma separated list of values. Will this be something that could be supported in the future, or does a solution exist today?

Hi @phillebaba this is going to be supported in the next few weeks. Please stay tuned to this repo for updates.


In-app content reporting

Issue
Closes #5676 Content reports (dmca and others)
Screenshots
Here are some screenshots.  DMCA one includes more fields, but looks roughly the same.

Click to expand

Will this page accept a URL parameter with claim id? If not, let's please add that. This will be linked from other apps like IOS/Android/Desktop so the UI doesn't have to be re-created there.

I missed the attached images before. Some feedback:

Timestamp UI could be improved if it's easy
Colons are almost always a sign that you can improve styling. Properly styled labels and values do not require colons.
"Submit Report?" needs another title. Perhaps confirmation dialog could be styled after the confirm publish dialog?
The green checkmark next to Report Submitted appears to introduce a new style. Either the dialog should close and a snackbar should be used, or the dialog can stay open and the feedback can be given by the colored bottom bar (I forget the name of this element).

--- Changes ---

Update:

CATEGORIES to [CATEGORIES]
RICK_URL to REPORT_URL

Split out the effects, and correct the dependancies.
Fix bug of not being able to proceed if reporting on Markdown because timestamp wasn't set.

Ping just in case ... anything else that needs changing?

All good, I'll get this shipped tomorrow. Thanks again!


Improve HttpBatchClient

Closes #1309
Closes #1310
Closes #1311
cc @codehans

Looks great! Just the one comment


Mark in_isr as unused in osal_pico.h

This prevents the following warning when building with -Wextra:
In file included from [redacted]/pico-sdk/lib/tinyusb/src/osal/osal.h:57,
                 from [redacted]/pico-sdk/lib/tinyusb/src/tusb.h:38,
                 from [redacted]/pico-sdk/lib/tinyusb/src/device/usbd.c:31:
[redacted]/pico-sdk/lib/tinyusb/src/osal/osal_pico.h: In function 'osal_semaphore_post':
[redacted]/pico-sdk/lib/tinyusb/src/osal/osal_pico.h:60:71: error: unused parameter 'in_isr' [-Werror=unused-parameter]
   60 | static inline bool osal_semaphore_post(osal_semaphore_t sem_hdl, bool in_isr)
      |                                                                       ^
In file included from [redacted]/pico-sdk/lib/tinyusb/src/osal/osal.h:57,
                 from [redacted]/pico-sdk/lib/tinyusb/src/tusb.h:38,
                 from [redacted]/pico-sdk/lib/tinyusb/src/device/usbd.c:31:
[redacted]/pico-sdk/lib/tinyusb/src/osal/osal_pico.h: In function 'osal_queue_send':
[redacted]/pico-sdk/lib/tinyusb/src/osal/osal_pico.h:162:79: error: unused parameter 'in_isr' [-Werror=unused-parameter]
  162 | static inline bool osal_queue_send(osal_queue_t qhdl, void const * data, bool in_isr)
      |

Casting unused arguments to void is how unused parameters are dealt with in the rest of the tinyusb codebase

Oops, there are a few other places that have the same issue. I will fix them all and amend the commit

At some point in the near future we'll be switching to use upstream version of tinyusb (see raspberrypi/pico-sdk#321 ), so  any PRs should probably be made to the upstream repo, https://github.com/hathach/tinyusb.

OK. I can't get my application to compile with the upstream tinyusb, so I'll hold off until the switch is complete.


Fixed the issue with new users not being added when authorized from a SA...

...ML request.

:+1:


Add ability to disable plugins?

As far as I can tell the only way to currently disable plugins is via the eslint-disable comments i.e:
/* eslint-disable import/no-unassigned-import */

I was wondering if it would be possible to add support for something like this that would allow users to blanket disable a plugin from there xo config in the package.json (this would take some work), something like:
"xo": {
  "eslint-plugin-disable": {
      "paths": {
        "import/no-unassigned-import": ["path/to/js/**/*.js"]
      }
    }
}

or
"xo": {
  "eslint-plugin-disable": [
      "import/no-unassigned-import"
    ]
}

I am hoping to hacking together a PR but wanted your input before I started.
Cheers.

You can use the config overrides targeted at a sub-path with the rules option.

Hey @sindresorhus,
Sorry could you give an example of what that would look like?
Cheers,
Otis.

https://github.com/sindresorhus/xo#config-overrides

Awesome got it :).
Thank you!


Add Design Pattern and Inspiration Tools

Add a new section for design pattern, user flow, and task exploration tools for guidance and inspiration

Yes, I was just thinking about some Resource section like the inspiration one, I have few adds in my mind 🙌

wow, thanks for adding a whole section!!


Why not run 'didReceive(_: target:)' delegate function in custom plugin?

struct IndicatorPlugin: PluginType {
    /// Called by the provider as soon as the request is about to start
    func willSend(_ request: RequestType, target: TargetType) {
        print("began")
    }

    /// Called by the provider as soon as a response arrives, even if the request is canceled.
    func didReceive(_ result: Result<Response, MoyaError>, target: TargetType) {
        print("ended")
    }
}

        let provider = MoyaProvider<Api>(stubClosure: { _ in
            .immediate
        }, plugins: [IndicatorPlugin()])

Hey @qiangjindong, please take a look at https://github.com/Moya/Moya/issues/1963 and see if it helps.


Fix KV issues and remove non_unique

Change Description

This PR fixes some issues with KV and the up port to llvm9.

Issues with building on the most recent versions of clang and gcc.
WASM size bloat because of std::function and performance concerns with its use.
Cleanup some of the macros.
Fix issues with memory management and over allocating.
remove non_unique as it isn't truly an index and the abstraction isn't fully thought out or functional.

API Changes

[ ] API Changes

The type alias non_unique is no longer available.
Documentation Additions

[ ] Documentation Additions

Closing this PR and making a new one to get the changes in develop for cicd.


Exec eats a lot of CPU while waiting

I have noticed that if I launch long running programs with Exec (for example BrowserSync) then Robo starts to consume a lot of CPU just sitting there and waiting. It's about 12% in my system (Core i7 CPU, Win7x64).
It's clearly on PHP side as shown by Process Explorer and it's not the issue if I run exactly same command directly in console.

Can you please run the same command through exec() inside a normal php file and simply do php testfile.php to see if the issue is specific to exec() or something inside Robo?

Sorry, lost track of this. :) Just running it with exec doesn't stress CPU, might be something outtput-related? Exec is not sending realtime output to console, right?
Call in Robo:
public function sync( $slides ) {
	$this->taskExec( 'browser-sync start' )
	     ->arg( '--host "dev.rarst.net" --open external' )
	     ->arg( '--files "shared.css,' . $slides . '/index.html"' )
	     ->arg( '--proxy "dev.rarst.net/slides/' . $slides . '"' )
	     ->run();
}

Call in plain PHP
exec('browser-sync start --host "dev.rarst.net" --open external --files "shared.css,answering/index.html" --proxy "dev.rarst.net/slides/answering"');

Anything else I can do to help figure this out? :)

Closed due to lack of activity.
I will add that taskExec just calls through to the Symfony Process component. This issue would probably be best addressed there, if it is still a problem.


db.WithContext should rollback the txn in case of panic

Rollback the txn in case of panic and propagate the panic.

@carmenlau @kiootic

I don't think it can be done at context. Instead, the middleware (core/middleware.DBMiddleware) should do this (like how it is done for redis).

I guess the reason is TxContext exposes three low-level functions BeginTx, CommitTx and RollbackTx so it is impossible to write a defer statement to rollback on panic. What about removing these 3 low-level functions and require the caller to use db.WithContext. It is also a good opportunity to move db.WithContext to TxContext.Do.

The SafeTxContext can also be embedded into TxContext. It seems that no one is using SafeTxContext.

Sure. To conclude:

Merge SafeTxContext into TxContext
TxContext only exposes Do function for executing a transaction.

Is this blocking any issue?

No. This is not blocking me. But this is actually a very old bug. It is also quite dangerous because the connection is returned to the pool without being explicitly rolled back or committed. However, what I observed is that the changes are actually committed but I did not figure why.


Why does my bundle file contain \n characters?

Do you want to request a feature or report a bug?
I want to report a bug. The bundle files contain \n everywhere. Console showed javascript errors.

What is the current behavior?
Webpack bundles files that contain \n everywhere
If the current behavior is a bug, please provide the steps to reproduce.

Here is my webpack.config.js
`var path = require('path');
module.exports = {
entry: {
"/js/editor-bundle.js": './src/js/Editor.js',
"/js/widget-bundle.js": './src/js/Widget.js',
"/js/popup-bundle.js": './src/js/Popup.js',
"/js/settings-bundle.js": './src/js/Settings.js',
"/js/front-bundle.js": './src/js/Front.js',
"/css/editor-bundle.js" : "./src/css/editor.js",
"/css/popup-manager-bundle.js" : "./src/css/popup.js",
"/css/widget-manager-bundle.js" : "./src/css/widget.js",
"/css/front-styles-bundle.js" : "./src/css/front.js",
"/css/settings.js" : "./src/css/settings.scss",
},
module: {
rules: [
{
test: /.(js|jsx)$/,
exclude: /node_modules/,
use: ['babel-loader']
},
// { // sass / scss loader for webpack
//   test: /\.(sass|scss)$/,
//   loader: ExtractTextPlugin.extract(['css-loader', 'sass-loader'])
// }
	{
		test: /\.scss$/,
    use: [
      {
        loader: "style-loader" // creates style nodes from JS strings
      },
      {
        loader: "css-loader" // translates CSS into CommonJS
      },
      {
        loader: "sass-loader" // compiles Sass to CSS
      }
    ]

	}
]

},
output: {
path: path.resolve(__dirname, 'bundle'),
publicPath: '/',
filename: '[name]'
},
externals: {
// require("jquery") is external and available
//  on the global var jQuery
"jquery": "jQuery"
},
optimization: {
// We no not want to minimize our code.
minimize: false
}
};
`
Here is my package.json
{   "name": "wp-lead-plus-x",   "version": "1.0.0",   "description": "=== Free Squeeze Page, Landing Page Builder & Templates Creator For WordPress=== Contributors: codingpuss, core37 Tags: squeeze page, page builder, landing pages, squeeze page plugin, squeeze page creator, splash page, splash page templates, page builder, landing page creator, squeeze page templates, WordPress squeeze page, best squeeze page, squeeze page for WordPress, sales page builder, free landing pages creator, video landing page, free landing page templates Requires at least: 3.8 Donate link: https://wpleadplus.com/ Tested up to: 4.9.4 Requires PHP: 5.3 Stable tag: 2.0.8 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html",   "main": "index.js",   "scripts": {     "start": "webpack --watch --mode development"   },   "repository": {     "type": "git",     "url"<EMAIL_ADDRESS> },   "keywords": [],   "author": "",   "license": "ISC",   "homepage": "https://bitbucket.org/gatoloco/wp-lead-plus-x#readme",   "devDependencies": {     "babel-core": "^6.26.3",     "babel-loader": "^7.1.4",     "babel-preset-env": "^1.7.0",     "bable-loader": "0.0.1-security",     "css-loader": "^0.28.11",     "extract-text-webpack-plugin": "^3.0.2",     "lodash": "^4.17.10",     "node-sass": "^4.9.0",     "sass-loader": "^7.0.3",     "style-loader": "^0.21.0",     "webpack": "^4.12.1",     "webpack-command": "^0.2.1"   },   "babel": {     "presets": [       "env"     ]   } }
What is the expected behavior?
I think it shouldn't generate \n
If this is a feature request, what is motivation or use case for changing the behavior?
No, this is not a feature request
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
webpack version:  4.12.1
Node.js version: 10.4.1
Operating System: MacOS
Additional tools:

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template and reopen, or open a new issue.

I've updated the template. Thanks


update google play to 5

This is the first step to migrate to the new Google Play SDK 5.0.0.

hi @andresesfm , is it possible also to use the queryProductDetailsAsync instead of the deprecated querySkuDetailsAsync? the main reason I am requesting is that the  queryProductDetailsAsync is now returning the promos for that subscription

hi @andresesfm , is it possible also to use the queryProductDetailsAsync instead of the deprecated querySkuDetailsAsync? the main reason I am requesting is that the queryProductDetailsAsync is now returning the promos for that subscription
thanks! :)

Also need to use productDetails.subscriptionOfferDetails to handle the offers of subscription, please check the migration guide. Thanks!

It's now implemented @PaxLyj please take a look

hi @andresesfm I am encountering this issue after U upgrade to v9.0.0-beta
Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.7/userguide/command_line_interface.html#sec:command_line_warnings

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* Where:
Build file '***/node_modules/react-native-iap/android/build.gradle' line: 19

* What went wrong:
A problem occurred evaluating project ':react-native-iap'.
> Failed to apply plugin 'kotlin-android'.
   > The current Gradle version 6.7 is not compatible with the Kotlin Gradle plugin. Please use Gradle 6.7.1 or newer, or the previous version of the Kotlin plugin.

* 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: Task failed with an exception.
-----------
* What went wrong:
A problem occurred configuring project ':react-native-iap'.
> compileSdkVersion is not specified. Please add it to build.gradle

* 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 2m 56s


Question about level 3 acceptance re static analysis

I was looking over the proposed Level 3 guidelines and saw this line:

Uses static analysis tools to validate pedigree and safety.

My concern is that in the F# community there isn't not exactly a strong stable of such tools. Does that mean that F# projects would not be eligible for that tier? How stringent is that requirement?

How about http://fsprojects.github.io/FSharpLint/
FSharpLint is a form of static analysis.

That's fair, though many of those rules are stylistic in nature and don't change correctness. I use fsharplint professionally through the ionide integration, so am familiar with it's feature set.

FSLint is a subjective set of rules (and this could be equally applied to Fantomas). It's not like the static analysis tools in the C# world.


Persistent notification to connect account

Every time I restart Chrome I get a notification from the extension to connect my Last.fm account, even if I already done it.

This is a long standing issue, that's really hard to reproduce. Please see #458 if you can get some more intel.


Remove com.* from labels.

After talking with @phobologic, since we don't own empire.com we should just remove the com. prefix. empire.app should give us enough namespacing and it reads better.

:+1: sorry for the late comments :)


Feat: add a global finalizer callback

After #184 has been merged, this library would have a global preparation function but not a corresponding global finalizer that would fire once, both for successful/failed transitions, something necessary when implementing protocols like 2-phase commits.  I believe that there is no way to workaround such functionality with code external to this library in a single place (i.e. without proliferating try...except/finally in all trigger-calls).
Therefore I suggest to add a finalize_after_all_transitions callback in a finally block inside Event._trigger().   The code for such a feature, without error handling would be something like this:
        for func in self.machine.prepare_conditions_check:
            self.machine._callback(func, event_data)
            logger.debug("Executed machine preparation callback '%s' before conditions." % func)
        ok = False
        try:
            for t in self.transitions[state.name]:
                event_data.transition = t
                if t.execute(event_data):
                    return True
            return False
        finally:
            event_data.kwargs['ok'] = ok  # Provisional name for `ok` flag, or an attr on machine?
            for func in self.machine.finalize_after_all_transitions:
                self.machine._callback(func, event_data)
                logger.debug("Executed machine finalize callback '%s' after all transitions." % func)

Of course if finalize cb is to receive the error raised, an except case is need additionally in the try block to store the captured exception.  Like the ok flag above, I'm thinking of 2 possibilities where to store it:
a) on the machine as an extra attribute, or
b) on the event-data, as another keyword item e.g. error.
Case (a) needs clearing this attribute before every trigger and kind of violate separation-of-concerns law; case (b) might clash with names already used by existing clients of the library.

Hi @ankostis,
I added a global finalize_event attribute and renamed prepare_conditions_check to prepare_transition. For now, return values are handled like before:
If a transition is successful, Event.trigger will return True and False if no transition was applicable (if events are processed instantly and not queued).
If a callback raises an exception, this exception will be passed.
The second part of your suggestion is a bit more tricky: Should the result of the transition be passed to finalize callbacks and how? Personally, I would prefer to let the user handle exceptions. Also I'd prefer to handle finalize callbacks the same was as other callbacks.
As mentioned before, checking the success of a transition can already be done with Event.trigger. Silently adding a keyword may lead to errors if callbacks do not expect it.

So with #184, you have implemented a "finalizer" capable of releasing "resources."

Personally, I would prefer to let the user handle exceptions.

I understand that handling exceptions becomes a burden. so you prefer to shift that to the user.
But handling exceptions is a requirement when emulating commit/rollback  behavior.
With #184 as is, a lost of user effort would be needed: capture exceptions inside ALL callbacks, store an appropriate flag somewhere, and then re-raise them.  At least that is my understanding.
Are we sure this is desired?
[brainstorming now] should'nt the true/false trigger flag be an attribute of the event_data?

capture exceptions inside ALL callbacks

Maybe I am missing something but as far as I can tell the effort stays exactly the same. Currently, a user has to try/except every call to Event.trigger if this may raise an exception (MachineError or exceptions caused by the callbacks).
This behaviour is not changed because of #184. If you have a variety of callbacks and all of them may raise an exception, you still can do
try:
    model.work()
except SomeException as e:
    # handle error

shouldn't the true/false trigger flag be an attribute of the event_data?
As mentioned before, adding it to event_data.kwargs may lead to errors if callback do not except an automatically generated parameter. Adding result to event_data itself could be done without side effects. This requires a Machine with send_event=True though.

[...] the effort stays exactly the same. [...] This behaviour is not changed because of #184.

I believe there is a subtle misunderstanding.
Surrounding model.work() won't help you implement commit/rollback behavior WITH finalize_event callbacks.
So if (one of) the point of #184 is to support commit/rollback capabilities, then there is no comparison of the effort; previously you just couldn't implement it centrally, unless you surrounded every trigger point, as you said.
Is it now more clear what I'm thinking?

Adding result to event_data itself could be done without side effects. This requires a Machine with send_event=True though.

That could be an interesting opportunity: if you set send_event=true, you get exception capturing for free?

(I'll give it another shot)
Before #184, in order to have a resource-cleanup-finalizer, you had to surround every trigger-point in try/except.
Now with finalize_event you don't have to do that. And that's great.
But you still need this try/except for implementing commit/rollback.

Hi @ankostis,

Surrounding model.work() won't help you implement commit/rollback behavior WITH finalize_event callbacks.

I see. Maybe we can find a way to process errors in callbacks without 'swallowing' caught exceptions in Event.trigger. As much as I like to enable your workflow, I also want to keep the current way of doing things for the sake of stability. I do not want to claim that the current way is superior but without further feedback, we cannot distinguish what is more desirable.

That could be an interesting opportunity: if you set send_event=true, you get exception capturing for free?

Unfortunately, no. Adding the boolean result would just tell you if a transition took place. But this could also be achieved with model callbacks as mentioned above.
Perhaps, we can solve this issue on the model level. This way we can keep core universal and do not have to introduce another attribute like raise_exceptions and/or implement specific finalize callback behaviour.

If you can catch exceptions raised by Event.trigger but want to process them in finalize callbacks, we could add error to event_data but raise every caught error. This would keep things as they currently are but also add useful information for commit/rollback strategies with finalize. Would that work for you?

You mean a boolean EventData.error attribute?
Yes, that's fine.
Actually much better than the OK flag in kwargs.

Then it should be called errored,  no?

You mean a boolean EventData.error attribute?

No, I mean the actual error.
Like
event_data.error = None
try:
...
except Error as e:
    event_data.error = e
    raise e
finally:
    for func in self.machine.finalize_after_all_transitions:
    ...

Yes, that would be the a perfect solution.  Thanks.

resolved by #175 I hope


npx create-react-app is not working

$ npx create-react-app my-app
You are running create-react-app 4.0.0, which is behind the latest release (4.0.1).
We no longer support global installation of Create React App.
Please remove any global installs with one of the following commands:

npm uninstall -g create-react-app
yarn global remove create-react-app

The latest instructions for creating a new app can be found here:
https://create-react-app.dev/docs/getting-started/
npm ERR! code 1
npm ERR! path C:\Users\User\Desktop
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c create-react-app my-app
npm ERR!      C:\Users\User\AppData\Local\npm-cache_logs\2020-11-23T18_27_48_723Z-debug.log

I had the same error and the solution for me was to remove the npm cache folder:
https://docs.npmjs.com/cli/v6/configuring-npm/folders#cache

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

Thanks 😊😊
On Thu, Nov 26, 2020, 12:02 Rishav Sinha<EMAIL_ADDRESS>wrote:

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/issues/10132#issuecomment-734114764,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMP2GX67QW7J7NQTQF46GF3SRX4PZANCNFSM4T73DQDQ
.

Worked for me as well, thank you.

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

Thanks for this! Worked for me too.

First, you'll need to uninstall "create-react-app" using the "npm uninstall -g create-react-app" command.
Run "npx create-react-app my-app" each time you want to create a new React app.
Hope you find this helpful

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

It's not working for me. Please help me!😢
Again I saw this error----
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path D:\udemy/package.json
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, open 'D:\udemy\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR!      C:\Users\User\AppData\Local\npm-cache_logs\2020-11-30T20_18_36_036Z-debug.log

"npx create-react-app my-app" instead of "npm install -g create-react-app".

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

It's not working for me. Please help me!😢
Again I saw this error----
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path D:\udemy/package.json
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, open 'D:\udemy\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR!  C:\Users\User\AppData\Local\npm-cache_logs\2020-11-30T20_18_36_036Z-debug.log

"npx create-react-app my-app" instead of "npm install -g create-react-app"

**npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /Users/reach/Documents/Personal Projects/Service_Project/iCareerZ/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/Users/reach/Documents/Personal Projects/Service_Project/iCareerZ/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR!      /Users/reach/.npmrc/_logs/2020-12-02T01_50_49_350Z-debug.log**
I also got the same problem. I try "npx create-react-app my-app" and it seems like not working. Please help

use yarn is better

npm init -y
npx create-react-app project1

I had to run both of the following commands to resolve this issue.

npm uninstall -g create-react-app
yarn global remove create-react-app

Possibly the wording on the following error message could be updated to indicate that both of these commands may be required.
Change:
Please remove any global installs with one of the following commands:
To:
Please remove any global installs with one or both of the following commands:

also chiming in here. i think there's a dependency issue somewhere, as i've confirmed this is happening on node v12.18.0 and v15.3.0:
acrossan/src → node -v
v15.3.0

acrossan/src → npm list -g | grep 'create-react-app'

acrossan/src → npx create-react-app test
Need to install the following packages:
  create-react-app
Ok to proceed? (y) y

Creating a new React app in /Users/acrossan/src/test.

Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...

npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR!      /Users/acrossan/.npm/_logs/2020-12-02T18_24_01_607Z-debug.log

Aborting installation.
  npm install --save --save-exact --loglevel error react react-dom react-scripts cra-template has failed.

Deleting generated file... package.json
Deleting test/ from /Users/acrossan/src
Done.
npm ERR! code 1
npm ERR! path /Users/acrossan/src
npm ERR! command failed
npm ERR! command sh -c create-react-app test

npm ERR!      /Users/acrossan/.npm/_logs/2020-12-02T18_24_01_670Z-debug.log

acrossan/src → npm i -g create-react-app

added 67 packages in 828ms

4 packages are looking for funding
  run `npm fund` for details
acrossan/src → create-react-app test

Creating a new React app in /Users/acrossan/src/test.

Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...

npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR!      /Users/acrossan/.npm/_logs/2020-12-02T18_28_06_026Z-debug.log

Aborting installation.
  npm install --save --save-exact --loglevel error react react-dom react-scripts cra-template has failed.

Deleting generated file... package.json
Deleting test/ from /Users/acrossan/src
Done.

I am able to solve the problem by first trying to uninstall the npm globally, update the npm, clear the cache then using npx command to create React app.
The command is as below:
npm uninstall -g create-react-app && npm i -g npm@latest && sudo npm cache clean -f && npx create-react-app my-app
This is taken from one of the Stack Overflow posts.

reach009 thnks

I am able to solve the problem by first trying to uninstall the npm globally, update the npm, clear the cache then using npx command to create React app.
The command is as below:
npm uninstall -g create-react-app && npm i -g npm@latest && sudo npm cache clean -f && npx create-react-app my-app
This is taken from one of the Stack Overflow posts.
https://stackoverflow.com/questions/64963796/create-react-app-is-not-working-since-version-4-0-1/65043610

This worked for me. Thank you very much @reach009

Worked for me as well. Don't forget to update npm. I initially tried all the steps besides that and it kept thinking I still had create-react-app installed globally even though I didn't.

I have never had create-react-app installed and still receive this error. In fact, I have no npm packages installed at all, but it still warns that I am running 4.0.0, and that global installation is no longer supported, and then exits.
node 14.15.0.

I am facing the same issue mentioned in the first post.
I have tried different versions of Node and NPM, npm uninstall -g create-react-app (although never installed CRA globally on my current machine), clear npm cache, reinstall the entire Node. My $ which create-react-app returns nothing, $ npm list -g --depth=0 returns
/Users/kvaropil/.nvm/versions/node/v14.15.1/lib
└──<EMAIL_ADDRESS>
I am really out of ideas how to fix this issue.

I had the same error and the solution for me was to remove the npm cache folder:
https://docs.npmjs.com/cli/v6/configuring-npm/folders#cache

This worked for me too, however, I went into ~/.npm/_npx/<cache hash>/node_modules and deleted the create-react-app directory specifically. Then, just to be very sure, I also manually edited ~/.npm/_npx/<cache hash>/package.json and set the version for create-react-app to 4.0.1, even though it was marked with a carrot already.
Then I ran npx create-react-app ... again, it prompted to install it, hit "y", and I was back in business.

I've also run into the same problem as others above and have been going around in circles for 2 hours.  My steps:
'npm uninstall -g create-react-app' (even though I never installed create-react-app globally),
'npm cache clean --force' (I also tried 'sudo npm cache clean -f')
then 'npx create-react-app my-app.'
Yet, I'm still running an error that I have it globally installed:
You are running create-react-app 4.0.0, which is behind the latest release (4.0.1).
We no longer support global installation of Create React App.
I'm at a loss and stuck in what feels like a maze.  My next step is to manually start deleting and files as baalansellers suggests, but I don't think that should be necessary.

I am able to solve the problem by first trying to uninstall the npm globally, update the npm, clear the cache then using npx command to create React app.
The command is as below:
npm uninstall -g create-react-app && npm i -g npm@latest && sudo npm cache clean -f && npx create-react-app my-app
This is taken from one of the Stack Overflow posts.
https://stackoverflow.com/questions/64963796/create-react-app-is-not-working-since-version-4-0-1/65043610

This did the trick for me. Thanks!

For me I got the same error even though create-react-app was installed in a parent directory, not globally. So I ran npm uninstall create-react-app without the -g flag and it worked.

For those who ran into similar issues I had, baalansellers (3 above) had the answer.  Thanks!
"... ~/.npm/_npx//node_modules and deleted the create-react-app directory specifically. Then, just to be very sure, I also manually edited ~/.npm/_npx//package.json and set the version for create-react-app to 4.0.1, even though it was marked with a carrot already.
Then I ran npx create-react-app ... again, it prompted to install it, hit "y", and I was back in business... "

I am able to solve the problem by first trying to uninstall the npm globally, update the npm, clear the cache then using npx command to create React app.
The command is as below:
npm uninstall -g create-react-app && npm i -g npm@latest && sudo npm cache clean -f && npx create-react-app my-app
This is taken from one of the Stack Overflow posts.
https://stackoverflow.com/questions/64963796/create-react-app-is-not-working-since-version-4-0-1/65043610

it isn't working for me, please help nothing is working for me

I am able to solve the problem by first trying to uninstall the npm globally, update the npm, clear the cache then using npx command to create React app.
The command is as below:
npm uninstall -g create-react-app && npm i -g npm@latest && sudo npm cache clean -f && npx create-react-app my-app
This is taken from one of the Stack Overflow posts.
https://stackoverflow.com/questions/64963796/create-react-app-is-not-working-since-version-4-0-1/65043610

it isn't working for me, please help nothing is working for me

@1-pro: Can you share more details on the error messages you got?

I am able to solve the problem by first trying to uninstall the npm globally, update the npm, clear the cache then using npx command to create React app.
The command is as below:
npm uninstall -g create-react-app && npm i -g npm@latest && sudo npm cache clean -f && npx create-react-app my-app
This is taken from one of the Stack Overflow posts.
https://stackoverflow.com/questions/64963796/create-react-app-is-not-working-since-version-4-0-1/65043610

it isn't working for me, please help nothing is working for me

@1-pro: Can you share more details on the error messages you got?

I am able to solve the problem by first trying to uninstall the npm globally, update the npm, clear the cache then using npx command to create React app.
The command is as below:
npm uninstall -g create-react-app && npm i -g npm@latest && sudo npm cache clean -f && npx create-react-app my-app
This is taken from one of the Stack Overflow posts.
https://stackoverflow.com/questions/64963796/create-react-app-is-not-working-since-version-4-0-1/65043610

it isn't working for me, please help nothing is working for me

==================================
First Time -> I Found Error (Use Git Bash)
$ npx create-react-app test
Creating a new React app in C:\React_TEE\test.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/type-fest
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/ansi-escapes
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/jest-watch-typeahead
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!       node_modules/react-scripts
npm ERR!         react-scripts@"" from the root project
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@jest/core
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!       node_modules/jest
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!         node_modules/react-scripts
npm ERR!         1 more (jest-watch-typeahead)
npm ERR!       1 more (jest-cli)
npm ERR!     2 more (jest-watcher, terminal-link)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>from @pmmmwh/react-refresh-webpack-plu
<EMAIL_ADDRESS>npm ERR! node_modules/@pmmmwh/react-refresh-webpack-plugin
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/react-scripts
npm ERR!     react-scripts@"" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\Miku\AppData\Local\npm-cache\eresolve-report.txt for a ful
l report.
npm ERR!      C:\Users\Miku\AppData\Local\npm-cache_logs\2021-01-29T19_19_32_095
Z-debug.log
Aborting installation.
npm install --save --save-exact --loglevel error react react-dom react-scripts
cra-template has failed.
Deleting generated file... package.json
Deleting test/ from C:\React_TEE
Done.
npm ERR! code 1
npm ERR! path C:\React_TEE
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c create-react-app test
npm ERR!      C:\Users\Miku\AppData\Local\npm-cache_logs\2021-01-29T19_19_32_148
Z-debug.log
==================================
I Fix Error (Use Git Bash)
npm uninstall create-react-app
npm uninstall -g create-react-app
npm i -g npm@latest
npm cache clean -f
npx create-react-app my-app
.
.
.
Happy hacking!

==================================
First Time -> I Found Error (Use Git Bash)
$ npx create-react-app test
Creating a new React app in C:\React_TEE\test.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/type-fest
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/ansi-escapes
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/jest-watch-typeahead
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!       node_modules/react-scripts
npm ERR!         react-scripts@"" from the root project
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@jest/core
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!       node_modules/jest
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!         node_modules/react-scripts
npm ERR!         1 more (jest-watch-typeahead)
npm ERR!       1 more (jest-cli)
npm ERR!     2 more (jest-watcher, terminal-link)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>from @pmmmwh/react-refresh-webpack-plu
<EMAIL_ADDRESS>npm ERR! node_modules/@pmmmwh/react-refresh-webpack-plugin
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/react-scripts
npm ERR!     react-scripts@"" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\Miku\AppData\Local\npm-cache\eresolve-report.txt for a ful
l report.
npm ERR!      C:\Users\Miku\AppData\Local\npm-cache_logs\2021-01-29T19_19_32_095
Z-debug.log
Aborting installation.
npm install --save --save-exact --loglevel error react react-dom react-scripts
cra-template has failed.
Deleting generated file... package.json
Deleting test/ from C:\React_TEE
Done.
npm ERR! code 1
npm ERR! path C:\React_TEE
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c create-react-app test
npm ERR!      C:\Users\Miku\AppData\Local\npm-cache_logs\2021-01-29T19_19_32_148
Z-debug.log
==================================
I Fix Error (Use Git Bash)
npm uninstall create-react-app
npm uninstall -g create-react-app
npm i -g npm@latest
npm cache clean -f
npx create-react-app my-app
.
.
.
Happy hacking!

I've tried all of these. My message keeps saying I'm using 4.0.1 but need 4.0.2 and to uninstall globally. When I uninstall globally, it says a message like "up to date in " and the message still pops up when I run npx create-react-app.
Further more, the folder ". ~/.npm/_npx//node_modules" does not exist and so I can't delete the create-react-app file

For me I got the same error even though create-react-app was installed in a parent directory, not globally. So I ran npm uninstall create-react-app without the -g flag and it worked.

This worked for me as well

npx create-react-app@latest your-project-name --use-npm  really works (https://stackoverflow.com/a/65185822/11821819)

I tried several times using the npm uninstall and each time the subsequent create-react-app failed.
The solution for me was to use:      yarn global remove create-react-app

I tried all these things and nothing was working.
Then I did npm list and realized I had a rogue node_modules/ and package.json in my parent folder which hosts all my projects. (A result of some careless npming )  🤦
Removing that solved it all. Good luck everyone.

I had all of the same problems.  Above someone had the answer: I went into ~/.npm/_npx//node_modules and deleted the create-react-app directory specifically. Then, just to be very sure, I also manually edited ~/.npm/_npx//package.json and set the version for create-react-app to 4.0.1, even though it was marked with a carrot already.
This worked.

In my case, I don't know why but I had a node_modules folder inside my home directory (~/), I had to delete this folder and the package.json inside it and npx create-react-app worked again.

For me I got the same error even though create-react-app was installed in a parent directory, not globally. So I ran npm uninstall create-react-app without the -g flag and it worked.

Worked for me. Thank you!

npx create-react-app@latest your-project-name --use-npm
This command worked for me on Mac pro terminal

$ npx create-react-app my-app
You are running create-react-app 4.0.0, which is behind the latest release (4.0.1).
We no longer support global installation of Create React App.
Please remove any global installs with one of the following commands:

npm uninstall -g create-react-app
yarn global remove create-react-app

The latest instructions for creating a new app can be found here:
https://create-react-app.dev/docs/getting-started/
npm ERR! code 1
npm ERR! path C:\Users\User\Desktop
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c create-react-app my-app
npm ERR!  C:\Users\User\AppData\Local\npm-cache_logs\2020-11-23T18_27_48_723Z-debug.log

Thanks 👍

You are running create-react-app 4.0.2, which is behind the latest release (4.0.3).
We no longer support global installation of Create React App.
always like this? why make thing like that, before is ok, why make so much unnessary change?

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

Worked for me too. Thanks!

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app
Worked for me too. Thanks!

Just run npm i -g<EMAIL_ADDRESS>Here, my error was quite same except for version which was 4.0.3
I think this work on MacBook M1 too

I solved this using the following command.
npm uninstall -g create-react-app
npm cache clean --force
then
npx create-react-app project_name --template all
Thanks for this! Worked for me too.

I happened to stumble upon this error in the LTS version.
Solved the issue by updating the create-react-app to the latest 4.0.3.
npm i create-react-app@latest.
Hooray! everything goes well afterwards.

Thanks all of you for your contribution 👍🤗

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

So let me get this straight. The solution to the problem is to do the very thing npm told you not to do anymore?

First, you'll need to uninstall "create-react-app" using the "npm uninstall -g create-react-app" command.
Run "npx create-react-app my-app" each time you want to create a new React app.
Hope you find this helpful

Thank you, this worked for me.
I don't know why in official page recommend uninstall the package.
Anyway I needed installed again with npm

You all save my time i have fixed it tnx all!

I happened to stumble upon this error in the LTS version.
Solved the issue by updating the create-react-app to the latest 4.0.3.
npm i create-react-app@latest.
Hooray! everything goes well afterwards.

Essentially updating the current create-react-app inside the parent repo worked for me as well.
npm uninstall -g create-react-app
npm cache clean --force
npm i create-react-app@latest
then
npx create-react-app my-app

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

Thank you worked for me also.

completely deinstall node.js  and install new worked for me. Thanks.

I had to open the node cli and type in 'npx create-react-app' to get it working..., then I moved the resultant folder "myApp" to my desired destination.

Resolví esto usando el siguiente comando.
npm uninstall -g create-react-app
entonces
npm install -g create-react-app

your are teh best

npx create-react-app@latest your-project-name --use-npm  really works (https://stackoverflow.com/a/65185822/11821819)

you sir are a legend i swear

sudo npm install -g  create-react-app  --allow-root  is work for me

If you're having trouble and don't want to waste more time, remove the entire npx cache for the current user (on linux/mac: rm -rf ~/.npm/_npx).
You can find the root npm cache directory path (that contains _npx directory) by using: npm config get cache

npx<EMAIL_ADDRESS>my-app
Hope this works for now.

instead of version i wrote “latest” and works like a charm i guess it will work anytime since it loads latest version
Sent from my iPhone

On 20. Dec 2021, at 03:42, krishna0999 @.***> wrote:

npx @.*** my-app
Hope this works for now.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

worked for me!!✌✌👍

I solved the create-react-app issue using,
npm uninstall -g create-react-app

then
npm install -g create-react-app

Here's the snapshot of the same,

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

Thanks @imrishav 👍

i tried litteraly all codes here and nithing went untill i found that code with latest in it i was going mad 😂
Sent from my iPhone

On 21. Dec 2021, at 07:45, Nitesh Sharma @.***> wrote:

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app
Thanks @imrishav 👍
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.

thanks!

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

This worked for me! Thanks @imrishav

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

Thanks for sharing! This commands worked for me.
After uninstalling 'create-react-app', I was prompted with the following type of error:
npm ERR! try running the command again as root/Administrator
So I just added sudo at the beginning of the command like so:
sudo npm install -g create-react-app

One Solution that worked for me is removing npm-cache folder from %AppData%
I removed npm-cache folder from 2 places. %AppData%/Roaming/npm-cache & %AppData%/Local/npm-cache

For me, it was something called tar .exe in npm. It was an outdated version of 2.2.2. I solved it by installing it again using the npm i tar command

Yes, it worked. Thanks!

If we use npm 5.1 or earlier, then we can't use npx.
Instead we can install create-react-app globally:
npm install -g create-react-app

Now we can run this command:
create-react-app my-app

npx comes with 5.2+ and higher:
And if we've previously installed create-react-app globally via :
npm install -g create-react-app:-
we need to uninstall the package using :
npm uninstall -g create-react-app
or
yarn global remove create-react-app
so as to ensure that npx always uses the latest version, since npx comes with npm 5.2+ and higher.

I'm facing difficulty in creating react app on windows 7. could anyone please help?

I'm facing difficulty in creating react app on windows 7. could anyone please help?

I've seen it wont work if you have . Or " or ' somewhere on folder name. Check if you have them in any parent folders.

I'm facing difficulty in creating react app on windows 7. could anyone please help?

I have the same problem, to add more info, in windows 7, the latest version for node supported its 13.6.0 and since create-react-app needs node 14, we can not run this command.
is there any workaround about this? tried -> npx<EMAIL_ADDRESS>web --template typescript, but doesn't work either

Just a heads up, one more think I had to do on Mac was remove package.json from my ~/.npm/_npx folder. For some reason, there was a package.json in there that just said
 "dependencies": {
   "create-react-app": "^4.0.3"
 }
}```

Once I deleted that file I was able to run `npx create-react-app my-app` no problem.

Hope this helps someone!

It may sound really dumb, but try running your terminal with admin privileges

Hey guys, I think it's unanimous the uninstall and reinstalling create-react-app works like a charm. It certainly
worked for me.
Happy coding

Oh....I forgot to give props to @imrishav
Thanks @imrishav

I have had this issue on node v14 on Mac OS. Running npm uninstall -g create-react-app and then using npx would still give the message A template was not provided. This is likely because you're using an outdated version of create-react-app.
I resolved it by following the steps here:
https://github.com/facebook/create-react-app/issues/8097
Adding here in case it helps someone.

Try this npx create-react-app@latest your-project-name --use-npm it works for me

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

Thanks for sharing!!!!

Try this npx create-react-app@latest your-project-name --use-npm it works for me

This is the cleanest solution that worked for me, thanks @gurjeetsinghvirdee

If npx create-react-app is not working then do this
npm uninstall -g create-react-app
npm install -g create-react-app
npx create-react-app my-app
cd my-app
npm start

I tried several times using the npm uninstall and each time the subsequent create-react-app failed. The solution for me was to use: yarn global remove create-react-app

This finally worked for me

I'll add that npx create-react-app@latest your-project-name did the trick for me. Didn't need the --use-npm flag.

npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! errno ERR_SOCKET_TIMEOUT
npm ERR! network Invalid response body while trying to fetch https://registry.npmjs.org/electron-to-chromium: Socket timeout
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
npm ERR!      C:\Users\лрроопр\AppData\Local\npm-cache_logs\2022-07-25T19_13_34_028Z-debug-0.log
Can you help me?
I have that error

or it show me that
npm ERR! code ECONNRESET
npm ERR! syscall read
npm ERR! errno ECONNRESET
npm ERR! network Invalid response body while trying to fetch https://registry.npmjs.org/scheduler: read ECONNRESET
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
npm ERR!      C:\Users\лрроопр\AppData\Local\npm-cache_logs\2022-07-25T19_43_33_201Z-debug-0.log

or it show me that
npm ERR! code ECONNRESET npm ERR! syscall read npm ERR! errno ECONNRESET npm ERR! network Invalid response body while trying to fetch https://registry.npmjs.org/scheduler: read ECONNRESET npm ERR! network This is a problem related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR!  C:\Users\лрроопр\AppData\Local\npm-cache_logs\2022-07-25T19_43_33_201Z-debug-0.log

Try this
Source: Stackoverflow

just don't use npx for create-react-app.

hi, i have try everything here, but nothing work for me :( i have a vps running with debian 11, some idea?

maybe the network

I have tried these all method but could not working, any other solution for it

Use a different network: For example, you can try connecting to a different Wi-Fi network or using a mobile hotspot.
Hope this should help you.This Works For me.

I have tried these all method but could not working, any other solution for it

Use a different network: For example, you can try connecting to a different Wi-Fi network or using a mobile hotspot.
Hope this should help you.This Works For me.

yessss yesssss yesssssss yahhhoooooooo!!!!!! its working thanks you soooo much for savingggggg im so exited got emotionallll

Also worked for me
npm uninstall -g create-react-app
then
npm install -g create-react-app

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

Best Solution, work for me, try this one.

Я решил это, используя следующую команду.
npm uninstall -g create-react-app
затем
npm install -g create-react-app

i love u   <3

I solved this using the following command.
npm uninstall -g create-react-app
then
npm install -g create-react-app

I had a similar issue too.
npm ERR! code ENOENT
npm ERR! syscall lstat
npm ERR! path C:\Users\USERNAME\AppData\Roaming\npm
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, lstat 'C:\Users\USERNAME\AppData\Roaming\npm'
npm ERR! enoent This is related to npm not being able to find a file.

This solution resolves my issue too.. Thank you for sharing ❤

$ npx create-react-app my-app
You are running create-react-app 4.0.0, which is behind the latest release (4.0.1).
We no longer support global installation of Create React App.
Please remove any global installs with one of the following commands:

npm uninstall -g create-react-app
yarn global remove create-react-app

The latest instructions for creating a new app can be found here: https://create-react-app.dev/docs/getting-started/
npm ERR! code 1 npm ERR! path C:\Users\User\Desktop npm ERR! command failed npm ERR! command C:\Windows\system32\cmd.exe /d /s /c create-react-app my-app
npm ERR!  C:\Users\User\AppData\Local\npm-cache_logs\2020-11-23T18_27_48_723Z-debug.log

I have tried these all method but could not working, any other solution for it

Just create a new folder and name it "npm" inside the C:\Users\USERNAME\AppData\Roaming directory. Here's a guide exactly showing that - https://ripixel.org/npx-create-react-app-not-working/

npm install -g create-react-app

Thanks worked for me too

This is what is happening for me, does anyone know how to fix it?

try npm create-react-app my-app

try npm create-react-app my-app

This outputted Unknown command: "create-react-app"


The xo.executeAutofix command doesn't work

When running :CocCommand xo.executeAutofix the [coc.nvim] Failed to apply ESLint fixes to the document. Please consider opening an issue with steps to reproduce. error appears. I suspect this is due to the applyAllFixes command not being implemented in the XO server but I don't know enough about coc extensions to know for sure.

Thanks for reporting and that's true the command of xo.executeAutofix won't work.
I personally don't have enough time to implement these functionalists, to be honest.
Try :CocFix instead, it works to apply auto-fix one by one though. Or a contribution will be welcomed.


10/25 features that sponsor wanted

Ability to manually override and insert their own users into taken slots
Ability to mark users as "no show"

Tacking on the ability to reset passwords onto this ticket.

Also tacking on the ability for the user to change their state.

Completed and merged into MR #37