[WIP] Fix/BaseSkillTestCase.setup

Proposed changes
changes the setup method on BaseSkillTestCase from a class method into a regular method. This will only affect mypy signature checking; I have chosen not to change it into setup_class since it would affect code execution logic.
After investigation it seems logical to turn the method, which is supposed to setup the class, into setup_class instead. With respect to backwards incompatibility, I suggest to introduce a setup (non-class method) that raises a DeprecationWarning :
def setup(self, **kwargs: Any) -> None:
    warn("Use .setup_class or overwrite this method", DeprecationWarning, level=2)
    self.setup_class(**kwargs)

references:

python docs
SO ref

Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to agents-aea?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.
[ ] Lint and unit tests pass locally with my changes and CI passes too
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that code coverage does not decrease.
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
DELETE INCLUSIVE THIS AND BELOW FOR STANDARD PR
Release summary
Version number: [e.g. 1.0.1]
Release details
Describe in short the main changes with the new release.
Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the main branch (left side), from develop
[ ] Lint and unit tests pass locally and in CI
[ ] I have checked the fingerprint hashes are correct by running (aea hash all --check)
[ ] I have regenerated the latest API docs
[ ] I built the documentation and updated it with the latest changes
[ ] I have added an item in HISTORY.md for this release
[ ] I bumped the version number in the aea/__version__.py file.
[ ] I bumped the version number in every Docker image of the repo and published it. Also, I built and published them with tag latest
(check the READMEs of aea-develop
and aea-user)
[ ] I have pushed the latest packages to the registry.
[ ] I have uploaded the latest aea to PyPI.
[ ] I have uploaded the latest plugins to PyPI.

Further comments
Write here any other comment about the release, if any.

Failing tests are those that expect a fresh setup and, looking into next.
=========================== short test summary info ============================
FAILED tests/test_cli/test_get_address.py::TestGetAddressCommand::test_get_address[fake-password]
FAILED tests/test_cli/test_get_wealth.py::TestGetWealth::test_get_wealth[None]
FAILED tests/test_test_tools/test_test_skill.py::TestSkillTestCase::test_get_quantity_in_outbox
FAILED tests/test_test_tools/test_test_skill.py::TestSkillTestCase::test_drop_messages_from_outbox
FAILED tests/test_test_tools/test_test_skill.py::TestSkillTestCase::test_assert_quantity_in_decision_making_queue
FAILED tests/test_cli/test_get_multiaddress.py::TestGetMultiAddressCommandNegativeMissingKey::test_run[None]
FAILED tests/test_cli/test_get_multiaddress.py::TestGetMultiAddressCommandConnectionPositive::test_run[fake-password]
FAILED tests/test_cli/test_get_multiaddress.py::TestGetMultiAddressCommandConnectionIdPositive::test_run[fake-password]
FAILED tests/test_cli/test_get_multiaddress.py::TestGetMultiAddressCommandConnectionIdURIPositive::test_run[fake-password]
FAILED tests/test_cli/test_get_multiaddress.py::TestGetMultiAddressCommandNegativeBadUri::test_run[None]
FAILED tests/test_cli/test_get_multiaddress.py::TestGetMultiAddressCommandNegativeFullMultiaddrComputation::test_run[fake-password]
FAILED tests/test_cli/test_get_multiaddress.py::TestGetMultiAddressCommandPositive::test_run[None]
FAILED tests/test_cli/test_get_multiaddress.py::TestGetMultiAddressCommandConnectionNegative::test_run[None]
FAILED tests/test_cli/test_get_multiaddress.py::TestGetMultiAddressCommandNegativeBadPortField::test_run[fake-password]
FAILED tests/test_cli/test_get_multiaddress.py::TestGetMultiAddressCommandNegativeBadConnectionId::test_run[None]
FAILED tests/test_cli/test_get_multiaddress.py::TestGetMultiAddressCommandNegativePeerId::test_run[None]
FAILED tests/test_cli/test_get_multiaddress.py::TestGetMultiAddressCommandNegativeOnlyHostSpecified::test_run[None]
FAILED tests/test_cli/test_get_multiaddress.py::TestGetMultiAddressCommandNegativeUriNotExisting::test_run[fake-password]
FAILED tests/test_cli/test_get_multiaddress.py::TestGetMultiAddressCommandNegativeBadHostField::test_run[None]
= 19 failed, 2328 passed, 120 skipped, 59 deselected, 9 warnings, 2 rerun in 1492.29s (0:24:52) =


Measuring Response Time Always Get -1

Hi.. When I try to measuring response time, I always get -1. I am using rest assured version 3.0.5
already use this method:
System.out.println("ResTime:"+response.time());
System.out.println("ResTime:"+response.timeIn(TimeUnit.MICROSECONDS));

Closed this issue. this issue not from rest-assured. but from Serenity. because I use serenity rest assured.


Bug in the code - it doesn't work.

For a thousand time, the dreaded "No such file or directory" that cannot be resolved for years.
The issue is pretty simple - the error states " No such file or directory: 'F:\Downloads\Chrome Downloads\NonaPhoneAlexa_output.wav'"
Here is the bummer - the original file is called NonaPhoneAlexa, the app tries to find NonaPhoneAlexa_output which is wrong.
The SAME FILE on the SAME LOCATION, works perfectly fine in 3.0.3 version. Obviously you changed something in the newer versions that causes this.

Duplicated https://github.com/IAHispano/Applio/issues/344


The peak method of GalaxyCluster can fail with a no attribute of unit

AttributeError                            Traceback (most recent call last)
 in
