Virtual desktop specific zone layout

I'm not sure if this is a missing feature or a bug (V0.27.1). But what is crucial for my uses cases is to have different zone layouts for different virtual desktops.
Maybe this is already covered by other virtual desktop related issues.

Expected Behaviour:
Layouts are specific to virtual desktops.

It's a bug

@fesc2000
just tested this on 0.27.1 and it doesn't repro for me.
Are you using custom layouts or the default templates?

Yes, these are custom layouts. I just checked:

when i apply a default layout it indeed only applies to the VD (nr 1) i'm currently on.
The other VD (nr 2) retains its custum layout.
When i then apply a custom layout to VD nr.1 it is applied to both virtual desktops.

@fesc2000
I still cannot reproduce it.
I followed you steps and also kept switching VDs and applying new layouts.
In 0.29 we will provide a bug report tool that will help collecting data.

Not sure if this is similar, same issue BUT i'm using 31.2. The issue I have is switching to virtual desktops. I have 2 ATM and I cannot click into the 2nd desktop. Stopping/starting the application sometimes fixes the issue. Not today.
I'm attaching two bug reports. One before stop/start the app and one after.
PowerToysReport_2021-02-11-10-25-31.zip
PowerToysReport_2021-02-11-10-26-35.zip

@kemerickpq
can you please elaborate on the repro steps?

@fesc2000
Sure. Using Windows 10 I've created multiple desktop. Two in my case. The second desktop is used for various tools ( Visul Code, Powershell, AWS Workspaces, etc... When I click [Start]+[Tab] I have the option to cycle through the desktops. As it stands I click the 2nd desktop, but it simply does nothing and returns me to the original desktop.

@fesc2000
what happens if you use the Win + Ctrl + right arrow shortcut to switch desktops?

Using those keys - it just cycles the 1 desktop.

@kemerickpq

Stopping/starting the application sometimes fixes the issue. Not today.

If quitting PowerToys is not enough to fix this problem, I would guess that PowerToys is not the cause.
Restarting Windows does fix the problem?

Yes .. rebooting fixes it for a while. I haven't determined if hibernation (sleep) or multiple users is contributing. Seems unlikely, but I agree that PowerToys may not be the issue.

Just updated to v0.31.2. It seems to fix the original issue, my custom layouts are now desktop specific.


Improve Shutdown Reliability

Make MongoDriver always use its own ActorSystem for increased isolation from other ActorSystems
MongoDriver now will not initialize from a 3rd party actor system
Add a Supervisor actor to MongoDriver to supervise shutdown of the driver and its ActorSystem
Give names to Monitor and Connection actors for easier tracking
Make Monitor/Connection/Supervisor actor names unique for better debugging
Make MongoDriver.close exit cleanly by waiting for ActorSystem to shutdown
When MongoDBSystem is closing, if it gets a ChannelConnected, just close the channel and log a warning
Add a test case to test the above.
Various documentation fixes to quiet down warnings a bit.

I would really like to use that with "production" version.
Master is currently unusable for me, for examlple the code of EvalCommand is commented and I rely on that.
So I tried to rebase that fix on 0.10.5.x.akka23 but I failed, trying to make those reactivemongo.core.nodeset.ProtocolMetadata work...
That would nice you could cut a release in near future @sgodbillon, even just a snapshot that would help a lot.
This problem is relatively critical for us, it create lot of issues when trying to use reactivemongo inside command line tools as part of some CI pipelines.

:+1:

Seems good to me :)

@reid-spencer Can you edit your PR to address my comments?  I'll merge it as soon it is done.

@sgodbillon - The requested changes have been made.

Thanks @reid-spencer , merging it :)
Can you take a look at https://travis-ci.org/ReactiveMongo/ReactiveMongo/builds/48764736? Seems that the build fails with openjdk6.  Still merging it though – we can focus on that error in a next PR.

@sgodbillon - That's just a timing thing:
[info] MongoDriver should
[info] ! start and close cleanly with no connections
[error]    TimeoutException: : Await termination timed out after [100 milliseconds]  (ActorSystem.scala:816)
[error] akka.actor.ActorSystemImpl$TerminationCallbacks.ready(ActorSystem.scala:816)
[error] akka.actor.ActorSystemImpl$TerminationCallbacks.ready(ActorSystem.scala:786)
[error] akka.actor.ActorSystemImpl.awaitTermination(ActorSystem.scala:642)
[error] reactivemongo.api.MongoDriver.close(api.scala:512)
[error] MongoDriverSpec$$anonfun$1$$anonfun$apply$1.apply(MongoDriverSpec.scala:16)
[error] MongoDriverSpec$$anonfun$1$$anonfun$apply$1.apply(MongoDriverSpec.scala:14)

Travis machines are slow. We should probably skip that test  if the TRAVIS environment variable is set.


Add JeffLirion and tuxuser to CONTRIBUTORS

I hope it's okay if I don't want my full name published and rather go with the nickname.

Coverage decreased (-0.4%) to 43.485% when pulling a946c3b12142a49b9869faa350d6e184c0042041 on tuxuser:contributors_add into 40ffe13448857df6d2ce34450f4a68234ade5b87 on google:master.

That's up to you!

Thanks, @fahhem and @tuxuser!  Any chance we can get a version bump and a release on pypi?


Taiko docs

I think that the only thing that is missing prior to merge is to double-check the general text and the second thing is the "Testnet" label. Ideally it should have a different colour than the Mainnet label, similar to how Optimistic Rollups have different colour compared to ZK Rollups.


Powershell script hangs when started from Run Configuration with missing mandatory parameter.

The current PowerShell scripts when ran with the default run configuration will run in interactive mode.
In interactive mode, PowerShell upon encountering a missing mandatory parameter, will prompt the user to input that parameter, which the run window does not support at the moment, and this causes the process hanging that can only be resolved by terminating it.
A potential fix is to run PowerShell in non-interactive mode, when starting from a run configuration, by adding "-NonInteractive" to the command parameters, as that would cause the script to terminate with missing mandatory parameter exception instead.
It would be nice if the "-NonInteractive" parameter be added to the default PowerShell run configuration template of the plugin.
Tested on Pycharm 2021.2.1
Reproducable code:
MandatoryParamDeadlock.ps1
param(
    # Mandatory Demo Parameter
    [Parameter(Mandatory)]
    [string]
    $DemoMandatoryParameter
)

Write-Host $DemoMandatoryParameter

Hanging Run Configuration:

Fixed Run Configuration:

This seems to be fixed by #90.


AK3DPanner broken in v4.0

This commit seems to break the functionality of an AKAudioPlayer used with an AK3DPanner.
let player = try! AKAudioPlayer(file: audioFile, looping: true)
let panner = AK3DPanner(player)
AudioKit.output = panner
AudioKit.start()
player.play()

This causes a crash saying that player was started in a disconnected state. This code works in previous versions of AudioKit

Good catch.  Thanks for finding the commit, fixing now.


Add support for setting to run scripts in isolation

We recently added a python.useIsolation setting in vscode-python to control running scripts in isolation: https://github.com/microsoft/vscode-python/pull/14845. Right now this setting only lives in the isolate branch of the vscode-python repo, but we're working towards adding support for this setting wherever we call the isolate script.
You may find it useful too 🙂

Details of why can be found here https://teams.microsoft.com/l/message/19:9b163ad1e1ed4c49938d9692be1ce751@thread.skype/1607553932217?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=6182cd1a-acf2-40e6-8b08-07bd25990df8&parentMessageId=1607553932217&teamName=Python for VS Code&channelName=Data Science&createdTime=1607553932217
TLDR - If users install packages using pip -e, then the only way to get stuff working for such packages is to ignore using the isolation setting.
I believe this only applies to Jupyter extension when we start python kernels (or a damone that starts the python kernel)

I believe this was deprecated by the trusted workspace work here: https://github.com/microsoft/vscode-python/pull/16485


CI: Use /info endpoint to verify data collection, not the raw CSVs

This allows for the same CI scripts to work regardless of data storage backend.
Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Pull Request title is properly formatted: FAI-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting main: [0.3.x] FAI-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

/test trustyai-explainability-e2e

/test trustyai-explainability-e2e


Unnecessary need for manual resolution of ambiguity

As of this commit[1], with the latest bikeshed[2], I needed to disambiguate ''auto'' into ''overflow/auto'' and ''continue/auto'' inside the propdef for overflow and continue (respectively) in css-overflow/Overview.bs, otherwise bikeshed would warn me about guessing, and actually pick the wrong one in the case of continue.
Given that it is inside a propdef, this shouldn't be considered ambiguous, and bikeshed should figure it out on its own.
[1] https://github.com/w3c/csswg-drafts/commit/1c4304f1b8624b77e5c14983f589c1cca62f959f
[2] https://github.com/tabatkins/bikeshed/commit/6aff9bd1a247a130fcb97b3309c34ee5aec674d0

Done!  I had to add a new feature to handle this (the data-link-for-hint attribute), but it's actually a really useful thing in general.  I'll document it later, but for now, propdef tables automatically apply this and will link to the correct property's values automatically.


Bug: color abnormal after source init.vim file

Self Checks

[ ] I'm using the latest lualine.
[ ] I didn't find the issue in existing issues or PRs.

How to reproduce the problem

Expected behaviour

Actual behaviour

Minimal config to reproduce the issue

Additional information

the only workaround is to use :colorscheme xxx to reset colorscheme

my vimrc file https://github.com/yimingwangdell/vimrc/blob/master/nvim/init.vim


Feature/logwidg3

I moved a folder A/ from Dropbox to OSF Storage, and the project log says:
"Taylor Swift moved A/ from Dropbox in Blank Space to A/ in OSF Storage in Blank Space"
But the recent activity log says:

I also think giving information about the file provider would be useful, since the project logs include that info.

Pass complete @hmoco! :octocat: I just had a few minor comments & questions.

@samanehsan, have responded, back to ya!

Also, it looks like "move" actions are still getting logged as "copy" actions.

Some of my logs are blank:

And the console error message is There is no text entry in dictionary for the action :comment_restored

The project logs for file comments are slightly different:

For consistency, I think that information should also be included in the recent activity logs.

The blank logs are now rendering properly!

The file comment logs are still the same though -- is it possible to include which file was commented?

Back to you @hmoco! :octopus:

Oh, one more thing -- folders should not be linked because they will always go to a Not Found error page:

