Very Weird Phaser Bug

Not sure what is going on, but sometimes when you refresh everything is all smooth and works like butter. But then sometimes when u refresh everything is all glitchy, and laggy? It does this on the latest chrome and opera and Firefox.
I've made a video to try to explain, although you cannot really tell because the screen recorder is shit and tears the screen too, but it's much noticeable on my side.
https://www.youtube.com/watch?v=8_j1T6Zauec&feature=youtu.be
And yes, it does this without recording the screen.
Here is my code (if it helps):
var game = new Phaser.Game(1280, 720, Phaser.AUTO, 'phaser-example', { preload: preload, create: create, update: update,   render: render });

function preload() {
	//game.load.spritesheet('GameSprite', '../img/gsprite.png');
	game.load.atlasJSONHash('GameSprite', '../img/gsprite.png', 'gsprite.json');
	game.load.image('background','./images/debug-grid.png');

}

var Player;
var tween;
var button;
var dashingLeft = false;

function create() {
    game.stage.backgroundColor = '#182d3b';

    game.add.tileSprite(0, 0, 1920, 1920, 'background');
	game.world.setBounds(0, 0, 1920, 1920);

	game.physics.startSystem(Phaser.Physics.P2JS);

    var style = { font: "32px Arial", fill: "#ff0044"};
    var PlayerPositionX = 0;
	var PlayerPositionY = 0;

	 Player =  game.add.sprite(game.world.centerX, game.world.centerY, 'GameSprite', 'PlayerMale');

	game.physics.p2.enable(Player);

	/*
    button = game.add.button(game.world.centerX - 95, 400, 'button', actionOnClick, this, 'over', 'out', 'down');
    button.onInputOver.add(over, this);
    button.onInputOut.add(out, this);
	*/
	cursors = game.input.keyboard.createCursorKeys();
	game.camera.follow(Player, Phaser.Camera.FOLLOW_PLATFORMER);

    game.input.onDown.add(moveSprite, game.world);

}

function update(){
	Player.body.setZeroVelocity();
	/*
	 if ( dashingLeft && (oldPos - Player.x < 100)  ) {  // 100 would be the length of your dash move
    Player.body.velocity.x = -500;  // or something some other dashing speed
  } else {
    dashingLeft = false;
  }
  */

}

function render() {

    game.debug.cameraInfo(game.camera, 32, 32);
    game.debug.spriteCoords(Player, 32, 500);

}

function moveSprite (pointer) {

    if (tween && tween.isRunning)
    {
        tween.stop();
    }

    //sprite.rotation = game.physics.arcade.angleToPointer(sprite, pointer);

    //  300 = 300 pixels per second = the speed the sprite will move at, regardless of the distance it has to travel
    var duration = (game.physics.arcade.distanceToPointer(Player, pointer) / 200) * 1000;

	//Player.body.x =  pointer.worldX;
	//Player.body.y =  pointer.worldY;

		tween = game.add.tween(Player.body).to({ x: pointer.worldX, y: pointer.worldY }, duration, Phaser.Easing.Cubic.Out, true);

}

Edit: I've removed the text as well and it still does it.

Does the observed performance behavior change between different versions of Phaser?
Usually such jumps are caused by GC or other resource cleanup; it also takes some time for browsers to collect stats and optimize/jit code.

Not that I know of, I was using an older version before I upgraded to the recent because I thought it could be the issue.
Nah the weird lag / glitchy effect stays after the refresh until another refresh. Sometimes I will get a good refresh and it works smooth as butter, and sometimes the total opposite.

Curious, I would not expect the lab to persist.

Okay.
I didn't add my graphics  (copyright issues atm)
But, in any event you can still see the lag when moving on certain refreshes, it's very noticeable.
http://codepen.io/anon/pen/dYvWaL

Sorry for the double post, but this is important.
As you said, you wouldn't expect the lag to persist, which is true because on some refreshes you can see the text blink for like 500ms then it stops everything becomes smooth/rendered.
But, I think I can narrow down the bug more, it's right after that certain 300-500ms of blinking, it doesn't stop and just continues.   Hope this helps? Not sure I have no where to start as I'm trying to convert my dom game to phaser, not versed in phaser at all :(

Are you still seeing it if you change the renderer to Phaser.CANVAS? Are you still seeing it if you take the debug text out of the render method? (try separately, try on a different computer)

@drhayes
Removing the text doesn't make a difference.
Changing the renderer to Phaser.CANVAS does fix the glitchyness but my animations are all very glitchy still.
Changing the renderer to Phaser.WebGL makes my animations very smoother but only works on a certain refresh.
So bug is isolated now for rendering under Phaser.WebGL, (if this is related to Phaser?) If not, it's probably a WebGL issue.

FWIW: I am not seeing the behavior in Android Chrome - here it always runs terrible at the start (I think it might be breaking through the frame skip) and then settles down. The codepen version appears to start with worse performance.

Actually I've seen this happen as well. It never happens on my PC, but on my Macbook Pro it's pretty consistent and will happen about 1 in 2 refreshes, it doesn't matter if it's canvas or webgl either.
There are two separate issues. One is when the updateLogic fires but with no render call. This has the effect of calling preUpdate on all subsystems. In some cases that blanks them - for example the Debug class's preUpdate erases the canvas it uses entirely. If render is then skipped it causes the Debug canvas to be blank for a single frame, usually coming back again in the next one. But it causes a 'flickering' effect (as it happens so quickly).
The second issue is with the frame skip logic on some systems. The actual concept behind the frame skip code is sound, and based on industry 'best practises'. However I'm pretty certain what happens is that the browser struggles at the start, most likely due to the large gc sweep that happens, but then is constantly 'behind' where the frame skip expects it to be. I think this picture from the Game Design Patterns book sum's it up well:

I'm pretty certain that what happens is the timer gets thrown out early on, so is in a constant never-ending state of 'catch up', doing double updates and no renders constantly, causing the effect we're seeing.
On my Macbook if I do 'Game.forceSingleUpdate = true' then it runs smooth as butter every time. On my PC it doesn't need it. On a slow device that can be quite dangerous, so it's sort of a 'middle ground' area where it's a problem.

it doesn't matter if it's canvas or webgl either. That's odd. For my PC, (Win 7, 64 bit), fx 6300, gtx 460 hawk (if this matters), it only does it when the game is rendered in webgl. I tried it when the renderer was set to Canvas and it works fine but the tweening and some animations are not as smooth (why I love the webgl).

Edit: Wow, I added
function update(){
	game.forceSingleUpdate = true
}

and I'm using Phaser.WebGL and it's working 100% now as well.  Thanks for that. I'll update my thread on the html5dev forums.

Closing this one off as there's no clear-path to doing anything more for it, without rewriting how Phaser works internally (which is what Lazer is all about).


Invalid ID?

Is the leading 4 in AMSD ID 4PRM1989.46.9 a typo?

it seems so - but these amsd_ids won't be used as id within database

It's a typo.
The AMSD ids are only for some but not all of the artefacts. I developed
them as a way of quickly citing individual entries in academic papers, so
that I didn't have to use a DOI.
On Wed, 6 Feb 2019 at 15:35, Hans-Jörg Bibiko<EMAIL_ADDRESS>wrote:

it seems so - but these amsd_ids won't be used as id within database
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/clld/amsd-data/issues/8#issuecomment-461044638, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJQdrrS810zZDpnKTn-FNs6l_GnORtkxks5vKugxgaJpZM4alW2Q
.

@Bibiko considering what @perezkelly says, it seems they should be used as ID in the database, no?

they will be stored in the database as normal info field but they won't used as internal primary keys since there are only a few of such amid_ids yet

Primary keys are always integers an not exposed from the web app in clld apps. The id column on the other hand is a unique string which can be used as URL component, and is exposed as the primary, linkable identifier of a record. Since all resources require such an ID, we'd have to make one up anyway. Why not use amsd_id in the cases it is defined?

Hmm, since I don't have access to research assistants at the moment it
would take me a long time to generate IDs. Is there some way an ID could be
automatically generated? At least for now? I will fix the dual entry of
ILI1948P102F3
On Wed, 6 Feb 2019 at 16:52, Hans-Jörg Bibiko<EMAIL_ADDRESS>wrote:

ok - of course - then the dots within these amid_ids should be replaced by
underscores as in PMH305470_D3450.1 PMH305470_D3450.2 etc. @perezkelly
https://github.com/perezkelly 948 amsd_ids are missing, and
ILI1948P102F3 occurs twice (not unique ids). How difficult would it be to
add those?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clld/amsd-data/issues/8#issuecomment-461074331, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJQdrhnIrUXbMjDyfBiA6RPTex6R8z3Wks5vKvpDgaJpZM4alW2Q
.


Allow passthrough of a singleton ratelimit object.

Also Allows custom rate periods, as well as disabling / bypassing the rate limiter.

Looks good, thanks again!


After pulling the new code, there was an error in creating the index

code:
  $builder=new \MacFJA\RediSearch\IndexBuilder();
            $res=$builder->setIndex($this->name)->addPrefixes($this->name.'1:')

                ->addTextField('lastname',false,null,null,true,true)
                ->addTextField('firstname',false,null,null,true,true)
                ->addNumericField('age',true,true)
                ->create($this->clientPhprearch);

is error:
\vendor\macfja\redisearch\src\Redis\Client\PhpredisClient.php line 55
Unknown Index name
   public function execute(Command $command)
    {
        $arguments = $command->getArguments();
        if (0 === count($arguments)) {
            /** @psalm-suppress TooFewArguments */
            $rawResponse = $this->redis->rawCommand($command->getId());
        } else {
           $rawResponse = $this->redis->rawCommand($command->getId(), ...$arguments);// errors
        }

        return $command->parseResponse($rawResponse);
    }

The syntax I wrote is wrong, it's not the program's problem


Added commands dump, drop, load and lsinfo.

Ok - version number and rm override updated.

Thanks!  👍


add a funny joke

Short description of what this resolves:
I added a funny joke to jokes.json
Changes proposed in this pull request:

Fixes: #

Thank you for taking the time to contribute! This is sincerely appreciated. 😇
(Powered by GitMate.io)

Thanks @Bilalharoon! 👍


ci: add job to test build and create release

Depends-On: #11

This pull request is part of a stack:

