Question file does not update if dropdown changed

What kind of request is this (question/bug/enhancement/feature request):
BUG
Steps to reproduce (least amount of steps as possible):

load an catalog app with a dropdown
change dropdown values

Result:
It should change fields, but it doesn't
Other details that may be helpful:
questions.yml

questions:
  # Database settings
  - variable: env.open.DATABASE
    description: "Select prefered Database"
    label: "Database"
    required: true
    type: enum
    group: "Database"
    options:
      - "InfluxDB"
      - "POSTGRES"
  - variable: usersDb.env.INFLUX_USER
    label: "InfluxDB Admin Username"
    show_if: "env.open.DATABASE=InfluxDB"
    default: "admin"
    description: "Username for InfluxDB"
    type: string
  - variable: usersDb.env.INFLUX_PASSWORD
    label: "InfluxDB Admin password"
    show_if: "env.open.DATABASE=InfluxDB"
    default: "admin"
    description: "Password for InfluxDB"
    type: string
  - variable: usersDb.env.POSTGRES_USER
    label: "POSTGRES Admin Username"
    show_if: "env.open.DATABASE=POSTGRES"
    default: "admin"
    description: "Username for POSTGRES"
    type: string
  - variable: usersDb.env.POSTGRES_PASSWORD
    label: "POSTGRES Admin password"
    show_if: "env.open.DATABASE=POSTGRES"
    default: "admin"
    description: "Password for POSTGRES"
    type: string

Environment information

Rancher version (rancher/rancher 2.1.7)
Installation option (single install/HA): single installation

Cluster information

Cluster type (Custom):
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.5", GitCommit:"32ac1c9073b132b8ba18aa830f46b77dcceb0723", GitTreeState:"clean", BuildDate:"2018-06-21T11:46:00Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:30:26Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

> docker version
Client:
 Version:      1.10.3
 API version:  1.24
 Go version:   go1.5.3
 Git commit:   20f81dd
 Built:        Thu Mar 10 21:49:11 2016
 OS/Arch:      linux/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

I have not been able to reproduce this issue in the latest or 2.1.7 versions of rancher.
As you can see in this recording 2.1.7 seems to be updating the subquestions without issue.

@exocode if you still see this issue, please re-open and let me know.


Comprehension / generator, opt-in feature to preserve line breaks

Before I begin, here is some context:
I would love to incorporate ruff as a pre-commit formatter for one of our projects. We developed the habit of almost always separating comprehension target-expression, for-in statement(s), and optional if-expression(s) into separate lines, except for very short and trivial comprehensions. Naturally, this makes identifying these separate comprehension parts very easy at a glance, at the cost of a few more lines. Also, we have increased our line length somewhat.
In its current form, ruff will always collapse comprehensions to a single line if:

it is short enough to fit within the line length
there are no "magic trailing commas" in any of the comprehension parts

We do use trailing commas ourselves, so many of our hand-formatted comprehensions that contain trailing commas in any form remain more or less unchanged after running ruff format. The ones that do not, usually get collapsed to a single line mess (also due to our increased line length).
One toy-example for this would be:
[
    i + n
    for i in range(5)
    for n in range(5)
    if i < 3
]

which would be collapsed to a single line:
[i + n for i in range(5) for n in range(5) if i < 3]

which is not as easy to recognize at a glance as the original example.
Would it be possible to have an opt-in feature to always preserve line breaks in comprehensions and generators? The behavior would be the same as if there were a trailing comma anywhere in the comprehension, and each comprehension-part is given a separate line, maybe even expand the whole comprehension into separate lines if there is at least one line break in it.

Thanks for the detailed write up. I can understand that nested comprehensions can get hard to read.

Would it be possible to have an opt-in feature to always preserve line breaks in comprehensions and generators?

Respecting line breaks would set a new precedence for ruff/black. There are other formatters that rely on line breaks. For example, prettier doesn't collapse an object expression if it has a line break after the last property's value:
let a = {
	a: 1,
  	b: 2
}

Whereas the following will be collapsed because it doesn't have a line break after b

let a = {
	a: 1,
  	b: 2 }

I could see a similar rule where the comprehension wouldn't collapse if there's a line break before the closing ], but I'm very hesitant of adding it because:

It makes formatting changes non-reversible. A comprehension never collapses after the formatter expanded it once
It's non obvious why the formatter doesn't collapse some comprehensions but does collapse others
It will lead to less consistent code because users can now overrule the formatter.

Black's/Ruff's magic trailing comma suffers the same problem.
I'm more open if we could identify a formatting rule that makes comprehensions more readable in general without requiring manual intervention. Are there specific patterns in the body that should never collapse? E.g. if there's any nesting?

Thank you for your feedback. Your arguments sparked a discussion within our team, what the actual requirements of such a feature would be, and that the initial idea of relying on line breaks is not sufficient or feasible.
Initially, we though that the decision, whether to collapse or expand a given comprehension is mostly subjective. After checking a number of actual examples from our code base, we noticed a pattern that may describe what we are looking for. We usually collapse comprehensions that do not stray too far from the "visual span", as in, you can see and perceive the whole comprehension without having to scan your eyes along horizontally too much, if that makes sense to you.
Another toy example that may show what I mean. Here are two comprehensions that would produce the same AST:
[x for x in range(3) if x == 0]

[descriptive_name for descriptive_name in range(3) if descriptive_name == 0]

We would prefer the top one collapsed, since it is short enough. The bottom one we would expand, as it is more effort to scan/read along the line to know what is going on, even though it has the same complexity as the top one.
Using this knowledge, our suggestion would be to introduce a maximum comprehension (or generator) expression length (opt-in of course, to preserve Black compatibility). Unlike the line length parameter, it only describes the length of a collapsed comprehension expression itself, regardless of indentation or nesting. I do not know any implementation details, but I imagine it working like so:

If a comprehension can be collapsed using existing rules, the collapsed single-line form is measured against the max comprehension expression length
If we are below the expression length, the collapsed form can be kept
Otherwise, it has to be expanded

Regarding nesting, I imagine this also working for deeply nested and highly indented cases. If a nested comprehension expression is short enough, it may be collapsed within a larger, expanded one. The overall line-length still wins over this, if indentation or nesting is too high.
Does this make sense at all? Also is this technically feasible to implement, or are we dreaming too much here?

+1, this would be a really good addition.
I would be happy with @Martin19037's suggestion for the comprehension* specific line length.
If we need more of a sledgehammer solution for some reason, even a bool setting that expands all comprehensions and generators into the multiline format would work. I find it very rare that one would be trivial enough not to expand. It is so much easier to understand what's happening in the expanded format, even the lines end up short. I see them as the exception rather than the rule.
I was considering adding ruff to one of my projects, but seeing that it would collapse all comprehensions turned me away.

Have separate line length would probably be the best. Alternatively, never unwrapping wrapped lines could also work.

Ha, I was about to suggest something similar to the lines of "Provide an option to not collapse comprehensions into one line"
Not sure how AST looks like, but in my mind, comprehensions have 3 "parts":

Expression -- the thing that will be added into list / returned by generator
Iteration -- the for part, contains at least 1 rule
Optional Guard -- the if part, if exist, contains at least one rule

So in addition to the overall line length (after collapsing), it could also have additional rules:

If there are more than N1 Iterations, do not collapse
If there are more than N2 Guards, do not collapse
If there are a total of more than N3 'parts' (expression + iterations + guards), do not collapse

I'd still love to have a per-project knob to just "do not collapse any comprehension", though.


ADDING Vigenere Cipher

I am creating a pull request for...

[ ] New algorithm

@abranhe, please check out my review and if you agree with me, add the Plagiarism label and close this PR.
Thanks!

Hello, @rkraja2751. Thanks for your interest in contributing to this repository. I am sorry to tell you that the code that you've written is strikingly similar to the code in this website:
https://www.geeksforgeeks.org/vigenere-cipher/
which is authored by someone else. We do not encourage plagiarism.
Here are a few things that you need to consider before contributing to any repository:
1. Always read the contribution guidelines of the specific repository that you are contributing to.

2. You can always refer to any online resources for the feature/fix that you are working on to contribute, but never copy-paste code which will result in categorizing your PR under Plagiarism.

3. Always write clean and well-structured code. It's a best practice that you can do while contributing to Open Source.

Looking forward to your next PR!
Thanks!

@hemanth-kotagiri
Really Sorry, for that. I will take care of it from next time.

Hey @rkraja2751! Don't be sorry! It's just a mistake that you've done and you're supposed to learn from it! Next time, please consider the points I mentioned before raising PRs in any repository, it will help you!
Thanks, again!


Breadcrumb is not displayed

It looks as if there were no breadcrumb displayed on the page.  The navigation only shows the "homepage" and the current page, but not the intermediate ones.  E.g. it looks like this with the readthedokus template:

but like this when using the standard dokuwiki template:

This is intended because the original "Read the Docs" looks that way. However, it sounds reasonable to add an option whether to show the original breadcrumb. I'll work on it.

Yes, from that perspective it makes sense. I'm still thinking more in DW terms than in Readthedocs terms :-)

I add the "Use Dokuwiki breadcrumbs" option. Enable it to show default DokuWiki breadcrumbs.

Works like a charm.  Thanks a lot


Prl 603 screen refinement part1

Before creating a pull request make sure that:

[X] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
PRL-603 Screen refinement Part 1
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Closing this PR and will open a new one


Adding Solution to Longest Increasing Subsequence II in Cpp

This pr solves issue  https://github.com/ritikbanger/Hacktoberfest2022-DSA/issues/287
c++ program for Longest Increasing Subsequence II
Please add the hacktoberfest & hacktoberfest-accepted tags if approved. Thanks!

@ritikbanger Can you please merge this under hacktober if this is okay.


Simplify the public surface area for Response for usability

Context and Problem:

When customers of the SDK call client library APIs which talk to Azure services that return cloud-hosted resources, their properties, or result of "crud-like" REST operations, they primarily care about two things (in the success path):

Did the API call succeed and complete the operation as expected?
How can I get the returned result to take further meaningful action on the value returned?

The Azure services that the SDK talks to on behalf of the customer would continue to evolve and add new features, response headers, or append to the returned body. The SDK needs a version resilient mechanism so that existing applications written against the SDK that do not use the new features would continue to work without needing to react to breaking changes within the SDK. This lead to a Response<T> templated type returned by almost all client library APIs which wraps the value the user cares about (created by deserializing meaningful operation-specific information from the response into a model) and the HTTP response returned by the service which exposes all the headers, status code, and body. Most customers wouldn't care about this raw response but it provides an escape hatch to the customer for version resiliency. This notion is a natural part of REST APIs and the HTTP protocol domain. Therefore, the concept of Response<T> exists in all the Azure SDK languages: https://azure.github.io/azure-sdk/general_design.html#response-formats
During the SDK usability studies, we observed some customers with limited cloud and REST experience, getting overwhelmed and confused by what they could do with the returned Response<T> type. This highlighted a need to simplify the type and to provide more conceptual and sample docs which explain what the user is expected to do. This is a classical example of "less is more". A common feeling expressed by participants: I just want to get the blob properties, and the Response<T> complexities get in the way.

