Error publishing simple DLL on .NET Core 3.1

Steps to reproduce:

Create simple Class library project targeted for .NET Core 3.1
Add the latest DllExport package via NuGet (configure via #175 at the time of writing this)
Build the project (successful)
Try to publish the project for either combination of platforms and you get the error

DllExport version: v<IP_ADDRESS>831+9a4bc51
Used Visual Studio 2019 v16.8.2
Target platform: x86
Runtime identifier: win-x86

Information from VS Output log:
Build started...
1>------ Build started: Project: DllExportTest, Configuration: Release x86 ------
1>DllExportTest -> [...]\DllExportTest\bin\x86\Release\netcoreapp3.1\win-x86\DllExportTest.dll
2>------ Publish started: Project: DllExportTest, Configuration: Release x86 ------
2>Determining projects to restore...
2>Restored [...]\DllExportTest\DllExportTest.csproj (in 291 ms).
2>DllExportTest -> [...]\DllExportTest\bin\x86\Release\netcoreapp3.1\win-x86\DllExportTest.dll
2>The file '[...]\DllExportTest\bin\x86\Release\netcoreapp3.1\win-x86\DllExportTest.pdb' to be packed was not found on disk.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========

Project builds without any issue but publish fails every time, tried also changing parameters with no luck.
Demo Project files:
DllExportTest.zip
Thanks for help! ✌

Thanks for the report!
Temporarily try the following (netstandard & netcoreapp targets only)
    <DebugType>embedded</DebugType>
    <DebugSymbols>true</DebugSymbols>

or
    <DebugType>none</DebugType>
    <DebugSymbols>false</DebugSymbols>

or related settings in project properties using VS IDE

Thanks for the temp solution, seems that if you set DebugSymbols to true, you don't need to specify the DebugType element.
On the other hand, when DebugSymbols are set to false or not present, you have to specify the DebugType.
Now the publishing works, but even with library OutputType, I keep getting .nupkg file as a result of publishing instead of .dll file and all the references. But I suspect that's another problem not related to this.

Make sure CopyLocalLockFileAssemblies property is not a true.
If only some specific, then below:

Element
attr/tag=value

PackageReference
ExcludeAssets="runtime" (ie. only at build time)

ProjectReference
Private="False"

Reference
Private="False"

To disable generation of the NuGet packages try the following below;
When Publish
<IsPackable>False</IsPackable>

When Build
<GeneratePackageOnBuild>False</GeneratePackageOnBuild>

You can also use https://github.com/3F/vsSolutionBuildEvent for other custom scripts (public/private) and much more besides or together with msbuild

IsPackable switch indeed disabled the generation of the NuGet package but now nothing gets published, not a single file :-/

Unfortunately there is no unified solution at this day.
'embedded' for some reason or 'none' ...  I don't want either implement some option for this case or forcefully remove pdb
Because first of all we need to review this issue https://github.com/3F/coreclr/issues/3
Keep it open for the future fixes!
I remind everyone,

This affects only .NET Core based projects.
Temp solution is https://github.com/3F/DllExport/issues/176#issuecomment-740658460

Thanks

IsPackable switch indeed disabled the generation of the NuGet package but now nothing gets published, not a single file :-/

Strange, it must generate a modified assembly. This however is another issue. Please open it as question if you want to discuss some solution.

I had similar problem. Winforms targeting 3.1 Single File option would not publish but would it would with Single File un checked.
Tried the solution
embedded
true
Resulted in whole project being unloaded! Coud not re-load until I removed the above.

I had similar problem. Winforms targeting 3.1 Single File option would not publish but would it would with Single File un checked.
Tried the solution
embedded
true
Resulted in whole project being unloaded! Coud not re-load until I removed the above.

Resulted in whole project being unloaded! Coud not re-load until I removed the above.

@cabbytech msbuild properties must be declared into PropertyGroup nodes. Did you? You can simply add a new one into parent Project node or use any available.
Also I remind this can be configured inside Visual Studio IDE using project properties menu - Build - Advanced

Resulted in whole project being unloaded! Coud not re-load until I removed the above.

@cabbytech msbuild properties must be declared into PropertyGroup nodes. Did you? You can simply add a new one into parent Project node or use any available.
Also I remind this can be configured inside Visual Studio IDE using project properties menu - Build - Advanced

Sorry my mistake. I have corrected. However, will not publish with that setting either.

Sorry my mistake. I have corrected. However, will not publish with that setting either.

Nothing of value in the log file but output window:
  System.ArgumentException: Invalid input specification: Found multiple entries with the same BundleRelativePath

Nothing of value in the log file but output window:
  System.ArgumentException: Invalid input specification: Found multiple entries with the same BundleRelativePath

@cabbytech It's unclear at all. Please use /v:diag or better /bl. Note the /bl by default collects the source text of project files. See Doc

@cabbytech It's unclear at all. Please use /v:diag or better /bl. Note the /bl by default collects the source text of project files. See Doc

Is this closed by now?

Okay, I finally looked into this issue.
Although I can't reproduce your problem for missing a .pdb,

2>The file '[...]\DllExportTest\bin\x86\Release\netcoreapp3.1\win-x86\DllExportTest.pdb' to be packed was not found on disk

56d4479b405a6f36ae43de9991bcbcbdcc improves deletion via temp renaming.
However, this is not the general point of the current issue;
Found this in your FolderProfile.pubxml
<SelfContained>true</SelfContained>

Current project does not officially support publishing of the self-contained a platform-specific executable.
Also
<PublishSingleFile>True</PublishSingleFile>

You can use ILMerge (or similar) at Pre-Procesing stage to combine modules if you're looking option for a single file, moreover for libraries (because this option only for executable app as far as I remember it)
So I checked your DllExportTest.zip (thank you for the prepared example!) on VS 17.12.1 publishing is ok even for much older DllExport 1.7.3 (your configured project)
1>------ Build started: Project: DllExportTest, Configuration: Release x86 ------
Restored D:\prg\issues\DllExport\_github\176\DllExportTest\DllExportTest.csproj (in 28 ms).
1>DllExportTest -> D:\prg\issues\DllExport\_github\176\DllExportTest\bin\x86\Release\netcoreapp3.1\win-x86\DllExportTest.dll
2>------ Publish started: Project: DllExportTest, Configuration: Release x86 ------
2>DllExportTest -> D:\prg\issues\DllExport\_github\176\DllExportTest\bin\x86\Release\netcoreapp3.1\win-x86\DllExportTest.dll
2>DllExportTest -> D:\prg\issues\DllExport\_github\176\DllExportTest\bin\x86\Release\netcoreapp3.1\win-x86\publish\
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

But the publish will receive an original unmodified module that's different issue #235, but this is already fixed since 2a8d962ce2660cf4ec334f712b331fc0245ac3eb
You can test related CI build until new release
tl;dr

SelfContained=true is not a bug, we just do not support it.
For a PublishSingleFile you can use DllExport's Pre-Procesing, for example, together with pre-configured ILMerge or something else.

I close the issue but please open it again if the solution above does not help. Thanks.


FORCE.COM IDE 2

can you provide the link to download Force.com IDE 2. Is it released or yet to be released?

You can only get access if your are in the pilot.
Sign up here http://go.pardot.com/l/27572/2017-01-23/6gh89x
It says closed but I think we are still taking pilot participants.


Standardizing module name and paths. Fixes #33

Changed from 'jekyll-plus' and Jekyllplus to :jekyll_plus and JekyllPlus
@e2 how do you feel about this?

Looks fine.
The gem name doesn't match, but that shouldn't be an issue with Guard.
I'll need #32 merged into master before I test this though (mostly since I want to add tests).
No rush with this - I have stuff to do as well.

@e2 I've updated this PR to be a module rename on the current master. Tests are passing, do you see any issues or shall I merge it.

Merge it to master. If if works from master, it's fine. If it doesn't or it's preventing a release - mention me in the issue and I'll check it out and create a PR as necessary.
This requires a bit of work to do properly, which means it won't happen soon - so let me know if you're blocked by this (e.g. if guard init doesn't work or doesn't work properly) and I'll create a quickfix.
Just to give you a sense of all the scenario I'd have to test for every plugin:
https://github.com/guard/guard-compat/issues/1

Ok thanks for your help!


Accessing the chartInstance for any processing purposes

How can I access the canvas or the chartInstance for any external purposes like saving it as png etc ? If I have the instance, I can call .toBase64Image() to get an image out of it.
Great work btw!.

Hi @TheCelebrimbor and thanks !
It should be already possible using template refs.
<template>
  <Bar ref='barChartRef'/>
</template>

<script>
   export default {
       mounted() {
             this.$refs.barChartRef.chartInstance.toBase64Image()
       }
   }
</script>

Keep me updated :)

I will add a section in the README for it!

@victorgarciaesgi Thanks for the quick reply.! I was able to access the canvasRef but not the chartInstance. It is null.
I am accessing the ref after all rendering is done with a custom save button.

Hum maybe it's because the chartInstance is not reactive. I will try something and keep you updated!

@TheCelebrimbor Can you try v0.2.3?
Are you on vue 2, because somewhat making chartInstance reactive doesn't seem to work on Vue 3 :(

@victorgarciaesgi I just updated to 0.2.3. It seems to break the whole thing. Now I get a new error whenever I interact with anything in the view containing the charts.
This even causes a stack overflow

