proposal: net/url: implement TextMarshaler/TextUnmarshaler interfaces for url.URL

In order to be able to pass url.URL variable to flag.TextVar(&url, ...), url.URL type must implement encoding.TextMarshaler and encoding.TextUnmarshaler interfaces.
This approach was suggested here instead of making a dedicated flag.URLVar function in flag package.

I think this would be good, but is it a breaking change? Right now, the output of this code
	u, _ := url.Parse("http://example.com")
	b, _ := json.Marshal(u)
	fmt.Println(string(b))

is
{
 "ForceQuery": false,
 "Fragment": "",
 "Host": "example.com",
 "Opaque": "",
 "Path": "",
 "RawFragment": "",
 "RawPath": "",
 "RawQuery": "",
 "Scheme": "http",
 "User": null
}

I think it would be better if the output were "http://example.com" but maybe someone somewhere would miss the old output?

@carlmjohnson nice catch!
I guess there are 2 options:

Make a breaking change since url.URL typically is not used as JSON(maybe only for debugging/logging purposes)
Implement explicitly json.Marshaler and json.Unmarshaler interfaces on url.URL as well to maintain backward compatibility

what are next steps for this? should I wait for more comments/suggestions/concerns?
should I wait for proposal to become accepted before I can implement it?
thank you.

Proposals need to be accepted before the change will be accepted, see proposal-process

If you have spare time you could implement it now, but it won't be reviewed and merged until after the proposal has been approved and the code tree is open. This is a quiet week for the Go team: https://groups.google.com/g/golang-dev/c/EDstQLuReWE/m/s7bR1dfmAQAJ After the quiet week, the proposal will probably be formally evaluated and eventually get a decision in a few weeks. There's a proposals team that looks at the open proposals and moves them towards a decision, although it can vary exactly how long that process takes. (See https://github.com/golang/proposal.) Once that happens, assuming the proposal is accepted, a commit can be accepted and merged during the next "development work" phase of the release cycle. (See https://github.com/golang/go/wiki/Go-Release-Cycle.) That won't be until August, unfortunately.

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

It seems like JSON decoding the { } form might still work since that's not a JSON string, so it won't try the TextUnmarshaler. So an old encoding might be readable by a new Go where URL implements these methods. The reverse would not be true.
Have we decided before whether this is OK? I seem to remember JSON encoding of IP addresses used to be base64 byte encodings, but I think we decided that was just so broken we could fix it.
Not changing the JSON seems like a big inconsistency too since I assume the goal here is to get better JSON support for URLs (in addition to flag support).

This proposal is a duplicate of a previously discussed proposal, as noted above,
and there is no significant new information to justify reopening the discussion.
The issue has therefore been declined as a duplicate.
— rsc for the proposal review group


feat(snap-rebuild): add io-engine controller api

Adds simple unit test to ensure api is working.
More will follow when the api is either exported via gRPC or through component/integration level testing.

@tiagolobocastro , should we call it TerminateSnapRebuild instead of DestroySnapRebuild ?

bors merge


QBO - "must categorize all expenses" toggle is off and Tags are not imported

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

Version Number: 1.4.71-4
Reproducible in staging?: Y
Reproducible in production?: Unable to check
Found when validating PR : https://github.com/Expensify/App/pull/41513
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Precondition: Log into New Expensify using an account that is on the accounting beta list

Go to categories page. Check that you see default categories
Go to More Features page > Enable Tags feature
Go to Tags page. Check that you see nothing
Create a tag. Make sure you see the newly created tag.
Go to workspace settings page -> More Features -> Enable Accounting
Go to Accounting page -> Connect to QBO
Go to the Categories page and check that you see the imported categories > Click Settings button the categories page
Go to to the Accounting page -> Import
Go to the Tags

Expected Result:
Step 7. "must categorize all expenses" toggle is on
Step 8. Customers (or locations or classes) are imported as tags
Step 9. You see some tags (you should not see the tag you created before)
Actual Result:
Step 7. "must categorize all expenses" toggle is off and locked
Step 8. Customers (or locations or classes) are Not imported
Step 9. You see the tag you created on step 4
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/1c873506-e062-4cd5-ac14-bf12b3d2cded

View all open jobs on GitHub

@jliexpensify I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

cc @hayata-suenaga @aldo-expensify, is this a blocker? taking a look at the code it seems expected here that the toggle will be disable if we're connected to an accounting system https://github.com/Expensify/App/blob/e0b6a06d2f34f35cda96ccc4d05252ede111c732/src/pages/workspace/categories/WorkspaceCategoriesSettingsPage.tsx#L51

I think the QBO stuff is behind a beta, no? Let's remove the blocker.

I tried to reproduce the three issues reported here, but I couldn't.

Step 7. "must categorize all expenses" toggle is off and locked

The toggle is on and locked as expected.

Step 8. Customers (or locations or classes) are Not imported

The classes and customers are imported as expected.

Step 9. You see the tag you created on step 4

I couldn't see the tag I manually created after connecting to accounting software

The bug is partly fixed. The toggle part is still repro ('Members must categorize all spend' toggle still off and locked)
https://github.com/Expensify/App/assets/43996225/d661a78e-4add-4f7e-a588-a4a741376530

@kavimuru
I just realized that when you click Settings button on the Tags page, the Not-Found page is displayed for a while. Is this issue being tracked somewhere else?

On Tags import:

Support for MultiTags import isn't done yet and I think that's probably messing up importing and displaying the tag lists imported: https://github.com/Expensify/App/pull/41351
The Tags menu item isn't appearing in the LHN when you connect to QBO, but it should be because Customers and Classes are imported by default. @hayata-suenaga @aldo-expensify I feel like I've asked about this in a number of places really, but it would be good to nail down where it's being taken care.

As for the required categories toggle, I can't repro that:

The Tags menu item isn't appearing in the LHN when you connect to QBO, but it should be because Customers and Classes are imported by default. @hayata-suenaga @aldo-expensify I feel like I've asked about this in a number of places really, but it would be good to nail down where it's being taken care.

@aldo-expensify, could you confirm that, in this issue, you accounted for the situation when the default configuration already satisfies the condition below:

[DONE] When the admin choose to import Classes, Customers/Projects, or Locations, enable the Tags feature on the backend so that these entities can be imported as tags to New Expensify.

For the bug (somewhat unrelated) I found while reproducing the original issue, the issue is apparently hard to reproduce.
It might have been the result of the backend fire this week. Please let me know if you encounter this issue (Not found page briefly displayed after a while) again.

The Tags menu item isn't appearing in the LHN when you connect to QBO, but it should be because Customers and Classes are imported by default. @hayata-suenaga @aldo-expensify I feel like I've asked about this in a number of places really, but it would be good to nail down where it's being taken care.

@aldo-expensify, could you confirm that, https://github.com/Expensify/Expensify/issues/390731, you accounted for the situation when the default configuration already satisfies the condition below:

ohh, I think initial case was not covered because I added that logic to the Auth command UpdatePolicyConnectionConfiguration, and that command is not used until the user start changing settings manually.
I think we can fix this here: https://github.com/Expensify/Web-Expensify/pull/41908

Testing again, I don't see that "Customers and Classes are imported by default". Do we need to correct our defaults?

We do enable Classes. Customer/Projects and Locations to be imported by default.

Just to confirm on this.. in OldDot, we enable Classes & Customer/Projects by default, but not Locations. We should maintain that consistency, is that what you're saying?

I think we can fix this here: https://github.com/Expensify/Web-Expensify/pull/41908

Also, nice! Looking forward to getting that one fixed 👍

We do enable Classes. Customer/Projects and Locations to be imported by default.

Just to confirm on this.. in OldDot, we enable Classes & Customer/Projects by default, but not Locations. We should maintain that consistency, is that what you're saying?

Yes, I made a mistake, Locations is not enabled by default

Sounds good!

Not overude. A fix has been merged

Looks like this was deployed, @youssef-lr should we close this, or did you want Applause to re-test?

@jliexpensify it's only been deployed to staging, we can close once it hits production.

Ah yes, you're correct - apologies!

This one just hit production, so closing it out!


Updating setting constants from outside

Hello,
I am trying to update settings from where this library is called.
<?php
include('mailchimp-api-3.0-php/vendor/autoload.php');

$api_key = '123abc123abc123abc123abc-us0';
$list_id = '132465789';

if (!defined('VERIFY_SSL')) {
    define('VERIFY_SSL', false);
}

$mailchimp = new Mailchimp($api_key);

$post_params = array(
	'email_address' =><EMAIL_ADDRESS>	'status'        => 'subscribed'
);
$response = $mailchimp->lists($list_id)->members()->POST($post_params);

So, if constants can be updated from construtor, it can be more helpful.

I can definitely see the utility in being able to edit these programatically. I can look into an implementation. That said this would likely be a move away from constants since these sort-of imply they are not changeable at run time.

Addressed in 3.0.0


Testing and debugging chapter

It would be beneficial to include a dedicated chapter discussing testing frameworks such as Jest and Mocha, as well as covering unit testing, debugging techniques, and browser developer tools.

i want to work on this

i want to work on this

Hi @NextThread , thanks for your interest in writing this chapter. I've assigned you this chapter. Let me know if anything is needed.

Thanks @sumn2u .
Sure

Hi @sumn2u I would like to work on this issue and add value to the content, so if possible could please assign me this issue.
Thanks !

i want to work on this

Hi @sumn2u I would like to work on this issue and add value to the content,

Hi, If this word is still available, i will like to work on it

Hi, If this word is still available, i will like to work on it

Hi @ichie-Ozor , thanks for your interest in writing this chapter. I've assigned you this chapter. Let me know if anything is needed.

you know am new to this, am supposed to clone the repo and work on it then push right?

you know am new to this, am supposed to clone the repo and work on it then push right?

Yes.

OK. I can see that it is a book and am supposed to contribute on unit testing. I have written an article on unit testing.

I want to contribute

I want to contribute to this book..

I want to contribute to this book..

I want to contribute to this book!

I want to contribute to this book!

Hi @ashikadsilva , thanks for your interest in writing this chapter. I've assigned you this chapter. Let me know if anything is needed.

Hii @sumn2u  can you please assign this issue to me I want to contribute to this.

hey @sumn2u can you please specify which chapters and topics to include in this.

@Kritika745  Well most of the chapter described in this issue have already been introduced, it would be fantastic if you could provide a more in-depth explanation of debugging techniques.
https://github.com/sumn2u/learn-javascript/blob/main/en/miscellaneous/debugging.md

Can you please assign this to me , I would like to contribute to this book also


Auto retry failed downloads - fixes #100

solves #100

Codecov Report
Attention: Patch coverage is 40.00000% with 21 lines in your changes are missing coverage. Please review.

Project coverage is 39.52%. Comparing base (a9b1046) to head (bc29000).

Files
Patch %
Lines

aoget/view/app_settings_dialog.py
0.00%
9 Missing :warning:

aoget/web/downloader.py
66.66%
5 Missing :warning:

aoget/view/main_window.py
0.00%
3 Missing :warning:

aoget/controller/downloads.py
50.00%
2 Missing :warning:

aoget/controller/main_window_controller.py
0.00%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #175      +/-   ##
==========================================
+ Coverage   39.49%   39.52%   +0.02%
==========================================
  Files          59       59
  Lines        4294     4324      +30
==========================================
+ Hits         1696     1709      +13
- Misses       2598     2615      +17

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


remove containerd proxy config

as we do the containerd proxy config via kubeadm and the build-in config overwrite our own config we have to remove it.
Signed-off-by: Mario Constanti<EMAIL_ADDRESS>

@bavarianbidi Do we know whether they will remove this from the upstream repo?

@bavarianbidi Do we know whether they will remove this from the upstream repo?

during the last session we had with them, they mentioned that this might be something they want to achieve in the near future to allign with other providers.


Add Megaservice support for MMRAG

Description
Add support for upcoming MMRAG VideoRAGQnA usecase in GenAIExamples, the PR is under developping.
Issues
List the issue or RFC link this PR is working on. If there is no such link, please mark it as n/a.
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)
[ ] Others (enhancement, documentation, validation, etc.)

