Upgrade to react-styleguidist 5.x

Now that 5.x is out, this package still requires 4.5 of react-styleguidist
"react-styleguidist": ">=4.5 <5",

It would be great to get a new version that is compatible with 5.x

You are totally right, we a 5.x compatible version is under development.

Maybe we should add a note on the main readme until the new version is ready, what do you think @MicheleBertoli?

Absolutely, as soon as we publish a branch for v5 we can link it in the README.

Any news on this topic?

The very basic plugin API in Styleguidist is kinda close so we should start moving Snapguidist to it but I need your help here because I don’t know what Snapguidist needs from Styleguidist.

I'm so sorry but I've been incredibly busy in the last few months (and @cef62 as well).
We'll do our best to get back on track asap, and any help from the community is highly appreciated.
Thanks!

Hello everyone!
I had some free time during the weekend, and I tried to make the minimum amount of changes to the package in order to support v5.
It's not optimal but I guess it's OK for now as far as it works, and it does work with the local example as you can see here:

However, I haven't been able to make it work with the react-styleguidist's basic example because it gives me the following errors:
Failed to compile.

Error in multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css
Module not found: Can't resolve 'style' in '/Users/michele/code/react-styleguidist/examples/basic'

 @ multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css

Error in ./~/react-styleguidist/lib/rsg-components/Playground/Playground.js
Module not found: Can't resolve 'babel' in '/Users/michele/code/react-styleguidist/examples/basic'

 @ multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css

Error in ./~/react-styleguidist/lib/rsg-components/Playground/Playground.js
Module not found: Can't resolve 'babel' in '/Users/michele/code/react-styleguidist/examples/basic'

 @ multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css

If you want to try it: yarn add snapguidist@next.

Hello everyone!
I had some free time during the weekend, and I tried to make the minimum amount of changes to the package in order to support v5.
It's not optimal but I guess it's OK for now as long as it works, and it does work with the local example as you can see here:

However, I haven't been able to make it work with the react-styleguidist's basic example because it gives me the following errors:
Failed to compile.

Error in multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css
Module not found: Can't resolve 'style' in '/Users/michele/code/react-styleguidist/examples/basic'

 @ multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css

Error in ./~/react-styleguidist/lib/rsg-components/Playground/Playground.js
Module not found: Can't resolve 'babel' in '/Users/michele/code/react-styleguidist/examples/basic'

 @ multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css

Error in ./~/react-styleguidist/lib/rsg-components/Playground/Playground.js
Module not found: Can't resolve 'babel' in '/Users/michele/code/react-styleguidist/examples/basic'

 @ multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css

If you want to try it: yarn add snapguidist@next.

Hello everyone!
I had some free time during the weekend, and I tried to make the minimum amount of changes to the package in order to support v5.
It's not optimal but I guess it's OK for now as long as it works, and it does work with the local example as you can see here:

However, I haven't been able to make it work with the react-styleguidist's basic example because it gives me the following errors:
Failed to compile.

Error in multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css
Module not found: Can't resolve 'style' in '/Users/michele/code/react-styleguidist/examples/basic'

 @ multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css

Error in ./~/react-styleguidist/lib/rsg-components/Playground/Playground.js
Module not found: Can't resolve 'babel' in '/Users/michele/code/react-styleguidist/examples/basic'

 @ multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css

Error in ./~/react-styleguidist/lib/rsg-components/Playground/Playground.js
Module not found: Can't resolve 'babel' in '/Users/michele/code/react-styleguidist/examples/basic'

 @ multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css

Repro steps:

git clone https://github.com/styleguidist/react-styleguidist.git
cd react-styleguidist/examples/basic
yarn add snapguidist@next.
apply the following changes to styleguide.config.js

@@ -1,5 +1,6 @@
+const snapguidist = require('snapguidist');
 const loaders = require('loaders');
-module.exports = {
+module.exports = snapguidist({
        components: 'src/components/**/[A-Z]*.js',
        defaultExample: true,
        webpackConfig: {
@@ -7,4 +8,4 @@ module.exports = {
                        loaders: loaders.all,
                },
        },
-};
+});

yarn styleguide

Hello everyone!
I had some free time during the weekend, and I tried to make the minimum amount of changes to the package in order to support v5.
It works with the local example (yarn start) as you can see here:

However, I haven't been able to make it work with the react-styleguidist's basic example because it gives me the following errors:
Failed to compile.

Error in multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css
Module not found: Can't resolve 'style' in '/Users/michele/code/react-styleguidist/examples/basic'

 @ multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css

Error in ./~/react-styleguidist/lib/rsg-components/Playground/Playground.js
Module not found: Can't resolve 'babel' in '/Users/michele/code/react-styleguidist/examples/basic'

 @ multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css

Error in ./~/react-styleguidist/lib/rsg-components/Playground/Playground.js
Module not found: Can't resolve 'babel' in '/Users/michele/code/react-styleguidist/examples/basic'

 @ multi ./~/react-styleguidist/lib/index ./~/react-dev-utils/webpackHotDevClient.js ./~/snapguidist/src/styles.css

Repro steps:

git clone https://github.com/styleguidist/react-styleguidist.git
cd react-styleguidist/examples/basic
yarn add snapguidist@next.
apply the following changes to styleguide.config.js

@@ -1,5 +1,6 @@
+const snapguidist = require('snapguidist');
 const loaders = require('loaders');
-module.exports = {
+module.exports = snapguidist({
        components: 'src/components/**/[A-Z]*.js',
        defaultExample: true,
        webpackConfig: {
@@ -7,4 +8,4 @@ module.exports = {
                        loaders: loaders.all,
                },
        },
-};
+});

yarn styleguide

We don’t have babel-loader anymore, you should transpile files before publishing. In general don’t rely on any webpack loaders ;-) For styles it’s better to use JSS and Styled component the same way it’s done in Styleguidist itself.

This guide may be useful too: https://react-styleguidist.js.org/docs/development.html

@MicheleBertoli @cef62 Ping me when you’re ready to discuss how to make it a plugin ;-)

We don’t have babel-loader anymore

Yeah, but it's a dependency of Snapguidist so it should be there.
It turns out I was missing -loader :)
It works now.
This is more a quick win to support v5, but our goal is definitely to write a plugin.
Thanks @sapegin.

Anyone who wants to try the next version, please run:
yarn add --dev snapguidist@next
Feedback is highly appreciated.


Update prometheus-remote-write version

Describe the bug
Due to a header requirement change, the newer versions of Prometheus are not compatible with this package without setting an override.
This should be fixable by updating the dependency to require at least 0.5.0 of prometheus-remote-write
https://github.com/huksley/prometheus-remote-write/releases/tag/v0.5.0

released at 0.1.1 version


CI failed because of secret not found

Describe the bug
Sometimes CI failed because of the following errors:
=== Try to get secret for 10 min ===
=== Get kubeconfig (try for 1m) ===
Error from server (NotFound): secrets "antrea-e2e-for-pull-request-121-kubeconfig" not found
=== Get kubeconfig (try for 1m) ===
Error from server (NotFound): secrets "antrea-e2e-for-pull-request-121-kubeconfig" not found
=== Get kubeconfig (try for 1m) ===
Error from server (NotFound): secrets "antrea-e2e-for-pull-request-121-kubeconfig" not found
=== Get kubeconfig (try for 1m) ===
Error from server (NotFound): secrets "antrea-e2e-for-pull-request-121-kubeconfig" not found
=== Get kubeconfig (try for 1m) ===
Error from server (NotFound): secrets "antrea-e2e-for-pull-request-121-kubeconfig" not found
=== Get kubeconfig (try for 1m) ===
Error from server (NotFound): secrets "antrea-e2e-for-pull-request-121-kubeconfig" not found
=== Get kubeconfig (try for 1m) ===
Error from server (NotFound): secrets "antrea-e2e-for-pull-request-121-kubeconfig" not found
=== Get kubeconfig (try for 1m) ===
Error from server (NotFound): secrets "antrea-e2e-for-pull-request-121-kubeconfig" not found
=== Get kubeconfig (try for 1m) ===
Error from server (NotFound): secrets "antrea-e2e-for-pull-request-121-kubeconfig" not found
=== Get kubeconfig (try for 1m) ===
Error from server (NotFound): secrets "antrea-e2e-for-pull-request-121-kubeconfig" not found
=== Fail to get secret ===
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting status of b5bdcb6e81c754e76792c3f602ccc1e9df6aa55b to FAILURE with url https://jenkins.antrea-ci.rocks/job/antrea-e2e-for-pull-request/121/ and message: 'Failed. Add comment /test-e2e to re-trigger.

To Reproduce
https://jenkins.antrea-ci.rocks/job/antrea-e2e-for-pull-request/121/console
Expected
It shouldn't happen.

I have observer this several times as well. @edwardbadboy and @lzhecheng believe that this is an issue with cluster deletion with ClusterAPI.

@lzhecheng @tnqn @edwardbadboy I believe this can be closed now?

@lzhecheng @tnqn @edwardbadboy I believe this can be closed now?

Sure.

It seems I was wrong, it is not actually fixed: https://jenkins.antrea-ci.rocks/job/antrea-e2e-for-pull-request/187/console

@edwardbadboy 's PR is to fasten the process of cluster deletion and we used to believe only slow deletion blocks cluster creation as well as getting secret. Now it seems there are other cases. We will keep investigating.

Closing this. The issue has not been observed in a while.


Reader for native SPECS SLE format

Implement reader for different versions of .sle file.

These parsers read the schedule (as xml) as well as the data from the SLE datafiles (which are SQLlite databases)
The output of the SleParsers is a flattened list of dictionaries, which each dict containing the data and metadata of one
spectrum (including the individual channel scans).

Mapping from parser output  to a dictionary that has a similar structure as the output of the XmlSpecs parser, which can then be used to write the nxmpes structure using config files.

Different config files for xml and sle parsing are read automatically based on the file extension.

Config file for SLE is already compatible with NXmpes_xps application definition.

Keyword arguments can be passed from convert to the individual parsers. For SLE files, one can e.g. remove the initial position alignment scans which improves the reading time.

Not working:

Channel readout and calibration (see method _get_calibrated_data in xps_reader_utils). This is related to the initial parsing of the data from the SLE file and can be fixed later. At the moment, the "calibrated" data is currently just the scan of the first channel.
For the data field, some information that is now hardcoded in the config_file is also available in the file, but parsing from the file currently breaks the code (because of XPS_DATA_TOCKEN).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

93 of 608 (15.3%)  changed or added relevant lines in 3 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-2.5%) to 51.255%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pynxtools/dataconverter/readers/xps/reader.py
4
7
57.14%

pynxtools/dataconverter/readers/xps/reader_utils.py
32
129
24.81%

pynxtools/dataconverter/readers/xps/sle_parsers.py
57
472
12.08%

Files with Coverage Reduction
New Missed Lines
%

pynxtools/nyaml2nxdl/nyaml2nxdl_forward_tools.py
1
79.04%

pynxtools/nexus/nexus.py
2
74.38%

Totals

Change from base Build<PHONE_NUMBER>:
-2.5%

Covered Lines:
5125

Relevant Lines:
9999

💛  - Coveralls


Weird SQL generation for QueryDSL Update

Here is the case we are facing at the moment, having a simple JPAUpdateQuery, like this :
JPAUpdateClause update = builder.buildUpdate(interventionOffers); // this is an Entity
        return update.where(interventionOffers.intervention.id.eq(interventionId).and(interventionOffers.offerStatus.eq(OfferStatusEnum.NOTIFIED))) // offerStatus is an enum
                .set(interventionOffers.offerStatus, OfferStatusEnum.CANCELLED)
                .execute();

here is the query that is generated :
Hibernate: update intervention_offers set offer_status=?, offer_status=?, offer_status=?, offer_status=? where intervention_id=? and offer_status=? and intervention_id=? and offer_status=? and intervention_id=? and offer_status=? and intervention_id=? and offer_status=?

QueryDSL version : 3.7.2
Thx,
Eugene.

Could you maybe elaborate on what the exact issue is?

besides this one?
set offer_status=?, offer_status=?, offer_status=?, offer_status=?

Thanks.
Could you also log what Querydsl generates? (The JPQL)

And what is builder.buildUpdate?

builder.buildUpdate it nothing more then a small utility that does this:
return new JPAUpdateClause(entityManager, entityPath);

I would gladly provide the generation of JPQL if I knew how to do it. :)

You could print the .toString() of the JPAUpdateClause.
Or you could debug and break on this line in JPAUpdateClause:
entityManager.createQuery(serializer.toString())
Then you could also compare the generated query and the query that Hibernate made.

Are you sure that you didn't hit those methods while debugging?
Both the set clause and where clause have exactly 4 times the same content.
Could you maybe prepare a reproduction project?

You are right... My bad. You can totally close this one, sorry for the noise

Ah, that's okay.
Anyway, thanks for opening the issue.


DOC: annotate bluesky.plans signatures

Description

annotates plan signatures with type hints
touches up and standardizes docstrings a bit

Motivation and Context
bluesky_queueserver's annotation collection mechanisms require annotations to collect.
The annotations are restricted to Python base types, NoneType, and imports from the typing module.  This means common arguments like ophyd.Device -> Any
Some questions:

It's not obvious from the top-level plan definitions, but are these generators are also sent Msg objects?  I omitted the return type but suppose it would be plan() -> Generator[Msg, Msg, None]?
should spiral_square's x_num and y_num be int rather than float?

How Has This Been Tested?
Test suite passes locally.  Also some fiddling with the queueserver will take place after this

FWIW the numpy drop schedule has:
On Apr 14, 2023 drop support for Python 3.8 (initially released on Oct 14, 2019)

Turns out that the type hint I applied to most detector list arguments (typing.List[Any]) will result in bluesky-queueserver not converting the provided arg into an actual device.
To be compatible with the current state of the queueserver, we either need to delete this hint or use the parameter_annotation_decorator to specify it is a __DEVICE__
At this point, the changes in this PR are maybe less than useful, since they don't actually enable bluesky-queueserver integration.  The best we get are the occasional float annotation.

By default, the queue server attempts to convert all string passed as values of each parameter without type annotation to a device or a plan object with matching name. The idea was that 'lasy' user may use queue server on plans without type annotations. This seems to work in simple cases, but it is not very efficient and may fail if certain cases. In my experience, once I mention that type annotation is optional, users don't want to listen any further. Specifying type as Any adds type annotation to the parameter and disables conversion.
Bringing the annotation decorator into Bluesky package may be challenging. I am thinking if there is an alternative way of telling the queue server that the parameter value is a device. For example, the names such as ophyd.Device or ophyd.OphydObject could be automatically replaced by __DEVICE__. It was mentioned that the devices do not have to be inherited from ophyd.Device. The queue server is using protocols.Readable and protocols.Flyable to decide if an object is a device: https://github.com/bluesky/bluesky-queueserver/blob/a6d9b489b51589f2c2e9509b3125329c80274d18/bluesky_queueserver/manager/profile_ops.py#L701 I am not sure if using typing extensions in annotations makes sense.

I pushed a few commits. The Queue Server (in 'main' branch) should be able to properly handle the updated annotations.

arguably as long as pyproject.toml supports python 3.8 where the type hints are limited, this is not feasible

can this be closed after https://github.com/bluesky/bluesky/pull/1776 , @callumforrester ?

It looks like bluesky has moved far beyond this PR, and the spirit of this effort has already been realized.  👍


Headline: Page jitters

Issue Summary
When viewing a page in Safari on iOS in landscape mode it begins to jump up & down.
Steps to Reproduce
View https://headline.ghost.io/design/ or similar in Safari on iOS
Ghost Version
Latest live version
Node.js Version
Latest live version
How did you install Ghost?
Latest live version on ghost.io
Database type
MySQL 5.7
Browser & OS version
Safari, iOS 16.4.1
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

Hey @escapehatch, thanks for providing a video. I still couldn't reproduce the issue on iOS Firefox. Is this something you encounter randomly, or is this happening all the time when you visit the post?

Hey @minimaluminium it appears to be happening every time, have tried Headline as well the Journal theme, on Safari as well as Firefox, both iOS. It only begins to jitter once you start scrolling down the page, past the initial block.

I can reproduce this in iOS 16.5 (iPhone 12 Pro Max) using Chrome and visiting https://edition.ghost.io/about/
When I turn the phone and enter landscape mode the text begins to jitter. I don't even need to scroll down.
When I visit https://headline.ghost.io/about/ & https://journal.ghost.io/about/ I saw the text jitters as well.


https://github.com/Uniswap/token-lists/releases

https://github.com/Uniswap/token-lists/issues/768


Decompiler control flow doesn't consider memory barriers

Describe the bug
Ghidra's decompiler rearranges loads and stores around memory barriers without respect to their ordering in the input assembly.
To Reproduce
Consider the following C program mbtest.c:
typedef unsigned int uint32_t;

extern uint32_t version;
extern uint32_t value;

uint32_t test() {
     while (1) {
         uint32_t current_version = version;
         uint32_t current_value = value;

         asm volatile("dmb ishld" ::: "memory");

         if (version == current_version) {
             return current_value;
         }
     }
}

When compiled with aarch64-linux-gnu-gcc -Os mbtest.c -c -o mbtest.o, we get the following assembly:
(precompiled zipped object file if needed)
    adrp    x1, 0 <version>
    adrp    x2, 0 <value>
    add     x1, x1, #0x0
    add     x2, x2, #0x0
    ldr     w3, [x1]
    ldr     w0, [x2]
    dmb     ishld
    ldr     w4, [x1]
    cmp     w4, w3
    b.ne    10 <test+0x10>
    ret

Which correctly encodes the loop and memory barrier. However, ghidra's decompile produces this:
undefined4 test(void)
{
  DataMemoryBarrier(2,1);
  return value;
}

Which is very incorrect, as it elides the accesses to the counter and value, and rearranges the access to the global value after the memory barrier.
Expected behavior
If the decompiler did not rearrange these accesses across the barrier, I would expect to see the output look more like this:
undefined4 test(void)
{
  uint uVar1;
  uint uVar2;

  do {
    uVar1 = version;
    uVar2 = value;
    DataMemoryBarrier(2,1);
    if (uVar1 == version) {
      return uVar2;
    }
  } while (1);
}

Environment (please complete the following information):

OS: Fedora 38, Linux 6.2.13
Java Version: 17.0.6
Ghidra Version: 10.2.2
Ghidra Origin: GitHub release

The issue is not the memory barrier.  The decompiler just doesn't know the "version" and the "value" variables are considered volatile.  You can set this on a variable from the Ghidra listing view via the right-click popup menu and selecting Data -> Settings ... and then changing the mutability setting to "volatile"
This should give the desired effect of seeing the loop in decompiler output.
The "asm" directive itself I think is preventing the compiler from optimizing the loop away in the source code example.

This is a partial solution, and I can see the loop represented this way, so I will probably do this. But I don't think it should be necessary.
In C you can, of course, mark a variable as volatile to ensure the compiler does not reorder its load, but that only affects the compiler's output. Take this example modified from the original comment, which adds the volatile keywords to the variables:
typedef unsigned int uint32_t;

volatile extern uint32_t version; // now volatile
volatile extern uint32_t value;   // now volatile

uint32_t test() {
     while (1) {
         uint32_t current_version = version;
         uint32_t current_value = value;

         asm volatile("dmb ishld" ::: "memory");

         if (version == current_version) {
             return current_value;
         }
     }
}

This code produces identical assembly to the version without marking those variables as volatile. From compiler explorer, ARM64 GCC 13.2.0:
test:
        adrp    x1, version
        adrp    x2, value
        add     x1, x1, :lo12:version
        add     x2, x2, :lo12:value
.L2:
        ldr     w3, [x1]
        ldr     w0, [x2]
        dmb ishld
        ldr     w4, [x1]
        cmp     w4, w3
        bne     .L2
        ret

However, a barrier serves an entirely different purpose than volatility. Volatility ensures that the compiler treats all pointer operations as having side effects, and so prevents the compiler from reordering the access. Barriers are used in the ARM64 memory model to disallow reordering by the processor across the barrier.
This is a different concept from volatility, because reordering the loads of version and value is fine, as long as both are loaded before the barrier. There would be no need for them to be declared volatile in a C program.
Without the barrier in the example above, the processor is free to reorder the load of value after both loads of version, and merge the loads of version together, which breaks the intended mechanics of the lock-free data structure.
This seems to be what Ghidra's P-Code optimizer does as well, as it ignores the barrier.


