Please rename pwsh to PowerShell Core 1.0, not 6.0

Please rename "PowerShell Core 6.0" to "PowerShell Core 1.0" to avoid confusion and disappointment.
Reasons:
The PowerShell Core 1.0 executable has been renamed to "pwsh."
Pwsh is very different and limited in comparison to Windows PowerShell on Windows.
Pwsh DSC is going to be very different than DSC on Windows PowerShell.
Pwsh really is a 1.0 product (i.e., new), it's not a 6.0 product (i.e., with a decade of refinement).
Going with version 1.0 follows the pattern in version number changes for .NET and ASP.NET when they went to .NET Core 1.0 and ASP.NET Core 1.0 (they did not go to version 5.0, see http://www.hanselman.com/blog/ASPNET5IsDeadIntroducingASPNETCore10AndNETCore10.aspx).
Using the 1.0 version number will help to emphasize and explain the difference between Windows PowerShell and PowerShell Core.  This helps to get the message out about cross-platform .NET Core in general, which was part of the reason for the version number choices for .NET Core and ASP.NET Core.
99% of admins and developers will assume that pwsh builds on top of and enhances Windows PowerShell 5.1, which is wrong.  Using the 6.0 version number is going to cause confusion and disappointment.  Changing the version number to 1.0 will help reduce this.  There will inevitably be bugs and limitations in something as complex, cross-platform and ambitious as pwsh 1.0, but by using the 1.0 version number, it will reduce the disappointment because "after all, it's a new 1.0 product..."  After a year of bug squashing, pwsh 2.0 can be released to reassure enterprise customers.
This will also help to protect the reputation of Windows PowerShell when there are complaints and griping in blogs, forums, twitter, etc. about the bugs in pwsh 1.0.  Consider, which would be less bad: complaints about "PowerShell 6.0" or complaints about "PowerShell Core 1.0"?  Again, very few people are going to be careful and precise in their distinction between Windows PowerShell and PowerShell Core, they are just going to say "PowerShell."  Remember, those of us following the development of pwsh are a very tiny percentage of the overall IT market; so what might seem like a "big" version number change to us (here in our tiny bubble of an echo chamber on GitHub) will actually be an almost unnoticed change to the outside world.
Finally, what if Microsoft changes it's mind in the future about Windows PowerShell and wants to release a new major update to it?  By having separate version tracks, someday there could be a "Windows PowerShell 6.0" without causing more confusion.  A few years from now, if pwsh only has a tiny market share, pwsh will be deprecated and axed, but Windows PowerShell will still be popular and growing strong.
So, please consider renaming pwsh to "PowerShell Core 1.0" before it goes live, it's definitely not too late, there's still plenty of time.
Thanks,
Jason

Quoting @joeyaiello
https://blogs.msdn.microsoft.com/powershell/2017/07/14/powershell-6-0-roadmap-coreclr-backwards-compatibility-and-more/

Note: while PowerShell Core 6.0 is cross-platform, there is also a PowerShell Core 5.0/5.1 released exclusively as part of Nano Server.

Naming to PowerShell Core 1.0 would be confusing in that respect.
Personally I think 6.0 is the better choice as it shows a linear progression of PowerShell regardless of the underlying framework.

Hi @thezim:
Good point about Nano, thank you.
Note that PowerShell is not a part of the Nano base container image anymore, and Nano installations as a percentage of Server installations is extremely small, and as a percentage of total machines with PowerShell installed, it is a tiny, tiny fraction of that. Besides, the future of PowerShell on Nano is pwsh, assuimg DevOps-style developers need PowerShell on Nano containers at all (they'll need it on their workstations and CI/CD servers, but perhaps not on the final Nano images outputted).
For "linear progression", it's only a progression in version numbering, not in actual capabilities or for backwards compatibility.  Pwsh is not a superset of Windows PowerShell 5.1, it's a smaller subset.  This is where the confusion and disappointment will enter as people "upgrade" from 5.1 to 6.0.  If the cmdlets, parameters and other features were the same in pwsh, then I agree that the underlying framework would be irrelevant, but they're not the same at all.
Thank you for voting!

With upgrade from 5.1 to 6.0 customers expect enhancements in the language. In fact, we've lost a lot of functionality on the contrary. We're just misleading people.
Of course, the internal version must be 6. But the product we'd better rename. I would even remove the version number from the product name to show people that this is the first milestone - PowerShell Core Threshold.

PowerShell Core is not really a smaller subset of Windows PowerShell. The built-in cmdlets, language, and public APIs have not been simplified or fundamentally changed in a way that reduces functionality. In fact, many cmdlets like Invoke-WebRequest and Invoke-RestMethod are getting awesome enhancements in 6.0.
Are there breaking changes? Yes.
Are there breaking changes to some public APIs or language behaviors? Yes
Is that enough to justify it being a 1.0 product? Not really.
From Semantic Versioning

MAJOR version when you make incompatible API changes,

A 6.0 version meets that version requirement.
The only functionality I've seen reduced is that PowerShell deprecated features like PSSnap-In and Workflow were removed. This is perfectly fine to do in a progressing API. It just means that some 3rd party cmdlets need to be updated to support 6.0, hence the MAJOR increment.
There are some issues still to be worked out on backwards compatibility which may be what gives you that subset feel. I don't think backwards compatibility though justifies starting over with 1.0.

I think a major version is fine. php4 to php5 had some of the same concerns regarding gains and losses and certainly things written for 5 didn't always run on 4 and vice versa. But it was still PHP. It, too, went through a massive underlying engine change. Not to compare PHP to my beloved PowerShell, but it is a language peer of sorts.
Outside the built-in modules is where the greatest difference between Windows PowerShell 5 and PowerShell Core 6. Most of the core language features and cmdlets are compatible or only require minor tweaking. Not enough to warrant a completely new version base, IMO.

I work in enterprise and last year from time to time I tried to use PowerShell Core for everyday routine tasks. I can definitely say it doesn't work. After forcing to Utf8, I won't even be able to work properly in the interactive session.
I see how much progress has been made over the past year and proud of my bit contributions, but for us it's still a toy - nobody's going to let us use even CoreFX in a production environment, not that PowerShell Core. We have no confidence. Many scenarios in Corefx are still not tested. In PowerShell Core, even the test coverage is less than 60 percent actually even less. We do not have tests for remote scenarios in general, and for remote scenarios across different platforms, all the more.
You'll be interested to know that of the 297 cmdlets we have 247 for Windows - 17% loss and 205 for Unix - 40% loss.
We need to distinguish between developers and users. For the first, we have to be internal 6.0. For the second, we should not focus on this "6.0", which gives rise to unjustified expectations. Nobody advertises Windows 6.0, 6.1, 6.2 - we know them under different names.

i'm working on Linux with PS Core over the last months....
I can only consider to try it (Ubuntu Desktop+ VSCode + Debugging)!
It does not feel like 6.0! It is more like 1.0!
I know that more projects (VSCode, Powershell Plugin, Powershell Editor Services) are involved here but for the end user only the full stack (Runtime, Editor and Debugger) counts...
but i'm happy if we are able to push the quality of the entire Linux Development Stack to a real 6.0 feeling...

The feedback is appreciated and we went through the same discussion internally before settling on calling it PowerShell Core 6.0.  At this time, we are not considering changing the version number.  There are pros/cons to both 6.0 and 1.0, however, as an engine and platform, PSCore6 is a superset of Windows PowerShell 5.1 and for some cmdlets, this is also the case with addition of new capabilities.  Certainly PSCore6 at this time has less cmdlet coverage than Windows PowerShell 5.1, but that will change over time.


Add Python 3.8 to classifiers

According to https://github.com/tensorflow/tensorflow/issues/33374#issuecomment-595341808 nightly and TF 2.2 support Python 3.8.

If we're doing this, let's also remove Py2 and Py3.4 from here

Done


docker daemon failed to start after installing vDVS plugin

This issue was reported on the slack channel for docker-volume-vsphere. Posting the details from the information posted by the customer on the slack channel.
Issue as reported by customer:
"Just tried hatchway for the first time.  After running the following command the docker daemon bombed out and will no longer restart even after rebooting the vm:"
docker plugin install --grant-all-permissions --alias vsphere vmware/docker-volume-vsphere:0.19`

Journalctl logs:
97a5348936b980a825af7795bb7494b72fe9e4df6dec3d458a328c/config.json: open /var/lib/docker/plugins/15fdae39e197a5348936b980a825af7795bb7494b72fe9e4df6dec3d458a328c/config.json
: no such file or directory
Dec 10 22:38:06 docker-client systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Dec 10 22:38:06 docker-client systemd[1]: Failed to start Docker Daemon.
Dec 10 22:38:06 docker-client systemd[1]: docker.service: Unit entered failed state.
Dec 10 22:38:06 docker-client systemd[1]: docker.service: Failed with result 'exit-code'.```

@shuklanirdesh82 can you please take a look?

Feel free to reach out to me if any further info is required, I will keep the affected docker host around in case the issue is not easily replicated.

@james65535 can you upload the plugin logs if any (/var/log/docker-volume-vsphere.log). SHouldn't this issue be raised on Moby, if the docker daemon is down.
docker plugin install --grant-all-permissions --alias vsphere vmware/docker-volume-vsphere:0.19
0.19: Pulling from vmware/docker-volume-vsphere
9bb07d39b032: Download complete
Digest: sha256:278cf4ffc37d5dacddab470d1fe4a55a3d93c3368b8f2ff8f6a0675ff49f8179
Status: Downloaded newer image for vmware/docker-volume-vsphere:0.19
Installed plugin vmware/docker-volume-vsphere:0.19
This is what I got with,
docker version
Client:
Version:      17.09.0-ce
API version:  1.32
Go version:   go1.8.3
Git commit:   afdb6d4
Built:        Tue Sep 26 22:42:38 2017
OS/Arch:      linux/amd64
Server:
Version:      17.09.0-ce
API version:  1.32 (minimum version 1.12)
Go version:   go1.8.3
Git commit:   afdb6d4
Built:        Tue Sep 26 22:41:20 2017
OS/Arch:      linux/amd64
Experimental: false

Thanks for the follow up, /var/log/docker-volume-vsphere.log doesn't exist. Also, I cannot do a docker version as the server is offline.  I note your comment about Moby, I'm fine with closing this issue if its not helpful for the project; my initial intent was to just discuss it in slack.

Also, I cannot do a docker version as the server is offline.

@james65535 It seems docker is not configured properly.
Closing this issue, let's reopen if the issue persists even after configure docker correctly.

@ashahi1 can you please perform plugin installation on the photon 1.0 VM with docker 1.13.1?
Here is the detail that I know of:
docker: 1.13.1
OS: Photon 1.0 (4.4.62-1.ph1-esx)
uname -a `Linux docker-client 4.4.62-1.ph1-esx #1-photon SMP Wed Apr 26 23:41:32 UTC 2017 x86_64 GNU/Linux`


allow additional header input for the sd-jwt vc issuer

Fixes #16

FTR
a new version of the npm package has been released which includes the above fix. You can find it at<EMAIL_ADDRESS>


💄style : improved testimonial wall responsiveness

What is the change?
Improved the Testimonial wall responsiveness.

Fixed the write-testimonial div unresponsiveness discussed in issue #986.
Fixed the whole Testimonial wall UI for mobile view discussed in issue #982, adjusting the width of blockquotes.

Related issue?
close: #982 #986
How was it tested?
Through localhost.
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelines while contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Did you lint your code before making the Pull Request?
[x] Have you made corresponding changes to the documentation?
[x] Your submission doesn't break any existing feature.
[x] Have you tested the code before submission?

Screenshots or Video:
https://user-images.githubusercontent.com/75828760/129140607-49d83239-7975-4a3d-8064-80e5f48ae740.mp4

Good work.
Please join ALPHAVIO discord channel. You can be potential mentor for our next projects we submit to upcoming open-source events.
Discord channel link in project README, I give updates there.

Thank you so much.


luarocks 2.3.0 can't find loadcaffe

am i doing something wrong?  trying to follow the README to install the package.
$ luarocks install loadcaffe

Error: No results matching query were found.

$ luarocks --version
/usr/local/bin/luarocks 2.3.0
LuaRocks main command-line interface

nevermind; figured it out.  missed this part of the make

Python modules have been installed and Homebrew's site-packages is not
in your Python sys.path, so you will not be able to import the modules
this formula installed. If you plan to develop with these modules,
please run:
  mkdir -p /Users/xxx/Library/Python/2.7/lib/python/site-packages
  echo 'import site; site.addsitedir("/usr/local/lib/python2.7/site-packages")' >> /Users/xxx/Library/Python/2.7/lib/python/site-packages/homebrew.pth


Added JSON import function

Import your nodes and edges from an external JSON document.
The JSON object must be like this:
{    "Sophie ": ["Albert", "Mike"],    "Mike":["Sophie", "Albert"] }
When importing the edges you loop through all the keys of the JSON object (Souce Nodes) and read the value of the JSON object in that key, that value must be an array of Destination nodes. You loop through all the Destination nodes and add an edge from the Source Node to the Destination Node

Thanks ✨


getStats() freezes Edge

the getStats calls somehow "freeze" Edge. Unclear whether it is the stats themselves or something in the drawing code. Currently deactivated by looking at the user agent

to re-activate revert 9b0d5d65bda0c89404ace47da2b7e626b8123b11

definetly in the drawing function, somewhere in drawSingleReport. Still works when returning before "Updates the graph". Problem seems to be in updateEnddate... probably the repaint function.

"not responding due to a long running script"... oh yes... :-/

https://github.com/fippo/webrtc-externals/blob/93ff1f02b09e3fab740ee255e9c82158c1925beb/webrtc-internals.js#L756-L768
is suspect... probably taking very long for some reason.

deactivating the drawTimeLabels fixes the freeze issue. So its something about the data that makes that loop go crazy

doesn't seem to be related to the data. Just doing this 80 times a second seems too much for Edge...


Is it possible to create a sandboxed package environment with vcpkg?

I'm trying to freeze the dependencies of a few projects of mine, which have been using a single vcpkg to manage the dependencies. This vcpkg instance also manages all the projects on the system.
Goal
I want a solution similar to python's venv where Project A and B could use separate sets of dependencies with different versions.
Something like Project A depends on
libA 1.0
libB 2.0
libC 3.0

but Project B depends on
libA 5.0
libB 6.0
libC 7.0

Questions
Given two projects, could I configure two separate working copies of the vcpkg as sandboxes, so that when I open the two projects in Visual Studio, VS knows which sandbox to use for each project?

I think that depends on how you consume the libs from vcpkg. If using the libs with cmake, you can use two vcpkg instance, since everything setting via CMAKE_TOOLCHAIN_FILE. Howver, it using them with MSbuild then only one instance can be used at once, since only have one vcpkg.user.targets under %APPDATA%..\Local\vcpkg. @kakyoism, Is the answer you want?

I think that depends on how you consume the libs from vcpkg. If using the libs with cmake, you can use two vcpkg instance, since everything setting via CMAKE_TOOLCHAIN_FILE. Howver, it using them with MSbuild then only one instance can be used at once, since only have one vcpkg.user.targets under %APPDATA%..\Local\vcpkg. @kakyoism, Is the answer you want?

When you say "only one instance at once (at a time?)" with MSbuild, do you imply that if I invoke MSbuild sequentially for two projects using two vcpkg instances, and update vcpkg.user.targets and other parameters configured under %APPDATA%..\Local\vcpkg accordingly, then I'll be fine?
I know this sounds a hack but in reality without this sandbox feature, multiple non-CMake-based projects are essentially unable to work with vcpkg safely. This is a serious drawback, IMHO.
Are there any workarounds?

There are two easy ways to sandbox individual MSBuild instances:
https://github.com/microsoft/vcpkg/blob/master/docs/users/integration.md#linking-nuget-file and https://github.com/microsoft/vcpkg/blob/master/docs/users/integration.md#export-command
With the first, we will generate a NuGet package that points to the specific absolute path on your machine. However, these paths may not be correct for another user's machine.
With the second, we create a shrinkwrapped NuGet package containing all the binaries you select from that particular instance; these can then be added to an MSBuild project and passed around to easily restore exactly those dependencies on any machine.
Finally, there is a more difficult route: you could manually edit the vcxproj files and set the VcpkgRoot MSBuild property to point into a git submodule of vcpkg. This may be made easier by the new Vcpkg Property Page in VS.

There are two easy ways to sandbox individual MSBuild instances:
https://github.com/microsoft/vcpkg/blob/master/docs/users/integration.md#linking-nuget-file and https://github.com/microsoft/vcpkg/blob/master/docs/users/integration.md#export-command
With the first, we will generate a NuGet package that points to the specific absolute path on your machine. However, these paths may not be correct for another user's machine.
With the second, we create a shrinkwrapped NuGet package containing all the binaries you select from that particular instance; these can then be added to an MSBuild project and passed around to easily restore exactly those dependencies on any machine.
Finally, there is a more difficult route: you could manually edit the vcxproj files and set the VcpkgRoot MSBuild property to point into a git submodule of vcpkg. This may be made easier by the new Vcpkg Property Page in VS.

Wow. All these routes look promising. I'll give them a try.
@ras0219-msft  Thanks a lot! Close now and will reopen it if I'm blocked again.


Redeploy

Change twillio stuff with new deployment? No contact from client regarding twillio billing as of yet.

Also will need to wipe existing database

Redeployment complete and database wiped!


FIXED THE SIDE ICON ISSUE

the icons are on top of everything even if the screen is smaller
ISSUE #787

@sanjay-kv please look into this its not merging


distributed-process-* test failures

distributed-process-extras-<IP_ADDRESS>
Node Monitoring:
  Death Notifications: [Failed]
ERROR: thread blocked indefinitely in an MVar operation

         Test Cases  Total
 Passed  3           3
 Failed  1           1
 Total   4           4
Test suite PrimitivesTests: FAIL

Ping @facundominguez

Also this package:
distributed-process-client-server-<IP_ADDRESS>...

tests/TestManagedProcess.hs:18:8:
    Could not find module ‘MathsDemo’
    Use -v to see a list of the files searched for.

tests/TestManagedProcess.hs:19:8:
    Could not find module ‘Counter’
    Use -v to see a list of the files searched for.

tests/TestManagedProcess.hs:20:18:
    Could not find module ‘SafeCounter’
    Use -v to see a list of the files searched for.

tests/TestManagedProcess.hs:28:8:
    Could not find module ‘TestUtils’
    Perhaps you meant Test.Util
    Use -v to see a list of the files searched for.

tests/TestManagedProcess.hs:29:8:
    Could not find module ‘ManagedProcessCommon’
    Use -v to see a list of the files searched for.

I'm allowing these test suites to fail since these versions are already on stackage since yesterday.


ios: Prevent mix build phases

Reference
SDK-XXXX -- .
Summary

Prevent mixed build phases.
Motivation

Without fix

With fix

Type Of Change

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

Testing Instructions

cc @BranchMetrics/saas-sdk-devs for visibility.

https://github.com/apache/cordova-lib/pull/933


MTD vrs FTD builds, and Makefile.am If/Else/Endif issues

As discussed in #1467 (Changes to Support IDEs)
These problems are intertwined and share a number of common traits and are being addressed together in a single commit, sadly I don't see a way to break this up.
PROBLEM 1
In src/core/Makefile.am - lists numerous IF/ELSE/ENDIF which choose which files are added or not added to a specific library. While IDEs can provide some level of exclusion, they are not that flexible.
PROBLEM 2
Need both --enable-cli-ftd --enable-cli-mtd, and likewise --enable-mtd
Need granularity such that CLI can be built with MTD only, And NCP can be built using MTD or FTD
Current ./configure solution is: FTD for both, or FTD for Neither
(there are no details for this item below)
PROBLEM 3
Linking the CLI application with the CLI library, and NCP with the NCP library
Currently when the CLI (or NCP) library is built - it is built using only one of the two internal header configurations, ie: FTD - with all of the structure/class elements, or  MTD with various structure/class elements removed.
This causes problems with link time optimization and static code analysis.
PROBLEM 4
Appvayor.
I do not have access to the version of Visual Studio used here, I have Visual Studio 2015, but the project appears to use an older version of Visual Studio, my experience has been:  VS2015 will upgrade the projects... this is a one-way process
if someone can advise, it would be helpful.
DETAILS FOLLOW
================================================
PROBLEM 1 - details
a)  Makefile.am files should not longer use If/Else/Endif type constructs to add/remove files from a build.
Instead, the makefile should generally compile everything.
For example some IDEs - such as Eclipse CDT based IDEs - compile all files ".c" and ".cpp" and are of the view - if the file does not belong, or should not be compiled then it should not be present in the directory.  While other IDEs have other schemes, in IDE land - there does not exist a single common way to exclude/include files based upon the build configuration.
Solution: Where required, appropriate #if/#else/#endif type statements need to be added to various source files so that the entire quote "translation unit" - effectively becomes a pseudo-empty translation unit.
A number of files did not have, or do not #include "openthread-config.h" - which is required to support the #if/#else/#endif described above, this was added to a number of files.
Result: A number of places additional tests must be applied to the conditional.
For example in several places, the #if SOMETHING becomes: #if SOMETHING && OPENTHREAD_FTD
PROBLEM 2 Details
This is described above, not expanded here.
PROBLEM 3 Details
When the NCP or CLI library is built, it uses the internal thread headers, and thus structures and class members.
When the NCP or CLI application is linked, the openthread library effectively uses a different set of header files (either MTD or FTD configuration) - the net result is these internal structures are different.
What is needed is the CLI library must be built in FTD mode, and MTD mode so that it matches the openthread library, these differences are flagged as errors by compilers and static code analysis tools that do "link-time-optimization"
Thus, in all cases we have added two command line defines:
When building anything-FTD,  "-DOPENTHREAD_FTD=1"  must be defined
When building anything-MTD, "-DOPENTHREAD_MTD=1" must be defined
PROBLEM 4 - No access to Visual Studio OLD?
I have Visual Studio 2015 - I do not have older versions, I cannot make any of the required changes to support the above for appvayor.
I believe the change is simple, because I believe the Windows solution only builds the FTD configuration.
In the library build projects add:  -DOPENTHREAD_FTD=1

Resolved by #1620.

@jwhui @DuaneEllis-TI
Just curious, does the file "dhcp6_client.cpp" need the "#if OPENTHREAD_ENABLE_DHCP6_CLIENT" macros?  Or has it been decided that the dhcp client should always be present?
Thanks.

@mstamer, good catch!  DHCPv6 Client should be optional.  Would you like to submit a PR?

Will do.

@jwhui  - Agree, it probably should.
This file also will need to include 'openthread-config.h'
it is an example of several that do not - perhaps it does via other headers

missed that info in the ticket (#1663)...  Do you prefer I add that info to this ticket as well?

@mstamer, I think it makes sense to make the #include change in the same PR.


Migratuion from permissionex (sponge)

Hey there,
Today I want to test out luck perms and try to migrate over to it. Every time i try to migrate it. It throw back this error.
https://hastebin.com/cavulapozo.md

It's a PEX bug.
Remove the "menoe" entry from your permissions file.


Proposal: Feature flags for Additional functionalities

In line with #158 & #165, features such as image,drawing,chart support can be moved to a single/multiple feature flags as per the broad consensus of the community. This would reduce the size, execution times and memory footprints of the binary and can in general be good for flexibility of the system. Note: Same is being implemented with Calamine library which can be investigated for replication.

@agentjill
Thank you for your suggestion.
I agree with your response to features.
Let's definitely do it.

Absolutely worth it. As written in a guide:

This is undoubtedly a very useful feature to have for some applications, but in the context of rust-analyzer we don’t need it. Simple env_logger-style filtering would be enough.
Once you identify a similar redundant dependency, it’s usually enough to tweak features field somewhere, or to send a PR upstream to make non-essential bits configurable.

If we check the compilation time with cargo +nightly build -p YOUR_PACKAGE --timings --release, we may see that these image encoders/decoders take a huge time, even though in my project I don't really them. The image to be inserted into a cell is just a include_bytes!("some.jpg") and is already encoded.

@xamgore
Thanks for the useful information!
I will try to proceed with this correspondence as soon as possible.

The issue can be fixed in many ways.
The first is to proxy all the image codec features through umya-spreadsheet. So if someone needs png they will turn on the feature umya-spreadsheet = { version = "*",  features = ["image/png"] }. Most of the time, people insert only one concrete, static image, so... that's enough for them.
On the other hand, when people insert an image from a previously defined set (for example, organization stamps which are meant to be printed on paper), usually those images have the same dimensions, to prevent bloating. Which means a new method could be made:
#[cfg(feature = "image")]
pub fn new_image(&mut self, path: &str, marker: MarkerType) {
    let path = std::path::Path::new(path);
    let img = image::open(path).unwrap();
    let (width, height) = img.dimensions();                      // 👈 the image crate is only used here
    self.new_image_with_dimensions(path, height, width, marker)  //    so we just pass dimensions
}

pub fn new_image_with_dimensions(&mut self, path: &str, height: i64, width: i64, marker: MarketType) {
    let mut file = File::open(path).unwrap();
    let mut buf = Vec::new();
    file.read_to_end(&mut buf).unwrap();    // caution: lacks std::read::BufReader
    picture.set_image_data(buf);
    // ...
    one_cell_anchor.get_extent_mut().set_cy(height as i64 * 9525);
    one_cell_anchor.get_extent_mut().set_cx(width as i64 * 9525);
    one_cell_anchor.set_picture(picture);
}

Also, people may want to include_bytes!("picture.jpg") or pass an in-memory buffer, which they got from a user or dynamically download on the Internet. So the method could become even more straightforward, letting the user do I/O themselves:
pub fn new_image_with_dimensions<B: Into<Vec<u8>>(&mut self, buf: B, height: i64, width: i64, marker: MarketType) {
    picture.set_image_data(buf.into());
    // ...
    one_cell_anchor.get_extent_mut().set_cy(height as i64 * 9525);
    one_cell_anchor.get_extent_mut().set_cx(width as i64 * 9525);
    one_cell_anchor.set_picture(picture);
}

Don't you mind helping me with a PR?

@MathNya if you wish to include this, you can create a feature branch. This will facilitate development of the necessary feature which could be merged on suitable time.


.gitignore files from vendor directory causing issues

Looks like some of my deps did not land in my upstream commit. Taking a closer look it seems the .gitignore files from the vendor directories are causing issues.  Checkout the following session:
Vendor the consul api:
confd $ gb vendor github.com/hashicorp/consul/api

Notice nothing new shows up in the vendor dir:
confd $ git status
On branch master
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   .gitignore

Untracked files:
  (use "git add <file>..." to include in what will be committed)

	bin/

no changes added to commit (use "git add" and/or "git commit -a")

Find all .gitignore files
confd $ find ./ -name .gitignore
.//.gitignore
.//vendor/src/github.com/hashicorp/consul/.gitignore
.//vendor/src/github.com/hashicorp/consul/website/source/.gitignore

Remove them:
confd $ rm vendor/src/github.com/hashicorp/consul/.gitignore
confd $ rm vendor/src/github.com/hashicorp/consul/website/source/.gitignore

Check git status again. Notice that the vendor dir changes are picked up:
confd $ git status
On branch master
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)
  (commit or discard the untracked or modified content in submodules)

	modified:   .gitignore
	modified:   vendor/src/github.com/hashicorp/consul (modified content)

Untracked files:
  (use "git add <file>..." to include in what will be committed)

	bin/

no changes added to commit (use "git add" and/or "git commit -a")

This is really a problem with my git setup, but it might bite people down the road.

I think #126 should address this, and if not we'll come up with a better
idea.
On Tue, 26 May 2015 08:35 Kelsey Hightower<EMAIL_ADDRESS>wrote:

Looks like some of my deps did not land in my upstream commit. Taking a
closer look it seems the .gitignore files from the vendor directories are
causing issues. Checkout the following session:
Vendor the consul api:
confd $ gb vendor github.com/hashicorp/consul/api
Notice nothing new shows up in the vendor dir:
confd $ git status
On branch master
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
modified:   .gitignore

Untracked files:
(use "git add ..." to include in what will be committed)
bin/

no changes added to commit (use "git add" and/or "git commit -a")
Find all .gitignore files
confd $ find ./ -name .gitignore
.//.gitignore
.//vendor/src/github.com/hashicorp/consul/.gitignore
.//vendor/src/github.com/hashicorp/consul/website/source/.gitignore
Remove them:
confd $ rm vendor/src/github.com/hashicorp/consul/.gitignore
confd $ rm vendor/src/github.com/hashicorp/consul/website/source/.gitignore
Check git status again. Notice that the vendor dir changes are picked up:
confd $ git status
On branch master
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
(commit or discard the untracked or modified content in submodules)
modified:   .gitignore
modified:   vendor/src/github.com/hashicorp/consul (modified content)

Untracked files:
(use "git add ..." to include in what will be committed)
bin/

no changes added to commit (use "git add" and/or "git commit -a")
This is really a problem with my git setup, but it might bite people down
the road.
—
Reply to this email directly or view it on GitHub
https://github.com/constabulary/gb/issues/130.

@davecheney Hmm.. this does not really work for me. Looks like it does not support vendoring just the bits I need. For example, I can't grab the consul/api package:
$ gb vendor fetch github.com/hashicorp/consul/api
Cloning into '/var/folders/ds/jbxmdvmx0rj1z7vc4br6j97h0000gn/T/gb-vendor-532109454'...
fatal: repository 'https://github.com/hashicorp/consul/api/' not found

But this works:
gb vendor fetch github.com/hashicorp/consul
Cloning into '/var/folders/ds/jbxmdvmx0rj1z7vc4br6j97h0000gn/T/gb-vendor-964976189'...
remote: Counting objects: 15005, done.
remote: Compressing objects: 100% (41/41), done.
remote: Total 15005 (delta 15), reused 0 (delta 0), pack-reused 14964

Yup, cloning a path under a repo isn't supported yet, but it will be
shortly. There is a spot in the manifest for a path element.
I'll try to fox that before I merge in #126
On Tue, 26 May 2015 09:26 Kelsey Hightower<EMAIL_ADDRESS>wrote:

@davecheney https://github.com/davecheney Hmm.. this does not really
work for me. Looks like it does not support vendoring just the bits I need.
For example, I can't grab the consul/api package:
$ gb vendor fetch github.com/hashicorp/consul/api
Cloning into '/var/folders/ds/jbxmdvmx0rj1z7vc4br6j97h0000gn/T/gb-vendor-532109454'...
fatal: repository 'https://github.com/hashicorp/consul/api/' not found
But this works:
gb vendor fetch github.com/hashicorp/consul
Cloning into '/var/folders/ds/jbxmdvmx0rj1z7vc4br6j97h0000gn/T/gb-vendor-964976189'...
remote: Counting objects: 15005, done.
remote: Compressing objects: 100% (41/41), done.
remote: Total 15005 (delta 15), reused 0 (delta 0), pack-reused 14964
—
Reply to this email directly or view it on GitHub
https://github.com/constabulary/gb/issues/130#issuecomment-105334128.

#126 will close this issue. I'll create a separate issue for https://github.com/constabulary/gb/issues/130#issuecomment-105334128


provide a config interface in the server

An interface for backend is needed.
Currently, to use a specific backend, the only way is extending the Server class. We should provide a backend interface following the principle composition over inheritance.

ref #7


fix(MyReactFormVisitor): Make Radio button sample generic

Issue #40
Fixes #40

Will / should some of that code be in the concerto-ui-core package? Or is having that part of the user code a better option?

Will / should some of that code be in the concerto-ui-core package? Or is having that part of the user code a better option?

I don't think so, MyReactFormVisitor is designed to demonstrate how a user can extend the built-in ReactFormVisitor with custom rendering code. I also think that the default rendering for Enums to Dropdowns is the right default option.


Issue with loading gps data, loader expects a not empty 'direction'

I think the issue lies in io.py in the schema definition in line 230
'direction': (not_callandtext and r.direction is None) or r.direction in ['in', 'out'],

should be
'direction': (not_callandtext and r.direction in [None, '']) or r.direction in ['in', 'out'],

I've created a pull request #9  with my idea of a fix

Is there any problem with the visualization data? I am trying to run the notebook in the demo folder (code below), but it does not display anything.
import os
viz_path = os.path.dirname(os.path.realpath(name)) + '/viz'
bc.visualization.export(U, viz_path)
from IPython.display import IFrame
IFrame("/files/viz/index.html", "100%", 700)
Thanks,
Pablo

Is there any problem with the visualization data? I am trying to run the notebook in the demo folder (code below), but it does not display anything.
import os
viz_path = os.path.dirname(os.path.realpath(name)) + '/viz'
bc.visualization.export(U, viz_path)
from IPython.display import IFrame
IFrame("/files/viz/index.html", "100%", 700)
Thanks,
Pablo


UI: Create PV/PVC in volume details drop down menu not working.

Longhorn UI version: e077811
Steps to reproduce:

Create a volume
Go to volume details page.
From upper right drop down menu click Create PV/PVC.

Longhorn UI version: 9f1e1cf
Fixed


Lower resource requirements in demo profile

The new higher requirements in values.yaml prevent one from starting Istio on the IKS free clusters. Lowering the requirements to the earlier values (matching e3e test values) allows Istio to start.

@ericvn: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ericvn
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: linsun
If they are not already assigned, you can assign the PR to them by writing /assign @linsun in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @ericvn. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Is this right? 992 files changed?

/ok-to-test

I believe the cla:no was because I inadvertantly created the PR against master instead of release 1:1 which had many commits. After the rebase to 1.1, the commits reverted back to this single file so should be OK?

/assign @linsun

@ericvn: GitHub didn't allow me to assign the following users: linsun.
Note that only istio members and repo collaborators can be assigned.
For more information please see the contributor guide

In response to this:

/assign @linsun

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ericvn, ymesika
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [ymesika]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ericvn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
9018e706030fa7204842f5b9792d7998f863131b
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
9018e706030fa7204842f5b9792d7998f863131b
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
9018e706030fa7204842f5b9792d7998f863131b
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@linsun: changing LGTM is restricted to assignees, and assigning you to the PR failed.

In response to this:

/lgtm
/approve
this is just restoring the old default we had on demo profile, being approved by env WG yesterday
cc @costinm @sdake @wenchenglu can we get this in 1.1?

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ericvn, linsun, ymesika
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [linsun,ymesika]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ericvn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
9018e706030fa7204842f5b9792d7998f863131b
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
9018e706030fa7204842f5b9792d7998f863131b
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
9018e706030fa7204842f5b9792d7998f863131b
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@linsun
@ericvn
any idea why CLA check didn't pass?

@wenchenglu I noted it above, but I think it was because I originally targeted this against master (sorry) and then there were many commits (instead of 1). The cla checker ran and found non-cal in those commits. When I rebased to 1.1, I got back to one commit, but the cla was already no.
I hope that make sense.

@ericvn thanks for the context

Shouldn't we update install/kubernetes/helm/istio/values-istio-demo-auth.yaml as well?

Thanks @howardjohn for picking up the missed change. I was going to make it after you mentioned it, but see you have the PR.


guv-web: Restrict User(s) Per Process

Regarding the guv-web interface:
I see the ability to restrict access for users on a per-host/server basis, but not a per-process basis. I would like to see this implemented (or if it's already possible, explain how it is done as I couldn't find anything in the documentation).
Reason being is I run multiple Ghost blogs on a single server, but want multiple users to be able to log into the web interface to restart, check logs, etc of their Ghost blog (or process). As of right now they have access to everyone else's Ghost blog on that same host.

The intention behind the manager is to be a bit like ps aux which lets you see all processes, regardless of user.
Have you considered isolating your processes by running multiple instances of guv under individual Docker containers instead?

I had thought about it, but didn't want to go that route if I would be able to restrict access per process in Guvnor. However if that is how this application is intended, then I can utilize both it and Docker like you suggested. Thanks.


Turn off python build cache on Circle Ci

Due to a corrupted state of the cache and the failing master branch, I am going to turn off the cache until I fix it.

Already fixed in #377 😂


Second Battery in calculations

Describe, what you want to be added!
I would like to be able to use a second battery in the calculations. Example with my Goodwe ET29.9. Thank you
Describe the solution you'd like
Nothing
Describe alternatives you've considered
Nothing
Additional Information
Nothing

Do you mean a second battery to be calculated, how long the runtime for it is?

Yes, calculate runtime AND consumption.

Understand - but i think, this is a very special request, as nearly all users have one battery.


[Improvement]: Implement Engagements related operations in Netsuite connector

Connector Name
module/netsuite (Netsuite)
Suggested improvement
Need to implement  Engagements related operations in Netsuite connector
https://discord.com/channels/957996897782616114/1024197445615362088/1024197445615362088

Closing as this wont be done.


Farsi(Persian) names of carriers

Hi. Please create a new folder named "fa" in https://github.com/googlei18n/libphonenumber/tree/master/resources/carrier
also please copy the 98.txt file from en folder to there. Because I want translate Iranian carrier names to Persian(Farsi). For example Irancell Carrier in en folder should be translated to "ایرانسل" in fa folder.
Note: Now Arabic language have a folder named ar in there.
Note2: It would be helpful if we have a 93.txt also in fa folder. Because we can translate Afghanistan carrier names to Persian also.
Note: I can create a new file there by new file Button, but I can't create new folder there. Why?
Thanks.

Thanks for contributing to geocoding in Persian! We'd be happy to review a pull request.
Are you using the command-line? Try creating the files before pushing to your repository.
You should be able to upload the files like so in your fork:
mkdir resources/carrier/fa
cp resources/carrier/en/98.txt resources/carrier/fa/
cp resources/carrier/en/93.txt resources/carrier/fa/

Then edit the files under resources/carrier/fa/ to Persian and commit and push them to your fork, then send us a pull request! Let me know if you need further help.

Oh, and please sign the CLA. See our contribution guidelines.

I also tried adding a file on the UI. Here's how:
Go to https://github.com/googlei18n/libphonenumber/tree/master/resources/carrier
Click on "Create new file"
In the "Name your file..." box type in "fa/" and hit Enter
It will then have a new "Name your file..." box, and you can enter 98.txt
Hope that helps!

Thanks. I created a pull request for this. I described changes there. Look at here: https://github.com/googlei18n/libphonenumber/pull/1151
Please check and merge it.
I hope it will be helpful.

Thanks @afarsi! I'm reviewing the PR.
Closing this issue, let's track completion at the PR.


wasm: sync WasmVm interface with upstream.

Remove functions that are no longer needed. For details, see:

https://github.com/envoyproxy/envoy-wasm/pull/276

Signed-off-by: Piotr Sikora<EMAIL_ADDRESS>

@lizan let me know if this is fine as-is or if you prefer that I bundle it in V8 PR.

Actually, one more change coming...
/wait

This is good to go, PTAL.


KeyringController:submitPassword should fail for wrong password

While working on test coverage I found an issue that KeyringController:submitPassword works well even if wrong password is passed. Function call should fail for wrong password.

I believe the unit tests are showing this only because the mock encryptor used will never verify the password. See: https://github.com/MetaMask/controllers/blob/main/tests/mocks/mockEncryptor.ts

Agree that seems to be likely cause


Update e2e test to use the latest maven plugin

Update e2etest to use the latest maven plugin , for the first part of issue #429

Codecov Report

Merging #493 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #493   +/-   ##
========================================
  Coverage    45.29%   45.29%
========================================
  Files           68       68
  Lines         2382     2382
  Branches       269      269
========================================
  Hits          1079     1079
  Misses        1237     1237
  Partials        66       66

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 54aa446...39b190a. Read the comment docs.

LGTM now.


Remove dependency on Microsoft.AspNetCore package

This is related to https://github.com/SAFE-Stack/SAFE-template/issues/326
Don't know the details but the Microsoft.AspNetCore package seems to be "obsolete"/"not meant to be used anymore" (It's been last updated 03.12.2018, while e.g. Microsoft.AspNetCore.App on 2 months ago)
For some reason having this package as a dependency makes the webapp fail in Azure AppEngine environment

