⚠ Bofrost.de has degraded performance

In 3b9c4bb, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 970 ms

Resolved: Bofrost.de performance has improved in 8786212 after 6 minutes.


feat(spanner): support comments and statement hints in untyped commands

SpannerCommandTextBuilder will try to determine the type of command based on the first word of the command text if no type is specified. This works well as long as the command text does not contain any comments or statement hints at the beginning of the command text.
This change adds a simple parser that will remove any comments and statement hints before checking the type of command. The command that is stripped of comments and hints is only used for determining the type of command. The original command will be passed on to Cloud Spanner.
Fixes #6847

Presumably this PR can be closed now that #6947 has been merged?

Presumably this PR can be closed now that #6947 has been merged?

Yes


add rfc template

Description
This adds an RFC template to Tide, similar to rustwasm's RFC template.
Motivation and Context

When making changes to an API it can be useful to get consensus on the design first in a structured manner before moving to implementation. The Rust project has proven that filing RFCs has been a a good strategy to discuss these kinds of changes, and we're seeing a similar process work well for rustwasm/gloo and crossbeam.
I've chosen to add the RFC template directly to Tide so we can discuss changes in the same repo. Having a separate RFC directory could be another option, but I feel that could be something we can  move to at a later stage if we think that's desirable. The main goal for now is to provide us with a more structured way of proposing API changes, for which this should be the right way to go.
How Has This Been Tested?

No tests needed.
Types of changes

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

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

This has received no objections since being raised, going to go ahead and merge so we can build on top of it.


Speedup vcs: Get rid of git status

This PR gets rid of the slow git status part. It makes use of git ls-files, which is much faster (thanks to @tupton for the hint in https://github.com/bhilburn/powerlevel9k/issues/60#issuecomment-368130608). Even git submodules are covered by  git submodule foreach --recursive.
This PR currently flips P9K_VCS_SHOW_SUBMODULE_DIRTY, so that new users won't see changed files in submodules.. Probably this is not necessary any more (my first version used the old git status, thus I added an if) and can be flipped back.

@dritter - Awesome! I tested this locally and saw a 50% speedup in user & sys time, and a 20% reduction in CPU overhead.

Here is a little write-up:
There are different Scenarios that can impact the performance of the vcs segment.

Testing git ls-files vs git status
Testing the vcs segment (old ad14807cef372994c3ba00632117f6d43b798ffb vs new fd5772afd2fcc23dfc3dbff2403eb236265ba5f4 ) as a whole

To be fair: The new VCS segment has new features (dir clobbering), that are tested as well.
 This is especially interesting, because the raw git ls-files (new way) is faster than git status (old way).

@dritter - Thanks for the thorough testing & reporting! This is excellent!
And yeah... the submodule thing really is interesting - especially since git ls-files is crushing git status. I wonder what our segment is doing that introduces so much delay in processing the submodules. I think we should open a new issue to investigate this behavior, specifically. Agree / disagree?

Yep, I agree on that. We should investigate that further. I opened #1054 for that.

Perfect =)


Add helper to reschedule all objects for reconciliation

Fixes #551

released in 0.58, thanks again for all of these!


Evict chunk descs of all unloaded chunks during maintenance.

Keeping these around has two problems:

Each desc takes 64 bytes, 10 of them is 640B. This is a lot of
overhead on a 1024 byte chunk.
It can take well over a week to reach a point where this and thus
Prometheus memory usage as a whole enters steady state. This makes RAM
estimation very hard for users, and makes it difficult to investigate
things like memory fragmentation.

Instead we'll wipe them during each memory series maintenance cycle, and
if a query pulls them in they'll hang around as cache until the next
cycle.
@beorn7

Looks superficially ok to me, but @beorn7 knows how to judge these subtleties around the storage better.

We can do this. :+1:
I don't think, though, that it will help a lot with "steady state". I have run into way too many volatile things taking a lot of RAM (like queries) so we need to solve that better anyway. (I have plans for making chunk eviction more dynamic, just not super high priority right now compared to all the other things on my plate.)
A very good point is the RAM usage of a single Desc. We originally thought an order of magnitude smaller than the chunk itself ought to be enough for anybody. However, for very long time series, there might be way more chunks on disk than in RAM, and then it might actually not be a good idea to keep all chunk descs in RAM until the next maintenance happens (or even load all chunk descs in the first place). But let's look at those options to improve at a different time.

I'm currently focused on testing the ingestion side of things, as that's the easier one to test. With this in at least we can say reasonably certainly that once the chunks are filled and there's been a full maintenance cycle that things should be steady.

If we don't have gigantic libraries for some SD mechanism that do loads of things... :(

I've been loadtesting with this and the previous committed changes. In a simple write-only system, memory now stabilises in a reasonable amount of time (about 6 hours after the chunks fill up) and is holding steady. This indicates no notable fragmentation in the current scrape->storage code path.


Improve DocumentBasedFixAllProvider performance for multiple documents

Previously, custom fix all providers called FixAllContext.GetDocumentDiagnosticsAsync for every document in the fix all scope. This change first replaces those calls with a single call to FixAllContextHelpers.GetDocumentDiagnosticsToFixAsync, which was extracted from CustomBatchFixAllProvider. It goes on to instead operate on a CompilationWithAnalyzers following the commentary in #1979. The result is improved performance when fixing violations in large projects, especially when only a few documents in the project contained violations.
Fixes #1974.

Current coverage is 79.44%

Merging #1983 into stabilization will increase coverage by +0.03% as of d9c4fc4

@@            stabilization   #1983   diff @@
=============================================
  Files                 559     560     +1
  Stmts               35094   35080    -14
  Branches             9711    9686    -25
  Methods
=============================================
- Hit                 27871   27870     -1
+ Partial              5668    5644    -24
- Missed               1555    1566    +11

Review entire Coverage Diff as of d9c4fc4

Powered by Codecov. Updated on successful CI builds.

With the latest change, the churn tests indicate that aside from true duplicates in 1.0.0, all three tested versions of Roslyn produce identical outputs.

:+1: Looks good to me, with two small remarks.

:+1:


[Dialog] Breaking in production build

Problem description
Using Next.js (v3.0.1-beta.16) along with material-ui.I am unable to open a dialog in production build generated using next build command provided by Next.js.
Link to minimal working code that reproduces the issue
Simple Dialog Example can be used to generate the issue:
https://material-ui-1dab0.firebaseapp.com/component-demos/dialogs#simple-dialogs
Versions

Material-UI: 1.0.0-alpha.21
React: 15.6.1
Browser: Google Chrome Version 59.0.3071.115 (Official Build) (64-bit)

Screenshots
Upon clicking the button that triggers the dialog, I am getting this error in console:
Uncaught (in promise) TypeError: Cannot read property 'contains' of null

NOTE : This is working fine while running in development mode.

I don't have that issue but the following:

We have release 1.0.0-beta.2.

@oliviertassinari Thanks for the quick response.Yes, I tried updating to beta release as well and I am facing the same issue you are facing.The UI breaks in the production build(Everything gets magnified and unexpected backgrounds).I was about to open an issue for this as well.

@oliviertassinari So I am able to figure out why is this happening with my configuration. I am using preact with preact-compat that replaces react (using webpack resolve) in production build. Can you confirm whether material-ui is compatible with preact or not ? I am facing this with all overlay components such as Drawer, Dialog which as per my guess uses Modal class.

I have figured out the source of the next.js issue. It comes from JssProvider. It's also highlighting a performance issue, should be fixed with https://github.com/zeit/next.js/pull/2648.

Can you confirm whether material-ui is compatible with preact or not?

I can't say, I have heard much on that topic.

merged :)

Thanks 👍

@divyanshutomar So, if you figure out some simple fixes we can apply to support preact, we would love to heard about it.

I confirm this doesn't work with preact and preact-compat.
I'm not quite sure how modalManager works, but the issue is happening because the this.focus() function can't find the instance of the modal.

We can open a preact issue. We haven't done any effort regarding supporting preact nor inferno. It's not something I will prioritize myself, but I would love to see a PR from the community :).

I'm having this issue still with 1.0.0-beta.4 version, and in development mode.

@fernandopasik Have a look at #7672 maybe?

@oliviertassinari I saw that one, but looks like it also says it's fixed?

@fernandopasik It hasn't been released, you can go back to beta.3

Oh it was merged after the 1.0.0-beta.4 version

Facing a production build issue with unstable render. I have posted an issue https://github.com/mui-org/material-ui/issues/9640 on material-ui repository.


Rails/ShortI18n

Rails/ShortI18n

Enabled by default
Safe
Supports autocorrection
VersionAdded
VersionChanged

Pending
Yes
Yes
2.7
-

This cop enforces that short forms of I18n methods are used: t instead of translate and l instead of localize.
This cop has two different enforcement modes. When the EnforcedStyle is conservative (the default) then only I18n.translate and I18n.localize calls are added as offenses.
When the EnforcedStyle is aggressive then all translate and localize calls without a receiver are added as offenses.
Examples
# bad
I18n.translate :key
I18n.localize Time.now

# good
I18n.t :key
I18n.l Time.now

EnforcedStyle: conservative (default)
# good
translate :key
localize Time.now
t :key
l Time.now

EnforcedStyle: aggressive
# bad
translate :key
localize Time.now

# good
t :key
l Time.now

Configurable attributes

Name
Default value
Configurable values

EnforcedStyle
conservative
conservative, aggressive

References
https://rails.rubystyle.guide/#short-i18n

I vote for aggressive

I vote conservative for readability

@Raou1d, shouldn't the cop then not be included at all?
To be honest I would like to have the reverse, have t and l enforced, but not I18n.t and I18n.l.

We have decided to go with the default configuration (conservative). You are free to configure it differently


feat(filterchecks): add optional metrics struct for caching

Add an optional metrics struct that if present, keeps track of the
efficacy of the extraction cache/evaluation cache.
The metrics count the number of times extract_cached() was called and
when it could use the cache, and the number of times comapre() was
called and when it could use the cache.
Like the caches, the memory for the pointer is assumed to be owned by
something else.
Signed-off-by: Mark Stemm<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature
Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area driver-kmod

/area driver-ebpf

/area libscap

/area libsinsp

/area tests