Full Error:
runtime-core.esm-bundler.js:38 [Vue warn]: Unhandled error during execution of watcher callback    at <Bar ref="chartRef" data= {datasets: Array(1), labels: Array(4)}datasets: [{…}]labels: (4) ["Windows", "Linux", "Mac", "Unix"]__proto__: Object >    at <VsCard content="" fitContent="" >    at <Chart class="block-content" data= {componentName: "Chart.vue", h: "440px", w: "400px", title: "Computers by Platform", id: "chart-computers-by-platform", …} >    at <AsyncComponentWrapper class="block-content" data= {componentName: "Chart.vue", h: "440px", w: "400px", title: "Computers by Platform", id: "chart-computers-by-platform", …} >    at <Dashboard elements= (2) [{…}, {…}] id="computer-summary-dashboard" rows=1  ... >    at <Summary onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< Proxy {$vs: Proxy, …} > >    at <BaseTransition mode="out-in" appear=false persisted=false  ... >    at <Transition name="fade" mode="out-in" >    at <RouterView>    at <Admin onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< Proxy {$vs: Proxy, …} > >    at <RouterView>    at <App> warn @ runtime-core.esm-bundler.js:38 logError @ runtime-core.esm-bundler.js:211 handleError @ runtime-core.esm-bundler.js:203 callWithErrorHandling @ runtime-core.esm-bundler.js:157 callWithAsyncErrorHandling @ runtime-core.esm-bundler.js:163 job @ runtime-core.esm-bundler.js:2077 flushPreFlushCbs @ runtime-core.esm-bundler.js:328 flushJobs @ runtime-core.esm-bundler.js:368 Promise.then (async) queueFlush @ runtime-core.esm-bundler.js:286 queueCb @ runtime-core.esm-bundler.js:308 queuePreFlushCb @ runtime-core.esm-bundler.js:311 scheduler @ runtime-core.esm-bundler.js:2105 run @ reactivity.esm-bundler.js:183 trigger @ reactivity.esm-bundler.js:189 set value @ reactivity.esm-bundler.js:730 show @ vuesax3.common.js:57048 toggle @ vuesax3.common.js:57052 callWithErrorHandling @ runtime-core.esm-bundler.js:154 callWithAsyncErrorHandling @ runtime-core.esm-bundler.js:163 invoker @ runtime-dom.esm-bundler.js:308 helpers.segment.js:1795 Uncaught (in promise) RangeError: Maximum call stack size exceeded     at _resolveWithPrefixes (helpers.segment.js:1795)     at helpers.segment.js:1603     at _cached (helpers.segment.js:1685)     at Object.get (helpers.segment.js:1602)     at _resolveWithContext (helpers.segment.js:1693)     at helpers.segment.js:1645     at _cached (helpers.segment.js:1685)     at Object.get (helpers.segment.js:1644)     at toRaw (reactivity.esm-bundler.js:698)     at toRaw (reactivity.esm-bundler.js:698) Promise.then (async) queueFlush @ runtime-core.esm-bundler.js:286 queueCb @ runtime-core.esm-bundler.js:308 queuePreFlushCb @ runtime-core.esm-bundler.js:311 scheduler @ runtime-core.esm-bundler.js:2105 run @ reactivity.esm-bundler.js:183 trigger @ reactivity.esm-bundler.js:189 set value @ reactivity.esm-bundler.js:730 show @ vuesax3.common.js:57048 toggle @ vuesax3.common.js:57052 callWithErrorHandling @ runtime-core.esm-bundler.js:154 callWithAsyncErrorHandling @ runtime-core.esm-bundler.js:163 invoker @ runtime-dom.esm-bundler.js:308 chart.esm.js:5872 Uncaught TypeError: Cannot read property 'includes' of undefined     at eventFilter (chart.esm.js:5872)     at Array.filter (<anonymous>)     at PluginService.notify (chart.esm.js:4776)     at Chart.notifyPlugins (chart.esm.js:5854)     at Chart._eventHandler (chart.esm.js:5873)     at listener (chart.esm.js:5759)     at Chart.event (chart.esm.js:3092)     at helpers.segment.js:28 eventFilter @ chart.esm.js:5872 notify @ chart.esm.js:4776 notifyPlugins @ chart.esm.js:5854 _eventHandler @ chart.esm.js:5873 listener @ chart.esm.js:5759 event @ chart.esm.js:3092 (anonymous) @ helpers.segment.js:28 requestAnimationFrame (async) (anonymous) @ helpers.segment.js:26 chart.esm.js:5872 Uncaught TypeError: Cannot read property 'includes' of undefined     at eventFilter (chart.esm.js:5872)     at Array.filter (<anonymous>)     at PluginService.notify (chart.esm.js:4776)     at Chart.notifyPlugins (chart.esm.js:5854)     at Chart._eventHandler (chart.esm.js:5873)     at listener (chart.esm.js:5759)     at Chart.event (chart.esm.js:3092)     at helpers.segment.js:28 eventFilter @ chart.esm.js:5872 notify @ chart.esm.js:4776 notifyPlugins @ chart.esm.js:5854 _eventHandler @ chart.esm.js:5873 listener @ chart.esm.js:5759 event @ chart.esm.js:3092 (anonymous) @ helpers.segment.js:28 requestAnimationFrame (async) (anonymous) @ helpers.segment.js:26

For now, going back to 0.2.0 !!!

Yeah I need to put my head on it I don't have much time for now, reverting to current behaviour

It seems to not be as simple at wrapping it in ref in Vue3 :(

It would be a much needed thing tho. Maybe you can expose an event on the component and emit the chart with an event every time it updates. I can bind to it with a v-model and then It would be good.

Also another question, are you using Vue 3 with Vite.js or just via vue-cli and Webpack 5?

Oh!, super easy to miss because it is not in the readme. Will check it out asap.
I use Vue 3 with webpack 5.

You're right sorry I will specify them in the docs! :)

The bug seems to be coming from chartjs when chartInstance is reactive https://github.com/chartjs/Chart.js/issues/8970

@victorgarciaesgi If you can give a small example of accessing those events in Vue 3 it would be great as well.
I am currently doing this
<component @chart:render="newChartInstance($event)" ref="chartRef" :is="chartComponent" :data="internalData" />
The event never fires. Hmmm......

Never mind! Stoopid mistake :D. It works for now !! thank you so much

You're sure? Because for me the @chart:render is not firing either aha

I bound to chart:update like this
<component @chart:update="chartInstance = $event"
seems to work for me. :)

@TheCelebrimbor hmm what's the error for Pie ? :(

Oh you mean changing the type of the Chart dynamicaly? Maybe add a key to your dynamic component.
You're welcome thanks for reporting the bugs! :)

@TheCelebrimbor Just so you know, chartInstance is now accessible by ref, I managed to make it reactive :)


Only works with python3?

lmoments3 only imports successfully in Python3. Maybe mention in the README that standard_precip only works with Python3 (I had previously been using standard_precip in Python2).

Thanks for the comment. I updated the Readme file.


How to target a different board/FPGA than the examples?

In the documentation it says you can re-target the examples for any FPGA with enough room. I would like to target a ZCU111 RFSoC so I can insert the IP into a custom design. I believe I need to alter the "build.py" file but I'm not clear on which lines need to be altered and how to specify ZCU111 rather than the default ZCU104. Can you provide guidance?
Thank you

Is it enough that I just switch the part in the Vivado GUI and regenerate everything?

Hi, you should be able to change the part in Vivado after the fact, at least if the device is from the same family and the HLS-generated code is compatible.
To see which Boards you can select in the build.py, see https://github.com/Xilinx/finn/blob/dev/src/finn/util/basic.py
For an example of how to add support for new boards, you could refer to this PR: https://github.com/Xilinx/finn/pull/787


Morphologically complex clitics and clitic behavior in general

While there is a lot of ongoing discussion about what a "clitic" is, in most approaches it is defined along the lines of "grammatically independent, but phonologically bound". E.g. when using the notion of p-word and g-word, a clitic is its own g-word, but not its own p-word.
This implies that a clitic belongs to a lexeme of its own, in turn meaning that clitics can potentially have inflectional morphology of their own (or have morphologically complex stems). And we do find instances of this in "the wild"; the following Tiriyó example shows two multi-morpheme enclitics in a row: the morphologically complex stem hkao 'in water', followed by the inflected form nai of the stem a(i) 'to be':
paru=hka-o=n-ai     i-pata
P.=AQU-LOC=3Sa-COP  3-village
'He lives on the Paru river.' (Meira 1999: 393)

In uniparser, I can model the postposition and the copula as lexemes like this (ignoring their phonological dependence):
-lexeme
 lex: a
 stem: .a.//.ai.
 paradigm: cop
 trans_en: be
 gloss: COP

-lexeme
 lex: hkao
 stem: hk&ao.
 gloss: AQU&LOC
 trans_en: in water
 paradigm: zero
 gramm: aqu,loc

-paradigm: cop
 -flex: n.
  gramm: 3
  gloss: 3Sa

-paradigm: zero
 -flex: .
  gramm:

where the copula has a paradigm containing n-, and the postposition is morphologically complex (&). This yields expected hk-ao 'AQU-LOC' and n-ai '3Sa-COP'. The current implementation of clitics, however, does not allow for either of these functionalities, only accepting single-morpheme clitics like the following:
-clitic
 lex: po
 stem: po
 type: en
 gramm: loc
 gloss: LOC
 trans_en: LOC

I would love to be able to (in addition to the simple clitic definition above) also write things like:
-clitic
 lex: a
 stem: .a.//.ai.
 type: en
 paradigm: cop
 trans_en: be
 gloss: COP

-clitic
 lex: hkao
 stem: hk&ao
 type: en
 gloss: AQU&LOC
 trans_en: in water
 gramm: aqu,loc

Of course, most clitics are morphologically simple; for these cases the current functionality where no . has to be added to the stem and no (zero) paradigm has to be defined is perfectly suitable.
Judging from the uniparser input format for clitics and lexemes, as well as from the existence of placeholders for paradigms in the Clitic class (and much shared/duplicate code), clitics are already treated more like lexemes rather than like inflection. This leads to the question of whether it would make sense to make the Clitic class inherit from Lexeme? I don't understand enough of the inner workings of uniparser to figure this out, just a thought. I strongly suspect it's not that simple.
Maybe implementing only the second use case with & would be simpler? Judging from a discussion I started on the lingtyp mailing list, languages with morphologically complex clitics only have a few of them (e.g., Tiriyó does not have countless cliticized forms of the copula, and a restricted number of morphologically complex postpositions).

Thanks for your useful suggestions! What I implemented for now is & in clitics described inside clitics.txt and a custom separator for affixes (so you can have an "affix" separated by =). The details on that latter thing are here.
Regarding class inheritance: you are right, it would be not that simple. I mean, just making Clitic a subclass of Lexeme would be easy, but the hard part would be to describe that multiple-lexemes-in-one-token relationship in Wordform instances. I did something like that earlier with "subwords" , however this solution looks rather ugly.

Thank you! I've tried to implement the above Tiriyó example as follows:
clitics:
-clitic
 lex: a
 stem: n&a&i
 paradigm: cop
 trans_en: s/he is
 type: en
 gloss: 3&COP&UNCERT

lexemes:
-lexeme
 lex: paru
 stem: paru.
 gloss: P.
 trans_en: paru river
 paradigm: n
 gramm: N

paradigms:
-paradigm: cop
 -flex: n.
  gramm: 3
  gloss: 3Sa

-paradigm: n
 -flex: .hk|ao
  gramm: aqu,loc
  gloss: AQU|LOC
  sep: =
  trans_en: in water
 -flex: .
  gramm:

Output:
<Wordform object>
paruhkaonai
paru+a; N,aqu,loc
paru=hk-ao=nai
P.=AQU-LOC=3-COP-UNCERT
trans_en	s/he is

main issue: 3&COP&UNCERT is translated to 3-COP-UNCERT in the gloss, but n&a&i becomes nai, rather than n-a-i.
minor issue: the translation is overwritten by that of the clitic

I just noticed the superfluous paradigm today. Thanks for the fix -- I see that IDs now work, too!

I think my clitic needs are covered, thanks a bunch.


Quick search (CTRL+P) not working

