Google.OrTools v7.6.7691 Issue with VS 2019

Hi there,
I have issues referencing Google.OrTools v7.6.7691 in VS 2019 in project .Net Core 2.1.

How can I resolve this issue?
Thanks,

This issue seems to be due to the missing target file for netstandard2.0 in the or-tools google.ortools.runtime.win-x<IP_ADDRESS>91 NuGet package.

Same probleme here with .Net Core 3.1:
warning NU1701: Package 'Google.OrTools.runtime.win-x64 7.6.7691' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework '.NETCoreApp,Version=v3.1'. This package may not be fully compatible with your project.

NuGet is just warning you that the package is compiled using .net framework but you're using .net core.

Strange, it should contain net45, netstandard2.0 and netstandard2.1 instead...
Need to check why...

I'll try to suppress net45 and the .target file to be sure netstandard2.0/2.1 is working as expected and not silently fallback on the net45 stuff...

Any news on this? Facing the same issue on all releases after 7.5.

Is this just a warning message or potentially affect the performance of CP-SAT?  Got the same message but my program using CP-SAT still runs and the results seem correct.

No, it is a mismatch between the .NET framework we build for (.net 4.5.2,
dotnet core 2.0, dotnet 2.1) and what is specified by default in visual
studio projects.
It should not affect anything.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le jeu. 10 sept. 2020 à 23:06, Gilbert2010<EMAIL_ADDRESS>a
écrit :

Is this just a warning message or potentially affect the performance of
CP-SAT? Got the same message but my program using CP-SAT still runs and the
results seem correct.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1983#issuecomment-690731338,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3OXUDUJM5ZO4254NFLSFE5WLANCNFSM4MSLNICQ
.

That's great. Thanks, Laurent.
On Thu, Sep 10, 2020 at 2:26 PM Laurent Perron<EMAIL_ADDRESS>wrote:

No, it is a mismatch between the .NET framework we build for (.net 4.5.2,
dotnet core 2.0, dotnet 2.1) and what is specified by default in visual
studio projects.
It should not affect anything.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68
53
00
Le jeu. 10 sept. 2020 à 23:06, Gilbert2010<EMAIL_ADDRESS>a
écrit :

Is this just a warning message or potentially affect the performance of
CP-SAT? Got the same message but my program using CP-SAT still runs and
the
results seem correct.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1983#issuecomment-690731338,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ACUPL3OXUDUJM5ZO4254NFLSFE5WLANCNFSM4MSLNICQ
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1983#issuecomment-690740902,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ6CP3OETBPTW2OE6HWYRQDSFE773ANCNFSM4MSLNICQ
.

We get same issue even though when restoring package --runtime linux-x64 is set
warning NU1701: Package 'Google.OrTools.runtime.win-x64 7.8.7959' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework '.NETCoreApp,Version=v3.1'. This package may not be fully compatible with your project.

On the linux platform, we do not build net frameworks, only net core.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le jeu. 17 sept. 2020 à 19:30, Adomas Sutkevičius<EMAIL_ADDRESS>a écrit :

We get same issue even though when restoring package --runtime linux-x64
is set
warning NU1701: Package 'Google.OrTools.runtime.win-x64 7.8.7959' was
restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2,
.NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1,
.NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the
project target framework '.NETCoreApp,Version=v3.1'. This package may not
be fully compatible with your project.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1983#issuecomment-694384859,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3PLTBZAYCDVOA2CRVLSGJBUHANCNFSM4MSLNICQ
.

Why is win-x64 restored if there is package https://www.nuget.org/packages/Google.OrTools.runtime.linux-x64/ Shoudnt this package be restored when using linux-x64 runtime?
And why do we get this warning?

our meta package Google.OrTools depends on three runtime package, and at runtime the correct libraries are loaded.
if you want only one runtime, you can rebuild from source since only runtime will be detected the meta package will only depend on it
see: https://github.com/google/or-tools/blob/a0a56698ba8fd07b7f84aee4fc45d891a8cd9828/ortools/dotnet/Google.OrTools/Google.OrTools.csproj.in#L73-L88
for full explaination, please read:
https://github.com/Mizux/dotnet-native/blob/master/README.md
then
https://github.com/google/or-tools/blob/stable/cmake/doc/dotnet.md

now all packages target netstandard2.0 and netstandard2.1 TFM so application targeting netcoreapp3.1 or netcoreapp2.1 should catch it, unfortunately it seems VIsual Studio do weird things.
Please note we are not using VS but only dev,test,use the dotnet-sdk i.e. the dotnet-cli

We are getting same warning using dotnet cli, inside linux container. It's not VS specific issue.

@Mizux Would it be possible to also add .NET 5 as target framework? It tries to restore with .NET framework if .NET 5 is the target framework currently:
Package 'Google.OrTools.runtime.win-x64 8.1.8487' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework 'net5.0'. This package may not be fully compatible with your project.

This is just a warning and is very likely not problematic at all as the
surface API used by or-tools is minimal.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le lun. 8 févr. 2021 à 11:30, despair3435<EMAIL_ADDRESS>a
écrit :

@Mizux https://github.com/Mizux Would it be possible to also add .NET 5
as target framework? It tries to restore with .NET framework if .NET 5 is
the target framework currently:
Package 'Google.OrTools.runtime.win-x64 8.1.8487' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework 'net5.0'. This package may not be fully compatible with your project.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1983#issuecomment-775043143,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3MZCGQGI5K4WP3CSXLS564NTANCNFSM4MSLNICQ
.

@lperron Yes, everything works as intended, that is not the issue. It is more about getting rid of the warning. As I treat warnings as errors in my project I now have to make an exception for this warning.

https://github.com/google/or-tools/issues/2207#issuecomment-716515367

@Mizux Would it be possible to also add .NET 5 as target framework? It tries to restore with .NET framework if .NET 5 is the target framework currently:
Package 'Google.OrTools.runtime.win-x64 8.1.8487' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework 'net5.0'. This package may not be fully compatible with your project.

FYI: We should provide net5.0 since last release v9.1


Do not fail on unordered dictionaries on python 3.5

These tests would sporadically fail on python 3.5, since the order of a dictionary is undefined.
It's simplest just to skip the assertion on these python versions, it ensures we at least exercise the code path.

Let's just put this in, without it all future PRs will randomly fail CI.


padreati's forth revision

Forth revision. On my host it takes 16 secs.
What I have done:

regular threads, fixed pool
mapped memory segments
better vectorization
station name registry to avoid creating new strings and work with arrays instead of hash maps

Hey @padreati, the output of this solution differs from that of the baseline impl. Could you take a look?

Hey @padreati, I'm gonna close this one for now as I haven't heard back for 2 days and I need to clear the slate a bit (this thing blew up quite a bit ;). Please feel free to re-open once all the tests pass and the output is as expected. Thanks a lot!


try/catch or rethrow needed in background thread (andoird sdk)

This file https://github.com/Azure/azure-mobile-services/blob/master/sdk/android/src/sdk/src/main/java/com/microsoft/windowsazure/mobileservices/table/MobileServiceTableBase.java
Line 365 should be wrapped:
                try{
                	serverEntity = new JsonParser().parse(content).getAsJsonObject();
                }
                catch(JsonSyntaxException | IllegalStateException e){
                	e.printStackTrace();
                }

If not wrapped and exception is thrown, it never bubbles up to the top. In fact, onCompleted(Throwable throwable) is never even called on table operations.

Fixed in #761

@rothschild86 This is fixed in the referenced Pull Request, will be released with the next android SDK release


Addition of Unicode Characters Into the Testing Templates

I added Unicode characters to some choice fields in the testing templates. From this I was able to uncover there was a hardcoded value left from the deprecated tests in the current tests and the email filter did not support unicode characters or long TLDs. Fixes #20.

I love the :heart: .

Looks good. Having unicode tests makes me happy.


hat*tricks

[Enter feedback here]

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

ID: cddd74b1-e0f1-1cae-e92d-c7c2b81e77e3
Version Independent ID: f853e977-81c2-64d6-682e-1e712344cbad
Content: Tutorial: Get started with Docker apps in Visual Studio Code
Content Source: docker/tutorials/docker-tutorial.md
Product: vs-code
GitHub Login: @ucheNkadiCode
Microsoft Alias: uchen

Hey @WilliamAntonRohm would you mind removing me from getting tagged on these issues? I’m no longer at the company

@ucheNkadiCode -- Uche, can you recall who took over for you, that is, to whom should I assign the authorship?

My former manager @spboyer will know! Thank you!


Are column values of 0 ever exposed?

I came across ColumnType::LeftEdge when reading gimli code recently, and it made me wonder how function calls at the start of a line are exposed by addr2line. There's a piece of code that turns 0 into None.

Yes, I think that None for the column means start of line, and we should document that better.
I think that we may not be correctly handling line numbers of 0 though. I'll have to check, but I think this means that none of the location info is valid.

http://dwarfstd.org/doc/DWARF5.pdf table 6.3:

register name
meaning

[...]
[...]

column
An unsigned integer indicating a column number within a source line. Columns are numbered beginning at 1. The value 0 is reserved to indicate that a statement begins at the “left edge” of the line.

[...]
[...]

Right, but is there any useful distinction between those two? Do any other tools make that distinction?

LLDB doesn't show the underline for the current column when it is not specified. I think it does show it for the "left edge".

So yeah, if "not specified" and "left edge" are both possible, then we shouldn't expose "left edge" as None.

I think it does show it for the "left edge".

Can you verify this please.
I'm happy to expose "left edge" if it has meaning, but I looked in llvm, lldb, gcc and gdb, and while I haven't looked exhaustively, I haven't found evidence that there is a difference between "not specified" and "left edge". They all simply use a u16 or u32 for columns, and 0 means not specified.


Enter confirms subtitle track selection

Implementation of https://github.com/killergerbah/asbplayer/issues/378
VideoDataSyncDialog now listens for enter key press when subtitle drop downs aren't in focus.
Can be significantly improved if I can figure out how to shift focus from the side panel to the dialog when it opens on click.
Currently it only submits on enter when the dialog is focused after a click, which I understand is not ideal for what the original issue intended.

