IcoMoon not giving me a woff2 to copy?

I tried following the directions in CONTRIBUTING.md, but IcoMoon doesn't seem to be giving me a woff2 file, just .eot, .svg, .ttf, and .woff. Am I doing something wrong?

Eh?? That's seriously odd, and it shouldn't have happened. :|
Uhm, I can't reproduce, and can't think of anything that would've caused this. Did you change any of the preferences in IcoMoon settings? (That shouldn't have affected anything, but I'm just trying to cover all ground, here).

Arch Linux, but I don't know why it would matter. Not to my knowledge, but I'll try the whole process again and see if I imported selection.json incorrectly.

No it shouldn't matter, you're right. Not sure why I asked now (my knee-jerk reaction to seeing weird shit is to ask questions).

Yeah, I don't know what I'm doing wrong, here's my selection.json, could you try importing it into IcoMoon and see if you can see anything wrong? https://gist.github.com/jacobmischka/fedf0753de7c9545c76242a44621ffc8
Thanks!

Wait, I know what it is. I completely forgot that IcoMoon only permits premium users to generate WOFF2 fonts... :\ Could you Gist the SVG for me?
Think I'm gonna have to rethink our procedure for updating the font...

Oh lol, sure: https://gist.github.com/jacobmischka/7e0be5e99a4edce56554bfe3098d384d
It's the icon for Rollup.
Thanks!

Thanks! Sorry about the inconvenience/confusion. :( Had I remembered WOFF2 fonts were premium-only, I definitely would've worded the contributor notes better.
I'll add it now.

No problem, also I forgot to mention the default filename is rollup.config.js, much like webpack's webpack.config.js.

Got it. =)
BTW, I'm just gonna take a moment to clean the file's geometry up in Illustrator. There're a lot of control points that can be left out, and I'm trying to keep the font's size as optimum as possible.
(Yes, I'm an meticulous, obsessive shithead. :') I make no apologies for knowing who I am, hahaha)

Sure that's fine, I just copied it from the site and changed the strokes to paths and changed the color, I take no pride in the icon :smile:

Nah you're right, mate. It's actually pretty common for font authors not to care about how geometry-heavy their icons are. I actually squashed 17 KBs out of a WOFF2 font simply by cleaning up geometry...


HIVE3 Computations issues with AEGOS-QC and accessing the genome

There are two major bugs that keep happening on HIVE3 for the computations.

If the nucleotide sequence is too big and is not shown on the NCBI page fully, it will say it cannot download sequences. That is because the sequences is not visible on the page and you have to customize the view for it. See this example.. I think this is the sole reason for why we are seeing "cannot download references" even though there is genbank and refseq information.

Regardless if I download the sequence or manually upload the genome or reads, I have been getting the last step (ARGOS-QC Post Alignment Quality Control) killed at 30%. It completes everything else up to the last step. It always kills at 30% and never a different percentage. It does not happen to all computations, but it is happening to most. Again this can happen regardless of how the genome or reads are inputted into the argos qc pipeline. I have been unable to pinpoint why it is doing this.

So I believe this is working now. I have had no issues running any computations today. I know that Vahan had done an update last week on HIVE3. For now I am going to close this, but I can reopen if the issue persists.


Supplementary tables & assay design

This PR has work on supplementary tables and assay design.

Apologies this is a bit of a behemoth. Now ready for review. Here's a summary of main changes...

To get a consistent view on which haplotype group a haplotype belongs to, I've added some code to the artwork_networks notebook to write out a file with group membership.
I've then modified the artwork_hapfreq_map notebook to use the network groups. This now properly accounts for haplotypes which carry a kdr allele but don't fall into one of the major haplotype groups, by adding a "other kdr" colour (black) to the pies and legend.
I've then added a supp_tables notebook which generates all the supplementary data tables:

supp_table_variants_missense.csv - all non-synonymous variants, suggest this becomes Supplementary Table 1.
supp_table_variants_tracking.csv - variants for tracking haplotype groups, suggest this becomes Supplementary Table 2.
supp_table_variants_all.csv - variants to take into account when doing primer design, suggest this is Supplementary Table 3.
supp_table_haplotype_panel.csv - some meta-information about the haplotypes, including which group we put them in, suggest Supplementary Table 4.
There is also supp_table_haplotypes_tracking.csv which has the actual haplotypes for the tracking variants. Not sure if this is needed.

Finally, there are some edits to main.tex, to consistify language, and also to tighten up the discussion on assay design.

Happy to discuss any aspect of course.

This all looks great, the tbl_variants_missense with all the isoforms is a particularly a great idea.
Just on thing caught my eye, and that was within the figure legend (line 398) wt is italicised where as later in the text (line 443) it isn't. Was that intentional?

Thanks, no not intentional, was just being lazy, we should consistify. I
thought italics looked a bit better and matched italicisation of "kdr", but
happy to do either way. There's a couple of figures IIRC that would also
need updating if we italicize everywhere.
On Thu, 3 May 2018, 12:46 Chris Clarkson<EMAIL_ADDRESS>wrote:

This all looks great, the tbl_variants_missense with all the isoforms is a
particularly a great idea.
Just on thing caught my eye, and that was within the figure legend (line
398) wt is italicised where as later in the text (line 443) it isn't.
Was that intentional?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/malariagen/agam-vgsc-report/pull/164#issuecomment-386268634,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAq8QqwCfLtXIKWVWcgcFC7Ko_093bM8ks5tuu4rgaJpZM4ThW51
.

Took the liberty of italicizing "wt" throughout text and figures.


Running DeepSphere for regression?

Is there a version of DeepSphere that can run regression instead of classification?

Unfortunately, the loss used right now is for classification only. However, changing the loss should be  simple. We can help you to do this. What loss do you want to use?

Thank you. I want to use mean_squared_error.

As I am quite busy, I will not have the time to implement this before the 23. So if you need this very soon, you will have to implement it yourself.

I just implemented the l2 and l1 losses for regression in the multichannel branch...
https://github.com/SwissDataScienceCenter/DeepSphere/tree/multichannel
There is a notebook demo_regression.
https://github.com/SwissDataScienceCenter/DeepSphere/blob/multichannel/demo_regression.ipynb
Please test and let us know if you encounter any issue with the code.

Support for regression and multiple channels has been implemented in #31 (thanks @nperraud). Feel free to reopen or create another issue if needed.


Deploy to hex.pm

We would like to use your driver. Did you think upload it to hex.pm?
Thanks

Hi, ferigis.
Sure.
Right now I am busy uploading it to coon. As soon as I am finished I'll add it to hex too.

great! thanks!

@comtihon
Quite a long time, and mongodb-erlang does not update to hex.pm.
And mongodb-erlang still use rebar, and by now, rebar3 is very great and we use rebar3 to replace rebar in many project. I think mongodb-erlang  should migrate to rebar3.
Every time I compile it using rebar3, it make a warning:
Package <<"rebar_ct">> not found. Fetching registry updates and trying again...

Change should be made.

I pushed versions of bson-erlang and mongodb-erlang from my forks to Hex now, I'll try to keep them up to date with the upstream versions.

Thanks!
For now mongodb-erlang is available in EnotHub.
I set up automatic deploying this repo to EnotHub on every new tag, so there will always be fresh version.

Ah, I'm super sorry, I pushed the client under the name mongodb_client at first, I've pushed a new version as mongodb_erlang now, which is the one I'm going to keep updated.


Fixed typo in description of core.local action

Self-explanatory - just a minor fix of the description (mistakenly refers to remote host)

Codecov Report

Merging #3198 into master will increase coverage by 0.09%.

@@            Coverage Diff             @@
##           master    #3198      +/-   ##
==========================================
+ Coverage   77.73%   77.83%   +0.09%
==========================================
  Files         433      433
  Lines       22395    22395
==========================================
+ Hits        17408    17429      +21
+ Misses       4987     4966      -21

Impacted Files
Coverage Δ

st2common/st2common/bootstrap/sensorsregistrar.py
80.58% <ø> (-4.85%)
:x:

st2actions/st2actions/scheduler.py
83.67% <ø> (-4.08%)
:x:

st2common/st2common/triggers.py
74.42% <ø> (-2.33%)
:x:

st2actions/st2actions/container/base.py
90.59% <ø> (-1.76%)
:x:

st2common/st2common/services/triggerwatcher.py
88.73% <ø> (-1.41%)
:x:

st2reactor/st2reactor/container/sensor_wrapper.py
72.62% <ø> (ø)
:white_check_mark:

st2api/st2api/controllers/v1/packs.py
90.12% <ø> (ø)
:white_check_mark:

...2reactor/st2reactor/container/process_container.py
42.92% <ø> (+0.46%)
:white_check_mark:

st2common/st2common/services/triggers.py
92.78% <ø> (+0.52%)
:white_check_mark:

st2common/st2common/models/api/base.py
91.22% <ø> (+0.68%)
:white_check_mark:

... and 9 more

Continue to review full report at Codecov.

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

Good catch :+1:


Bug: Some components change border radius when selecting examples

This is a weird one.
"New" badge on Tasks changes the border radius when selecting some examples on the homepage.
Tested on Brave and Chrome.
https://github.com/shadcn/ui/assets/38887390/be03e4e8-5b59-4c8b-b23b-462ffda35d6a

Same happens with the banner too! 🤔
https://github.com/shadcn/ui/assets/38887390/ab6aa63c-552a-44cf-857d-ff5804aefb40

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


Use jwtInterceptor to send the token as a request param?

I am using WebSockets and, for reasons that have to do with my back-end framework, can only use request params to send the token.  Is there a way to create a jwtInterceptor that will accomplish this, or is sending via header the only possibility?

Using this library, right now it's only possible to send it in the header.
However, you could easily implement it so that it uses the request params. You can change this line to use request.params instead of request.headers and that'd be it.
We'd be open to a PR if you want to make the header / param an option to the library :).
Cheers!

@mgonto This worked great!  Thank you so much.

Hey,
Would you care to send a PR so that we can make it configurable where to send the JWT, either header or request params?
Thanks!


Defaults not assigned when using compileAsync

What version of Ajv are you using? Does the issue happen if you use the latest version?
5.1.5 (latest)
Ajv options object

