git-user command does not work reliably

In the example below, the setting does not work at all

I have also experienced a weird edge case where git-user only sets user.name, but user.email remains unchanged.

This problem maybe come with if your local or global git user info is inComplete
First, you can check your local git user info in git project directory with
git config --list
The first user.name or user.email to appear is git config global user info
Then the second  user.name or user.email to appear is git config local user info
You can reset git user info with below command

gloabl: git config --global --unset user.name, git config --global --unset user.email
local: git config --unset user.name, git config --unset user.email

After that, try git-user again, then you set the git config in right way

Weird, but I noticed this issue as well. For my particular use case, I don't care if I have to use this command twice, but there is something wrong definitely.

@eJayYoung You're right! This was because I did not have a global user setup. You can use git-user for that as well.
Just run: git user --global
and setup the global user.


[modify][rss] reduce weather xml cache consumption

Coverage increased (+0.01%) to 84.664% when pulling 35a0935da54ca3901669a293662dfdedac361a9c on features/reduce-weather-xml into 5a56c44126efa67f1868022393406c62fe38c293 on master.


[BUG] teamManifestDir not working?

Reading the documentation for teams, it doesn't seem like I can get the teamManifestDir working based off the instructions or copying the patterns example
My repo is here. The namespace is created for the team but the manifest is never applied.

@CarmenAPuccio I was able to replicate the issue. I'm taking a look at the bug to ensure we are reading in the path correctly. Will let you know when the fix is in.

@CarmenAPuccio this is fixed in https://github.com/aws-quickstart/cdk-eks-blueprints/pull/365  and released.

Confirming it works now. Thanks so much!


Clippy lint clippy::str_to_string fails on generated commands with String arguments

I run a fairly extensive set of lints on my projects. Since updating Poise from 2746481a6cef9c141ac7940b5f1eed240dff33a8 to 60106518ea0ec5940682a724c257b246ff8ac2b2, I've found  that the lint clippy::str_to_string warns for commands that have String arguments.
#![warn(clippy::str_to_string)]

#[command(prefix_command)]
pub async fn some_command(
	ctx: PoiseContext<'_>,
	#[rest]
	#[description = "Some description."]
	command: String,
) -> Result<(), Error> {
	Ok(())
}

Warns with the following error:
warning: `to_string()` called on a `&str`
  --> src\commands\mod.rs:40:1
   |
40 | #[command(prefix_command)]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = help: consider using `.to_owned()`
   = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#str_to_string
   = note: this warning originates in the macro `$crate::_parse_prefix` (in Nightly builds, run with -Z macro-backtrace for more info)

It seems to only be with prefix_command, not slash_command. Not a huge deal at all, but I thought I'd mention it.

Thanks for the report
Fixed in 7830e76010621ca8a380ef537534ae1ed9b725e9
If you don't mind, can you give me the list of clippy lints you use? I'll put them into the example code to make sure the generated code doesn't trigger them again

Sure, here's the list I'm running: https://github.com/zedseven/radium/blob/dev/src/main.rs#L4-L38
Keep in mind these are partly personal preference and there's quite a few, so you don't have to set them up.


[question] How to run a notifier on the invoked task only?

So I've been using gulp-notifier to display notifications for each Gulp task. Unfortunately I wasn't able to configure it in a way that it would only run on the invoked task and not on all sub-tasks, because I'd like to have popup notififytions only on the initially invoked task.
What I tried now is to wrap the actual Gulp task function to add code which triggers a notification when needed. The wrapper looks like this and seems to work for my tasks:
var gulp = require('gulp');
var notifier = require('node-notifier');
var task = require('./task.js');

gulp.task(task.displayName, function(callback) {
	var notify = function() {
		notifier.notify('DONE.');
	};

	var result = task(function() {
		notify();
		callback();
	});

	if(result) {
		if (result.constructor.name == 'DestroyableTransform') {
			result.on('end', notify);
		} else if (result.constructor.name == 'Promise') {
			result.then(notify);
		}
	}

	return result;
});

This wraps the actual Gulp task which is loaded via require and tries to run the notifier on the end of the task. (At the moment it runs for every task.)
Is this the right way to go? Is there an easier and/or more compatible way to achieve this?
I'd like to not use a Gulp plugin for this, because I don't want people to actually know how to add the notifier within a task. Notifications should just work "out of the box" without adding logic within a task function.
Thanks!

Support questions should be directed to StackOverflow.

Indeed, done that now; I wasn't sure if this was the right place, although there were issues tagged with question, so I tried. ;) Thanks!

Sorry, questions are usually flagged when I'm not sure if an issue exists that needs to be fixed. Usually they are paired with "needs further investigation".

I see. :)


Java toolchain support: failed to create parent directory /tmp/expandedArchives/...

Expected Behavior
No exception during unpacking of downloaded JDK.
Current Behavior
Exception during unpacking of downloaded JDK.
Context
Linux
Gradle 6.8.2
build.gradle of user 1:
  test {
        javaLauncher = javaToolchains.launcherFor {
          languageVersion = JavaLanguageVersion.of(8)
          vendor = JvmVendorSpec.ADOPTOPENJDK
        }
  }

build.gradle of user 2:
  test {
        javaLauncher = javaToolchains.launcherFor {
          languageVersion = JavaLanguageVersion.of(11)
          vendor = JvmVendorSpec.ADOPTOPENJDK
        }
  }

Developer very happy about new toolchain feature of Gradle.
Steps to Reproduce

Run gradle with user 1 using toolchainspec A.
Run gradle with user 2 on same host using toolchainspec B.
Observe exception:

   > Unable to download toolchain matching these requirements: {languageVersion=8, vendor=ADOPTOPENJDK, implementation=vendor-specific}
      > Could not copy tar entry /home/matthias/.gradle/jdks/adoptopenjdk-8-x64-linux.tar.gz!jdk8u282-b08/ to '/tmp/expandedArchives/adoptopenjdk-8-x64-linux.tar.gz_5e11782de1d81f0b251caf949abef794/jdk8u282-b08'.
         > Failed to create parent directory '/tmp/expandedArchives/adoptopenjdk-8-x64-linux.tar.gz_5e11782de1d81f0b251caf949abef794' when creating directory '/tmp/expandedArchives/adoptopenjdk-8-x64-linux.tar.gz_5e11782de1d81f0b251caf949abef794/jdk8u282-b08'

User 2 cannot unpack JDK, because user 2 tries to re-use temporary directory created by user 1.
Your Environment
See context.

Come on, people! Perfect reproduction instructions, culprit easily locatable in the source code, simple solution (random name for temporary directory instead of "expandedArchives"). This is low hanging fruit.

Closing this issue, because it's obsolete.
/tmp/expandedArchives is no longer involved in toolchain auto-provisioning in recent Gradle versions.


The message "Problem occurred while parsing the software Package" is displayed during Android Software installation.(2.4)

Per Mattermost guidelines, GitHub issues are for bug reports: http://www.mattermost.org/filing-issues/.
For troubleshooting see: http://forum.mattermost.org/.
For feature proposals see: http://www.mattermost.org/feature-requests/
If you've found a bug--something appears unintentional--please follow these steps:

Confirm you’re filing a new issue. Search existing tickets in Jira to ensure that the ticket does not already exist.
Confirm your issue does not involve security. Otherwise, please see our Responsible Disclosure Policy.
File a new issue using the format below. Mattermost will confirm steps to reproduce and file in Jira, or ask for more details if there is trouble reproducing it. If there's already an existing bug in Jira, it will be linked back to the GitHub issue so you can track when it gets fixed.

Summary
Bug report in one concise sentence
The message "Problem occurred while parsing the software Package" is displayed during Android Software installation.
Environment Information

Device Name:Xiaomi K30 (MIUI 10.0.13)
OS Version: Android:10
Mattermost App Version:2.4 mobile apk
Mattermost Server Version:7.10.2

Steps to reproduce
How can we reproduce the issue (what version are you using?)
Mattermost-unsigned.apk   V2.4
Expected behavior
Describe your issue in detail
The message "Problem occurred while parsing the software Package" is displayed during Android Software installation.
Observed behavior (that appears unintentional)
What did you see happen? Please include relevant error messages, screenshots and/or video recordings.
Possible fixes
If you can, link to the line of code that might be responsible for the problem
possible cause:
Generally speaking, this problem is caused by the installation of the mobile phone can not install the software, that is, the minSdkVersion version does not support the mobile phone.

I think I haven't understood your issue. Is it an error when you are installing the latest apk downloaded from the releases page? Or is it something different?
If so, have you tried with older versions (2.3, 2.2...)? Do they install correctly?

It won't ever install as you are trying to install an unsigned version my friend. You either need to sign it or use the signed apk that matches your arch or use the play store

unsigned version

I use this version, may be this reason, I downloaded the mobile source code, how to compile into the signed version, is there any documentation or video tutorial, thank you.


[Ported PR] Update Text

A few PRs have come into the Git-it verify scripts since I ported it over here. I'll need to make those updates here so I'm creating issues for them.
https://github.com/jlord/git-it/pull/197

Closing this one because I think the UI is different again since this update, so will catch this in a bigger update text run through.


Changing the name of createdAtColumn and updatedAtColumn

I have a question regarding this 2 columns.
How can you change this fields names? Seems they have hardcoded names.
I find it a bit wired. It is not practical at all. I mean is ok when you want to bootstrap something fast, but if you want to integrate adonis with a shared database, then it will not really work. I have in my table a created and updated column, but adonis wants created_at and updated_at.
I really like the framework, but something like this makes me thinking twice before using it in an old project.

Been covered in the docs
class OompaLoompa extends Model {
  static get createdAtColumn() {
    return 'made_at_this_date'
  }

  static get updatedAtColumn() {
    return 'been_updated_at_this_date_yo'
  }
}

Also for these types of questions better use the forum or discord.

yeah ... I miss read that section.
Thanks a lot for the help.


lfec doesn't set the exit code correctly under unix when compilation fails.

I run this in a shell:
echo "invalid code" > foo.lfe
lfec foo.lfe && echo "This is wrong" || echo "Yay, it works"

The output is
./foo.lfe:1: bad module definition: name
./foo.lfe:1: unknown form
This is wrong

I.e. lfec claim it succeeded.

Ordinarily, I would put the offending code into a function, do a try/catch and then halt with the appropriate code, e.g.:
(try
  (compile)
  (catch (_ (halt 127))))