The reason for the comment logs appearing that way is that it seems that the file params are not being serialized and sent as part of v2 log responses.

@samanehsan have responded to the folder comment, I do not believe comment log serialization is within the scope of this PR, but if you think otherwise I can try and add that in.

@samanehsan, here is the ticket for the improvement necessary to include the file links in the comment logs: https://openscience.atlassian.net/browse/OSF-5766

Looks good to me @hmoco! :umbrella:


haproxy download failure

Running a concourse deployment a run into failure due to inability to download haproxy version.
Here is the log from deploy operation:
Using remote release 'https://github.com/cloudfoundry-community/haproxy-boshrelease/releases/download/v8.0.9/haproxy-8.0.9.tgz'

Director task 31
  Started downloading remote release > Downloading remote release. Failed: Downloading remote release failed. Check task debug log for details. (00:00:01)

Error 100001: Downloading remote release failed. Check task debug log for details.

Task 31 error

And below I have the output of bosk task --debug:
I, [2017-04-25 13:44:27 #14362] []  INFO -- DirectorJobRunner: Starting task: 30
I, [2017-04-25 13:44:27 #14362] [task:30]  INFO -- DirectorJobRunner: Creating job
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000125s) SELECT NULL
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000191s) SELECT * FROM "tasks" WHERE "id" = 30
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000123s) SELECT NULL
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000186s) SELECT * FROM "tasks" WHERE "id" = 30
I, [2017-04-25 13:44:27 #14362] [task:30]  INFO -- DirectorJobRunner: Performing task: #<Bosh::Director::Models::Task @values={:id=>30, :state=>"queued", :timestamp=>2017-04-25 13:44:26 UTC, :description=>"create release", :result=>nil, :output=>"/var/vcap/store/director/tasks/30", :checkpoint_time=>2017-04-25 13:44:26 UTC, :type=>"update_release", :username=>"admin", :deployment_name=>nil, :started_at=>nil}>
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000135s) SELECT NULL
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000075s) BEGIN
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000400s) UPDATE "tasks" SET "state" = 'processing', "timestamp" = '2017-04-25 13:44:27.927250+0000', "description" = 'create release', "result" = NULL, "output" = '/var/vcap/store/director/tasks/30', "checkpoint_time" = '2017-04-25 13:44:27.927386+0000', "type" = 'update_release', "username" = 'admin', "deployment_name" = NULL, "started_at" = '2017-04-25 13:44:27.927326+0000' WHERE ("id" = 30)
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000946s) COMMIT
I, [2017-04-25 13:44:27 #14362] [task:30]  INFO -- DirectorJobRunner: Processing update release
I, [2017-04-25 13:44:27 #14362] [task:30]  INFO -- DirectorJobRunner: Downloading remote release
I, [2017-04-25 13:44:27 #14362] [task:30]  INFO -- DirectorJobRunner: Downloading remote release from https://github.com/cloudfoundry-community/haproxy-boshrelease/releases/download/v8.0.9/haproxy-8.0.9.tgz
E, [2017-04-25 13:44:28 #14362] [task:30] ERROR -- DirectorJobRunner: Downloading remote release from https://github.com/cloudfoundry-community/haproxy-boshrelease/releases/download/v8.0.9/haproxy-8.0.9.tgz failed: Moved Permanently
E, [2017-04-25 13:44:28 #14362] [task:30] ERROR -- DirectorJobRunner: Downloading remote release failed. Check task debug log for details.
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/download_helper.rb:42:in `block (2 levels) in download_remote_file'
/var/vcap/packages/ruby/lib/ruby/2.3.0/net/http.rb:1446:in `block in transport_request'
/var/vcap/packages/ruby/lib/ruby/2.3.0/net/http/response.rb:163:in `reading_body'
/var/vcap/packages/ruby/lib/ruby/2.3.0/net/http.rb:1445:in `transport_request'
/var/vcap/packages/ruby/lib/ruby/2.3.0/net/http.rb:1407:in `request'
/var/vcap/packages/ruby/lib/ruby/2.3.0/net/http.rb:1308:in `request_get'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/download_helper.rb:19:in `block in download_remote_file'
/var/vcap/packages/ruby/lib/ruby/2.3.0/net/http.rb:853:in `start'
/var/vcap/packages/ruby/lib/ruby/2.3.0/net/http.rb:584:in `start'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/download_helper.rb:16:in `download_remote_file'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/update_release.rb:67:in `download_remote_release'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/update_release.rb:45:in `block in perform'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/base_job.rb:62:in `block in single_step_stage'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/base_job.rb:56:in `block in track_and_log'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/event_log.rb:99:in `advance_and_track'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/base_job.rb:54:in `track_and_log'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/base_job.rb:62:in `single_step_stage'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/update_release.rb:45:in `perform'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/job_runner.rb:106:in `perform_job'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/job_runner.rb:32:in `block in run'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh_common-260.0.0/lib/common/thread_formatter.rb:49:in `with_thread_name'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/job_runner.rb:32:in `run'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/base_job.rb:10:in `perform'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/db_job.rb:32:in `block in perform'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/db_job.rb:80:in `block (3 levels) in run'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/eventmachine-1.0.4/lib/eventmachine.rb:1046:in `block in spawn_threadpool'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `block in create_with_logging_context'
D, [2017-04-25 13:44:28 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000195s) SELECT NULL
D, [2017-04-25 13:44:28 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000076s) BEGIN
D, [2017-04-25 13:44:28 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000296s) UPDATE "tasks" SET "state" = 'error', "timestamp" = '2017-04-25 13:44:28.319331+0000', "description" = 'create release', "result" = 'Downloading remote release failed. Check task debug log for details.', "output" = '/var/vcap/store/director/tasks/30', "checkpoint_time" = '2017-04-25 13:44:27.927386+0000', "type" = 'update_release', "username" = 'admin', "deployment_name" = NULL, "started_at" = '2017-04-25 13:44:27.927326+0000' WHERE ("id" = 30)
D, [2017-04-25 13:44:28 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000904s) COMMIT
I, [2017-04-25 13:44:28 #14362] []  INFO -- DirectorJobRunner: Task took 0.397069564 seconds to process.

Hower when manually try to download for the link i.e. https://github.com/cloudfoundry-community/haproxy-boshrelease/releases/download/v8.0.9/haproxy-8.0.9.tgz it works. Could you please advice?

This likely has to do with haproxy moving from cloudfoundry-community to cloudfoundry-incubator.

On Apr 25, 2017, at 9:54 AM, Ioannis Polyzos<EMAIL_ADDRESS>wrote:
Running a concourse deployment a run into failure due to inability to download haproxy version. Below I have the output of bosk task --debug:
I, [2017-04-25 13:44:27 #14362] []  INFO -- DirectorJobRunner: Starting task: 30
I, [2017-04-25 13:44:27 #14362] [task:30]  INFO -- DirectorJobRunner: Creating job
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000125s) SELECT NULL
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000191s) SELECT * FROM "tasks" WHERE "id" = 30
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000123s) SELECT NULL
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000186s) SELECT * FROM "tasks" WHERE "id" = 30
I, [2017-04-25 13:44:27 #14362] [task:30]  INFO -- DirectorJobRunner: Performing task: #<Bosh::Director::Models::Task @values={:id=>30, :state=>"queued", :timestamp=>2017-04-25 13:44:26 UTC, :description=>"create release", :result=>nil, :output=>"/var/vcap/store/director/tasks/30", :checkpoint_time=>2017-04-25 13:44:26 UTC, :type=>"update_release", :username=>"admin", :deployment_name=>nil, :started_at=>nil}>
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000135s) SELECT NULL
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000075s) BEGIN
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000400s) UPDATE "tasks" SET "state" = 'processing', "timestamp" = '2017-04-25 13:44:27.927250+0000', "description" = 'create release', "result" = NULL, "output" = '/var/vcap/store/director/tasks/30', "checkpoint_time" = '2017-04-25 13:44:27.927386+0000', "type" = 'update_release', "username" = 'admin', "deployment_name" = NULL, "started_at" = '2017-04-25 13:44:27.927326+0000' WHERE ("id" = 30)
D, [2017-04-25 13:44:27 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000946s) COMMIT
I, [2017-04-25 13:44:27 #14362] [task:30]  INFO -- DirectorJobRunner: Processing update release
I, [2017-04-25 13:44:27 #14362] [task:30]  INFO -- DirectorJobRunner: Downloading remote release
I, [2017-04-25 13:44:27 #14362] [task:30]  INFO -- DirectorJobRunner: Downloading remote release from https://github.com/cloudfoundry-community/haproxy-boshrelease/releases/download/v8.0.9/haproxy-8.0.9.tgz
E, [2017-04-25 13:44:28 #14362] [task:30] ERROR -- DirectorJobRunner: Downloading remote release from https://github.com/cloudfoundry-community/haproxy-boshrelease/releases/download/v8.0.9/haproxy-8.0.9.tgz failed: Moved Permanently
E, [2017-04-25 13:44:28 #14362] [task:30] ERROR -- DirectorJobRunner: Downloading remote release failed. Check task debug log for details.
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/download_helper.rb:42:in block (2 levels) in download_remote_file' /var/vcap/packages/ruby/lib/ruby/2.3.0/net/http.rb:1446:in block in transport_request'
/var/vcap/packages/ruby/lib/ruby/2.3.0/net/http/response.rb:163:in reading_body' /var/vcap/packages/ruby/lib/ruby/2.3.0/net/http.rb:1445:in transport_request'
/var/vcap/packages/ruby/lib/ruby/2.3.0/net/http.rb:1407:in request' /var/vcap/packages/ruby/lib/ruby/2.3.0/net/http.rb:1308:in request_get'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/download_helper.rb:19:in block in download_remote_file' /var/vcap/packages/ruby/lib/ruby/2.3.0/net/http.rb:853:in start'
/var/vcap/packages/ruby/lib/ruby/2.3.0/net/http.rb:584:in start' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/download_helper.rb:16:in download_remote_file'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/update_release.rb:67:in download_remote_release' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/update_release.rb:45:in block in perform'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/base_job.rb:62:in block in single_step_stage' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/base_job.rb:56:in block in track_and_log'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/event_log.rb:99:in advance_and_track' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/base_job.rb:54:in track_and_log'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/base_job.rb:62:in single_step_stage' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/update_release.rb:45:in perform'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/job_runner.rb:106:in perform_job' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/job_runner.rb:32:in block in run'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh_common-260.0.0/lib/common/thread_formatter.rb:49:in with_thread_name' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/job_runner.rb:32:in run'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/base_job.rb:10:in perform' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/db_job.rb:32:in block in perform'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/bosh-director-260.0.0/lib/bosh/director/jobs/db_job.rb:80:in block (3 levels) in run' /var/vcap/packages/director/gem_home/ruby/2.3.0/gems/eventmachine-1.0.4/lib/eventmachine.rb:1046:in block in spawn_threadpool'
/var/vcap/packages/director/gem_home/ruby/2.3.0/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `block in create_with_logging_context'
D, [2017-04-25 13:44:28 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000195s) SELECT NULL
D, [2017-04-25 13:44:28 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000076s) BEGIN
D, [2017-04-25 13:44:28 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000296s) UPDATE "tasks" SET "state" = 'error', "timestamp" = '2017-04-25 13:44:28.319331+0000', "description" = 'create release', "result" = 'Downloading remote release failed. Check task debug log for details.', "output" = '/var/vcap/store/director/tasks/30', "checkpoint_time" = '2017-04-25 13:44:27.927386+0000', "type" = 'update_release', "username" = 'admin', "deployment_name" = NULL, "started_at" = '2017-04-25 13:44:27.927326+0000' WHERE ("id" = 30)
D, [2017-04-25 13:44:28 #14362] [task:30] DEBUG -- DirectorJobRunner: (0.000904s) COMMIT
I, [2017-04-25 13:44:28 #14362] []  INFO -- DirectorJobRunner: Task took 0.397069564 seconds to process.
Hower when manually try to download for the link i.e. https://github.com/cloudfoundry-community/haproxy-boshrelease/releases/download/v8.0.9/haproxy-8.0.9.tgz https://github.com/cloudfoundry-community/haproxy-boshrelease/releases/download/v8.0.9/haproxy-8.0.9.tgz it works. Could you please advice?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/starkandwayne/concourse-deployment/issues/8, or mute the thread https://github.com/notifications/unsubscribe-auth/AG2SUm5oP6YhyR2D00SK4tsii97TSV4tks5rzfsugaJpZM4NHhR6.

I can confirm it works and proceeds with the download when upgrade version to 8.1.0.
p.s a pull request submited...

@ipolyzos Hey I just want to confirm that I'm closing this issue as Geoff had successfully merged your pull request on Apr 25th

@xanderrman  I can confirm it is fine. Please proceed. Thank you.


chore: jsonfmt windowsiot

Automation for azure-sdk-for-python

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

Can one of the admins verify this patch?


Receiving bad gateway

Trying to get my stats at https://www.githubwrapped.io/nickatnight for 2023 and am receiving bad gateway response. See image

Looks to be resolved...closing


Core-logs page

Review my code:

made core-logs page.
Getting data from our server using fetch.
filter functionality.

good job!


chore(npm): new prerelease publish shell script

Helper script for pre releasing

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: process secret in config

Summary:
Briefly describe the changes made in this PR.
Issue Reference(s):
Fixes #2654
/claim #2654
Build & Testing:

[x] I ran cargo test successfully.
[x] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[x] I have added relevant unit & integration tests.
[ ] I have updated the documentation accordingly.
[x] I have performed a self-review of my code.
[x] PR follows the naming convention of <type>(<optional scope>): <title>

Moving to draft to reduce noise and improve CI efficiency. Once you are ready just mark it as "ready to review". Feel free to give a shoutout on the #contributors channel on Discord if you want immediate attention.


Unable to open the .exe file

I have downloaded the zip file for the automatic installer but was unable  to find out how to download it. This is on mac, and when I press the .exe file, it just opens up my unzipper. Do I need wine or is there a different download for mac.

I.RULE is not supported on Mac.
For the record, Ruler.IRule will totally run on Mac, it'll just fail to launch the game. I'd recommend installing I.RULE withoutr RULER and just using Bootcamp.


[Improvement] Upgrading and migration script for Jdbc

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

What would you like to be improved?
Since 1.6.0, Kyuubi supports use JDBC to store metadata for Batch Job API, we need upgrading and migration script for that like HMS does.
How should we improve?
Providing upgrading and migration script like HMS does.
Are you willing to submit PR?

[ ] Yes. I can submit a PR independently to improve.
[ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
[ ] No. I cannot submit a PR at this time.

I'd like to look into this: https://github.com/apache/hive/tree/master/metastore/scripts

Thanks @lightning-L


Dependencies update

This PR updates all of the library dependencies and explicitly imports those dependencies with implementation instead of compileOnly.

Gradle
Kotlin
Gson
MockK
Junit Jupiter
Kover

Thanks @brian-livefront


Add Substring_by_char

Which issue does this PR close?

Closes #1768.
Rationale for this change
Support substring by char
What changes are included in this PR?

new pub function substring_by_char
tests
benchmark
update docs

Performance
substring utf8 (start = 0, length = None)
                        time:   [20.035 ms 20.056 ms 20.081 ms]
Found 8 outliers among 100 measurements (8.00%)
  1 (1.00%) high mild
  7 (7.00%) high severe

substring utf8 (start = 1, length = str_len - 1)
                        time:   [21.334 ms 21.358 ms 21.388 ms]
Found 7 outliers among 100 measurements (7.00%)
  5 (5.00%) high mild
  2 (2.00%) high severe

substring utf8 by char  time:   [117.18 ms 117.29 ms 117.41 ms]
Found 10 outliers among 100 measurements (10.00%)
  4 (4.00%) high mild
  6 (6.00%) high severe

1/6 of the speed of substring(by byte)
Are there any user-facing changes?
Yes.

Codecov Report

Merging #1784 (f91ff1b) into master (1a64677) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1784      +/-   ##
==========================================
+ Coverage   83.39%   83.42%   +0.02%
==========================================
  Files         198      198
  Lines       56142    56269     +127
==========================================
+ Hits        46822    46940     +118
- Misses       9320     9329       +9

Impacted Files
Coverage Δ

arrow/src/compute/kernels/substring.rs
99.51% <100.00%> (+0.09%)
:arrow_up:

parquet/src/util/cursor.rs
62.18% <0.00%> (-1.69%)
:arrow_down:

parquet/src/file/serialized_reader.rs
94.46% <0.00%> (-1.17%)
:arrow_down:

parquet_derive/src/parquet_field.rs
65.53% <0.00%> (-0.69%)
:arrow_down:

arrow/src/datatypes/datatype.rs
65.42% <0.00%> (-0.38%)
:arrow_down:

parquet/src/encodings/encoding.rs
93.46% <0.00%> (-0.20%)
:arrow_down:

parquet/src/file/writer.rs
92.84% <0.00%> (-0.02%)
:arrow_down:

parquet/src/arrow/arrow_writer.rs
97.76% <0.00%> (-0.02%)
:arrow_down:

parquet/src/arrow/schema.rs
96.81% <0.00%> (-0.01%)
:arrow_down:

arrow/src/ffi.rs
86.97% <0.00%> (ø)

... and 10 more

Continue to review full report at Codecov.

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


[HUDI-2875] Make HoodieParquetWriter Thread safe and memory executor …

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
Fix problem mentioned in https://issues.apache.org/jira/browse/HUDI-2875.
Brief change log

Add synchronized to HoodieParquetWriter to make sure it is thread safe for any possible following uses.
Add a graceful exit for BoundedInMemoryExecutor.
let's first stop BoundedInMemoryExecutor and then close HoodieMergeHandle in SparkMergeHelper.

Verify this pull request
This pull request is manually verified the change by running a job locally
Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@hudi-bot run azure

curious to know what causes concurrent writers to a given HoodieParquetWriter? or is there some internal parquet shared state that is non-thread safe here?

Hi vinothchandar:
Concurrent writing to HoodieParquetWriter occurs at following code
https://github.com/apache/hudi/blob/master/hudi-client/hudi-spark-client/src/main/java/org/apache/hudi/table/action/commit/SparkMergeHelper.java#L103
When speculation is triggered, we firstly call mergeHandle.close which calls parquetWriter close method. At the same time, producer and consumer logic is still working, so write method of mergeHandle is called at same time which call write method of parquetWriter.
And parquetWriter does have a state which is not thread safe. It holds BytesInput which is used as internal data storage in parquet column format, it is not thread safe and its life cycle is controlled by parquetWriter. Such data structure is reused within JVM. So parquet writer cannot be written after closed to ensure relevant data structure will not be written into after being reset.

@hudi-bot run azure

Thanks @guanziyue for the fix. if I am not wrong, you have this fix already in your prod env and has been running smoothly w/o issues.

@guanziyue : we are looking to get this in for 0.11. wanted to keep you in the loop.

Thanks @guanziyue for the fix. if I am not wrong, you have this fix already in your prod env and has been running smoothly w/o issues.

Actually, I don't have an integral test of hudi. But I do try this in my prod env whic use hudi in a specific way.

@yihua : do you mind taking a look. LGTM.

@guanziyue thank you for taking the time to troubleshoot this concurrency issues and implement the fix!
I echo @vinothchandar concerns and i think we're taking a step a bit too far -- ParquetWriter is not assumed to be thread-safe, neither do i believe we should make it such.
Instead, i believe we should just resolve the problem with its concurrent access (which you already did) and make sure we make it clear that ParquetWriter is not thread-safe so its usage need to be properly guarded externally.

@guanziyue thank you for taking the time to troubleshoot this concurrency issues and implement the fix!
I echo @vinothchandar concerns and i think we're taking a step a bit too far -- ParquetWriter is not assumed to be thread-safe, neither do i believe we should make it such.
Instead, i believe we should just resolve the problem with its concurrent access (which you already did) and make sure we make it clear that ParquetWriter is not thread-safe so its usage need to be properly guarded externally.

Hi @alexeykudinkin, may I know if your concern is "adding a lock to parquetWriter" or "adding a lock to hot path"? I'm afraid that it is difficult to come up with a method to guarantee this problem is totally solved except adding a signal to hot path. Producer need to check if current thread is interrupted and response to it in a reasonable time or consumer need to immediately reject any writing just after close method is called, which also need a lock on hot path. For producer solution, we can have a lock-free check. For consumer, we may use volatile rather than a lock? But either of them is adding something to hot path.

@guanziyue it's not only performance, it's also creating additional surface that someone could dead-lock on.
My point is simple -- we should fix the root-cause, but we should not re-purpose the components that were not intended to be thread-safe and over-engineer them into ones.

@hudi-bot run azure

@hudi-bot run azure

@hudi-bot run azure

@hudi-bot run azure

Removed lock from parquet writer and avoid concurrent usage of merge handle by using correct order to call relevant methods. Add a test for it.

rebased w/ latest master and pushed an update.

@hudi-bot run azure

LGTM, @nsivabalan @yihua can you please help land that one?


nvcc does not find cicc

Hi,
I compiled core-image-sato-sdk system, it boots and everything works except that when I try to compile in the Jetson board using nvcc it throws an error:
sh: cicc: command not found
After reading in the blog of NVIDIA, I understood that the error is produced because nvcc is not finding nvvm (cicc). I reviewed the nvcc.profile file an effectively, the route of the file does not exists in the root file system. The weirdest part is that in the Packages.gz file of cuda-repo-l4t-8-0-local_8.0.34-1_arm64.deb, cicc is not mentioned. In equivalent files, such cuda-repo-ubuntu1504-7-5-local_7.5-18_amd64.deb, the Packages.gz files indicates that cicc is part of the cuda-core-.deb package.  I checked that core, command-line-tools, and other packages appear in the list of cuda-toolkit_8.0.34-1.bb file. Also, I added  IMAGE_INSTALL+= " cudnn cuda-toolkit" to local.conf file. What do you think can be the problem?
Thank you very much, you did an amazing job developing meta-tegra.
Sergio

I solved my problem adding the folder nvvm manually after flashing the internal SD. I think it can be done inside the cuda-toolkit.bb file, because this directory is not copied in the do_install task. However, I tried to add this to the task and I obtained  some errors because apparently I am trying to override a folder that cuda-cudart.bb already created.

Yes, the /usr/local/cuda-8.0/nvvm subtree wasn't being repackaged with the rest of the toolkit, an oversight on my part.  I've updated the recipe to bring it in.


How to use?

I know this was a lot of hard work, but how do you use it from the command line?

i need to read

But still consider adding example images with example outputs :)

I just added the command line and changed the name, see readme.md for details

但仍可考虑添加带有示例输出的示例图像:)，以 README.md


apply for vercel sponsorship account

We are currently using a trail Vercel account. In order to get a open source sponsored pro account, we need to send them an email that looks something like this:

Hi Product Advocacy Team!
I'm writing to request open source sponsorship for the Pangeo Forge project. Pangeo Forge is an open source project building a cloud-native open scientific data archive, more details can be found on our new Next.js site (https://pangeo-forge.org/) or on GitHub (https://github.com/pangeo-forge).
We have gone through the (https://github.com/pangeo-forge/pangeo-forge.org/issues/29) and have added the requested acknowledgements to our site. The Vercel team name is "pangeo-forge".
Thank you for considering this request.

Before sending this, we need to go through this checklist:

[x] The project should be non-commercial.
[x] The project should be open source.
[x] The project should not use Turborepo, and not be part of a monorepo with commercial projects.
[x] A Vercel banner in the footer of each site page. (see #28)
[x] A Vercel banner in the source repository's README.md file. (see #27)
[x] All links back to Vercel should use a UTM tag with the format: ?utm_source=[team-name]&utm_campaign=oss.

I have sent the email requesting sponsorship to vercel. In the past, this process has gone quite quickly and I'll report back when I hear from them.


Inttest

Jenkins build failed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1102/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1103/


event: YouTube caught censoring comments critical of CCP

This seems to have been discovered as early as 13 May 2020
News coverage mounted on 26 May 2020

Seems to have started with The Verge
Tim Pool and We Are Change use Verge article
Zerohedge did it's own write up, but refs Verge as well

I was wrong, Epoch Times way ahead on this one

And Taiwan news even before them


v-model  binds the id of input radio dynamicly appears only for the first time

Version
2.3.0
Reproduction link
https://codepen.io/xiaoguifly/pen/jwjWdq
Steps to reproduce
When I click one of the radio list,for example the second item ,the id attribute of the radio element only appears for the first time through the console,then I bind the value attribute to the radio, the id attribute appears all the time
What is expected?
the id attribute  of  radio appears all the time
What is actually happening?
the id attribute of radio appears only the first time

Vue.js version
2.3.0
Chrome version
59.0.3071.115 (64-bit)

When I click one of the radio list,for example the second item ,the id attribute of the radio element only appears for the first time through the console,then I bind the value attribute to the radio, the id attribute appears all the time

I don'T understand what you mean by that. To me, the elements seem to work great - styles are applied correctly, a log is printed ot the console for each item on each click ...
What exactly is wrong?

@LinusBorg  Please follow the steps:
1  open the console
2  click one of the items serveral times
3  see the different log,then you can find the differences between the first log and others(the first log has id ,others not)

Not for me:

However now I understood your problem - the id seems to be disappearing when you expect i to be the id (converted to a string)

@LinusBorg  my problem is that when you add :value="item.name" to the input radio,then you will see the logs are the same,I don't know why

because your v-modelis still v-model="item.id"` which still is wrong.

@LinusBorg  when I replace v-model="item.id" with v-model="item.name",the problem is still exist.Am I use the v-model wrong?Because I delete v-model ,then all is ok. Please give me a similar example of its usage,thank you!!!

Please look at my example. v-model="item.name" is still wrong.
I will not answer more questions in this issue. This is not a bug, it's a usage problem on your side. As I alrady suggested, please post your question to forum.vuejs.org or chat.vuejs.org.
I'm happy to help you further on the forum, but not here.


Fix dependency name in deprecated/build.gradle

The build.gradle in the deprecated directory was incorrectly trying to depend on the main project using fabric-api instead of quilted-fabric-api. This was causing build errors when trying include the quilted-fabric-api into projects. This changes has been present on most branches but is missing on 1.20.6 and 1.21

thank you so much for this! I've confirmed that this change was present before 1.20.6


integration with embed.ly

Embed.ly is used by many content provider, including medium.com, to provide a unified way to include 3rd party iframes.

http://embed.ly/providers/new

We already meet most of the requirements, the responsiveness has to be investiated.

@pelikhan what are our oembed endpoints?

Filed a request. Waiting to hear back from the embedly team.

Response from the embedly team:
We will need a few small updates to support this:

* add width, height attributes to oEmbed response
* remove div wrapper around iframe in "html" attribute
* set width and height attributes on iframe to match oEmbed response

e.g.
html:'<iframe src="https://makecode.microbit.org/#sandbox:05526-49228-18219-71208" width="800" height="600">'</iframe>
width:800
height: 600

@pelikhan do you think these changes would interfere with OneNote oembed support?

This is complete: http://embed.ly/provider/makecode

Here's a sample on medium:
https://medium.com/@samel/sample-microbit-embedly-7e04558b0fad
@Jaqster @abchatra

and here's a list of all embedly consumers: http://embed.ly/customers


grafana pod crashing due to persistent volume

What did you do?
Install helm charts
What did you expect to see?
Grafana up and running with persistence
What did you see instead? Under which circumstances?

Unable to mount volumes for pod "grafana-grafana-5554887f4d-k2bxd_monitoring(b184d337-27ec-11e8-91bd-06223c5ed442)": timeout expired waiting for volumes to attach/mount for pod "monitoring"/"grafana-grafana-5554887f4d-k2bxd". list of unattached/unmounted volumes=[grafana-storage]
Error syncing pod

Environment
Kops 1.8 on aws

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.1", GitCommit:"f38e43b221d08850172a9a4ea785a86a3ffa3b3a", GitTreeState:"clean", BuildDate:"2017-10-11T23:27:35Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.6", GitCommit:"6260bb08c46c31eea6cb538b34a9ceb3e406689c", GitTreeState:"clean", BuildDate:"2017-12-21T06:23:29Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
kops,

Manifests:

storageSpec:
   class: default
   accessMode: ReadWriteOnce
   resources:
     requests:
       storage: 2Gi

Prometheus Operator Logs:

I see the volume is dynamically created with the claim is bound.
Even when i delete the pod and automatically recreates, the pod still crashes.

Maybe the storageSpec example in grafana are outdated, could you try to use the same notation that we use in prometheus?

changed but fails validation:

storageSpec:
  volumeClaimTemplate:
    spec:
      accessModes: ["ReadWriteOnce"]
      resources:
        requests:
          storage: 2Gi

The format is different for grafana https://github.com/coreos/prometheus-operator/blob/master/helm/grafana/values.yaml#L70

I successfully created a grafana pod using the storageSpec below, in a k8s created by kops.  The first timeout error is related to something in your infrasctucture  and not in the grafana pod. Did you try to  create a storage in other deployments or you have the same error?
storageSpec:
   class: default
   accessMode: ReadWriteOnce
   resources:
     requests:
       storage: 2Gi

Since we don't support the helm chart in this repo anymore, closing this issue. Feel free to open a new one if you think it's not valid, thanks!


Generate and show recipient's identicon

It'd be nice to generate and show the identicon next to the recipient in the sendTx and the transaction recap (aka signer) views.

In the transaction recap would be already good:


Improve CI

add PHP 7.1
do not allow failure for 7.0
cache only composer downloads, not info about lib versions
prefer to install dist version of dependencies
let the build fail for tests first, CS latter

I would also like to add some external quality/test coverage check tool, but that would require some intervention on the repo settings. Any preference? I like Scrutinizer, but we also have CodeClimate and many others... @dcramer it's up to you, I will gladly add the integration in this PR!

I think we were using Scrutinizer on the sentry-php repo, so probably good to be uniform

Ok great! I've added a minimal .scrutinizer.yml config and the code coverage integration, but I don't have the privileges to set it up on Scrutinizer; if you can activate the repo there it should be enough!

just setup scrutinizer for this repo

Great, thanks! I've excluded the examples folder from the analysis, and this latest push proved that the PR integration is working correctly! :+1:
I'll merge this and later I will try to tackle some of the stuff that emerged from this.


Mine hard negatives instead of random negatives

Proposed changes:

...

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

/modeltest
include:
 - dataset: ["all"]
   config: ["all"]

Closing the issue as there is no improvement in the performance.


LoadASCIIFromFile didn't support wchar/wstring filename

If load file in Windows system, and the filename contain WideChar character, tinygltf can't open it

Unicode build may be possible to read Windows' native UTF8(16?) filename with LoadASCIIFromFile
Another options is use LoadASCIIFromString, or implement LoadASCIIFromStream
https://github.com/syoyo/tinygltf/pull/178
PR of implementing LoadASCIIFromStream is welcome.

I created a PR to support UTF-8 filepath
#216

Thank! PR has been merged so this issue should be ready to close.

Sure


Gaussian_Proc - index out of bounds

Forgive me if this is obvious, but this error can randomly occur and seems to have no dependence upon ParMoo input parameter choices.
Has anyone else encountered & resolved such issue?
Thank you in advance!

@WoodKieran Thanks for flagging this, do you have some sort of minimum working example that reproduces this issue?


SyntaxError in "django-sample" when tried to run the sample

Hello :D
I have this issue when I tried to run the sample
(venv) Eduardos-iMac:django_sample ecarradal$ python manage.py syncdb
Traceback (most recent call last):
  File "manage.py", line 3, in <module>
    from django.core.management import execute_manager
  File "/Users/ecarradal/Documents/documents/decidata/google-api-python-client/venv/lib/python3.6/site-packages/django/core/management/__init__.py", line 52
    except ImportError,e:
                      ^
SyntaxError: invalid syntax

@ecarradal I am assuming you are using Python 3.6? Which version of Django are you using? Also, is it a Mac/PC/Linux machine?

Closing this because there was no response for 7 days, so I am assuming the issue has been resolved. Feel free to reopen this if the problem persists.


chore(deps): bumps projen from 0.17.16 to 0.17.84

Thanks @pgollucci - this was already done and is now fully automated 👍


specify charset to avoid Mojibake

I am getting mojibake when browsing exported webdav with Firefox, specifying charset here to avoid the issue.

TIL what mojibake is, thanks!

Hey @karuboniru
I never added a license to this project and would like to add the MIT license. Do I have your permission to re-license the code that you wrote in this PR to the MIT license?

Of course no problem, I agree with the re-license.

Of course no problem, I agree with the re-license.

Thank you!


Expose file-manager.isTooLarge()

Closes #465
This does the job, but referencing module.exports internally is perhaps a bit ugly, and isn't a pattern used elsewhere in the project.
Would it be preferable to create a FileManager class?  Some thoughts:

fileManager.init() could remain as a factory method for overriding as required
fileManager.getCurrentFiles() appears to be a "static" method anyway, and only used for debug
instead of overriding require('./file-manager').isTooLarge, you would then override require('./file-manager').prototype.isTooLarge

I'll give the above a quick fiddle and see if it works easily 🙂

Ultimately I think a class might make sense, but would be a significant change.  Alternative PR at https://github.com/enketo/enketo-core/pull/470, which is maybe a bit cleaner than this one.


High resolution information is not recovered

I was trying to try out CVD with MiDAS v2 model provided in the code.

When I ran the default parameters for loss, it seemed like that network was being trained from scratch it missed all the information. For instance it lost all the information after one epoch. Here are the results for first 4 epochs. The input video.
When I set the --lambda_reprojection parameter to 10. It did not loose all the information but still lose lot of information. It looks like the network is blurring things out
I face the same issue with mc depth. Lot of information is lost. Video

Is this the expected behavior, also do you have any suggestions?

video

Same problem.  Have you fixed it?


Add implementation of vasprintf on Windows

vsnprintf(NULL, ...) returns the length of the output string.
Therefore, use this before calling vsnprintf again, to figure out the correct length of the string.
Discussion:
  if (::vsnprintf(buf, sizeof(buf), fmt, ap) < 0) { can't really fail, as we're guaranteed to have the correct length.
Should we use an assertion here, instead of an if?

@swift-ci please smoke test

@swift-ci please smoke test

could someone trigger the tests for me - it seems I can't after pushing (with and without -f) to any PR @ddunbar @shahmishal FYI

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

Hmm, looks like there's an odd behaviour difference on Windows vs Unix that's causing the builds to fail:
Same code:
#include <iostream>
#include <stdarg.h>

static std::string getFormattedString(const char* fmt, va_list ap) {
  int count = vsnprintf(NULL, 0, fmt, ap);
  if (count <= 0) {
    return "unable to format message";
  }

  std::string result = std::string(count, NULL);
  if (vsnprintf(const_cast<char *>(result.c_str()), count + 1, fmt, ap) <
    0) {
    return "unable to format message";
  }

  return result;
}

static std::string getFormattedString(const char* fmt, ...) {
  va_list ap;
  va_start(ap, fmt);
  std::string result = getFormattedString(fmt, ap);
  va_end(ap);
  return result;
}

int main(int argc, char *argv[]) {

  std::cout << getFormattedString("a").c_str() << "\n";
  std::cout << getFormattedString("abcdefghijklmnop").c_str() << "\n";
  std::cout << getFormattedString("1________________________________________________A").c_str() << "\n";
  std::cout << getFormattedString("%d", 12345).c_str() << "\n";
  std::cout << getFormattedString("a%de", 12345).c_str() << "\n";

  return 0;
}

Windows: http://rextester.com/WHTP25141

a
abcdefghijklmnop
1________________________________________________A
12345
a12345e

Unix: http://rextester.com/GJMKYN47723

a
abcdefghijklmnop
1________________________________________________A
0
a8e

Anyone got some ideas?

The endless battle against platforms should be fixed. Tested on a VM, seems to work now.
@swift-ci please smoke test

@swift-ci please smoke test

Your sample code is missing a va_copy.  As I understand it, the va_list type is a reference type on some platforms -- on those platforms, your first call to vsnprintf actually consumes the va_list so the second call to vsnprintf will not work as you expect.  You need to va_copy the varargs list to avoid this problem.

Your sample code is missing a va_copy. As I understand it, the va_list type is a reference type on some platforms -- on those platforms, your first call to vsnprintf actually consumes the va_list so the second call to vsnprintf will not work as you expect. You need to va_copy the varargs list to avoid this problem.

That was the problem :D I updated the code about 15 mins ago :)


Update README.md

Elaborate a bit on the most common use case.

Thanks. The first added paragraph mentions that coursier uses the ivy cache though, which is not the case. A few things will land in the ivy cache when sbt starts, to get sbt-coursier in particular. Once sbt-coursier is loaded, it will handle dependencies, possibly downloading in its own cache things already downloaded by sbt/ivy.

@alexarchambault I got the impression that coursier checked in my ivy cache for the presence of a jar before downloading but I may have been wrong.. Let me check again.

@alexarchambault My first paragraph means something different- it says- Coursier "downloads" from ivy cache into coursier cache. Does it not? I get the following error if I turn the internet off-
[error]   com.timushev.sbt:sbt-updates;sbtVersion=0.13;scalaVersion=2.10:0.3.0:
[error]     download error:
[error]       Caught java.net.UnknownHostException: repo1.maven.org (repo1.maven.org)
[error]       Caught java.net.UnknownHostException: repo.scala-sbt.org (repo.scala-sbt.org)
[error]       Caught java.net.UnknownHostException: oss.sonatype.org (oss.sonatype.org)
[error]       Caught java.net.UnknownHostException: oss.sonatype.org (oss.sonatype.org)
[error]       Caught java.net.UnknownHostException: oss.sonatype.org (oss.sonatype.org)
[error]       Caught java.net.UnknownHostException: repo.typesafe.com (repo.typesafe.com)
[error]       Caught java.net.UnknownHostException: repo.typesafe.com (repo.typesafe.com)
[error]       Caught java.net.UnknownHostException: repo.typesafe.com (repo.typesafe.com)
[error]       Caught java.net.UnknownHostException: repo.typesafe.com (repo.typesafe.com)
[error]       Caught java.net.UnknownHostException: jcenter.bintray.com (jcenter.bintray.com)
[error]     not found: /home/srgom/.ivy2/local/com.timushev.sbt/sbt-updates/scala_2.10/sbt_0.13/0.3.0/ivys/ivy.xml

which seems to imply that there was a search into ~/.ivy2/local (although my cache is in ~/.ivy2/cache actually so my statement is probably not true)

Two more things :-)

can you rebase on the latest master, and first do the changes to doc/README.md, then run sbt tut for those to be reported to the README.md at the root?
I'm not too happy with the first paragraph... coursier doesn't handle the very first dependency fetchings of sbt (that fetch sbt itself and the first plugins, sbt-coursier being one of them).

Closing this for now. Might cherry-pick the second paragraph later (or re-open with just it if you'd like).


Switch RabbitMQ for something more stable

We are having a lot of stability issues with RabbitMQ. Switch to something that works better

Since we already use AMQP, it is an easy switch to LavinMQ. Tested in production and it's working fine. I'll be watching it and if it proves suitable, I'll change the dev-env docker-compose to use LavinMQ instead of RabbitMQ

Satisfied with the results, I'm swapping the devenv docker-compose to use LavinMQ.


removed ignored 'placeholder' attribute

input[type="date"] does not support the placeholder attribute (ref: http://www.w3schools.com/tags/att_input_placeholder.asp).
Also I present this as a contender for the smallest possible PR to this repo.
note: if this PR is acceptable, I expand it to include the remaining ignored placeholders in this file.

Yes, this change is acceptable! Before we can merge however, we need for you the following things:

[ ] sign the CLA
[ ] change the commit message to docs(input): remove ignored placeholder attribute
[ ] make sure it's all one commit

I think we still want to keep the placeholder, because some browsers (including Firefox) do not support type="date" and fallback to type="text". In such cases, the placeholder is very helpful imo.

@gkalpak Ah, yes you are right. I guess this can't be merged then :(

poop.
well thanks for the quick review.


nyc only reports coverage for included files

Please use the template provided below, when reporting bugs:
Expected Behavior
All files under a given folder (for example `src/`` should be included in the coverage report with a coverage rating of "0%".
Observed Behavior
Failure to import a given source file into a test file causes it to have no test coverage data generated.
Bonus Points! Code (or Repository) that Reproduces Issue
http://github.com/robertmain/develop
Forensic Information
Operating System: the operating system you observed the issue on.
Environment Information: information about your project's environment, see instructions below:

run the following script:
sh -c 'node --version; npm --version; npm ls' > output.txt

share a gist with the contents of output.txt.
https://gist.github.com/robertmain/06913a128701ee0249ac220a9352ae05

@robertmain if you run with --all this should do the trick for you. You will need to make sure that nyc performs the instrumentation step with babel-register, etc., so that it's able to understand ES2015 code in the files that it walks during the application of --all.

@bcoe  I ran it with all in the config file and it didn't work. However, when I ran it with --all as you suggested it works correctly. Might want marking as a bug? :)

I just tried with "nyc": {"all": true} in my package.json it worked for me.  How are you setting the option in config?

Command line

That also worked for me.  The links in this ticket are 404's so I can't look at your example repo but I'm not able to get --all to fail on command-line, in package.json or in .nycrc.


Wrong compiled example of Downleveling section

The downleveling section compares the original template string in the "Explicit Types" section with the compiled one at the "Erased Types" section in which the target used is es5.
And while es5 actually outputs:

here's what the comparison says

This change was already merged in #2820.


Back sprint4

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
25 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-2.02%) to 95.731%

Files with Coverage Reduction
New Missed Lines
%

smartMoney_app/views.py
1
95.65%

smartMoney_app/category_views.py
8
91.92%

smartMoney_app/expense_views.py
8
83.56%

smartMoney_app/managers.py
8
90.36%

Totals

Change from base Build<PHONE_NUMBER>:
-2.02%

Covered Lines:
1794

Relevant Lines:
1874

💛  - Coveralls


Switch to shared binary clients

Having per-topic consumers and producers would encourage bad usage patterns, i.e. separate consumers and producers for each topic, where a much cleaner and more efficient approach is a single consumer and producer per app.
For now, just expose shared binary producer and consumers and provide helpers for serde of key and value. It's not particularly pretty, but it'll work and maintains the use of the default Kafka clients.
Reviewer checklist

[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage increased (+0.04%) to 98.445% when pulling 5b04a288dd72d9cc0a29d07ee94280c463afc9c6 on shared_binary_clients into dd0de5248414a05a2e54f0b29ac6a340fe984efc on main.


Provider google present in backend.tf (terraform)

Hello, thank you for the work.
Checking the configuration of the terraform section I saw that the tag "google" is shown in several providers are not GCP.
% grep -irl "google" terraform/*
terraform/**aws**/backend.tf
terraform/**azure**/backend.tf
terraform/gcp/output.tf
terraform/gcp/main.tf
terraform/gcp/provider.tf
terraform/packet/backend.tf
terraform/remote-state/main.tf

Thanks for your interest! :)
Yep, we use GCP for creating the backend storage on all the providers. Some provider must be defined for the backend, we decided for GCP.
However I think we could make this configurable too by using templates also for the terraform files (ie. having the ability to modify them according to config before they are used by terraform). PRs are very welcome :)


Ray crash on read_csv

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Ubuntu 19.10

Modin installed from (source or binary):

Modin version:
0.7.0+3.g7528bf3

Python version:
Python 3.7.5

Exact command to reproduce:

Describe the problem

When I run the reproducer code both with huge pages and without them I get Ray crash with message:
2020-02-07 11:16:24,545 INFO resource_spec.py:216 -- Starting Ray with 95.17 GiB memory available for workers and up to 18.63 GiB for objects. You can adjust these settings with ray.init(memory=<bytes>, object_store_memory=<bytes>).
2020-02-07 11:16:24,801 WARNING services.py:1365 -- WARNING: object_store_memory is not verified when plasma_directory is set.
F0207 11:16:26.652703 51019 direct_task_transport.cc:154] Lost connection with local raylet. Error: IOError: 14: Socket closed
*** Check failure stack trace: ***
    @     0x7f5ff966f98d  google::LogMessage::Fail()
    @     0x7f5ff9670dfc  google::LogMessage::SendToLog()
    @     0x7f5ff966f669  google::LogMessage::Flush()
    @     0x7f5ff966f881  google::LogMessage::~LogMessage()
    @     0x7f5ff94440e9  ray::RayLog::~RayLog()
    @     0x7f5ff93650c9  ray::CoreWorkerDirectTaskSubmitter::RetryLeaseRequest()
    @     0x7f5ff9367863  _ZNSt17_Function_handlerIFvRKN3ray6StatusERKNS0_3rpc16WorkerLeaseReplyEEZNS0_29CoreWorkerDirectTaskSubmitter24RequestNewWorkerIfNeededERKSt4pairIiSt6vectorINS0_8ObjectIDESaISC_EEEPKNS4_7AddressEEUlS3_S7_E_E9_M_invokeERKSt9_Any_dataS3_S7_
    @     0x7f5ff939ec3f  ray::rpc::ClientCallImpl<>::OnReplyReceived()
    @     0x7f5ff93419d3  _ZN5boost4asio6detail18completion_handlerIZN3ray3rpc17ClientCallManager29PollEventsFromCompletionQueueEiEUlvE_E11do_completeEPvPNS1_19scheduler_operationERKNS_6system10error_codeEm
    @     0x7f5ff93403a5  boost::asio::detail::scheduler::run()
    @     0x7f5ff93444a3  ray::CoreWorker::RunIOService()
    @     0x7f5ff905f302  (unknown)
    @     0x7f5ffa325669  start_thread
    @     0x7f5ffa461323  clone
Aborted (core dumped)

Source code / logs

#import pandas as pd
import ray
ray.init(huge_pages=True, plasma_directory="/mnt/hugepages")
import modin.pandas as pd

dtypes = {
    'object_id': 'int32',
    'mjd': 'float32',
    'passband': 'int32',
    'flux': 'float32',
    'flux_err': 'float32',
    'detected': 'int32'
}

PATH='/localdisk/benchmark_datasets/plasticc'
GPU_MEMORY = 16
TEST_ROWS = 453653104
OVERHEAD = 1.2
SKIP_ROWS = int((1 - GPU_MEMORY/(32.0*OVERHEAD))*TEST_ROWS)

test = pd.read_csv('%s/test_set_100000.csv'%PATH,
        # skiprows=range(1, 1+SKIP_ROWS),
        dtype=dtypes)

Data file is the same as in #1067

Thanks @gshimansky for reporting this!
I will discuss these issues with the Ray team. #1058 also has a core dump, which is coming from Ray as well. Thanks again for posting this!

The problem is not reproducible on ray 0.8.3 and 0.8.4.


[Feature] | FlowForms Logo

Which kind of problem this feature would address? Please describe.
Need a logo for the project.
Describe the solution you'd like
It would be good to have a social media preview image with a size of 1280 × 640px (width x height), and/or an icon / square logo. Nothing is defined regarding how should it look, but can be related to flows and forms 😅

We got one provided by Carol Meyes from Rootstrap! 🥇
Decided with the team the best option from two completely different logos. We will see them in the readme and in the documentation once #26 is finished


[BUG] Error happening on executing MTL notebooks under example/usecase

Bug description

Run the cell for multi-task learning noteobok

Expected behavior

Environment details
The way I installed is using conda and follow here

Merlin version:
Platform:
Python version:
PyTorch version (GPU?):
Tensorflow version (GPU?):

Additional context

      4 NUM_ROWS = os.environ.get("NUM_ROWS", 100_000)
      5 NUM_ROWS = 1
----> 6 train_ds, valid_ds = generate_data("tenrec-video", int(NUM_ROWS), set_sizes=(0.8, 0.2))
      7 schema = train_ds.schema

File ~/anaconda3/envs/rapids-22.08/lib/python3.8/site-packages/merlin/datasets/synthetic.py:111, in generate_data(input, num_rows, set_sizes, min_session_length, max_session_length, device)
    109     elif not os.path.exists(input):
    110         closest_match = difflib.get_close_matches(input, KNOWN_DATASETS.keys(), n=1)
--> 111         raise ValueError(f"Unknown dataset {input}, did you mean: {closest_match[0]}?")
    113     schema = _get_schema(input)
    114 elif isinstance(input, Schema):

IndexError: list index out of range

@liyunrui can you give us a bit more info about your env? where do you run this? in a cloud instance?  are you using merlin-models main branch?
I am not able to reproduce your error. are you able to import merlin libs . can you run the following and see if you are able to do the imports properly?
import merlin.models.tf as mm
from merlin.schema.tags import Tags
from merlin.datasets.synthetic import generate_data

generally IndexError: list index out of range comes when there is no dataset in the folder.
Are you installing rapids via conda? We recommend you to install Merlin via with pip in your conda env, if you want to use conda. Note that you dont have to use conda to install cudf and dask_cudf. you can install it via this command:
pip install rmm-cu11==22.10.0 cudf-cu11==22.10.0 dask-cudf-cu11==22.10.0 --extra-index-url=https://pypi.nvidia.com/
Please check out the other ticket that you follow, there are some updates there.

Hi rnyak,
Thanks for your reply.
Yes. I'm running on AWS SageMaker instance. And i can import code you suggested

@liyunrui are you still having the issue? can you send us pip list output in a .txt file. are you able to run 01 and 02 notebooks in this folder? can you please test?

I closed this issue due to lack of activity in the last couple weeks.


Github landing page needs updating

Steps to reproduce
Go to https://github.com/retr0h/gilt
Expected result
All links are up to date
Actual behavior

Miscellany
LOL

Good catch!

Corrected!

LOL:

Why yes, I am having a lot of fun with this...  :trollface:

damnit! lol


Html.input defaultValue does not update properly when switching pages

A simple 2 pages view is provided as an example.
To reproduce the problem:

type some string to input field of page1
click on "page2" button

Expected result: Input field on page2 is suppose to be empty.
Actual result: Input field on page2 contains the value from the page1.
Elm version: 0.18.0 (installed via nix package manager)
OS: Ubuntu 16.04
browser: firefox 56.0 (64-bit)
Testfile:
import Html exposing (..)
import Html.Attributes exposing (..)
import Html.Events exposing (..)

type Page
    = Page1
    | Page2

type Msg
    = NewPage Page
    | Query1 String
    | Query2 String

type alias Model =
    { selectedPage      : Page
    , query1            : String
    , query2            : String
    }

main : Program Never Model Msg
main =
    beginnerProgram
        { model = (Model Page1 "" "")
        , view = view
        , update = update
        }

view : Model -> Html Msg
view model =
    div []
        [ fieldset []
            [ button [ onClick (NewPage Page1) ] [ text "page1" ]
            , button [ onClick (NewPage Page2) ] [ text "page2" ]
            ]
        , text "this is page: "
        , text (toString model.selectedPage)
        , viewLevel2 model
        ]

viewLevel2 : Model -> Html Msg
viewLevel2 model =
    case model.selectedPage of
        Page1 ->
            div []
                [ input
                    [ placeholder "query for page1"
                    , defaultValue model.query1
                    , onInput Query1
                    ] []
                , text "copy of the query: "
                , text model.query1
                ]
        Page2 ->
            div []
                [ input
                    [ placeholder "query for page2"
                    , defaultValue model.query2
                    , onInput Query2
                    ] []
                , text "copy of the query: "
                , text model.query2
                ]

update : Msg -> Model -> Model
update msg model =
    case msg of
        NewPage page -> {model | selectedPage = page}
        Query1 s -> {model | query1 = s}
        Query2 s -> {model | query2 = s}

Hi, thanks for filing an issue!
The virtual-dom doesn't really have a concept of pages, only of DOM nodes. The structure of your view doesn't change, so as far as the virtual-dom is concerned, it should try to be as efficient as possible and reuse DOM nodes where possible. As mentioned, defaultValue is set when an input is first rendered, and cannot be updated by changing its content.
In cases like this, you can use Html.Keyed to ensure that virtual-dom library can tell your pages/inputs/.. apart.
Hope this helps

Thank you for your quick response. It helps a lot. If I wrap a call to viewLevel2 inside Html.Keyed.node, then it works as expected. But I am not sure if I have done it correctly.

Would you please suggest the correct way to work arount this issue. What do I suppose to pass as the first String argument (of the "node" function) and what String should go inside the list?
For example, I have changed line , viewLevel2 model with line , Html.Keyed.node (sp model) [] [((sp model), viewLevel2 model)], where sp model = toString (model.selectedPage).
Is this correct (both strings being the same)?

Is this still a bug or not?
I belive that different defaultValue shall yield different DOM node, such that it is not reused. From the user perspective, the current behaviour is definetly a surprise.

The behaviour you describe is much closer to how value works - it updates the value of the input whenever the property changes. Currently, this can cause the cursor to jump because rendering happens asynchronously. In 0.19, this should work seamlessly.
The behavior of the snippet in the first post seems correct.
If you're using defaultValue to work around the "jumping cursor", the least invasive solution I could come up with is this: https://ellie-app.com/ggpjpVBCka1/0

This worked for me too. I had applied defaultValue for jumping cursor issue. Just adding my 2 cents for devs who run into this.
My data model is a bit different in that it is a value from a tree, not as simple as model.resource1 and model.resource2. In my case I had no issues when the devaultValue was set with a direct value of the model, but it was when the input value was computed from the model value.
# static property, no issue
Html.input name "resource[title]" defaultValue resource.title

# computed property, this is an issue
Html.input name "resource[tags]" defaultValue (String.join ", " resource.tags)

With defaultValue not being a thing with Elm 0.19 anymore, I guess this can be closed.


Node examples

Closes #5. CC: @ljharb, @bmeck.

Thanks everyone for their help. I plan to merge in about one hour. Feel free to open new issues / pull requests if you spot a problem after that.


Error when decoding array of uint256

I'm getting a MatchError raised by ex_abi when I use this library to call a contract's method that returns an array of uint256. Initially I thought it was a bug in ex_abi but based on the evidence provided in https://github.com/poanetwork/ex_abi/issues/98 it seems that there might something wrong on how this library is handling the response from the RPC call and passing that to ex_abi for decoding.
The issue I reference in ex_abi has all the required information to reproduce the bug

Relevant issue reported here: https://github.com/Metalink-App/web3x/issues/7
Since web3x is forked form exw3 they appear to be identical issues.


Datatables Search Totals

Summary of problem or feature request
How go I get Search totals from the datatables search query assuming each user has a number of cars for example. I know how to get the total cars, but how to I get the total of a filtered result
Code snippet of problem
$users = User::where('created_date',Carbon::now()->subYears(1));

        return Datatables::of($users)
            ->addColumn('total_cars', $user->sum('num_cars'))
           // ->addColumn('search_total_cars', ??)
            ->make(true);

@knox2 added column is not searchable since it's not part of the query. I suggest you try adding a sub-query to fetch the total and use filterColumn and do the necessary search sql. Another work around is by creating a view with the total and use it via query builder.

@yajra can i get access to the filtered query builder from the code ie something like this:
$users = User::where('created_date',Carbon::now()->subYears(1));

return Datatables::of($users)
            ->addColumn('total_cars', $user->sum('num_cars'))
            ->with('search_total_cars', $this->query()->sum('num_cars'))
            ->make(true);

Hi @yajra the column search_total_cars is just a number at the footer that sums the total of the column total_cars during search, how can i get the value

Sorry for late reply, you can get it using javascript. Regards!

I am using Non service datatables(Am just using single function to get ajax), How can i  sum,
this function didnt worked for me,
Also i dont have query() function in my class.
->with('totalqty',$this->query()->sum('total_quantity'))
Any idea?


Support HCI_SOCK_USER/RAW

Summary
This is a work in progress to support RAW HCI commands over BTPROTO_HCI socket. As supporting this socket type means that NuttX's host stack is bypassed (packets are sent via socket back to user instead of NuttX's own stack), this PR also adds the ability to disable NuttX's stack entirely. In this case it is expected that a host stack be provided in userspace.
With this support I have managed to get nimBLE stack working (the demo starts a GATT server which I managed to test from nRF Connect Android app from my smartphone).
Work so far:

I've extended sendto() implementation for Bluetooth, to distinguish BTPROTO_L2CAP and BTPROTO_HCI
I've extended the frame metadata struct to include a "protocol" field which allows the radio driver to now which type of
frame it has received
I've extended btnet_req_data to support each of these cases so that the frame is forwarded to either L2CAP part of stack or directly to bluetooth driver as HCI buffer
I've added a callback to bt netdev driver which is used in bt_hcicore to forward HCI packets while they are being dequeued back to the network driver
I've extended bluetooth_connection_s struct and handling to include the notion of protocol, as it is required to consider a non-connected but bound socket when looking where to send a packet received from the controller

I have tested this with NuttX's host layer disabled but I would need to retest with NuttX's host layer enabled to validate that is still working. I would also need to condition the support of HCI RAW channel to when the host layer is disabled. My thinking is that  NuttX would either support: host-layer disabled + HCI RAW channel OR host-layer enabled + BTPROTO_L2CAP + BTPROTO_HCI w/MGMT channel. I think other combinations would not make sense or would be too difficult to support, but I'm not sure.
There's a few hacks which I left for proper solutions which required more work:

The sockaddr_hci indicates which BT device should receive the packet. I understand this is an index over all BT devices (not ALL network devices) so it requires this search which is not easy. I simply plugged a search for the n-th driver, which works for my test case on sim.
Error handling in various places

In https://github.com/apache/mynewt-nimble/compare/master...v01d:nuttx you can see the (also WIP) changes to nimBLE to add support for NuttX. It is mostly based on Linux port. This port originally used sendmsg() which in NuttX is not fully supported so I changed it to sendto() which is mostly the same. It uses read() for receving, which is strange, but works OK. There are a few fixes I needed to introduce to nimBLE which I hope I can get ported upstream to have proper support.
To be done:

Polish this
Validate approach to the case of supporting BTPROTO_L2CAP + MGMT
More testing

I also think that we need to decide when/how we're going to migrate to a pure socket based interface and drop support for current ioctl() based interface. In that case I think that supporting bluetooth and supporting AF_BLUETOOTH sockets would be just one option instead of two separate ones. This will also break support for btsak until something else which uses the socket interface is written.
Impact
Adds new support, for now it shouldn't break anything, but it requires testing
Testing
I'm testing this on sim with hci socket support and nimBLE. nimBLE is being built as an application (the stack + demo "nimble" app). Eventually it will be split into a library and optional demo apps. The test is as follows:

boot sim nuttx (with proper permission for HCI access)
ifup bnep0
nimble

While starting, nimble app start interacting with controller by sending an HCI commands and registers a GATT server. I've connected with my phone and works with no issues.

Ignore the changes to Config.mk, it is unrelated

@btashton I worked a bit more on the RX part and though the best way would be to add a callback to bt_netdev.c which bt_hcicore.c can invoke from within the priority_rx_work function, to pass an HCI packet to the driver. From there, it follows a similar path to that of received L2CAP packets, calling bluetooth_input to send the packet to the appropriate socket.
After some other changes I now need one final thing to complete this: I need to prepend the H4 header (I believe that is the name, the one byte header indicating CMD, EVT, etc.) to the HCI data received as bt_buf_s, to obtain a iob_s containing this header + packet. Do you know how this is supposed to be done? This is what is done for L2CAP in btnet_l2cap_receive case before calling bluetooth_input:
  frame      = buf->frame;
  buf->frame = NULL;

  /* Ignore the frame if the network is not up */

  priv = (FAR struct btnet_driver_s *)context;
  if (!priv->bd_bifup)
    {
      wlwarn("WARNING: Dropped... Network is down\n");
      goto drop;
    }

  /* Make sure that the size/offset data matches the buffer structure data.
   * REVISIT:  Wouldn't it be better to just have one copy rather than having
   * to synchronize?
   */

  frame->io_len    = buf->len;
  frame->io_pktlen = buf->len;
  frame->io_offset = (unsigned int)
    ((uintptr_t)buf->data - (uintptr_t)frame->io_data);

Ok, I got it. Wasn't too hard after all.
Now nimBLE appears to be receiving the packet. I need to continue debugging to see if there aren't other things missing.

Hey! It's working!
I just paired my smartphone =D
I had to fix a race condition in nimble but other than that it appears to be working. I will push what I have to both repos and see about getting it to a mergeable state.

@btashton I've updated the PR description to reflect the recent changes (which I added as separate commits to help reviewing)
I'm interested in your perspective for the case of supporting BTPROTO_L2CAP+MGMT channel. I tried to be aware of this case but I may have missed it somewhere.

@v01d sorry for the little delay, I'll take a look at it tonight.  My biggest concern is that with this we are moving the whole stack into userspace which means you cannnot use the l2cap, rfcomm, etc... with this.   This is why I thought we were talking about using nimble to provide the layer on top of l2cap and then make the calls the the management socket. I get that it is a lot of changes, but that is the only way I could see to get this in in an official way.

@v01d sorry for the little delay, I'll take a look at it tonight. My biggest concern is that with this we are moving the whole stack into userspace which means you cannnot use the l2cap, rfcomm, etc... with this. This is why I thought we were talking about using nimble to provide the layer on top of l2cap and then make the calls the the management socket. I get that it is a lot of changes, but that is the only way I could see to get this in in an official way.

NuttX's stack remains in place and can be activated or not via Kconfig (with the option I added). If you disable it, you can provide your own stack, which in this case would be nimBLE as an application/library interacting via RAW sockets. If you leave it enabled, it should work as before and could be modified to use L2CAP socket + mgmt socket as you intended. So, these approaches are not incompatible.
This could be a first step. A second step could be to try to talk with nimBLE devs if they would be open to add support for allowing their L2CAP stack be disabled and use it via L2CAP sockets instead. However, I would only do that if our intention were to replace NuttX stack with nimBLE, but I think that requires further community discussion. A good first step would be to support both stacks and then decide if we want to switch or continue with current stack as the official one.
My aim is simply to provide nimBLE as an external option. I don't think this needs to conflict with the work to support L2CAP + mgmt. We should simply try to iterate this to support both configurations.
Finally, regarding USER vs RAW for nimBLE. My expectation is as follows: when using nimBLE, NuttX's stack is disabled. However, each app would access the stack independently so using RAW would allow this. Using USER means that we need something like a central access point to the stack, via a daemon for example. I'd avoid that approach if possible.

@v01d sorry for the little delay, I'll take a look at it tonight. My biggest concern is that with this we are moving the whole stack into userspace which means you cannnot use the l2cap, rfcomm, etc... with this. This is why I thought we were talking about using nimble to provide the layer on top of l2cap and then make the calls the the management socket. I get that it is a lot of changes, but that is the only way I could see to get this in in an official way.

NuttX's stack remains in place and can be activated or not via Kconfig (with the option I added). If you disable it, you can provide your own stack, which in this case would be nimBLE as an application/library interacting via RAW sockets. If you leave it enabled, it should work as before and could be modified to use L2CAP socket + mgmt socket as you intended. So, these approaches are not incompatible.
This could be a first step. A second step could be to try to talk with nimBLE devs if they would be open to add support for allowing their L2CAP stack be disabled and use it via L2CAP sockets instead. However, I would only do that if our intention were to replace NuttX stack with nimBLE, but I think that requires further community discussion. A good first step would be to support both stacks and then decide if we want to switch or continue with current stack as the official one.
My aim is simply to provide nimBLE as an external option. I don't think this needs to conflict with the work to support L2CAP + mgmt. We should simply try to iterate this to support both configurations.

I think we are mostly in agreement on this part.

Finally, regarding USER vs RAW for nimBLE. My expectation is as follows: when using nimBLE, NuttX's stack is disabled. However, each app would access the stack independently so using RAW would allow this. Using USER means that we need something like a central access point to the stack, via a daemon for example. I'd avoid that approach if possible.

How do you see that working. What socket inteface/how would these apps talk? I don't see how RAW vs USER has anything to do with this.  You cannot have two applications sending HCI commands or you will have problems keeping the state in sync. This is why nimBLE uses USER so it has exclusive rights to manage HCI on the wire.

How do you see that working. What socket inteface/how would these apps talk? I don't see how RAW vs USER has anything to do with this. You cannot have two applications sending HCI commands or you will have problems keeping the state in sync. This is why nimBLE uses USER so it has exclusive rights to manage HCI on the wire.

I was thinking mostly about introspection tools, mostly. But, yet, two apps sending HCI commands that alter state would make no sense. Maybe it is better to guarantee exclusive access via USER for this case. In that scenario, using nimBLE would imply to a single app should have access to the stack. I don't think that sounds bad for a first approach.
Let me know later when you look at the changes closer. I think the goal would be to test both configuration: nuttx host stack + L2CAP + mgmt versus nimBLE stack + USER channel. With that I think we could make a first merge to NuttX, which shouldn't break anything. After that and some more testing we could open the discussion on which stack looks better to embrace.

hi @btashton , did you have time to take a closer look to this? I would really like to get the RAW HCI socket merged in NuttX so that I can then make a PR to nimBLE repo adding support for NuttX. I have tested this combination in sim and partially on nRF52 (with my WIP link-layer) and it works really well.
Do you think that, after a bit of more iteration to this PR, we could merge this to mainline? L2CAP_PROTO + mgmt can be added in a second step. I can make the switch to the USER channel so that only exclusive access is supported when the whole stack is in userspace (as with nimBLE). Did you had any other changes in mind?

I will look at it this weekend. Sorry it was my first week on a new job so I have not had much time and I want to give a detailed review that is deserves.
I just want to make sure we are using a solid API boundary and not hacking this in.
Longer term I think it's not a good idea to keep this only in user space since it breaks all the other expected functionality via sockets, so I want to be sure we are not crippling that. That still means we can fully support this as you have done and does not block this.
We should also consider if we want to put this in the 10.0.0 release or wait another cycle (merge right after the release). I'm inclined to do that just so we have more time to tweak the API and do testing.

I will look at it this weekend. Sorry it was my first week on a new job so I have not had much time and I want to give a detailed review that is deserves.

Sure! Just wanted to touch base.

I just want to make sure we are using a solid API boundary and not hacking this in.
Longer term I think it's not a good idea to keep this only in user space since it breaks all the other expected functionality via sockets, so I want to be sure we are not crippling that. That still means we can fully support this as you have done and does not block this.

I don't really see an incompatibility with both approaches, I added the option to disable NuttX host layer for this reason. RAW access would only be provided in this case. In the opposite case, L2CAP + mgmt would be supported. If we can support both options without conflict I think it is a good option to have.
But I agree that there should be a discussion soon about what we want to do with NuttX host stack: should we continue to maintain the current one or should we use nimBLE (or even something else) as our official one?

We should also consider if we want to put this in the 10.0.0 release or wait another cycle (merge right after the release branch). I'm inclined to do that just so we have more time to tweak the API and do testing.

Yeah, there's no rush, it is better to have 10.0 use current approach.

@v01d I apologise for the delay in reviewing. I have set some time aside tonight.

No problem! Thank you!

Hi @btashton, I'm thinking... would you rather I open this PR to nuttx mainline? This way we can get other reviewers in and your are not overburdened with this (I understand you are busy with next release and new job). If so, the PR would include both your initial changes and mine. There's some iteration I still would have to do to switch to USER channel instead of RAW though (so it would be a draft PR in the meantime), but I think it is a good first self-contained change (before addressing the L2CAP+MGMT you intended to do) .


Update Composer dependencies (2020-06-01-00-08)

Visual regression test passed!
View the visual regression test report


remove the bpfd-operator

Remove the stale and out of date bpfd-operator. It will be replaced in a followup PR adding the new bpfman-operator which has yet to be officially released.
See https://github.com/bpfman/bpfman/issues/887 for the follow up to this!
Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

/merge possible


html in strings breaks usability

First of all: I like this library. It is very clean and simple code.
But thats a major bug and preventing me from using it. A string can basically include html and this must not affect the editor.
Example code:
<json-editor id="editor"></json-editor>
<script>
  document.addEventListener('DOMContentLoaded', () => {
    document.getElementById('editor').value = '"John: Hello World!<br>Jane: Hello John!"';
  });
</script>

This will render an invalid json that then does not get updated until fixed:
"John: Hello World!
Jane: Hello John!"

Also: opening a html tag without closing it will cause a strange redraw and data after the "<" will get lost.
To overcome all of these issues it will be enough to escape the string. (That might also be necessary in keys):
format_string(input) {
  input = input.replace(/&/g, "&")
                    .replace(/</g, "<")
                    .replace(/>/g, ">")
                    .replace(/"/g, """)
                    .replace(/'/g, "'");
  return `<span part="string"><span part="string_quotes">\"</span>${input}<span part="string_quotes">\"</span></span>`;
}

Thanks! Very good catch, let me check your PR as we may need, as you said, sanitise the keys as well. I'll prepare a fixed version before the end of the day.

This should be fixed in 0.3.0. Thanks!


PasswordBoxes-Must-Have-Min-Length false positive on this regex

The test doesn't detect this regex as having a minLength
              {
                "name": "adminPassword",
                "type": "Microsoft.Common.PasswordBox",
                "label": {
                  "password": "password",
                  "confirmPassword": "Confirm password"
                },
                "constraints": {
                  "required": true,
                  "regex": "^.{12,}",
                  "validationMessage": "Password must be at least 12 characters long"
                },
                "options": {
                  "hideConfirmation": false
                }
              }

@edburns - your PR will fix this case?

@edburns - your PR will fix this case?

@bmoore-msft It will fix the case where the input regex to examine uses a positive lookahead.

A positive lookahead, written as ‹(?=⋯)›, can be used at the beginning of the pattern to ensure that the string is within the target length range. The remainder of the regex can then validate the desired pattern without worrying about text length.

I don't know what the poster means by "this regex" though.

@bmoore-msft It will fix the case where the input regex to examine uses a positive lookahead.

A positive lookahead, written as ‹(?=⋯)›, can be used at the beginning of the pattern to ensure that the string is within the target length range. The remainder of the regex can then validate the desired pattern without worrying about text length.

I don't know what the poster means by "this regex" though.

Ah, if you mean  "regex": "^.{12,}", then, no. My patch does not address that particular case.  Personally, the way to check for "length" using regex is very open ended and application dependent. I view this test as a "best effort" test case. I assumed that was why the failure was classified as a "warning". @bmoore-msft .

Ah, if you mean  "regex": "^.{12,}", then, no. My patch does not address that particular case.  Personally, the way to check for "length" using regex is very open ended and application dependent. I view this test as a "best effort" test case. I assumed that was why the failure was classified as a "warning". @bmoore-msft .

yes, using a regex to validate a regex is an interesting exercise to say the least...

yes, using a regex to validate a regex is an interesting exercise to say the least...

@bmoore-msft I do enjoy the programming equivalent of pointing your webcam at your screen though.

@bmoore-msft I do enjoy the programming equivalent of pointing your webcam at your screen though.


Sometimes tooltip is moving and does not fit at screen

It is very difficult to determine what causes this behavior. In most situations it works, but testers report that every now and then tooltips change position and go off-screen.

@bensonarafat Hi, I am facing same issue is there any update on this?

can you show the code?

can you show the code?

@hyunseokSon
Are you working on this?

Hi, I am facing same issue is there any update on this?