useDefaults: true,
loadSchema: (uri) => {
  return request.json(uri).then(function (res) {
    if (res.statusCode >= 400)
      throw new Error('Loading error: ' + res.statusCode);
    return res.body;
  });
}

JSON Schema

{
    "properties": {
        "foo": {
            "default": { "bar": 1 }
        }
    }
}

Sample data

{}

Your code

You can view the demo repro runkit here.
// Asynchronous: Bug exists

const validator = new Ajv({
    useDefaults: true,
    loadSchema: uri => {
        return request.json(uri).then(function(res) {
            if (res.statusCode >= 400)
                throw new Error('Loading error: ' + res.statusCode);
            return res.body;
        });
    }
});

validator.compileAsync(testSchema, true).then(validate => {
    const data = {};

    console.log('Async validate: ' + validate(data));
    console.log('Async data: ' + JSON.stringify(data));
});

// Synchronous: Bug does not exist

const validator2 = new Ajv({
    useDefaults: true
});

const validate2 = validator2.compile(testSchema2);
const data2 = {};
console.log('Sync validate: ' + validate2(data2));
console.log('Sync data: ' + JSON.stringify(data2));

Validation result, data AFTER validation, error messages
Sync validate: true
Sync data: {"foo":{"bar":1}}
Async validate: true
Async data: {}

What results did you expect?
Sync validate: true
Sync data: {"foo":{"bar":1}}
Async validate: true
Async data: {"foo":{"bar":1}}

Are you going to resolve the issue?
I'll try to look into it if I have time. I haven't looked at the codebase so I'm not sure if I will be able to hunt down the issue.

I just found out that omitting the second parameter from compileAsync, i.e. doing validator.compileAsync(testSchema) will make it work. I suppose we can close this as a non-issue.
I'm not 100% sure why this is the case though. The documentation says:

You can asynchronously compile meta-schema by passing true as the second parameter.

Maybe I don't fully understand what a meta-schema is, but how does this change things?

meta-schema is a schema that describes the schema itself. All draft-06 schemas should be valid documents according to draft-06 meta-schema. Meta-schemas ignore option useDefaults, as otherwise your schemas would be modified.

http://json-schema.org/documentation.html

Got it! Perhaps maybe we could add this in the documentation as well, because it's not exactly clear that meta-schemas should ignore useDefaults, and that setting the argument to true means that the schema is a meta-schema...
I interpreted that line as to compiling the meta-schema defined in $schema, rather than saying that compileAsync(schema) will consider schema to be a meta-schema.


Fix ili9341

Sometimes the display has artifacts. It seems it need some time after initial the controller.
Fix for issues #107

Thank you!


Failed to get link for weekend factor/map files

Expected Behavior

Hello I am running Lean CLI locally and am getting the following error (trace) messages in the console when running a lean cli backtest. Please let me know if they are expected and should be ignored, or a bug, or if need to do something different. I'm not sure if the fact they are weekend days is relevant. I don't have any code which request these files directly I believe.
I am running locally via the cli:
lean backtest project_name
Actual Behavior
The messages are:
20221031 23:28:55.204 TRACE:: Api.DownloadData(): Failed to get link for /Lean/Data/equity/usa/map_files/map_files_20221030.zip. Errors: File not found: equity/usa/map_files/map_files_20221030.zip
20221031 23:28:55.319 TRACE:: Api.DownloadData(): Failed to get link for

/Lean/Data/equity/usa/map_files/map_files_20221029.zip. Errors: File not found: equity/usa/map_files/map_files_20221029.zip

20221031 23:28:55.333 TRACE:: LocalZipMapFileProvider.Get(usa): Fetched map files for: 10/28/2022 NY

20221031 23:03:10.237 TRACE:: Api.DownloadData(): Failed to get link for /Lean/Data/equity/usa/factor_files/factor_files_20221030.zip. Errors: File not found:
equity/usa/factor_files/factor_files_20221030.zip

20221031 23:03:10.341 TRACE:: Api.DownloadData(): Failed to get link for /Lean/Data/equity/usa/factor_files/factor_files_20221029.zip. Errors: File not found:
equity/usa/factor_files/factor_files_20221029.zip

20221031 23:28:58.041 TRACE:: LocalZipFactorFileProvider.Get(usa): Fetched factor files for: 10/28/2022 NY

Potential Solution

Reproducing the Problem

System Information

Checklist

[ x] I have completely filled out this template
[x ] I have confirmed that this issue exists on the current master branch
[ x] I have confirmed that this is not a duplicate issue by searching issues

[ x] I have provided detailed steps to reproduce the issue

Note I am able to get equity data, for example:
20221031 23:36:36.714 TRACE:: ApiDataProvider.Fetch(): Successfully retrieved data for /Lean/Data/equity/usa/daily/drn.zip.
20221031 23:36:36.727 TRACE:: ApiDataProvider.Fetch(): Successfully retrieved data for /Lean/Data/equity/usa/daily/agg.zip.
20221031 23:36:36.738 TRACE:: ApiDataProvider.Fetch(): Successfully retrieved data for /Lean/Data/equity/usa/daily/jazz.zip.
20221031 23:36:36.752 TRACE:: ApiDataProvider.Fetch(): Successfully retrieved data for /Lean/Data/equity/usa/daily/psa.zip.

Note I am able to get equity data, for example:
20221031 23:36:36.714 TRACE:: ApiDataProvider.Fetch(): Successfully retrieved data for /Lean/Data/equity/usa/daily/drn.zip.
20221031 23:36:36.727 TRACE:: ApiDataProvider.Fetch(): Successfully retrieved data for /Lean/Data/equity/usa/daily/agg.zip.
20221031 23:36:36.738 TRACE:: ApiDataProvider.Fetch(): Successfully retrieved data for /Lean/Data/equity/usa/daily/jazz.zip.
20221031 23:36:36.752 TRACE:: ApiDataProvider.Fetch(): Successfully retrieved data for /Lean/Data/equity/usa/daily/psa.zip.

Hey @ari62! Welcome to Lean
It's expected behavior, it's unaware of the weekends and trying to serve an unexisting file, so it will fail. But nothing to worry about 👍 it will use the previous available file


The "All", "Favorites", and "Filter" buttons don't do anything on the "Speakers" page

I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

Tapping on any of these buttons seems to have no effect on the content displayed.
Expected behavior:

Since it's not possible to "favorite" or filter speakers (like you can with talks), I would not expect these buttons to exist.
Steps to reproduce:

On iOS, tap on "Speakers" at the bottom right, and tap on any of the mentioned buttons at the top of the screen.

removed in #30, we could update this issue to ask if anyone wants to implement favorites for speakers.

Thanks for the quick responses!

live update containing fix should be live. its not quite perfect yet, but is at least persisting locally and to the backend as able.

No intention to add favorite/filter for speakers tab.


C_CPP : Coin change Problem (DP Algorithmic Approach)

Description
Solving the Coin Change Problem (Dynamic Programming) : Given an amount 'n' and an array of coins, find out how many combinations of coins can be computed that amount to 'n' [DOCUMENTATION or VIDEO]
Domain
C/CPP
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

/assign

/assign


Encryption v2

Adding authenticated encryption support.
Behavioral Changes

Ranged Download (DownloadStreaming, DownloadContent)

If client is configured with client-side encryption options, first fetches properties to determine the appropriate range adjustment, then does the ranged read.
This does not affect other downloads that use this under the hood
Pro: Not excessively extending ranges when unnecessary
Con: Extra rest call

Partitioned Download (DownloadTo)

Decryption shifted from per-partition to the reassembled content stream
Pro: avoids overhead added to ranged download
Pro: avoids redownloading overlapping bytes from range extension
Pro: effectively separates transfer options from decryption logic
Con: v1 decryption loses parallelization (was tied to transfer parallelization)

@KrzysztofCwalina @tg-msft PR is in a state where your interests can be reviewed. You'll be interested in:

csproj files
Azure.Storage.Common.netstandard2.0.cs
GcmAuthenticatedCryptographicTransform.cs
BlobBaseClient.cs

Behavioral changes listed in PR description. Contents of Shared/ClientSideEncryption is where all the heavy operations take place if you need context. Happy to answer any questions.
QueueClient work is upcoming. Since queue message size is trivial that they are already buffered in the first place, there are no surprises coming in how data is managed.

/azp run net - storage - tests

/azp run net - storage - ci

/azp run net - storage - ci

/azp run net - storage - tests

@tg-msft Good catches! All internals though that will need to wait for GA. I am already writing my own list of work to track and I will add these to the list. Issue will be posted before merge.


importing Record destroys Record interface

Some of the solutions,
import { Dictionary, Record as Record_, Static, String, Unknown } from 'runtypes';
import * as t from 'runtypes';

type MyRecord<T> = {
  [k: string]: T
};

Yes of course. Importing Record from runtypes shadows TypeScript's built-in Record type alias. I think it's not an issue as you have already found the solutions.


Allow COPY FROM to skip lines

Summary of the changes / Why this improves CrateDB
Add a with clause option, skip for COPY FROM to be able to skip the specified number of lines.
resolves #12872
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

retest this please
unrelated failure cannot reproduce locally:
./gradlew :server:test --tests "org.elasticsearch.snapshots.BlobStoreIncrementalityIT.testIncrementalBehaviorOnPrimaryFailover" -Dtests.seed=4226F5626932A726 -Dtests.locale=yue-Hant -Dtests.timezone=America/North_Dakota/Center -Dtests.iters=50 --fail-fast

b926a9e is a test fix that I missed for #13261


fix(CI): prevent windows linting on MQ build

What does this PR do?
Forgot to remove the (too long) windows linting from previous PR #23077

Motivation
Keep time under control. Will add this job back as soon as we improve windows jobs duration

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge

/merge


Diagnostic in recipe_perfmetrics_CMIP5_4cds failing with ESMValCore 2.6rc2

