Is there a hooks could create actor ?

Do you mean canister?
There is:
https://connect2ic.github.io/docs/docs/React/hooks#usecanister
It abstracts all details away of how the canister is created, since every wallet does it differently.

Do you mean canister? There is: https://connect2ic.github.io/docs/docs/React/hooks#usecanister
It abstracts all details away of how the canister is created, since every wallet does it differently.

Using the canister method should knowing canisterId, but the canisterId may be unknown, maybe store on ic.Therefore, I think export the createActor method just like Plug extension is a better way.

Do you mean canister? There is: https://connect2ic.github.io/docs/docs/React/hooks#usecanister
It abstracts all details away of how the canister is created, since every wallet does it differently.

Using the canister method should knowing canisterId, but the canisterId may be unknown, maybe store on ic.Therefore, I think export the createActor method just like Plug extension is a better way.

So you want to use mainnet canisters is that correct? I have an issue open for that https://github.com/Connect2IC/connect2ic/issues/5
It seems like something worth supporting for sure. And yeah would also like to make it able to handle dynamic canisterIds where its not known beforehand. Will have to think about it however what the API should look like. Im not sure exposing the createActor is the way to go.

Yeah, i want to handle the dynamic canisterIds. Thanks for your support, please let me know when you finished it.

Yeah, i want to handle the dynamic canisterIds. Thanks for your support, please let me know when you finished it.

In the meantime, you could do:
const {activeProvider} = useConnect()

activeProvider.connector.createActor(canisterId, idlFactory)

Yeah, i want to handle the dynamic canisterIds. Thanks for your support, please let me know when you finished it.

In the meantime, you could do:
const {activeProvider} = useConnect()

const actor = await activeProvider.connector.createActor(canisterId, idlFactory)

Thanks.

Yeah, i want to handle the dynamic canisterIds. Thanks for your support, please let me know when you finished it.

In the meantime, you could do:
const {activeProvider} = useConnect()

const actor = await activeProvider.connector.createActor(canisterId, idlFactory)

Sorry for reopen it.
Is there any way to get this actor by function method, not hooks

Yeah, i want to handle the dynamic canisterIds. Thanks for your support, please let me know when you finished it.

In the meantime, you could do:
const {activeProvider} = useConnect()

const actor = await activeProvider.connector.createActor(canisterId, idlFactory)

Sorry for reopen it. Is there any way to get this actor by function method, not hooks

I  think the best way to use them as function method meanwhile using custom canister, is to wrap the function with connector.

async function createActorFromConnector<T>(connector, canisterId, idlFactory):Promise<ActorSubClass<T>>{
       // ...
}

and return Actor somehow

For now, all i know how to get the "connector" is use the useConnect hooks.But it's seems to be hard for me to use hooks, because of the older code's logic

For now, all i know how to get the "connector" is use the useConnect hooks.But it's seems to be hard for me to use hooks, because of the older code's logic

We can also consider wrapping window API for future version.

For now, all i know how to get the "connector" is use the useConnect hooks.But it's seems to be hard for me to use hooks, because of the older code's logic

Yes I will probably expose the "client" in the future so it can be used outside

For now, all i know how to get the "connector" is use the useConnect hooks.But it's seems to be hard for me to use hooks, because of the older code's logic

Hey there, check out latest version 0.1.0. The client is now exposed
So there's no need to use hooks https://connect2ic.github.io/docs/docs/Core/Client


Make Read/Write File not modify sent options object

This PR makes it so that we don't modify the options object sent to the readFile() and writeFile() methods which can cause unexpected consequences if the object is re-used.

This was found as part of looking into #37

:+1:


NestedScopeFunctions false positive on Gradle's Property<T>.set

Steps to Reproduce
// Needs `implementation(gradleApi())` and `kotlin-dsl` plugin to compile.
import org.gradle.api.publish.maven.MavenPublication

fun MavenPublication.setupLinks(project: Project) {
	pom {
		url.set("https://github.com/detekt/detekt")
		scm {
			connection.set("scm:git:github.com/detekt/detekt.git") // 120
			developerConnection.set("scm:git:ssh://github.com/detekt/detekt.git") // 121
			url.set("https://github.com/detekt/detekt/tree/main") // 122
		}
		licenses {
			license { // 125
				name.set("Apache License 2.0") // 126
				url.set("https://github.com/detekt/detekt/blob/v${project.version}/LICENCE") // 127
			}
		}
	}
}

Observed Behavior
...\PublishingPlugin.kt:120:15: The scope function 'set' is nested too deeply ('2'). Complexity threshold is set to '1'. [NestedScopeFunctions]
...\PublishingPlugin.kt:121:24: The scope function 'set' is nested too deeply ('2'). Complexity threshold is set to '1'. [NestedScopeFunctions]
...\PublishingPlugin.kt:122:8: The scope function 'set' is nested too deeply ('2'). Complexity threshold is set to '1'. [NestedScopeFunctions]
...\PublishingPlugin.kt:125:4: The scope function 'license' is nested too deeply ('2'). Complexity threshold is set to '1'. [NestedScopeFunctions]
...\PublishingPlugin.kt:126:10: The scope function 'set' is nested too deeply ('3'). Complexity threshold is set to '1'. [NestedScopeFunctions]
...\PublishingPlugin.kt:127:9: The scope function 'set' is nested too deeply ('3'). Complexity threshold is set to '1'. [NestedScopeFunctions]

Expected Behavior
set should definitely not be flagged, as it's not a scoped function, it's just a function call on an object.
The license flag might be valid, although this is just how DSLs work in general. In this issue let's focus on set.
Context
This code is in a module in my build logic in PublishingPlugin.kt.
Your Environment

