[FEAT]change the opacity of the slider buttons in mobile mode.

Hii, I would like to work on this.
Can you please elaborate a little bit more

i am already in queue for getting this issue assigned to me

@ShravaniAK Thank you for the issue, maybe we can do half the opacity + smaller size for the buttons? Can you work on this like that? If so, let me assign this issue to you 🚀

yes i can  work on this

@abhay-ag Thank you for your interest in this issue but looks like @ShravaniAK wants to work on this one as well. You can check out other issues and maybe you can find something you might want to look at 🚀 🚀

Hey @abhay-ag is still something left to do. If so please assign me.

@ShravaniAK any progress on this one?

Looks like @ShravaniAK is not responding 😞 Anyone here want to work on this one?

i am working on it

please reasign

i will finish it today

@aliemir Can I work on this Issue?

Hey @ShravaniAK,
Any updates on this issue?

If the issue still exists, please let me know. My setup is ready.

Hey @ShravaniAK do you need any help ??

Should I start working on this?

@s-vamshi @AbhishekTiwari23 @Vishrut19 Anyone still interested in this? Due to inactivity unassigned @ShravaniAK from this issue.

Yes i would like to work on this issue.
On Mon, Oct 24, 2022, 12:25 PM Ali Emir Şen @.***>
wrote:

@s-vamshi https://github.com/s-vamshi @AbhishekTiwari23
https://github.com/AbhishekTiwari23 @Vishrut19
https://github.com/Vishrut19 Anyone still interested in this? Due to
inactivity unassigned @ShravaniAK https://github.com/ShravaniAK from
this issue.
—
Reply to this email directly, view it on GitHub
https://github.com/refinedev/refine/issues/2739#issuecomment-1288505171,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO4YEGWAJDILZQUS3F3Q5ZTWEYXFFANCNFSM6AAAAAAREAFPD4
.
You are receiving this because you were mentioned.Message ID:
@.***>

actually my exams were going on , i will anyhow make a pr today ,please give me some hours

i have finished the work

i am not able to push , please help

Hey @ShravaniAK ,
You can follow this document
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from- a-fork

i am not able to make multiple commits

refine uses commit-lint. You can visit here to commit-lint rules -> https://cheatography.com/albelop/cheat-sheets/conventional-commits/


fix(npm_translate_lock): hash is stable when version changes

This is a requested feature from a large client. They have frequent merge conflicts on the npm_translate_lock_[hash] file in our external_repository_action_cache because they frequently edit the version number in their packages. We should never need to perform a 'pnpm import' just because a first-party package.json version field changed.

Type of change

Bug fix (change which fixes an issue)

Test plan

Manual testing; please provide instructions so we can reproduce:

I changed the version in e2e/pnpm_workspace/app/b/package.json and ran the build, it no longer updates the e2e/pnpm_workspace/.aspect/rules/external_repository_action_cache/npm_translate_lock_LTE4Nzc1MDcwNjU= file.

Note, I've taken care to not churn files which didn't previously have a version.


is "fails to guarantee reproducibility" a strong claim?

https://github.com/aaronpeikert/repro-tutorial/blob/322602043566c68b53cd18fab3853ffc695e5809/manuscript.Rmd#L223
@cjvanlissa Did you misread this as "fail to reproduce"? I meant that combining Git and RMarkdown is alone not enough to guarantee reproducibility.
Of course, present representatives of other workflows are exempt :smiling_imp:
e.g. worcs is more than RMarkdown + Git.
Including data and software is crucial for reproducibility in my opinion.

As we have argued elsewhere you need four components each of them alone is unlinkly.


[BUG]: error during migration generation on 0.23.1

What version of drizzle-orm are you using?
0.23.1
Describe the Bug
After upgrade to 0.23.1 I receive this error during generating migration, but it is working on 0.22.0 (thats way I am posting here and not in drizzle-kit repo).
schema.ts
import {integer, sqliteTable, text} from 'drizzle-orm/sqlite-core';
import {InferModel} from "drizzle-orm";

export const users = sqliteTable('users', {
    id: integer('id').primaryKey({autoIncrement: true}),
    name: text('name').notNull(),
    createdAt: integer('created_at', {mode: "timestamp"}).defaultCurrentTimestamp(),
    updateAt: integer('updated_at', {mode: "timestamp"}),
    deletedAt: integer('deleted_at', {mode: "timestamp"}),
});

export type Collection  = InferModel<typeof users>;
export type NewCollection  = InferModel<typeof users, 'insert'>;

> drizzle-kit generate:sqlite --out migrations --schema=src/data/schema.ts

drizzle-kit: v0.17.0
drizzle-orm: v0.23.1

TypeError: Right-hand side of 'instanceof' is not an object
    at C:\Users\user1\Desktop\orm-test\node_modules\drizzle-kit\index.js:26671:36
    at Array.forEach (<anonymous>)
    at generateSqliteSnapshot (C:\Users\user1\Desktop\orm-test\node_modules\drizzle-kit\index.js:26663:17)
    at serializeSQLite (C:\Users\user1\Desktop\orm-test\node_modules\drizzle-kit\index.js:26809:14)
    at prepareSqliteMigrationSnapshot (C:\Users\user1\Desktop\orm-test\node_modules\drizzle-kit\index.js:26854:26)
    at prepareAndMigrateSqlite (C:\Users\user1\Desktop\orm-test\node_modules\drizzle-kit\index.js:26980:31)
    at Command2.<anonymous> (C:\Users\user1\Desktop\orm-test\node_modules\drizzle-kit\index.js:49525:9)
    at Command2.listener [as _actionHandler] (C:\Users\user1\Desktop\orm-test\node_modules\drizzle-kit\index.js:856:21)
    at C:\Users\user1\Desktop\orm-test\node_modules\drizzle-kit\index.js:1284:69
    at Command2._chainOrCall (C:\Users\user1\Desktop\orm-test\node_modules\drizzle-kit\index.js:1216:16)

Process finished with exit code 0

@pavelcerveny this should be now fixed in the latest ORM version, please retest.

@dankochetov just tested it, it works now. thanks


fix output panics on unable to write to stderr

Fix #1951  by adding checking if term supports attr Bold

Thank you!


Standardize Databricks environment variable names

Description
In the documentation I can see that in order to authenticate to Databricks Unity Catalog I need to use environment variables DATABRICKS_WORKSPACE_URL and DATABRICKS_ACCESS_TOKEN
However, Databricks has worked recently to standardize the environment variables that hold this information with different names, they use DATABRICKS_HOST and DATABRICKS_TOKEN as stated in section 2.e. of this documentation
It would be great to Unify environment variable names that deltalake used with the ones Databricks uses so that users don't have to maintain 2 different sets of environment variables

This is a good idea, I've tagged it as a good first issue in case somebody wants to grab it, otherwise I think I'll knock it out next week ahead of the next crate release

@rtyler implementer of Unified Auth for Databricks Connect (and other SDKs for Databricks) here =) there's more than DATABRICKS_HOST and DATABRICKS_TOKEN environment variables, we have a full set of SDK OAuth compliance behaviors to verify. We have plans to get compliant auth experience for Rust by releasing something in Databricks Labs, no timeline promises for that yet.
I'd suggest moving this issue to v0.18 milestone and I'll see if we can accelerate the release of that thing in Labs :)

@nfx I'll gladly assign this to you :laughing:  Let me know how I can help!

@nfx I am thinking of queueing up a 0.16 later this week(end) or early next week. Do you think you'd have a chance to fix up some env variables before then? If not I can take this issue back and plonk some changes into a pull request


Fix loading data from configmaps.

ForAll is looping through all the configmaps and decoding the content in to the vol struct, with how this code is, every one of them will point to the same struct in memory. As such, if you restart the provisioner pod, only the data from the last configmap loaded gets used.

cc @mickymiek

@dylanzr  request a port of the changes to master branch as well or, let me know and I can ensure the same. Thanks!

@dylanzr request a port of the changes to master branch as well or, let me know and I can ensure the same. Thanks!

This is taken care by https://github.com/ceph/ceph-csi/pull/363


Source Root not detected by intellij when building with gradle

As stated in the title, the generated source root is not detected by intellij when building with gradle
I am not sure if this problem is coming from this plugin or from quarkus itself.
The project compile correctly, but intellij does not recognize the generated source root,
Quick fix is to right click on the open-api-json folder -> mark as source root, but it need to be done at every restart of the ide.

reproducer: https://github.com/rmanibus/quarkus-openapi_117

That doesn't happen on Maven.

Hi @rmanibus, I am facing the same issue as you. Would you happen to have any solutions?

The quick fix mentioned in my message is working (you might have to add other folders, this is only for json)


reducing location permission on Android emulator causes Exit from debug session

When testing app's response to different permissions, things work correctly if in app location settings I change from deny to only when in use and also to allow...but if I go the other way, reducing the level of permission it quits the debugging session with
Lost connection to device.
Exited (sigterm)

Currently using
VS Code Version: 1.45.1
Flutter extension: 3.10.1

