README.md does not match API

We changed the interface but not the documentation.

tests_per_second=10

https://github.com/niccokunzmann/hanging_threads#usage
https://github.com/niccokunzmann/hanging_threads/blob/master/hanging_threads.py#L52

I'll fix the docs.


Add a new flag variable that indicates if a simulation is currently running or not

Originated from https://github.com/OpenWaterAnalytics/EPANET/issues/208.
Add a new flag variable (like RunFlag) to the EN_Project structure that indicates if a simulation is currently running or not. This flag will be used in some functions like EN_setflowunits to prevent changes during a simulation.
The RunFlag would be set in EN_openH, EN_closeH, EN_openQ and EN_closeQ. It would require careful thought to identify which API functions, especially those that modify parameters, would be affected by it, since for some parameters it makes sense to allow a change during an extended period analysis but for others it doesn't.

There are three phases or modes when using the Toolkit. Before simulation, during simulation, and after simulation.


ProjectSettings.load_resource_pack won't replace files.

Godot version:
3.2.1.stable
OS/device including version:
Windows10 (latest)
Issue description:
Been trying a solution for a least a few hours on this issue. ProjectSettings.load_resource_pack doesn't replace files if replace_files is true . I made one pck file using export with a scene that had a red color_rect. the pck file loads properly without errors but wont have the red square.
pls don't fix this because its the only way to make pcks to work but turning on 'convert text resources to binary on export' does make it work but filenames are like res://folder/scene.tscn.converted.res instead of res://folder/scene.tscn and they do load the red color_rect
Steps to reproduce:
pretty much add a red color_rect, export as pck or zip, and try to load that pck file. the pck file will load properly (will return true) it won't have the red color_rect square.
Minimal reproduction project:
same as above.

anywho made a small snippet that might be useful for others that also have this issue. if you turned on 'Convert Text Resources to Binary On Exit' for pck files. Also if you leave 'Turn on Convert Text Resources to Binary On Exit' while compiling your app, the snippet still works.

pls don't fix this

Explain.


entt::any hash function

This change allows to get std::hash of entt::any content.

I'm not that convinced about this. What's the use case?

I'm not that convinced about this. What's the use case?

I'd like to use entt::any as a key in hash map.
For example, I have an asset system, in which assets can have keys of arbitrary type.
A texture may be loaded from file using FilePath type key or generated in runtime using struct PerlinNoise { float width, height; ... }; key.
There can be lots of other use cases for entt::any as a hash map key.

I'd like to use entt::any as a key in hash map.
For example, I have an asset system, in which assets can have keys of arbitrary type.
A texture may be loaded from file using FilePath type key or generated in runtime using struct PerlinNoise { float width, height; ... }; key.
There can be lots of other use cases for entt::any as a hash map key.

Interesting. So, a sort of erased key for which the type doesn't really matter? Never thought about it actually.

Yes, in the example above the type of key doesn't matter for asset system.

Yes, in the example above the type of key doesn't matter for asset system.

Ok, I like the idea overall, but there some things of the PR that I would change.
For example, I'm not that keen on polluting std:: directly from within EnTT. Probably an ADL based solution would be nicer here, if you get what I mean.

Ok, I like the idea overall, but there some things of the PR that I would change.
For example, I'm not that keen on polluting std:: directly from within EnTT. Probably an ADL based solution would be nicer here, if you get what I mean.

Okay, I'll fix it a bit later and reopen the request.

Okay, I'll fix it a bit later and reopen the request.

Oh, no, I was looking into this yesterday.
I'm working on some new feature for any because of job, so I delayed this PR a little (there were some conflicts to solve unfortunately).
But still, you can reopen it right away. I'm fine with fixing the conflicts and merging it once done with the changes on my side. :+1:

Oh, no, I was looking into this yesterday.
I'm working on some new feature for any because of job, so I delayed this PR a little (there were some conflicts to solve unfortunately).
But still, you can reopen it right away. I'm fine with fixing the conflicts and merging it once done with the changes on my side. :+1:

Ok, I'll reopen it.
I've been planning to fix your comments, but unfortunately have no time right now.

Ok, I'll reopen it.
I've been planning to fix your comments, but unfortunately have no time right now.

std::hash provides a specialization for pointer types. I think it would make more sense to use std::hash<void *> instead of return 0; if the type doesn't define a std::hash specialization.

I'd like to use entt::any as a key in hash map. For example, I have an asset system, in which assets can have keys of arbitrary type. A texture may be loaded from file using FilePath type key or generated in runtime using struct PerlinNoise { float width, height; ... }; key. Assets themselves are stored in hash map and indexed by these keys. There can be lots of other use cases for entt::any as a hash map key.

I have the exact same scenario. Really interested in this one.

Ok, I'm slowly addressing all issues and PRs. This PR has some conflicts and I'd like to split it in two parts (any and meta_any). Gimme the time to figure it out and it will land upstream. 👍

Unfortunately, I had to revert these changes because the whole things doesn't really work as expected in some projects of mine.
Main problem is that is_std_hashable can fail miserably (quite easily) and working around it is hard most of the times.
Briefly, imagine a type which is conditionally hashable. In this case, is_std_hashable returns true but the code doesn't compile because the underlying type isn't really hashable.
It happens with classes like containers, optionals, tuples and so on. That is, quite a lot of types at the end of the day. It's not feasible to write specializations for everything or ask the user to do so.
This makes supporting the feature as a built-in functionality very (very) challenging if not impossible as far as I can tell.
In theory, one could introduce a new class (any_index?) that stores an any and an erased hash function internally, mostly similar to what I did (it would probably use any_cast to achieve the same result). This solution wouldn't affect all uses of entt::any in a codebase.
@alexander-v @TerensTare @WoLfulus I'm open to PRs in ☝ this sense if you are willing to contribute. 🙂
However, I'm closing this PR because implementing it as a built-in feature of entt::any isn't viable.


Page should remove references to using packer scripts with AIB

in two places, this page mentions using packer scripts directly with AIB:
Azure Image Builder is built on Packer, so you can even use your existing Packer shell provisioner scripts with it.
...
You can also use existing Packer provisioner scripts with [Azure Image Builder](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/image-builder).
I don't believe this is true; these statements should be revised or removed.

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

ID: 1f33d707-2a5b-e0f7-2649-9b778d57a1da
Version Independent ID: 3584b4b8-c5f5-2170-3f8a-7a9a33025a84
Content: Create Linux Azure VM Images with Packer - Azure Virtual Machines
Content Source: articles/virtual-machines/linux/build-image-with-packer.md
Service: virtual-machines
Sub-service: imaging
GitHub Login: @cynthn
Microsoft Alias: cynthn

@larryclaman  Thanks for the feedback! We are investigating and will update you shortly.

@cynthn
Can you please check and add your comments on this doc update request as applicable.

OP here... I missed the sublet of the statement.... it says you can use existing provisioner scripts (which is true), and not that you can use existing JSON/HCL packer configs (which I incorrectly read it was ).
Closing this issue.

@ericd-mst-github FYI - you might just want to check the wording on this anyways, to see if we can make it clearer?


Permanent popup (scripted)

After roasting and smoking my brain for a good while, trying to implement this, I finally can't go any further.
I have a little color picker library that I'd like to utilize. For that to work nicely, I wanted to implement a "permanent" popover, that would not go away untill it was closed using it's .close() method, or .toggle().
I can trigger the popup, but as soon as I have clicked, it closes again. Why is that? I have made sure, but there is only a single click event, from what I can tell.
Here is the code:
            e._popover = new Popover(e, {
                trigger: "click",
                template: '
'
                    + '

'
                    + '

'
                    + '
',
            });
            // Re-implementing Popover open and close to allow
            // the color picker to work as expected.
            e._popover.open = function() {
				if (this.popover === null) {
					this.createPopover();
					this.stylePopover();
					this.updatePopover();

                    // Color picker
                    var content = $(this.popover).find(".popover-content")[0];
                    e._picker = new piklor(content, palette);
                    console.log(e._picker);
                    e._picker.colorChosen(function(col){
                        console.log("Color: ",col);
                    });
                    e._picker.open();
				}
			}.bind(e._popover);
			e._popover.close = function() {
				if (this.popover && this.popover !== null && this.popover.classList.contains('in')) {
                    e._picker.close();
					this.popover.classList.remove('in');
                    this.removePopover();
				}
			}.bind(e._popover);

Any idea? The only source I have not checked yet, but which I highly doubt, is the Piklor instance itself (maybe its clinging to click too, which I doubt.)

The tooltips/modals get dismissed on any click event inside/outside the
trigger. We need to implement a prevention for that.
I think this would give you a clue.
On Sun, Sep 20, 2015 at 5:30 AM, Ingwie Phoenix<EMAIL_ADDRESS>wrote:

After roasting and smoking my brain for a good while, trying to implement
this, I finally can't go any further.
I have a little color picker library that I'd like to utilize. For that to
work nicely, I wanted to implement a "permanent" popover, that would not go
away untill it was closed using it's .close() method, or .toggle().
I can trigger the popup, but as soon as I have clicked, it closes again.
Why is that? I have made sure, but there is only a single click event,
from what I can tell.
Here is the code:
        e._popover = new Popover(e, {
            trigger: "click",
            template: '
'
                + '

'
                + '

'
                + '
',
        });
        // Re-implementing Popover open and close to allow
        // the color picker to work as expected.
        e._popover.open = function() {
            if (this.popover === null) {
                this.createPopover();
                this.stylePopover();
                this.updatePopover();

                // Color picker
                var content = $(this.popover).find(".popover-content")[0];
                e._picker = new piklor(content, palette);
                console.log(e._picker);
                e._picker.colorChosen(function(col){
                    console.log("Color: ",col);
                });
                e._picker.open();
            }
        }.bind(e._popover);
        e._popover.close = function() {
            if (this.popover && this.popover !== null && this.popover.classList.contains('in')) {
                e._picker.close();
                this.popover.classList.remove('in');
                this.removePopover();
            }
        }.bind(e._popover);

Any idea? The only source I have not checked yet, but which I highly
doubt, is the Piklor instance itself (maybe its clinging to click too,
which I doubt.)
—
Reply to this email directly or view it on GitHub
https://github.com/thednp/bootstrap.native/issues/16.

How are you doing mate? I wanna talk to you about this and other stuff.

Im doing good!
You can reach me through Skype (wlaningwie) or E-Mail<EMAIL_ADDRESS>:) So if you wish to chat some, feel free to contact me!
Oh and if both do not work, then you can also use this gitter: https://gitter.im/Deskshell-Core/PhoenixEngine?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge
I am also still stuck on the color picker. I took some sleep and will see which event is triggering the close.