One participant stumbled to find the -> operator on Response<T>
VS IntelliSense doesn't show the returned model type, just Response<...>
Another question that came up: If ExtractValue and RawResponse have identical functionality, why not just use Http Response? Does ExtractValue has simpler functionality?
Verbatim: Usually we apply -> on pointers. Validating feedback like this from @BillyONeal: https://github.com/Azure/azure-sdk-for-cpp/pull/316#discussion_r455443256

Motivation and Goal:

Reduce concept count along with questions that would come up when customers approach any of the service client APIs, all of which return Response<T>.
Be idiomatic to the language and leverage concepts that C++ developers are already familiar with, following the principle of least surprise.
Avoid multiple ways of doing the same or very similar things while continuing to enable all existing use cases.

Design Change:

Make the Value and RawResponse fields public that the caller can access directly.
Do not make Value nullable, since it should always exist. This allows us to defer introducing the Nullable<T> concept (enabling progressive disclosure) and can remove noisy methods like HasValue().
Remove the notion of "Get" and "Extract" by leveraging a unique_ptr field directly. This minimizes another subtle concept and decision point for the user. Any user wanting to get ownership of either part of Response<T> can do so using std::move, and that avoids forcing the concept on everyone. For example, we remove questions like the following that the customer might ask: Which API should I call and what's the difference?
Remove the pointer-like convenience APIs (such as -> and *) by deferring their addition to the future, because they don't follow the principle of least surprise. Even though they enable users to write abbreviated code, the nuances of when to use one versus the other are complex, hurt auditability (such as "Find all references"), and conflates the pointer/reference operator semantics to a domain that doesn't necessarily need it. If we see strong evidence that customers understand and benefit from these, we can always add them back in the future, but removing it would be a breaking change.

API Design:
template <class T> class Response {
public:
  T Value;
  std::unique_ptr<Azure::Core::Http::RawResponse> RawResponse;

  // If it was possible in C++, this would be internal only, but having this as a convenience ctor
  // to enable correctness is valuable.
  explicit Response(T value, std::unique_ptr<Azure::Core::Http::RawResponse> rawResponse)
      : Value(std::move(value)), RawResponse(std::move(rawResponse))
  {
  }
};

In the future, depending on the need to return "value-less" response types, which are more user-friendly when we are confident there is little chance for the service to return anything meaningful, we'd add void specialization since C++ allows it, following precedence in other languages like Java:
template <> class Response<void> {
public:
  std::unique_ptr<Azure::Core::Http::RawResponse> RawResponse;

  explicit Response(std::unique_ptr<Azure::Core::Http::RawResponse> rawResponse)
      : RawResponse(std::move(rawResponse))
  {
  }
};

Questions:
Why is status code not exposed directly on Response<T> to make it more visible?

Most customers shouldn't need to concern themselves with the status code in the success path as long as the client libraries handle all the error cases correctly. Quoting Ted: Getting a 200 vs. a 201 vs. a 202. vs a 204 shouldn't really matter most of the time, but you've got the raw response if for some reason it really does. Response<T> is composed of two main parts: data related to your model representing the resource of operation result from the service (represented by the T) and the stuff related to the HTTP response. Duplicating parts of the response (such as the status code) muddies that a bit and would result in  the user having multiple ways to get to the status code.
In the error handling and recovery code paths (such as in try/catch exception blocks), it remains critical for the user to access the HTTP status code easily. This can be addressed by increasing the visibility of that on our exception types like RequestFailedException: https://github.com/Azure/azure-sdk-for-cpp/issues/1973

What if there is no Value within the Response<T>?

For almost all cases where we return a  Response<T> from our client libraries during the success path, the request returns both a Value and a response. In cases where the service doesn't return a model type today (when there are no meaningful response headers or body), we either return an empty placeholder struct as the T to be resilient to additions in the future OR we return a specialized Response<void> which wouldn't contain the T Value field. Therefore, when returning a Response<T>, the T must always exist.
Like many of the other returned objects, it is not required to set the Value or RawResponse fields to something defined or meaningful when an exception or error occurs. The user shouldn't be accessing the fields of the Response<T> object in such cases anyway.

Without a method, how can we validate if the user moved the raw response already, if they try again?

We rely on the C++ developer calling the Response<T> APIs to understand C++ primitives and common coding patterns around the lifetime semantics of smart pointers like std::unique_ptr. Like any library API returning a unique_ptr, if the user accesses the RawResponse without moving it or taking ownership, repeated field access will continue to work. It is the caller's responsibility to track ownership if they use std::move to extract the RawResponse from the Response<T> and know not to make multiple field access calls after that.

cc @CaseyCarter, @JeffreyRichter, @RickWinter, @vhvb1989, @kyle-patterson, @Jinming-Hu, @vinjiang

Fixed in https://github.com/Azure/azure-sdk-for-cpp/pull/1974

Good write-up and I approve of this proposal

Question:

By using the template specialization Response<void>, if the server makes a change in the future to return something, wouldn't be easier for the sdk client to have the empty placeholder model to just add fields into it? (instead of changing from Response to Response)

if the server makes a change in the future to return something

This is about trade-offs and a balance between future uncertainty and usability of customers today. If we foresee that future happening for some particular API, it makes sense to use an empty placeholder model.
However, if the likelihood of that is low and we create a bunch of empty models that remain empty, we hurt the overall usability of the SDK due to "death-by-thousand-cuts". How often would the customer try to grab the T value from the Response<T> to find nothing in it, that they learn the wrong pattern or feel the usability pain?
Life doesn't give guarantees :)
Keep in mind, even when the server makes the change in the future, the customer isn't automatically blocked. Us returning the RawResponse acts as the escape hatch for exactly that purpose. The addition must be deemed important enough, in mainline user scenarios, for us to address it. This issue exists today already, especially when the server adds things to the body/header that don't get deserialized into the model being returned.

wouldn't be easier for the sdk client to have the empty placeholder model to just add fields into it? (instead of changing from Response<void> to Response<T>)

We wouldn't do that as it would be considered a breaking change. If, 9/10 times we made the right call, it is reasonable for us to introduce a new method that returns the Response<T> and leave the void-returning one as is. This calculus would be done on a per-API basis following recommendations of the service owners, and expectations from a user, rather than painting everything with a broad brush. Other language SDKs have already made such calls in some places (which include both correct calls in favor of usability, and missteps that weren't yet deemed important enough to add new methods).


Add ISC license file

Might need to change the copyright owner in the license file. I took the latest commit author, but based on the package.json file, the author is Juha Lindstedt.

Thank you! 👌


Metadata -> SOAP List Metadata INVALID_SESSION_ID

I have configured Postman and am able to execute most of the calls. But for Metadata -> SOAM List Metadata I am getting the below error. Does anything specific need to be done for SOAP calls?
sf:INVALID_SESSION_ID
INVALID_SESSION_ID: Invalid Session ID found in SessionHeader: Illegal Session

Hi @ram4ufriends these are SOAP requests (as indicated in their name). This means that you need a SOAP session to use them. The default authentication for the collection is OAuth 2.0 and that's not compatible with SOAP.
If you want to call SOAP APIs, you need to authenticate with Auth > SOAP Login. This requires that you set these collection variables beforehand: username, password and secretToken.


AQI doesn't fail over when a sensor downs a laser counter

The Purple Air devices have two sensors for redundancy, and automatically "down" a sensor when they detect a problem.
https://www.purpleair.com/json?show=38607 is a device that's currently in this state - sensor A is "degraded" so the map reports the data from sensor B. Unfortunately it looks like aqi.py only pulls the values from sensor A, so if those stop working correctly then it will report the wrong information.
It doesn't look like there's a value in the json response that flags a sensor as degraded - the web UI seems to make this determination by comparing the values of sensors A and B (and it must also be doing some kind of lookback to decide which one to trust?)
It does look like a bunch of the sensor values seem to get "zeroed out", so spot checking those might also help weight the response.
For the sake of the bug report, here's a dump of the current json response for 38607:
//<PHONE_NUMBER>3542
// https://www.purpleair.com/json?show=38607
{
"mapVersion": "0.22",
"baseVersion": "7",
"mapVersionString": "",
"results": [
{
"ID": 38607,
"Label": "Hopi (Street)",
"DEVICE_LOCATIONTYPE": "outside",
"THINGSPEAK_PRIMARY_ID": "855224",
"THINGSPEAK_PRIMARY_ID_READ_KEY": "1UVUAPZARKPZ9UUM",
"THINGSPEAK_SECONDARY_ID": "855226",
"THINGSPEAK_SECONDARY_ID_READ_KEY": "P63TM3YUI180KBIP",
"Lat": 37.390649,
"Lon": -122.079714,
"PM2_5Value": "3333.12",
"LastSeen":<PHONE_NUMBER>,
"Type": "PMS5003+PMS5003+BME280",
"Hidden": "false",
"Flag": 1,
"DEVICE_BRIGHTNESS": "15",
"DEVICE_HARDWAREDISCOVERED": "2.0+BME280+PMSX003-B+PMSX003-A",
"Version": "6.01",
"LastUpdateCheck":<PHONE_NUMBER>,
"Created":<PHONE_NUMBER>,
"Uptime": "2510773",
"RSSI": "-46",
"Adc": "0.02",
"p_0_3_um": "0.0",
"p_0_5_um": "0.0",
"p_1_0_um": "0.0",
"p_2_5_um": "0.0",
"p_5_0_um": "0.0",
"p_10_0_um": "0.0",
"pm1_0_cf_1": "5000.24",
"pm2_5_cf_1": "5000.24",
"pm10_0_cf_1": "5000.24",
"pm1_0_atm": "3333.12",
"pm2_5_atm": "3333.12",
"pm10_0_atm": "3333.12",
"isOwner": 0,
"humidity": "41",
"temp_f": "78",
"pressure": "1012.61",
"AGE": 1,
"Stats": "{"v":1365.48,"v1":321.89,"v2":143.72,"v3":94.66,"v4":48.01,"v5":35.84,"v6":31.53,"pm":1365.48,"lastModified":1602126725789,"timeSinceModified":120012}"
},
{
"ID": 38608,
"ParentID": 38607,
"Label": "Hopi (Street) B",
"THINGSPEAK_PRIMARY_ID": "855228",
"THINGSPEAK_PRIMARY_ID_READ_KEY": "P5R421CYT6X3JN8L",
"THINGSPEAK_SECONDARY_ID": "855230",
"THINGSPEAK_SECONDARY_ID_READ_KEY": "9K0NZFANA8SU3CW6",
"Lat": 37.390649,
"Lon": -122.079714,
"PM2_5Value": "32.67",
"LastSeen":<PHONE_NUMBER>,
"Hidden": "false",
"Created":<PHONE_NUMBER>,
"p_0_3_um": "3252.21",
"p_0_5_um": "961.4",
"p_1_0_um": "258.47",
"p_2_5_um": "29.02",
"p_5_0_um": "2.4",
"p_10_0_um": "0.5",
"pm1_0_cf_1": "17.64",
"pm2_5_cf_1": "34.79",
"pm10_0_cf_1": "36.31",
"pm1_0_atm": "17.64",
"pm2_5_atm": "32.67",
"pm10_0_atm": "36.31",
"isOwner": 0,
"AGE": 1,
"Stats": "{"v":32.67,"v1":31.63,"v2":33.05,"v3":34.83,"v4":39.41,"v5":36.36,"v6":32.8,"pm":32.67,"lastModified":1602189246334,"timeSinceModified":120368}"
}
]
}

