[FLINK-11876] Introduce new InputSelectable, BoundedOneInput and BoundedMultiInput interfaces

What is the purpose of the change
Adds new TwoInputSelectable, BoundedOneInput and BoundedTwoInput interfaces for stream operators to support selective reading and EndOfInput event processing.
Brief change log

Add new InputIdentifier class to represent the identifier for the input(s) of the operator.
Add new TwoInputSelectable class for two-input operators that can select the input to get the next StreamRecord.
Add new BoundedOneInput class for one-input operators that can process EndOfInput event.
Add new BoundedTwoInput class for two-input operators that can proceess EndOfInput event.

Verifying this change
This change is to add some new interfaces which will be covered by the tests of the implemention subtasks FLINK-11877 and FLINK-11878 .
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency):  no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers:  no
The runtime per-record code paths (performance sensitive):  no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector:  no

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? JavaDocs

The code has been updated, and please you review it again. @pnowojski @StefanRRichter

See the following links for the code of runtime implemention and benchmark.

All code
Benchmark executor
Quick link to class StreamTwoInputSelectableProcessor
Quick link to class NetworkInput

Benchmark for StreamTwoInputSelectableProcessor and StreamTwoInputProcessor

Measurement: throughput
Reading Mode: ANY
Testing Scheme

Mocks InputChannel which be constructed using static buffers to avoid the network overhead.
Creates two SingleInputGates for each input so that StreamTwoInputSelectableProcessor and StreamTwoInputProcessor have the same structure containingUnionInputGate.
Creates one InputChannel for each SingleInputGate, and fills the data buffer of the InputChannel using the record containing a long value.
Uses JMH to execute the benchmark:
@Fork value: 10
@Fork warmups: 1
Number of warmup iterations: 0
Number of measurement iterations: 1
Records per forked invocation: 500,000,000

Environment

JDK: OracleJDK 1.8.0_202, OpenJDK 1.8.0_40
OS: Linux 3.10.0
CPU: 96 cores  Intel(R) Xeon(R) Platinum 8163 CPU @ 2.50GHz

Results

StreamTwoInputProcessor
| 21338.181 ±(99.9%) 373.656 ops/ms [Average]
| (min, avg, max) = (21038.197, 21338.181, 21975.121), stdev = 247.151
| CI (99.9%): [20964.524, 21711.837] (assumes normal distribution)

StreamTwoInputSelectableProcessor
| 22000.049 ±(99.9%) 191.925 ops/ms [Average]
| (min, avg, max) = (21806.272, 22000.049, 22181.491), stdev = 126.946
| CI (99.9%): [21808.125, 22191.974] (assumes normal distribution)

Summary

StreamTwoInputSelectableProcessor is about 3% faster than StreamTwoInputProcessor in throughput.
Repeated tests show that the test results are basically stable.
Using OpenJDK, the results are roughly the same.

Result Analysis

The reason for being a bit faster is that StreamTwoInputSelectableProcessor uses hot loop to process StreamRecord as much as possible, and StreamTwoInputProcessor exit the loop after processing a StreamRecord.
If StreamTwoInputSelectableProcessor exit the loop after processing a StreamRecord, it is about 6% slower than StreamTwoInputProcessor. After efforts, attempts have been made to implement the code which may be friendly to JIT, failing to eliminate the performance regression.

Concerns

If the actor model which is introduced in the future needs to exit the loop after processing a StreamRecord, there will be regression in performance.

The code has been updated, renamed InputSelectionBuilder to Builder, and the unit test has been added for Builder.

👏👏👏

Thank you for reviewing. @pnowojski @StefanRRichter @JingsongLi


TestGenerateCatalogWithExternalNodes

resolves https://github.com/dbt-labs/dbt-core/issues/9481

Problem

No test for catalog generation for external nodes
Solution
Add TestGenerateCatalogWithExternalNodes

Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
[x] This PR includes type annotations for new and modified functions

@aranke There's no where to port it to because 1.6.latest generate does not use a ResourceTypeSelector: https://github.com/dbt-labs/dbt-core/blob/1.6.latest/core/dbt/task/generate.py
This is not an issue in 1.6.latest, just putting a test in for good measure.


Updates to 1.1.0.M2

@spencergibb FYI

:+1:

@meltsufin ,
I believe now we need to merge the second commit from @spencergibb , otherwise we fail on CI during pushing 1.1.0.M2 artifact: https://jenkins.spring.io/blue/organizations/jenkins/spring-cloud-gcp-master-ci/detail/spring-cloud-gcp-master-ci/437/pipeline

Here it is: https://github.com/spring-cloud/spring-cloud-gcp/pull/1045


Syntax error in installation script

Compatible OS

[X] I'm running Raspotify on a compatible OS

Latest Version

[X] I'm running the latest version of Raspotify

Due Diligence

[X] I have done my due diligence

What happened?
The installation of Raspotify via install.sh fails due to a syntax error. This was still working a few days ago, so I suspect a regression.
Relevant log output
$ curl -sL https://dtcooper.github.io/raspotify/install.sh | sh
sh: 60: Syntax error: "(" unexpected (expecting "then")

duplicate of https://github.com/dtcooper/raspotify/issues/517

Run the following instructions (Use bash instead of sh)
sudo apt-get install apt-transport-https
curl -sL https://dtcooper.github.io/raspotify/install.sh | bash
Also note that support for Raspotify on Buster has been dropped. You need to run it on Bullseye.
Already raised in issue 517 See https://github.com/dtcooper/raspotify/issues/517

Thanks! It works now. Btw, I did run this on Bullseye in the first place and had the syntax error there.

Glad it is working. I have left a comment in https://github.com/dtcooper/raspotify/issues/517 that the page at https://github.com/dtcooper/raspotify/ ought to be updated with the corrected installation instructions.


Add spread test cases

Cadl Ranch Contribution Checklist:

[x] I have written a scenario spec
[x] I have meaningful @scenario names. Someone can look at the list of scenarios and understand what I'm covering.
[x] I have written a mock API
[x] I have used @scenarioDocs for extra scenario description and to tell people how to pass my mock api check.

@iscai-msft @timotheeguerin @weidongxu-microsoft Could you help review these cases?

Java should have supported the spread. Not sure about .NET

@chunyu3 Could you comfirm that these cases are supported in .NET?

Can we add one more scenario: Spread an Alias which contains model as property?
model Thing {
  @doc("name of the Thing")
  name: string;
  @doc("age of the Thing")
  age: int32;
}

alias ThingAliasWithModel = {
  @path id: string;
  ...Thing;
  @header top: int32;
};

op spreadAliasWithModel( ...ThingAliasWithModel ): OKResponse;

Pls notice the case is not updated because the discussion is not finalized https://github.com/Azure/cadl-ranch/pull/247#discussion_r1157859847


[OpenSearch Playground] Adds prod cluster config files

Signed-off-by: Tao liu<EMAIL_ADDRESS>Description
Adds prod cluster configuration files to repo, which were used for creating EKS cluster in prod.
Issues Resolved
#38
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

better to add some information about test steps.


[Multi-Device Conversation][DotNet] Cannot set display name when create/join conversation.

I tried to implement the code according to the example at the link: https://github.com/Azure-Samples/cognitive-services-speech-sdk/blob/master/quickstart/csharp/dotnet/multi-device-conversation/helloworld/Program.cs. But when I set display name (nickname) " await conversationTranslator.JoinConversationAsync(conversation, displayName)". Then I catch the event "ParticipantsChanged" but in it I only get Id and DisplayName as "Host" or "Participant" but not the display name I set.
Is this problem due to my account subscription or is there a problem with my code?
Thanks.

When I catch the Transcribed or Transcribing event it's the same. Just get DisplayName="Host" or DisplayName="Participant 1"


Can't get rid of folder with umlaut in folder name

