reboot notification comes back after clear-notification action removes it

When the reboot of sysconfig in not required and the warning to reboot comes, then you can run clear-notification action to get rid of the warning and the status of machine becomes active. However, the warning message comes back after couple of minutes and the machine status is back to blocked.
Steps to recreate:
juju deploy ubuntu
juju deploy sysconfig
juju add-relation sysconfig ubuntu
The juju status will show blocked status on sysconfig unit with message 'update-grub and reboot required. Changes in: /etc/systemd/system.conf, /etc/default/grub.d/90-sysconfig.cfg'.
You can clear the above notification by running:
juju run-action sysconfig/<unit> clear-notification --wait
and the sysconfig status is active. However after couple of minutes, the status goes back to blocked with the same message. I believe the update-status hook runs and brings back the warning.

Imported from Launchpad using lp2gh.

date created: 2022-11-22T09:57:13Z

owner: rahulsinghunsw

assignee: valexby

the launchpad url

(by rahulsinghunsw)
Juju Crashdump


SQL Server container startup fails intermittently

This was originally reported as testcontainers/testcontainers-java-module-mssqlserver#11.
We are experiencing an intermittent failures of our SQL Server integration tests that are based on org.testcontainers:mssqlserver. The error occurs in roughly 30-40% of the builds. This, however, heppens only on our Jenkins CI infrastructure, and not on Travis CI builds or local machine.
I should also note that we use TestContainers for integration of other relational databases (PostgreSQL, MySQL, MariaDB) as well, but with no such issues.
Error Message
org.testcontainers.containers.ContainerLaunchException: Container startup failed

Stacktrace
org.testcontainers.containers.ContainerLaunchException: Container startup failed
	at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:199)
	at org.testcontainers.containers.GenericContainer.starting(GenericContainer.java:628)
	at org.testcontainers.containers.FailureDetectingExternalResource$1.evaluate(FailureDetectingExternalResource.java:29)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:190)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
	at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
	at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
	at com.sun.proxy.$Proxy1.processTestClass(Unknown Source)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:108)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:146)
	at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:128)
	at org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:404)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit with exception
	at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:83)
	at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:192)
	... 34 more
Caused by: org.testcontainers.containers.ContainerLaunchException: Could not create/start container
	at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:264)
	at org.testcontainers.containers.GenericContainer.lambda$start$0(GenericContainer.java:194)
	at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:76)
	... 35 more
Caused by: org.rnorth.ducttape.TimeoutException: org.rnorth.ducttape.TimeoutException: java.util.concurrent.TimeoutException
	at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:53)
	at org.testcontainers.containers.JdbcDatabaseContainer.waitUntilContainerStarted(JdbcDatabaseContainer.java:88)
	at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:243)
	... 37 more
Caused by: org.rnorth.ducttape.TimeoutException: java.util.concurrent.TimeoutException
	at org.rnorth.ducttape.timeouts.Timeouts.callFuture(Timeouts.java:59)
	at org.rnorth.ducttape.timeouts.Timeouts.getWithTimeout(Timeouts.java:32)
	at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:38)
	... 39 more
Caused by: java.util.concurrent.TimeoutException
	at java.util.concurrent.FutureTask.get(FutureTask.java:205)
	at org.rnorth.ducttape.timeouts.Timeouts.callFuture(Timeouts.java:54)
	... 41 more

Standard Error
Feb 12, 2018 7:09:36 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING: ConnectionID:1 ClientConnectionId: 6534f393-9bf8-4278-9eae-d3a9aaaeb4e1 Prelogin error: host localhost port 32929 Unexpected end of prelogin response after 0 bytes read
Feb 12, 2018 7:09:36 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING: ConnectionID:1 ClientConnectionId: 2a9df843-bd21-431f-8e04-5f295ee14db4 Prelogin error: host localhost port 32929 Unexpected end of prelogin response after 0 bytes read
Feb 12, 2018 7:09:36 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING: ConnectionID:1 ClientConnectionId: 994e2acb-4024-44ba-8b23-cd39f4c03841 Prelogin error: host localhost port 32929 Unexpected end of prelogin response after 0 bytes read
Feb 12, 2018 7:09:36 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING: ConnectionID:1 ClientConnectionId: 997b401c-97a2-4ace-aa9d-ca0477cacc73 Prelogin error: host localhost port 32929 Unexpected end of prelogin response after 0 bytes read
Feb 12, 2018 7:09:37 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING: ConnectionID:1 ClientConnectionId: c697678a-ad5d-4991-8e9d-8e7c20cb2f5d Prelogin error: host localhost port 32929 Unexpected end of prelogin response after 0 bytes read
Feb 12, 2018 7:09:38 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING: ConnectionID:1 ClientConnectionId: acdebecf-da3d-42cc-9d3c-e8c7f610b0ea Prelogin error: host localhost port 32929 Unexpected end of prelogin response after 0 bytes read
Feb 12, 2018 7:09:39 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING: ConnectionID:1 ClientConnectionId: 4b57c876-48c6-431c-b958-da86ef5b2e4c Prelogin error: host localhost port 32929 Error reading prelogin response: Connection reset ClientConnectionId:4b57c876-48c6-431c-b958-da86ef5b2e4c
Feb 12, 2018 7:09:40 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING: ConnectionID:1 ClientConnectionId: 68e7f99e-2d70-4bcc-9fe4-654a875e56fd Prelogin error: host localhost port 32929 Error reading prelogin response: Connection reset ClientConnectionId:68e7f99e-2d70-4bcc-9fe4-654a875e56fd
Feb 12, 2018 7:09:41 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING: ConnectionID:1 ClientConnectionId: 2aabc0ea-6c43-4d94-a894-9b2c42f72f05 Prelogin error: host localhost port 32929 Unexpected end of prelogin response after 0 bytes read
Feb 12, 2018 7:09:42 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING: ConnectionID:1 ClientConnectionId: 268d348e-4694-4d8e-bae9-98071985e5bf Prelogin error: host localhost port 32929 Error reading prelogin response: Connection reset ClientConnectionId:268d348e-4694-4d8e-bae9-98071985e5bf
Feb 12, 2018 7:09:43 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING: ConnectionID:1 ClientConnectionId: b03b7801-6721-47bf-87fc-237e3a6a4bd6 Prelogin error: host localhost port 32929 Unexpected end of prelogin response after 0 bytes read

The integration test in subject is available here.
Should we permanently resort to a custom WaitStrategy or could MSSQLServerContainer get a bit more leeway out of the box?

Just pinging @StefanHufschmidt, maybe he has an idea.

We got some strange behavior with the MS SQL Server image for linux too.
It was sometimes the case that the image could not be pulled within the timeout time. - But you can see your image starting, so this should not be your problem.
Sometimes the image was strangely broken and we had to pull it again afterwards everything worked back again. - That should occur on every run afterwards until the image has been deleted and re-pulled back again. Since the MS SQL Server image is very large you might don't want to pull it every time.
I've noticed the warnings from the MS SQL Server container some time ago. This does not look very well but should not affect the whole start up process.
Since the MS SQL Server image is 1.43GB large and we have a default timeout of 120 seconds it could be that the download of the image is not fast enough. I saw that you've increased the timeout to 240 seconds. @vpavic have you tried it with an even higher value?
What's about the connection timeout?
JavaDoc says: * @return time to allow for the database to start and establish an initial connection, in seconds
Give it a try to increase it as well:
		@Override
		protected int getConnectTimeoutSeconds() {
			return 240;
		}

Sometimes the docker image seems to start very slow. So this might be a solution.

Thanks for the feedback @kiview and @StefanHufschmidt.

I saw that you've increased the timeout to 240 seconds. @vpavic have you tried it with an even higher value?

We've had this test marked with @Ignore for some time now so it didn't run on the CI env where it caused problems. Thanks for the #getConnectTimeoutSeconds tip, we'll try with that as well.
Just to note, providing custom timeout value(s) isn't a problem by itself, however when you do that in multiple different project it becomes a bit annoying, so my hope was this issue would result in a more sane default in Testcontainers.

We have had success with our integration tests that use MSSQLServerContainer for some time now with startup and connection timeouts of 240 seconds.
@kiview @bsideup Would you accept a PR that sets these timeout values as defaults for MSSQLServerContainer? That would effectively resolve this issue.

@vpavic This was solved in #748 for you, wasn't it?
I'll close for now.

@kiview See the comment just above yours - I was offering to submit a PR that would update the defaults, which is the thing that addressed the problem for us.
#748 just provided a nicer way for users to update the defaults.

Oh sorry, I see.
I think a PR would be a good idea, thanks.

Thanks - I'll try to put together a PR over the next day or two.

Looking at this, I realized that #748 actually did update the default timeouts to 240 seconds. Not sure how I managed to missed that.
Anyway, that makes this issues indeed resolved by #748. Thanks for the support!

I am experience similar random problems with DockerComposeContainer based tests. Is there a way to override the connect timeout in this case?


feat: add Lidarr and MusicBrainz support

This PR aims to add Lidarr and MusicBrainz support to Jellyseerr to address feature request #96
I'm pretty new to this kind of coding, so I'm mostly just making changes, running a build, and fixing bugs as they come up. I'm using https://github.com/sct/overseerr/pull/3800 by @anon0002 as a guide/code source for the heftier bits like the Lidarr API classes.
In feature request #96 @zachbakerdev mentioned using Deezer instead of MusicBrainz as it has more info on covers, but I'm not sure that Lidarr supports that and I've not interacted with Deezer before, so I'm currently sticking with MusicBrainz. I'm happy to also add Deezer support at some point in the future.

One of the other considerations I had was instead of using the cover art archive that Musicbrainz uses was searching on Musicbrainz for the albums, then mapping those albums to Deezer instead of the other way around. Just a consideration.

It seems like you forgot to add the type definitions I had to add so it will not work I think.
I'm talking about this
But since I don't know how jellyseer is setup you might not need it