It's not actually true that it only uses A. As you can see in your result above, this is a 2 element array. The app calculates as:
    self.pm2_5_atm = (float(data_a['pm2_5_atm']) + float(data_b['pm2_5_atm']))/2

So it has:

"pm2_5_atm": "3333.12",
"pm2_5_atm": "32.67",
Obviously, the first is going to swamp the second.

"Compare and contrast"
Looking at mine, the only difference is that yours has "Flag": 1, in the first array entry. I'm guessing that means "I'm bad, I'm bad, you know it" (Sorry, Michael Jackson!)
I've asked in the FB group if my suspicion is correct, and I've got some code ready if it is true.
For a workaround, you could just change the lines in WebAQI.py to only look at B for now.

I stand corrected! Thanks!
On Thu, Oct 8, 2020 at 9:09 PM Doug Claar<EMAIL_ADDRESS>wrote:

It's not actually true that it only uses A. As you can see in your result
above, this is a 2 element array. The app calculates as:
self.pm2_5_atm = (float(data_a['pm2_5_atm']) + float(data_b['pm2_5_atm']))/2

So it has:

"pm2_5_atm": "3333.12",
"pm2_5_atm": "32.67",
Obviously, the first is going to swamp the second.

"Compare and contrast"
Looking at mine, the only difference is that yours has "Flag": 1, in the
first array entry. I'm guessing that means "I'm bad, I'm bad, you know it"
(Sorry, Michael Jackson!)
I've asked in the FB group if my suspicion is correct, and I've got some
code ready if it is true.
For a workaround, you could just change the lines in WebAQI.py to only
look at B for now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dclaar/purple_air/issues/10#issuecomment-705956457,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4JWNNVMU6HKT6FMFUDADDSJ2EIPANCNFSM4SJH4J6A
.

If someone can tell me what the local interface does when a sensor is bad, I can implement that, but right now I only know about the web interface, so I've fixed that one.

Thanks!
On Sat, Oct 10, 2020 at 10:59 AM Doug Claar<EMAIL_ADDRESS>wrote:

If someone can tell me what the local interface does when a sensor is bad,
I can implement that, but right now I only know about the web interface, so
I've fixed that one.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dclaar/purple_air/issues/10#issuecomment-706588160,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4JWNJ2WDUJJVEDBOVPD2LSKCOIZANCNFSM4SJH4J6A
.

Fixed for web. Closed due to lack of information for local interface.


Test68

@tiagocomba please test in your own repo.

sex

@tiagocomba please test in your own repo.


Better Firefox Support

not all of the tests currently pass on firefox.

now that there is decent baseline support on FF, i will break up this issue into separate tickets.


BGP config Import/Export policies as list

https://github.com/napalm-automation/napalm-base/pull/14

Closing as discussed in napalm-automation/napalm-base#14


Trying to set up mysql storage and getting this error bungee.

Like the title says I'm getting errors when starting my bungee server up with Mysql storage settings
12.04 05:02:40 [Server] INFO Attempting to apply relocations to mysql_driver-5.1.47.jar...
12.04 05:02:40 [Server] INFO Attempting to apply relocations to hikari-3.3.1.jar...
12.04 05:02:40 [Server] INFO Loading storage provider... [MYSQL]
12.04 05:02:40 [Server] SEVERE INFO me.lucko.luckperms.lib.hikari.HikariDataSource - luckperms-hikari - Starting...
12.04 05:02:40 [Server] SEVERE INFO me.lucko.luckperms.lib.hikari.HikariDataSource - luckperms-hikari - Start completed.
12.04 05:02:42 [Server] SEVERE Failed to init storage dao
12.04 05:02:42 [Server] SEVERE java.sql.BatchUpdateException: Unknown character set: 'utf8mb4'
12.04 05:02:42 [Server] SEVERE at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
12.04 05:02:42 [Server] SEVERE at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
12.04 05:02:42 [Server] SEVERE at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
12.04 05:02:42 [Server] SEVERE at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
12.04 05:02:42 [Server] SEVERE at me.lucko.luckperms.lib.mysql.jdbc.Util.handleNewInstance(Util.java:425)
12.04 05:02:42 [Server] SEVERE at me.lucko.luckperms.lib.mysql.jdbc.Util.getInstance(Util.java:408)
12.04 05:02:42 [Server] SEVERE at me.lucko.luckperms.lib.mysql.jdbc.SQLError.createBatchUpdateException(SQLError.java:1163)
12.04 05:02:42 [Server] SEVERE at me.lucko.luckperms.lib.mysql.jdbc.StatementImpl.executeBatchInternal(StatementImpl.java:1060)
12.04 05:02:42 [Server] SEVERE at me.lucko.luckperms.lib.mysql.jdbc.StatementImpl.executeBatch(StatementImpl.java:970)
12.04 05:02:42 [Server] SEVERE at me.lucko.luckperms.lib.hikari.pool.ProxyStatement.executeBatch(ProxyStatement.java:128)
12.04 05:02:42 [Server] SEVERE at me.lucko.luckperms.lib.hikari.pool.HikariProxyStatement.executeBatch(HikariProxyStatement.java)
12.04 05:02:42 [Server] INFO Loading messaging service... [SQL]
12.04 05:02:42 [Server] SEVERE at me.lucko.luckperms.common.storage.implementation.sql.SqlStorage.init(SqlStorage.java:196)

This issue really exists because your MySQL server is a really outdated version - I suggest you upgrade to a newer version...
However, I've pushed a workaround fix for this in the above commit.


MINIFI-337: Update configuration readme for Repositories

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with MINIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[x] If applicable, have you updated the LICENSE file?
[x] If applicable, have you updated the NOTICE file?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

reviewing

@phrocker doc changes look good overall.  we need to address the flow vs flowfile vars and property names in the codebase

@apiri This PR follows #110

rebasing/reviewing now that #110 was merged

After rebasing, things look good.  Had some minor merge conflicts which were pretty straightforward to adjust.  Will get this merged.  Thanks!


Only present valid specialist sectors to Publishing API

It is possible for the relationship between a specialist sector and an edition to remain persisted despite the specialist sector being invalid. This extra check ensures we only present valid sepcialist sectors to the Publishing API.
This change was identified when publishing a document collection that had a specialist sector that was missing a content_id. The specialist sector in question appears to have been withdrawn as it is not visible on GOV.UK.
The Publishing API rejected the JSON as the links hash contained the nil``content_id of the specialist sector.

Closing this as after further investigation I think we need to address to root of the problem. That being that Editions are associated to Specialist Sectors that have no known content id.


[Bug]: local timezone added to EDF session start time

What happened?
This is not a bug per-se, more unexpected functionality.
When using the EDF converter, pynwb will set the timezone on the session start time to the computer's local time.
Given that the EDF file format itself doesn't contain timezone information, this added information makes running the EDF converter somewhat inconsistent i.e. running the converter locally vs in a deployed environment can produce different start times in the output NWB file.
For clarity, the reasoning behind why pynwb sets the session start time timezone to the computer's local time is discussed in this issue: https://github.com/NeurodataWithoutBorders/nwb-schema/issues/50 and implemented here: https://github.com/NeurodataWithoutBorders/pynwb/pull/641
Proposal
Given that EDF itself doesn't specify a timezone for its start date/time
Given that the user performing the conversion to NWB might be in a different timezone than where the EDF file was produced
When reading the raw metadata from EDF file set the startdate timezone to UTC, before NWB file creation. Here: https://github.com/catalystneuro/neuroconv/blob/main/src/neuroconv/datainterfaces/ecephys/edf/edfdatainterface.py#L49
This would be a best effort to make the session start time in the NWB file as timezone-less (and thus as close to the original EDF file) as possible.
Steps to Reproduce
interface = EDFRecordingInterface(file_path=edf_file_path)
metadata = interface.get_metadata()
interface.run_conversion(nwbfile_path=nwb_file_path, metadata = metadata)

Traceback
/opt/venv/lib/python3.12/site-packages/pynwb/file.py:472: UserWarning: Date is missing timezone information. Updating to local timezone.
  args_to_set['session_start_time'] = _add_missing_timezone(session_start_time)

Operating System
macOS
Python Executable
Python
Python Version
3.12
Package Versions
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] Have you ensured this bug was not already reported?

