Redirect from .pressbutton document is "empty", browser obj appears to be from first posted page, not redirected page.

I have some existing code that was working in older versions of zombie.
browser.pressButton("op", function(err, newbrowser, status) {
callback(newbrowser);
});
What appears to be happening:

called .pressbutton, which results in a POST to a redirector (URL A below)

zombie does all the redirections (URL B & C below)

the pressbutton function returns the browser object from the first call  URL A, instead of from the final call URL C

browser in debug mode

A - Zombie: POST http://localhost/PSS/branches/DEV/MDD-1964/?destination=user/main
B - Zombie: POST /PSS/branches/DEV/MDD-1964/ => http://localhost/PSS/branches/DEV/MDD-1964/user/main
C - Zombie: GET http://localhost/PSS/branches/DEV/MDD-1964/user/main

dump of the browser object sent back , presumably with the /user/main URL:

Zombie: 0.12.15
URL: http://localhost/PSS/branches/DEV/MDD-1964/?destination=user/main
History:

http://localhost/PSS/branches/DEV/MDD-1964/
2: http://localhost/PSS/branches/DEV/MDD-1964/?destination=user/main

Cookies:
has_js=1; Domain=localhost; Path=/
SESS5bdd381815e0aa015e2eda0e2d3a6508=bdh-6SDizokuHGqvUf1X0w5lvfLsY76sOWm0FAaDlOI; Domain=localhost; Path=/; Max-Age=1999994994; HttpOnly
Storage:
Eventloop:
The time:   Fri Mar 02 2012 12:59:38 GMT-0600 (CST)
Timers:     0
Processing: 1
Waiting:    0
Document:

The following is a workaround (in my case) - if I cause it to reload the redirect page, then it moves on as it should
pressButton("op", function(err, newbrowsera, status) {
newbrowsera.reload(
function(err, newbrowser, status) {
callback(newbrowser); });
});

Improved workaround.
Appears that the browser doesn'ty like multiple redirects... as I accidentally let it sit for about a minute, and then zombie started spitting out trace info again... so, after poking around, here's my solution:
When the "wait" function returns (and setting different times/functions does nothing - it just returns after about 5 seconds regardless of what I put in there... no errors, nothing).. I noticed that there was still an item processing... so I'm checking for that.
pressButton("op", function(err, newbrowsera, status) {
browser.wait(function(error,nbrowser) {
waitForCompletion(browser,callback);
});
});
});
function waitForCompletion(browser,callback){
if(browser._eventloop._processing>0){
console.log('Waiting');
setTimeout(function(){waitForCompletion(browser,callback);},5000)
} else {
callback(browser);
}
}
This is a drupal website, which has multiple possible "layers" for redirects... so I think zombie is getting confused.  Zombie worked with my code up until a few months ago, so I imagine some of the recent changes aren't super friendly to redirects and pauses.  (In actuality, the page loads in around 5-10 seconds in a browser).

The wait using this method is always exactly one minute.

RESOLVED: sortof.  It's actually something that executes differently in jsdom vs. a browser.
Suppose you have a doc structured like so:

 some javascript code with an onready event
 jquery(document).ready(A) ;

What happens in a browser (firefox):

Load files in #1 and #2
Execute A and B

What happens in jsdom:

Load files in #1
Execute A
Execute B
Load files in #2

SO:
If you put the javascript src links in the header... and the document.ready calls at the end of the document.. then jsdom will load everything, and THEN fire the events as you expect.


ci: add OpenAPI linting and validation

Add an additional GitHub actions workflow for OpenAPI linting and validation.
Fixes https://github.com/ga4gh/task-execution-schemas/issues/178
The workflow contains the following three jobs, executed in parallel:

Action OpenAPI Lint Action, based on Redocly CLI:

Lints OpenAPI definition at openapi/task_execution_service.openapi.yaml

Action Swagger Editor Validator, based on a call to Swagger Editor:

Validates the OpenAPI definition at openapi/task_execution_service.openapi.yaml

Action OpenAPI Diff, based on OpenAPI Diff:

Only runs for pull requests!
Creates diff between openapi/task_execution_service.openapi.yaml definition in head and base/target branch
Highlights breaking, non-breaking and unclassified changes
Note that check will fail on changes (at least on breaking changes) and GitHub Actions currently does not support allow-failure (see issue)

@kellrott or @aniewielska: Both the lint and diff tests completed successfully (or as expected) when tested in my fork. I suspect the failing checks are due to the PR coming from a fork. Perhaps you could add the new workflow file from within this repo and see if tests pass. Alternatively, you could give me write permissions to this repo so that I can try it myself.
See relevant tests results in my fork:

Latest push to head branch for this PR
Test PR against branch for this PR to check behavior of diff job on breaking changes

Superseded by #181


Apostrophes in App Window Title Breaks Build

Describe the bug
When I add an apostrophe in the default window title in tauri.conf.json and build my app, I am met with an "custom.protocol.taurilocalhost’s server IP address could not be found." screen in the webview upon running.
To Reproduce
Steps to reproduce the behavior:

Open tauri.config.json
Find the default window object under the "windows" array and add an apostrophe to the "title" property's value.
Save the file and run yarn tauri build to build the app.
Run the compiled executable under src-tauri/target/release.

Expected behavior
The app should open normally and run as expected.
Screenshots

Platform and Versions (required):

Operating System - Windows, version 10.0.19041 X64
Webview2 - 91.0.864.64

Node.js environment
  Node.js - 14.15.5
  @tauri-apps/cli - 1.0.0-beta.5
  @tauri-apps/api - 1.0.0-beta.4

Global packages
  npm - 6.14.11
  yarn - 1.22.10

Rust environment
  rustc - 1.53.0
  cargo - 1.53.0

App directory structure
/node_modules
/src-tauri

App
  tauri.rs - 1.0.0-beta.4
  build-type - bundle
  CSP - default-src blob: data: filesystem: ws: wss: http: https: tauri: 'unsafe-eval' 'unsafe-inline' 'self' img-src: 'self'
  distDir - html5
  devPath - http://localhost:5500

Additional context
I have not tested this particular app on Linux or any other operating systems.

This is not related to the apostrophe. It has been fixed on wry and will be released soon.

Just found your bug fix in the wry repo. I somehow didn't see the original  "ERR_NAME_NOT_RESOLVED" bug report here before I submitted this issue. I also tried adding and removing the apostrophe before building enough times that I thought it was the real culprit. Anyways, thank you for your bug fix.


[SPARK-35739][SQL] Add Java-compatible Dataset.join overloads

What changes were proposed in this pull request?
Adds 3 new syntactic sugar overloads to Dataset's join method as proposed in SPARK-35739.
Why are the changes needed?
Improved development experience for developers using Spark SQL, specifically when coding in Java.
Prior to changes the Seq overloads required developers to use less-known Java-to-Scala converter methods that made code less readable.  The overloads internalize those converter calls for two of the new methods and the third method adds a single-item overload that is useful for both Java and Scala.
Does this PR introduce any user-facing change?
Yes, the three new overloads technically constitute an API change to the Dataset class.  These overloads are net-new and have been commented appropriately in line with the existing methods.
How was this patch tested?
Test cases were not added because it is unclear to me where/how syntactic sugar overloads fit into the testing suites (if at all).  Happy to add them if I can be pointed in the correct direction.