Expected behavior
I have changed the folder for drafts to "Drafts" instead of "Entwürfe", and have deleted the "Entwürfe" folder on the server. I have refreshed the folder list on the phone, The folder should now be gone forever.
Actual behavior
When re-starting K-9, the old "Entwürfe" folder re-appears, and I get sync errors for it (because it does no longer exists on the server).
(NegativeImapResponseException: Command: EXAMINE "Entw&APw-rfe"; response: #4# [NO, Mailbox doesn't exist: EntwÃ¼rfe (0.000 secs).])
When refreshing the folder list, the folder is gone until I restart K-9 again, and then "Entwürfe" is back, etc.
Steps to reproduce

Create folder with umlaut in name
Delete folder on server
Refresh folder list on phone
restart K-9

Environment
K-9 Mail version: 5.202
Android version: 6.0.1
Account type (IMAP, POP3, WebDAV/Exchange): IMAP

Go to 'Account settings > Folders > Drafts folder' and select your new drafts folder.

I have done that, as I've said above. I have a "Drafts" folder that is used for drafts, and a un-dead "Entwürfe" folder.

Can you please export the settings and check if the file contains any reference to the old folder name?

Yup:
       <folder name="Entwürfe">           <value key="inTopGroup">false</value>           <value key="integrate">false</value>         </folder>

I've tested this on my tablet, and it's even worse there. Even folders without special characters stay there forever, and after refreshing the folders from the server, I sometimes get three identical inbox folders.
Android 6.0.1
K-9 5.202
IMAP

I've now gone back to the server, and the deleted folders also reappeared there, even though I have definately deleted them there before. Did K-9 recreate these folders from its configuration?
I've then changed the server to fix the folders there and not accept new folders from clients. Now finally after refreshing the folders in the client, the unwanted folders are gone for good.


FLUME-3217 . Creates empty files when quota

As it can be seen in FLUME-3217, Flume creates empty files when HDFS quota has been reached.
This is a first approach to the solution. It works although a better approach it could be implemented.
The idea is to capture the quota Exception in order to delete this annoying empty files generated by flume.

Can one of the admins verify this patch?

Hi @szaboferee I have reproduced the environment and you are right.
I could happen that if the quota is reached in the middle of a “transaction”, the all file dumps.
It is necessary to check if the file weight is zero before doing any delete operation. Moreover it will be necessary to implement some sort of “stopper” in the “append” function of the BucketWriter class in order to achieve the expected behavior.
I will try to do the modifications asap. Thank you and sorry for the stupid mistake.

Hi @szaboferee sure, I will add a test with minicluster. Now I am uploading a new version as I am having some trouble with test part in local.

@ffernandez92 thanks for the contribution.
I guess this problem can be quite painful.
For performance reasons I would go another way to fix this problem. I would add a check to the close() function. It would check after successful close if the file length is 0. That is simple to implement and would happen only after a close. If the close was not called from a catch block, we could omit this for further speed.
I guess, still there could be a problem when the quota is exceeded, Flume can get into a sort of infinite loop as it tries to write the same event to HDFS again and again. Some sort off backoff should be implemented to reduce load. Needs to be checked if it is true.
Let me know please, what you think.

Hi!
Sorry for the late answer I’ve been a little bit under a rush lately. I think you are right @szaboferee about the performance degradation.
I think that the solution you are proposing @majorendre it was also my first approach. But it was also problematic because of what you were saying about the infinite loop when quota was reached in the middle of a write.
I will try to reformulate the solution trying both approaches to see which one would be better.


Zombie.JS doesn't support javascript loaded via document.write

Hi,
I've been having trouble with zombie.js testing when using the Google Maps API. I originally thought the problem was with the resources using query parameters in the URL. This appeared to be incorrect, here's my test for that:
css = new Browser();
css.visit('http://other.localhost/bugs/zombiejs/gmaps/css.html', function() {
	console.log();
	console.log('Calling css.html (CSS loaded with query string ...');
	console.log('Title : ' + css.text('title'));
});

Where css.html was
<!doctype html>

		<title>Google Maps ZombieJS Bug</title>
		<link href="reset.css?time=1325674256" rel="stylesheet" type="text/css"></link>

Hello World

Here's my test case for zombie for testing to see if the bug is indeed a problem with document.write loaded scripts.
test case
write = new Browser();
write.visit('http://other.localhost/bugs/zombiejs/gmaps/write.html', function() {
	console.log();
	console.log('Calling write.html (Javascript loaded via document.write...');
	console.log('Title : ' + write.text('title'));
});

write.html
<!doctype html>

		<title>Google Maps ZombieJS Bug</title>

Hello World

write.js
var src = 'head.js';

document.write('<' + 'script src="' + src + '"' +
                   ' type="text/javascript"><' + '/script>');

head.js
alert('Bye World');

output
Calling write.html (Javascript loaded via document.write...
Title : <!doctype html>

		<title>Google Maps ZombieJS Bug</title>

Hello World

Using<EMAIL_ADDRESS>

No it doesn't. The default HTML parser doesn't support document.write.
I highly recommend not using document.write because it blocks the rendering loop, whereas adding script element allows JavaScript evaluating in parallel with page rendering for faster page speed.


Ubuntu repo issues

VSCode Version: Any
OS Version:
Distributor ID:	Ubuntu
Description:	Ubuntu 17.10
Release:	17.10
Codename:	artful

Steps to Reproduce:

sudo apt update

Results in:
Get:12 http://packages.microsoft.com/repos/vscode stable/main amd64 Packages [38.1 kB]
Err:12 http://packages.microsoft.com/repos/vscode stable/main amd64 Packages
  File has unexpected size (38219 != 38059). Mirror sync in progress?
  Hashes of expected file:
   - Filesize:38059 [weak]
   - SHA512:d960bc2562e8e3914627b1f8a255d6e78506acac42c7c540d6ce09c4d20f0447edb9d2596b87bb64d1d59e4786a89f7c9f7711743d057d10041f95cf8a7f7dd1
   - SHA256:692a9d9348b76a7ab30c112a4e1f4e99a8ba99454ec1ed4a5c82d1afa45c43f7
   - SHA1:4dfaf756f7b30988ddacc77863a363ffd6f409a4 [weak]
   - MD5Sum:256db81b96e2ac1ef30d0d1c63545b85 [weak]
  Release file created at: Fri, 26 Jan 2018 18:29:25 +0000

E: Failed to fetch http://packages.microsoft.com/repos/vscode/dists/stable/main/binary-amd64/Packages.bz2  File has unexpected size (38219 != 38059). Mirror sync in progress?
   Hashes of expected file:
    - Filesize:38059 [weak]
    - SHA512:d960bc2562e8e3914627b1f8a255d6e78506acac42c7c540d6ce09c4d20f0447edb9d2596b87bb64d1d59e4786a89f7c9f7711743d057d10041f95cf8a7f7dd1
    - SHA256:692a9d9348b76a7ab30c112a4e1f4e99a8ba99454ec1ed4a5c82d1afa45c43f7
    - SHA1:4dfaf756f7b30988ddacc77863a363ffd6f409a4 [weak]
    - MD5Sum:256db81b96e2ac1ef30d0d1c63545b85 [weak]
   Release file created at: Fri, 26 Jan 2018 18:29:25 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.

Does this issue occur when all extensions are disabled?: N/A

@Tyriar
Get:8 https://packages.microsoft.com/repos/vscode stable InRelease [2.802 B]
Get:9 https://packages.microsoft.com/repos/vscode stable/main amd64 Packages [43,2 kB]
Err:9 https://packages.microsoft.com/repos/vscode stable/main amd64 Packages
  File has unexpected size (43609 != 43234). Mirror sync in progress? [IP: <IP_ADDRESS> 443]
  Hashes of expected file:
   - Filesize:43234 [weak]
   - SHA512:1bd713bc0ff5f583b7427cd7f70bb378c324980df8db6a6480a03eade92b9a30ccdc4a0e58f35206035c073c6a64d3ca3775442d483a392c08a2918f85ee90f9
   - SHA256:e311c67fbc37c451043b20183bb3782b7a679d2fb488d5888f581b4393535934
   - SHA1:d86fe0862f1d85589ef2a620b4115951c028def0 [weak]
   - MD5Sum:755a820b77a2c96e347e9239f349abee [weak]
  Release file created at: Wed, 14 Mar 2018 06:38:24 +0000
Hit:10 http://dl.google.com/linux/chrome/deb stable Release
Fetched 2.802 B in 1s (3.279 B/s)
Reading package lists... Done
E: Failed to fetch https://packages.microsoft.com/repos/vscode/dists/stable/main/binary-amd64/Packages.bz2  File has unexpected size (43609 != 43234). Mirror sync in progress? [IP: <IP_ADDRESS> 443]
   Hashes of expected file:
    - Filesize:43234 [weak]
    - SHA512:1bd713bc0ff5f583b7427cd7f70bb378c324980df8db6a6480a03eade92b9a30ccdc4a0e58f35206035c073c6a64d3ca3775442d483a392c08a2918f85ee90f9
    - SHA256:e311c67fbc37c451043b20183bb3782b7a679d2fb488d5888f581b4393535934
    - SHA1:d86fe0862f1d85589ef2a620b4115951c028def0 [weak]
    - MD5Sum:755a820b77a2c96e347e9239f349abee [weak]
   Release file created at: Wed, 14 Mar 2018 06:38:24 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.

https://github.com/Microsoft/vscode/issues/45868


Cannot apply autocmd BufNew for help file

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled May  2 2021 18:02:30)
MS-Windows 32-bit console version
Included patches: 1-2824
Compiled by mool@tororo
Huge version without GUI.  Features included (+) or not (-):
+acl                +comments           +find_in_path       +listcmds           +popupwin           -sun_workshop       +vertsplit
+arabic             +conceal            +float              +localmap           -postscript         +syntax             +virtualedit
+autocmd            +cryptv             +folding            -lua                +printer            +tag_binary         +visual
+autochdir          +cscope             -footer             +menu               +profile            -tag_old_static     +visualextra
+autoservername     +cursorbind         +gettext/dyn        +mksession          -python             -tag_any_white      +viminfo
-balloon_eval       +cursorshape        -hangul_input       +modify_fname       -python3            -tcl                +vreplace
+balloon_eval_term  +dialog_con         +iconv/dyn          +mouse              +quickfix           +termguicolors      +vtp
-browse             +diff               +insert_expand      -mouseshape         +reltime            +terminal           +wildignore
++builtin_terms     +digraphs           +ipv6               +multi_byte_ime/dyn +rightleft          -termresponse       +wildmenu
+byte_offset        -dnd                +job                +multi_lang         -ruby               +textobjects        +windows
+channel            -ebcdic             +jumplist           -mzscheme           +scrollbind         +textprop           +writebackup
+cindent            +emacs_tags         +keymap             -netbeans_intg      +signs              -tgetent            -xfontset
+clientserver       +eval               +lambda             +num64              +smartindent        +timers             -xim
+clipboard          +ex_extra           +langmap            +packages           +sound              +title              -xpm_w32
+cmdline_compl      +extra_search       +libcall            +path_extra         +spell              -toolbar            -xterm_save
+cmdline_hist       -farsi              +linebreak          -perl               +startuptime        +user_commands
+cmdline_info       +file_in_path       +lispindent         +persistent_undo    +statusline         +vartabs
   system vimrc file: "$VIM\vimrc"
     user vimrc file: "$HOME\_vimrc"
 2nd user vimrc file: "$HOME\vimfiles\vimrc"
 3rd user vimrc file: "$VIM\_vimrc"
      user exrc file: "$HOME\_exrc"
  2nd user exrc file: "$VIM\_exrc"
       defaults file: "$VIMRUNTIME\defaults.vim"
Compilation: cl -c /W3 /GF /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32  -DFEAT_CSCOPE -DFEAT_TERMINAL -DFEAT_SOUND  -DFEAT_JOB_CHANNEL -DFEAT_IPV6      -DWINVER=0x0501 -D_WIN32_WINNT=0x0501 /source-charset:utf-8 /MP -DHAVE_STDINT_H /Ox /GL -DNDEBUG /arch:IA32 /Zl /MT /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_HUGE /Fd.\ObjCi386/ /Zi
Linking: link  /nologo /opt:ref /LTCG:STATUS oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib  comdlg32.lib ole32.lib netapi32.lib uuid.lib /machine:i386   libcmt.lib  user32.lib          winmm.lib WSock32.lib Ws2_32.lib  /PDB:vim.pdb -debug

I'm using vim-autoresize for resize focused buffer.
augroup autoresize
    autocmd!
    autocmd BufNew * call autoresize#resize()
augroup END

BufNew works fine for all buffer except help file. I don't know why I can't apply affect to help file. How to solve this problem?

When I try this I can see the BufNew autocommand triggered also for help buffers.

Oh, I found the issue in here, because this line:
autocmd BufWinEnter * if &buftype == 'help' | wincmd L | endif

I used it for opening vertical help file, but it incompatible with this plugin, I don't know how to mix my config with that, both are autocmd.

so this is an issue with your configuration and those two configurations seem to contradict a bit.
Please ask user questions on the vim_use mailinglist or use vi.stackexchange.com. This here is a bug tracker for problems with Vim. We cannot provide individual help here. Closing.

so this is an issue with your configuration and those two configurations seem to contradict a bit.
Please ask user questions on the vim_use mailinglist or use vi.stackexchange.com. This here is a bug tracker for problems with Vim. We cannot provide individual help here. Closing.

I believe this is a bug cause by wincmd L because not only this plugin but also lens.vim is broken with
autocmd BufWinEnter * if &buftype == 'help' | wincmd L | endif
You can try to reproduce this with minimal vimrc have autocmd like above and lens.vim. You will see.

If you want to report a bug, please open a new issue and provide a minimal reproducible example and clearly state what is wrong and what you expect.  Don't just mention it is brocken
Thanks.

If you want to report a bug, please open a new issue and provide a minimal reproducible example and clearly state what is wrong and what you expect. Don't just mention it is brocken
Thanks.

Sorry, I don't know how to say it right because my English is bad.

CTRL-W L	Move the current window to be at the far right, using the full
height of the screen.  This works like closing the
current window and then creating another one with
:vert botright split, except that the current window
contents is used for the new window.

Like the help file said, wincmd L moves the current window but also resize the window, it is unexpected behavior.
It should just move the current window to the left and respect the current width of window.

Not like the help file said, wincmd L moves the current window but it also resize the window -> unexpected behavior.

The fact that :wincmd L resizes the window is documented at :help CTRL-W_L:
                                                *CTRL-W_L*
CTRL-W L        Move the current window to be at the far right, using the full
                height of the screen.  This works like closing the
                current window and then creating another one with
                `:vert botright split`, except that the current window
                contents is used for the new window.

Notice the "using the full height of the screen" part.

It should just move the current window to the left and respect the current width of window.

Not sure but have a look at the vim-tradewinds plugin, or the win_splitmove() function.
If you decide to use the plugin, try to find the right sequence of keypresses to move the help window in the position and with the geometry that you want.  For the sake of the example, let's say it's abcd.  Then, replace this autocmd:
autocmd BufWinEnter * if &buftype == 'help' | wincmd L | endif

With this one:
autocmd BufWinEnter * if &buftype == 'help' | execute 'normal abcd' | endif

Just a suggestion, but since we sometimes have questions here, maybe we could open a discussions forum on github.  It would allow us to transfer questions out of the issue tracker.
FWIW, the fish shell has opened one about 4 months ago, and the kitty terminal open theirs about a year ago.

I am fine with enabling discussions.
Personally I just found them to be not so super helpful, because I still get them as notifications in my mail box and think those are issues and only later I notice it. But whatever.

Not like the help file said, wincmd L moves the current window but it also resize the window -> unexpected behavior.

The fact that :wincmd L resizes the window is documented at :help CTRL-W_L:
                                                *CTRL-W_L*
CTRL-W L        Move the current window to be at the far right, using the full
                height of the screen.  This works like closing the
                current window and then creating another one with
                `:vert botright split`, except that the current window
                contents is used for the new window.

Notice the "using the full height of the screen" part.

It should just move the current window to the left and respect the current width of window.

Not sure but have a look at the vim-tradewinds plugin, or the win_splitmove() function.
If you decide to use the plugin, try to find the right sequence of keypresses to move the help window in the position and with the geometry that you want. For the sake of the example, let's say it's abcd. Then, replace this autocmd:
autocmd BufWinEnter * if &buftype == 'help' | wincmd L | endif

With this one:
autocmd BufWinEnter * if &buftype == 'help' | execute 'normal abcd' | endif

Just a suggestion, but since we sometimes have questions here, maybe we could open a discussions forum on github. It would allow us to transfer questions out of the issue tracker.
FWIW, the fish shell has opened one about 4 months ago, and the kitty terminal open theirs about a year ago.

Thanks for your answer. I found solution for my issue. Simply:
autocmd BufWinEnter * if &buftype == 'help' | wincmd L | execute 'vertical resize '. g:autoresize_width |endif


Fix: reject signing

Task linked: CU-86931gtkf WalletConnect. Reject is not processed on signing screen


Update data-loss-prevention-policies.md

Minor change as label as a condition is GA

@chrfox Please review


2024-01-06T20:10:35+00:00

2024-01-06T20:10:35+00:00

2024-01-06T20:10:35+00:00

2024-01-09T00:12:14+00:00

Thanks for the effort!
But usually i don't maintain the Phishtank rules in the repository - Perhaps in the future i will setup a scheduled push. I will update everything on monday for a fresh push. I'm only accepting outside merge requests if it's updated og additions to the custom rules and not if you refresh the whole repo.


Wait till the database is ready before returning response?

I'm using this library in some vitest tests. I have it being launched before all tests, and then some tables are created. However, the script to create tables runs right after the launch command, at which point the database isn't actually ready to communicate with, it's just been launched.
Is there anyway to launch the database, but only have the Promise returned when the database is actually ready? Otherwise, I have to rely on a high number of connection retries for my DynamoDB client

+1


Allow INFN redirector to be used when no sites are found with -ws option

This introduces  a new feature in build_datasets script, which allows to use INFN redirector prefix in cases when no white-listed sites were found f or a given file (using the -ws option). At the moment a Warning is printed when this happens, which may be suppressed in the future.
My use case is the following. Most of the datasets are copied to some German T2s but not all of them. I want to preference those sites, but when the sample is not there, just use the redirector:
build_datasets --cfg samples.json -o -ws T2_DE_RWTH  --use-infn

The behavior should be the same as before, when the flag is not used.

Thanks for the changes, I think we are missing only adding the option in the documentation of the analysis example and Dataset handling pages. May you add it there please?

Ok updated documentation as well.
There may be some spurious changes due to removing white spaces at the end of lines, should be harmless

Thanks!! ready to go!


images disappeared of docker hub?

https://hub.docker.com/r/ptlange/kube-backup/tags
there used to be a 1.12.0 tag - but the newer tags seems to be gone.
zup?

Weird. Must be some bug with the github<>dockerhub build integration. It always seemed janky. I'll reupload soon.
But highly recommend to host your own images since you're giving my own janky bash code an awful lot of permissions in your clusters :P


Add support for posting interactive messages

I'm starting to brainstorm how I can add support for interactive messages in PoshBot. Creating a interactive message using PSSlack with a bit of extra properties on the attachment object is easy enough but it would be nice if PSSlack supported those constructs natively.
Example of posting interactive message
$tok = '<your-token>'

$attParams = @{
    Text = 'Choose a game to play'
    Fallback = 'You are unable to choose a game'
    Color = '#3AA3E3'
}
$att = New-SlackMessageAttachment @attParams
$att.callback_id = 'wopr_game'
$att.attachment_type = 'default'
$att.actions = @(
    @{
        name = 'game'
        text = 'Chess'
        type = "button"
        value = "chess"
    }
    @{
        name = "game"
        text = "Falken's Maze"
        type = "button"
        value = "maze"
    }
    @{
        name = "game"
        text = "Thermonuclear War"
        style = "danger"
        type = "button"
        value = "war"
        confirm = @{
            title = "Are you sure?"
            text = "Wouldn't you prefer a good game of chess?"
            ok_text = "Yes"
            dismiss_text = "No"
        }
    }
)

$text = 'Would you like to play a game?'
$m = New-SlackMessage -Channel 'testing' -Text $text -AsUser -Attachments $att
$m | Send-SlackMessage -Token $tok -Verbose

Maybe the following new parameters could be added to New-SlackMessageAttachment to support button and menus?

callback_id
attachment_type
actions

New functions for creating the button/menu actions and just a single Actions parameters on New-SlackMessageAttachment could also make sense. Food for thought.
Reference
Interactive Buttons
Interactive Menus

Awesome idea! Yeah, would definitely make sense to abstract it out - I like the first idea, a bit more flexible from what I can tell, or at least, less complexity and fewer assumption in parsing?
Sort of tied up with a fun neo4j module; if anyone wants to take this feel free! Otherwise will remove the help wanted tag if I can find time
Cheers!


AWS SQS/SNS Wrong queue access policy (broken in last version (1.5.0))

Expected Behavior
When some service is subscribed to many topics it's queue should have an access policy than allows all subscribed topics to publish events to the queue.
Actual Behavior

Currently the generated queue access policy has a condition that only allows one of the topics to publish events to it.
Tested that it is not always the same topic (I assume the last subscribed topic rewrites policy and restricts access to itself only)
Generated access policy example:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"Service": "sns.amazonaws.com"
},
"Action": "sqs:SendMessage",
"Resource": "arn:aws:sqs:region:XXXXXXXXX:your-service-name",
"Condition": {
"ArnEquals": {
"aws:SourceArn": "arn:aws:sns:region:XXXXXXXXX:lasttopicname"
}
}
}
]
}
In the previous version of dapr 'Condition' is not specified at all.
Seems to be broken with this commit:
https://github.com/dapr/components-contrib/commit/e9deaf37812131bca5d2c610572e290e92bb34ce
restrictQueuePublishPolicyToOnlySNS() method should add new sources to condition but not override existing
Steps to Reproduce the Problem
Create a test app that subscribes to few (>1) topics. Run the app with AWS SQS/SNS component configured for pubsub.
Check that instead of allowing all subscribed topics to publish to created queue it only allows it to one of them
in generated queue access policy.
Release Note