----> 1 src = GalaxyCluster(149.86, -11.02, 0.16, "A907bodge", r500=Quantity(1000, 'kpc'))
~/code/PycharmProjects/XGA/xga/sources/extended.py in init(self, ra, dec, redshift, name, r200, r500, r2500, richness, richness_err, wl_mass, wl_mass_err, custom_region_radius, use_peak, peak_lo_en, peak_hi_en, back_inn_rad_factor, back_out_rad_factor, cosmology, load_products, load_fits, clean_obs, clean_obs_reg, clean_obs_threshold, regen_merged, peak_find_method)
146                         rt = self.get_combined_ratemaps(peak_lo_en, peak_hi_en)
147                         peak = self.find_peak(rt)
--> 148                         self.peak = peak
149                         self.default_coord = peak
150
~/code/PycharmProjects/XGA/xga/sources/general.py in peak(self, new_peak)
381         :param Quantity new_peak: A new RA-DEC peak coordinate, in degrees.
382         """
--> 383         if not new_peak.unit.is_equivalent("deg"):
384             raise UnitConversionError("The new peak value must be in RA and DEC coordinates")
385         elif len(new_peak) != 2:
AttributeError: 'tuple' object has no attribute 'unit'
This happened when I guessed the coordinates of a cluster I want to test with:
src = GalaxyCluster(149.86, -11.02, 0.16, "A907bodge", r500=Quantity(1000, 'kpc'))

I re-discovered and fixed this bug in issue #739


targetNamespace

Subject is corrected to Kind: ServiceAccount
Commented out Indexer, it is not necessary for Unstructured List, but was necessary if Stuctured, in case it ever changes back to Structured.


feat: ChipSelectField supports creating new options

New prop ChipSelectFieldProps.onCreateNew will append a "Create new" option. When "Create new" is chosen, then the SelectField is replaced with the ChipTextField for creating a new option.
New prop ChipSelectFieldProps.disabled supports showing Tooltip for displaying a disabled reason.
ChipSelectField now uses React-Stately's 'useListData' to manage a dynamic list of option.
Updates tests and stories
Other changes:

React-Aria and React-Stately package version bumps.
Move the "DismissButton" component to always be in Popover instead of each caller needing to add it.
ChipTextField supports autoFocus

Super nit but what if we create two items with the same name? Should it be like this?

Super nit but what if we create two items with the same name? Should it be like this?

Yea, great question. Right now we do not do any dedupe logic. As per these being prototype components, these sort of edge cases aren't being captured. I'm sure there will most likely be follow ups to address this sort of behavior, or even how to deal with typos? FWIW, the caller could potentially catch duplicates in the onCreateNew callback and throw an error or something.


Logs fail when using logical ID

Description
sam logs errors with The specified log group does not exist. when a logical id is used, looks like it used the name you pass literally.
Steps to reproduce

Deploy a function named Hello without a FunctionName
Run sam logs -tn Hello

Observed result
$ sam logs -tn QueueCrawls --debug
# notable output:
2019-01-16 11:16:57 Fetching logs from CloudWatch with parameters {'logGroupName': '/aws/lambda/QueueCrawls', 'interleaved': True, 'startTime':<PHONE_NUMBER>370}

Expected result
Use the ID generated by SAM, in my case monitor-QueueCrawls-1FTA2THVAER1U.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

OS: Mac
sam --version: 0.6.0

Add --debug flag to command you are running

Closing as there has been no response.


[Adaptive Card iOS - AdaptiveCard.json]: Luminosity ratio for placeholder text 'Add a comment' with respect to background is '1.723.1' which is less than 4.5:1

Target Platforms
iOS
SDK Version
Version 1.0 (2.4.0-beta.<IP_ADDRESS>)
Application Name
Adaptive Cards
Problem Description
Test Environment:
Device: iPhone 11
iOS: 17.5.1
Application: Adaptive Cards
App Version: Version 1.0 (2.4.0-beta.<IP_ADDRESS>)
Tool: Accessibility Insight For Window
Repro Steps:

Launch Adaptive Cards iOS application.
Home screen will appear.
Navigate to "V1.0" control and select it.
Navigate to 'Elements' control and activate it.
Navigate to 'AdaptiveCards.json' under 'Elements' list item and activate it.
Card will be appear.
Navigate to 'Comment' button and activate it.
Navigate to 'Add a comment' text field.
Open the tool, check the contrast ratio, and observe the issue.

Actual Result:
Luminosity ratio for placeholder text 'Add a comment' is '1.723.1' with respect to background, which is less than 4.5:1.
Expected Result:
Luminosity ratio for placeholder text 'Add a comment' with respect to background should be equal to or greater than 4.5:1
Notes:
Issue is repro throughout the application with placeholder text like this.
User Experience:
When a minimum contrast ratio is not provided between text and its background, it is difficult for low-vision users as well as anyone in extreme lighting environments to read the content.
WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html
Screenshots

Card JSON
NA

Sample Code Language
No response
Sample Code
No response

Fix PR for this in https://github.com/microsoft/Teams-AdaptiveCards-Mobile/pull/244

Currently on build 1.0 (2.4.0-beta.<IP_ADDRESS>) there is no placeholder text is present, hence closing this issue.


added support for configurable uuid

fixes https://github.com/pivotal-cf/cf-rabbitmq-release/issues/9

bump

@longnguyen11288 have you signed the Pivotal CLA?

@benlaplanche I have

bump

Hello longnguyen11288, I have accepted this change in commit: https://github.com/pivotal-cf/cf-rabbitmq-release/commit/fe18845d610805733b5e2e3355e6a2d8c742095d and fixed a failing broker unit test in https://github.com/pivotal-cf/cf-rabbitmq-release/commit/413ac6a437ba44e6427bc775920c455bf93c3806 which you may want.
This change should be available in the cf-rabbitmq-170 release.
Thank you for the pull request.


⚠ Bofrost.de has degraded performance

In cc417cd, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1424 ms

Resolved: Bofrost.de performance has improved in fbc3f2e after 6 minutes.


Local model loading error with LM Studio

Bug Description
As with Ollama, I am unable to connect to LM Studio as well. LM-Studio is running, the latest version. Interestingly the error is similar to the Ollama error.
This seems to be an global issue with local model loading.
Reproduction

Start LM Studio
Add LM Studio to the workspace in Langflow.

Expected behavior
Local models should be loaded.
Who can help?

@igorrCarvalho

Operating System
Fedora 38 Workstation
Langflow Version
1.1.1
Python Version
None
Screenshot

Flow File
Please see screenshot.

Hi @byronichero
I've attempted to reproduce the issue you reported but couldn't replicate the error using the latest version of Langflow.
I tested the setup using two different methods:

Direct Repository Clone

Cloned the Langflow repository
Used make run_cli in one terminal

Split Terminal Approach

Used make frontend in one terminal
Ran make backend in another terminal

Both worked without errors.
You can also try the simplified CLI installation:
uv pip install langflow
uv run langflow run```

Please follow up our documentation: [DOCS](https://docs.langflow.org/get-started-installation)

![image](https://github.com/user-attachments/assets/b29f86c5-11ca-4c8f-8c51-ac5b90a90f14)
![image](https://github.com/user-attachments/assets/21b7994c-1f85-4f37-9a84-019b7284253a)
![image](https://github.com/user-attachments/assets/8b78fefc-2faf-45f7-8da6-5f88bfd1b1c6)


Microsoft Entra Authentication

We use Microsoft Entra Authentication for our Azure Elastic pool Dbs.
There is no option for this in login form.

Hi, you can enter a connection string in the source textbox instead of using the Connect dialog to build the connection string.  I think this will allow you to use Entra.  DBA Dash is using the latest SqlClient so it should support this.
This link has some connection string examples.
Let me know if it works.

It would be nice to have the configuration GUI allow for the selection of "Microsoft Entra ID with MFA" in the drop down, so we can put in the EID user name and then it would do the normal browser pop to allow the password and MFA for getting the token.  I think this is OAuth.

We have this working
We used the command line DBADashConfig -c to set them up
example connection string below - we've given the VM running the DBA dash server a managed identity and then granted that required access on Azure SQL Servers we want to monitor
"ConnectionString": "Data Source=***********.database.windows.net;Encrypt=True;Trust Server Certificate=True;Authentication=ActiveDirectoryManagedIdentity;Application Name=DBADash",

New connection dialog coming soon...

Included in 3.10 🚀


Adding GetRecommendedRdsInstanceType to RDS module

PR to address #783
This PR adds functionality to the RDS module to get a recommended instance type based on region, database engine, and a given list of instances. It will pick the first available one from the list or throw an error if none exist.
It uses the AWS SDK function DescribeOrderableDBInstanceOptions to achieve this.
I modeled it a lot off the EC2 get recommended instance type functionality, but it is somewhat simplified since the underlying AWS method used has less options.

Something that DescribeOrderableDBInstanceOptions exposes that I didn't think to add as an option is the DB engine-version. I believe there are cases where the version could make a difference on availability of an instance type, so i'll go ahead and add that. This code should still be reviewable as is, and I can make any feedback changes while I add that parameter.

Done!

Thanks! Kicking off tests now.

Ha! Got a test failure related to the instance type for EC2 instances:
TestTerraformRemoteExecExample 2021-03-11T10:22:13Z logger.go:66: Error: Error launching source instance: Unsupported: The requested configuration is currently not supported. Please check the documentation for supported configurations.
TestTerraformRemoteExecExample 2021-03-11T10:22:13Z logger.go:66: 	status code: 400, request id: 4e020e26-7c45-4ce8-a161-290cd71622d1
TestTerraformRemoteExecExample 2021-03-11T10:22:13Z logger.go:66:
TestTerraformRemoteExecExample 2021-03-11T10:22:13Z logger.go:66:   on main.tf line 26, in resource "aws_instance" "example_public":
TestTerraformRemoteExecExample 2021-03-11T10:22:13Z logger.go:66:   26: resource "aws_instance" "example_public" {
TestTerraformRemoteExecExample 2021-03-11T10:22:13Z logger.go:66:
TestTerraformRemoteExecExample 2021-03-11T10:22:13Z logger.go:66:
TestTerraformRemoteExecExample 2021-03-11T10:22:13Z retry.go:99: Returning due to fatal error: FatalError{Underlying: error while running command: exit status 1;

I think this is exactly the issue you're fixing for RDS here, but we need to use the GetRecommendedInstanceType for EC2 to solve it. Any chance you'd want to update that example/test accordingly?
The other test failure is unrelated; our GCP test account is hitting some quota issues that we're cleaning up separately.

Yup I can update that test

updated!

Thank you!
One note: I think you may have accidentally checked in a .tfvars file in the most recent commit. Could you remove that?

Whoops, removed!

Tests passed. Merging now.

https://github.com/gruntwork-io/terratest/releases/tag/v0.32.11


add support for Kafka <IP_ADDRESS>

WIP
The biggest feature added to <IP_ADDRESS> is time-based offset searching [1]
Will investigate how to incorporate this into the plugin
[1] http://www.confluent.io/blog/announcing-apache-kafka-0-10-1-0/

this backwards compatibility test run shows that we might have to bump the version to 6.0
https://travis-ci.org/logstash-plugins/logstash-input-kafka/builds/172205191

from their docs[1]:
Note: Because new protocols are introduced, it is important to upgrade your Kafka clusters before upgrading your clients (i.e. 0.10.1.x clients only support 0.10.1.x or later brokers while 0.10.1.x brokers also support older clients).

[1] https://kafka.apache.org/documentation#upgrade_10_1_breaking

Thanks @talevy .  I don't see the new consumer setting max_poll_interval_ms  introduced in <IP_ADDRESS> in our master doc yet.  Do we plan on adding it?  Maybe also note in its description that request_timeout_ms must always be larger than max_poll_interval_ms (which is a disclaimer in Kafka documentation)?

thanks @ppf2, the idea was to first enable speaking to <IP_ADDRESS> brokers and then following up with any enhancements like quering offsets by timestamp, and new configs.
will add those that you mention, for sure

ok thx!


Reconfigure WiFi / Pool address / Wallet

As after the first configuration and reboot the web interface stops responding it is useful sometimes to be able to reconfigure the board to connect to another Wifi network, another pool or change the wallet address. It is understandable the web server may use valuable resources that can impact on the hashrate. A few ways I see this can be achieve are:
1 - If simply leaving the web server enabled doesn't use any extra CPU resources when there is no opened connections it can be left with a simple form page that doesn't use CPU resources (like to show updated hashrate or other details) and through the web interface be able to change these details, save and reboot.
2 - If that is not possible, than through the pressing of the flash/boot bottom stop the mining job and start the web server. In order to give feedback to the user blink the ESP light in a certain sequence to confirm the change, and keep blinking in a different way to show that it is not mining and waiting with the web server running.
3 - If the board is taken to another place where the SSID previously configured cannot connect, the ESP notice that after some time, configure itself in AP mode and start the web server for a new configuration.
4 - If none of the above is worth implementing, simply if the flash/boot button is pressed for a few seconds while it is running (not before power on) the ESP resets its configuration and reboot in the default firmware configuration. In the case of ESP8266 Devkit can't the flash/boot button be used for this as well ?

Sadly will involve to have the web server running and will kill the already poor hash rate
On devices with 2 buttons, is enough pressing to For ESP32: Unplug the USB cable, press and hold the BOOT button, and then plug in the USB cable. and this will force the setup again
This should be in place too, if WiFi does not connect it reset the AP and the setup system
Yes, it's what we are doing https://github.com/matteocrippa/leafminer?tab=readme-ov-file#resetting-setup

Hi Mateo
ESP8266-NodeMCU Devkit has 2 buttons where the flash/boot one can may be used too to avoid the need to re-flash.
Great about point 3 then.
For 4 not sure I understood correctly. What is said on the URL is that ESP8266 has a limitation (for when there is only a single button). Where there are 2 is it already something possible or needs implementation ? The idea is to when pressing it for a few seconds while it is running it resets its current configuration to factory and reboots. I need to test, but I understand that if pressing the flash button before power on the device will not boot and will instead go into a state where it awaits a new flash, or am I confused ?

You can see it here https://github.com/matteocrippa/leafminer/blob/2db6981ff3d5af11ae3cb74e1f714f5bf3817917/src/main.cpp#L59
Basically I check if the button is pressed on start and if so I force the Access Point once again.
For now for esp8266 there's no other way to wipe it

Thanks Mateo
Would it perhaps be a option for 8266 when the button is pressed to stop the mining job and bring up the Access Point for reconfiguration ?

I recall the single button on esp8266 it's sadly not scriptable because it's just force the reboot

Hi Mateo
Not sure we are talking the same board, but at least on the NodeMCU one there are 2 buttons, where one is the RST one that does exactlly what you said, but there is another one called Flash that perhaps can be used after boot. See the picture below:

Ah ok, so we can add its GPIO and handle that.
I'm actually using some Weimos D1, and those have just a single RST button

@ffrediani do you know by any chance the GPIO for that button?

Hello @matteocrippa
It is connected to GPIO 0 (or D3)


DX: check file permissions

nice!
can you throw in to check php-cs-fixer in the root has x permission as well?

I think adding another check (if) for the execution flag on that one file is fine, there is not much gain trying to merge it in the current logic think.

please review my changes @kubawerlos

Hold on, we need update CONTRIBUTING.md file.

seems the checkbashisms script is broken itself;
https://travis-ci.org/github/FriendsOfPHP/PHP-CS-Fixer/jobs/734276849#L704
maybe fix;
--- dev-tools/bin/checkbashisms	2020-10-09 14:45:37.499597123 +0200
+++ dev-tools/bin/checkbashisms	2020-10-09 14:45:37.499597123 +0200
@@ -440,7 +440,7 @@
 	    # Finally the whole subexpression may be omitted for scripts
 	    # which do not pass on their parameters (i.e. after re-execing
 	    # they take their parameters (and potentially data) from stdin
-	    .?(\${1:?\+.?)?(\$(\@|\*))?~x) {
+	    .?(\$\{1:?\+.?)?(\$(\@|\*))?~x) {
             $ret = $. - 1;
             last;
         } elsif (/^\s*(\w+)=\$0;/) {
@@ -453,7 +453,7 @@
 	    # As above
 	    .?\$$var.?\s*
 	    (--\s*)?
-	    .?(\${1:?\+.?)?(\$(\@|\*))?.?\s*\&~x) {
+	    .?(\$\{1:?\+.?)?(\$(\@|\*))?.?\s*\&~x) {

 	    $backgrounded = 1;
 	} elsif ($backgrounded and m~

however they are not on github and my perl/regex/shell knowledge may not be enough, so I'll skip it for now

Thank you @kubawerlos.

friendly note @SpacePossum , the dev-tools/bin/checkbashisms is file provided externally, it's not part of our repo

Yeah I know, that is why I didn't change it in the repo. Still looks like a minor issue in script, but as they are not on github I don't know where to send the patch to

done, @SpacePossum : https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/5215 ;)

nice! thanks man : )


Extract a common method for retrying functions in Utils

Proposed changes

extract retry method in Utils, for

retry the function with max times
use LockSupport from scala to prevent manually control of thread sleeping
warn logs during retry
throw the exception in Failure for further processing

Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

LGTM

OK, let me fix the conflicts soon.


Macros stop working in raids

I've been having a major problem during most LFR's and Normal raids during boss fights where my macros will lock up at seemingly random times until I can do a /reloadui
Where can I look to see the error? or fix it. I'm using 2.0.14 release

Is it a particular macro or all macros?  Eg do you have another macro for that class and or a global one and does it work while your main macros fail?  If this is the case it may be faults with the macros themselves.  This is very possible if you are using castsequence lines where you don't have enough resources to cast the next spell in the castsequence.
If this is not the case you will be getting a Lua error and unless you have other mods that suppress this will popup on the screen in the middle of combat.
TimothyLuke

On 24 Feb 2017, at 10:46 pm, jweter<EMAIL_ADDRESS>wrote:
I've been having a major problem during most LFR's and Normal raids during boss fights where my macros will lock up at seemingly random times until I can do a /reloadui
Where can I look to see the error? or fix it. I'm using 2.0.14 release
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Here is the bug report from bugsack
11x GSE\API\StringFunctions.lua:46: bad argument #1 to 'gsub' (string expected, got table)
[C]: in function gsub' GSE\API\StringFunctions.lua:46: in function UnEscapeString'
GSE\API\StringFunctions.lua:34: in function UnEscapeTable' GSE\API\StringFunctions.lua:8: in function UnEscapeSequence'
GSE\API\Events.lua:102: in function ?' ...ibraries\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:145: in function <...ibraries\CallbackHandler-1.0\CallbackHandler-1.0.lua:145> [string "safecall Dispatcher[2]"]:4: in function <[string "safecall Dispatcher[2]"]:4> [C]: ? [string "safecall Dispatcher[2]"]:13: in function ?'
...ibraries\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:90: in function Fire' ElvUI\Libraries\AceEvent-3.0\AceEvent-3.0-3.lua:120: in function <ElvUI\Libraries\AceEvent-3.0\AceEvent-3.0.lua:119> [C]: ? [C]: in function LoadAddOn'
FrameXML\UIParent.lua:407: in function UIParentLoadAddOn' FrameXML\UIParent.lua:482: in function ArtifactFrame_LoadUI'
FrameXML\UIParent.lua:1497: in function <FrameXML\UIParent.lua:907>
[C]: in function SocketInventoryItem' FrameXML\PaperDollFrame.lua:1522: in function PaperDollItemSlotButton_OnModifiedClick'
[string ":OnClick"]:2: in function <[string ":OnClick"]:1>
Locals:
nil

It seems to lock up one macro at a time but, will lock anything and everything up given enough time.
I'm still not sure what causes it, it locks up macro even with no /castsequence in them.

You have a corrupt macro and it's causing your other macros to fail.  The most common causes of this are trying to import a GSE1 macro that is not well written or trying to force a GSE1 macro into the mods code.
The problem and the fix are documented here
https://wowlazymacros.com/forums/topic/one-cause-of-inability-to-open-options-and-table-expected-got-string-errors-gse2/
TimothyLuke

On 27 Feb 2017, at 1:16 am, Steelzombie<EMAIL_ADDRESS>wrote:
It seems to lock up one macro at a time but, will lock anything and everything up given enough time.
I'm still not sure what causes it, it locks up macro even with no /castsequence in them.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Feature idea - add configurable TTL option for journaled messages and snapshots

Thinking we could enable a setting via HOCON for journaled messages and snapshots to set a TTL duration for messages / snapshots. It'd be disabled by default but could be turned on via
akka.persistence.cassandra{
     journal.ttl = 4 d
     snapshot.ttl = 10 d
}

The whole point of Akka.Persistence is to keep a full record of past events, deleting old events would bring you back to an incomplete state.
I do get that this could be useful for e.g. a chat where you want to discard messages older than x time, and when the chatroom reboots, it only holds the x days latest events.
but is that really the responsibility of Akka.Persistence or its providers?
I'm thinking project scope creep. even if I see when it can be used.

There is a special message type DeleteMessagesTo(pid, seqNr, isPermanent), which when send to journal, will cause it to drop messages for a particular persistent actor event stream, up to event with seqence nr provided in message.
In general events should never be dropped, as this could cause persistent actor to recover in corrupted state. The only justified case I see, is that your events from far past are no longer necessary and occupy to much memory. In that caseyou may decide to snapshots actor's state and drop the events that happened before it.

Ok, got it - great points. This is something that should be taken care of inside the actor's code rather than using a database feature to do it.


[red-knot] Improve validation for search paths

Summary
This PR cleans up the settings validation and types in the module resolver. Namely:

Currently we validate that a ModuleResolutionPathBuf has either no extension, a .pyi extension or a .py extension. But for search paths specifically (which are the only module-resolution paths that are ever directly constructed), that's the wrong kind of validation for us to do: we should just validate that the path points to a directory.
For custom typeshed directories, validate that a <typeshed>/stdlib/ directory exists, that a <typeshed>/stdlib/VERSIONS file exists, and that the VERSIONS file parses.

Test Plan
cargo test -p red-knot_module_resolver. I haven't added any new tests specifically as part of this PR, but I'm happy to if you'd find them useful, either as this PR or as a followup.

I think it would ease reviewing if the validation change and the structure change aren't in the same PR. Or is there a specific reason why you put both changes into one PR?

I think it would ease reviewing if the validation change and the structure change aren't in the same PR. Or is there a specific reason why you put both changes into one PR?

I started off only doing the validation changes, but then I realised that really there were different invariants for module-search paths as opposed to module-resolution paths in general, and so improving the validation didn't really make sense while they were still being represented by one type. But I can certainly split it into two PRs.

I've extracted the structure change into its own PR: https://github.com/astral-sh/ruff/pull/12379.

Following the changes made in https://github.com/astral-sh/ruff/commit/2a8f95c437d64fdd9b2d512ac065288d775aabfb, this PR is now solely focussed on improving validation for search-path settings.

I like the validation code but I don't think the "all settings must be valid or we don't use any of the provided settings" provides the best user experience. It means the CLI will fail to start and so will the LSP.

I think this is somewhere where we might want different behaviour depending on whether redknot is being run as a CLI tool or as an LSP server.
As an LSP server, I can see that it makes sense to try to recover as much as possible, as the user may be in the middle of editing their workspace settings -- and even if they're not, it's annoying if redknot completely gives up from linting all your code because of a small typo in your workspace settings.
As a CLI tool, I think the tradeoff is pretty different. Something I've really liked about Ruff in the past is how strictly it validates the settings passed to it. It means that there's no ambiguity, and no chance of Ruff silently doing the wrong thing. This is especially important, in my view, for a tool that applies autofixes to your code -- moreover, it's a tool that many people have installed as a pre-commit hook, which means it'll automatically apply autofixes as part of every commit.

I agree on that assessment. But that still means that the infrastructure has to handle it gracefully for the LSP case. The CLI will want to call some function that tells it if the settings are correct.

I agree there's lots of design work still to be done here regarding error handling and settings resolution. It wasn't really my intent to solve that problem in this PR; I just really wanted to make the validation we were already doing make some kind of sense, and to add some proper error messages for it rather than simply having the module resolver call .unwrap() on an Option value.
@MichaReiser, what's your specific concern with the changes this PR is making? It's already the case on main that we panic in the module resolver as soon as we find a single search path that we consider to be invalid; this PR doesn't change anything in that regard. Should I add some more TODOs around the system calls in path.rs saying that we'll need to revisit them if we end up deciding to do settings resolution inside Salsa?
I can think of lots of possible ideas for solving the bigger questions you're posing here, but I'm not sure any of them are in the scope of this PR.


Passing store from a function  creates a new store.

Hello and thanks for the good work you are all doing.
I'm having a hard time with something and I'm not sure this is expected behaviour. If this is an SO question please let me know and I will close the issue and post there.
I have created a container wrapper that takes the connected component as an argument:
import store from 'somewhere'

const ComponentWrapper = (Container, railsProps, _railsContext) => {
  return (
    <Provider store={store}>
      <Container {...railsProps} />
    </Provider>
  )
};

with store.js defined as such:
const epicMiddleware = createEpicMiddleware(rootEpic, {
    dependencies: {}
  });

  const logger = createLogger({
    collapsed: true,
  });

export default createStore(RootReducer, {}, applyMiddleware(epicMiddleware, logger))

Happy days, as expected only one store is created, each component is connected to that one store. I will end up inserting more than one of these components in to a page and despite each component being wrapped in it's own provider/store, redux knows to only use one store. The behaviour here is exactly what I want and expect (I know multiple stores hurts gaearon's soul - and I understand).
However, if I redefine my store.js:
const epicMiddleware = createEpicMiddleware(rootEpic, {
    dependencies: {}
  });

  const logger = createLogger({
    collapsed: true,
  });

export const configureStore = (railsState) => {
    return createStore(RootReducer, railsState, applyMiddleware(epicMiddleware, logger))
}

export default configureStore

and wrap my component just as above but with the change
<Provider store={configureStore({})}>
      <Container {...railsProps} />
</Provider>

When mounting the components I have that each component has it's own store. I believe it might have something to do with setting of storeKey? However, I believe this is unexpected behaviour since configureStore({}) returns createStore(RootReducer, {}, applyMiddleware(epicMiddleware, logger)) exactly like before.
Why do I believe each component have their own stores? Because if I define my store as initially, and I mount two copies of the same component in to my DOM, each component listens to the same change in state (via dispatching actions) and rerenders accordingly - as expected - these two components have been connected to the same slice of state, the change of which causes the rerender in BOTH components - makes me smile every time. If I define store.js as shown in the latter definition, a change of one component only shows in that component and not in the other meaning that the two components are listening to two different slices of state. Since they are just a copy of the exact same component (technically container since I am using the container/presentation component pattern) they are both in fact connected to different stores.
I hope I have explained this correctly.

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux where there are a lot more people ready to help you out. Thanks!

If in doubt if something is a SO thing or a bug, I think it's always best to go first with SO and depending on the feedback there, it can be brought to the project issue tracker.

@FreddieOD
try this.
store.js:
const epicMiddleware = createEpicMiddleware(rootEpic, {
    dependencies: {}
});

const logger = createLogger({
    collapsed: true,
});

let store;
export const configureStore = (railsState) => {
    return store || (store = createStore(RootReducer, railsState, applyMiddleware(epicMiddleware, logger)));
}

export default configureStore


Mp messaging example

@romain-grecourt Fancy is what I have been aiming for, is 140 kB really too much?

It's trying to be fancy, but it's not. It's an example, keep it simple rather than lame, go to the point.
I really want to avoid duplicating assets from the website all over the place.

I personally like the design with all these animations. It makes it nice and dynamic. I don't see anything wrong with checking it in into repository. I agree it's better to put js files in the repository.
@romain-grecourt Are there any other concerns except that you don't like the design?

It's hard enough to maintain a website and keep things consistent. Let's not copy stuff from the website all over the place.
I don't agree with examples being fancy, they should be simple and illustrate a point. Demos can be fancy, is this a demo ?
At the very least get rid of the website background, it's not meant to be reused.

I think that one of the purposes of having the graphics is that we can use it in Helidon related assets such as are presentations, demos and samples. I don't agree that it must be kept on the web site only. Why the website background cannot be reused?

The re-usable assets are here: https://github.com/oracle/helidon-site/tree/master/graphics.
The website background was specifically designed for the parallax effect, it's not meant to be re-used ; I'm guessing that background.png was built using the individual layers of the parallax.

Sorry for rebase, background image is removed and snippet is generated locally


Use IAM RDS access to connect to DB

The permissions method for db access lets you use IAM authentication. However it seems like if you're using the agent you need to create a password.
It'd be great if we could give the agent IAM permissions to connect.

@danielcompton thank you for your request!
Yes this feature is on our roadmap. Definitely can see it being helpful for users that prefer IAM auth. Out of curiosity is this currently blocking your ability to use the agent?

Thanks, it's not a blocker for us, but would be nice to have.

https://github.com/ottertune/ot-agent/pull/84


First pass at adding Serilog.

Ready for code review.

First, thanks for the PR; the work is much appreciated!
Second, sorry for the delay in my reviewing this; between traveling last week and a dust-up at work, I've been slammed the past bit.  Fortunately I was able to pull together some time last evening to review this more fully and some time this morning to compose a more comprehensive response.
After taking a look @ the implementation, I do have a few questions/comments, some of which may well simply be the result of my lack of familiarity with Serilog (as mentioned, I've not used Serilog in the past and so can't speak from experience re: how it works).
After reading the code (including the initial unit test -- thanks for those, BTW!) and tracing through the test-run in the debugger a few times, I think I'm still a bit confused as to your approach.  It almost seems as if rather than this being an adapter for Common.Logging users to leverage Serilog, its instead more of a way for Serilog users to plug Serilog into Common.Logging.  I'm not sure I'm understanding this properly; can you help me better understand your general intent with this?
Your integration test first news up the Common.Logging adapter and sets its factory as would be expected of an integration test, but then the test code switches to interacting directly with Serilog types (e.g., Serilog.LoggerConfiguration, Serilog.ILogger) to configure and retrieve a logger instance with which to then write log entries.
Common.Logging typically expects the Common.Logging.ILoggerFactoryAdapter implementation to be responsible for reading configuration and retrieving an instance of the logger as a Common.Logging.ILog instance that the user then interacts with to commit log entries.  Instead, your implementation seems to have the user call Serilog directly and then Serilog sends log output to the CommonLoggingSink that then leverages your implementation of the Common.Logging.ILoggerFactoryAdapter to pass Serilog log entries through to any other Common.Logging logger that might be configured.
Can you help me understand whether the usage pattern I see in the test is a convenience for the sake of easily setting up the test case, or is it indicative of how a user would be expected to interact with your implementation more generally?  My rough interpretation of the overall approach you've used here is that it seems to me that it would require a user to code against Serilog directly, and then Serilog would use the CommonLoggingSink to pass events through to some other logger also configured as Common.Logging.
This impression is reinforced to me by the app.config file you've created for the integration test that seems to contain configuration metadata thatSerilog expects rather than metadata that Common.Logging would expect as was used in e.g., this test.  Its also pointed to by your CommonLoggingSink code that checks for and rejects Common.Logging having been configured with your Serilog-specific factory adapter (for the mentioned reason that it would result in endless recursion).
I'd expected the Serilog implementation to align more closely with the approaches used for other Common.Logging adapters where the LogManager.Adapter property would be set to an instance of the SerilogLoggerFactoryAdapter that would then be responsible for the configuration and construction of the logger when the user calls LogManager.GetLogger<T>(...) to return a Common.Logging.ILog instance with which to interact.  Interacting with that Common.Logging.ILog instance would then redirect logging activities to the underlying Serilog instance.
Some of my confusion also comes from my observation that you do seem to use this expected pattern in your other test.  But the way I understand your implementation of the CommonLoggingSink class, attempting to actually log anything using the Common.Logging.ILog instance returned by that call to LogManager.GetLogger<T>(...) would be expected to throw because the configured factory in that test is the SerilogLoggerFactoryAdapter type that your sink disallows in order to avoid infinite recursion.
As mentioned, its entirely possible that I'm just too much of a Serilog noob to properly understand how you've approached this; can you help improve my understanding of the points I've identified above?

The integration test was based on this one for Nlog And based on the behavior of nlog to be able to configure send messages to common.logging. Since Serilog supports that same type of behavior via Sinks, I went ahead and implemented the pattern to do so.
The other test was based on the tests for **ENTLib Maybe those tests were not the best to model my tests after, and they are pretty basic. If you think I need some additional tests here, I can write some.
If you look at my SerilogLoggerFactoryAdapter.cs  It creates a new instance of Serilogger.
And the Serlogger.cs takes that instance and pushes logs to serilogger.
My intented behavior was for it to work like other logging adapters, you use the adapter for serilog in common logging and messages are routed to serilog.

Ah, interesting ... so these two tests actually represent two different use-cases/usage patterns for Serilog support: one that relies upon the behavior in the CommonLoggingSink and another that's designed to work more "traditionally".  I'd not considered that; now I get it :)
I'll take another look again this evening and provide some more detailed feedback in light of this explanation; thanks again for the initial PR!

Thanks for the contribution; I've merged the PR into MASTER.  I have a few tweaks I need to make to your implementation, but nothing major -- primarily I want to move the Serilog-specific changes you introduced in AbstractLogger back into your SerilogLogger subclass, but otherwise this looks like a really solid contribution -- thanks again for both the work and your patience as I took a bit longer to review this than I'd originally hoped.


Enable IDE0044: MakeFieldReadonly

Enable IDE0044: MakeFieldReadonly as warning.

Add suppression for ComInterop via GlobalSuppressions.cs
Convert a few static readonly fields to const.

@xtqqczze Please rebase.

@iSazonov We can reuse this PR for src\Microsoft.Management.Automation changes?

The PR is still huge.

CIs still fail. Maybe split the PR?

Also, I happily went and added all my readonly tags to a [Serializable] class only to discover (of course) that a binary deserialize will fail in this instance due to the readonly property. But NO warning of this until the runtime error.

Originally posted by @vsfeedback in https://github.com/dotnet/roslyn/issues/27212#issue-327077528
@iSazonov Can you confirm that using the readonly-modifier in our case will not adversely affect types marked with SerializableAttribute?

@iSazonov Can you confirm that using the readonly-modifier in our case will not adversely affect types marked with SerializableAttribute?

Can you point a type you say about?

@iSazonov Can you confirm that using the readonly-modifier in our case will not adversely affect types marked with SerializableAttribute?

Can you point a type you say about?

@iSazonov In #13966 we made the field _originInfo readonly in the serializable class RemotingErrorRecord: https://github.com/xtqqczze/PowerShell/blob/94c15f6000e9d189c485f4e3d946cfd00372a317/src/System.Management.Automation/engine/remoting/client/RemotingErrorRecord.cs#L28

In #13966 we made the field _originInfo readonly in the serializable class RemotingErrorRecord

This was my concern too but the field is assigned only in protected constructor at deserialization time.
Also serialization commonly works only for public members and settable properties.

In #13966 we made the field _originInfo readonly in the serializable class RemotingErrorRecord

This was my concern too but the field is assigned only in protected constructor at deserialization time.
Also serialization commonly works only for public members and settable properties.
Do you see other samples of the pattern we need to review carefully?

I do not have any more examples, but I worry this may have been missed in review for PRs already merged.

I worry this may have been missed in review for PRs already merged.

I checked this in reviews but I was wrong about private fields
https://docs.microsoft.com/en-us/dotnet/api/system.serializableattribute?view=net-5.0:

When you apply the SerializableAttribute attribute to a type, all private and public fields are serialized by default.

So we need re-review this. I found follow examples (maybe you can find others):
ErrorPackage.cs, ExtendedTypeSystemException.cs, MshSecurityException.cs, PseudoParameters.cs,TypeTable.cs,LocalConnection.cs PSDataCollection.cs, Job2.cs, RemotingErrorRecord.cs, FormatTable.cs, HelpCategoryInvalidException.cs, HelpNotFoundException.cs, CommandDiscoveryExceptions.cs, CryptoUtils.cs, MetadataExceptions.cs, MshArgumentException.cs, MshArgumentNullException.cs, MshArgumentOutOfRangeException.cs, MshInvalidOperationException.cs, MshNotImplementedException.cs, MshNotSupportedException.cs, MshObjectDisposedException.cs, ParameterBinderExceptions.cs, ParserException.cs, SessionStateExceptions.cs

@xtqqczze Could you please revert changes I mentioned in previous comment in follow PR?

@xtqqczze Could you please revert changes I mentioned in previous comment in follow PR?

@iSazonov I am not so sure the changes are not a problem - they did not cause test failures after all. I'm been thinking that deserializers are usually implemented using reflection, so they can write to readonly fields.
Do you specific concerns with the SerializableAttribute and readonly fields?

Do you have specific concerns with the SerializableAttribute and readonly fields?

I am not sure it works.
And the remote code is probably not covered by tests.

@PaulHigin Could you please help?

Do we still need SerializableAttribute if we don't use BinarySerializer or we can remove them?
Can we make fields readonly or we can break XML serializer?

@PaulHigin Could you please help?

Do we still need SerializableAttribute if we don't use BinarySerializer or we can remove them?
Can we make fields readonly or we can break XML serializer?

@PaulHigin Could you please clarify?

@iSazonov  What part in the code are you referring to?  Can you provide a link?

@iSazonov What part in the code are you referring to? Can you provide a link?

https://github.com/xtqqczze/PowerShell/blob/94c15f6000e9d189c485f4e3d946cfd00372a317/src/System.Management.Automation/engine/remoting/client/RemotingErrorRecord.cs#L28
Should we remove SerializableAttribute-s in such cases if we don't use BinaryFormatter?
Can we make such fields readonly or we can break XML serializer?

@iSazonov Please see https://github.com/PowerShell/PSReadLine/pull/1923#issuecomment-733533803

@iSazonov ComInterop is frozen, but the code is not structured in separate project from System.Management.Automation, so we cannot currently disable analyzers for only ComInterop :(
D:\a\1\s\src\System.Management.Automation\engine\ComInterop\ExcepInfo.cs(18,23): error IDE0044: Make field readonly [D:\a\1\s\src\System.Management.Automation\System.Management.Automation.csproj]
D:\a\1\s\src\System.Management.Automation\engine\ComInterop\ExcepInfo.cs(19,23): error IDE0044: Make field readonly [D:\a\1\s\src\System.Management.Automation\System.Management.Automation.csproj]
D:\a\1\s\src\System.Management.Automation\engine\ComInterop\ExcepInfo.cs(23,21): error IDE0044: Make field readonly [D:\a\1\s\src\System.Management.Automation\System.Management.Automation.csproj]
D:\a\1\s\src\System.Management.Automation\engine\ComInterop\ExcepInfo.cs(24,24): error IDE0044: Make field readonly [D:\a\1\s\src\System.Management.Automation\System.Management.Automation.csproj]
D:\a\1\s\src\System.Management.Automation\engine\ComInterop\ExcepInfo.cs(25,24): error IDE0044: Make field readonly [D:\a\1\s\src\System.Management.Automation\System.Management.Automation.csproj]
D:\a\1\s\src\System.Management.Automation\engine\ComInterop\ExcepInfo.cs(26,21): error IDE0044: Make field readonly [D:\a\1\s\src\System.Management.Automation\System.Management.Automation.csproj]
D:\a\1\s\src\System.Management.Automation\engine\ComInterop\ComInvokeBinder.cs(26,37): error IDE0044: Make field readonly [D:\a\1\s\src\System.Management.Automation\System.Management.Automation.csproj]

@xtqqczze Please look the code in .Net Runtime repository. Perhaps they already fixed the issues.

/home/vsts/work/1/s/src/System.Management.Automation/engine/interpreter/InstructionList.cs(99,49): error CS0649: Field 'InstructionList._debugCookies' is never assigned to, and will always have its default value null [/home/vsts/work/1/s/src/System.Management.Automation/System.Management.Automation.csproj]

@xtqqczze Please look the code in .Net Runtime repository. Perhaps they already fixed the issues. If no we could suppress the warnings on file level:
[ExcepInfo.cs]
dotnet_diagnostic.IDE0044.severity = none

(For generated code https://docs.microsoft.com/en-us/dotnet/fundamentals/code-analysis/configuration-options#exclude-generated-code)

Doesn't this work?

@xtqqczze Please look the code in .Net Runtime repository. Perhaps they already fixed the issues. If no we could suppress the warnings on file level:
[ExcepInfo.cs]
dotnet_diagnostic.IDE0044.severity = none

(For generated code https://docs.microsoft.com/en-us/dotnet/fundamentals/code-analysis/configuration-options#exclude-generated-code)

Doesn't this work?

@iSazonov Unless I specify the absolute path, I see warning InvalidGlobalSectionName, so probably this approach doesn't work in a GlobalConfig file. In any case, suppression in a GlobalSuppressions.cs file works for this PR. Ideally, the ComInterop code would be split to separate project and we set RunAnalyzers to false in the csproj. We could open an issue to discuss the best approach.

Depends on #15704.

@iSazonov Unless I specify the absolute path, I see warning InvalidGlobalSectionName, so probably this approach doesn't work in a GlobalConfig file. In any case, suppression in a GlobalSuppressions.cs file works for this PR. Ideally, the ComInterop code would be split to separate project and we set RunAnalyzers to false in the csproj. We could open an issue to discuss the best approach.

absolute path? What about relative?
I don't like the assembly level suppression and I'd consider it as only last resort.
I believe we don't want ComInterop in separate project because we don't want new additional dll.

@iSazonov Unless I specify the absolute path, I see warning InvalidGlobalSectionName, so probably this approach doesn't work in a GlobalConfig file. In any case, suppression in a GlobalSuppressions.cs file works for this PR. Ideally, the ComInterop code would be split to separate project and we set RunAnalyzers to false in the csproj. We could open an issue to discuss the best approach.

absolute path? What about relative?
I don't like the assembly level suppression and I'd consider it as only last resort.

It seems that section headers for global AnalyzerConfig files must specify an absolute file path. A relative file path produces a compiler warning and is ignored.


ImportError: cannot import name inference (not duplicate)

I checked the older issue https://github.com/tensorflow/nmt/issues/39 that seemed similar to this error, but as cloned, I don't have a gnmt-master to move up into as suggested.
When I cloned into Intellij, I ended up with the path ~\IdeaProjects\nmt\nmt\nmt.py as the entry point.
Screenshot of issue, project structure, and run configuration: http://imgur.com/RVNDhf0

You can execute the following command to test your model:
python -m nmt.nmt \
     		--src=vi --tgt=en \
     		--vocab_prefix=./nmt/nmt_data/vocab  \
     		--out_dir=./nmt//nmt_attention_model \
     		--model_dir=./nmt//nmt_model \
     		--inference_input_file=./nmt//my_infer_file.vi \
    		--inference_output_file=./nmt//nmt_attention_model/output_infer

I use this command to test my model successfully. This command can also be found in the NMT tutorial, but it will be some different.  Maybe you can try both of them. Hope that can help you!

@fansiawang I'm currently running with ~\IdeaProjects\nmt\ as my project directory, so I'm not sure what you mean by moving up one directory to the first "nmt". Can you clarify?

I'd like to bump this @fansiawang. Still having the same issue.

I try a lot to fix these issues but nothing work what should I do?

Let's say
root
|_CONTRIBUTING.md
|_README.MD
|_nmt
  |_nmt.py
  |_...

Then, move up to the root and then run:
py -m nmt.nmt


[Gally]: master <- dev

Automatically created by Git-Ally

:tada: This PR is included in version 2.4.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Solver does poorly with sqrt() in cost function

#include <gtest/gtest.h>
#include <sleipnir/optimization/OptimizationProblem.hpp>

#include "CmdlineArguments.hpp"

TEST(EdgeCaseTest, NarrowFeasibleRegion) {
  sleipnir::OptimizationProblem problem;

  auto x = problem.DecisionVariable();
  x.SetValue(20.0);

  auto y = problem.DecisionVariable();
  y.SetValue(50.0);

  problem.Minimize(sleipnir::sqrt(x * x + y * y));

  problem.SubjectTo(y == -x + 5.0);

  auto status =
      problem.Solve({.diagnostics = CmdlineArgPresent(kEnableDiagnostics)});

  EXPECT_EQ(sleipnir::ExpressionType::kNonlinear, status.costFunctionType);
  EXPECT_EQ(sleipnir::ExpressionType::kLinear, status.equalityConstraintType);
  EXPECT_EQ(sleipnir::ExpressionType::kNone, status.inequalityConstraintType);
  EXPECT_EQ(sleipnir::SolverExitCondition::kSuccess, status.exitCondition);

  EXPECT_NEAR(2.5, x.Value(), 1e-2);
  EXPECT_NEAR(2.5, y.Value(), 1e-2);
}

This diverges and gives a bad search direction exit condition. Making the cost function just x * x + y * y converges to the correct answer.
I'm not sure how to deal with this besides implementing some kind of "feasible-only mode" that shrinks steps if they'll cause domain errors or ill-conditioning.

Adding the following constraints works around the issue, but we should ideally still handle domain errors more gracefully.
  problem.SubjectTo(x >= 1e-2);
  problem.SubjectTo(y >= 1e-2);


Make govuk-prototype-kit install command work with npm

We want users to be able to run
npx govuk-prototype-kit install

and have it do the thing they expect; i.e install the kit and create the project for them.
To get this to work I had to make a few changes; see the commits for details.

Closing in favour of #1621


Add GeneralRobustRegressionLoss

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (83c9b72) to head (2e51816).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #43   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           25        26    +1
  Lines          365       386   +21
  Branches        27        28    +1
=========================================
+ Hits           365       386   +21

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Revert "Revert "Revert "Prepare for making node admin components optional"""