This should be closed now with #215 having been merged and released.

Yup, fixed in 0.11 - thanks a lot!


The example https://secretagent.dev/docs/plugins/client-plugins/#client-plugins dont work

i think the example is out of date. Thanks

Can you share a bit more about what's not working? Is it throwing an error, or just silently not working?

Module '"@secret-agent/plugin-utils"' has no exported member 'ClientPlugin'.ts(2305)


Error occured during deployment

Hi there
Great product as always.
When I am deploying to AAS I get the following error shown below. It does appear to still complete the deployment.

I'm not able to reproduce this behaviour. If possible, could you e-mail me the .bim file of the model that you are deploying? do (at) kapacity.dk

@Guavaq I noticed the same error today as part of our release pipelines to Azure Analysis Services. I solved it by updating to the latest version of Tabular and AMO available in the portable version.

Seems like Azure Analysis Services has been updated with a build not supported by the current AMO used by Tabular Editor (18.2.3).
I will provide an updated build that targets <IP_ADDRESS> shortly.

Thanks @otykier it still deploys the measures. Just gives the error

Great @otykier
It seems to even deploy the model fully for a new database. It just keep throwing the error

Fixed in 2.9.2.

Thanks @otykier  I can confirm it is now working!


Use static_assert when possible.

There is only one throw in the code and it can be replaced with a static_assert. This patch will make PCG compatible with -fno-exceptions.