Issue Type: Bug
After installation the quick search shortcut (CTRL+P) is not working anymore.
Extension version: 1.1.2
VS Code version: Code 1.67.0 (57fd6d0195bb9b9d1b49f6da5db789060795de47, 2022-05-04T12:06:02.889Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

Not using the extension anymore


Codec incompatible

These are typically directed to the google group.
server: Freeswitch 1.10.2
client A to B:
A:  Google Chrome broswer built with web: SIP.js
B: Bria Android 6.3.4 (a kind of  softphone client )
result:
"SIP/2.0 400 Bad Request
Via: SIP/2.0/WS <IP_ADDRESS>;branch=z9hG4bK9223993;received=<IP_ADDRESS>;rport=62509
Max-Forwards: 70
From: "1002" <sip:1002@<IP_ADDRESS>:5060>;tag=irjp8b21bu
To: <sip:1001@<IP_ADDRESS>:5060>;tag=FBgyjK4aKXyDB
Call-ID: vaipsfa18rcqsthq7fk8
CSeq: 874 INVITE
User-Agent: FreeSWITCH-mod_sofia/1.10.5-release.8~64bit
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer
Reason: Q.850;cause=88;text="INCOMPATIBLE_DESTINATION"
Content-Length: 0
Remote-Party-ID: "1001" <sip:1001@<IP_ADDRESS>>;party=calling;privacy=off;screen=no
"

If client A and client B are the same "Google Chrome broswer built with web sip.js" ,they can build a session successfully.
So i believe the reason of question  "400 Bad Request"   is that codecs of both clients are incompatible.
Can i set the codec of SIP.js ? or how solve this question  ?
Hope the anwser, Please help, Thanks much!

I checked my Bria account , it only support "G.711u" and "G.711a" .
Could codec of SIP.js support "G.711u" and "G.711a" ?

I checked my Bria account , it only support "G.711u" and "G.711a" .
Could codec of SIP.js support "G.711u" and "G.711a" ?

These are typically directed to the google group.

These are typically directed to the google group.


[fix][io] Config autoCommitEnabled when it disabled

Motivation
As the title. When autoCommit offset is turned off, the kafka thread still executes the commint offset operation behind the scenes.
Documentation

[x] doc-not-needed

rerun failure checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


prohibit read access of certain files in FDP_ACF_EXT.1

or in FPT_ACF_EXT.1.  This is to ensure that things which require confidentiality (e.g. audit logs) have it.

FDP_ACF_EXT.1 has been modified to prevent 'accessing' and not specifically 'modifiying'. Since audit logs are not going to be owned by a regular user, this should be okay. Thoughts?

That helps, but we still need it in FPT (Protection of TSF).  I added a new requirement -- hopefully this will do it.


[Feature Request]Kick on panel close

it would be rather useful to have the option to kick a player from the party at the same time you send a message to them. for example after you completed a trade with them you thank them and kick them from your party, issue is in the default config, both thanks and kick both close the panel so you would have to do one or the other manually or change the config and press two buttons.
And in a similar vein the option to leave a party on outgoing messages

tos viloation, sorry


NULL values in forms displayed as text "None"

Hi,
as part of my testing for #237 I discovered that our forms display NULL values as a string "None":

(This is a screenshot taken from one of our tests' output - the test fails.)
I didn't find an easy solution to this issue. The only one I found was to display form fields as such:
<input type="text" name="field" id="id_field" value="{{ form.field.value|default:"" }}" />

…which would require us to rewrite forms to HTML because we use {{ form.as_p }} in templates.
By the way, our forms could benefit from displaying them with Bootstrap markup, so we may hire django-bootstrap-form or django-crispy-forms.

On Sat, Apr 04, 2015 at 08:25:38AM -0700, Piotr Banaszkiewicz wrote:

as part of my testing for #237 I discovered that our forms display
NULL values as a string "None":
…
I didn't find an easy solution to this issue.

We could create a custom NullableCharField and set it's default widget
to use the empty string as the default.  For a similar approach with
date fields, see 1.

By the way, our forms could benefit from displaying them with
Bootstrap markup, so we may hire django-bootstrap-form or
django-crispy-forms.

I haven't used either (but I prefer the Django API + Angular approach
anyway ;).  Both look reasonable, but django-crispy-forms seems pretty
stable (last commit 2014-03-19 2 vs. 2015-03-09 3) and it has 3x
as many contributors and 7x as many commits, so I'd lean towards it.
On the other hand, 2014-03-19 may be too stable ;).  There hasn't
been much activity recently 4, but that will hopefully change
soonish 5.

I took django-cripsy-forms for a ride.
With a generic code I was able to turn all forms into something like this:

I took django-crispy-forms for a ride.
With a very generic code I was able to turn pretty much any form into something like:

It's rendering Nones as empty strings by default :sparkles:
I like it a lot, however crispy introduces some warnings in Django 1.8:
/home/piotr/workspace/anaconda/envs/amy3k/lib/python3.4/site-packages/crispy_forms/templatetags/crispy_forms_tags.py:202: RemovedInDjango19Warning: memoize wrapper is deprecated and will be removed in Django 1.9. Use django.utils.lru_cache instead.
  whole_uni_form_template = memoize(whole_uni_form_template, {}, 1)

If we decide to use django-crispy-forms, but we don't like it in the long run, we can revert very easily. Instead of using:
{% load crispy_forms_tags %}
{% crispy form form_helper %}

…we'd change back to:
<form action="" method="post" role="form">
    {% csrf_token %}
    {{ form.as_p }}
    <input type="submit" value="Submit" />
</form>

On Sun, Apr 05, 2015 at 02:00:03PM -0700, Piotr Banaszkiewicz wrote:

With a very generic code I was able to turn pretty much any form
into something like:

Looks good to me :).

 Use django.utils.lru_cache instead.

That looks like maraujop/django-crispy-forms#364.  Since there's
already a PR to fix it, I'm optimistic that this gets dealt with once
Miguel Araujo gets back on top of things 1.
Let's do it.

Let's do it.

Great!
I have one concern, though. I'm making all these changes because Amy isn't compatible with Django 1.8.
So when I make a PR it will resolve #237, #240, incorporate additional dependencies, add crispy to all forms, and display of some None values as "—".
If I split this PR, then we have a broken application at each of smaller PRs.
Personally I'd not split, because all these changes depend on each other. What is your opinion, @wking?

On Sun, Apr 05, 2015 at 02:41:11PM -0700, Piotr Banaszkiewicz wrote:

So when I make a PR it will resolve #237, #240, incorporate
additional dependencies, add crispy to all forms, and display of
some None values as "—".
If I split this PR, then we have a broken application at each of
smaller PRs.

The “None” breakage doesn't seem particularly serious to me.  I don't
mind if you want to go with a single PR, but I'd suggest:

Switch to crispy forms.
Migrate 1 to Django 1.8 with template changes, etc (links from 2).

The crispy form business shouln't need Django 1.8, should it?  Was
there anything else you were proposing for the big PR?

The crispy form business shouln't need Django 1.8, should it?

It's a nice solution for our issue caused by "None" values in forms. Prior to Django 1.8 it was not causing our tests to fail, now it is.
I'll go with this order:

Switch to crispy forms
Make the templates work nicer with None values (ie. represent None as "—", "maybe" or "unknown")
Add migration
Upgrade to TEMPLATES in settings.py

Sounds good?

On Sun, Apr 05, 2015 at 03:57:09PM -0700, Piotr Banaszkiewicz wrote:

I'll go with this order:

Switch to crispy forms
Make the templates work nicer with None values (ie. represent
None as "—", "maybe" or "unknown")
Add migration
Upgrade to TEMPLATES in settings.py

Sounds good?

Yeah, although if it's possible I'd prefer to stick with empty strings
to represent None.  Since 3 and 4 are both part of the 1.8 transition,
I'd put them in a single PR with a bump to requirements.txt.

Hi @wking,

I'd prefer to stick with empty strings to represent None

Let me summarize how's None going to be stored and displayed:

database: for example in Person model fields that are both blank and null will save empty string or None as NULL
form: None value will generate a form with value="" or, in case of BooleanField, a select with three values ("unknown", "yes", "no")
object details template / object list template: None will be displayed as "—" in CharFields and IntegerFields and DecimalFields (e.g. Event.attendance, Event.admin_fee), or as "unknown" in BooleanFields

Does that work for you?

Since 3 and 4 are both part of the 1.8 transition, I'd put them in a single PR with a bump to requirements.txt.

So if I understand correctly you want to have two PRs:

crispy forms, template changes
Django version bump, migration, template settings update

It's fine, I can do that thanks to you: I know how to split a branch with git rebase -i and git cherry-pick :-)


OCF: remove presence, add support for Links and Collections, add polling algorithms

in favor of a future solution, and for observing /oic/res for resource deletion. Fixing #92.
Signed-off-by: Zoltan Kis<EMAIL_ADDRESS>

@gabrielschulhof , @poussa PTAL

Since the presence is gone, is there any reason to keep devicelost event in client?

Since the presence is gone, is there any reason to keep devicelost event in client?

We can remove it, and re-add later when the device entry/exit proposal is accepted.
Or, we could keep it there but it won't work until it's fixed in the spec. Of course implementation could keep working with /oic/ad but it will be adherent to an earlier version of the OIC Core spec.

Github now allows us to push to a PR if we are collaborators. Cool!

 Feel free to delete my commit.

@gabrielschulhof could we merge this?

@zolkis Please specify that the polling value is to be given in milliseconds.

Please specify that the polling value is to be given in milliseconds.

It is already there: client.md line 91.

@zolkis oh, there it is :)

LGTM 👍

Actually, I take back the "LGTM" for now by deleting the comment where I gave it, because polling should maybe not be specified per-resource. It makes no sense to issue multiple recurring requests to /oic/res on a given device for different resources on that device at potentially different intervals.
Instead, it makes sense to have a single recurring GET /oic/res listener per device, started whenever the first "delete" listener is attached to any resource on that device and removed whenever the last "delete" listener is removed from the resources on said device.

It makes no sense to issue multiple recurring requests to /oic/res on a given device for different resources on that device at potentially different intervals.

I agree with this, but this has little to do with the polling algorithm. That is about  a different polling than the one replacing presence (polling /oic/res), the former is a possible step in the latter and is triggered when polling /oic/res does not work (for any reason).
Whether a resource is polled or not (for value, or for testing existence), and with what interval, should be specified per resource, because it is resource specific (how often the resource is expected to change, or how often the client app wants to know about change).
When polling is not specified, it is up to the implementation whether and how to use polling to respect the contracts of this API.
When polling is specified by the application, it is a (resource dependent) hint to the implementation that can be taken into account or be overridden by the implementation.
Does that make sense?

Wait a sec - what now? I thought the only reason for implementing polling was so we poll /oic/res once per device for the purposes of implementing the "delete" event.

Oh, I see ... if polling /oic/res does not work, poll the individual resource. Right?

Oh, I see ... if polling /oic/res does not work, poll the individual resource. Right?

Yes! And the implementation decides on that, depending on the capabilities of the underlying stack.

Well, in this implementation it's very unlikely that polling /oic/res won't
work. Observing /oic/res will certainly not work, but polling /oic/res will
almost certainly work.
On Thu, Dec 29, 2016 at 4:38 PM, Zoltan Kis<EMAIL_ADDRESS>wrote:

Oh, I see ... if polling /oic/res does not work, poll the individual
resource. Right?
Yes! And the implementation decides on that, depending on the capabilities
of the underlying stack.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/01org/iot-js-api/pull/24#issuecomment-269638945, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA7k0elD1vMP-DnWSG6MTOeZU18jLzfLks5rM8XjgaJpZM4LAGDk
.

