Lags

Describe your bug here.
I have no idea why, but my game is lagging hard.
I only experienced this before on a few Mods or on the newest Kade Engine (Like the Camellia or Hex mods)
The 0.6 version is with it barely playable for me, with seemingly regular, like every 10 seconds, lag spikes, that last like 2-3 seconds.
Main issue might be haxe, or me having a built in graphics card tho
Idk, am not that smart with computers
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No

Also happens to me, hope this gets fixed.

Try again in 0.6.1
Close the issue if the problem was solved.

Issue remains.
Maybe even feels like it got worse somehow
Found out that botplay might not be included with the problem. only when you play yourself
Memory goes from 700 up to 750 MB and then goes back to 700, causing to freeze the screen (tested on week 7 - ugh)
Memory goes from 520 up to 570 MB and then goes back to 520, causing to freeze the screen (tested on week 4 - satin panties)


Error when executing group secrets

When executing the group secrets (with or without the -m option), when reaching the lambda section, an error appears saying:
[scan]	ERROR	No plugins to scan with!
Everything was being scanned fine, until it reached that point. Did I miss anything? Some requirements maybe?
After those errors (a lot of them, trust me), Prowler keeps scanning just fine actually.
Executed Prowler like this:
./prowler -g secrets -m 200
./prowler -g secrets
Thank you!

Hi @w0rmr1d3r, message[scan] ERROR No plugins to scan with! is not coming from Prowler, it should be from detect-secrets, the module that Prowler uses underneath. Look at here https://github.com/toniblyx/prowler/blob/master/include/secrets_detector and see how it is used, you can try manually as in line 44 and see if you get any result. I wonder if latest version of detect-secrets has some issues with plugins, they are all enabled by default but you can check it out with detect-secrets scan --list-all-plugins, more info here https://github.com/Yelp/detect-secrets#viewing-all-enabled-plugins

Hi @toniblyx !
I found more info!
The plugins are all installed, because running detect-secrets scan --list-all-plugins it prompts all the plugins.
So the issue must be with the lambdas.
I ran checks extra759 (Lambda variables) and extra760 (Lambda code). Like this:
./prowler -c extra759 and ./prowler -c extra760
The first one works just fine, it's the second one that gives that error.
Could it be due to the lambda function code being too large? Sometimes in AWS, if the lambda code is too large it isn't shown in the Console.

I know what is going on, if you run bash -x ./prowler -c extra760 -f <region> (the region part is to make sure it takes less time to finish since it does only your desired region). You will see the command that prowler runs underneath and then how detect-secrets fails when trying to analyze a zip file. I need to see what is wrong with it

I ran that, what it does, it downloads the zip file and unzips it in the tmp folder ./secrets-ACCOUNT_ID/ inside where the repo is (that's where I'm executing Prowler from).
When it unzips it, is when it prompts the messages.
The command Prowler is executing is:
detect-secrets scan --hex-limit 3.0 --base64-limit 4.5 --all-files ./secrets-ACCOUNT_ID/unziped_folder

Of course, replace ACCOUNT_ID and unziped_folder with correct values.
I tried to redirect the output (stdout and stderr) with COMMAND_FROM_ABOVE &> output.txt.
And opened that file, it just prompts the messages [scan]	ERROR	No plugins to scan with! and at the end it shows this:
{
  "version": "1.1.0",
  "plugins_used": [
    {
      "name": "ArtifactoryDetector"
    },
    {
      "name": "AWSKeyDetector"
    },
    {
      "name": "AzureStorageKeyDetector"
    },
    {
      "name": "Base64HighEntropyString",
      "limit": 4.5
    },
    {
      "name": "BasicAuthDetector"
    },
    {
      "name": "CloudantDetector"
    },
    {
      "name": "HexHighEntropyString",
      "limit": 3.0
    },
    {
      "name": "IbmCloudIamDetector"
    },
    {
      "name": "IbmCosHmacDetector"
    },
    {
      "name": "JwtTokenDetector"
    },
    {
      "name": "KeywordDetector",
      "keyword_exclude": ""
    },
    {
      "name": "MailchimpDetector"
    },
    {
      "name": "NpmDetector"
    },
    {
      "name": "PrivateKeyDetector"
    },
    {
      "name": "SlackDetector"
    },
    {
      "name": "SoftlayerDetector"
    },
    {
      "name": "SquareOAuthDetector"
    },
    {
      "name": "StripeDetector"
    },
    {
      "name": "TwilioKeyDetector"
    }
  ],
  "filters_used": [
    {
      "path": "detect_secrets.filters.allowlist.is_line_allowlisted"
    },
    {
      "path": "detect_secrets.filters.common.is_ignored_due_to_verification_policies",
      "min_level": 2
    },
    {
      "path": "detect_secrets.filters.heuristic.is_indirect_reference"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_likely_id_string"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_lock_file"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_not_alphanumeric_string"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_potential_uuid"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_prefixed_with_dollar_sign"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_sequential_string"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_swagger_file"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_templated_secret"
    }
  ],
  "results": {},
  "generated_at": "2021-05-31T06:33:38Z"
}

Hope it helps!

[scan] ERROR No plugins to scan with! is given when the zip file is in the folder. Seems like detect-secrets is not working as it was before. Looking at it.

I found the issue, seems to be a matter of python version https://github.com/Yelp/detect-secrets/issues/452

I checked my versions and guess what:
> detect-secrets --version
1.1.0
> python3 --version
Python 3.9.5

I prefer to wait for the issue Yelp/detect-secrets#452 to get resolved and fixed instead of forcing a downgrade in some dependencies, either that or we force prowler to use version 1.0.3 of detect-secrets until it gets solved.

Just tested with
$ detect-secrets --version
1.0.3
$ python --version
Python 3.9.4

so pip install detect-secrets==1.0.3 made the trick so far.

Correct!
I reinstalled detect-secrets with:
$ pip3 install detect-secrets==1.0.3
$ detect-secrets --version
1.0.3
$ python3 --version
Python 3.9.5

Executed:
./prowler -c extra760 -f eu-west-1

And isn't showing the error from before.
Shall we keep this issue open until it gets fixed from Yelp? What should we do here @toniblyx ?
Thanks!

To close it we should add that version constraint to the README, Dockerfile and Pipfile. Otherwise better to keep it open.

Okai! Let's keep it open!

I have updated README.md, util/Dockerfile and Pipfile with the proper version.


Consider changelog-maker

https://www.npmjs.com/package/changelog-maker

Nope. It's too specific to iojs


Stop generating button shows error message in UI

On clicking the stop generating button after asking Cody something it shows a new error message in the UI as Request failed: Socket hangup or Request failed: Aborted
https://github.com/sourcegraph/cody/assets/44617923/57c61308-fe99-46c3-83ba-00d6e0371dde
CC: @abeatrix @philipp-spiess

@deepak2431 ty. What version of the plugin?

@jdorfman While testing in the dev mode, I came across this issue.


Engrave cycloidal disc config

Engraved 1/4mm deep.

How wide are the engravings. Wondering if maybe it wont show up nicely

How wide are the engravings. Wondering if maybe it wont show up nicely

5mm tall, ~4mm wide

Is this the only pr needed to close #34?
Another option in simple parts like this one is that I can print the letter in like PLA in a different colour. Sort of like this print:
Also the only thing that matters in the gearbox is that there's one of each, right? doesn't matter which goes where for it to mate?

Is this the only pr needed to close #34?

Yup, forgot to link it whoops

Another option in simple parts like this one is that I can print the letter in like PLA in a different colour. Sort of like this print:

Missing pic? Also seems unnecessary tbh. We just need a tiny mark to make sure we have one of each

Also the only thing that matters in the gearbox is that there's one of each, right? doesn't matter which goes where for it to mate?

That's right

Whoops, dismissed reviews by enlargening the text to 8mm tall
@wmmc88 @wraftus


Make offline first

https://css-tricks.com/serviceworker-for-offline/

https://developers.google.com/web/tools/workbox/modules/workbox-webpack-plugin


adding Kotlin sample

Add Kotlin sample with example of "build.gradle.kts" file

Hello @jperedadnr ! Would be glad to have this merged :)
Thanks


The "onMouseMove" override was broken

Line 345 was if (!timeout.onMouseMove) when it should have been if (!options.onMouseMove, which caused overrides to fail.

Good catch! Thanks for your contribution!


Convert Publication Source

[my apologies if this is covered elsewhere...my first search didn't come up with anything]
What feature would you like to request?
The ability to convert from one publication source to another.
Is your feature request related to a problem? Please describe.
I would like to be able to

search for a publication
look up the cites_per_year

However, searching returns a pub with source PUBLICATION_SEARCH_SNIPPET and it needs to be AUTHOR_PUBLICATION_ENTRY.
Describe the solution you'd like
Externally, I have code that does this by

iterating through each author of the publication from a search
searching for publications by that author
check if the title matches the original publication paper

This seems like it would help torward doing away with the publication source altogether, so that you can "fill" the various sections.
Describe alternatives you've considered
It can be done externally, but the current implementation is a little confusing.
Do you plan on contributing?
Your response below will clarify if this is something that the maintainers can expect you to work on or not.

[x] Yes, I plan to contribute towards this feature in the next couple of days. if there isn't a reason not to do this

This is not going to be guaranteed in general, is it? a) You need to set filled = True in the search_single_pub function in your example b) not all authors have a Google Scholar profile that is public c) GS is going to link the Google Scholar pages of only the first few authors and not for everyone.
I'd be very happy to consider a PR from you if you could identify me (or any other GS profile) as an author on this paper, and get the cites_per_year from my (or any other) profile.

However, searching returns a pub with source PUBLICATION_SEARCH_SNIPPET and it needs to be AUTHOR_PUBLICATION_ENTRY.

As you've found out, publications in GS have different properties based on which database the result is fetched from. The Source attribute is meant to denote that, and indicate what other attributes to expect. In general, we leave it applications that build around scholarly to do the conversions that you mentioned here. This is because there are plenty of exceptions to the norm, and it's difficult to handle them all in general without knowing what you as a user are looking for. For e.g., if none of the authors of a paper have a public Google Scholar profile, there's no way to convert a result from PUBLICATION_SEARCH_SNIPPET to AUTHOR_PUBLICATION_ENTRY. So while the latter is usually the more useful one, the former will have to stay because it's the more generic one.

