The documentation shows this:
Process process = createProcess {
    command = "ls -l";
    path = home;
};

But trying it gives this:
java.io.IOException: Cannot run program "ls -l" (in directory "/home/sadmac/coding/ceylon/ceylon-llvm"): error=2, No such file or directory
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
        at ceylon.process.internal.ConcreteProcess.<init>(ConcreteProcess.ceylon:52)
        at ceylon.process.createProcess_.createProcess(Process.ceylon:95)
        at org.americanteeth.ceylon_llvm.LLVMCompilerTool.run(run.ceylon:137)
        at com.redhat.ceylon.common.tools.CeylonTool.run(CeylonTool.java:390)
        at com.redhat.ceylon.common.tools.CeylonTool.execute(CeylonTool.java:327)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
...

An strace reveals that the program is attempting to use the full "command" string as the path to the program, spaces and options and all.

shared Process createProcess(
         "The _command_ to be run in the new
         process, usually the name or path of a
         program. Command arguments must be passed
         via the [[arguments]] sequence."
        String command,
        "The arguments to the [[command]]."
        {String*} arguments = {},

I don’t see how this “lies” about parsing. Does some other documentation imply that it works like system(3)?

OIC:

     Process process = createProcess {
         command = \"ls -l\";
         path = home;
     };

from the module doc :(

three times :( :(

Also, while we're at it, arguments should probably be [String*] not {String*} since order is important.

good point.

I suppose List<String> would be sufficient to require ordering.

Yeah, List never gets proper consideration!
OTOH, for {} ordering, isn't that a concern of the caller? And they'll just do it.sequence() anyway.

And they'll just do it.sequence() anyway.

I think 99% of the time they’ll use [] literals instead of {} literals :)

Then those will be ordered correctly.

FYI : https://github.com/ceylon/ceylon-sdk/pull/382

#382 was merged, so this is done now, right?

I believe so
Sent from my iPhone

On 21 Jul 2015, at 18:44, Lucas Werkmeister<EMAIL_ADDRESS>wrote:
#382 was merged, so this is done now, right?
—
Reply to this email directly or view it on GitHub.

Indeed, closing.


Option to commit asynchronously in bulk import driver

Background
Split from:

https://github.com/gchq/sleeper/issues/2575

Follows on from:

https://github.com/gchq/sleeper/issues/2692

Description
We'd like BulkImportJobDriver to be able to add new files to the state store asynchronously, by sending a message to the state store committer.

Closing as duplicate


Chain proxy servers

How would one proxy send connections to a second proxy?

You should define the http.Transport inside proxy.Tr to use the second
proxy.
On Wed, May 18, 2016 at 6:43 PM, Drew Wells<EMAIL_ADDRESS>wrote:

How would one proxy send connections to a second proxy?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/elazarl/goproxy/issues/163

Inside transport.Dial() the http request has been unwrapped from the original HTTP connect. Are there some conveniences to create a proper HTTP connect to the upstream proxy?

Don't need dial
Something along the lines of
proxy.Tr = &http.Transport{Proxy:func(req *http.Request) { return

myproxy }}
https://golang.org/pkg/net/http/#Transport
On Wed, May 18, 2016 at 10:44 PM, Drew Wells<EMAIL_ADDRESS>wrote:

Inside transport.Dial() the http request has been unwrapped from the
original HTTP connect. Are there some conveniences to create a proper HTTP
connect to the upstream proxy?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/elazarl/goproxy/issues/163#issuecomment-220136612

hmm, I got it working with Dial. I'll try this approach too
	remoteaddr := c.Remote
	u, err := url.Parse(remoteaddr)
	if err != nil {
		log.Fatal("failed to parse upstream server:", err)
	}
	fmt.Println("upstream server", remoteaddr)

	dial := func(network, addr string) (net.Conn, error) {
		// Prevent upstream proxy from being re-directed
		if u.Host == addr {
			return net.Dial(network, addr)
		}
		fmt.Println("tr... dial", addr)
		dialer := svr.NewConnectDialToProxy(remoteaddr)
		if dialer == nil {
			panic("nil dialer, invalid uri?")
		}
		return dialer(network, addr)
	}

	svr.Tr = &http.Transport{
		Dial:    dial,
		DialTLS: dial,
	}

	log.Fatal(http.ListenAndServe(c.Listen, svr))

tr.Proxy doesn't appear to intercept calls made via ssh
Host serverInsideVPN
    ProxyCommand corkscrew localhost 7800 %h %p

This does work with a straight ProxyServer not using a custom transport

I added this dialer to catch ssh requests which seems to work well enough. Dialers receive only a host address, so it creates a URL compatible with what is expected inside proxy for a rules(config{}, *url.URL)
	dial := func(network, addr string) (net.Conn, error) {
		u := &url.URL{Host: addr}
		// non-HTTP traffic seems to not use proxy, check again here
		// ensuring we aren't preventing access to the remote address
		if !rules(c, u) {
			return net.Dial(network, addr)
		}
		fmt.Println("dialer caught...", addr)
		return svr.NewConnectDialToProxy(remoteaddr)(network, addr)
	}

It seems that chaining proxies causes some weird IO hanging.

This implementation is working for me:
func startProxy(addr string) {
	proxy := goproxy.NewProxyHttpServer()

	proxy.Tr = &http.Transport{Proxy: func(req *http.Request) (*url.URL, error) {
		return url.Parse("http://<NEXT_FORWARD_PROXY_HOST>:<NEXT_FORWARD_PROXY_PORT>")
	}}
	proxy.ConnectDial = proxy.NewConnectDialToProxy("http://<NEXT_FORWARD_PROXY_HOST>:<NEXT_FORWARD_PROXY_PORT>")

	http.ListenAndServe(addr, proxy)
}

Thanks @alexelisenko , can I close the issue?


:tada: streamlit app for etl-staging-sync

UI for command etl-staging-sync for migrating charts from staging servers to production.
It will be run on owid@etl-prod-2 together with fast-track (on a different port), and there'll be a link to it from admin.
The current version needs active staging server to sync charts from there, and the branch must be merged in ETL. I've increased the time for killing staging servers from 1 day to 3 days after merging.
Last time, we talked about snapshotting the staging server somewhere so that we can kill the server right away and reconstruct updated charts from the snapshot. I gave it a try, and it turned out to be unnecessarily complicated. Moreover, having an active staging server when syncing charts could be useful (e.g. if you realise you still have to make some chart edits there or if you find that the chart has been updated on live and you want to make the same changes on your staging before syncing the chart).
The streamlit app is very basic, though one think that's pretty cool is _run_command that runs a CLI command and shows its output (with colours!) as HTML in the app.
I haven't used streamlit for a while, so any tips are welcome!
How to test it

poetry install
etl-staging-sync-app
Use source gho and target etl-staging-sync-app (I've updated two charts)
Follow instructions (feel free to do anything to both staging servers)

Using terms "target", "live", "production"

You're totally right. I changed it to source and target with clarification of what they typically refer to. I have this problem in other places too, it might make sense to clean it up at one point.

Integrating it with etl-wizard

That was surprisingly easy!


createSFCModule not exported

Describe the bug
The examples show that we can use createSFCModule, however I'm only able to use loadModule.
To Reproduce
Steps to reproduce the behavior:

Add the latest vue3-sfc-loader to the .
Add a script tag with const { createSFCModule } = window["vue3-sfc-loader"];
Try to use the function.
See the error (createSFCModule is undefined):
Uncaught TypeError: createSFCModule is not a function

Expected behavior
createSFCModule should create a new component from a single file component source string.
Desktop (please complete the following information):

OS: Manjaro Linux
Browser: Firefox
Version: 83

My bad, the example is out of date, use this meanwhile : https://codepen.io/franckfreiburger/project/editor/AqPyBr

Is it possible to parse template source code that's inside a variable? Because I'd need this for my project.

https://github.com/FranckFreiburger/vue3-sfc-loader#using-another-template-language-pug show you how to define your own getFile()

Oh I see, thank you! I think I will create a dictionary with the sources then.

I'm having the following issue when trying this with the code below:
const { loadModule } = window["vue3-sfc-loader"];

const TestTextComponent = Vue.defineAsyncComponent(() => loadModule("TestTextComponent.vue", {
    moduleCache: {
        vue: Vue,
    },
    getFile() {
        return Promise.resolve(`
            <template>

[[ msg ]]

            </template>

` /*-->*/ )
    },
}))

I agree that the error message is not clear ;)
options.addStyle() is not optional

I agree that the error message is not clear ;)
options.addStyle() is not optional

Ah thanks, can you correct this example or make it optional? https://github.com/FranckFreiburger/vue3-sfc-loader#using-another-template-language-pug.

In order to avoid new issues like "my styles do not work" I will definitively keep addStyle() mandatory but the error will be clearer.
BTW, you can define addStyle with () => {}


Removing private SSH key

I noticed you had commited a private ssh key to your repo.
"I know. It was intentional."
Sorry to bother you then. Feel free to ignore this PR.
You know you can also secure private data while keeping it under source control.
"I didn't notice. What is this file? Is it a problem?"
This can be a very bad thing
"I keep accidentally typing git add ., any way I can prevent that from being an issue?"
There are a couple of steps you should take immediately:

Avoid commands like git add . and git add *. It's better to be more explicit when you can.
Assume your key is compromised. Unassociate it from any accounts you are using it for and generate a new key.
Store your keys in a location outside of your project.
Use a .gitignore file to prevent accidental commits of certain files.

Github also has a page about how to remove sensitive data from a repo.
Hope this PR finds you well

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

...... I thought I went through the travis encrypt file process.
Luckily, following decent practice, this key is only keyed as a deploy key for this repository. I've removed it, so (RIP Travis builds, all going to fail now) there is no further risk; the key has been neutralized.
For the life of me, I was unable to get the Travis encryption working. Apparently the reason it started working was that I disabled it? Somehow? Even though Travis was decrypting it?
https://github.com/nafi-lang/rust-nafi/blob/e4e7ec044a49996b02ef0555590ce1210b2cd6de/.travis.yml#L4
Basically, Travis needs a way to write to the repository such that it can update the gh-pages branch with up-to-date generated documentation. Hopefully I can go through the process of encrypting the private key properly this time. It's unfortunate that the automatic way didn't work for me on Windows even though I tried multiple times.

CLA not required; removal only
Travis is going to fail because it's removing a required key
I'll get to fixing it this weekend hopefully

(In hindsight, it may have been better to commit 30e7e0430ffc1eafbe10a1324b884c03a63a37b4 and then merge via bors... but oh well.)

glad I could help!

Noting this here so when I have this same problem again I might solve it faster. It took me a while longer than expected (life got in the way) but...
I got motivated to work on this again, and got the encryption right this time. https://github.com/nafi-lang/rust-nafi/blob/master/.travis/id_rsa.enc is actually an encrypted binary blob, and docs are auto-building to https://nafi-lang.github.io/rust-nafi/ again.
https://github.com/travis-ci/travis-ci/issues/4746 describes the issue on Windows. Unfortunately, since it's been around for two years, I don't think it's getting fixed anytime soon. Luckily, I stumbled across https://github.com/travis-ci/travis-ci/issues/8777 which allowed me to manually encrypt the file correctly this time.


This matches spec behaviour: http://w3c.github.io/web-animations/#dom-animationeffecttiming-easing
This change depends on #423 merging first.

Closing in favour of #426.


Does not appear to pulling data.

I just install the integration today and this is what I'm getting in my error log.

Here is my device setting

I've just pushed a fix.
Please update and verify if it works now.

It appears the calculation is off. It's like it's times it 100

and i think it needs to / by 100

Everything looks correct: 149.242 (100 GAL) is equal to 14924.2 (GAL).
Home assistant does not understand "100 GAL" measurement unit, I think EOW invention :-)

I summited a PR that fix the issue on my side. I don't believe there needs to be any math involved. The meter that is install is brand new and I'm sure there not 14,000 gallons though it

I don't mind to approve the PR if everything works for you and I see your point.
But I think that the problem is in the EOW side: they report the measurement unit is "100 GAL".
Could you please double check that the numbers on your meter are in gallons and not in hundreds of gallons?

@andrewchumchal  The simplest way to check it - take a look at your daily water consumption.

I just fixed it. Please update once again.
And thank you for reporting the issue

Thanks so much for this integration. I almost have it working. Sorry I can’t help you on issue #2. I have a very similar error to the one described above with the exception the unit CCF.
Traceback (most recent call last):   File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 182, in async_refresh     await self._async_refresh(log_failures=True)   File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 283, in _async_refresh     self.async_update_listeners()   File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 110, in async_update_listeners     update_callback()   File "/config/custom_components/eyeonwater/sensor.py", line 85, in _state_update     self._state = self.meter.reading   File "/config/custom_components/eyeonwater/eow.py", line 152, in reading     raise EyeOnWaterAPIError(f"Unsupported measurement unit: {read_unit}") custom_components.eyeonwater.eow.EyeOnWaterAPIError: Unsupported measurement unit: CCF

@caliKev I've just added support for CCF, it will be converted to gallons.
Please update and verify.

@kdeyev Thanks so much for the quick fix. The sensor has a value now. My system only uploads one reading daily, hopefully energy meter starts working once there is a second reading.


Missing arguments in results

Fixing the 2024.01 DStability missing result fields
Note; there is also another branch fixing the same issue, my code is a little more 'complicated', you choose :-)
other solution / PR: https://github.com/Deltares/GEOLib/pull/163