[✓] Flutter (Channel stable, v1.17.1, on Mac OS X 10.15.4 19E287, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
[✓] Android Studio (version 3.6)
[✓] VS Code (version 1.45.1)
[✓] Connected device (1 available)
• No issues found!

but....it has always done this. With all previous releases i've had installed it was the same thing.

Hi @gkrawiec
can you please provide your flutter run --verbose,
your pubspec.yaml
and a reproducible minimal code sample.
(making sure that doesn't rely on 3rd party plugins o packages)
Thank you


iOS Mixpanel crash

Integration Method: CocoaPods
Xcode Version: 10.2.1
Library Version:  3.3.7
Platform: iOS
Language: Objective-C
Description: I received this crash report 3 times within 30 days and I don't know how to reproduce it. Can you help to investigate on it? Thanks.
Expected Behavior:
Fatal Exception: NSRangeException*** -[NSArray initWithArray:range:copyItems:]: range {0, 3} extends beyond bounds [0 .. 1] Raw Text
0 | CoreFoundation | __exceptionPreprocess
1 | libobjc.A.dylib | objc_exception_throw
2 | CoreFoundation | _CFArgv
3 | CoreFoundation | -[NSArray initWithArray:range:copyItems:]
4 | Chope | Mixpanel.m line 1028-[Mixpanel archivePeople] + 1028
5 | Chope | MixpanelPeople.m line 135__65-[MixpanelPeople addPeopleRecordToQueueWithAction:andProperties:]_block_invoke + 135
6 | libdispatch.dylib | _dispatch_call_block_and_release
7 | libdispatch.dylib | _dispatch_client_callout
8 | libdispatch.dylib | _dispatch_lane_serial_drain$VARIANT$armv81
9 | libdispatch.dylib | _dispatch_lane_invoke$VARIANT$armv81
10 | libdispatch.dylib | _dispatch_workloop_worker_thread
11 | libsystem_pthread.dylib | _pthread_wqthread
12 | libsystem_pthread.dylib | start_wqthread

hi @zhangduyu there is a known issue in v3.3.7 that could cause the potential crash, we've fixed it in v3.4.8. Please use the latest version v3.4.9 https://github.com/mixpanel/mixpanel-iphone/releases/tag/v3.4.9
I'm closing this one now, please feel free to reopen it if the problem still exists.
The issue also related to
https://github.com/mixpanel/mixpanel-iphone/issues/821


filterBoolean tests seem to be failing?

See this TypeScript playground example. Perhaps something changed in a recent version of TypeScript such that this no longer works?

You're missing the augment for readonly arrays.
https://github.com/total-typescript/ts-reset/blob/37dc8f0af0b8aa055ec1c740c83a45ccf3d34cf7/src/entrypoints/filter-boolean.d.ts#L7-L9

Thanks @mondash!


using npm i has bundled library

When i download the module, i get .min.js files that are bundled. Thus unusable. Can anyone help?

I get this in the console.
ERROR in ./node_modules/mapboxgl-legend/dist/index.esm.min.js 1:7893
Module parse failed: Unexpected token (1:7893)

and in the code it says i have a ts7016.
Do i need loaders or something to use this module?

If you use npm to install modules it is implicit you're going to bundle them with Webpack, Rollup or any other bundler. Otherwise, you better load the library from a CDN.
Documentation on how to install the module and load it in https://github.com/markusand/mapboxgl-legend#get-started
If you still want to load the script directly from the installed module, you can find an example in https://github.com/markusand/mapboxgl-legend/blob/master/examples/index.html.
Atention! This requires to use a local web server to avoid CORS on loading scripts
If you're just creating an HTML file with all embedded javascript, the simplest, straightforward and recommended way is to forget about npm and load the library directly from a CDN, the same way you are loading with mapbox-gl.
<head>
    <script src="https://api.mapbox.com/mapbox-gl-js/v2.0.0/mapbox-gl.js"></script>
    <link href="https://api.mapbox.com/mapbox-gl-js/v2.0.0/mapbox-gl.css" rel="stylesheet" />
    <script<EMAIL_ADDRESS>    <link<EMAIL_ADDRESS>rel="stylesheet" />
</head>

By the way, never EVER include node_modules to your git repository. Use .gitignore

I suggest loading the library directly from the CDN. You already do it with mapbox, no need to hassle with all the bundler boilerplate for no reason.

Works perfectly from CDN. Great library Mark.
On Mon, Mar 28, 2022 at 11:23 PM Marc Vilella @.***>
wrote:

I suggest loading the library directly from the CDN. You already do it
with mapbox, no need to hassle with all the bundler boilerplate for no
reason.
—
Reply to this email directly, view it on GitHub
https://github.com/markusand/mapboxgl-legend/issues/7#issuecomment-1080584775,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL3TJCCDAKYXHNDIJK2IUOLVCGQE3ANCNFSM5RZYMSJA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Title: Solution for Text Alignment Problem on Hackerrank

Initiative (Required)
Hacktoberfest 2024 🎃
Is your proposal related to a problem? Please describe.
Problem Statement:
"You are given a partial code that is used for generating the HackerRank Logo of variable thickness.
Your task is to replace the blank (______) with rjust, ljust or center."
Add any other context or screenshots about the proposal request here.
No response

Any updates on this?


Bug bragg + chirped fixed.

Types of changes

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

Motivation and Context / Related issue

The diff did not show which function had been modified, and both bragg and chirped should have been. My bad.

How Has This Been Tested (if it applies)

Well, this change has been tested with DE in a separate file where everything was fine. I did not make all the changes in the fork as I thought I had.
Checklist

[X] The documentation is up-to-date with the changes I made.
[X] I have read the CONTRIBUTING document and completed the CLA (see CONTRIBUTING).
[X] All tests passed, and additional code has been covered with new tests.

So, this does change the value of chirped, and the test detected it, hence the red flags.
In photonics/test_core.py can you update the line chirped=("chirped", 0.937039), to chirped=("chirped", 0.94411397),
This way the tests should pass.

Should be done now. Let's cross fingers...


namespace controller causes OOM

Bug description
NamespaceController uses task queue to create ConfigMap istio-ca-root-cert in namespaces, when a namespace doesn't have resource quota to create it, the task will fail and be pushed back into the queue. The status error is:
(dlv) p err
error(*k8s.io/apimachinery/pkg/api/errors.StatusError) *{
	ErrStatus: k8s.io/apimachinery/pkg/apis/meta/v1.Status {
		TypeMeta: (*"k8s.io/apimachinery/pkg/apis/meta/v1.TypeMeta")(0xc00098ae60),
		ListMeta: (*"k8s.io/apimachinery/pkg/apis/meta/v1.ListMeta")(0xc00098ae80),
		Status: "Failure",
		Message: "configmaps \"istio-ca-root-cert\" is forbidden: exceeded quota: ob...+79 more",
		Reason: "Forbidden",
		Details: *(*"k8s.io/apimachinery/pkg/apis/meta/v1.StatusDetails")(0xc00136ff80),
		Code: 403,},}

Related log:
2020-10-18T20:21:56.058605Z	info	Work item handle failed (error when creating configmap istio-ca-root-cert: configmaps "istio-ca-root-cert" is forbidden: exceeded quota: object-counts, requested: configmaps=1, used: configmaps=0, limited: configmaps=0), retry after delay 1s

Also, because namespace informer does resync, more configmap creation tasks will be created, and the failed ones will be accumulated on task queue, this causes istiod's memory usage keeps growing until being OOM killed.
Our k8s cluster has 9,000 namespaces, istiod's memory usage could exceed 50G in one week.
Affected product area (please put an X in all that apply)
[ ] Docs
[ ] Installation
[ ] Networking
[X] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
If config creation failed because reasons like exceeded quota, it shouldn't be retried, namespace informer can take care of it with next resync.
Steps to reproduce the bug

stop istiod
Create thousands of namespaces, set config map's resource quota to 0
start istiod

**Version **
1.6.5

/assign

I think this is a scenario we do not consider before. Let me check whether resync is disabled in recent branch

IIRC in 1.7 we have no resync for namespace informer.  @howardjohn Do we need to fix it for 1.6?

IMHO it's necessary to add a check to determine if a change should be retried. Looks like there already have such checks(https://github.com/istio/istio/blob/master/security/pkg/util/configutil.go#L45-L48), but looks like that's not sufficient.
I guess request should only be retried for below reasons:
metav1.StatusReasonServerTimeout:
metav1.StatusReasonTimeout
metav1.StatusReasonTooManyRequests
metav1.StatusReasonServiceUnavailable

Also max retry times should be given. If a request can't retry or exceeds max retry times, the task shouldn't be enqueued anymore.
But, considering resync is disabled, and configmap informer doesn't filter config may by label anymore(see https://github.com/istio/istio/blob/release-1.6/pilot/pkg/serviceregistry/kube/controller/namespacecontroller.go#L74, release-1.7 checks configmap's name instead), if task failed to retry, will it cause some other issues?  Please kindly correct me if I misunderstand anything.

metav1.StatusReasonServerTimeout:
metav1.StatusReasonTimeout
metav1.StatusReasonTooManyRequests
metav1.StatusReasonServiceUnavailable

I donot think this is enough, there are many error types from k8s: https://github.com/kubernetes/kubernetes/blob/16e18a590f32b931cdceb5372664198c0e49831a/staging/src/k8s.io/apimachinery/pkg/apis/meta/v1/types.go#L708-L852

if task failed to retry, will it cause some other issues?

Nope, when it fails, we still put it back to the queue.

Also max retry times should be given. If a request can't retry or exceeds max retry times, the task shouldn't be enqueued anymore.

Then this is a permanent error, we have no way to notify that this namespace is unavailable.


FTP deployment failure to an existing function app

Plugin name and version
com.microsoft.azure.azure-functions-maven-plugin:0.2.0-SNAPSHOT
Actual behavior

@bsaby Just as the log shows. It it because the jar file is been occupied by the service. To solve this problem, you and add <stopAppDuringDeployment>true</stopAppDuringDeployment> in the plugin configuration

I can't repro this issue after adding the configuration <stopAppDuringDeployment>true</stopAppDuringDeployment>


alt tab can be trigged but the selected window cannot show up.

I tried to use it with plant vs zombie.
I have to enable FullscreenWindowMode so the game launch with fullscreen mode,
but I cannot switch to another window.

Yes, FullscreenWindowMode forces the window to be on the top.  Try pressing Win+D to minimize all windows.  Then you should be able to switch to another window after that.

Ok, try this update and let me know if it works or not:  dxwrapper.zip

I fiddled around with a similar Alt-Tab Issue a while ago, but it was for Windowed Mode, not sure if it applies here too.
Don't know what the code changes are in the ZIP, maybe they are pretty much the same.
I haven't gotten around to pushing some of my stuff to my fork yet for a possible PR ( wasn't sure if it was too hacky anyway ).
My main code change was in IDirect3D9Ex.cpp, AdjustWindow Function changing SetWindowPos(MainhWnd, HWND_TOP, 0, 0, 0, 0, SWP_NOMOVE | SWP_NOSIZE | SWP_NOZORDER | SWP_FRAMECHANGED); to SetWindowPos(MainhWnd, HWND_NOTOPMOST, 0, 0, 0, 0, SWP_NOMOVE | SWP_NOSIZE | SWP_NOZORDER | SWP_FRAMECHANGED);

Try this update and let me know if this works or not:  dxwrapper.zip

:thinking:

I am not sure if the last fix solved this issue.  However, I can reproduce this issue with dd7to9 on a couple of games.  What features of dxwrapper are you using for this game?  I don't think setting HWND_NOTOPMOST is the right fix.  I have seen where removing D3DCREATE_NOWINDOWCHANGES has solved this for some games.

Alt+Tab should work for most games with the latest build here:  dx7 binaries.zip

Closing issue.


[Legend] Gather the legends of the same layer in the same block

In back office

No change

In front

Have one block per layer
Be able to display several shapes in the same block
Visual separation between informations of several layers

Current

Proposition

Changed the background for a transparent one but we can totally keep the current style.
In this example, the title is not automatic, the first layer just has four legends and only the first one has a title. The second layer has two legends with both having a title.


🐛 Bug Report: UI: Update time format to MM/DD/YY

Which component is this bug for?
Anthropic Instrumentation
📜 Description
Can we update the data format to MM/DD/YY, current format is DD/MM/YY
👟 Reproduction steps
Check filter on the UI page
👍 Expected behavior
Can we update the data format to MM/DD/YY, current format is DD/MM/YY
👎 Actual Behavior with Screenshots

🤖 Python Version
No response
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

Are you willing to submit PR?
None

Thanks @gyliu513! While not a bug in the sdk I'll fix it in our UI to match the local system settings.


Deploying to Degen L3