Hi @pooky-programs , sorry for taking a long time to look at this. I thought that your changes were still in-progress since the PR is in draft.

@killergerbah no problem, and yeah this is still WIP! I just haven't had the time to sit down and work on it again, sorry for not telling you sooner. I'll be attempting to fix it after July ends.


[Feature] support ratelimit for topic or client ip

Is Your Feature Request Related to a Problem?
Add ratelimit for a special topic or client ip.
mainly for the following reasons:

some topics or clients use too much tps, that will affect other topics or clients.
when a consumer read code data, the pagecache is polluted, and will affect read hot data.
when a consumer read too fast, the downstream services may be unstable.

Describe the Solution You'd Like
add ratelimit support for topic or client ip, which is dynamic configured in broker.
Describe Alternatives You've Considered
not yet
Additional Context
No response

Is this rate limiting feature only effective for consumers?


Webview persistence: Webview won't be reconstructed when reloading more than once

#50696
I have a serializer like this registered:
  vscode.window.registerWebviewPanelSerializer(CatCodingPanel.viewType, {
    deserializeWebviewPanel(webviewPanel: vscode.WebviewPanel, state: any) {
      console.log(state)
      webviewPanel.webview.html = '
hi
'
      return Promise.resolve()
    }
  })

I believe this was fixed by 6e81adc78f03e587fdcd1846e0fb534977edc052


how can I install/use only Add to cart functionality of Saleor in my project.

Hi,
I have created a Project in django, in that I created an app. I want to insall Shopping cart / Add to cart plug in of Saleor in my project.
I am facing difficulty in installing ONLY Add to cart functionality of saleor.
For eg. I do install a third party package by pip install package name, and add the app/package name to INSTALLED APPS in settings.py file.
my question is, how can I just install Add to cart and use it in my project? Or  Can I customize Saleor's functinality or only front end can be customized?
PS: I am new to Django and Saleor.

Hey, I suggest you to clone Saleor and cut off or adapt parts you don't need. This project is not designed to be installed via PIP.

Hi,
Thanks for your reply. But I still have a query.
Like you said, if I want to use only "cart" app of Saleor, do I need to delete other folders from the Saleor?
Or, Can I inherit, like import cart from Saleor something like this, in my existing project?
I found that these apps have dependency on each other.

Ideal way to do it would be to read and understand how Saleor cart works, and write you own cart as per your requirements.
Apps in the Saleor project are not designed to be independent of each other. So even if you are deleting some other folder you have make sure that cart is not dependent on them. If it is then you will have to keep them or provide your own alternatives.
for example:
cart app depends on product app, for the add to cart functionalities. you will have to patch it with your own product app or what ever it is you are adding to cart..

I'll close this as I think enough information was provided. Thank you @askamist! ✨


feat: v20 evonodes payment adjustment

Issue being fixed or feature implemented
Since v19, Evo nodes are paid 4x blocks in a row.
This needs to be reverted when v20 activates.
What was done?
Starting from v20 activation, Evo nodes are paid one block in a row (like regular masternodes).
In addition, nConsecutivePayments isn't incremented anymore for Evo nodes.
How Has This Been Tested?
feature_llmq_hpmn.py with v20 activation.
Breaking Changes
no
Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation
[x] I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

@ogabrielides check this one: https://github.com/dashpay/dash/pull/5342/commits/a7c3840678c0e59bdb834ca172151e2adc97f629 (part of PR 5342)

@ogabrielides check this one: a7c3840 (part of PR 5342)
Seems as missing changes inside CDeterministicMNManager::BuildNewListFromBlock
Also CDeterministicMNList::GetProjectedMNPayees [used by rpc].

@knst Thanks!
Implemented it.

@knst You suggested change make sense. Included your commit.

Probably missing changes in test/functional/rpc_blockchain.py 1644bc3#diff-c1987c24fa3e5c788d16de5359500a19a1fea4f379e4288d076cf92be89541dc

Indeed !


Modify the comment of Makefile

docs/sources/contributing/devenvironment.md   can not be find in the project. I will delete it.
Signed-off-by: Yanqiang Miao<EMAIL_ADDRESS>

Very sorry!  I made a mistake.

Very sorry!  I made a mistake.

LGTM

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix-makefile-comment-err" git@github.com:miaoyq/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

please squash your commits and sign them

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix-makefile-comment-err" git@github.com:miaoyq/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~3
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix-makefile-comment-err" git@github.com:miaoyq/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~8
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Squashed. PTAL @duglin Thanks a lot!

LGTM
ping @vdemeester for the merge

LGTM


Add tests to Rna Transcription for partially invalid input.

The current test suite checks for an ArgumentError on completely invalid input, but not partially invalid input. For example, this solution passes all of the existing tests but accepts input that has a mix of valid and invalid characters:
class Complement

  DNA_REGEX = /[CGTA]/
  RNA_REGEX = /[CGAU]/

  KEYS = {
    'C' => 'G',
    'G' => 'C',
    'T' => 'A',
    'A' => 'U'
  }

  def self.of_dna(dna)
    raise ArgumentError unless dna.match(DNA_REGEX)
    dna.gsub(DNA_REGEX, KEYS)
  end

  def self.of_rna(rna)
    raise ArgumentError unless rna.match(RNA_REGEX)
    rna.gsub(RNA_REGEX, KEYS.invert)
  end

end

These additional tests might discourage novices from simply checking for the arguments present in the tests.

I like this change. @kotp what do you think?
Would you mind amending the commit to have the name of the exercise in it? E.g.
rna-transcription: add tests for partially invalid inputs

I like it, plus a misnamed test method was found and corrected as well.
Test version needs to be added.

I didn't even notice the mis-named test. That test would never actually get run! Good find.
For the test version, check out how it's done here: https://github.com/exercism/xruby/blob/bb819ff5f5a3dff8b135b44228d9549e65c2f880/acronym/acronym_test.rb#L26-L30

@kytrinyx Should I add a .version file as well or just bump the version number in the test and example files?

Don't bother with the .version file--that's used by generators to generate the new test suite correctly. Just bumping the number should be fine.

Ok version bumped to 2.

Thanks!


[WIP] Add support for globbing with multiple sub-directories

This adds support for more advanced globbing via pattern.
Namely it allows us to use ** wildcard for finding within deep subdirectories.
Example use case to find any *.info.yml file in all sub-directories and validate a key/value pair:
    - name: '[FILE] Detect module files in theme folder'
      pattern: 'themes/**/*.info.yml'
      ignore-missing: true
      path: .
      values:
        - key: type
          value: theme

Existing tests need resolving, and new ones added.


Added File Extension Check

Added file extension verification before uploading files Users will not be allowed to upload any other file types except proposed in this PR. This will help to filter uploaded files and reducing server load.

I don’t think this PR is sufficient or even necessary.

We support more than those file extensions and we use meta data sniffing instead, because extensions can be wrong, content cannot.
How does this reduce server load?

@bhutkeyur Files aren't uploaded anywhere. All processing is done locally on the user's machine.
See https://github.com/GoogleChromeLabs/squoosh/blob/dev/src/components/compress/index.tsx#L415 where we handle new files.


Webp not supported

This is not soported.
In line 131
        // Get image info
        $info = getimagesize($file);
        if($info === false) {
            throw new \Exception("Invalid image file: $file", self::ERR_INVALID_IMAGE);
        }
        $this->mimeType = $info['mime'];

This throw false, because getimagesize dont support webp https://www.php.net/manual/es/function.getimagesize.php
With WEBP images, show false Exception.
I tested in PHP 7.0 and 7.3
#173

webp was added to getimagesize() in 7.1.0 per the PHP docs. It isn't expected to work in 7.0 but should be working in 7.3 if your version of PHP/gd has webp enabled.


Submitted policy is over max allowed size

Topshelf.Hosts.ConsoleRunHost Error: 0 : An exception occurred, Amazon.SQS.Amazo
nSQSException: Submitted policy is over max allowed size. ---> Amazon.Runtime.In
ternal.HttpErrorResponseException: The remote server returned an error: (403) Fo
rbidden. ---> System.Net.WebException: The remote server returned an error: (403
) Forbidden.
   at System.Net.HttpWebRequest.GetResponse()
   at Amazon.Runtime.Internal.HttpRequest.GetResponse() in d:\Jenkins\jobs\build
-sdkandtools-release\workspace\sdk\src\AWSSDK_DotNet35\Amazon.Runtime\Pipeline\H
ttpHandler\HttpWebRequestFactory.cs:line 106
   --- End of inner exception stack trace ---
   at Amazon.Runtime.Internal.HttpRequest.GetResponse() in d:\Jenkins\jobs\build