Fixed in GEOLib v2.3.0 with a similar approach as in pr 163


nrf52_blenano2 tmp112 sensor sample build failed.

Hi,
Trying to build a samples/sensor/tmp112/ on the custom board (similar to the nrf52_blenano2).
But seems some definitions for i2c bus are missed :(
cmake -GNinja -DBOARD=nrf52_blenano2 ..
ninja
...
-- Generating zephyr/include/generated/generated_dts_board.h
-- Cache files will be written to: /home/axel/.cache/zephyr
-- Configuring done
-- Generating done
-- Build files have been written to: /home/axel/nrf52/tmp112/build
[100/133] Building C object zephyr/drivers/i2c/CMakeFiles/drivers__i2c.dir/i2c_nrf5.c.obj
FAILED: ccache /home/axel/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-gcc -DKERNEL -DNRF52832_XXAA -D_FORTIFY_SOURCE=2 -D__ZEPHYR_SUPERVISOR__ -D__ZEPHYR__=1 -I/home/axel/zephyr-current/kernel/include -I/home/axel/zephyr-current/arch/arm/include -I/home/axel/zephyr-current/arch/arm/soc/nordic_nrf/nrf52 -I/home/axel/zephyr-current/arch/arm/soc/nordic_nrf/nrf52/include -I/home/axel/zephyr-current/arch/arm/soc/nordic_nrf/include -I/home/axel/zephyr-current/boards/arm/nrf52_blenano2 -I/home/axel/zephyr-current/include -I/home/axel/zephyr-current/include/drivers -Izephyr/include/generated -isystem /home/axel/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/lib/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/include -isystem /home/axel/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/lib/arm-zephyr-eabi/gcc/arm-zephyr-eabi/6.2.0/include-fixed -I/home/axel/zephyr-current/lib/libc/minimal/include -I/home/axel/zephyr-current/ext/hal/cmsis/Include -I/home/axel/zephyr-current/ext/hal/nordic/nrfx -I/home/axel/zephyr-current/ext/hal/nordic/nrfx/drivers/include -I/home/axel/zephyr-current/ext/hal/nordic/nrfx/hal -I/home/axel/zephyr-current/ext/hal/nordic/nrfx/mdk -I/home/axel/zephyr-current/ext/hal/nordic/. -I/home/axel/zephyr-current/subsys/bluetooth -Os -g -Wall -Wformat -Wformat-security -Wno-format-zero-length -imacros /home/axel/nrf52/tmp112/build/zephyr/include/generated/autoconf.h -ffreestanding -Wno-main --sysroot /home/axel/zephyr-sdk/sysroots/armv5-zephyr-eabi/usr -mthumb -mcpu=cortex-m4 -std=c99 -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-strict-overflow -Wno-pointer-sign -Wno-unused-but-set-variable -fno-reorder-functions -fno-defer-pop -Werror=implicit-int -ffunction-sections -fdata-sections -mabi=aapcs -march=armv7e-m -MD -MT zephyr/drivers/i2c/CMakeFiles/drivers__i2c.dir/i2c_nrf5.c.obj -MF zephyr/drivers/i2c/CMakeFiles/drivers__i2c.dir/i2c_nrf5.c.obj.d -o zephyr/drivers/i2c/CMakeFiles/drivers__i2c.dir/i2c_nrf5.c.obj   -c /home/axel/zephyr-current/drivers/i2c/i2c_nrf5.c
/home/axel/zephyr-current/drivers/i2c/i2c_nrf5.c:349:35: error: ‘NORDIC_NRF5_I2C_40003000_BASE_ADDRESS’ undeclared here (not in a function)
  .base = (volatile NRF_TWI_Type *)CONFIG_I2C_0_BASE_ADDR,
                                   ^~~~~~~~~~~~~~~~~~~~~~~
/home/axel/zephyr-current/drivers/i2c/i2c_nrf5.c:351:13: error: ‘NORDIC_NRF5_I2C_40003000_CLOCK_FREQUENCY’ undeclared here (not in a function)
  .bitrate = CONFIG_I2C_0_BITRATE,
             ^~~~~~~~~~~~~~~~~~~~~
/home/axel/zephyr-current/drivers/i2c/i2c_nrf5.c:360:135: error: ‘NORDIC_NRF5_I2C_40003000_LABEL’ undeclared here (not in a function)
 DEVICE_AND_API_INIT(i2c_nrf5_0, CONFIG_I2C_0_NAME, i2c_nrf5_init,
                                                                                ^
/home/axel/zephyr-current/drivers/i2c/i2c_nrf5.c: In function ‘i2c_nrf5_config_func_0’:
/home/axel/zephyr-current/drivers/i2c/i2c_nrf5.c:367:130: error: ‘NORDIC_NRF5_I2C_40003000_IRQ_0’ undeclared (first use in this function)
  IRQ_CONNECT(CONFIG_I2C_0_IRQ, CONFIG_I2C_0_IRQ_PRI, i2c_nrf5_isr,
                                                                                ^
/home/axel/zephyr-current/drivers/i2c/i2c_nrf5.c:367:130: note: each undeclared identifier is reported only once for each function it appears in
/home/axel/zephyr-current/drivers/i2c/i2c_nrf5.c:367:265: error: ‘NORDIC_NRF5_I2C_40003000_IRQ_0_PRIORITY’ undeclared (first use in this function)
  IRQ_CONNECT(CONFIG_I2C_0_IRQ, CONFIG_I2C_0_IRQ_PRI, i2c_nrf5_isr,
                                                                                ^
[100/133] Building C object zephyr/drivers/serial/CMakeFiles/drivers__serial.dir/uart_nrfx_uart.c.obj
ninja: build stopped: subcommand failed.
...

Just tested again,
Now we have a double definitions :(
[2/114] Building C object zephyr/CMakeFiles/zephyr.dir/ext/hal/nordic/nrfx/drivers/src/nrfx_twim.c.obj
[3/114] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/random/rand32_entropy_device.c.obj
[4/114] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/clock_control/nrf5_power_clock.c.obj
[5/114] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/console/uart_console.c.obj
[6/114] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/timer/sys_clock_init.c.obj
In file included from /home/axel/zephyr-current/include/arch/arm/arch.h:20:0,
                 from /home/axel/zephyr-current/include/arch/cpu.h:15,
                 from /home/axel/zephyr-current/include/kernel.h:36,
                 from /home/axel/zephyr-current/subsys/random/rand32_entropy_device.c:8:
zephyr/include/generated/generated_dts_board.h:127:0: warning: "CONFIG_I2C_0_NAME" redefined
 #define CONFIG_I2C_0_NAME  NORDIC_NRF5_I2C_40003000_LABEL

In file included from <command-line>:0:0:
/home/axel/nrf52/tmp112/build/zephyr/include/generated/autoconf.h:187:0: note: this is the location of the previous defin
ition
 #define CONFIG_I2C_0_NAME "I2C_0"

In file included from /home/axel/zephyr-current/include/arch/arm/arch.h:20:0,
                 from /home/axel/zephyr-current/include/arch/cpu.h:15,
                 from /home/axel/zephyr-current/include/kernel.h:36,
                 from /home/axel/zephyr-current/subsys/random/rand32_entropy_device.c:8:
zephyr/include/generated/generated_dts_board.h:129:0: warning: "CONFIG_I2C_0_IRQ_PRI" redefined
 #define CONFIG_I2C_0_IRQ_PRI  NORDIC_NRF5_I2C_40003000_IRQ_0_PRIORITY

In file included from <command-line>:0:0:
/home/axel/nrf52/tmp112/build/zephyr/include/generated/autoconf.h:189:0: note: this is the location of the previous defin
ition
 #define CONFIG_I2C_0_IRQ_PRI

[7/114] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/timer/nrf_rtc_timer.c.obj
In file included from /home/axel/zephyr-current/include/arch/arm/arch.h:20:0,
                 from /home/axel/zephyr-current/include/arch/cpu.h:15,
                 from /home/axel/zephyr-current/include/kernel.h:36,
                 from /home/axel/zephyr-current/drivers/console/uart_console.c:16:
zephyr/include/generated/generated_dts_board.h:127:0: warning: "CONFIG_I2C_0_NAME" redefined
 #define CONFIG_I2C_0_NAME  NORDIC_NRF5_I2C_40003000_LABEL


typescript: Make the typescript signatures more specific to their module

Made a few changes to the Typescript Indexer so it's easier to index code across different modules:

Module signatures are now the module name instead of the word module.
Anchor signatures now include the file path instead of just having the offsets
Symbol signatures now include their module
Module names are now relative to KYTHE_ROOT_DIRECTORY
Corpus is now set to KYTHE_CORPUS

Anchor signatures now include the file path instead of just having the offsets
This is unnecessary; the anchor VName already includes the file path.  Putting it in the signature is redundant (and potentially confusing to humans).

Cleaning up old PRs, feel free to re-open and address the comments if this is still relevant.


GUI Border for Furnace, Blast Furnace, and Smoker creates visual impairments on the labels inputted by the game

In the gui screen for furnace, blast furnace, and smoker, the game inputs words acknowledging the block utilized and inventory. The added border for block distinction creates visual impairments

Reverted the gui texture back to pack previous version.


Clarifying Question: Does this support DQL?

(This is not a Feature Request, so much as just a clarifying question.)
I understand that the plugin supports the dv object from Dataview.
Does obsidian-run support DQL, the Dataview Query Language?
For example does it support inline syntax:
`= this.file.name`

Or query syntax:
LIST
FROM "My Folder"

If not would it be possible to add support for this to obsidian-run?
Do you know if the dv object allows you to run DQL queries?

Yes. dv has an evaluate function. I am sure it works because I am using it.

I see thanks for the quick reply. I'd like to experiment and see if there's a way I might be able to simplify the syntax for obsidian-run
Perhaps this is already possible. (If so, it should be added to the README).
I would like to wrap run start around already existing dataview queries rather than being forced to dip into the ts syntax.
For example if I write
```dataview
TABLE
FROM "1. PARA/🏠Areas/✅RESPONSIBILITIES"
	OR [[#]]
WHERE file.name != "✅RESPONSIBILITIES"

I'd like to wrap it in:
%% run start
```dataview
TABLE
FROM "1. PARA/🏠Areas/✅RESPONSIBILITIES"
	OR [[#]]
WHERE file.name != "✅RESPONSIBILITIES"
%%

Btw, thank you for making this really cool plugin. I'm currently working on using Obsidian as a static site generator using Quartz. Unfortunately Quartz is not compatible with Dataview (and they don't have plans to add that compatibility because Dataview isn't currently maintained). So your plugin seems like it could be a really good solution.

Sorry.  I should give you an example. I completely forget that I put it in my obsidian publish.
https://yomaru.dev/700+Knowledge/Run
const query = `
TABLE dateformat(file.mtime, "dd.MM.yyyy - HH:mm") AS "Last modified"
FROM !"node_modules"
SORT file.mtime DESC LIMIT 100`

return dv.tryQueryMarkdown(query)

Ok thank you so much. That answers my question. However, perhaps you might consider a feature to obsidian-run so that it automatically places the query into tryQueryMarkdown(). That way you could enable a syntax like this:
```dvrun
TABLE dateformat(file.mtime, "dd.MM.yyyy - HH:mm") AS "Last modified"
FROM !"node_modules"
SORT file.mtime DESC LIMIT 100
\```

(The slash is just there so that GitHub doesn't hide the syntax, but you get the idea.)
Then, users could take a plain dataview query (which they might have many) and they just change it to dvrun. Then it should behave just like before except now it's being run through obsidian-run

I don't think I will do it. Although it is easy, it is not the intention of obsidian run. Obsidian is a powerful generic JavaScript evaluator. I think it is a good idea to make a dv helper to favour many obsidian users. But in the end of the day, DQL is not JavaScript and it not is a standard query language and it is going obsolete. I don't want to make obsidian run look any more related to dataview.
In the future, when obsidian support the database feature, most of the obsidian run-dv use case will go obsolete because dataview is going obsolete.
Now the code is clean, the query is clear and I allow all flexibility and compatibility. It is good enough. Less is more.


Fix support for Django 4.0 and update test matrix

This PR supersedes #72, commits retained because the original author deserves the attribution. Thanks for setting this in motion @AetherUnbound!
This PR updates the django-bakery dependency to 0.13.1 which includes support for Django 4.0. This means there is nothing holding us back anymore from supporting Django 4.0 and higher.
I've fixed the remaining compatibility issues with Django 4 and updated the testing matrix to the latest supported Django / Python / Wagtail versions.
Notably, this PR drops support for:

Django 2.2, 3.0 and 3.1
Wagtail 2.14 and older
Python 3.6 and 3.7 (3.7 is quite old and not supported by Django 4.1)

Support for the following Django / Python / Wagtail versions has been added:

Wagtail 2.15 LTS; v4.0 and the upcoming v4.1 LTS release.

v3.0 is not explicitly supported because it is near end of support but should probably work.

Django 4.0 and 4.1
Python 3.10

All tests pass for me locally but I have not given this a test drive in a real project. We should verify everything still works as expected before making a new release.

Thanks so much @Stormheg! 😄 Is there any chance you could publish a release candidate for this? I'd love to test it out on the site I help run to see if it works before a full version release 🙂

Hi @AetherUnbound, I'd like to get a sanity-check / review from another core team member in first before publishing a release candidate.
If you want to, you could start testing this right now from my branch. Just pip install git+https://github.com/Stormheg/wagtail-bakery.git@chore/django-4x-compat.
Keen to hear about any issues you might encounter!

Tested this on our project, the build command we use for testing didn't raise any errors! https://github.com/pycascades/pycascades-cms/actions/runs/3302171649/jobs/5448653445

Thanks for the review @zerolab 🙏
@AetherUnbound great to hear you are not encountering any issues!
There are some things in #74 I'd like to see in to the next release. Mostly some readme changes and a few setup.py tweaks that are visible on PyPI. Without committing to a timeline, you can expect a release 'soon'.

@AetherUnbound this is now released in 0.6.0!

Incredible, thank you!


1.2.0 uncraftable lightwell

Luminous crafting table don't recognize lightwell recipes

This is because of the missing research. Either claim the quest, which unlocks it for you, or craft the altar under the floating crystal


Oxa/master.fic --> oxa/devfic for oxa-tools

What's this PR do? Any additional context?
Simply merging a change thats's in our master (oxa/master.fic) down to our development branch (oxa/devfic)
Where should the reviewer start?
See original changes
How can this be manually tested? (brief repro steps)
See original changes
What are the relevant TFS items? (list id numbers)
See original changes
Definition of done:

[x] Title of the pull request is clear and informative
[ ] Add pull request hyperlink to relevant TFS items
[x] For large or complex change: schedule an in-person review session

Reminders BEFORE merging

Get at least two approvals
If you're merging into the development branch then "flatten" or "squash" commits
If merging from development into master then don't "flatten" or "squash" commits

Reminders AFTER merging

Delete the remote branch
Resolve relevant TFS items
(reverse merge) If you merged into master then check to see if there are any changes in master that can be merged down to the development branch (like hotfixes, etc)

@eltoncarr , you authored the original change so i won't merge until you approve.


WIP: Expand ironic serialiser

Coverage increased (+0.07%) to 99.814% when pulling bcf8ee3ecf4ab0b2512b22d44a4e2492b008dcdd on CyberiaResurrection:ExpandIronicSerialiser into 2a5ec20431cbf5f81285bd9364108bef612b5490 on Algo-Web:master.

Coverage increased (+0.07%) to 99.816% when pulling 36b8577ed012d9310b10a38f2d3609611c03c7bd on CyberiaResurrection:ExpandIronicSerialiser into 2a5ec20431cbf5f81285bd9364108bef612b5490 on Algo-Web:master.

Coverage increased (+0.07%) to 99.818% when pulling 3531fea80bf520d4be2d82c97b048c7956bc2af6 on CyberiaResurrection:ExpandIronicSerialiser into 2a5ec20431cbf5f81285bd9364108bef612b5490 on Algo-Web:master.

Coverage increased (+0.07%) to 99.818% when pulling 3531fea80bf520d4be2d82c97b048c7956bc2af6 on CyberiaResurrection:ExpandIronicSerialiser into 2a5ec20431cbf5f81285bd9364108bef612b5490 on Algo-Web:master.

Coverage increased (+0.07%) to 99.819% when pulling 229b2d36b152e5058043e93ae9d52e0142e42f73 on CyberiaResurrection:ExpandIronicSerialiser into 2a5ec20431cbf5f81285bd9364108bef612b5490 on Algo-Web:master.

Coverage increased (+0.07%) to 99.819% when pulling 229b2d36b152e5058043e93ae9d52e0142e42f73 on CyberiaResurrection:ExpandIronicSerialiser into 2a5ec20431cbf5f81285bd9364108bef612b5490 on Algo-Web:master.

Coverage increased (+0.07%) to 99.819% when pulling 229b2d36b152e5058043e93ae9d52e0142e42f73 on CyberiaResurrection:ExpandIronicSerialiser into 2a5ec20431cbf5f81285bd9364108bef612b5490 on Algo-Web:master.

Coverage increased (+0.07%) to 99.819% when pulling efe29fe3abc64d9a84be462f9243cbd000d60269 on CyberiaResurrection:ExpandIronicSerialiser into 2a5ec20431cbf5f81285bd9364108bef612b5490 on Algo-Web:master.


Create versioning for specific tools using docusarus standard versioning

https://docusaurus.io/docs/versioning

I looked at out old versioning to understand everything again and it should be possible to just reuse it. I also don't see any drawbacks with that.
We only need to be aware of docusaurus v3 routing which now implements their routing properly as described in the specs, but as it didn't in v2 we need to change the redirecting to the main version. Will look into that next sprint


Height is way off

It seems the chart code does not respect the height of the container element (no idea why such a fundamental thing doesn't work).
https://jsbin.com/lipususega/edit?css,js,output
Any idea how to make the graphs just fit in their container? especially the negative one is really weird. they must fit in the container, which has fixed height in this example.

I see by manually calculating high and low options, things appear a bit better

I thought height was defined with height: 100 - not a string and without the pxpart, but it seems to work though. Maybe that's the way to support other units. But back to the problem you reported, I think it's the nature of SVGs to be sized without considering the parent element, so if you drop the inline height: 75px everything works.

I repeat, height setting does not work in in Firefox, no matter what you do. and I will not drop off the CSS height to the container, that is the design demand and that demo link is a super simplified page of the actual design, so if the API says height does something and in reality it does not, that is a bug

@yairEO There are couple of issues here with your Chart. First of all, if you'd like to hide the X-Axis labels you should use the appropriate configuration showLabel set to false on the axisX. Returning an empty string for labels to be skipped but gridlines to be drawn is a workaround where there shouldn't really be one.
Secondly there are a couple of things to configure if you'd want to get rid of the whole spacing Chartist applies to your charts.
The most obvious one is chartPadding as a global settings. There is also an offset configuration on the given axis that is preconfigured to fit regular text size labels. This value can be changed to something higher if the labels use a very big font.
Here's an example: http://jsbin.com/lujaro/edit?html,css,js,output
There are a couple of possible changes I would see as an option.

Setting showLabel to false could also explicitly set offset of the same axis to 0
axis offset and chartPadding are somewhat interrelated and I know it feels a bit redundant, however, it's important as start point of the labels should probably not be the container border but respect some padding that can be configured.
Automatically calculate label width / height and reserve necessary space. This was done already in earlier Chartist versions and I just consider this very harmful as it involves rendering and measuring just for the purpose of automatically adjust their width / height. This causes reflow which we can't really use on mobile specially. There was also an issue where it was recommended as optional setting but that never made it though.

@gionkunz - but what about the bug?

The offset setting is described in the default options hidden under the show code button ;-)

Which demo? The example I just provided looks the same in both browsers:

well, I was referring to the bug I was reporting, so the demo link is the one with the bug report setup.

what do you mean reflow? how much are we talking about here? i thought it only reflows when the browser window is re sizing. else, the measuring is only done once no?

@yairEO http://mir.aculo.us/2010/08/17/when-does-javascript-trigger-reflows-and-rendering/

@gionkunz - http://www.vocabulary.com/dictionary/condescending
please, no condescending, lets keep this normal

Sorry?

Automatically calculate label width / height and reserve necessary space. This was done already in earlier Chartist versions and I just consider this very harmful as it involves rendering and measuring just for the purpose of automatically adjust their width / height. This causes reflow which we can't really use on mobile specially. There was also an issue where it was recommended as optional setting but that never made it though.

what EXACTLY took so many reflows? how many reflows? when did they occur? I can help you guys if you would share information instead of posting weird links about basic DOM things..

I was referencing to an article of Thomas Fuchs from 2010 about reflow triggered by measuring only. If you feel I was acting condescending, then I'm very sorry that was definitely not my intention :-)
I just tested in a very isolated example that setting a height in FF 40 in px is not working as expected. I'll need to debug this first.

Thank you :) that was the bug I was issuing...the height property doesn't work on FF (doesn't matter with px or not)

If opened this bug #448 for tracking this issue with a little bit less noise, the example is reduced to the minimum to reproduce the issue.


Error in exchange waterbalance coupler Ribasim-MF-MS

After the refactor in waterbalance error #1808 test in coupler are giving unexpected results. Could be related to the changes in how fluxes are integrated on Ribasim side.
Possibly the same as #1851.

@rleander made a reproducer in Python that I translated into Julia so I can directly test changes in the core. Here it is: https://gist.github.com/visr/78a864974619f9d445a3a0e1226310b0. It outputs figures like the following:

These lines should both stay at 0 and 25 where they start. The error gets worse over time. Resetting the cumulatives like in https://github.com/Deltares/Ribasim/pull/1864 seems to help. But then how often should we do this and who should do this in BMI context? It is probably not a real solution, just like how forcing smaller timesteps or lower tolerances also helps reduce the problem.
Changing the solver algorithm to Rodas5P does seem to help, showing no divergence even if I run the bucket model for 30.000 days, hence #1869.

It seems like the cumulative flow states are difficult for some algorithms. Though I also wouldn't rule out that we can do more in the core to alleviate this.

This is with QNDF, only changing the reltol from 1e-5 to 1e-7. PR to make that the default incoming.

Is this without or without resetting to 0?
It kinda seems like it's showing growing oscillations:

With https://github.com/Deltares/Ribasim/pull/1912 divergence is very slow (I subtracted 25 from the bottom plot):


Got "Application has been already initialized." when deploying to Heroku

Hi,
I installed ember-1cli-rails v0.1.13 into my existing Rails 3.2.18 project. It works fine on local host. But when i deployed to Heroku i got the error Application has been already initialized.:
Below is the log when deploying to Heroku. I tried to turn off the command MyApp::Application.initialize! in config/environment.rb but the app crashed on Heroku although it deployed successfully. Do you have any clue why it is and how can i resolve it?
-----> Fetching custom git buildpack... done
-----> Multipack app detected
=====> Downloading Buildpack: https://github.com/heroku/heroku-buildpack-nodejs
=====> Detected Framework: Node.js

-----> Reading application state
       package.json...
       build directory...
       cache directory...
       environment variables...

       Node engine:         unspecified
       Npm engine:          unspecified
       Start mechanism:     Procfile
       node_modules source: package.json
       node_modules cached: true
                                                                                [473/1934]
       NPM_CONFIG_PRODUCTION=true
       NODE_MODULES_CACHE=true

-----> Installing binaries
       Resolving node version (latest stable) via semver.io...
       Downloading and installing node 0.12.0...
       Using default npm version: 2.5.1

-----> Building dependencies
       Restoring node modules from cache
       Pruning unused dependencies
       npm WARN package.json @ No repository field.
       valid
       Installing node modules
       npm WARN package.json @ No repository field.

-----> Checking startup method
       Found Procfile

-----> Finalizing build
       Creating runtime environment
       Exporting binary paths
       Cleaning npm artifacts
       Cleaning previous cache
       Caching results for future builds

-----> Build succeeded!

       @ /tmp/build_8236fbf22ea851f11d6bc9907fbd15eb
       └──<EMAIL_ADDRESS>
       WARNING: Node version not specified in package.json
       https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version

=====> Downloading Buildpack: https://github.com/heroku/heroku-buildpack-ruby
=====> Detected Framework: Ruby
-----> Compiling Ruby/Rails
-----> Using Ruby version: ruby-1.9.3
-----> Installing dependencies using 1.7.12
       Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
       Using aasm 3.0.23
       Using rake 10.3.2
       Using abn 2.0.0
       Using i18n 0.6.11
       Using multi_json 1.10.1
       Using builder 3.0.4
       Using journey 1.0.4
       Using erubis 2.7.0
.......
      Using tinymce-rails 3.5.8 from git://github.com/spohlenz/tinymce-rails.git (at update-manifest)                                                                  [252/1934]
       Your bundle is complete!
       Gems in the groups development and test were not installed.
       It was installed into ./vendor/bundle
       Bundle completed (1.49s)
       Cleaning up the bundler cache.
-----> Writing config/database.yml to read from DATABASE_URL
-----> Preparing app for Rails asset pipeline
       Running: rake assets:precompile
       Connecting to database specified by DATABASE_URL
       Creating scope :from. Overwriting existing method TimesheetEntry.from.
       Creating scope :public. Overwriting existing method ReviewTemplateAnswer.public.
       npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"0.6.x"} (current: {"node":"0.12.0","npm":"2.5.1"})
       npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"0.6.x"} (current: {"node":"0.12.0","npm":"2.5.1"})
       ><EMAIL_ADDRESS>postinstall /tmp/build_8236fbf22ea851f11d6bc9907fbd15eb/frontend
       > node_modules/bower/bin/bower install
       bower loader.js#3.2.0       not-cached git://github.com/ember-cli/loader.js.git#3.2.0
       bower loader.js#3.2.0          resolve git://github.com/ember-cli/loader.js.git#3.2.0
       bower ember-cli-shims#0.0.3 not-cached git://github.com/ember-cli/ember-cli-shims.git#0.0.3
       bower ember-cli-shims#0.0.3    resolve git://github.com/ember-cli/ember-cli-shims.git#0.0.3
...

 ├──<EMAIL_ADDRESS><EMAIL_ADDRESS>                                                                                [27/1934]
       ├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>       ├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>       ├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>       ├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>       ├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>       ├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>no
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>       ├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>       ├──<EMAIL_ADDRESS><EMAIL_ADDRESS>       ├──<EMAIL_ADDRESS>       ├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>       ├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>       ├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>       └──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>       The package `ember-data` is not a properly formatted package, we have used a fallback lookup to resolve it at `/tmp/build_8236fbf22ea851f11d6bc9907fbd15eb/frontend/node_mo
dules/ember-data`. This is generally caused by an addon not having a `main` entry point (or `index.js`).
       version: 0.2.0
       Could not find watchman, falling back to NodeWatcher for file system events
Building.Building..Built project successfully. Stored in "/tmp/build_8236fbf22ea851f11d6bc9907fbd15eb/tmp/ember-cli-3ee94d7f-918c-4612-abe1-386e790dac98/apps/front[6/1934]
       ** [Airbrake] Notice was not sent due to configuration:
       Environment Monitored? true
       API key set? false
       rake aborted!
       Application has been already initialized.
       /tmp/build_8236fbf22ea851f11d6bc9907fbd15eb/vendor/bundle/ruby/1.9.1/gems/railties-3.2.18/lib/rails/application.rb:135:in `initialize!'
       /tmp/build_8236fbf22ea851f11d6bc9907fbd15eb/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.18/lib/sprockets/assets.rake:95:in `block (2 levels) in <top (required)>'
       /tmp/build_8236fbf22ea851f11d6bc9907fbd15eb/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.18/lib/sprockets/assets.rake:60:in `block (3 levels) in <top (required)>'
       /tmp/build_8236fbf22ea851f11d6bc9907fbd15eb/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.18/lib/sprockets/assets.rake:23:in `invoke_or_reboot_rake_task'
       /tmp/build_8236fbf22ea851f11d6bc9907fbd15eb/vendor/bundle/ruby/1.9.1/gems/actionpack-3.2.18/lib/sprockets/assets.rake:29:in `block (2 levels) in <top (required)>'
       Tasks: TOP => assets:precompile:primary => assets:environment
       (See full trace by running task with --trace)
 !
 !     Precompiling assets failed.
 !

 !     Push rejected, failed to compile Multipack app

If you don't have ember-cli-rails, is that "API key set? false" line still there? Not an expert, but that's what stands out to me.

That's weird. I've never seen this one before. Is there a way you could provide a test repo reproducing the error?

@jamescgibson that looks like the message from Airbrake gem

Same problem for me. No Airbrake, but using Unicorn and deploying to staging, if that's at all relevant. Is there anything special I should do to make sure staging works? I'm already including config.consider_all_requests_local = false.
remote:        Building.Building..Building...BuildingBuilding.Built project successfully. Stored in "/tmp/build_71838f14ea40c623517148479022613e/tmp/ember-cli-24bef7dd-b6c1-4aae-a86e-e2f71eb52151/apps/dashboard".
remote:        rake aborted!
remote:        Application has been already initialized.
remote:        /tmp/build_71838f14ea40c623517148479022613e/vendor/bundle/ruby/1.9.1/gems/railties-3.2.18/lib/rails/application.rb:135:in `initialize!'
remote:        /tmp/build_71838f14ea40c623517148479022613e/vendor/bundle/ruby/1.9.1/gems/turbo-sprockets-rails3-0.3.6/lib/turbo-sprockets/tasks/assets.rake:186:in `block (2 levels) in <top (required)>'
remote:        /tmp/build_71838f14ea40c623517148479022613e/vendor/bundle/ruby/1.9.1/gems/turbo-sprockets-rails3-0.3.6/lib/turbo-sprockets/tasks/assets.rake:35:in `invoke_or_reboot_rake_task'
remote:        /tmp/build_71838f14ea40c623517148479022613e/vendor/bundle/ruby/1.9.1/gems/turbo-sprockets-rails3-0.3.6/lib/turbo-sprockets/tasks/assets.rake:50:in `block (2 levels) in <top (required)>'
remote:        Tasks: TOP => assets:precompile:all => assets:cache:clean => assets:environment
remote:        (See full trace by running task with --trace)
remote:  !
remote:  !     Precompiling assets failed.
remote:  !
remote:
remote:  !     Push rejected, failed to compile Multipack app

I have a similar error too (no Airbrake error on mine):
remote:        rake aborted!
remote:        Application has been already initialized.
remote:        /tmp/build_f2a2aab09aa82f21ebfa9bad42457f6e/lib/extensions/object.rb:10:in `raise'
remote:        /tmp/build_f2a2aab09aa82f21ebfa9bad42457f6e/vendor/bundle/ruby/2.1.0/gems/railties-3.2.18/lib/rails/application.rb:135:in `initialize!'
remote:        /tmp/build_f2a2aab09aa82f21ebfa9bad42457f6e/vendor/bundle/ruby/2.1.0/gems/turbo-sprockets-rails3-0.3.14/lib/turbo-sprockets/tasks/assets.rake:192:in `block (2 levels) in <top (required)>'
remote:        /tmp/build_f2a2aab09aa82f21ebfa9bad42457f6e/vendor/bundle/ruby/2.1.0/gems/turbo-sprockets-rails3-0.3.14/lib/turbo-sprockets/tasks/assets.rake:35:in `invoke_or_reboot_rake_task'
remote:        /tmp/build_f2a2aab09aa82f21ebfa9bad42457f6e/vendor/bundle/ruby/2.1.0/gems/turbo-sprockets-rails3-0.3.14/lib/turbo-sprockets/tasks/assets.rake:50:in `block (2 levels) in <top (required)>'
remote:        Tasks: TOP => assets:precompile:all => assets:cache:clean => assets:environment
remote:        (See full trace by running task with --trace)
remote:  !
remote:  !     Precompiling assets failed.
remote:  !

@rwz here's a repo which captures the unique parts of my setup using a base ember-cli/rails setup.
https://github.com/skylar/ecli-deploy
Starting at commit 7fe81a5 you'll see the error reproduced on deploy. I'm working on isolating the exact cause. It appears it may be related to initialization in the dm-rails gem or related DataMapper setup.

Isolating the cause, it appears that setting
config.assets.initialize_on_precompile = false
triggers the failure. It might be somewhat common for Heroku users since they recommend this in their docs as a way to avoid deploy errors and save time.  I'm sure that's why I set it.
https://devcenter.heroku.com/articles/rails-asset-pipeline#troubleshooting

We're sorry that this issue has sat for so long.
The project is now maintained by thoughtbot, and we're declaring an issue bankruptcy of sorts.
We're closing this issue. If what you've described is still a problem, please comment on this issue and we'll reopen.
Thanks for your patience.


⚠ Samsung has degraded performance

In a586acf, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2900 ms

Resolved: Samsung performance has improved in 23a0d83.


SDK Workstation link on README is broken!

Use this option to install the SDK on a workstation that already has ROS installed: One Line SDK Install (binary)
https://bitbucket.org/DataspeedInc/dbw_mkz_ros/src/81e63fcc335d7b64139d7482017d6a97b405e250/ROS_SETUP.md?fileviewer=file-view-default
returns 404
That link has no power here

Noticed the same issue, but found the file here: https://bitbucket.org/DataspeedInc/dbw_mkz_ros/src/master/ROS_SETUP.md

Hi @Horki
We have updated the link in readme. Thank you @alberto139 for the link.
Thank you.

@UAnjali that was fast 😳


Cannot install Rasa with Python 3.10: absl-py gives error "Python version 2.7 or 3.4+ is required"

Rasa Open Source version
3.2.10
Rasa SDK version
No response
Python version
Other
What operating system are you using?
Linux
What happened?
Python version: 3.10
(The version dropdown is broken, so I am inputting this manually.)
I tried to install Python the latest Rasa version With Python 3.10.7, but it failed when installing the absl-py package, with the error "Python version 2.7 or 3.4+ is required".
Command / Request
python -m venv venv
source venv/bin/activate
pip install rasa

Relevant log output
Collecting rasa
  Downloading rasa-1.10.2-py3-none-any.whl (510 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 510.3/510.3 kB 4.1 MB/s eta 0:00:00
Collecting webexteamssdk<1.4.0,>=1.1.1
  Downloading webexteamssdk-1.3.tar.gz (56 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 57.0/57.0 kB 1.6 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
Collecting fbmessenger<6.1.0,>=6.0.0
  Downloading fbmessenger-6.0.0-py2.py3-none-any.whl (11 kB)
Collecting sklearn-crfsuite<0.4,>=0.3
  Downloading sklearn_crfsuite-0.3.6-py2.py3-none-any.whl (12 kB)
Collecting prompt-toolkit<3.0,>=2.0
  Downloading prompt_toolkit-2.0.10-py3-none-any.whl (340 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 340.0/340.0 kB 8.2 MB/s eta 0:00:00
Collecting twilio<6.27,>=6.26
  Downloading twilio-6.26.3-py2.py3-none-any.whl (979 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 979.1/979.1 kB 15.4 MB/s eta 0:00:00
Collecting sanic-cors<0.11.0,>=0.10.0b1
  Downloading Sanic_Cors-0.10.0.post3-py2.py3-none-any.whl (17 kB)
Collecting rocketchat_API<1.4.0,>=0.6.31
  Downloading rocketchat_API-1.3.1-py3-none-any.whl (9.6 kB)
Collecting slackclient<3.0.0,>=2.0.0
  Downloading slackclient-2.9.4-py2.py3-none-any.whl (97 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 97.1/97.1 kB 2.8 MB/s eta 0:00:00
Collecting requests<3.0,>=2.23
  Downloading requests-2.28.1-py3-none-any.whl (62 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 62.8/62.8 kB 1.8 MB/s eta 0:00:00
Collecting sanic-jwt<1.5.0,>=1.3.2
  Downloading sanic-jwt-1.4.1.tar.gz (19 kB)
  Preparing metadata (setup.py) ... done
Collecting tensorflow-estimator==2.1.0
  Downloading tensorflow_estimator-2.1.0-py2.py3-none-any.whl (448 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 449.0/449.0 kB 4.7 MB/s eta 0:00:00
Collecting pymongo[srv,tls]<3.9.0,>=3.8.0
  Downloading pymongo-3.8.0.tar.gz (649 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 649.9/649.9 kB 13.8 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
Collecting oauth2client==4.1.3
  Downloading oauth2client-4.1.3-py2.py3-none-any.whl (98 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 98.2/98.2 kB 1.8 MB/s eta 0:00:00
Collecting kafka-python<2.0,>=1.4
  Downloading kafka_python-1.4.7-py2.py3-none-any.whl (266 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 266.1/266.1 kB 8.8 MB/s eta 0:00:00
Collecting pydot<1.5,>=1.4
  Downloading pydot-1.4.2-py2.py3-none-any.whl (21 kB)
Collecting python-engineio<3.13,>=3.11
  Downloading python_engineio-3.12.1-py2.py3-none-any.whl (49 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 49.6/49.6 kB 1.7 MB/s eta 0:00:00
Collecting absl-py<0.10,>=0.9
  Downloading absl-py-0.9.0.tar.gz (104 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 104.0/104.0 kB 2.9 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [6 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-4i0j4vq9/absl-py_a6eb2966754f41d392d770f4e258b343/setup.py", line 34, in <module>
          raise RuntimeError('Python version 2.7 or 3.4+ is required.')
      RuntimeError: Python version 2.7 or 3.4+ is required.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

This is due to abseil-py#161, which was fixed in version 0.12.0.

I see - thanks for the clarification. I wonder if an easier-to-understand error message could be displayed when trying to pip install from 3.10? If someone sees the message "3.4+ is required" when they are using 3.10, it is going to be confusing.

agree... confusing message "3.4+ is required" but it should say 3.4-3.10 is required"... wasted an hour trying to figure out why it's not installing :(


File names with space reported as separate files when using bash script

I tried to use tree.sh. It ran but it reports file names with spaces as separate files
For example while I have just 1 file named "Gradient Descent.html", it displays this.

Fixed this up in here: https://github.com/kddeisz/tree/commit/1876e16118611381efde10168657dd3195ee81f4?w=1


visualization of the Symmetry Descriptors

After getting the values of the descriptor，how can I get the visualization of the Symmetry Descriptors as Figure 1 shown in the paper？
Is there an implementation of this function in this repo？

Unfortunately, the visualization is not part of the repo. If you have a windows machine, I could share a visualization executable.

Of course I have. Could you please send this executable file to my mailbox ?
It's<EMAIL_ADDRESS>Thank you very much for your selfless sharing.

You should be able to download SphericalGridViewer.exe from the following website:
https://www.cs.jhu.edu/~misha/Spring23/Assignments/3/resources.html
(You will need to have glut32.dll in the same folder as the executable.)

You should be able to download SphericalGridViewer.exe from the following website: https://www.cs.jhu.edu/~misha/Spring23/Assignments/3/resources.html (You will need to have glut32.dll in the same folder as the executable.)

Appreciate for your excellent work firstly. I'm interested in the specific implementation of the visualization.
Can you provide the source code if possible?

Unfortunately, I cannot. The code is a mess. (It was written years ago when I didn't know better than to minimize dependencies.)


Bring chem setup scripts better in line with gcm_setup

Updated gmichem_setup, stratchem_setup and geoschemchem_setup, so that the resulting gcm_run.j script works with no edits required.  StratChem and GEOS-Chem are zero diff;  GMI experiments now explicitly set GMICHEM_DT, which is generally 2 * HeartBeat; in previous Git releases,  GMICHEM_DT defaulted to the HeartBeat.  Since gcm_setup has not changed, this PR is zero-diff.

I would like to add one more change to gmichem_setup, sorry!  Should be complete later today.

@mmanyin no problem. Just let me know when its done.

@sdrabenh thanks!  It's done now.


Add safe-add function

To be a participant-runtime counterpart to the &safe-add assembly instruction.

Can you update, add the missing comment, and merge?

Already merged. Closing


Create optimized commit and preload for migrations

I think we can speedup commit for migrations.  Also create preload, which doesn't exist yet.
This proposed optimization would only be used for migrations.

Closed by #403 and #404


Enquiry about run_coverage.pl

I was using run_coverage.pl when I passed the arguments related to it as shown in the documentation, it's showing that the suite does not exist.
I am new to this thing
Just a question please help.
I ran this
run_coverage.pl -p Lang -d Lang-11f-randoop.1.tar.bz2 -o /home/tushar/output
and got this
Test suite directory Lang-11f-randoop.1.tar.bz2 does not exist! at /home/tushar/defects4j/framework/bin/run_coverage.pl line 128.
I searched for test suite but didn't find any in the repository.
And if I have to download them separately please provide the source.
thanks in advance

Hi @tbhal,
Is your goal to measure coverage for a generated test suite, or are you trying to achieve something else?
If your goal is to measure coverage for a generated test suite:

Did you create a test suite, using the gen_tests script? If so, what command did you execute. If not, you need to create a test suite first -- if you want to measure coverage for a generated test suite (Defects4J does not store generated test suites).

The -d flag expects a directory, not a file. See the script documentation for further details.

Best,
René

Thanks @rjust, yes I want to calculate coverage.
I will run the gen_test script thanks for the input.

Hey @rjust I was using the gen_test_script you mentioned to use for generating the test suite.
It requires a parameter -g generator it says that by running run_test_gen.pl -g help I can see the list of supported generators but when I run this command it shows
run_test_gen.pl: command not found
I looked for the file in the defects4j directory but it does not have one.
Can you tell what can be the problem?
Thanks

Just to close the loop, did you manage to create the test suites and calculate coverage? The issue in the follow-up question seems to be a misspelled filename (gen_tests vs. run_test_gen).
Can we close this issue?

Just to close the loop, did you manage to create the test suites and calculate coverage? The issue in the follow-up question seems to be a misspelled filename (gen_tests vs. run_test_gen).
Can we close this issue?


EKS cluster autoscaling tests

Prepare manual load tests to ensure that cluster scales up and down as expected. Load tests will be included later into epiphany code but not at that moment.
Is your feature request related to a problem? Please describe.
EKS clusters we will provide in epiphany need to have horizontal autoscaling enabled and tested.
Describe the solution you'd like
There should be some Kubernetes Deployment defined with images applying some high load on cluster. With this deployment we should be able to scale number of replicas up and down, and check if vertical autoscaler is responding accordingly and scales nodes up and down.
Deployment and description of commands should be committed to sub-directory with terraform scripts of EKS cluster. There is no need to integrate it with any test pipeline at this point.
Describe alternatives you've considered
Unknown.
Additional context
No.

This task is extremely similar to #1441 and code might be shared by both tasks.

I'm having problems deploying a cluster.
Looks like an issue installing chart.
Error: failed to download "stable/cluster-autoscaler" (hint: running `helm repo update` may help)

  on cluster-autoscaler.tf line 1, in resource "helm_release" "cluster-autoscaler":
   1: resource "helm_release" "cluster-autoscaler" {

@przemyslavic  - I am working on that.. Looks like there is an issue when deploying 2 clusters.
Simplest solution which is working properly is to re-use the "cluster-autoscaler" role for other deployments, but @pyrkamarcin  mention that this solution might be not secure, so I am looking for other possibilities to run multiply roles  - one per cluster. Sadly its quite tought

Just make a new PR: https://github.com/epiphany-platform/epiphany/pull/1623 - please review

I already test the autoscaling feature, but it will be good if someone else will check it.
Some docs, which I did recently:
https://github.com/mum0l/epiphany/blob/feature/eks_autoscaler_fix/docs/design-docs/eks/README.md#testing-the-autoscaling-feature

@przemyslavic could you test it again?

Autoscaling has been tested in the same way as for the AKS cluster (according to the scenario described here). The number of pods and nodes varied depending on the load. Seems to be working properly.


make resizable by dragging

most of the time my path has an ellipsis  and i have no idea what it is... would be great to be able to drag the dev tools out to any width I like, so I can read it

Another layout suggestion (I rate it would be included in this work) would be to change the docking location? Forcing it to the right is blocking my form :')

sounds like a much easier job. will take a look at it.

https://github.com/react-hook-form/devtools/issues/82

Any progress on this? I can't read the path names since they are too long.

+1, the current implementation without dynamic width doesn't make the tool usable. Looking forward on this.

Hi, is this being looked at? If not I would like to contribute.

They closed the issue , but its still not fixed


V1.5.1 - Resolved ticket related to popup word wrapping

Resolved following ticket :
#188 Words interrupted due to word wrapping in popup and bottom panel

@lindsayking FYI
LK tested, now merging.


Revert "Fix turned off thrusters consume power"

Reverts space-wizards/space-station-14#26690

i still dont understand what is the problem

i still dont understand what is the problem

https://github.com/space-wizards/space-station-14/issues/27754

so maybe the problem is they consume too much power, or power flickering issue in general? because i suppose other power receivers can flicker

The better solution is making it handle draw properly and still show the sprite but just full-sending power or not will just cause this.

it does this if you go from powered to no power at all they keep flickering sound and sprite which is bad, its not just if there isnt enough power theres none at all


Move away from string interpolation & adopt query parameters

The current implementation uses string interpolation to construct sqlite queries.
See the following for a typical example:
https://github.com/ambertide/datalite/blob/81010fc015fbd8cba12ba86b27e4e88b8b79c179/datalite/datalite_decorator.py#L30
This causes problems when trying to insert JSON data (or other fancy strings) into a table.
There is another way to pass values into queries: so-called query parameters. Query parameters do not have this same limitation. See cursor-objects (sqlite3).

I also made certain changes that further adopt query parameters where I could to hopefully protect against SQL injections, I think it is in a good state right now.


[GOBBLIN-731] Make deserialization of FlowSpec more robust

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following Gobblin JIRA issues and references them in the PR title.

Description
Catching exception when loading FlowSpec from FileSystem and make sure that even some of spec files are problematic, the rest of them will still be successfully deserialized.
Adding unit test for that.
Removing some unnecessary modifiers while reading through the code.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@sv2000 @yukuai518  Can you take a look ? Thanks.


File saving shortcuts bug

Hello,
in the last 2 releases of VSCode Insiders the file saving shortcuts have been altered and are no longer consistent with the shortcuts indicated in settings:
Save --> ⌘S
Save As... --> ⇧⌘S
Save All --> ⌥⌘S
Currently on VsCodeInsiders:
Save --> no shortcuts!
Save As... --> ⌥⌘S
Save All --> ⌘S
I find this modification very inconvenient, in particular having removed the shortcut to save a single file.

We did not change any keybindings, you either installed an extension that took them or manually changed them:
https://github.com/microsoft/vscode/blob/8e1fe1d8999845ef8f88a6131a4a95b0f67fdd44/src/vs/workbench/contrib/files/browser/fileCommands.ts#L419

I haven't manually edited them, nor do I think I've installed any new extensions recently that may have altered the shortcuts.
I see the shortcuts changed also in the menu, look:

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

I'm on this version:
Versione: 1.47.0-insider
Commit: 6c235c723cb2d8defb840f732eac620f54aa8b9d
Data: 2020-06-26T05:33:20.679Z (4 ore fa)
installed 4 hours ago.
I see also a bit of confusion in Preferences: Keyboard Shortcuts:

@emilime that is strange, for me it shows:

I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line (NOT the integrated terminal in Code), execute: code --disable-extensions and try your steps again to see if it reproduces. If you see it is an issue with the extension, please file it against the extension repository itself.

Hello @bpasero,
you were right, disabling all the extensions shortcuts and menus return to normal.
Now investigate which extension is causing problems.
Thanks for the help


Updating line height (percentage) for fonts in FT updates in Figma styles as 'Auto' instead of percentage.

Workflow: Added a new percentage value in FT (line height)>>inserted this value to the heading token setting>>pressed update>>problem occurs.
Any idea why this should happen?

Does the problem persist if you remove the % from the token name? e.g. $lineHeights.125 instead of $lineHeights.125%?

Hi. Yes! Magic :) It is solved. Thank you.


amino acid database for HUMAnN3 run

Hi.
Thank you for developing this wonderful tool.
I have finished analyzing kraken/bracken using the pre-build database based on GTDB207 that you created and
I am now working on the HUMAnN3 analysis.
When I ran HUMAnN3, I used as the protein database for diamond the uniref90_201901.dmnd that I downloaded from your ftp server. But the latest version of the protein database in HUMAnN3 is not 201901 but 201901b.
(I then received an error saying that the latest version is 201901b, not 201901. This is not a problem as it can be addressed by renaming it...)
So, I would like to confirm this.
Am I correct in understanding that the uniref90_201901.dmnd for humann3 that can be downloaded from the ftp server also uses UniRef 90(version 201901)?
If I want to use uniref 90 (version 201901b), should I use the Struo2 pipeline to generate a new database?
(I do not intend to add my samples to an existing database, I just want to use the GTDB database.)
thanks!

When I ran HUMAnN3, I used as the protein database for diamond the uniref90_201901.dmnd that I downloaded from your ftp server. But the latest version of the protein database in HUMAnN3 is not 201901 but 201901b.

Yes, I used the 201901 database for creating the Struo2 custom databases

Am I correct in understanding that the uniref90_201901.dmnd for humann3 that can be downloaded from the ftp server also uses UniRef 90(version 201901)?

Yes, I'm using the UniRef version used for the HUMAnN3 201901 database.

If I want to use uniref 90 (version 201901b), should I use the Struo2 pipeline to generate a new database?

Yes, you would have to create a new set of custom databases with Struo2

Thank you for your quick response.
Is it possible to just generate the databases involved in the HUMAnN3 analysis to save time? In that case, in the config.yaml file, in the databases section, should I replace kraken2 and bracken with Skip and run the pipeline?
Also, what is required as input files for this?
Thanks for your kind understanding

Is it possible to just generate the databases involved in the HUMAnN3 analysis to save time?

You can skip the kraken2/bracken steps, but the humann3 part of the pipeline requires a lot of computation. Check out the Struo2 paper for an idea of how much is needed.

Thank you for your kind support. I'll try it.


Clean install fails with "Failed to run git"

What did you expect to happen?
I expect bin/doom install to succeed on new installation.
What actually happened?
bin/doom install fails with `Failed to run "git"; see buffer straight-process. I don't know how to read straight-process and didn't found a log file.
Additional details:

Link to your private config, : https://gitlab.com/bersace/dotfiles/-/tree/master/files/.config/doom

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux bullseye/sid
Release:        testing
Codename:       bullseye
$ \emacs --version
GNU Emacs 27.1
Copyright (C) 2020 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GNU Emacs
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.
$ git --version
git version 2.30.1

Steps to reproduce:

Install debian bullseye
Install prerequisites : emacs, git, fd, ripgrep.
Follow installation instructions from README  (clone and doom install)

System information:
bin/doom info fails with same error :
$ ~/.emacs.d/bin/doom info
Failed to run "git"; see buffer *straight-process*

How to debug this ? Do you have a clue ?
Regards.

Please include the rest of doom install's output. The backtrace doesn't include the output from straight.

same issue here with:
❯ doom info
  generated  Mar 15, 2021 18:55:44
     distro  Arch Linux Linux 5.11.6-arch1-1 x86_64
      emacs  27.1 ~/.emacs.d/
       doom  2.0.9 HEAD -> develop 46dedb3e3 2021-03-13 16:35:21 -0500 ~/.doom.d/ -> ~/.doom.d/
      shell  /usr/bin/fish
   features  XPM JPEG TIFF GIF PNG RSVG CAIRO SOUND GPM DBUS GSETTINGS GLIB NOTIFY INOTIFY ACL GNUTLS LIBXML2 FREETYPE HARFBUZZ M17N_FLT LIBOTF ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS LIBSYSTEMD JSON PDUMPER LCMS2 GMP
     traits  batch server-running envvar-file
    modules  :completion company ivy :ui doom doom-dashboard doom-quit fill-column hl-todo indent-guides minimap modeline nav-flash neotree ophints (popup +defaults) ligatures unicode vc-gutter vi-tilde-fringe workspaces :editor file-templates fold snippets :emacs dired electric undo vc :checkers syntax :tools ansible direnv docker editorconfig (eval +overlay) lookup lsp magit make terraform :lang cc common-lisp coq crystal csharp data (dart +flutter) elixir elm emacs-lisp erlang ess faust fsharp fstar gdscript (go +lsp) (haskell +dante) hy idris json (java +meghanada) javascript julia kotlin latex lean factor ledger lua markdown nim nix ocaml org php plantuml purescript python qt racket raku rest rst (ruby +rails) rust scala scheme sh sml solidity swift terra web yaml :config literate (default +bindings +smartparens)
   packages  n/a
        nil
       elpa  n/a

I cant even execute doom info.

My issue isn't with a clean install, I had a working doom setup at one point (this has been an issue for me for at least a few days, can't particularly remember when it started), but running doom upgrade:
$ doom upgrade
> Preparing to upgrade Doom Emacs and its packages...
✓ Doom is already up-to-date!
Doom is up-to-date!
> Synchronizing your config with Doom Emacs...
  > Regenerating envvars file at "~/.emacs.d/.local/env"
    ✓ Successfully generated "~/.emacs.d/.local/env"
  > Installing packages...
    - No packages need to be installed
  > (Re)building packages...
    - No packages need rebuilding
  > Updating recipe repos...
  > Updating packages (this may take a while)...
    x There was an unexpected errorp...
      Message: error
      Data: (error . "Failed to run \"git\"; see buffer *straight-process*")
      Backtrace:
        (signal error ("Failed to run \"git\"; see buffer *straight-process*"))
        (error "Failed to run %S; see buffer %s" "git" "*straight-process*")
        (if (car result) (cdr result) (error "Failed to run %S; see buffer %s" pro
        (let ((result (apply #'straight--call program args))) (if (car result) (cd
        (straight--get-call-raw "git" "fetch" "origin")
        (apply straight--get-call-raw "git" ("fetch" "origin"))
        (string-trim (apply #'straight--get-call-raw program args))
        (straight--get-call "git" "fetch" "origin")
        (and (straight-vc-git--ensure-remotes recipe) (straight--get-call "git" "f
        (while t (and (straight-vc-git--ensure-remotes recipe) (straight--get-call
    ! Extended backtrace logged to ~/.emacs.d/.local/doom.error.log

My ~/.emacs.d/.local/doom.error.log has the same output as the above comment
doom info:
  generated  Mar 15, 2021 20:55:43
     distro  "Arch Linux" Linux 5.11.6-arch1-1 x86_64
      emacs  27.1 ~/.emacs.d/
       doom  2.0.9 HEAD -> develop 46dedb3e3 2021-03-13 16:35:21 -0500 ~/.config/doom/
      shell  /usr/bin/zsh
   features  XPM JPEG TIFF GIF PNG RSVG CAIRO SOUND GPM DBUS GSETTINGS GLIB NOTIFY INOTIFY ACL GNUTLS LIBXML2 FREETYPE HARFBUZZ M17N_FLT LIBOTF ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS LIBSYSTEMD JSON PDUMPER LCMS2 GMP
     traits  batch server-running envvar-file
    modules  :completion company ivy :ui doom doom-dashboard doom-quit hl-todo modeline nav-flash ophints (popup +all +defaults) treemacs vc-gutter vi-tilde-fringe window-select workspaces :editor (evil +everywhere) file-templates fold (format +onsave) multiple-cursors rotate-text snippets :emacs (dired +ranger) electric ibuffer undo vc :term shell :checkers syntax spell :tools docker (eval +overlay) gist (lookup +docsets) lsp magit make :lang (cc +lsp) clojure common-lisp data (elixir +lsp) (elm +lsp) emacs-lisp erlang (go +lsp) (haskell +dante) (javascript +lsp) julia (kotlin +lsp) latex (markdown +lsp) (org +dragndrop +present) raku php (python +lsp) (ruby +lsp) rust scala (sh +lsp) (web +lsp) (yaml +lsp) :config (default +bindings +smartparens)
   packages  (xclip) (aggressive-indent) (lsp-ivy) (company-lsp) (lsp-ui) (lsp-mode) (ccls) (pipenv)
        nil
       elpa  n/a

My config is here, if thats useful in some way.

Here is strace output:
...
openat(AT_FDCWD, "/usr/bin/git", O_RDONLY|O_CLOEXEC|O_PATH|O_DIRECTORY) = -1 ENOTDIR (Not a directory)
pipe2([6, 7], O_CLOEXEC)                = 0
rt_sigprocmask(SIG_BLOCK, [INT CHLD], [], 8) = 0
vfork()                                 = 1284396
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
close(7)                                = 0
close(5)                                = 0
read(6, "Cloning into '/home/bersace/.ema"..., 16384) = 69
read(6, "fatal: multiple updates for ref "..., 16315) = 73
read(6, "", 16242)                      = 0
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=1284396, si_uid=1000, si_status=128, si_utime=0, si_stime=2} ---
rt_sigreturn({mask=[]})                 = 0
wait4(1284396, [{WIFEXITED(s) && WEXITSTATUS(s) == 128}], 0, NULL) = 1284396
close(6)                                = 0
faccessat(AT_FDCWD, "/home/bersace/.emacs.d/.local/straight/repos/melpa/", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/dev/null", O_RDONLY|O_CLOEXEC) = 5
faccessat(AT_FDCWD, "/home/bersace/.emacs.d/.local/straight/repos/./", F_OK) = 0
faccessat(AT_FDCWD, "/home/bersace/.gem/ruby/2.3.0/bin/git", X_OK) = -1 ENOENT (No such file or directory)
faccessat(AT_FDCWD, "/home/bersace/.poetry/bin/git", X_OK) = -1 ENOENT (No such file or directory)
faccessat(AT_FDCWD, "/home/bersace/.cache/pyenv/shims/git", X_OK) = -1 ENOENT (No such file or directory)
faccessat(AT_FDCWD, "/home/bersace/.cache/pyenv/bin/git", X_OK) = -1 ENOENT (No such file or directory)
faccessat(AT_FDCWD, "/home/bersace/.cache/gopath/bin/git", X_OK) = -1 ENOENT (No such file or directory)
faccessat(AT_FDCWD, "/home/bersace/.local/bin/git", X_OK) = -1 ENOENT (No such file or directory)
faccessat(AT_FDCWD, "/usr/local/sbin/git", X_OK) = -1 ENOENT (No such file or directory)
faccessat(AT_FDCWD, "/usr/local/bin/git", X_OK) = -1 ENOENT (No such file or directory)
faccessat(AT_FDCWD, "/usr/sbin/git", X_OK) = -1 ENOENT (No such file or directory)
faccessat(AT_FDCWD, "/usr/bin/git", X_OK) = 0
openat(AT_FDCWD, "/usr/bin/git", O_RDONLY|O_CLOEXEC|O_PATH|O_DIRECTORY) = -1 ENOTDIR (Not a directory)
pipe2([6, 7], O_CLOEXEC)                = 0
rt_sigprocmask(SIG_BLOCK, [INT CHLD], [], 8) = 0
vfork()                                 = 1284427
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
close(7)                                = 0
close(5)                                = 0
read(6, "Cloning into '/home/bersace/.ema"..., 16384) = 69
read(6, "fatal: multiple updates for ref "..., 16315) = 73
read(6, "", 16242)                      = 0
wait4(1284427, [{WIFEXITED(s) && WEXITSTATUS(s) == 128}], 0, NULL) = 1284427
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=1284427, si_uid=1000, si_status=128, si_utime=3, si_stime=24} ---
rt_sigreturn({mask=[]})                 = 1284427
close(6)                                = 0
...

The full git error is
$ LC_ALL=C strace -ff -e read=6 bin/doom  install
...
[pid 1289052] write(2, "fatal: multiple updates for ref "..., 73) = 73
[pid 1289032] <... read resumed>"fatal: multiple updates for ref "..., 16305) = 73
 | 00000  66 61 74 61 6c 3a 20 6d  75 6c 74 69 70 6c 65 20  fatal: multiple  |
 | 00010  75 70 64 61 74 65 73 20  66 6f 72 20 72 65 66 20  updates for ref  |
 | 00020  27 72 65 66 73 2f 72 65  6d 6f 74 65 73 2f 6f 72  'refs/remotes/or |
 | 00030  69 67 69 6e 2f 6d 61 73  74 65 72 27 20 6e 6f 74  igin/master' not |
 | 00040  20 61 6c 6c 6f 77 65 64  0a                        allowed.        |
...

@hlissner I found the error in my own git config file. Closing. Thanks for your feedback.
[remote "origin"]
	fetch = +refs/heads/master:refs/remotes/origin/master


Don't use the DefaultServeMux.

This allows to embed go-chromecast into an application that already uses the DefaultServeMux.

Thanks!


statSTR --samples flag doesnt work

with samples file, this option doesnt work, and when use samples file, no samples output

Can you post the command used?


Create Links “tiktok-33”

Automatically generated by Netlify CMS

👷 Deploy Preview for distracted-hoover-7b89cc processing.
🔨 Explore the source changes: 407ace0e5b7408fb49af2333f06f4b91c1b0b5b9
🔍 Inspect the deploy log: https://app.netlify.com/sites/distracted-hoover-7b89cc/deploys/610f185ff7945e0009678279


Question: SxS install of SDK v2.2.204 and 2.2.107

SxS install of SDK v2.2.204 and 2.2.107
In various places I read that depending on the version of Visual Studio one uses, he should install preferably Version 2.2.107 (for VS2017) or Version 2.2.204 (for VS2019). In my case, I've installed both VS versions (specifically v15.8.2 and v16.0.0).
I wonder:

Whether Side by side install of both SDKs allows seamless usage in both VS?
In case SxS install is not a solution, will a future SDK will be published that supports both VS2017 and VS2019?

OK, answering (at least partially) my own question:

After having installed SDK v2.2.107, then SDK v2.2.204,

VS 2019 can correctly build a netcoreapp2.2 project (just tested with the default generated console app, so it does nothing...)
VS 2017 cannot build anything targeting .NET Core >= 2.0 (in the Project Properties > Application tab > Target Framework combo, I can only see .NET Core 1.x)

Then I uninstalled v2.2.204 and kept v2.2.107

VS 2017 can build netcoreapp2.2 projects
VS 2019 as well...

It seems that - contrarily to what's explained here, here and here, VS 2019 can handle building against v2.2.107 SDK... (unless this works because I have VS2017 installed or my test project is too simple).

@livarcocc @nguerrera can you please help with this one?

Make sure that your VS 2017 is updated to 15.9.x and things would work fine SxS with VS 2017 pickinh 2.2.1xx and VS 2019 picking 2.2.2xx+. We did some work in 15.9 to make this happen. The behavior you describe sounds like you have 15.8 or earlier. If not, there's an issue that will need more info and investigation.

Thanks for the reply! Indeed I'm using 15.8.2; I'll give a try to updating my VS2017.


Mods that install translation yml files can conflict due to the symbolic link hierarchy of /config/bepinex/ to /opt/data/bepinex/BepInEx/

The symbolic link that the game uses for runtime to link back to the config folder is catching the plugins folder and yml files that were already loaded once, I'm assuming.
Repro:
Add these mods to a clean install:
OdinPlus-CrystalLights
OdinPlus-OdinsKingdom
OdinPlus-OdinsSteelworks
Smoothbrain-Jewelcrafting
The OdinPlus mods each have a [modname].English.yml file in their respective directories:
CrystalLights.English.yml
OdinsKingdom.English.yml
OdinsSteelworks.English.yml
It appears that because the way this docker has a symbolic link to the config folder which has the plugins folder used for pre-deployment to /opt/data, there is a circular issue happening where the yml files for the mods get read twice. This cause multiple errors, and in this case, a strange null reference exception, too.
[Warning: Unity Log] Duplicate key English found for OdinsKingdom. The duplicate file found at /opt/valheim/bepinex/BepInEx/plugins/OdinPlus-OdinsKingdom/OdinsKingdom.English.yml will be skipped.
[Info   : Unity Log] 04/02/2023 10:36:50: Loaded localization file #0 - 'localization' language: 'English'
[Warning: Unity Log] Duplicate key English found for OdinsKingdom. The duplicate file found at /opt/valheim/bepinex/BepInEx/plugins/OdinPlus-OdinsKingdom/OdinsKingdom.English.yml will be skipped.
[Info   : Unity Log] 04/02/2023 10:36:51: Loaded localization file #1 - 'localization_extra' language: 'English'
[Info   :   BepInEx] Loading [CrystalLights 1.0.7]
[Error  : Unity Log] ArgumentException: An item with the same key has already been added. Key: English
Stack trace:
System.Collections.Generic.Dictionary2[TKey,TValue].TryInsert (TKey key, TValue value, System.Collections.Generic.InsertionBehavior behavior) (at <695d1cc93cca45069c528c15c9fdd749>:0) System.Collections.Generic.Dictionary2[TKey,TValue].Add (TKey key, TValue value) (at <695d1cc93cca45069c528c15c9fdd749>:0)
System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement] (System.Collections.Generic.IEnumerable1[T] source, System.Func2[T,TResult] keySelector, System.Func2[T,TResult] elementSelector, System.Collections.Generic.IEqualityComparer1[T] comparer) (at <351e49e2a5bf4fd6beabb458ce2255f3>:0)
System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement] (System.Collections.Generic.IEnumerable1[T] source, System.Func2[T,TResult] keySelector, System.Func`2[T,TResult] elementSelector) (at <351e49e2a5bf4fd6beabb458ce2255f3>:0)
LocalizationManager.Localizer.LoadLocalization (Localization __instance, System.String language) (at <9f80e7b068584aef864ca3f29a29214a>:0)
LocalizationManager.Localizer.Load () (at <9f80e7b068584aef864ca3f29a29214a>:0)
CrystalLights.CrystalLights.Awake () (at <9f80e7b068584aef864ca3f29a29214a>:0)
UnityEngine.GameObject:AddComponent(Type)
BepInEx.Bootstrap.Chainloader:Start()
UnityEngine.UI.Image:OnCanvasHierarchyChanged()
[Info   :   BepInEx] Loading [OdinsSteelworks 0.1.12]
[Error  : Unity Log] ArgumentException: An item with the same key has already been added. Key: English
Stack trace:
System.Collections.Generic.Dictionary2[TKey,TValue].TryInsert (TKey key, TValue value, System.Collections.Generic.InsertionBehavior behavior) (at <695d1cc93cca45069c528c15c9fdd749>:0) System.Collections.Generic.Dictionary2[TKey,TValue].Add (TKey key, TValue value) (at <695d1cc93cca45069c528c15c9fdd749>:0)
System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement] (System.Collections.Generic.IEnumerable1[T] source, System.Func2[T,TResult] keySelector, System.Func2[T,TResult] elementSelector, System.Collections.Generic.IEqualityComparer1[T] comparer) (at <351e49e2a5bf4fd6beabb458ce2255f3>:0)
System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement] (System.Collections.Generic.IEnumerable1[T] source, System.Func2[T,TResult] keySelector, System.Func`2[T,TResult] elementSelector) (at <351e49e2a5bf4fd6beabb458ce2255f3>:0)
LocalizationManager.Localizer.LoadLocalization (Localization __instance, System.String language) (at :0)
LocalizationManager.Localizer.Load () (at :0)
OdinsSteelworks.OdinsSteelworks.Awake () (at :0)
UnityEngine.GameObject:AddComponent(Type)
BepInEx.Bootstrap.Chainloader:Start()
UnityEngine.UI.Image:OnCanvasHierarchyChanged()
Eventually it causes [Error  : Unity Log] The WorldGenerator instance was null
which then leads to a massive spam of
[Error  : Unity Log] NullReferenceException: Object reference not set to an instance of an object
Stack trace:
ZInput.GetButtonDown (System.String name) (at <19a546e6f6564ae49c59d4e69bf4c6f6>:0)
UIGamePad.ButtonPressed () (at <835a3a371c5a46df97eae1200aa13dbc>:0)
UIGamePad.Update () (at <835a3a371c5a46df97eae1200aa13dbc>:0)
Other mods that may encounter this problem in this docker because of their use of translation files in the same naming format are:
AzuAntiCheat (AzuAnticheat.English.yml) and  blacks7ar.TeleportationMeads (TeleportationMeads.English.yml)
The OdinPlus team suggest deleting the translation yml for their mods on the dedicated server as a workaround. However, they could not guarantee that a server side mod might not need a translation yml for other purposes, so I wanted to raise this issue to you, @lloesche .
Full log here
LogOutput.log
https://justpaste.it/byp2t

What's the reason of having the configuration files in /config/ one level down from the plugins folder? Instead at the same level of the plugins, so when the symbolic link happens in /opt/bepenix, it doesn't have this issue in the future, or others like it where the plugins folder gets read again after already having been copied.


Very strange error with wrong OrientDB version number & node trying to get exclusive lock on the database

OrientDB Version: upgrade from 2.2.15 to 2.2.26
Java Version: 1.8.121
OS: RHEL  6.7
Expected behaviour
version number on console and server log to be 2.2.26
node will join cluster and have the database online.
Actual behavior
we have 5 nodes,  4 upgrade correctly but one node will not and reports the version as 2.2.15 on the console and the server logs.  This node also will join the cluster but marks the database as unavailable and the logs show it could not get an exclusive lock on the database.  I can't get the logs off this system as it's commercially very sensitive.  but this is my hand copied/typed line:
WARNI  [60] Timeout(20001)ms on waiting for synchronous responses from nodes=[58] responsesSoFar=[] request=(id=4.0 task=exc_lock acquire resource=mydb) [ODistributedDatabaseImpl]
WARNI [60] -> [58] Server '60' cannot acquire distributed lock on resource 'mydb' (timeout=20000)...[ODistributedLockManagerRequester]
SERVER [60] Error on installing database 'mydb' on local node (error=com.orienttechnologies.common.concur.lock.OLockException: Servier '60' cannot acquire exclusive lock on resource 'mydb' (timeout=20000)) [OHazelcastPlugin]
INFO [60] Updated node status to 'ONLINE' [OHazelcastPlugin]
INFO [60] Distributed servers status (*=current @=lockManager[58]):
60 and 58 are our nodes,  60 is failing.
Tried,
a) checked the lib directory only has 2.2.26 versioned jars
b) cleared the node and rm -rf  the install directory. Then re-installing (we use ansible to copy the rpm we have built of Orientdb then the server xml is templated and ssl certs copied.)
c) cleared the node and rm -rf  the install directory. Then copied the install from a node that is working (reset the ssl certs and config)
d) remove java from the system and did b)
e) compared the jars from this node to the others (which are working)
Steps to reproduce
?

hi @hanksieM
how did you upgrade the 4 nodes succesfully?
Did you shutdown the cluster?

Yes, all the nodes were closed and the processes killed if they failed to stop (we get that occasionally).  We suspect the problem is with an in-house plug-in including Orientdb classes in the pom.xml and marking the scope as "compile" and not "provided".  Just testing I'll edit/close this post if that is the fix.

Ok @hanksieM
let me know, thanks

thanks for your time @maggiolo00,
I can confirm that the plugins were causing the problem,  We are still final checking and deploying but I will close this now.
The error was in the Maven pom file having the scope wrong and dependencies on various bits of OrientDB were including the core as a third party dependency.  We can't explain why most nodes worked and some did not; but that's class path problems for you!


feat(minifier): implement converting template literals to strings

basically:
`hello ${"world"}`

now becomes:
"hello world"

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#6486  👈
#6484
#6483
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @camc314 and the rest of your teammates on  Graphite

Merge activity

Oct 13, 2:21 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


One more icon request

Lint Staged config files:

.lintstagedrc file in JSON or YML format
lint-staged.config.js file in JS format

What icon should they use? Does Lint Staged have a logo?

@okonet ^

No, it doesn't have a logo at this moment.
But this is the "standard" configuration file Babel, ESLint and many others are using.

My local copy of the package is a mess at the moment (performing a dissection of V2 components, ripping useful stuff out and rewriting it so it's actually maintainable), so... assuming I don't get to this in the near future, somebody else can submit a pull request for it. =)
I imagine . lintstagedrc can just be assigned the generic gear icon.

Yes, gear is good IMO.

Could this add the other variants for .lintstagedrc that are supported? https://www.npmjs.com/package/lint-staged#configuration


Electron-packager on Windows does not work

Issue Details

Electron Packager Version:

^13.0.1

Electron Version:

^4.0.3

Operating System:

built on macOS Mojave 10.14.6 with wine (installed via brew)

Expected Behavior

The app should work on windows, just like on mac via

Actual Behavior

What works: packaging the app for Mac
What does not work: packaging the app for Windows

npm run electron:package:mac

To Reproduce

checkout Repository from https://github.com/ngx-rocket/generator-ngx-rocket

brew install wine
npm install
npm run electron:build
npm run electron:package:windows

open app.exe on Windows (app.exe is on Mac OS)

My bad.
It worked, if I copied the files to windows-8.1-VM


isOpen flag cause the modal to be destroyed

isOpen is a flag where the DOM got 'appended' and 'destroyed', is there an option where I want to make the modal work as opacity: 0 or 1 instead of display none and false? opacity simply hide and can keep the states in the Modal component.
I can use css to control it but that seems like a hack. A prop as an option will be great.

isOpen is a flag to decide the children is gone or not from the DOM, your code about will cause the children's state to be gone. This is not a styling question, I think you misunderstood my question. I'm asking is it possible to use opacity under the hood so that children can keep the states although the modal remain hidden.

@thian4 Oh, I'm sorry. Totally, misunderstood what you are asking. :pray:
That's correct. The state of what is inside the modal will be destroyed.
I'm not sure, but I think that using opacity, the modal will still be responsive to user input (keyboard and mouse).
One option, is to persist the state on the parent component and give it to the modal when (re)open.

@thian4 Oh, I'm sorry. Totally misunderstood what you are asking.
That's correct. The state of what is inside the modal will be destroyed.
I'm not sure, but I think that using opacity, the modal will still be responsive to user input (keyboard and mouse).
One option is to persist the state on the parent component and give it to the modal when (re)open.

Hey guys, any update on stopping the modal to unmount on isOpen=false and only hide using css property ?

Any updates? I too need states of what is inside the modal to retain.

This scenario of keeping mounted the inner component of the modal when it closes will not be implemented.
The lifecycle of the the inner component of the modal is in between open and closed. So the state is not preserved between state transitions.
You must:

Persist the state outside of the modal
If you want to persist, you can render the inner component and store in hook (it will make it easy to let mem leaks happen)

Did anybody find a good workaround, maybe using opacity: 0 or display: none or similar?
Our inner component is a complex 3rd party Map application that is loaded in an iframe (and takes about 5 secs to load). Whenever the modal is closed and re-opened the initialisation of the external map needs to happen again.  Meaning user waits 5secs again...
I am not sure I understand the workaround with const [comp] = useState(<InnerModalComponent ... />) from above to preserve the inner component. I do not think this would work since it is not adding anything to the actual browser DOM.

@jnachtigall After you store the rendered component of the state, you can use it as a normal variable like
<div>{comp}</div>

Problem is that:

You need to initialize the component and clean up (to avoid leaks)
You will need to change how to state is passed from one component to another


chore(master): release butler 11.1.2

:robot: I have created a release beep boop
11.1.2 (2024-04-08)
Miscellaneous

Debug Docker image build code in GitHub Actions (db36afa)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ptarmiganlabs/butler/releases/tag/untagged-593eab149e095cbc068e :sunflower:


Near CLI looks at CWD for a src/config.js file which can cause interference

Describe the bug
Essentially in the near cli on this line it tries an look for a config.js file within the users current working directory. To me this shouldn’t be the case, it should use a default unless a user explicitly specifies otherwise like --config <your config.js file>
...
const configPath = process.cwd() + '/src/config';
const nearEnv = process.env.NEAR_ENV || process.env.NODE_ENV || 'development';
try {
  const config = require(configPath)(nearEnv);
  return config;
} catch (e) { ... }
...

To Reproduce
Reproduction for this issue is tricky as you will see different results depending on what is in the config.js file.
Steps to reproduce the behavior:

Run near within a project directory that has a src/config.js file
See error

❯ near
/Some/project/directory/src/config.js:L99
export default function someMethod() {
^^^^^^

SyntaxError: Unexpected token 'export'

Expected behavior
I expect that when I run the near command that I will get determintic behaviour regardless of which directory I am in. I expect the the near cli would not be effected by external files within my current directory.
Desktop (please complete the following information):

OS: MacOS
Version: 2.0.1

Let me know what needs to be done and I can open a PR to address this, thanks!

I agree. This has bugged me quite a bit.
near dev-deploy
For example also fails (sometimes silently depending on your setup) if this config file specifies an object that contains additional fields it doesn't recognize...
Odd.

@chadoh Would it be safe to remove as @MaximusHaximus suggested?

cc @vgrichina

@vgrichina @MaximusHaximus @mattlockyer
Any update?


disable formatting lints (a single option)

I usually enable all stable lints, and then disable some:
[tool.ruff.lint]
preview = false
select = ["ALL"]
ignore = [
   "WHAT", # comment why
   "WHAT", # comment why
   "WHAT", # comment why
]

Now the linter forces me to add 15 exceptions to the 'ignore' list. The ruff linter documentation says: When using Ruff as a formatter, we recommend avoiding the following lint rules: ... (https://docs.astral.sh/ruff/formatter/#conflicting-lint-rules)
Can we have a single lint config option to switch off formatting lints?
[tool.ruff.lint]
preview = false
format = false  # ☜

I would rather solve this via #1774 than the introduction of a new rule selector for this purpose.
Do you mind if we track this there instead?

I don't mind, thank you.