rename testing.go to base_test.go since it will be included in binary

Codecov Report

Merging #226 into master will decrease coverage by 2.53%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #226      +/-   ##
==========================================
- Coverage   82.99%   80.45%   -2.54%
==========================================
  Files          43        8      -35
  Lines        2981     1847    -1134
==========================================
- Hits         2474     1486     -988
+ Misses        353      273      -80
+ Partials      154       88      -66

Impacted Files
Coverage Δ

vm/vmConvertToX.go
52.3% <0%> (-6.16%)
:arrow_down:

vm/vmStmt.go
79.87% <0%> (-3.72%)
:arrow_down:

vm/vmToX.go
76.63% <0%> (-1.87%)
:arrow_down:

vm/vmExpr.go
81.83% <0%> (-0.92%)
:arrow_down:

vm/vmExprFunction.go
69.63% <0%> (-0.81%)
:arrow_down:

packages/sortGo18.go

packages/osNotAppEngine.go

packages/sort.go

packages/net.url.go

packages/math.rand.go

... and 29 more

Continue to review full report at Codecov.

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


Updated censor.go to work with the improved flexibility of falsepositives.go

I changed the detector variable to use the new goaway.DefaultFalsePositives function as the false positives filter. This lets any word to pass without triggering the default profanities.
The code for the edited falsepositives.go is at https://github.com/CaenJones/go-away/blob/master/falsepositives.go
Thank you to:
QuackDuck
Arkaeriit
Google
Derplord264
*this will also adapt the admin rights to my home pc not my school laptop :)

Try to develop with a clone of Devzat so you can make sure compile works


Removing MongoDB dependency?

Following up on an earlier conversation with @bentaculum about removing MongoDB as a dependency.
What exactly would be involved with something like this? Eg: Is a replacement required or can it be removed entirely, what technical issues might this cause, etc. I see that pymongo is used in the train, predict, and predict_multiple scripts, but I don't have a lot of insight beyond that.