Reverts vespa-engine/vespa#4506

:+1

👍


How to generate a keypair correctly?

Hi,
how to generate a keypair correctly?
Take test seed here: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0005.md
seed: "e0eec84fe165cd427cb7bc9b6cfdef0555aa1cb6f9043ff1fe986c3c8ddd22e3"
correct result: m/44'/148'/0' GDRXE2BQUC3AZNPVFSCEZ76NJ3WWL25FYFK6RGZGIEKWE4SOOHSUJUJ6 SBGWSG6BTNCKCOB3DIFBGCVMUPQFYPA2G4O34RMTB343OYPXU5DJDVMN
How to properly turn seed into a correct result (keypair)? Trying:
import (
    "github.com/stellar/go/keypair"
)
var seeds [32]byte
copy(seeds[:], []byte("e0eec84fe165cd427cb7bc9b6cfdef0555aa1cb6f9043ff1fe986c3c8ddd22e3"))
pair, err := keypair.FromRawSeed(seeds)
xlmAddr := pair.Address()
xlmPK := pair.Seed()
fmt.Println(xlmAddr)
fmt.Println(xlmPK)

Result is different...

Hi!
The seed in your example is a hex string, so you need to decode it with the encoding/hex package's DecodeString function.
Once you have the SEP-5 seed decoded into a byte[], you can derive a key from the SEP-5 seed using the github.com/stellar/go/exp/crypto/derivation package.
Checkout the example here:
https://github.com/stellar/go/blob/horizonclient-v6.0.0/exp/crypto/derivation/main_test.go#L13