RELEASE NOTE:
Fixed bug with SQS/SNS wrong queue access policy

@amimimor Sorry for tagging you directly, but probably you can implement a quick fix for it

@amimimor please comment here with /assign.

@yaron2 we need to re-open this issue as I found and fixed another issue related to the fix (localstack testing appear to be inadequate in terms of resource access policies)


Update create-apps-for-teams-meetings.md

update response payload for updated getParticipant API

Docs Build status updates of commit 132817c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[AMQ-9545] Set cache-control to no-store by default for stronger security

Unspecified Cache-Control HTTP header is vulnerable. Set it to no-store to avoid caching sensitive data for stronger security. It should be the default unless users override it.
Reference: https://www.virtuesecurity.com/kb/cache-controls-explained/

Messed up branch history due to outdated branch and wrong operation with git.


Forms

Hello 👋 Reviewer,
In this project, I have added forms to my Blog app.
Project requirements

Create forms to perform the following functions:

Creates a Post on behalf of the current_user (use the method that you created in your ApplicationController).

Create a comment on behalf of the current_user (use the method that you created in your ApplicationController).

Allow Users to add likes to Posts.

Thanks, @DammyShittu  for this feedback but all linters all passing well.🥳👍🏼


vCloud Launcher should take multiple files as input

As webops I don't want to use a for loop to use many vapp definition files, I would like to be able to run vcloud-launch once:
vcloud-launch file-1.yaml file-2.yaml

https://www.pivotaltracker.com/story/show/66654822

Thank you for your interest in this project but we now consider it
both feature complete for our own usage and in maintenance mode.
While we will not be investing any more development time in this
project we may still include pull requests.


Custom_id_from_id_fields

When creating a DataEntry object, you can now add an optional field, id_fields, which has a default value of ['source', 'text'] currently, and which will use the elements of the id_fields list (concatenated) to create the string that will then be hashed to yield the DataEntry's id. This means that stampy, for example, has the dataentry section changed to:
return DataEntry({
"source": self.name,
"source_type": "markdown",
"url": url,
"title": question,
"authors": ['Stampy aisafety.info'],
"date_published": self._get_published_date(entry),
"text": answer,
}, id_fields=['url'])
Which means stampy now uses the 'url' only for id_fields. All sources are then easy to modify this way. One glaring problem is that the 'url' in fact does not uniquely describe stampy entries, since some entries have the same url (something to investigate)

