FediFetcher doesn't respect robots.txt

I have this in robots.txt:
User-agent: *
Disallow: /

FediFetcher ignores this and makes endless requests to my instance.

Thanks for this @33b5e5 .
I must admit I'm not 100% convinced that FediFetcher should be following the robots.txt, as it's not crawler of indexer. I will give this some thought, and also ask the community what they think.

For reference: I've created a poll for this here:
https://mstdn.thms.uk/@michael/111203851367937130
I want to make it clear that in true British fashion this is a non-binding poll, so I may not actually follow along with the majority here (partially because properly implementing robots.txt is complicated and time consuming), but I want to strongly take the community's view into consideration.

Not an argument for or against, but I just want to point out that you probably don't expect actual AP instances where your instanve's posts are referenced to abstain from fetching them due to robots.txt.
Of course, FediFetcher is not an instance. And I think it also does go and recheck for new replies etc from time to time. And can probably be configured to do it too aggressively.
Perhaps some kind of mutually agreed rate limit (in requests per hour, not minute) would be acceptable for everyone, but that's placing some of the burden to declare it on instance admins.
This is complicated.

Thanks for your comment @virtulis
Definitely agree that it's complicated. To be fair, FediFetcher does obey rate limits. And rate limits can be configured on the server side to be different per user agent. However, each user of FediFetcher runs their own copy of FediFetcher, so there is little point in implementing something specific on FediFetcher's end, as any such rate limit wouldn't be shared across FediFetcher 'instances'.
So imo if a server wants to have stricter rate limits on fedifetcher than on other traffic then that's totally understandable, and we'll honour that. But it would be on the server admin to configure their server (as in nginx, cloudflare, whatever - not their instance software) in that way.

Will also reference a related poll/question I had a few months prior: https://loud.computer/@virtulis/110673351562258162
The results aren't really in our favor. But using a small instance without these tools in the current state of fedi is a pretty bad experience.

Interesting. very different question though, and given the framing of algorithmic timeline not surprising at all 😬

Indeed I framed it in the least favorable way possible.

I'd just implement it to be honest, just make it visible in the logs that its being excluded. Just make sure you're caching the robots.txt for a period of time so you're not hitting that a lot instead 😄
Admins may want to exclude their instances from 'bot' traffic, and robots.txt is a well supported and common process to do so. Much in the same way as someone may want to block Googlebot its the admin's responsibility to understand what the block will do in term so their data.
Just to clarify, i'm against the idea of using robots.txt on public visible AP instances, but giving people options is always good.

Thanks for the responses and for running the poll. "FediFetcher should honour blanket bans in robots.txt" had the most votes, but not by a lot. I understand the gist of the counter arguments. FediFetcher is not exactly a bot. Still, it's not exactly a human actor on the Fediverse either, and I think there should be a way to opt-out.
Over the last 14 days FediFetcher traffic represents around 4% of the hits to my instance. It's not a big deal, but not insignificant either, especially if its use grows.
I don't think respecting a specific call-out in robots.txt while ignoring the default/wildcard makes sense. It goes against the basic logic of robots.txt. The RFC is clear about it: https://datatracker.ietf.org/doc/html/rfc9309#name-the-allow-and-disallow-line
To evaluate if access to a URI is allowed, a crawler MUST match the paths in "allow" and "disallow" rules against the URI.
So I'd maintain the blanket ban should be respected.
I understand there is an argument FediFetcher isn't a crawler. I disagree. It's automated. It's acting on behalf of individual users, but in bulk sends a lot of repetitive traffic for data that may or may not be read by a human. GoAccess categorizes it as a crawler.
I can handle it in Nginx. I have a growing pile of useragents that don't respect robots.txt which get served a 403 or 418. But I went to the trouble to open this issue because I like what the project is doing otherwise.

Thanks again for your detailed response!
There was overall 52% for - that cursed 52/48 ratio again 😁
Anyways, I have decided to implement FediFetcher honouring robots.txt. I think I'd still like to have a settings flag so that this can be turned off if a user really wants to, but with it being enabled by default.

I don't think respecting a specific call-out in robots.txt while ignoring the default/wildcard makes sense.

You are probably right. It also would mean a lot more work as I'd need to implement my own robots.txt parsing algorithm, rather than being able to use an off the shelf solution.
The other problem is time though: Implementing this is not trivial, and the structure of the script doesn't exactly lend itself to it - even worse if I want to implement caching the robots.txt, which is a must imo - as such I make no promise of a timeline, but would welcome a PR if anyone was so inclined.

If noone is working on this, I'm probably going to have a go at this later this week

That would be amazing! I'm not currently working on this, and won't be anytime soon.


Development of PlanetaryGearWithSpring dynamic system

New system is to implement is module gear.py. It should be inherited from similar class being implemented within scope of the module if possible.

Class name has been chanched to PendulumWithRoller due to characteristics closer to pendulum rather than gearbox. Class has been implemented and issue can be closed.
https://github.com/bogumilchilinski/dynpy/blob/c043c9d9944e415c610463fe59ae9109c1587d77/models/mechanics/pendulum.py#L1194-L1321


[NETBEANS-54] Module Review #193

Fix #193
Replaced the old license with the Apache license for spi.viewmodel module.

@emilianbold here is the new pull request.

This branch has conflicts that must be resolved

Oh, somebody pushed a fix for this already!

Sorry, closing. There's nothing else to do for this module.
Please select another issue.

ok, it is ok, I will be working on another issue.


More toUpperCase() fixes

More String.toUpperCase() fixes.

NetflixOSS » eureka » eureka-pull-requests #83 SUCCESS
This pull request looks good

Thanks for the fix.


[ARCTIC-1729] IcebergPartitionPlan impl buildTaskSplitter by Bin-Packing

Why are the changes needed?

fix #1729
IcebergPartitionPlan should implement buildTaskSplitter
Brief change log

move MixedHivePartitionPlan Bin-Packing to AbstractPartitionPlan
IcebergPartitionPlan use Bin-Packing

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before making a pull request

before:

now

Documentation

