Fix DuendeSoftware/Support#519, fix DuendeSoftware/Support#516

What issue does this PR address?
DuendeSoftware/Support#519 and DuendeSoftware/Support#516
Important: Any code or remarks in your Pull Request are under the following terms:
If You provide us with any comments, bug reports, feedback, enhancements, or modifications proposed or suggested by You for the Software, such Feedback is provided on a non-confidential basis (notwithstanding any notice to the contrary You may include in any accompanying communication), and Licensor shall have the right to use such Feedback at its discretion, including, but not limited to the incorporation of such suggested changes into the Software. You hereby grant Licensor a perpetual, irrevocable, transferable, sublicensable, nonexclusive license under all rights necessary to incorporate and use your Feedback for any purpose, including to make and sell any products and services.
(see our license, section 7)

thanks!

@leastprivilege thank you!


[PROJECT] Wise Strong Customer Authentication OTP Refactor

Overview
This is a refactor to implement Expense payment bundling and One-Time Password for Wise.
This was prioritized because it is time-sensitive and will a requirement for using Wise's API end of Q2.
Owner
@kewitz
Secondary Developer on project:
@kewitz
Roadmap & Timeframe

[x] Marking Wise expenses for payment.
[x] Paying Marked expenses in bundle and requesting OTP.
[x] Move all connected accounts from Personal token to OAuth.
[x] Demo and update documentation.

Success metrics
Wise keeps working for EU/UK hosts after the end of Q2.
Subjective: Bundling transactions for payment makes workflow better.
Release planning
June 4th.
Next steps

[x] Open up any appropriate project issues
[x] Open a documentation issue, link it to this one
[x] Open a release issue, link it to this one
[x] Create a project board, add this issue to the description, add any issues created above

Project Closure

Close all relevant project issues
Open up issues for improvements
Post comm's according to comm's plan (most likely in release issue)
Post project screencast on documentation slack channel
Post project closure in newsletter slack channel
Celebrate!!

Relevant Documentation
https://api-docs.transferwise.com/partners#batch-groups
https://api-docs.transferwise.com/partners#strong-customer-authentication-authorization-code-access-tokens

looks like this is all working, with DOCS! https://docs.opencollective.com/help/fiscal-hosts/payouts/payouts-with-transferwise#paying-expenses
Thanks for powering through @kewitz 🙌


Update to NuGet 3.3

How about we take the opportunity to fix the issue where if you've already got NuGet.exe in your local enlistment it won't update?  Here's a commit that does that: https://github.com/dsplaisted/msbuild/commit/b8ced26b54fc6667a2262db45493ff12c824ccbe

LGTM. @dsplaisted's PR #384 also includes this change. Should we wait for that PR or go ahead with this change?
I tried restoring with the new Nuget version on OSX but it still freezes midway.

I've been trying to pull b8ced26 into this but running into some merge issues because it depends on some infrastructure from xplat that doesn't exist here.  I do think we should do this for both master and xplat, and they're different enough that it needs to be separate.  But I like the idea of fixing the stale-nuget.exe problems, so I'll keep plugging.

@dotnet-bot test this please

Yea, the easiest way might be to just redo the changes, and then solve the conflict when we unify master and xplat.

Cherry-picking that change turned out to be a real pain, so I'm going to check this in as-is and rely on the improved behavior coming in from xplat when we re-merge it.  Since the update is nice but not required for full-framework builds, I hope that we can avoid any problems.  If any arise, we can revisit this decision.


Unable to change the default view settings for few pages

Version master.20160907042307_abe1199
1.Navigate to My setting->default views
2.Try changing view for:
Middleware: Middleware Domains
clouds: cloud providers, Tenants

Note this behavior is also present for Cloud->Stacks.
The linked BZ 0 was written against 5.5 and lists several more pages that do not comply with default view settings.


Autocompletion sometimes fails inside method calls

Tested versions
4.3 dev6
System information
Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; <IP_ADDRESS>33) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)
Issue description
Sometimes the autocompletion fails to appear. Usually it happens when doing some_method( and it's broken inside the parentheses. However it seems to have some convoluted conditions, because it happens only in very specific scripts/spots.
Here's example of such script:
@tool
extends EditorScript

func _run() -> void:
	for world in DirAccess.get_directories_at("res://Maps"):
		for scene in DirAccess.get_files_at("res://Maps/%s" % world):
			if scene.get_extension() == "tscn":
				process_scene("res://Maps/%s/%s" % [world, scene])

		for scene in DirAccess.get_files_at("res://Maps/%s/Interiors" % world):
			if scene.get_extension() == "tscn":
				process_scene("res://Maps/%s/Interiors/%s" % [world, scene])

func process_scene(path: String):
	EditorInterface.open_scene_from_path(path)
	var tile_map := get_scene().get_node_or_null(^"TileMap") as TileMap
	#print(get_

	if not tile_map:
		return

	print("Processing %s" % path)
	EditorInterface.get_selection().clear()
	EditorInterface.get_selection().add_node(tile_map)

	get_scene().get_tree().get_nodes_in_group(&"map_tools").front().menu_option(7)
	EditorInterface.save_scene()
	unreference()

If you uncomment the #print(get_ line and try to autocomplete something (in my case it was get_scene()), nothing will appear.
Steps to reproduce

Open the above script in script editor
Uncomment line 17
Put caret at the end and press Ctrl+Space

Minimal reproduction project (MRP)
N/A

I did some tests with lastest master b947c53dd and actually is very easy to reproduce, this happens in any place that has a if statment after, also if you don't complete the code and let the print function parentesis open will show the error: "Expected else after ternary operator condition" so maybe the problem is the editor wrongly thinking you're doing a ternary operation. If you close the print parenthesis the auto completation will works and no error will appear
https://github.com/godotengine/godot/assets/44306054/e56bc989-8ce9-45fc-ba7c-ade1b7dfb082

I looked into that a bit further. Turns out, having the right completion context for call arguments only works through a hack in the parser at the moment. As mentioned before the parser tries to parse a ternary and is therefore on an different code path than the hack.
The nature of that hack is to bypass the force parameter when pushing an completion context. Setting this parameter to true in the right places would fix the issue. However after asking in the contributor chat, it seems as if no one knows why we need the force parameter at all (or more precise why it should be false in any case). So I'd suggest removing it and relying only on the cursor position to determine whether the context should be updated.


Can't gulp bundle when updating version to 3.3.0

Category
[ ] Enhancement
[x] Bug
[ ] Question
@pnp/spfx-controls-react [ 3.3.0  ]
When I update the package to 3.3.0 and run gulp bundle --ship I get error:
<--- Last few GCs --->

[8200:0000020672DB2850]   117842 ms: Mark-sweep 1319.3 (1452.5) -> 1306.3 (1452.7) MB, 1007.9 / 0.0 ms  (average mu = 0.141, current mu = 0.065) allocation failure scavenge might not succeed
[8200:0000020672DB2850]   118911 ms: Mark-sweep 1320.0 (1452.7) -> 1308.6 (1455.7) MB, 966.0 / 0.0 ms  (average mu = 0.120, current mu = 0.096) allocation failure scavenge might not succeed

<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 000002A1EDEDC6C1]
Security context: 0x01a08281e6c1 <JSObject>
    1: d [0000017ADA69A149] [D:\WHD-Galleries-Plus\node_modules\terser\dist\bundle.min.js:~1] [pc=000002A1EF2A9DF5](this=0x01dc11b6c549 <AST_Defun map =<PHONE_NUMBER>7A11B1>,e=0x0208a3382291 <gn map =<PHONE_NUMBER>79FC61>,t=0x01cfebe87c49 <JSFunction (sfi = 000002777E26A479)>,n=0x00f959f19571 <Mn map = 000001EAF191E609>)
    2: /* anonymous */ [00000208A3382251]...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 00007FF6620C888A v8::internal::GCIdleTimeHandler::GCIdleTimeHandler+4506
 2: 00007FF6620A33C6 node::MakeCallback+4534
 3: 00007FF6620A3D40 node_module_register+2032
 4: 00007FF6623C1EAE v8::internal::FatalProcessOutOfMemory+846
 5: 00007FF6623C1DDF v8::internal::FatalProcessOutOfMemory+639
 6: 00007FF6625A85D4 v8::internal::Heap::MaxHeapGrowingFactor+9620
 7: 00007FF66259F5B6 v8::internal::ScavengeJob::operator=+24550
 8: 00007FF66259DC0C v8::internal::ScavengeJob::operator=+17980
 9: 00007FF6625A6957 v8::internal::Heap::MaxHeapGrowingFactor+2327
10: 00007FF6625A69D6 v8::internal::Heap::MaxHeapGrowingFactor+2454
11: 00007FF6626D0C77 v8::internal::Factory::NewFillerObject+55
12: 00007FF66274DE66 v8::internal::operator<<+73494
13: 000002A1EDEDC6C1

My package.json
{
    "name": "---",
    "version": "0.0.1",
    "private": true,
    "main": "lib/index.js",
    "engines": {
        "node": ">=0.10.0"
    },
    "scripts": {
        "build": "gulp bundle",
        "clean": "gulp clean",
        "test": "gulp test"
    },
    "dependencies": {
        "@fluentui/react": "^8.14.10",
        "@microsoft/sp-core-library": "1.11.0",
        "@microsoft/sp-lodash-subset": "1.11.0",
        "@microsoft/sp-office-ui-fabric-core": "1.11.0",
        "@microsoft/sp-property-pane": "1.11.0",
        "@microsoft/sp-webpart-base": "1.11.0",
        "@pnp/graph": "^2.5.0",
        "@pnp/sp": "^2.5.0",
        "@pnp/spfx-controls-react": "^3.3.0",
        "@pnp/spfx-property-controls": "2.5.0",
        "fslightbox-react": "file:src/common/WHLibs/fslightbox-react-pro-1.4.2.tgz",
        "gulp-spsave": "^3.1.1",
        "moment": "^2.29.1",
        "office-ui-fabric-react": "6.214.0",
        "react": "16.8.5",
        "react-dom": "16.8.5",
        "react-html-parser": "^2.0.2",
        "react-slick": "^0.27.11",
        "react-waypoint": "^9.0.3"
    },
    "devDependencies": {
<EMAIL_ADDRESS>"0.3.5",
        "@microsoft/sp-build-web": "1.11.0",
        "@microsoft/sp-module-interfaces": "1.11.0",
        "@microsoft/sp-tslint-rules": "1.11.0",
        "@microsoft/sp-webpart-workbench": "1.11.0",
        "@types/chai": "3.4.34",
        "@types/es6-promise": "0.0.33",
        "@types/mocha": "2.2.38",
        "@types/react": "16.8.8",
        "@types/react-dom": "16.8.3",
        "@types/webpack-env": "1.13.1",
        "ajv": "~5.2.2",
        "gulp": "~3.9.1",
        "gulp-replace": "^1.0.0",
        "gulp-sequence": "^1.0.0",
        "typescript": "^3.9.5",
        "yargs": "^11.0.0"
    }
}