I see this newest commit doesn't quite work bc it won't let me do
STAMPY_REGISTRY = [
    Stampy(name='aisafety.info', id_fields=['url']),
]
```, not sure why yet but it should be an easy fix

I see this newest commit doesn't quite work bc it won't let me do
STAMPY_REGISTRY = [
    Stampy(name='aisafety.info', id_fields=['url']),
]
```, not sure why yet but it should be an easy fix

probably a dataclass thing

ok I went in circles until I found out about KW_ONLY, and now I'm still kind of going in circles but hopefully less.
@mruwnik
so right now the plan is to have
class Alignmentdataset:
    # blabla
    id_fields: List[str] = field(default_factory=lambda: ['url', 'title'])

    # blabla
    def make_data_entry(self, data, **kwargs):
        return DataEntry(dict(data, **kwargs), id_fields=self.id_fields)
    # blabla

class DataEntry(UserDict):
    def __init__(self, *args, id_fields=None, **kwargs):
        super().__init__(*args, **kwargs)
        for k, default in INIT_DICT.items():
            if k not in self:
                self[k] = default and default()
        # Store id_fields in a way that does not interfere with UserDict's functionality
        self.__id_fields = id_fields

and the problem seems to be that in the tests we use DataEntry directly. is it weird to have the "default value" of ['url', 'title'] be defined twice in two different places? I could set it to a default in AlignmentDataset, and then a default in DataEntry which realistically would only be used if it was created independently of AlignmentDataset, which it should only do during tests. It seems a bit suboptimal, so do you reckon it's fine or is there a better way you can think of

Hmmm I see, so now DataEntry is kind of a private class of AlignmentDataset, and I change the tests to reflect that

ok done, but the conflicts means you gotta approve it again


Duplicate ID in Header Corpus

I am trying to incorporate RNNSharp, and I started with Grobid's training code.  I noticed that some of the corpus tei documents have the same xml:id.  I think this incorrect, and causes ambiguity.
e.g.
1105.header.tei.xml and header1036.tei have the same xml:id of 1105.  I think this creates an ambiguity between 1105._PEER_stage2_10.1088%2F0022-3727%2F43%2F7%2F075201.header and 1105.header.
The other duplicates that I have found for headers are 5, 200, and 387.

Hello Christopher,
You're right, this is ambiguous and the trainer might fail to align *.header.tei.xml and .header files for this training example.
I am working now again on the header model to update the format, the features and the training data (the header model was the first one to be developed, and there are quite a lot of things to fix - so I include this problem, many thanks.


Fixed published time and modified time for Structured data

closes #12059
Published Time and Modified Time were not populating for 'page' context because it is an extension of 'post' and hence there was no context 'page'. Fixed it by handling this scenario for published time and modified time

@ErisDS : Yeah you are right, my bad I had overlooked it. I have updated the PR with the fix.


Using external variables or commands in mup.json

Hi @arunoda,
Im currently working on a meteor app and using meteor up to deploy it to a google compute engine vm.
Mongodb is hosted on Compose so in my mup.json i have the following MONGO_URL...
"env": {     "MONGO_URL": "mongodb://<username>:<password>@somurl",   }
The thing is, i don't want to insert the username and password directly in the mup.json and push it to github.
With Compute Engine it is possible to store things in custom metadata and retrieve them using:
curl http://metadata.google.internal/computeMetadata/v1/instance/attributes/mongourl -H \ "Metadata-Flavor: Google\"
Is it possible to use a command as MONGO_URL value that wil be executed when running meteor deploy? Somthing like this..
"MONGO_URL": "curl http://metadata.google.internal/computeMetadata/v1/instance/attributes/mongourl -H \"Metadata-Flavor: Google\""

Sorry. This the current way.
We have no plans to change how mup.json works.
mup.json is a private file and should not be shared.
Seems like you need to something specific to Google Cloud.
May be you can env. variables directly from it rather than depending with
mup.json.
On Wed, Apr 15, 2015 at 8:23 PM Jeroen Gijsman<EMAIL_ADDRESS>wrote:

Hi @arunoda https://github.com/arunoda,
Im currently working on a meteor app and using meteor up to deploy it to a
google compute engine vm.
Mongodb is hosted on Compose so in my mup.json i have the following
MONGO_URL...
"env": {
"MONGO_URL": "mongodb://:@somurl",
}
The thing is, i don't want to insert the username and password directly in
the mup.json and push it to github.
With Compute Engine it is possible to store things in custom metadata and
retrieve them using:
curl
http://metadata.google.internal/computeMetadata/v1/instance/attributes/mongourl
-H
"Metadata-Flavor: Google"
Is it possible to use a command as MONGO_URL value that wil be executed
when running meteor deploy? Somthing like this..
"MONGO_URL": "curl
http://metadata.google.internal/computeMetadata/v1/instance/attributes/mongourl
-H "Metadata-Flavor: Google""
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/376.

@arunoda found a different solution :)
Travis automatically deploys the app using mup so thats why i needed the mup.json file in the repo.
With Travis you can encrypt files and let Travis decrypt it when its running the .yml file.
I added the encrypted mup.json file to the repo and my problem is solved!
http://docs.travis-ci.com/user/encrypting-files/
Btw meteor-up is awesome dude :)

Okay. That's good solution.
On 2015 අප්‍රේල් 16, බ්‍රහස් at ප.ව. 5.42 Jeroen Gijsman <
<EMAIL_ADDRESS>wrote:

Closed #376 https://github.com/arunoda/meteor-up/issues/376.
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/376#event-282994513.


New release ?

Would it be possible to enjoy a new release of django-push-notifications ? It has been one year and half since no release and I can see several commits the community could benefit from, given that Django 4.0 is out and that the current 2.0.0 release emits the following  warnings :
/venv/lib/python3.8/site-packages/push_notifications/models.py:235: RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().
    verbose_name=_("User public encryption key"),

Thanks for this package, keep up the good work!

Would be really nice to have a new release because the current released version does not supports Django 4.0.
it raise the following error.
File "push_notifications/admin.py", line 3, in <module>
   from django.utils.encoding import force_text

ImportError: cannot import name 'force_text' from 'django.utils.encoding'

Just to add - it also doesn't work with current versions of PyJWT, which make life very difficult when using other packages rely on the new PyJWT API.

Ditto, code needs updated for compatibility with Django 4.0.
The following conflicting lines:
from django.utils.encoding import force_text
from django.utils.translation import ugettext_lazy as _

should be updated to:
from django.utils.encoding import force_str
from django.utils.translation import gettext_lazy as _

The required fixes seem to already be present: https://github.com/jazzband/django-push-notifications/commit/ff1337798ce00a059edeccb9702c1c6db61a6bf8
we just need a new release created

The force_text was replaced with force_str in ce2140fccecb83cb2bf4203424bbdd47f44428ea.

Thank you @bigfootjon and @sevdog, I concur. We are awaiting a release. Any known issues holding it up?

@simonkern Would it be possible to create a new release?

I only opened two or three pull requests, but have no permissions regarding this package.

@simonkern  Thanks for the fast response. Do you know who has? It is a really nice package, and it would be a pity to lose it due to the lack of new releases.

Sorry everyone, I have pypi access

Which commit are we using for the release?

Latest commit from ‘master’ seems fine to me. It has some missing migrations in it. 4.0 support landed a few commits before that

OK I'll use db0606c908b669d9803cdfc26fca0926cb059fd3

It will be 2.1.0

Thanks for getting this out, but if it's not too late, the version number should probably be 3.0.0 since it's dropping support for Django 1.x:
https://github.com/jazzband/django-push-notifications/compare/2.0.0...master#diff-fa602a8a75dc9dcc92261bac5f533c2a85e34fcceaff63b3a3a81d9acde2fc52R32

any updates?

@jleclanche could you create this release.  Apparently when I restored my phone, it reset my authenticator app so I am currently locked out of pypi

@jleclanche and @jamaalscarlett Is there something in particular about not feeling comfortable with a new release? Not clear what the hold up is.

@bradleydworak I don't feel comfortable doing a release on this project because I haven't done one in years and I don't use the library anymore to test it / know if it's ready for a release.

@jleclanche I am using the latest master for a while, and its sending push-notifications to IOS and Android.
The current version 2.0.0 does not support Django 4.0 which is a blocker for many people. and a new release would unblock it.

 But I am not comfortable doing it myself.

Could the version be bumped to 3.0 and it released? That would be lower risk since people shouldn't be hit with the package upgrading under them and then more testing can happen for those that are ready to make the upgrade.

Sorry about the delay everyone
https://github.com/jazzband/django-push-notifications/releases/tag/3.0.0
https://pypi.org/manage/project/django-push-notifications/release/3.0.0/


Teach nad how to register multiple checks in the same config

It's still necessary to have nad listen on multiple ports (i.e. -p 2611 -p 2612), but this allows a single config to register multiple check bundles.

Updated to support edge case re: missing checks/check.


Replaced FileSystem newInputStream and newOutputStream

We used to have the following methods in FileSystem
  InputStream newInputStream(Path file)
  OutputStream newOutputStream(Path file, OpenOptions ... options)

Besides the names being very generic (and thus unclear), the OpenOptions also was a constant point of discussion. I therefore decided to replace these calls with:
 InputStream readFromFile(Path file)
 OutputStream writeToFile(Path file)
 OutputStream appendToFile(Path file)

This (hopefully) makes the semantics of writing more clear. writeToFile will give you a stream for writing to a file, creating it if needed, or overwriting it if it already existed. appendToFile will give you a stream to append to the end of an existing file.
This way OpenOptions is no longer needed. This saves confusion on the user side and complexity on the implementation side.

I've also added:
 OutputStream writeToFile(Path file, long size)

This is a variation specifies the size of the data that will be written in advance. Some adaptors (like S3) seem to need this.


 There seems to be no error in the code. It compiles and runs perfectly, but after some time I get this.
Observed behavior
ERROR in Error [ERR_IPC_CHANNEL_CLOSED]: channel closed
    at ChildProcess.target.send (internal/child_process.js:588:16)
    at AngularCompilerPlugin._updateForkedTypeChecker (/home/sibiraj/Documents/myapp/node_modules/@ngtools/webpack/src/angular_compiler_plugin.js:361:34)
    at Promise.resolve.then (/home/sibiraj/Documents/myapp/node_modules/@ngtools/webpack/src/angular_compiler_plugin.js:209:22)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)

closing as it is already open in #8331


Suggestions on JBrowseR

JBrowseR is very useful. However, I want to suggest two features:

tracks(...) needs to detect name collision.
For example, when I add two VCF tracks, abc.prog1.vcf.gz and abc.prog2.vcf.gz, both will have the name values abc. Then the browser will not render either file correctly.
search by gene names.
currently, users can specify genomic location, but cannot search specific gene names. JBrowse CLI seems to support it (link: https://jbrowse.org/jb2/docs/combined/#indexing-feature-names-for-searching), but JBrowseR does not seem to support it now.

Hey @zhanxw , thanks for both suggestions. We can work on incorporating these features.

Honestly, I think this tool is much worse that other tools that have been published, it's really hard to use, and I got lots of errors during installation. It's really useless to me.

@Spartanzhao if you are interested in describing what errors you got, we can try to help. please avoid venting your frustrations like this though, it's not kind or helpful

@cmdcolin this person just had a paper rejected in JOSS that I was a reviewer on. I think he's a bit upset about that.
It has reminded me, I need to find time this weekend to update JB2 in this package! 😄

A new release is on its way to CRAN with a new function text_index() supporting gene name search.
Check out example_apps/hg38_index_app.R for example usage!
While it may be worth avoiding name collisions down the road, I haven't implemented this feature yet—it's probably best to avoid data files with duplicate names.


redirect cron stdout to docker

@chrisys & @catt-tung ,
Figured I would just clear all the issues while I was in the repo. 🤣
Just needed to redirect the cron stdout to the docker proc. Also redirected stderr to stdout just in case.
resolves balenalabs/inkyshot#17

@chrisys
Sorry! I found a problem in the crontab entry. I had added an extra * somehow. Fixed and squashed the commits. You'll need to review again.

@SamEureka no worries, thanks again for this batch of contributions!


The instruction for Vue is out-of-dated

Hi, ifabreges
Thanks for the great plugin.
It took me a while figuring out how to make it work on my nativescript-vue project.
As nativescript-vue has been updated to 2.0.
The following settings work for me.
in main.js file
const application = require("application");
const localize = require("nativescript-localize");
application.setResources({ L: localize });
Vue.filter("L", localize);
in abc.vue file
 works like charms while  will yield errors.

I tested it and adding the L pipe to the application resources isn't required. It seems that nativescript is not taking into account the modified strings file at build time, it only takes it into account during the next build. I don't know how to fix that for now.

It just doesn't work for me...
Whatever I try it always crash with a message saying _vm.L is not a function.


PWX-28770 Add pod metric test template

Signed-off-by: dahuang<EMAIL_ADDRESS>What this PR does / why we need it:
Adds a sample test that fetches data from loggly.
Eventually we will use the loggly data to compute pod hour based on the deployed application.
Which issue(s) this PR fixes (optional)
Closes # PWX-28770
Special notes for your reviewer:
Local test passed.

Hi @dahuang-purestorage can you give the command you used and log of this run? Jus wanted to know how describe inside a describe works

@lsrinivas-pure Describe inside a Describe works fine in ginkgo. All ginkgo context blocks operate the same, just print logs differently. i.e. Describe, When, Context.
Are there any issues with this PR or can we get it merged? @lsrinivas-pure @nikolaypopov

Hi @dahuang-purestorage can you give the command you used and log of this run? Jus wanted to know how describe inside a describe works

...
STEP: Validate Px pod restart count
STEP: Getting current restart counts for portworx pods and matching
INFO[2023-02-16 13:29:45] Verifying : Description : loggly return code 200 not equal to 200
INFO[2023-02-16 13:29:45] Actual:200, Expected: 200
INFO[2023-02-16 13:29:45] Verifying : Description : loggy return empty response
INFO[2023-02-16 13:29:45] Actual:false, Expected: false
...
• [SLOW TEST:144.053 seconds]
{PodMetricFunctional}
/home/dahuang/go/src/github.com/portworx/torpedo/tests/basic/podmetric_test.go:20
  {PodMetricsSample}
  /home/dahuang/go/src/github.com/portworx/torpedo/tests/basic/podmetric_test.go:39
    {SamplePodMetricTest}
    /home/dahuang/go/src/github.com/portworx/torpedo/tests/basic/podmetric_test.go:54
      has to fetch the logs from loggly
      /home/dahuang/go/src/github.com/portworx/torpedo/tests/basic/podmetric_test.go:44


Allow custom config path

Currently only '.licensee.json' is allowed.
I would like to have two configs, one for production deps, and another for all deps.

Consider committing two configurations to your Git tree and symlinking one or the other to .licensee.json in your npm or other build scripts.


New YAML cert test cases

Problem
Adding the following cert test cases:
Test_TC_MC_2_1, Test_TC_MC_3_1, Test_TC_MC_3_2, Test_TC_MC_3_3, Test_TC_MC_3_4, Test_TC_MC_3_5
Change overview

New YAML files the will generate new test cases from the Cert test plan.
The generated code from the YAML files.
Added ability to organize test names in zapt file.

Testing

Manually generated code
Manually compiled code
Ran tests with the chip-tool against Linux node

Looks like you have some conflicts ..

/rebase

/rebase


Fancy Zones, iterate through layouts with right click

Description of the new feature / enhancement
A feature for fancy zones where instead of simply having one layout available through right click, you can iterate through multiple layouts.
Say you have N layouts defined on a monitor, right clicking while holding left click would cycle between layout 1, layout 2...layout N and no layout.
Current functionality is Layout, no layout.
Scenario when this would be used?
Sometimes I want my monitor split in half, other times thirds, would be cool if you could add multiple layouts per monitor and cycle through them by right clicking while dragging instead of the current functionality of toggling between fancy zone or normal window dragging.
Supporting information
No response

I support the suggestion to toggle the layout functionality.
But I have a different opinion about the key combination that triggers this feature.
Is it possible to switch layouts by scrolling up and down with the mouse wheel while dragging the window? Because the right button has been assigned to turn zone activation mode on or off.


Roll engine 47841ebad0bf..f9ce01674ed6 (1 commits)

https://github.com/flutter/engine/compare/47841ebad0bf...f9ce01674ed6
git log 47841ebad0bf0ad12ead16a3e67b766292c98f07..f9ce01674ed6dcdf6ad3c5b80cef6277d851cb50 --no-merges --oneline
f9ce01674 Roll src/third_party/skia c0b32b33552c..fec9b902a626 (3 commits) (flutter/engine#9169)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (cbracken@google.com), and stop
the roller if necessary.

Auto-roller completed checks. About to merge.


Add Spanish to Crowdin

Hello, I would like to translate GazellePW into Spanish language. Could you please add it to Crowdin?
Thanks.

done.


Add line numbers to EoS script editor

Obsolete, script editor will be scrapped and concepts reused in a newer version once psy_commando's statsutil is better integrated.


Provider DLL failed to initialize correctly

I just got v20170220, and I get this error when trying to run PixivUtil2.exe.
Traceback (most recent call last):

File "PixivUtil2.py", line 12, in <module>

File "urllib2.pyc", line 94, in <module>

File "httplib.pyc", line 80, in <module>

File "mimetools.pyc", line 6, in <module>

File "tempfile.pyc", line 35, in <module>

File "random.pyc", line 885, in <module>

File "random.pyc", line 97, in __init__

File "random.pyc", line 113, in seed

WindowsError: [Error -2146893795] Provider DLL failed to initialize correctly

In fact, it looks like the last version I can run is pixivutil20160513, everything from 20160613 on gives me that error. I'm still running Windows XP on this machine, could that be the cause?

I think so. Someone from my blog also have the same issue and he/she uses windows Vista.
The only information that I know is from http://bugs.python.org/msg248951
It might related to your pc environment variable that SystemRoot is not set.
You can check by typing ‘SET’ on the cmd console and look for ‘SystemRoot=C:\WINDOWS’. I think you can set it by ‘SET SystemRoot=C:\WINDOWS’ before running the app in the console.

That's strange, I just checked that and SystemRoot=C:\WINDOWS seems to be properly set here.

Can you rename/delete crypt32.dll from the installation folder?
reference: http://stackoverflow.com/a/31222117

Sorry for the slow reply, after doing that PixivUtil2.exe just shows a blank screen for a few seconds and then I get a Windows error dialog.

can you copy winxp c:\Windows\System32\crypt32.dll to the pixiv downloader folder?

Nope, still a Windows error.

welp, then I have no other idea.
Maybe run it from source code?

Download and install latest Python 2.7 from http://www.python.org/
Download the source code and extract it on some folder (e.g. c:\pixivutil)
Download the required library:
a. Open cmd window and navigate to where you install the python, and go to the script folder (e.g. C:\Python27\Scripts)
b.  run: pip install -r c:\pixivutil\requirements.txt
Run the PixivUtil2.py by double clicking it or from cmd using python.exe c:\pixivutil\PixivUtil2.py

Sorry for taking so long to reply back, after things happened I ended up installing Windows 7 on this same machine. Given how recent versions of pixivutil are still crashing for me (but now listing numpy.core.multiarray.pyd as the faulty module in Windows 7's error dialog), I find it likely that the reason might be something that's plagued me in trying to run many programs on this computer: the fact that its CPU is a very old Athlon XP, which doesn't have support for SSE2 instructions.
I'm not sure if anything more can be done at this point (and I can't even provide more assistance in regards to the original error), so please feel free to close this issue.

Removing crypt32.dll worked for me.  ✔


⚠ St. Lawrence Global Observatory CKAN Sitemap has degraded performance

In be12858, St. Lawrence Global Observatory CKAN Sitemap (https://catalogue.ogsl.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 24684 ms

Resolved: St. Lawrence Global Observatory CKAN Sitemap performance has improved in af92361 after 14 minutes.


Warning:Failed propType

i got this error. I on RN 0.25. and i already rnpm link

Many icons in Ionicons 3.0.0 have new names, I know this is a breaking change that's why it's released as 2.0. :-)

Let's keep the discussion about Ionicons upgrade here: https://github.com/oblador/react-native-vector-icons/issues/200


Please consider using FontAwesome for your icons

🎉 Thanks for taking the time to contribute to 🌲Evergreen! 🎉
It is highly appreciated that you take the time to help improve 🌲Evergreen.
We appreciate it if you would take the time to write up a bug report or feature request.
Sadly, if we don't receive enough information, or the issue/feature request doesn't
align well with our roadmap, we might respectfully
thank you for your time, and close the issue.
Bug fixes and documentation fixes are welcome.
In the case of a bug report 🐞
Please consider the following items when filing a bug report:

Issue and steps to reproduce.
Versions.
Screenshots.
Expected.
Actual.
Link to your project.
Browser name and version.
Operating system.

In the case of a feature/component request ✍
Please consider the following items when filing a feature request:

Usage, component API if applicable.
Design Example, screenshot of what the design should look like.
Problem that feature/component addresses.
Examples in other projects of feature/component.
Screenshots if design changes.

See the contributing guide for more details.
Respect earns Respect 👏
Please respect our Code of Conduct, in short:

Using welcoming and inclusive language.
Being respectful of differing viewpoints and experiences.
Gracefully accepting constructive criticism.
Focusing on what is best for the community.
Showing empathy towards other community members.

We don't plan on supporting FontAwesome at this time, but we will consider if it makes sense for some future version of Evergreen to support BYO-icon library.
We'd have to use something for defaults icons that are included in some components (like close X icons and such) with the ability to replace those with your own... TBD.


Spamed UserWarnings till Juputer Notebook kernel dies.

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
MacOSX x86
Modin version (modin.__version__):
10.15.2
Python version:
3.8.13
Code we can use to reproduce:
Trying to modify a large List of dicts in a column in pandas with:

tmp = pd.DataFrame(training_set_data['descriptors_and_weights'].tolist()).stack().apply(         pd.Series)
Describe the problem

Getting spammed this:
UserWarning: Distributing <class 'dict'> object. This may take some time.
Till my Jupyter notebook and kernel crashes. Finds no way to skip this error.

@joelostlund thank you for reporting your issue.
If you want the function you're applying in modin.pandas.Series to itself return a series, you should return pandas.Series instead of modin.pandas.Series. This is a bug in Modin mentioned here. I think you're getting a warning because you're making a Modin series for every single element in the result of the stack. Every time you make a Modin series, you'll get that warning.
So please try:
import pandas

tmp = pd.DataFrame(training_set_data['descriptors_and_weights'].tolist()).stack().apply( pandas.Series)

and let me know whether that works.

Thanks for the answer! Still getting another issue though.
UserWarning:Series.tolist` defaulting to pandas implementation.
UserWarning: Distributing <class 'list'> object. This may take some time.
AttributeError                            Traceback (most recent call last)
/var/folders/7k/zky42bzn36q0pn3wgv4f60tw0000gp/T/ipykernel_26668/1348720331.py in
1 import pandas
2
----> 3 tmp = pd.DataFrame(training_set_data['descriptors_and_weights'].tolist()).stack().apply( pandas.Series)
~/.pyenv/versions/3.8.12/envs/delivery-notebooks/lib/python3.8/site-packages/modin/logging/logger_metaclass.py in log_wrap(*args, **kwargs)
66             logger.info(f"END::PANDAS-API::{class_name}.{method_name}")
67             return result
---> 68         return method(*args, **kwargs)
69
70     return log_wrap
~/.pyenv/versions/3.8.12/envs/delivery-notebooks/lib/python3.8/site-packages/modin/pandas/series.py in apply(self, func, convert_dtype, args, **kwargs)
680                 return result
681         else:
--> 682             result = getattr(sys.modules[self.module], return_type)(
683                 query_compiler=result
684             )
AttributeError: module 'modin.pandas.series' has no attribute 'DataFrame'
`

@mvashishtha I forgot to tag you so just tagging back on my post above.

@joelostlund I can reproduce that error on modin 0.15.2 with script:
import modin.pandas as pd
import pandas

pd.Series(1).apply(lambda x: pandas.Series([x, x]))

But with the latest Modin source I get a slightly different error. I'm closing this issue in favor #4734, which is dedicated to this bug. Please follow progress there.


[stable/fluent-bit] Capabilities.APIVersions condition checks

Is this a request for help?: No

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug Report

Version of Helm and Kubernetes: Helm 2.12.3, Kubernetes 1.9.11
Which chart: stable/fluent-bit
What happened: helm template does not produce the correct rbac api version due to an empty Capabilities.APIVersions map used. This is a known issue: https://github.com/helm/helm/issues/3377, but can be resolved for this chart by changing the conditions used in _helpers.tpl. Example resolution here: https://github.com/helm/charts/pull/11031/files
What you expected to happen: The chart should default to the v1 rbac api and check for v1alpha1 and v1beta1 specifically
How to reproduce it (as minimally and precisely as possible):

Clone the charts repository
Change active directory to stable/fluent-bit
Run helm template . > test.yaml
Observe the rbac apiVersion is always rbac.authorization.k8s.io/v1alpha1, even if the cluster only has v1beta1 or v1.

I can take this on, as it's relatively trivial.

I am also facing this issue and the corresponding pull request isn't closed. Can this issue be reopened?


Sqlite3 Threading Issue

Deployment of app in wsgi currently showing the following exception when doing database operations.
sqlite3.ProgrammingError: SQLite objects created in a thread can only be used in that same thread.The object was created in thread id<PHONE_NUMBER>26720 and this is thread id<PHONE_NUMBER>04832

Resolved in #100


WeightReduction

I am having problems with weightreduction. It´s related to stackable ítems.
-First stack of an item u get into a bag Will get weightreduction but it Will do no effect.
-If u get the stack back, part of the weight Will remain in the bag, so puting it in and getting it back Will increase the weight of the bag.
-If u add a stack of an ítem that is already inside the bag it Will work and Will stack with the ítem that is already in the bag. But this Will not fix the first stack u put inside.
-Ítems with diffrent weightreduction can stack together.
-There is a random factor on this issue. Sometimes it Works like i Said, other times Works as it should work, and other it never work.
tested with:
[ITEMDEF i_xbag]
ID=i_bag
NAME=xbag
TYPE=t_container
on=@DropOn_Self
argo.weightreduction=50
on=@PickUp_Self
argo.weightreduction -=50

Seems like spliting item is triggering pickup_self trigger to all stack but when you split the stack, the items left in the container doesn't trigger dropon_self trigger. So game directly see them as picked up from container and remove the bonus.

weightreduction is percentage
this working:
on=@DropOn_Self
	argo.weightreduction=50
on=@PickUp_Self
	argo.weightreduction=0

The problem is stacks not working well under @DropOn_Self and @PickUp_Self triggers, so here is a simple fix you can use;
ID=i_bag
NAME=xbag
TYPE=t_container
TEVENTS=e_itemt

On=@Create
Timer=1

On=@DropOn_Self
ARGO.WEIGHTREDUCTION += 50
IF !(<ARGO.isEvent.t_e>)
  ARGO.EVENTS +t_e
ENDIF

[TYPEDEF t_e]
On=@PickUp_Stack
IF !(<ARGO.isEvent.t_e>)
  ARGO.EVENTS +t_e
ENDIF
WEIGHTREDUCTION -= 50
EVENTS -t_e

On=@PickUp_Pack
IF (<dARGN1> == <dAMOUNT>)
  WEIGHTREDUCTION -= 50
  EVENTS -t_e
ENDIF

On=@DropOn_Self
ARGO.WEIGHTREDUCTION += 50
IF !(<ARGO.isEvent.t_e>)
  ARGO.EVENTS +t_e
ENDIF

[function f_Reags_Al_Libro]
ref1=<ARGV[1]>
ref2=<ARGV[0]>
ref3=<ARGV[2]>
FORCONT
if  == t_reagent
ref2.sysmessage @,,1 You add  of  in reagent book.
cont =
WeightReduction = <ref1.tag0.reduce>
endif
endfor
Well, I tried many ways. I use to do it by this function as well and it dosnt work. it is not about the trigger.
I have a fix by script for the issue, but the fix does not worth for normal containers.
The problem is when u get the items into de bag, not when u take them off.
If u have already a Stack inside, it Will work often, if the bag is empty it use to fail. I am not the only one having problems with this.
Did you check it? Test it deeper cos it is broken.
Btw I am rastrero.


Create Test spec for Audio Settings

Create Test spec for Audio Settings that covers L2, L3 and L4.

duplicate of issue #29


v2.9.0

This is an automated message from CI:
Docker Image for build 1 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-1064
Note: ensure you backup your NPM instance before testing this PR image! Especially if this PR contains database changes.


Add React Tracking (Analytics) to Emission

For #692
Link to React-Tracking
Changes

[x] Add react tracking as dependency
[x] Add custom dispatch function
[x] Test tracking on a method (e.g. Artist Follow)
[x] Went for compositition over inheritance (:wink: @alloy), changed all root VCs in the AppRegistery to no longer extend RootContainer, but return and render a RootContainer component.

TODO

[x] Add segement (through Eigen => using the emission module we'll continue to rely on ARAnalytics, keeping in place Segment, Adjust, and our debugging popovers)
[x] Clean up / extract analytics from AppRegistry file

SEPARATE PRS COMING FOR:

Typings
Messaging analytics
Source screen property for all components

🚨 Important 🚨

When adding analytics to a component, you NEED to @track the entire component in order to add the tracking props. How what and why will be expanded upon, and added to the docs.
In order to decorate a method in typescript, it NEEDS to be a normal function, not ES7 property method, that if used in components' on clicks needs to be bound. See handleFollowChange() on the (Artist) Header Component.
When adding a new root class / component / VC, we no longer extend the RootContainer class. Instead, we return a RootContainer object in the render method of the component (e.g. the Artist component).

Fails

:no_entry_sign:

No CHANGELOG added.

Warnings

:warning:

Please assign someone to merge this PR, and optionally include people who should review.

:warning:

Changes were made to package.json, but not to yarn.lock.Perhaps you need to run yarn install?

:warning:

New dependencies added: react-tracking.

:warning:

New dependencies added: @types/stylelint.

:warning:

Could not get info from npm on @types/stylelint

:tada:
react-tracking
Author: The New York Times
Description: Declarative tracking for React apps.
Homepage: https://github.com/NYTimes/react-tracking

Created6 months agoLast Updated2 months agoLicenseApache-2.0Maintainers1Releases4Direct Dependencieslodash.mergeKeywordsnyt, react, declarative, tracking, metrics and layer

This README is too long to show.

yarn why react-tracking output
Has been hoisted to "react-tracking"This module exists because it's specified in "dependencies".Disk size without dependencies: "56kB"Disk size with unique dependencies: "128kB"Disk size with transitive dependencies: "128kB"Number of shared dependencies: 1

yarn why @types/stylelint output
Has been hoisted to "@types/stylelint"This module exists because it's specified in "devDependencies".Disk size without dependencies: "16kB"Disk size with unique dependencies: "16kB"Disk size with transitive dependencies: "16kB"Number of shared dependencies: 0

  Generated by :no_entry_sign: dangerJS

@orta addressed 😄

@orta should've linked, so'z, corresponding Eigen PR here: https://github.com/artsy/eigen/pull/2425


How to change opponent icon with bf places

Describe your problem here.
I want to make BF icon at the left side of the hp bar, would be pretty cool as event
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

function onEvent(n, v1, v2)
    if n == 'your event' then
        local x1 = getProperty('iconP1.x')
        local y1 = getProperty('iconP1.y')
        local x2 = getProperty('iconP2.x')
        local y2 = getProperty('iconP2.y')
        setProperty('iconP2.x', x1)
        setProperty('iconP2.y', y1)
        setProperty('iconP1.x', x2)
        setProperty('iconP1.y', y2)
    end
end

don't know if this'll work but it's worth a shot

function onEvent(n, v1, v2)
    if n == 'your event' then
        local x1 = getProperty('iconP1.x')
        local y1 = getProperty('iconP1.y')
        local x2 = getProperty('iconP2.x')
        local y2 = getProperty('iconP2.y')
        setProperty('iconP2.x', x1)
        setProperty('iconP2.y', y1)
        setProperty('iconP1.x', x2)
        setProperty('iconP1.y', y2)
    end
end

don't know if this'll work but it's worth a shot

K, u tried, but it not works


Webpack bundles both redux-saga/es and redux-saga/lib

The current way of accessing redux-saga's effects is by importing redux-saga/effects.js, but that file uses redux-saga/lib. This causes webpack to bundle both redux-saga/lib and redux-saga/es.
I didn't see anything in the documentation mentioning this, so I'm assuming it's a bug?
My current workaround is to add the following to my webpack configuration, but it feels unstable
{
  resolve: {
    alias: {
      'redux-saga/effects.js': 'redux-saga/es/effects.js'
      'redux-saga/util.js': 'redux-saga/es/util.js'
    }
  }
}

Thank you for your help :)

Whats the undesired effect of the current situation? Duplicated dependencies in the dist file?
From what I understand your alias fix is allowing webpack2 to perform tree shaking and all by using es modules, right?

If by current situation you mean without the alias fix, the undesired effect is having two versions of redux-saga in the same bundle (the contents of /lib and /es).
Here's the contents of my bundle without the alias:

And wWith the alias:

So while the fix does indeed allow webpack2 to perform tree shaking, the bigger benefit is not having two different redux-sagas.

Would you like to collaborate on straightening things? Im not too proficient with bundler configurations, would be cool to work on this with somebody more experienced on the matter. We could schedule some gitter/reactiflux/other_channel time

Actually if you want I can just make a PR with a fix that should make rollup/webpack2 always bundle /es and node/browserify/others always use /lib :)
It's a really minor change https://github.com/Ephys/redux-saga/commit/1ab5bb537279bfb3f1c4e3ecdd065f770d21bccc
Don't worry it doesn't break anything :)