@ano0002 I actually had a few questions about your implementation of the nodebrainz API, for example why didn't you copy the interfaces of TMDB with all of the Result interfaces?
I haven't added all of your work into this PR (yet) as I'm trying to learn a bit about Typescript/Javascript and how different people code as I'm doing this :D I'll admit I also don't have a deep understanding of how Jellyseerr functions so I'm trying to learn that as well to determine which nodebrainz features are needed.

@ano0002 I actually had a few questions about your implementation of the nodebrainz API, for example why didn't you copy the interfaces of TMDB with all of the Result interfaces?
I haven't added all of your work into this PR (yet) as I'm trying to learn a bit about Typescript/Javascript and how different people code as I'm doing this :D I'll admit I also don't have a deep understanding of how Jellyseerr functions so I'm trying to learn that as well to determine which nodebrainz features are needed.

I'll try to answer all those question when I get some time as right now I have all my final exams.

@ano0002 I actually had a few questions about your implementation of the nodebrainz API, for example why didn't you copy the interfaces of TMDB with all of the Result interfaces?
I haven't added all of your work into this PR (yet) as I'm trying to learn a bit about Typescript/Javascript and how different people code as I'm doing this :D I'll admit I also don't have a deep understanding of how Jellyseerr functions so I'm trying to learn that as well to determine which nodebrainz features are needed.

I didn't copy them because I didn't want to send the same kind of info. I could have reused it and modified it to take more parameters but that would have meant I'd have to rewrite every other time when the interface was already used so I chose to make a separate one.


[FLINK-15647][kubernetes] Support to set annotations for JM/TM Pods.

What is the purpose of the change
This PR introduces customized annotations support for JobManager/TaskManager Pods.
Verifying this change
This change added tests and can be verified as follows:

Specify new command-line parameters when deploying a session cluster, such as -Dkubernetes.jobmanager.annotation.test1=abc -Dkubernetes.jobmanager.annotation.test2=abc2  -Dkubernetes.taskmanager.annotation.test3=edf3 -Dkubernetes.taskmanager.annotation.test4=edf4
Manually check whether the newly created JobManager Pod has the customized annotations test1=abc and test2=abc2
Submit a Job to the running session cluster, then manually check whether the newly created TaskManager Pod has the customized annotations test3=edf3 and test4=edf4

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (docs)

Thanks for creating this PR @zhengcanbin. The changes look good to me.
Please rebase the PR onto the latest master. There are currently some merge conflicts. Once you have done this and Travis gives green light, then I will merge this PR.

Thanks a lot for the review @tillrohrmann! This PR relies on FLINK-16625. I will push a new commit base on FLINK-16625, meanwhile resolve the conflicts.

Hi @tillrohrmann! I have resolved the comments and both the Travis and Azure give a green light. Kindly expect to see your reply.

@flinkbot run azure


HTTP Server crashes on native posix

HTTP Server crashes on native POSIX target on http_server_init - console output below.
[net/app] [ERR] net_app_init: No network interfaces
[net/app] [ERR] init_net_app: Network initialization failed (-19)
[http/server] [DBG] http_server_add_url: (0x080e66e0): [0] HTTP URL /headers
[http/server] [DBG] http_server_add_url: (0x080e66e0): [1] HTTP URL /index.html
[http/server] [DBG] http_server_add_url: (0x080e66e0): [2] HTTP URL /
[http/server] [INF] new_server: Zephyr HTTP Server (0x080d22e0)
Segmentation fault (core dumped)

Debug shows that the problem is NULL pointer access on net_sin(&ctx->local)->sin_port = htons(port) from init_net (ctx=0x80d22e0 <http_ctx>, server_addr=0x0, port=80) at /home/khalbali/data/kalaghoda/zephyr/subsys/net/lib/http/http_server.c:840.
My suspicion is the mismatch in sockaddr structure on various platforms. This may be a good reason to align the structures.

[net/app] [ERR] net_app_init: No network interfaces

The crash happens because of this, not because of sockaddr stuff.

Works for me, just tried http-server sample application with native_posix target. Notice that you need to run the binary as a root in order to create the zeth network interface in the host side.
cd samples/net/http_server
mkdir build && cd build
cmake -DBOARD=native_posix ..
make
sudo --preserve-env=ZEPHYR_BASE zephyr/zephyr.exe

After this I was able to connect to <IP_ADDRESS>:80 from host side.


Using switch-case instead of multiple if-else

Increase code readability，using switch-case instead of multiple if-else
[ ] Configuration Infrastructure
[x] Docs
[x] Installation
[ ] Networking
[x] Performance and Scalability
[ ] Policies and Telemetry
[x] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

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

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

/ok-to-test

@ChenglongGao327: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
f0c4be9ac7e510ac1273a702a066c18e5e840c21
link
/test release-notes_istio

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

/retest

@ChenglongGao327: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
f0c4be9ac7e510ac1273a702a066c18e5e840c21
link
/test release-notes_istio

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

/retest

Thanks!


fix deadlock and goroutine leak in chunk restore

What problem does this PR solve?
fix #148
What is changed and how it works?
fix the concurrent control logic code
Check List
Tests

Manual test (add detailed scripts or steps below)
test the logic using code and  I would add integration testing in TOOL-998

/run-all-tests


Pending calls to acquire write locks block successive calls to requestRead

In the current implementation (coordinator) of the execCoordinator interface pending calls to requestWrite and fixWorkingSetWrite can block successive calls to requestRead. This lock management issue may potentially cause the occurrence of distributed deadlocks.
Affected versions:

v0.0.0..v0.1.0

Fixed in v0.2.0.


Creating token when authentication is not enabled makes the server crash (temporarily)

The server was unreachable for about 3 minutes, then we could see this in the logs:
2022-02-24 12:33:29,623 ERROR    tornado.access 500 POST /api/v1/environment_auth (<IP_ADDRESS>) 262051.11ms
2022-02-24 12:35:40,693 ERROR    inmanta.protocol.rest An exception occured during the request.
Traceback (most recent call last):
  File "/usr/lib64/python3.6/urllib/request.py", line 1349, in do_open
    encode_chunked=req.has_header('Transfer-encoding'))
  File "/usr/lib64/python3.6/http/client.py", line 1269, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/lib64/python3.6/http/client.py", line 1315, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/lib64/python3.6/http/client.py", line 1264, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib64/python3.6/http/client.py", line 1040, in _send_output
    self.send(msg)
  File "/usr/lib64/python3.6/http/client.py", line 978, in send
    self.connect()
  File "/usr/lib64/python3.6/http/client.py", line 1429, in connect
    super().connect()
  File "/usr/lib64/python3.6/http/client.py", line 950, in connect
    (self.host,self.port), self.timeout, self.source_address)
  File "/usr/lib64/python3.6/socket.py", line 724, in create_connection
    raise err
  File "/usr/lib64/python3.6/socket.py", line 713, in create_connection
    sock.connect(sa)
TimeoutError: [Errno 110] Connection timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/inmanta/lib64/python3.6/site-packages/inmanta/config.py", line 589, in validate_rs265
    with request.urlopen(self.jwks_uri, context=ctx) as response:
  File "/usr/lib64/python3.6/urllib/request.py", line 223, in urlopen
    return opener.open(url, data, timeout)
  File "/usr/lib64/python3.6/urllib/request.py", line 526, in open
    response = self._open(req, data)
  File "/usr/lib64/python3.6/urllib/request.py", line 544, in _open
    '_open', req)
  File "/usr/lib64/python3.6/urllib/request.py", line 504, in _call_chain
    result = func(*args)
  File "/usr/lib64/python3.6/urllib/request.py", line 1392, in https_open
    context=self._context, check_hostname=self._check_hostname)
  File "/usr/lib64/python3.6/urllib/request.py", line 1351, in do_open
    raise URLError(err)
urllib.error.URLError: <urlopen error [Errno 110] Connection timed out>

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/inmanta/lib64/python3.6/site-packages/inmanta/protocol/rest/__init__.py", line 488, in _execute_call
    result = await config.handler(**arguments.call_args)
  File "/opt/inmanta/lib64/python3.6/site-packages/inmanta/server/services/environmentservice.py", line 262, in create_token
    return 200, {"token": await self.environment_create_token(env, client_types, idempotent)}
  File "/opt/inmanta/lib64/python3.6/site-packages/inmanta/server/services/environmentservice.py", line 475, in environment_create_token
    return encode_token(client_types, str(env.id), idempotent)
  File "/opt/inmanta/lib64/python3.6/site-packages/inmanta/protocol/common.py", line 928, in encode_token
    cfg = inmanta_config.AuthJWTConfig.get_sign_config()
  File "/opt/inmanta/lib64/python3.6/site-packages/inmanta/config.py", line 475, in get_sign_config
    cls.list()
  File "/opt/inmanta/lib64/python3.6/site-packages/inmanta/config.py", line 439, in list
    obj = cls(name, section, cfg[section])
  File "/opt/inmanta/lib64/python3.6/site-packages/inmanta/config.py", line 507, in __init__
    self.validate_rs265()
  File "/opt/inmanta/lib64/python3.6/site-packages/inmanta/config.py", line 595, in validate_rs265
    "Unable to load key data for %s using the provided jwks_uri. Got error: %s" % (self.section, e.response)
AttributeError: 'URLError' object has no attribute 'response'

Here is the config of the server:

inmanta.cfg
# The directory where the server stores its state
state-dir=/var/lib/inmanta

# The directory where the server stores log file. Currently this is only for the output of
# embedded agents.
log-dir=/var/log/inmanta

fact-expire = 3600

# Force the hostname of this machine to a specific value
#node-name =

# Names of the agents this instance should deploy configuration for
agent-names = $node-name

# The deploy interval of the agent
agent_deploy_interval = 600

