[M2] [VULKAN] result for SqueezeNet with PyTorch in SHARK tank returns tensor with nan values

What happened?
On comparing the results obtained from PyTorch with SHARK results, it was found that the difference in values is more than the acceptable tolerance range.

No response
Version information
No response
Additional context

VulkanSDK needs to be installed on the system.
IREE built from source code with Vulkan flags enabled is also able to reproduce the error.
To execute with m1-moltenvk-macos target triple on Apple M2, please make the following change in the SHARK source code
file : https://github.com/nod-ai/SHARK/blob/d556c0d6ef8f69b32bc3b2d28165345dd2faf403/shark/iree_utils/vulkan_utils.py#L23
replace : if vulkan_device == "M1":
with : if vulkan_device == "M1" or vulkan_device == "M2":

Does this only repro on the M2? I don't think that anyone in the iree core team has that hardware.

This happens on M1 too: https://github.com/nod-ai/SHARK/runs/7636875382?check_suite_focus=true
All the following models fail on M1 Vulkan but pass on Linux Vulkan
=========================== short test summary info ============================
FAILED tank/convbert-base-turkish-cased_tf/convbert-base-turkish-cased_tf_test.py::ConvBertModuleTest::test_module_static_vulkan
FAILED tank/pytorch/MiniLM-L12-H384-uncased/MiniLM-L12-H384-uncased_test.py::MiniLMModuleTest::test_module_dynamic_vulkan
FAILED tank/pytorch/MiniLM-L12-H384-uncased/MiniLM-L12-H384-uncased_test.py::MiniLMModuleTest::test_module_static_vulkan
FAILED tank/pytorch/alexnet/alexnet_test.py::AlexnetModuleTest::test_module_static_vulkan
FAILED tank/pytorch/bert-base-uncased/bert-base-uncased_test.py::BertBaseUncasedModuleTest::test_module_dynamic_vulkan
FAILED tank/pytorch/bert-base-uncased/bert-base-uncased_test.py::BertBaseUncasedModuleTest::test_module_static_vulkan
FAILED tank/pytorch/mobilebert-uncased/mobilebert-uncased_test.py::MobileBertModuleTest::test_module_dynamic_vulkan
FAILED tank/pytorch/mobilebert-uncased/mobilebert-uncased_test.py::MobileBertModuleTest::test_module_static_vulkan
FAILED tank/pytorch/squeezenet1_0/squeezenet1_0_test.py::SqueezenetModuleTest::test_module_dynamic_vulkan
= 9 failed, 25 passed, 6 skipped, 112 deselected, 1 xfailed, 1 xpassed in 270.06s (0:04:30) =

@stellaraccident
Command :
<PATH TO ..../iree-compile> - --iree-input-type=none --iree-vm-bytecode-module-output-format=flatbuffer-binary --iree-hal-target-backends=vulkan --iree-llvm-embedded-linker-path=<PATH TO ..../iree-lld> --mlir-print-debuginfo --mlir-print-op-on-diagnostic=true --iree-llvm-target-cpu-features=host -iree-vulkan-target-triple=m1-moltenvk-macos --iree-stream-resource-index-bits=64 --iree-vm-target-index-bits=64 --iree-flow-demote-f64-to-f32=false%

MLIR : https://storage.googleapis.com/shark_tank/squeezenet1_0/squeezenet1_0_torch.mlir

What input should I use? With tools/iree-run-module --device=vulkan --module_file=squeezenet-vulkan.vmfb --entry_function=forward --function_input=1x3x224x224xf32 on 36f2451913c025c725f2d7e03935d2e9da9a872c I cannot reproduce this. Results are not NaN.

@antiagainst
I've tried reproducing the issue on my end, it is always reproduced when using pytest command to run test
but, w/o pytest (simple python script for test) and using iree-compile + iree-run-module I'm unable to reproduce the issue.
Also, this failure is specific to Vulkan, CPU test always pass
Not unsure on how to debug this further, lmk if you've got any ideas

There is something you should definitely check : the dimensions of the input image
I tried to train that network on a Nvidia GetForce GPU with images of CxHxW dimensions 3 x 160 x 512 and it kept producing NaN. The weirdest thing is that I did not have that issue when training on CPU. So I decided to reduce the image sizes to 3 x 160 x 256 and it stop producing NaN.
This may require more experimentation but the conclusion I can draw from that test is that there might be an implicit max sizes that the model expected to function "normaly"

Closing this for now given this is Vulkan on MoltenVK -- we have native Metal support and that's the way forward.


Empty ODE screen when opening the tool for the first time

Problem description
Right now when you open the ODE you see a lot of data examples on the left menu:

How to reproduce it

Open the ODE.
Check menu on the left

Suggested solution
If the user did not upload anything, it should be empty.
This issue is related to #328. Check it for further context.

@pdelboca we can close this issue too after you finish testing #328


switch to main branch of jitbench, plus some refactoring

add option to skip building and patching coreclr for development/testing
add option to set branch
switched to main githup repo from my private one

@davmason,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

test ci please

test Windows_NT_JitBenchStart perf

test Windows_NT_JitBenchStart perf

test Windows_NT_JitBenchStart perf


Not internet connection inside containers

Rancher Version:
v1.2.2
Docker Version:
1.12.5
OS and where are the hosts located? (cloud, bare metal, etc):
centos
Steps to Reproduce:
I not able to connect to the Internet inside a container set by rancher. The DNS is working fine, but I can't do a simple curl.
From the rancher-server and from the other infrastructure containers there is no problem, and also with a container that I manually set up in that same host.
Results:
Doing ping to google:
/ # ping google.com
PING google.com (<IP_ADDRESS>): 56 data bytes

Doing ip a:
/ # ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
3: eth0@if19: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether 1a:cf:a2:86:f3:80 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::18cf:a2ff:fe86:f380/64 scope link tentative flags 08
       valid_lft forever preferred_lft forever

Doing route -n:
/ # route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
<IP_ADDRESS>         <IP_ADDRESS>       <IP_ADDRESS>         UG    0      0        0 eth0
<IP_ADDRESS>       <IP_ADDRESS>         <IP_ADDRESS>     U     0      0        0 eth0
<IP_ADDRESS> <IP_ADDRESS>       <IP_ADDRESS> UGH   0      0        0 eth0

Where are your machines located? Can you give an example of 'a container set by rancher' so we can reproduce?

closing due to inactivity.


Uninitialized Read (and Divide by Zero) in ParseWave64HeaderConfig()

uninit-divzero-waveheader.wav.zip - contains fuzzed input
The parsing of the attached file uninit-divzero-waveheader.wav leads to a read of an uninitialized location in memory. The uninitialized read sometimes further leads to a divide-by-zero error. The uninitialized read can be uncovered using a tool such as Valgrind or MemorySanitizer. For example:
$ valgrind ./cli/wavpack uninit-divzero-waveheader.wav
==3921== Memcheck, a memory error detector
==3921== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==3921== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==3921== Command: ./cli/wavpack uninit-divzero-waveheader.wav
==3921==

 WAVPACK  Hybrid Lossless Audio Compressor  Linux Version 5.1.0
 Copyright (c) 1998 - 2019 David Bryant.  All Rights Reserved.

creating uninit-divzero-waveheader.wv,==3921== Conditional jump or move depends on uninitialised value(s)
==3921==    at 0x41016B: ParseWave64HeaderConfig (wave64.c:211)
==3921==    by 0x408A94: pack_file (wavpack.c:1777)
==3921==    by 0x404AE2: main (wavpack.c:1273)
==3921==
==3921==
==3921== Process terminating with default action of signal 8 (SIGFPE)
==3921==  Integer divide by zero at address 0x1002D83DC5
==3921==    at 0x410214: ParseWave64HeaderConfig (wave64.c:220)
==3921==    by 0x408A94: pack_file (wavpack.c:1777)
==3921==    by 0x404AE2: main (wavpack.c:1273)
==3921==

It appears that this is an uninitialized read of the field WaveHeader.NumChannels on this line. This sometimes leads to a subsequent divide by zero on this line -- I guess the division instruction may or may not be executed based on what value is read for WaveHeader.NumChannels.

This is fixed now, thanks!

Thanks for the reports and retest!

uninit-divzero-waveheader.wav.zip - contains fuzzed input

Aw, it's interesting and weird that when I wget the zip and unzip it and run valgrind wavpack uninit-divzero-waveheader.wav, all I get is:
root@15b10a339dee:/home/elts/wavpack# valgrind wavpack uninit-divzero-waveheader.wav
==838== Memcheck, a memory error detector
==838== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==838== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==838== Command: wavpack uninit-divzero-waveheader.wav
==838==

 WAVPACK  Hybrid Lossless Audio Compressor  Linux Version 4.70.0
 Copyright (c) 1998 - 2013 Conifer Software.  All Rights Reserved.

uninit-divzero-waveheader.wav is not a valid .WAV file!
==838==
==838== HEAP SUMMARY:
==838==     in use at exit: 0 bytes in 0 blocks
==838==   total heap usage: 7 allocs, 7 frees, 2,334 bytes allocated
==838==
==838== All heap blocks were freed -- no leaks are possible
==838==
==838== For counts of detected and suppressed errors, rerun with: -v
==838== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

I am not sure why it gives me uninit-divzero-waveheader.wav is not a valid .WAV file!, any clue?

uninit-divzero-waveheader.wav.zip - contains fuzzed input

Aw, it's interesting and weird that when I wget the zip and unzip it and run valgrind wavpack uninit-divzero-waveheader.wav, all I get is:
root@15b10a339dee:/home/elts/wavpack# valgrind wavpack uninit-divzero-waveheader.wav
==838== Memcheck, a memory error detector
==838== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==838== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==838== Command: wavpack uninit-divzero-waveheader.wav
==838==

 WAVPACK  Hybrid Lossless Audio Compressor  Linux Version 4.70.0
 Copyright (c) 1998 - 2013 Conifer Software.  All Rights Reserved.

uninit-divzero-waveheader.wav is not a valid .WAV file!
==838==
==838== HEAP SUMMARY:
==838==     in use at exit: 0 bytes in 0 blocks
==838==   total heap usage: 7 allocs, 7 frees, 2,334 bytes allocated
==838==
==838== All heap blocks were freed -- no leaks are possible
==838==
==838== For counts of detected and suppressed errors, rerun with: -v
==838== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

I am not sure why it gives me uninit-divzero-waveheader.wav is not a valid .WAV file!, any clue?


Add Bookmark of sites Project

This project will have the bookmark of the sites and saves that particular website in the home page for that particular user.

Please @ridsuteri  review this issue

@K-jais is it similar to issue #492 ?
if not please provide a brief description and gif/screenshots

@ridsuteri

@K-jais this looks similar to #579 , which is already merged into main ,hence i don't think it's available now :(


commissionReport.

Is anyone having issues with getting the commissions back from the commissionReport?
I printed out the message output from the commissionReport and the fill event that preceded it.
orderStatus orderId=20, status=Filled, filled=2, remaining=0, avgFillPrice=2060.5, permId=1594773782, parentId=0, lastFillPrice=2060.5, clientId=11, whyHeld=None
commissionReport commissionReport= ib.ext.CommissionReport.CommissionReport object at 0x110b8afd0
As you can see the attributes are displayed correctly for OrderStatus (and many other message types) but not for commissionReport.
Helpful hints or suggestions for a workaround are much appreciated. Thanks.