Changed to this:
xlmSeed, _ := hex.DecodeString("e0eec84fe165cd427cb7bc9b6cfdef0555aa1cb6f9043ff1fe986c3c8ddd22e3")
xlmKey, err := xlmDrv.DeriveForPath(xlmDrv.StellarPrimaryAccountPath, xlmSeed)
pair, err := keypair.FromRawSeed(xlmKey.RawSeed())
fmt.Println(pair.Seed())
fmt.Println(pair.Address())

Still the wrong result.
But this seed example - "000102030405060708090a0b0c0d0e0f"
gets correct result:
SB6VZS57IY25334Y6F6SPGFUNESWS7D2OSJHKDPIZ354BK3FN5GBTS6V
GCWSJRG6YZSA374IY7LF53PIGTO6JD6BP5CNMUAVNWL3YYE636F3APML
https://github.com/stellar/go/blob/horizonclient-v6.0.0/exp/crypto/derivation/main_test.go#L27

Hi @urbanurba, You should use BIP39 Seed in SEP-05, not m/44'/148' key. If you want to reproduce test 1 in SEP-10, please use the following code.
package main

import (
	"encoding/hex"
	"fmt"
	"github.com/stellar/go/exp/crypto/derivation"
	"github.com/stellar/go/keypair"
)

