[MINGW64] [gettext] ': not a valid identifierline 89: export: `dashless

For some obscure reason, git submodule outputs:
': not a valid identifierline 89: export: `dashless

from the mingw64 shell, but not from the mingw32 and msys shells.
It occurs on all repos, even those without submodules.
which git returns /usr/bin/git on all the 3 shells.
which perl returns /usr/bin/perl on all the 3 shells.
I've been unsuccessful at finding the root cause of this glitch. It's driving me nuts.
EDIT: a workaround for the moment is available in https://github.com/Alexpux/MSYS2-packages/issues/735#issuecomment-264556713.

For me it happens in both MINGW32 and MINGW64 shell.
WORKAROUND: Downgrade git to 2.9.1.

@Alexpux, it turned out #741 doesn't resolve the issue actually - it was a coincident I hadn't mingw-w64-x86_64-gettext/mingw-w64-i686-gettext installed at the time of testing (and the problem seem to come from these two), so despite that added patches didn't seems to do something with the problem itself (at least nnot at the first sight) I thought it was was fixed somehow ;)
So #741 is just an update of the git version.

The problem with removing mingw-w64-x86_64-gettext is breaking a lot of other packages that depend on it, even indirectly eg. mingw-w64-x86_64-gcc or mingw-w64-x86_64-cmake.

Found the culprit: /mingw64/bin/envsubst.exe

@Alexpux please reopen this.

@bit2shift I didn't mean removing of mingw-w64-x86_64-gettext is a solution, it was done so just for illustration purposes ;)

This seems to break(ish) git rebase and rebase interactive.
It seems to work fine at a glance, but I don't know what further implications it has.
For now I work around this issue by reverting to git 2.9.
Here is the output I get:
': not a valid identifierline 96: export: shortrevisions
': not a valid identifierline 96: export: shortonto ': not a valid identifierline 96: export: todocount
': not a valid identifierline 96: export: shortrevisions ': not a valid identifierline 96: export: shortonto
': not a valid identifierline 89: export: new_count

@DragoonX6 did you remove/disable /mingw64/bin/envsubst.exe?

I did not touch it.
$ envsubst -V
envsubst.exe (GNU gettext-runtime) 0.19.7
Copyright (C) 2003-2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Bruno Haible.

@DragoonX6 so you completely disregarded my comment from 6 days ago about /mingw64/bin/envsubst.exe

Oh, my bad, I missed that. Is your shim simply an override added to the path?

It was just to see what arguments were being passed through.
You can instead rename /mingw64/bin/envsubst.exe to something else and then install MSYS2's gettext (pacman -S gettext).
After that, running which envsubst´ should say /usr/bin/envsubst`.

Alright that works as a workaround for now.

@bit2shift Thanks for the workaround. I can confirm that it works. Although I have no idea what it might break.

Any update on this one? Did a pacman -Syu today and the issue is still there, at least on mingw64. I can also confirm the workaround seem to do the trick.

Issue exists still.

Issue exists with mingw32 variant when you install 32-bit version of the MSYS2 toolset as well.
There seems to be several problems lurking in everything right at the moment.  If you do a pacman -Syu, you get zapped by this and more.

I've figured out what's happening, although I don't have a fix yet:
git's shell script library includes gettext.sh and then uses the eval_gettext shell function defined there.
Specifically, git-sh-setup calls $(eval_gettext "usage: \$dashless \$USAGE"). The eval_gettext function evaluates (at /mingw32/bin/gettext.sh:88) this line:
gettext "$1" | (export PATH `envsubst --variables "$1"`; envsubst "$1")

This is the specific line which creates the "export" error you see in the stderr output.
The specific difference between /mingw32/bin/envsubst.exe and /usr/bin/envsubst.exe output is:
$ export ONE=1
$ export TWO=2
$ /mingw32/bin/envsubst.exe -v 'test $ONE $TWO'
ONE
TWO
$ /usr/bin/envsubst.exe -v 'test $ONE $TWO'
ONE
TWO

OK, that all looks OK. But...
$ /usr/bin/envsubst.exe -v 'test $ONE $TWO' | hexdump -C
00000000  4f 4e 45 0a 54 57 4f 0a                           |ONE.TWO.|
00000008
$ /mingw32/bin/envsubst.exe -v 'test $ONE $TWO' | hexdump -C
00000000  4f 4e 45 0d 0a 54 57 4f  0d 0a                    |ONE..TWO..|
0000000a

mingw32's envsubst uses CRLF line endings not LF. The export command in sh can ignore LF in the argument list but fails when it sees CR.
I can think of three possible approaches to fix this:

Make MSYS's sh ignore CRs (either in export commands, or in all input tokens...)
Change the line termination of mingw32's envsubst.exe output.
Make msys32's gettext.sh strip CRs from envsubst output before passing to sh.

I don't know enough about MSYS2 internals to know which of these (if any) is a good idea.

@projectgus great research!
Pinging @mingwandroid.

@projectgus you could've save yourself a considerable amount had you read all the comments and proceeded immediately to test the output of both envsubst.

I did read those, and I ran envsubst a few times  at first with different input. But I couldn't see what the difference between the two envsubst calls was until I worked backwards and found the eval_gettext shell function, which is when the penny dropped.

@mingwandroid If you have any suggestions of where/how to fix this one, I'm happy to try and come up with a PR as well if this is helpful.

bit2shift's workaround left me with a broken git that couldn't clone repositories unfortunately, reporting bad object errors whenever I tried to do so.
A workaround that is working for me, however, is patching gettest.sh to invoke /bin/envsubst instead of envsubst - thanks to SpaceManiac in #rust for the suggestion!

@MaulingMonkey you must be using some weird MSYS2 configuration (eg. modifications to $PATH), because you're the only one with that problem.
Check your $PATH on all 3 MSYS2 consoles (MinGW 32, MinGW 64, MSYS) to make sure both /bin and /usr/bin are present.

@MaulingMonkey also make sure you're not being affected by #30 (hint: rust).

"both /bin and /usr/bin" being present is useless, the two directories are the same (msys's path mapping maps /bin to be equivalent to /usr/bin). Any value of $PATH where /mingw64/bin precedes /usr/bin, as it should, will have the problem where the wrong envsubst is invoked by /mingw64/bin/gettext.sh. The problem has nothing to do with Rust and manifests on any use of git submodules or git stash.

Well, I can't reproduce the problem both of you are having.
It's funny, none of the people who upvoted, and tested my workaround with success, seem to be using rust.
Yet, both of you, @MaulingMonkey and @SpaceManiac, who happen to use rust, are the ones reporting a problem with it.
I'd look into it if I were you.

I ran into trouble before even firing up cargo RE: #30.  That said, it looks like my compounding failures were from trying to use msys's git with a network share CWD, not your workaround - sorry!
$ mkdir /i/temp
$ cd /i/temp
$ git clone https://github.com/octocat/Spoon-Knife.git
Cloning into 'Spoon-Knife'...
remote: Counting objects: 16, done.
remote: Total 16 (delta 0), reused 0 (delta 0), pack-reused 16
error: failed to read delta-pack base object 0350da31ba1fff7f40d7b57a533381722c0                                                                                f9fc7
fatal: unpack-objects failed

$ mkdir /c/temp
$ cd /c/temp
$ git clone https://github.com/octocat/Spoon-Knife.git
Cloning into 'Spoon-Knife'...
remote: Counting objects: 16, done.
remote: Total 16 (delta 0), reused 0 (delta 0), pack-reused 16
Unpacking objects: 100% (16/16), done.

FWIW, I currently use this workaround which works fine for invoking git from the shell: Add to ~/.bashrc :
alias git="PATH=/usr/bin git"

This excludes the MINGW32/64 paths (and everything not in MSYS2 main path) when running git, and so it doesn't end up running a non-MSYS envsubst.
It's possible to use different variants of this hack, and it might not work for shell scripts which do git stuff, but for the shell this is enough.

I can say that the renaming of envsubset.exe and installing gettext solved it for me, i was getting error ': not a valid identifierline 88: export: dashless` every time i ran git stash, and probably saw it other times.

Can I suggest that the change to mingw64/bin/gettext.sh be made the official solution? It's kinda ridiculous that an out-of-the-box installation of MSYS2 64-bit has a problem like this.

Having this issue on git rebase with git version 2.17.0. I do not have this problem on "Git For Windows" version 2.16.0.windows.2. The MinGW environment in Git For Windows is heavily tweaked, so that last fact might not be indicative of anything. Reinstalling gettext did the trick.

Happening on git stash with git 2.17.0.

I am trying to do one of the possible ways suggested to fix the problem.

Change the line termination of mingw32's envsubst.exe output.

