Excessive intermediate name elision

What's up?
I'm writing this issue following these comments:

"we should ... try and produce legible SQL",
"the examples ... are the biggest selling point for PRQL, in particular the SQL it generates. It looks clean, straightforward, something I would've written myself",

and also because fixing this might be helpful for those who would try to debug other aspects of SQL generator.

Using example from #3170
group {
	...,
	heappages = relpages,
	toastpages = relpages ?? 0,
	toasttuples = reltuples ?? 0,
	...,
} (
	aggregate {
		tpl_hdr_size = 123 + (count attname),
		tpl_data_size = (sum whatever),
	}
)

yields:
WITH table_1 AS (
  SELECT
    ...,
    COALESCE(reltuples, 0) AS _expr_0,
    relpages AS _expr_1,
    COALESCE(relpages, 0) AS _expr_2,
    123 + COUNT(*) AS _expr_3,
    COALESCE(SUM(whatever), 0) AS _expr_4
  FROM
    ...
),

which is then followed by all sorts of _expr_3 + _expr_4 + CASE WHEN _expr_5 = 0 THEN, which is hard to read, let alone debug.

Initially I thought this might be relevant to name shadowing (foo = foo + ...), but, in most cases I've seen so far, it isn't.
Here's what I was able to reduce that example to:

exhibit A
from t
derive {
  b = case {
    a == 1 => 123,
  },
  c = case {
    a == 0 => 0,
    true => b - a,
  },
}
select {
  c
}

Generated SQL:
WITH table_0 AS (
  SELECT
    a,
    CASE
      WHEN a = 1 THEN 123
      ELSE NULL
    END AS _expr_0
  FROM
    t
)
SELECT
  CASE
    WHEN a = 0 THEN 0
    ELSE _expr_0 - a
  END AS c
FROM
  table_0