func main() {
	// I ignored all errors.
	bip39Seed, _ := hex.DecodeString("e4a5a632e70943ae7f07659df1332160937fad82587216a4c64315a0fb39497ee4a01f76ddab4cba68147977f3a147b6ad584c41808e8238a07f6cc4b582f186")
	for i := 0; i < 10; i++ {
		path := fmt.Sprintf(derivation.StellarAccountPathFormat, i)
		keyPair, _ := derivation.DeriveForPath(path, bip39Seed)
		pair, _ := keypair.FromRawSeed(keyPair.RawSeed())
		fmt.Printf("%s %s %s\n", path, pair.Address(), pair.Seed())
	}
}

Actually m/44'/148' key is the intermediate value generated during the calculation, if you are interested in it, add a breakpoint here and explore k.Key.
Hope this information is helpful to you.

@overcat, this is what I was looking for,
thank you very much!

Closing, please reopen if needed.


tun module required be zerotier

We should consider moving this fixup to the ZeroTier package if it's a dependency of that package. It should still be available as an option in thingino-kopt, but it shouldn't be dependent on ZeroTier. For example, a user might need TUN support without needing ZeroTier

yes, fixup for a package should be in the package itself.

@wltechblog please check if this change [363a0b90cd97a0f1329b8ff2e44959234419ceeb] works for you.