In this case, that doesn't work. If Robert doesn't get to it sooner, I'll take a look at lfe_comp and see how it's handling a bad file (it's not a simple exception, or the above would work).

Alright, I had a chance to take a look at this. lfe_comp doesn't throw an error because it needs to track all possible failures (if 100 files are compiled, it wants the user to see a report with all of them, and not have to run 100 compiles after fixing each file individually).
As such, lfe_comp:file returns a tuple of {error, Errors, Warnings}.
I've got a patch ready that does (halt 1) in lfec when there is {error, Errors, _} but not {error, [], Warnings}. I'll submit it for Robert's review later today.
Thanks for the catch!

Lfe_comp should never return {error,_,_} unless there are errors. If there are only warnings and no errorrs then it returns {ok,_,_}. The actual errors and warnings are only returned if return is an options and only printed if report is an option.

Ah, good to know -- I'll turn off return then and just check for error. That'll be much cleaner :-)

This has been fixed.


Research 2nd server-side API

researched 2nd api:
https://api.themoviedb.org/
Used for Upcoming Movies: Users can click on the "Upcoming Movies" button to fetch the data from an API and display the upcoming movies.
const searchMoviesURL = https://imdb-api.com/en/API/SearchMovie/${apiKey};


Does it work inside Docker?

It's not working in my case. No any errors while installation:

I am using Jupyter inside the Docker, could it influence?

The server extension will be available after the server has been started. It won't be available immediately after you've installed it in a running server.
If you install the extension as part of your docker build then the extension will be available when you run the container. If you install the extension within your container on part of a file system that gets recreated when your container restarts, it won't be available.

Thanks for your answer!
It runs after server which hosts docker restart.
Thanks a lot for this cool tool!


page.type() doesn't work with date inputs

It's not really an issue with Puppeteer, but maybe you guys can advise 🙏
I'm devving a chrome extension and it uses devtools protocol to emulate input to fill in forms.
I use Input.insertText - same as Puppeteer. The prob is - it works for text inputs, but not for date inputs (<input type='date' />). Inputs simply ignore it.
Wherein Input.dispatchKeyEvent works just fine. But then I have to iterate over all the text characters - which is not what was my intention.
I've tried Puppeteer's .type api with date inputs and it works as intended. I've checked out the source at https://github.com/GoogleChrome/puppeteer/blob/master/lib/Input.js#L158 and it uses Input.insertText - just like I do.
So how can it be - that Puppeteer's input goes through - and mine doesn't.

same problem, puppeteer can't type or assign value to input type='date' fields.
tried
await page.type("[name='j_idt31:an_ugly_form_input']", "17-02-2019");
I am using waitForNavigation & waitForSelector before typing, so page is loaded well.
It open up calender picker as I can see in head-mode but can't type date into it.
looks like input box accept certain format or something.
P.S: I can easily type or assign value in developer console, tried page.evaluate as well.

@uzair004 , maybe this is the format. If the fake browser you are using is in en-US, it will expect that you type 02/17/2019.

@darakeon actually changing focus on date field then typing works for me, I realize there is readonly attribute I had to remove as well.
Now the problem is page.type is messing up the text I am providing to write in input field. Sometimes characters order changes.
    await page.focus("[name='j_idt31:verisysForm:issuedate_input']");
    await page.$eval("[name='j_idt31:verisysForm:issuedate_input']", (e) =>
      e.removeAttribute("readonly")
    );
    await page.type("[name='j_idt31:verisysForm:issuedate_input']", issueDate);

Please re-try with the latest Puppeteer version and using the hints from other commenters. If it's still the issue, please re-open with a recent repro script.


added flow dedupped table

we shouldn't be adding gold tables as sources

this isn't a real gold table it's not built in DBT it is also a hot fix for a console thing for flow for a 3-1-1 issue.


Joining and Starting Lobby works

Lobby can be joined by multiple users
Host can start the game for everyone

closed in: 81c9039

https://github.com/sopra-fs24-group-46/client/commit/247e6f3739876518261cc9457a441392f26d9697


[SPARK-21418][SQL] NoSuchElementException: None.get in DataSourceScanExec with sun.io.serialization.extendedDebugInfo=true

What changes were proposed in this pull request?
If no SparkConf is available to Utils.redact, simply don't redact.
How was this patch tested?
Existing tests

Test build #81388 has started for PR 19123 at commit 735ca94.

Test build #81388 has finished for PR 19123 at commit 735ca94.

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

Merged build finished. Test PASSed.

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

LGTM, merging to master/2.2. Thanks for picking this up!


Query protocol bloaty

AnySearch module can be merge into DQuery and Document and DString and be removed
Search results from any DQuery should return context (the address)
Search should allow for querying any state "created at" and "last edited at"

Blocked by #11


how to set "max.request.size" for a Stream producer thread?

Hi All/@sobychacko, @sabbyanandan, @garyrussell ,
To resolve "org.apache.kafka.common.errors.RecordTooLargeException" I made following changes.

message.max.bytes=9000000 -- increased value in kafka server.properties
spring.cloud.stream.kafka.streams.bindings.<channel name>.producer.configuration.max.request.size: 9000000

But the changes, made in the spring configuration doesn't seem to be effective, as I couldn't see this change is getting printed in my log file. SerDe configured similar way is getting reflected.
spring.cloud.stream.kafka.streams.bindings:
.producer.keySerde: com.xxx.processor.model.serde.ABCSerde
.producer.valueSerde: com.xxx.processor.model.serde.XYZSerde
Kindly advice, is there any other change I need to add?
Regards.

@sobychacko thank you, for the quick response.


HandleFuncs can now be Type Methods as well.

http.HandleFunc documentation was not discovered because only
first class functions were traversed when building apib documentation.
Now both first class functions and type methods are traversed.
For example:
type WidgetController struct {}

// GetTypeWidget retrieves a single Widget
func (* WidgetController) GetWidget(w, r) { }

Hi! Thanks so much for the PR, I'm sorry I haven't had a chance to review your code yet, things have been busy with work and Women Who Go. I will try to review your code this weekend.
Sarah

Hi Sarah,
funny when you said Women Who Go at first, I thought you meant the go board
game. After googling your organization, I am very impressed with what you
are doing! I am using your library for a work project, I work with
INgrooves music in Victoria B.C. Canada. It seems my PR's tests are failing
at the moment. Let me look into this as soon as I have more time.
Cheers, Ivan
--
Ivan
On Wed, Jun 22, 2016 at 5:55 PM, Sarah Adams<EMAIL_ADDRESS>wrote:

Hi! Thanks so much for the PR, I'm sorry I haven't had a chance to review
your code yet, things have been busy with work and Women Who Go. I will try
to review your code this weekend.
Sarah
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/adams-sarah/test2doc/pull/2#issuecomment-227920814,
or mute the thread
https://github.com/notifications/unsubscribe/APx-82uVfbjB4MIZrWkp1uqyExO5jM2eks5qOdmRgaJpZM4I2yaK
.

Yea, the tests were already broken. You can run the example pkg tests and check the output manually.
You've rewritten all the imports to github.com/ivaningrooves/test2doc instead of github.com/adams-sarah/test2doc so there's no way I can merge this ATM.

Yes, how would you do this if you were me? The PR contains 2 commits; the
first one is the actual change, the second involves the import rewrite so I
was able to confirm it works locally.
--
Ivan
On Mon, Jul 18, 2016 at 9:57 AM, Sarah Adams<EMAIL_ADDRESS>wrote:

Yea, the tests were already broken. You can run the example pkg tests and
check the output manually.
You've rewritten all the imports to github.com/ivaningrooves/test2doc
instead of github.com/adams-sarah/test2doc so there's no way I can merge
this ATM.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/adams-sarah/test2doc/pull/2#issuecomment-233389764,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APx-8_WlDSgAntfP_A3vCrP9oGg9aTFgks5qW7BwgaJpZM4I2yaK
.

Ah, so pull requests are based off branches. So you need to get rid of the second commit in this branch.

Hope that helps!

Thank you!
You should be able to build & run the PR now.
--
Ivan
On Mon, Jul 18, 2016 at 10:48 AM, Sarah Adams<EMAIL_ADDRESS>wrote:

Ah, so pull requests are based off branches. So you need to get rid of the
second commit in this branch.

Hope that helps!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/adams-sarah/test2doc/pull/2#issuecomment-233404012,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APx-8_ORsd0KggMpi2kMYxk7bmuA_OSsks5qW7xhgaJpZM4I2yaK
.

Hm, it looks like the imports are still pointing at your code and not mine.
Did you follow the steps I outlined above? Or did you do something else