Thanks for the detailed thoughts on this matter
These types of issues and choices are exactly why we emphasize the explicit setting of timezone throughout our conversion gallery: https://neuroconv.readthedocs.io/en/main/conversion_examples_gallery/recording/edf.html
That is the best we can do on NeuroConv and the NWB GUIDE (which has a graphical selector of available timezones), as this is more of a NWB schema issue - could you add your thoughts over there?
Setting UTC automatically is just as arbitrary (and still false) of a decision as setting the local computer timezone. Neither is ideal, and the requirement of a timezone in the session_start_time is a long and hotly debated issue in the NWB schema. There were recent efforts to make it not required at all (and thus not set to potentially incorrect values) on the NWB side, but they broke DANDI publication requirements (leading up to https://github.com/pydantic/pydantic/issues/9518) so it was all reverted in the end

@CodyCBakerPhD thanks for taking a look and your insight!
The recommendation to have the end user set the timezone explicitly makes total sense, and is definitely the approach I'll take on my end.
Also happy to add my thoughts over on the NWB schema if they're not too redundant to what's already been discussed.
And that's interesting to know that there was effort to remove the need for timezone altogether!
I had initially thought the EDF conversion a good spot to make the proposed change because EDF itself under specifies its start time, such that the information might be lost (in communication) between recording and the actual usage of the data
and while

Setting UTC automatically is just as arbitrary (and still false) of a decision as setting the local computer timezone. Neither is ideal

is totally true, UTC+0 would at least indicate no offset should be applied to the given time, and would maintain consistency across runtime environments e.g. local development vs. a production pipeline.
Again, totally happy to add those last thoughts over on the NWB schema page if they positively contribute to the conversation.
Just wanted to leave my thoughts here for posterity in case anyone comes across a similar issue.
Feel free to close out the issue if you think it best to leave the EDF converter as is!
Thanks again!

I should also add for context, the reason I originally ran into this issue and proposed the given change was that I had utilized the neuroconv Docker runtime, instead of using the Python library, and there was no way (as far as I could tell) to intercept the read metadata and apply that explicitly timezone setting that the documentation recommends. Perhaps that's a separate issue worth looking into?

Also happy to add my thoughts over on the NWB schema if they're not too redundant to what's already been discussed.

The thoughts have been shared before, yes, but it's more about 'casting your vote' or 'poking the sleeping dragon'
If enough people rally to push the system in a given direction, it makes it a higher priority, more momentum, higher chance of success, etc...
So yes, please share your thoughts with the rest of the community at the highest level


Can I use this for TX2i?

Hi JetsonHacks,
I am trying to get wifi working on the TX2i and I am struggling with it. Do you know if these scripts work in the TX2i?
Thanks

I do not know. I have not tried it on the TX2i.


Development

@yalvar I assume this was opened by mistake so I'm going to close it out for now.

Yes it was, apologize for the inconvenience.


HTML forevaa

@JD235  try this year for Hacktoberfest and have a look at the updated repo and contribute.Make sure to follow me and star the repo
HAPPY HACKING


Dependencies update #1

Coverage remained the same at 98.082% when pulling 3e93c35c69804c0db5c6ff23617426dd53137692 on dependencies-update-01.01.2020 into 248f6348e3193d5bda6b056eab91344faf1d5cb0 on master.


[Request] Qr from image c++

Can someone give me sample on how can i read/decode QR from image file using c++ ,
already built libZXing.so but i dunno how to use it, i read the example but can't find answer from there
any simple c++ code ?
Thanks

Yes, the ZXingReader.cpp is indeed not very easy to follow as it evolved into a fully fledged command line tool. I hope the following is helpful to you:
	using namespace ZXing;

	int width, height;
	uint8_t* data = // read your image data from a file or get it from somewhere else.
	                // The following code assumes 3 bytes (RGB) per pixel.

	auto hints = DecodeHints().setFormats(BarcodeFormat::QRCode);
	auto image = ImageView{data, width, height, ImageFormat::RGB};

	auto results = ReadBarcodes(image, hints);

	for (auto& result : results) {
		std::cout << result.text() << "\n";
	}

okay already solved but i have a next problem , i want Text to become QR i read the sample ZXingWriter , but i dont know how to convert the bitmatrix to QImage , btw im using zxing using QT

You are using Qt? If you only said that earlier... ;). Please have a look at ZXingQtReader.cpp and the brand new ZXingQtWriter.cpp.

Already resolved , :)   thanks


Show message when revealing upgrades tree without a selected piece

Requested Changes

[ ] Show message "Select a piece to views upgrades" when revealing the upgrades tree and no piece is selected.
[ ] Dismiss upgrades tree available upgrades when clicking on the screen (not on a piece). After dismissing the upgrades, the message written above should be displayed.

@Monkey-bored could you please update your progress regarding this issue?


Add topics for all exercises in preparation for Nexercism

Version 2.0 of Exercim will utilize the topics heavily, so I strongly suggest adding them to all exercises in your config.json
Please note that we are trying to be consistent between tracks and decided to you snake_case for topics.
You can find list of topics here - https://github.com/exercism/problem-specifications/blob/master/TOPICS.txt
Fill free to add something if needed

Topics (from the file linked above) should be added as an array of strings in the topics key of each exercise in this file:
https://github.com/exercism/cfml/blob/master/config.json


fix(analytics): exploring use of traits

Try out this version of the Hiro Wallet - download extension builds.

Two changes here:

Initialising analytics as per segment library documentation. Behaviour is the same, but by loading the analytics key later (only if user has consented), we avoid the case of analytics sometimes being undefined.

Trials use of Segment/Mixpanel traits, used to store account-level details that don't correspond to a given event

Merging but cc/ @markmhx's eyes

Trials use of Segment/Mixpanel traits, used to store account-level details that don't correspond to a given event

Thanks! Sounds good


Using captures in ? with OR branches has an effect on captures outside the optional matching

It's a bit much, so I'll just start with the testcase:
require 'bundler/inline'

# Using captures in `?` with OR branches has an effect on captures outside the optional matching
gemfile do
  source 'https://rubygems.org'
  gem 'rubocop-ast', '1.32.3'
  gem 'minitest'
end

require 'minitest/autorun'

class Matcher
  class << self
    extend RuboCop::AST::NodePattern::Macros

    def_node_matcher :one_branch, <<~PATTERN
      (
        send _ $_method_name
        (
          sym
          {$_}
        )?
      )
    PATTERN

    def_node_matcher :two_branch, <<~PATTERN
      (
        send _ $_method_name
        (
          sym
          {$_ | $_}
        )?
      )
    PATTERN

    def_node_matcher :three_branch, <<~PATTERN
      (
        send _ $_method_name
        (
          sym
          {$_ | $_ | $_}
        )?
      )
    PATTERN
  end
end

class Test < Minitest::Test
  def assert_match(code, matcher, expected)
    ast = RuboCop::AST::ProcessedSource.new(code, 3.3).ast
    actual = Matcher.send(matcher, ast)
    assert_equal(expected, actual)
  end

  def test_one
    assert_match("foo", :one_branch, [:foo, []])
  end

  def test_one_optional_matches
    assert_match("foo(:bar)", :one_branch, [:foo, [:bar]])
  end

  def test_two
    assert_match("foo", :two_branch, [:foo, []])
  end

  def test_two_optional_matches
    assert_match("foo(:bar)", :two_branch, [:foo, [:bar]])
  end

  def test_three
    assert_match("foo", :three_branch, [:foo, []])
  end

  def test_three_optional_matches
    assert_match("foo(:bar)", :three_branch, [:foo, [:bar]])
  end
end

#   1) Failure:
# Test#test_two_optional_matches [test.rb:68]:
# Expected: [:foo, [:bar]]
#   Actual: [[:foo], [:bar]]
#
#   2) Failure:
# Test#test_two [test.rb:64]:
# Expected: [:foo, []]
#   Actual: [[], []]
#
#   3) Failure:
# Test#test_three [test.rb:72]:
# Expected: [:foo, []]
#   Actual: [:foo, [], [], []]
#
# 6 runs, 6 assertions, 3 failures, 0 errors, 0 skips

There are three node patterns, all very similar except that an OR group has different amount of branches. I expect them to all return the same thing but what actually happens is that depending on the amount of branches the output changes:

One branch: As expected (but also not very useful)
Two branches: The first capture is wrapped in an array and is empty when the optional part matches
Three branches: When the optional doesn't match it has 4 captures but the first is not wrapped, and when the optional does match it only return 2 captures (with the expected shape even)

There seems to be some state leak. While I'm getting better at writing node patterns, understanding what is going on here is far beyond me. I think this pattern should be valid but maybe I'm misunderstanding something?

Thanks for opening the issue.
Yes, I agree that these patterns should all be valid and return the exact same results for any input.


3036 tests add fillet

Implemented tests for getPathToExtrudeForSegmentSelection:
This PR adds tests to verify that the function correctly identifies extrude paths based on selected segments across different sketches. The tests cover multiple scenarios, including cases with multiple extrusions and situations where no valid extrusion is present. This helps ensure the function behaves correctly and handles complex cases.
Additionally, for the sake of testing, the addFillet file was heavily refactored. All fillet-related logic was moved from the modellingMachine file to addFillet, making the code more modular and easier to test.
Related Issue: #3036 (from #2606: list of stuff for fillets)

@Irev-Dev could you please have a look on errors in the addFillet.test.ts and test cases overall ?

Update:
Adjusted the initialization logic to ensure that engineCommandManager connects properly. Same as in the artifactGraph.test.ts

Sorry left a few comments. Let me know what you think.

Comments are pure gold, thank you! I will start working on them tonight and hopefully tackle over the weekend :)

Merge it!
Before you do you will need to make the linter happy

This is probably not your fault, changing CI to not allow any warning has been a recent change, but since there are only two it should be a quick fix.


Server Crash when placing Tank with Fastcraft installed.

http://pastebin.com/xP6sHreF

This bug has already been reported and has nothing to do with fastcraft. We will fix this for next release (tomorrow).

Awesome, thanks.

Today? Aha, means that I got some work to do  :P

It would be great if you could. This is a bit of a show-stopper (together with the lighting update thing which is a show stopper on servers)


After upgrading to 0.2.8 Installed Charts list is empty

I was on 0.2.6 as the is no binary available for 0.2.7, upgraded to 0.2.8 and the list of charts is now empty:

I have 4 charts installed but can't list them (tried reset cache, private, different browsers and it always fails)

Reverting to 0.2.6 fixes the problem
P.S: This is on macOS Ventura usign the binaries provided here in "releases" btw and the screen are from firefox, although I can repo in safari and chrome

0.2.8 introduced some namespace filtering, together with data caching. Do you see a list of namespaces on the left in 0.2.8?

No this is empty too:

There are indeed several namespaces including "default"

Oh interesting but they are there although css style is set to "display-none" clearing the cache does not seem to help though

One more question: do you have something in your address bar for filterNamespaces=... parameter?

Nope just the default URL when helm-dasboard starts: http://localhost:8080/#context=gke_XXXXXX

@mc-zact Do you see any errors in the JavaScript console?

Been a bit busy this week @ronahk  I do see erros in the JS console that I did not notice at the time:
    buildChartCard http://localhost:8080/static/list-view.js:49
    loadChartsList http://localhost:8080/static/list-view.js:14
    loadChartsList http://localhost:8080/static/list-view.js:13
    jQuery 4
        c
        fireWith
        l
        o

Not sure that's the same issue @TalZiv  I use Firefox in strict mode if there was a block I would see it in the console to, and I'm not using any 3rd party ad blocker, also curious why your ad-blocker would block any resources,, would that be because of datadog monitoring?

The new release 1.0 has changed a bit the logic of handling the namespaces. Could somebody test if this issue is still relevant with 1.0?

Looking good for me now :)


fqdn: split DNSPoller into RuleGen and DNSPoller

