OandA Fires duplicate events occasionally

Expected Behavior
Only one event
Actual Behavior
Sometimes two of the exact same event
Potential Solution
No idea.
Reproducing the Problem
Cannot easily reproduce.
System Information
Here is a screenshot of the orders, complete with BrokerId ticket

Here is my output log:

20180704 13:16:02.177 Trace:: BrokerageTransactionHandler.OrderStatusChanged(): Time: 2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Submitted BrokerId: 1162
20180704 13:16:02.178 Trace:: LiveTradingResultHandler.OrderEvent(): Time: 2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Submitted
20180704 13:16:02.181 Trace:: BrokerageTransactionHandler.OrderStatusChanged(): Time: 2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Filled Quantity: 2136000 FillPrice: 1.16646 USD Message: Oanda Fill Event BrokerId: 1162
20180704 13:16:02.181 Trace:: BrokerageTransactionHandler.OrderStatusChanged(): Time: 2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Filled Quantity: 2136000 FillPrice: 1.16646 USD Message: Oanda Fill Event BrokerId: 1162
20180704 13:16:02.189 Trace:: Debug: New Order Event: Time: 2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Submitted
20180704 13:16:02.261 Trace:: LiveTradingResultHandler.OrderEvent(): Time: 2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Filled Quantity: 2136000 FillPrice: 1.16646 USD Message: Oanda Fill Event
20180704 13:16:02.272 Trace:: Debug: New Order Event: Time: 2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Filled Quantity: 2136000 FillPrice: 1.16646 USD Message: Oanda Fill Event
20180704 13:16:02.289 Trace:: LiveTradingResultHandler.OrderEvent(): Time: 2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Filled Quantity: 2136000 FillPrice: 1.16646 USD Message: Oanda Fill Event
20180704 13:16:02.295 Trace:: Debug: New Order Event: Time: 2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Filled Quantity: 2136000 FillPrice: 1.16646 USD Message: Oanda Fill Event

Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues (There are dup closed issues)

[ ] I have provided detailed steps to reproduce the issue

Are you using latest version of master? We had a similar issue about 2/3 mo
ago but thought we fixed it.
On Wed, Jul 4, 2018, 1:45 AM Worthy7<EMAIL_ADDRESS>wrote:

Expected Behavior
Only one event
Actual Behavior
Sometimes two of the exact same event
Potential Solution
No idea.
Reproducing the Problem
Cannot easily reproduce.
System Information
Here is a screenshot of the orders, complete with BrokerId ticket
[image: image]
https://user-images.githubusercontent.com/4762399/42256569-1f8deb16-7f8d-11e8-9368-dd5541f0116b.png
Here is my output log:
20180704 13:16:02.177 Trace::
BrokerageTransactionHandler.OrderStatusChanged(): Time: 2018/07/04 4:16:02
OrderID: 2 Symbol: EURUSD Status: Submitted BrokerId: 1162
20180704 13:16:02.178 Trace:: LiveTradingResultHandler.OrderEvent(): Time:
2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Submitted
20180704 13:16:02.181 Trace::
BrokerageTransactionHandler.OrderStatusChanged(): Time: 2018/07/04 4:16:02
OrderID: 2 Symbol: EURUSD Status: Filled Quantity: 2136000 FillPrice:
1.16646 USD Message: Oanda Fill Event BrokerId: 1162
20180704 13:16:02.181 Trace::
BrokerageTransactionHandler.OrderStatusChanged(): Time: 2018/07/04 4:16:02
OrderID: 2 Symbol: EURUSD Status: Filled Quantity: 2136000 FillPrice:
1.16646 USD Message: Oanda Fill Event BrokerId: 1162
20180704 13:16:02.189 Trace:: Debug: New Order Event: Time: 2018/07/04
4:16:02 OrderID: 2 Symbol: EURUSD Status: Submitted
20180704 13:16:02.261 Trace:: LiveTradingResultHandler.OrderEvent(): Time:
2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Filled Quantity:
2136000 FillPrice: 1.16646 USD Message: Oanda Fill Event
20180704 13:16:02.272 Trace:: Debug: New Order Event: Time: 2018/07/04
4:16:02 OrderID: 2 Symbol: EURUSD Status: Filled Quantity: 2136000
FillPrice: 1.16646 USD Message: Oanda Fill Event
20180704 13:16:02.289 Trace:: LiveTradingResultHandler.OrderEvent(): Time:
2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Filled Quantity:
2136000 FillPrice: 1.16646 USD Message: Oanda Fill Event
20180704 13:16:02.295 Trace:: Debug: New Order Event: Time: 2018/07/04
4:16:02 OrderID: 2 Symbol: EURUSD Status: Filled Quantity: 2136000
FillPrice: 1.16646 USD Message: Oanda Fill Event
Checklist

I have completely filled out this template

I have confirmed that this issue exists on the current master branch

I have confirmed that this is not a duplicate issue by searching
issues https://github.com/QuantConnect/Lean/issues (There are dup
closed issues)

I have provided detailed steps to reproduce the issue

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/QuantConnect/Lean/issues/2204, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACI6mZkVyOpQ1xsuIzjVNrNtDDZ1DwcSks5uDFZigaJpZM4VB_Gz
.

As I said yes I am
On Thu, 5 Jul 2018 at 00:53, Jared<EMAIL_ADDRESS>wrote:

Are you using latest version of master? We had a similar issue about 2/3 mo
ago but thought we fixed it.
On Wed, Jul 4, 2018, 1:45 AM Worthy7<EMAIL_ADDRESS>wrote:

Expected Behavior
Only one event
Actual Behavior
Sometimes two of the exact same event
Potential Solution
No idea.
Reproducing the Problem
Cannot easily reproduce.
System Information
Here is a screenshot of the orders, complete with BrokerId ticket
[image: image]
<
https://user-images.githubusercontent.com/4762399/42256569-1f8deb16-7f8d-11e8-9368-dd5541f0116b.png
Here is my output log:
20180704 13:16:02.177 Trace::
BrokerageTransactionHandler.OrderStatusChanged(): Time: 2018/07/04
4:16:02
OrderID: 2 Symbol: EURUSD Status: Submitted BrokerId: 1162
20180704 13:16:02.178 Trace:: LiveTradingResultHandler.OrderEvent():
Time:
2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Submitted
20180704 13:16:02.181 Trace::
BrokerageTransactionHandler.OrderStatusChanged(): Time: 2018/07/04
4:16:02
OrderID: 2 Symbol: EURUSD Status: Filled Quantity: 2136000 FillPrice:
1.16646 USD Message: Oanda Fill Event BrokerId: 1162
20180704 13:16:02.181 Trace::
BrokerageTransactionHandler.OrderStatusChanged(): Time: 2018/07/04
4:16:02
OrderID: 2 Symbol: EURUSD Status: Filled Quantity: 2136000 FillPrice:
1.16646 USD Message: Oanda Fill Event BrokerId: 1162
20180704 13:16:02.189 Trace:: Debug: New Order Event: Time: 2018/07/04
4:16:02 OrderID: 2 Symbol: EURUSD Status: Submitted
20180704 13:16:02.261 Trace:: LiveTradingResultHandler.OrderEvent():
Time:
2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Filled Quantity:
2136000 FillPrice: 1.16646 USD Message: Oanda Fill Event
20180704 13:16:02.272 Trace:: Debug: New Order Event: Time: 2018/07/04
4:16:02 OrderID: 2 Symbol: EURUSD Status: Filled Quantity: 2136000
FillPrice: 1.16646 USD Message: Oanda Fill Event
20180704 13:16:02.289 Trace:: LiveTradingResultHandler.OrderEvent():
Time:
2018/07/04 4:16:02 OrderID: 2 Symbol: EURUSD Status: Filled Quantity:
2136000 FillPrice: 1.16646 USD Message: Oanda Fill Event
20180704 13:16:02.295 Trace:: Debug: New Order Event: Time: 2018/07/04
4:16:02 OrderID: 2 Symbol: EURUSD Status: Filled Quantity: 2136000
FillPrice: 1.16646 USD Message: Oanda Fill Event
Checklist

I have completely filled out this template

I have confirmed that this issue exists on the current master branch

I have confirmed that this is not a duplicate issue by searching
issues https://github.com/QuantConnect/Lean/issues (There are dup
closed issues)

I have provided detailed steps to reproduce the issue

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/QuantConnect/Lean/issues/2204, or mute the thread
<
https://github.com/notifications/unsubscribe-auth/ACI6mZkVyOpQ1xsuIzjVNrNtDDZ1DwcSks5uDFZigaJpZM4VB_Gz
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/QuantConnect/Lean/issues/2204#issuecomment-402515382,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEirH2WKq5LzieDVqNfz2eby1KAnAbqzks5uDOUTgaJpZM4VB_Gz
.

You're talking about this
https://github.com/QuantConnect/Lean/pull/1271
I don't know what exactly the problem was back then as I don't think I was using live at that point. But the problem exists on the current master branch, and it is definitely intermittent - it happens randomly at OandA's descretion. It's really a bug on their end.
I don't know the great inner workings of Lean, but it seems that simply ignoring updates where the update has already been applied might be the way to go.
Since it is very specific to OandA, it might be worth adding a Warning:Oanda sent fill where fill was already registered for OrderID: 3 message just to alert users that it happened.

Hold on I'll believe this when I see it lol

@Worthy7 - yes! Please let me know if you find anything and if possible, some detailed logging to accompany any errors or unexpected behavior.

I ran a simple algo all day, seems to be fine! Thanks a lot @Martin-Molinero !


platform specific configuration

Originally reported by John Vandenberg (Bitbucket: jayvdb, GitHub: jayvdb)

If a block has two platform/OS-specific branches, currently the only way to reach 100% with a single configuration is to use #pragma: no cover on both branches, ignoring the block when coverage is run on any platform/OS.
It is useful for each platform/OS to require coverage for their own branch.
This can be currently be achieved by using a different configuration file for each platformOS.
It would be helpful that the configuration allows for different ignore patterns for platform/OS, so only one configuration file is needed for all platforms.
One easy way to do this is to iterate the section names in the ini file, extracting any section with pytest in the name, and then finding the most appropriate section for the host platform/OS.
Another approach is to allow the ignore regex to be specified on the command line.

Bitbucket: https://bitbucket.org/ned/coveragepy/issue/563

There's a new coverage plugin that can do these sorts of conditionals: https://sobolevn.me/2020/02/conditional-coverage


Support ignoring rules outside of TTL

This would resolve #64
I know I'm bombarding with PRs at the moment @ismay haha, don't worry I'm not in a hurry, just guess I got a bit motivated and excited ;).
This is still a WIP, especially tests, but I thought I would just put this here as a complement to #64 so you could see what my idea was.
A few thoughts I had / decisions I made:

Are there any indentation stylelint rules I should be careful of not triggering with this? Or I should probably also research stylelint rules concerning comments to make sure I don't introduce any edge cases there
With this approach we also support single-line comments such as // comment which it wouldn't in normal CSS as we convert them all to /* comment */ comments which I guess I'm also quite fine with if people prefer that that they have that possibility.

Todo:

[x] Add comment about why space is there in regex so it's clear that we don't input stylelint-disable-line and stylelint-disable-next-line as they should only be used within css blocks
[x] Add thorough, relevantly structured tests (valid / invalid isn't a suitable structure for this code)
[x] Add note to README

I quite like this approach as we don't have to do much and can let stylelint handle everything! 😜

I quite like this approach as we don't have to do much and can let stylelint handle everything! :stuck_out_tongue_winking_eye:

Haha yes, that's the plan! ^^

Hmmm... I'm ready for review, but prettier is acting up, it really doesn't like styled-components haha.
Travis CI was failing because of it, so I let prettier do it's thing, but while it on the one hand onelines a lot of the css that just has one declaration (which I guess works, but isn't that neat) the really bad thing is it adds semicolons in plain wrong places that probably breaks the tests (we'll see in a sec <.<).
I think the easiest thing is to maybe just make prettier ignore the fixtures folder where we keep all our styled-components syntax? As I have any way been adding // prettier-ignore statements before all of my styled-components stuff atm, which is really tedious.

Okay I implemented my proposed exclusion of test/fixtures from prettier linting and removed all prettier-ignore statements with a quick regex on the folder, Now hopefully all the tests should pass.
Feel free to tell me to reverse the prettier exclusion if you want.
I'll go get some dinner and come back to hopefully see a passed travis build :).

Okay... Going to dinner now! And this time it'll work :P.
I had missed also changing .lintstagedrc

Okay, now I'm just really confused. I need some help with this I'm afraid, Travis says lint:prettier fails, but it doesn't on my machine. I even tried doing git reset --hard onto the remote to make sure I had the exact same

Okay, now I'm just really confused. I need some help with this I'm afraid, Travis says lint:prettier fails, but it doesn't on my machine. I even tried doing git reset --hard onto the remote to make sure I had the exact same

@emilgoldsmith I've checked out your branch, and for me it fails where it fails for travis as well, src/parsers/index.js. You can fix it by running:
./node_modules/.bin/prettier --list-different --print-width 100 --tab-width 2 --no-semi --single-quote --write '{src/**/*.{js,jsx},test/*.{js,jsx}}'

From the root of the project. That fixed it for me. Don't know if you want me to commit this to your branch, so I'm listing it here. No idea why it doesn't fail on your machine though. Maybe a different version of prettier?

Hey @ismay thanks, yeah tried ```
rm -Rf node_modules
npm install
and then it suddenly found it. Mysterious indeed. I do believe that I have upgraded my node and npm versions since first installing the repo, so that could possibly be the issue (as in it was installed with different node version?) that kind of stuff sometimes causes issues. But definitely was mysterious!

When I did `npm install` it updated `package-lock.json`. I have npm v5.1 I don't know if it does some smart optimizations on install? I pushed it anyway as I assumed npm knew what it was doing, but I can remove that if you guys think so.

Coverage increased (+0.04%) to 99.408% when pulling ef173d6a13f3bc029807443d1ba82d612fa45e39 on emilgoldsmith:feature/#64/support-ignoring-rules-outside-TTL into 2786011d3031f2ec2c82cacdc100ffa4843eafc0 on styled-components:master.

Yay! Finally :P.
Yep, so this is now, finally, 100% ready for review.

Coverage increased (+0.04%) to 99.408% when pulling cb19500cd13bf7e2a049ee7f34a3a43e30fd1c33 on emilgoldsmith:feature/#64/support-ignoring-rules-outside-TTL into 2786011d3031f2ec2c82cacdc100ffa4843eafc0 on styled-components:master.

Nope, me neither, looks really good. Great job @emilgoldsmith !

Somebody publish a new version? I'm not setup locally right now :blush:

Don't we need some kind of permissions for that?

Remember to publish the newest version at some point :).
If you want I can also do it if you give me permissions, up to you, I'm also emilgoldsmith on npm anyway.

@emilgoldsmith We have permissions now:
╰─$ npm owner ls
emilgoldsmith<EMAIL_ADDRESS>ismay<EMAIL_ADDRESS>mxstbr<EMAIL_ADDRESS>

Awesome, well, in that case I guess I'll go ahead and publish what we have now!

Done!
And just pushed a v0.2.0 tag as well.
For the future maybe we shouldn't update the package.json beforehand as we did in #60 as then we can't use tools like np which are really neat, but they upgrade the package.json for you and don't allow you to publish the current version of the package.json.
So just did it manually this time :).


scripts not working

Describe the bug
A clear and concise description of the bug.
the script is not executing see log and additional info.
To Reproduce
Steps to reproduce the behavior:

run a script using command in additional info
See error

Expected behavior
it would execute
Screenshots
N/A
Attachments
INFO  REPORT: Analysis succeeded for file: file:///home/dot_______166/tm.exe (HeadlessAnalyzer)                         ERROR Failed to find script in any script directory: /home/dot_______166/ghidra-headless-decompile/fix.java (GhidraScriptUtil)                                                                                ERROR REPORT SCRIPT ERROR: fix.java : The class could not be found. It must be the public class of the .java file: Failed to find source bundle containing script: /home/dot_______166/ghidra-headless-decompile/fix.java (HeadlessAnalyzer) ghidra.app.script.GhidraScriptLoadException: The class could not be found. It must be the public class of the .java file: Failed to find source bundle containing script: /home/dot_______166/ghidra-headless-decompile/fix.java                           at ghidra.app.script.JavaScriptProvider.getScriptInstance(JavaScriptProvider.java:105)                                  at ghidra.app.util.headless.HeadlessAnalyzer.runScriptsList(HeadlessAnalyzer.java:908)                                  at ghidra.app.util.headless.HeadlessAnalyzer.analyzeProgram(HeadlessAnalyzer.java:1070)                                 at ghidra.app.util.headless.HeadlessAnalyzer.processFileWithImport(HeadlessAnalyzer.java:1552)                          at ghidra.app.util.headless.HeadlessAnalyzer.processWithLoader(HeadlessAnalyzer.java:1734)                              at ghidra.app.util.headless.HeadlessAnalyzer.processWithImport(HeadlessAnalyzer.java:1675)                              at ghidra.app.util.headless.HeadlessAnalyzer.processWithImport(HeadlessAnalyzer.java:1759)                              at ghidra.app.util.headless.HeadlessAnalyzer.processLocal(HeadlessAnalyzer.java:460)                                    at ghidra.app.util.headless.AnalyzeHeadless.launch(AnalyzeHeadless.java:127)                                            at ghidra.GhidraLauncher.launch(GhidraLauncher.java:78)                                                                 at ghidra.Ghidra.main(Ghidra.java:54)                                                                           Caused by: java.lang.ClassNotFoundException: Failed to find source bundle containing script: /home/dot_______166/ghidra-headless-decompile/fix.java                                                                                at ghidra.app.script.JavaScriptProvider.loadClass(JavaScriptProvider.java:146)                                          at ghidra.app.script.JavaScriptProvider.getScriptInstance(JavaScriptProvider.java:91)                                   ... 10 more
Environment (please complete the following information):

OS: Ubuntu 22.04.3 LTS on Windows 10 x86_64
Java Version: 17
Ghidra Version: latest
Ghidra Origin: official GitHub distro

Additional context
code:
//Decompile an entire program
import java.io.File;
import java.util.ArrayList;
import java.util.List;
import java.util.Arrays;
import ghidra.app.plugin.core.script.Ingredient;
import ghidra.app.plugin.core.script.IngredientDescription;
import ghidra.app.script.GatherParamPanel;
import ghidra.app.script.GhidraScript;
import ghidra.app.util.Option;
import ghidra.app.util.exporter.CppExporter;
public class fix extends GhidraScript implements Ingredient {
@Override
public void run() throws Exception {
	IngredientDescription[] ingredients = getIngredientDescriptions();
	for (IngredientDescription ingredient : ingredients) {
		state.addParameter(ingredient.getID(), ingredient.getLabel(), ingredient.getType(),
			ingredient.getDefaultValue());
	}
	// if (!state.displayParameterGatherer("Script Options")) {
	// 	return;
	// }

	String[] args = getScriptArgs();

	System.out.println("ARGS: " + Arrays.toString(args));

	// File outputFile = (File) state.getEnvironmentVar("COutputFile");
	File outputFile = new File(args[0]);

	CppExporter cppExporter = new CppExporter();
	List<Option> options = new ArrayList<Option>();
	options.add(new Option(CppExporter.CREATE_HEADER_FILE, new Boolean(false)));
	cppExporter.setOptions(options);
	cppExporter.setExporterServiceProvider(state.getTool());
	cppExporter.export(outputFile, currentProgram, null, monitor);
}

@Override
public IngredientDescription[] getIngredientDescriptions() {
	IngredientDescription[] retVal = new IngredientDescription[] {
		new IngredientDescription("COutputFile", "Output C File", GatherParamPanel.FILE, "") };
	return retVal;
}

}
command executed:
time /home/dot_______166/ghidra/support/analyzeHeadless . tmp_ghidra_project -import tm.exe  -scriptPath /home/dot_______166/ghidra-headless-decompile/ -postscript fix.java tm.cpp

Are you sure you are using JDK 17?  A similar looking error recently popped up when JDK 22 was being used.

when i run java -version i get the following output:
dot_______166@JAKE-PC:~/ghidra-headless-decompile$ java -version                                                        openjdk version "17.0.10" 2024-01-16                                                                                OpenJDK Runtime Environment (build 17.0.10+7-Ubuntu-122.04.1)                                                           OpenJDK 64-Bit Server VM (build 17.0.10+7-Ubuntu-122.04.1, mixed mode, sharing)

Would you mind just confirming what version is displayed on your Ghidra splash screen when it starts?

11.0.3

Hmmm, the latest version of Ghidra should not even be allowed to launch with JDK 11.

Oh my mistake i put the ghidra version in that comment. My splash screen says
ghidra 11.0.3
Java 17.0.10

Ok thanks, i'll think more about it.

Ok thanks, i'll think more about it.

https://github.com/NationalSecurityAgency/ghidra/discussions/6449#discussioncomment-9178409
I see this problem roughly 80% of the time I try to run a java script. I think the easiest way to reproduce it is to delete the osgi folder, launch the code browser, close it while it is taking forever to setup the osgi stuff, let it error and then it should happen the next time you try to run a java script.

Describe the bug
I have the exactly same problem. Not even a simple hello world runs.
To Reproduce
Select any script in Script Manager like "HelloWorldScript.java" and try to run it.
Expected behavior
it would execute
Screenshots
N/A
Environment (please complete the following information):
OS: Windows 10 x86_64
Java Version: 17.0.10 or 22.0.1 (zip and set path variable)
Ghidra Version: latest
Ghidra Origin: official GitHub distro
Additional context:
> Unable to load script: HelloWorldScript.java
>   detail: The class could not be found. It must be the public class of the .java file: HelloWorldScript

I'm having the same issue--custom scripts written in Java fail to run, but scripts included with Ghidra run without any problems.
It doesn't matter what version of Java I use--the result is the same whether I use Java 17, 21, or 22.
I'm running Ghidra on Arch Linux, and I'm using the latest version of Ghidra from the Arch repositories (11.0.3).
Here's a minimal reproducer script (TestScript.java):
// Test script

import ghidra.app.script.GhidraScript;

public class TestScript extends GhidraScript {
	@Override
	public void run() {
	}
}

Placing that script in a custom script directory $USER_HOME/Documents/Ghidra/scripts results in the following console output:
> Unable to load script: TestScript.java
>   detail: The class could not be found. It must be the public class of the .java file: TestScript

The problem can be worked around by moving the script into /opt/ghidra/Ghidra/Features/Base/ghidra_scripts/. When I do that, TestScript.java executes successfully:
TestScript.java> Running...
TestScript.java> Finished!

In the process of trying to figure out what the problem was, I accidentally fixed it for myself. Here's approximately what I did--not sure what part of this fixed the issue:

Have Ghidra already open with a CodeBrowser window open.
$ mkdir ~/ghidra_scripts (it didn't exist before since I prefer to keep my scripts in other directories)
$ mv TestScript.java ~/ghidra_scripts/
"Display Script Manager" -> "Manage Script Directories" -> "Refesh state by cleaning and reactivating all enabled bundles"
Close Ghidra.
Open Ghidra.
Open CodeBrowser window.
"Display Script Manager" -> "Manage Script Directories" -> Enable $USER_HOME/ghidra_scripts (I might have refreshed again after this--I forget whether or not I did)
Run TestScript.java : Results in successful script output in console.
Run other custom scripts in other custom directories (not $USER_HOME/ghidra_scripts`): Results in successful script output in console.
$ rm -r ~/ghidra_scripts
"Display Script Manager" -> "Manage Script Directories" -> "Refesh state by cleaning and reactivating all enabled bundles"
Close Ghidra.
Open Ghidra.
Open CodeBrowser window.
Run other custom scripts in other custom directories (not $USER_HOME/ghidra_scripts`): Results in successful script output in console.
"Display Script Manager" -> "Manage Script Directories" -> "Refesh state by cleaning and reactivating all enabled bundles"
Run other custom scripts in other custom directories (not $USER_HOME/ghidra_scripts`): Results in successful script output in console.

