Live query cloud code

I have a web app which uses ACLs and cloud code to make queries (as default fetching is disabled by CLPs).  However, how would I create a live query subscription using cloud code to override ACLs? Code examples would be highly appreciated!!

Hey @flovilmart any chance you can offer your opinion here? You've been really helpful! Thanks

Hi. Have you found a solution? Thanks.

Thanks for your question!
We want to make sure to keep signal strong in the GitHub issue tracker – to make sure that it remains the best place to track issues that affect the development of Parse Server.
Questions like yours deserve a purpose-built Q&A forum. Would you like to post this question to Stack Overflow with the tag #parse.com? We'll be happy to answer there. Post a link to your Stack Overflow question here, so that we don't lose track of it.
You may also use Server Fault for questions about managing your own servers.


Fix python invalid escape sequences

Sometimes, when working with python some Deprecation Warnings about invalid escape sequences show up:
rdkit\Chem\EnumerateStereoisomers.py:165: DeprecationWarning: invalid escape sequence \[
    """ returns a generator that yields possible stereoisomers for a molecule

rdkit\ML\Descriptors\MoleculeDescriptors.py:109: DeprecationWarning: invalid escape sequence \
    doc = re.sub('\ *\n\ *', ' ', doc)

Those aren't a problem (though someone mentioned that in a future python release these warnings might turn into errors), although they are sometimes an annoyance.
I thought I might get them fixed so that the warnings stop showing up. Also, along the way, I noticed my editor trimmed whitespace at the end of the lines of the files I edited.

Oh, I forgot: I'm not familiar with the InChi syntax, so I hope I didn't mess those up.


Error in recorder if logging.yml is not in current directory

I installed deepcave via pip and tried to use the recorder to convert some data. Unfortunately, I got the error that logging.yml does not exist which was only resolved when I copied the file from deepcave/utils to my current path.
The exact error is in "with (Path() / "logging.yml").open("r") as stream:" and that's what I believe is wrong: the path points to the current directory instead of utils.
Full error log:
Traceback (most recent call last):
File "/bigwork/nhwpeimt/autorl-offline-data/autorl_dataset/parse_dacbench_data.py", line 5, in <module>     from deepcave import Recorder, Objective
 File "/bigwork/nhwpeimt/miniconda3/envs/autorl_dataset/lib/python3.10/site-packages/deepcave/__init__.py", line 45, in <module>
from deepcave.runs.objective import Objective
 File "/bigwork/nhwpeimt/miniconda3/envs/autorl_dataset/lib/python3.10/site-packages/deepcave/runs/__init__.py", line 21, in <module>
from deepcave.utils.logs import get_logger
File "/bigwork/nhwpeimt/miniconda3/envs/autorl_dataset/lib/python3.10/site-packages/deepcave/utils/logs.py", line 7, in <module>
with (Path() / "logging.yml").open("r") as stream:
File "/bigwork/nhwpeimt/miniconda3/envs/autorl_dataset/lib/python3.10/pathlib.py", line 1119, in open
return self._accessor.open(self, mode, buffering, encoding, errors,
FileNotFoundError: [Errno 2] No such file or directory: 'logging.yml'

Update: I think this is not a path issue, the problem is that logging.yml is not downloaded when using pip install

Probaby cause by python 3.10 + pypi, see #96


[1.12.2] Crash on Gamestart (SoundEngine)

Crash Report: https://pastebin.com/cRJ5EGMk
Forge: <IP_ADDRESS>69
RandomTweaks: <IP_ADDRESS>

Does this issue occur without RandomTweaks?

Yes. But i got another problem, if a player on a server tries to sleep at night the server crashes:
https://pastebin.com/hpAvunj9

Yes it does. Well, guess i have to continue my search. Sorry.


BUG: optimize: newton raises exception with complex x0

Here's an example where newton crashes unexpectedly (using scipy version '1.4.0.dev0+b4bfa9d'):
In [3]: from scipy.optimize import newton

In [4]: def f(z):
   ...:     return z - 1
   ...:

In [5]: newton(f, 1+1j)
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-5-5306645b6b37> in <module>
----> 1 newton(f, 1+1j)

~/miniconda36/lib/python3.6/site-packages/scipy-1.4.0.dev0+b4bfa9d-py3.6-macosx-10.7-x86_64.egg/scipy/optimize/zeros.py in newton(func, x0, fprime, args, tol, maxiter, fprime2, x1, rtol, full_output, disp)
    323             eps = 1e-4
    324             p1 = x0 * (1 + eps)
--> 325             p1 += (eps if p1 >= 0 else -eps)
    326         q0 = func(p0, *args)
    327         funcalls += 1

TypeError: '>=' not supported between instances of 'complex' and 'int'

This example calls newton(f, x0) with no fprime so the code backs off to using the secant method.
The example call provides only a single x value, so the code tries to construct a second value p1.
p1 is a slightly scaled and shifted version of x0:  p1 = (1+eps)*x0 + <offset>
If x0 is real positive, offsetting by eps is fine. If x0 is negative, offsetting by eps would work against the scaling and could even result in p1==x0.  Hence the offsetting by -eps if p1 is negative. p1 being complex triggers the TypeError.
If I'm reading the history correctly, the code may have had this behavior since 2010 or earlier.
The optimize.root_scalar method doesn't support this use case --- the user must provide two x values in order to invoke secant.

For what it's worth: if I change the line where the error is raised to
        p1 += (eps if p1.real >= 0 else -eps)

then all the optimize tests still pass, and my example works:
In [1]: from scipy.optimize import newton

In [2]: def f(z):
   ...:     return z - 1
   ...:

In [3]: newton(f, 1+1j)
Out[3]: (1+5.0487097934133837e-29j)

In [4]: f(_)
Out[4]: 5.0487097934133837e-29j

I'm not recommending this change as the way to fix the bug, because I haven't investigated why that line is there in the first place.  It looks like a bit of a kludge put their to fix some special case. Indeed, if the line is simply removed, a couple tests fail.  But the quick fix does show that it should be easy to find a proper fix for this bug.

Actually the change you show seems reasonable to me. @charris, any thoughts on why that line is there in the first place?
I must admit that I don't particularly like the use case, finding the root of a function given one x-value by calling newton(f, x0).  [I like boost's bracket_and_solve_root approach better for that.]
And the doc for newton  is perhaps a little vague as to what happens when prime is not provided.
x1 : float, optional
Another estimate of the zero that should be somewhere near the actual zero. Used if fprime is not provided.

I think I may have written that description of x1, and it may indeed imply that x1 is needed fprime is not provided. But the code certainly has always supported not providing x1.  So we may have to support it a while longer and your modification seems safe and won't change any existing usage.

I don't recall, but it looks like it attempts to increase the magnitude of p1 by an absolute tolerance as well as a relative one. I think the possibility of complex was simply overlooked. If we had complex sign for complex x/|x|, then you could simply add that times eps, but zero might be a problem. The original goes back at least 8 years and was
        if x0 >= 0:
            p1 = x0*(1 + 1e-4) + 1e-4
        else:
            p1 = x0*(1 + 1e-4) - 1e-4

So one could do
    p1 = (eps if x0 == 0 else x0 * (1 + eps) + eps * (x0 / abs(x0)))

But without remembering why I did it in the first place, I cannot say why it is needed.

Hello folks,
Came across this today after a google search. I was having a similar problem, i.e. newton was intermittently raising a TypeError when x0 was complex.
Turns out that the exception was only raised for the built-in complex type which does not support comparisons to int. When I switched to using NumPy's complex128 it all worked fine without any exceptions.
For reference, my SciPy version is 1.5.2, NumPy is 1.19.2, and Python is 3.6.13.

I want to confirm that this works:
import numpy as np
from scipy.optimize import newton

def func(z):
    return 1 + z*z

newton(func, x0=np.complex128(1+1j), tol=1e-12)

But x0=1+1j still gives the error above (scipy 1.5.2). Great it works, but either the documentation should be changed to require x0 to be np.complex128, or x0 should be converted inside the function to np.complex128 if it is regular complex.


Changes to add export functions for Roles

Type of Change

[ ] Bug fix (non-breaking change, fixes #)
[X] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[X] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Add function to export Database and Server Roles
Approach

Adds code that wraps T-SQL scripts that fully generate the Role scripts
This command is based off of John Eisbrener's post "Fully Script out a MSSQL Database Role"
Reference:  https://dbaeyes.wordpress.com/2013/04/19/fully-script-out-a-mssql-database-role/
Used with Permission
Commands to test
Export-DbaDbRole
Export-DbaServerRole

Export of server roles I can understand, but what purpose would there be in exporting database roles?

Getting the full permissions of a role is note easy via any current process (at least that I am aware of)
This is why the script from John Eisbrener was created

thank you so much! your tests are glorious 🌞 💯
Just a few changes needed:
Was testing how far this can go back and found that it needs a try catch around the enumeration of the dbs or unprocessable dbs need to be skipped.

2005 was only slightly problematic

and 2000 needs to be skipped

I will look into the enumeration errors and also issue with SQL 2005 or earlier.
May take a day as this was done at SQLSaturday Auckland and I won't be home until tomorrow

You will also need to exclude Azure SQL from being passed in since these queries are not supported. You can just add -AzureUnsupported to your Connect-SqlInstance call to handle this one.

Changes added to exclude unsupported versions and fix problems with offline databases
Also replaced calls to Invoke-SqlQuery with .Query calls

So close! You can do -MinimumVersion on Connect-SqlInstance if you can't get it to work.

Do you have more details on where this error is being generated?
I have tried this against multiple SQL Server 2005 instances and cannot reproduce the above error.
The error looks like some issue with Collation differences . What is the collation of SQL2005 instance you are testing against?

I'd also verify what compat-level the database is in (on 80, those queries would not run).

Thanks @wsmelton
I tested on a 2005 instance and putting a Database into compat-level 70 is able to reproduce the error.
Using compat-level 80 did not cause error but I will restrict to compat-level 90 or higher

ohhh good call, i wouldnt have known

looking great thank you!


Do not allow workspace folders with scheme different than the current…

Fixes https://github.com/microsoft/vscode-remote/issues/1608
I simply put the check in the doAddFolder of the worksapceEditingService. That if in the remote context we do not allow to add new folders which bring a new scheme to the story. The newly added folder must have a scheme which is already known.
Let me know what you think and I can change that.
Maybe we should make it more explicit that when this.environmentService.configuration.remoteAuthority there is already one folder

Does the operation should fail in this case? Otherwise there will be no feedback at all.
What happens if user adds a folder by editing the file?

Got point -> I should throw some error / notification so the user gets feedback
I hoped that also goes through this api, did not check. Will do tomorrow

I have update the PR such that we show a warning when the user tries to drop a folder with a new scheme.
Here's the wording in case you have feedback on how to improve
"Workspace folders from different providers are not allowed in the same workspace."
As for the user editing the file that will be tackled with the explorer decoration provider and will not be a part of this PR.


[SPARK-15360][Spark-Submit]Should print spark-submit usage when no arguments is specified

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
In 2.0, ./bin/spark-submit doesn't print out usage, but it raises an exception.
In this PR, an exception handling is added in the Main.java when the exception is thrown. In the handling code, if there is no additional argument, it prints out usage.
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
Manually tested.
./bin/spark-submit
Usage: spark-submit [options] <app jar | python file> [app arguments]
Usage: spark-submit --kill [submission ID] --master [spark://...]
Usage: spark-submit --status [submission ID] --master [spark://...]
Usage: spark-submit run-example [options] example-class [example args]
Options:
--master MASTER_URL         spark://host:port, mesos://host:port, yarn, or local.
--deploy-mode DEPLOY_MODE   Whether to launch the driver program locally ("client") or
on one of the worker machines inside the cluster ("cluster")
(Default: client).
--class CLASS_NAME          Your application's main class (for Java / Scala apps).
--name NAME                 A name of your application.
--jars JARS                 Comma-separated list of local jars to include on the driver
and executor classpaths.
--packages                  Comma-separated list of maven coordinates of jars to include
on the driver and executor classpaths. Will search the local
maven repo, then maven central and any additional remote
repositories given by --repositories. The format for the
coordinates should be groupId:artifactId:version.

Test build #58751 has started for PR 13163 at commit ce0d2c0.

Test build #58752 has started for PR 13163 at commit 8d14bcf.

Is the fix not to just pull up the call to builder.buildCommand(env); in Main from line 86 to after line 60? then it does require rethinking a bit how the error path is handled, where it creates a builder for the 'help' command. But this would at least use the existing mechanism for handling arg parsing errors.
CC @vanzin

Test build #58751 has finished for PR 13163 at commit ce0d2c0.

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

Merged build finished. Test PASSed.

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

Test build #58752 has finished for PR 13163 at commit 8d14bcf.

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

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

Merged build finished. Test PASSed.

Sorry, this was me. But as others said, this is not the right fix. Here's a patch that does it:
diff --git a/launcher/src/main/java/org/apache/spark/launcher/SparkSubmitCommandBuilder.java b/launcher/src/main/java/org/apache/spark/launcher/SparkSubmitCommandBuilder.java
index 76897c4..a7c4179 100644
--- a/launcher/src/main/java/org/apache/spark/launcher/SparkSubmitCommandBuilder.java
+++ b/launcher/src/main/java/org/apache/spark/launcher/SparkSubmitCommandBuilder.java
@@ -107,28 +107,37 @@ class SparkSubmitCommandBuilder extends AbstractCommandBuilder {

   SparkSubmitCommandBuilder(List<String> args) {
     this.allowsMixedArguments = false;
+    this.sparkArgs = new ArrayList<>();

     boolean isExample = false;
     List<String> submitArgs = args;
-    if (args.size() > 0 && args.get(0).equals(PYSPARK_SHELL)) {
-      this.allowsMixedArguments = true;
-      appResource = PYSPARK_SHELL;
-      submitArgs = args.subList(1, args.size());
-    } else if (args.size() > 0 && args.get(0).equals(SPARKR_SHELL)) {
-      this.allowsMixedArguments = true;
-      appResource = SPARKR_SHELL;
-      submitArgs = args.subList(1, args.size());
-    } else if (args.size() > 0 && args.get(0).equals(RUN_EXAMPLE)) {
-      isExample = true;
-      submitArgs = args.subList(1, args.size());
+    if (args.size() > 0) {
+      switch (args.get(0)) {
+        case PYSPARK_SHELL:
+          this.allowsMixedArguments = true;
+          appResource = PYSPARK_SHELL;
+          submitArgs = args.subList(1, args.size());
+          break;
+
+        case SPARKR_SHELL:
+          this.allowsMixedArguments = true;
+          appResource = SPARKR_SHELL;
+          submitArgs = args.subList(1, args.size());
+          break;
+
+        case RUN_EXAMPLE:
+          isExample = true;
+          submitArgs = args.subList(1, args.size());
+      }
+
+      OptionParser parser = new OptionParser();
+      parser.parse(submitArgs);
+      this.printInfo = parser.infoRequested;
+    }  else {
+      this.printInfo = true;
     }

-    this.sparkArgs = new ArrayList<>();
     this.isExample = isExample;
-
-    OptionParser parser = new OptionParser();
-    parser.parse(submitArgs);
-    this.printInfo = parser.infoRequested;
   }

   @Override
@@ -147,7 +156,7 @@ class SparkSubmitCommandBuilder extends AbstractCommandBuilder {
     List<String> args = new ArrayList<>();
     SparkSubmitOptionParser parser = new SparkSubmitOptionParser();

-    if (!allowsMixedArguments) {
+    if (!allowsMixedArguments && !printInfo) {
       checkArgument(appResource != null, "Missing application resource.");
     }

@vanzin Thanks for your clarification. Let me learn and revise the change. '--help' is also broken.

--help seems to also work with my patch.

BTW this should be a good opportunity to add a unit test to make sure --help works, for example.

@vanzin Sure. I will do it after I fully understand the logic. Good to learn how Spark submit works. Thanks for your time!

Test build #58810 has started for PR 13163 at commit 9034dd3.

Test build #58810 has finished for PR 13163 at commit 9034dd3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Test build #58813 has started for PR 13163 at commit 9034dd3.

Test build #58813 has finished for PR 13163 at commit 9034dd3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Test build #58826 has started for PR 13163 at commit bfc4876.

@wangmiao1981 while you wait for tests to pass could you try to add a unit test to SparkSubmitCommandBuilderSuite.java?

@vanzin  Based on my understanding, the help message is print on console and the launcher should not expect help message String. So, will I expect no exception.

I'm not really sure I understand what you're saying; but it should be possible to write a unit test where you create a SparkSubmitCommandBuilder to execute --help and it doesn't throw an exception like it does before this fix. You don't need to check the output.

@vanzin  Yes, that is what I mean and I want to confirm with you. I only check no exception.

Test build #58826 has finished for PR 13163 at commit bfc4876.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

@vanzin I will check and fix the existing Unit test failure tonight.
[error] Test org.apache.spark.launcher.SparkSubmitCommandBuilderSuite.testExamplesRunner failed:
Thanks!

Test build #58832 has started for PR 13163 at commit b257891.

Test build #58832 has finished for PR 13163 at commit b257891.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #58852 has started for PR 13163 at commit e2776eb.

Test build #58852 has finished for PR 13163 at commit e2776eb.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

retest this please

Test build #58873 has started for PR 13163 at commit 9e90805.

Test build #58873 has finished for PR 13163 at commit 9e90805.

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

Merged build finished. Test PASSed.

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

Looks good, just a remaining nit.

Test build #58903 has started for PR 13163 at commit 8b632e3.

Test build #58903 has finished for PR 13163 at commit 8b632e3.

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

Merged build finished. Test PASSed.

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

Test build #58914 has started for PR 13163 at commit 79d2aa8.

Test build #58914 has finished for PR 13163 at commit 79d2aa8.

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

Merged build finished. Test PASSed.

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

Test build #58937 has started for PR 13163 at commit 2941e62.

Test build #58937 has finished for PR 13163 at commit 2941e62.

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

Merged build finished. Test PASSed.

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

LGTM, merging to master / 2.0.


The background styling was affected in the last version

When I pass a background style to the board the lane's background is affected too.
See in the storybook: Board Styling section.

My bad! Recent refactoring introduced this bug. Fixed in recent release..


Feature request: jump cursor to anchor line

hello, thanks for the great extension.
i find myself often wanting to go to a todo set as an anchor, only using the keyboard. the problem is, as i navigate to the extensions view, and press enter, or right arrow on one of the anchors, it moves the editor screen to the line, but not the cursor.
would it be possible to add a feature that when you press enter or press right arrow, or some arbitrary keybinding, that it takes the cursor directly to the line where the anchor resides ? so that you can directly start editing ?
thank you.

Hello,
I have changed it so that when you select an anchor, it will now also move your cursor to that position (instead of only just moving the editor screen to that line). You can then use the View: Focus First Editor Group command (keybinding ctrl+1 by default) to focus the editor and directly start editing.
Feel free to clone the repo and build the extension for yourself. :)
Thanks for the kind words! Enjoy using Comment Anchors!


enhancement: add user-agent to allowed CORS headers

Right now, we limit accepted headers via CORS to
{
  "Access-Control-Allow-Headers": [
    "Authorization, Content-Type"
  ]
}

to allow for browsers to communicate directly with openwhisk API endpoints, it is helpful to add User-Agent to the list of allowed headers. many popular request libraries tack on default user agents, including our own openwhisk npm.

The proper fix is to check if request method is OPTIONS AND contains the header Access-Control-Request-Headers then in the response for that request (pre flight) then echo back the same value in Access-Control-Allow-Headers
I just double check what we do in the apigateway for default config for Cors https://github.com/apache/incubator-openwhisk-apigateway/blob/master/scripts/lua/cors.lua
There might be other headers to allow it all depends on the request header value.

some background info
“This header is required if the request has an Access-Control-Request-Headers header.”
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Headers


Add Klarismo to list of users

Description
We are using Luigi in production to reliably process massive datasets of volumetric data.

Can you link to a presentation or blog post or something where you talk about your Luigi use? Note that all most other links are that way. Thanks!

We don't have anything public just yet, but I have an intention to write a post about how we're integrating Luigi with JIRA and Slack. Should I hold back until that's published, or can I just update the link later?

We can keep the PR open until then so that you have more incentive to write the post :)

can you rebase on latest changes now? thanks!

Let's just close this for now.


useEventListener does not check to see if event target is valid, which can break SSR

Prior Issues
Are there any existing issues or PRs that relate to this problem? If so, link them here.
What is the current behavior?
As reported by damntv on Discord, useEventListener currently does not check the event target is valid, which can cause an error if you are trying to target window, document, etc. during SSR.
Steps to Reproduce
useEventListener(window, "resize", () => {});

Throws an error when server side rendered because the window is not defined on the server.
What is the expected behavior?
@react-hookz/web should check to make sure the event target is valid, at least on server side, before trying to set the event.
Environment Details

@react-hookz/web version: 16.0.0
react version:
react-dom version:
typescript version:
OS:
Browser:
Did this work in previous versions? no

How should we go about fixing this?
Could it be just a simple isBrowser check before adding the event listener or maybe even setting the target parameter to null if isBrowser is false?
I attempted this, but found that I couldn't write a test which would reveal this bug, since in the SSR tests window can't be referenced at all. In fact, I launched a fresh NextJS project and learned that it won't even build if I give window to useEventHandler directly. All of this makes sense in a SSR setting. The workaround suggested in the Discord by damntv works in the tests and NextJS: useEventHandler(isBrowser ? window : null, ..., ...).
This begs the question: how would we move the isBrowser check inside of the hook in order for the users to be able to just do this in SSR:

useEventListener(window, ...);

Is this even possible (disclosure: I have little experience with SSR)?

I attempted this, but found that I couldn't write a test which would reveal this bug, since in the SSR tests window can't be referenced at all.

Doesn't that actually test the bug exactly? Assuming we don't have window when running SSR tests, that should be a great test case as that's the specific error we are trying to avoid not get during SSR.
My question is, do we have window provided during our not-SSR tests? If so, then I think that we could have this test in both test suites - and make sure the hook does not run but does not error during SSR, and does run client side.

My question is, do we have window provided during our not-SSR tests? If so, then I think that we could have this test in both test suites - and make sure the hook does not run but does not error during SSR, and does run client side.

We provide null during tests. Providing window makes the tests fail, because window cannot be referenced server-side, which is why it cannot even be passed to useEventListener server-side. useEventHandler(isBrowser ? window : null, ..., ...) works, because if isBrowser === false then window is not evaluated. If we moved the check inside the hook and passed window directly to the hook, window would be evaluated and error thrown.
The hook itself uses the provided event target only inside of an useEffect which runs only client-side.
Seems to me there is no bug here at all - or I am totally wrong and learn a lesson on SSR!

This makes me wonder, should we then perhaps support giving globalThis as the target as suggested in #961 ? Then users could just useEventListener(globalThis, ...) and everything should work. Currently the type of the target parameter does not allow this.

Any more thoughts on this? If not, I think this issue could be closed. Would love to see the issue list shrink a bit more!

As figured - types has changed and there is no more issues with global this, but useEventListener still not guarded against improper during SSR.
Im planning to address this issue by changing the way eventlistener added to our internal on and off methods that has target check. (on/off methods been introduced later that useEventListener)

Hi, this does not seem fixed to me. I'm encountering the exact same problem in next js. The error is ReferenceError: window is not defined.
The problem still remains that if we pass window to the hook, it gets evaluated on the server which gives this ReferenceError.

Something like: window || null or window ?? null also does not work because window is still getting evaluated.
However something like isClient() ? window : null will work, but again, this has to be done in the line where the hook is being called. In other words, it has to be done by the user.

I think the best approach to fix this is to change the function signature altogether and make it so that the target can be passed optionally in the options. The default for target can be window.

It has to be done by user, since user evaluates the window.
isClient() ? window : null works because isClient uses typeof window under the hood and thus it wont break.
Making target optional and placed as last call parameter will break arguments inferrence and is kinda weird.
nextjs users shall use globalThis to avoid issues during SSR since we have nothing to do with evaluation order - no matter where you'll place target parameter - attempt to evaluate window during SSR will case a reference error.

Just to note, this hook could also probably be reimplemented with React 18's useSyncExternalStore hook, which allows us to separately define the server-side behavior. But this goes back to the discussion and problems in #1023 .

@ArttuOll yes, but that does not solve the issue with attemp to pass window object during SSR

@ArttuOll yes, but that does not solve the issue with attempt to pass window object during SSR. we literally can do nothing since issue lays within user's code.

Yeah, you're totally right. That was just a quick thought.

Alternatively we can change the logic to: if target is null, set target to window

Even if there is no change being made in the function signature (which seems necessary to fix this), can we at least add the information that we should set target as globalThis for ssr to work properly in both useEventListener docs and the migration guide? I say this because in both places window is mentioned and in react-use target was optional, so migrating from react-use to react-hookz can be problematic because of this.

Alternatively we can change the logic to: if target is null, set target to window

This is bad bad design with inobvious logic, we definely wont follow react-use's way.

Even if there is no change being made in the function signature (which seems necessary to fix this)
It is not necessary. useEventListener accepts EventTarget along with null as first argument. Hook designed to be similar with addEventListener (except acceptance of null target).

can we at least add the information that we should set target as globalThis for ssr to work properly in both useEventListener docs and the migration guide?

Not all SSR engines have globalThis support. I really don't understand why you blaming hook for reference error that is caused by consumer's (hence your's) code. It seemed to me that SSR users shall be cautios with window evaluation and understand the execution vlow and how to overcome the need of it's referencing.
We physically unable to cover docs with all usecases that are possible within SSR (surprise - nextjs ist the only).
Attempt to evaluate window on server will cause a reference error and it is beyond hook library competence, as most SSR engines has it's own way to reference the window object safely (most of them leaning toward globalThis nowadays but not all).
The reason react-use assumed that by default developers want to add listeners to window - a big question to streamich.
We've never targeted to make things compatible with react-use, the target is to provide more obvious and more predictable hooks withut silly defaults and assumptions hiddent behind hook's facade.

The only thing we can do is to add notification that SSR users have to consult the docs of their SSR engine to safely reference the window object (i is complete surprise for me someone dont understand that though).

Whenever I've had to reference the window object, I've always done that in useEffect. Of course this won't work with hooks.
Listening to events of window is a common use case. So if there is no simple way to target window which works with SSR engines, then it doesn't seem like a good thing to me. But either way, adding some information about this in the docs should help with this.


Add "enable" everywhere

I'm a bit shy to propose this one, but as a first-timer to this plugin, it gets quite confusing...
For example to turn things off (educated guesses):
animals: chance: 0
structures: (mostly) enabled: false
however: villages should probably be spawnratio: 0.0
biome: weight: 0
But biome.cave: maxsize: 0
ores: chance-per-chunk: 0.0
trees: enabled: false
You get what I mean 😉? Every option is logical, but it'd be nice if they are harmonized... Or simplified by an "enabled" everywhere?

Is this considered done?

Hi @Hex27 , as a new user of this plugin, I found the various methods to disable features confusing. Different features use inconsistent settings to turn them off. (see what I figured out above)
While each option is logical, it would be beneficial to harmonize these settings.
The enable I've implemented just turns them off/on, but it doesn't address the underlying issue I pointed out in this ticket.
Of course feel free to close it, but I still think this one has merit enough to be addressed.


Extract the core functionality and provide a CLI tool

Is your feature request related to a problem? Please describe.
I'm an Emacs user and would like to use this tool at work, however seems no CLI option is available
Describe the solution you'd like
Extracting the core functionality into a separate package or somethin', then coupling that with the vscode extension for vscode users and offering a CLI that receives input from stdin and spits the results to stdout for everybody else
Describe alternatives you've considered
letting my coworkers sort the classes on their pull requests (not really an alternative)
Additional context
None.

Hey @shackra I made a CLI version of Headwind here: https://github.com/avencera/rustywind

Hey @shackra I made a CLI version of Headwind here: https://github.com/avencera/rustywind


Error when mash distance is 1

Hello !
I'm trying to use sistr on various scaffolds from Salmonella WGS assemblies, however I stumbled upon this error.
IndexError: list index out of range
After looking on it it appears that this happens when you submit a sequence that results in a mash distance equals to 1. I get it how a distance of 1 is a problem but maybe raising an error and skipping the sequence would be nice.

Hello,
thank you for the report, this issue has been addressed in the development branch of SISTR "sistr_cmd_update_2018" and will be merged into the main branch with the new release of SISTR.
Thanks,
James


[MM-22237] Fix text capitalization

Summary
Change 'mattermost' to 'Mattermost' on iOS camera permissions alert text.
Ticket Link
MM-22237
Checklist

[x] Includes text changes and localization file updates

Device Information
This PR was tested on: iPhone 11 Simulator
Screenshots

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/mattermost-mobile/4332
https://circleci.com/gh/mattermost/mattermost-mobile/4331

Artifact links:
https://4332-70265724-gh.circle-artifacts.com/0/~/mattermost-mobile/Mattermost_Beta.apk
https://4331-70265724-gh.circle-artifacts.com/0/~/mattermost-mobile/Mattermost_Beta.ipa


Not able to preview the app

The version of the SDK is 31.00. To preview it should be above 42.00.

Yeah, it haven't been updated for more than 3 years and it have a lot of outdated dependencies ¯\_(ツ)_/¯


Pin tensorflow-io version 0.23.1

Changed the tensorflow version to 2.7.1, and tensorflow-io version to 0.23.1 , to resolve errors according to issue #5

Hi @euhidaman,
Thanks for taking the time to open this pull request.
I'm closing this in favour of #11 which also pins the tensorflow-model-optimization dependency, which is needed for the notebook to work in Colab.


News page: Suggest relevant contents

In our current News/Data Use pages we have a few ways to suggest further readings:

Next story: the chronologically next earlier article of the same type;
Related GBIF resources: essentially suggested readings on our domain;
Tags: they point to the list of all items that are tagged with a specific term.

Ideally we want to suggest relevant contents based more on themes like "climate change" and "niche modelling", rather than time series, so "next story" may not be useful in the coming implementation. The goal is to allow visitors to explore more and still find them interesting.
The "Related GBIF Resources" are editor-specified pages in our domain as links. It can be used as a "see also" list, which should take precedence over other potential calculated suggestions (see the next paragraph).
For tags, we could calculate the relevance by shared tags, but given the amount of news/data use contents is not much, it's not easy to see how much impact it could be. Though we need to explore that. Before we could figure out the most-suitable way to guide visitors on our site, for now as a step of improvement, we should probably still keep the list of them, but the targeted page should be a pre-filtered search result page shows contents of the same type which share the same tag.
Any thoughts? Please comment on this thread.

In discussion we decide to close this now, and consider this after observing user behaviour and wishes


Support configuration via HTML data attributes

Hi, it would be great if you will add support for configuration via HTML data attributes.
like this:
<select id="ux-select"
              data-is-searchable="false"
              data-is-search-focus="false" >
    <option value="0">JavaScript</option>
</select>

Thank you for your request. Data attributes support has been added in the latest release.


Add a verification of docstrings.

Add a test case to verify that docstrings have been compiled into the support package.
Refs beeware/Python-Apple-support#165.
PR Checklist:

[x] All new features have been tested
[x] All new features have been documented
[x] I have read the CONTRIBUTING.md file
[x] I will abide by the code of conduct

I don't have write access to this repository, so I can't merge the PR.

I've also added permissions for team members.


Remove routes and views for legacy terms of service and privacy pages

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[ ] Closes currently open issue (replace XXXX with an issue no): Closes #XXXX Part of #15474

Description

Removes the views and routes for the legacy Terms of Service and Privacy pages. Completes 2 of the 5 tasks from #15474.

LGTM. Thanks @padulam for contributing to freeCodeCamp! 🌮 👍 💯


Breakpoints Invalid for Angular CLI 1.1.1

Breakpoint are not hit when using the Angular-CLI recipe with Angular CLI v 1.1.1.  However they do work with Angular CLI v 1.0.6.  This will need to be investigated.  The issue was discussed in PR #2 by @weinand.

This issue was moved to Microsoft/vscode#28730


Runtime error during phase 0 training

Hi @dianchen96 and @bradyz
I am at the stage 0 of training an image agent. There is a runtime error that looks related to a bug of PyTorch with Python 3.5. I am able to train once I set num_workers=0 but I am wondering if you know another way around that does not sacrifice training speed. Thanks!
Please find the error messages below.
(lbc) peiyunh@ubuntu:~/code/lbc/training$ CUDA_VISIBLE_DEVICES=0 PYTHONPATH="/home/peiyunh/software/CARLA_0.9.6/PythonAPI" python train_image_phase0.py --log_dir ../ckpts/image_phase0 --pretrained --teacher_path ../ckpts/priveleged/model-128.th --dataset_dir ../data
pygame 1.9.6
Hello from the pygame community. https://www.pygame.org/contribute.html
augment with  None
Finished loading ../data/train. Length: 167789
augment with  None
Finished loading ../data/val. Length: 52600
Loading ResNet weights from : https://download.pytorch.org/models/resnet34-333f7ec4.pth
Epoch:   0%|                                                                                | 0/3 [00:00<?, ?it/sException in thread Thread-4:                                                                                | 0/10 [00:00<?, ?it/s]
Traceback (most recent call last):
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 914, in _bootstrap_inner
    self.run()
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/multiprocessing/resource_sharer.py", line 139, in _serve
    signal.pthread_sigmask(signal.SIG_BLOCK, range(1, signal.NSIG))
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/signal.py", line 60, in pthread_sigmask
    sigs_set = _signal.pthread_sigmask(how, mask)
ValueError: signal number 32 out of range
Exception in thread Thread-4:
Traceback (most recent call last):
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 914, in _bootstrap_inner
    self.run()
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/multiprocessing/resource_sharer.py", line 139, in _serve
    signal.pthread_sigmask(signal.SIG_BLOCK, range(1, signal.NSIG))
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/signal.py", line 60, in pthread_sigmask
    sigs_set = _signal.pthread_sigmask(how, mask)
ValueError: signal number 32 out of range

Exception in thread Thread-4:
Traceback (most recent call last):
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 914, in _bootstrap_inner
    self.run()
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/multiprocessing/resource_sharer.py", line 139, in _serve
    signal.pthread_sigmask(signal.SIG_BLOCK, range(1, signal.NSIG))
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/signal.py", line 60, in pthread_sigmask
    sigs_set = _signal.pthread_sigmask(how, mask)
ValueError: signal number 32 out of range

Exception in thread Thread-4:
Traceback (most recent call last):
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 914, in _bootstrap_inner
    self.run()
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/multiprocessing/resource_sharer.py", line 139, in _serve
    signal.pthread_sigmask(signal.SIG_BLOCK, range(1, signal.NSIG))
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/signal.py", line 60, in pthread_sigmask
    sigs_set = _signal.pthread_sigmask(how, mask)
ValueError: signal number 32 out of range

Exception in thread Thread-4:
Traceback (most recent call last):
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 914, in _bootstrap_inner
    self.run()
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/multiprocessing/resource_sharer.py", line 139, in _serve
    signal.pthread_sigmask(signal.SIG_BLOCK, range(1, signal.NSIG))
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/signal.py", line 60, in pthread_sigmask
    sigs_set = _signal.pthread_sigmask(how, mask)
ValueError: signal number 32 out of range

Exception in thread Thread-4:
Traceback (most recent call last):
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 914, in _bootstrap_inner
    self.run()
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/multiprocessing/resource_sharer.py", line 139, in _serve
    signal.pthread_sigmask(signal.SIG_BLOCK, range(1, signal.NSIG))
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/signal.py", line 60, in pthread_sigmask
    sigs_set = _signal.pthread_sigmask(how, mask)
ValueError: signal number 32 out of range

Exception in thread Thread-4:
Traceback (most recent call last):
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 914, in _bootstrap_inner
    self.run()
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/multiprocessing/resource_sharer.py", line 139, in _serve
    signal.pthread_sigmask(signal.SIG_BLOCK, range(1, signal.NSIG))
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/signal.py", line 60, in pthread_sigmask
    sigs_set = _signal.pthread_sigmask(how, mask)
ValueError: signal number 32 out of range

Exception in thread Thread-4:
Traceback (most recent call last):
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 914, in _bootstrap_inner
    self.run()
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/multiprocessing/resource_sharer.py", line 139, in _serve
    signal.pthread_sigmask(signal.SIG_BLOCK, range(1, signal.NSIG))
  File "/home/peiyunh/miniconda3/envs/lbc/lib/python3.5/signal.py", line 60, in pthread_sigmask
    sigs_set = _signal.pthread_sigmask(how, mask)
ValueError: signal number 32 out of range

Also, what FPS should we expect to reach during training? I have about 0.6FPS for training and 0.8 FPS for validation. Is that too slow?

What pytorch version do you have?

I tried both 1.5.1 and 1.0.0. Both run into this error when num_workers is set above zero.

That's odd. I was using Ubuntu 14.04/16.04 with Python 3.5 + PyTorch 1.2 when working on this project, never run into this issue. Maybe try upgrading python to 3.6?

Would I need a new egg for using Python 3.6?

The 3.5 egg should be compatible with 3.6

Thanks so much @dianchen96 . Switching to Python 3.6 solves the issue. I am now able to train with num_workers=8. There seems to be a 4x speed up. This means phase 1 training will likely take 1.5 days to finish. Does that sound right to you?

That looks good. I'd recommend first trying lower epoch (e.g. 32) phase 1 model and see how they work. The numbers listed on index.md come from a 32 model. P.S you might need to slightly tune the steering PID parameters.


Is the official document of generating codes outdated? or some classes are not auto-generated?

I'm watching this document.
And I've developed with kotlin project.
I'm generating codes using com.netflix.dgs.codegen plugin in gradle with 5.12.4.
And my code gen config is as follows:
generateClient = true
generateDataTypes = true
generateKotlinNullableClasses = true
generateKotlinClosureProjections = true

My question is when I generate kotlin codes from my schema, there are many projection classes ~~~Projection for each type but has no classes named like ~~~ProjectionRoot.
But when I read the document, some example mentions MoviesProjectionRoot class. Is the class auto-generated one? If yes, then why my auto-generated codes has not that kind of class??

You are using a different API specifically for Kotlin client codegen. The docs are here: https://netflix.github.io/dgs/advanced/kotlin-codegen/


Missing hashtag(s) in step 45 of the new js course (build an rpg)

Describe the Issue
Step 45 of the new build an rpg in JS course seems to be missing multiple hashtags. For eg: The following seems to be missing a hashtag in front of the word text (the one in backticks).
Now you need to modify your display text. Change the innerText of the text to be You enter the store..
The word text in backticks seems to be referring to an element whose id is text. So I believe it should use a hashtag as in #text.
If this is correct, then there are multiple places to be fixed in this step.
Affected Page
curriculum/challenges/arabic/15-javascript-algorithms-and-data-structures-22/learn-basic-javascript-by-building-a-role-playing-game/62a7bfabe119461eb13ccbd6.md
Your code

Expected behavior
All references to an element whose id is text should be clarified either with a hashtag in front of the id value or by explicitly referring to the text element.
Screenshots
No response
System
N/A
Additional context
No response

The word text is referring to the text variable. As such, I do not believe it should be changed to say #text.

Expanded: "Change the innerText of the #text to be You enter the store.." suggests the HTML should be altered. However, the expectation is the innerText property of the text variable (object) be set to "...".

I suggest the text be changed to:

Change the innerText of the text variable to be You enter the store..

Although, I would also be fine with any of:
a) ...text object ...
b) ... of text to be ...

Hey @ShaunSHamilton, shall I go ahead and open a PR with your suggested changes?

@Sriparno08 We are still discussing the changes (if any) we might expect here. Once the author, or more contributors chime in about the suggestions, we will open this up for contribution as indicated by either the https://github.com/freeCodeCamp/freeCodeCamp/labels/help wanted or https://github.com/freeCodeCamp/freeCodeCamp/labels/first timers only label.

Alright, @ShaunSHamilton 👍

hi Shaun, the property 'innerText' is a property of the -variable- or the -element- ?
My understanding is when we teach concepts like innerText or innerHTML we are teaching properties that belong to the elements we retrieve from the querySelector. (these are all properties that we manipulate in the DOM, not in the javascript variable?)
Another way to test this is to say: let's pretend the code was:
let v = document.querySelector("#text");
Then would you still say "change the innerText of the variable v"? or would you say "change the innerText of the #text element?"

hi Shaun, the property 'innerText' is a property of the -variable- or the -element- ?

innerText is a property of a JavaScript object. That is, we are asking Campers to make use of a JavaScript object. Previously, we defined the variable text.

In my mind, we can go two ways with this:

Have an explicit hint (what we usually do) whereby we tell Campers what to use/change/do

If they need to do something to the <element id="text">, say #text.
If they need to do something to the variable text, say text.

Have a vague (actual) hint, which I would phrase:

"Set the #text element's text content "as rendered" to be You enter the store.." ^1

The difference being:

Campers know their code needs to involve the text variable, and somehow use a property named innerText
Campers know what to change, but need to think more in order to know to use text.innerText = ...

I think I'm beginning to understand what I didn't understand before. I was thinking along the lines of 'innerText' being a reference to what will actually change on the page versus the more literal innerText property of the object stored in the variable text.
Part of the confusion may be that I haven't seen all the steps in order. (maybe if I read them all in order it will be obvious)
In other steps the phrasing seems clearer such as when they say:
You should set the onclick property of button2 to be buyWeapon.
Somehow the word 'property' here made it clearer to me.
Can we go with something similar for eg:
Now you need to modify your display text. Change the `innerText` property of the `text` to be `You enter the store.`.

ie. adding the word property as needed to affected sentences?

ie. adding the word property as needed to affected sentences?

I would be happy with that. However, I do not like the "of the text ...". We should add something like "of the text variable"

Okay I understand that.
"... property of the text variable to be ..."
Or do it like the other sentence I mentioned which doesn't classify button1 at all.
"... property of text to be ..."

I prefer fewer words. So, let us go with:

Now you need to modify your display text. Change the innerText property of text to be You enter the store..

@Sriparno08 If you would like to update your PR with the agreed-upon changes? We can see what other reviewers think on the PR.

Sure! I am going ahead!


desired_configuration needs to be sync between metacontrol nodes

The metacontrol MAPE-K elements need to sync on what is the desired configuration at each time:

[ ] ros_graph_parser (and rosgraph_monitor? ) use it to know what .rossystem to compare with the one extracted from the rosgraph
[ ] mros1_reasoner needs to initialize what is the initial configuration, so it can assign the current QA values and configuration diagnostics from monitoring to it desired_configuration
[ ] rosgraph_manipulator.py receives it to select which configuration to deploy
=>This one is done via the MvpReconfiguration action goal received from mros1_reasoner

I propose to use a ROS global parameter to sync this value and also to initialize it.
What do you think @ipa-nhg @ipa-hsd @marioney

to me the best solution will be to set a new parameter to publish (from the metacontrol, right?) the new desired configuration. For example:
rosparam set /current_configuration "f1_v1_r1"
(obviously from code and not from command line)

* `ros_graph_parser` (and [`rosgraph_monitor`](https://github.com/rosin-project/rosgraph_monitor)? ) use it to know what .rossystem to compare with the one extracted from the rosgraph

Here is not needed. We can't modify dynamically the desired.rossystem that the rosgraph_monitor takes as input. The main purpose of the rosgraph_monitor for this models experiment is verify that all the required nodes to run my application are up. The current desired.rossystem looks -> https://github.com/rosin-project/rosgraph_monitor/blob/observers/resources/metacontrol_desired.rossystem

We can't modify dynamically the desired.rossystem that the rosgraph_monitor takes as input. The main purpose of the rosgraph_monitor for this models experiment is verify that all the required nodes to run my application are up.

For the immediate future, I am very interested in being able to change it dynamically, in order for the metacontrol to manage the nodes on the fly, have a dynamic rosgraph (e.g. kill and launch new nodes as required by the mission goals)

to me the best solution will be to set a new parameter to publish (from the metacontrol, right?) the new desired configuration. For example:
rosparam set /current_configuration "f1_v1_r1"
(obviously from code and not from command line)

Agreed! I think we should name that rosparam desired_configuration, so as not to confuse it with the one the rosgraph_parser generates

[ ] @marioney has an issue for metacontrol_experiments
[ ] @chcorbato needs to do it for mros1_reasoner

Since it is under control and there is one issue that will finalize the implementation of this, I close this "design issue"


Build failed for Nordic Demo

Nordic build fails on latest commits in ble_beta.
Building ‘aws_demos_ble’ from solution ‘aws_demos_ble’ in configuration ‘Debug’
1> Linking aws_demos_ble.elf
1> Output/aws_demos_ble Debug/Obj/aws_iot_mqtt_serialize.o: In function AwsIotMqttInternal_InitSerialize': 1> C:\Users\ljaynes\amazon-freertos\lib\mqtt/aws_iot_mqtt_serialize.c:624: undefined reference to AwsIotMqttBLE_InitSerialize'
Build failed
I can get it to build by renaming some defines and functions in the aws_iot_config.h file.
extern bool AwsIotMqttBLE_InitSerialize( void );
extern void AwsIotMqttBLE_CleanupSerialize( void );
#define AwsIotMqttInternal_InitSerializeAdditional AwsIotMqttBLE_InitSerialize
#define AwsIotMqttInternal_CleanupSerializeAdditional AwsIotMqttBLE_CleanupSerialize
to
extern bool IotBleMqtt_InitSerialize( void );
extern void IotBleMqtt_CleanupSerialize( void );
#define AwsIotMqttInternal_InitSerializeAdditional IotBleMqtt_InitSerialize
#define AwsIotMqttInternal_CleanupSerializeAdditional IotBleMqtt_CleanupSerialize
This allows me to build the project but I then get an error when turning on the mqtt proxy via the Android SDK.
8 3957 [BLE] Failed to initialize the decoder, error = 7, object type = 4
The error seems to be coming from the static AwsIotSerializerError_t _createDecoderObject() function in  aws_iot_serializer_tinycbor_decoder.c, because  cbor_value_copy_text_string() is returning CborErrorDataTooLarge.

Thank you for reporting the problem! We fixed the issue with this PR:https://github.com/aws/amazon-freertos/pull/342

Hi,
im having similar issue with esp32. After pairing/bonding im getting those errors:
5 78 [OTA] OTA demo version 0.9.2
6 78 [OTA] Creating MQTT Client...
7 78 [OTA] Waiting for a network connection.
8 8042 [Btc_task] [INFO ][DEMO][8042] BLE Connected to remote device, connId = 0

E (82063) BT_GATT: gatts_write_attr_perm_check - GATT_INSUF_AUTHENTICATION
E (82423) BT_SMP: Value for numeric comparison = 271894
9 8209 [InputTask] Numeric comparison:271894
10 8209 [InputTask] Press 'y' to confirm
11 8756 [InputTask] Key accepted
12 8756 [InputTask] status: 0
W (87913) BT_SMP: FOR LE SC LTK IS USED INSTEAD OF STK
13 10286 [Btc_task] Failed to initialize the decoder, error = 7, object type = 4
14 10295 [Btc_task] Failed to initialize the decoder, error = 0, object type = 3
15 12036 [Btc_task] [INFO ][DEMO][12036] BLE disconnected with remote device, connId = 0

PS amazon-freertos is with PR:#342 merged already

Thanks. It looks like the Nordic build issue was fix. Any idea on the failed to initialize the decoder error?

Hello,
We recently updated the protocol from using JSON to CBOR. The advantage is a big boost in speed due to a reduction of overhead. OTA should be faster now.
Those changes entails an update of the APP too. Please download the latest IOS SDK:
https://github.com/aws/amazon-freertos-ble-ios-sdk/
If you are using android, it has not been updated yet but we are working on it and should be updated soon.
I am not closing the ticket, I'll let you know when it is updated and close the ticket.
Hugues

Looks like the Android SDK was updated and the failed to initialize the decoder error was fixed. Thanks.


Contract address for nft 1155

Description
Adding the contract address parameter to erc 1155 flows.
Is this PR related with an open issue?
Related to Issue https://github.com/nevermined-io/internal/issues/363
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] Follows the code style of this project.
[ ] Tests Cover Changes
[ ] Documentation

Funny gif

package version should be updated


Download all Corporate Signatures for this CLA Group as CSV

Summary
Download all Corporate Signatures for this CLA Group as CSV
Background
For a description of the services needed, view the Project Console PRD.
Acceptance Criteria
The "done" criteria when this feature or problem is resolved. Such as:

Unit Tests added and running in CI
Functional Tests updated to cover feature, if applicable
Demonstrate the set of capabilities to the product team while the code is running in the DEV environment.

References

Project Console PRD

@pranab-bajpai
As we discussed the one of the meeting. This is not needed anymore.
Closing this issue. Re-open if necessary.


add instruments resources with get and list subcommands enhancement

Command would call the v3/instruments api resource. You could list all instruments or get one with the instruments_id . Optional flags could include --json, --pretty, --csv and --manufacturers_id to call /v3/manufacturers/{manufacturers_id}/instruments

resolved in v0.4.0


DB foreign key changed

[x]  Replaced foreign key in table image_results
[ ] New ERD schemas (if required)

https://github.com/mitwelten/mitwelten-db-backend/issues/27

No new ERD schemas, will be done when environment-entities are added to the schema.


Fix broken links to chrome dev tools docs

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm run test-challenges. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

Description

Fixed all the broken links to the chrome dev tools docs in the chrome video challenges.
Closes #11041

LGTM 👍  Thanks!


"Stay signed in" option for auth

Feature request
Is your feature request related to a problem? Please describe.
I'm constantly needing to log back into my app, even though I've set the expiration date to be a week long and have autoRefreshToken set to true. It seems like I need to re-enter my credentials even if the token is not actually expired (i.e. I need to re-enter my credentials even though a week has not passed since the last time I did it). This happens both on localhost and on my production website. The expiration date also doesn't matter, I've set it to be either the minimum or the maximum and the same behavior occurs.
If autoRefreshToken is true, I would expect the token to be automatically refreshed without needing to enter my credentials again. In other words, if I've logged in once, I should stay logged in unless I've explicitly logged out or cleared my cookies/cache.
Basically what I'm looking for is something that works equivalently to a "Stay signed in" checkbox that's present on most websites, which is AFAIK not possible with Supabase at the moment. You don't need to log in to GitHub/Twitter/YouTube every day you open the website, which is unfortunately pretty much the experience I have with Supabase Auth right now.
Describe the solution you'd like
If I've logged in once, I should stay logged in unless I've explicitly logged out or cleared my cookies/cache. This means no 401 errors, and no prompting to log in.
Ideally, the auto-refreshing of the token would actually function completely offline. So if the app is a PWA and you've already signed in online once, then you should still be authenticated if you visit the app again when you're offline.
This "stay signed in" option could be a separate opt-in parameter. But most likely, if autoRefreshToken is true, then most people would expect that this is the behavior that happens (that's certainly my assumption).
Describe alternatives you've considered
No way to do this in Supabase AFAIK.
Additional context
Potentially fixing https://github.com/supabase/supabase-js/issues/197 might fix this issue as well.

I moved to using client side auth and everything works as I would expect. So for anyone looking at this issue who's using Next.js, instead of following the Next.js + Supabase example, I would recommend handling everything client side instead (i.e. do not use getServerSideProps).

I'm reopening this because I'm still getting logged out even when using client side auth. It would be really, really great if I could stay logged in.
For context, the refresh token is being persisted locally. When the user tries to navigate to the app, I'm calling the signIn method on Supabase Auth with the refresh token.  But this is not happening; the user sometimes still needs to re-enter their credentials.

Closing in favor of https://github.com/supabase/supabase-js/issues/254. Please see that issue for updated details.


Fix readme for 403 when requesting secrets

Fixes for this error when trying to read secrets in container.
E0817 01:44:26.955028       1 vault.go:154] failed to retrieve the resource: type: secret, path: secret/.... from vault, error: Error making API request.
URL: GET http://vault:8200/v1/secret/...
Code: 403. Errors:

* permission denied

The problem is the the role created doesn't have the policy attached.

The sample-app role does not need the kubernetes-vault policy. The kubernetes-vault policy is used by the kubernetes-vault token role. There is a setup script that automates all of this and it currently works correctly.
See:

https://github.com/Boostport/kubernetes-vault/blob/master/deployments/quick-start/setup.sh#L102
https://github.com/Boostport/kubernetes-vault/blob/master/deployments/quick-start/setup.sh#L112

I followed the instructions listed in the readme and it doesn't work without this change.

@krazik Thanks for the feedback! I will spin up minikube and test the instructions out again to see what's happening.

Ok, here's are the environments I tested in:

Minikube with Kubernetes 1.7.0 without RBAC
Minikube with Kubernetes 1.7.0 with RBAC

In both cases, I deployed kubernetes-vault.yml which included RBAC objects.
In both cases, Kubernetes-Vault started successfully and the sample-app instances also received a token after they started.

ping @krazik

@krazik I am going to close this as the PR has gone stale and the issue was not reproducible.


fix todo: rollkit adapter multiple blocks submission

right now, rollkit adapter API can submit several blobs at the same time and expects that a single value "da layer height" is returned. It looks like it's implied that the blobs are going to be submitted all at the same time.
I am not sure why they make such an assumption, but it looks like we could:

leverage the existing batch functionality from the  utility pallet. It looks like batch_all variety should work better, so that all blobs are either included or not included.
roll our own implementation of submit_blob_batch and then reimplement submit_blob as a degenerate case of submit_blob_batch with one blob.
fuse the blobs together in the rollkit adapter or dock.

The (2) approach seems to be (1) better on the first sight, at least because it's more efficient. Specifically, it performs a single check, instead of performing the checks for each blob. The (2) will require additional benchmarking on our side, whereas (1) won't?

[!NOTE]
There is a weird thing, that if the blob validation fails, the blob will not get into the final NMT, but it will still occupy space in the block.
See https://github.com/thrumdev/sugondat/issues/74

The (3) maybe a good approach for now. It doesn't require any changes on the runtime side and should be pretty simple.

May be solved in https://github.com/thrumdev/blobs/issues/106


Docs

Updated docs to reflect new docker system
Also bumped common_models version and deleted some redundant code

Good to know, I'll see if I can look into why its failing


Backport 322886 to release 24.05

Description of changes
Combined minor bumps and fix 2.23 build:
https://github.com/NixOS/nixpkgs/pull/322886
https://github.com/NixOS/nixpkgs/pull/322977
@nixos/nix-team
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build nix
@ofborg build nixVersions.nix_2_18
@ofborg build nixVersions.nix_2_19
@ofborg build nixVersions.nix_2_20
@ofborg build nixVersions.nix_2_21
@ofborg build nixVersions.nix_2_22
@ofborg build nixVersions.nix_2_23

Oh, we don't have 2.23 yet?
ofborg's darwin builds are slow, but a few have succeeded, so I'm fairly confident the rest of them will be ok. Let's get this into the channel.


Rtl support feature

Description
I tried to add support for RTL. I think RTL support is essential. Especially for websites that use a language written from left to right, such as Arabic. I tried to do so in an easy way where all the user needs to do is to add the class "rtl" and their component will become in the right to left direction.
I also updated the documentation accordingly.
Motivation & Context
As a web developer, I did feel the need to use the rtl direction on different bootstrap elements, especially the navbar. I then realized that setting a class named "rtl" that updates the direction of any element and sets it to "rtl" is a good option.
The Issue https://github.com/twbs/bootstrap/issues/37938 was opened by ahmedaabuwarda as a feature request regarding this matter.
Type of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would change existing functionality)

Checklist

[X] I have read the contributing guidelines
[X] My code follows the code style of the project (using npm run lint)
[X] My change introduces changes to the documentation
[X] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Live previews
I used the rtl mode on the navbar. Here is a preview of the result I got, which is exactly the expected behavior:

Related issues
(https://github.com/twbs/bootstrap/issues/37938)

We already have RTL support.

Pull
--- Original Message ---
From: "Mark Otto" @.>
Sent: January 27, 2023 11:34 AM
To: "twbs/bootstrap" @.>
Cc: "Subscribed" @.***>
Subject: Re: [twbs/bootstrap] Rtl support feature (PR #37960)
Closed #37960https://github.com/twbs/bootstrap/pull/37960.
—
Reply to this email directly, view it on GitHubhttps://github.com/twbs/bootstrap/pull/37960#event-8369008101, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A47OQWCJWGTMHW2SLHE5JC3WUMJYFANCNFSM6AAAAAAUIAGUTA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Use Windows 11 build, It can't run in Windows 10

I set not windows 11 use setCustomEffect. It's only in Task Manager can see

Sorry I don't understand, what you want say ?

The result I build on Windows 11 can't be used on Windows 10, it can only see the process in the task manager

I watch this in the evening I can't currently

Hello I don't have windows 10 so I can't try, next week I download windows 10 to emulate it

Hello I don't have windows 10 so I can't try, next week I download windows 10 to emulate it

ok thanks

@GregVido Hello, Do you know how to solve this issue

Hello, I found the problem
  // mainWindow.setLightTheme()
  if (menuBlur || menuBlur === undefined) {
    if (IS_WINDOWS_11) {
      mainWindow.setMicaEffect()
    } else {
      // mainWindow.setRoundedCorner()
      mainWindow.setCustomEffect(4, '#fff6dc', 0.7);
    }
  } else {
    mainWindow.setCaptionColor('#fff6dc')
  }

mainWindow.setLightTheme() and mainWindow.setRoundedCorner() is for windows 11.
Sorry for the time, I'm a student and I don't have much time right now.

ok，thinks


Show the request parameters / url used to obtain an access_token / id_token

This issue is imported from pivotal - Originaly created at May 31, 2019 by Okke Harsta
Like the current playground we want to show the request parameters - authorization obfuscated - and url used to obtain an access_token / id_token. In the right panel add a tab with this information. See tasks.
The result from token / introspect and userinfo endpoints is asserted in https://github.com/OpenConext/OpenConext-oidc-playground/blob/master/oidc-playground-server/src/test/java/playground/api/OidcTest.java#L128.

When performing the code flow where the authorization url is returned to the client we need to store the this url in the state so we can show it on the Request tab when the tokens are retrieved and JWT decoded. (Okke Harsta - Jun 4, 2019)

For someone new to OAuth2 and OpenID Connect, I can imagine that it's not clear what the distinction is between the authorization and token request. Can we make that more visible to the end user? For instance by adding texts like:
step 1: authorization request (from the browser of the user)
stap2: (token request done by the relying party)  (Bart Geesink - Jun 13, 2019)

See activity (Okke Harsta - Jun 13, 2019)


[Suggestion] Remove title on first join

Similarly to the motd-on-join in #30, I would suggest removing the title that's displayed on first join (that you can change in the config) because imo it'd belong into an essentials plugin like Nexus, Nucleus, etc. and is quite out of place for a world management plugin.

Agreed
0b1f88b3cc4a69c50fc660a2921359a9f15c6ee0


External libraries (Maven) in Java

how do you add a maven library in a java project?  For example org.telegram.telegrambots.
I have already the pom.xml

Local OpenJDK needs to be implemented first. #101
Meanwhile, you can code telegram bots using Python or Node.js.

Local OpenJDK added in https://github.com/thebaselab/codeapp/commit/39155744844ad472f0b79c714230a8691a7832bb.


createaccountcmd: Improving account param description

Description
Updating the account parameter description to let the user know that a new account will be created rather than the user being added to an existing account
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

This is just doc changes, Travis tests LGTM; merging based on this.


there may be a bug in cooccur.c  when the bin file is empty

in file cooccur.c line 177-184
for (i = 0; i < num; i++) {
sprintf(filename,"%s_%04d.bin",file_head,i);
fid[i] = fopen(filename,"rb");
if (fid[i] == NULL) {log_file_loading_error("file", filename); free_fid(fid, num); free(pq); return 1;}
fread(&new, sizeof(CREC), 1, fid[i]);
new.id = i;
insert(pq,new,i+1);
}
when the content in "filename" is empty， the CREC new will computer twice。
let's see the corpus has only the following words:
"training the vectors can be speeded up by increasing the training parallelism to match the number of physical CPU cores available"
there will generate two bin files,  and one of files is empty.

when the content in "filename" is empty， the CREC new will computer twice。

Please clarify what you mean by this.  sizeof(CREC) will be the size of the C object, not the data file itself.
In terms of git usage, it will be easier to follow newly posted issues if you:

use ``` to denote code blocks.  it will look like this:

asdf {
  stuff;
}

link to the lines of code you are interested in.  if you click on the line number on github, three dots should show up.  one of the options will be copy permalink.  for example

https://github.com/stanfordnlp/GloVe/blob/a6f2b947358bd5a0bdb825af3ebe429ab43a3cb5/src/common.h#L7


ctrl+alt+h as ctrl+backspace

Hi,
I am trying to port an autokey script that translates ctrl+alt+h to ctrl-backspace but so far I didn't manage

To answer my own question, if somebody else needs that:
down + ctrl + alt + key "h" => function()
     kbd:pressMod("Control", "Delete")
     kbd:echo()
end


On Edge browser, klas-helper doesn't work

On web browser 'Edge' which MS launched out,
Somehow I can not use this program.
As far as I know, Chrome Extensions should be compatible with Edge as well,
but klas-helper doesn't apply to it.
I don't know exactly whether that is a problem of TamperMonkey or not,
just wanna know people have same issue like I mentioned above.

Is your edge browser is newer version(chromium based) or legacy version(Spartan)?

When I tested it, it works well after installing TamperMonkey.
(Legacy Edge)

It's chromium based one.
Would you test on it, and leave comments?

It works well. I tested it in Version 83.0.478.54 (Official build) (64-bit).

It also works on my environment, please provide detailed information about your environment. If we cannot implement bugs on our environment, we'll close this issue.


while scrolling in iphone cursor is also scrolling sometimes

Seems like a styling issue.
Closing since this is out of the scope of this library.


Cloudsuite: in-memory analytics benchmark

I signed it!

I think our README.md is getting out of date. It doesn't have information about all the benchmarks. Could you add information about this one?

I addressed everything except moving _HasDocker and updating README.md. For _HasDocker see the separate comment. There is no information about available benchmarks in the README.md file as far as I can see. Running ./pkb.py --help lists all the benchmarks and all the benchmark sets.

Took another pass. Mostly style comments at this point.

The tox.ini merge conflict is the major blocker at this point. If that's resolved, this LGTM. Beyond that, the next major thing is having the docker helper function moved into the docker.py module. The rest is less important. When you're done making changes, let me know, and I can merge this into master.

OK, I'm done

Merged. Thanks for contributing!


Accept string to use as the prefix

Closes #1, but I'd rather have #2 instead.

Closed with changes in #4.


WunderGraph CLI should not overwrite existing files if possible when installed in existing projects

Problem
I tried to install WunderGraph in a repo that I'd created from a template, SvelteKit in this instance. I followed this
I ran
npx -y @wundergraph/wunderctl init

And was surprised and frustrated to see how many files were overwritten.
git status
On branch wunder
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   .gitignore
        modified:   README.md
        modified:   package.json
        modified:   tsconfig.json

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        .svelte-kit/
        .wundergraph/

no changes added to commit (use "git add" and/or "git commit -a")

Suggested solution
Modify the CLI install in an existing project to not overwrite files. When that seems impossible, please be very sure that my changes were as minimal. Here are my thoughts per file.

.wundergraph: Feel free to do whatever you want here. Most won't have this directory if they are trying to install it from the CLI.
.gitignore: Append WunderGraph items to the file. Bonus to only append lines that aren't already there.
README.md: Please, don't overwrite the README files. Instead, include a WunderGraph.md README or something inside the .wundergraph directory if needed.
package.json: Please, don't overwrite this. Append your dependencies/devDependencies to the list. If you like, append script commands to the scripts list, but prepend them wunder such as wunder:start or wg:start.
tsconfig.json: I'm not sure what to do. If we can, we want to modify as little as possible here. If you can't, you can modify things your way to fix later in the diff, or link the user to a good help doc to get this working.

Alternatives
If CLI-based installs to existing projects are not yet high enough priority

Add a step-by-step walkthrough here to help guide users to install it themselves piece by piece manually.
If there is not currently time to do that, links to example project repos on the major frameworks could be provided to fill in the gaps.
If there is not time for that, then dumping all the files needed into the .wundergraph directory is preferable to blindly changing files in the installed directory.

Additional context
node --version
v16.18.0

@bmcilw1 just know that we are on this! Thank you for reporting.

@bmcilw1 Thanks for reporting this. ´wunderctl init` is now deprecated in favor of create-wundergraph-app, which doesn't overwrite any existing files.


WIP tests/e2e: Add encrypted image test for operator

This PR adds an encrypted image test for the operator repository.

Hi @GabyCT ,
I ran your code and have some results to share.
With the generated nginx-encrypted.yaml  it fails and doesn't even try to connect at kbs. You can debug kbs logs by running:
kubectl logs -l app=kbs -n coco-tenant

Then I decided to apply the following pod yaml which is pretty similar to what is used on Kata CI. Notice that I'm using kata-qemu-coco-dev runtimeclass and the encrypted image generated with this scripts (ghcr.io/wainersm/nginx:encrypted)
apiVersion: v1
kind: Pod
metadata:
  name: test-e2e
  annotations:
    io.containerd.cri.runtime-handler: kata-qemu-coco-dev
    io.katacontainers.config.hypervisor.kernel_params: ' agent.guest_components_procs=confidential-data-hub agent.aa_kbc_params=cc_kbc::http://<IP_ADDRESS>:30327'
    io.katacontainers.config.agent.policy: IyBDb3B5cmlnaHQgKGMpIDIwMjMgTWljcm9zb2Z0IENvcnBvcmF0aW9uCiMKIyBTUERYLUxpY2Vuc2UtSWRlbnRpZmllcjogQXBhY2hlLTIuMAojCgpwYWNrYWdlIGFnZW50X3BvbGljeQoKZGVmYXVsdCBBZGRBUlBOZWlnaGJvcnNSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBBZGRTd2FwUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgQ2xvc2VTdGRpblJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IENvcHlGaWxlUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgQ3JlYXRlQ29udGFpbmVyUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgQ3JlYXRlU2FuZGJveFJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IERlc3Ryb3lTYW5kYm94UmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgRXhlY1Byb2Nlc3NSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBHZXRNZXRyaWNzUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgR2V0T09NRXZlbnRSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBHdWVzdERldGFpbHNSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBMaXN0SW50ZXJmYWNlc1JlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IExpc3RSb3V0ZXNSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBNZW1Ib3RwbHVnQnlQcm9iZVJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IE9ubGluZUNQVU1lbVJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IFBhdXNlQ29udGFpbmVyUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgUHVsbEltYWdlUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgUmVhZFN0cmVhbVJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IFJlbW92ZUNvbnRhaW5lclJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IFJlbW92ZVN0YWxlVmlydGlvZnNTaGFyZU1vdW50c1JlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IFJlc2VlZFJhbmRvbURldlJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IFJlc3VtZUNvbnRhaW5lclJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IFNldEd1ZXN0RGF0ZVRpbWVSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBTZXRQb2xpY3lSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBTaWduYWxQcm9jZXNzUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgU3RhcnRDb250YWluZXJSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBTdGFydFRyYWNpbmdSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBTdGF0c0NvbnRhaW5lclJlcXVlc3QgOj0gdHJ1ZQpkZWZhdWx0IFN0b3BUcmFjaW5nUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgVHR5V2luUmVzaXplUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgVXBkYXRlQ29udGFpbmVyUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgVXBkYXRlRXBoZW1lcmFsTW91bnRzUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgVXBkYXRlSW50ZXJmYWNlUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgVXBkYXRlUm91dGVzUmVxdWVzdCA6PSB0cnVlCmRlZmF1bHQgV2FpdFByb2Nlc3NSZXF1ZXN0IDo9IHRydWUKZGVmYXVsdCBXcml0ZVN0cmVhbVJlcXVlc3QgOj0gdHJ1ZQo=
spec:
  runtimeClassName: kata-qemu-coco-dev
  containers:
    - name: test-container
      #image: ghcr.io/confidential-containers/test-container:multi-arch-encrypted
      image: ghcr.io/wainersm/nginx:encrypted
      imagePullPolicy: Always
      command:
        - sleep
        - "30"

This time it is able to connect to kbs:
[2024-09-26T19:33:41Z INFO  kbs::http::attest] Auth API called.
[2024-09-26T19:33:41Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /kbs/v0/auth HTTP/1.1" 200 74 "-" "attestation-agent-kbs-client/0.1.0" 0.000117
[2024-09-26T19:33:41Z INFO  kbs::http::attest] Attest API called.
[2024-09-26T19:33:41Z INFO  attestation_service] Sample Verifier/endorsement check passed.
[2024-09-26T19:33:41Z INFO  attestation_service] Policy check passed.
[2024-09-26T19:33:41Z INFO  attestation_service] Attestation Token (Simple) generated.
[2024-09-26T19:33:41Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /kbs/v0/attest HTTP/1.1" 200 2171 "-" "attestation-agent-kbs-client/0.1.0" 0.002289
[2024-09-26T19:33:41Z WARN  kbs::token::coco] No Trusted Certificate in Config, skip verification of JWK cert of Attestation Token
[2024-09-26T19:33:41Z INFO  kbs::http::resource] Get resource from kbs:///default/image_key/nginx
[2024-09-26T19:33:41Z ERROR kbs::http::error] Resource not permitted.
[2024-09-26T19:33:41Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "GET /kbs/v0/resource/default/image_key/nginx HTTP/1.1" 401 112 "-" "attestation-agent-kbs-client/0.1.0" 0.000556
[2024-09-26T19:33:41Z INFO  kbs::http::attest] Auth API called.
[2024-09-26T19:33:41Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /kbs/v0/auth HTTP/1.1" 200 74 "-" "attestation-agent-kbs-client/0.1.0" 0.000088
[2024-09-26T19:33:41Z INFO  kbs::http::attest] Attest API called.
[2024-09-26T19:33:41Z INFO  attestation_service] Sample Verifier/endorsement check passed.
[2024-09-26T19:33:41Z INFO  attestation_service] Policy check passed.
[2024-09-26T19:33:41Z INFO  attestation_service] Attestation Token (Simple) generated.
[2024-09-26T19:33:41Z INFO  actix_web::middleware::logger] <IP_ADDRESS> "POST /kbs/v0/attest HTTP/1.1" 200 2171 "-" "attestation-agent-kbs-client/0.1.0" 0.001573

But notice the error [2024-09-26T19:33:41Z ERROR kbs::http::error] Resource not permitted. on the logs above. It means that the resource (the encryption key) is disallowed to be fetched. This happen with kata-qemu-coco-dev, where we have to set the "allow all" policy to kbs (please see https://github.com/kata-containers/kata-containers/blob/main/tests/integration/kubernetes/k8s-guest-pull-image-encrypted.bats#L33). Running within a TEE environment (e.g. kata-qemu-tdx) this policy should not be set and it should work as long as attestation is working.
Ok, then I tried to set the "allow all" policy but hit an error, maybe a bug on latest kbs-client:
$ kbs-client --url http://<IP_ADDRESS>:30327 config --auth-private-key trustee/kbs/config/kubernetes/overlays/x86_64/key.bin set-resource-policy --policy-file ./trustee/kbs/sample_policies/allow_all.rego
Error: Parse error

@fitzthum ^ is it a known issue?

is it a known issue?

Yeah. I thought we had fixed this, but we have seen problems parsing the policies in the past. Maybe try randomly changing the format :'(

Yeah. I thought we had fixed this, but we have seen problems parsing the policies in the past. Maybe try randomly changing the format :'(

Actually let me be more clear. I wouldn't expect to run into a parsing problem with that policy in particular and actually I just tested it on my machine and it works fine. We have seen some issues parsing policies in general but not with this file.


verify separator

Verify separator byte value, to ensure that we're indeed at the right position in a valid frame. Otherwise we might mis-detect the start byte (as this could be anywhere in the ciphertext)

Thank you.


Fix handling of receiver and sender task failures

Sender task failures (1955)

Produced result partition becomes erroneous with a ProducerFailedException
Receiver cancels itself when encountering the ProducerFailedException by throwing an instance of CancelTaskException (it may also be cancelled by the JobManager if that call is faster than the detection of the failed producer)
Reference to Netty channel is released

Receiver task failures  (1958)

Sender keeps going. May be back-pressured when no receiver pulls the data any more.
Sender may be cancelled by JobManager
Partition stays sane
Reference to Netty channel is released
Transfer are canceled by a cancel message (receiver to sender)

I would like to merge this by the end of the day to have it in for the release testing.

Merging now.


Update PurchasePromptScript2.lua

Removed ticket support.
Also I had an idea that I would like to run by you guys. When you use PromptProductPurchase(), what if when it pops up we could also have it set so you could move it around the screen?

I will review this in a couple of weeks, once all ticket stuff is settled down and it is safe to completely remove support

Ok.

No longer able to merge.


docs: Add Bomctl chart document to the repo

Description
Adding the charter document to the repo
Type of change

[x] This change is a documentation update

Hi @riaankleinhans, thanks for the PR! Do you mind updating the title of the PR to something like docs: bomctl charter (as long as it starts with docs: and fixes the Bomclt typo). Thanks!

@jhoward-lm you are quick! Fixed the nits.

@riaankleinhans one other thing, your commits appear to be unverified, so I don't believe it will let us merge this PR until it's resolved. You may need to add the GPG/SSH key that was used to your GitHub profile, or configure your local git client to sign the commits.
If the local git client is the issue, you may need to re-write the history and re-push the commit. I'd recommend something like this to reset your branch's head back to main but keep your changes, then re-commit with a new squashed commit of your changes, then push again.
git reset --mixed origin/main
git add docs/charter.md
git commit --sign-off --message="add charter document"
git push --force-with-lease

Sorry if the commands are incorrect, I don't use the git CLI directly all that much, but that's the general idea 😄
One other tiny nit but I won't hold up the PR for it, and it's my fault for providing bad info in the first place, but I think this
**Adopted August 5, 2024** <!-- markdownlint-disable-line -->

would be preferable instead of the global <!-- markdownlint-disable --> I originally suggested


Added two new GraphicsOverlay samples in WinDesktop to match the Xamarin versions.

@anttikajanus please code review for inclusion into the WinDesktop samples. These two samples (AddGraphicsRenderer and IdentifyGraphics) match what is in the Xamarin repo.

@dkemlage Reviewed. Nice work. Couple very small things and feel free to merge when ready.


"LOCATION_CHANGE" dispatch twice

When I use a hashHistory, LOCATION_CHANGE will dispatch twice.
example:
user/xxx => user/xxx/#

i think the following code causes it
  if (history.getCurrentLocation) {
    handleLocationChange(history.getCurrentLocation())
  }

https://github.com/reactjs/react-router-redux/issues/570#issuecomment-297783172


Pass contextPath to settings.cometOnSessionLost

Missing bit to complete #1903.

Lol! How did I miss this?
@VlachJosef Thanks for spotting my miss. Can you please add your name to CONTRIBUTORS.md before I merge this so we make sure you get credit?

@farmdawgnation done.


Write a decent "How to contribute guide"

We should have a clear guide for developers on how to contribute to the project. This should detail how to set-up jekyll for local development as well as any guidelines wrt pull requests.

@alirazabhayani since you have gone through the process of setting everything up last, can you get something going please?


Run C++ tests on FreeBSD

#560 adds FreeBSD running on Cirrus CI. That CI doesn't run C++ tests at the moment because:

some tests for ConfigPaths fail;
ConfigPaths is being rewritten into Rust (#413), so it's better to fix that PR rather than the C++ code it replaces.

Once #413 is merged, we need to make sure the C++ tests work on FreeBSD, and run them on Cirrus CI.

I created a virtual machine with FreeBSD 12.0, checked out current master (https://github.com/newsboat/newsboat/commit/4edd2ffebe6949f8f61167d060ebee60d79d6f9f), and:

tests fail when ran under superuser;
tests succeed when run from under unprivileged user.

We aren't the first ones to run into this; cf. https://github.com/cirruslabs/cirrus-ci-docs/issues/299. The solution is to create a new, unprivileged user, and run everything from under it. PR to that effect forthcoming.


Monitoring system (like alerta) using svelte and gedis

Create alerta package with the following requirements

Actor (alerta)

[x] list alerts information from BCDB (list_alerts)
[x] list alerts by environment information from BCDB (list_alerts)
[x] create alert information from BCDB (new_alert)

UI using svelte

[x] Listing alerts
[x] Suitable filters

Along with documentation on covering the following

[x] Creating/initializing the application
[x] Creating components
[x] Routing between components
[x] Interaction with websockets (gedis websocket client)
[x] Add deployment instructions

Documentation

[x] How to create the package
[x] How to register the website on threebot
[x] How to create the actor and how to communicate with BCDB models and sending it back on the websocket

https://github.com/threefoldtech/jumpscaleX_threebot/tree/development/ThreeBotPackages/alerta

verified on branch development_web_alerta for only jumpscaleX_threebot repo and other repos on development :
alerta installation OK
listing alerts from UI and from BCDB OK
search content from UI OK
create alert from BCDB OK


Archive or delete this repository

There is already duplicate repository in
https://github.com/sympy/rubi

This one has a better README. Otherwise is there any reason to prefer one or the other? Nether preserves the git history which could be done.


New version: AuraSide.Mantle version <IP_ADDRESS>

- [X] Have you signed the Contributor License Agreement?

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.5 schema?

Microsoft Reviewers: Open in CodeFlow

Hi @Trenly,

This PR's version number 1.0.5 has 3 parameters (sets of numbers between dots - major, minor, etc), which is less than the current manifest's version <IP_ADDRESS>, which has 4 parameters.

Is this intentional?
(Automated response - build 643)

Yes

I'm going to start an exception file for these. Let me know if this or any other should be added to it.

I'm going to start an exception file for these. Let me know if this or any other should be added to it.

I don’t think its really that there are exeptions, since it is true that these versions don’t follow the same pattern as previous versions. It's moreso that the version written to control panel has changed and also doesn’t follow the pattern. I don’t know if it's possible (easy) for you to capture the ARP entries from the logs or your own installs, but genrally I would say that if the version matches control panel, changing the number of parameters is intentional


Status Bar Improvement Suggestions

Hi, I noticed that the status bar at the very bottom of the vs2022 dark theme is grey instead of blue (this is a place where it's more consistent compared to vs2019, which I like), can you modify this plugin to support this a little

If only the blue colors were purple.