The DNSPoller does two things: poll DNS and generate rules when they change. Most of the code and complexity is in the generation and we will soon have sources of DNS data that aren't from a DNS poll. We might also end up with a more generic scheme to generate rules that isn't specific to the fqdn package, and this makes it clearer what component would be replaced.
There is no change in functionality but note that DNSPoller.LookupUpdateDNS is now split into .LookupUpdateDNS and .UpdateGenerateDNS (the first commit in this PR). This meant that some tests were changed but they now update the DNS data directly instead of doing a lookup as the poller tests still do.

This change is

test-me-please

test-me-please

test-me-please

Coverage decreased (-0.03%) to 43.329% when pulling 6dff092072c9481746b9a8c76644289c23d5e86b on raybejjani:fqdn-split-dnspoller into 61ec92ce49afa33b1574a8ef1d15e7f5a5e235da on cilium:master.


Update Tutorial with new Zookeper Version and instructions

Follow on https://github.com/druid-io/druid-io.github.io/issues/193#issuecomment-162354625

@AdrieanKhisbe, thanks for the contribution!
Could you please fill out the Druid Individual CLA at http://druid.io/community/cla.html, or if you work for a corporation that has already filled one out could you let us know which one that is?

Hey @gianm! I just filled the form :)

@AdrieanKhisbe thanks! :+1:

you're welcome :)


MetaGOflow v1.0 fails to run because of incompatible Prosite binary in IPS 5.57-90.0

MetaGOflow v1.0 aborts with an error on cluster using AMD EPYC 7643 cpus due to the following Prosite binary incompatibility in InterProScan:
28/07/2023 13:53:31:803 Running InterProScan v5 in STANDALONE mode... on Linux
log4j:WARN No appenders could be found for logger (org.apache.activemq.broker.BrokerService).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
28/07/2023 13:53:37:135 RunID: hpc066.a.incd.pt_20230728_135336815_i87a
28/07/2023 13:53:44:194 Loading file /var/lib/cwl/stg0e3d7f9f-ad7f-4ce2-9653-2b028d4e70b2/2000001_3000000.faa
28/07/2023 13:53:44:195 Running the following analyses:
[Pfam-35.0,ProSitePatterns-2022_01,ProSiteProfiles-2022_01,TIGRFAM-15.0]
Pre-calculated match lookup service DISABLED.  Please wait for match calculations to complete...
28/07/2023 15:14:58:144 Uploaded 368019 unique sequences for analysis
2023-07-28 15:17:13,145 [amqEmbeddedWorkerJmsContainer-3] [uk.ac.ebi.interpro.scan.management.model.implementations.RunBinaryStep:199] ERROR - Command line failed with exit code: 1
Command: python3 bin/prosite/runprosite.py data/prosite/2022_01/profile_models /tmp/hpc066.a.incd.pt_20230728_135141098_4rxh//jobPrositeProfiles/000000212001_000000213000.fasta /tmp/hpc066.a.incd.pt_20230728_135141098_4rxh//jobPrositeProfiles/000000212001_000000213000.raw.out bin/prosite/pfsearchV3 -f -o 7 -t 4
Error output from binary:
Error setting affinity!
Error running prosite binary bin/prosite/pfsearchV3

2023-07-28 15:17:13,150 [amqEmbeddedWorkerJmsContainer-3] [uk.ac.ebi.interpro.scan.jms.worker.LocalJobQueueListener:216] ERROR - Execution thrown when attempting to executeInTransaction the StepExecution.  All database activity rolled back.
java.lang.IllegalStateException: Command line failed with exit code: 1
Command: python3 bin/prosite/runprosite.py data/prosite/2022_01/profile_models /tmp/hpc066.a.incd.pt_20230728_135141098_4rxh//jobPrositeProfiles/000000212001_000000213000.fasta /tmp/hpc066.a.incd.pt_20230728_135141098_4rxh//jobPrositeProfiles/000000212001_000000213000.raw.out bin/prosite/pfsearchV3 -f -o 7 -t 4
Error output from binary:
Error setting affinity!
Error running prosite binary bin/prosite/pfsearchV3

This seems to be due to a Prosite binary incompatibility as reported elsewhere with this version of IPS..
The version of IPS in v1.0 is 5.57-90.0 from Aug 2022. Unfortunately, even if this problem has been resolved in newer versions of IPS (latest: June 2023), changes to Docker mean that the current Dockerfile for IPS in MetaGOflow will not compile the newer versions of IPS.
The only way to resolve this for MetaGOflow v.1.0 would be to recompile the Prosite binaries with the newer compatible libraries and rebuild the IPS 5.57-90.0 container. This may not be worth the effort at this stage with more than half of the first EMO BON batch of data already analysed.
However, this should be resolved for MetaGOflow v1.1 (or whatever version we use to analyses the second EMO BON data tranch).

I've made some notes about this issue in a GoogleDoc (request access):
InterProScan version needs updating
Here the issue is that the version of IPS in MGF v.1.0.0 uses version 5.57-90.0 which contains an Prosite binary package that is incompatible with AMD EPYC cpus (specifically 7643 cpus (launched 2021), but presumably others with the same architecture). According to this post, the ProSite pftools library needs to be updated to v3.2.11. The latest version of IPS is 5.64-96.0.
This exact error is noted in the IPS documentation:
Additionally on some systems, specially on cluster environments, the following error has been reported
Error setting affinity!
Error running prosite binary bin/prosite/pfsearchV3
This means the provided binary is not compatible with your system. We have included alternative binaries that you can try, by updating you interproscan.properties file to point to the alternative binaries:
binary.prosite.pfscanv3.path=${bin.directory}/prosite/altbin/pfscanV3.noaf
binary.prosite.pfsearchv3.path=${bin.directory}/prosite/altbin/pfsearchV3.noaf
If the problem persist, you may need to compile those binaries from source, making sure to build without affinity by compiling with the flag
cmake -DUSE_AFFINITY=OFF ..
ACTION:
We need to make the above changes to IPS version 5.64-96.0 and rebuild the docker image.
However, changes to Docker mean that the current Dockerfile will no longer compile - the issue is this command:
RUN echo "localhost" > /etc/hostname && echo "<IP_ADDRESS>\tlocalhost" > /etc/hosts
Using this command is no longer persistent in the resulting image.
I think (this is beyond my understanding of Docker) it needs to be set via a parameter in the docker run command, or in the docker-compose config.

Re-opening...


code sync

Elaborate on code sync, and update data persistence to reflect new volumes behavior.
Release Playbook

[ ] Rebase against master
[ ] Code review
[ ] Merge into master
[ ] Verify changes at http://site-staging.convox.com
[ ] Promote release on site-production in the convox/production Rack

 Better Code Sync docs

Let's also add a separate doc specific to code sync that describes details of how it works, including dockerignore etc

Do you think it'd be useful to still keep a brief Code sync section in the Running Locally doc that links to the standalone Code sync doc?

@ianmalott Good suggestion. Just added.


The extract_keys method may fail if the token has three or more words

https://github.com/Olivine-Labs/luassert/blob/36fc3af9621696a9dfcf71c0bcd25cdbc9475cf8/src/util.lua#L322-L329
At line 328, the longkey maybe wrong in further iterations.
For example: if the tokens is {'is', 'match', 'error'}, the longkey variable will be match_match_error at the second iteration in the inner while loop. So it may fail to get the longest matching key when the key has three or more words.
Here is the potential fix which I brought up:
-      longkey = (token .. '_' .. key)
+      longkey = i > 1 and (tokens[i-1] .. '_' .. key) or key

a failing test case would be nice

tried this;
  it("multiple section modifiers #only", function()
    assert.is_not_is_not_equal(1, 1)
    assert.not_is_not_is_equal(1, 1)
    assert.not_not_is_is_equal(1, 1)
    assert.is_is_not_not_equal(1, 1)
    assert.is_not_is_not_is_not_equal(1, 2)
    assert.not_is_not_is_not_is_equal(1, 2)
    assert.not_not_not_is_is_is_equal(1, 2)
    assert.is_is_is_not_not_not_equal(1, 2)
  end)

But that passes nicely, so cannot reproduce this. Am I missing something @Triple-Z ?

@Tieske  Sorry, This is not what I am meaning...

With the change which I proposed before, luassert will recognize the longer token and match it first.
Like this test:
it("three words token #only", function()
  assert:register("assertion", "three_words_token", function() print("can you see me?") return false end, "assertion.same.positive", "assertion.same.negative")
  assert:register("assertion", "than_three_words_token", function() print("can you see me now?") return false end, "assertion.same.positive", "assertion.same.negative")
  assert:register("assertion", "more_than_three_words_token", function() print("can you see me now?") return false end, "assertion.same.positive", "assertion.same.negative")

  assert.is_not_more_than_three_words_token()
end)

However, I find there is another bug, the luassert cannot find the longest token if the tokens are not continuous.
Like this:
it("three words token #only", function()
  assert:register("assertion", "three_words_token", function() print("can you see me?") return false end, "assertion.same.positive", "assertion.same.negative")
  -- assert:register("assertion", "than_three_words_token", function() print("can you see me now?") return false end, "assertion.same.positive", "assertion.same.negative")
  assert:register("assertion", "more_than_three_words_token", function() print("can you see me now?") return false end, "assertion.same.positive", "assertion.same.negative")

  assert.is_not_more_than_three_words_token()
end)

It would raise an error: "luassert: unknown modifier/assertion: 'is_not_more_than'" .

tbh, I think the best route would be to document that tokens can have a maximum of 3 words. That is fair enough imo, and prevents us from going down a rabbit hole with this one.
wdyt @ajacksified @DorianGray ?

I just ran into the same problem, but in a little bit more surprising setup. Executing a spec with require "busted.runner"() directly worked just fine with a three-word-assertion. Running the same code from the console with busted gave me the "unknown modifier/assertion" error. Thanks to this thread I was able to shorten the assertion and circumvent the problem. Still quite the pitfall.


Having trouble with libarchive in Nobara 37 (a distro based on Fedora)

