Official browser support

Right now we recommend Chrome and Firefox on /news/support, but we transpile for more than that: https://github.com/freeCodeCamp/freeCodeCamp/blob/dd7fba4558f5a0c4b2dc35ebd919c22921c0b0df/client/.babelrc#L12
Should we officially support, say, Chrome, Firefox, Edge, Safari and Opera?  If we do, we can tailor our browserlist to that and also our Cypress tests.
Whatever we decide to support, I think we should make our tooling reflect that.

Except Firefox almost all browsers are Chromium under the hood so supporting multiple browsers should be a big problem. The only browser I want to drop from the list is Safari.
That lefts us with -

Chrome
Firefox
Edge (The new Chromium one)
Opera

My rationale for including Safari was just that it's pretty popular. If we can support it, that would be good.  Could you expand a bit on why you'd prefer to drop it?

It would appear that, according to WikiPedia, Safari is still fairly popular:

I'm not sure if we can view browser statistics for our /learn platform specifically, but I'd be concerned about dropping support for an OS default browser.

My main complain/concerns with Safari was -

Many weird CSS issues (especially since we are going to be using CSS Flexbox and Grid moving forward)
Can't test e2e due to Cypress not supporting it (it's in the road map though :thinking: )

For the above mentioned reasons, I think supporting Safari would be a painful experience since we'll have to not only find weird fixes for weird Safari bugs but also we can't test them with Cypress meaning either manually testing it or shipping broken feature to prod.
(Sorry for the very late reply. This somehow slipped under my radar.)

Thanks Twaha, that makes sense.
I've taken a look at our analytics and they're similar to the ones Nicholas posted, so ignoring Safari would be ignoring quite a lot of users.  That said, it seems sensible not to claim we support it when it's likely to be buggy (for the reasons you outlined).
How about this: transpile for Chrome, Safari, Firefox, Edge and Opera i.e. the top 5 (in that order)? Then we can update the support page as and when we're confident a browser works well enough.  At the very least we should wait until we Cypress test a particular browser.
I'll leave this open for a bit in case people want to weigh in.
cc @raisedadead

Please don’t drop support for Safari. It’s the default browser on macOS, iOS and iPadOS. And yes, people do want to learn to code using those devices!

@ojeytonwilliams - I am in agreement with your original proposal in the OP, if still interested please proceed or consider closing this stale.

We need to continue to support Safari the best we can, so nothing needs to change here.


Treasure maps never appear

For some reason, I have never been able to find a buried treasure map after looting dozens of shipwrecks. There are some other mods but I'm 90% sure it is this mod that causes it.

Lootr does not alter loot tables in any way, as noted on the CurseForge description page which outlines the most frequently asked questions, so it is most likely not responsible for this.
You can test this by creating a single-player creative world of your pack with Lootr disabled, and then open containers in shipwrecks to see if you can find maps.


feat: support nroots greater than 1

Summary
This adds support for nroots > 1 to the PySCFGroundStateSolver.
Technically, this would make it an ExcitedStatesSolver, but I do not think that differentiating this interface adds any value and is therefore unnecessary complexity.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

9 of 9 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.7%) to 77.922%

Totals

Change from base Build<PHONE_NUMBER>:
0.7%

Covered Lines:
120

Relevant Lines:
154

💛  - Coveralls


Please add offline installation tutorial

Hi bfontaine,
term2048 is an amazing app, I like it.
But someone may want to install it offline instead of pip installing.
I have figured out term2048 can be installed offline by following steps:

download term2048 repo
make deps
make check
sudo python setup.py install

Many beginners don't know the fourth step as it's not mentioned in current readme. It will be of great help to many people if you add the fourth step in your readme.
Thank you.

Hi @01joy, what do you mean by “offline”? You still have to download the repo and make deps will use pip to install dependencies.

Hi @bfontaine , but someone may don't know they have to sudo python setup.py install.

I added it in a dedicated section: https://github.com/bfontaine/term2048#install-from-source

It's very nice of you to add install from source, thank you.


--xlsx option is generating csv files and --csv excel file

When using the --xlsx option only CSV files are generated and when using the --csv one only an excel file is generated.
Additionally, the command help says:
  --xlsx               Path to result xlsx file
  --csv                Path to directory for output csv files

But when trying to set a path, eg spoonbill --csv data file.json I get an error:
Error: Got unexpected extra argument

may be closed by #63

Checked --csv, --xlsx - PASS


USER, LDAP Person extension by useful fields + cloud profile added to support Azure AD

This issue is about adding a few useful fields to LDAP user, User object and adding a way how to map Azure ID to it.
USER:

bad_password_attempts
bad_password_time
created_time
expiration_time
last_login_time
lock_out_time
logon_count
logon_hours
modified_time,
password_last_set_time
password_never_expire
is_privileged,
status
status_id

LDAP Person:

allowed_to_act_on_behalf_of_other_identity
allowed_to_delegate_to
department
display_name
domain
employee_type
employee_type_id
expiration_time
force_change_password_next_sign_in
force_change_password_next_sign_in_with_mfa
parent_dn
proxy_addresses
last_known_parent
member_of"
member_of_guid"
member_of_transitive"
object_category
object_class
object_guid
primary_group_id
resultant_pso
is_service_account
unique_name
usn_changed
usn_created
user_principal_name
user_account_control
user_password_expiry_computed_time
visibility

Active directory profile:

is_privileged
classification
consistency_guid
creator_sid
email_addr"
forest
is_deleted
object_sid
on_premises_distinguished_name
on_premises_domain_name
on_premises_immutable_id
on_premises_last_sync_time
on_premises_sam_account_name
on_premises_sync_enabled
on_premises_user_principal_name
is_recycled
nt_security_descriptor
is_security_group
sam_account_type
service_principal_name
sam_account_name
sid_history
token_groups

Could you add some samples of raw data that you are seeking to normalize to OCSF so we can better understand your use case?


store setup - token balances and fiat prices

Overview

should include a config-based way to display different fiat currencies in the UI

Out of scope

Oracle implementation

Isn't it already solved in the UserStore from the new lib?
This code was made by @EJSG
https://github.com/telosnetwork/telos-wallet/blob/develop/src/antelope/stores/user.ts#L56-L59

Good point, we can close this


Understanding Probability Distributions and their Simulations in R

Proposed title of the article
Understanding Probability Distributions and their Simulations in R
Proposed article introduction
When working with distribution, we typically want to know one of the four things below.

The density pdf of a particular value.
The distribution CDF.
The quantile value corresponding to a particular probability.
A random draw of values from a particular distribution.
R has functions for obtaining density, distribution, quartile, and a random value.

The general R naming is given as:

pname: This calculates the density at input X
pname: This calculates the cumulative probability density(CDF) at input X
qname: This calculates quartile at an input X
rname: This generates a random draw from a particular distribution

where the 'name' in all the four cases above represents the name of the given distribution.
Random value generation is a common activity in machine learning especially in Bayesian statistics where the posterior distribution can be intractable and therefore difficult to estimate parameters of interest from them. In such cases, we draw samples randomly from them using methods such as Monte Carlo simulation which is then used to estimate the population parameters. For the learner to be able to advance to such a level, first they should know the basics of how we draw samples from a certain distribution.
In this article, we will cover both the continuous and discrete probability distributions and how we simulate them as well as drawing samples from such simulated distributions.
Key takeaways

What's the probability distribution
What is the continuous and discrete probability distributions
Under the continuous probability distributions, the learner will know:

Uniform distribution; its pdf and how to simulate its distribution
Normal distribution; its pdf and how we simulate its distribution. Since the normal distribution is highly applicable in the real world, we shall have some application problems which we will learn how we can solve them using R instead of solving by hand.
Chi-Square distribution; how to simulate and solve its problems using R
Student-distribution; how to simulate and solve its problems using R
Exponential distribution; how to simulate and solve its problems using R

Under the discrete probability distribution the learner will know:

Binomial distribution: Here we will solve some practical problems using R code.
Poisson distributions: We will learn how to solve probability problems of Poisson distribution using R.

How to draw samples from the simulated distributions

Article quality
This article aims to make the learner able to solve any probability problem using R software instead of doing so by hand as in practice some problems might be highly challenging to address by hand. So, it will cover the topic in-depth and ensure clarity of the content so that the learner can grasp the content very easily.
References
N/A