I wanted to add Degen L3 to the splits SDK, I've already deployed the The main and the wallet contract on the degen
{
  "Contracts": {
    "SplitMain": "0x6301B6Bc76Dd56A26515EdeCeE203d1Ab84202DC",
    "SplitWallet": "0x006c77062eDEA0894762F31b9B0421a22245CD2b"
  }
}

I wanted to discuss is there any other contract i need to deploy before making a PR to add the chain or is there any other procedure.

Hey thanks for reaching out. We are not planning on adding new networks for SplitMain to the sdk. We just announced our launch of our v2 Split contracts: https://splits.org/blog/v2-launch/
The SDK support for those will be live this week. We will be putting a process in place for requesting those v2 contracts on new networks, and for requesting (basic) sdk support.
More advanced sdk support (i.e. fetching earnings) requires a subgraph, and we are going to be more selective about which networks are included in our subgraph. But interacting with the contracts should work with the basic sdk support.

If you really need to use SplitMain on Degen L3, unfortunately you will need to either interact with your contracts directly or fork the sdk

Currently, we are directly interacting with the contract, which is doing the job for now, i was not aware of v2, I'll check it out. thanks


Install issue due to invalid C++ redist from official guide

the usual install error for luxcore 2.4 blender 2.83.7 with C++ redistributables was only fixable by installing.

Microsoft Visual C++ 2015-2019 Redistributable (x86) - 14.27.29016
Microsoft Visual C++ 2015-2019 Redistributable (x64) - 14.27.29016

The links provided by the official installation guide on the website is not sufficient enough on windows 10 64 bit

The "usual install error" ? What do you mean ?
As far as I know, the Visual C++ 2015 runtime redristibutable linked in the first line of the Download page was the correct one and has worked for a long time. Wasn't it working for you ?
May be, Microsoft has changed the landing page ?


Update sample.cs

Applying the change of https://github.com/dotnet/samples/pull/1075 to the corresponding c# code.

Created this PR in the wrong repo by mistake. The upstream repo is already correct.


Simplify TokenBrokerResolver in Basic Auth Sample

First step to adapt sample for 3.0.0.
Reduces TokenBrokerResolver in spring-security-basic-auth sample to BasicAuth case, use XsuaaTokenFlows and remove
related dead code.

Thank you for your review and the helpful remarks 😊


Simplify Docker image and reduce size

Add a command to properly create the environment on GCP
Fix the following bugs:

Topic was not calculated
Default key type is now configurable

Hi Team,
It seems that Travis did not run properly. It looks like it is not linked to my modifications but rather to the build script by itself.
Badfuly I'm unable to relaunch the build and hence have it passed
Could you please do something about this ?
L.

Ugh. When did we enable Travis in this repository?  Because those scripts have not had any care and feeding in over a year, and the Linux distros they test with have been EOL for a while. I doubt they pass if you run against master.

In case you did not see this, #44 fixes the Travis build. Once merged (and I would like @SurferJeffAtGoogle or any other team member to review), you will need to rebase and push this PR again.

@ltouati you need to rebase and push again to pick up the changes from master that fixed the build.

Fixed code based on pr comments


Getting optimisation issue with some CSS

When I use webpack -p, I'm getting a non helping error message
ERROR in ./~/css-loader!./~/cssnext-loader!./src/index.css
Module build failed: Error: Please check the validity of the CSS block starting from the line #1
    at throwError (/.../node_modules/css-loader/node_modules/csso/lib/gonzales.cssp.node.js:399:15)
    at checkStylesheet (/.../node_modules/css-loader/node_modules/csso/lib/gonzales.cssp.node.js:1921:22)
    at Object.CSSPRules.stylesheet (/.../node_modules/css-loader/node_modules/csso/lib/gonzales.cssp.node.js:365:40)
    at _getAST (/.../node_modules/css-loader/node_modules/csso/lib/gonzales.cssp.node.js:409:38)
    at exports.srcToCSSP (/.../node_modules/css-loader/node_modules/csso/lib/gonzales.cssp.node.js:2287:16)
    at Object.exports.srcToCSSP (/.../node_modules/css-loader/node_modules/csso/lib/gonzales.cssp.node.js:2292:16)
    at Object.exports.parse (/.../node_modules/css-loader/node_modules/csso/lib/cssoapi.js:7:21)
    at Object.module.exports (/.../node_modules/css-loader/index.js:18:18)
 @ ./src/index.css 4:14-293

In this index.css I just have some inlined @import, so this error is not really helping.
Is there any way to improve that?
My first import is normalize.css and after taking a look in the <style> element I saw some empty :root elements (due to the fact I use future proof CSS transformed via cssnext).
It seems the parser you are using is kind of outdated for some part.
If you are using csso for minification, would you consider switch to a more fresh tool (csswring) based on an parser with an active development (postcss)?

PostCSS is backed by Autoprefixer, so it's probably developed more actively. :+1:

postcss 4 is really fast (just run this to check it out https://github.com/postcss/postcss/tree/master/benchmark ) & even support CSS specs that are not implemented in browsers. So seems a really good choice indeed.

Yes, write a PR... I've already tried to use an alternative library in the rework branch.
Check that all test pass and maybe add some for the new stuff.
The rework branch doesn't work out, because it removed the whitespace from css and this would break SourceMap.

rework is kind of unmaintained (last commit is from august 2014).
More & more people are switching to postcss now that the ecosystem start to be consistent.

yeah... I'm fine if you do a PR with postcss.

Closing since you now use postcss


Support dates in config

We've discovered a case where we want to use the date replacement in the config, specifying a minValue and a maxValue.
This PR adds that functionality - repeating the same JSON replace magic in the config in the same way as it is done elsewhere.

👍


Links are hard to read on the sources page

An other color is needed.
Maybe darker blue.

Fixed by #60.


Deprecation warning on node v6

node-lmdb produces a lot of deprecation warnings when run with node.js version 6 and up:
v8::ObjectTemplate::Set() with non-primitive values is deprecated
The call will be deprecated in version 7, but it is already quite annoying because the screen fills with deprecation warnings...

Are you running the latest master, because some of the warnings have been cleared with: https://github.com/Venemo/node-lmdb/commit/bda3aa5ff0bd01c87dd40cde0def05ce7884582e

There are still a few deprecation messages when running node-gyp rebuild with Node.js v6.

I didn't build from master - just the latest version available with npm (version 0.4.1).
But it's great to know that you've started looking into getting them fixed.

Try latest master, @braydonf submitted a pull request that improves on this.

@mzedeler Do you still experience this problem?

I believe I have fixed the last deprecation warnings now, so I'm closing the issue. Please reopen if you find any more problems with it.


IMixedRealitySceneSystem interface and definitions

Overview
Interface for the IMixedRealitySceneSystem service described in #3987
An complete implementation is in progress in draft PR #4107
While we wait for that PR to exit the draft stage @davidkline-ms suggested we discuss the interface, which is ready to be evaluated.
Looking forward to your comments and suggestions!

Looking good so far @Railboy

It might be out of scope for this review but it would be helpful to provide an example of how the scene system would be used

@julenka I'm saving that for the scene system implementation.


Remove or disable a Pet | Back End

Objective
Create a GraphQL mutation where the User will be able to remove or disable a Pet:

Additional information:

Will only need Logged User's token to validate the action

Tasks

[ ] [GraphQL] Create the mutation for Pet removal

[ ] Add UT to mantain code coverage

[ ] [Mongoose] Create the action for Pet removal

[ ] Add UT to mantain code coverage

A pet could set as Deceased only after been created and not in the process of creation?


KAFKA-3855: Guard race conditions in TopologyBuilder

Mark all public TopologyBuilder methods as synchronized as they can modify data-structures and these methods could be called from multiple threads

@guozhangwang

LGTM. Merged to trunk and cherry picked to 0.10.0.


Safari can't run NextJS Blitz

Describe the bug
Trying to start a Next.JS project inside Safari results in errors and does not boot up.
Link to the blitz that caused the error
https://stackblitz.com/edit/stackblitz-starters-xjuuc8?description=The React framework for production&file=README.md&title=Next.js Starter
Steps to reproduce

Open Safari
Go to https://stackblitz.com/edit/stackblitz-starters-xjuuc8?description=The React framework for production&file=README.md&title=Next.js Starter or start from the NextJS starter template
let it yarn and yarn dev
See the following error trace:

3 packages are looking for funding
  run `npm fund` for details
[callSiteLocation@
depd@
880@
__nccwpck_require__@
701@
__nccwpck_require__@
@
@
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:14872
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:15558
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:13457
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:10539
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:13780
@
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:14872
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:15558
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:13457
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:10539
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:13780
@
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:14872
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:15558
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:13457
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:10539
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:13780
@
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:14872
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:15558
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:13457
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:54:10539
executeUserEntryPoint@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:125:736
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:318:173
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:318:186
_0x5621ef@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:350:56573
_0x1d3a99@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:352:101528
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:352:618830
@https://stackblitzstartersxjuuc8-0zli.w-corp-staticblitz.com/blitz.810981ba.js:371:1352]

Expected behavior
No error is thrown. NextJS dev works.
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform
Browser name  = Safari
Full version  = 17.2
Major version = 17

Additional context
No response

Reproduced in Safari 17.4 as well.


feat: add IntelliJ icons

For that, we will need 2 icons, ideally 192*192:

icon.png
icon_dark.png

These can be identical.
Closes #13


Bullet Velocity vs Pinocchio Velocity

Hello and thank you for your work and support,
I am using PyBullet for the simulation of a Barret WAM and it seems that the velocity of Pinocchio and Bullet are not the same.
What you can see is just the Y axis. It is the axis along which the endeffector falls.

As you can see, both estimate the same values for the position. But the velocity differs.
The configuration is as follows:
p.resetJointState(bodyUniqueId=BW, jointIndex=1, targetValue=np.pi/2)
p.resetJointState(bodyUniqueId=BW, jointIndex=4, targetValue=np.pi/2)

There is no influence from any motor. It just falls to the ground. What's really interesting is, at the beginning apparently Pinocchio thinks that the ee is falling to the wrong side.
Here is the code:
q = np.empty(modelWAM.nq)
dq = np.empty(modelWAM.nq)

for i in range(0, 4):
    q[i] = p.getJointState(BW, i + 1)[0]
    dq[i] = p.getJointState(BW, i + 1)[1]

pinocchio.forwardKinematics(modelWAM, data, q, dq)
pinocchio.updateFramePlacements(modelWAM, data)

J = pinocchio.computeJointJacobians(modelWAM, data)

endPos = data.oMf[frame_id_end_effector].translation
linkState = p.getLinkState(
    BW, 6, computeForwardKinematics=True, computeLinkVelocity=True)

pinocchioPos.append(endPos.copy())
bulletPos.append(np.asarray(linkState[0]))
pinocchioVel.append((J @ dq)) # or
# bulletVel.append(pinocchio.getFrameVelocity(
#     modelWAM, data, frame_id_end_effector, pinocchio.WORLD).linear)
# leads to the same result
bulletVel.append(np.asarray(linkState[6]))

p.stepSimulation()

Do you have any idea what I have done wrong? Thank you in advance.

Check which frame J is computed in from pinocchio. If you request the frame LOCAL_WORLD_ALIGNED, the values should look similar.

Thank you, it seems to be working. Could you tell me, that is the difference between WORLD and LOCAL_WORLD_ALIGNED? Do I also need to get the dJ in that specific Frame than?

The frame WORLD has the spatial velocity described in fixed-frame. Very often, this is not what you want LOCAL_WORLD_ALIGNED is the same as the LOCAL body Jacobian except the Jacobian has been rotated to be align with the world frame.
A simple relationship between the LOCAL jacobian and LOCAL_WORLD_ALIGNED is the following:
J_local_world_aligned = [R, 0; 0, R] * J_local  where J_local has been pre-multiplied by a 6x6 matrix where R is the orientation of the link with respect to the world.
A good reference to understand the difference between WORLD and LOCAL is available in section 3.3.2 with a discussion on how to convert between the two in <IP_ADDRESS>  here:
http://hades.mech.northwestern.edu/images/7/7f/MR.pdf

Thank you very much

Thanks @stevenjj for nicely answering this issue.


Investigate rerendering of homepage components

With the new auth/GraphQL implementation, some homepage components are being rendered multiple times on the page's initial load. This is related to the use of context, but we need to determine why exactly this is happening and how to fix it.

This only happens when logged in -- closing in favor of #688.


Add links to my portfolio and twitter account.

First off, great idea for strengthen the data vis community and thanks for setting up this website! 👍
With this PR I would like to add a link to my portfolio and Twitter account.
I also reordered the links to freelancers by their forename alphabetically. Was not sure where to add my name otherwise.
Let me know what you think.

Thanks!
Yes, the names should be sorted alphabetically.

Thanks for merging! 🙂


Can't shim 'watchexec.exe': File doesn't exist.

The watchexec installer doesn't seem to work.
Installing 'watchexec' (1.9.2) [64bit]
Loading watchexec-1.9.2-x86_64-pc-windows-gnu.zip from cache
Checking hash of watchexec-1.9.2-x86_64-pc-windows-gnu.zip ... ok.
Extracting watchexec-1.9.2-x86_64-pc-windows-gnu.zip ... done.
Linking ~\scoop\apps\watchexec\current => ~\scoop\apps\watchexec\1.9.2
Creating shim for 'watchexec'.
Can't shim 'watchexec.exe': File doesn't exist.

I was able to build and install using cargo instead. I wonder if maybe something is wrong with the zip it's downloading?

It's likely the file structure contained in the ZIP archive changed between releases — this should be easy to fix.

Fixed


prevent spaces in emails

so this is not the first time a customer of mine is just copy pasting stuff in emails fields and somehow, a space at the end skips validation. this update ensure there is no space before or after the email, it would probably save a lot of time for everyone to have this build in.
it's probably better to fix it here rather than at form level because this also happens for csv imports etc

@emteknetnz sounds great! i made the changes


[docker] GitHub Action to push gem and build Docker image

Trigger Action on push to main with lib/aws_recon/version.rb changes.

release gem in pre-commit hook
build Docker image
push to Docker Hub

Fixed in https://github.com/darkbitio/aws-recon/commit/caf8418c2b147a47b9fb51a2ddea79cb8c5d2253.


$isIe() returns false on IE11

It seems that $getStyle(element, "height") is a little bit unreliable in some browsers since it returns auto for some elements. To work around this I was considering using element.offsetHeight but in this case it would only be needed for IE.
Unfortunately, as @jvalente mentioned, $isIe() returns false on IE11. Is there a workaround for this?

hey @pmpinto, feels a bit like a desert in here. :P did u manage to work this out?

Hi @pmpinto and @jvalente

I am unsure if it's necessary to use $isIe any more, since IE 11+ is an excellent browser
element.offsetHeight is probably more correct than using $getStyle(element, "height")

Hey @jvalente! I only needed $isIe() to make sure I was getting the proper height value, so I ended up using element.offsetHeight since it worked pretty much everywhere.
https://github.com/Doist/Todoist_Static/blob/05dd2b9a16b259659be899965e98aefa19769ec2/landing_pages/static/apps/landing_pages/js/Sticky.js#L59-L62

@pmpinto I would generally recommend using ES6 and using pure JavaScript in a ton of places -- since vanilla JS is becoming quite nice to work with. Check out http://youmightnotneedjquery.com/ 😊

Thanks @amix! I think Jano shared this website with me earlier. It's a good resource to have at hand, for sure.


Switch to using model.predict instead of model.predict_generator.

Hi!
When using imagededup with TF 2.5.0 I got the following warning  message:
/usr/local/lib/python3.8/dist-packages/tensorflow/python/keras/engine/training.py:2001: UserWarning:
`Model.predict_generator` is deprecated and will be removed in a future version.
Please use `Model.predict`, which supports generators.

This is due to this line in CNN method:
https://github.com/idealo/imagededup/blob/3465540cc5c8fdf9254aff76069e28641dfc515f/imagededup/methods/cnn.py#L102
Can push a simple fix if you are interested.

We replaced tensorflow with pytorch now. Thanks for your input anyway.


chore: use node_test macro on tests

This PR refactors the tests that were creating nodes manually like:
let (mut ctx, mut executor) = ockam_node::start_node();
executor.execute(async move {
    // ... test code
});

to start using the new node_test macro. Changing the node macro usages by the new one from the ockam_node_test_attribute repo will be done in a separate PR as the old node macro has been extended recently, so I'll have to make some modifications to the new macro.
Related

https://github.com/ockam-network/ockam/pull/2061#issuecomment-950731610

Merged as #2176 - thanks!


added in ol/util a tool to migrate configfiles

tool to migrate config files
Should be run after version upgrade to avoid manipulating config files manually for already configured nodes. A backup file is created before manipulating the original file.
currently only adds "db_path" into the "[workspace]" section of 0L.toml
potential enhancements:

update value for an attribute
remove attribute
rename attribute

example usage (currently takes no arguments):
cargo run -p ol-util

This is great @mortonbits. I think we should add a few more fields with names that have migrated. Namely related to TxParams and TxCost fields. Can you take a look at the difference in the files from v4.2.8, and v4.3.0? Very helpful thanks


wzrd doesn't work well on windows

It requires browserify to be installed globally and locally to compile the javascript, sometimes that doesn't even fix it as it messes up the pathing. Is there another tool available?

Thanks
Here's another that uses watchify, but otherwise feels the same as wzrd:
https://github.com/mattdesl/budo
npm install budo -g
budo index.js:bundle.js

Also there is Beefy:
https://github.com/chrisdickinson/beefy
I will check it out on a PC tomorrow and see if I can submit a PR to wzrd. It's the smallest/simplest of the bunch so I figured probably the best for a quick intro; but I could change it if it's still causing issues.

I'll give it a try as well tomorrow. If it works, we can just have a line saying if you are experiencing trouble with wzrd, give budo a try.


server: usage caps enforcement

fixes: #1297

[ ] remove all unwraps
[x] test upsert doc

why are billing tests ignored? f
fyi: i edited downgrade_denied to reflect the server enforcement of usage caps, and ran it locally. it passes.


Stubs for testing erlang SSL/TLS.

Added stubs for erlang. erlang-httpc for ssl-via-httpc and erlang-ssl for direct usage of ssl:connect.

Fantastic work, a few tweaks more and it's ace!

@Mamietti Thanks for the feedback, I'll try to do some fixes in the evening (hopefully I have time). Thanks for pointing out the stub documentation, I hadn't noticed it – I used one the existing stubs as the specification :-)


Is the target always required for the estimator?

I am still not very familiar with either Push/PushGP (implemented in other languages) and PyshGP. In all examples I've seen in this repo, it seems that you need to pass the inputs, denoted by X, and the targets/outputs, y. It's not clear to me why is this strictly necessary. If you're performing supervised learning, yes, sure you need a labeled dataset, but, in our case, we are performing GP, i.e. in general, in GP/GAs, you don't have to specify any target/label, you just need a way to evaluate the fitness. So, is this target what would be the fitness?
This does not seem right, because how can we evolve programs in case we don't have the target? We first need to execute the programs to evaluate them and then compute the targets (i.e. the evaluation of the programs), which would imply that the estimator assumes that you already executed and evaluated the programs, so how can you use PyshGP to evolve programs (i.e. GP)? So, what would the estimator actually do here?
What would this API (estimator that needs inputs and targets) correspond to (in terms of code constructs) in other implementations of Push and PushGP, in particular, I am interested in this C++ implementation by Maarten Keijzer?
I am trying to convert a GP program written with that C++ implementation to PyshGP, but it's not clear why you have targets in PyshGP, so what do they map to in that C++ implementation.

Good questions. It seems like you have some questions about PushGP in general and some questions about the specific implementation of pyshgp. I'll break down my answer into sections.
1. Just a clarification of terminology.
 It is possible to have supervised and unsupervised evolutionary systems. Typically, GP systems are supervised. The most popular kind of GP is symbolic regression/classification which is inherently supervised.
Based on my reading of your questions, it seems like you define "supervised" as: requires a dataset of know labels. If we configure our evolutionary systems with a fitness function, is that any less supervised? I would say no, but perhaps that is merely semantics.
2. Is PushGP always driven by input-output datasets?
No, PushGP can be driven by an error/fitness function. That said, in the PushGP literature it is almost always the case that we evaluate Push programs based on input-output pairs and thus the natural framing of the problem is usually with datasets. If you have a different way of evaluating programs, it is perfectly reasonable to supply your own error function.
3. How can custom error functions be used in pyshgp?
There are 2 "public" APIs in pyshgp: the Estimator and the SearchAlgorithm. The Estimator API is meant to mirror the scikit-learn API, which is driven by datasets. As you have noticed in #150, pyshgp will eventually open up Estimators to support custom loss functions (still dataset driven) and custom evaluators (not dataset driven).
The SearchAlgorithm API is less commonly used, but it is meant to handle what you are looking for. First you must instantiate a SearchConfiguration, which includes an Evaluator parameter. Then you instantiate a GeneticAlgorithm with the config and call .run().
I recommend looking into using a FunctionEvaluator for your evaluator.
4. How does the API of pyshgp compare with the API of CPushPush?
I have never looked into either implementation of CPushPush. Maarten was the original author, and the fork you linked is maintained by Kwaku Yeboah-Antwi. Based on the GitHub issues of Kwaku's fork, it seems like there is no GP system built in and thus there would be no corresponding code construct.
Hopefully those answers have helped. Let me know if you have any other questions.

@erp12 Thanks! That clarifies a few things, especially about the estimator.
I am very familiar with SL, UL, RL, GA, etc., but I never thought of GA as supervised. In the past, I only used and implemented GAs by using a fitness function, which is more similar to a reward function in RL, so I would almost say that GP/GA is more similar to RL than SL and UL, but, yes, it's true, the supervisory signal could work as the fitness (which is the case of most of your examples, if I understood them).
Regarding SearchAlgorithm, do you have examples? For example, could I solve the ant problem (a typical problem that GP is applied) using SearchAlgorithm? If you could provide a simple example of how to use this API, that would be nice. Meanwhile, I will see what I can do with SearchAlgorithm.
Given that I wasn't yet familiar with the details of Push and PushGP when I wrote the comment above, I didn't really think about the difference between Push and PushGP, which seems to be just a simple implementation of GP in Push, which, as you say, is apparently not implemented in CPushPush, but I was looking at another codebase that uses CPushPush that implements some form of GP, that's why I was probably confused.


extract volume: Fix NPE when Volume exists on secondary store but doesn't have a download URL

Description
This PR fixes an NPE that's noticed when we perform the following:

Download a volume - such that we have the download_url set in the volume_store_ref table against the respective volume
Perform an operation that causes the download_url to be cleared, say, destroy the SSVM
Post re-creation of the SSVM , re-initiate download of the same volume, it fails with an NPE

2020-12-10 08:56:03,164 ERROR [c.c.a.ApiAsyncJobDispatcher] (API-Job-Executor-2:ctx-ef7f5a39 job-652) (logid:169bd39d) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd
java.lang.NullPointerException
	at com.cloud.hypervisor.guru.VMwareGuru.getCommandHostDelegation(VMwareGuru.java:274)
	at com.cloud.hypervisor.HypervisorGuruManagerImpl.getGuruProcessedCommandTargetHost(HypervisorGuruManagerImpl.java:76)
	at org.apache.cloudstack.storage.RemoteHostEndPoint.sendMessage(RemoteHostEndPoint.java:120)
	at org.apache.cloudstack.storage.datastore.driver.CloudStackImageStoreDriverImpl.createEntityExtractUrl(CloudStackImageStoreDriverImpl.java:83)
	at org.apache.cloudstack.storage.image.store.ImageStoreImpl.createEntityExtractUrl(ImageStoreImpl.java:212)
	at com.cloud.storage.VolumeApiServiceImpl.setExtractVolumeSearchCriteria(VolumeApiServiceImpl.java:2887)
	at com.cloud.storage.VolumeApiServiceImpl.extractVolume(VolumeApiServiceImpl.java:2800)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
	at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
	at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
	at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:95)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
	at com.sun.proxy.$Proxy215.extractVolume(Unknown Source)
	at org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd.execute(ExtractVolumeCmd.java:137)
	at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
	at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
	at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
	at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
	at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
	at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
	at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
	at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
	at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[X] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[X] Major