fix: introduce new sendInstallState attributes (#11)
ci: add job to test build and create release (#12) 👈

@mergify queue


fix a warning from lgtm

by removing two lines of codes, probably wrong duplicate of the next two lines

No, not duplicates. Note the indentation.

well, but the "else"  does not make sense in a for loop that has no break...

Ok, so the else could be removed, but not its code block.
The current code is not wrong, though. Either something is found and returned, or else we show an error. I probably wouldn't spell it that way if I were to write that code, but since it's there now, I'd leave it as it is.
Thanks for your input.


Please don't use short tags

http://softwareengineering.stackexchange.com/questions/151661/is-it-bad-practice-to-use-tag-in-php

I think it would be better to use {!! $variable !!} instead.

Is the same. I prefer php but is a choise.

It's not the same, it's the laravel way of writting unescaped content https://github.com/laravel/framework/blob/5.4/src/Illuminate/View/Compilers/Concerns/CompilesEchos.php#L42
Personally, I prefer blade syntax over pure php on blade views for obvious reasons. Besides that, blade prepares raw content, unlike simply <?php echo ... ?>.
This is a small improvement, but can be turned a serious coding style problem in future versions.

@Frondor is and admin, and for this case in particular is a content field. maybe the @marktopper solution is better...

That's what I meant.


adds support for input type search

I'm not sure which files I needed to update, so I updated all instance of it.
fixes #1746

@ryanvaness ,
Thank you !


CBH and HR nav bar created

Issue = [1|CBH & HR - Nav Bar] Breadboard #83
Basic HTML and CSS used

I work with @mariannalf


simple example doesn't run

Watching your simple example video, I tried the examples given there, but nothing happens:
 auto-changelog --unreleased
Usage: auto-changelog [options]

or
 auto-changelog --latest-version 0.1.6
Usage: auto-changelog [options]

I installed auto-changelog via pip, version 0.1.7.

My apologies.
I'm aware of this, I updated Readme for 0.3.0, which I planned to release yesterday, but trying to do it in the middle of the night, tired, breaking multiple things in process..

0.3.0 released 🎉


feat: refactor AWS and identity pool clients to use suppliers

Refactors AWS and identity pool client types to use suppliers to get subject tokens and AWS security credentials. Moved internal implementations out of the client classes into stand alone supplier classes. Follow up PR will add support for custom suppliers in the client constructors.

Looks good so far; a few things + tests would wrap things up

What tests are you looking for? Since the new files are the same logic as the existing AWS/Identity pool clients, they already have coverage from the existing tests.

Looks good so far; a few things + tests would wrap things up

What tests are you looking for? Since the new files are the same logic as the existing AWS/Identity pool clients, they already have coverage from the existing tests.

Fair point; from a coverage standpoint this should all be the same. Tests would be useful for the follow-up PR.

Looks good so far; a few things + tests would wrap things up

What tests are you looking for? Since the new files are the same logic as the existing AWS/Identity pool clients, they already have coverage from the existing tests.

Fair point; from a coverage standpoint this should all be the same. Tests would be useful for the follow-up PR.

Yep, the next PR will include unit tests around suppliers used to instantiate the clients


Consider switching from mmap to memmap

memmap is actually maintained.
https://github.com/danburkert/memmap-rs

Hmm, yeah indeed. Thanks for pointing this out.
I'll tackle this as soon as I have some time, it should be pretty straightforward.

Hmm... After some digging, I can't find a way to create a memory-map from a linux file descriptor in memmap-rs, which is exactly the feature I'm using in mmap: https://github.com/vberger/wayland-kbd/blob/master/src/mapped_keyboard.rs#L153-L156

@danburkert Nudge, nudge.

Wait, you can do this already. On unix platforms you have FromRawFd impl'd on File so you can use that to get a File which you can then pass to memmap.

Yah the Mmap::open_with_offset function should work.  That being said, I've never tested against non-file-backed 'files'.

Fair point. I'll try this tomorrow.

@vberger Did you ever look into this? Did it end up being non-trivial?

Hmm, kinda forgot this, sorry for that...
I won't have time to spend on it for the next two weeks unfortunately... :-/

I won't have time to spend on it for the next two weeks unfortunately... :-/

All good!
Opened a PR for this whenever you have time: https://github.com/vberger/wayland-kbd/pull/9


odo support

Hello,
I'm totally new to xray.
I wonder if xray have odo support
http://odo.readthedocs.org/
Kind regards

@mrocklin, @cpcloud, @izaid and myself have discussed this, a little bit online and mostly offline.
The trouble is figuring out how to map the xray datamodel into odo. The datashape project, which odo relies on, currently lacks any support for named axes, which makes fitting xray objects into datashape a little awkward. Likewise, xray has tick labels, which don't exist in most odo datatypes. I'm certainly not opposed to adding xray to odo, but it would need some opinionated design choices which are not immediately obvious to me.
Generally, I recommend taking a look at xray's tools for converting to/from pandas and using pandas as intermediate data structure for converting to and from other formats.


EVP: allow empty strings to EVP_Decode* functions

This is a simple check order correction.
Fixes #12143

I've checked; this PR cherry-picks cleanly in 1.1.1

Setting ready-to-merge directly, since Pauli's review is more than 24 hours old.

Merged to master and 1.1.1.


v6.2.2 binary not working in Windows

Summary of Problem

What are you trying to do?

Using serialport as a dependency in my electron project, I'm developing on MacOS and building bundles for Linux and Windows.  I was using ^6.2.0 for serialport version.

What happens?

I recently re-ran yarn to upgrade some dependencies, and serialport was bumped up to v6.2.2.  This seems to work fine on the Mac.  But when I built a Windows 64 bit package and tried to run it, it exits immediately and I see this error in the log:
error: uncaughtException: \\?\C:\Users\partap\AppData\Local\Temp\b4b31dd3-0edf-4688-a81b-9e877893c1b6.tmp.node
is not a valid Win32 application\\?\C:\Users\partap\AppData\Local\Temp\b4b31dd3-0edf-4688-a81b-9e877893c1b6.tmp.node

What should have happened?

If I back off to v6.2.0 or v6.2.1, the windows executable runs normally.
Code to Reproduce the Issue
As far as I can tell, it breaks at:
var serialport = require('serialport')

Initially I thought that the error was referring to the entire electron binary, but since I saw the error in the log, it seems that the program runs long enough to start up the logger, anyways.
Versions, Operating System and Hardware

<EMAIL_ADDRESS>Node.js v?8.12.0
MacOS building for Windows with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Hardware and chipset? Prolific serial USB adapter

@partap So I think the issue is that a prebuilt binary for serialport-v6.2.2-electron-v57-win32-x64 was never built, where it exists for the v6.2.1 and v6.2.0 releases.
v6.2.2 Release: https://github.com/node-serialport/node-serialport/releases/tag/v6.2.2
I'm looking into ways to create that binary and add it to the release. If you have a Windows system handy, you can try to build from source: https://serialport.io/docs/guide-installation#windows

@HipsterBrown Thanks for the quick response!
Yeah, I tried building my app with v6.2.2 directly on Windows a little while after posting this issue and ran into a message complaining about needing vcbuild.exe or something. So I guessed that there's just not an appropriate binary available.
Last time I installed Visual Studio it wanted about 15GB(!)... This is just a little Windows VM I keep on my Mac for testing, so I'm not trying to double its image size.  I can get by with the older binary for now ;) . Not sure if there's anything I need to update the module for, anyways...
...Unless...I just realized today that the Windows build of my project is not properly detecting CTS or DSR pins with serialport.get().  I'm using them to determine if certain devices are actually connected to the serial port so the program doesn't wait around for a response for a timeout (video projectors...can take over a minutes to respond sometimes if cold).
I was assuming that the problem was with the Windows driver for my USB-Serial adapter, but I got a report from a colleague of this happening on a Windows machine with a native serial port.  This is actually the reason I needed a new Windows build in the first place...to make the CTS/DSR detection optional.
They are actually using a different model of projector than I have access to, so it might just be that it just doesn't set CTS like the same-branded brethren I'm using here, but is it possible that this is an issue with the Windows build of serialport? (and that it's fixed in the one newer patch-level version that I can't use? lol)
I'll be able to do better testing soon once I get some actual Windows hardware hooked up.  If there's an actual problem with serialport.get() I'll open a separate issue.


Initial User Creation

[ ] ask user if they want to create an initial user when first starting up
[ ] provide a command in the docker container itself to add users on the fly

When will this be implemented @greysoh?


[joy-ui] fontSize property on MUI Icons does not comply with TypeScript rules

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example: https://codesandbox.io/p/sandbox/blissful-night-4v3x2j?file=%2Fsrc%2FDemo.tsx (The one available in the offcial "Material UI Icons Size doc")
As you can see, it happens even in the live example codesandbox IDE of the official doc.
Steps:

Include any Material UI Icon in your code. i.e:

import Person from '@mui/icons-material/Person';
...
<Person />

Add it the fontSize property with any of the officially supported sizes (xs, sm, md, lg, xl, xl2, xl3 or xl4):

import Person from '@mui/icons-material/Person';
...
<Person fontSize="xl2" />

You will see the icon size applied, but the code will be highlighted with a TypeScript error telling that the only supported sizes are "small, medium or large", while none of these values actually works if you followed the "Material UI Icons Installation instructions".

Current behavior 😯

Putting the correct values (xs, sm, md, lg, xl, xl2, xl3 or xl4) in fontSize property works, but TypeScript error is raised.
Putting the incorrect values (small, medium or large) in fontSize property doesn't work, but TypeScript likes it.

Expected behavior 🤔

Putting the correct values (xs, sm, md, lg, xl, xl2, xl3 or xl4) in fontSize property works and TypeScript likes it.
Putting the incorrect values (small, medium or large) in fontSize property doesn't work and TypeScript raise an error.

Context 🔦
Just trying to customize the size of icons inside my app with the official fontSize prop to avoid css granular customization.
Your environment 🌎

npx @mui/envinfo
  System:
    OS: Windows 11 10.0.22631
  Binaries:
    Node: 18.17.0 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 9.6.7 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 120.0.6099.111 (Build oficial) (64 bits)
    Firefox: 121.0 (64-bit)
    Edge: 120.0.2210.77 (Compilación oficial) (64 bits)
  npmPackages:
    @emotion/react: ^11.11.3 => 11.11.3
    @emotion/styled: ^11.11.0 => 11.11.0
    @mui/base:  5.0.0-beta.29
    @mui/core-downloads-tracker:  5.15.2
    @mui/icons-material: ^5.15.2 => 5.15.2
    @mui/joy: ^5.0.0-beta.20 => 5.0.0-beta.20
    @mui/material: ^5.15.2 => 5.15.2
    @mui/private-theming:  5.15.2
    @mui/styled-engine:  5.15.2
    @mui/system: ^5.15.2 => 5.15.2
    @mui/types:  7.2.11
    @mui/utils:  5.15.2
    @types/react: 18.2.20 => 18.2.20
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: 5.1.6 => 5.1.6

tsconfig
{
  "compilerOptions": {
    "target": "es5",
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "bundler",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "incremental": true,
    "plugins": [
      {
        "name": "next"
      }
    ],
    "paths": {
      "@/*": ["./src/*"],
      "@mui/material": ["./node_modules/@mui/joy"]
    }
  },
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", ".next/types/**/*.ts"],
  "exclude": ["node_modules"]
}

I think for workaround, you can add:
import type { TypographySystem } from '@mui/joy/styles';

type FontSizeOverrides = { [k in keyof TypographySystem]: true };

declare module "@mui/material/SvgIcon" {
  interface SvgIconPropsSizeOverrides extends FontSizeOverrides {}
}

@siriwatknp Not sure about keys in TypographySystem, as it lists "body-sm", "body-md", etc.
What we want, from joy-ui documentation are sizes from xs to xl4
I managed to workaround the issue, that way:
// global.d.ts
import '@mui/joy/styles';

type SvgIconFontSize = 'xs' | 'sm' | 'md' | 'lg' | 'xl' | 'xl2' | 'xl3' | 'xl4';

type FontSizeOverrides = { [k in SvgIconFontSize]: true };

declare module '@mui/material/SvgIcon' {
  interface SvgIconPropsSizeOverrides extends FontSizeOverrides {}
}

Values from SvgIconOwnProps.fontSize (large/medium/small) are still suggested, but at least, I can put the good ones, without crashing my build.


what is this mean? "model.add(Dense(32,input_dim=16)), now the model will take as input array of shape(,16),and output arrays of shape(,32)",why is (,32)? I think the input_array's output arrays of shape is(,16)??

Please make sure that the boxes below are checked before you submit your issue. Thank you!

[ ] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/fchollet/keras.git --upgrade --no-deps
[ ] If running on Theano, check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps
[ ] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

in keras , the first layer is the first hidden_layer ?

I assume you have a data table (row_numbers, column_numbers)
so , 16 is column numbers ,it must take that as input data (well python counts from 0 by the way).
then right after this "Dense("  comes "32" , this 32 is classes you want to categorize your data.
Frankly speaking, I do not like the way KERAS implement it either. It is confusing. Why don't they do :
model =   Sequential()
model.add(Dense(input_layer_neurons=16, hidden_layer_neurons=32, kernel_initializer='normal', activation='relu'))

It will be easier to understand with a NN image.
Just found an example in this website:
http://keras.dhpit.com/
model.add(Dense(12, input_dim=8, init='uniform', activation='relu'))
It means 8 input parameters, with 12 neurons in the FIRST hidden layer.

thanks franfran

Thanks to @franfran

thanks man!!!!

thats good

Thanks franfran

thank you very much

It will be easier to understand with a NN image.
Just found an example in this website:
http://keras.dhpit.com/
model.add(Dense(12, input_dim=8, init='uniform', activation='relu'))
It means 8 input parameters, with 12 neurons in the FIRST hidden layer.

That image was very helpful. Thanks!

thans franfran


Crash when running app on iOS Simulator Only after updating Xcode to v11.2.1

I get a crash report when running my application on iOS Simulator only
This happened after updating Xcode today to version 11.2.1
Terminal Logs
Launching lib/main.dart on iPhone 11 Pro Max in debug mode...
Running Xcode build...
 ├─Assembling Flutter resources...                           7.0s
 └─Compiling, linking and signing...                         4.4s
Xcode build done.                                           13.3s

Sending crash report to Google.
Crash report sent (report ID: 352fd5eb36ef704a)
Oops; flutter has exited unexpectedly.
Crash report written to /Users/ahmedmehanna/development/projects/gnib/flutter_04.log;
please let us know at https://github.com/flutter/flutter/issues

Crash report
Flutter crash report; please file at https://github.com/flutter/flutter/issues.
command
flutter run -d 1BAE79D2-D4F8-4FA6-9DCF-3ADBEF610C46
exception
ProcessException: ProcessException: Process "/usr/bin/xcrun" exited abnormally:
An error was encountered processing the command (domain=NSOSStatusErrorDomain, code=-54):
The operation couldn’t be completed. (OSStatus error -54.)
Command: /usr/bin/xcrun simctl install 1BAE79D2-D4F8-4FA6-9DCF-3ADBEF610C46 /Users/ahmedmehanna/development/projects/gnib/build/ios/iphonesimulator/Runner.app
#0      runCheckedAsync (package:flutter_tools/src/base/process.dart:259:7)
<asynchronous suspension>
#1      SimControl.install (package:flutter_tools/src/ios/simulators.dart:145:16)
#2      IOSSimulator._setupUpdatedApplicationBundle (package:flutter_tools/src/ios/simulators.dart:437:31)
<asynchronous suspension>
#3      IOSSimulator.startApp (package:flutter_tools/src/ios/simulators.dart:339:15)
<asynchronous suspension>
#4      FlutterDevice.runHot (package:flutter_tools/src/resident_runner.dart:378:54)
#5      _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#6      _rootRunUnary (dart:async/zone.dart:1132:38)
#7      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#8      _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#9      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#10     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#11     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#12     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:552:7)
#13     _rootRun (dart:async/zone.dart:1124:13)
#14     _CustomZone.run (dart:async/zone.dart:1021:19)
#15     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
#16     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
#17     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#18     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#19     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
#20     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

flutter doctor
[✓] Flutter (Channel stable, v1.9.1+hotfix.6, on Mac OS X 10.15.1 19B88, locale en-IE)
    • Flutter version 1.9.1+hotfix.6 at /Users/ahmedmehanna/development/tools/flutter
    • Framework revision 68587a0916 (9 weeks ago), 2019-09-13 19:46:58 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/ahmedmehanna/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio 2.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.2.1, Build version 11B500
    • CocoaPods version 1.8.4

[✓] Android Studio (version 3.3)
    • Android Studio at /Applications/Android Studio 2.app/Contents
    • Flutter plugin version 32.0.1
    • Dart plugin version 182.5124
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[✓] IntelliJ IDEA Community Edition (version 2019.2.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 41.1.3
    • Dart plugin version 192.7402

[✓] VS Code (version 1.40.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.6.0

[✓] Connected device (2 available)
    • Android SDK built for x86 • emulator-5554                        • android-x86 • Android 10 (API 29) (emulator)
    • iPhone 11 Pro Max         • 1BAE79D2-D4F8-4FA6-9DCF-3ADBEF610C46 • ios         • com.apple.CoreSimulator.SimRuntime.iOS-13-2 (simulator)

• No issues found!

Hello @ahmedmehanna !
Thank you for posting an issue.
This issue also looks like a duplicate of the one reported here: #44813.
If you try to follow the steps written in the thread I attached, do you get the same error?

Hi @janmoppel I opened the project with Xcode, the project built successfully but couldn't run
I got the following error
Details

The operation couldn’t be completed. (OSStatus error -54.)
Domain: NSOSStatusErrorDomain
Code: -54
User Info: {
    NSDebugDescription = installForLaunchServices;
    "_LSFunction" = "-[_LSInstaller installApplication:atURL:withOptions:installType:reply:]";
    "_LSLine" = 717;
}

I tried to run old flutter project, I am sure it's working perfect, I got the same error
I can't run the project via iOS Simlulator, it is running only via android emulator
Note
I got this error after updating Xcode to v11.2.1

Can you create a new project in Xcode without any Flutter bits and run it on the simulator?
If not, you are hitting a Xcode or Xcode installation issue, and there's not much Flutter can really do...

Hi @jmagman
I have created a new project by Xcode and run it on Simulator successfully.
After that, I run the flutter app again on the Simulator and it runs successfully finally.
I don't have any idea how the issue is fixed.
So I think you can close the issue.
Thanks


[3.x] Move COREAUDIO_ENABLED check inside AUDIO_DRIVER_COREAUDIO_H block

OK we can do it your way. It's done.

Thanks for the contribution!
As I pointed out on https://github.com/godotengine/godot/pull/87272#issuecomment-1895379562, for the 3.x branch we prefer not to do this kind of style fixes unless they actually solve a problem. It took a lot of effort to improve the code style consistency of the whole codebase in the master branch, and redoing all that work for 3.x wouldn't be worth the effort at this stage.
The change in this commit is correct, but I know there are many other places with similar style inconsistencies which have no incidence on the functionality of the code, as I've fixed them all in the master branch. For this case specifically, you can have a look at #63368. As you can see, more than a thousand lines of code were impacted, so doing it file by file as started in this PR wouldn't be a good option. I wouldn't suggest trying to backport this PR to 3.x, as again this would be more effort than worth (not only to do it, but for maintainers to review it and make sure there's effectively no change in behavior).
I included this change in #87272 because why not, but otherwise I'd advise against trying to tackle other such minor header guard name/comment inconsistencies if they're not actual bugs that change the code logic.


Unable to extract uploader id

01-03-2023 11:12:41 cyril@VSFPC214 (VSFPC214:10.0) ~/Vidéos

youtube-dl https://youtu.be/pzPv6wXnbHc
[youtube] pzPv6wXnbHc: Downloading webpage
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
01-03-2023 11:12:45 cyril@VSFPC214 (VSFPC214:10.0) ~/Vidéos

youtube-dl --verbose https://youtu.be/pzPv6wXnbHc
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--verbose', u'https://youtu.be/pzPv6wXnbHc']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 2.7.17 (CPython) - Linux-5.4.0-135-generic-x86_64-with-Ubuntu-18.04-bionic
[debug] exe versions: ffmpeg 3.4.11, ffprobe 3.4.11, phantomjs 11, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] pzPv6wXnbHc: Downloading webpage
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 815, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 836, in __extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 534, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1794, in _real_extract
    'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 1012, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

#30839.


add install instructions for arch

create an asciinema cast for overview and quick start

Closes #158
Check the following

[x] Keep 100% code coverage
[x] Be properly formatted
[x] Have no linting errors
[x] Documentation changes are included
[x] Include a change file if expected

Additional context
Any additional info that might help get your pull request merged.

@bephinix if you are curious

@miniscruff This should be enough. :)


Android - currentLocation won't update location

calling currentLocation on the android emulator will return the last known location - and if a location is not available (eg if you turned off location and then turned it back on), it will return nothing.
It probably should in should try to get the location rather than failing without trying.
Also - in order to test out different locations I have to go to the maps app after changing the emulator location before currentLocation will pick up on the new location,.
I tried to use singleLocationUpdate on android but had the same issues. In light of the above, what is your advice If I want a single updated location.

+1
Any news about this issue?

I'm having the same issue.

same problem, how to solve?

Same problem. Only workaround I could find was to use continuous location and cancel once it got a result.


Made the getUserMedia standard with MediaStreamHelper.

It was my first time doing fork and pull request, and also I didn't know what Grunt is.
Finally, I understood how should I do, and what it is. XD
From https://github.com/rserota/wad/pull/53

Looks good. Thanks for the contribution!


feat(saas): Replaced next-mdx-remote to fumadocs for docs

#34  👈
main

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

Join @alifarooq9 and the rest of your teammates on  Graphite


Add async-graphql + mongodb examples, and a complete blog example built on Rust and Tide stack.

Add tide/examples/async-graphql.rs: Simple async-graphql example.
Add zzy/tide-graphql-mongodb: Clean boilerplate for graphql services using tide, rhai, async-graphql, surf, graphql-client, handlebars-rust, jsonwebtoken, and mongodb.

Graphql Services: User register, Salt and hash a password with PBKDF2 , Sign in， JSON web token authentication, Change password， Profile Update, User's query & mutation, and Project's query & mutation.
Web Application: Client request, bring & parse GraphQL data, Render data to template engine(handlebars-rust)， Define custom helper with Rhai scripting language.

Add zzy/surfer: the complete blog example, built on pure Rust and Tide stack.

Backend for graphql services using tide, async-graphql, jsonwebtoken, mongodb and so on.
Frontend for web application using tide, rhai, surf, graphql_client, handlebars-rust, cookie and so on.

this looks great, but i'm not convinced this needs to be in the tide repository, as compared to a different repo that's linked from the readme. is there any advantage to including it in this repository directly?


add demonstration of how to add a TechPreview-only option to an enumeration

This comes up when adding new values to a discriminated union for example.
/assign @JoelSpeed

now updated to use the published controller-tools release from the openshift fork.

/lgtm


MEN-2825: Remove references to outdated release_2 artifacts

It goes together with https://github.com/mendersoftware/mender-qa/pull/325


Improve the contributor experience.

Contributors may be having issues when working on the code. We should try to make the contributing getting-started experience as smooth as possible (with setup guides, troubleshooting, etc.).
Examples:

https://github.com/GoogleContainerTools/jib/issues/539#issuecomment-404063543

Please comment with other issues you experienced.

How to build
How to debug
Instructions for importing into different environments (e.g., IntelliJ and Eclipse)

I think this is mostly good now with #655 . Closing.


Issue 216

WIP

normalized the unstaged changes commands in code, environment, and files controllers
show unstaged code, environment, or files in status (no details given)
show tasks run after the latest snapshot

Pull Request Test Coverage Report for Build 835

57 of 66 (86.36%)  changed or added relevant lines in 7 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-1.0%) to 87.426%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