Sure thing. I already added you on Skype and waiting to talk to you. I edited your previous post for understandable privacy reasons.

Alright. I accepted the request. shows you as offline atm though. Give me a poke when you wanna =)

Implemented, see the lib folders.


static keyword

Static types
By prefixing the keyword static to a type you are limiting the (re)binding of a variable to that specific type.
example(paramName: static Number) => Any

// valid
function example(num) {
  return ++num;
}

// invalid
function example(num) {
  num = 'test'; // this line throws
  return num;
}

inspiration: http://stackoverflow.com/q/30004233/248058

Static is not needed:
example(paramName: Number) => Number

function example(num) {
  num = 'test'; // error: can not assign value of type String to variable of type Number
  return num;
}

Of course it is needed. It's javascript: once a variable is re-set the type of the parameter is not being checked anymore.

Well, I'm talking about static type checking.

You need to understand that currently we are just checking if you are passing the right parameters to the function.
My proposal would be stricter in the handling of the variable in the function itself.

@Mouvedia
Any type checker would have this static behaviour by default.

@Raynos You could probably have an option to set it globally.
But a granular approach is necessary if we want that feature.

Shouldn't static be implied? If you want to allow other types, shouldn't you use a union type for that?

If you want to allow other types, shouldn't you use a union type for that?
I don't know what you mean by that. You should come on Gitter we discussed about a global per-file opt-in.

This static behavior you're asking for is assumed and built-in behavior for rtype.


$ionicSlides.slideChangeEnd fires one time by fast swiping

