Core end2end tests cronet update

Update Core end2end tests and fixtures with the flag indicating whether :authority header override is supported.

@ctiller  Hi Craig, could you please help us review this PR when you got time? This is following our previous discussion about rejecting calls with :authority header when using Cronet. Thank you!
Changes:

Fixtures passing flag FEATURE_MASK_SUPPORTS_AUTHORITY_HEADER to unit tests with parameter config.
Added helper function validate_host_override_string
Unit test cases pass either "foo.test.google.fr" or NULL to grpc_channel_create_call depending on whether :authority header is supported.

Ping~

Revised as requested. Request another look.

test this please


Migrate Python samplegen to MVVM

Codecov Report

Merging #1053 into master will decrease coverage by -0.38%.
The diff coverage is 84.48%.

@@             Coverage Diff             @@
##             master   #1053      +/-   ##
===========================================
- Coverage     85.17%   84.8%   -0.38%
- Complexity     3484    3496      +12
===========================================
  Files           366     370       +4
  Lines         13856   13938      +82
  Branches       1576    1585       +9
===========================================
+ Hits          11802   11820      +18
- Misses         1597    1653      +56
- Partials        457     465       +8

Impacted Files
Coverage Δ
Complexity Δ

.../com/google/api/codegen/metacode/InitCodeNode.java
79.89% <ø> (-2.39%)
74 <ø> (-9)

.../google/api/codegen/nodejs/NodeJSGapicContext.java
89.45% <ø> (ø)
85 <ø> (ø)
:x:

...n/transformer/php/PhpImportSectionTransformer.java
93.33% <100%> (+1.02%)
5 <2> (+2)
:white_check_mark:

...gen/transformer/go/GoImportSectionTransformer.java
95.45% <100%> (-4.55%)
8 <1> (ø)

.../google/api/codegen/py/PythonSnippetSetRunner.java
100% <100%> (ø)
2 <ø> (ø)
:x:

.../transformer/StandardImportSectionTransformer.java
100% <100%> (ø)
5 <1> (+1)
:white_check_mark:

...e/api/codegen/transformer/TestCaseTransformer.java
86.66% <100%> (ø)
26 <1> (ø)
:x:

...former/py/PythonSampleMethodToViewTransformer.java
98.14% <100%> (-0.04%)
20 <ø> (-1)

...transformer/ruby/RubyImportSectionTransformer.java
97.43% <100%> (+0.13%)
12 <1> (+1)
:white_check_mark:

...api/codegen/transformer/py/PythonSurfaceNamer.java
100% <100%> (ø)
6 <6> (?)

... and 40 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update caf63b7...885726e. Read the comment docs.

I actually do not feel all that comfortable reviewing this; I have not done anything nearly this complex in toolkit. @landrito or @geigerj, would you take a look?

@garrettjonesgoogle or @shinfan should also take a look.

@garrettjonesgoogle @shinfan Do you have time to review these changes to MVVM to support Python samplegen?

The ImportSectionTransformer issue has been resolve. @shinfan PTAL

Huzzah.


Merge master into gcs-nio

Reviewer: @jean-philippe-martin
CC: @mziccard

gcloud-java-contrib/gcloud-java-nio-examples/README.md:25 should read -0.2.4-SNAPSHOT instead of -0.2.1.-SNAPSHOT. Same for line 30. The release script updates this one, but of course this will only work once we're merged into master.

gcloud-java-examples/README.md we'll want to update the instructions for ComputeExample to use appassembler. Not sure whether this needs to be in this PR or if it's better to leave it for a subsequent one, since this PR's already huge.

The CL's huge and I can't really check everything, but it looks to me like there's nothing else I'd change, everything else is good.

Looks good to me.


Visual Studio attempts to build with 'all' target instead of 'ALL_BUILD'

When attempting to build a project with the Visual Studio 14 2015 CMake generator, I get the following error message:
[vscode] Executing command: cmake --build c:/Users/vortr/git/vor/build --target all --config Release -- /m /property:GenerateFullPaths=true
Microsoft (R) Build Engine version 14.0.25420.1
Copyright (C) Microsoft Corporation. All rights reserved.

MSBUILD : error MSB1009: Project file does not exist.
Switch: all.vcxproj
[vscode] cmake exited with return code 1