I am getting the following error when I try to install via pip (python -m pip install dist/*.whl):
 × Running setup.py install for libarchive did not run successfully.   │ exit code: 1   ╰─> [6 lines of output]       running install       /usr/lib/python3.11/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.         warnings.warn(       Verifying that the library is accessible.       Library can not be loaded: libarchive.so: cannot open shared object file: No such file or directory       error: libarchive.so: cannot open shared object file: No such file or directory       [end of output]

Have you tried installing libarchive with dnf install libarchive-devel?


Cursor position is off when ZF_PROMPT has special characters like ansi escape codes

I'm trying to use a character like ❯ as the ZF_PROMPT, but it seems like it the cursor is shifted way right of where text is actually inserted:
https://user-images.githubusercontent.com/159/210809294-81ca5d92-b019-4746-9d02-136ac6f2e11f.mov
This is even more pronounced when adding ansi color codes, ie ZF_PROMPT="\e[41m   \e[0m\e[31m\e[0m" :
https://user-images.githubusercontent.com/159/210811146-38b11451-212f-4be9-b29a-d4c80be5a936.mov

Hi @technicalpickles, thank you for the thorough bug report! There are two things wrong here
The first is that zf doesn't yet support Unicode. I haven't made that super clear yet though, so that's on me. I do have plans to add utf-8 support soon.
The second is that I don't escape the ANSI escape sequences. That's a bug and I can get that fixed sooner.

I have created two issues to track this: https://github.com/natecraddock/zf/issues/15 and https://github.com/natecraddock/zf/issues/16
I won't close this issue until both are completed

I have now resolved this in my https://github.com/natecraddock/zf/tree/unicode branch. You are welcome to test now if you would like, or just wait for the 0.7.0 release. I should be adding the remainder of the unicode support soon and releasing the new version.

Will be released in zf 0.7.0 soon (hopefully this week)


Migrate to the fun zoomable sunburst diagram

Example: https://observablehq.com/@d3/zoomable-sunburst
Requires turning .csv to a hierarchical .json. See https://d3js.org/d3-hierarchy/stratify
@staylor7 's attempt: https://observablehq.com/d/6a5d607535b9bd1b

I made some progress on stratifying the data (I specified a more detailed hierarchy than the two layers that @staylor7 proposed.), though I could not get the sunburst to render yet.
(Accidently committed these to main, whoops.)
https://github.com/staylor7/rare-diseases/blob/83aac099fee8e5cdb08a2a3b3ba5e7342018407a/src/sunburst.ts#L16C1-L26C2

thanks quinn! Will take a look today!

I will try this too but I keep forgetting how to do the whole build thing in Terminal. Sorry I’m so behind - oy!
Steve

Stephen Taylor
Professor of Music
University of Illinois at Urbana-Champaign
Co-director, Illinois Modern Ensemble
www.stephenandrewtaylor.net
217 333-3712 office

On Dec 21, 2023, at 12:22 PM, SallyXue-0114 @.***> wrote:
thanks quinn! Will take a look today!
—
Reply to this email directly, view it on GitHub https://github.com/staylor7/rare-diseases/issues/9#issuecomment-1866744313, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHPFIKJRXACCJ2FBV4U2GVDYKR5AFAVCNFSM6AAAAABAFGHGK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRWG42DIMZRGM.
You are receiving this because you were mentioned.

New updates from Sally:

I managed to fix all the 'Problems' (the red wiggly lines) in Quinn's version of the code, but it's still not displaying anything. The issue might be related to the connection with main.ts? I've pushed my changes to the main branch.

In the 'sunburst-js' branch: Earlier, I converted our data (CSV file) into a two-layer stratified JSON file (hierarchy.json). Now, when I run script.js (I do this by using the 'Go Live' button in VSCode), it displays a kind of sunburst as shown in the following screenshot (this is just half of it; it's too large to capture entirely).

However, it's a bit messy at the moment (and sometimes freezes) because there's so much information in our CSV file.


Loss is not minimizing after 2nd epoch.

Hello everyone! I tried to implement the AC loss function on a U-Net model.
I am using the the AC loss as loss function and the Dice Coefficient as metric.
I am using the NIH dataset for training (https://wiki.cancerimagingarchive.net/display/Public/Pancreas-CT).
Since the data format is different (8, 256, 256, 1), I changed the indexes.
My code is the following:
def Active_Contour_Loss(y_true, y_pred):

    y_true = K.cast(y_true, dtype = 'float64')
    y_pred = K.cast(y_pred, dtype = 'float64')

    """
    lenth term
    """

    #Reordered indexes, because data format is different.
    x = y_pred[:,1:,:,:] - y_pred[:,:-1,:,:] #y_true shape is: (8, 256, 256, 1)
    y = y_pred[:,:,1:,:] - y_pred[:,:,:-1,:] #y_pred shape is: (8, 256, 256, 1)

    delta_x = x[:,1:,:-2,:]**2
    delta_y = y[:,:-2,1:,:]**2

    delta_u = K.abs(delta_x + delta_y)

    epsilon = 0.00000001 # where is a parameter to avoid square root is zero in practice.
    w = 1
    lenth = w * K.sum(K.sqrt(delta_u + epsilon)) # equ.(11) in the paper

    """
    region term
    """

    C_1 = np.ones((256, 256))
    C_2 = np.zeros((256, 256))

    #Reordered indexes, because data format is different.
    region_in = K.abs(K.sum( y_pred[:,:,:,0] * ((y_true[:,:,:,0] - C_1)**2) ) ) # equ.(12) in the paper
    region_out = K.abs(K.sum( (1-y_pred[:,:,:,0]) * ((y_true[:,:,:,0] - C_2)**2) )) # equ.(12) in the paper

    lambdaP = 1 # lambda parameter could be various.

    loss =  lenth + lambdaP * (region_in + region_out) # equ. (8) in the paper

    return loss

However, the output of the training does not go well:
Epoch 1/20
18750/18750 - 3202s - loss: 3657.6096 - dice_coef: 0.0187 - val_loss: 909.7355 - val_dice_coef: 0.5784
Epoch 2/20
18750/18750 - 3150s - loss: 716.8154 - dice_coef: 0.0240 - val_loss: 909.7353 - val_dice_coef: 0.5785
Epoch 3/20
18750/18750 - 3158s - loss: 717.3530 - dice_coef: 0.0230 - val_loss: 909.7353 - val_dice_coef: 0.5785
Epoch 4/20
18750/18750 - 3161s - loss: 718.0414 - dice_coef: 0.0221 - val_loss: 909.7353 - val_dice_coef: 0.5785
Epoch 5/20
18750/18750 - 3126s - loss: 717.6503 - dice_coef: 0.0222 - val_loss: 909.7353 - val_dice_coef: 0.5785
Epoch 6/20
18750/18750 - 3133s - loss: 718.0792 - dice_coef: 0.0229 - val_loss: 909.7353 - val_dice_coef: 0.5785
Epoch 7/20
18750/18750 - 3092s - loss: 717.6919 - dice_coef: 0.0229 - val_loss: 909.7353 - val_dice_coef: 0.5785

Any ideas what I am doing wrong?
Thanks in advance!

My mistake, I am sorry..
I should have typed y_true = K.cast(y_true, dtype = 'float64')

I also just reshaped my data, so that I don't have to do any other changes in the original code:
    y_true = tf.transpose(y_true2, [0, 3, 1, 2])
    y_pred = tf.transpose(y_pred2, [0, 3, 1, 2])

but unfortunately the training output is exactly the same.

Hello, I also encountered the same problem, have you solved it?

Hello!
I haven't solved the problem yet.
I contacted the author and he said that the loss is sensitive to unbalanced classes problems on diiferent datasets.
So, he suggested the following things:

Try to find two another well-choosed hyperparameters a and b: a* regionin + b * regionout in the region term according to your dataset.
Try to train with a pre-trained model (no need converged too much) to tackle the initialisation problem  of model and the AC model.

Good luck!
Please update if you solve it, I wll do the same :)

Hi there, I solved this problem by crop my data. I think the loss is sensitive to unbalanced categories. And  the learning rate is 0.0005, keep the y_pred is a probability map between [0,1]. No other code changes.

Thank you very much!
I can't test it for the next few weeks, but I will try and also update.


Remove some of the extra logs

getAllClustersForUpgrade is called multiple times each loop and the log is repetitive.
getClustersNonCompliantWithPolicy logs can be condensed into one line

Signed-off-by: Saeid Askari<EMAIL_ADDRESS>

/approve

/lgtm

/cherrypick release-4.11

/cherrypick release-4.10


Add an option to subscribe to compressed image topics.

Also allow for relative names in cam_base_topic.

I have added a new parameter called image_sub_compressed: false. When enabled, aruco_tracker will subscribe to cam_base_topic/compressed instead of cam_base_topic.
This modification is a workaround, because normally, image compression is handled by setting image_transport::TransportHints. However we are unable to use image_transport with lifecycle nodes.
Enabling this feature makes aruco_tracker work much faster and allows us to successfully use it with a multi-camera setup.

@Mergifyio backport iron rolling


Performance guideline missing changes

@SwRaw Please check the following threads:

https://github.com/ROCm/HIP/pull/3483#discussion_r1682112227
https://github.com/ROCm/HIP/pull/3483#discussion_r1677621743
https://github.com/ROCm/HIP/pull/3483#discussion_r1679144336
https://github.com/ROCm/HIP/pull/3483#discussion_r1679773120


Unable to detect wither a cursor is visible or not on Linux

Hi, would it be possible to add functionality to this to detect the visibility of a cursor across all platforms (working on linux specifically)?
This would be essential in order to switch between SimulateMouseMovement and SimulateMouseMovementRelative based on wither or not the cursor is visible (for fps games).

Hi! Thanks for asking! I will look into it and let you know whether it can be added.

I've looked into this, and it looks like it's easy to achieve only on Windows (which has a GetCursorInfo function). On macOS there is the CGCursorIsVisible function which is deprecated and doesn't have a replacement. For X11 I wasn't able to find anything at all, unfortunately.
That said, I won't look into it further at this time since I have other stuff to implement first. I'll close this as a won't-fix, but we can continue this discussion. I'll also gladly accept a pull request.

Hi again friend, I haven't had any luck finding something for X11, perhaps xquerypointer?

Sorry @ZeoWorks, can't really help you with this as I don't know myself.


[WIP] Meshery Operator - Lifecycle Management

Description
PR for Meshery operator lifecycle management.
Updates operator manifests for the system start, system restart and system channel switch commands.
Signed commits

[X] Yes, I signed my commits.

// adding @kumarabd to this thread

Yay!

@aneeshnema, will you open an issue to ensure that when meshery system update is invoked, should these Meshery Operator manifests are refreshed as well?

@Aisuko, these manifests should be accounted for in the air-gapped instructions. Will you crate an issue for this?

Air-gapped support
Sent from my mobile

On Apr 23, 2021, at 1:30 AM, abishek @.***> wrote:

@kumarabd commented on this pull request.
In mesheryctl/internal/cli/root/system/start.go:

@@ -301,6 +302,43 @@ func start() error {
if err != nil {
return err
}

operatorURL := "https://raw.githubusercontent.com/layer5io/meshery-operator/master/config/manifests/default.yaml"

@leecalcote Wt I meant was to not add it to brew/scoop but continue pulling from the Meshery-operator repository. This is to maintain consistency.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@leecalcote @metonymic-smokey Related concern- https://github.com/layer5io/meshery/issues/2758#issuecomment-828151529


Zypper package: Fix for global options property

Signed-off-by: dheerajd-msys<EMAIL_ADDRESS>Description
Unable to install a package via the package resource with zypper global options.
package 'sssd' do
   options '-D /tmp/repos.d/'
end

The options in the package resource will be appended to the end of the zypper command:
zypper install sssd -D /tmp/repos.d/

the proper way and the only way it works is lke this:
zypper  -D /tmp/repos.d/ install sssd
zypper --help
Usage:
        zypper [--global-options] <command> [--command-options] [arguments]
        zypper <subcommand> [--command-options] [arguments

Global Options:
--reposd-dir, -D <dir>  Use alternative repository definition file

Introduced global_options property to the zypper_package resource
Issues Resolved
fixes https://github.com/chef/chef/issues/7490

@lamont-granquist @tas50 @btm Please review it again. Thank you.

You will need to rebase on master to make expeditor happy.

I am adding functional test cases to this package now.

Yes @rhass I will revert these changes, I just wanted to confirm if functional test cases are running for zypper_package in travis. They are working properly in jenkins adhoc build (http://manhattan.ci.chef.co/job/chef-test/architecture=x86_64,platform=sles-12,project=chef,role=tester/217/console) and locally on suse and opensuse VM. And files which are commented out was failing here in travis and kept me stuck to verify for zypper_package tests.

@rhass @lamont-granquist Please re-review this PR again.
Thanks.


Dump app yaml when test-examples.sh fails

What this PR does / why we need it:
Dumps out all apps as YAML when a test app from test-examples.sh fails.
When this test fails it's pretty hard to diagnose what could be going wrong.
Does this PR introduce a user-facing change?

NONE

LGTM;  the most I've ever looked forward to getting dumped


Get pointblank table to render with targets

Describe the bug
In pr #18 there is a Quarto document with a pointblank table in it that I can't get to render.  Opened an issue in pointblank (https://github.com/rich-iannone/pointblank/issues/448), but might need to figure out a workaround for the time being.

had to update gt to latest CRAN version and pointblank to dev version.


Exclude directories/tags

Would it be possible to exclude certain folders or tags from resurfacing on various complements?

Hi, @crazymedguy :)
Is it the case of [Front matter complements](Front matter complement) that you want to exclude?

Hello, nope I mean when generally typing in obsidian and getting partial matches. I have certain links that I'd like to exclude from being suggested, such as "event notes", or work-related or privacy-related stuff. I can't have them pop out while typing because it would obscure the results.

Thank you for your explanation :) I see.
It would be possible to hide suggestions (not indexing) whose path matches specific patterns like a Exclude prefix path patterns option.
If you are OK, I'll add an option.

Ah.. but it doesn't show suggestions, so it doesn't need indexing.. 😅

Therefore, It seems best to add a ⚙Exclude prefix path patterns to the Internal link complements section and the Front matter complements section?

Sounds like a good idea! So if it excludes the page, it isn't even indexed at all, is that what you mean? Sounds good. Maybe some support for inline metadata like in Dataview (exclude:: true) would be great too

So if it excludes the page, it isn't even indexed at all, is that what you mean?

Yes. I'll try it first.

@crazymedguy
I have released to v5.9.0 🚀
Please confirm whether it works as you expected.

Would it be possible to automatically pick up the directories the directories from Settings > Files & Links > Excluded files?
In Omnisearch the following is given:

@sohanglal
Duplicated https://github.com/tadashi-aikawa/obsidian-various-complements-plugin/issues/203


add support for default timeout to timemon

To cater for use-cases where a blanket timeout rule is to be applied (i.e. restarting any program which runs over a given threshold), a new default (short form: d) argument is needed.
If a program is specified by name, the default value is ignored for that program's uptime check.

Closed by #9


JPG images with embedded CMYK profile show inverted in Illustrator

Hi, first of all let me say I'm impressed with this library and all functionalities it offers. Looks like a very promising replacement package for pdfkit!
I've noticed an issue with JPG files with an embedded color profile, they are rendered inverted in Adobe Illustrator. After some digging through the issues/pr's, I used the "after" PDF found in this PR https://github.com/Hopding/pdf-lib/pull/415.
Illustrator

Did some digging in and the source image has the U.S. Web Coated (SWOP) v2 profile embedded:

I'm not sure why this happened but I replaced the image in Illustrator with the original one and exported to a new PDF (out-new.pdf) which renders fine.
Any idea what might cause this issue?

same issue, any news?

Exact same issue I've been working on for two days now. Everything is perfect apart from this ?


Infinite loop caused by InscribedRectangle ctor

To reproduce
This was reported by a customer, and means the following configuration occured:

Tracking space is room scale
UnityBoundary.TryGetGeometry returns true
The boundary point array is empty

When this happens, the do-while loop inside of the InscribedRectangle ctor never returns.
It should be straight forward enough to add some some input checking to prevent getting into this state.

Unity Version: 2018.3
MRTK Version: RC1 Refresh

Fixed via #4550


Sh

Biggest change is that non-compatible devices quickly exit

Please do the changes in the previous pull request.

Sorry, I don't know how...

I don't see a button "Commit suggestion" so you better do it. Next time I'll just do it from the commandline.


removes nonce struct in favor of bundledtxinfo

📝 Summary
I've been reading through the primitives module and found this Nonce struct to be redundant and marked for deletion. This change so far does just a primitive replacement with BundledTxInfo. It probably also needs:

renaming of variables from nonce to something more relevant
getters on the struct to make stuff like nonce.nonce.nonce more readable.

Let me know what you think.

✅ I have completed the following steps:

[x] Run make lint
[x] Run make test
[ ] Added tests (if applicable)

Can you change the names of the variables as you mentioned so instead of having nonce.nonce we have something like tx_info.nonce?
Maybe in a future PR we can rename BundledTxInfo::nonce to something like BundledTxInfo::account_nonce (open to ideas) so we don't have nonce.nonce.


cenomanian, desulphuration

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[c,d]

/trunk merge


fix(linting-ui-bug): Implemented linting clean on focus change of editor to solve linting UI issue

This PR solve the stale UI marker isuse in linting

Covered in another PR


Clarify motivation

It seems like this package provides the same functionality as the native julia implementations provided by Transformers.jl. https://chengchingwen.github.io/Transformers.jl/stable/huggingface/#Transformers.HuggingFace.load_tokenizer
In view of that, could you offer some motivation for this wrapper? It may also be helpful to add such a discussion to the README to allow users to make an informed decision.

Motivation:

There is also the https://github.com/JuliaGenAI/HuggingFaceDatasets.jl?tab=readme-ov-file


Update rust to version 1.7.0

resolves #27

I'm in the process of testing this out.
1 question: why is the addition of libssp to the post link flags necessary with this update to rust? What happens when it is omitted? Is it something we'll always need, or is it potentially distro dependent?

Without the libssp, the linking fails with undefined references to stack_chk_fail

I can add SECURITY_LDFLAGS_append locally for ARM if people aren't using the stack protection generally and just pop that commit from the PR

This appears to work OK for me with or without the -lssp addition.
I'd prefer both not adding it all the time if not everyone requires it, and if it's something that people are going to commonly run into, I'd prefer we support it somehow within meta-rust itself (so folks don't need to go hunting around too much for a solution.
Perhaps it could be added to an include like (or even in the same file as) conf/distro/include/rust_security_flags.inc? If not, I suppose a PACKAGECONFIG value would also work.

Added the LD options to conf/distro/include/rust_security_flags.inc

Works for me, thanks again for putting this together.


Data Model: Review max length limits in database schema

Some of the max length limits in the database schema need extending.
With regard to meta_title and meta_description, see: https://github.com/TryGhost/Ghost/pull/4126#issuecomment-56632903
While we're at it, it's worth reviewing all of the max length limits now that we have more information about how people use their blogs.
For all of the "text" fields that don't have a clear answer to how long they should be, we need a plan for:

what field types should we use and why
what length should the field be in the database (hard limit)
to what length should the field be validated (taking utf8mb4) into account (soft limit)

We don't get to change these things later, only thing we can easily do is increase a soft (validated) limit
So it needs to be right, and future proof
In order to implement the changes, we will need #601 - the ability to change the max length on a column.
We're going to make these changes as part of the alpha

Closing this as it's effectively covered by #7432 and we don't need 2 issues open :)


If tests finish as "failed", the status is still green

For example - job, workflow file .
2 tests failed, job result is failed.
{
  "sha": "",
  "state": "failure",
  "context": "Testing Farm - 8to9",
  "description": "Build finished ",
  "target_url": "http://artifacts.osci.redhat.com/testing-farm/23ccb40f-e37b-4f83-9dca-f876c0a40ebd"
}

But overall job is marked as successful.

In the job file there is something wrong:
{
  "message": "Not Found",
  "documentation_url": "https://docs.github.com/rest"
}

I'm having the same problem in oamg/convert2rhel#585. It seems that the sha is not being passed correctly in the update.json file.
Raw logs, final request from github actions logs

The testing-farm-as-a-github-action gets the sha from $(git rev-parse HEAD). Thus it counts with a fact, that the git repository is already prepared and is a current directory before calling the action. Here is example. This is intended.
Problem, that @r0x0d has, seems to be an unprepared git repository -> is not a current directory. Thus the SHA can not be obtained:
Run echo "::set-output name=SHA::$(git rev-parse HEAD)"
  echo "::set-output name=SHA::$(git rev-parse HEAD)"
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
fatal: not a git repository (or any of the parent directories): .git

@fernflower @r0x0d Could that be it?
As a first step in fixing this, I propose to halt the action, if the SHA step is not successful. In this way, the user will be at least warned, that something went wrong.

Hi, @zmiklank! Sorry for the late response.
I agree with you, checking out the code would definitely help us in this case. The only problem is that (at least for Convert2RHEL) we are using the pull_request_target event to trigger our workflow, and I vaguely remember that checking out code wasn't the most recommended thing to do (I may be wrong on that one).
Still, in cases where we can't checkout the code, would it be ok to do what I mentioned? I mean, the action can still try to figure out by default what is the SHA they way it is doing right now, the functionality wouldn't change, the only thing is that every one who is using this action will be able to override this input with github.event.pull_request.head.sha, for example.

Hi, @r0x0d.
I am sorry, I think I can not understand your use-case. You want to trigger Github Action on Pull Request, but not test the PR's code?
I therefore cannot think about a use-case, where passing the SHA would be advantageous. The SHA is used only for posting results to the PR. If the tested code is not from the PR, then I can not see why to post a result to it.
Can you please further explain your use-case?

Reference: Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests.

Thank you for the reference. I agree, that running tests on unchecked and unknown code is not secure. We also use this action to test PRs, but we set trigger to PR comment, and we allow only authorized users to run the tests. See example.

Hey @zmiklank! For sure.

I am sorry, I think I can not understand your use-case. You want to trigger Github Action on Pull Request, but not test the PR's code?

We want to trigger the tests in the PR for our internal users, but not for the external ones. If an external user opens a PR for us, we want to validate that manually first, and then, we think that the PR is “safe to test”, we can trigger that either manually or with a label or something like that.
The deal for us is: We have some secrets we need to pass alongside the request because they are vital to our integration test suite. We don't want to rely on making comments or placing labels to internal collaborators to trigger the tests, so we decided to keep things as they are right now and trigger that automatically when a contributor pushes the code.
I definitely agree with you, there are numerous ways of doing that, and for sure, the way you mentioned using comments is one of them, but we would rather keep things more automatically for now and run on every push in our PRs.
And for further clarification, this is the way we are doing it right now.

I therefore cannot think about a use-case, where passing the SHA would be advantageous. The SHA is used only for posting results to the PR. If the tested code is not from the PR, then I can not see why to post a result to it.

You can see here that we have the SHA of the pull request in question, we use it in this custom action I made.
Does that sound clearer to you, @zmiklank? And to close that, I agree that my request sounds more appealing to Convert2RHEL/Leapp and may not be the case to everyone else. If you still think that my use case here could be completely different, then I think I will need to work out a different way then.

@r0x0d Thank you for explanations!
I think I understand your use case at some level now. I rethought your idea (to add a SHA input) once again and IMO it would not break anything. If @phracek agrees, I can implement that (hopefully, in a timely manner)
@phracek, do you agree?

Go ahead, I have nothing against it.

Thanks everyone!

@r0x0d, @fernflower
testing-farm-as-a-github-action v1.2.12 has just been released[1], containing changes that should fix this issue.
Please check it out, if the solution works for you.
[1] https://github.com/sclorg/testing-farm-as-github-action/releases/tag/v1.2.12

@zmiklank it seems that the new version has a problem :( https://github.com/r0x0d/convert2rhel/runs/8251179691?check_suite_focus=true#step:2:106

Seems to relate to #49 as that's the other thing added. Matches the error too

I have reverted the commit that could be causing the error and released new version of testing-farm-as-a-github-action until we fix that. Sorry for the inconvenience.
Thank you for testing it!

Seems to be working as expected now, @zmiklank! Thanks for your work.


feature: VCLTJV-3-add-git-action-workflow

Migrate to github actions
For this project we do not build a docker image, we upload it to nexus and work on SNAPSHOTs for development.

Hello anurag4dsb,
My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.
Status report is not available.

Incorrect fix version
The Fix Version/s in issue VCLTJV-3 contains:

None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

1.0.0

Please check the Fix Version/s of VCLTJV-3, or the target
branch of this pull request.

Waiting for approval
The following approvals are needed before I can proceed with the merge:

the author

2 peers

ping

/approve

Waiting for approval
The following approvals are needed before I can proceed with the merge:

the author

2 peers

The following options are set: approve

/help

Waiting for approval
The following approvals are needed before I can proceed with the merge:

the author

2 peers

ping

/approve

Waiting for approval
The following approvals are needed before I can proceed with the merge:

the author

2 peers

The following options are set: approve

ping

In the queue
The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.
The changeset will be merged in:

:heavy_check_mark: development/1.0

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.
IMPORTANT
Please do not attempt to modify this pull request.

Any commit you add on the source branch will trigger a new cycle after the
current queue is merged.
Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.
The following options are set: approve

I have successfully merged the changeset of this pull request
into targetted development branches:

:heavy_check_mark: development/1.0

Please check the status of the associated issue VCLTJV-3.
Goodbye anurag4dsb.


500 Error (NameError) name 'error_occurred' is not defined

Using telnet I send a EHLO, I sent a MAIL FROM and RCPT TO... I then send DATA and enter a data line... but as soon as I hit enter it throws this error inside of telnet:
500 Error (NameError) name 'error_occurred' is not defined
The python console shows the following:
SMTP session exception
Traceback (most recent call last):
File "C:\Program Files\Python3.6\python-3.6.1.amd64\aiosmtpd\smtp.py", line 281, in _handle_client
await method(arg)
File "C:\Program Files\Python3.6\python-3.6.1.amd64\aiosmtpd\smtp.py", line 657, in smtp_DATA
status = await self._call_handler_hook('DATA')
File "C:\Program Files\Python3.6\python-3.6.1.amd64\aiosmtpd\smtp.py", line 118, in _call_handler_hook
status = await hook(self, self.session, self.envelope, *args)
File "smtprelay.py", line 13, in handle_DATA
if error_occurred:
NameError: name 'error_occurred' is not defined
The code that is currently being run was pulled straight from the documenation:
http://aiosmtpd.readthedocs.io/en/latest/aiosmtpd/docs/migrating.html
Any idea what is going on here?

"error_occurred" is a meta-variable -- you're supposed to change that to checking for whatever error condition was handled in your smtpd application. If you don't anticipate any errors, remove the "if error_occurred:" statement.

Wow, do not program when sleep deprived kids...  I saw the trace, but my brain didn't seem to want to work.  I kept looking in smtp.py looking for where error_occurred was used.  I never even saw the "File "smtprelay.py", line 13, in handle_DATA" .  It also didn't help that I didn't read the sample code, and I just assumed it was working code.
Thanks for the reply, and sorry to waste your time...


GigaGrid not supported in React v15

Grid throws some console errors and strange behaviors are observed.  Will take a look at a fix

Was work on this done already?

I haven't done anything with this issue yet

On Jun 4, 2016, at 12:28 PM, Erfang Chen<EMAIL_ADDRESS>wrote:
Was work on this done already?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


dh_cms_set_peerkey: Pad the public key to p size

There was an intermittent failure in the CMS DH test sometimes.
This was caused by not fully padding the public key to the p parameter size.

ping @openssl/committers for review

This pull request is ready to merge

Merged to master. Thank you for the review.


BadMethodCallException with message 'This cache store does not support tagging.'

Hi there,
First of all, I have to say your package is amazing - it looks like it will save me a good amount of time building my project :).
To the main problem at hand... I am using php artisan tinker to create a Role, as demonstrated in the initial install instructions. When I attempt to save this new role, I get the BadMethodCallException message in the shell; however, when I echo the new role to the shell, I see a perfectly-formed role.
I have attached a screenshot of what I did, with the error message. I am also using Laravel 5.3.16 in this particular project of mine.

You have to use your CACHE_DRIVER as array or memcached.
==
I have created same package for running 5.3
https://github.com/klaravel/ntrust

How do you do that PLease show me

it is not working ohh

@dagogoilamini  What's not working?

duplicate #749

I get this error message even though my cache.php says 'default' => env('CACHE_DRIVER', 'memcached'), and even if I temporarily change it to 'default' => env('CACHE_DRIVER', 'array'),.


⚠ Bofrost.fr has degraded performance

In b48af1e, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1404 ms

Resolved: Bofrost.fr performance has improved in d987735 after 9 minutes.


Readd Disable prefetch for the CIS queue.

Reverts mozilla/mozillians#2370
Now that the release is out we can test this properly without interfering with the rest of the Celery pipeline

Coverage remained the same at 89.606% when pulling 8805692f3bf30f0c9677827064bfcd251711b251 on revert-2370-revert-2342-celery-prefetch into 1a5c59c0d66c2cc2a2fb6109544198153dc85cc3 on master.


Testimonial Darkmode notworking+cant see left right navigation icon in light mode+not responsive #1078

Description
Fixed Testimonial dark mode ui made responsive and light mode fixed
Fixes #1078
Replace issue_no with the issue number which is fixed in this PR
Screenshots

Checklist

[ Y] Tests have been added or updated to cover the changes
[Y ] Documentation has been updated to reflect the changes
[Y ] Code follows the established coding style guidelines
[ Y] All tests are passing

hey @thestarsahil please review it whenever possible


Fix memory leak in SQL instrumentation

The additional member variables _cursor and _connection were causing circular references, prventing cursor and connection from being garbage collected.  Switched to use wrapped property already available from the base class wrapt.ObjectProxy.

lgtm


Update support notice UI for USDT payment

Tasks

[ ] Update support notice for adding USDT payment info

References

Product doc
Design

Seems nothing has to be changed to support USDT donation.


Refactor integration tests

Replace use of .sl-checkbox per https://github.com/softlayer/ember-style-guide/issues/29, as well as utilize the same referenced selector in other references as appropriate.

@notmessenger please assign this to me.


Create docker image for snowflake integration

@glicht can you have a look?

It is failing as there is a dependency on cffi and it fails to compile it:

Looks like there is need to install libffi-dev. Will add this soon...

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/snowflake:<IP_ADDRESS>
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/snowflake/tags
Get started by pulling the image:
docker pull devdemisto/snowflake:<IP_ADDRESS>

Docker Metadata

Image ID: sha256:444be31b5dc075c8af154435b1c61db23330ef374a57cdd18e0f710605ab8461
Created: 2019-03-27T17:42:28.932019551Z
Arch: linux/amd64
Command: ["python3"]
Environment:

PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG=C.UTF-8
GPG_KEY=0D96DF4D4110E5C43FBFB17F2D347EA6AA65421D
PYTHON_VERSION=3.7.2
PYTHON_PIP_VERSION=19.0.3

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:9140779e495240bff0fdcf6c34234a80276806f3
org.opencontainers.image.version:<IP_ADDRESS>

Docker Image Ready - Production
Docker automatic build at CircleCI has deployed your docker image: demisto/snowflake:<IP_ADDRESS>
It is available now on docker hub at: https://hub.docker.com/r/demisto/snowflake/tags
Get started by pulling the image:
docker pull demisto/snowflake:<IP_ADDRESS>

Docker Metadata

Image ID: sha256:4c6b79b4c26b5c98295732359ae83524f880dbdf4ec3b5fb7690a561c66df25f
Created: 2019-03-28T08:30:38.232072515Z
Arch: linux/amd64
Command: ["python3"]
Environment:

PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG=C.UTF-8
GPG_KEY=0D96DF4D4110E5C43FBFB17F2D347EA6AA65421D
PYTHON_VERSION=3.7.2
PYTHON_PIP_VERSION=19.0.3

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:a8bd1a823336b75f47a44c23653b4c67c996c8ba
org.opencontainers.image.version:<IP_ADDRESS>


Add workspace services to e2e

What is being addressed
Most workspace services aren't tested in E2Es.
How is this addressed

Add workspace services deployment tests
Create a new pytest marker for workspace services
Remove certs shared service from tests as it doesn't play nice with the firewall (it doesn't use the pipeline)
MLFlow workspace service updates
Gitea workspace template
[unrelated temp fix] disable bundle-check-params in CI as porter is working on a fix

/test-force-approve
was tested a bunch of times via branch workflow