You need to unpack further. The commission report has attributed such as

dot  m_commission
dot m_currency
and more.

Thanks Anthony.


Corrected references to systemjs configuration

PR for #27

Thanks! I want "app" to stay mapped to "app" since systemjs.config is already in /src, but it's a minor tweak I can make.


"Goto Definition" doesn't work in Visual Studio 2022

Is your feature request related to a problem? Please describe.
"Goto Definition" doesn't work in Visual Studio 2022
e.g. when using WTL
LRESULT CView::OnPaint(UINT /*uMsg*/, WPARAM /*wParam*/, LPARAM /*lParam*/, BOOL& /*bHandled*/)
{
	CPaintDC dc(m_hWnd);

	return 0;
}

CPaintDC here is highlighted, but "Goto Definition" on it doesn't work, error message:

A definition for the symbol 'CPaintDC' could not be located.

Proposed solution
Let "Goto Definition" work by default.
More Info
If add WTL include path (e.g. vcpkg\packages\wtl_x64-windows\include) to the project, "Goto Definition" works.

I assume WTL is installed as a vcpkg port? If so, was "vcpkg integrate install" run to add vcpkg integration to your VS project? Can your code build successfully?
Go To Definition is an IntelliSense feature in VS so it uses the EDG-based IntelliSense parser. If it fails when referencing something from WTL that suggests that IntelliSense doesn't know about WTL. Do you have other issues in your codebase with respect to WTL (e.g. squiggles, no autocompletion, ...)?

Ping @playgithub for response.

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.


Using fread to populate memory returned by vkMapMemory fails when traced using pageguard

This is a rather curious corner case. If tracing with pageguard, then doing fread to populate memory returned from vkMapMemory will fail. The same code when not traced will work fine. Using memcpy or other means of copying memory works fine. Using assisted memory tracking mode works fine.
Example:

void* pBuf = NULL;
vkMapMemory(..., &pBuf);
fread(pBuf, size, 1, file); // <--- Returns != 1, errno = EFAULT

I made a small unit test to reproduce this issue in https://github.com/ARM-software/tracetooltests  - see src/vulkan_copying_3.cpp. Run it with the -c 2 option to reproduce this behaviour. You can see with the -c 0 and -c 1 options that neither memcpy and memset have this problem. Also reproduced with our own vktrace-based tracer.