datmo/core/controller/code/code.py
16
17
94.12%

datmo/cli/command/project.py
13
17
76.47%

datmo/core/controller/project.py
18
22
81.82%

Files with Coverage Reduction
New Missed Lines
%

datmo/cli/command/project.py
1
83.17%

Totals

Change from base Build 812:
-1.0%

Covered Lines:
2649

Relevant Lines:
3030

💛  - Coveralls


Fix/lit network must be provided of lit auth client

Description
We should force warn users to provide lit network when initialising lit auth client, and we shouldn't default to cayenne
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

better solution incoming


JSON mode has spurious prints in Python 3

Description
When running CAPA in JSON mode (-j) on a file and redirecting the output to a file, the output contains spurious lines that make the output not valid JSON.
Steps to Reproduce

capa -j <file> > out.json
python -m json.tool out.json

Expected behavior:
Pretty printed JSON.
Actual behavior:
Invalid JSON. The first three lines are:
 is not an ELF
 is not an ELF
 is not an ELF

I think these are from the lief dependency (from SMDA):
https://github.com/lief-project/LIEF/blob/b49786fd039a1cf5173d5e6d02a36481aa730a47/src/ELF/Parser.cpp#L158
Versions
# capa --version
capa 1.4.0

I just built from master (50d55f) so the version string appears wrong.
Additional Information
I think we just need to make sure that LIEF_ERR goes to stderr and not stdout.