Does this pull request introduces a new feature? ( no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Thanks for your contribution. BTW, You can associate the original issue using the syntax "fix: #1729 ".

Thanks for your contribution. BTW, You can associate the original issue using the syntax "fix: #1729 ".

sry, I forgot

before:

now

After the code modification, the average file size after optimizing seems to have decreased . I'm concerned that the tasks may have been split too small. Could you provide the value of this table property self-optimizing.target-size(which decides the split task size)? @huyuanfeng2018

before:

now

After the code modification, the average file size after optimizing seems to have decreased . I'm concerned that the tasks may have been split too small. Could you provide the value of this table property self-optimizing.target-size(which decides the split task size)? @huyuanfeng2018

128mb


Types vendor update for minio version bump

Vendor update for changes in rancher/types to bump Minio's version
Related PR: https://github.com/rancher/types/pull/1171

vendoring for: https://github.com/rancher/rancher/issues/27467


Added posibility to use mail smtp server without trusted certificate

Without this setup it is not possible to send emails via smtp server with self-signed certificate. You will reverie such error
{"level":50,"time":1669707712901,"pid":1,"hostname":"hive-emails-deploy-7944bbd7-f5gft","code":"ESOCKET","command":"CONN","stack":"Error: self signed certificate\n    at TLSSocket.onConnectSecure (node:_tls_wrap:1539:34)\n    at TLSSocket.emit (node:events:513:28)\n    at TLSSocket.emit (node:domain:489:12)\n    at TLSSocket._finishInit (node:_tls_wrap:953:8)\n    at TLSWrap.ssl.onhandshakedone (node:_tls_wrap:734:12)","type":"Error","msg":"self signed certificate"}

I left one comment

I applied your suggestion


Update georesources-report-types.ttl

Adding old "Collaborative Drilling Initiative - Final" as an internal report, at L1 request in order to edit old CDI reports.

@DavidArmstrongGSQ the indent is not there when editing but don't know why it's indented in review screen! I don't think the indent will be an issue except that it is not consistent with other lines.

@DavidArmstrongGSQ the indent is not there when editing but don't know why it's indented in review screen! I don't think the indent will be an issue except that it is not consistent with other lines.


"Flip" view navigation button

Our navigation buttons...

...should have a quick "flip" checkbox to reverse the view (and a keyboard shortcut). This is useful when painting to see things from a mirrored perspective.
A clear visual indicator is needed to make it obvious that it's active (so this is soft-blocked on @Keavon for UI and icon design).

This feature is just flip the view board, ya?, if we export the art board, it will export back on original side?

Hi @Keavon, I'm interested in working on this. Could you point me to which core module this flip view feature should be implemented in? （Looks like it's do with navigation but just want to make sure I start in the right direction)

Hi @Keavon, I'm interested in working on this. Could you point me to which module this should be implemented in? (Looks like it's in editor, but just want to make sure)

@jacinyan Yes, in the editor module. You'll want to trace through the code relating to the viewport navigation and specifically the tilt, which is the closest to flip. You can start tracing from an entry point such as navigate_tool.rs which deals with tilt.

@jacinyan Yes, in the editor module. You'll want to trace through the code relating to the viewport navigation and specifically the tilt, which is the closest to flip. You can start tracing from an entry point such as navigate_tool.rs which deals with tilt.
That said, there are other issues that may be more straightforward and also higher priority (and thus more likely to receive bandwidth from me for code review).

Sure, I'll go with something more straightforward.


Basic epa cems output

This PR makes a simple loading function with dask.dataframe.read_parquet. The meat of the PR is really in the testing; I had to pull some shenanigans to get it to work (see below).
Side note: the commit history of this PR is kind of messy because I made a second, separate branch to separate out epacems output code from ramp rate code. There will be a separate PR for ramp rate stuff. They should have been separate branches from the beginning. Oops!
Things to look at:

[ ] Do the epacems() default args make sense? They currently get all data. I guess a naive user could get a memory error, but only if they immediately .compute() to pandas without filtering.
[ ] What config arg should epacems() take? It currently takes a path to the cems directory. Other pudl.output functions take a sqlalchemy connection object, but that doesn't apply here. The other option I considered is a pudl_settings dict, but then the user has to know to make one of those before using this API.
[ ] Is the testing workaround acceptable? The problem is that in integration tests, the test .parquet files are created by etl_test.py. But because pytest runs the tests in alphabetical order, this epacems_test.py module runs before etl_test.py. So I have to create the .parquet files in epacems_test.py in order to run tests on them. I added a check in etl_test.py to skip recreating them if they already exist. I'm sure there's a better way to manage dependencies, but this works for now.

Finally, this would close issue #207 but for the request to filter by utility or plant IDs, which I did not implement. I think that is currently blocked by the crosswalk integration (#1123 ). The plant_id filtering would also be trivial for users that know pandas, so I'm not sure it needs an API.

The way we've dealt with the dependency of some test on the outputs of others in the past has been to use fixtures in a kind of unusual way. So the the pudl_engine fixture actually runs the ETL, and any other test that requires a database be present depends on that fixture.
For the direct SQLite / Parquet ETL, the pudl_engine fixture will also create the CEMS Parquet outputs, so having your test that needs them to be around depend on the pudl_engine fixture would ensure that they're available. And I'm going to merge that into dev tomorrow unless something weird happens.

OK I think I addressed everything above and it's ready to merge.

Hmm @TrentonBush It turns out that the EPA CEMS tests included here fail when you try and run the full tests.
tox -e full_integration

yields:
FAILED test/integration/epacems_test.py::test_epacems_subset - ValueError: These input states are not in our dataset: ['all']

because we also allow "all" as a state, as a readable shorthand for including all of the states. This gets parsed and replaced with the list of all valid EPA CEMS states through pudl.etl._validate_params_epacems(). It's a bit of a hack right now and we should replace it with a Pydantic based settings validation setup. But for now the settings from the settings files needs to be run through those validation functions to work the same as it would during the ETL.


TabBarTop w/ scrollEnabled does not scroll the tab bar correctly when an off-screen tab is focused

If you scroll a TabBarTop (w/ scrollEnabled) and then focus an offscreen tab the focused tab label does not animate to the 'middle' of the tab bar (like the currently focused tab indicator does). I've only tested this so far on iOS so I don't know whether Android is also affected by this issue. Note that the correct tab page is focused, and swiping the content view will fix the positioning of the tab bar labels.
I've attached a screenshot showing the issue. The tab to the left ("OLOGIE" in white text is visible) is currently focused and should appear under the yellow tab focus indicator, but doesn't.

Do you have an example project?
Have you set width in tabStyle?