Dependencies
List the newly introduced 3rd party dependency if exists.
Tests
Describe the tests that you ran to verify your changes.

@tileintel Hello Tiep, I raise this PR for my megaservice. It's independent from you megaservice, just want to let you know. Thanks

@chensuyue  Hello Suyue, does this change requires additional test script/function? If yes, where to add?

@ftian1 @chensuyue @ZePan110 Hello, anyone has comment on this one?

@chensuyue Hello Suyue, does this change requires additional test script/function? If yes, where to add?

please add unit tests to improve the code coverage.

@chensuyue Hello Suyue, does this change requires additional test script/function? If yes, where to add?

please add unit tests to improve the code coverage.

No problem. Where should I add it, or do you have any references, for example the unit test for other gateways?

@chensuyue Hello Suyue, does this change requires additional test script/function? If yes, where to add?

please add unit tests to improve the code coverage.

No problem. Where should I add it, or do you have any references? I didn't saw the unit test for other gateways.

https://github.com/opea-project/GenAIComps/tree/main/tests/cores/mega

Test script added at tests/cores/mega/test_service_orchestrator_with_videoragqnagateway.py.
Would you help to review and merge the code? @lvliang-intel @ftian1 @hshen14  Thanks a lot

Per Chang, Hanwen's requirement, update related code structure based on PR #625

Rebase the changes per @letonghan 's request, will wait until #625 is merged

Hello, @XuhuiRen @kevinintel  the CI is all passed, could you help to merge the code?  We have another PR in example repo depending on this, I’m afraid we don’t have enough time to wait until the Reorg changes merged.


Why store only path and not location with all the props?

First of all, thanks for compact and simple thing! Could you tell, what's the motivation beside storing only 'compacted' path string and not the whole location object? It would save users (yes, like me) from manually parsing url string for query params.

You don't need to parse it for query params. Just access it on this.props in the routing component. react-router gives everything you need to use it fine without redux. Don't rely on redux to use react-router!
We store the string for 2 reasons: 1. the app state should always be 100% serializable and plain objects, so we don't know if react-router will ever put something non-serializable in there. 2. when changing the path, the user should be able to just supply a string, and if we stored the location we'd have to parse the string into a location object ourselves, and react-router doesn't expose a stand-alone function for doing that.

Wow. Looks like a thing to highlight in docs — didn't knew about it.

@jlongster what would then be a good way to, from an action creator, call updatePath and only change the path part while keeping the same search string? In this case you would manipulate the path string? If using the useQueries history enhancer it would be great to be able to use and pass the query object along to update the path.


detect skill folder

I think that might be overkill. It should always use the assistant's configured skill folder, unless the user overrides it with the --folder param.


Install spotless plugin for the sdk

Problem

Solution

Alternatives
No response

will be tracked by https://github.com/hashgraph/hedera-sdk-java/issues/1669


Support virtual attributes for select

We are starting to push more virtual attributes into the select clauses.
This teaches select how to use virtual attributes.
Have not found an elegant way to introduce this to rails. Working on it.
class Disk
  virtual_delegate :used_disk_storage, :arel => (-> { ... })
end

ems = ExtManagementSystem.first
ems.hardware.disks.select(:id, :used_disk_storage).map(&:used_disk_storage)

Backported to Euwe via https://github.com/ManageIQ/manageiq/pull/14167


Fix path inside RPM & allow expansion to occur before other steps

Quoting in the bash prevented the shell from globbing. Now resolving the actual RPM name early.
The location x86 binaries changed from 'openshift' to 'openshift-clients'

@jupierce  the package name in 4.2 is openshift-clients, the package in 4.1 is still openshift (RPM name is the same in both cases) -- both going to still work?

Nice catch! Would not have worked on 4.1. Updated to support different paths in the RPM.

seems legit


AttributeError: module 'pkgutil' has no attribute 'ImpImporter'. Did you mean: 'zipimporter'?

Describe the bug
I got this error after trying to install a package using the Marimo tool for installing packages. Related but not the same as:

#2498

Environment
{
  "marimo": "0.9.1",
  "OS": "Darwin",
  "OS Version": "24.0.0",
  "Processor": "arm",
  "Python Version": "3.12.0",
  "Binaries": {
    "Browser": "129.0.6668.90",
    "Node": "v22.4.1"
  },
  "Dependencies": {
    "click": "8.1.7",
    "importlib-resources": "missing",
    "jedi": "0.19.1",
    "markdown": "3.7",
    "pygments": "2.18.0",
    "pymdown-extensions": "10.11.2",
    "ruff": "0.6.9",
    "starlette": "0.39.2",
    "tomlkit": "0.13.2",
    "typing-extensions": "missing",
    "uvicorn": "0.31.0",
    "websockets": "12.0"
  },
  "Optional Dependencies": {}
}

Code to reproduce
cd /tmp
mkdir marimo-venv
cd marimo-venv
python -m venv venv
source venv/bin/activate
pip install marimo
marimo new

Then:
import llm

And ask it to install that package.