Adding lief.logging.disable() after import lief in capa/features/extractors/smda/file.py appears to fix it. I'm not finding a way to specify where lief logs.

But lief.logging is only available through the nightly builds.

ah yeah i think you're right about LIEF
looks like its configured to use STDOUT for logging messages:
https://github.com/lief-project/LIEF/blob/1364f22c78475caaa2d6b7cbe01f74e87cf44c34/src/logging.cpp#L37

im used to logging messages being printed to STDERR, but maybe thats a personal preference. do you think this is something we should report upstream?

Yeah, it seems like something to report upstream. Disabling logging works for now.

Does this issue still persist after the upstream LIEF update?

Fixed when using LIEF master. There's no tagged release yet though so users will encounter this unless they are also using LIEF master.

Fixed when using LIEF master. There's no tagged release yet though so users will encounter this unless they are also using LIEF master.

LIEF 0.11 released yesterday, so we can update and pin the dep

LIEF 0.11 released yesterday, so we can update and pin the dep

https://github.com/danielplohmann/smda/pull/19

https://github.com/danielplohmann/smda/pull/19


Add S2N Client Fuzz Test

Addresses "End to End Client s2n_negotiate Fuzz Test" from https://github.com/awslabs/s2n/issues/378

This one should be easy to merge after the small comments are addressed


fix citation style

as part of the feedback given by the editors, fix the citation style to the one used in the default template.

solved with custom natbib style


Do we need to clip our new input into [0,1] after adding noise ?

Hi @Alan-Qin!
No, no clipping happens after adding noise. Mathematically, the smoothing operation doesn't involve any clipping, and there is no reason why practically this should be done. Hope this answers your question!

Thanks!


I'm delighted to wait for 1.21

I already have a 1.21 server at
sky.hardcoreanarchy.gay

I'm also waiting for version 1.21 of CarpetSkyAdditions. I wanted to be able to use the new automatic crafting table from 1.21 in my skyblock world. Currently I use the AutoCraftingTable Carpet Mod extension, but it is much more limited.

I am also very excited to update my skyblock world to 1.21 and make use of all the great new redstone features and see what new additions come with the mod

1.21.1 version

1.21.1 version

how to install this?

nice

1.12.3 released here
https://github.com/TreeOfSelf/CarpetSkyAdditions-Reborn/


Steps to reproduce
eb init using python 3.7
eb run local
Observed result
2.11.4 running Ruby 2.3 (Puma)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.11.4 running Ruby 2.2 (Puma)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.11.4 running Ruby 2.1 (Puma)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.11.4 running Ruby 2.0 (Puma)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v3.3.4 running Tomcat 8.5 Java 8', 'PermittedFileTypes': ['war', 'zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v3.3.4 running Tomcat 8 Java 8', 'PermittedFileTypes': ['war', 'zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v3.3.4 running Tomcat 7 Java 7', 'PermittedFileTypes': ['war', 'zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v3.3.4 running Tomcat 7 Java 6', 'PermittedFileTypes': ['war', 'zip']}, {'SolutionStackName': '64bit Windows Server Core 2019 v2.5.2 running IIS 10.0', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server 2019 v2.5.2 running IIS 10.0', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server Core 2016 v2.5.2 running IIS 10.0', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server 2016 v2.5.2 running IIS 10.0', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server Core 2012 R2 v2.5.2 running IIS 8.5', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server 2012 R2 v2.5.2 running IIS 8.5', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server Core 2016 v1.2.0 running IIS 10.0', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server 2016 v1.2.0 running IIS 10.0', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server Core 2012 R2 v1.2.0 running IIS 8.5', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server 2012 R2 v1.2.0 running IIS 8.5', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server 2012 v1.2.0 running IIS 8', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server Core 2012 R2 running IIS 8.5', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server 2012 R2 running IIS 8.5', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server 2012 running IIS 8', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.14.3 running Docker 18.09.9-ce', 'PermittedFileTypes': []}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.20.0 running Multi-container Docker 18.09.9-ce (Generic)', 'PermittedFileTypes': ['zip', 'json']}, {'SolutionStackName': '64bit Debian jessie v2.14.3 running Go 1.4 (Preconfigured - Docker)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Debian jessie v2.14.3 running Go 1.3 (Preconfigured - Docker)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Debian jessie v2.14.3 running Python 3.4 (Preconfigured - Docker)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v3.0.0 running Docker', 'PermittedFileTypes': []}, {'SolutionStackName': '64bit Amazon Linux 2 v3.0.0 running Python 3.7', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v3.0.0 running Corretto 11', 'PermittedFileTypes': ['jar', 'zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v3.0.0 running Corretto 8', 'PermittedFileTypes': ['jar', 'zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v0.1.0 running PHP 7.4 (BETA)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v0.1.0 running PHP 7.3 (BETA)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v0.1.0 running PHP 7.2 (BETA)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v0.1.0 running Node.js 12 (BETA)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v0.1.0 running Node.js 10 (BETA)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v0.1.0 running Go 1 (BETA)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v0.1.0 running Ruby 2.7 (BETA)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v0.1.0 running Ruby 2.6 (BETA)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v0.1.0 running Ruby 2.5 (BETA)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.10.4 running Java 8', 'PermittedFileTypes': ['jar', 'zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.10.4 running Java 7', 'PermittedFileTypes': ['jar', 'zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.15.1 running Go 1.14.1', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.6.20 running Packer 1.0.3', 'PermittedFileTypes': []}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.14.3 running GlassFish 5.0 Java 8 (Preconfigured - Docker)', 'PermittedFileTypes': ['zip']}], 'ResponseMetadata': {'RequestId': '810fca50-e016-4de3-8d6b-9497e3bea040', 'HTTPStatusCode': 200, 'date': 'Sat, 18 Apr 2020 18:53:07 GMT', 'RetryAttempts': 0}}
2020-04-18 13:53:08,419 (DEBUG) ebcli.lib.elasticbeanstalk : Solution Stack result size = 70
2020-04-18 13:53:08,433 (DEBUG) ebcli.lib.elasticbeanstalk : Inside list_platform_versions api wrapper
2020-04-18 13:53:08,434 (DEBUG) ebcli.lib.aws : Making api call: (elasticbeanstalk, list_platform_versions) to region: us-west-2 with args:{'Filters': [{'Type': 'PlatformOwner', 'Operator': '=', 'Values': ['self']}]}
2020-04-18 13:53:08,580 (DEBUG) ebcli.lib.aws : API call finished, status = 200
2020-04-18 13:53:08,580 (DEBUG) ebcli.lib.aws : Response: {'PlatformSummaryList': [], 'ResponseMetadata': {'RequestId': '67a8c525-c0f5-4d0b-b76f-97d046e02f43', 'HTTPStatusCode': 200, 'date': 'Sat, 18 Apr 2020 18:53:08 GMT', 'RetryAttempts': 0}}
2020-04-18 13:53:08,587 (INFO) eb : Traceback (most recent call last):
  File "/Users/jhaas/.local/share/virtualenvs/bazze-marketplace-RumDEcI_/lib/python3.7/site-packages/ebcli/containers/factory.py", line 115, in _get_solution_stack
    soln_stk = solution_stack_ops.find_solution_stack_from_string(solution_string)
  File "/Users/jhaas/.local/share/virtualenvs/bazze-marketplace-RumDEcI_/lib/python3.7/site-packages/ebcli/operations/solution_stack_ops.py", line 103, in find_solution_stack_from_string
    raise NotFoundError(alerts['platform.invalidstring'].format(solution_string))
