Session.Type misses characters randomly

Hi Christian,
I've been using your Sikuli wrapper for couple of months now and it's working out pretty well for us.
However, there's this issue that creates a lot of problem here..
We've noticed that randomly Session.Type command will miss entering characters..
Example:  Session.Type("abcdef") would type in "abcf" randomly and would work correctly other times.
I've tried to add a sleep also in between the click and type commands to see if it's related to timing, but it did not help.
Are you aware of this issue ?  I am using SikuliSharp 1.0.3 release.  Thanks much.

Hi @apahilaj1029
Did you test the same script in Sikuli directly?
For the record, I see you have created an issue here: https://answers.launchpad.net/sikuli/+question/186644 though your issue is slightly different... the original issue skips the first letters, yours skips the fourth and fifth...
What SikuliSharp does is simply sending the type command to Sikuli, and waiting for it to complete. There is no SikuliSharp interaction between letters, so if only some of them go through, there's not much that can be solved on the C# side.
To what kind of app are you trying to send the keys? Also, how often does it happen? Half of the time, just a few outliers?
What you could maybe do:

Try in Sikuli directly (e.g. using Jython), see if you have the same issue (then, the issue would be on Sikuli)
Enter individual letters with a "wait" command, see if that helps (then, diagnose the problem on the app side - maybe it can only buffer a few at a time)
Try upgrading to Sikuli 1.1.0 (and SikuliSharp 1.1.0), see if the issue persists