(For extra context: our HPC team have said that this is a blocker for use (a persistent service requiring execution from a privileged account is not a good fit for shared use HPC systems, and there are possible cybersecurity risks that limit our options. So it would be nice if we could work around that issue altogether)

Hi Genevieve, @patrickstock is working on making jupyter notebooks (potentially even cloud hosted on Colab/Sagemaker) for inference (WIP) and training (coming soon) that don't talk to an experiment tracking database, see here. This will result in getting rid of the mongoDB dependency entirely. We'll be happy to notify you once this is ready for trying it out.

Very cool, we'd love to try that out when it's ready


Adding and Using MDX on the wiki theme breaks the template

When converting your index page to mdx several things break on the default wiki layout.vto:
toc and footnotes are extracted from markdown, using the plugins from that only works for markdown-it .

Hey this follows up a help thread on the lume discord.
Thank you so much for helping. I've really wanted to use Deno for something large and I think I've found just the thing, fresh never excited me as much as lume. I'm excited to finally build.


python3Packages.dasbus: 1.7 -> unstable-11-10-2022

change format to setuptools
add hatchling as a build time dep
fix #212879 and https://github.com/NixOS/nixpkgs/commit/6ad9cb0b5f4645a45eee094721de30b547021218#commitcomment-97674867
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

3 packages built:

nwg-panel
python310Packages.dasbus
python311Packages.dasbus

Force-pushed because I forgot to add pytestCheckHook for tests. (also tests succeed)

Thanks for looking into 👍🏻

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/819

@ofborg build python310Packages.dasbus


[$250] Oldest unread message not displayed in Concierge

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

Version Number: 9.0.67-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @garrettmknight
Slack conversation (hyperlinked to channel name): ts_external_expensify_convert
Action Performed:

Signup for a new user and choose manage my team
Choose number of employees and accounting software option
Click Continue
Link for session: https://fsty.io/v/ujphfF43

Expected Result:
Oldest unread message displayed in Concierge
Actual Result:
Oldest unread message not displayed in Concierge, scroll to the bottom of the setup tasks/message
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

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

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

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/29b61d82-88ed-4a4c-ba67-dd8f6218f25d
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021866434424819479758
Upwork Job ID:<PHONE_NUMBER>819479758
Last Price Increase: 2024-12-10

Issue OwnerCurrent Issue Owner: @garrettmknight

I'm almost certain this is by design. @garrettmknight do you bring this up in Slack?

Bringing it up in the weekly update.

Sounds good. I'm still not sure that this is a real bug.

@garrettmknight do you mind clarifying what you're trying to get at in this issue?

Also, this might be an internal issue, but I wanted to give external a shot before recruiting.

Please correct me if Im wrong, but, I think this behavior might be intentional, as I worked on a similar issue (#52025) weeks ago.

Gonna try to find where this is definitively written down before moving forwad.

https://expensify.slack.com/archives/C9YU7BX5M/p1734030390771639

https://expensify.slack.com/archives/C9YU7BX5M/p1734030390771639

I don't have access, @garrettmknight  any update for us? Thank you.

Still waiting for a response on the TestFlight that has documented this behavior.

Confirmed that we're going to go with the opposite of my suggested behavior.


Undefined is not an object (evaluating '_reactNativeMixpanel.Mixpanel.sharedInstanceWithToken')

I am getting this error with this code:
import { Mixpanel } from 'react-native-mixpanel';
...
Mixpanel.sharedInstanceWithToken(TOKEN);
Mixpanel.track("New order");

Any idea of how to solve it? Thank you so much! 🙂

Mixpanel.default.sharedInstanceWithToken(TOKEN);
All must be Mixpanel.default

please Fix this issue or update your Document @davodesign84

@syafiq90 it's working right now for me. Not sure how I fixed it. I restarted the project again.

hey guys, we are getting the same issue:
Mixpanel.sharedInstanceWithToken("APIxxxxxx")
Error: `TypeError: Cannot read property 'sharedInstanceWithToken' of undefined.
Versions:

react-native-mixpanel: 1.1.1
pod 'Mixpanel', '~> 3.3.3'
react-native: 0.55.3

When console logging Mixpanel the functions show up as expected:

Let me know if you need any more info!
Cheers

It looks like RNMixpanel is undefined in node_modules/react-native-mixpanel/index.js line 4:
const { RNMixpanel } = NativeModules

I forgot to link it in xcode 🤦♂:
Go to node_modules ➜ react-native-mixpanel and add RNMixpanel.xcodeproj
In XCode, in the project navigator, select your project. Add libRNMixpanel.a to your project's Build Phases ➜ Link Binary With Libraries

import Mixpanel from 'react-native-mixpanel' instead of var Mixpanel = require('react-native-mixpanel') did it for me.
The module now exports a default object and a MixpanelInstance object. Therefore, the above default import should be used or import {MixpanelInstance} from 'react-native-mixpanel' for the new (?) interface

you can use like this, i found in file index.js:
const mixpanel = new MixpanelInstance(TOKEN)
await mixpanel.initialize()
mixpanel.track('my event')

My issue was not in the Javascript, but in this:
https://github.com/davodesign84/react-native-mixpanel/issues/50#issuecomment-258065688

Try to import with braces like :
import Mixpanel from 'react-native-mixpanel';


Swaped profile isn't included in build

Describe the bug
The scene is saved with none of the profiles selected. After changing anything and Unity is reloaded we check what platform we are using and then set the correct profile for it. Now the problem is that setting MixedRealityToolkit.ActiveProfile to correct one, doesn't work. It does work in the editor but doesn't on Android or Hololens(UWP).
To reproduce
Steps to reproduce the behavior:

Open included a project
Build for Android or UWP
Start the app on a device
App doesn't set text because the profile is null (should also be visible with the attached debugger)

Expected behavior
A proper profile should be selected as in the editor.
Your setup (please complete the following information)

Unity Version: 2021.3.4f1
MRTK Version: 2.8.2

Target platform (please complete the following information)

Android
HoloLens 2

Additional context
Sample project included that indicates the problem.
mrtk-sample.zip

Hi @bacnar, I took a look at the project and found some issues: you are relying on editor-only APIs (AssetDatabase.LoadAssetAtPath etc.) to load the profile. And the script is put under an Editor assembly (Main.asmdef). Thus, the script does not execute in a built player. We have two suggested paths:

Make ProfileSwapper a MonoBehaviour and expose serialized fields for the profiles. If you assign the profiles there, they will be included in the build. Make sure you add the MonoBehaviour to your scene.
Use Resources.Load, but look out for the pitfalls mentioned in Unity's documentation.


Update aws-java-sdk-dynamodb to 1.12.705

About this PR
📦 Updates com.amazonaws:aws-java-sdk-dynamodb from 1.11.1034 to 1.12.705
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #566.


Maybe contact the local authorities instead.


Use environment appName instead of hardcoded Loop

The before and after view of one screen is shown in the graphic below.


Tweak dashboard inputbox

Use form-control and form-inline class (from bootstrap)
Use div tag and class to add margin in the bottom of log operation section.

Before:

After:

LGTM

thx~


CleanMyMac X reports potential threat for Downloader.app

CleanMyMac X keeps telling me that Downloader.app is a potential threat  and contains a backdoor (see screenshot). Does anybody why this happens?

That is strange. I just performed the online scan which scans the file using different antivirus software and all show "found nothing". Do CleanMyMac provide more details about this?

One reason might be "WebKit". As it is showing WebKit as trojan and "Downloader.app" also uses the WebKit to load the Apple Download page so that might be the reason.

I was a little worried about this, but VirusTotal says it’s clean so I think it’s fine.

Thanks, @JJTech0130.


fix(rootScope, ngRepeat): add support for objects created with Object.create(null) for ngRepeat and $watchCollection

Basically, the hasOwnProperty method was being called from an object gotten from the user. When that object was initially created with Object.create(null), it didn't inherit from Object so it didn't have the hasOwnProperty method throwing an "undefined is not a function" error.
This was fixed by executing hasOwnProperty.call(object, key) instead of object.hasOwnProperty(key)

I added some tests and landed this for 1.4.x.

I guess @HeberLZ never made it home :(

@ocombe, I think the man just fine according to his GitHub activity :relieved:

I'm really sorry about this, completely forgot about this pr because at the company i used to work at, we stopped using Object.create(null)


Chart not animating

I am having basic problem getting this to render. The circle is not animating to 55% nor 10% in addition. What am I missing?
jquery 1.7.2
jquery.easypiechart.min.js
style.css
any help would be appreciated, thanks!
http://jsfiddle.net/sloga/g8wkvy0o/

You should add data-percent to the element that you call it!
Fixed code : http://jsfiddle.net/g8wkvy0o/1/


[integration] Kyverno Policy management

Tool / Product Name
Kyverno
Goal
As a user, I want keptn to be able to populate the policy inside my CI/CD pipeline

#help-integrations on Slack

[X] Yes

No Existing Integrations

[X] Yes

Assisted
Yes
Any other info?
No response

Requisite Materials: https://www.cncf.io/blog/2022/09/14/protect-the-pipe-secure-ci-cd-pipelines-with-a-policy-based-approach-using-tekton-and-kyverno/
https://www.youtube.com/watch?v=zVkumUImIao

https://www.cncf.io/blog/2022/09/21/10-ways-to-make-your-software-pipeline-more-observable/
https://www.youtube.com/watch?v=gBJ169_il6k


Example parameters containing '[' or ']' are not parsed in example response

In reference to the JSON API spec, some query parameters will include [ and ] as described in https://jsonapi.org/format/#fetching-pagination
In the example below, the query parameters provided are equivilent to url:

/v0/campaigns?page[size]=2&page[number]=1&sort=-id and
/api/v0/campaigns?page%5Bsize%5D=2&page%5Bnumber%5D=1&sort=-id

I have verified the results from Postman output as expected (showing 2 results, sorted descending):

However, ApiDoc ignores the parameters with a square bracket in the when simulating a response.
Here's my doc block
    /**
     * List Campaigns
     *
     * !
     *
     * Returns a list of Campaigns
     *
     * @authenticated
     *
     * @queryParam sort                     [-]?(field_key) Example: -id
     * @queryParam page[size]               The number of results per page Example: 2
     * @queryParam page[number]             The current page Example: 1
     */

Here's my response:

✅ Sorted by id Desc
❗page[size]=2 doesn't parse (you can see more than 2 results)
❗page[number]=1 doesn't parse

I dug into this a bit more, and I was able to confirm the query parameters appear to be passed to the controller via printing out request()->getQueryString() in the response.
It's an issue with https://github.com/spatie/laravel-json-api-paginate. The pagination is done via a Builder::macro which doesn't parse when executed via the Console (running php artisan api:gen)

Lol, I have no idea what's going on here. I'm just relieved the issue is closed. 😅
Glad you located the source of the issue.


websocket upgrade via xDS grpc does not work

Title: websocket upgrade via xDS grpc does not work
Note that I filed the same bug to go-control-plane - apologies for the dupe.
Versions
Envoy version:
$ /usr/local/bin/envoy --version
/usr/local/bin/envoy  version: 55af249d4d1d7f6df9ead63186c513c47f826d05/1.12.2/clean-getenvoy-4bd7718-envoy/RELEASE/BoringSSL

go-control-plane version:
github.com/envoyproxy/go-control-plane v0.9.1
Operating system: Mac
Description:
upgrade_configs: websocket is not honored when provided via the xDS grpc API
When setting upgrade_configs statically, everything works as expected
- name: envoy.http_connection_manager
  typed_config:
    '@type': type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager
    upgrade_configs:
      - upgrade_type: websocket
    codec_type: AUTO
    stat_prefix: ingress_http

However the same information is provided via xDS grprc, a 403 response is returned when connecting to the websocket
manager := &hcm.HttpConnectionManager{
	StatPrefix: "ingress_http",
	UpgradeConfigs: []*hcm.HttpConnectionManager_UpgradeConfig{{
		UpgradeType: "websocket",
		Enabled:     &wrappers.BoolValue{Value: true},
	}},
	CodecType: hcm.HttpConnectionManager_AUTO,

Upon inspecting the config_dump via the admin console I see the following is missing when provided via xDS GRPC, but present when using the static config. This is likely the reason the websocket is not upgraded when the config is provided via xDS
 upgrade_configs:
      - upgrade_type: websocket

However, when using xDS over GRPC, that snippet is missing
Repro steps:
Create an ingress listener as follows:
func (l *Listeners) MakeIngressHTTPListener(listenerName string, port uint32, roleName string) (*v2.Listener, error) {
	//rdsSource := ConfigSource(Xds)

	alsConfig := &als.FileAccessLog{
		Path: "/tmp/access_log_ingress",
	}

	alsConfigPbst, err := ptypes.MarshalAny(alsConfig)
	if err != nil {
		return nil, err
	}

	// HTTP filter configuration
	manager := &hcm.HttpConnectionManager{
		StatPrefix: "ingress_http",
		UpgradeConfigs: []*hcm.HttpConnectionManager_UpgradeConfig{{
			UpgradeType: "websocket",
			Enabled:     &wrappers.BoolValue{Value: true},
		}},
		CodecType: hcm.HttpConnectionManager_AUTO,
		Http2ProtocolOptions: &core.Http2ProtocolOptions{
			AllowConnect: true,
		},
		RouteSpecifier: &hcm.HttpConnectionManager_RouteConfig{
			RouteConfig: &v2.RouteConfiguration{
				Name: "local_service",
				VirtualHosts: []*route.VirtualHost{{
					Name:    roleName,
					Domains: []string{"*"},
					Routes: []*route.Route{{
						Match: &route.RouteMatch{
							PathSpecifier: &route.RouteMatch_Prefix{
								Prefix: "/",
							},
						},
						Action: &route.Route_Route{
							Route: &route.RouteAction{
								UpgradeConfigs: []*route.RouteAction_UpgradeConfig{{
									UpgradeType: "websocket",
									Enabled:     &wrappers.BoolValue{Value: true},
								}},
								ClusterSpecifier: &route.RouteAction_Cluster{
									Cluster: roleName,
								},
							},
						},
					}},
				}},
			},
		},
		HttpFilters: []*hcm.HttpFilter{{
			Name: wellknown.Router,
		}},
		AccessLog: []*alf.AccessLog{{
			Name: wellknown.FileAccessLog,
			ConfigType: &alf.AccessLog_TypedConfig{
				TypedConfig: alsConfigPbst,
			},
		}},
	}

	pbst, err := ptypes.MarshalAny(manager)
	if err != nil {
		return nil, err
	}

	transportSocket, err := scauth.MakeDownstreamTransportSocketTLS()
	if err != nil {
		return nil, err
	}

	listener := &v2.Listener{
		Name: listenerName,
		Address: &core.Address{
			Address: &core.Address_SocketAddress{
				SocketAddress: &core.SocketAddress{
					Protocol: core.SocketAddress_TCP,
					Address:  Localhost,
					PortSpecifier: &core.SocketAddress_PortValue{
						PortValue: port,
					},
				},
			},
		},
		FilterChains: []*listener.FilterChain{{
			Filters: []*listener.Filter{{
				Name: wellknown.HTTPConnectionManager,
				ConfigType: &listener.Filter_TypedConfig{
					TypedConfig: pbst,
				},
			}},
			TransportSocket: transportSocket,
		}},
	}
	return listener, err
}

Inspect the config dump via the admin web console and observe the following is not present
 upgrade_configs:
      - upgrade_type: websocket

Try to connect to a websocket and a 403 is returned
λ wscat -n -c wss://localhost:443/api/v1/myws
error: Unexpected server response: 403
> %

Doing the same with a static config works
Logs:
[2020-01-09 21:44:52.487][10655444][debug][conn_handler] [external/envoy/source/server/connection_handler_impl.cc:335] [C1] new connection
[2020-01-09 21:44:52.487][10655444][debug][connection] [external/envoy/source/extensions/transport_sockets/tls/ssl_socket.cc:191] [C1] handshake expecting read
[2020-01-09 21:44:52.487][10655444][debug][connection] [external/envoy/source/extensions/transport_sockets/tls/ssl_socket.cc:191] [C1] handshake expecting read
[2020-01-09 21:44:52.487][10655444][debug][connection] [external/envoy/source/extensions/transport_sockets/tls/ssl_socket.cc:191] [C1] handshake expecting read
[2020-01-09 21:44:52.493][10655444][debug][connection] [external/envoy/source/extensions/transport_sockets/tls/ssl_socket.cc:191] [C1] handshake expecting read
[2020-01-09 21:44:52.493][10655444][debug][connection] [external/envoy/source/extensions/transport_sockets/tls/ssl_socket.cc:191] [C1] handshake expecting read
[2020-01-09 21:44:52.495][10655444][debug][connection] [external/envoy/source/extensions/transport_sockets/tls/ssl_socket.cc:176] [C1] handshake complete
[2020-01-09 21:44:52.496][10655444][debug][http] [external/envoy/source/common/http/conn_manager_impl.cc:259] [C1] new stream
[2020-01-09 21:44:52.496][10655444][debug][http] [external/envoy/source/common/http/conn_manager_impl.cc:708] [C1][S9233027417805348807] request headers complete (end_stream=false):
':authority', 'localhost'
':path', '/api/v1/myws'
':method', 'GET'
'sec-websocket-version', '13'
'sec-websocket-key', 'lyYRVxlVhHPFuM+eSvIBLQ=='
'connection', 'Upgrade'
'upgrade', 'websocket'
'sec-websocket-extensions', 'permessage-deflate; client_max_window_bits'
[2020-01-09 21:44:52.497][10655444][debug][http] [external/envoy/source/common/http/conn_manager_impl.cc:1354] [C1][S9233027417805348807] Sending local reply with details upgrade_failed
[2020-01-09 21:44:52.497][10655444][debug][http] [external/envoy/source/common/http/conn_manager_impl.cc:1552] [C1][S9233027417805348807] encoding headers via codec (end_stream=true):
':status', '403'
'date', 'Fri, 10 Jan 2020 02:44:52 GMT'
'server', 'envoy'
'connection', 'close'
[2020-01-09 21:44:52.497][10655444][debug][http] [external/envoy/source/common/http/conn_manager_impl.cc:200] [C1][S9233027417805348807] doEndStream() resetting stream
[2020-01-09 21:44:52.497][10655444][debug][http] [external/envoy/source/common/http/conn_manager_impl.cc:1791] [C1][S9233027417805348807] stream reset
[2020-01-09 21:44:52.497][10655444][debug][connection] [external/envoy/source/common/network/connection_impl.cc:104] [C1] closing data_to_write=116 type=2
[2020-01-09 21:44:52.497][10655444][debug][connection] [external/envoy/source/common/network/connection_impl.cc:660] [C1] setting delayed close timer with timeout 1000 ms
[2020-01-09 21:44:52.497][10655444][debug][connection] [external/envoy/source/common/network/connection_impl.cc:104] [C1] closing data_to_write=116 type=2
[2020-01-09 21:44:52.497][10655444][debug][connection] [external/envoy/source/common/network/connection_impl.cc:589] [C1] write flush complete
[2020-01-09 21:44:52.497][10655444][debug][connection] [external/envoy/source/common/network/connection_impl.cc:589] [C1] write flush complete
[2020-01-09 21:44:53.497][10655414][debug][main] [external/envoy/source/server/server.cc:175] flushing stats
[2020-01-09 21:44:53.497][10655444][debug][connection] [external/envoy/source/common/network/connection_impl.cc:649] [C1] triggered delayed close

this is fixed in github.com/envoyproxy/go-control-plane v0.9.1


[ALL-557] feat(frontend): Add save and discard actions to the editor

End-user friendly description of the problem this fixes or functionality that this introduces
Some browsers prioritize their CTRL+S functionality and prevent the shortcut save from working.

[ ] Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below

Give a summary of what the PR does, explaining any non-trivial design decisions
DISABLED

ENABLED

NOTICE THE FILE NAME SO THE SPACE DOES NOT FEEL EMPTY

NOTE: The previous CMD+S functionality is still preset. This just adds another way of saving AND introduces a way of discarding. This does NOT yet solve the case of conflicting content (user makes unsaved edits and server has new content)

Link of any specific issues this addresses

Going to merge main into this so I can test it.

Works well!


Recover schema axioms from ACSet type

The ACSet system converts finitely presented schemas into Julia types. However, it omits the equational axioms, which means that the presentation cannot be completely recovered from the type. This has been brought out by @slibkind's PR #433, which defines a Presentation constructor for ACSet types that cannot recover the axioms.
We should provide some mechanism to completely recover the schema from the ACSet type. We could probably do this by encoding the axioms as pairs of tuples in the type parameters.
I think this will become important as we incorporate equational reasoning about schemas, e.g., in a hypothetical improved algorithm for left pushforward data migration (#436). Consider that the schema for symmetric graphs is not just finitely presented, but finite—however, you can only know this if you have the axioms!

@olynch, this would naturally be a part of, or a sequel to, struct acsets, since making the type parameters more "hidden" will reduce the pain caused by even larger parametric types.


About KlovitClient

So if you see this issue, you may know what KlovitClient is.
So the owner is just a skid that stole some popular code from the know client called HolaClient and Heliactyl.
He is just a skid he steals code from some other GitHub user he does not give any credits, and he demands that is programming it them.
Here is some proof:
They stole HolaClient theme

Next he says he knows JS, but he does not even know how telemetry's work or how to add them!

Next he says he can, but he asks for the code for free

The next proof is about the documentations!
He says he wants to code them, but he just asks for the code!

The next proof is from my dms with him!
He says he got permission from holaclient to use that but as you see in my other proofs the owner does not give permission to him to use that!

Also, he may abuse some free providers like AWS or just abuse!,

Here is more proof of him being a skid!

Some good proof of him being a programmer!

Any proof of me abusing?

I have modified the thme 90% and I have given credits to CR072 and he agreed with me.

Any proof of me abusing?  I have modified the thme 90% and I have given credits to CR072 and he agreed with me.

I just uploaded every proof that you have no right to use it and that you are a skid

Any proof of me abusing?  I have modified the theme 90% and I have given credits to CR072 and he agreed with me.

Nope dude, I didn't give you permission to take that file. I just gave you that unfinished theme.

Any proof of me abusing?  I have modified the theme 90% and I have given credits to CR072 and he agreed with me.

Nope dude, I didn't give you permission to take that file. I just gave you that unfinished theme.

Please read what a license means here: https://github.com/HolaClient/HolaClient/blob/latest/LICENSE

Any proof of me abusing?  I have modified the theme 90% and I have given credits to CR072 and he agreed with me.

Nope dude, I didn't give you permission to take that file. I just gave you that unfinished theme.

Yes.

Just close this, every issue has been resolved.

Just close this, every issue has been resolved.

Ohh, so you want to hide the fact that you abuse and card and also skid?
Nahhh this stays open!

Just close this, every issue has been resolved.

Ohh, so you want to hide the fact that you abuse and card and also skid?
Nahhh this stays open!

I don't abuse and card tho. DE1 is from Dribble.fun and Paid-IN1 is from Cubix.host (Web-1 is locally hosted.)

Nothing is skidded yet.

Just close this, every issue has been resolved.

Ohh, so you want to hide the fact that you abuse and card and also skid?
Nahhh this stays open!

I don't abuse and card tho. DE1 is from Dribble.fun and Paid-IN1 is from Cubix.host (Web-1 is locally hosted.)

 For what you did, I'm surprised that I did not report you already

Just close this, every issue has been resolved.

Ohh, so you want to hide the fact that you abuse and card and also skid?
Nahhh this stays open!

I don't abuse and card tho. DE1 is from Dribble.fun and Paid-IN1 is from Cubix.host (Web-1 is locally hosted.)

Cubix.host is one of layers new acquired hosting. + they abuse aws if you look at their dns reccords

Cubix.host

Ye here is proof
https://search.censys.io/search?resource=hosts&sort=RELEVANCE&per_page=25&virtual_hosts=EXCLUDE&q=Cubix.host
https://securitytrails.com/domain/Cubix.host/dns

Just close this, every issue has been resolved.

Ohh, so you want to hide the fact that you abuse and card and also skid?
Nahhh this stays open!

I don't abuse and card tho. DE1 is from Dribble.fun and Paid-IN1 is from Cubix.host (Web-1 is locally hosted.)

Cubix.host is one of layers new acquired hosting. + they abuse aws if you look at their dns reccords

I don't really know tho, I paid with LTC and doge

Just close this, every issue has been resolved.

Ohh, so you want to hide the fact that you abuse and card and also skid?
Nahhh this stays open!

I don't abuse and card tho. DE1 is from Dribble.fun and Paid-IN1 is from Cubix.host (Web-1 is locally hosted.)

 For what you did, I'm surprised that I did not report you already

It's a nice thing that you didn't rename this and There is a CREDITS.md is KlovitClient's repo

Will you close this if I implement some things in KlovitClient by myself like MySQL Integration and stuff? (I did everything by myself but still I have to prove it.)

Will you close this if I implement some things in KlovitClient by myself like MySQL Integration and stuff? (I did everything by myself but still I have to prove it.)

It is not about that it is just about the things you have done but sure IL close this.

Thanks and uhm can yu tell me how do I make a user friendly docs?

Thanks and uhm can yu tell me how do I make a user friendly docs?

Use docusaurs


Remove the GRIST_ALLOWED_HOSTS environment variable

Context
While reviewing @fflorent 's #895 and discussing with various people at ANCT we realized that the GRIST_ALLOWED_HOSTS environment variable was added in a PR submitted in 2022 by another developer working at the time with ANCT : #287.
It turns out that the use case that originally motivated the PR (#271) is now covered in two ways:

since https://github.com/gristlabs/grist-core/commit/e590e65a3fe915ed95099c94c2e1852d56e4e33a, cross-origin requests that do not require authentication are allowed, so that public documents can be queried just fine from any external domain ;
allowing authenticated requests from external domains currently requires, in addition to including the domain in GRIST_ALLOWED_HOSTS, making an API key available in a client, which is definitely something one wants to discourage as pointed out by @dsagal in https://github.com/gristlabs/grist-core/issues/271#issuecomment-1241288590. Indeed we saw this mistake occur in the very web app that motivated the addition of GRIST_ALLOWED_HOSTS (the exposed API key has since been revoked).

We are now confident that we do not need this variable and have removed it from our deployment. Given the specificity of the use case it enables, and the lack of adequate documentation as evidenced by #895, it seems doubtful that any other Grist deployment would currently be depending on it, although it is of course difficult to be certain.
We also estimate that keeping it available in Grist has multiple downsides:

as mentioned above, pretty much the only scenario it enables is the unsafe one where an API key is accessible to a public Web client;
it adds unnecessary complexity to an already difficult-to-follow process of origin validation (GRIST_ALLOWED_HOSTS played a significant part in my bafflement while trying to implement origin checking for #859);
while I have no evidence for this, I suspect a confused Grist self-hoster may end up setting GRIST_ALLOWED_HOSTS to bypass an otherwise broken configuration of APP_HOME_URL and the other relevant variables (which are unfortunately numerous).

Proposed solution
This PR mostly reverts commit 49b1749e98c873c564c2463eb8eb3189d434eaca. A few notes on what was kept:

in allowHost, the logic introduced by #287 that allows a domain name that doesn't match the standard <orgname>.<basedomain>.<tld> pattern enforced by parseSubdomain to match itself was kept, although with simplified logic that does not involve lodash. This might not be necessary, since requests whose Host match their Origin are by definition not cross-origin, and would therefore not end up in allowHost, but was kept out of an abundance of caution.
the matchesBaseDomain function seemeed like an unrelated but useful addition of #287 (notably making the checks against ALLOWED_WEBHOOK_DOMAINS more robust), so it was kept as well.

Looks good to me too. One note is to remove GRIST_ALLOWED_HOSTS from test/server/lib/helpers/TestServer.ts, where it no longer plays a role.

Good catch, I had missed that one, it's removed now.


HAWQ-1120. Optimize exec time for check_sizes_valid function in hawqregister.

cc @ictmalili @linwen

+1

+1

Merged into master, thank.


not working in glide image lib.

I have used gilde lib for image but not set setImageSource programmatically.

Use Glide as:
Glide.with(context)
                .load(URL)
                .asBitmap()
                .into(new SimpleTarget<Bitmap>(SimpleTarget.SIZE_ORIGINAL, SimpleTarget.SIZE_ORIGINAL) {
                    @Override
                    public void onResourceReady(Bitmap bitmap, GlideAnimation anim) {
                        frissonView.setBitmap(bitmap);
                    }
                });

thank u nice work ......

Hello @IntruderShanky, the library is not working with Glide. The code that you have shared above is not working.


[#1526] Buttons activation

Fixes button behavior described in #1526
Also contains minor style changes

+1


Migration 1.x to 2.0.x fails on Windows : couldn't open sink

Windows 7 with powershell 7
Migrating from influxdb 1.7.6 to 2.0.6 using command .\influxd.exe upgrade
Working directory is "C:\influxdb"
-> An error occurs : couldn't open sink "C:\Users\MY_CURRENT_USER\upgrade.log": no sink found for scheme "c"
I googled and found that this may need some tweaking in the migration code to make the sink compatible with Windows : https://github.com/uber-go/zap/issues/621
Did someone manage to uprade under windows?

@PeggyFree I think I have a fix (absolute path on Windows worked for me with my changes), if you have a free minute would you mind checking too? You can download a build from my branch out of the CircleCI artifact repository: https://191768-13124802-gh.circle-artifacts.com/0/artifacts/influxdb2-client-nightly-windows-amd64.zip

@danxmoran thank you for your help. Unfortunately your nightly build didn't solve the problem. Same error message.
Your zip file only contains influx.exe , while I'm calling  ".\influxd.exe upgrade", maybe it is the cause?

@PeggyFree sorry about that, you're right I pasted the wrong link. Try this one: https://191768-13124802-gh.circle-artifacts.com/0/artifacts/influxdb2-nightly-windows-amd64.zip

Thank you for your patience @danxmoran  . The upgrade process now fails the step after :
←[36mPlease type your primary username←[0m: MyUser

←[36mPlease type your password←[0m:

←[36mPlease type your password again←[0m:

←[31mPasswords do not match.
←[0m←[36mPlease type your password←[0m:

The script asks for a user : ok
The script asks for a password : ok
The script asks for the password confirmation : unfortunately it immediatly writes "Passwords do not match." and it can loop forever like that.

Yes, that's #21441. Our escape sequences need some fixing up...
As a work-around, you can pass the password (and other parameters from that dialog) to influxd upgrade as CLI arguments. You'll also need to pass -f, because the confirmation prompt is broken too 🤦

I'm sorry to bother you again @danxmoran , It now stops one second later. All seems to be linked...
PS C:\influxdb> .\influxd.exe upgrade  --config-file influxdb.conf --username 'influx2' --password 'password' -f {"level":"info","ts":1622010453.9718282,"caller":"upgrade/upgrade.go:378","msg":"Starting InfluxDB 1.x upgrade"} {"level":"info","ts":1622010453.9728045,"caller":"upgrade/upgrade.go:381","msg":"Upgrading config file","file":"influxdb.conf"} {"level":"info","ts":1622010453.9737813,"caller":"upgrade/upgrade.go:385","msg":"Config file upgraded.","1.x config":"influxdb.conf","2.x config":"C:\\Users\\co \\.influxdbv2\\config.toml"} {"level":"info","ts":1622010453.974758,"caller":"upgrade/upgrade.go:395","msg":"Upgrade source paths","meta":"/influxdb/donnees/meta","data":"/influxdb/donnees/ data"} {"level":"info","ts":1622010453.9757342,"caller":"upgrade/upgrade.go:396","msg":"Upgrade target paths","bolt":"C:\\Users\\co\\.influxdbv2\\influxd.bolt","engine ":"C:\\Users\\co\\.influxdbv2\\engine"} {"level":"info","ts":1622010453.983547,"caller":"bolt/bbolt.go:84","msg":"Resources opened","service":"bolt","path":"C:\\Users\\co\\.influxdbv2\\influxd.bolt"} {"level":"info","ts":1622010453.9864767,"caller":"migration/migration.go:154","msg":"Bringing up metadata migrations","service":"migrations","migration_count":1 5} Error: onboarding error: onboard failed, missing value See 'influxd -h' for help
Looks like my parameters still need to be tuned to login for the first time on influxdbV2, I see this ticket :
https://github.com/influxdata/influxdb/issues/15761

Based on your example it looks like you're missing the --bucket and --org flags (and --retention if you want to set a retention policy on the auto-created bucket). You'd normally be asked to input those interactively when missing, but that step is skipped when you pass -f. An unfortunate side-effect of the work-around...
The error message you hit is very unhelpful, I'll open a separate issue to track improving it.


No option to choose HDD/SSD storage space during ubuntu installation[mainnet]

During the "chat flow" to create a ubuntu container I am never asked to pick how much storage I would like and it only gives 250Mb by default.
Which is not enough to even update the system properly and install like 1 package.

It's already exist
https://github.com/threefoldtech/jumpscaleX_threebot/blob/development/ThreeBotPackages/tfgrid_solutions/tfgrid_solutions/chatflows/ubuntu_deploy.py#L51
please update your code

It's already exist
https://github.com/threefoldtech/jumpscaleX_threebot/blob/development/ThreeBotPackages/tfgrid_solutions/tfgrid_solutions/chatflows/ubuntu_deploy.py#L51
please update your code

Not on mainnet using the latest 3sdk release.

@MathiasDeWeerdt it should be there. are you sure you don't need to update?

@MathiasDeWeerdt it should be there. are you sure you don't need to update?

I am currently using the latest release.

verfied


Draft: React 18 support

Hello @inlet , thanks for your amazing work! I've started working on updating react-pixi to support react 18. We're currently using react-pixi along with react-three-fiber (for webxr stuff) and we're experiencing performance problems. R3F (react-three-fiber) is riding the concurrent train for a while so we decided to give it a shot, but react-pixi (among other things though) is blocking us right now. It's only a draft but i got the first version working. The main painpoint is that docz is pretty much dead and i'm not sure picking it up to support react 18 worth the time. I'm currently looking into using storybook with mdx addon, so let's see how it goes. I'll keep you posted and feel free to comment
Fixes #337

[x] Update src/render/index.js to react 18
[x] Update src/stage/index.js to react 18
[x] Update all stories to storybook
[x] Fix prod storybook build
[ ] Fix netlify preview
[ ] Update docs to use new api
[ ] Update codepens
[x] Fix tests
[ ] Fix Suspense tests
[ ] Fix 'receives different events in different containers' test

Hi @saitonakamura,
Thanks this is amazing! Yeah Docz is a pain, I'm happy to ditch it for something else.
Maybe switch to docusaurus?
Thanks for collaborating on this. I'm currently pretty stacked with work for the coming two week.. when I got time I can absolutely help you with this PR.
Thanks and we'll be in touch
Patrick

@saitonakamura is there any update on this?

@spassvogel if you want to try this out, i have a package npm i<EMAIL_ADDRESS>If you use TS you can use paths feature, otherwise use webpack aliases or something like that to redirect @inlet/react-pixi to @saitonakamura/react-pixi
I do this in tsconfig.json
"paths": {
  "@inlet/react-pixi": ["../node_modules/@saitonakamura/react-pixi"],
}

The api has changed to
import { createRoot, Container } from '@inlet/react-pixi`

const canvas = document.createElement('canvas')
document.appendChild(canvas)

const root = createRoot(canvas, { width: 800, height: 600 })
root.render(<Container></Container>)

Now app is created under the hood (it's a subject to change, I'm not sure about it)

Hmm, I tried, but my project uses Create React App, and it gives the following error and removes the 'paths' section from tsconfig :(

The following changes are being made to your tsconfig.json file:

compilerOptions.paths must not be set (aliased imports are not supported)

Any chance this is coming to the official release soon? Beginning to run into dependency hell 😄

Hi,
I'm having issues while trying to execute npm i<EMAIL_ADDRESS>The full output is the following:
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving<EMAIL_ADDRESS>npm WARN Found<EMAIL_ADDRESS>npm WARN node_modules/prop-types
npm WARN<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN   node_modules/eslint-plugin-react
npm WARN<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN     node_modules/eslint-config-react-app
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN node_modules/@saitonakamura/react-pixi
npm WARN   @saitonakamura/react-pixi@"*" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving<EMAIL_ADDRESS>npm WARN Found: prop-types@undefined
npm WARN node_modules/prop-types
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN node_modules/@saitonakamura/react-pixi
npm WARN   @saitonakamura/react-pixi@"*" from the root project
npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

In fact, when I inspect the package archive, the package.json contains this:
  "peerDependencies": {
    "pixi.js": "^6.0.0",
    "prop-types": "^18.0.0",
    "react": "^18.0.0",
    "react-dom": "^18.0.1"
  },

But the prop-types package doesn't have a 18.0.0 version.
I'm not very familiar with package dependencies so maybe there's something I get wrong, but I wonder why nobody reported this issue. Is it related to the Windows environment? Or did I miss something during the installation process?
Also, I'm using CRA with the typescript template.
Thank you for any hint

I'm using @saitonakamura/react-pixi. it works well. waiting for a official release

Hi,
I'm having issues while trying to execute npm i<EMAIL_ADDRESS>The full output is the following:
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving<EMAIL_ADDRESS>npm WARN Found<EMAIL_ADDRESS>npm WARN node_modules/prop-types
npm WARN<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN   node_modules/eslint-plugin-react
npm WARN<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN     node_modules/eslint-config-react-app
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN node_modules/@saitonakamura/react-pixi
npm WARN   @saitonakamura/react-pixi@"*" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving<EMAIL_ADDRESS>npm WARN Found: prop-types@undefined
npm WARN node_modules/prop-types
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN node_modules/@saitonakamura/react-pixi
npm WARN   @saitonakamura/react-pixi@"*" from the root project
npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

In fact, when I inspect the package archive, the package.json contains this:
  "peerDependencies": {
    "pixi.js": "^6.0.0",
    "prop-types": "^18.0.0",
    "react": "^18.0.0",
    "react-dom": "^18.0.1"
  },

But the prop-types package doesn't have a 18.0.0 version. I'm not very familiar with package dependencies so maybe there's something I get wrong, but I wonder why nobody reported this issue. Is it related to the Windows environment? Or did I miss something during the installation process? Also, I'm using CRA with the typescript template.
Thank you for any hint

I have the same issue.
@inlet @saitonakamura Did you have a chance to finish your job with upgrading React to 18?
Or @saitonakamura Could you change  "prop-types": "^18.0.0", to the correct version 15.8.1?

@dmytro-podolianskyi-ew I don't have prop-types dependency and looks like it works. you can try to remove that entry

I'm having issues while trying to execute npm i<EMAIL_ADDRESS>
I tried using yarn instead of npm, and it seems to work now.
Having to change package managers is quite annoying though...

Sure will do next week. Sorry for not devoting time to it, got mixed up with other stuff

Hey, is there an eta on the release? I just want to know if I should wait a day or two for this or just install now and upgrade later. Thanks so much.

We’re working on this in our spare time 😁 no eta yet for the release so yes install and upgrade when it’s available is probably a good idea!

Hey @saitonakamura, i would like to help here, I just need some context to understand how to help.
Maybe a markdown file, with listed tasks we need to addres?

Thank you so much for working on this, it will be a game-changer for my project!

Hey @saitonakamura , just sent a PR to your repo, https://github.com/wisebits-tech/react-pixi/pull/1
That's not much yet, but im gonna open others pr's along the week, if you see any issues just comment in the PR plx

Great to see you guys are collab on this, let me know when I can review a PR

I've published<EMAIL_ADDRESS>the createRoot api (which were changed initially) returned back to previous design with app.stage as a root container
import { createRoot, Text } from '@inlet/react-pixi';
import { Application } from 'pixi.js';

const app = new Application({
  width: 800,
  height: 600,
  backgroundColor: 0x10bb99,
  view: document.getElementById('my-canvas'),
});

const root = createRoot(app.stage);
root.render(<Text text="Hello World" x={200} y={200} />);

You check out the basic example with createRoot at https://codesandbox.io/s/j112mb?file=/src/index.jsx
<Stage> component should work as before
cc @spassvogel @Bevebage @hevans90 @pluveto
I also update prop-types version to a proper one, cc @pluveto @MonsieurNaexec

@saitonakamura is it stable enough to have this PR merged? Thanks!

@inlet Nah, a lot of tests still failing. But if you can release to npm under next tag or something like that it would certainly be great for the folk out there. Because it's stable enough so the examples and stories works

@saitonakamura, next PR i gonna try to start fixing tests so we can ensure a better version!
I think today i can make some PR's improving tests

We're slowly getting there guys

Wait will this new version still with for older react versions?

@Specy no, this one only for react 18
But this consists of nothing new but support for react 18. If you use older versions you can just use<EMAIL_ADDRESS>Eventually we will stumble upon problems when we'll do fixes or new features/ cause we'll need to backport them to the other version . But let the future us worry about it

Only 4 more test suits to go!

I'm using<EMAIL_ADDRESS>and I spotted an edge-case bug:
On iOS Safari (tested on iOS 15.6 and iPadOS 15.6) React 18's new double effect firing in [StrictMode](https://reactjs.org/docs/strict-mode.html) causes the Application to be created twice in quick succession. This causes the GL context Pixi uses to be created twice, as well. In turn, this causes the Pixi app to throw with the error: Invalid value of 0passed tocheckMaxIfStatementsInShader`.
I temporarily fixed this by disabling strict mode. However, it seems like one would want to reuse Pixi Applications across subsequent renders like this.
To reproduce: run this branch with React 18 and [StrictMode](https://reactjs.org/docs/strict-mode.html] enabled.

@mutewinter are you running your app with dev react build and strict mode? Also, do you use <Stage> or createRoot api?

@mutewinter can you do a codesandbox of something like that illustrating that issue?

Hey folks, providing an update on this.
I fixed the majority of the tests, only three tests were skipped

Good news are, 99% of the tests fixes were done in the tests bodies themselves
So I released the<EMAIL_ADDRESS>I'll continue migrating with the stories and updating the docs in the meantime
@inlet if you have time, I'd like to take a look at the skipped tests (marked in the starting message and provided with TODO explanations in the code), maybe you'll have some ideas

@mutewinter are you running your app with dev react build and strict mode? Also, do you use <Stage> or createRoot api?

Dev React build via Next.js which is using createRoot.

@mutewinter can you do a codesandbox of something like that illustrating that issue?

Here's the sandbox: https://codesandbox.io/s/react-pixi-18-and-strictmode-fails-on-ios-fg44ky?file=/src/index.jsx
Visit https://fg44ky.csb.app/ on iOS and you'll get the error: Invalid value of 0 passed to checkMaxIfStatementsInShader

@mutewinter , I found out that it's reproducible by simply creating and destroying 2 pixi apps using the same canvas, see https://codesandbox.io/s/gracious-water-nmiswl?file=/src/index.js, https://nmiswl.csb.app/. Maybe someone knows how to workaround it?

Hey! Thanks for the awesome work here. I'm trying to use<EMAIL_ADDRESS>in a TypeScript project and I get this error:
Module '"@saitonakamura/react-pixi"' has no exported member 'createRoot'.

Is the type declarations incorrect/out-of-date?

@joukosaastamoinen yeah, I've yet to update the d.ts, thanks for the report

https://github.com/wisebits-tech/react-pixi/blob/284e34390e744457cb0e6fd49c2be210b6928b76/src/render/index.jsx#L68
This warning appears to have the conditional inverted.

Released<EMAIL_ADDRESS>Only 2 fixes were made in the lib code: d.ts fix and fix of wrong warning
Other commits were related to tests, stories and stories deployment
cc @mutewinter @joukosaastamoinen

@inlet can you help me with the netlify? deploy looks to be successful, but when storybook is trying to load the assets it fails with 404. I check the storybook build locally and it's fine

A new small issue with this branch vs main: window is accessed here: https://github.com/wisebits-tech/react-pixi/blob/39e23a3dfa09ff032723815ca73a304708423d90/src/reconciler/hostconfig.js#L101, which causes rendering in Node to fail without a polyfill. Previously, one could get away without a polyfill of window by providing resolution and autoDensity: false. This code is commented in such a way that it doesn't appear done, so this may be on the todo list.

@mutewinter awesome that you've found it, I love how y'all helping with the testing!
Implementation of getEventPriority is just copied from the react-dom counterpart, TODO is left to think if we can do better. But you're indeed right that it should not fail the node so I'm gonna insert a check beforehand for now

@inlet can you help me with the netlify? deploy looks to be successful, but when storybook is trying to load the assets it fails with 404. I check the storybook build locally and it's fine

I’m currently on holiday but will help when I’m back, thanks 🙏

@mutewinter awesome that you've found it, I love how y'all helping with the testing!
Implementation of getEventPriority is just copied from the react-dom counterpart, TODO is left to think if we can do better. But you're indeed right that it should not fail the node so I'm gonna insert a check beforehand for now

Here's a patch that fixes the crash when rendering in Node:
index 7cbff42..700f3b7 100644
--- a/src/reconciler/hostconfig.js
+++ b/src/reconciler/hostconfig.js
@@ -98,6 +98,10 @@ function diffProperties(pixiElement, type, lastProps, nextProps, rootContainerEl
 }

 export function getEventPriority() {
+  // Escape hatch for Node renderer where we don't a Window.
+  if (typeof window === 'undefined') {
+    return DefaultEventPriority
+  }
   let name = window?.event?.type
   switch (name) {
     case 'click':

@mutewinter published a 5th with your fix

Hi guys. My project fundamentally relies on react-pixi. Looking to update to react 18 but see this is still WIP.
What is still required in order to get this over the line for release?
Thanks

Once finished I'll be glad to merge the PR!

Been using this branch in production for weeks and it has been solid for me.

I would like to use this package for an internal project at work, but I need support for React 18. What are the remaining todos for this PR?

@alvinalexander you can try using @saitonakamura 's fork that has experimental (but pretty stable) react 18 support here:
https://www.npmjs.com/package/@saitonakamura/react-pixi?activeTab=versions

@saitonakamura thanks for your awesome work on this! I'm going to be getting an official release working with React 18 as soon as possible.
We're still deciding how to handle docs and examples along with a general revamp across the whole PIXI ecosystem - it will likely be a combination of docusaurus and storybook. In the short term getting React 18 support working is the top priority and it appears that is generally a small part of this PR (mainly related to createRoot changes) compared with docs changes?

I've opened a minimal PR just to get the library working with React 18 before we do a docs overhaul in the near future.
https://github.com/pixijs/pixi-react/pull/358
@saitonakamura I think you've been doing a bigger overhaul including docs that may have extended beyond this original draft PR - it might be useful to sync to discuss?

React 18 is now supported, including a matching createRoot API as of v7.0.0 available at @pixi/react


[UWP] Helper implementations should be provided to parse and implement base element properties

Platform
What platform is your issue or question related to? (Delete other platforms).

UWP

Issue
Today to implement a custom element, parsing of all properties is required. We should provide a base implementation to handle parsing properties that are common to all elements.

@RebeccaAnne is this something that can be community-sourced?


Custom Theme/s Option

Is your feature request related to a problem? Please describe.
#7616 - I briefly asked why there isn't just an option for custom themes/css but was told a suggestion is better in suggestions rather than an issue
Describe the solution you'd like
Some ability to provide css files as themes in a folder to then show up as dedicated themes, or just a custom css per user option perhaps?
Just either an option for the server to serve new themes or for the user to provide custom css OR both.
Describe alternatives you've considered
Client side extensions to inject css, but after the recent "dark mode" issue I imagine people might enjoy the option of a custom option
Additional context
if you don't have anything nice to say, don't say anything at all

Thanks for opening this as a separate request. The UI update in 2.15.0 is the first step of a larger UI rework so by no means is the final version, and we're keen to gather feedback on it and other changes we could potentially make.


[Enhancement] Finish README and Fluent Site Revamp

Finish Fluent Design site revamp and finish banners for readme to increase user attentiveness.

#201

all done :) https://applemusicelectron.com/

README Update still needed.


updated the latest mkldnn

This commit will pull the latest changes from the mkl-dnn tree.
the mirror.bazel.build URL doesn't exist: "https://mirror.bazel.build/github.com/01org/mkl-dnn/archive/e0bfcaa7fcb2b1e1558f5f0676933c1db807a729.tar.gz" can you create it?

This commit will pull the latest changes from the mkl-dnn tree.


FIX: Use correct image for contour plotting

Should resolve various plotting issues.

Codecov Report
Patch coverage: 40.00% and project coverage change: -0.02 :warning:

Comparison is base (647c895) 63.38% compared to head (8cae58c) 63.36%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@               Coverage Diff               @@
##           maint/1.7.x     #785      +/-   ##
===============================================
- Coverage        63.38%   63.36%   -0.02%
===============================================
  Files               49       49
  Lines             5962     5965       +3
  Branches          1170     1170
===============================================
+ Hits              3779     3780       +1
- Misses            2001     2003       +2
  Partials           182      182

Flag
Coverage Δ

reportlettests
∅ <ø> (∅)

unittests
50.62% <0.00%> (-0.03%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

niworkflows/viz/utils.py
77.43% <40.00%> (-0.38%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Bug : Title of embedded note not displayed

If I embed a note with ![[my note]], the title isn't displayed, only the content of the note.
Is there a way to display it ?

A question in context please?
This embed formatting does not seem to work in Obsidian client 🤔

And using this style would conflict with this theme based way of controlling embed rendering
https://github.com/orgs/ObsidianPublisher/discussions/190#discussion-5502204
There is a clear need to canonicalize the rendering of embeds at both client and publish time, ideally across plugins/themes.
cc @ebullient @AnubisNekhet

Different strokes for different folks, sadly.
I almost never want the header I embedded to come along for the ride, but others do. It's something I allow to be changed with style settings (Hide the embedded heading), but I don't know how the style settings plugin interacts with publish...


Remove compileElements and projectInternalView API

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

I've triggered a build for you.


Console logs are coming after upgrading to version 1.5.1

I'm getting following logs after upgrading to version 1.5.1:

My configuration for localforage is as below:
import localforage from "localforage";
localforage.config({
  version: 1.0,
  description: "Personal DB"
});
const instance1 = localforage.createInstance({
  name: "db-instance1",
  storeName: "instance1"
});
const instance2 = localforage.createInstance({
  name: "db-instance2",
  storeName: "instance2"
});
const instance3 = localforage.createInstance({
  name: "db-instance3",
  storeName: "instance3"
});

Ah, interesting, are you defining any custom drivers? If not it seems we have a bug and shouldn't be logging here.

@tofumatt No, I'm not using any custom driver. In my previous comment, I logged the config that I'm using.

@kakadiadarpan can you test #751. If you can confirm that it work I will try to release is today or early tomorrow.

@thgreasi Sure, I'll do that.

@thgreasi Yes, #751 fixes this issue. Thanks!

Released a fix as 1.5.2 , thanks for the detailed report!
Happy instance creation!

Wow! That was fast. :clap:


cainjector is watching secrets in all the cluster even after setting --namespace flag

Describe the bug:
I've deployed cert-manager using helm chart in an AWS EKS cluster where I have +1000 namespaces and very high number of secrets (+15k). The problem is cainjector goes into a crashloopbackoff unless I set a very high (compared to other addons) amount of resources to it (2Gi ram/300m cpu).
According to the logs the reason seems to be that cainjector is trying to list and watch every single secret on the cluster and therefore it gets OOMKilled or the api simply times out when it queries for all the secrets. I'm already trying to lower the amount of secrets but when we keep scailing and deploying more apps/namespaces this will become a problem anyway.
I also tried setting the --namespace argument to both the controller and cainjector to track only one namespace that I care about, but I wonder why is cainjector still trying to query all secrets from the cluster. Furthermore, is there another option to limit this behaviour? I paste below my relevant helm values and cainjector logs.
# CAINJECTOR LOGS
I0707 14:56:46.351900       1 request.go:1079] Stream error http2.StreamError{StreamID:0x93, Code:0x2, Cause:error(nil)} when reading response body, may be caused by closed connection.
W0707 14:56:46.352186       1 reflector.go:324] k8s.io/client-go@v0.23.4/tools/cache/reflector.go:167: failed to list *v1.Secret: stream error when reading response body, may be caused by closed connection. Please retry. Original error: stream error: stream ID 147; INTERNAL_ERROR
I0707 14:56:46.352277       1 trace.go:205] Trace[145623991]: "Reflector ListAndWatch" name:k8s.io/client-go@v0.23.4/tools/cache/reflector.go:167 (07-Jul-2022 14:55:43.650) (total time: 62701ms):
Trace[145623991]: ---"Objects listed" error:stream error when reading response body, may be caused by closed connection. Please retry. Original error: stream error: stream ID 147; INTERNAL_ERROR 62701ms (14:56:46.352)
Trace[145623991]: [1m2.701863002s] [1m2.701863002s] END
E0707 14:56:46.352309       1 reflector.go:138] k8s.io/client-go@v0.23.4/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list *v1.Secret: stream error when reading response body, may be caused by closed connection. Please retry. Original error: stream error: stream ID 147; INTERNAL_ERROR
I0707 14:56:46.551650       1 request.go:1079] Stream error http2.StreamError{StreamID:0x97, Code:0x2, Cause:error(nil)} when reading response body, may be caused by closed connection.
W0707 14:56:46.551846       1 reflector.go:324] k8s.io/client-go@v0.23.4/tools/cache/reflector.go:167: failed to list *v1.Secret: stream error when reading response body, may be caused by closed connection. Please retry. Original error: stream error: stream ID 151; INTERNAL_ERROR
I0707 14:56:46.552312       1 trace.go:205] Trace[232330914]: "Reflector ListAndWatch" name:k8s.io/client-go@v0.23.4/tools/cache/reflector.go:167 (07-Jul-2022 14:55:43.681) (total time: 62870ms):
Trace[232330914]: ---"Objects listed" error:stream error when reading response body, may be caused by closed connection. Please retry. Original error: stream error: stream ID 151; INTERNAL_ERROR 62870ms (14:56:46.551)
Trace[232330914]: [1m2.870686471s] [1m2.870686471s] END
E0707 14:56:46.552349       1 reflector.go:138] k8s.io/client-go@v0.23.4/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list *v1.Secret: stream error when reading response body, may be caused by closed connection. Please retry. Original error: stream error: stream ID 151; INTERNAL_ERROR
E0707 14:57:43.650257       1 controller.go:203] cert-manager/certificate/customresourcedefinition/controller/controller-for-certificate-customresourcedefinition "msg"="Could not wait for Cache to sync" "error"="failed to wait for controller-for-certificate-customresourcedefinition caches to sync: timed out waiting for cache to be synced"
I0707 14:57:43.650315       1 shared_informer.go:266] stop requested
I0707 14:57:43.650373       1 trace.go:205] Trace[2040038594]: "Reflector ListAndWatch" name:k8s.io/client-go@v0.23.4/tools/cache/reflector.go:167 (07-Jul-2022 14:56:47.509) (total time: 56141ms):
Trace[2040038594]: [56.141318854s] [56.141318854s] END
I0707 14:57:43.650449       1 shared_informer.go:266] stop requested
E0707 14:57:43.650491       1 controller.go:203] cert-manager/certificate/apiservice/controller/controller-for-certificate-apiservice "msg"="Could not wait for Cache to sync" "error"="failed to wait for controller-for-certificate-apiservice caches to sync: timed out waiting for cache to be synced"
I0707 14:57:43.650498       1 shared_informer.go:266] stop requested
E0707 14:57:43.650540       1 controller.go:203] cert-manager/certificate/validatingwebhookconfiguration/controller/controller-for-certificate-validatingwebhookconfiguration "msg"="Could not wait for Cache to sync" "error"="failed to wait for controller-for-certificate-validatingwebhookconfiguration caches to sync: timed out waiting for cache to be synced"
I0707 14:57:43.650547       1 shared_informer.go:266] stop requested
E0707 14:57:43.650561       1 controller.go:203] cert-manager/certificate/mutatingwebhookconfiguration/controller/controller-for-certificate-mutatingwebhookconfiguration "msg"="Could not wait for Cache to sync" "error"="failed to wait for controller-for-certificate-mutatingwebhookconfiguration caches to sync: timed out waiting for cache to be synced"
E0707 14:57:43.650577       1 start.go:222] cert-manager/ca-injector "msg"="Error registering certificate based controllers. Retrying after 5 seconds." "error"="failed to wait for controller-for-certificate-customresourcedefinition caches to sync: timed out waiting for cache to be synced"
I0707 14:57:43.650586       1 shared_informer.go:266] stop requested
E0707 14:57:43.755676       1 controller.go:203] cert-manager/secret/customresourcedefinition/controller/controller-for-secret-customresourcedefinition "msg"="Could not wait for Cache to sync" "error"="failed to wait for controller-for-secret-customresourcedefinition caches to sync: timed out waiting for cache to be synced"
I0707 14:57:43.860441       1 shared_informer.go:266] stop requested
E0707 14:57:43.757338       1 controller.go:203] cert-manager/secret/mutatingwebhookconfiguration/controller/controller-for-secret-mutatingwebhookconfiguration "msg"="Could not wait for Cache to sync" "error"="failed to wait for controller-for-secret-mutatingwebhookconfiguration caches to sync: timed out waiting for cache to be synced"
I0707 14:57:43.757349       1 shared_informer.go:266] stop requested
E0707 14:57:43.757375       1 controller.go:203] cert-manager/secret/validatingwebhookconfiguration/controller/controller-for-secret-validatingwebhookconfiguration "msg"="Could not wait for Cache to sync" "error"="failed to wait for controller-for-secret-validatingwebhookconfiguration caches to sync: timed out waiting for cache to be synced"
I0707 14:57:43.757381       1 shared_informer.go:266] stop requested
E0707 14:57:43.757403       1 controller.go:203] cert-manager/secret/apiservice/controller/controller-for-secret-apiservice "msg"="Could not wait for Cache to sync" "error"="failed to wait for controller-for-secret-apiservice caches to sync: timed out waiting for cache to be synced"
I0707 14:57:43.757410       1 shared_informer.go:266] stop requested
I0707 14:57:43.862973       1 trace.go:205] Trace[456837381]: "Reflector ListAndWatch" name:k8s.io/client-go@v0.23.4/tools/cache/reflector.go:167 (07-Jul-2022 14:56:47.541) (total time: 56321ms):
Trace[456837381]: [56.321724952s] [56.321724952s] END
I0707 14:57:43.863420       1 logr.go:249] cert-manager "msg"="Stopping and waiting for non leader election runnables"
I0707 14:57:43.863474       1 logr.go:249] cert-manager "msg"="Stopping and waiting for leader election runnables"
I0707 14:57:43.863546       1 logr.go:249] cert-manager "msg"="Stopping and waiting for caches"
I0707 14:57:43.863636       1 shared_informer.go:266] stop requested
I0707 14:57:43.868198       1 logr.go:249] cert-manager "msg"="Stopping and waiting for webhooks"
I0707 14:57:43.868280       1 logr.go:249] cert-manager "msg"="Wait completed, proceeding to shutdown the manager"
E0707 14:57:44.062626       1 start.go:192] cert-manager/ca-injector "msg"="manager goroutine exited" "error"=null
Error: error registering secret controller: failed to wait for controller-for-secret-customresourcedefinition caches to sync: timed out waiting for cache to be synced
Usage:
  ca-injector [flags]