# The splaytime added to the agent_deploy_interval. Set this to 0 to disable splaytime
agent_deploy_splay_time = 600

# The repair interval of the agent
agent_repair_interval = 86400

# The splaytime added to the agent_repair_interval. Set this to 0 to disable splaytime
agent_repair_splay_time = 600

[database]
# The hostname of the database server
#host = localhost
# The port of the database server
#port = 5432
# The name of the database on the server
#name = inmanta
# The username to use to access the database
#username=
# The password to that belongs to the database user
#password=

[influxdb]
# The hostname of the influxdb server
# Enable metering by setting this value
#host = localhost
# The port of the influxdb server
#port = 8086
# The name of the database on the influxdb server
#name = inmanta
# The username to use to access influxdb
#username =
# The password to that belongs to the influxdb user
#password =
# The reporting interval
#interval = 30
# A dict of tags to attach to all influxdb records
#tags= environment=prod,az=a

[server]
# A comma-separated list of addresses on which the server will listen for connections
# ipv4 and ipv6 addresses are supported
bind-address = <IP_ADDRESS>
# The port on which the server will listen for connections
bind-port = 8888

# The public ip address of the server. This is required for example to inject the inmanta agent in
# virtual machines at boot time.
#server_address=localhost

# After how many seconds will discovered facts/parameters expire
#fact-expire = 3600

# After how many seconds will discovered facts/parameters be renewed? This value needs to be lower
# than fact-expire
#fact-renew = 1200

# The number of seconds to wait before the server may attempt to do a new recompile. Recompiles are
# triggered after facts updates for example.
auto-recompile-wait = 10

# On boot and at regular intervals the server will purge versions that have not been deployed. This
# is the number of most recent undeployed versions to keep available.
#available-versions-to-keep=10

# The number of seconds between version purging
#purge-versions-interval=3600

# Cert and key file to enable ssl in the server. Both have to be set to enable SSL.
#ssl-cert-file=
#ssl-key-file=

# Configures the Access-Control-Allow-Origin setting of the http server
# can be a single item or a list of strings
# More on Access-Control-Allow-origin:
# https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin
#access-control-allow-origin = *

[agent_client_rest_transport]
host = localhost
port = 8888
#ssl=false
#ssl_ca_cert_file=

[dashboard]
# Host the dashboard from within the server. The server does not (yet) override the config.js file
# of the dashboard. This will need to be configured manually. The dashboard will be available
# on the server under /dashboard/
enabled=true
# The path where the dashboard is installed
path=/opt/inmanta/dashboard

Hey team! Please add your planning poker estimate with ZenHub @andraskvr @arnaudsjs @bartv @FloLey @Hugo-Inmanta @sanderr


add worm tutorial

Hi @Munfred, could you take a look at this? I changed a few of the hyperparameters and added some text. Thanks!

I reviewed the content and seems to be in order, but I think the colab button is broken. It doesn't work when I try to click on it, doesn't find the notebook. And when I tried manually loading it in colab form the link https://github.com/YosefLab/scVI/blob/de_worm/docs/contributed_tutorials/scVI_DE_worm.ipynb it loads an empty notebook.
However, when I downloaded the file and uploaded it to colab, it loaded everything correctly, including the interactive plot results. I'm not sure what causes the issue.

ah, that must be because the link is pointing to the ipynb from the stable branch, which is the correct link once I pull everything there.


WSL1 works, WSL2 timesout

Environment
Windows build number: [run cmd.exe /c ver]
Microsoft Windows [Version 10.0.19043.844]
Your Distribution version: [On Debian or Ubuntu run lsb_release -r in WSL]
20.04, but cannot get into Ubuntu to run this.
Whether the issue is on WSL 2 and/or WSL 1: [run cat /proc/version in WSL]
WSL2 only.  machines work fine in WSL1, but I cannot install a WSL2 image or upgrade an existing one.
Steps to reproduce

PS C:\Users\lbuchholz> wsl --list --verbose
  NAME            STATE           VERSION
* Ubuntu-20.04    Running         1
PS C:\Users\lbuchholz> cmd.exe /c ver

Microsoft Windows [Version 10.0.19043.844]
PS C:\Users\lbuchholz> wsl --set-version Ubuntu-20.04 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
The operation timed out because a response was not received from the virtual machine or container.

WSL logs:
https://aka.ms/AAbdx7q
Expected behavior
WSL2 machine installs from store or WSL2 machine upgrades.  Both give the same error about not being able to connect to virtual machine or container.

Actual behavior

sits for 30 seconds, and then gives this error
I have tried completly uninstall the linux subsystem, Ubuntu, Hyper-V, Virt Platform etc.

Thanks for linking logs; appreciated.

WSL2 machine installs from store or

If you set the default version to WSL2 and then install a different distribution name (say Ubuntu vs Ubuntu-20.04) from the Store, does it also timeout? Setting the default version looks like:
PS C:\> wsl.exe --set-default-version 2

Afterwards install the new distro, which (assuming it succeeds) will be WSL2.

I fresh install gives this error, which I think is the same underlying problem.
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370109
Error: 0x80370109 The operation timed out because a response was not received from the virtual machine or container.
Press any key to continue...

Thanks, getting an error code is good. Capturing that error in WSL logs would be useful if you can. The error code gets a hit on open #5194.

I'll take a look at 5194, but I did a record of the actual process if that gives you anything useful.
https://aka.ms/AAbdxh0

Yea, looks like it may be the same issue as 5194

/dupe #5194


How to speed up zeth compilation efficiency?

We are running cargo build -F cuda --release on Ubuntu 22.04.4 LTS. This command takes too long, more than 30 minutes.
especially on the last few risc0 related packages.
Do you have any good suggestions to optimize the efficiency of the entire compilation？
Express my gratitude in advance~
Our environmental information is as follows:
Ubuntu 22.04.4 LTS

Architecture:             x86_64
  CPU op-mode(s):         32-bit, 64-bit
  Address sizes:          46 bits physical, 48 bits virtual
  Byte Order:             Little Endian
CPU(s):                   8
  On-line CPU(s) list:    0-7
Vendor ID:                GenuineIntel
  Model name:             Intel(R) Xeon(R) Platinum 8163 CPU @ 2.50GHz
    CPU family:           6
    Model:                85
    Thread(s) per core:   2
    Core(s) per socket:   4
    Socket(s):            1
    Stepping:             4
    BogoMIPS:             5000.00

+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.90.07              Driver Version: 550.90.07      CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  Tesla T4                       On  |   00000000:00:07.0 Off |                    0 |
| N/A   29C    P8              9W /   70W |       1MiB /  15360MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|  No running processes found                                                             |
+-----------------------------------------------------------------------------------------+

The first time doing a compilation for CUDA is expected to take a long time. It varies based on the GPU architecture and even version of the GPU drivers. I install and use sccache which makes subsequent builds go much faster.

Thank you for your guidance！
After using sccache, my compilation time was reduced to about 11mins.

But I want to further shorten the time, because after we develop locally, we need to push it to the remote server for debugging, and the long compilation time is unacceptable to us;
For example, we often only modify the code under guests folder. Under this condition, is there any way to speed up compilation?


FIX Disable HTTP caching on all relevant MFA API endpoints

Follow up to #417, applying the cache configuration to schema fetching and registration initialisation in both the main MFA UI and the Profile UI.
Fixes #393.

@emteknetnz Have applied tests, and expanded the scope a bit (I realised this might be impacting the registration flow in the Profile UI too, and noticed that there were early exits in the registration flow so shifted all of the cache control into LoginHandler for consistency.)


Everything Becomes Corrupted When Run 2 Times

Running Ghidra 10.2.3 Windows with latest version of ghidra emotion engine reloaded if the STABS analysis is run twice then every types in the project become corrupted and a new project needs to be recreated if it save.

This is fixed by #18.


Increase leniency to reduce test flakiness

Increasing the leniency of the test from 5 seconds to 20 seconds seems to reduce the flakiness of the test, having it pass much more consistently.

Though it is a short-term solution, I think it sweeps the actual problem (the time being off by too much) under the rug. But if this means we'll get more "reliable" tests then sure, let's increase it a bit.

Playing around with this more, an alternative would be to just remove the github.com provider here as it's the one that's consistently messing up. Given that there's two other HttpProviders tested against, this probably isn't a problem?
The VMs themselves report a system drift of maybe +/-0.0005 sec so re-syncing them will not do anything to fix the failing test.

I'm fine with either (or both) options. If left up to me I think I'd choose removing the github provider.

Great spot, thanks for the research!


Parallax is ignoring heightMapChannel value.

Parallax in chunk shader, is not respecting channel .$CH.
https://github.com/playcanvas/engine/blob/master/src/graphics/programlib/chunks/parallax.frag#L7

Fixed in https://github.com/playcanvas/engine/pull/309


tests/reference /validate_latin1 implemented incorrectly

validate_latin1.cpp
...
     const unsigned char word = static_cast<unsigned char>(*curr);

      if (word > 0xFF) {
        return false;
      }
...

is always true

It is dead code. Let us remove it.

btw is there a plan for adding support to validate_latin1?

btw is there a plan for adding support to validate_latin1?

It is not logically possible. Any sequence of bytes is valid latin1.

Can you describe your use case?

Can you describe your use case?

e.g. given an utf8 sequence

1byte utf8 -> true
2bytes utf8 -> check if its unicode value is <= 0xFF by parsing ((a & 0b00011111) << 6 | (b & 0b00111111))
3/4bytes utf8 -> false

ig it more like validate_latin1_from_utf8 for this case? I don't know much about other encoding

I understand the functionality, but what is your application?
We try to focus on providing functionality that is useful in practice. So I want to understand the motivation.

For me it mostly because I need to transfer any utf8 sequences stored in char* to Python Unicode object which requires to provide max unit value(can be 0x7f for ascii, 0xff for latin1, 0xffff or 0x10ffff). Plus it can be used for the checking in the latin1_length_from_utf8?