ebcli.objects.exceptions.NotFoundError: Elastic Beanstalk can't find a platform version that matches "Python 3.7 running on 64bit Amazon Linux 2".

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/jhaas/.local/share/virtualenvs/bazze-marketplace-RumDEcI_/lib/python3.7/site-packages/ebcli/core/ebrun.py", line 62, in run_app
    app.run()
  File "/Users/jhaas/.local/share/virtualenvs/bazze-marketplace-RumDEcI_/lib/python3.7/site-packages/cement/core/foundation.py", line 797, in run
    return_val = self.controller._dispatch()
  File "/Users/jhaas/.local/share/virtualenvs/bazze-marketplace-RumDEcI_/lib/python3.7/site-packages/cement/core/controller.py", line 472, in _dispatch
    return func()
  File "/Users/jhaas/.local/share/virtualenvs/bazze-marketplace-RumDEcI_/lib/python3.7/site-packages/cement/core/controller.py", line 472, in _dispatch
    return func()
  File "/Users/jhaas/.local/share/virtualenvs/bazze-marketplace-RumDEcI_/lib/python3.7/site-packages/cement/core/controller.py", line 478, in _dispatch
    return func()
  File "/Users/jhaas/.local/share/virtualenvs/bazze-marketplace-RumDEcI_/lib/python3.7/site-packages/ebcli/core/abstractcontroller.py", line 92, in default
    self.do_command()
  File "/Users/jhaas/.local/share/virtualenvs/bazze-marketplace-RumDEcI_/lib/python3.7/site-packages/ebcli/controllers/local.py", line 64, in do_command
    self.app.pargs.allow_insecure_ssl)
  File "/Users/jhaas/.local/share/virtualenvs/bazze-marketplace-RumDEcI_/lib/python3.7/site-packages/ebcli/containers/factory.py", line 45, in make_container
    soln_stk = _get_solution_stack()
  File "/Users/jhaas/.local/share/virtualenvs/bazze-marketplace-RumDEcI_/lib/python3.7/site-packages/ebcli/containers/factory.py", line 121, in _get_solution_stack
    raise NotFoundError('Solution stack {} does not appear to be valid'.format(solution_string))
ebcli.objects.exceptions.NotFoundError: Solution stack Python 3.7 running on 64bit Amazon Linux 2 does not appear to be valid

Expected result
Should be able to run elastic beanstalk locally in docker.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

OS: MacOS

Add --debug flag to command you are running

Hi @jasonrhaas , thanks for reporting this.
Could you provide the following information?

EB-CLI version
Application region

Thanks

I'm running into the same issue
EB-CLI version: 3.18.0 (Python 3.8.2)
Region: us-east-1

Thank you for the information @rupe120. We are actively investigating this issue.
Could you provide a couple additional pieces of information when you have a chance?

exact commands that were run to reproduce the issue
the value of default_platform in your .elasticbeanstalk/config file

Thanks

eb init --profile sandbox
I chose:

us-east-1 : US East (N. Virginia)
Create new Application
Default application name
Python
Python 3.7 running on 64bit Amazon Linux 2
Yes, setup SSH
Chose my key

eb create -t worker
I chose:

Default environment name
No Spot Fleet
Yes download sample application

eb local run
ERROR: NotFoundError - Solution stack Python 3.7 running on 64bit Amazon Linux 2 does not appear to be valid

The default_platform is "Python 3.7 running on 64bit Amazon Linux 2"

Thanks for the info @rupe120, that is very helpful. I have verified the bug and am working on a fix.
One thing to note, eb local run is not officially supported on Windows. Additionally it only supports docker platforms so "Python 3.7 running on 64bit Amazon Linux 2" will continue to fail once this bug is resolved. More info here.
This bug was introduced in the latest release, so if you would like to continue to use this functionality while waiting for a fix to be released you can downgrade awsebcli to version 3.17.1. If you do this you will need to re-initialize any applications directories that were initialized with 3.18.0.
I will leave this issue open while the fix is pending release.

I switched over to testing this under Ubuntu and I'm getting inconsistent results. I initially had to go all the way back to 3.13.0 before I got a different error message, but then I started receiving the same Solution stack does not appear to be valid message even with that version

This is likely because you did not fully reinitialize the application directory. I should have clarified that more. Just rerunning eb init is not enough, you will need to delete .elasticbeanstalk/config and then rerun eb init.
Alternatively, in this case, you could just change the default_platform value within .elasticbeanstalk/config to null then rerun eb init.

Nulling the platform got me past that error, though I'm still not able to perform a local run
I created a new EB application following the same steps I outlined above with version 3.17.1, and when I tried to perform a local run imediately after I recieved:
ERROR: NotSupportedError - You can use "eb local" only with preconfigured, generic and multicontainer Docker platforms.

Correct, eb local run only works with docker platforms. This is expected behavior.
Please see my previous comment:

Additionally it only supports docker platforms, so "Python 3.7 running on 64bit Amazon Linux 2" will continue to fail once this bug is resolved.

While experimenting with a Multi-container application, I faced the similar issue but downgrading from 3.18.0 to 3.17.1 worked. Thanks @halcarleton

This should be fixed in v3.18.2

Hi @halcarleton and @km2411
I just got this issue on 3.20.0 when running a freshly init'd and create'd app, when I run:
 eb local run --debug
I get:
2022-03-19 19:08:43,660 (INFO) eb : Traceback (most recent call last):
  File "/home/jakub/.local/lib/python3.9/site-packages/ebcli/containers/commands.py", line 286, in _run_live
    return utils.exec_cmd_live_output(args)
  File "/home/jakub/.local/lib/python3.9/site-packages/ebcli/lib/utils.py", line 232, in exec_cmd
    raise CommandError(error_msg, output_str, returncode)
ebcli.objects.exceptions.CommandError: Exited with return code 1

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/jakub/.local/lib/python3.9/site-packages/ebcli/core/ebrun.py", line 62, in run_app
    app.run()
  File "/home/jakub/miniconda3/envs/e39/lib/python3.9/site-packages/cement/core/foundation.py", line 797, in run
    return_val = self.controller._dispatch()
  File "/home/jakub/miniconda3/envs/e39/lib/python3.9/site-packages/cement/core/controller.py", line 472, in _dispatch
    return func()
  File "/home/jakub/miniconda3/envs/e39/lib/python3.9/site-packages/cement/core/controller.py", line 472, in _dispatch
    return func()
  File "/home/jakub/miniconda3/envs/e39/lib/python3.9/site-packages/cement/core/controller.py", line 478, in _dispatch
    return func()
  File "/home/jakub/.local/lib/python3.9/site-packages/ebcli/core/abstractcontroller.py", line 92, in default
    self.do_command()
  File "/home/jakub/.local/lib/python3.9/site-packages/ebcli/controllers/local.py", line 66, in do_command
    cnt.start()
  File "/home/jakub/.local/lib/python3.9/site-packages/ebcli/containers/abstractcontainer.py", line 66, in start
    self._pull()
  File "/home/jakub/.local/lib/python3.9/site-packages/ebcli/containers/abstractcontainer.py", line 122, in _pull
    return commands.pull_img(self._get_full_docker_path())
  File "/home/jakub/.local/lib/python3.9/site-packages/ebcli/containers/commands.py", line 46, in pull_img
    _pull_img(img)
  File "/home/jakub/.local/lib/python3.9/site-packages/ebcli/containers/commands.py", line 215, in _pull_img
    return _run_live(args)
  File "/home/jakub/.local/lib/python3.9/site-packages/ebcli/containers/commands.py", line 288, in _run_live
    _handle_command_error(e)
  File "/home/jakub/.local/lib/python3.9/site-packages/ebcli/containers/commands.py", line 297, in _handle_command_error
    raise CommandError
ebcli.objects.exceptions.CommandError: None

I'm using the demo app in this instruction https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker-eblocal.html and get the error too. Here's the log:
2022-11-11 17:33:32,742 (DEBUG) cement.core.foundation : laying cement for the 'eb' application
2022-11-11 17:33:32,742 (DEBUG) cement.core.hook : defining hook 'pre_setup'
2022-11-11 17:33:32,742 (DEBUG) cement.core.hook : defining hook 'post_setup'
2022-11-11 17:33:32,742 (DEBUG) cement.core.hook : defining hook 'pre_run'
2022-11-11 17:33:32,742 (DEBUG) cement.core.hook : defining hook 'post_run'
2022-11-11 17:33:32,742 (DEBUG) cement.core.hook : defining hook 'pre_argument_parsing'
2022-11-11 17:33:32,742 (DEBUG) cement.core.hook : defining hook 'post_argument_parsing'
2022-11-11 17:33:32,742 (DEBUG) cement.core.hook : defining hook 'pre_close'
2022-11-11 17:33:32,742 (DEBUG) cement.core.hook : defining hook 'post_close'
2022-11-11 17:33:32,742 (DEBUG) cement.core.hook : defining hook 'signal'
2022-11-11 17:33:32,742 (DEBUG) cement.core.hook : defining hook 'pre_render'
2022-11-11 17:33:32,742 (DEBUG) cement.core.hook : defining hook 'post_render'
2022-11-11 17:33:32,742 (DEBUG) cement.core.hook : registering hook 'add_handler_override_options' from cement.core.foundation into hooks['post_setup']
2022-11-11 17:33:32,742 (DEBUG) cement.core.hook : registering hook 'handler_override' from cement.core.foundation into hooks['post_argument_parsing']
2022-11-11 17:33:32,742 (DEBUG) cement.core.handler : defining handler type 'extension' (IExtension)
2022-11-11 17:33:32,742 (DEBUG) cement.core.handler : defining handler type 'log' (ILog)
2022-11-11 17:33:32,742 (DEBUG) cement.core.handler : defining handler type 'config' (IConfig)
2022-11-11 17:33:32,742 (DEBUG) cement.core.handler : defining handler type 'mail' (IMail)
2022-11-11 17:33:32,742 (DEBUG) cement.core.handler : defining handler type 'plugin' (IPlugin)
2022-11-11 17:33:32,743 (DEBUG) cement.core.handler : defining handler type 'output' (IOutput)
2022-11-11 17:33:32,743 (DEBUG) cement.core.handler : defining handler type 'argument' (IArgument)
2022-11-11 17:33:32,743 (DEBUG) cement.core.handler : defining handler type 'controller' (IController)
2022-11-11 17:33:32,743 (DEBUG) cement.core.handler : defining handler type 'cache' (ICache)
2022-11-11 17:33:32,743 (DEBUG) cement.core.handler : registering handler '<class 'cement.core.extension.CementExtensionHandler'>' into handlers['extension']['cement']
2022-11-11 17:33:32,762 (DEBUG) cement.ext.ext_plugin : plugin config dir /etc/eb/plugins.d does not exist.
2022-11-11 17:33:32,762 (DEBUG) cement.ext.ext_plugin : plugin config dir /Users/user/.eb/plugins.d does not exist.
2022-11-11 17:33:32,770 (DEBUG) ebcli.core.hooks : -- EBCLI Version: 3.20.3
2022-11-11 17:33:32,770 (DEBUG) ebcli.core.hooks : -- Python Version: 3.10.8 (main, Oct 13 2022, 10:17:43) [Clang 14.0.0 (clang-14<IP_ADDRESS>)]
2022-11-11 17:33:32,770 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/user/eb-docker-nginx-proxy-master
2022-11-11 17:33:32,773 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/user/eb-docker-nginx-proxy-master
2022-11-11 17:33:32,775 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/user/eb-docker-nginx-proxy-master
2022-11-11 17:33:32,777 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/user/eb-docker-nginx-proxy-master
2022-11-11 17:33:32,779 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/user/eb-docker-nginx-proxy-master
2022-11-11 17:33:32,782 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/user/eb-docker-nginx-proxy-master
2022-11-11 17:33:32,785 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/user/eb-docker-nginx-proxy-master
2022-11-11 17:33:32,788 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/user/eb-docker-nginx-proxy-master
2022-11-11 17:33:32,790 (DEBUG) ebcli.lib.utils : docker --version
2022-11-11 17:33:33,034 (DEBUG) ebcli.lib.utils : Docker version 20.10.20, build 9fdeb9c