Hi Christian,
Thanks for responding.
I’ve used Sikuli in the past but haven’t seen this issue with it.
This is a Flash application we are trying to automate and this issue happens very frequently (although not 100% of the time) – there’s no rhythm or rhyme to it.
When you say enter individual letters with a wait, are you saying type one character, wait x seconds and then enter another character of the string ?  Example:
Session.Type(“a”);
Thread.Sleep(500);
Session.Type(“b”);
….
We are using Sikuli 1.0.1 currently – is it possible to just upgrade the SikuliSharp to 1.1.0 and leave Sikuli at 1.0.1. just to isolate this issue ?
As an fyi – we are trying a prototype a work around for this issue by simulating a Ctrl C, V commands to copy and paste the entire string buffer to the text elements instead of typing them to see if that helps.  It looks promising so far, but we have yet to roll it out to our entire suite to see how it works.
Thanks,
Arun
From: Christian Rondeau<EMAIL_ADDRESS>Sent: Monday, January 18, 2016 9:19 PM
To: christianrondeau/SikuliSharp
Cc: Pahilajani, Arun S
Subject: Re: [SikuliSharp] Session.Type misses characters randomly (#5)
Hi @apahilaj1029https://github.com/apahilaj1029
Did you test the same script in Sikuli directly?
For the record, I see you have created an issue here: https://answers.launchpad.net/sikuli/+question/186644 though your issue is slightly different... the original issue skips the first letters, yours skips the fourth and fifth...
What SikuliSharp does is simply sending the type command to Sikuli, and waiting for it to complete. There is no SikuliSharp interaction between letters, so if only some of them go through, there's not much that can be solved on the C# side.
To what kind of app are you trying to send the keys? Also, how often does it happen? Half of the time, just a few outliers?
What you could maybe do:

Try in Sikuli directly (e.g. using Jython), see if you have the same issue (then, the issue would be on Sikuli)
Enter individual letters with a "wait" command, see if that helps (then, diagnose the problem on the app side - maybe it can only buffer a few at a time)
Try upgrading to Sikuli 1.1.0 (and SikuliSharp 1.1.0), see if the issue persists

—
Reply to this email directly or view it on GitHubhttps://github.com/christianrondeau/SikuliSharp/issues/5#issuecomment-172710796.

There's no difference between SikuliSharp 1.0.1 and 1.1.0 but the support for Sikuli 1.1.0.
Here's what SikuliSharp does for the Type command:
var script = string.Format(
  "print \"SIKULI#: YES\" if type(\"{0}\") == 1 else \"SIKULI#: NO\"",
  text
  );

_runtime.Run(script, "SIKULI#: ", 0d);

As you can see, it simply runs the type command, so if it fails entirely or fails to follow up on the Type command, there may be something in SikuliSharp, but since it fails for some characters, but continues execution, it cannot be in SikuliSharp. Which is why I suggest trying with Sikuli 1.1.0 (everything should work as-is, as far as I know).
Otherwise, if the copy/paste approach works, good!

Thanks for sharing more information on the Type command…
As of now, our copy/paste approach is working fine for us – no missing of characters -if it starts acting up, I’ll upgrade SikuliSharp and Sikuli to 1.1.0 and give that a try.
Thanks for your time.
Thanks,
Arun
From: Christian Rondeau<EMAIL_ADDRESS>Sent: Tuesday, January 19, 2016 10:45 PM
To: christianrondeau/SikuliSharp
Cc: Pahilajani, Arun S
Subject: Re: [SikuliSharp] Session.Type misses characters randomly (#5)
There's no difference between SikuliSharp 1.0.1 and 1.1.0 but the support for Sikuli 1.1.0.
Here's what SikuliSharp does for the Type command:
var script = string.Format(
"print "SIKULI#: YES" if type("{0}") == 1 else "SIKULI#: NO"",
text
);
_runtime.Run(script, "SIKULI#: ", 0d);
As you can see, it simply runs the type command, so if it fails entirely or fails to follow up on the Type command, there may be something in SikuliSharp, but since it fails for some characters, but continues execution, it cannot be in SikuliSharp. Which is why I suggest trying with Sikuli 1.1.0 (everything should work as-is, as far as I know).
Otherwise, if the copy/paste approach works, good!
—
Reply to this email directly or view it on GitHubhttps://github.com/christianrondeau/SikuliSharp/issues/5#issuecomment-173076734.

Good! I'll close this issue, let me know if you find out more.


Rows built below first set of rows on table molecules not showing on preview pages

@michaelrivera03 unfortunately the way that table is implemented is pretty confusing.
When you go to create a Row you should click the Add Another button. To add columns, you should use the "Streamfield menu" that has things like RichText Blob, Textarea Blob, etc.
Additionally, in order for each of the columns to show, they need a corresponding Header. In your screenshot, you only have one header. If you added 2 more, you'd see the content you've added show up on the same Row that you created.
If you need more clarification, just reach out.


Example to get Gmail contacts

Hey there,
I have a fresh symfony 1.4.8 installed and installed the doctrine and melody plugins.
I want to get the list of gmail contacts for a user that is logged in to my app.
My settings are:
melody:
google:
key:                  xxx
secret:               xxx
callback:             @mymodule # or absolute url
  scope: contacts

  user:
    email_adress:
      call: me
      path: email
      key: true

this is in my template:
echo link_to('Connect to Gmail', '@gmailConnect')
and this in the according action:
public function executeConnect(sfWebRequest $request)
{
echo 'test';
$this->getUser()->connect('google');
}
public function executeGoogle(sfWebRequest $request)
{
$this->me = $this->getUser()->getMelody('google')->getMe();
}
When I click the link it redirects me to:
https://www.google.com/accounts/OAuthAuthorizeToken?
and on the Google page it says:
Invalid Token.
I am new to symfony and didn't completely understand the whole concept of this plugin and the necessary steps. Could please someone help my and provide an example or explain further?
Thanks a lot.

Hello JeJeJeRe,
Regarding your issue with the empty array which automagically fixed itself when you moved the project to production environment. Let me take a wild guess here, your dev environment is Windows while the production one Linux. I have been experiencing the same issue for a week now, even created an issue on sfMelodyPluginDemo and finally managed to solve it:
https://github.com/ElWardi/sfMelodyDemo/issues/1
The issue is related to the curl PHP library which does not have the cacerts file under Windows. More info can be found in the aforementioned thread. Hope it helps.


New YAML configuration for diagnostics analysis options

New YAML configuration for diagnostics analysis options
Addresses https://github.com/dart-lang/linter/issues/3319
Problem: confusing way to specify diagnostics options
Let's look at an example:
analyzer:
  errors:
    unused_element: ignore
    unused_import: warning
    dead_code: error
  language:
    - strict-casts
linter:
  rules:
    double_quotes: false
    single_quotes: true

Section by section:

analyzer/errors: In this section, we can set the severity of individual diagnostic codes. In the example, the unused_element Warning's severity is set to "ignore", the unused_import Warning's severity is set to "warning" (the diagnostic type, "Warning," is distinct from the severity, "warning"), and the dead_code Warning's severity is set to "error."
analyzer/language: In this section, we can enable three different "strict analysis modes": strict-casts, strict-inference, and strict-raw-types.
linter/rules: In this section, we can specify a list of lint rules to enable (distinct from the names of the diagnostics they produce), or a map, where each key is a lint rule name, and each value is true or false, enabling or disabling the lint rule.

There can be confusion around these three sections, as they seem to each serve approximately the same function: enabling and disabling diagnostics that are produced by the analyzer.
Proposal: a single section
I believe we can combine these three sections into a single one, placed at analyzer/diagnostics (or alternatively just a top-level diagnostics section). The above example would be written as:
analyzer:
  diagnostics:
    unused_element: false|disable
    unused_import: warning
    dead_code: error
    strict-casts: warning|enable
    double_quotes: false|disable
    single_quotes: warning|enable

Here's how it works:

The analyzer/diagnostics section must be a YAML map.
Each key is just a diagnostic name. In the case of Warning diagnostics, this can be a "shared name" (e.g. unnecessary_null_comparison or a "unique name" (e.g. unnecessary_null_comparison_always_null_false). In the case of Lint diagnostics, this can be a lint rule name, which acts as a shared name (e.g. invalid_runtime_check_with_js_interop_types), or can be a unique diagnostic name (e.g. invalid_runtime_check_with_js_interop_types_dart_as_js). The three "strict modes" will have to be changed to report diagnostics that have a shared name like strict_casts (or they could be refactored in a bigger way to just be like lint rules...).
There are four possible values: false, info, warning, and error.

false means "don't report this."
info, warning, and error mean, "do enable this, and report violations at this severity."

Alternative possible values: disable, enable, info, warning, and error.

disable means "don't report this."
enable means "do enable this, and report violations at the default severity."
info, warning, and error mean "do enable this, and report violations at this severity."

Alternatives
Using a YAML list
The analyzer/diagnostics section could be a list. This would allow specifying lint rules without a true/false/warning/whatever value:
analyzer:
  diagnostics:
    - unused_element: false
    - unused_import: warning
    - dead_code: error
    - strict-casts
    - double_quotes: false
    - single_quotes

I think this probably makes the syntax more confusing, and not much more terse. One benefit is that developers don't have to "choose" what severity lint rules are reported at (e.g. "warning").
Save the strict modes for later
It can be an incremental migration. Refactoring the strict modes may be a bigger effort. We could leave them in place, for a first phase of migrating to analyzer/diagnostics. The two sections which are most important to combine are analyzer/errors and linter/rules.
Migration
The migration would be incremental.

In one release, Dart 3.N, we introduce the analyzer/diagnostics section. It cannot be specified side-by-side with analyzer/errors or linter/rules, but the values can be merged with included files.

If a file with analyzer/diagnostics includes one-or-more files with analyzer/errors or linter/rules, the options are merged, not at the YAML level, but at the internal-representation level.
If a file with analyzer/errors or linter/rules includes one-or-more files with analyzer/diagnostics, the options are merged, not at the YAML level, but at the internal-representation level.
In this release, we also offer an assist to migrate the contents of an analysis options file from the old format to the new. (I guess we'd offer it for any file named *.yaml which has either an analyzer/errors section or a linter/rules section?

In the next release, Dart 3.N+1, we deprecate the old options. There is no change in the behavior of what options are parsed; only new warnings are reported in analysis options files.
We delay deprecating them for CI purposes. (Maybe this can be done between dev releases or flutter rolls... but tricky with the customer tests.)

In the next release, Dart 3.N+2, we stop respecting the old sections (and report the old sections as "unknown"?).

CC @dart-lang/analyzer-team @DanTup @parlough

No strong opinion but I love that we're revisiting making the configuration easier to use!

Overall I really like this, thanks!
Just a couple of comments / preferences.

In the case of Warning diagnostics, this can be a "shared name" ... or a "unique name" ...

We don't currently expose the unique name anywhere and I'd like to preserve that. The existence of a unique name is an implementation detail that allows us to tailor the message for a diagnostic to be more contextual, nothing more.

Alternative possible values: disable, enable, info, warning, and error.

I have a preference for this option because (a) I like that users can enable without specifying the severity and (b) I prefer 'disable' to 'false' as the way to disable a diagnostic.

Using a YAML list

If I understand YAML correctly, the value of the 'diagnostics' entry is a list of single entry maps. That seems less than ideal.
Also, I like that the simple map means that the structure can't have multiple equal keys.

Save the strict modes for later

I like the idea of making these diagnostics, but I'm also fine with making that migration later.

Alternative possible values: disable, enable, info, warning, and error.

+1 I think disable seems more understandable and explicit than false

The three "strict modes" will have to be changed to report diagnostics that have a shared name like strict_casts (or they could be refactored in a bigger way to just be like lint rules...).

Save the strict modes for later

+1 I love these modes but putting them in this new category in their current form does feel a little awkward. I think getting them in an ideal position, including one that the lints package might be happy including, is best left to more focused work later on.

Using a YAML list

I agree that mixing the two options is confusing, and just a map is likely better. I like requiring the specific enable or severity. It is a bit more typing, but I think completion makes it not so bad. Maybe a quick fix could be offered to add enable if a value isn't specified. Anyway, https://github.com/dart-lang/sdk/issues/52394 (or similar) would be my preferred way to edit the map.

In the next release, Dart 3.N+2, we stop respecting the old sections (and report the old sections as "unknown"?).

I think it might be worth 3.N+2 instead increasing the severity of the specific warning while still providing the assist/fix. I imagine some apps skip releases and developers going from no warning at all to just "unknown" would be confusing.

What about includes from packages?

You mention that they will be merged at the internal representation level, but will that support stay? There are many lint/analysis config packages out there with an upper SDK bound of Dart 4, so developers can continue to pull the outdated configs in after 3.N+2. If those included configs just stop working with no indication it might be confusing. Maybe a special diagnostic will be needed if an included file uses the old syntax?

Completion for diagnostic names:

Just a note, but one very small downside of this is losing the more specific completion suggestions for the rules property. I think lints are more likely to be configured, but there are a lot of non-lint diagnostics that might drown them out. Maybe they can be ranked higher?

Here is the existing issue for hover there https://github.com/dart-lang/sdk/issues/55592.

I like the idea, though I do worry this might make it less clear what are lints ...

I hadn't really thought about that, but the point is well taken.
On the other hand, the aspects that users can control about warnings and lints is the same: whether it's enabled and if so what the severity is. It does seem like the affordance for controlling those aspects should be the same.
One possibility would be to have separate maps for the two, something like
analyzer:
  diagnostics:
    warnings:
      unused_element: false|disable
      unused_import: warning
      dead_code: error
    lints:
      strict-casts: warning|enable
      double_quotes: false|disable
      single_quotes: warning|enable

(I didn't go look to see which were warnings and which are lints, I just wanted to show the structure I have in mind.)
I haven't decided whether I think that's better or worse, but it would make the distinction clear.

Perhaps we should ensure we have good hovers on all of the possible values here? (we already show the lint docs in completion for lint names, though I don't think on hover - but we probably should).

That would be good. We have been working for a while to have two separate pieces of documentation for lints: one that explains what it does and why you might want to enable it (which is presumably what we'd show here), and another that explains what's wrong at the location where a diagnostic was produced. We only have the second form of documentation for warnings. We hadn't really thought about explaining what the warning does and why you shouldn't disable it, but maybe we should?

if so, we might want to ensure they are annotated in some way so it's clear one is a group of the others?

That's exactly the kind of confusion I don't want to cause users, which is why I'm strongly opposed to allowing unique names to be used at all. The "shared" name isn't the name of a group or category of diagnostics, it's the name of a single diagnostic. The existence of the unique name just allows us to have messages that are better tailored to the specifics of the problem being reported. Let me give three examples.
We sometimes have multiple messages in order to provide more context:

Extending 'Function' is deprecated.
Mixing in 'Function' is deprecated.

The problem is the same, the class Function is being used in a way that is no longer allowed. The different messages just indicate how it's being used.
Sometimes there is optional information associated with a diagnostic, so we end up with multiple messages:

'{0}' is deprecated and shouldn't be used.
'{0}' is deprecated and shouldn't be used. {1}

The second is used when the constructor is used and a message is included (@Deprecated('Use bar instead.')). The problem isn't different. In both cases the issue is that a declaration that is deprecated is being used in some way when it shouldn't be.
Sometimes we use multiple messages when the amount of information to be communicated is different:

The '{0}' directive is missing a '{1}' argument.
The '{0}' directive is missing a '{1}' and a '{2}' argument.
The '{0}' directive is missing a '{1}', a '{2}', and a '{3}' argument.

Again, the problem is the same: a doc directive is missing some required information. The different messages just allow us to correctly express the case when the number of pieces of information is different.
In none of these cases would it make sense for a user to enable one message and not another. It's a single diagnostic with multiple messages.
If there are cases where it would make sense for one message to be enabled and another not then it's an indication that they are different problems and should be different diagnostics with different (shared) names.

On the other hand, the aspects that users can control about warnings and lints is the same: whether it's enabled and if so what the severity is. It does seem like the affordance for controlling those aspects should be the same.

Do we intend/expect the distinction between lints/built-in-warnings to remain or be something users care about? It feels a little odd to put two different things into the same list, but if the differences between those is ultimately just an implementation detail (where the code lives), then perhaps the documentation for the two should also be combined?
For example, if I open a project I've not worked on before and I see an interesting looking rule name I've not seen before, how do I know where to go and look for the documentation (assuming no IDE hover)? It feels odd to have to search two places even if it's not a lot of effort.

That's exactly the kind of confusion I don't want to cause users, which is why I'm strongly opposed to allowing unique names to be used at all.
...
If there are cases where it would make sense for one message to be enabled and another not then it's an indication that they are different problems and should be different diagnostics with different (shared) names.

This sounds better to me too.

@DanTup @bwilkerson Do we currently still have no auto-complete in analysis_options.yaml, because we don't have good "broken" / "in-progress" YAML file support?
I think some usability issues can really be aided by some IDE tooling like:

auto-complete lint diagnostic and warning diagnostic names
auto-complete values (enable, warning, etc.)
ctrl-click support on lint diagnostic and warning diagnostic names; either to some code file like lint_codes.g.dart, or opening a link externally in the browser.

Do we intend/expect the distinction between lints/built-in-warnings to remain or be something users care about?

It's my belief that, from a user's point of view, the only difference between a warning and a lint is that the former is enabled by default and the latter is disabled by default. Don't misunderstand, I do think that the difference is important, but I think that's the only difference that users care about.
When we moved the code for lints from a separate package to being inside the SDK repo no user noticed the change.

Do we currently still have no auto-complete in analysis_options.yaml, because we don't have good "broken" / "in-progress" YAML file support?

We have auto-completion support in all of our YAML files: analysis options, pubspec, and even fix data. Sometimes it fails to work because of the lack of recovery in the YAML parser we use, but if you go to a linter/rules list, enter a new element by typing a -, then you can get suggestions even if you haven't started typing a lint name.

I think some usability issues can really be aided by some IDE tooling ...

I agree. I haven't tried implementing the ability to navigate from some location in a YAML file to an external web site, but it would be a nice feature if you could. Having the same information in a hover would be a second-best option.

ctrl-click support on lint diagnostic and warning diagnostic names; either to some code file like lint_codes.g.dart, or opening a link externally in the browser.

I don't know if Ctrl+Click to a website would feel good in VS Code, but we can include links in the hover (although if we also show all the information from the website in the hover, that might be redundant).

It's my belief that, from a user's point of view, the only difference between a warning and a lint is that the former is enabled by default and the latter is disabled by default. Don't misunderstand, I do think that the difference is important, but I think that's the only difference that users care about.

That distinction is probably also a bit blurry given the lint packages.. If you use the project templates that reference these packages, what is "enabled by default" and "on the diagnostic page instead of the lint page" probably don't seem to match up.

For the opening of links about the lints, there is this issue https://github.com/Dart-Code/Dart-Code/issues/2785. Maybe we could move it here to the SDK?

Some of the options for implementing that could be done entirely from the server (for ex. links in hovers), but something like a context menu would probably also (or instead) require work in the VS Code extension. I feel like hovers might be the better solution though (a single implementation could work across more editors), so it could be worth having an issue here to discuss/agree.


Fix intermittent test failure in BallerinaStreamsV2TimeAccumulatingWindowTest

Purpose
This pr fixes #13702 .
Approach
Re-design the window to use the streams:scheduler and got rid of EXPIRED events and used RESET event instead

Codecov Report

Merging #13761 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master   #13761      +/-   ##
============================================
+ Coverage     65.14%   65.14%   +<.01%
  Complexity      426      426
============================================
  Files          2116     2116
  Lines         94178    94178
  Branches      12492    12494       +2
============================================
+ Hits          61349    61352       +3
+ Misses        27844    27842       -2
+ Partials       4985     4984       -1

Impacted Files
Coverage Δ
Complexity Δ

...mantics/analyzer/StreamsQuerySemanticAnalyzer.java
86.3% <100%> (+0.08%)
0 <0> (ø)
:arrow_down:

...lang/compiler/desugar/StreamsPreSelectDesuagr.java
94.37% <100%> (+0.5%)
0 <0> (ø)
:arrow_down:

...allerinalang/net/jms/LoggingExceptionListener.java
50% <0%> (-50%)
0% <0%> (ø)

...java/org/ballerinalang/stdlib/task/timer/Stop.java
77.77% <0%> (-22.23%)
0% <0%> (ø)

...va/org/ballerinalang/stdlib/task/TaskExecutor.java
65.38% <0%> (-11.54%)
0% <0%> (ø)

...va/org/ballerinalang/channels/ChannelRegistry.java
94.59% <0%> (-2.71%)
0% <0%> (ø)

...in/java/org/ballerinalang/bre/bvm/BVMExecutor.java
89.38% <0%> (-1.77%)
0% <0%> (ø)

...a/org/ballerinalang/bre/bvm/GlobalMemoryBlock.java
78.43% <0%> (-0.99%)
0% <0%> (ø)

...inalang/compiler/desugar/StreamingCodeDesugar.java
97.01% <0%> (+0.11%)
0% <0%> (ø)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

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


QA: eVDC funationality - tester 3

Product Attributes
Product is defined in a mindmup.
Description: Kubernetes compatible virtual datacenter that is deployable in minutes everywhere in the world on TF Grid capacity
Attributes:

secure
everywhere
accessible
flexible
scalable

Product Components
What is this software product made off, what are the components? Examples: Search bar, filtering, geolocation, etc...

[ ] eVDC login (ThreeFold Connect authenticator)

[ ] splash screen (list compute nodes)

[ ] click compute nodes

[ ] download  and save kubeconfig file

[ ] cp kubeconfig to be the default kubeconfig file (.kube/config)

[ ] execute kubectl get nodes.  See list of nodes?

[ ] add worker node (by pressing "add node"

[ ] select size -> next

[ ] make payment with external wallet

[ ] click storage nodes

[ ] click zdb's info -> download and store information

[ ] click z-store config -> download and store information

[ ] click wallet information

Product Capabilities
What does this software product do? Examples:  Save to favorites, make payments, write and read reviews, etc.

product launches and operates a standard controller and worker kubernetes cluster

[ ] test some standard kubernetes commands.  Explanation of the commands and updated information are here: https://opensource.com/article/20/5/kubectl-cheat-sheet

[ ] kubectl get nodes

[ ] kubectl get ns

[ ] kubectl get pods -n kube-system

[ ] kubectl create ns hello-there

[ ] kubectl create cronjob my-cron --image=busybox --schedule="*/5 * * * *" -- echo hello

[ ]  kubectl edit cronjob/my-cron

As I don't have proper permissions to assign, claiming this slot by comment.

As I don't have proper permissions to assign, claiming this slot by comment.

Tested on Devnet on Friday 1/15/2021
Go into VDC, pops up with red message that it will expire and need to fund a given address (a little scary/not user friendly, should provide a link or QR code to fund. Looks like better payment experience is planned for this, per #1915).
Pop up says "14 hours" while the wallet page says that it expires on 30/01/2021, 09:15:45 when today is 15/01/2021 at 19:50 local time (Opened issue #2295 for this).
Ran kubectl get nodes
NAME         STATUS   ROLES    AGE   VERSION
k3os-28100   Ready    master   20m   v1.19.4+k3s1
k3os-27338   Ready    <none>   19m   v1.19.4+k3s1

Can't verify these ^ against info shown in web interface
Added a node, selected "medium". This costs more than the initial deployment... not sure why but assume it's for a longer time period (time periods being paid for is not clear throughout). No option for "small", even though the first worker I get is smaller than medium 2cpu/4gb vs 4/8. No way to escape from extend chatflow back to VDC screen (or rather not obvious that hitting the logo in upper left with accomplish this)
"Your VDC kubie has been extended successfuly" better to say "expanded"
kubectl shows the new node
Delete the node... "Are you sure you want to delete worker, this action can't be undone?" (move question mark to the comma, add period)
Looks like the funds I added for the new node are kept and applied to remaining nodes, but this isn't communicated.
Running some basic kubectl commands
kubectl get ns
NAME              STATUS   AGE
default           Active   39m
kube-system       Active   39m
kube-public       Active   39m
kube-node-lease   Active   39m
k3os-system       Active   39m

kubectl get pods -n kube-system
NAME                                     READY   STATUS      RESTARTS   AGE
metrics-server-7b4f8b595-qc279           1/1     Running     0          39m
local-path-provisioner-7ff9579c6-rp7sd   1/1     Running     0          39m
coredns-66c464876b-lgngv                 1/1     Running     0          39m
helm-install-traefik-j6jwq               0/1     Completed   0          39m
svclb-traefik-8vxfb                      2/2     Running     0          37m
svclb-traefik-7mhkb                      2/2     Running     0          37m
traefik-7f489654dc-pllnd                 1/1     Running     0          37m
svclb-traefik-jjvt7                      2/2     Running     0          8m5s

Downloaded ZDBS Info and Z-Stor Config
Confused about relationship between the disks of the worker nodes and the storage nodes. Total capacity of storage nodes not displayed.
kubectl get pods -n k3os-system
NAME                                         READY   STATUS    RESTARTS   AGE
system-upgrade-controller-6c9f84cb79-pb6w4   1/1     Running   0          46m

kubectl create cronjob my-cron --image=busybox --schedule="*/5 * * * *" -- echo hello
cronjob.batch/my-cron created

Edited, then deleted cron job.
Deploying from Marketplace and Command Line
Deployed Kubeapps
Chose silver (CPU 1000m [what does this little "m" mean?] - Memory 1024Mi)
Provided an access token for Kubeapps, but it isn't clear if I need to save this now or where I can access it again later.
Didn't try deploying anything from Kubeapps
Managed to launch a Presearch node container with the following command, and the node received and executed a search. Cool!
kubectl run --attach psnode --image=presearch/node --env="REGISTRATION_CODE=CODE"
This isn't quite equivalent to the docker command provided by Presearch shown below, as it doesn't provide the storage volume which is a bit more complicated to add in K8s.
docker run -it --rm -v presearch-node-storage:/app/node --name presearch-node -e REGISTRATION_CODE=CODE presearch/node

Tested on Devnet on Friday 1/15/2021
Go into VDC, pops up with red message that it will expire and need to fund a given address (a little scary/not user friendly, should provide a link or QR code to fund. Looks like better payment experience is planned for this, per #1915).
Pop up says "14 hours" while the wallet page says that it expires on 30/01/2021, 09:15:45 when today is 15/01/2021 at 19:50 local time (Opened issue #2295 for this).
Ran kubectl get nodes
NAME         STATUS   ROLES    AGE   VERSION
k3os-28100   Ready    master   20m   v1.19.4+k3s1
k3os-27338   Ready    <none>   19m   v1.19.4+k3s1

Can't verify these ^ against info shown in web interface
Added a node, selected "medium". This costs more than the initial deployment... not sure why but assume it's for a longer time period (time periods being paid for is not clear throughout). No option for "small", even though the first worker I get is smaller than medium 2cpu/4gb vs 4/8. No way to escape from extend chatflow back to VDC screen (or rather not obvious that hitting the logo in upper left with accomplish this)
"Your VDC kubie has been extended successfuly" better to say "expanded"
kubectl shows the new node
Delete the node... "Are you sure you want to delete worker, this action can't be undone?" (move question mark to the comma, add period)
Looks like the funds I added for the new node are kept and applied to remaining nodes, but this isn't communicated.
Running some basic kubectl commands
kubectl get ns
NAME              STATUS   AGE
default           Active   39m
kube-system       Active   39m
kube-public       Active   39m
kube-node-lease   Active   39m
k3os-system       Active   39m

kubectl get pods -n kube-system
NAME                                     READY   STATUS      RESTARTS   AGE
metrics-server-7b4f8b595-qc279           1/1     Running     0          39m
local-path-provisioner-7ff9579c6-rp7sd   1/1     Running     0          39m
coredns-66c464876b-lgngv                 1/1     Running     0          39m
helm-install-traefik-j6jwq               0/1     Completed   0          39m
svclb-traefik-8vxfb                      2/2     Running     0          37m
svclb-traefik-7mhkb                      2/2     Running     0          37m
traefik-7f489654dc-pllnd                 1/1     Running     0          37m
svclb-traefik-jjvt7                      2/2     Running     0          8m5s

Downloaded ZDBS Info and Z-Stor Config
Confused about relationship between the disks of the worker nodes and the storage nodes. Total capacity of storage nodes not displayed.
kubectl get pods -n k3os-system
NAME                                         READY   STATUS    RESTARTS   AGE
system-upgrade-controller-6c9f84cb79-pb6w4   1/1     Running   0          46m

kubectl create cronjob my-cron --image=busybox --schedule="*/5 * * * *" -- echo hello
cronjob.batch/my-cron created

Edited, then deleted cron job.
Deploying from Marketplace and Command Line
Deployed Kubeapps
Chose silver (CPU 1000m [what does this little "m" mean?] - Memory 1024Mi)
Provided an access token for Kubeapps, but it isn't clear if I need to save this now or where I can access it again later.
Didn't try deploying anything from Kubeapps
Managed to launch a Presearch node container with the following command, and the node received and executed a search. Cool!
kubectl run --attach psnode --image=presearch/node --env="REGISTRATION_CODE=CODE"
This isn't quite equivalent to the docker command provided by Presearch shown below, as it doesn't provide the storage volume which is a bit more complicated to add in K8s.
docker run -it --rm -v presearch-node-storage:/app/node --name presearch-node -e REGISTRATION_CODE=CODE presearch/node

Tested on testnet on Monday 8/02/2021

all above checks are done successfully

deploy a small web app on cluster using NodePort, working well as below

➜  ~ kubectl create deployment web --image=gcr.io/google-samples/hello-app:1.0
deployment.apps/web created

➜  ~ kubectl expose deployment web --type=NodePort --port=8080
service/web exposed

➜  ~ kubectl get service web
NAME   TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)          AGE
web    NodePort   <IP_ADDRESS>   <none>        8080:31172/TCP   6s

➜  ~ curl  http://<IP_ADDRESS>:31172
Hello, world!
Version: 1.0.0
Hostname: web-79d88c97d6-tqm4s

There is two issues

still there is issue, no maching between notified message about expire period when login to created VDC as below picture and expire date on listing the VDCs. note today is 8 Feb

below is expire date on listing the VDCs

2.small issue: i delete a node from cluster using VDC GUI but still shown on kubctl command as NotReady as below picture, i have (1 master and 1 worker )

while in command line shown as ( 1 master and 2 worker ) , still the second worker exist but not ready status

not sure if above is issue or not

Installing peertube from marketpalce not working as below
choose Peertube --> (bishoypeertube) --> choose subdomain for me on a getway --> Sliver --> (got error)

All taken into separate issues and fixed.


Read commit id from local

This is particularly useful when I am checking out several different commits.

I am not sure why this is failing.

@rhysd Would appreciate if you could help me here.

Hi, I also need this feature for something like #24
Is there a way I can help to get this PR merged?


Replace usage of find & findIndex with other methods to support IE & PhantomJS

After debugging quite a while I have noticed that the mocking does not work with IE & PhantomJS unless there is a polyfill for find and findIndex. I have replaced the occurrences with other methods supported in all browsers.

Hi @MasterCassim, why have you reverted changes in Mock.ts? We need to discuss that with @NagRock, I think a nicer solution would be to introduce required polyfills.

I reverted these changes because they were on classes which support the find; I have incorrectly modified the calls.

Codecov Report

Merging #88 into master will decrease coverage by 0.12%.
The diff coverage is 85.71%.

@@            Coverage Diff             @@
##           master      #88      +/-   ##
==========================================
- Coverage   94.58%   94.45%   -0.13%
==========================================
  Files          35       35
  Lines         609      613       +4
  Branches       69       70       +1
==========================================
+ Hits          576      579       +3
- Misses         24       25       +1
  Partials        9        9

Impacted Files
Coverage Δ

src/MethodStubCollection.ts
96.55% <85.71%> (-3.45%)
:arrow_down:

Continue to review full report at Codecov.

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


[BUG]refine comp creation successful message

✗ bin/vela comp run -t webservice poc --image nginx:latest
Creating App poc
SUCCEED

Maybe App should be renamed to Comp?

fixed


[#13901] Implement accessors via derive_ppx

Explain your changes:

Removed accessors, instead now there's [@@derive field]

Explain how you tested your changes:

CI will test

Checklist:

[ ] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them

Closes #0000

!ci-build-me

!ci-build-me

!ci-build-me

I would suggest to wait for https://github.com/MinaProtocol/mina/pull/14207 to be merged, remove the second commit of this branch and rebase on develop. We can then merge.

!ci-build-me

!ci-build-me

!ci-build-me


Add v2/tooltip

@therealemjy I don't see the same color issue any more. I believe it was fixed in this commit a14c8ed


Change the comments highlighting color from dark green to light green

The comments highlighting color is a bit hard to look at since it is dark. I want it to be light.
If there's a different usage for light green  already please forgive me.

If you can't find a color theme that suits you better then you can customize individual colors of any theme. See https://code.visualstudio.com/api/extension-guides/color-theme#syntax-colors and subsequent sections.

Is this for the Dark+ (Default) Theme?
Sorry, no changes planned there as changes affect many users that might not like the change.
As mentioned by John, you can customize the theme in the settings or check out one of the many themes available on the marketplace.

Is this for the Dark+ (Default) Theme?  Sorry, no changes planned there as changes affect many users that might not like the change.
As mentioned by John, you can customize the theme in the settings or check out one of the many themes available on the marketplace.

I'll make an extension for those who are interested: https://github.com/colors-extension-vscode


Switching to using dotnet generations TFM

cc @davidfowl

What is dotnet5.4? :confused:

:shipit:

@khellang it's something new and amazing :smile: Stay tuned to the https://github.com/aspnet/Announcements/issues/ repo regarding this.


Fix comment about shape

I've fixed comment above :shape in BarSeries following validation.
Please see it. Thank you.

Thanks! This has been fixed in caxlsx: https://github.com/caxlsx/caxlsx/commit/75cec07c4


Upgrade to Xcode 8.1, fix warnings

Any specific reason for this？Cuz Xcode gives warnings about 'iPhone Developer'

It was added here
https://github.com/SwiftyJSON/SwiftyJSON/pull/682/files
maybe @mokagio have more context here.

@mokagio Bump. Can you give more context on the changes of your PR and why it creates warnings in 8.1? Thank you!

Closing. As of Xcode 8.2 recommend settings in #764
Thanks everyone. 🙏


How to bypass or disable authenticator for Google account

I know the password of my gmail address. No recovery code and recovery email address and recovery phone number are not registered. It was only protected by authenticator and password. My phone malfunctioned, I had to do a soft reset. I didn't have an Authenticator backup. So I can't login to my gmail account. My important documents were in my drive account. I need access. I wonder if there is a web app so I can bypass or disable gmail authenticator and only login with password? How can I recover? Can this be done with the app?

No, I'm afraid not - you need to be able to log in to your account to use this proxy.


Object data limit for the encoder?

Is there a limit in data that the encoder can handle? I have a function that returns 7368 objects but the JSON encoder does not return any data.
Code snippet

public function getDataFunction() {
    //Create encoder
    $encoder = Encoder::instance($some_classes, new EncoderOptions(JSON_PRETTY_PRINT,    $some_url_link));

    //Get data
    $objects = self::getData();

    //Create assay instances
    $data_arr=array();
    foreach($objects as $object){
        $data = \Model\Data::instance($object);
         array_push($data_arr, $data);
    }

    //return 7368 objects
    echo count($data_arr);

    //Return json
    return $encoder->encodeData($data_arr);
}

Return result (curl)
HTTP/1.1 200 OK
Date: Mon, 27 Mar 2017 10:46:35 GMT
Server: Apache/2.4.18 (Unix) OpenSSL/1.0.2g PHP/5.5.34 mod_perl/2.0.8-dev Perl/v5.16.3
X-Powered-By: PHP/5.5.34
Content-Length: 4
Content-Type: text/html; charset=UTF-8

7368

When executing a curl request to this function it returns nothing. Other functions (that generates less data) returns data perfectly (same principle).
I also can't find any error logs.
Kind regards,
Wouter

No limit. Finally found the error (was in my part of code). Sorry!


Fixes #3340. Mouse ButtonShift doesn't work anymore on Windows Terminal.

Fixes

Fixes #3340

Proposed Changes/Todos

[x] Change to the ButtonCtrl instead of the ButtonShift
[x] Add unit test to proof

Pull Request checklist:

[x] I've named my PR in the form of "Fixes #issue. Terse description."
[x] My code follows the style guidelines of Terminal.Gui - if you use Visual Studio, hit CTRL-K-D to automatically reformat your files before committing.
[x] My code follows the Terminal.Gui library design guidelines
[x] I ran dotnet test before commit
[x] I have made corresponding changes to the API documentation (using /// style comments)
[x] My changes generate no new warnings
[x] I have checked my code and corrected any poor grammar or misspellings
[x] I conducted basic QA to assure all features are working

##Screenshots
https://github.com/gui-cs/Terminal.Gui/assets/13117724/74905d7f-3ce9-41b3-a317-37668e4435e8
The reason why ButtonShift doesn't work anymore on Windows Terminal is because it needed to use that button to disable the mouse from the CLI and use in the terminal to selecting text and it ignores the Win32 API that enable the CLI using that resources. But unfortunately I seeing even more theses procedures which make me question "Should I pay for a system that brakes certain features the users used and now they can't"

Just so I understand, the Windows Terminal team changed the behavior and apps no longer get ButtonShift events?
Do you know when they made this change?

Just so I understand, the Windows Terminal team changed the behavior and apps no longer get ButtonShift events?

They use the ButtonShift internally t manage the text selection on the Windows Terminal and now Terminal.Gui doesn't get that event.

Do you know when they made this change?

I realized this has been going on for a long time, maybe more than a year. In Linux ButtonShift is also used internally.
But I think the ButtonCtrl is better and more stable.


bug: Content overflowing

The content in the navigation bar under "Learning Paths" is overflowing horizontally, causing the last few items to be cut off.
Steps to Reproduce:
Navigate to the "Learning Paths" section.
Observe that the list of options in the navigation bar extends beyond the visible area, leading to overflow.

It will be fixed after #532 is merged.

Should be fixed


Template Install

someone tell me how can i install the template? Pleasee..

Look this - https://github.com/trydalcoholic/opencart-materialize/blob/master/docs/Documentation_Materialize_Template_ENG.pdf

hi, I try install theme on localhost (xampp-win32-7.2.12-0-VC15) win 10 64, but not work, Some advice?

seem like the style css file is not accessible

I follow the steps from documentation but  I thing sonting is wrong. please help me!

Check your config.php file and correct website url.


feat(blockquote): add rh-blockquote

What I did

Built a component for rh-blockquote based off of the design specs located at https://xd.adobe.com/spec/3e62e93c-8338-4f31-5040-3b81f0ed5c71-4853/screen/f5c8e80c-83cb-4ae9-8e92-5991c39e738b/specs/.

Issue Link
#319
Testing Instructions
1.Running npm run start will display the blockquote in a simple docs view after you select the component in the left nav.
Notes to Reviewers

@Nouveau make sure to add a changeset

We should use the design tokens in blockquote's css
we can do that in a subsequent PR if not here, so don't fret :)

@marionnegp The dark theme should be working correctly now. Could you give this another look? I think all of the items have been resolved.

The 8px border can stay as is!

@Nouveau Please merge in the latest main. you can avoid the conflict by just deleting the package lock first.
Make sure to squash before merging, though, using the github UI

Per @bennypowers

[ ] Rename rh-blockquote.e2e.spec.ts to rh-blockquote.e2e.ts

@Nouveau please add yourself to the contributors list in package.json


Remove nop container and image

Changes

The nop-image argument describes it as "The container image run at the end of the build to log build success", however currently it just runs immediately on pod start. I'm guessing this is due to the initContainer -> container change.
~This PR adds the nop image to the steps so that the entrypointer can apply to the nop container. Critically, this is required for the sidecar workaround described here: https://github.com/tektoncd/pipeline/issues/701#issuecomment-478794545.~
This PR removes the nop image/container since it is no longer necessary.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[ ] Commit messages follow commit message best practices

See the contribution guide
for more details.
Release Notes

No? I don't think the nop container was really part of the user facing API/contract.

/ok-to-test

Good call @dicarlo2 ! Now that you mention it, we should actually be able to completely get rid of the nop container now that we're not using init containers for the steps!
afaik the reason we had this container was b/c we needed to have at least one container to actually run a pod. now that we're using actual containers, we should be able to completely remove it!
im happy to do this in 2 phases if you want @dicarlo2 , we could merge this first, then in another PR remove the container (and the code for the image even!) but if you want to go straight to removing the container + image entirely that'd be cool too :D

@bobcatfish went ahead and removed the nop container/image entirely. I realized that the workaround I was thinking of doesn't actually require the nop container at all.

/hold
This image might actually be useful long-term for managing sidecars - working on a small PoC to show how. (The tests failed anyways, but just in case someone retests and they pass)

See https://github.com/tektoncd/pipeline/pull/728


Sixel supported, but not listed in device atributes

Hiii, just trying to use lsix on st, and I've realized that sxel isn't in device atributes. Could you possibly add it? Thanks

@alabnt lsix should work now

Ty


Fetch latest translations

Coverage remained the same at 29.409% when pulling b0eb9903fbef4b1ed3b55d90ce157a625bc12ac4 on qingweibinary:qingwei/update_translation into 3a7040760e84b0fee5c05673bb4bb10d7559c5ce on binary-com:master.


build: Share code between multiple dart_frog projects in a monorepo

Description
I'm looking for a way to share code between multiple dart_frog projects inside a monorepo, using local dependencies.
The current solution for sharing code between server and client seems to be to place the shared code inside the server project. (https://github.com/VeryGoodOpenSource/dart_frog/issues/410#issuecomment-1303707714) That solution works fine, since a Flutter project can import code outside of its own folder.
This solution does however not work when sharing code between two dart_frog projects, since one of the projects will always have to import from outside its folder (unless you nest all projects that depend on shared code).
I have thought about a few different possible solutions to this. The first is to use symlinks, but soft links don't work with Docker, and hard links don't work with git. The other option I can come up with is to be able to set a custom docker build context, since – as far as I understand it – that is the cause of this limitation.
I don't have an idea for how this could be implemented at a technical level, but it is possible to specify the docker file location and build context separately. For example:
docker build ../ -f path/to/docker file
That would allow for a file structure like this:
frog_1
frog_2
shared_code
client

Of course, this would require changing the |Dockerfile based on the build context and folder names. It would also be necessary to be able to specify the path to the build context in some way.
Requirements

[ ] Allow importing from outside the project
[ ] Allow specifying the docker build context

This issue is mostly intended as a starting point for a discussion of how this can be solved, and I am by no means saying that my proposed solution is the best one. I'm sure that the developers working on dart_frog have thought about this before. I would love to hear those thoughts, and if I have missed something.
This is quite an important feature for us, so I would be really happy if a solution can be found.

I haven't tested it myself yet, but has this been fixed by https://github.com/VeryGoodOpenSource/dart_frog/pull/910? I noticed that the issue was closed and then reopened.

Hi @Hannnes1 , I'm sorry for the confusion. This feature was fixed with #910, however the issue was reopened because it was yet to be released. You should now be able to use it with Dart Frog CLI latest version 🙌

Great, thanks!


Cleanup unused files

We accumulated a lot of images, scripts, and scenes that are no longer used. I did the best I could to make sure all the files deleted truly weren't necessary, and all remaining files are.
This cleanup can be really valuable especially for new contributors. There were a lot of scripts that could act as red herrings as they would look like they performed necessary functions, but actually were never used.

TODO: Alpha slider under the Color tab of the Screen Object settings is unused and hidden. It should be deleted.


Update Flight Hub to include latest 20H1 builds

Added Server for build 19023 which was published on 11/19/2019

PR closed as the change is in https://github.com/MicrosoftDocs/windows-insider/commit/1eec57a64aac37054ca43400900089b0a02c9af6


Create css changes for safe mode

Make it visually obvious for people that they are in safe mode.

progress: Navbar background and button are changing according to the safe mode state

Task completed, will reopen for review at end of project


Sample autogenerate code implementation with Helm sample

Description of the change:

Implementation for we are able to auto generated samples with its utils cleanup
Memcached Helm sample generate

(NOTE): The usage of the sample in the e2e tests will be made in a follow-up and are not part of the context of this PR. We need just the e2e tests since the samples have been gen using the chart when in the e2e tests are done with another scenario where no chart is informed.
Motivation for the change:
https://github.com/operator-framework/enhancements/pull/47
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

/hold
It can be reviewed but let's wait for the EP get merged.

Hi @jmrodri,
Really thank you for your review. All applied. Feel free to re-check it.

the lgtm was lost just because it was rebased with master.

/lgtm

/hold cancel


Suggestion for autoOrient()

I encountered an issue today with autoOrient() that I have never had come up before. Somebody tried to upload a jpg file and it threw an error that $exif['Orientation'] was not defined. Odd, but, uh, ok.
Anyway, right after the line $exif = $this->getExif();, might I suggest adding the following:
	if ( empty($exif['Orientation']) ) {
	    return $this;
	}

Do not really feel like doing a whole pull/request for this simple change, but still thought I should suggest it to ya @claviska .

Probably a notice — I usually disable them so they fall through the cracks. Easy fix :)

This block will prevent this issue.


[18.03] postfix: 3.2.5 -> 3.2.6

Motivation for this change
Release notes: http://www.postfix.org/announcements/postfix-3.3.1.html
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

cc @rickynils

eval looks stuck, let's try again
@GrahamcOfBorg eval

Success on aarch64-linux (full log)
Attempted: postfix
Partial log (click to expand)
stripping (with command strip and flags -S) in /nix/store/yywk96767ndawv0z4cfjy8dllqwvm04k-postfix-3.2.6/libexec  /nix/store/yywk96767ndawv0z4cfjy8dllqwvm04k-postfix-3.2.6/bin  /nix/store/yywk96767ndawv0z4cfjy8dllqwvm04k-postfix-3.2.6/sbin
patching script interpreter paths in /nix/store/yywk96767ndawv0z4cfjy8dllqwvm04k-postfix-3.2.6
/nix/store/yywk96767ndawv0z4cfjy8dllqwvm04k-postfix-3.2.6/libexec/postfix/.postfix-script-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/lnws52qanbi5vz8qg24v4ym57nznfndg-bash-4.4-p12/bin/sh"
/nix/store/yywk96767ndawv0z4cfjy8dllqwvm04k-postfix-3.2.6/libexec/postfix/.post-install-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/lnws52qanbi5vz8qg24v4ym57nznfndg-bash-4.4-p12/bin/sh"
/nix/store/yywk96767ndawv0z4cfjy8dllqwvm04k-postfix-3.2.6/libexec/postfix/postfix-wrapper: interpreter directive changed from "/bin/sh" to "/nix/store/lnws52qanbi5vz8qg24v4ym57nznfndg-bash-4.4-p12/bin/sh"
/nix/store/yywk96767ndawv0z4cfjy8dllqwvm04k-postfix-3.2.6/libexec/postfix/postmulti-script: interpreter directive changed from " /bin/sh" to "/nix/store/lnws52qanbi5vz8qg24v4ym57nznfndg-bash-4.4-p12/bin/sh"
/nix/store/yywk96767ndawv0z4cfjy8dllqwvm04k-postfix-3.2.6/libexec/postfix/postfix-tls-script: interpreter directive changed from "/bin/sh" to "/nix/store/lnws52qanbi5vz8qg24v4ym57nznfndg-bash-4.4-p12/bin/sh"
checking for references to /build in /nix/store/yywk96767ndawv0z4cfjy8dllqwvm04k-postfix-3.2.6...
moving /nix/store/yywk96767ndawv0z4cfjy8dllqwvm04k-postfix-3.2.6/sbin/* to /nix/store/yywk96767ndawv0z4cfjy8dllqwvm04k-postfix-3.2.6/bin
/nix/store/yywk96767ndawv0z4cfjy8dllqwvm04k-postfix-3.2.6


Storageoption for values

Hello,
I cant choose "file" as storage option. I wish to safe values to a file instead of memory or temp workspace. I case the system crashes.
Are there more dependecies for this?
Thank you.

similar question already asked with https://github.com/waldbaer/node-red-persistent-values/issues/4


 Please try 3.10.11 and up.

i have python 3.11

Oh sorry I didn't read the error corectly and assumed it was something different. Your anti virus probably deleted the file so please re download eveything with your av turned off

nah still didnt work

Did you re download every file before trying again?

yeah i did

Go into the /resources folder and check if uac_bypass.py is in there.

issue has been solved in development and was caused but poor support for older python versions (namely anything earlier than 3.10.11)


Add a CHANGELOG

Keeping a changelog makes it much easier to get an overview over the changes between two versions. https://keepachangelog.com/en/
I tried to fill in the changes in 0.3.10 from the git log. It's possible that I did not understand everything though.
I'm not sure whether adding an [Unreleased] section would be a good idea, since it introduces merge conflict if two user PRs add changes in parallel. I usually update the changelog of the crates I maintain right before releasing.

Thanks!


silver-dev-cv:1.0.0

I am submitting

[x] a new package
[ ] an update for a package

Description: Fixing the template that shows the package on the typst website. It even pointed to the wrong package :D

Fixed the stray quote. I think this template is better than the default John Doe, it the content itself helps the user set it up more contextually.

Contact links are not working for me using the example template content


[Refactor]: CDAT Migration Phase 3 - Port changes from main to cdat-migration-fy24

Is your feature request related to a problem?
Commits from 03-01-23 to 10-31-24
Todo
In Progress
Done
Rebased

https://github.com/E3SM-Project/e3sm_diags/pull/879

800

https://github.com/E3SM-Project/e3sm_diags/pull/676
https://github.com/E3SM-Project/e3sm_diags/pull/682
https://github.com/E3SM-Project/e3sm_diags/pull/683
https://github.com/E3SM-Project/e3sm_diags/pull/763
https://github.com/E3SM-Project/e3sm_diags/pull/805

Other PRs:

https://github.com/E3SM-Project/e3sm_diags/pull/679

via #794

https://github.com/E3SM-Project/e3sm_diags/pull/836

via #860

https://github.com/E3SM-Project/e3sm_diags/pull/830

via #798

https://github.com/E3SM-Project/e3sm_diags/pull/806

via #842

https://github.com/E3SM-Project/e3sm_diags/pull/840

via #875

https://github.com/E3SM-Project/e3sm_diags/pull/820

via #876

https://github.com/E3SM-Project/e3sm_diags/pull/712

via #876

https://github.com/E3SM-Project/e3sm_diags/issues/877
https://github.com/E3SM-Project/e3sm_diags/pull/851

via #882

https://github.com/E3SM-Project/e3sm_diags/pull/874

via #882

https://github.com/E3SM-Project/e3sm_diags/pull/675

via #883

Misc:

https://github.com/E3SM-Project/e3sm_diags/pull/732

[x] Core driver uses Xarray. Make sure there are no CDAT dependencies.

Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

Hey @chengzhuzhang, I just realized we still need to refactor https://github.com/E3SM-Project/e3sm_diags/pull/675 because it still uses the Dataset class from dataset.py and some CDAT-based utilities, and we want to remove CDAT dependencies for v0.8.0.
I can start refactoring it and then you can add the feature enhancements afterwards. Let me know your thoughts.

Closed after completion of #883


String parameters produce compilation error in Arduino

When using the LCD_screen, the compilation of:
required port Display
	{
		sends initDisplay, refreshDisplay, setDisplay
  // with initDisplay defined as: message initDisplay (id : UInt8, title : String, unit : String, initValue : Integer, minValue : Integer, maxValue : Integer);
	}

produces compilation error in the generated Arduino code:
// parameter title
ptr_union_t __ptrunion_title; //here is the faulty line
__ptrunion_title.pointer = (void*)title;
_fifo_enqueue( __ptrunion_title.buffer[0] );
_fifo_enqueue( __ptrunion_title.buffer[1] );

the error says:
BlinkArduino.cpp: In function 'void enqueue_Meteo_send_Display_initDisplay(Meteo_Instance*, uint8_t, char*, char*, int, int, int)':
BlinkArduino:1608: error: 'ptr_union_t' was not declared in this scope

Note that it works when we add the @sync_send "true" annotation (which is probably better, but still, it should work without that annotation).

Seems like @Lyadis is facing the same (or very similar) problem. What is the strategy here, Dr @ffleurey ?

@sync_send "true" work indeed.

The strategy is to only allow pointers when we do synchronous calls (so with the @sync_send "true"). For async messages it is not allowed and we should probably report it as en error earlier. The point is to never serialize pointers because they typically will not make sense when de-serialized.

Does it mean we should refactor the metamodel to split datatype into primitive type and pointers? So that it would be easier to make a checker (otherwise it is more like a hack to guess whether datatypes are primitive or pointers). Also, should the @sync_send be promoted as a proper concept?

Good questions :-) I think that the sync send probably deserves to be promoted. In terms of the pointers/value issues, it is quite specific to the target platforms so maybe some annotation can be a good start. What we need it to initialize a proposer "checker framework" to allow easily adding individual checks.


Fixed datetime written as dt

Changes proposed
datetime as dt in import, not reflected in code, changed code in body to reflect datetime as dt so program will run.

Thank you for submitting a pull request for this issue . We will review and merge it as soon as possible. If you encounter any other issues, please create a new issue so that the open source community can address it. In the meantime, you can check out other issues
Your contribution is greatly appreciated and we hope to see more from you in the future. Thank you again for your support.


Added Player UI and two blocks sprites

Player UI in hierarchy
PlayerUI.cs contains basic logic
For testing purposes, [Z] and [X] now control the scrolling of the blocks
Added sprites for visual testing

xd


2015-04-27 Bugfix-Release

A whole lot of Bugfixes:

Fix Seeds.rb: Reset PK Sequence after adding data #584
Seeding should be idempotent. Closes #520.
Don't be too optimistic about user supplied URLs #588
Restrict calendar output to HTML #587
Cast event_ids to String to make them compatible PostgreSQL #591

Release the :octopus:


Customizing Responses

How can I customize responses? Change error codes, display custom error messages and show the structure of a returned object.
For now, all of my responses in Swagger UI look like this:

I have the same problem! @theo4u, will be glad to your help!

@theo4u Could we have possibility to customize (override) model parameters as we do it in body?

yeah, need to find a good way to allow users to pass in these params for response here:https://github.com/theo4u/sails-hook-swagger-generator/blob/a5e58a645333d5c8b5e1026acc83de834f1888a6/lib/generators.js#L264

@theo4u Can we expect that you implement it in the near future?

@sudograce yeah very soon, trying to create space for most of the fixes

should be fixed in #58


Correctly handle HTTP errors in RequestLogPolicy

The condition that tests the HTTP status code to decide whether or not to upgrade log severity never sees the 4xx and 5xx responses because they are encapsulated in a StorageError.
Addresses #214

Hey @mohsha-msft the build failure doesn't seem related to my change, as both master and dev branches seem to be crashing in the same way when I run the test locally.
How should I proceed?

@pharaujo
We appreciate your efforts to improve Azure Blob Go SDK!
The build pipeline uses private credentials (storage account name and account key) which we do not expose to public PRs. Please raise the review request anyway. We'll take a look at the PR and will run the tests after that using our credentials.
For more clarification, reach out to us.

@mohsha-msft

(...) Please raise the review request anyway. We'll take a look at the PR and will run the tests after that using our credentials.

This already is the PR with the logging fix. Do you need anything else from my end?

Merging the branch with issue/http-log-policy branch to run regression tests. Will raise a separate PR to merge issue/http-log-policy with dev


[InfluxDB] Add nanosecond duration literal support documentation

URL for relevant page?
https://github.com/influxdata/influxdb/pull/8406
What products and version are you using?
InfluxDB 1.3.0
If we have somewhere where we mention possible duration literals, the new ns literal should be included there. Previously, it was not possible to specify nanoseconds in places like GROUP BY time(...).
It is still possible to use integers for duration math and the integers will be treated as nanoseconds. So these two are the same: 1d - 10 and 1d - 10ns.

Add ns to the Duration units table in the spec and the crosswalk doc:
ns | nanoseconds (1 billionth of a second)


fixed exponent in doc string submesh 1d

Description
Changed the equation string in submesh 1d DOC string to show proper exponent
Fixes #2226
before:

after:

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[ ] No style issues: $ flake8
[ ] All tests pass: $ python run-tests.py --unit
[ ] The documentation builds: $ cd docs and then $ make clean; make html

You can run all three at once, using $ python run-tests.py --quick.
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

Thanks, @TomTranter is this what you meant with the issue you opened?

Thanks, looks good! Very minor typography point, but can you change the exponential to \mathrm{e}?

@TomTranter @rtimms i have made the changes

need approving review from @TomTranter to merge

Just noticed style test is failing. Make sure lines are <=88 characters

@all-contributors add @dikwickley for code


Enhancement: Serialize cookie to string

Add method to Cookie type to allow cookies to be Serialized to a string for use when setting cookies. Useful for doing "response.headers.set()"

Implemented by https://github.com/gnk-softworks/narvik/pull/19


Error installing vaporsynth

When I try to install it in google colab I get this error:
Hit:1 https://cloud.r-project.org/bin/linux/ubuntu focal-cran40/ InRelease
Hit:2 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64  InRelease
Hit:3 http://security.ubuntu.com/ubuntu focal-security InRelease
Get:4 http://ftp.us.debian.org/debian buster InRelease [122 kB]
Hit:5 http://ppa.launchpad.net/c2d4u.team/c2d4u4.0+/ubuntu focal InRelease
Hit:6 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:7 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:8 http://ppa.launchpad.net/cran/libgit2/ubuntu focal InRelease
Hit:9 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Ign:4 http://ftp.us.debian.org/debian buster InRelease
Hit:10 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu focal InRelease
Hit:11 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal InRelease
Hit:12 http://ppa.launchpad.net/ubuntugis/ppa/ubuntu focal InRelease
Hit:13 https://www.deb-multimedia.org/ buster InRelease
Fetched 122 kB in 3s (45.1 kB/s)
Reading package lists... Done
W: GPG error: http://ftp.us.debian.org/debian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY DCC9EFBF77E11517
W: The repository 'http://ftp.us.debian.org/debian buster InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:55
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:55
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:57
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:57
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:59
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:59
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:61
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:61
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:55
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:55
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:57
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:57
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:59
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:59
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:61
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:61
Working... this may take a while.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:55
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:55
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:57
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:57
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:59
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:59
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:61
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:61
Reading package lists... Done
Building dependency tree
Reading state information... Done
deb-multimedia-keyring is already the newest version (2016.8.1).
The following packages were automatically installed and are no longer required:
libcodec2-0.9 libflite1 liblilv-0-0 libmysofa1 libopenal-data libopenal1
libserd-0-0 libsndio7.0 libsord-0-0 libsratom-0-0 libssh-gcrypt-4
libtwolame0 libwavpack1 libx264-155
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 87 not upgraded.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:55
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:55
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:57
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:57
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:59
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:59
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:61
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:61
Prepared apt sources!
Working... this may take a while.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:54
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:56
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:58
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (non-free/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (non-free/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:52 and /etc/apt/sources.list:60
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:55
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:55
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:57
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:57
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:59
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:59
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:61
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:53 and /etc/apt/sources.list:61
E: Unable to correct problems, you have held broken packages.
Package manager quit with exit code.
Installed VapourSynth

I'm not sure I'm afraid. I don't really use Google Colab, but it looks like an error out of my control though.


No alternate version of the article - the article links to itself and tab just provides a link to generic information.

The second paragraph contains the sentence \ link - " ... , see the alternate version of this article."
The link just links to itself; there is no seperarte alternate version of the article; just a tab that links off to more information about running c# azure functions in an isolated process. Does the link need updating or is there currently no alternate version of the article?
[Enter feedback here]

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

ID: 6e88ea08-81ef-2b5a-b9d6-539e85592672
Version Independent ID: f2d8b7b4-906a-d1f5-5201-fc22a7890955
Content: Quickstart: Create your first C# function in Azure using Visual Studio
Content Source: articles/azure-functions/functions-create-your-first-function-visual-studio.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@f1point2  Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Thanks @f1point2 for the feedback. I was trying to be clever with switching between tabs, but I can see how this could be confusing.

This has been removed. Thanks for your feedback. #please-close


ID scraper cache says not allowed

Original issue https://github.com/covidatlas/coronadatascraper/issues/853, transferred here on Monday Apr 20, 2020 at 04:21 GMT

Location, date, and short issue description

ID
Source

https://www.kemkes.go.id/
File

coronadatascraper-cache/2020-4-19/968a2cdd98a1f846c268a7debe59924c.html
Issue details

Says "not allowed" instead of showing table, works in Chrome

(Transferred comment)
Is this still an issue?


Indentation vs brace typo bug

Clearly a bug. Found in CI when compiled by gcc6 (as a warning)!

Wow! Nice warning!


[5.7] Fixes regression introduced in #26353

Closes #26624. Seems json asserts will work same as in v5.7.13

Honestly think you may just want to assert against $response->original in that case? Not json.


[BUG] Rancher never finishes provisioning nodes on vSphere 8

Rancher Server Setup

Rancher version: 2.7
Installation option (Docker install/Helm Chart): Helm chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):  RKE2

Proxy/Cert Details: Rancher-managed certs

Information about the Cluster

Kubernetes version: v1.24.6-rancher1-1
Cluster Type (Local/Downstream): Hosted, vSphere 8. Nodes are cloned from another VM.

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)
Cluster Owner

Describe the bug
Rancher keeps creating VMs on vSphere. As soon as the VMs come up, Rancher deletes them and creates new ones. Provisioning never completes.
To Reproduce
Unknown. There might be something in my vSphere configuration causing this, but with no logs in Rancher, I do not know where to start troubleshooting.
Result
Rancher starts cloning the VMs on vSphere, but as soon as they are up, it deletes them and starts cloning new ones. The process keeps repeating, and nothing ever gets provisioned.
Expected Result

As soon as cloning the VMs finishes, Rancher should start provisioning them and bring up the cluster.
Screenshots

The cluster is configured with 2 node pools:

rke-test-server, 1 node
rke-test-agent, 3 nodes

Rancher starts creating VMs called:

rke-test-server1
rke-test-agent1
rke-test-agent2
rke-test-agent3

As expected. But... as soon as they are up, Rancher deletes them and starts creating new ones

Additional context

There is nothing under Cluster Management/Provisioning logs for the cluster. Only the message "waiting for etcd, controlplane and worker nodes to be registered".
Looking at the rancher pod logs, I see this:
 Tools to come online...
2022/11/23 09:16:54 [INFO] [node-controller] (rke-test-server2) Waiting for VMware Tools to come online...
2022/11/23 09:17:43 [INFO] [node-controller] Waiting for machine to be running, this may take a few minutes...
2022/11/23 09:17:43 [INFO] [node-controller] Waiting for machine to be running, this may take a few minutes...
2022/11/23 09:17:43 [INFO] [node-controller] Waiting for machine to be running, this may take a few minutes...
2022/11/23 09:17:43 [INFO] [node-controller] Waiting for machine to be running, this may take a few minutes...
2022/11/23 09:17:43 [INFO] [node-controller] Detecting operating system of created instance...
2022/11/23 09:17:43 [INFO] [node-controller] Detecting operating system of created instance...
2022/11/23 09:17:43 [INFO] [node-controller] Detecting operating system of created instance...
2022/11/23 09:17:43 [INFO] [node-controller] Detecting operating system of created instance...
2022/11/23 09:17:43 [INFO] [node-controller] Waiting for SSH to be available...
2022/11/23 09:17:43 [INFO] [node-controller] Waiting for SSH to be available...
2022/11/23 09:17:43 [INFO] [node-controller] Waiting for SSH to be available...
2022/11/23 09:17:43 [INFO] [node-controller] Waiting for SSH to be available...
2022/11/23 09:18:00 [ERROR] Unknown error: Operation cannot be fulfilled on preferences.management.cattle.io "cluster": the object has been modified; please apply your changes to the latest version and try again
2022/11/23 09:20:55 [INFO] [node-controller] The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2022/11/23 09:20:55 [INFO] [node-controller]
2022/11/23 09:20:55 [INFO] [node-controller] The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2022/11/23 09:20:55 [INFO] [node-controller]
2022/11/23 09:20:55 [INFO] [node-controller] The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2022/11/23 09:20:55 [INFO] [node-controller]
2022/11/23 09:20:55 [INFO] [node-controller] The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2022/11/23 09:20:55 [INFO] [node-controller]
2022/11/23 09:20:57 [INFO] [node-controller] Generating and uploading node config rke-test-server2
2022/11/23 09:20:57 [ERROR] error syncing 'c-62845/m-rrg6t': handler node-controller: Error creating machine: Error detecting OS: Too many retries waiting for SSH to be available.  Last error: Maximum number of retries (60) exceeded, requeuing
2022/11/23 09:20:57 [INFO] [node-controller] Generating and uploading node config rke-test-agent6
2022/11/23 09:20:57 [ERROR] error syncing 'c-62845/m-7ch9x': handler node-controller: Error creating machine: Error detecting OS: Too many retries waiting for SSH to be available.  Last error: Maximum number of retries (60) exceeded, requeuing
2022/11/23 09:20:57 [INFO] [node-controller] Removing node rke-test-server2
2022/11/23 09:20:57 [INFO] [node-controller] About to remove rke-test-server2
2022/11/23 09:20:57 [INFO] [node-controller] WARNING: This action will delete both local reference and remote instance.
2022/11/23 09:20:57 [INFO] Creating jail for c-62845
2022/11/23 09:20:57 [INFO] [node-controller] Generating and uploading node config rke-test-agent4
2022/11/23 09:20:57 [INFO] [node-controller] Provisioning node rke-test-server1

It appears that Rancher never manages to connect to the newly-created VMs using SSH.
The machines are in the same subnet as Rancher, with nothing filtering traffic between them.
I did look through the docs to see if I need to configure SSH authentication credentials manually, but I came up empty - as far as I can tell, Rancher should be able to create its own credentials via cloud-init.
Is there anything else I need to configure in order for provisioning to succeed?

As I mentioned, everything listed in the issue happens when the source for the Rancher nodes is an existing VM that is cloned.
After discovering issue #38997, I converted the VM to a template, and tried again. This time, I was able to deploy both an RKE and an RKE2 cluster without any issues.
So the problem seems limited to nodes cloned from a VM - possibly related to VM customization?

Hi!
It's off topic, but unfortunately I couldn't find a better topic.
Which version of the vsphere-csi-plugin do you use with vsphere 8? We want to upgrade our vmware cluster from 7 to 8, but we didn't dare because of the 2.5.4 csi plugin version. (This version is in the latest rancher chart).

@Subick - I honestly do not remember. This issue was opened a while ago, and since I never got a reply I gave up on continuing to use Rancher for this purpose :(
I can tell you that this was an out-of-the-box, unmodified Rancher installation. So it was definitely using only the provider(s) installed automatically by the chart.

I'm sorry about that. Thank you for your reply.


Typo in reconnect message

https://github.com/jellyfin/jellyfin-apiclient-javascript/blob/a0143bcd7dc8389c51bcb5cabebcbd1d13e31d49/src/apiClient.js#L298
This should say Reconnect succeeded or Reconnect success

@Technetium1 Can you make a PR please?

@ferferga It has been done! https://github.com/jellyfin/jellyfin-apiclient-javascript/pull/357

Fixed in #357, which is now in master.


Star Wars Revised RPG: New Feature

Added skill point tabulation base on rankings

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[ ] I have authorization from the game's publisher to make this an official sheet on Roll20 with their name attached.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description
The main request, by "The Nameless", was to tabulate skill points used via rankings in order to compare total skill points with skill points used.
The sheet has been updated:

allow a granularity of 0.5 points and issues warning ('invalid value' - on hover) when negative values input for ranks
made changes to repeating sections ‘checkbox’ to cause a re-tabulation
re-coded how categories (regular, dark force, light force, profession, craft, knowledge & entertain) retotaling cause a recalculation of used point total
replaced defunct URL for logo with a user supplied black and white JediVsSith image

In accordance with what I have read, I will be updating the code (bug fix?) later to reflect the new URL for the logo, assuming this update is approved, and the image find a home on the Roll20 GitHub.
Tested under:
Chrome:  Version 128.0.6613.113
Firefox: Version 130.0

Character Sheet Info Roll20 Internal Use only.


Stop invalid view error when graphId does not exist in the FederatedStore

Normally when running a query against a federated store, in the event that a user specifies a non-existent graph, an error message should be returned informing the user that they inputted the wrong graph id.
However if the user specifies a view in their query, they receive an error telling them their view was invalid. This is confusing and obscures the true source of the error.

Merged into develop in #2089