For me it mostly because I need to transfer any utf8 sequences stored in char* to Python Unicode object in C which required to provide max unit value

Can you point at the API you are trying to support?
Is that part of the standard Python API?

Can you point at the API you are trying to support?
Is that part of the standard Python API?

It is PyUnicode_New. I don't want to use PyUnicode_FromString since it required an additional buffer which may be costly when the len is large. So I'll will use PyUnicode_New to create the buffer and write into it directly, which required me to determine the type of PyUnicode as I said.

@Nambers Can you give me a full code routine? How would you use afterward efficiently?
I understand here that the idea is that we could take UTF-8 strings in C or C++ and move them to Python at high speed. If simdutf can provide functionality to help with that, we will, for sure, add it.
But I'd like to make sure that it is worth our time to do it.
cc @TkTech

I understand here that the idea is that we could take UTF-8 strings in C or C++ and move them to Python at high speed. If simdutf can provide functionality to help with that, we will, for sure, add it.

Sounds great. So basically I need a function using SIMD to get the max char value or just detect if it is Latin1 (<= 0xFF) or 3bytes utf8 (<= 0xFFFF).
Here is my implementation so far str.c#L11 (I also need to consider unicode escape in it, but ig it is not sth simdutf need to consider).
Then after determined the kind, we just do some fast paths like following content in my file.
ref:
cjson, ujson, and python standard json implementations didn't use simd.
orjson also didn't use SIMD, they use some rust func create.rs#L15
I can't say what method is used by pysimdjson

Ok. So this makes sense. We will add this functionality.


Getting INVALID_SCOPE error

I am getting INVALID_SCOPE issue on production from some days before, Already my system is working and also updated with new SDK. But its start showing this error without doing any changes code and developer console.
Library version:
Repro steps, stacktrace, screenshots:
Expected Behavior:

Have you ever found a solution to this problem?


silx.gui: Fixed support of PySide6.4 enums

This PR solves issue #3730 for QFileDialog.
I also checked similar cases for all QDialog and inherited classes.
closes #3730 even if there is probably other enum issues but the one reported should be fixed.

BTW, I'm using qt.QFileDialog.DontUseNativeDialog rather than qt.QFileDialog.Option.DontUseNativeDialog to keep supporting PyQt5 < 5.11


Prepare 1.4.0-M2

should be merged after https://github.com/julien-truffaut/Monocle/pull/468

released


Auto-check for updates

Basically, if the user has opted-in to internet connectivity in Settings, at launch auto-check:
https://wasatchphotonics.com/binaries/apps/enlighten/sw_versions.json
...to see if there's a newer version.  If so, prompt to download:
ENLIGHTEN 4.0.11 (beta) has been posted.
You are using 3.2.36 (latest stable). Would you like to update?
(Cancel) (Ignore this version) (Download)
[  ] ignore betas
[  ] disable version checking

For the record, I'm not sold on the current format of the JSON file...I was actually picturing something more like this:
{
  "Applications": {
    "ENLIGHTEN": {
      "Stable": [ "3.2.36", "https://wasatchphotonics.com/binaries/apps/enlighten/Enlighten-Setup64-3.2.36.exe" ],
      "Dev": [ "4.0.11", "https://wasatchphotonics.com/binaries/apps/enlighten/beta/Enlighten-Setup64-4.0.11.exe" ],
    }
  }
}

In terms of persistence, we'd just be saving the list of versions they said not to bug about again, so they'd still get notified of even-newer versions unless they ticked "disable version checking".

Note we have a checkbox they have to tick to allow any internet access at all.

Note we have a checkbox they have to tick to allow any internet access at all.

That is good. I was going to include a note about "avoiding implicit network communication for non-internet application" but I figured it was outside the scope of this topic. I'm glad it was well handled in advance.

Looks like this was stubbed but never implemented:
https://github.com/WasatchPhotonics/ENLIGHTEN/blob/main/enlighten/network/UpdateChecker.py


ci: remove success notification

修改通知配置，防止开启daliy build之后各种build success邮件

Coverage remained the same at 80.906% when pulling 0917fa098257084d7df6c28a9a400e53c2c10c63 on xtx1130:add-travis-configure into f632629d2ea9a3908783f7e7143b34a0b8b05c2d on lavas-project:feature-entry.


Header styles not circulating in IE

Tested in Win7/IE10 VM. Header cells should have padding but don't. May be an issue with fixtable-core rather than the Angular wrapper.

This appears to be an issue with getComputedStyle() itself so I'm closing this issue in favor of a new one in the fixtable-core issue tracker.


[FEATURE] How to defines a kwk types using options as a member

Turns out the all-auto, settings based interface for building view and table is rad for building them in the wild but not so much for declaring member without ugly delctype
We need a way to provide alias that helps building those types.

Fixed in #50 by make_table/make_view and pseudo settings support.


update authentication not working

Logging in to the app with new credential authenticates with the old credential.
The credentials are picked from the textFields. Login for the first time works fine. After logout, if I try to login with another account, Alamofire authenticates with the previous credentials.
Say, initially when I login, I authenticate the request with some USERNAME and PASSWORD. Say USERNAME is JOHN and PASSWORD is 1234.
I logout immediately and I login with some other credential, say USERNAME is PETER and PASSWORD is 4321. App logs in again with the old credential JOHN and 1234 only. The new credential is not at all applied
func login(userName: String!, password:String!, completion: (error: NSError?) -> Void) {
        print(userName)  // Prints PETER for second attempt
        Alamofire.request(
            .GET,
            Management.LOGIN_URL)
            .authenticate(user: userName , password: password)
            .responseJSON { response in
                // But gives JOHN's data for second attempt
                switch response.result {
                case .Success(let JSON):
                    print(JSON)
                    self.setCookies(response)
                    self.setUserData(JSON as! NSDictionary)
                    completion(error: error)
                    }

                case .Failure(let error):
                    completion(error: error)
                }
        }
    }

func logout() {
        Alamofire.Manager.sharedInstance.session.resetWithCompletionHandler { () -> Void in
            print("Resetted")
        }
    }

private func setCookies(response: Alamofire.Response<AnyObject, NSError>) {
        if let
            headerFields = response.response?.allHeaderFields as? [String: String],
            URL = response.request?.URL
        {
            let cookies = NSHTTPCookie.cookiesWithResponseHeaderFields(headerFields, forURL: URL)
            Alamofire.Manager.sharedInstance.session.configuration.HTTPCookieStorage?.setCookies(cookies, forURL: response.response!.URL!, mainDocumentURL: nil)
        }
    }

Hi @kakilan,
I'm a bit surprised that doesn't work. What I would try instead is to set the NSURLCredentialPersistence in the authenticate method to .None. That's the only other thing I can think to do here while keeping your same approach.
.authenticate(user: userName , password: password, persistence: .None)

If that still doesn't work, you have a few other options.

Create a new Manager each time you logout
Use an ephemeral session to avoid the problem altogether
Use a base64 encoded basic Authorization header that wouldn't get cached

One of these approaches should resolve your issue.
Cheers. 🍻


Promise.settle -> can it return an array of the promises instead?

Instead of PromiseInspection results?
I think a really useful method would be Promise.allSettled, similar to Q.allSettled - where you wait for all of the promises to be fulfilled, and return a promise which is fulfilled if all of the promises had been resolved, and rejected if at least one had been rejected.
In other words:
Promise.allSettled([promises]).then(function(){ ... }).catch(function(){...})

Would be equivalent to:
Promise.settle([promises]).all().then(function(){ ... }).catch(function(){...})

if Promise.settle returned an array of promises or if Promise.all could receive an array of PromiseInspection results and work on it.
May I submit a PR to be considered?

@EtaiG , a version of it: spex.batch


Update the librairies version (especially the datatables)

Issue type:
Feature request
Environment:

AdminLTE Version:  2.4.3
Operating System:  Debian 9
Browser (Version):  Chrome Canary

Description:
Is it possible to update the minimal requirements of all the librairies used in adminLTE (for example datatables is now in the 1.10.19 version).

Updated all plugins.
Thanks!


PDF: monospace font too large

document.pdf
document.presentation.xml.zip

The Monospace font size looks too large. Can we reduce it similar to what we did for OGC? Thanks.

Similarly this also occurs in HTML.

Done (document.presentation.pdf:

/document.presentation.pdf)

Thanks @Intelligent2013 . In the PDF, can we also enlarge the text font sizes (normal, monospace, etc)? They are too small compared with normal content text.

@ronaldtse can this be closed?

Let me double check.

@opoudjis the HTML font size isn't fixed yet for "inline monospace".

Introduced inline formatting default for monospace size in isodoc/base_style_reset.css

Confirmed fix. Thanks.


Support  as navigateBack

C-t is used in vim as jumping back in tag stack. With LSP, this is
normally used for "navigating back". So adding this to vscode neovim for
the same convention.
However, as I tested, it does NOT currently work - it can send
to neovim alright. But I got "E73: tag stack empty", as if c-t were
still bound to neovim's default c-t behavior (jump back in tag stack).
I expected it to have been mapped to workbench.action.navigateBack.
Any hint?
TEST:
npm install vsce
export PATH=`realpath node_modules/.bin`:$PATH
vsce package

code --install-extension vscode-neovim-0.0.83.vsix

you just mapped xnoremap, which is visual mode, there is actually two lines that you must map
not sure what the vim function you made does, but its probably not necessary
it would be great if you could just do this in your PR: https://github.com/kflu/vscode-neovim/blob/55d64509ac962623e218053ce281c85febf27bb9/vim/vscode-jumplist.vim#L1
Thanks!


Add Sepolia

This PR primarily adds sepolia to the example config (since this is where all the ETH devs are testing). Additionally, we ran cargo fmt and commented out an unused field in the Config struct. I recommend adding cargo fmt --check to the github CI file (but not part of this this PR).
We also include a requirements.txt file to the python scripts. Would be good to update the instructions here to include venv & install instructions. It would also be easier for devs if INFURA wasn't essentially recommended as the node url for all the testnets -- since there are many public nodes that don't require an INFURA_KEY