Sounds like a helpful topic - let's please be sure it adds value beyond what is in any official docs and/or what is covered in other blog sites. (the articles should go beyond a basic explanation - and it is always best to reference any EngEd article and build upon it). @BejaminNaibei
Please be attentive to grammar/readability and make sure that you put your article through a thorough editing review prior to submitting it for final approval. (There are some great free tools that we reference in EngEd resources.)
ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.
Please be sure to double-check that it does not overlap with any existing EngEd articles, articles on other blog sites, or any incoming EngEd topic suggestions (if you haven't already) to avoid any potential article closure, please reference any relevant EngEd articles in yours. - Approved

Just and FYI I will be closing this topic form just to help clear up the queue where possible - can be REOPENED at anytime when ready to link a PR. 👍

Closed #6652 via 7440


ci: ignore execa from renovate updates due exclusive esm support

<EMAIL_ADDRESS>is exclusively ESM module, we gonna ignore it from renovate maintenance until we will have better support for ESM modules

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@next-major dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


lib/py: Automatically decode immutable struct fields as immutables.

Currently, Thrift requires exhaustive immutable annotations for all
container fields of an immutable struct to work correctly:
struct ImmutableParent {
  1: list<string> (python.immutable="") str_list,
  2: set<list<string> (python.immutable="")> (python.immutable="") set_of_lists,
  3: map<string,list<string> (python.immutable="")> (python.immutable="")map_of_lists,
} (
  python.immutable = "",
)

This is bad for several reasons:
1. Bad ergonomics, as definitions quickly get polluted by the
   annotations, and it is easy to miss.

2. Danger of missed annotation causing the decoder to fail
   with TypeError('unhashable type').

3. Lack of proper support for nested annotations in third-party
   compilers like Scrooge.

This diff changes the handling of immutable structs in the Python
decoder to automatically assume that all container fields of
immutable structs are also immutable.  This allows to side-step all
problems mentioned above.
This commit makes no attempt to validate nesting of mutable structs
within immutable structs, as that is a separate concern.

Do these changes break the ProtocolBase interface contract?

No, lib/py/src/ext/protocol.h is internal to the binary accelerator, as far as I can tell. TProtocol.TProtocolBase hasn't been touched.

There is a caveat I forgot to mention: this only works for py:dynamic, as the other modes do not make the generated class inherit from TFrozenBase, and there is, unfortunately, no other indication that the class is immutable (other that trying setattr on it).


Feat/adp 2218 web extension wallet manager

Context
Create a wallet manager that keeps one wallet active at any time.
It can be used to get an ObservableWallet object in the UI scripts. The observable properties of the wallet object can be subscribed to even before any wallet is created.
Wallet manager can:

Activate a new wallet. The wallet object starts emitting values from this active wallet.
Deactivate a wallet. The wallet object observables stop emitting values but do not complete.
Activate a previously deactivated wallet. The previously associated store is restored.
Clear cached store for wallets no longer active.

7e60722 - Use observableWalletName instead of walletName to make it clear we are expecting a user wallet name/identifier (e.g. My Testnet wallet)
5440c42 - Wallet manager channel and its internal wallet channel are now derived from the walletName


Disable FAIL_ON_UNKNOWN_PROPERTIES for forward compatibility

This makes sure that any future additions to the XML by FTL does not break existing builds of flank and is more permissive in structure about deserialization of unknown properties.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Naren:x: narenkmanoharanNaren seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #599 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #599      +/-   ##
============================================
+ Coverage      76.7%   76.75%   +0.05%
  Complexity      610      610
============================================
  Files            81       81
  Lines          2262     2263       +1
  Branches        324      324
============================================
+ Hits           1735     1737       +2
  Misses          308      308
+ Partials        219      218       -1

Thanks for the pull request! Please add a JUnit test that verifies no exception is thrown when an unknown XML property is present in the parsed XML.
Something like this, note the addition of random="prop".
 val unknownXml= """
<?xml version='1.0' encoding='UTF-8' ?>
<testsuites>
  <testsuite random="prop" name="EarlGreyExampleSwiftTests" tests="4" failures="1" errors="0" skipped="0" time="51.773" hostname="localhost">
    <testcase name="a()" classname="a" time="1.0" random="prop"/>
  </testsuite>
</testsuites>
        """.trimIndent()

val parsed= parseAllSuitesXml(unknownXml).xmlToString()

assertThat(parsed).isEqualTo(unknownXml)

Merged. Thanks for contributing!

Release :) ?

I'm working on it. The Bitrise GitHub release step is failing.
FTL finished the rollback so you shouldn't be broken anymore.

yep I see FTL is passing. Thanks !

It just started happening again for us? 🤔

It just started happening again for us?

The Firebase team had a mistake in the rollout. It should be resolved now.


Rename MeasurementMetadata

The MeasurementMetadata object tracks information that is relevant to a particular element of evidence throughout its lifecycle. It is not specific to a Measurement, or it applies to more than just Measurements. Accordingly, we should update the name to better indicate what it does.

This is addressed in #135

Resolved by #146.


Fix some minor things in ssl_test and friends.

Even if #15415 fails, these changes are useful.

Since #15415 was approved and will presumably be merged, and since that contains this, closing this.


Feedback on Project Manager Overview.md

An Overview of the Project Manager is here:
https://github.com/brondani/devtools/blob/mvp-prototype/tools/projmgr/docs/Overview.md
For now, please post your feedback using this issue.

Here are a few questions and feedbacks concerning this proposal.
1- is csolution a workspace-like environment where users can list all the projects they are working with or is it meant to support a specific application and offers specific added value for serving this application ?
In previous proposals we were considering .ctarget as what we called an "application project", that would provide the full picture of all the projects required for building a possibly complex application.
With current proposal, it looks like a user may use csolution to list completely different "applications" like "secure lock on target A", then "connected fan on target B" maybe because they share a few components together. Is that part of what we want to support ?
2- Clayer and Cproject allow to projects or sub-projects
If the csolution would apply to one target type at a time, clayer and cproject would anyway allow sharing common parts between 2 (or more) projects. Each csolution project could also include the target specific part without impacting the other project.
3- supporting different targets in csolution  raises many questions :