Changes were tested in Scala via spark-shell.
Changes were tested in Java by modifying an example:diff --git a/examples/src/main/java/org/apache/spark/examples/sql/JavaSparkSQLExample.java b/examples/src/main/java/org/apache/spark/examples/sql/JavaSparkSQLExample.java
index 86a9045d8a..342810c1e6 100644
--- a/examples/src/main/java/org/apache/spark/examples/sql/JavaSparkSQLExample.java
+++ b/examples/src/main/java/org/apache/spark/examples/sql/JavaSparkSQLExample.java
@@ -124,6 +124,10 @@ public class JavaSparkSQLExample {
     // |-- age: long (nullable = true)
     // |-- name: string (nullable = true)

+    df.join(df, new String[] {"age"}).show();
+    df.join(df, "age", "left").show();
+    df.join(df, new String[] {"age"}, "left").show();
+
     // Select only the "name" column
     df.select("name").show();
     // +-------+

Can you add a simple test for these?

ok to test

Test build #140994 has started for PR 33323 at commit 7beee40.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45508/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45508/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45508/

Test build #140994 has finished for PR 33323 at commit 7beee40.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140994/

Comments addressed, tests added, rebased onto current master.

Test build #142469 has started for PR 33323 at commit 52399ea.

Test build #142469 has finished for PR 33323 at commit 52399ea.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142469/

Had to push another revision due to a comment line being too long -.- sorry for the churn

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46976/

Test build #142470 has started for PR 33323 at commit 2314d1d.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46977/

Test build #142470 has finished for PR 33323 at commit 2314d1d.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142470/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46976/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46978/

Test build #142470 has finished for PR 33323 at commit 2314d1d.
* This patch **fails to build**.

* This patch merges cleanly.

* This patch adds no public classes.

Appears to have failed compilation with the following:
[warn] multiple main classes detected: run 'show discoveredMainClasses' to see the list
[error] ## Exception when compiling 493 sources to /home/jenkins/workspace/SparkPullRequestBuilder/sql/catalyst/target/scala-2.12/classes
[error] java.lang.StackOverflowError
[error] scala.reflect.api.Trees$Transformer.transform(Trees.scala:2563)
[error] scala.tools.nsc.transform.CleanUp$CleanUpTransformer.transform(CleanUp.scala:607)
[error] scala.tools.nsc.transform.CleanUp$CleanUpTransformer.transform(CleanUp.scala:37)
[error] scala.reflect.api.Trees$Transformer.$anonfun$transformStats$1(Trees.scala:2597)
[error] scala.reflect.api.Trees$Transformer.transformStats(Trees.scala:2595)
[error] scala.reflect.internal.Trees.itransform(Trees.scala:1430)
[error] scala.reflect.internal.Trees.itransform$(Trees.scala:1400)
[error] scala.reflect.internal.SymbolTable.itransform(SymbolTable.scala:28)
[error] scala.reflect.internal.SymbolTable.itransform(SymbolTable.scala:28)
[error] scala.reflect.api.Trees$Transformer.transform(Trees.scala:2563)
[error] scala.tools.nsc.transform.CleanUp$CleanUpTransformer.transform(CleanUp.scala:607)
...

Which appears to be unrelated to my change set?

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46976/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46977/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46977/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46978/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46978/

Seems the tests passed but mind addressing https://github.com/apache/spark/pull/33323#discussion_r688972950 comment?


Scheduled posts without auto saving

Issue Summary
With new posts which are not published yet (draft status) changes are saved automatically always. This feature is disabled as soon as you schedule an article for publication. Additionally changes to the main title of that article are not detected by ghost unless you manually click on "Reschedule". I wondered for some time why the preview of a scheduled post does not show the updated title and is also not reminding me about unsaved changes when leaving the article page in editor view.
To Reproduce

Create a new article
Write something including title (main headline) and body content
Schedule article for later
Modify the title
Title won't change / be saved unless you click on "Reschedule"

Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
Technical details:

Ghost Version: 2.23.2
Node Version: 10
Browser/OS: Chrome 75 macOS
Database: MariaDB

@MaluNoPeleke you can also hit Ctrl/Cmd+S to save. A scheduled post is the same as a "published" post in that the content is deemed to be final which is why an explicit save is required rather than the auto-save of drafts.
The behaviour is as expected so it's not a bug. However we are aware of the non-optimal UI of the save/publish post menu and it's on our internal roadmap for a redesign.

Thanks for the information and clarification.
Are you aware that changes to the title are currently also not detected in this mode so the browser won't stop you from leaving the page if you modified the title (which it does if you modify the body content)?

Are you aware that changes to the title are currently also not detected in this mode so the browser won't stop you from leaving the page if you modified the title

Strange, I'm not able to replicate that at all. If I change the title on a scheduled post then try to navigate away without saving I get the unsaved changes modal.

Yes, you are right, it must have been a one time only issue.


fix(app): critical bug when trying to create new key, fixes #381

This change ensures the Create a Secret Key functionality works.
Wondering how we can make this more robust. @hstove are we looking for a particular search param here, or just all of them?

Wondering how we can make this more robust. @hstove are we looking for a particular search param here, or just all of them?

TBH I'm having a brain fart this morning trying to remember exactly why we need them. I think, ideally, we shouldn't have to pass around query params like this. It might be due to a kind of 'race condition' when trying to parse the authRequest.


Fix leaking environment RIDs in GLES2

This PR adds the code necessary to correctly free environments in GLES2, which was previously missing causing them to leak.
Notes

This was showing up in the tracked_handles build (#54907)
On tracking this down, it turned out although the client code was correctly calling free, the freeing code in RasterizerScene had been forgotten
These will have been leaking during the editor and particularly during gameplay with multiple levels

Thanks!

Cherry-picked for 3.4.1.


Upon installation, add a Git Bash profile, if Git for Windows is present

Summary of the new feature/enhancement
When installing the terminal for the first time, it would be nice if a profile for Bash from Git for Windows would be automatically provided if Git for Windows is installed.
Proposed technical implementation details (optional)
Auto-detect via installer registry keys whether Git for Windows in installed, and if so, add an entry to profiles.json to run Bash from Git for Windows in the terminal app.

Tried to manually add but it opens in a separate window. Not sure if is compatible

If you are launching “mintty,” or if git bash is using “mintty,” it will launch in a separate window. We can’t fix that: they’ve chosen to launch their own terminal emulator.

The "trick" is that you must no run git-bash.exe (or git-cmd.exe) from the Git for Windows installation directory, as these hard-code to use mintty (or conhost) as the terminal, but you should use bin\bash.exe which just is the plain shell interpreter.

Specifically, use this JSON fragment to open Git Bash (if it's installed in the default location):
    "commandline" : "C:\\Program Files\\Git\\bin\\bash.exe",
    "icon" : "C:\\Program Files\\Git\\mingw64\\share\\git\\git-for-windows.ico",
    "name" : "Git Bash",
    "startingDirectory" : "%HOMEDRIVE%%HOMEPATH%"

Tried to manually add but it opens in a separate window. Not sure if is compatible

I also tried and see the same... it opens the git-bash.exe as a separate window

see the same

Good thing somebody responded with the actual fix :)

Issue extension and suggested name: Scan installed shell interpreters on Terminal first run/install and initial profiles.json generation
Scanning PATH for known shells at their default install locations. If a shell is present, add it (along with any custom fixes such as the 'bin\bash.exe' for Git for Windows. Essentially an enhancement for the function that scans names of configured WSL distros.
Fix PowerShell Core: on initial profiles.json generation, scan installed versions and name accordingly ('PowerShell Core '). Can get version from exe properties. Add icons to 'ms-appx://ProfileIcons' (pscore has some in assets folder. If detecting third-party interpreters, can or opt to try get from exe or ico if present in shell path). So that if you have both PSCore6 and PSCore7.0.0-preview or any other version installed prior to running Terminal for the first time, both PowerShells get registered on profiles.json.
Also to fix initial detection of cmd
Ideally (for this manually edited my profiles.json, but the intent is to have shells automatically detected) :

Scanning PATH for known shells at their default install locations.

Note that, strictly speaking, scanning PATH is not enough, as esp. Git for Windows often is not in the system PATH. Instead, Git for Windows (or shells in general) should be discovered by looking at the registry like I had proposed above. At the concrete example of Git for Windows the registry key to look at is InstallLocation at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Git_is1.

Tried to manually add but it opens in a separate window. Not sure if is compatible

I also tried and see the same... it opens the git-bash.exe as a separate window

use bin\bash.exe instead of git-bash.exe

We've got dynamic profile generation on our radar; #754 is in spec review #1258

I'm actually going to re-open this to make sure that it gets done once #754 is complete.

Here is a code snippet of my config file that has it loading in the terminal.  Thanks to everyone who contributed to the solution.  I'm using a custom icon, so it won't be in your path.
      {
        "acrylicOpacity": 0.5,
        "background": "#012456",
        "closeOnExit": true,
        "colorScheme": "Solarized Dark",
        "commandline": "C:\\Program Files\\Git\\bin\\bash.exe",
        "cursorColor": "#FFFFFF",
        "cursorShape": "bar",
        "fontFace": "Consolas",
        "fontSize": 10,
        "guid": "{72a69aca-322e-465d-a799-1d64dff65269}",
        "historySize": 9001,
        "icon": "C:\\Program Files\\Git\\git-bash.png",
        "name": "Git Bash",
        "padding": "0, 0, 0, 0",
        "snapOnInput": true,
        "startingDirectory": "%USERPROFILE%",
        "useAcrylic": false
      }

Just to add some notes I found (about the actual bash.exe path to use and startup parameters to launch a login shell):
https://stackoverflow.com/a/57369284/564226

You can find the Git for Windows icon at the following path:
C:\\Program Files\\Git\\mingw64\\share\\git\\git-for-windows.ico

Just to add some notes I found (about the actual bash.exe path to use and startup parameters to launch a login shell):
https://stackoverflow.com/a/57369284/564226

For posterity - this should be using "%PROGRAMFILES%\Git\bin\bash.exe", not "%PROGRAMFILES%\Git\usr\bin\bash.exe".  The latter doesn't seem to fully initialize the environment for bash (e.g. https://stackoverflow.com/questions/56839307/adding-git-bash-to-the-new-windows-terminal#comment110596050_57369284 ... also, compare the results of "uname -s" between a stock git bash outside of Terminal and what you get in Terminal when referencing the above two executables.  In my case, only "Git\bin\bash.exe" gives the "correct" result of MINGW64_T.  The latter gives MSYS_NT.)

The Git for Windows PR was merged, and Git for Windows v2.32.0-rc1 (or the next snapshot) will have this option.

That's awesome to hear! I guess I can close this then!
/dup https://github.com/git-for-windows/git/issues/3183
/dup https://github.com/git-for-windows/build-extra/pull/339


chat not working (using latest release)

https://github.com/PrismarineJS/prismarine-web-client/commit/1b08956d1071dfbcc0174471babc661c5a6f043c

you can send messages to the server, but no clients can receive them

Closed by #272


This view need to be fixed

I'm closing as it is part of https://github.com/block-bites/fondant-app/issues/87


Enable oesgx tool on Windows

The oesgx tool for detecting SGX capabilities should compile on Windows already but has not been enabled for it. We should just have it build in Win32 configs as well.

Resolved by #1028


Improve how repos from required modules are downloaded (i.e., make it more modular)

Problem
When downloading modules from cue.mod/dagger.mod, we have a regex that tries to match a repo prefix and path suffix from a URL. This has limited capability. It works well enough if you have .git to split them, or if it's GitHub, though.
As for authentication, it assumes a public repo (https) unless a --private-key argument is provided, in which case ssh is used. We need more authentication methods.
We could also benefit from downloading from import path, instead of just URL.
Solution
Make this more modular to be easier to add capabilities later:

Find URL to fetch:

Is it a URL? VCS?
Is it an import path? Vanity URL?

Download repo:

Try known vcs providers like Go does
Based on those, is downloading a zip available instead of a clone (e.g., GitHub)?

Authentication:

Try public
Try ssh forwarding
Check CLI arguments for additional methods

Closing. More context in parent issue: https://github.com/dagger/dagger/issues/2163.


Are chunk keys content-addressed like indicated in ArrayLake?

The ArrayLake documentation states that Zarr chunk keys are generated via the hash of its data.

When writing new chunk data, Arraylake uses a "content addressable" strategy to pick the keys to use in the object store; it computes a hash for each piece of data and then uses that hash as the key.

One artifact of this choice that I have noticed is that, when using Zarr's default compressor (i.e. Blosc w/ LZ4) on multiple threads, the chunk output is not deterministic and therefore the hash changes even though the data is logically identical, which I suppose causes you to write out multiple copies of the same chunk?
You can get deterministic hashes back by setting numcodecs.blosc.num_threads(1) but then performance of the shuffle filter tanks.
Is Icechunk employing the same content-addressable strategy?

No. We dropped that when moving from Arraylake repos to icechunk.
Icechunk keys are a form of random UID.

We should document this in the spec: https://icechunk.io/spec/

Icechunk keys are a form of random UID.

Interesting. So while there is still no locking necessary, it will be the case that an array with say large swaths of identical data chunks (e.g. all 1s) will now occupy multiple redundant blobs. Out of curiosity, what was the motivation for moving away from content-addressable keys?

what was the motivation for moving away from content-addressable keys

In order of increasing relevance:

There is a (small) performance impact of computing the hashes.
Arraylake had this feature but we didn't see important storage savings. Repeated chunks are usually very compressible.

Thanks for confirming both the initial question and the follow-ups.


Refactor Dependencies

We have

setup.cfg
environment.yml, and
nces_environment.yml

Ideally, we should allow user to decide
pip install "ontolearn [complete]"
pip install "ontolearn [base]" # without torch transformer etc.
as done many frameworks  such as dask.

requirement.txt file is added


[update] macro to implement Debug from Display and add Display implementation where needed

Related to issue : 1201

Replaced macro impl_display_from_debug with impl_debug_from_display

Added implementation of Display trait where needed.

Hi @hrouis and welcome! As I mentioned in #1201 unfortunately we won't accept a solution that introduces new dependencies. If you still want to tackle this issue you'll have to do it the long way.

Hello, thank you for your response I will adjust my PR to remove the dependency.

Nice! This looks really good. I imagine we might bikeshed a bit on what the new Display impls should look like. (The current PR changes them, and maybe the right approach is just to copy whatever the existing Debug-based output turns out to be)
Could you squash these commits so that none of them have the extra dep?

Done! I also considered copying the Debug output, but i thought it kind of defeats the purpose of this PR .
Happy to update if you think it is better to stay true to the Debug output :)

FTR @hrouis, you can ignore the fuzzing ci fails, fuzzing is currently broken, its unrelated to this PR.

Thanks for your contribution! Can you please squash this into a single commit, then in the commit log describe the change as it currently is. Cheers.

Could you rebase this now that #1200 is merged?

Oh, it's not merged. I'll just merge this then, it passes the fuzz tests on my local machine.

(Sorry for repeated ACKs, I have a "local" script running over SSH and I keep getting disconnected. I'll stop now.)

Thank you for all your remarks and feed back. This was very informative.


Add verbose settings-var (default=false) to display all labels (non-grouped)?

Maybe some users will prefer having all label-types listed in their notifications (e.g. Work fax: w, Main phone: x - y, Garden shed morse-code device: z - instead of all being under Other phone: w - x - y - z), so we could add a verbose (or similar) variable to the settings (default to false) which doesn't group number/email labels into "other" at all, but still groups the numbers/emails within each label. Most of that functionality can be reinstated from previous commits which removed it when in favour of "other", but wrapped in a conditional. Just an idea, so if you disagree feel free to close this.

Yeah, this could be a neat solution to the label debate. Something like settings.notifications.groupAll = false (by default), which if set to true would make notifications in a grouping-style similar to what we had before dce7bcfef3ec1c73aab59e0ae355dfce62ce213e (every label having its own group).
I am adding it to giobonvi-development before merging your branch, as it should be easier to revert the required commits (e.g translations).

I think that var-name could get confusing though - a boolean for xxx.groupAll will usually be construed as "group all the emails/phones into groups or not" whereas the intended use would be "group all emails/phones by their labels, rather than grouping the less common ones together under the 'other' label". I suggest perhaps using settings.notifications.compactGrouping = true (by default), with a comment above the setting explaining that the compact format groups less common types together under an "other" label to conserve space.

I was actually thinking of groupAllLabels and lost the "labels" part somewhere in my brain...
However, I prefer CompactGrouping as it is more immediate, thanks for the suggestion


error reaching us1.locationiq.com leaks API key

If there's any issue reaching us1.locationiq.com (DNS, down, whatever), your API key will be exposed in chat. Example (with now revoked API key):
<~xnaas> .w Middletown
<Sackbot> Unexpected error (HTTPSConnectionPool(host='us1.locationiq.com', port=443): Max retries exceeded with url: /v1/search.php?key=7c2455d4c9c4b8&q=Middletown&format=json&addressdetails=1&limit=1 (Caused by SSLError(SSLError(1, '[SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1056)')))) from xnaas at 2021-04-11 08:28:15.850762. Message was: .w Middletown

I imagine it probably...shouldn't do that?

Should be solved in https://github.com/sopel-irc/sopel-weather/commit/98b912db9405ebc28b9775bc94596a54dd926187


Do not run TestTLSCertificateRotation in parallel with other tests

Backport from upstream.
This test deletes the serving-tests/serving-certs during the test run. This might break the other test TestSystemInternalTLS because it waits for certain log lines to appear in the service pods. Deleting the serving-certs secret causes the application pods to be deleted so that the new cert can be mounted. And waiting for given log lines then fails because the pod no longer exists:
system_internal_tls_test.go:110: TLS not used on requests to queue-proxy: pods
"system-internal-tls-wgvxqtyx-00001-deployment-6fdc4c8c7d-4ll8q" not found
What this PR does / why we need it:
Which issue(s) this PR fixes:
JIRA:
Does this PR needs for other branches:

Does this PR (patch) needs to update/drop in the future?:

JIRA:

/cherry-pick release-v1.15
/cc @ReToCode


api: move #Resources to package holos

Previously, the #Resources struct listing valid resources to use with
APIObjects in each of the components types was closed.  This made it
very difficult for users to mix in new resources and use the Kubernetes
component kind.
This patch moves the definition of the valid resources to package holos
from the schema API.  The schema still enforces some light constraints,
but doesn't keep the struct closed.
A new convention is introduced in the form of configuring all components
using _ComponentConfig defined at the root, then unifying this struct
with all of the component kinds.  See schema.gen.cue for how this works.
This approach enables mixing in ArgoCD applications to all component
kinds, not just Helm as was done previously.  Similarly, the
user-constrained #Resources definition unifies with all component kinds.
It's OK to leave the yaml.Marshall in the schema API.  The user
shouldn't ever have to deal with #APIObjects, instead they should pass
Resources through the schema API which will use APIObjects to create
apiObjectMap for each component type and the BuildPlan.
This is still more awkward than I want, but it's a good step in the
right direction.
Closes: #237

We can add arbitrary resources when #Resources is left open by the user.
cue export --out yaml ./components/namespaces

kind: BuildPlan
apiVersion: v1alpha3
spec:
  components:
    kubernetesObjectsList:
      - kind: KubernetesObjects
        apiVersion: v1alpha3
        metadata:
          name: namespaces
        apiObjectMap:
          Jeff:
            foo: |
              kind: Jeff
              metadata:
                name: foo
        skip: false

diff --git a/components/namespaces/namespaces.cue b/components/namespaces/namespaces.cue
index a6cc0f2..bee6810 100644
--- a/components/namespaces/namespaces.cue
+++ b/components/namespaces/namespaces.cue
@@ -2,7 +2,8 @@ package holos

 let Objects = {
        Name: "namespaces"
-       Resources: Namespace: #Namespaces
+       // Resources: Namespace: #Namespaces
+       Resources: Jeff: foo: _
 }

 // Produce a kubernetes objects build plan.

resources.cue
package holos

import (
	corev1 "k8s.io/api/core/v1"
	appsv1 "k8s.io/api/apps/v1"
	rbacv1 "k8s.io/api/rbac/v1"
	batchv1 "k8s.io/api/batch/v1"

	ci "cert-manager.io/clusterissuer/v1"
	rgv1 "gateway.networking.k8s.io/referencegrant/v1beta1"
	certv1 "cert-manager.io/certificate/v1"
	hrv1 "gateway.networking.k8s.io/httproute/v1"
	gwv1 "gateway.networking.k8s.io/gateway/v1"
)

#Resources: {
	[Kind=string]: [InternalLabel=string]: {
		kind: Kind
		metadata: name: string | *InternalLabel
	}

	Certificate: [_]:        certv1.#Certificate
	ClusterIssuer: [_]:      ci.#ClusterIssuer
	ClusterRole: [_]:        rbacv1.#ClusterRole
	ClusterRoleBinding: [_]: rbacv1.#ClusterRoleBinding
	ConfigMap: [_]:          corev1.#ConfigMap
	CronJob: [_]:            batchv1.#CronJob
	Deployment: [_]:         appsv1.#Deployment
	HTTPRoute: [_]:          hrv1.#HTTPRoute
	Job: [_]:                batchv1.#Job
	Namespace: [_]:          corev1.#Namespace
	ReferenceGrant: [_]:     rgv1.#ReferenceGrant
	Role: [_]:               rbacv1.#Role
	RoleBinding: [_]:        rbacv1.#RoleBinding
	Service: [_]:            corev1.#Service
	ServiceAccount: [_]:     corev1.#ServiceAccount
	StatefulSet: [_]:        appsv1.#StatefulSet

	Gateway: [_]: gwv1.#Gateway & {
		spec: gatewayClassName: string | *"istio"
	}
}

An open question is how to close this down now, but that's for another day and it's not clear it's necessary.


Add test for Vault Enterprise install

Adds test for vault enterprise install

@infosecgithub

Please review https://github.com/hashicorp/terraform-aws-vault/pull/87 before this one and I will rebase appropriately


Shallow clone will be faster then full clone

Please fill up those following information before send Pull request

Pull request NO:
Agent repository URL:
Testcases repository URL:

Already done in Ref: #58 and close this PR


Search by commit SHA shouldn't require 7 characters

For some reason, search by commit SHA (eg. commit:12ab345) currently requires 7 letters; so 12ab345 would work but 12ab wouldn't, even though it works on the commandline and is unambiguous: git log 12ab works.
GitLens shouldn't require 7 letters, and and set of unambiguous letters should work.  Typing 7 letters is too annoying.

I can't reproduce this.
Here I am searching for 1bf4, which is unambiguous:

Here I am searching for 1bf, which is ambiguous (and thus doesn't return any results):

I can't reproduce this.
Here I am searching for 1bf4, which is unambiguous:

Here I am searching for 1bf, which is ambiguous (and thus doesn't return any results):


AbstractIndexedTable{RowType} <: AbstractArray{RowType}

Is that something we could have? We can fallback to Any if the row type is not clear, but I think there are many cases where the row type can be computed easily.
Background:
I have my own row type, that already works great with the table interface.
In other parts of my code I have functions defined like:
algorithm(::AbstractArray{<: MyRowType})

With the requested change, I could easily make those algorithms work on JuliaDB / IndexedTables etc, without it caring about it ;)
@piever mentioned, that this is how StructArrays works already, and StructArrays is actually used as the underlying container in InexedTables, so that would make the change even easier?!

I tend to prefer avoiding making tables act like arrays and vice versa.  Why not rely on the tables interface for algorithm?
If your code already works with StructArrays, you can use rows(tbl) to get a StructArray.

Hm, I guess I argument goes pretty similar as yours :D
I prefer avoiding writing anything specific to tables and would love to just define my algorithms on AbstractArray{<: Row}, without anyone needing to figure out, that rows(collection) needs to be called before calling the algorithm ;)

I'm not aware of the technical advantages/disadvantages of having them be an AbstractArray, but maybe it'd be enough to define a convert(::Type{AbstractArray}, t::IndexedTable) to return the StructArray of rows and you could call convert(::Type{AbstractArray}, t) before running your algorithm? Alternatively something like Tables.rows(t) is your best chance of getting something that works for all table types, even though not all tables implement rows as an AbstractArray: https://github.com/JuliaData/Tables.jl/pull/50.


Bug in notes.txt: Incorrect release name hardcoded (hyperswitch-stack)

Description:
In the notes.txt file of the hyperswitch-stack Helm chart, there is a small bug where the release name is hardcoded incorrectly. This bug can cause confusion during port-forward.
Location of Bug:
The bug is located in the  notes.txt within the hyperswitch-stack Helm chart
Reproduction of Issue caused
Helm install output:
> helm install hyperswitch-v1 . -n hyperswitch
W0330 20:13:37.389460   18336 warnings.go:70] metadata.name: this is used in Pod names and hostnames, which can result in surprising behavior; a DNS label is recommended: [must not contain dots]
NAME: hyperswitch-v1
LAST DEPLOYED: Sat Mar 30 20:13:31 2024
NAMESPACE: hyperswitch
STATUS: deployed
REVISION: 1
NOTES:
1. Get the application URL by running these commands:

export ADDRESS_CREATED=$(kubectl get ingress -n hyperswitch -o jsonpath="{.items[0].status.addresses[0].address}")
if [ -z "$ADDRESS_CREATED" ]
then
  kubectl port-forward deployment/hyperswitch-server-v1o52o1v2 8080:8080 -n hyperswitch & \
  kubectl port-forward deployment/hyperswitch-control-center-0f746cb72517 9000:9000 -n hyperswitch & \
  kubectl port-forward service/hypers-v1-hyperswitchsdk 9090:9090 -n hyperswitch & \  ## INCORRECT NAME OF SERVICE
  echo "======================================================"
  echo "** App server running on: http://localhost:8080      **"
  echo "** Control center running on: http://localhost:9000  **"
  echo "** Hyperswitch Web running on: http://localhost:9090 **"
  echo "======================================================"
  echo "\nRun this command to close exposed ports kill\n"
  echo "kill \$( lsof -i:8080 -t ) && kill \$( lsof -i:9090 -t ) && kill \$( lsof -i:9000 -t )"
  echo "======================================================"
else
  kubectl get ingress -n hyperswitch
fi

When I follow the command provided, the error:
> kubectl port-forward service/hypers-v1-hyperswitchsdk 9090:9090 -n hyperswitch
Error from server (NotFound): services "hypers-v1-hyperswitchsdk" not found