Ah, I see. I did not realize the operative property was having a GS profile. That makes more sense. Thanks!


Add winston

Description
Added Winston with the current config needs. Only works to output to console but can be changed to output to file if needed.
Winston added to dependencies
Fixes # (issue/ticket number)
Adding Winston for logging
Type of change
Setup
Tests:

I have checked error, warn, and info calls from a separate file in the same dir and it all works as expected.

Looks like there are some conflicts that need to be resolved before it can be merged in

Looks like there are some conflicts that need to be resolved before it can be merged in

Can you let me know where because GitHub says there are no conflicts with the base branch

hmm, github just says "This branch cannot be rebased due to conflicts" so i'm not sure

if you can't see the conflicts, maybe you can merge it?


Failing to compile socket2

Getting this error trying to build an empty project on Linux
❯ trunk build
  ❌ trunk | error
Error: bad status returned from cargo build:    Compiling socket2 v0.3.15
   Compiling syn v1.0.44
   Compiling instant v0.1.7
   Compiling pin-project-internal v0.4.27
   Compiling libc v0.2.79
   Compiling memchr v2.3.3
   Compiling log v0.4.11
   Compiling tracing-core v0.1.17
   Compiling futures-channel v0.3.6
   Compiling serde_derive v1.0.116
   Compiling maybe-uninit v2.0.0
   Compiling serde v1.0.116
   Compiling futures-task v0.3.6
   Compiling encoding_rs v0.8.24
   Compiling ryu v1.0.5
   Compiling serde_json v1.0.59
   Compiling http v0.2.1
error[E0432]: unresolved import `crate::sys`
  --> /home/mmstick/.cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.3.15/src/socket.rs:23:5
   |
23 | use crate::sys;
   |     ^^^^^^^^^^ no `sys` in the root

@mmstick thanks for opening an issue. At first glance, this does not appear to be an issue with Trunk. Trunk simply uses cargo to perform the build. If I was you, I would open an issue (well, first check the issues) in the socket2 repo.
From experience, typically when rust gives an error like that, it is probably because of some missing feature switch in one of your deps. I'll take a quick look to see if Google gives me any reasonable results.

@mmstick some quick googling led me here: https://github.com/async-rs/async-std/issues/505 Your socket2 does not yet support the wasm32 target.
A note on that, Trunk does indeed use Cargo as I mentioned above, however Trunk forces Cargo to build your project using the wasm32-unknown-unknown target. If the crate you are compiling is attempting to use OS specific interfaces which are not yet available for the wasm32 target, then you will get this sort of error.

This is a crate that Trunk is using to build with. I have no dependencies in this project.

Nevermind. There is in fact a dependency calling this


Native lib/code integration

Make it possible to add a custom kake.lua file in a project to link additional C/C++ code.

Done.


Minor: change doc formatting to force a republish

Which issue does this PR close?
Related to #5500
Rationale for this change
The  https://arrow.apache.org/datafusion/ site is currently broken

Somehow related to https://github.com/apache/arrow-site/pull/336#issuecomment-1480389066
What changes are included in this PR?
Change formatting of markdown (no content) to get the datafusion site to rebuild and republish
Are these changes tested?
No (I am testing live)
Are there any user-facing changes?
Docs

Well that appears to have fixed it now:


Consider Rust, Cargo and crates

CMSIS-Pack and CMSIS-Build focus on assembler, C and C++ as programming language at the moment.
@0Grit is requesting in the context of #43 to consider support for target software written in
Rust: https://www.rust-lang.org/
As well as looking at the concept of crates and packages managed using Cargo.
Crate: binary or library shipped as package
Cargo: the Rust package manager: https://doc.rust-lang.org/cargo/

From: @0Grit
Do not forget about Rust. It is quickly gaining momentum. New engineers feel no sense of attachment to C and will drop it like a rock.
Please 🥺🙏 consider looking at how Cargo and crates can be either used for inspiration or used directly to manage packs. Extend it if you have to.

From: @iomint
@0Grit : I do not see an issue in what is proposed here to handle a project from packs containing sw components developped in C language or in Rust. Do you ?

https://docs.rust-embedded.org/book/interoperability/rust-with-c.html

from: @0Grit
cmsis-build abstract the underlying build tooling from cmsis-packs? If so I trust your assertion.
I'm strapped for time and am unable to do much more than skimming of the materials. Just wanted to make sure these things are at least mentioned in the conversation. I've seen people like @ilg-ul who have a wealth of knowledge and work put into projects like this, get ignored in the past.
from :@fred-r
Well, I would think that:
the proposal is based on CMSIS-Pack components, so we can have a component providing RUST code
when it comes to the build chain, the spec lets it open I guess. Today it is proposing GCC, IAR and AC6 as a compiler but I assume we may support a toolchain with both C and RUST support ?
or maybe more realistic would be to mix C project and RUST projects compiled with their own toolchain each ?

I assume the major point you highlight is how to use both cargo and CMSIS packs ?
from: @ilg-ul
After embracing the CMSIS Packs idea and trying to use them for my projects (long time ago), I finally realised that their design has different goals, that do not match my criteria, especially in providing layer separation and reduced complexity.
Thus I designed xPacks, which are a more generic version of the highly successful, industry standard, npm packs.
In terms of the first criteria, layer separation, source xPacks are completely neutral to build processes, languages, platforms, etc.
In practical terms, source xPacks are collections of files with static dependencies to other xPacks, the same as npm packs are nodejs modules with dependencies of other packages.
Satisfying dependencies is a separate step that is executed before the build, to bring in all dependent packages, sources or binaries.
As for the second criteria, reduced complexity, CMSIS Packs favour very large packages (I saw some weighting hundreds of MB), with many, many source files, grouped in lots of components, each with its own version.
On the opposite end, xPacks (and npm packs), favour many small packages, each package having its own version, which applies to all files in the package.
Another major difference is that the main CMSIS Packs repository is centralised and not automated (or at least it was not when I used it, it required someone to accept the packages, and to update the index, which is, most of the time, outdated with vendor packages).
xPacks, being in essence npm packs, can be stored on any npm compatible server, like npmjs.com, GitHub, etc.
My 2 cents...
from @fred-r
==> to me this is the way CMSIS packs have been used so far.
The spec does not force you to do so.
I agree that it would be a much better practice to design smaller packs not mixing very different things.
The pack is only the way to convey the CMSIS components : this is the important point, designing consistent components.
from: @0Grit
I highly recommend looking at @ilg-ul's x-pack project. https://xpack.github.io/
I've used it and it's a great experience. He has packs to install toolchains, cmsis, etc. A lot of it sitting on top of NPM's infrastructure too. (Cross development host platform to boot)
The only thing preventing it from widespread usage is that he is basically the only person working on the project.
You would think he had a team considering how extensive the project is.
It would bring a tear to my eye to see some of his work be used by open-cmsis-packs somehow. Even if only by inspiration; though just using xpacks by itself and adapting the open-cmsis-packs spec to it would save everybody some time.
Not sure about how or if xpacks handles the "zones" concept though.
from: @ilg-ul
If allowed, multi-component packages may present additional challenges. Imagine you have multiple versions of a package which defines multiple components, each with its own version, all different in each package.
For whatever reason, a project may decide that it needs one component from one package version and another component from another package version. I did not check the recent specs, so I apologise if this is nonsense, but can the proposed package manager handle cases like this?
I don't know what the zones are, but I did a lot of thinking and experimenting with packages, and my current understanding of the subject is that any design that requires the packages to be identified by anything more than a (scoped) name and a semver, is a design too complicated.
As for what a package is, according to the npm documentation, "a package is any of the following":
A folder containing a package.json file.
A gzipped tarball containing (1).
A URL that resolves to (2).
A <name>@<version> that is published on the registry with (3).
A <name>@<tag> that points to (4).
A <name> that has a latest tag satisfying (5).
A git url that, when cloned, results in (1).

I personally could not find a more generic definition.

from: @fred-r
The example provided above (#43 (comment)) and referenced by @0Grit is clearly not a single package.
It is an application project made of several software projects.
Each software project is the composition of several CMSIS components (via several CMSIS packs).
I agree there is complexity but it only reflects the complexity of the systems we are dealing with.
I think we should not mix all topics:
I understand that you challenge the CMSIS-pack technology => to me x-pack covers this based on what you explained, even if I think that a "proper" usage of CMSIS-Pack should do the job...to be discussed by @jkrech and @ReinhardKeil
There is the project management aspect => here nobody said an application project should be a single pack

So I would recommend focusing this discussion thread on subject 2 and maybe @jkrech can redirect the 1st topic to the appropriate issue ?
from: @iomint
We are indeed deviating from the subject of this thread but these are interesting discussions for which we can open new issues thread or redirect to existing relevant ones.
During early discussion to set-up this open-CMSIS initiative, we have agreed to start from CMSIS-Pack (It has a certain footprint in the embedded with many MCU vendors publishing CMSIS packs) and see how to improve the spec and push an open reference implementation; @ilg-ul I invite you to look at the others issues - in particular #10 and #11 - to get an overview of the improvements we are looking for. It is great if there are good things pointing in the same directions from your xPack work that we can pick-up. It can helpful if you could have a look to #10 and #11 and flag to us the relevant elements of xPack.
About too large/complex (CMSIS) pack I fully agree with @ilg-ul concern and the feedback from @fred-r. How to favor (enforce ?) design practices to end up with "small" packs is a very good topic and will deserve a dedicated issue thread. We can provide examples/patterns and/or do something with a Pack checker but where to set the limit is a tricky question.
from: @ilg-ul
I took a quick look, but as long as you do not have a clearly layered design, and throw everything (dependencies, build, components, configuration, etc) into the same bucket, it is hard to flag any relevant differences.

I don't mind having my comments copied here, but I fail to see how they relate to Rust, Cargo and crates.
Two more comments:

GitHub has Discussions and Issues; I don't think that these are issues
Issues with lots of different topics under a generic subject are not very productive

I don't mind having my comments copied here, but I fail to see how they relate to Rust, Cargo and crates.
Two more comments:

GitHub has Discussions and Issues; I don't think that these are issues
Issues with lots of different topics under a generic subject are not very productive

Agree on all points.
See #40 to understand why I resorted to commenting in an issue.


Question: Which Xcode version was used to compile the release binaries

Hi
I was wondering, which Xcode version was used to compile the pre-built binaries from https://github.com/kishikawakatsumi/KeychainAccess/releases? (2.2.0 specifically).
I'm asking because a specific (and weird) issue I experienced using Carthage to embed KeychainAccess in my project. More details here: https://github.com/Carthage/Carthage/issues/832
Could it be that they were created using an older version dan Xcode 7.0.1 (maybe one of the beta builds?)

2.2.0 and 2.1.0 are built with Xcode 7.0.1.

Thanks! Are those binaries build with Carthage itself? Sorry for all the questions but I'm trying to pinpoint an issue that I'm having with this Framework and the pre-built ones specifically.

Yes. Those binaries are built with Carthage command: https://github.com/Carthage/Carthage#archive-prebuilt-frameworks-into-one-zip-file
carthage build --no-skip-current
carthage archive KeychainAccess


Gotolocation for search result in search find in files does not work. Impossible to follow search result i ipynb files

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

Version: 1.95.3 (user setup)
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631
For .ipynb files find in files search gotolocation does not work anymore for going directly to cell when single or double clicking on search results. Extensions disabled does not help. This is especially connected to this update. It works well in previous versions from September.

@anv2023 thanks for reporting! This should be fixed already in the latest versions of VS Code


Repository certificates expired?

Greetings,
I tried to add the binary package repositories today.  I got the following message, even after adding the repo signing key:
Err:11 https://packages.lexbor.com/ubuntu focal Release
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: <IP_ADDRESS> 443]
Reading package lists... Done
E: The repository 'https://packages.lexbor.com/ubuntu focal Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Hi @cro
What operating system? Version?
I tried it, it works fine.

