Add MVP specification

Would really appreciate each of your careful review of this general outline both so that we can all be on the same page and so that you can point out anything that needs to be changed or added. Thanks in advance for your valuable insight.

Would like @steve0xp's review as well when he accepts invite to repo.

@steve0xp in regards to your high level Qs you left here: https://github.com/BuidlGuidl/eth-tech-tree/pull/11#discussion_r1617959020
High level:

Matt said much of the same. I think the CLI is the shortest path to having something that people can interact with.
Would love to integrate with BG app. BG app is going to be getting an overhaul in the future so the opportunity will be there to add this as a data source.
Feel like we touched on this in out recent call. Good thoughts.

Details:

It is important for them to submit onchain as part of the learning process. The biggest problem I see with your idea is that most of these will lack the personal touch that a BG profile submission should have. "personal-challenges" might be nice to encourage them to submit there though.
Added a couple concepts to the readme.


Consider not making the Kotlin dep implicitly fetched

Currently spring-cloud-contract-kotlin-spec is part of spring-cloud-contract-spec. That means, that even if you don't use Kotlin, you will download Kotlin (which is around 50 mb).
Maybe we should consider making Kotlin and all the next specs opt-in ? That way we will not download the whole world.
The funny thing is that if you add the pact module then you will download Scala, Groovy & Kotlin.

I agree, the additional modules (like kotlin) can depend on core modules, but not the other way round.

That's a breaking change with regards to Hoxton.M2


Supported Windows 10 Installations?

Is Windows 10 Pro/EE deliberately unsupported for even Express and Developer Editions, or is this an oversight?

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

ID: c09beb1a-92a9-4335-511c-395ba64c875b
Version Independent ID: 8f43fca3-43d7-a2e4-1469-bf17f14d9ac8
Content: Hardware and software requirements for installing SQL Server - SQL Server
Content Source: docs/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-ver15.md
Product: sql
Technology: install
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

@drchilds Thank you for the feedback.
Windows 10 TH1 1507 or greater is stated as a hardware requirement so this is likely an oversight.
Assigning this to the author for review.

Hi @drchilds, thanks for contacting Microsoft! I have submitted a change to update the documentation that should be live later this week. I will close out this Git Issue in the meantime but please feel free to comment should you need anything further from us :)
Thanks again and hope you have a wonderful rest of your day!
Masha from the SQL Docs team


Updating readme from branch example

Updates
I updated the readme file. Please review and accept

thoughts
i probably shoudn't, but okay


fix flashloan v2 issues due to revm bump

Does this mean flashloan v2 is now default als not dependent on the proxy anymore? So if I use a single Ityfuzz instance I don't need to use the proxy?

yes this is correct. However, we are still backtesting the changes and recommending folks to use the stable version.

I'm eager to try the new stuff :smile:  Is it stable enough yet?


only yfd avaliable

Love the new theme! The icons look great. I can't seem to find the yfc and yfd options in Spotlight, nor in the repository to launch this dark theme that's featured on the screenshot. Will it be added in the future?

cheers, yfc is now default and yfd should be here: https://github.com/fontforge/YosemiForge/tree/master/Themes

OK, yes, I see that just starting FontForge has the new theme. But yfd.command doesn't start the dark theme shown in the screenshot. In fact, I checked the script and the files it copies over don't look like the dark-themed photo.
Look for example at this yellow box:

(Themes/PixmapsDark/palette3drotate.png)
which is green in the theme screenshot:

(elements inserted as direct links to files in your repository)
Also, since the original elements are removed by the script (rm -r $PIX*), is there a way to go back to the normal theme afterwards?

The screenshot is old so I think the colors of the box has changed.
You can get the bright theme back by copying the contents of this: https://github.com/fontforge/YosemiForge/tree/master/New Theme/pixmaps and deselect any theme in fontforge settings.
Is a bit messy right know since we are/were in the process of updating this as our main theme.

Ah, ok. Well, I'd like to test drive the dark theme in case you reenable it somehow. Right now both FontForge.app and yfd.command start the bright theme. Not a big issue, though, so feel free to close it :)


Spotify not loading after applying theme

Spotify won't load after i applied the theme.

Fixed by updating spotify


Is it possible to remove unused imports?

https://www.npmjs.com/package/prettier-plugin-organize-imports already does this (through the typescript language service) but can't sort imports like we can as with the trivago plugin.
I get that it's a 'prettier' plugin and this action might probably change the AST, but it could be opt-in and be a major differentiator from the trivago one

This plugin currently does not look at any of the code other than imports, so determining whether imports are used would be a big change. I won't immediately say "no" right now, but it would require a lot of upvotes on this request for me to seriously consider it, I'm afraid.
In the meantime, maybe there is an ESLint plugin or custom that can remove unused imports?

We use eslint to detect unused code, and I found this plugin: https://www.npmjs.com/package/eslint-plugin-unused-imports — it has an auto-fix too! Maybe that will work for your needs?
I concur with @IanVS that I don’t think it’s appropriate behavior for this prettier-plugin. IDEs often call prettier every time they auto-save, and it would be irritating if you add an import, and then scroll down to the function where you want to use the import, and the IDE chooses to save then, and the import has already vanished before you can start using it!


Should we support Tracker.jl?

In #1979 we removed support for Tracker.jl because:

It is quite a burden to maintain (in particular when adding new features).
AFAIK there are no cases where it's preferable over Zygote or ReverseDiff.

But then @devmotion wrote the following that made me think that we should at least discuss this!

I just noticed this change - this seems quite dangerous because things might start breaking silently without us noticing it while still stating officially in the package (compat entry, docs etc.) that Tracker is supported.

So I think in case this is the official policy (which IMO is a bit sad because Tracker is quite stable, much simpler than ReverseDiff or Zygote, and started to receive updates more frequently again) then IMO it should be removed from the package, docs, etc., ideally before removing tests for it.

Originally posted by @devmotion in https://github.com/TuringLang/Turing.jl/pull/1979#discussion_r1206426705

One thing I'd like to add is that we at least warn people that Tracker.jl isn't being tested against anymore: https://github.com/TuringLang/Turing.jl/blob/fb7da8d3d7e786effb559a10c5e13d47a6f9ccf4/src/essential/ad.jl#L14-L16
So users will be aware in the case they try to use it. Hence I think part of the above comment is addressed.
But whether we should support or not is still something to discuss.

It is quite a burden to maintain (in particular when adding new features).

Is there a concrete example of a recent feature for which Tracker support was not added or very time-consuming to add?
I think we definitely have to distribute our limited resources in a meaningful and productive way, and spending excessive amounts of time on fixing an AD backend does not seem like a good investment if there are good alternatives. However, dropping support for an AD system that works reliably completely is a seemingly extreme change. Maybe one way around it would be to more clearly state how well different AD systems are supported, a bit like the Tier 1/Tier 2/etc. support of Julia itself for different architectures.
It is also a bit strange IMO to drop support for the default reverse-mode backend and stop testing it, without removing it from the dependencies of Turing. Currently, still ForwardDiff and Tracker are the only AD dependencies of Turing and the only AD backends that are available for every user of Turing. For all other AD systems one has to install and load the backend separately.
In any case, my strong opinion is that anything that is declared compatible should be tested - but I think it would be fine to have different levels of support and hence mark some tests for some AD backends as broken (as we have been doing, e.g., in DistributionsAD for a long time).

Is there a concrete example of a recent feature for which Tracker support was not added or very time-consuming to add?

One was the tests in #1979 breaking for Tracker.jl without any obvious reason: https://github.com/TuringLang/Turing.jl/actions/runs/4769935772/jobs/8480760022
Granted, I didn't spend too much time debugging the above because we had also been running into some tests breaking for Tracker.jl in a Bijectors.jl PR too (https://github.com/TuringLang/Bijectors.jl/pull/253).
But the above is really just what "broke the camels back"; supporting Tracker.jl does take a significant higher effort from us due to its lack of support for ChainRules. Both Zygote and ReverseDiff now suppports it, which means that writing a single rrule is sufficient if we drop suppport for Tracker. If we don't, we also have to write rrules for this, which is IMO prone to error + requires effort. Hence, if Tracker.jl isn't actually used by anyone together with Turing.jl, then I think dropping it is reasonable.
This of course all hinges on "is it being used", which I obviously cannot say for sure. What I'm pretty confident about is that we have not recommend Tracker.jl in years; if we suggest reverse-mode, we always suggest ReverseDiff or Zygote. I also don't really remember anyone reporting any issues or asking any questions relating to Tracker.jl, which also indicates a lack of usage (I find it hard to believe that it just works so well that nobody has issues while simultaneaously never suggesting usage of it).

I think we definitely have to distribute our limited resources in a meaningful and productive way, and spending excessive amounts of time on fixing an AD backend does not seem like a good investment if there are good alternatives. However, dropping support for an AD system that works reliably completely is a seemingly extreme change. Maybe one way around it would be to more clearly state how well different AD systems are supported, a bit like the Tier 1/Tier 2/etc. support of Julia itself for different architectures.

I do like this idea, but it's a bit unclear to me how we should implement this wrt. test-suite.
For example, if we were to put Tracker.jl in Tier 2, do we continue testing it but allow the CI to fail for this particular suite? Otherwise the ranking doesn't do much for us maintainers :/

It is also a bit strange IMO to drop support for the default reverse-mode backend and stop testing it, without removing it from the dependencies of Turing. Currently, still ForwardDiff and Tracker are the only AD dependencies of Turing and the only AD backends that are available for every user of Turing. For all other AD systems one has to install and load the backend separately.

Aaah okay that's a mistake on my end. I completely forgot to check if Tracker.jl was a dep of Turing.jl; I thought that was only ForwardDiff.
So I wholeheartedly agree with the above!

In any case, my strong opinion is that anything that is declared compatible should be tested - but I think it would be fine to have different levels of support and hence mark some tests for some AD backends as broken (as we have been doing, e.g., in DistributionsAD for a long time).

I'm honestly fine with this, as long as we define which ones we're happy to allow "breaking" changes for, and which ones we aren't (your tier-based system would do the trick) :+1:

due to its lack of support for ChainRules. Both Zygote and ReverseDiff now suppports it

There is at least interest in adding something similar to what's done in ReverseDiff to Tracker as well: https://github.com/FluxML/Tracker.jl/issues/132 (Generally, in my experience the macro in ReverseDiff is also a bit buggy, limited, and does not work completely reliable, so IMO it's definitely not a first-class support of ChainRules in ReverseDiff)