Whereas the name of the service is: {{ .Chart.name }}-hyperswitchsdk

Can you assign this bug to me? I can pick this one up

Can you assign this bug to me? I can pick this one up

Sure!

Closing as completed in #79.


Fix changelog.md typo

Hello, you can pull the latest code, and re-push or force push, to trigger and pass the check


Sign up page is not responsive...

The Sign-up page given by Akshat is not responsive and not mobile-ready...
I think that we should only include Google OAuth as a way to sign in and remove local authentication.
See localhost/authorize/create

I agree, google oauth is the simplest

And everyone uses it...
So no need of setting up a local auth.


a bug for imports_dir options

in file protobuffs_compile.erl, function scan_string/3 at line 68 around, there is a bug for ImportPaths variate:
ImportPaths = ["./", "src/" | proplists:get_value(imports_dir, Options, [])],
because erlang language will treat string as a list, so list operation will flatten list, for example, the code following:
Options = [{imports_dir, "dir/"}],
ImportPaths = ["./", "src/" | proplists:get_value(imports_dir, Options, [])]
the ImportPaths is ["./","src/",100,105,114,47], while we expect the result is ["./","src/", "dir/"]
so, I think the right code maybe :
ImportPaths =
case proplists:get_value(imports_dir, Options) of
undefined -> ["./", "src/"];
ImportDir -> [ImportDir, "./", "src/"]
end,
is there anything i am wrong?

imports_dir is supposed to be a list of dir.


Create common Rust workspace

On repo's root, create common Rust workspace, containing shared components between the other Rust components.
At first, it should contain our Merkle tree implementation.

Close with #59


remove bad chimp example

@ens-st3 - if required

@msmanoj can you push out as a post release bugfix ?

@ens-st3 sure, i'll get it pushed ASAP after the release.

Hi @sarahhunt, could you check if this change looks good on live, please? Thanks

That looks good - thanks @msmanoj !


fix: fix output banner for yaml and json

fix output banner for yaml and json

Codecov Report
Attention: 16 lines in your changes are missing coverage. Please review.

Comparison is base (6e20381) 48.16% compared to head (73ff4ad) 48.08%.

Files
Patch %
Lines

pkg/kor/multi.go
0.00%
10 Missing :warning:

pkg/kor/kor.go
0.00%
4 Missing :warning:

pkg/kor/all.go
0.00%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #153      +/-   ##
==========================================
- Coverage   48.16%   48.08%   -0.09%
==========================================
  Files          20       20
  Lines        1802     1805       +3
==========================================
  Hits          868      868
- Misses        789      792       +3
  Partials      145      145

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


pull request for e2e test at 11/28/2016 15:26:04

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Using Canvas feature

In the canvas feature,
I think it’s better if the word used to ‘imagine’ can be auto-used as the Title.

Deprecated this flow so closing this ticket. Thanks for the feedback!


Tag docker images with version

It would be great, if the docker images could get tagged with a version, something like sinusbot/docker:1.0.0. This has several benefits.

Consistent version of the bot between different servers

Maybe a bug gets introduced in a newer version, then an older version can be choosen

Docker best practice

When building images, always tag them with useful tags which codify version information, intended destination (prod or test, for instance), stability, or other information that is useful when deploying the application in different environments. Do not rely on the automatically-created latest tag.

https://docs.docker.com/develop/dev-best-practices/

Hi,
yes this is indeed best practice but since we where in alpha/beta phase before we generally only wanted people to run the latest release since older releases do generally contain more bugs and miss many new features that the new scripts require to work.
Since the latest release of 1.0.0-beta.1 however we're moving into stable territory and tagging the versions is beginning to make sense.
Of course we will still only support the latest release at the moment and the SinusBot should always be kept up to date since regressions are rare, especially in the stable-isch non-insider releases and scripting updates are important.
TL;DR: yes, soon™
Buuut... old versions expire after a certain amount of time so you will not be able to run them after they reach a certain age. This will not change.
/cc @flyth

Added version tags, you can view the complete here: https://hub.docker.com/r/sinusbot/docker/tags
Note to quay.io users:
These tags are not available on quay.io yet. If someone actually cares about that for some reason: remind me to fix it.
Why do people even care about quay.io?
Note to maintainers:
This now requires manually building and pushing with the ./release.sh <version> helper script (use docker login before running it).
It would make sense to automate this via CI - I don't really care right now though sooo have fun.


[WIP] Remote torchserve deployment - Mnist examples

What changes are proposed in this pull request?
The current verison of MNIST example saves the model as state_dict using mlflow.pytorch.save_state_dict. Since, the mlflow.pytorch.save_state_dict does not contain MLModel file, it is not possible to register the model into MLflow.
Updating the example with model registration.
How is this patch tested?
Local and remote torchserve deployment
Existing unit tests
Release Notes
Is this a user-facing change?

[x] No. You can skip the rest of this section.
[ ] Yes. Give a description of this change to be included in the release notes for MLflow TorchServe Deployment Plugin users.