implemented directly in zerotier package.


Expand testing level to incorporate draining.

Utilize either ProBuilder or Blender to expand on the current testing level.
Level should now have a hole to sink the ball and count the score utilizing booleans.
Utilize unity colliders as a trigger to know when the ball is sunk.
Resources for ProBuilder boolean<EMAIL_ADDRESS>

I have a hole collider trigger that will allow for the player to go to the next hole

Please connect this issue to a branch


Stop working after somes tests

Hi, it's an interesting project but it's not working anymore after trying fews things, now i only get this message when i acces to it.

Symfony\Component\ErrorHandler\Error\FatalError
Cannot declare class App\Policies\User because the name is already in use``

Thanks.

Hi @kontas, thanks!
The problem you're having seems to be related to something else though; did you create App\Policies\User with it? There seems to be a duplicate classname in that namespace.

Hi @mtolhuys,
I don't remember me creating a policy with or without schematics, but, in did, i have this App\user.php policy :
`namespace App\Policies;
use App\User;
use Illuminate\Auth\Access\HandlesAuthorization;
class User
{
use HandlesAuthorization;
/**
 * Create a new policy instance.
 *
 * @return void
 */
public function __construct()
{
    //
}

}`
I Juste rename the class, and it's working again.
Did you think i make a mistake with your tools ?
Thanks for your help.

No problem @kontas.
It seems like you created a model or other User class under the App\Policies namespace. This could've been done through the package if you changed the config/schematics.php file to use that namespace. By default it uses the Laravel standard: namespace App though. So it won't happen 'out-of-the-box'. It looks like this:
    'model' => [
        'namespace' => 'App\\', <---- Namespace for model creation
        'path' => app_path(), <---- Path for model creation
        'paths' => [
            app_path(), <---- Path(s) for model scanning
        ],
    ],


onTransitionStart event

I think it would be great if there is an onTransitionEnd event so that I can manipulate the blocks when a transition occur. Thanks, Great work by the way :)

+1

+1