Dev container for node version switching and uniformity

Hi,
In this pull request you can find a .devcontainer folder and minimal configuration to make text-annotator-js run.
Dev containers allow developers to quickly setup a sane dev environment with the expected node versions and associated dependencies a dev container helps. See the documentation here https://containers.dev/
With VS code or other IDEs which support this construct it is practical to do development in such container. It makes it also easy to switch node versions to test older node versions.  A uniform dev environment should also make bugs more easy to replicate or report.
Added to the pull request are two scripts, one is executed once when the container is build, the other each time the container is started.
It does add a dependency on docker and an additional folder. Thanks for considering this.
Joren

Never heard of it :-) But sounds good in principle. Just one comment: there's no need to cd into each individual package folder. (In fact it's bad practice, I believe.) You should run npm install only once, in the root folder. npm workspaces will handle the rest.

Now the npm install thing is only called once in the root folder.


Add streaming ingestion support

There were a few major reasons this wasn't the first option developed.

Streaming wasn't (still isn't) available on our Java client (https://github.com/Azure/azure-kusto-java/issues/20)
Streaming without a fallback mechanizem can create a potentially high load on our ingestion service, which in turn will cause 429 or 5xx and will result in data loss
Streaming Async might cause data loss due to offset management issues
Streaming Sync can cause a bottle neck on Kafka itself, as it is much faster to write locally than over the net

Going forward, this is something we would definitely want, but need to have good reasoning with regards to the above issues.

Added to SDK backlog

Where are we with streaming ingestion? Just compared ingesting from Kafka using the Kusto Connector and ingesting via EventHubs. No matter what I do I cannot get the latency using the Kafka Connector down to below (at the best case) 3 - 5 seconds, that is tweaking the ingestionbatching policy. When I ingest from EventHubs, the latency is ~50 - 100 ms!

Hi Nils,
This change is not yet scheduled for implementation.
In general Kusto is not built for millisecond velocities, and configuring it that way means making a big compromise on ingestion capacity (MBs/Sec).
I can temporarily suggest the following  configurations,

Set the batching policy blob count to 1, preferably on the lowest possible level (table or DB)
Tune Kafka's Kusto Sink Connector flush.interval.ms parameter down to achieve a desirable result

Note!!!
This configuration can not ingest large amounts of data, and is highly inefficient on the engine.

Thanks @yogilad!
I managed to get the latency down to the 3 - k seconds range by chganging configuration as per your suggestion above - Thanks!
As for Kusto not being built for milliseconds latencies - I would be happy if I could get the latency down to the one second range, especially seeing that with EventHubs I get sub 100 - 300 ms latency. The fact that I am - ""out of the box" - getting that low latency from EventHubs makes me a bit concerned when you say that Kusto is not built for milliseconds velocities.
The use case right now for me is  am comparing ADX with Apache Pinot, and looking at what to use for real-time user-facing analytics.
Anyway, thank you again for your input - most valuable!

Let me clarify myself.
Kusto has multiple data intake channels.
The commonly used ones are built to ingest gigabyte+ of data with +-minutes latency.
The streaming ones handle less data, but do so in ~seconds latency.
You can tune to former to come close to the latter, but at the expanse of data volume.
This is the concern I raised above.
Can you share the amount of data you wish to ingest (MB/s, rate of requests, number of concurrent clients)?
Also, what's your timeline for the evaluation?

Hi Youchai!
Thanks for the clarifications!
If it is OK with you, I will send you an email, where I describe a bit more what we are thinking of doing.
Thanks!
Niels

Adding @ohadbitt
Update:

We'll try to push this change up the backlog, and hopefully get it working sometime next week.
You can then check if you are able to achieve a satisfactory result with it.

Discussing this with our PM, if you do need 'under 1 second' times Azure Stream Analytics (ASA) is more suitable. If you need 'under 1 second' times in combination with Kusto's analytics capabilities you can opt for a joint solution where ASA also forwards the data to Kusto for deeper analysis (in Kusto latency times).
This feature is about to be released (if it has not already)

Hi Yochai!
Thanks for the above. I just sent you an email as well. I'll definitely check the connector out whenever you have done the changes. Oh, speaking of which; it seems there is an issue with the latest connector (2.1), where it loads into Kafka Connect but is not added as a connector. I have a separate issue logged for that.
Thanks again!
Niels


Possible to run this standalone to HA

Hi,
Thanks for the work on this, I am looking forward to giving it a go. I have my HA installed manually, so can't install it using the addon. I have been trying to get it to work via docker, however I seem to have come accross quite a few issues. Is this something that is possible? Or am I trying in vain?
Thanks again

Hi!
The addon is actually capable of being run via docker in stand-alone mode. In fact, I run it that way when I debug it.
Here's you can find the launch command for running the docker container in stand-alone mode:
https://github.com/albertogeniola/ha-meross-local-broker/tree/main/.local_debug
Look at the run_addon_locally.sh

Thanks for the quick response and pointer!
I have managed to get the container running now, and can access the configuration page, however I am getting container errors
Traceback (most recent call last):

  File "/opt/custom_broker/mdns_register.py", line 94, in <module>

    exit(main())

  File "/opt/custom_broker/mdns_register.py", line 82, in main

    path = register_service(service_name=args.service_name, service_name_template=args.service_name_template, service_type=args.service_type, service_port=args.service_port, service_priority=args.priority, service_weight=args.weight, data=args.set, update_if_present=args.update_if_present)

  File "/opt/custom_broker/mdns_register.py", line 55, in register_service

    raise e

  File "/opt/custom_broker/mdns_register.py", line 50, in register_service

    return _register_service(service_name=service_name, service_name_template=service_name_template, service_type=service_type, service_port=service_port, service_priority=service_priority, service_weight=service_weight, data=data)

  File "/opt/custom_broker/mdns_register.py", line 32, in _register_service

    bus = SystemBus()

  File "/usr/local/lib/python3.7/dist-packages/dbus/_dbus.py", line 196, in __new__

    private=private)

  File "/usr/local/lib/python3.7/dist-packages/dbus/_dbus.py", line 102, in __new__

    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)

  File "/usr/local/lib/python3.7/dist-packages/dbus/bus.py", line 124, in __new__

    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)