[ ] Minor
[ ] Trivial

How Has This Been Tested?
Perform the above mentioned steps and the download url is created.

@blueorangutan package

@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✔centos8 ✔debian. JID-2477

@blueorangutan test

@Pearl1594 a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

@Pearl1594 is this also a bug in 4.14 ?

@weizhouapache I believe this got introduced in 4.15

@weizhouapache I believe this got introduced in 4.15

ok thanks @Pearl1594

@weizhouapache I believe this got introduced in 4.15

@Pearl1594 by the way, do you know what lines of code changes causes it ? is there any other issue ?

@weizhouapache I think it was introduced by https://github.com/apache/cloudstack/pull/4078/files#diff-b93da5c5293f8cb4470ff6b1642d312131bb053df07b71b4b951b08dff0ad9abR2881 and there are no other issues wrt this that I noticed.

thanks @Pearl1594
we will look into it @ravening

@Pearl1594 Im not able to reproduce the issue is kvm. Is it specific to vmware which is seen from your logs?
Before destroying systemvmn
mysql> select * from volume_store_ref\G
*************************** 1. row ***************************
                  id: 1
            store_id: 1
           volume_id: 962
      download_state: DOWNLOADED
        install_path: volumes/2/962/14961c07-b490-43f4-991a-1628e5878178.qcow2
                 url: NULL
        download_url: https://10-135-122-128.cloud.net/userdata/e21f48ea-3ffd-448f-95ad-defdb9d08245.qcow2
               state: Ready
           destroyed: 0
        update_count: 2
             ref_cnt: 0
             updated: 2020-12-10 16:20:15
download_url_created: 2020-12-10 16:20:17

After destroying systemvm
mysql> select * from volume_store_ref\G
*************************** 1. row ***************************
      download_state: DOWNLOADED
        install_path: volumes/2/962/14961c07-b490-43f4-991a-1628e5878178.qcow2
                 url: NULL
        download_url: NULL
               state: Ready
           destroyed: 0
        update_count: 2
             ref_cnt: 0
             updated: 2020-12-10 16:20:15
download_url_created: 1969-12-31 00:00:00
1 row in set (0.01 sec)

After creating systevm again
mysql> select * from volume_store_ref\G
*************************** 1. row ***************************
      download_state: DOWNLOADED
        install_path: volumes/2/962/14961c07-b490-43f4-991a-1628e5878178.qcow2
                 url: NULL
        download_url: https://10-135-122-128.cloud.net/userdata/26df39b8-1a43-45db-b515-f8a6ec9150a9.qcow2
               state: Ready
           destroyed: 0
        update_count: 2
             ref_cnt: 0
             updated: 2020-12-10 16:20:15
download_url_created: 2020-12-10 16:22:40
1 row in set (0.00 sec)

@ravening I faced this issue on a KVM environment.

Trillian test result (tid-3330)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 35253 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4530-t3330-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_kubernetes_clusters.py
Intermittent failure detected: /marvin/tests/smoke/test_privategw_acl.py
Smoke tests completed. 86 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File


guide: Managing(?) Experiments

Converted to issue from #2752  <-- See text contents

[ ] Combine and summarize the motivation text in the section index
[ ] Finish "Handling" Exps guide (mainly about exp show/compare)
[ ] Remove deep details from the command reference that can be moved here instead

Maybe also include (if natural)

[x] https://github.com/iterative/dvc.org/issues/2736
[ ] https://github.com/iterative/dvc.org/issues/2737

Other notes

https://github.com/iterative/dvc.org/pull/2752#pullrequestreview-737794776
https://github.com/iterative/dvc.org/pull/2752#pullrequestreview-737795264
https://github.com/iterative/dvc.org/pull/2752#pullrequestreview-737795421

Added to https://github.com/iterative/dvc.org/issues/2548 for now.

The title can be

organizing experiments
operations on experiments
managing results of experiments

Looks like we don't need this any more. @iesahin maybe check your original contents in https://github.com/iterative/dvc.org/pull/2752/files in case we still want to rescue anything. Thanks


Create Campaign - Form changes (Part 3)

NOTE: To be picked up after #2212 is completed and merged.
When logged in as a site admin, the user can create new campaigns in allReady.
Having reviewed the UX of this form we should add a visual clue (probably an asterisk) to required fields. Currently a user cannot identify these fields until they submit a form with any incomplete, required fields.
The following fields are currently considered required and should be marked:

Name/Campaign Title
Address1/Address Line 1
City
State
Postal Code
Country

This has been implemented

Thanks @mk0sojo - I'll close this out


Adding Resurrection to the Player

The resurrection of character caused some bugs with the client.
Fixing when the mouse goes out of the range of tile render walk indicator.

I had some fun improving the network packets, so I took the liberty of fixing up the rest of the PR as well.


Note that the CD triggering mechanism is on git tag

Pinging @harshula to remind him to push a tag to start the deployment process for ACCESS-OM2, when priority work is completed.

Thanks. Just want to confirm, you want me to do this only once you have completed your high priority tasks, in case something goes wrong with CD?

Correctamundo

No longer!


improve code coverage

We want to improve our code coverage, see https://codecov.io/gh/OpenSourceEconomics/soepy

@SeBecker , could you tell me again what our target rate of code coverage is? At the above link I am seeing that we have ca. 83% for soepy as a whole. However, coverage in the actual python folder is already at 96.53%. The lower overall value is due to no coverage on the test folder.
Is there some part of the code I should add tests for in your opinion? Or can we consider this done for now?

Our goal is a coverage rate above the 90% threshold. @peisenha: does this also include the coverage rate of the test directory?
Nevertheless there are still several options for increasing the coverage rate in the test directory. For instance we could move our regression vault creation module from test/resources to a new folder in the development directory (or we could adjust our regression test setup so that it executes the check function from the same module).

Thanks for following up. Please try to keep the test directory included and
moving the regression vault creation outside soepy/soepy an instead to
soepy/development is a good idea to do anyway. The creation does not need
to be part of the distributed package ...
On Thu, Feb 28, 2019 at 11:10 AM Sebastian Becker<EMAIL_ADDRESS>wrote:

Our goal is a coverage rate above the 90% threshold. @peisenha
https://github.com/peisenha: does this also include the coverage rate
of the test directory?
Nevertheless there are still several options for increasing the coverage
rate in the test directory. For instance we could move our regression vault
creation module from test/resources to a new folder in the development
directory (or we could adjust our regression test setup so that it executes
the check function from the same module).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OpenSourceEconomics/soepy/issues/10#issuecomment-468215005,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADcMJ7UdE2b3rzoVHuR0o9Z_JdIdFm5jks5vR6swgaJpZM4bHIbS
.

--
Philipp Eisenhauer
Economist
Mail<EMAIL_ADDRESS>Web www.eisenhauer.io
Repository https://github.com/peisenha


stylish_cmake_parser.parser.CMakeParseException: Expected type "left_paren" but got "1"

While running glint_ros. The error isn't verbose enough to pinpoint what's making it fail so if it's not obvious to you I can build from source and add debugging statements or find out which of my 20+ packages is causing this.
Error on Line 39, Char 35
Traceback (most recent call last):
  File "/home/user/.local/bin/glint_ros", line 8, in <module>
    sys.exit(main())
  File "/home/user/.local/lib/python3.8/site-packages/ros_glint/main.py", line 123, in main
    pkgs = list(find_packages(args.folder))
  File "/home/user/.local/lib/python3.8/site-packages/ros_introspect/package.py", line 270, in find_packages
    yield Package(package_root)
  File "/home/user/.local/lib/python3.8/site-packages/ros_introspect/package.py", line 151, in __init__
    self.add_file(infer_package_file(root / subpath, self))
  File "/home/user/.local/lib/python3.8/site-packages/ros_introspect/package.py", line 129, in infer_package_file
    return subtype(path, package)
  File "/home/user/.local/lib/python3.8/site-packages/ros_introspect/components/cmake.py", line 18, in __init__
    for content in parse_file(self.full_path) or []:
  File "/home/user/.local/lib/python3.8/site-packages/stylish_cmake_parser/__init__.py", line 31, in parse_file
    return parse_commands(s, debug)
  File "/home/user/.local/lib/python3.8/site-packages/stylish_cmake_parser/__init__.py", line 13, in parse_commands
    parser = CMakeParser(s, debug=debug)
  File "/home/user/.local/lib/python3.8/site-packages/stylish_cmake_parser/parser.py", line 71, in __init__
    cmd = self.parse_command()
  File "/home/user/.local/lib/python3.8/site-packages/stylish_cmake_parser/parser.py", line 118, in parse_command
    original += self.match(TokenType.left_paren)
  File "/home/user/.local/lib/python3.8/site-packages/stylish_cmake_parser/parser.py", line 108, in match
    raise CMakeParseException(f'Expected type "{token_type.name}" but got "{self.get_type()}"')