.
.
.

Expected behaviour:
I would expect cainjector should watch secrets in just one namespace when --namespace flag is set, but to be honest I don't know if there is any reason it should look elsewhere.
Steps to reproduce the bug:
I have 4 clusters in different regions with the following amount of secrets, the more amount of secrets the bigger amount of ram cainjector consumes.
            secrets
cluster1    2215
cluster2    4846
cluster3    6008
cluster4    15112

Install cert-manager using helm chart and the following values
# VALUES
cainjector:
  extraArgs:
  - --namespace=mynamespace
  resources:
    limits:
      cpu: 50m
      memory: 100Mi
    requests:
      cpu: 50m
      memory: 100Mi
extraArgs:
- --namespace=mynamespace
- --issuer-ambient-credentials
installCRDs: true
securityContext:
  enabled: true
  fsGroup: 1001
serviceAccount:
  annotations:
    eks.amazonaws.com/role-arn: arn:aws:iam::1234567890:role/cert-manager
resources:
    limits:
      cpu: 50m
      memory: 100Mi
    requests:
      cpu: 50m
      memory: 100Mi

Environment details::

Kubernetes version: v1.21.12-eks
Cloud-provider/provisioner: AWS EKS t4g.large instance type
cert-manager version: v1.8.2
Install method: helm chart