Version of detekt used: 1.21.0
Version of Gradle used (if applicable): 7.5.1
Link to your project (if it's a public repository): https://github.com/TWiStErRob/net.twisterrob.gradle/blob/d9e553b2e0896a7168e118284b6fd70a240987d4/gradle/plugins/src/main/kotlin/net/twisterrob/gradle/build/PublishingPlugin.kt#L116-L138
Running detektMain so type resolution is on.

A little bit of investigation:
When not using `kotlin-dsl` it doesn't report this problem
import org.gradle.api.publish.maven.MavenPublication

fun MavenPublication.setupLinks(project: Project) {
	pom {
		it.url.set("https://github.com/detekt/detekt")
		it.scm {
			it.connection.set("scm:git:github.com/detekt/detekt.git") // 120
			it.developerConnection.set("scm:git:ssh://github.com/detekt/detekt.git") // 121
			it.url.set("https://github.com/detekt/detekt/tree/main") // 122
		}
		it.licenses {
			it.license { // 125
				it.name.set("Apache License 2.0") // 126
				it.url.set("https://github.com/detekt/detekt/blob/v${project.version}/LICENCE") // 127
			}
		}
	}
}

When trying to reproduce in pure Kotlin, it doesn't report this problem
fun MavenPublication.setupLinks() {
	pom {
		url.set("https://github.com/detekt/detekt")
		scm {
			connection.set("scm:git:github.com/detekt/detekt.git") // 120
			developerConnection.set("scm:git:ssh://github.com/detekt/detekt.git") // 121
			url.set("https://github.com/detekt/detekt/tree/main") // 122
		}
		licenses {
			license { // 125
				name.set("Apache License 2.0") // 126
				url.set("https://github.com/detekt/detekt/blob/main/LICENCE") // 127
			}
		}
	}
}

interface Provider<T> {
	fun get(): T
	fun getOrNull(): T?
}

interface Property<T> : Provider<T> {
	fun set(value: T)
	fun set(provider: Provider<T>)
}

interface MavenPublication {
	val pom: MavenPom
	fun pom(configure: MavenPom.() -> Unit)
}

interface MavenPom {
	val url: Property<String>
	fun scm(action: MavenPomScm.() -> Unit)
	fun licenses(action: MavenPomLicenseSpec.() -> Unit)
}

interface MavenPomScm {
	val connection: Property<String>
	val developerConnection: Property<String>
	val url: Property<String>
}

interface MavenPomLicenseSpec {
	fun license(action: MavenPomLicense.() -> Unit)
}

interface MavenPomLicense {
	val name: Property<String>
	val url: Property<String>
}

When trying to reproduce with Java API, I laughably failed to realize there's no receiver there while doing Kotlin -> Java conversion.
interface Provider<T> {
	T get();
	@Nullable T getOrNull();
}

interface Property<T> extends Provider<T> {
	void set(T value);
	void set(Provider<T> provider);
}

interface MavenPublication {
	MavenPom getPom();
	void pom(configure: MavenPom.() -> Unit)
}

interface MavenPom {
	Property<String> getUrl();
	void scm(action: MavenPomScm.() -> Unit)
	void licenses(action: MavenPomLicenseSpec.() -> Unit)
}

interface MavenPomScm {
	Property<String> getConnection();
	Property<String> getDeveloperConnection();
	Property<String> getUrl();
}

interface MavenPomLicenseSpec {
	void license(action: MavenPomLicense.() -> Unit)
}

interface MavenPomLicense {
	Property<String> getName();
	Property<String> getUrl();
}

I think this is a black magic that the kotlin-dsl does that goes beyond what detekt should do. If a fix is provided in a PR will could review it but otherwise this is a "won't fix".

The black magic that kotlin-dsl does is apply 2 or 3 compiler plugins, so this is a general issue. Right now it's only because it transforms Action<T> { it: T -> } to { this: T -> }, but there are plans to transform property = value to property.set(value) for simpler-looking lazy configuration in gradle.kts.
@3flex do you have any idea what would it take to apply compiler plugins along with type resolution, or if this is out of the question; maybe using the detekt compiler plugin would "see" those kotlin-dsl transformations?

I think we should forget adding support for analysing code after a third party compiler plugin is applied in the standalone version of detekt. Possibly our compiler plugin will support it, but it may not be feasible - I have no idea :/


[AVM Question/Feedback]: Hard-coded expiry time of host pool registration token

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Description
Hello,
Just wanted to check why is the expiration_date for azurerm_virtual_desktop_host_pool_registration_info hardcoded to 48h? As far as I know the maximum lifetime of the registration token is ~ 30 days.
The question is, any specific reason why the value is not user customizable? Thanks a lot.
LINK: https://github.com/Azure/terraform-azurerm-avm-res-desktopvirtualization-hostpool/blob/2e66e67845b1698531aeef683ed7dc2e60f0a1c5/main.tf#L52C3-L52C48

@lineardraft Thank you for the question! There is no specific reason, you are correct "The expiration period must be a valid duration less than or equal to 30 days."


Fix for the samsung S20

I noticed that rear camera are listed at the end, so sourceId is now getting latest id in the devices list.
Tested on samsugn S20, J20, umidigi one pro, opera desktop.
https://github.com/code-kotis/qr-code-scanner/issues/92

@redochka Thanks for the PR 👍


[table] keyboard navigation not working on row actions

Describe the bug
Keyboard navigation not working on row actions, the overflow menu is not visible when using tab and hitting space to open results in a menu that you cant navigate.
To Reproduce

Tab to a row, the focus state of the overflow menu isn't visible.
Hit space it opens the overflow menu
With it open, I can't get into the overflow menu to select edit/delete/etc.

Expected behavior
Same behaviour as in Carbon?

Not sure when this functionality broke. It looks like it happened in stages. I went as far back as start of jan 2020 to check but even at that time it was not possible to navigate or select the row action overflow menu items using the keyboard.

:tada: This issue has been resolved in version 2.79.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


goreportcard not showing the grade for repo after new commits

I wanted to check the report of my repo and it worked fine the first time. When I tried to check it again after some new commits to the repo, it seems like it is still showing the results for the previous version of the repo. Can someone please help me on this?

@DarthSett could you please link to the repo?


[BEAM-5660] Add both dataflow legacy worker and fn-api worker into JavaPreCommit

R: @markflyhigh, @herohde

Re @herohde, I don't think they are related. All failures are url 404 not found. Filed JIRA: https://issues.apache.org/jira/browse/BEAM-5691


Add bare bone APIs for observation and event

This PR aims to finalize the naming of Python API for observation and event.

Do we want this as py-only API or REST API first?


TOC Candidate Nomination for Beyhan Veli

Candidate Name: Beyhan Veli
Candidate GitHub Username: @beyhan
Affiliation: SAP SE
Nomination Statement:
I have been active in the Cloud Foundry community for the past 9+ years supporting the Foundational Infrastructure WG, as TOC member and as CF user who brings new requirements to the CF platform derived from SAP use cases. If re-elected I would like to continue contributing to the CF platform evolution and support the CFF community.

Closing because elections are over.


The links to the AZ CLI and Powershell pages are the other way around

The CLI page leads to the Powershell page, and the Powershell link leads to the CLI page.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5d651422-3de2-d399-d863-030abc4ce6ed
Version Independent ID: a46bd7ed-cb90-7a85-63bc-d079ae78d9b6
Content: Reacting to Azure Blob storage events
Content Source: articles/storage/blobs/storage-blob-event-overview.md
Service: storage
Sub-service: blobs
GitHub Login: @cbrooksmsft
Microsoft Alias: cbrooks

@lokijota Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

#reassign: @normesta

Thank you for reporting the issue. The article has been fixed and the updated content should appear live shortly.

#please-close


Add the generate function to allow for custom pre-processing and post-processing.

Is your feature request related to a problem? Please describe.
Context: https://github.com/pdfme/pdfme/pull/389#discussion_r1435784763

idea
const inputs = [
  { headline: { name: "han-dot", favoriteColor: "blue" }, address: "aa-aa-a" },
];

const template = {
  schemas: [
    {
      headline: {
        type: "text",
        position: { x: 4.69, y: 7.15 },
        width: 186.51,
        height: 41.98,
        rotate: 0,
        opacity: 1,
        fontSize: 36,
        fontColor: "#14b351",
        fontName: "NotoSerifJP-Regular",
        readOnly: true,
        readOnlyValue: "Hi {name}, Your favorite color is {favoriteColor}",
      },
      address: {
        type: "text",
        position: { x: 4.69, y: 7.15 },
        width: 186.51,
        height: 41.98,
        rotate: 0,
        opacity: 1,
        fontSize: 36,
        fontColor: "#14b351",
        fontName: "NotoSerifJP-Regular",
      },
    },
  ],
  basePdf: "base64pdf...",
};

const pdf = await generate({
  inputs,
  template,
  options: {
    preprocessing: ({ inputs, template }) => {
      const newInputs = inputs.map((input) => {
        const newInput = {};
        Object.keys(input).forEach((key) => {
          const value = input[key];
          if (typeof value === "object") {
            const schemaIndex = template.schemas.findIndex(
              (schema) => schema[key]
            );
            const schema = template.schemas[schemaIndex][key];
            const { readOnlyValue } = schema;
            newInput[key] = readOnlyValue.replace(
              /{([^}]+)}/g,
              (_, key) => value[key]
            );
          } else {
            newInput[key] = key;
          }
        });
        return newInput;
      });
      return { inputs: newInputs, template };
    },
  },
});

Using post-processing, it would be possible to add digital signatures.
Describe the solution you'd like
Add the generate function to allow for custom pre-processing and post-processing.
Describe alternatives you've considered

pre-processing: Process inputs before passing them to the generate function.
post-processing: None.

Additional context
No response

Ref: https://discord.com/channels/933602537808990268/933602537808990271/1268136157087006761

This process could enable the following types of operations:

Encryption: https://medium.com/aia-sg-techblog/implementing-encryption-feature-in-pdf-lib-112091bce9af
Digital Signature: https://github.com/vbuch/node-signpdf
Convert in PDF/A: https://github.com/Hopding/pdf-lib/issues/1183#issuecomment-1685078941


Bump the emailaddress package version.

Bumping the emailaddress package version makes it so we don't have to use
the PackageImports language pragma anymore.

This is a simple PR so I'm going to go ahead and merge it in.


second query string is misinterpreted

This works:
http://localhost:3000?url=https://example.org?t=12
But this doesn't:
http://localhost:3000?url=https://example.org?t=12&v=15

Finally it was indeed working as intented.
Example code:
const express = require('express')
const app = express()
const port = 3001

app.get('/', (req, res) => {
  res.send('Hello World!')
  console.log(req.query);
})

app.listen(port, () => {
  console.log(`Example app listening at http://localhost:${port}`)
})

