about,Dialog add button

I added a button in a dialog box, and it can work properly, but there is no way the same as the original button to refresh the data corresponding to the Grid, and how to achieve refresh Grid

In dialog,
Serenity.SubDialogHelper.triggerDataChange(this.element);

Hope this is not a stupid question, I do not know where to write this code, my code is this.
` protected getToolbarButtons() {
var buttons = super.getToolbarButtons();
        buttons.push({
            title: '\u6587\u7ae0\u4e0b\u67b6\u0028\u4e0b\u67b6\u540e\u8981\u5237\u65b0\u9875\u9762\uff01\u0029',
            cssClass: 'send-button',
            onClick: () => {

                var action = new ArticleReportOffBulkAction();
                var ss: string[] = [this.entity.Id.toString()];

                action.done = () => { Serenity.SubDialogHelper.triggerDataChange(this.element); }
                action.execute(ss);
                //this.dialogClose();
               // Serenity.SubDialogHelper.triggerDataChange(this.element);
            }
        });

        return buttons;
    }`

Emergence of this issue: Can not read property 'triggerHandler' of undefined,

Try with triggerDataChange(this). It's probably Saltaralle generic to typescript issue.

perfect! I succeed !  thank !thank!than! you


Overload ApplicationErrorJdbc#migrateDatabase to accept a migration file name

Overload migrateDatabase with a migrations file name:
public static void migrateDatabase(Connection conn, String migrationsFilename)

Since this is so minor, I am not bothering with a minor version and just leaving the milestone as-is ( 2.1.1 )


We should not be using camel casing rules in comments/javadocs when referring to acronyms

A comment or Javadoc is just English text, so the acronym naming recommendations that otherwise apply to code (Dns instead of DNS, etc) should not be followed there.
Instead it should be just the way it is named: DNS, ID, FQDN, IP, MAC, etc.
It'd be good to do a scrub across the board.

fixed in beta2 with global replace in PR: https://github.com/Azure/azure-sdk-for-java/pull/901
It'd be good to have some sort of a checkstyle rule though -- looking for these patterns in comments and Javadocs (case sensitive) " Ip ", " Dns ", " Fqdn " at least.

This will be overwritten by auto-generation if we auto-generate the interfaces. The correct solution is to fix in Swagger specs.


Printf format problem in error message

Bug report
General Information

Cilium 1.6.0
Debian buster, Linux 4.19.0-5-amd64
Kubernetes 1.15.3

root@kc1b:~# kubectl get --all-namespaces no -o wide
NAME   STATUS   ROLES    AGE     VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                       KERNEL-VERSION   CONTAINER-RUNTIME
kc1b   Ready    master   9d      v1.15.3   <IP_ADDRESS>     <none>        Debian GNU/Linux 10 (buster)   4.19.0-5-amd64   containerd://1.2.7
kc2b   Ready    master   9d      v1.15.3   <IP_ADDRESS>     <none>        Debian GNU/Linux 10 (buster)   4.19.0-5-amd64   containerd://1.2.7
kc3b   Ready    master   9d      v1.15.3   <IP_ADDRESS>     <none>        Debian GNU/Linux 10 (buster)   4.19.0-5-amd64   containerd://1.2.7
kw1b   Ready    <none>   8d      v1.15.3   <IP_ADDRESS>     <none>        Debian GNU/Linux 10 (buster)   4.19.0-5-amd64   containerd://1.2.7
kw2b   Ready    <none>   7d10h   v1.15.3   <IP_ADDRESS>     <none>        Debian GNU/Linux 10 (buster)   4.19.0-5-amd64   containerd://1.2.7
kw3b   Ready    <none>   8d      v1.15.3   <IP_ADDRESS>     <none>        Debian GNU/Linux 10 (buster)   4.19.0-5-amd64   containerd://1.2.7

How to reproduce the issue

Used kubeadm to create 6 node 1.15.3 cluster (3 control, 3 workers)
installed Cilium 1.6.0
installed MetalLB in BGP mode
went to deploy first service (moving things by hand from an old Kubernetes cluster)
noticed it was failing to start.
kubectl described the pod; saw:

unable to connect to Cilium daemon: failed to create cilium agent client after 30.000000 seconds timeout: Get http://%!F(MISSING)var%!F(MISSING)run%!F(MISSING)cilium%!F(MISSING)cilium.sock/v1/config: dial unix /var/run/cilium/cilium.sock: connect: no such file or directory

I probably have something misconfigured, so this bug report is solely about that fmt.Printf format/argument mismatch.
Looks like perhaps the /var/run/cilium/cilium.sock path is URL encoded and then concatenated into a fmt.Printf pattern where fmt interprets the URL encoding as %F variables.
But the "Get " part is part of a Go *net/url.Error message, so you must be trying to http.Get the bogus URL and the fmt.Printf comes before that? I haven't looked at the code yet.
Just filing this now before I forget.

The printf format problem remains.


⚠ ClamAV has degraded performance

In dffe982, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 778 ms

Resolved: ClamAV performance has improved in a5a7990.


Move snappy-java version to dependencyManagement

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify.
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @dhalperi peeled off this trivial bit from my more quixotic shading PR. I believe you had commented on this at one point.

Coverage decreased (-0.01%) to 70.657% when pulling c7bd2b43ddf726248291a653f8d7d796a51800a0 on kennknowles:snappy-version into ce00d2466a9495f4eb262b5f7d2afec5788fcfe2 on apache:master.


[Bug] Update README

Describe the bug
README is no longer current
To Reproduce
N/A
Expected behavior
Current instructions for development and deploying

i am wokring one most of the issues