/kind bug

Related #5220

@SpectralHiss and I have come across an OpenShift cluster with around 1660 Secret resources and cert-manager 1.9.1. The cainjector kept being OOMKilled.
We noticed that although the Helm chart doesn't set resources.limits on the cainjector pod, the resources block had still been filled after installing it in the cluster. It is probably OpenShift that sets this default memory limit.
For context, after installing cert-manager with the Helm chart, the resources block looked like this:
resources:
  limits:
    memory: 128Mi
    cpu: 100m

After increasing the memory limit to 256MB, the cainjector started working again.
I think we ought to warn people with regards to memory requirements for cainjector.


replacement of es5 functions to es6 class def feat.P5.FFT

area covered
src/fft.js

Looks to be off to a good start! Just a small comment

@therewasaguy @kyle1james require your review !

Yes that is for later prs 😇


App crashing on Transfer fund to vault UAI

https://github.com/bithyve/bitcoin-keeper/assets/62699947/68fcbcbb-df70-4e10-982c-28aacfc796a6

App is crashing when we click on "Continue" button of Transfer fund UAI.

Verified this issue on keeper app v 1.1.11(293)


v4.1.3 introduces a bug related to @actions/artifact

The newest version has a bug which breaks my CI.

Same for me.

On it! 🩴

