philio PAN04 multichannel not updating values

Home Assistant release with the issue:
0.68.0
Last working Home Assistant release (if known):
Not aware if any
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
Z-wave sensor
Description of problem:
My philio PAN04-1 zwave entity not update it's sensor reading values. When restarting my Hass.io new values are set but on change nothing happens.
Excpected
like PAN04 do a refresh of the node after updates to get the right values

I propose to add node refresh for the device in workaround.py
Pull request #15203


UI Proposal: Make activity log links so users can read the actual proposal/discussion

As it stands, I'll have to manually find the discussion/proposal whereas intuitively I want to click the log entry and get to the discussion/proposal.

Duplicate of https://github.com/paideiadao/paideia-app/issues/18


avfoundation camera support doesn't load on OS X 10.7 or 10.9

The OS X camera provider on 10.7 is supposed to be avfoundation, but I get this in my log file (using Kivy 1.8.0 on OS X 10.7.4):
[DEBUG             ] [Camera      ] Ignored  (import error)
[INFO              ] [Camera      ] Provider: opencv(['camera_avfoundation'] ignored)

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/2440883-avfoundation-camera-support-doesn-t-load-on-os-x-10-7-or-10-9?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F42681&utm_medium=issues&utm_source=github).

Same problem with Python 2.7.6  Yosemite (10.10)

This works for me on OSX 10.11 and 10.10
$ python
Python 2.7.10 (default, Sep 14 2015, 02:26:06)
[GCC 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import kivy.core.camera.camera_avfoundation
[INFO   ] [Logger      ] Record log in /Users/ben/.kivy/logs/kivy_15-10-09_11.txt
[INFO   ] [Kivy        ] v1.9.0
[INFO   ] [Python      ] v2.7.10 (default, Sep 14 2015, 02:26:06)
[GCC 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)]
[INFO   ] [Image       ] Providers: img_tex, img_imageio, img_dds, img_gif, img_sdl2 (img_pil, img_ffpyplayer ignored)
[INFO   ] [Camera      ] Provider: avfoundation
>>>

I installed kivy with:
brew install sdl2 sdl2_image sdl2_ttf sdl2_mixer gstreamer
pip install -I Cython==0.21.2
USE_OSX_FRAMEWORKS=0 pip install<EMAIL_ADDRESS>

I think we can close this issue. It has been fixed by https://github.com/kivy/kivy/commit/e56d44feeac37ed9f433afe5c59b0fa938f33216
The fix has not been released to pypi yet (https://github.com/kivy/kivy/issues/3717) so you have to install with
pip install<EMAIL_ADDRESS>
or if using Homebrew with
USE_OSX_FRAMEWORKS=0 pip install<EMAIL_ADDRESS>

Great, thanks @cbenhagen


Index Without Rewriting

There's two options right now to convert a Delta or Parquet table:

Use Convert To Qbeast Command, which does a single commit to the Delta Log with Qbeast empty metadata.
Rewrite the files. (with Spark DataFrame or SQL API)

There's a third option that goes one step further and index the files without the need of rewriting the data.

Load data from files.
Index the Dataframe.
Group by blocks and cubes.
Extract the metadata for each file and create a new AddFile.
Mark the old files without Qbeast metadata as DeleteFile.
Commit to the transaction log.

Although we would need to compute the index, it can be done incrementaly and does not change anything on the file level. Plus, we can have both sampling and data-skipping benefits (especially in petabyte datasets) if we know that small blocks of data are not available in a specific file.
This issue is to work in a PoC that would be later introduced as part of qbeast-spark features.

@fpj should we move this back to the backlog?

I think this approach has potential, but there are some drawbacks that we need to take into consideration:

Metadata generation. The unindexed files can have a very "bad" layout, making serialization and deserialization a huge problem while indexing. I agree that we need to redesign structures, but I would rather not over-engineer the issue.
The cost of Indexing + Running Optimize seems to be similar of just Indexing the files in batches as explained in #294 . Should be benchmarked, I cannot give any specific numbers.
I can understand the advantage of having an updated IndexStatus to append new data, but how much would it change if we just manage to calculate the current stats (min-max) of the existing data and initialize a unique Revision? Once we have the domain, we could safely index the new records using this latest Revision.

Although it can be beneficial, I don't think we would work on this anytime soon. I am closing this, we should come back with a formal proposal and PoC.

Another benefit highlighted by @cugni ,

All fair points, but I don't think the actual advantage of Index without Rewriting is to improve the optimization process.
As you well said, if we are going to rewrite it later, it is best to do everything at once.
What needs to be evaluated is the potential benefit of having "enhanced file skipping." Instead of just considering the min-max with the cube metadata, it would be possible to discard more files because they do not contain any cube that overlaps with an interested query.
Let's make a 1 dimension example. We have 1 file with 2 values, 10 and 99, so the minMax is 10-99; if we are interested in a range of values in the range (40, 50), we will have to open the file. Now, let's assume that we index those files, and those two items get assigned to cube AA  with domain(10,20) and cube AZ with domain (90, 100). Thanks to this information, we could easily discard this file.

Although it's a good example, this would require extra Metadata Navigation. And even if we are using DataFrames, we know that serializing/deserializing a long list of blocks with their respective CubeId's and domains has overhead.
Again, worth to give it a shot, but I would need to recollect enough numbers to feel confident!!


x/tools/go/loader: program with nested interfaces works in Go but not with the loader

This took me awhile to boil down, but the link below is the smallest possible program that illustrates this bug. The program models the DOM, which has lots of interconnected interfaces.
The weird part is that it works with go run, so it seems there must be some case missing in the loader.
I noticed some other open issues around cgo and vendoring – this program doesn't use cgo or vendoring, it's just Go code with some interfaces.
Runnable example: https://github.com/matthewmueller/deep-interface-bug
Thanks in advance for your help!

UPDATE: I tried to make a callgraph visualization to help illustrate the problem better, but it uses the loader, which can't compile this program 😅

What version of Go are you using (go version)?
go version go1.9 darwin/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
GOOS="darwin"
GOARCH="amd64"

What did you do?
Runnable example at: https://github.com/matthewmueller/deep-interface-bug
What did you expect to see?
A loaded program
What did you see instead?

invalid operation: html (variable of type github.com/matthewmueller/deep-interface-bug/window.HTMLElement) has no field or method DispatchEvent

FWIW, here's the file that doesn't work:
window.go
package window

// EventTarget interface
type EventTarget interface {
	DispatchEvent() Event
}

// Node interface
type Node interface {
	EventTarget

	ParentElement() HTMLElement
}

// Element interface
type Element interface {
	Node
}

// HTMLElement interface
type HTMLElement interface {
	Element
}

// Event interface
type Event interface {
	SrcElement() Element
}

input.go

This is probably a dup of #18395.
CC @griesemer

@matthewmueller Could you please run your code using the latest (tip) version of go/types and report back if you see the same error? If it is indeed a duplicate of #18395 go/types will now complain with a respective error.

@matthewmueller I just confirmed myself that this is indeed a duplicate of #18395. A fix is in the works, but unfortunately it's too late to get that into Go 1.10. For:
package p

// EventTarget interface
type EventTarget interface {
	DispatchEvent() Event
}

// Node interface
type Node interface {
	EventTarget

	ParentElement() HTMLElement
}

// Element interface
type Element interface {
	Node
}

// HTMLElement interface
type HTMLElement interface {
	Element
}

// Event interface
type Event interface {
	SrcElement() Element
}

var _ = HTMLElement.DispatchEvent

gotype reports:
$ gotype x.go
x.go:22:2: internal error: incomplete embedded interface Element (issue #18395)
x.go:30:9: invalid operation: HTMLElement (type) has no field or method DispatchEvent

As a temporary work-around in this case you could manually inline the methods that the Element interface embeds via the Node type. This is always possible to do manually, and in fact the fix for go/types is to just do this automatically. But it's a larger fix which is why it's not going to make it anymore this round. Sorry.
Closing as duplicate of #18395.

Thanks for the response and workaround!
@griesemer I'll definitely give this a shot. It will definitely blow up the file sizes a lot because the DOM interface are huge – hopefully that doesn't slow down the compiler.

@matthewmueller Inlining all methods manually will always work but you may not have to go to that extreme to avoid the issue. You may be able to factor our a significant subset of the methods into a new interface that you then can embed.
Again, a fix is in the works ( https://go-review.googlesource.com/c/go/+/79575 ) and you could try the patch, but it's not the final version quite yet.

Thanks for the comments, I'm not sure factoring out by hand is an option because the DOM APIs are pretty massive and I'm not idea where all the cycles lie.

Again, a fix is in the works ( https://go-review.googlesource.com/c/go/+/79575 ) and you could try the patch, but it's not the final version quite yet.

Would this require a fork to Go itself or could I bring this in as a library?

@matthewmueller You can just apply that patch (  https://go-review.googlesource.com/c/go/+/79575 ) to go/types (it's only affecting go/types) and use the updated library.
DOM implementation: Sure, let us know how to get it.


Define some install steps/requirements

Hi all,
as the subject already mentions please create some small steps to install/setup monaco or at least some prerequisitest to install... Not everybody has go already installed.
Thanks,
Steve

I will include this as part of enhancing the documentation and provide the instructions for various platforms

@dieselsteve just to be sure, you are looking for install steps because you wish to contribute to the tool, or you're looking for a way to install, so you can run it?
For just running it, you find releases here and shouldn't need go installed at all: https://github.com/dynatrace-oss/dynatrace-monitoring-as-code/releases

@UnseenWizzardI an unskilled  Unix  user doesn't know what to do with the packages you already prepared so just a few bullet points would be great!
rgds Steve

@dieselsteve I see, just wanted to be sure we'd add the right info to the right part of the documentation 👍


Linux build instructions in BUILD.md

Adds the instructions given in #501 to BUILD.md for building the launcher on Linux.
Closes #501

(Testing would just be following the instructions and making sure they work ig)


"Auto" setting for "slidesToShow"

Sometimes the number of slides to show can't be explicitly set - for example when showing a number of logos and you want the slide to fill up the width of the screen, whatever that might be.
I tried enabling variableWidth, but that too seems to depend on slidesToShow when infinite is enabled as sometimes there is a blank space before the next X number of slides are displayed. I also have autoplay enabled if that makes any difference.
Basically, if there was a setting auto for slidesToShow, then the slides should fill the width of the container and if infinite is enabled then they should repeat seamlessly.

Hey @pavsid  ... sorry but this makes no sense;
If you don't have enough slides to fill a carousel; then do your users a favour and don't load the carousel from the server.... waste of bandwidth and time... the point of a carousel is to display TOO many of something...
or you can and just duplicate your slides and piss people off even more?

@simeydotme, who said there wasn't enough slides to fill the carousel? Let's say I have a carousel of 20 logos. On a screen 1600px wide it looks fine if I set slidesToShow to 10, but on a screen 1200 px wide 10 is too many.
My point is that there should be a setting to best fit the slides in the carousel based on screen width, and not have to explicitly set the number of slides, or breakpoints all the time.

who decides what is "best fit" ?

@simeydotme A calculation for what?? The number of slides to show at a width of 1600, 1200, 1024, 768, 480px, etc?
I presume this "auto" setting would require that the slides have been set a width themselves so the logic knows how many can be shown in the current viewport.
I'm surprised this hasn't been asked before actually, and I thought that maybe there was already a way to do it.

Calculate how many slides you can show in the container based on the
container's width divided by the slide's width ....
I kind of see what you're getting at now... but its very easy for you to do
yourself before the carousel loads :) - you must consider that if
@ken_wheeler includes every possible functionality, even ones that you can
do yourself with ease, then your users will be downloading so much code
bloat. :)
Simon
On Wed, Feb 25, 2015 at 3:57 PM, pavsid<EMAIL_ADDRESS>wrote:

@simeydotme https://github.com/simeydotme A calculation for what?? The
number of slides to show at a width of 1600, 1200, 1024, 768, 480px, etc?
I presume this "auto" setting would require that the slides have been set
a width themselves so the logic knows how many can be shown in the current
viewport.
I'm surprised this hasn't been asked before actually, and I thought that
maybe there was already a way to do it.
—
Reply to this email directly or view it on GitHub
https://github.com/kenwheeler/slick/issues/1071#issuecomment-75919728.

@simeydotme Yeah I guess that's a solution, but it would have to recalculate again on window resize, which again is easy enough.
I just thought this might be a feature required by others too, or already possible.
Thanks for your help :-)

It's OK, sorry for the confusion!! :smile:
I agree it would be nice to calculate based on container, but depending on
CSS, and project settings it can be very troublesome to do it in a
universal way. I would suggest you don't look at the viewport width for
this ... just the carousel container :)
You can leave the issue open and the repo owner can consider the feature
still, I was just trying to help with a short-term solution.
Best, Simon
On Wed, Feb 25, 2015 at 4:28 PM, pavsid<EMAIL_ADDRESS>wrote:

@simeydotme https://github.com/simeydotme Yeah I guess that's a
solution, but it would have to recalculate again on window resize, which
again is easy enough.
I just thought this might be a feature required by others too, or already
possible.
Thanks for your help :-)
—
Reply to this email directly or view it on GitHub
https://github.com/kenwheeler/slick/issues/1071#issuecomment-75922855.