dbus.exceptions.DBusException: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory```

I'm guessing that I maybe need to pass dbus from the host to the container?

Never mind, I have just disabled broadcast and done a reinit and I am in!
Thanks alot!

Exactly: either you install dbus on the host and pass it to the container or disable broadcasting. Congrats for having figured it out!


Windows support added while maintaining MacOS/Linux compatibility

Changes to package.json and inclusion of run-script-os in dev dependencies so that users on MacOS/Linux and users on Windows run different scripts. Added go-compile-windows.sh which builds the binary exe for windows. Modified the README with Windows specific setup steps. I do not have a MacOS or full Linux environment, so you should try my fork on your environment first for compatibility, but hopefully this should do it.

I want to merge this but it's a big PR that will require a lot of testing on multiple platforms. If someone can help test this out and write up a testing document with all of the results, I would be happy to merge! Thanks @dan-dean for the awesome work on Windows compatibility.


Can't edit or preview projects that use the now deprecated 'Media Interactions' template

You can no longer edit or preview old media interactions projects.
It gives an error of 'node.editor_size is null' or 'node.preview_size is null' from template_management.js. Where should template_management.js be getting this from?
It doesn't seem to be a problem with all deprecated project types, just media interactions ones.

I believe this information comes from the info file.

You can work around this by opening the edit url directly in another browser window whilst you have the workspace open. I'm going to close this as it doesn't appear to be an issue with users out there.


Show Android Soft Buttons

The current version of this app is in full screen mode which forces an extra swipe to activate the phone's dock (home/back buttons). It would be great if this was visible so you can open the app, do what needs to be done, then quickly exit with the phone's home button.

The current version of this app is in full screen mode which forces an extra swipe to activate the phone's dock (home/back buttons). It would be great if this was visible so you can open the app, do what needs to be done, then quickly exit with the phone's home button.

The app is kinda made as the name suggest to be just always open on a tablet, it's normal to have fullscreen mode


Implicit index.jsx support

Hi all, fantastic bundler! Would it be possible to add support for implicit loading of index.jsx within a directory using ES6 import syntax?
With the directory structure:
src
  - containers
    - App
      - index.jsx
  - index.jsx

And src/index.jsx of:
import React from 'react';
import ReactDOM from 'react-dom';

import App from './containers/App';

ReactDOM.render(
  <App/>,
  document.getElementById('root')
);

I get the console error: ./containers/App was not found upon request.
However if I rename src/containers/App/index.jsx to index.js, the error disappears and the app boots up fine.
My fusebox config is identical to the react example in the docs, except outFile is set to './build/bundle.js'.
If I am looking in the right place I believe a case would need added to https://github.com/fuse-box/fuse-box/blob/master/src/loader/LoaderAPI.ts around line 287.

Also came across this issue. It's a common pattern to use index files for React Components. F.e. https://github.com/Automattic/wp-calypso/tree/master/client/components/card and then use the component by only referencing the directory import Card from './components/card' instead of  './components/card/index'.

Thanks guys!
It's been added to the next milestone!

Coming soon!; -)
https://github.com/fuse-box/fuse-box/blob/master/test/path_resolver.js#L62


vue1里面的this.$compile 在vue2里面怎么用啊

vue1里面的this.$compile 在vue2里面怎么用啊

Please make sure to read the Issue Reporting Guidelines before opening new issues.
The issue list only accepts bug reports and feature requests. Questions should be posted to the Gitter chat room,  forum or StackOverflow.
BTW, You can use the Vue.compile in Vue 2.x later.
Thanks.


Add support for using swagger 'enum' field

Descriptive summary
Currently, in our PathParameterizer module we use the dictionary builder for looking up query parameters. Swagger 2.0 supports enums where you can provide those values in the swagger definition itself.

Add support for detecting presence of enum field and reading values from there instead of dictionary
If enum field has more than one value, then send requests for each of them

Rationale
For scenarios like gatekeeper API's /aleph and /illiad endpoints, each different query parameter implies a different endpoint behavior we test. This change will help us do that programmatically instead of relying on changing values in corpfs during testing

I have been reading over the enum definition on the Swagger website, will we be using reusable enums for the basic  enum [asc, desc] format?

We won't be using reusable enums since we're sticking with swagger 2.0. Built in support for reusable enums comes only with OpenAPI 3.0


Fix use of HTML tag or CSS class specification as icon of TypedInput

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes

TypedInput widget seems to support specification of TypeDefinition icon by HTML tag or CSS class.  But it fails to show when selecting from a type menu.
This PR fixes this problem.
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage increased (+0.05%) to 76.084% when pulling 15da19dceaa26f02b0e346c37dc265ceb19dec3e on node-red-hitachi:fix-icon-spec-for-typedInput into dfa077fd5f99cc64829b0e4494af45f463d7f622 on node-red:master.


[lc_ctrl/rtl] replace u_state_regs and u_cnt_regs with prim_sparse_fsm_flop

On investigation of the implementation of the security countermeasure verification framework it seems that the LC State and LC Count registers can be implemented using prim_sparse_fsm_flop which should enable the pre-defined security countermeasure tests for those registers.
Currently they are implemented using prim_flop:
 logic [LcStateWidth-1:0] lc_state_raw_q;
  assign lc_state_q = lc_state_e'(lc_state_raw_q);
  prim_flop #(
    .Width(LcStateWidth),
    .ResetValue(LcStateWidth'(LcStScrap))
  ) u_state_regs (
    .clk_i,
    .rst_ni,
    .d_i ( lc_state_d     ),
    .q_o ( lc_state_raw_q )
  );

  logic [LcCountWidth-1:0] lc_cnt_raw_q;
  assign lc_cnt_q = lc_cnt_e'(lc_cnt_raw_q);
  prim_flop #(
    .Width(LcCountWidth),
    .ResetValue(LcCountWidth'(LcCnt24))
  ) u_cnt_regs (
    .clk_i,
    .rst_ni,
    .d_i ( lc_cnt_d     ),
    .q_o ( lc_cnt_raw_q )
  );

This is different from LC FSM registers which use prim_sparse_fsm_flop, the interface appears to be the same except for the type parameter (StateEnumT).
  logic [FsmStateWidth-1:0] fsm_state_raw_q;
  assign fsm_state_q = fsm_state_e'(fsm_state_raw_q);
  prim_sparse_fsm_flop #(
    .StateEnumT(fsm_state_e),
    .Width(FsmStateWidth),
    .ResetValue(FsmStateWidth'(ResetSt))
  ) u_fsm_state_regs (
    .clk_i,
    .rst_ni,
    .state_i ( fsm_state_d     ),
    .state_o ( fsm_state_raw_q )
  );

@msfschaffner should we use prim_sparse_fsm_flop for lc_state as well?

This sounds like a good idea - I'll look into it shortly.


Add recursion & undefined case

Add yii-framework recursion case.  it's like this,  ["owner"]=> RECURSION
and change "throw error" to generate a default undefined case to make users always see var_masterpiece popup if there are not defined case.

Thanks so much for the update, and sorry for the super long delay. IIRC chrome web store was not letting me release new updates last time I checked, but Ill try again soon


Adding "Pause" functionality for Directory Statistics

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Problem
My organization has a huge folder with millions of objects, calculating the total size taking hours to complete, I will need to switch networks during the statistics calculation.
Desired Solution
Adding a "Pause" button next to the "Cancel" Button
Alternatives and Workarounds
No response
Additional Context
No response

@wjhhuizi The statistics feature for Storage Explorer is not meant to get extremely accurate results. This is impossible primarily because cloud storage is often in constant flux. Multiple users are uploading, modifying, or deleting objects all the time. Running a statistics operation from Storage Explorer on containers with millions of blobs in them takes a lot of time. By the time it finishes, the collected statistics are already out of date.
Adding a pause feature can only exacerbate this situation. It essentially makes the statistics operation take longer, and even more modifications to the container can occur in that time.
We will hold onto this feature request for future considerations. In the meantime, if you need reasonably fast and accurate statistics, have you considered Azure Storage blob inventory?


[TOPI] add take

add take

Take operator added to tvm.topi to support Tensorflow Gather operator in future.

@merrymercy can you help review this?

Review comments fixed.

In general, i feel there should exist better algorithms than current take that break things down and redo it. We should be able to do everything in a single compute, cc @yzhliu @Huyuwei for further comment

We can implement the logic in python like this:
def take(x, indices, axis=-1):
    in_len = len(x.shape)
    indices_len = len(indices.shape)
    out_len = in_len + indices_len - 1
    if axis < 0:
        axis = in_len + axis
    in_shape = get_const_tuple(x.shape)
    indices_shape = get_const_tuple(indices.shape)
    out_shape = in_shape[0:axis] + indices_shape + in_shape[axis+1:]
    def _compute(*out_index):
        index_along_axis = indices(*out_index[axis:(axis+indices_len)])
        in_index = out_index[0:axis] + (index_along_axis,) + out_index[axis+indices_len:]
        return x(*in_index)
    return tvm.compute(out_shape, _compute)

Reworked as per Huyuwei comment and also fixed tqchen review comments.

@PariksheetPinjari909 Now topi.take doesn't support scalar indices, so the behavior is slightly different from numpy. Should comment on this?

@Huyuwei  topi.take receive second argument as tensor instead scalar for frontend limitation registration reason.

Reworked as per comment.

wait approval from @Huyuwei


Clean new config

This is a big refactor of the way models are configured and run.
This PR does not remove any of the original code, but creates a new_config directory with the new architecture.
It also drastically simplifies the user interface, see ravenpy/ravenpy.py for the two main functions users will use:

run to run the model on an existing configuration
parse to read the outputs and create Python objects

See tests.conftest.gr4jcn_config for an example of the configuration with the refactor:
m = GR4JCN(
        params=[0.529, -3.396, 407.29, 1.072, 16.9, 0.947],
        Gauge=rc.Gauge.from_nc(
            f,
            data_type=["PRECIP", "TEMP_MIN", "TEMP_MAX"],
            alt_names=alt_names,
            extra={1: {"elevation": salmon_hru["land"]["elevation"]}},
        ),
        ObservationData=rc.ObservationData.from_nc(f, alt_names="qobs"),
        HRUs=[salmon_hru["land"]],
        StartDate=dt.datetime(2000, 1, 1),
        EndDate=dt.datetime(2002, 1, 1),
        RunName="test",
        CustomOutput=rc.CustomOutput("YEARLY", "AVERAGE", "PRECIP", "ENTIRE_WATERSHED"),
        GlobalParameter={"AVG_ANNUAL_RUNOFF": 208.480},
    )

Writing the config files to disk is then done with m.write(path).
The configuration supports symbolic expressions, e.g.
uniform_initial_conditions: Dict[str, float] = Field(
        {"SOIL[0]": P.GR4J_X1 * 1000 / 2, "SOIL[1]": 15},
        alias="UniformInitialConditions",
    )

I think the objective now would be to pinpoint non-intuitive stuff in the new configuration and fix those. Once we're happy, let's merge this PR and then create others adding the other emulators and functionalities we want to port.
Ping @Mayetea

The failing tests are due to a mistake on my end. I did an automated rename of something and I thought it applied only to a file, when it applied to the whole repo... will fix this.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

976 of 1049 (93.04%)  changed or added relevant lines in 10 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+1.6%) to 85.901%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ravenpy/new_config/rvs.py
121
122
99.18%

ravenpy/new_config/base.py
112
115
97.39%

ravenpy/new_config/utils.py
52
58
89.66%

ravenpy/ravenpy.py
64
84
76.19%

ravenpy/new_config/commands.py
365
408
89.46%

Files with Coverage Reduction
New Missed Lines
%

ravenpy/models/base.py
2
93.3%

Totals

Change from base Build<PHONE_NUMBER>:
1.6%

Covered Lines:
4722

Relevant Lines:
5497

💛  - Coveralls

So a few questions to guide the review:

Should ravenpy.run return something. At the moment, it will raise errors if something's wrong, otherwise if the simulation is complete, it returns None.
In ravenpy.init, I'm exposing run and parse, but should other parsers be made available at the top level (e.g. parse_diagnostics)?
Should we rename run and parse to something else ? run could also be raven.

Should ravenpy.run return something. At the moment, it will raise errors if something's wrong, otherwise if the simulation is complete, it returns None.

If we do not want to raise errors, could we return an object that describes whether the simulation failed (and how) ? This would be good information to pass along via WPS process / logging.

Should we rename run and parse to something else ? run could also be raven.

I like run; less confusing when we already have ravenpy and ravenwps.

Good questions.

Maybe it should return the standard "0"? I'm not a good enough developer to provide more in-depth comments on this.
Ideally we should have a method like "build" where we build_model the model before running it, maybe set_parameters, etc.? That would allow accessing everything before we actually launch a run. Ideal for calibration and assimilation, for example.
I suggest keeping run and parse. Calling "ravenpy.raven" seems odd to me.
I agree to uniformize to run_name.

Trying to setup my env to help evaluate, debug and contribute to this!

I agree with Trevor and Richard comment on the way we should structure the code. Also, shouldn't we removed the part of Ostrich in base.py? I never installed the binary for it since we were suppose to rip it. So right now, if I'm not commenting the Ostrich code, 60 tests fails and if I comment I still get errors for Ostrich unit tests (16 failed tests) and 2 others which could be related but doesnt give Ostrich errors.
So what do we do with this? Do ,we include the removal in this PR or in another PR?

Also, shouldn't we remove the part of Ostrich in base.py?
...
So what do we do with this? Do we include the removal in this PR or in another PR?

If we can get those changes underway, that removes one of the blockers for #264 (the other is being worked on currently).

This PR is only about the new config, so yes, Ostrich is still there. I'll open a new PR to plug SPOTPY to the new config once this one is merged, and then we'll be able to remove Ostrich.
The "build" step is shown in the PR description, configure the model m=GR4JCN(...), then write it to disk m.write(path).
We can return True if the simulation has completed, or the path of the output directory.

I think what Richard meant is that we should have a dedicated class to do the raven job something like this :
model = GR4JCN(...)
raven_runner = raven.build(model, path)
raven_runner.run()
raven_runner.write() #Writes the results in a file.
It might be impossible to refactor this way now, but I think its the way he was talking about.

That's very easy, I can whip something up for discussions.

See the latest commit for a new Emulator class with methods:

build
run
parse

I've tested the new push from yesterday and the only errors I have (non-related to Ostrich) is in test_read_from_netcdf and test_open_dataset_false_cache.
In test_read_from_netcdf, we assert to have a message different than None, but we receive None.
In test_open_dataset_false_cache, I get an error for Permission denied on accessing a file.

Weird, no clear idea where this is coming from. Bugs notwithstanding, what I'm interested in is feedback on the API: the naming of functions and arguments, the workflow, etc.

I'm currently trying to use the new_config in the spotpy test. I have 2 comments so far.
First, I think the import of the model should be as claer as before : from ravenpy.models import GR4JCN and not from ravenpy.new_config.emulators.gr4jcn import GR4JCN. So we could import all models from .emulators or choose to import a specific by naming it (as for GR4JCN)
Second, I dont understand why in the Emulator.build() we have overwrite as True for a default value, but in Config.build() the overwrite is set as False by default.
I'll let you know if I have more comment as soon as I make it work in with spotpy

test_spotpy_calibration should now run the calibration for gr4j. To run the other models that have a new config, we only need to add the low and high bounds.

Ah yes, I understand the issue. I'll try spotpy with your new push. Ill let you know, how it goes!

Check tests/new_config/emulators
There is a pytest fixture called emulator that will instantiate all the emulators in names.
Then this is used in tests/new_config/test_emulators to test all emulators with one single test, instead of writing one test per emulator.

Maybe I misunderstood the question, but calibration.py has a SpotSetup class using the new config.
It's exercised in test_spotpy_calibration, using the same emulator fixture.

I was talking about the netCDF that we shoot for the training, but I think I found how you were passing it with the fixtures. Ill try to make it work without fixtures, but it seems good. It was a bad interpretation on my end!

I've managed to make, spotpy work without fixture, but it doesnt do a rerun for raven for each evaluation. It keeps shooting the same nash -0.117301, so it doesnt try to balance the params. Im looking for the issue right now.

So I found out in debugging, that params are changing, but the Nash is always the same, which is (-0.117301) as stated in the other comment. I'll let you know if I found other info that could help you find the source of the issue!

I think I know what's wrong. We need to instantiate the model at each iteration, not update the parameters.

Shouldnt this be the job of the build function? We do :
self.config.params = list(x)
self.build(self.path / f"c{self._iteration:03}")
self.run()
While we were doing this before :
self.model.config.update("params", np.array(x))
self.model._execute(self.ts)
The only thing I see different is in the execute function where we do self.setup() before calling run().
I'll try adding it in the simulation too, and see what we get after!

But the config object underneath is completely different.

I've been testing and trying to run this new_config, and I have hit a few snags. I've been able to overcome some of them but others are blocking.
1- Gauge.from_nc : It seems it can only handle a single file with all variables merged. However, users that would use the ERA5 extraction tool (or have different files for different variables) would have those separated. Is it possible to send a list of files, as we could before with the ts forcing? Or maybe I just failed and it's already possible? I got errors saying it expects a str or path object, but not a set or tuple, etc.
2- Gauge.from_nc (again): When I take the spatial mean of the ERA5 weather data, I mean over latitude and longitude, meaning that those dimensions disappear. The code is failing because it expects getting a gauge lat/lon. Is this necessary? I think it was not required before? Can we have a system where if there is only 1 station, it just takes a random value (since it will not impact the results)? I can force it in the extras, but it seems to be a redundant step if it's not useful in the actual code.
3- GR4JCN has a parameter defined as AVG_ANNUAL_RUNOFF, but I don't think this is what GR4JCN actually needs. The parameter is G50 (unless it is something else entirely, in which case I am at a loss as to what it is) and represents the median annual snowpack depth.
4- We need to expose more clearly how to run a model from rv / nc files from a folder that a user would upload. Try as I might, I was unsuccessful. I was only able to run models that I had previously built.
5- One notebook (02_Extract_geographical_watershed_properties.ipynb) fails for obscure reasons, to investigate.
I'll add more as I progress!

You can call Gauge.from_nc multiple times and concatenate the results:
gauges = Gauge.from_nc(fn1, ...) + Gauge.from_nc(fn2, ...)

Lon and lat are necessary in Gauge commands (docs page 195). It was not required because we took the lats and lons from the HRU, but that was a hack. You can pass extra Gauge arguments using the extra keyword: Gauge.from_nc(fn, ..., extra={"latitude": 56})

? You mean there's a bug in the template?

ravenpy.run

Thanks for the above response!

Great, that works perfectly! I'll present both options (aggregated or separated netcdf files) in the notebooks.

OK I'll document that as well in the notebooks. Makes sense.

I am not sure where that value/parameter comes into play in the code. To my knowledge, the only other value that is required for CEMANEIGE is the median snowpack, which might or might not be computed internally from observations. Although, for forecasting, it would be necessary to provide the value anyways... so I am guessing this is the parameter. Where/how it interacts inside Raven itself though.

thanks, it works!

Hi @Zeitsperre, we have an issue in the second notebook (02_Extract_geographical_watershed_properties).
This block of code doesnt work :

With the following error :

Thanks in advance!

Extra info for you @Zeitsperre, the NB02 works on our pavics.ouranos server but not locally. So it might be as simple, as getting the good package for it. I'll let you check for it and dont hesitated to poke me, if you want to test things on my local env.

@Mayetea That's too bad. Do you think you could provide some printouts of the relative environments? i.e.: !conda list
Am I correct in assuming that you are spinning up your own version of RavenWPS? Or are you launching requests against an existing RavenWPS service at Ouranos/CRIM?

@Zeitsperre we are running notebooks locally on a local jupyterlab instance. We migrated the notebooks to the ravenpy repo so no link whatsoever to ravenwps (except the birdy call to ravenwps). packages are those in the ravenpy branch clean_new_config; both in the basic requirements and in requirements_docs.txt. Hope this helps! thanks!

Okay, thanks. That helps my understanding. I'll have time this afternoon to look into this. I'm wondering if the issue is that the returned grid0 object is based on pymetalink and its structure can therefore be dependent on resources, maybe? There have been a lot of changes to the base libraries in recent months, so something maybe needs an update.
News from me soon.

Even though, I have Raven.exe localy the code for RavenWPS in the NB is the following :

So I think Im using it from the server.
For my environment here it is:

Okay great! Final question: you're still working exclusively on Windows?

I am working in Linux/Ubuntu/Mint, and @Mayetea is working in Windows.

Gotcha. Thanks Richard. Good to know!

One error being raised is due to an OWSlib regression: https://github.com/geopython/OWSLib/issues/871

@richardarsenault If you want to maintain a specific set of sections in the imports of a notebook: https://pycqa.github.io/isort/docs/configuration/action_comments.html#isort-split


Manually update the warden session last_activity_at

Closes #221

Coverage increased (+0.01%) to 84.235% when pulling 73ad8d042ea484fa79c316667e4ec3437aa74acb on bug/221 into 707f1fefac70e5df02ec716782e8739dcc2ddfed on master.


feat(serde_with): add with_suffix!

This should properly close #381.
Apart from the used example it is pretty much identical to the existing with_prefix! code, except for the few places that actually do the suffixing / trimming.

Thank you for doing the work of adding with_suffix!. Since it is mostly a copy, I don't see a problem here. I like that you added a proper new example to the documentation :)

any ETA for a new release that would contain this? @jonasbb


Fix the DatabaseObjectWriter hierarchy

At the moment, we have some members of the DatabaseObjectWriter hierarchy that restrict the features of the super classes, as in
https://github.com/exasol/test-db-builder-java/blob/main/src/main/java/com/exasol/dbbuilder/dialects/postgres/PostgreSqlImmediateDatabaseObjectWriter.java#L33
A class should extend another one if:

the subclass is a superclass
the subclass can do everything the superclass can

Extending a class restricting the super class is usually not a good idea, as it breaks the Liskov substitution principle and will eventually lead to a hierarchy hard to maintain, extend and change.
We should fix this.

Shelved.


Data race with mi_page_s's flags field

In _mi_free_generic when freeing a non-local allocation, the flags field of the page is accessed without synchronization. This leads to a data race when the thread owning the page also modifies the flags field.

Ah, that is right!  I remember considering the race benign "enough" when writing this code but now that I look at it again I think it should be fixed -- let me look into it.
Why it is relatively benign is that the "aligned" field of the flags is monotonically increasing -- and if it increases it doesn't matter for the current pointer that is freed. As long as a race access doesn't return some completely arbitrary value it is fine (and thus ok on most/all hardware). However, it is of course not within C semantics or guarantees and we should fix this. Thanks!

Thanks @zoxc for the feedback; I refactored the free-ing code in a separate file and removed the "benign" race; and also improved the ptr_unalign to be faster as it is now always used for a non-local free (by adding a page_start and block_size_shift field).


Update ActiveEffect to v12

Updates ActiveEffect to v12.
Notes:
Changes
get target(): Actor | null;

to
get target(): Document | null;

There was a TODO there to make the return type more generic.

Why not Item | Actor | TokenDocument? Are there systems that target, say, ActiveEffect or FogExploration?


[BUG] Anonymous access issue

Anonymous access does not work as described in the documentation:
https://docs.gitops.weave.works/docs/guides/anonymous-access/
additionalArgs:
  - --insecure-no-authentication-user=gitops-test-user

In this case, only a welcome page is available:

@bigkevmcd thanks for looking into.
In case of insecure-no-authentication-user with oauth2-proxy  to secure access in common way - we will have result above.
In case of use weave-gitops internal oidc, or insecure-no-authentication-user without oauth2-proxy it works well.
So looks authentification conflicts with internal weave-gitops oidc.

@zs-dima I'd be happy to look at a PR that introduced support for oauth2-proxy.
I'm not entirely sure what it would take tho', as we basically take the OIDC ID Token and use that to talk to the kube-apiserver (which is very similar to what Kubernetes does natively).

@bigkevmcd thanks a lot for looking into
You can look into sample comfiguration: https://github.com/zs-dima/monitoring-stack-k3s
If you will change weave auth from the auth-methods=oidc to the insecure-no-authentication-user=gitops-test-user
Then add middlewares to the ingress traefik.ingress.kubernetes.io/router.middlewares: auth-oauth@kubernetescrd
https://github.com/zs-dima/monitoring-stack-k3s/blob/main/infrastructure/system/weave-gitops/release.yaml
Plus include weave into oauth2-proxy ingress hosts similar to other apps:
https://github.com/zs-dima/monitoring-stack-k3s/blob/main/infrastructure/auth/oauth2-proxy/release.yaml

you will be able to reproduce this issue.


[kmac] Latch absorbed signal to delay Done command

kmac_keymgr interface asserts CmdDone when it sees absorbed signal.
The SHA3 module asserts absorbed signal when it is in StAbsorb but the
next state is StSqueeze. It creates assertion error as only
StSqueeze expects CmdDone.
To break the timing path, latch in absorbed_o is added.
This issue is reported by @udinator

Thanks for preparing this so quickly Eunchan!
I'll test these changes with my local KDF and then update this comment.


Snarky ecdsa foreign field EC group double gadget

Work in progress
Closes #12943

Correct group_double chaining wiring for curves with a = 0 (no external checks)
foreign field EC group double circuit - chaining test - Sheet1 (2).pdf

Correct group double full test (i.e. with external checks)circuit + wiring for curves with a = 0
foreign field EC group double full test circuit - Sheet1 (1).pdf


wrong exception message

[This message is created by hyperf-bot]
Hi @bbbsb, this is a READ-ONLY repository, please submit your Pull Request to hyperf/hyperf repository, this Pull Request will close automatically.


Annotate for nullable reference types

Left about 130 warnings for you to consider, where null-forgiving is involved. :)
Feel free to push my branch for any additional changes.

Awesome work.  I'll work through these remaining warnings today.


Progression range should update on columns change

It seems that progression range is not updated when switching from 1 to 2 columns, and vice-versa. It should behave as resizing the window width.

I’m afraid this is tied to ts-toolkit’s Preference API as a quick experiment on colCount change showed wrong numbers were reported due to the scrollWidth being “cached” and not updated. Now currentPositionNumbers relies on this to find the positions in view(port).
On resize, Playground is relying on the positionChanged listener, so it could be a good idea to make things consistent since changing the number of columns is conceptually a resize of sorts, as is scroll, font-size, font-family, etc. But then maybe this could be overloading this event quite significantly.


Fix for 'regex' early termination of returned rows

Once the regex encountered the first instance of a non-match, it would return without processing the rest of the rows in the statement. This change allows it to process the remaining, only setting the sqlite3_result_int to zero then continuing. This worked fine for the example as it only had one item to process.

Coverage remained the same at 53.063% when pulling 853068c31ef39fcd9785c5ba92beac8a94c781c1 on ShanePerron:patch-1 into 98a44bcf5949f178c8116fa30e62c9ac2ef65927 on mattn:master.

Thank you.


GC v-for elements

Version
2.5.16
Reproduction link
https://codesandbox.io/s/2w1397zw70
Steps to reproduce

Open https://2w1397zw70.codesandbox.io/#/gc
Open DevTools and watch DOM Nodes
Click on the "Add" button (don`t click "Clear")
Follow the "Go back" link
Collect garbage