Sorry, it seems I was wrong. It compiled in our code base but your tests fail.


Support for multiple queues

Currently we only support one work queue. We should support more.
Considerations:

Each queue is backed by an SQS queue that must be provisioned
Each queue also need some IAM permissions set up
Each queue will need to show up in the Cloudwatch dashboard
Each queue will need a function definition to receive events
Each queue will need a function configuration (memorySize, etc...)
Each queue will need to set an ENV var (or something) so that its URL is available to the incoming job handler
Each queue may need a unique handler? (This may be more of a 'performance nice to have'...)

A couple of implementation options:

A funktor generate queue command could generate all the needed files and/or attempt to patch existing files.
We could have a master funktor.yml file that is where you configure the queues you want to have, and then have a funktor apply config (or whatever) command that generates a new serverless.yml and all the needed support files.

I think I'm leaning towards option 2.
So, for a new app you'd do something like
funktor bootstrap myapp
# creates myapp/funktor.yml
cd myapp
# edit funktor.yml to add additional queues, for instance
funktor  init
# generate serverless.yml and all the other files

Then some time later, if you need to add more queues you'd add them to funktor.yml and then do funktor init again.
A downside to this approach is that when we regenerate files we could potentially overwrite customizations done to them...

This is now working as of v 0.2.4.