2022-11-11 17:33:33,042 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/user/eb-docker-nginx-proxy-master
2022-11-11 17:33:33,045 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/user/eb-docker-nginx-proxy-master
2022-11-11 17:33:33,047 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/user/eb-docker-nginx-proxy-master
2022-11-11 17:33:33,049 (DEBUG) ebcli.lib.elasticbeanstalk : Inside list_platform_branches api wrapper
2022-11-11 17:33:33,049 (DEBUG) ebcli.lib.aws : Creating new Botocore Session
2022-11-11 17:33:33,049 (DEBUG) ebcli.lib.aws : Botocore version: 1.23.54
2022-11-11 17:33:33,058 (DEBUG) ebcli.lib.aws : Creating new Botocore Client for elasticbeanstalk
2022-11-11 17:33:33,141 (DEBUG) ebcli.lib.aws : Successfully created session for elasticbeanstalk
2022-11-11 17:33:33,141 (DEBUG) ebcli.lib.aws : Making api call: (elasticbeanstalk, list_platform_branches) to region: ap-northeast-1 with args:{'Filters': [{'Attribute': 'BranchName', 'Operator': '=', 'Values': ['ECS running on 64bit Amazon Linux 2']}]}
2022-11-11 17:33:33,229 (DEBUG) ebcli.lib.aws : API call finished, status = 200
2022-11-11 17:33:33,229 (DEBUG) ebcli.lib.aws : Response: {'PlatformBranchSummaryList': [{'PlatformName': 'Docker', 'BranchName': 'ECS running on 64bit Amazon Linux 2', 'BranchOrder': '10500', 'LifecycleState': 'Supported', 'SupportedTierList': ['WebServer/Standard', 'Worker/SQS/HTTP']}], 'ResponseMetadata': {'RequestId': '1e28f7ca-619f-430c-9a3d-b310c8bf7c85', 'HTTPStatusCode': 200, 'date': 'Fri, 11 Nov 2022 08:33:32 GMT', 'RetryAttempts': 0}}
2022-11-11 17:33:33,230 (DEBUG) ebcli.lib.elasticbeanstalk : Inside list_platform_versions api wrapper
2022-11-11 17:33:33,230 (DEBUG) ebcli.lib.aws : Making api call: (elasticbeanstalk, list_platform_versions) to region: ap-northeast-1 with args:{'Filters': [{'Type': 'PlatformBranchName', 'Operator': '=', 'Values': ['ECS running on 64bit Amazon Linux 2']}]}
2022-11-11 17:33:33,310 (DEBUG) ebcli.lib.aws : API call finished, status = 200
2022-11-11 17:33:33,311 (DEBUG) ebcli.lib.aws : Response: {'PlatformSummaryList': [{'PlatformArn': 'arn:aws:elasticbeanstalk:ap-northeast-1::platform/ECS running on 64bit Amazon Linux 2/3.2.1', 'PlatformOwner': 'AWSElasticBeanstalk', 'PlatformStatus': 'Ready', 'PlatformCategory': 'ECS', 'OperatingSystemName': 'Amazon Linux', 'OperatingSystemVersion': '2', 'SupportedTierList': ['WebServer/Standard', 'Worker/SQS/HTTP'], 'SupportedAddonList': ['Log/CloudWatch', 'Log/S3', 'Monitoring/Healthd', 'WorkerDaemon/SQSD'], 'PlatformLifecycleState': 'Recommended', 'PlatformVersion': '3.2.1', 'PlatformBranchName': 'ECS running on 64bit Amazon Linux 2', 'PlatformBranchLifecycleState': 'Supported'}], 'ResponseMetadata': {'RequestId': 'a3fc078a-45bb-4097-8a1b-459d41c5601d', 'HTTPStatusCode': 200, 'date': 'Fri, 11 Nov 2022 08:33:33 GMT', 'RetryAttempts': 0}}
2022-11-11 17:33:33,311 (DEBUG) ebcli.lib.elasticbeanstalk : Inside describe_platform_version api wrapper
2022-11-11 17:33:33,311 (DEBUG) ebcli.lib.aws : Making api call: (elasticbeanstalk, describe_platform_version) to region: ap-northeast-1 with args:{'PlatformArn': 'arn:aws:elasticbeanstalk:ap-northeast-1::platform/ECS running on 64bit Amazon Linux 2/3.2.1'}
2022-11-11 17:33:33,447 (DEBUG) ebcli.lib.aws : API call finished, status = 200
2022-11-11 17:33:33,447 (DEBUG) ebcli.lib.aws : Response: {'PlatformDescription': {'PlatformArn': 'arn:aws:elasticbeanstalk:ap-northeast-1::platform/ECS running on 64bit Amazon Linux 2/3.2.1', 'PlatformOwner': 'AWSElasticBeanstalk', 'PlatformName': 'ECS running on 64bit Amazon Linux 2', 'PlatformVersion': '3.2.1', 'SolutionStackName': '64bit Amazon Linux 2 v3.2.1 running ECS', 'PlatformStatus': 'Ready', 'DateCreated': datetime.datetime(2022, 11, 3, 17, 59, 2, 630000, tzinfo=tzutc()), 'DateUpdated': datetime.datetime(2022, 11, 5, 1, 52, 26, 10000, tzinfo=tzutc()), 'PlatformCategory': 'ECS', 'Description': '64bit Amazon Linux 2 running ECS', 'Maintainer'<EMAIL_ADDRESS>'OperatingSystemName': 'Amazon Linux', 'OperatingSystemVersion': '2', 'ProgrammingLanguages': [], 'Frameworks': [{'Name': 'ECS', 'Version': ''}], 'CustomAmiList': [{'VirtualizationType': 'pv', 'ImageId': ''}, {'VirtualizationType': 'hvm', 'ImageId': 'ami-03fe378c175d2ad9c'}], 'SupportedTierList': ['WebServer/Standard', 'Worker/SQS/HTTP'], 'SupportedAddonList': ['Log/CloudWatch', 'Log/S3', 'Monitoring/Healthd', 'WorkerDaemon/SQSD'], 'PlatformLifecycleState': 'Recommended', 'PlatformBranchName': 'ECS running on 64bit Amazon Linux 2', 'PlatformBranchLifecycleState': 'Supported'}, 'ResponseMetadata': {'RequestId': '8b788f1c-97ee-4590-95fe-4b6d435ddc7d', 'HTTPStatusCode': 200, 'date': 'Fri, 11 Nov 2022 08:33:32 GMT', 'RetryAttempts': 0}}
2022-11-11 17:33:33,448 (DEBUG) ebcli.lib.elasticbeanstalk : Inside list_platform_branches api wrapper
2022-11-11 17:33:33,448 (DEBUG) ebcli.lib.aws : Making api call: (elasticbeanstalk, list_platform_branches) to region: ap-northeast-1 with args:{'Filters': [{'Attribute': 'BranchName', 'Operator': '=', 'Values': ['ECS running on 64bit Amazon Linux 2']}]}
2022-11-11 17:33:33,503 (DEBUG) ebcli.lib.aws : API call finished, status = 200
2022-11-11 17:33:33,503 (DEBUG) ebcli.lib.aws : Response: {'PlatformBranchSummaryList': [{'PlatformName': 'Docker', 'BranchName': 'ECS running on 64bit Amazon Linux 2', 'BranchOrder': '10500', 'LifecycleState': 'Supported', 'SupportedTierList': ['WebServer/Standard', 'Worker/SQS/HTTP']}], 'ResponseMetadata': {'RequestId': '5bba52f8-31e5-464a-9704-4c0352c6dd67', 'HTTPStatusCode': 200, 'date': 'Fri, 11 Nov 2022 08:33:33 GMT', 'RetryAttempts': 0}}
2022-11-11 17:33:33,512 (INFO) eb : Traceback (most recent call last):
  File "/usr/local/Cellar/aws-elasticbeanstalk/3.20.3_1/libexec/lib/python3.10/site-packages/ebcli/core/ebrun.py", line 62, in run_app
    app.run()
  File "/usr/local/Cellar/aws-elasticbeanstalk/3.20.3_1/libexec/lib/python3.10/site-packages/cement/core/foundation.py", line 797, in run
    return_val = self.controller._dispatch()
  File "/usr/local/Cellar/aws-elasticbeanstalk/3.20.3_1/libexec/lib/python3.10/site-packages/cement/core/controller.py", line 472, in _dispatch
    return func()
  File "/usr/local/Cellar/aws-elasticbeanstalk/3.20.3_1/libexec/lib/python3.10/site-packages/cement/core/controller.py", line 472, in _dispatch
    return func()
  File "/usr/local/Cellar/aws-elasticbeanstalk/3.20.3_1/libexec/lib/python3.10/site-packages/cement/core/controller.py", line 478, in _dispatch
    return func()
  File "/usr/local/Cellar/aws-elasticbeanstalk/3.20.3_1/libexec/lib/python3.10/site-packages/ebcli/core/abstractcontroller.py", line 92, in default
    self.do_command()
  File "/usr/local/Cellar/aws-elasticbeanstalk/3.20.3_1/libexec/lib/python3.10/site-packages/ebcli/controllers/local.py", line 62, in do_command
    cnt = factory.make_container(self.app.pargs.envvars,
  File "/usr/local/Cellar/aws-elasticbeanstalk/3.20.3_1/libexec/lib/python3.10/site-packages/ebcli/containers/factory.py", line 76, in make_container
    raise NotSupportedError(strings['local.unsupported'])
ebcli.objects.exceptions.NotSupportedError: You can use "eb local" only with preconfigured, generic and multicontainer Docker platforms.


Improve React synchronization

For https://github.com/uber/deck.gl/issues/2831
https://github.com/uber/deck.gl/issues/2458
Background
The root cause of the synchronization issue is that there are up to 3 independent render loops: Deck, Mapbox and React. Each component in this mix may notify others to update, but they each update on its own schedule.
There are the following issues in the DeckGL React component implementation:

Deck may not redraw immediately after component render, making it lag behind the map and other overlays.
It keeps a copy of the current view state in the component state as a mechanism to trigger rerender.

Even if the user supplies the viewState via props, the internal state still gets updated and can potentially go out of sync or cause double rerender.
In order to mimic the view state handling logic, the component duplicates a considerable amount of code from the Deck class.

It calls deck.setProps inside the render method.

This is often unnecessary, when the render is triggered by an internal view state change.
In the case of viewport transition, setProps triggers another onViewStateChange call which calls setState. Calling setState inside of render causes React to emit an error. Sometimes this also causes the map to flash to the destination viewport before resume transitioning.

This PR rewrites the React component logic to something hopefully simpler and more generic.
Change List

Remove DeckGL component states
Remove DeckGL view state/size change handlers
Check for view state change in a custom render callback and trigger React render if needed

Coverage increased (+0.3%) to 62.128% when pulling 90b1d15a75c2fe11360144e8910092b40476717f on x/react-sync into 2fc418d6505f300ad74d818f3b445fea99541cdf on master.


ESM Module

Is your feature request related to a problem? Please describe.
For the usage of tree shaking and bundles size and the usage in modules anyway it is recommended to bring Bootstrap Toaster as a esm module.
Describe the solution you'd like
Convert to esm module
Describe alternatives you've considered
Bring both

I know it's been literally forever, and you've probably moved on but I'm finally close to getting this bundled as both UMD and ESM modules for 5.2.0.

Nice job. But as you said I already moved on. I needed a fast working solution so I created my own implementation.
Thank you for coming back. :)