fread may lead to the kernel writing into the buffer (if fread doesn't buffer the read), memcpy/memset happens entirely in the userspace.
So what happens when kernel tries to write into write-protected memory? Kernel won't explode, but the page fault we expect won't be thrown, and protected memory won't be written into. So the behavior you see is not a bug but unfortunately a limitation of this tracking method.
As a side note, I myself didn't even know about such possibility when implemented memory tracking for apitrace, but coincidentally recently I was asked what would happen in such case =)

I think @werman  is correct. In case fread is used SIGSEGV is not generated and fread simple fails with a Bad address error.
Initially I thought creating an internal implementation of fread in a separate .so file which would use an internal buffer. Redirecting calls to fread is not as simple as dlopening the file though. This is because existing calls to fread are resolved by the dynamic linker when the executable is being loaded and not when the dlopen will take place (much later). I.e. the dlopen is not going to change existing resolved symbols.
The only solution I can think of is the use of LD_PRELOAD but this is too intrusive as it needs to change the way the executable is invoked.
If anyone can think of a better alternative I would be delighted to hear it.

Concluded that there is no viable solution for this problem and decided to live with it.
A note has been added in the documentation to warn users (#732)


Fix for unauthorized access and push notification

ddec1c2 aims to fix the Unauthorised errors, its not a good thing for a server

This prevents to running of the event loop if the apiKey is null, which can only happen if the user logouts!
255448c: Due to some refactoring the savePushToken wasn't working fine, now it will

Automated message from Dropbox CLA bot
@kunall17, it looks like you've already signed the Dropbox CLA. Thanks!


Cannot run batch files using batch script task in azure devops

I am running the basic example provided
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/batch-script?view=azure-devops
Gives me the following error
2019-08-27T19:30:10.1477578Z ##[section]Starting: Run script test.bat
2019-08-27T19:30:10.3345938Z ==============================================================================
2019-08-27T19:30:10.3346075Z Task         : Batch script
2019-08-27T19:30:10.3346115Z Description  : Run a Windows command or batch script and optionally allow it to change the environment
2019-08-27T19:30:10.3346170Z Version      : 1.1.7
2019-08-27T19:30:10.3346203Z Author       : Microsoft Corporation
2019-08-27T19:30:10.3346236Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/batch-script
2019-08-27T19:30:10.3346310Z ==============================================================================
2019-08-27T19:30:10.3721220Z ##[command]d:\a\r1\a\test.bat
2019-08-27T19:30:10.3854918Z 'd:\a\r1\a\test.bat' is not recognized as an internal or external command,
2019-08-27T19:30:10.3855183Z operable program or batch file.
2019-08-27T19:30:10.4092423Z ##[error]Process completed with exit code 1.
2019-08-27T19:30:10.4108580Z ##[section]Finishing: Run script test.bat

This must be running under classic RM, and it's using the RM default working directory. Your script is probably in your source directory. Set the working directory for this step (task) to the source directory.


how can i create sections with header and footer ?

i want to create sticky headers with two sections lets say SECTION A ---> header ---> contents in grid ---> footer  similarly SECTIONB ---> contents in grid ---->footer once i scroll sectionA then sectionA header should stick on top and similarly when i start scrolling sectionB contents then its header should stick on top

Duplicated #9


Show the help information of the NCO NCRA command

The information should be displayed aside the command dialog.

Done.


made new Branch old was shitty

made all tests green
impelmented sqlite backend as database
ran black

@JulianFeinauer


Segfault after upgrade from 1.0.0 to 2.0.1_4

As part of upgrading all my packages, I'm now getting a segmentation fault when trying to start my meteor server. Removing fourseven:scss fixes this.
This is my upgrade output — https://gist.github.com/TimFletcher/620226f44c70f1eb393c
I'm wondering if it's something related to the libsass version?
This is what I get when starting the server:
meteor --settings settings/development.json
[[[[[ ~/code/personal/linkmetrics ]]]]]

=> Started proxy.
=> Started MongoDB.
Segmentation fault: 11ation

Should mention I'm using OS X Yosemite on a 2014 MBP, not Windows.

Hi Tim,
After a quick google search I found (this)[http://stackoverflow.com/a/28158992] - do those steps help it? Does it segfault from a new project too (meteor create test; cd test; meteor add fourseven:scss; meteor)?

Hey,
Yes. I'd tried those steps. When meteor dies it does leave a process running that I need to kill using those steps. Restarting meteor gives the same error again though.
I tried your new project approach and it worked fine so I guess there's some other issue elsewhere. I'll try removing the other packages one by one until it works. Thanks!

Cool, let me know which packages aren't playing nicely together!

Well, rather disappointingly, a clean install of all the packages in a new meteor app will start just fine. So I suppose it's something in my code. Most likely my SCSS I guess so I'll start removing that.

So it looks like the modulus operator doesn't work. This code (from https://github.com/thoughtbot/neat) is what causes the segfault:
  @else if length($query) % 2 == 0 {
  //  $query: append($query, $total-columns);
  }

There's a closed issue for this in libsass.
I've managed to work around this for now by installing an older version:
meteor add<EMAIL_ADDRESS>
Would love to get all this working with the latest versions but I'm good for now. Thanks for your help.

Ah interesting, I'll leave this open - it should be fixed in the 3.0.0-betas which I need to write this weekend.

Update @TimFletcher - adding pre-release NPM packages to a Meteor package isn't really possible, so I'm waiting for the stable 3.0.0 to come out. Sorry about the frustrations in the mean time.

No problem! I'm fine working with the older one for now. Doesn't seem to be causing any issues. Appreciate the update though!

Just triaging these issues, there's v3.0.0 out and I'll get v3.1.1 out soon too, both which should handle this again.

This was fixed long ago so I'm closing to reduce open issue noise. Thanks for the fix!


Fix the plugin acceptance tests

When I run it locally it does pass. Going to merge since it at least makes Ubuntu green again so that's an improvement.


">" creates files, even on terminating errors

">" (but not | out-file) creates files, even when the command has a terminating error.   (I was helping a newbie with > vs -gt.)
Steps to reproduce

PS /Users/js> try { 1 | Where $_ > 1  } catch { 'yes' }

PS /Users/js> get-item 1

Expected behavior
yes

get-item : Cannot find path '/Users/js/1' because it does not exist.
At line:1 char:1
+ get-item 1
+ ~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (/Users/js/1:String) [Get-Item], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetItemCommand

Actual behavior
yes

    Directory: /Users/js

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-----           7/14/2019  7:01 PM              0 1

Environment data

Name                           Value
----                           -----
PSVersion                      6.2.0
PSEdition                      Core
GitCommitId                    6.2.0
OS                             Darwin 16.7.0 Darwin Kernel Version 16.7.0: Thu Jun 21 20:07:39 PDT 2018; root:xnu-3789.73.14~1/RELEASE_X86_64
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

It is "by design". Redirection is compiled as Out-File cmdlet, then engine execute begin blocks for every cmdlet in the pipeline and the file is created in begin block of Out-File cmdlet.


Enhancement: Add Urban Environment

Would it be possible to add an Urban environment, and for Obstacles add Furniture (or Structure or something akin?) Something for Stairs, tables, carts, etc, Stairs/inclines are a very typically difficult terrain, not sure if that would be it's own obstacle category or not but just looking for something more urban/man made.

Urban environment has been added.  Furniture obstacle has been added.
No pictures yet, but I'll work on it.
I think stairs wouldn't need their own type of terrain.  The purpose of environment is that some classes ignore difficult terrain in certain environments.  So the environment/obstacle value is all about giving a Ruler the information it needs to calculate that. But since there's not a feat or item that lets you ignore the difficult terrain of stairs... there's really no point.


[B001255] Rep. Charles Boustany

Rep. Charles Boustany:
http://www.house.gov/boustany
Likely contact form URL to start with:
https://boustanyforms.house.gov/contact-me

YAML file not found. I am working on it.


Intermittent Blank Screen On Windows

Describe the bug
A tauri app bundled in an .msi file shows blank intermittently when started.
To Reproduce
Steps to reproduce the behavior:

Clone https://github.com/Kelerchian/try-tauri
cd /{PROJECT_PATH}/src-ui; npm install; npm run build;
cd /{PROJECT_PATH}/src-tauri; npx tauri build;
run /{PROJECT_PATH}/src-tauri/target/release/bundle/msi/try-tauri_0.1.0_x64.msi
start /{INSTALLATION_PATH}/try-tauri.exe

Expected behavior
App does not show blank screen when started.
Screenshots

Platform and Versions (please complete the following information):
OS: Windows_NT(10.0.19042) - win32/x64
Edge: 44.19041.423.0_neutral__8wekyb3d8bbwe
Tauri.js: 0.13.0
Tauri-bundler: 0.9.4
Tauri.rs: 0.10.0
Node: v12.14.0
NPM: 6.13.7
Yarn: None
Rustc: 1.47.0 (18bf6b4f0 2020-10-07)
Additional context
From tauri info
tauri.rs - 0.10.0
mode - embedded-server
build-type - bundle
CSP - default-src blob: data: filesystem: ws: http: https: 'unsafe-eval' 'unsafe-inline'
distDir - ../dist/ui
devPath - http://localhost:41234

I have the same issue. Check what happens od edge and on IE11. It turns out that my tauri use ie11 not edge. I have no clue how to change this.

It's probably a compatibility issue (IE11) with your JavaScript code. Can you try running your app on IE and see if it works?

How do you see if uses edge or ie11, and how do you configure it?
Also, note that it is intermittent.
It sometimes renders the application, it sometimes doesn't.
I'm sure this is not an issue with the JS code because the JS code should be static in this bundled build unless Tauri intermittently switch between ie11 (not compatible) and edge (compatible) between different executions.

I can try it if there's a repo I can clone to reproduce it.
Otherwise I'd recommend downloading the Microsoft Edge DevTools on Windows Store and trying to see what's going on (debug flag needed, npm run tauri --debug).

I put a link on the top comment. Here you go https://github.com/Kelerchian/try-tauri
Oh, when debugged with Edge DevTools, the DevTools crashes

I believe this issue will also be resolved by the next release.


Feat: add watsonx.ai embeddings

Add Watsonx.ai Embeddings
Issue #9
Changes made
Created embedding.go and embedding_option.go
Enabled two methods, following the Python SKD,

EmbedQuery (single query/text to embed)
EmbedDocuments (multiple queries/texts to embed)

The embedding options functional builder is followed by the prefix WithEmbedding to avoid collisions or confusion with the Chat (Generate) options. (Maybe is a good idea to add the Chat prefix to the generate options to maintain naming conventions)
Moved the methodgenerateUrlFromEndpoint
As this method is used by the embeddings as well, I believe its better to place this helper method in the client.go rather than in the generate.go
Updated README.md
Added examples of the embedding methods
Tests
Created a new file test_utils.go to keep common utility methods between all tests files such as the getClient
Created a embedding_test.go to tests embedding new feature with and without options

Glad to help :)


Backup data of elasticsearch:6.3.1 to s3

I want to backup data of elasticsearch to s3 with elasticsearch-dump is  running on docker.
But some problems apear in docker logs.
My command in shell：
docker run -dit --name=es-backup --net=host taskrabbit/elasticsearch-dump --s3SSLEnabled "false" --s3Endpoint "s3.stafdfdgig.egehap.com" --s3AccessKeyId "EQfjdksfhkd3N82CS" --s3SecretAccessKey "NQNnruud2zkfhfjksdhfksffdsafdI9div97q" --input=http://<IP_ADDRESS>:9201/bank --output "s3://db-backup/es-backup/bank"

My dokcer logs：

I can't slove the problem
tips:
The exactt s3 key secret endpiinot has been modified on github, I think it's insecure on open platform.

Seems to be having trouble parsing the response from s3 (which is xml). According to the aws-sdk forum, it might be a corrupted response. I'll add a retry option, but beyond that I can't do much

version 6.8.0 has been pushed to docker hub

版本6.8.1已被推送到docker hub
###I am trying v6.8.1

Run the shell command:
docker run -it --rm  --net=host taskrabbit/elasticsearch-dump:v6.8.1 --concurrency 1 --s3SSLEnabled="false" --s3Endpoint="s3.m" --s3AccessKeyId="sdjkghsdgkhaskdjghaskjd" --s3SecretAccessKey="fhsdlkfsadlfjsaldkfjalsdfkjl" --s3ForcePathStyle="true"  --input "http://<IP_ADDRESS>:9201" --output s3://db-backup/es-backup/es-all.json

The end of command resault:

Know the file has been uploaded s3
Restore data from s3 to elasticsearch, running the shell command：
docker run -it --rm  --net=host taskrabbit/elasticsearch-dump:v6.8.1 --concurrency 1 --s3SSLEnabled="false" --s3Endpoint="s3.om" --s3AccessKeyId="gsdkghklskdghasklghklS" --s3SecretAccessKey="jsdhafkjsdhfkjsdhfkjsadfhkjds" --s3ForcePathStyle="true"  --output "http://<IP_ADDRESS>:9201" --input s3://db-backup/es-backup/es-all.json

The resault of command:

Only 31083 objects were restored in elasticsearch and lost many data

@ferronrsmith


Increase bundle size substantially

This library increases the bundle size substantially. There might be ways to optimize this such as using PNG compression:
https://tinypng.com/
https://www.npmjs.com/package/imageoptim-cli
https://imageoptim.com/mac

Also, since Metro bundler cannot shake out which flags you are/aren't using, this import here: https://github.com/frostney/react-native-flags/blob/master/index.js#L5 will import all flags even if you're using just one flag.


ubuntu-latest is setting ubuntu20.04 instead of ubuntu22.04

Description
    pool:
      vmImage: ubuntu-latest

When using MS-hosted images and the vmImage ubuntu-latest for pool in Azure DevOps pipeline the following is seen during a pipeline run:

According to documentation the ubuntu-latest YAML-label should be Ubuntu 22.04, therefor I consider this a bug.
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[X] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] Ubuntu 24.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Operating System
Ubuntu
20.04.6
LTS

Runner Image
Image: ubuntu-20.04
Version: 20240624.2.0
Included Software: https://github.com/actions/runner-images/blob/ubuntu20/20240624.2/images/ubuntu/Ubuntu2004-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu20%2F20240624.2

Runner Image Provisioner
2.0.370.1

Is it regression?
No
Expected behavior
The ubuntu-latest YAML-label to reflect Ubuntu 22.04 image and not Ubuntu 20.04 image.
Actual behavior
The ubuntu-latest YAML-label is using Ubuntu 20.04 image and not the expected Ubuntu 22.04 image.
Repro steps

In Azure DevOps and in an Azure Pipeline, define a pool from stage level and use vmImage: ubuntu-latest

Hi @feliasson,
We have tested it from our side, and it is showing ubuntu-22.04.
# Starter pipeline
# Start with a minimal pipeline that you can customize to build and deploy your code.
# Add steps that build, run tests, deploy, and more:
# https://aka.ms/yaml

trigger:
- dependabot/npm_and_yarn/result/express-4.19.2

pool:
  vmImage: ubuntu-latest

steps:
- script: echo Hello, world!
  displayName: 'Run a one-line script'

Result:

 2024-06-27T09:16:34.8662048Z ##[section]Starting: Job
2024-06-27T09:16:35.0428058Z ##[section]Starting: Initialize job
2024-06-27T09:16:35.0430602Z Agent name: 'Hosted Agent'
2024-06-27T09:16:35.0430863Z Agent machine name: 'fv-az637-984'
2024-06-27T09:16:35.0430994Z Current agent version: '3.241.0'
2024-06-27T09:16:35.0465468Z ##[group]Operating System
2024-06-27T09:16:35.0465614Z Ubuntu
2024-06-27T09:16:35.0465686Z 22.04.4
2024-06-27T09:16:35.0465752Z LTS
2024-06-27T09:16:35.0465847Z ##[endgroup]
2024-06-27T09:16:35.0465934Z ##[group]Runner Image
2024-06-27T09:16:35.0466038Z Image: ubuntu-22.04
2024-06-27T09:16:35.0466135Z Version: 20240616.1.0

Hi @RaviAkshintala, then maybe the behavior occurs when pool is set from stage level when using the extends definition .
To give you an example how it looks like:
# pipeline yaml

resources:
  repositories:
  - repository: template
    type: git
    name: tooling
    ref: refs/heads/main

extends:
  template: pipeline-template/<template-name>-pipeline-template.yml@template
  parameters:
   <parameters>

# <template-name>-pipeline-template.yml@template

parameters:
  <parameters>

stages:

- stage: stage1
    pool:
      vmImage: ubuntu-latest

  jobs:
   <jobs>

I hope this can help to reproduce the behavior.

@feliasson As per your repro steps we have ran the pipeline and it is taking only ubuntu-22.04.Please find the below logs.
2024-06-28T07:05:19.5094686Z ##[section]Starting: Build
2024-06-28T07:05:19.6526690Z ##[section]Starting: Initialize job
2024-06-28T07:05:19.6529088Z Agent name: 'Hosted Agent'
2024-06-28T07:05:19.6529407Z Agent machine name: 'fv-az369-114'
2024-06-28T07:05:19.6529555Z Current agent version: '3.241.0'
2024-06-28T07:05:19.6560917Z ##[group]Operating System
2024-06-28T07:05:19.6561092Z Ubuntu
2024-06-28T07:05:19.6561187Z 22.04.4
2024-06-28T07:05:19.6561269Z LTS
2024-06-28T07:05:19.6561364Z ##[endgroup]
2024-06-28T07:05:19.6561483Z ##[group]Runner Image
2024-06-28T07:05:19.6561609Z Image: ubuntu-22.04
2024-06-28T07:05:19.6561722Z Version: 20240624.1.0
2024-06-28T07:05:19.6561953Z Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240624.1/images/ubuntu/Ubuntu2204-Readme.md
2024-06-28T07:05:19.6562242Z Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240624.1 ```

stages:
- stage: Build
  displayName: Build stage
  jobs:
  - job: Build
    displayName: Build
    pool:
     vmImage: 'ubuntu-latest'
    steps:
    - task: Docker@2
      displayName: Build and push an image to container registry
      inputs:
        command: buildAndPush
        repository: $(imageRepository)
        dockerfile: $(dockerfilePath)
        containerRegistry: $(dockerRegistryServiceConnection) `

@RaviAkshintala but your example here is not using extend and calling another template where the pool value is set?

Hi @feliasson ,
No, I have used only hosted agents on Azure pipelines and also not set any other template to use pool .

Hi @feliasson ,
No, I have used only hosted agents on Azure pipelines and also not set any other template to use pool .

What kind of answer is that? How are we supposed to report bugs if you are not willing to take similar steps to try to reproduce the behavior? I don't understand.

Hey @feliasson ,
Kindly look into my investigation below ,

I have tried with basic sample yaml pipeline as per your workaround.(Azure-pipelines.yaml)

stages:
- stage: BuildAndTest
  jobs:
  - template: templates/build-test.yml
    parameters:
      vmImage: 'ubuntu-latest'

this is build-test.yaml file

   parameters:
- name: vmImage
  type: string
  default: 'ubuntu-latest'

jobs:
- job: BuildAndTest
  displayName: 'Build and Test Job'
  pool:
    vmImage: ${{ parameters.vmImage }}
  steps:
  - script: |
      echo "Starting build and test on ${{ parameters.vmImage }}"

You can find below logs , it is taking 22.04 as ubuntu-latest . I hope the above workaround will  clarify your issue .
https://github.com/actions/runner-images/blob/ubuntu22/20240624.1/images/ubuntu/Ubuntu2204-Readme.md
2024-07-02T07:17:29.9344371Z Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240624.1
Thankyou !

You are still not using the extends definition to call the template:
https://learn.microsoft.com/en-us/azure/devops/pipelines/yaml-schema/extends?view=azure-pipelines

Hi @feliasson , I don't think so,  there is no difference. I tried the same but i am unable to reproduce the issue .
extends:
  template: templates/build-test.yml
    vmImage: 'ubuntu-latest'

2024-07-02T08:35:40.3792834Z Image: ubuntu-22.04
2024-07-02T08:35:40.3792953Z Version: 20240624.1.0
2024-07-02T08:35:40.3793228Z Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240624.1/images/ubuntu/Ubuntu2204-Readme.md
2024-07-02T08:35:40.3793559Z Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240624.1

Hi @feliasson ,
I hope the above workaround clarify your doubt, it is taking only ubuntu-22.04 when using ubuntu-latest.  Could you please provide your status ?

Hi @feliasson ,
I hope the above workaround clarify your doubt, it is taking only ubuntu-22.04 when using ubuntu-latest. Could you please provide your status ?

No there is nothing in your workaround that clarifies my doubt, because nothing in what you provided shows that you have properly used extends on a template from another repository, the pathing in your code example is from the same repository (self) for example.
Also you are not even inputting parameters in your example because it would look something like this if it was properly done:
# pipeline yaml file

extends:
  template: templates/build-test.yml@<loaded-repository>
  parameters:
    vmImage: 'ubuntu-latest'

# templates/build-test.yml@<loaded-repository>

parameters:
  vmImage: ''

stages:

- stage: stage1
  pool:
    vmImage: ${{ parameters.vmImage }}

  jobs:
    <jobs>

If you are not looking to properly try to reproduce the bug then please close this issue so that we can stop wasting time.

@feliasson We have given you fixes and reproduced the issue as per your problem description, but it is not working the way you want it to. We are closing the ticket now because there is no quick fix. However, we are still working on it, and we'll let you know once we find a solution.


Adjust written value for SDIDMAX to match mttp register diagrams

Registers 1 and 2, for 32-bit and 64-bit mttp respectively, show a 6-bit field for SDID (WARL). However, the text describing SDIDMAX specifies that the 32-bit value is 8 and the 64-bit value is 16, which both clearly cannot fit into a 6-bit field. Clarify the text to note that SDIDMAX should be 6 for both the 32-bit and 64-bit mttp registers.

thanks!


Cape not hidden when wearing Dark Plate with Elytra upgrade

Issue Description:
When a cape is enabled and you are wearing the Dark Plate with Elytra upgrade, the cape is still rendered, resulting in the presence of both the elytra and the cape.
What happens:
The cape is not hidden:

What you expected to happen:
The cape is hidden just like when you are wearing an Elytra in vanilla Minecraft

Steps to reproduce:

Have a cape enabled
Grab the third Dark Plate in EnderIO creative tab and wear it
Exit the inventory GUI, press F5 to view the player in third-person

Affected Versions (Do not use "latest"):

EnderIO: <IP_ADDRESS>
EnderCore: <IP_ADDRESS>
Minecraft: 1.9/1.10
Forge: <IP_ADDRESS>3

Your most recent log file where the issue was present:
don't think this is necessary

Known issue, that part isn't yet implemented. Partly because I have no way to test the code I have to write...

This should work in the next build. You you please report back here if it does? I have no way of testing capes... Thx.

tterrag's CI doesn't seem to be working right now. The latest build was built on Jul 29. http://ci.tterrag.com/job/EnderIO-1.10/

Yep, it's now fixed


python3Packages.watchdog: 2.0.2 -> 2.0.3

Motivation for this change
Update to latest upstream release 2.0.3
Change log: https://github.com/gorakhargosh/watchdog/releases/tag/v2.0.3
Things done

[x] 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 nixpkgs-review --run "nixpkgs-review wip"
[ ] 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.

Result of nixpkgs-review pr 120468 at 9b99f69f run on x86_64-linux 1

38 packages failed to build:

aws-sam-cli
buildbot (python38Packages.buildbot)
buildbot-full (python38Packages.buildbot-full)
buildbot-ui (python38Packages.buildbot-ui)
coconut (python38Packages.coconut)
datasette (python38Packages.datasette)
devpi-client
devpi-server
home-assistant
hovercraft
maestral (python38Packages.maestral)
maestral-gui
markdown-pp
octoprint
pympress
python38Packages.Nikola
python38Packages.cornice
python38Packages.deform
python38Packages.easywatch
python38Packages.hupper
python38Packages.lektor
python38Packages.ndjson
python38Packages.pypugjs
python38Packages.pyramid
python38Packages.pyramid_beaker
python38Packages.pyramid_chameleon
python38Packages.pyramid_exclog
python38Packages.pyramid_hawkauth
python38Packages.pyramid_jinja2
python38Packages.pyramid_mako
python38Packages.pyramid_multiauth
python38Packages.pytest-watch
spyder (python38Packages.spyder)
staticjinja (python38Packages.staticjinja)
python38Packages.watchdog
python39Packages.spyder
streamlit
topydo

2 packages skipped due to time constraints:

python38Packages.labelbox
python39Packages.labelbox

25 packages built successfully:

python39Packages.Nikola
python39Packages.buildbot
python39Packages.buildbot-full
python39Packages.buildbot-ui
python39Packages.coconut
python39Packages.cornice
python39Packages.datasette
python39Packages.deform
python39Packages.easywatch
python39Packages.hupper
python39Packages.lektor
python39Packages.maestral
python39Packages.ndjson
python39Packages.pypugjs
python39Packages.pyramid
python39Packages.pyramid_beaker
python39Packages.pyramid_chameleon
python39Packages.pyramid_exclog
python39Packages.pyramid_hawkauth
python39Packages.pyramid_jinja2
python39Packages.pyramid_mako
python39Packages.pyramid_multiauth
python39Packages.pytest-watch
python39Packages.staticjinja
python39Packages.watchdog

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 120468 run on x86_64-linux 1

2 packages failed to build and already failed to build on hydra master:

spyder: log was empty
python39Packages.spyder: log was empty

1 package failed to build and are new build failure:

(python38Packages.spyder): log was empty

63 packages built:

aws-sam-cli
buildbot (python38Packages.buildbot)
buildbot-full (python38Packages.buildbot-full)
buildbot-ui (python38Packages.buildbot-ui)
coconut (python38Packages.coconut)
datasette (python38Packages.datasette)
devpi-client
devpi-server
home-assistant
hovercraft
maestral (python38Packages.maestral)
maestral-gui
markdown-pp
octoprint
pympress
python38Packages.Nikola
python38Packages.cornice
python38Packages.deform
python38Packages.easywatch
python38Packages.hupper
python38Packages.labelbox
python38Packages.lektor
python38Packages.ndjson
python38Packages.pypugjs
python38Packages.pyramid
python38Packages.pyramid_beaker
python38Packages.pyramid_chameleon
python38Packages.pyramid_exclog
python38Packages.pyramid_hawkauth
python38Packages.pyramid_jinja2
python38Packages.pyramid_mako
python38Packages.pyramid_multiauth
python38Packages.pytest-watch
staticjinja (python38Packages.staticjinja)
python38Packages.watchdog
python39Packages.Nikola
python39Packages.buildbot
python39Packages.buildbot-full
python39Packages.buildbot-ui
python39Packages.coconut
python39Packages.cornice
python39Packages.datasette
python39Packages.deform
python39Packages.easywatch
python39Packages.hupper
python39Packages.labelbox
python39Packages.lektor
python39Packages.maestral
python39Packages.ndjson
python39Packages.pypugjs
python39Packages.pyramid
python39Packages.pyramid_beaker
python39Packages.pyramid_chameleon
python39Packages.pyramid_exclog
python39Packages.pyramid_hawkauth
python39Packages.pyramid_jinja2
python39Packages.pyramid_mako
python39Packages.pyramid_multiauth
python39Packages.pytest-watch
python39Packages.staticjinja
python39Packages.watchdog
streamlit
topydo


Modifying the request before sending to sentry.

I want to modify the request before sending to sentry. I want to check some params from the request. Some of the request that is captured is missing the body. Also I want to exclude some params from the request.
How is the request captured from the loggingevent with Raven Java ? HttpConnection.doSend() ?
Is it possible to modify this request ? Modifying RavenServletRequestListener.servletRequest  ?

@anujku - I think this comment will address your questions: https://github.com/getsentry/raven-java/issues/162#issuecomment-164921702


Add transpiler pass for extension mapper

Summary
@eddieschoute's swap mapper submission for the 2018 Qiskit developer challenge, updated to adhere to #1209 and fit as a transpiler pass.
Details and comments

Hi, it's great to see this being added! We plan to publish an updated version (including paper) mid November.

@ajavadia and @kdk what is the status of this.

The paper is up https://arxiv.org/abs/1902.09102 as well as the source code https://gitlab.umiacs.umd.edu/amchilds/arct. The latter is licensed under GPLv3. We use the igraph library which is GPLv2 licensed for doing some high-performance graph operations so there was no other option. If we remove that code and replace it with an other graph library it could be licensed under Apache (for example).

@ajavadia and @kdk any update about this?

Closing this as @eddieschoute is working on an alternative implementation.


Karpenter publish webhook metrics on TCP/9090 by default

Version

Karpenter Version: v0.22.0

Kubernetes Version: v1.23.14-eks-ffeb93d
Expected Behavior
Port 9090 is closed by default.
Actual Behavior
There are some metrics published. And the port could be configured via the env variable METRICS_PROMETHEUS_PORT  and it looks like default Knative metrics exporter
Some more context in Karpenter Slack
Steps to Reproduce the Problem
kubectl -n karpenter port-forward karpenter-796b44965b-j56gn 9090
Forwarding from <IP_ADDRESS>:9090 -> 9090
Forwarding from [::1]:9090 -> 9090
Handling connection for 9090

curl localhost:9090/metrics
# HELP webhook_go_alloc The number of bytes of allocated heap objects.
# TYPE webhook_go_alloc gauge
webhook_go_alloc{name=""} 2.4627608e+07
...
# HELP webhook_work_queue_depth Depth of the work queue
# TYPE webhook_work_queue_depth gauge
webhook_work_queue_depth{reconciler="ConfigMapWebhook"} 0
webhook_work_queue_depth{reconciler="DefaultingWebhook"} 0
webhook_work_queue_depth{reconciler="ValidationWebhook"} 0
webhook_work_queue_depth{reconciler="WebhookCertificates"} 0

Resource Specs and Logs
We run Karpenter with the following options:
    - args:
      - --webhook-port=10269
      - --metrics-port=10270
      - --health-probe-port=10271

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

This was probably missed when we moved the webhook into the main container rather than running two containers in the Karpenter controller pod. Will check this out soon.

Open minded to a contribution here. Changing feature -> bug.

Hi guys! Do you have any updates on fixing this feature?

The issue was solved in https://github.com/aws/karpenter/pull/4142

Did I get it right, there are no separated webhook metrics published anymore, all the metrics from both controller and webhook are published on the same endpoint?

My apologize. A misunderstanding on my end. We are planning in the near future to drop the webhooks, so this issue may not be relevant for long https://github.com/aws/karpenter-core/issues/103. Would it be possible for you to elaborate on your use-case for exposing the Webhook metrics port?


Calling start() twice creates 2

I'm using pleaseRotate with VueJS on one of my apps.
I call pleaseRotate.start() when I'm mounting [mount()] my app.
calling pleaseRotate.stop() doesn't kill existing pleaseRotate items, so if I'm going
[app] -> [back] -> [app]
pleaseRotate.start() is called twice, while pleaseRotate.stop() is called once [on beforeDestroy()]
and pleaseRotate is activated on both portrait and landscape mode [while the flag forcePortrait is at it's default setting of true].
My workaround is to put createElements() inside the if statement:
if (!document.getElementById('pleaserotate-backdrop'))
[which checks if there is already pleaseRotate div elements existing]
please contact me with any questions regarding this issue and reproducing it.

Please share your code...


Stop opening of alert in beforeOpen event?

I'm trying to prevent swal from opening if nothing is selected.
Here's how I initialize it.
          <swal
            #deleteSwal
            text="Are you sure you want to delete the following products?"
            type="question"
            [showCancelButton]="true"
            (confirm)="onDelete()"
            (beforeOpen)="beforeOpenDelete()"
          ></swa>

Is it possible to interrupt the opening process in beforeOpen event?

Unfortunately, no. Because the onBeforeOpen event comes directly from SweetAlert2 and does not provides any way to prevent the modal apparition.
However, you can still handle that before ngx-sweetalert2 is involved, for example:
<button [disabled]="!somethingIsSelected" [swal]="mySwal">Delete</button>

should work since the disabled state should prevent the [swal] directive to intercept the click.

Cool. Thanks for the confirmation and solution. That works for me :)


add reflector to convert logical plan to SQL statement

Codecov Report
Base: 80.40% // Head: 79.54% // Decreases project coverage by -0.87% :warning:

Coverage data is based on head (9a9c5d9) compared to base (7c0e7ae).
Patch coverage: 77.52% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #122      +/-   ##
==========================================
- Coverage   80.40%   79.54%   -0.87%
==========================================
  Files         101      103       +2
  Lines       12288    13520    +1232
==========================================
+ Hits         9880    10754     +874
- Misses       2408     2766     +358

Impacted Files
Coverage Δ

xngin-compute/src/eval/builder.rs
90.75% <ø> (ø)

xngin-compute/src/eval/mod.rs
93.33% <ø> (ø)

xngin-compute/src/eval/plan.rs
87.50% <ø> (ø)

xngin-expr/src/pred.rs
93.84% <ø> (-3.13%)
:arrow_down:

xngin-frontend/src/parser/dialect.rs
50.00% <ø> (ø)

xngin-frontend/src/parser/dml.rs
100.00% <ø> (ø)

xngin-frontend/src/parser/expr/tests.rs
100.00% <ø> (ø)

xngin-plan/src/builder/tests.rs
86.01% <ø> (ø)

xngin-plan/src/error.rs
47.72% <ø> (ø)

xngin-plan/src/lgc.rs
93.33% <ø> (ø)

... and 38 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


chore: BufferGeometry rename uv2 to uv1

uv2 has been renamed to uv1 in threejs: https://github.com/mrdoob/three.js/pull/25943

We'll need to perform some indirection here for the key to preserve backward compatibility. Had a tough time maintaining this with the back-to-back renames between versions.
https://github.com/pmndrs/three-stdlib/blob/d89e3c32a1eb97e9415e2c361e18af081bc66a25/src/loaders/GLTFLoader.js#L1753-L1770

@CodyJasonBennett I believe GLTFLoader.js is already up to date with backward compatibility in mind.
Would you prefer if I update my changes to follow the same strategy, or shall we ditch backward compatibility in this case? I think is not a terrible idea to ask users to update to a ThreeJS version that is more than a year old already.

The goal of this project is to make itself obsolete by fostering improvements to three examples, and upstreaming them, but we have the additional constraint of adhering to SemVer (which I personally think is an oversight) which means we have to employ tricks to maintain compatibility.
Requiring an upgrade to three.js is a breaking change (major version increment), and I think we can try to maintain an indirection table until that becomes infeasible. The need for an upgrade to three.js is a larger conversation than the changes in this PR alone, as we support as low as r128 with many breaking changes to public API and types since.

I can do this myself in a few hours, when I can take a closer look.

@CodyJasonBennett backward compatibility added ☺

Thanks; I appreciate the thoroughness. Elevating to a fix so we can get this out.


Flush buffers before revoking them while destroying an ImageAcquirer instance

This avoids exceptions when the ImageAcquirer start() fails due to DSStartAcquisition errors and buffers remains queued in the input queue.
Fixes #381

I confirm that with that fix I was able to reconnect to camera after a lost connection... without it the destroy of image acquirer fails and after any attemps to reconnect  fails wit "device already in use"

Surely this will fix many other situations where errors are thrown and no buffer cleanup is performed, so nice to know!

@psoftware Hi, thank you very much for the pull request. Excuse me, I was a bit away due to some family matters. I will look into the PR and then eventually merge it. Thank you again! /Kazunari.

@psoftware Hi, excuse me for having kept you waiting. I have just merged your PR into the master. Thank you again for the valuable fix. I appreciate that. Regards, Kazunari.

@kazunarikudo No problem at all! Thank you for reviewing the issue/pull request.
We are still working with Harvesters and we will be happy to contribute if any issue should arise in the future.
Thank you for your time!

@psoftware Hi Antonio, I am very happy to know that Harvester's been working for your business. That means a lot to me. I need to confess that my understanding of the issues to be addressed in the quality of Harvester is reflected, and it simply means the quality will never be beyond people's expectations. Thank you for your sincere patience and practical contribution!


use standard config directories

Proposed Changes

context https://github.com/projectdiscovery/goflags/pull/114
this PR updates default config directories used by uncover to standard ones
manually bumping goflags there by introducing auto-migration of old config files of uncover to new location
since path of config directory depends on setup  / environment /  distro it is printed with -version flag

$ ./uncover -version
[INF] Current Version: v1.0.6
[INF] Uncover ConfigDir: /Users/tarun/Library/Application Support/uncover

yeah, i think only users who are running nuclei / tools on nixOS and aws lambda are facing this issue . where Home folder is read-only in both cases and also in sandbox env with custom configs
ref: https://github.com/projectdiscovery/nuclei/issues/3576


Steam integration?

Will this library support Steam?
Thanks.

@Zyles It does support Steam, you need just to integrate it in.

I highly recommend https://github.com/Facepunch/Facepunch.Steamworks
Used in Rust (a game also developed with Unity)

@TylerOlsen Indeed!! @Zyles I never tested it, but with Facepunch or any steam wrapper, I heard Steam has little to no trouble integrating code into your game.

Steamworks integration was added in PR #143


Updates color palette with accessible alternatives that match AA

Updates color palette with accessible alternatives that match AA minimum contrast level. Updates some of vuepress classes to match identity.
Proposed Changes
The new color palette:
primary: #5d8000;
danger: #ed0030;
warning: #ad6500;
success: #008930;
info: #007aCa;
I still believe we could have some opinion from other users, but that's my bet on it. I know that the warning yellow is not very nice, though. And also, we may wanna rethink the hero section of the home page, the contrast really didn't work well with the emoji :/
An extra detail, I updated two vuepress classes to match the primary color on the "Show code" section of the documentation.

@elevatebart what do you think about it ?

Regarding the yellow, I've checked on other places like Bootstrap and WordPress that they end up using a black color text with the yellow background to solve the contrast issue. Its a bit more of work, thought.

It makes me think that I need to fix docgen-cli on windows 🤣
The color changes seem almost inconsequential and will make oruga better.
I like it.

@jtommy and @elevatebart, here is another option: the yellow goes dark text. That would be even better, AAA. And if we want to achieve AAA for the rest of the colors, then we would need to darken things a bit more...

This would be the color palette:
primary: #445E00;
danger: #B60000;
warning: #f4c300;
success: #006724;
info: #005C98;
To compare with the current proposal:

Even thought filled buttons loose a bit of their magic I think this darker colors do a great job for outlined buttons and form inputs. Check this out:

much clearer indeed

Went full AAA then guys. Lets see if we get used to it :)