What is expected?
DOM Nodes are GC`ed
What is actually happening?
Nothing

I've just tested and captured an allocation timeline. There are no DOM nodes retained after pressing "Go back", which means they have been correctly GC-ed.

Pressing "Collect garbage" won't have any effect if something is already GC-ed.

Oh, I'm sorry. I blindly trusted the Performance Monitor tab.
I've added @click for the Dummy component. All DOM nodes and JS event listeners were successfuly GC-ed. But this is only visible through taking a snapshot of the memory. It was a good lesson for me 😄

Hmm... Cannot reproduce the issue. I opened the https://2w1397zw70.codesandbox.io/#/gc page and pressed Add button couple times. Are you sure you don't have other pages in the same renderer process?

@a1ph Here is video (56 s): https://youtu.be/1-zwBCqAExk

Are you sure you don't have other pages in the same renderer process

It was recorded with one tab open.


US15: EPIC: User access by profile and permissions

Epic: https://trello.com/c/e3BUYACf
Profiles: https://trello.com/c/xURLGV60
Permissions: https://trello.com/c/vHIKLAqm

US16 is ok. Waiting to US17 until merging the epic US15 containing both into master.


when i return math.random() i get the error: math is not defined

Challenge Waypoint: Generate Random Fractions with JavaScript has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
function myFunction() {

  // Only change code below this line.

  return math.random();

  // Only change code above this line.
}

(function(){return myFunction();})();

Try capitalizing math. In the future please use the help chat before posting a bug report.
Happy Coding!

LMAO thanks man I did use chat no one responded but I'll try to be more diligent.


Keep Alive not sent when device is not plugged to power source

Hi, we created a Xamarin app and all is working correctly until the device is plugged to the power supply, but when we disconnect it, even with 100% battery, the client stop send the keepalive and the mqtt server disconnect it in a few seconds...
So, is that a problem this MQTTnet library or we need to treat the instance of the library class to be managed in a different way when in battery mode?
thank you very much!

This sounds like some issue with background services / power saving options on the mobile device to me...

Hi @SeppPenner , thank for the reply, but from the xamarin project I cannot manage or force the keepalive push of the library, or you are saying that the library does not check if the device is connected or not to the power source?
or do I have to instance the mqttnet library in a special way to tell the device operative system to do not kill that process? ...
thank you very much

I'm not an expert for Xamarin... I'm not sure if this is an issue with the library or with Xamarin / your project or energy saving options in general.

or do I have to instance the mqttnet library in a special way to tell the device operative system to do not kill that process? ...

I would assume that but I'm not sure.

I assume we cannot do much about this behavior in this library. Please check first how to execute certain tasks when a Xamarin application is suspended etc. due to power saving purposes. Apart from that you can try to avoid using keep alive since the client is simply not able support this.


Why permute the data in Fourier_1d.py

For line 104 ( x = x.permute(0, 2, 1)) in Fourier_1d.py, you change the axis using permute. But I am not clear why do you do that? Is this for some special reasons?

In our implementation, the input tensor is (batch, x, channel). We apply a Linear layer to the channel space, permute it to (batch, channel, x), and then apply convolution layers.
I think the permute operation can be avoided if you directly input tensor as (batch, channel, x) and use 1X1 conv as the Linear layer.

In our implementation, the input tensor is (batch, x, channel). We apply a Linear layer to the channel space, permute it to (batch, channel, x), and then apply convolution layers.
I think the permute operation can be avoided if you directly input tensor as (batch, channel, x) and use 1X1 conv as the Linear layer.

Thanks for your explanation! I understood.

Thanks for your explanation! I understood.


Extensions are not registered in the host if referencing local Microsoft.Azure.WebJobs.Extensions.* package

I'm trying to reference a local Microsoft.Azure.WebJobs.Extensions.SignalRService version by updating the version to a new version here.
https://github.com/Azure/azure-functions-dotnet-worker/blob/59cd1cb1357a71504153cb450e7dc3ac945be2e4/extensions/Worker.Extensions.SignalRService/src/Properties/AssemblyInfo.cs#L6
Then I add the in-process extension package to my local Nuget source with:
nuget add .Microsoft.Azure.WebJobs.Extensions.SignalRService.1.11.0-alpha.20230419.1.nupkg -source C:\Users\***\.nuget\packages

Then in an isolated function app, add a project reference to the isolated extension Microsoft.Azure.Functions.Worker.Extensions.SignalRService. When I build the isolated function app, there is no error. I guess the restore is successful because if I don't add the in-process extension package to local Nuget source, it would fail to find the specific version. However, when I run the function app, I get the following errors:
[2023-04-19T08:34:24.786Z] The 'Broadcast' function is in error: The binding type(s) 'signalREndpoints, signalRNegotiation, signalRTrigger, signalR' are not registered. Please ensure the type is correct and the binding extension is installed.
[2023-04-19T08:34:24.788Z] The 'JoinGroup' function is in error: The binding type(s) 'signalRTrigger, signalR' are not registered. Please ensure the type is correct and the binding extension is installed.
[2023-04-19T08:34:24.789Z] The 'JoinUserToGroup' function is in error: The binding type(s) 'signalRTrigger, signalR' are not registered. Please ensure the type is correct and the binding extension is installed.

I'd like to know what're the proper steps to using a local in-process extension version? It'd be better if we had a contribution guide.

What is the contents of your extensions.json file when you build your function app? If SignalR is listed there, can you verify the appropriate assemblies are also in the .azurefunctions folder?

Do you mean the extensions.file in bin\output directory? The SignalR is not listed there. Here is the content:
{
  "extensions": [
    {
      "name": "Startup",
      "typeName": "Microsoft.Azure.WebJobs.Extensions.FunctionMetadataLoader.Startup, Microsoft.Azure.WebJobs.Extensions.FunctionMetadataLoader, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=551316b6919f366c",
      "hintPath": "./.azurefunctions/Microsoft.Azure.WebJobs.Extensions.FunctionMetadataLoader.dll"
    }
  ]
}

And another interesting thing is, in the .azurefunctions folder, the assemblies referenced by Microsoft.Azure.WebJobs.Extensions.SignalRService are already there, but Microsoft.Azure.WebJobs.Extensions.SignalRService itself is not there.

@jviau I have uploaded a project https://github.com/Y-Sindo/azure-functions-dotnet-worker/tree/repro to reproduce the problem.  https://github.com/Azure/azure-functions-dotnet-worker/commit/20fe0b8bdc049a569d587e57a6083a402eded9ac is the code update I made.
Repro steps:

Add the customized in-process extension to local Nuget cache. In the root path of the repo, execute nuget add Microsoft.Azure.WebJobs.Extensions.SignalRService.1.11.0-alpha.20230419.1.nupkg -source [your-nuget-cache-path]
Run the function app samples/FunctionApp , and you will see the error logs as follows:

[2023-04-20T06:29:42.602Z] The 'SignalRTrigger2' function is in error: The binding type(s) 'signalRTrigger' are not registered. Please ensure the type is correct and the binding extension is installed.

This file is what controls host extension discovery & loading. Without SignalR there it is never loaded, triggers never registered, and thus your errors. Extensions get added to that file as part of build - the packages described by ExtensionInformationAttribute are added to a temporary csproj, restore/build is ran on it, then we scan the restored assemblies for marker types to indicate it has at least some triggers and needs to be added to the extensions file. Since this is not happening, either (1) SignalR is failing to restore at all, or (2) the marker types are now gone from the local SignalRService package you authored.
When you downgrade to the older version, does SignalR extension show up in extensions.file?

I believe the restore is successful because I can see the logs in the Visual Studio build output as follows:
1>Determining projects to restore...
1>Restored C:\Users\xxx\AppData\Local\Temp\iqilq20m.prh\WorkerExtensions.csproj (in 1.63 sec).
1>WorkerExtensions -> C:\Users\xxx\AppData\Local\Temp\iqilq20m.prh\buildout\Microsoft.Azure.Functions.Worker.Extensions.dll
1>Done building project "DotnetIsolated-ClassBased.csproj".

And I can see SignalRService package is in the WorkerExtensions.csproj as follows.
<Project Sdk="Microsoft.NET.Sdk">
    <PropertyGroup>
        <TargetFramework>net6.0</TargetFramework>
        <LangVersion>preview</LangVersion>
        <Configuration>Release</Configuration>
        <AssemblyName>Microsoft.Azure.Functions.Worker.Extensions</AssemblyName>
        <RootNamespace>Microsoft.Azure.Functions.Worker.Extensions</RootNamespace>
        <MajorMinorProductVersion>1.0</MajorMinorProductVersion>
        <Version>$(MajorMinorProductVersion).0</Version>
        <AssemblyVersion>$(MajorMinorProductVersion).0.0</AssemblyVersion>
        <FileVersion>$(Version)</FileVersion>
        <CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
    </PropertyGroup>
    <ItemGroup>
        <PackageReference Include="Microsoft.NETCore.Targets" Version="3.0.0" PrivateAssets="all" />
        <PackageReference Include="Microsoft.NET.Sdk.Functions" Version="4.1.3" />
        <PackageReference Include="Microsoft.Azure.WebJobs.Extensions.Storage.Blobs" Version="5.1.0-beta.1" />
<PackageReference Include="Microsoft.Azure.WebJobs.Extensions.Storage.Queues" Version="5.0.0" />
<PackageReference Include="Microsoft.Azure.WebJobs.Extensions.SignalRService" Version="1.8.0-alpha.20230421.1" />

    </ItemGroup>
</Project>

I have also checked out the local source code used to build the SignalRService package to version 1.8.0, equivalent to the version currently used by isolated worker extension. But SignalR extension is still missing in extensions.json.
Here are the steps that I build local SignalR package:

In azure-sdk-for-net repo, execute git checkout tags/Microsoft.Azure.WebJobs.Extensions.SignalRService_1.8.0
Go to folder sdk\signalr\Microsoft.Azure.WebJobs.Extensions.SignalRService  and get the nuget package with dotnet pack src\Microsoft.Azure.WebJobs.Extensions.SignalRService.csproj -o artifacts
Add the package to local NuGet cache: nuget add .\artifacts\Microsoft.Azure.WebJobs.Extensions.SignalRService.1.8.0-alpha.20230421.1.nupkg -source C:\Users\xxx\.nuget\packages\

Am I packing the package in the wrong way?

@jviau If you could not reproduce the issue, please let me know.

Finally, I have found that it was due to the SignalR package is a pre-release version and by default not picked up by NuGet.  I added <SkipDevBuildNumber>true</SkipDevBuildNumber> in the SignalR package to remove the pre-release prefix to make it work.


[ROADMAP] Navigation

I am looking forward to the new navigation library announced here:
https://github.com/facebook/react-native/wiki/Roadmap

Right now there are a large number of navigation libraries. We don't think one navigation library will be enough for every use case, but we do think we can make it better. The goal is for this new navigation library to be ideal for apps that handle navigation in JavaScript. Once it is released and stable, we can deprecate Navigator, NavigationExperimental, and ExNavigation.

related: https://dev.to/machadogj/react-navigation-with-redux-and-immutablejs?utm_content=buffer39860&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer

NavigationExperimental is a torture right now. Looking forward to see it changed to ReactNavigation

feel free to sketch something together if you have inspiration. I don't see myself having the time for the next few months.

I think I'll have time next week. I will try to properly design it to React Navigation

Would be very nice to have an experimental branch on Pepperoni that uses react-navigation. I'll also see if I can find some time for integrating it.

It's happening :tada: :tada: :rocket:

https://github.com/futurice/pepperoni-app-kit/pull/188

We finally changed to react-navigation with merging #189 :) thanks for submitting the PR @FruitieX !


[Wallet] CELO price in chart does not match oracle reported exchange rate

Expected Behavior
The exchange rate in the gold chart matches the one reported by the oracles
Current Behavior
There is a discrepancy between the exchange rate listed in gold chart and the one reported by the oracles. This could be due to an estimation issue for the script that collects gold exchange rates and puts them in firebase: https://console.firebase.google.com/u/1/project/celo-mobile-mainnet/database/celo-mobile-mainnet/data/~2FexchangeRates

See discussion here: https://celo-org.slack.com/archives/C0168LEGB7U/p1594226212063600

Updating these configs may fix the issue: https://github.com/celo-org/celo-monorepo/blob/master/packages/notification-service/src/exchange/exchangeQuery.ts#L8


first draft of string table

we need to add interior mutability for the string table to be usable beyond the lexer stage.
Contains unsafe code, needs a detailed review.

I would be fine lke it is now, too.
I started integrating StringTable with the Lexer but had some troubles with lifetimes:
anonymous lifetime of  &mut self in the lexer methods != lifetime of the &'t mut StringTable member, and since the &'t mut StringTable member of lexer can't be used by value, the lifetime during the call self.symtab.intern(...) is shorter than the lifetime required for the result of that call.
I had to rebase this branch onto the lexer branch, my current state is in branch https://github.com/comprakt/comprakt/tree/problame-string-interner-into-lexer
The words above probably make more sense if you look at the latest commit (and try compile it, get the error)


elm-github-install: init at 1.0.1

Motivation for this change
This add elm-github-install, an alternative package manager for elm.
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Thanks :)

FTR more recent versions of this software are MIT licensed.


Question regarding Kong 2.8 support in latest helm chart version (2.33.3)

Greetings,
We are looking to upgrade our Kong images to 3.x from Kong 2.8. We want to start by upgrading the chart without upgrading the image which appears to be possible according to the upgrade notes.  We are currently on chart version 2.8.2. We tested going to chart version 2.33.3 while preserving 2.8 images and things look like they are working well.
Is it intended to continue supporting older 2.8 images with newer versions of the helm chart or were we just lucky?
We see these label changes across many resources and we can't override them (they come from Chart.AppVersion) which is giving us doubts:
-     app.kubernetes.io/version: "2.8"
+     app.kubernetes.io/version: "3.5"

Thank you!
Martin

Chart support for older Kong and controller versions is on a fairly ad hoc basis. In general, chart changes tend not to break older Kong and controller resources, because the Kubernetes resources it creates a fairly application version agnostic and don't end up breaking compatibility with them.
Chart compatibility issues more often arise for the Kubernetes version as Kubernetes APIs are introduced and deprecated.
Our application support lifetime policies for Kong and the controller do apply to the chart. Kong 2.8 is the current LTS release and we will fix incompatibilities between it and the chart when found until it reaches EOL. We do usually rely on user reports to find these, however, as configurations vary considerably between installations, and we can only test a limited set of common base configurations (e.g. DB-less versus DB-backed) ourselves to check baseline compatibility.
https://docs.konghq.com/kubernetes-ingress-controller/latest/reference/version-compatibility/ covers compatibility between controller+Kubernetes and controller+Kong versions. Note that while LTS versions of Kong are still supported, this is for bugfixes, not new features. Controller 3.x breaks compatibility with Kong 2.8, and any controller fixes needed for new 2.8 bugs would land in a 2.x controller release.
Older EOL versions often will still work with more recent chart releases, but we won't necessarily provide a fix for them. We will still review issue reports and make fixes for older versions if we determine that they're simple enough and wouldn't break compatibility with newer versions.
Helm's AppVersion field accepts only a single value, so it's set to the default version of Kong included in a chart release. It doesn't imply anything about compatibility, and you can ignore it.
I think that should cover everything you'd need to know, so I'll go ahead and close this out. If you do have further questions, respond back and we'll reopen it.


3.0.2 - Updates to GitHub Action dependencies

further updates to dependencies break stuff! I'm closing this pr and attempt!


Manipulate Arrays with Shift - Incomplete Directions

Challenge http://www.freecodecamp.com/challenges/waypoint-manipulate-arrays-with-shift has an issue:

The directions should state that myRemoved should contain the first element of myArray.

Related to: https://github.com/FreeCodeCamp/FreeCodeCamp/issues/1867

Thanks @AryanJ-NYC this should be an easy fix.
Set `myRemoved` to the first value of `myArray` using `shift()`.


HolderOf does not work on drops

Is there an existing issue?

[X] I have searched the existing issues

What happened?
I want to mint reflection
but I cannot because UI tells me 'Conditions not Met'

However I have minted my complexity NFT
Please reproduce in steps

Mint Complexity
Go to Reflection
You are unable to mint

Expected Behavior
I expect to be able to mint reflection when I am holder of complexity
What browsers are you seeing the problem on?
No response
At which address did you encounter bug?
No response
Are you logged in?
None
Which wallet you are using?
No response
At which chain did you encounter bug?
No response
Screenshots
~
Wallet Address & Transaction hash
No response
Relevant log output
No response
Payment link for reward
https://canary.kodadot.xyz/dot/transfer/?target=<My_Polkadot_Address_check_https://github.com/kodadot/nft-gallery/blob/main/REWARDS.md#creating-your-dot-address>
Code of Conduct

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

pls anyone from @kodadot/internal-dev

for me it works:

@Jarsen136 For me, it's ready to mint, but it failed on mint. Missing some function to call fxart endpoint, such as https://github.com/kodadot/nft-gallery/blob/9fbffa9d3ee9dac70e8a56722b3ee0a16fdbe977/components/collection/drop/PaidGenerative.vue#L289-L326

Yes the code is wrong.
Please remove api.tx.balances.transfer
and supply correct value here in api.tx.nfts.mint
mint price is set via price
"mint_price":NULL
ROFL


Avoid unintended use of toString-based sort; closes #3.

Fix taken from https://github.com/tonyg/synchrotron/commit/7eb715d08d3c7b479b30b9f413a4a61db9940e82.

@langram Any updates on this? This fixes a pretty serious issue with the diff algorithm, and would be nice to see it in the lib.

With this patch A,b,c  a,b,c  a,B,c still conflicts due to > instead of >= https://github.com/Dmole/node-diff3/commit/61fdbee8613478e3e92a337a79256bbf6175213e

@Dmole, the output of diff3 -m on your example gives the same results as Diff.diff3_merge in synchrotron. So I think the synchrotron code is working as intended. It's still an open question whether this particular form of diff3 algorithm is the "right thing", of course!

@tonyg with what input? Without that extra change diffs that touch but do not overlap are falsely reported as a conflict.
What is wrong about the merge3 algorithm? It now seems to be working comparably to other diff3 implementations I use regularly, though I have not really done any though testing.
(or are you just commenting that all merges should only be used as an assist and should really be sanity checked by a human?)

@Dmole, I mean specifically the output of diff3 -m a o b where o contains a\nb\nc, a contains A\nb\nc and b contains a\nB\nc. It reports a conflict just like the one reported from Diff.diff3_merge. So when you say "falsely reported as a conflict", I see what you mean, but am not sure that calling output that matches Unix diff3 "false" is the right thing to do here.
Regarding alternative algorithms (such as your variant!), I just mean to refer to the fact that none of diff, diff3 or merge are able to be said to be "correct" since they're not aware of the meaning of the texts they affect, and that different approaches are appropriate in different situations depending on the contents of the files being manipulated. This old wikipage might be interesting.

Wow I did not even notice that, I wonder why unix merge is doing that, there must be a [historical] reason...
(Yah context aware diff never really took off.)


Feat/cli_failure

Codecov Report
Patch coverage has no change and project coverage change: -8.61 :warning:

Comparison is base (676717a) 30.89% compared to head (be4ddf1) 22.29%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #136      +/-   ##
==========================================
- Coverage   30.89%   22.29%   -8.61%
==========================================
  Files          98        6      -92
  Lines        2418      157    -2261
==========================================
- Hits          747       35     -712
+ Misses       1671      122    -1549

Impacted Files
Coverage Δ

packages/sidecar/lib/src/client/cli_client.dart

...kages/sidecar/lib/src/reports/stdout_reporter.dart

...s/sidecar/lib/src/server/starters/cli_starter.dart

...decar/lib/src/services/active_project_service.dart

...ecar/lib/src/utils/analysis_context_utilities.dart

...ar/lib/src/protocol/source/source_file_edit.g.dart

...rc/analyzer/providers/active_target_providers.dart

...decar/lib/src/protocol/communication/requests.dart

...car/lib/src/protocol/communication/requests.g.dart

...idecar/lib/src/server/starters/server_starter.dart

... and 82 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Outdated images.

Outdated images. Connections is now on left sidebar.

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

ID: 97bf9b6c-5628-f18c-7027-45b21eb3b6bc
Version Independent ID: a4394ad5-9d46-2a6d-16d9-48b0c88fb401
Content: Learn to connect to your data using connections and on-premises data gateways - Power Automate
Content Source: articles/add-manage-connections.md
Service: flow
GitHub Login: @stepsic-microsoft-com
Microsoft Alias: stepsic

Hi @quinlanharsch . Thanks for pointing this out. We're currently updating these docs to match the current UI.  I went ahead and fixed this one now, so it should be live shortly. I do appreciate the heads up.


No spelling mistake warnings for my graphql variables

Describe the bug
I would expect to get spelling mistake information on my GraphQL variables
To Reproduce
Link to Repo with Reproduction or Steps to Reproduce:

Create a query/mutation somewhere which includes variables
Have spelling mistakes within your variable name
See that nothing is wrong

Expected behavior
I would expect to get the same spelling error help like with other variables within IntelliJ in my GraphQL variable names.
Screenshots
Here you can see how IntelliJ shows my mistake on my JavaScript variable, but not in my GraphQL variable

Version and Environment Details
Operation system: Windows 10
IDE name and version: IntelliJ IDEA 2021.1.3 (Ultimate Edition)
Plugin version: 2.9.1

Hi! Fixed it, will be available in the next release.

I got the update today and it looks great. But it's only working for the query naming and not variables as seen on the image below:

Hi! I enabled generic support for most of the GQL entities, e.g. fields, query names, arguments, etc. But with variables there is an issue that their current implementation is still not completed, you can't resolve variable references and rename them, for example. This breaks spellchecker inspection, so I need to fix it first and I'm going to do it ASAP. I'll reopen this issue for now, though. Thank you for your feedback!


[Feature Request] Also show files under subdirectories when run LeaderfFile

When I run :LeaderfFile /path/to/bundle/, only file under bundle will be shown. Instead, when I run FZF /path/to/bundle/, even files under subdirectories will also ben shown. Just like following image shows:

Could LeaderfFile has the similar behavior like FZF?

What is the output of :echo g:Lf_Debug_Cmd?

@Yggdroot The output is:
git ls-files --recurse-submodules && git ls-files --others --exclude-standard

I think this command can list all the files.
Can you have a try this command in the terminal?
what is in your .gitignore?

Please have a try: Leaderf file --no-ignore.


ability to change the default image and icon

ability to change the default image and icon

Hey, thanks for the PR!
The icons look a bit too big though :)
I wanna release this cool feature, could you take care of the size?

Sure
Sent from my iPhone

On 19 May 2019, at 12:16 PM, Matteo Merola<EMAIL_ADDRESS>wrote:
Hey, thanks for the PR!
The icons look a bit too big though :)
I wanna release this cool feature, could you take care of the size?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey, thanks for the PR!
The icons look a bit too big though :)
I wanna release this cool feature, could you take care of the size?

no too much work to be done here user can overwrite the css class sample like

.sc-launcher {
    width: 40px !important;
    height: 40px !important;
}


llama: fix race in parallel make

Ensure the cleanup step completes before starting to build targets

It looks like .NOTPARALLEL is recursive so this prevents the entire build from being parallel, which is a significant slowdown. Surprisingly (to me at least), if I apply it to only clean-payload it also prevents parallel compilation. I don't see this with .WAIT, as expected. I'm not sure what the best syntax is to allow compilation to happen in parallel but all of the pre- and post-requisits to be serialized around it.

Closing in favor of a more extensive refactoring in #6924


Yarn Berry: Run commands in update-lockfile mode

Yarn Berry commands related to performing updates can run in a mode called update-lockfile, which was purpose-built for exactly what Dependabot does:
- `update-lockfile` will skip the link step altogether, and only fetch packages
  that are missing from the lockfile (or that have no associated checksums).
  This mode is typically used by tools like Renovate or Dependabot to keep a
  lockfile up-to-date without incurring the full install cost.

This makes yarn berry updates significantly more performant, but it has the downside that when the yarn cache is committed to the repo, old entries in there are not cleaned up. Everything still works as expected when this happens, but over time it could lead to that cache folder getting larger than is necessary.
I've opened an issue about this upstream:
https://github.com/yarnpkg/berry/issues/4886, not entirely sure if this is a bug or just a consequence of how this works.
For now I think it's worth the trade-off, as many projects don't commit the cache folder to repo, and the performance benefits are very significant.
I'll try to find some time to address this upstream.

On a large-ish repo:
time yarn add<EMAIL_ADDRESS>yarn add<EMAIL_ADDRESS>9.02s user 3.63s system 51% cpu 24.357 total

vs
time yarn add<EMAIL_ADDRESS>--mode=update-lockfile
yarn add<EMAIL_ADDRESS>--mode=update-lockfile  2.50s user 0.25s system 74% cpu 3.674 total

Another option could be to detect if there is a yarn cache folder present, and if there is not, then we use the update-lockfile mode. From the logs it does appear that the most costly step is fetching all the missing packages, which we would not have to do when there is a cache folder committed to the repo.

Another option could be to detect if there is a yarn cache folder present, and if there is not, then we use the update-lockfile mode.

I like this idea, I'm not sure we need to block on adding this since we are in beta and as you say, committing the cache is potentially not something many projects do 🤔

Another option could be to detect if there is a yarn cache folder present, and if there is not, then we use the update-lockfile mode.

I like this idea, I'm not sure we need to block on adding this since we are in beta and as you say, committing the cache is potentially not something many projects do 🤔

It is recommended by yarn:

Starting from Yarn v2, Yarn will by default configure the cache to be local to your project. This is done to make it easier for you to store it as part of your repository, which we believe is the best way to ensure that your projects can still be installed just fine regardless of the availability of your package registries.

I don't have any numbers, but anecdotally I've seen more repo's that don't have it in version control


Colorized output is dependent on stdout being a tty

It seems that the default implementation draws to stderr, but whether the output is colorized is dependent on whether stdout is a tty, so if you do something like foo > log, you get progress bars, but they're uncolored.
I'm not sure if there's a reasonable fix here without a lot of rearchitecting: it seems to me that console needs to be in charge of printing a styled string, to be able to know whether it should be colorized or not.

You can import clicolors-control and override it if you want a different behavior.

Would it make sense to use the draw target for tty detection?

In case somebody else runs into the same issue, it's now:
console::set_colors_enabled(true);


Rename ros-planning org

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

Project coverage is 47.22%. Comparing base (c174715) to head (d4d4aba).
Report is 15 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3603      +/-   ##
==========================================
+ Coverage   47.15%   47.22%   +0.07%
==========================================
  Files         603      603
  Lines       58999    59142     +143
  Branches     6969     7012      +43
==========================================
+ Hits        27814    27921     +107
- Misses      30773    30803      +30
- Partials      412      418       +6

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


Support Apple Silicon

Blender supports ARM64 chips for macOS. (e.g. Apple M1)
But the DDS addon will raise an error (be560160f997b2b2b346bce425c9379ced61b883) for them because libtexconv.dylib was built for x64.
It's possible to build the ARM64 version but I don't have mac for testing.
~Please comment if you want the ARM64 build and you can test it with Apple silicon.
I'll upload it on this thread.~

From v0.4.0, the addon uses universal binaries. I haven't tested it but it should support Apple Silicon.
Please comment here if you can try it with Apple Silicon.

The CI workflow uses Apple Silicon now.

About GitHub-hosted runners - GitHub Docs
GitHub Actions: macOS 14 (Sonoma) is now available - The GitHub Blog

I'll close this issue.