-- Generated by PRQL compiler version:0.9.2 (https://prql-lang.org)

Expected SQL:
WITH table_0 AS (
  SELECT
    a,
    CASE
      WHEN a = 1 THEN 123
      ELSE NULL
    END AS b
  FROM
    t
)
SELECT
  CASE
    WHEN a = 0 THEN 0
    ELSE b - a
  END AS c
FROM
  table_0

exhibit B
from t
group {
  a = w,
  b = x ?? 0,
} (
  aggregate {
    c = (count y),
    d = (sum z),
  }
)
select {
  a + b,
  c + d,
}

Generated SQL:
WITH table_0 AS (
  SELECT
    COUNT(*) AS _expr_0,
    COALESCE(SUM(z), 0) AS _expr_1,
    w AS _expr_2,
    COALESCE(x, 0) AS _expr_3
  FROM
    t
  GROUP BY
    w,
    COALESCE(x, 0)
)
SELECT
  _expr_2 + _expr_3,
  _expr_0 + _expr_1
FROM
  table_0

-- Generated by PRQL compiler version:0.9.2 (https://prql-lang.org)

Expected SQL:
WITH table_0 AS (
  SELECT
    COUNT(*) AS c,
    COALESCE(SUM(z), 0) AS d,
    w AS a,
    COALESCE(x, 0) AS b
  FROM
    t
  GROUP BY
    w,
    COALESCE(x, 0)
)
SELECT
  a + b,
  c + d
FROM
  table_0

With trivial changes to the last example, names are not elided:
select {
  a, b,
  c + d,
}

...
  SELECT
    w AS a,
    COALESCE(x, 0) AS b,
...
SELECT
  a,
  b,
  _expr_0 + _expr_1
FROM
  table_0

Same goes for c + d → c, d.

Yes, I think this is valid, and we should keep this open — it would be a nicer result if b were used instead of _expr_0. And it's a very well-written issue — Exhibit A seems very sufficient.
But my guess is that as queries become more complicated, the exact relationship between variables in PRQL & SQL become more difficult to track, and so using names across them consistently becomes less reliable. That's ironically more the case if we become better at https://github.com/PRQL/prql/issues/3170.
And because it's difficult to measure whether we're doing this "correctly", I would worry that work here wouldn't compound / might get removed to make way for functional improvements.
As ever, open to ideas / opinions. and if anyone wants to have a go at improving this, that'd def be an improvement...

But my guess is that as queries become more complicated, the exact relationship between variables in PRQL & SQL become more difficult to track, and so using names across them consistently becomes less reliable. That's ironically more the case if we become better at https://github.com/PRQL/prql/issues/3170.

My initial impression is that #3170, if implemented through CTEs or nested select, shouldn't affect this issue most of the time (in fact, examples above are already generating CTEs, and even if they didn't, into tmp/from tmp hack would quickly make a test case for future versions where #3170 is not an issue).
Shadowing though is problematic, as it definitely requires name mangling of some sort (although it still might be improved by generating something like _foo_1 for foo = f(foo) instead of _expr_7). But even then #3170 might actually come handy, 'cause it makes possible to use CTE boundaries for name shadowing on SQL level, like:
WITH ...,
table_1 AS (
  SELECT
    something(complicated + foo) as foo,
    ...
)
...

That definitely would not be possible in all cases though. Also I'm not sure whether f(foo) as foo is more readable than f(_foo_1) as foo: former would be closer to the PRQL source, while the latter would make it easier to navigate generated source code and figure out where one particular _foo_N comes from.


refactor(swap): support quoting for natively multichain asset

PR mainly addresses an issue of structuring the quote when natively multichain asset is involved.

:tada: This PR is included in version 1.14.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


RequestLogger doesnt log requests in chrome:headless mode

What is your Test Scenario?
I have a test where I expect certain requests to be made by my webapp on certain actions.
What is the Current behavior?
The RequestLogger is able to capture and log requests in regular 'chrome' mode but doesnt seem to be working in headless mode.
What is the Expected behavior?
RequestLogger should work in irrespective of headless mode or not.
Steps to Reproduce:

Set up RequestLogger to capture requests to a given url
Take some actions on your webapp which triggers requests to the above url.
Print captured results
Works in regular mode but is empty in chrome:headless mode.

Your Environment details:

testcafe version:                   1.4.1
node.js version:                    v12.7.0
command-line arguments:  testcafe chrome:headless ./test/integration/
browser name and version: Chrome 76.0.3809.100
platform and version:          macOS 10.14.5

@noamaankhan
Hello,
I checked my base "RequestLogger" scenario and everything works properly. Could you please provide your test code to reproduce the issue?

@Farfurix
Hi,
Thank you for responding promptly. Thanks to the screenshot-on-failure cmdline option, I was able to figure out the issue. Some elements were overlapping with each other because of which the button that was supposed to trigger few expected calls wasnt getting clicked. I was able to resize the window and fix the issue.


Hunk #1 FAILED at 153. 1 out of 1 hunk FAILED -- saving rejects to file drivers/media/usb/uvc/uvcvideo.h.rej

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D435i

Operating System & Version
Ubuntu 16.04

Kernel Version (Linux Only)
4.15.0-128-generic

Platform
PC

SDK Version
2.41.0

Issue Description
<初始化空的 Git 仓库于 /home/jindan/librealsense/ubuntu-xenial-hwe/.git/
Fetching Ubuntu LTS tag Ubuntu-hwe-4.15.0-128.131_16.04.1  to the local kernel sources folder
remote: Counting objects: 5930029, done.
remote: Compressing objects: 100% (867979/867979), done.
remote: Total 5930029 (delta 5025768), reused 5919832 (delta 5018658)
接收对象中: 100% (5930029/5930029), 1.26 GiB | 386.00 KiB/s, 完成.
处理 delta 中: 100% (5025768/5025768), 完成.
来自 git://kernel.ubuntu.com/ubuntu/ubuntu-xenial

[新标签]          Ubuntu-hwe-4.15.0-128.131_16.04.1 -> Ubuntu-hwe-4.15.0-128.131_16.04.1
Switching to LTS tag Ubuntu-hwe-4.15.0-128.131_16.04.1
正在检出文件: 100% (63727/63727), 完成.
Note: checking out 'Ubuntu-hwe-4.15.0-128.131_16.04.1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b
HEAD 目前位于 2c5bb3a... UBUNTU: Ubuntu-hwe-4.15.0-128.131~16.04.1
Applying patches for xenial-hwe line
Applying realsense-uvc patch
patching file drivers/media/usb/uvc/Makefile
patching file drivers/media/usb/uvc/uvc_driver.c
Hunk #1 succeeded at 208 with fuzz 2 (offset 5 lines).
patching file drivers/media/usb/uvc/uvcvideo.h
Hunk #1 FAILED at 153.
1 out of 1 hunk FAILED -- saving rejects to file drivers/media/usb/uvc/uvcvideo.h.rej
patching file drivers/media/v4l2-core/v4l2-ioctl.c
Hunk #1 succeeded at 1248 (offset 2 lines).
patching file include/uapi/linux/videodev2.h
Hunk #1 succeeded at 680 (offset 12 lines).>
I've been puzzling this problem for a long time. I hope I can get help！

Hi @jindanChina   Another RealSense user experienced this same set of errors and offered advice for how to correct it in the link below.
https://github.com/IntelRealSense/librealsense/issues/7863#issuecomment-736776850

Hi @jindanChina   Another RealSense user experienced this same set of errors and offered advice for how to correct it in the link below.
https://github.com/IntelRealSense/librealsense/issues/7863#issuecomment-736776850

@MartyG-RealSense Thank you very much, the above problem has been solved very well. But I encountered some other problems, I am trying to update the firmware of 435i to see if it can be solved, thank you again for your answers.

@MartyG-RealSense Thank you very much, the above problem has been solved very well. But I encountered some other problems, I am trying to update the firmware of 435i to see if it can be solved, thank you again for your answers.

@MartyG-RealSense After updating the firmware, many problems were solved, but another problem still exists. Can you help me solve it?
05/01 11:11:44,943 WARNING [140610460559104] (sensor.cpp:1086) RGB Camera: skipping Backlight Compensation control. descriptor: [min/max/step/default]= [0/0/0/0]
05/01 11:11:44,943 WARNING [140610460559104] (sensor.cpp:1086) RGB Camera: skipping Exposure control. descriptor: [min/max/step/default]= [0/0/0/0]
05/01 11:11:44,944 ERROR [140610460559104] (types.h:313) xioctl(VIDIOC_G_CTRL) failed Last Error: Invalid argument
05/01 11:11:44,944 WARNING [140610460559104] (sensor.cpp:1110) Failed to add Enable Auto Exposure control for RGB Camera
05/01 11:11:55,198 WARNING [140610635167552] (ds5-motion.cpp:477) IMU Calibration is not available, default intrinsic and extrinsic will be used.

@MartyG-RealSense After updating the firmware, many problems were solved, but another problem still exists. Can you help me solve it?
05/01 11:11:44,943 WARNING [140610460559104] (sensor.cpp:1086) RGB Camera: skipping Backlight Compensation control. descriptor: [min/max/step/default]= [0/0/0/0]
05/01 11:11:44,943 WARNING [140610460559104] (sensor.cpp:1086) RGB Camera: skipping Exposure control. descriptor: [min/max/step/default]= [0/0/0/0]
05/01 11:11:44,944 ERROR [140610460559104] (types.h:313) xioctl(VIDIOC_G_CTRL) failed Last Error: Invalid argument
05/01 11:11:44,944 WARNING [140610460559104] (sensor.cpp:1110) Failed to add Enable Auto Exposure control for RGB Camera
05/01 11:11:55,198 WARNING [140610635167552] (ds5-motion.cpp:477) IMU Calibration is not available, default intrinsic and extrinsic will be used.

Hi @jindanChina   I suspect from those new error messages that there are still problems with the kernel patching.  A way to confirm this would be to build libralsense with CMake using the RSUSB installation method.  It requires an internet connection but is not dependent on Linux versions or kernel versions and does not require patching.
Instructions for the RSUSB installation method can be found in the link below.
https://github.com/IntelRealSense/librealsense/issues/6964#issuecomment-665650908
I would recommend leaving out the term -DBUILD_WITH_CUDA:bool=true from the CMake build instruction in the above link, as you may not have an Nvidia GPU graphics chip in your computer.

Hi @jindanChina   I suspect from those new error messages that there are still problems with the kernel patching.  A way to confirm this would be to build libralsense with CMake using the RSUSB installation method.  It requires an internet connection but is not dependent on Linux versions or kernel versions and does not require patching.
Instructions for the RSUSB installation method can be found in the link below.
https://github.com/IntelRealSense/librealsense/issues/6964#issuecomment-665650908
I would recommend leaving out the term -DBUILD_WITH_CUDA:bool=true from the CMake build instruction in the above link, as you may not have an Nvidia GPU graphics chip in your computer.

@jindanChina hello,  instead of running the scripts manually you can use DKMS Debian:
https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md#linux-distribution
sudo apt install librealsense2-dkms

As for the manual patch  - it will be handled and update accordingly.

@jindanChina hello,  instead of running the scripts manually you can use DKMS Debian:
https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md#linux-distribution
sudo apt install librealsense2-dkms

As for the manual patch  - it will be handled and update accordingly.

@ev-mp @MartyG-RealSense Thank you, I will try your suggestions, you are really enthusiastic, thank you!

@ev-mp @MartyG-RealSense Thank you, I will try your suggestions, you are really enthusiastic, thank you!

Hi @jindanChina   Do you require further assistance with this case, please?   Thanks!

Hi @jindanChina   Do you require further assistance with this case, please?   Thanks!

Case closed due to no further comments received.

Case closed due to no further comments received.


[VS Code] Could not load file or assembly 'System.Runtime.Serialization, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The system cannot find the file specified.

Error:
Could not load file or assembly 'System.Runtime.Serialization, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The system cannot find the file specified.
Steps to Reproduce:
1.
2.

Version Data

extensionName
VSLS

extensionVersion
1.0.379

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.35.0

platformName
MacOS

platformVersion
18.6.0

@CampaignPortalIT we have seen occasional issues like this before, caused by installation problems. Can you try to uninstall the Live Share extension and install it again?

Closing due to inactivity. Please re-open if this you're still encountering the issue and can share more details. Thanks!


vela up -f https://raw.githubusercontent.com/oam-dev/kubevela/master/docs/examples/vela.yaml

Parsing vela appfile ...
Error: Get "https://raw.githubusercontent.com/oam-dev/kubevela/master/docs/examples/vela.yaml": dial tcp <IP_ADDRESS>:443: connect: connection refused

can you try
curl https://raw.githubusercontent.com/oam-dev/kubevela/master/docs/examples/vela.yaml

Make sure you're not blocked by GFW

can you try
curl https://raw.githubusercontent.com/oam-dev/kubevela/master/docs/examples/vela.yaml

Make sure you're not blocked by GFW

你能试一下吗
curl https://raw.githubusercontent.com/oam-dev/kubevela/master/docs/examples/vela.yaml

确保您没有被GFW阻止

curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection refused

你能试一下吗
curl https://raw.githubusercontent.com/oam-dev/kubevela/master/docs/examples/vela.yaml

确保您没有被GFW阻止

curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection refused

I can't reproduce it, closing, feel free to reopen if it's still happening.

I can't reproduce it, closing, feel free to reopen if it's still happening.


Typo in readme

Hi
You have typo in readme in "ource install/local_setup.sh", line 37 :smiley:

@Skwarson96 oh, didn't notice this ;)


Connection pool graph not working on JBOSS

Hello everyone
I had configured an agent to monitor a application running on a JBOSS, the agent worked but the connection pool graph is not working... as the screenshot below:

is there anything extra that I need to configure for this metric to appear in graphics?
thanks everyone.

https://github.com/pinpoint-apm/pinpoint#supported-modules
Please check out supported modules

Well... question answered.
Thanks.


Mini cart display error on single page, single post, archives, etc.

First, I would like to say thanks for this awesome theme - great work!
However, my mini cart has an error and I can't figure out why. On each WooCommerce page and WooCommerce category, everything is fine. On single pages, posts, archives, etc. (basically, everything that is NOT WooCommerce) the mini cart layout is broken. See here for example: https://kuestenvibes.de/datenschutz/ (add something to the cart first: https://kuestenvibes.de/shop/)
Apparently, it's not a plugin issue as I already tried to deactivate all plugins. At this point, I don't know where the error could come from so I do appreciate every help.

Thank you!
A CSS markup is missing:
img {
  max-width: 100%;
  height: auto;
}

Add this to _bscore_custom.scss and mini-cart image looks well everywhere.
I see that you enabled WooCommerce in main-theme and change code there. This is not a good idea, much better to use bootscommerce-child and do changes there. This will prevent bugs like this as well.
Does this help?

Can't believe it was that simple. Well, sometimes we miss the easiest solutions :)
Thank you for your help. I'm going to change to child theme soon...

👍 You're welcome.


fix(console): lints trigger with non-async tasks

change existing lints to only trigger with tasks that are async; those are all except those with kind 'blocking' and 'block_on'
this commit fixes issue #516

yea, good suggestion. I can do that!

I made the change. Please, don't hesitate to ask for any other change (nit or anything). I really want to learn, so I really appreciate any kind of suggestion! :)

looks lovely, thank you!


fix(ssr): change CommonJS and resolve plugin order

Description
When trying to build a node library with the ssr mode, vite was failing with couple of issues

CommonJS modules were not always transformed. The specific case for me was dependencies that are CJS build of ES module codebase with  __esModule flag set, in this case vite ended up assuming that files in the dependency imported by files in the dependency itself are ES modules instead of CJS. Applying the CommonJS plugin earlier fixed this issue

Tree shaking was just not working, I got ~34MB builds and the build did not reference imports properly and was broken. Apply the resolve plugin later fixed this issue, the build came down to ~5MB and generated build was correct.

I figured this out by testing bundling by just using rollup and rollup plugins, there also I was able to reproduce the issue when the CommonJS plugin is not applied early and resolve (the rollup one, not vite one, though I guess similar) is not applied later.
Just as a side note, I did try, enabling the dep optimiser and disabling CommonJS, which did solve the two issues above, but I had the issue that default exports from node builtins were not working. I have a minimal repro of that in this repo https://github.com/jiby-aurum/vite-issue. You will be able to repo it by cloning and running npm i && npx vite build && node dist/index.mjs. However I did not report an issue with it, as its experimental and not supported at the moment anyways.
Additional context
I am very new to the vite codebase and I am not sure if the order change of plugins is going to break something else. If it won't I would really appreciate if we can land this in 3.2 which is the next release in the pipeline

What is the purpose of this pull request?

[X] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

greatly appreciated if one of you can take a look at it @bluwy @patak-dev

Changing the order of plugins would almost always break things, and the tests are currently failing. I haven't looked deep into the issue, but I think it needs a different solution.

@bluwy I did not really look into tests, because locally some were already failing for me in main branch strangely.
Also not sure if it makes any sense to try to fix the CommonJS plugin, as we are anyways moving to dep optimisation. The issue I had with the dep optimiser was a much more straightforward one, it seemingly does not handle default exports properly. Basically with const EventEmitter = require("events"), EventEmitter should be a constructor function with the exports on it, however going through dep optimiser it becomes just a object with the exports on it. If you have any pointers what may be the cause, I can try to debug/fix rather the dep optimiser

@bluwy I close in favour of https://github.com/vitejs/vite/pull/10406, I commented a small change there, that just fixes the dep optimisation for me.


add wordllama

This requires pre-fetching the model which can be tedious to set up in firewalled envs. Otherwise, it's really quick and works a lot better than the original implementation.

Superseded by https://github.com/holoviz/lumen/pull/764


owr_video_renderer: add sink property

Make the video sink configurable at renderer creation time for further
flexibility. In some cases the default glimagesink can't be used. The
guintptr value should point to a valid GStreamer element.

So what would be the plan about this?
The existing tag property for renderers can't be used in WebKit because the video sink we have there doesn't (and won't, IMHO) support the video overlay interface.
Another option might to build a custom renderer within WebKit but we would need access to the pipeline but that's a private/internal API currently. So unless I misunderstood something we can't have a custom renderer either.

See issue #221 for discussion about how we will address this need. Closing.


Studying the Data

We've shown proficiency in scraping the data from the MPD website. The next step is to understand what the data means. Everyone will work together on this one to produce one document that describes the columns and meanings of specific classifications/categorizations with references in one text document.

closing this issue.


Use strict version for tfjs-core

Use strict version for tfjs-core. This is a quick fix for tensorflow/tfjs#560. Another PR support new ops is on the way.

This change is

The latest tfjs-core kernel backend has several new ops that node js does not support yet, and it would break NodeJSKernelBackend binding. This is why mnist-node example breaks.

Let’s not submit this yet. There are some other implications we need to
understand, would be good to get Daniels opinion.
Regarding a blacklist, that won’t work either, since it will be a compile
error with typescript.
On Wed, Aug 1, 2018 at 9:52 AM Shanqing Cai<EMAIL_ADDRESS>wrote:

@caisq approved this pull request.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tfjs-node/pull/130#pullrequestreview-142386340,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDLzdiYneOzUqCMyfYES2vVwkWDOEapks5uMbKxgaJpZM4VpnN5
.

Using strict tfjs-core version would cause issue for users who are using latest tfjs-core. https://github.com/tensorflow/tfjs-node/pull/132 should add new ops and fix the gap for now.


Exclude 'news' folder from getting included into extension

@brettcannon sorry, just noticed you had assigned your self to this. Oops


Configuration avoidance for Swift and C++ plugins

By minimizing the configuration time, Gradle improves the feedback loop to the developers waiting for his build to complete. With the various spike the native team have been doing, some technical debt got introduce at the configuration time.
Expected Behaviors
The Swift and C++ plugin should do the least amount of work possible during configuration. Some items to consider as part of this work are:

Lazy toolchain selection

There are 2 different motivations here:

Defer making a decision during plugin application, so that build logic can later influence this decision by configuring various things. This isn't about performance, this is about correctness.
Don't make a decision that isn't required for the current build. This is about performance.


Minor fix in MakeMultiAuth Command Acknowledgement  messages

This is a minor fix that have missed in MakeMultiAuthCommand.
corrected some acknowledgement message that was hard coded.

Thanks bro, this is very helpful.


[CC-PORTAL-FEEDBACK] Paginate to > 6 on members page

Taken at: https://p3000-z3feaf6d9-zc6a664da-gtw.z1add53af.slab.sh/en/members
Fields:

Which feature are you missing?: Paginate to > 6 on members page
What problem would that solve for you?: Currently there are 7 members on the ICC. The page only shows 6 until "Show More" button is pressed. This is a clunky UX.

Browser: Chrome 130 (Windows 10)
Screen size: 1368x912
Open #7 in Usersnap
Powered by Usersnap.

CC @rogankool @Kale98


Reduce flake8 max-line-length

Description
Reduce flake8 max-line-length
Changed Behaviour
No change
Fixes
Fixes # (issue)
Type of change

Code maintenance/cleanup

The Outreachy application period is over, so I'm closing your PR - thanks for your participation in Parsl+Outreachy so far!


do not use --iidfile parameter in docker build

[test]

[test-all]

[test-all]

[test-all]

I also tested this on rhel7 machine with docker installed and it worked.

I really do not want to build a container twice, because some layers already exist.

That is even better for us. We would need only the logs from the failing layer anyway.

[test]

[test]

s2i-base-container is failing here for CentOS 7:
Testing 'cgroup limits' usage...
  The test is running as root, all tests for cgroup limits will be run
  Testing 'limited memory' usage...
Traceback (most recent call last):
  File "/usr/bin/cgroup-limits", line 180, in <module>
    "NUMBER_OF_CORES": get_number_of_cores()
  File "/usr/bin/cgroup-limits", line 97, in get_number_of_cores
    limits = [l for l in [_read_cpu_quota(), _read_cpuset_size(), _read_nproc()] if l]
  File "/usr/bin/cgroup-limits", line 172, in _read_nproc
    except FileNotFoundError:
NameError: global name 'FileNotFoundError' is not defined
MEMORY_LIMIT_IN_BYTES=
test/run: line 25: [: : integer expression expected
MEMORY_LIMIT_IN_BYTES not set to 536870912.

It should be fixed by #322

And for RHEL8 there are failing for reason:
Testing 'cgroup limits' usage...
  The test is running as root, all tests for cgroup limits will be run
  Testing 'limited memory' usage...
Traceback (most recent call last):
  File "/usr/bin/cgroup-limits", line 180, in <module>
    "NUMBER_OF_CORES": get_number_of_cores()
  File "/usr/bin/cgroup-limits", line 97, in get_number_of_cores
    limits = [l for l in [_read_cpu_quota(), _read_cpuset_size(), _read_nproc()] if l]
  File "/usr/bin/cgroup-limits", line 171, in _read_nproc
    return int(subprocess.run('nproc', capture_output=True).stdout)
  File "/usr/lib64/python3.6/subprocess.py", line 423, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'capture_output'
MEMORY_LIMIT_IN_BYTES=
test/run: line 25: [: : integer expression expected
MEMORY_LIMIT_IN_BYTES not set to 536870912.

I think this is, however, not caused or related to this PR.


Add the new Open Food Facts icons

What

[ ] Add the new Open Food Facts icons so that we can release an updated version of Open Food Facts to F-Droid
[ ] Add the new Open Pet Food Facts icons, so that we can release updated versions of  Open Pet Food Facts to the Play Store
[ ] Add the new Open Beauty Facts icons, so that we can release updated versions of Open Beauty Facts to the Play Store
[ ] Add the new Open Product Facts icons, so that we can release updated versions of Open Product Facts to the Play Store
[ ] https://drive.google.com/drive/u/1/folders/1_soLYCz9EjRDugd2pdoda3Id7S6ub3B6

@teolemon  We can add the Hacktoberfest tag too, to let a beginner contribute to this one.

@teolemon I would like to work on this issue, I am new to open source kindly guide me also.

Is this issue still open ?

Yes, it is

@teolemon Can you assign me this issue ?

here you go @dmdbilal 👍

@teolemon Which logo do I need to change to ?

@teolemon Can you briefly explain what should i need to do for this issue ?

@dmdbilal you need to update the assets with the new logos that are in the folder linked in the original post.

@VaiTon @teolemon Do I need to change the logo only for Open food facts or All the projects specified there.

@dmdbilal as you want, any contribution is appreciated!

Is this issue still open ?

@TanishMoral11 yup it is


Do not install recommends

As discussed yesterday on irc, we should instruct salt to not install recommended packages.

Q - Should we instead just remove all the pkg.installed entries? Given how CaaSP/Kubic works, they are unnecessary steps anyway?


Allow PUSHS to be used before a section

Previously, a PUSHS before a SECTION directive would cause rgbasm to crash when encountering a subsequent POPS.
This is because the subsequently-called out_SetCurrentSection() expected the new section to be non-null, which wasn’t the case in this situation. This has been addressed by allowing the ‘null’ section to be set in this function, and only dereferencing it (to set nPC) if a non-null section is to be set.
In practice, this means that PUSHS/POPS can now be used to push/restore a context without a section.
Fixes #373.

Following further discussion in #373, I've updated this PR to allow pushing/restoring a section-less context (instead of disallowing a push before a section is set). I hope that force-pushing to this PR was an OK way to change direction like this!


Windows 10 Home (1903) does not install or uninstall rdpwrap

Windows 10 Home (1903).
When installing and uninstalling the SOFTWARE, the program reports -

[-] [-] TermService is hosted in a custom application (Between, etc.) - unsupported.
[] [] Image Path: "".

Also previously there was an error  -

OpenKeyReadOnly error Code 0

The configuration settings report about...

Everything worked fine yesterday
how to solve the problem?

Try https://github.com/stascorp/rdpwrap/issues/837


Yicheng: Event UI upgrade for upcoming events page

Note: 🔺filed are required.

Summary 🔺

Modified font sizes, line heights and font weights to improve readabiulity
Added support for photo of event guests
Added a link for event registration

Issue Number 🔺 https://github.com/UofT-VEEP/VEEP-Website/issues/40

New Proposal

The original design of the event page was two tabs: Events This Year and Past Events, however, I think using Upcoming Events and Past Events makes more sense, as it makes it easier for people to see what events to expect in the future, and where o look for if they are looking for past events. Do you agree with this change? If so, I think we can remove the Event Replay accordion as well.

I think using Upcoming Events and Past Events makes more sense, as it makes it easier for people to see what events to expect in the future, and where o look for if they are looking for past events.

@davidYichengWei Good idea! What do you think if we add a tab on the side of the screen (like vertically) that says upcoming events and past events. And then inside past events we can have different years (similar to past projects) I feel like that would look nice. What do you think?

Hi @CatherineZM ,
Yeah, I think that will definitely look good. What I'm thinking is just that if I'm a person who just wants to learn about past events of VEEP, it might be easier for me if all events are displayed on one page sorted by date, than if I have to click on different years to view the past events. Splitting them into different years will definitely make the page more organized as we have more events in the future though. What are your thoughts on this? We can discuss this in the meeting later as well.

it might be easier for me if all events are displayed on one page sorted by date, than if I have to click on different years to view the past events.

@davidYichengWei That's true. We could just have a bigger title of what year the event is and have the list instead of accordion for now. But in the future when we have a lot more events, we can have an accordion instead

@Felix-Deng @iiiizuo Take a look when you get a chance. If there's no more changes, you can merge it


[CRITICAL] [Advanced Approval Workflows] Implement <WorkspaceWorkflowsApprovalsEditPage /> for Editing Workflow

Coming from: #wave-control: advanced approval + workflows polish
Issue OwnerCurrent Issue Owner: @blazejkustra

Hey! I’m Błażej Kustra from Software Mansion, an expert agency, and I’d like to work on this issue!

@MelvinBot Calm down, I'm working on a PR 🙈

I'm glad to be assigned to this issue; I have context regarding the approval flow in this PR

@tgolen Could you help process payment for me to review this PR?

@isabelastisser Could you please help with paying @DylanDylann for a C+ review of the PR?

@DylanDylann, the offer was sent in Upwork. Please accept it, and I will process the payment. Thanks!

wait, not sure if this should've been closed.

@DylanDylann, the offer was sent in Upwork. Please accept it, and I will process the payment. Thanks!

Hi I believe you sent this to me as I just received an Upwork email for you - just wanted to confirm I am not the individual you meant to send this to :)

ops, thanks for the heads up @dylmye!
@DylanDylann, what's your Upwork profile?

@isabelastisser Here it is https://www.upwork.com/freelancers/~010c6310ab55f3d17d

@isabelastisser do you need anything else here or can this be paid and closed out?

This has been paid already. All set, Tim!


Mention rubocop-thread_safety as a known extension

Mentioning rubocop-thread_safety in the docs may have helped @tdeo in #4072.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[ ] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it).
[ ] Squashed related commits together.
[ ] Added tests.
[ ] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[ ] All tests are passing.
[ ] The new code doesn't generate RuboCop offenses.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[ ] Updated cop documentation with rake generate_cops_documentation (required only when you've added a new cop or changed the configuration/documentation of an existing cop).

We should probably rename this section at some point. :-)


Could not connect to given url Grafana v5.1.3 (087143285) Integration Zabbix 3.9.1

I'm submitting a ...

[X ] Bug report
[ ] Feature requestdd
[ ] Question / Support request

If you don't send bug report, remove sections below
For bug report please include this information:
Software Versions

Grafana
Zabbix
Grafana-Zabbix Plugin

Grafana v5.1.3
Zabbix 3.9.1
XXXXX

What did you do?
Hello actually I'm new with zabbix and I'm trying integrate Zabbix with Grafana, and when I start to create a new Data Source ( the plugin zabbix is enabled)  doesn't show the direct and Proxy options ( only the options: Browser (default) and Browser )
after create the connection, the message  Could not connect to given url appears.
What was the expected result?
Describe here

RETURN:
curl -X POST -d '{"jsonrpc":"2.0","method":"apiinfo.version","params":[],"id":1}' -H "Content-Type:application/json" http://IP/zabbix/api_jsonrpc.php
{"jsonrpc":"2.0","result":"3.4.9","id":1}
curl -X POST -d '{"user":"admin","password":"admin"},"id":1}' -H "Content-Type:application/json" http://IP/zabbix/api_jsonrpc.php
{"jsonrpc":"2.0","error":{"code":-32700,"message":"Parse error","data":"Invalid JSON. An error occurred on the server while parsing the JSON text."},"id":null}
What happened instead?
If it relates to metric data visualization would be great to get

An image or text representation of your metric query
The raw query and response for the network request (check this in chrome dev tools network tab, here you can see metric requests and other request, please include the request body and request response)

Hi! The second request looks wrong:
curl -X POST -d '{"user":"admin","password":"admin"},"id":1}' -H "Content-Type:application/json" http://IP/zabbix/api_jsonrpc.php

Data should be like
{"jsonrpc":"2.0","method":"user.login","params":{"user":"admin","password":"admin"},"id":1}

Are you sure that request is made from plugin?

I resolved it using Invoke-RestMethod instead of Invoke-WebRequest, and now api "understand" my json. (powershell code)
Curl never worked for me. is equivalen to to Invoke-WebRequest.
(I'm in Zabbix 4.2)

I met the same problem, I add a Zabbix datasource on remote host,  then click the "Save & Test" button , show "Could not connect to given url", but I already added a local host zabbix datasource successfuly.
My grafana and zabbix info:
grafana: <IP_ADDRESS>:3000 v6.2.5
zabbix plugin:  3.10.2
zabbix datasource1: <IP_ADDRESS>:8000  v4.2  (OK)
zabbix datasource2: <IP_ADDRESS>:8010  v3.2  (NOK)

Add Zabbix datasource like this:

Add zabbix datasource like this:

Problem resolved !
Just change the HTTP URL from
"http://<IP_ADDRESS>:8010/zabbix/api_jsonrpc.php"
to "http://<IP_ADDRESS>:8010/api_jsonrpc.php"


Added RGB Color game

I contributed this project under hacktoberfest21. This project is made using html , css , javascript.

Congratulations for your Open source contribution. Don't forget to follow and add a star on this repo.. Happy hacking


Not a bug, recommendation. Add core interfaces IAction<T...>, IFunc<T...>

This is a thing that I always miss in .net.
Can you modify the Action and Func delegates in a way that its instances are castable to predefined interfaces: IAction, IFunc.
Same as in Java 11.
As I know each Action<T,...> is compiled into a class with 1 method. This class must implement IAction<T,...> with that method.
I need it in Unit tests.

Hi, @vhforte. Thank you for this suggestion. The dotnet/runtime repository has an issue template for suggesting API proposals. Would you be able to fill out that template? Ideally, the submission would include sample code showing how these interfaces would be used, what types of functions this would enable for you, and what you currently need to do as a workaround in the absence of these interfaces.
You'll want to use the "API Suggestion" issue template here:
https://github.com/dotnet/runtime/issues/new/choose


AutoComplete focus gets lost to Popover in Firefox

So I've been using AutoComplete successfully for the last few weeks in Chrome. Unfortunately our client hates Google and we need to make our app work in Firefox.
It appears that the current AutoComplete loses it's focus in Firefox as soon as the popover opens with results. I tested this on the official Material-UI documentation site as well. I am using the latest version of Firefox (43.0.4) if that helps.
I've been messing with it for hours trying to figure the issue out myself, but can't seem to make any progress.

I am having a similar problem in Chrome. For me it occurs when I have more than 1 AutoComplete on screen. The popover is closed immediately because of a onClickAway on the render layer of the popover. It results in very weird behaviour.

Ok, this is what I observed:

Click on the textfield to open the popover
Focus event results in opening the popover (and it is probably rendered immediately)
After the focus event the popover immediately receives a click event which is handled by the onClickAway to dismiss the popover again.

It looks like a timing issue, because when I set a breakpoint after the focus event is received and then lit continu it works fine.

@alitaheri I don't think this deserves the Cross Browser Support label, it looks like a bug to me.

Yeah, you're right. Thanks

I think the issues @hmeerlo  and @jeffberry are describing are different. I am also seeing a Firefox-specific UI problem.
To reproduce:
Step 1.
Open Chrome at http://www.material-ui.com/#/components/auto-complete
Click on the AutoComplete in the Simple example box.
Type chrysanthemum
Result: List of options is displayed below the text box and the text box displays chrysanthemum.
Step 2.
Open Firefox on  http://www.material-ui.com/#/components/auto-complete
Click on the AutoComplete in the Simple example box.
Type chrysanthemum
Actual result: List of options is displayed and text box displays c. Clicking down arrow highlights the second item in the drop list, indicating focus is on the list rather than the text field.
Expected result: Same as Chrome.
Although the page I have referred to has multiple autocomplete widgets, the problem also shows on a page with just the one.

Further search reveals this the problem I describe is covered by #3339 and addressed in PR #3356.
It is also possible that  #3356 also fixes the other focus issue.

Thanks for updating this @pdc. Everyone can test the changes in those PRs in our latest alpha since #3356 was included as part of that release. Feel free to reopen this if you are still having this problem.
http://www.material-ui.com/v0.15.0-alpha.1/#/components/auto-complete


Problems rendering {{page.summary}}

Hi:
I found that the {{page.summary}} render <p> </p> tags around the variable.
I suppose that this has to do with the markdown formatting.
How can I add a class to that  <p> </p> tag?, the only way I found around the issue was using {{ page.summary | striptags}} and setting my own code around the variable.

That's exactly the case.  The content has HTML tags added by markdown processing. You would have to remove them with Twig probably  You could use striptags, or regex to achieve this.  We have a regex_replace filter available which is a pass through for preg_replace in PHP (need to get this added to docs)

I added my comment to the documentation, in hopes that someone may find it useful.
{{ page.summary | striptags}} works as intended

I found this useful! But I also discovered that there's a problem with this method. Since page.summary() generates <p> tags without putting a space between them, the striptags filter will join the two paragraphs together without a space. I could of course use the preg_replace filter, but considering how common it must be to want to use page.summary to generate a meta description tag, I think Grav would benefit from an easier way to achieve this. I guess one way would be to ensure that there's always a single space between generated the <p> tags generated from the markdown, and another would be to allow passing a second boolean parameter to page.summary that makes the method strip away HTML tags if true.


Implement Default for structs with lots of Optional fields

Some structs like Contact have lots of Optional fields, which are very verbose when initializing:
         Contact {
             phone: Absent,
             sip: Absent,
             keymasters: Absent,
             irc: Value("irc://freenode.net/#coredump".into()),
             twitter: Value("@coredump_ch".into()),
             facebook: Absent,
             google: Absent,
             identica: Absent,
             foursquare: Value("525c20e5498e875d8231b1e5".into()),
             email: Value("danilo@coredump.ch".into()),
             ml: Absent,
             jabber: Absent,
             issue_mail: Absent,
         }

Ah, true. That would probably be the better way than using the builder pattern everywhere (see #21).

On the other hand, the builder pattern would be nice to enforce requirements like that at least one contact field has to be set.

That is true.

In #38 we added the Default trait for most structs, so I consider this closed.


What to do when the offset is too large for the last lithology layer

Hi Matt et al. I can propose a solution to the issue I encountered with the sediment log I was testing.
issue Error when offsetis to large causing the function tops_from_loglike in utils.py to look for values in the array a that are out of range.
fix I propose to create a while loop that will chop of the last lithology unit if it is too thin for the chosen offset (from line 478 in utils.py)
try:
        values = a[tops + offset]
    except:
        lasttop = len(a) - tops[-1]
        i = 1
        while lasttop < offset:
            lasttop += len(a) - tops[-i]
            i += 1
        tops = tops[:-i]
        values = a[tops + offset]  # If the offset is too big relative to the last layer remove last top

I can make a pull request for this fix if you want, but I am not sure how generic this solution is.

Thanks for this John. I had a fix in the develop branch, but I have not tested it rigorously. It was a different approach to you. If you get a chance to try it out, I'd be interested in knowing if it fixes the problem you were experiencing.
You'd install with python -m pip install --upgrade https://github.com/agile-geoscience/striplog/archive/develop.zip

Thanks for this John. I had a fix in the develop branch, but I have not tested it rigorously. It was a different approach to you. If you get a chance to try it out, I'd be interested in knowing if it fixes the problem you were experiencing.
You'd install with python -m pip install --upgrade https://github.com/agile-geoscience/striplog/archive/develop.zip

Hi Matt, it is possible your fix does not work as I get the out of bounds error message. Is there a way to check that I am using the develop branch after running the pip command? (Sorry that I have a slow return around time on this issue)

Hi John, you can check the version with the following in a python interpreter:
import striplog
striplog.__version__

for me that is 0.8.8, which is the most recent development version. I am not sure exactly when the fix Matt mentions above went in, since the last commit is dated to January 12th.

Yep that is the version number I have. I am testing the modifications on the develop branch, so before replying that it does not work I would like to be sure. I had a look at the repo and it says that for the develop branch: "This branch is even with master." Does this perhaps mean that Matt's modifications have not been pushed to the repo?

Oops, my bad, I think I was in master, sorry about that. Anyway, develop is now synced and both are pushed.

I have not had success:
---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
<ipython-input-6-771446b87056> in <module>
      1 from striplog import Striplog
      2
----> 3 strip = Striplog.from_image(infile,
      4                             start=0, stop=2631,
      5                             col_offset=5,     # How far across the image to extract pixels.

~/miniconda3/envs/sedlogs/lib/python3.9/site-packages/striplog/striplog.py in from_image(cls, filename, start, stop, legend, source, col_offset, row_offset, tolerance, background)
    850
    851         # Get the pixels and colour values at 'tops' (i.e. changes).
--> 852         tops, hexes = utils.tops_from_loglike(loglike, offset=row_offset)
    853
    854         # If there are consecutive tops, we assume it's because there is a

~/miniconda3/envs/sedlogs/lib/python3.9/site-packages/striplog/utils.py in tops_from_loglike(a, offset, null)
    476     tops = np.append(0, tops)
    477
--> 478     values = a[tops + offset]
    479
    480     if contains_nans and transformed:

IndexError: index 12413 is out of bounds for axis 0 with size 12413

I attach an image of the log I am trying to digitalise so you can test it at your end to be sure it is not my fault for not managing to update to the most recent version of striplog.

sorry, the attached image comes out huge...

HI @johnjarmitage
I was just taking a look to try and fix this. The code in your error message does not look like the current code that I am seeing in the repo. The current version looks like this for the lines giving the error you posted above:
offs = tops + offset
values = a[offs[offs < a.size]]

This snippet should prevent the IndexError that you are getting. I am not sure which version you are using, but it might not be happening with the newer version. Do you have some data that I can test this with to try and replicate it? I am not sure if the snippet that I am seeing has had a release, but it looks like the change was here: https://github.com/agile-geoscience/striplog/commit/9ef74bf5622397c76750a8081831f6a7029a75e8

Hi @mtb-za
I ran python -m pip install --upgrade https://github.com/agile-geoscience/striplog/archive/develop.zip and then relaunched my notebook. There is now no error message, so it is possible that this bug has been fixed during the SWUNG meeting.
You can close the issue I think.

I am glad that it seems to have been resolved. Let us know if there is anything more that you come across.


Add ServerVulnerabilityAssessment and ManagedInstanceVulnerabilityAssessment operations

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] Please add REST spec PR link to the SDK PR
[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[x] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

REST API PR -https://github.com/Azure/azure-rest-api-specs/pull/4416

@jaredmoo   @yoavfr  @talhers

There are test failures, please look at Travis CI build and scroll all the way to the bottom.
I noticed that ManagedInstanceTestFixture is reusing the same test recording file for all tests that use it (notice .ctor.json). This seems like a problem, the tests that call into ManagedInstanceTestFixture should pass in the suite object and method name so that when ManagedInstanceTestFixture creates SqlManagementTestContext this suiteObject and testName should be the test method's class and method name. I am not sure however if this is specifically what is causing the test failure.

Other than this test issue the change looks good though :)

@yaakoviyun CI tests still failing, please take a look

@dsgouda , @jaredmoo  - tests are passing

@talhers

Ping...

@yaakoviyun @jaredmoo What Nuget package version do you wish to release this as, 1.24.-0-preview or 1.25.0-preview

@yaakoviyun please squash commits into a single commit and we are good to merge

How can I do it? What is the method you guys use for squashing?
Sent from Outlook

מאת: Deepak Shankargouda<EMAIL_ADDRESS>נשלח: יום רביעי 21 נובמבר 2018 19:36:54
אל: Azure/azure-sdk-for-net
עותק: Yaakov Iyun; Mention
נושא: Re: [Azure/azure-sdk-for-net] Add ServerVulnerabilityAssessment and ManagedInstanceVulnerabilityAssessment operations (#5005)
@yaakoviyunhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fyaakoviyun&data=02|01|yaiyun%40microsoft.com|d084f053e1a346a5986808d64fd7eda1|72f988bf86f141af91ab2d7cd011db47|1|0|636784186157830291&sdata=2t%2BaEZV0PSQwvSalix7LgjrORkY07nsfugkc%2F3RP3Nw%3D&reserved=0 please squash commits into a single commit and we are good to merge
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-sdk-for-net%2Fpull%2F5005%23issuecomment-440751045&data=02|01|yaiyun%40microsoft.com|d084f053e1a346a5986808d64fd7eda1|72f988bf86f141af91ab2d7cd011db47|1|0|636784186157840225&sdata=LS9J5nbbW6zGREv7P2%2FXzBhXw2Qg8wOLQj7yeWx9ZX8%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALNguRrwWD5vyU-lqtiMdYc2fgdg1-MBks5uxY82gaJpZM4YUvTO&data=02|01|yaiyun%40microsoft.com|d084f053e1a346a5986808d64fd7eda1|72f988bf86f141af91ab2d7cd011db47|1|0|636784186157840225&sdata=XUts5ZtX7VbnRBGz%2FSfVPo2LU5na37vh23cMAKwOmDM%3D&reserved=0.

@yaakoviyun The easiest way is to copy your changes to a temp directory, recreate a branch from latest psSdkJson6 and copy over the changes to this branch.

http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html

So, git rebase -i psSdkJson6 and then change all "pick" to "squash" except the first one. This will redo your change history on top of psSdkJson6 branch and squash them down into one commit.
Or,
git reset --hard psSdkJson6
git merge --squash ee511584aa30b93a7032b9afa896a17b40cc11ec

This will reset your branch to the same state as psSdkJson6, then squash merge all changes up until ee511584aa30b93a7032b9afa896a17b40cc11ec into this branch. (This is the commit id of the latest commit in your branch - https://github.com/Azure/azure-sdk-for-net/pull/5005/commits/ee511584aa30b93a7032b9afa896a17b40cc11ec )
These two methods are equivalent, just different UX.

@dsgouda Is it possible for you to squash merge in github UI?

Oh btw @yaakoviyun after you do this squash you will need to git push --force since it rewrites commit history so it is destructive to the remote branch that you are pushing to

When you do a pull from upstream, the best way to squash commits is as I mentioned above

Will it require a new PR?
I must say that is operation seems very messy and doesn’t feel like a best practice move.
Sent from Outlook

מאת: Deepak Shankargouda<EMAIL_ADDRESS>נשלח: יום רביעי 21 נובמבר 2018 20:17:07
אל: Azure/azure-sdk-for-net
עותק: Yaakov Iyun; Mention
נושא: Re: [Azure/azure-sdk-for-net] Add ServerVulnerabilityAssessment and ManagedInstanceVulnerabilityAssessment operations (#5005)
When you do a pull from upstream, the best way to squash commits is as I mentioned above
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-sdk-for-net%2Fpull%2F5005%23issuecomment-440763240&data=02|01|yaiyun%40microsoft.com|767790be585f4024a78c08d64fdd8bfb|72f988bf86f141af91ab2d7cd011db47|1|0|636784210279517808&sdata=W%2B2a%2Fb53rbBiiHErDsYjc3UI2DOIr5gjRGsEAOw9hd4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALNgucXLh4CvW3Ftk5vT3gUa3ztUiZXpks5uxZijgaJpZM4YUvTO&data=02|01|yaiyun%40microsoft.com|767790be585f4024a78c08d64fdd8bfb|72f988bf86f141af91ab2d7cd011db47|1|0|636784210279527813&sdata=Us2d7vJ8Ql9TslCh0fHix81ZFLnCkgA5q%2FgQqlzXWyA%3D&reserved=0.

It seems not the right thing to do.
Creating a new PR will hide all the original PR’s comments.
It seems that for every change, a developer will need two PRs and additional manual steps which raises the chance for mistakes.
Is this the way all PRs are managed?
Sent from Outlook

מאת: Deepak Shankargouda<EMAIL_ADDRESS>נשלח: יום רביעי 21 נובמבר 2018 20:26:52
אל: Azure/azure-sdk-for-net
עותק: Yaakov Iyun; Mention
נושא: Re: [Azure/azure-sdk-for-net] Add ServerVulnerabilityAssessment and ManagedInstanceVulnerabilityAssessment operations (#5005)
@jaredmoohttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjaredmoo&data=02|01|yaiyun%40microsoft.com|56fd8f0699824f69e42308d64fdee8a9|72f988bf86f141af91ab2d7cd011db47|1|0|636784216137842483&sdata=ZcmpTCoXKhyGHQelZHxFpq74ahYbJXXeq8jMZM0T5%2B8%3D&reserved=0 problem is if the "merge" is a part of the commit history, the whole commit history gets messed up too.
As for the concerns about merging, the idea is to make sure the branch is ready to be merged to psSdkJson6 and then recreate a new branch with the ready to merge changes.
If it still feels like an issue, simply create another branch and another PR with it referencing this one so we skip the review.
Hope this helps
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-sdk-for-net%2Fpull%2F5005%23issuecomment-440766058&data=02|01|yaiyun%40microsoft.com|56fd8f0699824f69e42308d64fdee8a9|72f988bf86f141af91ab2d7cd011db47|1|0|636784216137852487&sdata=rGxhLCH1uBuihyo7Zf6mzhZ4Zy%2BbCn441p4h6yClwYI%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALNguXev1AJUsFUluoBCupXUHpKZyCmgks5uxZrsgaJpZM4YUvTO&data=02|01|yaiyun%40microsoft.com|56fd8f0699824f69e42308d64fdee8a9|72f988bf86f141af91ab2d7cd011db47|1|0|636784216137862490&sdata=m2dKHdvW4Tph%2Fc4ccRQO4fiC%2FevKPZ2Qp8T69%2FYfquE%3D&reserved=0.

The additional steps are needed only if the branch was updated with remote master and some conflicts had to be resolved, else a simple git rebase should work.
If you are able to do a git rebase successfully, we can proceed with this PR
Apologize for the confusion


Handle JSX imports of directories.

https://github.com/linkedin/css-blocks/issues/173#issuecomment-389953581
Import walking of JSX files should use webpack's resolver when in a webpack environment.

I just ran into this issue. Perhaps the requirement to import files instead of directories ought to be documented until there's a fix? I think I would have been doubly affected though b/c my import "tree" looked like index.tsx --> App/index.ts --> App/App.tsx
I noticed while debugging my build that only .jsx and .tsx imports are explored, so the App/index.ts in the middle there would have blinded css-blocks to the existence of App/App.tsx, which is where the block import happens.
(To be fair though, App/index.ts only existed as boilerplate. Webpack's default resolver doesn't look for files named the same as the directory, and I didn't want to use directory-named-webpack-plugin and be fighting module resolution errors all over the place in my editor.)
I also poked around at the webpack resolvers that get passed to the css-blocks plugin. It looks like they can only operate in async mode (on the first run—there's a layer of caching that kicks in on subsequent runs). I wonder if @babel/traverse is capable of handling async visitors.


Rust flashcard

@Zhyfengss I think you might have forgotten your issue body? 😅

I really thank you for creating such a useful tool. I was in the process of
testing and carelessly commented in the article
Отправлено с мобильного устройства
On Fri, 15 Mar 2024 at 16:10 Adrian Sieber @.***> wrote:

@Zhyfengss https://github.com/Zhyfengss I think you might have
forgotten your issue body? 😅
—
Reply to this email directly, view it on GitHub
https://github.com/ad-si/Rust-Flashcards/issues/5#issuecomment-1999228053,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUVCOGLI4Y2HBH7OOVMQZXDYYK3I5AVCNFSM6AAAAABEXQHJ7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJZGIZDQMBVGM
.


add framer

Thanks, but you just made the list. Give it some time to mature before submitting here.
Also, make sure it follows:
https://github.com/sindresorhus/awesome/blob/master/awesome.md

When I visited the list I had no idea what Framer was, after reading the list I still don't. Hint hint.


Attach Files

Is there a way to attach files to a message?

That would be nice

+1

I normally use some kind of pastebin to do that.


Setting timezone doesn't work when using Browser Mode with Playwright + WebKit + macOS

Describe the bug
When using Vitest Browser Mode to test some code that depends on a timezone, I noticed that setting the TZ environment variable only affects the time zone for Chromium and Firefox browsers, when running the tests on macOS.
It seems as though this issue does not happen on Linux.
For contrast, I tried using Playwright Test and setting the timezone via the timezoneId option, and this works fine under macOS. So I don't think it's an inherent limitation of the Playwright provider. Setting the same option via Vitest Browser Mode Provider Configuration seems to have no effect at all.
Reproduction
I've created a minimal reproduction as a GitHub repo, because this issue can only be reproduced under macOS: https://github.com/ezzatron/vitest-browser-mode-timezone-repro
You can see the test suite results in this GitHub Actions workflow run show that under macOS, Chromium and Firefox are working, but WebKit is not (from the macos job):
RUN  v2.1.3 /Users/runner/work/vitest-browser-mode-timezone-repro/vitest-browser-mode-timezone-repro
      [chromium] Browser runner started by playwright at http://localhost:5173/
      [firefox] Browser runner started by playwright at http://localhost:5175/
      [webkit] Browser runner started by playwright at http://localhost:5174/

 ✓ |chromium| timezone.test.js  (2 tests) 47ms
 ✓ |firefox| timezone.test.js  (2 tests) 23ms
 ❯ |webkit| timezone.test.js  (2 tests | 2 failed) 213ms
   × timezone should be Asia/Jakarta
     → expected 'UTC' to be 'Asia/Jakarta' // Object.is equality
   × timezone offset should be -420
     → expected +0 to be -420 // Object.is equality

Linux is working fine (from the linux job):
RUN  v2.1.3 /home/runner/work/vitest-browser-mode-timezone-repro/vitest-browser-mode-timezone-repro
      [chromium] Browser runner started by playwright at http://localhost:5173/
      [firefox] Browser runner started by playwright at http://localhost:5175/
      [webkit] Browser runner started by playwright at http://localhost:5174/

 ✓ |chromium| timezone.test.js  (2 tests) 17ms
 ✓ |firefox| timezone.test.js  (2 tests) 11ms
 ✓ |webkit| timezone.test.js  (2 tests) 133ms

I also tested Windows, which didn't seem to work for any browser.
System Info
System:
    OS: macOS 14.6.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 491.09 MB / 32.00 GB
    Shell: 5.9 - /opt/homebrew/bin/zsh
  Binaries:
    Node: 22.9.0 - /opt/homebrew/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 10.8.3 - /opt/homebrew/bin/npm
    pnpm: 8.10.3 - /opt/homebrew/bin/pnpm
    bun: 1.1.30 - /opt/homebrew/bin/bun
  Browsers:
    Chrome: 129.0.6668.101
    Edge: 129.0.2792.89
    Safari: 18.0.1
  npmPackages:
    @vitest/browser: ^2.1.3 => 2.1.3
    vitest: ^2.1.3 => 2.1.3

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

timezoneId  doesn't exist on providerOptions. You can add @vitest/browser/providers/playwright to your types to get better Type Hint support. Does this help?
export default defineConfig({
  test: {
    browser: {
      providerOptions: {
        context: {
          timezoneId: 'Asia/Jakarta'
        }
      }
    }
  }
})

Yes, that does work. Thank you!
P.S. I did try adding @vitest/browser/providers/playwright to my tsconfig.json but for some reason the type hints aren't working for me in the real project where I had this issue (I didn't use TypeScript in the repro). It's probably a TypeScript config issue of some kind. The other types (@vitest/browser/matchers) are working for expect.element etc.

FWIW I updated the repro repo at https://github.com/ezzatron/vitest-browser-mode-timezone-repro to use TypeScript. Those @vitest/browser/providers/playwright types still don't seem to work for me. I put some extra properties in the providerOptions and there's no TypeScript errors when you run npx tsc --noEmit.
https://github.com/ezzatron/vitest-browser-mode-timezone-repro/blob/ff668e27c98836c7b388c78222189d8b96bdabe8/vitest.workspace.ts#L21-L27


feat(just): added nix installation to 00-default.just

Now all ublue images has an option to install nix on it

gonna put it in its own file

https://github.com/ublue-os/config/pull/161


Fetch Google OAUTH public key from the server rather than hardcoding zulip.com's

This is required to support Google auth with non-zulip.com servers, and thus is a natural follow-up to #1.
See https://github.com/zulip/zulip/issues/102 for details on the backend change that now supports doing this fetching.

I could work on this after doing #48...

There's some limitations with the Google Oauth APIs for android that limits our ability to do this, see this zulip-devel thread for context.
Barring a solution from Google, the best alternative is to allow users to auth themselves with Google via a WebView.

This is solved now, right?

Yep. 👍


Add Turing Network to Kusama Relay & some neumann cleanup

Announced: https://oak.tech/turing/crowdloan/
Crowdloan to begin soon within the week.
Clean up old types no longer relevant to neumann and turing

@chrisli30 - prepping this branch for internal review. Will do a real PR against the upstream tomorrow.


[Bug/Glitch] Game is crashing after the 4J logo - Fabric 1.21

Legacy4J Version
1.21-1.7-fabric
Mod Loader Version
Fabric Loader 0.15.11
Bug/Glitch Occurrence Context

Open Minecraft
Logos appearing normally (They are in an infinite loop but I don't know if this is normal)
Click on the screen to skip
The game closes

Crash Report
https://pastebin.com/Eb88mY93
What happened wrong?
I can't play the Legacy4J mod because my game is simply crashing after the logos appear in an infinite loop. I tried to solve this using the old versions of the mod but none of them actually worked, I didn't try to compare the logs of each version of the mod to see if they were the same.
Seeing now I forgot to add the Architectury API, but even after adding it my Minecraft continues to close the same way as before

#498


Missing xmlrpc gem on Ruby >= 2.4

Bug Report
Version of OpenNebula

[ ] 5.2.2
[ ] 5.4.0
[ ] 5.4.1
[ ] 5.4.2
[ ] 5.4.3
[ ] 5.4.4
[ ] 5.4.5
[ ] 5.4.6
[ ] 5.4.7
[ ] 5.4.8
[ ] 5.4.9
[ ] 5.4.10
[X] Development build

Component

[ ] Authorization (LDAP, x509 certs...)
[ ] Command Line Interface (CLI)
[ ] Contextualization
[ ] Documentation
[ ] Federation and HA
[ ] Host, Clusters and Monitorization
[ ] KVM
[ ] Networking
[ ] Orchestration (OpenNebula Flow)
[X] Packages
[ ] Scheduler
[ ] Storage & Images
[ ] Sunstone
[ ] Upgrades
[ ] User, Groups, VDCs and ACL
[ ] vCenter

Description
Since Ruby 2.4.0 xmlrpc isn't part of the stdlib (https://www.ruby-lang.org/en/news/2016/12/25/ruby-2-4-0-released/), we need to add dependency on xmlrpc Gem for Ruby 2.4+.
Progress Status

[x] Branch created
[x] Code committed to development branch
[x] Testing - QA
[x] Documentation
[x] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

PR to merge: https://github.com/OpenNebula/one/pull/2018


ExpressionTypeError: Unable to resolve type for operation: if_else

Unclear if that is a bug, a feature idea, or a communication need.
Issue
What should be done if we use if_else and set values of a different type?
To Reproduce
Use an if_else with different types.
I set a float as a missing value for an int column in this example.
import daft

df = daft.DataFrame.from_pydict({'a':[1,None,3]})
df.with_column('b', df['a'].is_null().if_else(0.0, df['a'])).show()

Expected behaviour
Intuitively, I would expect it to cast to int, but not sure how that would be implemented in the average case.
Maybe for a native fill_na, we can apply an automatic cast, but on the original if_else, we should keep it as an error.

Thanks @xdssio!
The behavior here is correct because, for example, if we do an .if_else(float, string), the behavior is not well defined. In the above case you presented, we would suggest: df['a'].is_null().if_else(0.0, df['a'].cast(float))).
I agree that perhaps the error message here should be more explicit. We should inform the user that the types of the columns provided to if_else need to be the same.

This is handled by supertype promotion semantics in our new Rust execution engine!


Strange advice: testImplementation -> runtimeOnly (instead of testRuntimeOnly)

Build scan link

Plugin version
1.19.0
Gradle version
7.6
(Optional) Android Gradle Plugin (AGP) version
7.4.2
reason output for bugs relating to incorrect advice
> Task :stringers:reason

----------------------------------------
You asked about the dependency 'org.robolectric:robolectric:4.4'.
You have been advised to change this dependency to 'runtimeOnly' from 'testImplementation'.
----------------------------------------

There is no path from :stringers to org.robolectric:robolectric:4.4 for debugCompileClasspath

There is no path from :stringers to org.robolectric:robolectric:4.4 for debugRuntimeClasspath

Shortest path from :stringers to org.robolectric:robolectric:4.4 for debugUnitTestCompileClasspath:
:stringers
\--- org.robolectric:robolectric:4.4

Shortest path from :stringers to org.robolectric:robolectric:4.4 for debugUnitTestRuntimeClasspath:
:stringers
\--- org.robolectric:robolectric:4.4

There is no path from :stringers to org.robolectric:robolectric:4.4 for debugAndroidTestCompileClasspath

There is no path from :stringers to org.robolectric:robolectric:4.4 for debugAndroidTestRuntimeClasspath

There is no path from :stringers to org.robolectric:robolectric:4.4 for releaseCompileClasspath

There is no path from :stringers to org.robolectric:robolectric:4.4 for releaseRuntimeClasspath

Shortest path from :stringers to org.robolectric:robolectric:4.4 for releaseUnitTestCompileClasspath:
:stringers
\--- org.robolectric:robolectric:4.4

Shortest path from :stringers to org.robolectric:robolectric:4.4 for releaseUnitTestRuntimeClasspath:
:stringers
\--- org.robolectric:robolectric:4.4

Source: debug, main
-------------------
(no usages)

Source: release, main
---------------------
(no usages)

Source: debug, test
-------------------
* Provides 1 service loader: org.robolectric.plugins.DefaultSdkProvider (implies testRuntimeOnly).

Source: release, test
---------------------
* Provides 1 service loader: org.robolectric.plugins.DefaultSdkProvider (implies testRuntimeOnly).

Source: debug, android_test
---------------------------
(no usages)

Describe the bug
Robolectric is a test dependency. It's even used as
import org.junit.runner.RunWith;
import org.robolectric.annotation.Config;
import org.robolectric.annotation.internal.DoNotInstrument;

@RunWith(AndroidJUnit4.class)
@Config(sdk = Build.VERSION_CODES.P)
@DoNotInstrument
public class ...Test {

but even if we ignore this, based on the
* Provides 1 service loader: org.robolectric.plugins.DefaultSdkProvider (implies testRuntimeOnly).

it sounds like testRuntimeOnly is the correct suggestion.
To Reproduce
Steps to reproduce the behavior:
// StandardTransformTest
    @Test fun `robolectric should be testRuntimeOnly`() {
      val id = "org.robolectric:robolectric"
      val coordinates = ModuleCoordinates(id, "4.4")
      val usages = setOf(
        usage(bucket = Bucket.RUNTIME_ONLY, variant = "test", kind = SourceSetKind.TEST),
      )
      val declarations = Declaration(id, "testImplementation").intoSet()

      val actual = StandardTransform(coordinates, declarations, supportedSourceSets).reduce(usages)

      assertThat(actual).containsExactly(
        Advice.ofChange(coordinates, "testImplementation", "testRuntimeOnly"),
      )
    }

Expected behavior
You have been advised to change this dependency to 'testRuntimeOnly' from 'testImplementation'.

Additional context
This is fixed by https://github.com/autonomousapps/dependency-analysis-android-gradle-plugin/commit/00ea30f44d78f102d4260fe78367f1c1195c827c, but there was no test added for the problem, the above one could help prevent regressions.

I posted a reason here https://github.com/autonomousapps/dependency-analysis-android-gradle-plugin/issues/810#issuecomment-1490023534 that advice from androidTestImplementation to runtimeOnly instead of androidTestRuntimeOnly. I assume that it is the same issue.

@BraisGabin this is already fixed on main, try to use the latest snapshot:
https://oss.sonatype.org/#nexus-search;gav~com.autonomousapps.dependency-analysis~com.autonomousapps.dependency-analysis.gradle.plugin~1.19.1-SNAPSHOT~~

Thanks all.


Syntax Highlighting: Support Multiline Strings

Taken from @usebruno/lang:
   // Multiline text block surrounded by '''
  multilinetextblockdelimiter = "'''"
  multilinetextblock = multilinetextblockdelimiter (~multilinetextblockdelimiter any)* multilinetextblockdelimiter

  // Dictionary Blocks
  ...
  value = multilinetextblock | valuechar*

Still not supported by vscode syntax highlighter.

Should be solved by PR #26


MGMT-15170: improve errors for appliance-config unmarshal failure

Output user friendly error messages when failing to parse appliance-config.yaml.
E.g.
FATAL failed to load asset "Appliance Config": can't parse appliance-config.yaml.
Ensure the config file is configured correctly (error in field ApplianceConfig.diskSizeGb)

/test all

/retest

/retest


ImageMagick Binary

I don't understand what path to the file should be inserted.  which one did I download or which did I install and take the path to the .exe file?

On Windows it's called magick.exe.

@FujiwaraChoki and for Mac?

if you used hombrew
/opt/homebrew/Cellar/imagemagick/7.1.1-27/bin/magick

I believe for Macs with Intel it should be
/usr/local/Cellar/imagemagick/7.1.1-27/bin/magick

And also change the version number to what you have installed

run brew info imagemagick for get path


Add support for meson.

Not really sure we need to frob PATH, but I wanted to make sure we're using our patched meson if present.  Also, might help insulate ourselves against newer g-speaks being installed remotely and coming first on PATH.

Untested but lgtm.


Unify approach to printing declaration names

Printing a declaration's name using << and getBaseName() is be independent of the return type of getBaseName() which will change in the future from Identifier to DeclBaseName
This PR depends (and includes the changes) from #9319

@swift-ci Please test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 0eb6f9b3a6a10b70ddcc98e1322e1f8c4735f8a8
Test requested by - @ahoppen

@swift-ci Please test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 0eb6f9b3a6a10b70ddcc98e1322e1f8c4735f8a8
Test requested by - @ahoppen

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 0eb6f9b3a6a10b70ddcc98e1322e1f8c4735f8a8
Test requested by - @ahoppen

@swift-ci Please smoke test


devDependencies includes bootstrap 2

In bower.json there is bootstrap 2.X in dependencies.
New stack is supposed to be based on bootstrap 3.
See : https://github.com/ovh-ux/ovh-manager-web/blob/master/bower.json

@whispyy ovh-utils-angular is a deprecated dependencie.
You can refer to this resolution used by the OVH Control Panel Web UI:
https://github.com/ovh-ux/ovh-manager-web/blob/master/bower.json#L99


[WIP] Adding Image Pull workload

Depends-On: https://github.com/cloud-bulldozer/benchmark-wrapper/pull/264
Description
Adding Image Pull workload which takes a list of images to pull and X pod's to do them. It then coordinates each image to be pulled by the pod at roughly the same time (within a few second margin of error). It can then display and index the resultant data around timings, retries, etc.
Fixes

/rerun all tests/test_image_pull.sh

/rerun all tests/test_image_pull.sh

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_image_pull
Pass
0
00:06:17

/rerun all tests/test_image_pull.sh

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

/rerun all tests/test_image_pull.sh

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_image_pull
Pass
0
00:02:51

is this still a WIP @dry923

is this still a WIP @dry923

@jtaleric nope its good. I was waiting on the tests to make sure I didn't have to modify anything but it looks solid.

/rerun all

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:03:43

test_byowl
Pass
0
00:00:12

test_fiod
Pass
0
00:20:31

test_flent
Pass
0
00:07:13

test_fs_drift
Pass
0
00:04:30

test_hammerdb
Pass
0
00:03:54

test_iperf3
Pass
0
00:06:05

test_kubeburner
Pass
0
00:23:05

test_log_generator
Pass
0
00:02:48

test_pgbench
Pass
0
00:02:30

test_smallfile
Pass
0
00:04:49

test_stressng
Pass
0
00:01:45

test_sysbench
Pass
0
00:01:11

test_uperf
Pass
0
00:25:20

test_vegeta
Pass
0
00:04:30

test_ycsb
Pass
0
00:03:03

test_scale_openshift
Pass
0
00:08:11

/rerun all tests/test_image_pull.sh

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_image_pull
Fail
3
00:25:46

hm, @dry923

/rerun all tests/test_image_pull.sh

hm, @dry923

The branch I was working on didn't include the updated operator version. Needed to go in an update some vars. Re-testing it now.

/rerun all tests/test_image_pull.sh

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_image_pull
Pass
0
00:02:36


EFI installation using rEFInd

Issue description
I'm about to try nixos as my new is on my home machine.
Apparently the refind package is marked as broken. Is an installation of nixos in combination with refind still possible, or are there any plans to make it possible in the near future.
Cheers

Today I started exhibiting from https://github.com/systemd/systemd/issues/19191 and forced to boot my machine via efi shell. I would like to change the bootloader to refind, but I have the choice only between grub and systemd-boot. :(

For reference a pr is here

Guess we can close that.

Why?

Because its years old and installing refind is literally just applying it to the system and running refind-install.

It also really needs module to support the kernel command line specified in the system config. It could be worked around by UKI (I made a simple module creating UKIs for myself) but then each generation gets its own UKI and the spare space on /boot disappears really fast.
Would also be nice to have NixOS icon on NixOS entries :)

running refind-install

If you have to manually install it, I would not consider this issue to be done.
It should be installed automatically on switch or boot like other bootloaders.


flake-parts doesn't evaluate.

A small flake-parts file.
{
  description = "Developer environment for AquaTerra.";

  inputs = {
    nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";
    flake-parts.url = "github:hercules-ci/flake-parts";
    devshell.url = "github:numtide/devshell";
  };

  outputs = { self, nixpkgs, flake-parts, ... }@inputs:
    flake-parts.lib.mkFlake { inherit inputs; } {
      imports = [ inputs.devshell.flakeModule ];
      flake = { };
      systems = [ "x86_64-linux" ];
      perSystem = { config, pkgs, ... }: {
        devshells.default = {
          packages = with pkgs;[
            nodePackages.nodejs bun
            nodePackages.expo-cli
          ];
        };
      };
    };
}

evaluates to an error when evaluated by nix flake lock.
error:
       … while updating the lock file of flake 'git+file:///mnt/Shtuffs/home/Dev/CIT214?ref=refs/heads/master&rev=07846b815d21746b90ea517cef921d3f7e3aa7a1'

       … while updating the flake input 'flake-parts'

       error: getting status of '/nix/store/2hc9lg18zd6yabw9jqj0wy3s9kyvkzp0-source': No such file or directory

For some reason, flake-parts doesn't evaluate here. Also related to https://github.com/nix-community/nixvim/issues/1241, as the same nix store path is referenced in the error.

This is beyond flake-parts' control. Which version of Nix are you using?
Does it still happen after rm ~/.cache/nix/fetcher-cache*?

This is beyond flake-parts' control. Which version of Nix are you using? Does it still happen after rm ~/.cache/nix/fetcher-cache*?

I'm using a flake based configuration, and nix was just updated to the 2.18.1 version. Tried your solution, didn't work.


⚠ SceneTime has degraded performance

In a1bce0c, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 13170 ms

Resolved: SceneTime performance has improved in 71ba77b after 7 minutes.


Stencil: use unstable features for portability

Rather than exhaustively enumerating via OS use the unstable feature to detect if ObjC interop is enabled.  This allows building on Windows.
Unfortunately, the entire test suite does not pass on Windows, with path issues due to PathKit's handling of paths.

This lays the groundwork for enabling Windows support.

Hello @compnerd ,
thank you very much for your MR, it has given me a clue when I was investigating an issue with variable parsing under Linux for my Sourcery port: https://github.com/krzysztofzablocki/Sourcery/pull/1188.
I have created #342 which changes the order of checks, and makes it possible to have a subclass from NSObject till, but also to conform to DynamicMemberLookup protocol, thus giving manual control for KVC-emulation on non-Darwin platforms, maybe that would be of interest to you.

@compnerd can I assume that @art-divin's PR supersedes this one? I.e. is #if canImport(ObjectiveC) equivalent to #if _runtime(_ObjC)?
If it's not the case, please feel free to reopen this PR, or adding your comment in #342.

They are not equivalent - canImport does not speak to the runtime, it it simply indicates that a module with that name is available  I can simply provide a module named ObjectiveC and it will incorrectly assume to be true and fail to build.

I can't seem to find any mentions towards using _runtime(ObjC)…
Only found some discussions about windows+swift+objc, that referred to https://github.com/apple/swift/issues/56739 which in turn referred to hasAttribute(…). But there's no mention of what attributes are available 😞

Yeah, _runtime(ObjC) is pretty rarely used, I think that there may be a few uses of it in Foundation.  But documentation is unlikely to be found - it is an internal (and thus unstable) feature.  The Windows + Swift + ObjC is definitely one way that the use of canImport(ObjectiveC) would return true, but in that case, I expect the KVC to be available.
It is more that there is no guarantee that I do not simply create a module with the name ObjectiveC.  Something like adding a module.modulemap with the following should be sufficient to evaluate the branch to true but not provide KVC:
module ObjectiveC [system] { }

I get that it's theoretically possible to define a module called ObjectiveC, but is that something that people do on Swift in Windows (or other non-Darwin platforms)? Sounds a bit like a footgun.
I don't mind using the _runtime if there's a realistic case for it, otherwise we might just stick with canImport 🤷

Sure, sticking with that for now is probably okay.  I tend to try to be more proactively careful about the possibility.


Redesign media and flux logs?

Issue submitted because they take forever to load directly into MATLAB tables
(This issue copied from the master list at https://sites.google.com/a/bu.edu/segre-lab/projects/comets/comets-issues . It may have been resolved and left unmarked as such)

Would it be feasible to alter media logs by being able to designate only certain metabolites to be logged? I'm not sure what the common use case is, but in my particular case I'm only interested in 5/200

Hey Mike, Im going to look into it, Im also not very happy with the current format of these logs..

I did some changes in the branch format_outputs, basically simplifying both media and flux logs

The media logs now write, for each timepoint and cell, only the concentration of those metabolites that is !=0. This reduces a lot the size of the file.
The flux log, I did not change it much, I just removed the weird brackets around numbers.

I wanted to suggest that we remove all the different formating options for the logs in comets, and agree to a unique, as simple as possible, format for all the output files. This would simplify the code, and any analysis software can take a csv table for instance. I feel this is important so I want to know your opinions before merging anything or going into more deep modifications.
In the meantime, I hope  this quick fix saves you some time Mike.


FS Error whether running Next Dev or Next Prod

Everything was working fine last night, but today I am coming across these errors (both Mac and Windows).
Reinstalled all my node_modules, did not help.
ERROR  Failed to compile with 39 errors                                                                                6:32:32 PM
These modules were not found:

fs in ./~/next/dist/server/index.js, ./~/next/dist/server/config.js and 33 others
module in (webpack)/lib/NormalModule.js, ./~/babel-core/lib/helpers/resolve.js
readline in ./~/friendly-errors-webpack-plugin/src/output.js
net in ./~/debug/src/node.js

To install them, you can run: npm install --save fs module readline net
Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined.
You likely forgot to export your component from the file it's defined in. Check your code at index.js?entry:16.
{ Error: Cannot find module '~/exampaths-next/.next/build-stats.json'
at Function.Module._resolveFilename (module.js:470:15)
at Function.Module._load (module.js:418:25)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at new Server (~/exampaths-next/node_modules/next/dist/server/index.js:104:30)
at module.exports (~/exampaths-next/node_modules/next/dist/server/next.js:10:10)
at walkTree (~/exampaths-next/node_modules/react-apollo/src/server.ts:76:15)
at /mnt/c/Users/akaga/Documents/Github/exampaths-next/node_modules/react-apollo/src/server.ts:90:11
at forEachSingleChild (~/exampaths-next/node_modules/react/lib/ReactChildren.js:51:8)
at traverseAllChildrenImpl (~/exampaths-next/node_modules/react/lib/traverseAllChildren.js:77:5) code: 'MODULE_NOT_FOUND'
, queryErrors: [ [Circular] ] }
WAIT  Compiling...                                                                                6:34:16 PM
ERROR  Failed to compile with 39 errors                                                                                6:34:21 PM
These modules were not found:

fs in ./~/is-windows-bash/index.js, ./~/mz/fs.js and 33 others
module in (webpack)/lib/NormalModule.js, ./~/babel-core/lib/helpers/resolve.js
readline in ./~/friendly-errors-webpack-plugin/src/output.js
net in ./~/debug/src/node.js

To install them, you can run: npm install --save fs module readline net

This is the error appearing on localhost.
Cannot find module '/mnt/c/Users/akaga/Documents/Github/exampaths-next/.next/build-stats.json'
Error: Cannot find module '/mnt/c/Users/akaga/Documents/Github/exampaths-next/.next/build-stats.json'
at Function.Module._resolveFilename (module.js:470:15)
at Function.Module._load (module.js:418:25)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at new Server (/mnt/c/Users/akaga/Documents/Github/exampaths-next/node_modules/next/dist/server/index.js:104:30)
at module.exports (/mnt/c/Users/akaga/Documents/Github/exampaths-next/node_modules/next/dist/server/next.js:10:10)
at walkTree (/mnt/c/Users/akaga/Documents/Github/exampaths-next/node_modules/react-apollo/src/server.ts:76:15)
at /mnt/c/Users/akaga/Documents/Github/exampaths-next/node_modules/react-apollo/src/server.ts:90:11
at forEachSingleChild (/mnt/c/Users/akaga/Documents/Github/exampaths-next/node_modules/react/lib/ReactChildren.js:51:8)
at traverseAllChildrenImpl (/mnt/c/Users/akaga/Documents/Github/exampaths-next/node_modules/react/lib/traverseAllChildren.js:77:5)

Getting the same thing w/ v.7.9.0 & next @ 2.1.1 even in tiny examples (just pages/index.js and the deps, nothing else); any ideas why this would be happening? Also worth nothing: on OS X

Can you provide the exact steps to reproduce, and an example repository? It's really hard to debug otherwise 👍

facepalm — was importing a nonexistent preset "next" in my babelrc; hard error to track down, but def. my own doing lol

@akadop Hey, @dizlexik was reporting a similar issue where it happened when he had his server using distDir and was essentially running 2 versions of the app. Can you post an example simple project of this issue occuring?

Sorry for the late response. Turns out it was infact running 2 different versions of the app, although I do not know how that happened. There was no error indicating port 3000 was in use.
In any case, Thanks for all the help.

Not sure if I should reopen the issue since it may not be related to Next.js. The case is that when using Next.js with Minio.js, the following errors shown:
These modules were not found:

* fs in ./node_modules/mkdirp/index.js, ./node_modules/minio/dist/main/minio.js

To install it, you can run: npm install --save fs

I have made a very simple project to show how to reproduce this error.
If this issue isn't the concern of Next.js but Minio.js, I would be happy to just post the issue there. Thanks.


Asset Info Tip

Asset info tip (asset info & amount) disappears if panel is updated while tip is opened

Set wallet automatically locked after 1 m
Open info
Wait

checked


python.pkgs.sip: 4.19.6 -> 4.19.8

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

cc @lovek323 @svanderburg

@GrahamcOfBorg build python27Packages.sip python36Packages.sip

Success on x86_64-linux (full log)
Attempted: python27Packages.sip, python36Packages.sip
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/g1s0mfj3vvnrib3w4sjscp86agigq267-python3.6-sip-4.19.8
shrinking /nix/store/g1s0mfj3vvnrib3w4sjscp86agigq267-python3.6-sip-4.19.8/lib/python3.6/site-packages/sip.so
shrinking /nix/store/g1s0mfj3vvnrib3w4sjscp86agigq267-python3.6-sip-4.19.8/bin/sip
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/g1s0mfj3vvnrib3w4sjscp86agigq267-python3.6-sip-4.19.8/lib  /nix/store/g1s0mfj3vvnrib3w4sjscp86agigq267-python3.6-sip-4.19.8/bin
patching script interpreter paths in /nix/store/g1s0mfj3vvnrib3w4sjscp86agigq267-python3.6-sip-4.19.8
checking for references to /build in /nix/store/g1s0mfj3vvnrib3w4sjscp86agigq267-python3.6-sip-4.19.8...
/nix/store/xny6hz5x1ywv8c2hca8xm5d5gp1xwxpn-python2.7-sip-4.19.8
/nix/store/g1s0mfj3vvnrib3w4sjscp86agigq267-python3.6-sip-4.19.8

Success on aarch64-linux (full log)
Attempted: python27Packages.sip, python36Packages.sip
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/n3qwqc6v66czhkjxzih0whcwdxywfmv0-python3.6-sip-4.19.8
shrinking /nix/store/n3qwqc6v66czhkjxzih0whcwdxywfmv0-python3.6-sip-4.19.8/lib/python3.6/site-packages/sip.so
shrinking /nix/store/n3qwqc6v66czhkjxzih0whcwdxywfmv0-python3.6-sip-4.19.8/bin/sip
strip is /nix/store/0pjsgkxz0rp5baycq5sp2s72lrr5q9sg-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/n3qwqc6v66czhkjxzih0whcwdxywfmv0-python3.6-sip-4.19.8/lib  /nix/store/n3qwqc6v66czhkjxzih0whcwdxywfmv0-python3.6-sip-4.19.8/bin
patching script interpreter paths in /nix/store/n3qwqc6v66czhkjxzih0whcwdxywfmv0-python3.6-sip-4.19.8
checking for references to /build in /nix/store/n3qwqc6v66czhkjxzih0whcwdxywfmv0-python3.6-sip-4.19.8...
/nix/store/ayy33qrp654nwby2mwqps3hcgah79wp8-python2.7-sip-4.19.8
/nix/store/n3qwqc6v66czhkjxzih0whcwdxywfmv0-python3.6-sip-4.19.8

Success on x86_64-darwin (full log)
Attempted: python27Packages.sip, python36Packages.sip
Partial log (click to expand)
cp -f /private/tmp/nix-build-python3.6-sip-4.19.8.drv-0/sip-4.19.8/sip.pyi /nix/store/577myka64nnqpf78qm0j9czf83qjgix8-python3.6-sip-4.19.8/lib/python3.6/site-packages/sip.pyi
make[1]: Leaving directory '/private/tmp/nix-build-python3.6-sip-4.19.8.drv-0/sip-4.19.8/siplib'
cp -f sipconfig.py /nix/store/577myka64nnqpf78qm0j9czf83qjgix8-python3.6-sip-4.19.8/lib/python3.6/site-packages/sipconfig.py
cp -f /private/tmp/nix-build-python3.6-sip-4.19.8.drv-0/sip-4.19.8/sipdistutils.py /nix/store/577myka64nnqpf78qm0j9czf83qjgix8-python3.6-sip-4.19.8/lib/python3.6/site-packages/sipdistutils.py
post-installation fixup
strip is /nix/store/7ddbq63v97nk8gkbf7gcsfmby37h6gbl-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/577myka64nnqpf78qm0j9czf83qjgix8-python3.6-sip-4.19.8/lib  /nix/store/577myka64nnqpf78qm0j9czf83qjgix8-python3.6-sip-4.19.8/bin
patching script interpreter paths in /nix/store/577myka64nnqpf78qm0j9czf83qjgix8-python3.6-sip-4.19.8
/nix/store/vskwv9z94rbgk9sr6b1iqlbxl5agmmlp-python2.7-sip-4.19.8
/nix/store/577myka64nnqpf78qm0j9czf83qjgix8-python3.6-sip-4.19.8

Included in https://github.com/NixOS/nixpkgs/pull/43972.


Flutter WEB: UnimplementedError: addJavaScriptHandler is not implemented on the current platform

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
addJavaScriptHandler not working on Flutter Web
Expected Behavior
addJavaScriptHandler will work as intended
Steps with code example to reproduce
webViewController.addJavaScriptHandler(
handlerName: 'my.getAuthCode',
callback: (args) {
// Put code here
});
Stacktrace/Logs

Stacktrace/Logs
<Replace this line by pasting your stacktrace or logs here>

DartError: UnimplementedError: addJavaScriptHandler is not implemented on the current platform
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 297:3                                      throw_
packages/flutter_inappwebview_platform_interface/src/in_app_webview/platform_inappwebview_controller.dart 688:5  addJavaScriptHandler
packages/flutter_inappwebview/src/in_app_webview/in_app_webview_controller.dart 171:16                           addJavaScriptHandler
packages/hitachi_wma/feature/mobile_emulator/presentation/pages/wma_mobile.dart 77:27
packages/flutter_inappwebview/src/in_app_webview/in_app_webview.dart 314:54
packages/flutter_inappwebview_web/src/in_app_webview/in_app_webview.dart 323:26                                  [_onPlatformViewCreated]
packages/flutter_inappwebview_web/src/in_app_webview/in_app_webview.dart 304:9
packages/flutter/src/widgets/_html_element_view_web.dart 65:30
dart-sdk/lib/async/zone.dart 1661:54                                                                             runUnary
dart-sdk/lib/async/future_impl.dart 162:18                                                                       handleValue
dart-sdk/lib/async/future_impl.dart 838:44                                                                       handleValueCallback
dart-sdk/lib/async/future_impl.dart 867:13                                                                       _propagateToListeners
dart-sdk/lib/async/future_impl.dart 643:5                                                                        [_completeWithValue]
dart-sdk/lib/async/future_impl.dart 713:7                                                                        callback
dart-sdk/lib/async/schedule_microtask.dart 40:11                                                                 _microtaskLoop
dart-sdk/lib/async/schedule_microtask.dart 49:5                                                                  _startMicrotaskLoop
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 181:7
Flutter version
vr 3.19.5
Operating System, Device-specific and/or Tool
Chrome
Plugin version
v6.0.0
Additional information
No response
Self grab

[ ] I'm ready to work on this issue!

As the error says, it is not implemented on Web platform


Adapt the extension chart

How to categorize this PR?

/kind enhancement
What this PR does / why we need it:
This PR adapts the extension chart in the following aspects:

The extension resources and VPA settings are updated
The HA type of the extension is switched from controller to server as the extension serves a webhook now

Which issue(s) this PR fixes:
Part of #3
Special notes for your reviewer:
N/A
Release note:

NONE

/approve