Django testing - /posts url tests

Can you fix the conflicts first?

@TianZhiWang if it wasn't already up to date, now it is
@kylecarlstrom good call, I'd seen that article before and until just now I couldn't get basic auth to work :/ BUT, I did figure it out :) so that problem has since been fixed!


CORE-11905: Allow passing custom certificate as CRT file to REST Worker

LGTM - I take it that Bouncy Castle is not a new dependency to C5 then?

No, it is not. It is used by P2P and Crypto sub-systems already.


SDK Crash On Voyage When Invoking PublicKeyOf for Username "aa"

Description
When invoking the PublicKeyOf method for a specific username, the SDK crashes with the error:
data.startsWith is not a function.
This occurs while running a logic invoke for the logic ID:
0x0800002d6a50f8211797e168014c6be6949235418aaab01eac26074dcbdc86a50355d9

Steps to Reproduce

Use the SDK to run a logic invoke with the following logic ID: 0x0800002d6a50f8211797e168014c6be6949235418aaab01eac26074dcbdc86a50355d9
Attempt to invoke PublicKeyOf for the username "aa"
Observe that the SDK crashes and throws the error: data.startsWith is not a function

@sarvalabs-prakhar  The serialization issue occurs because the current implementation inadvertently trims the hexadecimal prefix when serializing a string argument, and the encodeArguments method was not correctly spreading the arguments. As a result, the system attempted to encode an array as a string, causing unexpected encoding behavior.

