enable double precision for SparseTensorDenseMatMul on GPU

Trivial changes (just adding some extra macro calls)

I signed it!

Nagging Assignee @drpngx: It has been 17 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @drpngx: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@bendavid it looks like there are build errors. Could you take a look?

Nagging Assignee @drpngx: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

It has been 43 days that this pull-request has stalled. Please create a new pull-request with the requested changes.


Use faux-jax instead of sinon/nock

faux-jax is isomorphic and will improve the tests for all kinds of gateways. Nowadays we use sinon for browser and nock for server, this change will allow a single solution for both platforms.

This is finally happening here: https://github.com/tulios/mappersmith/tree/draft-2.0

Version 2.0.0-rc1 was merged


When the title is too long, the second column will not align correctly

Found a small issue. When there's nested block in first column and the title of first column takes more than 1 line, the second column will align to the nested block in first column.

Love this theme and the parallel!

good catch !  Maybe I should redesgin the layout.

Same thing happened to the admonition.
And parallel not works for Example. You can see the length of colored block is not changed with parallel-2 tag.

Many thanks!


Fix CI compiling errors

project is working absolutely properly, but CI is working not correct.
may can be helpful:
Error info

this bug was fixed by adding "dotnet restore" command in workflow, but, not sure is it that great solving of bug, closing it.


The Fast Track road to score is sometimes shown when a product does not need it

What

Reported by @stephanegigandet in the #mobileapp slack channel, and by others
The Fast Track road to score is sometimes shown when a product does not need it

Note: I'm not getting the issue. Questions to ponder: did Stéphane (or someone else) do something before the reporting the issue (like completing part of the product?). Was the product local cache/display up to date ?

https://fr.openfoodfacts.org/produit/20037154/pasta-sause-basil-combino
The fast track road to score is displayed when one of those is not populated (cf. ProductIncompleteCard.isProductIncomplete):

category (localized)
nutrition
ingredients (localized)