Fix-2876 Limit the client reconnect behavior

Motivation
This PR want to fix issue #2876
Client reconnect too much and load data from bookie to cause the high network bandwidth usage.
Add mechanisms to limit the subscribe per consumer to avoid high network bandwidth usage.
By default, the limit mechanisms is close. Can enable by broker.conf and namespaces policy.
Modifications
Add mechanisms to limit consumer subscribe times in a period.
Result
If enable the Subscribe Rate Limiter, broker will refuse a consumer subscribe which subscribe times is over more than max subscribe times in a period.

Fix #2876

@codelipenghui Thanks for the fix.
Seems there was some thing wrong in UT. Please reference the failure tests at this link:
https://builds.apache.org/job/pulsar_precommit_java8/4789/#showFailuresLink

rerun integration tests

@merlimat @rdhabalia can you guys review this?


Share the python Engine

Is there a way for compiling the freezed and initialised python engine wasm and run arbritary script at runtime? Or run a somehow compiled script at runtime? I am basically looking for a python intrepreter sandboxing option.

That is a neat idea! For now, I think you could just run eval/exec from inside a plugin. We've also been discussing ways of supporting something like this using a dynamically linked runtime, but haven't really started on that yet.

@zshipko, this would mean the input passed into the plugin.call from the host would actually be the Python code to eval/exec correct?

Yeah thanks for clarifying, the Python code would be the input to a plugin function that passes it to eval.


fix(onboarding): show a 'Finish' button in the final step

fixes #564
//cc @lcouzens

Codecov Report

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

@@           Coverage Diff           @@
##           master     #567   +/-   ##
=======================================
  Coverage   83.16%   83.16%
=======================================
  Files         162      162
  Lines        2477     2477
  Branches      408      408
=======================================
  Hits         2060     2060
  Misses        370      370
  Partials       47       47

Impacted Files
Coverage Δ

src/components/charts/commonChart/chartUtils.ts
80% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks @dlabrecq


Where to download model PoseC3D_ucf101.pdparams and model PoseC3D_epoch_0012.pdparams

Hi,
Could you please tell us where to download the models below:
      PoseC3D_epoch_0012.pdparams
      PoseC3D_ucf101.pdparams

Thanks!
-Scott

https://github.com/PaddlePaddle/PaddleVideo/blob/develop/docs/en/model_zoo/recognition/posec3d.md
另外，如果有图像、视频理解和生成的需求，可以使用我们新的跨模态工具: https://github.com/PaddlePaddle/PaddleMIX/tree/develop


Creating CAA records fails

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform v1.2.8
on darwin_amd64
+ provider registry.terraform.io/cloudflare/cloudflare v3.25.0

(Note: running under TFE; this is local output. TFE is running v1.2.4)
Affected resource(s)

cloudflare_record

Terraform configuration files
resource "cloudflare_record" "caa_issue_godaddy" {
  zone_id = data.cloudflare_zones.[snip]_com.zones[0].id
  name = "[snip].com"
  value = "0 issue \"godaddy.com\""
  type = "CAA"
  ttl = 24 * 60 * 60  # 24 hr
}

Link to debug output
https://example.com
Panic output
N/A
Expected output
The change to apply, or we get a decent error message about why they fail to apply. The UI just tells us "400 Bad Request", which isn't a usable diagnostic. Even going to the debug logs, all we get is,
"message": "flags is a required data field."

… which is useless: we are supplying flags. (flags is the 0 at the front of the record's content. The resource itself does not offer a flags attribute.)
Actual output
The change errors. The debug log provides the most insight:
2022-10-13T17:58:40.874Z [DEBUG] provider.terraform-provider-cloudflare_v3.25.0: Cloudflare API Request Details:
---[ REQUEST ]---------------------------------------
POST /client/v4/zones/[snip]/dns_records HTTP/1.1
Host: api.cloudflare.com
User-Agent: terraform/1.2.4 terraform-plugin-sdk/2.10.1 terraform-provider-cloudflare/3.25.0
Content-Length: 201
Authorization: Bearer REDACTED
Content-Type: application/json
Accept-Encoding: gzip

{
"created_on": "0001-01-01T00:00:00Z",
"modified_on": "0001-01-01T00:00:00Z",
"type": "CAA",
"name": "[snip].com",
"content": "0 issue \"godaddy.com\"",
"zone_id": "[snip]",
"ttl": 86400
}
[snip]
2022-10-13T17:58:41.157Z [DEBUG] provider.terraform-provider-cloudflare_v3.25.0: Cloudflare API Response Details:
---[ RESPONSE ]--------------------------------------
HTTP/2.0 400 Bad Request
Cf-Cache-Status: DYNAMIC
Cf-Ray: 7599f6f9f9fc5a3f-IAD
Content-Type: application/json
Date: Thu, 13 Oct 2022 17:58:41 GMT
Server: cloudflare
Set-Cookie: __cfruid=[snip]; path=/; domain=.api.cloudflare.com; HttpOnly; Secure; SameSite=None
Vary: Accept-Encoding
X-Envoy-Upstream-Service-Time: 12

{
"result": null,
"success": false,
"errors": [
{
"code": 1004,
"message": "DNS Validation Error",
"error_chain": [
{
"code": 9101,
"message": "flags is a required data field."
}
]
}
],
"messages": []
}

Steps to reproduce
Attempt to add a CAA issue record. AFAICT, CF's validation rules changed at some point in a way that the Provider can't cope with. (This would not be the first change in CF's validation logic that we've witnessed.)
Additional factoids
No response
References
Additionally, the Cloudflare provider fails to report the error. The only error the UI gets is,
Error: failed to create DNS record: HTTP status 400: DNS Validation Error (1004)

… which is worthless. One has to go to the debug logs to get "more" information.

Do not truncate or trim the output as the surrounding context is useful for debugging and without it, maintainers are restricted in what assistance and diagnosis they can provide.

The output contains credentials, which is another bug in this provider.

the resource usage is incorrect for a CAA record. it doesn't use value (simple values) but the data block since it needs additional properties. you can see an example of this in our tests https://github.com/cloudflare/terraform-provider-cloudflare/blob/master/internal/provider/resource_cloudflare_record_test.go#L713-L722. i can't speak for the when/if this changed in the API (best lodge a support ticket for the DNS team if you need to know more) but the expected usage for complex records (CAA/SRV/LOC) has always been to use the data block to ensure we build the correct payload with the conditional fields so this may have just been working by accident.

I'll look into data, and see if I can get it to work. But even if that's the case, there's still a number of bugs present here:

data is completely undocumented, AFAICT.
the logs contain access credentials, yet the bug report flow wants you to post unadulterated logs. Since redacting them is some effort, and AFAICT there's no way to purge them from TFE (meaning I've leaked the cred to anyone w/ Read access to our instance…) … the provider shouldn't log them.
the diagnostics the provider gives doesn't help the user in arriving at a solution


Idiomatic Way to Get Log Entry from Hash

The Log entry contains the identity of the user that signed the data. This is very useful information.
How can I get this from a given hash? Do I just go to the IPFS CID and the block of data is there?
I was wondering because, to create a ledger chronicling ownership with OrbitDB is technically as simple as having a log with { to } (and the original owner is the identity). Otherwise, I'd have to store {to, from}, which would be redundant.

Oh, nevermind. Probably just Entry.fromMultihash


FlowContentObserver Crash on Android O

DBFlow Version: 4.0.3
Issue Kind (Bug, Question, Feature): Bug/Question
Description:
Calling registerForContentChanges() on FlowContentObserver causes
java.lang.SecurityException: Failed to find provider TimeEntry_Model for user 0; expected to find a valid ContentProvider for this authority
This link explains the change in Android O
https://developer.android.com/preview/behavior-changes.html#ccn
In debugging I found that the Uri DBFlow uses for my model is dbflow://%60TimeEntry_Model%60  I've tried adding that to the authorities property for my content provider in the android manifest file. I also tried adding TimeEntry_Model. However, I always get the same crash.
My question is does this change in Android require something to change in DBFlow, or am I just not  specifying the correct authority for my database model?

It says "if you are targeting Android O"
...So you could keep your target below O, for now.

is this still an issue?

This is a real issue now, here's the change described > https://developer.android.com/about/versions/oreo/android-8.0-changes.html#ccn

@agrosner are u aware of this issue on android oreo?

I've managed to work around the issue on Oreo by not using the FlowContentObserver any more, the uri's it generate throw the SecurityExceptions on compileSdkVersion 26. Using DirectModelNotifier did give me the needed callbacks on data changes.