Here is issue with SDK it should prevent such mistake by providing the proper validation of types before encoding field.

@sarvalabs-prakhar Prefer to docs for usage encodeArguments


Error occurred while executing command

The error:
http://pastebin.com/9pG0fMyj
I have also tried these
/portal destination <PortalName> <x> <y> <z> (and with ,) and got a "Too many arguments!" message
/portal destination <world> <x> <y> <z> (and ,)and got a "too many arguments!"
/portal destination <portal name> <world:x,y,z> and got an error
There were others I tried.  None are working
Minecraft 1.10.2
Spongeforge 2147
PJP 0.13.6
Edit:
Looking at the commits on 0.13.6 I see there is a 0.13.7 that says it fixes this issue, but it's not in your releases on here.

/portal create <name> <world> -c <x,y,z>


ERROR: Package 'botasaurus' requires a different Python: 2.7.18 not in '>=3.7'

I have this error when i try to install botasaurus: ERROR: Package 'botasaurus' requires a different Python: 2.7.18 not in '>=3.7'
My python --version output:
Python 2.7.18
I also tried:
python -m pip install botasaurus --upgrade
logs:
% python -m pip install botasaurus --upgrade
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality.
Collecting botasaurus
  Using cached botasaurus-2.0.19.tar.gz (23 kB)
ERROR: Package 'botasaurus' requires a different Python: 2.7.18 not in '>=3.7'