hi @bh2smith apologies for the late response. I wasn't notified by github. That should be changed now.
I recently merged in a change that adds support for sepolia testnet.  I can add a requirements.txt to the integration tests. What public node do you recommend that don't require an INFURA_KEY? I'm not very familiar with the EVM ecosystem.

Dang. I was trying to sync my fork and this was automatically closed...


Peer to peer code review

I can't find any major issues or anything that needs to be fixed. Great work!! Keep up the good work.

It could be better to add a transimtion when hovering over the social media icons.


Cannot run the code

After downloading and installing everything, I ran "npm install" and "npm start" but this happened

您好，您的邮件我已经收到，我会尽快回复！  谢谢！

npm run start

Hi,
I have the same problem and  npm run start doesn't change anything.
Many thanks for help!


Update CR descriptions

Description
Changes proposed in this pull request:

Updates to the CR descriptions

Related issue(s)

https://github.com/kyma-project/kyma/issues/16042

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


🐞Terminal() does not work with custom CA certificates

What is the issue?
When calling Terminal() on a dagger engine with custom certs mounted in /usr/local/share/ca-certificates it either exits or times out. I have tested with a normal dagger runner and a custom runner without the mounted certificates and there are no issues. I believe it also affects the -i command because nothing happens when running that command with custom certs.
Dagger version
v0.12.0
Steps to reproduce
Follow these instructions to setup a runner with a custom CA: https://docs.dagger.io/manuals/administrator/custom-runner/#custom-ca-certs. Using the sleep to see if I can trigger the timeout.
Have been using this function to test:
// Returns a container that echoes whatever string argument is provided
func (m *TestDagger) ContainerEcho(java string) *dagger.Container {
	return dag.Container().From("ubuntu:latest").
		WithExec([]string{"apt-get", "update", "-y"}).
		WithExec([]string{"sleep", "120"}).
		WithExec([]string{"apt-get", "install", "-y", "maven", "git", fmt.Sprintf("openjdk-%s-jdk", java)}).
		Terminal()
}

Log output
This is the log output most of the time. Terminal just exits
dagger call container-echo --java 17
● Attaching terminal:
container: Container!
Container.from(address: "ubuntu:latest"): Container!
Container.withExec(args: ["apt-get", "update", "-y"]): Container!
Container.withExec(args: ["sleep", "120"]): Container!
Container.withExec(args: ["apt-get", "install", "-y", "maven", "git", "openjdk-17-jdk"]): Container!
exit 1
Setup tracing at https://dagger.cloud/traces/setup. To hide: export NOTHANKS=1
✔ connect 0.2s
✔ initialize 6.2s
✔ prepare 0.0s
✔ testDagger: TestDagger! 0.0s
✔ TestDagger.containerEcho(java: "17"): Container! 2m55.3s
✔ Container.sync: ContainerID! 0.0s
✔ Container.defaultArgs: [String!]! 0.0s
✔ Container.mounts: [String!]! 0.0s
✔ Container.entrypoint: [String!]! 0.0s
✔ Container.platform: Platform! 0.0s
✔ Container.user: String! 0.0s
✔ Container.workdir: String! 0.0s
_type: Container
defaultArgs:
- /bin/bash
entrypoint: []
mounts: []
platform: linux/amd64
user: ""
workdir: ""
This happens very rarely. Haven't been able to reproduce
dagger call container-echo --java 11
● Attaching terminal:
container: Container!
Container.from(address: "ubuntu:latest"): Container!
Container.withExec(args: ["apt-get", "update", "-y"]): Container!
Container.withExec(args: ["sleep", "120"]): Container!
Container.withExec(args: ["apt-get", "install", "-y", "maven", "openjdk-11-jdk"]): Container!
exit 1
Setup tracing at https://dagger.cloud/traces/setup. To hide: export SHUTUP=1
✔ connect 0.3s
✔ initialize 23.6s
✔ prepare 0.0s
✔ testDagger: TestDagger! 0.0s
✘ TestDagger.containerEcho(java: "11"): Container! 2m49.4s
! call function "ContainerEcho": process "/runtime" did not complete successfully: exit code: 2
┃ marshal: json: error calling MarshalJSON for type *dagger.Container: input: container.from.withExec.withExec.withExec.terminal resolve: terminal se
┃ ion failed: io: read/write on closed pipe
✔ Container.from(address: "ubuntu:latest"): Container! 0.7s
✔ Container.withExec(args: ["apt-get", "update", "-y"]): Container! 3.5s
✔ Container.withExec(args: ["sleep", "120"]): Container! 2m4.3s
✔ Container.withExec(args: ["apt-get", "install", "-y", "maven", "openjdk-11-jdk"]): Container! 2m44.0s
✘ Container.terminal: Container! 2m47.0s
! terminal session failed: io: read/write on closed pipe
✔ start sh 2m47.0s
Error: invalid selection for command "container-echo": response from query: input: testDagger.containerEcho resolve: call function "ContainerEcho": process "/runtime" did not complete successfully: exit code: 2
Stdout:
marshal: json: error calling MarshalJSON for type *dagger.Container: input: container.from.withExec.withExec.withExec.terminal resolve: terminal session failed: io: read/write on closed pipe
Run 'dagger call container-echo --help' for usage.

Thanks for reporting!
Just off the top of my head I can probably imagine what's going on here. Custom CAs have to wrap container execution in extra execs to setup/teardown CAs, which is mostly likely confusing the terminal code (it probably hits the setup exec first and then exits right away, skipping the actual container the terminal should be opened in).
Will fix for v0.12.1 and add integ tests for this combo of custom CA + terminal.


Built-in physics replication

This seems like an ideal thing to have.  Much easier to prototype when physics work OOTB.
Not terribly worried about latency.  So long as it looks good and doesn't eat too much bandwidth.

Added physics prefabs plus an example.  Its not terribly efficient, but it gets the job done for now.


Impersonate Tor Browser

(This result is by someone sent me in PM)

TOR browser
Cipher Suites (11 suites)
    Cipher Suite: TLS_AES_128_GCM_SHA256 (0x1301)
    Cipher Suite: TLS_CHACHA20_POLY1305_SHA256 (0x1303)
    Cipher Suite: TLS_AES_256_GCM_SHA384 (0x1302)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)
    Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca9)
    Cipher Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca8)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)
    Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)
    Cipher Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c)
    Cipher Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d)

Second legacy firefox 115esr tor based on it
Cipher Suites (17 suites)
    Cipher Suite: TLS_AES_128_GCM_SHA256 (0x1301)
    Cipher Suite: TLS_CHACHA20_POLY1305_SHA256 (0x1303)
    Cipher Suite: TLS_AES_256_GCM_SHA384 (0x1302)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)
    Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca9)
    Cipher Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca8)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)
    Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a)
    Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009)
    Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)
    Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)
    Cipher Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c)
    Cipher Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d)
    Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
    Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)

I noticed that ja3 on the Tor browser on PC and on the Tor browser on Android is the same

This can be added once we have implemented all the customization-related issues.


[Question] After a couple of hours, I get 401 errors and no more data

I have been testing the plugin for a while now. I noticed that after every few hours, the add-on stops working and is no longer able to receive data. I see this is my HA logs:

Logger: custom_components.openmediavault.omv_api
Source: custom_components/openmediavault/omv_api.py:301
Integration: OpenMediaVault (documentation, issues)
First occurred: 16 april 2022 22:11:23 (13 occurrences)
Last logged: 00:22:26
OpenMediaVault <IP_ADDRESS> unable to fetch data (401)

I am wondering if I have to do some special setting in OMV or HA. At a restart of HA it works for a couple of hours and then it suddenly stops.

I'm afraid I cant help you much here. 401 means OMV is refusing connection with authorization error, this is not a normal behavior.
maybe you can try to remove .omv_cookies file and reauthorize the integration, but that should not be the issue.

Hmmm ok. My NAS is still running and the account is also still accessible. It's not blocked or anything. Really don't understand what the issue.
However, as soon as it happens, the script also stops working. Was hoping it could run again after it failed, but it doesn't do that.

Deleted the file. Rebooted HA assistant. It worked then for 30 minutes and then stopped working again. Sometimes it works for hours before it stops. No idea what is going on.

your best bet may be omv logs. not sure if access issues are logged tho

Im also getting the OpenMediaVault <IP_ADDRESS> unable to fetch data (401) error. OMV still working fine and can still access. FWIW, I only started getting this error after last HA update,
As with OP its intermittent.

Did you deleted the file?

@tomaae Nope. I tried it, but did not help. I set up an extra OMV setup. Simple install with harddisk attached. Added it to HA as a second installation to monitor.
The plugin fetched the data nicely for over 36 hours and then suddenly died... NAS is still running and accessible. No clue why is suddenly stopped. Same error too as with my main OMV installation.

you should check OMV logs to find anything relevant. I dont think we can find something from HA side, as that is OMV returning the error.
also, which OMV version is that?

Can't find anything strange in the logs. No errors or what so ever.
Both my OMV installations run on: 6.0.22-1 (Shaitan)

Can't find anything strange in the logs. No errors or what so ever.
Both my OMV installations run on: 6.0.22-1 (Shaitan)
[EDIT] Strange this is, that when I restart HA and the plugin loads, that it works for a while again. So, to be honest, I don't think it has anything to do with the NAS, as I do not need to restart the NAS to make it work again.

i have the same issue as you but with OMV5. Same thing, works for a while and the drops, sometimes comes back up after an hour or so or it does not. i started getting the error after last update from integration. i will roll back and post results.

Same problem, only load data of the plugin first minutes after rebooting the docker.
OMV 6.0.27-1 (Shaitan)
Portainer 2.13.1
Home Assistant Core 2022.5.5
All the log errors like this:
error log.txt