Perhaps we could play it even safer ("ceinture et bretelles") by checking first if nova, nutriscore and ecoscore are computed (which is good enough for us, and wouldn't have displayed the fast track paragraph in the 2nd screenshot).

Perhaps we could play it even safer ("ceinture et bretelles") by checking first if nova, nutriscore and ecoscore are computed (which is good enough for us, and wouldn't have displayed the fast track paragraph in the 2nd screenshot).

I +1 for this approach


WX-300 support

Please add support for the WX-300.

Any idea what the fingerprint is?

How do I look that up?

HomeSee has groovy code
Looks like the WX300 can have two IDs, depending on if it is in switch or dimmer mode
        // zw:Ls2a type:1100 mfr:000C prod:4447 model:4036 ver:1.11 zwv:7.15 lib:03 cc:5E,55,9F,6C sec:26,70,5B,85,59,5A,7A,87,72,8E,73,86
        fingerprint mfr: "000C", prod: "4447", model: "4036", deviceJoinName: "HomeSeer Wall Dimmer WX300" //WX300 in Dimmer Mode

        // zw:Ls2a type:1000 mfr:000C prod:4447 model:4037 ver:1.11 zwv:7.15 lib:03 cc:5E,55,9F,6C sec:25,70,5B,85,59,5A,7A,87,72,8E,73,86
        fingerprint mfr: "000C", prod: "4447", model: "4037", deviceJoinName: "HomeSeer Wall Switch WX300" //WX300 in Switch Mode

Not sure how to handle two virtual devices for one physical device. I made a wx300 and wx300s:
https://github.com/paulschreiber/smartthings-edge-drivers/commit/41b45228d481916e2d3174c3dc68b9881843b6b0


Angular.io for Korean

Hi. @naomiblack. I am interested in contributing to the localization project.
And I already translated the Angular.io to Korean(...and Pull request).
Please let me know how I can contribute to the localization project.
Thank you.
My email<EMAIL_ADDRESS>

Hi! My rule for localization for other languages is that we need a team because it is a lot of work, and we want to be sure there are enough people to keep the docs updated.
To start a team, I'd like you to pair with at least one other person as lead. In the meantime, I'll add you to our localization chat on Slack so you can find out how we're doing this for other languages.
Community members: If you're interested in contributing to the localization project for Korean, please comment here and let us know how to reach you!

@naomiblack  Hi! I'd like to contribute to the korean localization with @onyoon7 as a team.
my email is<EMAIL_ADDRESS>Thank you!

@naomiblack Hi, I'm also interested in participating in Korean localization project as a team with @onyoon7. Please contact me through<EMAIL_ADDRESS>Thx!

@naomiblack I want to help. I can also translate to Korean.
<EMAIL_ADDRESS>

Hi, @naomiblack :
I also want to contribute as a member.
<EMAIL_ADDRESS>

Hi @naomiblack @dvidsilva @Foxandxss
It is almost completed localization for Korean and expects to be completed before mid February.
How do we proceed with the deployment and domains?


Allow to disable auto generated routes

There should be the possibility to disable the creation of automatically created routes

Additionally, you should be able to specify that no route at all should be generated, eg. when the relevant service is a back-end µ-service which should be reachable by ingress traffic.
Also take into account existing Lagoon services,eg. node or node-persistent, which have a route.yml defined in their openshift-templates dir: this route definition should additionally be ignored and therefore not created.
(if developers still want to reach that backend µ-service, something like an oc port-forward on the openshift CLI would be a go to solution, hence authentication is covered and a only a non public route is available through the port-forward. Ops and sec teams would be thankful ;-)


Fix nuget link

Instead of hhttps use https

Hi @Eun, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;


ZEPPELIN-307: Added a new empty paragraph at the end of the note

Add a new paragraph when the note is autosaved

Change looks good. But can we have an unittest for it before merge?

Hi @Leemoonsoo,
I'm not sure but the test should not be used commitParagraph ....? which is exactly what I should do .... I'm a little confused.

Basically, a unittest that fails without this patch and passes with this patch.
I thought little bit more about this action. Current rule of paragraph creation is

automatically adds one after execution of last paragraph.
manually inserts between paragraphs.

And this patch changes to

automatically adds one, after execution of last paragraph.
manually inserts between paragraphs.
automatically adds one, after saving non empty last paragraph.

I think it could be confusing, if i see a new paragraph created automatically, while editing the last paragraph. Another strategy, with less confusing(i think) is,

automatically adds one, after execution of last paragraph.
manually inserts between paragraphs.
automatically adds one, when user starts editing the last paragraph.

I personally prefer the current rule, but what do you guys think?

I also prefer the current rule

Since the auto-save is timer based, I do agree it is confusing to see a new paragraph appearing by itself.
I agree with @Leemoonsoo that the 'add paragraph when editing last' is more predictable and potentially less confusing.

And sometimes one does not want a new paragraph created automatically


Cannot deploy to Cloudflare because of crypto

hi,
I am deploying my sveltekit app to Cloudflare Pages.
However, when I use your library I get error on the crypto module.
(I think from there https://github.com/ciscoheat/sveltekit-superforms/blob/0884bf305e20fe0a4ca2d8e02bdd731ed81bf39c/src/lib/server/entity.ts#L2)
I get this build error through GitHub actions:
Using @sveltejs/adapter-cloudflare
Error: R] Could not resolve "crypto"
    .svelte-kit/output/server/entries/pages/auth/login/_page.server.ts.js:5:19:
      5 │ import crypto from "crypto";
        ╵                    ~~~~~~~~

  The package "crypto" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.
error during build:
Error: Build failed with 1 error:
.svelte-kit/output/server/entries/pages/auth/login/_page.server.ts.js:5:19: ERROR: Could not resolve "crypto"

I see, it's not an important dependency, so I will find a way around it and will remove it for the next release.

It's gone now, in 0.5.22! Thanks for helping out. :)


ANNOUNCING: Template10-Validation version 1.0.1

There are several improvements, nothing significant. Perhaps the biggest improvement was the REMOVAL of Template 10 from the validation library since there was no reference anyway. Ha! I think I had that referenced by mistake. Should reduce the footprint. I also updated it to the latest NetCore; this should allow apps using it to also update and gain the improvements without duplicating their footprint requirement for the framework. Finally, fixed two real bugs. Special thanks to @Quico20 for bringing this to my attention. If you were using the validation library before, the errors are actually real, but not likely to impact you. Even still, the changes should make upgrading invisible.

Version 1.0.1
Upgrade to NetCore 5.3.3
Removed Template 10 from library
Corrected Model.IsDirty bug #9
Corrected Model.ValidateAfter bug #5

Can we all just agree that the validation demo app is the coolest ever?

Wow, i'm amazed you accepted my pull request, I feel so proud to have helped. Now we will have to fix the bug with Newtonsoft.Json
Thanks man!!! It is a pleasure to have helped a little bit!!!

Most definitely best interface... LOL 😁


/opt/prefect needs to be writable for memo_store.toml

Without this PR orion fails on startup:
ERROR:    Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 645, in lifespan
    async with self.lifespan_context(app):
  File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 540, in __aenter__
    await self._router.startup()
  File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 622, in startup
    await handler()
  File "/usr/local/lib/python3.10/site-packages/prefect/orion/api/server.py", line 288, in wrapper
    memo_store_path.write_text(
  File "/usr/local/lib/python3.10/pathlib.py", line 1154, in write_text
    with self.open(mode='w', encoding=encoding, errors=errors, newline=newline) as f:
  File "/usr/local/lib/python3.10/pathlib.py", line 1119, in open
    return self._accessor.open(self, mode, buffering, encoding, errors,
OSError: [Errno 30] Read-only file system: '/opt/prefect/memo_store.toml'
ERROR:    Application startup failed. Exiting.
Orion stopped!

@desertaxle we should probably write this file best-effort and not crash the application if it's read-only.

@desertaxle we should probably write this file best-effort and not crash the application if it's read-only.

For sure. I'll implement that in the core library. Another valid approach could be to disable block auto-registration memoization in the helm chart with the PREFECT_MEMOIZE_BLOCK_AUTO_REGISTRATION setting.

Hey @mluscon, thanks for reporting this issue and offering a PR! I've solved this problem using a different approach in #67, by mounting a writable home directory and /tmp directory. Can you take a look at that and see whether it resolves your issue?

superseded by https://github.com/PrefectHQ/prefect-helm/pull/67#pullrequestreview-1130737267


[FLINK-12877][table][hive] Unify catalog database implementations

What is the purpose of the change
This PR unifies catalog database implementations.
Brief change log

unifies GenericCatalogDatabase and HiveCatalogDatabase into CatalogDatabaseImpl
updates HiveCatalog accordingly
removes GenericCatalogDatabase, HiveCatalogDatabase, and AbstractCatalogDatabase
updates unit tests

Verifying this change
This change is already covered by existing tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

cc @xuefuz @lirui-apache @zjuwangg

Thanks @bowenli86 for the PR. One question is do we plan to differentiate generic and hive-native databases? Seems HiveCatalog tries to tell them apart by checking CatalogConfig.FLINK_IS_GENERIC, but we don't have test to create generic DBs?

@lirui-apache thanks for your review! After a discussion with @xuefuz, we felt it's not necessary to distinguish whether a database is generic or not. Thus I completely removed that part from the PR.
@xuefuz can you take a look?

@xuefuz thanks for your review!
Merging


Problem with authenticating via Tumblr

Hi,
I'm currently trying to authenticate via Tumblr OAuth1. Unfortunately I'm always getting the following error when coming back from Mobile Safari:
Error Domain=oauthswift.error Code=-1 "The operation couldn’t be completed. Oauth problem." UserInfo=0x7fc56290abe0 {NSLocalizedFailureReason=Oauth problem.}

I'm using the following URLs as mentioned on Tumblr docs
let requestTokenURL = "http://www.tumblr.com/oauth/request_token"
let authorizeURL = "http://www.tumblr.com/oauth/authorize"
let accessTokenURL = "http://www.tumblr.com/oauth/access_token"

Tumblr's documentation stated that their implementation is very similar with Twitter, but if I change the key/secret and the URLs to Twitter's API everything works fine.
Does anyone know what kind of problem I'm facing here? Could this be an Issue with the OAuth Library itself?
Thanks!
Edit: Tumblr Sends valid oauth_token and oauth_verifier Parameters back. The url looks just like when authenticating against twitter.

The problem seems to be that Tumblr adds the following URL fragment at the end of the callback: #=
So the parameters are overwritten in authorizeWithCallbackURL.
// until here everything is fine for both
if ((url.fragment) != nil && url.fragment!.isEmpty == false) {
    println("Tumblr goes here")
    parameters = url.fragment!.parametersFromQueryString()
} else {
    println("Twitter goes here")
}
// parameters for Tumblr are nil, Twitter is fine

Fix:
https://github.com/dongri/OAuthSwift/commit/1babc0f465144411c0dd9721271f239685ce83a9

Thank you @dongri !


Pass more Context to Viewer Functions + Cell Viewer

when a viewer's predicate is a map with a :wrapped key, its value is called against the whole wrapped value instead of just the value
the contents of the cell are merged into the wrapped value on which viewer functions operate
a cell viewer is added to allow a.o. to control the visibility of result or code programmatically.

I checked that slideshow viewer still works, as this is the usual suspect when changing the shape of a presented notebook. Moreover #593 is not a regression from these changes, I'll fix that in a separate commit.


test: add cloud-init hardening for tests

📝 Description
The quick-test playbook uses a cloud-init hardening configuration similar to https://gist.github.com/lgarber-akamai/39249a70b523013396ce6d513c1310c9
✔ How to Test
make quick-test
📷 Preview
If applicable, include a screenshot or code snippet of this change. Otherwise, please remove this section.

linode/alpine3.1x doesn't support cloud-init. We will need to switch to another image.


Explore and document how to write Universe package unit tests

Since your test in test/image.cue has package codecov at the top, and you're in the codecov package directory tree, you don't need to import the universe.dagger.io/alpha/codecov package and don't need to use codecov.#Image just #Image. Like this:
package codecov

import (
	"dagger.io/dagger"
)

dagger.#Plan & {
	actions: test: #Image & {}
}

Comment from user:

How does it handle ambiguous package names in different paths? My gut tells me staying explicit is generally better.

This makes sense because for example, several packages may have an #Image action/definition and these could conflict in a slightly more complex test.

@jpadams should we close this issue?


Misleading Label name

When viewiing other peoples profiles , projects link label title is View my project which references other users project, I suggest to delete word my from this title,so that only  View project remains
Screenshot

Ahh! @bumbeishvili I remember you reported a similar issue earlier in #6598 :sweat_smile:
Well I guess we can fix all of these occurrences!
Thanks! Am on it.


add rudimentary search

Couldn't figure out how to test it locally. Adds a basic search so @voloshink can link to specific lines using their timestamp/username/whatever.
Use like this: https://overrustlelogs.net/Destinygg%20chatlog/September%202018/subscribers?search=search text

Should be fixed I think


DLL Not Found Exception (Although I tried all that has been mentioned)

Plugin Version or Commit ID
v0.10.1
Unity Version
2021.3.4f1
Your Host OS
macOS (M1 Chip)
Target Platform
UnityEditor, Android
[Windows Only] Visual Studio C++ and Windows SDK Version
No response
[Linux Only] GCC/G++ and GLIBC Version
No response
[Android Only] Android Build Tools and NDK Version
Build Tools: 30.0.2
NDK: 21.3.6528147
[iOS Only] XCode Version
No response
Command Sequences
Followed all of the steps in the installation section and I used the following command to build libs for Editor and Android

python3 build.py build --desktop cpu --android arm64 -vv

And It gave me the same error
DllNotFoundException: mediapipe_c assembly: type: member:(null)
and then I tried this
python3 build.py build --desktop cpu --android arm64 --opencv cmake  -vv
and still gave me the same error
Log

python3 build.py build --desktop cpu --android arm64 -vv

python3 build.py build --desktop cpu --android arm64 --opencv cmake  -vv

Additional Context
No response

Have you read https://github.com/homuler/MediaPipeUnityPlugin/wiki/Installation-Guide#dllnotfoundexception? (especially No.5)
Please also check https://github.com/homuler/MediaPipeUnityPlugin/issues/679#issuecomment-1200869407.

Thank you very much the issue is solved in the Unity Editor but the Android build (Hand Tracking Scene in the samples) is not starting the camera unless I switch to video and then to camera back and when I do that it doesn't detect anything
I also tried to logcat to see any issues but nothing is showing as an error
Build Tools: 30.0.2
NDK: 21.3.6528147
Test Device: Android 11 (API 30)
If you can help me with this I would be grateful

If you built only the Hand Tracking Scene, then maybe #681 is the same issue.
If it doesn't solve your issue, please share the steps to reproduce it (describe in a way that anyone can reproduce it in their local environment) and the Player.log (adb logcat Unity:V native:V tflite:V CRASH:E AndroidRuntime:E "*:S").
By the way, will you tell me what was the cause?

Thank you very much the issue is solved in the Unity Editor

P.S.
In practice, when building the sample app, you should not modify Scenes in Build if unnecessary.
By default, each scene is configured to work on UnityEditor, but not on other platforms.
For example, if you import this plugin to your project, each sample scene will work on your UnityEditor, but it won't work on your Android devices unless you copy dependent resources to Assets/StreamingAssets and change the AssetLoaderType to StreamingAssets.

Thanks for your response, Regarding the previous problem this command fixed it for me
python3 build.py build --desktop cpu --opencv cmake --macos_universal --ios arm64 -vv
Regarding the Android Problem I switched the AssetLoaderType to StreamingAssets and copied all the files there (Assets/StreamingAssets) and that made the camera initialize successfully but It didn't detect the hands
Player.log
And this is the Player.log file

By the way I used this command instead so I can build the android libs
python3 build.py build --desktop cpu --opencv cmake --macos_universal --android arm64 -vv
And the android is ARM64 I checked it

I switched to GPU inference mode and the Hand Tracking worked!! Thanks for your cooperation I appreciate it and sorry for spamming!!

Thanks for your response, Regarding the previous problem this command fixed it for me
python3 build.py build --desktop cpu --opencv cmake --macos_universal --ios arm64 -vv

I'm more interested in the cause, not how you fixed, but it's not important, so please let me know only if you find that.
P.S.

this is the Player.log file

You should check Development Build. Otherwise, most log messages won't be output.


feat(solana): update to 1.17.3 for installation

Description of changes
Update to 1.17.3 for installation.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Did you try to build this ? The sha256 and the cargosha should both change as well. (If you try to build , it should give you the correct sha to replace )

Done in #301355.


incompatibility with last version of freezed

Because intl_utils >=1.9.0 depends on intl_translation 0.17.10+1 which depends on analyzer ^0.39.12, intl_utils >=1.9.0 requires analyzer ^0.39.12.
And because freezed 0.12.3 depends on analyzer >=0.40.4 <1.0.0 and no versions of freezed match >0.12.3 <0.13.0, intl_utils >=1.9.0 is incompatible with freezed ^0.12.3.

sorry for that, mess in my cache


log warning if creation of task to generate widget was skipped

ISSUE:
All attempts (from schedule) to add new task for widget content generation will be quietly skipped if there is already exists queued/active task to generate widget content.
AFTER:
log warn message if there is possible stale task for widget content generation:
[2020-09-01T04:00:13.585778 #14248:330f68]  WARN -- : MIQ(MiqWidget#queue_generate_content) Widget: [Tenant Quota MC] ID: [1000000000025] Skipping task creation for widget content generation. Task with name "Generate Widget: 'Tenant Quota MC' already exists"

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1861046
@miq-bot add-label ivanchuk/yes, jansa/yes?

Jansa backport details:
$ git log -1
commit e81b9262c44dbef71739d352ae3a433dd9063bc0
Author: Gregg Tanzillo<EMAIL_ADDRESS>Date:   Tue Sep 1 18:37:13 2020 -0400

    Merge pull request #20505 from yrudman/log-warning-when-widget-generation-skipped

    log warning if creation of task to generate widget was skipped

    (cherry picked from commit 54df34293009c6ab1176466424bb269f4c9d1e5b)


Error loading resource (python not found)

When I run ai init I see the error saying that python was not found. It is in my PATH and installed. Any idea?

This may be a dupe of #67 it looks like the CLI may be throwing the wrong error message


Updates to upgrade instructions for 1.3

Updates to the install instructions to call out ordering of meta and data....also updating the instructions to call out removal/addition of the data nodes from the load balancer during the upgrade.
fixes #1304

fixes 1307


FYI: Meteor will be getting native support for waitOn, template-level

From Meteor's History.md:

v.NEXT

Template instances now have a subscribe method that functions exactly like Meteor.subscribe, but stops the subscription when the template is destroyed. There is a new method on Template instances called subscriptionsReady() which is a reactive function that returns true when all of the subscriptions made with TemplateInstance#subscribe are ready. There is also a built-in helper that returns the same thing and can be accessed with Template.subscriptionsReady inside any template.

Update: this was rolled into v1.0.4. Methinks iron-router waitFor should be deprecated, because Meteor now has a built-in alternative, which allows for more granularity (a sidebar with unimportant info can still be loading while the rest of the page is usable).

waitOn is just a convenience when you don't need the extra control provided by adding things to the waitlist, checking for their readiness, and choosing what to render (loading v template). So the point is not just applicable to waitOn but subscriptions and the waitlist.
Having said that there are still plenty of instances where doing subscriptions in the router can be useful.


Update resolver - Massage bounds

This PR adds some future-proofing to Pact, and updates the bare-minimum of code to do so.

What specifically is driving this upgrade? If it's not for production chainweb then let's avoid merging CPP compat stuff.

@slpopejoy I discussed this with @fosskers and we decided to leave this branch as-is and wait until the upgrade is in.  Then we can merge this branch without the CPP.

:+1: to what @mightybyte said.
The specific motivations for the PR were:

Can't hurt to future proof (the CPP is a temporary stop-gap, as noted)
I wanted the most recent LTS for my hobbyist Linux terminal wallet, which depends on both Pact and Chainweb.

Closing w/o deleting branch to keep the PR list clean, feel free to reopen for further developments


How to specify a network adapter to send a UDP broadcast?

I have a network adapters that has four separate Ethernet ports (e.g. eth0, eth1, eth2, eth3) and all the ports have different IP address. Is it possible to specify port that I want to communicate on?

I don't think this is supported in the plugin atm, you may want to identify the lower level Unreal call required on the ISocketSubsystem to select an adapter (see e.g. https://docs.unrealengine.com/4.27/en-US/API/Runtime/Sockets/ISocketSubsystem/GetLocalAdapterAddresses/) and when you've identified the calls required, make a pull request here with code changes and I'll merge the feature support.

@gstorer
Thank you for your detailed response. I have resolved by setting SendIP and ReceiveIP manually.


feature/load-external-json-file

fixed regex for including external json files
better solution than https://github.com/coderhaoxin/gulp-file-include/pull/149

Coverage decreased (-5.6%) to 78.571% when pulling 6da3806735b7d71f075da2131dbdf90b538c0b9b on media-square:feature/load-external-json-file into 5897e85ba4a2e36afa8e08c3dd2150bf7799d916 on coderhaoxin:master.


[FZ] Zone editor has two separate entries in Alt+Tab

Duplicate of https://github.com/microsoft/PowerToys/issues/1380


Features : Add support for renaming and deprecating

Reported in https://github.com/devcontainers/features/issues/123, there is a request to rename an existing Feature (docker-from-docker to docker-outside-of-docker). Currently, if we simply rename all the docker-from-docker references (ie. source code, and Features metadata) to docker-outside-of-docker , then the CLI will publish this as a new Feature.
In this case, people referencing to docker-from-docker will get stuck and not get any updates until they manually change it to docker-outside-of-docker. In order to prevent this and add backwards compatibility, as discussed in here, we can add a new alias property to devcontainer-feature.json to safely rename a feature.
Adding this new alias property will be beneficial for the community, it will provide an ability to rename any Feature without any dev config breaks.
From https://github.com/devcontainers/features/issues/123#issuecomment-1249890748 👇

We decided to move forward with the alias idea so that we can safely rename a feature, and if the devcontainer-feature.json has an alias property, we will continue to publish it under the aliased name. So the source code and everything can move to the new name, but we will publish both old and new names for backwards compatibility.
When we next bump up the major version, we will likely remove the alias since major version bumps already signify breaking changes and that's a good time to fully stop publishing the old name.
Once we implement alias support, we will rename docker-from-docker to docker-outside-of-docker.

Goal
Allow renaming an existing Feature with dual publishing.
Proposal
Add a new alias property to the devcontainer-feature.json -

Property
Type
Description

alias
string
Set if the Feature needs to be published under an aliased name. The property is useful for renaming an already published Feature.

Renaming a Feature
An already published Feature can be renamed by adding an alias property to the devcontainer-feature.json. The source code can be changed to a new name along with devcontainer-feature.json properties (like id, name, documentationURL etc). The value of alias property is the current id of the Feature which needs renaming.
The supporting tools will publish the Feature with both old (using alias property) and new (using id property) names.
Notes

As the id of the current Feature will be changed, the devcontainer-collection.json will no longer contain the old id.

I'd suggest renaming alias to something less neutral - perhaps a deprecatedIds array that we will still publish to, but that we can handle appropriately in downstream tooling. What do you think?

When I wrote this proposal of adding this new property for renaming a Feature, it was keeping the registry and namespace intact. It could simply change the id. (eg. ghcr.io/devcontainers/features/x can only be renamed to ghcr.io/devcontainers/features/y).
If we decide to support renaming across namespaces (even across registries in future), then we'd need more authentication. A simple GITHUB_TOKEN won't be sufficient in this scenario. 🤔 Not sure if we'd want to currently support that or wait for a request from the community for cross namespace renames.
What do you think @Chuxel ?

If we decide to support renaming across namespaces

I think a good first pass for this would be re-aliasing inside a single namespace.  The property could even just accept an ID (for now),
{
  "id": "docker-outside-of-docker",
  "deprecatedId": [
    "docker-from-docker"
  ]
}

and if we wanted to extend this in the future, we could additionally allow fully-qualified identifiers as well (eg: docker.io/<my_new_namespace>/docker-from-docker).
I think for now, erroring this case would be fine (until we got feedback such behavior would be useful)

Would the tar at the old location have the exact same content as at the new location? I guess the "deprecatedIds" (plural I assume?) can be picked up by the indexer and included in the index, so UIs can decide to show an info/warning when a devcontainer.json uses the old id?

Iterating the proposal to accommodate https://github.com/devcontainers/spec/issues/155. Formalizing a detailed proposal and also, extending the proposal to make the Templates adapt to this proposed change as well and adding.
Adding two new properties to the devcontainer-feature.json  👇
ℹ  For simplicity and to avoid confusion, writing the proposal by referring Features and it's spec. However, the same two new proposed properties will also be added to devcontainer-template.json
alias

Type: array and default value: []
This property will be useful to rename a currently published Feature within a single namespace.
The value of this alias property would be the old ids which were used to publish the Feature
The source code can be changed to a new name along with devcontainer-feature.json properties (like id, name, documentationURL).
The distribution tools like Dev Container CLI and Dev Container Publish GitHub Action will dual publish the old ids (which is defined by the alias property) and the new id.

Example: Let's say we currently have a docker-in-docker Feature 👇
Current devcontainer-feature.json :
{
    "id": "docker-in-docker",
    "version": "2.0.1",
    "name": "Docker (Docker-in-Docker)",
    "documentationURL": "https://github.com/devcontainers/features/tree/main/src/docker-in-docker",
    ....
}

We'd want to rename this Feature to docker-outside-of-docker. The the source code folder of the Feature will be renamed to docker-outside-of-docker and the updated devcontainer-feature.json will look like 👇
{
    "id": "docker-outside-of-docker",
    "version": "2.0.2",
    "name": "Docker (Docker-outside-of-Docker)",
    "documentationURL": "https://github.com/devcontainers/features/tree/main/src/docker-outside-of-docker",
    ....
}

Note - The semantic version of the Feature defined by the version property should be continued and should not be restarted at 1.0.0.
How backwards compatability can be handled for the installsAfter property when a Feature is renamed

Currently the installsAfter property is defined as an array consisting of the Feature id that should be installed before the given Feature.
The Feature to be renamed could be already defined by other Feature authors in their installsAfter property. Renaming the id could change the installation order for them if the installsAfter property is not updated with the new id. In order to avoid this unexpected behavior and  to support back compat, the CLI tooling will be updated to also look at the alias property along with the id for determining the installation order.

Few ways in which the alias property will be used by the supporting tools
- [Dev Container Publish GitHub Action](https://github.com/devcontainers/action) which auto-generates the README files can add a note with a list of old `id`s which were used to publish this Feature.
-  In the scenarios where Dev Configs are referencing the old `id`s,  the VS Code extension hints could be enhanced to deliver this warning that the `id` was renamed to a new one.
- The [containers.dev/features](https://containers.dev/features) website, and [supporting tools](https://containers.dev/supporting) like [VS Code Dev Containers](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) and [GitHub Codespaces](https://github.com/features/codespaces) wouldn't list the old `id`, instead list the new `id` of Features.
    - The [putManifestWithTags](https://github.com/devcontainers/cli/blob/main/src/spec-configuration/containerCollectionsOCIPush.ts#L172) will be modified. The same `tgz` file for the `id` will also be pushed to the `id`s  mentioned by the `alias` property for all the [tags](https://github.com/devcontainers/cli/blob/main/src/spec-configuration/containerCollectionsOCIPush.ts#L175).

isDeprecated

Type: boolean and default value: false
If this property is set to true, then it indicates that the Feature is deprecated and won't be receiving any further updates/support. The OCI artifacts would exist, hence, the current dev configs will continue to work.
This property could be used by the supporting tools to indicate Feature deprecation in few ways -

Dev Container Publish GitHub Action which auto-generates the README files can be updated to add a top-level header mentioning it's deprecation
The containers.dev/features website, and supporting tools like VS Code Dev Containers and GitHub Codespaces wouldn't list the deprecated Features.
VS Code extension hints could be enhanced to deliver this information about it's deprecation

Would the tar at the old location have the exact same content as at the new location?

@chrmarti Yes, same exact tgz of the new id will pushed to the old id. Described it in detail in https://github.com/devcontainers/spec/issues/146#issuecomment-1353625555

I'd suggest renaming alias to something less neutral - perhaps a deprecatedIds array that we will still publish to, but that we can handle appropriately in downstream tooling. What do you think?

In an offline discussion, decided to keep the property name as alias.  As interpreted from https://github.com/devcontainers/spec/issues/155 and from a group discussion, we've realized that the term deprecated could be perceived in two different ways. Deprecated either means there will be no support for some piece of code or some code is deprecated in favor of something else. To avoid this misinterpretation, decided to stick with alias // cc @joshspicer

I guess the "deprecatedIds" (plural I assume?) can be picked up by the indexer and included in the index, so UIs can decide to show an info/warning when a devcontainer.json uses the old id?

@chrmarti Yep, Yep! Added details in the comment above.

alias (or rather aliases?) to me means "equally valid ids". Do we want users to move off of these? If so, maybe oldIds or legacyIds would be clearer?
Maybe deprecated is more common than isDeprecated? (E.g., JSON schema itself uses deprecated.)

Example: Let's say we currently have a docker-in-docker Feature 👇

Probably docker-from-docker?

alias (or rather aliases?) to me means "equally valid ids". Do we want users to move off of these? If so, maybe oldIds or legacyIds would be clearer?

Yep, makes sense to me. I like legacyIds 👍

Maybe deprecated is more common than isDeprecated? (E.g., JSON schema itself uses deprecated.)

Good call 👍  sounds good.

Formalized to a PR --> https://github.com/devcontainers/spec/pull/163

Closing as completed with https://github.com/devcontainers/cli/pull/346 & https://github.com/devcontainers/cli/pull/335  🚀

Thank you for implementing this.
I tried setting deprecated, but is deprecated still not included in the metadata?
Or is it just a problem with the display on the log?
https://github.com/eitsupi/devcontainer-features/actions/runs/3834679292/jobs/6527285373#step:3:61

For deprecated we haven't changed any CLI logic, or updated the metadata.
The flag will only be used by the supporting tools to highlight its deprecation.
We are still allowing publishing this Feature, in case of a security vulnerability.
More details: https://github.com/devcontainers/spec/pull/163/files#diff-af72b90352b50d5f93c0dc94d88eba484e95de30f4c6fa6797ae2a1debe33034R75

Thanks, however, it was not my intention to republish this Feature in the index. (See #155)
Will deprecated Features be removed from the index in the future?

Yes, I am planning to update the indexing logic to make use of deprecated flag.
ℹ For the devcontainers/action, I merged a change to update the README file with this info --> https://github.com/devcontainers/action/commit/977880a0a17dd1f95b04cba35bf1b6722d9e75be

Sounds good!
The action now works fine.
https://github.com/eitsupi/devcontainer-features/blob/main/src/just/README.md

Yes, I am planning to update the indexing logic to make use of deprecated flag.

PR --> https://github.com/devcontainers/devcontainers.github.io/pull/120

@eitsupi  https://containers.dev/features no longer lists the deprecated just Feature! 🎉


Granting database role SNOWFLAKE.CORTEX_USER to another role fails

Hi,
I am trying to grant the database role SNOWFLAKE.CORTEX_USER to another role with the following config:
role_grants:
  - role: SNOWFLAKE.CORTEX_USER
    to_role: CORTEX_ANALYST_ROLE

But I get the following error:
failed to execute sql, [GRANT ROLE SNOWFLAKE.CORTEX_USER TO ROLE CORTEX_ANALYST_ROLE]
I would expect the following sql to be executed:
grant database role SNOWFLAKE.CORTEX_USER to role CORTEX_ANALYST_ROLE
titan-core version: 0.10.21
Role used: ACCOUNTADMIN
Did I miss anything in my config?
Thansks!

This is related to https://github.com/Titan-Systems/titan/issues/164 which should be fixed in the future v0.11 release

Fixed in v0.11.0. Use the new DatabaseRoleGrant resource.


Add get_each_mut methods on RawTable and HashMap

This PR adds a new method get_each_mut on RawTable and new methods get_each_mut and get_each_key_value_mut on HashTable. These methods enable looking up mutable references to several table or map entries at once. They take advantage of min_const_generics, which is available without a feature gate on recent nightly (but not stable) compilers. Hence everything is behind #[cfg(feature = "nightly")] for now.
Closes #151 (cc @HeroicKatora).

Okay, fixed the problems I could find on my own, so this should be ready for review.

@bors r+

:pushpin: Commit afce0976ebe6646d789328d5e3475ad7d581f677 has been approved by Amanieu

:hourglass: Testing commit afce0976ebe6646d789328d5e3475ad7d581f677 with merge de77272ec9faa18a61eca113137ab131c8410696...

:sunny: Test successful - checks-travis
Approved by: Amanieu
Pushing de77272ec9faa18a61eca113137ab131c8410696 to master...

Thanks!


Move BiBTeX references to separate module for clarity

The BiBTeX references injected into the @due.dcite decorations clutter up some of the modules with a lot of text. We could move these all to their own module (references?) and then just import and inject the pre-formatted refs for clarity.

Something like this? If so, I can do it.

Yep, exactly!


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v2.6.27 to before v5.15.13",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=61a7e26028b94805fd686a6dc9dbd9941f8f19b0",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=08eacbd141e2495d2fcdde84358a06c4f95cbb13"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "61a7e26028b94805fd686a6dc9dbd9941f8f19b0",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "08eacbd141e2495d2fcdde84358a06c4f95cbb13",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "net: fix use-after-free in tw_timer_handler\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.13 by commit 08eacbd141e2495d2fcdde84358a06c4f95cbb13, it was introduced in version v2.6.27 by commit 61a7e26028b94805fd686a6dc9dbd9941f8f19b0. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000053


Fatal Exception: java.lang.NullPointerException: okhttp3.Cache$Entry.readCertificateList

We have a few Android TV users (don't now it's related to Android TV) that gets a crash in a custom interceptor we have. Its not that many users but they are however getting this crash a lot.
This is an example of the stacktrace after we call proceed(), so I'm sure if we can do anything in our end (other than catching the exception):
Fatal Exception: java.lang.NullPointerException:
       at okhttp3.Cache$Entry.readCertificateList(Cache.kt:612)
       at okhttp3.Cache$Entry.<init>(Cache.kt:534)
       at okhttp3.Cache.get$okhttp(Cache.kt:178)
       at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:47)
       at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
       at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83)
       at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
       at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
       at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
       ...

Similar to https://github.com/square/okhttp/issues/6260

I can't see how it can happen, but even a corrupted cache file, causing base64 decode should fail, should be a IOException.
Will fix and backport to 4.x

Android TVs often work in mysterious ways! But sounds awesome you'll make a fix.
I forgot to mention at first, but in our project is using Retrofit 2.9.0 and have a reference to OkHttp 4.11.0 as well - not sure if that makes a difference.


Convert render_charts to simple tag for jinja2 support

This allows the tag to be called easily from jinja2:
from wagtailcharts.templatetags.wagtailcharts_tags import render_charts
from jinja2 import pass_context

# later...
self.environment.globals.update(
    {
        "render_charts": pass_context(render_charts),
    }
)

The template doesn't use any context, but it's passed in anyway for backwards-compatibility (and because it's no real extra work).
Usage of the tag isn't changed, so this is non-breaking.

Thanks @RealOrangeOne

This has been released in version 0.6 on pypi


Token program - transfer with external fee payer

It should be possible to transfer tokens using external account for fees.
See #79 and #80.

Merged.


CTIS Paybook - Added support for OrgnizationUUID

Change(s):

Added support for OrgnizationUUID
readme.md file updates
Deploy button links updated

Reason for Change(s):

New feature requests

Version Updated:

Not required

Testing Completed:

Yes

/package

/package


Could someone help me validate if I am collecting the reports correctly (attribution-report NODE JS version)

Hello everyone, I'm currently trying to create a version of attribution-reporting in NODE JS so far so good, I managed to complete the entire journey (trigger interactions with creatives, conversion on the final website, generate event and aggregable reports)
But I got to this part where I must store the aggregatable reports before sending them to the aggregation services, I wanted to know if anyone else did this step of collecting the reports in NODE JS
Below is the code responsible for collecting and storing the reports (I took the documentation code written in GO as a reference)
*Spoiler: Each report record I receive generates an .avro file
const avro = require('avsc');

const REPORTS_AVRO_SCHEMA = {
    "name": "AvroAggregatableReport",
    "type": "record",
    "fields": [
        { "name": "payload", "type": "bytes" },
        { "name": "key_id", "type": "string" },
        { "name": "shared_info", "type": "string" }
    ]
};
const RECORD_SCHEMA = avro.Type.forSchema(REPORTS_AVRO_SCHEMA);

const registerAggregateReport = (req, res) => {
    try {
        // const report = req.body;
        // Example to illustrate what the request body would be
        const report = {
            "aggregation_coordinator_origin": "https://publickeyservice.msmt.aws.privacysandboxservices.com",
            "aggregation_service_payloads": [
                {
                    "key_id": "bbe6351f-5619-4c98-84b2-4a74fa1ae254",
                    "payload": "7K9SQLdROKqITmnrkgIDulfEXDAR76XUP4vc6uzxPwDycQql3AhR3dxeXdEw2gbUaIAldnu33RSN4SAFcFFKgDQkvnhFzPoxJjO2Yfw4osJ1S0Odp0smu0rC5k5GuG4oIu9YQofCPNmSD7KRVJ9Y6Lucz3BXoI3RQhpQkO31RDyxVJdBbJ8JiS2KBtu8naUf5Z+/mNNKp39ObsNbo7kQKI0TwyRJDSJKqv42Yi3ctoAhOT0eaaUtMfho67i9XaEtVnh8wB4Mi+nzlAfVsGIavP6aXWDe44IgKZvTS/zEKjI68+nzWkyfdRNOf7jtb2XnoB7k5iM+Yu9Ayk5ic/aT1eA1iPEzLvW/tNLcohne3UL2DefZoTLb5l9aludA7Qlf0g+kW9nuvUSmHBuTjE/fTY5s9uRExHH+b2Hjm2sL9DyrFZUFqcl/KLS+McgOT8I0ZTpPRmr+njW8+4b01Hsc2MpY3KKAn1jUDUE45pGbhj/Gqlb1ikJO9nNKS/nnWJgR7+3P8JEpHC2fkfEase4+vrNxZujWolYfTUxswJpiEZs1+fCOroEyyEY6Zjvx5qLbk+7wMNqCeCltDPA6c8WtAPtMreIUvKbco6XUUzaGSnvWLz6/WJqCxG4hjPOfcYAWXIwSboqvNyBHrRr4H5V7C0unSkIjd0j/GeB3ywgnKEqiihuvZ5PPw+O5aYqJdaR3QEFZtpLj+3Uv4OGn2+CvU1thV0A0H1XViP846Tfmb0jVejN1+ih+VO5cf/7T2TPz6oGO9sa6qitWtll5vhwxVyG3vniCo3xghGnUcHSP5ogfp6qgDGSgsGFqSvdiuOpQU+MG/HrCDUjvce0GoXJP6674UcurGxR9UKAnVwZyKRIj/q9qzUgxhWEFC3ssADMmxhZBs3X+rrAxKfhXD12MfuUluRTCzpCKZ9/YapnJQYjngGx7GIkfW6tw8eSCC8yO41vWyHGRz4nKlgNeQkwYafGPzXqUXjyEyiupMUlmSsU/zT52wdCQYLJbQg7xhNuLebb8qh9LW07jMho4Vo9DBP9l463uqA8hcZnJ"
                }
            ],
            "shared_info": "{\"api\":\"attribution-reporting\",\"attribution_destination\":\"https://cliente.com\",\"report_id\":\"4d82121f-7d62-4fa4-bda4-a70c9e850089\",\"reporting_origin\":\"https://attribution.ads.uol.com.br\",\"scheduled_report_time\":\"1714764978\",\"source_registration_time\":\"0\",\"version\":\"0.1\"}"
        }

        report.aggregation_service_payloads.map(payload => {
            const payloadBytes = Buffer.from(payload.payload, 'base64');
            const record = {
                payload: payloadBytes,
                key_id: payload.key_id,
                shared_info: report.shared_info,
            };

            const outputFilename = `./reports/output_reports_${Date.now()}.avro`;
            const encoder = avro.createFileEncoder(outputFilename, RECORD_SCHEMA);
            encoder.write(record);
            encoder.end()
        });
        res.status(200).send('Report received successfully.');
    } catch (e) {
        console.error('Error processing report:', e);
        res.status(400).send('Failed to process report.');
    }
};

module.exports = {
    registerAggregateReport
}

*English is not my native language so take it easy
As the death of third-party cookies is something that will affect everyone, it would be nice to have references in more commonly used languages such as NodeJs, Java, etc., I hope this post can contribute in some way to this

Hi @dbrito ,
This looks about right. I see that your payload is base64 decoded and converted to a bytestring. And the key_id and shared_info are strings. Converted into the aggregation service report avro schema.

@maybellineboon thanks!
Just one question, the part where each "aggregation_service_payloads" in the report becomes an .avro file is also correct, right?
In this case, there is no scenario where I will receive more than one "aggregation_service_payloads" per report and I have to store these records in the same .avro file, right?

hi @dbrito ,
You can either collect all the json reports and convert them into a single file or you can create separate avro reports. For better performance, it is recommended to split the number of reports to the number of CPUs for your Aggregation Service instance. For example, you have 1,000 reports with 6 CPUs, you will have 6 files and the 1,000 reports will be split into 6 files.
Also, when batching, we do recommend to follow the batching strategies doc.

Thanks !
I'll take a look


chore: update poms to SNAPSHOT version for dev

Issue #, if available:
Description of changes:

Checklist

[ ] Meet tenets criteria
[ ] Update tests
[ ] Update docs
[ ] PR title follows conventional commit semantics

Breaking change checklist

RFC issue #:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report
Patch and project coverage have no change.

Comparison is base (b191d72) 79.19% compared to head (3f433a4) 79.19%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff            @@
##               main    #1299   +/-   ##
=========================================
  Coverage     79.19%   79.19%
  Complexity      639      639
=========================================
  Files            73       73
  Lines          2360     2360
  Branches        258      258
=========================================
  Hits           1869     1869
  Misses          410      410
  Partials         81       81

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


Using the package with Laravel 5.4 and Sentinel

Hello,
I've managed to load the sidebar, extend it and render it, all looks pretty awesome. I experienced some difficulty with using Sentinel inside SidebarExtenders to display some of the menus based on the permissions of the user. Unfortunately, when I try to access Sentinel it's always a empty object. I found that from Laravel 5.3 there is а change how classes are loaded and you can not access Auth (maybe Sentinel also) within __construct methods and while Laravel boots because actually there is still no real request. That's a problem because we load the sidebar using dependency injection inside the __construct method of our AdminController. So my questions are:

Does this package supports using of Sentinel inside it for Laravel 5.4?
Or can we somehow load the sidebar inside a middleware maybe? (Where Sentinel is available and works)

Thanks in advance.

Hi,
I'm also using sentinel inside the extenders, and they're working as expecting. They're able to get the current user etc.

Try resolving it through a view creator like in the docs.


Convert channel to alpha?

I have a grayscale image with alpha channel.
I'm trying to modify or generate a new image that takes the original grayscale data and uses it as alpha.  I want the black in my original img to be transparent and white to be opaque, and everything in between.
I know I can extract the alpha (I presume?) by:
var img = sharp("image.png")

// Extract the grayscale channel?
var gray = img.extractChannel(0)

// Now how do I use this as alpha?

but I'm not sure where to go next?
(Sorry, brand new to this sharp library!  Appreciate any help - thanks!)

Hello, if the "image.png" PNG is already single-channel without an alpha channel of its own then you can use it directly with joinChannel.
For an input of 1 or 3 channels to produce an output of 2 or 4 channels respectively, use something like:
sharp('rgb.png')
  .joinChannel('greyscale.png')
  .toFile('rgba.png');

Hi.
Thanks for your feed back.
The following code I believe achieves what I'm trying to do, but could you suggest how I could do it without writing the intermediate images?
Thanks again
const sharp = require('sharp');

doStuff()

async function doStuff() {
    var img = sharp("orig.png")

    // Extract the grayscale channel (which will be my new alpha)?
    var alpha = img.extractChannel(0)
    await alpha.toColorspace("b-w")
        .toFile("newAlpha.png")

    // Extract my alpha, which will be the new image
    var gray = img.extractChannel(1)
    await gray.toColorspace("b-w")
        .toFile("newGray.png")

    sharp('newGray.png')
    .joinChannel('newAlpha.png')
    .toFile('good.png');

    }

Thanks for the update, glad you got it working. Intermediate images will be required for this scenario.


chore: update travis ci badge

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

v1.15.5
GitHub release

Your semantic-release bot :package::rocket:


Updated mod to 1.20

Edit: Sorry wrong branch selected on the first PR
I updated the mixins, gradle configs, fabric configs over to 1.20. I built it, and it works on a 1.20 installation. No changes were made to the code, it's just the configs that I updated.

Doesn't work on 1.20.1 - I tried changing it manually but it crashes on startup (I can still submit a code revision tho if it's easier)

I am not a Java dev nor Minecraft mod dev so I have no idea how to make it compatible with all 1.20 versions, you should submit a revision since I practically don't know what I am doing


Utils - Add multibyte and UTF-8 support

Fixes #5297

I know this looks like scope creep, yet I feel like if we go this way we should take care of some other points in the code effected by this as well.
There are a few spots we do function_exists('mb_*. With the polyfil now added we should check if these will now always return true. We have to check if these have no unwanted side effects (for example if the polyfil does not behave exactly as the extension).
Places are:

https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/v3.2.1/src/Cache/Signature.php#L94
https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/v3.2.1/src/Fixer/Phpdoc/PhpdocAnnotationWithoutDotFixer.php#L123
https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/v3.2.1/src/Fixer/Alias/MbStrFunctionsFixer.php#L61

For the last one, MbStrFunctionsFixer, I think that one is already good as it checks if the functions are internal.

Thank you @paulbalandan.


Connect to Arc Controller has scrollbar at bottom

@ranasaria Something to look at if you get a chance


[HOLD for payment 2024-11-28] Update the Switch to Expensify Classic survey to drive better feedback

Problem: We are currently prompting people who Switch to Classic with a modal asking for a reason.  But we do it inconsistently (on web but not mobile), and there are too many results to look at, and the results are kind of useless because they include known complaints from users we don’t actually think should be using New Expensify, and that we aren’t going to prioritize.
Solution:
Case 1: People that are redirected into NewDot.

This user group has the NVP tryNewDot.classicRedirect.dismissed set to false
We show them the existing survey when they click Switch to Expensify Classic in Settings.
We add a new page to the start of the flow to offer a call to speak to a product manager. Clicking Book a call will open this Calendly link in a new browser tab, and closes the RHP modal when clicked.
Make the free form response page in the survey not mandatory anymore

Copy:
**Would you like to speak to a product manager?**

By switching to Expensify Classic, you will miss out on:
* Chatting directly on expenses and reports
* Ability to do everything on mobile
* Travel and expense at the speed of chat

We'd be excited to get on a call with you to understand why. You can book one with one of our senior product managers to discuss your needs.

[No thanks]
[Book a call]

[Internal - NW] Keep creating GHs for the research team. Engineering don't need to worry about this.

Case 2: People not redirected into NewDot

This user group has no tryNewDot NVP OR tryNewDot.classicRedirect.dismissed===true
We do not show them the survey when they click Switch to Expensify Classic in Settings.
Instead, we show them a new page to educate them on how to go directly to Expensify Classic next time.

Copy:
Quick tip...
You can go straight to Expensify Classic by visiting expensify.com. Bookmark it for an easy shortcut!
[Take me to Expensify Classic]

[Internal - DV/TRJ] Track the button click on that page separately in FullStory, so we can see how many keep hitting this flow going forward and continue to try and curb it if it remains high. I've purposely labelled this button slightly differently to Case 1 to make it easy for us to do that.

Issue OwnerCurrent Issue Owner: @trjExpensify

This is going to be implemented on web and hybrid app, correct? cc @AndrewGable

Yes it should be implemented on all platforms 👍

Asking for the next steps, let's try to make quick progress on this one!

Updated the solution OP to reflect where we landed. My next steps:

Get the Calendly link to include
Confirm if any of this actually needs backend (I don't think it does).
Get someone to start on it.

I've been chatting to Hans and confirmed we don't need any backend here. He's going to take on the implementation for us, starting today (tomorrow his time).
Working on getting the calendly link, and I'll add it to the OP.

Added the Calendly link to the OP, @hungvu193.

Thanks Tom, I'll prepare a PR today!

I created a PR here: https://github.com/Expensify/App/pull/52526
Also waiting for confirmed translations here:
https://expensify.slack.com/archives/C01GTK53T8Q/p1731572881369449

Created a draft PR for the tests here:
https://github.com/Expensify/App/pull/52754

👋 @shubham1206agra can we get the checklist please?

I've created a regression test request based off the tests I wrote for it in the PR here.

Payment summary here is correct. @hungvu193 you can go ahead and request, @shubham1206agra I've sent an offer which I'll pay after the checklist is added.

Looks good. Feel free to accept the offer.

Paid, closing!

$250 approved for @hungvu193


drivers: pwm: Convert drivers to new DT device macros

Convert pwm drivers to use new DT variants of the DEVICE APIs.
DEVICE_AND_API_INIT -> DEVICE_DT_DEFINE
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

@galak pwm_nrfx.c doesn't build anymore; adding #define DT_DRV_COMPAT nordic_nrf_pwm at the top seems to work.
Also, doesn't it need to use DEVICE_DT_DEFINE(PWM(idx)) instead of DEVICE_DT_INST_DEFINE(idx) since the instance numbers don't necessarily match the pwmN labels, and the rest of the macros in that file depend on the labels?  I'm unfamiliar with what's been going on with DT so I may be mistaken.


add diagnostics settings for firewall, public IP, and network security groups

Description
Defaults the diagnostic logs and metrics settings for these resources:
Azure Firewall

AzureFirewallApplicationRule
AzureFirewallNetworkRule
AzureFirewallDnsProxy
AllMetrics

Public IP Address

DDoSProtectionNotifications
DDoSMitigationFlowLogs
DDoSMitigationReports
AllMetrics

Network Security Group

NetworkSecurityGroupEvent
NetworkSecurityGroupRuleCounter

Virtual Network

AllMetrics

Demo
To demo this, deploy MLZ as you usually would with az deployment sub create.
You can visually see these diagnostic settings by selecting "Diagnostic Settings" from any of the resource groups. For example, here's a Hub Resource Group Diagnostic Settings blade:

Issue reference
The issue this PR will close: #465
Checklist
Please make sure you've completed the relevant tasks for this PR out of the following list:

[x] All acceptance criteria in the backlog item are met
[x] The documentation is updated to cover any new or changed features
[x] Manual tests have passed
[x] Relevant issues are linked to this PR

Should we make 'metrics' optional since they add expense that may not be required. Should logs even be optional? I thought we were also removing the TF virtual network diagnostic logging in this also, maybe making it an option parameter,


fix: balanceInput is broken

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[x] Bugfix
[ ] Feature
[ ] Refactoring

What's new?

[x] PR closes #3632
[x] PR close #3634
[ ] Requires deployment <rubick/magick_issue>
[ ] <brief_description_of_what_I've_added>

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

This bug was introduced from #3573 in the conflict-solving process : )  cc @petersopko

@yangwao can we speedtrack this to get beta back on track ? (currently mints with 0bsx and offers are not working)

I found another bug related to balanceInput on https://beta.kodadot.xyz/.

When I want to relist a nft, it tells me that the price I set should be lower than my balance.

What's more, the price I set should be greater than 10000

I found another bug related to balanceInput on https://beta.kodadot.xyz/.

✅  Fixed

2. What's more, the price I set should be greater than 10000

yes, this is some basilisk thing, the minimum price for the offer,
I guess with the upcoming Rococo deployment, it will change.

pay 50 usd

😍 Perfect, I’ve sent the payout
💵 $50 @ 64.01 USD/KSM ~ 0.781 $KSM
🧗 Caiv9TbPz68q5dC8EcHu5xKYPRnremimGzqmEejDFNpWWLG
🔗 0x3a0dc687823cd52062c1bcf4d455f7dcd617fef8a63e5acf68baec9137b0e5c6
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Supermicro only baseboard serial number set

Describe the bug
On our Supermicro Servers there is nearly never a system or chassis serial number set.  That leads to this error:
...
File "/usr/local/lib/python3.9/site-packages/pynetbox/core/endpoint.py", line 147, in get raise ValueError(
ValueError: get() returned more than one result. Check that the kwarg(s) passed are valid for this endpoint or use filter() or all() instead.

Expected behavior
Maybe fall back to baseboard serial ?
Environment:

OS: Rocky Linux 9.3
Netbox agent version 0.7.1

Additional context
Working fix in my setup for netbox_agent/vendors/supermicro.py :
def get_service_tag(self):
    default_serial = "0123456789"
    baseboard_serial = self.baseboard[0]['Serial Number'].strip()
    system_serial = str(self.system[0]['Serial Number']).strip()

    if self.is_blade() or system_serial == default_serial:
        return baseboard_serial
    return system_serial

Hi,
as a fellow supermicro user I can confirm that patch is needed.
if you have many, could you complain to supermicro of their incompetence so they finally start getting this right?
You might wanna have some conditions that whatever is returned is value is in fact looking like a serial number
(so [0-9A-F]{1,20} or something - don't have one to look at right now)

At least for us, it's probably not the fault of Supermicro. Supermicro doesn't sell its servers directly. We have to buy them from resellers, and on the bill, they show up with a custom serial from the reseller.
For example:
A Supermicro server with the serial supermicro-xyz shows up as reseller-xyz.
I think the resellers are supposed to set those serial numbers, but they nearly never do.
The "workaround" I proposed was to set the system serial number to the motherboard serial number if it is set to the default of "0123456789". Since the motherboard serial is set by Supermicro and is hopefully a unique identifier, this should resolve the issue.

Thank you @Garfunkl for the proposed solution.
We are facing the same issue with the default serial number in many of our Supermicro servers and I took the liberty to pick you proposed solution and opened this pull request: https://github.com/Solvik/netbox-agent/pull/317
In the pull request there is also a new command line option to update the serial number of existing servers, which we needed to update the old serial numbers with the new ones without removing the server object from Netbox.


Update sbt-scalafmt to 2.4.3

Updates org.scalameta:sbt-scalafmt from 2.4.2 to 2.4.3.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "sbt-scalafmt" } ]

labels: sbt-plugin-update, semver-patch

Codecov Report

Merging #124 (6d36acb) into master (f343741) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #124   +/-   ##
=======================================
  Coverage   54.41%   54.41%
=======================================
  Files           1        1
  Lines          68       68
=======================================
  Hits           37       37
  Misses         31       31

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f343741...6d36acb. Read the comment docs.


Added a HackerEarth Problem

Duplicate of #266.
Please make the changes requested in #266. Will merge that.


Nginx slower than simplehttpsserver?

Do you want to request a feature or report a bug?
No
What is the current behavior?
Run audits in Chrome, the first meaningful paint time from NGINX is 1200ms,
NODE_ENV=production yarn run serve is about 650ms
If the current behavior is a bug, please provide the steps to reproduce.
Config a https://localhost site hosted by NGINX, a self-signed CA used.
gzip enabled, http2 ssl enabled.

What is the expected behavior?
How to enhance the first meaningful paint time when hosting by NGINX?
Anyone share a practice is really appreciate.
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information.

Node version 8.9.4
npm version 5.6
Operating system: OSX 10.13.3
CLI version: latest preact-cli
Browser: Chrome 64

I found style.css hosted by Nginx in critical render path in audit test is 570ms
from simpleHttpsServer is 20ms


Fix pickling with MPI full mode

fixes #1286

@tjb900 should be fine now?

jeez... this was a rabbit hole: https://github.com/sympy/sympy/issues/4297
causing pickling to break with MPI_fullmode + OpenMP
I just pushed a workaround


Error: bam2cns unexpectedly returned

I'm receiving the following error message:
...
[Thu Apr 20 18:54:04 2017] Batch 411/2999
perl -I/home/seanla/Software/proovread/bin/../lib/ /home/seanla/Software/proovr\
ead/bin/bam2cns --append 1 --bam proovread-yeast-200Sx50L/bwa-sr-3/proovread-ye\
ast-200Sx50L.bam --bin-size 20 --coverage 11.25 --ignore-weak-reads 0 --mask-we\
ak-reads 0 --max-ins-length 0 --max-ref-seqs 100 --prefix proovread-yeast-200Sx\
50L/bwa-sr-3/proovread-yeast-200Sx50L.410 --qv-offset 33 --ref proovread-yeast-\
200Sx50L/bwa-sr-2/proovread-yeast-200Sx50L.fq --ref-offset 160792741
#------------------------------------------------------------------------------#
Warning: unable to close filehandle properly: Disk quota exceeded during global\
 destruction.
#------------------------------------------------------------------------------#
[Thu Apr 20 18:54:29 2017] bam2cns unexpectedly returned
        Exited at 'main'
        '/home/seanla/Software/proovread/bin/proovread', line 1634
        Last call 'main::correct_sr_mt'
        '/home/seanla/Software/proovread/bin/proovread', line 868

Any help resolving this error would be appreciated! Thanks.

That's a weird one. I'm not entirely sure what it causing this, but my guess is that it has something to do with too many open files. Looks like you are correcting a very large batch of sequences.

You might wanna check the recommendations on limits for chunk sizes (https://github.com/BioInf-Wuerzburg/proovread#getting-chunk-sizes-right-48). You seem to correct much more than 1X of Yeast PacBio data in one go. Using less data should already solve the issue.

You can increase the following value in the proovread.cfg:

## Number of reads to check out at once for individual consensus correction
##  process. Memory intensive step, be cautios with great values
'chunk-size' => 100, # <= increase to 1000

This is a warning, not sure if it actually has any negative affect on the execution of the program. It wouldn't be to hard to make proovread simply ignore it. Let me know if you want to go down that road.


Hi.

Gif itself: https://cdn.discordapp.com/attachments/846391703862247435/846391726552776734/TalkativeSimilarJay-size_restricted.gif
Can you help me with this ASAP?

Due to upstream model and low quality frames, the model loses its accuracy, but I find some frames that give true positive 44 and 21

K, thank you!


Corrupting index files

I have loaded this extension on my server and it took down a couple website, why i have no idea, I have uninstalled the extension. It seems like it corrupted these websites. I hope there is a solution to fix this corruption without a rebuild

Hi jpkinsley ,
sorry to read, that you have issues/errors/problems with your "index" - files, but I can assure you, that the Plesk Let's Encrypt Extension is definetely not your root cause for such an issue, as it doesn't change/modify any file in your webroot.  ;-)

The last 2 sites I loaded it on went down. It changed the index file to
where it changed it's path to the default plesk page
Joe
On Jun 27, 2017 3:56 PM, "Uwe Filthaut"<EMAIL_ADDRESS>wrote:

Hi jpkinsley ,
sorry to read, that you have issues/errors/problems with your "index" -
files, but I can assure you, that the Plesk Let's Encrypt Extension is
definetely not your root cause for such an issue, as it doesn't
change/modify any file in your webroot. ;-)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/plesk/letsencrypt-plesk/issues/181#issuecomment-311467326,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AcSXbMZmBVU90clTLYmNCtxhIU1_UGWsks5sIV5bgaJpZM4ODrrj
.


Better integration tests

Add saveIndex, loadIndex to C++ integration tests

I close it as it is consumed by a newer issue #253


[MM-29120/MM-27904, MM-29121] Collapsed Reply Threads: ThreadList and ThreadHeader

This is part 2 (a continuation) of #6585. Once part 1 is merged, the diff will be smaller e.g. https://github.com/mattermost/mattermost-webapp/compare/feature/threading-overhaul-comps-a...feature/threading-comps-b.
Storybook-only code. Nothing really to QA.

MM-18107:

MM-29121: <ThreadHeader> (storybook link)
MM-29120/MM-27904: <ThreadList> (storybook link)

Screenshots

I going to be some days out, so I've unassigned myself from this review.

@matthewbirtch
Thread Header
1–6 fixed ✓
Thread List

Done
Done
We're using a batteries-included browser API for these, so fine tuning low-level punctuation/plurals would be quite a bit of work (well-written customization methods/pipelines and i18n work). I think we should maybe stick with style='long' (Last week, 5 hours ago) for now.

This was technically a part of the previous PR, and some of these timestamp wording/formats could span multiple areas. Like with date separators, they currently have the leading zero for days. ThreadFooter would be in center channel, where current timestamps don't use relative time.

I set ThreadFooter and ThreadItem to standard numeric day (no leading zero).

Should we write up a separate story to address/synchronize time formats in Threads and Channels?

Capitalization applied in ThreadItem (Now, Yesterday, Last week, and so on)

Mixed short-vs-long (depending on unit) would be possible, but for reasons in 3, maybe we should just stick with long for now?

Should we write up a separate story to address/synchronize time formats in Threads and Channels?

@calebroseland ya, we might want to if we find that the long format is causing collisions with the username and channel name

@matthewbirtch perhaps we should keep track of anything that we are pushing to address later? Propose maybe opening a new page in the confluence site for tracking that stuff to revisit?

@matthewbirtch perhaps we should keep track of anything that we are pushing to address later? Propose maybe opening a new page in the confluence site for tracking that stuff to revisit?

Done: https://mattermost.atlassian.net/wiki/spaces/Threads/pages/1157791745/Items+to+Revisit

Closing PR as it is continued in feature/collapsed-reply-threads and merging would produce conflicts down the line.


Better handling for non-local keosd in cleos

make an explicit type for resolved addresses
deduplicate logic to wait for a newly spawned keosd to be available
better checking for loopback addresses
proper support for hostnames that resolve to loopback addresses

resolves #3878

I built this branch but now when I do
$ ./programs/cleos/cleos wallet create
Failed to connect to keosd at http://localhost:8900/; is keosd running?
$

🤔 why is it not launching?
I went back and tried some command on an older master and it did launch


Modal nodes created outside of Svelte root

In the actual version (5.1.1 and HEAD), modals HTML nodes are created outside of the root element for svelte. In my case, this is a problem since bootstrap CSS is prefixed (using postcss prefixer) to avoid CSS clashes in the interface.
Would it be possible to revert to the previous behavior?

Hi @bpiwowar,
You can set the previous behavior with:
<Modal container="inline">

Let me know if this doesn't fix your issue.

Sorry I should have checked the documentation.
Yes this works, thanks!


Extension issue

Issue Type: Bug
Extension Name: doxdocgen
Extension Version: 1.3.2
OS Version: Windows_NT x64 6.2.9200
VS Code version: 1.56.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Sorry, this is missing all the information.

Feel free to reopen if you have more information


N4BiasFieldCorrection issues

I encountered the following problem when running bias_correction.py
OSError: No command "N4BiasFieldCorrection" found on host ubuntu. Please check that the corresponding package is installed.
But I have successfully installed ANTs, and when I try to run which antsRegistration* in the terminal, it returns the Ant installation directory /opt/ANTs/bin//antsRegistration
So how to solve the problem? Looking forward to your reply，thx!

I am not familiar with the recent ants.

I am not familiar with the recent ants.
You may check the latest reply in this issue: ANTsX/ANTs#876 .

ok ， appreciate it


Improve error messages in space-age exercise

Fixes #67 .

@BNAndras I think this will help with obscure error messages in space-age exercise ;) Could you please take a look?


Number of packages is off.

Fresh install, clicked "scan Homebrew".

Looks right to me. LaunchRocket can only control packages that provide a service.

Oh, well, that makes sense. Let me just go over here and finish eating my other foot. :/


LittleFS Failed

Hello mobizt
I have a problem with initial spiffs fails.
I use spiffs to storage the server files
Window 10
Arduino IDE Version 1.8.19
Board :  ESP32 Dev module
Board Manager version Esp32 : 2.0.5
Partition scheme : NO OTA 2MB APP/2MB SPIFFS
This is my simple code
email_sdcard = SdEmail.sdBegin( sd_cs, &spiSD, sd_freq );
Serial.println( email_sdcard ? "Initial SD Success" : "Initial SD Fail." );
while ( WiFi.status() != WL_CONNECTED ) delay( 500 );
session.server.host_name  = smtp_host.c_str();
session.server.port       = smtp_port;
session.login.email       = smtp_sender_user.c_str();
session.login.password    = smtp_sender_pass.c_str();
session.login.user_domain = F("");
message.sender.email      = smtp_sender_user.c_str();
session.time.ntp_server = F("pool.ntp.org,time.nist.gov");
session.time.gmt_offset = 7;
session.time.day_light_offset = 0;
message.addRecipient("staff", smtp_receiver_email.c_str() );
message.sender.name = F("FM150W");
message.subject = model_name.c_str();
SMTP_Attachment att;
att.descr.filename = F("dataloger_20220422.csv");
att.descr.mime = F("application/octet-stream");
att.file.path = F("/d_20220928.csv");
att.file.storage_type = esp_mail_file_storage_type_sd;
att.descr.transfer_encoding = Content_Transfer_Encoding::enc_base64;
message.addAttachment(att);
if (!smtp.connect(&session))
return;
MailClient.sendMail(&smtp, &message, true);
This is my Error Show on Serial Monitor
./components/esp_littlefs/src/littlefs/lfs.c:1229:error: Corrupted dir pair at {0x0, 0x1}
E (2064) esp_littlefs: mount failed,  (-84)
E (2065) esp_littlefs: Failed to initialize LittleFS
Thank your so much

Do you understand the different between SD and Flash filesystems?
You can search google for this.
Follow the examples and read all comments that described all information that you should know before adapt it.


Accuratly adds some numbers

Idea from ju57u5 on IRC

Please create your own file in the src folder - your changes will be overwritten every time the distribution is generated.

Goddamnit. I should really look more before commenting. Sorry.

no worries, sorry it can't be merged, forgot to pull from upstream

It's alright it shouldn't be too hard to merge it.

fixed


Patch: 1.3.9

1. Related Tickets

Github#TicketID

2. What's this PR do?

3. Checklist (If you won't pass this checklist please comment why)

[ ] Build successfully on local.
[ ] I removed all commented or unnecessary code.
[ ] Update the PR URL into related tickets.
[ ] Note the reason, scope of influence, and solution into ticket.
[ ] My code has covered these test cases (please list down your tested cases):

4. Screenshots
(screenshots)
5. Notes
(notes)

@coderabbitai review


After finishing training, get the number of iterations

I am using the lib for my masters thesis, and for evaluation, my supervisor thought it would be nice to get the number of iterations the training took, for now, I have edited the code in net.itertrain to yield the i and then return it from net.train it works, but I wanted to know if there is a proper way of doing it?
Thanks

Editing the itertrain isn't too bad ... but you could also run your own training loop:
for i, (tm, vm) in enumerate(net.itertrain(...)):
    pass

This is probably what you're already doing, but you can do it in your own code instead of inside theanets.


pyvista _Brain init too stringent about size parameter

I'm hitting the error '"size" parameter must be int or tuple.' I'm generating lots of similar figures, so I store several project-level parameters (including brain plotting kwargs like figure size) in an external YAML file, and pyYAML's "safe loader" doesn't support tuples, only lists.  Instead of checking isinstance(size, tuple) maybe we could check if it is length-2, and then convert it to tuple?  Or do it however the mayavi code did it; it works to pass size=[1200, 1200] with the mayavi backend.
@GuillaumeFavelier since you're the PyVista master I wanted to run this by you before just making the change... but I'm happy to do it myself if you're OK with it and you're too busy.

Good catch @drammock, even just for compatibility with mayavi I think list should be supported. Feel free to take care of it if you want 👍


[HUDI-5237] Support for HoodieUnMergedLogRecordScanner with InternalSchema

Change Logs
Currently, only HoodieMergedLogRecordScanner has support of InternalSchema.
Implementing schema evolution in flink https://github.com/apache/hudi/pull/5830 is required supporting for HoodieUnMergedLogRecordScanner with InternalSchema as well.
Impact
Support for HoodieUnMergedLogRecordScanner with InternalSchema.
Risk level (write none, low medium or high below)
Low
Documentation Update
None
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@trushev
thanks for your work


Provide in-product documentation of how uncommitted changes are persisted

Experiment with options, UX sync and additional user studies
- Use SCM action button API
- (i) learn more in file explorer title menu for RemoteHub workspaces only, can right click to hide

Here are some explorations of how we can clarify that uncommitted changes are stored locally and survive reloads, to reduce user uncertainty:
Banner in vscode.dev
i. For PRs when Getting Started isn't displayed
       ![image](https://user-images.githubusercontent.com/30305945/201227465-d467b516-bdbf-4dfb-b809-e6695333730f.png)

    ii. For repos/commits/tags/branches/file deeplinks when Getting Started isn't displayed (e.g. because README or a specific file is already open)
       ![image](https://user-images.githubusercontent.com/30305945/201227485-b0aa4591-f6db-41c0-a364-de5b4c617747.png)

Getting Started walkthrough
This approach will not help with vscode.dev PRs or file deeplinks because other content is going to be displayed in the editor area. It may help if you come from vscode.dev root instance > Open Remote Repository, GitHub.com, or the Chrome extension.

Explorer view in Remote Repositories
For remote repositories only, we could consider showing a view in the explorer which provides context on how uncommitted changes are handled.

@joyceerhl have we received feedback that users are afraid to refresh the browser? Is that a common enough scenario to warrant adding UI?
@digitarald for insights on how successful banners are. My guess is that far fewer people read or even dismiss these than we would think.

@daviddossett Yes, this is something that came up repeatedly in the user study that we just ran for Edit Sessions (summary report will be shared out to team early next week). Users expressed confusion about where their changes were stored and were reluctant to refresh the page. They were pleasantly surprised when they learned that uncommitted changes were persisted but didn't expect that to be the case because that's what they've learned from other webpages or other online IDEs.

+1 to what @joyceerhl mentions, and I just sent the report she mentioned. Data loss is one of users' top concerns, and how changes are persisted throughout vscode.dev and RemoteHub were mysteries to users that we'd really like to clarify for a better first impression and more likely continued use.

A lot of this is about reducing onboarding anxieties when using vscode.dev for the first time. Not knowing where files are persisted will discourage some people from exploring vscode.dev fully. For example, some people might think that somehow they might end up making changes directly to the repo. Others might think that the repo has been forked/cloned to their own GH account (assuming they are logged in). And others just don't know so they don't even think of making any changes to the code that they are browsing.
If we can reduce this uncertainty and the corresponding anxiety about what will happen to any edits made in vscode.dev, we believe that we will see more people taking more advantage of vscode.dev.
Other brainstorming ideas:

Pop up dialog on first launch (like the workspace trust dialog) that tells people that any changes they make are stored in a virtual workspace and are not committed to any repository.
Hover text when hovering over a file in explorer that says "Changes to this and other files are stored in local storage and are not committed to any repository"
An "Enable editing" button similar to when opening Office docs as attachments that tells people that if they want to edit files in this workspace they should click this - edits are persisted in local storage...
A notification pop up saying "Creating virtual workspace..." while opening.
Something like the help panel in Joyce's mockups above but it is positioned at the top of the explorer with a blue background and a close button. Like a popup that remains in place until the user closes it.

@bamurtaugh does 'RemoteHub view' refer to the Remote Explorer view, or to a new view that is contributed to the Explorer view or Source Control view?
As another alternative, I think the team has talked about contextual walkthroughs in the past, and IMO the vscode.dev/github case is a great motivating scenario. My hypothesis is that users are more likely to need contextual handholding in vscode.dev than in VS Code for the desktop, because our custom vscode.dev link experiences mean that you can be dropped into a layout containing extensions you didn't explicitly install, files you didn't explicitly open, or views that you didn't explicitly focus. Additionally, if there is default content being displayed, our Getting Started editor with the walkthroughs don't kick in. My hesitation with introducing a Help or About Virtual Workspaces view in the Explorer view container is that such content only needs to be read once and feels heavyweight to have around for longer. For example, this is what Figma has:

@bamurtaugh does 'RemoteHub view' refer to the Remote Explorer view, or to a new view that is contributed to the Explorer view or Source Control view?

I meant the Remote Explorer.

Something like the help panel in Joyce's mockups above but it is positioned at the top of the explorer with a blue background and a close button. Like a popup that remains in place until the user closes it.

@stevencl's idea here ^ is along the lines of what I was thinking, for something more top-level / in the Explorer.

My hesitation with introducing a Help or About Virtual Workspaces view in the Explorer view container is that such content only needs to be read once and feels heavyweight to have around for longer. I would prefer a walkthrough experience which allows to display ephemeral context.

This makes sense. I think a contextual walkthrough would be great, but I wasn't sure how feasible it was at this point. In the meantime, I was thinking of a note in the Explorer to be similar to the note we pop up in the SCM view's commit box:

It's a valuable first piece of info, and users can choose not to show it again.

I do generally think a lot of folks close or miss the top banner, so including info in spots like a getting started walkthrough and RemoteHub view would be helpful. Although they don't have the same top-level benefit as the banner. I'd wonder if we could do anything in the File Explorer, since I'd expect this is another highly-viewed area.

I actually see a lot of users keeping the banner, as it has links that might be useful for later … maybe inducing some FOMO.
How might we make the banner the banner more welcoming and include some of the why-vscode.dev-is-cool.
Visual Studio Code (Preview). Anywhere, anytime, entirely in your browser.
Things to try out:
1. Quickly editing local files without installing VS Code. Any edits persist in your browser storage.
2. Share GitHub files, commit changes, and collaborate with Live Share ([How to]).
3. Take any changes and continue on to your desktop VS Code or Codespaces if you need to run, debug, or use the terminal ([How to]).
[Let's go]

The best part is that this banner is shown for al users, compared to walkthroughs or any welcome screens.
I wonder how much the information helps in the SCM view, as I understand that user research participants were even unsure about editing in vscode.dev. SCM would only be opened if they have some understanding that editing and committing works.

Here's another pass at a view in the explorer container, but further up and with more connection to Continue On per https://github.com/microsoft/vscode/issues/165406#issuecomment-1315417871

And a mockup of a toast when the user first adds, deletes, or modifies a file (which I suspect would be missed/ignored):

I think the contextual walkthrough is very appealing for a first launch experience. Would we always be able to determine if this is the first time the user has launched vscode.dev?
The notification has higher likelihood of not being noticed although since it is on first launch and the user hasn't started doing anything they may be more likely to pay attention to it than if they had started working and then the notification showed up. I think quite a few people noticed the notification during the study but some said that they had become accustomed to just ignoring them.
Would it be possible to try something like the SCM popup that Brigit showed? The About Remote Repositories panel mockup looks very permanent.

Oh I think understand what you're talking about now re: the SCM popover. Something like this?

I did some digging and it turns out we already tried the contextual walkthrough idea back when we were first designing the Getting Started walkthroughs: https://github.com/microsoft/vscode/issues/106717#issuecomment-698627820 and https://github.com/microsoft/vscode/issues/106717#issuecomment-790053982 the issue there was that apparently users didn't read most of the content. With a single popover though, maybe we have better odds.
We will need to introduce extension API for this because Remote Repos is an extension and there's no way for extensions to display ephemeral messages in the explorer like this at the moment. The SCM popover has an issue where the user focuses into the input box and then can't see that they have changed files because the popver obscures that content. This popover should only appear when we cannot show context through Getting Started, i.e. the editor will already have content (PR diff, deeplink to file), so we will run into the same issue here.

Now tracking in https://github.com/microsoft/vscode/issues/171190


Small files bugs

Fixed HOPS-111, HOPS-107, HOPS-112

Can one of the admins verify this patch?

can you squash or rebase so that we get only the three last commits?

Jenkins test this please.

I did a new pull request with the proper commit history: #394


upgrade frontend app dependency to node v14+ with a lot of dependencies.

use yarn for dependencies management
update webpack to v5 along with a lot of dev dependencies
update react to v18
update babel to v7 and use @babel/plugin-transform-runtime instead
use npm dependencies for bourbon v7 and normalize.css,
removed in client/app/styles/vendor
move dependeny of PropTypes to prop-types npm package
replace react-document-title with react-helmet
remove react-hot-reload as it's now embedded in react-dev-server
simplify dev-server, merge 3000 (express) and 3001 (dev-server) into one dev-server
update README.md

maybe I could send it to another branch and merge with the BE PR https://github.com/Wiredcraft/pipelines/pull/123 here. then we have it tested somethere (maybe omni pipelines on in-house-builder?).

omni-builder seesm a good place to test it

sure i will try to test it on omni-builder first. let's just leave this PR for now.

ppl already start to use this pr, seems no issues. let's merge it to master

wait for #125.


Update open source license meta data in setup.py

Switch from Apache License to MIT License in the below commit
  commit 280c86a5dc42e79d7a950a5e72eb2acb741ffe48
  Author: Jean-Sebastien Bevilacqua<EMAIL_ADDRESS>  Date:   Mon Nov 21 17:53:32 2016 +0100

      Restarting on new bases with only full Vulkan support

Can you join me on the #vulk irc channel. I'm connected from 9am to 9pm (France).