You need to upgrade python, alternatively to test botasaurus you my run it in gitpod https://gitpod.io/#https://github.com/omkarcloud/botasaurus-starter

I got it. So I needed Python 3, not 2.7 :)
I misunderstood the error message


x/pkgsite: @master and @semanticversion show two different things

What did you do?
Visited https://pkg.go.dev/mellium.im/xmpp/form@master and<EMAIL_ADDRESS>which should currently match. I fetched this semantic version by visiting<EMAIL_ADDRESS>The second link works and shows the current package. The first link shows an old version.
I also tried running go get -u mellium.im/xmpp@master on a project hoping to force it to update, but after waiting several minutes nothing happened. Either way, if the current default branch version shows up when visiting the semantic version, I would assume it would also be updated when visiting the special @master link.
What did you expect to see?
The documentation should be the same.
What did you see instead?
The @master link shows an old version of the package even though a newer version exists in the database.

Forced a refetch of this module and it looks okay now so I'm going to close.

When a package is visited at @ master we add it to a reprocessing queue. Reprocessing will typically finish in a few minutes but can sometimes take much longer or may be subject to a rate limit.

I think this is still an issue. The issue is that if the semver of the master version is rendered I would expect master to update immediately too (since the docs have already been generated for that version). It seems like a bug that they show two different things even though it already knows about the new files, and the proxy already knows that this version is the current HEAD on the default branch.

I see what you're saying. I'll leave this open. Adding in some context.
When someone runs go get -u module@master for a version the proxy has not seen, the proxy will resolve that to module@semver, module@semver will be added to the new modules feed, and the pkgsite populates its processing queue with module@semver with no understanding of this new version being master.

FYI this remains an issue
At the time of writing, https://pkg.go.dev/cuelang.org/go@master resolves to v0.3.0-alpha5.0.20201207144701-6de877a926cf.  Whereas the proxy resolves to v0.3.0-beta.3.0.20210124142225-9c5489fc66ed:
cd $(mktemp -d)
go mod init mod.com
go get cuelang.org/go@master

gives:
go get: added cuelang.org/go v0.3.0-beta.3.0.20210124142225-9c5489fc66ed

cc @julieqiu

https://pkg.go.dev/cuelang.org/go@master should now be up to date. We're also working on a fix for this general issue.

https://pkg.go.dev/cuelang.org/go@master should now be up to date. We're also working on a fix for this general issue.


WinPhone Namespace incorrect

Hello,
Looks like the line should really be:
OxyPlot.Xamarin.Forms.Platform.WP8.Forms.Init();

"WinPhone" is not a namespace in the forms code, "WP8" is however.

Thanks I have updated the OxyPlot packages, see https://github.com/oxyplot/documentation-examples/commit/804d581860a641ab27bf71693cd34aa863d6ab8a


What the diffrence among GodPotato-NET2.exe GodPotato-NET35.exe and GodPotato-NET4.exe

Those are the .net versions @Yiaos


Fix travis-ci build

It looks like there's an incompatibility between the SSL certificate for JCenter and Gradle in Java 7.  From my research, there are a few possible workarounds:

Drop Java 7 from .travis.yml
Stop using HTTPS for accessing JCenter (jcenter() -> jcenter { url "http://jcenter.bintray.com/" })
Stop using JCenter (replace with mavenCentral())
Upgrade Gradle

I'm willing to try any of these fixes, but wanted to get your feedback before doing so.

Closing, as this project is now deprecated.


add a way to send a notification when an action is done

For example, it would be cool to have something like
echo "do my action | shell=~/myscript.sh notif=true"

so that when I click the action, my script runs, and once the script is done, I get a notification.
It would be extremely useful for scripts that take some time, and not just a few milliseconds.

It's possible to solve this yourself by using the control API to refresh the plugin at the end of the myscript.sh. I'm not sure what other kind of notification is possible.

I was thinking more like a regular macos notification, or something like https://github.com/BlueHuskyStudios/BHBezelNotification/ or anything else. Something that I could add when I want a way to know that something very obviously finished.

You can do it with Apple Script, see https://code-maven.com/display-notification-from-the-mac-command-line - hope this helps

It does, and that's what I'll do for now, but I think that would be a great addition like terminal=true, to have a notif=true or notif="Job Done!" or similar. If you agree, let's reopen, and I might even try to add this 😬. If not, then keep it closed.


case sensitivity of Path environment variable on windows

Trying to run swift from emacs on windows (niche use case, I know) I was running into an error about swift not being able to find "swift-test.exe". Checking environment variables, I think I've tracked this down to a combination of emacs using unconventional capitalization, and a case sensitivity inside of SPM.
When run from cmd.exe, the environment variable is Path=C:\..., but from emacs it's PATH=C:\...
From https://github.com/apple/swift-tools-support-core/blob/4d539ff4c3d75394a78e17f68b675ad82434dd71/Sources/TSCBasic/ProcessEnv.swift#L55-L62
it looks like swift is looking for the "Path" one and not doing the typical-on-windows case insensitive lookup.
This brings me finally to a question: Is this a swift bug and/or an emacs bug? As far as I understand, while "Path" is the official casing, environment variables are expected to be treated insensitively on windows (which works a bit unfortunately with swift's representation as [String: String])
I can create a PR to fix this, and I may file a bug against emacs as well, but I wanted to check first, since my windows experience is pretty limited.

I would say it is a bug on both sides.  emacs should use Path, however, Swift should be cognizant of the case insensitivity as well.

@cobbal not sure if this actually fixes the emacs issue, but is definitely a step in the right direction.  Unfortunately, we do need to audit the rest of the stack to handle this :(.


[BUG] Text chunking max_chunk_limit error

What is the bug?
Text chunking processor will produce the following exception if the number of produced chunks exceed max_chunk_limit. This would lead to data loss.
The number of chunks produced by text_chunking processor has exceeded the allowed maximum of [100]

How can one reproduce the bug?
Use text chunking processor and produce more chunks thank max_chunk_limit.
What is the expected behavior?
There should be no data loss. Suppose parameter max_chunk_limit takes the default value 100. if the generated chunks exceed 100, we only keep the first 100 passages into the results.
What is your host/environment?
Linux and Mac.
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.

Raised a PR to fix the bug: https://github.com/opensearch-project/neural-search/pull/717

Please elaborate the truncating logic and overall background description.

Expected behavior when we are perform chunking with delimiter algorithm with " " as delimiter and ["a b c", "", "", "d e f"] as the input.

When max_chunk_limit >= 6 or max_chunk_limit == -1, the output should be ["a ", "b ", "c", "d ", "e ", "f"].
When max_chunk_limit <= 2 and max_chunk_limit != -1, the output should be ["a b c", "d e f"].
When max_chunk_limit = 5, the output should be ["a ", "b ", "c", "d ", "e f"]
When max_chunk_limit = 4, the output should be ["a ", "b ", "c", "d e f"]
When max_chunk_limit = 3, the output should be ["a ", "b c", "d e f"].

@yuye-aws if PR has fixed the issue can we close it?

Sure. I am closing the issue.


Option to skip updating the dependencies

Currently, when you do pipenv install somepackage all of the dependancies and the subdependancies get updated to the latest compatible version. Please provide an option to skip this update. Installing just one package takes seconds. Downloading and calculating hashes for hundreds of files take more than half an hour. I would like to do this update on my own schedule, separate from installing a package.

https://pipenv.readthedocs.io/en/latest/#cmdoption-pipenv-install-skip-lock

@frostming this is not the same. I need a new lock file, including the new package, just without the update of the old.

I need a new lock file, including the new package, just without the update of the old.

I can't conclude from the issue description.
I put the link without a word in the last comment is to remind you to read the doc carefully -- it is there for a reason.
Per your update, --keep-outdated is what you want.


Don't let users create markets with invalid ballotTime or revealTime parameters

https://github.com/bitcoin-hivemind/hivemind/issues/57 is much more clear about what needs to be fixed.


customize text shadow

is there any way to customize the text shadow or is it baked in? i would like to decrease its intensity, it's a bit too prominent for my taste, and if I can match the font to my company's brand then i'd like to modify the shadow to be likewise

Hi @greg-wolff
So right now it's not configurable at all, just something I set myself. I did consider making it an option but I'm struggling a bit UI wise so I haven't added it yet.
While I'm ok having one common setting for all the info types for shadows, I really don't want to add one per info type (like a different shadow for clock and battery for example) as it's just too much and I'm trying to stay reasonable with features and settings. There are a few other options that are "common" to all the Infos, such as the margins and fades that I temporarily moved into the advanced tab (Info appearance tweak section).
Because the Infos shows as a list on the left column, I thought maybe having an advanced section somewhere in there that would show those. An easy out would be put a unmovable "Common" section at the top (I don't think common is a great name but you get the idea) with margins and the other stuff. But if I put them on top, it gives them importance (and they'll be selected as default when you open that tab, which would make them very visible).
So I thought put an "Advanced" at the bottom of the list, but since the list is reorderable, I'd have to make the last one non reorderable which is a bit of clunky and ugly, even maybe with a separator. I did consider having it "stuck" to the bottom of the list but that doesn't feel super mac like.
All this probably sound like rambling, sorry, in the meantime I'll probably add another field in advanced (it's super crowded) while I figure this out. Stay tuned, I'll get back to you.

hey @glouel, thanks for the really quick reply! perhaps the text styles could be handled by having the omnipresent section at the bottom of the list, similar to the "Users & Groups" settings tab. I think it could even work with a separator, but I understand it might be a messy development workflow because you noted it's reorderable. perhaps using the other pattern of having a plus, minus, and settings icon for the list could work as well, allowing users to add multiple messages (and perhaps hook them up to simmple api calls or something). then the text styles could live under the dropdown for settings on the list. either way, i appreciate your attention to detail and am excited to see the text shadows in the advanced tab
here's some mockups of my ideas

(ignore the context menu on the second example, just showing the idea)

I'm on a Windows PC right now, but isn't Aerial using the Mac OS Fonts Window when clicking the cog wheel? It already has all the settings required. Can those be used?

hey @glouel, thanks for the really quick reply! perhaps the text styles could be handled by having the omnipresent section at the bottom of the list, similar to the "Users & Groups" settings tab.

Yes !!! I was pretty sure I saw something like that somewhere in macOS, but couldn't remember where. That's exactly the one I was thinking about with the thing bolted down with a separator ! I'll have to investigate that one.

I think it could even work with a separator, but I understand it might be a messy development workflow because you noted it's reorderable. perhaps using the other pattern of having a plus, minus, and settings icon for the list could work as well, allowing users to add multiple messages (and perhaps hook them up to simmple api calls or something).

I've been going back on forth on the idea. The code is ready for the concept of adding/removing and having multiple, yep, that was part of my big rewrite, including potentially having multiples of stuff (except for the location info which is a bit special because it can be random, all the other ones can be multiples). My thinking was, on 1.7 at least, only messages truly makes sense to duplicate (although a case could be made with the fact that you can set things differently on multiple screens, say you have 2 screens and you want one clock top left and top right on the other screen, etc).
As I'm adding more and more Info types (that was the goal of the whole thing, I was currently implementing a very niche countdown feature), I was thinking about that again and that some of these types, instead of being disabled by default, should just not appear by default.

then the text styles could live under the dropdown for settings on the list. either way, i appreciate your attention to detail and am excited to see the text shadows in the advanced tab
here's some mockups of my ideas

(ignore the context menu on the second example, just showing the idea)

I wholeheartedly agree ! Thanks for taking the time to make the mockup, I'll let you know when I have a beta in the next few days.

I'm on a Windows PC right now, but isn't Aerial using the Mac OS Fonts Window when clicking the cog wheel? It already has all the settings required. Can those be used?

Hi @NiklasBr !
I'm not 100% clear how those work, but there are more options that what seems available with the API I use (things like the angle of the shadow, which as far as I understand, is not available in CoreAnimation). It might be distracting to have options that are available but not used. This is not a new problem, there's a color picker too that I don't use, I need to have a look at if I can select what appears there. Thanks for your input !

@greg-wolff https://github.com/JohnCoates/Aerial/releases/download/v1.7.2beta1/Aerial.saver.zip contains a shadow radius option in the Advanced tab. I haven't had a chance to work on the new ui, maybe this week end.

@greg-wolff beta2 now has that setting option, regrouping the various text stuff that was hidden in advanced :

https://github.com/JohnCoates/Aerial/releases/download/v1.7.2beta2/Aerial.saver.zip

@glouel awesome! the text settings panel looks great! i have one last request, is it possible to add shadow distance and opacity? most design tools have this feature, and for me, i'd like to try and disable the shadow so setting opacity would be helpful for me. thanks for such quick replies and updates. i love aerial!

I did have a look at the API and found those yep, I'll see what I can do in a future beta !

There you go, offsets and opacity :

https://github.com/JohnCoates/Aerial/releases/download/v1.7.2beta3/Aerial.saver.zip

Nice job! :)
Maybe add measurement labels: pixels/points/degrees to the various controls and inputs?