saw the app when i am trying to run i am getting error
(bookwrms_env) PS D:\Desktop\satya\projects\Open Source\BOOKWRMS> flask --app flaskr init-db
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in run_code
File "D:\Desktop\satya\projects\Open Source\BOOKWRMS\bookwrms_env\Scripts\flask.exe_main.py", line 7, in
File "D:\Desktop\satya\projects\Open Source\BOOKWRMS\bookwrms_env\Lib\site-packages\flask\cli.py", line 1064, in main
cli.main()
File "D:\Desktop\satya\projects\Open Source\BOOKWRMS\bookwrms_env\Lib\site-packages\click\core.py", line 1078, in main
rv = self.invoke(ctx)
^^^^^^^^^^^^^^^^
File "D:\Desktop\satya\projects\Open Source\BOOKWRMS\bookwrms_env\Lib\site-packages\click\core.py", line 1688, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\Desktop\satya\projects\Open Source\BOOKWRMS\bookwrms_env\Lib\site-packages\click\core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\Desktop\satya\projects\Open Source\BOOKWRMS\bookwrms_env\Lib\site-packages\click\core.py", line 783, in invoke
return __callback(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\Desktop\satya\projects\Open Source\BOOKWRMS\flaskr\data_store\db.py", line 67, in init_db_command
init_db()
File "D:\Desktop\satya\projects\Open Source\BOOKWRMS\flaskr\data_store\db.py", line 50, in init_db
db = get_db()
^^^^^^^^
File "D:\Desktop\satya\projects\Open Source\BOOKWRMS\flaskr\data_store\db.py", line 18, in get_db
dbname=os.environ["READ_DB_NAME"],
~~~~~~~~~~^^^^^^^^^^^^^^^^
File "", line 679, in getitem
KeyError: 'READ_DB_NAME'

i do know why error we are getting but it would be helpfull if tell where would we get these ids

Those are from the postgres DB that is used. It used to have a sqlite file as a local DB but recently it was changed to use a postgres DB. That will come from setting up a local postgres dev DB


Ts Worker Failing

Since not so long the TS worker fails after several seconds after opening Atom and never starts again ;( This is message in the log:
/Users/tomi/.atom/packages/typescript-modules-helper/lib/typescript-import.coffee:44 bound event

/Users/tomi/.atom/packages/atom-typescript/dist/worker/lib/workerLib.js:193 ts worker restarting. Don't know why it stopped with code: null

I noticed another error related to this:

/Users/tomi/.atom/packages/atom-typescript/dist/worker/lib/workerLib.js:180 CHILD ERR STDERR: Atom Helper(63023,0x7fff74876000) malloc: *** error for object 0x7f923840ce20: pointer being freed was not allocated

which every 3-6 minutes.

ouch. Does trying an older version (try a month old version) fix it ... if not then it might be a new atom version bug

Did anyone else report this behaviour?

No. And its running fine all day on my windows machine

Rolled back to Atom 1.1.0 and so far all looks good. Looks like Atom issue ;(

I am having this issue on 1.2.1, can't rollback to 1.1 currently

@JoshEngebretson  are you on a Mac ?

Yes, OSX 10.11

@JoshEngebretson is pointer being freed was not allocated in your console too?

@basarat I'm on Mac as well.

Here is what I am seeing:

facing the same issue

I've created an issue : https://github.com/atom/atom/issues/9663 :rose:

I can confirm that with Atom 1.3.0 beta all is OK.

I'm getting this issue on XUbuntu. I'm using 1.1.0. I'll see if I can figure out how to upgrade to 1.3.0.

Don't seem to be having any issues with 1.3.0 beta

Atom 1.30 beta fixed this for me as well

I think we can close this one as all seems to be well with Atom 1.3.+


First attempt at implementing elseif - RFC

Here's an attempt at implementing elseif support per #1629.
Parsing
It adds another blessed reference, elseif(). If one is encountered while processing a section, the function is stripped off and the remaining expression is stashed along with the following nodes for processing in _parse cleanup. In cleanup, upon encountering a section with an l (now an array), is split into conditional mustaches using the stashed expression, or just a true expression for plain elses. The number of siblings is also stored in the primary mustache in a new b attribute.
Fragment creation
If a node with a b is encountered when creating Fragments, it and its siblings are passed a flag to notify them that they have siblings. Once all of the fragments are created, the ones with siblings are gathered up and given references to their sibling collection. Sections with siblings don't evaluate initially and wait for a task to be executed after the current turn of the event loop. The same happens when one of the siblings gets a new value. There is no caching yet, so each time, all of the siblings are reevaluated.
Syntax
Since, elseif is a function, it does require the parens, which I prefer, but that may not be what everyone likes. To me, it looks pretty good though:
{{#if foo}}
  foo is true
{{ elseif (bar) }}
  foo is false, bar is true
{{ elseif (baz || bat || check('ok')) }}
  yeah
{{ else }}
  ok
{{/if}}

Also, it was waaay less fiddly than special-casing elseif or else if in the parser. I also considered elsif, elif, and accepting all three. For stuck together else if clauses, I actually prefer the elsif from Ruby.
Status
Currently, all of the tests pass except those that expect the old parse trees to come out of the parser. I only have two very simple tests for elseif, with more pending feedback.
So, is the extra complexity worth the functionality provided?  Would you prefer special-cased syntax in the parser?

X-posting my comment on the syntax.
===
Reading back over your comment @evs-chris, I realized I view 'if' blocks like this conceptually:
{{#if}} // we're starting an if block, start checking for 'ifs'
{{ if cond1 }} // test for first condition
{{ elseif cond2 }} // else test for second condition
{{ elseif cond3 }} // else test for third condition
{{ else }} // else default condition
{{ endif }}
{{/if}} // end the if block, stop checking for 'ifs'

If you scrunch the starting and ending condition into the block delimiters, you end up with this:
{{#if cond1 }} // we're starting an if block
{{ elseif cond2 }} // else test for second condition
{{ elseif cond3 }} // else test for third condition
{{ else }} // else default condition
{{/if}} // we're ending the if block

Which I think is a pretty pretty way to show it.

Turns out special casing is easier than I thought it would be:
index b9303bd..29fc5c0 100644
--- a/src/parse/Parser/expressions/memberOrInvocation.js
+++ b/src/parse/Parser/expressions/memberOrInvocation.js
@@ -24,13 +24,13 @@ export default function ( parser ) {
                        };
                }

-               else if ( parser.matchString( '(' ) ) {
+               else if ( parser.matchString( '(' ) || expression.n === 'elseif' ) {
                        parser.allowWhitespace();
                        expressionList = getExpressionList( parser );

                        parser.allowWhitespace();

-                       if ( !parser.matchString( ')' ) ) {
+                       if ( !parser.matchString( ')' ) && expression.n !== 'elseif' ) {
                                parser.error( expectedParen );
                        }

diff --git a/src/parse/Parser/expressions/primary/reference.js b/src/parse/Parser/expressions/primary/reference.js
index d57a83f..800a03a 100644
--- a/src/parse/Parser/expressions/primary/reference.js
+++ b/src/parse/Parser/expressions/primary/reference.js
@@ -46,7 +46,11 @@ export default function ( parser ) {
        }

        pattern = parser.relaxedNames ? relaxedName : namePattern;
-       name = parser.matchPattern( /^@(?:keypath|index|key)/ ) || parser.matchPattern( pattern ) || '';
+       name = parser.matchString( 'else if' ) || parser.matchPattern( /^@(?:keypath|index|key)/ ) || parser.matchPattern( pattern ) || '';
+
+       if ( name === 'else if' ) {
+               name = 'elseif';
+       }

        // bug out if it's a keyword (exception for ancestor/restricted refs - see https://github.com/ractivejs/ractive/issues/1497)
        if ( !parser.relaxedNames && !dot && !ancestor && keywords.test( name ) ) {

To be clear, that patch allows any of
{{#if foo}}
{{ elseif (bar) }}
{{ elseif baz }}
{{ else if bat }}
{{/if}}

Also, I didn't mention it in the first post, but this also works with other sections in a way that should be expected if you've used {{else}} with {{#with}} or {{#each}}. It also works with implicit condition and iteration e.g.
{{#foo}}
{{ else if bar }}
{{/}}

:+1:

Nice. :+1:

:+1:

I believe this would call for a template version bump, right?

I believe this would call for a template version bump, right?

Yes, but it's backward compatible so it shouldn't throw an error.

I have bumped the version and created a PR for the template-spec. I think this is good to go if @martypdx and @Rich-Harris approve. I'm in the midst of a big project with an impending deadline and wanted to shore this up before I disappear for a while longer.

After a bit of pondering, would it make more sense to have another node type as a container for linked siblings?
{ t: 19, f: [{ t: 4, r: 'foo', f: ['...'] }, { t: 4, x: { r: ['bar'], s: '_1!==10' } }] }

I don't think it would really change the complexity of the logic because those sections still have to have a slightly deferred init process. Looking at both, I still prefer the current sibling count version, but I thought I'd ask.

This is bloody impressive stuff. I reckon it'd be better to choose between elseif and else if and stick to it (I'd vote for elseif personally, since every other 'special' reference is a single word), even if it initially seems harmless to be more relaxed - allowing both will probably mean documentation and examples get fragmented and add to a general sense of confusion.
The deferred init stuff makes me slightly nervous - is there any mileage in rewriting blocks during post-parse cleanup in the same way as standard if...else? I.e.
{{#if foo}}
  <!-- foo -->
{{elseif bar}}
  <!-- bar -->
{{elseif baz}}
  <!-- baz -->
{{else}}
  <!-- qux -->
{{/if}}

<!-- becomes as though we'd done... -->

{{#if foo}}
  <!-- foo -->
{{/if}}
{{#if !foo && bar}}
  <!-- bar -->
{{/if}}
{{#if !foo && !bar && baz}}
  <!-- baz -->
{{/if}}
{{#if !foo && !bar && !baz}}
  <!-- qux -->
{{/if}}

It adds some upfront complexity but skirts around the requirement for sections to know about their siblings - less that can go wrong at render time. @evs-chris if that sounds sane, am happy to jump in and have a crack at it, or if you'd rather I keep my mitts out/already tried and rejected this approach then that's fine too

I'd vote for elseif personally, since every other 'special' reference is a single word

:+1:

<!-- becomes as though we'd done... -->

Actually it's more complicated, turtles all the way down:
{{#if foo}}
  <!-- foo -->
{{else}}
    {{#if !foo && bar}}
      <!-- bar -->
    {{else}}
        {{#if !foo && !bar && baz}}
          <!-- baz -->
        {{else}}
            {{#if !foo && !bar && !baz}}
             <!-- qux -->
            {{/if}}
        {{/if}}
    {{/if}}
{{/if}}

However we implement, I think the key is to avoid unnecessary re-rendering of branches that don't logically change.

I'd vote for elseif personally, since every other 'special' reference is a single word

Sounds good to me. I was shooting for least surprise when I added the spacey version.

The deferred init stuff makes me slightly nervous - is there any mileage in rewriting blocks during post-parse cleanup in the same way as standard if...else?

I looked at that initially, but it looked like complex conditionals would get really ugly really fast. (As @martypdx commented whilst I was typing this)

if that sounds sane, am happy to jump in and have a crack at it

You are more than welcome to have a crack at it!

I merged the latest conditional attribute fix and got those working with elseif as well. Was there a reason that each template chunk in a template.m array was handled separately? I merged them all together and no tests failed, but I don't know if that's copacetic. I suppose it will be moot if @Rich-Harris wrangles multiple branches into a something less complicated than this.
I also didn't realize that and empty object {} was considered false for conditionals, as it is true for plain js. So the code in this PR now behaves accordingly.

Also, removed support for else if.

Closing this in favor of the much nicer #1676.


question about TEEU architecture

I studied the following demo in TEEU documentation:
import numpy as np

def average(data):
    return np.average(data, axis=1)

alice = sf.PYU('alice')
bob = sf.PYU('bob')

from secretflow.device import TEEU

# mrenclave can be omitted in simulation mode.
teeu = TEEU('carol', mr_enclave='')

a = alice(lambda: np.random.rand(4, 3))()
b = bob(lambda: np.random.rand(4, 3))()

# Transfer data to teeu.
a_teeu = a.to(teeu, allow_funcs=average)
b_teeu = b.to(teeu, allow_funcs=average)

# TEEU runs average.
avg_val = teeu(average)([a_teeu, b_teeu])
print(sf.reveal(avg_val))

a = sf.reveal(a)
b = sf.reveal(b)
np.testing.assert_equal(avg_val, average([a, b]) )

My question is that when alice and bob said that average is allow_funcs, there is a mechanism to prove that average is the function defined here, right?
In this demo, the function is defined locally. But in a real-world application, how can alice and bob ensure the functions allowed are safe functions? Does the authorization manager (carol) make this promise?
What if the project is barely between alice and bob (which is true in most cases) and there is no carol at all?

@zhouaihui could you please have a look?

From other tutorials, I found that users believe there is a copy of the codes in each party: every one of Alice, Bob, and Carol defines the same average in their local codebase.
If this is the case, my question is what if the code is close sourced?
In many cases, one of Alice and Bob, say, Alice, is the data holder, while the other is the codebase holder. On the one hand, Alice won't let Bob see his data, on the other hand, Bob won't let Alice see his codebase, and there is no Carol. How should we utilize TEEU then?

I studied the following demo in TEEU documentation:
import numpy as np

def average(data):
    return np.average(data, axis=1)

alice = sf.PYU('alice')
bob = sf.PYU('bob')

from secretflow.device import TEEU

# mrenclave can be omitted in simulation mode.
teeu = TEEU('carol', mr_enclave='')

a = alice(lambda: np.random.rand(4, 3))()
b = bob(lambda: np.random.rand(4, 3))()

# Transfer data to teeu.
a_teeu = a.to(teeu, allow_funcs=average)
b_teeu = b.to(teeu, allow_funcs=average)

# TEEU runs average.
avg_val = teeu(average)([a_teeu, b_teeu])
print(sf.reveal(avg_val))

a = sf.reveal(a)
b = sf.reveal(b)
np.testing.assert_equal(avg_val, average([a, b]) )

My question is that when alice and bob said that average is allow_funcs, there is a mechanism to prove that average is the function defined here, right? In this demo, the function is defined locally. But in a real-world application, how can alice and bob ensure the functions allowed are safe functions? Does the authorization manager (carol) make this promise? What if the project is barely between alice and bob (which is true in most cases) and there is no carol at all?

Now that secretflow suggests using multi-controller mode in production usage, the function you allowed is defined locally. This means the functions executed in TEE are limited by you locally.

how can alice and bob ensure the functions allowed are safe functions
In practice, whether the functions are safe or not depends on your algorithm design (You need to decide what can be output/revealed, just as what you do in designing which part should be protected by holomorphic encryption in federated learning.) TEEU only provides a mechanism that you could dynamically extend what can be executed and all this tradeoff must be agreed by all parties. Then all the details such as remote attestations and dynamic behavior will be handled automatically by the TEEU framework.

What if the project is barely between alice and bob (which is true in most cases) and there is no carol at all?
For the second question, TEE does not really care where it is located. As the TEE has a remote attestation mechanism, the data provider does not have to trust humans(in this demo, Carol). It is ok to just put the TEE machine in Alice or Bob.

It depends.
If the data providers have to perform remote attestation to check how my data will be used, then close source codes do not make sense here. You always have to open-source your codes to the data providers for them to verify your mrenclave, which implies code hash.
However, there are some cases that close source works. Say Alice provides the input, whereas Bob provides the functions, and Bob wants to protect the function. Say the function is a SQL statement, it is ok for Bob to hide the SQL query in certain conditions.

The SQL output will only be opened to Alice, say all the SQL outputs will be encrypted by Alice's key. And this part of the mechanism can be checked by remote attestation.
Bob could dynamically execute his private(close source) SQL queries. Without having access to the output.  he cannot perform valid attacks.

This kind of feature will be supported in future  TEE  releases. Let me know if this is an important scenario.

yes, I think this is more close to our scenario than the demo, I'm looking forward to it.

Thanks for your suggestion, we will take it into consideration for future support.

After all, Gramine + Intel SGX may not be accepted in the future due to reasons you know why.

Yea, we are attempting to run our codes on Hygon CSV. Stay tuned!


How do I launch the bot correctly?

I have a chat with a bot. I launched it. I blocked the bot on another client. I call sendBotStartMessage, it sends a message with the contents of /start, but the bot does not start.

Thx) It worked for me.


Mergify: configuration update

This change has been made by @ivan-015 from https://mergify.io config editor.

This PR will ensure that copied PRs made by mergify can be merged automatically


Live crashes the plugin

Greetings,
With all the "fun news" going on in the world right now, I've had a lot more events/people begin live streaming over Vimeo. I've never used Vimeo much before, but I use Kodi near daily. When I found this plugin I was super ecstatic to watch on my big screen instead of my laptop. Works perfectly for all the pre-recorded videos that I've watched. Fails every time when I try to watch any live stream. This morning I asked a buddy who has a Vimeo premium account if he'd do some testing with me. Before he started a live stream, I could search for his account and watch any of his videos. As soon as he started a live stream it crashed, and it crashed every time I tried to look at his channel no matter how I did it. The moment he stopped his live stream, I could view his videos again.
According to Kodi, I've got the latest version of the plugin. I only have Raspberry Pi4's (4Gb memory versions) running Libreelec (latest version) to test Kodi on right now: LibreELEC (official): 9.2.1 (RPi4.arm)
The most informative error that I could find (also almost identical every time it crashes) is:
2020-03-29 09:46:07.908 T:2451551088   ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the follow
ing error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <type 'exceptions.RuntimeError'>
                                            Error Contents: Could not convert JSON kind to model...
                                            Traceback (most recent call last):
                                              File "/storage/.kodi/addons/plugin.video.vimeo/addon.py", line 3, in <module>
                                                plugin.run()
                                              File "/storage/.kodi/addons/plugin.video.vimeo/resources/plugin.py", line 95, in run
                                                search(handle, query)
                                              File "/storage/.kodi/addons/plugin.video.vimeo/resources/plugin.py", line 144, in searc
h
                                                collection = listItems.from_collection(api.search(query, "videos"))
                                              File "/storage/.kodi/addons/plugin.video.vimeo/resources/lib/vimeo/api.py", line 99, in
 search
                                                return self._map_json_to_collection(res)
                                              File "/storage/.kodi/addons/plugin.video.vimeo/resources/lib/vimeo/api.py", line 218, i
n _map_json_to_collection
                                                raise RuntimeError("Could not convert JSON kind to model...")
                                            RuntimeError: Could not convert JSON kind to model...
                                            -->End of Python script error report<--
2020-03-29 09:46:07.971 T:2468336496   ERROR: GetDirectory - Error getting plugin://plugin.video.vimeo/<private link>
2020-03-29 09:46:07.983 T:3011697120   ERROR: CGUIMediaWindow::GetDirectory(plugin://plugin.video.vimeo/<private link>)
 failed

I didn't see anyone else reporting this problem. If you have another stream you want me to test on, please let me know. I can also try bumping up all the debugging options too if it helps.
Thanks!

Thanks for reporting the issue. I didn't even know Vimeo supported live streaming. I'll look into it. :+1:

@cstackpole I submitted the patch to the repository: https://github.com/xbmc/repo-plugins/pull/2795
This can take a while.

Whoa! I wasn't expecting a patch this fast. You are awesome. Thank you very much!


Follower Readiness Probe

Is your feature request related to a problem? Please describe.
We use Tile38 in kubernetes and autoscale the followers as need be. This works like a charm, until it doesn’t.
My problem currently is the readinessProbe for the followers. If a follower receives traffic,
before it is caught up, it errors out. It hasn’t been an issue, but the more data
we process the longer the new followers take to catch up to the leader, obviously.
A solution is something that is described here. But under no circumstance do I want to maintain a custom image alongside your image and execute python scripts in the readinessProbe.
Describe the solution you'd like
If I wanted to stick to the image you provide, I would have to do something like:
livenessProbe:
  exec:
    command: ["sh", "-c", "wget http://follower-url/server -O - | grep -e '\"caught_up\":true' > /dev/null && exit 0 || ext 1"]
  initialDelaySeconds: 60

This will work as long as I do not screw up the url for wget.
Kubernetes also provides a readinessProbe with httpGet that would make this a little safer.
If followers were to return 200 on an endpoint only if "caught_up": true,then Kubernetes could poll that endpoint
for a given period. If the error code is <400 Kubernetes would start to route request to it.
readinessProbe:
  httpGet:
    scheme: HTTP
    path: /healthz
    port: 9851
  initialDelaySeconds: 60

Something similar can be done in docker-compose also with the use of dokku/wait.
Do you think it would make sense to include this in Tile38 and if so, can I give it a try? :)
Edit: /healthz would be better, agreed @stevelacy

(note: I'm the author of that post)
In my case I was wanting to check a specific metric num_objects, you would be just needing the state of the follower to be "caught up".
I would suggest a standard /healthz path, with 200 for online/ready and 500 when not.

Makes sense to me.

See PR #609.

I just pushed a new release that adds the new HEALTHZ command.

So today I got along to test this out, but failed miserably. I should've tested it locally first I guess. :)
Now I got along to test it locally with this docker-compose.yml
version: "3"

services:
  tile38-leader:
    image: tile38/tile38:1.24.2
    container_name: tile38-leader
    command: tile38-server -vv -p 9851
    ports:
      - 9851:9851

  tile38-follower:
    image: tile38/tile38:1.24.2
    container_name: tile38-follower
    command: >
      /bin/sh -c 'mkdir -p tmp/data && \
                  echo "{\"follow_host\": \"tile38-leader\",\"follow_port\":9851}" > tmp/data/config
                  tile38-server -d tmp/data -vv -p 9852'
    ports:
      - 9852:9852

The logs tell me:
tile38-follower    | 2021/06/09 14:11:48 [INFO] caught up

But HEALTHZ returns
// follower
curl http://localhost:9852/HEALTHZ
>> {"ok":false,"err":"not caught up","elapsed":"170.2µs"}

// leader
curl http://localhost:9851/HEALTHZ
>> {"ok":true,"elapsed":"170.2µs"}

Am I missing something here?

tested, worked. thanks alot! 👍 🚀

You're welcome :)


 The service could be something like:
sudo /etc/init.d/fatjar start

Done.

Also see - https://github.com/camel-labs/camel-labs/tree/master/iot#installing-gateway-on-the-rasbian .


fix(#282): RSR-748 Remove dependency to compas-core.scl2007b4

What is the reason for this change?

Hello,
Compas-SCT uses compas-scl-xsd to get the XSD file for SCL2007B4, and compas-core.scl-extension to get the XSD file for Compas Privates (SCL_CoMPAS.xsd).
Compas-SCT doesn't use compas-core.scl2007b4 package (I think it never did). This Pull Request is a cleanup task.

Hello,
Compas-SCT uses compas-scl-xsd to get the XSD file for SCL2007B4, and compas-core.scl-extension to get the XSD file for Compas Privates (SCL_CoMPAS.xsd). Compas-SCT doesn't use compas-core.scl2007b4 package (I think it never did). This Pull Request is a cleanup task.

@massifben
I think we need this mapping, it is only specified in compas-core.scl2007b4
<jxb:bindings version="1.0"
 .....
    <jxb:bindings schemaLocation="../../../target/xsd/SCL2007B4/SCL.xsd" node="/xs:schema">
        <namespace:prefix name=""/>
        <namespace:prefix name="compas" namespaceURI="https://www.lfenergy.org/compas/extension/v1"/>
    </jxb:bindings>
</jxb:bindings>

https://github.com/com-pas/compas-core/blob/develop/scl2007b4/src/main/bindings/scl2007b4.xjb#L13


Update README.md and fixes Issue #1

Fixed issue #1

The admin email and password were both incorrect in the readme. After querying the database for the actual email and using the same password cadence as the other readme, admin12345! was the correct password.
Without knowing how to log into the admin half of this project would not be usable.

thank you.

No problem!


Show all markers on list

@anniemeng can you look into why the deploy failed? also consider adding us all to the heroku app

It's because it needs the updated config parameters from flask base which we're merging in on the PR you had of flask-base changes


Closes: #1 Actualizar repositorio

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

S epresenta nuevamente error


ci(check links) check for broken links

Streamlined the build / install / develop to utilize Make. Made the CI process more agnostic so it's easily reproduced elsewhere (locally or alternative CI options). Setup a link checker

Blocked by #1481

Update for this ticket - This commit now fixes make develop, and install the broken-link-checker which I've confirmed works.
The only thing broken is the travis.yml tests @hutchic if you have any free cycles to assist


Update binary installation procedure

Issue #, if available:
The methods demonstrating who to install eksctl, eksctl-anywhere, and kubectl were not following best-practice.
Description of changes:
I am mirroring the process called out in another page:
https://anywhere.eks.amazonaws.com/docs/getting-started/install/
Testing (if applicable):
N/A - following other examples.
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing as these changes have been merged in #7252.

/close


ERROR: the first paragraph might render incorrectly. line between the level 1 heading and the abstract tag not found in the following files:

This test has a bug and returns inconsistent results.
Levi confirmed to improve it

Issue resolved with 2e15943f789fbc3c1bc3d08e772f71c31dbd6802


I cant see the trading chart

https://gyazo.com/4bcb667a6835329284ae4871e9c26e77
Anyone knows why my trading chart doesnt work?

Everything else works perfect, only chart that doesnt work....

@3s3s


New module for associating files with phrases - assocfile

Based on "associate" module, lets associate files like images or videos
to be sent into a chat with phrases. It's looking for files inside
"files" folder in Kassy's main directory.

@p0358 our long term plan is to move all the modules out into their own git repositories so they can be kpm installed. There are a few options here: we can merge this in to the project and move it out later with the rest of the ones that are still in there (there are a number which arn't), create a new repository under the https://github.com/concierge organisation for it (where we intend to move the modules to) or you can maintain a personal repository for it.
Which would you prefer?

Yes, I was testing it even additionally now and...
It didn't want to send files with sendFile to Facebook, sendImage works for video and audio files as well, but it didn't work for text file I tried to send for some reason... Additionally corrected some messages output.
I will update exports after I see how it was done in the "associate", because something didn't want to work after I tried, so I gave up.
We can can merge this in to the project for now and move it out later with the rest of the ones that are still in there.
I think KPM modules list should be linked somewhere in main readme.

Approved. Will require changes for Hubot in future anyway so it is easier to do that in the hubot branch at the same time as everything else.


Refactor the mutation out of handleChatToGPT()

Here's the call tree and what each method mutates. What the methods should do is return relevant stuff and the mutation should happen (to the res and req objects) back in the chatController. Good luck!

handleChatToGPT() declares then mutates chatResponse

handleChatError() mutates chatResponse, res
handleLowLevelChat() mutates chatResponse

chatGptSendMessage() mutates chatResponse

pushCompletionToHistory() mutates chatHistory
getFinalReplyAfterAllToolCalls() calls pushCompletionToHistory()

chatGptChatCompletion() mutates chatHistory and chatResponse (sets openAIErrorMessage)
performToolCalls() mutates chatResponse (sets wonLevel and defenceReport), calls pushCompletionToHistory()

chatGptCallFunction() mutates sentEmails, declares then mutates reply: ChatCompletionMessageParam

applyOutputFilterDefence() mutates chatResponse (updates defenceReport)

handleHigherLevelChat() mutates chatReponse (lots), mutates req.session.levelState[currentLevel].chatHistory in several places, calls chatGptSendMessage()
handleErrorGettingReply() calls handleChatError(), mutates req (adds error to history)

AC:
No functional change. Regression test only

Do this after #704 to avoid stepping on toes

this ticket came out of #390

@kclark-scottlogic  I remember saying this one comes under dev test. I'm happy with that. @chriswilty  mentioned doing some exploratory testing, which I can imagine might be beneficial, but any regressions will be real subtle and hard to check (like, we want to know when the chat history and email list get updated in the backend, specifically when messages are blocked or we fail to get a reply from chatGPT)


Split repo: (1) OMOP->FHIR, (2) OMOP->OWL, (3) N3C OMOP ingest

Overview
Split repo:
(1) OMOP->FHIR
(2) OMOP->OWL
(3) N3C OMOP ingest
Most of the code in here applies to (2) and needs to be moved out into a new package, then imported here. Then, a repo needs to be created for (1) which will also import (2).
Related

https://github.com/HOT-Ecosystem/hapi-issues/issues/104

Completed.


Jit

Adds, in backends/decorators.py, a tn.jit function that can be used as a function decorator.
The backend is specified either as an argument to tn.jit ("backend=..."), or by specifying the index of a "backend_arg" to tn.jit which labels the argument of the decorated function which specifies the backend. This allows jit to be used without knowledge or instantiation of the backend in advance.

Yes, and this basically wraps that. The new functionality is as such:
@partial(tn.jit, backend_argnum=2)
def jit_me(A, B, backend):
    return A@B

jit_me(a, b, "jax")

This lets you vary the backend when jitting without needing to instantiate it until you call the jitted function.


Support internal source-build-reference-packages builds

For internal releases, we may need to have private versions of SBRP.  This would include:

internal-only branches for the changes.
builds on dncenc/internal tenant.
publishing to a secure Azure storage container.

Work being done in #1591 for 5.0.

@crummel, @dseefeld - Is there anymore work needed here?  Can this issue be closed?

All infrastructure is in place today to support this.


Runsettings from command line (--) doesnt have capability to pass TestRunParameters

Description
TestPlatform can handle only those settings which is of the form
<RunSettings>
    <node1>
        <node2>
             <node3>value</node3>
        </node2>
    </node1>
</RunSettings>

by running command dotnet test -- node1.node2.node3=value
It doesn't have capability to pass attribute and its value for a runsetting element.
for example:
  <TestRunParameters>
    <Parameter name="webAppUrl" value="http://localhost" />
    <Parameter name="webAppUserName" value="Admin" />
    <Parameter name="webAppPassword" value="Password" />
  </TestRunParameters>

Creating this issue to enhance command line to handle the above scenario.

/cc pvlakshm

For the above example, can we have something like
dotnet test -- TestRunParameters.Parameter(name=webAppUrl,value=http://localhost) TestRunParameters.Parameter(name=webAppUserName,value=Admin) TestRunParameters.Parameter(name=webAppPassword,value=Password)
Currently, if same argument is passed more than once with different values after --, last value is used and other values are ignored, so we might need a way to support passing same arguments with different values in such a way that they become multiple nodes in the runsettings.

Note that the addition of command line parameters should overlay the file contents passed in through the dotnet test -s <settingfile>
In this way, you can easily have default test options, but override just a few.

@harshjain2 Personally, I would rather error than allow multiple overrides in the command line.  Odds are if I provided multiple overrides to the same key, I made a mistake.

Maybe add a flag to indicate intentionally adding multiple values, for example
TestRunParameters.Parameter(name=webAppUrl,append=true,value=http://localhost)

It might be better to add testrunparameters as first class parameter in the cmdline.
dotnet test --TestRunParameter:webAppUrl="http://localhost --TestRunParameter:webAppUser=faizan

It might be better to add testrunparameters as first class parameter in the cmdline.

It is adapter specific currently, we should think if other adapters are interested in implementing this behavior (in order to make it first class in vstest.console)?

Closing; reactivate if still required.

If you can show me where the unit tests are for related behaviors, and the argument parsing, I will add the feature myself.
The core problem with requiring a config/settings file to execute tests with parameters is that it makes it harder to make general purpose tests. For example, I have created a set of unit tests which allow validation of project and solution configuration. For example: hint paths for Project Dependencies must exist, warnings must be set as errors, dependencies across projects in the same solutions must be imported in the same manner, so on. Reusing this test project requires that I somehow inform the unit tests which project files to inspect. Without command line parameters, settings files must be managed in addition to invoking the test runner.
As a test runner is already a wrapper to a test framework for the purposes of execution, it seems unnecessary to wrap it again, just so I can pass in arguments. As an alternate solution, I have tried environment variables, but they don't seem to make it to the execution context of the test.
Thanks in advance for any assistance you can provide @pvlakshm

It seems like this is still unresolved - why was it closed so hastily? The thing that makes the least sense is how it works right now, which is to simply throw up a random XML error

So is this possible now? :|

This still doesn't seem to be possible. Can this issue be reopened?

I also need to be able to modify TestRunParameters from cmdln.
Please re-open this issue.

Yes pleaaase

Please make this work!

@pvlakshm Why would you close this? This is something alot of people need. (Currently needing to find work arounds for this issue).

???? @pvlakshm

A little ugly but you could do something along the lines of:
dotnet test -- TestRunParameters/Parameter[contains(@name,'SETTINGNAME')]/@value=SETTINGVALUE
Left-hand-side of the '=' can be xpath that needs to resolve to an existing attribute or element.

Note: that the xpath cannot contain '='.

For Azure Dev Ops, we have moved away from dotnet test and started using VSTest. Instead we use a dotnet publish in our build pipeline than in release, we choose a settings file when running our vstest. This is no longer an issue for us.

Runsetting is an option for me if there's a secure way of storing credentials in it.

What? I did not unassign @pvlakshm  from this ticket...

A little ugly but you could do something along the lines of:
dotnet test -- TestRunParameters/Parameter[contains(@name,'SETTINGNAME')]/@value=SETTINGVALUE
Left-hand-side of the '=' can be xpath that needs to resolve to an existing attribute or element.

Note: that the xpath cannot contain '='.
This gives an error:
Unhandled Exception: System.Xml.XmlException: The '/' character, hexadecimal value 0x2F, cannot be included in a name.
at System.Xml.XmlDocument.CheckName(String name)
at System.Xml.XmlElement..ctor(XmlName name, Boolean empty, XmlDocument doc)
at System.Xml.XmlDocument.CreateElement(String prefix, String localName, String namespaceURI)
at System.Xml.XmlDocument.CreateElement(String name)
at Microsoft.VisualStudio.TestPlatform.Common.Utilities.RunSettingsProviderExtensions.CreateNode(XmlDocument doc, String xPath)
at Microsoft.VisualStudio.TestPlatform.Common.Utilities.RunSettingsProviderExtensions.UpdateRunSettingsNode(IRunSettingsProvider runSettingsProvider, String key, String data)
at Microsoft.VisualStudio.TestPlatform.CommandLine.Processors.CLIRunSettingsArgumentExecutor.CreateOrOverwriteRunSettings(IRunSettingsProvider runSettingsProvider, String[] args)
at Microsoft.VisualStudio.TestPlatform.CommandLine.Processors.CLIRunSettingsArgumentExecutor.Initialize(String[] arguments)
at Microsoft.VisualStudio.TestPlatform.CommandLine.Processors.ArgumentProcessorFactory.<>c__DisplayClass21_0.b__0()
at System.Lazy1.PublicationOnlyViaFactory(LazyHelper initializer)    at System.Lazy1.CreateValue()
at System.Lazy1.get_Value()    at Microsoft.VisualStudio.TestPlatform.CommandLine.Executor.GetArgumentProcessors(String[] args, List1& processors)
at Microsoft.VisualStudio.TestPlatform.CommandLine.Executor.Execute(String[] args)
at Microsoft.VisualStudio.TestPlatform.CommandLine.Program.Main(String[] args)

@kbirger the xpath must resolve to an existing node. Otherwise it will try and create the node.
Refer code here

Not having this capability makes it difficult to use Azure DevOps "secret" pipeline variables from unit tests. Secret variables are not automatically added to environment variables, and not having this feature means there's no way to explicitly reference the pipeline variable from the .NET Core CLI task and pass it in on the command line.

@kanchm thanks for your answer, it works! Maybe you could suggest, how to run it in bash/powershell?

Why was this issue closed without a resolution? I'm also facing this with vstest.console.exe`. My scenario is to override some property already defined in my runsettings file through commandline arguments.

Still no way of passing cmdline to the runsettings? Seems a bit silly to close the issue without any resolution.

For folks using Azure Devops vstest task, you can use

+++++++

There is no way to set TestRunParameters from the command line using -- RunSettings. This issue needs should never have been closed as that was the original topic. All other discussions are work arounds to the fundamental issue of needing to set run parameters dynamically during the CI process without needing a runsettings.xml file to manipulate.

Yay reopened :)

Woohoo!

@cslutgen, Completely agree. It is quite annoying when documentation (and) clearly states that you can just specify RunSettings on the commandline, but that doesn't work for NUnit test project.

This PR should fix this issue https://github.com/microsoft/vstest/pull/2251

So how do I override TestRunParameters via the command line?
dotnet test .\tests.dll --no-build --settings:nunit.runsettings -- Foo=Bar
Gives an error:
Unhandled exception. System.NotImplementedException: The method or operation is not implemented.
   at Microsoft.VisualStudio.TestPlatform.CommandLine.Processors.CLIRunSettingsArgumentExecutor.Initialize(String argument)
   at Microsoft.VisualStudio.TestPlatform.CommandLine.Processors.ArgumentProcessorFactory.<>c__DisplayClass20_0.<WrapLazyProcessorToInitializeOnInstantiation>b__0()
   at System.Lazy`1.PublicationOnlyViaFactory(LazyHelper initializer)
   at System.Lazy`1.CreateValue()
   at System.Lazy`1.get_Value()
   at Microsoft.VisualStudio.TestPlatform.CommandLine.Executor.GetArgumentProcessors(String[] args, List`1& processors)
   at Microsoft.VisualStudio.TestPlatform.CommandLine.Executor.Execute(String[] args)
   at Microsoft.VisualStudio.TestPlatform.CommandLine.Program.Main(String[] args)

Have you tried the following ?
-- TestRunParaeters.Parameter(name="YourParamterName",value="YourParameterValue")

I'm getting the same error.
Also it shows that I'm using version 16.3.0 (and here in the repo I can see the newest version is 16.5.0).
I've just installed .NET Core 3.1.1.
Tests which I'm trying to run are using NUnit.
  <ItemGroup>
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="16.5.0" />
    <PackageReference Include="NUnit" Version="3.12.0" />
    <PackageReference Include="NUnit3TestAdapter" Version="3.16.1" />
  </ItemGroup>

@kamilzzz You are right, this is available in 16.5.0-preview version. You will probably have to wait a couple of weeks for new dotnet sdk to be out to be able to consume this feature.

@singhsarab what of reason to reference package in csproj file if we still use old package inside of sdk ?
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="16.5.0" />
It is possible to use version from reference when we start tests from cli ?

Test SDK does not carry the console, just the targets that make your project a test project  and give it a default entry point. And then it depends on test host nuget.
The version of console is selected by the runner, not by the project.  Or VS uses the one that is built in into it. Or dotnet test uses the one the is built into the sdk.  You can also override it using the VSTestConsolePath msbuild param shown above:
C:\Projects\temp\UnitTestProject1 [master +12 ~9 -0 !]> dotnet --version
3.1.101
C:\Projects\temp\UnitTestProject1 [master +12 ~9 -0 !]> dotnet test
Test run for C:\Projects\temp\UnitTestProject1\UnitTestProject1\bin\Debug\netcoreapp3.1\UnitTestProject1.dll(.NETCoreApp,Version=v3.1)
Microsoft (R) Test Execution Command Line Tool Version 16.3.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...

A total of 1 test files matched the specified pattern.

Test Run Successful.
Total tests: 1
     Passed: 1
 Total time: 1,9922 Seconds
C:\Projects\temp\UnitTestProject1 [master +10 ~9 -0 !]> dotnet test -p:VSTestConsolePath="C:\Users\jajares\Downloads\microsoft.testplatform.portable.16.6.0-preview-20200309-01\tools\netcoreapp2.1\vstest.console.dll"
Test run for C:\Projects\temp\UnitTestProject1\UnitTestProject1\bin\Debug\netcoreapp3.1\UnitTestProject1.dll(.NETCoreApp,Version=v3.1)
Microsoft (R) Test Execution Command Line Tool Version 16.6.0-preview-20200309-01
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...

A total of 1 test files matched the specified pattern.

Test Run Successful.
Total tests: 1
     Passed: 1
 Total time: 1,9813 Seconds

I am trying to pass TestRunParameters through the CLI using dotnet test -- TestRunParameters syntax, but I am getting an error.
I use this command:
dotnet test --settings local.runsettings -- TestRunParameters.Parameter(name="myparam",value="foo")

but get the following error:
ParserError:
Line |
   1 |  … al.runsettings -- TestRunParameters.Parameter(name="myparam",value="f …
     |                                                                ~
     | At line:1 char:106 + … al.runsettings -- TestRunParameters.Parameter(name="myparam",value="f … +                                                               ~
Missing argument in parameter
     | list.

I have just updated to .NET Core SDK 3.1.201 and when running dotnet test, I can see that the MS Test CLI used for running the tests is v16.5.0. The tests are Nunit test and my project have the following package references.
<PackageReference Include="nunit" Version="3.12.0" />
<PackageReference Include="NUnit3TestAdapter" Version="3.16.1">
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="16.5.0" />

It seems like the issue is with the comma and I am missing a parameter, but I cant find any documentation on it. Initially I figured out the syntax based on output from the test CLI which showed this output:
The test run parameter argument 'TestRunParameters.myparam=foo' is invalid. Please use the format below.
     Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\")

What argument am I missing?

@mikanyg that looks like PowerShell 7 error, so you are running into powershell parser that does not understand your intent, because what you provided is not a valid powershell syntax, as you did not wrap it into a string.
You can overcome this in few ways, the easies is to always specify your -- settings last and use --% to terminate the parsing before it. The --% will be stripped by powershell and won't be passed to the dotnet command. See below my test program that just outputs the args it got each on a new line:
.\ConsoleApp18.exe test --settings local.runsettings --% -- TestRunParameters.Parameter(name="myparam",value="foo")

args
test
--settings
local.runsettings
--
TestRunParameters.Parameter(name=myparam,value=foo)

The parsing (that is done in dotnet cli, needs to be revisited. We already did few fixes on this in 16.6.0, but I think a proper revisit is warranted in 16.7.0. Ideally we would:

Make sure that the xml and cli runsettings are 1:1 and will remain 1:1
at least warn about seeing unknown settings
make settings case insensitive
document usage of --%
see how we are handling this in bash because there -- is used as parsing terminator I think
figure out how to apply settings from command line over the ones in xml
figure out how to denote that we are adding cli settings to the ones in xml
figure out how to disable setting that is in xml but we don't want it to be applied

@nohwnd Thx for did tip, yes I do use Powershell 7.
Now tried this command
dotnet test --settings local.runsettings --% -- TestRunParameters.Parameter(name="myparam", value="foo")

but got new error
The test run parameter argument 'TestRunParameters.Parameter(name=myparam,' is invalid. Please use the format below.
     Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\")

I have tried escaping the double quote with backslash as shown in the error output, I even tried single quote and no quote, but same error is output.
When I try running the command from cmd (without the --%) I get the same error.
Does this even work in 16.5?

This is a double escape issue.
The parameters are parsed and split by both powershell and the default commandline parsing mechanism in the dotnet.exe. That parsing is also the same thing that happens in any other console app. The problem here is that the console parse strips out the quotes and splits on spaces. Again using my toy app, I think the best option here is to actually NOT use the --% (contrary to what I said in the previous post) but instead make sure that we provide each setting as a distinct non-expandable string:
 .\consoleapp18.exe test -- 'TestRunParameters.Parameter(name=\"myparam\", value=\"foo\")'
args

test
--
TestRunParameters.Parameter(name="myparam", value="foo")

.\consoleapp18.exe test -- 'TestRunParameters.Parameter(name=\"myparam\", value=\"foo\")' 'TestRunParamet
ers.Parameter(name=\"myparam\", value=\"foo\")'
args

test
--
TestRunParameters.Parameter(name="myparam", value="foo")
TestRunParameters.Parameter(name="myparam", value="foo")

Escaping should also be pretty easy to automate the escape by a powershell function that you put into your profile if you want  the convenience of not having to escape the settings manually.
($settings -replace '"', '\"')

Did exactly this and still got an error. Could you try with the dotnet test instead of your test app?
dotnet test --settings local.runsettings -- 'TestRunParameters.Parameter(name=\"myparam\", value=\"foo\")'
Test run for D:\source\IntegrationTests.dll(.NETCoreApp,Version
=v3.1)
Microsoft (R) Test Execution Command Line Tool Version 16.5.0
Copyright (c) Microsoft Corporation.  All rights reserved.

The test run parameter argument 'TestRunParameters.Parameter(name=myparam, value=foo)' is invalid. Please use the format below.
     Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\")

Help is much appreciated

Oh I see it. It also passes it to msbuild which then passes it to vstest.console via a msbuild parameter for the vstest task. The problem there is that the pass mechanism already puts the string into double quotes so we can't simple double the single quotes to give msbuild a literal string (which is probably what we should do to avoid some of these quotest shenenigans). So we need to triply escape this.
dotnet test --settings local.runsettings -- 'TestRunParameters.Parameter(name=\\\"myparam\\\", value=\\\"foo\\\")'

Triple escape:

pass powershell parser by making the param a non-expandable string by putting single quotes around it, this will cause that the string will not be split on spaces, but it will get the quotes stripped.

PS> dotnet ConsoleApp18.dll 'a b'
args
a b
PS> dotnet ConsoleApp18.dll '"a b"'
args
a b

Escape quotes to get them through the command line parser while passed to dotnet.exe (or any other console).

PS> dotnet ConsoleApp18.dll '"a b"'
args
"a b"

escape the double quotes that are passed to msbuild to ensure we don't break the msbuild command by escaping every quote with \. That is why we need to end up with \" rather than just ".

"dotnet.exe" exec "...\MSBuild.dll"
    -verbosity:normal "-property:VSTestCLIRunSettings=\"TestRunParameters.Parameter(name=\"myparam\", value=\"foo\")\""

PS> dotnet ConsoleApp18.dll '\\\"a b\\\"'
args
\"a b\"

There is one more pass, but here the task probably escapes correctly before passing the call, because vstest console is correctly passed escaped quotes \", so we don't need to do anthing.

@nohwnd Triple backslash confirmed working.
But I really do hope this feature get some more love? I don't have anything good to say about the workaround other than it works.

@mikanyg I think the msbuild problem is reasonably easy to solve by using ' (as long as you don't want to provide params that contain ', or by doing the escape ourselves.
The dotnet.exe parsing we should be able to solve by grabbing Environment.Commandline instead of the parsed args, and the same in vstest.console testhost.

@nohwnd Found another issue in the same area. Turns out I needed to use dotnet vstest (instead of dotnet test) since the test I was trying to execute were in a dll, not a csproj. When changing to vstest the parsing error returned.
After trying several backslash escape option, it works with a single backslash (not triple).
Like in this example:
dotnet vstest .\bin\Debug\netcoreapp3.1\IntegrationTests.dll -- 'TestRunParameters.Parameter(name=\"myparam\", value=\"myvalue\")'

Guess it is parsed less times than when running from dotnet test.
Hope this helps improve the feature.

@mikanyg thanks for reporting back, I saw it as well in the issue that is linked just above your comment, see my original comment below:
@TroyWalshProf will close your issue, and will track it here.
_originally posted in https://github.com/microsoft/vstest/issues/2377
Please see https://github.com/microsoft/vstest/issues/862#issuecomment-603894275 for some workarounds and explanation. You will need to do some escaping, which will also depend on whether you run the commands from cmd or powershell. Because vstest does not route via msbuild you should be able to escape it like this, and in the same way for vstest.console.
# powershell
dotnet vstest tests.dll -- 'TestRunParameters.Parameter(name=\"Browser\",value=\"Chrome\")'

or
REM cmd
dotnet vstest tests.dll -- TestRunParameters.Parameter(name=\"Browser\",value=\"Chrome\")

We will be working on improving this, but can't promise any date.

@nohwnd I tried what you outlined above and is worked for the most part.
The issue is that I have use a lot of code that uses parameter names with non alphanumeric characters.
Example:
dotnet vstest tests.dll -- TestRunParameters.Parameter(name=\"MainGroup:Browser\",value=\"Chrome\")
Any reason
https://github.com/microsoft/vstest/blob/7eaa0a21b51c8e75d99848de3e4e4555b8334dfe/src/Microsoft.TestPlatform.Common/Utilities/RunSettingsProviderExtensions.cs#L98
couldn't be changed to:
var attrName = $"(?<{AttributeNameString}>\\S+)";?
or you could also do something like this if you don't want to allow names to start or end with non alpha numeric:
var attrName = $"(?<{AttributeNameString}>(\\w+\\S*\\w+)|(\\w+))";)

@TroyWalshProf Honestly I don't know if there are any implications for changing this. To me it looks like it is just trying too hard to validate the format. In the PR that added it I see that this is an invalid case new object[] { "TestRunParameters.Parameter(name=\"asf@#!\",value=\"rgq\")" }, but I don't see any explanation why. This will need further investigation.
Were you able to use it with the special chars and it works?

@nohwnd I agree, does seem like they are being a bit too strict. I think it is literally a one char change (w to S) to get this to align with what Azure DevOps currently supports.
To be clear, currently this works:
dotnet vstest tests.dll -- TestRunParameters.Parameter(name="MainGroupBrowser",value="Chrome")
But this does not:
dotnet vstest tests.dll -- TestRunParameters.Parameter(name="MainGroup:Browser",value="Chrome")

Note to self: Check if it will blow up in devops, if you provide space, or if there are any docs on the values they actually support in the task.

Is this supposed to be working in bash on Linux?
I am trying to run dotnet test -- TestRunParameters.Parameter(name="myParam", value="myValue")
But I get the following error: bash: syntax error unexpected word '('

@philipreimer You're hitting the same quoting/escaping issues as other people, bash is interpreting some of those characters as shell syntax instead of passing them through to the dotnet process, you'll probably have to quote the entire parameter entry and then escape the quotes inside it. Hopefully you won't need double- or triple-quoting/escaping like they did above.

@qidydl I tried several version but cannot figure out how to do get this working. Here's what I tried:
dotnet test -- 'TestRunParameters.Parameter(name="myParam", value="myValue")'
dotnet test -- "TestRunParameters.Parameter(name=\"myParam\", value=\"myValue\")"
dotnet test -- "TestRunParameters.Parameter(name=\\\"myParam\\\", value=\\\"myValue\\\")"
Now I always get: One or more runsettings provided contain invalid token
Any ideas?
BTW, would be nice if it could tell me which token is invalid.

@philipreimer are you running from cmd or powershell? The last version looks like it is almost there but you would have to use single quotes around the whole string:
dotnet test -- 'TestRunParameters.Parameter(name=\\\"myParam\\\", value=\\\"myValue\\\")'

@nohwnd I am using bash on Manjaro Linux
GNU bash, Version 5.0.16(1)-release (x86_64-pc-linux-gnu)

$ dotnet --info
.NET Core SDK (gemäß "global.json"):
 Version:   3.1.103
 Commit:    6f74c4a1dd

Laufzeitumgebung:
 OS Name:     manjaro
 OS Version:
 OS Platform: Linux
 RID:         arch-x64
 Base Path:   /usr/share/dotnet/sdk/3.1.103/

Host (useful for support):
  Version: 3.1.3
  Commit:  ed88943d24

.NET Core SDKs installed:
  3.1.103 [/usr/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.App 3.1.3 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.1.3 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

@philipreimer I am currently digging into this, what I plan to do is:

take the literal part after -- from the Environment.CommandLine to get it unparsed
pass this to msbuild already escaped, or using single-quoted string

This should take care of both of the issues, you as the caller will just have to ensure that you don't run into the parser of the command line you are using, I cannot do anything about that. Which in the case of bash is avoided by using -- as you already do.
Would be really nice if you helped me test this 🙂

@nohwnd I can help testing.
I also have one general question: why is the format for passing TestRunParameters the way it is? It seems very complicated. I am not familiar with the internals of the dotnet CLI but wouldn't something like this -- TestRunParameters.myParam=myValue TestRunParameters.myOtherParam=myOtherValue be much easier to handle and be just as powerful?

@philipreimer  I can't answer that I don't have that context either. I started a new issue on your behalf. I think this might be coming from azdo, or maybe was always like that and was never meant to be used "interactively". I am not sure how soon we will get to the issue. It potentially has a ton of dependencies, and so it will be difficult to change.
Thanks for the testing part, I am building dotnet/sdk now, so I am not sure how feasible it will be for you to actually try it on your side 😔

@nohwnd since this issue has been closed what is the usual process now? Will your changes be included in the next version of dotnet sdk? Do I have to wait for that and when will that happen? Or is there some preview version I can download?

Heh, I did not know that GH now matches also part of the message, not just whole line. The fix for this is not complete.

Right now there is a PR pending with the changes that I've done on vstest side, and I am waiting for them to build and merge, to test a fix that I wrote yesterday for sdk to PR it. Once that PR is merged it will be available via a local sdk build (on windows it's simple you just run build.cmd and then eng/dogfood.cmd, on linux I am not sure yet).
And then when sdk inserts into dotnet/installer it will be available to download directly as a pre-release.
https://github.com/dotnet/sdk/pull/11465

I could not get it to not require any escaping, that would only be possible on Windows via PInvoke, and even that was not 100%. So instead I aimed to make it the same syntax for dotnet test, dotnet vstest and vstest.console. It needs a single escapement, and will merge your test run parameters if they contain spaces. Typically after ", value or when you provide value with spaces. In powershell --% parsing terminator is the secret sauce. On bash you need to escape all spaces quotes and parentheses, but the error messages are helpful. It also aligns nicely with the current error message if you do it wrong.
# cmd
dotnet test  -- TestRunParameters.Parameter(name=\"myParam\", value=\"value\")

# powershell
dotnet test --%  -- TestRunParameters.Parameter(name=\"myParam\", value=\"value\")

# bash
dotnet test -- TestRunParameters.Parameter\(name=\"myParam\",\ value=\"value\"\)

At the moment I am waiting for PR to dotnet/sdk to build to see if I pass their tests. It works locally on my Windows.

Sorry for bringing that up but bash is not the only shell used on non-windows systems. For example, zsh is the default shell in current macos versions, I think.
Will the bash version work in those other shells as well?

@philipreimer  bash was an example. The point is that the syntax should be the same for dotnet vstest, dotnet test and (on windows) vstest.console, no matter how many hops there are. I am aware of zsh, and I hope it will work there as well using the same syntax as in bash, but that depends on the escaping rules that zsh has. There is a merge building in dotnet/sdk so let's hope we can have an installer for that soon.

@philipreimer I was able to validate this on bash and zsh on Ubuntu (actually Ubuntu 18.4 in WSL2).
Download and extract to dotnet folder:
mkdir dotnet
wget https://aka.ms/dotnet/net5/dev/Sdk/dotnet-sdk-linux-x64.tar.gz
tar zxvf dotnet-sdk-linux-x64.tar.gz -C dotnet

And then just run it from that folder:
/mnt/c/temp/dotnet/dotnet test --no-build -- TestRunParameters.Parameter\(name=\"myParam\",\ value=\"value\ with\ space\"\)

I am attempting to use the syntax here using cmd.
dotnet test --logger:"trx;LogFileName=TestResults.trx"  -- TestRunParameters.Parameter(name=\"myParam\", value=\"value\")

But when I do, I get the error message:
One or more runsettings provided contain invalid token

What (if any) version of .NET Core SDK was this fixed in?

I installed .NET Core SDK 3.1.202 and tried again. Now I am getting a different error message with the same command on the same test project (also using cmd).
dotnet test --logger:"trx;LogFileName=TestResults.trx"  -- TestRunParameters.Parameter(name=\"myParam\", value=\"value\")

The test run parameter argument 'TestRunParameters.Parameter(name=myParam,value=value)' is invalid. Please use the format below.
     Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\")

Since I have literally copied and pasted the command from above, it seems like this is a bug of some kind with the latest release.

This was fixed in the master of dotnet/sdk, so it will be part of the next 5.0 release. Checking with the team to get the simplest way to get it into 3.1 as well.

The vstest.console part was released in this preview https://www.nuget.org/packages/Microsoft.TestPlatform.TestHost/16.7.0-preview-20200519-01
@NightOwl888 we will have to backport to net3.1.xxx after this proves to be working because the bar is a bit higher there than getting it into master of the current dotnet. So this will take some time till it's released... Can't think of any way to get it to you faster, that would be simpler than using the above escaping workaround.

Thanks. Since our use case is a test framework library that many others will use, getting it to "us faster" wouldn't help. We can wait for an official release, but it would be great if we can get a notification when that happens so we can add the documentation about the feature as well as the minimum prerequisite version of .NET Core SDK.

It can be helpful while configuring VsTest step on Azure DevOps.
If u try to implement .runsettings TestRunParameters section for Azure DevOps VsTest step and you have similar log
##########################################################################
DtaExecutionHost version 18.170.30112.1.
Starting TestExecution Model...


Investigate using git archive

The current logic in sbt-source-dist is to manually filter out files specified in .gitignore as well as manually construct the archives. It might make sense that rather than doing this, we should use git archive (if the machine has git) which should be a lot faster and correct, even if we have to manually end up deflating it for the other archive formats.
We can use https://github.com/sbt/sbt-git to do the heavy lifting, just need to make this plugin extend sbt-git.

@jrudolf Regarding the problem you described at https://github.com/apache/incubator-pekko/pull/143#issuecomment-1425456760, I didn't experience this but I suspect because I used it on a clean repo and maybe its including either target or something along those lines?
I know that sbt source dist currently doesn't fully support .gitignore. It may be quicker to just solve that problem. If you want to work on this issue don't forget to assign yourself.

So I haven't been able to replicate this, at least my original theory of target getting included turned out to be incorrect

git archive is probably the way forward but there are a few git managed files that we would ideally leave out of the source distribution.

.gitignore
.asf.yaml

It's probably not too bad to include these in the source distribution but the existing code leaves them out.

git ls-tree is another option I believe, with the correct args it can give us a list of files and then we can add others (such as .gitignore and `.asf.yaml).

#30 merged


Redeployment multi-step: first Configuration in index is selected by default

When redeploying Content, I'm asked to choose a Configuration file and if I have multiple configurations the one selected by default is always the first one in the list.  I'd expect the default selection to be the matching configuration-name listed in the Deployment file.
Here I have made a deployment with the default configuration. Yet when I click redeploy, the menu is selecting the first configuration in alphabetical order (blue).
https://github.com/posit-dev/publisher/assets/41300090/01c07bdf-b55c-4d69-93fb-b227c75b5f25

no longer occurring


Remove esm package

the esm package is the last thing preventing ember from running in webcontainers.
See:

https://github.com/stackblitz/core/issues/647#issuecomment-1144044823
https://github.com/stackblitz/webcontainer-core/issues/354

It looks like esm is only used for loading the brocfile
❯ git grep esm
README.md:Typescript by default only allows the [ES6 modules](https://nodejs.org/api/esm.html) `import/export` syntax to work
README.md:Broccoli supports [ES6 modules](https://nodejs.org/api/esm.html) via [esm](https://www.npmjs.com/package/esm) for
lib/load_brocfile.ts:import esm from 'esm';
lib/load_brocfile.ts:const esmRequire = esm(module);
lib/load_brocfile.ts:    // Load brocfile via esm shim
lib/load_brocfile.ts:    brocfile = esmRequire(brocfilePath);

since ember doesn't care about brocfiles -- is there a way to opt out of this behavior and prevent esm from being loaded at all? (it monkey patches node globals, which breaks tools like stackblitz)

Ember-CLI did use Brocfiles at one point (I remember dealing with them) but apparently that was in https://github.com/ember-cli/ember-cli/tree/v0.2.7/blueprints/app/files before the jump to 1.13 when ember-cli became the default. Given that that was 8 years ago I imagine the current Ember-CLI doesn’t need to support that far back … 😉

Have ember-cli build error on node@22 because of this package.

https://github.com/broccolijs/broccoli/commit/5bd188377a67f9f72aafd85a62b6a250c1c89fbb

do you have a repro repo? it's been a while since I've seen this one

@NullVoxPopuli yes, it's here: https://github.com/Brain-up/brn/pull/2631
Trying to bump node to latest

looks like ember-data needs upgraded -- ember-data/private-build-infra uses, and private-build-infra moving off of ESM is what unblocked stackblitz from working.
@ember-data/private-build-infra @ 3.28.7 is just too old


Update KeyDB client with missing commands:

Description
Adds missing command extensions /  commands that are visible in keydb 6.3

bitop lshift/rshift
pexpireat
ttl
pttl
mexists
hrename
object lastupdated (I'm not clear what the response from this command really means and how it's meant to be used)
cron

Addresses #54

cc @raphaelauv


Add settings view

Add a new setting view with a navbar
This view must have a dedicated shortcut on the home view and will be used later to gather all Whales Manager settings (check updates for images and docker engine, register agents, configure authentication ...)

Done in commit feat (frontend): add image list support in settings view (7267ba9)


Jedis can't connect to Redis if it wasn't available during the launch of the Jedis client

I am new to Jedis. I hope my issue will useful.
Expected behavior

Redis server unavailable
Launch Jedis client
Make Redis server available
Successfully start to work with Redis

Actual behavior

Redis server unavailable
Launch Jedis client
Make Redis server available
Get exception JedisNoReachableClusterNodeException: No reachable node in cluster"

From Jedis code, I learned that during the creation of object JedisClusterConnectionHandler method discoverClusterNodesAndSlots will be called. This method will retrieve Redis nodes but if it fails to do so the number of nodes will be zero and the framework will not try to reobtain nodes as a result exception JedisNoReachableClusterNodeException.
Jedis version: 2.8.1
Redis version: 3.2.10
Java version: 8

@Lrakulka

Expected behavior

Redis server unavailable
Launch Jedis client
Make Redis server available
Successfully start to work with Redis

Seems logical. But there is JedisNoReachableClusterNodeException: No reachable node in cluster. So, apparently, you didn't Make Redis server available. Did you?

If be more precise, my Redis server is always online and healthy but to access it you need VPN.
0. Redis server online

VPN turn off
Launch Jedis client
VPN turn on
Make a request to Jedis server get an exception JedisNoReachableClusterNodeException

If VPN enabled during Jedis launch, everything is fine.

I solved this issue by extending JedisConnectionFactory.
public class CustomJedisConnectionFactory extends JedisConnectionFactory {
    private static final Logger LOGGER = LoggerFactory.getLogger(JedisConnectionFactoryProxy.class);

    private JedisCluster jedisCluster;

    public JedisConnectionFactoryProxy(RedisClusterConfiguration clusterConfiguration) {
        super(clusterConfiguration);
    }

    @Override
    protected JedisCluster createCluster(RedisClusterConfiguration clusterConfig, GenericObjectPoolConfig poolConfig) {
        jedisCluster = super.createCluster(clusterConfig, poolConfig);
        return jedisCluster;
    }

    @Override
    public RedisConnection getConnection() {
        if (jedisCluster.getClusterNodes().isEmpty()) {
            afterPropertiesSet();
        }
        return super.getConnection();
    }
}


Pinned tabs duplicate

When opening tabs, none of the Navigation Strategies seem to avoid duplication if the initial tab is pinned. IDE and Notebook avoid duplication only if the tab is unpinned. Can this be changed?

Hi @kmaustral ! This is unexpected. Could you please provide the steps to reproduce? Thank you!

Sure.

Note in sidebar with link to note in window which is pinned.
Click link and note opens a second time alongside the pinned version

On Thu, 12 Dec 2024 at 19:05, oxdc @.***> wrote:

Hi @kmaustral https://github.com/kmaustral ! This is unexpected. Could
you please provide the steps to reproduce? Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/oxdc/obsidian-vertical-tabs/issues/74#issuecomment-2538077570,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTR6NYLDOAOJI2WTZCGYKL2FE7VJAVCNFSM6AAAAABTO5BGRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZYGA3TONJXGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @kmaustral ! If I'm correct, in your case, a pinned note is in the sidebar. If you try to open this note again, another tab of it will open in the main area. This is the designed default behavior for now. Tab deduplication only works in the main area by default because most users treat the sidebar as a special area. I'll add an option to deduplicate sidebar tabs. Thank you!

Note quote. I click a link from a note in the sidebar to a different note
in the pane which is already pinned. It then opens a duplicate. It doesn't
do this if the note is unpinned.
On Fri, 13 Dec 2024 at 13:55, oxdc @.***> wrote:

Hi @kmaustral https://github.com/kmaustral ! If I'm correct, in your
case, a pinned note is in the sidebar. If you try to open this note again,
another tab of it will open in the main area. This is the designed default
behavior for now. Tab deduplication only works in the main area by default
because most users treat the sidebar as a special area. I'll add an option
to deduplicate sidebar tabs. Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/oxdc/obsidian-vertical-tabs/issues/74#issuecomment-2540424995,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTR6NYH7A4YY3SXQFGMND32FJEAHAVCNFSM6AAAAABTO5BGRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBQGQZDIOJZGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @kmaustral ! Unfortunately, I cannot reproduce based on your description. I'm not sure if I understand correctly. Could you please try to reproduce in a Sandbox vault? If the problem still exists in the Sandbox, could you please record a video with all the steps required to reproduce the bug, and upload it here? Thank you so much!

Hi @kmaustral ! Since I cannot reproduce this issue in the latest version, I am closing it for now. The next version will include some improvements, so when it is released, please upgrade and test again. If you still encounter the issue after the update, feel free to reopen it. Thank you for your understanding.

Thanks. Sorry I haven't had time to sandbox the issue. But one other
problem has come up with Plugin Update Tracker. With Vertical Tabs
installed, the plugin update screen cannot stay focused. It continually
reverts to the next open tab.
On Fri, 27 Dec 2024 at 01:09, oxdc @.***> wrote:

Hi @kmaustral https://github.com/kmaustral ! Since I cannot reproduce
this issue in the latest version, I am closing it for now. The next version
will include some improvements, so when it is released, please upgrade and
test again. If you still encounter the issue after the update, feel free to
reopen it. Thank you for your understanding.
—
Reply to this email directly, view it on GitHub
https://github.com/oxdc/obsidian-vertical-tabs/issues/74#issuecomment-2562790953,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTR6N5Y2554IZ4NLA4PXYT2HQE2BAVCNFSM6AAAAABTO5BGRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRSG44TAOJVGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @kmaustral ! Thank you.

But one other problem has come up with Plugin Update Tracker. With Vertical Tabs installed, the plugin update screen cannot stay focused. It continually reverts to the next open tab.

I have fixed this issue.


Creating a position shortly after another one fails with insufficient funds

If you try to create a second long position after opening another one, the setup fails without reason. Looking at the logs one can find that insufficient funds appear to be the issue. However, waiting a few more minutes and the very same action succeeds without an issue.
2022-09-05 12:34:46  INFO xtra_actor_request{actor_type=daemon::process_manager::Actor message_type=daemon::process_manager::Event}:xtra_message_handler:Handle Event: sqlite_db: Appended event to database event=ContractSetupStarted order_id=b8610496-65ee-45b2-b37e-83e5e3533176
2022-09-05 12:34:46 ERROR Setup contract:Generate own params: daemon::order::contract_setup: error=Failed to build party params
2022-09-05 12:34:46 ERROR Setup contract: daemon::order::contract_setup: error=Failed to build party params
2022-09-05 12:34:46  WARN fallible task handle_error{err=Failed to build party params}: model::cfd: order_id=b8610496-65ee-45b2-b37e-83e5e3533176 peer_id=Some(12D3KooWEsK2X8Tp24XtyWh7DM65VfwXtNH2cmfs2JsWmkmwKbV1) Issuing event: ContractSetupFailed with: Failed to build party params: InsufficientFunds { needed: 251067, available: 0 }
2022-09-05 12:34:46  INFO fallible task handle_error{err=Failed to build party params}:xtra_actor_request{actor_type=daemon::process_manager::Actor message_type=daemon::process_manager::Event}:xtra_message_handler:Handle Event: sqlite_db: Appended event to database event=ContractSetupFailed order_id=b8610496-65ee-45b2-b37e-83e5e3533176
2022-09-05 12:34:51  WARN Send message every interval{interval_secs=180}:xtra_actor_request{actor_type=daemon::wallet::Actor<bdk::blockchain::electrum::ElectrumBlockchain, sled::tree::Tree> message_type=daemon::wallet::Sync}:xtra_message_handler:Handle Sync:Sync wallet: electrum_client::raw_client: got error for req_id 82: JSON(Error("EOF while parsing a value", line: 1, column: 0))
2022-09-05 12:34:51  WARN Send message every interval{interval_secs=180}:xtra_actor_request{actor_type=daemon::wallet::Actor<bdk::blockchain::electrum::ElectrumBlockchain, sled::tree::Tree> message_type=daemon::wallet::Sync}:xtra_message_handler:Handle Sync:Sync wallet: electrum_client::raw_client: removing all waiting req of this batch
2022-09-05 12:34:51  WARN Send message every interval{interval_secs=180}:xtra_actor_request{actor_type=daemon::wallet::Actor<bdk::blockchain::electrum::ElectrumBlockchain, sled::tree::Tree> message_type=daemon::wallet::Sync}:xtra_message_handler:Handle Sync:Sync wallet: electrum_client::client: call 'batch_script_get_history' failed with EOF while parsing a value at line 1 column 0, retry: 1/1

Unfortunately a knows bug/limitation of (how we muse) BDK.
 Unfortunately this takes some time to be picked up, hence, it fails first and then works.

I don't think that this is the case, I painfully collected funding from a number of faucets multiple time to get enough funds.. but let me check.

Did you double check? If it is an issue above what I described please re-open.


middleware: split up ResyncBitcoin RPC into two RPCs

The ResyncBitcoin RPC is split up into the ResyncBitcoin and ReindexBitcoin RPC.
This builds on top of work done in 35013917cbb7aa5512a4f4373dd355d143db555c. Will rebase on master once https://github.com/digitalbitbox/bitbox-base/pull/163 is merged.

This is being implemented in https://github.com/digitalbitbox/bitbox-base/pull/176.


FIA_UAU.7 missing from App Note 18

Section <IP_ADDRESS>, FIA_UIA_EXT.1.3, Application Note 18
2nd paragraph: The direction to include FIA_UAU.7 from Appendix B is missing; without it being specified here, there is no mechanism for the ST author to include it.
Add FIA_UAU.7 to the list of SFRs to be included from Appendix B

Recommendation...
Disregard and/or link to issue #162 .  The section number, SFR and application note referenced in the issue don't correlate to each other.  Regardless, the resolution of issue #162 should resolve this concern.

Closing this issue after discussion in MINT meeting on 2023-02-13.
This issue will be resolved when #162 is resolved.


Create LICENSE

Coverage remained the same at 100.0% when pulling bfa4a3546d7b1a6335447590c42bdaa2a48fc028 on add-license-1 into 8313c86825852a739ba23dd7f66b84b6f6732d84 on master.


feat: increase video view count

This pr will solve task #21.

@foyzulkarim vai, is it possible to give any feedback on this pr ?

@aninda052
I have checked the suggestions. Actually we will make a common base-repository later which will have the common update function. In that common update function we will send the payloads from the Service file.
We should not add the simplification on the current service.js file. So, please add new functionas as I suggested.
Plus, please check I said earlier, we want to perform some other operations when we update (the operations may be different), and we MUST not do those operations on the controller.js file.
I hope you get the idea. Please let me know if you have other questions. Thanks.


is there a way to manipulate the time before using fallback gateway?

More a question than an issue ..
Love this tool btw.
Been playing with ConnectTimeout: 10 but that doesn't seem to work:
Connection timed out during banner exchange

Hi @Zhann, thank you for your feedback,
Can you give me an (anonymised) example of configuration file ?

Note that when you are setting the gateways field; assh will iterate over all the entries of this field until the the first successful connection.
So technically, the first host is not a fallback, but the second one, the third one... are
If you want to have "fallback gateways", you need to put the magic "direct" host as the first entry of this field, so assh will try to connect without gateways before trying the rest of the list.
Do you find that odd? I may write a note on the README.md if this is not 100% clear as it is for me the feature I'm using the most every days :)

example:
hosts:
  aaa:
    gateways:
    - bbb
    - ccc
    - direct
    - eee

ssh aaa will try until first success:

ssh bbb -> ssh aaa
ssh ccc -> ssh aaa
ssh aaa
ssh eee -> ssh aaa

I just released a new version here: https://github.com/moul/advanced-ssh-config/releases/tag/v2.2.0
Can you get the latest version and run these commands:
$ assh proxy --dry-run <your-host>
$ assh info

For example, here is mine:
$ assh proxy --dry-run test-ccc
ERRO[0000] Cannot use gateway '<IP_ADDRESS>': dry-run: Execute [ssh <IP_ADDRESS> -- nc <IP_ADDRESS> 22]
ERRO[0000] Cannot use gateway '<IP_ADDRESS>': dry-run: Execute [ssh <IP_ADDRESS> -- nc <IP_ADDRESS> 22]
ERRO[0000] Failed to use 'direct' connection: dry-run: Golang native TCP connection to '<IP_ADDRESS>:22'
ERRO[0000] Cannot use gateway '<IP_ADDRESS>': dry-run: Execute [ssh <IP_ADDRESS> -- nc <IP_ADDRESS> 22]
FATA[0000] Proxy error: No such available gateway

$ assh info
Debug mode (client): false
CLI Path: /usr/local/bin/assh
Go version: go1.5.3
OS/Arch: darwin/amd64

RC files:
- ~/.ssh/assh.d/ocs.yml
- ~/.ssh/assh.d/pathwar.yml
- ~/.ssh/assh.d/test.yml
- ~/.ssh/assh.yml
- ~/.ssh/assh.d/esl.yml
- ~/.ssh/assh.d/hosts.yml
- ~/.ssh/assh.d/moul.yml

Statistics:
- 187 hosts
- 0 templates
- 7 included files

Hi @Zhann, #116 should fix this issue, can you get the latest version and give a new try ?

Hi @moul, sorry for not replying earlier. Yes, this fixed my issue! Thank you very much.

super :+1:


SemVer conventions

Hi,
there is a convention to version numbers that precede 1.0 release.
If you don't use semantic versioning or want to do things another way in pre-release phase, then ignore this 😄 Just wanted to make sure you're aware of this convention.

I don't consider Salt at a "initial development release" milestone yet. I feel confident in a good portion of the code but I want to expand on our example set as well as write at least a couple of small applications with it to get a "feel" for it. This will likely result in many small changes (and a couple major changes to middleware). When we move to 0.1.0 I'll also be committing to a deprecation cycle.


Vim response (diff mode display,  scrolling up/down and general display) is slow on Virtual Machine Vmware Workstation.

I'm not sure if there is anything actionable here.  Please give more context.

I'm not sure if there is anything actionable here.  Please give more context.

ViM
Vim-Vi Improved 9.0 Gui version with Ole support
Included patches: 1-886
Huge version with GUI.
Features Included All out of
-balloon_eval_term
-dnd
-ebcdic
-farsi
-footer
-hangul_input
-perl
-postscript
-python
-sun_workshop
-tag_old_static
-tag_any_white
-term_response
-tgetent
-vtp
-xfontset
-xim
-xpm_w32
-xterm_save
Compiled with gcc under Msys2 and used as standalone distro.
Vmware
Esxi Vmware 6.7 ~ Workstation 14
Vmware Tools v11301
Step to reproduce
Sizing consideration
Cpp file of 4400 mines code and open tagbar which show 48 functions.
Step
Launching Vim GUI on Windows 10 64bits virtualized and

open this large cpp file >>> 1 to 3 seconds spent
open tagbar list >>> equal, some seconds
The test is simple just typing right and down arrow keys of keyboard in gamer mode ;) many time

Right, Down
Right, Down
15 times
Right, Down
Looking at the cursor, a big lag response is seen.!! Of 1-3 seconds !!!
Then Launching Visual Studio 2022, same file, same test, no lag.
Options
My updatetime option is 300.
I can extract all if needed.
I can profile with your instructions what to profile
I can do -None startup.
_vimrc
Contains
set rop=type:directx, gamma: 1.0, contrast:1.5, level:0.0, geom:2, renmode:6, taamode:3
set guifont=Iosevka_SS05_Light:h10:W280:cANSI:qDRAFT
:echo $HOME shows c:\users\administrator
:echo $VIM shows c:\Vim
:echo $VIMRUNTIME shows c:\Vim\vim90
:echo $MYVIMRC shows c:\Vim_vimrc
Thanks.

Clear the 'renderoptions' option and try again.

Since i comment my own rop and set rop= in _vimrc, vim response is better in major part.
Using Tagbar is less slower
Vertical split of source then moving around is less slower
even cmd eg :e /some/long/path/to/something was slow and is now less slower.
Thank you Jürgen for this workaround.
My own rop, for instant commenté, was:
set rop=type:direct,
\gamma:1.0,
\contrast:1.5,
\level:0.0,
\geom:2,
\renmode:6,
\taamode:3
DirectxDiag
Under this Os Win, dxdiag shows me
Directx version 12.0
Main Driver version : 10.0.18362.329
Date: 6/21/2006
DDI Direct3D: 12
Functionality level: 12_1, 12_0, 11_1, 11_0, 10_1, 10_0,9 etc..
Driver model: WDDM 1.3
So, slow issue is it due to directx driver or rop ?
Thank you for your advise Jürgen.
Nicolas.


Error while deploying to GCLOUD

I get the Error
ERROR: (gcloud.preview.app.deploy) Error Response: [400] Invalid character in filename: node_modules/sitemap/env/lib/python2.7/site-packages/setuptools/script (dev).tmpl

Hi @dorshay6
Hm, seems like this file (env/lib/python2.7/site-packages/setuptools/script (dev).tmpl) is not from this project :)


Full optimization optimizes out randomization

As in the title: if I set engine.set_optimization_level(OptimizationLevel::Full) and then in the embedded scripts I have rand(1, 10), the engine will remove function call and will always produce the same random value in the for loop/function call.
For example, in Rhai:
fn test_fn() {
    for i in 0..10 {
        print(`Random value = ${rand(1, 10)}`);
    }
}

will produce
Random value = 1
Random value = 5
Random value = 10
Random value = 9
Random value = 4
Random value = 10
Random value = 4
Random value = 10
Random value = 10
Random value = 7

at default optimization level, and
Random value = 3
Random value = 3
Random value = 3
Random value = 3
Random value = 3
Random value = 3
Random value = 3
Random value = 3
Random value = 3
Random value = 3

at full optimization level.

I understand the concept of pure functions and the reasoning behind this problem, but I would not call it "by design". At best, it is a limitation of the optimizer, not a feature.
In any case, would it be possible to add a big warning section to the rhai-rand documentation and book section? Ideally, would be possible to add optimizer hints that the function is volatile in the future versions?

It probably is possible to mark the function as volatile...  But why can't the script be compiled before the library is loaded into the engine?
If that's inconvenient, it still is possible to keep two Engine's, one for compilation and one for execution.

I agree, it is totally possible, and now I did that, but it is really not obvious and a bit error-prone.

True in that respect.
I'll need to think a bit to decide whether it is good to introduce yet another flag to plugin functions, as there are already many.

But would not such flag useful for many use cases? Such as functions that should not be called during compilation, or get current time, as in the docs?
In any case, thank you for answering!

OK, you talked me into it.
I'll add volatile marker for plugin modules to the next version.  Then this will be solved.


Create 0000-01-02-trustonyu.md

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

Thank you @github-learning-lab !


Broken markup shortcuts for bold, italic, strikethrough in Slate text block

/Describe the bug
Markup shortcuts for inline formating (**text** for bold, *text* for italic and ~~text~~ for strikethrough) in slate text blocks do not work .
To Reproduce
Steps to reproduce the behavior:

Go to https://demo.plone.org/ (or any other page using Volto 17.x)
Edit a page
Add text block
Enter **text** and press space .
Text still formatted as normal text .

Expected behavior
Text should be formatted as bold.
Software (please complete the following information):

OS: ubuntu
Browser chrome
Volto Version 18.0.0-alpha.6
Plone Version 6.0.9

@07tAnYa Please don't work on issues that already have an open PR waiting for review.

@07tAnYa please read and follow Contributing to Plone and First-time contributors, especially Things not to do.


Variable decorators

ClassDecorator, PropertyDecorator, MethodDecorator, ParameterDecorator supported in typescript. All of them aimed class structure.
However, the following notation will be very useful. More javascript like code but powered with decorators.(Currently raises decorators are not valid here exception)
@ComponentDecl
var obj = {
//some object definition
}

@Log
function MyMethod() {

}

Why not just a function call? It is more flexible than decorator in TS.

There is a long discussion in the original decorator proposal about function declarations: https://github.com/Microsoft/TypeScript/issues/2249; one thing to note, what TypeScript has is an implementation to an existing  ECMAScript proposal, and we will not want to deviate from the proposal much specially in such an early stage.
And as @HerringtonDarkholme mentioned, using a function should achive what you want with a clearer semantics:
var obj = ComponentDecl()({
//some object definition
});

var MyMethod = Log()(function MyMethod() {

});


wlx-overlay-s: 0.4.1 -> 0.4.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for wlx-overlay-s is: Wayland/X11 desktop overlay for SteamVR and OpenXR, Vulkan edition
meta.homepage for wlx-overlay-s is: https://github.com/galister/wlx-overlay-s
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 0.4.2 with grep in /nix/store/a9d9k9yw4rg73n041j8yj8645r3dg087-wlx-overlay-s-0.4.2
found 0.4.2 in filename of file in /nix/store/a9d9k9yw4rg73n041j8yj8645r3dg087-wlx-overlay-s-0.4.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

wlx-overlay-s

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/a9d9k9yw4rg73n041j8yj8645r3dg087-wlx-overlay-s-0.4.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A wlx-overlay-s https://github.com/r-ryantm/nixpkgs/archive/afa35b5e7a63b1c82a79591b06a7829308e7be9e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/afa35b5e7a63b1c82a79591b06a7829308e7be9e#wlx-overlay-s

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/a9d9k9yw4rg73n041j8yj8645r3dg087-wlx-overlay-s-0.4.2
ls -la /nix/store/a9d9k9yw4rg73n041j8yj8645r3dg087-wlx-overlay-s-0.4.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

wlx-overlay-s

Maintainer pings
cc @Scrumplex for testing.

@NixOS/nixpkgs-merge-bot merge


Documentation updates

Beyond suggestions for improvement I had already mentioned at https://github.com/maxcountryman/jiff-cron/pull/4#discussion_r1824813337, documentation should be reviewed for remaining migration work.
E.g. the method documentation of Schedule::upcoming mentions "DateTime" and should be changed to referring to jiff's Zoned and linked.
Side note: Shouldn’t we re-export jiff? After all, jiff types are part of our public API.

Partially addressed by #4, will be closed by #16.