-sdkandtools-release\workspace\sdk\src\AWSSDK_DotNet35\Amazon.Runtime\Pipeline\H
ttpHandler\HttpWebRequestFactory.cs:line 114
   at Amazon.Runtime.Internal.HttpHandler`1.InvokeSync(IExecutionContext executi
onContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK
_DotNet35\Amazon.Runtime\Pipeline\HttpHandler\HttpHandler.cs:line 84
   at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 55
   at Amazon.Runtime.Internal.Unmarshaller.InvokeSync(IExecutionContext executio
nContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_
DotNet35\Amazon.Runtime\Pipeline\Handlers\Unmarshaller.cs:line 47
   at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 55
   at Amazon.SQS.Internal.ValidationResponseHandler.InvokeSync(IExecutionContext
 executionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\sr
c\AWSSDK_DotNet35\Amazon.SQS\Internal\ValidationResponseHandler.cs:line 25
   at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 55
   at Amazon.Runtime.Internal.ErrorHandler.InvokeSync(IExecutionContext executio
nContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_
DotNet35\Amazon.Runtime\Pipeline\ErrorHandler\ErrorHandler.cs:line 70
   --- End of inner exception stack trace ---
   at Amazon.Runtime.Internal.HttpErrorResponseExceptionHandler.HandleException(
IExecutionContext executionContext, HttpErrorResponseException exception) in d:\
Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_DotNet35\Amazon.
Runtime\Pipeline\ErrorHandler\HttpErrorResponseExceptionHandler.cs:line 99
   at Amazon.Runtime.Internal.ExceptionHandler`1.Handle(IExecutionContext execut
ionContext, Exception exception) in d:\Jenkins\jobs\build-sdkandtools-release\wo
rkspace\sdk\src\AWSSDK_DotNet35\Amazon.Runtime\Pipeline\ErrorHandler\ExceptionHa
ndler.cs:line 38
   at Amazon.Runtime.Internal.ErrorHandler.ProcessException(IExecutionContext ex
ecutionContext, Exception exception) in d:\Jenkins\jobs\build-sdkandtools-releas
e\workspace\sdk\src\AWSSDK_DotNet35\Amazon.Runtime\Pipeline\ErrorHandler\ErrorHa
ndler.cs:line 202
   at Amazon.Runtime.Internal.ErrorHandler.InvokeSync(IExecutionContext executio
nContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_
DotNet35\Amazon.Runtime\Pipeline\ErrorHandler\ErrorHandler.cs:line 76
   at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 55
   at Amazon.Runtime.Internal.CallbackHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\Handlers\CallbackHandler.cs:line 45
   at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 55
   at Amazon.Runtime.Internal.Signer.InvokeSync(IExecutionContext executionConte
xt) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_DotNet
35\Amazon.Runtime\Pipeline\Handlers\Signer.cs:line 38
   at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 55
   at Amazon.Runtime.Internal.CredentialsRetriever.InvokeSync(IExecutionContext
executionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src
\AWSSDK_DotNet35\Amazon.Runtime\Pipeline\Handlers\CredentialsRetriever.cs:line 7
2
   at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 55
   at Amazon.Runtime.Internal.RetryHandler.InvokeSync(IExecutionContext executio
nContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_
DotNet35\Amazon.Runtime\Pipeline\RetryHandler\RetryHandler.cs:line 84
   at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 55
   at Amazon.Runtime.Internal.CallbackHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\Handlers\CallbackHandler.cs:line 45
   at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 55
   at Amazon.Runtime.Internal.EndpointResolver.InvokeSync(IExecutionContext exec
utionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWS
SDK_DotNet35\Amazon.Runtime\Pipeline\Handlers\EndpointResolver.cs:line 34
   at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 55
   at Amazon.SQS.Internal.ProcessRequestHandler.InvokeSync(IExecutionContext exe
cutionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AW
SSDK_DotNet35\Amazon.SQS\Internal\ProcessRequestHandler.cs:line 23
   at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 55
   at Amazon.Runtime.Internal.Marshaller.InvokeSync(IExecutionContext executionC
ontext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_Do
tNet35\Amazon.Runtime\Pipeline\Handlers\Marshaller.cs:line 37
   at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 55
   at Amazon.Runtime.Internal.CallbackHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\Handlers\CallbackHandler.cs:line 45
   at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 55
   at Amazon.Runtime.Internal.ErrorCallbackHandler.InvokeSync(IExecutionContext
executionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src
\AWSSDK_DotNet35\Amazon.Runtime\Pipeline\Handlers\ErrorCallbackHandler.cs:line 4
4
   at Amazon.Runtime.Internal.PipelineHandler.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\PipelineHandler.cs:line 55
   at Amazon.Runtime.Internal.MetricsHandler.InvokeSync(IExecutionContext execut
ionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSD
K_DotNet35\Amazon.Runtime\Pipeline\Handlers\MetricsHandler.cs:line 40
   at Amazon.Runtime.Internal.RuntimePipeline.InvokeSync(IExecutionContext execu
tionContext) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSS
DK_DotNet35\Amazon.Runtime\Pipeline\RuntimePipeline.cs:line 135
   at Amazon.Runtime.AmazonServiceClient.Invoke[TRequest,TResponse](TRequest req
uest, IMarshaller`2 marshaller, ResponseUnmarshaller unmarshaller) in d:\Jenkins
\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_DotNet35\Amazon.Runtime
\AmazonServiceClient.cs:line 117
   at Amazon.SQS.AmazonSQSClient.SetQueueAttributes(SetQueueAttributesRequest re
quest) in d:\Jenkins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_Dot
Net45\Amazon.SQS\AmazonSQSClient.cs:line 2000
   at Amazon.SimpleNotificationService.AmazonSimpleNotificationServiceClient.Sub
scribeQueue(String topicArn, IAmazonSQS sqsClient, String sqsQueueUrl) in d:\Jen
kins\jobs\build-sdkandtools-release\workspace\sdk\src\AWSSDK_DotNet35\Amazon.Sim
pleNotificationService\AmazonSimpleNotificationServiceClient.Extensions.cs:line
99
   at JustSaying.AwsTools.SnsTopicBase.Subscribe(IAmazonSQS amazonSQSClient, Sqs
QueueBase queue)
   at JustSaying.AwsTools.QueueCreation.AmazonQueueCreator.EnsureQueueIsSubscrib
edToTopic(String region, SnsTopicByName eventTopic, SqsQueueByName queue)
   at JustSaying.AwsTools.QueueCreation.AmazonQueueCreator.EnsureTopicExistsWith
QueueSubscribed(String region, IMessageSerialisationRegister serialisationRegist
er, SqsReadConfiguration queueConfig)
   at JustSaying.JustSayingFluently.TopicHandler[T]()
   at JustSaying.JustSayingFluently.WithMessageHandler[T](IHandlerResolver handl
erResolver)

This is caused by reaching the limit for SQS policy. Have not spent time to dig into this issue more and think of a proper solution for addressing this.  Raising this just to have this for the record.

Hey @dariusdamalakas - I believe this issue was fixed a while back. Let me know if this is still an issue in the latest version.

@payman81 , do you remember what the root cause / fix?
I've updated locally to latest code (master branch), and can still reproduce it. The root
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "deff9abfac2f4ea6b8f9f79d006993bc",
      "Effect": "Allow",
      "Principal": {
        "AWS": "*"
      },
      "Action": "sqs:SendMessage",
      "Resource": "arn:aws:sqs:eu-west-1:xxxxxxxxxx:dev-dariouso-referencetemplates",
      "Condition": {
        "ArnLike": {
          "aws:SourceArn": "arn:aws:sns:eu-west-1:xxxxxxxxxx:dev-dariouso-eventhappened6"
        }
      }
    },
    {
      "Sid": "535a6b9f9f4b442ba33eb2711ed17dcf",
      "Effect": "Allow",
      "Principal": {
        "AWS": "*"
      },
      "Action": "sqs:SendMessage",
      "Resource": "arn:aws:sqs:eu-west-1:xxxxxxxxxx:dev-dariouso-referencetemplates",
      "Condition": {
        "ArnLike": {
          "aws:SourceArn": "arn:aws:sns:eu-west-1:xxxxxxxxxx:dev-dariouso-eventhappened7"
        }
      }
    },

The pattern here is that each topic gets a condition. Looking at how to overcome this. It's the AWS C# SDK which is generating these policies. I don't see currently an easy way to override this.

The policy per topic is overkill. This is what I thought was fixed. I'll pick this up and provide a fix then.

@payman81 , ok, cool. I've just had a quick look, and I don't see an easy solution here.
On my local machine, i've hooked up extra statements to override the policy that AWS is building for us by default. I've added that code to SnsTopicBase.Subscribe
Not sure how to easily pass in a func here to expose the policy for the library consumer though, if you know what the best option here let me know.  The only thing I can think of is a major refactor to the initialization pipeline, which is an overkill for this issue.  We could take advantage of SubscribeQueueToTopics operation in AWS3 SDK, but we need to defer initializtion, i.e. build-up what are the topics/queues, and then create them in batches where possible. This is out of scope of this issue.

P.s. to reproduce you'll need around 15 topics subscribed to single queue.

Norm Jonhson replied with suggestion to use IAmazonSQS.SetAttributes and IAmazonSimpleNoticationService.Subscribe. This will allows us to control queue policy.

@payman81 @AnthonySteele, @stuart-lang  i start working on this. Thinking of adapting IVerifyAmazonQueues to allow to hook in into queue/topic creation. Potentially reworking how SnsTopicBase and SqsQueueBase because that is where subscription logic is.

@dariusdamalakas I'm trying something simpler to see if it works. I'd explicitly set the policy on queue creation with a wildcard. I think that would prevent individual policy per topic when you call 'Subscribe' later on.
This way all the change will be contained within SqsByName.

@payman81 yup, that would work, however, that means from the very strict policy we'd go to allow anything policy.

This change here will produce the following
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "804e930b16e24e26b302128a14b2ee10",
      "Effect": "Allow",
      "Principal": {
        "AWS": "*"
      },
      "Action": "sqs:SendMessage",
      "Resource": "arn:aws:sqs:eu-west-1:507204202721:issue211-2"
    }
  ]
}

I agree this is too relaxed. But we can easily add a condition to limit subscriptions to this account/region only. I think this level of policy is acceptable.

@payman81 yeah, at least a restriction to account please. I was thinking about adding restriction like this: arn:aws:sns:eu-west-1:<accountId>:<environment>-*. Essentially this would allow only topics from environment to subscribe to queues, such as dev, tst, prd, etc.

Have a look at this spike here
This will produce the following policy.
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "527e6bf619ff45c7b068b91fd92d5adc",
      "Effect": "Allow",
      "Principal": {
        "AWS": "*"
      },
      "Action": "sqs:SendMessage",
      "Resource": "arn:aws:sqs:eu-west-1:507204202721:issue211-2",
      "Condition": {
        "ArnLike": {
          "aws:SourceArn": "arn:aws:sns:eu-west-1:507204202721:*"
        }
      }
    }
  ]
}

@payman81  looks good!  simple, and does the job. Still does not allow to customize policies, but we can say that is good enough for now. Do you need any help to finish this up?

submitted #216 to fix this. Will let you know once it's merged.


Improvement to money.exchange.ExchangeRates.install API.

Extend money.exchange.ExchangeRates.install to accept a class or instance in addition to the currently supported dotted Python path string.  This makes configuration at runtime a little easier in some cases.

Sorry for the delay, getting back to you asap.

Thank you!
On Mon, Mar 16, 2015 at 9:02 AM, Carlos Palol<EMAIL_ADDRESS>wrote:

Merged #13 https://github.com/carlospalol/money/pull/13.
—
Reply to this email directly or view it on GitHub
https://github.com/carlospalol/money/pull/13#event-255466314.

Thank you for contributing. I'll make a couple of releases soon.


Fixed encoding issues

Let's say you have a "ñ" in your Minecraft password (which Mojang allows you to do), when you put the email and password in the accounts.txt file, you will probably get a "[error] failed to auth<EMAIL_ADDRESS>because the encoding is different
For example, in my windows 10 machine with python 3.7 the default encoding for open() is set to "cp1252" but I previously opened my file with utf-8 in notepad and python still open it with cp1252, that means if I write "email@domain.com:passwordñ" in accounts.txt in notepad with utf-8 encoding, the password would be "passwordÃ±" because the default encoding (cp1252) is used in python.

Didn't know this, thanks!


Upgrade to 1.19

I think the MobSpawnS2CPacket got removed, maybe merged with the Entity spawn one?
It seems like you used both for different things, so not too sure how to handle that.
But it compiles and the way it's currently configured works for me.
But maybe this is of use to you!

Tyvm! :)


exception when Loop input "M" "cond" are empty strings

Describe the bug
In ONNX Loop spec, "M" and "cond" input can be empty strings, if we don't need them.
Running the Loop, we will have following error:

RuntimeError: [ONNXRuntimeError] : 10 : INVALID_GRAPH : Node:Loop__5 Node (Loop__5)'s input 1 is marked single but has an empty string in the graph

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
ONNX Runtime installed from (source or binary): source
ONNX Runtime version: master
Python version: 3.5
GCC/Compiler version (if compiling from source): VS2017
CUDA/cuDNN version:
GPU model and memory:

To Reproduce
Define a Loop having empty strings for M or cond input, run it.
Expected behavior
should run without errors.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Happy new year!


Allow shipping containers from macOS

Please describe your use case how you'd like to use containers from macOS.

I'm new to devenv (and nix for that matter), but this seems like an enticing way to manage dependencies and the like! 🙂
I'm usually on MacOS, so I'm happy to test (and potentially dev over the next few weeks), though given my ignorance around nix, I'll probably have myriad questions. 😅
Anywho – I just tried using containers on MacOS (to see what happens), and I received the following as output:
$ devenv container shell
~/.nix-profile/bin/devenv: line 110: declare: -A: invalid option
declare: usage: declare [-afFirtx] [-p] [name[=value] ...]

Based on this SO answer, it seems that declare -A requires Bash 4+, but MacOS ships with Bash 3. However, MacOS now uses zsh by default. From my limited understanding, zsh has associative arrays – though I've read that they're "... implemented differently ..." than associative arrays in bash (no idea how).
Looking at the "offending line", the call to /nix/store/m76vd4ma4455s1rsqm8kq8ps5vhinvmj-docopts-0.6.4-with-no-mangle-double-dash/bin/docopts -A subcommand -h "$help" : "$@" is where the problem arises since docopts targets Bash 4+, though docopts enumerates how to achieve Bash <4 compatibility. To me, this points to a few routes forward for MacOS support:

Implement some dynamic checking to permit associative arrays (some sort of switch on MacOS that removes -A and implements the other compatibility changes)
Install bash 4+ via nix? (I have no idea if this is possible.)
Use something other than docopts.

Update: I installed bash via nix-env --install bash (which showed up as 5.2-p15 for me). After installing bash, I was able to get to container "compilation" (not sure what to call it), once I added the nix2container bits to my devenv.yaml.
At the moment, I'm now "stuck" here:
$ devenv container devcontainers --docker-run
/nix/store/0ggk9l9spp3gfcl995idcwf3pbb3zhyg-image-devcontainers.json

Copying container /nix/store/0ggk9l9spp3gfcl995idcwf3pbb3zhyg-image-devcontainers.json to docker-daemon:devcontainers:latest

Getting image source signatures
Copying blob 606ff57294bb done
FATA[0004] writing blob: io: read/write on closed pipe

Even when leaving containers."devcontainers"... unspecified (as I did prior to this), I get the same errors. I'm not too certain how to proceed with debugging from here, so some pointers would definitely be helpful! 🙂
For reference, this is my devenv.nix and devenv.yaml:

 devenv.nix
{ pkgs, config, ... }:

{
  name = "devcontainers";
  devcontainer.enable = true;

  processes = {
    ping.exec = "ping <IP_ADDRESS>";
  };

  containers."devcontainers".name = "devcontainers";
  containers."devcontainers".startupCommand = config.processes.ping.exec;

  # https://github.com/cachix/devenv/blob/main/examples/starship/devenv.nix
  starship.enable = true;
  starship.config.enable = true;

  languages.javascript.enable = true;
  languages.typescript.enable = true;
  languages.go.enable = true;

  # https://devenv.sh/packages/
  packages = [
    pkgs.zsh
    pkgs.git
  ];
}

 devenv.yaml
inputs:
  nixpkgs:
    url: github:NixOS/nixpkgs/nixpkgs-unstable
  nix2container:
    url: github:nlewo/nix2container
    inputs:
      nixpkgs:
        follows: nixpkgs
  mk-shell-bin:
    url: github:rrbutani/nix-mk-shell-bin

The main issue is that the container needs to be built on a Linux machine.

Please describe your use case how you'd like to use containers from macOS.

Hum, I keep having trouble with direnv + VSCode, so I'd like to try devcontainer with devenv. Unfortunately I'm on a macOS machine so I can't build the container.

I would like to be able to build images on MacOS for aarch64-linux and x86_64-linux for:

Build images for local dev (cross-platform env Mac|WSL2|Linux)
Build images for remote dev (SSH, Github Codespaces, GitPod)
Build images for staging and production

Can we do all this within a Linux container on Mac for Docker already? Just curious.
Looking forward to something like this!

Yeah, you can do it in a container or WSL2.
We could support cross-compiling, but that would limit to only packages that support cross-compilation (which is still a lot).

Good to know, thanks.
Cross-compiling would be important for my case since I'm on Apple Silicon, but most cloud/server CPUs are x86_64.

Yeah, you can do it in a container

Are there any instructions for how to do this?
I'd like to build a devcontainer for use with VS Code on a Mac.
devenv container shell --docker-run does not work for me. Though I get a different error to what @jmuchovej posted. I get:
❯ devenv container shell --docker-run
/nix/store/6mil5af39zlgxaplzpqnjfl80r89qzfj-image-zap-devenv-shell.json

Copying container /nix/store/6mil5af39zlgxaplzpqnjfl80r89qzfj-image-zap-devenv-shell.json to docker-daemon:zap-devenv-shell:latest

Getting image source signatures
Copying blob 85f15165725a done
Copying config 3910136d57 done
Writing manifest to image destination
Storing signatures
exec /nix/store/cmybmvzb77znaay66f0lqb2s20rd7zim-entrypoint: exec format error

If I try to open the devenv in VC Code and start a VS Code terminal with direnv, I get:
direnv: loading /workspaces/workspace/.envrc
direnv: loading https://raw.githubusercontent.com/cachix/devenv/d1f7b48e35e6dee421cfd0f51481d17f77586997/direnvrc (sha256-YBzqskFZxmNb3kYVoKD9ZixoPXJh1C9ZvTLGFRkauZ0=)
direnv: using devenv
direnv: .envrc changed, reloading
Building shell ...
evaluating derivation 'git+file:///workspaces/workspace#devShells.x86_64-linux.default'direnv: ([/nix/store/xwsp5wk6141wf5zskld99s1c36wmh4z7-direnv-2.32.2/bin/direnv export bash]) is taking a while to execute. Use CTRL-C to give up.
error:
       … while setting up the build environment

       error: unable to load seccomp BPF program: Invalid argument
./.envrc:1389: pop_var_context: head of shell_variables not a function context
environment:1: pop_var_context: head of shell_variables not a function context

If I enable devcontainers (devcontainer.enable = true;) and try to open the devenv in VC Code by opening the workspace with devcontainer.json, I get a similar error on building when VSCode builds the devcontainer:
error:
       … while setting up the build environment

       error: unable to load seccomp BPF program: Invalid argument
[338769 ms] updateContentCommand failed with exit code 1. Skipping any further user-provided commands.
[338773 ms] Error: Command failed: /bin/sh -c devenv ci
[338773 ms]     at IN (/Users/tom/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js:1733:130)
[338773 ms]     at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
[338773 ms]     at async E1 (/Users/tom/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js:1725:4370)
[338773 ms]     at async p1 (/Users/tom/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js:1725:3727)
[338773 ms]     at async g1 (/Users/tom/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js:1725:2815)
[338774 ms]     at async Bae (/Users/tom/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js:2092:29064)
[338774 ms]     at async Sae (/Users/tom/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js:2092:26423)
[338775 ms] Exit code 1
[338776 ms] Command failed: /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) --ms-enable-electron-run-as-node /Users/tom/.vscode/extensions/ms-vscode-remote.remote-containers-0.292.0/dist/spec-node/devContainersSpecCLI.js run-user-commands --user-data-folder /Users/tom/Library/Application Support/Code/User/globalStorage/ms-vscode-remote.remote-containers/data --container-session-data-folder /tmp/devcontainers-57901f0a-990a-49a9-a5b1-3e15b1f3f1311683630384316 --workspace-folder /Users/tom/workspace --id-label devcontainer.local_folder=/Users/tom/workspace --id-label devcontainer.config_file=/Users/tom/workspace/.devcontainer.json --container-id cb7d09269e077bd750d53888e8c9762766ad36f8532e38d18bb0a43103bf1f76 --log-level debug --log-format json --config /Users/tom/workspace/.devcontainer.json --default-user-env-probe loginInteractiveShell --skip-non-blocking-commands true --prebuild false --stop-for-personalization true --remote-env REMOTE_CONTAINERS_IPC=/tmp/vscode-remote-containers-ipc-29878c87-f6bd-4f8e-bfba-1651c1fb1c44.sock --remote-env SSH_AUTH_SOCK=/tmp/vscode-ssh-auth-29878c87-f6bd-4f8e-bfba-1651c1fb1c44.sock --remote-env REMOTE_CONTAINERS=true --mount-workspace-git-root true --terminal-columns 182 --terminal-rows 29 --dotfiles-target-path ~/dotfiles

Please describe your use case how you'd like to use containers from macOS.

Would like to see if it could replace a local + docker-compose for a more performant native dev experience. Example use case:

Run a rails/django/node/{etc} service locally that has service dependencies like Redis and Postgres.
Be able to build and execute tests in a container like-for-like with a prod image that would be used for deployment. The concern I see with the local only + local services is if you push code your remote ci/cd and deployed image could have issues you don't see running locally.
Run and execute the local service directly in a container (with the accepted performance hit) to replicate the same architecture as a deployed image. This saves pulling a built image down from your ci/cd stack to debug issues.

My alternative at the moment is running process dependencies in docker containers and managing them via docker-compose, or even the local service at a performance impact due to the docker or podman VM layer. But it gives you more confidence avoiding the works on my machine issue.
tl;dr local dev with service/process dependencies that we can test in the same "prod" deployment environment without the macOS container VM overhead.
If this is possible somehow already would appreciate someone sharing a walkthrough!

The easiest way to achieve this is using linux builder on macos: https://nixos.org/manual/nixpkgs/unstable/#sec-darwin-builder

Please describe your use case how you'd like to use containers from macOS.

Would like to see if it could replace a local + docker-compose for a more performant native dev experience. Example use case:

Run a rails/django/node/{etc} service locally that has service dependencies like Redis and Postgres.
Be able to build and execute tests in a container like-for-like with a prod image that would be used for deployment. The concern I see with the local only + local services is if you push code your remote ci/cd and deployed image could have issues you don't see running locally.
Run and execute the local service directly in a container (with the accepted performance hit) to replicate the same architecture as a deployed image. This saves pulling a built image down from your ci/cd stack to debug issues.

My alternative at the moment is running process dependencies in docker containers and managing them via docker-compose, or even the local service at a performance impact due to the docker or podman VM layer. But it gives you more confidence avoiding the works on my machine issue.
tl;dr local dev with service/process dependencies that we can test in the same "prod" deployment environment without the macOS container VM overhead.
If this is possible somehow already would appreciate someone sharing a walkthrough!

That's currently possible using https://devenv.sh/services/ and https://devenv.sh/containers.

I'd be great if someone can sketch out how to setup a linux builder and then run devenv --system aarch64-linux container build project.

I'd like to test if containers work at all locally on my Apple Sillicon, before handing things over to CI and prod. It's fine if the resulting containers are ARM linux ones. The docs say that:

To be able to generate containers on macOS, you will need to use a remote Linux builder.
The easiest ways to do so are: - Set the remote builder up using Nix. - Use the nix-darwin linux-builder module.

So I followed the former link's instructions and have a linux builder running, and I adapted my /etc/nix/nix.conf and
/etc/ssh/ssh_config.d/100-linux-builder.conf accordlingly
<<< Welcome to NixOS 24.05pre-git (aarch64) - ttyAMA0 >>>

Now when I run devenv container build processes I would expect the linux builder to produce an arm linux container with all the processes inside, instead it errors out:
λ devenv container build processes
Error:   × Containers are not supported on macOS yet: https://github.com/cachix/devenv/issues/430

λ devenv --system aarch64-linux container build processes
Error:   × Containers are not supported on macOS yet: https://github.com/cachix/devenv/issues/430

How would I get passed this check so the linux-builder is used?

Bumping this, is there any update on this issue? I too would also like to be able to use this feature - I use Nix in all my (and work's) infra and not having to use WSL thru a VM just to be able to work on this would be indispensible.

@domenkozar I have a linux builder on my mac, but even with devenv --system aarch64-linux container build project I get Error:   × Containers are not supported on macOS yet: https://github.com/cachix/devenv/issues/430


Error when bulding with Hugo 0.48

Building my site using hugo-bootstrap-premiums works fine with Hugo 0.47, but with Hugo 0.48 I get the following error:
Error while rendering "taxonomy" in "": template: _default/list.html:7:31: executing "_default/list.html" at <.Paginator.Pages>: undefined variable: $index
Any ideas why that might be?

@h0bbel it's due to the fact that Hugo has moved to Go 1.11 since 0.48 :
https://discourse.gohugo.io/t/range-offset-variable-undefined-in-0-48/14427/4

I am sure that is correct, but is there a way to fix the theme? I've been looking at it, but I'm clueless when it comes to Go, so I don't know how to rectify it.

Yep, i'll give it a go this week.

@h0bbel i've fixed it in my fork and i've created a PR ( #49  ).
Adrian

Awesome, thanks Adrian — I made the same changes in my copy, and now I'm up and running with Hugo 0.49. Thanks again!

Just got the same error. Checking your PR.

Merged it.


[Settings Sync] Rewriting syncing.json every few seconds is bad for SSDs

Issue Type: Performance Issue
When Settings Sync is turned on, VS Code rewrites file %APPDATA%\Code\User\syncing.json every few seconds. This is bad for SSD longevity, since it contributes to flash media wear.
During a 35-minute trace, I observed this file being written nearly 200 times.
The rewriting seems to be largely gratuitious—the same unchanged data is being written over and over again.
Steps to reproduce:

Turn on Settings Sync.
Using Process Monitor (procmon) or a similar utility, run a trace for WriteFile operations filtered by process and/or path.
Observe file %APPDATA%\Code\User\syncing.json being rewritten every few seconds.

VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.19042

I do not think VS Code is performing this operation. Can you please disable your extensions and try?


Your gif indicators should be with transparent background, or with possibility to change him.

Your gif indicators should be with transparent background, or with possibility to change him and also you should add possibility to change animation color

I freaking wish I could use this but because of this problem I am f~~~ed!!!!!.!.!


Allow the use of uppercase and lowercase letters for all namings

In the PFDL, only lowercase letters (e.g. fields in structures) or only uppercase letters (e.g. service names) are allowed as the first letter for some components. For users it is sometimes very difficult to understand the error, because the error message, depending on the content of the task can be quite large. The following error message is a result of writing ProductionTask instead of productionTask
mismatched input 'ProductionTask' expecting STARTS_WITH_LOWER_C_STR
File ./PFDL_Examples/test.pfdl, in line 16:5
extraneous input '{' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 20:12
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 29:13
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 31:34
extraneous input 'Model_generation' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 33:4
extraneous input 'Transport' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 34:4
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 36:14
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 38:34
extraneous input 'Disassemble_gear' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 40:4
extraneous input '{' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 43:12
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 45:13
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 47:22
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 49:23
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 53:18
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 55:38
extraneous input 'Transport' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 57:8
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 59:18
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 61:38
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 62:24
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 65:14
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 67:34
extraneous input 'Transport' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 69:4
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 71:14
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 73:34
extraneous input 'dedent' expecting {<EOF>, 'Struct', 'Task', NL}
File ./PFDL_Examples/test.pfdl, in line 74:20

In general, it would be very helpful for users to remove these restrictions on namings and allow all namings to start with either an uppercase or a lowercase letter.

I will try to fix these error messages, could you provide the example file? It seems like these errors get larger if the PFDL file grows. I did not get such errors for small examples.
The naming restrictions allow us to distinguish between certain components (e.g. Task calls vs .Service calls). We would need additional keywords if we allow arbitrary naming of components. Currently, there is no plan to make such changes.


Cleanup formatting in CHANGELOG.md

Bugfix:  Markdown formatting was broken. This commit fixes up the formatting so that the rendered HTML is correct.

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[x] I have authorization from the game's publisher to make this an official sheet on Roll20 with their name attached.
[x] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[x] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Character Sheet Info Roll20 Internal Use only.

Hi @stefanlasiewski! As this is an official publisher sheet, we'll need approval from the original author, @seregrauko, before merging any changes. Even though this is a small one.

this is fine


Simulator randomly freezes for 2-10 seconds during HoC gameplay in level 3 after adding water

Don't know if this happens in other levels, but I experienced it several times after adding water in level 3.

I can't reproduce this. If you still see this please reopen.


Does not bind to correct IP on Heroku

When starting this up on heroku, aws-es-kibana binds to <IP_ADDRESS> (local loopback), which heroku obviously isn't looking at, so 60 seconds later, we get this:
Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
Workaround: set the BIND_ADDRESS config (env) to <IP_ADDRESS>, which for sure will bind to the address heroku can see.  Confirmed this fixed the issue for us.
Suggestion: Bind to <IP_ADDRESS> by default (less secure in general, but fixes the problem on heroku)

This has been fixed with #38


BatchClientImpl okHttp Interceptor Queue Limit at 5

The okHttp interceptor used in BatchClientImpl does not seem to be able to intercept more than 5 calls. This causes a batch client that is waiting on more than 5 requests to be added to block forever.
These calls appear not to invoke the intercept() function of the interceptor. Furthermore, the ServiceCall returned by an invoked request method, e.g. createTopicAsync(), is not cancelled; a response is not returned; and the registered callback is not invoked. This implies that the request was intercepted (or else it would have just gone to the server) but not processed.
Failing example:
EmbeddedSocialBatchedClientImpl batchOps = new EmbeddedSocialBatchedClientImpl.Builder()
                .batchSize(7)
                .baseUrl(ESClient.baseURL)
                .build();

for (int i = 0; i < 7; i++) {
      // the interceptor gets invoked here. all 7 calls "succeed" but only 5 invoke the "intercept()" function
      batchOps.getEsClient().getBuildsOperations().getBuildsCurrentAsync(callback);
}
// after this point, the latch() in batchOps still has value 2! issueBatch thus blocks forever
try {
     // the batchOps thread blocks here
     batchOps.issueBatch();
} catch (InterruptedException | IOException e) {
     System.out.println(e.getMessage());
}

I was able to reproduce this issue. I'm currently working on a fix.

Fixed, PR issues, and PR merged (PR #15). Thanks!


Inject Fish Shell Integration Crashes Or Fails

Shell Mode: /usr/bin/fish/
I have managed to turn on frames for Bash by running the command palette option (the script did not work, unless I'm misunderstanding how to use it), but I'm not having the same luck with fish. I have not tried zsh.

Executing the Inject Fish Shell Integration option in the command palette will close that terminal window after what looks like the script ends. It's launched in a Extraterm Fish shell.

Running the setup_extraterm_fish.fish script by typing "fish setup_extraterm_fish.fish" into the Extraterm Fish terminal window will result in the script outputting "Setting up Extraterm support." in shell but nothing more. Show and form still do not work and there are no frames in the terminal window.

Running calling the script like that is running the script in a new fish session and exiting, meaning it's not in the current interactive shell. You need to source the file in the current shell like this. (dot, space, then the script)
. setup_extraterm_fish.fish
Here's an example of how mine is setup in my home directory (where I placed my setup scripts). This is from my ~/.config/fish/config.fish file.
. ~/extraterm-commands/setup_extraterm_fish.fish


Benchmark multi-threaded on big cores

Even though we don't believe that being allocated multiple big cores for an extended period of time is a realistic scenario on current android phones, it would still be useful to run multi-threaded benchmarks on big cores. We haven't really optimized for little cores, which have a significantly different architecture (in order vs out of order execution) and so the multi-threaded benchmarks there aren't telling us as much as we'd like. The cost of adding these benchmarks is extra latency on the benchmarking pipeline, but big-core is much faster than little core and multi-threaded is even faster, so it shouldn't be a huge difference

+1!
(just wanted to note that I most certainly don't believe that big cores can't be used for extended periods of time (see: games), and a large number of ML use cases are not about sustained non-stop execution and would be much happier to have 4+x lower latency for their bursty workloads :)

(just wanted to note that I most certainly don't believe that big cores can't be used for extended periods of time (see: games),

My understanding from @bjacob is that if you have 2 big cores running at full tilt you will start getting thermally throttled after less than a second

Do you know that big cores are used while running games on an android phone?  (honest question - systrace'ing a game would tell. we can follow up internally to find out answers.).

Always important to identify which experiential statements in one area carry over to frameworks and tooling that have a large variety of usage scenarios - doesn't mean the observations were wrong, only that the problem space is much different and larger here :)
Games generally run on big cores with the guidance being to run latency-insensitive background tasks on the little cores, e.g.
https://developer.android.com/games/optimize?hl=zh-cn#defer-work-to-slow-cpus
There's also fun things like this deep dive: https://www.androidauthority.com/fact-or-fiction-android-apps-only-use-one-cpu-core-610352/

Concretely a lot of ML workloads - especially mobile ones - don't even run longer than a second and especially if on the big cores (200ms on big and then done is better than 4sec on little competing with other work, from a system health perspective). We also have very different threading characteristics than older frameworks that would do things like spin in-between work or only use single threads for a majority of the time: we look a lot more like a game engine than an ML framework.
Doesn't mean that certain models with certain use cases won't match the previous experience, only that they are a fractional part of the total set of scenarios we are targeting. As a framework our job is to let the user make the decisions for their particular scenario as we don't own their code or application and we cannot blindly make assumptions that dramatically impact a large chunk of those scenarios. Someone looking to use BERT to translate text in a chat application once every few minutes for 150ms each invocation should not suffer because we only tuned our framework to target a mobilevision model running at 90hz on 4k images for hours on end.

(also interesting: https://developer.qualcomm.com/sites/default/files/docs/adreno-gpu/developer-guide/cpu/cpu.html#controlling-task-execution + https://developer.qualcomm.com/sites/default/files/docs/adreno-gpu/developer-guide/cpu/cpu.html#use-big-cores-for-compute-intensive-tasks)

Games generally run on big cores with the guidance being to run latency-insensitive background tasks on the little cores, e.g. https://developer.android.com/games/optimize?hl=zh-cn#defer-work-to-slow-cpus

Thanks for the very interesting link! I learned a few things there, including, not least, the existence of the NDK Thermal API --- going to be super handy.
Quick check though that I'm reading correctly the paragraph you linked to above. In my reading, it's not suggesting that we should or can get anything scheduled specifically on a big core. It's saying that games should use sched_setaffinity to explicitly tell non-latency-critical, short-duration tasks to go on little cores. Otherwise, such tasks might go on big cores, which would be wasteful.
Note that we know as a matter of fact that for normal android programs, sched_setaffinity (which again is the method pointed to by the above link) only works at best to pin to slow cores. The cpuset bits mapping to big cores are disregarded in my experience. There seems to be an exception when the calling process is taskset though -- taskset does work and I believe I strace'd it once and it did nothing else than calling sched_setaffinity. Not such how that works!
Anyway, my summary of the above link would be:

Let the game main thread follow default scheduling (the article does not mention whether that would go on slow or fast cores in practice).
Move as many auxiliary tasks as possible to worker threads and give them affinity to slow cores.

In other words --- still in my limited understanding!! --- the article doesn't say we can (or should) schedule anything on fast cores --- it says, on the contrary, that we can and should shedule certain things on slow cores.

There's also fun things like this deep dive: https://www.androidauthority.com/fact-or-fiction-android-apps-only-use-one-cpu-core-610352/

Thanks, that was an interesting article, and a blast from the past. Notice that the "quad core" SoC it refers to is a Snapdragon 801 which has 4 symmetic out-of-order cores (Krait 400, similar to what we had in the Nexus 5).  And the "octa core" SoC it refers to is a Snapdragon 615, which has 8 in-order Cortex-A53 cores --- branded a "4+4" asymmetric config but the only difference is in the clock speed, 1.5 GHz vs 1.0 GHz, so given that each of these cores has a fluctuating clock speed in practice, for our purposes it's essentially a symmetric platform.
That means that the "big" vs "LITTLE" distinction in the above graph is not very meaningul.
Another thing that I missed in the above article is was a mention of whether the benchmarks were run on battery or while charging.

Concretely a lot of ML workloads - especially mobile ones - don't even run longer than a second and especially if on the big cores (200ms on big and then done is better than 4sec on little competing with other work, from a system health perspective). We also have very different threading characteristics than older frameworks that would do things like spin in-between work or only use single threads for a majority of the time: we look a lot more like a game engine than an ML framework.

Certainly, big cores are useful for short burst ML workloads.

FWIW, none of that changes the fact that we all agree with @GMNGeoffrey 's rationale at the top of this issue. Let's have multi-thread big core benchmarks! No one's arguing against that.

Yep! It's all about the scenario - if you are not latency sensitive then little cores are fine - if you are latency sensitive however they are not great. Lots of stuff factor into that as well - you may have multiple latency sensitive workloads - ML and otherwise - and want to allow ML to run on big core while forcing all your other stuff to run on the little cores if you know the ML workload is lighter. If your ML is synchronized to user input then you may never choose to run on the little cores even if you can't force things to run on big cores - but that's where the OS scheduler comes in (they're never good, but a chance at getting something done several times faster is better than being guaranteed to be slower).
We need to be fast on both, and agreed that this is really about making sure we aren't blinding ourselves to one or the other (just as we shouldn't only run benchmarks on little cores we shouldn't only run on big ones).
It's just a snapshot, but mobilebert runs in 5.6s on 1 little core, 2s on 4 little cores, and 700ms on 1 big core - I'm excited to get the big core multithreading numbers as Vulkan on the same device runs in 190ms. I know almost nothing is tuned and our little core perf is not great yet, but the orders of magnitude are at least feeling ok 🎉

Accidentally marked the PR fixing (#7807) this as fixing itself :facepalm:


Intellisense not working.

Issue Type: Bug
It works at first. But after typing a few more lines, the intelisense stops working completely.
OmniSharp log:
[2020-09-08 00:00:00.901] [renderer1] [error] Problem invoking 'GetCodeActions' on OmniSharp server: Error: Pending request cancelled: /v2/getcodeactions
[2020-09-08 00:00:05.897] [renderer1] [error] Problem invoking 'GetCodeActions' on OmniSharp server: Error: Pending request cancelled: /v2/getcodeactions
Extension version: 1.23.2
VS Code version: Code 1.48.2 (a0479759d6e9ea56afa657e454193f72aef85bd0, 2020-08-25T10:13:11.295Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz (4 x 2594)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.90GB (8.38GB free)

Process Argv

Screen Reader
no

VM
0%

I have the same issue too.........

can you provide a project that this reproduces on ?

Same issue. Fresh install of VS Code, fresh install of Omnisharp.  Syntax Highlighting, IntelliSense, Go to Definition, Find All References NOT WORKING

me too

@HaykShirinyan, Exact same behavior.

How to make it crash

dotnet tool install -g dotnet-script
dotnet script init
Add a nuget package like this :

#r "nuget: CliWrap, 3.2.3"
using CliWrap;

Ctrl+Shift+P -> Restart OmniSharp
It crashes after a certain time

Logs
OmniSharp server started.
    Path: c:\Users\nfs12\.vscode\extensions\ms-dotnettools.csharp-1.23.6\.omnisharp\1.37.3\OmniSharp.exe
    PID: 17236

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on Windows 6.2.9200.0 (x64)
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 2 MSBuild instance(s)
            1: Visual Studio Community 2019 16.8.30717.126 - "e:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin"
            2: StandAlone 16.8.0 - "c:\Users\nfs12\.vscode\extensions\ms-dotnettools.csharp-1.23.6\.omnisharp\1.37.3\.msbuild\Current\Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: Visual Studio Community 2019 16.8.30717.126 - "e:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin"
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in 'c:\Users\nfs12\OneDrive\Desktop\New folder'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.MSBuild.ProjectSystem
        No solution files found in 'c:\Users\nfs12\OneDrive\Desktop\New folder'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in 'c:\Users\nfs12\OneDrive\Desktop\New folder'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Found 1 CSX files.
[info]: OmniSharp.Script.ScriptContextProvider
        Searching for compilation dependencies with the fallback framework of 'net5.0'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Added CSX project 'c:\Users\nfs12\OneDrive\Desktop\New folder\main.csx' to the workspace.
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.Completion.CompletionOptionsProvider, Order: 0
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.ImplementTypeWorkspaceOptionsProvider, Order: 110
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.BlockStructureWorkspaceOptionsProvider, Order: 140
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.

[2020-11-24 18:49:23.255] [exthost] [info] ExtensionService#_doActivateExtension ms-dotnettools.csharp {"startup":false,"extensionId":{"value":"ms-dotnettools.csharp","_lower":"ms-dotnettools.csharp"},"activationEvent":"onLanguage:csharp"}
[2020-11-24 18:49:23.255] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/nfs12/.vscode/extensions/ms-dotnettools.csharp-1.23.6/dist/extension
[2020-11-24 18:52:21.468] [exthost] [error] [ms-dotnettools.csharp] provider FAILED
[2020-11-24 18:52:21.468] [exthost] [error] Problem invoking 'GetCodeActions' on OmniSharp server: Error: Pending request cancelled: /v2/getcodeactions

There have been lots of improvements since this issue was opened. Please open a new issue with logs if you are still running into this.


For how long it would support bash on Windows?

git on win from anaconda doesn't ship bash but conda-forge git ships bash. And I guess this may one of the reasons why build number is 1000: when priority to conda-forge then git would be with bash.
One of my packages depends on bash on win. Is it reliable to depend on conda-forge git? or bash would be removed eventually from it?

git package redistrubutes some Microsoft copyrighted files + git post install script partially fails

@msarahan @scopatz please review git-bash conda-forge package.


Creating modal for receiving user feedback in-app

Summary
This PR is to create a user feedback/bug reporting feature in-app, allowing users to provide feedback or report a bug straight from the app.
IMPORTANT NOTE: REPORTING A BUG WILL CREATE AN ISSUE IN GIT, PLEASE TEST SPARINGLY.

Why is this change needed?
For user acceptance testing

What did you change?
Faye - Created the UI for the feedback modal
Liam - Set up the API and nextjs server to create Git issues from the bug reports submitted in the app

Screenshots of UI changes, if any

OS

[ ] Linux
[x] MacOS
[x] Windows

Looks good overall. I tested the bug report functionality and no issue was created - I assume this is because mlvet-bug-reporter hasn't yet accepted its collaborator rights to the repo though. @LiamTodd ?

Yeah thats correct. The invite has since been accepted


python3.5 ?

Details

Project URL: https://github.com/parmentelat/asynciojobs
Build URL (if applicable): https://readthedocs.org/projects/asynciojobs/builds/
Read the Docs username (if applicable): parmentelat

Expected Result
A description of what you wanted to happen
My code is based on asyncio and uses a lot of async def foo() and await coro() syntax that was introduced in python3.5; so for sphinx to be able to autodoc this code, it needs to run at least python3.5.
Actual Result
A description of what actually happened
At first I have struggled a bit to find about the advanced settings page where I chose CPython3.x, but this now seems to give me 3.4.
As a result of course, sphinx crashes when trying to build.
Is there anything I can do with the settings of my project to get a python3.5 instead ?
Or does this necessarily require an upgrade from on platform side ?
Thanks and my apologies if this is not the right channel for this question.

Any update on this issue? I'm also trying to document a project with async and await.

Closing this as a duplicate of #1990, feel free to watch there for updates.


fix: increase error badge size & add text next to it

This PR...
Changes

Fixes

How to test it

Screenshots

Checklist

[ ] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test


ra_lsp_server 100% CPU consumption non-stop

I believe this issue was already reported earlier and closed as fixed. I've just installed rust analyzer and found that it uses 100% (and sometimes 200%) of CPU and doesn't dwindle down. Also ra_lsp_server stayed up when I quit vs code.
 If you are on Mac, could you try enabling rust-analyzer.useClientWatching option?
It would also be useful to get a stack trace from rust-analyzer at 100% CPU.

@matklad Indeed, this option helped, looks like right now it works as expected!

Cool! The underlying problem is tracked upstream.


Improving delegate generation

Brief Description
The generated delegates are often not well to use and should be improved for the developer.
Instead of having a raw delegate for the developer a nicier, high level one is prefered.
State:
I already talked with @ddobrev and @tritao about it and started implementing.
The new generated code should look like this:
public delegate void HighLevelDelegate (SomeClass class, int someparam);
internal delegate void LowLevelDelegate(IntPtr class, int someparam);

public void SetCallback(HighLevelDelegate del);
internal void SetCallback(LowLevelDelegate del);

However our current approach includes that each callback will be saved until the life-time of a specific class or the application itself ends.

Duplicate of https://github.com/mono/CppSharp/issues/511 .


Problem indexing partials

Hi,
using this gem I had a problem: the partials are not indexed.
Reading the code I've found (perhaps) the source of problem. In search-index-resource.rb:112 calling render() method with {:layout => false} the result doesn't contains any partials.
I haven't found any other resource method to have clean content with, already, partials.
The solution that I've found is Nokogiri side and not Middleman side.
I'll try to describe it:

replace line 112 in search-index-resource.rb  from html = resource.render( { :layout => false }, { :current_path => resource.path } ) to html = resource.render({ :current_path => resource.path } )

Now the problem is that we have all rendered HTML and not, only, yielded.

replace line 112 in search-index-resource.rb  from Nokogiri::HTML(html).xpath("//text()").text to Nokogiri::HTML(html).xpath("//body/*[not(@class='some_class') and not(@class='another_class')]//text()").to_a.join(" ")

some_class and another_class can be passed with an array from configurations. Something like this:

search.exclude_html_classes = ['some_class', 'another_class']

What do you think about this solution?
If right I can work to a PR.

Hi @mukkoo, thanks for the report!
It seems odd that Middleman skips partials when rendering without a layout. Though it seems to be the case when rendering in middleman-search, if I set a layout for a specific page to false in its frontmatter, then middleman displays it without layout but including partials (at least in version 3, I haven't tried 4).
Considering that, before going the Nokogiri way, I'd try to invest more time in figuring out what is causing middleman to skip partials in search-index-resource. If you want to tackle that, great; if not, I'll work on that some time during next week.
@matiasgarciaisaia what do you think?

I don't really like the proposed alternative - seems too hacky for me :/
I'll second @spalladino - if middleman is behaving weird with partials, let's find out why. Rendering all the HTML just to get some part of it - it doesn't seem sensible.
Thanks for the catch, @mukkoo! Hope to give you good news soon :)

Hi, @mukkoo - sorry for the delay.
We took some time with @spalladino to test this (you can check our test project), and - we couldn't repro the issue :(
We created a partial with a pretty much unique word, and middleman-search correctly indexed it.
I don't think it had to do with any of the changes we did in the gem, but check it - we may have fixed it, or who knows what's going on.
If you have any more info to share, we'll take another look later - during the next 2~7 months, perhaps 😛

Closing after 1 month


fix for fxpmath/issues/2

I'm not completely sure but this should fix:
https://github.com/francof2a/fxpmath/issues/2

sorry, it doesn't solve the problem, it requires more logic to handle numpy.float64.


Fix WSClient.update() exception when eventlet has monkey_patched select

What type of PR is this?
/kind bug
/kind regression
What this PR does / why we need it:
Fixes exception in WSClient.update() caused by select not having a poll() attribute when running under eventlet.  Introduced by PR #268
Which issue(s) this PR fixes:
Fixes #281
Special notes for your reviewer:
Does this PR introduce a user-facing change?
NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/assign

This repo has been merged into the main python repo. We are archiving this repo. Please submit the PR to the main repo. Thanks!
/close


dispatch: fix missing receivers in Groups()

Closes #1959

@prymitive can you tell me if it fixes the issue for you?

I can do some testing after work and update here

Test using master branch:
$ ./alertmanager --version
alertmanager, version 0.18.0 (branch: HEAD, revision: f450720213de12237437552fa8e86b715e0baafa)
  build user:       lukasz@kwakBook
  build date:       20190723-21:56:49
  go version:       go1.12.7

kwakBook:alertmanager lukasz$ curl -s localhost:9093/api/v2/alerts/groups | jq -c '.[] | .receiver' | sort | uniq -c
   3 {"name":"by-cluster"}
  15 {"name":"by-cluster-service"}
  24 {"name":"by-name"}
kwakBook:alertmanager lukasz$ curl -s localhost:9093/api/v2/alerts/groups | jq -c '.[] | .receiver' | sort | uniq -c
   3 {"name":"by-cluster"}
  15 {"name":"by-cluster-service"}
  24 {"name":"by-name"}
kwakBook:alertmanager lukasz$ curl -s localhost:9093/api/v2/alerts/groups | jq -c '.[] | .receiver' | sort | uniq -c
   3 {"name":"by-cluster"}
  15 {"name":"by-cluster-service"}
  24 {"name":"default"}

There's either default or by-name receiver, but never both, so we hit this issue.
Test using this PR as HEAD:
$ ./alertmanager --version
alertmanager, version 0.18.0 (branch: pr/1964, revision: 110dd7555c254a3409515d1d7289e6833b7acd1a)
  build user:       lukasz@kwakBook
  build date:       20190723-21:45:37
  go version:       go1.12.7

kwakBook:alertmanager lukasz$ curl -s localhost:9093/api/v2/alerts/groups | jq -c '.[] | .receiver' | sort | uniq -c
   3 {"name":"by-cluster"}
  16 {"name":"by-cluster-service"}
  13 {"name":"by-name"}
  13 {"name":"default"}
kwakBook:alertmanager lukasz$ curl -s localhost:9093/api/v2/alerts/groups | jq -c '.[] | .receiver' | sort | uniq -c
   3 {"name":"by-cluster"}
  15 {"name":"by-cluster-service"}
  12 {"name":"by-name"}
  12 {"name":"default"}
kwakBook:alertmanager lukasz$ curl -s localhost:9093/api/v2/alerts/groups | jq -c '.[] | .receiver' | sort | uniq -c
   3 {"name":"by-cluster"}
  16 {"name":"by-cluster-service"}
  13 {"name":"by-name"}
  13 {"name":"default"}

Both receivers are always present as expected, so the issue is gone.

Can it be that this issue was not fully fixed?
I am still seeing duplicates when I add multiple receivers
   - match:         destination: webhook       receiver: webhook       continue: true     - match:         destination: webhook       receiver: slack
That is the part of my config that generates the duplicate alerts in the UI, Also they are inheriting the group_by from the main config.
I am running the image with master tag from dockerhub which states that was built 2 days ago so this fix should be in there

@fcastello can you share a screenshot and the full AlertManager configuration? I tried to reproduce but couldn't spot the issue.


ng g component my-component adds Backslashes on app.module.ts on Windows

Please provide us with the following information:

Environment :
Windows 10
angular-cli: 1.0.0-beta.14
node: 6.3.1
os: win32 x64
Reproduce

App created on Windows, using angular-cli@webpack ng new newapp.
Creating and moving to another folder inside the app root folder : mkdir app/feature && cd app/feature
Creating a new component using the angular-cli@webpack ng g component my-component

Error
Module not found: Error: Can't resolve './feature
egister-form/register-form.component' in 'E:\Dev\Learning\shooping-angular2\src\app'

Helpful informations
Details : On Windows, in the app.module.ts, the path is created using a backslash as first char after the current path.
import { RegisterFormComponent } from './feature\register-form/register-form.component';
should become:
import { RegisterFormComponent } from './feature/register-form/register-form.component';

Same here
Environment :
angular-cli: 1.0.0-beta.11-webpack.8
node: 6.5.0
os: win32 x64

The issue is still there with the cli beta 15

angular-cli: 1.0.0-beta.15
node: 4.4.6
os: win32 x64

Anybody looking into it?

It'd be really nice if we could get a quick response from the team acknowledging this issue. This isn't some breaking feature, but given the cross-platform nature, proper path generation is more an expected functionality than a nice to have feature.

Dupe of https://github.com/angular/angular-cli/issues/1719, already fixed.


sanitize RecipientInterface input value type in reduceRecipients

Related: https://github.com/vulpemventures/taxi-daemon/issues/91


Feature request: add support for ImageOptim

Their API is not free, but for those of us who would like the most efficient compression (lossy or lossless), I believe it's worth adding as an option: https://imageoptim.com/api

I don't need this anymore now that this plugin supports Imgix. :D


riot-{web,desktop}: 1.5.0 -> 1.5.4

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Notify maintainers
cc @

Superseded by https://github.com/NixOS/nixpkgs/pull/74546


Re-render nodes after setting the state

Hey,
Is there any function that we can call, to re-render the nodes?
here is my what I'm trying to do, I have a node, inside that I have a switch, to show and hide nodes emerging from it based on some condition.
I'm setting its isHidden property to true and false and setting the elements state, but that doesn't re-render the nodes and hide the nodes emerging from it until I drag a card, which is causing the re-render I guess, for some reason.
any idea what might be going wrong here? or any better solution?
thanks in advance.

Can you create a codesandbox so that we can reproduce this issue? We are using the isHidden option in the hidden example

Im doing the same, but I'm not getting the issue, is there any way to re-render the nodes, with the help of a function or something?

I think that you are not changing your state but references to the nodes. You need to update your internal state in order to let ReactFlow know about your changes.


Configuration

Can you please provide some information about the running machine? GPU, OS...
Thanks,

Sorry about Late reply, OS was windows and GPU was NVIDIA DGX. This model was run on 50 GB alloted GPU. but as this is binary classificaiton task, you may need alot less.

Sorry about Late reply, OS was windows and GPU was NVIDIA DGX. This model was run on 50 GB alloted GPU. but as this is binary classificaiton task, you may need alot less.

Please, tell us. Which tensorflow-gpu, keras, python versions did you use for your environment? Thanks.


Madpack: Add a script for automating changelist creation

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/668/

I ran the utility with 1.13 and 1.14 as the release tags and noticed that the output file created by this utility isn't the same as the one checked in changelist_1.13_1.14.yaml. For ex, all the summary functions are missing from the udf section. Also the udt section has an extra entry mlp_step_result[]:

Thanks for the comments @kaknikhil. I addressed them and added the support for return type based dependencies. It would be great if you could take another look at the latest version.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/673/

Thanks for the review @kaknikhil .

We had an issue with the knn help messages during one of the releases because they didn't show up on the diff_udf.sql output. IIRC, the problem was that the same function was converted from a pure SQL function to a plpython function. I don't have a quick solution to identify such cases.
This indentation should be OK.
We can check if the new_vers tag/branch exists and use master in its place. Alternatively, we can change the comment to avoid using the new version. It does not have any functional value.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/679/

@kaknikhil I checked the 1.11 -> 1.12 scenario. The tool is missing thetree_train and forest_train entries. The change seems to be the removal of surrogate_params and the addition of null_handling_params. Since both of them are text type, it does not get picked up by the diff_udf.sql script.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/681/

@orhankislal The new changes look good. Apart from the 2 minor comments LGTM +1


fix(net): use real tcp port for local node record

closes #8851
we didn't configure the tcp port correctly when setting up discv4.
resulting in misreporting of the listener ports via admin_nodeInfo

yes
--discovery.port 0
  "enode": "enode://d86fe05d5678034b25446dbc283a5695abb76699190302d432967579c2a9407d9d8460442199a2190214ecd2c794b842a84f54ccff578daf95fef27df47b4b7b@[2001:a61:27a5:aa01:a800:b445:d962:40d5]:30303?discport=63219",
  "enr": "enr:-Jq4QNb7SAX1vsus8aen2EbH2Omnwl5cbdqZ--bEy4YF2TcVVzkVEL0bnr-m4R9WL50DvqgKosk-I1XzZtEy9Dtp1A8BgmlkgnY0g2lwNpAgAQphJ6WqAagAtEXZYkDViXNlY3AyNTZrMaED2G_gXVZ4A0slRG28KDpWlau3ZpkZAwLUMpZ1ecKpQH2EdGNwNoJ2X4R1ZHA2gvbz",
  "ip": "2001:a61:27a5:aa01:a800:b445:d962:40d5",
  "ports": {
    "discovery": 63219,
    "listener": 30303
  }

as long as you have some peers, finding peers is the job of discovery, but they are technically entirely separate


Document Correction

Please can you correct this part of your GitHub Documentation :
Aligned Infraestructure Guide -> Aligned Infrastructure Guide
Update also it in Table of Contents

Regards,

Fixed, thanks


VCF file format

Are we sure that the current format is correct? Do you know anyone who uses VCF files? Maybe they could test it out to make sure it works with standard programs.
One easy fix is to update the source field:

##source=https://github.com/snayfach/snpMLST

I'm not sure what the differences are, but there's not a 4.2 version of the format: https://samtools.github.io/hts-specs/VCFv4.2.pdf
It's not clear what nucleotides the 4 genotypes refer to:

GP1:GP2:GP3:GP4

Applied the easy fix as well as improved GP1:GP2:GP3:GP4 description.


IRODS ingestion of gantry data (continue 01)

Continuation of https://github.com/AgPipeline/issues-and-projects/issues/6
Task to do
Set up and document an automated process for ingesting gantry data into CyVerse Data Store (IRODS)
Reason

[ ] Ease of access from VICE (for workbench/data exploration)
[ ] Close to CyVerse & UA computational resources

Result

Scripts and configuration necessary for setting this up
Document (as text file in the code repository where the automation & logic end up)
Monitoring & alerting (at least documenting what success/failure looks like)

Steps to take

[x] Confirm these: https://github.com/AgPipeline/issues-and-projects/issues/38#issuecomment-580498348
[ ] Script to create tar files like specified above
[ ] Script to run irsync on tar files above
[ ] Ensure tar file creation & irsync work reliably (or fail noisily)

I’ve addressed the open questions in #38 here: https://github.com/AgPipeline/issues-and-projects/issues/38#issuecomment-582019827 - so you can go ahead with option c: if new data appear after a tar is made, upload a new version that includes the version number in the name and delete the old one, with the caveat that the appearance of new data after packaging indicates a possible bug or error that should be investigated.

Thanks David!

Continued in https://github.com/AgPipeline/issues-and-projects/issues/93


bug: Invalid uri character when the URL path contains chinese characters

Describe the bug
We are using the OSS service. When deleting a path  contains chinese characters, it throws an error:
Unexpected (permanent) at List::next, context: { called: reqsign::Sign, service: oss, path: 中文目录/, listed: 0 } => signing http request, source: invalid uri character

Steps to Reproduce
let mut builder = Oss::default()
        .root("/path/to/dir")
        .bucket("test")
        .endpoint("https://oss-cn-beijing.aliyuncs.com")
        .access_key_id("access_key_id")
        .access_key_secret("access_key_secret");;
let op: Operator = Operator::new(builder)?.finish();
operator.remove_all("中文目录/").await.unwrap();

Expected Behavior
Should work successfully.
Additional Context
OpenDAL version: 0.50.2
Are you willing to submit a PR to fix this bug?

[ ] Yes, I would like to submit a PR.

Thank you, @photino, for reporting the bug. I have confirmed that it is indeed an issue caused by reqsign, where the query is not encoded correctly like s3.
https://github.com/Xuanwo/reqsign/blob/13c22a1b0a2609862c1dcb9b42647cf5b270fd31/src/aws/v4.rs#L347-L360
I will get it fixed.