The run for the grading diagnostic in recipe_perfmetrics_CMIP5_4cds ends with a diagnostic failure. However, inspecting the log does not give much of an idea as for why. It actually looks like the diagnostic is running fine since these are the final lines:
INFO    Wrote variable grade to /scratch/b/b381943/esmvaltool_output/recipe_perfmetrics_CMIP5_4cds_20220615_073238/work/ts/grading/RMSD_ts-global.nc
DEBUG   >>> Leaving ncdf_write (interface_scripts/auxiliary.ncl)
DEBUG   <<< Entering log_provenance (interface_scripts/logging.ncl)
INFO    Provenance information saved in /scratch/b/b381943/esmvaltool_output/recipe_perfmetrics_CMIP5_4cds_20220615_073238/run/ts/grading/diagnostic_provenance.yml
DEBUG   >>> Leaving log_provenance (interface_scripts/logging.ncl)
DEBUG   >>> Leaving grading

@remi-kazeroni was able to run the recipe requesting the right resources in Levante. Closing this.


Addition of windowless (javaw) option

Added a new option to call "javaw" instead of "java", only for Windows as Unix does not need this utility.

Fixes #65

Proposed Changes

Add new option for windowless
If true, javaExe becomes javaw
Check if caller platform is actually Windows, if true then use javaw, used for cross-platform compatibility
Added changelog entry and documentation for the option

Readiness Checklist
Author/Contributor

[X] Add entry to the CHANGELOG.md listing the change and linking to the corresponding issue (if appropriate)
[X] If documentation is needed for this change, has that been included in this pull request

Reviewing Maintainer

[ ] Label as breaking if this is a large fundamental change
[ ] Label as either automation, bug, documentation, enhancement, infrastructure, or performance

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

Comparison is base (3292af6) 90.45% compared to head (2041a78) 90.54%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #66      +/-   ##
==========================================
+ Coverage   90.45%   90.54%   +0.08%
==========================================
  Files           3        3
  Lines         220      222       +2
==========================================
+ Hits          199      201       +2
  Misses         21       21

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


bump version in package.json to v2.27.5

release version v2.27.5

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Failed to download resource "mplayer--patch"

curl: (22) The requested URL returned error: 404 Not Found
Download failed: https://gist.githubusercontent.com/jacknagel/7441175/raw/37657c264a6a3bb4d30dee14538c367f7ffccba9/vo_corevideo.h.patch

这个是什么?


Simplify the receiver lists

This PR depends on #1359.
I think there is more room for simplifications. I'm not sure if all tools should use additional_receivers instead of receivers. Examples:
https://github.com/mozilla/relman-auto-nag/blob/6ca57369d7b287286a00aaa97a841bfd43b59c59/auto_nag/scripts/configs/tools.json#L460-L462
https://github.com/mozilla/relman-auto-nag/blob/6ca57369d7b287286a00aaa97a841bfd43b59c59/auto_nag/scripts/configs/tools.json#L464-L465
https://github.com/mozilla/relman-auto-nag/blob/6ca57369d7b287286a00aaa97a841bfd43b59c59/auto_nag/scripts/configs/tools.json#L467-L468

I think there is more room for simplifications. I'm not sure if all tools should use additional_receivers instead of receivers.

I'd use additional_receivers for all tools, wdyt @calixteman?


How can i use 6.6.1 in kibana6.6.2 ?

My ELK ver is all 6.6.2.
Is there any way to install sentinl6.6.1 to kibana6.6.2?
(Byfar there isn't a sentinl6.6.2 version)
I use:
kibana-plugin install sentinl6.6.1
Plugin installation was unsuccessful due to error "Plugin sentinl [6.6.1] is incompatible with Kibana [6.6.2]"
How do i do?
downgrade ELK version or find something else
......

somebody in emergency can use this kibana-plugin elasticalert:
https://github.com/bitsensor/elastalert-kibana-plugin/releases
Maybe

you try to download the plugin to local, update plugin package.json version
t6.6.2, and then install the plugin
labosen<EMAIL_ADDRESS>于2019年3月22日周五 上午11:29写道：

somebody in emergency can use this kibana-plugin elasticalert:
https://github.com/bitsensor/elastalert-kibana-plugin/releases
Maybe
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sirensolutions/sentinl/issues/703#issuecomment-475481904,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APRMhLTv58COe9SNDXL734sA3dxEX7_1ks5vZE4VgaJpZM4cAqoK
.

@chenyg0911  thx, this works well


Consider an integration with exception notifier

The exception notifier gem allows to wrap several notifiers (email, slack, etc.). It would be nice to have a Rollbar notifier plugin for this gem
I know this can feel like a duplicate tool since Rollbar offers to some extent the same functionalities via the web interface, exception_notifier is agnostic and but you'd be able to very easily integrate with existing systems (almost 2k likes on the exception notifier gem). Also it would make migrating much easier.
Currently if I want to integrate Rollbar, I'd have to add code everywhere, whereas if there was an exception_notifier extension I could get everything for free.
Mirror issue https://github.com/smartinez87/exception_notification/issues/413

We will take a look into this, sorry for the delay!

Marking this as wontfix as we're not going to be able to consider this any time soon.


Added support for setting "Expires" tag together with max-age.

Thanks for the PR! This is a great option. If you don't mind adding some tests, I'd be super grateful. :)

Thanks for the PR @Dzitu :heart:
It looks like tests were requested a while back. We are working on merging the plugin repo back into the main repo this week, and these open PRs are blockers. Since this PR isn't in a position to be merged yet, I'm going to close it for now.
Long term, I believe serveStatic will be pulled out of core all together -- serving static content is outside of the REST wheelhouse. If this PR is still important to you, please re-open it against the main repo prior to the serveStatic breakout, or the serveStatic repo when it finds a new home.


remove uncle bandit page

It seems that the uncle bandit page has been removed in another PR: https://docs.flashbots.net/flashbots-protect/rpc/uncle-bandits.
@bertmiller let's close this PR


Hendrix additions

Changed file hierarchy to match written example, added class-based Pubmed module

sounds good! I'll go ahead and merge in the meantime


Incorrect batch progress saved in checkpoint at every_n_train_steps

Bug description
When saving a checkpoint at every_n_train_steps=3, it performs the checkpoint saving inside on_train_batch_end function in ModelCheckpoint class. During that checkpoint saving, the state dict of fit loop is snapshotted and saved, along with the batch progress of it. But the batch_progress is only incremented after on_train_batch_end is called/checkpoint is saved, thus the saved checkpoint having incorrect batch_progress which looks like this:
# in checkpoint file checkpoint['loops']['fit_loop']['epoch_loop.batch_progress']
{total: {ready: 3, completed: 2, started: 3, processed: 3}}

And the expected value should be: {total: {ready: 3, completed: 3, started: 3, processed: 3}}, which is what the checkpoint saved after validation contains.
This causes an issue that when we resume from batch_end checkpoint, the starting batch_idx is 2 while the global step is 3 in training_step function in model module (they should match), and following saved checkpoint all having incorrect step value in file name.  This doesn't seem like expected behavior, am I missing something?
I'm currently using a hack in the on_train_batch_end override function like this to overcome this issue:
    def on_train_batch_end(self, trainer, pl_module, outputs, batch, batch_idx) -> None:
        # hack: https://github.com/Lightning-AI/lightning/blob/master/src/lightning/pytorch/loops/training_epoch_loop.py#L233-L237
        # At the time this function is called, the `completed` value in batch progress is not incremented yet.
        # If a checkpoint is saved, the saved checkpoint will have an incorrect completed value in batch progress.
        # When we resume from this checkpoint, it will cause batch_idx becoming one step behind global step value in training_step func in modelModule
        trainer.fit_loop.epoch_loop.batch_progress.increment_completed()
        super().on_train_batch_end(trainer, pl_module, outputs, batch, batch_idx)

        # revert back changes to completed value in batch progress
        trainer.fit_loop.epoch_loop.batch_progress.total.completed -= 1
        trainer.fit_loop.epoch_loop.batch_progress.current.completed -= 1

What version are you seeing the problem on?
v1.9, master
How to reproduce the bug
No response
Error messages and logs
# Error messages and logs here please

Environment

Current environment
#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version (e.g., 1.5.0):
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 2.0):
#- Python version (e.g., 3.9):
#- OS (e.g., Linux):
#- CUDA/cuDNN version:
#- GPU models and configuration:
#- How you installed Lightning(`conda`, `pip`, source):
#- Running environment of LightningApp (e.g. local, cloud):

More info
No response
cc @carmocca @justusschock

I came across this issue as well. Is there a solution to it?

I came across this issue as well. Is there a solution to it?