Copy paste resetting the "Action" picklist

In previous versions,
when I used the "Copy (Excel format)" feature from the "Data Export"
and paste the result on "Data Import", the "Action" picklist didn't change
In recent version (1.20.1) the picklist is reset to the "Insert" mode

Hi @Mart-User,
It does indeed, the goal is to automatically fill some data import inputs.
I would suggest to paste and then update the fields.
Since you did not used the issue template, some information are missing,  can I have more info about the the dml you are trying to perform and the object ?
Maybe a gif from a screen recording ?

My use case:
I have a log object that I often delete the records based on a saved query
Because In my org I have several errors and I have to do that to look at the data more precisely
So every day I go to the "Data Export", get my saved query, retrieve data
Then I import the data in "Data Import" to do a delete
Since I know I would use the delete function, I was used to already select the "Delete" action
And the paste the query from "Data Export", that would already select the related SObject
but now I have to paste and then re-select delete
The simple step-by-step would be:
*open the "Data Export"
*do a simple select query
*use the "Copy (to Excel)"
*open the "Data Import"
*select "Delete" action on "Data Import"
*paste your query
*Action picklist would reset to "Insert" (even having an Id in the pasted query)
I can't record it since some data is confidential.
I know it is a minor thing but makes a whole difference for me,
also I don't see how would be beneficial resetting the Action value to "Insert" in this case
But if it won't be reviewed, no problem.