Still having the same issue too.
It started since OMV 6. On OMV 5 I did. It have this problem.
The moment it stops working is also completely random. Sometimes it works for a day. Other moments it stops after a hour or few hours. 🤷♂

Just for a different angle of view, my instance does work fine, latest HA and up to date OMV 6. Never seen this problem in the past too.
So the issue affect a lot op people, but not everyone.
I'm open for questions, if someone needs to compare his settings with mine ;-)

Do you use a separate account or your admin account?
Do you have any extra settings set, so that you perhaps can handle more requests?

Using admin account, no additional settings made.

First difference spotted, i run OMV on a intel i5  machine, as also my HA is an intel Celeron machine. No rPi's involved here.

First difference spotted, i run OMV on a intel i5 machine, as also my HA is an intel Celeron machine. No rPi's involved here.

I run OMV and HA on the same machine (intel i3)

it is a difficult one, since I'm not able reproduce it.
I could try to create some crazy debug version if someone is willing to work closely with me on this. But be warned, it may be a lot of manual file replacing and testing.

If I can access the files somewhere, I could give it a try. Not sure where everything is stored.

Happening here too. I think it happens because of the session timeout in OMV. I have it set to 60 minutes and the error happens every hour on the dot, and I have the following messages in the server log:
Jun 03 01:16:53 nas openmediavault-webgui[2508012]: Authorized login from <IP_ADDRESS> [username=admin, user-agent=python-requests/2.27.1]
So I think the session expires when the query happens, then it reconnects fine in the next query. Should be an easy fix to try to reconnect on 401, if that doesn't work, then rethrow the error.

Happening here too. Though for me, the plugin works mostly fine apart from intermittent errors. I think it happens because of the session timeout in OMV. I have it set to 60 minutes and the error happens every hour on the dot, and I have the following messages in the server log:
Jun 03 01:16:53 nas openmediavault-webgui[2508012]: Authorized login from <IP_ADDRESS> [username=admin, user-agent=python-requests/2.27.1]
So the session expires when the query happens, then it reconnects fine in the next query. Should be an easy fix to try to reconnect on 401, if that doesn't work, then rethrow the error.
I've disabled the session timeout for now, to see if it still happens.

Where do you disable the session timeout?

Where do you disable the session timeout?

System -> Workbench -> "Auto logout"

Where do you disable the session timeout?

System -> Workbench -> "Auto logout"
No 401 errors since I've disabled it.

Thanks. I disabled it just now. See how that will go. :-)

Happening here too. Though for me, the plugin works mostly fine apart from intermittent errors. I think it happens because of the session timeout in OMV. I have it set to 60 minutes and the error happens every hour on the dot, and I have the following messages in the server log:
Jun 03 01:16:53 nas openmediavault-webgui[2508012]: Authorized login from <IP_ADDRESS> [username=admin, user-agent=python-requests/2.27.1]
So the session expires when the query happens, then it reconnects fine in the next query. Should be an easy fix to try to reconnect on 401, if that doesn't work, then rethrow the error.
I've disabled the session timeout for now, to see if it still happens.

Thanks a lot for this solution... It is perfect now... I disabled the session timeout and all work fine :-)

I'm afraid I cant help you much here. 401 means OMV is refusing connection with authorization error, [...].

Yes You were right

Happening here too. Though for me, the plugin works mostly fine apart from intermittent errors. I think it happens because of the session timeout in OMV. I have it set to 60 minutes and the error happens every hour on the dot, and I have the following messages in the server log:
Jun 03 01:16:53 nas openmediavault-webgui[2508012]: Authorized login from <IP_ADDRESS> [username=admin, user-agent=python-requests/2.27.1]
So the session expires when the query happens, then it reconnects fine in the next query. Should be an easy fix to try to reconnect on 401, if that doesn't work, then rethrow the error.
I've disabled the session timeout for now, to see if it still happens.

So far so good. Timeout seemed to been have te problem. It’s still stable for now.

thats interesting, may be worth reporting to omv developers.
sessions should not time out since it is accessed every minute. since it affects only some people, its most likely a bug and not some intentional change.

Still up and running here. Since the timeout is off, it’s running fine. No issue here anymore. 🤞

thats interesting, may be worth reporting to omv developers.
sessions should not time out since it is accessed every minute. since it affects only some people, its most likely a bug and not some intentional change.

It looks like OMV uses updatelastacces to reset the timeout on each API call, which is set to False in omv_api.py:249. (It should be enabled by default if you omit the option)

thats interesting, may be worth reporting to omv developers.
sessions should not time out since it is accessed every minute. since it affects only some people, its most likely a bug and not some intentional change.

It looks like OMV uses updatelastacces to reset the timeout on each API call, which is set to False in omv_api.py:249. (It should be enabled by default if you omit the option)
Edit: Omitting the option seems to work. There's still an initial 401 if I set the timeout to 1 minute (probably connects on startup, then only makes the first query after the timeout when home assistant is finished starting up?) so I think the reconnect on 401 is still needed to fully fix it.

Changed in master, can you test it?
Would be weird imo, but worth a try.
It should reconnect, I will have to test reconnection.

Yeah, the change in master works too.
Seems like the #Api error path is not reached because it's handled as a socket error.
This is what's returned for a 401:
{'response': None, 'error': {'code': 0, 'message': 'Session expired.', 'trace': 'OMV\\HttpErrorException: Session expired. in /usr/share/php/openmediavault/session.inc:157\nStack trace:\n#0 /usr/share/php/openmediavault/rpc/proxy/json.inc(68): OMV\\Session->validateTimeout()\n#1 /var/www/openmediavault/rpc.php(45): OMV\\Rpc\\Proxy\\Json->handle()\n#2 {main}'}}
So we need to check for session expiry in the socket error path too.


Vulnerability issue

We are getting vulnerability error while running checkmarx tool and it says untrusted data binding directly to the object. Please go through the attachment.

@karventhan-a1 Please add a reasonable description of your issue, other close. Thank you.

@karventhan-a1 Please add a reasonable description of your issue, otherwise close. Thank you.

I hope this is reasonable description only. If you are not getting, please let me know. You can go through the attachment also for more information

Please add a PoC how this issue is supposed to affect Mocha. Thank you.

There is no poc item with us for now. But if we read encodeURIComponenet(window.location.search) instead of reading window.location.search this will be more security though someone appending some url in the query string.
There is no issue with Mocha but when implement Mocha, our vulnerability tool is catching this and throwing error. Please let me know this change is possible or not. If you say this is not a relevant fix then we will make it as a known issue and proceed further.

I don't think it is a vulnerability. And encodeURIComponenet(window.location.search)  is not secure mocha.
In makeUrl, we just save the current query string temporarily and set it back again to URL. We don't use it in HTML page or eval it.


Do not attempt clear for redis cache when no keys present

Previously, if there exists no keys in a specified namespace attempts to clear
the a redis backed cache would raise a TypeError. This change ensures that
a delete is not attempted in this scenario.

Hey @abn thanks for the contribution! would you mind adding tests for this change?

@argaen sure thing; I am guessing the travis failure is unrelated?

Yeah, I have to fix the pipeline, will do when I have time :)

Closing in favor of https://github.com/argaen/aiocache/pull/478


feat(windows): Make Egress test pass on Windows

This PR modifies the e2e_egress_test to be able to run on Windows nodes
Verified locally in an AKS cluster:
   Ran 1 of 42 Specs in 471.548 seconds
   SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 41 Skipped
   --- PASS: TestSuite (471.56s)

Signed-off-by: Sotiris Nanopoulos<EMAIL_ADDRESS>
Description:

Testing done:

Affected area:

Functional Area

New Functionality
[ ]

CI System
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Demo
[ ]

Documentation
[ ]

Egress
[ ]

Ingress
[ ]

Install
[ ]

Networking
[ ]

Observability
[ ]

Performance
[ ]

SMI Policy
[ ]

Security
[ ]

Sidecar Injection
[ ]

Tests
[x]

Upgrade
[ ]