git 2.16.2 here
timuy@DESKTOP-QINEVD6 MINGW64 ~/Projects/sgminer-gm
$ git submodule init
': not a valid identifierline 88: export: `dashless
Submodule 'jansson' (https://github.com/akheron/jansson.git) registered for path 'submodules/jansson'

timuy@DESKTOP-QINEVD6 MINGW64 ~/Projects/sgminer-gm
$ git submodule update
': not a valid identifierline 88: export: `dashless
Cloning into '/home/timuy/Projects/sgminer-gm/submodules/jansson'...
': not a valid identifierline 88: export: `sha1
': not a valid identifierline 88: export: `displaypath
Submodule path '': checked out 'bc743ad2d9807b00e7dc0b5d3524d0a47a14f3c3'

@tofutim do you update all packages to latest?

Let me try that, though I found the bashrc trick did solve the problem.

I'm seeing this issue on a 64-bit cygwin installation with stash.
PATH=/usr/bin git stash list completes without warnings,


[folding] retain folded state on copy/paste

VSCode Version:1.7.2
OS Version:WIN 10 14931

It is recommended to support folding of the code snippet also retain its folded format

E.g:
Now copy a piece of code (folding state)

After pasting to another location, it is desirable to maintain its folded state. Of

Rather than paste after the start

I hope my description is accurate

@jrieken

To keep the number of issues in our inbox on a manageable level, we're closing issues that have been on the backlog for a long time but haven't gained traction: We look at the number of votes the issue has received and the number of duplicates issues filed.
If you disagree and feel that this issue is crucial: We're happy to listen and to reconsider.
Maybe you want to give it a try yourself and provide the feature through an extension or a PR: We're happy to give advise and get you started.
Thanks for your understanding. Thanks for helping and happy coding!

I am glad this issue was re-opened, since I would really like to see this feature integrated!
I still don't know, though, how to vote for this issue. Just by placing a "+1"?

@aeschli So how can I upvote? (You write "We look at the number of votes the issue has received...")

To vote, add a :+1: on the description

Ok - thanks!

Hmmm... other, related issues had more votes. Here it is only me now it seems...

+1 for a "Paste Folded"

I need this. 1+

+1 for a "Paste Folded"
I need copy the skeleton of code for better analyse.

Hi guys, I spent several hours to figure out, you may find it helpful, I think this issue can be closed. @nardxxx @haywirephoenix @rowild @aeschli @sbfkcel
Step1: Open your code in vscode
Step2: Cmd + Shift + P (Mac) or Ctrl+Shift+P (Windows) to open Command Palette, search and select Fold All
Step3: Toolbar -> Selection -> Column Selection Mode
Step4: Column select all the code, copy and paste, done!

@huahuayu
Validated is not the same problem as I describe what I hope to solve.
Column selection mode refers to turning a horizontal selection into a vertical selection.
When selecting, if you need to select the complete content of each line, you need to drag the cursor to the end of each line. And if it is in a folded state and copied and pasted, it is not pasting the complete content (that is, not including the folded part of the content, from your GIF demo, the code line number after pasting can also be clearly seen).

@sbfkcel ok then I will withdraw my comment. I only need to keep the function signature, so it's different.

+1 for this feature

1 for this feature.

+1

+1 for an option)

+1 for this feature

+1

It would nice if this worked for Copy line down as well, which I use more often (together with Move line down) in cases where I'm want the copy in the same file. (The advantages being a) you don't have to be as precise in selecting what you want, and b) in Python, where indentation isn't automatically adjusted on paste, I don't end up pasting onto a line where there's already a tab character, thus shifting my first line out of place).
Interestingly, Copy line down and regular copy-pasting have opposite (undesirable) behaviors.
Copy-paste - the original stays folded, the pasted version gets unfolded:

Copy line down - the new copy stays folded, the original gets unfolded:

+1

I upvote.

+1


Optimize the performance of sum by using universal intrinsics

Introduction
Inspired by #2887, we can take advantage of universal intrinsics, Compare with develop branch,  the new implementation has about 13x faster in AVX2, about 4x faster in SSE2, about 6x faster in NEON.
Benchmark
Each test has run for 10 loops and then take the average result, The radio is the MFlops division of Baseline and optimized branch(The bigger the radio is, the better performance is achieved).

X86 BaseLine

data size(10^3)
develop(float)

4000
568.87 MFlops   0.014063 sec

8000
564.95 MFlops   0.028321 sec

X86 loop unrolling

data size(10^3)
develop(float)
ratio

4000
1820.37 MFlops   0.004395 sec
3.19

8000
1883.19 MFlops   0.008496 sec
3.33

X86-SSE2 enabled

data size(10^3)
usimd-sum(float)
ratio

4000
2642.44 MFlops   0.003027 sec
4.64

8000
2642.40 MFlops   0.006055 sec
4.67

X86-AVX2 enabled

data size(10^3)
usimd-sum(float)
ratio

4000
7447.40 MFlops   0.001074 sec
13.09

8000
5649.32 MFlops   0.002832 sec
9.99

ARM BaseLine

data size(10^3)
develop(float)

4000
338.97 MFlops   0.023601 sec

8000
338.20 MFlops   0.047309 sec

ARM loop unrolling

data size
usimd-sum(float)
ratio

4000
1007.34 MFlops   0.007942 sec
2.97

8000
1009.55 MFlops   0.015849 sec
2.98

ARM-Neon enabled

data size
usimd-sum(float)
ratio

4000
2151.17 MFlops   0.003719 sec
6.34

8000
2154.59 MFlops   0.007426 sec
6.37

System Info

Arm
x86

Hardware
KunPeng

Processor
ARMv8 2.6GMHZ 8 processors
Intel(R) Xeon(R) Gold 6161 CPU @ 2.20GHz

OS
Linux ecs-9d50 4.19.36-vhulk1905.1.0.h276.eulerosv2r8.aarch64
Windows Server 2008 R2 Enterprise

Compiler
gcc (GCC) 7.3.0
MSVC14.06

Looks good to me, thanks

Oops - that code is single-precision only, right ? arm/sum.c gets built for both SSUM and DSUM (where the -DDOUBLE automagically changes the FLOAT type to double instead of float)


Home page needs to be more appealing.

The home page needs to be appealing. For this, we can make changes in the background color.
Specially footer and contributor can be user appealing

Could you please assign me this as a GSSOC Contributor.


Hotfix/Transaction middleware

Purpose
If there is an exception thrown, the TokuTransactionMiddleware is not running commands.rollback. If anything is written to the database before an exception is thrown, it is committed to the database.
DRF creates a nice, properly formatted response if there is an exception.  Since the response is not None, the process_exception in the TokuTransactionMiddleware was never being called.
Changes
Checks to see if an exception was thrown(by looking at the status_code).  If it's greater than or equal to 400, the transaction is rolled back.  Otherwise, the transaction is committed.

Need to merge to master.


tests: add can create filter test

Signed-off-by: Meenal Trivedi<EMAIL_ADDRESS>

Hi @Kegsay , I am unable to debug the failure cause, is it due to the line map[string]string rather than map[string]int due to type conversion in python?

Correct, it shouldn't be a string, use int instead.

@Kegsay Done the changes, & woah CI was super fast in this! 🚀


typo in ssl_server2 when verifying certificate

The ssl_server2 sample application has the following comment:
    /*
     * 5. Verify the server certificate
     */

But it is actually verifying the client certificate

ARM Internal Ref: IOTSSL-1400

Fixed in PR #974.


Getting error java.lang.NoSuchMethodError: okhttp3.RequestBody.create(Ljava/lang/String;Lokhttp3/MediaType;)Lokhttp3/RequestBody;

I am using Visual Tracker with Selenium Webdriver Java ( not selenide).
I had to change the port in env since 8080 was already taken by some other process
.env
Frontend
REACT_APP_API_URL=http://localhost:4200
PORT=8686
Backend
JWT_SECRET='jwtPrivateKey'
JWT_LIFE_TIME=1d
IMG_UPLOAD_FOLDER=imageUploads/
BODY_PARSER_JSON_LIMIT="1mb"
APP_PORT=4200
APP_FRONTEND_URL=http://localhost:8080
DB
POSTGRES_PORT=5432
POSTGRES_USER=postgres
POSTGRES_PASSWORD=postgres
POSTGRES_DB=vrt_db
========================================================================
docker-compose looks like
version: "3.7"
services:
ui:
image: visualregressiontracker/ui:2.0.0
ports:
- "${PORT}:8080"
environment:
REACT_APP_API_URL: ${REACT_APP_API_URL}
api:
image: visualregressiontracker/api:2.0.0
environment:
DATABASE_URL: postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@postgres:${POSTGRES_PORT}/${POSTGRES_DB}
JWT_SECRET: ${JWT_SECRET}
JWT_LIFE_TIME: ${JWT_LIFE_TIME}
IMG_UPLOAD_FOLDER: ${IMG_UPLOAD_FOLDER}
APP_FRONTEND_URL: ${APP_FRONTEND_URL}
BODY_PARSER_JSON_LIMIT: ${BODY_PARSER_JSON_LIMIT}
ports:
- "${APP_PORT}:3000"
expose:
- "${APP_PORT}"
volumes:
- ./imageUploads:/${IMG_UPLOAD_FOLDER}
depends_on:
- postgres
postgres:
image: postgres:12
restart: always
environment:
POSTGRES_USER: ${POSTGRES_USER}
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
POSTGRES_DB: ${POSTGRES_DB}
ports:
- "${POSTGRES_PORT}:5432"
expose:
- "${POSTGRES_PORT}"
volumes:
- postgres:/var/lib/postgresql/data
migration:
image: visualregressiontracker/migration:2.0.0
environment:
DATABASE_URL: postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@postgres:${POSTGRES_PORT}/${POSTGRES_DB}
depends_on:
- postgres
volumes:
postgres:
========================================================================
CODE
public class VisualTest {
protected WebDriver driver;
VisualRegressionTracker visualRegressionTracker;
@BeforeSuite
public void bs() throws InterruptedException {

    VisualRegressionTrackerConfig config = new VisualRegressionTrackerConfig(
            "http://localhost:8686", // replace with your data
            "Goole", // replace with your data
            "41d0bcef-f26e-46a8-8d6a-95c0d39dc70a", // replace with your data
            "Main" // replace with your data
    );

    visualRegressionTracker = new VisualRegressionTracker(config);

    WebDriverManager.chromedriver().setup();
    driver= new ChromeDriver();
    driver.get("https://google.com");
    Thread.sleep(3000);
    driver.manage().window().setSize(new Dimension(1200,800));
}
@Test
public void testExample() throws IOException {
    visualRegressionTracker.track(
            "Home page",
            ((TakesScreenshot) driver).getScreenshotAs(OutputType.BASE64),
            TestRunOptions.builder()
                    .diffTollerancePercent(0)
                    .build()
    );
}

@AfterSuite
public void tearDown() {
    driver.close();
}

}
========================================================================
ERROR
java.lang.NoSuchMethodError: okhttp3.RequestBody.create(Ljava/lang/String;Lokhttp3/MediaType;)Lokhttp3/RequestBody;
at io.visual_regression_tracker.sdk_java.VisualRegressionTracker.startBuild(VisualRegressionTracker.java:34)
at io.visual_regression_tracker.sdk_java.VisualRegressionTracker.track(VisualRegressionTracker.java:78)
at com.visualtracker.VisualTest.testExample(VisualTest.java:46)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1257)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at com.intellij.rt.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:66)
at com.intellij.rt.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:110)