Ok I see, are you aware of the "Delete records" functionality ?
https://github.com/tprouvot/Salesforce-Inspector-reloaded/issues/134
I think it fits your need perfectly 🤌
Other suggestion would be to schedule the deletion using the purge-sobject framework
Anyway I could detect when manual action is performed and not override it on paste but in your case I think 'Delete functionality' would save you some clics

I tried the "Delete records" feature but if there are several records (like 40k, which is my case) the tab opens blank, with fewer records it works.


Kadira breaks under the new mongo driver (2.1.18, that will be soon on meteor)

Hey Guys,
I am working along with the MDG in switching the next version of meteor to the newest possible native mongodb driver. It is not fully integrated on devel, but will soon be on the mongo-3.2 branch. You can see the PR here https://github.com/meteor/meteor/pull/7104
When I was testing in a project kadira broke because of the new driver.
W20160529-17:58:30.183(-3)? (STDERR) /Users/fabs/code/meteor-mongo-3.2/meteor/dev_bundle/server-lib/node_modules/fibers/future.js:267
W20160529-17:58:30.183(-3)? (STDERR)                        throw(ex);
W20160529-17:58:30.184(-3)? (STDERR)                              ^
W20160529-17:58:30.184(-3)? (STDERR) TypeError: Cannot read property 'createDataHandler' of undefined
W20160529-17:58:30.184(-3)? (STDERR)     at setLabels (packages/meteorhacks_kadira/lib/hijack/set_labels.js:10:1)
W20160529-17:58:30.184(-3)? (STDERR)     at packages/meteorhacks_kadira/lib/hijack/instrument.js:33:1
W20160529-17:58:30.184(-3)? (STDERR)     at runWithAFiber (packages/meteorhacks_meteorx/lib/server.js:33:1)
W20160529-17:58:30.184(-3)? (STDERR)     at packages/meteorhacks_meteorx/lib/server.js:26:1
W20160529-17:58:30.185(-3)? (STDERR)     at Array.forEach (/Users/fabs/code/meteor-mongo-3.2/meteor/packages/es5-shim/.npm/package/node_modules/es5-shim/es5-shim.js:435:21)
W20160529-17:58:30.185(-3)? (STDERR)     at Package (packages/meteorhacks_meteorx/lib/server.js:25:1)
W20160529-17:58:30.185(-3)? (STDERR)     at /Users/fabs/code/react/board/.meteor/local/build/programs/server/boot.js:290:5