This seems to be the troublesome line:
https://github.com/vector-of-bool/vscode-cmake-tools/blob/develop/src/common.ts#L682
this.allTargetName correctly evaluates to ALL_BUILD, but this.defaultBuildTarget evaluates to all, which overrides it (I guess -- I don't know much TypeScript).
I reproduced this problem on both 0.8.7 and the current develop branch.

Looks like a recent refactor broke this behavior for a few contexts. I'll see about fixing it.

Should be fixed now

Awesome, thank you!

I have this very same issue with version 0.11.1

Possible regression. You shouldn't need to work around this, but does it continue to use all after you reload the window?

Oops I just tried manually selecting the "ALL_BUILD" target in the status bar and now the "all" target is gone, F7 builds the ALL_BUILD target and everything works. I made sure by cleaning and rebuilding again, so I can confirm 0.11.1 is fine, sorry 😅 (btw thanks a lot for this package)


Micrometer Observation component

A list of questions and TODOs related to this component that we must resolve before merging
Discuss:

The Tracer abstraction from Camel has a notion of only high cardinality tags, we are missing low cardinality tags for metrics (that means that metrics will not have any tags at this point)
Are the changes in the Tracer in the tracing component acceptable?

TODO:

[ ] Spring Boot Starter is missing
[ ] Polish the documentation
[ ] Currently the behaviour is almost identical to OpenTelemetry one, that requires the presence of custom handlers - I'm considering to remove them so that the additional code will not be necessary. That will mean that with Micrometer Observation with OTel Tracer the spans will be a little bit different than with the OpenTelemetry component

Recrated from https://github.com/apache/camel/pull/9377

A list of questions and TODOs related to this component that we must resolve before merging
Discuss:

The Tracer abstraction from Camel has a notion of only high cardinality tags, we are missing low cardinality tags for metrics (that means that metrics will not have any tags at this point)
Are the changes in the Tracer in the tracing component acceptable?

TODO:

[ ]  Spring Boot Starter is missing

This is not a problem, we could do that later

[ ]  Polish the documentation

This could be done with a subsequent PR

[ ]  Currently the behaviour is almost identical to OpenTelemetry one, that requires the presence of custom handlers - I'm considering to remove them so that the additional code will not be necessary. That will mean that with Micrometer Observation with OTel Tracer the spans will be a little bit different than with the OpenTelemetry component

On this, I'm not really sure about it: if we goes this way it's important to document and notes the difference, otherwise users might think the result will be the same with Micrometer and Opentelemetry and it won't be the case

Recrated from #9377

Please rebase on 3.x, so we are good. Waiting for @orpiske and @davsclaus reviews.

Thanks for the big work, there is a little merge conflict, I wonder if you could resolve that and push update to this PR so it can be merged cleanly.
Also we would need this to be ported to Camel v4 (main) but that is JDK17 and JakartaEE; which I assume micrometer also works with, but just wanted to mention the difference to Camel v3.

I fixed the conflicts and did some additional changes

modified the tracer api to introduce a low cardinality tag (those would be used for metrics and traces)
modified the current micrometer observation behaviour to remove the custom handlers

Below you have a screenshot of a trace view for a very simple route
@Component
class MyRoute extends RouteBuilder {

	@Override
	public void configure() throws Exception {
		from("direct://foo")
				.log("hello")
				.to("http://httpbin.org/headers");
	}

}

With the Micrometer Observation you also get the following metric.
MeterId{name='camel.operation', tags=[tag(HTTP_METHOD=GET),tag(HTTP_STATUS=200),tag(component=camel-http),tag(error=none)]}

I also changed the behaviour so that it is close to the OpenTelemetry one but not the same - I will document the differences plus I've left the code in the tests that can be used to have the same behaviour.
So the question to you is - do you find such information valuable (traces and metrics) in its current form if you were to troubleshoot any issues within a Camel based system? I can try a more complex scenario and we can discuss what metrics / tags can be more useful in your opinion. We can also play around with the names if you think e.g. name of the component should be there in a span name.
As for Jakarta - Micrometer is working fine with JDK17.
cc @bclozel

So I've been playing around with this and I'm really surprised with how it's actually working currently with OpenTelemetry. Let's assume that I have the following routes
from("direct://foo")
				.log("hello")
				.to("direct://bar")
				.to("http://example.org");
		from("direct://bar")
				.log("hello")
				.to("direct://micrometer")
				.to("http://example.org");
		from("direct://micrometer")
				.setHeader(MicrometerConstants.HEADER_METRIC_NAME, constant("new.name"))
				.setHeader(MicrometerConstants.HEADER_METRIC_TAGS, constant(Tags.of("dynamic-key", "dynamic-value")))
				.to("micrometer:counter:name.not.used?tags=key=value")
				.to("direct://baz");
		from("direct://baz")
				.log("hello")
				.to("bean:com.example.cameldemo.MyBean")
				.to("exec:wc?args=--words /usr/share/dict/words")
				.process(exchange -> {
					// Use the Camel Exec String type converter to convert the ExecResult to String
					// In this case, the stdout is considered as output
					String wordCountOutput = exchange.getIn().getBody(String.class);
					// do something with the word count
					System.out.println(wordCountOutput);
				})
				.to("file:///tmp/camel-outputdir?flatten=true")
				.to("http://example.org");

I would assume that for the whole flow (e.g. from producerTemplate.send("file:///tmp/camel-outputdir?flatten=true", defaultExchange);) to the end I would have a single trace. From what I see this is not the case cause all direct:// components are completely ignored in terms of continuing a trace (look at TracingEventNotifier:shouldExclude method).

Is this really the intent of how this should actually work? I would assume that there should be 1 trace for the whole processing because otherwise this doesn't make a lot of sense (at least to me).

As far as I remember it was not really easy to have a full trace, in the end we were able to have one trace for each route.
This means from..to, when you pass to another from..to, like for example
	from("direct://bar")
			.log("hello")
			.to("direct://micrometer")

This will be another trace. I don't remember the reason, but I think instrumenting it to take into account all the routes for a single trace was too hard to implement or too invasive. I might remember wrongly nevertheless

This will be another trace. I don't remember the reason, but I think instrumenting it to take into account all the routes for a single trace was too hard to implement or too invasive. I might remember wrongly nevertheless

This will actually not be a trace because direct seems to be an internal component that gets ignored.

This will be another trace. I don't remember the reason, but I think instrumenting it to take into account all the routes for a single trace was too hard to implement or too invasive. I might remember wrongly nevertheless

This will actually not be a trace because direct seems to be an internal component that gets ignored.

This looks wrong then. Can you open an issue?

Thanks

IMO the graph should like this (please correct me if I'm wrong)
from("direct://foo")
				.log("hello")
				.to("direct://bar")
				.to("http://example.org");
		from("direct://bar")
				.log("hello")
				.to("direct://micrometer")
				.to("http://example.org");
		from("direct://micrometer")
				.setHeader(MicrometerConstants.HEADER_METRIC_NAME, constant("new.name"))
				.setHeader(MicrometerConstants.HEADER_METRIC_TAGS, constant(Tags.of("dynamic-key", "dynamic-value")))
				.to("micrometer:counter:name.not.used?tags=key=value")
				.to("direct://baz");
		from("direct://baz")
				.log("hello")
				.to("bean:com.example.cameldemo.MyBean")
				.to("exec:wc?args=--words /usr/share/dict/words")
				.process(exchange -> {
					// Use the Camel Exec String type converter to convert the ExecResult to String
					// In this case, the stdout is considered as output
					String wordCountOutput = exchange.getIn().getBody(String.class);
					// do something with the word count
					System.out.println(wordCountOutput);
				})
				.to("file:///tmp/camel-outputdir?flatten=true")
				.to("http://example.org");

We have a red graph beacuse I'm explicitly throwing an exception in a controller in my application.
I've achieved this graph by removing the instanceof check here (https://github.com/apache/camel/blob/camel-3.x/components/camel-tracing/src/main/java/org/apache/camel/tracing/Tracer.java#L296) but obviously I might be missing sth. I'm not committing that change, but if you confirm my assumptions I can file an issue and point to a potential solution.

Actually everything is fine after doing the before mentioned change. I didn't have the file or exec only because I was throwing an exception in the bean component and the exchange processing was stopped :facepalm:
So how do we proceed? I mean should I commit the change with the exclusion or not?

The latest observation screenshot looks really great, with all the span details.
@marcingrzejszczak are you referring to the shouldExclude method you linked above, where you can only make this work if you remove that entirely or what?

Ah okay, so AbstractInternalSpanDecorator is intended for camel components that are used for internal communication like direct / seda etc. And in your example above you call routes from routes via direct:bar/direct:baz. Do you not see spans for those or how does it filter those?

So without my change afair you'll see spans but not for direct components and you'll not see a single trace for the whole flow of a message but you'll see multiple different traces. That's because spans are no longer maintaining parent child relationship.

Okay I think we can accept that code change. Are all the unit test passing with this PR in both camel-tracing and camel-micrometer ?

Okay I think we can accept that code change. Are all the unit test passing with this PR in both camel-tracing and camel-micrometer ?

If I do the change to the shouldExclude a lot of tests in camel-opentelemetry are failing because number of spans is invalid (previously they were ignored, now they are not).

Maybe we could mark them as disabled and get back to them once we have the fix in place.

It's up to you - I don't have a problem with adding back the code from the shouldExclude method so that we merge this with all the tests passing and then filing a new issue that most likely shouldExclude method is broken and then we could fix micrometer, opentracing and opentelemetry module tests. WDYT?

If you time to do that, it would be nice, we are probably in the same situation on main, 3.x and 3.20.x, so we should fix the shouldExclude method on LTS branch too (3.20.x). To me it's +1. Thanks a lot for your time.

OK so I'm changing this PR as ready for review

Hopefully I fixed checkstyle issues and also I've created the new issue here https://issues.apache.org/jira/browse/CAMEL-19124

Can you work on the SB starter for the 3.x branch, so we have all together. Then afterwards we can possible cherry pick to main branch. If not then we appreciate if you would then work on PRs for main so we have this in v4 as well.

merging this for 3.x so its included in Camel 3.21 onwards.

Also I wonder if you would contribute an example such as for camel-spring-boot-examples. And you are welcome to include screenshots in the example as it helps users to quickly see this awesome feature

Screenshots is also welcome in docs. However they may be harder to do, and the img may need to go in docs root folder where we have images for other pages such as EIPs

Sure I can work on the starter. Of course the screenshots should be done after we fix the issue with shouldExclude method because the trace view will be broken

Spring Boot configuration https://github.com/apache/camel-spring-boot/pull/784
Spring Boot example https://github.com/apache/camel-spring-boot-examples/pull/98


fix: v2 migration 문서에 존재하는 오타를 수정합니다

Overview

PR Checklist
fix #236

[x] I read and included theses actions below

I have read the Contributing Guide
I have written documents and tests, if needed.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.83%. Comparing base (ba8be13) to head (ef9061d).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #237   +/-   ##
=======================================
  Coverage   99.83%   99.83%
=======================================
  Files          31       31
  Lines         600      600
  Branches      145      145
=======================================
  Hits          599      599
  Misses          1        1


Nether /rtp tps to overworld

As the title says, when you /rtp in the nether dimension you get teleported back to the overworld.

We will need to write custom handling for RTP entirely, for now this is not priority but we will keep it in mind.


Add gradle wrapper

@nishtahir thanks for the PR. Gradle 4.3.1 is the latest stable release. I am thinking we should just wait for 4.4 since they already have 4.4 RC3 out.
Let me know if that works out for you and I'll add the gradle wrapper for 4.4 when it comes out.

I also realized I didn't have the "issues" tab enabled. I enabled it and added an issue #38 to track it.

Thanks for jumping on this. Although I don't really see the value in waiting for it, you could just as easily merge this, and update to 4.4 when it comes out.


[Bug] API and datasource has same name

Steps to reproduce:

Add an API
Navigate to API datasource page
Add the credentials
Edit the name
Save the datasource
Now click on Add API
Add credentials
Edit the name and add same name as datasource
Now open the API datasource page
and observe

Observation:
It is observed that the API datasource and API can be Save at first but on trying to open the API datasource page  displays an error
Expectation:
It is expected to not save and display an error at first place

when widget have same name

Datasource names need not be unique from actions/widgets as they're not "in scope" for evaluations.

@ofpiyush I'm not sure about that, we do not seem to allow re-use of names currently either.

API or Widget of the same name will cause an issue with Eval, datasource causes no such issues and hence need not be unique.
Moreover, we'd need to know names of all actions and widgets across all apps of an org to disallow name conflicts on a datasource.

we do not seem to allow re-use of names currently either.

We went a little overboard on name conflict fixes with this PR https://github.com/appsmithorg/appsmith/pull/1781

Closing the issue as per above comment


Add Missing IDT entry #CP (vector 21)

This exception vector is supported on both AMD and Intel processors.
#313 is a good example of how this documentation should look.
This feature is documented in:

Section 8.2.20 of the AMD64 Architecture Programmer’s Manual Volume 2: System Programming
Section 6.15 - Interrupt 21 of the Intel Software Developer’s Manual Volume 3: System Programming Guide

Pull request created.


Upgrade to SQLAlchemy 2.x

Hi all,
Pandas is now depending on SQLAlchemy 2.x
When using pandas and jupyterlab at the same time, which is a very common situation, it may case some conflicts.
https://github.com/jupyter-server/jupyter-scheduler/blob/1b50f81f966c9e0146f91b1606fd78519857527e/pyproject.toml#L36

The sqlalchemy 2.x dependency was introduced in pandas 2.2.0, which was released on 2024-01-19.

@mattholy thank you for opening this issue. We plan to update to SQLAlchemy 2.x at some point but this is not a priority / we are not working on it now.

Hi @andrii-i, thanks for your work on this project, we use it extensively and it's really great!
Is there any chance you are able to upgrade to SQLAlchemy 2.x? We are finding this is a major blocker recently.
Many thanks!

Hi @adampinky85. Glad you are finding this project useful.
We are still planning to update to SQLAlchemy 2.x at some point but this is not a priority / we are not working on it now. At the same time, could you please share more about why Jupyter Scheduler not using SQLAlchemy 2.x is a major blocker for you recently?

thanks @andrii-i, yes manage environments running jupyterlabs and the kernel is built with a large number dependencies for research purposes including jupyter-scheduler.
On the EC2 instance we also have a number of project that are cloned and available for users to access from their notebooks (e.g., analysis libraries or business logic). There are now a number of libraries that require SQLAlchemy 2.x. which are not compatible to run from our notebooks.
jupyter-scheduler is exactly the right tool for our use case, we don't need airflow / apscheduler etc. as it requires more effort for users. They want to be able to run their notebooks easily with a few clicks.

@mattholy, @adampinky85, thank you for bringing up this issue and providing context. I just released v2.7.0 that among other things updates SQLAlchemy to 2.x.

[build-system]
requires = ["hatchling>=1.3.1", "jupyterlab~=4.0"]
build-backend = "hatchling.build"
[project]
name = "jupyter_scheduler"
version = "2.5.0"
description = "A JupyterLab extension for running notebook jobs"
readme = "README.md"
license = { file = "LICENSE" }
requires-python = ">=3.7"
authors = [
{ name = "Project Jupyter" },
]
keywords = ["Jupyter", "JupyterLab", "JupyterLab3"]
classifiers = [
"Framework :: Jupyter",
"Framework :: Jupyter :: JupyterLab",
"Framework :: Jupyter :: JupyterLab :: 3",
"Framework :: Jupyter :: JupyterLab :: Extensions",
"Framework :: Jupyter :: JupyterLab :: Extensions :: Prebuilt",
"License :: OSI Approved :: BSD License",
"Programming Language :: Python",
"Programming Language :: Python :: 3",
"Programming Language :: Python :: 3.7",
"Programming Language :: Python :: 3.8",
"Programming Language :: Python :: 3.9",
"Programming Language :: Python :: 3.10",
"Programming Language :: Python :: 3.11",
]
dependencies = [
"jupyter_server>=1.6,<3",
"traitlets~=5.0",
"nbconvert~=7.0",
"pydantic>=1.10,<3",
"SQLAlchemy>=2.0,<3",
"croniter~=1.4",
"pytz==2023.3",
"fsspec==2023.6.0",
"psutil~=5.9"
]
[project.optional-dependencies]
test = [
"pytest",
"pytest-cov",
"jupyter_server[test]>=1.6,<3"
]
dev = [
"click"
]
docs = [
"sphinx",
"myst_parser",
"pydata_sphinx_theme"
]
[project.urls]
Homepage = "https://github.com/jupyter-server/jupyter-scheduler"
[tool.check-wheel-contents]
ignore = ["W002"]
[tool.hatch.build]
artifacts = ["jupyter_scheduler/labextension"]
[tool.hatch.build.targets.wheel.shared-data]
"jupyter_scheduler/labextension" =
@.***/scheduler"
"install.json" =
"share/jupyter/labextensions/jupyter_scheduler/install.json"
"jupyter-config/server-config" = "etc/jupyter/jupyter_server_config.d"
"jupyter-config/nb-config" = "etc/jupyter/jupyter_notebook_config.d"
[tool.hatch.build.targets.sdist]
exclude = [".github"]
[tool.hatch.build.hooks.jupyter-builder]
dependencies = ["hatch-jupyter-builder>=0.5"]
build-function = "hatch_jupyter_builder.npm_builder"
ensured-targets = [
"jupyter_scheduler/labextension/static/style.js",
"jupyter_scheduler//labextension/package.json",
]
skip-if-exists = ["jupyter_scheduler/labextension/static/style.js"]
[tool.hatch.build.hooks.jupyter-builder.build-kwargs]
build_cmd
On Wed, May 8, 2024, 11:42 PM adampinky85 @.***> wrote:

Hi @andrii-i https://github.com/andrii-i, thanks for your work on this
project, we use it extensively and it's really great!
Is there any chance you are able to upgrade to SQLAlchemy 2.x? We are
finding this is a major blocker recently.
Many thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/jupyter-server/jupyter-scheduler/issues/478#issuecomment-2101875995,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZFSY64G6UXUWVPVIWAJD4TZBLWA5AVCNFSM6AAAAABCUD23GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBRHA3TKOJZGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

some of the specific changes made in the SQLAlchemy version update from 1.0
to 2.×:

True division and floor division: The Core expression language now
supports both "true division" (i.e. the / Python operator) and "floor
division" (i.e. the // Python operator) including backend-specific
behaviors to normalize different databases in this regard.
Improvements to declarative mixins, @declared_attr and related
features: The declarative system in conjunction with declared_attr has
been overhauled to support new capabilities. A function decorated with
declared_attr is now called only after any mixin-based column copies are
generated, allowing it to call upon mixin-established columns and receive a
reference to the correct Column object.
Association proxies: The AssociationProxy class now supports reuse
among subclasses, allowing a particular hybrid to be repurposed across
subclasses or other classes.
Type annotations: SQLAlchemy now includes type annotations for all
public APIs, making it easier to use with static type checkers.
Performance improvements: SQLAlchemy 2.× includes several performance
improvements, including faster query execution and reduced memory usage.
Deprecated features: Several features have been deprecated in
SQLAlchemy 2.×, including the text() function for constructing SQL
expressions, the type_ attribute of Column objects, and the
bindparam() function
for constructing parameterized queries.

Here is an example of how you might use some of these new features in your
code:
python Edit Run Full Screen Copy code
from sqlalchemy import Column, Integer, String, ForeignKey from
sqlalchemy.orm import relationship from sqlalchemy.ext.declarative import
declarative_base from sqlalchemy.ext.associationproxy import
association_proxy
Base = declarative_base()
class A(Base): tablename = "a" id = Column(Integer, primary_key=True)
type = Column(String)
mapper_args = {"polymorphic_on": type, "polymorphic_identity": "a"}
class ASub1(A): mapper_args = {"polymorphic_identity": "asub1"}
class ASub2(A): mapper_args = {"polymorphic_identity": "asub2"}
class B(Base): tablename = "b"
id = Column(Integer, primary_key=True) a_id = Column(Integer, ForeignKey("
a.id"))
a = relationship("A", primaryjoin="B.a_id == A.id", backref="b")
b_value = association_proxy("a", "type")
class C(Base): tablename = "c" id = Column(Integer, primary_key=True)
b_id = Column(Integer, ForeignKey("b.id"))
b = relationship("B", backref="c")
In this example, we've used the new type annotations for the Column and
relationship objects, as well as the new association_proxy class to create
a proxy for the type attribute of the A class. We've also used the new
polymorphic_identity attribute to define subclasses of the A class.
On Wed, May 29, 2024, 1:13 PM Cygel White @.***> wrote:

[build-system]
requires = ["hatchling>=1.3.1", "jupyterlab~=4.0"]
build-backend = "hatchling.build"
[project]
name = "jupyter_scheduler"
version = "2.5.0"
description = "A JupyterLab extension for running notebook jobs"
readme = "README.md"
license = { file = "LICENSE" }
requires-python = ">=3.7"
authors = [
{ name = "Project Jupyter" },
]
keywords = ["Jupyter", "JupyterLab", "JupyterLab3"]
classifiers = [
"Framework :: Jupyter",
"Framework :: Jupyter :: JupyterLab",
"Framework :: Jupyter :: JupyterLab :: 3",
"Framework :: Jupyter :: JupyterLab :: Extensions",
"Framework :: Jupyter :: JupyterLab :: Extensions :: Prebuilt",
"License :: OSI Approved :: BSD License",
"Programming Language :: Python",
"Programming Language :: Python :: 3",
"Programming Language :: Python :: 3.7",
"Programming Language :: Python :: 3.8",
"Programming Language :: Python :: 3.9",
"Programming Language :: Python :: 3.10",
"Programming Language :: Python :: 3.11",
]
dependencies = [
"jupyter_server>=1.6,<3",
"traitlets~=5.0",
"nbconvert~=7.0",
"pydantic>=1.10,<3",
"SQLAlchemy>=2.0,<3",
"croniter~=1.4",
"pytz==2023.3",
"fsspec==2023.6.0",
"psutil~=5.9"
]
[project.optional-dependencies]
test = [
"pytest",
"pytest-cov",
"jupyter_server[test]>=1.6,<3"
]
dev = [
"click"
]
docs = [
"sphinx",
"myst_parser",
"pydata_sphinx_theme"
]
[project.urls]
Homepage = "https://github.com/jupyter-server/jupyter-scheduler"
[tool.check-wheel-contents]
ignore = ["W002"]
[tool.hatch.build]
artifacts = ["jupyter_scheduler/labextension"]
[tool.hatch.build.targets.wheel.shared-data]
"jupyter_scheduler/labextension" =
@.***/scheduler"
"install.json" =
"share/jupyter/labextensions/jupyter_scheduler/install.json"
"jupyter-config/server-config" = "etc/jupyter/jupyter_server_config.d"
"jupyter-config/nb-config" = "etc/jupyter/jupyter_notebook_config.d"
[tool.hatch.build.targets.sdist]
exclude = [".github"]
[tool.hatch.build.hooks.jupyter-builder]
dependencies = ["hatch-jupyter-builder>=0.5"]
build-function = "hatch_jupyter_builder.npm_builder"
ensured-targets = [
"jupyter_scheduler/labextension/static/style.js",
"jupyter_scheduler//labextension/package.json",
]
skip-if-exists = ["jupyter_scheduler/labextension/static/style.js"]
[tool.hatch.build.hooks.jupyter-builder.build-kwargs]
build_cmd
On Wed, May 8, 2024, 11:42 PM adampinky85 @.***>
wrote:

Hi @andrii-i https://github.com/andrii-i, thanks for your work on this
project, we use it extensively and it's really great!
Is there any chance you are able to upgrade to SQLAlchemy 2.x? We are
finding this is a major blocker recently.
Many thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/jupyter-server/jupyter-scheduler/issues/478#issuecomment-2101875995,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZFSY64G6UXUWVPVIWAJD4TZBLWA5AVCNFSM6AAAAABCUD23GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBRHA3TKOJZGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@andrii-i thank you, we really appreciate the effort! I've just rolled the upgrade and everything is working great :)

Hi @FacePrintPay. I removed your comment that cited content of pyproject.py as it looked like spam. Please feel free to repost with more context.


Improve tests

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues
-

It's should prevent such errors.

👍


Question for angular/http

I'm submitting a ...
[ ] bug report
[ ] feature request
[x] question about the decisions made in the repository

How can I use http in this system?
`import { Injectable } from '@angular/core';
import { Http } from 'angular/http';
@Injectable()
export class NgRestService {
constructor(private http:Http) {
}`
I always stuck at
Module not found: Error: Can't resolve 'angular/http'

Should import { Http } from '@angular/http';


feat: Add CI

It is working on all architectures on my fork

Lovely. The Windows build is not working BTW because it doesn't have bash installed by default (it runs powershell): https://github.com/exercism/vlang/actions/runs/3446525018/jobs/5751533877
I'd either remove Windows, or add a PowerShell or batch script file specific to Windows.
Let me know which you prefer.

Ah yep. Weird that it fails quietly like that. I'll just pull windows off, as long as it runs in a bash/zsh environment it should be okay

The Windows build is not working BTW because it doesn't have bash installed by default (it runs powershell).

Bash is installed in the Windows GitHub Actions environment. It's just that PowerShell is the default.
Better approach: if the script works on Windows, we should be able to run it on all 3 platforms by specifying bash explicitly.

Ah nice good to know, thank you!

Great!


Fix data for United Kingdom

May be useful: https://github.com/carlaiau/flatten-the-curve/

https://github.com/CSSEGISandData/COVID-19/issues/911#issuecomment-602224614

https://github.com/jakobzhao/virus

https://github.com/stevenliuyi/covid19

https://github.com/pomber/covid19


ADK Installation Info Missing/Incorrect

Depending on what components of the ADK are selected when installed, it is possible ReAgent.dll and the associated files will not be included (on my ADK install, for example, there was no 'Windows Setup' folder under the ADK root, nor in the WinPE root.
Please expand the Workaround to state which components of the ADK must be installed to get the ReAgent.dll (there isn't a Windows Setup component in the linked 1903 ADK).

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

ID: b73c22f0-cb0d-e34b-29d8-06829b86784f
Version Independent ID: 083115ed-f1be-e962-5b0e-5079dec37353
Content: MBR2GPT - Windows Deployment
Content Source: windows/deployment/mbr-to-gpt.md
Product: w10
Technology: windows
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

It appears that the Windows Setup\amd64\Sources is added when you install USMT.  I'll add this detail.

@greg-lindsay Assigning this to an independent contributor. Thank you for the hint.

Closing via #6315. Thank you.


Convert string to MIT

I would be great to have a function to convert a string to an MIT of the correct frequency.
For instance:
frequencymap = Dict{Char,Any}(
    'Q' => Quarterly,
    'M' => Monthly,
    'Y' => Yearly,
)
convert_string_to_mit(t::AbstractString) = length(t) > 5 ? MIT{frequencymap[t[5]]}(parse(Int, t[1:4]), parse(Int, t[6:end])) : MIT{Yearly}(parse(Int, t[1:4]))
convert_string_to_mit("2022")
convert_string_to_mit("2022M11")
convert_string_to_mit("2022Q3")

We could also use Julia's syntax: convert(MIT{Monthly},"2022M1")

I've been using, for example, eval(Meta.parse("2022M1")), and thought it's simple enough that it didn't need to be packaged in a new function. I felt the overhead of maintaining another function (doc string, unit tests) wasn't worth it. But we can add it, if you see value in doing so. Let me know.

I don't feel strongly about this, but it might be more natural to think about convert(MIT{Monthly},"2022M1") compared to eval(Meta.parse("2022M1")). The performance is also a bit better when avoiding eval(). Below, myfunc uses eval().

How about we add a method to parse, e.g. Base.parse(::Type{<:MIT}, ::AbstractString). This way it's not a new function. I feel that if we're producing a value from a string that's parsing rather than a conversion. What do you think?

Great idea!


opscode-push-jobs-client has no candidate

Current problem we have with chef-ingredient and the rename of our product push-jobs to push-client.
============================================================================
Error executing action `install` on resource 'chef_ingredient[push-client]'
============================================================================

Chef::Exceptions::Package
-------------------------
apt_package[push-client] (/var/chef/cache/cookbooks/chef-ingredient/libraries/debian_handler.rb line 66) had an error: Chef::Exceptions::Package: opscode-push-jobs-client has no candidate in the apt-cache

Fixed with https://github.com/chef-cookbooks/chef-ingredient/pull/66 just need to consume it by running:
~/delivery-cluster $ berks update chef-ingredient
~/delivery-cluster $ rake maintenance:clean_cache
~/delivery-cluster $ rake setup:prerequisites

Bumping chef-ingredient to version 0.15.0 will fix this.


Updated Dockerimage to use correct version of Swift

Specified a digest in the Dockerfile in order to use
DEVELOPMENT-SNAPSHOT-2016-05-03-a instead of
DEVELOPMENT-SNAPSHOT-2016-05-09-a. Using the latest snapshot of Swift raises an error when building the project.

Thanks! Hopefully the new snapshot will be out soon. We can't support 05-09 because of a bug in the compiler when using Whole Module Optimization.


Add 'Plan Editor' widget to the demo application

Added 'Plan Editor' widget to the demo application.

Would you add a couple screenshots?

xref https://github.com/bluesky/bluesky-widgets/pull/128


[feature] Concat constants

Describe your idea:
Sometimes I see code such as
String value = "1" + "2";

Is that possible to implement a flag (or do it by default) to merge such constants? So after decompilation it would be
String value = "12";

@bagipro sure this can be implemented.
But, did you know the reason why this happens? I mean, java compiler always concat constant strings, so this will not occur in normal java building pipeline. Did you see such cases in any open source projects, so I can trace the cause of the issue.

@skylot
Probably because it's concatenated from different final fields, so the compiler replaces field references with their values, but doesn't concatenate. I will find such examples

@skylot
APK: https://drive.google.com/file/d/1scyr_jQjtDN5ICSfExkbTRzTew_0n0Nw/view?usp=sharing
Class com.dsi.ant.channel.EventBufferSettings
    public java.lang.String toString() {
        return "Event Buffer Settings:" + " -Buffer Time: " + this.mBufferTimeMilliseconds + "ms";
    }

And with int, class com.dsi.ant.channel.EventBufferSettings
                android.util.Log.i(str, "Decoding version " + readInt2 + " AntContinuousScanController parcel with version " + 1 + " parser.");

Done.
@bagipro thanks for samples.

@skylot
Thanks!


Extension not working

I followed all the steps and downloaded the last version.
The extension on my chrome browser is gray and after clicking on it it shows ''can't read or change site's data''.
Any suggestions to help.

I followed all the steps and downloaded the last version. The extension on my chrome browser is gray and after clicking on it it shows ''can't read or change site's data''. Any suggestions to help.

Youshould enter to an exercice, but for me, even when the extension work, it don't add time on it!


Does POSIX::2008 v0.24 fix a security hole?

The changes in POSIX::2008 say:

Fixed potential env buffer overflow in _execve50c()

Is that a security fix?
Diffs are at https://metacpan.org/release/CGPAN/POSIX-2008-0.24/diff/CGPAN/POSIX-2008-0.23 but it's unclear.

For what it's worth, v0.04 fixed an overflow reported in https://rt.cpan.org/Public/Bug/Display.html?id=96644

the bug thread says "major security leak"; and any bugger overflow is a
stability issue, which would be a potential Denial of Service handle, so it
would seem so.
// Bill
// happily long since no longer a Computer Security researcher
On Fri, Jun 14, 2024, 11:14 Robert Rothenberg @.***>
wrote:

For what it's worth, v0.04 fixed an overflow reported in
https://rt.cpan.org/Public/Bug/Display.html?id=96644
—
Reply to this email directly, view it on GitHub
https://github.com/briandfoy/cpan-security-advisory/issues/154#issuecomment-2168250512,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABVF6HNNLYQW4NHWOM7OG3ZHMCG7AVCNFSM6AAAAABJKRAM2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRYGI2TANJRGI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Since there's a fixed version, I don't have a problem flagging this as an advisory.

CPAN::Audit 20240615.001 has been released with this info.
Thanks,

Are these not two separate issues?

v0.24: Fixed potential env buffer overflow in _execve50c().

From latest release, unable to find any commit/patch or other references.

v0.04: Fixed _readlink50c (#96644).

https://rt.cpan.org/Public/Bug/Display.html?id=96644

The issue added as CPANSA-POSIX-2008-001 in https://github.com/briandfoy/cpan-security-advisory/commit/fb57b45712aacb426b43ee78fbe9905ec696fbab appears to have the description of the one fixed in v0.04 from 2015

Diffs are at https://metacpan.org/release/CGPAN/POSIX-2008-0.24/diff/CGPAN/POSIX-2008-0.23 but it's unclear.

Maybe not vulnerability relevant, but interesting to see these labels with expletives being added in 0.24:
From https://metacpan.org/release/CGPAN/POSIX-2008-0.24/diff/CGPAN/POSIX-2008-0.23:
       }
     }
-    else if (errno != ERANGE) {
+    else if (errno != ERANGE)
       /* gnulib says, on some systems ERANGE means that bufsize is too small */
+      goto FuckTheSkullOfGoogle;
+
+    if (UNLIKELY(bufsize+1 == 0)) {
+    MicrosoftMustDie:
+      errno = ENAMETOOLONG;
+    FuckTheSkullOfGoogle:
       Safefree(buf);
       return NULL;
     }

Oh, yeah, I mixed those up. A fix is on the way.


X86 dev backend: NumMulSaturated

Subtask of https://github.com/roc-lang/roc/issues/3513

currently implemented for everything except u128/i128


feat: Implement CAST from struct to string

Which issue does this PR close?

Closes https://github.com/apache/datafusion-comet/issues/814
Rationale for this change

As we add support for complex types, we will need to support CASTing them to string, so that users can run df.show() for example.
What changes are included in this PR?

Implement CAST from struct to string
How are these changes tested?

Codecov Report
Attention: Patch coverage is 66.66667% with 5 lines in your changes missing coverage. Please review.

Project coverage is 54.82%. Comparing base (845b654) to head (7cf7ab7).
Report is 12 commits behind head on main.

Files with missing lines
Patch %
Lines

...scala/org/apache/comet/expressions/CometCast.scala
66.66%
2 Missing and 3 partials :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##               main    #1066       +/-   ##
=============================================
+ Coverage     34.46%   54.82%   +20.35%
+ Complexity      888      858       -30
=============================================
  Files           113      110        -3
  Lines         43580    10760    -32820
  Branches       9658     2089     -7569
=============================================
- Hits          15021     5899     -9122
+ Misses        25507     3807    -21700
+ Partials       3052     1054     -1998

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Bug : Quick Links in Footer Section Not Working on Home Page

The quick links in the footer section of the website are currently not functioning. On clicking the link, it redirects us to 404 error page.
This issue affects the following links on Home Page:

Menu
Services
Contact Us
Cart

Error : 404 Error - footer link
When users click on these links, they do not redirect to the appropriate sections or pages. This is impacting the user experience as it prevents easy navigation to important parts of the site.
I'm GSSOC'24 contributor. Please assign this issue to me so I can resolve it as soon as possible.
@khushi-joshi-05

@GarimaSingh0109  @sunny0625
Can I start working on this issue?
As it needs to be resolved as soon as possible so that user can get the best experience while using the website.
Also it makes the negative impact when not redirected to the appropriate page.

This issue is already solved.
Try to contribute to different issues.


Python: introduce NIX_PYTHONPREFIX in order to set site.PREFIXES (20.03 backport)

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

best send this to staging-20.03

best send this to staging-20.03

Ok! Done.


Permission System

We are thinking about chained permission system inspired by iptables. This is just an idea.
Basically permissions will go through each of the rules in the chain and stop at the first matching rule. Better explained with the follow example:

Each of the servers will start with a basic chain.

Basic chain

server nsfw disable
enable all

When a command is ran, it will hit first rule. If it is a nsfw command it will be unable to run it due to that rule, and it will exit the chain. If the command is not nsfw, it will advance to the next rule and since it allows any command to be ran, it will trigger that rule and exit the chain.
Dj role

DJ role music enable
server music disable
enable all

If it is a a music command, and the person running the command is in a DJ role, first rule in the chain will trigger. If he is not in the DJ role, second rule will trigger, disallowing him the use of music commands. If it is any other command, it will allow it with 3rd default rule.

First

This is basicaly done.


Fix #11 - TypeError, PEP and pritification

Documented some functions (I don't get the others)
Let linter yell. Says update_text() is redefined
Autoformater reformat
Fix Trello issue 11.

@allEyezOnCode said ok for me


Regions as colored bars?

Hi everyone, is it possible to draw regions as colored bars? I mean like the progress wave, we color the wave (some chosen color) for selected area of the waveform. something like the below image. thanks

The barGap, barWidth and barRadius can get you a similar effect, and for the colors you might be able to use the region divs as CSS masks over the canvas wave, and apply some color filtering using that mask. Would be an easy way without writing your own renderer.

That is what I want to achieve about regions... can you give me an example about adding mask to canvas wave? and what would happen to regular regions? should I override some functions or anything? thanks

I did this by simply applying backdrop-filter: hue-rotate(120deg); to a region. The waveform is red, and now the area of the waveform under the region is green. However this doesn't work in Firefox (not even the latest).
You're on your own 😃 It seems like filter doesn't affect elements behind the target element, and I don't know if masking helps with that. Maybe you can mask parts of the waveform canvas and apply CSS to those segments only, I don't know. Here's a helpful article: https://css-tricks.com/almanac/properties/c/clip-path/
Other than that, I can't give you any other advice. Worst case scenario you will have to write a custom renderer for Wavesurfer. GL.

Thanks for your response, I will first try mask and clip, if I couldn't succeed I will then try changing the way wave bars are drawn, maybe using svg instead of canvas so that I can manipulate it easily. Thanks again.

@nevahid were you able to figure this out?


WSL2 doesn't start (/HCS_E_CONNECTION_TIMEOUT) after installing Docker desktop

Windows Version
Microsoft Windows [Version 10.0.22621.2283]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
Default Distribution: Ubuntu Default Version: 2
Distro Version
No response
Other Software
Docker Desktop 4.23.0
Repro Steps
N/A
Expected Behavior
Should be able to access wsl2
Actual Behavior
The operation timed out because a response was not received from the virtual machine or container.
Error code: Wsl/Service/CreateInstance/HCS_E_CONNECTION_TIMEOUT
Diagnostic Logs
WslLogs-2023-09-26_17-32-22.zip

Thank you for reporting this @rahulghangas. Unfortunately it looks like the issue is that your distribution disk is corrupted:
79	False	Microsoft.Windows.Lxss.Manager	GuestLog	0	09-26-2023 05:02:50.278	"	"	"text: 	""[  515.260595] JBD2: Invalid checksum recovering data block 21927 in log ""
vmId: 	{04a7f618-e691-413e-9765-90e8b1e12902}"				5008	17024	5		00000000-0000-0000-0000-000000000000
80	False	Microsoft.Windows.Lxss.Manager	GuestLog	0	09-26-2023 05:02:50.370	"	"	"text: 	""[  515.351993] JBD2: recovery failed ""
vmId: 	{04a7f618-e691-413e-9765-90e8b1e12902}"				5008	17024	5		00000000-0000-0000-0000-000000000000
81	False	Microsoft.Windows.Lxss.Manager	GuestLog	0	09-26-2023 05:02:50.370	"	"	"text: 	""[  515.352336] EXT4-fs (sdc): error loading journal ""
vmId: 	{04a7f618-e691-413e-9765-90e8b1e12902}"				5008	17024	5		00000000-0000-0000-0000-000000000000
82	False	Microsoft.Windows.Lxss.Manager	GuestLog	0	09-26-2023 05:02:50.373	"	"	"text: 	""[  515.355146] WSL (1) ERROR: UtilMount:1632: mount(/dev/sdc, /distro, ext4, 0x0, discard,errors=remount-ro,data=ordered ""
vmId: 	{04a7f618-e691-413e-9765-90e8b1e12902}"				5008	17024	5		00000000-0000-0000-0000-000000000000

It looks like the file that's corrupted is C:\\Users\\rahul\\AppData\\Local\\Packages\\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc\\LocalState
You can try these instructions  to recover your disk, or if you don't need to recover data you can just reinstall a new distribution and delete the old one via wsl --unregister.


Can you get this to swap IDs for HashIDs?

It would be really nice to swap the integer IDs for HashIDs instead. Is that possible in this package?

Hi @Jamesking56 ,
That's actually possible!
$links->action([OrdersController::class, 'show'])
    ->parameters(['currentPeriod' => $this->period->getHashId()]);

But at the moment it is not possible when you want to overwrite the id of the current model given to the resource. Let's say that the example above sits in an OrderResource which has an Order as model. Then it is possible to overwrite the currentPeriod id with an hash id. But the order id cannot be overwritten by a hash id due to the first rule of the parameter resolver(https://github.com/spatie/laravel-resource-links/blob/3c326ff56a689b02087a64c486c17e804bbc0f7e/src/ParameterResolver.php#L51). Though that's something we can work out in the future to make it work.


Convert the docstrings of examples in examples/* to use Markdown formatting

(e.g. for links and images), because some of these examples are now being rendered in the docs.
Added by @fchollet in requests for contributions.

See #11758

Tu add an example to the docs, just modify the file keras/docs/mkdocs.yml.

Hi! I'd like to start working on this if possible. Are there any specific guidelines on how visibility should be improved? Or should it be figured out from the two existing examples in mkdocs.yml?

It's just making sure that the page is rendered correctly in the docs. No need to be fancy.
Also, it is advised to do one pull request per example file. This is faster to review.

Pull requests should include a screenshot to facilitate the review process.

Can i start working on this issue?

Why this issue is still open? I guess every file is converted for Markdown.

Some PRs are note merged yet. So we can't really close this issue.

Hi @gabrieldemarmiesse,
building the documentation using master branch, it states that the following pages exist in the docs directory, but are not included in the "nav" configuration:
  - examples/class_activation_maps.md
  - examples/mnist_cnn.md
  - examples/mnist_dataset_api.md
  - examples/mnist_denoising_autoencoder.md
  - examples/mnist_hierarchical_rnn.md
  - examples/mnist_irnn.md
  - examples/mnist_mlp.md
  - examples/mnist_net2net.md
  - examples/mnist_siamese.md
  - examples/mnist_sklearn_wrapper.md
  - examples/mnist_swwae.md
  - examples/mnist_tfrecord.md
  - examples/mnist_transfer_cnn.md
  - examples/neural_doodle.md
  - examples/neural_style_transfer.md
  - examples/pretrained_word_embeddings.md
  - examples/reuters_mlp.md
  - examples/reuters_mlp_relu_vs_selu.md
  - examples/tensorboard_embeddings_mnist.md
  - examples/variational_autoencoder.md
  - examples/variational_autoencoder_deconv.md

I've worked on those and sent its PR(#12717 - #12763), one per example as you advised.
I hope my PRs get accepted so we can finally close this issue :)

Is any more help needed on this or not?

Hi @qwertpi, I've covered all examples in examples/* directory, once the PRs get merge we can close this issue.

Hi @marcemq , @qwertpi , @gabrieldemarmiesse , Is this still an open issue?
I am new to open source and looking to contribute to keras

I am new to open source and would like to contribute to this code

hello, I am new to open source and wants to learn and contribute, is this open?


EFRS-718 Fixed translations, and no result message under user list

I have read the CLA Document and I hereby sign the CLA


nixos/postgres Add syslog option

Motivation for this change
Having the option to use postgres to log all your queries should
be quite valuable to many users.
Doing this at application level is usually less reliable and slower.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Does logging work as desired if you add this new configuration to extraConfig instead of the changes you made here?

Yes:

Thanks for answering. Two things:

I don't think you need to change log_destination, but I'm not sure.
Isn't the name enableSystemLogging misleading? All logging is too the system log (journald) already. I would also think that people might want to only turn a few of these options on instead of all sometimes. Maybe an attribute set representing the configuration file would make the situation better here.

I don't think you need to change log_destination, but I'm not sure.

Default behavior appears to be logging to some file in /var/lib/postgresql/PG_VERSION/log. Enabling syslog will put everything into journalctl on a systemd machine.

I would also think that people might want to only turn a few of these options on instead of all sometimes

Probably yeah. Especially log_statement all may not always be desirable for larger apps.

Maybe an attribute set representing the configuration file would make the situation better here.

So you mean a configuration option per postgres option nested within something called logging? Yeah I can rework it into that.

Actually I think that writing of files into /var/lib/postgresql/PG_VERSION/log is because of the logging collector. I'm not sure what happens to stderr.

Actually I think that writing of files into /var/lib/postgresql/PG_VERSION/log is because of the logging collector. I'm not sure what happens to stderr.

I believe stderr is be redirected to journald.

So you mean a configuration option per postgres option nested within something called logging? Yeah I can rework it into that.

What about something like this?

Maybe that didn't work because I still had the log collector enabled? Wait I'll try again

Yeah it was that, so enabling the logging collector will capture the stderr, and then if you enable syslog you get both files and syslog output. The advantage being that logging collector will never drop a message (at a small risk of freezing the system if it's unable to write for some reason).

@jappeace what about something like this?

@aanderse I just saw yeah, but I didn't want to break backward compatibility, and I also like having the types, there are several fields which are simply weird booleans or enums.

@aanderse I just saw yeah, but I didn't want to break backward compatibility, and I also like having the types, there are several fields which are simply weird booleans or enums. But you're right, it's pretty much a one to one mapping.

The problem with applying type checking to less commonly used configuration values (ie. making them options) is that you end up replicating the entire configuration file eventually. See https://github.com/NixOS/rfcs/pull/42 for an interesting discussion on the pros and cons of options vs a single settings option (for less common configuration). This RFC is likely to become the recommendation to module authors going forward.

@aanderse Okay, I see, so module size appears to be a big problem (I thought it was the opposite, more = better). These logging options then shouldn't be added as separate options but as in your suggestion. You should make a PR for that.


The model_urls are broken

The model_urls = {
'iresnet34': 'https://sota.nizhib.ai/pytorch-insightface/iresnet34-5b0d0e90.pth',
'iresnet50': 'https://sota.nizhib.ai/pytorch-insightface/iresnet50-7f187506.pth',
'iresnet100': 'https://sota.nizhib.ai/pytorch-insightface/iresnet100-73e07ba7.pth'
} are broken,
could you please update the urls or give the new way to downloading the models.
Thank you very much!

Or you can upload models to Google drive, anyway thanks :D

I've disabled them because of the storage traffic spikes I had to pay too much for.
You can download the old mxnet weights from https://github.com/deepinsight/insightface/tree/master/model_zoo (R100 mxnet link in the table) and use the scripts provided in my repo to convert them.


Implement an "omni tool" for the gallery

Show on the gallery page.
Allow the user to go forward and back through pages if the sort isn't "random".
Allow the user to choose a sort: "random", "ascending", and "descending".
Allow the user to choose a filter: by artist and by week.
Allow the user to perform a search.
Allow the user to to to the top of the page on click (stretch: make it smooth).

A similar stripped-down omnitool could be used for the Weeks page which just has a "to top" feature.

Implemented.


Plugins using System.Net.Sockets do not compile in version 1.27.0 and beyond (.NET 8 update)

Describe the issue
There seems to be some issue with the .NET 8 implementation since plugins using System.Net.Sockets cannot compile (they work fine with 1.26.1 and earlier).
Error is:
error CS1069: the type name 'TcpListener' could not be found in the namespace 'System.Net.Sockets'. This type has been forwarded to assembly...
This is strange since I could not find any reference of TcpListener being removed in .NET 8.

Expected behavior
Plugins compile fine.
Plugin code:
using MultiFunPlayer.Common;
using System.Diagnostics;
using System.Globalization;
using System;
using System.IO;
using System.Text;
using System.Net.Sockets;
using System.Net;
using System.Threading;
using System.Threading.Tasks;
using System.Collections.Generic;
using Newtonsoft.Json;
using System.Linq;
using Stylet;
using System.Reflection;
using NLog;
using System.Xml.Serialization;

namespace Demo;

public class WebsocketPlugin : AsyncPluginBase
{
	private TcpListener _tcpListener = null;
	Socket client = null;

    protected override void Dispose(bool disposing)
    {
        if (_tcpListener != null)
        {
            _tcpListener.Stop();
        }
    }
    protected override async Task ExecuteAsync(CancellationToken cancellationToken)
    {
        _tcpListener = null;
		try
		{
			IPAddress ipAddress = IPAddress.Parse("<IP_ADDRESS>");

			Logger.Info("Starting TCP listener...");

			_tcpListener = new TcpListener(ipAddress, 5050);

			_tcpListener.Start();

			while (!cancellationToken.IsCancellationRequested)
			{

				Logger.Info("Server is listening on " + _tcpListener.LocalEndpoint);
				Logger.Debug("Waiting for a connection...");

				try
				{
					client = await _tcpListener.AcceptSocketAsync(cancellationToken);
				}
				catch (Exception)
				{
				   // continue;
				}

				if (client == null)
				{
					//continue;
				}

				Logger.Debug("Connection accepted.");

				byte[] data = new byte[1024];
				while (!cancellationToken.IsCancellationRequested)
				{

					Logger.Debug("Reading data...");
					try
					{
						int size = client.Receive(data);
						string content = Encoding.UTF8.GetString(data).Substring(0, size);
						string[] ContArray = content.Split(",");
						double pos = double.Parse(ContArray[0]);
						double time = double.Parse(ContArray[1]);
						Logger.Debug($"Received data: {content}");
						InvokeAction("Axis::Value::Set", DeviceAxis.Parse("L0"), pos, time);
					}
					catch (Exception e)
					{
						break;
						Logger.Debug(e, "or Client disconnected");
					}
				}
			}
		}
        catch (Exception e)
		{
				Logger.Error(e, "Error starting plugin");
		}
		finally
        {
			client.Close();
            Logger.Info("TcpListener closing");
			InvokeAction("Axis::Value::Set", DeviceAxis.Parse("L0"), 0.01, 0.5);
            if (_tcpListener != null)
            {
                _tcpListener.Stop();
            }
        }
    }
}```

Hmm yea it seems like MFP code does not use TcpListener anywhere so the assembly is not referenced.
Add //#r "name:System.Net.Sockets" at the top and it should work.
I think you are also missing using MultiFunPlayer.Plugin;

Hmm yea it seems like MFP code does not use TcpListener anywhere so the assembly is not referenced. Add //#r "name:System.Net.Sockets" at the top and it should work.
I think you are also missing using MultiFunPlayer.Plugin;

Adding //#r "name:System.Net.Sockets" worked, thanks! I'm curious about the double slash, usually that just makes the line a comment. Is the //#r specific to MFP plugins? Official C# syntax seems to be #r only: https://github.com/dotnet/interactive/blob/main/docs/magic-commands.md#c-kernel

Last I checked if you try to compile the plugin with #r it wont work and will show a compilation error. It only seems to work in C# scripts, it does not work when compiling into a in memory dll/assembly.
I had to implement a similar feature for MFP plugins but it has to compile hence its commented. I think I tried to preprocess the source code so that #r would be commented for compilation inside MFP but then debugging does not work since the source code is different.
FYI you should be able to debug your plugin via Visual Studio or VSCode by attaching to MFP process and adding a breakpoint into your plugin source code.


drag and drop of method that fails recompile could be handled better

When testing drag and drop of methods to make sure they went to the right side (class, instance), I dragged a method that referenced an instance variable to a place in the hierarchy above the class that implemented it.  it failed compilation (with an undefined symbol error).
I saw the method pane flash pink but then it acted like nothing happened, displayed the target class's class definition, and the dragged method was not there.

This case works correctly in 3.0.74


Linux Mint Guest OS crashes while using VSCode

Issue Type: Bug
problem:
VirtualBoxVM crashes with Application Error while running VSCode

start with Windows 10
Run Oracle VirtualBox
create linux mint VM
run linux mint VM
install VSCode for Linux from tar.gz
clone some repo from GitHub
cd into local repo and start editor (usually code -a .)
work with VSCode in local clone (unsure exactly what activity triggers this)

After some unpredictable amount of time, clicking on a menu or the settings icon (maybe some other actions also trigger), the expected pop-up menu will be all black instead of filled with content.  A short time (usually no more than a minute) later, the guest VM will be unresponsive and an Application Error dialog will appear in the Win10 host.  The VM is dead at this point.  Here is the content of the dialog just received:
The instruction at 0x00007FF84210F161 referenced memory at
0x00000000000000000000000000000000.  The memory could not be written.

Click on OK to terminate the program

This has been a consistent problem in the VSCode versions since I started.  May be tied to git plugin and editing in a directory that is a git repo.
VS Code version: Code 1.40.0 (86405ea23e3937316009fc27c9361deee66ffbf5, 2019-11-06T18:14:08.920Z)
OS version: Linux x64 4.15.0-70-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (1 x 1991)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: disabled_offoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: unavailable_offviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 0

Memory (System)
5.82GB (3.37GB free)

Process Argv
-a . --no-sandbox

Screen Reader
no

VM
100%

Extensions (6)

Extension
Author (truncated)
Version

gitlens
eam
10.1.2

vscode-docker
ms-
0.8.2

python
ms-
2019.10.44104

cpptools
ms-
0.26.2-insiders

preview-vscode
myh
1.3.0

vscode-print
pdc
0.7.13

Also:
(base) mintadmin@mint-vm:~/.../eclipse/adl2pydm$ more /etc/os-release
NAME="Linux Mint"
VERSION="19.2 (Tina)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 19.2"
VERSION_ID="19.2"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.ubuntu.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=tina
UBUNTU_CODENAME=bionic

Windows 10 host details (running Oracle VirtualBox)
VS Code version: Code 1.40.0 (86405ea23e3937316009fc27c9361deee66ffbf5, 2019-11-06T17:02:13.381Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 1992)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.85GB (6.32GB free)

Process Argv
-a .

Screen Reader
no

VM
0%

screen shot at time of recent crash

Linux Mint Guest VM is in right panel

Suspecting that git is involved, will try working without plugins next.

FYI: code -a --disable-extensions .
System still crashed.

This screen shows one of the symptoms.  In this case (just installed VSCode-linux-x64-1573664143 now), starting with: code -a --disable-extensions ., opened one of the python source code files.  Then clicked on the settings gear (planning to look for plugin configuration to verify that plugins are still off) and received this black box instead of a pop-up menu:

And now the VM has crashed with exactly the same VirtualBoxVM.exe - Application Error dialog as originally posted: The instruction at 0x00007FF84210F161 referenced memory  ...
Hope this is enough info for y'all to figure this one out.

Ok, one more variation to try (don't use the -a option), once the VM is restarted.  code --disable-extensions

This is not a good sign (tried clicking the settings gear):

Any other diagnostics?

... and system has now crashed again
Was moving mouse between menus, looking if any of them would appear with text content rather than all black.  Started with Help (all black), slid left to Terminal (text content), back to Help (all black and VM crashed right away.)

Can you run with code --disable-gpu and see if it still crashes ?

Started with code --disable-gpu  and observe no initial problems while clicking the settings gear or moving between the different items in the menu bar.  Before, symptoms were displayed during these activities as shown above.
Before we declare this to be a finding, let's work with it a bit, typical activities, and see if problem recurs.

Here's the VirtualBox Display setup for this VM:

restarted code as code --disable-gpu -a . and still no problems
This "works for me now".  However, not closing the issue since it remains a bug.  I assume you have all you need to resolve it?

Oh, two more things that may not have been clear about the system description:

VSCode is installed by the unprivileged user, not root account, in subdirectory of ~/Apps/, subdir includes the build number so I can easily revert if desired
linux mint Mate variant is used

update:  worked with that (code --disable-gpu -a .) all day with no problems
Looks like a NULL pointer was not checked, perhaps related to when GPU use is enabled.
Once that line of code is found, will you follow up with Oracle VirtualBox?  There is no way that a user program on linux (even in a VM) should crash the entire machine.

It just crashed out.  Same error message.  Crashes only happen when interacting with VSCode editor.

Thanks for testing this, the fix for it has to come from chromium. I am leaving the issue open until the fix is landed in future versions, can you test our exploration build from https://github.com/microsoft/vscode/issues/84574#issuecomment-553260601 that has newer chromium runtime to see if its fixed.

On it now.  And, thanks for being responsive!

Youch!  Crashed right out in this many minutes!  (started with code -a .)

Specifically, had been editing python code.  Needed to configure the new app with theme and extensions (GitLens, Python).  Ran debugger once.  No problems yet.  Edited a .coveragerc file and git commit.  When trying to do the git push, got the black pop-up menu.  Tried using the menubar.  Help menu OK, Debug menu all black and then VM crashed.

Thanks for the repro steps, I will see if I can narrow down the issue from upstream. Will ping back if needed addional info.

FYI, this installation detail:
(base) mintadmin@mint-vm:~/.../eclipse/adl2pydm$ ll ~/Apps/VSCode-linux-x64/bin/
total 4.0K
lrwxrwxrwx 1 mintadmin mintadmin   18 Nov 18 17:10 code -> ./code-exploration*
-rwxr-xr-x 1 mintadmin mintadmin 1.7K Nov  7 20:47 code-exploration*

This is a known issue when running Chrome (and Electron, and anything built on Electron) under VirtualBox. See https://www.virtualbox.org/ticket/15417 and https://www.virtualbox.org/ticket/12738
The issue has been known for many years. Apparently there aren't enough resources at VirtualBox to work on a fix, so don't expect one soon. For now your best bet is either using the --disable-gpu flag, or moving to a different virtualization software, e.g. VMWare Workstation, if you don't mind going proprietary. I can confirm these issues went away when I migrated my VM from VirtualBox to VMWare Workstation.

Additionally, if memory serves well, I believe my workaround back in the day was to quit the application with ctrl-q as soon as the graphical glitches started to appear. If you catch it in time, you can simply quit and relaunch the application and your VM will keep on truckin'.

Aha!  Well, thanks for getting to the root cause of this issue.  I confirm your empirical approach to quit as soon as glitches start to appear.  That has worked for me as well.  For now, this conversation has helped me remember to use --disable-gpu when in the VM.
Let's leave this issue open until the upstream (VirtualBox) issues are resolved, if ever.  That would be helpful to others who encounter this problem, seeing it as yet unresolved.

@deepak1556 & @jrial: I applaud you both on your responsiveness and diligence on this issue.

Understood this issue is closed, but as a note for future visitors, this issue affects VMWare Fusion as well.

jmaha: no, this issue is still open. It was mentioned in another issue, which has been closed.
Quoting @prjemian:

Let's leave this issue open until the upstream (VirtualBox) issues are resolved, if ever. That would be helpful to others who encounter this problem, seeing it as yet unresolved.

@jrial Aha, thanks for the clarification. Well I can confirm the same issue with VMWare Fusion, and also can confirm that setting the --disable-gpu flag in all VSCode (and disabling hardware acceleration in my Chromium-based Electron app in development) eliminates the graphical corruption -> OS crash issue described here.

I just tried this with the latest version of VSCode on a ubuntu VM. After opening VSCode and pressing right click on a file in the side panel shows an empty context menu. Second right click crashes the VM.

Same symptoms here with Centos7.
Followed these instructions insode VSCode to fix - no performance changes other than it doesn't crash!
Open the Command Palette (Ctrl+Shift+P).
Run the Preferences: Configure Runtime Arguments command. This command will open a argv.json file to configure runtime arguments.
You might see some default arguments there already.
Add
"disable-hardware-acceleration": true
Restart VS Code.

On my linux mint, that file is ${HOME}/.vscode/argv.json

Also happens on Ubuntu 19.10, fully updated, latest vs code

I have the very same issue using Virtual Box and Red Hat 7.8 as the guest OS. Using VS Code version 1.44.2. The only way to make it stable is to open it with code --disable-gpu -a

I'm having this same issue with a centos 7 in a virtual box vm.  Opening right-click context menus will eventually crash the whole VM.

Related?  #98924

Yes.

Still experiencing the same crash when clicking VSCode menu on LinuxMint VM. VSCode menus turns black and the whole VM is crashed. Experienced each time tried to use the VSCode menu.

Ran into the same issue (although no crash dialog pops up) with Ubuntu 20 (guest) on Windows 10 with Virtual box. After losing many hours of work time to this, I found the workaround here but it doesn't seem to be a long term solution.

You should check out a more permanent fix here.
Until they fix it, it's the better we got.
P.S. Can you confirm it still works.

You should check out a more permanent fix here.
Until they fix it, it's the better we got.
P.S. Can you confirm it still works.

no, it did not work for me, thanks anyway! I have finally switched to a dual boot machine.

At least you can spend many hours to all the guys trying to work with Visual Studio Code And add a banner with All Red CAPS on the homepage stating that VirtualBox is not compatible with this app!

Same issue - seems like dual boot is the solution

Same issue when working with xubuntu on virtualbox, centos works fine.

Same issue when working with xubuntu on virtualbox, centos works fine.

Can you reproduce with v86? https://copy.sh/v86/
If you want to try with Arch, https://copy.sh/v86/?profile=archlinux&c=.%2Fnetworking.sh%3Bdate --set%3D"`hwclock`"%3B.%2Fstartx.sh

Closing as the upstream issues https://github.com/microsoft/vscode/issues/84745#issuecomment-561645280 have not gained any momentum. Please continue to disable hardware acceleration in VSCode for this specific setup as workaround.

The upstream issues are cited above.


Orphan replica set after upgrade with a different app selector value

Don't know if this is a helm bug, kubernetes, please advice
This happens when upgrading an existing deployment with the "same REALEASE name" but the app selector used by the deployment is not the same.
My application gets deployed using an existing chart and I passing the -f option to override some fields, one of these fields is the app selector on the deployment.yaml template
ex.
spec:
  replicas: {{ .Values.replicaCount }}
  selector:
    matchLabels:
      app: {{ .Values.applabel }}

If for any reason I decide to change the app selector when upgrading an existing release I will end up with two replica sets of the same deployment but one of them being a left over from previous deployment. Looks like there is not proper clean up when the selector changes.

Yeah, this is a known limitation of Deployments and other similar types. Kubernetes doesn't keep track of the "old" label selector, so if the labels or the label selector change, Kubernetes orphans the old replica set (or in some cases the pods).
The best we've been able to do in Helm is suggest that Deployment objects (a) always specify a selector, and (b) never change any of the information that the selector uses.

@gerardo8a Closing due to inactivity and since it is a known issue. Please re-open or create another issue if you need further assistance. Thanks!

hi, are there any recommendations to fix this.

This kubernetes behaviour is somewhat annoying in helm context since helm is able to create necessary resources back is necessary. If anyone is looking for solution to this replicaset flood in your cluster this has helped us https://github.com/kubernetes/kubernetes/issues/24330#issuecomment-210670062


Add bool to verify()

What would you like to see added?
Add a return value to verify()
Additional Context
Can we add a bool as a return code for verify()?   It's not appropriate to use exceptions in all environments to handle failures.

It's not appropriate to use exceptions in all environments to handle failures

You don't have to use exceptions, the verify method provides a overload that accepts a std::error_code which gets filled with details about the verification error. If you provide a error code the verify method won't throw (except for truly exceptional circumstances like OOM).
Ideally you should check the reason the verification failed and give the provider of the token a hint on what went wrong, but if all you care about is a true/false result you can simply use std::error_code's operator bool to check for errors (true meaning an error occurred).
I hope this clarifies your issue.

Thanks I missed that overload
On Fri, Jul 12, 2024 at 12:19 PM Dominik Thalhammer <
@.***> wrote:

It's not appropriate to use exceptions in all environments to handle
failures
You don't have to use exceptions, the verify method provides a overload
https://github.com/Thalhammer/jwt-cpp/blob/a6927cb8140858c34e05d1a954626b9849fbcdfc/include/jwt-cpp/jwt.h#L3551
that accepts a std::error_code which gets filled with details about the
verification error. If you provide a error code the verify method won't
throw (except for truly exceptional circumstances like OOM).
Ideally you should check the reason the verification failed and give the
provider of the token a hint on what went wrong, but if all you care about
is a true/false result you can simply use std::error_code's operator bool
https://en.cppreference.com/w/cpp/error/error_code/operator_bool to
check for errors (true meaning an error occurred).
I hope this clarifies your issue.
—
Reply to this email directly, view it on GitHub
https://github.com/Thalhammer/jwt-cpp/issues/355#issuecomment-2226220052,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACCDOIIX2QDQGCYEYHZ6VATZMAT5BAVCNFSM6AAAAABKXICZ3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRWGIZDAMBVGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


chore: upgrading vitest to v1.0

Sorry, I broke the reviewed working branch. Here are the fixes.

vitest to v1.0.4
@vitest/coverage-v8 to v1.0.4
Commented.

ref: https://github.com/honojs/hono/pull/1817

@watany-dev
Thanks! LGTM! Let's go!


Add django_select2 to the global space.

When javascript output is wrapped django_select2 can not be found, adding it to the window instead of a var fixes this. There may be a better way. I hit this error with this feature of django-pipeline turned on (it is by default):
https://django-pipeline.readthedocs.org/en/latest/configuration.html#wrapped-javascript-output
Everything works under the test app with this change.

No longer needed in v5


Calling .execute() on a Cursor gives issues

This doesn't work:
async def main():
    async with asqlite.connect("test.sqlite3") as conn:
        async with conn.cursor() as cur:
            print((await cur.execute('SELECT * FROM stats')).fetchone())

asyncio.run(main())

# sqlite3.ProgrammingError: SQLite objects created in a thread
# can only be used in that same thread. The object was created
# in thread id 7764 and this is thread id 34968.

while this does:
async def main():
    async with asqlite.connect("test.sqlite3") as conn:
        async with conn.execute('SELECT * FROM stats') as cur:
            print(await cur.fetchone())

asyncio.run(main())

@thegamecracks suggested in the discord server:
asqlite.Cursor.execute() returns sqlite3.Cursor

This code shouldn't have worked. Thanks. Fluent style chaining like this requires chained await.


Add sarabalter's title

created a branch, created a file and made a commit, and opened a pull request


docs: add info about community meeting

Signed-off-by: Navendu Pottekkat<EMAIL_ADDRESS>Adds info about the community meeting to the events page.

@Boburmirzo @Nas-asira Could you please check this out?


Common Module: Connect-SQL verbose messaging

Verbose switch is enabled on the verbose message. I'd prefer if verbose wasn't forced
Yes:
write-verbose 'Message'
No:
write-verbose 'Message' -Verbose

This is a workaround for a bug that the Verbose logs are not outputted from helper functions (in an imported module) when for example running a configuration with Start-DscConfiguration -Verbose.

I can't find the issue where this was discussed (maybe in the DscResource). Can you confirm that the helper function actually output verbose messages without the -Verbose?

Interesting. I didn't try to run it like that. I'll verify and see.

@johlju I'm going to open this as a separate ticket for investigation, i added them back in for now. Although I thought CmdletBinding took care of things like that.

Although I thought CmdletBinding took care of things like that.

So did we, when we discussed it. But it seems to only happen when LCM is running the resources, so the $VerbosePreference is not passed to helper functions in the next level of modules. Another workaround is to call the helper functions with ´-Verbose:$VerbosePreference, but I thought it was to complicated to remember for contributors. But I can have missed the -Verbose` parameter in new helper function when I have reviewed. 🙂


mapToOneOrDefault?

Instead of mapToOneOrNull.

Why not both? In more functional languages, for monadic data structures, they often expose a getOrElse and an orNull like http://www.scala-lang.org/api/2.11.7/index.html#scala.Option.

I'm hoping that the use of null is more of a rarity than the norm in this case, and that those who actually want null can just pass it explicitly as a default. I realize that it's only one method and all it does is call another, but every method has a cost and unless there's a compelling reason to have both I always default to having only one.

Understandable; Android DEX limits. :)


List and remove deprecated and or abandonware dependecies

One of the initial tasks must be the removal of deprecated and abandonware dependencies.
Cleaning the project will open the road for the update to Polymer 2.
The dropping of dependencies will create the need to refactor the Theme.
A "substitution" issue will be open for each dropped dependency.

List of dropped dependencies
(grouped by replacement or reason)
app-layout (rep)

paper-drawer-panel
paper-scroll-header-panel
paper-menu
paper-toolbar

paper-styles  (rep)

paper-material

Web Animations API or CSS animations (rep)

neon-animation

Abandonware (rea)

fontawesome-iconset

It also looks like the paper-card element (replacement for paper-material) has better support for proper implementation of the material design specification for cards. This means it's probably possible to get rid of the entire existing custom x-card element.


PaLM/Bard Image support

Bard now supports images. For example, I asked it to show me an image of "cat-dog" and it pulled up a Wikipedia image from that 90's cartoon.
The wrapper is returning something like this atm:
You: Thats okay, can you show me an image from the web?

Could be the bison model is not Bard, or I need to program around this.

}
],
"messages": [
{
"author": "0",
"content": "Can you show me an image of a cat-dog?"
},
{
"author": "1",
"content": "I am a large language model, also known as a conversational AI or chatbot trained to be informative and comprehensive. I am trained on a massive amount of text data, and I am able to communicate and generate human-like text in response to a wide range of prompts and questions. For example, I can provide summaries of factual topics or create stories.\r\n\r\nHowever, I am not able to generate images."
},
{
"author": "0",
"content": "Thats okay, can you show me an image from the web?"
}
]
}

So the Makersuite playground responds in the same way as my wrapper.
It looks like the functionality is currently limited to the Bard Portal.
All good. Will monitor and dig into this more.

https://9to5google.com/2023/05/23/google-bard-images/
I might have to wrap additional APIs into this. Google Lens?

Alright got a roadmap, looks a little bit like this:
a) google image search API for "[Image of a ...]" tags
https://www.serphouse.com/blog/api-to-get-images-from-google
b) fetch the image to display?
c) also Google Lens will be different for interpretation.
Thoughts:
possibly wrong rabbit hole to explore.
Where are Google PaLM API gurus?! (hard to find solid resource to reference. Everyone else is using the session cookie from Bard Portal... not pure api. d'oh)

w00t w00t Got images to appear via google search api. (If chatgpt has similar tags for images or I can coax it into forming them, I should be able to make similar modification to that model.)
I'll need to play with context, or introduce examples. Eva is playing dumb sometimes and I have to convince her she has access to web image search.

https://developers.google.com/custom-search/v1/reference/rest/v1/cse/list#response

A couple of things atm:
a) queries are truncated a few characters... I suspect one of the 3s in the code.
b) Sometimes response returns a link that returns a 404, need to find away to exclude those first.
c) Might need to adjust context, sometimes doesn't realize she has the ability to show images.
Also the links above have some good snippets of information to reference.

Links:
https://cloud.google.com/vision/docs/detect-labels-image-api
https://cloud.google.com/vision/docs/reference/rest/v1/AnnotateImageRequest
https://developers.google.com/custom-search/v1/reference/rest/v1/cse/list#response
https://cloud.google.com/vision/docs/labels
https://cloud.google.com/vision#section-2
https://www.serphouse.com/blog/api-to-get-images-from-google
https://9to5google.com/2023/05/23/google-bard-images/
https://cloud.google.com/vision/docs/detecting-web#vision_web_detection-drest
https://developers.google.com/custom-search/docs/element

Might need minor tweaks here and there, but overall happy with current iteration.


spark_disconnect does not close a Livy connection

After succesfully connecting to Livy and performing some operations, the connection is not closing when passing the spark_disconnect(sc) command.  The Spark application remains open.  Here's my connection string:
devtools::install_github("rstudio/sparklyr")

library(sparklyr)

library(dplyr)

sc <- spark_connect(master="http://[ip address]:8998" ,
                method="livy", config=list())

Thanks! Fixed in 0.4.39


Question: Error while cucumber report generation post test execution

I often get below error post test case(s) execution, while generation of cucumber report. The json report file also remains empty.
Error in reporter Error: Pickle not found
    at TestCase.findPickle (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright-bdd\src\reporter\cucumber\messagesBuilder\TestCase.ts:133:24)
    at TestCase.addRun (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright-bdd\src\reporter\cucumber\messagesBuilder\TestCase.ts:52:27)
    at C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright-bdd\src\reporter\cucumber\messagesBuilder\index.ts:123:16
    at Array.forEach (<anonymous>)
    at MessagesBuilder.createTestCases (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright-bdd\src\reporter\cucumber\messagesBuilder\index.ts:114:23)
    at MessagesBuilder.doBuildMessages (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright-bdd\src\reporter\cucumber\messagesBuilder\index.ts:91:10)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at CucumberReporterAdapter.onEnd (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright-bdd\src\reporter\cucumber\index.ts:69:5)
    at ReporterV2Wrapper.onEnd (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright\lib\reporters\reporterV2.js:91:12)
    at wrapAsync (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright\lib\reporters\multiplexer.js:79:12)
    at Multiplexer.onEnd (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright\lib\reporters\multiplexer.js:51:25)
    at InternalReporter.onEnd (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright\lib\reporters\internalReporter.js:70:12)
    at Runner.runAllTests (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright\lib\runner\runner.js:77:28)
    at runTests (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright\lib\program.js:218:18)
    at t.<anonymous> (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright\lib\program.js:55:7)

Error in reporter Error: Pickle not found
    at TestCase.findPickle (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright-bdd\src\reporter\cucumber\messagesBuilder\TestCase.ts:133:24)
    at TestCase.addRun (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright-bdd\src\reporter\cucumber\messagesBuilder\TestCase.ts:52:27)
    at C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright-bdd\src\reporter\cucumber\messagesBuilder\index.ts:123:16
    at Array.forEach (<anonymous>)
    at MessagesBuilder.createTestCases (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright-bdd\src\reporter\cucumber\messagesBuilder\index.ts:114:23)
    at MessagesBuilder.doBuildMessages (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright-bdd\src\reporter\cucumber\messagesBuilder\index.ts:91:10)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at CucumberReporterAdapter.onEnd (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright-bdd\src\reporter\cucumber\index.ts:69:5)
    at ReporterV2Wrapper.onEnd (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright\lib\reporters\reporterV2.js:91:12)
    at wrapAsync (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright\lib\reporters\multiplexer.js:79:12)
    at Multiplexer.onEnd (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright\lib\reporters\multiplexer.js:51:25)
    at InternalReporter.onEnd (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright\lib\reporters\internalReporter.js:70:12)
    at Runner.runAllTests (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright\lib\runner\runner.js:77:28)
    at runTests (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright\lib\program.js:218:18)
    at t.<anonymous> (C:\Users\ADMIN\Desktop\sample-automation\node_modules\playwright\lib\program.js:55:7)

I will definitely enrich error message with more details.
In upcoming playwright-bdd v8 this part was changed, so the error should gone.
Is that error appears on every test run or it's a floating one?

I think I am still using 7.5.0. It does not appear on every test though. But often when I run multiple tests I see this, have no idea why it happens

I think I am still using 7.5.0.

Yes, v8 is not released yet.

It does not appear on every test though.

Could you show the content of your playwright.config.ts (if possible)?

When will the v8 get released ??
Also , any idea why we see the other error posted above ??
Error in reporter Error: Attachment without body and url

When will the v8 get released ??

Within this or next week.

Also , any idea why we see the other error posted above ??
Error in reporter Error: Attachment without body and url

Do you add any attachments manually in tests?

Nope, even when I commented out the attachments, I still see the error twice , no idea why

I think I am able to reproduce the error now .
I have jar file which i run in a child process. It takes an argument and return a string. Every time this piece of code runs, I get the error "Error in reporter Error: Attachment without body and url"
Then( 'I see in title {string}', async ( { page }, pageTitle: string ) => {
	// Verify the page title
	await expect( page ).toHaveTitle( pageTitle );

	try {
		// Run the child process command
		const output = execSync( 'java -jar library.jar "XXXX XXXX XXXX XXXX"' ).toString();

		// Log the output or perform further actions
		console.log( 'Java Help Output:', output );
	} catch ( error ) {
		// Handle potential errors
		console.error( 'Error running command:', error.message );
	}
} );

Also even When you run a simple command like "java -help" in a child process, you can see stderr attachment in playwright html report

Fixed in Playwright-BDD v8.


Fix display issue where carousel was breaking out of grid.

Changes

Fixes a display issue where carousel in "Prove It" section was breaking out of the grid in Firefox.

References #3834. For review: @DoSomething/front-end

:+1:


feat(Volume):added wiki link

Try to fulfill the following points before the Pull Request is merged:

[ ] The PR is reviewed by one of the team members.
[ ] It must be checked if anything in the Readme must be adjusted (development-, production-, setup).
[ ] It must be checked if any section in the wiki (https://cloud.denbi.de/wiki/) should be adjusted.
[ ] If the PR is merged in the master then a release should be be made.
[ ] The PR is responsive on smaller screens.
[ ] If the requirements.txt have changed, check if the patches still work
[ ] If the new code is well commented

For releases only:

[ ] If the review of this PR is approved and the PR is followed by a release then the .env file
in the cloud-portal repo should also be updated.
[ ] If you are making a release then please sum up the changes since the last release on the release page using the clog tool with clog -F

@DavidWein94  @vktrrdk  we should update the wiki regarding volume handling. (As described by the PR Template tasks)


React compatabilty?

Is your feature request related to a problem? Please describe.
My issue is when I have a useState hook the setter value is use with () brackets so I want it to automatically add those when I autocomplete the name with nvim-cmp. The problem is if I set the below kind of config for Field, (which is what the setter is) it causes alot of problems when just trying to use lots of other normal variables.
Describe the solution you'd like
Can there be some kind of compat added for these sorts of setter functions or some other alternative to fix this problem?
Describe alternatives you've considered
I have tried using mini.pairs plugin but it lacks alot of configuration and general usability compared to this plugin.
Additional context
The config mentioned:
	{
		"windwp/nvim-autopairs",
		opts = {
			fast_wrap = {},
			disable_filetype = { "TelescopePrompt", "vim" },
			enable_check_bracket_line = false,
		},
		config = function(_, opts)
			require("nvim-autopairs").setup(opts)

			-- setup cmp for autopairs
			local cmp_autopairs = require("nvim-autopairs.completion.cmp")
			local cmp = require("cmp")
			local handlers = require("nvim-autopairs.completion.handlers")
			cmp.event:on(
				"confirm_done",
				cmp_autopairs.on_confirm_done({
					filetypes = {
						["*"] = {
							["("] = {
								kind = {
									cmp.lsp.CompletionItemKind.Function,
									cmp.lsp.CompletionItemKind.Method,
                                                                        -- This is not good
                                                                        cmp.lsp.CompletionItemKind.Field,
								},
								handler = handlers["*"],
							},
						},
					},
				})
			)
		end,
	},

bump

I think you can write a custom handler to check if a completion text has a useState.
Personally, I use Luasnippet for that useState.
local ls = require('luasnip')
-- some shorthands...
local s = ls.snippet
local text = ls.text_node
local insert = ls.insert_node
local lambda = require('luasnip.extras').lambda

return {
    -- use state
    s('us', {
        text('const ['),
        insert(1, 'state'),
        text(', set'),
        lambda(lambda._1:gsub('^%l', string.upper), 1),
        text('] = useState('),
        insert(2, 'initialState'),
        text(')'),
    }),
    -- use effect
    s('ue', {
        text({ 'useEffect(() => {', '\t' }),
        insert(1, 'effect'),
        text({ '', '}, [' }),
        insert(2, 'input'),
        text('])'),
    }),
}

Thanks I'll use that!


Support NATS error codes for JetStream interactions

Overview
Prefer NATS error codes when conditionally handling JetStream API errors and expose the code to users.
The basic idea is that in the past we would return errors like replicas > 1 not supported in non-clustered mode in the ApiErr and clients would parse these messages if they wanted to handle different errors differently.
Another case would be when accessing a consumer, you'd get a error like 404 but you would not know if this is due to a stream being missing or a consumer being missing.
We now have codes in addition to the errors, the replicas > 1 not supported in non-clustered mode has code 10074, libraries should check this code rather than parse the text.  The error text is not part of the API promises and we need to be able to make changes to language, typos, etc.
The cli has nats error lookup 10074 to compliment these.
The behavior is documented in ADR-7, initial server PR https://github.com/nats-io/nats-server/pull/2168
Clients and Tools

[x] Schemas @ripienaar https://github.com/nats-io/jsm.go/commit/bf9eafc7e3f0a4a6faca1344d7f389be24ac49aa
[x] CLI @ripienaar
[x] Go @piotrpio
[x] Java @scottf
[x] JavaScript @aricart
[x] .Net @ColinSullivan1
[x] C @kozlovic (implemented since the get-go, currently on branch https://github.com/nats-io/nats.c/tree/js)
[x] Python @wallyqs
[ ] Rust @Jarema

Other Tasks

[ ] docs.nats.io updated
[ ] Update ADR to Implemented
[x] Update client features spreadsheet

Client authors please update with your progress. If you open issues in your own repositories as a result of this request, please link them to this one by pasting the issue URL in a comment or main issue description.

Following releases of the Go client use errors wrapping for JetStream errors to capture APIError details: https://github.com/nats-io/nats.go/pull/1047


Request: add programmatic.solutions to the filter

Evidence: https://programmatic.solutions/u4cef7/does-python-have-a-string-contains-substring-method
Original: https://stackoverflow.com/questions/3437059/does-python-have-a-string-contains-substring-method

Thanks a lot!