Module / Invalid paths

Good call @H-i-red. That fixed an issue for me.

Really strange. This is something I definitely fixed/changed in the last release, I'm not sure how it got reverted. I even generated a module with it, and go the correct code.
Anyway, it's been fixed in 1.4.2:
https://github.com/nystudio107/generator-craftplugin/releases/tag/1.4.2
This is also live up on https://pluginfactory.io/


Started GET "/home" for ::1 at 2020-07-19 20:25:41 +0100 Processing by RailsAdmin::MainController#index as HTML   Parameters: {"model_name"=>"home"} Completed 401 Unauthorized in 1ms (ActiveRecord: 0.0ms)    LoadError (cannot load such file -- /home/mario_afonso/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/routes_proxy.rb):

Pre-check

Do not use the issues tracker for help or support, try Stack Overflow.
For bugs, do a quick search and make sure the bug has not yet been reported
If you found a security bug, do not report it through GitHub. Please send an e-mail to<EMAIL_ADDRESS>instead.
Finally, be nice and have fun!

Environment

Ruby [version]
Rails [version]
Devise [version]

Current behavior
Include code samples, errors, steps to reproduce the error and stack traces if appropriate.
Will be even more helpful if you provide a sample application or a test case that reproduces the error.
Expected behavior

You need to give us more information on how to reproduce this issue, otherwise, there is nothing we can do.
Please open up a new issue and make sure to fill in all the information requested in the template shown inside the text box.
Thank you!


Uncaught (in promise) RangeError: Invalid time value

I got some builds which are using group: for parallel execution, there it can happen that some procs don't have a start date defined which will result in a javascript error as stated in the title. With this error it's not possible to see the build details anymore.

After that I prepared a query to look for the procs values:
sqlite> select proc_id, proc_name, proc_state, proc_started, proc_stopped, build_id, repo_full_name from procs left join builds on (proc_build_id = build_id) left join repos on (build_repo_id = repo_id) where repo_full_name = 'demos/launcher' and build_number = 5;
568||failure|1507131916|1507132244|129|demos/launcher
569|clone|success|1507131916|1507131922|129|demos/launcher
570|restore|success|1507131922|1507131928|129|demos/launcher
571|frontend-prepare|success|1507131928|1507131986|129|demos/launcher
572|frontend-lint|success|1507131986|1507132000|129|demos/launcher
573|frontend-test|success|1507131986|1507131998|129|demos/launcher
574|frontend-build|success|1507131986|1507132014|129|demos/launcher
575|backend-prepare|success|1507132015|1507132151|129|demos/launcher
576|backend-vet|success|0|1507132186|129|demos/launcher
577|backend-varcheck|success|1507132151|1507132187|129|demos/launcher
578|backend-structcheck|success|1507132151|1507132184|129|demos/launcher
579|backend-unconvert|success|1507132151|1507132172|129|demos/launcher
580|backend-ineffassign|success|1507132151|1507132159|129|demos/launcher
581|backend-lint|success|1507132151|1507132174|129|demos/launcher
582|backend-test|success|1507132151|1507132201|129|demos/launcher
583|backend-build|success|1507132151|1507132186|129|demos/launcher
584|docker|failure|1507132201|1507132233|129|demos/launcher
585|rebuild|skipped|0|0|129|demos/launcher
586|flush|skipped|0|0|129|demos/launcher
587|slack|failure|1507132233|1507132241|129|demos/launcher

After setting the proc_started values for ids 576 to a real date the UI started to work as expected agin.

I think a patch to rpc.go will prevent this from happening:
+if proc.Started == 0 && proc.Finished != 0 {
+  proc.Started = build.Started
+}
if err := s.store.ProcUpdate(proc); err != nil {
  log.Printf("error: rpc.update: cannot update proc: %s", err)
}


Bump framework version to v6.0.89

$subject

PR builder [7.x.x] started
Link: https://github.com/wso2/product-is/actions/runs/5500941600

PR builder [7.x.x] completed
Link: https://github.com/wso2/product-is/actions/runs/5500941600
Status: success


Is it possible to deploy to Vercel? Zeabur is going to charge a fee.

Is it possible to deploy to Vercel? Zeabur is going to charge a fee.

Is it possible to deploy to Vercel? Zeabur is going to charge a fee.

It seems that is not possible.

You can try railway, which support docker.

Just made a template, you can try it

刚刚做了一个模板，你可以试试

I am having some issues and need your help

Hello vsd269,
Thank you for trying out the template! I'm here to help you with any issues you're having. To assist me better, please provide the following information:
Specific errors or problems you're encountering: Please include any error messages or unexpected behavior.
Steps to reproduce the issues: Describe the actions you take that lead to the problem.
Relevant code snippets or screenshots (if applicable): This will help me visualize the problem.
Once I have this information, I'll be able to troubleshoot effectively.

你好vsd269，
感谢您尝试该模板！我来这里是为了帮助您解决遇到的任何问题。为了更好地帮助我，请提供以下信息：
您遇到的具体错误或问题：请包含任何错误消息或意外行为。 重现问题的步骤：描述您采取的导致问题的操作。 相关代码片段或屏幕截图（如果适用）：这将帮助我可视化问题。 一旦掌握了这些信息，我就能有效地排除故障。

https://github.com/H-T-H/Gemini-Telegram-Bot/assets/142389217/0e3d7b36-d8a2-4932-97e8-e6ea9492aa37

I would appreciate it if you could help me figure out what the problem is. Thank you for your time.


[BEAM-3137] Improved validation of DynamicDestinations results in BigQueryIO.write

https://issues.apache.org/jira/browse/BEAM-3137
R: @reuvenlax

Fixed checkstyle, PTAL.

Reuven is traveling and busy, so
R: @chamikaramj

All done, thanks!


Cherry-pick vendored plumbing with cmd/combine for Release v0.28.3

Changes
Original commit message: This uses the cmd/combine tool in the plumbing repo to build a combined
base image from distroless and Windows, which cmd/entrypoint will build
on.
Cherry-picking this into 0.28.x branch because the release pipeline for
pipelines in the dogfooding cluster depend on the cmd/combine tool being
available in the vendor directory of the commit being released.
The release of plumbing that included cmd/combine was only added to
plumbing after 0.28 was cut, so it doesn't currently appear in the
0.28.x release branch vendor directory. ... phew hopefully that makes
sense.
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Release notes block below has been filled in or deleted (only if no user facing changes)

Release Notes
NONE

Looks like this would require the following codegen change:
Diffing /home/prow/go/src/github.com/tektoncd/pipeline against freshly generated codegen
diff -Naupr /home/prow/go/src/github.com/tektoncd/pipeline/vendor/k8s.io/apimachinery/pkg/apis/meta/v1/types.go /home/prow/go/src/github.com/tektoncd/pipeline/tmpdiffroot.ZLBOVO/vendor/k8s.io/apimachinery/pkg/apis/meta/v1/types.go
--- /home/prow/go/src/github.com/tektoncd/pipeline/vendor/k8s.io/apimachinery/pkg/apis/meta/v1/types.go	2022-01-28 17:15:41.046751650 +0000
+++ /home/prow/go/src/github.com/tektoncd/pipeline/tmpdiffroot.ZLBOVO/vendor/k8s.io/apimachinery/pkg/apis/meta/v1/types.go	2022-01-28 17:10:38.832278939 +0000
@@ -1180,15 +1180,6 @@ type ManagedFieldsEntry struct {
 	// FieldsV1 holds the first JSON version format as described in the "FieldsV1" type.
 	// +optional
 	FieldsV1 *FieldsV1 `json:"fieldsV1,omitempty" protobuf:"bytes,7,opt,name=fieldsV1"`
-
-	// Subresource is the name of the subresource used to update that object, or
-	// empty string if the object was updated through the main resource. The
-	// value of this field is used to distinguish between managers, even if they
-	// share the same name. For example, a status update will be distinct from a
-	// regular update using the same manager name.
-	// Note that the APIVersion field is not related to the Subresource field and
-	// it always corresponds to the version of the main resource.
-	Subresource string `json:"subresource,omitempty" protobuf:"bytes,8,opt,name=subresource"`
 }

I don't think this is going to work.Will try deploying from the 0.28 version of the release infra in a separate namespace on dogfooding.


Model files Frozennode Administrator

Is there someone who got the model-files to administer the Confide and Entrust package in Frozennode Administrator? I get problems with the relationships.

I subscribe to the issue!


Add Archive  button for notifications

Checklist

[X] I have used the search function to see if someone else has already submitted the same feature request.
[X] I will describe the problem with as much detail as possible.
[X] This issue only contains a request for one single feature, not multiple (related) features.

App version
6.400
Problem you are trying to solve
Notifications only allow for mark as read, delete and replying to emails
Suggested solution
I would love it if I had the option to change the delete email button in notifications to archive as this is how I've set up my gmail app and allows me to keep a record of all the emails I may have deleted.
Screenshots / Drawings / Technical details
No response

This will be possible once #3530 is implemented.


ABI - Create contacts view

Concat: People + Organizations
Create messaging options for SQL

@jravenel,
https://docs.google.com/spreadsheets/d/1q5ovCWPlLcQJywLZLbRSQCULfG-Mf2Z-squpmDC__9w/edit#gid=800734934


change of navbar according to theme

as in dark mode nav is not going with the  theme i can make it better for u please assign me this i will make itbetter

@kashishchadha Thanks for creating the issue in SkillWise!!! The issue has been assigned to you.
Before you start working on your PR, please make sure to:

⭐ Star the repository if you haven't already.
Pull the latest changes to avoid any merge conflicts.
Attach before & after screenshots in your PR for clarity.
Include the issue number in your PR description for better tracking.

I'm excited to see your contribution as part of Hacktoberfest 2024! 🎉
Don't forget to follow me on GitHub for more updates.
Happy open-source contributing! 🚀

@PriyaGhosal please assign it to me .


Add support to restrict pull requests to defined paths

This adds the ability to define a list of regions to include
or exclude from the pull request builder trigger.
This should solve issue #221

If you don't mind, would you please pull the configuration out of the trigger and make it an extension instead?

Sure I'll look into doing that

Thank you for this pull request! Please check this document for how the Jenkins project handles pull requests.

this is exactly what I need :)

This is super amazing. We've recently rolled this out for our cross-platform project that supports Android, iOS and other platforms and it has resulted in a huge improvement to our build queue. PRs that don't touch Android code now no longer trigger Android builds and vice versa for iOS.
Is there something we can help with to get this merged & released?

Yeah would like to know if there is something I can do to help get this merged. Would love to get this on our jenkins hosts.

how does this work with required checks on github? if your PR doesn't trigger because it only changed certain file types, does it just never pass the checks?

This would help us a lot in our setup. I would love to see this merged.

It looks like this checks all the files changed in a PR against a regular expression(s) and determines if the job should build based on a match of the regex pass or fail. It would be pretty cool if this could get merged, is anyone familiar enough with this plugin to support this functionality as an extension?

Where are we at with this PR? Does it need to be updated and resubmitted so we can get it merged?

latest needs to be merged in, and the code changes need to be implemented as an extension.