For example, if we were to put Tracker.jl in Tier 2, do we continue testing it but allow the CI to fail for this particular suite?

I thought about marking the failing tests as broken, opening an issue (if someone has time to fix it, PRs would always be welcome) but not prioritizing work on such fixes.

I noticed a backlink to this issue from the Tracker one, so perhaps some background will help you with your decision.

There is at least interest in adding something similar to what's done in ReverseDiff to Tracker as well: https://github.com/FluxML/Tracker.jl/issues/132

As I recall, that issue was created after yet another painful session fighting Zygote bugs. Unfortunately there's nothing to back up the interest: most of the AD-related work we do is necessarily spent on writing/improving ChainRules and keeping Zygote above water.
That said, if this is something that you think you might have capacity for on your side, let us know. A ReverseDiff-like solution is arguably easier now with package extensions, though in an ideal world one would be able to auto-add rules like I mentioned in https://github.com/FluxML/Tracker.jl/issues/132#issuecomment-1231010319. As-is, I fear the only plan is to wait for a better AD which doesn't require us to (re)write too many custom rules.


Will make a proper NavBar

It consists of the BetterColor name on the left side, Home, and Github link buttons. I can add more buttons if the maintainer needs

Hi @Yasshu55, Can I take this?

can i work on this?


Error executing action 'SubstituteValuesAspireManifestAction': System.ArgumentException: Unknown dictionary in placeholder {db.inputs.password}.

🔥 Bug Description
aspirate generate  fails with error:
Error executing action 'SubstituteValuesAspireManifestAction':
System.ArgumentException: Unknown dictionary in placeholder {db.inputs.password}.
🔍 Steps to Reproduce the Bug

Go to '...'
Click on '....'
Scroll down to '....'
See error

🧯 Possible Solution

Usefull tips or places to start go here.

Any chance you could share the manifest.json file please that was generated in the AppHost directory?
Thanks

manifest.json
I believe the issue could be on my side , I haven't find to much info how I need to setup the secrets in my project to make everything right.
So this is also my Program,cs  from AppHost:
`
var builder = DistributedApplication.CreateBuilder(args);
var pgpassword = builder.Configuration["PGPASSWORD"];
var postgresdb = builder
.AddPostgresContainer(name: "db", port: 5432, password: pgpassword)
.AddDatabase("postgres");
var rabbitmqp = builder.Configuration["RABBITMQ_PASSWORD"];
var rabbit = builder.AddRabbitMQContainer(
name:"rabbit", port: 5672,  password: rabbitmqp);
var nmap = builder
.AddProject<Projects.Gur8Aspire_NetworkExplorer>("nmap")
.WithReference(rabbit);
var apiservice = builder
.AddProject<Projects.Gur8Aspire_ApiService>("apiservice")
.WithReference(postgresdb)
.WithReference(nmap);
builder.AddProject<Projects.Gur8Aspire_Blazor>("webfrontend")
.WithReference(apiservice);
var app = builder.Build();
app.Run();
`
And  part of appsettings.json from web API:
`
{
"Aspire": {
"Npgsql": {
"EntityFrameworkCore": {
"PostgreSQL": {
"ConnectionString": "Host=localhost;Port=5432;Database=postgres;Username=postgres;Password=;Include Error Detail=true",
"DbContextPooling": true,
"HealthChecks": true,
"Tracing": true
}
}
},
"RabbitMQ": {
"Client": {
"HealthChecks": true,
"ConnectionString": "amqp://user:password@localhost:5672"
}
}
},
`