Test command: `curl "http://localhost:3000?url=http://localhost:3001?t=12&v=15"


Rename question and action attributes

This is a quick PR to tidy up keys in the YAML to prevent stutter and remove extra logic to deal with irregular mapping to object attributes.

Yaaas! Just to check: we're updating the spreadsheet so the columns match the new CSV fixture?

Yup - I'll do the update as soon as this gets merged! :)


Load counter values on startup

When metricsd starts up, it should load current counter values from carbon (Graphite).

As of 0.9.9, carbon only speaks pickle, so the JVM needs to generate requests appropriately.  pyrolite contains a pickle implementation for Java and appears to be compatible.


get_token should put Response headers and status in the AccessToken object

It would be very useful for debugging to have the Response.header and Response.status parameters merged into the returned AccessToken object as there's no way to bubble that full Response object up when calling the get_token method.

In addition to debugging, I've run into a situation where the response contains a header value that is necessary for further requests.


Is Windows 10 IoT Enterprise 2019 LTSC released?

In this document is the future used for the LTSC release:

The Fall 2018 release of Windows 10 IoT Enterprise will also be an LTSC release.

Windows 10 Enterprise LTSC 2019 is released: https://docs.microsoft.com/en-us/windows/whats-new/ltsc/#the-long-term-servicing-channel-ltsc
Is Windows 10 IoT Enterprise 2019 LTSC also released and this documentation not updated?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a1e7dc7e-3df6-2eaf-9c11-ed03c00719e0
Version Independent ID: ab5e43cf-c4db-cd8f-e92a-c33e4ebc2b68
Content: Overview of Windows 10 IoT Enterprise - Windows IoT
Content Source: windows-iotcore/windows-iot-enterprise.md
Product: windows-iot
Technology: iot
GitHub Login: @saraclay
Microsoft Alias: saclayt

You are correct. I've just updated this. Thank you for filing an issue!


Implement pool snapshot

Will be usefull in graphs/statistics

We're not using Bal v2 in the first release of Ocean V4.
Therefore: is this issue still relevant, or should we close?

It is, it's not related to to balancer v2 pools , it's related to the subgraph implementation of balancer v2 (this is where i got my inspiration). Changed the title so it's not  confusing. Already have a working draft working for it. Don't want to implement it in v3 because it won't be of much value without other changes in the market and at this we want to freeze the market.

thx for the clarification! :)

deprecated by https://github.com/oceanprotocol/ocean-subgraph/issues/208


chore(deps): update dependency @sentry/cli to v1.52.3

This PR contains the following updates:

Package
Type
Update
Change

@sentry/cli (source)
devDependencies
patch
1.52.1 -> 1.52.3

Release Notes

getsentry/sentry-cli
v1.52.3
Compare Source

fix: Correctly store child process before attaching handlers (#718)

v1.52.2
Compare Source
This release sets node.engine: >=8 which makes it incompatible with Node v6
If you need to support Node v6, please pin your dependency to 1.52.1
or use selective version resolution: https://classic.yarnpkg.com/en/docs/selective-version-resolutions/

feat: Support Google Cloud Builder VCS detection (#481)
fix: Mark files as unusable withid (#709)

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

removing sentry!

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (1.52.3). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


Failed to run Benchmark

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): CentOS7.6
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): Source
TensorFlow version (use command below): Latest Master 203f9256a596170151e4ddc93aeda6ed2905e8e7
Python version:
Bazel version (if compiling from source): 3.1
GCC/Compiler version (if compiling from source): 10.2
CUDA/cuDNN version:
GPU model and memory:

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
There is no output of benchmark
bazel --output_user_root=$build_dir run --copt=-O3 //tensorflow/core/kernels/image:non_max_suppression_op_benchmark_test -- --benchmarks=../

Describe the expected behavior
It should output the performance data of unit test.
Isolate to this Commit: https://github.com/tensorflow/tensorflow/commit/29bb0deb26db7179eefc87e750fd8755b2c9def3 which enables the new benchmark feature.

Is there any document about this new benchmark? Looking into the source code, it confuse me. Since the https://github.com/tensorflow/tensorflow/blob/c70e89e48a87fb76698beefcd9d7588b6f53c97f/tensorflow/core/platform/default/test_benchmark.cc#L55-L62 will set no args. But the benchmark do needs args to trigger the testinghttps://github.com/tensorflow/tensorflow/blob/c70e89e48a87fb76698beefcd9d7588b6f53c97f/tensorflow/core/platform/default/test_benchmark.cc#L159-L228.
I think that's why there is no output of the benchmark results.

https://github.com/tensorflow/tensorflow/commit/bba12d0401800fbf873ea35f34517a8c47a54272 should have fixed the issue


Replace ordered_set with dict

Summary of changes
This is a follow up of the discussion on https://github.com/pypa/setuptools/pull/4457#pullrequestreview-2163619857.
Since Python 3.7, dict preserve insertion order.
This means that dict is a capable implementation of an ordered set,
despite the method names not lining up completely.
We can effectively use dict to obtain the same functionality that would be implemented by ordered_set and therefore we can remove the extra dependency.
Closes
Pull Request Checklist

[ ] Changes have tests
[ ] News fragment added in newsfragments/.
(See documentation for details)

Optionally, we could have something like
# setuptools/_ordered_set.py

from collections.abc import MutableSet

class ordered_set(dict, MutableSet):
    add = dict.setdefault

    def discard(self, item):
        self.pop(item, None)

But that would be mostly cosmetic, since we can simply use the dict methods directly and obtain the same effects...

Searching for "ordered" in python files, there's still a few bits of logic that still assume dicts are unordered. It's getting late here, but I could open a PR in parallel with yours with all those I found.


Add a shortcut for /storage

to merge before https://github.com/prometheus/prometheus/pull/7691
Signed-off-by: Julien Pivotto<EMAIL_ADDRESS>

Should this go to /nfs or even /go/nfs?

Should this go to /nfs or even /go/nfs?

While now it is for NFS it could be extended in the future, WDYT? I have no strong opinion about the /go part.

I don't think we should start creating a redirect farm, let's just link to the doc page directly.

It is short. If an operator sees this on a vnc or bmc, without copy/paste, they can quickly type the link in a browser.
I also anticipate that we would need a redirect anyway when the docs would move and need a redirect. As people use old version of prometheus, that link will be around for a long time.

As-is searching for "prometheus nfs" will find it, I don't feel we should be over-thinking this.


Does not work with custom titlebar (appWindow.close)

When I close the app with appWindow.close and reopen the app, the window position is not preserved.
It seems that closing app with appWindow.close does not trigger a CloseRequested event, so the state is not read.
If I close the window with system titlebar and reopen the app, the window position is preserved. So I can confirm it's about appWindow.close.

I am using pnpm as package manager and tauri info seems not happy with it:
 app:spawn Running "D:\Desktop\Program\Repo\taulock\node_modules\.pnpm\@tauri-apps+cli<EMAIL_ADDRESS>tauri info" +0ms

Operating System - Windows, version 10.0.22000 X64
Webview2 - 94.0.992.31

Node.js environment
  Node.js - 14.16.1
  @tauri-apps/cli - 1.0.0-beta.10
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error("unexpected character 't' while parsing major version number")', src\info.rs:323:53
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
  @tauri-apps/api - tauri-apps
 app:spawn Command "D:\Desktop\Program\Repo\taulock\node_modules\.pnpm\@tauri-apps+cli<EMAIL_ADDRESS>failed with exit code: 101 +1ms

And part of package.json:
"@tauri-apps/cli": "^1.0.0-beta.10",
"@tauri-apps/api": "^1.0.0-beta.8",

Cargo.toml:
[build-dependencies]
tauri-build = { version = "1.0.0-beta.3" }

[dependencies]
serde_json = "1.0"
serde = { version = "1.0", features = ["derive"] }
# tauri = { version = "1.0.0-beta.8", features = ["window-all"] }
[dependencies.tauri]
git = "https://github.com/tauri-apps/tauri/"
branch = "next"
features = ["window-all"]
[dependencies.tauri-plugin-window-state]
git = "https://github.com/tauri-apps/tauri-plugin-window-state"
branch = "dev"


Fix: no automatic foreign keys referencing partitions

When using atlas migrate diff and the schema contains partitioned tables the autogenerated migration sometimes contains duplicate foreign key constraints. It happens when there is a foreign key in DB schema that references a partitioned table. In this case the foreign key search sql filters tables by the source table of the FK only, But we have to filter also by the target table, because if we don't the query also gives us all the partitions of tha partitioned table aprat from the partitioned table itself.
I've faced this situation using Postgres. My fix adds checks and some query formatting.

Thanks for the contribution, @s-sokolko.
However, I won’t merge this as it conflicts with our current work on supporting partitions (which should be released soon). I appreciate your effort.


AppendQuery breaks the encoded query

Issue summary
AppendQuery breaks the encoded query after manipulation
System informations
(In case of a bug report Please complete the table below)

Information
Description

league uri manipulations version

PHP/HHVM version

OS Platform

Standalone code, or other way to reproduce the problem
$uri = Http::createFromString("https://www.domain.com/?url=https%3A%2F%2Fm.domain.com%2F%3Fresult%3Dtrue");
$modifier = new AppendQuery("newquery=hi");
$newUri = $modifier->process($uri);
var_dump($newUri);

Expected result
object(League\Uri\Schemes\Http)#29 (9) {
  ["scheme":protected]=>
  string(5) "https"
  ["user_info":protected]=>
  NULL
  ["host":protected]=>
  string(14) "www.domain.com"
  ["port":protected]=>
  NULL
  ["authority":protected]=>
  string(14) "www.domain.com"
  ["path":protected]=>
  string(1) "/"
  ["query":protected]=>
  string(49) "url=https%3A%2F%2Fm.domain.com%2F%3Fresult%3Dtrue&newquery=hi"
  ["fragment":protected]=>
  NULL
  ["uri":protected]=>
  NULL
}

Actual result
object(League\Uri\Schemes\Http)#29 (9) {
  ["scheme":protected]=>
  string(5) "https"
  ["user_info":protected]=>
  NULL
  ["host":protected]=>
  string(14) "www.domain.com"
  ["port":protected]=>
  NULL
  ["authority":protected]=>
  string(14) "www.domain.com"
  ["path":protected]=>
  string(1) "/"
  ["query":protected]=>
  string(49) "url=https://m.domain.com/?result=true&newquery=hi"
  ["fragment":protected]=>
  NULL
  ["uri":protected]=>
  NULL
}

@shtse8
This is expected behavior all outputting methods remove double encoding where it is not needed. This is per RFC3986 rules.

That's wried. The result url will become:
https://www.domain.com/?url=https://m.domain.com/?result=true&newquery=hi

Reference from RFC3986
  Under normal circumstances, the only time when octets within a URI
   are percent-encoded is during the process of producing the URI from
   its component parts.

It seems the _toString producing the URI without encoding.

Not at all, you are over encoding your query string here's a better example. I've added 'foo=bar' in your  original URL encoded. Only the ampersand really needs to be encoded. The other characters are not required to be encoded
<?php

$uri = Http::createFromString("https://www.domain.com/?url=https%3A%2F%2Fm.domain.com%2F%3Fresult%3Dtrue%26foo%3Dbar");
$modifier = new AppendQuery("newquery=hi");
$newUri = $modifier->process($uri);
echo $uri; //'https://www.domain.com/?url=https%3A%2F%2Fm.domain.com%2F%3Fresult%3Dtrue%26foo%3Dbar'
echo $newUri; //'https://www.domain.com/?url=https://m.domain.com/?result=true%26foo=bar&newquery=hi'

Understand. You are right. I got it now.


Azure DevOps InstallAppleCertificate Fails with OpenSSL Flag -legacy on macOS Agent

The InstallAppleCertificate task in Azure DevOps is failing on macOS agents when attempting to parse a valid .p12 certificate. The failure occurs during the OpenSSL command execution with the following error:
pkcs12: Unrecognized flag nodes -legacy pkcs12: Use -help for summary. unable to load certificate<PHONE_NUMBER>01536:error:0909006C:PEM routines:get_name:no start line:crypto/pem/pem_lib.c:745:Expecting: TRUSTED CERTIFICATE
Steps to Reproduce
Set up an Azure DevOps pipeline using the InstallAppleCertificate task.
Use a valid .p12 certificate file (tested locally and verified to be working).
Add the opensslPkcsArgs: '-legacy' argument to the task to ensure compatibility with legacy certificates.
Run the pipeline on a macOS agent (macOS-15 or macOS-14).
Expected Behavior
The .p12 certificate should be parsed successfully, and the certificate should install without errors.
Actual Behavior
The task fails with the error:
pkcs12: Unrecognized flag nodes -legacy unable to load certificate<PHONE_NUMBER>01536:error:0909006C:PEM routines:get_name:no start line:crypto/pem/pem_lib.c:745:Expecting: TRUSTED CERTIFICATE
Environment Details
Azure DevOps Pipeline Agent: macOS-15
OpenSSL Version: [Include version after debugging step]
Task Version: InstallAppleCertificate v2.246.5
Certificate: .p12 file verified to be valid locally.

I don't think that it's related to this extension. You can raise this issue on their repository, thanks. Feel free to reopen if in case I misinterpreted and this issue is related to my extension.


Add initial Travis config

Allows enabling Travis CI for the project. It is only a half of configuration second part of the setup requires visiting https://travis-ci.org/. More on this Integrate Travis CI with your GitHub repo.
There is still a room for improvement like to add a batch, as soon as I have no access to concrete URL. I have not included the update to the README.

@veghtomi I have finally recovered build to green with amendments you have requested for :)


访问不了ui了

用docker-compose方式启动了所有组件, 已经用了一段时间了, 一直可以打开ui. 不知为何突然再也打不开了, 访问http://x.x.x.x:9093/ui/index.html一直报错: {"message":"Not Found"} . 这里的IP不是<IP_ADDRESS>. 请问如何解决? 各种办法都试过了, 系统都用了新的.

用nginx把<IP_ADDRESS>:9093映射出来访问, 还是NotFound. 很纳闷. apiserver日志里只有重复的一条: "level":"ERROR","prefix":"echo","file":"echo.go","line":"340","message":"code=404, message=Not Found"

好像是镜像问题. 我用老的gateway镜像启动一切正常. docker-compose启动就没UI, 换了几个环境重试都是如此.

有日志么

apiserver每次访问都是这条: "level":"ERROR","prefix":"echo","file":"echo.go","line":"340","message":"code=404, message=Not Found"

你是怎么启动的？docker-compose.yml文件看看

是从最新的源码拉下来直接启动的.
prometheus_1   | level=info ts=2020-02-12T07:33:56.159Z caller=web.go:416 component=web msg="Start listening for connections" address=<IP_ADDRESS>:9090
prometheus_1   | level=info ts=2020-02-12T07:33:56.183Z caller=main.go:655 msg="TSDB started"
prometheus_1   | level=info ts=2020-02-12T07:33:56.183Z caller=main.go:724 msg="Loading configuration file" filename=/etc/prometheus/prometheus.yml
prometheus_1   | level=info ts=2020-02-12T07:33:56.185Z caller=main.go:751 msg="Completed loading of configuration file" filename=/etc/prometheus/prometheus.yml
prometheus_1   | level=info ts=2020-02-12T07:33:56.185Z caller=main.go:609 msg="Server is ready to receive web requests."
etcd_1         | 2020-02-12 07:33:57.703532 I | etcdmain: etcd Version: 3.3.12
etcd_1         | 2020-02-12 07:33:57.703736 I | etcdmain: Git SHA: d57e8b8
etcd_1         | 2020-02-12 07:33:57.703743 I | etcdmain: Go Version: go1.10.8
etcd_1         | 2020-02-12 07:33:57.703745 I | etcdmain: Go OS/Arch: linux/amd64
etcd_1         | 2020-02-12 07:33:57.703748 I | etcdmain: setting maximum number of CPUs to 4, total number of available CPUs is 4
etcd_1         | 2020-02-12 07:33:57.703771 W | etcdmain: no data-dir provided, using default data-dir ./default.etcd
etcd_1         | 2020-02-12 07:33:57.704737 I | embed: listening for peers on http://localhost:2380
etcd_1         | 2020-02-12 07:33:57.704867 I | embed: listening for client requests on <IP_ADDRESS>:2379
etcd_1         | 2020-02-12 07:33:57.801892 I | etcdserver: name = default
etcd_1         | 2020-02-12 07:33:57.801953 I | etcdserver: data dir = default.etcd
etcd_1         | 2020-02-12 07:33:57.801963 I | etcdserver: member dir = default.etcd/member
etcd_1         | 2020-02-12 07:33:57.801967 I | etcdserver: heartbeat = 100ms
etcd_1         | 2020-02-12 07:33:57.801971 I | etcdserver: election = 1000ms
etcd_1         | 2020-02-12 07:33:57.801974 I | etcdserver: snapshot count = 100000
etcd_1         | 2020-02-12 07:33:57.801986 I | etcdserver: advertise client URLs = http://<IP_ADDRESS>:2379
etcd_1         | 2020-02-12 07:33:57.801991 I | etcdserver: initial advertise peer URLs = http://localhost:2380
etcd_1         | 2020-02-12 07:33:57.802000 I | etcdserver: initial cluster = default=http://localhost:2380
etcd_1         | 2020-02-12 07:33:57.851929 I | etcdserver: starting member 8e9e05c52164694d in cluster cdf818194e3a8c32
etcd_1         | 2020-02-12 07:33:57.852012 I | raft: 8e9e05c52164694d became follower at term 0
etcd_1         | 2020-02-12 07:33:57.852028 I | raft: newRaft 8e9e05c52164694d [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
etcd_1         | 2020-02-12 07:33:57.852033 I | raft: 8e9e05c52164694d became follower at term 1
etcd_1         | 2020-02-12 07:33:57.874987 W | auth: simple token is not cryptographically signed
etcd_1         | 2020-02-12 07:33:57.887683 I | etcdserver: starting server... [version: 3.3.12, cluster version: to_be_decided]
etcd_1         | 2020-02-12 07:33:57.888258 I | etcdserver: 8e9e05c52164694d as single-node; fast-forwarding 9 ticks (election ticks 10)
etcd_1         | 2020-02-12 07:33:57.888756 I | etcdserver/membership: added member 8e9e05c52164694d [http://localhost:2380] to cluster cdf818194e3a8c32
etcd_1         | 2020-02-12 07:33:58.453294 I | raft: 8e9e05c52164694d is starting a new election at term 1
etcd_1         | 2020-02-12 07:33:58.453409 I | raft: 8e9e05c52164694d became candidate at term 2
etcd_1         | 2020-02-12 07:33:58.453443 I | raft: 8e9e05c52164694d received MsgVoteResp from 8e9e05c52164694d at term 2
etcd_1         | 2020-02-12 07:33:58.453460 I | raft: 8e9e05c52164694d became leader at term 2
etcd_1         | 2020-02-12 07:33:58.453471 I | raft: raft.node: 8e9e05c52164694d elected leader 8e9e05c52164694d at term 2
etcd_1         | 2020-02-12 07:33:58.454112 I | etcdserver: published {Name:default ClientURLs:[http://<IP_ADDRESS>:2379]} to cluster cdf818194e3a8c32
etcd_1         | 2020-02-12 07:33:58.454249 I | embed: ready to serve client requests
etcd_1         | 2020-02-12 07:33:58.456384 I | etcdserver: setting up the initial cluster version to 3.3
etcd_1         | 2020-02-12 07:33:58.456692 N | etcdserver/membership: set the initial cluster version to 3.3
etcd_1         | 2020-02-12 07:33:58.456755 I | etcdserver/api: enabled capabilities for version 3.3
etcd_1         | 2020-02-12 07:33:58.457129 N | embed: serving insecure client requests on [::]:2379, this is strongly discouraged!
etcd_1         | proto: no coders for int
etcd_1         | proto: no encoder for ValueSize int [GetProperties]
pushgateway_1  | level=info ts=2020-02-12T07:33:54.491Z caller=main.go:79 msg="starting pushgateway" version="(version=0.9.1, branch=HEAD, revision=b4410a3a361a770a084007ef50aebf42d0e8793c)"
pushgateway_1  | level=info ts=2020-02-12T07:33:54.491Z caller=main.go:80 build_context="(go=go1.12.7, user=root@556a5d403380, date=20190801-14:03:20)"
pushgateway_1  | level=info ts=2020-02-12T07:33:54.493Z caller=main.go:133 listen_address=:9091
pushgateway_1  | level=info ts=2020-02-12T07:34:21.662Z caller=diskmetricstore.go:138 msg="metric families overlap" err="Metric family has the same name as a metric family used by the Pushgateway itself but it has a different help string. Changing it to the standard help string. This is bad. Fix your pushed metrics!" metric_family="name:"go_memstats_sys_bytes" help:"Number of bytes obtained by system. Sum of all system allocations." type:GAUGE metric:<label:<name:"instance" value:"ea848861ac3c" > label:<name:"job" value:"proxy" > gauge:<value:7.0715392e+07 > > " standard_help="Number of bytes obtained from system."
pushgateway_1  | level=info ts=2020-02-12T07:34:36.661Z caller=diskmetricstore.go:138 msg="metric families overlap" err="Metric family has the same name as a metric family used by the Pushgateway itself but it has a different help string. Changing it to the standard help string. This is bad. Fix your pushed metrics!" metric_family="name:"go_memstats_sys_bytes" help:"Number of bytes obtained by system. Sum of all system allocations." type:GAUGE metric:<label:<name:"instance" value:"ea848861ac3c" > label:<name:"job" value:"proxy" > gauge:<value:7.0715392e+07 > > " standard_help="Number of bytes obtained from system."
pushgateway_1  | level=info ts=2020-02-12T07:34:51.662Z caller=diskmetricstore.go:138 msg="metric families overlap" err="Metric family has the same name as a metric family used by the Pushgateway itself but it has a different help string. Changing it to the standard help string. This is bad. Fix your pushed metrics!" metric_family="name:"go_memstats_sys_bytes" help:"Number of bytes obtained by system. Sum of all system allocations." type:GAUGE metric:<label:<name:"instance" value:"ea848861ac3c" > label:<name:"job" value:"proxy" > gauge:<value:7.2155384e+07 > > " standard_help="Number of bytes obtained from system."
pushgateway_1  | level=info ts=2020-02-12T07:35:06.662Z caller=diskmetricstore.go:138 msg="metric families overlap" err="Metric family has the same name as a metric family used by the Pushgateway itself but it has a different help string. Changing it to the standard help string. This is bad. Fix your pushed metrics!" metric_family="name:"go_memstats_sys_bytes" help:"Number of bytes obtained by system. Sum of all system allocations." type:GAUGE metric:<label:<name:"instance" value:"ea848861ac3c" > label:<name:"job" value:"proxy" > gauge:<value:7.222092e+07 > > " standard_help="Number of bytes obtained from system."
pushgateway_1  | level=info ts=2020-02-12T07:35:21.663Z caller=diskmetricstore.go:138 msg="metric families overlap" err="Metric family has the same name as a metric family used by the Pushgateway itself but it has a different help string. Changing it to the standard help string. This is bad. Fix your pushed metrics!" metric_family="name:"go_memstats_sys_bytes" help:"Number of bytes obtained by system. Sum of all system allocations." type:GAUGE metric:<label:<name:"instance" value:"ea848861ac3c" > label:<name:"job" value:"proxy" > gauge:<value:7.222092e+07 > > " standard_help="Number of bytes obtained from system."
pushgateway_1  | level=info ts=2020-02-12T07:35:36.662Z caller=diskmetricstore.go:138 msg="metric families overlap" err="Metric family has the same name as a metric family used by the Pushgateway itself but it has a different help string. Changing it to the standard help string. This is bad. Fix your pushed metrics!" metric_family="name:"go_memstats_sys_bytes" help:"Number of bytes obtained by system. Sum of all system allocations." type:GAUGE metric:<label:<name:"instance" value:"ea848861ac3c" > label:<name:"job" value:"proxy" > gauge:<value:7.222092e+07 > > " standard_help="Number of bytes obtained from system."
pushgateway_1  | level=info ts=2020-02-12T07:35:51.662Z caller=diskmetricstore.go:138 msg="metric families overlap" err="Metric family has the same name as a metric family used by the Pushgateway itself but it has a different help string. Changing it to the standard help string. This is bad. Fix your pushed metrics!" metric_family="name:"go_memstats_sys_bytes" help:"Number of bytes obtained by system. Sum of all system allocations." type:GAUGE metric:<label:<name:"instance" value:"ea848861ac3c" > label:<name:"job" value:"proxy" > gauge:<value:7.222092e+07 > > " standard_help="Number of bytes obtained from system."
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Starting Grafana" logger=server version=4.6.3 commit=7a06a47 compiled=2017-12-14T08:36:59+0000
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Config loaded from" logger=settings file=/usr/share/grafana/conf/defaults.ini
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Config loaded from" logger=settings file=/etc/grafana/grafana.ini
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.data=/var/lib/grafana"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.logs=/var/log/grafana"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.plugins=/var/lib/grafana/plugins"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.log.mode=console"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_ADMIN_USER=admin"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_ADMIN_PASSWORD=*********"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_USERS_ALLOW_SIGN_UP=false"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Path Home" logger=settings path=/usr/share/grafana
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Path Data" logger=settings path=/var/lib/grafana
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Path Logs" logger=settings path=/var/log/grafana
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Path Plugins" logger=settings path=/var/lib/grafana/plugins
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="App mode production" logger=settings
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Initializing DB" logger=sqlstore dbtype=sqlite3
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Starting DB migration" logger=migrator
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create migration_log table"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create user table"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add unique index user.login"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add unique index user.email"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="drop index UQE_user_login - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="drop index UQE_user_email - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Rename table user to user_v1 - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create user table v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index UQE_user_login - v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index UQE_user_email - v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="copy data_source v1 to v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Drop old table user_v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Add column help_flags1 to user table"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update user table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Add last_seen_at column to user"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create temp user table v1-7"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index IDX_temp_user_email - v1-7"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index IDX_temp_user_org_id - v1-7"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index IDX_temp_user_code - v1-7"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index IDX_temp_user_status - v1-7"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update temp_user table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create star table"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add unique index star.user_id_dashboard_id"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create org table v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index UQE_org_name - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create org_user table v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index IDX_org_user_org_id - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index UQE_org_user_org_id_user_id - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="copy data account to org"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Skipping migration condition not fulfilled" logger=migrator id="copy data account to org"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="copy data account_user to org_user"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Skipping migration condition not fulfilled" logger=migrator id="copy data account_user to org_user"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Drop old table account"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Drop old table account_user"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update org table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update org_user table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create dashboard table"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add index dashboard.account_id"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add unique index dashboard_account_id_slug"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create dashboard_tag table"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add unique index dashboard_tag.dasboard_id_term"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="drop index UQE_dashboard_tag_dashboard_id_term - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Rename table dashboard to dashboard_v1 - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create dashboard v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index IDX_dashboard_org_id - v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index UQE_dashboard_org_id_slug - v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="copy dashboard v1 to v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="drop table dashboard_v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="alter dashboard.data to mediumtext v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Add column updated_by in dashboard - v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Add column created_by in dashboard - v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Add column gnetId in dashboard"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Add index for gnetId in dashboard"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Add column plugin_id in dashboard"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Add index for plugin_id in dashboard"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Add index for dashboard_id in dashboard_tag"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update dashboard table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update dashboard_tag table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create data_source table"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add index data_source.account_id"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add unique index data_source.account_id_name"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="drop index IDX_data_source_account_id - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="drop index UQE_data_source_account_id_name - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Rename table data_source to data_source_v1 - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create data_source table v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index IDX_data_source_org_id - v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index UQE_data_source_org_id_name - v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="copy data_source v1 to v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Drop old table data_source_v1 #2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Add column with_credentials"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Add secure json data column"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update data_source table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create api_key table"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add index api_key.account_id"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add index api_key.key"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add index api_key.account_id_name"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="drop index IDX_api_key_account_id - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="drop index UQE_api_key_key - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="drop index UQE_api_key_account_id_name - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Rename table api_key to api_key_v1 - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create api_key table v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index IDX_api_key_org_id - v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index UQE_api_key_key - v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index UQE_api_key_org_id_name - v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="copy api_key v1 to v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Drop old table api_key_v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update api_key table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create dashboard_snapshot table v4"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="drop table dashboard_snapshot_v4 #1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create dashboard_snapshot table v5 #2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index UQE_dashboard_snapshot_key - v5"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index UQE_dashboard_snapshot_delete_key - v5"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index IDX_dashboard_snapshot_user_id - v5"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="alter dashboard_snapshot to mediumtext v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update dashboard_snapshot table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create quota table v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index UQE_quota_org_id_user_id_target - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update quota table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create plugin_setting table"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create index UQE_plugin_setting_org_id_plugin_id - v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Add column plugin_version to plugin_settings"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update plugin_setting table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create session table"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Drop old table playlist table"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Drop old table playlist_item table"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create playlist table v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create playlist item table v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update playlist table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update playlist_item table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="drop preferences table v2"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="drop preferences table v3"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create preferences table v3"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update preferences table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create alert table v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add index alert org_id & id "
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add index alert state"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add index alert dashboard_id"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="create alert_notification table v1"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Add column is_default"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="add index alert_notification org_id & name"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update alert table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Update alert_notification table charset"
grafana_1      | t=2020-02-12T07:33:58+0000 lvl=info msg="Executing migration" logger=migrator id="Drop old annotation table v4"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="create annotation table v5"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="add index annotation 0 v3"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="add index annotation 1 v3"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="add index annotation 2 v3"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="add index annotation 3 v3"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="add index annotation 4 v3"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="Update annotation table charset"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="Add column region_id to annotation table"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="Drop category_id index"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="Add column tags to annotation table"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="Create annotation_tag table v2"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="Add unique index annotation_tag.annotation_id_tag_id"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="Update alert annotations and set TEXT to empty"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="create test_data table"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="create dashboard_version table v1"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="add index dashboard_version.dashboard_id"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="add unique index dashboard_version.dashboard_id and dashboard_version.version"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="Set dashboard version to 1 where 0"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="save existing dashboard data in dashboard_version table v1"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="alter dashboard_version.data to mediumtext v1"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="create tag table"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Executing migration" logger=migrator id="add index tag.key_value"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Created default admin user: admin"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Starting plugin search" logger=plugins
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=warn msg="Plugin dir does not exist" logger=plugins dir=/var/lib/grafana/plugins
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Plugin dir created" logger=plugins dir=/var/lib/grafana/plugins
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Initializing Alerting" logger=alerting.engine
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Initializing CleanUpService" logger=cleanup
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Initializing Stream Manager"
grafana_1      | t=2020-02-12T07:33:59+0000 lvl=info msg="Initializing HTTP Server" logger=http.server address=<IP_ADDRESS>:3000 protocol=http subUrl= socket=

apiserver_1    | 2020/02/12 07:34:00.378583 [info] addr: <IP_ADDRESS>:9092
apiserver_1    | 2020/02/12 07:34:00.378626 [info] addr-store: etcd://etcd:2379
apiserver_1    | 2020/02/12 07:34:00.378630 [info] addr-store-user:
apiserver_1    | 2020/02/12 07:34:00.378633 [info] addr-store-pwd:
apiserver_1    | 2020/02/12 07:34:00.378635 [info] namespace: dev
apiserver_1    | 2020/02/12 07:34:00.378637 [info] discovery: false
apiserver_1    | 2020/02/12 07:34:00.378640 [info] service-prefix: /services
apiserver_1    | 2020/02/12 07:34:00.378643 [info] publish-lease: 10
apiserver_1    | 2020/02/12 07:34:00.378645 [info] publish-timeout: 30
apiserver_1    | 2020/02/12 07:34:00.428208 [info] api server listen at <IP_ADDRESS>:9092
apiserver_1    | 2020/02/12 07:34:00.428838 [info] rpc: start a grpc http proxy server at :9093
apiserver_1    |    ____    __
apiserver_1    |   / // /  ___
apiserver_1    |  / // / _ / _
apiserver_1    | //_////___/ v3.3.5
apiserver_1    | High performance, minimalist Go web framework
apiserver_1    | https://echo.labstack.com
apiserver_1    | _____________________________O/
apiserver_1    |                                     O
apiserver_1    | ⇨ http server started on [::]:9093
apiserver_1    | {"time":"2020-02-12T07:35:35.250455332Z","level":"ERROR","prefix":"echo","file":"echo.go","line":"340","message":"code=404, message=Not Found"}

从新pull最新的apiserver 的镜像，由于项目改名，apiserver的默认ui路径使用了老的项目名称路径


[#13403] Flaky test: org.infinispan.client.hotrod.retry.DistributionR…

…etryTest#testPutIfAbsent

Also fixes other methods in the same class

Fixes #13342
Fixes #13350
Fixes #13381
Fixes #13389
Fixes #13394
Fixes #13403
Fixes #13435
Fixes #13452
Fixes #13455
The test would fail randomly due to the client seeing the server disconnected sooner than the prior client. In this case we are allowing that to happen but if so we assert the failed server is present.

Jenkins looks good, but running the GH action again. It stopped somewhere in the IT tests.

Thanks, @wburns!


Blender stutters when running filtering by portal entity

When I go into sorting entities by portals, a problem arises.... My blender starts to go crazy and stutter.... What could this be caused by?
https://streamable.com/3puef2

Blender version : 3.6.4
Sollumz version : last pull on main branch
What is the issue you're having?
It's a huge project ( about 28 rooms ) and about 2000+ props, I have some slow on export the ytyp ( seems normal, because of the numbers of props ).
But when I tried to change the filter to "Portal" I'm stuck in a loop of blender not responding.
What are you trying to do?
Trying to change the Filter By in the MLO menu to Portal.
Any errors or warnings? (Post screenshot below) :
no
Files to reproduce the problem (if applicable)
Private project, if needed I can give the blend file and the fiveM ressources.
Video in the help channel : https://discord.com/channels/899043946142003240/1163127104053989467

Sollumz rebuilds the list of valid portals/rooms multiple times per entity to do the filtering each time the UI needs to be redrawn. That seems to be causing the performance issue here, and, of course, it only gets worse the more entities you add.


feat(losses): add Tversky loss implementation

Add Tversky loss implementation.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 54.33%. Comparing base (b267f93) to head (6788158).
Report is 1 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #19511       +/-   ##
===========================================
- Coverage   76.28%   54.33%   -21.95%
===========================================
  Files         367      367
  Lines       41233    41254       +21
  Branches     8076     8077        +1
===========================================
- Hits        31453    22417     -9036
- Misses       8059    17245     +9186
+ Partials     1721     1592      -129

Flag
Coverage Δ

keras
54.33% <100.00%> (-21.80%)
:arrow_down:

keras-jax
?

keras-numpy
54.33% <100.00%> (+0.05%)
:arrow_up:

keras-tensorflow
?

keras-torch
?

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

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


fork_ami support for private repos

The initial version of the new fork_ami job works only with public repos; changing the flow to git clone locally and update the remote repo with the local copy does not work for some reason related to git+ssh. We probably want to investigate more.

As per @stevekuznetsov, oct sync local should work for this use-case.

I don't think we are moving forward with enhancing AMIs anymore.


chore: upgrade lerna to ^5.6.2

Problem

Solution

Additional Notes

Links
Ticket

GitHub issue _____
Other links
Verification
Manual tests

Automated tests

[ ] Unit tests added/updated
[ ] E2E tests added/updated
[ ] N/A - (provide a reason)
[ ] deferred - (provide GitHub issue for tracking)

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

Codecov Report

Merging #973 (eef0933) into main (3e86718) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@           Coverage Diff           @@
##             main     #973   +/-   ##
=======================================
  Coverage   93.00%   93.00%
=======================================
  Files         120      120
  Lines        5275     5275
  Branches     1562     1562
=======================================
  Hits         4906     4906
  Misses        348      348
  Partials       21       21

Continue to review full report in Codecov by Sentry.

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


sf::Text crashes on destruction when _GLIBCXX_DEBUG is defined

On x86_64 Arch Linux with GCC 7.2.0, the destructor of sf::Text causes a segmentation fault when _GLIBCXX_DEBUG is defined.  The following code
#include <SFML/Graphics>
int main() {
    sf::Text text;
}

compiled with
g++ main.cpp -D_GLIBCXX_DEBUG -lsfml-graphics

should reproduce the error; I've attached the valgrind output.  This was tested with SFML 2.4.2 from the repos, but I've also checked with SFML built from the latest source and the result is the same.
valgrind.log

For consistent results, maybe you have to compile SFML with _GLIBCXX_DEBUG too.

That's a good point—I seem to be getting a crash even when SFML is compiled using it (by passing -DCMAKE_CXX_FLAGS=-D_GLIBCXX_DEBUG to cmake), but you're right that I shouldn't expect this to work, so I don't think it's really an issue.


Fix #663 - Preventing non admin with access to share folder to READ and WRITE.

Remove the @requires_admin flag in methods get_file and put_file, and added a \\ to the logger, so it displays correctly the file path.

Logger without \\

Logger with \\

Current output:

Output modified adding \\ to the logger:


Add logo snippet

This snippet helps users get any company logo with the Clearbit Company Logo API. Learn more: https://clearbit.com/blog/logo

I dont understand this. What's it supposed to do?

Hey Pedro! This snippet helps you get any company logo. For example, you can use it to quickly customize your Notion pages with your company logo. Try it yourself: https://logo.clearbit.com/raycast.com — and please keep me posted :)

Ooooh ok. I think it's a bit too specific for this project. I'd like to try and keep the snippets for very well known things. But great to discover this API, very useful indeed! Thanks for your contribution 🙏

Got it. Thanks for your feedback, and keep up your great work 🙂


nls support for package.json and common-js

Assignments

[x] Windows @joaomoreno
[x] OS X @weinand
[ ] Linux @Tyriar

Details
We now have nls support for package.json and common-js. To test do the following:
Package.json for Extensions

create a package.nls.json file as a sibling to your package.json file
in package.json, replace strings that should be localized with a key surrounded by %%. For example

"commands": [
			{
				"command": "typescript.reloadProjects",
				"title": "%typescript.reloadProjects.title%",
				"category": "TypeScript"
			}
		],

In the package.nls.json add a key value pair that maps the key to a human readable value for our default language (which is English).

{
	"typescript.reloadProjects.title": "Reload Project",
}

Ensure that when you start  the extension the correct string is presented in the user interface. Also ensure that pseudo translation works. To do so start vscode with --locale=pseudo. The strings from the package.nls.json should be enclosed in [] and vowels should be doubled.
CommonJS Extensions
Install vscode-nls as a dependency of your extension. In the extension main add the following code:
import * as nls from 'vscode-nls';
let localize = nls.config({ locale: 'pseudo' })();

And in the activate function add
console.log(localize('key', 'Extension activated'));

This should show the following in the console:
[Plugin Host] ［Exteensiioon aactiivaateed］

In other files in the extension you don't need to configure the nls module again. You can simple do:
import * as nls from 'vscode-nls';
let localize = nls.loadMessageBundle();

If you want to leave the code in since you tested it with your extension code then simply remove the locale property and initialize as follows:
import * as nls from 'vscode-nls';
let localize = nls.config()();

More detailed testing steps would be appreciated.
Also, I have no idea how to test a Portuguese translation, for example...

@joaomoreno we do not have any translations other than the pseudo translation. If we had, you could test Portuguese by launching code with "--locale=pt_PT" or "--locale=pt_BR".

Isn't each extension supposed to ship its own translations files? If so, how can I set up a Portuguese file?

@joaomoreno the process (i.e. tools) that produces these files is not yet ready (https://github.com/Microsoft/vscode-nls-dev). The default package.nls.json I've created manually. I assume that you can make a Portuguese clone of it but we would have to reverse engineer the name of that file from the source in vscode-nls-dev.
For the other nls files it is even more complex to manually doing it because the keys that you pass to localize() are converted into sequential numbers...

Got it


handling failed OpenSSL_memdup

Why CI failed?

It happens.

Ping @jakkdu - are you going to update this PR? I just added a new comment, and there was a previous unresolved issue from @ajmohan above too.

Thanks. I forgot this PR. I will close the PR and send a new PR for the issue.

@mattcaswell I think your issue is somewhat different from the current issue
I think it is better to make a separate PR for the issue, isn't it?

I'd fix it while you're in there touching the code anyway - just make it a separate commit in the same PR.

Ok. Then I will add new commit related with @ajmohan and yours.

Make it two extra commits - one for each change.

I will close the PR and send a new PR.
Sorry I deleted my forked repo.


key path and auto increment

Can I set up key path and auto increment by using localForage?

There is no auto increment functionality for now. How would you like it to work?

The function I try to achieve is when inserting new entry into the database, for example
key = 1,
Content={
id: 1,
......
.....}.
This way, when using ng-repeat with #href, it is easier to circulate the array by looking at the object.id instead of a separate key. Once the id is found, the rest of the content could be located at the same object level.
I originally pushed indexDb entries into an array without assigning specific id within the object. It made it real hard to use $stateparam to find the object content.
I don't know if I made myself clear. I did managed to make it work right now, by manually insert object.id when storing the data into indexDb.


Segfault on HidApi::new() when no HID devices are found.

If I am correct, something isn't checking if it's NULL in case there's no devices, so when it tries to move stuff from the non-existant CFFI struct into a native struct... it, well, segfaults.
If I understand correctly, all that needs to be done is add a NULL check to get_hid_device_info_vector, or restructure the loop slightly.
I may try to send a PR tomorrow, but first I must sleep.

"NULL in the case of failure." says the hidapi manual. Their documentation is also slightly wrong, because no devices is indeed a possibility, but might be rare.
The rust wrapper should  check the case, but we have to decide what we want to return. I think changing the return signature to a Result might be the right choice if we want to interpret it exactly like the hidapi doc.

I'm leaning towards an Option, given that we have no way to see if there are just none or if there was an error. That said, the final user will end up knowing if it's an error or not, given that there's a printf("Can't create udev\n"); inside hid_enumerate(). >_>

Let's be rusty about this: if hid_enumerate() returns NULL, we should return None. Result is a boolean operation -- either it works or it fails.
But if we're pragmatic, we should return an empty Iterator. That way, if one really needs to check for the length of the devices instead of matching a particular device, api.devices().iter().collect::<Vec<&hidapi::HidDeviceInfo>>().len() would do the job.

Facing this issue on a laptop,
hidapi detects only one device, if I unplug it -> SeqFault.
Are there any work arounds?

This should probably be fixed in the library. A workaround would be adding an extern "C" hid_enumerate() in your application. (You should look for the correct function prototype).
Then you can call it and if it returns a NULL pointer you should omit calling HidApi::new() or refresh_devices.

I will create a PR today after work which will fix this issue.

#9 closes this.


Deploy an example Node app to ECS

Add a Cloud Formation template, SAM config and a Hello World Node.js app
that can be deployed to run on AWS ECS using Fargate.
This is the smallest template that's needed to run an app and access it
via a DNS record from the public internet. Not all of this is needed for
every deployed service however - the networking stack (VPC, subnets,
internet gateway, routing etc.) is all something that can be set up once
per account and used across multiple services. The aim of this example
however is to work out everything that's needed to run an internet
facing service, so it's all in a single template and stack.
Once it's deployed with sam deploy, the service can be accessed at the
DNS name for the load balancer.
Note, the Node app is present in this repo but currently there's no
automation or instructions for building the container and pushing it to
ECR. Instead I built the container on my laptop and ran docker push to
push it to my account on Docker Hub. This isn't sustainable as Docker
Hub rate limits downloads, but it's fine for an example app. We have
followup work planned to set up a proper pipeline.

Trello

Looks great, congrats for getting that up.
I'll try and run the SAM command now and 👍🏻 the README.md
Would be good to chat more about that availbility zone change, check I understand the implications of what's going on there?

I'll try and run the SAM command now and 👍🏻 the README.md

You'll need to change the stack name in samconfig.toml if you want to deploy everything fresh, otherwise it'll try to overwrite and there won't be any changes (since this is already deployed)


Hydrated Bloc yields the error state

Describe the bug
So i switched from flutterbloc to hydaretdbloc, when i my switch on the data connection and  i do not have an active internet connection the hydrated bloc works but when i complete shutdown the WiFi & the data connection it does not work
Expected behavior
Load the cached rest data rather than yielding the error state

Hi @Iampato 👋
Thanks for opening an issue!
Can you please share the link to a sample app which illustrates the problem you’re having? Thanks!

Can i just add you to the repo since its private

@Iampato sure 👍

@Iampato It doesn't look like you're using hydrated_bloc in the repo. Have you pushed your changes to a branch?

Wooh i forgot i just push

Sorry just saw this now! Will take a look ASAP 👍

@Iampato can you please reopen this issue in https://github.com/felangel/bloc if you're still having trouble. I realize this is quite an old issue and the hydrated_bloc repository has been merged into the core bloc repository 👍


Use my own SSL certificate, not from letsencrypt

Where I must put files of mine cert site.cert and site.key and what settings I must apply in docker-compose.yml (or elsewhere) to make my site works with those certs?

It is pretty easy. I just need to put my crt and key files named as DOMAIN.crt DOMAIN.key into the ${NGINX_FILES_PATH:-./data}/certs folder.


Demos are broken

Download the repo zip, launch the demo, and select chains. On Chrome (Mac), one encounters a reference error. body.nextGroup is not a function.
The dev demo doesn't even run. At all. No part of it works. Black screen.

To run the demos from source you'll need to build first, see CONTRIBUTING.md for instructions.

Ah, got it. Thanks.


feat: Support globbing for plugins

This also deprecates the dir and ext flags because globs are just better.
Closes #6 because that wasn't updated to use globs.

Successfully tested


Fix up WFS-T inserts

Issues were:

geometryName not correct
geometry type not correct

SDK-489
closes https://github.com/boundlessgeo/qgis-webappbuilder-plugin/issues/367

Coverage decreased (-0.2%) to 72.132% when pulling e601982cd53651cdba8fff06b9041de2fd979561 on wfst-inserts into 20062ffc19cdf07d5eeb9fbea00c4c9b6353cf7e on master.

Coverage increased (+0.3%) to 72.646% when pulling 22f26a4affb71e1662e9dfec3c6b96e97ec4effe on wfst-inserts into 20062ffc19cdf07d5eeb9fbea00c4c9b6353cf7e on master.


Do not throw an Exception when the effect is not identifiable

Martí,
Congratulations on this very simple to use package, it seems great so far.
One design suggestion though.
Instead of throwing an Exception when the effect is not identifiable, I believe you should still return a probability object, but with exactly the information you now provide in the Exception message: that the effect is not ID and the hedge.
The reason being that the effect not being identifiable is not an error in itself, it is the correct behavior of the algorithm.
So it is better to return the formal result of the algorithm (non-identifiability and the reason for non-identifiability) in a way that can be stored in an object for further manipulations.
An exception should be used for real errors and exceptions only.

Dear Carlos,
First of all, thank you for your kind words. This has been a tricky project, and I am pleased my contribution can help the scientific community.
Regarding your suggestion, how would you implement this modification? The fact that the causal effect is not identifiable cannot be encoded in a probability object, because it is not a probabiliy. The thrown exception has to be interpreted as a natural and possible outcome of the algorithm, and not an error.
I understand your concern, but I do not know how to encode the information of non-identifiability into the Probability class.

Hi Marti,
I understand it is not a probability, but is also not an error. The way it currently is we would need to capture the useful information you provide in ad-hoc manner (that it is non-id,  the hedge etc). So I believe a better solution would be the function to return an output with that information.
(Tikka also made this choice of producing an error in his first causal.effect package, but notice he doesn't do that anymore in the newer packages.)
But in the end of the day, of course, this is a design choice! Just a suggestion.
Best, Carlos


Making it more obfuscated!

changelog:

every int declaration was moved outside a function as declarations outside functions are implicitly ints.
same for the function c and main, we don't have to declare them as int.
the variable c was renamed to d to avoid conflicts with the function
fh was renamed f because it's shorter
the char f[] in the function c was changed to a char*f, which is shorter and we can do that without danger since we do not edit it.
if(f[m+++1]=='\0') is equivalent to if(f[m+++1]==0) and subsequently to if(!f[m+++1])

Additional notes:

a lot of variables are declared but not initialised and then used with ++, this could cause some problems with some specific compilers but everything works well with both clang 14 and gcc 11.3 here
i can't declare l as an int[] because fgets disagrees
there is probably a way to optimise more by replacing the ifs with ternary operators but i'm too lazy to do that

oh yeah i forgot to mention but all this saves a whopping 33 characters.
I could've saved more space by removing the spaces in the printf but didn't want to


[Mint] Run CI with PostgreSQL

The CI pipeline runs with SQLIte right now. All the necessary parts are there, what needs to be done is to properly set up the test database during runtime (in conftest.py) for Postgres, i.e., the database needs to be cleared for each tests otherwise we will run into uniqueness issues.
The CI already installs postgres, one line needs to be commented out in the test.yaml matrix.

Related: #386


Feature Request: Support for Ed25519?

Would it be possible to support this algorithm? I don't know whether the library doesn't support it or whether it's simply not part of the JWT spec. It would be nice to be able to use Ed25519 keys, though.

Ed25519 isn't part of JWA (unfortunately). The specs allow use non-standard algs, you just can't expect interoperability, and this library doesn't support such a set up (as is).

You can check out all support algorithms in the JWS spec:
https://tools.ietf.org/html/rfc7518#section-3.1

Check out my fork: jsonwebtoken-ed25519

@omsmith Edwards-curve cryptography was defined for JOSE in RFC 8037, the last specification to come out of the working group.  Is that not sufficient? https://tools.ietf.org/html/rfc8037

@StevenACoffman this wasn't possible with node's crypto until very recently. I expect @omsmith to add the support for Ed25519 and Ed448 JWA eventually, until then - you can use my implementation, with the added benefit of supporting more various key formats such as JWK, JWE encryption and all the bells and whistles of the JOSE specifications.


Handle user intent w/ ARUI bridge

Depends on #188

@ovenmitt, will you take a look at this? I modified the ARUI scripts a bit to pass the InterpretedAudioUserIntentMsg to the callback function, so we can publish it.


vm._uid is not unique enough

Vue.js version
dev branch
Steps to reproduce

Load 2 separated vue components on the same page, by using two different webpack builds. Each of them has to not share the Vue module they're using.

What is Expected?
To not have repeated vm._uid across multiple components. This breaks vue-devtools.
What is actually happening?
Devtools are working in a strange way because of the repeated _uid they are relying on.

A possible solution is to generate those _uids a bit more randomly, with Math.random(). I can come up with a pull request for that.

Load 2 separated vue components on the same page, by using two different webpack builds.

No, there's no other way around and using global Vue is a no go for me.

This also means you are loading two copies of Vue on the same page - quite sub-optimal and not really a use case it's designed for.
Isn't it better to make the two webpack bundles share the Vue dependency instead?

This also means you are loading two copies of Vue on the same page - quite sub-optimal and not really a use case it's designed for.

Yeah, that's how I'm doing it. I'm loading them via code splitting and they're happen to load at completely different stages.
Sharing Vue dependency across webpack bundles is not an option because those two bundles actually come from two completely separated repos.

Looks like it really is a bad idea to load multiple Vue dependencies on the same page.
I'd probably have to go with global Vue instead.

@yyx990803  there are valid use cases for this, for example when an widget is being shipped to be used by 3rd parties. The widget needs to be embedded in a page without knowing what other frameworks / libraries are loaded - think a twitter button. Having the sites install vue separately will be a massive deal breaker for them. Can we just specify a prefix for all the components?

Make Vue an external dependency of your widget library and make sure the client loads only one Vue copy. It's much better for your users too. Cheers.

Confirmed, having one single instance of Vue is the best solution for this problem. I've avoided many problems that way.

@posva It's not easier, it gets more complicated for them to the point that they may drop it in favour of something else.  Currently they just need to insert something like <script type="text/javascript" src="http://s3-with-cloudfront-url-here.com"></script> in their website and that's it, the widget works.
A lot of them may be on wordpress, drupal and so on without having a build system in place. Asking them to install a specific version of vue separately from a different site is a deal breaker.

@motanelu I'm doing with work on WordPress also and yes, that's still the best option.

@motanelu As a drop-in widget, it should be bundled with it's own vue/vuex (and other dependencies) into one javascript file (with webpack/rollup etc), and never rely on the global vue provided by the user. This way your widget will always work no matter what website it runs on.

@fnlctrl that's why it would be good to be able to prefix component uids

Why would you need to prefix component uids? The bundled widget will run in a closure and will have no access to anything outside, so it will never interfere with other vue instances.

I've experienced some issues with vue-devtools


TextGeometry in Cannon?

How would I import a string of text as new CANNON.Body({}) ?
Is that possible?  Would I convert text to something like the bunny.js file seen here?
http://schteppe.github.io/cannon.js/demos/bunny.html
Thanks.

@Tzikas Whitestorm.js uses Physics.js as it's physics(Already built-in).
Why not using WHS.TEXT class?

Hi,
If you want to use the ConvexPolyhedron class, you need to do use something like HACD to decompose the mesh into convex pieces. You could also use the Trimesh shape directly but it has limited collisions... See the collision table.
You could also use simpler shapes to make up efficient approximate collision shapes for your geometry. Like this:

How do you use https://github.com/kmammou/v-hacd ?  I can't find any clear instructions.

I never actually used HACD myself, I downloaded the bunny pre-decomposed... Can't help you there.

I'm trying to have multiple letters crash into one another.  Do you think I could wrap each 3D letter in a box shape and simulate it that way?  It doesn't have to be perfect.

Boxes should be fine I think! Depends on how you will use them.
An other idea: if you don't need bevels on your text mesh, you could probably use a 2d polygon decomposition library and then extrude the convex 2d polygons into 3d shapes. See https://github.com/schteppe/poly-decomp.js

I'll look into that, but to be honest I have no idea how to implement it.  I'm creating 3D letter using THREE.TextGeometry and THREE.Mesh.  How would I insert that obj into a Cannon box ?:
var boxShape = new CANNON.Box(new CANNON.Vec3(1,1,1));
var b2 = new CANNON.Body({ mass: 5 });
b2.addShape(boxShape);

I guess you could get the bounding box from the mesh (see http://stackoverflow.com/questions/15492857/any-way-to-get-a-bounding-box-from-a-three-js-object3d) and then use the size of that box for the Cannon box.
To sync positions and rotations, see https://github.com/schteppe/cannon.js/blob/master/examples/README.markdown#threejs (may be out of date).


Add missing iron-input & iron-form depedencies to make it works well

Hi, I just add those missing depedencies because when I press enter in text field it makes my url like this localhost:8081? and I inspect the console then see that iron-input and iron-form are missing. After I do that, it works very well. I hope it helps you to make this study case of web components todo more engaging! Thanks a lot.

Yes indeed, good catch! I am not used to use Bower. too old tool IMO
thanks

You're welcome. Yes, you're right because it (Bower) says "maintenance" and Polymer decides to migrate their components to npm.


[WIP] [Constraint solver] While simplifying constraints, test protocol conf…

…ormance of arguments.
When we simplify bindings and function applications, we generate
independent constraints for protocol conformance and argument
conversion. What we previously did not do is examine these constraints
together to see if they make any sense.
This commit collects the protocol conformance constraints while
simplifying these independent constraints, and then tests these against
the argument conversion constraints for arguments to see if the
arguments could possibly conform to the protocols.
The end result is eliminating some of the exponential behavior observed
the type checker.

@swift-ci Please smoke test and merge

@swift-ci Please smoke test and merge

@swift-ci Please smoke test

@swift-ci Please smoke test

There may be too much going on with allowed argument conversions to reasonably implement this idea in a robust way.


[Feature][Zeta] Seatunnel base zeta on yarn

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
There are many scenarios where job-level isolation is required. At present, there are two choices: k8s and yarn. However, k8s is generally used by large companies, and its operation and maintenance costs are high. Therefore, it is recommended to give priority to implementing seatunnel base zeta on yarn.
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[x] Yes I am willing to submit a PR!

Code of Conduct

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

I'm making some progress on this, and I'm going to continue to finish it


Add test coverage verification

So we can know when we reached 100% test coverage, we need something indicating it.
It would be good to add a test coverage badge to README so we can easily track where we are.

Travis build status badge added on #182
Test coverage still needed.

Test coverage solved with #184


boards: 96b_carbon: Require BT for NET_L2_BT

Since NET_L2_BT no longer "select"s BT, enable the L2 only if
Bluetooth itself is enabled.
Fixes #14469
Signed-off-by: Carles Cufi<EMAIL_ADDRESS>

cc @thomasstenersen

@carlescufi lets see if this works, if it doesn't then we might need to put a depend on BT_L2CAP_DYNAMIC_CHANNEL somewhere.

@Vudentz I tested it locally and it worked, but let's see what shippable has to say.

@Vudentz actually this makes it build, but it doesn't enable CONFIG_BT at all, so I am pretty sure this won't run.

Codecov Report

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

@@            Coverage Diff             @@
##           master   #14474      +/-   ##
==========================================
- Coverage   52.04%      52%   -0.04%
==========================================
  Files         308      308
  Lines       45554    45554
  Branches    10545    10545
==========================================
- Hits        23707    23691      -16
- Misses      17051    17063      +12
- Partials     4796     4800       +4

Impacted Files
Coverage Δ

subsys/testsuite/ztest/include/ztest_assert.h
38.88% <0%> (-38.89%)
:arrow_down:

subsys/testsuite/ztest/src/ztest.c
65.28% <0%> (-7.44%)
:arrow_down:

Continue to review full report at Codecov.

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

@Vudentz @ulfalizer I've re-created the dependencies for NET_L2_BT in the board defconfig, seems it's the only way if we want the samples to be functional.