(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
What component(s) does this PR affect?
Components

[ ] area/deploy: Main deployment plugin logic
[ ] area/build: Build and test infrastructure for MLflow TorchServe Deployment Plugin
[ ] area/docs: MLflow TorchServe Deployment Plugin documentation pages
[ ] area/examples: Example code

How should the PR be classified in the release notes? Choose one:

[ ] rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
[x] rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
[ ] rn/feature - A new user-facing feature worth mentioning in the release notes
[ ] rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
[ ] rn/documentation - A user-facing documentation change worth mentioning in the release notes

remote_torchserve_test.txt


"missing field workspace" when running in docker

I have a cosmwasm contract and I'm running the optimizer via docker like this in the contract directory:
docker run --rm -v "$(pwd)":/code   --mount type=volume,source="$(basename "$(pwd)")_cache",target=/code/target   --mount type=volume,source=registry_cache,target=/usr/local/cargo/registry -e RUST_BACKTRACE=full   cosmwasm/workspace-optimizer:0.12.6

And it gives the following error:
1.60.0-x86_64-unknown-linux-musl (default)
cargo 1.60.0 (d1fd9fe2c 2022-03-01)
Building artifacts in workspace ...
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { inner: ErrorInner { kind: Custom, line: None, col: 0, message: "missing field `workspace`", key: [] } }', src/main.rs:35:55

The contract code is here

Facing the same issue similar to the issue above , and i have been struggling to overcome this issue. Please we need an urgent response to this situation.

If you compile a single contract project instead of a workspace, use cosmwasm/rust-optimizer instead of cosmwasm/workspace-optimizer

Thank you for your time and feedback. I stopped having that issue but another was introduced.
Error:
rust warning: spurious network error (2 tries remaining): failed to resolve address for github.com: Try again; class=Net (12) error: failed to get cw-controllersas a dependency of packagecw4-group v1.1.0 (/code)`
Caused by:
failed to load source for dependency cw-controllers
Caused by:
Unable to update /packages/controllers
Caused by:
failed to read /packages/controllers/Cargo.toml
Caused by:
No such file or directory (os error 2)
`
And i checked all the files and folder but they where in the right position.
Your feedback will be appreciated again.

Please I need a Feedback.
How long does it take to get a reply.

Looks like network issues / wrong dependenciea sources maybe?
Do you know Google? It pretty good search engine is.

In the next update 0.15.0, the two images will be unified. See https://github.com/CosmWasm/rust-optimizer/pull/143. With this change the original issue does not happen anymore since there is only one image that works for both single contract and workspace projects.


Fixing print statement and starting clients #8

I attempted to use this tool today but ran into a few issues.
First was the following exception:
/usr/bin/python3.4 elasticsearch-stress-test.py  --es_address internal-radar-loa-elastics-V0IPG0MET5WO-523946241.us-west-2.elb.amazonaws.com --indices 25 --documents 5 --seconds 300 --not-green --clients 5 --number-of-shards 2 --number-of-replicas 1 --no-cleanup --stats-frequency 10
  File "elasticsearch-stress-test.py", line 388
    print "Ctrl-c received! Sending kill to threads..."
                                                      ^
SyntaxError: Missing parentheses in call to 'print'

After I fixed that I hit this following exception:
/usr/bin/python3.4 elasticsearch-stress-test.py  --es_address internal-radar-loa-elastics-V0IPG0MET5WO-523946241.us-west-2.elb.amazonaws.com --indices 25 --documents 5 --seconds 300 --not-green --clients 5 --number-of-shards 2 --number-of-replicas 1 --no-cleanup --stats-frequency 10

Starting initialization of internal-radar-loa-elastics-V0IPG0MET5WO-523946241.us-west-2.elb.amazonaws.com
Done!
Creating indices..
Generating documents and workers..
Done!
Starting the test. Will print stats every 10 seconds.
The test would run for 300 seconds, but it might take a bit more because we are waiting for current bulk operation to complete.

Test is done! Final results:
Elapsed time: 4 seconds
Successful bulks: 0 (0 documents)
Failed bulks: 0 (0 documents)
Indexed approximately 0.0 MB which is 0.00 MB/s

LGTM, thanks @aboutte!
This was written for python 2.7, there might be more compatibility issues hidden..


Cross-compiling or statically linking sqlx fails because of OpenSSL

Hello! Thank you for such an awesome Rust SQL client. We've been trying it out at work, and it looks super-promising. We'd love to use it to replace diesel and tokio-postgres in some of our open source tools.
However, many of our open source tools like falconeri and dbcrossbar are shipped as statically-linked binaries using my rust-musl-builder. (rust-musl-builder seems to be popular for other Rust projects, with something like 740,000 downloads. So if I can figure out how to make sqlx work for me, that would hopefully help out some other people, too.)
The problem: Compile-time OpenSSL connections cause linker headaches when cross-compiling
In order to produce a statically-linked binary using sqlx, we need to compile it twice, for two different environments:

The host environment. Here, sqlx-macros is compiled against GNU Libc, and Rust requires it to be a shared library that can be loaded as a "plugin" for the compiler.
The target environment. Here, sqlx is compiled against musl-libc, which is a 100% static C library that will allow a Rust binary to work on any Linux distribution with a modern kernel. This is super-useful for distributing one Linux binary that works everywhere. In this case, sqlx must be compiled as a static library, not a shared one.

The problem occurs because:

sqlx-rt always links against OpenSSL, in both the host and target environments.
The Rust openssl-sys library can be configured to link either statically or dynamically using OPENSSL_STATIC, but we're forced to choose one.

Here are three proposed solutions. I'd be happy to submit a PR for any of them.
Proposed solution 1: Fix openssl-sys to support both static and dynamic versions of OpenSSL at the same time
This is possible, but it might be complicated. The only reason to do this would be to link against OpenSSL in a macro while cross-compiling. But OpenSSL is native C code, and it makes everything related to cross-compiling excessively difficult.
Proposed solution 2: Modify sqlx-macros to have an offline-only feature
I could submit a PR that modified sqlx-macros to support an offline-only feature that required an up-to-date sqlx-data.json file, and that had no ability to connect to the database. This would only be useful when cross-compiling. This might be a relatively simple solution for people who can pass --features to cargo build when cross compiling, and who can set up appropriate features.
Proposed solution 3: Add support for rustls to sqlx-rt
If solution (2) seems unappealing, another option would be to allow using sqlx-rt without any C dependencies at all. To do this, we could use a native Rust library like rustls. I've used this in other Rust projects, and it seems to be well behaved and easy to set up.
If we had support for rustls, cross-compiling would magically work, even for people who just have a stock Rust install. There would be no need for tools like rust-musl-builder.
I'd also be happy to submit a PR for this approach.
Next steps

Does this seem like a problem worth solving?
If I send you a PR solving this problem, would you be interested in merging it?
Which of the proposed solutions above (1, 2 or 3) seems like the best approach?

I'd be delighted to send you a PR + documentation. And I could add an sqlx-specific test to rust-musl-builder to make sure that every release of rust-musl-builder still supports cross-compiling with sqlx. This would make it very easy for Rust developers to build static Rust binaries using sqlx.
Once again, thank you very much for such an awesome Rust SQL interface! I really love the way it allows us to use natural SQL while still preserving the benefits of Rust's type checking.

For an immediate workaround, look to:
https://github.com/launchbadge/sqlx/issues/473#issuecomment-655517309

I don't mind adding support for rustls. It's just non-trivial because of a limitation with Cargo.
See: https://github.com/launchbadge/sqlx/issues/575#issuecomment-664962185

There's a very promising fix proposed in https://github.com/sfackler/rust-openssl/issues/1337#issuecomment-685735809.
I'm going to try adding this to rust-musl-builder and see what happens.

I have updated rust-musl-builder to set:
X86_64_UNKNOWN_LINUX_MUSL_OPENSSL_DIR=/usr/local/musl/
X86_64_UNKNOWN_LINUX_MUSL_OPENSSL_STATIC=1

...as proposed at https://github.com/sfackler/rust-openssl/issues/1337#issuecomment-685735809. This makes sqlx work very nicely, out of the box. I've also added an sqlx example program to rust-musl-builder, and it's compiled as part of the test suite.  It's still necessary to use cargo sqlx prepare to avoid connecting to a database at buid time.
Thank you for your help figuring this out! I'm delighted to be able to build entirely static Linux binaries using sqlx, and I hope this helps somebody else.


Improve Static Application Security Testing Results

Describe the bug
I notice you've got Sonarqube setup as a workflow action however none of the identified issues (which also pinged on our internal SAST analyser) appear to have been fixed.
Consequently, I've forked the code and produced a public version of Sonarqube analysis which provides an overall score of E.
Notable concerns are:

Use of MD5 for seeding AES
Disabling of TLS verification instead of using a local CA
Apparent Redirect URLs based on User Input

I believe all 3 of these are OWASP baselines, there's a further 307 code smells noted: https://sonarcloud.io/project/issues?resolved=false&types=CODE_SMELL&id=perlboy_mock-data-holder
To Reproduce
Steps to reproduce the behavior:

Enable Sonarqube
Work through issues
Fix code

Expected behaviour
Good code quality should be a prerequisite when promoting an example data holder within a highly secure ecosystem.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context

Thank you for taking the time to review the Mock Data Holder and provide feedback.
The current list of Sonarqube open items can be found here - https://sonarcloud.io/summary/overall?id=ConsumerDataRight_mock-data-holder
An unreviewed Sonarqube list differs from the reviewed Sonarqube list as the issues requiring no action have been closed. When reviewing the Sonarqube results, the following context was applied when deciding if an issue needed to be resolved or not - The goal of the Mock Solutions is to provide a set of tools to assist participants to develop and test their own solutions. They need to be easy to use and provide a way to see what is going on inside when dealing with requests and responses.
Transparency and code quality are important. The items that need addressing have been left open and are visible to all. A large number of the remaining items will be resolved in the next release that is being prepared.


Save gitea specific settings for vscode

e.g. allow to run tests from IDE

Sponsored by Kithara Software GmbH

If I have custom settings, it will be overwritten by this change?

this file has been add in here now. https://github.com/go-gitea/gitea/blob/0196b3583a09131f42dd0a364ad46babd5f12e04/contrib/ide/vscode/settings.json#L1-L4

Ah, we already have it. So this PR is unnecessary?

for beginner it's easy to just clone and start ... not sure why we should complicate onboarding ...

for beginner it's easy to just clone and start ... not sure why we should complicate onboarding ...

It would cause a lot of conflicts for developers who want to modify .vscode/settings.json, unless you could be 100% sure that nobody would edit the settings.json for their personal usage.

I have said here. https://github.com/go-gitea/gitea/pull/32279#issuecomment-2418242286
You can not change the workspace level settings any more. I think this should be blocked.

Inactive for long time.
Again: I do not think this change is right for developers who need to write their own settings.json

@6543 still I do not think it is right (unless the developers never edit this setting file). Correct me if I am wrong since I am not a heavy VSCode user.

for beginner it's easy to just clone and start ... not sure why we should complicate onboarding ...

Maybe it would be better if we move the contrib/ide/vscode folder to .vscode in the project root directory.


Flask-vue-curd on Google Cloud

Hi,
Can you please tell me how I can load this on Google Cloud ? Since it needs 2 ports to be used(5000 and 8080), How can I deploy and access it on Google Cloud ?

@siliconberry Check to see if this answers your question:
<EMAIL_ADDRESS>


Install script

Implement a install script for an automated installation.
It should provide options to

install the scheme file globally
specify a custom path to the scheme file
increase the verbosity
print a help

This includes error- and exit code handling.
The default installation type should be local and the default scheme file is src/xml/nord.xml as implemented in #1.


Angelic Search

Added angelic search algorithm tests and notebook.
Angelic search is not running correctly in all instances
Making progress is not implemented yet.

There are still conflicts. I see that you have made some changes to your master fork of the repository. I am not an expert with git, so there may be another way around this, but this is what I would do:

Delete my fork entirely (remember to store somewhere your changes!)
Fork the repo anew.
Create a fork on that repo.
On that fork, add your changes.
Create a Pull-Request.

@MrDupin @MariannaSpyrakou
The following could also be a way :
git checkout master
git reset --hard <ShaOfTheDesiredCommit>

Sha can be found with git reflog.


Obtain metrics per class on custom dataset

💡 Your Question
Hello,
Is there any way to get the metrics results for each class in the dataset?
I am training YOLO-NAS on a two class custom dataset, and it would be very useful to have the model performance for each class. Something similar to what YOLOv5 and YOLOv8 show:

Thanks in advance for any help
Versions
No response

The PR with this change is merged in master and should be available in the next SG release.
Or you can install master branch from git and use it today.
You will need to provide include_classwise_ap: True for DetectionMetric class in YAML (Or via code) and (optionally) class names.

I got an error while trying to add this:
        DetectionMetrics_050_095(             score_thres=0.1,             top_k_predictions=300,             num_cls=107,             normalize_targets=True,             include_classwise_ap=True,             post_prediction_callback=PPYoloEPostPredictionCallback(                 score_threshold=0.01,                 nms_top_k=1000,                 max_predictions=300,                 nms_threshold=0.7             )

Hi, which version to download to get this feature? I have 3.1.1

@gsrujana I have tried on 3.5.0, It works~


[APIM 2.2.0] Charset is not Removing in Tenant API

Description
The below mediation sequence is used to remove the charset from requests
<?xml version="1.0" encoding="UTF-8"?>
<sequence xmlns="http://ws.apache.org/ns/synapse" name="sample-sequence">
   <property name="setCharacterEncoding" value="false" scope="axis2"/>
</sequence>

The sequence is working as expected for Carbon Super tenant but not for Tenant specific APIs.
Reproducing Steps

Start a WSO2 APIM 2.2.0 Pack
Create a Tenant and publish an API
Add the above-mentioned sequence as in-sequence
Enable the Wire logs and invoke the API (POST) and analyze the Headers

Fixed by https://github.com/wso2/carbon-kernel/pull/3195


FORM_ID columns in HEADER, RECEIVED_FILINGS and FILER_FILINGS are inconsistently named

The are 38 tables in the SoS table set that list the form that the data comes from. In 35 of the tables, the column is FORM_TYPE and in 3 of them the column is FORM_ID. This is inconsistent for no reason at all. The FORM_TYPE columns are all VARCHAR2(8) and the 3 FORM_ID columns are VARCHAR2(7).
The columns should be renamed in the model and the import fixed, if there is any issue with it. It will just be easier to work with if this is so. If nobody objects, I can do this at some point. Just checking.

Question: Did the state name the fields differently, or is this a variation that we introduced?

The state named them differently. But that is no reason not to fix them. :-)

To me, this is a philosophical software design question.
I totally agree that it's silly for these fields to have different names. But he scope of this app has been narrowly defined to only be a 1:1 download of the state data, as much as possible. If the state gave them different names, our design dictates ours should have different names. Though we should explain their similarity in our field help_text and model documentation.
The problem you're pointing out, in my opinion, is best solved in second-layer likes like our campaign-browser, where we make oodles of decisions about how to transform and improve the state's data structure.

Agreed.


Circular dependencies

After running npm build, it seems like some instances and functions are duplicated.
For example, there are two INTERNAL_SYMBOL in packages\core\dist\syncedstore.js
var INTERNAL_SYMBOL$1 = Symbol("INTERNAL_SYMBOL");
var INTERNAL_SYMBOL = Symbol("INTERNAL_SYMBOL");

I can't reproduce this issue, let me know if you're still running into this after updating your repo


Filter on several attributes

Hi,
I would like to know if it is possible to filter not only on 1 attribute, but on several like :
       filterProperties: ['title','description']  // This doesn't work

So, if one of the 2 attributes contains what's in the textFilter, then it's kept in the list.
Thank you & kind regards

@kyoshiro2708  I am facing the problem ! Any lead ?

If I'm right, it seems that you misunderstand the usage of filterProperties .

assume the user searches for "fish"

{name: 'fish', description: 'fish', color: 'blue'}

filterProperties: ['name', 'description'] ... The object will be matched and passed to the array in update
filterProperties: ['name', 'color']       ... The object will NOT be matched or passed to the array in update

So in your case, when you input 'abc',  items will be considered matched only when both  title = 'abc'  and description = 'abc' .
If you want to filter items by more than one attribute, use the comparator  instead of filterProperties .


Verify displayed items instead of verifying the list's existence in xxxxScreenTest tests

We should check if the items exist. The list is still a list even when it's empty.

I would like to work on this issue. :hand:
Is it correct that I am correcting this type of test that was pointed out to me before with this task?
https://github.com/DroidKaigi/conference-app-2024/pull/395#discussion_r1716187285

Yes, that's what I mean. Thanks!

I would like to work on this issue
#464

@iamayushsharmaa Thank you for raising your hand. This issue has already been assigned. However, since there are many screens to fix, if you have a specific screen you'd like to work on, please let me know the name. I think we can collaborate to address this issue.

yeah sure

The contents of FavoritesScreenTest also need to be modified, but we are working on the following PR, so we will check the contents after they are merged and modify them again if there are any shortcomings.
https://github.com/DroidKaigi/conference-app-2024/pull/569

Confirmation of remaining tasks

[ ] AboutScreenTest
[ ] ContributorsScreenTest
[ ] EventMapScreenTest
[ ] FavoritesScreenTest
[ ] ProfileCardScreenTest
[ ] SearchScreenTest
[ ] SponsorsScreenTest
[ ] StaffScreenTest
[ ] TimetableItemDetailScreenTest
[ ] TimetableScreenTest


Kubeflow Notebooks: Cannot select Allow access to Kubeflow Pipelines from Configurations Dropdown

Summary
I want to give my notebook server access to Kubeflow Pipelines. I cannot select it from the dropdown. When I try to connect to the Pipelines API Server, I get status 500 and error message: "Internal error: Unauthenticated: Request header error: there is no user identity header".
Reproduction
in Kubeflow, go to the notebooks webapp and try to check the "Allow access to Kubeflow Pipelines" option in the Configurations Dropdown
Dagit UI/UX Issue Screenshots

Additional Info about Your Environment
Plural managed EKS cluster with Kubeflow

Message from the maintainers:
Impacted by this bug? Give it a 👍. We factor engagement into prioritization.

The PodDefault resources in the user namespaces are missing. That's why it is not possible to select "Allow access to Kubeflow Pipelines"
apiVersion: kubeflow.org/v1alpha1
kind: PodDefault
metadata:
  name: access-ml-pipeline
  namespace: <user-namespace>
spec:
  desc: Allow access to Kubeflow Pipelines
  env:
  - name: KF_PIPELINES_SA_TOKEN_PATH
    value: /var/run/secrets/kubeflow/pipelines/token
  selector:
    matchLabels:
      access-ml-pipeline: "true"
  volumeMounts:
  - mountPath: /var/run/secrets/kubeflow/pipelines
    name: volume-kf-pipeline-token
    readOnly: true
  volumes:
  - name: volume-kf-pipeline-token
    projected:
      sources:
      - serviceAccountToken:
          audience: pipelines.kubeflow.org
          expirationSeconds: 7200
          path: token

i assume 8a758fc670dd2a735007ab175c0e825dd3046921 allows the access token to be mounted, if it was selected?
What would be the right place to add the above PodDefault? It should be available as soon as the namespace is created, correct?


Web editor does not launch, getting black screen.

Godot version
Godot 3.5 RC 2
System information
Windows 11 last updated on 5-25-2022, and Arch Linux updated just a few days ago. Tested on Chrome, and Firefox on both Arch Linux and Windows. Using auto as the webgl renderer. Both my windows machine and my Linux machine are laptops, My windows machine has a 5000 series Ryzen 7 and an RTX 3060. My Linux machine has an intel graphics card and a GeForce GT 525M.
Issue description
I am seeing a black screen on the web editor after I select Start Godot Editor. I tried waiting for 20 minutes after clicking the button, and nothing changed within that time. I have also tried it on multiple computers under both Google Chrome, and Mozilla Firefox.
NOTE: Works in Godot 3.5 RC 1.
NOTE: Disabling Malwarebytes Browser Guard (this is the only browser extension I have) does NOT effect it,  and my Linux machine does not have any browser extensions.
Web Console Output From Windows Machine On Google Chrome:
Godot Engine v3.5.rc2.official.5f9bc7ea5 - https://godotengine.org
godot.tools.js:337 OpenGL ES 3.0 Renderer: WebKit WebGL
godot.tools.js:337 Async. shader compilation: OFF
godot.tools.js:337
godot.tools.js:337 WARNING: Asset Library not available, as it requires SSL to work.
I @ godot.tools.js:337
godot.tools.js:337    at: ProjectManager (editor/project_manager.cpp:2597) - Asset Library not available, as it requires SSL to work.
I @ godot.tools.js:337
08105a12:0x5629b Uncaught (in promise) RuntimeError: null function or function signature mismatch
    at Object::notification(int, bool) (08105a12:0x5629b)
    at Node::propagate_notification(int) (08105a12:0xf9a4f)
    at Node::set_name(String const&) (08105a12:0x430ef)
    at ProjectManager::_notification(int) (08105a12:0x7c76da)
    at ProjectManager::_notificationv(int, bool) (08105a12:0xe37369)
    at Object::notification(int, bool) (08105a12:0x5629b)
    at Control::_size_changed() (08105a12:0xfd263)
    at Control::_notification(int) (08105a12:0x98acbf)
    at Control::_notificationv(int, bool) (08105a12:0x5b170)
    at ProjectManager::_notificationv(int, bool) (08105a12:0xe37362)
36godot.tools.js:337 Output buffer has not enough frames! Skipping output frame.
I @ godot.tools.js:337
V @ godot.tools.js:167
d.port.onmessage @ godot.tools.js:175

NOTE:
I also just want to say that this is my first bug report, so if there is anything that I did wrong, please let me know.
Steps to reproduce
Go to https://editor.godotengine.org/releases/3.5.rc2/, then click Start Godot editor.
Minimal reproduction project
No response

I can confirm this on 3.5.rc2 (Firefox 100, Fedora 36):

Fixed by https://github.com/godotengine/godot/pull/61409.


[Azure.Monitor] Add sovereign support for Query and Ingestion

Fixes https://github.com/Azure/azure-sdk-for-net/issues/32169

Ingestion is still a wip, will be added later

API change check
API changes are not detected in this pull request.

/azp run net - Azure.Monitor.Query - tests-weekly

@nisha-bhatia Reminder to also update the READMEs in this PR

/azp run net - Azure.Monitor.Query - tests-weekly

/azp run net - Azure.Monitor.Query - tests-weekly

/azp run net - Azure.Monitor.Query - tests-weekly

/azp run net - Azure.Monitor.Query - tests-weekly

Closing this PR: sovereign support will be addressed after metricsBatch https://github.com/Azure/azure-sdk-for-net/pull/38640


Automatic Bonus Progression "Allow Property Runes" not actually allowing property runes

As the title suggests, this option:

is not actually allowing property runes to be added to armor (weapons seem to be fine). If I try to add a property rune, it just gets cleared again.
No errors generated in the console.
Pf2e version: 6.0.4
Tested with no modules running.

Just realised I was trying to add the wrong type of rune. Apologies.


java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer SeekBarPreference.onSetInitialValue

Can you please look into this crash? From time to time I see this crash reported, but it's a rare one.
Fatal Exception: java.lang.RuntimeException: Unable to start activity ComponentInfo{.MyActivity}: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2984)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3045)
       at android.app.ActivityThread.-wrap14(ActivityThread.java)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1642)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:154)
       at android.app.ActivityThread.main(ActivityThread.java:6776)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410)