/area proposals

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Add ability to track metrics on filtercheck cache efficacy.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mstemm
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [mstemm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi Mark! Thank you, it LGTM!
We are in the process of freezing libraries for the next Falco 0.32.1 release; this can be merged right after :)

New changes are detected. LGTM label has been removed.

@VadimZy: changing LGTM is restricted to collaborators

In response to this:

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

LGTM label has been added.  Git tree hash: b34617a35b80a9223b441050e8efe276396bbce8

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, mstemm
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,mstemm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

I'm going to remove the hold tag, as falco 0.32.1 has already been released. Still needs a second approval though.

Ups sorry! Go ahead!

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, mstemm
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,mstemm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


runtime: high-percentile latency of memory allocations has regressed significantly

Heavily-allocating and highly-parallel applications' memory allocation latencies regressed significantly in the Go 1.12 release (up to 3-4x in k8s' 99th percentile latency).
Much of the background and work done for this issue has been summarized in https://github.com/kubernetes/kubernetes/issues/75833.
To re-summarize:
The offending commit with bisection was found to be 8e093e7a1cd8a092f23717cb8f34bca489a3eee5, which introduced the notion of scavenging to make up for the RSS increase for scavenging from scavenged memory (a mouthful). This change landed to fix an issue for some users where, as a result of previous changes in Go 1.12, the allocator could outrun things like debug.FreeOSMemory.
However, these extra syscalls caused an unacceptable increase in the latency of memory allocations which took this slow path which had the heap lock acquired. In the case of an already heavily-allocating and highly-parallel application (like the k8s situation: hundreds of thousands of goroutines and 64 Ps), this can have serious consequences in terms latency because subsequent span allocations' would end up spending a lot of time trying to acquire the heap lock.
While the fundamental issue is more the fact that the span allocator is not very scalable (all span allocations are serialized via a single lock), this is much more difficult to fix. At the very least we should bring back the latency to Go 1.11 or better in these situations.
In investigating this further, we discovered that the fact that the allocator could outrun things like debug.FreeOSMemory was partially because of the VSS growth introduced by the regression in #31616 in Go 1.12, so fixing this bug could be as simple as reverting 8e093e7a1cd8a092f23717cb8f34bca489a3eee5 and fixing #31616.

@gopherbot please backport open a backport to 1.12. I think it makes sense to fix this issue for Go 1.12 since it would at least let users safely move to Go 1.12 without having to skip a release due to performance issues.
We should do more in the future to ensure that performance regressions like this get discovered prior to release as opposed to after, perhaps through improved benchmarks.

As of https://go-review.googlesource.com/c/go/+/183857/9 landing, this is now fixed.

@gopherbot please backport open a backport to 1.13.

@gopherbot please backport to 1.13.


Cannot find 'Yaml' function

I'm getting this error
Unrecognized function or variable 'Yaml'.

44      MException("yaml:load:Failed", "Failed to load YAML string.").addCause(cause).throw

any ideas where this function is supposed to be located?

Sorry, not an issue with this, following here helped
https://uk.mathworks.com/matlabcentral/answers/96005-why-do-i-get-the-error-undefined-function-or-variable

Hi @jambo6,
I only found the time to answer today but I'm glad it works now for you. Would you mind giving a bit more details about the solution? I was trying to reproduce your error, but didn't know how. Maybe I could add something to the documentation the prevent others from having the same trouble.


Open Source about Another Paper

I am very interested in the author's work. I wonder if the author can open source the code of another paper[1].
Thanks!
[1] Hyungjin Chung, Eun Sun Lee, and Jong Chul Ye. 2022. MR Image Denoising and Super-Resolution Using Regularized Reverse Diffusion. arXiv preprint arXiv:2203.12621 (2022).

Unfortunately, we will not be able to open-source the code for [1] in the near future due to conflicts in patenting. Thanks for your interest.


Added notes and working_hours output to UserResource class.

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io


Self-generated certificate is regenerated every 15 seconds

Do you want to request a feature or report a bug?
Bug
Did you try using a 1.7.x configuration for the version 2.0?

[ ] Yes
[X] No

What did you do?
I configured Traefik with Docker provider and swarmMode=true, and I deployed a service with an HTTPS entrypoint and no tls options.
What did you expect to see?
Traefik should generate a certificate for HTTPS and keep it, so that it can be added to trusted certificates in a browser.
What did you see instead?
Traefik generates a new certificate for HTTPS every 15 seconds, so the browser keeps telling that the certificate is not trusted.
Output of traefik version: (What version of Traefik are you using?)
Version:      2.0.1
Codename:     montdor
Go version:   go1.13.1
Built:        2019-09-26T16:18:03Z
OS/Arch:      linux/amd64

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
time="2019-09-30T13:54:52Z" level=debug msg="No default certificate, generating one"
...
time="2019-09-30T13:55:07Z" level=debug msg="No default certificate, generating one"
...
time="2019-09-30T13:55:22Z" level=debug msg="No default certificate, generating one"

Hi @bgranvea ,
Thanks for your interest in the project.
It seems to be a duplicate of #5381
So I will close this issue.

hum yes maybe it is the same root cause as #5381 but with swarmMode=true, it seems even worse as the certificate is regenerated even when no new container is deployed.
And I don't understand why you don't consider #5381 as a bug: IMHO the self-generated certificate feature is not usable with a browser.

Hi @bgranvea, for the "swarmMode" making this behavior even worse, it's related to the issues #5419. This issue had been closed and will be in the next 2.0.x release. You can already test it with the image containous/traefik:experimental-v2.0 if you want to live on the edge :)
As for #5381, we consider the "self generated certificate" as a "degraded" mode. If you're willing to use a self signed certificate for all of your services, we recommend generating one and setting Traefik to use it as explained in https://docs.traefik.io/v2.0/https/tls/. I personnaly use the awesome tool mkcert https://github.com/FiloSottile/mkcert which generate for multiple domains and wildcards including *.local, and install the CA in my browsers.


Palette Manager not showing list of nodes and plugins for a package

Current Behavior
As reported here: https://discourse.nodered.org/t/bug-palette-manager-not-showing-the-number-of-plugins-nodes/90753
When node-red-contrib-uibuilder is installed, the palette manager should show how many plugins and nodes it has. But it doesn't.

Only just spotted by @fmarzocca but a quick test showed that it has been happening for at least several releases. Also happens across different platforms (Windows, Linux and FlowFuse).
Expected Behavior
Should show the list of nodes and plugins provided by the package:

This is the relevant section of package.json:
  "node-red": {
    "version": ">=4",
    "nodes": {
      "uibuilder": "nodes/uibuilder/uibuilder.js",
      "uib-cache": "nodes/uib-cache/uib-cache.js",
      "uib-element": "nodes/uib-element/customNode.js",
      "uib-file-list": "nodes/uib-file-list/customNode.js",
      "uib-html": "nodes/uib-html/customNode.js",
      "uib-save": "nodes/uib-save/customNode.js",
      "uib-sender": "nodes/uib-sender/uib-sender.js",
      "uib-tag": "nodes/uib-tag/customNode.js",
      "uib-update": "nodes/uib-update/customNode.js"
    },
    "plugins": {
      "uib-plugin": "nodes/uib-plugin.html"
    }
  },
  "engines": {
    "node": ">=18"
  },

So the palette manager should be showing 9 nodes and 1 plugin. The palette itself is showing all 9 nodes.
Steps To Reproduce
Install node-red-contrib-uibuilder from the palette manager or manually from the command line.
Example flow
N/A, no flow is needed. The nodes work and appear in the palette sidebar as expected.
Environment

Node-RED version: 4.0.2
Node.js version: Various, mostly v20
npm version: Various, mostly v10.7
Platform/OS: Windows 11, Debian Linux, FlowFuse
Browser: Various including Vivaldi

The reason your plugin is empty is because you are not calling RED.plugins.registerPlugin
https://github.com/TotallyInformation/node-red-contrib-uibuilder/blob/459a913f9d1a26143fcfe7786b8536c2d158f96e/resources/ti-common.js#L7
I'll see why the nodes aren't showing up in addition to the plugins.

One possibility would be that plugins and nodes are in the same container as shown in the following image:

Note: to do this the content of set should be separated to nodeSet and pluginSet.

Many thanks. Sorry it took a while for me to get back to this. Been busy with my web components and new website 😊
I've changed the plugin resource file to use registerPlugin as follows:
;(function () { // eslint-disable-line sonarjs/cognitive-complexity
    'use strict'

    // Register the plugin
    RED.plugins.registerPlugin('uib-plugin', {
        onadd: function() {
            let _dbg = false

            ......

        }
    })
}())

The code is correctly run. However, no difference in the pallet manager.

![image](https://github.com/user-attachments/assets/a329f393-2efa-420c-a82e-ab2a06dba2c9)

Hi, no worries 🙂
Did you have tested with the code in #4945 ?

I've changed the plugin resource file to use registerPlugin as follows:

I've some issues with how the TS is compiled to JS. You might try using module.exports = function () {}. It seems like plugins are handled in a different way than nodes which is pretty annoying since I have to use export = (RED: NodeAPI): void => { } and can export one thing only. Sadly there are still no plan using pure TypeScript and it's features…
Works within plugins:
"use strict";
module.exports = function(RED) {
    RED.plugins.registerPlugin("dummy", {
        type: "dummy"
    });
};

does not work within plugins, but works well with nodes:
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
exports.default = (RED) => {
    RED.plugins.registerPlugin("dummy, {
        type: "dummy",
    });
};

However there is still the issue that node-red doesn't show both plugins and nodes in the palet manager.