you can change the checkpoint then its being saved
     checkpoint['loops']['fit_loop']['epoch_loop.batch_progress']['total']['completed'] = \
         checkpoint['loops']['fit_loop']['epoch_loop.batch_progress']['total']['processed']
     checkpoint['loops']['fit_loop']['epoch_loop.batch_progress']['current']['completed'] = \
         checkpoint['loops']['fit_loop']['epoch_loop.batch_progress']['current']['processed']
     checkpoint['loops']['fit_loop']['epoch_loop.state_dict']['_batches_that_stepped'] = \
         checkpoint['loops']['fit_loop']['epoch_loop.batch_progress']['current']['processed']```

Definitely still an issue and definitely still open.

Same problem. Hope to see an appropriate solution.


Newbie question

Where does the config element go? Could you please add that to the readme with an example

hi, assuming that you're using neovim, and vim-plug.
call plug#begin()
" TRUNCATED  ...
Plug 'sunjon/shade.nvim'
" TRUNCATED  ...
call plug#end()

lua require'shade'.setup({
      \   overlay_opacity = 50,
      \   opacity_step = 1,
      \   keys = {
      \     brightness_up    = '<C-Up>',
      \     brightness_down  = '<C-Down>',
      \     toggle           = '<Leader>s',
      \   }
      \ })

I added the lines you suggested to my .vimrc. Upon launching vim I noticed errors which are included below.
user1@RErrabolDevMach:~$ gvim
Error detected while processing /home/user1/.vimrc:
line  141:
[string "vim chunk"]:1: module 'shade' not found:
^Ino field package.preload['shade']
^Ino file '/usr/local/share/lua/5.2/shade.lua'
^Ino file '/usr/local/share/lua/5.2/shade/init.lua'
^Ino file '/usr/local/lib/lua/5.2/shade.lua'
^Ino file '/usr/local/lib/lua/5.2/shade/init.lua'
^Ino file '/usr/share/lua/5.2/shade.lua'
^Ino file '/usr/share/lua/5.2/shade/init.lua'
^Ino file './shade.lua'
^Ino file '/usr/local/lib/lua/5.2/shade.so'
^Ino file '/usr/lib/x86_64-linux-gnu/lua/5.2/shade.so'
^Ino file '/usr/lib/lua/5.2/shade.so'
^Ino file '/usr/local/lib/lua/5.2/loadall.so'
^Ino file './shade.so'
user1@RErrabolDevMach:~$

I installed python-shade and it didn't seem to make any difference.

this is a neovim specific plugin, because it is written in lua.
you're using gvim so i don't think you can use this plugin.
you might want to check out https://github.com/blueyed/vim-diminactive instead. I am not familiar with gvim, but the vim-diminactive should be compatible with gvim

Thanks for the clarification. I will try in neovim and let you know.

I'm assuming this is resolved now. Create a new issue if you're still having problems.


specify timestamp override as current time or previous image created_…

…at value if force is specified
Signed-off-by: Samuel Dacanay<EMAIL_ADDRESS>What this PR does / why we need it:
When an image is submitted for analysis by digest & tag, right now it will throw an error if the created_at timestamp is not specified.
Now, if it's missing, we will default it to the current time epoch, and if the force parameter is specified, we will try to retrieve it from the previous image's value. If it still doesn't exist on the previous image, we will set it to the current time epoch
Which issue this PR fixes : fixes #552
Special notes:
Manual Functional test below to verify it is working. As you can see, no creation_timestamp_override is specified and therefore, one is set to the current time (which was 1:58 pm)
samdacanay@samsanchorembp ~ % curl -X POST -H "Authorization: Basic YWRtaW46Zm9vYmFy" -H "Content-Type: application/json" -d '{"source": {"digest": {"pullstring": "swaggerapi/swagger-ui@sha256:f75b398a3a3d0b4ffa03693a001af52367b13ec55b61e7fbebe078cbd69a060e","tag": "docker.io/swaggerapi/swagger-ui:latest"}}}' "http://localhost:8228/v1/images"
[
  {
    "analysis_status": "not_analyzed",
    "analyzed_at": null,
    "annotations": {},
    "created_at": "2020-08-07T20:58:13Z",
    "imageDigest": "sha256:f75b398a3a3d0b4ffa03693a001af52367b13ec55b61e7fbebe078cbd69a060e",
    "image_content": {
      "metadata": {
        "arch": null,
        "distro": null,
        "distro_version": null,
        "dockerfile_mode": null,
        "image_size": null,
        "layer_count": null
      }
    },
    "image_detail": [
      {
        "created_at": "2020-08-07T20:58:13Z",
        "digest": "sha256:f75b398a3a3d0b4ffa03693a001af52367b13ec55b61e7fbebe078cbd69a060e",
        "dockerfile": null,
        "fulldigest": "docker.io/swaggerapi/swagger-ui@sha256:f75b398a3a3d0b4ffa03693a001af52367b13ec55b61e7fbebe078cbd69a060e",
        "fulltag": "docker.io/swaggerapi/swagger-ui:latest",
        "imageDigest": "sha256:f75b398a3a3d0b4ffa03693a001af52367b13ec55b61e7fbebe078cbd69a060e",
        "imageId": "af194872176ffeadbd6f0d2918372c0f8e49406c4cb7e64e450957e00ddbbe63",
        "last_updated": "2020-08-07T20:58:14Z",
        "registry": "docker.io",
        "repo": "swaggerapi/swagger-ui",
        "tag": "latest",
        "tag_detected_at": "2020-08-07T20:58:14Z",
        "userId": "admin"
      }
    ],
    "image_status": "active",
    "image_type": "docker",
    "last_updated": "2020-08-07T20:58:14Z",
    "parentDigest": "sha256:f75b398a3a3d0b4ffa03693a001af52367b13ec55b61e7fbebe078cbd69a060e",
    "userId": "admin"
  }
]

Thanks @dakaneye I'll take a look!


Displaying the project overview for large cohorts is slow

Describe the bug
Opening the project overview for projects with many cases is slow.
To Reproduce
Steps to reproduce the behavior:

Open project with  many cases
VarFish will go on loading for multi-second time to display 5 cases.

Expected behavior
Result should be almost instantaneous.
Screenshots
N/A
Additional context

#304

Tasks

[x] apply workaround
[ ] adjust sodar-core dependency once resolved there

Root Cause Analysis

look at all queries generated by project overview
see that there are many queries such as

SELECT "djangoplugins_plugin"."id", "djangoplugins_plugin"."point_id", "djangoplugins_plugin"."pythonpath", "djangoplugins_plugin"."name", "djangoplugins_plugin"."title", "djangoplugins_plugin"."index", "djangoplugins_plugin"."status" FROM "djangoplugins_plugin" WHERE "djangoplugins_plugin"."name" = 'samplesheets' ORDER BY "djangoplugins_plugin"."index" ASC, "djangoplugins_plugin"."id" ASC LIMIT 1
 SELECT "timeline_projecteventstatus"."id", "timeline_projecteventstatus"."event_id", "timeline_projecteventstatus"."timestamp", "timeline_projecteventstatus"."status_type", "timeline_projecteventstatus"."description", "timeline_projecteventstatus"."extra_data" FROM "timeline_projecteventstatus" WHERE "timeline_projecteventstatus"."event_id" = 131926 ORDER BY "timeline_projecteventstatus"."timestamp" DESC LIMIT 1

a candidate culprit is this code

https://github.com/bihealth/sodar-core/blob/a8ba2c860157eed0602dd32d2c285175af872464/timeline/templatetags/timeline_tags.py#L41
this will first iterate over all events and then select the latest 5
thus, loading of the project overview needs time linear to ALL events for the project

Resolution Proposal
The following patch to sodar-core will resolve this (github)
diff --git a/timeline/templatetags/timeline_tags.py b/timeline/templatetags/timeline_tags.py
index eae4b34..a5ccd32 100644
--- a/timeline/templatetags/timeline_tags.py
+++ b/timeline/templatetags/timeline_tags.py
@@ -1,3 +1,4 @@
+import itertools
 import html

 from django import template
@@ -46,9 +47,13 @@ def get_details_events(project, view_classified):
     if not view_classified:
         events = events.exclude(classified=True)

-    events = events.order_by('-pk')
+    events = events.order_by("-pk")

-    return [x for x in events if x.get_current_status().status_type == 'OK'][:5]
+    return list(
+        itertools.islice(
+            (x for x in events if x.get_current_status().status_type == "OK"), 5
+        )
+    )

 # Template rendering -----------------------------------------------------------

Affected Components

sodar-core

Affected Modules/Files

sodar-core timeline/templatetags/timeline_tags.py

Required Architectural Changes
N/A
Resolution Sketch

patch sodar-core
change dependency
workaround, see below

diff --git a/HISTORY.rst b/HISTORY.rst
index 0eae5d6..600ea5e 100644
--- a/HISTORY.rst
+++ b/HISTORY.rst
@@ -35,6 +35,7 @@ End-User Summary
 - Added feature to select multiple rows in results to create same annotation (#259)
 - Added parameter to Docker entrypoint file to accept number of gunicorn workers
 - Extended documentation for how to update specific tables (#177)
+- Improving performance of project overview (#304)

 Full Change List
 ================
@@ -71,6 +72,7 @@ Full Change List
 - Added feature to select multiple rows in results to create same annotation (#259)
 - Added parameter to Docker entrypoint file to accept number of gunicorn workers
 - Extended documentation for how to update specific tables (#177)
+- Improving performance of project overview (#304)

 -------
 v0.23.9
diff --git a/requirements/base.txt b/requirements/base.txt
index 25298ef..20036ab 100644
--- a/requirements/base.txt
+++ b/requirements/base.txt
@@ -67,7 +67,8 @@ celery >=5.1.0, <5.2
 # TODO: bump to django-postgres-copy==2.6.0?
 django-postgres-copy ==2.3.5

-django-sodar-core >=0.10.2, <0.11
+#django-sodar-core >=0.10.2, <0.11
+-e git+https://github.com/bihealth/sodar-core.git@optimize-get_details_events#egg=django-sodar-core

 # Simplejson is more advanced than then built-in one.
 simplejson >=3.17.2

We still need to wait for fix in sodar-core.


helm overwrite existing resources deployed by non-helm

Hi:
I have an EKS cluster created with Terraform and working to implement AWS Console RBAC in the cluster discussed here.  As part of this process, I am able to deploy the Role, Binding using Helm Chart and patch aws-auth configmap using kubectl.
Deploying configmap using Helm complains the resource already exists and requires the configmap metadata fields (ownership,etc) to be set to helm values.  Ideally would like helm to overwrite the resource, so we can start developing custom charts and use helm for cluster updates/deployments.
Can helm overwrite existing resources deployed by non-helm, or is there a workaround that should make this possible ?
Error:
Error: rendered manifests contain a resource that already exists. Unable to continue with install: ConfigMap "aws-auth" in namespace "kube-system" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: key "app.kubernetes.io/managed-by" must equal "Helm": current value is "Terraform"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "console-rbac"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "kube-system"
Output of helm version:
v3.5.3+g041ce5a
Output of kubectl version:
Client Version: v1.19.0
Server Version: v1.20.7-eks-d88609
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
AWS EKS

@kumarpmd you can try to delete the existing resources deployed by non-helm by kubectl.

@yxxhero Thank you.  The deletion will work since it removes the "Terraform" ownership metadata.  Requires an extra  manual step, "kubectl patch" for example.
Ideally prefer to handle create and update with Helm.  Any flags that can trigger overwrite, etc..

This is not something we plan to support. Overwriting existing resources must be performed manually as there are many things that can go wrong with "commandeering" existing resources in the cluster.
Duplicate of #2730.

I want to say that over three companies working with kubernetes and helm this is the single largest annoyance in helm. Telling people 'we need to take downtime in order to start using a helm chart for service x. Is a non starter (sure i can delete the deployment with --cascade=false, but i still have to delete a service so ... downtime). For one service this is less of a problem, I can go in and manually patch all the resources pre helm deploy and 'fool it'. But why can't I have a flag to solve this problem for me a --this-might-be-a-bad-idea-but-ignore-ownership-restrictions on upgrade/install.
I've written such a thing but it's a hack:

run helm template capture the output
parse the output and find all the objects type/name/namespace
for objects patch object on the cluster with labels/annotations
actually run helm install

I've also written this type of logic into a companies deployment pipelines:

run helm install
if error output, parse object name/namespace/type out of error and patch
loop 1 until no error

TL;DR the transition from live services deployed without helm to live services deployed with helm is FRAUGHT and sticking your head in the sand and having such a strong opinion is just user hostile, it's a pattern with helm (see also app version embedded in chart and not bundling dependencies into charts, and strict semver versioning in general) and it's disappointing.

I also think it should be possible to make helm take ownership over a resource with some sort a --force flag instead of needing workarounds or downtime inducing changes

Bruh, when you have to manually delete over 54 services in 2 production clusters (over 108 - helm 2 deployments) with service NodePorts, because no patch...And then redeploy all 108 services and add new NodePorts to the loadbalancer pools.
(Don't ask me why they we're using NodePorts for routing and  manual setups, I was just there for 2 months...)

This feature is really necessary. I think at the very least, helm should ask us if we'd like to overwrite.

Yes, or better, add a label/annotation to mark a ressource "adoptable". My example use case:
I create a Kubernetes Cluster on AWS (EKS). There's a concept of an "IAM Service Account", i.e. a Kubernetes ServiceAccount which also has configured privileges on AWS. These are usually not created by Helm, and ServiceAccounts are namespaced.
So you create your IAM serviceaccount, including the namespace it lives in. But now the Helm chart wants to create the namespace, too, but it is already there....
Or do I not include the namespace in the helm chart? what if the Chart should work on non-AWS-Clusters, too, where the namespace might not pop up beforehand?
Making the Namespace manifest a pre-install hook on an existing chart will (understandably) delete the namespace on the next update, including all resources within. So that's not an option either.
I'd love to see an annotation like "helm.sh/existing-resource-policy" with options like "reject" (default), but also "overwrite", "merge" or "adopt".

I had to create a Python script with that operates Helmfile via Taskfile in order to do this in a standard way.
Does https://kluctl.io (https://github.com/kluctl/kluctl) does this?

As someone who needs to update the aws-auth ConfigMap in an EKS cluster it surprises me there's no way to take control of the resource in Helm...
In a previous project that used Kluctl this was possible using the annotation kluctl.io/force-apply-field: ".data.mapRoles"
Incoming HACK HACK HACK to get around this... 🙁

Unfortunately deletion is impossible for me. Can't edit it, tried adding 'group: karpenter.k8s.aws' to no avail, and can't patch the finaliser. Aargh

Unfortunately deletion is impossible for me. Can't edit it, tried adding 'group: karpenter.k8s.aws' to no avail, and can't patch the finaliser. Aargh

For me this fixes it: Helm >= 3.16 offers a "take ownership" options for API users, Flux 2.4.0 implements it now: https://github.com/fluxcd/helm-controller/issues/1059
It might not selectively patch or delete resources, but it will adopt/override them if already present.
@ElvenSpellmaker Take a look at EKS access entries: https://docs.aws.amazon.com/eks/latest/userguide/setting-up-access-entries.html, so you can leave aws-auth behind.
@agray-ctm Check if the resource you try to patch is valid (see https://github.com/aws/karpenter-provider-aws/blob/main/pkg/apis/crds/karpenter.sh_nodeclaims.yaml#L84-L90).

this is super annoying.

It looks like there's already support for a TakeOwnership option via the Go SDK (https://github.com/helm/helm/pull/12876). Is there a reason why we won't support setting it via the CLI?

Reopening given https://github.com/helm/helm/pull/12876
Worth mentioning I think, that this PR allows adopting not overwriting existing resources, as this issue describes. But, I think the overall problem is that Helm won't proceed with an install/upgrade when a resource already exists. And "adopting" resources solve that.
The final thing here it seems, would be to expose https://github.com/helm/helm/pull/12876's functionality to the cli.


Improve reStructuredText performance

While we wait on a mature (or even moderately capable) native go reStructuredText support (e.g. #1436), I would like to open a new issue as a proposal for an intermediate solution.
I'm preparing a site with ~1600 rst posts. Using the current implementation, it takes 2 and a half to three minutes to render the site. On a theory that we were loosing some time to python process startup, I prototyped a solution where:

a very basic flask app that takes a POST request with some and returns the rendered restructured task:
import docutils.core

from flask import Flask
from flask import request

app = Flask(__name__)

@app.route("/", methods=["POST", "GET"])
def main():
    if request.method == "GET":
        return "rst2html service; use the POST method to convert"
    else:
        return docutils.core.publish_parts(request.data, writer_name="html")['body'].strip()

if __name__ == '__main__':
    app.run()

a modification to the existing getRstContent() function that does the appropriate HTTP request for converting the content.

This gets the rendering time down for my site down to ~30 seconds. I tried converting all the rst to markdown (which didn't go well,) and rendering was ~3 seconds, so this isn't ideal, and doesn't obviate the need for #1436, but puts rst support into the realm of usable.
The challenge is how to make this solution production worthy. My initial inclination is to write the script above to a tempfile, and then start it in a goroutine in the background, but I'm not sure if hugo has a concept, of a "background job" that we could hook into, and by the time we need to render rst the first time, its too late. At the same time, rst clearly has a niche audience within hugo, and it seems disruptive to force RST to restructure the way that hugo processes text (though, I think that's not historically inconsistent, based on my memory of adding the existing rst support.)
Would it make sense to write a "go rst library" with a functional interface, that uses this approach internally that hugo could consume? My largest concern is potentially leaking the flask app, but I assume that's possible to overcome.
Is there another option that I'm missing?

The challenge is how to make this solution production worthy.

I would say that unless 1000s of people are shouting for speedier RST, your solution will never be accepted into Hugo. It adds complexity that I don't want to maintain/support.
You are right about the os/exec overhead -- if that could be reduced by batching the RST conversion somehow (it needs some refactoring, but Hugo could send all (or batches of) the pages in one Go to the external helper), that could be interesting. But that should also somehow include Aciidoc, which I guess is more popular than RST.

That said, a "http page handler" fits nicely into a future plugin scenario, but the Python server would have to be provided by you.

I've been thinking about writing a go package that does asciidoc/rst via a REST api running a mini "embedded" flask app, (but that would be an implementation detail hidden from hugo), but that would basically integrate into the existing implementation.
Should be pretty easy to get something together, I'd implement it as something in my own account, and is this something that you'd be interested or willing to merge?

you'd be interested or willing to merge?

We're not running any embedded "flask server" (whatever that is) inside Hugo, if that answered your question.

Currently, hugo is willing to run third party python scripts (e.g. the current working asciidoc/rst implementation) via exec, and it cannot ensure these dependencies exist.
I'm proposing a package that:

exposes a go functional interface to perform these text transformations.

supports rst and asciidoc.

would be able to drop into the existing hugo implementation without architecture changes of any kind.

I'm in favor of leaving the implementation details to that package and not discussing that as part of this proposal, though I think a more robust version of the script in the original post is pretty reasonable.
It also makes some sense to me to create a package in pypi that depends on all of the Python dependencies, to simplify the user experience for getting access to these features.

Let me think about it.
I agree on the tech side of your arguments, but it is still one more knob to care about. And that is a knob I don't need (Ascciidoctor, RST) personally. To take one example: I have spent a fair amount of energy to all the 3 template engines up to "Hugo spec", but I'm not even sure Ace or Amber is in use by any numbers. I have seen enough people contribute stuff and then leave the building, so I'm extremely hesitant to new knobs, esp. if they're not hitting the "core Hugo functionality".

That's fair, though, I'm the original contributor of the restructured text support (and some other miscellany) and while I'm not hugely involved these days.
Also as envisioned, this wouldn't add any new knobs or potential configuration, but would just replace the existing functionality with a different backend, (admittedly one with more moving parts.)

I'm willing to begin work on this soon, if the proposal makes sense to you (all?) If you have additional feedback, that would increase my chances of getting this changed merged, I would love to hear them.

I'll delegate the decision making to @anthonyfok -- I believe he did the work on the Asciidoc side.
But it should:

Replace any old solution, i.e. not several ways to generate RST / Asciidoc
Any web server should be lazily started,  i.e. I, who doesn't use either of them, should not "feel it" outside the tests

Agreed on replacing exiting old methods for generating rst/asciidoc. Method would be generalizable to any python text processing strategy, and lazily started.
What are the minimum supported go versions for hugo these days?

What are the minimum supported go versions for hugo these days?

1.6. We follow a two current-1 policy.

I've created a new library package with a functional public interface that does what I've described above, that's https://github.com/tychoish/shimgo, the hugo impact is minimal comparatively and is in #2672 for consideration and further discussion.

This issue has been automatically marked as stale because it has not been commented on for at least six months.
The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.


Create stale issue and PR bot

This PR creates a stale issue bot.
More info here: https://github.com/marketplace/actions/close-stale-issues
The default value is that issues and PRs will be marked stale after two months of no activity. Once marked stale, issues and PRs with no further activity will be closed seven days later. (Assuming I understand the documentation correctly.)

Merging but future PRs related to this bot welcome :)
And it it's too annoying or counter-productive, we can always kill this bot too.


add nabu implementation network env

New property implementation network. This needs to be added to the config file.

This was an issue with gleaner/nabu


Shader compilation failure with indexed location and sampler2DArray array

I’m attempting to enable the Vulkan renderer of the Dolphin emulator on macOS with MoltenVK.
I’ve put the necessary glue code in place, and I patched MoltenVK to work around #61. The emulation starts up fine but some of the GLSL shaders generated by Dolphin fail to compile once translated to MSL, with two reported errors.
The first error is
program_source:59:20: error: 'color' has a duplicate index '0'
    float4 ocol1 [[color(0)]];
                   ^
program_source:58:20: note: duplicate 'color' index '0' here
    float4 ocol0 [[color(0)]];

It seems to be caused by the following code in the GLSL shader:
layout(location = 0, index = 0) out vec4 ocol0;
layout(location = 0, index = 1) out vec4 ocol1;

which gets translated to
float4 ocol0 [[color(0)]];
float4 ocol1 [[color(0)]];

causing the error. Apparently the specified index is ignored by the converter. I’ve noted that this shader code also causes problems with some native Vulkan drivers: Dolphin emits a layout(location = 0)/layout(location = 1) instead in that case.
The second error is
program_source:103:26: error: type 'texture2d_array<float>' does not provide a subscript operator
    float4 param_1 = samp[0].sample(samp[0]Smplr, float3(float2(tevcoord.xy) * _126.texdim[0].xy, 0.0).xy, uint(round(float3(float2(tevcoord.xy) * _126.texdim[0].xy, 0.0).z))) * 255.0;

The GLSL shader contains:
layout(set = 1, binding = 0) uniform sampler2DArray samp[8];
[…]
texture(samp[0], …)

which seems to be converted to
fragment main0_out main0(texture2d_array<float> samp [[texture(0)]], …
[…]
samp[0].sample(samp[0]Smplr, …)

which doesn’t work because samp is no longer an array. The samp[0]Smplr bit also seems suspicious, even though the compiler doesn’t complain about it.
I’m attaching the generated GLSL shader, the MoltenVK log (with the converted MSL) and a reduced test case that reproduces the erroneous code generation when run through MoltenVKShaderConverter.

One thing I just noticed in the MoltenVK log is that the SPIR-V does contains both the layout and location info for ocol0/ocol1, but the “Estimated original GLSL” doesn’t:
               OpName %389 "ocol0"
               OpName %391 "ocol1"
               OpDecorate %389 Index 0
               OpDecorate %389 Location 0
               OpDecorate %391 Index 1
               OpDecorate %391 Location 0

layout(location = 0) out vec4 ocol0;
layout(location = 0) out vec4 ocol1;

Thanks for the detailed report.
Since it is a shader conversion issue...can you also report it to SPIRV-Cross, so it can be tracked and fixed there, please?
The texture array issue might be a similar to this issue.

This is related to dual-source blending I think. Does Molten support that?

@billhollings, thanks for pointing me to the right direction. I’ve created https://github.com/KhronosGroup/SPIRV-Cross/issues/516 and commented on https://github.com/KhronosGroup/SPIRV-Cross/issues/507#issuecomment-376293546 (which indeed seems related). I’m closing this issue.

Replaced by enhancement issue #123. Closing.


Confusing placement of active editor for Cat Painting Step 8

Describe the Issue
I've run into this several times in the forum in the past week. The active editor is placed within the existing .cat-head rule set and apparently people don't notice that and instead create a new .cat-head rule set and add the background there.
Affected Page
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-intermediate-css-by-building-a-cat-painting/step-8
Your code
This is what I'm seeing in the forum:
.cat-head {
  width: 205px;
  height: 180px;
  border: 1px solid #000;
  border-radius: 46%;

/* User Editable Region */

.cat-head {
  background: linear-gradient(#5e5e5e 85%, #45454f 100%);
}

/* User Editable Region */

}

Expected behavior
I think the active editor should include the entire existing .cat-head rule set so that it is clear it already exists and that that is where the background property should be added. We can add an empty line at the bottom of the rule set to indicate where the background property should go.
Screenshots
No response
System
N/A
Additional context
No response

I definitely agree.
I went ahead and made a PR that moves the editable region to include the full selector.


Start optimising the memory footprint of the UTxO.

This changes the memory representation of TxIn and TxOut, to reduce overhead.
In particular, we use unpacked Word64 for coin values and txout indices, and use
the serialisation of addresses as ShortByteString.
This does not yet change the representation of TxId.
The changes are nearly opaque, in that we provide view patterns that takes the
place of the old constructors. We do need to add a Crypto constraint wherever we
use a TxOut, however, since the view pattern relies on
serialisation/deserialisation.
This is a draft PR for now, as I'd like to add some properties around the TxOut (I've introduced a panic when deserialisation fails in the view pattern, which should never occur, since the constructor itself is not exported, and so the only way to construct a TxOut is using serialisation).

Since we rely on the (de)serialiseAddress then we should inherit the round trip property, but it's worth adding a QC test anyway.


wsl2 Ubuntu 20.04 LTS Android build failed -no matching toolchains

System information

OS Platform and Distribution (e.g., Linux Ubuntu 20.04, WSL2): wsl2 Ubuntu 20.04LTS
Target (e.g. desktop cpu, android arm64): android arm64
Bazel version:4.0
Python version:3.9
GCC/G++ version:9.3
Unity version:2019.25.1f
Android NDK version (if building for Android): r19
Xcode version (if building for iOS):

Describe the problem
I am getting issues while building libraries for the android on wsl2(ubuntu 20.04).
Although I have successfully build library and .apk for mediapipe repository.
the android path is as follows.
$ANDROID_HOME=/root/Android/Sdk
$ANDROID_NDK_HOME=/root/Android/Sdk/ndk-bundle/android-ndk-r19c
Steps to reproduce the issue
Provide the exact sequence of commands / steps that you executed before running into the problem.
python3.9 build.py build --android arm64 --opencv=cmake --opencv_deps=ffmpeg -v
Full logs
root@DESKTOP-MOU5O95:/home/aashutosh/mediapipe4/MediaPipeUnityPlugin-master# python3.9 build.py build --android arm64 --opencv=cmake --opencv_deps=ffmpeg -v
INFO (build.py): Building protobuf sources...
DEBUG (build.py): Running bazel build -c opt //mediapipe_api:mediapipe_proto_srcs
Starting local Bazel server and connecting to it...
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'rules_cc' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'rules_python' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'bazel_skylib' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'pybind11' because it already exists.
INFO: Analyzed target //mediapipe_api:mediapipe_proto_srcs (43 packages loaded, 666 targets configured).
INFO: Found 1 target...
Target //mediapipe_api:mediapipe_proto_srcs up-to-date:
bazel-bin/mediapipe_api/mediapipe_proto_srcs.zip
INFO: Elapsed time: 5.643s, Critical Path: 0.19s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
DEBUG (build.py): Unarchiving 'bazel-bin/mediapipe_api/mediapipe_proto_srcs.zip' to 'build/Scripts/Protobuf'...
INFO (build.py): Built protobuf sources
INFO (build.py): Downloading protobuf dlls...
DEBUG (build.py): Running nuget install -o .nuget -Source https://api.nuget.org/v3/index.json
Feeds used:
/root/.nuget/packages/
https://api.nuget.org/v3/index.json
All packages listed in /home/aashutosh/mediapipe4/MediaPipeUnityPlugin-master/packages.config are already installed.
DEBUG (build.py): Copying '.nuget/System.Buffers.4.4.0/lib/netstandard2.0/System.Buffers.dll' to 'build/Plugins/Protobuf/System.Buffers.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/System.Buffers.dll'...
DEBUG (build.py): Copying '.nuget/Google.Protobuf.3.15.6/lib/netstandard2.0/Google.Protobuf.dll' to 'build/Plugins/Protobuf/Google.Protobuf.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/Google.Protobuf.dll'...
DEBUG (build.py): Copying '.nuget/System.Memory.4.5.3/lib/netstandard2.0/System.Memory.dll' to 'build/Plugins/Protobuf/System.Memory.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/System.Memory.dll'...
DEBUG (build.py): Copying '.nuget/System.Runtime.CompilerServices.Unsafe.4.5.2/lib/netstandard2.0/System.Runtime.CompilerServices.Unsafe.dll' to 'build/Plugins/Protobuf/System.Runtime.CompilerServices.Unsafe.dll'...
DEBUG (build.py): Changing the mode of 'build/Plugins/Protobuf/System.Runtime.CompilerServices.Unsafe.dll'...
INFO (build.py): Downloaded protobuf dlls
INFO (build.py): Building resource files
DEBUG (build.py): Running bazel build -c opt //mediapipe_api:mediapipe_assets
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'rules_cc' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'rules_python' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'bazel_skylib' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'pybind11' because it already exists.
INFO: Analyzed target //mediapipe_api:mediapipe_assets (18 packages loaded, 46 targets configured).
INFO: Found 1 target...
Target //mediapipe_api:mediapipe_assets up-to-date:
bazel-bin/mediapipe_api/mediapipe_assets.zip
INFO: Elapsed time: 1.325s, Critical Path: 0.65s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
DEBUG (build.py): Unarchiving 'bazel-bin/mediapipe_api/mediapipe_assets.zip' to 'build/Resources'...
INFO (build.py): Built resource files
INFO (build.py): Building native libraries for Android...
DEBUG (build.py): Running bazel build -c opt --config=android_arm64 //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'rules_cc' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'rules_python' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'bazel_skylib' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/3214a78bf55a4fc910e84191acf2e25e/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'pybind11' because it already exists.
INFO: Build options --cpu, --crosstool_top, --fat_apk_cpu, and 1 more have changed, discarding analysis cache.
ERROR: While resolving toolchains for target //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_dummy_app: no matching toolchains found for types @bazel_tools//tools/android:sdk_toolchain_type
ERROR: Analysis of target '//mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android' failed; build aborted: no matching toolchains found for types @bazel_tools//tools/android:sdk_toolchain_type
INFO: Elapsed time: 0.245s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (2 packages loaded, 56 targets configured)
Traceback (most recent call last):
File "/home/aashutosh/mediapipe4/MediaPipeUnityPlugin-master/build.py", line 392, in
Argument().command().run()
File "/home/aashutosh/mediapipe4/MediaPipeUnityPlugin-master/build.py", line 153, in run
self._run_command(self._build_android_commands())
File "/home/aashutosh/mediapipe4/MediaPipeUnityPlugin-master/build.py", line 51, in _run_command
return subprocess.run(command_list, check=True)
File "/usr/lib/python3.9/subprocess.py", line 524, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['bazel', 'build', '-c', 'opt', '--config=android_arm64', '//mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android']' returned non-zero exit status 1.
root@DESKTOP-MOU5O95:/home/aashutosh/mediapipe4/MediaPipeUnityPlugin-master#
Additional context

Add any other context about the problem here.

Please check if you really have set ANDROID_HOME and ANDROID_NDK_HOME.
echo $ANDROID_HOME
echo $ANDROID_NDK_HOME`