Hi I'm lending a hand on this repo. As @jrazgunas pointed out, the next things for this are re-implementing the change as an extension, and resolving the merge conflicts.

+1 for this. Let me know if I can help in any way.

@dulvac It will be a little while (couple weeks?) before I've ramped up & cleared up enough things to work on this one myself, so if you are particularly eager, you should just look at the other implementations in the extensions directory if we don't hear from @tlusk

We are no longer using Jenkins for our CI so I won't be re-implementing this as an extension, but I rebased it against the latest and fixed the conflicts.

+1 @tlusk This works perfectly in our environment.  Love to see this merged into master.

Can you show example usage of includeRegions in job dsl?
I have:

built hpi locally
uploaded it using PluginManager Upload plugin site.
restarted jenkins
verified that I have correct plugin version installed (1.33.2-SNAPSHOT (private-59ce2292-sbochniak))
Added includedRegions into my job dsl

  triggers {
            githubPullRequest {
                // ...
                includedRegions('my-project/.*')
              //...

I get below error:
ERROR: (script, line 39) No signature of method: javaposse.jobdsl.dsl.helpers.triggers.TriggerContext.includedRegions() is applicable for argument types: (java.lang.String) values: [my-project/.*]

Did I do anything wrong?

can we get this merged please?

Seriously, this is my co-worker, we are still using his fork on one Jenkins system.  This is super useful functionality.

Hi - This is still on my queue but I'm continuing to play catch up on open issues. If anyone wants to help push this along, the next thing I'd do on this is add tests in order to prevent regressions.

@botchniaque were you able to get your issue resolved?

Is this ever going to be merged or shall I just start using the forked version?

Sorry guys; the cycles I've had, I've spent on key bug fixes and Jenkins 2 stuff. Hopefully I'm over that hump now. This is still on the list.
However, there are no explicit tests on this changeset, and that's making me hesitate in particular. I recognize the value in this feature but don't want to merge it without some tests that the regions would be respected (or not, depending on one's configuration). There are assertions on existing tests but I wanted something more directly testing the feature & settings. That would prevent regressions later on and reduce any manual testing needs.

@benpatterson I added some unit tests to check if the trigger regions are matching correctly for you

Hi @benpatterson, could you please review the above added tests? If not, do you have an idea when this can be reviewed and merged? I really need this feature but would rather not use the forked version.

Hi folks. I will review in the coming week. Thanks for checking in...

Any news on this one? Can I somehow help to get this merged?

Awesome PR! Thanks very much. Do mind resolving the merge conflicts?

Just wanted to let you know that we are running this in production and it works great, thanks!

Alright. Let's do this. The various rebases and added tests are very much appreciated. To me the code looks fine overall. Now that we have the tests nothing is sticking out to me. I realize we didn't get this in as an extension but we can defer that.

Released in v 1.38.0. It'll take ~24 hours to appear on the Jenkins infrastructure for pulling onto your systems.


Repository cleanup

Cleaned the repository from unnecessary code in the management_webpage folder. Also updated README.md and fixed the docker-compose in the main directory.
To load the dummy data, the script in the management_webpage/development_endpoint folder has now been changed. It now uses the main docker-compose (root of repository) as well.

I'm not sure if I was doing something wrong but running docker-compose up -d at root created an error for the epnd_fairification_webui_1 container, specifically with the port.
"Error for webui: Cannot start service webui: Ports are not available, already in use."
I was able to resolve the issue by commenting out port and address in run.sh under management_webpage, and in the docker-compose.yml file in the root of the repo. Unsure if I did something wrong.

I'm not sure if I was doing something wrong but running docker-compose up -d at root created an error for the epnd_fairification_webui_1 container, specifically with the port. "Error for webui: Cannot start service webui: Ports are not available, already in use."
I was able to resolve the issue by commenting out port and address in run.sh under management_webpage, and in the docker-compose.yml file in the root of the repo. Unsure if I did something wrong.

Could it be you had a service running on port 5000? I'm not sure if the issue is for port 5000 in the container, or on the host?

Yeah, sorry, my bad. Turns out that port by default is allocated to Control Center on mac (and can disable by unchecking Airplay receiver in system preferences). This is also weird considering when I made the changes I mentioned in my previous comment, the port would be accessible and everything would work.

Yeah, sorry, my bad. Turns out that port by default is allocated to Control Center on mac (and can disable by unchecking Airplay receiver in system preferences). This is also weird considering when I made the changes I mentioned in my previous comment, the port would be accessible and everything would work.

Sounds very familiar, also spend several hours fixing that one when upgrading to macOS Monterey.....


coordinate conversion 3D to 2D

Excuse me ,I have some problem in  coordinate conversion.Whether pred_bodys_2d or new_pred_bodys_3d in test.py can not recover the pixel coordinates matching to the origin images.Thanks a lot!(By the way ,your code for 3D HPE works perfect.)

The saved results correspond to the resolution of 512x832 (the input size of the network), thus it should be properly padded to match the original images. You can refer to the code here for the new pred_2d.

consider it has been resolved.


issue raise_top

https://github.com/zagortenay333/timepp__gnome/issues/133

Closing this since I added the fix myself.


Autoplay Progress does not work on Mac FireFox

Check that this is really a bug

[X] I confirm

Reproduction link
https://swiperjs.com/demos#autoplay-progress
Bug description
Using the most recent version of FF (123.0) on Mac 14.3.1, the autoplay progress dot is filled and does not draw the circle.
Expected Behavior
No response
Actual Behavior
No response
Swiper version
11.0.7
Platform/Target and Browser Versions
FF (123.0) on Mac 14.3.1
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

I believe I've figured out the issue.
The css for the element is currently:
.autoplay-progress svg {
stroke-dashoffset: calc(125.6 * (1 - var(--progress)));
}

The fix, add px after 125.6:
.autoplay-progress svg {
stroke-dashoffset: calc(125.6px * (1 - var(--progress)));
}

This was tested on Mac Safari, Chrome and FF - All Latest Versions.

t0ggles-create swiper


Missing data from VGG-SS

Hi, I am trying to download all videos from the test portion of VGG-SS, however many samples are missing. Do you have all of the videos? And if so, how can I get access to them. Thanks.

Hi  , I would like to work on the VGG-SS dataset. I appreciate it if you could share the datasets through email at(1115443867@qq.com). Have a great day !

Hi, I am trying to download all videos from the test portion of VGG-SS, however many samples are missing. Do you have all of the videos? And if so, how can I get access to them. Thanks.

Hello, I would like to work on the VGG-SS dataset. In case you already have access to the data, I appreciate it if you could share the videos with me.

Hi , I would like to work on the VGG-SS dataset. I appreciate it if you could share the datasets through email at(1115443867@qq.com). Have a great day !

Hii i am also looking for VGG-SS 10k and 144k dataset could you please share it with me throught email at<EMAIL_ADDRESS>in case you have its access?


Add support for "\t"

Sometimes you want indentations in your strings without the indentation from the code :D

Please create an MCVE on RunKit so I can see exactly what you want to accomplish.
https://npm.runkit.com/outdent

@glemiere I'm going to close this because it's already supported.  If this does not cover your use-case, please comment and we can re-open the issue.
Example of indented string, with source code indentation removed:
https://runkit.com/embed/rvwjw7kooe7j/clone
From the README:

You can explicitly specify the indentation level by passing outdent as the first interpolated value. Its position sets the indentation level and it is removed from the output:
const output = outdent`
      ${outdent}
        Yo
    12345
          Hello world
`;

assert(output === '  Yo\n345\n    Hello world');

Note: ${outdent} must be alone on its own line without anything before or after it. It cannot be preceded by any non-whitespace characters.
If these conditions are not met, outdent will follow normal indentation-detection behavior.


Add the possibility of using AddObject method

This adds the possibility to Add Object Element to the SignedXml and it simply uses method AddObject from SignedXml DotNet.
There was DataObject DotNet missing in the DotNet Aliases, that is why I have added the "System.Security.Cryptography.Xml.DataObject" under "System.Security" assembly.

@haoranpb, I did the requested changes, could you look again? The "re-request review" button does not work for me.

@maciejmlocek I think it's already merged into our internal system with few minor changes yesterday. I'll take a look tonight to reflect the changes

@haoranpb so you mean, somone else requested these changes earlier, right?

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Reopening, as this should get merged.

Availability update: We will publish a fix for this issue in the next update for release 19.


fix the bug when image is replicated from other registries

Signed-off-by: Chen Jing<EMAIL_ADDRESS>Fixes ISSUE #118
Description
The risk scanner need to fetch the vulnerability report from harbor.
However, when the image is replicated from dockerhub to harbor. I found that risk scanner cannot get the vulnerability report. This is because there is a bug in the code:
id.Registry() should be docker.io but we must fetch from the harbor instance.
Actually we don't need to send the request like this, we should use the harbor sdk to send the request.
However, there is a known issue that makes the sdk not work.
So now we must use the string-url to send the request, however, after this change, the repilicated image's vulnerability report can be fetched if the project is a public one, but cannot be fetched when the project is a private one
Well, at least, this time we make this happen when the project is a public one, a workaround for now is to change the project to public manually after replication. Then risk scanner can work "properly"

When the Harbor issue is fixed, we still should use the SDK, that is the right thing to do.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@c5f15a6). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #124   +/-   ##
=======================================
  Coverage        ?   43.70%
=======================================
  Files           ?       10
  Lines           ?     1167
  Branches        ?        0
=======================================
  Hits            ?      510
  Misses          ?      624
  Partials        ?       33

Flag
Coverage Δ

unittests
43.70% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Fix bug in extracting ingress types in Composites from YAML for the metadata.json

Purpose

Fix bug in extracting ingress types in Composites from YAML for the metadata.json

Goals

Fix bug in extracting ingress types in Composites from YAML for the metadata.json

Approach

Fix bug in extracting ingress types in Composites from YAML for the metadata.json

User stories

N/A

Release note

N/A

Documentation

N/A

Training

N/A

Certification

N/A

Marketing

N/A

Automation tests

Unit tests

N/A

Integration tests

N/A

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
Ran FindSecurityBugs plugin and verified report? yes
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Samples

N/A

Related PRs

N/A

Migrations (if applicable)

N/A

Test environment

N/A

Learning

N/A

Codecov Report

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

@@           Coverage Diff           @@
##           master     #637   +/-   ##
=======================================
  Coverage   66.74%   66.74%
=======================================
  Files          36       36
  Lines        1245     1245
  Branches      107      107
=======================================
  Hits          831      831
  Misses        375      375
  Partials       39       39

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 441511c...36c7124. Read the comment docs.


Make the tests work with Python 2.7

Currently, there is a problem with unicode file names.

After more investigation, it appears that the problem occurs because of improper unicode handling in python 2.7's urllib. UTF-8 file names cannot be joined at some point. It would be great to find a solution that does not involve a lossy conversion of all file names to ascii.

I'm now thinking of not trying to support python 2 actively, since it's on the way to deprecation and we lack the time resources, unless somebody is interested on maintaining support themselves.

I support dropping py2!

I agree with dropping python 2.


upload two files(set custom files)

I have two file in one form and I most set different setting for two files(such as file location).
so I can't set different setting. My solution for this is set public $files property and disable line 95 of uploader.php:
$this->files = $this->request->getUploadedFiles();
change to:
if(!$this->files)
{
	$this->files = $this->request->getUploadedFiles();
}
and:
private $files; => public $files;

Hi, i look it


Add --no-video (to mirror audio only)

As a first step, rename --no-display to --no-mirror:

the option impacts both video and audio playback, so "no display" is not an appropriate name
it is confusing with the option --display= which is totally unrelated (it refers to the device display)

Using the short version -N works as before.
Using --no-display still works, but generates a warning:
WARN: --no-display is deprecated, use --no-mirror instead.

Then add a new option --no-video:
scrcpy --no-video

And adapt recording to audio files:
scrcpy --no-video --record=file.opus
scrcpy --no-video --audio-codec=aac --record-file=file.aac
# .m4a/.mp4 and .mka/.mkv are also supported for both opus and aac

To record only:
scrcpy --no-mirror --record=file.opus

The opus muxer has been added to the prebuilt FFmpeg for windows releases: https://github.com/rom1v/scrcpy-deps/commits/6.0-scrcpy-3
Fixes #3842

Please review and test. Here is a release of this PR:

scrcpy-win64-pr3978.zip SHA-256: 69c2eb1d3cad610a4e8488ffce6b8f66365b1375b321feb4f2426b3165a5c337
scrcpy-win32-pr3978.zip SHA-256: 559d582f04359ccf4ca72532e73b890079bd9276ba43946cc48d07571b1abc51

Just tried the --no-video, it works great.
I have no need to test other features of this PR, but if you want I can.

@Piripe Thank you for your tests :+1:
If you could test recording only the audio to .opus and .aac and play it with some player (vlc, firefox, other…) to confirm that everything is ok, that would be great :)

I tried recording only the audio with and without the mirroring, it works great!

I also made a little AHK script (I edited the script in the autoadb issues) using autoadb and scrcpy, I really like this way to mirror my phone 😀
https://github.com/Genymobile/scrcpy/assets/77517308/ce2980fc-0707-4432-98e1-9484954dabe3
(Note: I'm REALLY unorganized, as you can see in my taskbar)
The script:
#NoTrayIcon
#Persistent

global hAutoadb

/* Setup Tray icon and add item that will handle
 * double click events
 */
Menu Tray, Icon
Menu Tray, Icon, icon.ico
Menu Tray, Add, Show / Hide autoadb, TrayClick
Menu Tray, Add, Mirror Display, DisplayClick
Menu Tray, Default, Mirror Display

;// Run autoadb hidden
DetectHiddenWindows On
Run autoadb scrcpy --no-video,, Hide, PID
WinWait ahk_pid %PID%
hAutoadb := WinExist()
DetectHiddenWindows Off
return

TrayClick:
OnTrayClick()
return

DisplayClick:
Run scrcpy --no-audio --turn-screen-off --stay-awake --show-touches -b 30M,,, PID
WinWait ahk_pid %PID%
hScrcpy := WinExist()
WinHide ahk_id %hScrcpy%
return

;// Show / hide Autoadb on double click
OnTrayClick() {
	if DllCall("IsWindowVisible", "Ptr", hAutoadb) {
		WinHide ahk_id %hAutoadb%

	} else {
		WinShow ahk_id %hAutoadb%
		WinActivate ahk_id %hAutoadb%
	}
}

Hi, will this work with v4l2? Currently, v4l2 with no display with --required-audio doesn't stream audio

I plan to add --no-mirror-video and --no-mirror-audio later (where --no-mirror would be an alias for both), so that you could use:
scrcpy --no-mirror-video --v4l2-sink=…

Question about the option name: in this MR, --no-display has been renamed to --no-mirror.
I'm wondering if it should be called --no-playback instead (and --no-video-playback/--no-audio-playback for individual streams)?
For example, if we use a V4L2 think without a scrcpy window (scrcpy --no-mirror --v4l2-sink=/dev/video2), then we can consider we are still "mirroring" the device?
What do you think?


remove .clear() from public API

follow up for https://github.com/hoodiehq/hoodie-client-store/pull/66
The .clear() method makes sense https://github.com/hoodiehq/pouchdb-hoodie-api as it’s for local data only. But as hoodie-client-store has sync, the .clear() method becomes confusing. What shall happen if I continuously sync data with a remote db and then call .clear()?
Instead of the clear() method, we added the reset() method which also accepts options to change the local and remote db name. We should not expose the .clear() method any longer.

[x] claim this issue (@nickcolley)

[x] README: replace .clear() with .reset(options)

[x] commit with docs(README): replaced .clear with .reset

[x] start a PR (#68)

[x] Add test that db.clear is undefined to /tests/specs/constructor.js

[x] commit with `test: .clear() removed

[x] cherry pick methods from pouchdb-hoodie-api instead of exposing them all: https://github.com/hoodiehq/hoodie-client-store/blob/master/index.js#L64 so that .clear() does not get exposed anymore.

[x] commit with
```
fix: .clear() removed
BREAKING CHANGE:

`store.clear()` method has been removed in favor of `store.reset(options)`
```

[x] review & merge

I'll pick this up but will wait encase a proper starter wants to do this PR :)

@nickcolley don’t worry, please take it, these issues are for everyone :) We have enough ready starter issues

fixed via https://github.com/hoodiehq/hoodie-client-store/pull/68


Update Develocity plugin to 3.17.2

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build


Loading React types does not work anymore

Since they added exports field, index.d.ts cannot be imported anymore directly like in the sample code.
Module not found: Error: Package path ./index.d.ts?raw is not exported from package /Users/***/GITHUB/gdm-ui/node_modules/@types/react (see exports field in<EMAIL_ADDRESS>
This isn't directly a bug in the addon, but it makes the example invalid.

I see in code this is already resolved by DefinePlugin, but I leave the issue open since in README this is not reflected.

Can you point me to where it's out of date? Sorry, I know the README isn't very thorough and could be improved.

I honestly didn't check the current Readme and I copied form here: https://storybook.js.org/addons/storybook-addon-code-editor
I expected this to be in sync with the repo, seems like I was wrong. This still has the old example for me, but I guess not much you can do here.

I see the old README there too. I guess it takes time for them to update it.

React type definitions are loaded automatically in v2. See changes here.


[Haxe][CodeGenerator] Index was outside the bounds of the array.

Index was outside the bounds of the array.

   at ASCompletion.Completion.ASGenerator.GuessVarName(String name, String type)
   at ASCompletion.Completion.ASGenerator.AssignStatementToVar(ScintillaControl sci, ClassModel inClass, StatementReturnType returnType)
   at ASCompletion.Completion.ASGenerator.GenerateJob(GeneratorJobType job, MemberModel member, ClassModel inClass, String itemLabel, Object data)
   at ASCompletion.Completion.GeneratorItem.get_Value()
   at PluginCore.Controls.CompletionList.ReplaceText(ScintillaControl sci, String tail, Char trigger)
   at PluginCore.Controls.CompletionList.HandleKeys(ScintillaControl sci, Keys key)
   at PluginCore.Controls.UITools.HandleKeys(Keys key)
   at PluginCore.Controls.UITools.HandleEvent(Object sender, NotifyEvent e, HandlingPriority priority)
   at PluginCore.Managers.EventManager.DispatchEvent(Object sender, NotifyEvent e)

var _ = "";
_; | // | <-- cursor

fixed via #2152


Geophysical surveys layout

We need a consistent layout for the surveys. I think we are little pedantic about the Tx, Rx, Systems. They could be included under a single heading of Instrumentation.  How about the following format?
DCR (or any survey)
Landing page:   iconic image for DCR
Motivational examples
Basic ideas
Examples:  (links to case histories that use the technique)
Governing equations
Instrumentation    (includes Tx, Rx, Systems)
Survey design
Data
Interpretation
Practical Considerations

What do you envision as the difference between the "Motivational Examples" and "Examples"? From a user perspective, I think having a single "Examples" page, with motivational examples, and further link to case histories might be the way to go?

What about combining "Governing Equations" and "Basic Ideas" into a single "Governing Physics" (the equations are then more tightly coupled to the basic ideas)?

[ ] index page (landing page):

purpose (motivation, why) (eg. Purpose: to illustrate the fundamentals of a DC resistivity survey, provide a vision for how it is applied in the field, and demonstrate potential uses)
iconic image (shows the basics, fundamentals, eg. DC one right now)
motivational examples to show where it has been useful (these contain links to case histories)
overview of the chapter: what (v. similar to what is currently there)
contents | case histories (lists of both)

[ ] physics

start with iconic picture(s) (Figure 2 on http://gpg.geosci.xyz/en/latest/content/DC_resistivity/DC_measurements_and_data.html)
once over lightly
bring in 2 sphere example

charges + currents (movie)
potentials

governing equations: formulate in terms of j, phi (link back to fundamentals). Pictures connected to each of the variables in the equations (show potential and highlight phi, for example)

[ ] survey

setup: basic survey - 4 electrode system (transmitter and receiver - link to instrumentation). Can put in any configuration (eg. poles, dipoles)  - link to survey design (prompt that you should give thought to line spacing, station spacing, ...)
layout: wenner, slb, ..., "rules of thumbs" (electrode spacing, depth of investigation)
instrumentation: transmitters, receivers, systems

[ ] data:

plotting data (pseudo-sections)
apparent resistivity - why would you plot these? what do you gain?

[ ] interpretation:

inversion
depth of investigation
hypothesis testing

[ ] survey design: working with synthetics - forward and inverse
[ ] practical considerations:

Index page layout

looking sharp.
How do you split the page in two (i.e. drawing)?
Can you push an example in rst?

(don't actually know yet, ha). I can take a first crack at the re-organization and then do a pr to run it by everyone?

This issue will be addressed in

index: #204,
physics: #205
survey #206
data #207
interpretation #208
survey design #209
practical considerations #210


Updated to include a couple c# books

updated to include a couple c# books, that i think are good reads.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Updated book section to include c#

LGTM! Thanks for adding these resources @kakoon8 - I just moved the section up so it's roughly alphabetical. Happy coding 📚 👓 🗒 !


Detecting obsolete YAML config for platforms now obsolete

Detecting obsolete YAML configuration for platforms is obsolete as of Home Assistant 2023.6
Ref: https://github.com/home-assistant/core/pull/93585
The repair feature in Spook can thus be removed.

Same for unknown integrations:
https://github.com/home-assistant/core/pull/93807

dropped in #191


--blacklist option doesn't work when running goodbyedpi.exe -2 mode

Operating system / операционная система
Windows 10 21H2
Running as service / Запуск программы как сервис
I run it as a regular program / Запускаю программу обычным образом
Describe the bug / Опишите ошибку программы
Hello,
The --blacklist option doesn't work when I use goodbyedpi.exe -2
I tested with goodbyedpi.exe -2 and goodbyedpi.exe -5
On -5, the blacklist works just fine. But on -2, the blacklist doesn't work.
Is this a bug or limitation of the program?
Thanks
Additional information / Дополнительная информация
No response

This is a known issue. SNI/hostname analysis works only for Window Size=1 or 2, not more.
Non-window-size splitting does not have this issue.
It should print this message:
https://github.com/ValdikSS/GoodbyeDPI/blob/4a82fd442dcdd69de731fb717fb055f8547083fa/src/goodbyedpi.c#L998-L1002


github_analyzeCharactersTextfile_chunks.py: Counting of characters is wrong if chunk size is too small

Counted characters: result is depending on chunk size, assumption: only last chunk is analyzed or added to results

Tested: Problem is the dictionary.update()-function (in sourcecode: number_of_type_char.update(check_freq_count) ). It will only update key-value-pairs, that means replace the old one with the new ones (and perhaps holds the key-value-pairs who are not updated by a new key).
What is needed is a function, which add the already existing values from the key to the new one (read from current chunk) of the same key and put some new keys (with its value, of course) to the dictionary if key is not existing yet.

2.0 - Program is able to handle files bigger than system memory


Last Week in Pony - May 28, 2023

Please feel free to modify the language for correctness here, @SeanTAllen . As I said over in Zulip, I came down with something at the end of the week so I opted to highlight a quick topic rather than the original CoC plan.


Update talk: Weirdest PromQL

We need to make those changes in Sessionize because next time we render those files it'll be overwritten.
I'll see if we can make it happen through that.

Fixed the one intention. It should be good now.
If not let me know.


Integration Test - Release - 2019/05/14 22:12:59

Auto create for integration test. IssueCommandFlow

@PRMergerTest2 : Thanks for your contribution! The author, @v-caxian, has been notified to review your proposed change.


model api deployment ?

In https://github.com/IBM/MAX-Question-Answering-Web-App#deploy-the-model
it says docker run -it -p 5000:5000 codait/max-question-answering-web-app, should it not be docker run -it -p 5000:5000 codait/max-question-answering?

That is a typo. On the same note, should we be hosting the web app in a long running instance too?

Webapp long running instance here: http://max-question-answering-web-app.max.us-south.containers.appdomain.cloud/


Azure - fix appserviceplan resource type parsing bug

Bug fix for #2741
change resource type to be case-insensitive

Going to abandon this PR to get ride of some of the clutter


Unable to use Yarp on Azure App Services?

Scenario
We use a library called Cocoon which utilizes YARP 1.1 to proxy requests to a .NET 6 application to an older WebForms application. It's running fine on our hosted servers - the NET 6 application proxies requests to an internal IP address on a port using HTTP.
Azure Problems
We wish to port our application to Azure App Services, so I set up a DevOps release pipeline to create two App Services hosted on a Windows App Service Plan, in the same region. The parent NET 6 application is then configured to proxy traffic to the WebForm app. I used the Azure domain names for each service with HTTPS for both sites.  Both apps are running fine when queried directly.
All proxied requests to the WebForms app fail with a 400 status code, even requests for static content. I've tried to add more logging to see what's going wrong, but I've not figured out any more than a 400 status code.
What I've Tried

I tried disabling HTTP/2 on the WebForm app - no change.
I configured the proxy address to use http:// and turned off HTTPS Only on the WebForm app in case it was related to SSL.
I upgraded the YARP version from 1.1 to 2.0 to see if that made a difference.
Tried creating a simple controller action on the WebForm site that logged the request details but it never gets executed

Log
Below is the log from the NET 6 application when it tried to request a proxied resource (in this case a static image /img/DefaultLogojpg). It starts the request and first makes a call to the remote URI https://webform-site-url/facadeauth which is a Cocoon check for authentication status on the WebForm app. This returns 401 which is correct since the user isn't logged in - so this part of the operation worked correctly and did request the remote resource.
It then gets a 400 error on requesting the actual resource, and it seems to be repeated several times (it might be a retry option in Cocoon/YARP?).

If there are any other tests or YARP configurations I can try, or specific logging I can perform to diagnose the cause I'm welcome to suggestions as I've been stuck on this for several days.

Glancing at Cocoon's implementation, I suspect you are forwarding the request's host header as-is.
For example, if you had sites A.azure and B.azure, where A proxied requests to B, you may be sending requests to B's IP while specifying A as the host.
Assuming you don't have access to YARP's transforms, you can try setting
context.Request.Headers.Host = default;

before proxying the request (e.g. in the first middleware that runs), and YARP will use B.azure as the host header instead.

Thanks for the suggestion @MihaZupan, will investigate

Triage: Seems to be answered. 9 days no response. Closing.

@MihaZupa many thanks for your excellent suggestion - it was the Host header that was the culprit!
I believe the Azure front-end uses the Host header value to direct the correct App Service - so when the request is made to A.azure, it forwards to B.azure with the original host header. I think Azure sees this as an error - hence 400 - bad request. All fixed!


Improve release page UI

Improve the release page UI by

adding the file size
change the icon from desktop-download to package
make download title bold

Screenshot

Codecov Report

Merging #3693 into master will decrease coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #3693      +/-   ##
==========================================
- Coverage    35.8%   35.79%   -0.02%
==========================================
  Files         287      287
  Lines       41489    41496       +7
==========================================
- Hits        14857    14854       -3
- Misses      24445    24454       +9
- Partials     2187     2188       +1

Impacted Files
Coverage Δ

models/attachment.go
44.52% <0%> (-2.25%)
:arrow_down:

modules/process/manager.go
76.81% <0%> (-4.35%)
:arrow_down:

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 c28bf94...45f6b65. Read the comment docs.

LGTM


Anti-commutativity

Quaternions are non-commutative, so some equivalences e.g. (a * b) <=> (b * a) are not sound.

One idea is to introduce a swap_sign(a, b) function that returns the sign given that a and b are swapped.

Another problem is that when you take the exponential, multiplication turns into addition, so anti-commutativity on multiplication implies anti-commutativity on addition. This leads to unsoundness in quaternion algebra, because addition is commutative.

One idea is to lift quaternions into vectors and multiplication into quaternion multiplication.

One idea is to use type judgements on quaternions. Pattern matching for binding variables could fail by default on type judgement.


vmlistener_test tearDown logic is unstable

vmlistener_test tearDown logic is unstable: it fails intermittently when I run e2e test locally:
2017/05/30 18:28:55 Failed to invoke command [docker volume rm vmlistener_test_volume_1496168883]: exit status 1

FAIL: vmlistener_test.go:61: VMListenerTestParams.TearDownTest
vmlistener_test.go:67:
c.Assert(err, IsNil, Commentf(out))
... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0xc420167620), Stderr:[]uint8(nil)} ("exit status 1")
... Error response from daemon: unable to remove volume: remove vmlistener_test_volume_1496168883: VolumeDriver.Remove: Remove failure - volume is still mounted.  volume=vmlistener_test_volume_1496168883, refcount=1

PANIC: vmlistener_test.go:80: VMListenerTestParams.TestKillVM
... Panic: Fixture has panicked (see related PANIC)
OOPS: 8 passed, 1 FAILED, 1 MISSED
--- FAIL: Test (274.17s)

@shuklanirdesh82 Can you please take a look?

@shaominchen can you please supply the whole test run log?

@shuklanirdesh82 My local environment has been overwritten by other tests. Will provide if I reproduce this. Meanwhile you can also try to run e2e test locally a few times - it should not be difficult to reproduce.

@shaominchen I did multiple times (6 times so far with master code) and not able to reproduce hence the request for full logs.

BTW .. PR#1306 should take care of such intermittent failure (supplied a quick PR) until we are getting rid off all log.fatalf() messages.

@shuklanirdesh82 Here are the complete logs:
shchen-m02:docker-volume-vsphere shchen$ make e2e-test
/Library/Developer/CommandLineTools/usr/bin/make --directory=vmdk_plugin e2e-test
Makefile:152: warning: overriding commands for target clean' ../plugin/Makefile:87: warning: ignoring old commands for target clean'
=> Running target e2e-test Tue May 30 12:16:14 PDT 2017
../misc/scripts/build.sh e2e-dkrVolDriver-test "<IP_ADDRESS>" "<IP_ADDRESS>" "<IP_ADDRESS>"
Makefile:152: warning: overriding commands for target clean' ../plugin/Makefile:87: warning: ignoring old commands for target clean'
make: Entering directory `/go/src/github.com/vmware/docker-volume-vsphere/vmdk_plugin'
=> Running target e2e-dkrVolDriver-test Tue May 30 19:16:14 UTC 2017
GO15VENDOREXPERIMENT=1 go test github.com/vmware/docker-volume-vsphere/tests/e2e -v
=== RUN   Test
2017/05/30 19:16:15 START: basic-test.TestVolumeIsolation
2017/05/30 19:16:15 Creating volume [basic_test_volume_1496171775] on VM [<IP_ADDRESS>]
2017/05/30 19:16:18 Checking volume [basic_test_volume_1496171775] availability from VM [<IP_ADDRESS>]
2017/05/30 19:16:18 Checking volume [basic_test_volume_1496171775] availability from VM [<IP_ADDRESS>]
2017/05/30 19:16:19 Destroying volume [basic_test_volume_1496171775]
2017/05/30 19:16:20 END: basic-test.TestVolumeIsolation
2017/05/30 19:16:20 START: basic-test.TestVolumeLifecycle
2017/05/30 19:16:20 Creating volume [basic_test_volume_1496171780] on VM [<IP_ADDRESS>]
2017/05/30 19:16:22 Checking volume [basic_test_volume_1496171780] availability from VM [<IP_ADDRESS>]
2017/05/30 19:16:22 Attaching volume [basic_test_volume_1496171780] on VM [<IP_ADDRESS>]
2017/05/30 19:16:24 Confirming attached status for volume [basic_test_volume_1496171780]
2017/05/30 19:16:26 Removing container [basic_test_container_1496171780] on VM [<IP_ADDRESS>]
2017/05/30 19:16:27 Confirming detached status for volume [basic_test_volume_1496171780]
2017/05/30 19:16:27 Sleep for 2 seconds
2017/05/30 19:16:31 Destroying volume [basic_test_volume_1496171780]
2017/05/30 19:16:32 Checking volume [basic_test_volume_1496171780] availability from VM [<IP_ADDRESS>]
2017/05/30 19:16:33 Creating volume [basic_test_volume_1496171780] on VM [<IP_ADDRESS>]
2017/05/30 19:16:35 Checking volume [basic_test_volume_1496171780] availability from VM [<IP_ADDRESS>]
2017/05/30 19:16:35 Attaching volume [basic_test_volume_1496171780] on VM [<IP_ADDRESS>]
2017/05/30 19:16:37 Confirming attached status for volume [basic_test_volume_1496171780]
2017/05/30 19:16:39 Removing container [basic_test_container_1496171780] on VM [<IP_ADDRESS>]
2017/05/30 19:16:40 Confirming detached status for volume [basic_test_volume_1496171780]
2017/05/30 19:16:40 Sleep for 2 seconds
2017/05/30 19:16:44 Destroying volume [basic_test_volume_1496171780]
2017/05/30 19:16:44 Checking volume [basic_test_volume_1496171780] availability from VM [<IP_ADDRESS>]
2017/05/30 19:16:45 END: basic-test.TestVolumeLifecycle
2017/05/30 19:16:45 Finding VM name from IP Address [<IP_ADDRESS>]
2017/05/30 19:16:46 Initializing the SingleNode Config DB on esx [<IP_ADDRESS>]
2017/05/30 19:16:47 START: defaultvmgroup.TestAddVMToDefaultTenant
2017/05/30 19:16:47 Adding VM [VM1.2] to a vmgroup [_DEFAULT ] on esx [<IP_ADDRESS>]
2017/05/30 19:16:48 END: defaultvmgroup.TestAddVMToDefaultTenant
2017/05/30 19:16:48 START: defaultvmgroup.TestRemoveDefaultTenantVMs
2017/05/30 19:16:48 Removing VM [VM1.2] from a vmgroup [_DEFAULT ] on esx [<IP_ADDRESS>]
2017/05/30 19:16:49 END: defaultvmgroup.TestRemoveDefaultTenantVMs
2017/05/30 19:16:49 START: defaultvmgroup.TestReplaceDefaultTenantVMs
2017/05/30 19:16:49 Replacing VM [VM1.2] from a vmgroup [_DEFAULT ] on esx [<IP_ADDRESS>]
2017/05/30 19:16:50 END: defaultvmgroup.TestReplaceDefaultTenantVMs
2017/05/30 19:16:50 Removing the SingleNode Config DB on esx [<IP_ADDRESS>]
2017/05/30 19:16:51 Creating volume [restart_test_volume_1496171811] on VM [<IP_ADDRESS>]
2017/05/30 19:16:55 START: restart_test.TestPluginKill
2017/05/30 19:16:55 Attaching volume [restart_test_volume_1496171811] on VM[<IP_ADDRESS>]
2017/05/30 19:16:56 Confirming attached status for volume [restart_test_volume_1496171811]
2017/05/30 19:16:58 Killing vDVS plugin on VM [<IP_ADDRESS>]
2017/05/30 19:16:59 Sleep for 2 seconds
2017/05/30 19:17:01 Stopping container [restart_test_container_1496171811] on VM [<IP_ADDRESS>]
2017/05/30 19:17:13 Starting container [restart_test_container_1496171811] on VM [<IP_ADDRESS>]
2017/05/30 19:17:14 Stopping container [restart_test_container_1496171811] on VM [<IP_ADDRESS>]
2017/05/30 19:17:25 Confirming detached status for volume [restart_test_volume_1496171811]
2017/05/30 19:17:25 Sleep for 2 seconds
2017/05/30 19:17:29 END: restart_test.TestPluginKill
2017/05/30 19:17:29 Removing container [restart_test_container_1496171811] on VM [<IP_ADDRESS>]
2017/05/30 19:17:30 Destroying volume [restart_test_volume_1496171811]
2017/05/30 19:17:30 Creating volume [restart_test_volume_1496171850] on VM [<IP_ADDRESS>]
2017/05/30 19:17:33 START: restart_test.TestVolumeStaleMount
2017/05/30 19:17:33 Attaching volume [restart_test_volume_1496171850] on VM [<IP_ADDRESS>]
2017/05/30 19:17:34 Confirming attached status for volume [restart_test_volume_1496171850]
2017/05/30 19:17:36 Killing docker on VM [<IP_ADDRESS>]
2017/05/30 19:17:36 Sleep for 2 seconds
2017/05/30 19:17:39 Confirming detached status for volume [restart_test_volume_1496171850]
2017/05/30 19:17:39 Sleep for 2 seconds
2017/05/30 19:17:56 Sleep for 2 seconds
2017/05/30 19:17:58 Sleep for 2 seconds
2017/05/30 19:18:02 END: restart_test.TestVolumeStaleMount
2017/05/30 19:18:02 Removing container [restart_test_container_1496171850] on VM [<IP_ADDRESS>]
2017/05/30 19:18:03 Destroying volume [restart_test_volume_1496171850]
2017/05/30 19:18:04 Listing swarm cluster nodes on VM [<IP_ADDRESS>]
2017/05/30 19:18:04 Creating volume [swarm_test_volume_1496171884] on VM [<IP_ADDRESS>]
2017/05/30 19:18:06 Confirming detached status for volume [swarm_test_volume_1496171884]
2017/05/30 19:18:06 Sleep for 2 seconds
2017/05/30 19:18:10 START: swarm_test.TestDockerSwarm
2017/05/30 19:18:10 Creating a docker service swarm_test_service_1496171884 on VM [<IP_ADDRESS>]
2017/05/30 19:18:12 Checking docker service [swarm_test_service_1496171884] status on VM [<IP_ADDRESS>]
2017/05/30 19:18:12 Listing docker services running on VM [<IP_ADDRESS>]
2017/05/30 19:18:12 Checking running containers for docker service [swarm_test_service_1496171884] on docker hosts: [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>]
2017/05/30 19:18:13 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.1.4jb1meifdtivsykhw2z65ybb2
2017/05/30 19:18:13 Confirming attached status for volume [swarm_test_volume_1496171884]
2017/05/30 19:18:15 Scaling 2 replicated services for swarm_test_service_1496171884 on VM [<IP_ADDRESS>]
2017/05/30 19:18:16 Checking docker service [swarm_test_service_1496171884] status on VM [<IP_ADDRESS>]
2017/05/30 19:18:16 Listing docker services running on VM [<IP_ADDRESS>]
2017/05/30 19:18:16 Checking running containers for docker service [swarm_test_service_1496171884] on docker hosts: [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>]
2017/05/30 19:18:17 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.1.4jb1meifdtivsykhw2z65ybb2
2017/05/30 19:18:17 Sleep for 5 seconds
2017/05/30 19:18:22 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.1.4jb1meifdtivsykhw2z65ybb2
2017/05/30 19:18:22 Sleep for 5 seconds
2017/05/30 19:18:28 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.1.4jb1meifdtivsykhw2z65ybb2
2017/05/30 19:18:28 Sleep for 5 seconds
2017/05/30 19:18:33 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.1.4jb1meifdtivsykhw2z65ybb2
2017/05/30 19:18:33 Sleep for 5 seconds
2017/05/30 19:18:39 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.1.4jb1meifdtivsykhw2z65ybb2
2017/05/30 19:18:39 Sleep for 5 seconds
2017/05/30 19:18:44 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.1.4jb1meifdtivsykhw2z65ybb2
2017/05/30 19:18:44 Sleep for 5 seconds
2017/05/30 19:18:49 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.1.4jb1meifdtivsykhw2z65ybb2
2017/05/30 19:18:49 Sleep for 5 seconds
2017/05/30 19:18:55 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.1.4jb1meifdtivsykhw2z65ybb2
2017/05/30 19:18:55 Sleep for 5 seconds
2017/05/30 19:19:00 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.1.4jb1meifdtivsykhw2z65ybb2
2017/05/30 19:19:00 Sleep for 5 seconds
2017/05/30 19:19:06 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.1.4jb1meifdtivsykhw2z65ybb2
2017/05/30 19:19:06 Sleep for 5 seconds
2017/05/30 19:19:11 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.1.4jb1meifdtivsykhw2z65ybb2
2017/05/30 19:19:11 Sleep for 5 seconds
2017/05/30 19:19:17 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.2.ypfvob4ti7e8qczzv3qct41c2
swarm_test_service_1496171884.1.4jb1meifdtivsykhw2z65ybb2
2017/05/30 19:19:17 Stopping docker service swarm_test_service_1496171884.1.4jb1meifdtivsykhw2z65ybb2 on VM [<IP_ADDRESS>]
2017/05/30 19:19:28 Checking docker service [swarm_test_service_1496171884] status on VM [<IP_ADDRESS>]
2017/05/30 19:19:28 Listing docker services running on VM [<IP_ADDRESS>]
2017/05/30 19:19:28 Checking running containers for docker service [swarm_test_service_1496171884] on docker hosts: [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>]
2017/05/30 19:19:29 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.2.ypfvob4ti7e8qczzv3qct41c2
2017/05/30 19:19:29 Sleep for 5 seconds
2017/05/30 19:19:34 Containers running on docker host [<IP_ADDRESS>]: swarm_test_service_1496171884.1.n552uhd3gmeup01dwix1nqrid
swarm_test_service_1496171884.2.ypfvob4ti7e8qczzv3qct41c2
2017/05/30 19:19:34 Confirming attached status for volume [swarm_test_volume_1496171884]
2017/05/30 19:19:37 Destroying volume [swarm_test_volume_1496171884]
2017/05/30 19:19:37 Failed to invoke command [docker volume rm swarm_test_volume_1496171884]: exit status 1
2017/05/30 19:19:37 Removing docker service swarm_test_service_1496171884 on VM [<IP_ADDRESS>]
2017/05/30 19:19:38 Listing docker services running on VM [<IP_ADDRESS>]
2017/05/30 19:19:38 Failed to invoke command [docker service ps swarm_test_service_1496171884]: exit status 1
2017/05/30 19:19:38 Confirming detached status for volume [swarm_test_volume_1496171884]
2017/05/30 19:19:38 Sleep for 2 seconds
2017/05/30 19:19:41 Sleep for 2 seconds
2017/05/30 19:19:44 Sleep for 2 seconds
2017/05/30 19:19:47 Sleep for 2 seconds
2017/05/30 19:19:51 END: swarm_test.TestDockerSwarm
2017/05/30 19:19:51 Destroying volume [swarm_test_volume_1496171884]
2017/05/30 19:19:52 Finding VM name from IP Address [<IP_ADDRESS>]
2017/05/30 19:19:53 START: Test vmdkops service restart + kill vm process
2017/05/30 19:19:53 Creating volume [vmlistener_test_volume_1496171993] on VM [<IP_ADDRESS>]
2017/05/30 19:19:55 Attaching volume [vmlistener_test_volume_1496171993] on VM [<IP_ADDRESS>]
2017/05/30 19:19:57 Confirming attached status for volume [vmlistener_test_volume_1496171993]
2017/05/30 19:19:59 Restarting vmdkops service on ESX host [<IP_ADDRESS>]
2017/05/30 19:20:02 Confirming attached status for volume [vmlistener_test_volume_1496171993]
2017/05/30 19:20:06 Retrieving VM power state for [VM1.2]
2017/05/30 19:20:07 VM[VM1.2]'s current power state is [poweredOn]
2017/05/30 19:20:07 Retrieving World ID for VM [VM1.2] from ESX [<IP_ADDRESS>]
2017/05/30 19:20:07 VM's process ID is: 6134808
2017/05/30 19:20:07 Killing VM from ESX [<IP_ADDRESS>]
2017/05/30 19:20:08 Confirming [poweredOff] power status for vm [VM1.2]
2017/05/30 19:20:08 Sleep for 3 seconds
2017/05/30 19:20:11 Retrieving VM power state for [VM1.2]
2017/05/30 19:20:14 Powering on VM [VM1.2]
2017/05/30 19:20:16 Confirming [poweredOn] power status for vm [VM1.2]
2017/05/30 19:20:16 Sleep for 3 seconds
2017/05/30 19:20:19 Retrieving VM power state for [VM1.2]
2017/05/30 19:20:20 Confirming detached status for volume [vmlistener_test_volume_1496171993]
2017/05/30 19:20:20 Sleep for 2 seconds
2017/05/30 19:20:31 Failed to invoke command [docker volume inspect  --format '{{index .Status.status}}' vmlistener_test_volume_1496171993]: exit status 255
2017/05/30 19:20:31 Sleep for 2 seconds
2017/05/30 19:20:33 Failed to invoke command [docker volume inspect  --format '{{index .Status.status}}' vmlistener_test_volume_1496171993]: exit status 255
2017/05/30 19:20:33 Sleep for 2 seconds
2017/05/30 19:20:43 END: Test vmdkops service restart + kill vm process
2017/05/30 19:20:43 Checking container [vmlistener_test_container_1496171993] presence on VM [<IP_ADDRESS>]
2017/05/30 19:20:44 Destroying volume [vmlistener_test_volume_1496171993]
2017/05/30 19:20:44 Failed to invoke command [docker volume rm vmlistener_test_volume_1496171993]: exit status 1

FAIL: vmlistener_test.go:61: VMListenerTestParams.TearDownTest
vmlistener_test.go:67:
c.Assert(err, IsNil, Commentf(out))
... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0xc4201673a0), Stderr:[]uint8(nil)} ("exit status 1")
... Error response from daemon: unable to remove volume: remove vmlistener_test_volume_1496171993: VolumeDriver.Remove: Remove failure - volume is still mounted.  volume=vmlistener_test_volume_1496171993, refcount=1

PANIC: vmlistener_test.go:80: VMListenerTestParams.TestKillVM
... Panic: Fixture has panicked (see related PANIC)
OOPS: 8 passed, 1 FAILED, 1 MISSED
--- FAIL: Test (269.22s)
=== RUN   TestVolumeProperties
2017/05/30 19:20:44 running end_to_end tests - current time:  2017-05-30 19:20:44.834216839 +0000 UTC
2017/05/30 19:20:44 Running test on VM -  <IP_ADDRESS>
2017/05/30 19:20:44 Creating a volume of Format Type -  thin
2017/05/30 19:20:48
successfully created a  volume --  volumeprop_test_volume_1496172044
2017/05/30 19:20:48 Verifying volume properties like size, disk-format and attached-to-vm fields at vm and esx for volume -  volumeprop_test_volume_1496172044
2017/05/30 19:20:56 Finished verifying volume properties like size, disk-format and attached-to-vm fields at vm and esx for volume -  volumeprop_test_volume_1496172044
2017/05/30 19:21:08 Creating a volume of Format Type -  zeroedthick
2017/05/30 19:21:10
successfully created a  volume --  volumeprop_test_volume_1496172068
2017/05/30 19:21:10 Verifying volume properties like size, disk-format and attached-to-vm fields at vm and esx for volume -  volumeprop_test_volume_1496172068
2017/05/30 19:21:17 Finished verifying volume properties like size, disk-format and attached-to-vm fields at vm and esx for volume -  volumeprop_test_volume_1496172068
2017/05/30 19:21:28 Creating a volume of Format Type -  eagerzeroedthick
2017/05/30 19:21:31
successfully created a  volume --  volumeprop_test_volume_1496172088
2017/05/30 19:21:31 Verifying volume properties like size, disk-format and attached-to-vm fields at vm and esx for volume -  volumeprop_test_volume_1496172088
2017/05/30 19:21:39 Finished verifying volume properties like size, disk-format and attached-to-vm fields at vm and esx for volume -  volumeprop_test_volume_1496172088
--- PASS: TestVolumeProperties (65.71s)
FAIL
2017/05/30 19:21:52 -----Clean-up finished - current time:  2017-05-30 19:21:52.060603163 +0000 UTC
exit status 1
FAIL	github.com/vmware/docker-volume-vsphere/tests/e2e	336.449s
make: *** [e2e-dkrVolDriver-test] Error 1
make: Leaving directory `/go/src/github.com/vmware/docker-volume-vsphere/vmdk_plugin'
make[1]: *** [e2e-test] Error 2
make: *** [e2e-test] Error 2

Thanks @shaominchen #1306 takes care of this one.

Reopen this issue as it still happens intermittently. We have missed one step in previous fix - to check the volume detached status. This step is REQUIRED because stopping or removing a container will NOT release the volume immediately, since it takes some time for the container to stop or exit. We must use a poller to check and verify the volume status is detached before removing it. Please refer to basic_test as an example: https://github.com/vmware/docker-volume-vsphere/blob/master/tests/e2e/basic_test.go#L84

We have missed one step in previous fix - to check the volume detached status. This step is REQUIRED because stopping or removing a container will NOT release the volume immediately, since it takes some time for the container to stop or exit. We must use a poller to check and verify the volume status is detached before removing it. Please refer to basic_test as an example: https://github.com/vmware/docker-volume-vsphere/blob/master/tests/e2e/basic_test.go#L84

Test case step https://github.com/vmware/docker-volume-vsphere/blob/master/tests/e2e/vmlistener_test.go#L126 does make sure detached state before invoking docker volume rm.

Testcase does uses polling mechanism to check upon power state and detach/attach state. Only gap here is about refCount thread state (see https://github.com/vmware/docker-volume-vsphere/pull/1300#discussion_r118602099)

At present there is no way to know about refCount operation is in progress or completed. (vDVS plugin refcount thread is running in background and no hook to hang on reliably)

As discussed offline we need to improve plugin error message that returns refcount=-1 when the operation is in-progress ... accordingly change is needed for docker volume rm  util.
There is nothing left for the issue so closing this issue.

@shuklanirdesh82 I have filed issue #1348 for vmdk plugin issue. However, after the plugin issue gets fixed, we still need to fix this test case accordingly to check the "volume rm" error messages. So please file a new issue (since the current one is closed) and mark it depending on issue #1348.

#1349 is opened to track the improvement.


[SPARK-18264][SPARKR] update vignettes for CRAN release build and add info on release

What changes were proposed in this pull request?
Changes to DESCRIPTION to build vignettes.
Changes the metadata for vignettes to generate the recommended format (which is about <10% of before). Unfortunately it does not look as nice
(before - left, after - right)

Also add information on how to run build/release to CRAN later.
How was this patch tested?
manually, unit tests
@shivaram
We need this for branch-2.1

Test build #68249 has started for PR 15790 at commit d51b04b.

Test build #68249 has finished for PR 15790 at commit d51b04b.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68249/
Test FAILed.

Merged build finished. Test FAILed.

This is great @felixcheung - Taking a closer look now

interesting. jenkins failed because it is building vignettes again right after it is built correctly, and the second time it didn't have the Spark jar (so trying to download it as per install.spark)
I'll try to track down where it is doing that.
  Use Petal_Width instead of Petal.Width  as column name
/home/jenkins/workspace/SparkPullRequestBuilder/R
* checking for file '/home/jenkins/workspace/SparkPullRequestBuilder/R/pkg/DESCRIPTION' ... OK
* preparing 'SparkR':
* checking DESCRIPTION meta-information ... OK
* installing the package to build vignettes
* creating vignettes ... ERROR

Attaching package: 'SparkR'

The following objects are masked from 'package:stats':

    cov, filter, lag, na.omit, predict, sd, var, window

The following objects are masked from 'package:base':

    as.data.frame, colnames, colnames<-, drop, intersect, rank,
    rbind, sample, subset, summary, transform, union

Spark not found in SPARK_HOME:
Spark not found in the cache directory. Installation will start.
MirrorUrl not provided.
Looking for preferred site from apache website...
Preferred mirror site found: http://mirror.nexcess.net/apache/spark
Downloading spark-2.1.0 for Hadoop 2.7 from:
- http://mirror.nexcess.net/apache/spark/spark-2.1.0/spark-2.1.0-bin-hadoop2.7.tgz
trying URL 'http://mirror.nexcess.net/apache/spark/spark-2.1.0/spark-2.1.0-bin-hadoop2.7.tgz'
Fetch failed from http://mirror.nexcess.net/apache/spark
To use backup site...
Downloading spark-2.1.0 for Hadoop 2.7 from:
- http://www-us.apache.org/dist/spark/spark-2.1.0/spark-2.1.0-bin-hadoop2.7.tgz
trying URL 'http://www-us.apache.org/dist/spark/spark-2.1.0/spark-2.1.0-bin-hadoop2.7.tgz'
Fetch failed from http://www-us.apache.org/dist/spark
Quitting from lines 31-32 (sparkr-vignettes.Rmd)
Error: processing vignette 'sparkr-vignettes.Rmd' failed with diagnostics:
Unable to download Spark spark-2.1.0 for Hadoop 2.7. Please check network connection, Hadoop version, or provide other mirror sites.
Execution halted

Basically it is building vignettes multiple times - once in create-doc.sh, once with R CMD build.
I'll skip the one in create-doc.sh to get it to create vignettes together with the source package, which I think is the more nature or common behavior.
Also, we are currently passing --no-manual to R CMD check (in check-cran.sh while running from run-tests.sh), otherwise it will once again try to build vignettes (this time from the source package)

Test build #68307 has started for PR 15790 at commit 4d6c919.

Test build #68307 has finished for PR 15790 at commit 4d6c919.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68307/
Test PASSed.

I looked the qpdf warning is from a fairly strict check - I don't see a way around it other than getting qpdf on the system (it's a tool, not a R package).

Can you open a Spark JIRA for installing qpdf and cc @shaneknapp on it ? We can install it on the Jenkins machines.

test this please

ok, qpdf is installed per the jira.   no environment variables set up yet though.

Test build #68348 has started for PR 15790 at commit 4d6c919.

Test build #68348 has finished for PR 15790 at commit 4d6c919.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68348/
Test FAILed.

Test build #68352 has started for PR 15790 at commit 9f24e3f.

Test build #68352 has finished for PR 15790 at commit 9f24e3f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68352/
Test PASSed.

this is good to go in?

ping @shivaram

Sorry I got caught up with some other stuff - Will take a look at this today.

@felixcheung I noticed one more thing - We are somehow not registering the vignette correctly with the R package. So for example if I launch ./bin/sparkR and then run vignette(package="dplyr")
I see a list of vignettes that I can then launch with vignette("introduction", package="dplyr"). However this doesn't seem to work with our vignette - I'm not sure what we need to do to get this to work though.

Tested that more, I think the vignettes works only with installed package (or installed built package)
R CMD INSTALL SparkR_2.1.0.tar.gz

and then
library(SparkR)
vignette("sparkr-vignettes", package="SparkR")

Test build #68497 has started for PR 15790 at commit 323609e.

Test build #68498 has started for PR 15790 at commit 4d34bbe.

Test build #68500 has started for PR 15790 at commit 1681005.

Test build #68497 has finished for PR 15790 at commit 323609e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68497/
Test PASSed.

Test build #68498 has finished for PR 15790 at commit 4d34bbe.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68498/
Test PASSed.

Test build #68500 has finished for PR 15790 at commit 1681005.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68500/
Test PASSed.

I think https://github.com/apache/spark/blob/master/dev/make-distribution.sh should change too but I'm not 100% how the R package is built there.

So one proposal I was thinking of is to just check in a built version of the vignette in to the source tree. That way the release packaging wouldn't need to change. The only thing to keep in mind is that whenever we update the vignette we will need to rebuild it. Thoughts ?

Problem is the required and generated vignette.rds RDS file is a binary file?
I'm not sure about checking in binaries in git, that would show up in a source-only release?
Maybe create-distribution.sh should run the equivalent of R CMD install SparkR.tar.gz to generate the binaries necessary that would only go to a binary release?
How about we merge this PR first - I can test out the release mechanism more next week.

Sure - Sounds good. LGTM. Merging this to master and branch-2.1


Add darwin and windows to GOOS build targets

Summary

Add darwin and windows to GOOS build targets
Fixes #839

Checklist

[ ] Categorize the PR by setting a good title and adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog
[ ] PR contains the label area:operator
[x] Link this PR to related issues
[x] I have not made any changes in the charts/ directory.

Note: This will build the whole operator and not only the CLI for darwin and windows. Is there a specific reason that the K8up operator and CLI are a single binary?

Is there a specific reason that the K8up operator and CLI are a single binary?

There's no real reason. I currently feel like the benefits for having a seperate cli binary aren't worth the effort. That might change in the future ofcourse.

Nope all good, I just didn't have the time to get around to merge it :)


Paste content by dragging from clipboard

Hello! It will be great to realize this function, i also used this in «Copied» app.

Closing as duplicate of https://github.com/p0deje/Maccy/issues/290#issuecomment-874359593


fix rebuild_from_arrays

Fixes #409

Codecov Report

Merging #419 (f561929) into main (8fccac0) will increase coverage by 0.47%.
The diff coverage is 88.76%.

@@            Coverage Diff             @@
##             main     #419      +/-   ##
==========================================
+ Coverage   78.86%   79.34%   +0.47%
==========================================
  Files          41       41
  Lines        3866     3921      +55
==========================================
+ Hits         3049     3111      +62
+ Misses        817      810       -7

Impacted Files
Coverage Δ

src/Rasters.jl
66.66% <ø> (ø)

src/plotrecipes.jl
55.92% <22.22%> (ø)

src/utils.jl
85.08% <75.00%> (+1.90%)
:arrow_up:

src/stack.jl
80.26% <85.71%> (+1.45%)
:arrow_up:

src/write.jl
95.23% <97.05%> (+5.76%)
:arrow_up:

src/convenience.jl
83.33% <100.00%> (+8.33%)
:arrow_up:

src/series.jl
89.23% <100.00%> (+11.95%)
:arrow_up:

src/sources/gdal.jl
85.06% <100.00%> (+0.09%)
:arrow_up:

src/sources/grd.jl
82.60% <100.00%> (+0.12%)
:arrow_up:

src/sources/ncdatasets.jl
83.56% <100.00%> (+0.23%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Controller refactor to use dynamic client instead of generated code

This project uses controllers which watches over 3 cr's. Controller plugin(lvmnodes). Node plugin(lvmvolumes, lvmnodes, lvmsnapshots)
Currently all these controllers are using generated code to implement client. We could use dynamic client from client-go which would reduce code foot prints and will make code more readable as well. In addition to that i am adding only 1 method which would create and return controllers as opposed to using multiple methods to build controller.
Progress on each controller:
Node plugin:

[x] lvmvolumes : Refactored and tested. WIP pr is raised
[x] lvmnodes : Refactored and tested. WIP pr is raised
[x] lvmsnapshots: Refactored and tested. WIP pr is raised

Controller plugin:

[ ] lvmnodes : Yet to start

PR:
https://github.com/openebs/lvm-localpv/pull/186

Pr is merged. Closing the issue.


Cannot download from URL

how to download using https url?
by the way Good Plugin,

Hello, thank you
You can inherit from DownloadFile and create your own implementation that downloads from your HTTPS endpoint. Then use this class with the RemotePdfViewPager to perform the download.
Other way is managing the download by yourself outside this library, copy the pdf to the sd card, then open it with a normal PDFViewPager

Hi thanks for advance,,
solved for download first and getPdfPathOnSDCard
for https not yet solved,,
thanks


Add Newsblock.io

:clap:

Do you have a write-up of your experience with React Native or a link to the mobile app?

right now, only this: https://github.com/bradoyler/newswatch-react-native

Got it, thanks!


lguf-brightness: Init at 2018-02-07

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ x NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@periklis Good work, we'd appreciate if the version number in the commit message was updated as well :-)

@GrahamcOfBorg build lguf-brightness

@GrahamcOfBorg eval

@GrahamcOfBorg build lguf-brightness

@periklis When I try executing this binary, I only get a new prompt and the status returned from last executed command is 255. Is this the expected behavior when not having that fancy piece of monitor as it's supposed to be used with?
I would believe that it is but it's not saying that much if I append either --help or --version either, it just returns 255 as status.

@etu this tools is currently working only if libusb detects an LG UltraFine monitor and has very rudimentary error messages.

@periklis Ok, thank you :slightly_smiling_face:
Just wanted to confirm that.


chore(frontend): Update dependencies safely

End-user friendly description of the problem this fixes or functionality that this introduces

[ ] Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below

Give a summary of what the PR does, explaining any non-trivial design decisions

Link of any specific issues this addresses

To run this PR locally, use the following command:
docker run -it --rm   -p 3000:3000   -v /var/run/docker.sock:/var/run/docker.sock   --add-host host.docker.internal:host-gateway   -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:54443e0-nikolaik   --name openhands-app-54443e0   docker.all-hands.dev/all-hands-ai/openhands:54443e0

We can update the dependabot yaml to group or exclude or whatever, if we have problems with some packages. For example, we separate there a few packages whose updates can mess things up or have in the past. Keeping them out of "all" group allows us to upgrade the rest more smoothly. If that helps here? Cc @amanape

Normally group updates shouldn't be an issue (though I prefer it if it were individual). It is just that this was left too long and it grouped some major changes (Vite v5 -> v6, React v18 -> v19) that I want to handle in a separate PR since they will require making additional changes in some of our components


Optimize search in stubs_ and replace push(make) to emplace C++17

@martinhaefner I think such commits will be useful for such a library.

Wow. I think, I'm getting old. Did not know about this...


Balance command doesn't listen to selector input

When running ./zenbot.sh balance binance.BTC-USDT zenbot returns error that I haven't provided my GDAX credentials. Seems like it is ignoring the selector option and trying to get the balance for the default selector in conf.js, gdax.BTC-USD

same here :(
no idea what could be the reason.


Fix for typo in documention.

Checklist

[ ] tests are passing with cargo test.
[x] documentation is changed or added
[x] commit message is clear

Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

Looks great, thanks a lot! 🎉


Only remove instance-specific listeners.

I ended up siding with a design where we just manually remove listeners in implementations that add them. Since listeners may be added to ref, or may be added to query, and since listeners require the name of the event in addition to the relevant callback to be removed, there didn't seem to be a good opportunity to generalize this cleanup.
Fixes #106

LGTM


default to 10km radius for places returned as points

feedback welcome if this is a good distance to default to
closes #96

Can you rebase this onto odes-client so the tests pass?


fix: intermitent error on multithread

I changed the ScopedContext class to avoid error on closing the scoped context on a diferent thread than it was created.
I had this error on my project when using aws sdk for SQS but I assume it will throw this error for any aws service.
This fix the issue mentioned in #70
I have also created a test that simulates the error, if it doesn't make sense to keep the test, let me know and I will remove it.

Any updates on this?


Cmake error

I'm trying to run CMake but it gives this error
CMake Error at CMakeLists.txt:2 (project):
No CMAKE_CXX_COMPILER could be found.
Tell CMake where to find the compiler by setting either the environment
variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
to the compiler, or to the compiler name if it is in the PATH.

nvm solved by
sudo apt-get update && sudo apt-get install build-essential


Not a clear mention of React 17 removing Timings from the Chrome Performance tab.

Is there any chance the documentation (https://reactjs.org/docs/optimizing-performance.html#profiling-components-with-the-chrome-performance-tab) can make a note about React 17 no longer using the Timing API from Chrome? It's super confusing to not see it, especially after seeing so many outdated blogs referencing Timings.

Oof, this should've just been completely removed. Want to send a PR removing it and adding a small note that it used to exist?


README improvements

Changes:

adds badge that points to https://registry.terraform.io/providers/airbytehq/airbyte/latest/docs
updates version in README to the latest released version to terraform registry

Feel free to use it as a suggestion.
For me, more important is to solve those issues:

it is helpful to go directly from repository to docs for terraform resources
if you publish new version, ideally, README should point to that version, not a few versions ahead

@airbytehq/platform-deployments @ThomasRooney can you check this change to README?

@ThomasRooney can we merge this?


Automated cherry pick of #3649: fix: agent-list show zone info

Cherry pick of #3649 on release/2.12.
#3649: fix: agent-list show zone info

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.12@d94401c). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.12   #3652   +/-   ##
==============================================
  Coverage                ?   6.96%
==============================================
  Files                   ?     500
  Lines                   ?   83851
  Branches                ?       0
==============================================
  Hits                    ?    5838
  Misses                  ?   77519
  Partials                ?     494

Flag
Coverage Δ

#aFlag
6.96% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/baremetalagents.go
5.75% <0%> (ø)

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 d94401c...2328853. Read the comment docs.

/lgtm
/approve


coming soon DeluxeSpeedView

new Speedometer

Coming Soon .......

its awesome my suggestions:
1: give option to change background color.
2: option to change all these three meter color (Green, yellow and red).
3: option to change color of white strips
4: option to change colors of label
5: options to change label "KM/H"

all these options are available
see Attributes in README
and also you can change any color in your code
like
speedView.setTextColor(Color.BLUE);
speedView.setLowSpeedColor(Color.BLUE);
speedView.setMediumSpeedColor(Color.BLUE);
speedView.setHighSpeedColor(Color.BLUE);
speedView.setMarkColor(Color.BLUE);

label "KM/H", and background Circle color : in the next version .....

ok thank you :) waiting for next version.

now, DeluxeSpeedView available .... :smile:
see Last Version Here.
@Baawaaji


can't compile ios build in github actions

Building ios with flutter errors in github actions, works in local but errors in the CI server from github actions
I already tried setting rust versions but nothing works
The following build commands failed: 2024-06-15T22:15:10.2055610Z              	PhaseScriptExecution [CP-User]\ Build\ SuperNativeExtensions\ Rust\ library /Users/runner/Library/Developer/Xcode/DerivedData/Runner-aixrnwwuerndpkeiqaoqortzrvbz/Build/Intermediates.noindex/ArchiveIntermediates/Runner/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/super_native_extensions.build/Script-B60078EBBFDC64C400A6EDB63F400D8C.sh (in target 'super_native_extensions' from project 'Pods')
i tried with this
rustc 1.70.0 (90c541806 2023-05-31) ruby 3.0.7p220 (2024-04-23 revision 724a071175) [x86_64-darwin22] 1.[15](https://github.com/getathelas/scribe-mobile/actions/runs/9532706651/job/26275112675#step:9:16).2 Xcode 15.0.1 Build version 15A507 Dart SDK version: 3.3.0 (stable) (Tue Feb 13 10:25:19 2024 +0000) on "macos_x64"
and changed rust version multiple times up and down, what is going on here ? we are blocked this packaged is being added as a transitive dependency by flutter quill.
https://pub.dev/packages/flutter_quill/changelog
I appreciate any guidance here, because I am out of ideas

Can you post here verbose build logs? This does not contain the actual error.

sure here is the complete log
https://jmp.sh/s/QDv09yzJbXh8gj9bB3AQ

I think this is the error ?
SEVERE: error[E0282]: type annotations needed for `Box<_>`
2024-06-16T05:17:53.0338530Z              SEVERE:   --> /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/time-0.3.25/src/format_description/parse/mod.rs:83:9
2024-06-16T05:17:53.0338670Z              SEVERE:    |
2024-06-16T05:17:53.0338790Z              SEVERE: 83 |     let items = format_items
2024-06-16T05:17:53.0338880Z              SEVERE:    |         ^^^^^
2024-06-16T05:17:53.0338950Z              SEVERE: ...
2024-06-16T05:17:53.0339230Z              SEVERE: 86 |     Ok(items.into())
2024-06-16T05:17:53.0339740Z              SEVERE:    |              ---- type must be known at this point
2024-06-16T05:17:53.0339940Z              SEVERE:    |
2024-06-16T05:17:53.0340310Z              SEVERE: help: consider giving `items` an explicit type, where the placeholders `_` are specified
2024-06-16T05:17:53.0340380Z              SEVERE:    |
2024-06-16T05:17:53.0340560Z              SEVERE: 83 |     let items: Box<_> = format_items
2024-06-16T05:17:53.0340730Z              SEVERE:    |              ++++++++
2024-06-16T05:17:53.0340810Z              SEVERE:
2024-06-16T05:17:53.0340950Z              SEVERE:    Compiling form_urlencoded v1.2.0
2024-06-16T05:17:53.0341060Z              SEVERE:    Compiling rand_chacha v0.3.1
2024-06-16T05:17:53.0341340Z              SEVERE: For more information about this error, try `rustc --explain E0282`.
2024-06-16T05:17:53.0349610Z              SEVERE: error: could not compile `time` (lib) due to 1 previous error
2024-06-16T05:17:53.0350090Z              SEVERE: warning: build failed, waiting for other jobs to finish...
2024-06-16T05:17:53.0350400Z              SEVERE: --------------------------------------------------------------------------------
2024-06-16T05:17:53.0350590Z              SEVERE: #0      runCommand (package:build_tool/src/util.dart:118:5)
2024-06-16T05:17:53.0350800Z              SEVERE: #1      RustBuilder.build (package:build_tool/src/builder.dart:139:5)
2024-06-16T05:17:53.0350910Z              SEVERE: <asynchronous suspension>
2024-06-16T05:17:53.0351210Z              SEVERE: #2      ArtifactProvider.getArtifacts (package:build_tool/src/artifacts_provider.dart:68:25)
2024-06-16T05:17:53.0351320Z              SEVERE: <asynchronous suspension>
2024-06-16T05:17:53.0351570Z              SEVERE: #3      BuildPod.build (package:build_tool/src/build_pod.dart:31:23)
2024-06-16T05:17:53.0351720Z              SEVERE: <asynchronous suspension>
2024-06-16T05:17:53.0352000Z              SEVERE: #4      BuildPodCommand.runBuildCommand (package:build_tool/src/build_tool.dart:48:5)
2024-06-16T05:17:53.0352110Z              SEVERE: <asynchronous suspension>
2024-06-16T05:17:53.0352370Z              SEVERE: #5      BuildCommand.run (package:build_tool/src/build_tool.dart:34:5)
2024-06-16T05:17:53.0352470Z              SEVERE: <asynchronous suspension>
2024-06-16T05:17:53.0352710Z              SEVERE: #6      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
2024-06-16T05:17:53.0352810Z              SEVERE: <asynchronous suspension>
2024-06-16T05:17:53.0353000Z              SEVERE: #7      runMain (package:build_tool/src/build_tool.dart:248:5)
2024-06-16T05:17:53.0363560Z              SEVERE: <asynchronous suspension>
2024-06-16T05:17:53.0364440Z              SEVERE: --------------------------------------------------------------------------------
2024-06-16T05:17:53.0364840Z              SEVERE: BuildTool arguments: [build-pod, ../rust, super_native_extensions]

also found this link
https://users.rust-lang.org/t/time-crate-compilation-error/111789

This should be fixed in current super_clipboard version (0.8.17).

Thanks @knopp overriding this dependencies seems to have worked, wondering why in my local didn't complain about this issue?


small warn

I have this compiler warn, which doesn't allow me to treat all warnings as errors
/usrsctplib/netinet/sctp_output.c:11009:24: warning: ‘strseq_m’ may be used uninitialized in this function [-Wmaybe-uninitialized]
     strseq_m->reserved = ntohs(0);
                        ^
../usrsctplib/usrsctplib/netinet/sctp_output.c:11005:22: warning: ‘strseq’ may be used uninitialized in this function [-Wmaybe-uninitialized]
     strseq->sequence = ntohs(at->rec.data.stream_seq);

Does the following patch
diff --git a/usrsctplib/netinet/sctp_output.c b/usrsctplib/netinet/sctp_output.c
index 6ee205a..f8c1060 100755
--- a/usrsctplib/netinet/sctp_output.c
+++ b/usrsctplib/netinet/sctp_output.c
@@ -10971,8 +10971,10 @@ sctp_fill_in_rest:
                 */
                if (old) {
                        strseq = (struct sctp_strseq *)fwdtsn;
+                       strseq_m = NULL;
                } else {
                        strseq_m = (struct sctp_strseq_mid *)fwdtsn;
+                       strseq = NULL;
                }
                /*-
                 * Now populate the strseq list. This is done blindly

silence the warning? I think that the warning is a false positive.

Any feedback?

@tuexen ooops! totally forgot about this. Will check and report back ASAP

Also got this and can't build at all. Trying to figure out how to disable "cc1: all warnings being treated as errors" now.

You can disable the feature that warnings are treated as error by using
./configure --disable-warnings-as-errors

or
cmake -DWERROR=OFF path/to/usrsctp

when configuring the build.
BTW: Does the above patch fix the warning for you?

This is probably the same as issue #114. The patch above fixes the build for the current "master" branch.


Requiring HTTPS (at least for the API)

If we are doing API authentication by snoopable things (cookies, tokens, passwords) we should run the API over HTTPS exclusively.

Agreed. Added https://github.com/ijl20/tfc_prod/issues/1. However I'm going to leave this open part of the API release milestone so we don't forget/ignore it...

Done (at least on smartcambridge.org/tfc-app1) by @abrahammartin
Still need to sort out https acces to tfc-app[2,3,4]. See https://github.com/ijl20/tfc_prod/issues/2


Very high numbers in PregeneratorMaxChunksPerTick causes server crash (forge)

Tested with 100 PregeneratorMaxChunksPerTick and the server stops with the error:
[Server Watchdog/FATAL] [net.minecraft.server.dedicated.ServerHangWatchdog]: A single server tick took 60.00 seconds (should be max 0.05)
Obviously that's an insane number, but OTG should probably set it to safe levels if it detects the number is set too high in the OTG.ini

For v8_r2, have set the maximum to 5. I've not seen any improvement past 3 myself.


multivolume paramak parts

The following multi volume paramak reactor only exports the center column and misses the multivolume stl blanket.
import paramak

center_column = paramak.RotateMixedShape(
    points=[
        (50, 600, 'straight'),
        (150, 600, 'spline'),
        (100, 0, 'spline'),
        (150, -600, 'straight'),
        (50, -600, 'straight')
    ],
    name='center_column'
)

blanket = paramak.RotateSplineShape(
    points=[
        (600, 0),
        (600, -20),
        (500, -300),
        (400, -300),
        (400, 0),
        (400, 300),
        (500, 300),
        (600, 20)
    ],
    name='blanket',
    rotation_angle=40,
    azimuth_placement_angle=[0, 45, 90, 135, 180, 225, 270, 315],
)

my_reactor = paramak.Reactor([blanket, center_column])

my_reactor.export_dagmc_h5m()
my_reactor.export_brep('brep_filename.brep')
volumes = gmsh.model.occ.importShapes('brep_filename.brep')
print(volumes)
>>>>volumes [(3, 1), (3, 2), (3, 3), (3, 4), (3, 5), (3, 6), (3, 7), (3, 8), (3, 9)]

volumes_with_tags from a paramak assumes each shape is just one volume
A method of detecting multi volumes should and getting the properties of each volume in the shape should be added to export_dagmc_h5m

This is now solved but some tests should be added to keep it working

tests added


Patch update frequency and script

Hello, this pr adds two things

Decreased update frequency to 3 days from 6 hours.
Fixed bug where date isn't handled as expected.

Happy days @molangning :)


Update to latest Gradle Android Tools (2.1.3)

Otherwise this will happen in AS:

Error:Android plugin 2.1.0 is not compatible with Gradle 2.14.1.

Travis seems flaky again, it can't find certain artifacts ... also having the problem with other projects

I've heard that the Android SDK repos are having troubles today.
Does the error happen when using the library, or just when compiling it?

Which error? The one I quoted originally happens when I open the project in Android Studio. The one from Travis happens also for me with trying to get Android 24 sdk.

The original error quoted, yeah.
I suppose the reason I'm not getting the error is because I was running an older version of Android Studio.

Could be I'm running beta2 of 2.2.0. Nonetheless Gradle 2.14.1 support was 'added' in 2.1.3

This one is now green @dlew

Thanks!


Expand/Collapse arrow is impossible to spot on selected transforms

Update: This only happens when the Stretch Width setting for the two-tone background is disabled.

Hey there,
In the upcoming restructure, I've removed the stretch width. I think I originally added this in when I wasn't really thinking smart about how to handle drawing content. It's a useless feature to have unless specified widths could be assigned.
After the next release is  published all foldout/expand icon issues with two-tone or prefix styles should be fixed. I'll keep this open until then, just to make sure that it's all clear

Hierarchy Decorator v0.7 has just been released with fixes to this issue 🙂


Content iteration: Link guidance

Acceptance Criteria:

[ ] Sync with Dev and Design
[ ] Research and consulting other design libraries
[ ] How to use guidance
[ ] Accessibility guidelines
[ ] Inclusive language
[ ] Descriptive text for images
[ ] Translation & Localization
[ ] Bilingual review – content design
[ ] Ensure consistency: ordering, terminology, high level voice/tone/style
[ ] Final review

Update link guidance to include guidance on:

opening links in new tab (avoid with some exceptions)
sharing of links behind the firewall (avoid)
English only/French only links

Discussion thread
gov.UK guidance to consider
Draft research


Feat: improve pioneers/influencers

Pioneers endpoint will benefit of having:

Preview option. Will return only 3 profiles at random out of the 100 most pioneer users.
Friends/Following/Follower reach setting. See the scores of those in your WoT.
All time / 24h / Last Month. We should explore Redis Timeseries? We can also generate daily, using cronjob like tasks.
Optionally: rename "pioneers" to "influencers" to match design/UI.

https://github.com/pubky/pubky-nexus/pull/234