[BUG] Use of Py_LIMITED_API sometimes results in references to nonexistent PyTuple_SET_ITEM function

Describe the bug
Use of Py_LIMITED_API sometimes results in implicit declaration of PyTuple_SET_ITEM function, and consequent ImportError when importing.
When the code below is built with  python3 setup.py build_ext --inplace, the following warning is emitted:
my_module.c: In function ‘__pyx_pf_9my_module_my_function’:
my_module.c:2246:3: warning: implicit declaration of function ‘PyTuple_SET_ITEM’; did you mean ‘PyTuple_SetItem’? [-Wimplicit-function-declaration]
 2246 |   PyTuple_SET_ITEM(__pyx_t_1, 0, __pyx_v_firstword);
      |   ^~~~~~~~~~~~~~~~
      |   PyTuple_SetItem

And if an attempt is made to import and use the function from the built .so file, using python3 -c 'import my_module as mm; print(mm.my_function())', the following error is emitted:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: /home/user/cython_bug/my_module.cpython-310-x86_64-linux-gnu.so: undefined symbol: PyTuple_SET_ITEM

Code to reproduce the behaviour:
Cython code (my_module.pyx):
# cython: language_level=3

def my_function():
    firstword = "greetings"
    mesg = f"{firstword} {firstword}"
    return 42

setup.py script:
from setuptools import setup, Extension
from Cython.Build import cythonize

extensions = [
    Extension(
        name="my_module",
        sources=["my_module.pyx"],
        language="c",
        extra_compile_args=["-DCYTHON_LIMITED_API=1",
                            "-DPy_LIMITED_API=0x030a0000",
                            ],
    )
]

setup(
    name="my_cython_project",
    version="0.1",
    description="A sample Cython project",
    packages=["my_module"],
    ext_modules=cythonize(extensions),
)

Expected behaviour
When -DCYTHON_LIMITED_API=1 and -DPy_LIMITED_API=0x030a0000 are passed as compiler options, generated code should't refer to undeclared functions.
It should be possible to build a shared library with python3 setup.py build_ext --inplace, and then import and use it with python3 -c 'import my_module as mm; print(mm.my_function())'.
(At which point, the result "42" should be printed, in this case.)
OS
Linux
Python version
3.10.12 (but also occurs for Python 3.11.9)
Cython version
3.0.10
Additional context
The generated code constructs a tuple, and then attempts to set elements of the tuple using code like this:
  PyTuple_SET_ITEM(__pyx_t_1, 0, __pyx_v_firstword);

But PyTuple_SET_ITEM never gets declared, if the -DCYTHON_LIMITED_API=1 and
-DPy_LIMITED_API=0x030a0000 options are passed to the Cython compiler. (The code compiles without error if those options are not passed: but then the built .so file can't be used with other versions of Python.)
The call to PyTuple_SET_ITEM is generated due to the following bit of Python code:
  mesg = f"{firstword} {firstword}"

If the line is removed, or the f-string changed to just f"{firstword} ", that call no longer gets generated.

It's worth trying with the master branch (or the limited-api-preview branch which also contains a few unmerged PRs). The master branch has significant improvements in the limited API (but still isn't perfect).
The 3.0 branch only has absolutely minimal support for the limited API - while there are modules that compile, they don't do a lot.
Improvements to the limited API are going in the master branch rather than the 3.0 release branch so if the limited API is important to you then you'll have to use that for now.

I'll close this because I'm reasonably sure that f-strings are fixed in master. But do let me know if you try it and it isn't true.

I'll give the master branch a go - cheers.

Can confirm that this bug is fixed in master :)
But hopefully this report will be useful to anyone else encountering the same problem. I was just using the latest release, not realizing master would be the better option.


CFF Royale

name: Clash Files Royale
key: CFF
color: black
emblem: A_Char_Knight_02
info:
  logo: /static/img/brands/logo/cff.jpg

  description: >
    CFF Royale is a Mature Clash Royale Clan Family Devoted to their love of Pizza...
    just joking, we do love pizza but we love clash royale more. While we push in war
    we encourage growth and communication throughout both of our clans and want players to
    better themselves while feeling at home with family. We keep it cheesy and saucy!

  social:
    - discord: http://discord.gg/adDyDTa
    - website: https://theclashfiles.com/
    - instagram: https://www.instagram.com/CFF_Royale
    - twitter: http://twitter.com/TheClashFiles
clans:
  - name: CFF Thin Crust
    tag: #J8PVYG2
  - name: CFF Deep Deep Dish
    tag: #U99QLV0

It sent me saying I had a wrong clan tag
On Fri, Feb 22, 2019, 11:01 AM SML<EMAIL_ADDRESS>wrote:

What is the current issue / what has changed?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RoyaleAPI/family-config/issues/20#issuecomment-466426306,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AtaZDuCOLZiQaZZ-0p3sAaVzCHiqo4XEks5vQAZjgaJpZM4bJuF_
.

Oh sorry. I didn't realize. Thank you!
On Mon, Feb 25, 2019, 11:09 AM SML<EMAIL_ADDRESS>wrote:

But I’ve updated it to the right tag already in the original issue. Are
these correct? https://royaleapi.com/f/CFF
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RoyaleAPI/family-config/issues/20#issuecomment-467046842,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AtaZDov3Nmc4ex3gnnT4GtMyBHskW9lpks5vQ_yigaJpZM4bJuF_
.


Fix #106 - Fix javadocs so they compile

Summary:
This change re-formats a few Javadocs so they compile using ./gradlew javadoc. Fixes #106.
Expected behavior:
./gradlew javadoc now successfully completes:

Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with gradle test to make sure you didn't break anything
[x] Format the title like "Fix #<issue_number> - " (for example - "Fix #1111 - Check for null value before using field")
[x] Linked all relevant issues
[x] Include screenshot(s) showing how this pull request works and fixes the issue(s)

Thanks @barbeau , I keep this PR in mind for future modification and addition to javadocs to avoid error when compiling


2017 Korean Crisis

"In 2017, tensions with North Korea worsened with the inauguration of U.S. President Donald Trump, whose administration adopted a more assertive stance than the preceding Obama administration. In April, Trump said in an interview that he was sending a "powerful armada", consisting of the USS Carl Vinson and its carrier strike group, to Korea.[99][100][101] On April 24 the Japanese destroyers Ashigara and Samidare participated with the USS Carl Vinson in tactical training drills near the Philippines; North Korea threatened to sink her with a single strike.[102]
On May 3, North Korea issued a rare and harshly worded criticism of its chief ally, China, stating that "One must clearly understand that the D.P.R.K.'s line of access to nukes for the existence and development of the country can neither be changed nor shaken[...] And that the D.P.R.K. will never beg for the maintenance of friendship with China, risking its nuclear program which is as precious as its own life, no matter how valuable the friendship is... China should no longer try to test the limits of the D.P.R.K.'s patience[...] China had better ponder over the grave consequences to be entailed by its reckless act of chopping down the pillar of the D.P.R.K.-China relations." The harsh commentary also accused the Chinese media of dancing to the tune of the U.S.[103]
On July 4, 2017, North Korea successfully conducted its first test of an intercontinental ballistic missile (ICBM), named Hwasong-14.[104] It conducted another test on 28 July.[105] On August 5, 2017, the UN unanimously imposed further sanctions on North Korea over its nuclear program. North Korea responded saying that it was a "violent violation of our sovereignty" and that it would make the US "pay the price for its crime... thousands of times" [106]
On August 8, 2017, President Donald Trump warned that North Korean nuclear threats "will be met with fire, fury and frankly power, the likes of which the world has never seen before". North Korea responded by announced it was considering plans to attack US military bases in the US territory of Guam.[107] On August 10, 2017, North Korean Lt. Gen. Kim Rak-gyom responded to Trump, saying his words were "nonsense" and asserting that "reasonable dialog" wasn't possible with Trump. The North Korean governmental news agency KCNA reported that Kim Jong-un's military will be able to fire four ICBMs, type Hwasong-12, into the Philippine Sea just 30-40 kilometres away from the island Guam itself. The flight time of their Hwasong-12 will be exactly 17 minutes and 45 seconds. (This plan could possibly be put into effect mid August, 2017, according to the KCNA).[108]
Guam Homeland Security spokeswoman Jenna Gaminde posits in the Pacific Daily News a flight time of 14 minutes, however, and avers in the event of missile launches that Guam's 15 All-Hazards Alert Warning System sirens would sound, whereupon the Civil Defense department would use all forms of mass media, including social media, to inform the public.[109]
Japan stands ready to defend Guam (and hence the United States) with their anti-missile system MIM-140 Patriot. Vehicles of this system have already been deployed at the Ministry of Defence of Japan in Tokyo. [110]"
Source: https://en.wikipedia.org/wiki/Korean_conflict#The_Trump_era

What is the underpinnings here? Nuclear proliferation? The ability of the "nuclear club" to prevent other notions to acquire the Nuclear bomb and ICBMs? We could considering giving US/(rank 1 nuclear power) (and may by USSR if communist) an event when a country proceeds with the nuclear/missile WMD program decisions, where they threatens with consequences.