Please note that the support (in #4945) is not merged yet! It's quite normal with the current version, nodes and plugins are not correctly showed in the Palette. This is not the cause of TS.

Please note that the support (in #4945) is not merged yet!

I know, I just wanted to sum things up, since declaring plugins works in general.


RFC: Exploit Artifact Storage

Problem
Currently there's no formalized way to store exploit artifacts in a consistent way, and has been handled by either just printing extracted data into Success log level or by manually writing a temporary file based on the output. This has worked fine until we have needed a storage mechanism that is a bit more consistent.
Solutions

Use the db - Now that #177 is merged and we have a proper DB wrapper we could use what we've got and store artifacts in the database. This will require another table and a bit of schema stitching, which shouldn't be a problem. There's also other potentially useful things with this as the primary preferred way, such as keeping time based snapshots of the artifacts (ie logs captured over time from a target). One thing to keep in mind would be that sometimes accessing sqlite artifacts might not be the most ergonomic so maybe we could write some basic tooling around extracting the files based on exploit runs.
Add a basic handler for file writes to go-exploit - Currently we have been using a very simple write to temp file based on context, we could just easily port this to go-exploit and make it a public function for writing the files.
Both! - It could be possible to just have the artifact store function handle both cases and have a setting to toggle based on if db is enabled or not.

Other notes
Naming is always hard. loot isn't really very explicit but also pirates are neat. I am using artifacts in this based on prior verbiage, but could easily be switched up

loots

Artifact is the right term imo based on NIST Glossary but I know was contentious, maybe "evidence"?


crictl logs broken (1.9)

crictl logs yields the following error unconditionally:
FATA[0000] The container has not set log path

We can reproduce this in each of our deployments and also following the minimal example in the docs. We looked inside the issue and it seems that crictl isn't able to get the container's logPath right (it's always left empty). I have tested it with crio 1.9, which is setting the log files accordingly (I can see them in the logs and access them from the host).
I've seen some fixes for critools 1.10 indicating that the issue has been fixed. If so, is there any chance we can backport them to 1.9?
Unrelated to the issue but following the backporting question: Is there a policy or process established for critools to decide which commits should be backported? We're trying to roll fast and will update to K8s 1.10 in the coming months, but we usually need a few months of time.

Unrelated to the issue but following the backporting question: Is there a policy or process established for critools to decide which commits should be backported? We're trying to roll fast and will update to K8s 1.10 in the coming months, but we usually need a few months of time.

We gladly jump in to backport things if that would help.

I've seen some fixes for critools 1.10 indicating that the issue has been fixed. If so, is there any chance we can backport them to 1.9?

Which fix are you talking about? It seems to be a crio bug to me, which doesn't return LogPath in ContainerStatus.

Which fix are you talking about? It seems to be a crio bug to me, which doesn't return LogPath in ContainerStatus.

@Random-Liu I skimmed the history and saw a few commits related to logs. I am not sure if it's a crio bug as it works with kubectl logs.

@vrothberg Could you show the output of crictl inspect <container-id>?

By the way, with master branch, logs won't work with current examples. This is because logPath and logDirectory is not set. Opened #321 to reflect recent changes.

I took some more time looking into the issue and realized that logs work when using docker, so I begin to doubt my hypothesis that it's a crictl issue.
@feiskyer Below are the logs (when using CRI-O). The logPath is clearly empty which explains the error, but I am not sure why:
{
  "status": {
    "id": "e7afd83de2dd789e2d70958b7d9a18a42fddf06d590edab32690fb053e55ac10",
    "metadata": {
      "attempt": 0,
      "name": "dex"
    },
    "state": "CONTAINER_RUNNING",
    "createdAt": "2018-06-05T10:45:45.750328318Z",
    "startedAt": "2018-06-05T10:45:46.285758221Z",
    "finishedAt": "1970-01-01T00:00:00Z",
    "exitCode": 0,
    "image": {
      "image": "docker.io/sles12/caasp-dex:2.7.1"
    },
    "imageRef": "docker.io/sles12/caasp-dex@sha256:4997cc886a0c3c103588e5c4195725513bd4d6ab2e758764af00998dfe25c1bb",
    "reason": "",
    "message": "",
    "labels": {
      "io.kubernetes.container.name": "dex",
      "io.kubernetes.pod.name": "dex-7bcd9b8cb5-9bj5n",
      "io.kubernetes.pod.namespace": "kube-system",
      "io.kubernetes.pod.uid": "93c031ee-68ad-11e8-a946-5afab06adeee"
    },
    "annotations": {
      "io.kubernetes.container.hash": "5eea8f3d",
      "io.kubernetes.container.ports": "[{\"name\":\"https\",\"containerPort\":5556,\"protocol\":\"TCP\"}]",
      "io.kubernetes.container.restartCount": "0",
      "io.kubernetes.container.terminationMessagePath": "/dev/termination-log",
      "io.kubernetes.container.terminationMessagePolicy": "File",
      "io.kubernetes.pod.terminationGracePeriod": "30"
    },
    "mounts": [
      {
        "containerPath": "/etc/dex/cfg",
        "hostPath": "/var/lib/kubelet/pods/93c031ee-68ad-11e8-a946-5afab06adeee/volumes/kubernetes.io~configmap/config",
        "propagation": "PROPAGATION_PRIVATE",
        "readonly": true,
        "selinuxRelabel": false
      },
      {
        "containerPath": "/etc/dex/tls",
        "hostPath": "/var/lib/kubelet/pods/93c031ee-68ad-11e8-a946-5afab06adeee/volumes/kubernetes.io~secret/tls",
        "propagation": "PROPAGATION_PRIVATE",
        "readonly": true,
        "selinuxRelabel": false
      },
      {
        "containerPath": "/etc/pki/trust/anchors/SUSE_CaaSP_CA.crt",
        "hostPath": "/etc/pki/trust/anchors/SUSE_CaaSP_CA.crt",
        "propagation": "PROPAGATION_PRIVATE",
        "readonly": false,
        "selinuxRelabel": false
      },
      {
        "containerPath": "/var/run/secrets/kubernetes.io/serviceaccount",
        "hostPath": "/var/lib/kubelet/pods/93c031ee-68ad-11e8-a946-5afab06adeee/volumes/kubernetes.io~secret/dex-token-qrlk5",
        "propagation": "PROPAGATION_PRIVATE",
        "readonly": true,
        "selinuxRelabel": false
      },
      {
        "containerPath": "/etc/hosts",
        "hostPath": "/var/lib/kubelet/pods/93c031ee-68ad-11e8-a946-5afab06adeee/etc-hosts",
        "propagation": "PROPAGATION_PRIVATE",
        "readonly": false,
        "selinuxRelabel": false
      },
      {
        "containerPath": "/dev/termination-log",
        "hostPath": "/var/lib/kubelet/pods/93c031ee-68ad-11e8-a946-5afab06adeee/containers/dex/0acacc1a",
        "propagation": "PROPAGATION_PRIVATE",
        "readonly": false,
        "selinuxRelabel": false
      }
    ],
    "logPath": ""
  }
}

Closing the issue as it turns out to be a crio issue: https://github.com/kubernetes-incubator/cri-o/pull/1591#issuecomment-394734679

Hi, any updates ?

this should be fixed, and 1.9 is out of support. are you encountering this in a newer version?

Hi @haircommander .  thanks for the reply
Yes. i have opened issue about this.
https://github.com/kubernetes-sigs/cri-tools/issues/1078


Which versions of UWP?

My App targets Windows 10 version 1809 and also has it as Minimum version. I cannot find this property.

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

ID: 08b14dc1-9480-76fb-db85-308d0dcec01f
Version Independent ID: 1dc3033d-ea42-c97d-81b5-caa9e5ef5dc6
Content: NavigationView.SettingsItem Property (Windows.UI.Xaml.Controls) - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.ui.xaml.controls.navigationview.yml&version=GBlive&_a=contents
Product: uwp
Technology: winrt-reference
Git Login: jwmsft
Microsoft Alias: jimwalk

The doc page isn't showing the versions which we will look into separately. But SettingsItem property existed since the beginning of NavigationView (16299) so I wouldn't expect that NavigationView would work but SettingsItem doesn't. Can you provide more details?


Different MCMC back-ends

Currently the back-end for running the MCMC is the emcee python code, but other back-ends using different stochastic sampler methods could be used. A couple of thoughts are:

DNest3 (diffusive nested sampling) - this would require the site to produce and compile a C++ code, rather than a python script (unless using e.g. PyDNest). This would enable evidences to also be produced.
LibBi (sequential Monte Carlo) - the script could then produce the file in the LibBi modelling language (see the manual). Code is on github here.
Stan (Hamiltonian Monte Carlo) - there is a python interface for this.
PyMC - another tool including MCMC.
probably some more (BUGS, JAGS, ...)

One of the main reasons for using emcee is the general lack of problem specific tuning required, so it's worth seeing what level of tuning the other options require. I think all of the above are open source and with a GPL (or equivalent) license, so there should be no licensing issues.
It is probably worth checking out the speed of each, and what problems they are most useful for.

Another option would be to use nestle, which is a pure python nested sampling using the MultiNest algorithm. This should be relatively simple to add.

A further option is https://github.com/johnveitch/cpnest as a nested sampling method. Again, this should be relatively simple to add.

Closing this due to the use of bilby.


Docs for V4 navbar reference pull-xs-right

The documentation for the V4 navbar uses the class pull-xs-right for the inline form, but there is no such class. pull-right works.

Already addressed in v4-dev branch, where the plain pull-right no longer exists.


iOS Build Fails with Linker Errors

## Environment
(Note: I've also tried with Xcode version 14.0.)
Flutter version: 3.19.5
receive_sharing_intent version: 1.6.8 (I also tried version 1.6.7.)
iOS version: 13.0
Xcode version: 15.2
Description
When integrating receive_sharing_intent into my Flutter project, the iOS build fails with multiple linker errors related to CoreAudioTypes, Flutter, and undefined symbols for architecture x86_64. This issue persists despite following all the suggested steps in the documentation and attempting several troubleshooting steps.
## Steps to Reproduce
Add receive_sharing_intent to pubspec.yaml and run flutter pub get.
Follow the setup instructions for iOS as per the package documentation.
Attempt to build the project for iOS.
The build fails with the following errors:
ld: warning: Could not find or use auto-linked framework 'CoreAudioTypes': framework 'CoreAudioTypes' not found
ld: warning: Could not find or use auto-linked framework 'Flutter': framework 'Flutter' not found
Undefined symbols for architecture x86_64:
"FlutterMethodNotImplemented", referenced from:
receive_sharing_intent.SwiftReceiveSharingIntentPlugin.handle(: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in receive_sharing_intent[x86_64]6
receive_sharing_intent.SwiftReceiveSharingIntentPlugin.handle(_: __C.FlutterMethodCall, result: (Any?) -> ()) -> () in receive_sharing_intent[x86_64]6
"OBJC_CLASS$_FlutterEventChannel", referenced from:
in receive_sharing_intent[x86_64]6
"OBJC_CLASS$_FlutterMethodChannel", referenced from:
in receive_sharing_intent[x86_64]6
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
## Troubleshooting Steps Attempted

Ensured all setup steps in the package documentation were correctly followed.
Deleted the "Other Linker Flags" in the build settings of the share extension.
Changed the target iOS version to the same values.
Ran flutter clean, flutter pub get, and pod install after making changes (also cleaned the folder under Product before building).
Upgraded the package to version 1.6.8.
And perhaps more that I don't remember. I have been trying for a few days and have read all related issues here.

I would like to mention that it worked at the beginning of the week. I didn't change anything, and then it stopped working. The only difference was that I added signing details correctly, and all errors under "Signing & Capabilities" were resolved, and maybe I ran pod install again. Then, these errors showed up. I even deleted everything and tried a new project again on different Macs, and it also showed me the same error.
None of these steps resolved the build issues.
Any help or guidance would be greatly appreciated.

@KasemJaffer

Hi everyone,
I wanted to update this issue with the solution that worked for me, in case it helps anyone else facing a similar problem. After spending 5 days on this, I've finally resolved the issue with the following change in the Podfile:
Original Configuration:
target 'Runner' do   pod ...   use_frameworks! :linkage => :static end
Updated Configuration:
target 'Runner' do   pod ...   use_frameworks! end
The key was to remove :linkage => :static from the use_frameworks! directive.
I'm closing this issue now, but I hope this solution helps anyone who encounters the same problem.


Please update README.md

I recently tried using it by following the steps in the README.md file and it does not work, please update the file.
I keep getting this error when i try to export/set the API key
openai.error.AuthenticationError: No API key provided. You can set your API key in code using 'openai.api_key = ', or you can set the environment variable OPENAI_API_KEY=). If your API key is stored
in a file, you can point the openai module at it with 'openai.api_key_path = '. You can generate API keys in the OpenAI web interface. See https://platform.openai.com/account/api-keys for details.

Thanks, this may have a similar root cause as #589 I will look into that.

experiencing same issue.

I reproduced this, even with my API key set in .env (following the README) I get this error.
I will look into getting a fix out.

If you are still getting the error after my fix, perhaps there is a problem with how you are setting your API key.

are you using the .env file or the env variable?
Can you show exactly how you are setting the API key in 1 without posting your exact key, perhaps replace your key with random keystrokes.

I'm receiving an similar error, but in my case i can put the api keys:
"INFO:openai:error_code=invalid_api_key error_message='Incorrect API key provided: [sk-PSSF*****************************************UYc]. You can find your API key at https://platform.openai.com/account/api-keys.' error_param=None error_type=invalid_request_error message='OpenAI API error received' stream_error=False"

If you are still getting the error after my fix, perhaps there is a problem with how you are setting your API key.

are you using the .env file or the env variable?
Can you show exactly how you are setting the API key in 1 without posting your exact key, perhaps replace your key with random keystrokes.

I am using powershell. Still get same error.
$env:OPENAI_API_KEY = "[my key]"
error: openai.error.AuthenticationError: Incorrect API key provided: [*****************************************]. You can find your API key at https://platform.openai.com/account/api-keys.
I also updated main.py and set the api key directly in there; same error but slightly different message:
pydantic.error_wrappers.ValidationError: 1 validation error for ChatOpenAI
root
Did not find openai_api_key, please add an environment variable OPENAI_API_KEY which contains it, or pass  openai_api_key as a named parameter. (type=value_error)

Housekeeping: Closing stale issues.
Feel free to reopen if you're still having this problem!


Enhancement to Alerts/Incidents Fields

This request is coming from a specific Customer, but has stated the importance of tooltips, and would like all Alert and Incident fields should have tooltips to give a base level of info for what that field is for. This will help all users understand the purpose of each field.
Example- In Alerts module, Source IP is for a public source IP, while Local IP is for a private source IP

Thanks for reporting issue and we will address it in any upcoming releases.


[firestore-bigquery-export] switch to materialized views

Since this isnt using materialized views I need to scheduled copy its views into physical tables in order to use bigquery bi engine with it in google data studio.  if it was using mat views data studio could use accelerated access

Thanks @meyerovb
I have updated this for discussion.

@meyerovb thanks for the suggestion. is there anything stopping you from generating the materialized views yourself based on the gen schema scripts?

@i14h I have tried to create a Materialized View from one of the current views.  I had to reference the raw table (Materialized Views only work with native tables), rather than the <table>_raw_latest view and received the error Materialized views do not support analytic functions or WITH OFFSET.

HI @jasonberryman
Did you manage resolve a Materialised view for your project?
Based on the current data, this appears tricky as Materialised Views appear to be more limited than standard views.
I'll move this issue back to accepted to investigate whether a script os possible for this.

+1 vote for matterialized views

Hey guys, do you have any ideas how to create materialized view for <collection>_raw_latest views? latest views are using PARTITION BY and ORDER BY to fetch latest timestamp, flag if document is deleted etc. But, ORDER operation is not allowed in the BQ materialized views.
Any tips and tricks how to overcome this issue? I am thinking about writing Firebase -> BQ connector which will use DML to update existing rows. What do you think?

@cimox I have the same question. Have you found a way to achieve this?

@davestimpert I did not find a solution to this issue at the time. However, I created a custom set of materialized views to improve performance, which worked nicely for my use case. Unfortunately, I did not need to work with these Firebase export datasets since then, so no more progress on my end.

@davestimpert I am not maintaining that system anymore so writing it based on my memory from few years back. I think we used the raw_changlog table to create a materialized view that flattened all the columns. We couldn't do any filtering in this view, which is sad. Then we created a latest view based on it and used same logic as what Google gives in raw_latest. I had attended some Google sessions at that time and I had heard about some enhancements being planned by Google for materialized view that will make it easier for creating the latest_view from raw_changelog and have it materialized in one step. If you are a paid customer, it might not hurt to create a ticket for the Google BQ team to confirm the possibilities.

I dont know what I'm doing but maybe this query would do the trick ?
It seems compatible with materialized views, and how I understand it, MAX_BY will run for each GROUP
SELECT
  document_id,
  document_name,
  MAX(timestamp) AS latest_timestamp,
  MAX_BY(operation, timestamp) AS latest_operation,
  MAX_BY(data, timestamp) AS latest_data
FROM
  `xxx.xxx.raw_changelog`
GROUP BY
  document_id, document_name

It wont exclude the deleted documents, but materialized views seems to support WITH statements


feat: propagating ciru rpc response

This PR is aimed to return the resp from c.doSwrk. It's motivated primarily by the need to access the PID of the restored process, which isn't straightforward to do without getting the result from resp directly.

The main problem is that this PR changes the API which means that everyone including go-criu has to change their code. It would be good to understand what problem this PR is trying to solve. At this point I am not in favour of this change.

Yeah, I was afraid of the API change issue - but couldn't really see a way around it. I want access to the PID of the restored process, which I can't get without rpc.CriuResp. The alternative is not using go-criu and directly calling CRIU over RPC, as far as I can tell.
Finding the PID of the new process is especially useful for us because we're migrating the checkpoints to new machines.

Can't you use the notification mechanism? That should tell you the PID.

https://github.com/checkpoint-restore/go-criu/blob/633daeeea34e73411f21101f0e7f6cb207153172/main.go#L166 is still private and inaccessible from outside go-criu though?

@nravic Could you try with something similar to criuNotifications in runc?

@nravic Could you try with something similar to criuNotifications in runc?

I think runc doesn't really use go-criu because it is older than go-criu. That is the kind of the main question here. Directly doing RPC calls or going through go-criu. go-criu is easier to use but abstracts away some things.
But, @nravic , if you implement the PostRestore() callback you should get a notification which PID the restored process has. No need to access GetPid().


Question about exogenous variables

I noticed that only batch_x were passed in the model during training. Are the exogenous variables related to Datetimes not modeled in this architecture or it there a way to include them?

The neuralforecast's PatchTST implemention also declares itself as not supporting exogenous variables FYI. I'm not a professional in ML, just being courious that whether it's an
incomplete implemention or a limition by design.


multi: update dex client

Closes #632

I've noticed a few issues that I'm unable to resolve atm:

The server and market selection on the dex market page no longer stack on top of every element on the page when the dropdown is expanded
The dex market page doesn't scroll downwards unless the scrollbar is used (noticed the same thing on the post bond step).
The order type selection on the order form should be directly under the order type collapsed view.

I think issues arose after recent dropdown code changes and the gioui version update.

I have solved it

I've noticed a few issues that I'm unable to resolve atm:

The server and market selection on the dex market page no longer stack on top of every element on the page when the dropdown is expanded
The dex market page doesn't scroll downwards unless the scrollbar is used (noticed the same thing on the post bond step).
The order type selection on the order form should be directly under the order type collapsed view.

I think these issues arose after recent dropdown code changes and the gioui version update.

https://github.com/crypto-power/cryptopower/pull/633#issuecomment-2334526408 has been resolved by https://github.com/crypto-power/cryptopower/pull/633/commits/756a6cf52e188a2fb754f1cac9c1cf67ca4419a9

I found the logs, its checking bonds every millisecond?

Seeing some weird stuff with bonds. It's spinning sowhere:
2024-09-19 08:31:58.934 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.934 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.945 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.946 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.946 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.946 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.946 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.957 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.958 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.958 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.958 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.958 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.973 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.974 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.974 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)

Seeing some weird stuff with bonds. It's spinning somewhere:
2024-09-19 08:31:58.934 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.934 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.945 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.946 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.946 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.946 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.946 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.957 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.958 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.958 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.958 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.958 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.973 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.974 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)
2024-09-19 08:31:58.974 [DBG] DEXC: Soon to expire bond found: acec8ef3f7b76c10742240bbbd02b5120e813e0b2a60aa4ee4a08d38f2c329d9:0 (dcr)

I've investigated this.
dcrdex checks for bond rotation every bondTickInterval (20 secs) in watchBonds  and continues to log this until an okay bond has been posted. See: watchBonds  -> bondStateOfDex -> where the log actually happens
Same thing happens when a newly expired bond is found.

dcrdex checks for bond rotation every bondTickInterval (20 secs)

In my logs its logging 4 times per millisecond. It should only be once ever 20 seconds correct?

More odd logging, bot the number of times in a millisecond it happens and why it needs usdc.eth:
2024-09-24 06:16:15.007 [ERR] DEXC: couldn't find minimum lot size for usdc.eth
2024-09-24 06:16:15.007 [ERR] DEXC: couldn't find minimum lot size for usdc.eth
2024-09-24 06:16:15.007 [ERR] DEXC: couldn't find minimum lot size for usdt.eth
2024-09-24 06:16:15.007 [ERR] DEXC: couldn't find minimum lot size for usdt.eth
2024-09-24 06:16:15.008 [ERR] DEXC: couldn't find minimum lot size for eth
2024-09-24 06:16:15.008 [ERR] DEXC: couldn't find minimum lot size for usdc.eth
2024-09-24 06:16:15.008 [ERR] DEXC: couldn't find minimum lot size for usdc.eth
2024-09-24 06:16:15.008 [ERR] DEXC: couldn't find minimum lot size for usdt.eth
2024-09-24 06:16:15.008 [ERR] DEXC: couldn't find minimum lot size for usdt.eth
2024-09-24 06:16:15.008 [ERR] DEXC: couldn't find minimum lot size for eth
2024-09-24 06:16:15.008 [ERR] DEXC: couldn't find minimum lot size for usdc.eth
2024-09-24 06:16:15.008 [ERR] DEXC: couldn't find minimum lot size for usdc.eth
2024-09-24 06:16:15.008 [ERR] DEXC: couldn't find minimum lot size for usdt.eth
2024-09-24 06:16:15.008 [ERR] DEXC: couldn't find minimum lot size for usdt.eth

. it looks like func (pg *DEXMarketPage) exchange() *core.Exchange is being hit many times per millisecond

Aha, thanks. that's the other place bondStateOfDex is being called causing the spamming logs.

It looks like something else is still being hammered:
2024-09-25 04:44:16.196 [TRC] DEXC: wallet status requested for unknown asset 42 -> dcr
2024-09-25 04:44:16.340 [TRC] DEXC: wallet status requested for unknown asset 42 -> dcr
2024-09-25 04:44:16.345 [TRC] DEXC: wallet status requested for unknown asset 42 -> dcr
2024-09-25 04:44:16.359 [TRC] DEXC: wallet status requested for unknown asset 42 -> dcr
2024-09-25 04:44:16.373 [TRC] DEXC: wallet status requested for unknown asset 42 -> dcr
2024-09-25 04:44:16.401 [TRC] DEXC: wallet status requested for unknown asset 42 -> dcr
2024-09-25 04:44:16.425 [TRC] DEXC: wallet status requested for unknown asset 42 -> dcr
2024-09-25 04:44:16.453 [TRC] DEXC: wallet status requested for unknown asset 42 -> dcr
2024-09-25 04:44:16.453 [TRC] DEXC: wallet status requested for unknown asset 42 -> dcr
2024-09-25 04:44:16.479 [TRC] DEXC: wallet status requested for unknown asset 42 -> dcr
2024-09-25 04:44:16.863 [TRC] DEXC: wallet status requested for unknown asset 42 -> dcr
2024-09-25 04:44:16.870 [TRC] DEXC: wallet status requested for unknown asset 42 -> dcr
2024-09-25 04:44:16.907 [TRC] DEXC: wallet status requested for unknown asset 42 -> dcr

When I navigate to the dex onboarding page, it calls func (pg *DEXOnboarding) bondAmountInfoDisplay(gtx C) D and func (pg *DEXOnboarding) bondAccountHasEnough() bool about 30 times instantly. Do you know why? Is that just how it is? Seems like resources are being wasted. I guess because The logic is inside the view constructors? Is this correct?


Update devcontainer to install github cli, launch browser, run hugo serve

By default now runs "hugo serve" and auto launches a browser
in the host to display the live update of the page as you edit it.
Adds the github cli to dev container.
Signed-off-by: Ed Warnicke<EMAIL_ADDRESS>

Testing this is as easy as running code git-bom/site ! Thanks, Ed :)


Support escape characters

It seems that node-glob supports escaping special characters but this library doesn't.

good idea, I'll do this and https://github.com/jonschlinkert/is-glob/issues/4 today.

Awesome, much appreciated.

No problem, thanks for creating the issue. Let me know if you think of anything else


Grammar compatibility on android7 webview

Describe the bug
When I accessing web with android7 webview, error message shows in logcat:
"Uncaught SyntaxError: Unexpected token {", source: https://<IP_ADDRESS>/@vite/client (493)
The following is the incorrect JavaScript fragment:
async function waitForSuccessfulPing(socketProtocol, hostAndPath, ms = 1000) {
....
catch { } //row 493
...
};
Reproduction
none
Steps to reproduce
none
System Info
System:
    OS: macOS 12.2.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 77.40 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 14.18.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.5.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 117.0.5938.149
    Safari: 15.3
  npmPackages:
    @vitejs/plugin-legacy: ^4.1.1 => 4.1.1
    @vitejs/plugin-vue: ^4.2.3 => 4.3.4
    vite: ^4.4.5 => 4.4.9

Used Package Manager
npm
Logs
"Uncaught SyntaxError: Unexpected token {", source: https://<IP_ADDRESS>/@vite/client (493)
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

This is by design, support for legacy browsers is a build-only feature. During dev mode, Vite doesn't transpile files.


Bugfix for Python 3.9

Overview
In Python 3.9, typing.Callable is deprecated, in favor of collections.abc.Callable. Thus, the code needs to be updated accordingly.
Reason
get_type_hints for collections.abc.Callable returns in format [[…], …] instead of […, …], the latter of which is the case for typing.Callable.
Additionally, collections.abc.Callable is a class instead of data.
Example
With typehints_fully_qualified = True for clarity.
Tested on Python 3.9.1 (tags/v3.9.1:1e5d33e, Dec  7 2020, 17:08:21) [MSC v.1927 64 bit (AMD64)] on win32.
Should be

But got

After the bugfix

Please add a test that fails without this fix.

Also please rebase against master, as the previously failing tests have been fixed there now.

I have added the test case here. But the check failed.
I tried to test on the current master branch, but got the same warning. I suppose this is not due to my changes.

The spot where the check failed relates directly to your patch. As for the warnings you see, those are normal.

You should probably test with tox locally to see if the tests pass before pushing more commits to the PR.

You should probably test with tox locally to see if the tests pass before pushing more commits to the PR.

Thanks for the comments. I will do it next time.

Pull Request Test Coverage Report for Build 695552377

6 of 7 (85.71%)  changed or added relevant lines in 1 file are covered.
12 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 88.528%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sphinx_autodoc_typehints.py
6
7
85.71%

Files with Coverage Reduction
New Missed Lines
%

/tmp/pytest-of-runner/pytest-0/dummy/dummy_module.py
12
78.46%

Totals

Change from base Build 695222096:
-0.3%

Covered Lines:
463

Relevant Lines:
523

💛  - Coveralls

I checked and the tests pass even without this patch.

Never mind, I didn't patch all the necessary files.

@zwang123  I've rebased on main, can you please fix the CI, thanks!

Closing due to inactivity, please reopen a new PR in case you'd like to pick it up again. Thanks for the understanding!


tests: adds support for testing multiple image types

Now the CI tests can take input for each testing scenario specifying which image to build and test. For example, now the ceph_ansible2.1-jewel-centos7_cluster testing scenario is actually building and deploying a centos7 jewel image.

jenkins test ceph_ansible2.1-jewel-xenial_cluster

jenkins test this please

jenkins test ceph_ansible2.1-jewel-xenial_cluster

jenkins test ceph_ansible2.1-jewel-xenial_cluster


when >= FILES_MAX, do not use this Plugin, will cost too much time.

when >= FILES_MAX, do not use this Plugin, will cost too much time.

Hey @JaredDC thanks for the PR!
Had a question here. How did you choose the value for FILES_MAX? I created a folder with 500 files and it barely took a second to show all of them. I'm just thinking that with git repos and all having lots of tiny files, 300 might get exceeded rather too quickly. Running the plugin on my Program Files, it took around 2 seconds for 100,000+ files.

Hey @JaredDC thanks for the PR!
Had a question here. How did you choose the value for FILES_MAX? I created a folder with 500 files and it barely took a second to show all of them. I'm just thinking that with git repos and all having lots of tiny files, 300 might get exceeded rather too quickly. Running the plugin on my Program Files, it took around 2 seconds for 100,000+ files.

This is my point of view.
When there are too many files, it is not appropriate to display in the form of a directory, or use a depth form like 'tree -L 3' command in Linux to show less files. tree command
300 may be a more appropriate value.

Oh, do you mean more than 300 files in the same directory?
If that is the case, correct, it is not really appropriate. But, it is not appropriate for that subfolder if it was inside. Do we not want to show the parent folder too in that case?
I will try once with your patch when I have time to see the behaviour and will let you know.

fix pack-zip.ps1 error by
cd "$(SolutionDir)Scripts"
powershell -file "$(SolutionDir)Scripts\pack-zip.ps1"

Here is an example, there are no folders with more than 300 files here. I would really like to be able to open the folder to go to the bin folder and open the executable directly. Seems too limiting. If it was a limit of 300 files only in that folder, I would see that making sense. But then, it would need to have lazy loading as and when sub folders are expanded to have any advantage.

If you would like to use it, here is the link to the build. Let me know if it suits you. At this point, I do not feel it is a useful limitation to impose. Let me know if you have other thoughts on this.

When there are dozens(may be just 30) of video files in the folder, this plugin will be really slow

Okay, just verified that now, it is true. Looks like the thumbnail generation takes time for video files. @mooflu thoughts on this issue?


limitcpu: 3.0 -> 3.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/limitcpu/versions.
meta.description for limitcpu is: A tool to throttle the CPU usage of programs
meta.homepage for limitcpu is: https://limitcpu.sourceforge.net/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.1 in filename of file in /nix/store/3wc0rkn5j4a616761xr3fdcfsngqbka1-limitcpu-3.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

limitcpu

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3wc0rkn5j4a616761xr3fdcfsngqbka1-limitcpu-3.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A limitcpu https://github.com/r-ryantm/nixpkgs/archive/b6f9a438d719cd4082545511fdb29a5f38f71b63.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b6f9a438d719cd4082545511fdb29a5f38f71b63#limitcpu

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3wc0rkn5j4a616761xr3fdcfsngqbka1-limitcpu-3.1
ls -la /nix/store/3wc0rkn5j4a616761xr3fdcfsngqbka1-limitcpu-3.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

limitcpu

Maintainer pings
cc @rycee for testing.

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

1 package built:

limitcpu


Support post deployment test integration

Add support for following use case:

Things the post deployment step might need to do:

Wait/Trigger on a condition such as:

Enough time passed since deployment
Deployment is stable (i.e. no changes within interval?)

Run "standard K8s" tests such as:

All resource status is "green"
No error Events on resources(?)

Run customized tests (bring your own test pod?)
Mark failed/passed with Event
Set passing status along with latest commit status

[ ] ***Manifest resources - status lastBuiltCommit and Synced condition updated to reflect post test status
[ ] ***Manifest resources - add passConditions
[ ]

available options

kubectl rollout status deployment myapp (and configured with these)
life-cycle probes
helm tests?
octopus
kube-monkey
kube-hunter
kube-burner
kube-bench
kubetest2
e2e-framework
Bash Automated Testing System
DETIK
KIND?

After some research
It looks like there is no standard. Many solutions are available some more automated than others. All solutions require lots or scripting to integrate with other solutions and CI/CD frameworks.
Thus a solution here must include

Waiting for pre-condition
Triggering a custom workload (with any testing solution preferred)
Waiting for testing workload to complete
Determining outcome and configuring status accordingly

pre-condition, completion-condition and outcome-condition

Time since ???
Readiness of ???
Annotation check
Label check
Status check

All of these may be possible using jq or yq given a resource definition.
Custom workload

Container
Pods
Jobs/Deployments
More complex setups - e.g. services/roles etc...

While being under permissive is not desired - over complicating the setup may also be counter productive.
Allowing a Pod definition might be a good comromise.


use of offsetname?

quick question for use on offsets i havent been able to find anything on.
constexpr std::ptrdiff_t dwPrediction = 0x181A850;
constexpr std::ptrdiff_t dwEngineViewData = 0x5ECBFC;
constexpr std::ptrdiff_t dwNetworkGameClient_isBackgroundMap = 0x281477;
constexpr std::ptrdiff_t dwSoundService = 0x5ECB60;

dwPrediction is a pointer to the CPrediction class.
dwEngineViewData was added by this pull request.
dwNetworkGameClient_isBackgroundMap is used internally within the CEngineClient::IsInGame function.
dwSoundService is a pointer to the CSoundService class (see above pull request).


executor: drop kernel32-sys dependency

Fixes #227

CI seems down ATM, otherwise LGTM :rocket:

spurious network failures

Ok so the last error happens sometimes, it seems to be a network issue (The CI seems a bit off lately) Looks good to me, thanks!


Force creation of timeline if none exists

On first start or when all timelines are removed, we can still add images or videos to a none existing project. That will not be saved.

Idea: Leave everything as it is, but when the user clicks on a day instead of showing the file chooser, display the "create new timeline" dialog.


Implemented resolving of Binding Expressions

This is a fix for issue #12 that works for me. I'm not sure if this is the correct way to do such things, but at least it works for my use case. Maybe you consider taking it over to your official version of the MQTT Extension.

Great! Will review/test/release next friday!

Hi, I've checked the issue. It seems that you're using a CustomConfigProvider. The build-in NameResolver was not applied in that situation. This I fixed with https://github.com/keesschollaart81/CaseOnline.Azure.WebJobs.Extensions.Mqtt/commit/3641511ce7f0839552f447c05b4104e7d4766edc
It leverages the frameworks ResolveWholeString. If you agree my solution is better, I'll close this PR and #12.


Create Kali image with SSH server

Create Dockerfile.sshd that adds openssh-server so the container can accept SSH connections, and run as a detached container.
Host keys needs to be deleted and it should also allow to load them as well as user .ssh directory via a volume. If not provided, it should automatically generate the host keys.

Basic version created, see 23884ed71a76d9286ccc620192da47986b992dd4


Don't autorun tray icon when start ubuntu

Don't autorun tray icon when start ubuntu !

Did you try enabling the "Tray Icon" item in the "View" menu? That worked for me once I enabled it, and the tray icon re-appeared when I restarted the program as well.

i enabled but i'm not working

Please test if the latest release did solve this. If not please reopen the issue or create a new one and tell us. I will be closing this one for now.
Thank you!


When I use Cesium.Cartesian3.lerp to calculate the point, it will jump to the page path address

When I use the Sandcastle example, it can run normally, but when I open a new page directly and run it directly in the console, it will jump to the path.
http://localhost:544/Apps/HelloWorld.html to http://localhost:544/Apps/(-2379556.799372864,%20-4665528.205030263,%203628013.106599678)
Sandcastle example:
https://sandcastle.cesium.com/index.html#c=jZFRT8MgFIX/CulTm1RKoQWadYvJXjU+mPjUF9ahIzJoKO0yf710m3PTxcgT957z3XMDo3BgVHInHZgDI3dgKXs1bOHLoRc3UXuol9Z4oYx0TZTMGtOYMXDatsIrawJ5opbC+XAThkAtXRc3BoRzMfbbcNIAuMOEVWVJIasqwjCnRXqWCkrLEnOIUYkIwpScJUIxRzmBOaJlVVHGj0KS/juSIgIZYkWOCCvYdSbFBBa8qhDmV5GMUwQ5ZqgoKbtOfBR+Azu7i1EK8N9rJJOYzKI0qnu/13LxlXCvtp11HgxOxxBmXm47LQKVrYb2XXrY9v30+pO1zi7Req1GoNbzG98FWi36Piivg9bP6kM20aLOgv8Xqq1YK/P2NEqnxX6ybfLFw7EJIayzUN4mvbV6JdyPyZ8
Browser:
chrome 91.0.4472.101(64)
Operating System: Win10
Cesium Version: 1.82

Hi @xiaobaogeit ! I'm unable to replicate this on my device, so I'm not sure what's wrong.

You can try the code
<!DOCTYPE html>

    <meta charset="utf-8" />

    <meta http-equiv="X-UA-Compatible" content="IE=edge" />

    <meta
      name="viewport"
      content="width=device-width, initial-scale=1, maximum-scale=1, minimum-scale=1, user-scalable=no"
    />
    <title>Hello World!</title>

@xiaobaogeit What do you mean by running it in console directly - are you running the lerp code in the browser's JS console? What behavior are you seeing when doing so?

@ebogo1  You can watch this animated picture, or you can directly use the code of the entire page I posted before, and the effect will jump to the URL.


[docs] Add Kyuubi JDBC config section

What changes were proposed in this pull request?
Add Kyuubi JDBC config section in Hue Document
https://docs.gethue.com/administrator/configuration/connectors/
How was this patch tested?

(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)

Please review Hue Contributing Guide before opening a pull request.

Thanks for your review @pan3793!
@pan3793 @chengduhaha Possible to add the JDBC interface section for Hue at https://kyuubi.readthedocs.io/en/master/client/bi_tools/hue.html?

@chengduhaha would be great if you could send a PR to update Kyuubi docs as well.
@Harshg999 I wrote the original https://kyuubi.readthedocs.io/en/master/client/bi_tools/hue.html about 2 years ago, I will appreciate it if you can help check if something is wrong or outdated :)

BTW, Kyuubi provides a docker compose based playground for testing and dev cases
https://github.com/apache/kyuubi/tree/master/docker/playground

I am going to update the Kyuubi docs PR. Thanks!
在 2024-01-04 20:49:56，"Cheng Pan" @.***> 写道：
@chengduhaha would be great if you could send a PR to update Kyuubi docs as well.
@Harshg999 I wrote the original https://kyuubi.readthedocs.io/en/master/client/bi_tools/hue.html about 2 years ago, I will appreciate it if you can help check if something is wrong or outdated :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Hi @pan3793 , I updated the Kyuubi docs , please review. Thanks for your patience. :)

@pan3793 The original https://kyuubi.readthedocs.io/en/master/client/bi_tools/hue.html looks good to me.
We have now removed support for Hue related to CDH 6.x but if anyone is using it, then it should work fine. Maybe good to add a deprecated title or something for it?

@Harshg999 thanks for checking.

We have now removed support for Hue related to CDH 6.x but if anyone is using it, then it should work fine. Maybe good to add a deprecated title or something for it?

I suppose the CDH 6 user should know it's EOL now. Kyuubi also supports the EOL versions of Zookeeper, Hive, etc, we don't emphasize the deprecation message either. Keeping support for an EOL third-party component is quite a common case, especially those versions are adopted widely. The latest Spark 3.5 even supports Hive Metastore 0.12!

the content LGTM, is the CI failure related? Maybe code style issue?

the content LGTM, is the CI failure related? Maybe code style issue?
he code style is good. The failed log is about a connection refused, as shown below.

Built in 965 ms
Watching for changes in /root/repo/docs/docs-site/{archetypes,content,layouts,static,themes}
Watching for config changes in /root/repo/docs/docs-site/config.toml
Environment: "development"
Serving pages from memory
Running in Fast Render Mode. For full rebuilds on change: hugo server --disableFastRender
Web Server is available at http://localhost:1313/ (bind address <IP_ADDRESS>)
Press Ctrl+C to stop
http://localhost:1313/user/browsing/
dial tcp4 <IP_ADDRESS>:443: connect: connection refused       http://www.cloudera.com/documentation/enterprise/5-5-x/topics/search_mapreduceindexertool.html


Feature request to enable adding custom toolbar buttons in plugins.

I am currently working on a plugin for the editor, that allows users to motivate a selected section of text with an external source.
Currently, by following the documentation, plugins access events through their execute method, where they can match patterns in the text to execute some plugin logic (such as the date plugin matching a written date, or the dbpedia plugin matching the "dbp:" prefix.)
As the RDFa-editor handles toolbar buttons, it would be useful if plugins could add their own toolbar button(s), and receive the events of these buttons.
This feature would provide users of the editor with a more straightforward interface with their installed plugins, instead of having to remember the exact prefix string to execute the functionality of a certain plugin.
Concretely, adding this feature requires a new method for the editor, for example:
editor.addToolbarButton(eventName: string, pathToIcon: path)

that adds a new button to the toolbar, using the passed icon (or another way that can be used to pass an icon to the toolbar).
Secondly, the event of this button click should be passed to the plugin.
This could make use of the already existing execute interface, but needs a way to distinguish the button event from different buttons and from text updates. This could be using an optional eventName parameter for example, as this does not break compatibility
An example of an implementation of this feature could be:
export default Service.extend({
  init(){
    this._super(...arguments);
    this.get('editor').addToolbarButton('myPluginEvent', 'myPluginIconPath') // If you can access the editor in the init method
  }

 execute: task(function * (hrId, contexts, hintsRegistry, editor, eventName) {
    if (eventName === 'myPluginEvent') {
        selectedText = editor.currentSelection()
        // Handle selected text
    } else {
        // Regular plugin  behavior
    }
  })
})

I currently have not enough experience with Ember and the RDFa-editor to create a pull request by myself,
but if there is interest for this feature I am certainly willing to help.
Kind regards,
Ruben

the input is much appreciated @Dexagod . We definitely want to make the toolbar more dynamic in the future, but are currently focused on core editor behaviour (backspace, delete, ...) so I doubt we'll get to a clean API for this case soon.
You could try out an undocumented API for plugins that might suit your use case. It's been in use for about 2 years now so it's unlikely to be removed or changed. let us know if this is the route you'll take, so we can keep backwards compatibility in mind if it does need to change.
A plugins service can implement the suggestHints callback. This is triggered when a user pushes the add annotation button. The callbacks has two parameters. The first is the rdfaBlocks of the current selection (what was previously called "contexts"). The second is an api for the editor, that allows you to do updates.
import Service from '@ember/service';

export default class RdfaEditorSamplePluginService extends Service {
  /**
   * @property rdfaBlocks rdfaBlocks for the current selection
   * @property editor
   */
  async suggestHints(rdfaBlocks, editor) {
    return [{component: 'annotate-text', info: { editor }}];
  }
}

in the component you could do the following:
import Component from '@glimmer/component';
import { action } from '@ember/object';

export default class AnnotateTextComponent extends Component {
  get editor() {
    return this.args.info.editor;
  }

  @action
  async insert(annotation) {
    const selection = this.editor.selectCurrentSelection();
    this.editor.update(selection, { set: { property: 'http://purl.org/dc/terms/description'}});
    this.args.closeHints();
  }

  @action
  closeHints() {
    this.args.closeHints();
  }
}

with a template like this
<div>
<button {{on "click" this.insert}}>annotate as description</button> <button {{on "click" this.closeHints}}>close</button>
</div>

If useful the sample plugin is available here: https://github.com/nvdk/ember-rdfa-editor-sample-plugin
known issues:

probably broken on empty selection (e.g. a caret), assumes text is selected.
some selections run into an error in ember-rdfa-editor <= 0.40.0. It seems its not always splitting text nodes correctly when required. This is fixed on the dev branch of ember-rdfa-editor and should be in the next release of ember-rdfa-editor.


Fix Memory16 soundness

See this comment.
I went with option 2: The memory machine directly proves that the address increases. Just costs us one extra witness column to store the carry bit. I don't think it's worth calling the AddSub16 machine instead. I also think witgen might be simpler, because otherwise the memory machine would need to do a large number of AddSub16 calls when finalizing (which would fail if AddSub16 is already finalized).
To test:
cargo run -r pil test_data/std/memory16_test.asm -o output -f --field bb --pr
ove-with plonky3-composite

(Note: This doesn't test that the permutation constraint is satisfied. Doing --field bn254 --prove-with halo2-mock would be better, but on BN254 witgen currently selects the wrong memory machine to do witness generation.)

I found a way to remove the extra carry column! Now there is only one extra column with this PR, to store the second address limb.

OK, think it's sound now, BUT now that we represent both the address and time step as two limbs, we can actually reduce complexity again ^^
Basically, to compare the time step, we can do the same as for comparing the address: Let the prover provide whether the higher limb is equal, then:

If yes, assert that this is indeed true and assert that the lower limb is less
If no, assert that the higher limb is less

This way, we don't need the two branches in witgen and the weird tmp columns with different semantics depending on the case.
I can do this after the summit. Marking this as ready for review in case you want to merge before, because I can also do it in a different PR.

Nice, thanks! I'll merge it into my PR since we still need to do some reviewing there.


Pass lr_scheduler to Accelerator.prepare

This PR adds support for passing the learning rate scheduler to Accelerator.prepare. This only concerns learning rate schedulers that are called at each optimizer step, not schedulers that are called at the end of each epoch.
Why?
There are three reasons motivating this change:

users don't always remember they have to define the scheduler after they have prepared the training dataloader (since its size changes). This way is easier.
the scheduler step should be synchronized with the optimizer step, so when the step is skipped for the optimizer (in mixed precision), it should also be in the scheduler. With this PR, this is now the case.
this will unlock more cases where the optimizer step is skipped: having Accelerate automatically handle gradient accumulation

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Failed upgrades/downgrades can suppress exceptions

Currently if a database upgrade or downgrade fails, a call to onMigrationFailed() is made to give an opportunity to take corrective action. Because this is not an abstract method and the default implementation is a noop, this effectively suppresses exceptions by default.

Closed by #43


train problem

for example,if i use celebahq,i should follow the cmd：python train.py --dataset celebahq --data_file /data/yiwang/download/celeba_hd_256/train.txt --gpu_ids 0 --max_iters 80000 --g_cnum 64 --pretrain_network 1 --batch_size 8 --model srn --feat_expansion_op subpixel --random_mask 1 --random_crop 0 --use_cn 1
what's the train.txt? how should i get it when the dataset is Paris-Streetview?

The mentioned train.txt is a file storing the full paths of the training images, like:
/data/face/0x1.png
/data/face/0x2.png
...
/data/face/0f4.png
To generate the corresponding training file of a given dataset, you can traverse all its training data and write their full paths into a file.

ok！thank you ,and another problem occured,
No such file or directory: './checkpoints/20190717-153620_./dataset/Paris_Streetview/paris_train_original_srn_subpixel_contextual_b8_s936x537_gc32_dc64_rand-mask'

It seems some input options are invalid. The input for the option --dataset is just a dataset name like 'paris_streetview' instead of a path. If given a path, the creation of checkpoint folder would fail.

thank you for your answer!but the problem still happen,my paris-streetview include 3 folders and 1 file,paris_eval_corrupted, paris_eval_gt, paris_train_original and paris-streetview.txt .  The paris_train_original image shape is 936X537. So i follow the cmd:
python train.py --dataset paris_streetview --data_file ../paris_streetview.txt --gpu_ids 0 --img_shapes 936,537 --pretrain_network 0 --batch_size 8
by the way,my paris-streetview like this:
/dataset/paris-streetview/48.842502_2.344968_270_-004.JPG
/dataset/paris-streetview/48.842502_2.344968_90_-004.JPG
/dataset/paris-streetview/48.842513_2.343543_270_-004.JPG
/dataset/paris-streetview/48.842513_2.343543_90_-004.JPG
/dataset/paris-streetview/48.842529_2.369006_270_-004.JPG
/dataset/paris-streetview/48.842529_2.369006_90_-004.JPG

About the experimental settings, you can refer to our paper. We use randomly cropped 256x512 (hxw) images from paris-streetview for training and 256x256 images in eval_gt for evaluation.


Updating Plugin from 0.8.5 to 0.8.7 version is breaking for iOS.

🐛 Bug Report
I just updated my plugin from 0.8.5 to 0.8.7 and same code is placed, but it is not playing for iOS devices.
It should play for all devices.
Reproduction steps :-

Uodate Mediamanager plugin.
Write code to play mp3 url.

async void playAudio()
        {
            var item =  await CrossMediaManager.Current.MediaExtractor.CreateMediaItem("https://file-examples.com/wp-content/uploads/2017/11/file_example_MP3_5MG.mp3");
            item.MediaType = MediaType.Audio;
            item.Album = "Kishor";
            item.Author = "Geeky";
            item.Title = "Impelsys";
            item.Artist = "Prinju";
            await CrossMediaManager.Current.Play(item);
            //await CrossMediaManager.Current.Play("https://file-examples.com/wp-content/uploads/2017/11/file_example_MP3_5MG.mp3");
        }

Version: 1.x
Platform:

[ ] :iphone: iOS
[x] :monkey: Xamarin.Forms

It works. See sample project: ElementPlayer.Forms.iOS

ElementPlayer.Forms.iOS

Where can I see @adambarath ?
Thanks

https://github.com/martijn00/XamarinMediaManager/tree/develop/Samples/ElementPlayer.Forms.iOS


Make it possible to run tests only

Coverage remained the same at 40.97% when pulling fede8b3ec91416131c1b449075b29d1aa468a81a on jmontleon:tests-only into 339edf6314a8112b3b8c074ba82ebac9f8ee81a5 on openshift:master.

/lgtm

/lgtm


Added LPS33HW Pressure Sensor Driver

Added the driver for LPS33HW & LPS35HW Pressure Sensors from STMicroelectronics. The jd_sensor_api is also updated to include pressure and temperature reading APIs for the Pressure Sensors.

@mmoskal I made the changes and did the Clang formatting ( had to remove SortIncludes: false as it says undefined key ). I have 4 unused functions which I left for future usage in case someone wants to use the sensor in different configuration. Should I remove them or leave?
Everything else is good.

good to leave the functions, as long as they don't give warnings (you can make them non-static, use some magical attribute, or put them in #if 0)

@mmoskal Done!

Thank you very much!


New version: TortoiseSVN.TortoiseSVN version 1.14.29085

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

/azp run


Asset Management - Delete issue

Delete building return inconsistent message

Chrome cache cleared and tested again on QA test charger tenant same issue occurs again.

Provided a fix on SocketIO.
Just tested it in QA and no errors in the logs anymore:

I hope, this will work for good this time :S !


Broken link in comment

Richard Harter's webpage was taken offline after his passing in 2012. Fortunately, the whole site was cloned and put back online at http://www.richardhartersworld.com/, this corrects the link to his original code.

Thank you.


[Bug]: Unexpected behaviour with navigateTo

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Unexpected behavior when using navigateTo in the property pane.
https://user-images.githubusercontent.com/23132741/138678349-1380d740-ee96-4209-a75d-0783c3940604.mov
Steps To Reproduce

Open Property Pane for a widget.
Click on OnClick dropdown.
Select navigateTo from the options.
try adding string variable to route to navigateTo(variableName.replace("",""))
See the error

Environment
Production
Version
Cloud

This will be solved in when UI building pod changes the action selector

@Nikhil-Nandagopal In that case, shall we close this issue or keep it open for tracking?

@Rishabh-Rathod lets keep it open


ClassSignal: allow to access ClassSignal itself

This commit allows to do this:
class A:
    pChanged = ClassSignal()

class B(A):
    p = Property(Variant, getP, setP, notify=A.pChanged)

This looks good to me. Thank you for catching that!


ARTH Colours      Colors of the Earth Element are yellow, brown, taupe, beige.     YANG EARTH ELEMENT  Primary Stars: Hades, Demeter Organ: Stomach Colours: Light Brown, Yellow, Tan   YIN EARTH ELEMENT  Primary Star: Zeus Organ: Brain Colours: Brown, Beige, Khaki

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
ARTH
Colours
Colors of the Earth Element are yellow, brown, taupe, beige.
YANG EARTH ELEMENT
Primary Stars: Hades, Demeter
Organ: Stomach
Colours: Light Brown, Yellow, Tan
YIN EARTH ELEMENT
Primary Star: Zeus
Organ: Brain
Colours: Brown, Beige, Khaki
What part(s) of the article would you like to see updated?
ARTH
Colours
Colors of the Earth Element are yellow, brown, taupe, beige.
YANG EARTH ELEMENT
Primary Stars: Hades, Demeter
Organ: Stomach
Colours: Light Brown, Yellow, Tan
YIN EARTH ELEMENT
Primary Star: Zeus
Organ: Brain
Colours: Brown, Beige, Khaki
Additional information
ARTH
Colours
Colors of the Earth Element are yellow, brown, taupe, beige.
YANG EARTH ELEMENT
Primary Stars: Hades, Demeter
Organ: Stomach
Colours: Light Brown, Yellow, Tan
YIN EARTH ELEMENT
Primary Star: Zeus
Organ: Brain
Colours: Brown, Beige, Khaki

ARTH
Colours
Colors of the Earth Element are yellow, brown, taupe, beige.
YANG EARTH ELEMENT
Primary Stars: Hades, Demeter
Organ: Stomach
Colours: Light Brown, Yellow, Tan
YIN EARTH ELEMENT
Primary Star: Zeus
Organ: Brain
Colours: Brown, Beige, Khaki


VirusTotal scans

Hi I don't mean to accuse you of anything as I don't understand these things but why does virus total flag this as a trojan?
https://www.virustotal.com/gui/file/f6715a023490ca6ab119f6827c33dc697caee2f26a0ea95a13de070fb1e83fbb/behavior/VirusTotal Jujubox
https://www.virustotal.com/gui/file/36205472df8cfe6ad5bd740fa7aba7357430671ff1868a7451f2c5820c002451/relations

Use python version bro

What you mean?

I downloaded the exe from releases, then uploaded it to scan

It detects as a trojan because it reads and uses the combolist on mojang's api

Also where did you get that version OxygenX that is probably a ratted version since its bigger than mine

Oh OK thanks why does api detect as trojan tho just curious. Mb 2nd VT is linked to 1st VT under relations tab. So to reach the 1st link I posted, you go to relations tab on my second link and click the oxygen exe from execution parents

Everything from right here lol which is why confuse

How'd you see file size btw

Noob if you want you can attach the file you have onto a comment and I can check what the problem is.

I've already deleted the exe from my computer lol, just wanted to get some more info on why all the red on VT. Thanks though, the conclusion right now I have is that the 1st VT link is just an unrelated ratted version of the exe that prob also shows up on the scan bc they have the same code so comes under execution parents or something. Can anyone reaffirm this? Also 1st time github user should I close this thread

Well I could've reaffirmed it with the exe but rip. I guess this is closed just wait for Shadow to see the conclusion.

Maybe I can still find it somewhere, will have to check later though. I should clarify I only downloaded 1 file, and that was from github right here. There are 2 links I posted, the 2nd one I posted is the same as the one shadow did, my concern was mainly the 1st link I posted, which was found ON the virus total website as a relation.

Welp if you do find it tell me and I will check it to see if it is the same code as oxygenx or its a standalone because it is probably a ratted version of oxygenx which was detected by virus total as a relation as it contacts the same website (mojang auth server). If you do find it please attach it and I can check if it is this :)


[#noissue] Fix: Set baseApplicationKey in the transactionView page

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

Codecov Report

Merging #5350 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #5350   +/-   ##
=======================================
  Coverage   41.08%   41.08%
=======================================
  Files        2747     2747
  Lines       83014    83014
  Branches    11061    11061
=======================================
  Hits        34110    34110
+ Misses      45909    45908    -1
- Partials     2995     2996    +1

Impacted Files
Coverage Δ

...navercorp/pinpoint/rpc/common/SocketStateCode.java
82.92% <0%> (-2.44%)
:arrow_down:

...pinpoint/profiler/monitor/DeadlockMonitorTask.java
18.6% <0%> (-1.17%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
78.81% <0%> (-1.05%)
:arrow_down:

...rc/main/java/com/navercorp/pinpoint/test/Item.java
70% <0%> (ø)
:arrow_up:

...cluster/zookeeper/ZookeeperClusterDataManager.java
64.7% <0%> (+2.2%)
:arrow_up:

...tor/metric/datasource/DefaultDataSourceMetric.java
78.12% <0%> (+3.12%)
:arrow_up:

...pc/server/LoggingServerMessageListenerFactory.java
100% <0%> (+10%)
:arrow_up:

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 e5ec2c5...9dd7742. Read the comment docs.


[BUG] Error in the middle of indexing

Describe the bug
Marqo displays a server-side related error in the middle of idexing
To Reproduce

Index data using flax-sentence-embeddings/all_datasets_v4_mpnet-base model
Run the index script

Expected behavior
The index should be successfully done.
Screenshots

Closing issue as issue is with Marqo cloud.


Xcode 6.0.1 fails to load test bundle for iOS application test target

I'm having what appears to be a similar issue as #565 - my test bundle doesn't load in Xcode 6. It's an iOS app that's been around for a while, and I'm using CocoaPods to pull Kiwi in. Here's my environment:

Xcode 6.0.1
Kiwi 2.3.0 (I've tried HEAD as well)
CocoaPods
iPhone 6 Simulator (iOS 8)

And here's the error message:
IDEBundleInjection.c: Error 3587 loading bundle '/Users/josh/Library/Developer/Xcode/DerivedData/MyApp-eqkdocnxomrmqdcpsvnruhralyhf/Build/Products/Test-iphonesimulator/MyAppTests.octest': The bundle “MyAppTests.octest” couldn’t be loaded because it is damaged or missing necessary resources.
DevToolsBundleInjection environment:
XCInjectDiagnostics: (null)
XCInjectBundleInto: /Users/josh/Library/Developer/Xcode/DerivedData/MyApp-eqkdocnxomrmqdcpsvnruhralyhf/Build/Products/Test-iphonesimulator/MyApp.app/MyApp
XCInjectBundle: /Users/josh/Library/Developer/Xcode/DerivedData/MyApp-eqkdocnxomrmqdcpsvnruhralyhf/Build/Products/Test-iphonesimulator/MyAppTests.octest
TestBundleLocation: /Users/josh/Library/Developer/Xcode/DerivedData/MyApp-eqkdocnxomrmqdcpsvnruhralyhf/Build/Products/Test-iphonesimulator/MyAppTests.octest
TMPDIR: /Users/josh/Library/Developer/CoreSimulator/Devices/EDC94527-6C09-4DD9-ACFA-EA8F55316D4E/data/Containers/Data/Application/0A2BD137-EF66-4D2D-8EFA-24145EFA64AB/tmp
DYLD_LIBRARY_PATH: /Users/josh/Library/Developer/Xcode/DerivedData/MyApp-eqkdocnxomrmqdcpsvnruhralyhf/Build/Products/Test-iphonesimulator
DYLD_INSERT_LIBRARIES: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/PrivateFrameworks/IDEBundleInjection.framework/IDEBundleInjection
DYLD_FRAMEWORK_PATH: /Users/josh/Library/Developer/Xcode/DerivedData/MyApp-eqkdocnxomrmqdcpsvnruhralyhf/Build/Products/Test-iphonesimulator
Test target MyAppTests encountered an error (Test process exited with code 82)

So, the reason it turned out it wasn't working is that the frameworks were not copied under build phase.

@amol-c I have seen that issue before, but I think that's different to @joshuatbrown's original issue.
Speaking of which, is it still happening or did @tjarrat's fix work?

Hi,
I'm spending a lot of time looking for a workaround. I'm using an existing workspace and Cocoapods and now I'm adding the XCTest target, but when I ran this on iPhone6 simulator, it says
IDEBundleInjection.c: Error 3585 loading bundle 'PATH/TO/File.xctest': The bundle “TargetTest” couldn’t be loaded because it doesn’t contain a version for the current architecture.

While on other simulators (as iPhone4 and iPhone5 with different iOS version) it works fine.
Do you know something about this error? I also set Build Active Architecture Only to NO


Add support for aggregate functions (COUNT, GROUP BY, HAVING)

$ sqlitis "select count('typeID'),character_id from skills  where active>0 and ('typeID'=3337 or 'typeID'=3336 or 'typeID'=12212) group by character_id having count('typeID') =3"
ERROR: Failed to convert SQL: select count('typeID'),character_id from skills  where active>0 and ('typeID'=3337 or 'typeID'=3336 or 'typeID'=12212) group by character_id having count('typeID') =3
[BUG] Failed to convert 'typeID' to model

Yep, not all syntax is supported yet: https://github.com/pglass/sqlitis#sql-support-checklist

Also I was using double quotes and the message is different when using single quotes?

Can you be more specific about the quotations?
Do you mean this, (where all quotes are single quotes)?
$ sqlitis 'select count('typeID'),character_id from skills  where active>0 and ('typeID'=3337 or 'typeID'=3336 or 'typeID'=12212) group by character_id having count('typeID') =3'