I'm closing this, sorry for the noise.  I was installing the package repo in a container and I think maybe the ca-certificates package was out of date.


Bug: In Plando, with Songs on Song locations and some Shared Songs you can plando items other than Songs and junk

Title is self-explanatory. I doubt this is intended, or at the very least if it is, it shouldn't be. You should only be able to plando items other than songs on song locations in Songs Anywhere. The behavior of Shared Songs seems to be allowing you to plando major items like Master Sword, Light Arrows, etc without throwing an error. I feel like this is an oversight and given that Plando was implemented way after you added Shared Songs I don't doubt you probably didn't check for this when you put plando together. If the user wants major items on a song location, they'd use Songs Anywhere. So because of that this doesn't seem intended but if it is, feel free to close.

I think this is intended, pando takes precedence over everything else.


Command line args

Just wanted to discuss while 3.0 has not been released.
Is it worth looking to see if we can improve the command line usage? There are a bunch of better parsing libraries and conventions like -s --short which git uses which could make the usage nicer.
We could to try keep compatibility have a translation to start which translates the command line args as they are now into the new args. Help will only show the new args.
What does everyone think? Is it worth investigating or not?
// @andreasohlund @SimonCropp @gep13 @GeertvanHorrik

I think it's definitely worth investigating. It saves the code having to parse itself, it automatically supports /, -, -- and short and long codes. However... I know that it might also look like a big dependency. I don't care about it, but I know others do.
Maybe not for 3.0, if we are adding command line variables, it can be a smooth transition (add -u for -url, etc). We need to carefully thing this through instead of hurrying because 3.0 has to be released.

I think the current command line syntax in GitVersion is a mess (sorry for being frank), so cleaning it up to something a bit more conventional and familiar would be highly appreciated! :smile:
If the dependency can be made on a source code level (and not as a NuGet binary reference), I'm all for it. Perhaps add it as a git submodule?

We are aware of this ;-)
We are trying to find a set of commands that we can re-use amongst all tools. This way, no matter what tool you use, it should be very easy to get used to any tool you would like to use. It's still on the agenda.

Yeah, need to get v3 out the door. Then look at v4 for this sort of breaking change. Need to figure out how we could do some sort of compatibility mode to read legacy command lines and convert to the new one.

I agree that v3 should be shipped without this change. If the new command line argument syntax can be implemented in a backwards compatible way, it can be released as a minor v3 bump too; no need to wait for v4.


Change unit from percent to none

Fix from the previous PR https://github.com/redhat-appstudio/infra-deployments/pull/4338

@gabemontero FYI
Please take a look

/ok-to-test

/retest

/retest

/retest

/refresh

Yeah @divyansh42 closing and then reopening this PR may do the trick wrt getting that Red Hat Konflux job sorted out
trying it now

yeah that job is still stuck after closing / reopening the PR @divyansh42
Wednesday your time accept that invite if you haven't, create a new branch/pr and let's see how that does

yeah that job is still stuck after closing / reopening the PR @divyansh42
Wednesday your time accept that invite if you haven't, create a new branch/pr and let's see how that does

@divyansh42 accepted the invite already, all you have to do is to update this PR with new commit to trigger checks again by either rebasing your branch or amending the commit if you are already on tip of the main branch

yeah that job is still stuck after closing / reopening the PR @divyansh42
Wednesday your time accept that invite if you haven't, create a new branch/pr and let's see how that does

@divyansh42 accepted the invite already, all you have to do is to update this PR with new commit to trigger checks again by either rebasing your branch or amending the commit if you are already on tip of the main branch

yep that seems to have cleared it out thanks @hugares


Feature/pdct 1440 implement multi geographies in the navigator backend

Description
Implement multiple navigators in the backend.
Clean up to come after validation on staging and the final update to the frontend to remove old references.
Proposed version
Please select the option below that is most relevant from the list below. This
will be used to generate the next tag version name during auto-tagging.

[ ] Skip auto-tagging
[x] Patch
[ ] Minor version
[ ] Major version

Visit the Semver website to understand the
difference between MAJOR, MINOR, and PATCH versions.
Notes:

If none of these options are selected, auto-tagging will fail
Where multiple options are selected, the most senior option ticked will be
used -- e.g. Major > Minor > Patch
If you are selecting the version in the list above using the textbox, make
sure your selected option is marked [x] with no spaces in between the
brackets and the x

Type of change
Please select the option(s) below that are most relevant:

[ ] Bug fix
[ ] New feature
[ ] Breaking change
[ ] GitHub workflow update
[ ] Documentation update
[ ] Refactor legacy code
[ ] Dependency update

How Has This Been Tested?
Please describe the tests that you added to verify your changes.
Reviewer Checklist

[ ] DB_CLIENT DEPENDENCY IS ON THE LATEST VERSION
[ ] The PR represents a single feature (small driveby fixes are also ok)
[ ] The PR includes tests that are sufficient for the level of risk
[ ] The code is sufficiently commented, particularly in hard-to-understand areas
[ ] Any required documentation updates have been made
[ ] Any TODOs added are captured in future tickets
[ ] No FIXMEs remain

@katybaulch great to be getting this in!
Some questions as this is quite a big change:

To confirm where this sits against the following PR, my understanding is that this is us now passing in actual geographies not just a conversion of geography to an array of the geo like “fr’ -> [“fr”].
Re testing of this, have we spun up the local stack to test this before pushing to staging?
The main part I'm concerned about is the query changes for the creation of the pipeline input. As a minimum I would suggest we do the following to convince ourselves that the changes work as just looking at the code I don't feel like I can confirm fully that there will be no change in functionality other than the geographies field - I would suggest we spun up the stack locally with a staging dump, create the pipeline input from the "main" built backend and compare this against the "feature/pdct-14400..." built backend.

@katybaulch great to be getting this in!
Some questions as this is quite a big change:

To confirm where this sits against the following PR, my understanding is that this is us now passing in actual geographies not just a conversion of geography to an array of the geo like “fr’ -> [“fr”].
Re testing of this, have we spun up the local stack to test this before pushing to staging?
The main part I'm concerned about is the query changes for the creation of the pipeline input. As a minimum I would suggest we do the following to convince ourselves that the changes work as just looking at the code I don't feel like I can confirm fully that there will be no change in functionality other than the geographies field - I would suggest we spun up the stack locally with a staging dump, create the pipeline input (by invoking the endpoint) from the main built backend and compare this against the feature/pdct-14400... built backend.

Just to clarify, we're now passing an array of geographies. Where there is only one geography, this will have the effect “fr" -> [“fr”]. Where there are multiple e.g., France and UK, it would pass ["fr", "uk"].
Sounds good. Let's catch up after lunch as I could really use a hand validating this!

@katybaulch great to be getting this in!
Some questions as this is quite a big change:

To confirm where this sits against the following PR, my understanding is that this is us now passing in actual geographies not just a conversion of geography to an array of the geo like “fr’ -> [“fr”].
Re testing of this, have we spun up the local stack to test this before pushing to staging?
The main part I'm concerned about is the query changes for the creation of the pipeline input. As a minimum I would suggest we do the following to convince ourselves that the changes work as just looking at the code I don't feel like I can confirm fully that there will be no change in functionality other than the geographies field - I would suggest we spun up the stack locally with a staging dump, create the pipeline input (by invoking the endpoint) from the main built backend and compare this against the feature/pdct-14400... built backend.

Just to clarify, we're now passing an array of geographies. Where there is only one geography, this will have the effect “fr" -> [“fr”]. Where there are multiple e.g., France and UK, it would pass ["fr", "uk"].
Sounds good. Let's catch up after lunch as I could really use a hand validating this!

Confirmed locally that there are some differences so iterating to fix before merge.

@katybaulch great to be getting this in!
Some questions as this is quite a big change:

To confirm where this sits against the following PR, my understanding is that this is us now passing in actual geographies not just a conversion of geography to an array of the geo like “fr’ -> [“fr”].
Re testing of this, have we spun up the local stack to test this before pushing to staging?
The main part I'm concerned about is the query changes for the creation of the pipeline input. As a minimum I would suggest we do the following to convince ourselves that the changes work as just looking at the code I don't feel like I can confirm fully that there will be no change in functionality other than the geographies field - I would suggest we spun up the stack locally with a staging dump, create the pipeline input (by invoking the endpoint) from the main built backend and compare this against the feature/pdct-14400... built backend.

Just to clarify, we're now passing an array of geographies. Where there is only one geography, this will have the effect “fr" -> [“fr”]. Where there are multiple e.g., France and UK, it would pass ["fr", "uk"].
Sounds good. Let's catch up after lunch as I could really use a hand validating this!