The of underpinnings are a mix of nuclear proliferation and spheres of influence, I know this may sound a little bit confusing but I will try to explain it using several examples of countries that have nuclear weapons but are not in the nuclear club (USA, Russia/USSR, UK, France and China)
North Korea
The history of the North Korean nuclear weapon programme is already quite well known so I'm not really rally going to post anything about its history. North Korea has managed to avoid the worst effects of the constant economic sanctions being placed on it by great powers such as the US because North Korea's most important ally and trading partner China has vetoed any international sanctions by the UN against North Korea solidifying the country as part of the Chinese sphere of influence however now it appears that things are changing as since China currently wants to expand the influence across the globe, having a pariah state in your sphere of influence is becoming more of an unnecessary burden then a useful asset.
India and Pakistan
During the Cold War, the Indian subcontinent was often the place of many conflicts between India (supported by the USSR) and Pakistan (supported by the USA), however after the collapse of the Soviet Union, American aid to Pakistan drastically declined during the 1990s as it was no longer necessary for the US to fund proxy conflicts against their main rivals at that time, this had created a situation both India and Pakistan had no backing from any of the great powers. When both India and Pakistan greatly expanded their nuclear weapons in 1998 the G8 applied economic sanctions to both of these countries. However after the sanctions on both Pakistan and India were lifted due to ineffectiveness of the sanctions and their use as strategic allies by the US in the War on Terror.
Israel
Although it has never admitted  nor denied having nuclear weapons, Israel is widely believed to have a current stockpile of 80 to 400 nuclear weapons. The Israeli nuclear weapons programme started shortly after the Israeli's state founding in 1948 with the first steps being investigating the nuclear field. Over the next decades Israel would secretly receive support from outside powers with their nuclear weapons programme such as France which in 1958, France aided in the construction of the Negev Nuclear Research Center. It is thought that Israel created their first nuclear weapon in December 1969.  It wasn't until 1986 when extensive details of the weapons program were first provided by  Mordechai Vanunu, a technician formerly employed at the Negev Nuclear Research Center who was later kidnapped by the Mossad where he was brought back into Israel and was sentenced to 18 years in prison for treason ans espionage. Due to Israel being an important country in the US sphere of influence it has largely avoided sanctions.


[help]dbg with lambda

As you may know, some times dbg expression may be an proc of lamda showing as below
int factorial(int n) {
  if (dbg(n <= 1)) {
    return dbg(1);
  } else {
    return dbg([&](){ printf("%d\n", n);
      return n * factorial(n - 1);
    }());
  }
}