So now custom scripts in custom directories works for me and I can't get it back into the broken state any more. If someone really wants me to I can try restoring my ~/.ghidra directory from yesterday's backup to see if things are broken again and maybe try to figure out the minimum number of steps required to fix the issue, but it would be kind of a pain for me to do all of that so I'd rather not unless it's deemed necessary for finding the root cause of the issue. Hopefully the information I've already posted will be enough for someone else to determine the root cause or find a simpler fix.

In the process of trying to figure out what the problem was, I accidentally fixed it for myself. Here's approximately what I did--not sure what part of this fixed the issue:

Have Ghidra already open with a CodeBrowser window open.
$ mkdir ~/ghidra_scripts (it didn't exist before since I prefer to keep my scripts in other directories)
$ mv TestScript.java ~/ghidra_scripts/
"Display Script Manager" -> "Manage Script Directories" -> "Refesh state by cleaning and reactivating all enabled bundles"
Close Ghidra.
Open Ghidra.
Open CodeBrowser window.
"Display Script Manager" -> "Manage Script Directories" -> Enable $USER_HOME/ghidra_scripts (I might have refreshed again after this--I forget whether or not I did)
Run TestScript.java : Results in successful script output in console.
Run other custom scripts in other custom directories (not $USER_HOME/ghidra_scripts`): Results in successful script output in console.
$ rm -r ~/ghidra_scripts
"Display Script Manager" -> "Manage Script Directories" -> "Refesh state by cleaning and reactivating all enabled bundles"
Close Ghidra.
Open Ghidra.
Open CodeBrowser window.
Run other custom scripts in other custom directories (not $USER_HOME/ghidra_scripts`): Results in successful script output in console.
"Display Script Manager" -> "Manage Script Directories" -> "Refesh state by cleaning and reactivating all enabled bundles"
Run other custom scripts in other custom directories (not $USER_HOME/ghidra_scripts`): Results in successful script output in console.

So now custom scripts in custom directories works for me and I can't get it back into the broken state any more. If someone really wants me to I can try restoring my ~/.ghidra directory from yesterday's backup to see if things are broken again and maybe try to figure out the minimum number of steps required to fix the issue, but it would be kind of a pain for me to do all of that so I'd rather not unless it's deemed necessary for finding the root cause of the issue. Hopefully the information I've already posted will be enough for someone else to determine the root cause or find a simpler fix.

https://github.com/NationalSecurityAgency/ghidra/discussions/6449#discussioncomment-9178409

save problem while using analyzeHeadless
ERROR REPORT SCRIPT ERROR: print_program_name.java : The class could not be found. It must be the public class of the .java file: print_program_name not found by ab350b1b [2] (HeadlessAnalyzer) ghidra.app.script.GhidraScriptLoadException: The class could not be found. It must be the public class of the .java file: print_program_name not found by ab350b1b [2]


weighted_* generators panic if all weights are zero

Currently if all weights are zero then these generators will panic when generating values with this message:
attempt to calculate the remainder with a divisor of zero

Alternatives:

panic when creating the generator with a helpful message, or
generate with uniform distribution instead of panicking

Fixed in https://github.com/jakoschiko/dicetest/commit/e711b1e5402df86eaa8181e1e69dc8a3b7f48931.
I decided to fall back to uniform distribution if the sum of weights is zero.


Refactor move jetty into separate module, add JDK http service implementation module

JDK comes with a basic http service.  Adds a separate jex implementation based on that with some current limitations (no multipart file upload support, no session support, currently no cookie support although we should be able to add that).

Interesting stuff. Is the long term goal to get rid of jetty completely, or to offer multiple jex flavors for different needs?

multiple jex flavors for different needs?

The Jex JDK server is approx 80K + JDK http server + the only other dependency being logging (logback or log4j etc) so it is very lightweight. The use cases where we will look to use this is for services that are largely doing messaging (ActiveMQ / Kafka etc). For these services we are effectively only using the http endpoints for kubernetes liveness, readiness probes + metrics reporting.
The Jex JDK server does not support file uploads, websockets, sse and sessions but that is ok for these services.
The other potential use case I have in mind would be small graal native-image rest servers.

get rid of jetty completely

I did some quick performance tests of Jetty, Undertow and Netty.  Undertow was just a touch faster than Jetty with Netty (using Helidon SE) the slowest for my test. All pretty similar really.  The summary is that Jetty is still imo a really really good choice when we want a serious http server - especially with the way Loom is going to work. With Undertow, Netty we need a separate second thread pool beyond their worker pools which is ok but Jetty is just going to be easy with Loom.

The Jex JDK server is approx 80K + JDK http server + the only other dependency being logging (logback or log4j etc) so it is very lightweight. The use cases where we will look to use this is for services that are largely doing messaging (ActiveMQ / Kafka etc). For these services we are effectively only using the http endpoints for kubernetes liveness, readiness probes + metrics reporting.

Makes sense!

I did some quick performance tests of Jetty, Undertow and Netty. Undertow was just a touch faster than Jetty with Netty (using Helidon SE) the slowest for my test. All pretty similar really. The summary is that Jetty is still imo a really really good choice when we want a serious http server - especially with the way Loom is going to work. With Undertow, Netty we need a separate second thread pool beyond their worker pools which is ok but Jetty is just going to be easy with Loom.

Glad to see you arrive at this conclusion too. As much as I dislike Jetty's API, I think it's a solid general purpose webserver, and I'm pretty much married to it at this point :)


Fb saml logout

This change is

[Current coverage][cc-pull] is 58.15%

Merging [#59][cc-pull] into [master][cc-base-branch] will decrease coverage by -7.84%

2 files (not in diff) in ...operatorservice/bean were created. more
19 files (not in diff) in .../org/oscm/domobjects were created. more
2 files (not in diff) in .../org/oscm/vatservice were modified. more

Misses +45
Hits -45

10 files (not in diff) in ...gerservice/validator were modified. more

Misses +53
Partials +4
Hits -57

4 files (not in diff) in .../triggerservice/bean were modified. more

Misses +57
Partials +13
Hits -70

2 files (not in diff) in .../oscm/triggerservice were modified. more

Misses +10
Hits -10

2 files (not in diff) in ...triggerservice/local were modified. more

Misses +1
Partials +4
Hits -5

2 files (not in diff) in ...gerservice/assembler were modified. more

Partials +9
Hits -9

3 files (not in diff) in ...scriptionservice/dao were modified. more

Misses -169
Partials +6
Hits -80

8 files (not in diff) in ...criptionservice/bean were modified. more

Misses +80
Partials +173
Hits -297

@@             master        #59   diff @@
==========================================
  Files          1872       1895     +23
  Lines         95867      95924     +57
  Methods           0          0
  Messages          0          0
  Branches      11898      11907      +9
==========================================
- Hits          63261      55781   -7480
- Misses        32606      37227   +4621
- Partials          0       2916   +2916

Powered by Codecov. Last updated by [89a287e...10a529f][cc-compare]
[cc-base-branch]: https://codecov.io/gh/servicecatalog/development/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/servicecatalog/development/compare/89a287e0489dca4d4a33f1d635cc73019fe95eb2...10a529f304a444edfb5a7185fd4a97698a9383bd
[cc-pull]: https://codecov.io/gh/servicecatalog/development/pull/59?src=pr


Lexically scoped variables in the macro language

The macro interpreter currently does not create lexical scopes for any block parameters. It is up to each block-accepting macro method to define the block variables when a call is interpreted, and these macro methods all leave the variables untouched after that call finishes:
{%
  x = 1
  [2].each { |x| }
  x # => 2
%}

This is inconsistent with blocks in normal code which do create a lexical scope. On the other hand, macro for loops destroy the variables upon exit:
{% begin %}
  {% x = 1 %}
  {% for x in [2] %}
  {% end %}
  {% x %} # Error: undefined macro variable 'x'
{% end %}

for loops don't exist in normal Crystal code, but in Ruby they retain the last values of the variables (and it's a great source of confusion there). IMO both macro constructs should support lexical scoping and the local shadowing of variable names.

+1 this has bitten me numerous times.


Ability to set defaults

https://github.com/sindresorhus/eslint-plugin-xo/pull/45#discussion_r73125085
I don't see a problem with this as long as it's clearly documented. The original RuleTester isn't very well documented anyways. We should improve upon it where it makes sense.

I don't see a problem with this as long as it's clearly documented

True, but the documentation would be in a different project, so not "easily" accessible?
How about exporting a createTestCase (name TBD) function as part of this tool (or new module) that creates a test case with defaults?
const testCase = createTestCase({
  parserOptions: { ... }
});

const errorTestCase = createTestCase({
  parserOptions: { ... },
  errors: [{
    ruleId: 'explicit-length-check',
    message: '`length` property should be compared to a value'
  }]
});

ruleTester.run('explicit-length-check', rule, {
  valid: [
    testCase('array.foo'),
    testCase('array.length')
  ],
  invalid: [
    errorTestCase('if ([].length) {}'), // No other options, just pass a string
    errorTestCase({
      code: 'if ([].length) {}',
      parserOptions: {} // other parserOptions
    }),
    errorTestCase({
      code: 'if ([].length) {}',
      errors: [...] // other errors
    })
  ]
});

Something like
function createTestCase(defaultOptions) {
  return function(options) {
    if (typeof options === 'string') {
      return Object.assign({}, defaultOptions, {code: options});
    }
    return Object.assign({}, defaultOptions, options);
  };
}

I like the explicitness of this.

True, but the documentation would be in a different project, so not "easily" accessible?

It would actually be more accessible. People would go here to know about this module, not the ESLint docs. This module is already different from RuleTester in that it's for AVA. And it's not like RuleTester is very well documented.

How about exporting a createTestCase (name TBD) function as part of this tool (or new module) that creates a test case with defaults?

I see a use-case for both. For the common case, your suggestion is more verbose. Having an option called testCaseDefaults (or something) would be much more concise. The whole point of RuleTester is to reduce redundant boilerplate.

Let's do this. I'm not sure when I'd get to this, so if someone wants to have a try at it, please let me know here :)


(%TheTrueLtaker) gen9ilovemath: changing to mnm base and adding ce

%TheTrueLtaker: "changing to mnm base and adding ce"
Created via Iolanthe on Sat, 23 Sep 2023 21:51:57 GMT.

Cross Evolution doesn't work as an add-on.


Support Lint Warnings

Features

rename Errors panel to Problems panel
show errors and warnings in Problems panel
show errors and warnings on canvas (cf. https://github.com/camunda/linting/pull/32)

Artifacts

https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/lint-warnings-test/camunda-modeler-lint-warnings-test-linux-x64.tar.gz
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/lint-warnings-test/camunda-modeler-lint-warnings-test-mac.dmg
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/lint-warnings-test/camunda-modeler-lint-warnings-test-mac.zip
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/lint-warnings-test/camunda-modeler-lint-warnings-test-win-ia32.zip
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/lint-warnings-test/camunda-modeler-lint-warnings-test-win-x64.zip

Requires https://github.com/camunda/linting/pull/32

Is it correct that we abuse Carbon "Notifications" (https://carbondesignsystem.com/patterns/notification-pattern/) here to style? These errors are not notifications and I have not ever seen a linting panel like this.
What made us change from the good enough UI?

From: Philipp Fromme @.>
Sent: 25 October 2022 22:28
To: camunda/camunda-modeler @.>
Cc: Subscribed @.***>
Subject: [camunda/camunda-modeler] Support Lint Warnings (PR #3257)

rename Errors panel to Problems panel
show errors and warnings in Problems panel
show errors and warnings on canvas (cf. camunda/linting#32https://github.com/camunda/linting/pull/32)

[image]https://user-images.githubusercontent.com/7633572/197874044-c3be0b57-ae3c-4e9f-896e-6db5596c08c3.png

Requires camunda/linting#32https://github.com/camunda/linting/pull/32

You can view, comment on, or merge this pull request online at:
https://github.com/camunda/camunda-modeler/pull/3257
Commit Summary

f3aebb6https://github.com/camunda/camunda-modeler/pull/3257/commits/f3aebb63fc3381f9e2ee80a70e91457ef78446cb chore: update error and warning icons
d54442bhttps://github.com/camunda/camunda-modeler/pull/3257/commits/d54442b8259af9ad79a7c42353f61a83f56ded51 feat: show errors and warnings in linting status bar button
9cf5d74https://github.com/camunda/camunda-modeler/pull/3257/commits/9cf5d7465bf4cc850b4e2638f2e3b68e99d469c0 feat: show errors and warnings in problems panel

File Changes
(10 fileshttps://github.com/camunda/camunda-modeler/pull/3257/files)

M client/resources/icons/Error.svghttps://github.com/camunda/camunda-modeler/pull/3257/files#diff-23f32208c1efa133c4d1be2ed8ddeac722f965f9b7ff0d24f746ea90880c30b5 (6)
M client/resources/icons/Warning.svghttps://github.com/camunda/camunda-modeler/pull/3257/files#diff-af0664e382a9bf6ee3caa520af3a45fdb68ac3ce3b57f96cf777d4503756f74b (8)
M client/src/app/tabs/Linting.jshttps://github.com/camunda/camunda-modeler/pull/3257/files#diff-4ca2a5a535bf1bb08007afad625941bfc7a6b2f1e526d373be3afd8e461d0dd5 (13)
M client/src/app/tabs/Linting.lesshttps://github.com/camunda/camunda-modeler/pull/3257/files#diff-d6b91766968f1dce7a5e421c5f09b29ce75020002218d5cc90c537bea05b2d11 (44)
M client/src/app/tabs/tests/LintingSpec.jshttps://github.com/camunda/camunda-modeler/pull/3257/files#diff-9c1d1544f26b33c8cd821ccc5752c7f24d873a152bee257aaca7cf43cc2abd84 (29)
M client/src/app/tabs/panel/Panel.lesshttps://github.com/camunda/camunda-modeler/pull/3257/files#diff-b1f1f8585a2c3c7f8239068729bff0c621e00cc7c86c901901691153a6ddfddf (5)
M client/src/app/tabs/panel/tabs/LintingTab.jshttps://github.com/camunda/camunda-modeler/pull/3257/files#diff-390126b7ae3aa39a26b0c77db156620874bcdab7d32200d53f0d2533487cc7eb (22)
M client/src/app/tabs/panel/tabs/LintingTab.lesshttps://github.com/camunda/camunda-modeler/pull/3257/files#diff-5e07a3beeac3c93f32dc05b48d315de030dc397fb12c9183d3194dc4cf66db5a (90)
M client/src/app/tabs/panel/tabs/tests/LintingTabSpec.jshttps://github.com/camunda/camunda-modeler/pull/3257/files#diff-eb72935e1987cb8c2fa6b7987323f8fe5b69b1eaf6324f5b9a293ec2ea42fdca (41)
M client/src/styles/_colors.lesshttps://github.com/camunda/camunda-modeler/pull/3257/files#diff-38624395ffdd591e8d0de75d0170eaf6138f87524680560abcc66df6c3a708b1 (11)

Patch Links:

https://github.com/camunda/camunda-modeler/pull/3257.patch
https://github.com/camunda/camunda-modeler/pull/3257.diff

—
Reply to this email directly, view it on GitHubhttps://github.com/camunda/camunda-modeler/pull/3257, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAAOJ2NOXLQZ3PZ66BHEYRLWFA7HZANCNFSM6AAAAAAROKNK3U.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Alternatively, we could remove the background and border:

Then we would basically end up with what we had before with the only notable change being that the entire line can be clicked.
Happy holidays, @nikku. 🏝

Thank you Phillip for sharing this preview, It looks great! I'm fine with keeping the errors/warnings without a background color as long as this layout stays the same.
@christian-konrad and @nithinssabu, as we have a very similar panel in the web modeler, can we adopt this look?
@nikku we don't abuse we customize carbon to our own needs. :wink:

Currently, our notifications look less like notifications than the lint errors and warnings. 🤡 So, besides making lint errors and warnings look less like notifications we should also make notifications look more like notifications, so they stand out.

Assuming, we'd adopt IBM Carbon for notifications I can see the problem:

@philippfromme @YanaSegal recent design looks great, maybe we can still reduce the line height (in Desktop Modeler only), and then it's time for a review!
@YanaSegal we could then do same sketches for Web Modeler (but without reducing line height)

@philippfromme Regarding the notification, I agree. Let's tackle it by opening a dedicated issue.

Just personal opinion, but we should not put notification styles into data tables. Just not the way the UI is meant to be composed. Or is this a practice we adopt in other apps, too?
Love https://github.com/camunda/camunda-modeler/pull/3257#issuecomment-1292241207. Much simpler, less noisy, and what I'd expect as a Nico from a lint panel.
Thanks for prototyping @philippfromme :muscle:

If we want to go ahead and carbonize our notifications, that should be an easy pick, too.

what I'd expect as a Nico

😍

I will create a separate issue for the notifications.

Some suggestions: @philippfromme @YanaSegal @christian-konrad

In my opinion, the errrors will look a bit cleaner without the borders for the cells (light grey lines in between). Discussed this with @YanaSegal and we will not have these borders when we introduce this in Web Modeler to see how it looks. This is also in line with a recent design improvement we did for the error panel in the Web Modeler. (see the attached video)
Should we always show ID instead of names (like we currently do). In the prototype, I see that the ID is shown when name is not present, otherwise the name is shown. In my opinion, showing the names here do not add much value as the user can identify the element by clicking on the error. IDs are less likely to overflow, names are more likely to overflow. Since the problems panel will be used by the "developer" persona, it's fine to show the IDs.

https://user-images.githubusercontent.com/5987816/198274685-0679d8b9-78df-4150-b998-9a3f3e72b163.mov

In my opinion, the errrors will look a bit cleaner without the borders for the cells (light grey lines in between). Discussed this with @YanaSegal and we will not have these borders when we introduce this in Web Modeler to see how it looks. This is also in line with a recent design improvement we did for the error panel in the Web Modeler. (see the attached video)

I would at least keep the horizontal lines (cf. https://carbondesignsystem.com/components/data-table/code/#live-demo) but we can remove the vertical lines.

Should we always show ID instead of names (like we currently do). In the prototype, I see that the ID is shown when name is not present, otherwise the name is shown. In my opinion, showing the names here do not add much value as the user can identify the element by clicking on the error. IDs are less likely to overflow, names are more likely to overflow. Since the problems panel will be used by the "developer" persona, it's fine to show the IDs.

I actually agree with you. The idea of showing the label instead of the ID sounded good in theory but as you can see it's not very useful unless you show the entire label which might take a lot of space. I would be fine with removing this feature.
@christian-konrad @YanaSegal 👀

t's not very useful unless you show the entire label

Why? You only need the first 10 characters to identify the problem source anyways. Let's keep showing the names. No one recognizes the IDs (which are in most cases default IDs).

In my opinion, the errors will look a bit cleaner without the borders for the cells

I don't agree because we are using a tabular layout. We need the vertical lines, too, otherwise it may look odd when the error descriptions are left aligned but there's a margin to the element labels.
(I would rather say we should introduce a bottom border at the problems panel header in Web Modeler, since the contrast between the header and the content is too low)
Btw. we can still change it later again if we don't see fit.

@christian-konrad Okay, so basically leave it as it is?

Horizontal and vertical lines for layout ✔
Show name instead of ID if exists ✔

I'm fine with that.

@christian-konrad

Why? You only need the first 10 characters to identify the problem source anyways. Let's keep showing the names. No one recognizes the IDs (which are in most cases default IDs).
The names are not unique and can appear multiple times as "no" or "yes" elements. are you sure you want to show only the names?

I agree that the borders are needed

For the review, I have added a plugin that produces warnings for manual tasks.
Download here:

https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/lint-warnings-test/camunda-modeler-lint-warnings-test-linux-x64.tar.gz
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/lint-warnings-test/camunda-modeler-lint-warnings-test-mac.dmg
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/lint-warnings-test/camunda-modeler-lint-warnings-test-mac.zip
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/lint-warnings-test/camunda-modeler-lint-warnings-test-win-ia32.zip
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/lint-warnings-test/camunda-modeler-lint-warnings-test-win-x64.zip

As discussed today in the Weekly, let's leave the IDs as are and reiterate.
@philippfromme please create a new issue for following up on this.

Follow-up issue: https://github.com/camunda/camunda-modeler/issues/3270

I created an issue for implementing this feature in the web modeler: https://github.com/camunda/web-modeler/issues/2812 @CatalinaMoisuc 👀

As a follow up, I also created https://github.com/camunda/camunda-modeler/issues/3272

changed the padding to reduce line height
changed the title of the linting toggle

@barmac @marstamm A technical review would be awesome! 🚀

Follow-up for sorting reports by category: https://github.com/camunda/camunda-modeler/pull/3275


🚀 - Use iconStart and iconEnd for new Button

Description
https://taiga-ui.dev/next/components/button#icons

Not just button, everywhere with TuiIcons directive


Change misleading message about route being cause of delay

The message given when Rsync doesn't start after 10 minutes misleads the user. There are multiple reasons why Rsync could be stuck, and blanketly stating that the route is at fault is not accurate.
Previous
Paused - waiting for route to be admitted

New
Migration may be stuck.

In the above case, a bad PV with missing backing store was the cause of failure, completely unrelated to routes.
The next step will be for me to go into the backend and

Present this message before 10 minutes of nothing happening.
Give the user a call-to-action

Looking good!


Refactor, bugfixes, additional tests.

Now at 96.5% coverage for the entire package; 100% coverage for vangoh.go itself. The only un-tested code is vangoh.NegroniHandler.
Changes include:

Easier-to-type variable naming.
Consistent use of Key and Secret across the codebase.
Adding more tests, greatly increasing coverage.
Exporting helper functions to make it easier for consumers of the library to test their integration.
Not reporting error information by default, but allowing exposure via a debug flag.
Compiling route regexes at time of inclusion, rather than re-compiling per-request.
Allowing secret providers to store custom data and access the request immediately after successful authentication, useful when writing custom auth middlewares.
No longer decodes the signature sent by the client, simply creates a b64 signature on the server and the compares them.

Would be happy to talk about these changes individually, break them into separate PRs as necessary, etc.

@twrobel3 ETA on a review? Days; weeks; months? :stuck_out_tongue_winking_eye:

Any other feedback / changes required before merging?

Nope, looks good to go.  Merged!
Cheers,
-Taylor

Thanks!


https://docs.viromedia.com/ seems to be "inactive"

I can't seem to find information regarding when it will be up or if there's any other alternative. Are there downloadable links or other places I can refer to?

Does this mean that this project is not active?

I also need to read documentation but when i check it says not active..

Use this link for the Viro-community doc:
https://viro-community.readme.io/docs/overview


Storage: review PR on redefining authorization and action API

new endpoint design in #12

duplicate of #8


Make the CI a bit smarter

I've added a clever skip on the ci, if code isn't changed (i.e just markdown et al) the CI will skip

Its a bit weird... it still installs, but exits?


Ontology builder parallelization

Extending on issue #44  the function ontology_builder was optimized to parallelize itself across the number of CPU cores.

Closing due to inactivity


Force reload if a secret is updated

fixes #1342

This change is

I was just about to push my fix :)
Btw, is it enough? What about when a new secret is created? I'll give it a test…

Coverage decreased (-0.006%) to 44.018% when pulling bca894a388c34562c77c6a473b766ff879d48921 on aledbf:force-reload into 01a1aa378cb146578dc6023e35e65e4c54f63741 on kubernetes:master.

@stibi no, I'm updating the PR

@stibi please use quay.io/aledbf/nginx-ingress-controller:0.220

Coverage decreased (-0.03%) to 43.996% when pulling 33ce78ab66a1a83717898d8f78b514bf99c9d622 on aledbf:force-reload into 01a1aa378cb146578dc6023e35e65e4c54f63741 on kubernetes:master.

Coverage decreased (-0.03%) to 43.996% when pulling 33ce78ab66a1a83717898d8f78b514bf99c9d622 on aledbf:force-reload into 01a1aa378cb146578dc6023e35e65e4c54f63741 on kubernetes:master.


cFos Firmware 1.20 is not supported by this plugin

I updated my Wallbox to cFos Firmware 1.20, and now the plugin is not able to connect to my Wallbox.
My log shows the following:
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: homeassistant
Source: custom_components/powerbrain/sensor.py:82
Integration: cFos Powerbrain (documentation, issues)
First occurred: 07:42:46 (84 occurrences)
Last logged: 07:50:04
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 204, in _handle_refresh_interval
await self._async_refresh(log_failures=True, scheduled=True)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 349, in _async_refresh
self.async_update_listeners()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 146, in async_update_listeners
update_callback()
File "/config/custom_components/powerbrain/sensor.py", line 82, in _handle_coordinator_update
new_value = self.device.attributes[self.attribute]
TypeError: string indices must be integers

Thanks for reporting. In fact cFos has changed the API without notice. I will provide a fix very soon.

Works and thanks a lot


Merge release/1.0 branch to main

This picks up any changes from the 1.0.3 release that weren't already on the main branch.
Checklist

[X] I've read the Contribution Guidelines
[X] My contributions are licensed under the Swift license.
[ ] I've followed the coding style of the rest of the project.
[ ] I've added tests covering all new code paths my change adds to the project (if appropriate).
[ ] I've added benchmarks covering new functionality (if appropriate).
[ ] I've verified that my change does not break any existing tests or introduce unexplained benchmark regressions.
[ ] I've updated the documentation if necessary.

@swift-ci test


Add setup files for pip packaging

Starter files added

had to rename directory to be same as package name to be released.
not sure about github actions impact? some were ok others not.
had to remove the symlink, feel free to put something else there

The conflicts are my fault...
I manually pulled in the changes from this PR (as you should see)
except for the README.md change

On your main branch:
git checkout -b readme-change
to save the readme change
git checkout main
then
git reset --hard 95c3554d2951f651cf59ab282aba3ca3814bd7c9
git pull upstream main
I can pull in that change today... just a bit tired...

definitely work off of topic branches - keep main synced with upstream main

for a README.md change:
add the change to sources/FOOTER.md
then
make docs
git add sources index.html
git commit etc...
I use this in my git config:
git config --global pull.rebase true
git config pull.rebase true

this makes pull from upstream work - it works on topic branches too.
I will add a CONTRIBUTE file and we can document some of the work flow.

PS: I added a p2p library - I tested an example in the venv - worked.
11711df1ef0409e5062429d761d89930af4ccff6
I don't believe the setup is placing the build in the correct place - if you can check that - that would be great.
I will look for a CI script to test a python3 venv configuration.
👍🏽

OK will do

I made changes to fix setup build in this branch https://github.com/bitkarrot/0x20bf/tree/fix-setup
the p2p library looks interesting!

PS: I added a p2p library - I tested an example in the venv - worked.
11711df
I don't believe the setup is placing the build in the correct place - if you can check that - that would be great.
I will look for a CI script to test a python3 venv configuration.
👍🏽

conflicts should be fixed now.


group ordering rule

I believe all the information needed is in the XcodeProj structure.

Fixed by #8


Add basic SwiftUI Support

As the title. See the comments for details on what this entails and what parts can use more work.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


lib.types.*.check: return a message

Project description
We can improve type error messages by returning a string instead of false.
The module system can improve its error messages with these strings.
Other users of types can benefit from this too, for example validating configuration parameters in Nixpkgs, such as #153740
To implement this without breaking anything, we can make this variation of the type checking function optional.
So we'll keep the check : any -> bool attribute on types, add getErrorMessage : any -> nullOr str and add helper functions that are compatible with old / out-of-tree types.
One helper would be getTypeErrorMessage: type -> a -> nullOr str which returns a generic message like "value is not of type ${type.description}".
Another helper could be validate : type -> a -> a which uses getTypeErrorMessage to throw an error message as appropriate. It could also transform the value; supporting the coerceTo type.
We could deprecate the check attr at some point, by logging when lib.types.*.check is used.

This will also simplify testing, as the exceptions only occur in an optional utility function.

A distinction must be made between checks that are lazy and checks that aren't.
Non-module system users will expect a strict check; for example https://github.com/NixOS/nixpkgs/pull/173568.
The module system needs a shallow or lazy check.


Issue#16: Add display of bills

Add display of bills
update database
Delete useless code

Thanks Tung-Tung, I made a couple changes to remove the API keys.


对于支持jackson是否有什么考虑

项目使用jackson作为序列化工具，dubbo3额外引入了fastjson2，导致序列化工具重复臃肿，我看官网文档支持很多序列化工具，唯独不支持jackson,是否有自己的考虑

jackson序列化不支持map这种类型，反序列化会丢失数字等类型的精准对应关系，开启类型标注又太危险。这是我的个人猜测。

从dubbo3.2开始只保留了fastjson2、hession、jdk的引入，默认只支持这三种序列化方式，其他的都移动到 dubbo spi extension 中作为可选扩展组件了。
仓库目前已经实现了Jackson的序列化，目前因为还在做适配的原因所以暂时还未打包发布maven中央仓库，而且暂时只做了3.2的适配，有需求的话可以自行clone打包引入。之前的版本默认不支持Jackson是基于性能和依赖引入的考虑。

反序列化会丢失数字等类型的精准对应关系，开启类型标注又太危险

正如上面所说的，切换序列化需谨慎，而且dubbo目前还没有测试过完全排除fastjson2之后是否会出现预期之外的问题。

Starting from Dubbo 3.2, only the introductions of fastjson2, hession, and jdk are retained, and only these three serialization methods are supported by default. All other serialization methods have been moved to Dubbo SPI Extension as optional extension components.
Currently, the repository has implemented Jackson serialization. However, it is temporarily not packaged and released to the Maven Central Repository due to ongoing adapter development. Currently, only the adapter for Dubbo 3.2 is available. If you have a need for it, you can clone, package, and introduce it yourself. The previous versions did not support Jackson by default based on considerations of performance and dependency introduction.

Deserialization can lose the precise correspondence of types such as numbers, and enabling type annotations can be too risky.

As mentioned above, switching serialization should be cautious, and Dubbo has not yet tested whether there will be unexpected problems after completely excluding fastjson2.


Build 3.5 and 3.6 variants

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

conda-forge-admin, please rerender

conda-forge-admin, please rerender


[SPARK-18594] [SQL] Name Validation of Databases/Tables

What changes were proposed in this pull request?
Currently, the name validation checks are limited to table creation. It is enfored by Analyzer rule: PreWriteCheck.
However, table renaming and database creation have the same issues. It makes more sense to do the checks in SessionCatalog. This PR is to add it into SessionCatalog.
How was this patch tested?
Added test cases

Test build #69194 has started for PR 16018 at commit 27f5617.

cc @cloud-fan @yhuai

Test build #69194 has finished for PR 16018 at commit 27f5617.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69194/
Test PASSed.

LGTM

Test build #69199 has started for PR 16018 at commit 311f34b.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69199/
Test FAILed.

retest this please

Test build #69202 has started for PR 16018 at commit 311f34b.

Test build #69202 has finished for PR 16018 at commit 311f34b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69202/
Test FAILed.

retest this please

Test build #69204 has started for PR 16018 at commit 311f34b.

Test build #69204 has finished for PR 16018 at commit 311f34b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69204/
Test PASSed.

Thanks! Merging to master/2.1!


UI Dropdown menus are not folding up

My openOutpaint menu looks like this
https://i.imgur.com/CrgvO5A.png
Running on chrome browser
I've figured out whats going on. The menu has a variety of dropdown submenus that you're supposed to click to expand
Prompts
Stable Diffusion Settings
Save/Upscaling
Debug Info
However, these are being rendered as permanantly expanded even when closed. All the content is rendered ontop of each other in the same spot
If i click one to open it, the menus below it shift down to give it room, although those above in the list arent affected and will still render over it
Here's Stable Diffusion Settings and Prompts both expanded
https://i.imgur.com/qMFBbhO.png
They are mostly readable, so the program is useable, but this is still quite inconvenient
Great tool otherwise!

hey, would you mind filling out this section of the bug report form? this feels like another extension issue

Environment (please complete the following information):

OS and Version: [e.g. iOS 15, win10x64 v22h2, palmOS 3]
GPU: [e.g. GTX1660, RTX3090, RX750, Voodoo2]
Browser and Version: [e.g. chrome 108, safari 16.1]
Any browser extensions: [rationale: microsoft editor chrome addon hates overmask]
Commit of openOutpaint-webUI-extension: [e.g. 0217dec, https://github.com/zero01101/openOutpaint-webUI-extension/commit/342142952a63eddcb1cb5a1f18a9affc281e4526]
Commit of A1111 webUI: [e.g. c5bdba2, https://github.com/AUTOMATIC1111/stable-diffusion-webui/commit/5f1dfbbc959855fd90ba80c0c76301d2063772fa]
How you interact with A1111 webUI: [e.g. local hardware, colab, cloud host like linode]

@NanakoAC Were you able to resolve your issue?

no the issue is not resolved
Windows 10, Version	10.0.19044 Build 19044
GPU: Name	NVIDIA GeForce RTX 3090 Ti
Browser: Google Chrome | 80.0.3987.149 (Official Build) (64-bit) (cohort: Stable)
Extensions: Only one (dark reader. I tried disabling it, no change)
Not sure how to find those commits yet, but fairly recent
i use local hardware and google chrome

Browser: Google Chrome | 80.0.3987.149 (Official Build) (64-bit) (cohort: Stable)

wow so that's a nearly 3-year-outdated build you're using there, uh, any chance you could update that to something a bit more modern, or try a different updated browser?

Yeah... 3 years is quite a long time... Very surprised, actually, that openOutpaint managed to run at least okay at all.

Will be closing this issue for now as it seems to be an outdated browser version.


Fix helm may identify achieve of the application/x-gzip as application/vnd.ms-fontobject

What this PR does / why we need it:
Fixes:  #12261
Special notes for your reviewer:
I think the ensureArchive method should be hardened and the judgment of whether the achieve is application/x-gzip should be added. contentType can be used as an error message for the user.
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

Personally, I would switch the order of ensureArchive and LoadArchive. Something like:
	c, err := LoadArchive(raw)
	if err != nil {
            err = ensureArchive(name, raw)
	    if err != nil {
	 	return nil, err
	    }

            if err == gzip.ErrHeader {
			return nil, fmt.Errorf("file '%s' does not appear to be a valid chart file (details: %s)", name, err)
	    }
	}

And then rename ensureArchive to something more appropriate e.g. reportContentTypeError.
This means we only try to sniff the file content if and only if the actual loading fails. Which is what I see ensureArchive trying to do: report a more informative error iff the file is not an archive.

Thanks for the review. But I think verifying the file type before LoadArchive might be a more reasonable step. And LoadArchive may return an error for other reasons than the wrong file type.


Not working in Firefox or IE

Perhaps I have no idea what I'm doing, but I can't seem to get this to work in Firefox or IE.
I do have an error, but it doesn't seem to be impeding it from working in Chrome.

Uncaught TypeError: $(...).simplebar is not a function

Here is my code up until the actual content that changes from page to page:
<!doctype html>

<meta charset="utf-8">
<title>Coley Verbick: Web, Mobile, Radio Production, Voice Over and Photography</title>
<link href="../css/styles.css" rel="stylesheet" type="text/css">
<link href="http://overpass-30e2.kxcdn.com/overpass.css" rel="stylesheet" />
<link href="../css/simplebar.css"  rel="stylesheet"/>

Home

Portfolio

About

Resume

Contact

<input type="checkbox" id="nav-trigger" class="nav-trigger" />

I know you're rewriting this plugin, but the other suggested plugins broke my jQuery.  If the whole not working in Firefox and IE thing is part of the rewrite, just let me know and I'll see if I can figure out another way.

Hi,
You seem to have loaded perfect-scrollbar.jquery.js instead of simplebar! :)

Even with changing that I'm still getting ugly scrollbars in Firefox and IE.  There are several warnings within the CSS.

Timestamp: 6/1/2016 10:26:25 PM
Warning: Unknown pseudo-class or pseudo-element '-moz-scrollbar'.  Ruleset ignored due to bad selector.
Source File: file:///C:/Users/Coley%20Coley/Documents/My%20Webs/coley/css/simplebar.css
Line: 24, Column: 27
Source Code:
.simplebar-scroll-content::-moz-scrollbar {


Settings - Blank page opens when user navigates to Profile screen

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
1.Open the app
2. Login with existing account
3. Tap on user's avatar
4. Select "Profile"
Expected Result:
Profile page should open
Actual Result:
Blank page opens when user navigates to Profile screen
Workaround:
Unknown
Platform:

Where is this issue occurring?

iOS
Android

Version Number:  1.1.11-0
Reproducible in staging?: Yes
Reproducible in production?: No
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: https://user-images.githubusercontent.com/43996225/139373204-c72b808c-b820-4abe-a1d2-6c39ae9aefbc.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:
View all open jobs on GitHub

Nice, yup you are correct santhosh and your solution is good too. Since this is a deploy blocker i've gone ahead and created a PR so we can CP and inform QA to test soon.

Fix for this was merged and will be deployed in 1.1.11-1

This worked 🎉


XMPP Client not showing in ext sim list

Only shows up if the Resource in the client is set to MyApp and the Application Name in the ExtSim list is set to MyApp.
If the Resource name is changed, it shows up in the Sim UI but still doesn't communicate.


Renaming a model attribute or deleting an attribute and creating a new attribute with the same args of the deleted one

I am trying to rename an attribute, but instead, it renames my model:
builder
  .model(model.name)
  .blockAttribute(ID_ATTRIBUTE_NAME)
  .then<ModelAttribute>((attr) => {
      attr.name = UNIQUE_ATTRIBUTE_NAME;
   });

I tried another way, which is finding the attribute I want to rename, taking its args and creating from it a new attribute, from the type (name) I want and then delete the attribute that I don't want:
const argsFromIdAttribute = (
        modelIdAttribute.args[0].value as RelationArray
      ).args;

 // change the @@id attribute to @@unique attribute
      builder
        .model(model.name)
        .blockAttribute(UNIQUE_ATTRIBUTE_NAME, argsFromIdAttribute);

// remove the @@id attribute from the model - I know it will not work because I need to remove a block attribute, but the
     // lib doesn't have it so consider it as a pseudo code
      builder.model(model.name).removeAttribute(ID_ATTRIBUTE_NAME);

In this case, I am getting the following error: Subject must be a prisma field!
What am I doing wrong? Does this library support what I am trying to do?

Hi @abrl91,
You're right, the API isn't very clear about this. The .then() function is always going to return the current subject of the builder.
Subjects can only be nodes that can contain other nodes, such as models which can contain fields or attributes, or fields which can contain attributes. An attribute never becomes the current subject because it doesn't contain anything else. However, I agree that it isn't very satisfying from a user perspective for the builder to make this distinction. It would be nice for the TypeScript system to automatically assign the type of the current subject to .then() so that you would at least know what type you were receiving, but I couldn't figure out how to make that work.
These are the kinds of kinks that I want to make sure are worked out of the interface before releasing v1 of the library, and I'm open to suggestions for how it can be improved.
.removeAttribute() similarly, is expecting to target field attributes, not model attributes. Although I don't think there's any technical reason why it couldn't support both. That would be a good enhancement.
In the meantime, I think this would achieve the effect you're seeking:
    builder.model(model.name).then<Model>((model) => {
      for (const prop of model.properties) {
        if (prop.type === 'attribute' && prop.name === ID_ATTRIBUTE_NAME) {
          prop.name = UNIQUE_ATTRIBUTE_NAME;
          return;
        }
      }
    });

@MrLeebo Thank you, it works!

Hi @abrl91,
You're right, the API isn't very clear about this. The .then() function is always going to return the current subject of the builder.
Subjects can only be nodes that can contain other nodes, such as models which can contain fields or attributes, or fields which can contain attributes. An attribute never becomes the current subject because it doesn't contain anything else. However, I agree that it isn't very satisfying from a user perspective for the builder to make this distinction. It would be nice for the TypeScript system to automatically assign the type of the current subject to .then() so that you would at least know what type you were receiving, but I couldn't figure out how to make that work.
These are the kinds of kinks that I want to make sure are worked out of the interface before releasing v1 of the library, and I'm open to suggestions for how it can be improved.
.removeAttribute() similarly, is expecting to target field attributes, not model attributes. Although I don't think there's any technical reason why it couldn't support both. That would be a good enhancement.
In the meantime, I think this would achieve the effect you're seeking:
    builder.model(model.name).then<Model>((model) => {
      for (const prop of model.properties) {
        if (prop.type === 'attribute' && prop.name === ID_ATTRIBUTE_NAME) {
          prop.name = UNIQUE_ATTRIBUTE_NAME;
          return;
        }
      }
    });

The issue with the .then() was confusing because it seems like the subject can get Block or Property

About removeAttribute() - I know it is only for a field attribute. I just wrote it as a pseudo code to emphasize what I am trying to do.
BTW, we use your library for a very important feature (in Amplication), and I must say that it really helps us and it is very easy to use and understand.

The issue with the .then() was confusing because it seems like the subject can get Block or Property

Yeah, that type definition is too broad. It should be schema.Block | schema.Field

Hi @abrl91,
You're right, the API isn't very clear about this. The .then() function is always going to return the current subject of the builder.
Subjects can only be nodes that can contain other nodes, such as models which can contain fields or attributes, or fields which can contain attributes. An attribute never becomes the current subject because it doesn't contain anything else. However, I agree that it isn't very satisfying from a user perspective for the builder to make this distinction. It would be nice for the TypeScript system to automatically assign the type of the current subject to .then() so that you would at least know what type you were receiving, but I couldn't figure out how to make that work.
These are the kinds of kinks that I want to make sure are worked out of the interface before releasing v1 of the library, and I'm open to suggestions for how it can be improved.
.removeAttribute() similarly, is expecting to target field attributes, not model attributes. Although I don't think there's any technical reason why it couldn't support both. That would be a good enhancement.
In the meantime, I think this would achieve the effect you're seeking:
    builder.model(model.name).then<Model>((model) => {
      for (const prop of model.properties) {
        if (prop.type === 'attribute' && prop.name === ID_ATTRIBUTE_NAME) {
          prop.name = UNIQUE_ATTRIBUTE_NAME;
          return;
        }
      }
    });

Hey @MrLeebo
I tried to use the same technique to rename the args in the @@inique or @@index or @@id attributes
for example
model Example {
  text_id             Int
  info_id             Int
  converted       Boolean?

  @@id([text_id, nfo_id])
  @@index([ info_id ], map: "app_text_info")
}

with something like:
const modelIdAttribute = modelAttributes.find(
   (attribute) => attribute.name === ID_ATTRIBUTE_NAME
);

(modelIdAttribute.args[0].value as RelationArray)?.args.map((arg) =>
  formatFieldName(arg)
);

Do you have any idea why it doesn't work and how to do it right?


HTML

HTML
User Story
AS A marketing agency
I WANT a codebase that follows accessibility standards
SO THAT our own site is optimized for search engines
Acceptance Criteria
GIVEN I’m a marketing agency user
AND the codebase follows accessibility standards
WHEN a search engine trawls our website
THEN semantic HTML elements can be found throughout the source code
AND HTML elements follow a logical structure independent of styling and positioning
AND Image and icon elements contain accessible alt attributes
AND heading attributes fall in sequential order
AND Title elements contain a concise, descriptive title
AND Application's links all function correctly.

HTML elements follow a logical structure independent of styling and positioning
Image and icon elements contain accessible alt attributes
Heading attributes fall in sequential order
Title elements contain a concise, descriptive title
Application's links all function correctly.


Create windows-fix-crx-installing.patch

This small patch should fix crx installing bug.

Actually I think I'll combine this with #41 since that PR seems to be almost done. Also, this patch isn't referenced in the patches/series file...

Merged in #41.


Using Oracle oci driver causes NPE, because of OracleURLParser "thin" expectations

When using "oci" driver instead of "thin" the OracleURLParser is not capable of recognizing the pattern and returns null. This causes NPE later. At the same time the prefix that is expected for the OracleURLParser to pick up the connection string is "jdbc:oracle" and not "jdbc:oracle:thin". This makes it impossible to register custom parser specifically for oci.

@ivan-slavchev would you like to submit PR?

https://github.com/opentracing-contrib/java-jdbc/pull/72

0.2.10 release with fix will be available in couple of hours


Chrome 71: Clicking on a link(Set to open in new tab/window) in fullscreen window will exit fullscreen and return to default size.

Even if I try to view source by right clicking, will exit full screen mode.

That isn't happening to me.


First presentation !

As you all know, the first presentation is coming pretty fast !
So I will try to anticipate the big midterm rush by starting to think about it right now.
Here is what we need to do according to the file we were given:

I think it would be great to prepare individually what you all did since the beginning, you will have to present those.

Also, I think it would be great to have a visual representation of the project: big labelled boxes that are linked to represent every part of the code (Classes and important functions)

#49


[SPIKE] State Management

Description
As we move toward a new React-based stack, we should look into the various state management libraries that are available and make a decision about which to go forward with.

We currently use Vuex - we would need to move toward a different library in the React world.
Tentative Example options:

Just useReducer
Redux + Redux Toolkit
Zustand

Acceptance Criteria

We have copied this Notion template to a subpage of the Tech Modernization page named the same as this issue and have filled out the various sections appropriately
We have added it as a link in the top-level Tech Modernization page

Associated Notion doc

PR here for GitHub version


feature/add loop option to scroll tools

Allow the scroll tools StackScrollToolMouseWheelTool and StackScrollTool to configure the loop option.
PS: this is my first PR and i read the contributing guide and wish i did it right.

Looks great, can you add a todo for the volume scroll logic that does not implement loop yet

Thanks for your time, Can you check again?


How Do I Contact Defi Wallet Support Number?

How can I recover my Defi Wallet account? If you need to recover your Defi Wallet account, you can contact their customer service hotline at +1~53O-.447-.2879 or +1~53O-.447-.2879 USA for assistance in the recovery process.
How to contact Defi Wallet Manager? You can access live chat by clicking the "Contact Us" ☎+1~53O-.447-.2879 button in the help center and then selecting "Chat." Phone: Defi Wallet also offers phone support for urgent issues. You can call Defi Wallet at ☎+1~53O-.447-.2879 for Quick response & Support. There are in brief ways to talk to someone on Defi Wallet.
Does Defi Wallet have a live chat? Yes, Defi Wallet does offer a live chat option for customer support. To access the live chat feature:
Go to Defi Wallet's Help Center on the platform.
Look for the "Contact Us" ☎+1~53O-.447-.2879 option.If you are trying to reach Defi Wallet Support +1~53O-.447-.2879 (24/7), the only Defi Wallet phone number is ☎+1+1~53O-.447-.2879(24/7) or +1~53O-.447-.2879 USA for Quick response & Support. You can also access live chat by clicking the "Contact Us" button in the help center and then selecting "Chat."
Choose the chat option to speak with a live person.
You can also contact Defi Wallet support at ☎+1~53O-.447-.2879 (Talk with Human) & (☎+1~53O-.447-.2879 (Contact-USA)).
Follow the prompts to describe your issue and get assistance.

Closed as spam issue.


Minor NPE for multicluster.

configStore seems to be nil for remotes.

@costinm: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
c34557a328ead90bd415fd978efe69270aaaca9e
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@costinm The cla is changed to LF, you need to resign

https://github.com/istio/istio/pull/44103  need to fix select policy

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Kubecost chart failing to download

When running the example "eks-cluster-with-new-vpc" and deploying the add-ons with "terraform apply -target="module.eks_blueprints_kubernetes_addons"" I am experiencing an error during the kubecost chart download:
Error: could not download chart: failed to download "oci://public.ecr.aws/kubecost/cost-analyzer/cost-analyzer" at version "1.96.0"
with module.eks_blueprints_kubernetes_addons.module.kubecost[0].module.helm_addon.helm_release.addon[0],
on ../../modules/kubernetes-addons/helm-addon/main.tf line 1, in resource "helm_release" "addon":
1: resource "helm_release" "addon" {
The download link looks strange, with "cost-analyzer" duplicated. How can I fix this?

Hello @espuuks this issue should be fixed once we merge this https://github.com/aws-ia/terraform-aws-eks-blueprints/pull/915

Hi still facing the same error with v4.11.0. Thanks

What terminal problem did you have? I'm having the same error  @ZeroDeth


Flaky build: AppVeyor build sometimes fails due to problems uploading JUnit XML

In our AppVeyor builds, we sometimes see the build fail when it has trouble uploading the JUnit XML files. For example...
...
Finished in 710.703 seconds
2089 tests, 11649 assertions, 0 failures, 8 skipped
Command exited with code 1
$wc = New-Object 'System.Net.WebClient'
$endpoint = "https://ci.appveyor.com/api/testresults/junit/$($env:APPVEYOR_JOB_ID)"
Write-Output "Searching for JUnit XML output beneath $($env:TEST_JUNIT_XML_ROOT)"
Get-ChildItem -Path $env:TEST_JUNIT_XML_ROOT -Recurse -File -Name -Include "*.xml" | ForEach-Object {
  $full = "$($env:TEST_JUNIT_XML_ROOT)\$($_)"
  Write-Output "Uploading JUnit XML file $($full)"
  $wc.UploadFile($endpoint, $full)
}
Searching for JUnit XML output beneath c:\projects\junit-test-results
Uploading JUnit XML file c:\projects\junit-test-results\core-main-process.xml
Uploading JUnit XML file c:\projects\junit-test-results\core-render-process.xml
Exception calling "UploadFile" with "2" argument(s): "The remote server returned an error: (500) Internal Server Error."
At line:7 char:3
+   $wc.UploadFile($endpoint, $full)
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : WebException

Rebuilding can sometimes resolve the failure.
I wonder if we could enhance the build script to retry the upload if it fails at first. Alternatively, perhaps we could consider catching this error and logging it, but not allowing it to cause the overall build to fail.

Affected CI provider(s): AppVeyor
Affected platform(s): Windows
Example commit experiencing flakiness: https://github.com/atom/atom/commit/b6bf3a5c5d2d74c998cb953131d516e854893288
Example failing build at that commit: https://ci.appveyor.com/project/Atom/atom/builds/23020313/job/aeqv4kml7rhony8o
Example passing build at that commit: https://ci.appveyor.com/project/Atom/atom/builds/23023754
Example log from failing build: https://github.com/atom/atom/files/2968124/build.log

Happened two more times:

https://ci.appveyor.com/project/Atom/atom/builds/22988139/job/qsbmjlisx3m70qd8#L2237
https://ci.appveyor.com/project/Atom/atom/builds/22989936/job/q8ns484u2l970ksx#L2229

Another time:

https://ci.appveyor.com/project/Atom/atom/builds/23187726/job/deb4by5jr3mcr0k8

A couple more:

https://ci.appveyor.com/project/Atom/atom/builds/23222531/job/x4afnj1o7x9phiho#L2224
https://ci.appveyor.com/project/Atom/atom/builds/23280615/job/81uh9159k4s6691v#L2250


update(docker): split the build phase into multiple RUN commands

What type of PR is this?
/kind bug
/kind cleanup
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it:
This PR splits various make commands into different docker RUN instructions, in this way we can catch errors in single steps. With the previous approach :point_down: we were not able to catch failures when make package failed: the CI job was successful but the build failed https://app.circleci.com/pipelines/github/falcosecurity/falco/3647/workflows/1fca77ee-28c8-4a4c-8344-ff44f3db447f/jobs/31261
RUN source scl_source enable devtoolset-9; \
    cmake ${CMAKE_OPTIONS} /source; \
    make falco -j${MAKE_JOBS}; \
    make package; \
    make tests -j${MAKE_JOBS}; \
    make all -j${MAKE_JOBS}

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

@Andreagit97: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

docker/OWNERS [Andreagit97]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

I love this!
I'd target Falco 0.34 since we will surely be biten by this issue during the release IMHO. @LucaGuerra ?
/milestone 0.34.0

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

docker/OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 902a3da8583eec555e74fa3e61d0e71a3f02b8fb

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

docker/OWNERS [Andreagit97,FedeDP,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Updated python requirements.

This included django 1.8 (but django 1.7 is still supported)

Remarks to be discussed.

travis will be fixed after I rebase this on top of #1591 (after it is merged)

Rebase and merge.


[flutter_tool] Screenshot command must require device only for _kDeviceType

There are cases where we have access to the observatory without having a device connection accessible.

Please add a test case for this new behavior

Please add a test case for this new behavior

Done


LADiff RAG version

Hi.
Does your released code also contain content of LADiff, augmented with retrieval?
Is RAG also done during training time?

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Hello @hkchae96 ,
The RAG version of LADiff is currently not yet available. We are working on refactoring the code, which will be ready before the conference. We will release the RAG version, including the training and evaluation code.
Thank you.

@hkchae96 RAG code is now available in branch rag!


Doesnt work on Monterey

I've tested on monterey, but it don't mute the microphone

I cannot confirm this. I am on macOS 12.6 (M1 Pro MacBook Pro) and the app is working fine.

Hey @HugoMinariAtlas, sorry for the late response.
I'm also on 12.6 with 2 different MacBook Pros and don't have issues.
So what exactly isn't working for you?


How to change the height?

I can't change the height of the widget. It is not possible to do it with SizedBox.

Hey @ledesmac96
No, you can't specify the dropdown height. But I'm thinking about to make this property available in future release!

Still can't set height. Wrapping in SizedBox also not working.

Hello, do you plan on adding this property ?

Hey @angela-boyadjian
Property overlayHeight is already available. Only applicable if items are greater than 4 otherwise adjust automatically.
Let me know if this is not helpful for you!


macOS - macOS defaults to using Apple.News instead of NNW

I just recently had a peculiar issue happen. macOS refuses to let NNW handle RSS schemes anymore. Meaning this issue manifested itself and NNW use to handle RSS schemes. So this is strange to me. The only difference is I have had NNW open for a few days uninterrupted.
I even checked SwiftDefault to confirm that NNW should be handling RSS schemes.
Not saying this is a bug, but does anyone else have this issue? (and hopefully knows how to fix it)
NNW:5.0.3
macOS:10.15.1
and incase in mattes Apple.News: 5.2

update never mind...didn't realize the URL schemes is "feed" and "feeds". found that out by looking the plist.

You should be able to set your default aggregator in NetNewsWire itself, in preferences.
If that doesn’t work, please let us know so we can reopen this bug. :)

Thanks. Still not sure why it switched, but it was an easy fix


build(dependabot): remove docker auto-updates

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 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
608

Relevant Lines:
608

💛  - Coveralls


add lex error for function args

Add lex error DuplicateArgumentError

The codes below will now yield SyntaxError due to duplicate arguments in function definition
def f(a, a): pass
def f(a, *a): pass
def f(*a, **a): pass
lambda a,a: 0
lambda a,*a: 0

Example error message
SyntaxError: duplicate argument in function definition at line 2 column 9
def f(a, a): pass
        ^

Add lex error for named arguments must follow bare *

The code below will now yield SyntaxError if no kw arguments follow bare asterisk

def f(a, b, *): pass

Example error message
SyntaxError: named arguments must follow bare * at line 2 column 12
def f(a, b, *): pass
           ^

The code below works fine as expected

def f(a, b, *, c): pass

clippy is complaining for the return Ok(arguments); line and test_argument_handling is now passing. If you remove the decorator from the function (in test_compile.py) and fix the clippy error this should clear all issues.

a formatting issue has come up, also, since #4367 was just merged, rebase on main so no hiccups occur when merging

There are a few more tests that are now "unexpectedly" passing.
I believe you can use the following command to test your changes locally:
# this runs all of the tests (not necessary if you know which test is affected)
cargo run --release --features ssl,jit -- -m test -j 1 -u all --slowest --fail-env-changed -v
# this runs only the test suite named "test_whatever" (usually located at `Lib/test/test_whatever.py`)
cargo run --release --features ssl,jit -- -m test -j 1 -u all --slowest --fail-env-changed -v test_whatever

Thanks @nicku12345!


Python Issue

At present attempting to run the code however this error is being returned. Tired with older versions of the CDK however same error is returned
Software
npm 8.3.1
Python 3.10.2
CDK 2.12.0 (build c9786db)
aws-cli/2.4.3 Python/3.8.8 Windows/10 exe/AMD64 prompt/off
cdk bootstrap aws://OPPS/eu-west-2
Traceback (most recent call last):
  File "C:\Users\USER\Documents\Git\aws-cdk-tfsec\app.py", line 5, in <module>
    from aws_cdk import core
  File "C:\Users\USER\AppData\Local\Programs\Python\Python310\lib\site-packages\aws_cdk\core\__init__.py", line 4925, in <module>
    class ConstructNode(metaclass=jsii.JSIIMeta, jsii_type="@aws-cdk/core.ConstructNode"):
  File "C:\Users\USER\AppData\Local\Programs\Python\Python310\lib\site-packages\aws_cdk\core\__init__.py", line 4963, in ConstructNode
    runtime_info: typing.Optional[aws_cdk.cx_api.RuntimeInfo] = None,
AttributeError: module 'aws_cdk.cx_api' has no attribute 'RuntimeInfo'

Hi @steveyminecraft
Thanks for reporting this issue. I want to ask you if you could test two things:

Downgrade the CDK version to 1.103.0 (It's not mentioned in the README but the dependencies are set for this particular version)
Could you try with Python 3.7 ?  I have tested also with Python 3.9, 3.10 and 3.12 and getting a different issue with the core package of CDK.

Please let me know your tests.

Hi @steveyminecraft ,
Did you have any chance to review my suggestions?
Regards

Closing due to inactivity


v1.27.0 - an stacktrace is shown if idb_companion is not installed

Describe the bug
When running Maestro on iOS without having idb_companion installed it spews out a stack trace instead of guiding user to necessary steps (i.e. installing idb_companion)

Hey @dmitry-zaitsev we wouldn't need IDB with latest release in v1.31.0. maestro is now decoupled with idb 🎉


VS Terminal

Hello, I have a problem with running the Python code in visual studio, its just repeat the results in Terminal each time I run the code! Any help guys. Thank you.

Each time you run the program VS Code outputs in the same terminal/CMD, if you're getting confused then just delete the terminal before running the code again or use
For Windows:
cls

For Linux
clear

in the terminal/cmd before running the code again.


[FR] changeset status --only

Affected Packages
cli
Problem
Would love a simple way to use changeset status in a CLI flow that doesn't involve string parsing or saving to a JSON file such that I can chain commands off it. The specific use case is automating a release for only patches.
Proposed solution
Would love something like changeset status --only patch which exits 0 if only patch changes are detected such that it can be chained like changeset status --only patch && yarn release

+1. related to https://github.com/changesets/changesets/issues/1308#issuecomment-1937431855.
Plz introduce a --strict or (--exit-code a la git) semantics to {version,status} subcommands.


Spring boot azure keyvault refresh on demand

I am using spring boot with azure's keyvault
        <dependency>
			<groupId>com.azure.spring</groupId>
			<artifactId>azure-spring-boot-starter-keyvault-secrets</artifactId>
		</dependency>

but there is a problem, when I want to update secret.
How to force for example via rest api lets say, refresh of this value ?
   @Value("${x-value}") private val xValue: String = "0"
thanks!

https://github.com/Azure/azure-sdk-for-java/issues/27731


All components are loaded at once in development mode

Environment

Operating System: Windows_NT
Node Version:     v18.18.1
Nuxt Version:     3.7.4
CLI Version:      3.9.0
Nitro Version:    2.6.3
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      app, buildDir, runtimeConfig, imports, css, components, alias, modules, auth, image, googleFonts, colorMode
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>@/modules/google-fonts/module<EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-kpf6bg?file=plugins%2Fnxui.ts
Describe the bug

Created some custom components in the /packages/components directory
Created /plugins/nxui.ts file to load the components.
When I run pnpm run dev, all components in the /packages/componets directory will be loaded.
When I refresh the page, all components in the /packages/componets directory are loaded.

This is a minimal example, I just created a card component under /packages/compoents, imported and exported the component in /packages/compoents/index.ts. The plugins are imported in /plugins/nxui.ts.
My page doesn't use the card component, but when the page loads it introduces it.
As you can imagine, when I have dozens of components, it takes dozens of seconds for the page to load.
I don't know from which version it became like this.

Additional context
No response
Logs
No response

They are all loaded because you are loading all of them in the plugin. I'm not sure I would consider this a Nuxt issue. What do you think should happen?
(Part of this is how Vite works in dev mode - vite has to load every component because you are initialising them.)

They are all loaded because you are loading all of them in the plugin. I'm not sure I would consider this a Nuxt issue. What do you think should happen?
(Part of this is how Vite works in dev mode - vite has to load every component because you are initialising them.)

You may not understand what I mean.
Let's ignore components.
For example, let me create the folder /packages/utils
Create is.ts,index.ts in this folder
is.ts
export const isUndefined = (val: any): val is undefined =>
  val === undefined

index.ts
export * from './is'

Now, I don't import them in any of the components, but nuxt.js automatically loads them all after I execute npm run dev. What I understand is that it will only be loaded when I import /packages/utils/is.ts or /packages/utils/index in the component?
Now, I don't import them in any of the components, but when I execute npm run dev and access localhost:3000 through the browser, nuxt.js will automatically load them all. The problem caused by this is that no matter whether I actually import and use the module in the project, nuxt will load them. In the end, it will take dozens of seconds to load when I visit or refresh the page. This is very painful during the development process.

Would you update your reproduction to show this?

Would you update your reproduction to show this?

Ok, I have a rough idea of what's causing this problem, I need a moment to put together a minimal example

@cdwmhcc Hey, have u managed to do smth with this? Since I have same problem

I think it's a Vite think rather than Nuxt https://github.com/vitejs/vite/issues/8237