stylish_cmake_parser.parser.CMakeParseException: Expected type "left_paren" but got "1"

The ambiguity of the location of the failure should be resolved with the next release of the library.


Fix spelling & grammar in comments, docs, and messages

Changes look good, could you squash commits into one?
And for reference, did you find those using codespell or a different tool?

Changes look good, could you squash commits into one?

Oh, sure. I thought you would just use GitHub's "Squash & Merge".

And for reference, did you find those using codespell or a different tool?

I did start with codespell. I think all but one spelling mistake was found using it. Of course it doesn't handle the grammar (e.g. amount vs. number).

BTW, in case anyone else wants to join the fun, here's the codespell command I used. It's not as clean as it could be, but it got me most of the way there.
codespell --skip="*.o,./doc/translations/*,./.git/*,*.pyc,*.a,*.png,./thirdparty/*,./editor/translations/*"

BTW, in case anyone else wants to join the fun, here's the codespell command I used. It's not as clean as it could be, but it got me most of the way there.
codespell --skip="*.o,./doc/translations/*,./.git/*,*.pyc,*.a,*.png,./thirdparty/*,./editor/translations/*"

Nice! See also ab3bccdb78cc7dffb6ab796053ef63489f05558d for a list of words to exclude to reduce false positives.

Thanks!

list of words to exclude to reduce false positives.

Neat!
"merchantibility" - I reported that as a bug in the CC license. :-)


commitment_laszlo will actually be signed by us, then sent to laszlo. he will not need to sign it (unless he wants to close the channel) So the "send to laszlo" button, could be "sign and send" and then we wouldnt necessarily expect a green "signed" check next to laszlo.

on https://dev.savingsatoshi.com/en/chapters/chapter-10/making-a-payment-5?dev=true
commitment_laszlo will actually be signed by us, then sent to laszlo. he will not need to sign it (unless he wants to close the channel) So the "send to laszlo" button, could be "sign and send" and then we wouldnt necessarily expect a green "signed" check next to laszlo.

@pinheadmz  Is this also the case on the final challenge for part 1 where you are updating the laszlo state for the second beer?

yes this applies to all commitment_laszlo transactions.
and, asymmetrically, we need leszlo's signature on every commitment_you tx that we hold (and similarly we dont need to sign that unless we are ready to close the channel)


[Add] New method to have a way to initiate a new conversation

Hello @themester, I was trying to send a message to a newly added following contact but encountered that the method that is there right now is part of Conversation object, so the proposal is to use this method as part of Inbox, to start a new conversations with a person that you never messaged before.  Further messages should be sent as part of Conversation object.
All comments are welcome.
Regards.

Can you make this changes:

inbox.go