but compiler report an error
main.cpp:9:16: error: lambda expression in an unevaluated operand
    return dbg([&](){

so I make a compromise to make compiler happy
int factorial(int n) {
  if (dbg(n <= 1)) {
    return dbg(1);
  } else {
    auto a = [&](){
      printf("%d\n", n);
      return n * factorial(n - 1);
    };
    return dbg(a());
  }
}

Is there a  solution to avoid the stack variable when DBG_MACRO_DISABLE is true

Thank you for reporting this.
Here is a smaller example to reproduce this:
dbg([]() { return 42; }());

This does actually compile and work if DBG_MACRO_DISABLE is set. However, as you noticed, it does not compile if the dbg macro is enabled. I get:

error: lambda-expression in unevaluated context only available with ‘-std=c++2a’ or ‘-std=gnu++2a’

The problem is that we use decltype(…) on the expression inside of dbg(…)
#define dbg(...)                                                     \
  dbg_macro::DebugOutput(__FILE__, __LINE__, __func__, #__VA_ARGS__) \
      .print(dbg_macro::type_name<decltype(__VA_ARGS__)>(), (__VA_ARGS__))

This leads to the "in unevaluated context" error.
This will actually work with C++20, but I don't know how to fix this for older versions. It would be great if we could at least generate a proxy type (dbg_macro::NoTypeAnnotation) if decltype(…) fails.


Tuple argument are handled inconsistently

For a function argument that is a tuple, when the argument is referenced by the argument name, you may or may not get the same tuple (as denoted by obj.ReferenceEquals)
Repro steps
Given
let source = [(1,1); (2,2)]

source
|> List.iter (fun outer ->
    source
    |> List.exists (fun inner -> obj.ReferenceEquals (outer, inner)) // but Seq.exists fails!!
    |> fun found -> if not found then failwith "boom!")

printfn "Hooray!"

The output is "Hooray!" but if the List.exists is change to Seq.exists then the exception condition is hit.
Expected behavior
The argument, when reference by name, should always be the original object.
Actual behavior
Sometimes, and I'm not sure the conditions under which it decides, the tuple is split and recreated in a new Tuple object. Even in optimized code. Neither of the exists function are marked as inline.
Known workarounds
Don't do reference equality checks on tuples!
Related information
Using Ilspy, it can be seen that for the List.exists case the following function object is created:
internal class clo@6-1 : FSharpFunc<Tuple<int, int>, bool>
{
	public Tuple<int, int> outer;

	[DebuggerNonUserCode, CompilerGenerated]
	internal clo@6-1(Tuple<int, int> outer)
	{
		this.outer = outer;
	}

	public override bool Invoke(Tuple<int, int> inner)
	{
		return object.ReferenceEquals(this.outer, inner);
	}
}

And for Seq.exists the following is created:
internal class main@9-1 : FSharpFunc<Tuple<int, int>, bool>
{
	public Tuple<int, int> outer;

	[DebuggerNonUserCode, CompilerGenerated]
	internal main@9-1(Tuple<int, int> outer)
	{
		this.outer = outer;
	}

	public override bool Invoke(Tuple<int, int> tupledArg)
	{
		int item = tupledArg.Item1;
		int item2 = tupledArg.Item2;
		Tuple<int, int> objB = new Tuple<int, int>(item, item2);
		return object.ReferenceEquals(this.outer, objB);
	}
}

In the slightly modified case:
let source = [(1,1); (2,2)]

let (*inline*) referenceEquals outer inner = obj.ReferenceEquals (outer, inner)

source
|> List.iter (fun outer ->
    source
    |> Seq.exists (referenceEquals outer)
    |> fun found -> if not found then failwith "boom!")

printfn "Hooray!"

This works, but if the inline is uncommented then it fails again...

@manofstick I'll close this as by design. IIRC the F# Language spec basically says that tuples may be made and consumed as much as the F# compiler likes, and ReferenceEquals is meaningless for these types.  We can dig out the relevant wording if you like

@dsyme
No worries; but ConstraintSolver.fs should be modified to remove this use of undefined behaviour. (Looks like it had already been thought of, given the comment).
And I guess I would have also thought that the optimizer would have removed the additional tuple construct. But anyway.

No worries; but ConstraintSolver.fs should be modified to remove this use of undefined behaviour. (Looks like it had already been thought of, given the comment).

Absolutely, I had no idea.

And I guess I would have also thought that the optimizer would have removed the additional tuple construct.

100% agreed
let's track those as specific other issues?


test sanity [ Don not merge ]

Coverage remained the same at 84.596% when pulling b735b1c9e0a0925fee48f78241d5c824fd1a292f on ambiknai:testsanity into 05199f71fafe7217b788abaffa3a2dfb2a68b495 on kubernetes-sigs:master.

Closing as testing completed and pre submit works as expected


[WIP] Release 1.1.0

feat: hint user install types/rax https://github.com/appworks-lab/pack/pull/854
fix: rax-spa project targets null https://github.com/appworks-lab/pack/pull/862
Chore: update webview icon https://github.com/appworks-lab/pack/pull/856 https://github.com/appworks-lab/pack/pull/846
feat: add recommend extensions https://github.com/appworks-lab/pack/pull/837
fix: only exit process when prepublishOnly https://github.com/appworks-lab/pack/pull/836
fix: make sure that the start & end fields exist https://github.com/appworks-lab/pack/pull/838

Codecov Report

Merging #863 (29ea389) into master (701bc48) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 29ea389 differs from pull request most recent head 8c8df83. Consider uploading reports for the commit 8c8df83 to get more accurate results

@@           Coverage Diff           @@
##           master     #863   +/-   ##
=======================================
  Coverage   57.14%   57.14%
=======================================
  Files           1        1
  Lines          70       70
  Branches       15       15
=======================================
  Hits           40       40
  Misses         30       30

Continue to review full report at Codecov.

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


Scan RF Codes

Hi, I just installed you plugin for Homebridge. First of all, let me tell you it's an amazing work. Works like a charm with my Air Conditioner, and it's super easy to configure.
In the case of my windows shades, they work with RF, and I just can't learn the HEX Codes, because they change randomly on every learn. I saw a previous thread where you solved it on v2.2.1 of your plugin. I think I am using the latest version of your plugin, but for me it's not working.
The shades work great with the Broadlink App.
Any help will be much appreciated.
Best regards!

I suspect this is related to #119 - keep an eye on that.


Powerapps SQL Connection

I have been trying to follow these instructions to connect to a local instance of SQL Server.  However, it only provided the option for a host name (localhost) and database name.
I have installed the local gateway.  I do not get the option to use the gateway or even to put in credentials.  I continue to get a bad gateway error.    Clearly I am missing something here, but unsure of the next steps to correct this problem.   Is there somewhere I need to configure to use the local gateway?
Thanks for help.  Marc.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bbcbf308-e9b9-d59d-5b1b-ba224dcc1aa9
Version Independent ID: 5959353c-ab28-1bc6-8c21-3b186c1bf61d
Content: Overview of the SQL Server connection - Power Apps
Content Source: powerapps-docs/maker/canvas-apps/connections/connection-azure-sqldatabase.md
Service: powerapps
GitHub Login: @lancedMicrosoft
Microsoft Alias: lanced

Thank you for reaching out. Please use Help&Support for help with investigation of this issue.


python: How to make result of overridePythonAttrs overridable?

Issue description
The currently recommended way of overriding Python packages seem to be using overridePythonAttrs function of buildPythonPackage. Unfortunately, overridePythonAttrs does not seem to be overridable by itself. If I manage to chain multiple overridePythonAttrs (e.g. with fixed-points overlays) I get attribute 'overridePythonAttrs' missing.
Yet, overrideDerivation was overridable.
Am I missing something? Would it be hard to make overridePythonAttrs overridable?
Steps to reproduce
Works
with import <nixpkgs> {};

(pythonPackages.pillow.overrideDerivation(old: {
  name = "pillow-override";
})).overrideDerivation(old: {
})

Does not
with import <nixpkgs> {};

(pythonPackages.pillow.overridePythonAttrs(old: {
  name = "pillow-override";
})).overridePythonAttrs(old: {
})

I tried to look into how this is done for overrideAttrs, but this seem be still beyond my Nix skills.

Could you test https://github.com/NixOS/nixpkgs/pull/32318.


Events Successfully Sent to Destination but Not Synced with Warehouse (eu portal)

hi, we are testing the Analytics-CSharp sdk and we ran into an issue: even if the events get received in our destinations, we don't see them in the debugger and either they don't get synced with the warehouse:
to give you more informations here is the last test we made:

we created a .net source in segment
we sent a sample track event using the sdk
we received the event in our destination, but not in the debugger
we saw that the synced rows with our warehouse remained 0 for that source

here is our configuration
var configuration = new Configuration("***",     flushAt: 1,     flushInterval: 10,     exceptionHandler: new ErrorHandler(),     apiHost:"events.eu1.segmentapis.com/",     storageProvider:new InMemoryStorageProvider());
here are our logs:
Message: Analytics starting = False
Message: Segment.io performing flush
Message: Analytics starting = False
Message: Analytics starting = True
Message: Segment.io running {"type":"track","event":"h","properties":{},"anonymousId":"173a40ff-90fc-4354-950c-4c465c61eed4","messageId":"1513bb45-9e86-4638-9ad3-227ea10340e0","userId":null,"timestamp":"2024-01-29T14:20:55.7609390Z","context":{"os": "Microsoft Windows 10.0.20348","platform": ".NET","library": {"name": "Analytics-CSharp","version": "2.3.0"}},"integrations":{},"metrics":null,"_metadata":{"bundled":[],"unbundled":["segment_lambda(test_portal EU)"],"bundledIds":[]}}
Message: Segment.io performing flush
Message: Segment.io uploaded jbu5CUhUV2hWp6YN82pAz7o7ctxBB6nb-0.json
Message: Segment.io performing flush
could this problem be related to the use of the sdk? (since we are not having the same issue with other type of sources)
thanks a lot in advance

hey @mnasini, thanks for reporting this issue. the Segment Debugger does not show every event arrived, instead it does a sampling on the events. If your destination has received the events, that means Segment has received it first. please reach out to our backend team in regards of the warehouse not synced issue.

@mnasini Could you please try setting the ApiUrl to events.eu1.segmentapis.com/v1. I've experienced the same issues trying to set this SDK up until I figured that out. Also, you must build the Analytics-CSharp yourself since the ApiHost currently is not honored in the event pipeline - the changes were made in #79 (two months ago) but they're still not released...

hey @nmaricmoberg, that's a good callout. I'll escalate a release and get back to you all

hi @mnasini and @nmaricmoberg , 2.3.2 is out. please have a try

hi @wenxi-zeng, 2.3.2 appears to be working fine with the EU api host. thank you for the escalated release! :)

hello @wenxi-zeng i can confirm is working, thanks a lot to everyone!


IHasToBeRemovedWhenTransisionedOut

Hi Eric-Paul,
First I want to tell you that the Navigator-as3 is something I am using for every project I have done for about a year. It really takes the pain out of navigation in every AS3 projects.
But something is bothering me. The issue I want to report has to do with the integration with Robotlegs and PureMVC. Although I never thought about it when I used PureMVC. But that's more because I had a different approach back then.
One of the coolest things in Robotlegs is, when you add something on the stage the needed mediator gets created just in time so you can manipulate the view before the user sees it. So when the user gets redirected to a NavigationState which needs a certain view you add it and the mediator gets created... Right?
Right now I am creating views which are doing pretty heavy stuff (they are displaying big sets of CPU intensive graphics). I want to show these data in different views/States i.e.:

/lists/flower-view
/lists/row-view
/lists/thumb-view
/lists/another-awesome-view

All these view mediators respond to contextEvents (that's where my DataUpdate Event comes from). And because the view and mediator never get removed they keep on responding to Events sent to them.
And that's my problem. My opinion is if you addChild the clip in the dungons of the Navigator we should be able to undo this. I tried to remove the view from the mediator but that resulted in lots of Errors!
My suggestion is the following; why not add another interface to say you want the view to be removed when possible..
So here I introduce my new friend:
IHasToBeRemovedWhenTransisionedOut
I hope you can fullfill my request.
Thanks,
Jankees

HI guys,
First of all, thanks for sharing !
And my question, i don't find the remove method, where is it ?
And in my test, if i remove the view after the transitionOutComplete in my mediator, the view is well removed and if i back again to this view, it's re-created and added to stage again ? so why we need a remove method ?
but i agree that it could be more elegant to have an interface for doing this as pure/clean as possible..
thks,
Fred

sure it could be more elegant to have this feature, so we don't have to code aech time with the transitionOutComplete.. ;)


Any way to control shapefile alpha?

The readshapefile method does not have the capability of passing an alpha keyword argument as all other methods.
Is there any way to control the opacity of the lines drawn by the readshapefile method?

Hi @guidocioni! I was looking at the code and in effect the alpha argument is not available in readshapefile. However, I was testing with the underlying LineCollection call inside readshapefile and of course this is possible, so the limitation comes from the basemap side.
Maybe it is a good idea to include it for basemap 1.4.0 so that it is more user-friendly. In the meantime, one workaround for you would be to provide the color argument as a 4-value tuple, e.g. (R, G, B, A), where A is the opacity. The four values should be between 0 and 1.


Remove nlohmann json submodule and add header directly instead

There were random git submodule checkout errors in MAVSDK CI for that repo. It's not clear why, but a reason could be that the repo is large. @julianoes
One of the repo file names is too long and causes failures on Windows 10. https://github.com/mavlink/qgroundcontrol/issues/11747

Tested with MAVSDK, and it still builds with this PR.

Thanks @bkueng!


Adding Wi-Fi P2P support for nearby Android devices to detect each other

Feature description
In addition to Bluetooth Low Energy, Wi-Fi P2P should also be used to enable the communication between nearby Android devices which don't support Bluetooth Peripheral mode.
Wi-Fi P2P is very well supported by Android 4+
I understand Google Exposure Notification APIs are used here but could you forward this request to Google?

Problem and motivation
Both Bluetooth Central mode and Bluetooth Peripheral mode need to be supported by the Android devices in order for the Google Exposure Notification APIs to work and it is said Bluetooth Peripheral mode is supported by Android 5+. But I believe there are still Android devices running Android 6+ that don't support Bluetooth Peripheral mode. (Depending on what kind of Bluetooth chipset is used and the manufacturer.)

Is this something you're interested in working on
Please forward this request to Google.

Internal Tracking ID: EXPOSUREAPP-2185

Actually this is a nice idea, but please keep two things in mind:
First, the interoperability with iOS devices needs to be provided at any point and because iOS has no API for Wifi Direct, this would be a one sided platform feature. The EN framework is developed together between Google and Apple, so it is not possible for Google to add platform specified features.
Secondly, you can track distances with Wi-Fi RTT (Round-Trip-Time), but this was introduced in Android 9 (API Level 28), so adoption is drastically lower than with BLE. Also this standard was designed for static beacons to track indoor movement, and not to track distance between to moving/dynamic devices. I know that there is true range multilateration (RSSI) (which got implemented in API Level 1), but this is heavily inaccurate and not usable for fine distance measurements.
So there is practically no way of tracking a position between two devices precisely enough using the Wifi-protocol.

Should this be transferred to the Android repo as it is Android exclusive?


sdk release 12.0.2

OPS Build status updates of commit 2983505:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

BingAds/bingads-12/guides/release-notes.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Install fails due to python3.7-dev on Kali

Running "sudo apt-get install autoconf automake libtool python3.7-dev python3-tk jq awscli" fails as following:
Reading package list ... Done
Building dependency tree ... Done
Reading state information ... Done
E: Unable to locate package python3.7-dev
E: Couldn't find any package by glob 'python3.7-dev'
E: Couldn't find any package by regex 'python3.7-dev'

Hello , use the package only python3 , the installation will be :
apt-get install autoconf automake libtool python3 python3-tk jq awscli


New Editors

Coda
Fix forEach() statements
Add validation for macOS into Visual Studio

Thanks for the loop fix


Question about TMC13

Hi,
I have another question about the file testTMC.py for lidar point clouds.
Before the compression, the coordinates of lidar point clouds are shifted by mean value and normalized by max value.
I am curios why the mean value and max value are not stored and counted as a part of  bit-stream.

Yes, they should be coded directly, but this code omitted them. In fact, they account for very few bits.

Thank you for the reply!


run tools.file.download hangs or kills debug session on lollipop

running drozer on macosx mavericks
latest lollipop on Nexus 4
dz> run tools.file.download /data/app/package/some.apk <dest_path>

@ccjon ; can you provide more info please

I have no idea what this was about... previous life.. sorry about the flotsam.


Make pydantic validation friendlier, when loading a builder from a _quarto.yml file

Currently, our use of pydantic validation errors can get pretty cryptic. It would be nice if we could point to the area of the source file, where validation is failing, with a very friendly and humanly interpretable message.

Pydantic doesn't always seem to kick in - if you have a top level config it will error in a different way.  For example, consider the below config:
quartodoc:
  foo: bar
  style: pkgdown
  dir: api
...

Will result in this error
Traceback (most recent call last):
  File "/opt/anaconda3/bin/quartodoc", line 33, in <module>
    sys.exit(load_entry_point('quartodoc', 'console_scripts', 'quartodoc')())
  File "/opt/anaconda3/lib/python3.9/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/opt/anaconda3/lib/python3.9/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/opt/anaconda3/lib/python3.9/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/opt/anaconda3/lib/python3.9/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/opt/anaconda3/lib/python3.9/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/Users/hamel/github/quartodoc/quartodoc/__main__.py", line 52, in build
    builder = Builder.from_quarto_config(config)
  File "/Users/hamel/github/quartodoc/quartodoc/autosummary.py", line 593, in from_quarto_config
    return cls_builder(**{k: v for k, v in cfg.items() if k != "style"})
TypeError: __init__() got an unexpected keyword argument 'foo'

I'm going to try and focus on the issue in https://github.com/machow/quartodoc/issues/138 that deals with situations when pydantic validation error is being raise

I think right now we only feed part of the config in, but if it will help with giving better feedback, having pydantic serialize the full config seems like fair game.
(Similar, I'm not sure if pydantic gives better validation messages when serializing directly from json. But if it does, it also seems like fair game to somehow tap into that)

From pairing, maybe it's possible to add line information using this approach?:
https://github.com/pydantic/pydantic/issues/1273#issuecomment-593472805

implemented in https://github.com/machow/quartodoc/releases/tag/v0.3.4


Update utils_keras.py

Added a VGG-type CNN baseline model that has increased resiliency to two categories of adversarial attacks compared to the existing baseline CNN model.

I signed it
Sent from my iPhone

On Sep 10, 2019, at 4:24 PM, googlebot<EMAIL_ADDRESS>wrote:
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it!) and we'll verify it.
What to do if you already signed the CLA
Individual signers
It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.
Corporate signers
Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.
ℹ Googlers: Go here for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Using ampersand in query string

The query I'm trying to execute is:
localhost:3000/ads?subcategory=Health%20%26%20Beauty
So I would expect req.query.subcategory to be "Health & Beauty" instead subcategory is "Health "
and req.query[" Beauty"] is "". Is this supposed to happen? It seems the url is being decoded before it splits on ampersands. Is this a problem with some other url parsing package I am using?
I'm not sure where this is supposed to be posted as an issue.

It is not supposed to happen and I'm not able to reproduce with Express 4.14.0 using the following app:
var express = require('express')
var app = express()

app.use((req, res) => {
  res.send('got query: ' + JSON.stringify(req.query))
})

app.listen(4000)

And then the test:
$ node t &
[1] 9420
$ curl -s http://localhost:4000/ads?subcategory=Health%20%26%20Beauty
got query: {"subcategory":"Health & Beauty"}

Why you use %26 instead of normal &? The issue is real and appears for version 4.16.2 too.
For a query: "A & A Travel" (typed in the browser) I am receiving req.query as:
{"q":"A "," A Travel":""


Experiment with various functionality provided by apollo android client

Description

Played around with graphql and apollo android client, using queries and mutations.
Observed the responses returned by the server by logging them.
Used the cache functionality provided by Apollo android client.

With reference to PR #8

@wtrocki @harshithdwivedi Please have a look at it.

I could not run thar but from just code impression we need to think how to structure app and avoid utils class. Generally splot app to different areas like data, cache etc. It will help later

Utils class was just like the Application class, for implementing the singleton pattern. Will change it to data, cache etc.

Maybe ignore me this time. Keep structure the way it works for you and when we get some complex implementation we can think how to separate concerns


What is the best way to train ?

I'm using mitie_sklearn and I want to ask about some things,

What is the best way to make data-set for the training? are there any optimum values? Also What is the optimum value for the number of data points per entity?
e.g. say I have 8 entity should each one of them contain equal numbers of data points? assume I have 100 data points on one of them. all of them should be the same ?

Should I make combination or rasa capable of doing combinations?
e.g. a) What is John's Last name.
b) What is John's age ?.
Should I train the third one like - Tell me The Last name and Age of John's.
or it doesn't need to be trained with combinations?

3)What is the best way to extract the generic entities such as "objects name" as it may contain any values e.g.  please tell me the price of XYZ.
I want to extract entity of XYZ as an Object name.
Thank you :)