The reason is that, even though there is still MongoInternals.NpmModule as a backward compatibility feature (the new place where it is expected to be since <IP_ADDRESS> is MongoInternals.NpmModules.mongodb.module the new driver does not have a Connection property and thus
var originalCreateDataHandler = mongodb.Connection.createDataHandler;
throws an error.

Thanks @Fabs.
I'll make changes.

Still experiencing this problem in v2.29.0. I've removed the package for the time being to be able to use Meteor 1.4-beta-3.

@MechJosh0 check v2.29.1.

@arunoda I can confirm v2.29.1 worked for me. Thank you.

Can I use kadira:debug in my Meteor <IP_ADDRESS>,  How can I just fix the same error for now?

Having the same problem, is there a fix?

+1

+1

still experiencing the problem for kadira:debug

I have the same problem here :(

W20170320-09:30:12.360(5.5)? (STDERR) 						throw(ex);
W20170320-09:30:12.360(5.5)? (STDERR) 						^
W20170320-09:30:12.360(5.5)? (STDERR)
W20170320-09:30:12.361(5.5)? (STDERR) TypeError: Cannot read property 'createDataHandler' of undefined
W20170320-09:30:12.361(5.5)? (STDERR)     at setLabels (packages/meteorhacks_kadira.js:3335:53)
W20170320-09:30:12.361(5.5)? (STDERR)     at packages/meteorhacks_kadira.js:2872:5
W20170320-09:30:12.361(5.5)? (STDERR)     at packages/meteorhacks_meteorx.js:190:7
W20170320-09:30:12.362(5.5)? (STDERR)     at Array.forEach (native)
W20170320-09:30:12.362(5.5)? (STDERR)     at packages/meteorhacks_meteorx.js:189:29
Any solution for this?

I had this issue on meteorhacks:kadira v2.23.4 with Meteor <IP_ADDRESS>.
Updating to meteorhacks:kadira v2.30.3 with Meteor v<IP_ADDRESS> fixed it for me. The issue is resolved and Kadira works.


Support Bayer12 formats.

Is your feature request related to a problem? Please describe.
Support the following Bayer formats:

BayerGR12
BayerRG12
BayerGB12
BayerBG12

Describe the solution you'd like
Harvester GUI should support those formats.
Describe alternatives you've considered
None.
Additional context
None.

We have actually a need for these pixel formats. Is it possible to open this issue?

Of course!
So could you leave your comment here everytime you confirmed any of these pixel formats worked or not worked so that everybody can share the latest status?

Yes, I'll do that. Thank you!


DX: Add composer keywords (#30

as per https://github.com/composer/composer/pull/10960 this allows composer to warn the user, when installing the tool as a project dependency instead of a dev-dependency

Thank you :+1:


make blackstone and cobbled deepslate hammerable

fixes blackstone and cobbled deepslate not being hammerable

I created a separate commit with your changes and included you as a co-author, since there were issues when changing the target branch.


Perl: URI 1.60 -> 1.65

Looks good, waiting for revdep rebuilds, i.e. git, munin and xmltv.

(Yeah, I was cheating a bit and using Travis as a big test hammer.)
The errors seem unrelated to my update, though. A whole bunch of 404/50whatevers leading to dependency failures. Trying it locally:
$ nix-env -f ~/Hacking/nixpkgs --show-trace -iKA pkgs.perlPackages.NetAmazonEC2
...
output path ‘/nix/store/kq9ish8mm7hhxlwwg87c8lym014jf7ri-Net-Amazon-EC2-0.14-stanaka-bc66577e13.zip’ should have sha256 hash ‘1c0k3addkaaf4zj7z87svm9xc3c06v0r06rf5rpqmps413lqisbn’, instead has ‘1a46lcphsrvi0ypgk64qwan3zfar6f1ha4z2w4ly7ga6lwrb2a1c’
Down the rabbit hole I go.

All those updates are now in maser. Closing.


Project manager loads with the size settings of the previously opened project

Windows 7 64 bits, Godot 2.0.1
I quit "to project list", then the Project Manager opens in a tiny window that appears to have the same options as the last opened project.
My game had a tiny resolution and a viewport stretch mode. The project manager opened tiny too, and when resized it zooms without filter while keeping the ratio with black bands. Just as my game :p
Open this project: http://zylannprods.fr/dl/godot/ProjectManagerWrongDisplay.zip
Then "quit to project list", notice the weird window size and stretch behaviour.

Can confirm the same bug on current HEAD with Ubuntu 15.10 64bits. Clicking Quit to Project List will open the project manager with a window size equivalent to the project display settings (test_width and test_height, or width and height if the previous two are not set).

Confirmed on Windows 10 64 bit

Confirmed on Arch Linux 64-bit, Godot 2.0.3.

That must be a regression, I don't remember it from before 2.0.

It's indeed a regression between 2.0 and 2.0.1, I'm currently bisecting the faulty commit and will try to fix it.

$ git bisect log
git bisect start
# bad: [53aa9cd51ab2551d67a71729ff61ae6668abda74] Release 2.0.1
git bisect bad 53aa9cd51ab2551d67a71729ff61ae6668abda74
# good: [9e2b9f8cb1c34fe7c3aa91bdd7f40ebb6a1a318f] bump to stable, congratulations everyone
git bisect good 9e2b9f8cb1c34fe7c3aa91bdd7f40ebb6a1a318f
# bad: [9ed3d21d5a3f0c5bad70b9a24d0fd2be8b6e81e8] Sync classes
git bisect bad 9ed3d21d5a3f0c5bad70b9a24d0fd2be8b6e81e8
# bad: [ee5c250b632c9067c6be6d121b50d62e83e0d3b0] OUYA gamepad mappings fix
git bisect bad ee5c250b632c9067c6be6d121b50d62e83e0d3b0
# good: [61f17fb1bb507a15a325ee4c23a69d85f9d8b7b6] applied some typo fixes. see godotengine/godot-docs#18
git bisect good 61f17fb1bb507a15a325ee4c23a69d85f9d8b7b6
# good: [d86b12a3973a46a0b6890276e40f3ff464baa5a2] Fixed closing a scene tab when it was not the CURRENT tab. Fixes #3810
git bisect good d86b12a3973a46a0b6890276e40f3ff464baa5a2
# bad: [e4d367e7a1fa6e8cefb95b57fe776cba13e84e75] theora on server build
git bisect bad e4d367e7a1fa6e8cefb95b57fe776cba13e84e75
# bad: [45a0bbe56e64ad14f18c037bf7130f3d383ec6d6] adds -pm and -project_manager command line options to start project manager
git bisect bad 45a0bbe56e64ad14f18c037bf7130f3d383ec6d6
# first bad commit: [45a0bbe56e64ad14f18c037bf7130f3d383ec6d6] adds -pm and -project_manager command line options to start project manager

45a0bbe56e64ad14f18c037bf7130f3d383ec6d6 is the first bad commit
commit 45a0bbe56e64ad14f18c037bf7130f3d383ec6d6
Author: Ariel Manzur<EMAIL_ADDRESS>Date:   Thu Feb 25 03:02:09 2016 -0300

    adds -pm and -project_manager command line options to start project manager

    fixes bug where the user has an engine.cfg on the executable directory so it runs the game instead of opening the project manager

:040000<PHONE_NUMBER>b3a45d1e3f87d954b79618dfa18af17aaac2 e095cfe74d9ac51cc2d20c361421b0618fbbdebf M      main
:040000 040000 c20d27f3d6a7f12aa29c0586288df42b10a8cdd7 de5302994198a242a5dd1132b5fd0682c1e752f1 M      tools


Add Discord links

Description
Adds an invitation to the Bootstrap Discord server to the Community sections of the docs, the docs footer, and the project README.
Motivation & Context
To give users another option for seeking support when working with Bootstrap.
Type of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would change existing functionality)

Checklist

[x] I have read the contributing guidelines
[x] My code follows the code style of the project (using npm run lint)
[x] My change introduces changes to the documentation
[x] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Live previews

https://deploy-preview-39104--twbs-bootstrap.netlify.app/

Related issues

When it'll be reviewed, there's also https://github.com/twbs/bootstrap/pull/38873 tackling a part of it.

Closing it as handled in #38873 with Bootstrap subreddits at the same time.
Thank you for you PR @martinbean


data url as icon for marker with SVG not working

Hi
I'm using SVG icons inside of my app and would like to use them for the map as well.
icon:  data:image/svg+xml;base64,PHN2ZyB4b....
-> no icon at all on the map
Loading png the same way works like a charm.
My Env:
"ionic-native": "2.5.1",
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0

SVG is not supported.

sad to hear, thanks for the fast answer!

Hello. svg is working or not for marker?

no

Same problem. but svg not working only for map


Remove travis ci, update renovate bot settings

Removing Travis CI - we have GIthub Actions instead now
Added CI badge to readme.md
Updated renovate bot settings so it submits only up to 5 PRs in parallel and auto-tag its PRs with dependencies

should we also remove the travis.yml from the repo root?

should we also remove the travis.yml from the repo root?

Yes, it's part of this change.

Yes, it's part of this change.

Sorry, missed that. Looks good!


Yank v0.2.0 and roll back master to v0.1.x

Background
In PR #3 the generic-array dependency was semver bumped and v0.2.0 of this
crate was released just to include that change.
In general, I prefer to avoid making a new minor release (AKA semver bump) of an
"interface" crate, which main role is providing a trait for crates to
inter-operate, because it causes the ecosystem to be split in two. For example,
for aligned to work with as-slice v0.2.x (PR japaric/aligned#6) I would need
to semver bump the aligned crate (i.e. release v0.4.0). Then cortex-m to
work with that new version of aligned would need also a semver bump. You can
see how this produces a cascade of semver bumps across the ecosystem.
Proposal
In the case of PR #3, the goal of supporting generic-array v0.13.x could have
been achieved without a semver bump. So I propose we support that crate on the
v0.1.x line and yank v0.2.0.
Bump the MSRV
(MSRV = Minimum Supported Rust Version)
Due to the generic-array dependency, as-slice v0.1.0 has an effective MSRV of
1.19.0; on the other hand as-slice v0.2.0 has an effective MSRV of 1.31.0.
In this first alternative, the approach would be release a v0.1.2 of as-slice
that depends on both generic-array v0.12.x and v0.13.x. This approach bumps
the MSRV of v0.1.0 from 1.19 to 1.31 in v0.1.2, which is a breaking change.
However, we can get away with the MSRV bump because there's no guaranteed
MSRV; MSRV is not documented therefore there's no guaranteed MSRV.
Cargo feature
The other option is to support generic-array v0.13.x in v0.1.2 behind an
opt-in Cargo feature, e.g. ga13. Enabling this feature makes as-slice v0.1.2
support both v0.12.x and v0.13.x of generic-array. Enabling the Cargo
feature does bump the MSRV but this is not a breaking change because it's
an opt-in bump.

Isn't depending on two generic-arrays bad for compilation time?

No, there's hardly any difference in compilation time between compiling
generic-array once or twice. I measured cargo clean; cargo build-ing this
crate and I got 2.64 s +- 0.5s for both configurations, so if there's any
difference is within standard deviation.

Isn't yanking v0.2.0 a "breaking change"?

No, it's not a breaking change according to the Rust project's concept of
guaranteed stability. Crates that depend on v0.2.0 published on crates.io will
continue to use version v0.2.0 and thus continue to compile. On the other hand,
unpublished crates, which can be modified by the person who's compiling them,
will indeed break but can be easily fixed by subbing v0.2.0 for v0.1.2.

But builds will break!

Sure, but the CI builds of unpublished crates also break whenever new warnings
are introduced in rustc and you were using #[deny(warnings)]. This breakage
is along the same line and still within Rust's concept of guaranteed stability
of published crates, which all crates are expected to follow (e.g. by
following semver).

This is not a pain-free change but I think some short-term pain is a better alternative than a long-term ecosystem split and a cascade of semver bump.
Thoughts? @korken89
cc @burrbull

I think this is good, I was from the start going to simply bump the patch.

See PR #5


T(...)Server.close() cannot stop the server

Hello,
The "close" method of the TSimpleServer/TThreadedServer classes cannot close the server because the thread who called "serve()" is blocked at "client = self.trans.accept()". The only way I found to stop it is to call "server.trans.close()" after "server.close()", which is not obvious. I think you should call "self.trans.close()" in the TServer.close() method.
If you agree I can propose a PR.
Regards

I am glad to see your pull request, thanks.


Update the bastion network name to pi_network_name #437

As identified in issue #437, the bastion network name results in a deprecation warning.
The PR updates to support the new PowerVS terraform field pi_network_name
I have verified via a terraform plan that this is working as expected without a deprecation warning.
Signed-off-by: Paul Bastide<EMAIL_ADDRESS>

/ok-to-test

/lgtm
/hold-for @yussufsh

/approve


About me field will no longer display when on other user's page

Tested on devserver and works as expected.

Looks good to me!


embed custom model  for generated model

how to embed custom model  for generated model .for example, embed gorm.Model directly in generated structs

It is already a generated model, is it meaningless to reuse the gorm model?


Can't find module @capacitor-community/apple-sign-in with Capacitor 3

Describe the bug
I'm upgrading and app from Capacitor 2.0 to Capacitor 3.0.
The last plugin that needs to be migrated is this one.
I tried to update to the latest version with no luck.
How can I install the latest version compatible with Capacitor 3?
In the repo there's a 1.0.0 release, but the latest npm release is version 0.1.2.
I also tried to install directly from GitHub, npm install capacitor-community/apple-sign-in but I always get an error:
./src/app/services/authentication.service.ts:11:0-69 - Error: Module not found: Error: Can't resolve '@capacitor-community/apple-sign-in' in 'D:_git\MyApp\MyApp\src\app\services'
[ng] Error: src/app/services/authentication.service.ts:12:82 - error TS2307: Cannot find module '@capacitor-community/apple-sign-in' or its corresponding type declarations.
[ng] 12 import { SignInWithApple, SignInWithAppleResponse, SignInWithAppleOptions } from '@capacitor-community/apple-sign-in';
Screenshots

How can I successfully install and use this plugin with Capacitor 3.0?

Any guesses what the problem might be?
Only this plugin is missing to complete my app migration to Capacitor 3. At the moment, I don't know which version to install.
There doesn't seem to exist a version in npm compatible with Capacitor 3.

Any guesses what the problem might be?
Only this plugin is missing to complete my app migration to Capacitor 3. At the moment, I don't know which version to install.
There doesn't seem to exist a version in npm compatible with Capacitor 3.

I also found this issue. Any update on this?

Yeah. What's going on with this?

Why has support for Capacitor 3 not been released? This is literally the only plugin that I have that isn't supporting capacitor 3 right now.

There has been a mixup of versions, latest version (0.1.2) was compatible with Capacitor 3 already, while version 1.0.0 wasn't, not sure why it was published with a major version bump 8 months ago and then continued doing patch/minor bumps from 0.x.x
I've published 1.0.1 with latest changes


ghc-mod fails in cabal project

Everything works fine when I edit some non-project hs file, but each time I press Cmd-S, when cabal project is added as a root directory, I see an error popup with this text:
cabal-helper-wrapper: ghc: readCreateProcess: runInteractiveProcess: exec: does not exist (No such file or directory)
ghc-mod: readCreateProcess: /Users/pavel/.cabal/libexec/cabal-helper-wrapper "--with-ghc=ghc" "--with-ghc-pkg=ghc-pkg" "--with-cabal=cabal" "/Users/pavel/Documents/DEV/biocad/tests/ysar" "/Users/pavel/Documents/DEV/biocad/tests/ysar/dist" "package-db-stack" "entrypoints" "source-dirs" "ghc-options" "ghc-src-options" "ghc-pkg-options" "ghc-merged-pkg-options" "ghc-lang-options" "licenses" (exit 1): failed

OS X 10.10.5
Atom 1.0.19
Cabal <IP_ADDRESS> (from Homebrew)
ghc 7.10.2 (from Homebrew)
ghc-mod <IP_ADDRESS> (from cabal)

Looks like ghc-mod can't find cabal-helper-wrapper. It should be in .cabal/libexec/. If you don't have /Users/pavel/.cabal/libexec/cabal-helper-wrapper, this might indicate an installation issue. Otherwise if it's there, I'm not sure what's going on.

I have it and it works, as I can see.
From console%
$ /Users/pavel/.cabal/libexec/cabal-helper-wrapper "--with-ghc=ghc" "--with-ghc-pkg=ghc-pkg" "--with-cabal=cabal" "/Users/pavel/Documents/DEV/biocad/tests/ysar" "/Users/pavel/Documents/DEV/biocad/tests/ysar/dist" "package-db-stack" "entrypoints" "source-dirs" "ghc-options" "ghc-src-options" "ghc-pkg-options" "ghc-merged-pkg-options" "ghc-lang-options" "licenses"
WARNING: cache is out of date: /usr/local/Cellar/ghc/7.10.2/lib/ghc-7.10.2/package.conf.d/package.cache
ghc will see an old view of this package db. Use 'ghc-pkg recache' to fix.
[1 of 5] Compiling CabalHelper.Types ( CabalHelper/Types.hs, /Users/pavel/.ghc-mod/cabal-helper/CabalHelper/Types.o )
[2 of 5] Compiling CabalHelper.Common ( CabalHelper/Common.hs, /Users/pavel/.ghc-mod/cabal-helper/CabalHelper/Common.o )
[3 of 5] Compiling CabalHelper.Sandbox ( CabalHelper/Sandbox.hs, /Users/pavel/.ghc-mod/cabal-helper/CabalHelper/Sandbox.o )
[4 of 5] Compiling CabalHelper.Licenses ( CabalHelper/Licenses.hs, /Users/pavel/.ghc-mod/cabal-helper/CabalHelper/Licenses.o )
[5 of 5] Compiling Main             ( CabalHelper/Main.hs, /Users/pavel/.ghc-mod/cabal-helper/Main.o )
Linking /Users/pavel/.ghc-mod/cabal-helper/cabal-helper-<IP_ADDRESS>-Cabal-<IP_ADDRESS> ...
[Just (ChResponsePkgDbs [ChPkgGlobal,ChPkgUser]),Just (ChResponseEntrypoints [(ChLibName,ChLibEntrypoint {chExposedModules = [ChModuleName "Data.YSAR"], chOtherModules = []}),(ChExeName "ysar",ChExeEntrypoint {chMainIs = "Main.hs", chOtherModules = []}),(ChSetupHsName,ChSetupEntrypoint)]),Just (ChResponseCompList [(ChLibName,["src"]),(ChExeName "ysar",["bin"]),(ChSetupHsName,[])]),Just (ChResponseCompList [(ChLibName,["-fbuilding-cabal-package","-O","-outputdir","dist/build","-odir","dist/build","-hidir","dist/build","-stubdir","dist/build","-i","-idist/build","-isrc","-idist/build/autogen","-Idist/build/autogen","-Idist/build","-optP-include","-optPdist/build/autogen/cabal_macros.h","-hide-all-packages","-package-id","base-<IP_ADDRESS>-075aa0db10075facc5aaa59a7991ca2f","-XHaskell2010"]),(ChExeName "ysar",["-fbuilding-cabal-package","-O","-outputdir","dist/build","-odir","dist/build","-hidir","dist/build","-stubdir","dist/build","-i","-idist/build/ysar/ysar-tmp","-ibin","-idist/build","-isrc","-idist/build/autogen","-Idist/build/ysar/ysar-tmp","-Idist/build/autogen","-Idist/build","-optP-include","-optPdist/build/autogen/cabal_macros.h","-hide-all-packages","-package-id","base-<IP_ADDRESS>-075aa0db10075facc5aaa59a7991ca2f","-XHaskell2010"]),(ChSetupHsName,[])]),Just (ChResponseCompList [(ChLibName,["-i","-idist/build","-isrc","-idist/build/autogen","-Idist/build/autogen","-Idist/build","-optP-include","-optPdist/build/autogen/cabal_macros.h"]),(ChExeName "ysar",["-i","-idist/build/ysar/ysar-tmp","-ibin","-idist/build/autogen","-Idist/build/autogen","-Idist/build/ysar/ysar-tmp","-optP-include","-optPdist/build/autogen/cabal_macros.h"]),(ChSetupHsName,[])]),Just (ChResponseCompList [(ChLibName,["-hide-all-packages","-package-id","base-<IP_ADDRESS>-075aa0db10075facc5aaa59a7991ca2f"]),(ChExeName "ysar",["-fbuilding-cabal-package","-O","-outputdir","dist/build","-odir","dist/build","-hidir","dist/build","-stubdir","dist/build","-i","-idist/build","-isrc","-idist/build/autogen","-Idist/build/autogen","-Idist/build","-optP-include","-optPdist/build/autogen/cabal_macros.h","-hide-all-packages","-package-id","base-<IP_ADDRESS>-075aa0db10075facc5aaa59a7991ca2f","-XHaskell2010"]),(ChSetupHsName,[])]),Just (ChResponseList ["-fbuilding-cabal-package","-O","-outputdir","dist/build","-odir","dist/build","-hidir","dist/build","-stubdir","dist/build","-i","-idist/build","-isrc","-idist/build/autogen","-Idist/build/autogen","-Idist/build","-optP-include","-optPdist/build/autogen/cabal_macros.h","-hide-all-packages","-package-id","base-<IP_ADDRESS>-075aa0db10075facc5aaa59a7991ca2f","-XHaskell2010"]),Just (ChResponseCompList [(ChLibName,["-XHaskell2010"]),(ChExeName "ysar",["-XHaskell2010"]),(ChSetupHsName,[])]),Just (ChResponseLicenses [("BSD3",[("integer-gmp",Version {versionBranch = [1,0,0,0], versionTags = []}),("ghc-prim",Version {versionBranch = [0,4,0,0], versionTags = []}),("rts",Version {versionBranch = [1,0], versionTags = []}),("base",Version {versionBranch = [4,8,1,0], versionTags = []})])])]

I get the exact same behaviour when I've built from the command line first. When I Cmd-S with no dist directory, I just get the following:

ghc-mod: cabal: readCreateProcess: runInteractiveProcess: exec: does not exist (No such file or directory)
@zmactep Have you found a solution by any chance?

I have a similar issue using Stack and I've added a comment under Issue #44.
"Haskell-ghc-mod: /home/eric/.local/bin/ghc-mod check /home/eric/code/my-project/src/Main.hs failed with error code 1
ghc-mod: cabal: readCreateProcess: runInteractiveProcess: exec: does not exist (No such file or directory)"
I get the same Atom error after following all advice above (from Issue #44). ghc-mod check works fine from command line for both Stack/non-Stack located .hs files and also works inside Atom for non-Stack located .hs files. But trying to check (cmd-s) a Stack located .hs file in Atom gives me the above error.
$ which ghc-mod = /home/eric/.local/bin/ghc-mod (set to same in Haskell-ghc-mod)
$ which ghc = /home/eric/.stack/programs/i386-linux/ghc-7.10.2/bin/ghc
extra-deps: [ghc-mod-<IP_ADDRESS>] in project stack.yaml
no dist folder in project root directory (but .stack-work/dist exists)
have: /home/eric/.stack/global-project/.stack-work/install/i386-linux/lts-3.15/7.10.2/libexec/cabal-helper-wrapper
Stumped. How do I ghc-mod check files interactively within Atom and within a Stack project.
Thanks.

@eatobin, here's a crazy idea: run Atom from terminal, with, in project directory, stack exec atom. This whole thing seems very much like an environment issue, and this trick might help solving that, at least until we figure out what is going wrong exactly.
Please make sure to delete dist/ directory first, as ghc-mod tends to get confused sometimes and tries to cabal configure a stack project.

fib_tuple.txt
Thank you! Tried it and no crashes! But... check this out: Save the attached file to src in a stack project and also to Desktop. The file when opened in the stack project directory with "stack exec atom" opens and returns no Errors and no Warnings. Now open this same file from the Desktop (don't close Atom) and there are no Errors and 2 Warnings on line 10??!!
Do you get similar results?

Would you mind telling what are those warnings specifically? I'm on Linux and don't use stack, so testing this would be a problem.

Ah, nevermind that. Unused variables I presume?

Try adding {-# OPTIONS_GHC -Wall #-} pragma to your source file. Maybe cabal/stack settings suppress some warnings.

The pragma did it - that was it. Thank you!

Would you mind posting output of stack exec env for future reference?

stack-exec-env.txt
Sure.


Update Assets / engines folder

All changes related to system/engines/ (which contains 3rd party tools) - updated on demand.

Avoid Potential XSS vulnerability in jQuery versions < 3.5.
To achieve this, all outdated jQuery versions and references (prior to 3.5) will be removed.


Add ubiquiti-unifi-security-gateway

What does this PR do?

Add ubiquiti-unifi-security-gateway
Motivation

Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] If the PR doesn't need to be tested during QA, please add a qa/skip-qa label.

@lizaerem 👋 , could you have another look at this PR :)


SIMPLE + ADVANCED develop_supervised_model :: add random forest regressor

Work done in #204 Needs testing and documentation

Work done in #213


Use aarch64 MacOS on CI

Feature Request
Test on Macos M1 runner to improve CI speed.
Waiting on addition of Macos M1 runner.

[x] https://github.com/github/roadmap/issues/52
[ ] Small runners are available
[ ] Android NDK is preinstalled
[x] Update checks.yml
[ ] Update compileContracts.sh

Blocked: no android NDK, no small runners.


Display links on separate lines

This part of the document currently renders like this:

I changed the document so it will render like this:


Folder Picker - JavaScript API

Is your feature request related to a problem? Please describe.
Currently we only have custom folder pickers represented as options in the Command Bar with indentation showing the folder hierarchy.
Describe the solution you'd like
A native way to pick folders, probably using something similar to the sidebar where you can collapse and expand folders.
Describe alternatives you've considered
The alternative is currently to show the folders as options in the Command Bar results.

This would replace my folder picker function in helpers/userInput.js.


supplying verticalposition to Timeseries should raise an error

Describe the bug
When supplying verticalposition=VerticalPositionType('ZBed') as an argument to TimeSeries, it is not written to file. This makes sense since Timeseries do not have vertical positions. It would be great if this would be checked upon initialisation (or can it be validated already manually)
When supplying an array instead of list, I get this error:
ValidationError: 1 validation error for TimeSeries
    east2_0001 -> datablock -> 0
      value is not a valid list (type=type_error.list)

To Reproduce
ts_one = TimeSeries(name=pli_PolyObject_name_num,
                    verticalposition=VerticalPositionType('ZBed'),
                    quantityunitpair=[QuantityUnitPair(quantity="time", unit=refdate_str),
                                      QuantityUnitPair(quantity=bcvarname, unit=varunit)],
                    timeinterpolation=TimeInterpolation.linear,
                    datablock=datablock_list,
                    )
ForcingModel_object.forcing.append(ts_one)

Expected behavior
Raise exception when not-supported arguments are supplied.
Version info (please complete the following information):

OS: Windows, Anaconda, Spyder
Version: 0.3.0

Remedy: Possibly the ForcingBase.Config.extra could be changed to Extra.forbid?

@veenstrajelmer : the current behavior is:
When you provide attributes that are not known for a particular function type (e.g. verticalposition for a non-3D TimeSeries), then that attribute is silently dropped, so it is not added to the in-memory TimeSeries object.
This behavior is intentional, because some users have asked to allow creation of a set of forcing object with a given dataframe as input, where that dataframe also contains several user-specific columns that don't have to appear in the model input files, but the user also doesn't want to first drop these columns.
(Specifically this came up in discussions with @xldeltares who had dataframe input for lateral timeseries on urban manholes.)
Can you understand and accept not changing this behavior?

This is understandable. The bugfixes for the T3D header already made the initialization a bit more strict so I think there is enough feedback for the user.


use no top-level wrapper

Setting the top-level wrapper to false still wraps the entire input block in a div
config.wrappers :tag => false, do |b|

yields
<div class="string required">

Would be nice to be able to disable it completely. This is useful when building input forms using the dl, dt, dd tags, as inserting a div tag inside a dl is invalid HTML5.
Will work on it myself if i get time =)
my full config block, in case anyone has a workaround:

  config.wrappers :tag => false, do |b|
    b.use :placeholder
    b.use :label, :tag => :dt
    b.use :input, :tag => :dd do |i|
      i.use :input
      i.use :hint, :tag => :p
      i.use :error, :tag => :span, :class => 'invalid-side-note'
    end
  end

I think that you have a missing comma in you wrappers call. Try this code
config.wrappers :tag => false do |b|
  b.use :placeholder
  b.use :label, :tag => :dt
  b.use :input, :tag => :dd do |i|
    i.use :input
    i.use :hint, :tag => :p
    i.use :error, :tag => :span, :class => 'invalid-side-note'
  end
end

I removed the extraneous ',', but to no effect. Still getting the div wrapper.

Ok. I will investigate it. Thanks

simple_form.rb:145 and builder_rb.:38...
options[:tag] ||= :div clobbers false and nil, when it should only clobber nil.
i'll patch it this afternoon, see how it goes.

Ok. Thanks

commit above fixes the problem for me. Tried a bit to get some tests covering it, but it wasn't obvious how to properly test options in the config block.

(rebased to single commit)

Could you provida a test and open a pull request?

Closed. Thanks

I just want use this config, but in simple_form 1.5.1, the error is shown below:
E:/gpetest/config/initializers/simple_form.rb:4:in block in <top (required)>':undefined method wrappers' for SimpleForm:Module (NoMethodError)..
how can i do next? thanks.

I can't use this configuration with SimpleForm 1.5.1, only with the master branch


cd kernels/selective_scan && pip install .      Why does this error occur?

(VMamba) root@autodl-container-3b294fb6e2-9031d1fb:~/autodl-tmp/VMamba/kernels/selective_scan# pip install .
Looking in indexes: http://mirrors.aliyun.com/pypi/simple
Processing /root/autodl-tmp/VMamba/kernels/selective_scan
Preparing metadata (setup.py) ... done
Requirement already satisfied: torch in /root/miniconda3/envs/VMamba/lib/python3.10/site-packages (from selective_scan==0.0.2) (2.1.1+cu118)
Requirement already satisfied: packaging in /root/miniconda3/envs/VMamba/lib/python3.10/site-packages (from selective_scan==0.0.2) (24.1)
Requirement already satisfied: ninja in /root/miniconda3/envs/VMamba/lib/python3.10/site-packages (from selective_scan==0.0.2) (<IP_ADDRESS>)
Requirement already satisfied: einops in /root/miniconda3/envs/VMamba/lib/python3.10/site-packages (from selective_scan==0.0.2) (0.8.0)
Requirement already satisfied: filelock in /root/miniconda3/envs/VMamba/lib/python3.10/site-packages (from torch->selective_scan==0.0.2) (3.13.1)
Requirement already satisfied: typing-extensions in /root/miniconda3/envs/VMamba/lib/python3.10/site-packages (from torch->selective_scan==0.0.2) (4.9.0)
Requirement already satisfied: sympy in /root/miniconda3/envs/VMamba/lib/python3.10/site-packages (from torch->selective_scan==0.0.2) (1.13.1)
Requirement already satisfied: networkx in /root/miniconda3/envs/VMamba/lib/python3.10/site-packages (from torch->selective_scan==0.0.2) (3.2.1)
Requirement already satisfied: jinja2 in /root/miniconda3/envs/VMamba/lib/python3.10/site-packages (from torch->selective_scan==0.0.2) (3.1.3)
Requirement already satisfied: fsspec in /root/miniconda3/envs/VMamba/lib/python3.10/site-packages (from torch->selective_scan==0.0.2) (2024.2.0)
Requirement already satisfied: triton==2.1.0 in /root/miniconda3/envs/VMamba/lib/python3.10/site-packages (from torch->selective_scan==0.0.2) (2.1.0)
Requirement already satisfied: MarkupSafe>=2.0 in /root/miniconda3/envs/VMamba/lib/python3.10/site-packages (from jinja2->torch->selective_scan==0.0.2) (2.1.5)
Requirement already satisfied: mpmath<1.4,>=1.1.0 in /root/miniconda3/envs/VMamba/lib/python3.10/site-packages (from sympy->torch->selective_scan==0.0.2) (1.3.0)
Building wheels for collected packages: selective_scan
Building wheel for selective_scan (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
╰─> [107 lines of output]
  torch.__version__  = 2.1.1+cu118

  CUDA_HOME = /root/miniconda3/envs/VMamba

  CUDA version:  11.8
  running bdist_wheel
  running build
  running build_ext
  /root/miniconda3/envs/VMamba/lib/python3.10/site-packages/torch/utils/cpp_extension.py:424: UserWarning: There are no g++ version bounds defined for CUDA version 11.8
    warnings.warn(f'There are no {compiler_name} version bounds defined for CUDA version {cuda_str_version}')
  building 'selective_scan_cuda_oflex' extension
  creating /root/autodl-tmp/VMamba/kernels/selective_scan/build/temp.linux-x86_64-cpython-310/csrc/selective_scan/cusoflex
  Emitting ninja build file /root/autodl-tmp/VMamba/kernels/selective_scan/build/temp.linux-x86_64-cpython-310/build.ninja...
  Compiling objects...

  Traceback (most recent call last):
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 2100, in _run_ninja_build
      subprocess.run(
    File "/root/miniconda3/envs/VMamba/lib/python3.10/subprocess.py", line 526, in run
      raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

  The above exception was the direct cause of the following exception:

  Traceback (most recent call last):
    File "<string>", line 2, in <module>
    File "<pip-setuptools-caller>", line 34, in <module>
    File "/root/autodl-tmp/VMamba/kernels/selective_scan/setup.py", line 146, in <module>
      setup(
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/__init__.py", line 117, in setup
      return distutils.core.setup(**attrs)
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 183, in setup
      return run_commands(dist)
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 199, in run_commands
      dist.run_commands()
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 954, in run_commands
      self.run_command(cmd)
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/dist.py", line 950, in run_command
      super().run_command(command)
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 973, in run_command
      cmd_obj.run()
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/wheel/_bdist_wheel.py", line 378, in run
      self.run_command("build")
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 316, in run_command
      self.distribution.run_command(command)
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/dist.py", line 950, in run_command
      super().run_command(command)
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 973, in run_command
      cmd_obj.run()
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/_distutils/command/build.py", line 135, in run
      self.run_command(cmd_name)
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 316, in run_command
      self.distribution.run_command(command)
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/dist.py", line 950, in run_command
      super().run_command(command)
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 973, in run_command
      cmd_obj.run()
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/command/build_ext.py", line 98, in run
      _build_ext.run(self)
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 359, in run
      self.build_extensions()
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 873, in build_extensions
      build_ext.build_extensions(self)
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 476, in build_extensions
      self._build_extensions_serial()
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 502, in _build_extensions_serial
      self.build_extension(ext)
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/command/build_ext.py", line 263, in build_extension
      _build_ext.build_extension(self, ext)
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 557, in build_extension
      objects = self.compiler.compile(
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 686, in unix_wrap_ninja_compile
      _write_ninja_file_and_compile_objects(
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 1774, in _write_ninja_file_and_compile_objects
      _run_ninja_build(
    File "/root/miniconda3/envs/VMamba/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 2116, in _run_ninja_build
      raise RuntimeError(message) from e
  RuntimeError: Error compiling objects for extension
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for selective_scan
Running setup.py clean for selective_scan
Failed to build selective_scan
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (selective_scan)

正常情况下，nvcc 不会出现在 conda env 目录中，而是出现在 /usr/local/cuda-?/ 中的 cuda 路径中。
我为您安装相应的Linux版本（例如ubuntu）支持的官方源建议存储库（或其镜像）提供的nvidia-drivers，并使用nvidia-official运行文件（安装在/usr/local/）安装cuda库。您安装的 cuda 版本受驱动程序支持，并且与您的 conda env 或 pip env 中安装的两个版本。

感谢回复


chore: update github action v1 to v2

update github action v1 to v2

v2 is faster than v1
https://github.com/actions/checkout#whats-new

@acao
Hello, hope you're doing well.
Could you review this PR?
Thanks!

@Gumichocopengin8 thank you!


Update README.md

Update readme with information about Educates now being Learning Center for TAP

@dambor Can you merge this?


Add Prometheus e2e simple flow

Issue #, if available: https://github.com/aws/eks-anywhere-packages/issues/639
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold
Need Prometheus to be moved to prod packageBundle first

/unhold Prometheus has been added to the prod packageBundle

/lgtm

/approve

/cherrypick release-0.13


Progress Buffer feature

Area
UI Components
The problem
Needing bufferValue feature:
https://mui.com/material-ui/react-progress/#linear-buffer
TBD: business use case for this
The solution
n/a
Alternatives and examples
n/a
Are you a JPMorgan Chase & Co. employee?

[X] I am an employee of JPMorgan Chase & Co.

Closed by #3090


ICC Color Profiles

For tile sources where it is available, we should explicitly either apply or not apply the ICC profile.
I imagine there would be three options: default, apply, ignore, where default should apply the profile to image outputs but not to numpy outputs.

See https://pillow.readthedocs.io/en/stable/reference/ImageCms.html#cmsprofile

See also https://github.com/ghsmith/SVSUtil


TFLu: Fix Ethos-U build errors

-Fix variable length array error in conv_test.
-As for now, suppress -Wdouble-promotion in Ethos-U operator until it is
resolved in Flatbuffers.

This is the flexbuffer error:
18:25:16  tensorflow/lite/micro/tools/make/downloads/flatbuffers/include/flatbuffers/flexbuffers.h:1420:25: error: implicit conversion increases floating-point precision: 'float' to 'double' [-Werror,-Wdouble-promotion]
18:25:16      Value(float f) : f_(f), type_(FBT_FLOAT), min_bit_width_(BIT_WIDTH_32) {}
18:25:16                         ~^
18:25:16  1 error generated.

The flexbuffers error has been fixed by this PR: https://github.com/google/flatbuffers/commit/dca12522a9f9e37f126ab925fd385c807ab4f84e So I will undo the change in tensorflow/lite/micro/kernels/ethos-u/ethosu.cc

The existing code doesn't really follow the style guide and is worth fixing, IMO.
My hope is that the following two PRs will fix your issue:

I have created #43858 to get the code to conform to the style guide and hopefully also fix the issue with VLA.
And @njeffrie has separated out the flatbuffer upgrade to its own PR #43856

OK, good. Let's close this PR then.