hi @sunnysachdeva99!
thanks for detailed report!
here I could see two issues:

as you changed frontend PORT in .env you need to change port as well in backend section that refers to frontend url APP_FRONTEND_URL=http://localhost:8686 but that is not the cause of this error
the exception that you are getting is because some library versions are conflicting, check your dependency tree if there are several versions of okhttp3 and keep only one, or add direct dependency to needed version com.squareup.okhttp3:okhttp:4.8.0

please, let me know if it worked for you

Thanks, @pashidlos for your quick reply.
Found that selenium-java also uses okhttp3 , hence I excluded it and have this in visual-tracker
But now I got below error. I am using webdrivermanager to launch browser. This dependency also uses google gson and I see from your check-in comment that you have removed webdrivermanager "webdrivermanager dependency removed". Is there a problem if I use webdrivermanager ?
com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:226)
at com.google.gson.Gson.fromJson(Gson.java:932)
at com.google.gson.Gson.fromJson(Gson.java:897)
at com.google.gson.Gson.fromJson(Gson.java:846)
at com.google.gson.Gson.fromJson(Gson.java:817)
at io.visual_regression_tracker.sdk_java.VisualRegressionTracker.startBuild(VisualRegressionTracker.java:43)
at io.visual_regression_tracker.sdk_java.VisualRegressionTracker.track(VisualRegressionTracker.java:78)

No, no problem, the reason to remove webdrivermanager was that it's already included in selenide as peer dependency so no need to duplicate it
next error is also seems strange to me, could you check if there any error in docker logs?
also try with example project?

I am getting the same error using the example project. Please see the screenshot

ok, then seems the problem in the backend api
is the frontend working fine? so you are able to login and create new projects?
try going to the url where backend is working http://localhost:4200/api it's a swagger page with all endpoints
find POST /build, auth with apiKey and try sending request with your project name and branch
let me know if you are getting the error response

My updated .env looks like
Frontend
REACT_APP_API_URL=http://localhost:4200
PORT=8686
Backend
JWT_SECRET='jwtPrivateKey'
JWT_LIFE_TIME=1d
IMG_UPLOAD_FOLDER=imageUploads/
BODY_PARSER_JSON_LIMIT="1mb"
APP_PORT=4200
APP_FRONTEND_URL=http://localhost:8686
DB
POSTGRES_PORT=5432
POSTGRES_USER=postgres
POSTGRES_PASSWORD=postgres
POSTGRES_DB=vrt_db
I am able to create projects from front end which is pointing to http://localhost:8686/projects
However, if I open http://localhost:8686/api then I get error " Validation failed (UUID is expected)

use backend port 4200 by default instead of 8686

this should work for you http://localhost:4200/api

curl -X POST "http://localhost:4200/builds" -H "accept: /" -H "apiKey: 41d0bcef-f26e-46a8-8d6a-95c0d39dc70a" -H "Content-Type: application/json" -d "{"branchName":"Main","project":"GoogleTest"}"
Response body
Download
{
"statusCode": 403,
"message": "Forbidden resource",
"error": "Forbidden"
}
Response headers
access-control-allow-origin: *
connection: keep-alive
content-length: 69
content-type: application/json; charset=utf-8
date: Thu, 23 Jul 2020 08:00:28 GMT
etag: W/"45-T7Txzr/IRLfQ4TEPfbVWLpgje4Q"
x-powered-by: Express

set up is fine
the problem is in apiKey it's used to identify specific user
go to User Profile page and you will find one, use it instead of project ID
we gonna fix the text on project page in this task https://github.com/Visual-Regression-Tracker/Visual-Regression-Tracker/issues/52

in Swagger, it worked after changing to Project ID. However, in the code, still the same error.
@pashidlos this project looks very cool. In terms, of testing, let me know if I can contribute

could you double check if apiKey was updated in code of your tests?
on the screen you shared before I see that there is project ID is used
in terms of contribution you are more than welcome here!
before official release I announce pre-release state when you could also participate
I announce them in telegram https://t.me/visual_tracker or in twitter https://twitter.com/VisualReTracker
just in case you want some practice in development, there are some issues marked as good first issue

yes i double checked. with both api, same error

could you upload your code somewhere on github?
together with .env and docker-compose.yml

https://github.com/sunnysachdeva99/Visual_Regression/blob/master/src/test/java/com/practice/AppTest.java

this is what I've changed to make it working, main problem was in apiUrl, it should be link to backend api, change to 4200
let me know your result

you are right , when I changed to backend port, then I am not getting error. However, one question on baseline images.
The way Applitoos or other providers work is when we run the automation for the first time, it uploads the screenshot and considers it as a baseline.
Help me understand how does it work for  Visual-Regression-Tracker ? During its installation, docs mentioned to create imageUploads folder.
Do we need to take screenshot manually and add it in imageUploads folder ?

regarding baseline, right now it's not supported to accept first image as baseline
the thing is that for me make sense to force user visually review image before accepting it as baseline, otherwise it's possible that you keep asserting baseline that might not be as expected (as it was auto accepted)
feel free to submit feature request for that, I'll consider it

image folder
no, it's only to persist the data from container that after they are recreated you don't loos images, add image only via tests

thanks for making project better!


Use TempraryDirectoryChanger for Executer.run()

Description

ForcedCreationDirectoryChanger doesn't clean up after itself. For big runs, this can end up creating a huge amount of data in temporary folders. ARMI will clean up after the run completes, but it's possible that it could fill up the entire hard drive on some systems and cause the run to crash. TemporaryDirectoryChanger cleans up on __exit__(), which will prevent too much temporary directory memory using during a run.
Checklist

[x] This PR has only one purpose or idea.
[ ] Tests have been added/updated to verify that the new/changed code works.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

[x] The release notes (location doc/release/0.X.rst) are up-to-date with any bug fixes or new features.
[x] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in setup.py.

The alternative to this approach is to continue using the ForcedCreationDirectoryChanger and update its __exit__ method to delete the directory in the same fashion that the TemporaryDirectoryChanger does. I initially backed off of this because I didn't want to impact other use cases of ForcedCreationDirectoryChanger. But I am concerned that the naming of the runDir will not be as consistent anymore when using the TemporaryDirectoryChanger. Right now; the naming of the runDir is based on a hash of the caseTitle, so when you run a case multiple times the names of the runDir will be consistent. Using a random  directory might be harder for users to keep track of when debugging.

The alternative to this approach is to continue using the ForcedCreationDirectoryChanger and update its __exit__ method to delete the directory in the same fashion that the TemporaryDirectoryChanger does. I initially backed off of this because I didn't want to impact other use cases of ForcedCreationDirectoryChanger

It sounds like the tradeoff here is having a better named temp dir upon failures versus potentially impacting other users. If you think the better named dir is important we could definitely survey everyone to be sure no one is relying on a workflow that leaves files behind. I think since the temp dir changer has the runDir as root, the random name shouldn't cause too many issues

I agree that it's probably better to use the TemporaryDirectoryChanger here. I think this PR is ready to go, then.


This comes from trying to get decorations @jrieken

I am not seeing this anymore on Linux at least.

@joaomoreno why do you think this is from decorations?

Cause when I repro'd it, it happened on the ignore checker. I also can't repro this any more on my machine, tho.


Kore does not retain https portion of Kodi host address when using SSL

Bug report
Describe the bug
Here is a clear and concise description of what the problem is:

When adding a Kodi host to Kore using an https address it functions normally (ie. https://kodi-host), but when the host entry is edited the https:// portion is dropped from the Address field (ie. kodi-host). I believe this is a minor Kore UI bug.
Expected Behavior
Here is a clear and concise description of what was expected to happen:

Kore should save the https portion of the address with the host record or default to using https if port 443 is entered.
Actual Behavior

Anytime an existing Kodi host entry using https is edited Kore only displays the hostname portion and attempts to connect over http which fails. This then requires https:// to be manually added every time a change is made.
Possible Fix

If port 443 is entered to connect to Kodi, Kore should attempt to use https by default. Or it should retain the https portion of the url if it is used to connect. (Or both)
To Reproduce
Steps to reproduce the behavior:

Under Kodi Settings -> Services -> Control -> Enable SSL (This will require a server.pem and server.key in the userdata dir)
Add the Kodi host in Kore using https://kodi-host for the address field and other required information to add the host
Save and confirm Kore connectivity is working
Edit the host entry in Kore and see that the https portion of the url has been removed
Click Test and Kore will not connect to Kodi because it tries http rather than https

Debuglog

The debuglog can be found here:
I can provide a debug log if needed, but it doesn't seem relevent for this minor bug as this is a Kore UI issue.
Your Environment
Used Operating system:

Mobile device: Pixel 5
Android version: Android 13
Kodi version and platform: Kodi 19.4 on OSMC
Kore version: 3.0.0 F-Droid

note: Once the issue is made we require you to update it with new information or Kodi versions should that be required.
Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.

Fixed #945


Making corrosion go brrrr

Actually before merging this I wanna switch the stress_test example to use the same code as the unit test


cassandra fails on some OpenJDK 13 builds

Again, using my own bleeding edge builds:
$ jdk11/bin/java -version
openjdk version "11.0.4-testing" 2019-07-16
OpenJDK Runtime Environment (fastdebug build 11.0.4-testing+0-builds.shipilev.net-openjdk-jdk11-b140-20190620-jdk-11.0.48)
OpenJDK 64-Bit Server VM (fastdebug build 11.0.4-testing+0-builds.shipilev.net-openjdk-jdk11-b140-20190620-jdk-11.0.48, mixed mode)

$ jdk13/bin/java -version
openjdk version "13-testing" 2019-09-17
OpenJDK Runtime Environment (fastdebug build 13-testing+0-builds.shipilev.net-openjdk-jdk13-b11-20190623-jdk-1326)
OpenJDK 64-Bit Server VM (fastdebug build 13-testing+0-builds.shipilev.net-openjdk-jdk13-b11-20190623-jdk-1326, mixed mode, sharing)

Cassandra fails to run:
$ jdk13/bin/java -jar dacapo-evaluation-git+8b7a2dc.jar -n 5 cassandra
Cassandra starting...
...
Caused by: java.lang.NumberFormatException: For input string: "13-testing+0-builds"
	at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:68)
	at java.base/java.lang.Integer.parseInt(Integer.java:658)
	at java.base/java.lang.Integer.parseInt(Integer.java:776)
	at org.github.jamm.MemoryLayoutSpecification.getEffectiveMemoryLayoutSpecification(MemoryLayoutSpecification.java:190)
	at org.github.jamm.MemoryLayoutSpecification.<clinit>(MemoryLayoutSpecification.java:31)
	... 28 more