polling /oic/res will almost certainly work

No problem, then you won't need to implement resource polling for presence.
The decision on polling /oic/res and polling individual resources are kind of independent, since the latter can be also triggered by applications (as a different feature) when they set resource.polling - but the implementation can override that too, depending on implementation (system) context.
Too flexible/confusing?

I would say so. If a resource does not support observation, we shouldn't provide polling for it. Let the applications implement that themselves.
Polling for presence is a necessity. Polling for data is not.

Of course presence (and polling, either for presence or value) makes sense only for resources that are under observation...
We have 2 separate needs to provide app-settable polling interval:

presence via polling either oic/res, or the resource itself;
polling the resource anyway (presumably with larger interval) regardless whether observe is on or off (most likely on).

One might argue this second use case is not needed. But even if the implementation can be trusted to provide the ondelete event when the resource is unreachable, the impl still needs to know what is the interval after which a resource is declared dead. That is resource dependent and app-context dependent, so optimally the app should have a way of telling that to the impl.
Keeping resource.polling would also allow implementations to choose the best polling times per remote device.
If we remove resource.polling, then polling becomes entirely encapsulated by implementations (or how should we allow apps to provide an interval hint for that), and as a result, for the second use case apps will poll themselves, which IMHO is not desirable.
We could leave this open for longer consideration if needed.

OK, so, like, "The resource hasn't given me any new data in > resource.polling, so it must be dead" ... ?

No, it's more like "the resource has not given me any new data in resource.polling time, so let's check", and if that retrieve fails, the resource is dead. The implementation should do this, in order to be able to fire the resource.ondelete event, but it would be nice if the app would have some effect on the value of resource.polling.

OK, gotcha. But what if the retrieve doesn't fail? Do I convert the response to an "update" event? Do I assume that the properties have the same value as the last update event and can therefore discard the response?
Also, I would prefer that this checking be opt-in rather than opt-out. That is, I would not perform this check unless resource.polling were explicitly set to a positive value, because I want the default to be not to perform this check, rather than to always perform this check at, say, 5 second intervals unless resource.polling is set to 0.

It is opt-in.
By default, resource.polling is undefined. The implementation decides whether to do polling or not in order to implement resource.ondelete.
If at some point the app sets resource.polling to 0, the impl stops polling the resource itself altogether and relies only on polling /oic/res.
If at some point the app sets resource.polling to a positive value, the impl starts polling. If retrieve fails, the impl fires the resource.ondelete and unwinds the resource (stops observing etc).
If retrieve succeeds, we have two options:

the impl checks the resource representation; if changed, fires the resource.onupdate event (like saying "I know the resource is alive, but since no change happened, no events are fired".
the impl fires the resource.onupdate event anyway, like saying "here is your data you asked at least every resource.polling intervals".
I am somewhat open to which semantic we implement, but option 1 would be closer to the original contract of resource.onupdate. If the app would do polling itself, would do the resource repr comparison itself. So I say we should go by option 1.

Actually, come to think of it, I wouldn't fire onupdate even if the data had changed, because, presumably the resource will fire notify in such an event, and the onupdate will be fired "naturally".

Right, so it would be enough to do the first part of the steps (including the clause for "if retrieve fails, ...".

Based on the discussion above, it seems the polling part is more or less stable, so merging this in order to have presence removed and errors defined. Polling algorithms can be refined in later commits.


Add prop to allow dragging from top area only

This new prop, dragFromTop, will allow users to drag only the top are of the view to close it instead of the whole view. This easily fixes the issue of not being able to scroll inside of it when closeOnDragDown is true.
In my case, I am using a WebView inside of the BottomSheet and wasn't allowing me to scroll.
I haven't faced any issues so far.
Thought it might be helpful to others :)

It was just what I needed. Very good, thank you :)

@corasan Thank you for taking the time to improve this lib. However, I will rename dragFromTop to dragFromTopOnly in the next release.

Wow, this really helped me as it was rendering a web view and not allowing me to properly interact with elements on the web. Thanks a lot!

Wow, this really helped me as it was rendering a web view and not allowing me to properly interact with elements on the web. Thanks a lot!


get_route_to() now returns all vrfs

Added test case for multi-vrf environment
<!-- Make sure you have read http://napalm.readthedocs.io/en/latest/contributing/index.html --!>

Coverage increased (+0.0009%) to 79.852% when pulling e23f8d8775e344eccdb2a90b9edbed30e6b73841 on kbirkeland:develop into 6782586f7d51cdc5346b67a6ec1af5e05deb25fc on napalm-automation:develop.

Thanks @kbirkeland


NTR resolution of meiotic recombination intermediates

Hi,
for PMID 22292001
I need
regulation of resolution of meiotic recombination intermediates
regulates GO:0000712
resolution of meiotic recombination intermediates is also missing this relationship
is_a GO:0071139

GO:0000712    resolution of meiotic recombination intermediates?

yep - GO:0000712 is missing the 'is_a GO:0071139' link

thought it was weird ! Thanks

updated descr

I think for now we'll just use GO:0000712 for annotations - the paper doesn't provide any data about a regulatory mechanism (although there's a tantalizing possibility, it's untested).
So all we need in the short term here is the missing link GO:0000712 is_a GO:0071139.


fix: fix misc. issues

add missing name field to coder_parameter
add example code for dotfiles
update jupyterlab screenshot
Add example code for personalize
add example code for vscode desktop
fix icon path and add display_name to vscode desktop
fix version name in KasmVNC
fix kasmVNC to install non-interactivly
fix jupyterlab

@bpmct can you approve this one?
KasmVNC is still broken
I would appreciate some help


QOM for Insert or general Query is missing in jOOQ

Is this related to? https://github.com/neo4j-contrib/sql2cypher/issues/1.
It's not missing in jOOQ 3.18:
https://www.jooq.org/javadoc/dev/org.jooq/org/jooq/impl/QOM.Insert.html
But perhaps you downgraded jOOQ?

There's a part about the QOM API being experimental, where I'm not quite sure what to do with those top level types like Query, or any other type listed here:
https://blog.jooq.org/a-brief-overview-over-the-most-common-jooq-types/
As you can see, I'm not even sure how to name these types other than "most common jOOQ types". I'm not sure yet whether:

There should be a separate QOM / DSL type or a shared one
Accessors and mutators should be on the shared one (e.g. on org.jooq.Select) or not

We can already work with this QOM API, but this is the part that will probably break in the near future. Once this project here builds with tests, I'll make it part of jOOQ's CI/CD pipeline, to be able to proactively upgrade its logic, should jOOQ's API change.
So, in the short run, perhaps you have a specific question?

I don't know what I was thinking here… :) It works.


Fullscreen event not firing

