Sync with github account is requested every app launch

Nós escrevemos os dados necessários em sua área de transferência porque era muito grande para ser enviado. Por favor, Cole.
Issue Type: Bug
Since I formatted my linux, Manjaro, and installed the versions available in pamac, which are:
visual-studio-code-bin, snap and flatpak.
In all of them, synchronization with the github account, liveshare, etc. is requested at every restart of the application. I've already installed and reinstalled several times, including deleting the cache and files created by default, and still the synchronization is requested.
Is there anything I can do to fix this problem?
VS Code version: Code 1.64.2 (f80445acd5a3dadef24aa209168452a3d97cc326, 2022-02-09T22:02:29.527Z)
OS version: Linux x64 5.15.19-1-MANJARO snap
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 2337)

GPU Status
2d_canvas: unavailable_softwaregpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: disabled_offrasterization: disabled_softwareskia_renderer: enabled_onvideo_decode: disabled_softwarevulkan: disabled_offwebgl: unavailable_softwarewebgl2: unavailable_software

Load (avg)
1, 1, 1

Memory (System)
7.68GB (1.14GB free)

Process Argv
--no-sandbox --force-user-env --unity-launch --crash-reporter-id 65b790ce-eed3-4f10-a419-539b1e7c13bf

Screen Reader
no

VM
0%

DESKTOP_SESSION
plasma

XDG_CURRENT_DESKTOP
KDE

XDG_SESSION_DESKTOP
KDE

XDG_SESSION_TYPE
x11

Extensions (19)

Extension
Author (truncated)
Version

jest-snippets
and
1.8.0

bracket-pair-colorizer
Coe
1.0.62

vscode-eslint
dba
2.2.2

es7-react-js-snippets
dsz
4.3.2

gitlens
eam
11.7.0

prettier-vscode
esb
9.2.0

comment-anchors
Exo
1.9.6

auto-close-tag
for
0.5.14

auto-rename-tag
for
0.1.10

code-runner
for
0.11.7

vscode-language-pack-pt-BR
MS-
1.64.6

vsliveshare
ms-
1.0.5330

material-icon-theme
PKi
4.13.0

LiveServer
rit
5.7.4

synthwave-vscode
Rob
0.1.11

react-proptypes-generate
sum
1.7.6

errorlens
use
3.4.1

quokka-vscode
Wal
1.0.445

material-theme
zhu
3.13.19

(5 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30425749
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30433059
pythonvs932:30410667
wslgetstartedc:30433508
vsrem710:30416614
pythonvsnew555cf:30436485
vsbas813:30436447

Can you follow these steps so that we can get more information on what's going on?

Open the Command Palette
Run the Developer: Set Log Level... command
Choose Trace
Wait for the issue to happen...
Open the Output pane (ctrl+shift+u I think)
drop in this issue he contents of the following:

GitHub Authentication Output channel
Log (Settings Sync) Output channel
Log (Window) Output channel

@TylerLeonhardt
Nothing new as I can see. There is some time difference due to timezone settings, just ignore it.
On sign in
1. GitHub Authenticatior
[Info  - 19:13:17.296] Logging in for the following scopes: user:email
[Trace  - 19:13:22.827] Handling Uri...
[Info  - 19:13:22.827] Exchanging code for token...
[Info  - 19:13:23.472] Token exchange success!
[Info  - 19:13:23.473] Getting user info...
[Info  - 19:13:23.815] Got account info!
[Info  - 19:13:23.815] Storing 1 sessions...
[Info  - 19:13:23.824] Reading sessions from keychain...
[Info  - 19:13:23.824] Stored 1 sessions!
[Info  - 19:13:23.824] Login success!
[Trace  - 19:13:23.828] Token acquired from secret storage.
[Info  - 19:13:23.828] Got stored sessions!
[Trace  - 19:13:23.829] Read the following session from the keychain with the following scopes: user:email
[Info  - 19:13:23.829] Got 1 verified sessions.
[Info  - 19:13:23.830] Getting sessions for user:email...
[Info  - 19:13:23.830] Getting sessions for user:email...
[Info  - 19:13:23.831] Got 1 sessions for user:email...
[Info  - 19:13:23.831] Got 1 sessions for user:email...

2. Log (Settings Sync)
[2022-02-17 20:13:59.618] [settingssync] [info] Auto Sync: Triggered by Activity
[2022-02-17 20:13:59.752] [settingssync] [info] Settings: No changes found during synchronizing settings.
[2022-02-17 20:13:59.755] [settingssync] [info] Keybindings: No changes found during synchronizing keybindings.
[2022-02-17 20:13:59.757] [settingssync] [info] Snippets: No changes found during synchronizing snippets.
[2022-02-17 20:13:59.758] [settingssync] [info] Tasks: No changes found during synchronizing tasks.
[2022-02-17 20:13:59.760] [settingssync] [info] GlobalState: No changes found during synchronizing ui state.
[2022-02-17 20:13:59.792] [settingssync] [info] Extensions: No changes found during synchronizing extensions.
[2022-02-17 20:13:59.793] [settingssync] [info] Sync done. Took 76ms

3. Log (Window)
[2022-02-17 20:13:23.826] [renderer1] [info] Settings Sync: Updated current session 2100b5ae-e543-420d-85e6-9a34c70d01dc

After restart
1. GitHub Authenticatior
[Info  - 19:16:29.278] Reading sessions from keychain...
[Info  - 19:16:29.311] Getting sessions for user:email...
[Info  - 19:16:29.311] Getting sessions for all scopes...
[Info  - 19:16:29.328] Got 0 sessions for user:email...
[Info  - 19:16:29.328] Got 0 sessions for ...

2. Log (Settings Sync)
[2022-02-17 20:16:29.414] [settingssync] [info] Using settings sync service https://vscode-sync.trafficmanager.net/
[2022-02-17 20:16:29.414] [settingssync] [info] Auto Sync is enabled.
[2022-02-17 20:16:29.414] [settingssync] [info] Auto Sync: Suspended until auth token is available.

3. Log (Window)
[2022-02-17 20:16:28.051] [renderer1] [info] IExtensionHostStarter.start() took 26 ms.
[2022-02-17 20:16:28.184] [renderer1] [error] [Extension Host] (node:120757) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `code --trace-deprecation ...` to show where the warning was created)

do you have gnome-keyring installed on your system?

Hmm nothing in the logs pointed me to that. It was just a hunch. I wish there was a way for me to detect if gnome-keyring was the problem but I'm not sure there's anything I can do with this. Glad you are all unblocked.

After restart (logged out) :

GitHub Authentication:

[Info  - 11:42:58.496] Reading sessions from keychain...
[Info  - 11:42:58.523] Getting sessions for user:email...
[Info  - 11:42:58.548] Got 0 sessions for user:email...
[Info  - 11:42:58.608] Getting sessions for all scopes...
[Info  - 11:42:58.608] Got 0 sessions for ...
[Info  - 11:43:11.687] Getting sessions for all scopes...
[Info  - 11:43:11.687] Got 0 sessions for ...

Log Window

[2022-02-18 12:42:57.451] [renderer1] [info] IExtensionHostStarter.start() took 95 ms.
[2022-02-18 12:42:57.574] [renderer1] [error] [Extension Host] (node:15732) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `code --trace-deprecation ...` to show where the warning was created)

Log Main

[2022-02-18 12:42:56.507] [main] [info] update#setState idle
[2022-02-18 12:42:56.537] [main] [info] ExtensionHostStarterWorker created
[2022-02-18 12:42:57.367] [main] [info] Starting extension host with pid 15732 (fork() took 10 ms).
[2022-02-18 12:42:57.367] [main] [info] ExtensionHostStarterWorker.start() took 11 ms.
[2022-02-18 12:42:57.725] [main] [warning] Switching to using in-memory credential store instead because Keytar failed to load: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files
[2022-02-18 12:43:26.508] [main] [info] update#setState checking for updates
[2022-02-18 12:43:26.521] [main] [info] update#setState available for download

Settings Sync

[2022-02-18 12:42:57.684] [settingssync] [info] Using settings sync service https://vscode-sync.trafficmanager.net/
[2022-02-18 12:42:57.684] [settingssync] [info] Auto Sync is enabled.
[2022-02-18 12:42:57.684] [settingssync] [info] Auto Sync: Suspended until auth token is available.

@renaudcerrato secrets on Linux in vscode are stored using org.freedesktop.secrets which is suppose to be an abstraction layer over keyrings that implement it properly.
With that said, I've never had much success in understanding if KDE has a keyring/wallet that is compatible, even though my reading says that the primary use case was for abstracting over gnome and KDE... I can tell you for sure that gnome-keyring works, but I need some help from folks who use KDE to understand if KDE actually has an alternative or not and that status of that.
This link:
https://forum.authpass.app/t/what-is-the-provider-of-org-freedesktop-secrets-for-kde-plasma-5/162
Says:

Here’s a current answer from a KDE developer, so I consider this to the be official answer. He said:

KWallet still doesn’t implement org.freedesktop.secrets, and KSecretService is dead.