LOL! I was searching and asking around for quite some time how to point /utils and /effects to the right directories for both types of builds
Had no idea (and could find this info) that such simple package.jsons fixes this....
Happy to accept a PR from you. Apart from this I'm strongly considering switching the bundler to rollup, but that might be another PR or I can make it later, just dont know when.
Bless you!

This is a really cool trick, thanks for sharing it, @Ephys!


allows merging properties and templates for api job and collocating r…

…eleases
This PR allows us to collocate releases into a single manifest. The changes in properties allow us to install plugins into kibana for example.
@malston && @bonzofenix

@dpb587 - I think this is ready for merging; we have CLAs on file; and I think this is a good extension to the templates


Generate a pdf file instead of text file

A pdf file with all the added hyperlinks instead of the text file.

This is the simplest way to achieve this task: https://github.com/JazzCore/python-pdfkit .

Hey @dheeraj135
You can send a PR instead.

I am working on this issue.

Sure @dheeraj135


have @param take an error message

so if you pass in @param("<NAME>", errmsg=...) it would use that errmsg as the error string if param fails in some way, this would allow us to fine tune client facing error messages

This could be done in call.Param's handle method. Basically do a try/except and then check if there is an errmsg flag, if there is then raise a new ValueError with the error message.
You could also allow minor templating with {value} or something like that and then it will always call format on the error message with certain predefined values (assuming format doesn't fail if it has keywords that aren't in the string)