Other
[ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project?

Did you notify the maintainers and provide attribution?

Is this a breaking change?

Codecov Report

Merging #4022 (4af84fb) into main (eea4672) will increase coverage by 0.57%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #4022      +/-   ##
==========================================
+ Coverage   67.28%   67.85%   +0.57%
==========================================
  Files         205      205
  Lines       11559    11569      +10
==========================================
+ Hits         7777     7850      +73
+ Misses       3731     3668      -63
  Partials       51       51

Flag
Coverage Δ

unittests
67.85% <100.00%> (+0.57%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/envoy/bootstrap/config.go
93.91% <100.00%> (-0.05%)
:arrow_down:

pkg/providers/kube/client.go
64.19% <0.00%> (-0.62%)
:arrow_down:

pkg/catalog/ingress.go
91.81% <0.00%> (+0.21%)
:arrow_up:

pkg/validator/validators.go
92.45% <0.00%> (+0.78%)
:arrow_up:

pkg/certificate/providers/config.go
79.89% <0.00%> (+32.98%)
:arrow_up:

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 eea4672...4af84fb. Read the comment docs.


Ranking rules should not do any work when only one bucket candidate exists

As explained in the Meilisearch documentation and in this issue, the role of a ranking rule is to sort search results by their relevancy. Each ranking rule narrows down a list of documents until just a few equally relevant documents remain.
It is quite common for a ranking rule to narrow down a list of documents into just one document. If that happens, there is no need to give this document to any other ranking rule, since there is nothing left to sort. However, this easy optimisation is not yet implemented.

Fixed by https://github.com/meilisearch/meilisearch/pull/3542


Permission denied (publickey)

Hi, I just executed the command:
git clone git@github.com:robinparisi/tingle.git
And the error I receive is:
<EMAIL_ADDRESS>Permission denied (publickey).

Hi,
It's not an issue related to this repo but feel free to check this link : https://help.github.com/articles/error-permission-denied-publickey


Added initial basic language server implementation

Draft of a language server for vacuum for getting real time diagnostics.
Its super minimal, and currently only shows diagnostics using the basic ruleset.
https://github.com/daveshanley/vacuum/assets/38726107/b52e79f6-913c-46b8-86df-bc628589a087
I do have a few issues with this pr:

Some dependencees were added, not sute how you feel about that
without a config file, it will be very tedious to have custom rules/rulesets for the language server, you would have to reconfigure your language server client every time you enter a new project with a different configuration.

I saw there were plans for a config file, i would be glad to help out where i can.

Oh wow, this is great! What great potential. I will review ASAP.

Ill add some docs and clean the code.
Regarding integration, i would like to add this as an "official" neovim language server which can be downloaded using a ls manager.
Ill look into vscode and intellij as well.
I don't see a point in merging this (unless you want to)
At least not until the config file.
I would be happy to work on it and merge this one after,unless you have some specific plans in mind.

Sorry about the delay in my response, I was away for the weekend.
OK so a config feature sounds right here to make this work correctly. We already use https://github.com/spf13/viper in the project, so it makes sense to use that for pulling out the configuration variables.
Here would be my requirements for the feature:

Should support any type of markup file (this is where viper steps in)
Should have a default lookup of ./vacuum.config.* and ~/vacuum.config.*
Should allow setting of all root flags (https://github.com/daveshanley/vacuum/blob/main/cmd/root.go#L51)
Should allow setting of individual command flags (for example: https://github.com/daveshanley/vacuum/blob/main/cmd/lint.go#L198)
Command flags should be kept in top-level sections of the config (for example)

lint:
  details: true
  category: schemas
  ...

Can you elaborate on the  ~/vacuum.config.* directory.
Why should vacuum have a personal configuration and not only a per project configuration?
Im not aware of any linters that support this.
Off the top of my head Detekt is a linter i use for kotlin which also doesnt do this.

Also, you said the project already uses Viper, im assuming you meant cobra, and that viper is a good fit with cobra.
Because i didnt see any usage of viper (besides you TODO comments for the config file)

Also, you said the project already uses Viper, im assuming you meant cobra, and that viper is a good fit with cobra. Because i didnt see any usage of viper (besides your TODO comments for the config file)
Anyway, i started working on it, ill have a pr ready by tomorrow, maybe even today

Yes, I meant to say that we have cobra in the library, which depends on viper, so there is no new dependency to add.
Looking forward to the PR, this will be a great new set of features.

Can you elaborate on the  ~/vacuum.config.* directory. Why should vacuum have a personal configuration and not only a per project configuration?
Im not aware of any linters that support this. Off the top of my head Detekt is a linter i use for kotlin which also doesnt do this.

It's a personal preference, I always like a tool that considers 'me' and not 'where I am'. So I like a default behavior always applied to a tool. However, it should always be over-ridden by a config that is in the working directory - it's like a soft fallback config.

If you do insist on going this route.
Do we want this to comply to basedir spec?

Can you elaborate on the  ~/vacuum.config.* directory. Why should vacuum have a personal configuration and not only a per project configuration?
Im not aware of any linters that support this. Off the top of my head Detekt is a linter i use for kotlin which also doesnt do this.

It's a personal preference, I always like a tool that considers 'me' and not 'where I am'. So I like a default behavior always applied to a tool. However, it should always be over-ridden by a config that is in the working directory - it's like a soft fallback config.

If you do insist on going this route. Do we want this to comply to basedir spec?

Yes, this is a good idea.

oh no! what happened to this?

oh no! what happened to this?

Dont worry i simply made a mess of my forked so i moved some branches around,
Ill create a new one once config file is merged

@KDanisme
The configuration feature was merged into vacuum. Is there a possibility to get this re-submitted? I'd like to expose this functionality, I'd rather you be the contributor rather than just lift the code you've already written.

@daveshanley Hi yes,
Sorry i was busy with work.
I was simply putting this off because i wanted to add some comments and docs.
Regarding our previous talk.
I was in the middle of creating a vscode plugin for this language server, including adding a PR to neovim language server plugins.
Do you want the vscode plugin to be in this repo as well?

Yes, I would like to keep it all together, and add a build to publish it accordingly.

Then i will add the vscode and intellij extensions in different PRs

Nice! This will be very exciting to see.


Add option to disable --release?

It would be nice to be able to easily build in debug mode while developing the lambda. Opt-in of course.

This is a great idea. The default is optimized for speed and compact size. I think debug should be an option too. I'll look into this


sbomasm version displays the default short description

sbomasm version
  ____    ____     ___    __  __      _      ____    __  __
 / ___|  | __ )   / _ \  |  \/  |    / \    / ___|  |  \/  |
 \___ \  |  _ \  | | | | | |\/| |   / _ \   \___ \  | |\/| |
  ___) | | |_) | | |_| | | |  | |  / ___ \   ___) | | |  | |
 |____/  |____/   \___/  |_|  |_| /_/   \_\ |____/  |_|  |_|
sbomasm: A brief description of your application

@surendrapathak this issue is also fixed with #8


Add configurable API version, default to '2017-02-14'

Adds configurable Stripe API version, via DJSTRIPE_API_VERSION and defaults it to 2017-02-14, which is the latest version we're compatible before we get (potentially) broke by the Transfer/Payout split introduced by 2017-04-06.  This is what we're currently using in production.
The main reason for this is that (currently) the default version specified by dj-stripe is 2016-03-07, which was causing issues for us when synchronising customers.  A change introduced in 589204d0bc27778121967b1215b4f0c6f25e64df which uses status='all' for Subscription.api_list was causing the following errors for us:
[2017-04-24 23:27:46,572: INFO/PoolWorker-1] message='Stripe API response' path=https://api.stripe.com/v1/subscriptions?status=all&customer=cus_redacted response_code=400
[2017-04-24 23:27:46,572: INFO/PoolWorker-1] error_code=None error_message=u'Invalid status: must be one of trialing, active, past_due, or unpaid' error_param=status error_type=invalid_request_error message='Stripe API error received'
[2017-04-24 23:27:46,572: WARNING/PoolWorker-1] ERROR: Request req_redacted: Invalid status: must be one of trialing, active, past_due, or unpaid

This is primarily because the status=all support wasn't added until API version 2016-07-06, so we started monkey patching it.  I hate monkey patching, so here's the pull request to officially add it to dj-stripe, with a stark warning in the docs. ;-)
Tests all run successfully.

Interestingly I realise this partially undoes some of the work from #116 by re-enabling STRIPE_API_VERSION support, but I think with the additional checks here (particularly documentation and a warning system check) this should be a bit safer.  If a user decides to diverge they'll get an explicit "you really shouldn't do that" warning, which they can obviously silence if they feel comfortable with it.

@kavdev Ready to land. ;-)


project is not deploying at all

Describe the bug
I can't get deploy anymore when creating this project
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-v3vzww
Steps to reproduce
I get errors now when I try to deploy my code. it has not worked for days
Expected behavior
I always get errors now trying to deploy a project. This project
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 129
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 86015221,
  "usedJSHeapSize": 70303165,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = sam610
Chat ID = 6c238405cb19

Additional context
Error:
An error occured while streaming this message.

Thanks for the report and patience during this beta period! Tracking all deployment related bug fixes in issue #499


[Question]: Is it possible to customize the VectorIndexAutoRetriever?

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
I have used the WeaviateVectorStore for my data indexing and vector storing. Now, while querying the index with a query such as
query="Based on the Movie Title and Movie Description, tell me what is the moral of the movie 'Home Alone'"; I get an error: ValueError: Filter operator FilterOperator.IN not supported. This is because Weaviate does not have an IN operator.
So, I was wondering if it is possible to customize the VectorIndexAutoRetriever so that I can change the IN to an AND operator?

I don't think it's possible right now. There would need to be a PR to add some function hook to post-process before querying

Maybe you can try to modify the prompt in llama_index\core\indices\vector_store\retrievers\auto_retriever\prompts.py.
This is the default prompts VectorIndexAutoRetriever using and I tried to add a new prompt example follow the pattern of the given example.  It works.


fix: Creating new experience issue

Description
Fix: Ensure Level ID is retrieved when adding points in GiveExperience trait
When the addPoints method in the GiveExperience trait is executed, it creates a new Experience. If the condition for the Level query returns null, the default level is retrieved from the config file. This update ensures that the Level ID is correctly retrieved in such cases.
Type of Change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Related Issues and Pull Requests

Issue #...
PR #...

Testing
Please provide a passing test where possible. This package uses PestPHP
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have added tests that prove my fix is effective or that my feature works
[x ] New and existing unit tests pass locally with my changes
[ ] I have made corresponding changes to the documentation [OPTIONAL]

@oktayla I think there is some failing tests on your changes. Can you check it?
Thanks

Closing due to lack of activity


Feature - Add printer settings

[x] #36
[x] #37
[x] #38
[x] #39

All todo's completed now can close this issue


Enhance User Experience with Background Images

Is your feature request related to a problem? Please describe.
While our web project offers valuable content and functionality, the current use of white backgrounds throughout the application gives it a somewhat plain and uninviting appearance. To create a more engaging and visually appealing user experience, we should consider introducing background images to certain sections of the application.
Describe the solution you'd like.
We propose adding background images to select sections of our web application to improve the aesthetics and make it more visually engaging. Background images can set the mood, convey our brand's personality, and provide a better sense of context to users.
Describe alternatives you've considered.
Benefits:
Enhanced Aesthetics: Background images can add depth and visual appeal to our project, making it more attractive to users.
Brand Identity: Carefully chosen images can help convey our brand's identity and values.
Improved User Engagement: A visually engaging interface can keep users on our site longer, potentially leading to increased engagement.

Add any other context or screenshots about the feature request here.
No response

how do you propose to do this

how do you propose to do this