That's from August.
I have seen several folks mention that KeePassXC is apparently a solution (although they don't mention it in the context of vscode) so that might be a valid alternative for us.
In short, my recommendation is:

provide feedback to KDE to finish their implementation of org.freedesktop.secrets
use gnome-keyring or give KeePassXC a try and let me know how it goes!


move env to env.example to avoid overriding it

Please update the README to reflect the change, like "Before running docker compose command make sure to copy compose/.env.example to compose/.env".
Something like that.

Could you please explain a bit more about the reason of this change?

Thanks @denics :+1:


docs: updated faq due to keycloak process change

Description
Due to keycloak upgrade processes needed an adjustment.
Issue
not needed
Checklist
Please delete options that are not relevant.

[ ] I have followed the contributing guidelines
[ ] I have added copyright and license headers, footers (for .md files) or files (for images)
[ ] I have performed a self-review of my changes
[ ] I have successfully tested my changes
[ ] I have added comments in the default values.yaml file with helm-docs syntax ('# -- ') if relevant for installation
[ ] I have commented my changes, particularly in hard-to-understand areas

@evegufy i noticed with @Phil91  that the way how the user creation works in keycloak changed. therefor we adjuted the documentation and refurbished it overall a bit.


KAFKA-873, KAFKA-2079: curator + exhibitor integration

My motivation for introducing curator to kafka was to get optional exhibitor support, however I noticed this  is also a solution to ticket KAFKA-873 (https://issues.apache.org/jira/browse/KAFKA-873).
Structurally I believe the code is sound, however some tests are blocking which I believe is duet o races related to in-memory Zookeeper but not entirely sure. Am looking into it and testing outside of in-memory ZK, as well. But would love comments/discussion on this PR. I imagine exhibitor support is something that many are interested in, especially those of us in AWS & cloud environments.
Some notes on this PR:
-- A ZkClient-Curator bridge is used so that Kafka code continues to use the ZkClient abstraction
-- Exhibitor support implemented here is optional (enabled if and only if exhibitor is configured in Kafka server or consumer configuration)

Created separate Jira ticket requesting exhibitor support: https://issues.apache.org/jira/browse/KAFKA-2079

Thank you for the pull request, Aaron.
Can the exhibitor piece be broken out into a separate patch (dependent on this) and be submitted against the exhibitor jira?  KAFKA-2079
Could you rebase this pull request against the master branch to see if we can get it into the upcoming 0.8.3 release? See discussions here on the jira. KAFKA-873

Are we gonna celebrate 2nd anniversary of this pull requests in the state of pull request?

We went a different route and implemented a ZooKeeperClient that uses async operations under the covers, but presents a batched interface. Closing this.


Provider-aws latest release has a conflict with consul-cluster module

In the last version of the  aws provider, v3.0.0, following conflicts appear for resource resource/aws_autoscaling_group when running a terraform plan
Error: "availability_zones": conflicts with vpc_zone_identifier

  on .terraform/modules/consul_cluster/terraform-aws-consul-0.7.6/modules/consul-cluster/main.tf line 14, in resource "aws_autoscaling_group" "autoscaling_group":
  14: resource "aws_autoscaling_group" "autoscaling_group" {

Error: "vpc_zone_identifier": conflicts with availability_zones

  on .terraform/modules/consul_cluster/terraform-aws-consul-0.7.6/modules/consul-cluster/main.tf line 14, in resource "aws_autoscaling_group" "autoscaling_group":
  14: resource "aws_autoscaling_group" "autoscaling_group" {

Related to this change:
https://github.com/terraform-providers/terraform-provider-aws/pull/12927
Only one of the two parameters(vpc_zone_identifier, availability_zones) should be passed right?

3.0.0 just came out, with some backwards incompatible changes, and we have not yet tested/upgraded this repo for it. As a short term workaround, you can pin your AWS provider to 2.x.x.

Only one of the two parameters(vpc_zone_identifier, availability_zones) should be passed right?

I think we want to pass both, but we probably need to change the default for our corresponding input variables in consul-cluster to be null. Would you be up for a PR that makes that change?

Hey @brikis98
Yes, I pinned the provider-aws version and it worked.
Sure, I'll test it and open a PR. Thanks for the help

@rafaelremondes are you going to put in a pr? I am having the same issue.

:raised_hands: Thank you @rafaelremondes @brikis98 !

Fixed by @rafaelremondes in https://github.com/hashicorp/terraform-aws-consul/releases/tag/v0.7.7.


Buttons!

It's time to create some opinionated button components.
Here's what I'm thinking we'll want ...
For all buttons, there will be props that make it easy to

add a vertically centered icon before the text
control colors
stretch the button to the full width of its container
make it a larger size — e.g. on marketing pages we provide some extra horizontal padding
disable the button (in which it'll use Assembly's disabled style)
make the button an icon-only button with a tooltip text explanation (replacing the need for our current IconButton component)

MbxButton looks like this:

That's what we have throughout Studio and marketing pages. Account Dashboard is the outlier with larger text. There seems to be to be enough enthusiasm for the smaller-text norm that we should stick with that.
MbxSecondaryButton is the outlined version of the primary button:

MbxDiscouragingButton is gray, but not too gray, and outlined:

MbxTextButton looks like a bold link. Usually it includes an icon, and it can take on whatever text size its container is using.

MbxAppButton is for denser apps like Studio's style editor. Borders are not fully rounded, text is usually smaller — though we could have two sizes, txt-xs and txt-s. The default color is gray instead of blue, so it's not hogging too much attention in a dense UI. (You'll be able to make it blue with an option).

MbxAppSecondaryButton is the same as MbxAppButton but outlined instead of filled.

Oh, I'm also thinking all these buttons can have an active state (passed in as a prop), in which case they will assume their hover colors.
Maybe the MbxTextButton will also get a faint background gray in this state — not sure how to best handle in that situation, though.


2021.10-004 Pinebook Pro Boot Menu Always Shows

Whenever a power cycle is performed the tow-boot boot menu shows without a timeout. Tow-Boot is on SPI. emmc has no OS and has 2 partitions (2GB swap, rest ext4 for storage only). There is nothing on it right now related to booting. SD is 512GB running Armbian.
Ran into this issue a while back and it was not a legitimate issue until I upgraded the keyboard/trackpad fw and could not get past the menu requiring me to short pin6 to ground to bypass SPI and use U-Boot on SD.
Edit: forgot to mention. When I choose to boot from SD then it boots Armbian fine.

Just a note: Realized that if I wait a little while then choose reboot in the boot menu then the SD will boot. In my case I was stuck because I had no keyboard (tow-boot doesn't seem to support external keyboards for the boot menu?). Maybe this is just a SD initialize time issue?

Hello, cannot reproduce this.
TB 2021.10-005 on sdcard.
emmc disconnected.
spi empty.
Did you also have this bug with the new version ?


Unable to create new project with deploy

Contrary to the previous seamless integrations, I am no longer able to create a clone of this repo with deploy button and get vercel project deployed. Are we aware of this issue?
I have tried to reproduce this with a new github account, to make sure it's not due to my already existing project.
How can we debug this issue?
Thank you for the awesome product!

Having the same issue it fails with:

Error: either NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY env variables or supabaseUrl and supabaseKey are required!
--

<span>    at __webpack_require__.X (/vercel/path0/.next/server/webpack-runtime.js:177:21)</span>

Ah I missed these lines:
Once the project has deployed, continue with the configuration steps below.

The initial build will fail due to missing Stripe environment variables. After configuring Stripe, redeploy the application.

Searching for the Supabase integration and setting up it fixed the deploy.


Is the UTM coordinate of the picture in the SF-XL dataset the coordinate of the camera when taking the picture?

Is the orientation  the azimuth in coordinates?

Yes, the UTM / GPS indicates the camera position. This is true for almost any visual geolocalization / place recognition dataset. And the orientation is the azimuth, ranging from 0° to 360° (0° means the camera points north, 180° the camera points south).

Think you your reply


Add TravisCI and Coverage buttons to project README

Task 1 needs to be completed

@noelpimentel you're in charge for this

Okay!!

Lol, my bad.


WIP: Add license headers to files in private/

This is on top of PR #169.
I tried to track changes back enough to give appropriate attribution.  Of course, it can be corrected if I've missed something/someone.

I will rebase this on top of recent changes

Oooh, you read my mind ;-)  Carry on...

Oh, sorry. 😄Done with the rebase & thanks for the changes. Please feel free to merge whenever you like.
By the way, what's the right way of updating the copyright notices? Add the current year whenever one makes a change to a file?

The newly added files in private are still missing copyright notices.

Yes I try to update the year as I modify the file.  Commas if its discontinuous, or hyphenated for a range of years.
There seem to be various practices for all this:

I like to use multiple copyright lines as I figure that gives maximal explicit credit.  It also shows exactly who you'd need to ask if you want a different license.
New contributors to a file get added to the bottom of the list.
whoever updates a file should add the year they update to the appropriate copyright line.  But should not re-order the lines.
sometimes I don't update the year if I feel I'm making a minor "maintenance change" (whatever that means).


Allow for inclusion of files/folders displayed by "Show all files"

Including files/folders show by "Show all files" was disabled in #117 due to huge bugginess.
It'd be nice to have this functionality back.

This is fixed by #234.


Add guidance for using ASP.NET Core APIs in libraries

Fixes https://github.com/aspnet/AspNetCore.Docs/issues/14309
Fixes https://github.com/aspnet/AspNetCore.Docs/issues/15303
Add a doc focused on guidance for using ASP.NET Core APIs in a class library.
Internal review page

Pinging @davidfowl & @DamianEdwards for a review.

@davidfowl This is ready for another look.

@davidfowl @DamianEdwards I'm hoping to get some more feedback before the holiday break.

@twsouthwick You mentioned you're doing some work in this area. I'd love to hear your feedback as well.

@DamianEdwards It's ready for another look. Also, see my question above.

@rynowak Ready for another look. Thank you soooo much for all of your feedback.


#length, #percent variant for the  width, height props

t's my fault for not reading the documentation well. In the semantic versioning rule, I should make a new major release because this is a breaking change, but I think it's ok because I don't have a project that depends on it yet. :sweat_smile:


Structure LayerStore tests differently

SDK-287
we won't know if this fixes it until we have run Travis a few times

Coverage remained the same at 70.745% when pulling 1a308666303a368c6c86c6c22cdf11d035ca7562 on intermittent into e93e82f868b255959b7647b3a4ff7a9c635f832a on master.

I restarted the build 3 times and did not get the failure, so fingers crossed this truly fixes it. But we won't know for a while.


Persist node taint label

What this PR does / why we need it:
PKS users, Alana or Cody, want to assign labels or taint to nodes. And those labels and taints are expected to be persistent regardless of PKS upgrade, bosh recreate VM or other incidents - unless the operator removed it intentionally.
How can this PR be verified?
https://pks.ci.cf-app.com/teams/dev/pipelines/pks-api-persist_node_taint_label
Is there any change in kubo-release?
yes
Is there any change in kubo-ci?
no
Does this affect upgrade, or is there any migration required?
no migration
Which issue(s) this PR fixes:
https://docs.google.com/document/d/1mbhPLfMw0sbMcNScQm5aeJhQTwZf76V0pZQkpMbXmy8/edit?ts=5eb51956&pli=1#
https://www.pivotaltracker.com/story/show/172862983

close  this  since I should send PR to  develop branch


renderman addon errors while loading

Traceback (most recent call last):
File "C:\Program Files\Blender Foundation\Blender\2.79\scripts\modules\addon_utils.py", line 350, in enable
mod.register()
File "C:\Users\Aeroboy\AppData\Roaming\Blender Foundation\Blender\2.79\scripts\addons\RenderManForBlender-master_init_.py", line 119, in register
load_addon()
File "C:\Users\Aeroboy\AppData\Roaming\Blender Foundation\Blender\2.79\scripts\addons\RenderManForBlender-master_init_.py", line 94, in load_addon
if guess_rmantree():
File "C:\Users\Aeroboy\AppData\Roaming\Blender Foundation\Blender\2.79\scripts\addons\RenderManForBlender-master\util.py", line 553, in guess_rmantree
"Error loading addon.  RMANTREE %s is not valid.  Correct RMANTREE setting in addon preferences." % rmantree)
File "C:\Users\Aeroboy\AppData\Roaming\Blender Foundation\Blender\2.79\scripts\addons\RenderManForBlender-master\util.py", line 59, in throw_error
raise ImportError(msg)
ImportError: Error loading addon.  RMANTREE  is not valid.  Correct RMANTREE setting in addon preferences.

Is there anybody in there?

Is there anybody in there?

yup


[BUG]: Unable to create custom steps by extending BaseStep

Contact Details [Optional]
<EMAIL_ADDRESS>System Information
ZenML version: 0.8.0
Install path: /Users/-/Library/Caches/pypoetry/virtualenvs/medical-imaging-pipeline-mXFg84T2-py3.7/lib/python3.7/site-packages/zenml
Python version: 3.7.6
Platform information: {'os': 'mac', 'mac_version': '10.16'}
Environment: native
Integrations: ['pytorch', 'scipy', 'sklearn']
What happened?
Cannot create a custom steps by extendingBaseStep API such as BaseAnalyzerConfig ,  with custom argument types as the verification of input argument types fails in the 'BaseStep`  metaclass
the error seems to be originating from here (line 137, base_step.py):
            **if issubclass(arg_type, BaseStepConfig):**
                # Raise an error if we already found a config in the signature
                if cls.CONFIG_CLASS is not None:
                    raise StepInterfaceError(
                        f"Found multiple configuration arguments "
                        f"('{cls.CONFIG_PARAMETER_NAME}' and '{arg}') when "
                        f"trying to create step '{name}'. Please make sure to "
                        f"only have one `BaseStepConfig` subclass as input "
                        f"argument for a step."
                    )
                cls.CONFIG_PARAMETER_NAME = arg
                cls.CONFIG_CLASS = arg_type

arg_type is set to string TypeBuiltDataset which is my custom step's argument type instead of a class
Reproduction steps

Extending BaseStep to create a custom Step (using class-based API)

class PreprocessComponent(BaseStep):
    """
    Base class for data preprocessing

    """

    @abstractmethod
    def entrypoint(
        self,
        dataset: TypeBuiltDataset,
    ) -> Output(dataset=TypeBuiltDataset):
        """
        Base entry point for data preprocessing
        """
        raise NotImplementedError

Specify custom arguments in the entrypoint (TypeBuildDataset)

Relevant log output
Traceback (most recent call last):
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/Users/-/workstation/repo/medical-imaging-pipeline/src/applications/ultrasound/features/ingest.py", line 18, in <module>
    from src.pipeline.component import IngestComponent
  File "/Users/-/workstation/repo/medical-imaging-pipeline/src/pipeline/component.py", line 75, in <module>
    class PreprocessComponent(BaseStep):
  File "/Users/-/Library/Caches/pypoetry/virtualenvs/medical-imaging-pipeline-mXFg84T2-py3.7/lib/python3.7/site-packages/zenml/steps/base_step.py", line 137, in __new__
    if issubclass(arg_type, BaseStepConfig):
  File "/Users/-/opt/anaconda3/envs/py376/lib/python3.7/abc.py", line 143, in __subclasscheck__
    return _abc_subclasscheck(cls, subclass)
TypeError: issubclass() arg 1 must be a class

Code of Conduct

[x] I agree to follow this project's Code of Conduct

Hi @raghumulukutla!
We rely on type annotations inside steps to find the right classes to read/write the artifacts that are passed between steps. Can you show us the code that TypeBuiltDataset is referring to, maybe we can figure out a way to support this data type?

It's a pretty complex annotation.
TypeBuiltDataset = Union[LazyDataset, Tuple[LazyDataset, ...]]
LazyDataset however is an instance of dict
The thing is that  I am planning to write a Materializer for read/writing artifacts myself. Seems like we are restricted to basic types (int, float, str) at the moment while specifying arguments for custom steps?

Moreover, I get the same error trying to do something simple:
class IngestConfig(BaseStepConfig):
    """
    Base class for data ingestion config
    """

class IngestComponent(BaseStep):
    """
    Base class for data ingestion

    """

    @abstractmethod
    def entrypoint(
        self,
        config: IngestConfig,
        context: StepContext,
    ) -> Output(dataset=TypeBuiltDataset):
        """
        Base entry point for data ingestion
        """
        raise NotImplementedError

With the code above, the BaseMetaClass tries to check 'IngestConfigis  an instance ofBaseConfigand fails because the former of typestrand notclass`
For comparison this is the code inbase_analyzer.py, a built-in step:
class BaseAnalyzerConfig(BaseStepConfig):
    """Base class for analyzer step configurations"""

class BaseAnalyzerStep(BaseStep):
    """Base step implementation for any analyzer step implementation on ZenML"""

    @abstractmethod
    def entrypoint(  # type: ignore[override]
        self,
        dataset: DataArtifact,
        config: BaseAnalyzerConfig,
        context: StepContext,
    ) -> Output(  # type:ignore[valid-type]
        statistics=StatisticsArtifact, schema=SchemaArtifact
    ):
        """Base entrypoint for any analyzer implementation"""
``

Seems like we are restricted to basic types (int, float, str) at the moment while specifying arguments for custom steps?

You can pass natively json-able types as config parameters, so it's a bit more than int float and strings. If your LazyDataset is an instance of a dict it might work as a config parameter rather than an artifact. We should definitely make this clearer in the docs.
However, back to the original query: IMO having a complex data type with a Union is not the way we intended materializers to recognize this types. Rather, you should have your materializer have multiple ASSOCIATED_TYPES to cover the union case at the materializer level. Perhaps unfurling the Union and just writing a materializer for the raw
I'm a bit confused by your second comment though: Can you share exactly what the error emssage is when you try to write this IngestConfig? It sounds to me that the IngestComponent might be the one at fault here due to output being equal to TypeBuiltDataset?

As @htahir already mentioned, the config parameters are at the moment limited to json-serializable data types as ZenML, however the actual step inputs and outputs allow you any custom class. Can you explain a little the motiviation of passing a dict instance as the type annotation? That would mean your actual inputs/outputs returned from the step would be an instance of an instance of a dict?

Regarding the Union type: Those are currently not supported as step inputs/outputs as well as associated types for a materializer, implementing the type validation and logic to find the correct materializer should be possible though.
I personally always thought it was desirable to have the signatures of my pipeline steps clearly defined, I'm guessing in your case the step dynamically receives data from somewhere and therefore doesn't know in advance what the output would be?
I'll just leave this here as a potential temporary solution while we figure out the best way to handle this: You could always annotate your step input/output with a simple Tuple annotation instead of TypeBuiltDataset and return a single-element tuple in case there is just one dict. (This would obviously still require a custom materializer that actually takes care of writing/reading these tuples)

Perfect! Closing now as its solved


aiapy releases not syncing with Zenodo

In GitLab by @PaulJWright on Aug 25, 2023, 05:27
"The project citation should be to the aiapy paper and the software citation should be the specific Zenodo DOI for the version used within your work."
For citing the Zenodo release, the latest version is 0.6.0, while aiapy is currently at 0.7.3

In GitLab by @wtbarnes on Aug 25, 2023, 13:23
This issue thread could be useful (in the absence of an official GitLab integration): https://github.com/zenodo/zenodo/issues/1404

In GitLab by @wtbarnes on Aug 25, 2023, 13:21
Thanks for bringing this up. The main reason the Zenodo records lag the actual releases is because, unlike GitHub, there is no integration between Zenodo and GitLab, meaning the releases have to be uploaded by hand. I was staying on top of this for a while, but then got lazy.
I would suggest that when we update these, we start from the most recent.

I have set this up again, will need to wait for a release to check.


Doesn't run on Android

I am using Unity 2020.3.13f1 which is the version this project was originally created for.
In the Build Settings, Texture Compression was set to ASTC.
The game turns into a black screen after the made with Unity logo disappears.

Unfortunately, I do not have an Android device to test it at the moment. I have updated the version to 2021.3.25f1, perhaps it would fix this issue. If not, write me and I'll try to take a look :)

Sorry it was my fault. It turned out I didn't build the addressables.
After building them with Build > New Build > Default Build Script on the Addressables Groups window, I was able to build the game for both Windows and Android.
BTW, have you considered port this project to ECS 1.0?
Thank you so much for making this project open source.


[Tasks 1540, 1541] Add Snapshots and basic rendering tests

Add basic tests, snapshots for noFeedbackBoardsView, editableText, and actionItemDisplay components
Add test:watch command to allow faster test validation
Add initial testing documentation to CONTRIBUTING.MD`

@msa2984, Have no idea why, but the files I changed aren't recognizing the "mocks" file change, which is why this PR created today, instead of yesterday, so I added them directly to file. Wondering if you'd have better luck diagnosing/if you even see the issue when referencing the mocks.

➕ ➕ ➕ for updating the CONTRIBUTING doc to add testing info!
Some notes for posterity before I merge this into the bigger PR:

I swapped your tests over to Enzyme, this way we can remove the React-Test-Renderer dependency and all tests use the same framework.
I re-generated the snapshots. It seems like the snapshots using Enzyme vs React-Test-Renderer are slightly different, however from comparing them they are both correct, just a slightly different way of rendering.
I moved the shared mock calls into a setupTests.tsx file, this seems to be a much cleaner way of initializing the SDK + API mocks which are used by all of the more complex components.
I added a reference to enzyme-to-json, as this seems like the recommended serializer for snapshot testing with enzyme.

@msa2984, Have no idea why, but the files I changed aren't recognizing the "mocks" file change, which is why this PR created today, instead of yesterday, so I added them directly to file. Wondering if you'd have better luck diagnosing/if you even see the issue when referencing the mocks.

I'm wondering if you were seeing an issue similar to what I was seeing - occasionally when I would add a new mock to that folder and reference it in my test, I would get various "Could not reference X of undefined" errors. Usually restarting VS Code would resolve the issue though, so I always figured that it was just a weird file detection error. Moving the shared API + SDK mocks into the setupTests.tsx seems to have resolved the failures I was seeing with your tests when I first checked out the branch.


fix: thread-safe pride

The pride feature was not thread safe at all (untested?)

Now it is :)

there was no reason to force push master lol, im just getting gud at git


How to actually reproduce an experiement

Sorry, I am new to sacred. I am not sure whether this is the right place to ask.
I know we can use Observers to record the information of experiments. But I am wondering how to use those data to actually reproduce an experiment? Do we have to manually apply those configs and codes?
Thanks

Yes, unfortunately, there is currently no automated process for reproducing experiments. You need to get the right source code (possibly from the database), and the config from the database and then run your experiment with ex.run(config_updatas=config_from_db).
I'm working on an automated way of doing that, but I'm rather busy, so it is going to take a while.

I have written a solution for myself, but I am not sure what a general solution would need to look like.
The way I am doing it is to create a virtual environment directly from python, install all the required packages, load all the source code files from the database and then run the main source code file. The main problem in my opinion is the storage of the data (if its quite big for example), which should be stored a the very same place as it was when initially running the experiment. Any thoughts on this topic. I would appreciate help, so that I can maybe try to generalize my solution and fit it into the sacred library.

@Leinadj Can you share your code somewhere? Although I am not using sacred now, I am still willing to see it!


Remove app/pretender dir in production builds

By default ember-cli includes anything found in app/* dir like app/pretender. To get around this we can remove the app/pretender from the app tree using broccoli-funnel when it's not needed.
Fixes #17

<3


ext: mbedtls: Extend mbedtls generic config

A follow up of discussion in #12063.
This PR extends the generic config file for mbedTLS with additional configuration options, including the following:

More algorithms to enable,
Add switch to enable all algorithms in specific group,
Add RNG section,
CTR_DRBG is no longer always enabled when AES is enabled. Now there is a config to enable/disable it with dependency to AES.

Additionally, second commits unifies prefixes for mbedTLS Kconfig options. Now all options (including those in generic config file) have MBEDTLS_ prefix.

Great response to challenges of https://github.com/zephyrproject-rtos/zephyr/pull/12063, I'd suggest some tweaks to Kconfig option ordering/wording.

Applied fixes according to the review.

LGTM, thanks.


Critical: .NET install domains and URLs are changing

Some .NET binaries and installers are hosted on Azure Content Delivery Network (CDN) domains that end in .azureedge.net. These domains are hosted by edg.io, which will soon cease operations due to bankruptcy. We are required to migrate to a new CDN and will be using new domains going forward. It is possible that .azureedge.net domains will have downtime or become permanently unavailable.

Current status:

azureedge.net CDN domains are functional
New CDN domains are functional
Updated install scripts that use new CDNs are available.

Recommended action:

Switch azureedge.net references to new domains
Consider switching to temporary install script URLs
Validate that firewall rules are resilient to using Akamai and/or Azure Front Door CDNs.

Last update: 2024.12.23
Next Update: 2024.12.26

You may need to adapt to these changes.
There is a chance that azureedge.net domains will cease being functional with downtime in the near term. We will do our best to avoid that. Moving your usage to the new CDN is the best path to avoiding service disruption.
Test links:

https://dotnetcli.azureedge.net/dotnet/Sdk/LTS/latest.version
https://dotnetcli.azureedge.net/dotnet/release-metadata/releases-index.json

Our plan is a work-in-progress and is expected to evolve.
Affected resources
Domains affected:

https://dotnetcli.azureedge.net
https://dotnetbuilds.azureedge.net

URLs affected:

https://dot.net/v1/dotnet-install.sh
https://dot.net/v1/dotnet-install.ps1
https://aka.ms/dotnet/ (various)

Not affected:

https://dotnet.microsoft.com/
https://download.visualstudio.microsoft.com/

There are many users of these resources, for example:

https://github.com/search?q=dotnetcli.azureedge.net&type=code
https://github.com/search?q=dot.net%2Fv1%2Fdotnet-install&type=code

Earlier today, we switched the two azureedge.net domains above to use Azure Traffic Manager. We intended this change to be transparent to all users. These domains are currently sending 100% of traffic to our edg.io CDNs. In the near term, we intend to start sending some or all traffic to a different CDN, which may break users with conservative firewall rules.
Users should not consider azureedge.net to be a long-term usable domain. Please move to the new domains as soon as possible. It is likely that these domains will be retired, however, no other party will be able to use them. We are not able to control the timing of these events.
Install script
The .NET install script is used to install .NET from our CDN. We are changing CDNs (documented in a following section), which requires us to change the install script to use the new CDN.
Updated scripts:

https://raw.githubusercontent.com/dotnet/install-scripts/6cbf2c9ff4615b468f39dfbd2e536e2f6fbe2f95/src/dotnet-install.ps1
https://raw.githubusercontent.com/dotnet/install-scripts/6cbf2c9ff4615b468f39dfbd2e536e2f6fbe2f95/src/dotnet-install.sh

Note: These scripts are for temporary usage and are unsigned (important for PowerShell users). We will update the install script at the official location at a later time.
The updated scripts prefer the new CDNs, while enabling fallback to the legacy azureedge.net domains. The legacy domains may be removed at a later point.
Tracking PRs:

dotnet/install-scripts #554
dotnet/install-scripts #555
dotnet/docs #44052

Notes (for the install script):

The -NoCdn or --no-cdn argument can be used to bypass using the CDN, which may help some users.
The -AzureFeed or --azure-feed argument can be used to specify an alternate storage account or CDN.

Plan for domains
There are multiple domains, used for different purposes.
Official builds
Official builds and JSON files are hosted via a CDN, available for use by the install script and other installers.

New: https://builds.dotnet.microsoft.com
Old: https://dotnetcli.azureedge.net

Note: Official builds are tested and signed by Microsoft. A microsoft.com domain was chosen to reflect that.
You can change from old to new domains by changing the domain section of the URL. The other parts of the URL do not need to change.
Example URLs:

New: https://builds.dotnet.microsoft.com/dotnet/Runtime/8.0.11/dotnet-runtime-8.0.11-linux-x64.tar.gz
Old: https://dotnetcli.azureedge.net/dotnet/Runtime/8.0.11/dotnet-runtime-8.0.11-linux-x64.tar.gz
New: https://builds.dotnet.microsoft.com/dotnet/release-metadata/releases-index.json
Old: https://dotnetcli.azureedge.net/dotnet/release-metadata/releases-index.json

A set of short links are available for official builds.
Link pattern:https://aka.ms/dotnet/[x.y]/[package].
Example URLs:

https://aka.ms/dotnet/9.0/dotnet-sdk-win-x64.zip
https://aka.ms/dotnet/8.0/aspnetcore-runtime-linux-x64.tar.gz

These links produce301 HTTP results that forward to our CDN.

Currently forward to:  https://dotnetcli.azureedge.net.
Will be changed to forward to: https://build.dotnet.microsoft.com.

CI builds
Continuous integration (CI) builds are hosted via a CDN, available via the install script and GitHub README files.

New: https://ci.dot.net
Old: https://dotnetbuilds.azureedge.net

Note: CI builds include a mix of tested and untested builds, signed and unsigned builds.
Example URLs:

New: https://ci.dot.net/public/Runtime/9.0.1-servicing.24610.11/dotnet-runtime-9.0.1-win-x64.exe
Old: https://dotnetbuilds.azureedge.net/public/Runtime/9.0.1-servicing.24610.11/dotnet-runtime-9.0.1-win-x64.exe

A set of short links are available for CI builds.
Link pattern:https://aka.ms/dotnet/[x.y]/daily/[package].
Example URLs:

https://aka.ms/dotnet/9.0/daily/dotnet-runtime-win-x64.exe
https://aka.ms/dotnet/9.0/daily/aspnetcore-runtime-linux-arm.tar.gz
https://aka.ms/dotnet/10.0.1xx/daily/dotnet-sdk-osx-arm64.pkg

These links produce301 HTTP results that forward to our CDN.

Currently forward to:  https://dotnetbuilds.azureedge.net.
Will be changed to forward to: https://ci.dot.net.

CI build pages use the CI short links.
Example build pages:

dotnet/runtime
dotnet/aspnetcore
dotnet/sdk

Remaining changes
The following changes are planned:

Update azureedge.net domains traffic manager configuration to use one or more new CDNs
Publish official install scripts (at https://dot.net/v1/ location).
Update aka.ms/dotnet short links to forward to new CDNs.

The following resources use URLs that will be updated to the new domains.

dotnet/dotnet-docker Dockerfiles
dotnet/core JSON files
dotnet/templating template data
iis.net is affected

Risks
There is a chance that the edgio CDN services will be terminated before we, our partners, and our users have a chance to adapt to the proposed changes in a staged and safe manner. If that happens, we will change existing scripts and links to use the new URLs and CDN immediately. That approach would maintain service for the bulk of users but might break users with firewall rules.
There is a significant chance that we will not be able to use azureedge.net domains for long.
We recommend that users adapt to these changes as quickly as possible.
Azure DevOps and GitHub Actions installation tools are dependent on some of these resources. We are working directly with those teams to maintain continuity of service. They are moving to the new domains at best speed.

@KalleOlaviNiemitalo we took it over, so it won’t be taken away.

@KalleOlaviNiemitalo we took it over, so it won’t be taken away.

so why not keep the current urls for like 1-2 more dont net versions so after .net 11 you have to use the new urls this would give people time to update their whitelists

Given this issue I'm wondering when Microsoft will provide their own domain registrar on Azure to prevent such issues in the future. Currently this is the only thing that is really missing on the Azure platform. I can host virtually anything on Azure but when it comes to domains I still need to resort to a third party. I can point all my nameservers to Azure, sure. But the domain itself needs to be hosted somewhere else.

Does this affect the installers in the Azure Devops pipelines?  We use a mix of classic and Yaml pipelines.

Users should not consider azureedge.net to be a long-term usable domain. Please move to the new domains as soon as possible. It is likely that these domains will be retired, however, no other party will be able to use them. We are not able to control the timing of these events.

I updated the issue with that text.
Separately, we are working closely with the Azure DevOps and GitHub Actions teams. They plan to start deploying changes to use the new domains on the 26th. Note that this situation is fluid, so that date could change. Both Azure DevOps and GitHub Actions have on-prem scenarios. We'll start addressing that in the new year.

Great question and thanks for the additional detail. We haven't heard of any such breakage example. It's certainly possible.
There are many other teams (and companies) with this same problem. The way that their impacted scenarios surface will be quite varied.

FYI @dotnet/distro-maintainers

I will share this with them @Varorbc.

maybe a noob question why didn’t just keep the old domain? why would a domain change be needed? couldn’t the old domain name not simply resolved to the new servers?

We asked the same question. We were told that this option wasn't being made available. We don't have more information on that.

What's the difference between getting official builds from builds.dotnet.microsoft.com and download.visualstudio.microsoft.com? Most of the JSON files seem to point to the latter.

No difference. Both are fine. download.visualstudio.microsoft.com is/was unaffected by this situation.
We'll be publishing new guidance after we've had a chance for some "downtime". It's likely that the new guidance will apply more to how the install script, GitHub Actions, and AzDo Tasks are implemented than requiring a typical user to do something significantly different.

It is unfortunate but understandable that MS is now in full control of the azureedge.net domain yet is unable to setup redirects.
A bit more confusing is this part:

URLs affected:

https://dot.net/v1/dotnet-install.sh
https://dot.net/v1/dotnet-install.ps1
https://aka.ms/dotnet/ (various)

These are already aliases, aka.ms is literally a redirect service.  Can these urls not be updated to the correct locations?  Infact it looks like some already are redirect to "not affected" domains:
wget2 https://dot.net/v1/dotnet-install.ps1
HTTP response 301  [https://dot.net/v1/dotnet-install.ps1]
URL 'https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1'

wget2 https://dot.net/v1/dotnet-install.sh
HTTP response 301  [https://dot.net/v1/dotnet-install.sh]
URL 'https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.sh'

Should they be removed from the affected list?
It does look like several of the aka.ms urls will 301 redirect as mentioned in this ticket already or showing in the actual location 301 returned that is is pointing to a safe domain.

@mitchcapper the contents of those scripts were changed to use the new CDNs. It should be transparent to most folks, but depending on how your infrastructure is set up like allow lists, copy of the scripts, etc. you might need to take action.

I updated the content above. It addresses the change in the install script. Thanks for asking for that clarification @mitchcapper. Good question.


Added support for inviting users via Admin API Integration

Whilst Admin API Integrations had the permissions to create invites they were
blocked from doing so at the HTTP level. We've removed this restriction for
creating Invites as well as browsing Roles, because a Role ID is necessary to
create an invite. The code was also not setup to support Admin API Integrations
as it made assumptions about the existence of a User. That has been updated in
the permissions layer - so that the Invites are limited to Contributors,
Authors and Editors as well as at the email layer, which has has the copy and
from address updated to reflect the lack of a User creating the Invite.

The email template has been duplicated and edited to support changes in content.
Originally:
Rediverge is using Ghost to publish things on the internet! John has invited you to join them. Please click the link below to activate your account.

...

If you have trouble activating your Rediverge account, you can reach out to John on<EMAIL_ADDRESS>for assistance.

Now:
Rediverge is using Ghost to publish things on the internet! You have been invited to join them. Please click the link below to activate your account.

...

If you have trouble activating your Rediverge account, you can reach out on<EMAIL_ADDRESS>for assistance.


Sickbeard MP4 Automator

Hey there. Assuming this is a friendly request area.
Most of us hate buffering so we convert the media to MP4 via a tool like Sickbeard MP4 Autoconvertor. That being said.... the installation of all the pre-reqs etc etc can be a real pain on a fresh install of ubuntu.
It would be sweet if your 'all in one' scripts included an MP4 convertor like sickbeard, with a walkthrough of the autoProcess.ini pre-programed with defaults that would support Direct Play instead of Plex Server transcoding.
Thanks for the consideration and your hard work.

Ok, here's the deal with that - I had transcoding working via nzbToMedia PP scripts, but the resulting MP4 simply would NOT play more than 3-5 seconds without freezing for me.
That being said, I'll look into MP4_automator some more - you're right, it's a little daunting to install and configure and it seems to overlap/replace nzbToMedia.


Derived lending market authority does not match the lending market authority provided

After the successful settlement, the following error log continues to appear until the following manual withdrawal of assets is performed.
Error log:
Total number of loans are 16007 and possible liquidation debts are 1501

Risk factor: 1.0006 borrowed amount: 0.11300469913827243953 deposit amount: 0.11293781769573352369
borrowed asset names: [mSOL] deposited asset names: [USDC]
obligation pubkey: 6mwpQUYMPR2B6vfdvFPMwgZEgnJxJoNah93a8yjhewkS

Risk factor: 0.9986 borrowed amount: 2.58027401228546719022 deposit amount: 2.58383573741491935321
borrowed asset names: [SOL] deposited asset names: [USDC,SOL]
obligation pubkey: 3oaUh7UD7cGgqmXdJb5L5NVVEUL6yN92i3vgaNQtFNog

Risk factor: 0.9961 borrowed amount: 1.22297761902600408377 deposit amount: 1.22770719476512583196
borrowed asset names: [USDC,SOL] deposited asset names: [USDC,MER]
obligation pubkey: 2cuYrNqXqyxtfU8hDiAsAUGETPBv6AUDXj8yex7XcueE

Risk factor: 0.9938 borrowed amount:<PHONE_NUMBER>701414514782 deposit amount:<PHONE_NUMBER>5005122846444
borrowed asset names: [SOL] deposited asset names: [USDC]
obligation pubkey: 6nxJixuJ3PkUoN817YU6jS2Bc5FzKb5PJGxxG26N4jAR

Risk factor: 0.9935 borrowed amount: 3.3416741054238528543 deposit amount: 3.36345212121688435908
borrowed asset names: [SOL,PAI] deposited asset names: [USDC]
obligation pubkey: 2XVuPEgPLK8qT4p7H4cJbiNRwqeZ7CL7KDUu9N5NSWQd

Risk factor: 0.9909 borrowed amount: 1.7688618085821416548 deposit amount: 1.78516208364606905815
borrowed asset names: [SOL] deposited asset names: [USDC]
obligation pubkey: 5zBgaeFXaAYP8VCUgE6cir1Hcw6sSj5jgJbj2YJYczYL

Risk factor: 0.9902 borrowed amount: 0.55158704319587709826 deposit amount: 0.55702531829371121554
borrowed asset names: [PAI,USDT,USDC,SOL] deposited asset names: [USDC,PAI,USDT]
obligation pubkey: A9Nhr5kocYauqaePc7WNibyWVWjpStCB3jUCUkhw5wuS

Risk factor: 0.9891 borrowed amount: 45.0642043251359262413 deposit amount: 45.5610902024681504241
borrowed asset names: [SOL,USDT] deposited asset names: [USDT]
obligation pubkey: 4CBdTGf5A6BVaCJn3m8jJWFbejnXJ4rFKfDwcq3GRkk8

Risk factor: 0.9829 borrowed amount:<PHONE_NUMBER>0946713532311 deposit amount:<PHONE_NUMBER>2815426387637
borrowed asset names: [SOL,mSOL] deposited asset names: [USDC,MER]
obligation pubkey: 3YPNiWgt9GtzbeSR76RkUvsV5xppFhF79toEXbMungDd

Risk factor: 0.9829 borrowed amount: 0.00014387979636914275 deposit amount: 0.00014637899878704832
borrowed asset names: [mSOL] deposited asset names: [USDC]
obligation pubkey: EH4TBkWxZNMqSj52Tb8bzVaGA48URkQq27V5JGKNfkRb

name: MER price: 0.46901358
name: PAI price: 1
name: SRM price: 7.5065113000000006
name: USDT price: 1.00004999
name: undefined price: 0
name: SBR price: 0.15672268
name: mSOL price: 198.31635
name: pSOL price: 198.31635
name: USDC price: 1
name: SOL price: 198.31635
name: BTC price: 62718.445

Time: Fri Oct 22 2021 09:33:42 GMT+0900 (日本標準時) - payer account 7LpKT3hBfhRWLok878cdaPFRGmsHNzrScneCR5fwDcW3, we have 1 accounts for liquidation
Liquidating obligation account 6mwpQUYMPR2B6vfdvFPMwgZEgnJxJoNah93a8yjhewkS which is owned by zb5xC4dehK2gn1fGHETaqahyfZTVKa9JjEWZw7CvAgG with risk factor: 1.00059219705058496482
which has borrowed 0.11300469913827243953 ...

liqudiation transaction sent: rP2kHjyUr1Sq45pt96DMr5rNFpnGcNkyZu5Xu5FgzVGUJETi54v6aWwGcV3iqGXQTUi5629DLUfKxjKyjm42mC3.
Redeem reserve collateral: 61YWFdT44kMWgv3b9RTarAS8h4dV8txr3hbUo4yyitZaYoN9uhECgyfz9u4uqGtGrPTsQLFP7bmNRAu4wKPjw7J7.
Transaction simulation failed: Error processing Instruction 2: custom program error: 0x3
    Program TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA invoke [1]
    Program log: Instruction: Approve
    Program TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA consumed 2297 of 200000 compute units
    Program TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA success
    Program Port7uDYB3wk6GJAw4KT1WpTeMtSu9bTcChBHkX2LfR invoke [1]
    Program log: Instruction: Refresh Reserve
    Program Port7uDYB3wk6GJAw4KT1WpTeMtSu9bTcChBHkX2LfR consumed 14473 of 200000 compute units
    Program Port7uDYB3wk6GJAw4KT1WpTeMtSu9bTcChBHkX2LfR success
    Program Port7uDYB3wk6GJAw4KT1WpTeMtSu9bTcChBHkX2LfR invoke [1]
    Program log: Instruction: Redeem Reserve Collateral
    Program log: Derived lending market authority does not match the lending market authority provided
    Program log: Market authority is invalid
    Program Port7uDYB3wk6GJAw4KT1WpTeMtSu9bTcChBHkX2LfR consumed 8211 of 200000 compute units
    Program Port7uDYB3wk6GJAw4KT1WpTeMtSu9bTcChBHkX2LfR failed: custom program error: 0x3
(node:32644) UnhandledPromiseRejectionWarning: Error: failed to send transaction: Transaction simulation failed: Error processing Instruction 2: custom program error: 0x3
    at Connection.sendEncodedTransaction (/home/xs666244/script/port/liquidator_org/node_modules/@solana/web3.js/src/connection.ts:3575:13)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at Connection.sendRawTransaction (/home/xs666244/script/port/liquidator_org/node_modules/@solana/web3.js/src/connection.ts:3535:20)
    at Connection.sendTransaction (/home/xs666244/script/port/liquidator_org/node_modules/@solana/web3.js/src/connection.ts:3523:12)
    at redeemCollateral (/home/xs666244/script/port/liquidator_org/src/partial.ts:663:21)
    at /home/xs666244/script/port/liquidator_org/src/partial.ts:169:7
(node:32644) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 17)

Thank you, it is sent.


[docs] Document that @emotion/react is not fully supported in the System

Hello!
Currently it's not really possible to use@emotion/react to write custom styles for MUI.
More precisely it is possible to use className and the css property but not the classes prop that the MUI component provides.
The reason for that is that the internal styles will always take precedence over the custom styles unless users explicitly increase specificity using !important or && which is not an acceptable solution.
As detailed here there is no way for the user to configure it's project to change this state of things.
I have opened an issue about it some time ago but for reasons that I perfectly understand you decided not to address it.
Considering this, I think it is best, to save users frustration, to let them know that @emotion/react is not really supported.

Fixed by https://github.com/mui/material-ui/pull/33205


support combining two n-gram LMs

What's the use case for this? Hot word detection?

What's the use case for this? Hot word detection?

Please have a look at
An Empirical Study of Language Model Integration for Transducer based Speech Recognition
The above paper uses a neural LM for ILM, while we are using an n-gram for ILM.
Please also have a look at
https://github.com/k2-fsa/icefall/blob/6434c8eadc0d4326e1db69824cf0e40dc9a71c8a/egs/librispeech/ASR/pruned_transducer_stateless2/beam_search.py#L1862
We will replace
https://github.com/k2-fsa/icefall/blob/6434c8eadc0d4326e1db69824cf0e40dc9a71c8a/egs/librispeech/ASR/pruned_transducer_stateless2/beam_search.py#L1868
with an n-gram LM
and merge
https://github.com/k2-fsa/icefall/blob/6434c8eadc0d4326e1db69824cf0e40dc9a71c8a/egs/librispeech/ASR/pruned_transducer_stateless2/beam_search.py#L1866
and
https://github.com/k2-fsa/icefall/blob/6434c8eadc0d4326e1db69824cf0e40dc9a71c8a/egs/librispeech/ASR/pruned_transducer_stateless2/beam_search.py#L1868
into a single n-gram LM with this pull-request.


Perfdash should support more e2e performance test.

Now, the implementation of Perfdash is specific to Density test and Load test. It is almost impossible to add support for other e2e performance tests without a refactoring.
We should refactor and generalize the code to make it support more e2e performance test.
@gmarek @yujuhong
/cc @kubernetes/sig-testing

+/infty
cc @hongchaodeng @kubernetes/sig-scalability

Close this one since #565 and kubernetes/kubernetes#22912 have been merged.


Issue #638 - Prefer ALSA backend

Implement #638
Feature proposal: Prefer ALSA backend over others
when multiple are enabled.
I implemented an environment variable CUBEB_PREFER_ALSA.
It can be used as follows:
CUBEB_PREFER_ALSA=y

Nevermind. For some reason I had tried the media.cubeb.backend = "alsa" setting, but I must have done something else wrong while trying it and it lead me to believe something like the PR would be an appropriate workaround to that config setting not working properly. On second try, the setting is working perfectly, and this feature isn't needed.

Nevermind. For some reason I had tried the media.cubeb.backend = "alsa" setting, but I must have done something else wrong while trying it and it lead me to believe something like the PR would be an appropriate workaround to that config setting not working properly. On second try, the setting is working perfectly, and this feature isn't needed.


migrate off deprecated github action

Migrate from last-successful-commit-action to nx-set-shas. This reflects upstream changes made in tj-actions/changed-files:
https://github.com/tj-actions/changed-files/pull/822

Do we need to update the permissions as well?
https://github.com/nrwl/nx-set-shas#permissions-in-v2
It says it needs:
    permissions:
      contents: 'read'
      actions: 'read'

Or will these be included by default?

I don't think actions are restricted by default on this repo but I can add those in case that is turned on later.


Correct commander options handling and add tests

In order to correct commander options handling and add tests, we refactor the command line handling into a function that can be easily tested.

@Ginxo, interested in this work at all?


Prevent mqueue from implicitely becoming a bind mount with --ipc=host

Currently, when running a container with --ipc=host, if /dev/mqueue is
a standard directory on the hos the daemon will bind mount it allowing
the container to create/modify files on the host.
This commit forces /dev/mqueue to always be of type mqueue except when
the user explicitely requested something to be bind mounted to
/dev/mqueue.
Signed-off-by: Kenfe-Mickael Laventure<EMAIL_ADDRESS>
ping @crosbymichael @rhatdan

Linking #19876

Job: Docker-PRs-userns FAILED:

---
pping root)
SKIP: docker_cli_run_test.go:3667: DockerSuite.TestRunModeNetContainerHostname (Test cannot be run when remapping root)
SKIP: docker_cli_run_test.go:2479: DockerSuite.TestRunModePidHost (Test cannot be run when remapping root)
PASS: docker_cli_run_test.go:2501: DockerSuite.TestRunModeUTSHost	0.848s
SKIP: docker_cli_run_test.go:2102: DockerSuite.TestRunMountOrdering (Test cannot be run when remapping root)

----------------------------------------------------------------------
FAIL: docker_cli_run_test.go:2434: DockerSuite.TestRunMountShmMqueueFromHost

docker_cli_run_test.go:2445:
    out, _ := dockerCmd(c, "run", "--name", "ipchost", "--ipc", "host", "busybox", "cat", "/dev/shm/test")
/go/src/github.com/docker/docker/pkg/integration/dockerCmd_utils.go:35:
    c.Assert(err, check.IsNil, check.Commentf("%q failed with errors: %s, %v", strings.Join(args, " "), out, err))
... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0xc820b12d40)} ("exit status 125")
... "run --name ipchost --ipc host busybox cat /dev/shm/te
---

Job: Docker-PRs-Win2Lin FAILED:

---
ttachSilent	1.716s
PASS: docker_cli_start_test.go:112: DockerSuite.TestStartMultipleContainers	2.299s
PASS: docker_cli_start_test.go:96: DockerSuite.TestStartPausedContainer	0.850s
PASS: docker_cli_start_test.go:71: DockerSuite.TestStartRecordError	1.819s
PASS: docker_api_containers_test.go:1425: DockerSuite.TestStartWithNilDNS	0.688s
PASS: docker_api_containers_test.go:882: DockerSuite.TestStartWithTooLowMemoryLimit	0.141s

----------------------------------------------------------------------
FAIL: docker_cli_stats_test.go:98: DockerSuite.TestStatsAllNewContainersAdded

docker_cli_stats_test.go:131:
    c.Fatal("failed to observe new container created added to stats")
... Error: failed to observe new container created added to stats

----------------------------------------------------------------------
PASS: docker_cli_stats_test.go:80: DockerSuite.TestStatsAllNoStream	3.498s
PASS: docker_cli_stats_test.go:56: DockerSuite.TestStatsAllRunningNoStream	3.910s
PASS: docker_cli_stats_test.go:43: DockerSuite.TestStatsContainerNotFound	3.175s
PASS: docker_cli_stats
---

Job: Docker-PRs-gccgo FAILED:

---
docker_integration_cli.DockerSuite	7.064s
PASS: docker_cli_run_test.go:2701: TestRunRestartMaxRetries.pN52_github_com_docker_docker_integration_cli.DockerSuite	3.985s
PASS: docker_cli_run_test.go:2147: TestRunReuseBindVolumeThatIsSymlink.pN52_github_com_docker_docker_integration_cli.DockerSuite	2.124s
PASS: docker_cli_run_test.go:1179: TestRunRootWorkdir.pN52_github_com_docker_docker_integration_cli.DockerSuite	1.091s

----------------------------------------------------------------------
FAIL: docker_cli_run_unix_test.go:842: TestRunSeccompAllowAptKey.pN52_github_com_docker_docker_integration_cli.DockerSuite

docker_cli_run_unix_test.go:848:
    c.Fatalf("expected apt-key with seccomp to succeed, got %s: %v", out, err)
... Error: expected apt-key with seccomp to succeed, got Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.OBAzubhEAg --no-auto-check-trustdb --trust-model always --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-security-automat
---

Job: Docker-PRs-WoW-TP4 FAILED:

---
b0267a.
+ ec=125
+ set +x

----------------------------------
ERROR: Failed to build test binary
----------------------------------

-----------------------------------------------
ERROR: Failed with exitcode 125 at Tue Feb  9 16:33:24 CUT 2016.
-----------------------------------------------

INFO: Tidying up at end of run
INFO: Nuking /d/CI
INFO: Zapped successfully
INFO: End of cleanup
INFO: Ended at Tue Feb  9 16:33:25 CUT 2016 (1m 12s)
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe D:\temp\hudson6600222008511807087.sh
+ set +e
+ set +x
INFO: End of cleanup
Notifying endpoint 'HTTP:https://leeroy.dockerproject.org/notification/jenkins'
---

Job: Docker-PRs-WoW-TP4 FAILED:

---
97081c.
+ ec=125
+ set +x

----------------------------------
ERROR: Failed to build test binary
----------------------------------

-----------------------------------------------
ERROR: Failed with exitcode 125 at Tue Feb  9 17:00:11 CUT 2016.
-----------------------------------------------

INFO: Tidying up at end of run
INFO: Nuking /d/CI
INFO: Zapped successfully
INFO: End of cleanup
INFO: Ended at Tue Feb  9 17:00:12 CUT 2016 (1m 12s)
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe D:\temp\hudson4304507035559340228.sh
+ set +e
+ set +x
INFO: End of cleanup
Notifying endpoint 'HTTP:https://leeroy.dockerproject.org/notification/jenkins'
---

Job: Docker-PRs-userns FAILED:

---
pping root)
SKIP: docker_cli_run_test.go:3667: DockerSuite.TestRunModeNetContainerHostname (Test cannot be run when remapping root)
SKIP: docker_cli_run_test.go:2479: DockerSuite.TestRunModePidHost (Test cannot be run when remapping root)
PASS: docker_cli_run_test.go:2501: DockerSuite.TestRunModeUTSHost	1.603s
SKIP: docker_cli_run_test.go:2102: DockerSuite.TestRunMountOrdering (Test cannot be run when remapping root)

----------------------------------------------------------------------
FAIL: docker_cli_run_test.go:2434: DockerSuite.TestRunMountShmMqueueFromHost

docker_cli_run_test.go:2445:
    out, _ := dockerCmd(c, "run", "--name", "ipchost", "--ipc", "host", "busybox", "cat", "/dev/shm/test")
/go/src/github.com/docker/docker/pkg/integration/dockerCmd_utils.go:35:
    c.Assert(err, check.IsNil, check.Commentf("%q failed with errors: %s, %v", strings.Join(args, " "), out, err))
... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0xc820bf0460)} ("exit status 125")
... "run --name ipchost --ipc host busybox cat /dev/shm/te
---

Job: Docker-PRs-userns FAILED:

---
pping root)
SKIP: docker_cli_run_test.go:3667: DockerSuite.TestRunModeNetContainerHostname (Test cannot be run when remapping root)
SKIP: docker_cli_run_test.go:2479: DockerSuite.TestRunModePidHost (Test cannot be run when remapping root)
PASS: docker_cli_run_test.go:2501: DockerSuite.TestRunModeUTSHost	0.967s
SKIP: docker_cli_run_test.go:2102: DockerSuite.TestRunMountOrdering (Test cannot be run when remapping root)

----------------------------------------------------------------------
FAIL: docker_cli_run_test.go:2434: DockerSuite.TestRunMountShmMqueueFromHost

docker_cli_run_test.go:2445:
    out, _ := dockerCmd(c, "run", "--name", "ipchost", "--ipc", "host", "busybox", "cat", "/dev/shm/test")
/go/src/github.com/docker/docker/pkg/integration/dockerCmd_utils.go:35:
    c.Assert(err, check.IsNil, check.Commentf("%q failed with errors: %s, %v", strings.Join(args, " "), out, err))
... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0xc821aa52a0)} ("exit status 125")
... "run --name ipchost --ipc host busybox cat /dev/shm/te
---

Job: Docker-PRs-WoW-TP4 FAILED:

---
a7865e.
+ ec=125
+ set +x

----------------------------------
ERROR: Failed to build test binary
----------------------------------

-----------------------------------------------
ERROR: Failed with exitcode 125 at Tue Feb  9 17:40:40 CUT 2016.
-----------------------------------------------

INFO: Tidying up at end of run
INFO: Nuking /d/CI
INFO: Zapped successfully
INFO: End of cleanup
INFO: Ended at Tue Feb  9 17:40:41 CUT 2016 (1m 13s)
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe D:\temp\hudson8544444697795995595.sh
+ set +e
+ set +x
INFO: End of cleanup
Notifying endpoint 'HTTP:https://leeroy.dockerproject.org/notification/jenkins'
---

LGTM

Job: Docker-PRs-Win2Lin FAILED:

---
         125.1 MB
busybox             latest              d9551b4026f0        9 weeks ago         1.113 MB
hello-world         frozen              690ed74de00f        3 months ago        960 B
emptyfs             latest              11f64303f0f7        2 years ago         0 B

-----------------------------------------------
Windows CI Timeout Detection - End of debugging
-----------------------------------------------

c:\scripts>exit 0
POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 0
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe C:\Users\Jenkins\AppData\Local\Temp\hudson3176938035746148017.sh
+ set +x

---

Job: Docker-PRs-WoW-TP4 FAILED:

---
469117.
+ ec=125
+ set +x

----------------------------------
ERROR: Failed to build test binary
----------------------------------

-----------------------------------------------
ERROR: Failed with exitcode 125 at Tue Feb  9 19:32:37 CUT 2016.
-----------------------------------------------

INFO: Tidying up at end of run
INFO: Nuking /d/CI
INFO: Zapped successfully
INFO: End of cleanup
INFO: Ended at Tue Feb  9 19:32:38 CUT 2016 (1m 14s)
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe D:\temp\hudson7295603797677312460.sh
+ set +e
+ set +x
INFO: End of cleanup
Notifying endpoint 'HTTP:https://leeroy.dockerproject.org/notification/jenkins'
---

Looks like you have a couple of extra commits

LGTM

@cpuguy83 thanks, fixed.

LGTM

Job: Docker-PRs-WoW-TP4 FAILED:

---
cd580c.
+ ec=125
+ set +x

----------------------------------
ERROR: Failed to build test binary
----------------------------------

-----------------------------------------------
ERROR: Failed with exitcode 125 at Tue Feb  9 21:38:53 CUT 2016.
-----------------------------------------------

INFO: Tidying up at end of run
INFO: Nuking /d/CI
INFO: Zapped successfully
INFO: End of cleanup
INFO: Ended at Tue Feb  9 21:38:54 CUT 2016 (1m 13s)
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe D:\temp\hudson7516330331215967345.sh
+ set +e
+ set +x
INFO: End of cleanup
Notifying endpoint 'HTTP:https://leeroy.dockerproject.org/notification/jenkins'
---

Job: Docker-PRs-Win2Lin FAILED:

---
aking bundle: binary (in bundles/1.11.0-dev/binary)
Building: bundles/1.11.0-dev/binary/docker-1.11.0-dev
# github.com/docker/docker/docker
/usr/local/go/pkg/tool/linux_amd64/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory

---
Build step 'Execute shell' marked build as failure
Performing Post build task...
Could not match :Build timed out  : False
Logical operation result is FALSE
Skipping script  : cd c:\scripts
sh timeout-post-build.sh

END OF POST BUILD TASK 	: 0
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe C:\Users\Jenkins\AppData\Local\Temp\hudson780522057342652313.sh
+ set +x

---

Job: Docker-PRs-WoW-TP4 FAILED:

---
1ecd24.
+ ec=125
+ set +x

----------------------------------
ERROR: Failed to build test binary
----------------------------------

-----------------------------------------------
ERROR: Failed with exitcode 125 at Tue Feb  9 22:18:52 CUT 2016.
-----------------------------------------------

INFO: Tidying up at end of run
INFO: Nuking /d/CI
INFO: Zapped successfully
INFO: End of cleanup
INFO: Ended at Tue Feb  9 22:18:53 CUT 2016 (1m 16s)
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe D:\temp\hudson170925096743446905.sh
+ set +e
+ set +x
INFO: End of cleanup
Notifying endpoint 'HTTP:https://leeroy.dockerproject.org/notification/jenkins'
---

LGTM pending janky.


Abort MPU returns 404 for all regions when Upload Id doesn't exist

Tests reveal that AWS S3 returns 404 for us-east-1 and 204 for all other regions. We have a customer complaining about this incorrect behavior. We could leverage usEastBehavior to toggle the legacy behavior.
The fix should be against 6.2.5.

As discussed, we will return a 204 in all cases in 6.2.  In 6.3, where we have the usEastBehavior concept, we will toggle.


vasttrafik: update token on read error

Description:
Updates token when an read error occurs.
Seems like the token sometimes expires before it should.
Related issue (if applicable): fixes #
#5641
If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[ ] New dependencies are only imported inside functions that use them ([example][ex-import]).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

Hi @persandstrom,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!


When the code will be released?

Hello, thank you for your great work! When the code will be released?

Hi,
Sorry for the release delay. This period is a bit busy for us, and we will clean the code and release it together with metadata in early April.
Yiming

Released


Reveal and document pgm.enableReverseMode()

Internally, this library appears to use an enableReverseMode() function to reverse the commands of a migration when inferring a down() migration.
At my company when we revert a change we want to just make a new migration that does the inverse of what a reverted migration does. For migrations with a down() migration, this is easy - just call it in the up() migration.
But for migrations where it is inferred, it is not obvious how you would call the automatic down() migration for a given up() migration. But! Internally this library's enableReverseMode() function would do the trick, just call it first before calling the up()      migration.
But, the TypeScript interface doesn't say it exists, nor is it mentioned in the docs. But I'm pretty sure this should generally work.
So my suggestion is to not hide this and actually make it be a documented part of this library. Even further, it would potentially make sense to even have a CLI command to generate a "revert" migration for a given migration.

@osdiab You can consider using @lorefnon/ts-pg-migrate where I have exposed this. I maintain that fork because I needed some features from a few PRs here that haven't received any attention in many months.
 Would you like to work with me together on node-pg-migrate? I got repo-admin rights (not org-admin).

Beside that, I need to have a look into what enableReverseMode is actually doing, and/or if this is outdated.

Hi yeah, good to see this repo maintained once more.
I have a few minor features in my fork. I use this in production. I'll send separate PRs for them over the next few days.


Fix #2330 Added cancel option in filter dialog box.

Fixes #2330
Changes: Added the cancel option in the dialog box. Also removed the bug when the user presses back. When the user pressed back all the selected options were removed from the track but still the filter bar was showing the selected filtering options. Now on pressing back only the dialog box disappears.
Screenshot of the change:

@raj10071997 Screenshot please.

@srv-twry Added the screenshot of the change and also updated the issue. Sorry for the delay.

@iamareebjamal  Please review this PR.

@iamareebjamal Please merge this PR if no changes are required in it.


When used with multiple watch paths block vars are improperly assigned

When I create a new Filewatcher with an array of paths it does not properly assign the block vars. Instead I get a Hash assigned to the first variable.
Filewatcher.new(watch_dirs).watch do |fn, ev|

fn will now contain
{"/path/to/index.md"=>:deleted}

ev is empty.
Notice also, that the event is also :deleted and is not :changed like it should be.
I have validated that this does work properly using the gem version of filewatcher, albeit you now have to use FileWatcher.new, not Filewatcher.new

Hello!
You're absolutely right. I'm sorry, I'll try to fix this soon (and cover by tests).

No worries! Just thought you'd like to know. Thanks for providing this gem, it's nice and lightweight. I am using it for one of my projects, https://github.com/ngzax/urbit-sync

@ngzax, some news:

changes argument instead of fn, en should be, it's correct for now
README is incorrect about this
But I decided to throw every option to Ruby API, and calling block with filename, event arguments (calling multiple times with every option), almost like in the README now
README is fixed (on my local), I'm fixing (and completing) tests

Stay tuned :ok_hand:

Tests fixed
Bug with permanent deleted event fixed
Tests supplemented

You can track the fight between me and Travis CI in #76 now.

I have verified that this is now working properly. Thanks for the quick fix.


Add example developerkitaudio support for firmware(ISD9160) v1.0.2, m…

…ake the leds turned on or off correctly when use "record and playback".

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


Split "full PREP example" into two: 1) show how to use, 2) show validation against matlab

Currently the full PREP example does both, showing how it can be used, and validating the results against the Matlab results.
https://pyprep.readthedocs.io/en/latest/auto_examples/index.html
I think we should rather have two examples:

one example where PREP usage is shown more extensively and with more explanations than currently
and another example with a focus on validation against the Matlab results (here, the plotting code should be improved, because currently it's very messy to read and probably lots of unneeded code duplication)

Note that regarding the validation part of the example, we should also rely on @a-hurst's https://github.com/a-hurst/matprep_artifacts/tree/master
instead of the old saved data. As for some reason, things have become out of sync and it looks terrible now: https://pyprep.readthedocs.io/en/latest/auto_examples/run_full_prep.html#sphx-glr-auto-examples-run-full-prep-py


add update customers

update customers Information

Hi Tina, could you also write the testing functions for your update api as I mentioned in the slack chat?

Hi Tina, could you also write the testing functions for your update api as I mentioned in the slack chat?

Hi Bobby, I just added the testing functions. Thank you for the reminder.

We have some failing tests on this branch, I can fix them but don't think we should merge yet

@liyingxin97 I did some quick test updates to this branch just because it was approved and wanted to make sure we didn't merge in any failing test cases to main. Just want to make sure these changes look ok to you

@devops-customers-squad/squad-members one thing I'm realizing is that we forgot to implement the subordinate addresses API (described in the issue). Anyone know what we're supposed to do in this case - should we make a new issue, or reopen the issue?

@devops-customers-squad/squad-members one thing I'm realizing is that we forgot to implement the subordinate addresses API (described in the issue). Anyone know what we're supposed to do in this case - should we make a new issue, or reopen the issue?

I think we can just move it under in progress again


Binary lost its Copy and Clone impls in 0.21.1 and 0.22

I think by mistake, as putting #[derive(Copy, Clone)] back on it compiles and passes the tests without error on both.

It's back on master and releases are pending.

We will release 0.22.0 soonish, which contains the fix.


fix(ci): update build submodule and remove deprecated linters

Description of your changes

Updated submodule build to 75a9fe3ae6b6de82c5f7ddc6a267617940f16b83 (refs/heads/master) .
Removed linter interfacer (deprecated, archived, last commit was 6 years ago).
Replaced linter golint (deprecated) with the recommended replacement revive.
Updated .golangci.yml to reflect the changes above and replaced deprecated configurations with new key names.

I have:

[X] Read and followed Crossplane's contribution process.
[X] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
It only affects the reviewable target in the Makefile, so make reviewable test as indicated in the PR template is more than enough.

I was unable to run make reviewable when I tried to help @mateusz-lubanski-sinch  with PR#116.
This change addresses all the warnings and errors that I got when running it.

I'm currently trying to get build work. Do not merge yet.

Superseededd by #119


B-21469-INT Add move canceler to history & audit logs

Agility ticket
Summary
Add move cancelation to move history.

Cancel a move
As an office user, confirm events exist in the move history of the move for the move being canceled, and the shipments being canceled
Try and break

Can you add some AC to the story in agility please (to cover both customer and office user canceling a move).

When I cancel a move with a PPM shipment, I'm seeing a row with blank Details.  This is canceled as an SC.


Build my own custom keyboard

Or, maybe create custom modules in FLUX.
https://www.youtube.com/watch?v=N7OVagiblPo


Ensure proper usage of yargs + npm create script without using --

This PR is part of #700
There was a reason for me adding the -- requirement and your changes (reflected in #703) just steamrolled over those necessary changes without discussion. I am providing you 2 different options that I strongly encourage you picking and merging one. I also would appreciate PR reviews rather than just coding over what you want/don't want; that way we can have a discussion when you have a disagreement so I can explain why I made the decisions I did.
This PR is option 1 (without using --, but using positional args)
--
If you don't want to use the -- that NPM requires you to use to pass --flag arguments (what yargs calls "options"), then you need to change the create script to use strictly positional arguments.
This is because without the --, NPM parses your --location and --folder as NPM flags instead of create.ts flags. It tries to parse, determines they do nothing, ignores them, and proceeds to pass in the other arguments.

See the top red circle where --folder and --location are actually dropped. Then further you can see how location actually parsed iamfolder due to guessing it's position from the command string

Ah, I see. I only ever tested --location followed by --folder.

Ah, I see. I only ever tested --location followed by --folder.

Closing in favor of #707

Closing in favor of #707


[BUG] Settings Scaling in V10

Module Version: v0.11.6
Expected behavior
Settings displayed as standard
Screenshots

Browser:
Foundry Version: V10
Game System: dnd5e
Additional context
minor scaling of the settings windows fixes this error.

came here to comment the same thing. I know you have a lot of projects so this ones definitely low priority because like they mentioned if you drag the window to be maybe 3 pixels wider the problem is fixed.

This is a issue with foundryvtt, should be solved with the next patch release ?
https://github.com/foundryvtt/foundryvtt/issues/8175


How to install the old version of ffmpeg?

How to install the old version of ffmpeg, via "brew"?

Please fill out one of the templates on: https://github.com/Homebrew/brew/issues/new/choose

If you want to ask a question please do so on our Discourse: https://discourse.brew.sh

We will close issues asking questions without comment.

I think this question is better suited for Discourse: https://discourse.brew.sh

From the issue template:

Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you do not read fill out the issue template repeatedly you will be blocked from ever submitting issues to Homebrew again.

If you add the necessary information to this issue ((don't create a new one, please) then this issue may be reopened.

If you add the necessary information to this issue (don't create a new one, please) then this issue may be reopened.

Although not in this case: please ask on our Discourse or IRC instead.


Update with The Hateful Eight data

Impaired hearing subtitles file can provide word data: https://pastebin.com/raw/BwaWPw5e

Ah, nvm, looks like the data doesn't get updated after the article's are published.


Images location

@ankush-me
Hi, where are the 5 images (hiking, indian+musicians, sandwich, sea, village) that Synthtext script uses saved, from where the script load this images? Is there some file or? Ty

Please check here.

Yea but how to run .h5 file? With matlab or?? I don't understand that .h5 file

I am not sure what you mean by 'run[ning]' that file. That h5 file is used by the generation script to get information about the background images.

Okay but how did you put images into this file? Yes I checked here "https://github.com/ankush-me/SynthText#generating-samples" but I can't figure out. Four days I can't understand how to add my own background images. Can you just tell me what do I need to do to add images into .h5 file or how to open this file or I don't know? Where I put my own images??

I am sorry this has been difficult for you.
As mentioned in the readme, for adding new images, you need to obtain their segmentations and depth values. Once you have them you need to modify the script (here: Lines 102-113) to read that information in.  It is not required to dump the new images in an h5 file -- it is just given as a container for the 5 sample images. You store the image, segmentation, depth data for each new image as you desire as long as there are loaded correctly in the generation script.

Okay I get it, so if I understand I need get depth value from predict_depth.m and segmentation value from run_ucm.m and floodFill.py?
And then this values I put in the script?

Yes that is correct in principle, but again, generating a new h5 file is not required -- you can just load the three things directly.  Also note that predict_depth.m and run_ucm.m are now quite dated --- it will be difficult to make them run (as they depend on external codebases (that too in MATLAB!) which may not be maintained anymore). It will be easier to use more modern alternatives to both of these.

Also 8K images with their segmentation and depth values are provided --- check the readme.


Add Docker attestation and provenance

Dockerfile

change user to nonroot
add the BUILDKIT_SBOM_SCAN_CONTEXT buildarg for proper SBOM creation Docker/build.py
add provenance
add sbom attestation
some formattíng

This is so the FastSurfer docker image satisfies docker scout criteria.
At this point, it might be necessary to check whether the user inside the docker container is manually entered, or otherwise weird things happen (similar to our --allow-root flag).
I will look into that.

I hope this finally works.... unfortunately, the attestation changes mean that people that want to do attestation, need to change a couple of things, such as:

change to the containerd image store
set up a docker-container buildx builder

but the basic build should still work without that, just attestation are a bit weird :(.

please add some documentation to readme, including attestation requirements.


Implement our own memory allocator

Currently we use https://crates.io/crates/linked-list-allocator. The problem with external allocator is we don't know if it is going to access the memory that already freed or not. We want to change page protection to none so we can catch when the PS4 app try to access the memory that already freed.

Another problem is we cannot do partial de-allocation with external allocator. We need this ability because munmap can partially free the allocated region.

Just found some techniques for how to allocate pages with PS4 alignment on both *nix and Windows. If we are successful with this we don't need this anymore.


Deletion of default site in site_mstr

The SiteMaint class allows the deletion of a site record that is also the default site value.   This causes all subsequent lookups with getDefaultSite() method to fail.   Adding code to prevent deletion of default site records.   User must assign new default site 'before' deleting old site record.

This is resolved with patch 6.1.1

deployed at patch 6.1.1


IVT Syscall Support Request/Feature

Hi All,
I am looking to play around with triggering software interrupts on the RP2040, and I have gotten some conflicting documentation on weather or not this would be possible. The IVT should be able to be configured from the V6 spec from ARM, but I can't quite determine if that is possible on the 2040.
I want to experiment with "thread safety" and airlift some of the code at my job out of deep gluey MCU code into more isolated processes. I know that RTOS exists, this is more of a learning exercise and I would like to add a few examples to the main repo.
Could someone point me at the correct place in either the ARM docs or the Pico docs on how to manually configure an internal software interrupt? (I am trying to avoid the hack of using the PIO between multiple cores to use that for interrupting)
Thanks!
Scott

"2.3.2. Interrupts" in https://datasheets.raspberrypi.com/rp2040/rp2040-datasheet.pdf and "4.1.14. hardware_irq" in https://datasheets.raspberrypi.com/pico/raspberry-pi-pico-c-sdk.pdf ?

this is not an SDK issue (if the documentation is insufficient then open an issue in pico-feedback)


Unexpected behaviour when using v-on:input and v-bind:value instead of v-model.

Version
2.6.10
Reproduction link
https://jsfiddle.net/9mj0nakc/2/
Steps to reproduce
Type in each input
What is expected?
Input box 2 to be bound to variable test.b
What is actually happening?
It doesn't behave like v-model

On this page:
https://vuejs.org/v2/guide/components.html#Using-v-model-on-Components
It says that
<input v-model="searchText">
does the same thing as:
<input
  v-bind:value="searchText"
  v-on:input="searchText = $event.target.value"
>

But it appears this is not true when referencing a property of a variable, e.g. var['prop'].
If you do not think this is a problem, I would like to at least understand:

what is special/different about v-model vs the second method that makes it work properly and listen to changes on the prop when the on&bind combination doesn't seem to listen to changes.
and how I could make on&bind it work similarly to v-model.

you must set the initial value of b. v-model gets around this by always using $set

Please, next time consider using the forum, the Discord server or StackOverflow for questions first. But feel free to come back and open an issue if it turns out to be a bug 🙂

I have signed up to the discord server, thank you for the suggestion.
Perhaps the documentation should say something along the lines of:

does the same thing as:

<input
  v-bind:value="search.text"
  v-on:input="$set(search.'text',$event.target.value)"
>

instead of

does the same thing as:

<input
  v-bind:value="searchText"
  v-on:input="searchText = $event.target.value"
>

because it does not do 'the same thing as' currently described.


article command fails when using --blog option

Using middleman 4.1.7 and middleman-blog 4.0.1
When I attempt to generate an article using the --blog option, it fails. For example, I have a blogs named "blog" and "work"
middleman article 'Test' --blog work
I get:
/Users/andrewcroce/.rvm/gems/ruby-2.3.1/bundler/gems/middleman-blog-1f154d8846e2/lib/middleman-blog/commands/article.rb:55:in 'throw': uncaught throw "Could not find an active blog instance named work" (UncaughtThrowError)

Similar error for the "blog" blog.
The command works fine without specifying the --blog option, and defaults to the first blog "blog".
Heres the blog activations from my config:
activate :blog do |blog|
  blog.name = 'blog'
  blog.prefix = 'blog'
  blog.sources = "{year}/{month}/{day}-{title}/{title}.html"
  blog.new_article_template = File.expand_path('../source/blog/article.erb', __FILE__)
  blog.default_extension = '.markdown.erb'
  blog.permalink = "{title}.html"
  blog.taglink = 'tags/{tag}.html'
  blog.layout = "article"
  blog.paginate = true
  blog.tag_template = "tag"
  blog.summary_separator = /READMORE/
end

activate :blog do |blog|
  blog.name = 'work'
  blog.prefix = 'work'
  blog.sources = "{title}/{title}.html"
  blog.new_article_template = File.expand_path('../source/work/case_study.erb', __FILE__)
  blog.default_extension = '.markdown.erb'
  blog.permalink = "work/{title}.html"
  blog.layout = "case_study"
end

Thanks!
UPDATE:
For the record, I have manually created article files in the "work" blog, and they do appear to be properly queried using blog(work).articles.

Digging into this a bit, in article.rb line 46:
blog_inst = if options[:blog]
   app.extensions[:blog][options[:blog]]
else
   app.extensions[:blog].values.first
end

Its trying to access the blog instance by key, as if the keys were the same as the blog names. But they're not, the keys are instance_0 and instance_1.

Just to confirm this issue does exist.

Any updates on this ?

I just submitted a PR for this: #307. Note, this is really just a hack to get it working. I'm not a Ruby dev, just a Middleman user who needed this to work. There is certainly a better way to fix this, so the key names DO match the blog names.

Has this moved? Having the same issue.

Hiya
@mamela The PR was merged into Master - https://github.com/middleman/middleman-blog/pull/307
Please reference this in your Gemfile for now
gem "middleman-blog",       git: "https://github.com/middleman/middleman-blog.git",       branch: "master"
Closing as PR merged - if still an issue please re-open


More rules need to be updated

I have manually replicated the changes in https://github.com/autoclouddev/terraform-aws-autocloud-access-role/pull/2
but I am still getting a warning;

@tparvu thanks for the follow up here, we will take a look on our end on Monday and keep you updated.


4.0: Autocomplete list for round names is no longer present

Compared to 3.0, the autocomplete list for round names no longer exists

Can confirm that the functionality works in 4.07!