This does not look like Dacapo problem, exactly, but the fact that Cassandra relies on https://github.com/jbellis/jamm/, which parses the version string and gets confused because of that. Submitting the issue here for the record.
Amusingly, jdk11 build runs cassandra fine, probably because there is a dot in "11.0.4".

I believe it is fixed with https://github.com/jbellis/jamm/commit/c81473ebf3cf41bcc5e7ebfeb3559bc88249a486, but unable to verify here.


github

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

VS Code Version:
OS Version:

Steps to Reproduce:

/needsMoreInfo

I didn't i was checking want it's features were but mistakenly clicked
something
On Tue, 2 Jul 2024, 12:03 am John Murray, @.***> wrote:

/needsMoreInfo
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/219558#issuecomment-2200776447,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJSIA3LPSMFASF65H5757YDZKGOIBAVCNFSM6AAAAABKFZZZ2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBQG43TMNBUG4
.
You are receiving this because you authored the thread.Message ID:
@.***>


Blog post: designing apps for AiiDAlab, an AiiDA-enabled graphical user interface

Adding a blog post about design principle for developing AiiDAlab apps. Please review the text 🙏 I'll add some figures shortly 🙂

Alternative title:
AiiDAlab: designing graphical user interfaces for AiiDA plugins


What happened to errorProps?

I'm trying to style a specific label that shows up when an error exists, but I no longer see the errorProps property on each field.
How can we do this now?
Thanks

I would recomend creating a custom input. See the example in the docs that does exactly this.


OSError: [Errno 8] Exec format error

I am using the Python Craigslist Headless code on a raspberry pi with a fresh installation of Bullseye.  Prior to using the headless fork, I had been using the Python Craigslist code.  When I try to execute my pre-existing code on the headless code, I receive the following error message.  Any help would be greatly appreciated.  Thanks, Vic
2023-03-23 11:20:08,220 INFO     patching driver executable /root/.local/share/undetected_chromedriver/undetected_chromedriver

2023-03-23 11:20:08,513 CRITICAL Terminating due to unexpected error: <class 'OSError'>