as depicted in example diagram, the various projects may contain very different SW layers and fitting all of them inside a common structure may bring more noise (exclude / include management) than just sharing sub-projects or layers between 2 different projects https://github.com/brondani/devtools/blob/mvp-prototype/tools/projmgr/docs/images/TargetBuild-Types.png
the main diagram explains that ctarget.yml (BTW: typo, name wasn't updated) should include azone.info. I guess this can have added value as the csolution can provide a consolidated view of the memory mapping and resource assignments (secure / non secure memory map, peripherals assignments, bootloader flash area vs. application flash area, etc....) but how will that work when  multiple HW are supported ?
same for compiler options, what if virtual platform requires different options than real mcu, do we need also  include and exclude mecanisms for compiler options ? same for defines ...

4- worskspace with multiple csolution projects ?
if you get a workspace with several csolution application projects, your workspace can provide you a list of solutions and target-types you support in your workspace, and that could possibly offer the user the possibility to switch between different target-types for the related solution, e.g. switch between iot-product~virtual.csolution.yml and iot-product~production-HW.yml .

The csolution.yml file is not related to a workspace.  We defined it right now as: A solution is the software view of the complete system. It combines projects that can be generated independently and therefore manages related projects.

You are right, it might be sufficient to have csolution to support just one target at a time.  However, we got feedback that this might be not provide the flexibility required. If we need at the end the 'target-type' approach or not is something that should be evaluated (with several test projects). It is possible to exchange layers based on target/build type selections - so yes the concept you describe is there.

You are raising a valid risk here, and this approach will need clear guidance to users what makes sense and what should be avoided. And clearly we will need to do work on the rzone assignment - this is ahead of us and I plan to get the concept done before XMAS.  There are already provisions for different compiler options (specific to a target), so that problem is already addressed. I can provide an example if needed.

As said, we should explore the best way to work with build/target-types.  Let's not come to early to conclusions that it is too complex.  I believe managing projects with build/target-types simplifies, but I might be wrong.  We should get examples before we judge.  It is always possible to decide that target-types do not get exposed to the users.

Hi,
as you may expect I agree with LMESTM's point of view.
One more element I'd like to highlight again is the fact that I am not convinced bu the "solution" wording : see my points here

Fred,
thanks for your good contribution. I like your user stories and agree we should evaluate it. As "full stack" example I believe we can use a project like this: https://github.com/arm-software/ATS-Keyword.  And we could map it to:

Nucleo board viewed as "production hardware"
Disco board (with similar device, but a superset with different pin mapping) viewed as "test board"
Virtual Hardware (simulation) for testing.

I did not like "solution" initially. But Visual Studio introduced it ~20 years ago and many programmers know already what it is. We can go around our virtual "Open-CMSIS table" to see if there are better ideas.  IMHO a single word works better, so "product" or "system" might be feasible too.  (Multi-project Workspace - the MDK term - is clumsy).  In context of all the complexity, I feel this is a detail.
Reinhard
"azone/rzone" needs more work - your picture with the different "context/resource" boxes is good.  We should find a way that users can understand and manage such systems.

Well, to me as you said solution has a strong "track record" in the dev community and I immediately associate it to an sln file so Visual Studio solution.
I would prefer something showing more clearly we are dealing with embedded SW for a target HW. But I agree it is tricky and probably not critical.

thanks for your good contribution. I like your user stories and agree we should evaluate it. As "full stack" example I believe we can use a project like this: https://github.com/arm-software/ATS-Keyword. And we could map it to:

Nucleo board viewed as "production hardware"
Disco board (with similar device, but a superset with different pin mapping) viewed as "test board"
Virtual Hardware (simulation) for testing.

@ReinhardKeil  In your above proposal, all the boards / HW types seem to refer to the same device. in the user stories suggested by @fred-r there are different devices, typically one is trust-zone enabled, the other one is not.

Laurent, when looking at the Nucleo/Disco STM32L5 offering the devices on the boards are different and also the pinout differs.  The idea is to mimic production hardware (on a device with less pins/memory). If the example ATS-Keyword is suitable or not needs to be evaluated.

Yes I understand that it could make more sense for HW types that are closely related one to the other, but if you open this door, do you plan to restrict users to select only closely related HW ? how can we ensure this ?

@ReinhardKeil  It sounds like the discussion above is trying to determine what to call the 'application' now that managing multiple execution contexts, and processors on a single board is desired?
As someone who has done a decent amount of schematic & layout but specializes in firmware & IoT;

I would want to be able to describe the hardware unit (PCB) and any logic specific to bringing up or managing that hardware to exist within a BSP pack.
That pack would contain tests and a reference to a sample external to said pack.
I would not want any samples for that board in the pack because that breaks my mental model for the "full stack".
That BSP should be 'optionally' dependent packs that add processor support and drivers for other IC's on board.

I think I would have application level 'projects' for each processor, and possibly a project per zone needed by my application on a particular MCU.
I could live with the top level collection of applications/projects being called a "Solution" or "System".

Also. Do not forget about Rust. It is quickly gaining momentum. New engineers feel no sense of attachment to C and will drop it like a rock.
Please 🥺🙏 consider looking at how Cargo and crates can be either used for inspiration or used directly to manage packs. Extend it if you have to.

The order of processing of the project files induces the overlay order of the elements that can be present at various levels like the  general properties keywords.  In the proposal, the .csettings.yml is processed first (even before the .csolutions.yml) but when I look at the list of the general properties keywords I think it is sufficient to apply them at a lower level  .project.yml except  compiler: and defines: (for symbol and path settings) that sounds general and could correspond to a "workspace" like environment (concept introduced by LMESTM in the first point of his first post of this thread https://github.com/Open-CMSIS-Pack/Open-CMSIS-Pack/issues/43#issuecomment-965463956 ) where users can list all the projects they are working with.

Also. Do not forget about Rust. It is quickly gaining momentum. New engineers feel no sense of attachment to C and will drop it like a rock.

@0Grit : I do not see an issue in what is proposed here to handle a project from packs containing sw components developped in C language or in Rust. Do you ?

Build system is abstracted from packaging? If so I trust your assertion.
I'm strapped for time and am unable to do much more than skimming of the materials. Just wanted to make sure these things are at least mentioned in the conversation. I've seen people like @ilg-ul who have a wealth of knowledge and work put into projects like this, get ignored in the past.

Well, I would think that:

the proposal is based on CMSIS-Pack components, so we can have a component providing RUST code
when it comes to the build chain, the spec lets it open I guess. Today it is proposing GCC, IAR and AC6 as a compiler but I assume we may support a toolchain with bot C and RUST support ?
or maybe more realistic would be to mix C project and RUST projects compiled with their own toolchain each ?

I assume the major point you highlight is how to use both cargo and CMSIS packs ?

After embracing the CMSIS Packs idea and trying to use them  for my projects (long time ago), I finally realised that their design has different goals, that do not match my criteria, especially in providing layer separation and reduced complexity.
Thus I designed xPacks, which are a more generic version of the highly successful, industry standard, npm packs.
In terms of the first criteria, layer separation, source xPacks are completely neutral to build processes, languages, platforms, etc.
In practical terms, source xPacks are collections of files with static dependencies to other xPacks, the same as npm packs are nodejs modules with dependencies of other packages.
Satisfying dependencies is a separate step that is executed before the build, to bring in all dependent packages, sources or binaries.
As for the second criteria, reduced complexity, CMSIS Packs favour very large packages (I saw some weighting hundreds of MB), with many, many source files, grouped in lots of components, each with its own version.
On the opposite end, xPacks (and npm packs), favour many small packages, each package having its own version, which applies to all files in the package.
Another major difference is that the main CMSIS Packs repository is centralised and not automated (or at least it was not when I used it, it required someone to accept the packages, and to update the index, which is, most of the time, outdated with vendor packages).
xPacks, being in essence npm packs, can be stored on any npm compatible server, like npmjs.com, GitHub, etc.
My 2 cents...

"As for the second criteria, reduced complexity, CMSIS Packs favour very large packages (I saw some weighting hundreds of MB),with many, many source files, grouped in lots of components, each with its own version."
==> to me this is the way CMSIS packs have been used so far.
The spec does not force you to do so.
I agree that it would be a much better practice to design smaller packs not mixing very different things.
The pack is only the way to convey the CMSIS components : this is the important point, designing consistent components.

I highly recommend looking at @ilg-ul's x-pack project. I've used it and it's a great experience. He has packs to install toolchains, cmsis, etc. A lot of it sitting on top of NPM's infrastructure too.
The only thing preventing it from widespread usage is that he is basically the only person working on the project.
You would think he had a team considering how extensive the project is.
It would bring a tear to my eye to see some of his work be used by open-cmsis-packs somehow. Even if only by inspiration; though just using xpacks by itself and adapting the open-cmsis-packs spec to it would save everybody some time.
Not sure about how or if xpacks handles the "zones" concept though.

If allowed, multi-component packages may present additional challenges. Imagine you have multiple versions of a package which defines multiple components, each with its own version, all different in each package.
For whatever reason, a project may decide that it needs one component from one package version and another component from another package version. I did not check the recent specs, so I apologise if this is nonsense, but can the proposed package manager handle cases like this?

Not sure about how or if xPacks handles the "zones" concept though.

I don't know what the zones are, but I did a lot of thinking and experimenting with packages, and my current understanding of the subject is that any design that requires the packages to be identified by anything more than a (scoped) name and a semver, is a design too complicated.
As for what a package is, according to the npm documentation, "a package is any of the following":

A folder containing a package.json file.
A gzipped tarball containing (1).
A URL that resolves to (2).
A <name>@<version> that is published on the registry with (3).
A <name>@<tag> that points to (4).
A <name> that has a latest tag satisfying (5).
A git url that, when cloned, results in (1).

I personally could not find a more generic definition.

@ilg-ul see the discussion earlier up. https://github.com/Open-CMSIS-Pack/Open-CMSIS-Pack/issues/43#issuecomment-966479145

Yes, I saw it, but for me such a project is too complicated to be a single package.
Small simple packages are also much easier to test, and in environments like GitHub, you can run the unit tests automatically on push.

The example provided above (https://github.com/Open-CMSIS-Pack/Open-CMSIS-Pack/issues/43#issuecomment-966479145)  and referenced by @0Grit  is clearly not a single package.
It is an application project made of several software projects.
Each software project is the composition of several CMSIS components (via several CMSIS packs).
I agree there is complexity but it only reflects the complexity of the systems we are dealing with.
I think we should not mix all topics:

I understand that you challenge the CMSIS-pack technology => to me x-pack covers this based on what you explained, even if I think that a "proper" usage of CMSIS-Pack should do the job...to be discussed by @jkrech and @ReinhardKeil
There is the project management aspect => here nobody said an application project should be a single pack

So I would recommend focusing this discussion thread on subject 2 and maybe @jkrech can redirect the 1st topic to the appropriate issue ?

We are indeed deviating from the subject of this thread but these are interesting discussions for which we can open new issues thread or redirect to existing relevant ones.
During early discussion to set-up this open-CMSIS initiative, we have agreed to start from CMSIS-Pack (It has a certain footprint in the embedded with many MCU vendors publishing CMSIS packs) and see how to improve the spec and push an open reference implementation;   @ilg-ul I invite you to look at the others issues - in particular #10 and #11 - to get an overview of the improvements we are looking for. It is great if there are good things pointing in the same directions from your xPack work that we can pick-up. It can helpful if you could have a look to #10 and #11 and flag to us the relevant elements of xPack.
About too large/complex (CMSIS) pack I fully agree with @ilg-ul concern and the feedback from @fred-r. How to favor (enforce ?) design practices to end up with "small" packs is  a very good topic and will deserve a dedicated issue thread. We can provide examples/patterns and/or do something with a Pack checker but where to set the limit is a tricky question.

if you could have a look to #10 and #11 and flag to us the relevant elements of xPack.

I took a quick look, but as long as you do not have a clearly layered design, and throw everything (dependencies, build, components, configuration, etc) into the same bucket, it is hard to flag any relevant differences.

I have now created issue #47 and hopefully captured the comments correctly there. I am hiding the comments in this issue as they are off-topic, sorry in case the initial issue title was misleading into this direction.

Fred,
thanks for your good contribution. I like your user stories and agree we should evaluate it. As "full stack" example I believe we can use a project like this: https://github.com/arm-software/ATS-Keyword. And we could map it to:

Nucleo board viewed as "production hardware"
Disco board (with similar device, but a superset with different pin mapping) viewed as "test board"
Virtual Hardware (simulation) for testing.

@ReinhardKeil : I am not sure ATS is the best choice for a first shot.
It requires an AWS account and, it deals with Audio as well as ML ?
Besides, I am not surea bout the adherence with the HW : I do not see many peripherals into the project.
Why not getting started with a CMSIS-Zone project ?
https://github.com/ARM-software/CMSIS-Zone/tree/main/Examples/STM32L5
I would like to see how to deal with this application:

when we have the STM32L552E-EVAL
when we want the same application project on STM32L476RG-NUCLEO : the secure software being implemented with the Firewall instead of TrustZone
on a simulator : how to deal with the virtualization ?
This would be user-story 4.

For user-story 1 and user-story 2, I would recommend this project:
https://www.st.com/en/embedded-software/x-cube-sbsfu.html
This provides a bootloader and a user-application.
I would like to see how we can handle just a few situations:

Supporting Nucleo-L476RG and Nucleo-L432KC: one has a user-button, the other one not
Supporting DISCO-L496 which supports 2 crypto libraries
Supporting STM32F769I-Discovery which is another series, has no Firewall and supports 2 crypto libraries too
Supporting STM32H7B3I-DK which is yet another series and has external FLASH
Why not a virtual device ?

For user-story 5, X-CUBE-SBSFU can be nice two as it has a dual core flavor.
For user-story 6, probably we could consider the mbedTLS library ?

ects' for each processor, and possibly a project per zone needed by my application on a particular MCU.

@0Grit : I agree that the board pack should not contain examples.
Probably a discussion can be initiated about what a good pack is as suggested by @iomint .

I think I would have application level 'projects' for each processor, and possibly a project per zone needed by my application > on a particular MCU.

My intention here is to promote one single application project per board.
This allows dealing with shared resources between components of the board.
Typically, if you have one SoC with multiple cores then we use execution contexts to associate each SW project to an HW execution unit.
If you split it in several application projects (one per core) then you are in trouble to handle shared resources in my opinion and also to do the partitioning of the system.
That's my opinion and I'll be happy to get your view on this.

I think the only alternative would be to have some new protocol and software developed to manage and share resources in a distributed fashion, without a central entity to manage the resource. That sounds like a nightmare so I think I'm aligned with your intent.
Your first sentence throws me off though. A board can have multiple use cases. Someone who buys an off the shelf solution will develop a different "whole board application" than another person who buys the same board for another purpose.
The board support package is a dependency of the application project and enables it to function. If I ever wanted to port the "whole board application" to another board I should be able to as long as that other boards BSP provides the execution contexts and resources needed by my application.

The application project contains all the SW projects running on the target board (making the application).
Now, these SW projects have:

applicative layers => board-agnistic
system software : RTOS, board support package (including MCU drivers)

Then yes when you move to another board you can re-use your applicative layer (the CMSIS component).
But you need a brand new project as the system software will be different at least for the BSP part (not the same MCU drivers typically, not the same pins, not the same memories).
That's why I am not convinced one application project can support multiple HW targets easily but this is what we are going to experiment.
But the intention with the "application project" is to have a cradle allowing you to handle your application (both HW + SW).

What "I think I would want" are build configurations for each supported board within one top-level project.
Agree that this needs experimentation.

What "I think I would want" are build configurations for each supported board within one top-level project.
Agree that this needs experimentation.

Ok, you are aligned with the proposal from our ARM colleagues.
Let's see if this is feasible without ending up with a nuclear plant system... :-)

What would help me also is a legend to understand the arrows in this diagram:

I mean:

the blue arrows going from top to bottom probably mean : "references..."
the blue arrows going from left to right have two meaning I think

"is an input of"
"generates ..."

Also the color code for the boxes is not obvious to me:

green is clearly an enity
light blue an light yellow must be groups of "similar elements"
but .csolution.yml is blue wjile .cproject.yml is white : why ?

And .cproject.yml appears twice in the diagram:

one time as aninput of the PM entity
one time as an output of the PM entity
This puzzles me.

Referring to the updated spec proposal shared during the week (January 11th, open CMSIS meeting): https://github.com/brondani/devtools/blob/mvp-prototype/tools/projmgr/docs/Manual/Overview.md
The project description format to use to export or import a project seems now the .cproject.yml while the .cprj file becomes a intermediate file for the compilation. Is it the way you see it ?

The CPRJ file allows reproduceable builds as it contains all information to work stand-alone.  We will use it in CI systems for test automation where CMSIS-Build downloads packs in case that they are missing.  Also it fixes the pack versions used during the build process.
Today the CPRJ file is also the import mechanism for the MDK IDE to support backwards compatibility. Currently *.cproject.yml is not used as import/export file for third-party IDEs as the features might not map to an 'old' IDE.  However the *.yml files are clearly structured in a way to enable IDE integration (for example with VS Code).

I would suggest to close this item - or did we miss anything?


[EventRequest] IssuedFinChargeMemoLine.Table.al (table 305 "Issued Fin. Charge Memo Line")

Hi MS,
Please help us in migrating our verticalized solution by adding below Event in IssuedFinChargeMemoLine.Table.al Table.
Standard Code

Modified Code

Event Signature

Thanks
SUD

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


template ref compiled with any type

Version
3.2.9
Reproduction link
github.com
Steps to reproduce
git clone https://github.com/LongJinCen/Vue3-TS-error
npm i
npm run build-without-webpack

the source file content:
<template>
  <div ref="hint">
    {{ props.value }}
  </div>
</template>
<script lang="ts" setup>
import { ref } from "@vue/reactivity";

interface Props {
  value?: number
}
const props = withDefaults(defineProps<Props>(), {
  value: 1
})

const hint = ref()

</script>

when build finished, a App-compiled file will generate at the root directory:
import { defineComponent as _defineComponent } from 'vue'
import { toDisplayString as _toDisplayString, openBlock as _openBlock, createElementBlock as _createElementBlock } from "vue"

import { ref } from "@vue/reactivity";

interface Props {
  value?: number
}

export default /*#__PURE__*/_defineComponent({
  props: {
    value: { type: Number, required: false, default: 1 }
  },
  setup(__props: any) {
const props = __props as { value: number }
const hint = ref()
return (_ctx: any,_cache: any) => {
  return (_openBlock(), _createElementBlock("div", {
    // _value, _refs all have an any type, which will case an error
    ref: (_value, _refs) => {
      _refs['hint'] = _value
      hint.value = _value
    }
  }, _toDisplayString(props.value), 513 /* TEXT, NEED_PATCH */))
}
}

})

What is expected?
ref has a correct type
What is actually happening?
if ref property is a function, the paramer's type are all any

You are not giving the ref a type:
const hint = ref<HTMLElement | undefined>()

You are not giving the ref a type:
const hint = ref<HTMLElement | undefined>()

That's not the problem. I looked at the type definition for _createElementBlock:
// the props's type definition is not correct, The result is that ref is of type any
export declare function createElementBlock(type: string | typeof Fragment, props?: Record<string, any> | null, children?: any, patchFlag?: number, dynamicProps?: string[], shapeFlag?: number): VNode<RendererNode, RendererElement, {
    [key: string]: any;
}>;

not just createElementBlock, such as  createBlock ect, also have the save problem

I have ran same the same problem and can confirm that using ref<HTMLElement>() or ref<HTMLElement | undefined>() does not help.
@posva Please re-open this issue.


Simple Hodl Address

cc #35
I've put emphasis in time/date for user friendness but block height could probably be added on the future.

Just running a few tests, will likely merge by the end of the day.


Could you create ios-unity5 guide in objective c?

Hi Blitzagency
Thank you for creating this swift guide.
Could you also develop for objective C version?

In mutiple reference to The Nerd guide you can have a video tutorial on The Nerd Website

I have forked this project and updated for objective-c.
https://github.com/armandsLa/ios-unity5-objc


Updated the ObjectDetectionAPI to run batches.

@lingtangraster @Rob-Fletcher @dwilson1988 I was finding that the TensorFlow/ObjectDetectionAPI.py wasn't running batches when I I defined a batch_size.  I implemented that in the Python class and it appears to work and run really fast, about a minute to detect ~900 objects in Pro using a batch_size = 100:

Let me know if this is helpful or completely off base.

Hi @gbrunner, thanks for your suggestions.
Batch support was done through vectorize method in TemplateBaseDetector class.
def vectorize(self, **pixelBlocks):
        input_image = pixelBlocks['raster_pixels']
        _, height, width = input_image.shape
        batch, batch_height, batch_width = \
            prf_utils.tile_to_batch(input_image,
                                    self.json_info['ImageHeight'],
                                    self.json_info['ImageWidth'],
                                    self.padding,
                                    fixed_tile_size=False)

        batch_bounding_boxes, batch_scores, batch_classes = self.inference(batch, **self.scalars)
        return prf_utils.batch_detection_results_to_tile_results(
            batch_bounding_boxes,
            batch_scores,
            batch_classes,
            self.json_info['ImageHeight'],
            self.json_info['ImageWidth'],
            self.padding,
            batch_width
        )

ObjectDetectionAPI's ChildObjectDetector class inherited it, the input of the inference method is already a batch image array, which is a 4-d numpy array with shape [batch, image_height, image_width, bands].
Therefore, as I can see there is no need for any code modification at present. Thanks again for your time in reporting this issue, please let me know if you have any other suggestions.


Camera wrapped by TresGroup cannot be used properly after version 4.0

Describe the bug
I tried writing this code in tresjs v 4.0.2
    <TresPerspectiveCamera :position="[5, 5, 5]" />
    <OrbitControls />
    <TresAmbientLight :intensity="0.5" color="red" />
    <TresMesh ref="boxRef" :position="[0, 2, 0]">
      <TresBoxGeometry :args="[1, 1, 1]" />
      <TresMeshNormalMaterial />
    </TresMesh>
    <TresDirectionalLight :position="[0, 2, 4]" :intensity="1" cast-shadow />
    <TresAxesHelper />
    <TresGridHelper :args="[10, 10, 0x444444, 'teal']" />
  </TresGroup>

Then I got this

However, it can run correctly in v3.9.0

Reproduction
https://stackblitz.com/~/github.com/hexianWeb/starter
Steps to reproduce
No response
System Info
No response
Used Package Manager
pnpm
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hi @hexianWeb thanks for reporting this, what would be the use-case of adding a camera to a group?

Sorry for the late reply, I know adding a camera to a group is a weird operation. But I think it should probably have a more obvious error message (for example: can't wrap camera by group.)  and why it works normally in v3.9.0, but doesn't work after v4.0.


can't download CT-ORG: CT volumes with multiple organ segmentations dataset

hi,i find CT-ORG dataset from Cancer Imaging ARCHIVE,https://faspex.cancerimagingarchive.net/aspera/faspex/external_deliveries/259?passcode=caf2906b2acd7345a7f275ba96475214dc0c1bf9#
but i can't download the dataset,the error like this:

can you share the dataset on google drive?
thank you!!
chenjunqiang

@junqiangchen I have the same question with you, did you solve the poblem?


Please add number of years to anniversaries

Hi.
Can you please add number of years (e.g. in brackets beside the event) for anniversary events (such as birthdays etc.) so you can see it right away (which anniversary it is)?
Have a nice day.

Just update the event text in your calendar

What do you mean? Should I update text for recurring events (anniversaries) every year? I hope not...

I'm not sure how this would be done. Google Calendar doesn't even support this feature on it's own

All my anniversaries come from contacts in my phone. I had one calendar widget which displayed the anniversary number (I think it was Agenda widget or similar).

Joining this with #114 as showing age for Birthdays and Anniversaries looks like very close tasks

Joining this with #79 as showing age for Birthdays and Anniversaries looks like very close tasks

I don't think it's the same, or better... birthdays are stored in Google Calendar and tied with contacts. But one (like me) could have a shared calendar with yearly recurring events and if the widget is able to count the "instance number" of these recursions and display it in square brackets it would be very useful!
You could for example use it to count any age, of your pet, house, anything... without depending on a phone contact.
Please, change your mind about closing this issue.

I had one calendar widget which displayed the anniversary number (I think it was Agenda widget or similar).

Yes, it's Pure Calendar Widget. See my question here: it would be great to have a feature like this in Calendar-Widget, too.

@virtualdj As our widget cannot know a difference between "Anniversary" and any other recurring event, your suggestion better call:
Add an option: "Show occurrence number of a recurring event"
?!
I found good example cases here:

https://answers.microsoft.com/en-us/msoffice/forum/all/is-there-any-way-to-show-the-occurrence-number-of/47618036-12e2-4286-9826-444ee68aa4c6?auth=1

https://webapps.stackexchange.com/questions/10850/increment-number-inside-a-recurring-event-in-google-calendar

your suggestion better call:
Add an option: "Show occurrence number of a recurring event"

Yes, of course, but this also answers the OP requests because it can be useful for anniversaries, birthdays or any yearly event.

2. https://webapps.stackexchange.com/questions/10850/increment-number-inside-a-recurring-event-in-google-calendar

This is about changing the displayed text into Google Calendar (i.e. the event name), while I'm asking only to change the display on the widget.
So it's not something done at the server side (Google Calendar) but on the client (your widget): it should count the number of repetitions of a recurring event and display it (if the user enabled the relevant option).

1. https://answers.microsoft.com/en-us/msoffice/forum/all/is-there-any-way-to-show-the-occurrence-number-of/47618036-12e2-4286-9826-444ee68aa4c6?auth=1

Yes, something like that, for Android.
I don't know exactly how to implement the counter, probably like THIS? As I said, Pure Calendar already does it so there has to be a way.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_46227195-2617-41d4-9d47-84f64766a7ef/pull/1 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target_46227195-2617-41d4-9d47-84f64766a7ef.git

Docs Build status updates of commit 8a86072:
:clock10: Pending: waiting for processors (8 builds ahead of you)
:warning: Docs Build is busy, currently there are 8 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 8a86072:
:clock10: Pending: waiting for processors (8 builds ahead of you)
:warning: Docs Build is busy, currently there are 8 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 8a86072:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-UserAccountBuildPermissionInsufficientError] Owner v-alji no longer has Read permission of the repository https://github.com/VSC-Service-Account/docs-archive-test-source. It might be due to recent GitHub changes on SSO. Please ask the owner v-alji to logon to Docs Portal https://ops.microsoft.com once again. If it is not the case, please ask anyone of Admin permission of the repo to assign a new owner via Docs Portal https://ops.microsoft.com

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 8a86072:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-UserAccountBuildPermissionInsufficientError] Owner v-alji no longer has Read permission of the repository https://github.com/VSC-Service-Account/docs-archive-test-source. It might be due to recent GitHub changes on SSO. Please ask the owner v-alji to logon to Docs Portal https://ops.microsoft.com once again. If it is not the case, please ask anyone of Admin permission of the repo to assign a new owner via Docs Portal https://ops.microsoft.com

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


VSC freezes X when loading a project

VSCode Version:1.12.0 - Commit 5e5e9e3bb56a3182e58ad097e107966633643253
OS Version:Arch Linux

Steps to Reproduce:

Open VSC
File > Open Folder > Open
Crash. Seems to happen with git projects only?

This started happening out of the blue, older or newest VSC git version don't make a difference. I was on the same - working version, and after OS update it started freezing X. I can only move my cursor afterwards. Switching to a different TTY and killing VSC does not make a difference, I have to restart X.
I did a clean install of the OS and it still happened.
I can't reproduce this on my desktop with nvidia GPU, only laptop with integrated intel(and old AMD card, which is possibly not working).
I attached a folder that causes it.
MCModUpdater.zip

@C0rn3j I opened your project on both OSX and Linux and had no problems.
Do you have any extensions installed?

Do you have any extensions installed?

No, this happens on a clean install too.
As I said, it works just fine on my desktop that is Arch Linux too, so I'm wondering that it may be a bit hw specific?

@C0rn3j Have you tried starting with --disable-gpu?

Actually launching it through the terminal fixes the issue.
I use Cinnamon for a DE, the icon for VSC seems to have this content
"/opt/VSCode-OSS/code-oss" %F
I think this is totally caused by git - if I launch VSC through a terminal like this, it asks to verify the fingerprint. I guess whatever prompt VSC is invoking crashes it all? I'll edit this comment in a moment.

 c0rn3j@Lappy  ~  /opt/VSCode-OSS/code-oss
The authenticity of host 'gitlab.com (<IP_ADDRESS>)' can't be established.
ECDSA key fingerprint is SHA256:HbW3g8zUjNSksFbqTiUWPWg2Bq1x8xdGUrliXFzSnUw.
Are you sure you want to continue connecting (yes/no)?

@C0rn3j Are you using ssh for the git origin?

@chrmarti I don't think I quite get the question.
I have an ed25519 SSH private key and I have the public key added on gitlab.

@C0rn3j I just wanted to confirm you are using ssh as opposed to https to access your Git repository. Which you do from what I understand.
@joaomoreno Not sure if this might be a regression with the latest work on SCM and the Git provider.

@chrmarti I believe I was using very old(months) build of VSC just fine but then at some point it started crashing(I assume gitlab added a new server), which prompted me to update VSC but the bug was still there.

Glad to know that the crashes have stopped.
We have to find a way to cancel this verification, when used within Code.

To keep the number of issues in our inbox on a manageable level, we're closing issues that have been on the backlog for a long time but haven't gained traction: We look at the number of votes the issue has received and the number of duplicates issues filed.
Thanks for your understanding. Happy coding!

Does launching it via the Terminal fixes it? If so, I'd say that's a pretty good workaround.

We have ~5000 issues and growing. We're a team of ~20 devs and not growing. We have to make compromises. This issue has been around for > 6 months and you seem to be the only one who reported it. It appears you have a workaround. At some point we have to make tough decisions.

This issue has been around for > 6 months and you seem to be the only one who reported it.

I have also troubleshooted how this happens, so there's no extra user contribution needed.
I will not be submitting any more issues to VSC.
I suggest you look how other projects deal with older issues, this is the first time my reproduce-able bug report was outright closed.

Does launching it via the Terminal avoid the problem?

And it's interesting how you mention that it freezes X. Does it actually freeze the whole X session? Other applications are frozen too?

Does launching it via the Terminal avoid the problem?

As I said before, yes because that prompts to add the fingerprint to known ones, whereas launching it through the icon doesn't and freezes.

Does it actually freeze the whole X session?

As I recall it completely freezes Cinnamon. Everything is frozen and the only thing responsive is the cursor.
Re-testing it today, I get this when the fp is not present:

If I uninstall x11-ssh-askpass (which I assume I did not have installed at the time of original report), VSC simply won't sync with this message.
ssh_askpass: exec(/usr/lib/ssh/ssh-askpass): No such file or directory
Host key verification failed.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Which I would consider the proper behaviour.
All in all you could have simply asked "Is this still an issue when using latest release?", I'd have retested, confirmed it isn't, and issue would have been happily closed.

Oh, that's good news, then. Many thanks for confirming.


Survey submission errors even with all questions completed.

Uservoice tickets have been coming in suggesting the surveys don't seem to allow users to submit their answers.
So far, this bug has been replicated on:

[ ] Internet Explorer 8

I cannot replicate this bug on Firefox, which was the browser used by one of users submitting the ticket.

Remo's suggestion for fixing the missing .map functionality:
https://github.com/remomueller/tasktracker/blob/master/app/assets/javascripts/external/compatibility/array_prototype_map.js
https://github.com/remomueller/tasktracker/blob/master/app/assets/javascripts/external/compatibility/array_prototype_index_of.js
This allows index_of and map to be added (looked like map didn’t exist) for IE8 and Firefox support.

@remomueller @krand7 I just ran into this issue while integration-testing the research topic functionality.
I was creating a new user and going through the about-me survey flow. After filling in all the questions, the submit button was not working. Here's the screenshot:

js error location:

This looks like a separate issue that is not browser specific, recommend opening a new issue for this.


ZSH: command completion indents prompt

Using Linux, ZSH, two line setup.
On command completion the prompt gets temporarily indented.

There is a possible fix in d45efb0d46dfd881e77e1160e83f806088f17ce8 when an unnecessary reset was dropped.

Fixed with adding non-printing characters in 6b7b13be793bad4c2ce2f36a1e751ff8621fff83


Handling no-time-zone use case

Hello! We ran into a prob with our use of moment, I'm wondering if theres a better solution than to what we did and if its something we could help with a PR.
We have a web app that doesnt need the automagic time zone stuff that moment has. I.e. a user in PST picks 8AM, it should show up as 8AM for everyone no matter what TZ they are in. Our current hacky solution is:
export const localTime = t => //1p
  moment(t).utc().add(moment.parseZone(t).utcOffset(),'m')

My questions are:

is there a better way to do this
if there isnt, could we submit a PR for a convenience method to do this?

Thanks!

I assume that you are passing in an ISO 8601 date with offset. Because of this, when you use the default moment constructor, it will convert the date from that point in absolute time to the user's local time. If you ignore the offset, then the time will be interpreted as local. The best way to do this is to not have your back end system send the offset, and instead sent the time in the format '2016-01-01T13:00:00' or whatever.
If that is impossible, then you could use a parse format that ignores the offset.
I explain this pretty extensively in this blog post: https://maggiepint.com/2016/05/14/moment-js-shows-the-wrong-date/
In particular, this section may be of use: https://maggiepint.com/2016/05/14/moment-js-shows-the-wrong-date/#doNotWant
Does that cover what you're looking for?

Closing for lack of response. I suspect @maggiepint's answer is just what the OP wants anyway.


remove dependencies for python2.

for it's out of support, and many distros has deleted python2.
python3-pam  is avaliable in arch and void linux .
don't know other distros.

See #709


Remove TieredSmt

As a follow-up to https://github.com/0xPolygonMiden/crypto/issues/243, we need to remove TieredSmt after it has fully been removed from miden-vm.

Closed by #243.


Files not being deleted from the channel if you delete more than 100 files at once

what the title says
ex: if you decide to delete 165 files, in Teldrive/rclone you wont see them, but if you open your channel there will still be 65 files there
tested both on local DB and neonDB

sure my discord is .zdyo
sorry late reply, i've been a little busy


Implement the CLEANING_MODE_MATCHING_ANY_TAG option

ACL caching was not being cleaned properly when ACLs were deleted as this option had not been implemented and hence the clean() call was silently failing.

NB Composer.json in the Alchemy project will need to be updated, so I'll commit and pull request that too (separately of course, because it's a different project)

Yes please
On 27 May 2015 at 10:11, elicoten<EMAIL_ADDRESS>wrote:

NB Composer.json in the Alchemy project will need to be updated, so I'll
commit and pull request that too (separately of course, because it's a
different project)
—
Reply to this email directly or view it on GitHub
https://github.com/Techlightenment/zf2/pull/4#issuecomment-105833347.
Information in this e-mail and any attachments is confidential, and may
not be copied or used by anyone other than the addressee, nor disclosed to
any third party without our permission. There is no intention to create any
legally binding contract or other binding commitment through the use of
this electronic communication unless it is issued in accordance with the
Experian Limited standard terms and conditions of purchase or other express
written agreement between Experian Limited and the recipient. Although
Experian has taken reasonable steps to ensure that this communication and
any attachments are free from computer viruses, you are advised to take
your own steps to ensure that they are actually virus free.
Experian Ltd is authorised and regulated by the Financial Conduct
Authority.
Companies Act information: Registered name: Experian Limited. Registered
office: The Sir John Peace Building, Experian Way, NG2 Business Park,
Nottingham, NG80 1ZZ, United Kingdom. Place of registration: England and
Wales. Registered number: 653331.

--
*** NB THIS EMAIL ADDRESS IS NO LONGER IN USE - PLEASE USE
<EMAIL_ADDRESS><EMAIL_ADDRESS>***
Reuben ThompsonDirector of Technology, Alchemy Social
Experian Marketing Services7 Old Town | Clapham | London | SW4 OJT
T: +44 (0) 20 7819 5706 | M. +44 (0) 7946 452 872 |
<EMAIL_ADDRESS>F: +44 (0)<PHONE_NUMBER> | www.experian.co.uk/alchemy | skype: reuben_tech
Information in this e-mail and any attachments is confidential, and may not
be copied or used by anyone other than the addressee, nor disclosed to any
third party without our permission.  There is no intention to create any
legally binding contract or other binding commitment through the use of
this electronic communication.  Although Experian has taken reasonable
steps to ensure that this communication and any attachments are free from
computer virus, you are advised to take your own steps to ensure that they
are actually virus free.  Experian Limited (Registered No. 653331), with
registered office at Landmark House, Experian Way, NG2 Business Park,
Nottingham, NG80 1ZZ, United Kingdom.


Add more ruff rules

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (fd70664) to head (19337d7).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #168   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           65        65
  Lines         1412      1411    -1
  Branches       152       151    -1
=========================================
- Hits          1412      1411    -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Translate setup/custom-cloud/kops/ in Japanese

This is a...

[x]  Feature Request
[ ]  Bug Report

Problem:
No heading and subheading of setup/custom-cloud/kops/ in Japanese.
Proposed Solution:
Translate heading and subheading of setup/custom-cloud/kops/ in Japanese.
Copy from en content and Update content/ja/docs/setup/custom-cloud/kops.md.
Page to Update:
https://kubernetes.io/ja/setup/custom-cloud/kops/

/remove-lifecycle stale

/assign

/close


nuke tcp.Address and add proper IPv6 support

This PR helps us to get IPv6-ready.
fixes #1994
closes #1995

@mhils: only 1 failing test, that is related to binding to an IPv6 socket. At the moment I hard-coded it to use the v4 family. We need to introduce a nifty way of fixing this. The second example could be useful: https://docs.python.org/3/library/socket.html#example
@ujjwal96 ping FYI

Copying here from Slack: We can't use create_connection as we need to do the spoof_source_address logic between s = socket.socket() and s.connect(). We need to so something like this:

Move if self.spoof_source_address: and connection.bind(self.source_address) into _makesocket().
Copy the implementation of create_connection and adapt it to use our _makesocket: https://hg.python.org/cpython/file/3.6/Lib/socket.py#l688

Yes, I grep-ed for *.host and *.port in console/.

Done.


[DISCUSSION] Remove wikimedia android data client

Summary:
The library is out of date and unmaintained (I believe) making it more difficult to integrate with new APIs or model changes. We should move the code into our codebase.

I was under the impression that we were maintaining a fork of this? @maskaravivek

The library is out of date

Given the fact that the library is claimed to be a successor of the mediawiki:api I would say it is far from being outdated. If anything, it must be more up-to-date. "Incomplete" might be appropriate.

... and unmaintained ...

I don't think it is. There have been changes in the upstream as recent as November 2019.
I also have one comment related to @maskaravivek's comment at #3257 (where this discussion originated):

Yes, there's a lot of history behind why the data-client came into picture and honestly I would prefer to have everything in our main codebase rather than maintain a library that too for model classes which keep changing frequently.

IIUC, the library provides a nice model to access the Mediawiki and REST API's response. And I thought the API response would be stable and thus the model would not need to be changed. I don't understand why the model needs to be changed frequently. What am I missing?

Having said that, as of now it's interesting to note that the Wikipedia app itself doesn't seem to be using the external library. It seems to be using a version of the library present within their codebase.

This was the maintainer's (@dbrant 's) recommendation to me in Aug 2019 when we were encountering issues with needing to make a modification to the library:

Therefore, for the time being, I would recommend that you simply take the current source files that you're using from the library and copy them into your project (keep making any modifications you need), and no longer depend on the library.  At a later time, when the new endpoints and models are settled, we may revisit publishing a common client library that will factor in the needs of both products, but I'm afraid that doing this today would be prohibitively difficult.

I am personally OK with either option - (1) maintaining the fork as a separate library or (2) putting everything into our main codebase. However, it would be great if we could get an updated recommendation from @dbrant in case anything has changed on WMF's side. :)

I am in favor of 2 as the description says

I am also in favor of 2. To make the transition easier, maybe we could add it as a library module in our codebase.

To make the transition easier, maybe we could add it as a library module in our codebase.

Sounds good to me. Let's give it a few days in case we get an update from dbrant, if we don't hear anything we can start doing this next week?

Oh hey 👋
Yes, please do proceed with the option that is most sensible to you.
The problem with the "data-client" library is that it was a little too ambitious in scope, and ended up containing too much business logic that was specific to our product.
For the future, it might be a good idea to have a shared library that contains only the model classes that are returned by the API, and nothing else. (i.e. no network services, no utility functions, etc.)

Thank you for the update, @dbrant ! I agree that a more simplified shared library would be a better idea in the future. :)
Seems like we are all on board for option 2. Feel free to take this up, anyone!