Confirmed locally that there are some differences so iterating to fix before merge.

I have removed the pipeline query updates from this PR so we can test in isolation on staging.

@katybaulch great to be getting this in!
Some questions as this is quite a big change:

To confirm where this sits against the following PR, my understanding is that this is us now passing in actual geographies not just a conversion of geography to an array of the geo like “fr’ -> [“fr”].
Re testing of this, have we spun up the local stack to test this before pushing to staging?
The main part I'm concerned about is the query changes for the creation of the pipeline input. As a minimum I would suggest we do the following to convince ourselves that the changes work as just looking at the code I don't feel like I can confirm fully that there will be no change in functionality other than the geographies field - I would suggest we spun up the stack locally with a staging dump, create the pipeline input (by invoking the endpoint) from the main built backend and compare this against the feature/pdct-14400... built backend.

Just to clarify, we're now passing an array of geographies. Where there is only one geography, this will have the effect “fr" -> [“fr”]. Where there are multiple e.g., France and UK, it would pass ["fr", "uk"].
Sounds good. Let's catch up after lunch as I could really use a hand validating this!

Confirmed locally that there are some differences so iterating to fix before merge.

I have removed the pipeline query updates from this PR so we can test in isolation on staging.

This is the PR specifically for the pipeline changes with more comments from Mark on :) https://github.com/climatepolicyradar/navigator-backend/pull/388


chore: Update Langfuse README to avoid common initialization issues

fixes https://github.com/deepset-ai/haystack/issues/8126

A docs edit has also been submitted for https://docs.haystack.deepset.ai/docs/langfuseconnector
Please double check it as well @dfokina


Caching Public Keys?

Describe the problem you'd like to have solved
I'm writing a micro-service in which I'm trying to squeeze every bit of performance that I can.  I am using verify to validate a JWT token against a public key file that I've read in as a string (-----BEGIN PUBLIC KEY----- etc.) .  It work fine.
What I'm wondering is if there is a way I can "cache" the public key after it's decrypted so that on subsequent calls to verify, it doesn't have to continuously redo the work of decoding that key.  I checked the results coming back from verify when setting the option complete to true, but didn't see anything along these lines.
Describe the ideal solution
In the results that come back from verify, include a property of the decoded key that I can pass back in on subsequent calls to verify.
Alternatives and current work-arounds
n/a - as mentioned, passing in the entire PEM string to verify each time works

You can actually do like this if you are using NodeJS >= v11.6.0:
import {createPublicKey, KeyObject} from 'crypto';

private parsePublicKey(pKey: string) {
  return createPublicKey({
    key: pKey,
    format: 'pem',
  });
}

With that KeyObject you can call verify as much as you want


CI smoke test for STC test

[x] A small test bucket to run for newer changes under systest
[x] A 15-30 minutes run
[x] Run on every commits pushed

$ cat test_lists/SYSTEST_CI
-i Hard_Bootme_Test
-i Processor_Speed_Check
-i Test_IO_Adapters_EEH
-i Test_EEH_Operation
-i Reboot_OS_And_Verify_uCode_Update

Propose list

similar to issue 1287 I think.   We can cancel that one

We will still need #1287 for the job to run. This is more of a grouping for the 1287 to run on it..

Maybe @onye1 you can use this as a placeholder  to start with on the CI and CT runs


Can't check if value is an integer/whole number

We have two methods to check if a number is an integer/whole number or not but they don't seem to work very well in Flutter:
value.runtimeType == int;
print((2 + 2).runtimeType == int); is true
print((2 / 2).runtimeType == int); is false...
and equally with:
value is int;
print((2 + 2) is int); = true
print((2 / 2) is int); = false...
Strangely in Dartpad they all equate to true
Flutter: 1.9.1+hotfix 2

@lrhn Not sure why it's not clear, I was simply stating that those methods in my original post do not work. Since 2 / 2 certainly is an integer, returning that it is false can't be expected behaviour?
Beyond that I was expecting isInt to be there along with isEven, isNegative etc.

