nrf5340: retained memory GPREGRET driver faults due to using wrong address

Describe the bug
If using GPREGRET1 on an nRF5340-based board with the retained memory driver, the board will fault with an odd address - 0x551c. There appears to be something wrong in dts land because the addresses should be getting remapped by this code:
                peripheral@50000000 {
                        #address-cells = <1>;
                        #size-cells = <1>;
                        ranges = <0x0 0x50000000 0x10000000>;

                        /* Common nRF5340 Application MCU
                         * peripheral description
                         */
                        #include "nrf5340_cpuapp_peripherals.dtsi"
                };

Which has this in the included file:
power: power@5000 {
        compatible = "nordic,nrf-power";
        reg = <0x5000 0x1000>;
        interrupts = <5 NRF_DEFAULT_IRQ_PRIORITY>;
        status = "okay";
        #address-cells = <1>;
        #size-cells = <1>;

        gpregret1: gpregret1@551c {
                #address-cells = <1>;
                #size-cells = <1>;
                compatible = "nordic,nrf-gpregret";
                reg = <0x551c 0x1>;
                status = "okay";
        };

        gpregret2: gpregret2@5520 {
                #address-cells = <1>;
                #size-cells = <1>;
                compatible = "nordic,nrf-gpregret";
                reg = <0x5520 0x1>;
                status = "okay";
        };
};

However, seemingly, DT_INST_REG_ADDR() is returning 0x551c for this and not the remapped address of 0x5000551c
Expected behavior
Driver should work and address returned should be shifting up which it is not
Impact
Showstopper
Environment (please complete the following information):

Commit SHA or Version used: 789addb02f6cd7479601ed3b487bcf57c2a3919c

@mbolivar-ampere is this a bug in the dts tools/parsing? Seems that the parent here gets the address updated (0x50005000), but it's child nodes do not (0x551c)

This is not a bug; the power node does not have a ranges property, so the address space of its child nodes is a completely distinct address space.
If you want to translate gpregret1 and gpregret2 addresses into the parent address space, add a ranges property to the power node appropriately. See the DT spec for details.


IPv6 Support

Do you have any plans to support IPv6 with this script?

This is not really possible or viable at this point with most VPS providers.
Previous issues had been opened about this if you want further detail.

So from what I can guess, most of the tickets that have been opened, people have been wanting to connect to their server with IPV6, but what I am looking for is allowing IPV6 connectivity when connected to the VPN.

what I am looking for is allowing IPV6 connectivity when connected to the VPN.

That's the issue actually. Connecting via IPv6 is simple. Providing IPv6 to clients needs either a fully routable subnet (which isn't available for most users with IPv6) or IPv6 NAT (which is an ugly workaround and only recently supported).
TL;DR: no IPv6 in the near future.


Introduce the generalized constant form

I'm not super happy with the wording, please feel free to suggest something better

I'm going to go ahead and land this since I want to tweak it slightly as part of a larger update to the explainer.


feat: add baidu translation impl

Describe what this PR does / why we need it
The implementation of the Baidu translation component
Does this pull request fix one issue?

#98
Describe how you did it
With Baidu translation Open APIs
Describe how to verify it
I implemented a text translation and here are two examples:
success

failure

Special notes for reviews

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

请使用 maven 配置文件：许可证环境构建许可证标头

Thanks, I changed the other problems first, and when you merge your pr, I can use the plugin to change the license. QAQ


Could Not invoke EscPosPrinterDiscovery.enableLocationSetting

Hi, Thank you for the 4.0 update, just tried the latest version 4.0.1, Im facing this error with usePrintersDiscovery call, may I ask did I missed any dependency? My App is in a Monorepo setup and use to work good with https://github.com/januslo/react-native-bluetooth-escpos-printer

I'm running into the same issue. What's the fix here?

@ronanru  I guess you com.google.android.gms:play-services-location dependency in Android somewhere and it could conflict with the lib.
@TrustyTechSG how you resolved this?

hi @tr3v3r , I never resolved it, I was try to walk around it by use my existing library to do the scanning and then use this new 4.0 SDK to do the printing, but again facing another "Invalid params" error with the printer.connect call.
Tried to search in my project only find dependencies classpath 'com.google.gms:google-services:4.4.1', have no idea what is the root cause of this.

Could you please check on the bare app ( clear RN )? Or try run example folder and check if issue exist.
If it  is reproducible I can try to help.
But I think it is connected with some of the dependencies you're using in your app.
Please check what js libs or native libraries use com.google.android.gms:play-services-location?

@tr3v3r I managed to reproduced it, it is caused by expo-location, simply install expo-location then you will face this error by calling start function from usePrintersDiscovery.

Its the same when https://github.com/michalchudziak/react-native-geolocation is installed

ok I'll try to update 'com.google.android.gms:play-services-location'

Just released 4.1.4 with the fix.
I'd appreciate if you could validate if everything is OK now
@sweebee @TrustyTechSG @ronanru

@tr3v3r Nice, tested and working!


Revert the ExecutionContext after processing requests

If user code modifies the ExecutionContext it could leak to the next http request. This happens because nothing reverts to the original on the way out. We piggy back on the async state machine logic to do this.
Added a test

PS: I'm guessing this potentially regress the performance so this solution might not be the final one (depending on results).
Fixes #13991

Are you planning to rewrite this to manually capture and restore the execution context before merging @davidfowl?

Yes but I want to measure this first and try out the new API I proposed here https://github.com/dotnet/corefx/issues/41131

@davidfowl What are we doing here? There are two PRs, this one and @benaadams 's one https://github.com/aspnet/AspNetCore/pull/14146 . Seems like the sentiment in the triage room is that we like @benaadams 's one better.

@davidfowl What are we doing here? There are two PRs, this one and @benaadams 's one #14146 . Seems like the sentiment in the triage room is that we like @benaadams 's one better.

Agree, waiting for performance runs to test the changes. I'll close this one.


.card-columns break card layout in v4

In Bootstrap 4 Alpha 4, card-columns split card in half and then display card in two column. See picture:

Also, the jsbin example:
https://jsbin.com/robemogiba/edit?html,output
The problem doesn't exist in Bootstrap 4 Alpha 3
P/s: I am using OSX Yosemite with Chrome version 52.0.2743.116 (64-bit)

Dupe for #20654

Yeah, closing as a duplicate.


refactor: custom mock was replaced with gomock

gomock instead of  custom mock (introduce protocol)

Part of https://github.com/hyperledger/aries-framework-go/issues/269
Signed-off-by: Andrii Soluk<EMAIL_ADDRESS>

@soluchok a suggestion - Can we update the commit title to better align with the changes ie prefix with feature/protocol that we are changing ? eg. "refactor: Introduce - replace custom mock with gomock'. We use custom mocks in many places and the title without prefix might infer that we are replacing all of custom mocks with gomock.


sap_hana_preconfigure: Set THP to madvise from RHEL 9.2 onwards

Solves issue #879 .

We better also assert the current setting of THP and set it on the running system, as we also do for KSM.


Toggle requires 3 clicks before "flipping"

First off, awesome job on the toggle switch and dark theme. It looks great. I noticed some issues with this first go of it.
After giving the toggle focus with that first click, the clicking the toggle again doesn't actually "flip" the toggle and apply the dark theme. I noticed this only happens if you don't have any cookies or history from CW where the toggle has already been successfully "flipped". If you don't, you have to click on the toggle three times before it flips and the dark theme applies.
If you have already flipped the toggle once though, then it works as expected so long as you have that history in your browser cache. Clear that history though, and you've got to click on the toggle three times again before it starts working as intended.

Screen Capture: Calcite Web on Safari 11.0.3 running on OSX 10.3.3
I tested the issue on a few different browsers and found it impacted all of the ones I tested with.

Safari 11.0.3 on OSX 10.13.3
Safari Mobile on iPhone running iOS 11.2.6
Chrome 64.0.3282.186 x64 on Windows 7 x64

I did not check to see if the issues appeared on Firefox or Chrome for OSX since I don't have those browsers.

Will 👀 at this today, thanks.


ConnectionBanner component #2

Ready for review: https://deploy-preview-10--sharp-bardeen-c4599c.netlify.com/?path=/story/connectionbanner--wrong-network-default


nixos/flatpak: pass system fonts

Fixes https://github.com/NixOS/nixpkgs/issues/119433
Description of changes
If fonts.fontDir.enable is true, then we also pass down the system fonts to the flatpak service. This is done through a special x11 fonts build that copies all font files instead of linking them. This allows the flatpak config to remain unchanged -- /nix/store can remain unexposed for fonts to work.

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Ooops sorry I messed up the push. Let me create a new PR.


fix(TrackObjectGrabAttach): dropping objects early - fixes #1563

maxDistanceDelta being a constant caused the magnitudes of the
calculated positional and angular velocities to not be limited properly.
This resulted in the held objects getting dropped prematurely without
properly detaching them: The objects were attached in theory but not
following the controller as intended.
The solution is to change the constant to the predefined velocity limit,
causing the magnitude to limit properly to fit the later if-statements.

I don't think this is a viable solution.
It only actually makes sense if the velocity limit is lower than 10f
If the velocity limit is 20f for instance and your max distance delta then also becomes 20f, then you get unexpected results.
I would say a better fix would be having additional parameters for allowing custom settings of angular velocity distance delta and velocity distance delta.

Superseded by https://github.com/thestonefox/VRTK/pull/1600


Move osmoassert into osmoutils, remove osmoutils twap dependence

What is the purpose of the change
Pre-requisite for moving osmoutils into its own go.mod

Merging as sub-component of #3788


warning about GO15VENDOREXPERIMENT showing up even though it's not set

Hi,
I get this error every time I invoke godep now:
godep: WARNING: Go version (go1.6) & $GO15VENDOREXPERIMENT= wants to enable the vendor experiment, but disabling because a Godep workspace (Godeps/_workspace) exists
but $GO15VENDOREXPERIMENT is not set:
➜  ~ echo $GO15VENDOREXPERIMENT

I see I can do
export GO15VENDOREXPERIMENT=0 and it will go away, but for new terminals of course the warning will still show up unless I explicitly put export GO15VENDOREXPERIMENT=0 into my shell rc.
I'm guessing this is why:
(v == "go1.6" && go15ve != "0")
I'm fine putting export GO15VENDOREXPERIMENT=0 into my shell rc for now, so feel free to close this if you'd prefer not to take action on it.

This warning is there to tell you that your combo version of go and config vars is telling godep to use the vendor experiment, but godep disables it because it found an existing old style godep workspace.
Exporting GO15VENDOREXPERIMENT=0 disables the vendor experiment, so the warning goes away.
Maybe I should make the warning clearer somehow?
Sent from my iPhone