So it's not possible to keep your targetSdk below the compileSdk? I was
curious about this.
On Wed, Sep 20, 2017 at 9:59 AM, Sjoerd van Gestel<EMAIL_ADDRESS>
wrote:

I've managed to work around the issue on Oreo by not using the
FlowContentObserver any more, the uri's it generate throw the
SecurityExceptions on compileSdkVersion 26. Using DirectModelNotifier did
give me the needed callbacks on data changes.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Raizlabs/DBFlow/issues/1356#issuecomment-330879142,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAfQEMPeXZiD4VAoaRXJ4vwimrgs-CHdks5skSg_gaJpZM4OModX
.

@CapnSpellcheck No, thats not possible for us.

observeOnTableChanges in the RX implementation also don't seem to work anymore on Oreo

This is kinda a breaking issue, since Android 8.0 has been out for a while. Is there any indication when this issue will be fixed?

@surajm097 @simon-the-canadian According to the docs you will only have a problem if you target 26. Do either of you confirm this? If this is true, that would significantly reduce the severity, as most apps don't need to target 26.
(Note, I do not work on this project)

@CapnSpellcheck You're right that its only an issue if you target api 26. I'm not targeting that api yet mainly because of this crash. I'm not in a huge hurry to target 26 either, but it would be nice to have this addressed some time in the near future.

This bug is preventing usage of the lifecycle logic added as default in support v26 witch can't be used without targetSdkVersion 26, this now became blocking for us.

These APIs now require that a valid ContentProvider is defined for the authority in all Uris. Defining a valid ContentProvider with relevant permissions will help defend your app against content changes from malicious apps, and prevent you from leaking potentially private data to malicious apps.

meaning if you do not provide a ContentProvider that has the authority you're targeting then you cannot use the default ContentResolverNotifier anymore. I will have to introduce a breaking change in DBFlow in order to switch over default to DirectModelNotifier. For now your best option to switch to the direct option. I may have to deprecate ContentResolverNotifier in a near-future release in order to have people switch over as some may not be aware they're using it.

@agrosner DirectModelNotifier lacks a feature of FlowContentObserver: batched notifications (including notifyAllUris = false). It should be added to it if you deprecate  FlowContentObserver.

@agrosner, are there any workarounds for this issue? When this issue is planned to be fixed?
I've added generation of external content provider and added a provider to my manifest (with grantUriPermissions="true"). Now my data is available with content://com.sample/MyEntity uri. But FlowContentObserver still needs dbflow://`MyEntity` to be accessed. Is it possible in this case to write my own ModelNotifier which will work with uris like content://? Have you any other ideas for workaround?
Guys, @WonderCsabo, @simon-the-canadian, how do you deal with it?
Thank you, I'll appreciate any help with this issue.

Any progress?
need to change this method
public static Uri getNotificationUri(@NonNull Class<?> modelClass,
                                         @NonNull Action action,
                                         @Nullable SQLOperator[] conditions) {
        Uri.Builder uriBuilder = new Uri.Builder().scheme("dbflow")
            .authority(FlowManager.getTableName(modelClass));
        if (action != null) {
            uriBuilder.fragment(action.name());
        }
        if (conditions != null && conditions.length > 0) {
            for (SQLOperator condition : conditions) {
                if (condition != null) {
                    uriBuilder.appendQueryParameter(Uri.encode(condition.columnName()), Uri.encode(String.valueOf(condition.value())));
                }
            }
        }
        return uriBuilder.build();
    }```

fixed. https://github.com/Raizlabs/DBFlow/releases/tag/4.2.0

@agrosner you could add the content provider to the dbflow project manifest, so client could automatically get it via manifest merging.

Yes. I do not want to force consumers on it. If it's exported there could be collisions in Android os that will prevent installing. If I included it in the library, most devs might not be aware it was there and get bug reports later about it.


feat: use custom overlay for stream preview

Closes #545, #414

Since we're back to the regular twitch URL, shouldn't twitch-player.html be deleted?


Error: This command needs 2 arguments: release name, chart path in helm upgrade command

Output of helm version: "v2.12.2"
Output of kubectl version: Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.0", GitCommit:"ddf47ac13c1a9483ea035a79cd7c10005ff21a6d", GitTreeState:"clean", BuildDate:"2018-12-03T21:04:45Z", GoVersio n:"go1.11.2", Compiler:"gc", Platform:"windows/amd64"}                                                                                Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.11-eks", GitCommit:"6bf27214b7e3e1e47dce27dcbd73ee1b27adadd0", GitTreeState:"clean", BuildDate:"2018-12-04T13:33:10Z", Go Version:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.): AWS
Error: This command needs 2 arguments: release name, chart path
i am running kubernetes and trying to create a test environment and for this changing the command helm upgrade , am getting above error

@kumbamashwin did you get the upgrade command working?

I'm going to close this ticket due to inactivity, but please re-open if this still needs to be addressed. Thanks!

for me it was extra spaces with helm upgrade.
If you are using multi line command with backslash ( \ ), Ensure there are no spaces after the backslash.


[CT-2516] [Bug] Upgrade to 1.5.0 generates "TypeError: argument of type 'PosixPath' is not iterable" on model runs.

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
We just upgraded our poetry packages for dbt-core and dbt-bigquery to 1.5.0.
When running: poetry run dbt --version everything works fine. But when calling a model like:
poetry run dbt run -s model_name
poetry run dbt build -s model_name
We get a new error never seen before.
Expected Behavior
That the models get built as prior with the normal CLI output.
Steps To Reproduce

Update pyproject.toml with setting dbt-core & dbt-bigquery versions to "1.5.0"
run "poetry update"
run "poetry run dbt --version"
Verify that it outputs the correct versions

run "poetry run dbt run -s name_of_model"

Relevant log output
14:13:06  Running with dbt=1.5.0
14:13:49  Encountered an error:
argument of type 'PosixPath' is not iterable
14:13:49  Traceback (most recent call last):
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/cli/requires.py", line 86, in wrapper
    result, success = func(*args, **kwargs)
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/cli/requires.py", line 71, in wrapper
    return func(*args, **kwargs)
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/cli/requires.py", line 142, in wrapper
    return func(*args, **kwargs)
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/cli/requires.py", line 168, in wrapper
    return func(*args, **kwargs)
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/cli/requires.py", line 215, in wrapper
    return func(*args, **kwargs)
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/cli/requires.py", line 242, in wrapper
    manifest = ManifestLoader.get_full_manifest(
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/parser/manifest.py", line 227, in get_full_manifest
    manifest = loader.load()
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/parser/manifest.py", line 386, in load
    self.parse_project(
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/parser/manifest.py", line 539, in parse_project
    hook_parser.parse_file(file_block)
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/parser/hooks.py", line 120, in parse_file
    self.parse_node(hook)
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/parser/base.py", line 394, in parse_node
    self.render_update(node, config)
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/parser/base.py", line 370, in render_update
    context = self.render_with_context(node, config)
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/parser/base.py", line 240, in render_with_context
    get_rendered(parsed_node.raw_code, context, parsed_node, capture_macros=True)
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/clients/jinja.py", line 591, in get_rendered
    return render_template(template, ctx, node)
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/clients/jinja.py", line 546, in render_template
    return template.render(ctx)
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/jinja2/environment.py", line 1301, in render
    self.environment.handle_exception()
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/jinja2/environment.py", line 936, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
TypeError: argument of type 'PosixPath' is not iterable

Environment
- OS: Ubuntu 20.04
- Python: 3.8.10
- dbt: 1.5.0

Which database adapter are you using with dbt?
bigquery
Additional Context
No response

@christopherekfeldt Thanks for opening! I'm going to label this as a potential regression for v1.5.
It's weird that this is happening during project parsing. Based on the error message and occurrence, I'd guess that you're accessing a flag that's being passed in, and trying to loop over it (?).
Educated guesses - any chance you're doing one of the following?

Referencing the invocation_args_dict context variable somewhere in your project
Have a package installed that's doing this, i.e. dbt_artifacts

No I don't think so. I searched it and found nothing in our project reflecting "invocation_args_dict".
These are the packages specified in our packages.yml:
packages:

package: dbt-labs/dbt_utils
version: 1.0.0

package: dbt-labs/codegen
version: 0.9.0

package: elementary-data/elementary
version: 0.7.5

package: calogica/dbt_expectations
version: 0.8.5

On the last part my answer is no, we only have one project dir and a common profile in our dbt root folder.
The only connection to dbt apart from installing the tools dbt-core and dbt-bigquery with Poetry is the tool sqlfluff-templater-dbt = "2.0.3" which we use for pre-commit together with sqlfluff. But can't see how that is correlated with the parsing of the project.

Heads up that the elementary package uses the invocation_args_dict variable:
https://github.com/elementary-data/dbt-data-reliability/blob/0.7.5/macros/edr/dbt_artifacts/upload_dbt_invocation.sql#L55-L90

Okay, commented out all packages besides dbt-utils and removed dbt_packages/ folder and rerun "poetry run dbt deps".
Getting the same output still when running dbt compile/run/build -s model_name

Heads up that the elementary package uses the invocation_args_dict variable:

That felt like a promising lead! However:

I tried installing the package into an empty project, and I was able to run everything without a problem.
It sounds like @christopherekfeldt removed the package, and is still seeing the same error

On looking again at the stacktrace, I'm now seeing that the error seems to crop up during hook parsing:
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/parser/manifest.py", line 539, in parse_project
    hook_parser.parse_file(file_block)
  File "/mnt/c/git/bica-dbt/dbt/.venv/lib/python3.8/site-packages/dbt/parser/hooks.py", line 120, in parse_file
    self.parse_node(hook)

@christopherekfeldt Do you have any on-run-start or on-run-end hooks defined in dbt_project.yml? Do any of them make use of the flags variable?


Doesn't seem to detect streaming on Win11 Pro machine

Task is running, and nvstreamer launched when I connected, but nothing appears in the log and no actions taken

Fixed - was the Console vs Terminal issue


⚠ Carbubu has degraded performance

In 4bfe269, Carbubu (https://carbubu.fr) experienced degraded performance:

HTTP code: 200
Response time: 4936 ms

Resolved: Carbubu performance has improved in fe3da60 after 18 minutes.


Fix add screen command

I tried adding a screen just now:
$ screenly screen add 2k7e-th9s
Error occurred: WrongResponseStatus(200)

The screen was paired properly, but got an error above.
When repeating the command I got the following:
$ screenly screen add 2k7eth9s
Error occurred: WrongResponseStatus(400)

Action Items

[ ] Fix the status code in the API end-point (should return 201, not 200)
[ ] Add handling for 400 response code when the screen has already been paired

@vpetersson you can enter a name after the command. It takes an optional name.

Got it -- i missed that.