Yep good idea, it's in points for radius/offsets, and the slider goes from 0 to 100% opacity FYI. Will add that for next build.

Closing with 1.8.0 : https://github.com/JohnCoates/Aerial/releases/download/v1.8.0/Aerial.saver.zip


Using async fetch with promise.all on a synchronous internet connection

I have a super-fast full fibre 1gb internet connection which seems to be synchronous. Upload and download benchmarks are great. However. When run hundreds of tiny fetch in a promise.all configuration I notice that only about 2 or 3 fetch are reolved per second while I can resolve hundreds when using my 4G phone as a hot spot.
I created this test case for node 14.
const fetch = require('node-fetch')

const promises = []

for(var i = 0; i < 100; i++) {
  promises.push(fetch('https://geolytix.github.io/public/geolytix.svg'))
}

console.time('promise all')

Promise
  .all(promises)
  .then(arr => {

    console.log(arr.length)

    console.timeEnd('promise all')
  })
  .catch(error => {
    console.error(error)
  })

10 fetch over 4g take 0.2 seconds, 100 take 1 second.
With my gigabit internet connection 10 fetch requests take 4 seconds, and 100 take 50 seconds.

This is a unfair measurements cuz you are resolving the promise once you get the response headers... not when you have gotten the hole response body.
I would also look into using a custom user agent where you can configure the concurrency and also setting a keepAlive option
https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/node-reusing-connections.html

@bitinn can you maybe enable discussion in this repo for this kind of help question that isn't really an issue with node-fetch per say?

https://github.com/node-fetch/node-fetch#custom-agent
fetch(url, { agent: agent })

Unfortunately the results are exactly the same.
I pass in an httpsAgent with keepAlive as true like so:
const fetch = require('node-fetch')

const promises = []

const https = require('https');

const httpsAgent = new https.Agent({
	keepAlive: true
})

const options = {
	agent: httpsAgent
}

for(var i = 0; i < 100; i++) {
  promises.push(fetch('https://geolytix.github.io/public/geolytix.svg', options))
}

console.time('promise all')

Promise
  .all(promises)
  .then(arr => {

    console.log(arr.length)

    console.timeEnd('promise all')
  })
  .catch(error => {
    console.error(error)
  })

@jimmywarting Fair point about resolving once the headers are received.
I can change the promise array like so:
const getPromise = () => new Promise(resolve=>{

  fetch('https://geolytix.github.io/public/geolytix.svg', options)
    .then(response => response.text())
    .then(text => console.log(text))
    .then(() => resolve())

})

for(var i = 0; i < 10; i++) {
  promises.push(getPromise())
}

The behaviour is the same... Give or a take a few hundreds of a second.

Did you also try setting max sockets?
I know that browser did use to have like 6 or 12 a long time ago.

Hello there... setting maxSockets to 1 did massively speed the process up. Down to 1 second for 10 fetch requests. Same for 100 fetch requests.
const https = require('https');

const httpsAgent = new https.Agent({
  keepAlive: true,
  maxSockets: 1
})

const options = {
	agent: httpsAgent
}

const getPromise = () => new Promise(resolve=>{

  fetch('https://geolytix.github.io/public/geolytix.svg', options)
    .then(response => response.text())
    //.then(text => console.log(text))
    .then(() => resolve())

})

I'll close this... Thanks for your help. Much appreciated. :star::star::star: @jimmywarting

Conducted a own test with fetch version: "3.0.0-beta.10"
import fetch from './src/index.js';
import https from 'https'

for await (let max of [1, 2, 4, 8, 16, 12, 32, 64, 100]) {
	const httpsAgent = new https.Agent({
		keepAlive: true,
		maxSockets: max
	})

	var getPromise = () => fetch('https://geolytix.github.io/public/geolytix.svg', { agent: httpsAgent })
		.then(res => res.arrayBuffer()) // makes as litle text decoding as possible
		.then(ab => {}) // do nothing else

	var promises = []
	for (let i = 0; i < 100; i++) {
		promises.push(getPromise())
	}

	console.time(`concurrency, maxSockets: ${max}`)
	await Promise.all(promises)
	console.timeEnd(`concurrency, maxSockets: ${max}`)
}

// No agent at all

var getPromise = () => fetch('https://geolytix.github.io/public/geolytix.svg')
.then(res => res.arrayBuffer()) // makes as litle text decoding as possible
.then(ab => {}) // do nothing else

var promises = []
for (let i = 0; i < 100; i++) {
promises.push(getPromise())
}

console.time(`concurrency, no agent`)
await Promise.all(promises)
console.timeEnd(`concurrency, no agent`)

and also browser version:
getPromise = () => fetch('https://geolytix.github.io/public/geolytix.svg', {})
  .then(res => res.arrayBuffer()) // makes as litle text decoding as possible
  .then(ab => {}) // do nothing else

promises = []
for (let i = 0; i < 100; i++) {
  promises.push(getPromise())
}

console.time('concurrency, browser (chrome)')
await Promise.all(promises)
console.timeEnd('concurrency, browser (chrome)')

The result i got was
concurrency, maxSockets: 1: 4.080s
concurrency, maxSockets: 2: 7.940s
concurrency, maxSockets: 4: 883.019ms
concurrency, maxSockets: 8: 555.286ms
concurrency, maxSockets: 16: 830.911ms
concurrency, maxSockets: 12: 1.336s
concurrency, maxSockets: 32: 549.577ms
concurrency, maxSockets: 64: 290.405ms
concurrency, maxSockets: 100: 827.026ms
concurrency, no agent: 713.054ms
concurrency, browser (chrome):<PHONE_NUMBER>1875 ms

For me with a synchronous connections it is the other way around.
maxConnection 1, keep alive is fastest at around 0.8s... The more connections I allow the slower this gets.


Fix issue #1171

This is the PR to fix Issue #1171
Only changes in save_as() method are needed as the two open("r") versions now have the required encoding argument (with "utf-8" as the default string).
I've not added encoding_type string argument like has been done for the two open("r") versions in this file.
Can be added if you wish, but then ensure_ascii maybe should be too.
Plus if we add encoding_type (and ensure_ascii) here then we probably should do the same in synthesizer save_as method too.

At this point all I've done is exactly mirror the code that exists in synthesizer.save_as().

Hey @CAW-nz I think this is good enough for now, thanks!


upgraded to the latest modules from angular2 and ngbootstrap

this fixes issue #182
(make it work with angular ^2.0.0-rc.1 #182) https://github.com/valor-software/ng2-select/issues/182

+1

What's the status of this?
I see that the checks have failed, but from what I could see in the details, the failed checks are for not finding the '@angular' components.
If the build system has not been updated to ^2.0.0-rc.1, then obviously the checks will fail.

Sorry for delay, I will update ng2-select today, latest tomorrow

D:\meanproject\ng2-select-development>npm install

<EMAIL_ADDRESS>prepublish D:\meanproject\ng2-select-development
npm run flow.clean && npm run flow.compile

<EMAIL_ADDRESS>flow.clean D:\meanproject\ng2-select-development
del bundles coverage demo-build typings "components/**/*.+(js|d.ts|js.map)" di
st "ng2-select.+(js|d.ts|js.map)"

No se pudo encontrar D:\meanproject\ng2-select-development\bundles
El nombre de archivo, el nombre de directorio o la sintaxis de la etiqueta del v
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "D:\node\node.exe" "D:\node\node_modules\npm\bin\npm-cli.js
" "run" "flow.clean"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>flow.clean: del bundles coverage demo-build ty pings "components/**/*.+(js|d.ts|js.map)" dist "ng2-select.+(js|d.ts|js.map)"
npm ERR! Exit status 123
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>flow.clean script 'del bundles co
verage demo-build typings "components//*.+(js|d.ts|js.map)" dist "ng2-select.+
(js|d.ts|js.map)"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ng2-select package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     del bundles coverage demo-build typings "components//*.+(js|d.ts|
js.map)" dist "ng2-select.+(js|d.ts|js.map)"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ng2-select
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls ng2-select
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     D:\meanproject\ng2-select-development\npm-debug.log
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fseve
<EMAIL_ADDRESS>npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepublish script 'npm run flow.c
lean && npm run flow.compile'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ng2-select package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run flow.clean && npm run flow.compile
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ng2-select
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls ng2-select
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     D:\meanproject\ng2-select-development\npm-debug.log
D:\meanproject\ng2-select-development>clear

You will not be able to run it on windows, use osx or Linux


Dropping Python 2 support