Caused by java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer
       at android.app.SharedPreferencesImpl.getInt(SharedPreferencesImpl.java:242)
       at android.support.v7.preference.Preference.getPersistedInt(Preference.java:1709)
       at net.xpece.android.support.preference.SeekBarPreference.onSetInitialValue(SeekBarPreference.java:274)
       at android.support.v7.preference.Preference.dispatchSetInitialValue(Preference.java:6517)
       at android.support.v7.preference.Preference.onAttachedToHierarchy(Preference.java:1257)
       at android.support.v7.preference.PreferenceGroup.addPreference(PreferenceGroup.java:194)
       at android.support.v7.preference.XpPreferenceInflater.android.support.v7.preference.PreferenceGroup.addItemFromInflater(XpPreferenceInflater.java:4126)
       at android.support.v7.preference.XpPreferenceInflater.rInflate(XpPreferenceInflater.java:293)
       at android.support.v7.preference.XpPreferenceInflater.rInflate(XpPreferenceInflater.java:293)
       at android.support.v7.preference.XpPreferenceInflater.inflate(XpPreferenceInflater.java:103)
       at android.support.v7.preference.PreferenceInflater.inflate$7af30e91(PreferenceInflater.java:112)
       at android.support.v7.preference.XpPreferenceManager.inflateFromResource$6154c3e6(XpPreferenceManager.java:67)
       at .MyFragment.android.support.v7.preference.PreferenceFragmentCompat.addPreferencesFromResource(MyFragment.java:9432)
       at android.support.v7.preference.XpPreferenceFragment.onCreatePreferences(XpPreferenceFragment.java:54)
       at android.support.v7.preference.PreferenceFragmentCompat.onCreate(PreferenceFragmentCompat.java:224)
       at android.support.v4.app.Fragment.performCreate(Fragment.java:2329)
       at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1377)
       at android.support.v4.app.FragmentTransition.addToFirstInLastOut(FragmentTransition.java:1109)
       at android.support.v4.app.FragmentTransition.calculateFragments(FragmentTransition.java:996)
       at android.support.v4.app.FragmentTransition.startTransitions(FragmentTransition.java:99)
       at android.support.v4.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2364)
       at android.support.v4.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManager.java:2322)
       at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2229)
       at android.support.v4.app.FragmentManagerImpl.dispatchStateChange(FragmentManager.java:3221)
       at android.support.v4.app.FragmentManagerImpl.dispatchActivityCreated(FragmentManager.java:3171)
       at android.support.v4.app.FragmentActivity.android.support.v4.app.FragmentController.dispatchActivityCreated(FragmentActivity.java:16192)
       at android.support.v7.app.AppCompatActivity.onStart(AppCompatActivity.java:177)
       at .MyActivity.onStart(MyActivity.java)
       at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1256)
       at android.app.Activity.performStart(Activity.java:6972)
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2937)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3045)
       at android.app.ActivityThread.-wrap14(ActivityThread.java)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1642)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:154)
       at android.app.ActivityThread.main(ActivityThread.java:6776)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410)