@beeb / @sburton84, please confirm if #196 resolves the bug? I believe you can point your workflow this way:
uses: zgosalvez/github-actions-report-lcov@hotfix/artifacts2

@zgosalvez see below

@beeb, kindly confirm again. I believe I've found the rest of the problems.

@zgosalvez all good with the latest fix!

Thanks! v4.1.4 is now out 🚢


Is there a way to process multiple unrelated plasmids automatically with mob-typer in the program?

Could you provide more details? Do you mean multiple fasta inputs?

I have one fasta file with multiple unrelated plasmid sequences and want to
do fasta-typer on them individually. Since typer is said to only allow
fasta file  that only has one plasmid, is there a way to do analysis on
them automatically one-by-one?
On Sat, Dec 21, 2019 at 9:05 AM Kirill Bessonov<EMAIL_ADDRESS>wrote:

Could you provide more details? Do you mean multiple fasta inputs?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/phac-nml/mob-suite/issues/44?email_source=notifications&email_token=AMR7GZ2YYANMN2YVBFZ7FV3QZZEFVA5CNFSM4J6EUOO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHO7YXA#issuecomment-568196188,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMR7GZ33QDF5MICSHIHRMHDQZZEFVANCNFSM4J6EUOOQ
.

--
Han Zhang
Class of 2022
University of California, Berkeley
<EMAIL_ADDRESS>