reactor-core 3.4.31 (was 3.4.14)

About this PR
📦 Updates io.projectreactor:reactor-core from 3.4.14 to 3.4.31
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.projectreactor", artifactId = "reactor-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.projectreactor", artifactId = "reactor-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #239.


Add additional tests for std.math.sqrt()

These tests spotted an implementation issue of LDC.
Provided by KevinBrogan.
@KevinBrogan I find this test from your LDC contribution really good. It must go upstream. Thanks!

Auto-merge toggled on

:+1:

Merging in the interest of letting other things run.


Memory leaks in iree/test/e2e/models/collatz.mlir targeting VMLA backend

If you are an IREE team member, please consider doing further triage: remove the "help wanted" label, add other relevant labels, and redirect to a more appropriate assignee.
Describe the bug
A clear and concise description of what the bug is.
I found memory leak issue in iree/test/e2e/models. If I built IREE with ASAN, it causes errors. For example:
inhoseo@inho:~/iree$ ../iree-build/iree/tools/iree-run-mlir -export-all -iree-hal-target-backends=vmla iree/test/e2e/models/collatz.mlir
I /usr/local/google/home/inhoseo/iree/iree/tools/iree-run-mlir-main.cc:205] Compiling for target backend 'vmla*'...
I /usr/local/google/home/inhoseo/iree/iree/tools/iree-run-mlir-main.cc:318] Evaluating all functions in module for driver 'vmla'...
I /usr/local/google/home/inhoseo/iree/iree/tools/utils/vm_util.cc:258] Creating driver and device for 'vmla'...
EXEC @collatz
I /usr/local/google/home/inhoseo/iree/iree/tools/utils/vm_util.cc:201] result[0]: Buffer<float32[]>
f32=31
=================================================================
==3191115==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 424 byte(s) in 1 object(s) allocated from:
#0 0x6f7f52 in calloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x6f7f52)
#1 0xbc0a6f in iree_allocator_system_allocate (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc0a6f)
#2 0xbc00bc in iree_allocator_malloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc00bc)
#3 0xade279e in iree_hal_vmla_module_loader_try_load(iree_hal_executable_loader_t*, iree_hal_executable_spec_t const*, iree_hal_executable_s**) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade279e)
#4 0xade5402 in iree_hal_local_executable_cache_prepare_executable (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade5402)
Indirect leak of 3668 byte(s) in 1 object(s) allocated from:
#0 0x6f7f52 in calloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x6f7f52)
#1 0xbc0a6f in iree_allocator_system_allocate (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc0a6f)
#2 0xbc068e in iree_allocator_clone (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc068e)
#3 0xade22fe in iree_hal_vmla_module_loader_try_load(iree_hal_executable_loader_t*, iree_hal_executable_spec_t const*, iree_hal_executable_s**) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade22fe)
#4 0xade5402 in iree_hal_local_executable_cache_prepare_executable (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade5402)
Indirect leak of 1200 byte(s) in 1 object(s) allocated from:
#0 0x6f7f52 in calloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x6f7f52)
#1 0xbc0a6f in iree_allocator_system_allocate (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc0a6f)
#2 0xbc00bc in iree_allocator_malloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc00bc)
#3 0xc10741 in iree_vm_bytecode_module_alloc_state (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xc10741)
#4 0xb1b5f43 in iree_vm_context_register_modules (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xb1b5f43)
#5 0xb1b54a4 in iree_vm_context_create_with_modules (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xb1b54a4)
#6 0xade2541 in iree_hal_vmla_module_loader_try_load(iree_hal_executable_loader_t*, iree_hal_executable_spec_t const*, iree_hal_executable_s**) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade2541)
#7 0xade5402 in iree_hal_local_executable_cache_prepare_executable (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade5402)
Indirect leak of 240 byte(s) in 1 object(s) allocated from:
#0 0x6f7f52 in calloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x6f7f52)
#1 0xbc0a6f in iree_allocator_system_allocate (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc0a6f)
#2 0xbc00bc in iree_allocator_malloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc00bc)
#3 0xc0bde1 in iree_vm_bytecode_module_create (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xc0bde1)
#4 0xade2426 in iree_hal_vmla_module_loader_try_load(iree_hal_executable_loader_t*, iree_hal_executable_spec_t const*, iree_hal_executable_s**) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade2426)
#5 0xade5402 in iree_hal_local_executable_cache_prepare_executable (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade5402)
Indirect leak of 208 byte(s) in 1 object(s) allocated from:
#0 0x727a7d in operator new(unsigned long) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x727a7d)
#1 0xaf33941 in ruy::Context::Context() (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xaf33941)
#2 0xade1a02 in iree_hal_vmla_module_loader_create (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade1a02)
#3 0xadc6e3b in iree_hal_vmla_driver_factory_try_create (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xadc6e3b)
#4 0xbeefd4 in iree_hal_driver_registry_try_create_by_name (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbeefd4)
#5 0xc035c4 in iree::CreateDevice(absl::string_view, iree_hal_device_s**) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xc035c4)
#6 0x72f6fc in iree::(anonymous namespace)::EvaluateFile(std::unique_ptr<llvm::MemoryBuffer, std::default_deletellvm::MemoryBuffer >, mlir::DialectRegistry&) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x72f6fc)
#7 0x72b44a in main (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x72b44a)
#8 0x7fba6c341d09 in __libc_start_main csu/../csu/libc-start.c:308:16
Indirect leak of 184 byte(s) in 2 object(s) allocated from:
#0 0x6f7f52 in calloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x6f7f52)
#1 0xbc0a6f in iree_allocator_system_allocate (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc0a6f)
#2 0xbc00bc in iree_allocator_malloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc00bc)
#3 0xade45d5 in iree_hal_local_descriptor_set_layout_create (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade45d5)
#4 0xadc8221 in iree_hal_task_device_create_descriptor_set_layout (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xadc8221)
#5 0xbf9ee2 in iree_hal_module_descriptor_set_layout_create (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbf9ee2)
#6 0xb1bf1da in iree_vm_native_module_begin_call (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xb1bf1da)
#7 0xc20274 in iree_vm_bytecode_issue_import_call (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xc20274)
#8 0xc1ef71 in iree_vm_bytecode_call_import_variadic (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xc1ef71)
#9 0xc14c51 in iree_vm_bytecode_dispatch (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xc14c51)
#10 0xc11e7b in iree_vm_bytecode_module_begin_call (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xc11e7b)
#11 0xb1b64b9 in iree_vm_context_register_modules (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xb1b64b9)
#12 0xb1b54a4 in iree_vm_context_create_with_modules (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xb1b54a4)
#13 0x72fa55 in iree::(anonymous namespace)::EvaluateFile(std::unique_ptr<llvm::MemoryBuffer, std::default_deletellvm::MemoryBuffer >, mlir::DialectRegistry&) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x72fa55)
#14 0x72b44a in main (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x72b44a)
#15 0x7fba6c341d09 in __libc_start_main csu/../csu/libc-start.c:308:16
Indirect leak of 168 byte(s) in 1 object(s) allocated from:
#0 0x727a7d in operator new(unsigned long) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x727a7d)
#1 0xae4f16a in iree::hal::vmla::ModuleCreate(iree_allocator_t, iree_vm_module**) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xae4f16a)
#2 0xade1a02 in iree_hal_vmla_module_loader_create (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade1a02)
#3 0xadc6e3b in iree_hal_vmla_driver_factory_try_create (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xadc6e3b)
#4 0xbeefd4 in iree_hal_driver_registry_try_create_by_name (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbeefd4)
#5 0xc035c4 in iree::CreateDevice(absl::string_view, iree_hal_device_s**) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xc035c4)
#6 0x72f6fc in iree::(anonymous namespace)::EvaluateFile(std::unique_ptr<llvm::MemoryBuffer, std::default_deletellvm::MemoryBuffer >, mlir::DialectRegistry&) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x72f6fc)
#7 0x72b44a in main (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x72b44a)
#8 0x7fba6c341d09 in __libc_start_main csu/../csu/libc-start.c:308:16
Indirect leak of 160 byte(s) in 2 object(s) allocated from:
#0 0x6f7f52 in calloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x6f7f52)
#1 0xbc0a6f in iree_allocator_system_allocate (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc0a6f)
#2 0xbc00bc in iree_allocator_malloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc00bc)
#3 0xade5761 in iree_hal_local_executable_layout_create (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade5761)
#4 0xadc8783 in iree_hal_task_device_create_executable_layout (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xadc8783)
#5 0xbfbe12 in iree_hal_module_executable_layout_create (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbfbe12)
#6 0xb1bf1da in iree_vm_native_module_begin_call (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xb1bf1da)
#7 0xc20274 in iree_vm_bytecode_issue_import_call (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xc20274)
#8 0xc1ef71 in iree_vm_bytecode_call_import_variadic (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xc1ef71)
#9 0xc14c51 in iree_vm_bytecode_dispatch (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xc14c51)
#10 0xc11e7b in iree_vm_bytecode_module_begin_call (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xc11e7b)
#11 0xb1b64b9 in iree_vm_context_register_modules (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xb1b64b9)
#12 0xb1b54a4 in iree_vm_context_create_with_modules (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xb1b54a4)
#13 0x72fa55 in iree::(anonymous namespace)::EvaluateFile(std::unique_ptr<llvm::MemoryBuffer, std::default_deletellvm::MemoryBuffer >, mlir::DialectRegistry&) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x72fa55)
#14 0x72b44a in main (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x72b44a)
#15 0x7fba6c341d09 in __libc_start_main csu/../csu/libc-start.c:308:16
Indirect leak of 120 byte(s) in 1 object(s) allocated from:
#0 0x6f7f52 in calloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x6f7f52)
#1 0xbc0a6f in iree_allocator_system_allocate (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc0a6f)
#2 0xbc00bc in iree_allocator_malloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc00bc)
#3 0xb1b5349 in iree_vm_context_create_with_modules (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xb1b5349)
#4 0xade2541 in iree_hal_vmla_module_loader_try_load(iree_hal_executable_loader_t*, iree_hal_executable_spec_t const*, iree_hal_executable_s**) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade2541)
#5 0xade5402 in iree_hal_local_executable_cache_prepare_executable (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade5402)
Indirect leak of 32 byte(s) in 1 object(s) allocated from:
#0 0x727a7d in operator new(unsigned long) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x727a7d)
#1 0xae59a6a in iree::hal::vmla::(anonymous namespace)::VMLAModule::CreateState(iree_allocator_t) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xae59a6a)
#2 0xae5a1f3 in iree::vm::NativeModule<iree::hal::vmla::(anonymous namespace)::VMLAModuleState>::ModuleAllocState(void*, iree_allocator_t, iree_vm_module_state**) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xae5a1f3)
#3 0xb1b5f43 in iree_vm_context_register_modules (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xb1b5f43)
#4 0xb1b54a4 in iree_vm_context_create_with_modules (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xb1b54a4)
#5 0xade2541 in iree_hal_vmla_module_loader_try_load(iree_hal_executable_loader_t*, iree_hal_executable_spec_t const*, iree_hal_executable_s**) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade2541)
#6 0xade5402 in iree_hal_local_executable_cache_prepare_executable (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade5402)
Indirect leak of 32 byte(s) in 1 object(s) allocated from:
#0 0x6f7f52 in calloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x6f7f52)
#1 0xbc0a6f in iree_allocator_system_allocate (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc0a6f)
#2 0xbc00bc in iree_allocator_malloc (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbc00bc)
#3 0xb1b7d49 in iree_vm_instance_create (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xb1b7d49)
#4 0xadc6da7 in iree_hal_vmla_driver_factory_try_create (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xadc6da7)
#5 0xbeefd4 in iree_hal_driver_registry_try_create_by_name (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbeefd4)
#6 0xc035c4 in iree::CreateDevice(absl::string_view, iree_hal_device_s**) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xc035c4)
#7 0x72f6fc in iree::(anonymous namespace)::EvaluateFile(std::unique_ptr<llvm::MemoryBuffer, std::default_deletellvm::MemoryBuffer >, mlir::DialectRegistry&) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x72f6fc)
#8 0x72b44a in main (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x72b44a)
#9 0x7fba6c341d09 in __libc_start_main csu/../csu/libc-start.c:308:16
Indirect leak of 8 byte(s) in 1 object(s) allocated from:
#0 0x727a7d in operator new(unsigned long) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x727a7d)
#1 0xae4f42d in iree::hal::vmla::ModuleCreate(iree_allocator_t, iree_vm_module**) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xae4f42d)
#2 0xade1a02 in iree_hal_vmla_module_loader_create (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xade1a02)
#3 0xadc6e3b in iree_hal_vmla_driver_factory_try_create (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xadc6e3b)
#4 0xbeefd4 in iree_hal_driver_registry_try_create_by_name (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xbeefd4)
#5 0xc035c4 in iree::CreateDevice(absl::string_view, iree_hal_device_s**) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0xc035c4)
#6 0x72f6fc in iree::(anonymous namespace)::EvaluateFile(std::unique_ptr<llvm::MemoryBuffer, std::default_deletellvm::MemoryBuffer >, mlir::DialectRegistry&) (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x72f6fc)
#7 0x72b44a in main (/usr/local/google/home/inhoseo/iree-build/iree/tools/iree-run-mlir+0x72b44a)
#8 0x7fba6c341d09 in __libc_start_main csu/../csu/libc-start.c:308:16
SUMMARY: AddressSanitizer: 6444 byte(s) leaked in 14 allocation(s).