Hello friends, I make "onTransitionEnd" for my work(http://www.bectero.com/concerts-events/backend/).


[Task]: Support NFT Output

Task description
TBD
Requirements
TBD
Acceptance criteria
TBD
Creation checklist

[ ] I have assigned this task to the correct people
[ ] I have added the most appropriate labels
[ ] I have linked the correct milestone and/or project

Closed by https://github.com/iotaledger/explorer/pull/959


Support for latest FP PRO ^3.11

Latest fingerprint pro is ^3.11
lock file states pro-spa depends on ^3.9
Please update it to reflect the newest updates.
It would be nice if "latest" release would always be in sync with the "latest" fp-pro.
Or configurable.
yarn.lock
"<EMAIL_ADDRESS>  version "1.3.1"
  resolved<EMAIL_ADDRESS>  integrity sha512-1k+85IYh1bBDJY/syHzBmTzKKaPGQkpq8GO9+vf7MHdqlmIiLAcutaHMUXey9DxylKm93qCHRY/1fCOOQ/LiTA==
  dependencies:
    "@fingerprintjs/fingerprintjs-pro" "^3.9.2"
    tslib "^2.6.2"

"<EMAIL_ADDRESS>  version "3.9.2"
  resolved<EMAIL_ADDRESS>
Workaround for me now is to overwrite fp-pro in package.json, but that is not stable ofc.
  "dependencies": {
    "@fingerprintjs/fingerprintjs-pro-spa": "1.3.1",
    "@fingerprintjs/fingerprintjs-pro": "3.11.0"
  },
  "resolutions": {
    "@fingerprintjs/fingerprintjs-pro": "3.11.0"
  }

which gives me a yarn.lock file of
"<EMAIL_ADDRESS>  version "1.3.1"
  resolved<EMAIL_ADDRESS>  integrity sha512-1k+85IYh1bBDJY/syHzBmTzKKaPGQkpq8GO9+vf7MHdqlmIiLAcutaHMUXey9DxylKm93qCHRY/1fCOOQ/LiTA==
  dependencies:
    "@fingerprintjs/fingerprintjs-pro" "^3.9.2"
    tslib "^2.6.2"

"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>  version "3.11.0"
  resolved<EMAIL_ADDRESS>  integrity sha512-93GjPzKPXoTj03Hvu9DA+P+py6ixQOXkOMLAzvIA7aY2uKoJQFgyCiL1ZFJvTsdml0gxy42rfkxf2z+AeRRo0w==
  dependencies:
    tslib "^2.4.1"

Hey @Harm-Nullix!
Thank you for the issue, we will introduce new version of the fingerprintjs-pro-spa soon with updated dependency.
But it shouldn't block you, we declared dependency version as "^3.9.2" it means that v3.11.0 is still a valid dependency.
To update it you can just call npm update @fingerprintjs/fingerprintjs-pro-spa or a similar command in your package manager, it will change lock file and update dependency.

Released in v1.3.2


Fix the redis-slave issue in guestbook-go

See https://github.com/kubernetes/examples/issues/447

/easycla


documentation page for IDE0300 code-style rule is missing

Type of issue
Missing information
Description
The new IDE0300 rule has no documentation page - the URL opened by VS when clicking the rule is a 404: https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/style-rules/ide0300.
Page URL
https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/style-rules/
Content source URL
https://github.com/dotnet/docs/blob/main/docs/fundamentals/code-analysis/style-rules/index.md
Document Version Independent Id
6d91b560-c12f-6e6d-e92b-1babb27edb67
Article author
gewarren
Metadata

ID: b0a396c1-9c21-75a9-70b5-799cafc941b5
Product: dotnet-fundamentals

PR that introduced the analyzer is here: https://github.com/dotnet/roslyn/pull/69118


Portal : Issues regarding subscriber dashboard

Describe the bug
1.Icons are not clickable but still has hand cursor
2.Title is repeated in description
3.In note sentence, It should in "developer" instead of "developers"
4.Out of 4 dashboards, only one sentence as full stop
Pre- Requisites
Login to https://dev.raaghu.io/
Steps to reproduce the behavior:
Go to Dashboard section of landing page of portal
Verify the cursor for icons in dashboard
Scroll down and check the description of each section
Actual behavior
1.Icons are not clickable but still has hand cursor
2.Title is repeated in description
3.In note sentence, It should in "developer" instead of "developers"
4.Out of 4 dashboards, only one sentence as full stop
Expected behavior
1.Icons are not clickable so it should not have hand cursor
2.Repeated  Title in description should be removed
3.In note sentence, It should in "developer" instead of "developers"
4.Full stop is not required for these sentence
Screenshots

Desktop (please complete the following information):
OS: Windows
Browser chrome
Version [e.g. 22]
Smartphone (please complete the following information): : NA
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [125]
Additional context
NA
@kaushikgokhale

Completed -


Evaluation number dTokens in Loans

Show the current numbers of dTokens with loans in the background (later for dUSD the number of circulating dTokens to that ones in loans could be different)

dTokens hold by vaults in liquidation must be added as a second line. To acquire the data the script must be adapted.

Adaption of graph will be handled later in a separate issue #179


travis: update go versions

Signed-off-by: zhouhao<EMAIL_ADDRESS>

@coolljt0725 @xiekeyang PTAL

LGTM

LGTM


Copy (c) does not work on Linux

Hitting the keyboard shortcut 'c' does not copy anything to the clipboard on Linux (Debian Stretch).
Fantastic app otherwise, thanks so much!

Got it! Your copy-paste node plugin requires the installation of xclip on Linux. After installing xclip, the app copies the song title perfectly! Cheers! Maybe a good idea to add this to the readme perhaps?

Good catch, thanks! I added a note to the installation instructions in the readme. (3a7b07efaec5f9268fc50627d8ecc136f59366b7)
Glad you like the app. :)


Row.key casting bug

In the Row class instead of:
def key
<EMAIL_ADDRESS><EMAIL_ADDRESS>end

it should be:
def key
<EMAIL_ADDRESS>@schema.values['KEY'])
end

Unless I'm mis-understanding the purpose of the method.