Was this closed because this feature request was implemented?  Otherwise it should be re-opened.
This would be a very useful feature.  Honestly, I couldn't care less how many slides appear at once.  I simply want the carousel to operate as a content "overflow."  It makes no sense to constantly watch for container size changes and recreating the carousel over and over again.  Also, what if the slides are variable-width?  It should just resize smoothly as the container size changes, and let the container be responsible for the responsive breakpoints.

I think this issue should be reopened. Instead of needing to definee the 'slidesToShow' per breakpoint it'd be great if this value would be calculated based on the width of the slides, wouldn't it?

I agree. I am looking for this feature.

well thats exactly what I need

has someone the lines that are needed to modify to make this work with variableWidth and not infinite?

Thanks @ramirezcgn saved me many hours having to figure this out, hopefully your code will be committed soon.

Can someone help me with where @ramirezcgn's code should go? I would love to have this feature but its a little over my js skill level. thanks

Hi @chancer4 you'd just add it to a new JS file. Then include it after slick.
eg

Then init slick, something like below.
var vaaTabs = (function () {

  var setActiveLink = function(element){
    var $nav = $('#deal-types ul');
    $nav.find('li').each(function(){
      $(this).children('a').removeClass('active');
    });
    $(element).addClass('active');
  }

  initSlick = function(){
    var $nav = $('#deal-types ul');
    $nav.slick({
      dots: false,
      infinite: false,
      speed: 300,
      prevArrow: false,
      nextArrow: false,
      autoSlidesToShow: true,
      variableWidth: true,
    });
  }

  return {
    initSlick: initSlick,
    setActiveLink: setActiveLink
  }
})();

@ramirezcgn
Thanks man. this is saved my day :)