But we have many other solutions with<EMAIL_ADDRESS>and SPFx v1.11
I just want to understand why this one is breaking.

@gabsnery what Alex mentioned regarding versions is likely the reason, but just to double-check that this is not caused by some commonly known nodejs issues, could you please try this out?
https://stackoverflow.com/questions/53230823/fatal-error-ineffective-mark-compacts-near-heap-limit-allocation-failed-javas


Fixed #23932 -- Added docs on how to migrate unique fields

Could you try to fix your branch so it doesn't contain all the unrelated commits? Also, fixes -> fixed in the commit message.

Fixed things up according to Tim's comments - thanks!

You might also want to consider to link to the migration operations when you mention them for the first time.

Just saw that this change is part of the migration operations docs. I think it should be part of docs/topics/migrations.txt (which is getting really large)
@timgraham How do you feel about moving docs/topics/migrations.txt to docs/topics/migrations/index.txt and add docs/topics/migrations/advanced-usecases.txt that would for now cover this topic and maybe https://docs.djangoproject.com/en/dev/topics/migrations/#custom-fields and https://docs.djangoproject.com/en/dev/topics/migrations/#model-managers (and maybe something else as well)?

Or maybe the more "recipe" type migration examples like this and "Data migrations and multiple databases" would be better suited in "howto".

:+1: @timgraham Didn't think of the howto section. That's probably the best place for that.

I thought migration ops page might be better than migrations page for this because migrations page says "If you’re interested in the more advanced migration operations ..." and then links to migration ops; this recipe is arguably more advanced than things in migrations page; but mainly it's more of a special case and so less of an interest to someone reading migrations page for general overview of migrations.
Having it in Howto may be good, but it should be at least linked and shortly explained in migration ops page because of the exception that users will run into when they try this.

@akulakov Yes, the howto page should be linked from both topics/migrations and ref/migration-operations.

Ok, sounds good!

I don't think we should have 1 page for every example like this. As suggested above, could you first move the "Data migrations and multiple databases" example to a separate document along with an entry in the table contents and links from the other migration docs. The new content can be a separate commit after that. Not sure on a good name for the document, maybe "migration-recipes" or "writing-migrations"?

@timgraham sorry but the multiple databases thing is a separate PR: https://github.com/django/django/pull/4013 ?  Or you are suggesting it should be merged into this PR? (I'm new so not sure how to best separate PRs so would be happy to get any guidance..)

Sorry, this is what I was trying to describe: https://github.com/django/django/pull/4042. The idea is to merge that first and then add this in that new document.

I merged the linked PR. Could you move the example to docs/howto/writing-migrations.txt?

@timgraham Yes, thanks -- will do that.

Moved it to writing-migrations.txt.
I think it might be good to have a direct link to this section from migrations.txt, for the reason of this use case: a user runs into the failed migration while doing a reasonable migration operation with a unique field, (and exception will refer to unique field as the source of failure), user goes to migrations.txt to look for notes on unique field migrations. If he doesn't find a specific note on that, that creates impression that either this is a bug or django docs are incomplete (because it's not obvious that this type of migration will be covered in a howto section).
Does that make sense? I was thinking of adding this like to 'see also' section:
:doc:`Creating migrations that add unique fields to existing non-nullable rows </howto/<link>`

I don't think adding every entry of the "how to" as a "see also" entry makes much sense. I think most people will use a search engine when they have a problem and will be able to find the appropriate docs.

I didn't mean this should be done for every entry but only for ones (and realistically it will probably be one or two for any 'main' page), when django seems to behave in a way that could be seen as buggy (even to someone experienced with django).
In other words, when I have to do e.g. migration with multiple databases, the expectation is that there'd be a blog post or a howto section, official or otherwise, on how to do this. It seems like a "howto type of thing". With unique field migration, it seems like a regular type of migration I'd expect django to "just do".
However it's probably a fairly rare use case, so it might be ok to have people google for it.
Just thought I'd bring it up, this will also help me understand how django docs usually approach this type of "principle of least surprise" issue. thanks!

This looks good. Here are some cosmetic edits: http://dpaste.com/160W9M3
One thing I thought of is that in the event someone doesn't take the database offline during the migration and a row is created after the AddField and before RunPython, the existing value for the new field will be clobbered by the migration. Do you think this warrants a note? We could try to make the migration "smarter" by trying to have the RunPython only modify rows that have the duplicate value.

@timgraham: 2 comments on your diff: line 66 has "valuae" and it looks like the uuid import got lost in the migration file.

Adding a short wanting sounds like a good idea. However, making the migration smarter would involve database level defaults from my point of view.