Library modules often lead to a bit more overhead in the setup, I am fine just copying them to a distinct package inside commons. Modular applications have many benefits but I don't think we get any of them right now and you get a bit of complexity

@macgills I suggested adding it as library module as I thought it might be the easiest way to setup as the project is already setup as an Android library.
I just did it locally and it hardly took me 5 minutes to set it up.
My first focus was to get this as part of our code base as quickly as possible. I am okay moving stuff to the app too but it might be useful to have it modular.


802.1q support

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

97 of 106 (91.51%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.5%) to 80.008%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/tc/types/utils.go
0
9
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.5%

Covered Lines:
1929

Relevant Lines:
2411

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

97 of 106 (91.51%)  changed or added relevant lines in 4 files are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.3%) to 79.801%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/tc/types/utils.go
0
9
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/server/server.go
5
70.57%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
1924

Relevant Lines:
2411

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

97 of 106 (91.51%)  changed or added relevant lines in 4 files are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.3%) to 79.801%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/tc/types/utils.go
0
9
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/server/server.go
5
70.57%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
1924

Relevant Lines:
2411

💛  - Coveralls


plugins with "signalk-plugin-enabled-by-default": true are not enabled after re-start

It appears that plugins that have "signalk-plugin-enabled-by-default": true defined in package.json are not actually active until the Submit button is clicked in the Plugin Config screen.
Steps to reproduce on server v1.10.2:

Installed plugin which has "signalk-plugin-enabled-by-default": true defined in package.json file.
Re-started server
In Server / Plugin Config expand the section for the plugin.
Active checkbox is checked as expected.
When trying to use actions provided by the plugin they fail.
After clicking  Submit in Server / Plugin Config then plugin becomes functional.

Works on my machine.
You are missing a step from the steps to test this properly:

make sure there is no pre-existing configuration for the plugin in your plugin-config-data directory

The test was conducted on a "clean" Docker instance so there was no pre-existing configuration data.
Would it make a difference if the plugin is handling PUT requests or handling a 'non-Signal K API' route?

I double checked, a bit differently but the result should be the same:

add "signalk-plugin-enabled-by-default": true to an existing, installed plugin
make sure that there is no existing config file for the plugin
restart the server

=> the plugin is enabled (its start method is called as the server starts).
If you set DEBUG=signalk:interfaces:plugins you get debug logging of plugins loading and starting.
If I add
app.get('/foo', (req, res) => {
  res.json('bar')
})

the endpoint works, without enabling anything in the plugin config panel.
Please provide more detail about what exactly is not working. The actual plugin code would also help...


Test for ExpressionTool outputs validation

Test that the output objects returned by an ExpressionTool process are validated against the outputs schema. This is not true for CWL <= v1.2, and has been fixed for CWL >= v1.3.