2023-03-23 11:20:08,533 CRITICAL Traceback (most recent call last):

  File "/usr/local/sbin/cl_alert.py", line 307, in main

    cl_ads= CraigslistForSale(site=nationwide[i], category='moa', filters={'query': 'iphone', 'max_price': 150})

  File "/usr/local/sbin/base.py", line 59, in __init__

    self.browser = CraigslistBrowser()

  File "/usr/local/sbin/browser.py", line 20, in __init__

    self.driver = uc.Chrome(options=self._get_options())

  File "/usr/local/lib/python3.9/dist-packages/undetected_chromedriver/__init__.py", line 441, in __init__

    super(Chrome, self).__init__(

  File "/usr/local/lib/python3.9/dist-packages/selenium/webdriver/chrome/webdriver.py", line 80, in __init__

    super().__init__(

  File "/usr/local/lib/python3.9/dist-packages/selenium/webdriver/chromium/webdriver.py", line 101, in __init__

    self.service.start()

  File "/usr/local/lib/python3.9/dist-packages/selenium/webdriver/common/service.py", line 88, in start

    self._start_process(self.path)

  File "/usr/local/lib/python3.9/dist-packages/selenium/webdriver/common/service.py", line 195, in _start_process

    self.process = subprocess.Popen(

  File "/usr/lib/python3.9/subprocess.py", line 951, in __init__

    self._execute_child(args, executable, preexec_fn, close_fds,

  File "/usr/lib/python3.9/subprocess.py", line 1823, in _execute_child

    raise child_exception_type(errno_num, err_msg, err_filename)

OSError: [Errno 8] Exec format error: '/root/.local/share/undetected_chromedriver/undetected_chromedriver'

hey I'm sorry I can't help with your issue, but I just read the other issue where a user introduces the headless fork. Can you confirm that works?

Thanks for the reply.  I will try to contact the author of the headless fork to get resolution.


need troubleshooting guideline for future support

Which document would you like to be mentioned?
Troubleshooting document for user/contribute to check and add support for uncovered environment.
The troubleshooting should provides the checklist with instructions to find a root cause of issue from the log.
This should be also added to GitHub template when creating kind/bug issue.
Why is this needed?
The troubleshooting guideline could help maintainers/contributors to determine root cause.
In addition, it can further help on updating the code to support uncovered environment.
For example,
When cgroups stat is zero, we can follow the below steps after change log level to maximum.
flowchart TD;
   bpfAttached--no-->kernelDependencyCheck
   bpfAttached--yes-->containerIDResolved
   containerIDResolved--no-->pidNamespaceCheck
   containerIDResolved--yes-->cGroupManagerCreated
   cGroupManagerCreated--no-->cGroupPathCheck
   cGroupManagerCreated--yes--> cGroupStatDeletedOnUpdate
   cGroupStatDeletedOnUpdate--yes-->deletedConditionCheck

bpfAttached: check attachment log
kernelDependencyCheck: check permission, check kernel version
containerIDResolved: check "cannot resolve..." and "PID 0..."
pidNamespaceCheck: /proc mount if needed
cGroupManagerCreated: check "could not start cgroup stat handler..."
cGroupPathCheck: check /proc/$(pidof kepler)/cgroup
cGroupStatDeletedOnUpdate: check "Error reading cgroup stats for container"

@sunya-ch looks great! can you add to the trouble shooting section here?

@rootfs Oh I didn't notice that we already have that section. I will make an update on that and also to the GitHub template to link to that page. Thanks.


Run function after everything is done

Hey there!
I'm a bit of a JS noob, and I'm trying to run a function to dynamically adjust the position of any tooltips that might appear off-screen. I'm having trouble figuring out when I can run the function.
This does not seem to work, as the printed offset for all the items is the same (the origin of the containing div).
$.when($("#main-map").interactiveImage(data, {
    shareBox: false,
    debug: false
})).then(function (result) {
    result.find(".item").each(function (item_index) {
        $(this).show();
        console.log($(this).offset());
    });
});

Could I get a pointer in the right direction? :)
Thanks!

Hello @iamjackg,
Sorry for the delay!
I created this code pen to help solving this issue: https://codepen.io/jpchateau/pen/qBZwQqw
First of all, I think I see the correct offset of each item (using FF).
Not sure about that, but you could try something like this in the function you execute for each item:
// Identify the items that are off screen
$('#main-map').off();
// Modify the data array of items with corrected positions
$("#main-map").interactiveImage(items, options);

Actually, it consists of detroying an instance and recreating it.
Tell me if it works!

Hey there!
Thanks for the suggestion. I'll look into it! The main issue I was running into was that I needed to wait while all the initialization happened asynchronously. I solved that by modifying the source to trigger a jQuery event when everything is done.

Thank you for the feedback. I close the issue.


Update flyway-core to 7.7.1

Updates org.flywaydb:flyway-core from 7.5.4 to 7.7.1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.flywaydb", artifactId = "flyway-core" } ]

labels: library-update, semver-minor

Superseded by #112.


Allow to turn off logging for probes to file.

What type of PR is this?
/kind feature

What this PR does / why we need it:
This PR allows us to turn off logging for probes to host path and instead print it to stderr.
Which issue(s) this PR fixes:

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

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/assign @mborsz

As discussed offline, I think that your purpose, disabling the probes completely will work better than adjusting it to your use case (there is no point in maintaining multiple probe configuration, given that you don't need this measurement at all in your use case).

Closing - I think we decided for a different approach.

Closing - I think we decided for a different approach.


Target profile page rewrite: Create basic React app architecture

This is up and running (repo platform-app). @mirandaio has made it available at https://platform-app.netlify.com/.


[Builder] Add index from/to Fixed/UFixed type casting (Fix #241)

Description
This PR introduces expanding support for casting between Index, Fixed, and UFixed types in the Allo IR. This enhancement allows for seamless conversions between these types, which broadens the flexibility of type handling in the IR layer.
Problems
Previously, the Allo IR lacked direct support for conversions between Index and Fixed/UFixed types, limiting the flexibility in scenarios where such conversions are needed for operations. Attempting these conversions required workarounds or was unsupported, creating friction in code requiring dynamic type handling.
Proposed Solutions

Added Index <-> Fixed/UFixed single-step conversions in the cast_map within ASTTransformer.
Implemented new casting operations IntToFixedOp and FixedToIntOp as intermediary conversions to facilitate direct type transformations.
Updated the IndexCastOp to handle Index -> Fixed/UFixed conversions.

Examples
Here’s a snippet of the updated behavior:

Index to Fixed/UFixed Casting:
def kernel(a: index) -> Fixed:
    a_fixed: Fixed = a
    return a_fixed

Fixed/UFixed to Index Casting:
def kernel(a: Fixed) -> index:
    a_idx: index = a
    return a_idx

Both conversions now produce correct IR output without errors, validating the new casting support.
Checklist

[x] PR's title starts with a category (e.g., [IR], [Builder])
[x] Changes are complete (i.e., finished coding on this PR)
[x] All changes have test coverage, with cases for both Index -> Fixed/UFixed and Fixed/UFixed -> Index conversions
[x] Code is well-documented

Thanks, I fixed the init value issue in the test case, and added two test cases for float <-> index casting


Support networkx >=2.6

Currently only networkx 2.5 is supported with this package, but this is a fairly old version of networkx.  I would like to request support of newer versions of this library.

Thanks for filing, @DManowitz! Looks like our original reason for pinning was overly cautious. PR #4035 will fix this.


Converting more forms to the API

Converted

[x] PurchaseOrderCancel
[x] PurchaseOrderComplete
[x] PurchaseOrderIssue
[x] SalesOrderCancel
[x] BuildOrderCancel
[x] StockItemUninstall

Unit Tests

[ ] PurchaseOrderCancel
[ ] PurchaseOrderComplete
[ ] PurchaseOrderIssue
[ ] SalesOrderCancel
[ ] BuildOrderCancel
[ ] StockItemUninstall

Ref: https://github.com/inventree/InvenTree/issues/2253

@SchrodingersGat while total coverage went up, unit coverage is lower now. Maybe we need to add some tests?


[🐞] Signals don't trigger rerender with some problematic JSX markup

Which component is affected?
Qwik Runtime
Describe the bug
I was randomly writing some edge case code (orphaned signals in this case) to see what happens when I first encountered this bug. Trying to reproduce the bug in the playground later revealed that this bug depends on the returned JSX markup.
In the following reproduction, app.tsx exports two components V1 and V2, which have different JSX markup (V1's children are nested in extra p's) but are otherwise the same.
Expected behavior: apart from the visual differences (from not having extra p's), both components should show the same behavior, that is:

clicking on ++ and -- buttons should always increment and decrement the counter (both parent's and child's), and
the counter should reset to zero whenever Child rerendering triggers its useTask$.

Actual behavior: Once V2's Child unmounts for the first time, the parent counter gets stuck and no longer updates. V1 does not show this behavior and works as expected.
Reproduction
https://qwik.builder.io/playground/#v=1.4.2&f=5Va9DoIwEN55ClwICWAENgKdfATD7oA4kGA0xoH03b3eHW1BEkEdSFz4aa%2FXu%2B%2B7PztoklT7Y0dNaNovfmJhY%2BpoeU5cEQ5lDChMhhbtY3mvrnumrjBX%2BzswuBeDijnYGx6zBc%2Ftg0q3LX46NrcKpfqAZmAuBkscckxv78hSuHgLiX%2Bv6BlFUkSRHon4cDeSksuUBoEUQTBUqpJsrom9y6QNHN%2BMlqQ4tHXdVK92j456npsTemBiodySEFHkDlsEsUTJP%2BI5WTXPn7M7ze03zP6YxgUkMneOQxj2%2BNm0dUiBzJA6%2BMw443N%2B0YwnBKiZJHiCWT1yg3IaoM1Zl1Z8uAll8U4NAOtUGyri7HbU8R4j8789KYlT41kZhyoTjTVraU3QBnRnUr%2FJ%2B0b1BA
Steps to reproduce
No response
System Info
System:
    OS: Linux 4.14 Arch Linux ARM
    CPU: (8) arm64 Cortex-A55
    Memory: 860.85 MB / 3.58 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 20.10.0 - /usr/sbin/node
    npm: 10.3.0 - /usr/sbin/npm
  npmPackages:
    @builder.io/qwik: ^1.3.5 => 1.4.2
    @builder.io/qwik-city: ^1.3.5 => 1.4.2
    undici: * => 6.5.0
    vite: ^5.0.11 => 5.0.12

Additional Information
No response

Thank you for the repro, that indeed looks like a bug.

Let me take a look.
It would be great if you could offer a clue that off the top of your head about this bug.

Since we have v2 well underway and it rebuilds some of this code, let's wait until we can test this with v2 alpha.

Also I want to point out another related issue with the example app we get after running pnpm create qwik and choosing the Basic App starter, the counter there is broken and can reproduced quickly by running pnpm preview, hitting the "+" button makes the number drops from 70 to 50

I did a double check with the latest v2 code and it's working fine.
v2 will be release soon so I marked this issue with STATUS-3: solved by V2, thanks.


Add static files or directory inside the dart2native binary.

After I build the binary of dart server using dart2native. I still need those files or directories next or relative to the binary.

I don't think this'll work. The dart2native compiler would need to be updated to do such a thing – and then you'd have to teach dart:io to read from a virtual embedded file system or some such.
You're better just setting up your deployment to include your files!


Different GraphicsMode optimization options

Hi! Thank you for helping out with SSD1306 development! Please:

[ ] Check that you've added documentation to any new methods
[ ] Rebase from master if you're not already up to date
[ ] Add or modify an example if there are changes to the public API
[ ] Add a CHANGELOG.md entry in the Unreleased section under the appropriate heading (Added, Fixed, Changed, etc)
[ ] Run rustfmt on the project with cargo fmt --all - CI will not pass without this step
[ ] Check that your branch is up to date with master and that CI is passing once the PR is opened

PR description
In my use case, I'm using the display on an 8MHz SPI connection, which means a flush is around 1ms. This allows me to switch the partial update to a full update, and basically eliminate tracking of the dirty area.
I still need to benchmark this to see if there is any point in adding the extra complexity, but I wanted to open this draft to hear some of your thoughts on the matter.
By default, the implementation uses the old dirty area tracking method with the partial screen update, so it's hopefully backwards compatible.

Oh, also this is based on #123, hence the duplicate commits.

Just in case, please don't waste time on reviewing the code yet (since this was thrown together extremely quickly and has a ton of potential issues, including the crash of #123), only the general idea :)

A speed bump of around 8% (117813 cycles instead of 128348 while drawing a piece of text) when using FastSetPixel. Tested on a nRF52832 @ 64MHz

Since it's possible to draw to an otherwise unexpected location, I'm thinking about making it possible in FastSetPixel (or a different UncheckedFastSetPixel) to write to an unchecked address. It's already up to the user to draw to the right area, so I think an explicitly unsafe option is not that big deal to add.

Closes #122

I'm done modifying this. There is a single compare that could be optimized away iff it can be ensured that every write is inside the display area, but I don't think it would be worth the extra complexity and the risk.

I like the idea of moving the dirty tracker to a separate struct for cleanliness, as well as the fix for #122, but I'm not sure I see a benefit to making it customisable with another associated type, particularly if we add this one on top of those added in #125. Is 1ms update really too slow for your application?

My benchmark is my original C code that was able to display a realtime sampled signal at 100fps. While I don't expect the same performance, I'm not even close to that with this patch either :) After #125, most of the set_pixel code is the 4 min/max calls, so yeah, I would like to see those go away.

100fps? I take it that's not over 400kHz I2C... It seems dubious at least that the min/max would significantly slow down the drawing.

I'm using 8MHz SPI

I don't know why I didn't think of this, but I could just use a tailor-made graphics mode implementation for my use case...

I'm closing this, if someone wants their GraphicsMode to be faster, they can reimplement it easy enough and that basically makes the added complexity of this PR not worth breaking everybody's code.


CRUD Operations for User Profiles

Description:
Enable Create, Read, Update, Delete (CRUD) operations for user profiles in FusionLMS.
Acceptance Criteria:

Functionality for creating, viewing, updating, and deleting user profiles.
Secure handling of user data.
Ensure that we properly link the profile with the account on the user creation.

ETA: 01.02 (Thu)


Release notes for 0.19

Good point, I'll add those.

Added.

OK, we'll hold this PR open until just before release in case any addition PRs need to be merged.


Can it be trained or fine-tuned on custom datasets?

yes, it can but you may need to build a customized dataset mapper and data register in this folder: https://github.com/UX-Decoder/Segment-Everything-Everywhere-All-At-Once/tree/v1.0/datasets

how to build customized dataset mapper and data register @jwyang
what are the steps to follow ?


WIP [Enhancement] Getting GUI app to run on physical Android device requires changes to setup

Tags

Outline Connectivity Tester GUI app (Android)
Enhancement
WIP

Overview
I have been fiddling wih setup/configuration and exploring different ways to run the app for debug/development on a physical android device.
The current procedure works well with running the app on Emulator but if I run the app on device the front-end cannot reach local vite server to communicate with the backend.
Below I outline two approaches that worked for me. Each approach requires making changes to config files in the project and some manual commands. Perhaps, we can automate this processes or simply include the steps in the README documentation since this is very specific to Android physical device.
Method 1
Step 1: Add --host flag to vite in file mobile_app/package.json such that "watch:frontend": "vite --host",
Step 2:
In capacitor config.ts, change the IP_ADDRESS value with local IP address of the host computer. Please note that it is assumed that the physical android device is connected to the same WiFi network as the development computer.
  case "android":
    config.server =  {
      url: "http://IP_ADDRESS:3000",
      cleartext: true
    };

Please note that when you run vite with --host flag, the backend server will be exposed to the whole network which can be considered a security risk. This should be fine if devices are on an isolated or private network though.
Finally you can use WiFi or USB debugging to run the app on a physical device.
Method 2
This method is more secure than previous one but requires a few more steps. In this approach, all IP addresses in capacitor config.ts must be set to localhost.
import { CapacitorConfig } from '@capacitor/cli';

let config: CapacitorConfig = {
  appId: "org.getoutline.sdk.example.connectivity",
  appName: "@outline_sdk_connectivity_demo/app_mobile",
  webDir: "output/frontend",
  server: {
    url: "http://localhost:3000"
  }
}

switch (process.env.CAPACITOR_PLATFORM) {
  case "android":
    config.server =  {
      url: "http://localhost:3000",
      cleartext: true,
    };
    break;
  case "ios":
  default:
    config.server =  {
      url: "http://localhost:3000"
    };
    break;
}

export default config;

Then, in terminal run:
adb -s DEVICE_NAME reverse tcp:3000 tcp:3000
where DEVICE_NAME is the name of the device returned by adb devices command. You do not need to specify the device name if adb devices only return one result. However if emulator is running in addition to physical device, you get two devices in the result. For examople:
$ adb devices
List of devices attached
adb-2A101FDH200FF3-9WeC8L._adb-tls-connect._tcp device
emulator-5554   device

The command adb reverse tcp:3000 tcp:3000 open a listening socket on the mobile device (localhost:3000) and it passes all traffic to it to the computer on network that is running vite. In this approach --host flag is not needed.
To stop reverse port forwaring, run:
adb -s DEVICE_Name reverse --remove tcp:3000

just an update on this issue: I am going to test the process on iPhone physical device and find a consistent solution for both android and iphone


useful sounds from AKWF

AKWF/AKWF_overtone/AKWF_overtone_0029.wav - voice aah (or AKWF/AKWF_hvoice/AKWF_hvoice_0092.wav)
AKWF/AKWF_hvoice/AKWF_hvoice_0036.wav - voice ooh
AKWF/AKWF_hvoice/AKWF_hvoice_0027.wav another nice choir
AKWF/AKWF_hvoice/AKWF_hvoice_0008.wav ladies choir (needs some transposing trick to be usable)
nice flute AKWF/AKWF_hvoice/AKWF_hvoice_0083.wav
AKWF/AKWF_granular/AKWF_granular_0023.wav synth strings

AKWF/AKWF_0003/AKWF_0249.wav organ'ish sound

AKWF/AKWF_0001/AKWF_0010.wav piano
AKWF/AKWF_0001/AKWF_0023.wav synth string
AKWF/AKWF_0001/AKWF_0032.wav brassy
AKWF/AKWF_0001/AKWF_0037.wav organ
AKWF/AKWF_0001/AKWF_0042.wav basa
AKWF/AKWF_0001/AKWF_0067.wav sqr varhany
AKWF/AKWF_0001/AKWF_0077.wav klarinet
AKWF/AKWF_0001/AKWF_0078.wav syn voice eeee
AKWF/AKWF_0001/AKWF_0083.wav church organ
AKWF/AKWF_0001/AKWF_0084.wav church organ even more so
AKWF/AKWF_0001/AKWF_0091.wav clavinet
AKWF/AKWF_0001/AKWF_0100.wav synth strings

AKWF/AKWF_0002/AKWF_0116.wav - what?
AKWF/AKWF_0002/AKWF_0117.wav bass / flute
AKWF/AKWF_0002/AKWF_0118.wav clarinet / flute / pianoish
AKWF/AKWF_0002/AKWF_0146.wav hybrid

AKWF/AKWF_0002/AKWF_0151.wav varhany
brassy AKWF/AKWF_0002/AKWF_0157.wav
AKWF/AKWF_0002/AKWF_0178.wav trombone?

AKWF/AKWF_0001/AKWF_0088.wav - church organ (muted)
AKWF/AKWF_0002/AKWF_0128.wav - church organ (full)

AKWF/AKWF_cello/AKWF_cello_0001.wav
AKWF/AKWF_violin/AKWF_violin_0007.wav
AKWF/AKWF_0017/AKWF_1603.wav - beefy square
AKWF/AKWF_altosax/AKWF_altosax_0001.wav - guitar? harpsi?
AKWF/AKWF_altosax/AKWF_altosax_0017.wav - guitar?
AKWF/AKWF_birds/AKWF_birds_0004.wav - FM synth
AKWF/AKWF_bw_squ/AKWF_squ_0022.wav - punchy square


interpolation in shorthand properties

theme
export const space = [0.8, 1, 2, 3, 4]
space.xs = space[0] / 2 + 'em'
space.small = space[0] + 'em'
space.medium = space[2] + 'em'
space.large = space[4] + 'em'

Some styled component:
const StyleComp = styled.div`
	margin: 0 0 0 large;
`

Undesired output:
margin: 0.8px 0.8px 0.8px 4em;

Expected output:
margin: 0 0 0 4em;

I do understand the difficulty in this mixed input, where one would want 0 a real value and not place [0] in the theme "space" array. Are you planning to address this?
It's very annoying to specifically write it in 2 lines:
const StyleComp = styled.div`
	margin: 0;
    margin-left: large;
`

The solution is simple, 0 has to be 0 if you want it to be 0:
export const space = [0, 0.8, 1, 2, 3, 4]
space.xs = space[1] / 2 + 'em'
space.small = space[1] + 'em'
space.medium = space[3] + 'em'
space.large = space[5] + 'em'

I found out about this only after months of working with xstyled, and now i have tons of files with zeros, and I cannot simple modify the theme, adding 0 to the beginning of the space array, since tons of files are depended on the current indexes!
This is a huge problem for me now, because this simple yet important thing was not covered in the docs at the time when I first started using xtyled, months ago and now it's all over my workplace's system.
I need to think what to do about it. I have to find every place in the code that uses the words space/small/medium/large and manually see if there are any zeros there as well.
So far I've manually changed every zeros I've found to 0px (though it's not that pretty to look at IMO)

Just look for margin.*(xs|small|medium|large)? Hope it will not be too difficult, maybe we should add something about it in documentation, feel free to add it if you think it could help people!
Happy to see that it helps you!


Accept file with no blank line at the end

Hi, it turns out if the .dokku-monorepo doesn't end up with a blank line, the last line will never be parsed. This PR fixes it.
It also fixes issue https://github.com/iamale/dokku-monorepo/issues/4

Sorry for such a long wait!


Event/polyfill-ie8.js certain event listeners on window in IE8 never fire

Bug
Currently if you use the polyfill service for Events in IE8, and try to add a click handler to the window, it will never fire, because in IE8 click events (and others, listed below) are fired on the document but not window.
Test Case
it('should bubble to window when fired from element', function() {
    var fired = false;
    window.addEventListener('click', function() {
        fired = true;
        // cleanup
        window.removeEventListener(type, listener);
        document.body.removeChild(element);
    });
    var element = document.createElement('div');
    document.body.appendChild(element);
    element.dispatchEvent(new Event('click', { bubbles: true }));
    expect(fired).to.be(true);
}

Fix
Re-target event listeners for events triggered on the window in modern browsers, but document and not window in IE8 to the document when added to the window. Care needs to be taken to ensure that:

The listeners for window fire after document when events bubble up
Stopping propagation on the event from a listener on document properly stops the event from bubbling/triggering on the window
The listeners for window only fire if window is the target, or the event bubbles up.

Discussion
I'm currently working on this in a side-fork because I need it for a project (creating as close to a polyfill as possible for IE8 StorageEvents). I'm happy to upstream the changes if you're interested in a pull request for this issue, but I'm not sure whether the fix is actually worth the added complexity since most of the time developers will add handlers to the document instead of window for these events anyway:

click
dblclick
keypress
keyup
keydown
mousedown
mouseup
mousemove
mouseover
mouseout

storage is broken as-is though as modern browsers only trigger the storage event on window whereas IE8 triggers it on document. Unfortunately, just retargeting the storage event isn't sufficient because the Storage API on IE8 is busted

Wow, nice diagnosis, thanks.  I think you're right, this is a real edge case.  It wouldn't be hard to add a line to addEventListener to bind the listener to document instead of window, but as you say this potentially has unexpected consequences on stopPropagation.
Potentially the best thing to do here is to throw an error to the console if addEventListener is called on window for an element specific event, with a message that links to this issue.  What do you think?

That sounds like a good middle ground.

@tejacques would you consider contributing a PR for this?

Sure -- I'll try to take a stab at it this week.

Hey @triblondon I've got a commit with the behavior we discussed but not sure how best to add a test for it targeting IE8 specifically (or if it makes sense to do so) -- is there a way to do this with the way the tests are set up? I was considering using this technique: http://stackoverflow.com/questions/5574842/best-way-to-check-for-ie-less-than-9-in-javascript-without-library

I'd suggest not restricting it by browser - that's a minefield that we have to tread carefully. Erroring whenever a listener is bound to window for something element specific with advice to bind to document should be fine.  Your change looks good, except I'd add advice to bind to document, and remove the specific reference to IE8 (presumably it also happens in 7 and 6)

Hmm, I was under the impression that the polyfill-ie8.js file was only used for IE8 (or under), but the tests applied to both polyfill.js and polyfill-ie8.js, I didn't want to add a test for this new behavior which wouldn't occur for browsers using the other polyfill file.

Sorry, I totally didn't read your earlier comment properly and eagerly clicked the commit links.  I thought we were talking about the polyfill implementation, not the tests.
Still, I guess the test is a matter of binding to window for one of the affected events, firing it, and then asserting that EITHER it works, or you get the error we've put in the polyfill.

That makes sense, I'll add that in and submit a PR later today.

Hi @tejacques can we finish this off?

Oh wow, I think I just forgot to actually make a PR -- sorry about that. Will re-familiarize myself with this and hopefully get that up today.

This is up in #463


Add skill for recipe unit conversion

Describe the contribution to the taxonomy
When cooking or baking it is often convenient to convert units depending on what measurements you prefer and which measuring tools you have available.
Input given at the prompt
>>> Convert these recipe ingredients from from metric to imperial:\n- 57g butter\n- 28g sugar\n- 453g breadcrumbs

Response that was received
...
1 cup of breadcrumbs is approximately equal to 40 grams, so:
453 grams of breadcrumbs is equal to approximately 11.3 cups of breadcrumbs.

11.3 cups is far too much.
Response that is now received instead
I do not have access to hardware for generating data and training so this commit is untested.
Contribution checklist

[ ] tested contribution with lab generate
[ ] lab generate does not produce any warnings or errors
[x] all commits are signed off (DCO)
[x] the qna.yaml file was linted

Thank you for your contribution to InstructLab! Unfortunately, once a Github repo is made public, all open PRs are automatically closed since they link against a private repo. We have detected that your PR might have been one of the ones affected by this change. If you are still interested in contributing your improvement, please fill out the following short form by no later than May 3rd, and we will get back to you with the additional steps necessary once we have had time to assess the PRs of those still interested:
https://forms.gle/V7SrPPMZDo6iGDYu8


LogScreen - profiles, wrap lines, button groups and toolbar

LogScreen improvements and new features

Added features: filter profiles, toggle wrap lines.
New dialog to select profile.
Previous dialog renamed to Custom: dialog reviewed using button groups
Toolbar revision.

Big improvements for our Log Screen


Fixes for regressions I introduced with the caching stuff

Seems like we should add pertinent unit tests to catch these issues in the future.

https://github.ibm.com/apimesh/gateway-director-test/blob/master/scenario7/test/test.js is the unit test script that caught the regressions (reported in https://github.ibm.com/apimesh/scrum-gateway-director/issues/172).


ARROW-14314: [C++] Sorting dictionary array not implemented

13334

 Quality gate: Passed
 Everything looks good
Details

 Quality gate: Failed
2 Issues

 2 Code issues

Details


duplicate PAGINATION_CHANGED event, updatePagination() => onPaginationChanged() (view settings / viewport resize)

Issue raised here: https://github.com/readium/SDKLauncher-iOS/issues/53
https://github.com/readium/readium-shared-js/blob/develop/js/views/reflowable_view.js#L667
https://github.com/readium/readium-shared-js/blob/develop/js/views/reader_view.js#L729
    function openPage(pageRequest, dir) {

        initViewForItem(pageRequest.spineItem, function(isViewChanged){

            if(!isViewChanged) {
                _currentView.setViewSettings(_viewerSettings);
            }

            _currentView.openPage(pageRequest, dir);
        });
    }

I was about to look into fixing this issue and see it is already in progress. Any idea when the fix will get merged into develop?

Hello @matwood
see the ongoing discussion in the pull request: https://github.com/readium/readium-shared-js/pull/174
This is on the todo list, but there is no ETA I'm afraid (we will revisit this issu at the next dev conference call)

@danielweck When is the conference call? Are others free to join and listen?
I'm free to bug fix, test, and do general code cleanup as needed.

This week's meeting is on Tuesday, 7 July at 1600h UTC
http://www.timeanddate.com/worldclock/fixedtime.html?msg=ReadiumJS+Engineering+Meeting&iso=20150707T16&p1=%3A&ah=1
Telecon:
This meeting is using GoToMeeting
https://global.gotomeeting.com/meeting/join/334772733
Meeting ID: 334-772-733

@rkwright I forgot to ask on this weeks call if the meeting is the same time and meeting ID every week or if there was a mailing list or some other way to keep up to date.

@matwood
It's the same ID/date every week. We have meetings for  JS on Tuesday. SDK/native on Wednesday and a bug triage/other topics on Thursday, all held at the same time of day

Yes, see link here:
http://readium.github.io/meetings.html
Also, strongly urge you to join readium-dev mailing list.  Just send me an email<EMAIL_ADDRESS>or subscribe here:
https://groups.google.com/forum/?fromgroups#!forum/readium-dev

Fixed here:
https://github.com/readium/readium-shared-js/commit/377b3014567cbda4236df1c53734e25cac4111fa
(ensures that only the tail end of a debounced series of event callbacks is consumed)
This fixes some Media Overlays playback issues as well (as the MO engine is very sensitive to onPaginationChanged), such as TOC linking.


feat!: Run plugin on live deploy URL by default

Closes #587
We previous released the ability to run the plugin during the onSuccess build step as experimental/undocumented functionality. We've had good feedback from users and are now ready to roll this out as the default behaviour.
⚠ This PR has breaking changes
The plugin will now run after a deploy has completed auditing the live deploy rather than the statically served build folder. This will:

Allow the plugin to be used on ISR/SSR sites
Speed up "time to deploy" since the plugin run no longer holds up the deploy
Allow the plugin to run in an environment truer to production

The main side effect of this change is that if score thresholds have been configured, the plugin will no longer fail the deploy if those scores are not met.
To continue running the plugin onPostBuild (i.e. before the deploy is complete, using the statically served build folder) and maintain the "fail on thresholds" functionality, set fail_deploy_on_score_thresholds to 'true' in netlify.toml:
[[plugins]]
  package = "@netlify/plugin-lighthouse"

  # Set the plugin to run prior to deploy, failing the build if minimum thresholds aren't set
  [plugins.inputs]
    fail_deploy_on_score_thresholds = "true"

  # Set minimum thresholds for any report area
  [plugins.inputs.thresholds]
    performance = 0.9

If your configuration currently relies on serveDir to ensure the correct page(s) are audited, please note this will have no impact on the new default plugin behaviour. Either continue to run during the onPostBuild stage via the above steps, or amend your path input(s) to ensure the full page route is specified.
For example -
Old configuration relying on serveDir:
[[plugins]]
  package = "@netlify/plugin-lighthouse"

  # Serves the 'pages' directory and audits the file about.html
  # On the live deploy this may correspond to http://1234--yoursite.netlify.app/pages/about
  [[plugins.inputs.audits]]
    serveDir = "pages"
    path = "about.html"

New configuration not relying on serveDir:
[[plugins]]
  package = "@netlify/plugin-lighthouse"

  [[plugins.inputs.audits]]
    path = "pages/about"

Test steps for this PR
Check the new default behaviour
Using a test site,

Install this branch version of the plugin
Make sure you don't have the fail_deploy_on_score_thresholds input set
Deploy your test site
Lighthouse output should appear during the onSuccess step
Lighthouse reports should appear in the UI
Viewing the full lighthouse report should show the deploy URL in the header (not localhost)
Check setting thresholds that your deploy won't achieve. The deploy should complete as normal, but the plugin runs in the deploy summary should note the failing threshold
Check you can still audit multiple pages by specifying them in the netlify.toml and they all run onSuccess

Check the old onPostBuild behaviour
Using a test site

Install this branch version of the plugin
Set the plugin input fail_deploy_on_score_thresholds = "true" as per the instructions above
Deploy your test site
Lighthouse output should appear during the onPostBuild step (and the deploy should take longer while this runs)
Lighthouse reports should appear in the UI
Viewing the full lighthouse report should show localhost in the header (not the deploy URL)
Check setting thresholds that your deploy won't achieve. The deploy should fail as a result of the thresholds
Check you can still audit multiple pages by specifying them in the netlify.toml and they all run onPostBuild

All manual tests/edge cases checked, just putting a pin in this for now so docs has a chance to weigh in 📌

The changes you made to the README look good to me, but I found a few pre-existing things in code blocks that could use further tidying up to align with the other changes you made.

Great call outs - thank you! I've updated those sections now

Great work @aitchiss!


7.5.9 breakes our C5DK Blog package

7.5.9 seem to break our C5DK Blog package when we programmatically create the blog pages. It seem that the https://github.com/concrete5/concrete5/commit/0e5e1553602189bc22d68b14b5122fa8c77bd0e7 commit is the problem.
When we explain our users to setup the blog page default page type, we are making the user create a composer ready content block. We do this to be as standard as possible, and because the administrator then will be able to edit the blog page through composer. This will not work any more!
Is this only for the for the composer content block or is it for all blocks inserted in our blog page default page type?
I have a huge problem about how to overcome this. Do we need to make a special version for 7.5.9?
The error we got is as follows:

This worries me a lot - we are already working hard to find a solution to make our C5DK Blog package work in 8.0.
@aembler  Please advice

This is related to a bug fix for the developer API: when developers create content programmatically using Page::add(), it's a bummer to have the composer content blocks included in the page (and then have to be stripped out.) Instead, you have to opt in to including these composer blocks in the outputted page. You obviously want these blocks, since you're creating an alternate composer interface.
If you change the top section of your method to this
			$blog = $C5dkRoot->add($pt, array(
				'cName'					=> $this->title,
				'cHandle'				=> $this->getUrlSlug($this->title),
				'cDescription'	=> $this->description,
				'cAcquireComposerOutputControls' => true
			));

It fixes the problem.

Thanks a bunch... :-)


Revert " Swift CI: TestProcess.test_passthrough_environment : failed - Test failed: InvalidEnvironmentVariable("swift_xcode")"

Reverts apple/swift-corelibs-foundation#1920

We are seeing failures in CI and PR testing.
00:21:58.445 Test Case 'TestProcess.test_passthrough_environment' started at 2019-02-18 23:40:01.778
00:21:58.445
<EXPR>:0: error: TestProcess.test_passthrough_environment : threw error "The operation could not be completed"
00:21:58.445 Test Case 'TestProcess.test_passthrough_environment' failed (0.054 seconds)

@swift-ci test and merge

@millenomi Just wanted to make sure you are aware that I revert the change.


LRScheduler in Trainer

I just got the following error AttributeError: module 'torch.optim.lr_scheduler' has no attribute 'LRScheduler'
when accessing 'deepinv/deepinv/training/trainer.py' and running 'scheduler: torch.optim.lr_scheduler.LRScheduler = None' line 138, in Trainer
Is "LRScheduler" defined in a specific PyTorch version? I can't find it in some recent versions.

solved by removing LRScheduler:
scheduler: torch.optim.lr_scheduler = None


Reduce amount of Git cloning in CI

Reduce amount of Git cloning in CI, which should be possible with the reduced dependencies of Math and (to a lesser extent) Multiprecision in develop branch.

Fixed by e2c0a372ccba134ec53f07c3ba80d13595ab64ed
If further activities such as Docker image are pursued, these can follow potential tech improvements fom the wide-integer project.


Massive Refactor - Custom Action Feature Types

Is your feature request related to a problem? Please describe.
Only one slider and touchpad are allowed per remote. There are good use cases for multiple touchpads and sliders.
Describe the solution you'd like

All custom actions should get a type field with possible values button, slider, or touchpad. This should allow for the creation of multiple sliders and touchpads.
Deprecated field logic for touchpad and slider fields outside of custom actions, like touchpad style and slider ID.
Add labels and icons to all features.
Remove dependency on all HA custom elements except for ha-icon.
Need to move all internal value logic from slider to base class, like it is in service call tile feature.
Touchpad actions (center, up, down, left, right) would have to be redefined within the touchpad custom action rather than using button actions

Except for default touchpad option which would use button actions.

A configuration UI.

Describe alternatives you've considered
Multiple remote cards in a stack, but this doesn't work for multiple of the same element in a row.
Additional context
I should be able to reuse and unify logic from/with service-call-tile-feature.

Released v4


[ALLUXIO-1748] Fix incompatible type compilation error on Java 8

https://tachyon.atlassian.net/browse/ALLUXIO-1748

Can one of the admins verify this patch?

ok to test

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8731/
Test PASSed.

Merged build finished. Test PASSed.

It will be great if we can get this backported to branch-1.0.

Thanks for the fix! In the future please include a link to the JIRA ticket as the first line of the pull request message - we have a tool which will update automatically update the JIRA ticket if you do this, and the link is convenient for reviewers to get to the ticket.

LGTM

@rnirmal I've backported your fix to branch-1.0

@aaudiber thanks for backporting it. I will include a link to the JIRA ticket for future PR's.


Make kind 1.16 the default

This is mostly a test, probably not the proper way to make this change

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests_istio

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

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests_istio

e2e-simpleTests-distroless_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests-distroless_istio

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

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests_istio

e2e-simpleTests-distroless_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTestsMinProfile_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTestsMinProfile_istio

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

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests_istio

e2e-simpleTests-distroless_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTestsMinProfile_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTestsMinProfile_istio

e2e-dashboard_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-dashboard_istio

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

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests_istio

e2e-simpleTests-distroless_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTestsMinProfile_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTestsMinProfile_istio

e2e-dashboard_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test integ-new-install-k8s-tests_istio

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

Helm at it again :woman_shrugging: need to update to helm to 2.16.0. 2.16.0 doesn't support Job for whatever reason, so we its actually impossible to install Istio with tiller on k8s 1.16 right now. sigh

/retest
I think the metrics issues are legit too, retest  to verify

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests_istio

e2e-simpleTestsMinProfile_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTestsMinProfile_istio

e2e-dashboard_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests-distroless_istio

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

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTestsMinProfile_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTestsMinProfile_istio

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

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-dashboard_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTestsMinProfile_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests_istio

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

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test integ-new-install-k8s-tests_istio

e2e-simpleTests-distroless_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTestsMinProfile_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-dashboard_istio

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

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-distroless_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTestsMinProfile_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test integ-new-install-k8s-tests_istio

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

/retest

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-simpleTests-distroless_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests-distroless_istio

e2e-simpleTestsMinProfile_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTestsMinProfile_istio

e2e-simpleTests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-simpleTests_istio

e2e-dashboard_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test integ-new-install-k8s-tests_istio

lint_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test lint_istio

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

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test integ-new-install-k8s-tests_istio

lint_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test lint_istio

e2e-dashboard_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-dashboard_istio

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

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test lint_istio

e2e-dashboard_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test e2e-dashboard_istio

integ-new-install-k8s-tests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test integ-new-install-k8s-tests_istio

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

confirmed only breakage is grafana now that we updated helm

/retest

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test integ-new-install-k8s-tests_istio

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

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test integ-new-install-k8s-tests_istio

integ-mixer-k8s-tests_istio
a51658bf5c8bc037a981083c3346b2ba89e1075b
link
/test integ-mixer-k8s-tests_istio

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

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pilot-multicluster-e2e_istio
c121dea186d03ae6f14baa1c180727adc4b728b9
link
/test pilot-multicluster-e2e_istio

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

/retest

This change will enable indirectly us to upgrade to kind v0.6.0 which will reduce test flakes (https://github.com/istio/istio/pull/19133)

fixes https://github.com/istio/istio/pull/18820


[ACR] merge feature branch to master.

Merge feature/container-registry-preview branch into master.

@northtyphoon @yugangw-msft merging feature branch into master.


Added stable 2019-10-01 api version.

The signed off PR for this addition can be found here in the private repo: https://github.com/Azure/azure-rest-api-specs-pr/pull/867

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

@sergey-shandar can you lend a hand here getting this approved. We need our management SDK built so we can update CLI and what not to prepare for GA.

Since it's not referenced in the README, nothing for the SDKs is being build, and that's why the Avocado job is failing

@nschonni is that needed for merge? I don't think we did anything like that in the past and we were able to generate sdk for CLI fine.

I added the new api version to the readme. Let me know if there's anything else blocking. Thanks.

@nschonni @sergey-shandar
ping. Please let me know if there is anything blocking the merge of this PR. Thanks.

@nschonni @sergey-shandar ping.
Our team needs this PR to be merged in. It has already been approved in the private repo as mentioned in the description. Please let me know what is blocking this from being merged in thanks.
If it is because the Avocado thing is failing please let me know. Sometimes builds block PRs sometimes they don't. Thinks.

Sorry, I can't merge anything, just was pointing out how to fix (part) of the build failure. I think the remaining build failures are from example files that are not referenced from the spec file in this version

@nschonni
Sorry about. Thought you were reviewing this for merge :). Thanks though, I got the avocado build working, turned out to be a flub in the readme and a few missing example links.
@sergey-shandar are you able to merge this?


add buy sell widget and fix react bootstrap problem

Closes #14.
We implement the frontend of the buy and sell functionality here.
We're using react-bootstrap instead of conventional bootstrap - I find it a lot easier.

This is ready for review! Done implementing the feature.


Promote supported K8s versions to 1.23 - 1.25

Promote supported K8s versions to 1.23 - 1.25
/fixes https://github.com/fybrik/fybrik/issues/1900
Signed-off-by: Alexey Roytman<EMAIL_ADDRESS>

Helm 3.10 instead of 1.10

done


js error when loading cached imports

In version 1.2.1 of less, an error occurs when loading imported stylesheets and they are cached.
On line 3083, the following call:
callback(null, sheet, { local: true, remaining: remaining });
uses the wrong arguments for the callback function, which expects the arguments e, root, _, sheet, env (anonymous function defined on lines 3018 - 3028. This function checks:
    if (env.local) {
        log("loading " + sheet.href + " from cache.");

since env is undefined, the js interpreter throws an error. It doesn't seem to be problematic for the rest of the script, but it's rather annoying to have firebug throw an error each time this happens.
A fix is to change 3083 to:
callback(null, null, data, sheet, { local: true, remaining: remaining });

Confirmed:
Uncaught TypeError: Cannot read property 'local' of undefined

I also noticed that this problem does NOT happen on the Rekonq browser, version <IP_ADDRESS> (libqtwebkit4 2.2). It happens on some major browsers, though; Chromium 16, Internet Explorer 7 and Firefox 10 have presented the same behavior.

As a second note, this issue was only noticed when deployed to a production server; everything works flawlessly in a local dev server (Django's default, in my case).


Its not letting me install @mui/icons-material with yarn not npm

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example:
Steps:

cloned my repo installed every package except @mui/icons-material
Tried to install it independently yarn add @mui/icons-material
Tried with npm

Current behavior 😯
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error An unexpected error occurred<EMAIL_ADDRESS>ESOCKETTIMEDOUT".
info If you think this is a bug, please open a bug report with the information provided in "C:\\Users\\mattj\\ucla\\articles-fronend\\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

log:
Trace:
  Error<EMAIL_ADDRESS>ESOCKETTIMEDOUT
      at ClientRequest.<anonymous> (C:\Users\mattj\AppData\Roaming\nvm\v18.12.1\node_modules\yarn\lib\cli.js:141517:19)
      at Object.onceWrapper (node:events:627:28)
      at ClientRequest.emit (node:events:513:28)
      at TLSSocket.emitRequestTimeout (node:_http_client:838:9)
      at Object.onceWrapper (node:events:627:28)
      at TLSSocket.emit (node:events:525:35)
      at Socket._onTimeout (node:net:562:8)
      at listOnTimeout (node:internal/timers:564:17)
      at process.processTimers (node:internal/timers:507:7)

Expected behavior 🤔
for it to install flawlessly
Context 🔦
Please help, I have a few days to submit my project!
This repo used to work flawless on my windows 7 pc and I deployed it to netlify about a month ago. Now its not working on my windows 11 laptop that recently bought.
Your environment 🌎

npx @mui/envinfo
  System:
    OS: Windows 10 10.0.22621
  Binaries:
    Node: 18.12.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
    npm: 8.19.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.22621.819.0), Chromium (108.0.1462.54)
  npmPackages:
    @emotion/react: ^11.9.0 => 11.10.5
    @emotion/styled: ^11.8.1 => 11.10.5
    @mui/base:  5.0.0-alpha.110
    @mui/core-downloads-tracker:  5.11.0
    @mui/material: ^5.11.0 => 5.11.0
    @mui/private-theming:  5.11.0
    @mui/styled-engine:  5.11.0
    @mui/system:  5.11.0
    @mui/types:  7.2.3
    @mui/utils:  5.11.0
    @types/react: ^17.0.43 => 17.0.52
    react: ^18.0.0 => 18.2.0
    react-dom: ^18.0.0 => 18.2.0
    typescript: ^4.4.2 => 4.9.4

It let me install it with bash any thoughts on why that is?

Sounds like a duplicate of https://github.com/mui/material-ui/issues/34874 See the related discussions on the linked issues. Happy to see it was resolved tough.


Factor DB weights out into their own files

Preparation for #10897:

Put the RocksDB and ParityDB weights into their own files.

This will come in handy when switching to auto-generated files.

bot merge


Update from bump-version

This is an automated pull request to update from branch bump-version

📝Changed routes:

/faq

(view full size)

Commit fd32b1b644abce204fa1a3529101751b7359b042 (https://bckstudio-on-zeitnow-bpam0uabu.vercel.app).

📝Changed routes:

/faq

(view full size)

Commit fd32b1b644abce204fa1a3529101751b7359b042 (https://bckstudio-on-zeitnow-bpam0uabu.vercel.app).


Deployment does not have minimum availability

Pods "homepage-77cdf87bbc-" is forbidden: error looking up service account default/homepage: serviceaccount "homepage" not found:Deployment does not have minimum availability.

kubectl create serviceaccount homepage
serviceaccount/homepage created
Fix this bug

I also found this bug on a fresh deploy. Simply creating the SA fixed it like @xinmans said.

Since it seems like a misconfiguration, I'm closing this.


Use selected entities for filtering with configurable behavior

User story
Rather than separate notions of selected entities and filtered entities, we should derive filtering from selections for less confusion.
Preferred solution

Add a coordination type for setting the behavior for each selection coordination type

obsSetSelection -> obsSetSelectionMode: "select", "filter"
featureSelection -> featureSelectionMode: "select", "filter"

Deprecate/remove current filtering-related coordination types

Possible alternatives
Use case

[ ] Relevant to HuBMAP Consortium
[ ] Relevant to Kidney Precision Medicine Project
[ ] Relevant to Human Tumor Atlas Network
[ ] Other

Related to #1457