In Dart, when not compiled to JavaScript, the int value 1 is not the same as the double value 1.0. The former is an instance of the class int, which means that is int and .runtimeType == int says yes. The latter is an instance of the class double, which is neither a subclass or a superclass of the int class, which means that 1.0 is intand1.0.runtimeType == int are false (1.0.runtimetype == doublewould be true). Usingis intor.rnutimeType`, you are asking about the runtime type of an object, not a mathematical property.
So 2/2 is an integer (mathematically), but it is not an int because it is a double.
(I you check, for example, Java, an instance of Double with the value 1.0 is also not an instanceof Integer).

@lrhn That's why Dart is missing .isInt ie value.isInt.
It's also a slight issue with Dartpad since we use that with stackoverflow and such to show if something code-wise works or doesn't. I actually posted this issue on stackoverflow originally and this very thing happened, the person answering refused to accept that is int did not verify a whole number because dartpad showed that it did..

With extension methods you can have something like this:
extension on num {
  bool get isInt => this % 1 == 0;
}

Sample usage:
double d = 2.6;
double d2 = 2;
int i = 2;
print(d.isInt); // returns false
print(d2.isInt); // returns true
print(i.isInt); // returns true


Sankaku complex grabber crash when you click on a image

Bug description
When you click on a image with the source sankaku complex the program will crash.
Steps to reproduce
Just open a image for example when you search nekopara or something different and the program will not respond untill it will crash at the end. (Have also deleted my settings and it did the same thing)
Expected behavior
Like with the other sources tou aspect that it will not crash when you click on a image
System information
Windows 10 with the nightly version

Indeed. More than a crash, it causes an infinite loop, which ends up crashing.


ERROR: Updates were rejected because the tip of your current branch is behind

Hi @stevejenkins
Has anyone run into this error?
root@raspberrypi-hole1:/usr/local/bin/pihole-cloudsync# ./pihole-cloudsync --push
--push option detected. Running in Push/Upload mode.
Local Pi-hole lists are different than remote Git repo. Updating remote repo...
To github.com:REDACTED/my-pihole-lists.git
! [rejected]        main -> main (non-fast-forward)
error: failed to push some refs to 'git@github.com:REDACTED/my-pihole-lists.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
Done!

I had this error on my own repository when I made a local commit and tried to push it. I am 99.999% sure that I didn't make any changes to the remote repository (on github.com).


Save modal/dialog

Closes #114

Created a save dialog that allows the user to select between current and new branch and also write a commit message
Changed the save button to use Material-UI

Currently the branch name and commit message are only logged to console because backend does not support this feature yet. This can be changed after #113 and #115 are merged.
Known issue:
When the save dialog is opened, warning "findDOMNode is deprecated in StrictMode" will be output to console. This is a problem within the library and as far as I understand only way to get rid of it is to either not use strict mode at all or to update Material-UI to alpha version. The functionality of the component is not affacted in any way and the warning should not show up in production (since strict mode won't be enabled) so my suggestion is to just ignore it.

Made a separate issue about integrating this with the upcoming backend changes -> #121


Test that are passing are not shown on dock panel

Since updating to 1.0.0 only if there is an error you will see something in the results dock panel. In lib/executor/pytest-executor.js there is nothing done when the BufferedProcess receives an output and updates on the execution are not printed on the results panel.

Hey @agorer , I am unable to reproduce this. I have tested running only one test that is passing and the results show the panel with the only test that is passing. I have tested running only one test that is failing and the results are shown too. Could you help me to reproduce this?
Thanks!

I have gone back to the previous version, so I am not really able to test it anymore. But from what I remember, in lib/executor/pytest-executor.js nothing is done when there is an output event on the BufferedProcess so no real time updates are shown. No results were shown when all tests were finished, but I see that is taken care of in the exit event of the BufferedProcess.

@agorer ,
The plug-in does not update in real time while monitoring the stdout, because now it just monitors when the process exist, then collects the data using the junit parser to parse the results. So, if there is an error (py.test not available for example), the dock will print an error. Otherwise (if tests pass, fail, etc) it will show the results.


Adding controller host log info to http methods

Codecov Report

Merging #2836 into master will increase coverage by 23.55%.
The diff coverage is 75%.

@@             Coverage Diff             @@
##           master    #2836       +/-   ##
===========================================
+ Coverage   45.65%   69.21%   +23.55%
===========================================
  Files         908      908
  Lines       43417    43425        +8
  Branches     5888     5890        +2
===========================================
+ Hits        19824    30055    +10231
+ Misses      21935    11359    -10576
- Partials     1658     2011      +353

Impacted Files
Coverage Δ

...n/pinot/common/utils/FileUploadDownloadClient.java
70.4% <75%> (+15.69%)
:arrow_up:

.../impl/dictionary/FloatOnHeapMutableDictionary.java
80% <0%> (-13.34%)
:arrow_down:

...mpl/dictionary/DoubleOffHeapMutableDictionary.java
70.9% <0%> (-7.28%)
:arrow_down:

...impl/dictionary/FloatOffHeapMutableDictionary.java
80% <0%> (-7.28%)
:arrow_down:

...e/operator/dociditerators/SortedDocIdIterator.java
59.45% <0%> (-5.41%)
:arrow_down:

...ot/core/query/pruner/ColumnValueSegmentPruner.java
84.74% <0%> (-3.39%)
:arrow_down:

...not/broker/broker/helix/ClusterChangeMediator.java
63.33% <0%> (-3.34%)
:arrow_down:

...manager/realtime/HLRealtimeSegmentDataManager.java
74.28% <0%> (-2.39%)
:arrow_down:

...ata/manager/realtime/RealtimeTableDataManager.java
38.63% <0%> (-1.52%)
:arrow_down:

.../broker/routing/HelixExternalViewBasedRouting.java
90.33% <0%> (+0.33%)
:arrow_up:

... and 480 more

Continue to review full report at Codecov.

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


WebSockets Usage/Compatibility

Hello, I wanted to ask if there is any way of running this plugin to connect to a WebSocket, keep it running on background, and show notifications on a socket instance. I was thinking about using Socket.io for this.

Websockets increase network traffic a lot, because of heart beat packets.
Is it a good idea to apply this type of strategy to notifications? Firebase Cloud Message is always free and saves a lot of device traffic because it's Google's service that triggers the packet only when it's needed.
But it's totally possible to implement and integrate it easily with awesome notifications. Can you build a java method to handle websocket? I can do the integration.

I thought Push Notifications were based around WebSockets, but I guess I'll have to investigate a bit more about that.
What alternatives would you recommend for a NodeJS Server that'll have to send the notifications down to the Flutter app?

Hi! Sorry for taking so long to respond to your issue on GitHub. I was focused on releasing the new 0.7.0 version of awesome_notifications and awesome_notifications_fcm and i didn't had time enough to do both. But now I can answer all your questions.
So now i'm asking you to recreate this topic using the new issue template. There's a lot of missing informations that i need to understand your problem, and all the instructions are already in the new issue template. Also, remember to check beforehand if your issue was posted by another user.
So I will automatically close all previous issues so far.
Sorry for the inconvenience and i will be waiting for your new issue request.
Thank you so much for your support!


ConfigServer Security & Firewall: Radios are missing in preconfigured profiles

Unable to choose Preconfigured Profiles in CSF Module.
Unable to have CSF excluded from the in-built rendering mechanism.

What is your server-side OS and its version?
Module:                  ConfigServer Security & Firewall version 9.11
Operating system:  CentOS Linux 6.8
Webmin version:     1.810
Theme version:	Authentic Theme 18.10

What is your client-side OS, browser and its versions?
Operating system:  Windows 10 build 1607
Browser:                  Google Chrome 52.0.2743.116 m (64-bit)

What are the steps to reproduce the issue
The only thing I know of that is NOT default is that using "Module category assignments", I reassigned the CSF module to "Networking" instead of the default "System" Category.

This is true, I missed it! I will fix it upon next release.
Thanks for reporting, pal.
P.S.  Exclusion of this module has not been supported yet. I might invent my time in it but I don't see much reason really.

I tried to exclude as a workaround for the missing check boxes / radio
buttons.
On Aug 26, 2016 5:03 AM, "Ilia Rostovtsev"<EMAIL_ADDRESS>wrote:

This is true, I missed it! I will fix it upon next release.
Thanks for reporting, pal.
P.S. Exclusion of this module has not been supported yet. I might invent
my time in it but I don't see much reason really.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/qooob/authentic-theme/issues/540#issuecomment-242673438,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABm-rUda9PZKNtG0Xw4X0F7rwq48CE4Yks5qjqv_gaJpZM4Jtstj
.

It will be fixed in 18.20

Version 18.20 is out, please upgrade.


Cluster-Selector: The Kubernetes native way

Is your feature request related to a problem? Please describe.
Currently the selector for ClusterProfiles and Profile is kinda primitive. Not to say it would not be sufficient. However: what if we used a selector declaration which is a bit more native to Kubernetes aka the LabelSelector struct:
...
   selector:
       matchLabels:
          environment: production
       matchExpressions:
          - { key: tier, operator: In, values: [cache] }

This would  not replace the current option, for compatibility reasons. The would probably be combined.
Describe the solution you'd like
Implement the proposed selector, if it's accepted as feature.

@oliverbaehler I would love that.
The logic is implemented in libsveltos
as clusterSelector is used by different services:
Cluster Selector is used by:

addon-controller with Profile/ClusterProfile and Set/ClusterSet
access-manager
event-manager

v1beta1 was introduced. v1beta1 changes the ClusterSelector field from labels.Selector to metav1.LabelSelector.
v1alpha1 still uses ClusterSelector exposed as string (that gets converted to labels.Selector).
conversion webhook will translate from v1alpha1 to v1beta1 for all CRD instances which a ClusterSelector field.

v1beta1 uses Kubernetes LabelSelector.
type Selector struct {
	metav1.LabelSelector `json:",inline"`
}

Conversion webhook has been implemented to convert from v1alpha1 (still supported) to v1beta1 and viceversa. All repos have been updated accordingly.  So closing this as completed. It will be available in next release.
Thank you @oliverbaehler for proposing this.


Process requests on a preemptive CPU stock

Here is my first attempt at modelling a CPU stock.  Requests keep track of how many CPU seconds they need to complete (initially 500ms) and how many they have been given so far.  Processes (requests) are interrupted every 100ms to schedule another process in a round-robin fashion.
But I think I broke something in the visualization.  This is traffic ramp at HEAD:

And this is the same ramp with a CPU stock.

@jchesterpivotal why are the RequestsProcessing never going down?  Where does that data come from anyway?  I think my requests are ending since latency stabilizes at 500 ms.

I think the reason the requests pile up in RequestsProcessing is because there's no longer a movement being scheduled to get them into RequestsCompleted in the same way, which is what the queries look.
I was thinking that an alternative would be for the CPU stock to only hold one Request at a time, scheduling them to return to a 'waiting' stock or to completed, depending on how much processing time the entity has accumulated.
This problem and the ticktock stocks I've written make me think that providing a more general ticktock/timer helper would be good. While the underlying simulator doesn't have that kind of regularity baked in, a lot of the things in the model assume regular ticks, so it should be easier to achieve that.

there's no longer a movement being scheduled to get them into RequestsCompleted

I do move requests into the sink. But I don't schedule it.
https://github.com/josephburnett/skenario/blob/dc449508d0706013841bcfbcacb5f106a58c23df/pkg/model/cpu.go#L45
I wonder if I should just collapse the request processing and cups stocks since the rp stock isn't doing much anymore. No need for passing requests back and forth.
Maybe a tick tock mixing thingy. But it isn't difficult to do for each stock. And the autoscaler tt is quite different from the cpu tt.

Sorry for slow reply, was recovering from a laser eye surgery.

I wonder if I should just collapse the request processing and cpu stocks since the rp stock isn't doing much anymore. No need for passing requests back and forth.

I think so, yes. While a Process is a distinct concept in the real world, I don't think it's a necessary level of fidelity for our simulation. Whether a Request is executing in a thread or as a whole process is kinda by-the-by.
I found that it's helpful to think of how it might be done as a state machine for the single case, and then making each state into a stock. So at the moment there's a single RequestsProcessing stock and movements out of it are based on the Sakasegawa approximation calculated at the time a Request joins the stock. But we might instead have movements between RequestsProcessing and RequestsBlocked -- the standard 2-state OS model from every introductory textbook oh god flashbacks help me.
Another alternative I kicked around is whether to instead create stocks for progress. Eg RequestsFirstStage, RequestSecondStage etc. This has the downside of increasing the amount of movement bookkeeping and it's not clear to me how this would correctly create slowdowns during contention for CPU time. But it would at least retain the property of Requests being interchangeable tokens, rather than carrying state of their own.

More speculatively this makes me wonder again if I'll wind up back with the database-centric rewrite I tried and failed at previously. Being able to update deadlines based on past, current and future state would make some of these problems easier. However it would require a heavy amount of rewriting and I expect performance would be substantially reduced. Based on some profiling I saw that the current implementation running time is dominated by the batching-and-dumping of data into SQLite. The actual simulation code itself runs in milliseconds.
On the other hand it'd still be able to simulate large scenarios in a few seconds so ... meh?

While a Process is a distinct concept in the real world, I don't think it's a necessary level of fidelity for our simulation.

Okay.  I'll just roll the CPU simulation up into requests processing as general resource consumption.  And maybe add memory consumption as well.

Being able to update deadlines based on past, current and future state would make some of these problems easier.

I don't think updating deadlines is necessary.  It isn't hard to schedule just ahead of ourselves (temporal recursion?)  And the performance of the simulation is something I don't want to lose.

OK, sounds good. I don't intend any drastic architectural changes until at least the current backlog is fully drained. So far it's more or less holding up to what we're asking of it.

This has been superseded by the CPU model by @juliababkina


workflow level task dry run UI

Purpose of the pull request
This pull request adds the UI of workflow level task dry run.
Brief change log
1、Add the option whether to dry run or not on the start page.
2、Add a dryrun flag  column on the workflow instance page.
3、Add a dryrun flag  column on the task instance page.

Verify this pull request
This pull request is already covered by existing tests.

Codecov Report

Merging #6173 (c625faa) into dev (a1e447d) will decrease coverage by 0.08%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #6173      +/-   ##
============================================
- Coverage     39.07%   38.98%   -0.09%
+ Complexity     3250     3224      -26
============================================
  Files           638      637       -1
  Lines         25266    25426     +160
  Branches       2743     2767      +24
============================================
+ Hits           9872     9913      +41
- Misses        14516    14605      +89
- Partials        878      908      +30

Impacted Files
Coverage Δ

...nscheduler/server/entity/TaskExecutionContext.java
45.08% <0.00%> (-22.96%)
:arrow_down:

.../dolphinscheduler/common/process/ResourceInfo.java
36.36% <0.00%> (-6.50%)
:arrow_down:

...er/master/dispatch/host/assign/RandomSelector.java
77.77% <0.00%> (-5.56%)
:arrow_down:

...api/service/impl/ProcessDefinitionServiceImpl.java
35.66% <0.00%> (-0.73%)
:arrow_down:

...pache/dolphinscheduler/common/utils/JSONUtils.java
72.28% <0.00%> (-0.33%)
:arrow_down:

...er/api/service/impl/TaskDefinitionServiceImpl.java
33.16% <0.00%> (-0.17%)
:arrow_down:

.../org/apache/dolphinscheduler/api/enums/Status.java
100.00% <0.00%> (ø)

...g/apache/dolphinscheduler/dao/vo/AlertGroupVo.java
0.00% <0.00%> (ø)

...apache/dolphinscheduler/spi/task/AbstractTask.java
0.00% <0.00%> (ø)

...ache/dolphinscheduler/dao/entity/TaskInstance.java
67.33% <0.00%> (ø)

... and 26 more

Continue to review full report at Codecov.

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


Don't create and process payment when checkout total is 0

Right now, when the checkout total is 0, the payment is processed. We are sending requests to gateways with 0 amount. Instead of that, when the checkout total is 0, payment will be not created and any request won't be sent to the gateway, order automatically will be marked as paid.
SALEOR-1241
⚠
The frontend part should be finished before merging.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[x] Changes are mentioned in the changelog

Task linked: SALEOR-1241 PaymentError: Unable to process the payment request. with value 0

So the product in basket is discounted to free (it could be virtual product you allow to download for free)? Some edge case of of one of plenty of projects you want to hardcode into core? @IKarbowiak @maarcingebala @korycins @fowczarek

@a2xchip What edge case are you talking about hardcoding? It's impossible to charge a credit card for zero of whatever currency using most payment gateways.

We will open a new PR which will be a port of https://github.com/saleor/saleor/pull/8938.


Possible deadlock

At udpJanitor() function.
The thread hold l.udpPoolMutex.Lock(). then check udpPoll for whether there is a UDP connection got timed out.
If there is, the thread call conn.Close() to close the connection.
https://github.com/1lann/go-sip/blob/68e86c65407ef8cf672ae38526e7f3d29944b94f/sipnet/connection_pool.go#L81-L85
However, at conn.Close()
https://github.com/1lann/go-sip/blob/68e86c65407ef8cf672ae38526e7f3d29944b94f/sipnet/connection.go#L198-L216
if c.Listener != nil . This function will try to hold l.udpPoolMutex too.
This cause a deadlock and the program will stop listening for new connections.
Tested on go version go1.12.7 linux/amd64.
I'd like to create a pull request however I'm not familiar with Golang. So any help would be much appreciate. Thanks

I've checked the caller of Conn.Close() function. The only callee when c.Transport == "udp" is udpJanitor() function. So I've commend out connection.go line 207 and line 209. Works great so far.

Thanks for reporting this, I did a proper fix which is by marking the connections to be closed, and then closing them after the mutex is unlocked.


Drag & Drop doesn't work when window or container has scroll

I have tested this library for a while I feel most part of it is working really well; but when I have been asked if it works in scrollable container. Since then I tried again with this scenario. Yes it seemed work quite well in firefox, but didn't in chrome. I also looked into source code I came across this variable scrollableContainer and still didn't work. Could any body here point out a solution to this?

I've added an example of my running into what looks like the same bug. First it shows two sortable lists behaving beautifully. Then I decrease the window size to create a scroll bar, and suddenly the dragged items jump as soon as I click on them.

Hi what kind of error you see in the browser console?

@a5hik, there is no error. I think Chrome ignores the scroll screen offset.
E.g. if the element is at x=100px on the screen and the screen is scrolled to 200px, FireFox and IE 11 will correctly identify that the element is actually at 300px, while Chrome will continue to think that it's at 100px.

@meassinal and @Serhioromano: I ended up solving my issue by having scroll within the element rather than using browser scroll. E.g.
This doesn't address the underlying issue but it makes the library usable when you need lateral scroll.
Hope that helps.


How to specify network_configs for ResNet-18?

In the maskal/configs/COCO-InstanceSegmentation folder, there are many network settings, how to set the yaml file for ResNet-18?
For example how to change the mask_rcnn_R_50_FPN_3x.yaml setting to mask_rcnn_R_18_FPN.yaml?

In the maskal/configs/COCO-InstanceSegmentation folder, there are many network settings, how to set the yaml file for ResNet-18?
For example how to change the mask_rcnn_R_50_FPN_3x.yaml setting to mask_rcnn_R_18_FPN.yaml?

@adalinadalin I have checked the configs folder, but there is no Resnet-18 config file (yet). The current configs folder is directly forked from Detectron2.
I guess if you want to use Resnet-18, you can make your own yaml file with Depth: 18 under Resnets. If it works out of the box, then that would create a Resnet-18 model. I haven't checked it though.

@adalinadalin Did you solve this? Shall I close this issue?

@pieterblok Thanks for your reply. Yes, I can make my own yaml file with Depth: 18 under Model-Resnets. Detectron2 does not  provide a pretrain weights for ResNet-18 now.  You can close this issue. Thank you.


[KBM]Disable utility by default on new install

Summary of the Pull Request
Keyboard Manager starts enabled by default, which consumes resources and starts a Low level keyboard hook. This makes little sense because the utility needs user configuration to do anything useful.
This PR makes it so that KBM starts off by default.

PR Checklist

[x] Closes: #29273
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Validation Steps Performed
Cleaned up local settings (delete %localappdata%\Microsoft\PowerToys) and tested. Verified KBM was off by default.

/azp run


weighted moving average

Description
This update addresses discrepancies in the Weighted Moving Average (WMA) functionality and its corresponding test cases.
Key Changes
Corrected Unit Test Assertions:
Updated the expected values in the test cases based on manual recalculations of the WMA formula.
Ensured the expected results match the implementation for both default linear weights and custom weights.
Validated WMA Implementation:
Verified the correctness of the WMA calculation for different scenarios, including grouped and ungrouped data.
Tested with varying window sizes and weights.
Improved Test Coverage:
Ensured tests cover edge cases, such as insufficient data for rolling calculations.
Included assertions for grouped and non-grouped datasets.
Outcomes
The Weighted Moving Average functionality is now thoroughly validated and aligned with the expected behavior.
All tests pass successfully, confirming the correctness of the implementation.
This update strengthens the reliability of the WMA feature in the data transformation module.

There has not been any response for the last 2 weeks. Please respond or address the aformentioned concerns before the end of the week.


is webvr-polyfill compatible with the newest versions of THREE.js?

Description:
I updated packages in a webvr-polyfill-using application and now see the black screen reported here in Samsung 8, Chrome (the only device I have for testing this). Previously this worked fine.
the latest versions of THREE.js no longer include VREffect and VRControls scripts. Which version of webvr-polyfill and THREE.js should we use?
Additional Information:

webvr-polyfill version: 0.10.10
Browser name/version/release channel: Chrome 72.0.3626.105
Operating System: Samsung

Three has support for WebVR via renderer.vr.enabled = true, check out the demos for that.
Separately, the webvr polyfill can be included to provide the WebVR API if the platform does not exist

@jsantell I found that, in my Samsung 8 chrome browser, it is necessary to visit chrome://flags/ to enable support for vr mode there and so I will probably continue using webvr-polyfill.
Do you know, is there is a way to use webvr-polyfill by and three.js without VRControls and VREffect scripts, or are those scripts required for webvr-polyfill to be used with three.js?

@jsantell is Web VR commonly supported in phone browsers? Would you still recommend using native Web VR, even though it is not supported in the current Samsung 8 chrome browser?
What are your thoughts and recommendations?

@jsantell I found that, in my Samsung 8 chrome browser, it is necessary to visit chrome://flags/ to enable support for vr mode there and so I will probably continue using webvr-polyfill.
Do you know, is there is a way to use webvr-polyfill and three.js without VRControls and VREffect scripts, or are those scripts required for webvr-polyfill to be used with three.js?

VRControls and VREffect are no longer necessary https://github.com/immersive-web/webvr-polyfill/issues/340#issuecomment-473320935

@jsantell is Web VR commonly supported in phone browsers? Would you still recommend using native Web VR, even though it is not supported in the current Samsung 8 chrome browser?
What are your thoughts and recommendations?

Here's the most accurate support matrix I'm aware of: https://caniuse.com/#search=webvr. The polyfill is still necessary to support a majority of users (most notably at the moment, Chrome, which is supporting the in-flux WebXR API)

@jsantell thank you


Resolves #853 - fix camera matrix update ordering

Removes camera flickering when doing 3d world edits
Also uses a single camera helper object instance rather than reconstructing on every update

lgtm


Use X-Franz headers to talk to the server

1fcfccd broke communication with the internal server by using X-Ferdi
headers instead of X-Franz headers on HTTP requests.
For compatibility reasons, we retain the X-Franz headers insteaf of
X-Ferdi headers in the internal server.
This commits reverts the change to the headers to restore internal
server functionality.

Checklist:

[x] My pull request is properly named
[x] The changes respect the code style of the project ($ npm run lint)
[x] I tested/previewed my changes locally

For future reference: Changing these will also require us to change the same settings in the internal-server (git submodule) as well as the external server repo (and deploy this). So, this PR is good for reverting the prev commit.


We should absorb non-enumerable properties as well

Currently by absorbing all the non-enumerable properties are lost, because a simple for-in loop does not contain them. We could use getOwnPropertyNames instead. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/getOwnPropertyNames

Currently I am trying to copy String.prototype properties on the Stack.prototype and it is completely impossible with absorb...

I am not sure, added the following code to e3 for now:
var extractStringMethods = function () {
    var stringMethods = {};
    var names = Object.getOwnPropertyNames(String.prototype);

    for (var index in names) {
        var name = names[index];
        if (name == "valueOf" || name == "toString")
            continue;
        var method = String.prototype[name];
        if (!(method instanceof Function))
            continue;
        stringMethods[name] = method;
    }
    return stringMethods;
};

Stack.prototype.absorb(extractStringMethods());

I don't like the idea to absorb properties from Object.prototype and make them own properties. On the other hand by inheritance we won't be able to absorb properties from the ancestor. That can lead to failure. So this is probably an issue and it should be done with careful filtering of properties coming from Object.prototype.

What about merge? If I do this by absorb, I have to do the same with merge...

I consider this a bug, because the expected behavior would be to get all the properties by absorb, even properties from the ancestor classes, except Object. I am not sure about the other native classes, but using stuff from String.prototype or Array.prototype might be ok.


Support for python 3.13

The first stable release of Python 3.13 is out. We should add this to the unit tests on GitHub
At the same time, xarray as dropped support for Python 3.9 and I suggest we do too.  See https://github.com/nci/scores/issues/641 for a past discussion on this.

I agree, it's time. Thanks for the PR.


Create multiple http clients with different internet connections

What version of Go are you using (go version)?

$ go version
go version go1.11.5 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/andrusd/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/andrusd/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/lib/go"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build501600568=/tmp/go-build -gno-record-gcc-switches"

What did you do?

What did you expect to see?
Multiple http requests with different internet connections connected to my server
package main

import (
	"net/http"
	"net"
)

func main() {
	//Get By Default network
	GetByDefaultNetwork()
	// Get By Wifi custom network
	httpCustomClient := &http.Client{Network: net.GetNetworkOs("eth1")}
	GetByCustomNetwork(httpCustomClient)
}

// Example custom eth1
func GetByCustomNetwork(custom *http.Client) {
	custom.Get("http:/google.com")
}

// Example default eth0
func GetByDefaultNetwork() {
	http.Get("http://google.com")
}

What did you see instead?
nothing

If this is not possible go. It is possible to add this functionality, since working with servers with multiple connections is common in the cloud

The code posted doesn't use the custom http.Client.

:+1: @renthraysk  Already solved. The proposal should be better understood

You can achieve your goals by using an http.Client using an http.Transport that defines the Dial hook(s) with a net.DialTCP and setting the local addr on the dials.

@bradfitz  I had no knowledge of this. Thank you. Now I just have to find where to learn more about this


insecure transport

Hello Nikolas,
Since approx. 1 week for some reason the module shows no real car data any more.
I haven't changed anything in the car (e.g. security settings) nor in my magic mirror installation (except some regular system updates "sudo apt update & upgrade").
You can see the error message “insecure transport…… https” on the screen, which unfortunately does not speak to me 😊
Cheers
Hans

Oh, wow - thanks a lot and sorry :-)
Am Dienstag, 10. Dezember 2024 um 16:47:55 MEZ hat NikolasRupp @.***> Folgendes geschrieben:
Hi,
Please have a look at Issue #12.
You have to log in on the web to accept the new Terms and Conditions.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Add Playfair Cipher

Add Playfair Cipher
I tried to make the Playfair cipher in C it's very complex without the Set but somehow I managed it using loops
if you think anything wrong with this code so tell me I will fix that. :)

Here some reference that I use to implement the code:
https://en.wikipedia.org/wiki/Playfair_cipher

I don't have time rn to check it, I'll merge it and make changes if it's wrong somewhere :)


Refactored HttpTesting Controller Integration Tests

I rewrote each test to not use a setTimeout when selecting UI elements or in the case of making a request to google, it awaits a Promise that blocks for 500ms before selecting an element.

LGTM


Windows下NNI检测不到GPU

Windows系统nvidia-smi命令使用正常，出现和 #2055 相同的error，在gpu_metrics中显示如下：
{"Timestamp": "Wed Jun  3 18:24:50 2020", "gpuCount": 0, "gpuInfos": []}
看过其他issues后均未能解决问题，求帮助。
nni Environment :

nni version: 1.6
nni mode(local|pai|remote): local
OS: Windows10
python version: Python3.7
is conda or virtualenv used?: conda used
is running in docker?: no

Hi @Scotty1027, does the C:\Users\{youraccount}\AppData\Local\Temp\{youraccount}\nni\script folder has any file in your machine?

Hi @Scotty1027, does the C:\Users\{youraccount}\AppData\Local\Temp\{youraccount}\nni\script folder has any file in your machine?

There are three files in this folder ：gpu_metrics,  gpu_metrics_collector,  pid

script.zip

It shows like this

Seems your machine could parse gpu info correctly, have no idea why the content in metric file generated by NNI is {"Timestamp": "Wed Jun  3 17:11:02 2020", "gpuCount": 0, "gpuInfos": []}. When you run this script manually, is the content in your $env:METRIC_OUTPUT_DIR correct? did you tried stop gpu_metrics_collector services in backend, and restart NNI experiment?

Everything was fine when I ran it again earlier today. Interestingly, I did nothing.
Thanks for you kindness !

Sorry to bother you again, There comes another problem.
When I use GPU to run it, the trial's status always shows Failed. But when I use CPU, it goes fine.

The photo shows the status of trial when I use CPU, it's too slow.

Sorry to bother you again, There comes another problem.
When I use GPU to run it, the trial's status always shows Failed. But when I use CPU, it goes fine.

The photo shows the status of trial when I use CPU, it's too slow.

I think I made a mistake in my code, now it's alright.
Thank you anyway.

Everything was fine when I ran it again earlier today. Interestingly, I did nothing.
Thanks for you kindness !

closing the issue as it has been resolved


Issue #368 unit tests - Array

I wasn't quite sure how far to take this, but I have added a couple of unit tests for the Array class as per AlmasB's suggestion via email. Unit tests are a bit strange to do retrospectively in my opinion.
It would also be nice if a style guide / xml would be available somewhere so I wouldn't need to filter out the slight formatting changes that IntelliJ wanted to make (particularly spacing between some parameters and brackets).
Relates to issue #368

Looks good. Many thanks!

It seems non-public test methods are not accessible: https://travis-ci.org/github/AlmasB/FXGL/jobs/671703490
so I made them public. Odd that the PR didn't trigger CI...

Huh that's strange. IntelliJ was able to run them just fine :/


Autogenerated docs are automatically deployed, but not committed

When regenerating documentation, any docs that are generated from upstream are included, however they have already been deployed to the production docs. This causes confusion for users submitting PRs and undue work in reviewing changes.

I guess the only danger here, is if autogenerated docs are committed, people might submit PRs against the autogenerated docs, not realising that they're editing "output files" and not "input files" ? :man_shrugging:

@lurch this is actually already true, and often a source of confusion for people trying to contribute! I myself am often a victim as well

I'm going to close this (please re-open if you feel differently) but as external docs have been removed from the repo they can't be committed. There is a related but different issue with regards to ensuring that the docs are published from an upstream documentation change (there is currently no trigger to force a rebuild) but I'll record that separately.


runtime: floating-point comparison error on Loong64

What version of Go are you using (go version)?

$ go version
go version devel go1.21-f5c7416511 Thu Mar 9 22:13:26 2023 +0000 linux/loong64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?

package main

import(
        "fmt"
)

func main() {
        var target float64 = 100000.0
        for i := 1; i < 100000000; i++ {
                var fslice []float64
                for j := 0; j < 100; j++ {
                        fslice = append(fslice, 1.124567)
                }
                var sum float64
                for _, f := range fslice {
                        sum += f
                        sum += 0.1
                        sum += 0.2
                        sum += 0.3
                        if sum >= target {
                                fmt.Println("err 1")
                        }
                        if sum >= target {
                                fmt.Println("err 2")
                        }
                        if sum >= target {
                                fmt.Println("err 3")
                        }
                        if sum >= target {
                                if sum < target {
                                        fmt.Println("err 4")
                                }
                        }
                }
        }
}

What did you expect to see?
(i.e. no output)
What did you see instead?

err 3
err 4
err 2
...

(i.e. numbers are unordered)

CC @golang/loong64

Commit 48d61a46e280 had the "Fixes" keyword misspelled, so the issue was not auto-closed.
Manually closing as completed.


Fix #322 freeze attack by detecting expiry of stale metadata files

This fixes Issue #322. Please see that issue!
It replaces PR #323, which got too messy.
Update:
This PR also:

:bug::bug: Fixes two additional bugs issues identified below, both causing unprintable NoWorkingMirrorError exceptions - one in python 3 only and the other in either 2 or 3 with certain mirror name issues.
adds .DS_Store to .gitignore

This started as a manual squash commit of detect_expiry_322, to avoid merge conflicts.
Comment lines from the individual commits include:

Fix #322 by detecting expiry of stale files. initial attempt
temp commit of files from Soma
removing freeze_attack_stale_expiry and leaving the test added to indefinite freeze attack
fixing indefinite freeze attack test: now incorporates old reject-freshly-downloaded-but-expired-timestamp test as well as reject-stale-already-present-but-expired-snapshot test
small refinements to indefinite freeze attack test
Pulled the recursion out of the except block in refresh() to avoid unprintable nested exceptions.
Added comments to the last commit (retry_once)
Merge pull request #1 from awwad/detect_expiry_322_temp (removing cruft in another branch)

Tests all look good to me. Running full tox again on 2.7 and 3.4. LMK if you think this is OK, Vlad?

Sidenote: there is not enough information in the code about why "unsafely update root if necessary" is unsafe.

I tried to explain here: https://github.com/awwad/tuf/blob/detect_expiry_322_clean/tuf/client/updater.py#L620-L624
Previously, "safely" fetching root.json required knowing its hash and file size (as specified in snapshot.json).  Now, safely fetching root.json is knowing its exact version number.  A root.json is unsafely fetched without knowing its version number (i.e.,, snapshot.json might have expired, thus the clients is unsure of the currently trusted version).

tuf.client.updater.refresh(): Removed the retry_once stuff, waiting for a fix to the python 3 string issue causing unprintable exceptions.
test_indefinite_freeze_attack: Removed forced failure conditions that I'd left in for debugging the string issue. All should be in order again. As for this comment on cleaning up the test, I've tried to cut out pieces, but end up with behavior that surprises me. It may be that I'm failing to understand something.
For example, within test_with_tuf, for test 2, the signing key for timestamp is loaded again at current line 362, even though it was loaded earlier at current line 278. When I comment out the second loading, I get a failure to write the repository at line 371 with a complaint that there are not enough signatures to sign timestamp metadata. This leads me to guess that loading the repository again causes us to lose the timestamp keys. (Is that expected?) So I try commenting out the repository reload at 356, but somehow that leads to a different complaint at line 371's repository.write() call: that the root keys aren't loaded. The root keys aren't loaded, but they weren't necessary anywhere in this test previously (if I reloaded the repository and the timestamp keys). Why are the root keys necessary in this case?

I've created a branch on my repo that reliably produces the unrelated error of the possible bug noted and will in the future address it in a separate issue & PR.
Vlad, please let me know if there's anything left to do with this PR.

I think the only remaining issue is the unprintable exception.
You can override unicode() (as we do with str()) so that exception messages are correctly printed in Python 3.
See:
https://github.com/awwad/tuf/blob/detect_expiry_322_clean/tuf/__init__.py#L332

It wasn't a need for unicode(), but we figured it out. There were two bugs in tuf/init.py class NoWorkingMirrorError.
See c4ef697 (use of dictionary.iteritems() not possible in python 3) and 7cd20fe (uninstantiated logging object).

Hokay. NOW I think this PR is done. Hehehe.

I just recalled that import of tuf.log and logging were removed here:
https://github.com/theupdateframework/tuf/commit/1c51b8d732d553e87a3b4555b369294c75f2389e
That would explain the uninstantiated logging object.  I verified that we didn't break the commit above.

One reason why we might have missed the exceptions raised in init(): http://stackoverflow.com/questions/25374679/exception-in-python-exception-classs-str-missed

Yeah, exceptions in str() are sneaky.

WRT logging removal:
Right, I remember some traffic about this a while back. Should I remove the logging stuff again?

The issue that Alex fixed only occurs if you import tuf.log in init().  We now only import logging, so it should be fine.  I tried to import 'tuf.conf', and the 'tuf.log' file is not created (as we wish).

Correction: only occurs if you import log.py

Messed around with it and it seems OK to me on edge cases, too. Okay, so nothing else I'm aware of. I leave it to you. ^_^

I reviewed the changes and made edits here: https://github.com/theupdateframework/tuf/commit/dd8a7eb0dd155cdb672e27d1d86d4cc07064d77b
Please merge those changes with this pull request (if all my changes are good to go).


[Closes #5] Add mappings logs tool window

Resolves Issue 5: Output logs of mapping.
Implementation
It is implemented using BeControls from the JetBrains.IDE.UI.Extensions namespace - it is fully C# oriented (analog of Java Spring framework developed by JetBrains).
Example
It is a single-instance tool window, opening automatically only when unsuccessful mapping has occured.

I've added such a functionality:

if a mapping operation has completed successfully, tool window content is redrawn, however it is not shown.
if a mapping operation has failed, it is an explicit behaviour that it is shown so that user will definetely see what properties were not mapped correctly.


Scroll to button is showing when we are present on the top of the website

Description
The scrool to top of the website button are present when we are on the top so it should be remove from the webite when we are on the  top
Steps to Reproduce
Do some chnages on the code of the button
Expected Behavior
Then when we go down then the button is showing
Actual Behavior
When we pressnt on top of  the webiste then also it is present
Screenshots

Additional Information
No response
What browser are you seeing the problem on?

[ ] Firefox
[X] Chrome
[ ] Safari
[ ] Microsoft Edge

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

Not something we are looking for it.
Please understand.


Explore to use webpack for extensions

The idea is to use webpack for extensions with the goal of faster extension loading/activation and reduce installation size/time. We attempt to do this for emmet and git are because both are owned by us, reasonable complex, and activate on startup (*).

Numbers

Extension
Before
After
Delta

css
1759
34
-1725

emmet
201
61
-140

html
2094
292
-1802

json
696
297
-400

typescript
404
278
-126

Total saving is 4193 files 👏

@jrieken Looks great! I think a lot of the savings might come from not including devDependencies in node_modules. Now when I'm publishing extensions I always do yarn --prod, but of course I could use webpack too.
It would be great if we can put this to the documentation.

I think a lot of the savings might come from not including devDependencies in node_modules.

The vsce tool does that by default. I run yarn list --prod --json to know when runtime dependencies you have and bundles only those. Next step is to not bundle dependencies of excluded/bundled depenencies

@jrieken I don't think it does for devDependencies in subfolders, which are quite common in Language Server extensions.

it does for devDependencies in subfolders, which are quite common in Language Server extensions.

Yeah, that's something I have learnt over the weekend...


Styling with flex... Is it not possible to omit the sliderWidth and itemWidth and make it infer it from flex styles?

I want to put a carousel in between two icons on my page page. Think of it as:
icon1 horizontalCarousel icon2
Do I have to specify the sliderWidth and itemWidth? Can I not give flex properties?

Is this a bug report, a feature request, or a question?
Question

Have you followed the required steps before opening a bug report?
(Check the step you've followed - put an x character between the square brackets ([]).)

[x] I have read the guidelines regarding bug report.
[x] I have reviewed the documentation in its entirety, including the dedicated documentations :books:.
[x] I have searched for existing issues and made sure that the problem hasn't already been reported.
[x] I am using the latest plugin version.
[x] I am following the issue template closely in order to produce a useful bug report.

Have you made sure that it wasn't a React Native bug?
(Write your answer here.)
Yes

Is the bug specific to iOS or Android? Or can it be reproduced on both platforms?
(Write your answer here and specify the iOS/Android versions on which you've been able to reproduce the issue.)
Yes
Is the bug reproductible in a production environment (not a debug one)?
(Write your answer here.)
Yes

Environment

(Write your answer here.)
Expected Behavior

(Write what you thought would happen.)
Actual Behavior

(Write what happened. Add screencasts/screenshots!)
Reproducible Demo
(Paste the link to a Snack example in which the issue can be reproduced. Please follow the guidelines for providing a Minimal, Complete, and Verifiable example.)

Steps to Reproduce

(Write your steps so that anyone can reproduce the issue in the Snack demo you provided.)

+1

@batubb Sorry, please allow me to advertise for my open source library! ~
I think this library react-native-reanimated-carousel will solve your problem. It is a high performance and very simple component, complete with React-Native reanimated 2


Delete heading to make consistent with other enums

Also, begin the description with "Specifies..." like other enumerations.

Docs Build status updates of commit 7d6d185:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/Word.xlseriesnamelevel.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


add Committers Area.

FMPhotoPicker, lost the main maintainer in TMH.
so, we need more committer and maintainer in the worldwide.
in the future, I hope many committer and maintainer join FMPhotoPicker.

@congnd thanks!


Loading controller only when route is selected

Let's say I have two pages, cloud and settings. I have the following code set up:
var routerApp = angular.module('APP', ['ui.router']);

routerApp.config(function($stateProvider, $urlRouterProvider, $locationProvider) {

    $locationProvider.html5Mode(true);
    $urlRouterProvider.otherwise('/cloud');

    $stateProvider

        .state('cloud', {
            url: '/cloud',
            templateUrl: 'pages/templates/cloud.html',
            controller: 'cloud',
        })

        .state('settings', {
            url: '/settings',
            templateUrl: 'pages/templates/settings.html',
            controller: 'settings'
        });

});

routerApp.controller('cloud', function($scope, $http, $state) {
    alert("cloud");
});

routerApp.controller('settings', function($scope, $http, $state) {
    alert("settings");
});

Regardless of what page I load, settings or cloud, the each controller will run no matter what. Meaning I will get 2 alerts, regardless, when I reload the page.
Could anyone help explain what I need to do so that if I reload my website on /settings, only the code in my settings controller will run and vice versa?

I'm not seeing that behavior so you probably have something else going on: http://run.plnkr.co/FWbuOm6AO2FH3WnX/

I messed up, I actually had a ng-controller="cloud" in the html that made it load. Thanks for your help and testing it for me.


Regarding Some Commands

When will you add search command and other premium commands like setup channel which are available in EplayHq Bot...Still Waiting For It
Btw Noice Works

i'll update it frequently. For it'll be this as far.
Thanks


Liveness probe added in ContainerCard component

Hey, I just made a Pull Request!
Only Readiness probe is showing in ContainerCard component in Kubernetes PodDrawer, this PR will enable the Liveness Probe too in PodDrawer.

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

I would like this to be customizable since there are differing opinions about liveness probes in the community


[gdal] build failure

Operating system
windows 10 x64
Compiler
MSVC14
Steps to reproduce the behavior
./vcpkg install gdal:x64-windows

Failure logs
PS E:\vcpkg> .\vcpkg install gdal:x64-windows
Computing installation plan...
warning: vcpkg appears to be in a Visual Studio prompt targeting x86 but installing for x64-windows. Consider using --triplet x86-windows or --triplet x86-uwp.
The following packages will be built and installed:
<EMAIL_ADDRESS>Detecting compiler hash for triplet x64-windows...
-- Setting "%HTTP_PROXY%" environment variables to "<IP_ADDRESS>:9981".
-- Setting "%HTTPS_PROXY%" environment variables to "<IP_ADDRESS>:9981".
-- Setting "%SOCKS5_PROXY%" environment variables to "<IP_ADDRESS>:9981".
Compiler found: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64/cl.exe
Restored 0 package(s) from C:\Users\lenovo\AppData\Local\vcpkg\archives in 266 us. Use --debug to see more details.
Installing 1/1<EMAIL_ADDRESS>Building<EMAIL_ADDRESS>-- Using cached OSGeo-gdal-v3.9.2.tar.gz.
-- Cleaning sources at E:/vcpkg/buildtrees/gdal/src/v3.9.2-9586dcef0a.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source E:/vcpkg/downloads/OSGeo-gdal-v3.9.2.tar.gz
-- Applying patch find-link-libraries.patch
-- Applying patch fix-gdal-target-interfaces.patch
-- Applying patch libkml.patch
-- Applying patch target-is-valid.patch
-- Using source at E:/vcpkg/buildtrees/gdal/src/v3.9.2-9586dcef0a.clean
-- Configuring x64-windows
-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
Command failed: E:/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake.exe --build . --config Debug --target install -- -v -j9
Working Directory: E:/vcpkg/buildtrees/gdal/x64-windows-dbg
See logs for more information:
E:\vcpkg\buildtrees\gdal\install-x64-windows-dbg-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
ports/gdal/portfile.cmake:106 (vcpkg_cmake_install)
scripts/ports.cmake:192 (include)
error: building gdal:x64-windows failed with: BUILD_FAILED
See https://learn.microsoft.com/vcpkg/troubleshoot/build-failures?WT.mc_id=vcpkg_inproduct_cli for more information.
Elapsed time to handle gdal:x64-windows: 8.6 min
Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+gdal
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[gdal]+Build+error+on+x64-windows&body=Copy+issue+body+from+E%3A%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md
Additional context
install-x64-windows-dbg-out.log

It seems happen when installing. Is there anyway to avoid this problem?

e:\vcpkg\buildtrees\gdal\src\v3.9.2-9586dcef0a.clean\apps\argparse/argparse.hpp(1780): fatal error C1001: An internal error has occurred in the compiler.

Use newer compiler ¯\_(ツ)_/¯

e:\vcpkg\buildtrees\gdal\src\v3.9.2-9586dcef0a.clean\apps\argparse/argparse.hpp(1780): fatal error C1001: An internal error has occurred in the compiler.

Use newer compiler ¯\_(ツ)_/¯

Thanks for your help. It's the time to upgrade my vs version.


Primitive interface updates for EstimatorV2

Part of https://github.com/Qiskit/qiskit-ibm-runtime/issues/1131
Support EstimatorV2 input/output:

Input RFC Output RFC
Input would be one or more PUBs (Primitive Unified Bloc). Each is a tuple of (circuit, observables, parameter values).
Output would be PubResults

Based on the following Qiskit PRs Estimator 11227:

EstimatorV2 Container https://github.com/Qiskit/qiskit/pull/11524
BaseEstimator V2 https://github.com/Qiskit/qiskit/pull/11527

Some of the work has already been done in https://github.com/Qiskit/qiskit-ibm-runtime/pull/1224

Completed in 0.21.0 release