Hi, what have you tried so far?

I've checked these but I couldn't find anything.
Since it's crashing at addPreferencesFromResource I think it might be something with the XML?
This is how I use it:
<net.xpece.android.support.preference.SeekBarPreference xmlns:app="http://schemas.android.com/apk/res-auto"
                                                                        android:key="volume"
                                                                        android:title="@string/settings_sound_volume"/>

It's not XML related, it crashes because it's trying to load the value from hard drive and it finds a String instead of the expected integer.
Did you by any chance use the same key "volume" for anything else? Or did you edit shared preferences manually? This is the only thing that comes to my mind...
Unless... "volume" is a very generic name, some library you're using may be writing in your default shared preference file.

Can it be that android:defaultValue is not set in XML?

In that case the default value is 0.

Finally, I managed to catch this live (based on a user report, so I'm still unable to reproduce it locally).
This is extremely weird. I have 5 SeekBarPreference and 1 SeekBarDialogPreference.
In a way, all of these are affected.

2 of them were missing from the prefs, which simply would not be possible, only on a fresh install but the app has been used for almost a year.
3 of them returned ClassCastException  and were stored as String. Seemingly numerical value, but for 1 of these the actual value should be different based on the user settings.
1 of them is Integer, but the value stored is different from what it should be.

This is really weird. I've checked all the relevant code 3 times and I don't put String into these ever (it would also result in a more frequent crash, I guess).
Not sure if this helps.
I think I can add some workaround locally but would be great to get to the bottom of this.

After adding the workaround (basically, I check for these errors and load a default value if there is an issue), it doesn't crash on the user's device anymore.
However, I noticed in the logs that there are errors thrown for MultiSelectListPreference, too. Most probably we haven't seen this yet because the app was crashing prior to loading these preferences.
I have a feeling that this is coming from the similar weird issue with the stored values.
I have 4 MultiSelectListPreference and all 4 throws this error.
This issue doesn't crash the app, though. I think the rest of the preferences should be fine as there is no crash or any other error in the logs.
 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1408)
 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1518)
 	at java.lang.reflect.Method.invoke(Native Method)
 	at android.app.ActivityThread.main(ActivityThread.java:6776)
 	at android.os.Looper.loop(Looper.java:154)
 	at android.os.Handler.dispatchMessage(Handler.java:102)
 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1642)
 	at android.app.ActivityThread.-wrap14(ActivityThread.java)
 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3045)
 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2937)
 	at android.app.Activity.performStart(Activity.java:6973)
 	at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1256)
 	at android.support.v7.app.e.onStart(AppCompatActivity.java:177)
 	at android.support.v4.app.g.onStart(FragmentActivity.java:16192)
 	at android.support.v4.app.l.q(FragmentManager.java:3181)
 	at android.support.v4.app.l.c(FragmentManager.java:3231)
 	at android.support.v4.app.l.k(FragmentManager.java:2239)
 	at android.support.v4.app.l.a(FragmentManager.java:2332)
 	at android.support.v4.app.l.a(FragmentManager.java:2374)
 	at android.support.v4.app.q.a(FragmentTransition.java:115)
 	at android.support.v4.app.q.a(FragmentTransition.java:1070)
 	at android.support.v4.app.q.a(FragmentTransition.java:1187)
 	at android.support.v4.app.l.a(FragmentManager.java:1377)
 	at android.support.v4.app.Fragment.performCreate(Fragment.java:2246)
 	at android.support.v7.preference.f.onCreate(PreferenceFragmentCompat.java:224)
 	at android.support.v7.preference.m.a(XpPreferenceFragment.java:54)
 	at com.myapp.q.b(SettingsFragment.java:)
 	at android.support.v7.preference.q.a(XpPreferenceManager.java:67)
 	at android.support.v7.preference.h.a(PreferenceInflater.java:112)
 	at android.support.v7.preference.p.a(XpPreferenceInflater.java:103)
 	at android.support.v7.preference.p.a(XpPreferenceInflater.java:293)
 	at android.support.v7.preference.p.a(XpPreferenceInflater.java:293)
 	at android.support.v7.preference.p.a(XpPreferenceInflater.java:293)
 	at android.support.v7.preference.p.a(XpPreferenceInflater.java:293)
 	at android.support.v7.preference.p.a(XpPreferenceInflater.java:4126)
 	at android.support.v7.preference.PreferenceGroup.b(PreferenceGroup.java:194)
 	at android.support.v7.preference.Preference.a(Preference.java:1256)
 	at android.support.v7.preference.Preference.a(Preference.java:6516)
 	at net.xpece.android.support.preference.MultiSelectListPreference.a(MultiSelectListPreference.java:195)
 	at android.support.v7.preference.l.b(XpPreferenceCompat.java:90)
 	at net.xpece.android.support.preference.m.a(SharedPreferencesCompat.java:39)
 	at net.xpece.android.support.preference.m.b(SharedPreferencesCompat.java:52)
 	at org.json.JSONArray.(JSONArray.java:108)
 	at org.json.JSONArray.(JSONArray.java:92)
 	at org.json.JSONTokener.nextValue(JSONTokener.java:97)
 	at org.json.JSONTokener.syntaxError(JSONTokener.java:449)
 org.json.JSONException: End of input at character 0 of

Can you say what devices do the crashes come from (model, amdroid version)?

This occurrence was on a Samsung A5 running Android 7.
For the rest, you can find a screenshot attached to a previous comment.

The stacktrace may be useful. What version of the lib were you using? I'll need to match the line numbers. Thanks

1.3.2
For the MultiSelectListPreference that's all I have.

First some background on the last error: I used to store string sets as Strings with JSON arrays on Gingerbread. When reading the preference I tried to read it as Set and if it failed, fall back to parsing String as JSON array and reconstruct the Set from that.
Now, wrong data is stored instead of Set so it mistakenly tries to parse it as JSON array from String. The preference contained an empty string it looks. It shouldn't contain a string at all on Android 7.
A String was also stored in the SeekBarPreference.
I don't see where this comes from.

Does your MultiSelectListPreference has a default value? What is it? Is it an empty string? If so, it should be @null instead or point to an empty string array resource.

Please try and test the current snapshot and let me know if you encounter any errors.
implementation 'com.github.consp1racy:android-support-preference:7d2c9b3fbb'

I'll try the snapshot version, though I can't reproduce these so not sure if I'll notice anything.
I don't set a default value in XML. I set the value runtime and here it can happen that I pass a set like this without any value: Set<String> set = new HashSet<>().

I have the same problem. Firebase Crashlytics

just uninstall your app and then install it. look like you saved string on that key before.
or change the key.


after using enable its shows this error

Name
after using enable
Description:
[16:13:30.582] [Server thread/CRITICAL]: pocketmine\utils\AssumptionFailedError: "Position world is null or has been unloaded" (EXCEPTION) in "pmsrc/src/world/Position" at line 70
--- Stack trace ---
#0 plugins/SkyWars/src/vixikhd/skywars/arena/ArenaScheduler(137): pocketmine\world\Position->getWorld()
#1 plugins/SkyWars/src/vixikhd/skywars/arena/ArenaScheduler(63): vixikhd\skywars\arena\ArenaScheduler->reloadSign()
#2 pmsrc/src/scheduler/TaskHandler(117): vixikhd\skywars\arena\ArenaScheduler->onRun()
#3 pmsrc/src/scheduler/TaskScheduler(141): pocketmine\scheduler\TaskHandler->run()
#4 pmsrc/src/plugin/PluginManager(466): pocketmine\scheduler\TaskScheduler->mainThreadHeartbeat(integer 1)
#5 pmsrc/src/Server(1774): pocketmine\plugin\PluginManager->tickSchedulers(integer 1)
#6 pmsrc/src/Server(1663): pocketmine\Server->tick()
#7 pmsrc/src/Server(1051): pocketmine\Server->tickProcessor()
#8 pmsrc/src/PocketMine(304): pocketmine\Server->__construct(object BaseClassLoader#2, object pocketmine\utils\MainLogger#3, string[37] C:\Users\User\OneDrive\Desktop\Flana, string[45] C:\Users\User\OneDrive\Desktop\Flana\plugins)
#9 pmsrc/src/PocketMine(327): pocketmine\server()
#10 pmsrc(11): require(string[81] phar://C:/Users/User/OneDrive/Desktop/Flana/PocketMine-MP.phar/src/PocketMine.ph)
--- End of exception information ---
[16:13:30.583] [Server thread/EMERGENCY]: An unrecoverable error has occurred and the server has crashed. Creating a crash dump
[16:13:30.622] [Server thread/EMERGENCY]: Please upload the "C:/Users/User/OneDrive/Desktop/Flana/crashdumps/Fri_Mar_4-16.13.30-GMT_2022.log" file to the Crash Archive and submit the link to the Bug Reporting page. Give as much info as you can.
[16:13:30.638] [Server thread/EMERGENCY]: Forcing server shutdown
How to reproduce?

...
...

Server version:

This server is running ... 「...」 implementing API version ... for Minecraft: ... ... (protocol version ...)

Other informations:

did you manage to fix it?

did you manage to fix it?

i will fix it asap

looking forward to seeing it

any updates? im depending on this plugin for my server

this will fix the issue, tho can u implement a join command with random arena select? just like in gamacz's 1vs1 plugin  (which can be found in his repos)


Permissions

Hi, with the new TxAdmin on version 2.0 the persmissions do not take any effect and everyone have "all_permisions" however we set them only few permissions.

You are on a release candidate version.
Please update to v2.0.1.


Internal: update to new jsdom only test syntax

Deploy preview for gestalt ready!
Built with commit 55c98bee60aa24fbd8f0f653b9c6cc0d868aa3cd
https://deploy-preview-232--gestalt.netlify.com

Codecov Report

Merging #232 into master will increase coverage by 1.34%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #232      +/-   ##
==========================================
+ Coverage   63.56%   64.91%   +1.34%
==========================================
  Files          45       45
  Lines         818      818
  Branches      188      188
==========================================
+ Hits          520      531      +11
+ Misses        211      201      -10
+ Partials       87       86       -1

Impacted Files
Coverage Δ

packages/gestalt/src/FlyoutUtils/Caret.js
100% <0%> (+91.66%)
:arrow_up:

Continue to review full report at Codecov.

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


Introduce Storage API

Fixes / Features

Creates Storage CRD that allows attaching existing GCS Bucket to workloads