// New initialises a new conversation with a user, for further messages you should use Conversation.Send
//
// See example: examples/inbox/newconversation.go
func (inbox *Inbox) New(user *User, text string) error {
	insta := inbox.inst
	to, err := prepareRecipients(user.ID)
	if err != nil {
		return err
	}
...

newconversation.go

err = inst.Inbox.New(&user, strings.Join(os.Args[1:], " "))

Hello @themester , changes done. :+1:


Scopes on Recursive Regex Cause Problems

Non-issue example:
Adding scopes to the this capture group (a)+ will only apply the scopes to the last match. While annoying, that behavior is the expected behavior and it's easy enough to work around.
A similar behavior happens with recursion
(a)b\g<1>? this can match ababab but only tags the last a with a scope.
The issue
Let's say (a)\g<1>? is trivial recursion (just repetion)
And (basecase|(\[)\g<1>(\])) is basic recursion (balanced square brackets around the word "basecase")
Anything more complex than those, such as adding alternation, dual-recusion, branching recursion, becomes impossible to reliably highlight.
For illustration, applying a balanced parentheses pattern to [[basecase]] would only add scopes to "basecase". And while there might be a hacky way to color the outside brackets, that hack will fall apart as soon as there's a more complex matcher applied to something like [basecase lambda {basecase[basecase][basecase]}]. Only the last basecase will have scopes. It might only be possible to find "lambda" using a recursive pattern, but by using a recursive pattern we are unable to tag the "lambda", because it only adds scopes to the inner most basecase.
TLDR; this is fundamentally limiting, not just an inconvenience that can be worked around.
Not only is the behavior incredibly unintuitve, but add multiple-recusion (e.g. \g<1>|\g<2>) on top of it and it's debatably undefined behavior.
Rare? Well...
Even hello-world tutorials for defining languages (like a BNF grammar) use recursion like this. When defining a syntax it's easy to define it with this kind of recusion, so it's necessary that this work if those languages are ever going to be correctly parsed by textmate.
Requested solution
There are only a handful of textmate grammars that use complex recusion, and the ones that do almost certainly don't expect this behavior. So changing the scoping behavior shouldn't affect anyone negatively regardless of whether or matches the original textmate implementation.
With that in mind, having the FIRST recursive case be given scopes rather than the last basecase should avoid this problem.

dup:
https://github.com/microsoft/vscode-textmate/issues/127
https://github.com/microsoft/vscode-textmate/issues/164


Adding placeholders for custom NSP vues

Description
Adds placeholder text for NSPs with custom vues
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale

[ ] Major
[x] Minor

Screenshots (if appropriate):
TODO

ping @davidjumani is this ready?

@blueorangutan ui

@davidjumani a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_multiplication_x:
(SL-JID-842)

Hi @davidjumani, Can you address the outstanding comments.

ping @davidjumani please address the outstanding comments. thanks.

@blueorangutan ui

@davidjumani a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5620 (SL-JID-1073)

Verified the placeholder descriptions from the API params.
@davidjumani Can you update the description for the below param in addNetscalerLoadBalancer API.
https://github.com/apache/cloudstack/blob/b9905c7e377bc9c5f5129e7d43be40183a06c052/plugins/network-elements/netscaler/src/main/java/com/cloud/api/commands/AddNetscalerLoadBalancerCmd.java#L86

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_multiplication_x: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 2338

@blueorangutan package

@sureshanaparti a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_multiplication_x: suse15. SL-JID 2345


[Question]: Best way to return full set of image embeddings from index

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
I'm trying to use a MultiModalVectorStoreIndex to build clip image embeddings using a chroma vector store and then return the full set of image embeddings for some downstream tasks. I'm having trouble returning those from the index object though.
This is what I run:
        image_store = ChromaVectorStore(chroma_collection=self.chroma_collection)
        storage_context = StorageContext.from_defaults(
            vector_store=None, image_store=image_store
        )
        index = MultiModalVectorStoreIndex(
            nodes = image_documents,
            embed_model = None,
            image_embed_model = "clip",
            storage_context = storage_context,
            is_text_vector_store_empty=True,
            show_progress = True,
            store_nodes_override = True

        )

And then I try to retrieve through:
       print(index.storage_context.vector_stores['image'].client.get())

When I do this I get back my full document dictionary but the embeddings are all empty. Even though when running I get back the "Generating image embeddings" progress bar. Also when I inspect the image_nodes from MultiModalVectorStoreIndex:_add_nodes_to_index() I can see my embeddings. How can I retrieve everything though (not just a top k)?
Thanks again

I believe image_to_image_retrieve() takes image input, embeds and then retrieves similar embedded images.
What I'm looking for is a way to retrieve all image embeddings -- either through the index or retriever. I could extend class functionality but am wondering if there's a built-in way to do this.
Appreciate the help.

Closing topic, but the issue was that chromadb defaults to only returning the metadata and documents. If you want to return the embeddings, you need to pass this in the include parameter inside get(), like this:
self.db = chromadb.PersistentClient(path=self.index_path)
self.chroma_collection = self.db.get_or_create_collection("image_collection")
image_store = ChromaVectorStore(chroma_collection=self.chroma_collection)
storage_context = StorageContext.from_defaults(
    vector_store=None, image_store=image_store
)
self.index = MultiModalVectorStoreIndex(
    nodes = self.image_documents,
    embed_model = None,
    image_embed_model = "clip",
    storage_context = storage_context,
    is_text_vector_store_empty=True,
    show_progress = True,
    store_nodes_override = True
)
chroma_db_data = self.chroma_collection.get(include=["metadatas", "documents", "embeddings"])


Store timestamps instead of cull time

This way the displayed cull time is always accurate, not just after waiting for hundreds of jalist pages to load.
Copy of https://github.com/MrLittleKitty/Snitch-Master/issues/43

Definitely on the TODO list yea.


Fix another issue with MSAA depth buffer copying during replay with D3D12

Description
I've just found another issue with copying depth on D3D12, similar to the one that was fixed recently.

It looks like your branch hasn't been rebased properly onto v1.x upstream, causing a bit of divergence where I rebased the clang-format commit. I strongly recommend in git having a separate branch for each PR that you fork off my v1.x each time, that will ensure you don't have pollution like this or merge commits.
I've pushed the fix commit manually, with a tweak to the commit message to follow the commit message formatting 72 character limit.

Sorry, I'm not that confident with git, yet. Thanks for fixing this manually!


Install instructions

After Go v1.17 the "go get github.com/digitalocean/pgremapper" install command is deprecated, which means it goes not work in e.g. Rocky Linux 8 using Go from standard repo.
I managed to install by running:
git clone https://github.com/digitalocean/pgremapper
cd pgmapper
go build -o /usr/local/bin

This installed pgremapper in /usr/local/bin
Best, Jesper

Thanks for reporting this! I think the new way is actually go install github.com/digitalocean/pgremapper@latest; I'll make a note to update the docs.


[enhancement]: Suggest inpainting model when incorrect type used

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
No response
What should this feature add?
Input type (c10::Half) and bias type (float) should be the same
This error appears for me when using a regular model like epicrealism_pureEvolutionV5.safetensors on a mask layer of the unified canvas instead of  epicrealism_pureEvolutionV5-inpainting.safetensors, which resolves the issue. It seems reasonable to either restrict the model list or add more information to the error suggesting that a different model be used.
Alternatives
No response
Aditional Content
[2023-08-09 20:26:23,061]::[uvicorn.access]::INFO --> <IP_ADDRESS>:53738 - "POST /api/v1/images/upload?image_category=mask&is_intermediate=true HTTP/1.1" 201
[2023-08-09 20:26:23,075]::[uvicorn.access]::INFO --> <IP_ADDRESS>:53738 - "POST /api/v1/sessions/ HTTP/1.1" 200
[2023-08-09 20:26:23,116]::[uvicorn.access]::INFO --> <IP_ADDRESS>:53738 - "PUT /api/v1/sessions/3a023468-ed1f-4ca9-9727-4a7bf0d62233/invoke?all=true HTTP/1.1" 202
[2023-08-09 20:26:23,135]::[uvicorn.access]::INFO --> <IP_ADDRESS>:53741 - "PATCH /api/v1/images/i/55b0007c-9f89-4382-86f7-6259a25e3b78.png HTTP/1.1" 200
[2023-08-09 20:26:23,141]::[uvicorn.access]::INFO --> <IP_ADDRESS>:53742 - "PATCH /api/v1/images/i/e966b627-589d-425a-a723-7e9bda530abf.png HTTP/1.1" 200
Generating:   0%|                                                                                | 0/1 [00:00<?, ?it/s]You have disabled the safety checker for <class 'diffusers.pipelines.stable_diffusion.pipeline_stable_diffusion_img2img.StableDiffusionImg2ImgPipeline'> by passing `safety_checker=None`. Ensure that you abide to the conditions of the Stable Diffusion license and do not expose unfiltered results in services or applications open to the public. Both the diffusers team and Hugging Face strongly recommend to keep the safety filter enabled in all public facing circumstances, disabling it only for use-cases that involve analyzing network behavior or auditing its results. For more information, please have a look at https://github.com/huggingface/diffusers/pull/254 .
Generating:   0%|                                                                                | 0/1 [00:00<?, ?it/s]
[2023-08-09 20:26:28,043]::[InvokeAI]::ERROR --> Traceback (most recent call last):
  File "/Applications/InvokeAI/.venv/lib/python3.9/site-packages/invokeai/app/services/processor.py", line 90, in __process
    outputs = invocation.invoke(
  File "/Applications/InvokeAI/.venv/lib/python3.9/site-packages/invokeai/app/invocations/generate.py", line 236, in invoke
    generator_output = next(outputs)
  File "/Applications/InvokeAI/.venv/lib/python3.9/site-packages/invokeai/backend/generator/base.py", line 144, in generate
    results = generator.generate(
  File "/Applications/InvokeAI/.venv/lib/python3.9/site-packages/invokeai/backend/generator/base.py", line 328, in generate
    image = make_image(x_T, seed)
  File "/Applications/InvokeAI/.venv/lib/python3.9/site-packages/invokeai/backend/generator/inpaint.py", line 292, in make_image
    pipeline_output = pipeline.inpaint_from_embeddings(
  File "/Applications/InvokeAI/.venv/lib/python3.9/site-packages/invokeai/backend/stable_diffusion/diffusers_pipeline.py", line 826, in inpaint_from_embeddings
    init_image_latents = self.non_noised_latents_from_image(init_image, device=device, dtype=latents_dtype)
  File "/Applications/InvokeAI/.venv/lib/python3.9/site-packages/invokeai/backend/stable_diffusion/diffusers_pipeline.py", line 886, in non_noised_latents_from_image
    init_latent_dist = self.vae.encode(init_image).latent_dist
  File "/Applications/InvokeAI/.venv/lib/python3.9/site-packages/diffusers/utils/accelerate_utils.py", line 46, in wrapper
    return method(self, *args, **kwargs)
  File "/Applications/InvokeAI/.venv/lib/python3.9/site-packages/diffusers/models/autoencoder_kl.py", line 242, in encode
    h = self.encoder(x)
  File "/Applications/InvokeAI/.venv/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/Applications/InvokeAI/.venv/lib/python3.9/site-packages/diffusers/models/vae.py", line 110, in forward
    sample = self.conv_in(sample)
  File "/Applications/InvokeAI/.venv/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/Applications/InvokeAI/.venv/lib/python3.9/site-packages/torch/nn/modules/conv.py", line 463, in forward
    return self._conv_forward(input, self.weight, self.bias)
  File "/Applications/InvokeAI/.venv/lib/python3.9/site-packages/torch/nn/modules/conv.py", line 459, in _conv_forward
    return F.conv2d(input, weight, bias, self.stride,
RuntimeError: Input type (c10::Half) and bias type (float) should be the same

[2023-08-09 20:26:28,047]::[InvokeAI]::ERROR --> Error while invoking:
Input type (c10::Half) and bias type (float) should be the same
[```

@lstein @psychedelicious - I'm seeing this as well on main. Unclear what is causing the issue, but non-inpainting models should be working.
No issues on txt2img.

@lstein - Issue seems to be caused by non-default VAE selection.
https://discord.com/channels/1020123559063990373/1131987080466137219/1138919616157073468


All my forks dissatisfy me

Hi,
I am writing for advice.  As you're aware, I made the cw 44.3 for Juno, based it from the provenance.io verison.  Thing is, I know that if I do this right (TM) I will be able to easily merge in changes from upstream, and that is really critical to me.
So here's what I think the upgrade path should look like:

Fork the master branch of this repository
https://github.com/cosmos/ibc-go/blob/main/docs/migrations/ibc-migration-043.md
https://github.com/cosmos/ibc-go/blob/main/docs/migrations/ibc-migration-v100.md

After that it is cleanup and restructuring.  If you (CW team) have additional advice on this, I'd love it.  I intend to maintain a fork that is as faithful as possible to the original code here that also uses the latest released version of the cosmos-sdk.
In the past week I've tried three different styles for this and to be honest, I'm not happy with any of them.
Cherry picking doesn't lead to clean merges, nor does rebasing.
I basically taught myself git rebase for this, but in the end I had divergent code.  I want a graph that looks like:

See how everything converges there?
That would be very nice.
If there is a strategy to get that, please do let me know.

Hey, this one feels sooooo much better:
https://github.com/notional-labs/wasmd/tree/fourth-try

@alpe , the lead maintainer, is currently busy with finalising the Tgrade binary.
The 0.44 upgrade is our top priority for wasmd, and he should have time to look into this in a week or so.
Lots of people have been pushing code to speed this up, but in the end, his feeling was that many of them were huge and almost more work to review thoroughly than to write.  (A number of external PRs have had bugs he has caught).
I think the best way to move forward is to check with Alex on how he can best be supported. Having some PRs to look at showing what needs to be done is good. Maybe he could benefit from a chat explaining the changes high level? From a review of the final branch he makes? From testing of the result?
I do appreciate that Juno has declared their plans to upgrade on Dec 15th but there was no request from us as to when we can promise this, and I am unsure any 0.44 upgrade will be merged by then, and highly doubtful if it will be fully tested and a 1.0-beta tagged by then.
CosmWasm has long suffered from many chains pushing aggressive release timelines without checking in with us or fully supporting us. This does not make us go faster, and rather distracts us and often makes us slower. (Not signalling out Juno here, it is common)

I think the key decision, and one that will possibly prevent alignment with mainline code, is whether contracts have 20 byte or 32 byte addresses. If this is the same in both forks, you might just be able to jump from one to the other without requiring a complicated migration (but a hard fork/upgrade)

I'm going with 20, and I think that's what 42 uses, correct?
Also, very explicitly, I do not want to push on Tgrade / confio for time/resources, but instead contribute a faithful upgrade.  I totally understand what you mean about the difficulty of reviewing something like this, and one of the reasons that I want a faithful upgrade is so that we can take on bugs together.
Long-run, I am interested in contributing test suites, ARM support, and more.
So, I will continue to make PR's -- I am closing #683 because it is frankly dissatisfactory -- in favor of my branch fourth-try which:

forks directly from wasmd master
uses the ibc-go upgrade guidelines
follows gaia v6 wherever possible (eg: root.go)
has a focus on accuracy and rigorous testing

I'm going to try and keep the whole thing easy-to-merge with the tip of wasmd, so that we can continue to collaborate.
Thanks for your work on wasmd guys.

I'm going with 20, and I think that's what 42 uses, correct?

That is what 42 uses.
Other 44 forks have used 32 byte ones, which was also recommended by SDK devs.
I think this needs to be agreed, mainly on the people who already have 44 ports on mainnet, so we can keep them all aligned.

On Uni testnet, contracts are 32 bytes long
(Public key "external accounts" are 20 bytes everywhere in both 0.42 and 0.44, it affects module accounts)

We (Provenance) would have used 32 (in fact that was how we originally did it on our fork) but at the time this was incompatible with IBC. The cosmoshub at the time did not endorse 0.43/0.44 so we decided we shouldn’t wait for the IBC resolution which the Cosmoshub wouldn’t support anyway.
We expect to migrate to 32 when everything else eventually caught up in a future release.

I think we (osmosis) would have a preference for 32 byte.  @valardragon has concerns about 20 byte address collision resistance.

I'm going with 20, and I think that's what 42 uses, correct?

That is what 42 uses. Other 44 forks have used 32 byte ones, which was also recommended by SDK devs.
I think this needs to be agreed, mainly on the people who already have 44 ports on mainnet, so we can keep them all aligned.

We'll use whatever the consensus here is. Currently using 32, but could easily switch.

I don't think there is a strong reason not to go with 32 (speaking as someone on 20 right now). When I discussed this internally it sounded like there wasn't any reason the 20 byte based addresses would stop working but of course any new loaded code or instantiation would be of the longer form.
We (Provenance) are hoping to see a standard release from cosmwasm with full 0.44+ support including these longer addresses which we already added support for in the rest of our modules.
We expect to have to do some minor work to move off of our fork to this main line and are fine with that.

Ok, 32 it is and thanks to everyone for the discussion here.  I'll update my things.  I also think (gasp) that I might be missing something here.  Replacing the sdk.addrlen's is a little.... vexing.
I'll maybe post some questions here.

There.  Much better!


Change data export

Filename: query name + date executed
Metadata of query on first line of results.

@mhkuu: does KB have a version numbering for the corpus? Would be nice to include that!

Metadata:

query comment
exact query
date executed
filter settings (i.e. distribution, article type, date window)

I'll keep the username in the filename; we could otherwise get conflicting filenames.

@mhkuu Do you have an example of how the title of the file and the first line would look?

Yes, I just downloaded a search named "oxford" (with a very insightful comment) locally:
Filename: tex_oxford_2015.04.17-15.14.22.zip
First two lines of resulting .csv-file:

comment
query
date executed
excluded article types
excluded distributions
date lower
date upper

sdfdsfdsfdsfs
oxford
2015-04-17 15:14:22.999000
[u'st_advert']
[u'sd_antilles']
1878-01-01
1936-05-29

I'll look into the formatting of the date executed and the excluded article types/distributions.

Would it be an idea to add the meta-information at the bottom or in a column instead of a row?
Many programmes expect the first row to contain row information. I now need to first remove this first row to be able to do anything with the files.

Good idea, I moved comment to a new issue: #66.


EXCEPTION_STACK_OVERFLOW in JDK 17.0.1 Windows x86

A fatal error has been detected by the Java Runtime Environment:

EXCEPTION_STACK_OVERFLOW (0xc00000fd) at pc=0x569c1119, pid=21680, tid=22944

JRE version: OpenJDK Runtime Environment Temurin-17.0.1+12 (17.0.1+12) (build 17.0.1+12)
Java VM: OpenJDK Client VM Temurin-17.0.1+12 (17.0.1+12, mixed mode, emulated-client, serial gc, windows-x86)
Problematic frame:
C  [awt.dll+0xd1119]

No core dump will be written. Minidumps are not enabled by default on client versions of Windows

If you would like to submit a bug report, please visit:
https://github.com/adoptium/adoptium-support/issues
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.

---------------  S U M M A R Y ------------
Command Line: -DEDITOR_PARALLEL -XX:+IgnoreUnrecognizedVMOptions --add-modules=ALL-SYSTEM se.entra.phantom.client.Phantom
Host: 11th Gen Intel(R) Core(TM) i9-11900K @ 3.50GHz, 16 cores, 127G,  Windows 10 , 64 bit Build 22000 (10.0.22000.434)
Time: Thu Feb 24 21:05:44 2022 Romance Standard Time elapsed time: 0.414076 seconds (0d 0h 0m 0s)
---------------  T H R E A D  ---------------
Current thread (0x19e47950):  JavaThread "AWT-EventQueue-0" [_thread_in_native, id=22944, stack(0x1e480000,0x1e4d0000)]
Stack: [0x1e480000,0x1e4d0000],  sp=0x1e4cf130,  free space=316k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [awt.dll+0xd1119]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  sun.awt.shell.Win32ShellFolder2.getStandardViewButton0(IZ)[I+0<EMAIL_ADDRESS>j  sun.awt.shell.Win32ShellFolderManager2.getStandardViewButton(I)Ljava/awt/Image;+14<EMAIL_ADDRESS>j  sun.awt.shell.Win32ShellFolderManager2.get(Ljava/lang/String;)Ljava/lang/Object;+661<EMAIL_ADDRESS>j  sun.awt.shell.ShellFolder.get(Ljava/lang/String;)Ljava/lang/Object;+4<EMAIL_ADDRESS>j  com.sun.java.swing.plaf.windows.WindowsLookAndFeel$LazyWindowsIcon.createValue(Ljavax/swing/UIDefaults;)Ljava/lang/Object;+11<EMAIL_ADDRESS>j  se.entra.phantom.client.BasicTweaker.modify(Ljava/lang/Object;Ljava/lang/Object;)V+41
j  se.entra.phantom.client.BasicTweaker.modifyDefaults()V+39
j  se.entra.phantom.client.BasicTweaker.createTweaks()V+11
j  se.entra.phantom.client.WindowsTweaker.createTweaks()V+1
j  se.entra.phantom.client.UIScaler.applyScalingAndTweaks()Lse/entra/phantom/client/UITweaks;+4
j  se.entra.phantom.client.UIScaler.set(Ljavax/swing/LookAndFeel;DZ)Lse/entra/phantom/client/UITweaks;+119
j  se.entra.phantom.client.Plaf.initializeLAF(Ljavax/swing/LookAndFeel;D)Lse/entra/phantom/client/UITweaks;+7
j  se.entra.phantom.client.Phantom.lambda$1(Lse/entra/phantom/client/FontManager;DLjava/lang/String;ZLse/entra/phantom/client/IPhantomFontScaling;[I)V+165
j  se.entra.phantom.client.Phantom$$Lambda$171+0x19604108.run()V+24
j  java.awt.event.InvocationEvent.dispatch()V+11<EMAIL_ADDRESS>j  java.awt.EventQueue.dispatchEventImpl(Ljava/awt/AWTEvent;Ljava/lang/Object;)V+21<EMAIL_ADDRESS>j  java.awt.EventQueue$4.run()Ljava/lang/Void;+32<EMAIL_ADDRESS>j  java.awt.EventQueue$4.run()Ljava/lang/Object;+1<EMAIL_ADDRESS>J 1222 c1 java.security.AccessController.doPrivileged(Ljava/security/PrivilegedAction;Ljava/security/AccessControlContext;)Ljava/lang/Object<EMAIL_ADDRESS>(17 bytes) @ 0x03213dcc [0x03213d80+0x0000004c]
j  java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Ljava/security/PrivilegedAction;Ljava/security/AccessControlContext;Ljava/security/AccessControlContext;)Ljava/lang/Object;+18<EMAIL_ADDRESS>j  java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V+46<EMAIL_ADDRESS>j  java.awt.EventDispatchThread.pumpOneEventForFilters(I)V+78<EMAIL_ADDRESS>j  java.awt.EventDispatchThread.pumpEventsForFilter(ILjava/awt/Conditional;Ljava/awt/EventFilter;)V+35<EMAIL_ADDRESS>j  java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V+11<EMAIL_ADDRESS>j  java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4<EMAIL_ADDRESS>j  java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V+3<EMAIL_ADDRESS>j  java.awt.EventDispatchThread.run()V+9<EMAIL_ADDRESS>v  ~StubRoutines::call_stub
siginfo: EXCEPTION_STACK_OVERFLOW (0xc00000fd), ExceptionInformation=0x00000000 0x1e480000
See attached log file(s) for complete info.
hs_err_pid21680.log
hs_err_pid12764.log
hs_err_pid13452.log

Adding command line parameter -Xss1m makes it work fine...

Did you try 17.0.2?

A silly question: only 17.0.1 is available on Windows x86, not 17.0.2, otherwise I would have tried it out.
Sent from my iPhone
On 25 Feb 2022, at 18:15, Martijn Verburg @.***> wrote:

Did you try 17.0.2?
—
Reply to this email directly, view it on GitHubhttps://github.com/adoptium/adoptium-support/issues/461#issuecomment-1051038677, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGXD5VROIMXRHPRLDN74VRTU462I7ANCNFSM5PITCNVQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>

Win32 17.0.2 was just released on Friday Feb 25th (and is available at: https://adoptium.net/releases.html) if you want to try it.

That should be released now - if not I’ll follow up on the pipeline
tomorrow
On Sun, 27 Feb 2022 at 17:15, Christopher Mindus @.***>
wrote:

A silly question: only 17.0.1 is available on Windows x86, not 17.0.2,
otherwise I would have tried it out.
Sent from my iPhone
On 25 Feb 2022, at 18:15, Martijn Verburg @.***> wrote:

Did you try 17.0.2?
—
Reply to this email directly, view it on GitHub<
https://github.com/adoptium/adoptium-support/issues/461#issuecomment-1051038677>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/AGXD5VROIMXRHPRLDN74VRTU462I7ANCNFSM5PITCNVQ>.
Triage notifications on the go with GitHub Mobile for iOS<
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android<
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
@.***>
—
Reply to this email directly, view it on GitHub
https://github.com/adoptium/adoptium-support/issues/461#issuecomment-1053619669,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABME2FJ7KHDUAOXCXD7UOLU5JL2ZANCNFSM5PITCNVQ
.
You are receiving this because you commented.Message ID:
@.***>

--
Cheers, Martijn (Sent from Gmail Mobile)

Same problem, uploaded new "hs_err_pid*.log".
hs_err_pid10412.log

The same problem exists JDK Windows 32-bit x86 17.0.0.
It is not seen in 64-bit versions, not under Mac/Linux, no matter the architecture of the CPU.

The workaround for this problem in JDK 17.0.0, 17.0.1, 17.0.2 for Windows x86 is to add the parameter -Xss1m.
The problem seems to be resolved in JDK 17.0.3.


[FP]: jakartaee-migration-1.0.0-shaded.jar version is matching a number of old/resolved vulnerabilities

Package URl
<EMAIL_ADDRESS>CPE
cpe:2.3:a:apache:tomcat:1.0.0:::::::*
CVE
No response
ODC Integration
{"label"=>"CLI"}
ODC Version
7.1.0
Description
Moving to the apache-tomcat 10.0.21 package, dependency check is reporting 20 CVEs against the jakartaee-migration-1.0.0-shaded.jar.
Most (all?) of these appear to be old/resolveld CVEs in pre 10.x releases.
Thanks.

hmm... cpe should read:
cpe:2.3:a:apache:tomcat:1.0.0:*:*:*:*:*:*:*


Zod schema generated based on OpenAPI containing anyOf keyword doesn't work correctly - consider using .strict on every schema passed to z.union

What version of kubb is running?
kubb/2.5.2 darwin-arm64 node-v18.17.0
What platform is your computer?
MacOS
What version of external packages are you using(@tanstack-query, MSW, React, Vue, ...)
No response
What steps can reproduce the bug?
Currently, when OpenAPI schema uses anyOf, like on the attached schema below, kubb generates schema with z.union function to map it. The result code is:
const schema = z.union([
  z.object({ propertyA: z.string() }),
  z.object({ propertyA: z.string(), propertyB: z.string() }),
])

If we use this schema on an object with both properties, the result will have only propertyA.
const result = schema.parse({ propertyA: 'abc', propertyB: 'def' }); // { propertyA: 'abc' }

How often does this bug happen?
Every time
What is the expected behavior?
The generated zod schema should return correctly parsed object. Possible solution for that is to add .strict() modifier to all schemas inside union
const schema = z.union([
  z.object({ propertyA: z.string() }).strict(),
  z.object({ propertyA: z.string(), propertyB: z.string() }).strict(),
]);
const result = schema.parse({ propertyA: 'abc', propertyB: 'def' }); // { propertyA: 'abc', propertyB: 'def' }

Swagger/OpenAPI file?
{
  "openapi": "3.0.0",
  "paths": {
    "/api/test": {
      "post": {
        "operationId": "Test",
        "responses": {
          "200": {
            "description": "Success",
            "content": {
              "application/json": {
                "schema": {
                  "anyOf": [
                    {
                      "type": "object",
                      "properties": { "propertyA": { "type": "string" } },
                      "required": ["propertyA"]
                    },
                    {
                      "type": "object",
                      "properties": {
                        "propertyA": { "type": "string" },
                        "propertyB": { "type": "string" }
                      },
                      "required": ["propertyA", "propertyB"]
                    }
                  ]
                }
              }
            }
          }
        }
      }
    }
  },
  "info": {
    "title": "Test",
    "description": "Test",
    "version": "0.0.0"
  }
}

Additional information
No response

@stijnvanhulle, should be easy fix, I guess. Solution proposed by @marcin992 looks legit and correct. What do you think?

@kopach Aha another edge case, I will open a PR to fix this. Seems indeed an easy one :)

thank you @stijnvanhulle