Width was not set initially, but setting it does not resolve the issue for me. The following code reproduces the problem for me (on the iOS simulator).
import React from 'react';
import {
  AppRegistry,
  Text,
} from 'react-native';
import { TabNavigator, TabView } from 'react-navigation';

function makeTabComponent(i) {
    return class extends React.Component {
      static navigationOptions = {
        title: `Tab #${i}`,
      };

      render() {
        return <Text>This is the {i}'th tab!</Text>;
      }
    }
}

const ReactNavigationTestCase = TabNavigator({
  Tab1: { screen: makeTabComponent(1) },
  Tab2: { screen: makeTabComponent(2) },
  Tab3: { screen: makeTabComponent(3) },
  Tab4: { screen: makeTabComponent(4) },
  Tab5: { screen: makeTabComponent(5) },
  Tab6: { screen: makeTabComponent(6) },
  Tab7: { screen: makeTabComponent(7) },
  Tab8: { screen: makeTabComponent(8) },
  Tab9: { screen: makeTabComponent(9) },
  Tab10: { screen: makeTabComponent(10) }
}, {
  initalRouteName: 'Tab1',
  tabBarComponent: TabView.TabBarTop,
  tabBarPosition: 'top',
  swipeEnabled: true,
  tabBarOptions: {
    scrollEnabled: true,
    tabStyle: { width: 100 }
  }
})

AppRegistry.registerComponent('ReactNavigationTestCase', () => ReactNavigationTestCase);

An example project with the code above is available here.

@mauritsd This is the solution that I made and works for me. I hope it helps
const routeConfiguration = {
  News: { screen: News },
  Databank: { screen: DataBank },
  Videos: { screen: Videos }
};

const numberOfTabs = Object.keys(routeConfiguration).length;
const tabWidth = width / numberOfTabs;

const tabNavigatorConfig = {
  tabBarOptions: {
    tabStyle: {
      width: tabWidth,
    }
  }
};

const MainTab = TabNavigator(routeConfiguration, tabNavigatorConfig);

Thanks, but I think a bugfix is necessary here. I'll have a look at the iOS code for the tab bar and maybe send a pull request.

This is not working for me when swipe the tabs menu and click at some tab as you can see.

@Fenwil Where are you getting the width from in const tabWidth = width / numberOfTabs;?

Pinging OP @mauritsd since this issue is quite old and related to an old version of the lib. If no answer I'll close in 7 days.

This has been fixed in one of react-navigation's dependencies. Sorry; forgot to close it.

@mauritsd which dependencies, I am figuring out this issue and cannot handle it.

@toninho, can you share your code plz.

I was able to make it work by changing the original source code in node_modules/react-native-tab-view/src/TabBar.js -> _handleTabPress and adding there
if (this.props.scrollEnabled) {
      global.requestAnimationFrame(() => {
        this._scrollView.scrollTo({
          x: this.props.navigationState.index * this.props.layout.width,
          animated: false,
        });
      });
 }

in my case I set tabStyle width to device width

@toninho, anyway, please share your code. this is my email<EMAIL_ADDRESS>


Decide on the name of the python package

What should we name python package? I think the name should:

Be specific enough to make it clear it's related to Belarusian language.
Be generic enough to support various conversions of Belarusian language.