Thanks for your manifest
It looks like Aspire preview 1-4, not preview 5 (latest) because they'e now moved inputs to be a top level parameters object not part of the container resource like your manifest shows
 "inputs": {
        "password": {
          "type": "string",
          "secret": true,
          "default": {
            "generate": {
              "minLength": 10
            }
          }
        }
      }
    },

    ```

    In the latest preview of Aspire that Aspirate supports this should be a parameter.v0 resource, not part of the container. Unfortunately there were lots of breaking changes in preview5, but its not GA yet :)


Configure Zappr

This is a reduced example of a configuration file for Zappr.
If you have questions you can reach us

in our Gitter channel
on Twitter

These are the features we currently support:
Approvals

Approve pull requests with comments and configurable pattern
"Veto" (ie. block) pull requests with comments and configurable pattern
Configure how many approvals your pull request needs before merging
Extensively configure who can approve or veto in your project

Pull Request guidelines

Block a PR until it has the required set of labels (e.g. reviewed)
Block a PR as long as it has unfinished tasks

Specification guidelines

Configure minimum length of pull request title and description
Configure if pull request description can be the same as pull request template

Commit message guidelines

Configure patterns that all commits in a pull request must match

Automatic branch creation

Automatically create a branch in your repository for every issue

Coverage remained the same at 38.095% when pulling 96dd6d3beac5ccacc7ba83f052ab940a01e39af8 on configure-zappr into 25e7cd8cf3bdefff32ed96c66e909ca8554f0bb1 on master.

Coverage remained the same at 38.095% when pulling 96dd6d3beac5ccacc7ba83f052ab940a01e39af8 on configure-zappr into 25e7cd8cf3bdefff32ed96c66e909ca8554f0bb1 on master.


DPL-033 addition of a phiX control during library prep in Heron pipeline [Heron]

User story
DPL_033 As stakeholder in Heron pipeline (Stef L) I would like enable the addition of a phiX control during library prep  to allows us to normalise the negative control and to thus pass more samples.
Who are the primary contacts for this story
Rich R
Sara S
Emma G
Naomi Park
Stef L
Acceptance criteria
To be considered successful the solution must allow:

[ ] A new NovaSeq sequencing pipeline dedicated only to Heron samples needs to be created.
[ ] The prompt ‘add spike control’ should not be present in this inbox.
[ ] The prompt ‘add spike control’ should instead appear when the pool tubes are created towards the end of the library prep. This is because phiX will be added during the sample pooling step
[ ] A new sequencing inbox for Heron samples has been created which does not provide the ‘add spike control’ option.
[ ] The ‘add spike control’ option instead appears during the pool tube creation step. This enables the operator to register the barcode of the phiX spike during the sample pooling step.
[ ] The phiX must be registered such that it demultiplexes as tag 888 on the NPG QC page.

Dependencies
This story is blocked by the following dependencies:

#<issue_no.>
sanger/#<issue_no.>

References
This is part of a change control process (028/21)
Additional context
The Heron pipeline is being modified to enable the addition of phiX during the pooling step. The addition of phiX will allow us to normalise the read number in the negative control and thus to reduce the number of failed samples. To enable this I (Stef L, Tris B, Team Heron) require the following changes to be made to the Heron LIMS pipeline:
Heron_phiX_LIMS story.docx

Details of PhiX:
PhiX is usually added in the sequencing pipeline as part of the AddSpikedInControlTask. This involves:

Looking up the PhiX by barcode
Adding the PhiX asset as a parent to the lane
The PhiX does NOT actually get added as an aliquot in the lane (I think this is because PhiX addition actually predates multiplexing)

When the batch.xml and flowcell_io look up the PhiX they use the relationship spiked_in_buffer which finds any SpikedBuffer parents, the aliquot information etc is then pulled from there.
Changes:
Unfortunately the PhiX will now be added before the lane is generated, and instead the PhiX will need to be injected into the pool tube.
Solutions:

We could potentially just add PhiX as a parent of the tube, and then adjust spiked_in_buffer_links to include non-direct ancestors. However this will affect 175483 lanes which have multiple SpikedBuffer ancestors. (I believe most of these cases are due to SpikedBuffer itself sometimes having SpikedBuffer ancestors)

A more robust solution would be to switch to actually transferring the PhiX into the tube, and allowing transfers to persist it downstream. This would require:

Either migration of historic data, or a fallback mechanism if PhiX is not present
Some means of easily identifying PhiX that has been added as a control, such that entity_type can be set to 'library_indexed_spike'/'library_control' as appropriate. (Rather than 'library_indexed'/'library' as with standard samples. We do have PhiX.sample which may be useful here. (Although it will be worth checking that we don't have PhiX.sample running as a standard sample anywhere)
spiked_phix_barcode is usually pulled straight from the SpikedBuffer spiked_in_buffer&.human_barcode. I don't actually know the best way to get this is we transfer the aliquots in, as the library_id points back at the stock. (And we can't fix this without changing historical data)

Other issues:

A new NovaSeq pipeline would probably need to be backed by new request types and updated heron submisison templates to reduce risk of accidentally processing samples via the wrong pipeline.
The new pipeline approach feels somewhat restricted, and it would feel cleaner to detect the spiked in controls, and dynamically change the behaviour of the step.
Annoyingly previous convention was to append (spiked in controls) to pipelines with controls, and omit it on those without. But by the time NovaSeq went live, controls were spiked into all pipelines, so this was felt to be redundant. :(

#Detect multiple PhiX ancestors
SELECT labware.id, COUNT(DISTINCT phix.id) FROM labware
LEFT OUTER JOIN asset_links ON asset_links.descendant_id = labware.id
LEFT OUTER JOIN labware AS phix ON phix.id = asset_links.ancestor_id
WHERE labware.sti_type = 'Lane::Labware'
GROUP BY labware.id
HAVING COUNT(DISTINCT phix.id) > 1

Don't appear to have any PhiX in lanes as a 'normal' sample:
SELECT receptacles.sti_type, labware.sti_type, COUNT(aliquots.id) FROM receptacles
LEFT OUTER JOIN aliquots ON aliquots.receptacle_id = receptacles.id
LEFT OUTER JOIN labware ON labware.id = receptacles.labware_id
WHERE aliquots.sample_id = 1255141
GROUP BY receptacles.sti_type, labware.sti_type

sti_type
sti_type
COUNT(aliquots.id)

Receptacle
LibraryTube
230

Receptacle
SampleTube
2

Receptacle
SpikedBuffer
6024

We do have 5  SpikedBuffer tubes containing a sample other than PhiX.sample
SELECT aliquots.sample_id, COUNT(labware.id) FROM receptacles
LEFT OUTER JOIN aliquots ON aliquots.receptacle_id = receptacles.id
LEFT OUTER JOIN labware ON labware.id = receptacles.labware_id
WHERE labware.sti_type = 'SpikedBuffer'
GROUP BY aliquots.sample_id

sample_id
COUNT(labware.id)

NULL
1

1081381
5

1255141
6024

These SampleTube outliers may be artefacts, there has been in the past issues with generating parent library tubes as the page used defaulted to sample tube in the drop down menu

Sample '1081381' appears to be a PhiX variety, and has only appeared on a single lane (2141255) where its actually flagged as 'library_indexed' (ie. treated as though it isn't PhiX) already. So we don't need to worry about accidentally altering the behaviour here.

Screenshots of current place in Sequencing pipeline where PhiX control is added:
First task on batch screen (Novaseq pipeline):

Scan barcode of SpikedBuffer tube:

Looking into lanes that have more than one SpikedBuffer Tube ancestor, to see if it's safe to start identifying the SpikedBuffer of a lane as the most recently created of all the SpikedBuffer ancestors.
-- Lanes that have more than one SpikedBuffer ancestor, where the 'most recent' doesn't match the 'direct'
SELECT labware_id, num_phix_ancestors, most_recent_phix_id, direct_phix.id AS direct_phix_id

FROM
(
  SELECT labware.id AS labware_id, COUNT(DISTINCT phix.id) AS num_phix_ancestors, MAX(phix.id) AS most_recent_phix_id

  FROM labware

  LEFT OUTER JOIN asset_links ON asset_links.descendant_id = labware.id
  LEFT OUTER JOIN labware AS phix ON phix.id = asset_links.ancestor_id

  WHERE labware.sti_type = 'Lane::Labware'
    AND phix.sti_type = 'SpikedBuffer'

  GROUP BY labware.id
  HAVING COUNT(DISTINCT phix.id) > 1
) AS phix_ancestors

JOIN asset_links AS al_direct ON al_direct.descendant_id = labware_id AND al_direct.direct = true
JOIN labware AS direct_phix ON direct_phix.id = al_direct.ancestor_id AND direct_phix.sti_type = 'SpikedBuffer'

WHERE most_recent_phix_id <> direct_phix.id;
-- 278 rows

-- Lanes that have more than one SpikedBuffer ancestor, where the 'most recent' is not also 'direct'
-- A lot of the above rows are explained by the Lane having >1 'direct' SpikedBuffer tube
SELECT labware_id, num_phix_ancestors, most_recent_phix_id, al_most_recent.direct AS is_direct

FROM
(
  SELECT labware.id AS labware_id, COUNT(DISTINCT phix.id) AS num_phix_ancestors, MAX(phix.id) AS most_recent_phix_id

  FROM labware

  LEFT OUTER JOIN asset_links ON asset_links.descendant_id = labware.id
  LEFT OUTER JOIN labware AS phix ON phix.id = asset_links.ancestor_id

  WHERE labware.sti_type = 'Lane::Labware'
    AND phix.sti_type = 'SpikedBuffer'

  GROUP BY labware.id
  HAVING COUNT(DISTINCT phix.id) > 1
) AS phix_ancestors

JOIN asset_links AS al_most_recent ON al_most_recent.descendant_id = labware_id AND al_most_recent.ancestor_id = most_recent_phix_id

WHERE al_most_recent.direct = false;
-- 32 rows (all SpikedBuffer tube 13232535)

Technical tasks:

[ ] Modify NPG interfaces (MLWH flowcell and batch xml) to allow indirect SpikedBuffer ancestors of lanes, as well as direct parents
[ ] Modify V1 API to accept multiple parents for a tube (for Limber tube creation)
[ ] Limber interface to allow PhiX tube scanning
[ ] Tweak integration suite test for Heron pipelines
[ ] Sequencescape pipeline - without PhiX addition


Add sipuri.rs

#3

Codecov Report

Merging #7 into master will decrease coverage by 0.54%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master       #7      +/-   ##
==========================================
- Coverage   93.45%   92.91%   -0.55%
==========================================
  Files          11       12       +1
  Lines         611      790     +179
==========================================
+ Hits          571      734     +163
- Misses         40       56      +16

Impacted Files
Coverage Δ

crates/sipmsg/src/sipuri.rs
90.90% <0.00%> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #7 into master will decrease coverage by 0.54%.
The diff coverage is 92%.

@@            Coverage Diff             @@
##           master       #7      +/-   ##
==========================================
- Coverage   93.45%   92.91%   -0.55%
==========================================
  Files          11       12       +1
  Lines         611      790     +179
==========================================
+ Hits          571      734     +163
- Misses         40       56      +16

Impacted Files
Coverage Δ

crates/sipmsg/src/userinfo.rs
93.54% <100%> (-0.9%)
:arrow_down:

crates/sipmsg/src/parameters.rs
98.36% <100%> (+0.12%)
:arrow_up:

crates/sipmsg/src/sipuri.rs
90.9% <90.9%> (ø)

Continue to review full report at Codecov.

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


Time is constantly drifting on V3

No matter the watch style, performance setting, NTP Auto Sync, battery level, etc., it starts drifting in a very short time, becoming up to a minute fast very quickly. After 1-2 days or so, it’ll be 3-4 minutes fast. I need to frequently sync the time manually because of this.

Watchy V3 - Watchy_GSR v1.4.7M
Using pre-compiled bins for the V3 (ESP32S3)

This is a known issue with Watchys (with the exception of some V1's), they all drift.  But, Watchy GSR thanks in part to the work I did with SmallRTC and the Drift Calculation, the drift can be brought into a manageable value.  Look at the Troubleshoot menu and then Edit RTC.  The information is in Usage, you can search for drift and it will give you another link on Note 6 to information of SmallRTC's explanation of how it does Drift Compensation.
If you're unsure how to run this test, reply back.  But I would suggest NTP Sync, then go to Troubleshoot, Edit RTC, open a browser window to time.is and manually validate the time, then Menu to go in and Menu again to begin the drift calculation.  24 to 48 hours or longer later, revisit the time.is and Edit RTC and change the time to match it (you can't NTP here), once you have the time as close as you can get it, Menu past it and Menu once more to get it to calculate the drift and fix the time.  If afterwards, it is still going too fast, refer to the Drift Compensation from Note 6 above on how to reduce the drift value.
I'm still reducing mine and now it's quite close to being accurate by itself.  Though the math doing the calculation is correct, the environment and floating point limits are reducing it's accuracy, hence the need to manually adjust it later.


Renovate for Edition 2021

In a still-future edition, unsafe_op_in_unsafe_fn may error.
Let's get ahead of that.

Well it should never hard error, just deny by default.
But this is seemingly a small enough amount of unsafe I guess it's fine.

Yeah, this adds a little bit of noise but it's good because it shows where our unsafe API is pretty directly exposing internal unsafety.


Segger System View support on different platforms setup documentation.

I've noticed this PR https://github.com/apache/incubator-nuttx/pull/5327 and tried to get Segger System View it on my S32K144 based board.
Unfortunely there wasn't a how to guide, but I tried to mimick the SIM sysview configuration https://github.com/anchao/incubator-nuttx/blob/9efb473feaa116b61c6d47d00878baf6a08a167d/boards/sim/sim/sim/configs/sysview/defconfig
When compiling though I got a couple of errors:

Regarding a ASM file optimized for ARMv7 SEGGER_RTT_ASM_ARMv7M.S, my workaround was to remove that from build system and use the fallback C file.

Some errors regarding missing up_perf_gettime and up_perf_getfreq function, I circumvented this by enabling CONFIG_TIMER_ARCH which implements these functions, but it seems that the sim config didn't require those.

After this it successfully compiles and it seems I can connect through SEGGER systemview,

However as you can see it's partly working however time stays at zero and I can't see task switching itself.
@anchao would you be able to provide steps you did to get it to work on your Cortex-M55 platform, or do you have an idea on which interfaces I need implement/enable to get this fully to work?

Hi @PetervdPerk-NXP  ,

Unfortunely there wasn't a how to guide, but I tried to mimick the SIM sysview configuration

Yes, the SIM configuration simply enables the configuration to ensure that the compilation can work normally.
We will add a back-end based on file to save the system view stream on SIM platform, which is still under development

Regarding a ASM file optimized for ARMv7 SEGGER_RTT_ASM_ARMv7M.S, my workaround was to remove that from build system and use the fallback C file.

Sorry to confuse you, I just tested the configuration under v8m, you can temporarily remove the optimization of v7m, I will try to fix this issue further

Some errors regarding missing up_perf_gettime and up_perf_getfreq function, I circumvented this by enabling CONFIG_TIMER_ARCH which implements these functions, but it seems that the sim config didn't require those.

I have uploaded a new PR, they implemented cycle counter based on DWT, you can try this commit:
https://github.com/apache/incubator-nuttx/pull/5850
In addition, you also need to initialize the CPU clock frequency in the board implement, eg:
https://github.com/apache/incubator-nuttx/pull/5850/commits/b5edd67cc592a226c9b0fe32914ac5763c78eea9#diff-2e2c7b8e12a8db8218fd22d16f664621da802957420e528caf0c44d0307dc819R57

do you have an idea on which interfaces I need implement/enable to get this fully to work?

I think this should be caused by the cycle counter not working properly, please check whether up_perf_init() or up_perf_gettime() is working properly

Hi @anchao ,
We've rebased on #5850 and implemented the up_perf_init() hook on our board and it seems to be working fine now.
Would it be something to include some documentation on how to use Segger Systemview in the official NuttX documentation?
https://nuttx.apache.org/docs/latest/

We are planning to invite the professional technical writer to improve the document, please stay tuned.

When compiling though I got a couple of errors:

Regarding a ASM file optimized for ARMv7 SEGGER_RTT_ASM_ARMv7M.S, my workaround was to remove that from build system and use the fallback C file.

@PetervdPerk-NXP https://github.com/apache/incubator-nuttx/pull/5930 could fix the above issue.


fix(storybook): Set addon-a11y to manual avoiding false positives

Hey, I just made a Pull Request!
In storybook, the addon-a11y automatic execution timing is not consistent for some components. This resulted in false positives for some components like DismissableBanner. Upon refreshing the page multiple times, it would sometimes pop a WCAG 2 violation. The behavior was inconsistent, the error would pop only sometimes and with different contrast ratio warnings.
This patch configures the addon-a11y to set the execution as manual thus ensuring the user is aware of the state the report is running against.

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thanks all! 👍


raft: Require sync when committed index changes

I ran into an issue when the following things occurred:

new entries were added to raft
a node crashed
the node restarted

raft2017/05/09 10:52:42 applied(38) is out of range [prevApplied(0), committed(37)]
panic: applied(38) is out of range [prevApplied(0), committed(37)] [recovered]
	panic: applied(38) is out of range [prevApplied(0), committed(37)]

It turns out that in my application code, when I would Save the WAL before applying raft entries (and then persist the new applied index), raft wasn't always persisting the committed index to disk when it changed, per the logic in MustSync.
Before this change, MustSync would return true if the number of entries was non-zero or the HardState's Vote or Term value changed, but not if the HardState's Commit value changed.
With this change, when the client calls Save on the WAL, if the committed index has increased, it will cause the HardState to be persisted to disk.

This actually causes a new issue when I perform snapshots (at entry 3) before adding the raft entries:
panic: 1 state.commit 37 is out of range [3, 3] [recovered]
	panic: 1 state.commit 37 is out of range [3, 3]

due to state.Commit being out of range [r.raftLog.committed, r.raftLog.lastIndex()]. I'll continue investigating how to address the issue I'm facing.

I thought there was an issue with this fix, but it was actually a problem with my application. Reopening.

commit index does not need to be persisted. It is recoverable as long as the majority is running.
Check raft paper for details. Thanks.

@xiang90 If I understand correctly, it should be invariant that applied <= committed. Is this correct? And the application layer is responsible for persisting applied. Since this raft implementation requires on startup that applied <= committed, how is my application to know when the underlying raft impl has persisted committed to disk, and that it's safe to write applied? If a node crashes, should I check to see how far the raft library has marked the log as committed, and roll-back my applied if applied > committed, and re-apply raft entries that I have already applied to my DB?

@bts if your application does not keep on disk state, then you need to restore from snapshot and apply to commit. You do not need to persist applied index. When you start to persist applied index, you also probably want to persist committed index. It is all up to the application. We want to keep core raft close to the paper. If this is not something we have to do, we leave it out.

@xiang90 In the situation where I am crashing, if I were to persist to the committed index alongside my applied index, it would always be greater than or equal to my applied value. The issue here is that the raft library reports to my application that it's committed to 38, and then when it crashes and restarts, it starts reporting 37 because it never persisted the committed index to 38 on-disk.

it starts reporting 37 because it never persisted the committed index to 38 on-disk.

can you application simply ignore all entries from raft that is smaller than the one your application persisted?

or you can persist the commit index in WAL. this is really up to you, right?

@xiang90 By the way, thank you for working through this with me. I appreciate it.

can you application simply ignore all entries from raft that is smaller than the one your application persisted?

RestartNode (with my applied index) panics, but yes, I could open the WAL before calling that, and check to see whether raft failed to persist committed as far as the application applied, and call RestartNode with the minimum of these values. This doesn't seem ideal though; should every client of this library (who uses AppliedIndex) be required to do this to prevent panics in raft?

or you can persist the commit index in WAL.

If my application persisted the commit index that raft is reporting but merely keeping in-memory, I will experience the same panics. How should I be querying raft to ask how far it has instead durably persisted this value to disk?
Also I was just taking a look at the raft paper, and came across this quote:

As described in Section 5.3, a leader knows that an entry from its current term is committed once that entry is stored on a majority of the servers

Do we know how they define "store"? If it means "durably persisted to disk," then it would seem to me that this change is required?

that entry is stored

it says about the entry not the commit index. raft paper defines volatile and non-volatile state somewhere I believe... I can check the paper later this week to find it for you.

@xiang90

or you can persist the commit index in WAL.

I misunderstood what you were saying in this quote yesterday, and thought you were recommending that I persist the committed index on my application, alongside my applied index.
How would the user of this library accomplish this? I only see Save, which does not save the committed index when it changes. The only other method I see that might accomplish this task is SaveSnapshot, but I don't imagine that the library would require that clients snapshot on every extension to the log (if they are keeping track of AppliedIndex)?

@xiang90
So, having thought about this some more, I've come to the conclusion that in the presence of byzantine faults there is no way around requiring applications of libraries like this to express their log entries as idempotent operations and to embrace re-applying entries as a necessary reality. Between this, and the fact that the paper lists committedIndex under "volatile storage," let's drop this change.
At the same time, I feel like this (panic) situation I am running into here represents a clear issue with the current implementation -- if it is possible (and easily reproducible!) to have a scenario where the application applies entries beyond what raft considers to be committed upon startup after a crash, this needs to be recoverable scenario.
What would you think about my submitting a new PR where, instead of panicking when the application-supplied AppliedIndex is beyond the committed index, it returns back to the application a lower number for AppliedIndex that it needs to rollback to? This seems more sensible than requiring users of AppliedIndex functionality to fish around in a snapshot to detect how far raft managed to persist its Committed index, take the minimum of these two values, and pass that in as AppliedIndex. Thoughts?

(...or maybe it should just be documented that users of AppliedIndex know that they are required to take on this burden to use the feature correctly, and avoid panics)


adding curl quickstart

Adding a curl quickstart that shows curl commands for each PaLM API endpoint.

Looks great, Soo! I just made a couple of nitty suggestions for your consideration...


Feature: Blogroll Page

✅ Checklist

[X] I have followed every step in the contributing guide.
[X] The PR title follows the convention we established conventional-commit

Changelog
This PR will add an archive/blogroll page to the website.

The blog post links in the preview deployment are pointing to localhost:3000. This should be fixed.


[Question] Sample content for .cognito/db/$userPoolId.json

Kindly share a sample content for .cognito/db/$userPoolId.json..
I just cloned to config.json it doesn't work.

If I leave it as empty i get resource not found execption.

Thanks for the question. I should really have an example for this in the readme, or a way to create the pools using the API...
I think this should be the minimum you need for a pool to work:
{
  "Users": {},
  "Options": {
    "Id": "your user pool id",
  }
}


Create own vpc+subnet to ensure success when the user has no default VPC

Turns out we dont actually need this (at least yet) and it adds a whole bunch of complexity and slows down startup/shutdown significantly.
So I'm going to abandon this as a draft PR for now in case we need it later on.
The functionality works, but there are still 2 tasks to go:

fully parallelize startup and cleanup
allow cleanup to run in less runs, currently we need to run cleanup three times to fully eliminate the vpc. We should be able to get it down to 2 times.

Superceded by https://github.com/shotover/aws-throwaway/pull/22


use hwy/simd for RMSNorm(f, bf, f) calculation

use highway/simd for RMSNorm(f, bf, f) calculation for performance purpose.
static HWY_NOINLINE HWY_MAYBE_UNUSED void RMSNorm(
     const float* HWY_RESTRICT x, const hwy::bfloat16_t* HWY_RESTRICT weight,
     float* HWY_RESTRICT out, size_t size) ;

It seems copybara has faced an issue, maybe the rerun can solve it :))

Yes indeed, still have an issue with copybara transforms. Looking into it :)

Issue resolved 👍 One more internal review, then it will be merged.


Markdown text does not recognize bold and italic

See the Description section of Bar Charts -> multi axis demo

the <au-markdown> should be purely markdown, no html tags

I had no idea about that limitation


Error following RAP generator installation, generator setup

Stuck on step 6. "Run the class zdmo_cl_rap_generator_setup. This class generates the following objects"
I get a message

Check the class texts - they appear missing

Tried re-pulling the repo a few times with no luck. Can you advise on the class texts I need for ZDMO_CL_RAP_GENERATOR_SETUP?

Not sure what has happened here. (Sorry for my late reply). Which branch have you tried? And can you maybe try again ? I have published several updates since february.


sc-4857 Add Trisa Logo on the landing page

Codecov Report

Merging #478 (adbd0c1) into main (bd19b1f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #478   +/-   ##
=======================================
  Coverage   37.46%   37.46%
=======================================
  Files         151      151
  Lines        2389     2389
  Branches      608      608
=======================================
  Hits          895      895
  Misses       1319     1319
  Partials      175      175

Continue to review full report at Codecov.

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


occlusion spot: remaining TODOs

below is remaing TODOs

better interpolation using original path behind ego #290
consider using lanelet info to filter unnecessary possible collision.
fix velocity of spline interpolation #290
consider safe margin before collision point https://github.com/autowarefoundation/autoware.universe/pull/344
consider detection area of passable/impassable collisiopn. https://github.com/autowarefoundation/autoware.universe/pull/354

below is bug fix
https://github.com/autowarefoundation/autoware.universe/pull/351

@taikitanaka3 Do you still have any remaining issues? If not, please close the issue.

feature implementation is done so i can close this


CAMEL-12629 - add support for Channel.CHANNEL_SHELL command execution

that's fair. those pieces can be moved to another place.

Thanks @davsclaus , @oscerd


Safari v16 black flickering on right slide of almost all sliders (proof by video)

Check that this is really a bug

[X] I confirm

Reproduction link
https://swiperjs.com/demos#infinite-loop
Bug description
I own a Macbook Pro 16" with macOS Ventura which uses Safari v16.0 .
Many slider's don't work correctly and if you switch slide a black flicker happens.
This can get reproduced on the swiperjs website.
I even made a short clip to describe the issue better:
https://user-images.githubusercontent.com/10922763/173672756-56845390-1d5b-4fee-b998-447c49ef14f3.mov
https://youtu.be/HpTp97CuoLY
Kind regards,
thanks for this code,
Daniel Oberlechner
Expected Behavior
No flickering while switching slides ...
Actual Behavior
Black flickering on the right side of the slider.
Swiper version
8.2.4
Platform/Target and Browser Versions
macOS Ventura first day patch, Safari 16
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

I've got the same issue!


Error: "react-native run-ios" not working even for sample apps, AwesomeProject

I'm using a Macbook air to test run some application for ios. the react-native run-ios does not seem to work appropriately as I always get the "unable to connect to server... do npm start" error message as soon as I open up the app on the emulator.
I've tried this again for facebook's example app, AwesomeProject and I still got the same error.
The react-native version I am using is 0.30.0 and the react-native-cli is 1.0.0

@bluej-21 do you have watchman installed?
https://facebook.github.io/react-native/docs/getting-started.html

yes, I do. Also it seems like the packager is running, it'll display the  messages on the packager but it doesn't seem to display the  messages.

I also am having trouble running the AwesomeProject example. I've looked through every Github/Stack solutions and none of them work.  Using fresh installs of literally everything.
:CFBundleIdentifier does not exist
Please advise!
.

For me everything is working fine.
Have you tried to reset the packager?
node node_modules/react-native/local-cli/cli.js start --reset-cache
Or the hard way with reinstalling everything and restarting watchman also:
rm -rf node_modules/ && npm cache clear && watchman watch-del-all && npm i
Is network working well? Can you open the index.js-File in your browser?
Something like this: http://localhost:8081/index.ios.js?platform=ios&dev=true&minify=false
Anyhow, let's compare versions:
within the Project after "react-native init AwesomProject":
$ react-native --version
react-native-cli: 1.0.0
react-native: 0.31.0

$ node -v
v6.3.1

$ uname -a
Darwin macbook.fritz.box 15.6.0 Darwin Kernel Version 15.6.0: Thu Jun 23 18:25:34 PDT 2016; root:xnu-3248.60.10~1/RELEASE_X86_64 x86_64

(OSX El Capitain Version 10.11.6 (15G31))

XCode Version 7.3.1 (7D1014)

I've run into this issue since upgrading to Xcode 8.

I'm on Xcode 8 and I haven't seen this problem yet. Is it still causing troubles for people?

I have a similar problem.  I don't get an error; instead it just hangs.  Nothing happens.  Only since upgrading Xcode and OSX

Earlier today watchman was not reloading my JS when I made changes.  Tried fresh install of watchman, react-native-cli, rebooting, etc.  Now I’m experiencing a similar issue to @ostigley .  In my current react native project when I run react-native run-ios, nothing happens.  No errors.  Just hangs.
Tried creating a new project with react-native init AwesomeProject, and this hangs as well.
@itinance I tried running node node_modules/react-native/local-cli/cli.js start --reset-cache, and this hangs as well.
Tried running rm -rf node_modules/ && npm cache clear && watchman watch-del-all && npm i, and this hangs on the watchman command.
So something seems to be wrong with my watchman.  I might be related to the Xcode and or OS update (recently updated to macOS 10.12.1 and Xcode 8), but not sure.
watchman -v
4.7.0

react-native -v
react-native-cli: 1.2.0
react-native: 0.34.1

node -v
v5.7.1

Any ideas?

@blackburnian I found the problem was with watchman.  Fixed it here:
https://github.com/facebook/watchman/issues/381#issuecomment-257669560

I tried many github examples but non of them is working with latest react native installation, but my own made projects are working fine

@vikrampanwar  get same issue, have u update your node to node 8?

Let's merge this into a more recent issue, for clarity.

Duplicate of #14447

Duplicate of #14423


Add mathieularose.com

Cloudflare scan: https://radar.cloudflare.com/scan/0eb3e7b5-57c1-4633-9319-5c535dddbeb1/summary

This PR is:

[x] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (512kb.club site)
[ ] Other not listed

[x] I used the uncompressed size of the site
[x] I have included a link to the Cloudflare report
[x] This site is not an ultra minimal site
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[x] Check to confirm

- domain: mathieularose.com
  url: https://mathieularose.com/
  size: 311.98
  last_checked: 2024-04-21

Cloudflare Report: https://radar.cloudflare.com/scan/0eb3e7b5-57c1-4633-9319-5c535dddbeb1/summary

Thanks!


Device-id in node red integration

I'm trying to set node red integration but I cannot understand where to indicate the device_id (work_for service).

thanks

The device_id is an internal identifier from home assistant for every device (collection of entities) and not easy to find:
https://community.home-assistant.io/t/device-id-entity-id-where-to-find/289230


fix typos [skip ci]

@bradrydzewski i don't have admin permissions here, you need to fix and merge that :)


Does this work with fonts installed locally on the server?

Rather than Google Fonts we would like to use fonts installed locally on the server. Can we simply enter the URL to the font on our server, would that work? Thanks.

Sorry for the late response 🙈
It must be an url to a css which includes fonts.


Update composer.json

Builds are passing on 7.1 so let's not require 7.2
BTW that's super cool what you did here

Hello @sanmai,
Thank you very much for your contribution and generous compliment. I hope you have been able to compile and run the library in this initial state. If you have any problem with both the extension and the library, I will be happy to assist you.
See you. =D
PS: This is my first project on Github, so I still have a lot to learn.


[FEAT] Standardized Deprecation Protocol

:bulb: Feature request
Feature Name

Standardized Deprecation Protocol
The Desired Behavior

[ ] Decide and document the number of versions between a symbol's deprecation and its removal
[ ] Deprecation messages should contain the version that the symbol was deprecated and the version that it will be removed
[ ] Release script that will fail the pipeline if any symbols that are marked for removal in that release still exist in the public API

Your Use Case

As an app dev, I want to know when a symbol will be removed.
As a maintainer, I don't want to forget to remove deprecated symbols.

@damienwebdev So 3 minor versions in pre-release? How about post v1, every major?

@griest024 that strategy sounds good!


Edited the readme file to correct the website to freecodecamp.org (from freeCodeCamp.org)

The website is freecodecamp.org and not freeCodeCamp.org because a website is always in small letters, so I corrected it in the readme file.

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Thank you, but that is the intended way


AssertionError

I receive this message when running forwarder.py
Traceback (most recent call last):
File "/Users/myusername/Desktop/telegram-chat-forward/forwarder.py", line 77, in
assert forwards
AssertionError
What could it be? Thank you!

Hello,
I also got a similar message after running the script for the 3rd time
Traceback (most recent call last):
File "forwarder.py", line 6, in
from telethon.tl.patched import MessageService
ModuleNotFoundError: No module named 'telethon'


Add rangeSeparator to Russian l10n

A little addition to Russian locale
Flatpickr.l10ns.ru.rangeSeparator = " по ";

Also if it's possible, you could add something like "rangeFrom" to all locales -
so it would look like this:
"From 2017-05-01 to 2017-06-01"

@Onefivefournine hi. There should be a new plugin released soon with much more advanced range settings and so on. Please take a look at https://github.com/chmln/flatpickr/issues/584#issuecomment-289295697


Docker Hub repository name
dgageot/flamegraph-extension
Terms of services

[X] I accept the term of services

/validate

/validate

/validate

/validate


should this be there?

I compiled the following contract (which does a bubble sort)
def Main() -> list:
    nums = [775, 885, 105, 315, 456, 728, 150, 264, 837, 923, 714, 669, 824, 421, 136, 469, 76, 588, 920, 710, 576, 992, 146, 265, 182, 110, 971, 298, 932, 595, 895, 313, 793, 666, 8, 738, 489, 652, 506, 471, 397, 848, 693, 680, 204, 876, 242, 799, 891, 228]
    swapped = True
    while swapped:
        swapped = False
        for i in range(len(nums) - 1):
            if nums[i] > nums[i + 1]:
                # Swap the elements
                tmp = nums[i]
                nums[i] = nums[i + 1]
                nums[i + 1] = tmp
                # Set the flag to True so we'll loop again
                swapped = True
    return nums

Note how there seems to be a range specific error message encoded in the NEF file which doesn't seem to be used when executing the contract. This means the contract file is larger than needed to be and we pay for that when deploying.

This happens because we didn't start to implement code optimization. There are some other cases that more code than necessary is generated, for example:
example_list[2] = 1

The compiler adds code for checking if the index is a negative number even though it's a literal value that we know that's not negative.
Currently, the compiler is generating the smart contract to behave the same way as expected in Python, not the most optimized code.
I'm going to start working on code optimization this month.

👍


Use argv[0] instead of macro PROGEXECNAME

the first argument (argv[0]) always exists and is the name of the binary/path to the binary that was run.
for example if I run a program like this: ./prog, argv[0] will be ./prog.
and if it is run like this:/path/to/prog, argv[0] will be /path/to/prog.

Thanks!


Installed version displayed twice in the Updates dashboard

Got my latest version in the Updates overview twice:

Got a new version pending 2021.4.18 so that might be in the way

Ah, actually have 2 entries in the database:
29	2021-05-21 17:55:58	2021-05-21 17:56:18	2<IP_ADDRESS> c65e2c0ab1ff	1
28	2021-05-21 17:55:58	2021-05-21 17:55:58	2<IP_ADDRESS> c65e2c0ab1ff	1

Interesting. It is not supposed to be possible that two identical entries are created. If someone is experiencing the same problem, the logs at the time of the update would be helpful.

Interesting. It is not supposed to be possible that two identical entries are created. If someone is experiencing the same problem, the logs at the time of the update would be helpful.

@adriankumpf,
this happened to me when I initially setup my TeslaMate installation.. but I just removed the faulty entry and it never happened again.

29	2021-05-21 17:55:58	2021-05-21 17:56:18	2<IP_ADDRESS> c65e2c0ab1ff	1
28	2021-05-21 17:55:58	2021-05-21 17:55:58	2<IP_ADDRESS> c65e2c0ab1ff	1

@fatbasstard,
just remove the entry with ID 28 and it should look good again 👍

I am temporarily closing this until more information is available or someone else reports back with this bug.


[Event Request] codeunit 64 "Sales-Get Shipment" - OnBeforeSetSalesHeader

Please add new event in codeunit 64:
[IntegrationEvent(false, false)]
local procedure OnBeforeSetSalesHeader(var SalesHeader: Record "Sales Header"; var SalesHeader2: Record "Sales Header"; var IsHandled: Boolean)
begin
end;

procedure SetSalesHeader(var SalesHeader2: Record "Sales Header")
var
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeSetSalesHeader(SalesHeader, SalesHeader2, IsHandled);
    if IsHandled then
        exit;

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. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 47990.


fix hash documentation (28 vs 32 bytes)

closes #1588

this PR triggered a property test failure which turned out to be caused by a hash conflict (in testing we use a short hash that has only four bytes). we generated two different transactions with the same ID, which then destroyed a UTxO. I've added a commit to this PR that just adds some better logging to this test failure.


ER: remove discovery backend dependency

Hi,
I have an enhancement request: remove discovery backend dependency (or at least make it optional).
Adding backend requirement makes swarm installation a big pain.
(by backend i also mean adding a file/list of nodes - which might not be known when the cluster is created).
I think that the discovery backends are not necessary... The agents should connect to the manager and not vice versa...
A much simple way would be:
The agent should be launched with the manager address.
the agent access to the manager and registers itself...
heartbeats are being sent from the agent to the manager so the manager will know when the agent disconnected and vice versa.
The manager can push notification to the agent (socket.io etc...)
the agent listens on some port - where one can change it's manager configuration (in case something bad happens to the manager).
Again - installing discovery backend just for installing swarm is really problematic...

Another reason why this is a better approach is the ports issue  - currently agents needs to have some ports open. It would be best to avoid such thing if possible.

Closing due to lack of activity. Please reopen if you wish to continue discussing it.
Quick note -- this will not be on the roadmap of Swarm.


⚠ Bofrost.de has degraded performance

In dc2887c, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1258 ms

Resolved: Bofrost.de performance has improved in a59d66e after 6 minutes.


Show me defects for only what I'm working on by default; but let me switch via settings/configurations

Today, we will show defects in both the SARIF Viewer and Problems Pane for all analyzed files. This could be a bit overwhelming depending on the total number of defects in the built directory + the ruleset selected.
It would be more actionable/inviting to onboard users onto this new workflow if the analysis results were focused on the opened files. Just to clarify, this would not be on just the active file as this would cause a lot of churn in the SARIF Viewer/Problems pane when people switch files frequently.

The most canonical implementation would be to put this feature in the filter dropdown. A new category called "Location" with a single checkbox called "Only Open Documents". @HenokAddis sounds reasonable?

We discussed this yesterday and the understanding I left with is that this is not required prior to releasing to customers. We should see what their feedback is as we scale up and implement this based on their responses.
This is not cut, just tabled until broader adoption and feedback to reach the best experienced/design.


Parameters for my program.

Hi,
I want to call my program with parameters but i have an error.
How can I use my program like this without this error ?
$ cam2pcd -o file.pcd
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::program_options::unknown_option> >'
  what():  unrecognised option '-o'

Thanks

Resolve with a custom CmdLineOpts in my projects.


library shares composer package name with SOAP library

I know this is just an example library for making use of the REST API, but it shares the same package name in its composer.json file as the SOAP library https://github.com/avadev/AvaTax-Calc-SOAP-PHP.git (and indeed Packagist gives that one precedence).  Is it worth giving this one a different name (like avalara/avatax-rest) so it can exist in Packagist separately or is it your opinion that this is only example code?

Opened a pull request for this. I would like to be able to use composer without specifying the repository location to identify between the two.

Hey @anyarms - is this library still being maintained? :)


Remove Scholar Ruin II Weaving Suggestion

Remove the Scholar suggestion regarding Ruin II weaving as it is no
longer accurate with the changes made to the job in Shadowbringers.
The module is detrimental to players trying to analyze their fights
currently because it overwrites the existing Weaving module that
otherwise explains poor weaving, and gives misinformation that it is
suboptimal to use Ruin II in a fight unless moving.
Signed-off-by: Panic Stevenson<EMAIL_ADDRESS>

I'm not sure removing the module outright would be a good change. Weaving using Ruin II and Biolysis is very good for keeping up DPS – removing the module outright would be bad. It would be better to revert it to a default weaving suggestion.

Removing the module allows Scholar to inherit the default weaving suggestion instead of using its custom one:

The issue with Biolysis is resolved with https://github.com/xivanalysis/xivanalysis/pull/559.

I'm sorry, I did go back to edit my message a bit – I'm very sorry if it was missed. I'm currently discussing with a few people from the balance to figure this out, but there may still need to be custom logic for isBadWeave if biolysis is indeed introducing a delay.
If you'd like to hop on the discord channel, I'd love to discuss this with you so we don't duplicate efforts.

Discussed the changes with @nonowazu offline.
Closing in favor of https://github.com/xivanalysis/xivanalysis/pull/562.


azcopy sync command does not support folder deletion

Even though the --delete-destination parameter of azcopy sync is set, a folder that is not in the source is not deleted from the destination. I don't know if this is intended, but I think the user has to manually delete the folder. Any updates?

It was already confirmed as an issue that was raised, so I ended it. It would be nice if the function was added.


HA Energy monitoring?

IS there a way for the integration to provide energy usage to the new Energy Monitoring in HA?

if someone puts in a PR then sure. The 'pychonet-2.0' branch will (should) create sensors for any supported ECHONETLite object, so in theory it could be built upon that.
Not going to be me sorry as the only ECHONET lite object I have to play around with is the HVAC.

I haven't looked at the new Energy Monitoring API but I have been playing with the data my heatpump returns. One of the api call returns the total consumed KWH in 100WH increments. It's not quite instantaneous but it could be possible to interpolate the 100WH increments to try figure out an instantaneous rate when it's on.

Energy usage is actually configured with energy (KWH) usage not power readings (KW), which I had originally assumed, despite the name...

The plus side of this, is that the used energy is returned (at least on my models)  in 100Wh increments

So I plan on looking this up to long term energy statistics as well!

I played around with the energy module in the 'moekadenroom' emulator, but i think you need to combine a number of EPCs together to come up with the energy readings..
That 0x85 value is probably the best best as it is an enduring value...
The new library should be able to expose any ECHONETlite values as sensors...

Just about, unfortunately 0x85 wasn't mapped in pychonet to a handler. PR incoming :)

https://github.com/scottyphillips/pychonet/pull/6

@khcnz will be taking over this project soon at this rate...

I'm very happy being a supporter not a owner! I think we can close this issue now.
@dmshimself presuming you have a mitsubishi heatpump and it implements the correct codes, then if you delete and re-add your device after 2.0.11 is merged you'll have a cumulative energy sensor you can utilize with the new HA energy monitoring system.

Nice :-)  I'm looking forward to giving that a go.  Really appreciate the effort

The new integration burst into life with the 3 echonet entities working.  I'm gussing that as I cannot see anything else, then either 2.0.11 hasn't merged yet or my mitsubishi ducted system hasn't got or isn't configured with whatever is needed for the energy monitor to show.
The HA core log shows the usual warning abut the integration not being one supported by HA, but I cannot see a version displayed.  I downloaded it about an hour ago.  Is there a way can can see what version is installed?
If it is 2.0.11, is there something I can put into AC installer terms to ask the company that did the install to come back and do whatever to let this energy sensor burst into life?

Do you install it manually or through HACS? HACS doesn't have those changes published yet.
If you manually installed it from the master branch by downloading the code you can double check it worked by seeing if you have a manufacturer listed on the device page

Alternatively If you also enabled debug mode for echonet the restart:
custom_components.echonetlite: debug
custom_components.echonetlite.sensor: debug
custom_components.echonetlite.climate: debug
custom_components.echonetlite.select: debug
you'll want to look for this in your logs
2021-09-07 17:58:18 DEBUG (MainThread) [custom_components.echonetlite.sensor] {'instance': {'host': '<IP_ADDRESS>', 'eojgc': 1, 'eojcc': 48, 'eojci': 1, 'getmap': [128, 160, 176, 129, 161, 130, 131, 163, 179, 164, 133, 165, 134, 136, 137, 138, 154, 139, 171, 187, 157, 158, 190, 143, 159],
and you need to have a value 133

I installed manually as per the current docs and I do indeed have manufacturer listed on the device page, so thats good.  The debug idea sounds interesting, but when I configure echonetlite or look through the contents of its folder, I cannot see how to set this debug up.  Could you do me the favoour of pointing to me how to set that up?

Add something like this to your configuration.yaml file (not part of econet)
logger:
default: warning
logs:
custom_components.echonetlite: debug
custom_components.echonetlite.sensor: debug
custom_components.echonetlite.climate: debug
custom_components.echonetlite.select: debug

Perfect - thanks for that.  I get the data and I see no sign of a 133 as shown below :-(  Can I pose a general question.  Does this mean this Mitsubishi doesn't have this feature at all or could it be an option the installer didn't configure or one that I didn't know I needed to buy?  The installer was very helpful and if I know what to ask for, I might get a good result.  I know I coild put something like a Shelly EM in, but I'd like to see how far I can take this without.
2021-09-08 21:39:12 DEBUG (MainThread) [custom_components.echonetlite] Plaform entry data - {'instances': [{'host': '<IP_ADDRESS>', 'eojgc': 1, 'eojcc': 48, 'eojci': 1, 'getmap': [128, 160, 176, 129, 130, 131, 179, 134, 136, 137, 138, 187, 157, 158, 143, 159], 'setmap': [128, 129, 143, 160, 176, 179], 'uid': '0000060104a0c9a0fffe095236013001', 'manufacturer': 'Mitsubishi'}]}

I think that's all but guaranteed that your unit doesn't support it and there is nothing you can do about that (unless perhaps they are firmware upgradable but i've never heard of that). My units are mitsubishi AP series wall units which are a 'newish' model.

Mine is 12 months old, but living in NZ we don't always get the latest gear here.  I really appreciate the guidance and it looks as though I'll be going along the Shelly route.

hey @khcnz , are you happy with your energy readings from the heat pump?
Mine seem to be way too low on 2 AP series heatpumps. (50-100W even on full blast)

Yea the readings are in Watt Hours not Watts. So you should see the cumulative number jumping around 100WH every few mins or so. If it was to jump 100WH every 120 seconds that would equate to 3KW running. Watt Hours are a measure of the total energy usage (not instantons) and is what HomeAssistant needs for it's energy tracking feature also.
I had a small console app looping and retrieving the value in a loop with 10second delays and I was getting results like this which shows the cumulative counter going up 100Wh in approx 84 seconds

hehehe, yeah. I was converting to W :D
Mine goes up 100W every hour or so.

Almost looks like it only shows the indoor unit consumption only :(
Do you have that script somewhere so I could play with it?

I haven't converted it to the new async but this might give you enough to go on along with the new async example in the pychonet
import mitsubishi_echonet as mit
import time
from datetime import datetime

unit = mit.HomeAirConditioner(netif="ip address here")
lastPowerReading = unit.getCumulativePowerReading()
lastTimeReading = datetime.now()

while True:
    time.sleep(10)
    nextPowerReading = unit.getCumulativePowerReading()
    nextTimeReading = datetime.now()
    print(f"Total Cumlative Usage: {nextPowerReading}Wh")
    print(f"Period Cumulative Usage: {(nextPowerReading-lastPowerReading)}Wh")
    print(f"Av Instant Power: {(nextPowerReading-lastPowerReading)*60*6}W")
    print(f"Time Delta: {(nextTimeReading - lastTimeReading)}s")
    lastPowerReading = nextPowerReading
    lastTimeReading = nextTimeReading

Oh that code was slightly wrong but i can't find the example i had corrected, it should be storing the last time the value changed, and using that to calculate the number of seconds between updates to get the average power.

My unit goes up by 100Wh about every two hours when off

Mine only goes up when on.
and then very slow even on full blast.:(
On Mon, 13 Sept 2021 at 13:44, khcnz @.***> wrote:

My unit goes up by 100Wh about every two hours when off
[image: image]
https://user-images.githubusercontent.com/130233/133011977-c3a046ad-dc05-48ce-b3fc-01849ad7d185.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/scottyphillips/echonetlite_homeassistant/issues/31#issuecomment-917769835,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZXJMSCDWF6PYGV3ZO3NOTUBVJODANCNFSM5BR73U3Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I've just turned mine on to triple check, here you can see it is climbing fast after turning on

I'm not quite sure where it would be going wrong, I have AP series also, it really does look like from your example it isn't on and just consuming 100Wh every few hours.

out of curiosity, which AP series do you have?
I have one MSZ-AP35VGKD and one MSZ-AP42VGKD.
On Tue, 14 Sept 2021 at 10:44, khcnz @.***> wrote:

I've just turned mine on to triple check, here you can see it is climbing
fast after turning on
[image: image]
https://user-images.githubusercontent.com/130233/133165748-14c1e34d-c8cd-485c-b6f2-74ba40cfcfe3.png
I'm not quite sure where it would be going wrong, I have AP series also,
it really does look like from your example it isn't on and just consuming
100Wh every few hours.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/scottyphillips/echonetlite_homeassistant/issues/31#issuecomment-918638093,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZXJMRHM4FUTCGD3GHT4ATUBZ5GVANCNFSM5BR73U3Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

One MSZ-AP25VGKD that is standalone internal unit and exterior pump and then one multi-unit with one exterior pump and internally 1x MSZ-AP50VGKD and 4x MSZ-AP22VGKD
Oh, I've been looking at this a little more, I can see on the multi unit all the heatpumps have energy graphs that seem to go up in the correct amounts when the unit is on, but on the standalone MSZ-AP25VGKD it is not, and seems to go up a small amount like your screenshot. I'll take a deeper look into this device tonight.

Maybe those heatpumps really use that little energy?
lol
On Tue, 14 Sept 2021 at 12:06, khcnz @.***> wrote:

One MSZ-AP25VGKD that is standalone internal unit and exterior pump and
then one multi-unit with one exterior pump and internally 1x MSZ-AP50VGKD
and 4x MSZ-AP22VGKD
Oh, I've been looking at this a little more, I can see on the multi unit
all the heatpumps have energy graphs that seem to go up in the correct
amounts when the unit is on, but on the standalone MSZ-AP25VGKD it is not,
and seems to go up a small amount like your screenshot. I'll take a deeper
look into this device tonight.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/scottyphillips/echonetlite_homeassistant/issues/31#issuecomment-918675928,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZXJMTKTGBKH6UMPGTDQ6LUB2GZNANCNFSM5BR73U3Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

One MSZ-AP25VGKD that is standalone internal unit and exterior pump and then one multi-unit with one exterior pump and internally 1x MSZ-AP50VGKD and 4x MSZ-AP22VGKD
Oh, I've been looking at this a little more, I can see on the multi unit all the heatpumps have energy graphs that seem to go up in the correct amounts when the unit is on, but on the standalone MSZ-AP25VGKD it is not, and seems to go up a small amount like your screenshot. I'll take a deeper look into this device tonight.

khcnz, did you ever find a solution to this? I've noticed the same issue as yourself with that model.
I presume that this might be a datalogging issue on the device itself rather than something that can be solved with the script?

Hi,
The official app has added energy monitoring. And based on that it looks like some units report every 550Wh while other units report every 100Wh.

Hi,
The official app has added energy monitoring. And based on that it looks like some units report every 550Wh while other units report every 100Wh.

Yeah but the energy usage that is reported or interpreted is way too low, my 9kwh standalone used less power than my NAS today according to home assistant.
I'm guessing it is a problem on the mitsubishi end, I tried playing around with Pychonet myself yesterday but I'm just not familar enough with the coding language to get it going properly.

You can create a template sensor like this:
{{ states("sensor.office_heatpump_measured_cumulative_power_consumption") |float*5.75}}
This will give you the real energy usage of the Heatpump

"sensor.office_heatpump_measured_cumulative_power_consumption") |float*5.75}}

Thanks for the response, I will use this and see how it goes - just so I learn something here why the multiplication factor of 5.75?
Really appreciate you getting back to me.

I got it from the official Mitsubishi app.
On Sat, Oct 26, 2024, 11:16 PM Zerosignal84 @.***>
wrote:

"sensor.office_heatpump_measured_cumulative_power_consumption")
|float*5.75}}
Thanks for the response, I will use this and see how it goes - just so I
learn something here why the multiplication factor of 5.75?
Really appreciate you getting back to me.
—
Reply to this email directly, view it on GitHub
https://github.com/scottyphillips/echonetlite_homeassistant/issues/31#issuecomment-2439475895,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZXJMUDAF2W3QME5OQRKQTZ5NTWLAVCNFSM6AAAAABQTFUH3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZGQ3TKOBZGU
.
You are receiving this because you commented.Message ID:
@.***>

Mitsubishi Electric in New Zealand just released this for the Melview app in September.
https://www.mitsubishi-electric.co.nz/materials/Controllers/Manuals/Wi-Fi/1_Operation/Guide_Wi-Fi_Energy_Monitoring.pdf
Does not seem applicable to the Australian version just yet.

Basically each unit reported by some Heatpumps is 575wh while for others is
100wh.
Echonet can not make that distinction and actually reports 100wh for all
devices.
On Sat, Oct 26, 2024, 11:18 PM Liviu Sas @.***> wrote:

I got it from the official Mitsubishi app.
On Sat, Oct 26, 2024, 11:16 PM Zerosignal84 @.***>
wrote:

"sensor.office_heatpump_measured_cumulative_power_consumption")
|float*5.75}}
Thanks for the response, I will use this and see how it goes - just so I
learn something here why the multiplication factor of 5.75?
Really appreciate you getting back to me.
—
Reply to this email directly, view it on GitHub
https://github.com/scottyphillips/echonetlite_homeassistant/issues/31#issuecomment-2439475895,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZXJMUDAF2W3QME5OQRKQTZ5NTWLAVCNFSM6AAAAABQTFUH3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZGQ3TKOBZGU
.
You are receiving this because you commented.Message ID:
@.***
com>

Thanks Droopanu.
For those interested in the Melview energy page, it is located here https://app.melview.net/energy.html
It will not load for my devices but I can force it to but no data is showing.

I'm in New Zealand and I have that version on the app. It shows me only the
yellow bars (indicative energy view) for all my units.
But for someunits I get the 100wh units while for others I get the 525wh
units...
On Sat, Oct 26, 2024, 11:24 PM Zerosignal84 @.***>
wrote:

Mitsubishi Electric in New Zealand just released this for the Melview app
in September.
https://www.mitsubishi-electric.co.nz/materials/Controllers/Manuals/Wi-Fi/1_Operation/Guide_Wi-Fi_Energy_Monitoring.pdf
Does not seem applicable to the Australian version just yet.
—
Reply to this email directly, view it on GitHub
https://github.com/scottyphillips/echonetlite_homeassistant/issues/31#issuecomment-2439480000,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZXJMSHJ457XAC4SSBFR5LZ5NUWNAVCNFSM6AAAAABQTFUH3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZGQ4DAMBQGA
.
You are receiving this because you commented.Message ID:
@.***>


Can't see any assembly code for a self-hosting compiler

A self-hosting compiler involves writing a rudimentary compiler for a language X(Here C) in another language (Suppose assembly), I can't find any assembly or any other language used for compiling a code . I have been googling my wits out to find at least a simple guide to write a compiler in assembly for C language . Your blog is the closest one I found but still I don't see any .

it needs to be bootstrapped with an existing compiler, once that is done you can use 8cc to compile 8cc and can forget about the existing compiler. that is what is meant by self hosted.

Here's an idea.  Write a compiler for a very simple, minimal language in asm.  Then use that language to write a compiler for a slightly more complex language with more abstractions.  Then write your C compiler in that.  The way 8cc can be bootstrapped, is by using gcc or clang, since those already exist.  You could also ask this guy.

Thanks Elronnd. I knew this way , was just looking for assembly code(using which a c compiler has been implemented) to read . There are a lot of self  hosted compiler code but I could not find in an assembly lang.

@0decimal0 Your definition of self-hosting is not the one I have seen for years [https://en.wikipedia.org/wiki/Self-hosting_(compilers)](Wikipedia definition and history of the term). Bootstrapping is the name of the process for getting a compiler to run on and for a target machine. Sometimes people bootstrap starting with assembly, others start by cross-compiling.


combined, comprehensive kubernetes views

This is an umbrella issue:

[x] #1444 add DaemonSets (released in 1.3)
[ ] #2239 add StatefulSets
[ ] #2571 add CronJobs
[x] #2552 combined view of k8s controllers
[x] ~enable searching/filtering by controller type when in combined view~~
[x] #2670 get rid of type selector
[x] #2661 get rid of ReplicaSets (at least from the UI)

 Scope Kubernetes View

enable searching/filtering by controller type when in combined view, and get rid of type selector

The current convention dictates that we use the search term controller_type:daemonset or something similar. Maybe node_type:? type:?

Whoops accidentally closed

The current convention dictates that we use the search term controller_type:daemonset or something similar. Maybe node_type:? type:?

Let @ekimekim decide.

I can already search by node type since its part of the metadata fields:

In fact, that is one of the examples. @ekimekim Maybe I am missing the requirement here?

No, it was me and @rade missing that this was already possible.

Referencing here for visibility: https://github.com/weaveworks/scope/issues/2693
Feature request to have a Volumes topology that connects to the pods/containers which access that volume. Shouldn't be too hard, and seems useful.

Shouldn't be too hard,

It's harder than you might think. See my comment in the issue.


Aligning multiple processing streams

Hi @Lestropie,
I  have a grand plan to run a multimodal analysis using T1 information (particularly cortical thickness and gray matter density), rsFMRI, and DTI/tractography using the HCP MMP1 atlas.  To that end, my analysis plan looks like this:

BIDS-Apps/Freesurfer's recon-all, particularly for quality metrics and and any future inquiries I may have.
fMRIPREP, loading in the pre-run Freesurfer.
XCP Engine (https://github.com/PennBBL/xcpEngine) for atlas-based ANTs cortical thickness on the fMRIPREP'd T1 images and atlas-based functional connectivity using the fMRIPREP'd rsFMRI and the XCP post-processed T1s (for coregistration).
DWI preprocessing and connectome construction using MRtrix3_connectome.

My rationale for this ordering is to minimize duplicate (and potentially disparate processing) streams, particularly for the T1s which will get processed with all of these steps (ANTs cortical thickness in XCP, 5ttgen in MRtrix3) .
So here's my question: Is there a way for me to pipe the pre-run Freesurfer (for parcellation and labeling purposes) and the fMRIPREP preprocessed T1s (along with the brain mask) into MRtrix3_connectome as the target for 5ttgen or will I need to follow some instructions (like the BATMAN tutorial) using these images apart from the docker environment?
If I have to do that, if I place those images in the appropriate derivatives folders, will MRtrix3_connectome detect the existence of those files and not try to rerun the anatomical processing stream?
I hope that's clear enough what my question is.
Thanks

Hi @araikes,
Currently there's no way of exploiting data processed using other tools as input to this script. There is of course nothing stopping you from creating a fork of the tool and making tailored modifications specific for your own purposes.
Longer-term, enabling this sort of inter-application data utilisation is one of the principle goals of BIDS Derivatives. There needs to be a robust definition of how such data is to be stored by one application in order for another application to be able to read and utilise such with any confidence. While you could make specialised modifications to dump data from one specific tool in a specific location in a specific format and for some other tool to then read from that location, it would not be a generalised solution. Probably once BIDS derivatives is merged into the main specification, I would then look into getting this tool to scan the output directory for pipelines that may have provided a pre-processed T1 and possibly a parcellation; but unfortunately it's not something I can prioritise right now.
If you're interested in making modifications yourself I can certainly point you in the right direction with respect to the how and where.
Cheers
Rob

Hi @Lestropie
Thanks for the response. I kind of figured that, at least for the time being, it would be a somewhat hacked together at best.
As I have time over the next little bit, I'll fork the repo and see if I can figure out a way to use other preprocessed outputs.
Thanks for the great tool.

One other question:
Is there a non-hacky way to do multi-session processing? Currently, it tells me that it can't find the dwi/fmap folders.

Currently the script is simply hard-wired assuming one session per subject. Navigating the BIDS input directory to determine e.g. multi-session structure is something I'd like to add, I just hadn't explicitly listed it until now (#51). So it's possible to have a structure that adequately conforms to BIDS but the script won't accept; the former is much more difficult technically than the latter.
You can just create a unique subject ID per session and run the script that way.

@Lestropie I'll hack my way around it and if I find some time I'll try to edit the code to use pybids to grab the structure.
Thanks

Hi @Lestropie,
I have a kind of janky version of your script that will allow for longitudinal studies as well as reusing fMRIPrep pre-processed T1s. It certainly can be improved to use pybids, but it appears serviceable (running it right now and it's running eddy currently).
Here's my current question: How usable is this script without mtnormalize functionality in it? If I run it to completion on my subjects and run the group steps, is it going to give me invalid/unusable findings?
Thanks

The functionality of the script following use of the group-level analysis is almost equivalent to how inter-subject intensity normalisation was achieved prior to creation of the precursor to the mtnormalise command. So it's no more invalid than every AFD analysis that was done prior to the creation of that method. It's simply a different mechanism being used for intensity normalisation, and each has their pros and cons.
I've had a manuscript accepted that demonstrates the necessity for appropriate connection density normalisation, and another I've drafted and am waiting for feedback on that describes and proves it in more detail. So hopefully those will clarify things soon. Eventually I'll incorporate mtnormalise in here, but it'll take a little more trickery to do it right, and that will probably wait for when I write a publication on this tool.
Ultimately the cross-subject variance within structural connectome data due to the inherent poor reproducibility of tractography probably swamps any potential variance from the intensity normalisation method.

Hi @Lestropie,
It's good to know that I can use those outputs. I'm very broadly speaking new to MRtrix so understanding that AFD from this script will allow me to achieve what I'm looking for. My question was originally borne out of the code comments you had as well as the BATMAN tutorial.
Thanks again for all the help.


Add wheel conditional dependencies

Bumping bugfix version to 1.3.1.
Previously, if genty was installed on Python 2.6 via a wheel
that was generated on Python 2.7+, the ordereddict dependency
would not get installed, because it was not included in the
bdist_wheel metadata.
Add the conditional dependency so that this will be installed in
the future.

Verified that @jmoldow has signed the CLA. Thanks for the pull request!

+2


[INSTALL] new NCEPLIBS-bufr version 12.0.1

Which software in the stack would you like installed?
A new version of the NCEPLIBS-bufr library is now available from https://github.com/NOAA-EMC/NCEPLIBS-bufr/releases/tag/v12.0.1
What is the version/tag of the software?
v12.0.1
Which machines would you like to have the software installed?
This library needs to be installed on WCOSS2 (cactus and dogwood) as well as various HPC machines including Jet, Hera, and possibly others where there's already an installation of an earlier version of the library.  This is a quick-update release at the request of @rmclaren, but if there are still earlier versions of the library available on any platform, please leave them there in order to give users time to transition on their own schedule.
Please also note that this is a follow-on to #626, given that the previous version 12.0.0 of this library is still waiting to be installed on WCOSS2.
Any other relevant information that we should know to correctly install the software??
Please see https://github.com/NOAA-EMC/NCEPLIBS-bufr/blob/develop/README.md.  The -DMASTER_TABLE_DIR option does not need to be specified (you can just let it default to path1), but the -DENABLE_PYTHON=ON should be included for any machines on which it is currently available for earlier versions of the library.
Additional context
Full release notes are available from https://noaa-emc.github.io/NCEPLIBS-bufr/md__home_runner_work_NCEPLIBS_bufr_NCEPLIBS_bufr_bufr_docs_ReleaseNotes.html

@Jeff Ator - NOAA Federal @.***> I will send bufr/12.0.0 to
NCO today. I noticed that you changed the bufr tag name by eliminating the
lib name. Is that what you planned to do?
On Fri, Sep 15, 2023 at 12:01 PM Jeff Ator @.***> wrote:

Assigned #778 https://github.com/JCSDA/spack-stack/issues/778 to
@Hang-Lei-NOAA https://github.com/Hang-Lei-NOAA.
—
Reply to this email directly, view it on GitHub
https://github.com/JCSDA/spack-stack/issues/778#event-10385198792, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKWSMFAWTOZV3KDMA7IXC7LX2R3WPANCNFSM6AAAAAA42AS4IM
.
You are receiving this because you were assigned.Message ID:
@.***>

This will go on the RDHPC & other platforms (not talking about WCOSS2/Acorn here) after the spack-stack-1.5.0 release, presumably in the first week of October.

I'll add 12.0.1 to the recipe shortly.

@jeff Ator - NOAA Federal @.***> I will send bufr/12.0.0 to NCO today. I noticed that you changed the bufr tag name by eliminating the lib name. Is that what you planned to do?

Yes this was intentional, per a previous discussion in library issue 516.  So all good!

Please include<EMAIL_ADDRESS>in the spack-stack-1.5.1 configuration. Thanks!

Please include<EMAIL_ADDRESS>in the spack-stack-1.5.1 configuration. Thanks!

Please create the PRs for develop, I will bring it over to the release-1.5.1 branches. Thanks.

Please include<EMAIL_ADDRESS>in the spack-stack-1.5.1 configuration. Thanks!

Please create the PRs for develop, I will bring it over to the release-1.5.1 branches. Thanks.

Done:
https://github.com/JCSDA/spack/pull/330
https://github.com/JCSDA/spack-stack/pull/797

<EMAIL_ADDRESS>has been installed on all tier-1 platforms as far as spack-stack is concerned (RDHPC, JCSDA, EPIC, ...). We agreed that we can consider install requests as done once these steps are completed and that installation on wcoss2 by GDIT is handled elsewhere, therefore closing this as complete.


Issue with k8s.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/

This is a Bug Report

Problem:
At no point does this guide mention the package "kubernetes-cni", which is required for (at the very least, Kube-Router) network addons to work.
Proposed Solution:
Instruct users to dnf install kubernetes-cni during installation.
Page to Update:
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/

Additional Information:
I have been following the guide closely on installing kubeadm and then going on to set up a single control-plane cluster, selecting Kube-Router as the network addon, and at no point during any of the steps in the guide does it mention to install kubernetes-cni, Causing me to get stuck at "If your network is not working or CoreDNS is not in the Running state"
I spent quite a while searching through issues and logs until I heard about this package, and noticed it seemed important, moments after installing it the core-dns pod changed from pending to running.

At no point does this guide mention the package "kubernetes-cni", which is required for (at the very least, Kube-Router) network addons to work.

we prefer to not mention the kubernetes-cni package. currently it's a transitive dependency and should have been installed for you if you used rpm instead of dnf?
https://github.com/kubernetes/release/blob/master/build/rpms/kubelet.spec#L36
is that a dnf bug?
in the very near future kubernetes-cni will be removed and its contents folded into the kubelet package.
please continue the discussion if you have further questions.
/sig release cluster-lifecycle
/close


support ":paste" for pasting multi-line expressions

Same description as in https://youtrack.jetbrains.com/issue/KT-13319

@holgerbrandl, it's already supported by :paste or :p. Moreover you can use :help for print more information.
[1] :help
:quit or q                     quit the kshell
:load or l <path>              load file and evaluate
:type or t <expr>              display the type of an expression without evaluating it
:list or ls                    list defined symbols
:imports or i                  show imports
:help or h [command]           print this summary or command-specific help
:paste or p                    enter paste mode
:syntax {on | off}             syntax highlighting
:prompt [pattern]              customize prompt

You also can use :help prompt for example.

Thats's awesome. So much better than kotlinc REPL.
I've just added paste mode support to my "Send to Terminal" plugin (which is under jb review now), to write Kotlin in IDEA and eval in terminal REPL. Now we/I can do stuff like

Looks great! I know about your plugin, it is really useful.


Upgrade to netty-tcnative 1.1.33.Fork8

Motivation:
A new version of netty-tcnative was released with some important bug-fixes.
Modifications:
Bump up version.
Result:
Using latest netty-tcnative version

Cherry-picked into 4.0 (4b63ac95ae9d1dccf221103a4904c9177530c4e3) , 4.1 (06fcb569802da6be93ad30f6e75dacebdb1dd59b) and master (a5a0b3e1e4032e629be390d686148d42e573db0b)


how to download subtitles???

I would like to know how to download subtitles from the site. I tried to use tags that show how to download but this is giving error.
error: unknown option '--list-subs'
error: unknown option '--sub-lang'
could someone help ???
Thanks!

I'm using the following command to download a single Arabic subtitle for one episode:
cr-dl download --sub-lang arME --subs-only -o "{episodeNumber}.ass" "https://www.crunchyroll.com/ar/one-piece" --episode 959

I'm using the following command to download a single Arabic subtitle for one episode:
cr-dl download --sub-lang arME --subs-only -o "{episodeNumber}.ass" "https://www.crunchyroll.com/ar/one-piece" --episode 959