I am using an HTML5 player and cannot get the enterfullscreen or exitfullscreen events to fire. I have tried using other events and can get all of them to work expect the fullscreen.
My player does have custom controls and icons but I have tried using the default controls and icons and still have the same issue. There are no errors in the console. I have seen this issue in Chrome, Safari, and Firefox on a Mac. I am using the latest version of plyr.
My setup code:
Full JS: https://www.pastiebin.com/5894dce55f600
plyr.setup('.js-player', { 		html: controls, 		//debug: true 	});
The event call:
$('.js-player').on('enterfullscreen', function(event) { 		console.log("here!");    });
This shows nothing in the console.
My video HTML:
<video poster="images/headphones.jpg" class="js-player">          <source src="videos/sample-video.mp4" type="video/mp4"> </video>

Same error here? It gets logged when debug is enabled but it does not bubble up to be caught once fired?

@lorengrayh instead of $('.js-player') use players[0]
setup the player like this:
var players = plyr.setup(document.querySelector('#player'), { autoplay: true, controls: ['play-large', 'play', 'progress', 'current-time', 'mute', 'volume', 'fullscreen'] });

Closing this one as I think it's fixed but feel free to re-open if not solved in v3 👍

I'm seeing this behavior in 3.4.3. cue events attached at the same time fire as expected.
like @dieskim's case, when debug is enabled, I see the enterfullscreen and exitfullscreen events fire, but my handlers are never called.
the actual event is attached via:
const video = document.getElementById('plyr-element-id')
video.addEventListener('enterfullscreen', (e) => console.log('enter the dragon'))

The dragon hasn't entered yet :(

use below code you will get event of full screen and exit full screen.
after initialised plyr add below lines -  (i am using same jsfiddleexample - https://jsfiddle.net/r9wpkxyq/11/)
window.plyr = new Plyr('#plyr-video', {
controls: ['play', 'progress', 'current-time', 'mute', 'volume', 'fullscreen'],
autoplay: true,
loop: { active: true },
invertTime: false,
volume: 0,
muted: true
})
window.plyr.on('enterfullscreen', (event) => {
console.log('Entered full-screen mode');
});
window.plyr.on('exitfullscreen', (event) => {
  console.log('Exited full-screen mode');
});


Checkout: auto redirect to storefrontURL/checkout-spa/checkout=xxx

Summary
I have deployed saleor-app-checkout app and storefront app which followed by the instruction. But when I clicked on the checkout button, the issue came. instead of open storefront/checkout/?checkout=xxx, it opened storefront/checkout-spa/checkout=xxx. And then show not found page.
If i take params from the url and join to checkout-app/checkout-spa/?checkout=xxx, It will be OK.
Steps to reproduce

Add products to cart
Click the checkout button
Browser will open storefront/checkout-spa/?checkout=xxx

A link to a reproduction repository
No response
Output from envinfo
No response

We cannot reproduce this issue. I think it likely results from a misconfiguration. Can you provide more details or a link to an environment?

I think this is something to do with the production and env variables or something ? I am also facing the same issue here at this https://shop.cicilabel.com , my checkout url application is this https://checkout.cicilabel.com
I am also facing the same issue , where the page ends up on 404 maybe some config or env variable issues

Now, after changing the .env to something else , I was able to get the too many redirects error : https://shop.cicilabel.com/checkout/?checkout=Q2hlY2tvdXQ6NTI2NzFlMzYtNDA5OC00MzAyLWJiNjAtNzA1ZTgyYjA2ZWNj&locale=en-US&channel=default-channel&domain=cici-label.herokuapp.com&saleorApiUrl=https%3A%2F%2Fcici-label.herokuapp.com%2Fgraphql%2F

Closing due to lack of minimal reproducible example.


deprecation: package needs updating

Last time I looked at this, @azure/arm-containerservice didn't actually work for us - I think it didn't play nicely with the credentials that the Azure Account extension gave us.  I think I raised an issue for that but I can't remember where or find it now... anyway @Tatsinnit has bravely volunteered to pick this one up so hopefully he will be able to get it sorted!

👍  Thanks: @itowlson - I might have something to share\show\thought-share tomorrow as a fix for this, at least at this repo level. 🙈

💡 I am re-opening this, because I can see with the changes type fix we end up in a internal error for MS-Rest-JS in --> ServiceClient.ts ==> sendRequest which cause extension level type error. Thanks heaps.

Hiya guys @philliphoff & @itowlson 🛡 🤖
Below is my 2 cent finding of how this update will break existing merge config and save kubeconfig changes.
Weird ms-rest-js ==> serviceClient.ts failure led to more deep dependency issue.
I am sure new package is bigger and better, butI really think that this whole @azure/containerservices or arm-resource et. al. packages change was not thought through and they contain breaking changes from the original packages, and mere: https://github.com/Azure/azure-sdk-for-js/blob/master/documentation/Migration.md is not full thought through for various other dependencies 🐉
Here is the weird behaviour I see so I am planning to revert my changes and keep using old packages until we have clear plan to tackle this. Please advice.

Behaviour after Package update: When I select things like save kubeconfig I see random error thrown which is like this: TypeError: Cannot read property 'then' of undefined which gets thrown from this line: https://github.com/Azure/vscode-aks-tools/blob/master/src/extension.ts#L52

Lets Dig Deeper

We use vscode-azureextensionui which has ISubscriptionContext dependency which we use for our credential to be types as ServiceClientCredentials Now this is dependent on ms-rest  i.e. NOT ms-rest-js :) and surely ms-rest-js has done this differently in new implementation because I see signRequest has different return signature + even simple ugly type conversation let it fail at the ms-rest-js ==> ServiceClient.ts on this line https://github.com/Azure/ms-rest-js/blob/master/lib/serviceClient.ts#L328 .   https://github.com/Azure/vscode-aks-tools/blob/master/src/tree/azureAccountTreeItem.ts#L5

Gyst: I noticed that when we upgraded our packages to latest @azure/arm-containerservice  **Why ms-rest-js fails at ms-rest-js ==> sendRequest then I realised that might have to do with the type conversion. Which points that ms-rest-js have some sort of different way of handling the sendRequest vs ms-rest. 🐓

Plausible solution with a But :

Seems like only way to correctly use is to Change the depenedent on using alternative to using vscode-azureextensionui because the ServiceClientCredentials from this is dependent on ms-rest (that is deep, and do we have and alternative at all for this) - I think not at this stage.

To unblock this for now:

I propose we keep using the old one until be have a plan or you guys think that there is an easy alternative to the types we used at clusterTreeItem level etc...

Thanks heaps in taking time for reading this, I thought I will do a quick idea dump as to what are my findings and get your pinions to move forward for this. : = )

💡 -- Thanks @itowlson for quick chat and you summed it write, i..e bunch of stuff not talking nicely to each other with this extension is consuming so I am going ahead and reverting these changes.


Log go test outputs

We capture the output and it is not displayed on the CI logs so we do not know why it failed when it does, for example.

Codecov Report

Merging #126 (65a7bcd) into master (12f28c6) will increase coverage by 0.01%.
The diff coverage is 63.63%.

@@            Coverage Diff             @@
##           master     #126      +/-   ##
==========================================
+ Coverage   62.37%   62.39%   +0.01%
==========================================
  Files          16       16
  Lines         925      936      +11
  Branches      113      115       +2
==========================================
+ Hits          577      584       +7
- Misses        319      321       +2
- Partials       29       31       +2

Impacted Files
Coverage Δ

app_test_suite/steps/executors/gotest.py
65.51% <63.63%> (-0.45%)
:arrow_down:

Continue to review full report at Codecov.

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


Make error

[ 28%] Building NVCC (Device) object CMakeFiles/warpctc.dir/src/warpctc_generated_reduce.cu.o
[ 28%] Building NVCC (Device) object CMakeFiles/warpctc.dir/src/warpctc_generated_ctc_entrypoint.cu.o
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/ctc_entrypoint.cu(1): error: this declaration has no storage class or type specifier
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/ctc_entrypoint.cu(1): error: expected a ";"
2 errors detected in the compilation of "/tmp/tmpxft_00000943_00000000-12_ctc_entrypoint.compute_62.cpp1.ii".
CMake Error at warpctc_generated_ctc_entrypoint.cu.o.cmake:266 (message):
Error generating file
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/build/CMakeFiles/warpctc.dir/src/./warpctc_generated_ctc_entrypoint.cu.o
CMakeFiles/warpctc.dir/build.make:63: recipe for target 'CMakeFiles/warpctc.dir/src/warpctc_generated_ctc_entrypoint.cu.o' failed
make[3]: *** [CMakeFiles/warpctc.dir/src/warpctc_generated_ctc_entrypoint.cu.o] Error 1
make[3]: *** Waiting for unfinished jobs....
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/reduce.cu(44): warning: function "__shfl_down(float, unsigned int, int)"
/usr/local/cuda/include/sm_30_intrinsics.hpp(278): here was declared deprecated ("__shfl_down() is deprecated in favor of __shfl_down_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
detected during:
instantiation of "T CTAReduce<NT, T, Rop>::reduce(int, T, CTAReduce<NT, T, Rop>::Storage &, int, Rop) [with NT=128, T=float, Rop=ctc_helper::add<float, float>]"
(76): here
instantiation of "void reduce_rows<NT,Iop,Rop,T>(Iop, Rop, const T *, T *, int, int) [with NT=128, Iop=ctc_helper::negate<float, float>, Rop=ctc_helper::add<float, float>, T=float]"
(124): here
instantiation of "void ReduceHelper::impl(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::negate<float, float>, Rof=ctc_helper::add<float, float>]"
(139): here
instantiation of "ctcStatus_t reduce(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::negate<float, float>, Rof=ctc_helper::add<float, float>]"
(149): here
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/reduce.cu(44): warning: function "__shfl_down(float, unsigned int, int)"
/usr/local/cuda/include/sm_30_intrinsics.hpp(278): here was declared deprecated ("__shfl_down() is deprecated in favor of __shfl_down_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
detected during:
instantiation of "T CTAReduce<NT, T, Rop>::reduce(int, T, CTAReduce<NT, T, Rop>::Storage &, int, Rop) [with NT=128, T=float, Rop=ctc_helper::maximum<float, float>]"
(76): here
instantiation of "void reduce_rows<NT,Iop,Rop,T>(Iop, Rop, const T *, T *, int, int) [with NT=128, Iop=ctc_helper::identity<float, float>, Rop=ctc_helper::maximum<float, float>, T=float]"
(124): here
instantiation of "void ReduceHelper::impl(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::identity<float, float>, Rof=ctc_helper::maximum<float, float>]"
(139): here
instantiation of "ctcStatus_t reduce(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::identity<float, float>, Rof=ctc_helper::maximum<float, float>]"
(157): here
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/reduce.cu(44): warning: function "__shfl_down(float, unsigned int, int)"
/usr/local/cuda/include/sm_30_intrinsics.hpp(278): here was declared deprecated ("__shfl_down() is deprecated in favor of __shfl_down_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
detected during:
instantiation of "T CTAReduce<NT, T, Rop>::reduce(int, T, CTAReduce<NT, T, Rop>::Storage &, int, Rop) [with NT=128, T=float, Rop=ctc_helper::add<float, float>]"
(76): here
instantiation of "void reduce_rows<NT,Iop,Rop,T>(Iop, Rop, const T *, T *, int, int) [with NT=128, Iop=ctc_helper::negate<float, float>, Rop=ctc_helper::add<float, float>, T=float]"
(124): here
instantiation of "void ReduceHelper::impl(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::negate<float, float>, Rof=ctc_helper::add<float, float>]"
(139): here
instantiation of "ctcStatus_t reduce(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::negate<float, float>, Rof=ctc_helper::add<float, float>]"
(149): here
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/reduce.cu(44): warning: function "__shfl_down(float, unsigned int, int)"
/usr/local/cuda/include/sm_30_intrinsics.hpp(278): here was declared deprecated ("__shfl_down() is deprecated in favor of __shfl_down_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
detected during:
instantiation of "T CTAReduce<NT, T, Rop>::reduce(int, T, CTAReduce<NT, T, Rop>::Storage &, int, Rop) [with NT=128, T=float, Rop=ctc_helper::maximum<float, float>]"
(76): here
instantiation of "void reduce_rows<NT,Iop,Rop,T>(Iop, Rop, const T *, T *, int, int) [with NT=128, Iop=ctc_helper::identity<float, float>, Rop=ctc_helper::maximum<float, float>, T=float]"
(124): here
instantiation of "void ReduceHelper::impl(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::identity<float, float>, Rof=ctc_helper::maximum<float, float>]"
(139): here
instantiation of "ctcStatus_t reduce(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::identity<float, float>, Rof=ctc_helper::maximum<float, float>]"
(157): here
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/reduce.cu(44): warning: function "__shfl_down(float, unsigned int, int)"
/usr/local/cuda/include/sm_30_intrinsics.hpp(278): here was declared deprecated ("__shfl_down() is deprecated in favor of __shfl_down_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
detected during:
instantiation of "T CTAReduce<NT, T, Rop>::reduce(int, T, CTAReduce<NT, T, Rop>::Storage &, int, Rop) [with NT=128, T=float, Rop=ctc_helper::add<float, float>]"
(76): here
instantiation of "void reduce_rows<NT,Iop,Rop,T>(Iop, Rop, const T *, T *, int, int) [with NT=128, Iop=ctc_helper::negate<float, float>, Rop=ctc_helper::add<float, float>, T=float]"
(124): here
instantiation of "void ReduceHelper::impl(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::negate<float, float>, Rof=ctc_helper::add<float, float>]"
(139): here
instantiation of "ctcStatus_t reduce(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::negate<float, float>, Rof=ctc_helper::add<float, float>]"
(149): here
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/reduce.cu(44): warning: function "__shfl_down(float, unsigned int, int)"
/usr/local/cuda/include/sm_30_intrinsics.hpp(278): here was declared deprecated ("__shfl_down() is deprecated in favor of __shfl_down_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
detected during:
instantiation of "T CTAReduce<NT, T, Rop>::reduce(int, T, CTAReduce<NT, T, Rop>::Storage &, int, Rop) [with NT=128, T=float, Rop=ctc_helper::maximum<float, float>]"
(76): here
instantiation of "void reduce_rows<NT,Iop,Rop,T>(Iop, Rop, const T *, T *, int, int) [with NT=128, Iop=ctc_helper::identity<float, float>, Rop=ctc_helper::maximum<float, float>, T=float]"
(124): here
instantiation of "void ReduceHelper::impl(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::identity<float, float>, Rof=ctc_helper::maximum<float, float>]"
(139): here
instantiation of "ctcStatus_t reduce(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::identity<float, float>, Rof=ctc_helper::maximum<float, float>]"
(157): here
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/reduce.cu(44): warning: function "__shfl_down(float, unsigned int, int)"
/usr/local/cuda/include/sm_30_intrinsics.hpp(278): here was declared deprecated ("__shfl_down() is deprecated in favor of __shfl_down_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
detected during:
instantiation of "T CTAReduce<NT, T, Rop>::reduce(int, T, CTAReduce<NT, T, Rop>::Storage &, int, Rop) [with NT=128, T=float, Rop=ctc_helper::add<float, float>]"
(76): here
instantiation of "void reduce_rows<NT,Iop,Rop,T>(Iop, Rop, const T *, T *, int, int) [with NT=128, Iop=ctc_helper::negate<float, float>, Rop=ctc_helper::add<float, float>, T=float]"
(124): here
instantiation of "void ReduceHelper::impl(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::negate<float, float>, Rof=ctc_helper::add<float, float>]"
(139): here
instantiation of "ctcStatus_t reduce(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::negate<float, float>, Rof=ctc_helper::add<float, float>]"
(149): here
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/reduce.cu(44): warning: function "__shfl_down(float, unsigned int, int)"
/usr/local/cuda/include/sm_30_intrinsics.hpp(278): here was declared deprecated ("__shfl_down() is deprecated in favor of __shfl_down_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
detected during:
instantiation of "T CTAReduce<NT, T, Rop>::reduce(int, T, CTAReduce<NT, T, Rop>::Storage &, int, Rop) [with NT=128, T=float, Rop=ctc_helper::maximum<float, float>]"
(76): here
instantiation of "void reduce_rows<NT,Iop,Rop,T>(Iop, Rop, const T *, T *, int, int) [with NT=128, Iop=ctc_helper::identity<float, float>, Rop=ctc_helper::maximum<float, float>, T=float]"
(124): here
instantiation of "void ReduceHelper::impl(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::identity<float, float>, Rof=ctc_helper::maximum<float, float>]"
(139): here
instantiation of "ctcStatus_t reduce(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::identity<float, float>, Rof=ctc_helper::maximum<float, float>]"
(157): here
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/reduce.cu(44): warning: function "__shfl_down(float, unsigned int, int)"
/usr/local/cuda/include/sm_30_intrinsics.hpp(278): here was declared deprecated ("__shfl_down() is deprecated in favor of __shfl_down_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
detected during:
instantiation of "T CTAReduce<NT, T, Rop>::reduce(int, T, CTAReduce<NT, T, Rop>::Storage &, int, Rop) [with NT=128, T=float, Rop=ctc_helper::add<float, float>]"
(76): here
instantiation of "void reduce_rows<NT,Iop,Rop,T>(Iop, Rop, const T *, T *, int, int) [with NT=128, Iop=ctc_helper::negate<float, float>, Rop=ctc_helper::add<float, float>, T=float]"
(124): here
instantiation of "void ReduceHelper::impl(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::negate<float, float>, Rof=ctc_helper::add<float, float>]"
(139): here
instantiation of "ctcStatus_t reduce(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::negate<float, float>, Rof=ctc_helper::add<float, float>]"
(149): here
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/reduce.cu(44): warning: function "__shfl_down(float, unsigned int, int)"
/usr/local/cuda/include/sm_30_intrinsics.hpp(278): here was declared deprecated ("__shfl_down() is deprecated in favor of __shfl_down_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
detected during:
instantiation of "T CTAReduce<NT, T, Rop>::reduce(int, T, CTAReduce<NT, T, Rop>::Storage &, int, Rop) [with NT=128, T=float, Rop=ctc_helper::maximum<float, float>]"
(76): here
instantiation of "void reduce_rows<NT,Iop,Rop,T>(Iop, Rop, const T *, T *, int, int) [with NT=128, Iop=ctc_helper::identity<float, float>, Rop=ctc_helper::maximum<float, float>, T=float]"
(124): here
instantiation of "void ReduceHelper::impl(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::identity<float, float>, Rof=ctc_helper::maximum<float, float>]"
(139): here
instantiation of "ctcStatus_t reduce(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::identity<float, float>, Rof=ctc_helper::maximum<float, float>]"
(157): here
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/reduce.cu(44): warning: function "__shfl_down(float, unsigned int, int)"
/usr/local/cuda/include/sm_30_intrinsics.hpp(278): here was declared deprecated ("__shfl_down() is deprecated in favor of __shfl_down_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
detected during:
instantiation of "T CTAReduce<NT, T, Rop>::reduce(int, T, CTAReduce<NT, T, Rop>::Storage &, int, Rop) [with NT=128, T=float, Rop=ctc_helper::add<float, float>]"
(76): here
instantiation of "void reduce_rows<NT,Iop,Rop,T>(Iop, Rop, const T *, T *, int, int) [with NT=128, Iop=ctc_helper::negate<float, float>, Rop=ctc_helper::add<float, float>, T=float]"
(124): here
instantiation of "void ReduceHelper::impl(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::negate<float, float>, Rof=ctc_helper::add<float, float>]"
(139): here
instantiation of "ctcStatus_t reduce(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::negate<float, float>, Rof=ctc_helper::add<float, float>]"
(149): here
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/reduce.cu(44): warning: function "__shfl_down(float, unsigned int, int)"
/usr/local/cuda/include/sm_30_intrinsics.hpp(278): here was declared deprecated ("__shfl_down() is deprecated in favor of __shfl_down_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
detected during:
instantiation of "T CTAReduce<NT, T, Rop>::reduce(int, T, CTAReduce<NT, T, Rop>::Storage &, int, Rop) [with NT=128, T=float, Rop=ctc_helper::maximum<float, float>]"
(76): here
instantiation of "void reduce_rows<NT,Iop,Rop,T>(Iop, Rop, const T *, T *, int, int) [with NT=128, Iop=ctc_helper::identity<float, float>, Rop=ctc_helper::maximum<float, float>, T=float]"
(124): here
instantiation of "void ReduceHelper::impl(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::identity<float, float>, Rof=ctc_helper::maximum<float, float>]"
(139): here
instantiation of "ctcStatus_t reduce(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::identity<float, float>, Rof=ctc_helper::maximum<float, float>]"
(157): here
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/reduce.cu(44): warning: function "__shfl_down(float, unsigned int, int)"
/usr/local/cuda/include/sm_30_intrinsics.hpp(278): here was declared deprecated ("__shfl_down() is deprecated in favor of __shfl_down_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
detected during:
instantiation of "T CTAReduce<NT, T, Rop>::reduce(int, T, CTAReduce<NT, T, Rop>::Storage &, int, Rop) [with NT=128, T=float, Rop=ctc_helper::add<float, float>]"
(76): here
instantiation of "void reduce_rows<NT,Iop,Rop,T>(Iop, Rop, const T *, T *, int, int) [with NT=128, Iop=ctc_helper::negate<float, float>, Rop=ctc_helper::add<float, float>, T=float]"
(124): here
instantiation of "void ReduceHelper::impl(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::negate<float, float>, Rof=ctc_helper::add<float, float>]"
(139): here
instantiation of "ctcStatus_t reduce(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::negate<float, float>, Rof=ctc_helper::add<float, float>]"
(149): here
/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/src/reduce.cu(44): warning: function "__shfl_down(float, unsigned int, int)"
/usr/local/cuda/include/sm_30_intrinsics.hpp(278): here was declared deprecated ("__shfl_down() is deprecated in favor of __shfl_down_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
detected during:
instantiation of "T CTAReduce<NT, T, Rop>::reduce(int, T, CTAReduce<NT, T, Rop>::Storage &, int, Rop) [with NT=128, T=float, Rop=ctc_helper::maximum<float, float>]"
(76): here
instantiation of "void reduce_rows<NT,Iop,Rop,T>(Iop, Rop, const T *, T *, int, int) [with NT=128, Iop=ctc_helper::identity<float, float>, Rop=ctc_helper::maximum<float, float>, T=float]"
(124): here
instantiation of "void ReduceHelper::impl(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::identity<float, float>, Rof=ctc_helper::maximum<float, float>]"
(139): here
instantiation of "ctcStatus_t reduce(Iof, Rof, const T *, T *, int, int, __nv_bool, cudaStream_t) [with T=float, Iof=ctc_helper::identity<float, float>, Rof=ctc_helper::maximum<float, float>]"
(157): here
make[3]: Leaving directory '/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/build'
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/warpctc.dir/all' failed
make[2]: *** [CMakeFiles/warpctc.dir/all] Error 2
make[2]: Leaving directory '/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/build'
Makefile:127: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/build'
generating /tmp/tmpzdx_enm6/_ctc.c
setting the current directory to '/tmp/tmpzdx_enm6'
running build_ext
building '_ctc' extension
creating data
creating data/f3v1
creating data/f3v1/v-yuewng
creating data/f3v1/v-yuewng/gitclone
creating data/f3v1/v-yuewng/gitclone/speech
creating data/f3v1/v-yuewng/gitclone/speech/libs
creating data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc
creating data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/pytorch_binding
creating data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/pytorch_binding/src
gcc -pthread -B /opt/conda/envs/pytorch-py3.6/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/opt/conda/envs/pytorch-py3.6/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include -I/opt/conda/envs/pytorch-py3.6/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH -I/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/include -I/opt/conda/envs/pytorch-py3.6/include/python3.6m -c _ctc.c -o ./_ctc.o
gcc -pthread -B /opt/conda/envs/pytorch-py3.6/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/opt/conda/envs/pytorch-py3.6/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include -I/opt/conda/envs/pytorch-py3.6/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH -I/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/include -I/opt/conda/envs/pytorch-py3.6/include/python3.6m -c /data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/pytorch_binding/src/warp_ctc.c -o ./data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/pytorch_binding/src/warp_ctc.o
gcc -pthread -shared -B /opt/conda/envs/pytorch-py3.6/compiler_compat -L/opt/conda/envs/pytorch-py3.6/lib -Wl,-rpath=/opt/conda/envs/pytorch-py3.6/lib -Wl,--no-as-needed -Wl,--sysroot=/ ./_ctc.o ./data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/pytorch_binding/src/warp_ctc.o -L/data/f3v1/v-yuewng/gitclone/speech/libs/warp-ctc/build -lwarpctc -o ./_ctc.so
/opt/conda/envs/pytorch-py3.6/compiler_compat/ld: cannot find -lwarpctc
collect2: error: ld returned 1 exit status
Traceback (most recent call last):
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/distutils/unixccompiler.py", line 197, in link
self.spawn(linker + ld_args)
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/distutils/ccompiler.py", line 909, in spawn
spawn(cmd, dry_run=self.dry_run)
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/distutils/spawn.py", line 36, in spawn
_spawn_posix(cmd, search_path, dry_run=dry_run)
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/distutils/spawn.py", line 159, in _spawn_posix
% (cmd, exit_status))
distutils.errors.DistutilsExecError: command 'gcc' failed with exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/site-packages/cffi/ffiplatform.py", line 51, in _build
dist.run_command('build_ext')
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/distutils/command/build_ext.py", line 339, in run
self.build_extensions()
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/distutils/command/build_ext.py", line 448, in build_extensions
self._build_extensions_serial()
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/distutils/command/build_ext.py", line 473, in _build_extensions_serial
self.build_extension(ext)
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/distutils/command/build_ext.py", line 558, in build_extension
target_lang=language)
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/distutils/ccompiler.py", line 717, in link_shared_object
extra_preargs, extra_postargs, build_temp, target_lang)
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/distutils/unixccompiler.py", line 199, in link
raise LinkError(msg)
distutils.errors.LinkError: command 'gcc' failed with exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "build.py", line 39, in
ffi.build()
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/site-packages/torch/utils/ffi/init.py", line 184, in build
_build_extension(ffi, cffi_wrapper_name, target_dir, verbose)
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/site-packages/torch/utils/ffi/init.py", line 108, in _build_extension
outfile = ffi.compile(tmpdir=tmpdir, verbose=verbose, target=libname)
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/site-packages/cffi/api.py", line 690, in compile
compiler_verbose=verbose, debug=debug, **kwds)
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/site-packages/cffi/recompiler.py", line 1513, in recompile
compiler_verbose, debug)
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/site-packages/cffi/ffiplatform.py", line 22, in compile
outputfilename = _build(tmpdir, ext, compiler_verbose, debug)
File "/opt/conda/envs/pytorch-py3.6/lib/python3.6/site-packages/cffi/ffiplatform.py", line 58, in _build
raise VerificationError('%s: %s' % (e.class.name, e))
cffi.error.VerificationError: LinkError: command 'gcc' failed with exit status 1
Makefile:5: recipe for target 'warp' failed
make: *** [warp] Error 1

I had the same problem.
I solved the problem by downgrading pytorch version.
ex.
pip uninstall torch
pip install torch==0.4.1


Dynamic List Functionality

We need to add functionality to pull DynamicLists and DynamicListItems from the database.

Note: We have a model for list items, but we will have to do some extra work to pull ticket statuses from the ticket_status table.

Would this allow setting up of different status lists per queue?
So tickets in the data processing (eg received, authorised, processing added, QC, completed etc) can have different statuses to those in the software development queue (R&D, in coding, security testing, User acceptance testing, ready for push to live, pushed to live etc)
One list of statuses
Each status can be linked to one or many queues so that when reporting across department with different queues is easy to pull out all the "Closed" tickets without having to choose each queue's own version of closed.

@cjohnsonuk
No, this is just adding core DynamicList functionality. However this is something we can add to our feature request list for possible future development.
Cheers.


--separate-relative inserts a new line even when it is not really needed

Hey Anthony
It seems that --separate-relative inserts a new line even when it is not really needed (e.g. when you only have relative imports).
Reproducer
mkdir my_package
touch my_package/{a,b,__init__}.py
cat <<EOF >> my_package/__init__.py
from .a import *  # noqa
from .b import *  # noqa
EOF

$ reorder-python-imports --py38-plus --separate-relative --separate-from-import --diff-only my_package/__init__.py
--- my_package/__init__.py
+++ my_package/__init__.py
@@ -1,2 +1,3 @@
+
 from .a import *  # noqa
 from .b import *  # noqa

If you want I can have a look
Pre-commit + pyupgrade
This new line was actually causing problems with pre-commit though and at least initially it was relatively hard to understand why the hooks were failing.
I had both reorder-python-imports and pyupgrade (in this order) and to the extend that I can understand this, they were probably creating "conflicting" patches, or perhaps more precisely, patches which when applied were resulting in the original file. I.e. reorder-python-imports was adding a newline and pyupgrade was removing it.
This way the hooks were always failing no matter how many times you run them.
Not sure if there is something that can be done about this case, but If you want I can open a ticket on pre-commit.

https://github.com/asottile/reorder_python_imports/pull/24

This seems to be fixing it:
diff --git a/reorder_python_imports.py b/reorder_python_imports.py
index 37d0ba5..4c4ba0d 100644
--- a/reorder_python_imports.py
+++ b/reorder_python_imports.py
@@ -384,7 +384,7 @@ def apply_import_sorting(
         if last_import_obj is not None:
             new_imports.append(CodePartition(CodeType.NON_CODE, '\n'))

-    if relative_imports:
+    if relative_imports and len(sorted_blocks) > 1:
         relative_imports.insert(0, CodePartition(CodeType.NON_CODE, '\n'))
     # XXX: I want something like [x].join(...) (like str join) but for now
     # this works
diff --git a/tests/reorder_python_imports_test.py b/tests/reorder_python_imports_test.py
index 756d586..71c73e6 100644
--- a/tests/reorder_python_imports_test.py
+++ b/tests/reorder_python_imports_test.py
@@ -891,6 +891,19 @@ def test_separate_relative_and_separate_from():
     )

+def test_separate_relative_and_separate_from_when_only_relative_imports_are_present():
+    ret = fix_file_contents(
+        'from . import bar\n'
+        'from . import foo\n',
+        separate_from_import=True,
+        separate_relative=True,
+    )
+    assert ret == (
+        'from . import bar\n'
+        'from . import foo\n'
+    )
+
+
 def test_fix_crlf():
     s = (
         '"""foo"""\r\n'

fwiw I'm probably going to remove this option at some point due to the number of weird edge cases it causes, but in the meantime would you like to send a PR?

reopening as this change caused a regression and was reverted (see #136)


restore terminal session on startup issues when using both vscode and vscode insiders

Issue Type: Bug
I always run both the regular and insiders version simultaiously (insiders for front end, regular for backend),
when I re-open my editors, the terminal shows "Session contents restored from [date] at [time]", and it does correctly show the previous commands, however when i press "up" to retrieve my prevous commands it looks like it is pulling it from the regular version, as it gives me "npm run watch" which i only ever run on the backend (regular version) and never on the insiders version.
expected behaviour is that it would give me "npm run serve" which is the last command i used in the insiders integrated terminal
step by step:
run vscode and vscode insiders with bash integrated terminal for each
run npm run serve on insiders, and npm run watch on regular
close insiders and re-open
see "session contents restored from [date] at [time]"
tap up arrow
result:
will give you the command "npm run watch"
expected result:
will give you the command "npm run serve"
VS Code version: Code - Insiders 1.62.0-insider (f961b92f0faec5c68124ab4d89922d38cf6f513d, 2021-10-28T05:15:59.105Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 x 3403)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.89GB (6.80GB free)

Process Argv
--disable-extensions --crash-reporter-id 39fb7dae-3747-496d-a8ee-f25193692d3c

Screen Reader
no

VM
0%

Extensions disabled
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30291494
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30291487
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
pythonvsuse255:30319630
vscod805cf:30301675
pythonvspyt200:30323110
vsccppwt:30382699
pythonvssor306:30340298
bridge0708:30335490
pygetstartedt2:30353727
bridge0723:30353136
pythonrunftest32:30365365
pythonf5test824:30361779
javagetstartedt:30350119
pythonvspyt187:30365360
pydsgst2:30361790
vsaa593cf:30376535

When I close VS Code, I expect the WSL terminal to terminate normally.  When I launch VS Code again, I expect the WSL terminal to just open.  This is the way it has been working for me for years. Now I am getting this message "Session contents restored from 11/5/2021 at 9:57:47 AM".  I can infer from this that something is different about this current version of VS Code (1.62.0) that is causing the terminal to exit abnormally.  How can I determine if this is the case, or have you introduced this message in the newest version, as I have never seen it before.

@vicel005 the message is a new feature that restored the buffer, you can disable it with terminal.integrated.persistentSessionReviveProcess

This feature is INCREDIBLE slow, it should be disabled by default IMO.
On m1 max 10 core, with only vscode open, it restores 5 EMPTY sessions for like 4-5 seconds. This is the worst feature I've seen for a long time in vscode.

@pavelloz we found and fixed a bug in the feature a week ago, 4 seconds is actually spot on 👉  https://github.com/microsoft/vscode/issues/133964


What makes this work on RPi?

Hi @pegasy, the version you've pushed to Docker works on my RPi4 as well (awesome, btw!), so I was looking to understand what you've done to get the lancachenet stack work on ARM.
When looking at your build.sh it appears that you're not changing much of the underlying stuff, other than modifying proxy_max_temp_file_size in generic and map_hash_bucket_size in monolithic.
Lancache-dns seems to be largely unchanged, yet your version works on RPi, while the  LanCache team's doesn't.
I suspect the magic may happen in the sed lines, but I'm very much a Linux novice and don't have a good grasp on it yet. I figure you're probably mainly changing the Docker tags, but maybe there's more happening?
Or is it working perhaps as you're performing the build directly on the RPi?
So yeah, if you have a bit of time I would appreciate if you could share some insight. :)
Cheers

It's mostly building it on the RPi thats the difference, the docker images that lancachenet/* provide are not built for arm.
sed -e "s/lancachenet\\/$s/pegasy\\/lancachenet_$s/g" -i Dockerfile this only replaces the FROM lancachenet/generic:latest to FROM pegasy/generic:latest in each of the "stages".
sed -e "s/proxy_max_temp_file_size 40960m;/proxy_max_temp_file_size 1920m;/g" -i overlay/etc/nginx/sites-available/generic.conf.d/root/20_cache.conf changes the proxy_max_temp_file_size from 40960m to 1920m, since it seems that's the limit for a 32bit os, so on 64 bit raspbian / ubuntu on a RPi it wouldn't be needed to change this setting I think, once I have some more time to tinker (or get another RPi4) I will try installing a 64 bit os instead and try it out.


Instance spinup hangs terminal window infintely

Describe the bug
Found at the Contrib Day after Drupalcon Lille today by a group of first-time contributors: the process of spinning up the Drupal instance hangs forever, although Drupal runs ok and is accessible via the 8080 link on the Ports tab. New terminal windows can be opended and function normally.
To Reproduce
Use Drupalpod to spin up an instance of the below issue with the config shown.
Expected behavior
The command prompt should return, allowing the terminal to be used for further commands.
Screenshots

Version and configuration information (please complete the following information)

https://www.drupal.org/project/drupal/issues/1671190
Issue branch 11.x
Drupal core version 11.x
Project type Drupal core
[x] Core
[ ] Module
[ ] Theme

Additional context
We are a group of 4 developers.  2 of our machines displayed this problem (repeatably) and 2 had no problem (also repeatably).
Everyone was using Chrome. Version numbers for failing machines are:
Version 118.0.5993.88
Version 117.0.5938.149
Unable to get info from the others as they have had to leave.

This happened repeatedly. The workaround they used was just to open another terminal, which was fine. But we need some more instrumentation to figure out what was going on.


HACKING.rst: Document recommended strategies for profiling

See original issue on GitLab
In GitLab by [Gitlab user @samthursfield] on Jan 25, 2018, 09:59
Make sure it's easy for developers to profile BuildStream.
We should link to documentation for:

Python cProfile
PyFlame

In GitLab by [Gitlab user @samthursfield] on Feb 8, 2018, 17:13
mentioned in commit 85cf4011e070e4620323ae18b7be6c4c5184a551

In GitLab by [Gitlab user @samthursfield] on Feb 8, 2018, 17:15
mentioned in merge request !267

In GitLab by [Gitlab user @jmacarthur] on Feb 15, 2018, 17:36
mentioned in merge request !275

In GitLab by [Gitlab user @samthursfield] on Feb 28, 2018, 15:14
mentioned in commit 88d6c7f186a1bf827c90d1b21125005558bc3d0b

In GitLab by [Gitlab user @samthursfield] on Mar 7, 2018, 09:08
mentioned in commit 141484fc3b17d558d053ccb11de2d24c632f09a6

In GitLab by [Gitlab user @juergbi] on Mar 7, 2018, 09:16
closed


Make CircleCI config consistent

Greetings folks!  In almost all of the other nodejs repos, we've managed to make the CircleCI config look exactly the same.  This is useful, as it lets us update supported nodejs versions, or make broad changes with a single PR to synthtool.
Right now this repo and profiler are (I think...) the only two we haven't moved - largely because they have some custom logic in the config.yaml.
I want to start a discussion the "right way" ™ to do this one.  Should we just change the repo to fall in line with what the others are doing?  Or should we take advantage of the jinja templating we have in synthtool to do something custom?
Adding @kinwa91 @kjin  and @GoogleCloudPlatform/node-team for the discussion :)

I took a cursory look of the config.yml in cloud-trace-node and notice
we’re also depending on several DBMS docker images from Circle. I think it
will be hard to generalize it using our templates in synthtool.
Do we plan to migrate both to Kokoro as well? If so, we should perhaps
focus our efforts to implement the same environment on Kokoro rather than
trying to do more things with CircleCI.
Jonathan
On Wed, Sep 5, 2018 at 11:52 AM Justin Beckwith<EMAIL_ADDRESS>wrote:

Greetings folks! In almost all of the other nodejs repos, we've managed to
make the CircleCI config look exactly the same. This is useful, as it lets
us update supported nodejs versions, or make broad changes with a single PR
to synthtool.
Right now this repo and profiler are (I think...) the only two we haven't
moved - largely because they have some custom logic in the config.yaml.
I want to start a discussion the "right way" ™ to do this one. Should we
just change the repo to fall in line with what the others are doing? Or
should we take advantage of the jinja templating we have in synthtool to do
something custom?
Adding @kinwa91 https://github.com/kinwa91 @kjin
https://github.com/kjin and @GoogleCloudPlatform/node-team
https://github.com/orgs/GoogleCloudPlatform/teams/node-team for the
discussion :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/cloud-trace-nodejs/issues/854,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD0OmF6a4lxs4_MRnIvyHvhumUXLwTSxks5uYB1qgaJpZM4WbfWK
.

--
Jonathan Lui | Developer Programs Engineer |<EMAIL_ADDRESS>| +1
(206) 488-2633

The custom logic is mostly to support (1) caching test fixtures for speed improvements and (2) the extra docker images needed. We can have the same set of jobs as other repos, but the config.yml would still need to be different from others.

IIUC, this repo needs custom config as it is doing significantly more complex tasks than regular libraries.
I'm going to close this out. If this is a mistake, please re-open or add a comment.


Video Enhancement - Collapse video when clicking away

This works with multiple videos on the page and is cross-browser / device tested.
Testing Instructions

Boot up PL
Navigate to http://localhost:3000/pattern-lab/patterns/02-components-video-video--background-video-with-inline-script-and-external-controls/02-components-video-video--background-video-with-inline-script-and-external-controls.html
Click the button to launch video
Click anywhere outside bolt-video to see the video close

Hi @remydenton - I think I have both your items above addressed within an adjustment to the selector. Let me know if you find anything else.


Fix link to gopherwasm

Fix link to gopherwasm
Closes #15
Signed-off-by: Ricardo Seriani<EMAIL_ADDRESS>

Good catch, thanks!


'MAJOR' is not defined Error

Hello,
I have installed gaze2.0  on my windows conda python 3.5 env.
I want to do head position in realtime so I ran ex_pnp_head_pose_estimation_video.py  from master branch I get the error below:
\lib\site-packages\deepgaze\haar_cascade.py", line 138, in _findFrontalFace
    if(MAJOR=='2'): flag = cv2.cv.CV_HAAR_SCALE_IMAGE
NameError: name 'MAJOR' is not defined
[ WARN:0] terminating async callback

is it possible the example is incompatible with ver2?

Hi @m3m3-chan
Thank you for pointing that out. I fixed the bug, there was a line missing at the beginning of the file.
If you checkout again the library and install it should work.

@mpatacchiola  Thanks for your prompt response!


dataset file missing

can you please help me to run this code. Pkl file is missing.

I can not find .json file. Please let me know whereis thhis file?


Landing Page

When running the application, a user needs a starting page to land on, so they can use the navbar to get around the application.  The landing page should be the all events page.

 CELTS #82: Landing Page


Malware, Trojan

BitDefender which is the best protection for your computer, first prevented this download saying it was malware. Then the program was blocked because it is a Trojan. This program is used to steal your account info. DO NOT DOWNLOAD.

If there is one way to code something, then there is another way that isn't a trojan. If you have any respect at all for the community you will either remove this program or rewrite a legitimate version.

Toolbox needs to include dll injection, x86 hooks and other techniques often used by viruses, and that's why it's sometimes detected as a virus by heuristic detection. I wish there was a way to code toolbox without the above techniques.
You can check virustotal scans: dll, launcher. Note how the launcher is detected the most, because it downloads and injects a dll from the internet, which is scary behavior. However the launcher itself is made by very few lines of code that you can easily check.
The code is completely open source, so you're free to look at it and try to find code to steal your account info.
You shouldn't trust me on this, but ask any other toolbox user and you'll find out that toolbox has been around in various forms since 2014 and has never compromised anyone's account.

I respect for the community, and I've been working hard to earn and keep the community's trust for almost 4 years now.

autistic screeching
You are free to read & compile the source code although I doubt you have the capability to do it after you wrote this kind of message.


Missing string interpolation in Runner._prepare_job

When job preparation fails with a missing file, the exception message does not contain the file name. It says "FileNotFoundError: file '%s' does not exist", instead.

Fixed by 78df342a


Revisit Implementations update PRs

We maintain IMPLEMENTATIONS.md which is described as

Below is a list of known tooling that implements the 3.0.0 specification

With 3.1 coming, should we start a new list of implementations as the tools start to add support?
Is the IMPLEMENTATIONS file still useful, with other lists such as https://openapi.tools also being maintained?
There are a number of open Pull Requests to add implementations to the list, that all probably need rebasing at once. I can immediately see:

#2285
#2278 (does need a minor update)
#2206 (approved but not merged)
#2203
#2187
#2182
#1680 (changes requested)
#1668
#1662 (does need a minor update)
#1600 (a tool with "openapi" in the name)
#1506 (includes a tool with "openapi" in the name)

(late additions)

#2323
#2353

Are there some guidelines by which we can evaluate these PRs and either merge or close them? 11 of the current 39 total PRs relate to this one file and are all minor updates that don't affect the spec itself. I'm happy to do the actual wrangling to make a single set of updates if I can get some guidance on this.

Thanks @lornajane - we have finally begun moving from IMPLEMENTATIONS.md to https://tools.openapis.org


MSBuild task has been updated - build log file will be created only when createLogFile = true

Task name: MSBuild
Description: In previous version log file was created in two cases: System.Debug = true, or createLogFile = true, which caused certain issues (see the related ticket). Now log file will created only when createLogFile = true is specified in MSBuild task.
Documentation changes required: N
Added unit tests: N
Attached related issue: https://github.com/microsoft/build-task-team/issues/953
Checklist:

[X] Task version was bumped - please check instruction how to do it
[X] Checked that applied changes work as expected
Links to the test pipelines:
https://dev.azure.com/v-andreym/MSBuild Test Project/_build?definitionId=1
https://dev.azure.com/v-andreym/MSBuild Test Project/_build?definitionId=2

/azp run


Update Roadmap.md

Also add:

Workshops on working in open source
Train the trainer sessions - to open source communities to give them material to provide to colleagues
Presentations on building a culture


As an admin, I don't need to see the Address Verification Endpoint for each service

We can just remove the textbox that we auto-populate, and get the validator to pull the endpoint directly from each class.
We can also deprecate the settings (endpoint and zipcode endpoint).
Also, we shouldn't show in view mode the auth credentials (ID or Token) that don't need to have a value. For example, when in in edit mode, if a user selects Google Geocoding, we hide the Auth Token field. However, we show in in View mode, and also when the user clicks edit (before making any changes to the drop-down).

Included in beta release version 3.36 (Beta 2) and higher

Included in production release version 3.36


Update service-fabric-cluster-manifest.md

Fixed typos.

Hi @alexandair, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

@alexandair : Thanks for your contribution to the Azure documentation! The author, @dsk-2015, has been notified to review your proposed change.

@alexandair  thanks for reviewing the article.  Changes look good to me, I'll sign off for @dsk-2015 who is out right now.  @tysonn go ahead and merge.


Incompatible Library

On running it on the latest Qt libraries, I get this:
Cannot mix incompatible Qt library (version 0x50701) with this library (version 0x50800)
Aborted (core dumped)

Please help.

Strange, I will check it.

Where do you have your copy of Qt from? Via apt-get or different packaging system? Built from source? Downloaded official binary of Qt?

i'm using Arch Linux. so, its the latest Qt from pacman.

It works now with the latest of your repo. But there are warnings and such:
QQmlExpression: Expression qrc:/qml/main.qml:246:36 depends on non-NOTIFYable properties:
    DownloadImage::path
QQmlExpression: Expression qrc:/qml/main.qml:25:30 depends on non-NOTIFYable properties:
    MiscTools::appPath
qrc:/qml/main.qml:275: TypeError: Type error
qrc:/qml/main.qml:199: TypeError: Type error
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
file:///usr/lib/qt/qml/QtQuick/Controls/Private/MenuContentItem.qml:268: TypeError: Cannot call method 'toUpperCase' of undefined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/MenuContentItem.qml:268: TypeError: Cannot call method 'toUpperCase' of undefined
file:///usr/lib/qt/qml/QtQuick/Controls/Private/MenuContentItem.qml:268: TypeError: Cannot call method 'toUpperCase' of undefined

Don't see them affecting the usage of the application itself though. So, yay! It works!


Get Interval precision from system table in Exasol SQL dialect

Situation
Currently the precision of INTERVAL data types is hard-coded in the Exasol SQL dialect. The necessary information is not available via JDBC.
Acceptance Criteria

Ask the JDBC driver developers if it is possible to provide that precision via JDBC.
If yes: ticket for JDBC driver is created
If no: obtain precision from system tables

moved to https://github.com/exasol/exasol-virtual-schema/issues/16


Background locator still update when device is not in motion

The plugin still posts location information even when the device is not in motion, the device is plugged into my computer, but I still receive the speed that is greater than 0, even the longitude and latitude changes on every update.
What should I do to make it stop updating when not in motion?

Hi @KelvinForteta
Thank you for opening an issue.
Use distanceFilter, and set it to a number like 20 meters, so you won't get any update while the device is still;

Ok thanks, I will give it a try.


Fix comp fwd ctf bads

closes #5013

No updated test? :)
It should be an easy few lines hopefully, add a bad to raw.info['bads'] in the right place...?

test added
I want to see if you had become a sloppy reviewer with the years :)

Thanks @agramfort, and congrats on finding some time to write code :)