@inho9606 I think this is not related to your prototype in MLIR... The prototype you have is checking the shape during compilation. I don't think that it would cause any ASAN issues.
Looking at the error log. It complained about LeakSanitizer: detected memory leaks after execution. This means that there are memory leaks. Could you check this issue without your prototype?

@inho9606 I think this is not related to your prototype in MLIR... The prototype you have is checking the shape during compilation. I don't think that it would cause any ASAN issues.
Looking at the error log. It complained about LeakSanitizer: detected memory leaks after execution. This means that there are memory leaks. Could you check this issue without your prototype?

Oops,, yes right. Sorry for confusing you..

@benvanik I'll pass the issue to you. It seems that there is a memory leak in VMLA hal.
To repro:

Build IREE with ASAN config.
Run iree-run-mlir -export-all -iree-hal-target-backends=vmla iree/test/e2e/models/collatz.mlir

VMLA is deprecated.


ACME challenge is only reachable when request hits the node where challenge-Pod resides

Describe the bug:
I am troubleshooting my cert-manager install and have been trying to fix  failing http-01 challenges.
All challenges eventually fail with the following output or similar:
❯ kubectl -n testdescribe challenge test-https.sec-mpv24-2906987614-2354977944
Name:         test-https.sec-mpv24-2906987614-2354977944
Namespace:    test
Labels:       <none>
Annotations:  <none>
API Version:  acme.cert-manager.io/v1
Kind:         Challenge
Metadata:
  Creation Timestamp:  2022-01-28T23:18:06Z
  Finalizers:
    finalizer.acme.cert-manager.io
  Generation:  1
    Manager:    cert-manager
    Operation:  Update
    Time:       2022-01-28T23:18:07Z
  Owner References:
    API Version:           acme.cert-manager.io/v1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  Order
    Name:                  test-https.sec-mpv24-2906987614
    UID:                   406f327d-803c-4475-bc7b-dcd40a9b4af5
  Resource Version:        280744128
  UID:                     9de20e60-a742-4052-8b93-6ebdf086e21d
Spec:
  Authorization URL:  https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/1548355948
  Dns Name:           test.example.com
  Issuer Ref:
    Group:  cert-manager.io
    Kind:   ClusterIssuer
    Name:   letsencrypt-staging
  Key:      Pj3C2Y_klI2ReHxUUXIEzGpxSphk8vE9rfTFISMK5MM.8XwTWMIb7GFxept-I9u6qcCEY4uy11f_nGU_xKKU7gE
  Solver:
    http01:
      Ingress:
        Class:  nginx
  Token:        Pj3C2Y_klI2ReHxUUXIEzGpxSphk8vE9rfTFISMK5MM
  Type:         HTTP-01
  URL:          https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/1548355948/KDSmMA
  Wildcard:     false
Status:
  Presented:   true
  Processing:  true
  Reason:      Waiting for HTTP-01 challenge propagation: failed to perform self check GET request 'http://test.example.com/.well-known/acme-challenge/Pj3C2Y_klI2ReHxUUXIEzGpxSphk8vE9rfTFISMK5MM': Get "http://test.example.com/.well-known/acme-challenge/Pj3C2Y_klI2ReHxUUXIEzGpxSphk8vE9rfTFISMK5MM": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  State:       pending
Events:
  Type    Reason     Age   From          Message
  ----    ------     ----  ----          -------
  Normal  Started    11m   cert-manager  Challenge scheduled for processing
  Normal  Presented  11m   cert-manager  Presented challenge using HTTP-01 challenge mechanism

I have done some investigation, including trying to curl the token from the cert-manager-controller pod shell. I have now determined this to work only when my request hits the one node out of three where the challenge Pod resides.
I have a total of three worker nodes which are all listed in the DNS record for test.example.com, all of them are listed under status.loadBalancer.ingress in my ingress specs as well. I can not for the life of me figure out why only these requests go through.
All other ingresses seem to work fine.
Expected behaviour:

All curls on the challenge endpoint go through.
Steps to reproduce the bug:

I have no idea. Seems like a terrible edge case to me.
Anything else we need to know?:
 Closing.


initial-contributing-guide

Initial contributing docs.
Esp. for place to document community conventions.
And, to highlight important/core tools.
Largely modeled from foundation of Parquet community doc, given I see there is potential community overlap.

This change is

[ ] Do we have community guidelines for what/when to test?  I imagine that'd be good to include in here.
[ ] Seems like Reviews are to be done by Reviewable, not commenting in the GH Issue?  Is it worth calling out that?  [ ex: maybe this should be in Reviewable not here :-p
[ ] Who 'can' do reviews [ ex: who has to review for something to be merged ]?

Thanks for asking the right questions. We will be coming up with a contribution guideline and update the readme and repo when relevant. Closing for now.


Registration with email

✅  Safe to release independently of corresponding FE portion

Allows for registration via email
Supports routes for changing password, and resetting password
Email templates

Looks like the login tests are failing. Can you check those?