ibus-engines.typing-booster-unwrapped: 2.6.4 -> 2.6.6

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/ibus-typing-booster/versions.
meta.description for ibus-engines.typing-booster-unwrapped is: '"A typing booster engine for the IBus platform"'.
meta.homepage for ibus-engines.typing-booster-unwrapped is: '"https://mike-fabian.github.io/ibus-typing-booster/"
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.6.6 with grep in /nix/store/1p313y46v2j8rw50rgkrnqswvn2rasbh-ibus-typing-booster-2.6.6

directory tree listing: https://gist.github.com/e54d0946dbb82f1df7a198e4ca85b476

du listing: https://gist.github.com/837f14402ce7876d8d032d7386df0876

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
ibus-engines.typing-booster
ibus-engines.typing-booster-unwrapped

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1p313y46v2j8rw50rgkrnqswvn2rasbh-ibus-typing-booster-2.6.6 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A ibus-engines.typing-booster-unwrapped https://github.com/r-ryantm/nixpkgs/archive/62c55bc70142a4d21c712079a16c6a6c391fe7ea.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1p313y46v2j8rw50rgkrnqswvn2rasbh-ibus-typing-booster-2.6.6
ls -la /nix/store/1p313y46v2j8rw50rgkrnqswvn2rasbh-ibus-typing-booster-2.6.6/bin

cc @ma27 for testing.

Backported as 974bbd1217aeaf01ee1539d2947cba356b6553a5.


integrating leonid pull into dev

The changes look good to me, but I cannot approve my own pull request. The conflicts also need to be mreged before the pull request can be approved.


Error regarding addon profiles for Azure Kubernetes Service in China North 2

Azure China regions have different capabilities when it comes to Azure Kubernetes Service (AKS). In particular they support different addon profiles - omsagent, aciConnectorLinux, kubeDashboard, azurepolicy, etc. As an example, China East 2 supports omsagent with log analytics, while China North 2 does not.
Unfortunately it seems even specifying these addons as disabled (enabled: false) causes Azure to reject these requests with error messages like below.
error: creating Managed Kubernetes Cluster "test" (Resource Group "test-rg"): containerservice.ManagedClustersClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="OperationNotAllowed" Message="Addon 'azurepolicy' is not supported in this cloud environment."

If addon profiles are completely omitted in the Pulumi application, then the request still fails because the addon profiles are filled in automatically as disabled which still causes the request to fail.
Example request when addon profiles are omitted
Code
const k8sCluster = new azure.containerservice.KubernetesCluster(projectName, {
    // ...

    // addonProfile: {
    //     omsAgent: {
    //         enabled: false,
    //     }
    // },
});

Request to azure api
Snippet showing addon profiles are filled in automatically as disabled.
"addonProfiles": {
    "aciConnectorLinux": {
        "enabled": false,
        "config": null
    },
    "azurepolicy": {
        "enabled": false,
        "config": null
    },
    "httpApplicationRouting": {
        "enabled": false,
        "config": null
    },
    "kubeDashboard": {
        "enabled": false,
        "config": null
    },
    "omsagent": {
        "enabled": false,
        "config": null
    }
}

Workaround
omsagent is allowed in the request as enabled: false, so the workaround here is to specify that addon in the AKS input arguments. This causes the other addons to be omitted and the cluster gets created successfully in China North 2.
Here's an example:
export const k8sCluster = new azure.containerservice.KubernetesCluster(projectName, {
    // ...

    addonProfile: {
        omsAgent: {
            enabled: false,
        }
    },
});

Closing this based on the workaround above.


propress

i have the difficulity when i run the prepare.py.please tell me how to solve the problem that some datas couldn't change the .npy. looking forward to your letter.

can you show me the error message?

see config_training.py for set data paths.
or using https://github.com/xairc/lung_nodule_summary/prepare.py

thanks!

The first epoch of our training network was 0.079. Is this a normal result of training?

may be it takes about 1 or 2days.


Develop Data Needed DN_0080_5859_wmi_activity

Develop Data Needed DN_0080_5859_wmi_activity (Event ID 5859) using this template and related Logging Polic (if there is any) using this template.

already developed


Added mergeOptions in gateway

Signed-off-by: hritikgupta<EMAIL_ADDRESS>

@hritikgupta Hi, thanks for the contribution. Just wonder if you could include a sample on using the mergeOptions in the test file?

/azp run

/azp rerun

/azp run

Solved in #82


Changes for ssh tests and wait for server status

Changes for ssh test cases and wait for server status so that test cases
may not leave volume behind.

Good to merge. Following builds with ssh code changes passed
http://jiocloud.rustedhalo.com:8080/job/pkg_test_build/64/console
http://jiocloud.rustedhalo.com:8080/job/puppet_rjil_pkg_test/63/console


BRB 181 FWU routing

Description
Tests that a user can find FWU content in the learning store.
And can also access it.

Links to Tickets or other pull requests
Epic:
https://ticketsystem.dbildungscloud.de/browse/BRB-181
Initiative:
https://ticketsystem.dbildungscloud.de/browse/BRB-178
PR schulcloud server:
https://github.com/hpi-schul-cloud/schulcloud-server/pull/3975
PR dof app deploy:
https://github.com/hpi-schul-cloud/dof_app_deploy/pull/485

Changes
Added new feature, steps and Page to end to end tests.

Deployment

New Repos, NPM packages or vendor scripts

Approval for review

[ ] All points were discussed with the ticket creator, support-team or product owner. The code upholds all quality guidelines from the PR-template.

Notice: Please remove the WIP label if the PR is ready to review, otherwise nobody will review it.

this tests should be done new in cypress
on this repository, lernstore is not connected to edu-sharing
tests here run by tags, but there is no runner for new tag "@lernStore", so actually this test is skipped

Outdated Repo


improve detector

can now give different via_stacks, and move the vias w.r.t. each other

Thank you Simon!


DataGrid styling with ThemeProvider

Changes
The latest major version of @mui/x-data-grid shipped with some breaking changes to styling. We must now explicitly set the colours for table header etc.
This has been achieved for both dark and light mode using the ThemeProvider component so that changes apply globally to all usages of DataGrid. I have added a story for ThemeProvider in storybook to show its effect on DataGrid.
While here, I also addressed some other feedback from @Sowbhagya-ipg that she didn't want to see cell outlines on cell click. This has been turned off globally.
UI/UX
In light mode, table header, content and footer should be white.

In dark mode, table header, content and footer should be black.

Clicking a cell no longer generates an outline.
Before:

After:

Release notes

Resolved compatibility bug with latest version of @mui/x-data-grid where the table header / content / footer styling did reflect the correct background colours.
Resolved compatibility bug with @mui/x-data-grid where we do not with to see a cell outline on cell focus.

Testing notes
Can be tested using the Genera/ThemeProvider/DataGrid story in light and dark mode.

[x] Relevant labels added to the PR.
[x] ~Appropriate tests have been added.~
[x] Lint and test workflows pass.

Matt gave me a demo. Looks Good!


Mixed boundary conditions for static linear elastic problem

Hello, everyone.
Thanks a lot for MFEM.
I try to solved the static problem of linear elasticity.
If I want to fix the horizontal component of the displacement (on the boundary) and set tangential stress (Sigma_xy)  to zero, I should use the code like:
GridFunction x(fespace);
x = 0.0;
Array<int> ess_tdof_list, ess_bdr(mesh->bdr_attributes.Max());
ess_bdr = 0;
ess_bdr[1] = 1;
ess_bdr[3] = 1;
fespace->GetEssentialTrueDofs(ess_bdr, ess_tdof_list, 0);
VectorArrayCoefficient f(dim);
Vector pull_force(mesh->bdr_attributes.Max());
pull_force = 0.0;
f.Set(0, new PWConstCoefficient(pull_force));
f.Set(dim - 1, new PWConstCoefficient(pull_force));
LinearForm *b = new LinearForm(fespace);
b->AddBoundaryIntegrator(new VectorBoundaryLFIntegrator(f));
b->Assemble();
a->FormLinearSystem(ess_tdof_list, x, *b, A, X, B);

Am I right? The full example I posted here: https://github.com/vasily-golubev/mfem_static_example/blob/main/static_elasticity.cpp

This looks correct to me.
In particular the call fespace->GetEssentialTrueDofs(ess_bdr, ess_tdof_list, 0); will extract the degrees of freedom corresponding to the x-components on boundary attributes 2 and 4 and then FormLinearSystem will make impose zero Dirichlet b.c. on them.

Great, many thanks.
I used the ElasticityIntegrator to solve 2D static elastic problem. However, as far as I understand, this class implicitly implies the plain strain problem (Dz==0, D-displacement). If I want to describe the plate behaviors (plain stress problem, Sigma_zz==0, Sigma - stress tensor), I have to change mechanical properties as: https://fenics-solid-tutorial.readthedocs.io/en/latest/2DPlaneStrain/2D_Elasticity.html (the end of "Governing equations" section).
Am I right?
Maybe it is usefull to add the other constructor like ElasticityIntegrator(lambda, mu, true\false for stress\strain problem)?

Sorry, if it is not important, the issue can be closed. @tzanio


Required class change causes issues when migrating

I think people would appreciate if the changes to the Required class from flask_security.forms could be somehow be listed as a breaking change, removed in general (if people should use wtf's DataRequired instead) or marked deprecated. Right now using Required() on a form field causes a generic error like this which is not ideal:
  File "~/Project/.venv/lib/python3.7/site-packages/flask_security/forms.py", line 76, in __init__
    self._original_message = kwargs["message"]
KeyError: 'message'

Interesting - yes - a change for i18n I made assumes that every validator has a 'message' keyword - which all the current uses do. Is there a use case to not have a message? I can easily throw an exception which would at least tell user what is going on...

Is there a use case to not have a message?

There's no message in the official documentation(s), that's what many use. I think it defaulted to "This field is required" as well, but I'm not sure.

got it - I'll make it backwards compatible

Thanks!

thank you... I/we need all the testing we can get - there are so many changes - mine as well as all the PRs that have never been released from the mainstream FS.


Update service-gateway-onprem-manage-oracle.md

Updated on-prem gateway instructions for Oracle DB to reflect new method to install and configure Oracle clients for MS tools with the Oracle Client for MS Tools.

#sign-off

@arthiriyer - can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks, @alexkeh
#sign-off

Hey, @alexkeh -- are you a MSFT employee, vendor, or contractor? If so you should be editing articles in the private repo. Start here:
https://aka.ms/savetime
That gets you into the private repo.
Enter the URL of the article you want to edit.

@maggiesMSFT I work at a partner. company, Oracle. I am not a MS employee, vendor, nor contractor.
Nonetheless, I tried to access the site with my MS credentials. It says I don't have permission to the resource.

@maggiesMSFT I work at a partner. company, Oracle. I am not a MS employee, vendor, nor contractor.
Nonetheless, I tried to access the site with my MS credentials. It says I don't have permission to the resource.

Hi, @alexkeh -- got it. Thanks for explaining and for updating the docs!


undefined class ActiveMerchant::Billing::PaypalExpressResponse

added initializer to require appropriate ActiveMerchant files
[fixes #32]

Beautiful, thanks! Added in @6ae311446800e72a05e8a9647e445fe46a7adbd0.

I don think this fix got merged

Oops, it got merged, the push didn't go through though. How about now?

Looks good, thanks!
On Tue, Feb 14, 2012 at 10:30 PM, Ryan Bigg
<EMAIL_ADDRESS>wrote:

Oops, it got merged, the push didn't go through though. How about now?

Reply to this email directly or view it on GitHub:
https://github.com/spree/spree_paypal_express/pull/33#issuecomment-3975262


chore: add docker to codespaces

Tip from https://github.com/github/feedback/discussions/14542#discussioncomment-2625978

 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.


bug

Error occurred when executing AnimateDiffSampler:
CUDA error: invalid configuration argument
CUDA kernel errors might be asynchronously reported at some other API call, so the
stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.
when i use any workflow，this bug appears。
how to debug this?plz

I used two computers run this , with gpu 3090,4090, and both had this problem

This is a knows issue with xformers, see #29. You should disable xformers with --disable-xformers on startup.


Plugin causes Homebridge to shutdown

Describe The Bug:

Homebridge shutting down/restarting continuously for the past few hours. Determined that this plugin was causing the issue, as there have been Enlighten issues all day as well and I suspect this plugin needs some additional error handling work when the service is disrupted/unavailable
To Reproduce:

Enable the plugin while Enphase is down
Expected behavior:

Logs:
Show the Homebridge logs here, remove any sensitive information.
```[4/5/2024, 5:26:20 PM] [homebridge-enphase-battery] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.
[4/5/2024, 5:26:22 PM] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[4/5/2024, 5:26:27 PM] [HB Supervisor] Restarting Homebridge...
[4/5/2024, 5:26:27 PM] [HB Supervisor] Starting Homebridge with extra flags: -I -P /volume1/homebridge/node_modules --strict-plugin-resolution

**Plugin Config:**

```json
Show your Homebridge config.json here, remove any sensitive information.

Screenshots:

Environment:

Plugin Version: 2.0.2
Homebridge Version:
Node.js Version:
NPM Version:
Operating System:

Thanks for the report and sorry for the trouble.  I'm definitely not a Javascript dev, so I just hacked together something that could work.  I solved this problem personally by running it as a bridge so things are more isolated.  If you have time and can offer a PR, I'm happy to take contributions for ways to improve this.


fold rest of class names but not the first one

It's possible to fold all but no the first one, to get a reference what is the basic class name for identify to naked eye.
example:
from:

to:

on this case, i can see my "general" class name then folded...
by default all is folded, so, i can't indentify unless you click the class or selector.

Yes, there's an example at the home page for when you want to fold after set of characters.
Also it's easier if you use the registered commands to fold/unfold
feel free to reopen issue if needed 👍🏻


Question: About posibility of using Entt with runtime (script defined) components.

Hi, I'm working on a hobby game engine in my spare time and I have a use case that I believe should be pretty common.
I would like to define new components in scripts but I want them to be defined in a way that makes use of the ECSs pros, keeping the components as only data and tightly packed in the memory and I wouldn't want to reinvent the wheel and implement an ECS just for this.
What I want to be able to do is to dynamically define components/structs by creating some sort of DynamicComponentDefinition class that takes a list of fields and types and "reinterprets" a given buffer like it would be a normal structure where I can access the fields by name.
I've already implemented something like that with proper alignment and packing and it works pretty well on it's own. (Keep in mind this just reinterprets a buffer as a buffer of "dynamic structs" but it does not own it).
This seems at odds with Entt where the registry needs to know at compile time the structure and size of a component in order to create the associated component storage.
Even if my DynamicComponentDefinition definition would own the buffer I cannot know at compile time it's size and allocating the buffer for each component separately having a uint8_t *buffer member (instead of uint8_t buffer[N]) defeats the purpose of dense component storage that is cache friendly, each component only storing a pointer to the actual data which could be scattered in memory.
I hope this make sense for anyone reading this.
Is there a way to have this kind of runtime defined components with Entt?

Correct me if I'm wrong, but if you don't know the size of the buffer at compile-time, all you can do is either dynamically allocat it or prepare pools for different sized buffers to use when needed (like, a pool for objects up to 50b, one for objects up to 100b, and so on). I don't see how you could that otherwise, so feel free to point me towards the solution you would use instead if I'm missing it.

The way I was considering implementing something like this is to have some sort of freelist allocator or in this case a packed freelist allocator, for the sake of simplicity something like this:
template <typename Entity>
struct ComponentStorage
{
    ComponentStorage(u32 typeSize, bool trivialConstruct, bool trivialCopyConstruct, bool trivialDestruct);

    bool hasComponent(Entity entity);
    u8* getComponentBuffer(Entity entity);

    std::vector<Entity> sparse;
    std::vector<Entity> dense;
    std::vector<u8> buffer;

    u32  typeSize : 29;
    bool construct : 1;
    bool copyConstruct : 1;
    bool destruct : 1;
};

and for each type of "dynamic" component I will have one of these ComponentStorage associated with it via a type id or some sort of hash.
Then I'd implement a "dynamic component definition" something like this:
class FieldDefinition
{
public:
    template <typename T>
    void get(u8* buffer, T& value) const;
    template <typename T>
    void set(u8* buffer, const T& value) const;

private:
    FieldDefinition(size_t offset, size_t alignment, size_t size);

    size_t offset;
    size_t alignment;
    size_t size;

    friend class DynamicComponentDefinition;
};

class DynamicComponentDefinition
{
public:
    DynamicComponentDefinition() {};

    template <typename T>
    void addField(FieldHash fieldHash);
    size_t pack();
    size_t size() const noexcept;
    size_t alignment() const noexcept;

    std::optional<FieldDefinition> getField(FieldHash fieldHash);

    template <typename T>
    void get(u8* buffer, FieldHash hash, T& value) const
    template <typename T>
    void set(u8* buffer, FieldHash hash, const T& value) const;
    u8* next(u8* buffer) const noexcept;

private:
    std::unordered_map<FieldHash, FieldDefinition> fields_;
    size_t size_{ 0 };
    size_t alignment_{ 0 };
};

And this will be used to "reinterpret" the buffer in the ComponentStorage as my "dynamic" component, that provides a way to retrieve fields based on their hash or name.
I could go as far as implement the whole ECS based on ComponentStorage and have the rest of the "native" components just be a thin wrapper template over it.
Now, I wouldn't want to implement this from scratch as Entt is already way better than I could ever make but given it's compile time nature, I'm not sure if it is possible to integrate this kind of feature/behavior.

Got it. So, all you need is in fact a way to create multiple pools of the same type and to combine them in a view or view-like object, right?

Yes, I guess so, I think that might be enough, if I can create pools of the same type ComponentStorage, each of these holding buffers for different DynamicComponentDefinition "dynamic" components and a way to create views of combinations of them or combinations of native compile time components and "dynamic" ones, than I could easily use Entt with scripting languages and define my own components inside the scripting language and these will be cache friendly, more or less, same as the native ones.

I assume you're using the last stable tag. In this case, all pools are associated with compile-time type. So, all you can do is to create a bucket for runtime types and us it from your scripting env.
With the upcoming release instead, things should change quite a lot. It's not a problem for itself to create pool and to associate them to runtime identifiers. Though, the problem so far was  that of combining them with standard views. The ::view function cannot really accept also these idenfiers and there was no way to combine views.
This should be solved with something like this in the next release(s):
auto v1 = registry.view<foo, bar>();
auto v2 = registry.view(runtime_identifier);
for(auto entity: v1 | v2) { ... }

Could it work? OFc you don't have it upstram yet, so probably this doesn't answer the question. However, you've a use case, so probably you're a good candidate for asking a feedback. 🙂

The ability to create your own storage, manage it externally, then use it to build a view to combine with other views in a pack is now on master.
I'm closing this issue because you should have everything you need to do what you ask. Feel free to continue the discussion here or reopen the issue if needed.
Thanks!

Sorry for late reply, somehow I missed the last two notifications on this issue. Thanks for adding this to the library , I'll check it out.

auto v1 = registry.view<foo, bar>();
auto v2 = registry.view(runtime_identifier);
for(auto entity: v1 | v2) { ... }

I'm confused how this works. How is runtime_identifier created?

It's up to the user in this case @xharris name hashing or any other generator.


[Feature Request] Support versioned scripts AFTER repeatables

I would like to be able to run post-repeatable one time scripts (or versioned upgrades).
My scenario is simple - I have a table filled by a function. If the function changes and upon my decision I want to refill the table. The function is created as part of repeatables - hence cannot be referenced in an upgrade script before it is changed.
I know there are many workaround, but none of them is perfect:

run 2 separate migrations - 1 to update the function, another to call it in a versioned script. this is inconvenient and lacks the "connection" or "context" between the 2.
have the upgrade script turn on a flag somewhere and have a callback to check this flag on every migration. while this sound reasonable it seems a waste to me if this check would be positive seldom, especially if the check itself is time consuming and not just a flag.
change the function in the versioned script (as well as in repeatables). might work, unless this function uses 10 other functions and then it becomes a mess.
do not refill the table using flyway - but do it manually after the migration finishes. this adds manual work - which flyway should help me avoid - so not a good one.
using a callback with a placeholder which would only act if the placeholder is true (false by default) and set this placeholder using an environment variable only when needed. a bit cumbersome but would probably work.

Basically would have been nice to add a script which would run ONCE (versioned) AFTER the repeatables are done.
Whether they affect the schema version or not - makes little difference to me (but they probably should).

If I understand your scenario correctly, you'd like to:

Run a versioned migration to create a table
Run a repeatable migration to define a function that fills the table
Somehow execute the function to fill the table

Then, for your next deployment:

Make a change to the function
Somehow re-execute the function to fill the table

One approach could be to include the function definition and execution in the same repeatable migration. When you change the function, the entire script, including the function execution, will be re-run.
Function FillTable()
  // Do something
End

FillTable()

Perhaps it's undesirable to have the function definition and execution in one migration. Note that for Flyway 6.2 we're working on functionality to force repeatable migrations to run, even when unchanged (https://github.com/flyway/flyway/issues/1453). This will allow you to define a repeatable migration which simply executes the function. You can then decide whether to execute it upon migrate.
I assume the afterMigrate.sql callback (https://flywaydb.org/documentation/callbacks.html#sql-callbacks) isn't desirable for you as you'd like to execute the function only when changed, not after every migrate.
Ultimately I suppose this a script dependency and ordering problem. We've encountered a few instances of this (e.g. https://github.com/flyway/flyway/issues/2541#issuecomment-547358068). We're still thinking of a good way to solve the general problem.
Is this of any help to you?

It is similar to the extended info provided in #2541 , but I think my solution is much simpler than specifying execution order based on input.
I want the execution order to be exactly as it is today (totally makes sense) plus an added execution phase of versioned scripts after repeatables are done.
Not sure it will answer the need of 2541 (function-procedure dependency, for that im actually disabling compile validation in beforeMigrate and then enabling it plus validating in afterMigrate, then compiled object order makes no difference) but in many cases I would like to run a function after it has been created or changed in the same migration run.
You suggested yet another alternative to the 5 I already mentioned, but I think its still a workaround.

Fair enough that none of the proposed approaches are satisfactory. We'll keep this feature request open to see if it gets more support.
Are you able to use any of the workarounds, or are you completely blocked by this issue?

I'm currently using workaround 4 (change the function using flyway, then run it manually) - so I'm not blocked. Since I only have to do it seldom I don't want to invest any efforts in any of the alternatives.

General problem captured here https://github.com/flyway/flyway/issues/2698


Adh ultra ssd

Hi, please review and approve the PR.
Scope: Compute --> Instances --> Azure Dedicated Host --> How-to
Change: Added content to reflect new feature - ADH support for Ultra disks

@vamckMS : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@vamckMS : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Resolved conflict.

@brittanyrowe,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge. Thanks.

Will be doing sign off on June 3 in the afternoon.

Supposed to create this PR on our private repo, mistakenly created the PR on public docs.

@vamckMS, ok to close this PR? Thanks.

Yes please, and can we delete the PR as well?

Yes please, and can we delete the PR as well?

I can only close it.


Login Behavior

If I'm logged in, and go to the home page of this app, then click 'login', I'm taken back to the profile page. This is odd behavior. Why can't I go to the login form and try to login?

I don't feel that it's a common pattern for someone to be able to access the login page after one is logged in? If you are logged in and want to log in with another user, the pattern is usually to logout then login again? Let me know if I'm misunderstanding something or if there's a scenario for this that I have missed:)

This behavior is intentional and is codified in our framework spec: you have to logout before you can log in as another user.

I think the issue is that we don't use template masking to hide the login button once you're logged in. We should do this so you can't see that login option and click it.

Yes, that's something we fix in this example.


Metadata API: Add Key.from_securesystemslib_key()?

I've been playing with repository code / metadata creation and this is a mistake that's bit too easy to make:
sslib_key = generate_ed25519_key()
key = Key.from_dict(sslib_key["keyid"], sslib_key) # key for public TUF metadata
signer = SSlibSigner(sslib_key) # signing key

This works just fine... and results in public metadata that includes your private key (TUF key doesn't handle the private key of course but we allow unrecognised fields in the format). Oops.
We should probably have a function for this use case: The securesystemslib key format might be opaque to us (can't be 100% sure what's in there) but I think in this case making some assumptions about that is better than allowing the above to happen
So something like
from_securesystemslib_key(key_dict: Dict[str, Any]):
    return Key(
        keydict["keyid"],
        keydict["keytype"],
        keydict["scheme"],
        {"public": keydict["keyval"]["public"]}
    )

?

Very good point. Also making it clear in the function name itself whether you are also getting private or just public key.

I'd like to give it a try, pls :)

actually securesystemslib.keys.format_keyval_to_metadata(keytype, scheme, key_value, private=False) probably does what we want? I think adding a helper still makes sense but it could call that instead of trying to parse the values itself.


/console commands appaer in chat

Checks

[X] I confirm that I have searched for existing issues / pull requests before reporting to avoid duplicate reporting.
[X] I confirm that I noted that if I don't follow the instructions, the issue may be closed directly.

Description
I want to disable that admin commands using /console appear in public chat. I have broadcastcommandexecution on false and restarted. But it still sends a message once sending the command. Version: 1.18.2

Setting broadcastCommandExecution to false only disables Minecraft-to-Discord messages. All / commands from Discord will send Discord-to-Minecraft messages, there is currently no option in the config to disable this function.

Setting broadcastCommandExecution to false only disables Minecraft-to-Discord messages. All / commands from Discord will send Discord-to-Minecraft messages, there is currently no option in the config to disable this function.

Could you make one please?

Please try the latest build.

Will try later today

?

Will try later today

It worked


[Feature][Config UI] Config UI needs to support BitBucket

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Like other data sources that Config UI already supports, we need to design the Connetion page and the Blueprint transformation page for BitBucket.
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

https://www.figma.com/file/Eux4Dhorxp7M0TwzOnL6Yh/Config-UI-for-V1.0?node-id=1999%3A10071

I'll take it.

https://www.figma.com/file/Eux4Dhorxp7M0TwzOnL6Yh/New-Config-UI-(wym)?node-id=3828%3A25209&t=ZJNsNfLDEZ60IBLa-1


fix(middleware): log invalid filetype

Fixes #3291

@johnjbarton, I pulled down this change today and it still results in output that does not help the issue.
After this change, the new command line output appears like this:
WARN [middleware:karma]: Invalid file type (), defaulting to js.

Given that output, I cannot ascertain which file is actually offending Karma.


The daily page is broken on mobile

As you can see, the "Daily" page is really broken on mobile. This issue concerns the default theme as well but is it possible to change that in your theme? Plus, this page is not really "material".

Indeed I should have worked on this page long time ago. When I created the theme, I wanted to keep it as is because I liked the "newspaper" style and it make sense ("Daily" evokes newspaper).
But it's time to find a new design for this page, I'll think about something :)

What about something like this app ?
https://play.google.com/store/apps/details?id=com.google.android.apps.magazines&hl=en

Any news? ;)

Working on it, slowly but surely :)
I preferred prioritize the support of Shaarli 9.1.

You mean Shaarli 9.2? ;)

Damn your right, I just noticed that 0.9.2 was out.


[Error during generate()] index out of range in self

I am trying to run the following and getting an error
import lmql
query_string = """
    "Hello [WHO]"
"""

result = await lmql.run(query_string, model="local:gpt2")
print(result)

This is throwing an error:
[gpt2 ready on device cpu]
'NoneType' object has no attribute 'cadam32bit_grad_fp32'
[Error during generate()] index out of range in self

This is a friendly reminder - the current text generation call will exceed the model's predefined maximum length (1024). Depending on the model, you may observe exceptions, performance degradation, or nothing at all.
.../src/lmql/runtime/dclib/dclib_cache.py:600: CacheWarning: CachedDcModel: underlying model <lmql.models.lmtp.lmtp_dcmodel.LMTPDcModel object at 0x2b724a0b0> raised an exception during generation and will thus not be cached: <class 'lmql.models.lmtp.errors.LMTPStreamError'> 'failed to generate tokens 'index out of range in self''
  warnings.warn(msg, category=CacheWarning)

And the cell takes forever to return. Any pointers as to what could be happening?

Hi there. The error message suggests there may be an issue with your installation of bitsandbytes or transformers. Maybe this helps: https://github.com/oobabooga/text-generation-webui/issues/2397

Hi, here's some more info suggestion the problem is with the max length of transformers model getting exceeded (similar to related but non-LMQL posts on this error: https://stackoverflow.com/questions/62081155/pytorch-indexerror-index-out-of-range-in-self-how-to-solve and https://discuss.huggingface.co/t/adding-new-tokens-indexerror-index-out-of-range-in-self/6731)
Here's what I do: first of all, I made a clean conda install with python 3.10.13 and 'pip install lmql[hf]'. Then, I start a server locally with
lmql serve-model
Then I try two things:

I try to run a decorated query

import lmql

@lmql.query
def simply_question(question):
    '''lmql
    "The answer is: [ANSWER]."
    return ANSWER
    '''

answer = simple_question("What is the meaning of life?", model="gpt2", temperature=0.5)

This generates the error, but the server outputs
"This is a friendly reminder - the current text generation call will exceed the model's predefined maximum length (1024). Depending on the model, you may observe exceptions, performance degradation, or nothing at all."
I can retry and set the maximum length
answer = chain_of_thought("What is the meaning of life?", model="gpt2", temperature=0.5, max_len=50)
but this will generate an (expected) AssertionError:
AssertionError: The decoder returned a sequence that exceeds the provided max_len (max_len=50, sequence length=50). To increase the max_len, please provide a corresponding max_len argument to the decoder function.
So this route ends here for me, as the model will ultimately generate over its own max length and then raise the Index Error. Perhaps there is a way I could solve it myself, but it could also hint at a potential issue with either Transformers or LMQL.
So the other route:

I use a length-constrained prompt with the Generations API:

prompt = """
"Greet the user in four different ways: [GREETINGS]" \
   where len(TOKENS(GREETINGS)) < 10
"""

m: lmql.LLM = lmql.model("gpt2")
m.generate_sync(prompt)

I get the same error, where despite the max token length constraint, the model will still keep generating.
However, this time I can change the call to
m.generate_sync(prompt, max_tokens=10)
which works perfectly fine! However, the 'max_tokens' parameter is not available in the decorated query afaik and of course we want to specify such a constraint in the query itself!
Btw, I also tried with "gpt2-medium" which behaves the same. Did not try other models.
Hope this helps,

Gijs


Add executable option to jenkins_job_builder pip install

Thank you for contributing to openstack/ansible-role-jenkins-job-builder!
openstack/ansible-role-jenkins-job-builder uses Gerrit for code review.
If you have never contributed to OpenStack before make sure you have read the
getting started documentation:
http://docs.openstack.org/infra/manual/developers.html#getting-started
Otherwise please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


Where can I download the pre-trained dataset for Uniref50?

Thank you for your suggestion.
Due to the large amount of data in the ESM-1b embedding of Uniref50, we currently have no plans to release it. However, it may still be released as our subsequent projects progress.
I will keep this issue open, and I will update here if there are any latest developments. Thank you.

Thank you for your response. Additionally, could you provide a download link for the Pfam results from UniRef50? I have attempted to generate it locally, but the process is too slow.

It looks like you've solved the previous problem, which is really nice!
In fact, Pfam has provided Pfam domain results of all proteins in uniprot for everyone to download (https://ftp.ebi.ac.uk/pub/databases/Pfam/current_release/Pfam-A.regions.uniprot.tsv.gz). Maybe it's because Pfam's file download system has poor guidance, and I also looked for it for a long time.
Anyway, I hope this reply is helpful to you
Best.

Hi, I conducted a test using a protein sequence from an influenza virus, with the target database set as Swiss-Prot. I observed substantial discrepancies between the results obtained from the official web server and my local setup. Below are the top ten hits ranked by similarity, first as per the official website and then my local results.

Thanks for your feedback.
I carefully checked the result you got from the server. The reason for the difference in results is that the Swiss-Prot dataset used in our paper (the same as in the GitHub repository) and the Swiss-Prot dataset used on the server are of different sizes. You can refer to Supplementary Table 16 Datasets in our supplementary material. For your convenience, I show this table below.

As you can see, Swiss-Prot in Test contains only 430,140 proteins, while Swiss-Prot (unfiltered) in Target datasets on web server contains 568,744 proteins. This is explained in detail in our paper. In short, in order to avoid potential data leakage during testing, we filtered Swiss-Prot during testing to avoid proteins with high sequence identity with the training data.
Our GitHub repository is mainly to facilitate other researchers to reproduce our work, so it contains the Swiss-Prot used in our tests to ensure consistent experimental results. I checked and found that the protein you searched from the web server is not included in the filtered Swiss-Prot (plmsearch_data/swissprot/protein.fasta), so PLMSearch cannot find it. You can also confirm it yourself.
Finally, since the server handles a large number of requests every day, a large number of embeddings and pfam results will be generated. Due to the limited storage space of the server, these embeddings are often only generated in memory for search, and then cleaned up and not saved. If it is really needed by most users, we may update it in subsequent versions.
Hope this reply is helpful to you.
Best.

Your response has clarified my doubts. Thank you!

By the way, we have uploaded the Dataset of PLMSearch Web Server in Zenodo. Enjoy it.


Support Spring Boot 3.x / Camunda 7.20

With https://github.com/camunda/camunda-bpm-platform/issues/2755 Camunda7 switched to Spring Boot 3.1.
This should be supported by camunda-platform-7-keycloak.

Apache HttpClient 4 is no longer supported in Spring Framework 6.
<dependency>
    <groupId>org.apache.httpcomponents</groupId>
    <artifactId>httpclient</artifactId>
</dependency>

I could help with the migration to HttpComponents HttpClient 5. Let me now.

@cachescrubber:
Thanks a lot for your input. Even if the official 7.20 release is some weeks away this is an important point. You're welcome to help! 👍

Camunda 7.20.0 has landed on maven central. ✨ Let me know if I can help with getting the plugin out (testing, whatever).

@cachescrubber:
Thanks for the hint. I'm about to release version 7.20. So far no help is required. 👍


Potential API Query Parameter Discrepancy: is_overdue in Payables

During the migration of the Monite repository to the OpenAPI Qraft v2, I noticed a recent commit in main where Vitaliy added a filter for the is_overdue field in Payables. However, according to our OpenAPI documentation, the GET /payables endpoint does not support a is_overdue query parameter.
Details:

Commit Reference: The actual commit 🔗 cc: @vkuprin
Endpoint: GET /payables
Query Parameter: is_overdue

Possible Scenarios:

The API has recently been updated to include this query parameter, but schema.json hasn't been updated.
The parameter doesn’t actually exist in the API, indicating a potential error in the implementation.

Action Required:

Please verify whether the is_overdue query parameter is correctly implemented in the API.
If it’s missing, please correct the implementation or update the OpenAPI documentation accordingly.

Additional Note:
There was an issue with the implementation of the getQueryData(…) function in Qraft, which has been fixed in the new version. This issue caused an incorrect type realization, which might be related.

Thank you for bringing this to attention.
Clarification:
The is_overdue filter is not currently supported by the GET /payables endpoint, as the implementation of filters is still in progress by the backend team. At this stage, only the overdue label tag is available, and full filter functionality, including is_overdue, will be added in a future update.
Next Steps:
•	The backend team is aware and actively working on completing the filter implementation.
•	We will update the OpenAPI documentation (schema.json) once these features are fully supported.

I appreciate the diligence in catching this, and we’re committed to aligning the implementation with the documentation. Please feel free to reach out if there are further questions or concerns

Thank you for highlighting this.
Clarification:
Currently, the is_overdue filter is not supported by the GET /payables endpoint, as the implementation of filters is still in progress by the backend team. At this stage, only the overdue label tag is available, and the full filter functionality, including is_overdue, will be added in a future update.
Impact:
•	This issue is not critical and does not affect the app’s functionality. The main objective of adding the overdue label has been achieved, and no breaking changes have been introduced.

Next Steps:
•	The backend team is aware of this and is actively working to complete the filter implementation.
•	The OpenAPI documentation (schema.json) will be updated once these features are fully supported.
Thanks again for catching this. We’ll continue to ensure the implementation aligns with our documentation. Please let me know if there are any other questions or concerns.

@vkuprin, thanks a lot for the clarification, will keep an eye out for updates.

Yo, have you solved the issue with the is_overdue field if filter?

@radist2s  Yes, It's covered with custom filters that you can create and isOverdue was removed
For instance you can pass now from our customisation monite.ts
 MonitePayableTable: {
    defaultProps: {
      summaryCardFilters: {
        Unpaid: {
          status__in: ['draft', 'new', 'approve_in_progress', 'rejected'],
        },
        Scheduled: {
          tag_ids: ['f4031683-7605-48c6-969c-dcfc5397935b'],
          status__in: [
            'draft',
            'new',
            'approve_in_progress',
            'waiting_to_be_paid',
            'partially_paid',
          ],
        },
        Paid: {
          status__in: ['paid'],
        },
      /// you can put here logic for overdue based on what our payables query support as parametor and build even your own overdue logic
      },
    },


installation docs should state that kubectl context needs to be set

in this section. Otherwise, this error occurs.
make install STAGINGVERSION=v0.1.2 PROJECT=my-project
OVERLAY is stable
STAGINGVERSION is v0.1.2
DRIVER_IMAGE is jiaxun/gcs-fuse-csi-driver
SIDECAR_IMAGE is jiaxun/gcs-fuse-csi-driver-sidecar-mounter
WEBHOOK_IMAGE is jiaxun/gcs-fuse-csi-driver-webhook
./deploy/base/webhook/patch-ca-bundle.sh
error: current-context is not set
jq: error (at <stdin>:9): Cannot iterate over null (null)

Fixed in commit https://github.com/GoogleCloudPlatform/gcs-fuse-csi-driver/commit/5b8c5ecb4145d274f2eaddf2e38e1801aa2eb06e, thanks!


Call composite overflow gallery snapshot tests

What

Renamed UI test file HorizontalGallery.test.ts to OverflowGallery.test.ts because the horizontal gallery will not always be present in a wide Desktop screen and mobile landscape.
Why

https://skype.visualstudio.com/SPOOL/_workitems/edit/3157103
How Tested

Ran snapshot tests locally. Check new snapshots generated by CI.
Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

looks good I am curious about why the vertical gallery is not present in this snapshot  will wait for the rest to generate to approve.

Because that is a stable snapshot. I am working on running only for beta.

Is RTL meant to flip the vertical gallery from right to left? And to move tiles in the horizontal gallery from right to left?

Is RTL meant to flip the vertical gallery from right to left? And to move tiles in the horizontal gallery from right to left?

Is RTL meant to flip the vertical gallery from right to left? And to move tiles in the horizontal gallery from right to left?

Yes, that is intended :)


custom cache key

It would be awesome to have the ability to provide a custom cacheKey that would fall back to use the URI if none provided.
Our use-case is that some of the images are already available locally, prior to being uploaded to a remote distribution endpoint.
With a custom cacheKey we could take advantage of the local images by setting something like like cacheKey: ${image.id}-${updatedAt}  with the local image path. Later if it uses the remote URL it would already have the image cached based on the custom cacheKey and not need to re-cache the same image.

It would be awesome to have the ability to provide a custom cacheKey that would fall back to use the URI if none provided.
Our use-case is that some of the images are already available locally, prior to being uploaded to a remote distribution endpoint.
With a custom cacheKey we could take advantage of the local images by setting something like like cacheKey: ${image.id}-${updatedAt} with the local image path. Later if it uses the remote URL it would already have the image cached based on the custom cacheKey and not need to re-cache the same image.

@kevinranks, thanks for your suggestion.
I'm summarising my understanding so that we can brainstorm it internally and come up with a solution.
You expect an additional prop cacheKey to avoid caching redundant images. Currently, path based caching can lead to caching the same image twice specifically in scenarios where the image was loaded from local and later retrieved from network.
Have I understood it correctly?

It would be awesome to have the ability to provide a custom cacheKey that would fall back to use the URI if none provided.
Our use-case is that some of the images are already available locally, prior to being uploaded to a remote distribution endpoint.
With a custom cacheKey we could take advantage of the local images by setting something like like cacheKey: ${image.id}-${updatedAt} with the local image path. Later if it uses the remote URL it would already have the image cached based on the custom cacheKey and not need to re-cache the same image.

@kevinranks, thanks for your suggestion.
I'm summarising my understanding so that we can brainstorm it internally and come up with a solution.
You expect an additional prop cacheKey to avoid caching redundant images. Currently, path based caching can lead to caching the same image twice specifically in scenarios where the image was loaded from local and later retrieved from network.
Have I understood it correctly?

Yes exactly. In an app that users upload many images to a remote server, it makes sense to be able to utilize the local copy of that image prior to uploading it remotely. It's my understanding that right now the internal cache key is based off of the URL. By offering the ability to override that it gives developers a lot more control over the cache. For example, being able to reference a local path for an image and then later use the remote URL, and as long as the cacheKey is the same for both you can show the local (temp) image while the image is being uploaded remotely, all without any additional components or special logic.

@kevinranks, it definitely makes sense. We will brainstorm internally and come up with a solution. Also, if you're interested in contributing to this repo, would suggest you to join our discord channel - https://discord.gg/BNHhcpYD


POwer Toys Run not working

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
PowerToys Run
Steps to reproduce
2024-07-10.txt
✔ Expected Behavior
Power Toys Run working
❌ Actual Behavior
doesnt open
Other Software
No response

/dup https://github.com/microsoft/PowerToys/issues/33504


Add required asterisk to cloudCredential name and message if none supplied

UI for rancher/rancher#19755
If rancher/rancher#19755 is approved and completed please add a required asterisk to the cloudCredential name and supply an error in the UI if no name is provided.
We'd like the cloudCredential name to be required (requires that backend change) because it is not editable. We should be requiring the user to supply a (hopefully useful) name upon cloud credential creation so they avoid getting cloud credentials with randomly generated names that are of little use to them.

Closing as stale. Please re-open if still required.


Problem in Alerta web UI config.js not found HTTP 404

I have installed Alerta server and alerta web UI both on same windows server. Alerta server is running fine. When I am running the web UI the alerts are not displaying and I see the following message on the command console
/vendor/fonts/glyphicons-halflings-regular.eot? HTTP/1.1" 200 -
404, message File not found
/vendor/js/angular-route.min.js.map HTTP/1.1" 404 -
404, message File not found
404, message File not found
/vendor/js/angular.min.js.map HTTP/1.1" 404 -
/vendor/js/angular-resource.min.js.map HTTP/1.1" 404 -
404, message File not found
/vendor/js/angular-sanitize.min.js.map HTTP/1.1" 404 -
404, message File not found
/vendor/js/angular.min.js.map HTTP/1.1" 404 -
404, message File not found
/vendor/js/angular-route.min.js.map HTTP/1.1" 404 -
404, message File not found
/vendor/js/angular-resource.min.js.map HTTP/1.1" 404 -
404, message File not found
/vendor/js/angular-sanitize.min.js.map HTTP/1.1" 404 -
/config.json HTTP/1.1" 200 -
404, message File not found
/config.js HTTP/1.1" 404 -
Below are the config files receives from API server
{"actions":[],"alarm_model":{"name":"Alerta 6.5.0"},"audio":{"new":null},"auth_required":false,"client_id":null,"colors":{"highlight":"skyblue ","severity":{"cleared":"#00CC00","critical":"red","debug":"#9D006D","indeterminate":"lightblue","informational":"#00CC00","major":"orange","minor":"yellow","normal":"#00CC00","ok":"#00CC00","security":"blue","trace":"#7554BF","unknown":"silver","warning":"dodgerblue"},"text":"black"},"columns":["severity","status","lastReceiveTime","duplicateCount","customer","environment","service","resource","event","value","text"],"customer_views":false,"dates":{"longDate":"d/M/yyyy h:mm:ss.sss a","mediumDate":"EEE d MMM HH:mm","shortTime":"HH:mm"},"endpoint":"http://localhost:8080","github_url":"https://github.com","gitlab_url":"https://gitlab.com","keycloak_realm":null,"keycloak_url":null,"pingfederate_url":null,"provider":"basic","refresh_interval":5000,"severity":{"cleared":5,"critical":1,"debug":7,"indeterminate":5,"informational":6,"major":2,"minor":3,"normal":5,"ok":5,"security":0,"trace":8,"unknown":9,"warning":4},"signup_enabled":true,"site_logo_url":"","sort_by":"lastReceiveTime","tracking_id":null}
When I see in the internet explorer developer tool I can see the below error
Syntax Error in File: controllers.js, Line: 91, Column: 53.
Can anyone please help me resolving this issue. I am not able to find any root cause. Thanks

I would guess it is the "arrow function" ...
window.addEventListener('message', event => { ... }

Does it work if you use chrome or firefox?

I am using IE11 . I have not tested on chrome or firefox as those are not installed on windows server. Do you say arrow function doesn't work with IE11?

Hard to believe, I know. But yes, IE11 doesn't support arrow functions ...

Thanks for the help. I changed the arrow operator to normal function and it
started working on IE browser. But the URL is not working outside of the
windows server where api server is running. It is because of CORS issue.
Could you please help me how to create alertad.conf in windows how to
configure the path. Thanks
On Fri 30 Nov, 2018, 7:04 PM Nick Satterly<EMAIL_ADDRESS>wrote:

Hard to believe, I know. But yes, IE11 doesn't support arrow functions ...
[image: screenshot 2018-11-30 at 14 34 10]
https://user-images.githubusercontent.com/615057/49292264-14c87080-f4ad-11e8-9167-14784aee70a9.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alerta/angular-alerta-webui/issues/183#issuecomment-443204946,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AjZhhDtQ1V3aoa3Igxb8RfRfXWDV01Toks5u0TQAgaJpZM4Y7jdh
.

Just put the URL of your Alerta web UI into the CORS_ORIGINS list as explained here ... https://docs.alerta.io/en/latest/configuration.html#cors-config

Thank you very much. I updated the CORS ORIGIN and its working fine now. Closing the issue.


feat: improving test code and refactoring source code

Background
Since we use SGX, it's not easy to unit test locally.
There are limitations to manually testing with the SGX environment every time.
The same goes for IPFS and other related modules
Implement

Most modules with dependencies have been interfaced.
Added some missing tests.
Removed the docker test, I don't think we need that right now. Leave the docker test for the queryClient test
Fixed logs to be taken as debugs rather than errors in non-problematic situations.
Modified service to take sgx and queryClient as arguments when creating it.
Modified the names of the functions that get from the service to start with Get.
Fixed what appeared to be a couple of bugs.
Renamed the function to SecretKey instead of CombinedKey.

Notes
Most of the code changes are due to simple function name changes. A few are due to interface changes.

@youngjoon-lee @H4NLee
I had a lot of code fixes.
I'm sorry, but please review this commit again.(https://github.com/medibloc/panacea-oracle/pull/90/commits/2b86098566bf4dec30c513c39d33b48c415ba8b3)

Remove Get prefix in service
Change function name RetrieveAndStoreOraclePrivKey to DecryptAndStoreOraclePrivKey
Change function name NewOracleSgx to NewOracleSGX
Consolidate duplicate code created using mocks into mocks/suite.god


Programmatically open hotkeys dialog

Hey @chieffancypants,
Thank you for this awesome feature! :smiley:
Is it possible to open the hotkeys dialog programmatically? If so, is it possible to provide a way to accomplish it?
Thanks.

hotkeys.toggleCheatSheet() :-)

Thank you so much @aramando :+1:
I'll give it a try!!


Deno - error: Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'replace')

Spec
Runtime: Deno
Database Provider: Neon
Reproduce:
I run into this error when I try to migrate.
Code
deno.json
{
    "imports": {
        "db/": "./src/db/",
        "kysely"<EMAIL_ADDRESS>        "kysely-postgres-js"<EMAIL_ADDRESS>        "postgres"<EMAIL_ADDRESS>    },
    "tasks": {
        "migrate": "deno run -A ./src/db/migrator.ts"
    }
}

migrator:
import * as path from "node:path";
import { fileURLToPath } from "node:url";
import { promises as fs } from "node:fs";
import { Migrator, FileMigrationProvider } from "kysely";
import { db } from "db/database.ts";

const __filename = fileURLToPath(import.meta.url);
const __dirname = path.dirname(__filename);

async function migrateToLatest() {
    const migrator = new Migrator({
        db,
        provider: new FileMigrationProvider({
            fs,
            path,
            migrationFolder: path.join(__dirname, "./migrations")
        })
    });

    const { error, results } = await migrator.migrateToLatest();

    results?.forEach((it) => {
        if (it.status === "Success") {
            console.log(`migration "${it.migrationName}" was executed successfully`);
        } else if (it.status === "Error") {
            console.error(`failed to execute migration "${it.migrationName}"`);
        }
    });

    if (error) {
        console.error("failed to migrate");
        console.error(error);
        Deno.exit(1);
    }

    await db.destroy();
}

migrateToLatest();

db instance:
import { Database } from "db/types/index.ts";
import postgres from "postgres";
import { Kysely } from "kysely";
import { PostgresJSDialect } from "kysely-postgres-js";
import { load } from<EMAIL_ADDRESS>
const env = await load();

const dialect = new PostgresJSDialect({
    postgres: postgres({
        database: env["PGDATABASE"]!,
        host: env["PGHOST"]!,
        user: env["PGUSER"]!,
        password: env["PGPASSWORD"]!,
        port: 5434,
        max: 10,
    })
});

export const db = new Kysely<Database>({
    dialect
});

Hey 👋
Print env object, it might have an undefined connection string.
Try npm i<EMAIL_ADDRESS>

Seems similar to #10. Closing this.

very cryptic error yeah, it means the connection to the DB isn't working, in my case I had the wrong port number


安装docker版本没有HTTP节点

安装了docker版本，在工作流定义界面没有HTTP节点与Flink节点

for now docker version is not sync with DolphinScheduler release version

dev branch is willing to change this situation, BTW, dev branch just prepare for the next version and a lot of test need to done

please use english to desc your problem，thx


[docs] add a section to introduce OpenDigger so people can know more about our data

Description
Data is the core of Hypercrx. If people know more about OpenDigger, they will know more about our data.

#509

For README, How about naming the section as "Data Source" | "数据来源" and insert it to between "Install" and "Dashboard"?

/self-assign


minor: pico_stdio/stdio.c pulls in mutex header when it does not need to

src/rp2_common/pico_stdio/stdio.c includes pico/mutex.h even when PICO_STDOUT_MUTEX=0.
simple fix incoming...

merged into develop


Zipkin Support

Is there a plan to support Zipkin?

Hi @cchatfield,
Yes, we plan to add it soon, but time is a bit of a problem at the moment. If you can help it would be much appreciated.

I think I can take care of it

@azbshiri That would be great! We just implemented support for jaeger, so we are just missing Zipkin now.
Thanks for the help


Stuck on Update Screen

Hi, first of all i have been checking pingendo and i think is a great program, thanks to the people behind its creation, i downloaded the version v0.33.1 for windows from http://www.pingendo.com/, for use it offline (no internet), here is my problem if my computer is not connected to anything (local networks or virtual machines etc) the program works fine, but as soon im connected to something even if it does not have internet access, the program just shows me that is looking for updates and does nothing else

@ghostzero192 we are aware of the the problems about update and offline story.
For this reason in the upcoming 4.0 version we'll use the standard HTML5 cache system. For the current version no fixes are planned at the moment. Sorry.

@gseregni well at least i can use it while i wait for version 4.0, thanks for the answer.

@ghostzero192 you can test an alpha of Pingendo 4 at http://v4.pingendo.com/playground.html


[docs] Implement a search + individual pages for the icons

Tried importing this from material-ui and its not working.
It says: Module not found: Can't resolve '@material-ui/icons/Delete'

Please check that you node_modules folder includes @material/icons, because it works pretty fine.
https://codesandbox.io/s/0oqo41426n

We would need a reproduction, as demonstrated above it works on codesandbox.

I was looking into the potential for improving the icon documentation page. We have two important leverages that we should use:

Implement a search. We have 1k icons, with 5 variants each. It's not always simple to use material.io to navigate them.
Leverage SEO for the 1k icons. We can make them easier to discover and generate more traffic.

Implement a search. We have 1k icons, with 5 variants each. It's not always simple to use material.io to navigate them.

I rather enjoyed https://material.io/tools/icons/ to be honest. What features do you think are lacking currently?

Leverage SEO for the 1k icons. We can make them easier to discover and generate more traffic.

I don't think that generates useful traffic. Somebody searching for an icon doesn't need a React component library for that.

I rather enjoyed https://material.io/tools/icons/ to be honest. What features do you think are lacking currently?

@eps1lon This way, we can provide the correct import code. We have started in this direction with #12720. I have the following user experience in mind https://fontawesome.com/icons/helicopter?style=solid. We can contextualize the icon in different contexts, we can provide the raw source, the import path, the different variants.
https://stackoverflow.com/questions/50829728/how-to-use-material-ui-icons-in-react: 25 views a day.

I don't think that generates useful traffic. Somebody searching for an icon doesn't need a React component library for that.

The goal is to save people time. We can look at the search volume on Google. It's still early enough so we can correctly position ourselves:

"icons" Volume: 246 000/mo | CPC: $2.13
"material icons" Volume: 165 000/mo | CPC: $0.39
"react icons" Volume: 8 100/mo | CPC: $0.00
"material icons react"Volume: 0/mo | CPC: $0.00

I have removed the important flag as you are raising some concern about the value it can bring.

update: it works i had material-ui in my modules, but i still needed to do: npm install material-ui/icons.
I wonder why it comes as a separate package from material-ui

I wonder why it comes as a separate package from material-ui

@ousmaneMetso Bundle size: https://bundlephobia.com/result?p=<EMAIL_ADDRESS>

What features do you think are lacking currently?

Aliases. It's hard to find certain icons without knowing their exact name. But it would be a huge job to improve that, and well outside the remit of Material-UI.


Fix lint issues and add additional validations to pools

Fixes

server & client lint issues
more validations on /pools & /pools/:id

Looks Good 👍


[Question] Touch ID Required in setItem on Android?

On version 6.0.0-alpha.4 of this package and using Android, when I setItem it requires me to use touchID: true when I want to use touchID to get the item back out - otherwise I get a decryption error.
From the user perspective that means that anytime we setItem, it requires them to use their fingerprint to confirm it. So, for example, if a user logs in with their fingerprint (we unlock the token and send it along), and we get a new token from the server and want to save that new token for the next time they log in, we require the user to user their fingerprint again to confirm it.
That ends up being 2 fingerprints in a row to log in. Is that functionality the intent of the package? I noticed in a previous issue someone mentioned that you don't need to have touchID to setItem. That is technically true, but if you want to use the touchID to get it back out then you're in trouble.

hey @duncan-iaria could you please provide a snippet from your setItem?


Daemonize does not appear to function as intended

Hi There-
When I invoke the following per the readme,
sudo /home/pi/uhppoted/uhppoted-tunnel daemonize max-retries -1 --max-retry-delay 5m --out udp/broadcast:<IP_ADDRESS>:60000 --in tls/client:[redacted] --ca-cert /home/pi/uhppoted/actrl-ca-crt.pem --cert /home/pi/uhppoted/actrl-ctrl-crt.pem --key /home/pi/uhppoted/actrl-ctrl-key.pem
it throws "flag provided but not defined: -daemonize" followed with the usage list.  If I run ./uhppoted-tunnel help, the synopsis shows the daemonize command at the end of the argument list, which if I do it simply runs the command on the session, no installing the service.
In my setup, I have a remote VPS set up as a tls server in/out, and running everything on the command line works as intended and runs great, but it all goes to hell when log out of one of the endpoints (including leaving the pid file around as a nice annoyance), so getting to run as a service as intended for both the pivot node and the remote endpoint would be really nice.
Also, I figured out the hard way one could not specify the ethernet port for the out udp/broadcast interface, with that, the pi could hop it on a wifi, and securely TLS it out to where it needs to go, no cables needed.  Instead, the pi sees eth0 up and it jacks the router up to the point wifi won't work (yes, it's Bullseye...)
Thanks,
-GW

Well, that's embarrassing .. there was a typo in the service name.
I've pushed a set of fixes to the main branch so you'll need to pull that and rebuild it - the build-all target in the Makefile will build a binary for the RaspberryPi if you're not building on the Pi itself.
I don't have a free Raspberry Pi at the moment but have tested daemonize/undaemonize on Debian 11/Bullseye and  they do seem to be working now.
BTW, daemonize only supports the --in, --out and --label options - it doesn't currently support the --max-retries,  --max-retry-delay, --ca-cert, ---cert or --key  options which may be why you are getting "flag provided but not defined" error. The service uses the defaults, which are:

--max-retries: 32
--max-retry-delay: 5m
--udp-timeout: 5s
--ca-cert: ca.cert
--cert: client.cert
--key: client.key or server.key
--client-auth: false

The certificate and key files are expected to be in the runtime directory i.e. the directory from which the service was installed (or set in the service file).
re. ethernet port. The udp/broadcast interface is the pipe to the actual controller so it will use the wired LAN for the out port. The in port should be able to connect via wifi though?

Okay, great!
Now, I can think of the following issues:  The defaults work well for the endpoints, but the 'pivot' node (the VPS running as a TLS server) ideally should not be an 'open relay' and should run as a service in client-auth mode.  Further to that, reuse of client keys should be discouraged, especially given the fact that these are remote and if physically accessed, it would not be difficult to yoink the keys AND the server address off the SD card.  Taken to it's logical conclusion, single shared key at one compromised location used across a VPS hub would provide physical access to every location, so I'd rather wait before going through the effort of doing a build for three platforms, eh?

Not entirely sure I follow your threat model - can you explain how a physically compromised endpoint would provide access to the rest of the system?
BTW:

the client keys need only be signed by the root CA i.e. they don't need to be shared (think you have it like that already?)
the daemonize command doesn't take all the parameters but if you edit the service file you can add them to the ExecStart line e.g.

...
[Service]
Type=simple
ExecStart=/opt/uhppoted/bin/uhppoted-tunnel --lockfile /var/uhppoted/tunnel/uhppoted-tunnel-qwerty.pid --in  tls/server:<IP_ADDRESS>:12345 --out tls/server:<IP_ADDRESS>:54321 --client-auth
...

Oh, cool, that should be documented!
What I meant to say, without --client-auth at the relay node, anyone with access to one endpoint can essentially take control of the endpoints, but now I see you can set that manually so while not straight-forward it is usable.  Thank you very much!

Great - glad that works for you!
re. documented. Editing the service file is a workaround and not ideal - I think the better long term option is going to be a something like a configuration file but it needs some thinking about.
(tracking issue is here

A config file is totally the way to go.
Woke up this morning thinking that long and verbose init or command lines are hard to read and debug.  They're also potential security issues as you potentially leak config details through common tools like ps (I know, security through obscurity yada yada but let's not leave the door wide open...)
Again, thanks for the help, and finding a work-around so quickly.  It's up and running, and I've been watching events trickle in from a remote door controller across town.  Even tried to attack both the endpoint and the VPS a few different and hideous ways and it seems pretty solid.  Next step is to build (or wait for the next stable rel) and daemonize this mess...  I guess I should leave this open for now until release?

re. events. Very cool! Thanks for letting me know!
The next release is a good couple of weeks away (there are a bunch of small fixes and some documentation spread across all the repositories that need to happen first) so if you want to put it to bed you may have to build it yourself.
And, yup, happy to leave this open until it's released.

Closing - fix released in v0.8.2.
Feel free to reopen if necessary.

After a week's run on the command line with no errors at all, decided to give daemonize a go...
Whelp, for some reason it can't find the default ssl files:
Oct 24 12:13:54 [...] systemd[1]: Started UHPPOTE UTO311-L0x access card controllers UDP tunnel service/daemon.
Oct 24 12:13:54 [...] uhppoted-tunnel[167174]: 2022/10/24 12:13:54 uhppoted-tunnel service v0.8.2 - Linux (PID 167174)
Oct 24 12:13:54 [...] uhppoted-tunnel[167174]: ERROR: open ca.cert: no such file or directory
Oct 24 12:13:54 [...] systemd[1]: uhppoted-tunnel-pivot_server.service: Main process exited, code=exited, status=1/FAILURE
Oct 24 12:13:54 [...] systemd[1]: uhppoted-tunnel-pivot_server.service: Failed with result 'exit-code'.
I stuck them in /etc/uhppoted, /etc/uhppoted, /etc/uhppoted/tunnel, still can't find them, where is it looking?
When I edit the unit file as you described previously with explicit file references, the service appears to start just fine

It defaults to the current working directory:
./bin/uhppoted-tunnel help

  Usage: uhppoted-tunnel [options] <command> [parameters]

  Commands:
    daemonize     Daemonizes uhppoted-tunnel as a service/daemon
    undaemonize   Deregisters uhppoted-tunnel as a service/daemon
    version       Displays the current version
    help          Displays this message. For help on a specific command use 'uhppoted-tunnel help <command>'

  Defaults to 'run'.

   'run' options:
    --ca-cert      File path for CA certificate PEM file (defaults to ca.cert)
    --cert         File path for client/server TLS certificate PEM file (defaults to client.cert or server.cert)

The reason being that you can have multiple tunnels running on a machine (and hence multiple tunnel daemons) and they probably each need a separate set of certificates and keys - so by default they look in their 'own' directory. And you can choose to override the defaults either by specifying the location with either a command line argument or by setting the working directory in the service file.


Light Status - Disconnected

Hello
Is it possible to know when light are disconnected ?  ( no power )
it can be very usefull ...
Yeelight for exemple can say Status and Online

Hi,
Thats actually a pretty good idea, I'll probably implement a feature where you can subscribe to status change events.
For now, I suggest calling getDevices() in 5-30 sec intervals and compare the results manually.


Add docs for the new time/date filters

Is your feature request related to a problem? Please describe.
#11418 added a bunch of custom date functions but there is no documentation on how to use them.
Describe the solution you'd like
We should add a user-tutorial page in https://superset.apache.org/ on how to use the new time picker. Explaining:

The definition of Previous/Last periods
Free text shortcuts, e.g. "now: last 7 days"
Custom time functions
Anchor for relative dates

it's currently WIP!

it's currently WIP!

While this isn't well-covered in the Superset docs, it is covered a bit in the Preset docs.
Also, while the time range selector covers most use cases pretty well, it's acknowledged that the UI needs a revamp. @kasiazjc and @lauderbaugh are looking into this and gathering data points, along with others.
Some of the nomenclature/tooltips in this UI have been updated a few times since this issue was created, which hopefully helps at least a little.
Given the above, @ktmud do you think this needs to remain open as an issue? I wonder if it'd be better suited as an Ideas discussion than an Issue (i.e. bug), but I'm curious your thoughts.

Closing this since it's not a bug, it's quite stale, and there are numerous ways to contribute or request changes on docs these days.


Add CTO Resources

https://github.com/mateusz-brainhub/awesome-cto-resources
[Resources to help you grow as a CTO like books, blog posts, lessons learned from tech leaders.]
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Either fullwidth or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.
Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of sub-lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

The link in the PR description is broken.I would suggest using dashes instead of colons and putting the types in parenthesis. I suggest you add a LICENSE file as well.

Hey, sorry for the lack of response, please see #1363.

❯ awesome-lint https://github.com/mateusz-brainhub/awesome-cto-resources
✖ Linting

  README.md:9:3
  ✖    1:1    Missing or invalid Table of Contents                          remark-lint:awesome/toc
  ✖    1:26   Invalid badge source                                          remark-lint:awesome/badge
  ✖    9:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖    9:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   10:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖   10:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   11:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖   11:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   12:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖   12:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   13:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖   13:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   14:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖   14:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   15:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖   15:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   16:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖   16:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   17:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖   17:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   18:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖   18:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   19:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖   19:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   20:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖   20:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   21:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖   21:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   22:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖   22:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   23:3    Incorrect indentation before bullet: remove 2 spaces          remark-lint:list-item-bullet-indent
  ✖   23:5    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   28:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   28:177  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   29:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   29:3    Don’t pad link with inner spaces                              remark-lint:no-inline-padding
  ✖   29:127  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   30:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   30:115  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   31:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   31:192  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   32:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   32:92   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   33:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   33:188  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   34:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   34:69   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   39:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   39:83   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   40:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   40:145  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   41:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   41:106  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   42:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   42:125  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   43:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   43:154  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   44:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   44:232  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   45:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   45:175  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   46:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   46:113  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   47:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   47:137  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   48:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   48:186  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   49:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   49:116  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   50:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   50:131  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   51:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   51:207  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   52:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   52:163  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   53:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   53:151  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   54:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   54:157  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   55:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   55:123  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   60:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   60:103  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   61:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   61:3    Invalid list item link URL                                    remark-lint:awesome/list-item
  ✖   62:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   62:173  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   63:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   63:129  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   64:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   64:148  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   69:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   69:79   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   74:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   74:85   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   75:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   75:70   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   80:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   80:79   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   81:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   81:197  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   82:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   82:118  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   83:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   83:161  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   88:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   88:204  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   89:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   89:131  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   94:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   94:100  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   95:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   95:180  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   96:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   96:139  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   97:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   97:377  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   98:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   98:276  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖   99:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖   99:178  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  100:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  100:106  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  105:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  105:3    Don’t pad link with inner spaces                              remark-lint:no-inline-padding
  ✖  106:99   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  107:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  107:120  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  108:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  108:123  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  109:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  109:54   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  114:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  114:127  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  115:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  115:150  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  120:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  120:138  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  126:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  126:160  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  127:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  127:171  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  132:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  132:137  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  133:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  133:86   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  134:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  134:56   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  139:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  139:105  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  140:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  140:186  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  141:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  141:159  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  146:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  146:192  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  147:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  147:152  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  152:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  152:171  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  153:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  153:104  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  154:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  154:172  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  155:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  155:99   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  156:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  156:124  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  157:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  157:64   List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  158:1    Marker style should be *                                      remark-lint:unordered-list-marker-style
  ✖  158:142  List item link and description must be separated with a dash  remark-lint:awesome/list-item
  ✖  177:1    License must be the last section                              remark-lint:awesome/license

  173 errors

https://github.com/sindresorhus/awesome-lint

Can you fix the merge conflict?

Closing for lack of response.


[NFC] [Doc] Adding documentation webpage using mkdocs

Adding Mkdocs documentation
Use mkdocs material to generate a documentation page from the existing markdown documentation.
This PR aims at providing this with as few changes as possible to the existing doc.
So far the only real change is that i have to move the markdown files in a folder within doc (maybe it is possible to change that though).
TODOs

[x] Add utility script to get mkdocs & run doc page
[x] Add utility script to build
[x] CI for mkdocs
[x] Can the subfolder docs be removed (may be a bit messy to have the sources next to the config though) ?

I managed to do the mkdocs integration without moving any documentation files (the only modifications are to fix some path to some figures).
The only issue is that the CI can not be tested here until it is merged ....
Also to publish the page the URL will be https://adaptivecpp.github.io/AdaptiveCpp/, but there is already old webpage here

If you want to test it in the doc folder there is a serve_doc.sh script, just run it it will create a python venv with the correct packages and start the doc server

Neat. If I run your script, the main page is a generic "Welcome to mkdocs" page. Is is possible to have something AdaptiveCpp-specific there, e.g. the main readme.md?

I made the requested changes, and wrote a small index page for the documentation.

Yes i'm merging the PR and check if the workflows behaves correctly

Also note that the documentation workflow is not triggered automatically yet on push in develop, i will change that once we confirmed that the workflow does work fine