Has this been implemented?


Landscape client computer-title should be automatic

On previous revisions of the landscape-client-charm, the computer-title option needed by the landscape client used to be automatically computed as the hostname of the charm the landscape-client-charm was subordinated to, through the container_relation_joined hook [1]. This meant that multiple landscape clients could each be registered with a different computer-title.
Now, the computer-title is a config option, meaning that all landscape-client charm units will register using the same computer title. There should still be an option to use the previous behaviour.
[1] https://bazaar.launchpad.net/~landscape/landscape-client-charm/trunk/view/head:/hooks/hooks.py#L90

Pull request is here https://github.com/canonical/landscape-client-charm/pull/11

Issue has been resolved.


System labels showing until you add user label, then have to refresh browser to get them back

Version - v1.0.1
Steps to Reproduce:

Add a Digital Ocean host without any user labels
Go to host detail page and click on the Labels tab
Edit host and add a user label
Go back into detail's page and look at labels tab (system label missing)
Refresh page (system labels come back)

Results: Before you add a user label you get 3 system labels showing:

After you add a user label, you see only the user label

Expected: Should not have to refresh page to get system labels to show back up

version - v1.1.0-rc3
Verified fixed


CMSFields error adding blocks to DataObjects

We've been using Blocks on non-SiteTree viewable DataObjects. Recently it started throwing errors, trying to add the Blocks gridfield to these classes:
[Recoverable Error] Argument 1 passed to GridFieldOrderableRows::getSortTable() must be an instance of DataList, instance of UnsavedRelationList given, called in /var/www/public/3sheeps/gridfieldextensions/code/GridFieldOrderableRows.php on line 235

Adding  a $this->owner->ID check in BlocksSiteTreeDataExtension::updateCMSFields() solves the issue.

closed via #125


CUDA printing is unreliable

Reporting a bug

[X] I am using the latest released version of Numba (most recent is visible in
the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[X] I have included below a minimal working reproducer (if you are unsure how
to write one see http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports).

Reproducer:
from numba import cuda

@cuda.jit
def f():
    print("Hello from f")

print("Launch f")
f[1, 1]()

@cuda.jit
def g():
    print(1)

print("Launch g")
g[1, 1]()

Expected:
Launch f
Hello from f
Launch g
1

Actual:
Launch f
Launch g
Hello from f

The problem is between the keyboard and the chair - printing is asynchronous. Changing to:
from numba import cuda

@cuda.jit
def f():
    print("Hello from f")

print("Launch f")
f[1, 1]()
cuda.synchronize()

@cuda.jit
def g():
    print(1)

print("Launch g")
g[1, 1]()
cuda.synchronize()

yields:
Launch f
Hello from f
Launch g
1

Some explanation added to the docs in #5423.

Right, it needs a synchronize call.


Dishwasher testing

@ollo69 - No pressure but when you're ready, I have a 2019 model dishwasher to test.

On coming week end....

@ollo69 I also have a newer dishwasher that we can test with.

@ollo69 ..i too can join the dishwasher test...

With release 0.4.0 DishWasher is available.
Device based on APIv1 may work, device based on APIv2 very probably will not work because I need some debug info to complete.
To provide me right information you must enable debug log adding this to your configuration.yaml:
logger:
  default: warning
  logs:
    custom_components.smartthinq_sensors: debug

Then let the HA run for 5-10 minutes and send me the home-assistant.log files to my e-mail<EMAIL_ADDRESS>If you want check before the log file for sensible information (mac-address, e-mail, etc) and remove it.
If the new version not work at all, send me the log and then roll-back to last 0.3.x waiting for update.
Thanks.

I would really like to talk with the person that define standard in LG!!!
On dishwasher with APIv2 the format for the info is completely different from the others, some job to do here....

Ok @ollo69 .. I have shared the logs as requested..thanks for your assistance again

Noticed this today after a restart... hasn't occurred since.
2020-05-07 11:39:48 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.lg_dishwasher is taking over 10 seconds
2020-05-07 11:39:48 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.lg_dishwasher fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 426, in _make_request
    six.raise_from(e, None)
  File "<string>", line 3, in raise_from
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 421, in _make_request
    httplib_response = conn.getresponse()
  File "/usr/local/lib/python3.7/http/client.py", line 1344, in getresponse
    response.begin()
  File "/usr/local/lib/python3.7/http/client.py", line 306, in begin
    version, status, reason = self._read_status()
  File "/usr/local/lib/python3.7/http/client.py", line 267, in _read_status
    line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
  File "/usr/local/lib/python3.7/socket.py", line 589, in readinto
    return self._sock.recv_into(b)
  File "/usr/local/lib/python3.7/site-packages/urllib3/contrib/pyopenssl.py", line 326, in recv_into
    raise timeout("The read operation timed out")
socket.timeout: The read operation timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 725, in urlopen
    method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
  File "/usr/local/lib/python3.7/site-packages/urllib3/util/retry.py", line 403, in increment
    raise six.reraise(type(error), error, _stacktrace)
  File "/usr/local/lib/python3.7/site-packages/urllib3/packages/six.py", line 735, in reraise
    raise value
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 677, in urlopen
    chunked=chunked,
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 428, in _make_request
    self._raise_timeout(err=e, url=url, timeout_value=read_timeout)
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 336, in _raise_timeout
    self, url, "Read timed out. (read timeout=%s)" % timeout_value
urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='aic.lgthinq.com', port=46030): Read timed out. (read timeout=10)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 472, in async_device_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/smartthinq_sensors/sensor.py", line 377, in update
    self._api.device_update()
  File "/usr/src/homeassistant/homeassistant/util/__init__.py", line 240, in wrapper
    result = method(*args, **kwargs)
  File "/config/custom_components/smartthinq_sensors/__init__.py", line 322, in device_update
    self._restart_monitor()
  File "/config/custom_components/smartthinq_sensors/__init__.py", line 306, in _restart_monitor
    raise ex
  File "/config/custom_components/smartthinq_sensors/__init__.py", line 293, in _restart_monitor
    self._device.monitor_start()
  File "/config/custom_components/smartthinq_sensors/wideq/device.py", line 715, in monitor_start
    mon.start()
  File "/config/custom_components/smartthinq_sensors/wideq/device.py", line 107, in start
    self.work_id = self.session.monitor_start(self.device_id)
  File "/config/custom_components/smartthinq_sensors/wideq/core_v2.py", line 437, in monitor_start
    "workId": gen_uuid(),
  File "/config/custom_components/smartthinq_sensors/wideq/core_v2.py", line 389, in post
    language=self.auth.gateway.language,
  File "/config/custom_components/smartthinq_sensors/wideq/core_v2.py", line 177, in lgedm2_post
    timeout=DEFAULT_TIMEOUT,
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 578, in post
    return self.request('POST', url, data=data, json=json, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 530, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 643, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 529, in send
    raise ReadTimeout(e, request=request)
requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='aic.lgthinq.com', port=46030): Read timed out. (read timeout=10)
2020-05-07 11:40:48 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.lg_dishwasher is taking over 10 seconds
2020-05-07 11:40:48 ERROR (MainThread) [homeassistant.helpers.entity] Update for sensor.lg_dishwasher fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/urllib3/contrib/pyopenssl.py", line 488, in wrap_socket
    cnx.do_handshake()
  File "/usr/local/lib/python3.7/site-packages/OpenSSL/SSL.py", line 1934, in do_handshake
    self._raise_ssl_error(self._ssl, result)
  File "/usr/local/lib/python3.7/site-packages/OpenSSL/SSL.py", line 1646, in _raise_ssl_error
    raise WantReadError()
OpenSSL.SSL.WantReadError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 381, in _make_request
    self._validate_conn(conn)
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 976, in _validate_conn
    conn.connect()
  File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 370, in connect
    ssl_context=context,
  File "/usr/local/lib/python3.7/site-packages/urllib3/util/ssl_.py", line 377, in ssl_wrap_socket
    return context.wrap_socket(sock, server_hostname=server_hostname)
  File "/usr/local/lib/python3.7/site-packages/urllib3/contrib/pyopenssl.py", line 491, in wrap_socket
    raise timeout("select timed out")
socket.timeout: select timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 725, in urlopen
    method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
  File "/usr/local/lib/python3.7/site-packages/urllib3/util/retry.py", line 403, in increment
    raise six.reraise(type(error), error, _stacktrace)
  File "/usr/local/lib/python3.7/site-packages/urllib3/packages/six.py", line 735, in reraise
    raise value
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 677, in urlopen
    chunked=chunked,
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 384, in _make_request
    self._raise_timeout(err=e, url=url, timeout_value=conn.timeout)
  File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 336, in _raise_timeout
    self, url, "Read timed out. (read timeout=%s)" % timeout_value
urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='aic.lgthinq.com', port=46030): Read timed out. (read timeout=10)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 472, in async_device_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/smartthinq_sensors/sensor.py", line 377, in update
    self._api.device_update()
  File "/usr/src/homeassistant/homeassistant/util/__init__.py", line 240, in wrapper
    result = method(*args, **kwargs)
  File "/config/custom_components/smartthinq_sensors/__init__.py", line 322, in device_update
    self._restart_monitor()
  File "/config/custom_components/smartthinq_sensors/__init__.py", line 306, in _restart_monitor
    raise ex
  File "/config/custom_components/smartthinq_sensors/__init__.py", line 293, in _restart_monitor
    self._device.monitor_start()
  File "/config/custom_components/smartthinq_sensors/wideq/device.py", line 715, in monitor_start
    mon.start()
  File "/config/custom_components/smartthinq_sensors/wideq/device.py", line 107, in start
    self.work_id = self.session.monitor_start(self.device_id)
  File "/config/custom_components/smartthinq_sensors/wideq/core_v2.py", line 437, in monitor_start
    "workId": gen_uuid(),
  File "/config/custom_components/smartthinq_sensors/wideq/core_v2.py", line 389, in post
    language=self.auth.gateway.language,
  File "/config/custom_components/smartthinq_sensors/wideq/core_v2.py", line 177, in lgedm2_post
    timeout=DEFAULT_TIMEOUT,
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 578, in post
    return self.request('POST', url, data=data, json=json, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 530, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 643, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 529, in send
    raise ReadTimeout(e, request=request)
requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='aic.lgthinq.com', port=46030): Read timed out. (read timeout=10)

This are timeout due to network issue.
I will put a easier error message on next release...


Testing/utils

New unittest for utils.py
Unit test fetch in basic ways. Would have tested more fetches, but
downloading stuff for tests is annoying and mocking is more
dependencies.
Minor dependency cleanup too.
Thoughts?

Cool! Yea extra really needs to be cleaned up and tested


Added wildcard watermelon.tools to CSP

Description
Will allow all from our source
Type of change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)

I'll approve once we know we can add what you will send me to Webflow's storage

I'll approve once we know we can add what you will send me to Webflow's storage

How is it related? This one opens up the CSP, if we cannot do it do we remove it?

I'll approve once we know we can add what you will send me to Webflow's storage

How is it related? This one opens up the CSP, if we cannot do it do we remove it?

No response @baristaGeek but I'll merge as this is low risl


Filtering ITMS/FTMS from Lumos data files losing all scan data

Dear Proteowizard developers,
I hope you are well. I'm currently having some trouble with msconvert regarding filtering of a Thermo Lumos raw data file containing multiple mass analyzer steps. I am using ProteoWizard 3.0.8725 x64. Direct and non-filtered conversion from raw to mzML, then subsequent import into Skyline works fine and the filter string names are preserved in the unfiltered mzML file.
Curiously however, if implementing filtering for only FTMS (--filter "analyzer FT" OR --filter "analyzer orbi" OR "--filter "analyzerType FTMS"), all scans are lost with only the chromatogram/metadata preserved. I have provided a copy of the command line process run below:
`W:\1_RAW_Data\4_Lumos>>
msconvert Lumos_data.raw --filter "analyzer FT"
format: mzML
m/z: Compression-None, 64-bit
intensity: Compression-None, 32-bit
rt: Compression-None, 64-bit
ByteOrder_LittleEndian
indexed="true"
outputPath: .
extension: .mzML
contactFilename:
filters:
analyzer FT
filenames:
Lumos_data.raw
processing file: Lumos_data.raw
writing output file: .\Lumos_data.mzML
`
This same process works fine with my Velos Orbitrap data so I don't believe my commands to be the issue.
Cheers,
Chris

What are your  sections in the resulting mzML?

Thanks for the quick reply.
Comparing the filtered vs non-filtered mzml conversion:
run id spectrumList is missing
run id chromatogramList is the same.
index name="spectrum" is different (no details present for this section and
no offset values)
index name="chromatogram" is different (TIC intensity is 0.001% of the
non-filtered mzML file)
indexedmzML, mzML, cvList,
fileDescription, referenceableParamGroupList, softwareList,
instrumentConfigurationList
and dataProcessingList are the same.
On Mon, Jul 30, 2018 at 1:14 PM, Matt Chambers<EMAIL_ADDRESS>wrote:

What are your sections in the resulting mzML?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ProteoWizard/pwiz/issues/144#issuecomment-408959329,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aca4SK1RGjbFD68LhdCphmdK5pKXBK1sks5uL0z5gaJpZM4VkqW0
.

I mean what are the contents in the <instrumentConfigurationList>

Sorry for the misinterpretation:

On Tue, Jul 31, 2018 at 12:33 PM, Matt Chambers<EMAIL_ADDRESS>wrote:

I mean what are the contents in the
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ProteoWizard/pwiz/issues/144#issuecomment-409304102,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aca4SJ8eQeaUbhFaTIWppfNXS3-m5QS6ks5uMJTbgaJpZM4VkqW0
.

Hmm, are you sure that your data contains FT scans? The scan filters say FTMS? Can you send a RAW file?

100% sure. It's a triggered neutral loss experiment. I've compressed the raw file so it's a 400MB zip archive. Do you have a preferred method to share the data? It's not a sensitive method/sample so can be public.

This will work for non-sensitive data: https://skyline.ms/filecontent/home/support/file sharing/begin.view?

Thanks. It's uploaded and available now.

I can reproduce the problem and have figured out the cause, I just haven't gotten to fix it yet. (the filter only checks the first analyzer, when it really should check the last, or all)

That's great to hear, thanks Matt! Is the single mass analyzer assumption specific only for msconvert or are other programs part of the Proteowizard suite such as msaccess subject to this limitation?

Should be fixed in #204.

Sorry for resurrecting this issue but I am having the same problem using the msconvert in ProteoWizard 3.0.18215.f6864290f
I am using this file from PRIDE
Pride repo: PXD004732
Test File:  01625b_GB2-TUM_first_pool_10_01_01-2xIT_2xHCD-1h-R1.raw
MSCONVERT="/c/Program Files/ProteoWizard/ProteoWizard 3.0.18215.f6864290f/msconvert.exe"
TESTFILE="01625b_GB2-TUM_first_pool_10_01_01-2xIT_2xHCD-1h-R1.raw"
count_filters() {
    grep -P "filter" ./out/*.mzML | grep -oP "value=\".*?ms(\d|\s)" | sort | uniq -c
}

"${MSCONVERT}" ${TESTFILE} --filter "peakPicking true 1-" -o out/
count_filters
#   28830 value="FTMS + c NSI d Full ms2
#    3227 value="FTMS + p NSI Full ms
#   28830 value="ITMS + c NSI r d Full ms2

"${MSCONVERT}" ${TESTFILE} --filter "analyzer orbi" --filter "peakPicking true 1-" -o out/
count_filters
# EMPTY

"${MSCONVERT}" ${TESTFILE} --filter  "peakPicking true 1-" --filter "analyzer orbi" -o out/
count_filters
# EMPTY

"${MSCONVERT}" ${TESTFILE} --filter "analyzer orbi" -o out/
count_filters
# EMPTY

"${MSCONVERT}" ${TESTFILE} --filter "analyzer FT" -o out/
count_filters
# EMPTY

"${MSCONVERT}" ${TESTFILE} --filter "analyzer FTMS" -o out/
count_filters
# EMPTY

Is there anything I am doing wrong?
Kindest wishes,
Sebastian

Sorry for resurrecting this issue but I am having the same problem using the msconvert in ProteoWizard 3.0.18215.f6864290f
I am using this file from PRIDE
Pride repo: PXD004732
Test File:  01625b_GB2-TUM_first_pool_10_01_01-2xIT_2xHCD-1h-R1.raw
MSCONVERT="/c/Program Files/ProteoWizard/ProteoWizard 3.0.18215.f6864290f/msconvert.exe"
TESTFILE="01625b_GB2-TUM_first_pool_10_01_01-2xIT_2xHCD-1h-R1.raw"
count_filters() {
    grep -P "filter" ./out/*.mzML | grep -oP "value=\".*?ms(\d|\s)" | sort | uniq -c
}

"${MSCONVERT}" ${TESTFILE} --filter "peakPicking true 1-" -o out/
count_filters
#   28830 value="FTMS + c NSI d Full ms2
#    3227 value="FTMS + p NSI Full ms
#   28830 value="ITMS + c NSI r d Full ms2

"${MSCONVERT}" ${TESTFILE} --filter "analyzer orbi" --filter "peakPicking true 1-" -o out/
count_filters
# EMPTY

"${MSCONVERT}" ${TESTFILE} --filter  "peakPicking true 1-" --filter "analyzer orbi" -o out/
count_filters
# EMPTY

"${MSCONVERT}" ${TESTFILE} --filter "analyzer orbi" -o out/
count_filters
# EMPTY

"${MSCONVERT}" ${TESTFILE} --filter "analyzer FT" -o out/
count_filters
# EMPTY

"${MSCONVERT}" ${TESTFILE} --filter "analyzer FTMS" -o out/
count_filters
# EMPTY

Is there anything I am doing wrong?
Kindest wishes,
Sebastian

Try a newer version of pwiz. Even though this issue was fixed in 2018, it seems your version manages to predate it.

Try a newer version of pwiz. Even though this issue was fixed in 2018, it seems your version manages to predate it.

Noticed the error was due to the path not using msconvert from the actual updated installation (so I guess the issue is that updating pwiz does not remove older versions, which in itself could be a design choice...)
Thanks for the reply.


Incomplete handling of optional traits when parents have > 4 total desired traits

https://github.com/tylercamp/palcalc/blob/main/PalCalc.Solver/BreedingSolver.cs#L228
If there are 2 required traits and 4 optional traits in the solver, and two parents contain all 6 traits between them, the solver will attempt to calculate the probability of inheriting 6 traits, which is not possible and no children will be produced.
When the total desired traits exceeds the max, we should generate permutations of required + optional traits up to the max of 4.

Fixed with https://github.com/tylercamp/palcalc/commit/d4be2000c5d22c0e7acaf1a2c22a9a3288d78a6f pending release

Fixed in v1.4.2