You can run mob_recon on this multi-sequence fasta file. You should get the same number of plasmids and get mob_typer aggregate report per each plasmid entry.
Alternatively we can implement multi-plasmid typing in mob_typer assuming each entry in the file represent a single plasmid

Sorry, could you  specify how I can implement multi-plasmid typing in
mob-typer?
ᐧ
On Sat, Dec 21, 2019 at 9:58 AM Kirill Bessonov<EMAIL_ADDRESS>wrote:

You can run mob_recon on this multi-sequence fasta file. You should get
the same number of plasmids and get mob_typer aggregate report per each
plasmid entry.
Alternatively we can implement multi-plasmid typing in mob_typer assuming
each entry in the file represent a single plasmid
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/phac-nml/mob-suite/issues/44?email_source=notifications&email_token=AMR7GZ7HT2N5HOJL5NASYNTQZZKMTA5CNFSM4J6EUOO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHPAVKA#issuecomment-568199848,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMR7GZ3WZUUAXKOP3A5SOQDQZZKMTANCNFSM4J6EUOOQ
.

--
Han Zhang
Class of 2022
University of California, Berkeley
<EMAIL_ADDRESS>

Multi-plamsid typing would require quite extensive modification of the mob_typer E.g. getRepliconContigs()  and other results reporting functions. It is much more easier to split multi-fasta file into separate files. We will consider this feature in future releases.