Testing / Documentation
Tested manually, CI/CD tests in progress

[ y ] Tests pass
[ y/n ] Appropriate changes to documentation are included in the PR

PTAL @sharabiani @44past4


Add relationship documentation (saving and deleting)

Documentation to help new users with relationships; specifically saving and deleting them.
Recently issues were encountered by a new user (me) in #116, these additions are targeted to helping users who are not used to the data adapter "ways". (Inspired by Firebase documentation)

Sweet, thank you!


[NEW-FEATURE] Invokable dialogues from PLC

[ ] Keep dialogues that require interaction in the bottom part of the screen

[ ] Toasts can be invoked from the PLC and it does not require interaction
[ ] Toast must be hidden by a single action when necessary

/cib

Branch 12-_NEW-FEATURE_Invokable_dialogues_from_PLC created!

[ ] we have to consider role of user, when interacting with dialog, if user don't have needed role, offer log in
[ ] test correct synchronization of multiple instances of the same dialog
[ ] differentiate between different instances of dialogs


Font size option

Create $font_sizes and $font_size_custom maps.

I'll check this PR once #35 has been merged.


Clarify fork boundary op pool behavior

Not sure if this has already been discussed, but GET queries to the op pool around the fork boundary return a list of what could be mixed message types, some pre-electra and some post-electra.  It's not clear how this should be handled considering we are adding version: electra to the top-level of the JSON, implying the message should be interpreted as containing electra structs.
In Lighthouse we're opting to convert all messages to their electra version in electra, but this may be unexpected as it is unspecified.

In Teku we went with returning Electra messages only and ignored the other ones.
This behaviour sounds inline with the decision of dropping pre Electra messages once we reach the fork. If we take as example the Attestations, the first block post Electra will contain Electra attestations only and IMO the GET queries should be inline with that. Repackaging non Electra messages to their Electra version might be an easier implementation but didn't look accurate to me.
I'm wondering what would be the use cases and which approach would be the best

We had a quick discussion on the PR that we don't want mixed attestation arrays. I tend to agree that it might be better to just drop them from the response as I would expect the only reason why they are still in the op pool is that it's not worth it to prune it at fork boundry.

switched this to filtering in LH i think that makes more sense, thanks for the feedback guys 🙏


[BuilderTransform] Rework missing buildWithAvailability detection

Since all of the branches of an if statement are joined together and
hence produce the same type, that type should be used to check
whether buildWithAvailability is required but missing regardless of
availability condition kind.
Resolves: https://github.com/apple/swift/issues/63764

@swift-ci please test

@swift-ci please test Linux platform

@swift-ci please test Linux platform


Fix invalid PHP code samples in utests

@see https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/1538

:+1:

:+1:

Thank you @SpacePossum.


Add validation mastheads

Summary
When https://trello.com/c/eB9u3xe7/40 was getting QA'd, it was highlighted that we hadn't added a validation masthead at the top of the page to highlight that something was wrong. This has now been added and retrofitted to some other existing single-question-pages that were missing the same, so that we're more consistent.
Note
Checking with @laurenceberry whether the masthead should be inside the column-two-thirds or outside.
Ticket
https://trello.com/c/eB9u3xe7/40

This looks different from our other banner messages - everywhere else they are full-width I think.

Also, the DUNS number one doesn't work for empty input:

Re: full-width/half-width, see notes on PR. Waiting for Laurence to give feedback on which it should be.
Re: duns number validation on no input - the existing template specifically excluded a masthead in this instance. I didn't override the decision in this case - I just converted it to using the validation macro. I guess we could add a masthead for no input, but it feels like there was a conscious decision to exclude this case... for some reason.
Maybe no good reason. 🤔

I've had a bit of a dig round...  surprisingly, we are slightly inconsistent in whether or not the validation masthead is inside or outside the 2/3 column.  But the vast majority (including the base "service edit" template that is used for all the service submission form pages) have it outside.  It's only a couple of pages in the "return your signed framework agreement" flow that have it inside the 2/3 column.
Outside
https://github.com/alphagov/digitalmarketplace-supplier-frontend/blob/c93cb30c3af6e81929f1581590d373cb89bc3bbd/app/templates/services/_base_edit_section_page.html#L29
https://github.com/alphagov/digitalmarketplace-supplier-frontend/blob/7cce1d5e694fccc46f39bf32a6e19ae390c3b743/app/templates/frameworks/signature_upload.html#L44
https://github.com/alphagov/digitalmarketplace-supplier-frontend/blob/d8e1c22372e17016cf85a0ad9b694b1c546fa8a0/app/templates/frameworks/reuse_declaration.html#L37
https://github.com/alphagov/digitalmarketplace-supplier-frontend/blob/5949fb1e6feefcadb7971b64cb61dc3dbd32d203/app/templates/frameworks/contract_variation.html#L31
https://github.com/alphagov/digitalmarketplace-supplier-frontend/blob/2b4626cb13d4a0e99dab0f26b7aac3b4602782b6/app/templates/frameworks/edit_declaration_section.html#L35
https://github.com/alphagov/digitalmarketplace-supplier-frontend/blob/77919075e66886ba432211c02996aa58091e5a3d/app/templates/frameworks/updates.html#L59
Inside
https://github.com/alphagov/digitalmarketplace-supplier-frontend/blob/7cce1d5e694fccc46f39bf32a6e19ae390c3b743/app/templates/frameworks/signer_details.html#L42
https://github.com/alphagov/digitalmarketplace-supplier-frontend/blob/7cce1d5e694fccc46f39bf32a6e19ae390c3b743/app/templates/frameworks/contract_review.html#L45

I doubt there was a good reason not to include the masthead, it was possibly because we didn't use to use mastheads on single question pages which we've agreed to do from now on.
Either way, mastheads should be full width.

the existing template specifically excluded a masthead in this instance - no, it's the other way round: the template specifically included a masthead in the instance that a duplicate clashing DUNS number had been entered.  The page previously followed our pattern of "no masthead if a single question page", but DUNS number was a "special case" because we wanted to direct people to contact support if their DUNS number was already used, so we added a special banner message for that.
So I think if we're now adding banners for all single-question pages then the empty/invalid DUNS number case should also have one.  But we still need the special messaging for if there's a DUNS number clash.
Here's the PR that added the message:
https://github.com/alphagov/digitalmarketplace-supplier-frontend/pull/186

@TheDoubleK comments addressed, tests updated.


problem with typehub

I was unable to use https://app.typehub.cloud/, firefox developer console reports invalid CORS headers

huh, now it works...
Thank for coming back to me!


Added JSON support

Hi,
If you're still interested in this, I've merged this PR into the well-maintained fork at https://github.com/jaytaylor/gouuid
https://github.com/jaytaylor/gouuid/commit/9e6c9177ecebbbbefa121d96f59bd1c186507949


V4 installation issue.

When i run it i get this:

I am root user and I'm running it as root. sooooooo?????

curl -fsSL https://cdn.coollabs.io/coolify/install.sh | sudo bash


fix(#278): expose the internal logger

Fix #278

looks good!
Currently the build fails, because the APi changes, due to the improved user profile type:
Please copy the file "temp/oidc-client-ts.api.md" to "docs/oidc-client-ts.api.md" and add that file in the MR too....

i still only see one file changed, please re-check commit and avoid stuff like Merge branch in MR. On MR you should operate with git rebase and squash...

nice work, thanks for contributing to this library!


Create Dropbox remote docs

Part of solution for https://github.com/iterative/dvc/issues/1277, aligned with https://github.com/iterative/dvc/pull/4793.

This is awesome @gmrukwa, thanks!!!
It would be great if you can let us know when iterative/dvc/pull/4793 is merged so we can take a final look here and/or take it over 🙂

Hello @shcheklein! I finally had some time to finish the documentation changes we agreed on in https://github.com/iterative/dvc/pull/4793. Thanks for the review in advance!

Hello @shcheklein! I finally had some time to finish the documentation changes we agreed on in https://github.com/iterative/dvc/pull/4793. Thanks for the review in advance!

@jorgeorpinel thanks for the review! 🙂

@jorgeorpinel thanks for the review! 🙂

Thank you @gmrukwa! This LGTM i.e. we can take it over to see if it needs some final copy editing.

Thank you @gmrukwa! This LGTM i.e. we can take it over to see if it needs some final copy editing.

Closing since the core repo one is closed.


horizontal scroll

My hotsite have horizontal scroll.
the animations don't work.

I am also experiencing some horizontal scroll issues with this.
It seems to only really be an issue while the affected elements are off the screen (not yet scrolled into viewport), and I think I've narrowed it down to being an issue only when using *-left animations (zoom-out-left, fade-left, slide-left, etc.), and only if the element it applies to is on the right side of the viewport in a column structure or if it's 100% width (obviously).
A quick fix for this issue is to put overflow: hidden; on either the wrapper class or the body, but I don't think that will be a suitable fix for all scenarios, as some layouts depend on content/elements flowing outside of the wrapper.
I haven't looked at the source to try and pinpoint why this might be happening, but I'm hoping that this information alone might spark some inspiration :)
If I do get time to take a look at the source, I'll post back if I find anything; otherwise, I hope this info helps!


Link Ocean Market’s terms visible at bottom of market.oceanprotocol.com

Consider this a bug because it helps address a major issue: rug pulls.


Add "Elm-game-of-life"

A small project I made when starting to learn Elm.

Thanks! Merged and deployed.

Nice Thanks!


idp-browser.p12 not generated by init-idp.sh

According to documentation on https://hub.docker.com/r/unicon/shibboleth-idp/, the steps for running container are the following:

Generate configuration by running

docker run -it -v $(pwd):/ext-mount --rm unicon/shibboleth-idp init-idp.sh

Create Dockerfile and build customized image with

docker build --tag="<org_id>/shibboleth-idp:<version>" .

Run the customized image with

docker run -e<passwords go here> <org_id>/shibboleth-idp

However, step 3 failed for me with
java.lang.IllegalStateException: no valid keystore

The reason for this is that at step 1 file 'credentials/idp-browser.p12' was not generated.
When I generated this file and manually put it to 'credentials' folder before step 2, docker image started successfully.
I suppose 'idp-browser.p12' should have been generated when running 'init-idp.sh', but silently failed for some reason.
My environment: macOS 10.12, docker 1.13.1
The issue is 100% reproducible, if you need any logs/command outputs please ping me.

Hi @sesm,
Please keep reading down to https://github.com/Unicon/shibboleth-idp-dockerized#browser-based-tls-certificate-and-key
The cert needed here is not one that the IdP install creates for you. You should generate your own key and CSR and combine the key and signed cert (and root/intermediate certs) into a p12 file. This set is used for browser based TLS connections. If you need one for testing, see https://github.com/UniconLabs/dockerized-idp-testbed/tree/master/idp/shibboleth-idp/credentials.

@jtgasper3 thank you for clarification!