i did something about this on the home page but getting the right image choice is my problem so i got variants of what i did, you can suggest other images or still reject.

@kivenalaric the second variant looks good. please proceed with that one

can you give me access to push sir, tried pushing and permission was denied.

@kivenalaric
Are you working on a new fork because in fork, there is no need for permission
Only if you are working in the main repo and in main branch will it restrict you from pushing

Let me fork again because i forked it

Gone review required @rohitagr0310


incomplete documentation and inconsistencies

Script fails saying that you must connect to Exchange online first. Nowhere in the documentation it explains how to do this. It also says that all it needs is the PowerShell modules for Azure AD, nothing about Exchange.
I do have Exchange Module and I could do the connection before running the script. But then the problem is that it is not clear whether I should connect to source or the target Exchange.
Documentation should be updated to explain that Exchange Modules are required. Scripts should be update to connect to the correct Exchange.
In the documentation, Fabrikan often mentioned as the source and Contoso as the target. However in the scripts Fabrikan is the target and Contoso the source.
Down the line, a script also mentions a CSV file which the documentation never mentions how to create, nor it points to a documentation explaining how to create it.

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

ID: c61c960c-f5c3-76f7-ac18-dfeaf30230e4
Version Independent ID: 3dc607b2-869e-976f-80da-d73cfb1210e5
Content: Cross-tenant mailbox migration - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/cross-tenant-mailbox-migration.md
Product: microsoft-365-enterprise
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@pmdci Thank you for your feedback.

In step-by-step-instructions-for-the-target-tenant-admin (step 3) we have discussed about connecting to Exchange online. - https://docs.microsoft.com/en-us/microsoft-365/enterprise/cross-tenant-mailbox-migration?view=o365-worldwide#step-by-step-instructions-for-the-target-tenant-admin
The scripts show fabrikam as the source and Contoso as a target.  Could you please elaborate on where you see this so that that can be fixed?
This is what I see - -ResourceTenantDomain fabrikam.onmicrosoft.com -TargetTenantDomain contoso.onmicrosoft.com
3)CSV is used for creating migration batches and details about getting the CSV file is provided in the FAQ.

Hope this helps!
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @pmdci Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

Come on lads... Do I need to do everything?
Here is its:
It says "Source tenant domain, such as fabrikam.onmicrosoft.com”.
<EMAIL_ADDRESS>Then at "The script will pause and ask you to accept or consent to the Exchange [...]" it says "SetupCrossTenantRelationshipForTargetTenant.ps1 -ResourceTenantDomain contoso.onmicrosoft.com".
<EMAIL_ADDRESS>Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Sriraman M<EMAIL_ADDRESS>Sent: Friday 5 February 2021 14:56
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/microsoft-365-docs] incomplete documentation and inconsistencies (#4026)
@pmdcihttps://github.com/pmdci Thank you for your feedback.

In step-by-step-instructions-for-the-target-tenant-admin (step 3) we have discussed about connecting to Exchange online. - https://docs.microsoft.com/en-us/microsoft-365/enterprise/cross-tenant-mailbox-migration?view=o365-worldwide#step-by-step-instructions-for-the-target-tenant-admin
The scripts show fabrikam as the source and Contoso as a target. Could you please elaborate on where you see this so that that can be fixed?
This is what I see - -ResourceTenantDomain fabrikam.onmicrosoft.com -TargetTenantDomain contoso.onmicrosoft.com
3)CSV is used for creating migration batches and details about getting the CSV file is provided in the FAQ.

Hope this helps!
Thanks
Sri
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/4026#issuecomment-774082577, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADIZM73DT6RG3LHZEVADXT3S5QBI5ANCNFSM4W3QMFNQ.

@pmdci Thank you for your feedback. I don't see the screenshots, unfortunately. But when you run the script (SetupCrossTenantRelationshipForTargetTenant.ps1) - There are some parameters and values that you need to mention (required) and one of them is -ResourceTenantDomain.
Hope this helps!
Thanks
Sri

I added the text besides the screenshot as well.Everyone in my organisation sees the inconsistency. Fix it, don't fix it. I am done giving you guys feedback. On 15 Feb 2021 18:49, Sriraman M S<EMAIL_ADDRESS>wrote:
@pmdci Thank you for your feedback. I don't see the screenshots, unfortunately. But when you run the script (SetupCrossTenantRelationshipForTargetTenant.ps1) - There are some parameters and values that you need to mention (required) and one of them is -ResourceTenantDomain.
Hope this helps!
Thanks
Sri
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.

You do understand I am NOT asking you for help and all I am doing is pointing an inconsistency on your documentation, that everyone) here at my end) sees but you? On 15 Feb 2021 18:56, Pedro Mac Dowell da Costa Innecco<EMAIL_ADDRESS>wrote:I added the text besides the screenshot as well.Everyone in my organisation sees the inconsistency. Fix it, don't fix it. I am done giving you guys feedback. On 15 Feb 2021 18:49, Sriraman M S<EMAIL_ADDRESS>wrote:
@pmdci Thank you for your feedback. I don't see the screenshots, unfortunately. But when you run the script (SetupCrossTenantRelationshipForTargetTenant.ps1) - There are some parameters and values that you need to mention (required) and one of them is -ResourceTenantDomain.
Hope this helps!
Thanks
Sri
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.

Here is the screenshot of the inconsistency in IMGUR: https://imgur.com/a/LcNgc4V
[https://i.imgur.com/ajl5F4O.png?fb]https://imgur.com/a/LcNgc4V
imgur.comhttps://imgur.com/a/LcNgc4V
Imgur: The magic of the Internet
imgur.com

From: Pedro Mac Dowell da Costa Innecco on behalf of Pedro Mac Dowell da Costa Innecco<EMAIL_ADDRESS>Sent: 13 February 2021 10:40
To: MicrosoftDocs/microsoft-365-docs<EMAIL_ADDRESS>MicrosoftDocs/microsoft-365-docs<EMAIL_ADDRESS>Cc: Mention<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/microsoft-365-docs] incomplete documentation and inconsistencies (#4026)
Come on lads... Do I need to do everything?
Here is its:
It says "Source tenant domain, such as fabrikam.onmicrosoft.com”.
<EMAIL_ADDRESS>Then at "The script will pause and ask you to accept or consent to the Exchange [...]" it says "SetupCrossTenantRelationshipForTargetTenant.ps1 -ResourceTenantDomain contoso.onmicrosoft.com".
<EMAIL_ADDRESS>Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Sriraman M<EMAIL_ADDRESS>Sent: Friday 5 February 2021 14:56
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/microsoft-365-docs] incomplete documentation and inconsistencies (#4026)
@pmdcihttps://github.com/pmdci Thank you for your feedback.

In step-by-step-instructions-for-the-target-tenant-admin (step 3) we have discussed about connecting to Exchange online. - https://docs.microsoft.com/en-us/microsoft-365/enterprise/cross-tenant-mailbox-migration?view=o365-worldwide#step-by-step-instructions-for-the-target-tenant-admin
The scripts show fabrikam as the source and Contoso as a target. Could you please elaborate on where you see this so that that can be fixed?
This is what I see - -ResourceTenantDomain fabrikam.onmicrosoft.com -TargetTenantDomain contoso.onmicrosoft.com
3)CSV is used for creating migration batches and details about getting the CSV file is provided in the FAQ.

Hope this helps!
Thanks
Sri
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/4026#issuecomment-774082577, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADIZM73DT6RG3LHZEVADXT3S5QBI5ANCNFSM4W3QMFNQ.

@pmdci Thank you for the feedback. I now found multiple instances where the target and the source are incorrect. I will update the document and let you know. Sorry again for the confusion as I was only looking at the downloaded script.
Thanks
Sri

That is because you didn't read my original post. On 17 Feb 2021 22:28, Sriraman M S<EMAIL_ADDRESS>wrote:
@pmdci Thank you for the feedback. I now found multiple instances where the target and the source are incorrect. I will update the document and let you know. Sorry again for the confusion as I was only looking at the downloaded script.
Thanks
Sri
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.

@msbemba Please let me know when you update this.

@pmdci  and @yogkumgit  Fabrikam and Contoso were interchanged in a few places. According to most parts of the document source is Contoso and Target is Fabrikam. So we have made sure that It is consistent throughout the document. I have requested the author to review the same and once he reviews and approves the  PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4204 the document will be live.
Thanks
Sri


Fix missing : in calico/node image name

Typo in calico/node image name (missing :) ... Have updated some files to use a new variable in the versions file (so that we declare once).
TODO:
Update remaining instances (but not planning to do that in this PR since that would require a full QA).

What's the reason for the new variable?


Support fetching repos with pagination

Hi, Great package by the way! Just wanted to say that I just encountered an issue with updating the cache and noticed some of my repos were missing. On closer inspection it turns out that get_org_repos does not actually use pagination:
def get_org_repos(org)
    res = get "/orgs/#{org}/repos"
    if res.is_a?(Array)
      res.map do |repo|
        { 'name' => repo['full_name'], 'url' => repo['html_url'] }
      end
    else # TODO: handle error
      []
    end
  end

I went ahead and modified it to use res = get "/orgs/#{org}/repos?per_page=100" just to see and lo and behold my repos popped in.
Don't mind submitting a PR but not entirely sure how I could achieve this in ruby?

Pagination should be working, it is handled here: https://github.com/edgarjs/alfred-github-repos/blob/master/github#L167

Ah I see, interesting, wonder why when I change it to per_page=100 that fetches my repos. Are you sure this is actually what GitHub supports today on the repos endpoint? Cant understand why this doesn't work then for me if you saying it should...

If you see line 144 it already has the per_page parameter. This was aded in a PR, honestly I've lost track of the github API recently so I'm afraid I can't assure that is how github works. But the pagination works for me :)


Update de.json

changed "couldn't connect to" with "couldn't establish a connection with" since it works better in german

Thanks!