It looks like you deleted my example pkg too :(

Hi Sarah,
I did remove the changes from the PR but I had to add them back to my fork
to not break my companie's CI pipeline. I don't understand why my second
revision gets added to the PR automatically. I might have to create a new
PR... Give me moment to fix it.
--
Ivan
On Mon, Jul 18, 2016 at 4:28 PM, Sarah Adams<EMAIL_ADDRESS>wrote:

It looks like you deleted my example pkg too :(
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/adams-sarah/test2doc/pull/2#issuecomment-233489368,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APx-85xaqHqGfQurZL7N0xdO8w95_Mgqks5qXAwegaJpZM4I2yaK
.

I created a new PR https://github.com/adams-sarah/test2doc/pull/3

See #3


train on a custom dataset

I'm trying to train surfemb on a custom dataset. But when I do inference, I find some files/dirs are musts(they're  detection_results, surface_samples, surface_samples_normals).
For dectection_results, I've already known it's from CosyPose,  but I don't know how to generate it in detail.
For surface_samples, I followed your guidance that  run command $ python -m surfemb.scripts.misc.surface_samples_remesh_visible clip first. But I encountered this error:
Traceback (most recent call last):
  File "/root/miniconda3/envs/surfemb/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/root/miniconda3/envs/surfemb/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/root/surfemb/surfemb/scripts/misc/surface_samples_remesh_visible.py", line 32, in <module>
    ms.compute_scalar_ambient_occlusion(occmode='per-Face (deprecated)', reqviews=256)
AttributeError: 'pymeshlab.pmeshlab.MeshSet' object has no attribute 'compute_scalar_ambient_occlusion'

Could you please give me any suggestions on these two problems?

The second problem has been addressed. coverting pymeshlab to version 0.2 works.

Thank you. I've been studying cosypose's codes these day, and your suggestions help me a lot.

The second problem has been addressed. coverting pymeshlab to version 0.2 works.

Hi LeroyChou , I am having similar problem with pymeshlab
After changing pymeshlab version to 0.2 , how did you change these 3 lines in suface_samples_remesh_visible.py in misc folder. Because in that version, some functions are renamed or changed. so pymeshlab says it has no attribute ...
ms.repair_non_manifold_edges_by_removing_faces()
ms.subdivision_surfaces_midpoint(iterations=10, threshold=pymeshlab.Percentage(args.remesh_percentage))
ms.ambient_occlusion(occmode='per-Face (deprecated)', reqviews=256)

thanks in advance

The second problem has been addressed. coverting pymeshlab to version 0.2 works.

Hi LeroyChou,  I am having problem with
ms.ambient_occlusion(occmode='per-Face (deprecated)', reqview=256)
this line stops the code without giving any error. Did you have the same problem? if so, how did you solve it?
thanks in advance

The second problem has been addressed. coverting pymeshlab to version 0.2 works.

Hi LeroyChou, I am having problem with
ms.ambient_occlusion(occmode='per-Face (deprecated)', reqview=256)
this line stops the code without giving any error. Did you have the same problem? if so, how did you solve it? thanks in advance

hello.
yes I was troubled by the same problem. My solution is converting the pymeshlab's version to 0.2 and it works in my case.


docs removed

Probably it only requires in addition removing webhook, but @ankit27kh please check.

Probably it only requires in addition removing webhook, but @ankit27kh please check.

webhook removed. readthedocs project deleted


operator cert-manager (1.8.2)

Signed-off-by: Richard Wall<EMAIL_ADDRESS>

/merge possible

/retest

/merge possible


python39Packages.aiohttp build failure on x86_64-linux as of b9e05544

Issue description
Build of python39Packages.aiohttp failed on x86_64-linux as of b9e05544c9b0a382d3416d602791a63ec2e63217. This is currently breaking python39Packages.tensorflow-datasets.
error: builder for '/nix/store/knjg6d8w9l90n9qjpbx1aq2fsq12g03l-python3.9-aiohttp-3.8.4.drv' failed with exit code 1;
       last 10 log lines:
       > XFAIL test_client_functional.py::test_broken_connection[pyloop]
       > XFAIL test_connector.py::test_del_with_scheduled_cleanup[pyloop]
       > XFAIL test_web_functional.py::test_http10_keep_alive_default[pyloop]
       > XFAIL test_web_server.py::test_unsupported_upgrade[pyloop] - The behavior of C-extensions differs from pure-Python: https://github.com/aio-libs/aiohttp/issues/6446
       > XFAIL test_web_urldispatcher.py::test_decoded_url_match[pyloop-urldecoded_route] - Regression in v3.7: https://github.com/aio-libs/aiohttp/issues/5621
       > XFAIL test_web_urldispatcher.py::test_decoded_url_match[pyloop-urldecoded_route_with_regex] - Regression in v3.7: https://github.com/aio-libs/aiohttp/issues/5621
       > XFAIL test_web_urldispatcher.py::test_decoded_url_match[pyloop-urlencoded_route] - Regression in v3.7: https://github.com/aio-libs/aiohttp/issues/5621
       > ERROR test_web_sendfile_functional.py::test_static_file_if_none_match[sendfile-pyloop-additional_etags1-Fri, 31 Dec 9999 23:59:59 GMT] - pytest.PytestUnraisableExceptionWarning: Exception ignored in: <coroutine o...
       > = 2556 passed, 17 skipped, 6 deselected, 7 xfailed, 1 error in 240.67s (0:04:00) =
       > /nix/store/74l4x6m97bvry7ccxv51h952ayvg2j46-stdenv-linux/setup: line 1596: pop_var_context: head of shell_variables not a function context
       For full logs, run 'nix log /nix/store/knjg6d8w9l90n9qjpbx1aq2fsq12g03l-python3.9-aiohttp-3.8.4.drv'.
error: 1 dependencies of derivation '/nix/store/kw0x60w0lxcprc1gdyiwrhxazp7ji6s9-python3.9-datasets-2.12.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/j5bkfd1jbyvz3c30l1hwd0bhk9p7wfc1-python3.9-fsspec-2023.4.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/7a1zcgl7vyvfdx47h7rlqi3894m6vcwc-python3.9-google-auth-2.19.1.drv' failed to build
error: 1 dependencies of derivation '/nix/store/g764y43dckf26rw7nk56x79ih3f6a25q-python3.9-tensorflow-datasets-4.8.2.drv' failed to build

full build log
python39Packages.tensorflow-datasets maintainers cc: @ndl
python39Packages.aiohttp maintainers cc: @dotlambda
Other cc: n/a
Steps to reproduce

Checkout nixpkgs at commit b9e05544c9b0a382d3416d602791a63ec2e63217
Run nix-build -A python39Packages.aiohttp

Technical details
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.0-1038-azure, Ubuntu, 22.04.2 LTS (Jammy Jellyfish), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.16.1`
 - nixpkgs: `/nix/store/7qmvrn8r4gj590k780r4pr85mgw7qg80-source`

Contents of ~/.config/nixpkgs/config.nix:
{ allowUnfree = true; cudaSupport = true; cudaCapabilities = ["8.0"]; }

Misc.
This issue was automatically generated by nixpkgs-upkeep.

CI workflow that created this issue.
Internal tags:<PHONE_NUMBER>920603416<PHONE_NUMBER>348592529

greetings ! @samuela
I cant reproduce the build issue ( thats on x86_64-linux )
git checkout b9e05544c9b0a382d3416d602791a63ec2e63217
HEAD is now at b9e05544c9b Merge pull request #236466 from SuperSandro2000/dnscontrol

[kirillvr@osaka:~/nixpkgs]$ nix-build -A python39Packages.aiohttp
/nix/store/0ic1yscpxv6w2dpvajr04wys119fs95g-python3.9-aiohttp-3.8.4

try flake
nix build github:nixos/nixpkgs?rev=b9e05544c9b0a382d3416d602791a63ec2e63217#python39Packages.aiohttp
I've noticed from your build log derivation hash doesn't match to what I get

same issue, but for python3.10-aiohttp-3.8.4

aiohttp has flaky tests (python3.11-aiohttp-3.8.4 on armv7l-linux). Restarting the build usually fixes the issue.

Ah well that makes sense... We should skip the flaky tests or fix them somehow

I was able to reproduce this since upgrading to 23.05. On all my build machine the behavior seems to be consistent: it fails when there are other active build jobs, but the test can pass when aiohttp is the only active build job at the time.

builds on nixos-unstable


Stories optimisation

Background
There are a number of challenges that exist around how we currently allow users to access stories on the site. We want to address these challenges and put in place a number of optimisations, being mindful of the work around discoverability / concepts that will be coming at a point in the future.
User story
As a product owner
I want to understand the current pain points and opportunities that sit within Stories
To enable us to prioritise and implement changes that will improve these
Acceptance criteria

Gain a clear understanding of user needs
Gain a clear understanding of organisational needs
Prioritised view of changes based on value and feasibility

I'm going to close this as done – this was a precursor to the Stories optimisation work we've been doing. There's more work to do here, but we should create a new ticket if/when we want to make the next round of improvements.


Fix #2844 - IOS

This fixes the issue of Toast hiding behind the keyboard in ios. #2844 was reported for android but it was working fine in android.

Looks good @PlabanJr! Can you please attach a gif as well?

@sankhadeeproy007


(dependency) clean up routing

(DONE) ng-repeat logic for displaying random question result to same page
http://www.java2s.com/Tutorials/AngularJS/AngularJS_Example/Directives/data_ng_repeat_Loop_through_two_dimensional_array.htm
(DONE) display max number of questions available
(DONE) add form validation for min and max input values

if plan to update routes, there is a dependency on this feature https://github.com/cch5ng/angular_front_end_interview/issues/7

currently routing looks ok (except nav menu styling)
need to resolve issue with template and data manipulation for coding questions

perhaps it makes more sense to use the static html content from dillinger results


Bump to ginkgo v2

This will help https://github.com/cloudfoundry/cli/pull/2378 in getting to ginkgo v2 as ykk is used in there

turns out this isn't necessary for https://github.com/cloudfoundry/cli/pull/2378 cause I didn't understand initially where ginkgo v1 was being pulled from.  Still seems valuable to keep it up to date here since this is a dependency of the cli (though maybe this dependency is unnecessary since long ago with that go bug/issue?)


Add namespace to zipkin-to-stackdriver yaml file.

Redo fix for #2333

Hi @bianpengyuan. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

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

/assign @douglas-reid

/lgtm
/approve

/ok-to-test

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

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
d2b2c1a13a77c7b1563f9424f91ab041c17b9c81
link
/test istio-pilot-e2e

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

this file is gone, only the template should need edit

Thanks for the contribution!  As @ldemailly mentioned - PR https://github.com/istio/istio/pull/3481 removed this "generated" file.  Currently we are maintaining the templates that are generated here: https://github.com/istio/istio/tree/master/install/kubernetes/templates.  Note this is subject to change in the near future.


Not picking url from Shared Data in ios

Hi, currently the react-native-share-menu not picking the url from shared data in ios.
so sharedData that I'm getting when sharing from imdb ios app is -
Breaking Bad (2008–2013)
A high school chemistry teacher diagnosed with inoperable lung cancer turns to manufacturing and selling methamphetamine in order to secure his family's future.
but the data I want to get is (which other apps are able to get)  -
Breaking Bad (2008–2013)
A high school chemistry teacher diagnosed with inoperable lung cancer turns to manufacturing and selling methamphetamine in order to secure his family's future.
https://www.imdb.com/title/tt0903747/
PS: the screenshot attached of gmail.

@RajanCurateus  Any update on this? How did you resolve the issue of the data being null?


Preview does not render correctly

The preview window does not show the UML correctly. Please see the attached image.
The export does it correctly with background color.

Correct:

I found a solution. I just need to add on top
skinparam style strictuml
So it looks like:
@startuml
skinparam style strictuml
class Test {
    +string ToString()
}
@enduml

Thank you for you feedback!


[discussion] add —watch to the wireit command as an option

was curious about the reason behind the —watch flag not being able to be added to the wireit command directly?
imo, it would be super useful to be able to do
“scripts”: {
  “dev”: “wireit —watch” //always watch mode
}

imo it’s a bit clunky to have to send the “--watch” flag with the runner command , ie npm/yarn/pnpm run rather than being able to bake it into the command by default.
i have a command similar to the above and i always forget that i need to call it with the —watch flag manually.

I've also noticed this and wondered if this should actually be part of the wireit config. It happens that almost all of my --watch commands are services that deserve a watch flag in their own "command" such that they can't really beat  run without --watch anyways...

+1 to a watch: true config option as well. imo either could be great

A watch: true would be useful, when I first read the documentation I felt it was strange that this wasn't already possible

I think these are valid suggestions. I suppose workaround for now would be to do something like
"scripts": {
  "dev:base": "wireit",
  "dev": "npm run dev:base --watch"
}

so npm run dev will always watch.

Yeah, I'm open to either "watch": "wireit --watch" or something like {"watch": true} which would be more convenient and also eliminate the extra node process needed by the workarounds.
My only trepidation is around using such a script as a dependency, though. Watch mode is a global thing -- it applies to all scripts in the graph. So what would it mean to launch a script not in watch mode, but depend on a script that is "intrinsically" in watch mode?
Maybe the simple answer to that is that we don't allow making a intrinsic-watch script a dependency, which would force you to factor out a separate e.g. :watch script for something that can be used in either way.

That sounds like a great solution.

@aomarks Maybe a bit off-topic: What if we would allow specifying a "watchCommand" next to the normal "command". The "watchCommand" would be expected to be long-running and would be executed instead of the normal command, when the "--watch" flag gets passed.
This way, it wouldn't be necessary to have two separate commands for watching. For normal builds it would be npm run build and for watching it would be npm run build --watch. It wouldn't directly solve the original problem, but it probably would make it less painful. But I haven't fully thought this throug, it probably would mean changing other stuff.

Adding my voice to this, I have some trouble with my peers using the wrong commands and this would help tremendously.

Just voicing support for the original proposal of having a package.json script call wireit --watch . This would ease transition for those developers coming from setups where starting to develop normal entails running npm run dev
The current workaround proposed doesn't work cleanly on Windows 11 + Windows Terminal + PowerShell Core, as it produces repetition and looks like something is stuck in a loop, so bad DevX.

I figured it was perhaps time to refactor
"start": "yarn run -TB concurrently \"yarn run build:tsc --watch\" \"rollup --config ./rollup.config.js --watch\" \"dhost site --bind-all\"",

to use the now-available service mode.  However, I'm not sure how to wire it up.
I tried using @augustjk's workaround:
  "scripts": {
    "start": "yarn run serve --watch",
    "serve": "yarn run -TB wireit",
    "build": "yarn run -TB wireit",
    "build:tsc": "yarn run -TB wireit",
    "build:bundle": "yarn run -TB wireit",
    "publish": "yarn run -TB wireit"
  },
  "wireit": {
    "serve": {
      "service": true,
      // i've tried cascade: false here too
      "command": "dhost site --bind-all",
      "dependencies": [
        "build"
      ]
    },
    "build": {
      "dependencies": [
        "build:tsc",
        "build:bundle"
      ]
    },

however, it seems like service: true is blocking watch from doing its job:
🏃 [build:tsc] Running command "tsc --build --pretty"
✅ [build:tsc] Executed successfully
🏃 [build:bundle] Running command "rollup --config ./rollup.config.js"

./dist/mount.js → ./site/bundles...
created ./site/bundles in 69ms
✅ [build:bundle] Executed successfully
✅ [build] No command to execute
🏃 [serve] Running command "dhost site --bind-all"
* Serving static files from …
* Local http://localhost:9000 (on your clipboard!)
* Network http://<IP_ADDRESS>:9000
------------------------------------------
^C💀 [serve] Killed
👀 [serve] Watching for file changes

Notice that 👀  doesn't show up until after I press ^C to stop wireit.  serve is just a dumb server, but I want the dependencies (build) to run again on file changes.
There are other issues that would need resolution (like making sure that livereload still works correctly), but I can't make any progress until I figure out how --watch and service: true are meant to work together.
Not sure if this is a bug, a misunderstanding, or an unimplemented feature.  Happy to raise into its own issue if that's a better venue.

So what would it mean to launch a script not in watch mode, but depend on a script that is "intrinsically" in watch mode?
Maybe the simple answer to that is that we don't allow making an intrinsic-watch script a dependency, which would force you to factor out a separate e.g. :watch script for something that can be used in either way.

As others in the thread have hinted, it's common to have a service that is not watched by Wireit that is dependent on packages that should be watched by Wireit (which might in turn depend on other services). Some packages in the graph may need to be watched/managed by other tools such Vite/Rollup (and not Wireit) so that they can handle incremental bundling, HMR etc.
A simple work around might be to just provide an empty files/output array in the Wireit config depending on your needs, so that it's not fighting with your bundler etc. over outputs and inputs.


Raytasker initial PR

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@mj0lken ping here 🙂

I'm closing this due to inactivity; feel free to open it again or comment in the thread when you're ready to continue working on it 🙂
You can also catch me in Slack if you want to discuss 😄


Laravel Elixir has been Replaced with Mix

In version 5.4 of Laravel, the Elixir build system was replaced with Laravel Mix.
You can see the documentation here for more information:
https://laravel.com/docs/5.4/mix
We should either:

Consider renaming this project to Mix
Create a separate repo for Mix

Resolved by release v1.0.0


Add support for GROUP BY summaries and fix broken LIMIT m, n clause

Also added test cases.  GROUP BY summaries support (CUBE, ROLLUP, WITH CUBE, WITH ROLLUP, WITH TOTALS) requires sqlalchemy 1.2.13+

No activity in a while, so I guess I'll just maintain my own fork


Latest Node Docker image breaks build

Bug Report
The latest node image breaks the build.
Latest:  docker.io/library/node:22-alpine3.20@sha256:96cc8323e25c8cc6ddcb8b965e135cfd57846e8003ec0d7bcec16c5fd5f6d39f
Pinning the image to the previous version still works:
FROM --platform=$BUILDPLATFORM node:22-alpine3.20@sha256:b64ced2e7cd0a4816699fe308ce6e8a08ccba463c757c00c14cd372e3d2c763e AS build
Log
#20 13.11 ReferenceError: require is not defined
#20 13.11     at file:///app/tailwind.config.js:39:11
#20 13.11     at ModuleJobSync.runSync (node:internal/modules/esm/module_job:395:35)
#20 13.11     at ModuleLoader.importSyncForRequire (node:internal/modules/esm/loader:329:47)
#20 13.11     at loadESMFromCJS (node:internal/modules/cjs/loader:1414:24)
#20 13.11     at Module._compile (node:internal/modules/cjs/loader:1547:5)
#20 13.11     at Object..js (node:internal/modules/cjs/loader:1677:16)
#20 13.11     at Module.load (node:internal/modules/cjs/loader:1318:32)
#20 13.11     at Function._load (node:internal/modules/cjs/loader:1128:12)
#20 13.11     at TracingChannel.traceSync (node:diagnostics_channel:322:14)
#20 13.11     at wrapModuleLoad (node:internal/modules/cjs/loader:219:24)

should this pinning be committed  to main until it is fixed? ...as without this the builds are broken.

node:21 will work :)

Fixed on dev.


Using Snapcraft instead of AppImage

Consider switching to Snapcraft from the AppImage.
The greatest advantages are easier to install and more reliable update options (like updating over the package manager instead of manually downloading a file)
I can write a GitHub Action for that.

Considering that OCAT will be upgraded less and less frequently, no other adjustments will be made at this time, thank you very much for your suggestion.


Routing error if the remaining path after matched path is empty

Moved from this PR: https://github.com/react-navigation/react-navigation/pull/3961
Not sure if it's still an issue @ericvicenti

I think we fixed this a while ago. Let me know if there are any clear repros


Update Django, django-haystack and djangorestframework versions

First of all, many thanks for maintaining this project.
I've allowed myself to add some support for newer Lib versions and Python versions.
Python

Drop support for deprecated Python versions ( 3.4 )

Test

Add Python 3.8
Add Django 3.0
Add Python pypy3.6-7.1.1
Remove Python 3.4
Remove Django 1.11
Remove Django 2.0
Remove Django 2.1
Remove Python pypy3.5-6.0

Travis
https://travis-ci.org/github/rhblind/drf-haystack/builds/697279837
djangorestframework

Support DRF v3.11

django-haystack

Support up to Django-Haystack 3 (Not released yet)

Django

Drop deprecated Django versions (1.11, 2.0, 2.1)
Add support for Django 3
Remove python_2_unicode_compatible decorator since there's no support for Python2
Change deprecated base_name to basename in Router

https://www.djangoproject.com/download/

Many thanks for your work.
Also, if you're interested in becoming a maintainer, that would be very welcome, as we're lagging a bit behind on care and love for this project :)
Let me know 👍

@rhblind You're welcome.
It is an interesting proposition. However, I'm a bit short on time these past few months ( and upcoming ones 😂 ).
I don't think I would have enough time to do some quality job as a maintainer.
Thanks for the offer though, I really appreciate it.
PS: Do you think it will be possible to create a new release on PyPi with those changes in the near future?

No problem :)
Yes, I'll have to make a new release soon, it's long overdue. I just want to confirm in the test suite, that the ES5 backend works, so I'm in the process of updating docker and tox configuration with ES5 as well.


Imagenet benchmarking

Added two main parts :

Handling of the training and test of both ImageNet100 and a subset of Imagenet100 for debugging purposes

Made an initial baseline for the results of training an initial columnformer architecture on imagenet100

hi @clane9, thanks for observations on the changes, its more organized this way ! I have done the requested modifications. Let me know if something else is needed


mod not working at all fabric 1.20.1?

unless the mod has any dependencies that i don't see, game won't launch even with a clean instance consisting of only SmoothGui and Fabric API

seems like you are right

Same here.

yep, seeing this issue as well


[Feature request]: Improved camera image quality

Describe the solution you'd like
I have 2 Eufy Cam 2C Pros running the latest version of the integration and the entity_picture attribute URL seems to retrieve the "Dectected by Local AI" image from the Eufy app if its available rather than the larger resolution still image above it in the app.
Is it possible to choose the larger better quality image rather than the "Dectected by Local AI" one as that is zoomed in pixelated?
Originally posted in: https://github.com/fuatakgun/eufy_security/issues/839 and https://community.home-assistant.io/t/eufy-security-integration/318353/1624?u=benjani85

Checking in to see if there is any chance this question is feasible? Is there a limitation somewhere along the line like Eufy's API?
I would really like to make use of the detection images but that will only be possible if the quality is good.


Incorrect mepc value after irq is taken

Hi all,
During a test, this segment of code is running on the core:

At PC=0x80000276 (a nop instruction), our testbench asserts a software interrupt, as shown from the waves below:

However, we see that mepc_q gets set to 0x80000274 after this interrupt is detected and handling begins, meaning that after the interrupt handler has ended, the core will jump back to this address, but as you can see from the code snippet, this is a misaligned address, so Ibex immediately takes an illegal instruction exception, and fails the test.  This address comes from the exception_pc, which is muxed to the value of pc_if_i, which for some reason is set to this misaligned address, and is less than the pc_id_i.

Looks like the prefetch buffer changes are causing this - I'll look into it.


Plugin Support ( css, scss, text etc)

Consolidates #32 #37 #74 #103 #91 #85.
An effort needs to me made to make existing plugins hmr compatible. And a general solution for plugins that have transitive imports also needs to be devised. For instance scss files also import their own files.

[ ] css
[ ] scss
[ ] text

same thing for less files, they can import their own files as well.

try sormy/bs-systemjs-hot-reloader + sormy/systemjs-hot-reloader (js, sass, less, styl etc)

Good to hear it,
I am interested on this, let me know any chage ;)
Thanks!


Cannot resolve IP for Mouse Without Borders

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Mouse Without Borders
Steps to reproduce
Restarted one of the devices and now cannot reeastablish connection now after months of use. The IPs cannot be resolved even after manual mapping, whether the IPs are static or dynamic, and with firewall rules added and ensuring that the devices are discoverable.
✔ Expected Behavior
Connection between the two devices
❌ Actual Behavior
Cannot resolve IP
Other Software
No response

To add, it weirdly seems almost like the devices can still kind of see eachother. If the wrong security key is entered then the error that comes up is different, but then with the right key it's as if the devices never were able to see eachother at all.

For anyone that happens to see it, my issue was very specific. I live in an apartment with shared WIFI and it seems after the restart, the device was put on a different hidden network (Likely connected to a different AP). I was not able to figure out how to change this, but I connected both via cable to a network switch and manually set up an alternative IP for both on that ethernet connection, then mapped those IPs for both devices in MWB and generated a new key, after which everything worked. For those that may wonder why I don't just connect them to ethernet with that switch, it's cause the port refuses to work in my apartment since they had an outage not too long ago lol.


cant make public access to a menu

hi , im using luci on owrt 19.07.3 , git-20.229.71287-57456a7
i want to grant access to a page using this method
https://openwrt.org/docs/guide-user/luci/statistics.chart.public
i made this a lot of time on owrt 18.06 with success
but now i have an unwanted behavior , the index page is replaced with my view page and i can't log in anymore
here the file i have placed in a fresh installed router, to reproduce the issue
https://gitlab.com/davidea/test-luci/-/tree/second
lastly, where i can find the documentation about the assign method i've used?

This is not supported anymore.


v1.0 development

Task list
Judgel Processor

[x] Implment terminatable TLE verdict
[x] Implement Compilation Error verdict
[x] Make testcase for debugging
[x] Implement Runtime error verdict
[x] Implement by file name testcase
[x] Implement fixed tabular length
[x] Light weight and optimization
[x] Add help page
[x] ?Add custom time limit
[x] Error handling
[x] Killable TLE process
[x] Add easy current directory mode

Source code auxiliary

[x] Uniform naming convention
[x] Comments
[x] Formatted code
[x] Uniform file and path

Testing

[x] All rounded edge case testing
[x] Test on other computers with the potential setting

Installation

[x] Standalone compilation
[x] Make .msi file for judgel
[x] Simplify .msi installation process

Remarks

Directories must not contain spaces, if have, must use "
Testcase .in .out   must not contain space
Sometimes RTE becomes TLE if the program takes too long to exit
Can use relative path

v1.0 publishes now!


Halloween 🎃 🎃 🎃

https://spacedock.info/mod/2875
https://github.com/zer0Kerbal/Halloween

The changes to JackOLantern are already present in #8806, I'm going to force-push to your branch to remove them.

A few things:

The mod isn't published on SpaceDock yet
The netkan and license file within the zip say CC-BY-NC-SA-4.0, SpaceDock says "CC BY-NC-SA 3.0 unported". I guess SD needs an update?
Is the name "Halloween! (HWLN)" correct? Especially the "HWLN" part, should that be "HLWN", maybe?

been pushing hard - to get it out before the holiday. HLWN is what it should be. 🎃
I should have this out in the next 24-48 hours.
Was trying to determine the correct license, and it seems that CC BY-NC-SA 4.0 is going to be the license. SD corrected.

more chainsaw over cuts. 🪚

I should have this out in the next 24-48 hours.

@zer0Kerbal, the holiday is only 11 days away, are you still planning to click Publish on SpaceDock?

at least the candles are standing up straight and attaching correctly finally.


fix: LEAP-1579: LEAP-1576: LEAP-1582: Improve comment icons usability

In this PR the way we display comment icons on the overlay should be improved.
What has changed:

overlayNode is now orchestrating the visibility of the icon
added a watcher for shapes based on classification, so in some cases we will not lose the position of the comment icon
icons will not be displayed for resolved comments
icons will not be displayed for regions related not to current item in multi-object case (is actual for images in MIG case)
icons will not be displayed for classifications hidden by conditions (see 'visiblewhen')
if coment is linked to perRegion result ant the result is not selected we still display the icon but near the region itself

PR fulfills these requirements

[x] Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
[ ] Tests for the changes have been added/updated (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
[x] Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
[x] Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)
(check all that apply)

[ ] Product design
[ ] Backend (Database)
[ ] Backend (API)
[x] Frontend

Does this PR introduce a breaking change?
(check only one)

[ ] Yes, and covered entirely by feature flag(s)
[ ] Yes, and covered partially by feature flag(s)
[x] No
[ ] Not sure (briefly explain the situation below)

What level of testing was included in the change?
(check all that apply)

[ ] e2e
[ ] integration
[ ] unit

Which logical domain(s) does this change affect?
CommentsOverlay

/git merge develop


end of Node.js 10 support

Node 10 is no longer maintained, and I'll be looking to start using features that it doesn't have, in this project. I think we'll wait a while to see if Glitch moves over to a later version of Node for its in-container software though.

I think this issue requires an update, Glitch now supports well beyond 10.x all the way to 16.6! This also means dependencies like commander can be updated!

glitch has long supported node higher than 10, but the observation in the issue description was that glitch uses specifically node 10 for some important things. that makes it an appealing target because we know it'll be available in the project containers

Node.js 12 is out of support too now.


[Fix #6263] Fix an error for Layout/EmptyLineAfterGuardClause

Fixes #6263.
This PR fixes an error Layout/EmptyLineAfterGuardClause when guard clause is after heredoc including string interpolation.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Run rake default or rake parallel. It executes all tests and RuboCop for itself, and generates the documentation.

PR and changelog say Layout/EmptyLinesAroundClassBody, but changes are to Layout/EmptyLineAfterGuardClause. 🙂

Oops 💦  I fixed the cop name. Thanks for your review.


Missing locale files with next-i18next

I'm running into an issue with next-i18next. Read all related issues, read the PR which should cover i18n issues, but still in a circle of fail.
{"errorType":"Error","errorMessage":"ENOENT: no such file or directory, scandir '/var/task/public/static/locales/en'","trace":["Error: ENOENT: no such file or directory, scandir '/var/task/public/static/locales/en'","    at Object.readdirSync (fs.js:955:3)","    at getAllNamespaces (/var/task/src/netlify/functions/next_admin/nextPage.js:89104:21)","    at createConfig (/var/task/src/netlify/functions/next_admin/nextPage.js:89109:29)","    at new NextI18Next (/var/task/src/netlify/functions/next_admin/nextPage.js:119486:48)","    at Object.k7Sn (/var/task/src/netlify/functions/next_admin/nextPage.js:89904:18)","    at __webpack_require__ (/var/task/src/netlify/functions/next_admin/nextPage.js:31:31)","    at Module.cha2 (/var/task/src/netlify/functions/next_admin/nextPage.js:69840:63)","    at __webpack_require__ (/var/task/src/netlify/functions/next_admin/nextPage.js:31:31)","    at Module.kt/p (/var/task/src/netlify/functions/next_admin/nextPage.js:91877:22)","    at __webpack_require__ (/var/task/src/netlify/functions/next_admin/nextPage.js:31:31)"]}
To Reproduce
The whole configuration done according to docs.
i18n.js (next-i18next)
const NextI18Next = require('next-i18next').default
const { localeSubpaths } = require('next/config').default().publicRuntimeConfig
const path = require('path')

module.exports = new NextI18Next({
  defaultLanguage: 'en',
  otherLanguages: ['fr'],
  localeSubpaths,
  localePath: path.resolve('./public/static/locales'),
})

next.config.js

const { nextI18NextRewrites } = require('next-i18next/rewrites')
module.exports = {
    target: 'serverless',
    rewrites: async () => nextI18NextRewrites(localeSubpaths),
    publicRuntimeConfig: {
      localeSubpaths,
    },
    i18n: {
      defaultLocale: 'en',
      locales: ['en', 'fr'],
    },
  }
}

Versions

Next: 10.0.6
next-on-netlify: 2.0.0

hey @2j2e! thanks for bringing this to us! my first thought:
why are you using next-i18next along with the framework's embedded i18n support? aka, you have:
 i18n: {
      defaultLocale: 'en',
      locales: ['en', 'fr'],
    },

in next 10+, this configuration alone will take care out of i18n out of the box for you, with no need for an additional package like next-i18next. i believe packages like that one existed before next 10 was released with native i18n support.

note: if you're using i18n in next 10.0.6, you need to be on next-on-netlify 2.8.7 per a breaking change in 10.0.6. see this release: https://github.com/netlify/next-on-netlify/releases/tag/v2.8.7

I tried with and without explicit next.config.js settings and it has zero effect. According to official Next.js docs the i18n support is only about proper routing, everything else should be done with external libraries.
The i18n routing support is currently meant to complement existing i18n library solutions like react-intl, react-i18next, lingui, rosetta, and others by streamlining the routes and locale parsing.
next-i18next built on top of react-i18next, so we should be good here.

if you're using i18n in next 10.0.6, you need to be on next-on-netlify 2.8.7 per a breaking change in 10.0.6.

According to my lock file, the plugin uses v2.8.7 under the hood.
"<EMAIL_ADDRESS>  version "2.0.0"
  resolved<EMAIL_ADDRESS>  integrity sha512-vUAnMExD4FpjtxjO65NYzpzPgoIPCiNxXW9GIC9n5tuW5UUbdGRerSH9kqp5j75J89Ll/cVzUlZJpnSRxy5v0Q==
  dependencies:
    chalk "^4.1.0"
    find-up "^4.1.0"
    jimp "^0.16.1"
    make-dir "^3.1.0"
    next-on-netlify "2.8.7"
    semver "^7.3.2"

Looking on the pipeline next.js > next-i18next > netlify > netlify/plugin-nextjs I can think on 2 source of the issue.

Next.js + next-i18next build is doing something wrong.
Netlify + netlify/plugin-nextjs is doing something wrong.

I made a quick test with Vercel deployment and everything works fine, this means #1 is not an option for this case.

i believe this is related to https://github.com/netlify/next-on-netlify/issues/124

Not sure about #124,
Here is the example repo which a clone of the official next-i18next example combining with Netlify configuration.

Wooh, I found that next v10 is not actually supported by next-i18next, what a twist.

@2j2e haaa oh no.. what does that mean exactly for you/for this issue?
i will say that i still believe this is at least in part related to #124 because it seems public/static/locales is not getting bundled with the netlify function for your pages/index.js, causing that error during "runtime"/from within the function environment. that, or somehow they are being bundled and just accessible at a different path. either way, it will depend on the work that will resolve #124, which is a high priority for us right now!
and again rewrites: async () => nextI18NextRewrites(localeSubpaths) - this won't be supported on netlify at the moment and so would probably cause its own issues (even if there was next 10 support for next-i18next).
all that said, is this specific issue something you want to keep open for when next 10 is supported by next-i18next? would you be comfortable tracking the other issues (#124, #24) that would be blockers for this type of integration?
let me know what you're thinking!

Thank you for a quick tracking and answers. I decided to switch to the next-translate. Not just decided, but already did and works perfect for now.
I don't know if you want to keep this issue open, but I'm OK to close it.

@2j2e of course!!! and oh that's great news yay! i'll close this one and if you run into any issues with next-translate you can always open another! 🖖


Component pattern

Hi,
I like alot of the principles here, but, why is the render method at the bottom of the class, in my experience i always look for the render method when I inspect a React class, so why don't put it under the constructor so it will be at the top of the file?
Component Organization

class definition

constructor

event handlers

'component' lifecycle events
getters
render

defaultProps
proptypes

Hi @skeie,
This is mostly preference. I come from a pretty "Crockfordian" style of writing JavaScript—manually hoisting variables and putting the meat of your function at the bottom. While that has no baring on the organization of a class definition, it's a major influencer.
While we compiled this before we'd found any other suitable guides, we've updated it as we've seen people Rally around particular patterns. "render at the bottom" seems like the common approach. AirBNB—who's JavaScript styleguide has 24k stars—also recommends render at the bottom.
All that to say "popular opinion" is the only reason we write render at the bottom :)

Thanks :-). Think I will go for render at the top though.


utf-8 error

16:47:14     | python: unloading script "slack_extension"
16:47:14     | python: loading script "/home/gromozeka/.weechat/python/autoload/wee_slack.py"
16:47:14     | python: registered script "slack_extension", version 0.98.7 (Extends weechat for typing notification/search/etc on slack.com)
16:47:19     | python: stdout/stderr: Traceback (most recent call last):
16:47:19     | python: stdout/stderr:   File "/home/gromozeka/.weechat/python/autoload/wee_slack.py", line 1753, in url_processor_cb
16:47:19     | python: stdout/stderr:     process_message(message)
16:47:19     | python: stdout/stderr:   File "/home/gromozeka/.weechat/python/autoload/wee_slack.py", line 1439, in process_message
16:47:19     | python: stdout/stderr:     channel.buffer_prnt('unknown', message_json['text'])
16:47:19     | python: stdout/stderr:   File "/home/gromozeka/.weechat/python/autoload/wee_slack.py", line 587, in buffer_prnt
16:47:19     | python: stdout/stderr:     message = message.decode('UTF-8', 'replace')
16:47:19     | python: stdout/stderr:   File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
16:47:19     | python: stdout/stderr:     return codecs.utf_8_decode(input, errors, True)
16:47:19     | python: stdout/stderr: UnicodeEncodeError: 'ascii' codec can't encode characters in position 120-129: ordinal not in range(128)
16:47:19 =!= | python: error in function "url_processor_cb"
16:47:19     | python: stdout/stderr: Traceback (most recent call last):
16:47:19     | python: stdout/stderr:   File "/home/gromozeka/.weechat/python/autoload/wee_slack.py", line 1753, in url_processor_cb
16:47:19     | python: stdout/stderr:     process_message(message)
16:47:19     | python: stdout/stderr:   File "/home/gromozeka/.weechat/python/autoload/wee_slack.py", line 1439, in process_message
16:47:19     | python: stdout/stderr:     channel.buffer_prnt('unknown', message_json['text'])
16:47:19     | python: stdout/stderr:   File "/home/gromozeka/.weechat/python/autoload/wee_slack.py", line 587, in buffer_prnt
16:47:19     | python: stdout/stderr:     message = message.decode('UTF-8', 'replace')
16:47:19     | python: stdout/stderr:   File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
16:47:19     | python: stdout/stderr:     return codecs.utf_8_decode(input, errors, True)
16:47:19     | python: stdout/stderr: UnicodeEncodeError: 'ascii' codec can't encode character u'\u2013' in position 166: ordinal not in range(128)
16:47:19 =!= | python: error in function "url_processor_cb"
16:47:19     | python: stdout/stderr: Traceback (most recent call last):
16:47:19     | python: stdout/stderr:   File "/home/gromozeka/.weechat/python/autoload/wee_slack.py", line 1753, in url_processor_cb
16:47:19     | python: stdout/stderr:     process_message(message)
16:47:19     | python: stdout/stderr:   File "/home/gromozeka/.weechat/python/autoload/wee_slack.py", line 1439, in process_message
16:47:19     | python: stdout/stderr:     channel.buffer_prnt('unknown', message_json['text'])
16:47:19     | python: stdout/stderr:   File "/home/gromozeka/.weechat/python/autoload/wee_slack.py", line 587, in buffer_prnt
16:47:19     | python: stdout/stderr:     message = message.decode('UTF-8', 'replace')
16:47:19     | python: stdout/stderr:   File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
16:47:19     | python: stdout/stderr:     return codecs.utf_8_decode(input, errors, True)
16:47:19     | python: stdout/stderr: UnicodeEncodeError: 'ascii' codec can't encode characters in position 112-117: ordinal not in range(128)
16:47:19 =!= | python: error in function "url_processor_cb"
16:47:20     | python: stdout/stderr: Traceback (most recent call last):
16:47:20     | python: stdout/stderr:   File "/home/gromozeka/.weechat/python/autoload/wee_slack.py", line 1753, in url_processor_cb
16:47:20     | python: stdout/stderr:     process_message(message)
16:47:20     | python: stdout/stderr:   File "/home/gromozeka/.weechat/python/autoload/wee_slack.py", line 1439, in process_message
16:47:20     | python: stdout/stderr:     channel.buffer_prnt('unknown', message_json['text'])
16:47:20     | python: stdout/stderr:   File "/home/gromozeka/.weechat/python/autoload/wee_slack.py", line 587, in buffer_prnt
16:47:20     | python: stdout/stderr:     message = message.decode('UTF-8', 'replace')
16:47:20     | python: stdout/stderr:   File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
16:47:20     | python: stdout/stderr:     return codecs.utf_8_decode(input, errors, True)
16:47:20     | python: stdout/stderr: UnicodeEncodeError: 'ascii' codec can't encode characters in position 54-59: ordinal not in range(128)
16:47:20 =!= | python: error in function "url_processor_cb"
I comment out line 587, and it earned

thanks for the stack trace. I'm going to figure out the right way to handle this unexpected state and write some better debug info.

one request:
try exiting weechat, deleting ~/.weechat/slack.cache and starting weechat. please let me know if the bug goes away when you do this!

Getting the same error, removing the slack.cache didn't help.

+1
Installed the script from master today, here's the log:
17:03 script: 299 scripts for WeeChat 1.3
17:03 Plugins loaded: alias, charset, exec, fifo, irc, logger, perl, python, relay, ruby, script, trigger, xfer
17:03 python: stdout/stderr: Traceback (most recent call last):
17:03 python: stdout/stderr:   File "/home/rw/.weechat-work/python/autoload/wee_slack.py", line 1752, in url_processor_cb
17:03 python: stdout/stderr:     process_message(message)
17:03 python: stdout/stderr:   File "/home/rw/.weechat-work/python/autoload/wee_slack.py", line 1439, in process_message
17:03 python: stdout/stderr:     channel.buffer_prnt('unknown', message_json['text'])
17:03 python: stdout/stderr:   File "/home/rw/.weechat-work/python/autoload/wee_slack.py", line 587, in buffer_prnt
17:03 python: stdout/stderr:     message = message.decode('UTF-8', 'replace')
17:03 python: stdout/stderr:   File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
17:03 python: stdout/stderr:     return codecs.utf_8_decode(input, errors, True)
17:03 python: stdout/stderr: UnicodeEncodeError: 'ascii' codec can't encode character u'\u2019' in position 137: ordinal not in range(128)
17:03 !!! python: error in function "url_processor_cb"

I experienced the same error on startup, ended up with https://github.com/rawdigits/wee-slack/pull/121. I still don't fully understand what happened.

To elaborate : this exception is raised while trying to print the debug trace. Not that helpfull.
Fix it by applying 5ee8926b8bb1dbd04ebc4cf810bafef3d99ccdcb (so that the Exception handling does not raise an exception before debugging). This will lead you to another UnicodeEncodeError raised by this line IIRC which should be fixed by #121

Calve's patch fixed this, and we haven't seen these recur in a long time. Closing this bug.


Parse error for example on llhd.io and code generated from Moore

Reproduction steps:

Install moore and llhd-sim from cargo: cargo install moore llhd-sim.
Versions reported: llhd-sim (0.3.1), moore (0.10.0)
Run llhd-sim on attached llhd example.
Run moore on out.sv to generate llhd code and run it through llhd-sim.

Error message:
Parse error at line: 1, column: 85
Unexpected `-`
Expected `(`

example.llhd.txt
out.sv.txt

Thanks for the bug report! This is caused by llhd-sim using an outdated version of LLHD; will be fixed as part of #8.

This repository is now deprecated in favor of the implementation within LLHD. Tracking continues there. This bug should have been fixed as part of the migration there.


[Doc][Seatunnel] version 3.0.2 has Seatunnel task but no related documentation

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
version 3.0.2 has the Seatunnel task but no related documentation, need to migrate ST doc to version 3.0.2
https://dolphinscheduler.apache.org/en-us/docs/3.0.2
Documentation Links
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I am interested!

@HudsonShi  I had assigned to you, please try to make our document wonderful


Syntax highlighter and file open dialog should recognise .pxi and .pxd as cython files

From<EMAIL_ADDRESS>on 2010-11-09T19:22:28Z
Attached patch fixes this.  However I haven't duplicated the corresponding icon files under spyderlib/images/filetypes.
Perhaps instead of duplicating files where the same type of file can have multiple extensions, it would be better to add an extra field to the tuple on line 77 of spyderlib/widgets/codeeditor/codeeditor.py.
Attachment: patch.txt
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=446

From pierre.raybaut on 2011-04-24T07:36:54Z
This issue was closed by revision 00519ac2e504 .

From pierre.raybaut on 2010-11-10T10:34:33Z
This issue was closed by revision 00519ac2e5 .
Status: Fixed


Change the min and max value of fields

and minor cleanup

Why are we changing these?

In the database the maximum length of username, email and password fields are 255. But they are 64 in the code. Furthermore the minimum length of email field is at least 6 instead of 2 (for example: a@a.ru).

Merged in a9679484ae280783dde96c983e3ec557b2319fa4


Allow to accept sync function for PlainOption/mapOrElseAsync

We close this once by https://github.com/option-t/option-t/issues/1683#issuecomment-1456004819.
We'll reopen this when we conclude about #1683.
If you have some opinions, please comment to #1683


wpg: 6.5.7 -> 6.5.9

Description of changes
Tested it locally on x86_64-linux, everything seems to work as expected.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Ohh, just noticed the commits here are messed up, sorry, will fix

Now this is ready for review :D

Only one nit: rename the PR to wpgtk: 6.5.7 -> 6.5.9. wpg is "only" the executable :)

Result of nixpkgs-review pr 257249 run on x86_64-linux 1

2 packages built:

wpgtk
wpgtk.dist

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1121

@ofborg build wpgtk wpgtk.passthru.tests


FirehoseStatsReporter never reports stream name in its error message when used in FirehoseAppender

The message always says

Failed to publish a log entry to kinesis using appender: null

This is happening because in FirehoseAppender the constructor for FirehoseStatsReporter is called before the appender is fully initialized with a valid stream name

Hi, I have this issue resolved , How do I collaborate?


30-seconds-example - PyProj Issue Perhaps

Greetings, this library is great, was able to run airports-parallel notebook. But ran into an error here in the 30-seconds-example notebook.
I've been running into errors and warnings w/ pyproj lately due to espg changes lately in other code.
When I run:
aoi.crs

Result: {'init': 'epsg:4326', 'no_defs': True}
PyProj Version I'm Running
import pyproj

pyproj.__version__

Result: '1.9.6'
When I run this cell:
# Define the aoi and input parameters of the workflow to run it.

input_parameters = workflow.construct_parameters(geometry=aoi,
                                                 geometry_operation="bbox",
                                                 start_date="2018-01-01",
                                                 end_date="2020-12-31",
                                                 limit=1)
input_parameters["sobloo-s2-l1c-aoiclipped:1"].update({"max_cloud_cover":60})
input_parameters

Get the Following Error Message:

AttributeError                            Traceback (most recent call last)
<ipython-input-12-98126c8ec4dd> in <module>
      5                                                  start_date="2018-01-01",
      6                                                  end_date="2020-12-31",
----> 7                                                  limit=1)
      8 input_parameters["sobloo-s2-l1c-aoiclipped:1"].update({"max_cloud_cover":60})
      9 input_parameters

~/opt/anaconda3/envs/dsi/lib/python3.7/site-packages/up42/workflow.py in construct_parameters(self, geometry, geometry_operation, handle_multiple_features, start_date, end_date, limit, scene_ids, order_ids)
    301                 datetime = f"{start_date}T00:00:00Z/{end_date}T00:00:00Z"
    302                 input_parameters[data_block_name]["time"] = datetime
--> 303             aoi_fc = any_vector_to_fc(vector=geometry,)
    304             aoi_feature = fc_to_query_geometry(
    305                 fc=aoi_fc,

~/opt/anaconda3/envs/dsi/lib/python3.7/site-packages/up42/utils.py in any_vector_to_fc(vector, as_dataframe)
    276             df = vector
    277             if df.crs != "epsg:4326":
--> 278                 df = df.to_crs(4326)
    279
    280     if as_dataframe:

~/opt/anaconda3/envs/dsi/lib/python3.7/site-packages/geopandas/geodataframe.py in to_crs(self, crs, epsg, inplace)
    532         else:
    533             df = self.copy()
--> 534         geom = df.geometry.to_crs(crs=crs, epsg=epsg)
    535         df.geometry = geom
    536         df.crs = geom.crs

~/opt/anaconda3/envs/dsi/lib/python3.7/site-packages/geopandas/geoseries.py in to_crs(self, crs, epsg)
    422         else:
    423             proj_in = pyproj.Proj(self.crs, preserve_units=True)
--> 424             proj_out = pyproj.Proj(crs, preserve_units=True)
    425             project = partial(pyproj.transform, proj_in, proj_out)
    426         result = self.apply(lambda geom: transform(project, geom))

~/opt/anaconda3/envs/dsi/lib/python3.7/site-packages/pyproj/__init__.py in __new__(self, projparams, preserve_units, **kwargs)
    344             projstring = projparams
    345         else: # projparams a dict
--> 346             projstring = _dict2string(projparams)
    347         # make sure units are meters if preserve_units is False.
    348         if not projstring.count('+units=') and not preserve_units:

~/opt/anaconda3/envs/dsi/lib/python3.7/site-packages/pyproj/__init__.py in _dict2string(projparams)
    684     # convert a dict to a proj4 string.
    685     pjargs = []
--> 686     for key,value in projparams.items():
    687         pjargs.append('+'+key+"="+str(value)+' ')
    688     return ''.join(pjargs)

AttributeError: 'int' object has no attribute 'items'

I'm happy to take a look at this and fix if you'd like, but thought I'd Submit an Issue as I don't think I can dig into it today.
Take care.

I think https://github.com/up42/up42-py/blob/master/up42/utils.py#L264 just needs df = df.to_crs(epsg=4326). Will test out fix when I have time.

@nygeog Hi Danny, thank you for your feedback and effort!
The newest version of geopandas (0.7.0) introduced a breaking change for the crs object, the old {'init': 'epsg:4326', 'no_defs': True} form is deprecated in favour of "EPSG:4326". To make it a bit clearer we now pinned the geopandas version, cleaned up the code to be more consistent with the crs usage and released a new version 0.8.3.
Please  update to the newest version of up42-py and geopandas via pip install up42-py --upgrade. Thanks again for your feedback!
PS: We also split up create_and_run_job to run_joband test_job recently, please have a look at the changelog.


Under "Download Docker for Mac" SHA256  checksum links to bad page(s)

File: docker-for-mac/install.md
There are links to the checksums for the downloads available in the "Download Docker for Mac" section shown here:

The links go to: https://download.docker.com/mac/edge/Docker.dmg.sha256sum
This is a 404 page.

Closing issue as it refers to old docs that have since been moved/deprecated/refreshed.


Usage is vague for options supporting multiple values

Snippet from README - CLI parameters
OPTIONS:
    -a, --accept <accept>                      Comma-separated list of accepted status codes for valid links
    -b, --base <base>                          Base URL or website root directory to check relative URLs e.g.
                                               https://example.com or `/path/to/public`
        --exclude <exclude>...                 Exclude URLs from checking (supports regex)
    -s, --scheme <scheme>...                   Only test links with the given schemes (e.g. http and https)

I only just realized the syntax is implied with the ... when raising this issue. It didn't stand out to me when looking at the README :sweat_smile:

The --scheme option implied multiple values could be supplied, and it did not click for me when I had to separate the input with -- after trying the option (NOTE: I've seen discussion for implicit behaviour when no inputs are provided, which would have prevented the helpful error).
When trying to use this, I originally tried --scheme 'file://' (didn't work), then after realizing to drop :// suffix, I tried --scheme 'http file', --scheme 'http,file' (--accept mentions a comma separated list), and --scheme 'http|file' (--exclude had an example after the listed options using regex | pattern).
I was not successful until --scheme 'http' --scheme 'file'. It did not occur to me that providing multiple values without wrapping them together in quotes was how it was probably intended (--scheme 'http' 'file' / --scheme http file).
Some brief examples may have been useful? It would also be helpful to clarify that these options are for links in inputs, originally I thought they also applied to inputs (as redundant as that may seem, I was trying to troubleshoot why my local inputs were attempting to be requested remotely, thinking --offline would apply as well).

We should definitely add usage examples for that yeah!
There will be a proper lychee book with examples at some point, but in the meantime we could add it to the README.md (and maybe the troubleshooting guide?).
We could even start a folder with example snippets for different use-cases that we can later put on into the book.
Open for suggestions and pull requests here.

At long last we got proper documentation for repeating options in the lychee docs here. 🥳 There is a button to edit the source in case we need to make any adjustments, but it's a start.
(P.S.: There is also a dark mode for the docs now. 🤫)
Closing this issue because there is a "fix" now, but feel free to post a comment below to let me know what you think!


"Dead" tokens in PF2e system

I'm not sure how Enhanced Terrain Layer interacts with the PF2E system and what the module is looking for to consider a token "dead" for purposes of the "Dead cause difficult terrain" rule.
There's no "Dead" condition in the PF2e system; if "Tokens cause difficult terrain" is checked, but "Dead cause difficult terrain" is not, even when tokens have 0 hp and they're Marked Defeated in the Encounter Tracker, they still count as difficult terrain.

This is something best handled by the PF2e drag ruler integration rather than by Enhanced Terrain layer. And will be next release, assuming no bugs make me eat those words.
Once I put out the next release, when the Dead Caused Difficult terrain setting is checked, creatures that have 0 hp, the unconscious, paralyzed, immobilized, petrified or dead conditions will be treated as difficult terrain by all creatures.
Furthermore the Tokens Cause difficult terrain setting will now only apply to creatures that do not have the same disposition as you. Friendly creatures ignore difficult terrain caused by other friendly creatures, likewise for hostile creatures.

Closing the ticket as I think it should be covered.
But @velara I wanted to add that the next version of Enhanced Terrain will allow you to include a function in the options that can be used to "figure" out if a token is dead.  So system specific Rulers can provide their own way of determining that status to the cost function.
Easy as cost([], { isDead: (token) => { //add code here to determine if the token is dead }}).


Removes references to Odyssey and minor cleanups in src/vis/vis.js

I started to cleanup src/vis/vis.js a bit, which has a lot of stuff in it. I realised that they are some references to the Odyssey project, so I spent a little bit of time :fire: them (code, tests, vendored library). I did some more minor changes (there's much more to clean up, but didn't have time for more).
CR: @viddo
cc: @xavijam @javierarce @javisantana @acanimal
(closes #796)

whoa, 7k LOCs?  :fire_engine: :ambulance:
:shipit:

:tada: :+1:

:es:


chore: add Helm chart

Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[x] Optimization
[ ] Documentation Update

Description
Added Helm chart to simplify OLS installation
Related Tickets & Documents
https://issues.redhat.com/browse/OLS-50
Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

Tested in local. looks good to me

Tested in local and I see this error in client. Looks like clusterrole and its binding in ols namespace are missing.
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [130 bytes data]
* We are completely uploaded and fine
{ [5 bytes data]
< HTTP/2 401
< content-type: text/plain; charset=utf-8
< x-content-type-options: nosniff
< content-length: 13
< date: Thu, 14 Dec 2023 08:40:24 GMT
<
{ [5 bytes data]
Unauthorized
* Connection #0 to host ols-proxy.ols.svc left intact

Nice catch, I forgot to add role/rolebinding to ols
Thanks!

@vishnuchalla regarding OLS itself
For the service to work correctly, we need access to BAM (KEY and URL)
We can keep sensitive data in secret and then mount it to OLS.
Or (at the first stage) add information to the README, how to do this manually
WDYT?

@vishnuchalla regarding OLS itself For the service to work correctly, we need access to BAM (KEY and URL)
We can keep sensitive data in secret and then mount it to OLS. Or (at the first stage) add information to the README, how to do this manually WDYT?

I think we need to add instructions in README.md to do it manually for now. I will need @bparees to share his thoughts in terms of on-premise offering.

We can keep sensitive data in secret and then mount it to OLS.
Or (at the first stage) add information to the README, how to do this manually

right now OLS consumes the key from an env var. So the ideal flow would be:

helm chart takes the key as a parameter
helm chart creates a secret from the parameter
ols deployment injects the env var from the secret into the ols pod

long term i am anticipating a flow more like:

there exists a OLS config CRD that includes object references to LLM cred secrets
there exists an OLS config controller that watches the CRD and creates/updates the OLS deployment to mount the referenced secrets
the OLS config controller also creates an ols.config.yaml which includes the filesystem paths of the mounted LLM creds.  The ols.config.yaml gets injected into the OLS deployment either as an env var, or as a mounted configmap.
OLS app uses the ols.config.yaml to configure itself on startup

does that make sense?

I added the secret manifest.
In terms of long-term support - also understandable

needs a rebase, otherwise lgtm


News: add reload functionality

Description
The news page is missing refresh functionality to load new articles. a good implementation would be swiping down to reload the page, or having a reload button in the upper right corner.
https://github.com/threefoldtech/threefold_connect/assets/101194226/99515617-28ad-4967-92ad-233d357efefb
Environment

Android Version: 13
Threefold Connect version: 3.7.3 - 173

Now, swiping down reloads more articles.

Verified on Android 14,
Threefold-Connect: 4.0.0 -184
APK:12-12-2024
Currently reload functionality has been successfully added and swiping down reloads more articles.

https://github.com/user-attachments/assets/e20adcc9-bbd9-47c9-bc8f-e65c38beec89
Related Link:

https://app.testlodge.com/a/26076/projects/40893/suites/206114?expand_section=407472#case_4048995


Ignore DD_INSTRUMENTATION_TELEMETRY_ENABLED env

What does this PR do?
Add DD_INSTRUMENTATION_TELEMETRY_ENABLED to the list of known environment variables.
Motivation
Not have warnings about it.
Describe how to test/QA your changes
Done by CI.
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Future of probot/autolabeler?

Noticing there are PRs from greenkeeper that haven't been touched in quite some time, and the last commit to master was April 4th, 2018.
Don't mean to sound entitled to OSS, just trying to be pragmatic:
Is probot/autolabeler all but deprecated?

I would be happy to maintain autolabeler but don't have access to this repository to do the maintenance.

Tagging a random couple of probot org members (apologies if not the best way to contact):
@hiimbex @JasonEtco any thoughts or feelings on this?

👋 This repo is definitely not one that we are actively maintaining. I can't speak for the other Probot folks, but I don't think that there's anything major left to do here - the thing works, we can update dependencies but even that requires a time investment.
I just went ahead and merged #28 to at least update the docs.
Long-term - if y'all are interested in taking over this repo, we can talk about that, otherwise it'll just have to sit here 😅
@mithro - would giving you write access to the repo be enough? I'll chat about it with the other Probot folks to make sure it's 👌, but I imagine that'd be no problem (and thank you for the offer ❤)

@jasonetco - yes. If you have me access, I could keep it up to date and review pull requests

@mithro would you be interested in maintaining probot/stale as well? There are quite a few open PRs there that could use some attention as well :)
(Full disclosure: I'm particularly interested in #162, so if @JasonEtco or someone else is willing to look at it, that'd also be appreciated.)

@waldyrious, Stale is a different case - there are some open PRs, but we still watch that repo and the deployment of it closely. It's considered more of a GitHub-managed project so we're still maintaining it.

I'm not a huge fan of the probot/stale bot, so would probably not want to maintain it.

Not trying to be pushing but were any decisions on this made?

I am using a 'policy' on my repos where anyone that successfully submits a PR and gets it merged gets invited as a collaborator. May I suggest you could use something like that here?
This sounds like giving away control over the repo, but as owner you can always revoke the permissions again and it's all versioned so their is little real danger of code getting lost.
In addition, you could use a 'two pair of eyes' rule where no one can create a PR and merge it on their own. But with many collaborators it should be much easier to find someone willing to review and merge your PR.

Thanks for your patience here y'all.
We've understood that this repo isn't getting the attention it needs, and the small group of Probot maintainers don't have the bandwidth to change that. For that reason, I'd like to transfer the repo to @mithro, who is already maintaining the deployment of the app.
@mithro - are you interested in that path? No pressure, we can figure something else out if you don't want to take ownership.

@JasonEtco - More then happy to take over ownership. This bot makes me happy every time I see the labels added :-)

Awesome, thank you @mithro, I'm really glad to hear that it'll get some love under your care 😊 I just tried transferring the repo, but:

@JasonEtco I renamed my forked repo, give it another go...

Thanks @mithro, but I believe that you'll need to do the transfer, as I can't transfer a repo to another user's account 😅

@JasonEtco - I have done the transfer now.

Awesome, thanks so much @mithro. I can't close this issue anymore (the irony lol), but I think we're all set. Thanks everyone for the discussion ❤


add kaggle buttons to W0DX

Hey guys, check out this!

I managed to add Kaggle buttons to use them along with the Colab ones. Just added for the W0D0, but let me know if there useful, I can add them for all weeks as soon as possible. They're seem to work perfectly and I think will simplify the use of Kaggle described here.

Awesome! Would this automatically update the tutorial though? If we made an update on the git version, would it open to that updated version?

I tried it @ebatty, and it seems to work kind of the same as Colab. It'll keep working even if you update the *.ipynb file, because Kaggle links are connected directly to the source links (notebooks are actually json files). So, if you keep the same name, it should keep working, even if updated.
Kaggle links work like this:
https://kaggle.com/kernels/welcome?src=RAW_SOURCE_EXAMPLE_LINK.ipynb
Which is actually raw source for this notebook and with some markdown magic you can generate this:

Which is actually:
[![Kaggle](https://kaggle.com/static/images/open-in-kaggle.svg)](https://kaggle.com/kernels/welcome?src=https://raw.githubusercontent.com/NeuromatchAcademy/course-content/master/tutorials/W0D0_NeuroVideoSeries/W0D0_Tutorial1.ipynb)
Hope that helps to understand, I'll add the coming weeks to merge all of them in one PR if approved.

Hmm, I'm not sure why the CI is failing. I'll try to look into it


I just open an issue to say thank you

I had to do a lot of research and I couldn't find what I wanted, but I came across your project and the fact that you can add comments to fields in a data class is great, I didn't find that anywhere else ! This is my project that use your code https://github.com/AmibeSkyfy16/BypassAnvilRestriction/tree/master/src/main/kotlin/ch/skyfy/bypassanvilrestriction/config
https://github.com/AmibeSkyfy16/TomlConfigLib

I'm so glad that you have a good time with it 😸. I see you are using interface to extend funtionality, I hope that polymorphism limitation isn't so destructive because nowadays I've spent my time into another project (which is minecraft related) and won't finish in a short time 🤔.

Guess what

👍


[yak_widgets] codecov ignores test for Initializer

fixed in https://github.com/iapicca/yak_packages/pull/124


remove .nvmrc; use NODE_VERSION env for netlify

This PR removes .nvmrc and uses an environment variable to set the Node.js version when deploying via Netlify.
My reasoning is that .nvmrc is consumed by more than just Netlify.  My shell, for instance, will automatically switch to a version specified in .nvmrc when I navigate to my working copy.  This may also have other unintended consequences.
So--if this works--I think it's best to not let the Node.js v12 requirement when deploying "leak" out of this context.

It seems to work.


Import Error

from flask_modals.modal import (from flask import (Blueprint, render_template, get_flashed_messages,
ImportError: cannot import name 'app_ctx_stack' from 'flask' (...Python\Python311\Lib\site-packages\flask_init.py)

Got the same error:
Flask==3.0.1
Flask-Modals==0.2.4

I tried with Flask-Modals 0.5.1, but same result
The only workaround that I was able to find was to downgrade the Flask version below 3.0.0, but that is not gonna work for me. That project seems to be dead, but in case someone decides to try implement Flask-Modals and gets the same error.

Same problem here
Flask                        3.0.3
Flask-Modals                 0.5.1