On Mar 10, 2016, at 22:40, Shawn Smith<EMAIL_ADDRESS>wrote:
I see I can do
export GO15VENDOREXPERIMENT=0 and it will go away, but for new terminals of course the warning will still show up unless I explicitly put export GO15VENDOREXPERIMENT=0 into my shell rc.
I'm guessing this is why:
(v == "go1.6" && go15ve != "0")
I'm fine putting export GO15VENDOREXPERIMENT=0 into my shell rc for now, so feel free to close this if you'd prefer not to take action on it.
—
Reply to this email directly or view it on GitHub.

@freeformz it's okay, I just thought that not having the GO15VENDOREXPERIMENT set at all should be the same as having it set to GO15VENDOREXPERIMENT=0. No worries.


Update installation docs to v0.5.1

@tillkruss Do you have a (public) release checklist? I could contribute to it.

e.g. update all CI ... oooor publish supported Relay versions in JSON format 🎉

e.g. update all CI ... oooor publish supported Relay versions in JSON format 🎉

We could do that. How would you want it to look?

https://OUR-R2-BUCKET/supported-versions.json
{'0.4.6','0.5.1'}


Fixed bokeh LayoutPlot bugs

Turns out that the bokeh LayoutPlot implementation was wrong in all kinds of subtle ways so I've completely rewritten the implementation from scratch. The main issue was that AdjointLayout plots were not correctly positioned on the grid. Secondly when enabling tabs AdjointLayout plots were split across multiple tabs.

[x] Fixes https://github.com/ioam/holoviews/issues/1489
[x] Fixes https://github.com/ioam/holoviews/issues/2568
[x] Fixes https://github.com/ioam/holoviews/issues/2652
[x] Adds unit test

Ready to review and merge.

Turns out that the bokeh LayoutPlot implementation was wrong in all kinds of subtle ways...

Why do I feel deja vu? ;-p
To be fair it has always been very tricky code and I am always happy to see it refactored and improved. I've had to restart a test build for what I assume was a transient but otherwise I am happy to merge.
The only thing I would ask you to consider is whether there is another unit test or two you could add. The more unit tests the better given how tricky it is to get right!

Why do I feel deja vu? ;-p

I think this code has been around since I first wrote the bokeh backend, so it has actually held up surprisingly well, unlike the matplotlib version.

The only thing I would ask you to consider is whether there is another unit test or two you could add. The more unit tests the better given how tricky it is to get right!

Added a unit test for the tabs issue, layouts themselves have enough unit tests covering them.

Added a unit test for the tabs issue, layouts themselves have enough unit tests covering them.

Thanks. I'll merge when the tests go green.


Review crowdloans feature

Describe the task

[x] Review crowdloans feature:

[x] Data is missing (Check with address 12Mx6Cp4Z672y13xPDZy9QH2wLDVpQdisdk56Nf6QPnjSLVy)
[x] Data is incorrect

[x] Update the new crowdloans project

Version test for extension: http://<IP_ADDRESS>:8900/s/ySE2gmYJiN84pze
Version test for webapp: https://0f000153.subwallet-webapp.pages.dev/
Validation passed these cases


Transition black-adder and tiffon to Emeritus Maintainers

According to the policy established in #2733.
Once this is merged, the @jaegertracing/jaeger-maintainers group will be updated accordingly.

@jaegertracing/jaeger-maintainers – I just want to say it was an honor being a part of the Jaeger project. What an incredible learning experience and I can honestly say it was some of the most satisfying work I've done. Thanks to everyone!
Best,
Joe

@jaegertracing/jaeger-maintainers – I just want to say it was an honor being a part of the Jaeger project. What an incredible learning experience and I can honestly say it was some of the most satisfying work I've done. Thanks to everyone!
Best,
Joe


Implement redis-py API

This PR changes how znsocket behaves and reimplements parts of the redis-py API.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

154 of 238 (64.71%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-4.6%) to 68.421%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

znsocket/client.py
36
43
83.72%

tests/test_connection.py
30
54
55.56%

znsocket/server.py
83
136
61.03%

Totals

Change from base Build<PHONE_NUMBER>:
-4.6%

Covered Lines:
195

Relevant Lines:
285

💛  - Coveralls


Add emoji support

This uses the Emoji map from https://github.com/kyokomi/emoji -- but with a custom replacement implementation.
The built-in are fine for most use cases, but in Hugo we do care about pure speed.
The benchmarks below are skewed in Hugo's direction as the source and result is a byte slice,
Kyokomi's implementation works best with strings.
Curious: The easy-to-use strings.Replacer is also plenty fast.
BenchmarkEmojiKyokomiFprint-4  	   20000	     86038 ns/op	   33960 B/op	     117 allocs/op
BenchmarkEmojiKyokomiSprint-4  	   20000	     83252 ns/op	   38232 B/op	     122 allocs/op
BenchmarkEmojiStringsReplacer-4	  100000	     21092 ns/op	   17248 B/op	      25 allocs/op
BenchmarkHugoEmoji-4           	  500000	      5728 ns/op	     624 B/op	      13 allocs/op

Fixes #1891

@moorereason I have adjusted re your comments. Please merge if you think it looks OK.

:+1: Merged in cafb784.


More UI crashes