Hello. Thank you for this awesome library!
I'm wondering if you have thought about removing Python 2 support?
The main benefit would be being able to move the type hints from the type stub library directly to the source implementation. This would simplify things for type-hint users because type hints would work out of the box, rather than needing to install a separate library and needing to ensure that MyPy points to the stubs.
--
Thanks to setup.py's python_requires, Python 2 users would safely resolve ordered-set==3.1.1 when calling pip2 install ordered-set. Meanwhile, Python 3 users would resolve the newest version, e.g. ordered-set==4.0.0.
That is, this won't negatively impact Python 2 users at all outside of missing possible future changes (although, this library seems very stable already).
--
Given the go-ahead, I'd be happy to put up a PR that inlines the type hints, tweaks setup.py, and runs MyPy in CI.
(Type stubs give some issues to the wrapper around MyPy that I'm using, so I would love to see this change and am eager to help however possible.)
--
Finally, see https://python3statement.org for precedent from most of the Python ecosystem for no longer supporting Python 2 once it goes EOL in 5 days. Includes Pytest, TensorFlow, Apache Spark, and Requests. https://python3statement.org

I realized that the typing change does not in any way depend on dropping Python 2, thanks to PEP 561. See https://github.com/LuminosoInsight/ordered-set/pull/60.
Due to the greater ecosystem initiative to drop support for Python 2, I still personally think it would be great to drop Python 2 support for new releases, although I understand possibly not wanting to do this because the burden of Python 2 support is so minimal for this library.
The benefits (I see) to dropping are:

Support the greater ecosystem initiative to drop Python 2.
Can use modern versions of tools like Pytest 5, whereas now you'd need to use Pytest 4.
Can inline the type hints, which improves code readability and reduces duplication.
Remove the collections vs. collections.abc compatibility code.

The downside is Python 2 users missing out on any future changes to this library (although they can keep using 3.1.1.). ordered-set seems to be a very foundational library and the maintenance burden is light, so I think both choices are compelling and justified.
Either way, thanks again for this awesome library!

I'm definitely interested in dropping Python 2 support and have a branch where I've started to do it. Would you like to take a look at https://github.com/LuminosoInsight/ordered-set/pull/61 ?


03/29/2018 02:42 : Create Pull Request for branch prTesting_2018032902 -> master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

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


Add filesystem-ag-driver

Add filesystem-ag-driver that provides generic filesystem interface to AG
The filesystem-ag-driver finds its backend-filesystem plugin from driver configuration file and dynamically loads the plugin.
Add iPlant DataStore backend plugin (iRODS + BMS)

Awesome, thanks!


Target annotations for Java 6

Hi!
I'm hoping you will consider this PR to target (just the) annotations for Java 6 (instead of the current target of Java 7).  The issue is that the error prone annotations are now used in recent guava versions (which still supports Java 6), and this can cause issues for some libraries (e.g. Jackson json library) which reflect on guava's annotations (e.g. see exception below).  This is easily solved by not including the error prone annotations at runtime (and normally they are not included at runtime since guava marks them as an optional dependency), but unfortunately the annotations must be included at runtime in order to support IBM Java 6 SR8 and prior due to http://www-01.ibm.com/support/docview.wss?uid=swg1IZ76354.  Let me know if this convinces you of the benefit of this PR or if we can discuss this further.  Thanks.
com/google/errorprone/annotations/concurrent/LazyInit : Unsupported major.minor version 51.0
java.lang.UnsupportedClassVersionError: com/google/errorprone/annotations/concurrent/LazyInit : Unsupported major.minor version 51.0
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:249)
	at sun.reflect.generics.factory.CoreReflectionFactory.makeNamedType(CoreReflectionFactory.java:95)
	at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:107)
	at sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:31)
	at sun.reflect.annotation.AnnotationParser.parseSig(AnnotationParser.java:370)
	at sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:181)
	at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:69)
	at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:52)
	at java.lang.reflect.Field.declaredAnnotations(Field.java:1014)
	at java.lang.reflect.Field.getDeclaredAnnotations(Field.java:1007)
	at com.fasterxml.jackson.databind.introspect.AnnotatedClass._constructField(AnnotatedClass.java:826)
	at com.fasterxml.jackson.databind.introspect.AnnotatedClass._findFields(AnnotatedClass.java:706)
	at com.fasterxml.jackson.databind.introspect.AnnotatedClass._findFields(AnnotatedClass.java:692)
	at com.fasterxml.jackson.databind.introspect.AnnotatedClass.resolveFields(AnnotatedClass.java:475)
	at com.fasterxml.jackson.databind.introspect.AnnotatedClass.fields(AnnotatedClass.java:284)
	at com.fasterxml.jackson.databind.introspect.POJOPropertiesCollector._addFields(POJOPropertiesCollector.java:350)
	at com.fasterxml.jackson.databind.introspect.POJOPropertiesCollector.collectAll(POJOPropertiesCollector.java:283)
	at com.fasterxml.jackson.databind.introspect.POJOPropertiesCollector.getJsonValueMethod(POJOPropertiesCollector.java:169)
	at com.fasterxml.jackson.databind.introspect.BasicBeanDescription.findJsonValueMethod(BasicBeanDescription.java:222)
	at com.fasterxml.jackson.databind.ser.BasicSerializerFactory.findSerializerByAnnotations(BasicSerializerFactory.java:348)
	at com.fasterxml.jackson.databind.ser.BasicSerializerFactory.buildMapSerializer(BasicSerializerFactory.java:764)
	at com.fasterxml.jackson.databind.ser.BasicSerializerFactory.buildContainerSerializer(BasicSerializerFactory.java:573)
	at com.fasterxml.jackson.databind.ser.BeanSerializerFactory._createSerializer2(BeanSerializerFactory.java:194)
	at com.fasterxml.jackson.databind.ser.BeanSerializerFactory.createSerializer(BeanSerializerFactory.java:153)
	at com.fasterxml.jackson.databind.SerializerProvider._createUntypedSerializer(SerializerProvider.java:1203)
	at com.fasterxml.jackson.databind.SerializerProvider._createAndCacheUntypedSerializer(SerializerProvider.java:1176)
	at com.fasterxml.jackson.databind.SerializerProvider.findPrimaryPropertySerializer(SerializerProvider.java:606)
	at com.fasterxml.jackson.databind.ser.impl.PropertySerializerMap.findAndAddPrimarySerializer(PropertySerializerMap.java:72)
	at com.fasterxml.jackson.databind.ser.BeanPropertyWriter._findAndAddDynamic(BeanPropertyWriter.java:854)
	at com.fasterxml.jackson.databind.ser.BeanPropertyWriter.serializeAsField(BeanPropertyWriter.java:671)
	at com.fasterxml.jackson.databind.ser.std.BeanSerializerBase.serializeFields(BeanSerializerBase.java:675)
	at com.fasterxml.jackson.databind.ser.BeanSerializer.serialize(BeanSerializer.java:157)
	at com.fasterxml.jackson.databind.ser.impl.IndexedListSerializer.serializeContents(IndexedListSerializer.java:119)
	at com.fasterxml.jackson.databind.ser.impl.IndexedListSerializer.serialize(IndexedListSerializer.java:79)
	at com.fasterxml.jackson.databind.ser.impl.IndexedListSerializer.serialize(IndexedListSerializer.java:18)
	at com.fasterxml.jackson.databind.ser.DefaultSerializerProvider.serializeValue(DefaultSerializerProvider.java:130)
	at com.fasterxml.jackson.databind.ObjectMapper.writeValue(ObjectMapper.java:2383)
	at com.fasterxml.jackson.databind.ObjectMapper.valueToTree(ObjectMapper.java:2515)

A couple comments (as someone more involved with Guava than with Error Prone):

Guava 20.0 is the last version of Guava to support Java 6. (You might already be aware of this; I just wanted to state it explicitly -- and go improve our docs while I'm at it.)
But even Guava 20.0 depends on a Java-7 version of error_prone_annotations. (As far as I can tell, all versions of error_prone_annotations are built for Java 7 -- except for a couple that were built for Java 8 before that was fixed.) I guess that we got away with this because, as you say, Guava omits the annotations at runtime by default. (We changed that in Guava 22.0, but since that version requires Java 7, anyway, it doesn't introduce compatibility problems.)

Now I don't know what the pros and cons of this are for Error Prone, but I wanted to record all that somewhere.

Hi @cpovirk, thanks for these details.  It's helpful to know that Java 6 support is never coming back in Guava.  In this case, I will probably just roll back from Guava 20 to Guava 18, before the Java 7 error prone annotations were introduced.

@trask We'll close this PR then, since you're planning to roll back your Guava version.

Hi @eaftan, I just tried rolling back to Guava 18, but I also use gRPC (which still supports Java 6), and depends on Guava 19.  Any chance to reconsider?  Thanks.


Column Offset Being Overridden

materialize-v0.97.3
A pretty glaring issue...
eg: I need a 'col s6' to be in the middle of the row, so I use 'offset-3':

(screenshot from Firebug)
This works fine on the http://materializecss.com/ website, but not on my local machine.
Unfortunately, the s6 has a left margin of zero, and as it comes after the offset in the style sheet, it overrides the margin on the offset.

(screenshot from Firebug, but same problem exists in Chrome)
The ghpages-materialize.css being used on the http://materializecss.com/ website is identical to the one in the materialize-v0.97.3.zip download file, except it is missing the [margin-left: 0;] on every <.row .col.xx> *.
If I remove the [margin-left: 0;] from every <.row .col.xx>, then it all works as it's supposed to (at least as far as I can tell).
I just thought I should bring this to your attention for the next release.
[note: I would add a codepen, but they are using v0.97.0 of the css, and it doesn't have this issue.]
*And has a bunch of extra page styling at the bottom, but that is inconsequential to the issue.

#2325, #2323, #2316, #2313, #2312, #2308.
Please people, try and use the search bar in issues first and search through closed issues. I will keep this issue open in hopes that more people don't keep opening issues.
To reiterate, fixed in d5db2a3. So if you need a fix asap you can either rollback your version, or get our github master version. We are working hard on squashing these bugs but a release won't happen for at least a week. We are setting up more elaborate tests with Jasmine and integrating with Travis CI to help but this will also take some time.
(Sorry @mattrixk if this seems personal. It is not, we've just seen this issue many times. I do appreciate the effort and quality of your issue tho :))

Ahh, wow. Oops. Sorry about that @acburst . That really is a lot of raised issues isn't it? I did a search for "offset" but didn't find anything, so I raised my own. I didn't think to try any closed issues.
Also, don't worry, no offence was taken, but I do feel a bit of a boob now. I shall endeavour to search more thoroughly in the future.

Oups, sorry @acburst , first time on GitHub!

Maybe the problem is that nobody searches for offset column, but instead for offset grid?

New release is out!


fix sdk-cli Cargo.lock

Hey @hydra-yse,
Wasn't urlencoding a liquid feature only crate of  sdk-common?

It's now also being used for bitcoin BIP21 serialization, so I removed the optional = true


Fix the duplicate block id on the Get Started page

Currently the subtitle in "Usage" and the subsection in "Base Icon Button" have the same identifiers. The second identifier is better to change.

Awesome thanks!


Fix str and local free bugs

This commit fixes a few safety bugs in the string and local ref code. It also cleans up the invoke code to make it easier to always free local refs. The HasEnvPtr trait was no longer providing any value so removed it along the way.
Bugs:

Returning an empty string from Java would result in writing to a null pointer, since Vec::with_capacity(0) does not allocate and the JNI string functions always write a trailing nul byte.
Allocate one extra byte in general when decoding Java strings to account for the trailing nul.
Always wrap the return result of JNI function calls that can return a Java object in a Local before doing anything else, like checking for an exception. This ensures Local::drop is called and the ref is correctly freed.
Fix up a few places where exceptions needed to be checked and weren't and vice versa.
Fix up ?Sized bounds so that "abc".to_java() compiles

Happy to merge and address further possible changes in a follow-up, as well