The optimum number is whatever number it takes for your model to work well. Google overfitting vs undercutting. Ideally intent examples would be balanced, but entities don't need to be.
The more natural way someone would ask the second question is What is his age? using the context of the first question. This can be accomplished with Rasa Core.
I have no idea what you're asking. Entities are part part of the training data format. So XYZ would be labeled as an entity and it would be extracted with a value and a named. That's what makes it Named Entity Recognition.

Many thanks @wrathagom ,
let me explain what I meant in the 3rd one .
I know when extracting an entity like 'person' , the classifier would be robust to that , but what if I want to extract multiple entities like [SW engineer, programmer, student, etc..] and they all are persons and the context almost the same? what is the best way to handle this problem using rasa_nlu?

Seeing as you created a new issue for the 3rd question #548  I am guessing the other 2 are resolved. I'll close, but if you're still having trouble (not relating tot he 3rd item) then we can re-open.


Update PPP

Codecov Report

Merging #254 (e05ff8c) into master (16c63c5) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #254   +/-   ##
=========================================
  Coverage     55.51%   55.51%
  Complexity      610      610
=========================================
  Files           107      107
  Lines          2785     2785
  Branches        387      387
=========================================
  Hits           1546     1546
  Misses         1096     1096
  Partials        143      143

Impacted Files
Coverage Δ

...c/main/java/seedu/address/model/person/Height.java
63.63% <0.00%> (ø)

...c/main/java/seedu/address/model/person/Weight.java
63.63% <0.00%> (ø)

.../java/seedu/address/model/person/JerseyNumber.java
72.72% <0.00%> (ø)

Continue to review full report at Codecov.

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


Make sure db_table exits successfully on empty db

Follow-up to #729, seems like on an empty DB even though it is not being extracted, the function still doesn't return successfully, and so you cannot build your first package. Having return 0 is a simple way to ensure the function always succeeds.

Maybe it's more clear to put the return 0 at the top, in the sense of:
(( $(bsdtar -tf "$2" | wc -l) )) && return 0

bsdtar ...

Thanks!


Implement SchedulerFlags wrapper around scheduler env access

Replaces direct in-scheduler env access with an explicit Flags object.
A non-static flags object is used for two reasons:

support easy mocking in tests
make it painfully obvious when low-level code is reaching out into the system env

@nickbp I love everything about this.
Is there anything in particular you want review of?

retest this please

retest this please

@nickbp I think it's mostly outside the scope of this PR, but could this replace all of the environment setup that occurs in the individual schedulers' ServiceSpecTests? It seems like it would require that they extend SchedulerFlags with their own options, but then that type would probably need to be retained (instead of getting erased as just an instance of the base-level SchedulerFlags) to be of any use...just spitballing, but it'd be nice to unify how we approach this in both SDK and consuming code.
The need to add a SchedulerFlags argument to several methods in DefaultOfferRequirementProvider gives me a little pause, not because of this change so much as the implicit dependencies it exposes in that class, but it's something to keep in mind.

TBF, I think one of Nick's goals is to make people pause and be, "Wait should this really be an envvar?"
Agreed on cleaning up the downstream tests as well.

Note, I ran this locally and it seems to be failing CI due to:
    at com.mesosphere.sdk.scheduler.SchedulerFlags$FlagException.notFound(SchedulerFlags.java:29)
    at com.mesosphere.sdk.scheduler.SchedulerFlags$FlagStore.getRequired(SchedulerFlags.java:178)
    at com.mesosphere.sdk.scheduler.SchedulerFlags$FlagStore.access$300(SchedulerFlags.java:154)
    at com.mesosphere.sdk.scheduler.SchedulerFlags.getJavaHome(SchedulerFlags.java:135)
    at com.mesosphere.sdk.specification.DefaultService.run(DefaultService.java:88)
    at com.mesosphere.sdk.helloworld.scheduler.Main.main(Main.java:21)```

Some schedulers weren't specifying JAVA_HOME. Cleaned them up. The system works!

retest this please (jenkins threw an NPE)

retest this please

retest this please

@nickbp:  you should rebase on master to absorb the elastic test fix if this fails again


Add DNSSEC

This PR is proposal to add secure on the DNS

DNSSEC
prevent hack from rainbow tables

Ability to have more than 1 DNS (should be 2 or 3+)

Hey, sorry for the late response. Looks good, thanks! I will review it in detail and then merge it.

Hey, first, @dprandzioch thanks for the project, and @ianbogda - thanks for updates!
@ianbogda could we maybe create persistence commit as a separate PR? Seems to be very easy fix, and for sure very important one. If you want I could do this MR from my side.


Screenshot not showing the area I am trying to reach

Just a question, I am trying to reach a button way down on a page, and I get an error
The screenshot gets produced but don't show that part of the page, is this an issue or not?

This is not an issue. What you can do is try to scroll down to the button then perform the actions. This way the screenshot will capture the part of the screen that you need.


GPMD freezes with Wallpaper Engine

OS:
Windows 10
Issue Descriptions:
App completely freezes when opened while Wallpaper Engine is open. Music still plays. It unfreezes sometimes but usually stays frozen till closed via task manager.
Steps to Reproduce:
Open Wallpaper Engine with wallpaper applied. Then open GPMD and play a song. A couple seconds into the song and the entire app will freeze. Can only be closed by task manager.

This sounds like an issue with windows 10 notifications that currently isn't capable of being fixed on our side. Try disabling desktop notifications in GPM settings.

I use the music player and the wallpaper engine and haven't had any problems.
I also coincidentally have notifications turned off - so that very well could be it.

Disabling desktop notifications did the trick for me - no more GPMDP freezing with an active wallpaper engine.

Looks like desktop notifications was the problem. I don't know how to close this but thanks for the help!


Feature request: allow to configure sauce connect version

hi,
This is a feature request.
we are currently experiencing stability issues  using the sauce connect tunnel. after a conversation with the sauce labs support it seems that the problem is at their end with the latest version of sauce connect (v4.5.3). Their current recommendation is to use v4.5.1 until the issue is resolved.
However it seems that the gradle-sauce-connect-plugin always uses the latest version of sauce connect. I think in general it would be helpful, if the plugin allowed to also configure a specific version of sauce connect to use.

Yeah, as an explanation we use SauceLab's endpoint that informs us of available versions which are https://saucelabs.com/versions.json We also use the available checksum to avoid corrupted downloads.
A good solution would be to allow developers to provide URL and digest as an option. Both which could be found from https://wiki.saucelabs.com/display/DOCS/Sauce+Connect+Proxy

@johnroach yes, i saw that in the sourcecode of the plugin. actually its really conveninent that the plugin determines the latest version automatically.
based on your comment and our needs i experimented a bit and came up with this version: https://github.com/abendt/Gradle-Sauce-Connect-Plugin
if it is acceptable for you i could make a PR out of it.


NIFI-3949: Updated Grok Reader to allow for sub-patterns to be used w…

…hen determining the schema
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

+1 Looks good, was able to successfully run the expression that previously caused problems


config: migrate dashboard into pingcap org

/hold
Waiting @breeswish review.

/hold cancel
/status can-merge


R package: Make it possible to disable parallelization

Thanks for your contribution!
I am running an experiment where I want to parallelize in another dimension that using OpenMP in BanditPAM. Actually, it was caused by what I think is a race condition (maybe from multiple parallelizations), and I want to avoid that - an I am already parallelizing elsewhere.
I made an option to disable parallelization, although the package is compiled with OpenMP. Please see this pull request.

Thank you for submitting a PR! @bnaras could you take a look?


Tomhaile/ch17200/initial load error trying to load reporting

https://app.clubhouse.io/augur/story/17200/initial-load-error-trying-to-load-reporting-markets

Coverage remained the same at 62.077% when pulling 7a0d1aa941b7fbc452bde3db34a2bdca1ad5290e on tomhaile/ch17200/initial-load-error-trying-to-load-reporting into e87fcd50e12dc5ef1871a3630e8d4211e48784e1 on master.


There are extra options in the completion list when typing a letter in double quote

OS: All
Build Version: 20201113.10
Repro Steps:

Open dependon-with-copy2.json file in VS Code -> Click on the second resource and delete the existing dependsOn property  -> Type a letter, e.g. "o".
Check the completions list.

Expect:
Show all options contained the letter in the completion list.
Actual:
There are two extra in the completion list, e.g. "o".

The search also occurs on information that doesn't appear in the title (description, etc.).  So this is desired if not ideal behavior.

@StephenWeatherford Sorry I don't understand what you mean.

The search also occurs on information that doesn't appear in the title (description, etc.). So this is desired if not ideal behavior.

When typing a letter "o", the completion list displays as the following:

When typing a letter "l", the completion list displays as the following:

When typing a letter "j", the completion list displays as the following:

There is no rule between the completion list and the letters typed.


Broken developer manual link to latest documentation

doc/Developer_Manual/index.rst says:

developers should usually be reading either their locally built copy of the documentation, or the online nightly documentation build

and points to http://buildbot.topographica.org/doc/Developer_Manual/index.html, but that doesn't work.

Nowadays I think topographica.org shows the latest changes, not the latest released changes, so we can just remove that sentence.


cavy-cli init

It would be useful if cavy-cli had an init command that:

creates an index.test.js file
copies in anything that exists in index.js, wrapped in the Cavy Tester component
creates a example spec file in a spec folder and passes it into the Tester component

Close by #9


Data generation code

Where is the code that generates the data table linked from the paper?
The repo doesn't appear to contain the names of the headers in the data table (numsteps, problem_id, ...)

Which part are you interested in? The only columns that are needed to run and evaluate the scenario are "code", "input", and "output". You may also use "contest_date" to evaluate across time.
Unfortunately, we are not planning on releasing the code used to generate the specific samples.

"we are not planning on releasing the code used to generate the specific samples" - do you mean you are not planning to release the code that generates the data to be evaluated upon, or the code that is generated by the model?

We are not planning to release the code that generates the dataset (evaluation set).

Model generated codes can be found at https://huggingface.co/spaces/livecodebench/code_generation_samples/tree/main


TW 375: Command Information

What was changed
More information about command functionality, along with code examples, have been added.
Why?
CLI and Docs need more information.
How was this tested:

Any docs updates needed?

Changing per comments. After this, consider deleting the tool and editing the docs when necessary.


Add Maestro Dapp Platform builder tool

Checklist

[x] I have read the How to Contribute.
[x] I have read the Builder Tool Requirements
[x] I have run yarn build after adding my changes without getting any errors.

Builder Tool addition

Title: Maestro Dapp Platform
Description: Blockchain indexer, APIs and event management system for the Cardano blockchain.
Website:  https://www.gomaestro.org/dapp-platform
Get started: https://docs.gomaestro.org/
Tags:

http
hosted

From a quick look it might be better suited in the showcase section. (Similar to other services not a direct builder tool)

@rphair @katomm @fill-the-fill Can you please check my latest updates?

@katomm @fill-the-fill can you please approve?

@rphair When does this go into production?

@Vardominator generally editors can't even predict this.  Periodically, as you can imagine, staging gets merged into the production branch when everything seems to go well together.


Sync Docker compose scripts with backend (DSpace/DSpace)

The Docker compose scripts in the Angular UI have become outdated, and were never updated when the Entities test data set was updated on the backend in https://github.com/DSpace/DSpace/pull/2623
This means that the data set being used for e2e tests in GitHub CI is outdated, and this has recently resulted in errors which are not reproducible on the more recent Entities test data set. For example in https://github.com/DSpace/dspace-angular/pull/961/checks?check_run_id=1524916589
This PR updates all Docker compose scripts to include:

Comments describing / linking back to related dockers scripts (in backend project)
Updates Entities data sets to the same ones used by Backend.
Other minor updates to sync the scripts with related backend scripts (as necessary)

🎉 This fixes the Docker backend for e2e tests!  Merging this immediately.  Anyone having issues with e2e tests failing cause of Docker problems should rebase on main and hopefully that'll fix it.


yarn install fails inside /mnt with EINVAL for lstat during step 3

Your Windows build number:  Version 10.0.16273.1000

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)

Running yarn (install) in a directory inside /mnt/c/Users/foo/bar
$ pwd
/mnt/c/Users/duybui/code/web/old
$ yarn
yarn install v0.27.5
warning package.json: No license field
info No lockfile found.
warning<EMAIL_ADDRESS>No license field
[1/4] Resolving packages...
warning aurelia-cli > npm > request ><EMAIL_ADDRESS>Use uuid module instead
warning browser-sync > browser-sync-ui > weinre ><EMAIL_ADDRESS>express 2.x series is deprecated
warning browser-sync > browser-sync-ui > weinre > express ><EMAIL_ADDRESS>connect 1.x series is deprecated
[2/4] Fetching packages...
warning<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning<EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^15.0.0".
error An unexpected error occurred: "EINVAL: invalid argument, lstat '/mnt/c/Users/duybui/code/web/old/node_modules/accord/node_modules/cliui/README.md'".
info If you think this is a bug, please open a bug report with the information provided in "/mnt/c/Users/duybui/code/web/old/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

What's wrong / what should be happening instead:
Note that every time I run the command it may fail while lstat'ing a different file.

My current workaround is to create a node_modules directory outside /mnt, then ln -s it into my directory inside /mnt.

Related issue in the Yarn repo: yarnpkg/yarn#4188

Also getting this. I can install packages successfully using npm, so am I correct in thinking that this is a Yarn issue, not a WSL?

It's a WSL issue with the recent file system later changes

I see.

It fails on the new build of windows. I reverted back to 16251.rs3 and yarn works fine again

Adding @SvenGroot who is taking a look at this. Also, marking it as a bug.

Also fails on 16278.rs3, npm works fine

This looks like it's the same error in React Native's packager (roughly equivalent to webpack --watch):
✘130 ➜ yarn start
yarn start v1.0.1
$ node node_modules/react-native/local-cli/cli.js start
Scanning 723 folders for symlinks in /mnt/c/code/learning-hub/mobile-app/node_modules (80ms)
 ┌────────────────────────────────────────────────────────────────────────────┐
 │  Running packager on port 8081.                                            │
 │                                                                            │
 │  Keep this packager running while developing on any JS projects. Feel      │
 │  free to close this tab and run your own packager instance if you          │
 │  prefer.                                                                   │
 │                                                                            │
 │  https://github.com/facebook/react-native                                  │
 │                                                                            │
 └────────────────────────────────────────────────────────────────────────────┘
Looking for JS files in
   /mnt/c/code/learning-hub/mobile-app

Loading dependency graph...
React packager ready.

Loading dependency graph, done.
Bundling `index.android.js`
  Transforming modules  100.0% (913/913), done.
 ERROR  EINVAL: invalid argument, lstat '/mnt/c/code/learning-hub/mobile-app/.git/index.lock'
{"errno":-22,"code":"EINVAL","syscall":"lstat","path":"/mnt/c/code/learning-hub/mobile-app/.git/index.lock"}
Error: EINVAL: invalid argument, lstat '/mnt/c/code/learning-hub/mobile-app/.git/index.lock'
    at Error (native)

See http://facebook.github.io/react-native/docs/troubleshooting.html
for common problems and solutions.
error Command failed with exit code 11.

This one is pretty intermittent though.

We have been trying to get to the bottom of this issue, but the bug seems very evasive. Every time we try to gather an strace or put it under the debugger, it does not repro. Seems like some kind of race condition. If someone is able to get a strace of the failing command, that might shed some light. strace -o <trace_file> -ff <failing_cmd>

I attempted to create a react app using yarn create-react-app hello-api and ran it through the strace recommended.  I zipped up the output.
https://github.com/AndyGauge/yarn-debug/blob/master/yarn-fail.zip

When I run strace -o ~/trace.log yarn install the error does NOT show up.
When I run strace -o /dev/null yarn install the error DOES show up.

rails webpack:install fails with the same message.  The trace.log file: https://github.com/AndyGauge/yarn-debug/blob/master/trace.log

I was able to reproduce locally. You can download a zip of all of the trace files at https://www.dropbox.com/s/oy78n0qvtqqyxwb/yarn_trace.zip?dl=0

If it helps, for me the problem seems to be resolved in 16288.1.

No the original issue has absolutely NOT been resolved in latest insider (non skip-ahead) build.

I was able to reproduce this issue with strace on.
trace.zip

Thanks for all the input. We've been able to determine the root cause of this issue and are working on a fix.

You made my (our) day! Keep up the good work.

The news of the cause being determined is very, very welcome. I shall be glad to test it. Maybe the fix is in build 16296, which just landed here?

I was upgraded to 16296 yesterday and still had to work around the issue by moving across file systems to run yarn add I'm sure it still affects yarn install.

We're still working on the fix, so it's not available yet. I'll update this thread once the fix becomes available.

This issue has annoyed me for a month, expecting fix it in the next release.

@jingsam agree, this one is particularly painful.

I am having this error on Windows 10 Home 1709 16299.15

I upgraded to 17017.1000 and no longer observe this issue. Can someone confirm a fix?

Updated my Windows 10 Pro yesterday to 16299.15, which was already painful with .url shortcuts not working, night light having weird coloration, Nvidia driver 387.68 shitting themselves (why even install this version automatically, it's not even available from Nvidia themselves), and now WSL not handling yarn add properly.
This really is the worst Windows update for me so far. I'm reverting back to the previous Windows 10 version. Any ETA for when this is fixed?

@khuongduybui I also upgraded to 17017.1000 and the issue is no longer observed. Thanks!

I have upgraded to 17017.1000 but this issue still exists.
yarn install v0.27.5
[1/4] Resolving packages...
[2/4] Fetching packages...
warning<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning<EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>error An unexpected error occurred: "EINVAL: invalid argument, lstat<EMAIL_ADDRESS>info If you think this is a bug, please open a bug report with the information provided in "/mnt/d/Work/BlueSense/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

@skyzh I am using latest version of yarn 1.x and do not observe the problem. Maybe that could help.

Running 1709 (OS Build 17017.1000) and still seeing the issue;
bren@Crowley:/mnt/e/project$ yarn install
yarn install v1.1.0
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
error An unexpected error occurred: "EINVAL: invalid argument, lstat '/mnt/e/project/node_modules/amqplib/node_modules/string_decoder/index.js'".
info If you think this is a bug, please open a bug report with the information provided in "/mnt/e/project/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
bren@Crowley:/mnt/e/project$

Build 17017 does not have the fix for this issue yet. The fix has been checked in and is making its way through our system, and will hopefully be in an insider build sooner rather than later, but it's difficult for me to say when that will happen. We'll keep you informed.

Is it possible that fixes like that will be patched with normal windows updates?

This is working for me now after updating to 17017.rs_prerelease.171010-1400 with yarn 1.0.2.

@SvenGroot I installed the official release today and encountered this problem. I understand this will go out to insiders, but what about those of us not in the insider program - will this be available as an update through Windows Update or the Microsoft Store?
We rely on Yarn Workspaces - so this effectively stopped me from being able to work on our project, unless I roll back Windows 10 (which I might do tonight).

@SvenGroot  I was just hit by this when upgrading to the RTM fall update.
Can you confirm if there's an ETA for the fix and if it will be possible to get it without going through the insiders builds?

We are working to get this bug serviced in the Fall Creator's Update as soon as possible. Unfortunately, the timing of that depends on a lot of things besides just me, so I can't give you any dates. We'll keep you posted.

Thanks for the update, and looking forward to the fix.

Still getting failures in compilation of very large projects within lxss with gcc very occasionally reporting EINVAL. Re-running the compilation cures the problem, so it appears that the referenced file (a header, usually) is still occasionally turning into something odd, then coming back again. Built 17017.1000. This is a terrible pity, because WSL used to be totally reliable for the biggest compilations, like native GNU/Linux. Very sad to see it not working as it used to.

Unfortunately, Insider build 17025 does not appear to have the fix for this yet. However, it looks like it will be in the next Insider preview build. We're still working on getting this serviced on the Fall Creator's Update as well.

Thanks for letting me know.

😿

For some of us this issue is a massive showstopper and causing more than a little frustration. Don't forget that it's also a regression (at least from a user perspective), so I would expect it to be very high-priority. It has been about 3 weeks since the FCU landed and we haven't gotten much more than a vague "we're working on it", which doesn't exactly inspire a whole lot of confidence that this will be addressed in a timely manner. We would greatly appreciate a little more information/assurance about when/how the fix is going to land, so we can at least make better decision on how to mitigate the productivity loss caused in the meantime. Any insight into the process, even if it's just a hypothetical worst-case scenario, is better than having a question mark hanging over the whole thing (if it's not going to be speedy).
I don't want to sound ungrateful or anything - I'm very appreciative of the work that has gone into WSL, and from what I understand things like update timing are mostly outside the WSL team's control - but a little more transparency would go a long way to alleviate some of our concern.

This sort of thing paints Windows + WSL as an unreliable setup for modern Web development where Linux or MacOS seem more robust and streamlined. I understand Microsoft's interest in making something like WSL, especially with new hardware offerings such as the Surface Book 2 competing directly with Macbook Pros. They want to target professional users who use their laptops as their main work tool, but there doesn't seem to be enough focus going into making WSL attractive/trustworthy enough with issues such as this persisting almost 2.5 months after being reported.
How can I, as a professional, justify purchasing Microsoft products when I can't trust them to properly support them in a timely manner?
Sorry for the rant. I really want my next laptop to be a Surface Book 2, but it is not looking very likely.

The rants might seem harsh, but maybe to reiterate the impact of this issue:
Right now it is not possible to work on any nodejs, webpack, etc. project since both npm and yarn fail to install. The workaround is very painful and costs too much time because it needs to be done on each dependency change or adjustment.
I'm actually quite pessimistic, there were no WSL updates between Creator's Update and Fall Creator's Update for users of the stable Windows version as far as I can remember, therefore it is somewhat sad to have an absolutely broken WSL for node users, especially with the big fanfare of blog posts announcing that WSL would no longer be beta?

The above couldn't explain the situation any better. I had been tempted to write something similar but wasn't sure I could contain my anger and frustration in the process.
The amount of time (AND MONEY) I've lost the last 3 weeks trying to work around this bug has made me incredibly bitter after spending hours writing guides, resources, tutorials, etc. talking up WSL.

I have the #1 result on Google for a majority of the keywords revolving around setting up development with Windows and it makes me incredibly tempted to just edit my post and tell people to stay the hell away.
If Microsoft can't take this seriously, I'm afraid I can't take them seriously either.

I had been developing with WSL since January 2017. This issue forced me to install and dual boot with Ubuntu. I managed to fix the issue on my personal laptop but the issue persisted on my main work laptop. It will be a hard sell for me to go back to developing on Windows after this issue.

I should note that for many npm workflows, including the majority of webpack setups, you can simply use Windows yarn or npm, and that it's possible to alias them such that you don't even need to change your workflow.
That said https://blogs.msdn.microsoft.com/commandline/2017/07/28/windows-subsystem-for-linux-out-of-beta/ is pretty ironic 😓

@simonbuchan

I should note that for many npm workflows, including the majority of webpack setups, you can simply use Windows yarn or npm, and that it's possible to alias them such that you don't even need to change your workflow.

Working with 2 filesystems at the same time is already hacky enough to be working with two redundant binaries for each OS simultaneously as well. Which to use when and how? I would rather just have everything inside the Linux context and have it work 100%. That should be the goal.

@simonbuchan That may work ok for some people, but be warned that it doesn't play nice with native modules, binary/binstub formats, and packages that make use of inotify (or anything else that requires OS checks at install time).
The other workaround to have node_modules reside on the WSL filesystem is probably better, but that obviously breaks any Windows tooling (e.g. VS Code intellisense).

I must say, my Vim skills have greatly increased due to this issue exclusively.
Being this issue has arisen from Yarn , its probably safe to assume the people most pained from this issue are ReactJS developers (and some Angular). This issue has really empowered the "nay-windows sayers" in my workplace when they argue "you cannot develop javascript on windows, in the same way you cannot really develop .NET applications without windows".
I'm a big advocate from win10 and personally feel the new direction and innovations from Microsoft should be both acknowledged and enjoyed because really, its just a great OS!
Please take this as a strong use case to improve the release methodology for WSL or we'll loose the opportunity to enjoy it as an option in our environment.

Apparently my Surface Pro 4 has updated itself overnight because now I have the same issue. It's sad that this issue was surfaced 2.5 months ago and it still is hitting new people.

Hi all. I've been pinged several times over the last 48 hours for an update on the fix for this issue.
Know that we appreciate and understand the enthusiasm for the fix for this issue, but we do ask for your patience as the fix makes its way up through our build and test systems, on its way to the Insider rings.
As @SvenGroot stated above, the fix has been checked in but it didn't make it up to the Insider release branch in time for 17025 which was released on 11/1. It's v. likely it'll arrive in the next Insider build.
Sven is also working to backport this fix to Fall Creators Update (FCU), but since this isn't a fix for a major security exploit, it'll make its way through our normal servicing channels, passing through numerous review and testing gates before it's formally released in an up-coming servicing release.
Please note...
While Microsoft is much more agile today than ever before (we now essentially ship Windows every week) there are still processes that churn behind the scenes to ensure that we catch as many bugs as we can before they're released, and that fixes are tested & released in an organized manner.
Only fixes for the most high-risk, high-impact issues bypass these standard processes, but these exceptional fixes are themselves placed under the most exacting scrutiny possible, requiring HUGE deployment of humanpower & tooling to quadruple-check that the fix is good before its released. We reserve these rapid fix deployments only for the most important fixes for the most critical of issues, and while annoying, this fix does not qualify as 'exceptional'.
No software is ever perfect or bug free, and when you're delivering software used by more than a billion people every day, one has to take whatever steps possible to ensure the best outcome for the largest audience. The last thing we'd want is to release a fix that doesn't resolve the issue, and that may even make things worse.
So, please bear with us while we process this fix through our release processes.
Thanks.

We appreciate the pain some of you are feeling because of this issue. Please believe me: we take this very seriously and have been working very hard to get the fix to you as soon as possible.
In the mean time, the following workaround should get around this issue. When starting bash, run the following commands:
sudo umount /mnt/x
sudo mount -t drvfs -o noatime,fallback=1 X: /mnt/x
Replace /mnt/x and X: with the mount point and drive letter for any affected drives. If you've done this correctly, you can run mount and you'll see a line like this:
C: on /mnt/c type drvfs (rw,noatime,fallback=1)
If the fallback option is shown, it has been mounted correctly. We believe that doing this will allow you to use the drvfs mount without hitting this issue.
You'll have to do this every time you start a new WSL instance (so every time you open bash after all bash windows were closed).
Note! Doing this will disable all the performance improvements we've implemented since RS1 (version 1607, the Anniversary Update). Don't use this workaround unless you're hitting this issue.
I'll update once the fix is released, at which point I strongly recommend you stop using this workaround.

@SvenGroot you are our savior, thank you!
I've added the workaround to my ~/.bashrc and it seems to work:
# Workaround for issue: https://github.com/Microsoft/WSL/issues/2448
if ! mount | grep -q "C: on /mnt/c type drvfs (rw,noatime,fallback=1)"; then
        echo "== Remount of C: drive required =="
        pushd ~ > /dev/null
        sudo umount /mnt/c
        sudo mount -t drvfs -o noatime,fallback=1 C: /mnt/c
        popd > /dev/null
fi

Thanks for this fix.  Just to confirm my understanding of when this fix is necessary (for usage with Yarn), it's only necessary when performing certain functionality of Yarn? Like when creating and updating dependencies?
I've wrapped the above code within a prompt so that my WSL is not always crippled back to version 1607.

Workaround bei @Melatonin64 works fine as well as the workaround by @khuongduybui (symlink outside /mnt). Quick bugfix would be appreciated though! Thanks for the support here @ wsl team!

Thanks a lot for the workaround, that will definitely tide me over until the fix is available.
@JimW
I think it will depend on what you're specifically doing, but anecdotally/personally I haven't run into the issue (yet) outside yarn install/upgrade. The rest of my day-to-day workflow works fine on the new version, so I won't be using the workaround the vast majority of the time. So yeah, it sounds like you have the right idea.

I'm really very sad i meet the same problem today.When i use create-react-app then this problem appear.Hope mircrosoft fix this bug soon.....
sad

@imgwho in latest insider release I have not observed the issue, using yarn 1.x, but there are other workarounds, especially https://github.com/Microsoft/WSL/issues/2448#issuecomment-342254181, that could help.

@imgwho, create-react-app will successfully complete with the above workaround code, using the latest regular "Outsider" Windows.

@khuongduybui  thx ~~ i'll try

@JimW  oh  i update the create-react-app to 1.4.3 then i found the problem sloved ,, thx~~~

@imgwho and whoever else it might help, there's yarn's built-in yarn create react-app myapp, meaning you no longer need the independent create-react-app package...

This bug should be fixed in Insider build 17035, which was just released. Please stop using the workaround posted above, and let us know if you still encounter any issues.

Will an update for this be possible to push to non-insider or are those of us not on insider effectively screwed this update?

@hikurangi  i'm Fall Creator's Update (build 16299.19) use WSL on Ubuntu 16.04.3 LTS ,i used use npm to install yarn and then i use apt-get to install yarn
yarn official website
Debian/Ubuntu Linux

On Debian or Ubuntu Linux, you can install Yarn via our Debian package repository. You will first need to configure the repository:

curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
On Ubuntu 16.04 or below and Debian Stable, you will also need to configure the NodeSource repository to get a new enough version of Node.js.

Then you can simply:

sudo apt-get update && sudo apt-get install yarn
Note: Ubuntu 17.04 comes with cmdtest installed by default. If you’re getting errors from installing yarn, you may want to run sudo apt remove cmdtest first. Refer to this for more information.

and then i found..  oops....
wuv@wuv:/mnt/e/practice/react$ yarn create react-app app
yarn create v1.3.2
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed<EMAIL_ADDRESS>with binaries:
      - create-react-app
[##############################################################################] 107/107 Creating a new React app in /mnt/e/practice/react/app.

Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts...

yarn add v1.3.2
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
error An unexpected error occurred: "EINVAL: invalid argument, lstat '/mnt/e/practice/react/app/node_modules/acorn-jsx/index.js'".
info If you think this is a bug, please open a bug report with the information provided in "/mnt/e/practice/react/app/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

Aborting installation.
  yarnpkg add --exact react react-dom react-scripts --cwd /mnt/e/practice/react/app has failed.

Deleting generated file... node_modules
Deleting generated file... package.json
Deleting generated file... yarn-error.log
Deleting app / from /mnt/e/practice/react
Done.
error Command failed.
Exit code: 1

so i think i should just waiting the 17035 come...

@Log1x As we've pointed out before, a fix for the Fall Creator's Update will be coming soon. Please be patient, and continue to use the workaround I posted above in the mean time. I will update here once the fix has been released.

The fix was in 17035 so all current Insiders builds should no longer have this issue.

@orenfromberg @peterjuras @Log1x and anyone else reporting this issue - can you please upgrade to Insiders fast-ring build 17035 (or later) - or install a VM running this build - and let us know if your workflow is now fixed & unblocked?
TIA.

hello,
The last insider build fixed the issue on my machine.  Below is my environment:
Yarn: v1.3.2
Node.js: v6.9.5, v8.6.0
Insider Build Preview OS Build:  17035.1000
Insider Build Preview Version:    1709

sneakily ran npm install works as expected however it just made the office internet choked up a little bit but all good.
thanks for all your hard work!

After updating the issue seems to be fixed for me!

Great, thanks for testing and sharing your results. We (i.e. @svengroot ;)) continue to backport the fix through our release machinery.

@bitcrazed @SvenGroot Thanks so much for your work on this. As developers, we can all appreciate how tricky these things can be to solve and the effort required to backport a fix.
Is there currently an ETA on this? And if not, an approximation - one week, a month?

@bitcrazed @SvenGroot Please, tell me, in what not insider build will this bug be fixed?

At one point in the day-and-a-half long cross-compiled on eight processors on a 16GB machine, I received:
x86_64-w64-mingw32-gcc: command not found
Once, and once only. Restarting the make process got past this point.
The "x86_64-w64-mingw32-gcc" is my cross compiler, as found by many, many thousands of other make processes in this long compilation. Why it should disappear for one, and only one, call among the galaxy of other calls, I don't know.
I also received two "fork: invalid argument" notices. Again, restarting the make process recovered from this. This might be #2469 again.
So, this is much, much more reliable. But the "command not found" is a mystery.

@RinatMullayanov - we'll let you know once the fix bubbles up into the servicing release mechanisms.

@Warblefly - wow - 36 hour compile??? ;) Have asked the team to take a look at #2469 which is similar to the issue you describe - please follow/contribute there.

I wish I didn't have to connect Microsoft Account with my installation of Windows in order to participate in Windows Insider. I could really use this fix ASAP, not whenever this is scheduled to go out to non-Insiders. :-(

You can download an ISO

Or you can download a Linux ISO while you’re at it. I know I did, and the console works significanlty faster, by the way. Still boot to Windows, but not at work. It’s a shame; miss it a lot.
Seriously folks, I don’t want to sound bitter, but people got other things to do than downloading ISOs or installing insider builds. I know they’re pretty stable, but still.
I know the WSL team probably has very little influence on the release cycle, but I think those who have should reconsider the criticality of the fix. You risk losing people, people.

I'm having the same issue when trying to use yarn. It is blocking my environment. I might need to change OSes or use docker just because of this :s

@bitcrazed @SvenGroot any reason you guys don't use the Release Preview ring for stuff like that? Seems ideal to me.

@TomasHubelbauer The reason we ask you to primarily get your distros from the store is that this allows distro vendors to patch and service their releases, ensuring that when you install a distro, you're always installing the latest supported version. This requires that you sign-in with your MSA, so that we know to push updates to your machines when they're published.
@hoichi The distros that you download and install manually are identical to the distros you install via the Store so there'll be no perf differential between the two.
@Stanzilla Let's just say that the Windows servicing release mechanism is complex, for good reasons ;)

The fix for the Fall Creator's Update should be coming very soon. We can't comment on the timeline, because the patch could be delayed for any number of reasons beyond our control. In the meantime, the workaround posted above should prevent any issues.
We appreciate your patience and understanding.

@SvenGroot
I'm on build 16299.64 . Is this issue related to #2464 ? Will that be fixed in the incoming backport patch?

@nutcasev15  - #2464 went off the reserve because it started as what looked like as a LxFs problem and then someone posted a DrvFs problem in the same thread. The original LxFs problem is still in an indeterminate "needs repro" state. I compile huge GCC builds on LxFs regularly without EINVAL issues so there is no way to tell what is going on over there or whether it is "related". The 17035 release notes for this issue say DrvFs, and I'd take that at face value.

Good news, everyone!
The November 30th, 2017 Cumulative Update (KB4051963) for the Fall Creator's Update contains the fix for this issue. Please install this update, and let us know if you encounter any further issues.
To verify if you have installed the update, your OS build number should be 16299.98 or later.

The update requires a computer reboot, but afterwards it works for me.

A quick summary of #2712: the files that intermittently go missing are simply "not found". This isn't an EINVAL error. Not sure if it's exactly related to #2448.

Works for me too, no issues anymore

after applying the update, the error is no more.
but - was this always so slow? create-react-app test takes over 62 seconds in bash compared to 16 seconds in cmd on a decent i7 4.2Ghz workstation.

Yeah, I hadn't used WSL for months. Trying it now and adding packages using yarn is incredibly slow for my project. I usually work on it on my dual booted Ubuntu install and it is definitely quicker there.

@rhyek @mindhaq Disk IO perf is a well known WSL issue that Sven is working with the storage team to address in future WSL releases.
However, while WSL disk perf is slower right now, it should work correctly. Can you confirm?

@bitcrazed Yes, everything is functional.

Great thanks.
Closing for now since we have a few confirmations that the issue appears to be resolved.

@bitcrazed Apart from slow IO it is working fine now, thank you!
It's good to hear that disk perf is being addressed. Is there an Issue to follow on?

Thanks for letting us know.
The larger disk perf issue is primarily being tracked in issue #873

I upgrade my OS to newest insider preview(17025.10000)，still have this problem

newest insider preview(17025.10000)

this

I am using Windows version 1803, build 17134.112 and still encountering this bug.

@Nadav-Ruskin  NPM 6.0 is recommended, It is no worse than yarn now

That's not really a fair answer, @muyu66. First, it's not true that npm@6 matches Yarn in terms of functionality. More importantly, WSL is not meant to be limited to a subset of tools, and you can't expect development teams to drop Yarn because none is "recommended".

Sorry if I haven't made myself clear: The error I'm experiencing is more related to #2606, that is, I can't build (my own projects) using make -j<anything larger than 1>. I've posted about it here because this thread contains the workaround and claims that the issue has been fixed.
I'll make a new issue to avoid further confusion.

@tomitrescak what build? (Win+R -> type winver)
Your OS build number should be 16299.98 or later to get this fix.

Ah, ok, I got 16299.64, installing update now.


[Bug]: Extended enum exported multiple times produces build issues

Package name
schematics
Package version
9.3.5
Reproduction steps
Override an existing model enum using allOf in the spec
allOf:
- $ref: '#/definitions/_MyEnumModel'
- type: object
discriminator: xxx
properties:
xxxType:
type: string
description: >
description
enum:
- Value1
- Value2
- Value3
Current result
Enum files generated are having conflicts between each other (between the initial Enum and the extended Enum the the exports level) while trying to build the ts files from the specs.
Error is : MyEnum is exported multiple times
Expected result
Green build
Additional comments
No response

swagger spec to reproduce the issue
swagger: '2.0'
info:
  version: ''
  title: ''
paths: {}
definitions:
  _BaseModel:
    type: object
    required:
      - enumField
    properties:
      id:
        type: string
      enumField:
        type: string
        enum:
          - AAA
          - BBB
          - CCC
  'Model':
    type: object
    discriminator: enumField
    allOf:
      - $ref: '#/definitions/_BaseModel'
      - type: object
        discriminator: enumField
        required:
          - enumField
        properties:
          enumField:
            type: string
            enum:
              - AAA
              - BBB

It seems that discriminator in the sub schema is not necessary as already present in the Model schema.
swagger: '2.0'
info:
  version: ''
  title: ''
paths: {}
definitions:
  _BaseModel:
    type: object
    required:
      - enumField
    properties:
      id:
        type: string
      enumField:
        type: string
        enum:
          - AAA
          - BBB
          - CCC
  'Model':
    type: object
    discriminator: enumField
    allOf:
      - $ref: '#/definitions/_BaseModel'
      - type: object
-        discriminator: enumField
        required:
          - enumField
        properties:
          enumField:
            type: string
            enum:
              - AAA
              - BBB

I also want to raise the point that this swagger is not valid.
Following the documentation of allOf

allOf validates the value against all the subschemas

Here _BaseModel schema does not validate the other subschema in the allOf


Missing IMWRITE_JPEG_SAMPLING_FACTOR constants

The list of missing constants:

IMWRITE_JPEG_SAMPLING_FACTOR
IMWRITE_JPEG_SAMPLING_FACTOR_411
IMWRITE_JPEG_SAMPLING_FACTOR_420
IMWRITE_JPEG_SAMPLING_FACTOR_422
IMWRITE_JPEG_SAMPLING_FACTOR_440
IMWRITE_JPEG_SAMPLING_FACTOR_444

This makes it impossible to change sampling factor from the default 4:2:0 to turn off chroma down-sampling for example.

For now, you can define them in your code and use them directly. Constant values are just numbers.
Alternatively, open a PR if you want to share those constants with the community.


 (81, 19): parse expected comma after load's type

Reporting a bug
Im getting an error like pasted below while trying to run the most basic example taken from official WWW:
https://developer.nvidia.com/blog/numba-python-cuda-acceleration/
import numpy as np
from numba import vectorize

@vectorize(['float32(float32, float32)'], target='cuda')
def Add(a, b):
  return a + b

N = 100000
A = np.ones(N, dtype=np.float32)
B = np.ones(A.shape, dtype=A.dtype)
C = np.empty_like(A, dtype=A.dtype)

C = Add(A, B)

Ubuntu 18.04.5, Numpy 1.19.4, Numba 0.52.0, kernel 5.4.58-050458-generic, CUDA 11.2.0, NVIDIA driver 460.27.04, GeForce GTX 1660

Traceback (most recent call last):
File "GPUtest.py", line 13, in
C = Add(A, B)
File "/usr/local/lib/python3.6/dist-packages/numba/cuda/dispatcher.py", line 37, in call
return CUDAUFuncMechanism.call(self.functions, args, kws)
File "/usr/local/lib/python3.6/dist-packages/numba/np/ufunc/deviceufunc.py", line 300, in call
cr.launch(func, shape[0], stream, devarys)
File "/usr/local/lib/python3.6/dist-packages/numba/cuda/dispatcher.py", line 148, in launch
func.forall(count, stream=stream)(*args)
File "/usr/local/lib/python3.6/dist-packages/numba/cuda/compiler.py", line 372, in call
kernel = self.kernel.specialize(*args)
File "/usr/local/lib/python3.6/dist-packages/numba/cuda/compiler.py", line 899, in specialize
self._bind, targetoptions)
File "/usr/local/lib/python3.6/dist-packages/numba/cuda/compiler.py", line 811, in init
self.compile(sigs[0])
File "/usr/local/lib/python3.6/dist-packages/numba/cuda/compiler.py", line 952, in compile
kernel.bind()
File "/usr/local/lib/python3.6/dist-packages/numba/cuda/compiler.py", line 576, in bind
self._func.get()
File "/usr/local/lib/python3.6/dist-packages/numba/cuda/compiler.py", line 446, in get
ptx = self.ptx.get()
File "/usr/local/lib/python3.6/dist-packages/numba/cuda/compiler.py", line 416, in get
**self._extra_options)
File "/usr/local/lib/python3.6/dist-packages/numba/cuda/cudadrv/nvvm.py", line 548, in llvm_to_ptx
ptx = cu.compile(**opts)
File "/usr/local/lib/python3.6/dist-packages/numba/cuda/cudadrv/nvvm.py", line 236, in compile
self._try_error(err, 'Failed to compile\n')
File "/usr/local/lib/python3.6/dist-packages/numba/cuda/cudadrv/nvvm.py", line 254, in _try_error
self.driver.check_error(err, "%s\n%s" % (msg, self.get_log()))
File "/usr/local/lib/python3.6/dist-packages/numba/cuda/cudadrv/nvvm.py", line 144, in check_error
raise exc
numba.cuda.cudadrv.error.NvvmError: Failed to compile
 (81, 19): parse expected comma after load's type
NVVM_ERROR_COMPILATION

Is some default behavior changed and broke the decorator?

I am facing the same issue on Windows 10, with:

GTX 1050 Ti
Nvidia Driver Version 460.89
cuda_11.2.0_460.89_win10
numba==0.52.0
llvmlite==0.35.0

I am facing the same issue on Windows 10, with:

GTX 1050 Ti
Nvidia Driver Version 460.89
cuda_11.2.0_460.89_win10
numba==0.52.0
llvmlite==0.35.0

@AlyShmahell Have you tried to downgrade CUDA?

@AlyShmahell Have you tried to downgrade CUDA?

@AlexKurek thank you for reporting this. It will need some investigation to figure out what is going on here.

@AlexKurek thank you for reporting this. It will need some investigation to figure out what is going on here.

CUDA 11.2 isn't currently supported by Numba. Downgrading should let it work.

CUDA 11.2 isn't currently supported by Numba. Downgrading should let it work.

@stuartarchibald What is the latest CUDA we can use currently?

@stuartarchibald What is the latest CUDA we can use currently?

@stuartarchibald What is the latest CUDA we can use currently?

@AlexKurek I think it's anything supported and <11.2, so 11.1.x would be the last compatible. We are aware of the issues and there's work ongoing to provide 11.2+ support.

@stuartarchibald What is the latest CUDA we can use currently?

@AlexKurek I think it's anything supported and <11.2, so 11.1.x would be the last compatible. We are aware of the issues and there's work ongoing to provide 11.2+ support.

@AlexKurek yes it worked after downgrading to the following:

cuda version 10.1
llvmlite==0.31
numba==0.48

@AlexKurek yes it worked after downgrading to the following:

cuda version 10.1
llvmlite==0.31
numba==0.48

I experienced this issue with CUDA 11.6. The issue was resolved by using cuda 11.1 instead.


Working directory of shell scripts should be the job workspace dir

Description:
Currently, the shell scripts set the TESTGRID_HOME as the working directory. This is an issue since the shell scripts of testgrid jobs such as infra-provision.sh will look for artifacts under the TESTGRID_HOME then.
For example, the local-is-deployment looks for the wso2is-5.4.0.zip distribution under TESTGRID_HOME!
https://github.com/wso2/testgrid/blob/e86b2f1a05ad523f585711f6dbd27bb6327ec3ba/test-scripts/local-is-deployment/Deployment/deploy.sh#L35
We set the working dir at this location:
https://github.com/wso2/testgrid/blob/e86b2f1a05ad523f585711f6dbd27bb6327ec3ba/deployment/src/main/java/org/wso2/testgrid/deployment/deployers/ShellDeployer.java#L52
Affected Product Version:
0.9.0-m12
OS, DB, other environment details and versions:
N/A
Steps to reproduce:
See above.
Related Issues:
N/A

@DarthFloopy Apologies for missing your comment.
The issue is fixed now. Hence closing.