For (2) we originally were planning to implement only lacinization: conversion of cyrillic text to lacinka. But after talking to a specialist it seems like we'll have to implement conversion for official (narkamauka) to classic (tarashkevica) modes. That's necessary for proper lacinization later.
Some ideas (I don't have a good idea at the moment).

belalphabet
belconversion
belorthography (see wiki)

@frombrest do you have ideas?

I haven't done any work on this issue. And I don't think I'm going to spend more time on it. Instead let's just decide on a name, so that we can do an alpha release of the package.
I'm planning to go with belorthography as the package name.
@frombrest any concerns?

I am ok, but that sounds a bit like library going to be spell-checking rather than transliteration/metagraphy conversion.

Do you have other preferences/suggestions for the name? I agree that belorthography feels more generic. But well, who knows. Maybe  it will become more generic. For example I think we'll need to implement orthography detection - given text infer whether it's cyrillic or latinica.

Let's go with belorthography .... In case of critical necessity it is possible to deprecate this library and migrate clients to another one with new name.


Unable to find Microsoft.IdentityModel.JsonWebTokens package

In package System.IdentityModel.Tokens.Jwt ver. 5.2.4 dependency to  Microsoft.IdentityModel.JsonWebTokens cannot be resolve, because this package isn't in nuget.org.
Maybe yours build and release flow has incorrect order?

@sbebrys something happened with the signature so nuget is hiding the package. I am investigating.

@sbebrys this should be fixed now.


Actual behaviour
LND hangs and tries to connect to the backend. It can be stopped via kill -9
Via printf debugging I pinpointed the location where it hangs for me:

https://github.com/lightningnetwork/lnd/blob/880279/chanbackup/pubsub.go#L208
https://github.com/lightningnetwork/lnd/blob/880279/chanbackup/pubsub.go#L179
https://github.com/lightningnetwork/lnd/blob/880279/chanbackup/multi.go#L92
https://github.com/lightningnetwork/lnd/blob/880279/chanbackup/crypto.go#L67
https://github.com/lightningnetwork/lnd/blob/880279/chanbackup/crypto.go#L37
https://github.com/lightningnetwork/lnd/blob/880279/keychain/btcwallet.go#L208 -- the callback to Update() never gets called

Because lnd doesn't advance past s.updateBackupFile(), it doesn't enter the select call for the quit channel.

Tried to reproduce locally and it gets stuck here:
1 @ 0x1030e1f 0x104ddd9 0x104ddaf 0x158bb41 0x158bfae 0x158b9f0 0x1597769 0x105e331
#	0x104ddae	time.Sleep+0x12e									/usr/local/go/src/runtime/time.go:105
#	0x158bb40	github.com/btcsuite/btcwallet/wallet.(*Wallet).scanChain+0x100				/Users/user/go/pkg/mod/github.com/btcsuite/btcwallet@v0.0.0-20190524003533-2c05240dff28/wallet/wallet.go:527
#	0x158bfad	github.com/btcsuite/btcwallet/wallet.(*Wallet).syncToBirthday+0x2ad			/Users/user/go/pkg/mod/github.com/btcsuite/btcwallet@v0.0.0-20190524003533-2c05240dff28/wallet/wallet.go:561
#	0x158b9ef	github.com/btcsuite/btcwallet/wallet.(*Wallet).syncWithChain+0x4df			/Users/user/go/pkg/mod/github.com/btcsuite/btcwallet@v0.0.0-20190524003533-2c05240dff28/wallet/wallet.go:328
#	0x1597768	github.com/btcsuite/btcwallet/wallet.(*Wallet).handleChainNotifications.func1+0x38	/Users/user/go/pkg/mod/github.com/btcsuite/btcwallet@v0.0.0-20190524003533-2c05240dff28/wallet/chainntfns.go:43

Will be fixed by #3141.


no command as dysgu filter-normal

i tried dysgu filter-normal but got no such a command error

Hi
I tried to run dysgu filter-normal but got no such a command error. I installed via pip. Thank you!

thanks: dysgu, version 1.3.16

Ah, that is the problem! You will need to upgrade to the latest version to use filter-normal.

i followed the installation instruction via pip. How can I upgrade to the latest version?

I think with pip install dysgu --upgrade


Bot Customization Bug?

Hello Auri:
Regarding the latest v.0.6.0 release of The Archive, the "Bot Customization", at least for me, has presented issues. Attempts at customizing the apparel of bots will be undone after the game is closed. Once relaunched, bot apparel will be the standard default ones once again. This applies to the experimental BepInEx version, I am unaware if it exists with melonloader as I do not use the latter besides for older rundowns. I had: 1. Created a new, clean profile and deleted all data related to GTFO & The Archive to eliminate any potential conflicts and 2. Reinstalled the necessary data fresh. The issues arose once more despite these steps. This issue was not present in the previous v0.5.52 and conflict with anything else is unlikely as I only operate with the use of:

DoorCheeseFix
The Archive
Click
and LowSpecGaming

This is certainly not a top priority to fix, however, you may try to recreate this problem yourself to see if you come up with similar results and implement changes, if necessary, to the next release. Thank you for your time and your amazing work on this mod.

UPDATE:
It seems that changing the bots' names is necessary in saving the cosmetic changes to the bots. I was unaware of this and am unsure if this was intentionally made in such a way. Changing this back maintains the changes made whilst the name was changed, however, reverting it back to its original naming of "Woods", "Dauda", "Hackett", and/or "Bishop" then making changes will not save those changes if a the game is shut down and relaunched.

It seems that changing the bots' names is necessary in saving the cosmetic changes to the bots.

I might have forgotten to change some things when I implemented changes to how settings are saved, it is indeed not intended for the things to not save haha
This happens because (currently) changing values through code requires me to mark the settings as "dirty" (aka changed) manually for them to save, so the reason they only save after changing a bots name is because after doing that it does get set as "dirty" due to the UI interaction.
Changing names to the default ones shouldn't change anything?
Will fix soon™


Unhandled keys in input

I was playing with curtsies.events and found some keys it didn't handle (shift and alt with arrow keys). It asked me to report them here, so here they are.
keylog.txt:
b'\x1b[1;3C' is called Alt-Right
b'\x1b[1;2C' is called Shift-Right
b'\x1b[1;2B' is called Shift-Down
b'\x1b[1;2D' is called Shift-Left
b'\x1b[1;2A' is called shift-up
b'\x1b[1;3B' is called alt-down
b'\x1b[1;3D' is called alt-left
b'\x1b[1;3A' is called alt-up

Some more unhandled:
b'\x1b[3;2~' is called shift-delete
b'\x1b[1;2H' is called shift-home
b'\x1b[1;2F' is called shift-end
b'\x1b[5;2~' is called shift-pageup
b'\x1b[6;2~' is called shift-pagedown
b'\x1b[5;3~' is called alt-pageup
b'\x1b[6;3~' is called alt-pagedown
b'\x1b[1;3H' is called alt-home
b'\x1b[1;3F' is called alt-end

My terminal doesn't want to register alt-delete for some reason (I assume it's bound in the emulator or something), but pattern recognition suggests it would also confuse curtsies.

Thanks @alethiophile! Do you remember what keyboard, operating system, and terminal emulator this might have been using?

see #136