A couple of notes (in addition to Markus' notes):
null=True is not being reset in the diff, is this intentional? I think we're setting null=True as a temporary measure to enable the operation, and if user needs null=True, he'll know not to reset it.
MyModel or Poll for model name example?

Thanks for the reviews. Hopefully I fixed all the issues:  http://dpaste.com/3X53YZ3
null=False isn't needed in the AlterField because that's the default.

One quick note: UUIDField is already max_length=32 by default, perhaps cleaner to leave this arg out?

Yes, it's currently part of the auto-generated migration, but shouldn't be as UUIDField is missing a deconstruct() method, I'll fix that first.

merged in 1f9e44030e9c5300b97ef7b029f482c53a66f13b, thanks!
Fix for UUID.deconstuct(): https://github.com/django/django/pull/4065

Great -- much thanks for your help, @timgraham and @MarkusH !


python310Packages.ansible-doctor: 1.3.0 -> 1.4.0

Description of changes
https://github.com/thegeeklab/ansible-doctor/releases/tag/v1.4.0

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 177420 run on x86_64-linux 1

2 packages built:

ansible-doctor (python39Packages.ansible-doctor)
python310Packages.ansible-doctor


Create Patternfly 3 Table component methodology

Data integration mockups include Table like functionality.  Patternfly 3 examples reflect a minimal level of Table definition/examples based on Rectabular however, it would be helpful to define a common implementation pattern for adding tables as components and within components.

Right now we have only one table used in the codebase, here.
The idea behind the ExtensionIntegrationsTable component is to provide an abstraction over the underlying table library, with columns and the overall table behavior already defined for the consumer. So to use it one needs to pass only the data array - of the right shape - and the select handler.
This doesn't mean that there is a lot of thought behind this solution. What do you think about this pattern? Would it work for you?

Thx Riccardo,
This is a start.
our UX mockups currently have 2 table scenarios.
The first is a summary table of the columns defined for a "View" which basically shows a known number of columns (id, isKey, name, datatype, etc..). So the pattern in ExtensionIntegrationsTable component should work.
The 2nd scenario involves displaying a table of data returned from a query that could contain any number of columns. This would require data dynamically driving the column definitions (#columns, header titles, cell datatype, etc...)
Barry


Feat: aliased app dir for easier imports

Addresses https://github.com/postlight/lux/issues/272
The documentation for rollup-plugin-alias isn't great, but this appears to be the correct usage. I tested it in the social-network example app and the test-app and it's working as expected.

Awesome job! This works in the test-app as well 👍


Correct the Blob and Key-Value titles and intro text, since they are …

…switched.
The provider documentation for blobs and key-value have their titles and intro text switched.  Swap them with one-another.  Fixes #70

Thank you )


Replace Image generation with DOT JS-based rendering

Sonatype has identified that JGraphX has a known vulnerability:
https://sbom.sonatype.com/report/T1-a4e79c5353879ed9b588-3209d9d507fc3a-1727273211-8e351c4d6ac9418cb8a26ab64b24c8db
To address this, a DOT file should be generated by RefactorFirst and then rendered via a Javascript library call similar to the following:
<!DOCTYPE html>

    <meta charset="UTF-8">
    <title>Graphviz Example</title>

Released in 0.6.0


Update docker-compose to handle newer versions of postgres

Add fix for recent versions of Postgres that require a password be set or to explicitly trust the host

For dev and for simplicity we set the POSTGRES_HOST_AUTH_METHOD=trust env var to not have to provide a password

Hello?

I wonder what I'd do if I were David Bowmen and could become a monolith...

another day another dollar, is anyone home?

So can this be merged @OhArthits ?


Missing CharacterController.gd script

Unable to enable the plugin because the script Character/Scripts/CharacterController.gd doesnt exist when the plugin.gd file tries to preload it.

Hi, thanks for catching that. The original CharacterController.gd script was replaced, so I corrected the plugin script to reflect this.
I've submitted a pull request so this should be fixed once it gets merged in.
You can also clone the old-version branch if you want to see the original code that got removed.


Request for Adding Forward Proxy Functionality

Hello,
I would like to propose the addition of a forward proxy feature to our system. A forward proxy acts as an intermediary server between client devices and target servers, enhancing network security and privacy by hiding client device identities. It also enables efficient management of network traffic through filtering, monitoring, and logging of incoming requests.
Implementing a forward proxy would improve our system's capabilities in handling caching, load balancing, and access control. It would provide an additional layer of defense against unauthorized access attempts and enhance overall network performance.
I kindly request your consideration of this proposal for adding a forward proxy functionality to our system.
Thank you for your attention.
Best regards,
JackCen

Hello @ghotm,
I feel this is a bit out of scope of this project. Do you mind explaining why you think Zen and its users might benefit from a multi-user/forward proxy mode?

1.Enhanced Privacy and Security: With a forward proxy mode, Zen users can route their internet traffic through intermediary servers, effectively concealing their IP addresses and encrypting their data. This added layer of privacy and security is particularly valuable for users who prioritize anonymity and protection against surveillance or data interception.
2.Access to Restricted Content: In regions where certain websites or online services are restricted or censored, a forward proxy can help Zen users bypass these restrictions by accessing content through servers located in unrestricted regions. This capability empowers users to freely access information and resources that may otherwise be inaccessible due to geopolitical or regulatory barriers.
3.Improved Performance and Reliability: By caching frequently accessed resources and optimizing network traffic, a forward proxy can enhance the speed and reliability of internet connections for Zen users. This is especially beneficial in environments with limited bandwidth or unreliable network infrastructure, where proxy servers can mitigate latency and buffering issues.
4.Collaborative Workspaces: In scenarios where multiple users within an organization or team utilize Zen for collaborative work, a multi-user mode with forward proxy support can streamline access to shared resources and facilitate secure communication channels. This enables seamless collaboration and information sharing while maintaining privacy and security protocols.
5.Compliance and Governance: For businesses and institutions that require stringent compliance with data protection regulations or internal governance policies, a multi-user/forward proxy mode offers centralized control and monitoring of internet usage. Administrators can implement access controls, content filtering, and auditing mechanisms to ensure adherence to regulatory requirements and organizational guidelines.
This is merely a proposal, as I am currently facing the issue mentioned in the second point. However, since Zen does not support forward proxying, I find myself compelled to stop using Zen.
Thank you for your attention


[Linter] Rule configuration severity is not enforced

I encountered an issue with the configuration of the @typescript-eslint/no-explicit-any rule in the eslintrc.json file. Despite the rule being set to "error", warnings are still being generated instead of errors.
Configuration
eslintrc.json
{
  "rules": {
    "@typescript-eslint/no-explicit-any": "error"
  }
}

Command line output
⚠ typescript-eslint(no-explicit-any): Unexpected any. Specify a different type.
     ╭─[src/helpers/htmlTemplate.ts:144:1]
 144 │
 145 │ export function renderHtml(template: string, data: Record<string, any> = {}): string {
     ·                                                                   ───
 146 │   // Render template
     ╰────
  help: Use `unknown` instead, this will force you to explicitly, and safely, assert the type is correct.

Finished in 20ms on 34 files with 83 rules using 16 threads.
Found 62 warnings and 0 errors.

PR https://github.com/oxc-project/oxc/pull/2031 fixed the off problem but not the severity.
Tested on the latest 0.2.1.

I'm trying to do a PR to correct the issue.
It seems that the replace (here : https://github.com/oxc-project/oxc/blob/main/crates/oxc_linter/src/config/mod.rs#L97) makes the associated severity disappear.
It's always Allow.

Also, the oxlint -D all command only outputs warnings.

From what I understand, severity is hardcoded into the rules.
So we can't change the gravity by configuration at the moment?

@Boshen I can help on this one.
I have already looked a little at how we could overcome this problem but it affects the design of Oxlint.

Changing a diagnostic to an error was never implemented. The current design treats everything as a warning.
I would consider it as a bug if vscode raises any errors at the moment.

We can also start a topic on changing the current implementation to distinguish warnings and errors when we supply "--deny" / "--warn" from the cli and "error" / "warn" from the config.

The whole error/warning flow is currently broken from my tests. Given a file.tsx with the following contents:
var Hello = ;

Running with --deny-warnings has no effect:
$ npx oxlint@latest --deny-warnings

  ⚠ eslint-plugin-react(jsx-no-target-blank): Using target=`_blank` without rel=`noreferrer` (which implies rel=`noopener`) is a security risk in older browsers: see https://mathiasbynens.github.io/rel-noopener/#recommendations
   ╭─[file.tsx:1:23]
 1 │ var Hello = ;
   ·                       ────────
   ╰────
  help: add rel=`noreferrer` to the element

Finished in 2ms on 1 file with 86 rules using 10 threads.
Found 1 warning and 0 errors.

Running with -D correctness has also no effect:
$ npx oxlint@latest -D correctness

  ⚠ eslint-plugin-react(jsx-no-target-blank): Using target=`_blank` without rel=`noreferrer` (which implies rel=`noopener`) is a security risk in older browsers: see https://mathiasbynens.github.io/rel-noopener/#recommendations
   ╭─[file.tsx:1:23]
 1 │ var Hello = ;
   ·                       ────────
   ╰────
  help: add rel=`noreferrer` to the element

Finished in 2ms on 1 file with 86 rules using 10 threads.
Found 1 warning and 0 errors.

No matter what I do, I can't make oxlint to return a non-zero status when running.

@alisnic
npx oxlint@latest --deny-warnings
echo $?

This is not printting 1?

It is printing, I am confused. I'm sorry, I guess I was confused by the "Found 1 warning" message
$ echo $?
1

I can fix this now after changing how diagnostics work under the hook
https://github.com/oxc-project/oxc/blob/f6daf0b7ae4fb9a3ac9e8520824eb06a278c78ea/crates/oxc_diagnostics/src/lib.rs#L47

Next version:
Breaking change:

--deny / -D from the CLI and error from configuration file will report diagnostics as severity "error".
--warn / -W from the CLI and warn from configuration file will report diagnostics as severity "warning".


[Feature Request] Implement Collase/Expand Module Settings

Already working on a settings overhaul.

Included in version 1.1.5


[flodash] unnecessary flutter dependency

The flodash library is purely for manipulating data structures. Can we drop it's flutter dependency?

The flodash library is purely for manipulating data structures. Can we drop it's flutter dependency?

Hi @tsouza, Sorry for the late reply. Flutter has been removed from the dependency list and a prerelease version has been published. Will be promoting it to stable in some time. Thank you for raising this. It was on the bucket list but was lost down the line.


Ryan M: Watch claybag.com

Ryan M requests the watch of the watch_keyword claybag\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

claybag\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by double-beep in Charcoal HQ


Bug 2089446 - Handle leftover rook-ceph-external-cluster-details secret

Resolves bz#2089446
Signed-off-by: Timothy Asir Jeyasingh<EMAIL_ADDRESS>

@bipuladh , @GowthamShanmugam Please review

/close
closing for now as https://bugzilla.redhat.com/show_bug.cgi?id=2089446#c6


Remove dependency on Foundation

Is your feature request related to a problem? Please describe.
Dependency on Foundation affects significantly cold start.
Describe the solution you'd like

Remove dependency on any Foundation types like Date and Data.
Extend API to be able to provide custom JSON encoder/decoder.

Additional context

cold start of lambda is ~0.3s faster without Foundation, decoding Event without any date formatters/decoders, difference increases when statically linked;
https://github.com/swift-server/swift-aws-lambda-runtime/pull/79#issuecomment-673932658

Foundation JSON encoder/decoder has terrible performance on Linux, see https://github.com/swift-server/swift-aws-lambda-runtime/issues/153#issue-671370288, changing will improve performance of AWSSDKSwift not only during cald start

It is relatively easy to use custom JSON encoder and remove dependency on Foundation when using Swift AWS Lambda Runtime

It is not possible not to link Foundation when using AWSSDKSwift,
see https://github.com/swift-server/swift-aws-lambda-runtime/issues/163

CC @fabianfett

I think you need to break this up into separate tasks. This is a huge task which would require us to replace
URL, Date, DateFormatter, NSRegularExpression, JSONEncoder, CharacterSet, UUID, ContiguousBytes, DataProtocol
You would also need a FoundationCompat library to provide the interfaces that require Foundation. eg AWSPayload conversion to and from Data
One thing that might hold all of this back though is swift-crypto pulls in Foundation, I'm not sure how you want to resolve that one.
There is an argument for doing some of this work still. We could look at replacing the JSONEncoder. I'm sure @fabianfett would be really keen on this.

One thing that might hold all of this back though is swift-crypto pulls in Foundation, I'm not sure how you want to resolve that one.

Same is true for AsyncHTTPClient

There is an argument for doing some of this work still. We could look at replacing the JSONEncoder. I'm sure @fabianfett would be really keen on this.

I think it would be enough to make the default JSONEncoder and JSONDecoder replaceable.
Also I have an offering to replace UUID: https://github.com/fabianfett/swift-extras-uuid

Same is true for AsyncHTTPClient

Good point. Removing Foundation from AHC would be a good starting point but someone needs to do an implementation of Date first and that would be a huge undertaking. And getting SSWG to accept it would be even harder.

I think it would be enough to make the default JSONEncoder and JSONDecoder replaceable.

Should be easy enough.

Also I have an offering to replace UUID: https://github.com/fabianfett/swift-extras-uuid

You can go ahead, although given we can't remove Foundation in the foreseeable future is this necessary? What do we gain, except less exposure.

@adam-fowler @fabianfett
thank you for your feedback and identifying the main problems.

Good point. Removing Foundation from AHC would be a good starting point but someone needs to do an implementation of Date first and that would be a huge undertaking. And getting SSWG to accept it would be even harder.

Had a (very) quick lock at AsyncHTTPClient and it seems:

it uses Date only to write expires Cookie value (always in the same format and in UTC),
URL to parse schema and host
Data in 2 (convenience) functions

So technically its some work but probably not a huge effort - dumping a timestamp is much smaller task than rewriting Date;
I will play with in spare time (low priority), this should give me a better understanding of the "not using Foundation" challenges.
I understand that such PR could be never approved...

I understand that such PR could be never approved...

I wouldn't be so sure of that. If you can produce a PR which removes Foundation I think there will be people sympathetic to it.

https://github.com/swift-server/async-http-client/issues/299


Hey! Any example how to extract rgb color from palette?

hey! Im pretty newbie in rust. Just finished extracting voxel position and it's all works, but how to extract rgba data for each voxel? Thanks!

Thanks for github, found here how to do this properly
https://github.com/expenses/isomagic/blob/7f84772085d3f980e5766e5a8f5a33c85f50f5af/src/main.rs
`
fn colour(&self, index: u8, subtract: u8) -> Rgba {
let colour = self.palette[index as usize - 1];
let r = (colour % 256) as u8;
let g = ((colour >> 8)  % 256) as u8;
let b = ((colour >> 16) % 256) as u8;
let a = ((colour >> 24) % 256) as u8;
    let r = r.saturating_sub(subtract);
    let g = g.saturating_sub(subtract);
    let b = b.saturating_sub(subtract);

    Rgba {
        data: [r, g, b, a]
    }
}

`


BUG: Date validation for plan a trip page

Describe the bug
Date validation in Plan a trip page. The trip gets planned for an earlier date.
Expected behaviour
The trip is expected to be planned for a future date.The alert message should be popped up once the future date is selected.
Screenshots

Are you contributing under any open-source program ?
I am a GSSOC'24 Contributor

Good issue.. @nidhipai78
assigned to you. Plz follow the contribution guidelines for raising a PR. After contributing, please notify and link the PR here.

Hello,
The PR has been submitted for "Date Validation" in Plan a Trip for the
issue #611.
The link is  https://github.com/apu52/Travel_Website/pull/677
https://github.com/apu52/Travel_Website/pull/677
Thank You
On Sat, Jun 1, 2024 at 4:32 PM Krishnendu Dasgupta @.***>
wrote:

Good issue.. @nidhipai78 https://github.com/nidhipai78
assigned to you. Plz follow the contribution guidelines for raising a PR.
After contributing, please notify and link the PR here.
—
Reply to this email directly, view it on GitHub
https://github.com/apu52/Travel_Website/issues/611#issuecomment-2143406821,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2IUQ2RGNR4AUVTQYYJ5O5DZFGS4FAVCNFSM6AAAAABIJPIZRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTGQYDMOBSGE
.
You are receiving this because you were assigned.Message ID:
@.***>

@apu52 check the PR plz..

@apu52 check the PR plz..

Thanks for the reminder. Done


Hitting "Enter" selects the text

I don't know if this is intended behavior but I noticed a difference in the new 0.7.1 release. When you hit "Enter" in the middle of a line containing text, it selects the part of the text between where you intended the line break and the end of the line.
These screenshots will make it clearer.
BEFORE: the cursor is between the "e" and the "d" in the word "Mobiledoc".

AFTER: I hit Enter and the text gets selected

Thanks @YoranBrondsema. Seems like a regression.


Change "static" property does not affect resize/drag ability

First of all - thanks for the great grid layout system, it helped a lot to create dynamic widgets pages!
The problem we have - after change static property of layout item to true/false - when user clicks at grid layout item button, designed for it - it doesn't affect item behaviour anyhow.
If we save layout with static = true and reload page - item will stay static until next page reload - without any difference if static will be set to true or false. Same with static = false - console.error(layout); before render() with ReactGridLayout shows static true or false for item, but its behaviour doesn't change and stays same as static property was set when page was loaded.
layout.map((item, index) => inside ReactGridLayout shows item.static correctly set to true or false
// item.static = `true` or `false` - `borderColor` changes correctly
console.error(layout);

return (
  <ReactGridLayout
    layout={layout}>
    {layout.map((item, index) =>
      <div
        style={{
          borderColor: item.static ? 'crimson' : ''
        }}>

Please let me know what additional code / info should I provide to describe situation better.

I'm having the same problem. @elmeister did you end up solving this somehow?

@felixbouleau, nope, the problem is still present unfortunately.

Could you please create a reproduction? http://www.webpackbin.com/VymTE3zWG
On Dec 29, 2016 9:19 AM, "Sergey"<EMAIL_ADDRESS>wrote:

@felixbouleau https://github.com/felixbouleau, nope, the problem is
still present unfortunately.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/STRML/react-grid-layout/issues/400#issuecomment-269644509,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJFP_cUr4Rju0u_7jFkyYydJ1O8R1piks5rM896gaJpZM4Kq-Wq
.

@STRML I really don't know what I'm doing. But here's an attempt to show what's failing for me: http://www.webpackbin.com/E1e8-mAVf
After pressing "Freeze #0" I expect item 0 to be static. The proper style is applied, but I can still move and resize it.

I'm experiencing the same bug.

Not sure if this applies to everyone, but I was having the same issue.
I was passing data-grid on each element, instead of using layout.
I then transitioned to using layout instead of data-grid on each element, and then static functioned correctly for me.

I am only using layouts property for this.

I've been trying to handle the same problem, and for me it looks like it's being caused by the componentWillReceiveProps function in ReactGridLayout.js
  ReactGridLayout.prototype.componentWillReceiveProps = function componentWillReceiveProps(nextProps) {
    var newLayoutBase = void 0;
    // Allow parent to set layout directly.
    if (!(0, _lodash2.default)(nextProps.layout, this.props.layout)) {
      newLayoutBase = nextProps.layout;
    }

    // If children change, also regenerate the layout. Use our state
    // as the base in case because it may be more up to date than
    // what is in props.
    else if (!(0, _utils.childrenEqual)(this.props.children, nextProps.children)) {
        newLayoutBase = this.state.layout;
      }

    // We need to regenerate the layout.
    if (newLayoutBase) {
      var newLayout = (0, _utils.synchronizeLayoutWithChildren)(newLayoutBase, nextProps.children, nextProps.cols, nextProps.verticalCompact);
      var _oldLayout = this.state.layout;
      this.setState({ layout: newLayout });
      this.onLayoutMaybeChanged(newLayout, _oldLayout);
    }
  };

ReactGridLayout holds it's own state, and sometimes it seems to believe that it's layout is more correct than the one you pass it as props (see lines 8-13 of the above code).
The way I got around this was to have the component always trust the layout passed in props. Be careful, I believe this turns it into a more "controlled" component, so there's less room for error on your part, but it should now exactly follow the layout you give it.
Here is my edited componentWillReceiveProps function:
  ReactGridLayout.prototype.componentWillReceiveProps = function componentWillReceiveProps(nextProps) {
    // Always assume that the passed layout is correcct
    var newLayoutBase = nextProps.layout;

    // We need to regenerate the layout.
    if (newLayoutBase) {
      var newLayout = (0, _utils.synchronizeLayoutWithChildren)(newLayoutBase, nextProps.children, nextProps.cols, nextProps.verticalCompact);
      var _oldLayout = this.state.layout;
      this.setState({ layout: newLayout });
      this.onLayoutMaybeChanged(newLayout, _oldLayout);
    }
  };

This seems to me like a slightly destructive/hacky solution, mostly because I don't really understand how !(0, _lodash2.default)(nextProps.layout, this.props.layout)) resolves. If any dev could shed some light on a better solution, it would be appreciated! Good luck

I've also been affected by this today. After lots of head scratching we figured out a solution that worked for us: setting an i property for each of the layout items, and also setting the same value as the react key for the item elements.

I've also been affected by this today. After lots of head scratching we figured out a solution that worked for us: setting an i property for each of the layout items, and also setting the same value as the react key for the item elements.

Any more info you can shed on your solution Andre?


enable strict testing mode

@YaroShkvorets I've re-enabled the strict testing mode I've added on this PR. This means whenever any decoding fails, the test will fail as well. As you can see there is a table failing to decode. Trying to figure out whether this is a contract/ABI issue or if it's something going on with the decoder here.


Reduce false-positive results by replacing code with whitespace?

I believe currently Dustmite deletes code when it does its reduction? But that means we cannot have a test condition like grep -F module.d(145): Error: No property info for 'abcd' and instead have to search for something like: grep -F "Error: No property info for 'abcd' without the line number, which will bring out more false positives during reduction.
If instead Dustmite replaced code it wants to delete with whitespace characters, then the line numbers would be preserved, and we could have less false-positives this way.
What do you think?

I think this is a great idea. It will increase I/O so probably will slow down reductions that don't need it, so, maybe a --white-out switch?

It's a bit tricky because DustMite mutates its tree containing the reduced program on successful reductions by completely removing nodes. That would have to change (keep nodes but reduce non-whitespace characters with whitespace, and also don't try to reduce them again). An alternative would be to change how DustMite represents the reduced program in memory, e.g. make the tree immutable but keep a separate state which represents whether a node is removed or not. What complicates things is that there are other reduction types, like unwrap / concat, which do more complicated things than just remove nodes.

Whee!

Implemented in 6746464fe8036342d0f657e11c442e9c24539085. It took me the better half of today to figure out the necessary alogrithm / data structure changes, but I'm pretty happy with the result :)

Amazing.

Awesome, thanks!


Add Quakespasm

New Port for Quake supporting mods and Dimension of the Machine as well as GL4ES accelerated!
URL: https://github.com/Slayer366/quakespasm-for-GL4ES
Quakespasm
Instructions:
Files needed
Quake:
quakespasm/id1/pak0.pak
quakespasm/id1/pak1.pak
quakespasm/id1/music/track02.ogg
quakespasm/id1/music/track03.ogg
quakespasm/id1/music/track04.ogg
quakespasm/id1/music/track05.ogg
quakespasm/id1/music/track06.ogg
quakespasm/id1/music/track07.ogg
quakespasm/id1/music/track08.ogg
quakespasm/id1/music/track09.ogg
quakespasm/id1/music/track10.ogg
quakespasm/id1/music/track11.ogg
Scourge of Armagon:
quakespasm/hipnotic/pak0.pak
quakespasm/hipnotic/music/track02.ogg
quakespasm/hipnotic/music/track03.ogg
quakespasm/hipnotic/music/track04.ogg
quakespasm/hipnotic/music/track05.ogg
quakespasm/hipnotic/music/track06.ogg
quakespasm/hipnotic/music/track07.ogg
quakespasm/hipnotic/music/track08.ogg
quakespasm/hipnotic/music/track09.ogg
Dissolution of Eternity:
quakespasm/rogue/pak0.pak
quakespasm/rogue/music/track02.ogg
quakespasm/rogue/music/track03.ogg
quakespasm/rogue/music/track04.ogg
quakespasm/rogue/music/track05.ogg
quakespasm/rogue/music/track06.ogg
quakespasm/rogue/music/track07.ogg
quakespasm/rogue/music/track08.ogg
quakespasm/rogue/music/track09.ogg
Dimension of the Past:
quakespasm/dopa/pak0.pak
Arcane Dimensions:
quakespasm/ad/pak0.pak
quakespasm/ad/pak1.pak
quakespasm/ad/pak2.pak
Dimension of the Machine:
quakespasm/QuakeEX.kpf
quakespasm/mg1/pak0.pak
Notes: Thanks to Ozkan Sezer (sezero) for the one of the most awesome and incredibly capable source ports for Quake supporting mods such as Arcane Dimensions and the latest 2021 Re-release, Dimension of the Machine.  It is recommended to use an RK3566 or faster CPU to run Arcane Dimensions or Dimension of the Machine.  Thanks to ptitseb for GL4ES.
Tested on ArkOS, 351Elec/AmberElec, RG351P, RG351M, RG351MP, RG353P, RG503

Your port is missing the quakespasm.port.json

quakespasm.ports.json added 👍

port images missing per the check.

@Slayer366 Can you please add one more thing. A markdown file should be added to the markdown folder with the same name as the port zip (.md instead of .zip). These details will get rendered on the detail page of the new wiki for this port.
Example file
Tool to help generate one if you need.

You got it.  That md generator you guys have there is pretty slick, btw.

Agreed.  Thank you for doing that for me.  Good lookin' out.

Quakespasm games run fine on RGB30 (JELOS), but there's no audio if I launch from EmulationStation. However, when launching from SSH, the audio plays fine. Maybe some permissions issue or something?

Gotcha.  I'll look into it.
On Thursday, October 26, 2023 at 09:19:52 PM CDT, tabreturn @.***> wrote:
Quakespasm games run fine on RGB30 (JELOS), but there's no audio if I launch from EmulationStation. However, when launching from SSH, the audio plays fine. Maybe some permissions issue or something?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@Slayer366 if you want quick feedback/testing, you can head over to the Portmaster discord and open a forum thread. We have a group of testers with a variety of devices willing to test ports. https://discord.gg/JxYBp9HTAY


feat: Updated deps_app/2 to support missing optional applications

Following up your PR you made on Dialyxir. I have tried to manage the issue mentioned by @josevalim.
The PR updates the deps_app/2 function in the Dialyxir.Project module in lib/dialyxir/project.ex to handle different versions of Elixir. Added version checking for Elixir 1.15 or later, and adjusted the implementation accordingly. The changes ensure that the deps_app/2 function works correctly with the appropriate version of Elixir.
I'm not totally sure if my change is backward compatible with previous versions of Elixir.

@GRoguelon yes, can you please open a new PR that targets master on this repo?

Directly submitted on jeremyjh/dialyxir#514


horizontal scroll bar on topics in drawer

Steps to Reproduce

Visit my test course at https://ocw-draft-qa.global.ssl.fastly.net/courses/peters-test-2021-09-29-1/pages/asdf/
Using responsive mode, set the browser width to "Laptop with MDPI screen"

Expected Behavior
right side drawer is responsive, but without scrollbars.
Actual Behavior
right side drawer displays a horizontal scrollbar
Screenshot or Screencast

I can't reproduce this the same way, but if I use response mode and narrow the window, I will see scroll bars. We should wrap the topics until we get to the mobile layout, where the drawer content is hidden.

@pdpinch I have created the PR for this but I wonder this might be a breaking change for a few dimensions. As it will be good for width: 1280px (Laptop with MDPI screen),  but we have a range of width from 992px to 1250px where the course info is unreadable and horizontal scroll will come in handy here.
For example:
for width:992px

for width:1250px

If it's important for 1280px then we can only remove the horizontal scroll for this dimension and not for the dimension range stated above.
What are your thoughts?

Yeah, that's not great. Can we let the content in the drawer wrap at that width?
Or, what happens if we let the drawer go to the mobile presentation at that width? I think it becomes a button, but I can't remember.

Yeah, I tried to wrap the content in that width but it became difficult, (1-2 words per line were not looking user friendly).
yes, you are right, it becomes a button in mobile representation but that occurs on 991px width, which I believe is the default breakpoint for medium screens. I'm not sure whether it's a good practice to change the default breakpoint or not. Our issue is from 992px to 1250px.
What do you think?

I guess if the content is not being adjusted in this drawer section then a horizontal scroll makes sense but if the content is being adjusted in the section then a horizontal scroll doesn't make sense and can be considered a bug

Is it possible to only show the horizontal scroll when the content is being adjusted, and it doesn't fit?

Yes, I'll update it to only show the horizontal scroll when the content doesn't fit.
If the content fits, then horizontal scroll will not be shown.


Fix some styles errors with the scroll bars

Remove some extra scrollbars when the cover is full open and other scroll changes.

Thanks! you rocks 😎


Support rolling(humble)

Some modifications are necessary to migrate to ros2 rolling(humble).
https://github.com/autowarefoundation/autoware.universe/pull/247

https://docs.ros.org/en/foxy/Releases/Release-Humble-Hawksbill.html

We have to plan migration steps to Humble.
My (super rough) proposal is:

Support rolling after Ubuntu 22.04 is released. (Around the end of April.)

If a change is supported by Galactic, merge to the main branch.
If not, merge to the rolling branch.

Support Humble after ROS 2 Humble is released. (Around the end of May.)

Ideally, just renaming rolling to humble.

Create the galactic branch and merge humble to main.

@xmfcx @mitsudome-r What do you think about it?

https://github.com/autowarefoundation/autoware.universe/labels/rolling
https://github.com/autowarefoundation/autoware.universe/labels/humble

I'll set up Ubuntu 22.04 next week and work in a branch.

TODO: Remove workarounds after we moved to Humble.
https://github.com/autowarefoundation/autoware.universe/pull/720

@esteve From your ROS experiences, do you have any suggestions on this?
https://github.com/autowarefoundation/autoware.universe/issues/268#issuecomment-1078430411

@kenji-miyake in my opinion, the plan sounds good. After Humble is released, we won't be supporting Rolling, right?

@esteve No, I believe we won't (at least proactively).
But if someone wants to add the Rolling support by using ROS_DISTRO macros, I think it can be acceptable.
However, it cannot be a mandatory condition for merging PRs because Rolling may collapse frequently.

Now the main branch supports both Galactic and Humble.
See https://github.com/autowarefoundation/autoware/pull/2692 for further information.


Added Not Found and Under Dev Page components

Related Issue
Closes: #113
Describe the changes you've made
Added two components under the pages folder called Not Found and Under Dev Page.
You can check it out live here, they are available under these paths, /notfound and /underdev
Type of change
What sort of change have you made:

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Unusual behaviour of my code on present UI
This PR is based on the new UI that I have been working on so it won't look good on the present UI although you check it here Not Found and Under Development
Screenshots
Here are the screenshots of how it looks on the new UI

LGTM.


Overriding object properties with union() doesn't work as described by bicep documentation

Description of the issue
Code from example https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-functions-object#example-6 doesn't result in the expected result. Property three is expected to have value c2 but Export-AzRuleTemplateData produces value c1
To Reproduce
param firstObject object = {
  one: 'a'
  two: 'b'
  three: 'c1'
}

param secondObject object = {
  three: 'c2'
  four: 'd'
  five: 'e'
}
var objectUnion = union(firstObject, secondObject)

resource taskDeployment 'Microsoft.Resources/deployments@2020-10-01' = {
  name: 'name'
  properties: {
    mode: 'Incremental'
    template: {
      '$schema': 'https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#'
      contentVersion: '<IP_ADDRESS>'
      resources: [
        {
          apiVersion: '2019-12-01'
          type: 'Microsoft.ManagedIdentity/userAssignedIdentities'
          name: 'example'
          properties: {
            taskOptions: objectUnion
          }
        }
      ]
    }
  }
}

Steps to reproduce the issue:
bicep build bug.bicep; powershell -noprofile Export-AzRuleTemplateData -TemplateFile bug.json -OutputPath bug1-export.json

Expected behaviour
            "parameters": {
                "taskOptions": {
                    "one": "a",
                    "two": "b",
                    "three": "c2",
                    "four": "d",
                    "five": "e"
                }
            }

And here is the output of az deployment group create --what-if -x Ignore --subscription <SUB-ID> -g <RG-NAME> -f bug.bicep. Note c2 as the value of properties.taskOptions.three
<SNIP>
      properties.taskOptions.five:  "e"
      properties.taskOptions.four:  "d"
      properties.taskOptions.one:   "a"
      properties.taskOptions.three: "c2"
      properties.taskOptions.two:   "b"

Error output
            "parameters": {
                "taskOptions": {
                    "one": "a",
                    "two": "b",
                    "three": "c1",
                    "four": "d",
                    "five": "e"
                }
            }

Module in use and version:

Module: PSRule.Rules.Azure
Version: 1.27.1

Captured output from $PSVersionTable:
Name                           Value
----                           -----
PSVersion                      5.1.22621.963
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.963
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

@dmgonch Thanks for raising this. Is this the same as what happens when deployed to ARM?

@BernieWhite No, ARM results match the doc. I updated the bicep to be --what-if deployable as pasted above output of the command.


Vim don't respond when start debugging

Hi,
First at all, Thank you for your hard work.
This is my first time with this plug and I'm very new user with vim, so can be a bad configuration my problem.
I do this steps:
1- Add the log file as describe in the vdebug help:
:VdebugOpt debug_file ~/vdebug.log
:VdebugOpt debug_file_level 2
2- Press F5 in vim and get "Vdebug will wait for a connection in the background" instead of  "Waiting for a connection (this message will self-destruct in 30 seconds...)"
3- Refresh the browser "F5" -> http://localhost:9000/exercise_php.php
4- Nothing change so press again F5 in vim and get -> Found connection, starting debugger
5- Nothing happen -> Press some keys -> Vim stay like "lock"
6- Refresh browser and stop the script
7- vim start to perform every clicked keys.
vdebug.log:
1 - [Debug] {Mon 31 2020 16:58:30} Closing the socket
2 - [Debug] {Mon 31 2020 16:58:30} keymapper: unmap
3 - [Debug] {Mon 31 2020 17:00:09} Closing the socket
4 - [Debug] {Mon 31 2020 17:00:09} Closing the socket
vim --version
VIM - Vi IMproved 8.1 (2018 May 18, compiled Jun 15 2019 16:41:15)
Included patches: 1-875, 878, 884, 948, 1046, 1365-1368, 1382, 1401
Modified by<EMAIL_ADDRESS>Compiled by<EMAIL_ADDRESS>Huge version with GTK3 GUI.  Features included (+) or not (-):
+acl               +extra_search      +mouse_netterm     +tag_old_static
+arabic            +farsi             +mouse_sgr         -tag_any_white
+autocmd           +file_in_path      -mouse_sysmouse    +tcl
+autochdir         +find_in_path      +mouse_urxvt       +termguicolors
-autoservername    +float             +mouse_xterm       +terminal
+balloon_eval      +folding           +multi_byte        +terminfo
+balloon_eval_term -footer            +multi_lang        +termresponse
+browse            +fork()            -mzscheme          +textobjects
++builtin_terms    +gettext           +netbeans_intg     +textprop
+byte_offset       -hangul_input      +num64             +timers
+channel           +iconv             +packages          +title
+cindent           +insert_expand     +path_extra        +toolbar
+clientserver      +job               +perl              +user_commands
+clipboard         +jumplist          +persistent_undo   +vartabs
+cmdline_compl     +keymap            +postscript        +vertsplit
+cmdline_hist      +lambda            +printer           +virtualedit
+cmdline_info      +langmap           +profile           +visual
+comments          +libcall           -python            +visualextra
+conceal           +linebreak         +python3           +viminfo
+cryptv            +lispindent        +quickfix          +vreplace
+cscope            +listcmds          +reltime           +wildignore
+cursorbind        +localmap          +rightleft         +wildmenu
+cursorshape       +lua               +ruby              +windows
+dialog_con_gui    +menu              +scrollbind        +writebackup
+diff              +mksession         +signs             +X11
+digraphs          +modify_fname      +smartindent       -xfontset
+dnd               +mouse             +startuptime       +xim
-ebcdic            +mouseshape        +statusline        +xpm
+emacs_tags        +mouse_dec         -sun_workshop      +xsmp_interact
+eval              +mouse_gpm         +syntax            +xterm_clipboard
+ex_extra          -mouse_jsbterm     +tag_binary        -xterm_save
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/uuid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time  -g -O2 -fdebug-prefix-map=/build/vim-4Pursk/vim-8.1.0875=. -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -L. -Wl,-z,relro -Wl,-z,now -fstack-protector -rdynamic -Wl,-export-dynamic -Wl,-E  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim   -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE  -lm -ltinfo -lnsl  -lselinux  -lacl -lattr -lgpm -ldl  -L/usr/lib -llua5.2 -Wl,-E  -fstack-protector-strong -L/usr/local/lib  -L/usr/lib/x86_64-linux-gnu/perl/5.28/CORE -lperl -ldl -lm -lpthread -lcrypt  -L/usr/lib/python3.7/config-3.7m-x86_64-linux-gnu -lpython3.7m -lcrypt -lpthread -ldl -lutil -lm -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -ldl -lz -lpthread -lm -lruby-2.5 -lpthread -lgmp -ldl -lcrypt -lm

php7.3 --version
PHP 7.3.19-1~deb10u1 (cli) (built: Jul  5 2020 06:46:45) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.19, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.3.19-1~deb10u1, Copyright (c) 1999-2018, by Zend Technologies
    with Xdebug v2.7.0RC2, Copyright (c) 2002-2019, by Derick Rethans

Thank you very much!

Did you set a breakpoint in vim (:Breakpoint) or did you configure php-xdebug to automatically break at the beginning of the script?

@lucc Hey, for any reason my response disappear or didn't saved here.
Yes I did :Breakpoint.
Sorry for the delay.

@Abyweinberg vdebug can't use port 9000 if you have fpm on 9000.
Could you try to configure xdebug to use 9001 and also set this in the vdebug configuration 9001 is used ?
xdebug ini setting:
xdebug.remote_port = 9001

somewhere in your vimrc if you don't yet have any vdebug settings
let g:vdebug_options = {
    \'port': 9001
\}

@Abyweinberg do you still have the issue or is it resolved?

Hi, @BlackIkeEagle thanks for ask, right now I saw your comment (trying with other port).
I move to vscode for the moment because the pressure of the task (php task "actually a work interview") and now I'am developing in Python.
Please let me check your solution in the next few days (actually I hope to check it tonight UTM +2) I'll be very glad to help.
BTW Hope you understand my not native English.

@Abyweinberg The last issue is the same as #484 - this should be fixed in the latest version.

Thank you for your help.
Have a grate day!


Roadmap ?

Hello,
I hope you're doing well. I’ve been exploring this repo. I was wondering if you’re planning to continue maintaining it? Additionally, I’m curious if you’re considering adding any new features or updates. Are you aiming to eventually release a 1.0 version?
Thanks!
Deno is yet to have a mature mqtt library thats why asking.

Hi,
thanks for asking!
Its a hobby project to me which I started with two in mind:

get to learn Typescript
get to learn Deno
I'm not using it in any production like capacity.

My plan (if I find the time) is to port it to Node.js so it will run on Node, Deno and Bun and maybe some others as well,  as everybody has Node compatability these days.  The only hard depency on Deno currently is in the Deno socket all other stuff is plain vanilla Typescript/Javascript.
Feel free to submit ideas or PR's, fork it  or borrow ideas.
Kind regards,
Hans

Btw: although not part of the standard library it is on JSR.io ;-)

Current version is 1.0.18 and it has been tested against https://github.com/eclipse/iottestware
(see https://github.com/seriousme/opifex/blob/main/bin/conformanceServer.ts)
The implementation has been hardened against potential adversarial messages (e.g. oversized, undersized, malformed etc) and protocol misbehaviour E.g. it looks for message size then reads the whole message before attempting to parse it.
Message size is capped at 2Mb and can easily be adjusted, see: https://github.com/seriousme/opifex/blob/e742c86f27217671326c507426f7f294c1117352/mqttConn/mqttConn.ts#L86
Hope this gives some insight into the robustness ;-)
Kind regards,
Hans

Current version (1.3.0) runs on both Nodejs and Deno, Bun is having some issues with the socket stream.

@seriousme Are there any plans to allow the server to have handlers that can read and do stuff with messages such as onPublish etc? I'm interested in using this in an IoT project and would need to be able to read the message contents. If you don't plan to add it but wouldn't mind having it as a feature, I could contribute the code.

Hi,
I don't have any specific plans in this direction. Can you elaborate a bit more on what you want to achieve?
E.g. if you want to add persistent storage you can already use the persistence interface (https://github.com/seriousme/opifex/blob/main/persistence/persistence.ts) to create your own storage adapter.
And if you want to use custom authentication/authorization you can supply your own handlers.
Kind regards,
Hans

Hi! Thanks for the prompt response :) I just need to be able to access the published events in my server code, since I run a kind of HTTP-MQTT gateway. As a workaround I decided to use a loopback MqttClient that just connects to localhost, but I'm having another issue - the server just seems to reject all connections. When I do console.log(conn) in my for await loop, it prints TcpConn {} but my testing MQTT client (mqttui) just reports constant "Connection refused" (I think it's ECONNREFUSED). I'm not sure if it's because I'm also running an HTTP server in the same application - do you have any ideas what could be going wrong?

Hi, best solution for a HTTP-> MQTT gateway is to have the HTTP server use an MQTT client, that way you don't need to fiddle with  the MQTT server and you can always use any generic MQTT server.
Kind regards,
Hans


copy hasExclusiveAccess pattern into ARM STREX instruction to be the …

…same as the THUMB and STREXn instructions, to fix problem I noted in #1661

With this fix
the decompile has gone from
int FUN_1003afc0(int *param_1)

{
  int iVar1;

  iVar1 = *param_1;
  *param_1 = iVar1 + 1;
  return iVar1 + 1;
}

to
int FUN_1003afc0(int *param_1)
{
  bool bVar1;
  int iVar2;

  do {
    iVar2 = *param_1;
    bVar1 = (bool)hasExclusiveAccess(param_1);
  } while (!bVar1);
  *param_1 = iVar2 + 1;
  return iVar2 + 1;
}

my issue that this fixes is moved to #2010

@simeonpilgrim in order for the issue to automatically be closed you need to use one of the keywords listed here

@astrelsky maybe the workflow is super different to those I am used to elsewhere... so I want the issues case to be closed prior to the PR being merged down? And thus someone will accept the PR if there is a case, and the case is closed?

fixes #2010

I think it has to be in the original one

interesting the issue now shows:

@simeonpilgrim simeonpilgrim linked a pull request that will close this issue yesterday
copy hasExclusiveAccess pattern into ARM STREX instruction to be the … #2005

so not sure if how I originally linked it, triggered that (thus it was enough) or how it is now linked by altering the first comment changed the nature of the linking.

interesting the issue now shows:

@simeonpilgrim simeonpilgrim linked a pull request that will close this issue yesterday
copy hasExclusiveAccess pattern into ARM STREX instruction to be the … #2005

so not sure if how I originally linked it, triggered that (thus it was enough) or how it is now linked by altering the first comment changed the nature of the linking.

It is how it is linked now. It changed after you moved it into the original pull request description/message/comment. I had initially commented that it needs to be in the initial comment but deleted it after I saw you did. Happened to check before and after so I'm certain it was just a reference before and said it will close it after the change.


No quit function

In the menu after clicking the app's icon in the panel, there is no function to quit the app.

Added a right-click quit option and ⌘+Q support in the latest update.


gio: Add a GioInfaliableFuture

Needed for https://github.com/gtk-rs/gir/pull/1397

I guess you mean Infallible :)

I guess you mean Infallible :)

English is difficult :P


[#741 subtask] support the config fields for Starwhale runtime

Current Behavior
No support
Proposed Behavior

related issue: #741
config fields:

conda
pip

https://github.com/star-whale/starwhale/pull/796


MagicComments should be applied after Prism tokenization to properly track line numbers

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[ ] I have tried the npm run clear or yarn clear command.
[ ] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[ ] I have read the console error message carefully (if applicable).

Description
The way magic comments are currently applied (before passing the code to Prism) interferes with Prism after-tokenize hook (and possibly other hooks too). I implemented a way to manually specify type names for proper highlighting:

(this is a screenshot from the webpage)
This requires me to erase each line with a specific pattern:
// custom-syntactic-tweak-that-adds-types:Vehicle

This results in magic comments being shifted.
Reproducible demo
https://codesandbox.io/s/docusaurus-magiccomments-breaks-lines-n78f0r?file=/docusaurus.config.js
Steps to reproduce
To see the problem:

Click on "Tutorial" to go to the intro doc.

How to reproduce it starting from a fresh installation:

Using prism-include-languages.js hook to Prism after-tokenize and erase any token that contains a new line
Test how // highlight-next-line works in a code block

Expected behavior
Magic comments are applied after the after-tokenize hook so that user-provided hooks work if lines are added or removed.
Actual behavior
Magic comments are applied before passing the code to the Prism tokenizer and this results in highlighted lines being shifted if a hook is used to add/remove tokens that contains new lines.
Your environment

Public source code: https://codesandbox.io/s/docusaurus-magiccomments-breaks-lines-n78f0r?file=/docusaurus.config.js
Public site URL: https://n78f0r.sse.codesandbox.io/docs/intro
Docusaurus version used: 2.2.0
Environment name and version (e.g. Chrome 89, Node.js 16.4): Brave v1.47.171 (Jan 12, 2023), Node.js v16.15.1
Operating system and version (e.g. Ubuntu 20.04.2 LTS): CodeSandbox (?)

Self-service

[ ] I'd be willing to fix this bug myself.

Not sure how easy it is to implement, but accepting a PR to experiment. We can even move this logic to a Prism hook if it works.


Can't load music list in music sticker

Instagram Version 3<IP_ADDRESS>.10
Rootless method (local patch)

bro look, we can't fix every feature, we are just doing this module to enable developer options.
basically in the last issues, it was about instagram versions.
please try to use a stable version.


Compiling vulkan shaders never ends

idk what to do, i have amd drivers on the last update.
rx580 8gb
i39100F
16gb ram at 2400mhz
I been waiting so much I think,
I tried to use the hassaku models so I don't have to download a default model from shark nodai, also I tried with default models but is the same result. if someone knows how I can fix that pls let me know :]

had same problem. i think this is normal

i think so, buy someone with 32gb of ram on the discords server told me that it takes to him like 5 minutes to compile the vulkan shaders, I have 16 so it should take 10 minutes or mores but it have me waiting 30minutos for nothing, i put it on the SSD but i didn't worked,

I also have an RX580 and 16GB of RAM and cannot get passed this part, but mine doesn't freeze forever. When it gets to compiling Vulkan shaders, I can check the RAM usage with free -h and see that it is constantly climbing until it hits 16 GB then it segfaults (swap space makes no difference). Maybe 16GB is just not enough?

RX580 8GB, Win10, same thing. RAM usage doesn't even come 100% on 16GB RAM, it's normal.
GPU usage max 30% in the process.


🌱 Correct the release package path

Summary
The default working directory was removed in https://github.com/open-cluster-management-io/managed-serviceaccount/pull/100/files#diff-29d508c8d0fc8d2fc3ea8e21d26ed76072f2de9d4a031e3307d41711e219bb76L15-L17, so the path should be changed accordingly
Related issue(s)
Fixes #

/cc @xuezhaojun

/lgtm


Code didn't upload

I was compiled the code then the massage is successful but when i am upload the code it's said upload failed please tell me whats the reason for this please 🥺

Can you make sure you open the "firmware" folder in VSCode and then do a build and upload?

Ok i was tried but still it's said failed friend what is the reason you think please tell me please 🥺

Can you expand the terminal window a bit so that the error is visible?

Yes but i didn't understand error friend

Try editing platformio.ini and remove the two lines:
upload_port = /dev/cu.SLAB_USBtoUART
monitor_port = /dev/cu.SLAB_USBtoUART

Yes but i didn't understand error friend

I was edit it but it doesn't upload please help me please 🙏🥺

So the error is saying that it can't find your device on /dev/cu.SLAB_USBtoUART
That's because your device is probably on a different port. So remove the two lines from platform.io and try again and see what error you see.
There's some good instructions here on working out what COM port your device is on when using windows: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/establish-serial-connection.html

Yes you right there was a port error now I install silicon lab driver and then it's recognize it but some time it  recognize it and some time it doesn't recognize it

problem tab

Problem tab

Now another error occur are you know a fix for this

Again a problem are you know a fix

Finally i fix it thanks a lot friend error is port not selected 🙏🙏🙏 thanks a lot agin friend

Thanks a lot. please help me in future errors ok friend thankyou


python311Packages.pytest-ansible: 3.0.0 -> 3.1.5

Changelog: https://github.com/ansible-community/pytest-ansible/releases/tag/v3.1.5
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 232730 run on x86_64-linux 1

2 packages built:

python310Packages.pytest-ansible
python311Packages.pytest-ansible


kernel/timeout: ensure next_timeout() returns non-negative number

For the MAX() operation to be performed correctly so that a zero
timeout is returned when a timeout is in the past, both of its
parameters should be signed, for otherwise 'to->dticks - ticks_elapsed'
would always be treated as greater than or equal to 0 in an unsigned
comparison. Let's cast the second parameter accordingly.
Fixes #28414
Signed-off-by: Vincent Wan<EMAIL_ADDRESS>

Closing due to changes from #28034.


Support running tests optimized by AOT

Feature description
See https://github.com/micronaut-projects/micronaut-gradle-plugin/pull/280#issuecomment-957181453
Currently we cannot run tests in "AOT mode", because each test annotated with @MicronautTest will create its own application context, so in theory we have to run one AOT phase per test.

ping on this: would also be a good idea to run the GraalVM agent against the optimized app JAR instead of the regular one.


[eloquent backport] Set clock type if Marker frame_locked is true (#482)

Backport #482 for Eloquent

Linux
Linux-aarch64
macOS
Windows

Compiler/cmake warnings are expected.

Can we get this merged @jacobperron ?
FYI @mjcarroll

Sure, I think this just needs a review.


Spinnaker inline script in values

What this PR does / why we need it: This allows you to configure halyard scripts, configmaps, and secrets in the values.yaml files. This is useful for fully configuring halyard from the values file. I've included a sample values_saml.yaml file to help other people configure saml auth.
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/ok-to-test

/lgtm

/approved


Add onerror as an option

It'd be nice to be able to do custom error handling on occasion, this PR allows an onerror function to be passed to .parse().

See this WordPress ticket for a use case.

this is not a bad idea but I don't understand the use case or the reason and there is no test with this change so it won't land as it is.
Do you mind elaborating a little bit more what is the problem  you have and what are you trying to solve? The onerror is something that should happen, and was thought to happen, only as network failure, not on client-side operations. Please try to let me understand what is going on, thank you

OK, I've added a test and verified that everything else is fine.  Apologies I  couldn't accept this PR witohut tests, the version 1.4.2 supports the onerror callback passed through options.

Thanks, @WebReflection! I tried writing a test, but I was getting a bit stuck on the async nature of triggering the error. :-)

very dirty approach indeed but it does what it's supposed to do ;-)
https://github.com/twitter/twemoji/blob/gh-pages/test.js#L539-L555


Optimizing Dockerfile

Reducing the image size by removing unnecessary dependencies.

It looks like this is no longer relevant.


Hide resolved comments

It would be nice to filter the comments tab to show only unresolved comments / conversations.

Looks like a dupe of #339.

Closing as dupe of #339.


MI - DEVELOPER section (Troubleshooting Integration Studio)

Updating content, links, and images.[1]
Update yaml.
See preview on netlify[2].
[1] https://github.com/wso2/docs-ei/blob/master/en/micro-integrator/docs/develop/troubleshooting-WSO2-Integration-Studio.md
[2] https://wso2docs-configurationcatalog-3.netlify.com/develop/troubleshooting-wso2-integration-studio/

Done. Need Review.

@dakshika - Any thoughts on this section? do we need to add any more content?

Done


fix: delete existing file when uploading image

Checklist
fixes: #45

[x] run npm run test and npm run benchmark
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[x] commit message and code follows the Developer's Certification of Origin
and the Code of conduct

I will take a look in the week, but you must add a test to prove that previous task image was indeed deleted.


Double link in See Also to Administration

There is Administration in the See Also two times with same link (https://docs.microsoft.com/en-us/dynamics365/business-central/admin-setup-and-administration) . It is confusing...

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 58d0c2b2-6293-9604-440b-987e32fac282
Version Independent ID: 541e941e-2c6c-3f31-b998-17be0815c1ad
Content: Overview of Tasks to Set Up Business Central - Business Central
Content Source: business-central/setup.md
Service: dynamics365-business-central
GitHub Login: @edupont04
Microsoft Alias: edupont

Good catch! It will be fixed in Monday's update.


[Feature Request] Option to not remove containers upon completion (Act equivalent: --reuse)

Feature Summary
If a Github Action fails, it is often very useful to connect into the container that was running the action to check status of files, do some interactive debugging, etc. to find out what happened rather than trial-and-error of running the containers.
act has an option --reuse which simply does not remove the containers after they are executed, a similar option should be added for this runner
Great work! This is really impressive.

--keep-container should keep docker container, workdir and container network, therefore also needs to recreate runners after a job finishs.
These feature may sometimes loose jobs, if you are have more than --parallel jobs. Althought it seems to work for me on windows without that problem.
PS C:\Users\Christopher\bug_29> docker ps
CONTAINER ID   IMAGE                            COMMAND               CREATED          STATUS          PORTS     NAMES
4c83c3e0d9fe   catthehacker/ubuntu:act-latest   "tail -f /dev/null"   50 seconds ago   Up 35 seconds             c31b1d937a16411bb6f1fd4b663f12b1_catthehackerubuntuactlatest_0b2343
f9e0268d6114   catthehacker/ubuntu:act-latest   "tail -f /dev/null"   50 seconds ago   Up 35 seconds             57846543eefd43a4a9a33530295f48b3_catthehackerubuntuactlatest_ccb40a
290176a9d457   catthehacker/ubuntu:act-latest   "tail -f /dev/null"   50 seconds ago   Up 35 seconds             dddce8ee4c3441c6b7be393522e715a7_catthehackerubuntuactlatest_9f7e6a
d20b275f8188   catthehacker/ubuntu:act-latest   "tail -f /dev/null"   50 seconds ago   Up 36 seconds             c5c54a35ab284c10b2e289d74b5f8c82_catthehackerubuntuactlatest_357674
00ce6c277103   ubuntu:latest                    "tail -f /dev/null"   6 minutes ago    Up 6 minutes              d18256beaccf4f45b3527dedde735c30_ubuntulatest_4e4749
8d076eaff2cc   ubuntu:latest                    "tail -f /dev/null"   6 minutes ago    Up 6 minutes              7ee3450c7eba4ca8b6009e9ae71cfadb_ubuntulatest_1fabf3
7e4e7ccb4c90   ubuntu:latest                    "tail -f /dev/null"   6 minutes ago    Up 6 minutes              dc9ee34c112440b9844182554aa7bc5d_ubuntulatest_31da63
46edb85bc7c4   ubuntu:latest                    "tail -f /dev/null"   6 minutes ago    Up 6 minutes              e8be6c27d9534301900f54389fd180f5_ubuntulatest_0c7b6e


Force install of specified docker version, fixes #295

This allows Ubuntu/Debian to downgrade Docker version if
a newer version is installed, instead of failing.

This needs more work to allow deployment on CentOS

tested ok :)


Changing the "# References" to display before the set of attributes(if any)

Fixes: #429
To display the # of references before the set of attributes, the provideCodeLens must return a range for the attributes of the node. So changed the omnisharpLens object to contain two ranges - one the actualRange of the node ( to be consumed by the resolveCodeLens method) and the other attributeRange that will be consumed to determine the position to display the references.
Also added attributeSpantoRange helper to convert span to a range in the document.

Omnisharp-roslyn side : https://github.com/OmniSharp/omnisharp-roslyn/pull/1075

The "run test" and "debug test" now shows up as a separate codelens. Do we need to shift that as well alongside the reference codelens.

This is marked as "Blocked on OmniSharp".
What's blocking this? I want this!

it was "Blocked on OmniSharp" because it required a corresponding change in the Omnisharp language server.
however, it was decided that this change will not be implemented for reasons listed in the discussion above

That's very disappointing to hear ☹. I've been wanting this to be fixed for ages, but haven't voiced my frustration until now. Can't we just have a configurable attribute line limit with a default value of 0? If the number of lines occupied by attributes is above that limit, # references is displayed as it is now. This would allow the same behavior as it is now by default yet still allow people like me to configure this the way we think is best for our use cases 😃


Model->fill() ignores $fillable property in unit tests

Following #1181, #6816, #8399 and so on... I used @taylorotwell proposed solution to explicitly call the boot method on setUp().
I have a user controller with the following validation rules:
public function store(Request $request)
{
    ...
    $this->validate($request, [
        'name' => 'required',
        'email' => 'email|required|unique:users',
        'password' => 'confirmed|max:32|min:8|required',
        'roles' => 'exists:roles,id|required',
    ]);

    $user = new User();
    $user->fill($request->all());
   ...
}

My User.php model defines the fillable properties as:
protected $fillable = ['name', 'email'];

To pass the confirmed validation, I have to send both password and password_confirmation fields in the POST request.
During development everything works fine, but in unit tests I'm getting a database error. It tries to insert data into a password_confirmation column. It's like it ignores the $fillable array.
Is there some other model method I have to call (like the boot() function) before running the tests?
Thanks!
Edit
Reading the Model.php source, I've found that someone is calling Model::unguard() https://github.com/laravel/framework/blob/5.1/src/Illuminate/Database/Eloquent/Model.php#L2180 after the setUp() function and before the test. If I call User::reguard() at the beggining of the test it passes, but (I don't know why), the unguard() and reguard() functions get called multiple times and the test gets really slow.

Try to use $guarded. The $guarded property should contain an array of attributes that you do not want to be mass assignable.
http://laravel.com/docs/master/eloquent#mass-assignment

I tried using $guarded but with same results (also $guarded isn't a good idea since it will try to add everything in the POST request unless it is blacklisted there).
I believe this has something to do with #1181, maybe I'm missing a call to register some handler needed by Laravel.

Found the problem: the base seeder in v5.0.x only called Model::unguard() (https://github.com/laravel/laravel/blob/v5.0.22/database/seeds/DatabaseSeeder.php#L15) while v5.1.x was updated and added a call to Model::reguard() (https://github.com/laravel/laravel/blob/v5.1.0/database/seeds/DatabaseSeeder.php#L19) (I was using v5.0.22).


Adding dbhagen as a contributor for and with the pulumi-fortios provider

This PR will create a new repository for the Fortinet FortiOS Provider.

Sorry about that, @ringods. Updated.


Add chainerx.fmod

Add chainerx.fmod.
TODO: Add tests

@take-cheeze The travis tests seem to show core dumped. What could be causing this?

@aksub99 Seems some memory access error happened like SIGSEGV.

Jenkins, test this please!

Jenkins CI test (for commit fd3f31e3bd38c843c2311a121f82afd3140ef714, target branch master) failed with status FAILURE.

CI is failing for some other reason so will wait a while

Jenkins, test this please!

Jenkins CI test (for commit fd3f31e3bd38c843c2311a121f82afd3140ef714, target branch master) failed with status FAILURE.

@take-cheeze This pull-request is marked as st:test-and-merge, but there were no activities for the last 3 days. Could you check?

ChainerCI, test this please!

Jenkins CI test (for commit fd3f31e3bd38c843c2311a121f82afd3140ef714, target branch master) failed with status FAILURE.

Seems this broke the build. Will revert temporary


⚠ Bofrost.at has degraded performance

In 6660e61, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1083 ms

Resolved: Bofrost.at performance has improved in 391ef02.


Unused parameter in corsika_runner

https://github.com/gammasim/gammasim-tools/blob/8cdb37a97cf9c4fcf37ed0380927c28e4735cb3a/simtools/corsika/corsika_runner.py#L84
This parameter is set in the simulator, but is not actually used anywhere in the CORSIKA runner. It's seems weird to simply remove it. Any ideas @GernotMaier?

CorsikaConfig has an option to load CORSIKA parameters from a yaml file, but this is not set in corsika_runner.
This needs a bit more investigation to understand better if we want that option or not (if not, than we should remove the code consistently also in corsikaconfig.
I assigned the issue to myself and will look into it.

corsika_parameters_file is used (implemented in one of the merge request listed above). I therefore close this issue.


Add support for ingressClassName to Helm chart

Also rewrite API version handling according to https://github.com/brigadecore/charts/pull/92.
closes #21
Signed-off-by: Christian Zunker<EMAIL_ADDRESS>

/brig run


Codeunit 1279 GenerateHashBytes returns an empty string for an empty InputString

Codeunit 1279 GenerateHashBytes returns an empty string for an empty InputString but muste be SHA256("") =
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Availability update: We will publish a fix for this issue in the next update for release 20.


Clearing cached data - Go

Is there a way to clear cache?

I second what @levinit said. I am closing this issue.


Who can tell me how to start this game?

I have configured the operating environment.

Have you checked the wiki?
I am not sure what your problem is exactly, a little more information would be useful

I meant that I wanna play this game on an interface, such as some GUIs.
Otherwise, can u give me some advice about the entry of this project.
I am not goot at python, and I really wanna play it before researching the code. ^_^

This page on the wiki explains how to play against a model using GoGui.

Very thanks for your reply, and I am using GoGui, stdout: GTP engine ready.
But the process went down when I type "play" or some other keywords, do you know what happened.
this is the log:
Using TensorFlow backend.
GTP engine ready
play
Traceback (most recent call last):
File "greedy_player_gtp.py", line 13, in
run_gtp(player)
File "/Users/hemingwei/Documents/Project/RocAlphaGo-develop/interface/gtp_wrapper.py", line 152, in run_gtp
engine_reply = gtp_engine.send(cmd)
File "/Library/Python/2.7/site-packages/gtp.py", line 151, in send
message_id, getattr(self, "cmd_" + command)(arguments))
File "/Library/Python/2.7/site-packages/gtp.py", line 208, in cmd_play
move = parse_move(arguments)
File "/Library/Python/2.7/site-packages/gtp.py", line 93, in parse_move
color_string, vertex_string = (move_string.split(" ") + [None])[:2]
AttributeError: 'NoneType' object has no attribute 'split'

The demo code seems need two files -"my_model_spec.json"/ "weights.00999.hdf5".
So lazy me used tests/test_date/minimodel.json and tests/test_date/hdf5/random_minimodel_weights.hdf5 as replacements of them.
Is there something wrong?

it seems you are using an older version, please make sure you are using the newest develop branch.
(your fork is is behind quite a bit)
i have to urge you to read the wiki, this project is till under development and it is better to understand a little of how it works when using it, also you would have found where you can find pre-trained weight and corresponding model files;-)


vendorVersion is not getting updated in the log

https://github.com/kubernetes-sigs/ibm-vpc-block-csi-driver/blob/master/cmd/main.go#LL87C69-L87C82 i snot working as expected

Hi @arahamad
Can you please assign this issue to me (id: https://github.com/Sony-Neyyan)


feat(tpc): build-time third-party-capital composables

Still WIP.
This PR re-introduce TPC as dependency and not type provider. TPC will be used to generate all composables (and components if possible).
It's very messy right now. But feel free to comment it.
Composables and components will be generated at USER build-time and not at @nuxt/scripts. TPC will be declared as a peer dependency so it will be up to users to update TPC to the latest version (We can also add a version check from npm later.) . This way, users will always have the "latest" TPC independently from @nuxt/scripts releases.
steps:

[x] review from Aurora team for the implementation
[x] clean it
[x] move TPC to peer-deps

optionnal:

[ ] refactor with magic-ast
[ ] do it for embed components

would love a follow up with your comment: "We can also add a version check from npm later."
That'll be great to show a message to the user, if they're using an outdated version of tpc

I think this is good for a first implementation. I'll probably open another PR for internal DX to ease the developement with TPC.

I'm still not convinced TPC in its current format will be worth maintaining with Nuxt Scripts in the long term but I'm happy to move this forward for the time being once comments are addressed.
Either way this is a nice solution to avoiding the runtime of TPC, great work @huang-julien :clap:


Edit pipeline name missing on Firefox

Describe the bug
On Firefox the edit name of the pipeline does not exist.
To Reproduce
Steps to reproduce the behavior:

Go to pipelines
Click on Edit pipeline

Expected behavior
There should be the possibility to rename the pipeline.
Screenshots

Desktop (please complete the following information):

OS: OS Monterey
Browser firefox
Version 106.0.1
mage-ai = 0.6.3

Additional context
Add any other context about the problem here.

This might be due to a malformed pipeline YAML file.
Can you go into default_repo/pipelines/blue_river/metadata.yaml and share the contents?
Change default_repo to the name of your Mage project.

It is an empty pipeline:
name: blue river
type: python
uuid: blue_river

Try changing it to this:
name: blue river
type: python
uuid: blue_river
blocks: []
widgets: []

The issue is truly with Firfox, on Safari the option exists

Thanks for reporting. We'll debug this ASAP. Sorry for the inconvenience.

Can you also try using the latest version 0.7.5?

Tested with 0.7.5 and it has the same behavior.

Will debug on our end, sorry for the inconvenience.

Hi @acirtep, sorry for the delay, but this issue should be addressed in the latest version (v0.8.5). PR: https://github.com/mage-ai/mage-ai/pull/2058


BUG: Bell icon is not functional

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
When I click the bell icon , nothing happens Thus it is not functional which makes the user experience bad.

Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@DownOnCoffee
Notification section

@saurabhsingh720 has the notification system been developed on the backend?

@DownOnCoffee no yet.


Couldn't able to view users through console App

Describe the issue:
Couldn't able to view users through console App in tenant mode
How to reproduce:

Created a tenant through the management console
Login to console app using the created tenant
Created a secondary user store.
Go to users tab.
Again go to list user store tab
Now again Navigate to users tab blank page is shown. No error logs in the back end
Saml tracer is as below.
Restart the server solves this issue.

SAML-tracer.txt
Expected behavior:
Navigation should happen successfully.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: [IS-5.11.0-beta2-SNAPSHOT]
OS: [Linux]
Database: [H2]
Userstore: [JDBC]

Seems https://github.com/wso2/product-is/issues/9790 fixed this issue. Need to verify after the release and close the issue

@thivi please verify and close.

I verified this issue in 5.11.0-beta3-SNAPSHOT and it is working fine.


update changelog; update npm dependencies; run test on 4th node

Coverage remained the same at 91.978% when pulling 9f2a0d0456f432e1b32844a3291a87f8c7789ca8 on boguslavsky:update-changelog into e786962828bd523c178143dff03b7f5ff61350df on exonum:master.


sorting out compat issues

closes #42 #43 #44 #45 #46 #47 #48 #49 #50 #51 #52 #53 #54 #55

Codecov Report

Merging #56 (5bb4f60) into main (1472c78) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main      #56   +/-   ##
=======================================
  Coverage   96.46%   96.46%
=======================================
  Files          10       10
  Lines         622      622
=======================================
  Hits          600      600
  Misses         22       22

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more