It looks like you logged in as root user but your current directory is under another user(aashutosh)'s home directory.
If you've set those environment variables for aashutosh, they are not set for root automatically.

Hey, thanks!
You were right. $ANDROID_HOME and $ANDROID_NDK_HOME path were not set for the root user.
I moved mediapipe directory to the root folder and it worked.
Build successfully completed.

Hi, I got the similar error but I've set ANDROID_HOME and ANDROID_NDK_HOME.
I've run this build command on Macos:
sudo python build.py build --desktop cpu --android arm64 --opencv=cmake
Error I got:
While resolving toolchains for target //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_dummy_app: no matching toolchains found for types @bazel_tools//tools/android:sdk_toolchain_type


openssl: remove run-time dependency of perl due to c_rehash

Replaces perl based c_rehash script with shell script wrapping openssl rehash
with the same functionality.
Fixes: #19965
Supersedes: #156776, #83446 https://github.com/NixOS/nixpkgs/pull/219323
Possibly related to: #157093, #82924###### Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Is it possible to make these changes in quictls?

@Izorkin that appears to have been done already in the second commit.

@Izorkin that appears to have been done already in the second commit.

Right, I wasn't paying attention :)

built the 2 commits on top of master (x86_64-linux):

nice work

built the 2 commits on top of master (x86_64-linux):