Alternatively run mob_recon -i multifasta.fa --run_typer -o outputfolder on multi-fasta file that should reconstruct all plasmid and type them automatically without any need of splitting them individually.

It seems a lot of error for little gain especially in cases when a given plasmid is split into several contigs (draft assembly) instead of a single contig (complete assembly).

@kbessonov1984  suggestion will largely do what you want but if you have multiple plasmids that are quite similar, this approach won't work. Assuming that your fasta file is a set of complete plasmids, the easiest way to run the analysis that you want is to split your multi-sequence fasta file into individual files with one sequence per file. This is easily done through any number of method but if you want a quick python script to do that you can use the python 3 code below. Once you have single fasta files you can then run mob-typer individually on each one easily:
`
from Bio import SeqIO
import pandas as pd
from argparse import (ArgumentParser, FileType)
import os
def parse_args():
"Parse the input arguments, use '-h' for help"
parser = ArgumentParser(
description="Split multi-fasta to individual files")
parser.add_argument('-o', '--outdir', type=str, required=True, help='Output directory')
parser.add_argument('-i', '--in_fasta', type=str, required=True, help='Input assembly fasta file to process')
return parser.parse_args()

def main():
args = parse_args()
outdir = args.outdir
with open(args.in_fasta, "r") as handle:

    for record in SeqIO.parse(handle, "fasta"):
        id = record.id
        seq = record.seq
        outfile = os.path.join(outdir,"{}.fasta".format(id))
        out_fasta = open(outfile,'w')
        out_fasta.write(">{}\n{}\n".format(record.id,record.seq))
        out_fasta.close()

call main function
if name == 'main':
main()
`

Multi-plamsid typing would require quite extensive modification of the mob_typer E.g. getRepliconContigs()  and other results reporting functions. It is much more easier to split multi-fasta file into separate files. We will consider this feature in future releases.
Alternatively run mob_recon -i multifasta.fa --run_typer -o outputfolder on multi-fasta file that should reconstruct all plasmid and type them automatically without any need of splitting them individually.

It seems a lot of error for little gain especially in cases when a given plasmid is split into several contigs (draft assembly) instead of a single contig (complete assembly).

Thanks for your answer. The reason I did not split fasta files into separate ones is that we have too many sequences and it's impossible to run them individually manually. For mob-recon --run_typer, the results generated do not contain the typing results for some reason. Could you check if the --run_typer function is working ?

@kbessonov1984 suggestion will largely do what you want but if you have multiple plasmids that are quite similar, this approach won't work. Assuming that your fasta file is a set of complete plasmids, the easiest way to run the analysis that you want is to split your multi-sequence fasta file into individual files with one sequence per file. This is easily done through any number of method but if you want a quick python script to do that you can use the python 3 code below. Once you have single fasta files you can then run mob-typer individually on each one easily
import pandas as pd
from argparse import (ArgumentParser, FileType)
import os

def parse_args():
    "Parse the input arguments, use '-h' for help"
    parser = ArgumentParser(
        description="Split multi-fasta to individual files")
    parser.add_argument('-o', '--outdir', type=str, required=True, help='Output directory')
    parser.add_argument('-i', '--in_fasta', type=str, required=True, help='Input assembly fasta file to process')

    return parser.parse_args()

def main():
    args = parse_args()

    outdir = args.outdir
    with open(args.in_fasta, "r") as handle:

        for record in SeqIO.parse(handle, "fasta"):
            id = record.id
            seq = record.seq
            outfile = os.path.join(outdir,"{}.fasta".format(id))
            out_fasta = open(outfile,'w')
            out_fasta.write(">{}\n{}\n".format(record.id,record.seq))
            out_fasta.close()

# call main function
if __name__ == '__main__':
    main()

Thanks for your answer! The reason we couldn't split the files and run them individually is that we have a lot of files and it'll take forever to run them individually. Is there a way to run mob-typer on multiple fasta files with single plasmid sequence automatically?


DeepL with immersive-translate Token

Hi I hosted this DeepLX on my self hosted home server, and want to use immersive-translate with this project and i setted up a token, how do i cuztomize the token in immersive-translate?

Immersive translation does not have this feature.

Right... ima open a new issue in immersive translate then


Add NetAcuityGeolocationService

@trevorackerman I apologize for getting your name wrong in the commit message.

The default build will have to not depend on the net acuity artifact unless it can be distributed under one of these licenses - http://www.apache.org/legal/resolved.html#category-a
You'll need to add a maven profile so that building with the net acuity artifact is optional.
Follow the example of what we did for using the neustar version of the geolocation services as a guide. I'd recommend making a module like the neustar module to accomplish this.
I have 2 high priority items I must tackle first, and after I get those done I'd be happy to help guide you by forking your copy of the project and making a pull request against it. But it may be about a week or more before I can do that.

We have moved to a new repo.  If this functionality is desired, please submit a PR there.  https://github.com/apache/incubator-trafficcontrol


Allows for building of Executable by running the SantosBuild script.

Big changes to Note:

Project path is now under user's Document/SantosGUI/
Fonts stored in /application/datas/fonts/

These are pulled during package build. Added to app.spec file
Any new resource that is non-python, non-binary needs to be added to the datas list in app.spec

Still waiting on versions btw!

Looks good! Ship it.


repository url missing

this might be useful info in package.json

Thanks for catching that. Before I can accept your pull request, you will need to sign a CLA. You can find instructions at https://developers.google.com/open-source/cla/individual
Please add a comment or send me an email if/when you sign the CLA. Thanks!

CLA signed, thanks.


Independence

Description
Re-Wrote the plugin and redesigned every theme to have a clean and consistent look.
Heavily leveraged the native platform theme support.
Also addresses these issues:

#181
#139
#104
#124
#94

Motivation and Context
Was going to loose periodic updates from the Material UI upstream.
Wanted to switch to something I could maintain.
So I built the themes from scratch and now I know every nook and cranny :D
How Has This Been Tested?
I have tested all the environments (linux, windows, and macos) and all the legacy theme migrations.
There should be almost seamless theme transition. Save for file colors, which I could not migrate.


DNN-10243: process all binded functions to apply empty values on not exist properties.

code review done


Submit simple job webportal plugin

Coverage decreased (-0.01%) to 52.904% when pulling 55cfa82c515ba1de9a3d07008bff7968dc5ba1d8 on qixcheng/webportal-plugin/submit-simple-job into 746ccb5d07e236341716466cb1d418c2992af9c8 on master.

Coverage decreased (-0.01%) to 52.904% when pulling 55cfa82c515ba1de9a3d07008bff7968dc5ba1d8 on qixcheng/webportal-plugin/submit-simple-job into 746ccb5d07e236341716466cb1d418c2992af9c8 on master.

Coverage decreased (-0.01%) to 52.904% when pulling 55cfa82c515ba1de9a3d07008bff7968dc5ba1d8 on qixcheng/webportal-plugin/submit-simple-job into 746ccb5d07e236341716466cb1d418c2992af9c8 on master.

Hi @squirrelsc, since @scarlett2018 is in holiday, could you please review this document and figure out where to improve?


PENV-464: fix race detection on jetDropRegister

- What I did
block the map field when rage and delete. No slowdowns found
- How I did it
- How to verify it
- Description for the changelog

Codecov Report

Merging #101 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #101   +/-   ##
=======================================
  Coverage   74.70%   74.70%
=======================================
  Files          46       46
  Lines        2926     2926
=======================================
  Hits         2186     2186
  Misses        595      595
  Partials      145      145

Impacted Files
Coverage Δ

etl/controller/pulsemaintainer.go
82.60% <100.00%> (ø)

Continue to review full report at Codecov.

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


Fix wording for comparison operators.

Fixes #737

Yes, this was a mistake. Maybe we should include the same text as in the functional version https://github.com/data-apis/array-api/blob/293512d35f8acccb55b184462505cdb1ab5d1a14/src/array_api_stubs/_2022_12/elementwise_functions.py#L1376

@hameerabbasi Looks like there may be some trailing whitespace which needs to be removed to make CI happy.


Ambient declarations of mixins