@ramierzcgn
thx, for help, but can you help with integrate to ajax. After add this hack I have one slide to show (default slick parameter, I think). I have func to callback after successful ajax:
function InitSlick($Slick) { 	if(!$Slick.hasClass('slick-initialized')) { 		AutoSlick($);         // slider         $Slick.slick({ 			draggable: false, 			speed: 250, 			// slidesToShow: show_default, 			autoSlidesToShow: true, 			slidesToScroll: 1, 			infinite: false, 			prevArrow: "<button class='prev_btn'></button>", 			nextArrow: "<button class='next_btn'></button>"         });     } }
and have callback:
function getS(num, param){ 	if(num != ''){ 	$.ajax({ 	type: "POST", 	url: "pages.php", 	data: "numb=" + num, 	success: function(msg){		 		var Slider = $('#pages_preview'); 		$(Slider).slick('unslick'); /* ONLY remove the classes and handlers added on initialize */ 		$('.page').remove();		 	 		$('#pages_preview').html(msg);			 		HideDataPreloader('pages');	 		InitSlick($(Slider)); 	} 	}); 	} }

@ramirezcgn
thx, for help, but can you help with integrate to ajax. After add this hack I have one slide to show (default slick parameter, I think). I have func to callback after successful ajax:
function InitSlick($Slick) {
	if(!$Slick.hasClass('slick-initialized')) {
		AutoSlick($);
        // slider
        $Slick.slick({
			draggable: false,
			speed: 250,
			// slidesToShow: show_default,
			autoSlidesToShow: true,
			slidesToScroll: 1,
			infinite: false,
			prevArrow: "<button class='prev_btn'></button>",
			nextArrow: "<button class='next_btn'></button>"
        });
    }
}

and have callback:
function getS(num, param){
	if(num != ''){
	$.ajax({
	type: "POST",
	url: "pages.php",
	data: "numb=" + num,
	success: function(msg){
		var Slider = $('#pages_preview');
		$(Slider).slick('unslick'); /* ONLY remove the classes and handlers added on initialize */
		$('.page').remove();
		$('#pages_preview').html(msg);
		HideDataPreloader('pages');
		InitSlick($(Slider));
	}
	});
	}
}

will the fix work for vertical slide?

What I did to work around this one is a hidden input field with a value of the slider array count which then I pull the value from that field and set to the slidesToShow option.

High IQ here, thanks @tdrdimov !

Calculate how many slides you can show in the container based on the container's width divided by the slide's width ....
I kind of see what you're getting at now... but its very easy for you to do yourself before the carousel loads :) - you must consider that if @kenwheeler includes every possible functionality, even ones that you can do yourself with ease, then your users will be downloading so much code bloat. :)
Simon
On Wed, Feb 25, 2015 at 3:57 PM, pavsid<EMAIL_ADDRESS>wrote:

@simeydotme https://github.com/simeydotme A calculation for what?? The
number of slides to show at a width of 1600, 1200, 1024, 768, 480px, etc?
I presume this "auto" setting would require that the slides have been set
a width themselves so the logic knows how many can be shown in the current
viewport.
I'm surprised this hasn't been asked before actually, and I thought that
maybe there was already a way to do it.
—
Reply to this email directly or view it on GitHub
#1071 (comment).

my bad I didn't get on this issue before, I just created whole carousal from scratch to handle autoSlidesToShow 🥲.


198 add val data to training

I moved the old validation data into the training set and I moved the old "test" set into the validation set. ⚠  This PR will constitute the final results for the paper since we would no longer have a test set.
closes #198

closed this b/c I want merge with #204


Network request failed

Trying the remote heroku parse server on a vanilla install but I get "Network request failed" when trying to sign up for an account. anything I'm missing here?

I'm sorry - it appears that Heroku has an error starting the dyno.  Not sure why.

I had that same issue with the default heroku url include. You might want to make your own or build a local one no issues with those.

@bartonhammond You may want to check that the Heroku environment variable "verbose" is set to true so that you get the detailed server logs.  Also, I notice that the package.json start script hard-codes the environment variables via the setenv file.  I think you may want to drop this so that it is picking up Heroku's user-entered environment variable settings.

Yeah. I got a note from Heroku support about the env vars.
Thanks for looking at it.

This is fixed now, please verify.

It's still happening... I've ran a heroku instance at https://meetdine.herokuapp.com/parse. Server seems to be working fine. The IOS app itself throws a network request failed even if i used the same credentials that I've setup on heroku.

Have you tried debugging?  What did you see?  Are you using https as the
protocol?  Did you try both Anroid and iOS?  I know that iOS requires https.
On Nov 22, 2016 6:16 PM, "Efren Macasaet"<EMAIL_ADDRESS>wrote:

It's still happening... I've ran a heroku instance at
https://meetdine.herokuapp.com/parse. Server seems to be working fine.
The IOS app itself throws a network request failed even if i used the same
credentials that I've setup on heroku.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/bartonhammond/snowflake/issues/163#issuecomment-262404910,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABORPGAYDAJsJIUrwcokvtu6DP-tWVGlks5rA4XkgaJpZM4Kx5YZ
.


Get started on a book

TODO:

[ ] config (Cargo.toml)
[ ] config (CLI flags)
[ ] supported workflows

...maybe others...?

fixes #128


Bracket Colorize wrong in string

Colorize wrong in a javascript string

if(rslt != null)
    {
	   let data = rslt.substr(rslt.indexOf("base64,")+7);
	    jsonPacket += '"PlatePhoto" : "'+data+'"}';
     }

I have kind of same problem
if (this.query.whereAnd) {
      result.push(
        `(&${this.query.whereAnd
          .map((el) => `(${el.field as string}=${el.criteria})`)
          .join("")})`
      );
    }

Does this issue still occur? I can't seem to reproduce

It's fixed.

@CoenraadS
if (errorCodesInput == "Only Errors") {
       condition += `AND ( RecordStatus != '' OR  ) `;
}


[CFEP-22] Too Big To Be Compromised (TB2C)

This PR has the "too big to be compromised" proposal from our discussion.

xref https://github.com/conda-forge/cfep/issues/8 for prior discussions

Also see CFEP-08 for a prior proposal. This proposal is largely similar, but specifies voting rules, exempts upstream maintainers to help avoid maintenance issues, and doesn't specify how we declare the TB2C list except that we maintain it.

Do you have a shortlist of packages you are considering? Is "python" (which version) included in these? I would like to run through one to see what dependencies would be affected by one of your "too big to fail" packages.
I feel like many things are "optional" and we have included many "batteries" with our packages which may make this a difficult endeavor.

I do not yet have a list. I want to generate a similar list and see how many maintainers we have who do not satisfy the criterion in the CFEP. We may be in the position of codifying a policy that we de facto already have.

I'm closing this for now since I don't think i'll have time to put energy into it on second thought.

I'm closing this for now since I don't think i'll have time to put energy into it on second thought.

This is an effort that will take some dedication, coordination, and kind helpful comments from all of us. Also, maybe we should write a NF small grant, or some other sort of funding, to help whoever leads this.
Thanks @beckermr for starting it. Let's use this as a base for the next step b/c there are already many good ideas and points here.


Molecule runs lint only on some verifier code

Issue Type

Bug report

Molecule and Ansible details
$ ansible --version && molecule --version
ansible 2.9.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/tadej/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/tadej/tmp/mol/venv/lib64/python3.7/site-packages/ansible
  executable location = /home/tadej/tmp/mol/venv/bin/ansible
  python version = 3.7.5 (default, Oct 17 2019, 12:09:47) [GCC 9.2.1 20190827 (Red Hat 9.2.1-1)]
molecule, version 3.0a5.dev10+gec108275

Molecule installation method (one of):

source

Ansible installation method (one of):

pip

Replicating the issue:
$ molecule init role -r bla && cd bla
$ molecule init scenario -s second
$ echo "invalid-stuff" >> molecule/default/tests/test_default.py
$ echo "invalid-stuff" >> molecule/second/tests/test_default.py
$ molecule lint -s default; molecule lint -s second
--> Validating schema /home/tadej/tmp/mol/bla/molecule/default/molecule.yml.
Validation completed successfully.
--> Validating schema /home/tadej/tmp/mol/bla/molecule/second/molecule.yml.
Validation completed successfully.
--> Test matrix

└── default
    ├── dependency
    └── lint

--> Scenario: 'default'
--> Action: 'dependency'
Skipping, missing the requirements file.
--> Scenario: 'default'
--> Action: 'lint'
--> Executing Yamllint on files found in /home/tadej/tmp/mol/bla/...
Lint completed successfully.
--> Executing Flake8 on files found in /home/tadej/tmp/mol/bla/molecule/default/tests/...
    /home/tadej/tmp/mol/bla/molecule/default/tests/test_default.py:16:1: E305 expected 2 blank lines after class or function definition, found 0
    /home/tadej/tmp/mol/bla/molecule/default/tests/test_default.py:16:1: F821 undefined name 'invalid'
    /home/tadej/tmp/mol/bla/molecule/default/tests/test_default.py:16:9: F821 undefined name 'stuff'
--> Validating schema /home/tadej/tmp/mol/bla/molecule/default/molecule.yml.
Validation completed successfully.
--> Validating schema /home/tadej/tmp/mol/bla/molecule/second/molecule.yml.
Validation completed successfully.
--> Test matrix

└── second
    ├── dependency
    └── lint

--> Scenario: 'second'
--> Action: 'dependency'
Skipping, missing the requirements file.
--> Scenario: 'second'
--> Action: 'lint'
--> Executing Yamllint on files found in /home/tadej/tmp/mol/bla/...
Lint completed successfully.
--> Executing Flake8 on files found in /home/tadej/tmp/mol/bla/molecule/default/tests/...
    /home/tadej/tmp/mol/bla/molecule/default/tests/test_default.py:16:1: E305 expected 2 blank lines after class or function definition, found 0
    /home/tadej/tmp/mol/bla/molecule/default/tests/test_default.py:16:1: F821 undefined name 'invalid'
    /home/tadej/tmp/mol/bla/molecule/default/tests/test_default.py:16:9: F821 undefined name 'stuff'

Desired Behavior
molecule lint -s default should report errors in files under molecule/default/tests, and molecule lint -s second should report errors in files under molecule/second/tests.
Actual Behaviour
Linter always checks the same set of files (in the example above, always from the default scenario).

I tracked down the issue to the lint verifier method: https://github.com/ansible/molecule/blob/master/molecule/verifier/base.py#L117
We should not cache the result of this method across different scenarios because linter instances contain a scenario-specific content: list of files to check. To resolve the issue, we can either completely kill the caching or make it more granular (per verifier caching).
I can prepare a fix for this once we settle on how we want to fix this.

Nice work.
/cc @ssbarnea who was last working on the caching stuff

Please see https://github.com/ansible/molecule/issues/2293#issuecomment-554026415 and comment there.

#2513 is making this bug irrelevant.


Add ShowAuthInHeader to allow status page to hide the auth UI

Progress on https://github.com/NuGet/NuGetGallery/issues/4979.
I decided to not make this a configuration value since there is currently no customer need for it.

I would recommend ignoring whitespace in the diff:
https://github.com/NuGet/NuGetGallery/pull/4981/files?w=1

Merged to dev with https://github.com/NuGet/NuGetGallery/commit/d8bfb6e32f0b92dfec863aca0c2f3d5bb249d6c7.


DOC-9350 Docs for Log and Metric export to Azure Monitor supported for Dedicated Azure clusters

Fixes DOC-9350, DOC-9351
(1) In cockroachdb-dedicated-on-azure.md, removed Observability limitations.
(2) In export-logs.md, added filter section for Azure Monitor.
(3) In export-metrics.md, added filter section for Azure Monitor.
Rendered previews
Export Logs to Azure Monitor
Export Metrics to Azure Monitor

Hi
@arjunmahishi please review Export Logs to Azure Monitor
@aa-joshi please review Export Metrics to Azure Monitor
On both pages, in the Enable section there is just a message to contact their CRL account team. In a separate PR, I will document the Enable section once I get the loom videos from you both.
Thanks.

@mikeCRL and @kevin-v-ngo is this sufficient documentation for Azure Monitor for the 5/20 24.1 release. I will follow up with a separate PR for the Enable sections as soon as possible.

Mike and Kevin said that this pr was sufficient for the 5/20 v24.1 release in this slack thread


remove 'execute' file mode bits

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information

PR #6091 changed the file mode bits of extractor/dumpert.py from 644 to 755.
extractor/globalplayer.py from PR #6903 got added in mode 755.
This PR changes them (back) to the standard 644 used by all other files under yt_dlp/
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[x] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Copilot Summary

🤖 Generated by Copilot at 2e41301
Summary
📱🛠🌐

Add support for --write-link and --write-url options to write video or playlist URLs to a file. Refactor the code for writing metadata files to avoid duplication and improve readability.

is_valid checks
refactored for clarity
autumn leaves falling

Walkthrough

Add support for downloading videos from the website tubitv.com (tubitv.py, test_tubitv.py)

Not the first time this has happened. We probably need a CI step to enforce this since it's easily missed in review

oops, sorry
came from my default python script template fwiw


{KeyVault}Fix #17461 Add some examples for 'keyvault/_help.py'

Description

Resolve #17461
{KeyVault} Adds two examples for the az keyvault seret set command to prompt users how to use the command.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Please take a look at the linter error. You can run with azdev linter keyvault locally.


Promise.map - expecting an array or an iterable object but got object null

Using a promise like this;
return Promise.map(document.months, function(month, monthIndex) {

getting
5/12 12:16:54 [4344] - error: Possibly unhandled rejection at promise Promise {
  _bitField: 18087936,
  _fulfillmentHandler0:
     TypeError: expecting an array or an iterable object but got [object Null]

     - promise.js:10 apiRejection
       [hypetrain]/[bluebird]/js/release/promise.js:10:27

     - promise_array.js:62 MappingPromiseArray.init
       [hypetrain]/[bluebird]/js/release/promise_array.js:62:19

     - map.js:30 MappingPromiseArray._asyncInit
       [hypetrain]/[bluebird]/js/release/map.js:30:10

     - async.js:143 Async._drainQueue
       [hypetrain]/[bluebird]/js/release/async.js:143:12

     - async.js:148 Async._drainQueues
       [hypetrain]/[bluebird]/js/release/async.js:148:10

     - async.js:17 Immediate.Async.drainQueues
       [hypetrain]/[bluebird]/js/release/async.js:17:14

     - timers.js:649 runCallback
       timers.js:649:20

     - timers.js:622 tryOnImmediate
       timers.js:622:5

     - timers.js:594 processImmediate [as _immediateCallback]
       timers.js:594:5

This was working with 2.x series but bugging out with 3.x?

What's document.months?

I tried
		_.forEach(day.hours, function(hour, hourIndex) {
			return processHour(hour)
				.then(data => {
				})
		})

but know i don't know how to wait for all of those promises.

It's not iterable, you should use Promise.props instead of Promise.map to go through object keys. See Symbol.iterator for things that work with iterations.

Is there anyway i can convert it to iterable?

@boneskull well, ES2017 adds Object.entries but for your use case I recommend either converting it to an array first (arrays are iterable) or defining a Symbol.iterator:
document.months[Symbol.iterator] = Array.prototype[Symbol.iterator]

Can work


⚠ Processors has degraded performance

In eac62a6, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 51 ms

Resolved: Processors performance has improved in 793043d.


Saved pointers in a non-Actor class cannot be restored

I was implementing a checkpoint system where I store the last checkpoint encountered in my GameInstance:
UPROPERTY(SaveGame)
ACheckPoint* LastCheckPoint;

The first thing I noticed was that, when loading, LastCheckPoint was not getting restored. From this code, I see that as a non-AActor there won't be a valid level defined to find references:
https://github.com/sinbad/SPUD/blob/373585d2ceeea2e4e33262e079d8212c0ead1b0d/Source/SPUD/Private/SpudPropertyUtil.cpp#L855
As a quick test, I tried making the below change (I can see an edge case here for actors contained in streaming levels):
ULevel* Level = RootObject->GetWorld()->GetCurrentLevel();

Now  LastCheckPoint gets restored, but, is immediately GC'd. It's valid and legit in my GameInstance's SpudPostRestore, where I set a breakpoint when value changes and subsequently see TFastReferenceCollector doing its job and garbage collecting LastCheckPoint before the level finishes loading.
I thought that perhaps the order of restoration might matter, so tried shuffling level loading so it occurred before restoring data, however this did not help:
https://github.com/sinbad/SPUD/blob/db0ac4932ad0402d3445323898802d7c6ac184f8/Source/SPUD/Private/SpudSubsystem.cpp#L481
Any ideas why we might be losing a reference count when restoring data from a save? I do note that according to the log output, this class is taking the fast path.

On the losing reference count thing, I don't know - it can't be that SPUD holds the only reference, your level would do as well (and would be the ultimate owner), so maybe the level is unloading again or there's some other sequence going on.
On a more general note, I think it's a really bad idea to hold level actor references in global objects, since you can't guarantee that the level is loaded, and when it is, that reference will potentially be stopping the level actor unloading. It's for this reason that (hard) cross-references are only allowed between actors in the same level in UE (I've recently discovered that TSoftObjectPtr<> works well for references between streaming levels, but have not tried making any of these saved properties yet, I suspect it won't work (and all my sublevel cross-references are static).
Personally I'd store a checkpoint ID rather than a hard actor reference for this kind of thing. Either a GUID or a human readable manually assigned ID associated with your checkpoint actor would do it.

On a more general note, I think it's a really bad idea to hold level actor references in global objects

Gah, wow you are so right. I am using soft object pointers literally everywhere else to avoid reference creep and prevent destruction blocking, so the real mystery is why I threw away all common sense to try to force this solution. This is the textbook scenario where you want to avoid a hard reference and yet here I am, lost in the trees 🤣.
Thank you for this, I switched to a GUID system and it worked effortlessly.

I've recently discovered that TSoftObjectPtr<> works well for references between streaming levels, but have not tried making any of these saved properties yet, I suspect it won't work

It seems like this would work since you're already doing a 2-pass restore method. If everything retains the same name, it should all just line up.


New auto-completion mechanism for Text prompts

@alexwlchan I've arrived at a satisfiable solution for me, feel free to test it with the latest commit and if you do, let me know if it improved things for you!


Prop Type - Prop Validators Error

I use this module in order to create a multi selectable box which is populated by user's contacts. When contacts are selected, new chat group with the selected ones is created and so on.
However when I only just install the package following the steps in the
Official Page
and insert the component as following (same with the demo)
      <MultiSelect
        items={items}
        selectedItems={selectedItems}
        onChange={this.handleChange}
      />

I got the following error :
index.js:1452 Warning: Failed prop type: Calling PropTypes validators directly is not supported by the `prop-types` package. Use PropTypes.checkPropTypes() to call them. Read more at http://fb.me/use-check-prop-types
    in t (created by n)
    in n (at Contacts.jsx:103)
    in div (at Contacts.jsx:101)

After my research I learned that, it is caused because React and/or Redux version. Is there such a compatibility problem right now? If not how can I overcome the situation?

@engineer-only - which version of react do you use?


feat: add aws amplify hosting preset

🔗 Linked issue
Resolves #80
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Note: AWS Amplify support is still in progress with amplify team collaboration 🚀 (special thanks to @Narrator)
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation as needed.

can anyone enlight me where to put env. variables!?? It's a common question:
I have .env variables:
SUPABASE_URL=""
SUPABASE_KEY=""
STRIPE_SECRET_KEY=""
STRIPE_PUBLIC_KEY=""
ENDPOINT_SECRET=""
Now, how to add the variables???
 Nothing works.
:( I'm baffled. Any ideas?


Upgradinig to 1.7 causes the following error with SC 8.1

After upgrading to 1.7 from 1.2 I get the following error, have you seen this before?
System.TypeLoadException : Could not load type 'Sitecore.Reflection.INexusDataApiEx' from assembly 'Sitecore.Kernel, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.    at System.Reflection.RuntimeAssembly.GetType(RuntimeAssembly assembly, String name, Boolean throwOnError, Boolean ignoreCase, ObjectHandleOnStack type)    at System.Reflection.RuntimeAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)    at Sitecore.Reflection.ReflectionUtil.CreateObject(String assembly, String className, Object[] parameters)    at Sitecore.Reflection.ReflectionUtil.CreateObject(String typeName, Object[] parameters)    at Sitecore.Reflection.Nexus.GetApi[T](String typeName, T& api)    at Sitecore.Data.Engines.DataCommands.ResolvePathCommand.DoExecute()    at Sitecore.Data.Engines.EngineCommand2.Execute()
at Sitecore.Data.Engines.DataEngine.ResolvePath(String itemPath)
at Sitecore.Data.Managers.ItemProvider.ResolvePath(String itemPath, Database database)
at Sitecore.Data.Managers.ItemProvider.GetItem(String itemPath, Language language, Version version, Database database, SecurityCheck securityCheck)
at Sitecore.Data.Managers.ItemManager.GetItem(String itemPath, Language language, Version version, Database database)
at Sitecore.Data.Database.GetItem(String path)``

Further testing shows that this problem only occurs from v1.5, v1.4.1 is ok

It was a major internal change introduced in v1.5.0. Big chunck of FakeDb logic was moved from commands to providers which allowed to simplify it significantly. Since all the old functional tests were green, the version was considered as stable and released.
I've never meet this error before. Could you please share a failing test to reproduce the problem on FakeDb side? Thanks.

@sergeyshushlyapin sorry for the slow reply. All the tests in this class fail https://github.com/mikeedwards83/Glass.Mapper/blob/8f4506a14b7c1cd3f9179ed6459741c73fa7ea1a/Tests/Integration Tests/Sitecore/Glass.Mapper.Sc.Integration/DataMappers/SitecoreFieldStringMapperFixture.cs

Looks like this issue is not actual anymore. At least I managed to build Glass against Sitecore 8.1 (locally) and the mentioned tests passed. Closing.


Ionic 4 compatibility

Hi!
In ionic 4 have an issue what is based on this 2 file :
https://github.com/ionic-team/ionic-native/blob/master/src/%40ionic-native/plugins/three-dee-touch/index.ts#L168
https://github.com/ionic-team/ionic-native/blob/master/src/%40ionic-native/core/decorators/cordova-function-override.ts#L7
File 1. says, the method should exist to overwrite it.
File 2. implements file 1.
The solution is very easy and you have to modify only one file.
**www/ThreeDeeTouch.js **
You have to define the onHomeIconPressed function :
ThreeDeeTouch.prototype.onHomeIconPressed = function(){};
Then in the waitForIt function you have to modify the if :
if (window.ThreeDeeTouch && typeof window.ThreeDeeTouch.onHomeIconPressed !==ThreeDeeTouch.prototype.onHomeIconPressed)
In your case the function does not exist.
In my case the function exist but if the function was modified by a developer its trigger the deviceReady on native-site.

@EddyVerbruggen You can have a look here? Would be awesome to have a solution in master.
Thank you

OK, happy to merge and release this! Thx.


core-node-docs:write

Description

Related Issue(s)

Checklist

[ ] I have read the contribution guidelines
[ ] I have considered the performance impact of these changes
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

Why am I not able to find this in preview?
@Yndira-E How are we handling meta title and descriptions in this type of content? Should Sumit add the specific details similar to webpages or blogs?

@sumitshinde-84, @Hasmin-AC asked:

Why am I not able to find this in preview?

I can't find it either, I'm guessing the text in this PR should be added to this file?

If that's the case, it has to do with the name of your file, it should be file-use-case.md without the write

@sumitshinde-84, @Hasmin-AC asked:

Why am I not able to find this in preview?

I can't find it either, I'm guessing the text in this PR should be added to this file?
If that's the case, it has to do with the name of your file, it should be file-use-case.md without the write

Yes, I need to update the coreNodes.json file to include the documentation for the file-write and file-read and other nodes nodes.


Iron doesn't fulfill requests under performance testing

Hello
I'm running the "hello world" example from Iron under a virtual SSD single-core machine in the cloud, testing with wrk --latency -t2 -c100 -d60s on a different single-core virtual machine from the same data center.
I get approximately 10000 - 15000 requests/s
When I try to open the hello world page in my browser from my machine I only get a response from the server after 60 seconds, when the test is done.
Is there a way to fix it?
Iron version: 0.6.0
Code
Compiled in Release mode on the latest Manjaro
extern crate iron;
use iron::prelude::*;
use iron::status;

fn main() {
    Iron::new(|_: &mut Request| {
        Ok(Response::with((status::Ok, "Hello World!")))
    }).http("<IP_ADDRESS>:3000").unwrap();
}

Setup
My PC -> Rust backend in the cloud on SSD VPS (Ubuntu 17.10 amd64)
wrk --latency -t8 -c100 -d10s http://server:3000
Requests/sec:    146.30
Simultaneously from another VM as the client in the same data center.
VM (Ubuntu 17.10 amd64) -> Server Nginx -> backed on Rust (hello world)
wrk --latency -t2 -c100 -d10s http://server
Requests/sec:    255.88
Running wrk on my VM in the cloud alone
VM -> backend
wrk --latency -t2 -c100 -d10s http://server:3000
Requests/sec:  24816.01
Simultaneously running, again.
VM -> backend
wrk --latency -t2 -c100 -d10s http://server:3000
Requests/sec:  24816.01
PC -> nginx -> backend
wrk --latency -t8 -c100 -d10s http://server
Requests/sec:     49.91
*Upd
Simultaneously VM -> nginx and My PC > nginx
VM
Requests/sec: 20266.25
PC
Requests/sec: 1405.94

The performance depends on your network quality. Maybe the best way to fix it is to link your PC to datacenter via fiber directly.

Because iron based on hyper 0.10.x currently, which use sync IO.

This works perfectly on my machine. Maybe this was fixed by #523 ?


Gatling requests are failed and how the requests are generated when we record a flow

HI , I have recorded a login feature and executed it , After the execution i was going through the report and found that all the requests are failed . how are these requests generated and why they have failed .

First, this is a bug tracker: issues and feature requests only. For such questions, please use the community mailing list.
Then, there's no way to help you as you don't provide any details on your errors (check the errors block below this one). Please provide those informations when posting on the mailing list.


[Gluten-219] add ch ut job

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@liuneng1994 @zzcclp
There is a core dump after run pass all queries.
https://github.com/oap-project/gluten/runs/7188393461?check_suite_focus=true#step:11:664

@liuneng1994 @zzcclp There is a core dump after run pass all queries. https://github.com/oap-project/gluten/runs/7188393461?check_suite_focus=true#step:11:664

yeah, there is an known issue, we will fix this later, but it doesn't affect the UT .

Verified on Jenkins. LGTM.

@liuneng1994 @zzcclp Thanks for adding this check!


2.x Update deprecated Twig class

Ticket: #2327
Issue and Solution
After seeing #2327, I checked whether we forgot some other deprecated Twig classes, and found one instance, which I’m changing with this pull request.
Impact
None.
Usage Changes
None.
Considerations
None.
Testing
Should be covered by existing tests.

giddy up!


A Better Way for System Requirements

Some distributions may distribute older versions of specific packages for the sake of consistency but you might need that package's official LTS for your development workflow. I've come across a situation that Ubuntu 20.04 distributing Node 10 while Node's official LTS is 14. It caused VueJS to not compile since it requires at least 12.
That's why <SYSTEMNAME>.requirements.txt is not a good idea. Instead, we can provide a shell script, automagically installing the dependencies from dedicated sources.

See Node's distribution README and how to install it on Ubuntu 20.04 for a better understanding.


Use the scoped name for the VRF also while doing the l3out clone

will create a new pull request to address the review comments.


Remove duplicate info now added at  https://github.com/scientificcomp…

…uting/scientificcomputing.github.io/pull/19

Adds additional requirement on ipython version due to https://github.com/ipython/ipython/issues/13845


Rendering streamlines results in a crash after transition from 1.4 to 1.5

I am using a MegaMol rendering pipeline that commits streamlines geometry to OSPRay.
The ISPC device crashes reporting an internal embree error.
The error is: "RTC_INVALID_OPERATION: scene got not committed"
The Embree version is the same for 1.4 and 1.5.

Hi,
Could you retry this with the latest v1.6.0 release?

I can confirm that it works with v1.6.0.

Sorry, testing it in MegaMol requires to upgrade the geometries to the new requirements from Embree.
I had no time to do that in the last weeks.
But now that it is done, I can say that it works with MegaMol as well.


passwords.txt database password

Hi,
I am trying to setup the site on my GoDaddy web hosting account. ( csgoheist.com ) The package includes web hosting and MySQL databases. However I have followed your steps but am stuck on what to put for the database password. I have googles everywhere for how to find the database details on godaddy but they are all out dated. This is the page i see, next to the very badly drawn red star is the database i have setup, and uploaded the database .sql file you gave onto.
  I cannot work out how to find the database's password? Unless it is the password to the user account that has admin rights to the database? Can anyone help?
Thanks.

Is that your first page or why do you cant read the readme ?
All what you need is understand !!! Sorry but you have issues like a ninja

You mean where it says '{"default-password":"YOUR DATABASE PASSWORD","steamAPIKey":"YOUR STEAM API KEY"}'
I cant find out the the database password is.
I am asking if it is the password to the admin account of the database or if the actual database has a password.

that i mean with kind provider its not the best option to set up a gmabling page

What do you recommend then?

Do I just need to buy another sql server? Or do I need to buy another web hosting package again?


Testing data produced is wrong in some cases, fixed

Motivation

The testing data is not correct in some cases, like in updaters if you try adding PointWithTrace example as test, it will produce the wrong image to test. This is because skipping animations will skip intermediate values for updaters and you get wrong output. Same is the reason for cache to not work correctly with these examples. #983 testing issues gets fixed with this change
Overview / Explanation for Changes

Don't skip animations while producing testing data
Oneline Summary of Changes

- Fixed wrong testing output data produced in some cases (:pr:`997`)

Acknowledgements

[x] I have read the Contributing Guidelines

Reviewer Checklist

[ ] Newly added functions/classes are either private or have a docstring
[ ] Newly added functions/classes have tests added and (optional) examples in the docs
[ ] Newly added documentation builds, looks correctly formatted, and adds no additional build warnings
[ ] The oneline summary has been included in the wiki

uhh the new issue is that we also have to skip animations while testing, but that makes a lot of tests fail...


Stop using deprecated MockBuilder::setMethods in unit tests

MockBuilder::setMethods() is marked as deprecated since PHPUnit 8, but it's used in monolog tests.
In this pull request I've replaced these calls to onlyMethods() / addMethods().
Summary of changes:

the replace setMethods() -> onlyMethods() was enough in most cases
DynamoDbHandlerTest has a tricky case (Aws\DynamoDb\DynamoDbClient:: formatAttributes exists in aws/aws-sdk-php v2, but was removed in v3.0, but its call was tested based on the version)
AmqpHandlerTest requires the checking of \PhpAmqpLib\Channel\AMQPChannel::__destruct existence before the onlyMethods() usage (because __destruct was removed in php-amqplib/php-amqplib:2.5.0)
RedisHandlerTest requires the usage of addMethods() because Predis\Client uses magic method __call() for commands processing

Thanks. Looks all fine to me except for the 7.2/lowest CI build which uses aws-sdk 2.4.9 and outputs:
1) Monolog\Handler\DynamoDbHandlerTest::testHandle
Trying to configure method "formatAttributes" which cannot be configured because it does not exist, has not been specified, is final, or is static

Not sure why that is to be honest, as the code change you did looks good to me.

Thanks for noticing this.
This warning definitely should be fixed. I'll investigate this problem later.

Finally I've found out the reasons of this warning.
Aws\DynamoDb\DynamoDbClient from aws/aws-sdk-php 2.4.9 has method formatAttributes. So mock creation call looks like
        $this->client = $this->getMockBuilder('Aws\DynamoDb\DynamoDbClient')
            ->onlyMethods(['__call', 'formatAttributes'])
            ->addMethods([])
            ->disableOriginalConstructor()
            ->getMock();

addMethods with an empty array breaks the list of methods given by onlyMethods call.
So I have fixed it by calling addMethods for non-empty absent methods list only.
I've checked the outputs of all test runs and looks like this warning was fixed completely.

Great, thanks!


Reduce integration test time

Time to run all gt4py tests using tox is very large. There are tests which are clearly in the wrong spot, for example there are multiple tests in test_code_generation.py that actually validate run results, not just test generation. Those should to be in test_suites.py or moved elsewhere.
Much of this is from legacy backends, back when we did not have unit tests for each section. By looking at the corpus of integration tests, I bet we can reduce the CI time by at least a factor of 2.

Improving compile times as proposed in #995  may be part of a solution.


Reporter R02 Features

Planned for out to Beta, June 2024.R02 release in ArcGIS Online
Product name
Reporter
Priority 2 Features

[ ] Sign in capability - AGOL and Guest

[ ]  Allow for anonymous usage/comments - config option
[ ]  Support and disable likes/votes - config option
[ ] Commenting - config option

[ ]  Allow for anonymous usage/comments - config option (add warning when no features exist)
[ ]  Field picker option
[ ]  Add an option to support images in the comments
[ ]  Use the form in the related table (what if it's form, will it be a new screen?)

[ ]  Map only/list only designs - follow chart viewer pattern (add link to chart viewer)
[ ]  Sort capabilities (newest/oldest, highest voted)
[ ] Filter/Attribute filters
[ ]  Splash/Cover page with sign-in capability - indicator in app header that user is signed in or not
[ ] Language switcher

Mobile Design
https://www.figma.com/file/5LYgCbB11FUDS7rq7DkOvu/Crowdsource-Reporter-|-23.R3?type=design&node-id=238-138&mode=design
Desktop Design
https://www.figma.com/file/5LYgCbB11FUDS7rq7DkOvu/Crowdsource-Reporter-|-23.R3?type=design&node-id=676-590&mode=design&t=64K1tSCFuxGpeAec-0
App Planner - https://tasks.office.com/esriIS.onmicrosoft.com/en/Home/Planner/#/plantaskboard?groupId=bf4bf1e7-5061-4835-b42e-9702388b0d6c&planId=GHwbgM9q5UelCOTOx8PPpWQAD0KV
Release checklist:
Sample app (Home page)
thumbnail
test suite (TestRail)
Documentation
Item details
Onboarding
Intro blog
App example to Gallery (Nilakshi) or more for social media (marketing)
Holistic testing
Include in build/item copier
Update Matrix with new app/tools
Key Dates
String Freeze - Thursday, May 16, 2024
Release - Wednesday, June 12, 2024
QA tasks
Accessibility review
Automate core set of test cases

@sumitzarkar
Updated designs:
https://www.figma.com/file/5LYgCbB11FUDS7rq7DkOvu/Crowdsource-Reporter-|-23.R3?type=design&node-id=2123-559&mode=design
https://www.figma.com/file/5LYgCbB11FUDS7rq7DkOvu/Crowdsource-Reporter-|-23.R3?type=design&node-id=2125-18032&mode=design

We've added a progress bar ( mobile and desktop)

Coverpage Sign In ( Similar to splash screen page in 3.X version)

Sign in on the top right corner of the app

When users enable sign-in from app details, they'd have an option to sign in to the app and eventually sign out.

In the cover page, provide an option, when the cover page is enabled. (instant app team)

Toggle button: Enable sign-in on the cover page

In this case, the current configurable button 'Enter' could be configured as say: 'Guest', and another additional button would appear next to it with the text 'Sign In'.

If users click Enter, they enter as a guest

If users click Sign in, they'll see the oAuth sign-in dialog.

Comments header text will show the related table name instead of string 'Comments. '

Configuration changes in the Reporter tab ( Designs are not updated yet)

Users would see a list of layers, and for those layers that are checked, they'd see options: Like, Dislike, Show Reporting Layers. For each of the enabled options, the user will configure the appropriate field. The UI would look similar to the CountDown Instant app. https://localgovdev.mapsdevext.arcgis.com/home/item.html?id=0125d213b027409b8d549e0295832e71

In mobile figma designs - we've added a feature template screen before adding a point.

Let me know if you've any questions.

@sumitzarkar  here are the designs for the config panel (reporter tab). It has a sticker 'almost done'
https://www.figma.com/file/5LYgCbB11FUDS7rq7DkOvu/Crowdsource-Reporter-|-23.R3?type=design&node-id=837-1367&mode=design

@skrishn
As discussed on the call, we can show the menu for the sort options.
Below is the updated UI for the sort

Desktop Mode
Mobile mode

Please let us know if any changes are required

@skrishn
Here is our understanding about all the features we will be covering in this release

Sign in capability - AGOL and Guest - This will handled by the instant app team and we don't need any changes from our side

Filtering - Will be covered in #593

Sorting - Will be covered in #606

Progress bar in creation workflow

Like dislike count - Will be covered in #591

comments  - Will be covered in #592

count
list
comments details
New comments

Search Widget #546

Show features list when only one layer - #520

Show popup for non-editable layers - #525

remove next cancel - #551

Highlight on hover - #583

zoom scale - #360

#598

#599

Please let us know if we are missing anything

@sumitzarkar this list looks correct for R02

@skrishn

Progress bar in creation workflow

Dev Checklist

Items
Is required
Status
Comments

Required NLS changes?
No

Required Backward compatibility
No

Required 508
No

Need Sanitize?
No

Impact Analysis Report

Impacted Areas
Comments

Have Configuration changes?
No

Have Runtime changes?
Yes

Impact on RTL
No

Impact at runtime
The Progress bar should be shown as per mockups in the following panels with the respective progress:

On the Create a Report button click, the layer list should be displayed with the 25% progress barOn click of layer  If the layer contains the template then the template panel should be displayed with the 50% progress barIf the layer does not contain the template then the add location panel should be displayed with 75% progressAfter adding location, the editor should be displayed with the 100% progress bar

On the back click of any panel should maintain the progress of the progress bar


Some problem about camera coordinates 3D box IoU compute

Hi, recently i use "d3_box_overlap" in eval.py, to compute the same two 3D boxes 3D IoU. The IoU should be 1.0, but i get 8.3721865e-09. Some thing must be wrong，but i don`t know why.

There is a small bug about computing the 3D IoU of two exactly same boxes. I didn't fix it since this code is borrowed from traveller59/kitti-object-eval-python and this bug is seldom triggered.
You could try to modify here to fix it: https://github.com/sshaoshuai/PCDet/blob/master/pcdet/datasets/kitti/kitti_object_eval_python/eval.py#L131

Thank you very much!

hello, do you konw how to modify?

There is a small bug about computing the 3D IoU of two exactly same boxes. I didn't fix it since this code is borrowed from traveller59/kitti-object-eval-python and this bug is seldom triggered. You could try to modify here to fix it: https://github.com/sshaoshuai/PCDet/blob/master/pcdet/datasets/kitti/kitti_object_eval_python/eval.py#L131


Add missing feature switch

@zhenlan thoughts on changing the default behavior to throw on a missing feature? I would prefer that we do it that way. It is a breaking behavioral change, but not a breaking API change. Therefore it wouldn't require a major version bump.

Discussed with @zhenlan, let's go ahead and make the default behavior to not throw for a missing feature. There is a scenario for this where a developer codes ahead of someone who is setting up configuration.

@jimmyca15 Thanks for the clarification, I'll update the PR.

@jimmyca15 Updated following your comments and now ready for review.

This PR has not had any recent activity. In an effort to address #68, a new PR, #78, has been created. Any future discussion can be moved there.


ERR: Better error message describe with non-numeric data

Closes #2326
The other option is to return an empty dataframe. I think most users would prefer an exception though.

Looks good to me. Thanks @TomAugspurger!


modifiedWriteValues ignored in patches

#106  added support for modifiedWriteValues but this ignored in patches
  SCR:
    _modify:
      IOSB0:
        access: write-only
        modifiedWriteValues: oneToClear

            <field>
              <name>IOSB0</name>
              <description>Set bit 0</description>
              <bitOffset>0</bitOffset>
              <bitWidth>1</bitWidth>
              <access>write-only</access> << it works
            </field>

https://github.com/stm32-rs/stm32-rs/blob/da9085da570e8934b205115f128500c27ca721fb/peripherals/flash/flash_v1.yaml#L8-L10

Yes, I do it like in this example. Why doesn't this patch work? Doesn't this provide an advantage when used with svd2rust?

How looks your patch? Have you added _W1C?

Oh. Thank you. This is not at all the behavior I expected.
    RLDF:
      _read:
        NotReached: [0, "Downcounter doesn't reached 0x40"]
        Reached: [1, "Downcounter reached 0x40"]
      _W1C:
        Clear: [1, "Clear flag"]

<modifiedWriteValues>zeroToClear</modifiedWriteValues>
              <enumeratedValues>
                <name>RLDFR</name>
                <usage>read</usage>
                <enumeratedValue>
                  <name>NotReached</name>
                  <description>Downcounter doesn't reached 0x40</description>
                  <value>0</value>
                </enumeratedValue>
                <enumeratedValue>
                  <name>Reached</name>
                  <description>Downcounter reached 0x40</description>
                  <value>1</value>
                </enumeratedValue>
              </enumeratedValues>
              <enumeratedValues>
                <name>RLDFW</name>
                <usage>write</usage>
                <enumeratedValue>
                  <name>Clear</name>
                  <description>Clear flag</description>
                  <value>0</value>
                </enumeratedValue>
              </enumeratedValues>

oneToClear is _W1C. Not _W0C

I get it. In this case, I need W0C.

Can we close this, or there still an issue?

I'm not sure. On the one hand, there is a functionality implements this. By the way, it's undocumented #5 . On the other hand, this behavior seems unintuitive.
I would like to add the possibility of such a patch as in my original example.

I would like to add the possibility of such a patch as in my original example.

Reasonable. Could you make PR?


report invalid coder IDs, rather than raising error

Instead of
Traceback (most recent call last):
  File "/home/forkel/venvs/grambank/bin/grambank", line 11, in <module>
    load_entry_point('pygrambank', 'console_scripts', 'grambank')()
  File "/home/forkel/venvs/grambank/pygrambank/src/pygrambank/__main__.py", line 36, in main
    return args.main(args) or 0
  File "/home/forkel/venvs/grambank/pygrambank/src/pygrambank/commands/describe.py", line 39, in run
    describe(args, sheet)
  File "/home/forkel/venvs/grambank/pygrambank/src/pygrambank/commands/describe.py", line 87, in describe
    print('{}\t{}:\t{}'.format(k, coders_by_id[k], str(v).rjust(3)))
KeyError: 'A'

the problem should be reported in a readable way.

That would be nice, thanks for being thoughtful. For now my notes say "Make noise if there's something in traceback" and that should catch things hopefully in the meantime :)

To clarify, the reason I was asking https://github.com/glottobank/Grambank/pull/1181 how to interpret that particular traceback message it was because I hoped that if I know how to read traceback, you don't have to do more work to make the traceback feedback readable.

@xrotwang wrote
Ah, ok. You posted the symptoms of a problem, and I posted a commented solution. So whenever you encounter the symptoms again, consider trying the solution from here.

Yes, I fully understood that. I was asking for help to interpret the message that traceback produced, so that in future I may be able to read it myself more easily.

The aim was to make your life easier by understanding the output of pygrambank commands myself. That way, issues like this one #35 don't need to be filed because I'd already be competent enough to read the output. Unless you are imagining other users besides me, Christoph and Simon.


p11-kit fails to build locally on non-NixOS systems (single-user install) due to failing tests on master

Describe the bug
p11-kit builds on nixos/hydra, but fails on non-nixos systems in single-user installs (not multi-user) due to failing test.
Similar issue: https://github.com/NixOS/nixpkgs/issues/72838
test-conf: common/test.c:612: p11_test_copy_setgid: Assertion `false && "this code should not be reached"' failed.
./build/litter/tap-driver.sh: line 639: 56517 Aborted                 (core dumped) "$@"
ERROR: test-conf - missing test plan

============================================================================
Testsuite summary for p11-kit 0.23.21
============================================================================
# TOTAL: 743
# PASS:  741
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 2
============================================================================
See ./test-suite.log
Please report to https://github.com/p11-glue/p11-kit/issues
============================================================================
make[4]: *** [Makefile:4928: test-suite.log] Error 1
make[4]: Leaving directory '/build/source'
make[3]: *** [Makefile:5036: check-TESTS] Error 2
make[3]: Leaving directory '/build/source'
make[2]: *** [Makefile:5640: check-am] Error 2
make[2]: Leaving directory '/build/source'
make[1]: *** [Makefile:4813: check-recursive] Error 1
make[1]: Leaving directory '/build/source'
make: *** [Makefile:5643: check] Error 2
builder for '/nix/store/r6mh4dp2vqlhfr5j7x6wpdy9snp6bl08-p11-kit-0.23.21.drv' failed with exit code 2
error: build of '/nix/store/r6mh4dp2vqlhfr5j7x6wpdy9snp6bl08-p11-kit-0.23.21.drv' failed

To Reproduce
Steps to reproduce the behavior:

nix-shell -I nixpkgs=https://github.com/nixos/nixpkgs/archive/master.tar.gz -p p11-kit --check

Expected behavior
p11-kit succeeded on hydra, so I assumed it would succeed locally
Additional context
I ran into this issue trying to review https://github.com/NixOS/nixpkgs/pull/94637
Notify maintainers
None, recent/involved: @worldofpeace @FRidh
Metadata
❯ nix-shell -p nix-info --run "nix-info -m"
these paths will be fetched (0.00 MiB download, 0.00 MiB unpacked):
  /nix/store/iinpypz3m7d68kqcb043qi9iiwvsm6pm-nix-info
copying path '/nix/store/iinpypz3m7d68kqcb043qi9iiwvsm6pm-nix-info' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 5.7.16-200.fc32.x86_64, Fedora, 32 (Workstation Edition)`
 - multi-user?: `no`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.7`
 - channels(michael): `"nixos-unstable-20.09pre239318.c59ea8b8a0e, nixpkgs-20.09pre240426.f9567594d5a"`
 - nixpkgs: `/home/michael/.nix-defexpr/channels/nixpkgs`

This is labeled as a channel blocker because p11-kit is in the gnome3 closure.
cc @nixos/gnome

I couldn't reproduce this @mjlbach

@worldofpeace Thanks for checking, I'm not sure what it could be about my local system then. I can try to debug/test on a couple vms.

@mjlbach Yeah, from looking at https://hydra.nixos.org/job/nixpkgs/trunk/p11-kit.x86_64-linux it seems on nixos linux the build is successful. We actually happen to have the tests on darwin disabled (perhaps for a similar reason). I'm not sure there's a way to detect in stdenv non-nixos linux.

Updated the issue title and description to make it more clear this does not affect NixOS, but rather linux systems using nix.

One option would be to have an "allowlist" for tests. Something like
doCheck = hostPlatform.system == "x86_64-nixos"

My hostPlatform.system on NixOS is
$ nix eval -f '<nixpkgs>' hostPlatform.system
"x86_64-linux"

which I assume is the same as non-NixOS.

My hostPlatform.system on NixOS is
$ nix eval -f '<nixpkgs>' hostPlatform.system
"x86_64-linux"

which I assume is the same as non-NixOS.

Yes, that's what I was hoping was not the case. Maybe there should be a stdenv.isNixOS... Not sure how widespread these sorts of failures are.

Based on looking at the p11_test_copy_setgid code, perhaps this happens when you have /tmp on a filesystem mounted nosuid?

Yes, that seems to be the case:
$ mount
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,seclabel)

Although this seems to be standard for systemd managed systems? (ubuntu, fedora, etc.?)

Actually, the callers of p11_test_copy_setgid pass in BUILDDIR rather than /tmp, so it might be some other filesystem that matters.

/run maybe? See #2957.

I'm not sure how to verify that, but based on the issue description I tried
 TMPDIR=/tmp nix-shell -I nixpkgs=https://github.com/nixos/nixpkgs/archive/master.tar.gz -p p11-kit --check

And still reproduced my issue

This doesn't block a channel, right?

BTW, I don't reproduce the issue on my sandboxed non-NixOS builder.
Current master, result /nix/store/j9199a0p4847pc1f1czjfrkw7nf6f0rn-p11-kit-0.23.21.

This doesn't block a channel, right?

Yep, I forgot to unlabel it.

@vcunat Thanks for the info. Are you using a single or multi-user install? I have sandboxing enabled on both the ubuntu and fedora vms, but it's installed via single-user (not sure if this matters, but I have no idea what other substantive difference there could be).

Yes, multi-user.

I've confirmed this issue only affects systems in single-user install.

One issue is that in order to use single-user installs on redhat based linux distributions, it seems you have to disable SELinux

I think I might be running into this issue too (single-user install, Ubuntu).
From bisecting, it seems to be a regression since building with meson https://github.com/NixOS/nixpkgs/commit/3ca33e5ef4f8c3e24013905cf741330c9ace3a6c.
nix build --rebuild github:NixOS/nixpkgs/nixos-23.05#p11-kit works, but nix build --rebuild github:NixOS/nixpkgs/nixos-23.11#p11-kit doesn't.

I think I might be running into this issue too (single-user install, Ubuntu).
From bisecting, it seems to be a regression since building with meson https://github.com/NixOS/nixpkgs/commit/3ca33e5ef4f8c3e24013905cf741330c9ace3a6c.
nix build --rebuild github:NixOS/nixpkgs/nixos-23.05#p11-kit works, but nix build --rebuild github:NixOS/nixpkgs/nixos-23.11#p11-kit doesn't.

It sounds OK to me to just disable this problematic tests (in nixpkgs), if it helps some users.  Feel free to try that out and send a PR.

The two problematic tests are test-rpc and test-conf.
I looked to see if there was a way to configure this through meson, and therefore the nix mesonCheckFlags, but there doesn't appear to be one yet (see https://github.com/mesonbuild/meson/issues/6999 and https://github.com/mesonbuild/meson/pull/11502).
I think the next option is to patch the meson.build file to remove the test.
@vcunat does that sound reasonable? (If so, I'll try that out and open a PR 🙂)

Yes, that does sound OK to me.

Actually, the callers of p11_test_copy_setgid pass in BUILDDIR rather than /tmp, so it might be some other filesystem that matters.

Looks like this was actually done in https://github.com/p11-glue/p11-kit/pull/17 precisely to work around this problem.
And apparently, you also made a PR to skip the tests that need suid on nosuid file systems: https://github.com/p11-glue/p11-kit/pull/319
So I would expect this to be resolved.
Maybe @jonathanlking is experiencing a different issue?

From bisecting, it seems to be a regression since building with meson 3ca33e5.

Looking at the diff, maybe we need to bring back the FAKED_MODE environment variable?

@jtojnar good spot, thanks!
Yes, adding back the preCheck step that sets FAKED_MODE makes things build again 🎉
I intend to open a PR with that change now.


bug: docslt error not caught by ci

Describe the bug
https://buildkite.com/risingwavelabs/pull-request/builds/26773#01892212-5807-4b26-91e3-948930a2f26a
...
INFO found 1 blocks at src/expr/src/vector_op/position.rs
ERROR expect /// or //! at src/expr/src/vector_op/string.rs:409
ERROR expect /// or //! at src/expr/src/vector_op/string.rs:446
INFO found 11 blocks at src/expr/src/vector_op/string.rs
...

The new docslt added in #10729 was mis-formatted. The relevant parts were skipped. It gave a false confidence that they are covered and passed the tests.
Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response

@stdrc Do you think we can make the wrong-format error a fatal one rather than skipped? Are there better alternatives?

I think it'll be better to fail on wrong format. Let me check this later.


FIR designer refactor loops

squash out the external designer library
make it easier to add more options

Progress branch: https://github.com/pothosware/pothos/tree/fir_designer

https://github.com/pothosware/pothos/commit/a1d25ace48f03e268aa35553586972f9fa68a1e3


serializer and adapter for ember-orbit

Orbit source is the equivalent of an adapter. Orbit serializer is a thing. Do you mean you wish it would be easier to plug a custom serializer through injection system?

No, it is not necessary i wasnt digging to the source code. When i tried to
understand the source then i found that extending the jsoapi source classes
will do the serializer and adapter. But for beginners, it will be
difficult, but it is simple if we understand the concept. You can provide
some docs about extending the classes like "urlbuilder class" etc.
On Sat 21 Dec, 2019, 6:04 PM Paul Chavard<EMAIL_ADDRESS>wrote:

Orbit source is the equivalent of an adapter. Orbit serializer is a thing.
Do you mean you wish it would be easier to plug a custom serializer through
injection system?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/orbitjs/ember-orbit/issues/233?email_source=notifications&email_token=ALUGHGZQ4334FYQR2ORXCC3QZYEODA5CNFSM4JM7G362YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHO3KOA#issuecomment-568177976,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALUGHG2J3VJNUKJ3KYP2CV3QZYEODANCNFSM4JM7G36Q
.

I agree we need to improve the docs especially for @orbit/jsonapi. These are coming with v0.17.


Windows OS - Horizontal scroll using trackpad

In Windows settings, trackpad scroll is set to "Natural Scrolling".
In VScode, only vertical scroll works as per this setting, whereas, the horizontal scroll works in opposite direction.
This is not consistent. It should work in any one particular way. Either both vertical and horizontal do a natural scroll or a regular scroll.
This is only with "Two finger" trackpad scroll. VSCode version: 1.42.1

@ckr1989 VS Code is built with Electron, which is built with Chromium. Can you please try to scroll with Chrome? Does that respect the OS settings?

I checked in chrome browser. Same problem exists in chrome. So, does it mean it's an issue in chromium?

Yes, you can report against Chromium at https://bugs.chromium.org/p/chromium/issues/list


Error while setting Custom Dimension

Hi,
Based on the documentation here[https://developer.matomo.org/api-reference/PHP-Matomo-Tracker], it says that setCustomDimension function is available to set values of custom dimensions using the PHP tracker code.
However, when I put this in my PHP script like below:
`<?php
require_once "assets/custom/php/matomo_tracker.php";
MatomoTracker::$URL = '/matomo';
$matomoTracker = new MatomoTracker( $idSite = 1 );
$matomoTracker->setTokenAuth('<auth_token>');
$matomoTracker->doTrackPageView('Home');
$matomoTracker->setCustomVariable(1,$user_details['firstName'][0] . " " . $user_details['lastName'][0]);
?>`
It throws an error in my log files: PHP Fatal error:  Uncaught Error: Call to undefined method MatomoTracker::setCustomDimension() in /var/www/html/index-analytics-php.php:19
Is the document mentioned earlier referring to some other PHP library?
Thanks,
Any help is appreciated,
Krishna Vasudevan

This is the repository for the Android SDK.


[emmet] Inconsistency on cursor placement when applying emmet proposals

VSCode Version: 1.47.3
OS Version: Windows x64 10.0.18363

vscode.zip

Steps to Reproduce:

In attached html file, put cursor inside body {} style rule, and type: dis, and then intellisense will show  display: none as the first choice (Emmet abbreviation). Press tab key, and cursor will be after the semi-colon.
Press enter key to go to next line. Type ov or over, and intellisense will show overflow: hidden; as the first choice (Emmet abbreviation). Press tab key, and hidden will be hilighted/selected, rather than cursor being after the semi-colon.

I can see the advantages of both cursor placements, but why the inconsistency?

Does this issue occur when all extensions are disabled?: Yes

I believe this is by design.
In the cheat sheet https://docs.emmet.io/cheat-sheet/, di (or d:i) and ov have different expansion patterns. The green highlight around hidden refers to the fact that that selection will be focused after the expansion.

@rzhao271 As I understand it, the green hilight simply tells what the default property value is if you don't give any starting characters. For example, display will have the value 'block', and overflow will have 'hidden'.
But that doesn't explain why when pressing the tab key, overflow incorrectly puts the cursor before the semicolon, whereas  display correctly puts the cursor after the semicolon.
Please re-open this.

Will reopen, but I noticed this inconsistency between di and ov is also in Sublime Text and the Emmet website itself here.
Something else to note is that db expands to display: block;|, whereas just d expands to display: block|;. My guess is that if you already gave Emmet the suggested value, it'll put the cursor after the semicolon, but if you didn't, it'll put it before the semicolon, giving you a chance to change the value. In your demo, you typed dis, which the VS Code Emmet interpreted as di, which expanded to display: inline;|.
@sergeche can you confirm this is intended behaviour?

@rzhao271 Thanks for re-opening and investigating. I believe most people expect the cursor to end up after the semicolon, because in our minds, this is "Microsoft-style intellisense/auto-complete". I do know that for me, when pressing tab and sometimes the cursor is placed oddly like this, it disrupts the typing flow, because I now can't press enter, but have to either press end then enter, or down-arrow.

Closing this again. Considering that this is how Emmet works on other editors too, I'm not sure it's worth changing this behaviour just for VS Code.
Also, as I mentioned earlier, depending on the abbreviation, Emmet will suggest a value to fill in and then the cursor will end up after the semicolon. Type oh or ovh instead of ov for overflow hidden, for example.


Intallation in Ubuntu 16.04

I have tried to install peatio at my system as written step here https://github.com/peatio/peatio/blob/master/doc/setup-local-ubuntu.md
But
rbenv install 2.1.2
now working due to end  of life this version
so I had to use this version rbenv install 2.4.2
other things fine but below command not working
bundle exec rake db:setup
Please anyone help me.

rbenv install 2.1.1
rbenv global 2.1.1
gem install bundler
bundle install
bundle exec rake db:setup

Now getting bellow error when run install 2.1.1
Installing ruby-2.1.1...
WARNING: ruby-2.1.1 is past its end of life and is now unsupported.
It no longer receives bug fixes or critical security updates.
BUILD FAILED (Ubuntu 16.04 using ruby-build 20170914-2-ge40cd1f)
Inspect or clean up the working tree at /tmp/ruby-build.20171004145600.304
Results logged to /tmp/ruby-build.20171004145600.304.log
Last 10 log lines:
make[2]: Leaving directory '/tmp/ruby-build.20171004145600.304/ruby-2.1.1/ext/nkf'
compiling callback-6.c
compiling callback-7.c
compiling callback-8.c
installing default callback libraries
linking shared-object dl/callback.so
make[2]: Leaving directory '/tmp/ruby-build.20171004145600.304/ruby-2.1.1/ext/dl/callback'
make[1]: Leaving directory '/tmp/ruby-build.20171004145600.304/ruby-2.1.1'
uncommon.mk:180: recipe for target 'build-ext' failed
make: *** [build-ext] Error 2

Because of the version of MySQL in Ubuntu 16.04 is higher than Ubuntu 14.04 (5.7 vs 5.5) so when you run
bundle exec rake db:setup
=> error.
You need to modify the DB migrate scripts before run it.
https://github.com/peatio/peatio/tree/master/db/migrate

thats tough

you can just switch back to an older mysql one moment
sudo add-apt-repository 'deb http://archive.ubuntu.com/ubuntu trusty universe'
sudo apt-get update
sudo apt-get install -y mysql-server-5.6 redis-server libmysqlclient-dev
sudo /etc/init.d/mysql stop
sudo /etc/init.d/mysql start

if you have modified code supporting latest mysql please share...

sandeep-enuke  this looks like an error because of the stuff you did in the past you should start with a fresh install you can contact me here https://gitter.im/peatio/peatio if you need more help

I have ubuntu 16.4 I had the same error in my project
my solution is to install ruby, rbenv, bundler finally delete and create Gemfile file:
first step: install ruby
update system
sudo apt-get update
sudo apt-get upgrade

rbenv
sudo apt-get install git-core curl zlib1g-dev build-essential \
                         libssl-dev libreadline-dev libyaml-dev libsqlite3-dev sqlite3 \
                         libxml2-dev libxslt1-dev libcurl4-openssl-dev \
                         python-software-properties libffi-dev

    git clone git://github.com/sstephenson/rbenv.git .rbenv
    echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc
    echo 'eval "$(rbenv init -)"' >> ~/.bashrc
    exec $SHELL

ruby-build
git clone git://github.com/sstephenson/ruby-build.git ~/.rbenv/plugins/ruby-build
echo 'export PATH="$HOME/.rbenv/plugins/ruby-build/bin:$PATH"' >> ~/.bashrc
exec $SHELL

Install Ruby through rbenv:
rbenv install 2.2.1
rbenv global 2.2.1

Install bundler
echo "gem: --no-ri --no-rdoc" > ~/.gemrc
gem install bundler
rbenv rehash

second step: delete and create the Gemfile file
Search for the Gemfile file in the project, it must be at the root of the project. for more information about Gemfile http://bundler.io/
cd peatio

with the command ls we can see all the files and folders of the project
ls

delete Gemfile file
rm Gemfile

create Gemfile
bundle init

now we can install bundle
bundle install


Domain-specific package contribution reviews

All along, we planned to have domain-specific package reviews at https://github.com/r-multiverse/contributions: spatial, Bayesian, databases, etc. I have a proposal for how that could work:

Each new moderator adds labels with their fields of expertise: https://github.com/r-multiverse/contributions/labels. We might want to consider a "domain" prefix for namespacing purposes (e.g. "domain: spatial").
Package maintainers can add e.g. Config/R-multiverse/domain/spatial to the DESCRIPTION file.
For a pull request at https://github.com/r-multiverse/contributions/pulls, the bot automatically reads the DESCRIPTION and assigns the appropriate label.
When selecting packages to review, the moderator filters pull requests based on their own labels.

https://github.com/ropensci/rcrossref/blob/bf3fcfe0d7deede6c93847081f84e8ab45ba079e/DESCRIPTION#L49

Thanks for pointing out this syntax is possible: Config/R-multiverse/domain: spatial, web

I think most package authors would probably be wary of adding things to DESCRIPTION.
Isn't a simpler answer just to have these labels available for the user to add when making their PR, or subsequently when it gets flagged for manual review? We could include instructions in the bot message.

I think a lot of package authors would probably be wary of adding things to DESCRIPTION.

Why? (genuine question)
I regularly send this link to package authors: https://r-pkgs.org/description.html#sec-description-custom-fields
And I suppose this might help too: https://github.com/search?q=Config+user%3Acran+path%3A**%2FDESCRIPTION&type=code&ref=advsearch
We could even provide a simple {desc} wrapper to help with it.
The idea of having the field was also to serve as verification (since you need write access to the package to have those fields, but not to put them in the PR).

Bioconductor has something similar via the BiocViews and it is hard to use that field as a user even if the ontology is limited/controlled: Some maintainers do not explore the options, it is hard to say if they explicitly do cover a certain tag or they don't because they use a parent label but not the child label, as maintainers update and add or remove functionality of their packages often this tags are not updated ...
Of course if via a bot there is more change tracking on packages that would lead to adding or removing tags this could be more useful, but that is not easy to automate.
If it where something like Config/R-multiverse: yes that would be easier to add, it only needs to do that once and it serves as write verification.

Just catching up on this thread.

Isn't a simpler answer just to have these labels available for the user to add when making their PR,

Most users won't have high enough privileges in the repo. I think they need "Triage" at least.

or subsequently when it gets flagged for manual review? We could include instructions in the bot message.

Maybe I missed something in your comment, but for this to work, the users need to be able to choose the labels somehow. Otherwise, moderators would have to comb through packages outside their expertise in order to assign those labels in the first place. My proposal is to have the labels show up automatically, and then the moderators can just hone in on just the sub-communities the agreed to review.

Bioconductor has something similar via the BiocViews and it is hard to use that field as a user even if the ontology is limited/controlled: Some maintainers do not explore the options,

I agree with @maelle that we could make this process simple with the right documentation in r-multiverse.org.

it is hard to say if they explicitly do cover a certain tag or they don't because they use a parent label but not the child label

I don't think we need a nesting structure for labels.

as maintainers update and add or remove functionality of their packages often this tags are not updated ...
Of course if via a bot there is more change tracking on packages that would lead to adding or removing tags this could be more useful, but that is not easy to automate.

It would be nice if Config/R-multiverse/domain were kept up to date, but it really only needs to be accurate at the time a package is manually reviewed at https://github.com/r-multiverse/contributions. The underlying goal is to decrease the workload of moderators. Instead of being responsible for all the packages, we want moderators to just focus on ones relevant to their expertise (whether it's spatial, Bayesian, time series forecasting, Rust infrastructure, etc.). When a moderator has a free moment to review some packages, they should be able to just go into https://github.com/r-multiverse/contributions/pulls and filter on the labels they want to review.

But also I think authors will already be thinking something along the lines of should I bother with R-Multiverse, and if we say you have to modify your package to submit to it, that creates another psychological hurdle.

Labels would be completely optional. They would just help get a faster manual review if one is needed. I don't think we should require them.

If it where something like Config/R-multiverse: yes that would be easier to add, it only needs to do that once and it serves as write verification.

Verification is important when the package URL username is different from the username who created the pull request at https://github.com/r-multiverse/contributors/pulls. It helps us confirm that the author of the package actually wants it in R-multiverse. @jeroen mentioned that an R-multiverse URL in the DESCRIPTION would also serve this purpose.

Just catching up on this thread.

Isn't a simpler answer just to have these labels available for the user to add when making their PR,

Most users won't have high enough privileges in the repo. I think they need "Triage" at least.

Yes, I think you're right. So there is no simpler answer.
I think the solution with the Config label's interesting, and if an automated generator makes its way into other software packages then that also helps raise the profile of R-Multiverse.

It would be nice if Config/R-multiverse/domain were kept up to date, but it really only needs to be accurate at the time a package is manually reviewed at r-multiverse/contributions. The underlying goal is to decrease the workload of moderators. Instead of being responsible for all the packages, we want moderators to just focus on ones relevant to their expertise (whether it's spatial, Bayesian, time series forecasting, Rust infrastructure, etc.). When a moderator has a free moment to review some packages, they should be able to just go into r-multiverse/contributions/pulls and filter on the labels they want to review.

If this field/label is needed only at the review time, why include it in the DESCRIPTION file of the package? I would then make it a field on the issue when submitting the package to r-multiverse for review. The bot could read the issue and then assign the label automatically without needing to modify the package for being included in r-multiverse.

If this field/label is needed only at the review time, why include it in the DESCRIPTION file of the package?

We could consider that route, if

it doesn't matter if the package authors explicitly consent to all the labels, and
we can reliably parse the text in the PR description.

For (2), we might have a PR template with a special syntax to facilitate this. But the data would be less structured than DESCRIPTION/Config fields, so I think we would have to accept that errors would happen more often.

The infrastructure for domains could be as simple as a single github.com/r-multiverse/domains repo with a simple Markdown file for each domain and a simple scheduled GitHub Actions workflow to build the pages for all the domains.

Neat idea!

I think the automatically-updating domain pages idea could work well.
Just a note that I think 3 is not relevant where the licence is open source (e.g. R-universe just scrapes all of CRAN). So if you're concerned about 3, then I think a licence check would probably work as well if not better.
Also I don't at this point have a preference whether this should be named "domain" or something else.

Also I don't at this point have a preference whether this should be named "domain" or something else.

I'm thinking "topics" would be a better name. That's my preference now.

Just a note that I think 3 is not relevant where the licence is open source (e.g. R-universe just scrapes all of CRAN). So if you're concerned about 3, then I think a licence check would probably work as well if not better.

That's an interesting point. A valid open-source license really is the most reliable and direct form of consent to redistribute the software. Maybe that could simplify https://github.com/r-multiverse/r-multiverse.github.io/pull/33

I am working on a big update to multiverse.internals (mostly for https://github.com/r-multiverse/r-multiverse.github.io/pull/33) and checking the DESCRIPTION file for topics seems like a lot of extra work. Maybe we could just ask contributors to put topic names in PR titles and then have moderators search https://github.com/r-multiverse/contributions/pulls for e.g. is:pr is:open in:title spatial.

For other reasons I put this request for arbitrary metadata, which might be helpful for this purpose: https://github.com/r-universe-org/help/issues/530


This input should be line oriented by default and use the line codec.

See https://github.com/logstash-plugins/logstash-codec-multiline/issues/14
Preliminary:

the line codec is replaced by the multiline codec.
stdin is given data larger than 32K

Fault:

the multiline codec expects line oriented data
stdin input reads data in 32K chunks
it is highly unlikely that the newline characters align on the 32K boundary.
when the last character of the chunk is not a newline, the multiline codec assumes \npiece_of_line_in_this_side_of_32K_block is a full line and buffers it as such. The other piece of the line in the next 32K block is also treated as a line
when the multiline codec combines these 'lines', one sees an extra newline in the middle of a natural line.

Proposal:

use FileWatch::BufferedTokenizer to line orient the data fed to the codec and make the plain codec the default.

I believe this issue is responsible for the numerous failures I'm getting when trying to parse my multiline log stream using stdin w/ the multiline codec. When using the multiline filter this behavior is not a factor, only when using multiline as a codec with the stdin input.
[amartinez@centos4 ocppserver-logstash]$ zcat ~/SessionData/ocpplogs/2016-03-13-ocppserver.log.gz | tail -n +130000 | head -65000 | sudo /opt/logstash/bin/logstash -b 250 -f bugRepro.conf | grep ""ocpp_logtime" =>"
"ocpp_logtime" => "[13 Mar 201\n6 04:16:10:353]"
"ocpp_logtime" => "[13 Mar 2016 04:19:08:\n608]"
"ocpp_logtime" => "[13 Mar 2016 04:\n19:52:908]"
"ocpp_logtime" => "[13 Mar 2016 04:20:06\n:111]"
"ocpp_logtime" => "[13 Mar 2016 04:20\n:15:217]"
"ocpp_logtime" => "[13 Mar 2016 04:22:58:1\n47]"
"ocpp_logtime" => "[13 Mar 2016 04:24:\n53:896]"
"ocpp_logtime" => "[13 Mar 2016 0\n4:25:21:805]"
"ocpp_logtime" => "[13 Mar 20\n16 04:27:05:976]"
"ocpp_logtime" => "[13 Mar 20\n16 04:27:43:712]"
"ocpp_logtime" => "[13 Mar 2016 04:29:44:464\n]"
"ocpp_logtime" => "[13 Mar 2016 04:35:08:17\n2]"
Config @ https://github.com/anthonyjmartinez/ocppserver-logstash/tree/bug-testing

The next major release of LS will solve this.  Your only option now is to use a file as a intermediate store after decompressing and chopping up the original.

Thanks for the information. How chopped up does the original need to be in order to avoid further issues? Does this also mean that using filebeat to handle the live stream from the source machine directly is not possible at this time?

By chopped up I refer to your tail -n +130000 | head -65000 bit. I meant that after you unzip the file and discard any lines you want and append the result to a new file - then LS will read the new file and handle multiline but you would need auto-flush.
Filebeat is preferable as it has a different implementation of multiline that does not have the line requirement built in. Filebeat tails files though, so try to have the multiline pattern match at the end of the block.

FYI (to future readers of this issue) We are planning a change to the way inputs use functions like line and multiline. This is scheduled to be in the next major release whenever that is.

So, was this ever resolved? I am still getting this issue. I'm using Logstash version 6.7.0.

@guyboertje Sorry to keep pestering you, but was there ever a resolution to this problem?


cmake: Only set deprecated property when supported

Description
CMake versions older than 3.22 do not supported setting the deprecated property on an INTERFACE target.
I have tested with CMake 3.22 and 3.13 locally.
Fixes https://github.com/uxlfoundation/oneMath/issues/619

what happen if the cmake version is older than 3.22? Don't we want to manually leave a deprecation message or something?

what happen if the cmake version is older than 3.22? Don't we want to manually leave a deprecation message or something?

The deprecation property is used to only add a message if a deprecated target is used. In our case we want the deprecated target to be an alias of the new target which does not seem to be possible before 3.22. Adding a message() would be printed even in valid usages so we can't do this.
Users using the minimum CMake version won't get a warning when using a deprecated target unfortunately. I don't think this is a good enough reason to bump the CMake version but that would be fine with me.

Pinging @vmalia since you are around. Could your team help review this by the end of next week?