Here's the full traceback:
ERROR: Exception:
Traceback (most recent call last):
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/cli/base_command.py", line 160, in exc_logging_wrapper
    status = run_func(*args)
             ^^^^^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/cli/req_command.py", line 247, in wrapper
    return func(self, options, args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/commands/install.py", line 326, in run
    session = self.get_default_session(options)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/cli/req_command.py", line 98, in get_default_session
    self._session = self.enter_context(self._build_session(options))
                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/cli/req_command.py", line 125, in _build_session
    session = PipSession(
              ^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/network/session.py", line 343, in __init__
    self.headers["User-Agent"] = user_agent()
                                 ^^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/network/session.py", line 175, in user_agent
    setuptools_dist = get_default_environment().get_distribution("setuptools")
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/metadata/importlib/_envs.py", line 188, in get_distribution
    return next(matches, None)
           ^^^^^^^^^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/metadata/importlib/_envs.py", line 183, in <genexpr>
    matches = (
              ^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/metadata/base.py", line 612, in iter_all_distributions
    for dist in self._iter_distributions():
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/metadata/importlib/_envs.py", line 176, in _iter_distributions
    for dist in finder.find_eggs(location):
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/metadata/importlib/_envs.py", line 144, in find_eggs
    yield from self._find_eggs_in_dir(location)
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/metadata/importlib/_envs.py", line 111, in _find_eggs_in_dir
    from pip._vendor.pkg_resources import find_distributions
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_vendor/pkg_resources/__init__.py", line 2164, in <module>
    register_finder(pkgutil.ImpImporter, find_on_path)
                    ^^^^^^^^^^^^^^^^^^^
AttributeError: module 'pkgutil' has no attribute 'ImpImporter'. Did you mean: 'zipimporter'?
Traceback (most recent call last):
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/__pip-runner__.py", line 50, in <module>
    runpy.run_module("pip", run_name="__main__", alter_sys=True)
  File "<frozen runpy>", line 226, in run_module
  File "<frozen runpy>", line 98, in _run_module_code
  File "<frozen runpy>", line 88, in _run_code
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/__main__.py", line 31, in <module>
    sys.exit(_main())
             ^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/cli/main.py", line 70, in main
    return command.main(cmd_args)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/cli/base_command.py", line 101, in main
    return self._main(args)
           ^^^^^^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/cli/base_command.py", line 216, in _main
    self.handle_pip_version_check(options)
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/cli/req_command.py", line 179, in handle_pip_version_check
    session = self._build_session(
              ^^^^^^^^^^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/cli/req_command.py", line 125, in _build_session
    session = PipSession(
              ^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/network/session.py", line 343, in __init__
    self.headers["User-Agent"] = user_agent()
                                 ^^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/network/session.py", line 175, in user_agent
    setuptools_dist = get_default_environment().get_distribution("setuptools")
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/metadata/importlib/_envs.py", line 188, in get_distribution
    return next(matches, None)
           ^^^^^^^^^^^^^^^^^^^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/metadata/importlib/_envs.py", line 183, in <genexpr>
    matches = (
              ^
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/metadata/base.py", line 612, in iter_all_distributions
    for dist in self._iter_distributions():
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/metadata/importlib/_envs.py", line 176, in _iter_distributions
    for dist in finder.find_eggs(location):
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/metadata/importlib/_envs.py", line 144, in find_eggs
    yield from self._find_eggs_in_dir(location)
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_internal/metadata/importlib/_envs.py", line 111, in _find_eggs_in_dir
    from pip._vendor.pkg_resources import find_distributions
  File "/private/tmp/marimo-venv/venv/lib/python3.10/site-packages/pip/_vendor/pkg_resources/__init__.py", line 2164, in <module>
    register_finder(pkgutil.ImpImporter, find_on_path)
                    ^^^^^^^^^^^^^^^^^^^
AttributeError: module 'pkgutil' has no attribute 'ImpImporter'. Did you mean: 'zipimporter'?

I googled AttributeError: module 'pkgutil' has no attribute 'ImpImporter'. Did you mean: 'zipimporter'? and found a lot of hits.
So it seems like the version of pip that is being used is incompatible with Python 3.12.
Why that would happen, I am currently unsure.
I noticed you marimo env lists Python 3.12, but your venv appears to be using Python 3.10, which is perplexing but could explain the issue.
Is it at all possible that marimo is installed globally? Does which marimo return something inside the venv or outside it?

I'm definitely suffering from https://xkcd.com/1987/ - I've lost track of which Python environment and which Marimo installations I have lying around I'm afraid.
I think you're right, the root cause here is definitely that I somehow had a Python 3.12 running against a 3.10 virtual environment. No idea at all how that happened though!

Looking forward to the day when uv is totally feature complete and universally adopted and never have to think about virtual environments again 😅 One can dream ...!


Device profile changes in 4.5.0 webui fault

Device profiles can be created in v4.5.0 but any configuration or codec changes after creation do not register as being altered or saved in the db. It also does not go back to the device profile screen like previous on hitting the submit/save to configuration or codec changes.
The rest api and rpc still seem to be working correctly.

For the moment I have dropped back to v4.4.3 which I have confirmed has this working.

Thanks for reporting this issue, I'm going to look into this right now :-)

So far I have not been able to reproduce this:

Tested using Firefox and Chrome
I created a "test profile" with standard JS codec template, clicking Submit takes me to the list of profiles
I click the test profile and change the temp field in the JS codec template, clicking Submit takes me to the list of profiles
I click the test profile and the temp field in the JS codec reflect the latest change

Have you tried to refresh / clear your browser cache to make sure your browser is using the latest front-end code and sources?
Please let me know if there is anything else I can do to reproduce this issue.

I just rechecked, it seems once the device profile has been assigned to a device is when it occurs for me in the UI.

I have same issue, cant submit changes. Version is updated to 4.5.0

I have taken another recording with browser dev tools open. it does mention some label not being correct on that page, but if that has anything to do with it or not i do not know.
https://cdn.discordapp.com/attachments/1088316656901689344/1157164077941018674/Screen_Recording_2023-09-29_at_13.55.17.mov

Confirmed on my side. It works until the device profile is affected to minimum one device.

With the help of @skiplyfrance I have found the issue. The issue is the measurements tab, with the migration to the latest ReactJS + Ant versions, something has changes with regards to the name field validation. If you have that tab open, you will see a validation issue, which is the reason why the form does not submit. I will create a fix for this.
Thanks @ccall48 and @skiplyfrance to help me with debugging this issue :+1:

cool beans, at least i know i wasn't going crazy now 😅
tbh i only found it by chance when i was trying to help somebody on discord with a payload decoder.

@ccall48 @skiplyfrance would the following error notification be helpful to add to all the forms in case of a validation error?

The actual validation error is displayed per input field:

It would definitly help. Maybe "Please complete all required fields." could be more explicit but I'm not a native english speaker.

In this case it is an empty required field, but in general this error will be triggered in case of all validation errors, thus also:

Optional fields with incorrect input
Required fields that have incorrect input

The above commit fixes this issue + I have added this fix to all other forms as well to make sure the form behavior is equal to all forms.


How to build with CUDA9.0 ?

copying pointnet2_ops/_ext-src/src/sampling_gpu.cu -> build/lib.linux-x86_64-3.6/pointnet2_ops/_ext-src/src
running build_ext
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/yuenlin/documents/PVN3D-master/Pointnet2_PyTorch-master/pointnet2_ops_lib/setup.py", line 38, in <module>
    include_package_data=True,
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/setuptools/__init__.py", line 153, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib/python3.6/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib/python3.6/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/setuptools/command/install.py", line 68, in run
    return orig.install.run(self)
  File "/usr/lib/python3.6/distutils/command/install.py", line 589, in run
    self.run_command('build')
  File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/usr/lib/python3.6/distutils/command/build.py", line 135, in run
    self.run_command(cmd_name)
  File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/setuptools/command/build_ext.py", line 79, in run
    _build_ext.run(self)
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/Cython/Distutils/old_build_ext.py", line 186, in run
    _build_ext.build_ext.run(self)
  File "/usr/lib/python3.6/distutils/command/build_ext.py", line 339, in run
    self.build_extensions()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 404, in build_extensions
    self._check_cuda_version()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 781, in _check_cuda_version
    raise RuntimeError(CUDA_MISMATCH_MESSAGE.format(cuda_str_version, torch.version.cuda))

RuntimeError:
The detected CUDA version (9.0) mismatches the version that was used to compile
PyTorch (10.2). Please make sure to use the same CUDA versions.

i use pytotch 1.0.1 and CUDA9.0, but failed to building wheel for pointnet2-ops

copying pointnet2_ops/_ext-src/src/sampling_gpu.cu -> build/lib.linux-x86_64-3.6/pointnet2_ops/_ext-src/src
running build_ext
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/yuenlin/documents/PVN3D-master/Pointnet2_PyTorch-master/pointnet2_ops_lib/setup.py", line 38, in <module>
    include_package_data=True,
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/setuptools/__init__.py", line 153, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib/python3.6/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib/python3.6/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/setuptools/command/install.py", line 68, in run
    return orig.install.run(self)
  File "/usr/lib/python3.6/distutils/command/install.py", line 589, in run
    self.run_command('build')
  File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/usr/lib/python3.6/distutils/command/build.py", line 135, in run
    self.run_command(cmd_name)
  File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/setuptools/command/build_ext.py", line 79, in run
    _build_ext.run(self)
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/Cython/Distutils/old_build_ext.py", line 186, in run
    _build_ext.build_ext.run(self)
  File "/usr/lib/python3.6/distutils/command/build_ext.py", line 339, in run
    self.build_extensions()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 404, in build_extensions
    self._check_cuda_version()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 781, in _check_cuda_version
    raise RuntimeError(CUDA_MISMATCH_MESSAGE.format(cuda_str_version, torch.version.cuda))

RuntimeError:
The detected CUDA version (9.0) mismatches the version that was used to compile
PyTorch (10.2). Please make sure to use the same CUDA versions.

i use pytotch 1.0.1 and CUDA9.0, but failed to building wheel for pointnet2-ops

Did you solve this? I am having the same problem.

copying pointnet2_ops/_ext-src/src/sampling_gpu.cu -> build/lib.linux-x86_64-3.6/pointnet2_ops/_ext-src/src
running build_ext
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/yuenlin/documents/PVN3D-master/Pointnet2_PyTorch-master/pointnet2_ops_lib/setup.py", line 38, in <module>
    include_package_data=True,
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/setuptools/__init__.py", line 153, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib/python3.6/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib/python3.6/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/setuptools/command/install.py", line 68, in run
    return orig.install.run(self)
  File "/usr/lib/python3.6/distutils/command/install.py", line 589, in run
    self.run_command('build')
  File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/usr/lib/python3.6/distutils/command/build.py", line 135, in run
    self.run_command(cmd_name)
  File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/setuptools/command/build_ext.py", line 79, in run
    _build_ext.run(self)
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/Cython/Distutils/old_build_ext.py", line 186, in run
    _build_ext.build_ext.run(self)
  File "/usr/lib/python3.6/distutils/command/build_ext.py", line 339, in run
    self.build_extensions()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 404, in build_extensions
    self._check_cuda_version()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 781, in _check_cuda_version
    raise RuntimeError(CUDA_MISMATCH_MESSAGE.format(cuda_str_version, torch.version.cuda))

RuntimeError:
The detected CUDA version (9.0) mismatches the version that was used to compile
PyTorch (10.2). Please make sure to use the same CUDA versions.

i use pytotch 1.0.1 and CUDA9.0, but failed to building wheel for pointnet2-ops

I want to ask do you solve this? I am having the same problem

copying pointnet2_ops/_ext-src/src/sampling_gpu.cu -> build/lib.linux-x86_64-3.6/pointnet2_ops/_ext-src/src
running build_ext
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/yuenlin/documents/PVN3D-master/Pointnet2_PyTorch-master/pointnet2_ops_lib/setup.py", line 38, in <module>
    include_package_data=True,
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/setuptools/__init__.py", line 153, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib/python3.6/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib/python3.6/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/setuptools/command/install.py", line 68, in run
    return orig.install.run(self)
  File "/usr/lib/python3.6/distutils/command/install.py", line 589, in run
    self.run_command('build')
  File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/usr/lib/python3.6/distutils/command/build.py", line 135, in run
    self.run_command(cmd_name)
  File "/usr/lib/python3.6/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/setuptools/command/build_ext.py", line 79, in run
    _build_ext.run(self)
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/Cython/Distutils/old_build_ext.py", line 186, in run
    _build_ext.build_ext.run(self)
  File "/usr/lib/python3.6/distutils/command/build_ext.py", line 339, in run
    self.build_extensions()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 404, in build_extensions
    self._check_cuda_version()
  File "/home/yuenlin/.venvs/pvn3dmaster/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 781, in _check_cuda_version
    raise RuntimeError(CUDA_MISMATCH_MESSAGE.format(cuda_str_version, torch.version.cuda))

RuntimeError:
The detected CUDA version (9.0) mismatches the version that was used to compile
PyTorch (10.2). Please make sure to use the same CUDA versions.

i use pytotch 1.0.1 and CUDA9.0, but failed to building wheel for pointnet2-ops

Did you solve this? I am having the same problem.

hello, do you solve this, I am having the same problem

same problem. has anyone solved?


iPad Pro 3 with iOS 13.3.1 could not run

when I start the VM, it crash.

Me too.

I also encountered this problem, how to solve it

I imagine this is connected to #60


Version Missing in istioctl after Canary Upgrade

Bug Description
istioctl does not display the version after performing a canary upgrade:
istioctl version
client version: 1.11.1
istiod version: 1.11.1
pilot version: 1.10.4
data plane version:  (1 proxies), 1.10.4 (3 proxies)

I expected:
istioctl version
client version: 1.11.1
istiod version: 1.11.1
pilot version: 1.10.4
data plane version:  1.11.1 (1 proxies), 1.10.4 (1 proxies)

The same for proxy-status:
istioctl ps
NAME                                                   CDS        LDS        EDS        RDS        ISTIOD                             VERSION
productpage-v1-6cbbc6568c-k49k2.default                SYNCED     SYNCED     SYNCED     SYNCED     istiod-899959c89-t882f             1.10.4
public-ingressgateway-85fcc7448-zlgvv.istio-system     SYNCED     SYNCED     SYNCED     SYNCED     istiod-1-11-1-6d9b4745dd-qvsks     *

Version
istioctl version
client version: 1.11.1
istiod version: 1.11.1
pilot version: 1.10.4
data plane version:  (1 proxies), 1.10.4 (3 proxies)

Additional Information
I'm following the operator-based canary upgrade documentation.

This is not a bug. I was not including the ISTIO_META_ISTIO_VERSION was empty when building my container image.


Support to guzzle 7

Can you guys please add support to guzzle v7?

https://github.com/coinbase/coinbase-commerce-php/pull/34
You have this PR ;)

It seems like they don't care about this product. Issues aren't answered here and I contacted their support e-mail but no real reply yet after a week.
You can't even turn off payment notification e-mails in the settings for example.

I also have a real bad experience with their support email, same as you. I really don't understand how a company treats this way their customers, it blows my mind.

It seems like they don't care about this product. Issues aren't answered here and I contacted their support e-mail but no real reply yet after a week.

Closed by mistake... btw @Fossil01 do you know a good PHP alternative to Coinbase?

You can use my fork for now, which is what I am doing.

Oh, ok, nice :)

So they now just labelled this as "Not actively maintained" nice....

So they now just labelled this as "Not actively maintained" nice....

Awesome lol


On mobile, nav links scroll the nav

Tested on my Android phone on both Chrome and Firefox.
If you are jumping up in the page, this is fine, but if you are going down, this scrolling puts the hamburger close button out of screen, making it a bit hard/annoying to get out of the nav.
Screenshot

Does seem better in #316

thank you for reporting this, @zmoon! i just merged #316, can you confirm that this is not an issue anymore? i tested this on ios and everything seems to be working fine.

Yep seems good!

Awesome! thank you 🙏


Contribution is not updated

I'm done signing in as incognito and refreshing the page multiple times but still not updating my recent contributions

Hi John! Sorry for the late reply. This might be an issue with the way Apollo caches API request results. If you're still interested, could you try signing out and in again?

I've more than 400 commits contribition graph shows only 30
Re-logged in nothing changed. Although i'm first time using this app how can it be cached?

Looking at the code, quite a few GitHub queries are using values from 2021. This is why the data is not consistent.
https://github.com/neat-run/wrapped/blob/91ab99a527e593769fb06762e02f83e33f62d27e/utils/constants.js#L12-L15

@tedspare update your static dates with dynamic last year...

@tedspare, this is a really cool tool. Do you think it can be updated for 2022? I have opened a quick PR for the same: https://github.com/neat-run/wrapped/pull/29.

Thanks @bhuvansingla for closing this! Was AFK for a while.


style: navbar menu on mobile

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[ ] Feature
[ ] Refactoring
[x] Style

Needs Design check

@exezbcz please review

Context

[x] Closes #6331

Did your issue had any of the "$" label on it?

[x] My DOT address: Payout

Screenshot 📸

[x] My fix has changed UI

Copilot Summary

🤖 Generated by Copilot at bb72158
Improved the layout and responsiveness of the main navigation bar. Added a button to connect a wallet using the button-connect-wallet class.

🤖 Generated by Copilot at bb72158

The navbar items had too much padding
So the developer did some editing
He made them responsive
And removed the excessive
Styles for #NavProfile and added button-connect-wallet fitting

@exezbcz, how about this one? Smaller padding on the navbar item, but still more than 48px for the touch point. ref: material.io/develop/web/supporting/touch-target

oh wait still didnt show on safari ios

so from what i see, every nav item has now smaller height

the connect as well.

If this will ensure responsiveness on nova wallet, let's go
One small thing, I know its not part of the issue - could you please fix the text in the button in dark mode

should be black

so from what I see, every nav item now has smaller height

yes correct. I made it smaller, but still more than > 48px. because based on google design, touch point for mobile is min 48x48

One small thing, I know its not part of the issue - could you please fix the text in the button in dark mode

sure, let me update that

pay 50 usd

😍 Perfect, I’ve sent the payout
💵 $50 @ 4.48 USD/DOT ~ 11.161 $DOT
🧗 1xjvRADwdJcnmUCLWerEHR4iGCT5EBTm4D4fzLLg4LcAC9p
🔗 0x073cbd9a17ae6cdb57f521c0ff5370bff566db3d30555cb176137c99aecdba3d
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Use the correct copyright notice

The whole PaddlePaddle github organization works under Apache license. However, I see many source files in this repo has Baidu copyright notice like the following:
https://github.com/PaddlePaddle/paddle-mobile/blob/7e863861ab6672fa83d5969e71f2128ae76462db/src/framework/data_type.h#L1
Please correct them into "PaddlePaddle Authors" instead of "Baidu Inc.".

fixed.


build_runner fails due to missing --delete-conflicting-outputs when building docker image

Steps to reproduce
Following the steps
Execute  docker build -t app .
Logs
PS C:\Users\Taha\AndroidStudioProjects\functions-framework-dart\examples\hello> docker build -t app .
[+] Building 75.6s (13/15)
 => [internal] load build definition from Dockerfile                                                               0.0s
 => => transferring dockerfile: 419B                                                                               0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/subfuzion/dart:slim                                                     5.0s
 => [internal] load metadata for docker.io/google/dart:latest                                                      3.3s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 4.03kB                                                                                0.0s
 => [stage-1 1/2] FROM docker.io/subfuzion/dart:slim@sha256:1a60fa1089065c4dd86d0735becafab9d14dca828ba0ee19ab6b5  9.2s
 => => resolve docker.io/subfuzion/dart:slim@sha256:1a60fa1089065c4dd86d0735becafab9d14dca828ba0ee19ab6b547c9e81e  0.0s
 => => sha256:96038e2c2edc52d526490905a0a8a29009121e6b818611cbeb0bf680ef4ff0fc 3.36kB / 3.36kB                     0.0s
 => => sha256:d2479f507fd5864befeaa2e34e66c0fcd3a4569391414055045504b6d6264439 5.25kB / 5.25kB                     1.2s
 => => sha256:1a60fa1089065c4dd86d0735becafab9d14dca828ba0ee19ab6b547c9e81e479 3.03kB / 3.03kB                     0.0s
 => => sha256:b61110f8811e25de718932280def2f6e2a76db1d1efa9ec5839e8ae5ea0a3592 85.33kB / 85.33kB                   1.8s
 => => sha256:bb427ce0421e3ec656217773e46edc510071334101188c5958fa89faa9dadbbb 806.48kB / 806.48kB                 2.5s
 => => sha256:47b4e080f3c21e53a31376bdb4e7da17e2840c3e884b2f9ec2b251c514e472de 1.07MB / 1.07MB                     3.5s
 => => extracting sha256:b61110f8811e25de718932280def2f6e2a76db1d1efa9ec5839e8ae5ea0a3592                          0.0s
 => => extracting sha256:d2479f507fd5864befeaa2e34e66c0fcd3a4569391414055045504b6d6264439                          0.0s
 => => sha256:1a7f627f3770b2bfc01ae558b9ef3c97db9b7aee8614b7948515a95b9f4cd1bb 14.61kB / 14.61kB                   3.4s
 => => extracting sha256:bb427ce0421e3ec656217773e46edc510071334101188c5958fa89faa9dadbbb                          0.0s
 => => sha256:cbec143a02d30d0ca4174074f8919cac8652f325a3710b4c983e699dba00de59 57.98kB / 57.98kB                   4.1s
 => => sha256:e8f92b5f341209361f2168ad7b6e51d93c2e7457fa601aa7c9a92249a5588000 217B / 217B                         5.1s
 => => extracting sha256:47b4e080f3c21e53a31376bdb4e7da17e2840c3e884b2f9ec2b251c514e472de                          0.0s
 => => sha256:74f9d6fb6203c0de9ebdc3214249151bedd52f457493b6732a314187fcd033c1 375B / 375B                         4.7s
 => => extracting sha256:1a7f627f3770b2bfc01ae558b9ef3c97db9b7aee8614b7948515a95b9f4cd1bb                          0.0s
 => => extracting sha256:cbec143a02d30d0ca4174074f8919cac8652f325a3710b4c983e699dba00de59                          0.0s
 => => sha256:0399d7ff3b284bf28985db4586b3f4c4b20c20dce0c7d02d856a39562efe622d 158B / 158B                         5.2s
 => => sha256:5d74d374fa1b997fc7e3319a10a40ee3c8b8435cfe44920e627d75c8e0336650 11.48kB / 11.48kB                   6.4s
 => => extracting sha256:e8f92b5f341209361f2168ad7b6e51d93c2e7457fa601aa7c9a92249a5588000                          0.0s
 => => extracting sha256:74f9d6fb6203c0de9ebdc3214249151bedd52f457493b6732a314187fcd033c1                          0.0s
 => => sha256:8346061d681ce7ab61469d917ddb90aa594d2036785a3a75e5dfef1e787c4a0d 41.94kB / 41.94kB                   6.5s
 => => extracting sha256:0399d7ff3b284bf28985db4586b3f4c4b20c20dce0c7d02d856a39562efe622d                          0.0s
 => => sha256:4289624774d737fdd22c04278f684fe55bda50b98befaed6fa61cc8c5a9ce35f 120.54kB / 120.54kB                 7.0s
 => => extracting sha256:5d74d374fa1b997fc7e3319a10a40ee3c8b8435cfe44920e627d75c8e0336650                          0.0s
 => => sha256:1057b7629ca333d5344117084946b32a44424faed73d2f24072e648060947184 122.43kB / 122.43kB                 8.8s
 => => extracting sha256:8346061d681ce7ab61469d917ddb90aa594d2036785a3a75e5dfef1e787c4a0d                          0.0s
 => => extracting sha256:4289624774d737fdd22c04278f684fe55bda50b98befaed6fa61cc8c5a9ce35f                          0.0s
 => => extracting sha256:1057b7629ca333d5344117084946b32a44424faed73d2f24072e648060947184                          0.0s
 => [stage-0 1/8] FROM docker.io/google/dart@sha256:ee2eace7c54696a43ba0f7db7ebeacf0b851d199cecd3bf4d7e3863a01dc  35.4s
 => => resolve docker.io/google/dart@sha256:ee2eace7c54696a43ba0f7db7ebeacf0b851d199cecd3bf4d7e3863a01dcbbf0       0.0s
 => => sha256:ee2eace7c54696a43ba0f7db7ebeacf0b851d199cecd3bf4d7e3863a01dcbbf0 742B / 742B                         0.0s
 => => sha256:5de967ecef0e9ad9ba8b3df26c8aec7d5b69bb496ac7bd05df85c36c3253ec2d 3.07kB / 3.07kB                     0.0s
 => => sha256:46c8e211f114a92f0bbcf260d117bc6a0836ae90c0c812d6936c363065dd8f85 52.59MB / 52.59MB                  15.5s
 => => sha256:65db95c42438444e9844fbd6e4f71b711b201526c36c08ab4543d808aa210c08 214.52MB / 214.52MB                30.7s
 => => extracting sha256:46c8e211f114a92f0bbcf260d117bc6a0836ae90c0c812d6936c363065dd8f85                          2.2s
 => => extracting sha256:65db95c42438444e9844fbd6e4f71b711b201526c36c08ab4543d808aa210c08                          4.2s
 => [stage-0 2/8] WORKDIR /app                                                                                0.3s
 => [stage-0 3/8] COPY pubspec.yaml /app/pubspec.yaml                                                              0.0s
 => [stage-0 4/8] RUN dart pub get                                                                                6.2s
 => [stage-0 5/8] COPY . .                                                                                0.0s
 => [stage-0 6/8] RUN dart pub get --offline                                                                       1.0s
 => ERROR [stage-0 7/8] RUN dart pub run build_runner build                                                       27.6s
------
 > [stage-0 7/8] RUN dart pub run build_runner build:
#13 12.73 [INFO] Generating build script...
#13 13.05 [INFO] Generating build script completed, took 345ms
#13 13.05
#13 13.07 [INFO] Creating build script snapshot......
#13 25.62 [INFO] Creating build script snapshot... completed, took 12.6s
#13 25.62
#13 26.16 [INFO] Initializing inputs
#13 26.53 [INFO] Building new asset graph...
#13 27.57 [INFO] Building new asset graph completed, took 1.0s
#13 27.57
#13 27.57 [INFO] Checking for unexpected pre-existing outputs....
#13 27.57 [INFO] Found 1 declared outputs which already exist on disk. This is likely because the`.dart_tool/build` folder was deleted, or you are submitting generated files to your source repository.
#13 27.57 [SEVERE] Conflicting outputs were detected and the build is unable to prompt for permission to remove them. These outputs must be removed manually or the build can be run with `--delete-conflicting-outputs`. The outputs are: bin/main.dart
------
failed to solve with frontend dockerfile.v0: failed to build LLB: executor failed running [/bin/sh -c dart pub run build_runner build]: runc did not terminate sucessfully
PS C:\Users\Taha\AndroidStudioProjects\functions-framework-dart\examples\hello>

Solution
Add --delete-conflicting-outputs in DockerFile
At line 10 updated following  line
RUN dart pub run build_runner build --delete-conflicting-outputs
After making changes, images builds successfully
PS C:\Users\Taha\AndroidStudioProjects\functions-framework-dart\examples\hello> docker build -t app .
[+] Building 40.7s (16/16) FINISHED
 => [internal] load build definition from Dockerfile                                                               0.0s
 => => transferring dockerfile: 448B                                                                               0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/subfuzion/dart:slim                                                     2.3s
 => [internal] load metadata for docker.io/google/dart:latest                                                      2.2s
 => [stage-0 1/8] FROM docker.io/google/dart@sha256:ee2eace7c54696a43ba0f7db7ebeacf0b851d199cecd3bf4d7e3863a01dcb  0.0s
 => CACHED [stage-1 1/2] FROM docker.io/subfuzion/dart:slim@sha256:1a60fa1089065c4dd86d0735becafab9d14dca828ba0ee  0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 687B                                                                                0.0s
 => CACHED [stage-0 2/8] WORKDIR /app                                                                              0.0s
 => CACHED [stage-0 3/8] COPY pubspec.yaml /app/pubspec.yaml                                                       0.0s
 => CACHED [stage-0 4/8] RUN dart pub get                                                                          0.0s
 => [stage-0 5/8] COPY . .                                                                                0.0s
 => [stage-0 6/8] RUN dart pub get --offline                                                                       0.8s
 => [stage-0 7/8] RUN dart pub run build_runner build --delete-conflicting-outputs                                31.8s
 => [stage-0 8/8] RUN dart compile exe bin/main.dart -o bin/server                                                 5.6s
 => [stage-1 2/2] COPY --from=0 /app/bin/server /app/bin/server                                                    0.0s
 => exporting to image                                                                                0.1s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:a82797f3df1b4b7ea3ead64fd8e56fd3c5cdb15d233514adfaf744aa2681ecf6                       0.0s
 => => naming to docker.io/library/app

Good catch. I just fixed this two weeks ago in #23 for the main Dockerfile, but missed it for the example. Thanks!


Split ModBase in a different github repo for better modding

Splitting them in different repositories allow us to use it as a git submodule in our project and also will be better for you to manage the issues.

You are right, I will do that later :+1:

Also, yesterday I tried to add your ModBase to my Mod, but I couldn't due to some errors (probably I'm too newbie to use this methodology and I'm doing something wrong). I'll try to open a new issue explaining all the troubles that I found, how I solved and where am currently blocked.

BTW, I'm not sure if you're aware of this other Mod for better modding (it's a little bit more advanded than yours, maybe you could merge both projects): https://github.com/DlkGames/SkylineToolkit

Looks like a far more expansive project then I am willing to go for, at least for the time being. I like to keep things simple and small.
In their library, it looks like alot of wrapping of Collosal's libraries is being done, which may break at one point when the game receives updates, or generally just adds alot of noise imo. It really depends on the goals and vision of its collaborators and users. Interesting for sure, it may become a modders dream, but on the flipside also not something that may appeal to smalltime modders.
My focus for the time being is to provide a minimalistic set of base classes. I do have some more ideas to add, but main focus will remain keeping things small. Perhaps even a new project for fancy stuff...

I also think is a good idea to keep it simple. Maybe you could think in a way to achieve some of the SkylineToolkit functionality by focus in extending your ModBase.
For example, this mod can be extended: https://github.com/Rychard/CityWebServer
As said, I'm really newbie and I don't know how much difficult can it be, nor the technological problems that can occur when doing this kind of things.

Renamed this repo to CSAutosave and moved ModBase over to
https://github.com/skwasjer/CSModBase. Note that the readme is slightly off now, I need to correct that still.

Nice! :+1:


Meta function extension methods

as discussed here: #12
*each

[ ] coordEach
[ ] featureEach
[ ] flattenEach
[ ] clusterEach
[ ] segmentEach
[ ] geomEach
[ ] propEach

*reduce

[ ]  featureReduce
[ ] flattenReduce
[ ] clusterReduce
[ ] coordReduce
[ ] propReduce
[ ] geomReduce
[ ] segmentReduce

other

[ ] coordAll
[ ] getCluster

this will be closed in favor of a new attempt


Vue components imported with @ into script setup have no type

If I import a vue component into a .ts file, volar picks up the type of the imported component as a DefineComponent.

However if I import a component the same way into another component, with script setup, no type is picked up.

And that causes an issue if I try to pass it to the render function. The vue compiler doesn't mind of course, it's just volar complaining about it. But volar also does pick up the type if I use a relative path to the component.

And the @ alias is defined like this in vue.config.js

@DanSweeney23 Did you also add the path to compiler options e.g. like what create-vue does.


Create CMakeLists.txt

CMakeLists.txt that compiles to shared object and installs system-wide shared library

#124 already introduced modern CMake


Move BillingAgreementDetails to above PaymentDetails in PayPal Express gateway SetExpressCheckout request

We spent a lot of time trying to figure out why the n2:BillingAgreementDetails option wasn't working for us when trying to do PayPal Merchant Initiated Billing.  Turns out, PayPal needs the n2:BillingAgreementDetails to come before the n2:PaymentDetails in the XML request sent to PayPal.
All this patch does is rearrange the request to put n2:BillingAgreementDetails above n2:PaymentDetails
As far as I could tell, there is no documentation to reference from PayPal that stipulates this required order, but this does seem to resolve my problems.
There is no test for the n2:BillingAgreementDetails block currently, so I didn't add one.

My pull request (#260) fixes the same issue but a bit more thoroughly.  The XSD defines elements in a , so there is specific ordering.  It seems that Paypal isn't always very picky about it, which is why most things have worked so far.

Fixed by merge 2ccfdb54a7dc74e3b2c6008e5e76c5560ea5d034. Closing.


Allow whitelist in DFP to leverage x-forwarded-for

I believe this is a feature request, but might still be blocked by upstream docker. The idea is to allow docker-flow-proxy to allow a whitelist of IPs at the HAProxy level via x-forwarded-for. Though I'm not sure if we can accomplish this with the way Docker swarm currently works.
Example using Google Cloud Platform since Google LBs can't implement IP restrictions yet:
GCP LB --> Docker Swarm(DFP) --> Docker Swarm(Nginx) --> (Docker Swarm(Application)
One work around currently would be to have a proxy sitting between the Google LB and the Docker Swarm to provide the whitelisting, but that isn't ideal since now we are looking at 3 LBs in front of everything.
GCP LB --> Nginx or HAProxy --> Docker Swarm(DFP) --> Docker Swarm(Nginx) --> (Docker Swarm(Application)
Ideally using the x-forwarded-for we could inspect the original IP of the client and create a whitelist to allow certain IPs through say for 3rd party approved testing only via their IPs. The issue is that the ingress of docker swarm response currently with the 10.255.x.x address as the client IP so we need to identify the true client IP via another method. Another feature is the proxy protocol support.
Here are a few related issues I've found both in the projects as well as upstream in docker.
Moby #25526
DFP #348

I don't think that's possible due to the way Overlay network is designed. The moment a request enters Overlay network, the original IP is lost. That means that you have to either a) not use Overlay or b) put something before it. I don't think I see a way to add this feature to DFP unless we move it outside Overlay/Ingress network.

Closing since there does not seem to be a good solution that can be applied in DFP. The problem is with ingress network.


[Backport] set target_lag to a str to allow for 'downstream' as accepted value

resolves https://github.com/dbt-labs/dbt-snowflake/pull/732
docs dbt-labs/docs.getdbt.com/#

Problem

Solution

Checklist

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

@McKnight-42 It looks like this is failing tests in 1.6 somehow. I reran it to make sure and the same tests failed (dynamic tables). Maybe it has something to do with the fact that we have two things to backport and they conflict?

@McKnight-42 It looks like this is failing tests in 1.6 somehow. I reran it to make sure and the same tests failed (dynamic tables). Maybe it has something to do with the fact that we have two things to backport and they conflict?

I believe it is the warehouse field since we would be testing against 1.6.latest which doesn't have that fix in it yet, that adding will get this pr moving.


Change "requires" -> "depends" in fabric.mod.json

It was renamed in schemaVersion 1 (see fabric-example-mod).

Fixes https://github.com/InsomniaKitten/Couplings/issues/5


AttributeError: 'User' object has no attribute 'first_name' with slim sidebar

Issue Summary
We have a custom user model where we have removed the first_name and last_name attributes. When enabling the slim sidebar, we get the following traceback
File "/media/brylie/SecondHD/Code/WesternFriend/WF-website/.venv/lib/python3.9/site-packages/wagtail/admin/ui/sidebar.py", line 164, in js_args
    'name': self.user.first_name or self.user.get_username(),
  File "/media/brylie/SecondHD/Code/WesternFriend/WF-website/.venv/lib/python3.9/site-packages/django/utils/functional.py", line 247, in inner
    return func(self._wrapped, *args)
AttributeError: 'User' object has no attribute 'first_name'

Steps to Reproduce

define a custom user model without the first_name or last_name fields
enable the slim sidebar with WAGTAIL_EXPERIMENTAL_FEATURES = ["slim-sidebar",]
observe the AttributeError

Make custom user models more simple
It is often advised for projects to define a custom user model early on. Similarly, many custom user models opt-out of personally identifiable first_name and last_name fields.
There should be a bit clearer documentation around defining custom user models while Wagtail core could be made more resilient to the available properties.
https://github.com/wagtail/wagtail/issues/7410
Technical details

Python version: 3.9.5
Django version: 3.2.9
Wagtail version: 2.15.1

Thank you @brylie, I can confirm the issue, and am working on a fix.


suggestion

Please release for IOS , Because there is no suitable software on IOS for FT8.
73, EP7NIM

Please release for YAESU FT-100(D) , Because there is no suitable model number for FT-100 rig in the FT8CN. Thanks！
73
BU2AE

暂时还没有开发IOS版本的计划。


[QBD] Handle the syncing for QBD

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/49698
PROPOSAL:
Tests

Same as Tests

[x] Verify that no errors appear in the JS console

Offline tests

Can't test when offline
QA Steps

Prerequisites: Turn on Beta quickbooksDesktopOnNewDot on your account
In Web/Desktop

Sign in on an account that enabled beta quickbooksDesktopOnNewDot
Go to any Workspace -> Accounting
Click on "Connect" button next to "Quickbooks Desktop" integration
Click on "Done" button on "QuickBooks Desktop setup" page
Verify that it starts to sync data from QBD
Verify that after a few seconds, it shows a connection error
Click on three-dot menu on the right of "Quickbooks Desktop" integration
Verify it shows "Reinstall connector" menu
Click on "Reinstall connector" menu
Verify it opens QuickBooks Desktop setup page
Follow steps here
Back to ND, click on "Done" button on "QuickBooks Desktop setup" page
Verify that it syncs data successfully from QBD

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

N/A

Android: mWeb Chrome

N/A

iOS: Native

N/A

iOS: mWeb Safari

N/A

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/25da0236-f4ca-4963-b4a0-f607d3ffd965
https://github.com/user-attachments/assets/3ce3c09f-a308-49d0-9395-7c4ea7d59498

MacOS: Desktop

https://github.com/user-attachments/assets/4ad13c97-ceed-4b7b-af6d-86aedccd0ddc
https://github.com/user-attachments/assets/f5f5909c-3df1-40f9-992f-5e896ea60006

@hoangzinh I've raised a PR so the backend properly sets the error message.

@hoangzinh I've raised a PR so the backend properly sets the error message.

@hoangzinh it should be good now, can you test it?

Pinging you here @hoangzinh to retest in case you've missed my notifications on NewDot.

Okay, I've retested it on my own and it seems to work well @francoisl:
https://github.com/user-attachments/assets/1b3b38ba-d6b1-4e62-baca-e6007d6e0641

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


Remove isort dependency

Looks like isort was removed as a dependency since ruff was used with isort config, but somehow it got back in the dependencies.
Description
Removes isort from dependencies and Makefile.
Related Issues

Checklist

[x] Is this code covered by new or existing unit tests or integration tests?
[ ] Did you run make test successfully?
[ ] Do new classes, functions, methods and parameters all have docstrings?
[ ] Were existing docstrings updated, if necessary?
[ ] Was external documentation updated, if necessary?

Additional Notes or Comments

Codecov Report
Attention: 48 lines in your changes are missing coverage. Please review.

Comparison is base (34830a7) 80.33% compared to head (cd78876) 80.59%.
Report is 16 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1251      +/-   ##
==========================================
+ Coverage   80.33%   80.59%   +0.25%
==========================================
  Files          95       97       +2
  Lines        6602     6684      +82
==========================================
+ Hits         5304     5387      +83
+ Misses       1298     1297       -1

Files
Coverage Δ

superduperdb/base/config.py
100.00% <ø> (ø)

superduperdb/components/model.py
93.66% <100.00%> (+11.00%)
:arrow_up:

superduperdb/ext/openai/model.py
96.09% <ø> (+0.64%)
:arrow_up:

superduperdb/ext/torch/model.py
76.80% <ø> (ø)

superduperdb/misc/superduper.py
76.25% <ø> (ø)

superduperdb/base/build.py
65.85% <66.66%> (-1.65%)
:arrow_down:

superduperdb/base/logger.py
86.95% <80.00%> (-3.05%)
:arrow_down:

superduperdb/cli/serve.py
39.28% <50.00%> (+4.28%)
:arrow_up:

superduperdb/cli/stack.py
55.55% <55.55%> (ø)

superduperdb/components/stack.py
41.53% <41.53%> (ø)

... and 7 files with indirect coverage changes

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


method to get serialized remote object

hi all:
i use remote to use an API within my main process.  i generally use that API simply to get raw data.  however, the returned object is a remote object (as clearly documented), riddled with getter/setters/etc to sync-get-send via IPC.  is there a way to get a serialized version of the remote object with ease?
thanks!

I forgot to add, JSON.stringify produces a max call stack, which perhaps is expected.
api = require('remote').require('/path/to/api/services/index.js');
setDataz = function(err, result) { JSON.stringify(result); } // kaaaboooom!!
api.bots.list(setDataz)

you know... i think i have a cycle.  brb

so the main process would have to decycle.  what if we detected if the call was coming from remote and decycled prior to passing?

You can use the ipcRenderer module to send raw data.


M41A MK1 Rifle Crate (x2 MK1, x2 magazines) Cost: $4000

We dont have Mk1

We dont have Mk1

the crate was made, just with MK2s in it lol


Decouple gfx-replay player from scene graph.

Motivation and Context
This changeset decouples gfx::replay::Player from SceneNode by:

Introducing a forward-declared GfxReplayNode type, which can be cast into either SceneNode* or an index, depending on the implementation.
Moving gfx::replay::Player implementation into callback functions.

The intent is to make the player reusable with the batch renderer, which will utilize indices rather than SceneNode and SceneGraph.
How Has This Been Tested
All tests are passing.
Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

FYI: saw some minor perf issues while looking at this PR (unrelated to this change) and fixed them in #1954


[SuperEditor][SuperTextField] Implement performSelector (Resolves #836, #1274)

[SuperEditor][SuperTextField] Implement performSelector. Resolves #836, #1274.
The issue
Steps to reproduce:

Setup the keyboard with a language that has accents (e.g. Portuguese or German)
Run SuperEditor or SuperTextField demos
Press and hold letter "a" (wait for the accent panel to be shown)
Press backspace to delete the "a"

The letter is deleted but the accent panel is not closed:
https://github.com/superlistapp/super_editor/assets/31278849/6c872d94-3462-4b89-b738-511beb5afef4
This panel is entirely managed by the IME. As we are handling the key events, we prevent the IME from handling them and closing the panel. The navigation between the characters in the accent panel also doesn't work.
The solution
We need to change the way we handle shortcuts. On mac, we need to let the key events propagate to the IME and then we handle the selectors the IME generates.
These selectors are like system-level shortcuts. The OS maps the shortcuts to a string, which might be seen as an intent, like moveLeft:, deleteBackward:, scrollToBeginningOfDocument: and others. The user can override the keybinding and the only thing we know is the selector name.
For each selector,  the performSelector method  is called on the TextInputClient. By handling performSelection instead of the key events, the interaction with the accent panel works as expected:
https://github.com/superlistapp/super_editor/assets/7597082/d4a9e8d0-20cc-485d-a462-2d0453937591
Changes in this PR
This PR makes the following changes:

Implements performSelector handling for both SuperEditor and SuperTextField. I used a map to configure the handlers for each selector. We can change it to be a list, like the list of keyboard handlers.
Implements missing shortcuts:

OPTION + UP ARROW: Move the selection to the beginning of the paragraph.
OPTION + DOWN ARROW: Move the selection to the end of the paragraph.
CMD + UP ARROW: Move the selection to the beginning of the document.
CMD + DOWN ARROW: Move the selection to the end of the document.
SHIFT + OPTION + UP ARROW: Expand the selection to the beginning of the paragraph.
SHIFT + OPTION + DOWN ARROW: Expand the selection to the end of the paragraph.
SHIFT + CMD + UP ARROW: Expand the selection to the beginning of the document.
SHIFT + CMD + DOWN ARROW: Expand the selection to the end of the document.

Adds a new MovementModifier to move the selection to the beginning or end of a paragraph.
Wraps the text input handler widgets with an Actions widget. This is used to prevent the framework from using the arrow keys to move focus between widgets.
Changes the new line insertion in SuperTextField to be handled by the performAction call instead of key handlers. This is needed because, if the accent panel is opened and the user presses ENTER, handling the key event causes a new line to be inserted instead of confirming the select character and closing the panel.
Changes SuperTextField replacement delta handling to consider the incoming composing region. Previously, we were ignoring the composing region. This was causing us to clear the composing region on the IME. Because of that, when trying to navigate through the suggestions in the accent panel, the panel was closed immediately.

Remarks

Obviously, not all of our shortcuts have a corresponding selector, se we keep handling the key events for these shortcuts.
I declared private methods for the selector handlers, like _moveCaretUpstream, because we already have public methods with conflicting names.
I didn't added a public API yet. After confirming if we should use a map, list or other approach to map the handlers we should add a public API to override the selector handlers.
Most of the tests worked without any changes. The flutter test package maps common macOS shortcuts to selectors. During tests, I've noticed the deleteBackwardByDecomposingPreviousCharacter: wasn't mapped, so I opened https://github.com/flutter/flutter/pull/132919. This PR is already merged in Flutter master. When we cherry-pick this PR to stable, we will need to include a workaround to generate the platform channel message manually.

@brian-superlist After this PR is merged, you'll need to update your list of keyboard handlers. Most notably, doNothinOnMac must be added above the handlers that perform caret movement and content deletion.


Xcode10 beta6 compilation error

I'm use cocoapods.
http://prntscr.com/ku9puj
in Xcode9 everything fine

Also Carthage is not working with Xcode 10 GM
*** Building scheme "SwipeCellKit" in SwipeCellKit.xcworkspace
Build Failed
	Task failed with exit code 65:
This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/4k/pb54lttd6fd_19j3tf6c3f1m0000gq/T/carthage-xcodebuild.Oq47LW.log

Please take a look at the PRs or use the search functionality.

After the swift 4.2 merge, still carthage is not working:
Checking out SwipeCellKit at "2.4.3"
It should be version 2.5 right?


Migrating OurPartnersContent to Bootstrap

Summary
This PR migrates the OurPartnersCardContent component to use Bootstrap - resolving #1452
Checklist

[na] On the frontend, I've made my strings translate-able.
[na] If I've added shared components, I've added a storybook story.
[x] I've made pages responsive and look good on mobile.

Screenshots
Current Page:

Updated Page:

Known issues
There are some minor style differences between this and the current prod page (this has the correct background, slightly more readable font, standard link decorations on hyperlinks) - I think this looks good and is more consistent with our standard bootstrap styles, but wanted to call it out.
Steps to test/reproduce
For each feature or bug fix, create a step by step list for how a reviewer can test it out. E.g.:

Go to the Partners page
Verify that the content renders as expected

🚀


Remove version: Youdao.YoudaoTranslate version <IP_ADDRESS>

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://download.ydstatic.com/cidian/static/10.2/20240201/YoudaoDictSetup.exe
Response status code does not indicate success: 403 (Forbidden).
(Automated message - build 880)


Document the guideline exception: TracerProvider returns _internal::Tracer from a public method

We’ve a scenario where we’d want to create an exception to the guideline that public method signatures and types shouldn’t expose _internal types. C++ doesn’t have a notion of internal, so we enforce it by convention, using the _internal namespace.
https://github.com/Azure/azure-sdk-for-cpp/blob/de6ed1da385a45e9e26afaae01e09a9671324bec/sdk/core/azure-core/inc/azure/core/tracing/tracing.hpp#L294-L310
There’s no great way to strictly adhere to the guideline, in this case, so we'd want to document the exception that captures such a scenario.

We need the TracerProvider type to be public, since the end customer needs to instantiate it.
We need packages outside of Azure.Core (i.e. Azure.Core.Tracing.OpenTelemetry) to implement the CreateTracer virtual method on that type. We have no way to mark a method on a public type as internal.
We don’t want the Tracer types to be public, since the customer doesn’t need it. So, it is marked as _internal, even though it is returned from a public method.

https://github.com/Azure/azure-sdk-for-cpp/blob/f391e45bc144ce23488949aff9475f0ebfd199ba/sdk/core/azure-core-tracing-opentelemetry/README.md#enabling-tracing-using-opentelemetry
cc @LarryOsterman, @JeffreyRichter

Would you mind linking to the C++ guidelines that describe how to manage _internal types? I did a quick scan through the guidelines and did not find guidance related to internal types.
It would be helpful to understand the guidance which is being updated.

If a customer calls the CreateTracer method above, they might want to assign the result to a variable that they declare as a SharedPtr (instead of auto) and therefore, Tracer should NOT be internal; it should be public.

From what I understand, the CreateTracer method is not intended to be called by the customer at all, and is only meant for the SDK. That is why the goal is to try and hide as much of the unnecessary details as possible, within the internal namespace, leading to this exceptional case. Only instantiating the TracerProvider type is needed by the customer.
Following through with making Tracer public would end up requiring a few other types like Span/etc. to be marked as public too, none of which the customer needs. We wanted to avoid exposing such types, similar to how .Net keeps its DiagnosticScope and factory types internal:
https://github.com/Azure/azure-sdk-for-net/blob/ac2497255f274d294d4f4f16497c11db8f2de148/sdk/core/Azure.Core/src/Shared/DiagnosticScope.cs#L18


Cluster can not pull images from private registry (pull access denied)

Environmental Info:
K3s Version:
k3s version v1.21.5+k3s2 (724ef700)
go version go1.16.8

Node(s) CPU architecture, OS, and Version:

Linux node1.k3s 4.14.238-182.422.amzn2.x86_64 #1 SMP Tue Jul 20 20:35:54 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
1 server1, 4 agents
Describe the bug:

After update from v1.21.1+k3s1 to v1.21.5+k3s2 or v1.21.6+k3s1 or v1.22.2+k3s2 or v1.22.3+k3s1 cluster can not pull images from private registry
Steps To Reproduce:

Working setup:

create registry access/credentials: /etc/rancher/k3s/registries.yaml

mirrors:
  docker.io:
    endpoint:
      - "https://hub.docker.com"
configs:
  "hub.docker.com":
    auth:
      username: {{ docker_username }}
      password: {{ docker_password }}

Install K3s:

export K3S_TOKEN={{ token }}
export INSTALL_K3S_VERSION=v1.21.1+k3s1
export K3S_URL="https://{{ master_private_ip}:6443"
curl -sfL https://get.k3s.io | sh -

Not working setup:

create registry access/credentials: /etc/rancher/k3s/registries.yaml

mirrors:
  docker.io:
    endpoint:
      - "https://hub.docker.com"
configs:
  "hub.docker.com":
    auth:
      username: {{ docker_username }}
      password: {{ docker_password }}

Install K3s:

export K3S_TOKEN={{ token }}
export INSTALL_K3S_VERSION=v1.21.5+k3s2
#export INSTALL_K3S_VERSION=v1.21.6+k3s1
#export INSTALL_K3S_VERSION=v1.22.3+k3s1
export K3S_URL="https://{{ master_private_ip}:6443"
curl -sfL https://get.k3s.io | sh -

Expected behavior:
The cluster can pull images.
Actual behavior:
The cluster can not pull images.
Additional context / logs:

crictl info
....
   "cni": {
      "binDir": "/var/lib/rancher/k3s/data/9d8f9670e1bff08a901bc7bc270202323f7c2c716a89a73d776c363ac1971018/bin",
      "confDir": "/var/lib/rancher/k3s/agent/etc/cni/net.d",
      "maxConfNum": 1,
      "confTemplate": ""
    },
    "registry": {
      "mirrors": {
        "docker.io": {
          "endpoint": [
            "https://hub.docker.com"
          ],
          "rewrite": null
        }
      },
      "configs": {
        "hub.docker.com": {
          "auth": {
            "username": "{{ docker_user }}",
            "password": "{{ docker_password }}",
            "auth": "",
            "identitytoken": ""
          },
          "tls": null
        }
      },
      "auths": null,
      "headers": null
    },
    "imageDecryption": {
      "keyModel": ""
    },
....

k3s --version
k3s version v1.21.1+k3s1 (75dba57f)
go version go1.16.4

crictl pull smartsupp/smartsupp-addons:develop
Image is up to date for sha256:4caaf28a78a86ffae8f9b3a585a7b627d36a387b3ec31cfa39372de19e81ff9e

k3s --version
k3s version v1.21.5+k3s2 (724ef700)
go version go1.16.8

crictl pull smartsupp/smartsupp-addons:develop
FATA[2021-11-09T09:38:32.586464333+01:00] pulling image: rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/smartsupp/smartsupp-addons:develop": failed to resolve reference "docker.io/smartsupp/smartsupp-addons:develop": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

kubectl describe
│   ----     ------     ----                           ----               -------                                                                                │
│   Normal   Pulling    <invalid> (x2 over <invalid>)  kubelet            Pulling image "smartsupp/smartsupp-chatbot:develop"                                                                │
│   Warning  Failed     <invalid> (x2 over <invalid>)  kubelet            Failed to pull image "smartsupp/smartsupp-chatbot:develop": rpc error: code = Unknown desc = failed to pull and un │
│ pack image "docker.io/smartsupp/smartsupp-chatbot:develop": failed to resolve reference "docker.io/smartsupp/smartsupp-chatbot:develop": pull access denied, repository does not exist or  │
│ may require authorization: server message: insufficient_scope: authorization failed                                                                                │
│   Warning  Failed     <invalid> (x2 over <invalid>)  kubelet            Error: ErrImagePull                                                                                │
│   Normal   BackOff    <invalid> (x2 over <invalid>)  kubelet            Back-off pulling image "smartsupp/smartsupp-chatbot:develop"                                                       │
│   Warning  Failed     <invalid> (x2 over <invalid>)  kubelet            Error: ImagePullBackOff

Backporting

[x] Needs backporting to older releases

mirrors:
  docker.io:
    endpoint:
      - "https://hub.docker.com"

I am pretty sure that hub.docker.com is not a valid registry endpoint. Try https://docker.io instead.

Give
mirrors:
  docker.io:
    endpoint:
      - "https://registry-1.docker.io"
configs:
  registry-1.docker.io:
    auth:
      username: <dockerhub username>
      password: <dockerhub token>
``` a try.

As @Oats87 noted, the correct endpoint for docker.io is registry-1.docker.io, not hub.docker.com.

Thank you very much for these tips. I will try them and let you know.

I confirm it was just a bug in the endpoint .... btw it's weird that it works in the older version ...
Thank you again very much for your quick cooperation.


ACM Controller - DomainValidationOptions in status

Is your feature request related to a problem?
I'd like to start using the ACM controller but one issue that I've run into is that the DomainValidationOptions field that is included in the Spec of the resource doesn't contain fields such as the ResourceRecord which houses the CNAME record that needs to be created to validate an ACM certificate. This seems to be due to the DomainValidationOptions field having a different type when a certificate is requested vs when a certificate is described
Describe the solution you'd like
I would like the full DomainValidationOptions which includes the ResourceRecord to be included in the Status of the Certificate resource. This way, once a Certificate is created the client that created the Certificate can easily identify the required CNAME records for validation.
Describe alternatives you've considered
The client could check the ACM resource using the Certificate ARN but that would be inconvenient.
If the community agrees that this feature would be good to have then I can work on a PR. I've tried adding a new field to generator.yaml but it didn't seem to work and I didn't see the sdkFind function getting updated although the CertificateStatus was updated.
      CertificateDomainValidationOptions:
        is_read_only: true
        from:
          operation: DescribeCertificate
          path: Certificate.DomainValidationOptions

Maybe this is due to the DomainValidationOptions already being present in the Spec ?

@malmanzor Thank you for raising this and wanting to fix it! At first glance I think you might want to use set.from config instead of from.operation (e.g in ec2 https://github.com/aws-controllers-k8s/ec2-controller/blob/main/generator.yaml#L176-L178 )

@A-Hilaly thanks for the suggestion. I gave it a try and changed the config in generator.yaml to
     CertificateDomainValidationOptions:
        is_read_only: true
        set:
        - from: DomainValidationOptions

When I regenerated the code the CertificateDomainValidationOptions were removed from the CertificateStatus in certificate.go . I'm not sure what is wrong but I took a look at the documentation for the set option which I found here (I'm not sure that is the right place). My use case seems to be a little different from the documented use case in that I'm trying to configure an object in the status block and I'm trying to set fields that are found in the resource output but not the input. Are those supported for set?
I will keep trying to find a configuration that fits.

@malmanzor I think you're on the right path. The only thing I could think is missing is that your from is a plural Options rather than Option. If you want an array of those options, then there is a third alternative, which is using custom_field: Like here https://github.com/aws-controllers-k8s/s3-controller/blob/main/generator.yaml#L52C1-L53