The purpose is to return the casted key for the rows you are reading (you might not have selected it but it's still there). Your change assumes that the key alias is called 'KEY' when in fact it could be anything.

As a further point of clarification, that method is actually going to be removed per https://issues.apache.org/jira/browse/CASSANDRA-3513. If you want the key, select it.


fix filter bug with new dates

There was an issue with the new date filters not working, fixed it and also made them function more in a similar way to the other filters.

Thanks for the bug fix!


use the middlewares defined on the config file

(optional) Issue number:
Summary of the change:

I am sorry that we cannot accept this PR. If users don't want to use package routes, then they might complex settings in their routes.
It also make more sense to set middleware in their on laravel routes than in config/lfm.php.
The line \UniSharp\LaravelFilemanager\Lfm::routes(); was meant to provide convenient routes customization for this case.


[Snyk] Security upgrade org.springframework.boot:spring-boot-starter-web from 2.7.18 to 3.2.10

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.
Snyk changed the following file(s):

pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue
Score
Upgrade

Path Traversal SNYK-JAVA-ORGSPRINGFRAMEWORK-7945490
  635
org.springframework.boot:spring-boot-starter-web:  2.7.18 -> 3.2.10 Major version upgrade No Path Found No Known Exploit

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Path Traversal

We don't upgrade major versions of spring-boot


Suggestions for crafting

First of all, I would like to say: THIS UPDATE IS AMAZING.
All of the major problems I was having in v0.9.1 are gone, and we finally have D-Pad crafting! And to think this update came out literally 2 days after my complaint. I tested out Survival and Creative last night and it works so well on controller. Now I am generally satisfied with this supportive mod and would recommend it to anyone.
Minor Bugs:

When the Virtual Mouse is disabled, the player cannot use the D-Pad for crafting nor navigating menus.
When the Virtual Mouse is disabled and the player is moving the mouse while in the crafting menu, the "Close Inventory" icon flickers.
The Vibration feature doesn't seem to work, despite it working in the previous version of Controllable
For option menus that use a vertical scroll bar, sometimes when attempting to use the mouse, the bar is stuck to the bottom in some cases.

Suggestions to Improve the Crafting (If feasible):

Map the B button to close the crafting menu, and Y as quick move.
Allow the player to instantly craft the item by clicking it in the Recipe Book, similar to Bedrock Edition.
Allow the player to quickly move between the Book/Inventory interfaces with LB/RB. (Bedrock Edition does this with a L-Stick press.)

Keep up the fantastic work, and take all the time you need.

When the Virtual Mouse is disabled, the player cannot use the D-Pad for crafting nor navigating menus.
Fixed in https://github.com/MrCrayfish/Controllable/commit/0f5ef1c3244cff454a862868bc65f4b903bb5860
When the Virtual Mouse is disabled and the player is moving the mouse while in the crafting menu, the "Close Inventory" icon flickers.
Fixed in https://github.com/MrCrayfish/Controllable/commit/2ee0124a38b9a5d758071b19ba70b25b2eb06b1a
The Vibration feature doesn't seem to work, despite it working in the previous version of Controllable
The mod has switched to GLFW which doesn't support rumble. However this should be changing soon. (https://github.com/glfw/glfw/pull/1678 and original issue https://github.com/glfw/glfw/pull/1678)
For option menus that use a vertical scroll bar, sometimes when attempting to use the mouse, the bar is stuck to the bottom in some cases.
Fixed in https://github.com/MrCrayfish/Controllable/commit/b649d5c97d5af594589049f0af9d7d2293c78a15

glfw/glfw#1678 was added in April, so I doubt it will be merged anytime soon. Can you ship your own fork of glfw?

I've added support to craft items directly from the recipe book https://github.com/MrCrayfish/Controllable/commit/f29bfceb0ae9691b2715d5abca04af7ce6d94552

"Map the B button to close the crafting menu, and Y as quick move."
A separate binding has been added in modern version of Controllable to close the inventory.


implement a self-override of AuthenticationStateProvider bug in server-side-blazor

First I'm sorry about my written English
I've had a recurring problem and I hope you can help me
I am trying to implement a self-override solution for uthenticationStateProvider without EF.
I used two project examples as a base, both written in CSB.
I went through them step by step and implemented them as a SSB project
the first is chris sainty ex:
Link: https://chrissainty.com/securing-your-blazor-apps-authentication-with-clientside-blazor-using-webapi-aspnet-core-identity/
the second is Steve Sanderson "MissionControl" demo:
Link: https://github.com/SteveSandersonMS/presentation-2019-06-NDCOslo/tree/master/demos/MissionControl
Both of them I managed to implement and run in the SSB environment with minor changes depending on the environment
Describe the bug
In Both of them The AuthenticationState does not change when user signin, the same code in CSB mode does change the AuthenticationState.
JWT is created and saved inlocal storage but the AuthenticationState does not change accordingly and I still remain in unauthorized state

Hi. It looks like this is a question about how to use ASP.NET Core. While we do our best to look through all the issues filed here, to get a faster response we suggest posting your questions to StackOverflow using the asp.net-core-mvc tag.

@mkArtakMSFT, blazor tag, not asp.net-core-mvc tag.

As suggested by @mkArtakMSFT, you'd better post your questions in  StackOverflow using the blazor tag, accompanied by a repo of your apps, so we can detect the issues you're facing.
However, it is a bad idea to use Jwt with server-side Blazor. Why validate the user on the server, a very secure environment, and then send a Jwt token to be stored on the user's localStorage. Do you see the absurd ? Still worse, this may introduce security vulnerabilities and risks that you wouldn't want to undergo.
The following is what SteveAnderson has to say about implementing a custom AuthenticationStateProvider in server-side Blazor, which I guess, you did:
For server-side Blazor, it is very unlikely that you should implement a custom AuthenticationStateProvider. The built-in implementation already integrates with ASP.NET Core's built-in authentication mechanisms. If you implement a custom one, you may introduce security vulnerabilities.
The only common scenario for a custom AuthenticationStateProvider is client-side Blazor, because in that case you may want to integrate with any number of external authentication systems independently of your server-side code. Also, in client-side Blazor, authentication only exists to present a convenient UI to well-behaved users - it's not actually the place where security is enforced, since client-side rules can always be bypassed.
Without seeing your code I can't say much except to mention these:

Known issue: In ASP.NET Core 3.0 Preview 6, it's not possible to specify custom NotAuthorizedContent or AuthorizingContent on the Router component with server-side Blazor (though it does work with client-side Blazor). This will be fixed in the Preview 7 release

As far as I remember (not completely sure), the AuthenticationStateProvider in server-side Blazor remains unchanged during the lifetime of the connection, which implies that the AuthenticationState won't change. But again, only seeing your code can enable better answers.

enetstudio Thanks for the answer
I still experience the technology and want to check things out.
In a real environment, I do not intend to validate using JWT
The fact that I can implemente auth only through EF its limit me in terms of my organization and work environment.
I will have to find a solution  that will work with MYSQL and there is currently no such one for .core 3.0
Thanks in advance

"In a real environment, I do not intend to validate using JWT"
"The fact that I can implemente auth only through EF"
I guess you mean implementing authentication on server-side Blazor, right ? You can use Windows Authentication as well.
Incidentally, you do not implement authentication via EF, which is an ORM framework. You probably meant the Identity system...

"Incidentally, you do not implement authentication via EF, which is an ORM framework. You probably meant the Identity system..."
yep....


mp3tag: Fix pre_(un)install script

mp3tag has a problem where the program will not uninstall if the context menu is installed. This edit should fix that issue.

[x] I have read the Contributing Guide.

/verify

@HUMORCE could you please approve this PR when you have the time?

EDIT: It also has this issue where the tag panel is completely blank, this PR will also address that issue.

/verify

Proof:

EDIT: It also has this issue where the tag panel is completely blank, this PR will also address that issue.

Additionally, Why do you remove the pre_uninstall section? It was there was there to remove the context menu option if the user activated it.

This is not going to work, a blank usrfields.ini file will cause the fields in the Tag Panel in mp3tag to become completely blank.

I dont use this app so I dont know about this, but data\usrfields.ini was created as a dir, before.

Additionally, why did you remove the pre_uninstall section? It was there to remove the context menu option if the user activated it.

the context menu cannot be uninstalled when we do not kill explorer, is it?
"##": "An external script is needs to (un)install the context menu.",

No I have tested it. In the previous commit, I have found a way to remove the context menu without having to restart explorer.exe. You can try it out for yourself, in my bucket.
scoop bucket add MyScoop 'https://github.com/Zliced13/MyScoop'

scoop install mp3tag_fixed

Make sure to run the commands to add mp3tag as a context menu option, then run the scoop uninstall command. It should uninstall the context menu in the uninstallation process.

ok, why use script to copying/moving export\* instead of persist here?

Because the export folder is part of the mp3tag archive. If I were to persist the whole folder, it would end up creating endless copies of export.orginal folders in the scoop/apps/mp3tag/current folder, which no one probably wants.


Stable Diffusion

What operating system are you using?
windows
What browser are you using?
Edge
Describe the bug
Stable Diffusion  应该怎么配置？
还有对应的一些环境变量，应该怎么配置呢？
What provider are you using?
Others (Specify in description)
What prompt did you enter?
No response
Console Logs
No response
Participation

[ ] I am willing to submit a pull request for this issue.

We use Replicate to support Stable Diffusion.
You can create a new account on Replicate, copy the token from https://replicate.com/account/api-tokens , and set it in anse.


Fix musl

unrecognized relocation (0x2b) in section `.text.malloc_conf_init'

this was a problem with how upstream binaries were built. It should fix itself by next stable release.
Regardless I think it is helpful to install the musl-packages that this PR proposes.

Thank you @polachok!
The other errors are due to rust-lang/rust#36793 and should be fixed by next nightly. This fix will probably be backported to the beta so it should also be fixed there soon-ish.


Add yaml output

Fixes #37
todo

[ ] add test
[ ] build_module_as_str seems unused and untested, same with the new build_module_as_yaml_str.
[x] local imports for pyyaml dep, not at top
[x] use file-name to guess output (default json)
[x] add --yaml flag
[x] --platform-info should respect --yaml flag

help wanted

[x] poetry extra dep (I'm not a poetry user, not sure about this
[x] left a TODO

Are you using pre-commit?

Are you using pre-commit

No I have never learned that, was always worried it would mess up by other projects.  I do manually run black before committing, but I understand maybe there are other standards at play here...

pre-commit mucked around in poetry.lock with lots of unrelated changes.  I'll not commit those.
pylama gaves lots of strange-looking errors so I uninstalled that.
poetry-check.............................................................Passed
poetry-lock..............................................................Passed
Sync with Poetry.........................................................Passed
isort (python)...........................................................Passed
black....................................................................Passed
prettier.................................................................Passed
rstcheck.................................................................Passed
pylama...................................................................Failed
- hook id: pylama
- exit code: 1

Executable `pylama` not found

bandit...................................................................Failed
- hook id: bandit
- exit code: 1

[node_visitor]	WARNING	Unable to find qualified name for module: req2flatpak.py
--------------------------------------------------
 tests/test_req2flatpak.py:106:
 [  B506  ] Severity: MEDIUM Confidence: HIGH
 Use of unsafe yaml load. Allows instantiation of arbitrary objects. Consider yaml.safe_load().

The yaml.safe_load() seems nothing to worry about b/c its in a test.

now I can't commit, not too impressed so far...
[WARNING] Stashed changes conflicted with hook auto-fixes... Rolling back fixes...
[INFO] Restored changes from /home/cbm/.cache/pre-commit/patch1677370833-285058.

... and installing it does not go well:
git commit
/usr/bin/python3: No module named pre_commit

So back to luddite mode for me I think!

I'm not very confident about the test: please take a look at that.

So back to luddite mode for me I think!

Don't blame me, but I had to smile reading about your struggle. Our pre-commit setup is not prefect yet. I tweaked it in #42 and #39.

No I have never learned that, was always worried it would mess up by other projects.

You can instal it on a pre-repository basis.

To fix the ci you will have to run the following:
poetry lock --no-update && SKIP=poetry-lock git commit

hi guys, this PR is almost finished, well done! we have a few open comments from the code review and three complaints from pylint. @cbm755 are you going to walk the last mile? I hope you are not getting annoyed, do you need / want help?

three complaints from pylint

I don't know about the complexity complaint. The import complaints could be resolved similar to how I did it in the tests.

Thanks @real-yfprojects for the edits.  I tested this and it works for me!
I do notice that the yaml dict out is in a rather unpleasant order:
build-commands:
- pip3 install --verbose --exists-action=i --no-index --find-links="file://${PWD}"
  --prefix=${FLATPAK_DEST} --no-build-isolation pymupdf
buildsystem: simple
name: python3-package-installation
sources:
- only-arches:
  - aarch64
  sha256: 36181c4cb27740791d611d0224dd18ac78e23a1f06aa2151394c5b9194b4f885
  type: file
  url: https://files.pythonhosted.org/packages/9c/90/4dcdb731e9aaecfa2f10300bf51f4f2d2079083819fd4a109a3e1d331338/PyMuPDF-1.21.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
- only-arches:
  - x86_64
  sha256: e5273ff0c3bf08428ef956c4a5e5e0b475667cc3e1cb7b41d9f5131636996e59
  type: file
  url: https://files.pythonhosted.org/packages/e0/27/83c843ef54f5c65874c844a77e216326eb5b2a2fcb08bd7cb0784fb759f9/PyMuPDF-1.21.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Note "build-commands" before "name" for example.  And "sha256" before "type".  Its still valid but I wonder why that happens?  Should I file an new issue?
For comparison, here is the JSON:
{
    "name": "python3-package-installation",
    "buildsystem": "simple",
    "build-commands": [
        "pip3 install --verbose --exists-action=i --no-index --find-links=\"file://${PWD}\" --prefix=${FLATPAK_DEST} --no-build-isolation pymupdf"
    ],
    "sources": [
        {
            "type": "file",
            "url": "https://files.pythonhosted.org/packages/9c/90/4dcdb731e9aaecfa2f10300bf51f4f2d2079083819fd4a109a3e1d331338/PyMuPDF-1.21.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl",
            "sha256": "36181c4cb27740791d611d0224dd18ac78e23a1f06aa2151394c5b9194b4f885",
            "only-arches": [
                "aarch64"
            ]
        },
        {
            "type": "file",
            "url": "https://files.pythonhosted.org/packages/e0/27/83c843ef54f5c65874c844a77e216326eb5b2a2fcb08bd7cb0784fb759f9/PyMuPDF-1.21.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl",
            "sha256": "e5273ff0c3bf08428ef956c4a5e5e0b475667cc3e1cb7b41d9f5131636996e59",
            "only-arches": [
                "x86_64"
            ]
        }
    ]
}

My understanding of modern Python is that dicts have a consistent unofficial ordering based on the the order you insert things into them.  In this case, that translates into a pleasant ordering when outputing JSON but not YAML...

I found a very long thread about it here where I discovered there is a sort_keys=False option.

I do notice that the yaml dict out is in a rather unpleasant order:

Good call!

well done, thank you for the effort! ready to merge. 🎉