by swiping fast between slides, $ionicSlides.slideChangeEnd fires as u finish swiping and not for every slide.. it works ok if u swipe slower
ionic 1.3.x
as i see problem comes from Swiper
any way i found a solution listening to
vm.swiper.on('onSlidePrevStart', () => {
and
vm.swiper.on('onSlideNextStart', () => {
works with fast swiping
so maybe $ionicSlides.slideChangeEnd can be modified to work onSlideNextEnd(swiper) , onSlidePrevEnd(swiper) instead of Swiped onSlideChangeEnd(swiper) callback

Hi @emps,
I'll check it out.
Thanks,
Dan

半年过去了，此bug进展如何？

Any news on this one?

use
vm.swiper.on('onSlidePrevStart', () => {
and
vm.swiper.on('onSlideNextStart', () => {
to indicate swipes

This issue was moved to driftyco/ionic-v1#131


Added: Support for adding empty custom field for CSV mapping to export packed orders

Related Issues

Closes #
Short Description and Why It's Useful

Screenshots of Visual Changes before/after (If There Are Any)

IMPORTANT NOTICE - Remember to add changelog entry
Contribution and Currently Important Rules Acceptance

[x] I read and followed contribution rules

Verified and working fine in release v2.5.0.
https://jam.dev/c/b5ce4130-557f-4e38-9e1a-4aae5d7bdeb9


Package executes on bundle load

@nchanged as requested 👍
Sample:
https://github.com/vegarringdal/fusePackageTest
To get up and running:
npm install
node fuse
Package is very simple:
console.log("I WON!!!!")
console.log("But only because I executed on bundle load, and did not wait")
console.log("MOOOHAHAHA :-)")

export class somePackage{

    constructor(){

    }

    sayhello(){

    }
}

Package is build like this:
var buildPackage = function () {

    let fb = require("fuse-box");
    let fuse = fb.FuseBox;

    let bundle = fuse.init({
        package: "my-package",
        homeDir: "./myPackage/",
        outFile: "./my-package-bundle.js",
        globals: {
            "my-package": "my-package"
        },
        sourceMap: {
            bundleReference: "./my-package-bundle.js.map",
            outFile: "./my-package-bundle.js.map",
        },
        plugins: [
            fb.TypeScriptHelpers(),
            fb.SourceMapPlainJsPlugin()
        ]
    })

    bundle.bundle(`
          > [index.ts]
        `);
}

Loaded in index.html before app bundle
<script src="./my-package-bundle.js"></script>
<script src="./app-bundle.js"></script>

But a you can see in console, the code executes

so, the desired functionality would be to have entry option for packaging? right?

package: {
    name :  "my-package",
    entry : "index.js"
}

Yes, because you dont want packages to execute on load.

i like what @vegarringdal said, let us treat it the same way as package.json main property

@devmondo
Its kinda a bug, since without entry you cant really load it without this to you code...
FuseBox.pkg("my-package", {}, function(___scope___) {
        ___scope___.entry = "index.js"
});

And normally you dont want a package to execute on load
But if calling this a feature gets me closer to this: https://github.com/fuse-box/fuse-box/issues/170 then lets not call it a bug, but a feature 👍 😄

please remember to think about #170 when fixing this, since both will need the entry to work in the same way.
👍

FuseBox.init({
    package: {
        name: "super-name",
        entry: "index.ts"
    },
    homeDir: `${__dirname}/src2`,
    outFile: `${__dirname}/build/out2.js`,
    cache: false
}).bundle("index.ts")

very nice, keep up the good work :-)

how about we call it main instead of entery to be semantic with package.json ?

@devmondo perfect idea!

how about we call it main instead of entery to be semantic with package.json ?

Agree
Thats why I also used "main" when making this in first post
https://github.com/fuse-box/fuse-box/issues/170
Any chance #170 might reach next milestone ? (yes I know Im asking al the time, but really want it  to make it simple to bundle in pakages that is kind aspecial and enable debuggin/watch on them when developing)

@vegarringdal  we should increase our Red Bull dose then ;)

hehe :-)

just got around to try this after Ive got all my other issues fixed
this still executes when loaded...
Im I doing something wrong here ?
    let fb = require("fuse-box");
    let fuse = fb.FuseBox;

    let bundle = fuse.init({
        package: {
            name:"aurelia-v-grid",
            main: "index.ts"
        },
        homeDir: "./node_modules/aurelia-v-grid/src/",
        outFile: "./bundle/aurelia-v-grid/fb-aurelia-v-grid-bundle.js",
        globals: {"aurelia-v-grid": "aurelia-v-grid"},
        sourceMap: {
            bundleReference: "./fb-aurelia-v-grid-bundle.js.map",
            outFile: "./bundle/aurelia-v-grid/fb-aurelia-v-grid-bundle.js.map",
        },
        plugins: [
            fb.CSSPlugin(),
            fb.HTMLPlugin({
                useDefault: true
            }),
            fb.TypeScriptHelpers(),
            fb.SourceMapPlainJsPlugin()
        ]
    })

    // include everything in grid (html elements/css and attribute)
    bundle.bundle(`
    + [**/*.html]
    + [**/*.ts]
    + [**/*.css]
`);

for anyone else reading this I needed to remove the globals.. if that is added it fill execute right away


update ecYeastGEM based on v8.4.2

MATLAB is selecting SOFTWARE OPENGL rendering.

      _____   _____   _____   _____     _____     |
     /  ___| /  _  \ |  _  \ |  _  \   / ___ \    |   COnstraint-Based Reconstruction and Analysis
     | |     | | | | | |_| | | |_| |  | |___| |   |   The COBRA Toolbox - 2021
     | |     | | | | |  _  { |  _  /  |  ___  |   |
     | |___  | |_| | | |_| | | | \ \  | |   | |   |   Documentation:
     \_____| \_____/ |_____/ |_|  \_\ |_|   |_|   |   http://opencobra.github.io/cobratoolbox
                                                  |

 > Checking if git is installed ...  Done (version: 2.25.1).
 > Checking if the repository is tracked using git ...  Done.
 > Checking if curl is installed ...  Done.
 > Checking if remote can be reached ...  Done.
 > Initializing and updating submodules (this may take a while)... Done.
 > Adding all the files of The COBRA Toolbox ...  Done.
 > Define CB map output... set to svg.
 > TranslateSBML is installed and working properly.
 > Configuring solver environment variables ...
   - [----] ILOG_CPLEX_PATH: --> set this path manually after installing the solver ( see https://opencobra.github.io/cobratoolbox/docs/solvers.html )
   - [----] GUROBI_PATH: --> set this path manually after installing the solver ( see https://opencobra.github.io/cobratoolbox/docs/solvers.html )
   - [----] TOMLAB_PATH: --> set this path manually after installing the solver ( see https://opencobra.github.io/cobratoolbox/docs/solvers.html )
   - [----] MOSEK_PATH: --> set this path manually after installing the solver ( see https://opencobra.github.io/cobratoolbox/docs/solvers.html )
   Done.
 > Checking available solvers and solver interfaces ... Done.
 > Setting default solvers ... Done.
 > Saving the MATLAB path ... Done.
   - The MATLAB path was saved as ~/pathdef.m.

 > Summary of available solvers and solver interfaces

			Support 	   LP 	 MILP 	   QP 	 MIQP 	  NLP
	----------------------------------------------------------------------
	gurobi       	active        	    1 	    1 	    1 	    1 	    -
	ibm_cplex    	active        	    0 	    0 	    0 	    0 	    -
	tomlab_cplex 	active        	    0 	    0 	    0 	    0 	    -
	glpk         	active        	    1 	    1 	    - 	    - 	    -
	mosek        	active        	    0 	    - 	    0 	    - 	    -
	matlab       	active        	    0 	    - 	    - 	    - 	    0
	pdco         	active        	    1 	    - 	    1 	    - 	    -
	quadMinos    	active        	    0 	    - 	    - 	    - 	    -
	dqqMinos     	active        	    0 	    - 	    0 	    - 	    -
	cplex_direct 	active        	    0 	    0 	    0 	    - 	    -
	cplexlp      	active        	    0 	    - 	    - 	    - 	    -
	qpng         	passive       	    - 	    - 	    1 	    - 	    -
	tomlab_snopt 	passive       	    - 	    - 	    - 	    - 	    0
	lp_solve     	legacy        	    1 	    - 	    - 	    - 	    -
	----------------------------------------------------------------------
	Total        	-             	    4 	    2 	    3 	    1 	    0

 + Legend: - = not applicable, 0 = solver not compatible or not installed, 1 = solver installed.

 > You can solve LP problems using: 'gurobi' - 'glpk' - 'pdco'
 > You can solve MILP problems using: 'gurobi' - 'glpk'
 > You can solve QP problems using: 'gurobi' - 'pdco'
 > You can solve MIQP problems using: 'gurobi'
 > You can solve NLP problems using:

 > Checking for available updates ...
 > There are 7848 new commit(s) on <master> and 0 new commit(s) on <develop> [800dcf @ master]
 > You can update The COBRA Toolbox by running updateCobraToolbox() (from within MATLAB).
Converting COBRA structure to RAVEN..

***************************************************************
   GECKO: Adding enzyme constraints to a genome-scale model
***************************************************************

Getting genome-scale model ready... Done!

==================
Generating ecModel:
==================
Retrieving EC numbers............................................ Done!
Matching kcats............................................ Done!
Adding enzymes to reactions............................................................... Done!
Improving model with curated data....................................................................................... Done!
Removing repeated rxn: r_0226No2 & r_0226No3
Removing repeated rxn: r_0438No1 & r_0438No2
Removing repeated rxn: r_0438No1 & r_0438No3
Removing repeated rxn: r_0438No1 & r_0438No4
Removing repeated rxn: r_0438No2 & r_0438No3
Removing repeated rxn: r_0438No2 & r_0438No4
Removing repeated rxn: r_0438No3 & r_0438No4
Removing repeated rxn: r_0439No1 & r_0439No2
Merging reactions: arm_r_0439 & r_0439No1
Merging reactions: arm_r_0543 & r_0543No1
Merging reactions: arm_r_1838 & r_1838No1
Removing unused protein: P00424
Removing unused protein: P18496
Removing unused protein: P22135
Removing unused protein: P32453
Removing unused protein: Q3E7B6
Removing incorrect pathways... Done!

==============================================================
Generating ecModel with shared pool assumption (ecModel_batch):
==============================================================
Calculating total abundance.................................................................... Done!
WARNING: Reaction r_1663 is not present in the reaction list

WARNING: Reaction r_4062 is not present in the reaction list

WARNING: Reaction r_4064 is not present in the reaction list

Matching data to enzymes in model... Done!
Estimating GAM.............................................................. Done!
Fitted GAM = 27.4 -> Error = 0.1816
[Warning: MATLAB has disabled some advanced graphics rendering features by switching to software OpenGL. For more information, click here.]
Total protein amount measured = 0 g/gDW
Total enzymes measured = 0 enzymes
Enzymes in model with 0 g/gDW = 0 enzymes
Total protein amount not measured = 0.5 g/gDW
Total enzymes not measured = 968 enzymes
Total protein in model = 0.5 g/gDW
The ECmodel is overconstrained!
 Done!
Saving simulation results files...
File successfully saved.
Sigma factor (fitted for growth on glucose): 0.49

=============
Saving models:
=============
Saving ecYeastGEMv8.4.2:
Converting RAVEN structure to COBRA..
Each model.subSystems{x} is a character array, and this format is retained.
Document written
Each model.subSystems{x} is a character array, and this format is retained.
Saving ecYeastGEM_batchv8.4.2:
Converting RAVEN structure to COBRA..
Each model.subSystems{x} is a character array, and this format is retained.
Document written
Each model.subSystems{x} is a character array, and this format is retained.

It looks like this PR can safely be closed in favor of a new one (generated by the pipeline).


Fix class weight labels

Reference Issues/PRs
Fixes #22413
What does this implement/fix? Explain your changes.
Let y determine the classes instead of class_weight.
Any other comments?

Ready for review

Reviewed, everything looks good!

I ran pytest sklearn/utils/tests/test_class_weight.py
I'm getting a ModuleNotFoundError when I try to run that command.

I ran pytest sklearn/utils/tests/test_class_weight.py

I'm getting a ModuleNotFoundError when I try to run that command.

I had that issue as well and it prevented me from running any of the tests. Try following this. It works after I followed the steps.

Looks like there were some upstream changes to some cython modules, which required recompilation. Looking into the failed test cases now.


make the usage text more visible

Use whitespace and indent to make the first-run usage text more visible:
[~/projects/flutter/flutter] flutter
Flutter - https://flutter.io - version<PHONE_NUMBER>/master

  The Flutter tool anonymously reports feature usage statistics and basic crash reports to Google in
  order to help Google contribute improvements to Flutter over time. Use "flutter config" to control
  this behavior. See Google's privacy policy: https://www.google.com/intl/en/policies/privacy/

Manage your Flutter app development.

Usage: flutter <command> [arguments]

Global options:
-h, --help            Print this usage information.
-v, --verbose         Noisy logging, including all shell commands executed.
...

I experimented with changing where it displayed but had some issues with long and short running commands; happy to iterate on the look.
@Hixie

Some ideas to make it even more obvious:
╔═══════╗
║       ║
╚═══════╝

\e[0;1;41;37m - white on red text
\e[0;1;31m ... \e[0m bright red text, could be used for inside the box or outside it
Dunno, just some ideas. LGTM either way. If you do go the ANSI escape route, make sure it's disabled when you have a dumb terminal detected? We have code to do that already.

Perhaps a welcome message the first time the tool is run, with a prominent message about analytics, and  a 2 second delay before we continue with running the first command? Red text to me would signify an error condition; this is more something that we want to emphasize. I think the delay will help the user notice the message, instead of having it scroll quickly to the top of the screen.

It could be green text, or purple. :-)
I'm worried about a delay because it'll make us look slow.
You could always try \e[5m ... \e[25m.

\e[35m is magenta, FWIW.

ok, updated:

made the usage text bold (on terminals that support it)
drew a double-bordered box around it
for commands like --help, have the text print after the main command text, so that it's not lost to scrolling
for other commands, print out after the engine artifacts are downloaded

Well that looks awesome.


Release version 3.0.1

Issues of this new version should be done before resolving this issue.

Checklist

[x] Upgrade the application's version.
[x] Close and release artifacts on Maven Central.
[x] Update version in readme and add version in changelog.
[x] Create a release on the repository.

Done.


Update sbt-updates to 0.6.1

Updates com.timushev.sbt:sbt-updates from 0.6.0 to 0.6.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

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

labels: sbt-plugin-update, early-semver-minor, semver-spec-patch, commit-count:1

Codecov Report

Merging #18 (427711a) into main (145b1be) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #18   +/-   ##
=======================================
  Coverage   46.62%   46.62%
=======================================
  Files           5        5
  Lines         326      326
  Branches        7        7
=======================================
  Hits          152      152
  Misses        174      174

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 145b1be...427711a. Read the comment docs.


Update git.aliases.bash

Simply because I don't want to type gpu origin master but gpuo master.

Great - thanks!


Hello Sir! I Have 0.012XMR In my Wallet But They are disappeared Now

Hello Sir,
I want to know that my account automatically send 0.01XMR To Null Address(No Address).
Please Help me it took more than 1 month to mine 0.1 xmr or tell me where to contact I am Providing You All Proof.
Transaction ID:
e95fda6f01a098cec93d557e0638c2af5f0ad7dbcfd6ccb268f838e1bf9b69b4
Transaction ID Image:-

Transaction Image:-

Please help Me!

Unfortunately, this means your private keys are no longer private and they have transferred your monero out of the wallet

But How Can I Get This Amount Back. And It is not showing any address.

And I How My Keys Shared While This Is My Personal PC With Original Windows. And Other Stuff.

Monero transactions are not reversible.
The address will only show if you sent the transaction from your device. The monero blockchain stores addresses as stealth addresses and are not shown in the app

There is a high probability that your device has been compromised. the keys are encrypted on your drive and are never sent to the server


Update openapi schema url

Needed for the SSO Settings API specs.

Need to also call make generate-client


current tab page is truncated when tabline string is too long since open many tab pages.

Thanks for your plugin, and it's clear and useful.
When I open many tabpages for example 20 tabs, and each file name is pretty long, then the generated tabline string is too long, and excedding the current vim columns(window width), so only  the last 10 tabpage's titles are displayed, and the first 10 tabpage's titles are truncated. This is not convenient that I cannot see which tabpage is activated when I use the first 10 tabpages.
Could you fix this?

Thanks for opening the first issue.
I'm not sure what type of solution you're looking for, but I think the tab max character length configuration could help:
let g:mintabline_tab_max_chars = 15

Have you tried this?

Thanks for your reply.
I know 'g:mintabline_tab_max_chars', but it won't help.
Maybe I didn't describe my problem clearly.
For example, I open 14 tabpages, and work on '11th' one (title highlighted):

When I jump to the '8th' tabpage, the tabline still display the last several tabpages since the vim width is limited (8th is high lighted but I can't see it):

What I want is that the tabline likes:
...5 file 6 file 7 file 8 file 9 file ...
i.e. the tabline can 'shift' to display currently activated tabpage.
p.s. GVim's 'guitablabel' don't have such problem, it will automatically shift to show the activated tabpage (there are "<" ">" in the two ends of the tab title):

Thanks for your quick fix.
I got your idea and have some thoughts.
It would be better if we can remember the last actived tab index. If we just jump between current activated tab and the last one, it will be better if the current displayed tab indexies range keep unchanged.
i.e.
... 3 4 5 6 7 8 9 10 11 12 ...
... 3 4 5 6 7 8 9 10 11 12 ...
instead of
...8 9 10 11 12 13 14...
1 2 3 4 5 6 7 8 9 ...

Instead of iterating to find the start and end displayed tab indexes (while window_width < strchars(join(raw_tabs, ''))), we can store length of each raw_tab, and make a cumsum, and use this cumsum and window_width = &columns and current and last activated tab index to find the start and end tab indexes.

@extr15 I've been thinking about it, but it doesn't seem to be a trivial problem. Addressing the issue will require a significant amount of code, which would exceed the current codebase. I'm not sure if the difference is worth it, so I'll merge the PR as it is for now. Let me know if you can think of a simple solution.

Thanks for your time. It indeed need some more time to implement the details.


Unable to find reusable workflow

Describe the bug
My reusable workflows aren't being found by the static analysis.
To Reproduce
Steps to reproduce the behavior:

Create a workflow.
Create a reusable workflow.
Try to include it in the base workflow.
Github Action will run successfully, vsc will complain with an error.

Expected behavior
Should not be an error if the reusable workflow functions on github.
Screenshots

Extension Version
v0.25.3

Tested this on Windows and repro'd the issue. On Mac the issue doesn't happen. Appears to be an issue with pathing on Windows.

The PR has been completed and the fix will be available in our upcoming release v0.25.6 planned for release April 21 2023.

Thank you very much.

The change is live and released on our new version v0.25.6! Thank you all so much for your support in helping report bugs and great repro steps!

Same here
v0.25.7
My setup :
Version: 1.79.0 (user setup)
Commit: b380da4ef1ee00e224a15c1d4d9793e27c2b6302
Date: 2023-06-07T14:26:35.552Z
Electron: 22.5.5
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621

try referencing the workflow like the document suggests.
uses: {your-org or user name}/{repository name}/.github/workflows/{workflow name}.yml@{branch}


Add direct_support keys in core_eia860__scd_generators_energy_storage as foreign keys to core_eia__entity_generators

Overview
Closes #3695.
What problem does this address?
Ensures FK constraints addressed between the new storage table and the harvested EIA generator and plants IDs.
What did you change?

Make plant_id_eia_direct_support_x fields into integers
Add foreign key constraint
Harvest plant/gen ID combinations

Testing
How did you make sure this worked? How can a reviewer verify this?
Update alembic, regenerate changed assets and run pudl_check_fks. Manually inspect the generator entities table to make sure that the IDs from the storage table are present.
Question for reviewer
I'm almost certain that rows 2315-6 in core_eia860__scd_generators_energy_storage are reporting a second plant ID in the generator support 1 column. Based on the non-existence of those generator IDs in all other EIA data, and the fact that they're valid plant IDs. Should we do anything about this, or accept the introduction of bad generator IDs into our harvesting process?
# To-do list
- [x] Review the PR yourself and call out any questions or issues you have
- [x] Clean up alembic migrations
- [x] Check for unmapped plant IDs
- [ ] Update min/max row counts
- [ ] For minor ETL changes or data additions, once `make pytest-coverage` passes, make sure you have a fresh full PUDL DB downloaded locally, materialize new/changed assets and all their downstream assets and [run relevant data validation tests](https://catalystcoop-pudl.readthedocs.io/en/latest/dev/testing.html#data-validation) using `pytest` and `--live-dbs`.

@cmgosnell I expect there might be some additional row count failures that are caused by the harvesting, but I'm unable to run them locally. I'd like to just merge them into the nightly builds and patch a fix on Monday to update any remaining row count failures.

@e-belfer I think you're done for the day/week and I need to re-run my ETL locally anyway so I can give this a try and update any row counts that are off so we have a chance at getting a good build by Monday.

Excessively null generators
Running the full ETL locally, there were some excessively null rows in the yearly and monthly generator output tables. I'd guess because these generator IDs only showed up in the new table, and were missing from the tables that provide the majority of the generator attributes. See error messages below.
Monthly/Yearly Generator Output Errors
dagster._core.errors.DagsterExecutionStepExecutionError: Error occurred while executing op "out_eia__yearly_generators":

The above exception was caused by the following exception:
ValueError: Found 4 Null rows in mcoe_all_gens.

  File "/Users/zane/code/catalyst/pudl/src/pudl/analysis/mcoe.py", line 209, in mcoe_generators_asset
    return mcoe_generators(
           ^^^^^^^^^^^^^^^^
  File "/Users/zane/code/catalyst/pudl/src/pudl/analysis/mcoe.py", line 704, in mcoe_generators
    ).pipe(pudl.validate.no_null_rows, df_name="mcoe_all_gens", thresh=0.9)
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/miniforge3/envs/pudl-dev/lib/python3.12/site-packages/pandas/core/generic.py", line 6231, in pipe
    return common.pipe(self, func, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/miniforge3/envs/pudl-dev/lib/python3.12/site-packages/pandas/core/common.py", line 502, in pipe
    return func(obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/code/catalyst/pudl/src/pudl/validate.py", line 124, in no_null_rows
    raise ValueError(f"Found {null_rows.sum(axis='rows')} Null rows in {df_name}.")

dagster._core.errors.DagsterExecutionStepExecutionError: Error occurred while executing op "out_eia__monthly_generators":

The above exception was caused by the following exception:
ValueError: Found 4 Null rows in mcoe_all_gens.

  File "/Users/zane/code/catalyst/pudl/src/pudl/analysis/mcoe.py", line 209, in mcoe_generators_asset
    return mcoe_generators(
           ^^^^^^^^^^^^^^^^
  File "/Users/zane/code/catalyst/pudl/src/pudl/analysis/mcoe.py", line 704, in mcoe_generators
    ).pipe(pudl.validate.no_null_rows, df_name="mcoe_all_gens", thresh=0.9)
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/miniforge3/envs/pudl-dev/lib/python3.12/site-packages/pandas/core/generic.py", line 6231, in pipe
    return common.pipe(self, func, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/miniforge3/envs/pudl-dev/lib/python3.12/site-packages/pandas/core/common.py", line 502, in pipe
    return func(obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/code/catalyst/pudl/src/pudl/validate.py", line 124, in no_null_rows
    raise ValueError(f"Found {null_rows.sum(axis='rows')} Null rows in {df_name}.")

Expected Row Counts
Not all tables were populated due to the above errors, but for those that were populated, there were no additional changes to the row counts beyond those already documented. The only tables left unpopulated are related to the EIA Plant Parts and the FERC-EIA record linkage.
Unmapped Plant/Utility IDs
Generating this list now...

I've mapped the IDs, but these four plants are still missing a PUDL plant ID for the subsequent output tables. Need to look into this further.

The integration test failure has to do with one generator (EIA plant ID 60321, generator ID PV1) which is reported in the 860 storage direct support columns in 2023 ER data but nowhere else in the fast ETL data, causing a completely empty row and the corresponding failure.
Problem is, that plant ID and another generator (EXIS2) do exist in our data in other years (retired 2019), and so the plant attributes (location, lat/lon coords, etc.) are carrying through in the full ETL run and not triggering the null row error. The generator itself never has data. So, consistent with the other generators dropped, I've added it to the empty_generator_ids list.


[BLOCKED] Move terraform operations inside container

What is this PR trying to achieve?
Further extraction of build process into containers to increase reproducibility and portability.
Who is this change for?
💻

Waiting for the official hashicorp/terraform image to be 0.9.11

I wonder whether this issue with there not being an official docker image for the latest version with terraform is a general problem we might encounter with terraform builds being in docker.
I mean, could it be that anytime we upgrade terraform our build is broken for a few days until terraform updates the official docker image? Does it mean that before upgrading we should always check if a corresponding docker image exists?

I mean, could it be that anytime we upgrade terraform our build is broken for a few days until terraform updates the official docker image? Does it mean that before upgrading we should always check if a corresponding docker image exists?

If we move entirely to using the Docker image locally as well, then we’d never upgrade ahead of the Docker image. Hopefully a non-problem if we go Docker Everywhere™?

@alicefuzier what @alexwlchan said. I imagined we'd be using the make commands ourselves, thereby avoiding the issue.

👍

Looks ok to me, but there seems to be some kind of conflict with master? I assume docker/nginx/manage_images.sh should not be part of this pull request..

replaced by https://github.com/wellcometrust/platform-api/pull/584


Inclusion of optional libraries should be guarded with "try ... except" and the functionality disabled if not present

Not all libraries used by the PyKOB components are standard on systems with Python: pySerial, pyAudio, and Tkinter are optional additional installs.
Inclusion of references to these libraries should be guarded with try ... except and the functionality not used if the libraries aren't present.

The pykob modules do not rely on a graphical interface. It is only MKOB that does (a different module/application).
I don't think any pykob modules should import graphic libraries. However, if they do, they should be guarded as you suggest.

The pykob modules do not rely on a graphical interface. It is only MKOB that does (a different module/application).
I don't think any pykob modules should import graphic libraries. However, if they do, they should be guarded as you suggest.


Update reedline to paste multiple command lines

Changes to reedline since

Pasting text containing multiple newline separated commands will now return each command (considered valid based on Validator) for evaluation and parse the paste after the next invocation of Reedline::read_line

Tests
Make sure you've run and fixed any issues with these commands:

[x] cargo fmt --all -- --check to check standard code formatting (cargo fmt --all applies these changes)
[x] cargo clippy --all --all-features -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect to check that you're using the standard code style
[x] cargo build; cargo test --all --all-features to check that all the tests pass

Thanks. looking forward to testing it.


Furrl UI containing their UI and a new feature called collage maker f…

Description
Basic and static UI of Furrl  Application, which is an e-commerce platform for unique and quirky clothes that matches your vibe, this UI contains their home page including genre section and post section, This Ui also has a collage maker written only in dart, (The only dependency is image_picker)

[ ] Bug fix (non-breaking change which fixes an issue)
[x] 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

How Has This Been Tested?

[x] Manual testing

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Sorry forgot to insert Screenshots in the PR

crate a issue for this

Created #124

Looks great!!! thanks for contribution. #happyHactoberfest

@tanmoy27112000 brother , I have a question, why in the hactober website they're saying this repos have been excluded, also all the repos that I've been contributing are all excludes, do you know the real reason for it


nak: 0.7.6 -> 0.9.1

Use tag instead of rev = "refs/tags..."
Fix changelog url
Add version check hook
Add update script

Changelog: https://github.com/fiatjaf/nak/releases/tag/v0.9.1
Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/5005


Cannot setup MQTT connection to mosquitto broker on RPi

I am running mosquitto broker on my rpi with SSL and TLS setup with ca.crt, server.crt and server.key .
How can I establish the connection to the mosquitto broker via my esp32 over ssl ?
I am new to this so any help would be helpful.

https://github.com/tuanpmt/espmqtt


希望能够增加视频解析下载功能=。=

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

不考虑


Special characters using win32com.client

It seems that the the special characters ( ) { } ~ can not be sent using the function SendKeys() of the library win32com.client. For this reason they are excluded from the list of special characters used in the brute force technique.
https://github.com/tassoneroberto/py7dtd/blob/853f4a9b837b38eb232958795e24f5698cd905a7/src/py7dtd/bots/crack_passcode.py#L91-L96

Fixed in https://github.com/tassoneroberto/py7dtd/commit/737b69132bcf30f0c859571f5fa1239aa8e72768


can't use NFC on Latitude E7270

Hello,
I have some problems to use the NFC on my Dell Latitude E7270 (with ID 0a5c:5834 Broadcom Corp. 5880).
I have ubuntu 22.04 on it.
When I try to enable the NFC using your python script, there is a communication between your python script and the device
nuliel@nuliel-Latitude-E7270:~/controlvault2-nfc-enable$ ./nfc.py on
INFO:__main__:Looking for supported device...
INFO:__main__:Found 0A5C:5834
DEBUG:cvcomm:Enumerating interfaces...
DEBUG:cvcomm:Interface found: INTERFACE 3: Vendor Specific
DEBUG:cvcomm:Enumerating endpoints...
DEBUG:cvcomm:BULK IN found: ENDPOINT 0x84: Bulk IN
DEBUG:cvcomm:BULK OUT found: ENDPOINT 0x4: Bulk OUT
DEBUG:cvcomm:Endpoint discovery successful.
INFO:__main__:Handler ControlVault2 (Broadcom ControlVault 2)
INFO:__main__:Turning NFC on...

But when I run pcsc_scan, I can't see any NFC card:
nuliel@nuliel-Latitude-E7270:~/controlvault2-nfc-enable$ pcsc_scan
Using reader plug'n play mechanism
Scanning present readers...
0: Broadcom Corp 5880 [Contacted SmartCard]<PHONE_NUMBER>ABCD) 00 00
1: Broadcom Corp 5880 [Contactless SmartCard]<PHONE_NUMBER>ABCD) 01 00

Sun Oct 29 09:29:51 2023
 Reader 0: Broadcom Corp 5880 [Contacted SmartCard]<PHONE_NUMBER>ABCD) 00 00
  Event number: 0
  Card state: Card removed,
 Reader 1: Broadcom Corp 5880 [Contactless SmartCard]<PHONE_NUMBER>ABCD) 01 00
  Event number: 0
  Card state: Card removed,

Note that I have not changed the identifier of the device:<PHONE_NUMBER>ABCD seems to be set by default.
I already installed the driver (Dell-ControlVault2-Driver-and-Firmware_N23KC_WIN64_<IP_ADDRESS>_A21_01.EXE) on a windows 10 vm with the Broadcom 5880 given to the vm. So the controlvault2 device should be updated. Note that I never succeeded to use the fingerprint reader on the windows vm, but maybe it's not link with my problem with NFC.
I installed freeDOS on a usb key to run ushdiag, but this program can't see anything on USB... (maybe a problem with freeDOS or the program is too old, I don't know).
My goal is to use my yubikey with this NFC reader. For the tests, I try with a random smartcard (a smartcard for transport that is recognized with the smartcard reader of my laptop (ATR received), but not recognized by the NFC reader), and with my yubikey.
Do you know why I can't use NFC? Is the sequence sent by your script always ok with this firmware? Is there another requirement that I've not done?

Note that I never succeeded to use the fingerprint reader on the windows vm, but maybe it's not link with my problem with NFC.

Contacted reader, Contactless reader and Fingerprint reader ("touch sensor") are components connected to a single chip - Broadcom 5880.
I assume you share the whole USB device to the Windows VM. Does the NFC work (card/Yubikey is detected) for you on Windows? If not, I'd say that there is some hardware issue - check the NFC antenna connection first (it is a separate component connected to the daughter board).

Hello,
Thank you for your answer. I've opened my laptop to verify that all the ribbon cables are well connected, and it seems to be the case.
On virtualbox, I share the usb device "Broadcom 5880", so fingerprint + NFC + smartcard reader. I can't share only one part.
Windows seems to recognize partially my fingerprint reader as there is a possibility to configure a fingerprint reader (but I can't add my fingerprint), and I've tested nfc with the yubico software, contactless smartcard is recognized but but my yubikey isn't recognized in nfc. So maybe it's a problem of configuration of nfc/fingerprint reader or a hardware problem :/


[AutoRelease] t2-newrelicobservability-2023-04-20-60002(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/2985
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1031

issue link:https://github.com/Azure/sdk-release-request/issues/2985


Kafka scaler sometimes fails with no matching metrics found

Report
I have a scaled object with 4 scalers: one prometheus, one cron and two Kafka on two different topics.
We have a lot of failures inside the events on the corresponding HPA like  unable to fetch metrics from external metrics API: no matching metrics found for s3-kafka-private_aoaa_anomaly_v1
The same error appears in the Keda operator logs (see bellow).
When doing a describe on the corresponding scaled objects at the time of the issue, the metric is listed in the External Metric Names but there is no entry of it in the Health: section.
Describe of the scaled objet:
Name:         vcstream-gen-anomaly
Namespace:    vcstream-dev
Labels:       app.kubernetes.io/managed-by=Helm
              scaledobject.keda.sh/name=vcstream-gen-anomaly
Annotations:  meta.helm.sh/release-name: vcstream-gen-anomaly
              meta.helm.sh/release-namespace: vcstream-dev
API Version:  keda.sh/v1alpha1
Kind:         ScaledObject
Metadata:
  Creation Timestamp:  2022-01-10T15:19:18Z
  Finalizers:
    finalizer.keda.sh
  Generation:  6
    Manager:         keda-adapter
    Operation:       Update
    Time:            2022-02-16T07:41:36Z
  Resource Version:  335673688
  UID:               d24419d0-0360-4ab4-b9dc-a2b1f161da1c
Spec:
  Advanced:
    Restore To Original Replica Count:  true
  Cooldown Period:                      60
  Fallback:
    Failure Threshold:  3
    Replicas:           1
  Max Replica Count:    6
  Min Replica Count:    1
  Scale Target Ref:
    Name:  vcstream-gen-anomaly
  Triggers:
    Metadata:
      Desired Replicas:  1
      End:               59 18 * * *
      Start:             0 8 * * *
      Timezone:          Europe/Brussels
    Type:                cron
    Metadata:
      Metric Name:     process_cpu_usage
      Query:           avg(process_cpu_usage{component="vcstream-gen-anomaly", namespace="vcstream-dev"} * 100) > 5 OR on() vector(0)
      Server Address:  http://prometheus-server.monitoring.svc.cluster.local
      Threshold:       75
    Type:              prometheus
    Authentication Ref:
      Name:  keda-trigger-auth-kafka-credential
    Metadata:
      Bootstrap Servers:    decathlon-aoaa-vcstream-dev-01-peered-aoaa.aivencloud.com:12658
      Consumer Group:       vcstream-gen-anomaly
      Lag Threshold:        100
      Offset Reset Policy:  latest
      Topic:                private_aoaa_anomaly_v1
    Type:                   kafka
    Authentication Ref:
      Name:  keda-trigger-auth-kafka-credential
    Metadata:
      Bootstrap Servers:    decathlon-aoaa-vcstream-dev-01-peered-aoaa.aivencloud.com:12658
      Consumer Group:       vcstream-gen-anomaly
      Lag Threshold:        100
      Offset Reset Policy:  latest
      Topic:                private_aoaa_deadletter_v1
    Type:                   kafka
Status:
  Conditions:
    Message:  ScaledObject is defined correctly and is ready for scaling
    Reason:   ScaledObjectReady
    Status:   True
    Type:     Ready
    Message:  Scaling is performed because triggers are active
    Reason:   ScalerActive
    Status:   True
    Type:     Active
    Message:  No fallbacks are active on this scaled object
    Reason:   NoFallbackFound
    Status:   False
    Type:     Fallback
  External Metric Names:
    s0-cron-Europe-Brussels-08xxx-5918xxx
    s1-prometheus-process_cpu_usage
    s3-kafka-private_aoaa_anomaly_v1
    s3-kafka-private_aoaa_deadletter_v1
  Health:
    s0-cron-europe-brussels-08xxx-5918xxx:
      Number Of Failures:  0
      Status:              Happy
    s1-prometheus-process_cpu_usage:
      Number Of Failures:  0
      Status:              Happy
    s3-kafka-private_aoaa_deadletter_v1:
      Number Of Failures:  0
      Status:              Happy
  Last Active Time:        2022-02-16T09:12:16Z
  Original Replica Count:  1
  Scale Target GVKR:
    Group:            apps
    Kind:             Deployment
    Resource:         deployments
    Version:          v1
  Scale Target Kind:  apps/v1.Deployment
Events:               <none>

Describe of the HPA:
Name:                                                              keda-hpa-vcstream-gen-anomaly
Namespace:                                                         vcstream-dev
Labels:                                                            app.kubernetes.io/managed-by=Helm
                                                                   app.kubernetes.io/name=keda-hpa-vcstream-gen-anomaly
                                                                   app.kubernetes.io/part-of=vcstream-gen-anomaly
                                                                   app.kubernetes.io/version=2.6.0
                                                                   scaledobject.keda.sh/name=vcstream-gen-anomaly
Annotations:                                                       <none>
CreationTimestamp:                                                 Mon, 10 Jan 2022 16:19:18 +0100
Reference:                                                         Deployment/vcstream-gen-anomaly
Metrics:                                                           ( current / target )
  "s0-cron-Europe-Brussels-08xxx-5918xxx" (target average value):  1 / 1
  "s1-prometheus-process_cpu_usage" (target average value):        0 / 75
  "s3-kafka-private_aoaa_anomaly_v1" (target average value):       <unknown> / 100
  "s3-kafka-private_aoaa_deadletter_v1" (target average value):    0 / 100
Min replicas:                                                      1
Max replicas:                                                      6
Deployment pods:                                                   1 current / 1 desired
Conditions:
  Type            Status  Reason                   Message
  ----            ------  ------                   -------
  AbleToScale     True    ReadyForNewScale         recommended size matches current size
  ScalingActive   False   FailedGetExternalMetric  the HPA was unable to compute the replica count: unable to get external metric vcstream-dev/s3-kafka-private_aoaa_anomaly_v1/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: vcstream-gen-anomaly,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: no matching metrics found for s3-kafka-private_aoaa_anomaly_v1
  ScalingLimited  False   DesiredWithinRange       the desired count is within the acceptable range
Events:
  Type     Reason                   Age                    From                       Message
  ----     ------                   ----                   ----                       -------
  Warning  FailedGetExternalMetric  109s (x7439 over 46h)  horizontal-pod-autoscaler  unable to get external metric vcstream-dev/s3-kafka-private_aoaa_anomaly_v1/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: vcstream-gen-anomaly,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: no matching metrics found for s3-kafka-private_aoaa_anomaly_v1

Expected Behavior
No failure event on the HPA
Actual Behavior
Failure event on the HPA and the metric is show as <unknown>.
Steps to Reproduce the Problem
No idea how to reproduce it.
Logs from KEDA operator
E0216 09:14:02.481279       1 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"no matching metrics found for s3-kafka-private_aoaa_anomaly_v1"}: no matching metrics found for s3-kafka-private_aoaa_anomaly_v1

KEDA Version
2.6.0
Kubernetes Version
1.19
Platform
Google Cloud
Scaler Details
prometheus, kafka, cron
Anything else?
No response

You have probably hit this issue: https://github.com/kedacore/keda/issues/2592
I recommend you to update to 2.6.1

@zroubalik upgrading it now ;), thanks for the info.
I'll give feedback after upgrade and a few hours to see if the failures still happened.

@zroubalik so after a few hours running with 2.6.1 I confirm that this issue is fixed ;)
I'm closing it now.

In version 2.7.1 it still happening.

@zroubalik, i'm still with this problem also.
my keda version: 2.7.1
I created scaledObjet with kafka consumer.

$ kubectl describe hpa keda-hpa-ccs-relationship-worker-metrics --namespace ccs-dev
...
Conditions:
  Type           Status  Reason                   Message
  ----           ------  ------                   -------
  AbleToScale    True    SucceededGetScale        the HPA controller was able to get the target's current scale
  ScalingActive  False   FailedGetExternalMetric  the HPA was unable to compute the replica count: unable to get external metric ccs-dev/s0-kafka-alias-bank-account-events/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: ccs-relationship-worker-metrics,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: the server could not find the requested resource (get s0-kafka-alias-bank-account-events.external.metrics.k8s.io)
Events:
  Type     Reason                   Age                   From                       Message
  ----     ------                   ----                  ----                       -------
  Warning  FailedGetExternalMetric  43s (x4078 over 17h)  horizontal-pod-autoscaler  unable to get external metric ccs-dev/s0-kafka-alias-bank-account-events/&LabelSelector{MatchLabels:map[string]string{scaledobject.keda.sh/name: ccs-relationship-worker-metrics,},MatchExpressions:[]LabelSelectorRequirement{},}: unable to fetch metrics from external metrics API: the server could not find the requested resource (get s0-kafka-alias-bank-account-events.external.metrics.k8s.io)

Boa tarde @johnnytardin, voce conseguiu algo?


Focus compose box when LHN report clicked

<If necessary, assign reviewers that know the area or changes well. Feel free to tag any additional reviewers you see fit.>
Details

When a user clicks on a chat from the LHN, the ReportView component updates, showing the latest conversation. At this point, we want the compose box at the bottom to be focused so that users can quickly and efficiently start typing a new message.
This change will make the compose box (ReportActionCompose) automatically get focused whenever the reportID prop changes, which happens whenever a user clicks on a different chat / report - not just via the LHN.
Fixed Issues

Fixes https://github.com/Expensify/Expensify/issues/158106
Tests

View any chat
Open a new chat by clicking it on the LHN
See the compose box automatically get focused

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[ ] iOS
[ ] Android

Screenshots

https://user-images.githubusercontent.com/3885503/112335496-f5c8fa80-8cc4-11eb-8664-41baf4e265ac.mov
Web

See above
Mobile Web

Not needed
Desktop

See above
iOS

Not needed
Android

Not needed

Sorry @johnmlee101 - unassigning b/c i accidentally requested pullerbear twice 😅

Title:
[Chat] mWeb - <IP_ADDRESS> - Chat - Key pad does not open in iOS Safari after tapping on conversation
Expected Result:
The box is highlighted blue and key pad does open
Actual Result:
Key pad does not open
Action Performed:

Go to https://staging.expensify.cash
Log in with any user
Open a new chat by clicking it on the LHN
See the compose box automatically get focused

Build version : <IP_ADDRESS>
Is it reproducible in production? : Yes
Device and OS: iPhone 8/iOS 14.2 / Safari browser
Attachment
Video

Hi @isagoico, since this issue is reproducible in production, I think it should not be a DeployBlockerCash. Removing that label now and checking it off on the deploy checklist. When you have a moment, can you please create a new issue for the bug you reported in the comment above?

All done! New issue can be found here https://github.com/Expensify/Expensify.cash/issues/2108


Available versions

$ pip install kivymd==2.0.1
ERROR: Could not find a version that satisfies the requirement kivymd==2.0.1 (from versions: 0.1.0, 0.1.1, 0.1.2, 0.100.2, 0.102.0, 0.102.1, 0.103.0, 0.104.0, 0.104.1, 0.104.2, 1.0.1, 1.0.2, 1.1.1, 1.2.0)
ERROR: No matching distribution found for kivymd==2.0.1
(kivymd-venv) mybox ~/Code/Python Projects/Samples
same result for 2.0.0 on linux mint 20
The 2.0.0 version posted on the main git page is not in the version list, and the master.zip installs what appears to be a dev version: 2.0.1.dev0

pip install https://github.com/kivymd/KivyMD/archive/master.zip

Hi Champ,
Did that as mentioned in the ticket that the master.zip installs 2.0.1.dev0 which looks like a dev branch.. not stable production.
Either way the main git page states the installation as follows:
pip install kivymd==2.0.0
Which is NOT in the list of install-able versions when pip installs as previously stated:
from versions: 0.1.0, 0.1.1, 0.1.2, 0.100.2, 0.102.0, 0.102.1, 0.103.0, 0.104.0, 0.104.1, 0.104.2, 1.0.1, 1.0.2, 1.1.1, 1.2.0)
All this started because the 2.0.1.dev0 branch/version is throwing an error on a module that should exist (using the master.zip you mentioned, I had already tried):
from kivymd.uix.tab import MDTabsBase
ImportError: cannot import name 'MDTabsBase' from 'kivymd.uix.tab' (/home/paul/.pyenv/versions/kivymd-venv/lib/python3.11/site-packages/kivymd/uix/tab/init.py)

https://kivymd.readthedocs.io/en/latest/components/tabs/

https://kivymd.readthedocs.io/en/latest/components/tabs/#api-break

Thank you Yuri for your prompt response, you are very quick!
But the original posted issue was about the pip install being broken, and its still broke and that version is unavailable:
$ pip install kivymd==2.0.0
ERROR: Could not find a version that satisfies the requirement kivymd==2.0.0 (from versions: 0.1.0, 0.1.1, 0.1.2, 0.100.2, 0.102.0, 0.102.1, 0.103.0, 0.104.0, 0.104.1, 0.104.2, 1.0.1, 1.0.2, 1.1.1, 1.2.0)
ERROR: No matching distribution found for kivymd==2.0.0
This is still an open issue, especially because the page states that method of install.

The needs are stable versions to build projects, not continuous evolving masters

The needs are stable versions to build projects, not continuous evolving masters

Version 2.0.0 will no longer break the existing API.

Please stop talking about version 2.0.0 because there is no version 2.0.0 available, as all the comments try to show:
$ pip install kivymd==2.0.0
ERROR: Could not find a version that satisfies the requirement kivymd==2.0.0 (from versions: 0.1.0, 0.1.1, 0.1.2, 0.100.2, 0.102.0, 0.102.1, 0.103.0, 0.104.0, 0.104.1, 0.104.2, 1.0.1, 1.0.2, 1.1.1, 1.2.0)
ERROR: No matching distribution found for kivymd==2.0.0

https://github.com/kivymd/KivyMD/issues/1609#issuecomment-1925442922

master is not a stable version and is not suitable for building projects

Version 2.0.0 has not been released yet.

Ok, this is the source of confusion because kivymd's readme.md states the opposite

The same with ghost version 1.2.0 that does not exist in documentation nor github tags just a magic pip package taken out of nowhere and api breaking mentions in the latest docs. What was the reason to release unsupported version that is not a version? :-(
Please create tags for 1.2.0 and 2.0.0 releases. Master currently shows version 2.0.1.dev0.
I ran away from JavaScript to avoid lack of versioning and maintenance nightmare. Please avoid this here.
Until versioning is resolved KivyMD is NO GO. Once people start developing their own widgets there will be no incentive to go back to KivyMD :-(
I know there may be problems with 2.0.0 but you can safely release a 2.0.0 and make fixes with time. People would at least have a reference ground to work on. This is really important. Please consider many people asking for that and thanks in advance :-)

The same with ghost version 1.2.0 that does not exist in documentation nor github tags just a magic pip package taken out of nowhere and api breaking mentions in the latest docs. What was the reason to release unsupported version that is not a version? :-(
Please create tags for 1.2.0 and 2.0.0 releases. Master currently shows version 2.0.1.dev0.
I ran away from JavaScript to avoid lack of versioning and maintenance nightmare. Please avoid this here.
Until versioning is resolved KivyMD is NO GO. Once people start developing their own widgets there will be no incentive to go back to KivyMD :-(
I know there may be problems with 2.0.0 but you can safely release a 2.0.0 and make fixes with time. People would at least have a reference ground to work on. This is really important. Please consider many people asking for that and thanks in advance :-)
@HeaTTheatR please do not get angry, we are very close to a first release, its either stay with KivyMD 1.1.1 or try switching to 2.0.0, or avoid it at all. Having a 2.0.0 release would give us a reference point. So far there are two releases announced that does not exist (1.2.0 and 2.0.0) and that does not look good.

Thanks for the feedback. KivyMD version 2 has one serious bug so far - https://github.com/kivymd/KivyMD/issues/1601
This bug is almost fixed. As soon as I merge my local changes with the master branch and we test it for a while, then we can release version 2

thanks really @HeaTTheatR
i was so glad when i had of the release earlier this year because the documentation looks really promissing with alot of new improvement.
actually one of the issues that drove me back immidiatley was when i couldn't set auto_dismiss=False, it was stated like this in the documentations but it obviously not part of the valid arguement.

thanks really @HeaTTheatR i was so glad when i had of the release earlier this year because the documentation looks really promissing with alot of new improvement.
actually one of the issues that drove me back immidiatley was when i couldn't set auto_dismiss=False, it was stated like this in the documentations but it obviously not part of the valid arguement.

You can create an appropriate issue

As of today (April 30th), the issue still continues and the README file still has the misleading info that doesn't work:
pip install kivymd==2.0.0
Although @HeaTTheatR first comment works like a charm, please consider to amend this in the README file.
Thanks!

Esta história de versões novas quebrarem as construções antigas é muito ruim... MDToolBar não funciona, pois mudou para MD...
Outro problema é estar lendo uma Documentação de algo que não funciona!


Fixed defect in tabular NN caused by pynvml

Issue #, if available:
Description of changes:
Fixed defect in tabular NN caused by pynvml introduced in #94
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-153-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-153/1/index.html


Moved: Neat's input and output parameters are useless if a network is provided

This suggestion has been moved from Neataptic.
https://github.com/wagenaartje/neataptic/issues/144

So I checked the code, at least within the neat module, the first 2 arguments (inputs and outputs) are only use to create the random network if none is provided.
This means that if one is, those 2 are useless and hence the calling code looks awkward. I think it should make more sense to make inputs and outputs also options (heck, make it accept just a single options object) and hence they are optional and only used (and required) if no template network is provided.

An extra comment, I notice that when a network is provided, it is used as a template as is. That means that either passing a random network or any other, means the first generation is all equal and does the same thing (AFAIU). Maybe it'd make sense to randomly mutate each template the first time?

This has functionally been resolved by Neat's support for constructor overloading:
https://github.com/liquidcarrot/carrot/blob/e7eb40acfbf3eb1cf320c5ed37520dfeddd20fef/src/neat.js#L92-L111
Closing for now


Unit tests are not executed

Is this a bug report?
Yes
Can you also reproduce the problem with npm 4.x?
I am using latest yarn 0.27.5 and npm 5.2.0 on Windows.
Environment

Node 8.1.3
Yarn 0.27.5 or NPM 5.2.0
<EMAIL_ADDRESS>Windows

Steps to Reproduce

Run yarn test or npm test (is running script react-scripts test --env=jsdom)

It says: "Determining test suites to run..." -> "Press a to run all tests."

After hitting a

You see:

No tests found
In C:\PROJECT
  18490 files checked.
  testMatch: C:\PROJECT\src\**\__tests__\**\*.js?(x),C:\PROJECT\src\**\?(*.)(spec|test).js?(x) - 6 matches
  testPathIgnorePatterns: \\node_modules\\ - 18490 matches
Pattern: "" - 0 matches

No tests were executed but there are tests inside in PROJECT/src/ eg. default App.test.js - these tests are being executed when saving changes while in jest watch mode.
Expected Behavior
All tests inside src/**/*.test.js should be executed
Note (Temporary workaround)
Using Windows 10 bash (ubuntu) it's running fine, so looks like it affects only Windows (tested on both - Win 7 & 10)

FYI Maybe it's related to https://github.com/facebook/jest/issues/4033

Hello. I can confirm this issue on my machine as well. Thanks to the note's temporary workaround (using bash), I'm able to execute my tests again.
To make sure it's nothing with my project's setup, I created a clean create-react-app project in C:\my-app. The output of running all tests:
No tests found
In C:\Users\mbeierling\Projects\test\my-app
  14439 files checked.
  testMatch: C:\my-app\src\**\__tests__\**\*.js?(x),C:\my-app\src\**\?(*.)(spec|test).js?(x) - 1 match
  testPathIgnorePatterns: \\node_modules\\ - 14439 matches
Pattern: "" - 0 matches

The "1 match" will have to be the default src/App.test.js file, created when running the create-react-app command. Still, no test is actually executed and the "No tests found" output is shown.
When run using bash on Windows, the output is:
yarn test v1.0.2
$ react-scripts test --env=jsdom
  console.error node_modules\fbjs\lib\warning.js:33
    Warning: React depends on requestAnimationFrame. Make sure that you load a polyfill in older browsers. http://fb.me/react-polyfills

 PASS  src\App.test.js
  √ renders without crashing (24ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        2.772s
Ran all test suites related to changed files.

Hi,
I solved this issue by removing the locally installed watchman path variable. When running jest --verbose I got "@providesModule naming collision" warnings as reported in issue.
After removing the variable, jest is matching and executing all tests again.
Maybe this workaround helps some of you.
My system is running:

Microsoft Windows 10 Enterprise (x64)
Version	10.0.15063 Build 15063

Thank you very much @zehbauer, removing watchman from my path env-var worked!


chk smart bar color

For me it is like blank i guess not visible due to color?

Could you tell me what version of FlorisBoard you are using? You can usually see this by scrolling down and clicking about on the main screen or by pressing the three dots.
Thanks

Could you tell me what version of FlorisBoard you are using? You can usually see this by scrolling down and clicking about on the main screen or by pressing the three dots.
Thanks

Tested on 0.3.15beta1 too

At the time of installing the theme, did you use the .json file from the master branch or the .flex from the 0.3.14 branch?
Since 0.3.14 themes use a new format. As 0.3.14 is now available on F-Droid I will push the 0.3.14 branch to master so if you try and reinstall it with the new .flex file it should work.

At the time of installing the theme, did you use the .json file from the master branch or the .flex from the 0.3.14 branch?
Since 0.3.14 themes use a new format. As 0.3.14 is now available on F-Droid I will push the 0.3.14 branch to master so if you try and reinstall it with the new .flex file it should work.

.flex

At the time of installing the theme, did you use the .json file from the master branch or the .flex from the 0.3.14 branch?
Since 0.3.14 themes use a new format. As 0.3.14 is now available on F-Droid I will push the 0.3.14 branch to master so if you try and reinstall it with the new .flex file it should work.

.flex

Welp .json has been redundent & theme importer wont accept that since 0.3.14 so i used .flex

At the time of installing the theme, did you use the .json file from the master branch or the .flex from the 0.3.14 branch?
Since 0.3.14 themes use a new format. As 0.3.14 is now available on F-Droid I will push the 0.3.14 branch to master so if you try and reinstall it with the new .flex file it should work.

1st one is some other theme with smart
Nd 2nd one is darcula theme

Yeah I see what the issue was now. I need to add the colours for the smartbar to the theme. I'm working on the fix now

Yeah I see what the issue was now. I need to add the colours for the smartbar to the theme. I'm working on the fix now

Sure thing

The issue should now be fixed. Please reopen if it persists


Added Typetalk Plugin to the list

@sonots
Hi, I created alerty plugin for Typetalk.
Could you add this to the list? :pray:

Sorry to be late. Thank you!


Redis object should be stored inside Site

Now that we have a Site object, we can inject the redis client into it, so we don't need to pass around both all the time. We'll lose the ability to scatter a single site over multiple redises, but I don't think we want that anyway.

Redis will be wrapped by a Source object when the time comes.

Redis will be wrapped by a Source object when the time comes.


New front page

The front page (landing page) will have the role to present the market to the user.
Maybe we can have a section for news/announcements
Have call to action for publish, maybe other
Have one section for each category (

assets  with action to /assets
pools with action to /pools
best sellers (accounts)

The order is not relevant, it's just the order i thought them up

We can pick some nice text from oceanprotocol.com and also embed a video of one of the demos @kremalicious made (couldn't find then on youtube, hope we have them saved somewhere)
Fetch total tv for each main network, 1 subgraph call for each
Fancy call to action, maybe we can add something extra there
Best selling assets . Fetch top 3 for each main net and the just show the top 3.  It will be possible in the upcoming subgraph update
Top tvl pools. Fetch top 3 pool for each main net and the order them. I think it would look nice to have some teasers for the pool as well. We can show the tokens, tvl , ?
Quick tutorials . Nothing from here exists, these titles are just quick ideas. Ideally we need a page for each with nice explanations for the concept. flow, metadata, etc.
Best sellers. Fetch top 3 from all networks.

initial launch demo: https://www.youtube.com/watch?v=KiDg0ry6oV4
CtD launch demo: https://www.youtube.com/watch?v=RxrkUd9pds0

hello, here is the first version of the design:
https://www.figma.com/file/e5KaRp3fayJYPQR9JUBYPK/Homepage-draft?node-id=2%3A35


Handle up/down normals when drawing a circle

When using Vector3.up or Vector3.down as the normal for GizmosPlus.Circle(), the circle gets draw incorrectly with a radius of 0. This happens because the calculation for getting the component up and left vectors for the circle is done by taking the cross product of the normal and Vector3.up, and taking the cross product of two parallel vectors returns the zero vector.
To handle this, I've added an extra check for the case where the calculated left vector is zero and have the drawing logic use Vector3.left and Vector3.forward as the component vectors to ensure that the circle draws correctly in the X-Z plane.

I also noticed that GizmosPlus.Arrow() had the same issue, causing the head to not draw correctly for a vertical up/down normal. I've updated the pull request to catch all other cases where this issue came up, which seems to just be Arrow() and Rectangle().

Thanks for the PR! Looks good!


warn Package react-native-vector-icons has been ignored because it contains invalid configuration. Reason: "dependency.assets" is not allowed

warn Package react-native-vector-icons has been ignored because it contains invalid configuration. Reason: "dependency.assets" is not allowed

What is the fix oh dearest @cyberonics-jasim if I may ask? 😄


Add contract verification method to TronBox

Hello! I'd like to suggest adding a method for contract verification directly to TronBox. This would simplify the verification process for developers and enhance the usability of the tool. It might be worth considering integration with the Tronscan API for automatic contract verification after deployment. I'd be happy to discuss possible approaches and solutions if this is relevant for the project. Thank you!

Thanks! We are developing the contract flatten method, after which we will develop the contract verification method.

Any updates on this @llwslc ?


german localization

Codecov Report

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

@@           Coverage Diff           @@
##           master     #356   +/-   ##
=======================================
  Coverage   99.26%   99.26%
=======================================
  Files          18       18
  Lines         410      410
=======================================
  Hits          407      407
  Misses          3        3

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 65cfe19...6596623. Read the comment docs.

Danke!


chore(appLoc): added 'appLoc' sanitation

Issue
closes #119
Intent
Sanitize appLoc.
Implementation
Added sanitizeAppLoc function and used it in getBuildTargets and getTargetToBuild functions.
Checks

[x] Code is formatted correctly (npm run lint:fix).
[x] Any new functionality has been unit tested.
[x] All unit tests are passing (npm test).

[x] All CI checks are green.
[x] JSDoc comments have been added or updated.

:tada: This PR is included in version 1.13.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Debugger:Different representation in Watch window between VS & VSCode

Environment data
dotnet --info output:
VS Code version:
C# Extension version:
Steps to reproduce
1 Set bp at line of "_appSettings = options.Value;"
2 Press F5 to start debugging
3 Change to watch window and input an expression of "this.good()" to evaluate
Expected  behavior
Prompt wrong information rather than "not available"
Actual behavior
I have tried this in VS, and VS reports that cannot find the definition for good. Is it a by-design behavior in VSCode? At the same time, when you input this express in debug console in VSCode, it would tell nothing and this would lead customers' feel confused.

@ClaireKang, could you please provide the dotnet, VS Code, and C# version information, as well as any other unusual configuration you may have? I just tried to reproduce this on my machine, and got the expected error message that you saw in VS, both in the watch window and in the debug console:

This is vscode and other plugins' version, and I use visual studio2015 to retest this result.

This pic is vscode and plugins' version, and I use Visual Studio 2015 to retest it

This pic is vscode and plugins' version, and I use Visual Studio 2015 to retest it


Problems with brew-cask

Hi,
i use kitchenplan for quite a time now and provisioned some computers with it. Today i wanted to run on a new system but got stuck at:

package[brew-cask] action install[2016-02-01T16:55:08+01:00] INFO: Processing package[brew-cask] action install (homebrewalt::default line 59)
/usr/local
Error: HOMEBREW_BREW_FILE was not exported! Please call bin/brew directly!
================================================================================
Error executing action install on resource 'package[brew-cask]'
SystemExit
exit
Cookbook Trace:
/opt/kitchenplan/vendor/cookbooks/homebrewalt/libraries/homebrew_package.rb:88:in require' /opt/kitchenplan/vendor/cookbooks/homebrewalt/libraries/homebrew_package.rb:88:in get_version_from_formula'
/opt/kitchenplan/vendor/cookbooks/homebrewalt/libraries/homebrew_package.rb:68:in current_installed_version' /opt/kitchenplan/vendor/cookbooks/homebrewalt/libraries/homebrew_package.rb:37:in load_current_resource'
Resource Declaration:
In /opt/kitchenplan/vendor/cookbooks/homebrewalt/recipes/default.rb
59: package "brew-cask" do
60:   options "--HEAD"
61: end
62:
Compiled Resource:
Declared in /opt/kitchenplan/vendor/cookbooks/homebrewalt/recipes/default.rb:59:in `from_file'
package("brew-cask") do
action :install
retries 0
retry_delay 2
guard_interpreter :default
options "--HEAD"
package_name "brew-cask"
timeout 900
cookbook_name :homebrewalt
recipe_name "default"
end

[2016-02-01T16:55:08+01:00] INFO: Running queued delayed notifications before re-raising exception
[2016-02-01T16:55:08+01:00] DEBUG: Re-raising exception: SystemExit - package[brew-cask] (homebrewalt::default line 59) had an error: SystemExit: exit
/usr/local/Library/Homebrew/utils.rb:117:in exit'   /usr/local/Library/Homebrew/utils.rb:117:in odie'
/usr/local/Library/Homebrew/config.rb:31:in <top (required)>'   /usr/local/Library/Homebrew/global.rb:18:in require'
/usr/local/Library/Homebrew/global.rb:18:in <top (required)>'   /opt/kitchenplan/vendor/cookbooks/homebrewalt/libraries/homebrew_package.rb:88:in require'
/opt/kitchenplan/vendor/cookbooks/homebrewalt/libraries/homebrew_package.rb:88:in get_version_from_formula'   /opt/kitchenplan/vendor/cookbooks/homebrewalt/libraries/homebrew_package.rb:68:in current_installed_version'
/opt/kitchenplan/vendor/cookbooks/homebrewalt/libraries/homebrew_package.rb:37:in load_current_resource'   /opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/provider.rb:104:in run_action'
/opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/resource.rb:648:in run_action'   /opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/runner.rb:49:in run_action'
/opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/runner.rb:81:in block (2 levels) in converge'   /opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/runner.rb:81:in each'
/opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/runner.rb:81:in block in converge'   /opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/resource_collection.rb:98:in block in execute_each_resource'
/opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/resource_collection/stepable_iterator.rb:116:in call'   /opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/resource_collection/stepable_iterator.rb:116:in call_iterator_block'
/opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/resource_collection/stepable_iterator.rb:85:in step'   /opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/resource_collection/stepable_iterator.rb:104:in iterate'
/opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/resource_collection/stepable_iterator.rb:55:in each_with_index'   /opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/resource_collection.rb:96:in execute_each_resource'
/opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/runner.rb:80:in converge'   /opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/client.rb:345:in converge'
/opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/client.rb:431:in do_run'   /opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/client.rb:213:in block in run'
/opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/client.rb:207:in fork'   /opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/client.rb:207:in run'
/opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/application.rb:236:in run_chef_client'   /opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/application/solo.rb:226:in block in run_application'
/opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/application/solo.rb:218:in loop'   /opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/application/solo.rb:218:in run_application'
/opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/lib/chef/application.rb:55:in run'   /opt/kitchenplan/vendor/bundle/ruby/2.0.0/gems/chef-11.18.12/bin/chef-solo:25:in <top (required)>'
vendor/bin/chef-solo:16:in load'   vendor/bin/chef-solo:16:in '
I can't figure out whats the problem. Installing casks by hand works without any problems. I guess it's a problem with homebrew-alt but i'm not sure.
I saw superlumic but i don't have the time now to migrate all my configuration.

Here the output on pastern without markdown formatting problems:
http://pastebin.com/aN1JXKQF

+1


General Issue: Experimenting with Docker Image for Contributor

Background Information
Currently, when users want to contribute or create a post in the repository, they must install all R package dependencies that the repository requires before the contributor blog page can be rendered.
Related issue: https://github.com/pharmaverse/blog/issues/108
This could hinder the user's ability to move quickly and may potentially pollute their local environment. Users should be able to contribute to the repository without having to install all dependencies.
Proposal
My proposal is to create a Docker image with all the dependencies installed and push this to the registry.
Users can pull and use the image for development before pushing commits to the repository.

Plan

use rocker/rstudio as a base for users
install quarto
install R package dependencies

@bms63
I pushed a registry to pharmaverse but don't have access to link it to the blog repo.

Can you do this?

I clicked some buttons! https://github.com/pharmaverse/blog/pkgs/container/blog
let me know if it worked.

It works!

Alright, two more things on my to-do list and then we can write a blog and have people try this to get feedback.
👍🏼


Collect key browser info each time a user logs in

To help with debugging we could store key browser details (e.g. Browser vendor, version, OS) each time a user logs in.
We do not need this information for analytics however it can be useful when troubleshooting and investigating reported issues.

A logsystem:
logs: [
  :uuid: [
    {
      date: timestamp,
      type: 'login',
      data: {
        browser: 'IE',
        version: '2',
        os: 'iOs'
      }
    },
    {
      date: timestamp,
      type: 'click',
      data: '.info-click--save-and-continue'
    },
    {
      date: timestamp,
      type: 'click',
      data: {
        route: '/',
        component: 'asssssessssssment',
        button: '.info-click--save-and-continue'
      }
    }
  ]
]

@warrensearle I've tested it and it works as intended.


Show transaction QR

Tested @ Chrome/OS X only

Don't pull yet. Occasionally hides the raw & signed tx strings for some reason.

Should be fine now. I still get the hidden textarea bug occasionally but that isn't related to these changes. Tested @ Chrome & FF on OS X.

Gak tahu

I believe this is outdated, please open a new PR if possible


Additional unnecessary leading spaces in list items not removed

remark nicely reformats
1. abc
2.  def
   ghi
3. jkl

and
1. abc
2. def
    ghi
3. jkl

but sometimes additional leading spaces are kept in the output.
e.g.
1. abc
2. def
     ghi
3. jkl

becomes
1.  abc
2.  def
     ghi
3.  jkl

and
* abc
* def
   ghi
* jkl

comes out as
*   abc
*   def
     ghi
*   jkl

Is there a reason for keeping those spaces?

The reason that the lists are reformatted is because they can cause serious problems between all the different vendors out there (tab-size indent works everywhere).
There’s no reason to change the paragraphs, as those are harmless, so I’d rather not have the user’s style mangled.
This could however easily be done through a plug-in. I wrote this as a quick example:
var remark = require('remark');
var visit = require('unist-util-visit');

var doc = ` indented

<!-- br -->

not-indented
 indented

<!-- br -->

1. abc
2.  indented
   indented
3. jkl

<!-- br -->

1. abc
2. indented
    indented
3. jkl

<!-- br -->

1. abc
2. indented
     indented
3. jkl
`

function plugin() {
    return function (tree) {
        // Trim first text in paragraph.
        visit(tree, 'paragraph', function (node) {
            var head = node.children[0];

            if (head && head.type === 'text') {
                head.value = head.value.replace(/^\s+/, '');
            }
        });

        // Trim after newlines in text.
        visit(tree, 'text', function (node) {
            node.value = node.value.replace(/\n\s+/g, '\n');
        });
    }
}

console.log(remark().use(plugin).process(doc).toString());


Infidelity optimizer breaks with Qubit Hilbert space

Following the example code in the readme file, but changing the Hilbert space to Qubit instead of Spin results in only NaNs being calculated for the fidelity at every iteration. Changing the data type for higher precision did not make any difference.
import netket as nk
import netket_fidelity as nkf

# Create the Hilbert space and the variational states |ψ⟩ and |ϕ⟩
hi = nk.hilbert.Qubit(4)
sampler = nk.sampler.MetropolisLocal(hilbert=hi, n_chains_per_rank=16)
model = nk.models.RBM(alpha=1, param_dtype=complex)
phi = nk.vqs.MCState(sampler=sampler, model=model, n_samples=100)
psi = nk.vqs.MCState(sampler=sampler, model=model, n_samples=100)

# Transformation U
U = nkf.operator.Hadamard(hi, 0)

# Instantiate the operator to optimize the infidelity with U|ϕ⟩ by sampling from |ψ⟩ and |ϕ⟩
I_op = nkf.infidelity.InfidelityOperator(phi, U=U, U_dagger=U, is_unitary=True, cv_coeff=-1/2)

# Create the driver
optimizer = nk.optimizer.Sgd(learning_rate=0.01)
te =  nkf.driver.infidelity_optimizer.InfidelityOptimizer(phi, optimizer, U=U, U_dagger=U, variational_state=psi, is_unitary=True, cv_coeff=-0.5)

# Run the driver
te.run(n_iter=100)

I just pushed a commit ensuring that when building the operators with Qubit you get an informative error.


msglist: Gracefully ignore ill-formed image URLs.

Recently I've occasionally been seeing a red error banner at the top
of the message list (the one that says "Oh no! Something went
wrong. Try again?".)  I've only seen it when looking at #test here
on czo -- so figured there must be an oddity in some message there
that triggered whatever bug it was.
And indeed, it turns out that the trigger is a message with an image
element where the image's URL isn't a well-formed URL.  We'd been
implicitly assuming that that couldn't happen -- the server is after
all generating this HTML, and could prevent that.  But it turns out
that it doesn't.
Quite possibly the server should and in the future will refuse to
generate such elements.  But the Zulip server renders messages to HTML
immediately at send time, and in general we never go back and
re-render old messages.  (That's because if we did, then every subtle
change in Zulip's Markdown format, or even changes in its
implementation that were intended to have no effect on behavior, would
carry a risk of silently corrupting old messages.)  So even if the
server becomes stricter about this in the future, clients will still
need to handle messages with this kind of malformedness indefinitely.
(For that matter, in fact, it's possible the server already has made
that change in the two years since the message I found that triggers
this issue was sent.)
From the code, it looks like this bug has been here since we started
explicitly absolutizing these URLs, in 7ef0aebe0 in 2019.  Yet I was
pretty confident I hadn't seen it before, when I saw it sometime in
the last few weeks; and every time I've seen it since then, it's been
on the same stream and likely due to the same one message there.
So that's a little reassuring that this isn't a super common issue
to hit, at least.
Fixes: #4449

Merged, thanks!

Merged, thanks!