At first the UI was blank and i was seeing 'network error' in the UI
this was in my console  ((same error i usually see)
`Access to fetch at 'https://rpc.ankr.com/eth' from origin 'https://amarok.bridge.connext.network' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
AFTER refreshing, i saw this in the UI
missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (data="0x", transaction={"to":"0xEE9deC2712cCE65174B561151701Bf54b99C24C8","data":"0xf1537686000000000000000000000000ff970a61a04b1ca14834a43f5de4533ebddb5cc8","accessList":null}, error={"reason":"missing response","code":"SERVER_ERROR","requestBody":"{"method":"eth_call","params":[{"to":"0xee9dec2712cce65174b561151701bf54b99c24c8","data":"0xf1537686000000000000000000000000ff970a61a04b1ca14834a43f5de4533ebddb5cc8"},"latest"],"id":43,"jsonrpc":"2.0"}","requestMethod":"POST","serverError":{},"url":"https://rpc.ankr.com/arbitrum"}, code=CALL_EXCEPTION, version=providers/5.7.2)

It's an RPC error.

Updated RPCs.

Haven't supported this from past couple of days, closing this issue.


fix(build.sh): export get_config_value and set_config_value to make ublue-update installer work

Dunno why the functions got deleted in the script, saw get_config_value was there, but wasn't exported, just fixed it up real quick. Noticed the issue when automatic updates with rpm-ostreed were still enabled when using the bling module to install ublue-update

I never created such functions, I just assumed this is something you added in while PRing in the ublue-update installer, apparently not.
No idea what these do, though. Some comments would be warranted.

originally the functions were included with the modules, I don't know how they got removed, i'll add them back in https://github.com/ublue-os/bling then

reopening this to simply delete the set_config_value function inside build.sh

nvm it was never defined, all good

New PR to fix this: https://github.com/ublue-os/bling/pull/37


Minimum MongoDB version

What part of the documentation isn’t clear?
While the documentation specifies that MongoDB is a requirement for some features to work, the minimum version of MongoDB is not documented.
The issue is that MongoDB is distributed under the SSPL license. This license makes it a non-free/libre/open-source tool.
The last version of MongoDB to be released under AGPLv3 was v4.0.3. Would this version be sufficient for the needs of running IndieKit?
How could the documentation be improved?
Add a line referring to the minimum MongoDB version required for IndieKit
Additional context
No response

On a related note, I'm stuck on MongoDB 4, as MongoDB 5+ requires CPU features not supported by the NAS where I host Indiekit. If Indiekit were ever to require MongoDB 5+, I'd need to figure out some new infrastructure to host it.

Prisma looks cool, though I don't think being able to change the database provider is supported due to confusion about what features are supported where.
https://www.prisma.io/docs/concepts/components/prisma-schema/data-sources
https://github.com/prisma/prisma/issues/3834

@aciccarello Hmm. This might not be an issue; I was thinking more of being able to support different databases; but once you have chosen one platform, you can’t migrate to another. But need to investigate further.

FerretDB might be good MongoDB replacement to evaluate.
https://blog.ferretdb.io/ferretdb-1-0-ga-opensource-mongodb-alternative/

Have added a note to the README and documentation website. I tried testing with MongoDB v4.0.3, but as this is now end of life, I couldn’t install it locally.
The project is know to work with v4.4 or later, and may work with the last openly licensed version but this has not been tested.
More broadly speaking, I think this issue further supports the case for Indiekit providing support for different database types, as mentioned previously in this thread.


Service Discovery

Hello,
Environment info:

KrakenD version: devopsfaith/krakend:2.1.2
System info: Ubuntu 20.04 LTS / docker engine 20.10.17
Hardware specs: 16CPU/10Go Memory

Describe the bug
I want to set  the Service Discovery by using DNS SRV RECORD, but I have this issue :
{"@timestamp":"2023-04-13T15:44:16.922+00:00", "@version": 1, "level": "ERROR", "message": "[ENDPOINT: xxx] no hosts available", "module": "KRAKEND"}
[GIN] 2023/04/13 - 15:44:16 | 500 |      86.964µs |   <IP_ADDRESS> | GET      "xxx"
Error #01: no hosts available
Nevertheless, the DNS server return the correct information :
17:44:26.586003 IP <IP_ADDRESS>.44657 > xxx.local.domain: 4478+ [1au] SRV? _api.._tcp.mds.local. (50)
17:44:26.586017 IP <IP_ADDRESS>.55777 > xxx.local.domain: 34244+ [1au] SRV? _api.._tcp.mds.local. (50)
17:44:26.587021 IP xxx.local.domain > <IP_ADDRESS>.55777: 34244* 1/0/2 SRV xxx.domain.:5001 0 0 (105)
from the docker host, the resolution is correct:
nslookup

set type=srv
_api._tcp.mds.local

_api._tcp.mds.local     service = 0 0 5001 xxx.domain.
by using curl, the service is responding
<IP_ADDRESS> : container's IP
xxx.local.domain : DNS server
Your configuration file:
"endpoint": "xxx",
"input_headers": [
"*"
],
"input_query_strings": [],
"method": "Get",
"output_encoding": "no-op",
"extra_config": {},
"backend": [
{
"url_pattern": "xxx",
"encoding": "json",
"sd": "dns",
"method": "Get",
"extra_config": {},
"disable_host_sanitize": true,
"host": [
"_api._tcp.mds.local"
]
}
]
thanks for you help

Hello team,
i fixed it by using  priority and weith on my SRV record.
but now i have a new issue
Error #01: Get "http://XXX.:XXX/v1/XXX/XXX": EOF
Now, krakend send the request to the good  destination host  by used  http schema, how to switch to https
i suspect the schema to be hard coded  : https://github.com/luraproject/lura/blob/master/sd/dnssrv/subscriber.go
line 136
thanks for your help

Hello @MDS-Info,
You are right, the protocol is hardcoded. We can add a new flag in the configuration sd_protocol that would default to the value http but you could change it to https.
There would still the limitation that you couldn't mix http and https servers, but the DNS SRV does not provide any mechanism to prevent that.
We will have a look at this issue in the next release.

The attribute sd_scheme was added in KrakenD 2.4
https://www.krakend.io/docs/backends/service-discovery/#sd_scheme
Thanks!


Unbrick r30gb

Hi  @roleoroleo
I bricked my Yi Dome Guard Camera with my backup after i didn't soft reset succesfully. The cam has permanent red light.
I've readed your how to hard unbrick, but how you can see in the photo my board hasn't GND, RX & TX to solder with my USB-TTL.
I'll aprecciate any suggestion.
Thanks!

Maybe is this?
TP3 -> GND
TP2 -> TXD
TP1 -> RXD

Ok! I tried again with soft method with my old backup and i had configured the cam with the YI app succesfully.
But when I try to hack with yi-hack after the reboot the led still permanently blink green without connection.
Any idea?

Try to restore again backup partition.
But load a backup file obtained with this procedure:
https://github.com/roleoroleo/yi-hack-Allwinner-v2/tree/master/unbrick
using the "hacked" option
./build.sh hacked
When you restart the cam, it should be already preapred fot the hack.
And the hack procedure shouln't brick the cam.

I got install again the hack with 0.2.1 firm. I think that the mistake was in the wifi config. Once I copied the key and SSID the cam works perfect with the firmware. Therefore this post can be closed succesfully! :)
Thank you again @roleoroleo !!!


Display Jib tasks runnable from the root Gradle project

Description of the issue:
gradle tasks does not display Jib tasks. However, listing all available tasks using gradle tasks --all lists Jib tasks in the group "Other tasks". gradle tasks shows a task if  task group description is not empty.
Expected behavior:
gradle tasks should display the Jib tasks runnable from root project in a group named e.g. "Jib tasks".
Steps to reproduce:
Starting from the Jib project root:
➜  jib git:(master) cd examples/spring-boot-draft
➜  spring-boot-draft git:(master) ./gradlew tasks 2>&1 | grep -i -B2 jib
➜  spring-boot-draft git:(master)

➜  spring-boot-draft git:(master) ./gradlew tasks --all 2>&1 | grep -i -B2 jib
Other tasks
-----------
_jibSkaffoldFiles
--
eclipseJdt - Generates the Eclipse JDT settings file.
eclipseProject - Generates the Eclipse project file.
jib
jibBuildTar
jibDockerBuild
➜  spring-boot-draft git:(master)

Environment:
./gradlew --version
------------------------------------------------------------
Gradle 4.10.2
------------------------------------------------------------

Build time:   2018-09-19 18:10:15 UTC
Revision:     b4d8d5d170bb4ba516e88d7fe5647e2323d791dd

Kotlin DSL:   1.0-rc-6
Kotlin:       1.2.61
Groovy:       2.4.15
Ant:          Apache Ant(TM) version 1.9.11 compiled on March 23 2018
JVM:          1.8.0_201 (Oracle Corporation 25.201-b09)
OS:           Linux 4.18.0-15-generic amd64

@aivantsov v1.0.2 released with your fix. Thanks for your contribution.


Adapt existing actions to API v1.24

This pull request adapts the existing actions to API v1.24 without adding the new actions (e.g. plugins, etc).
It also fixes some minor typos and outdated links.

:warning: seems like /build regexp is not working properly. Working on it!

Thanks @yan-foto left some comments in the review, also, please rebase your commits.

Thanks @liron-l ! I also added some comments. The changes as of this PR are minor and doesn't reflect the whole new API v1.24. I could also add them if I come to it!


Security: Use of strncopy() function in "Get Started" project

From @prafullkotecha on February 14, 2018 2:8
Here's the message from devskim plugin:
[Devskim: Finding DS111237]
Banned C function detected (strncpy)
Severity: [Important]

strncpy is dangerous, as if the source contains 'n' or more characters, it will not null terminate the destination.

Fix Guidance: Use strcpy_s or strlcpy if possible. If no safe function is viable, strcpy/strncpy should be proceeded by conditional checks to verify tha that the source string will fit in the destination with a null termnator.

More Info:
https://github.com/Microsoft/DevSkim/blob/master/guidance/DS111237.md
#define strncpy(dest, src, len) __builtin___strncpy_chk(dest, src, len, __builtin_object_size(dest, 1))

Copied from original issue: Microsoft/azure-iot-developer-kit#322

Tested on the new code, there is no strncopy() function found, and the GetStarted example works well. We will re-check it when the prod version is ready.


Multiple apps found matching input criteria when trying to install Microsoft.dotnet

Brief description of your issue
When I try to update Microsoft.dotnet, winget does not respect -e flag
Steps to reproduce
Have dotnet SDK installed without winget
run any of the following:
winget upgrade -e --id "Microsoft.dotnet"

winget upgrade --id "Microsoft.dotnet" -e

winget upgrade -e "Microsoft .NET SDK"

 winget upgrade Microsoft.dotnet

Expected behavior
The flag is respected and update proceeds normally
Actual behavior
No matter what combination of flags is used the Multiple installed packages found matching input criteria. Please refine the input. error is displayed

Environment
Windows Package Manager v1.1.12702
Windows: Windows.Desktop v10.0.22489.1000
Package: Microsoft.DesktopAppInstaller v1.16.12702.0

====
Conflicting software:
Microsoft .NET SDK               Microsoft.dotnet
Microsoft .NET SDK 5.0.100 (x64) {c0d1830b-4a91-46dc-981e-ebf607e87cfc}

Duplicate of #1142


Action JIRA edits 2/10

@MilosDrobnjakovic  thanks for the suggestions, they have all been actioned. Please can you review.


Snippets for Session Management

Snippets demonstrate the Flask webapp environment. These will appear in https://firebase.google.com/docs/auth/admin/manage-cookies

I think developers will be able to port these samples to their preferred web frameworks. In case of Node.js we show samples assuming the Express framework.


fix an UD about parameters eval order

Signed-off-by: Yuchen Dai<EMAIL_ADDRESS>Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

Thanks! Did you observe any real issues here or just code inspection?

I haven't seen any real issue yet. Compilers are not that crazy, at least on x86.
As you guessed, it's code inspection when I am working on some sibling code.


Update the game over message

Update the game over message so people know how to play again!

Great work done


Streamlink and settings for it probably don't work

Streamlink has basic functionality, the "choose" setting just doesn't work as expected imo but maybe I just don't know how it's supposed to work.
I restructured the code a bit in ef9aedb2cdc50889470f8938c0e7f15a91ff7571 to easier give some console error messages in case the path is wrong.

So the issue with the "choose" not working might be due to default-stream=<quality> being used [in config], since it relies on the last line starting with "Available streams" that gets printed to stdout, when no quality and no --default-stream are specified.
There is no simple ways to prevent this, since streamlink does not include an option just to show quality options. It is possible to add --default-stream someinvalidbullshithere to force an error, but then "Available streams" part is indented [ I guess can be resolved with a trim ].


Handle unprocessed deletes without throwing an IllegalArgumentException

I started running into exceptions that looked like the following:
java.lang.IllegalArgumentException: Cannot find a dynamodb table for class software.amazon.awssdk.enhanced.dynamodb.Key
	at app.cash.tempest2.internal.DynamoDbLogicalDb.expectedRawItemType(DynamoDbLogicalDb.kt:390)
	at app.cash.tempest2.internal.DynamoDbLogicalDb.rawItemKey(DynamoDbLogicalDb.kt:376)
	at app.cash.tempest2.internal.DynamoDbLogicalDb.toBatchWriteResponse(DynamoDbLogicalDb.kt:308)
	at app.cash.tempest2.internal.DynamoDbLogicalDb.access$toBatchWriteResponse(DynamoDbLogicalDb.kt:65)
	at app.cash.tempest2.internal.DynamoDbLogicalDb$Sync.batchWrite(DynamoDbLogicalDb.kt:120)
	at app.cash.tempest2.LogicalDb.batchWrite(LogicalDb.kt:125)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at app.cash.tempest.internal.ProxyFactory$invocationHandler$1.invoke(ProxyFactory.kt:55)
[skipping the private part of the stack trace]

unprocessedDeleteItemsForTable returns Key, but line 308 tries to call rawItemKey() on it and chokes. The net result is that tempest can't handle unprocessed deletes. Removing the unnecessary conversion should resolve it.
I couldn't see a way to verify that this would solve the problem, as there don't seem to be any tests around unprocessedDeletes. I tried a similar approach to my test here, but there's no way to delete more than 16MB. There's a max of 25 items, and each one can be 400KB. If each one is as big as possible, you only hit 10MB. Without mocking the dynamo client, there's no way to trigger a failure here.
The easiest way to test this is probably to expose the toBatchWriteResponse as an internal function and unit test it - there isn't an existing practice of that in this project so I was hesitant to do so. Let me know if you'd like a test added that follows that approach.

This change looks like this should be breaking. I definitely want to get a test on this to confirm, especially that the old way breaks. One way to force a failure would be to set an actual throughput on the table and overload it with a large batch. I believe dynamodocker and dynamodb-local both respect non-zero values.
I did some spot checking on internal usage, and all the high volume stuff uses TransactionWrite for delete, which doesn't return unprocessed keys. Its possible we just haven't exercised this sufficiently, but I would still be surprised if this just never worked.

This change looks like this should be breaking. I definitely want to get a test on this to confirm, especially that the old way breaks. One way to force a failure would be to set an actual throughput on the table and overload it with a large batch. I believe dynamodocker and dynamodb-local both respect non-zero values.
I did some spot checking on internal usage, and all the high volume stuff uses TransactionWrite for delete, which doesn't return unprocessed keys. Its possible we just haven't exercised this sufficiently, but I would still be surprised if this just never worked.

Unfortunately local dynamo does not respect the limits (docs):

Provisioned throughput settings are ignored in downloadable DynamoDB, even though the CreateTable operation requires them.

@kyeotic Had a moment of brilliance - I realized that testing this is actually super easy. Added a test for it; the test fails if you revert my change


auto-import favors import from target instead of source

TypeScript Version:  4.0.0-dev.20200529
Verify no issue with vs code version 1.45.1 + typescript vsrion: 3.8
Verify issue with vs code + typescript 3.9.3
still have issue with vs code + typescript 4.0.0-dev20200529

Search Terms:
import / auto import
Code
we have project configure as
|
|-- sharedlib
       | -- src
       | -- dist
|-- package1
       | -- src
       | -- dist
|-- package2
       | -- src
       | -- dist

where src is *.ts source code, dist is where compiled *.js files
sharedlib/tsconfig.json
{"compilerOptions": {
    "rootDir": "./",
    "baseUrl": ".",
    "outDir": "dist",
    "paths": {
      "*": [
        "types/*"
      ]
    },
    "composite": true
  },
  "include": [
    "src/**/*.ts",
  ]
}

package1/tsconfig.json
{"compilerOptions": {
    "baseUrl": ".",
    "outDir": "dist",
    "rootDir": "./",
    "paths": {
      "*": [
        "../sharedlib/types/*"
      ],
      "sharedlib": [
        "../sharedlib"
      ]
    },
  },
}

sharedlib/src/foo.ts
export const foo = 1

package1/src/bar.ts
console.log(foo)

Expected behavior:
When in visual studio code + typescript 3.8
auto import will prompt me to import as
import foo from 'sharedlib/src/foo'

console.log(foo)

Actual behavior:
On typescript 3.9.3+
first, before compile sharedlib, it can't recognize foo, thus no auto import
after compile, it auto import the js from
import foo from 'sharedlib/dist/src/foo'

console.log(foo)

the problem are

now when I add new exportable in sharedlib, I have to compile the package first before I am write reference code from other packages
Because code write before/after ts 3.9 are import from different path even for same module, javascript will treat they as different modules, thus breaks states/singleton, if I didn't manually remove /dist from import

Playground Link:
Related Issues:

@chengB12 can you provide a repository with this problem? I think some important information got lost or mangled when you were distilling it down to a simple case. E.g., I think you’d need in your paths "sharedlib/*": ["../sharedlib/*"], not just the starless version, for any of this to compile under any TypeScript version.

Hi, I changed in paths, still same issue
I have created a sample project, how can I upload it?

@chengB12 thanks! This is helpful. I do see that an auto-import isn’t offered for foo, but I still can’t reproduce it offering to import from sharedlib/dist/src/foo after compiling. Can you provide exact steps on how to reproduce that?
Also, in the non-example version of this, are you using Lerna, yarn workspaces, or any other method of symlinking the packages together within node_modules?

Here is something interesting, I can't reproduce it with bare minimal
our original project having tons of export on ts-sharedlib, and our package1 has tons of import from ts-sharedlib. in this case vs code with ts 3.8 can infer from 'ts-sharedlib/src' and ts 3.9 can infer from 'ts-sharedlib/dist/src'
however, when I trying to strip all other files from package1, leaving only one example, and suddenly, neither ts 3.8 nor ts 3.9 can infer import anymore.
It sounds like vs code can be trained to auto import cross packages given enough success imports
either way, it sounds like a bug to me if bare minimal can't infer imports

Sorry I can't provide whole 'issue-reproducible' repo, if needed, I may be able to provide a few screenshots

When you remove all existing references from package1 to sharedlib, the lack of auto imports is currently expected behavior, tracked in #37812. The paths case is a good test case for #38923. But that’s a really well-understood problem, so the dist thing is much more concerning to me, but I can’t know whether or not it’s really a bug without seeing the whole project. For example, if you currently import sharedlib/dist/src/foo anywhere in package1, you’ll get that as a suggestion:

But I don’t think that’s a bug.

I can share a screenshot,
You can see, I have existing import from 'ts-sharedlib/src...'
and after I comment correct import line,
the auto-import I got is from 'ts-sharedlib/dist/src'

It’s not just the file that matters, though; it’s every file in the project and every file’s dependencies, those dependencies’ dependencies, and so on 😕. Would you be able to share TS Server logs?

We have lint to ensure no code use import xx from 'ts-sharedlib/dist/src...'
it shouldn't comes from existing imports
tsserver.log

Alright! I think I have a repro thanks to your logs. Hopefully last question @chengB12, when you click the lightbulb here, do you get an option for both src and dist/src like this?

No, I only get hint from sharedlilb/dist

Even if you add "ts-sharedlib/*": ["../ts-shardlib/*"] to paths?

with "ts-sharedlib/": ["../ts-shardlib/"] it display for both now, what's different between it and "ts-sharedlib": ["../ts-shardlib"]?

However, the problem is instead of hint for import from 'ts-sharedlib/src', it hint for '../../ts-sharedlib/src'

Are you using Lerna or yarn workspaces or something else that will symlink these packages together through node_modules? Or do you have an installed copy of these packages in node_modules?
The * in paths is a wildcard that will capture the rest of the module specifier request and substitute it for the * in the value [docs]. I’m honestly not sure how it’s even possible for you to resolve imports from ts-sharedlib/src without having the /* in paths, unless there’s something going on in your node_modules, which there doesn’t appear to be from your server logs.
Regarding the relative import, can you check your VS Code setting for TypeScript > Preferences: Import Module Specifier:

after change vs setting, it looks fine now,
regards how to resolve ts-sharedlib, I don't know, we don't use symlink. we have this line in tsconfig.json though
"references": [
    {
      "path": "../ts-sharedlib"
    }
  ]

probably this line do the trick?

Nah, that line is correct. I think you just need to keep your path mapping with the wildcard, and I’ll fix the bug that makes the extra suggestion from dist show up. Still not sure what’s going on with getting the dist suggestion when you don’t have the wildcard path mapping. If you can provide an isolated repro for that, I can investigate it separately.

How do imports from ts-sharedlib/src resolve at runtime? Are you publishing/packaging the dist directory of ts-sharedlib?

yes, we are publishing ts-sharedlib to ts-sharedlib/dist

side effect on that change:

Previously with wrong path setup, it can infer import from '../src', now it auto-import from 'src/' instead, which is not a correct path

I believe this is caused by outDir -- see https://github.com/microsoft/vscode/issues/103087

What this issue is complaining about is exactly the behavior you would want, since the src folder won't exist outside development.
Auto import suggestions started showing up for me (maybe because of ...experimental.enableProjectDiagnostics": true) on 3.8.3.  However it is inserting the wrong imports.  It is pointing to the source location instead of the output location.  I don't have paths set in any tsconfig files.  Lerna is hoisting the packages.  If I change the tsconfig for the referring package ("project"), to "disableSourceOfProjectReferenceRedirect": true, the suggested imports are correct.
I don't see why this setting should affect proposed imports.  The suggested imports should always be to the transpiled output, with disableSourceOfProjectReferenceRedirect determining whether the source file is the source of truth, or the generated .d.ts.

The problem is target won't exists when inside development, before compiling, and who need auto-imports outside development, I am curious.
Force compiling, otherwise, intelli-sense won't work properly doesn't sound right

Yes literally the last thing you'd ever want is auto imports to try to import the eventual dist path because YOURE IN THE DEV PATH - it should go to the relative (or absolute if there is a paths config) of the dev source so that once compiled the compilation step can either modify properly or do nothing if it is relative and will thus remain correct.
There is not a single case where you would want to import a dist resource from your src resource.  That's insane.

@bradennapier let’s keep the conversation less shouty and incredulous. The problem is that you can invent scenarios where any of these paths do or don’t work depending on exactly what you package/deploy/run, and the compiler simply cannot know that information today. There is definitely a bug here, but anyone here saying words like “always” and “never” is making assumptions that don’t hold for all configurations and all runtime circumstances that aren’t reflected in configurations.

My bad, didn't mean to imply shouting on the caps.

Just a question - in what case would you want your files in the src directory to auto import to the dist directory?  Should this not take paths into account to figure out where to import?
This recently started affecting our larger project for some reason, before it was only on a single package of ours that this was happening.

If i have a paths property in my tsconfig which indicates:
"paths": {
      "core/*": ["./core/*"],
      "services/*": ["./services/*"],
      "packages/*": ["./packages/*"]
    },

I would think it would realize that it should use packages/ (perhaps check if it exists first).
I have my editor settings to do absolute specifically but that doesn't seem to fix anything.

Where importing from dist might possibly make sense is if you have a monorepo with composite projects that you intend to publish to a package registry. Suppose you have
packages/
  app/
    src/**/*.ts
    dist/**/*.js, *.d.ts
  dep/
    src/**/*.ts
    dist/**/*.js, *.d.ts

In each, the rootDir is src and the outDir is dist. In app, you have either paths or node_modules symlinks set up to be able to reference ../dep/* as dep/*, because in production, app will install dep into its node_modules.
Now, suppose you’re trying to import something from dep into app during development. What should the module specifier be? The answer is pretty clear if the exported symbol is exported from dep’s main entrypoint in its package.json: the module specifier can just be "dep". But what if the symbol is from dep/src/some/sub/dir.ts / dep/dist/some/sub/dir.js, and that symbol isn’t available from just "dep"? Of the two paths, it seems likely that dist is better, since the JS and TS are not colocated. But that answer only really makes sense because I told you that dep is going to be published to a package registry and ultimately installed in app’s node_modules, which is something the compiler doesn’t know.
Your screenshot shows a relative import path to dist, which I do think is harder to justify. The OP here had a non-rooted import path to dist, like my example above. Either way, this particular behavior was an unintended side effect of fixing a related auto-import issue for yarn workspace / lerna users.

I have added the dist folder into exclude as well to try to resolve - perhaps this could be how we could indicate never to use dist for auto imports?

It just doesn’t work like that, in this particular case. The reason we look in dist even when you exclude it is so that if you are wanting to import a symbol from, say, ../dep/src/index.ts, which happens to be symlinked to ./node_modules/dep/src/index.ts, we want to see if the output file ./node_modules/dep/dist/index.js happens to match the "main" field in ./node_modules/dep/package.json, because if it does, we can just have you import from "dep". The bug is that when that process doesn’t yield the really nice module specifier "dep", we’re left with a random file in dist that we don’t know how to generate a module specifier for other than writing a path with dist in it, and we prematurely gave up on the other non-dist paths because we were hoping that it would yield just "dep".
It seems like you’re concerned that we’re not going to fix this or something, but that’s not the case; I’m working on it 🤷
What would be tremendously enlightening to me, if not directly helpful with this issue, is if you could explain why you’re using paths in the first place. In your example tsconfig snippet earlier, how do you suppose that an import from "core/*" will resolve at runtime? Is core going to be published to a package registry and installed in the other packages’ node_modules? If so, how do these things resolve during local runs and testing? I have always used lerna or yarn workspaces for this kind of thing, which means you don’t have to use paths.

Thanks @andrewbranch not worried it won't be fixed, was just curious for real cause I was trying to think of a case :-P, thanks for the descriptive response though!
The paths are used to remove relative imports and is a fairly common request from people (there are lots of issues around this).  It is a common pattern with webpack for example to add a resolve.alias to handle this so that your src dir is always allowed to imported as an absolute.
I accomplish this in typescript by adding https://github.com/zerkalica/zerollup as a plugin, but this issue would occur for anyone using webpack or rollup as example as well, or https://github.com/dividab/tsconfig-paths -- but there are probably around 10-12 packages all to deal with these cases.
eslint plugins also exist specifically for this https://github.com/alexgorbatchev/eslint-import-resolver-typescript

@andrewbranch I believe I'm still running into this, even with the current TS version:

Note that this is an import from within the same project.
Other suggestions are all kinds of weird:

From top to bottom:

index.d.ts in the current project's root dir, which re-exports from ./Values (this file is copied during the build)
index.ts in the current project's src dir, which re-exports from ./src/Values/index.ts (source file for the 1st suggestion)
index file for the referenced project @zwave-js/core (preferred import, because its the referenced project's main export)
Values.d.ts in the current project's root dir, which re-exports from @zwave-js/core (this file is copied during the build)
Values.ts in the current project's src dir, which re-exports from @zwave-js/core (source file for the 4th suggestion)
Absolute path (relative to baseUrl) to the original source (where suggestion 3 exports from). Using this path would be completely invalid.

Tbh, I haven't figured out a good way to import sources from the current project with a relative path and from referenced projects using their absolute path. Sometimes it works, sometimes it doesn't 🤷♂

@AlCalzone  for me, I solve this issue by

use nightly typescript build
specify in paths in tsconfig.json

{
   paths: {
        "zwave-js/src": [ "../zwave-js/src/*" ]
   }
}

Imports that refer to the target location are working for me, even when the source has not been built and the target location does not exist.  And of course such imports work as expected at runtime.  This works with just project references, without any need to configure a "paths" entry in tsconfigs.
So a source file can import shared/dist/foo, and TS uses node resolution, finds the hoisted shared package, doesn't find dist/foo, but is able to resolve to the .ts source file (in its original, non-hoisted location) that will eventually produce it.

I do have paths configured, because the directory structure is a bit different than the package names that are released later on. My first problem should is not affected by paths though, since it is an "internal" import.
The 2nd one does go away once there is one import in the current file that points to the correct location. When it is not, I think this heuristic makes sense:

Prefer symbols that are exported from another project's main entry point
In the current project, prefer symbols that are just exported (i.e. at the definition site) over ones that are re-exported

from comment of https://github.com/microsoft/TypeScript/pull/40253
this is fixed by checking paths first to look up matches, so changing paths to make what you want it to be recommended in auto-import works for me

I believe I'm still running into this, even with the current TS version:

@AlCalzone can you confirm which nightly you’re using?

My first problem should is not affected by paths though, since it is an "internal" import.

It’s affected by baseUrl. You may want to remove that setting once #40101 is merged. I also plan to explore adding a setting that makes it so that imports within a project prefer relative imports.
That said, I want to keep this thread focused on the original problem—there’s a lot of other auto-import work to be done in this release, and it will get harder for me to track if all the different issues become about auto-imports broadly. The only thing relevant to this issue is the fact that you got the Constants import both from build and from src. If you can definitely reproduce this with a recent nightly, is this an open source repo I could clone to reproduce? That would be very helpful. Thanks!

can you confirm which nightly you’re using?

20200909

I also plan to explore adding a setting that makes it so that imports within a project prefer relative imports.

That would be lovely!

is this an open source repo I could clone

Yep :)

clone https://github.com/AlCalzone/node-zwave-js/tree/c48522b5c9365428a50493f723f99111271f8dca
npm install
open packages/zwave-js/src/lib/commandclass/AlarmSensorCC.ts
delete line 14: import { MessagePriority } from "../message/Constants"; - you'll get an error in line 163
toggle quick fixes on MessagePriority

@AlCalzone something in your build produces a bunch of .d.ts files in the root level of packages/zwave-js that import directly from build. These root-level declaration files are not excluded by your tsconfig, so these outputs become future inputs. So, this behavior is expected, although we have https://github.com/microsoft/TypeScript/issues/40195 to track adding an error/warning for this, since a lot of people end up in this situation accidentally. I didn’t dig into your build process to understand whether it’s intentional or not in your case.

Thanks, that explains it. In my case it is intentional, because it simulates Node.js's sub-module exports.

In that case, you probably just need to tweak your tsconfig.json include/exclude to make sure the editor doesn’t see those files.

@andrewbranch That seems to work :)


TypeError: invalid type promotion when reading multi-file dataset

I'm trying to select data from a collection of weather files. Xarray opens the multifile dataset perfectly, but when I try the following selection:

cfsr_new = xr.open_mfdataset('*.grb2.nc')

lon_sel = np.array(cfsr_new.lon[np.array([3, 4, 8])])
lat_sel = np.array(cfsr_new.lat[np.array([2, 3, 4])])
time_sel = cfsr_new.time[100:200]

selection = cfsr_new.sel(lon=lon_sel, lat=lat_sel, time=time_sel)
selection.to_array()

I get:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-38-3f04c6458da2> in <module>()
----> 1 selection.to_array()

/Users/<user>/anaconda/lib/python3.5/site-packages/xarray/core/dataset.py in to_array(self, dim, name)
   1847         data_vars = [self.variables[k] for k in self.data_vars]
   1848         broadcast_vars = broadcast_variables(*data_vars)
-> 1849         data = ops.stack([b.data for b in broadcast_vars], axis=0)
   1850
   1851         coords = dict(self.coords)

/Users/<user>//anaconda/lib/python3.5/site-packages/xarray/core/ops.py in f(*args, **kwargs)
     65             else:
     66                 module = eager_module
---> 67             return getattr(module, name)(*args, **kwargs)
     68     else:
     69         def f(data, *args, **kwargs):

/Users/<user>//anaconda/lib/python3.5/site-packages/dask/array/core.py in stack(seq, axis)
   1754
   1755     if all(a._dtype is not None for a in seq):
-> 1756         dt = reduce(np.promote_types, [a._dtype for a in seq])
   1757     else:
   1758         dt = None

/Users/<user>//anaconda/lib/python3.5/site-packages/toolz/functoolz.py in __call__(self, *args, **kwargs)
    217     def __call__(self, *args, **kwargs):
    218         try:
--> 219             return self._partial(*args, **kwargs)
    220         except TypeError:
    221             # If there was a genuine TypeError

TypeError: invalid type promotion

On further investigation, it appears the problem is the dataset contains a mix of string and float data - the strings are redundant representations of the time stamp, therefore they don't appear in the index query. Explicitly selecting on the desired data variable solves this:
selection = cfsr_new.TMP_L103.sel(lon=lon_sel, lat=lat_sel, time=time_sel)
I think a clearer error message may be needed: when you do sel without indexing on certain dimensions, those are included in the resulting selection. It's possible for those to be of mixed incompatible types. Clearly  to do to_array you need a numpy-friendly uniform type. The error should make this clearer.

What are the types of the incompatible arrays? This certainly is not desirable for xarray -- we'd like to be able to stack these arrays together, into a lowest compatible dtype (even if that's only object). I think the main issue here is actually in dask.array, but it would be nice to be able to provide them with a minimal example.


Add two more items to the substitution map

pythonExecutable names the full path to the Python executable that the pex
will be shebanged with.
toolName is the project name, which can form the basis of the pex file name

Closes #207

Tested locally; I'm not sure there's an existing test for the original placeholders.

Hmm, not sure how my changes could have broken that test.  Is it a CircleCI problem perhaps?  Trying a clean local build to see if that reproduces the failure.

Thanks @ethankhall - it was just a transient connectivity problem.  Build kicked and it passed.


Fix terminal stdin

closes #160

Oh thank you for fixing the terminal stdin. I kept getting a StdinException when using fvm together with Fastlane and could not figure out at all what was going wrong.

Still getting it with 1.3.3 :(
This is inside an SSH session, not sure it has something to do with it.
[2020-10-14T23:55:20.745Z] + fvm --verbose install
[2020-10-14T23:55:21.686Z] Version: 1.22.1 - already installed.
[2020-10-14T23:55:21.686Z] [     0.513s] StdinException: Error setting terminal echo mode, OS Error: Operation not supported by device, errno = 19
[2020-10-14T23:55:21.686Z] Internal Error: Could not finish setting up Flutter sdk
[2020-10-14T23:55:21.686Z] #0      flutterSetupWorkflow (package:fvm/src/workflows/flutter_setup.workflow.dart:11:5)
[2020-10-14T23:55:21.686Z] <asynchronous suspension>
[2020-10-14T23:55:21.686Z] #1      InstallCommand.run (package:fvm/src/commands/install_command.dart:51:13)
[2020-10-14T23:55:21.686Z] <asynchronous suspension>
[2020-10-14T23:55:21.686Z] #2      CommandRunner.runCommand (package:args/command_runner.dart:197:27)

I just think this is a bug in dart... might have to remove the echoMode.. as the api is very inconsistent.

I have pinned fvm to 1.2.3 for now in CI, didn't get it to work with any 1.3.x

Might be related: https://github.com/dart-lang/sdk/issues/34213
Or maybe this can help from the APK utils in Flutter: https://github.com/flutter/flutter/pull/42892/files

Also having a problem on my local machine. I am using fastlane and call fvm from there, now with 1.3.3 the fastlane commands don't terminated after the fvm commands finish.

@kuhnroyal could you provide me the snippet on fastlane so I could try to replicate?

Add this to a project in $PROJECT/fastlane/Fastfile
lane :fvmtest do
  Dir.chdir "#{ENV["project_root"]}" do
    sh("fvm flutter doctor")
  end
end

Run with fastlane fvmtest or  bundle exec fastlane fvmtest depending on how you installed fastlane.
fvm flutter doctor succeeds but the process doesn't terminate.


fix: use proper kubeconfig path in installHac.sh

/test appstudio-e2e-tests

@rhopp still valid?

I completely forgot on this PR and I delivered this fix as part of different PR.


pkg/core/table/cpin.go: expose CPIN table information

This expose valuable information about the number of retries we
can apply before device is locked, and if it is persistent or not.
This information is taken into account by calling code when getting
ErrAuth rather we want to proceed or not.

@ChriMarMe please review


colordiff: support Darwin as a platform

This change just adds darwin to the supported platforms attribute of
the package.
Tested on OS X 10.10.3
@nckx for review.

Thanks for testing! Merged.


UploadOptions mutates provided object

Is this a client library issue or a product issue?
This is a client-library issue.

Did someone already solve this?
I could not find anything.

Do you have a support contract?
I work for Google 😄 .

Environment details

OS: Mac 12.3.1 (21E258)
Node.js version: 16.14.0
npm version: 8.3.1
@google-cloud/storage version: 5.19.3

Steps to reproduce
import { Storage } from '@google-cloud/storage';

async function main() {
  const opts = {
    metadata: {},
  };

  console.log('before: ', { opts });

  const storage = new Storage({
    projectId: 'sv-actions-test',
  });
  await storage.bucket('sv-actions-test').upload('package.json', opts);

  console.log('after: ', { opts });
}

main();

The opts passed to upload are modified:
before: { opts: { metadata: {} } }
after: { opts: { metadata: { contentType: 'application/json' } } }

It's very unexpected and undocumented that the object passed to upload would mutate the properties of that object. This was the root cause of an extremely difficult to debug bug in the upload-cloud-storage GitHub Action, causing the wrong Content-Type to be applied to object uploads.
The workaround is to deep copy the entire object before passing it to upload. I would expect the SDK to handle this and not mutate objects it is given. Other functions in the SDK may have this same problem.
I believe the issue is here.

Hi @sethvargo ,
Uploading an object to cloud storage requires a content type (https://cloud.google.com/storage/docs/json_api/v1/objects/insert). This is happening here: https://github.com/googleapis/nodejs-storage/blob/aab390cb3024b562f05c44ade51e71c484341feb/src/file.ts#L1844-L1852 Since no content type is being passed into the function, the library is trying to auto-detect a content type. What would be the expected behavior for you in this case? Would you have preferred that the function error and force you to pass a content type? Something else?

The MDN article might do a better job of explaining the issue than me: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/assign#warning_for_deep_clone


implement text based entity card/content filters

Overview
This PR introduces the ability for card/content extensions to the catalog frontend plugin, to receive a filter argument that's text based, in addition to the previous callback based system. The filter decides whether the extension should be rendered or not. This lets you for example only show the CI/CD tab for a select set of kinds - even if you are using custom kinds. All from the convenience of your app-config file.
Example in the configuration file for declarative integration:
app:
  extensions:
    - entity.cards.about
    - entity.cards.links:
        config:
          filter: 'kind:component has:links'

The suggested format in this PR is a space separated list of key:parameters pairs, where all such pairs need to match an entity for it to be rendered. Additionally, the parameters list is comma separated, letting you for example target multiple kinds with kind:user,group. This is heavily inspired by the github filter syntax for issues and pull requests.
Alternatives
This is, of course, a bespoke format. We went back and forth a bit on how it should look. It needs to be convenient to type for humans, and still be easy enough for e.g. a management console to have a UI for and generate the string from.
One contrast that comes to mind, is the catalog backend API. It doesn't have a query syntax like this yet, and its current filtering capabilities do leave some room for improvement. If we were to introduce a query format for the backend, it would be good if it could tap into the same syntax as we choose here. Or put differently, the syntax chosen here is knowingly different from the catalog backend filters; is that a bad thing or does this actually make some movement toward a better way of expressing filters there too in the future?
Open to suggestions and ideas.

One thing of note here is that the filter builder throws errors. This does probably fail "too hard", leading to error overlays if you have bad syntax problems. We may want to compile forgivingly (making filters more permissive in the face of failures, ie ignoring restriction clauses) and emitting warnings instead.


subclasses of declared exception should be thrown

if a service throws "ServerExecption" but ends up throwing a sub-class
of ServerException e.g. ValidationException, the ResponseExceptionMapper
resulting Exception is lost.
Additional information, Resteasy also does it this way:
https://github.com/resteasy/Resteasy/blob/cc424c27f0e9b5ccbc712fd114b7c9abb43e6ba5/resteasy-client-microprofile/src/main/java/org/jboss/resteasy/microprofile/client/ExceptionMapping.java

@andymc12 Should this be merged to 3.3.x-fixes as well?

@coheigea yes, I'll back port that now.  Thanks!


Text shrinks when moving Alacritty between 4k monitor and retina display

Which operating system does the issue occur on? OSX Sierra
If I start alacritty on my 4k monitor then drag it to my laptop the text shrinks by 4x. If I start it on my laptop then drag it to my monitor the text grows by 4x.

This is a duplicate of #71.


Hide "Compare and Pull Request" popup

Description
I'd like to have 2 unrelated branches in the same repo that share no history.
Git itself supports this well through orphan branches, but github get's confused and wants me to PR isntead.
Also see here: https://github.com/orgs/community/discussions/22526
Example URLs
https://github.com/port19x/dotfiles

We can’t just hide the popup, but there’s a plan to make it less invasive.

https://github.com/refined-github/refined-github/issues/6295


[zh] Sync access-application-cluster/*.md and relative linked files.

Sync access-application-cluster/*.md
Rename and sync cheatsheet.md to quick-reference.md

Depends on PR #44669 link anchor fixes of file:
content/zh-cn/docs/tasks/administer-cluster/access-cluster-api.md

See preview.

/lgtm
/approve


goog.color.blend appears to perform Simple Alpha Compositing than actual Blending per W3C spec

Source code:
https://github.com/google/closure-library/blob/master/closure/goog/color/color.js#L674
References:

https://www.w3.org/TR/compositing-1/#simplealphacompositing
https://www.w3.org/TR/compositing-1/#blending

The Closure formula is result = rgb2 + factor * (rgb1 - rgb2). To figure out whether the existing implementation is doing Simle Alpha Composition or Blending, we can try to express it in terms of the formulas defined in the spec.
The spec defines Blending as Cr = (1 - αb) x Cs + αb x B(Cb, Cs) where B(Cb, Cs) is defined by blending mode. Each mode has its own formula for B. We can express Closure's implementation in W3C Blending terms Cr = (1 - αb) x Cs + αb x B(Cb, Cs) and figure out which blending mode it is:
result = rgb2 + factor * (rgb1 - rgb2)
       = rgb2 - factor * rgb2 + factor * rgb1
       = (1 - factor) * rgb2 + factor * rgb1

// equivalent
Cr = result
αb = factor
Cs = rgb2
B(Cb, Cs) = rgb1

// figure out blending mode?
B(rgb1, rgb2) = rgb1 // since Cs is already derive above, Cb has to be rgb1
B(Cb, Cs) = Cb // back in W3C spec terms

B(Cb, Cs) = Cb does not match any defined blending modes. However, since user can provide result of B(Cb, Cs) as input, that is an actual use case. It does require knowledge and proper usage.

The spec also defines "simple alpha compositing" as co = Cs x αs + Cb x αb x (1 - αs). If we were to express Closure's formula in that term:
result = rgb2 + factor * (rgb1 - rgb2)
       = factor * rgb1 + rgb2 - factor * rgb2
       = rgb1 * factor + rgb2 * (1 - factor)

// equivalent
co = result
Cs = rgb1
αs = factor
Cb x αb = rgb2

This makes more sense as Closure's rgb2 is simply taken as pre-multiplied value.

Action item: I don't think we need to update the implementation. However, I think it is worthwhile to update the Doc to mention the technicality and provide proper usage of each case.

I will submit CL


[FIX ISSUE#2] [GSSOC 2023] Adding pre-loader

The pull request makes the following changes:

Fixes issue #2

[x] The pre-loader screen shows a spinning logo while the main content is loading.
[x] This improves the user experience and reduces bounce rate.
[x] I have tested the code on different browsers and devices and it works as expected.

You should be assigned to the issue before making pr

Pr is not merged if you are not assigned to the issue and
Comment
assign it to me on the issue first


Superscript exponent not documented as operator on doc/Language/operators.pod6

At some point (hopefully soon), the Unicode superscript exponent operator should be documented together with the '**' operator on the "operators" page (source: doc/Language/operators.pod6) under "Exponentiation Precedence".  The two operators are fairly identical in theory, but there is an open RT #130414 on differences in associativity.  As noted on the ticket, roast tests have been added and so identical behavior is part of the current spec.  User facing documentation is intended to reflect working features and it may be appropriate to hold off on documentation until the ticket is resolved (but not sure).

Not clear what is the problem here. The tests have been merged, although the ticket is not resolved. Anyone can clarify?

@JJ The superscript form still isn't documented.


Repositories for paper Automatic Assessment of Oral Reading Accuracy for Reading Diagnostics

Hi, could you please add teh following repositories to the paper: "Automatic Assessment of Oral Reading Accuracy for Reading Diagnostics"?
https://github.com/bomolenaar/jasmin_data_prep
https://github.com/cristiantg/kaldi_egs_CGN/tree/onPonyLand
Thank you,
Cristian.

Hi! Done ✅ Thanks for repositories!


Add JetBrains project files to gitignore

merged, thanks!

Thank you too, this makes committing a lot easier!


schedule slang flow fails on inputs passed as unmodifiable collection

also the run time exception is fired from Slang language and not from score as ScoreEvent.Error

using CLI or API???

API

API
From: Meir Wahnon<EMAIL_ADDRESS>Sent: Thursday, March 12, 2015 2:46 PM
To: openscore/score-language
Cc: Hajyhia, Shehab
Subject: Re: [score-language] schedule slang flow fails on inputs passed as unmodifiable collection (#160)
using CLI or API???
—
Reply to this email directly or view it on GitHubhttps://github.com/openscore/score-language/issues/160#issuecomment-78472727.

@meshipeer please re-open


Harbor API "automatically_scan_images_on_push" not work

Harbor create project API:
POST /project
{
"project_name": "string",
"public": 0,
"enable_content_trust": true,
"prevent_vulnerable_images_from_running": true,
"prevent_vulnerable_images_from_running_severity": "High",
"automatically_scan_images_on_push": true
}
Response 201 Created but the following parameter in API body did not take affect (In project/Configuration, the corresponding settings are not checked or value changed)
"automatically_scan_images_on_push":true not work
"prevent_vulnerable_images_from_running_severity":"High" not work
"prevent_vulnerable_images_from_running":true not work
We really need "automatically_scan_images_on_push" from Harbor project creation API because we are creating lots of projects day by day and leverage Clair for vulnerability scan.

docker 17.03.2-ce, docker-compose 1.16.1
HTTPS enabled
Log I found related to create project from API is proxy.log:
Apr 24 10:27:38 <IP_ADDRESS> proxy[17712]: <IP_ADDRESS> - "POST /api/projects HTTP/1.1" 201 0 "-" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36" 0.008 0.008 .

Post the data as the following:
POST /project
{
  "project_name": "string",
  "metadata": {
    "public": 0,
    "enable_content_trust": true,
    "prevent_vulnerable_images_from_running": true,
    "prevent_vulnerable_images_from_running_severity": "string",
    "automatically_scan_images_on_push": true
  }
}

There are some changes in API and the doc isn't updated properly. We'll update it later.

Hi @ywk253100, does Harbor 1.4.0 release support the POST data format as you mentioned above?  I tried but got 400 bad request: invalid json request ...

I found the following format works on Harbor v.1.4.0
POST api/projects
{
"project_name": "string",
"metadata": {
"public": "1",
"enable_content_trust": "true",
"prevent_vul":"true",
"severity": "high",
"auto_scan":"true"
}
}

No " needed for the boolean values.


This is a query, and not an issue....

Do you know, offhand, what the barriers are to porting this work to apply against standard MRI Ruby instead of mruby?
I have done some experimentation with manual bindings between Crystal and Ruby (embedding Ruby into a Crystal program), and for some trivial things, it worked better than I expected.
i.e. Bind Ruby 3 into Crystal, load code from an external file into the Ruby VM, call Crystal code with rb_protect to, in turn, invoke Ruby methods, capturing the return VALUE and transforming that to equivalent Crystal data structures (Strings).
An awful lot of what I see in anyolite looks like things that I would want to implement to enable less trivial, and less manual binding between Crystal and Ruby, so I am wondering if you are aware of any major gotchas to doing so?

As far as I'm aware the API functions of mruby and MRI are very similar to each other, so this should not be a big problem (though I haven't yet tried it).
What exactly did you have in mind for the last paragraph? Is there anything you're missing in Anyolite what could be improved using MRI (except for obvious things like speed and ecosystem)?

Mostly speed and ecosystem. honestly. Interoperability that manages to avoid tripping over garbage collection provides some interesting opportunities, and while I was already hatching some ideas in my head for how to achieve this, it looks like you've already done a fair amount of the hard thinking and typing work.
I might take what you have done, fork it, and marry it with a few things that I have been hacking on to see if I can get a proof of concept to link with MRI Ruby.

It would definitely be cool to see how switching to MRI improves certain aspects!
Garbage collecting was a problem I fixed by implementing a reference table in Crystal, which keeps track of all shared objects, and by giving a customized destructor method to all shared mruby objects. It is not the most sophisticated approach, but it should prevent any internal dangling pointers and segfaults. If MRI provides a method to give custom destructor methods to data objects, the concept can easily be ported.

I just thumb up as I wish to see this coming.
I'm currently working on an actor framework inspired by Akka and want to create ruby actors, allowing the use of ruby ecosystem, zero compilation time and still being able to run some performance-needed portion in crystal.
I'm not sure it's so easy to port MRI however.

Support for MRI is on the roadmap for future versions and I already built some of the infrastructure to support different Ruby implementations.
Most of the work will be mapping all implementation-dependent functions to the respective MRI functions instead of the mruby functions, probably some changes in the installation process and lots of testing.
There are also some implementation details I haven't figured out completely, like gem support or dealing with the differences in argument passing, so don't expect it too soon.

Aaaand it's done!
MRI 3.0.2 can be selected as an alternative implementation to Anyolite now (mruby is still recommended, though)! Instructions are in the README file.
There might be some weird bugs or inconveniencies (like the broken documentation - I'll fix it in the next days), but the test scenario runs completely fine.
Gem installation is also only possible manually, but it should work fine.
That also means that this issue can (finally) be closed.
If you have any other questions or comments, feel free to join the discussion thread under the 0.13.0 release.

Sweet!!!!!
I am going to be giving this a workout soon.


Input focus event

Hi there, thanks for great lib.
I wonder if there is any way to handle focus event when entering text field? For example, after "clicking" mouse check whether active window waiting for input...
I'm not familiar with this all things, sorry if question is weird.

Thank you for your suggestion,I will think about it.


Locale could not be found warning

I was testing the i18n on this lib, and noticed the fr locale could not be found:

It's mentioned in the docs though, and it's available in the source at: src/i18n/locales/fr.ts.
Checking the source led me to this import, which I'm suspecting to be a typo:
https://github.com/bradymholt/cRonstrue/blob/75084b54fd5b62fa53016c1fe217e1e042c404a6/src/i18n/localeLoader.ts#L1
So I suspect it should be importing from ./locales, not ./locale, which would explain the missing locale warning I encountered above? Not sure though, as there are unit tests, so just bringing this up to see if my assumption is correct.

Hmm, I might be wrong in my assumption as my local version (1.91.0) does seem to ship with translations. So in that case, the bug still remains (locale that should be present can't be found) but I'm not sure of the cause.


When to use sdfstudio vs nerfstudio ?

Sorry if this question looks dump but i was wandering when should i use nerfstudio and when to use sdfstudio ?
I can't wrap my head on the difference between the two projects and when to use (and not use) each one of them.

Nerfstudio models do not implicitly represent the surfaces/geometry while SDFStudio models do implicitly represent the surfaces/geometry. Nerfstudio models generally do a better job of reconstructing fine-grained details, but have noisier surfaces/geometry. SDFStudio models generally are smoother and provide better exports to e.g., meshes.
See e.g., the paper of NeuS for more details https://lingjie0206.github.io/papers/NeuS/

Thanks @MvWouden.
@MohamedAliRashad If you want a good surface reconstruction/mesh then you could use sdfstudio.


🐛 [Bug] login button not fixed size

🐛 Bugreport
The login button has gotten away at certain display sizes. please set it back to a clean width.

fixed here https://github.com/gradido/gradido/pull/2732


test overzooming with large zoom_factor

Reviewing Joto's code review #59 highlighted that we are not handling underzooming - right now, in that use case it returns a blank tile.
I added a check at L126 so the composite function errors when we handle an underzooming scenario.
    if (tile_obj->z > target_z)
    {
        std::ostringstream os;
        os << "Underzooming not supported. TILE Zoom("
           << tile_obj->z << ") greather than TARGET Zoom (" << target_z << ")";
        throw std::invalid_argument(os.str());
    }

Oddly, the underzooming scenario does not make it past the vtile::within_target check on L110. It also doesn’t raise the expected out-of-target error if vtile::within_target is false. It still returns a blank tile. It's unclear to me what's happening.
@ericfischer @artemp @springmeyer

@millzpaugh - within_target already checks for "under-zooming" cases and returns false ^.
/cc @springmeyer

@artemp This is odd - you're right that it has the appropriate error message, but it doesn't throw the error, it still returns a blank tile.
Also - I wrote an additional test in this branch that has a huge zoom factor (z0 --> z18). The original tile has 4 points - when it's passed in for overzooming, it returns a blank of tile and doesn't error, even if zxy is out of range. Do you mind looking into this?

#overzooming fails if there's a large zoom factor
@artemp I'm noticing that a blank tile is returned if we have an instance where we're overzooming by a large zoom factor. The zoom factor threshold doesn't seem to be consistent - one test case fails if the zoom factor is greater than 4, another test case fails if the zoom factor is greater than 7.
I've written two tests:
**overzooming 1 tile with 4 points **
success overzooming: z0 --> z4
failure overzooming: z0 --> z5+
overzooming 1 tile with 14 points, poi label from mapbox streets, starting at z15
success overzooming: z15 --> z22
failure overzooming: z15 --> z23+
will continue looking into this tomorrow!

@millzpaugh - just wondering if empty tile returned because there are no point in resulting tile after over-zooming ?

@artemp I'm using tilebelt to calculate the tile where the point should be at each zoom level, so unless there's a bug in that library, the zxy should be correct and contain the point.

@artemp It turns out boost's boost::geometry::within function is exclusive of coordinate bounds, so any points at 0 or 4096 were getting dropped if buffer_size=0. boost::geometry::covered_by is inclusive of bounds so using that incorporates border points. Now tests are passing! 🎉
cc @springmeyer

@millzpaugh - great find! Using covered_by when buffer_size  is 0 will result in duplicate points if there are on the boundary, I guess this is OK as we're already dealing duplicates when buffer_size>0

@millzpaugh - I think this is ready to be merged, right ?

@artemp yes! ready to be merged.
and I can't take full credit for that find - it was the result of a great pairing session with @flippmoke. :)

team effort :+1:


Cover Google Cloud Storage with tests

This resolves #20
Also, bump the version from 0.0.6 to 0.1.0, as we have introduced some BC breakage around configuration and can now consider GCS "officially supported"

@shevron That's great! Thanks!!!


[8.0.0] Nasty npm install bugs, unable to run gulp

All of the sudden I seem to be having issues with getting 8.0.0 up and running. I don't know if this is an isolated incident on my part or if things are still in flux.
Pulling down 8.0.0 I run nom install and get the following errors:
><EMAIL_ADDRESS>install /Users/eric/Development/wp-dev/www/b2b/htdocs/wp-content/themes/banjos/node_modules/gulp/node_modules/v8flags
> node fetch.js

npm ERR! unpack Could not read data for<EMAIL_ADDRESS>npm ERR! unpack Could not read data for<EMAIL_ADDRESS> [[B-
><EMAIL_ADDRESS>install /Users/eric/Development/wp-dev/www/b2b/htdocs/wp-content/themes/banjos/node_modules/browser-sync/node_modules/socket.io/node_modules/engine.io/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/bufferutil.node
  SOLINK_MODULE(target) Release/bufferutil.node: Finished
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/validation.node
  SOLINK_MODULE(target) Release/validation.node: Finished
npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN optional dep failed, continuing<EMAIL_ADDRESS>
><EMAIL_ADDRESS>install /Users/eric/Development/wp-dev/www/b2b/htdocs/wp-content/themes/banjos/node_modules/gulp-pleeease/node_modules/pleeease/node_modules/chokidar/node_modules/fsevents
> node-gyp rebuild

  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  SOLINK_MODULE(target) Release/fse.node: Finished

><EMAIL_ADDRESS>install /Users/eric/Development/wp-dev/www/b2b/htdocs/wp-content/themes/banjos/node_modules/browser-sync/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/bufferutil.node
  SOLINK_MODULE(target) Release/bufferutil.node: Finished
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/validation.node
  SOLINK_MODULE(target) Release/validation.node: Finished
npm ERR! cb() never called!

But it does seem to "finish" though. I use that term loosely because it doesn't straight barf at me and roll back, which I've seen before when I screw something up.
Once I try to run any gulp commands I get this:
Error: Cannot find module 'glob'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/Users/eric/Development/wp-dev/www/b2b/htdocs/wp-content/themes/banjos/node_modules/browser-sync/node_modules/glob-watcher/node_modules/gaze/node_modules/globule/lib/globule.js:15:12)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

Any thoughts?

Ok, Im going to close this because it seems to be machine specific. I was able to get everything going on a second machine, therefore it's not Sage specific. I am however open to suggestion as to what I have borked on this machine tho. @austinpray?

Hey there bud,
So I just tried this on:

fresh osx yosemite install: node v0.10.35 npm 1.4.28
fresh debian wheezy node v0.10.36 npm 1.4.28

Both installed great. Plus travis has been building this stuff all the live-long day
First thing I would try is:
npm cache clean
rm -r node_modules
npm install

Lemme know if that fixes it. Definitely start up a discourse thread if it doesn't.
I recommend installing node with nvm and avoid using sudo with npm.

yea npm cache clean was the first thing I tried, then I got similar but different errors. Im gonna nuke npm and node on that machine (OS X ML) and try reinstalling with nvm and see if that does anything.
Something happened and I don't know what, last week I was fine on that machine, today, completely borked.
If I have anymore issues I will hit you up on discourse.
Thanks.

You can avoid using nvm, and the sudo npm <whatever> approach by simple supplying a path, as the default is usually / on OSX.
So, for example, npm cache clean ~/  will target your user directory, and avoid the need to sudo in this case (and others like this).


Revert patch that caused failing test on databricks 321 [databricks]

This reverts https://github.com/NVIDIA/spark-rapids/pull/6273 because of https://github.com/NVIDIA/spark-rapids/issues/6446

build


public static final String CONTAINER_WIDGET_BASE = SCHEMA + "://rexxar-container/widget";

Final CONTAINER_WIDGET_BASE cannot be changed by setting SCHEMA.

@ChasonChen fixed  https://github.com/douban/rexxar-android/pull/24


Allow mash error silencing

re: #485  and #487
@dblock @michaelherold thoughts?

I like that this gives more flexibility around disabling warnings over #487. However, in #485, @nonnenmacher specificly calls out Mash.load as a culprit for annoyance with the warnings. Personally, I would rather extract Mash.load into a companion gem and get rid of it, but since it's here we should think about addressing that case.

@michaelherold this works with load as well Hashie::Mash.quiet.load(path, parser: parser)

🤦♂ Of course it does ... 🤦♂

I'm wondering if we should do some sort of caching so we don't generate a new class every time we call .quiet. Maybe a lookup table with keys based on the method keys you send to the method?
Otherwise, I really like this approach! 👍

Interesting thought, I may have some time later to look into that

I'm wondering if we should do some sort of caching so we don't generate a new class every time we call .quiet. Maybe a lookup table with keys based on the method keys you send to the method?

One argument against is that quiet would work like merge, always generating a new thing. Maybe we can also have quiet! that mutates the existing class?

One argument against is that quiet would work like merge, always generating a new thing. Maybe we can also have quiet! that mutates the existing class?

Since we're only memoizing the classes and not the objects instantiated from them, I don't think we need to worry about a non-mutating and mutating method, I'd be open to hearing opposition if I'm not thinking this through all the way 😅

I think this is pretty much there AFAIK. A bit of cleanup and we're good to go?

I think this handles most use cases, faraday_middleware supports passing a custom mash class in which was one of the other concerns.

Seems like my autoload isn't working in some of the integration tests... do either of you see anything wrong with how I'm autoloading the new extension?

I like that this gives more flexibility around disabling warnings over #487. However, in #485, @nonnenmacher specificly calls out Mash.load as a culprit for annoyance with the warnings. Personally, I would rather extract Mash.load into a companion gem and get rid of it, but since it's here we should think about addressing that case.

@michaelherold this works with load as well Hashie::Mash.quiet.load(path, parser: parser)

Sound nice !
and would do perfectly I guess
especially if the parser is an argument, as one of the problem of Safe_yaml and underlying implementation (e.g psych versus sick) don't allow passing options from the parse call).

I think this handles most use cases, faraday_middleware supports passing a custom mash class in which was one of the other concerns.

yep it does, especially as the two mains cases where we have the problems and often are out of reach for code modification (i.e because we can't modify the data) are
-- loading configurations that have defined/not changeable names
-- REST responses that contains attributes out of reach (e.g this zip thing)

I'm good with this, @michaelherold?

Go for it!

Merged.


Setup Django project and configure settings for development and production environments.

I've added the basic setups


Drop 'generic' in InferenceAPI framework list

cc @Narsil @osanseviero (see internal slack)
Related to https://github.com/huggingface/api-inference/pull/1737 (private repo)

Thanks @MoritzLaurer for reporting and @Narsil for the review. CI failures are unrelated.


Spa , Ara cube data is not working. Throws Accessviolation error

Hi,
I am using Spanish, arabic trained data in tesseract, but in the statement TesseractEngine it is throwing AccessViolation Error.

One more need, I have an urgent requirement for having Accurate text extraction, So we are going to use TesseractAndCube Engine mode. For this Engine mode we need Cube.* trained data. Please provide the Cube trained data for other languages like portuguese etc., Or kindly give me the steps to train the Cube data file for other languages.
Thanks and Regards,
Merlin

See Tesseract issue 946.


The procedure parameters created with "Type Of Column TABLE_NAME.COLUMN_NAME" appear as normal data type in the source code.

Description
The procedure parameters created with Type Of Column TABLE_NAME.COLUMN_NAME , appear as normal data type in the source code.

DBeaver Version
Community Edition 23.3.0
Operating System
Windows Server 2019
Database and driver
DB : Firebird 4.0
Driver : Firebird Jaybird driver 5.0.2
Steps to reproduce
After creating the table and the procedure, please look at the code of the procedure.
Instead of "TYPE OF COLUMN TBL_TEST.COL1" you will see varchar(10) in both input and return parameters.
CREATE TABLE TBL_TEST(COL1 VARCHAR(10), COL2 VARCHAR(10));
SET TERM # ;
CREATE OR ALTER PROCEDURE SP_TEST_PARAM_TYPES(
    P_1 TYPE OF COLUMN TBL_TEST.COL1,
    P_2 TYPE OF COLUMN TBL_TEST.COL2)
RETURNS (
    R_1 TYPE OF COLUMN TBL_TEST.COL1,
    R_2 TYPE OF COLUMN TBL_TEST.COL2)
AS
BEGIN
  R_1 = :P_1;
  R_2 = :P_2;
  SUSPEND;
END#
Additional context
No response

Thanks for the report @ugrsyn
And how about functions? Can functions have such kind of syntax in the definition?

Could you please provide a function definition also?

Sure.
SET TERM # ;
CREATE OR ALTER FUNCTION FNC_TEST(P_1 TYPE OF COLUMN TBL_TEST.COL1)
RETURNS TYPE OF COLUMN TBL_TEST.COL1
AS
DECLARE VARIABLE V_TEST TYPE OF COLUMN TBL_TEST.COL1;
BEGIN
  V_TEST = :P_1;
  RETURN V_TEST;
END#


Paste image

Would be useful to be able to paste image by using cmd+V. This can be achieved in webkit relatively easily, and would be great for sharing screenshots!
http://jsfiddle.net/KJW4E/519/

This has already been implemented in #55, just waiting for the code to be cleaned up and merged in.
Safari doesn't actually support e.clipboardData.items (ugh), so the code you posted isn't enough. The implementation I came up with catches the paste event in Swift and sends the image data directly to a Javascript function.


Do not allow files from zip folder that have not been extracted

When adding a file from inside a zip folder it comes with 0 bytes in size, so there is really no file and it can't be used.

@KarimMokhtar In windows just double click the zip to open it, then drag and drop the file from within the zip into the <FileUploader />

@KarimMokhtar any updates on this?

Looks like this project won't be maintained any time soon.
Its a good library tho, this was the only issue I ever had with it.


WHERE IS THE NEW VERSION?

Where is the update on stellar ? There are several Bugfixes which need to be applied.

Please don't yell :-1:


Update VTK 9 version to 9.2.6.

Description
Updating to latest VTK 9 release.
Type of change

* [ ] Bug fix
* [ ] New feature
* [ ] Documentation update

[X] Other~~
TP library update

How Has This Been Tested?
Successful compile on pascal
Reminders:

Please follow the style guidelines of this project.
Please perform a self-review of your code before submitting a PR and asking others to review it.
Please assign reviewers (see VisIt's PR procedures for more information).

Checklist:

- [ ] I have commented my code where applicable.
- [ ] I have updated the release notes.
- [ ] I have made corresponding changes to the documentation.
- [ ] I have added debugging support to my changes.
- [ ] I have added tests that prove my fix is effective or that my feature works.
- [ ] I have confirmed new and existing unit tests pass locally with my changes.
- [ ] I have added new baselines for any new tests to the repo.
- [ ] I have NOT made any changes to protocol or public interfaces in an RC branch.

Sorry about the early review request. Decided I should keep put it in draft until I build and test on Windows.


Process condition in protocol version less than 5

Here we found two issues in develop branch:

startVideoStream will execute on NACK
createOpenGLInputSurface never executed if protocol version < 5, this issue seems fixed in #638

StartVideoStream() method in SdlProxyBase currently return sdlSession.startVideoStream() if protocol version is less than 5, but acceptedParams has already returned null, this not make sense.
Below is the code snippet:
https://github.com/smartdevicelink/sdl_android/blob/develop/sdl_android/src/main/java/com/smartdevicelink/proxy/SdlProxyBase.java#L3956-L3958
tryStartVideoStream method in SdlProxyBase, in if(navServiceStartResponse) condition, if protocol version is less than 5, getAcceptedVideoParams will return null,  VideoParams will not send to proxy, leads the VideoStream never start.
Below is the code snippet:
https://github.com/smartdevicelink/sdl_android/blob/develop/sdl_android/src/main/java/com/smartdevicelink/proxy/SdlProxyBase.java#L4148-L4150

Fixed with #646


glassbox domains

Hey,
I just stumbled upon this article from The Verge.
This one (glassbox.aircanada.ca) hits the list as written from The App Analyst.
Anyone have more domains to block for Glassbox data collection and etc?

report.usaa.glassboxdigital.io

Related, posted just a few hours ago:
Apple tells app developers to disclose or remove screen recording code

think anyone can absorb the domains in their list? hehe
so we can close this one ;)

We presently carry the following three domains, which come to us via AdAway.  Which may or may not be related.
glassbox.aircanada.ca
glassboxdigital.com
theglassbox.com

Closing this since it's just old.


Impala connector

A connector for Apache Impala. Related to #247 .

Hi @igrangel @IshanDindorkar,
I do not have access to an Impala instance, could you guys check with the following configuration?:
[Impala]
db_url=impala://host:port/database
mappings=path_to_mappings

You probably have to first install Impyla:
pip install impyla


Update automation-properties.md

Fixed minor typo in intricacies section. OS -> iOS.

@dg2445 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @dg2445
I'll have to close this PR, as the original text is correct.


Feature Request: Space key to select suggestion

I love this plugin! Thanks for making it. What do you think about adding the option to use space key for selecting a suggestion. This would mirror the behaviour of macOS on a system level. What do you think?

Hi, @dolphinpoint. Thank you for your PR :)
Do you mean adding a Space option to Select a suggestion key?

Yep! That's exactly what I mean.

Thanks! I'll implement it 👍
By the way, if you use a space key as selecting suggestion, how will you insert space instead?

Thanks! I'll implement it 👍

+1 for this feature :) Thanks for bring this feature for us 🎉

By the way, if you use a space key as selecting suggestion, how will you insert space instead?

I'm gonna try to give feedback based on my workflow :)
I only use Custom Dictionaries + alias -> that opens the suggester menu with 3 to 8 suggestions.

TAB with the Left Hand to select the suggestion;
ARROWS to navigate with the Right Hand;

This way, using SPACE instead of TAB would be 1000 times better than TAB because my left hand thumb is almost touching the SPACE BAR :)
Have a great day 🌞

@dolphinpoint @FelipeRearden
I have released v6.0.0-beta1 and v6.0.0-beta2 🚀
The main target of these releases is not this feature. However, it includes this feature.
If you use BRAT and you want to use it as soon as possible, I hope you can use them until the official release of v6.0.0 🙏

Thank you very much @tadashi-aikawa  !!!!!!!

If you use BRAT and you want to use it as soon as possible, I hope you can use them until the official release of v6.0.0 🙏

Working perfect on version 6.0.0-beta2 on Obsidian 0.14.5
Thanks again for making one of my favorite plugins 💙
Have a great day 🌞

Amazing! thanks!!!

I have released v6.0.0 🚀

I have released v6.0.0 🚀

Working perfect on version 6.0.0 Obsidian 0.14.6
Thank you very much @tadashi-aikawa !!!!!!!!!!!!!!!!!!! 💙