This should be from gnome-terminal running on Fedora (in a Qubes Xen container), keyboard is a UHK (https://uhk.io).

Resolved by https://github.com/bpython/curtsies/pull/136


Move operation errors into operation center

What feature or improvement do you think would benefit Files?
Currently there's an app blocking popup when there's an issue which is annoying when doing many operations at once or wanting to retry one later.
Requirements

Remove model for error
Add a retry and cancel button to operation center errors
Show what the issue with the operation is (Currently only an X in use error message)
Add a flyout/tooltip to say when operation need the users attention (Should be dismissed with an X button or when operation center is opened)

Files Version
<IP_ADDRESS>
Windows Version
10.0.22621.1265
Comments
No response

Same as #7060, #8239 and #7360?

I believe there asking for adding a skip all button. My request is to remove the model completely and have it show in the operations center instead.

I've had cases where I've had to wait to do the operation for a few minutes before it can be retried, and while I can cancel it to use Files I would have to re navigate and select the items again then click the delete button which can take time to do.


Wrong css includes

Hello,
I'm using master and when I'm generating the output with:
node shins.js --customcss --css pub/css/tradegecko.min.css

The css are included like this in the generated html file:
    <link rel="stylesheet" media="screen" href="pub/css/screen.css">
    <link rel="stylesheet" media="screen" href="pub/css/screen_overrides.css">
    <link rel="stylesheet" media="screen" href="pub/css/tradegecko.min.css">
    <link rel="stylesheet" media="print" href="pub/css/print.css">
    <link rel="stylesheet" media="print" href="pub/css/print_overrides.css">
    <link rel="stylesheet" media="print" href="pub/css/tradegecko.min.css">
    <link rel="stylesheet" media="screen" href="pub/css/darkula.css">
    <link rel="stylesheet" media="screen" href="pub/css/theme_overrides.css">
    <link rel="stylesheet" media="screen" href="pub/css/tradegecko.min.css">

In my opinion there are 2 issues here:

theme_overrides.css should be included last one. This way I can override the themes without having to modify inside their files. I guess this is the purpose of this file.
tradegecko.min.css is included twice in the screen context

Thanks,
Silviu

this ambiguity is due to the overloading of the term "theme". Here it refers to the syntax highlighting theme CSS, not the --css option "theme". However, I can't see any issue in re-ordering those.
Bug, now fixed.

Fixed in<EMAIL_ADDRESS>


Fix #292

@JonnyBurger Poking in to make sure you saw the feedback on this PR!

Hi!
Yes, I mean removing the Deploy button in the readme until we we can run our unit test suite against Heroku as well as Sqlite.

@pgebheim what's the status of this?  We can't just leave these bounties in limbo.  If this is inadequate, it should be closed; otherwise merge it and let's pay out the bounty.

Postgres seems to work, I will return soon ans clean it up and ask you to review it.

PostgreSQL compatibility seems like an important piece here--is it likely this will be rebased and merged soon?

Hi guys,
added another commit so there is no merge conflict with the newest master.
You can also reach out to me e.g. on Twitter where we can chat in realtime to resolve the last few issues.

Closing -- this PR is being merged into a new PR #620

Hey @JonnyBurger  -- merged in the cleaned up version of this patch in #620!!!
Thanks for that great base to start with.

Yes!! Awesome, congrats!
Happy that it got merged.
Thanks for doing the final refactoring yourself and thanks for the collaboration opportunity!

@JonnyBurger Any chance you're on Gitcoin Slack? Would love to DM you about a few bounties to come -- great work here!

@vs77bb
Awesome, can you email me?
<EMAIL_ADDRESS>


Fixed bottom-yielding definition of toggleGroupFull

The current value of toggleGroupFull is ⊥, since it's defined as toggleGroupFull = toggleGroupFull.
Presumably, this is a typo for toggleColumnFull from XMonad.Layout.Groups.Examples.

Thanks!


base href conflict

Please, create base href replacement optionally.

Solution:
Replace

with

in
angular-cli\addon\ng2\blueprints\ng2\files\__path__\index.html

Thanks. I solved this problem by:
import {APP_BASE_HREF} from '@angular/common';

bootstrap(AppComponent, [
  ROUTER_PROVIDERS,
  provide(APP_BASE_HREF, {useValue : '/' });
]);

Closing in favor of https://github.com/angular/angular-cli/issues/1064, which is more explicit.

@fdhadzh I tried your solution but it only works for routes like this: localhost:4200/xxx.
The moment the route is one "layer" deeper it doenst work: localhost:4200/xxx/yyy or just localhost:4200/xxx/ (second slash).
This is because without a base tag the generated script tags no longer refer relative to /:
<script type="text/javascript" src="inline.bundle.js"></script>
<script type="text/javascript" src="styles.bundle.js"></script>
<script type="text/javascript" src="scripts.bundle.js"></script>
<script type="text/javascript" src="vendor.bundle.js"></script>
<script type="text/javascript" src="main.bundle.js"></script>

I want to use svg markers that require relative FuncIRIs.
@filipesilva Is this currently solvable with the current webpack setup?
Thanks.
Problem described here:
https://stacksandfoundations.com/2016/06/22/svgs-funciri-angular2-and-the-base-tag/


a possible way to make sure FeathrMvelPluginContext gets serialized and re-loaded on executor nodes

I didn't have time to try this out before going on leave, but wanted to share it with @jaymo001 as a potential fix for an issue we might encounter with the FeathrMvelPluginContext.

Close this PR as it is stale for a while. Let me know if anyone wants to reopen it.


WSL Import of squashfs

Is your feature request related to a problem? Please describe.
Some distributions ship images in squashfs format, especially for bootable ISOs.
Describe the solution you'd like
It would be great to have a native way to import this clean image into WSL using the --import command, without having to extract the squashfs to a directory, and then tar it.
Describe alternatives you've considered
I have to use the unsquashfs command from WSL or a linux machine to properly decompress the squashfs image to a directory, then TAR it back up for import. 7zip under Windows fails to extract it properly.

Importing a rando sqashfs isn't a supported scenario AFIAK. wsl.exe --import is the thing you do after an --export. Ref #2955 (message).
That said, an ask is an ask I guess.

Importing a rando sqashfs isn't a supported scenario AFIAK. wsl.exe --import is the thing you do after an --export. Ref #2955 (message).
That said, an ask is an ask I guess.

Indeed it is.
It would make evaluating certain distros within WSL far easier when all the end-user has access to is an ISO containing boot files and a squashfs.

Tar was chosen because it is a ubiquitous format that's been around forever. Marked as a feature request.

User story:
Used Debian from the store to unsquashfs the filesystem.squashfs to a directory, then used tar -pcf to turn it back into a TAR for import to WSL.
In WSL, I imported the TAR, upgraded the WSL instance, and then launched it. I am now running the distribution I wanted to test, but I was unable to do so without first having another installed WSL distribution for easy access to unsquashfs and TAR, since 7zip wasn't completely able to extract/repackage for me under Windows.

Alternatively, options maybe added in .wslconfig file, for example, bsdtarPath for path and bsdtarCommandLine for the command line of unsquashfs binary. Also those options can be use to specify other binary to extract from .tar.xz file.

Developer story: the gz limitation ties directly to what developers can use in the
WSL-DistroLauncher, as the WslRegisterDistribution thing now has the same limitation. Most distributions use more modern and efficient things like xz, zstd, and squashfs for packing; if WSL could be made to use these porting to WSL would be a lot more easier.


SPARKC-347 drop indices that can not be used in predicate push down

We store indices definitions in TableDef in order to use them in
predicate push down. As discussed, currently we do not support predicate
push down for custom and collection indices.
This commit drops these kinds of indices for TableDef#isIndexed and
TableDef#indexedColumns methods. Meaning if an index is not targeted at
single column it never participates in an evaluation of a result for
these two methods.
Nevertheless please note that all indices are present in TableDef.
Unused indices eventually are going to be used in predicate pushdown as
well.
To hide this planned changes from users, some of the TableDef properties
are now private.

Build against Scala 2.11 finished with success

Build against Scala 2.10 finished with success


fix for #121: if type is server app set name of boot.js to application.name and do not generate index.html

two approvals, merging thank you @hkollmann


Allow steam agecheck url

Allow to submit urls in this format:
https://store.steampowered.com/agecheck/app/APPID/

Done #18


double-beep: Watch +1(518)261-0913

double-beep requests the watch of the watch_number +1(518)261-0913. See the MS search here and the Stack Exchange search here.

Approved by Makyen in Charcoal HQ


Helm install nginx-ingress issue

Output of helm version:
version.BuildInfo{Version:"v3.0.3", GitCommit:"ac925eb7279f4a6955df663a0128044a8a6b7593", GitTreeState:"clean", GoVersion:"go1.13.6"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.3", GitCommit:"b3cbbae08ec52a7fc73d334838e18d17e8512749", GitTreeState:"clean", BuildDate:"2019-11-13T11:23:11Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.10-gke.36", GitCommit:"34a615f32e9a0c9e97cdb9f749adb392758349a6", GitTreeState:"clean", BuildDate:"2020-04-06T16:33:17Z", GoVersion:"go1.12.12b4", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.): GKE
Hi, im trying to install nginx-ingress controller from documentation guide >> https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-helm/#
Bu it gives me below error:
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(CustomResourceDefinition.spec): unknown field "preserveUnknownFields" in io.k8s.apiextensions-apiserver.pkg.apis.apiextensions.v1beta1.CustomResourceDefinitionSpec
Dont understand why this error, if i pulling it from stable repo.

hmm i've tested it in clean cluster, it worked. So its the issue in my environment. Im closing it.


Fixes thumbnail generation for YouTube links

Oof thinking about it
I could have just restricted the changes to neonize.aioze.preview.compose
Do I draw up a new pull request or would you merge anyways

@krypton-byte


Exo-View Hand Key Point Annotations

Hello,
I have some questions regarding 2d hand key point annotations. The dataset has 2D hand key point annotations on the exo-views, even when the hands are completely occluded.
Because there is no separate section dedicated to this part in the paper---https://arxiv.org/pdf/2311.18259, this part is a bit unclear to me, so could you please enlighten me on this?
Based on the appendix 13.D.2. 3D human hand pose from ego-video, I am guessing that, in the dataset, the 2D hand key points on the exo-views with the label "automatic" are purely estimated by off-the-shelf body pose estimation models. Thus, the annotations are there even when the hands are occluded. would it be correct?
For the key points with the "manual" label, we are certain that they are at least visible and the annotators were able to annotate them, right?
Also, some annotations are really off from other given key points. Would there be any reason or suggested way to filter them out?

Thank you so much for the clarification in advance!

Yes keypoints with tag "automatic" are projections from the 3D pose and thus can be present without a visible hand. Keypoints with "manual" tag are done by human annotators and you expect them to be only present when hands are visible.
You can run a hand detector or apply some bio-mechanical constraints to filter out big outliers.

Closing this issue for now. Please feel free to re-open it if the problem persists. Thanks!


[v3] RCTReloadNotification error

I was able to install v3 version firestack using yarn add<EMAIL_ADDRESS>which could be an issue in the first place.
Never the less I am getting RCTReloadNotification error, that I believe was resolved on master, will this fix be added to v3 any time soon?

RCTReloadNotification has been removed from RN 0.40 and newer, I guess that might be the issue.

@moooji indeed, there are few similar issues floating arround #219 and #218, with #225 actually fixing the issue, but fix hasn't been applied to v3 branch yet.

This is "fixed" in the latest version of v3, but probably not in the npm package yet. This PR https://github.com/fullstackreact/react-native-firestack/pull/240 got merged today and removed the reference to RCTReloadNotification. You should not get the error anymore when using the latest v3 from this repo (not the npm version).

Great, I'll push the next version of the next branch to npm.


Steps missing

Hello,
I think the following steps are missing:

Add NotificationDetail.xib
Update Main.Storyboard
NHInfoHubName and NHInfoConnectionString are null in getNotificationHub.

I haven't coded in objective c up until now so I might have missed something. You can double check to see if is something is missing from the tutorial. I added the credentials in getNotificationHubdirectly.

Otherwise the other steps were accurate. I found the steps for the Apple developer account explicit and helpful.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 431c3a81-db2a-b34d-0f2c-50d71dc10c49
Version Independent ID: c44dd034-b17a-663f-2f33-99c1f04edfbe
Content: Send push notifications to iOS apps using Azure Notification Hubs
Content Source: articles/notification-hubs/notification-hubs-ios-apple-push-notification-apns-get-started.md
Service: notification-hubs
GitHub Login: @sethmanheim
Microsoft Alias: sethm

@razvansalajan Thanks for the feedback! We are currently investigating and will update you shortly.

@razvansalajan Hi -- we are in the process of publishing some major updates to this article (should be within the next week or so), so please check back soon. Thank you for the feedback! #please-close


test: ignore me pls!

[!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

#4931  👈
#4930
main

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

Join @rzvxa and the rest of your teammates on  Graphite


schema: Define a relaxed schema as v1 and move current schema to v2

We introduce a relaxed schema as v1 which will accept all existing taxonomy files in the main branch of the taxonomy repo. The current v1 schema is renamed to v2 and will be used for future contributions to the taxonomy repo.
The check_yaml script is updated to allow a schema version to be specified. When the schema-version option is not specified, the script will use the latest schema version from the schema base. If the schema-version is specified as a non-positive integer, then the script will use the version key from the YAML document for the schema version to use.
The script is also changed to only check for attribution.txt when the schema version is higher than 1.
See https://github.com/instructlab/instructlab/issues/989
Depends on https://github.com/instructlab/schema/pull/11

Before merging this PR, we should probably wait until the cli containing https://github.com/instructlab/instructlab/pull/1009 is published. If we merge before then, then we will require version: 2 while the cli will not accept version: 2.

Before merging this PR, we should probably wait until the cli containing instructlab/instructlab#1009 is published.

This happened this afternoon. ilab has released v0.14.0 (aka stable) which includes the version: 2 schema support.
So we can merge this PR when the backend is ready.


GraphCore IPU Support

:tada: This PR is included in version 0.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Tus uploads on Opera Mini

Maybe we could take a look at why this might be failing and try to fix it?
Can be tested with this: http://www.opera.com/developer/mobile-emulator

Thank you for reporting this. I am able to reproduce this and will work an a fix.

Here is what I found: This issue is not directly bound to Opera Mobile but is more a problem with the Presto engine which is still used by the Mobile Emulator. Newer versions of Opera Mobile now utilize Webkit/Blink as a render engine and should not have this issue.
Anyway, Opera 12 also uses Presto which is why you can reproduce this behavior in the desktop version, too. The root cause seems to be that you cannot set custom request headers for XMLHttpRequests if the destination has a different host than your current script. It could be related to some kind of same origin policy but I need to do some more investigation.

The server has now been fixed, so even Presto works with it. Everything should be working now :)


Windows 10 Pro Insider Preview fails in uvc-wmf.cpp

Required Info

Camera Model
R200

Firmware Version

Operating System & Version
Windows 10 pro Insider Preview

Kernel Version (Linux Only)

Build System
VS2013

Every application gets the following error:
RealSense error calling rs_create_context(api_version:4):
IKsControl::KsProperty(...) returned 0x80004003
The camera was working fine on Windows 10 before I upgraded.  I may have made a mistake upgrading to the Windows 10 Pro Insider Preview.  All 3 subdevices are present in the device manager.  I tried cpp-capture but all the librealsense apps fail with this error.  The 0x80004003 is a problem with E_POINTER - bad reference provided.  It fails at "rs::context ctx;"  The failure occurs with the call:
auto it = ks_controls.find(xu.node);
with it = 0xcdcdcdcd upon return with xu.node = 1
I can back off the preview edition...

@bobdavies2000 makes me question if this is a librealsense issue or a Windows issue. It works alrighty on vanilla Windows 10. It's possible they changed implementation details of WMF in the Insider Preview, but also possible that it is just broken in that version.

Thanks for the note.  I just went back to Windows 10 and with no changes to
the hardware, everything is working fine.  They have broken the uvc-wmf
interface in that preview.
Bob

I can confirm that this problem exist on W10 Build 14352.


document issue

i'm a newer to delta, When I read Conditional update without overwrite
In this chapter, I found in IDEA that the expr method can not be resovled, and the comma is missing at the end of the code.

someone  notice before


⚠ Bofrost.lu has degraded performance

In fafe2bc, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1177 ms

Resolved: Bofrost.lu performance has improved in 3b6c43d after 7 minutes.


Are all of these prefix definitions really required?

I think they only appear in examples, but not all example-appearing prefix are defined
  AGRO:
    prefix_prefix: AGRO
    prefix_reference: http://purl.obolibrary.org/obo/AGRO_
  CHEBI:
    prefix_prefix: CHEBI
    prefix_reference: http://purl.obolibrary.org/obo/CHEBI_
  ENVO:
    prefix_prefix: ENVO
    prefix_reference: http://purl.obolibrary.org/obo/ENVO_

also re-normalize the remaining prefix definitions to the more succinct style


Have a generic ASL/LSQ video that points folks to the VRS service on pages with user generated content.

Dashboard/profile page
User Generated Content - Standard Interface Content
In email/support https://github.com/accessibility-exchange/platform/issues/1540
Any user’s page - FRO, individual, community org
My Projects for the user
Project and engagement pages
Specific resources and training modules

@michelled and @cherylhjli we'll need copy for this generic video that we can share with the translators and interpreters.

"This page has been created by another user on the website, and may not include Sign Language translations. Please call us at [phone number] through VRS and we can have this page interpreted."
How's that? Might want to check with Erik to see if that's actually how VRS works.


Spec improvements

This is a bunch of miscelaneous commits that fix and improve some stuff in our test suite. I could open separate PRs for them but they are so small that I figured I could compile them all on a single PR.

@bundlerbot r+


Can not import bambooai without setting OPENAI_API_KEY

Problem
Recent versions of openai lib require the OPENAI_API_KEY on openai.OpenAI() init.
This cascades down to bambooai on the following line (see traceback below): https://github.com/pgalko/BambooAI/blob/c292bda57d958431688c21cd62479e1ca56ec295/bambooai/google_search.py#L10
Python 3.11.0 (main, Oct 24 2022, 18:26:48) [MSC v.1933 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import bambooai
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\USER\AppData\Roaming\Python\Python311\site-packages\bambooai\__init__.py", line 2, in <module>
    from .bambooai import BambooAI
  File "C:\Users\USER\AppData\Roaming\Python\Python311\site-packages\bambooai\bambooai.py", line 15, in <module>
    from . import models, prompts, func_calls, qa_retrieval, google_search, reg_ex, log_manager, output_manager, utils
  File "C:\Users\USER\AppData\Roaming\Python\Python311\site-packages\bambooai\google_search.py", line 10, in <module>
    openai_client = openai.OpenAI()
                    ^^^^^^^^^^^^^^^
  File "C:\Users\USER\AppData\Roaming\Python\Python311\site-packages\openai\_client.py", line 104, in __init__
    raise OpenAIError(
openai.OpenAIError: The api_key client option must be set either by passing api_key to the client or by setting the OPENAI_API_KEY environment variable

Suggested solution
Since google_search.py may not be needed, maybe we can do a conditional import.
I will try to implement a fix on the weekend following best practices (conditional imports usually are not).

My bad, had a similar issue with Groq. Will fix it and push shortly.

Should be fixed now :-)

Awesome! I will test it and close after that.
Let me take the opportunity to say that I am really open to collaborate in this project, allocating some weekly hours to it if you think that should help. I could tackle minor issues like this, but let me know if you are interested in coordinating efforts!

Awesome! I will test it and close after that.
Let me take the opportunity to say that I am really open to collaborate in this project, allocating some weekly hours to it if you think that should help. I could tackle minor issues like this, but let me know if you are interested in coordinating efforts!

I would very much like that! The project might have some value for the community, but there is only so much that one person can do. It has been stagnant for last 6 months, due to me working on a different project, and I have only just resumed the development. The output formatting really needs some work, and could use some help if that is something that would interests you.  Even some sort of basic Flask app or Streamlit front end would go a long way as requested by some people.
With some smart logic we could possibly consolidate all LLM output in the print_wrapper() function in the OutputManager Class and serve it conditionally to the front end. Currently all LLM responses (and some other stuff) are printed out via this function, so maybe not too much work would be required.


Make rcon-client

It appeared that all of the robocup programs had already been built when I opened them up. This includes sslrefbox but, there is a second program that can be built in sslrefbox in the rcon-client folder. I doubt that many people will use it very often but for the sake of consistency it might be good to prebuild this one too.

:+1: on this! Whats the command to build it (is it in the same repo)?
This is the only docs I could find, its pretty bad :/
https://robocup-ssl.github.io/ssl-refbox/install.html

Ah it's here: https://github.com/RoboCup-SSL/ssl-refbox/tree/master/rcon-client

Yeah, just go into rcon-client and run Make

Fixed in 	19eb9f5


Update docs main page

This page is very outdated: https://iov-one.github.io/iov-core-docs/ Our current packages list is
@iov/bcp
@iov/bns
@iov/bns-governance
@iov/cli
@iov/crypto
@iov/dpos
@iov/encoding
@iov/ethereum
@iov/faucets
@iov/jsonrpc
@iov/keycontrol
@iov/lisk
@iov/multichain
@iov/rise
@iov/socket
@iov/stream
@iov/tendermint-rpc

Also there is no such thing as "Main entry package" anymore.
This file needs to be updated on master: https://github.com/iov-one/iov-core-docs/blob/master/index.html and will then be included in the gh-pages branch automatically in the next iov-core build.

Done, see https://iov-one.github.io/iov-core-docs/


Bulk Delete

Thanks for this app, I've plugged it in and it looks good for all my needs except there is no bulk_delete option.  Please may you add this feature and in the meantime point to the section of the documentation which explains how I can bulk create manual audit logs for each object I'm about to delete in bulk.
I'm a little miffed why bulk_create and bulk_update were both added to this app but this wasn't.
UPDATE
I think I've got the right code now so my question has been answered.  But another has now arisen, see below.
def bulk_delete_with_history(objects, model, batch_size=None, default_user=None, default_change_reason="", default_date=None):
    """
    The package `simple_history` does not log what was deleted if the items
    are deleted in bulk.  This does.
    """
    model_manager = model._default_manager
    model_manager.filter(pk__in=[obj.pk for obj in objects]).delete()

    history_manager = get_history_manager_for_model(model)

    history_type = "-"
    historical_instances = []
    for instance in objects:
        history_user = getattr(
            instance,
            "_history_user",
            default_user or history_manager.model.get_default_history_user(
                instance),
        )
        row = history_manager.model(
            history_date=getattr(
                instance, "_history_date", default_date or timezone.now()
            ),
            history_user=history_user,
            history_change_reason=get_change_reason_from_object(
                instance) or default_change_reason,
            history_type=history_type,
            **{
                field.attname: getattr(instance, field.attname)
                for field in instance._meta.fields
                if field.name not in history_manager.model._history_excluded_fields
            }
        )
        if hasattr(history_manager.model, "history_relation"):
            row.history_relation_id = instance.pk
        historical_instances.append(row)

    return history_manager.bulk_create(
        historical_instances, batch_size=batch_size
    )

The problem though is a signal is sent for each object deleted by -
model_manager.filter(pk__in=[obj.pk for obj in objects]).delete()
So I need to disconnect this signal but I'm struggling.  I've tried this, where Customer is just a class of mine I'm testing.
models.signals.post_delete.disconnect(HistoricalRecords.post_delete, sender=Customer)
Any ideas?  I notice you guys add the signals using models.signals.class_prepared which is unusual for third party packages as per the Django docs.
UPDATE 2
https://stackoverflow.com/questions/64089809/is-there-a-way-to-disconnect-the-post-delete-signal-in-simple-history/64092484#64092484
I made a classic mistake with disconnecting signals. One must of course disconnect with the object that was connected. This is discussed here in more detail - django signal disconnect not working
This now works because I am disconnecting with reference to the correct object.
        receiver_object = models.signals.post_delete._live_receivers(Customer)[0]
        models.signals.post_delete.disconnect(receiver_object, sender=Customer)

Still, I think it would be nice if django-simple-history provided a bulk_delete utility function like they provide one for bulk_create and bulk_update.

@ddabble Would be really cool to have this. Would you accept an MR with this code?
@rossm6 Would you be able to make an MR with this snippet or could I just create one with your code?

@rossm6 Thanks for creating this issue and investigating the signal part 🙏🏻
We tried your proposal to disconnect the post_delete() signal but unfortunately it did not work for us (the receiver object reference found within _live_receivers was not the same than in receivers).
Only the following worked instead:
    receiver_object = None
    for receiver in models.signals.post_delete.receivers:
        (_, sender_id), receiver_ref, weak_ref = receiver
        if sender_id == id(model):
            receiver_object = receiver_ref
            break
    if receiver_object:
        assert models.signals.post_delete.disconnect(receiver_object, sender=model)

where model is a model class that we pass to the bulk_delete_with_history function.


Indeterminate Linear Progress Bar

Area
UI Components
The problem
We can use spinner to represent indeterminate state of circular progress, but can't find an equivalent for linear progress
The solution
Someting like
https://mui.com/material-ui/react-progress/#linear-indeterminate
Alternatives and examples
/
Are you a JPMorgan Chase & Co. employee?

[X] I am an employee of JPMorgan Chase & Co.

Code API needs to be updated, around default variant and value=undefined

Zazu Goal: S(3)

Zhihao to pickup
ready for Core by EOS

@navkaur76 to add required updates to (Next) library.

Jul 1 - Found some problems with new indeterminate implementation on buffer. Also changing site examples to remove radio toggle.

Jul 3 - updated site examples, doc wording, rearranged examples. #3429 ready for review

Figma updates complete + branches merged by Yun.

Released in code in<EMAIL_ADDRESS>


Snakemake v8.25.0 error

DENIS hits an error with snakemake v8.25.0:
rule all:
    input:
        output_files
    message: f"Pipeline done. Started {start_time}"

^ Seems to be from line 54 of the Snakefile.
Downgrading snakemake to v7.3.7 resolves the error.

Please excuse the wait time, this turned out to be three different issues at once, which resulted in a lot of trial and error on my side.
The first error did occur because of a missing new line at the end of my Snakefile. Older versions of Snakemake were fine with this but newer versions (e.g. Snakemake 8.25.0) are not. This is fixed and already on the main branch (#2).
The second error, which you reported for Snakemake 7.3.7 is a known bug caused by a dependency (see here). It can be manually fixed by installing tabulate=0.8.10 but is also fixed in Snakemake >=7.15.2.  Upgrading Snakemake to 8.25.0 led me to the third bug, which is discussed here. From what I can tell, this was introduced with Snakemake 8 and unfortunately does not have a solution, yet. My recommendation is to use Snakemake >=7.15.2,<8.
Tldr: This pipeline is broken in Snakemake >=8. Use one installed with e.g. this: mamba install "snakemake>=7.15.2,<8".