Declarations of mixins are not handled as expected by TypeScript compiler, I can't find a way to make it work manually either.
Search Terms:

ambient mixin declaration
type 'T & Constructor' is not a constructor function type
mixin type annotations

Code
One of the solutions I've tried (out of tens):
Declaration:
type Constructor<T = {}> = new (...args: any[]) => T;
function mixin<T extends Constructor<SomeClass>>(
  superClass: T,
): Constructor<T> & T;

Usage:
const anotherMixin = <T extends Constructor<SomeClass>>(
  superClass: T,
) =>
  class extends mixin(superClass) {}

Expected behavior:
I'd expect it to be possible to make ambient type declarations for mixins.
Actual behavior:
TypeScript compiler emits these declarations by copying all of the fields from parent classes.
There's no way to make a type declarations manually.
Playground Link:
Playground does not support emitting type declarations.

type Constructor<T = {}> = new (...args: any[]) => T;
function mixin<T extends Constructor<SomeClass>>(
  superClass: T,
): Constructor<T> & T;

here T is the original constructor type - I'm pretty sure you want to write something like Constructor<MixedInstanceType> & T
interface MixedInstance {
  yay: any;
}

declare function mixin<T extends Constructor<SomeClass>>(
    superClass: T,
): Constructor<MixedInstance> & T;

You can then write something like
interface AnotherMixinInstance {
  // ...
}

declare const anotherMixin: <T extends Constructor<SomeClass>>(ctor: T) =>  Constructor<AnotherMixinInstance> & Constructor<MixedInstance> & T;

Let me be more specific here, maybe I'm missing something:
I'm using a library which provides a mixin for classes extending HTMLElement, but there are no type declarations for this library. This mixin does not introduce any new props/methods, it's declaration could be empty.
I want to create another mixin which overrides some of the functionalities of the one from the library, it does not define any new props/methods neither.
So basically I have something like this:
mixinFromLibrary.d.ts
type Constructor<T = {}> = new (...args: any[]) => T;
function mixinFromLibrary<T extends Constructor<HTMLElement>>(
  superClass: T,
): Constructor<T> & T;

and my implementation, which is built on top of the one from the library:
const myMixin = <T extends Constructor<HTMLElement>>(superClass: T) =>
  class extends mixinFromLibrary(superClass) {}

By doing so I get Type ... is not a constructor function type. I'd like class extends mixinFromLibrary(superClass) to be equal (in terms of type) to class extends superClass.

Works in the latest version.

Actually it doesn't :(


Add hasheddan as provider-alibaba maintainer

Description of your changes

Adds hasheddan to OWNERS.md as a maintainer of provider-alibaba. As the
top committer and the person responsible for handling much of the
release process, it has become a blocker to not have maintainer access
to this repository.
Signed-off-by: hasheddan<EMAIL_ADDRESS>[skip ci]
@jbw976 will be needed to update repository permissions if this is merged
Checklist

I have:

[x] Run make reviewable to ensure this PR is ready for review.
[x] Ensured this PR contains a neat, self documenting set of commits.
[ ] Updated any relevant documentation, examples, or release notes.
[ ] Updated the dependencies in app.yaml to include any new role permissions.
[ ] Updated the package resources documentation to include any new managed resources or classes.

@jbw976 will be needed to update repository permissions if this is merged

This is now completed @hasheddan


remove support for python 3.7

📝 Description of the feature
As pymechanical and pymapdl have dropped their support for python 3.7 (respectively on May 3 and June 14) we should drop it too
💡 Steps for implementing the feature

[ ] Update pyproject.toml
[ ] Remove python 3.7 tests from CI

Not only PyMAPDL and PyMechanical... but all PyAnsys libraries. The metapackage dropped it support some months ago 😄 Thanks for opening this @Gryfenfer97 !


Checkpoint Metadata

Should grad_accum and precision be persisted in checkpoints? If so, how should we support allowing the user to override these fields when resuming from a checkpoint.
Or, are these fields additional metadata that should be recorded in a checkpoint -- but not used when resuming from training?
Are there other metadata fields that we should persist in a checkpoint? (The device? Scale Schedule ratio? Whether deterministic mode was used? The checkpoint load path? E.g.) While the yahp code path records all of this information by dumping the yaml next to the checkpoint, we do not currently save this information in the checkpoint for the non-yahp code path.
Originally posted by @hanlint in https://github.com/mosaicml/composer/issues/445#issuecomment-1034384445

Closing. We have some metadata logged now


Ephemeral Replies And Editing The Message

Use ephemeral replies to tell the user that he cant play the game and edit the message instead of deleting and sending again as it is faster

Recently addressed in v4.0.2 👍


[Issue #23] Add contributing guide

Add Cloverfield Boilerplate Scaffold Generator contributing guide

Two little fixes and it's done.


Waymo Performance and Code

This is a nice work. Would you release the code and performance evaluation on the Waymo Open Dataset?
I expect your positive response.

Yes. We will release some experiment code on Waymo. We are working on code cleanning now.

@kentang-mit Thanks for your open-source code! May I know if you would release both training&evaluation code and pre-trained models in this week?

@kentang-mit I see. I'd like to incoporate your model on Waymo into my framework, would you like to give a rough time for releasing your code? Thanks a lot!

@Son-Goku-gpu Glad to here that! we are working hard towards a new release in mid September.

Closed due to inactivity.

Hi, I am also looking forward to your code for Waymo Open Dataset. It will be great :)
I don't want to rush you, but would you tell me if the code is going to be released soon? Or does it take a little more time?
Thank you very much for your great work!


Aurora crashes suddenly

Expected Behaviour
Aurora functions normally
Actual Behaviour
Aurora crashes after a few seconds or minutes

Reproduction steps
Open Aurora, wait
Frequency
Everytime, after a few seconds or minutes (it varies)
Aurora Version:
v75
Previously an Issue?
No
2022-10-17 20.23.31.log

This only happens if General Settings -> Device Manager -> Asus is running.

Can you copy this file as AuraServiceLib.dll to your Aurora folder and try again?
https://github.com/Aurora-RGB/Aurora/blob/v65/Project-Aurora/Project-Aurora/Interop.AuraServiceLib.dll

Also another option is using armory crate or newest aura sync with the original dll. Whatever works better

I reverted the aura sdk library update:
https://github.com/Aurora-RGB/Aurora/releases/tag/v76

The problem persists after updating to v76.

I've fully reverted asus changes this time. Check v77 please

The problem persists after updating to v77.

Alright, I will give up on razer's aura library. I will integrate RGB.NET.Devices.Asus later. Should be easy after implementing the Logitech library

win10-x64.zip
I've implemented RGB.NET's asus library, also changed device mapping system to handle RGB.NET instead of only Asus devices. Can you unzip this OVER your own Aurora and try it?
Also make a copy of your %appdata%/Aurora folder just in case

It works perfectly! I just had to set all Asus leds as something (logo led in my case) in "Configure Asus Peripheral Devices".
Thanks!

https://github.com/Aurora-RGB/Aurora/releases/tag/v81
new implementation is now with the latest release


feat(menu): add keyboard events and improve accessibility

This PR adds keyboard events and proper focus management to the menu.
r: @jelbourn

@jelbourn Comments should be addressed, and updated the keyboard behavior.

LGTM aside from that one comments


[BUG] zhaquirks.xiaomi.aqara.light_aqcn2 no color_temp, reconfiguration fails

it's not possible to set color_temp attribute to these device (i have 2 of these that where working on Z2M), reconfiguration fails

{
  "node_descriptor": "NodeDescriptor(byte1=1, byte2=64, mac_capability_flags=142, manufacturer_code=4447, maximum_buffer_size=127, maximum_incoming_transfer_size=100, server_mask=0, maximum_outgoing_transfer_size=100, descriptor_capability_field=0, *allocate_address=True, *complex_descriptor_available=False, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False, *is_valid=True, *logical_type=<LogicalType.Router: 1>, *user_descriptor_available=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0102",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0008",
        "0x0300"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019",
        "0x0406"
      ]
    }
  },
  "manufacturer": "LUMI",
  "model": "lumi.light.aqcn02",
  "class": "zhaquirks.xiaomi.aqara.light_aqcn2.LightAqcn02"
}

don't ask me how, but actually reconfiguration still fail, but color temp slider showed up in HA.

Thats failing is the setting up attribute reporting.
Its not the same as setting the CT in ZHA its only that the device is not supporting attribute reporting of it.
Philips HUE device is not using attribute reporting and ZHA need pulling the state of the device with reading the attribute from the device (pulling) that is not Zigbee standard.


fixes #1273 a bug where unnecessary namespaces would be added to models generation

fixes #1273

Hey @baywet,
Any chance we need to update the samples for this one?

We shouldn't as the ms Graph mail samples are namespaced and not impacted by that change. The new ones might though cc @jasonjoh


[DO NOT MERGE] Auto PR to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
96b1407cb7bdcfe6eedcb757baed0449d9cdfce2
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[Feature Request]: Add stargazers timeline

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
My feature is to add an exported stargzers time line that will be used to showcase the timeline of all the contributors who starred your repo
Use Case
To engage with the contributors and provide more better engagement with them.
Benefits
This will enhance the overall engagement of the contributors, who wants to contribute, and drive them to work more,
Add ScreenShots
The end result would be an animated gif exported using my own project
https://github.com/user-attachments/assets/0dfadd5d-ea4e-43cc-a977-ce67021336f1
Priority
Medium
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@yashksaini-coder there is already contributor's webpage in our website, so i wouldn't require this

@yashksaini-coder there is already contributor's webpage in our website, so i wouldn't require this

This is not for contributor's but for the stargazer who took interest in your project it is a great way of showing positive feedback,
Also it is in the correct timeline order so ca be showcased once the project reach a milestone. Let me work on it just assign level 1 if you think it's not that big feat
@Soujanya2004

@yashksaini-coder got it, u can work on that

thanks

@Soujanya2004 can you review the PR #325 I raised to fix this issue, only then can I start working on the #321 issue, as the problem is with the contributor.js file missing so proper contributions data is not fetched.


chore(links): remove redundant links

What does this PR do?

remove redundant links

Description of Task to be completed?

remove home link from login and signup page

remove sidenav from login and signup

How should this be manually tested?

open the online app on https://postit-dyno.herokuapp.com/dashboard

Any background context you want to provide?

feedback from scoreCard

What are the relevant pivotal tracker stories?

https://www.pivotaltracker.com/story/show/153054098

Screenshots (if appropriate)

none

Questions:

none

Coverage decreased (-0.8%) to 90.705% when pulling<PHONE_NUMBER>5d375dd4ff089b563e386d6a8b2cd0 on chore/remove-redundant-links/153054098 into<PHONE_NUMBER>59a166a9ce7fb922f0c7c7f38fd822 on defense-feedback.