nice work

@gdamjan what’s this TUI you have there for inspecting deps?

@gdamjan what’s this TUI you have there for inspecting deps?

:)
it's  nix-tree
https://github.com/utdemir/nix-tree

Built openssl and quictls on aarch64-darwin

🎉


[GOREPORT] Fix linting issues maya/command/snapshot_delete.go

Goreport is showing several linting errors. Please see the report at
https://goreportcard.com/report/github.com/openebs/maya
This issue is to fix the errors in
https://github.com/openebs/maya/blob/master/command/snapshot_delete.go
Line 9: warning: exported type SnapshotDeleteCommand should have comment or be unexported (golint)
Line 23: warning: exported method SnapshotDeleteCommand.Help should have comment or be unexported (golint)
Line 36: warning: exported method SnapshotDeleteCommand.Run should have comment or be unexported (golint)
Line 55: warning: exported method SnapshotDeleteCommand.DeleteSnapshot should have comment or be unexported (golint)
Line 122: warning: exported method ReplicaClient.MarkDiskAsRemoved should have comment or be unexported (golint)

can I work on this?

Working on this. Assign me please.

Hi working on this. Assign me the issue.


[Error]: spawn EINVAL -4071

Describe the bug
While running tsp install right after tsp init (a new clean project) on Windows 11 (details below) with Node 20.12.2, I am getting the following error:
Error: spawn EINVAL
at ChildProcess.spawn (node:internal/child_process:421:11)
at spawn (node:child_process:761:9)
at installTypeSpecDependencies (file:///D:/Scratch/TypeSpec/node_modules/@typespec/compiler/dist/src/core/install.js:4:19)
at file:///D:/Scratch/TypeSpec/node_modules/@typespec/compiler/dist/src/core/cli/cli.js:157:95
at Object.handler (file:///D:/Scratch/TypeSpec/node_modules/@typespec/compiler/dist/src/core/cli/utils.js:16:16)
at file:///D:/Scratch/TypeSpec/node_modules/yargs/build/lib/command.js:206:54
at maybeAsyncResult (file:///D:/Scratch/TypeSpec/node_modules/yargs/build/lib/utils/maybe-async-result.js:9:15)
at CommandInstance.handleValidationAndGetResult (file:///D:/Scratch/TypeSpec/node_modules/yargs/build/lib/command.js:205:25)
at CommandInstance.applyMiddlewareAndGetResult (file:///D:/Scratch/TypeSpec/node_modules/yargs/build/lib/command.js:245:20)
at CommandInstance.runCommand (file:///D:/Scratch/TypeSpec/node_modules/yargs/build/lib/command.js:128:20) {
errno: -4071,
code: 'EINVAL',
syscall: 'spawn'
}
It seems similar to an error mentioned here: https://blogs.namitoyokota.com/error-spawn-einval
Could you please look into it and see if it will require similar resolution?
Edition	Windows 11 Pro
Version	23H2
Installed on	6/30/2023
OS build	22631.3527
Experience	Windows Feature Experience Pack 1000.22700.1003.0
Reproduction

Create new directory
Execute tsp init with defaults (see Getting Started)
Execute tsp install

Checklist

[X] Follow our Code of Conduct
[X] Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

I have confirmed that manually adding shell: true resolved the problem. Will be submitting PR shortly.

No need for action. Issue related to https://github.com/microsoft/typespec/pull/3243


feat: configure smart detection rules

Add variable for configuring smart detection rules.
Default value of variable matches the default rules that are automatically created by Azure.

Tests pass 🎉


sourcemaps have empty mappings and names

I'm having some issues with mappings and names it seems. Here is my current setup. Let me know what other info would be helpful to solve. It seems that sourcesContent paths are wrong but I'm not sure?
Directory Structure
dist
--css
----style.css
----style.css.map
src
--scss
----abs
----bourbon
----style.scss

style.css
.all-my-complied-scss-files-styles {}
/*# sourceMappingURL=style.css.map */

style.css.map
{
"version":3,
"file":"style.css",
"names":[],
"mappings":"",
"sources":["style.scss"],
"sourcesContent":["@import \"bourbon/bourbon\";\n\n@import \"abs/colors\",\n        \"abs/variables\";\n\n@import \"settings\";\n@import \"../bower_components/foundation/scss/foundation\";\n@import \"../bower_components/foundation/scss/normalize\";\n\n@import \"abs/abs\";\n\n@import \"custom\",\n        \"pages\",\n        \"apps\";\n"],"sourceRoot":"/source/"
}

Gulp Task
gulp.task('sass', function() {
    return gulp.src(sources.sass)
        .pipe(sourcemaps.init())
            .pipe(sass({
                outputStyle:'compressed'
            }))
        .pipe(sourcemaps.write('.'))
        .pipe(gulp.dest('dist/css/'))
        .pipe(gulpif(state === 'watch', livereload()));
});

while there are still issues with sourcemaps (https://github.com/dlmanning/gulp-sass/pull/220), sourcemaps are not empty now (check the 2.x branch if you have issues with the latest npm)


feat: updating repo

Moving repo to latest standards... I'll list shortly all changes

So... I am planning on changing the internal functioning of synchronize in order to avoid using subprocess if possible, as well as making atomic tests. There are Python packages that will allow us to do precisely these operations.
Pinging @MaxJPRey @greschd for visibility.
The purpose of this PR was to align the repo to other Ansys repos mainly.


Bug: Strange error when scrolling through a line containing substring ['%']?

Self Checks

[x] I'm using the latest lualine.
[x] I didn't find the issue in exsisting issues or prs.

How to reproduce the problem

You will need to create a lua file, with lua LSP Client sumneko/lua-language-server attached.
The lua file should contain a lua table like this:window = {
  mappings = {
    -- root behaviour.
    ['-'] = 'navigate_up',
    ['<C-]>'] = 'set_root',

    -- tree itself.
    ['R'] = 'refresh',

    -- open files.
    ['<2-LeftMouse>'] = 'shift_M_open',
    ['<cr>'] = 'shift_M_open',
    ['w'] = 'picker_open',
    ['o'] = 'macOS_open',
    ['%'] = 'open_vsplit', -- THIS LINE TO BE SPECIFIC
  }
}

Move your cursor upward until it is located at the line containing the substring ['%'].

Expected behaviour
Do nothing.
Actual behaviour
An error occurred:
Error executing vim.schedule lua callback: ...acker/start/lualine.nvim/lua/lualine/utils/nvim_opts.lua:77: E539: Illegal character <'>
stack traceback:
        [C]: in function 'nvim_win_set_option'
        ...acker/start/lualine.nvim/lua/lualine/utils/nvim_opts.lua:77: in function 'setter_fn'
        ...acker/start/lualine.nvim/lua/lualine/utils/nvim_opts.lua:50: in function 'set_opt'
        ...acker/start/lualine.nvim/lua/lualine/utils/nvim_opts.lua:74: in function 'set'
        ...nvim/site/pack/packer/start/lualine.nvim/lua/lualine.lua:422: in function 'refresh'
        ...nvim/site/pack/packer/start/lualine.nvim/lua/lualine.lua:343: in function <...nvim/site/pack/packer/start/lualine.nvim/lua/lualine.lua:342>
Press ENTER or type command to continue

Minimal config to reproduce the issue

use {
  'nvim-lualine/lualine.nvim',
  requires = {
    'kyazdani42/nvim-web-devicons',
    {
      'SmiteshP/nvim-navic',
      requires = 'neovim/nvim-lspconfig',
      config = function () require('nvim-navic').setup{ separator = '  ' } end
    }
  },
  config = function ()
    local navic = require('nvim-navic')
    require('lualine').setup {
      options = {
        theme = 'palenight', -- Purple
      },
      sections = {
        lualine_c = { 'filename', { navic.get_location, cond = navic.is_available } },
        lualine_x = { 'encoding', 'filetype' },
      }
    }
  end
}

Aditional information
Reasoning: I guess the char % might have a special meaning to the next char that follow, thus causing the error. E.g. it escapes the single quote '.

and if you look closely, you will also find that the left-curly-braces, i.e. {s, showing in the image is bolded: (ignoring the cat which is from another desktop program.)

It's because of nvim-navic it needs to escape % in it's output as they have special meaning in statusline.

@shadmansaleh Thanks for the explanation, let me report it there. Closing.


Constantly pushing TrackEnd events

After calling stop once, the player will continue to send TrackEnd for every song that starts via play.
Here is an example of my logs, showing that running stop once will instantly skip the entire queue.
My event hook handler is as simple as
def event_hook(self, event):
    self.logger.debug("event hook fired %s", event)
    if isinstance(event, wavelink.TrackEnd):
        event.player.next.set()

My queue handler un-sets player.next and will block until a new song enters the queue. Once it does, it'll play the song and then wait for player.next to be set again.
The event_hook is instantly firing TrackEnd, which in turn sets player.next, and clearing out the entire queue.

Can't repro but will keep an eye out thanks.

Still haven’t had any issues with this, and as the websocket was update recently I can assume this bug is gone. Feel free to open another issue if this continues to happen.


Automatic ABR quality restrictions based on size

Have you read the FAQ and checked for duplicate open issues?
This was discussed as a part of #565, but the limit based on video container size wasn't implemented.
Is your feature request related to a problem? Please describe.

A functionality that Dash.js and hls.js have is the ability to limit which quality levels are selected based on video element size.
Describe the solution you'd like

On the ABR settings, an extra flag could be added to instruct the ABR manager to limit the quality level based on the video element. For example:
{
  abr: {
    capLevelToPlayerSize: true
  }
}

Or:
{
  abr: {
    limitBitrateByPortal: true
  }
}

Those are the options used in Dash.js and hls.js. You can choose any name fits for this project.
Describe alternatives you've considered

Without this feature, a possible solution would be to introduce a ResizeObserver on the video element to react to changes in size and dynamically set the ABR restrictions on Shaka player.
Additional context

This would allow saving time (and potential problems with the orchestration of the ResizeObserver and the dynamic setting of restrictions) that can arise in the implementation of a video player that handles bandwidth in a smart way not to load a video quality that is higher than required at a given moment.

ResizeObserver is not available on Edge (until it becomes Chromium-based), IE (which we will drop support for some day), or Safari (which is a bigger issue).  If we restrict ABR based on the size of the video element at the level of Shaka Player, our options seem to be limited to:

ResizeObserver (except on IE, Edge, Safari)
Polling getClientRects() (fallback for IE, Edge, & Safari perhaps?)

I worry about the expense of polling, especially on embedded devices.
A cheap and easy time to check the size is when we go into or out of fullscreen mode, which there are universal events for.
It's not clear to me in what other circumstances an application would change the size of the video element.  But it does seem clear the application always knows when that happens, because it is the thing changing the size of the element.
So I have always felt that the most efficient way to do this is at the app level.  But I'll look into what dash.js and hls.js do.  Perhaps there's something else I've overlooked.

hls.js polls the video size once per second to implement the capLevelToPlayerSize option.  They use clientWidth and clientHeight to determine the size.

dash.js adds a resize event listener on the window, which only reacts to changes in the window size, not other layout changes.  This could be useful in some cases, but it wouldn't, for example, be able to account for pure app-driven layout changes, such as something equivalent to YouTube's "theater mode" button.
It's not obvious that this is connected to their limitBitrateByPortal option, though.  It seems that their approach is just to recompute the size every time they make an ABR decision, which is pretty clever compared to polling every second.

Neither relies on ResizeObserver, which I've just found will be supported in Safari TP according to caniuse.com.
One last note from my research: I've also discovered that there is a resize event on the video element, which only reacts to changes in the decoded frame size, not layout changes.  This is equivalent to getting an event fired when you make an ABR decision, so this is misleading and not useful.

In general, I'm in favor of this option, and I'm in favor of the default being true.  It seems very helpful to the service provider to help them more easily avoid wasting bandwidth on higher resolutions just to downscale them on the device, not to mention saving the end-user's battery.
An event-driven solution, such as ResizeObserver, would seem ideal.  It would require no changes to the plugin interface, just a new option.  But we probably can't get that on all platforms, especially when we consider TVs.
I'd really like to avoid polling, since polling turns out to be surprisingly expensive in specific cases on devices.  (See #2252)
Another alternative is to make AbrManager instances aware of the video element and measure its size every time it makes a decision, as dash.js does.  This is probably our best option for robustness, but may require changing the plugin interface.

This feature will be amazing! 🥳
I think a mix of ResizeObserver and a fallback could be a great solution to get the player size 🤔
In the case of a dash manifest with 720p + 1080p streams and a player resolution of 850p, we could add a parameter to choose worst/best quality if we don't match the exact resolution.

Thanks @TheModMaker to point me to this issue. He suggested using:
player.configure({
  	abr: {
		restrictions: {
  			maxWidth: 400,
                        maxHeight: 300
  		}
  	}
  });

to limit the size of the video choosen by the abr-manager. This works inside a webpage which is not changing in size, but doesn't work for example when switching to fullscreen-mode.
In my opinion a polling or continuous tracking of size-changes isn't necessary, it would be greate if maxWidth and maxHeight just adapt when shaka.abr.SimpleAbrManager.chooseVariant is called the next time.

You make a good point.  That would update the restrictions every abr decision interval, which by default is every 8 seconds.  That would be sure to be more performant than polling, and at such a long interval, probably close enough in battery performance to listening for size change events.

I fixed the problem using restrictions:
this.player.configure({
    restrictions: {
        maxHeight: height
    }
});

Where height comes from a window resize event.

Did any of you manage to set ABR restrictions that adapt to player size?

ResizeObserver is not available on all supported platforms, but is now available on all evergreen browsers.  And the platforms that don't support ResizeObserver (TVs, set top boxes, etc) also don't support resizing.
So I think it would be reasonable to add this as a built-in feature, inside something like if (window.ResizeObserver).

@Doolali the problem is that the restrictions might actually prevent playback if the video element is smaller.
This is not relevant for full screen players, but for example for small preview videos.
In a perfect world I would like to give a suggested or target resolution where shaka can for example decide to use a larger version if the screen is around 1000px in height, it could choose 1080p.

If you use abr.restrictions instead, playback will still be possible.  These are restrictions on adaptation, whereas restrictions is a hard playback restriction (meant to match up with DRM policies the player wouldn't know about).
@EyMaddis, in your example, if abr.restrictions.maxHeight is set to 1000, but the smallest resolution available is 1080p, then 1080p will still be played.


System test: Extend existing test with notification to a single energy supplier

As energy suppliers now receive notifications for charge information and charge prices, our existing system test which currently creates a new subscription and verifies the confirmation sent to the grid access provider, should be extended to include a verification step that ensures that (a single) energy supplier receives a notification (D18) with the new subscription.
Tech note:

It would be a really good idea that to use an energy supplier that isn't used by any teams for manual testing.

Acceptance criteria

[ ] 1 Given a new subscription is created by the system test ( as grid access provider )
And the grid access provider has peeked the related confirmation
When an energy supplier peeks
Then a Notification (Charge Information D18) is received and it contains the Charge ID for the new subscription.

To verify AC is fulfilled; have a look at the test in BusinessProcessTests() and perhaps run it :smile:
Deployed here, where the extended system test was executed:


Allow scrolling for long list of options.

With a large dataset, displaying all the options without scrolling or pagination is a bit overwhelming.
It is not currently possible to allow scrolling with css alone on the current template since the filter and (un)check all controls are in the same ui > li as the options.
When I get a chance I'll submit a PR separating out the option list from these controls, to allow setting scrolling with css.
I'm curious what your thoughts are on adding this option via the directive's attributes (maybe a max-height) or whether it should be up to the user to implement themselves via css.

I did this with css in my project as far as I can remember. Should be straightforward.

@amitava82 you mean without changes to the default template? Maybe I'm being dense, but I can't see how to do it. Working on a PR at the moment with a fix, but if you have a pure CSS solution, would be excited to see it

Well... what I was trying didn't work, as it would require throwing out bootstraps dropdown-list which I'm not (yet) willing to do.
I've been trying with no luck to get the filter input and (un)select buttons to be "sticky" with variations of position:fixed, but that is not going to work

Well, I got it working in my project, but it feels pretty ugly and I'm a reluctant to merge in right now without a bit more thought.
Pretty much, I created a nested list inside the .dropdown-menu

and then duplicated a bunch of bootstrap styles to make it look right:
(from my code using LESS)
.dropdown-menu ul {
    list-style-type: none;
    margin: 0; padding: 0;
    max-height: 200px;
    overflow: scroll;
    & > li > a { // from .dropdown-menu > li > a
        display: block;
        padding: 3px 20px;
        clear: both;
        font-weight: normal;
        line-height: 1.428571429;
        color: #333;
        white-space: nowrap;
        padding: 3px 10px;
        cursor:pointer;
    }
    & > li > a:hover { // from .dropdown-menu > li > a:hover
        color: #262626;
        text-decoration: none;
        background-color: #f5f5f5;
    }
}

I'm going to leave this issue open for now, and use that in my personal project, and take some time to reflect on whether its an ok approach.

Since the plugin supports custom template, one should be able to provide own template for unique look. I've updated example with long dropdown and custom template.

This is exactly what I did. I probably should've put that demo together myself, as I already had all the pieces. Thank you for adding it.
Do you think it makes sense to somehow work this into the directive? That is, ship it with multiple templates built in, and an attribute to do the toggle? If not, I think its time to close this issue ;-)
Another reason for my custom template: I use font-awesome icons rather than glyphicons. Not sure if we should, or how we could integrate some flexibility there,  but I suppose thats a topic for another conversation.

I'd leave that to user. But sure if you have some templates then those can be added as an example.
With custom template, user has complete flexibility in the look n feel.

OK, I'll consider getting some custom templates up there. At the very least, I'd like to help make the documentation / examples a bit prettier :-) I'll open an issue on that when I'm ready to start thinking about it.


Shall we rename the master branch to main?

Hey @piotr-oles!
How would you feed about us renaming the master branch to main?
Feature motivation
Many communities, both on GitHub and in the wider Git community, are considering renaming the default branch name of their repository from master. GitHub is gradually renaming the default branch of their own repositories from master to main.
Feature description
Renaming the branch.
Feature implementation
Following the instructions here is super simple: https://github.com/github/renaming
I did this on ts-loader today and it was super straightforward.  Renaming the branch and then copy-pasting the command to change my local branch and I was done.  Would recommend!

Hi! We can do this, no problem :)
The only thing to keep in mind is that our semantic-release configuration points to the master branch (release.config.js), so we have to update it as well.

I'm happy to do this - I'll make sure I tackle release.config.js as well

okay let's tackle this!

:tada: This issue has been resolved in version 6.2.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 7.0.0-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket: