mpmc_loffli: oldHead should be reloaded from m_head when compare_exchange_weak failed

It could be fixed like this,
bool MpmcLoFFLi::pop(Index_t& index) noexcept
{
    Node oldHead;
    Node newHead;

    do
    {
        // Reload oldHead here
        oldHead = m_head.load(std::memory_order_acquire);
        newHead = oldHead;

        // we are empty if next points to an element with index of Size
        if (oldHead.indexToNextFreeIndex >= m_size || !m_nextFreeIndex)
        {
            return false;
        }

        // NOLINTNEXTLINE(cppcoreguidelines-pro-bounds-pointer-arithmetic) upper limit of index set by m_size
        newHead.indexToNextFreeIndex = m_nextFreeIndex.get()[oldHead.indexToNextFreeIndex];
        newHead.abaCounter += 1;
    } while (!m_head.compare_exchange_weak(oldHead, newHead, std::memory_order_acq_rel, std::memory_order_acquire));
   // ...
}

bool MpmcLoFFLi::push(const Index_t index) noexcept
{
    // ...

    Node oldHead;
    Node newHead;

    do
    {
        // Reload oldHead here
        oldHead = m_head.load(std::memory_order_acquire);
        newHead = oldHead;

        // NOLINTNEXTLINE(cppcoreguidelines-pro-bounds-pointer-arithmetic) index is limited by capacity
        m_nextFreeIndex.get()[index] = oldHead.indexToNextFreeIndex;
        newHead.indexToNextFreeIndex = index;
        newHead.abaCounter += 1;
    } while (!m_head.compare_exchange_weak(oldHead, newHead, std::memory_order_acq_rel, std::memory_order_acquire));
    // ...
}

@xywanz I need to have a closer look, but oldHead will be updated if compare_exchange_weak fails. Which version of iceoryx are you using?
Do you have this fix in the version you use: https://github.com/eclipse-iceoryx/iceoryx/issues/2351

It's my fault. compare_exchange_weak will update oldHead if it fails.


Add Pantograph unlock option

An option to connect your wallet through Pantograph would be a nice addition for the unlock options at https://dex.tomochain.com/unlock.
The required javascript to connect with Pantograph is found here: https://pantograph.io/pantograph-extension-custom-code/

[ ] Add unlock wallet with Pantograph

Refer to commits: tomochain/tomomaster@3748aab, tomochain/tomomaster@ba58855 for implementing

[ ] logo pantograph

Available on the devnet.


Allow inverting new v3 single-db logic to assume single-db unless otherwise specified

I'm mainly interested in this for the plugin_mysql_server.
At HubSpot currently all keyspaces are unsharded, and cross-db queries are not allowed. This will change in the future, but we would probably assume unsharded/single-db by default. We are planning to use plugin_mysql_server as the primary entry point for users to run ad hoc queries from their laptops. As it stands right now, in order to get maximum query flexibility (useful for ad-hoc querying), every user would need to always remember to connect to keyspace/0.
I'd like to invert this logic, so that the default is keyspace/0 unless explicitly requested or a keyspace has multiple shards. I imagine an implementation something like this:
const(
  assumeSingleDbConnections = flag.Bool( ...., false, ... )
)
func (vh *vtgateHandler) ensureKeyspaceTarget(ctx context.Context, schema string) string {
    keyspace, shard := topoproto.ParseKeyspaceOptionalShard(schema)
    // allow `keyspace/*` to connect to multiple dbs?
    if shard == "*" {
      return keyspace
    }
    if shard != "" || !*assumeSingleDbConnections {
        return schema
    }

    // detect shard count for keyspace. Something like this, or a better approach?
    srvKeyspace, err := vh.vtg.router.serv.GetSrvKeyspace(ctx, vh.vtg.resolver.cell, keyspace)
    shardCount := 1// count srvKeyspace.Partitions[0].ShardReferences[0]

    if shardCount == 1 {
        return fmt.Sprint("%s/0", keyspace)
    }
    return schema
}

I'm open to a more baked in solution in VTGate if there's interest, but am happy to keep this in the plugin as well.
@alainjobart @sougou

Closing this in favor of expanding V3 capabilities in #2723


Hash collisions should cause failure

@abaldwin88
Hello Alex, I've created little tool, which helped me find one bug. Please check it out here: https://github.com/alex-bender/roamer_collisions

I was reviewing whole project and noticed only now that hash is 12 for now. I will test with it later.

Also, what do you think about including file size to the hash calculation? It will fix that .git folder issue.

@alex-bender That's a great tool!  I just arbitrarily picked 12 for the hash length.  This tool should help us pick a logical cutoff length.  It may also prove that we should give users the option to manually set the hash length.
One thing I noticed was that the hash calculation in your tool needs an adjustment to match roamer.  Roamer uses the full path where as you are just using the filename.
I changed both hash_seed assignments to use abs_path...
hash_seed = abs_path + str(os.path.getmtime(abs_path))

I started running time ./findit.py ~/ but my home directory is massive so it looks like it might take awhile.  I'm going to let it run overnight and report back the results.  I'd be curious to hear the results for your home directory after making the above modification.

I've changed length to 12 and hash_seed is calculating based on abs_path now.
I'm gonna make it more informative by adding file counters.
I can inform you about new commits if you want.

@abaldwin88 Now I didn't think that it's a great tool. I've changed the length to 12 and hash_seed assignments to abs_path and ran it overnight (unfortunately without time) so here is the results:
python3 findit.py /home/
Visited items: 880674
Hash, count
7b12bc7f79f3 1
2abc40865a50 1
957fdd8e9488 1
25ab779df9f2 1
0fc6cff4960b 1
61fdaa9e5f67 1
681e5c8d267e 1
ea52a1cfad14 1
77f3f3cc343f 1
71a3797932bf 1

Seems that it was work in vain.

I certainly wouldn't call it work in vain.  It was a good pragmatic test for a potential issue.  Here are my results...
Visited items: 2949460
Hash, count
35d6be85ef1d 2
c132d1f58b0c 1
223c107643a9 1
d3719fc18d2a 1
56780739e35c 1
625a2f9db994 1
9fc7e35e17ad 1
e3bd67cd5752 1
985f245e8d72 1
789400e7382b 1
    17835.82 real     17466.23 user       265.73 sys


Error message when merging or shift clicking

Everytime you shift click to create mutliple tools or merge tools you get this error message :

Is there a way it could be disabled ?
Thanks in advance for your time considering my request !

When I disabled this plugin and tried to reciprocate the bug I still found it so I figured it's coming from another one, sorry for the useless post


[+] Adding Research paper

Hi!
I am adding some Research papers (1 book,  a pdf), and I added 2 links as well, one is embedded.sw.net's Cipher Refs; Even if this merge is not related to the 'ChaCha' directly, It still serves some usefulness in the future;
Note. If this is wrong, or if this merge could be improved, do point it out!

Replying to the bot: Yes, it is only Docs, as expected from me - as I rarely "open a pull request With code", I always start small, if it is code I contribute to, and it's the first time (in that repo) that I contribute as; then it will be stuff I am sure about;
Anyway! :)

ScreenShot so people don't have to go and look what is going to be merged
(do still check it though)

Thanks! point out if anything could be improved in the PR next time I do one !

the toc Cryptobook src
embeddedsw.net's Cipher Reference List


Throttle libp2p validation

During Prater genesis our node did nothing more than validate and process AggregateAndProof from gossip. Download and inspect the profile below.

Our node should have some queue to prevent being DDOS by gossip messages.
How should this queue be designed?
Should we prioritize some messages (blocks) over others (attestations)?

lodestar-64vali-pratergenesis-CPU-20210323T092838.cpuprofile.zip

Between 2021-03-23 15:14:19 and 2021-03-23 15:15:41 our Beacon node on Prater validated 487 AggregateAndProof and did nothing else.

 How are the old attestations arriving now instead of the new ones?
Can the attestation pre-state status be cached so it's not re-tried and failed 768 times?


Calculate asset composition via orders

Current asset composition hide founds, that are blocked while stacking. LDCELR is stacked freezed coins
Binance API doesn't support EARNs yet https://dev.binance.vision/t/earn-locked-staking/1453/24

commit 13b1acd9966c6f92ac9123087fedbe3f052767bc


Error occurred when executing ADE_AnimateDiffModelSettingsSimple:

`Error occurred when executing ADE_AnimateDiffModelSettingsSimple:
AnimateDiffSettings.init() got an unexpected keyword argument 'motion_pe_stretch'
File "/home/xxx/Masaüstü/stable-diffusion-webui/extensions/sd-webui-comfyui/ComfyUI/execution.py", line 155, in recursive_execute
outputs_ui[unique_id] = output_ui
File "/home/xxx/Masaüstü/stable-diffusion-webui/extensions/sd-webui-comfyui/ComfyUI/execution.py", line 85, in get_output_data
if isinstance(r, dict):
File "/home/xxx/Masaüstü/stable-diffusion-webui/extensions/sd-webui-comfyui/ComfyUI/execution.py", line 78, in map_node_over_list
def get_output_data(obj, input_data_all):
File "/home/xxx/Masaüstü/stable-diffusion-webui/extensions/sd-webui-comfyui/ComfyUI/custom_nodes/ComfyUI-AnimateDiff-Evolved/animatediff/nodes_gen1.py", line 218, in get_motion_model_settings
motion_model_settings = AnimateDiffSettings(`

i also tested another workflow and giving same result. after update it happend but i dont remember what i updated on comfyui. it was something like named "node" ...

Thanks for the report, issue should now be fixed with that the changes I have now pushed. The old motion model settings should now work as intended. With the update I did several hours ago, motion model settings nodes are now deprecated (and hidden), and the intended way to modify PE is to use AnimateDiff Settings node (under ad settings). For backwards compatiblity, motion_model_settings inputs and ad_settings inputs both work the same. Here are some examples of how the nodes go together:

Issue should be solved, so I'm closing.


Reuse Compliance

Repository update according to the updated copyright/licensing standard.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: KDS42:x: NGorbarovYou have signed the CLA already but the status is still pending? Let us recheck it.

OK

Pull Request verified and accepted. Ready for merge.

Ready for merge.


Week 3 updated

Project
Name of the project
Changes
What was updated (new pages, weekly update, etc.)
Notes
If there are any further notes.

LGTM!


WebSocket schema

Hi again.
I can see /api/socket dispatches positions and devices properties. Referring to the AsyncSocket.java src, I see events also being dispatched. (java not being a strong suit of mine, I'm not exactly sure how it's being implemented tho.)

Is it safe to assume that only these three properties are being emitted from this endpoint?
Also could this be used to send device commands?

Yes, there are up to 3 properties (positions, devices and events). WebSockets are only used for live updated. For commands there is REST API.

OK. Thanks.


unpickling circuit from 0.16

I'm loading some circuits that have been pickled in 0.16 and try to load them in 0.17. Because they don't have Bit._repr and  QuantumCircuit._metadata (added in #5272 and #5270 respectively), after loading it very hard to work with them without getting errors like:
AttributeError: 'QuantumCircuit' object has no attribute '_metadata'

This PR checks if the internal attribute exists at property calling time.

It seems that we don't have a well-defined policy on supporting serialized circuits with previous versions.


WIP: Use kubeadm bootstrapper in circleci

The kubeadm bootstrapper will allow us to test with new versions of k8s quicker than official releases of minikube.

@cmluciano: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
76a8e56b388fe905af696b4f22237b0e8b55e895
link
/test e2e-smoke

prow/istio-pilot-e2e.sh
d2638e36923b0f5b1c25af51e3aa66ff9adceb31
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e

Awaiting fix for https://github.com/istio/istio/issues/3108

The fix is in but you might have to rebase for CircleCI to pick it up (regardless the test doesn't seem to be required at the moment so all that is needed is an approval for someone [I don't have sufficient background to do a review on this type of change])


[BACKLOG-20951] - implementing safe stop function

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd clean install && mvn -B -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd site

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  assemblies/static/src/main/resources/ui/trans-toolbar.xul
  engine/src/it/java/org/pentaho/di/trans/safestop/SafeStopTest.java
  engine/src/it/resources/safe-stop-gen-rows.ktr
  engine/src/main/java/org/pentaho/di/trans/Trans.java
  engine/src/main/java/org/pentaho/di/trans/step/BaseStep.java
  engine/src/main/java/org/pentaho/di/trans/step/StepInterface.java
  engine/src/main/java/org/pentaho/di/trans/steps/script/ScriptDummy.java
  engine/src/main/java/org/pentaho/di/trans/steps/scriptvalues_mod/ScriptValuesModDummy.java
  engine/src/main/java/org/pentaho/di/trans/streaming/common/BaseStreamStep.java
  engine/src/main/java/org/pentaho/di/www/StopTransServlet.java
  engine/src/test/java/org/pentaho/di/www/StopTransServletTest.java
  ui/src/main/java/org/pentaho/di/ui/spoon/trans/TransGraph.java
  ui/src/main/resources/org/pentaho/di/ui/spoon/messages/messages_en_US.properties

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: <0.1% (click to expand)
org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -0.4% :small_red_triangle_down:
Complexity Change: -0.5% :small_red_triangle_down:

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change: -3.3% :small_red_triangle_down:
Line Change: -3.9% :small_red_triangle_down:

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -0.9% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.step.BaseStep

Branch Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Method Change: -1% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -1% :small_red_triangle_down:
Complexity Change: -1.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.ifnull.IfNullMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.9% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Branch Change: -2.6% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.streaming.common.BaseStreamStep

Complexity Change: -0.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:
Line Change: -0.1% :small_red_triangle_down:
Method Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.Trans

Branch Change: -0.1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:
Method Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.gpload.GPLoadMeta

Branch Change: -0.9% :small_red_triangle_down:
Complexity Change: -0.8% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

Note: The list of offending coverage changes extends beyond the presented results and was truncated to prevent reaching the comment size limit.

License header violations

:heavy_exclamation_mark: Couldn't find acceptable copyright on engine/src/it/java/org/pentaho/di/trans/safestop/SafeStopTest.java

:heavy_exclamation_mark: Couldn't find acceptable license on engine/src/it/java/org/pentaho/di/trans/safestop/SafeStopTest.java

:heavy_exclamation_mark: Copyright year is not the current year on engine/src/main/java/org/pentaho/di/trans/Trans.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on engine/src/main/java/org/pentaho/di/trans/step/BaseStep.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on engine/src/main/java/org/pentaho/di/trans/step/StepInterface.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on engine/src/main/java/org/pentaho/di/trans/steps/script/ScriptDummy.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on engine/src/main/java/org/pentaho/di/trans/steps/scriptvalues_mod/ScriptValuesModDummy.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on engine/src/main/java/org/pentaho/di/www/StopTransServlet.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on engine/src/test/java/org/pentaho/di/www/StopTransServletTest.java. Found 2017. Was expecting 2018

:heavy_exclamation_mark: Copyright year is not the current year on ui/src/main/java/org/pentaho/di/ui/spoon/trans/TransGraph.java. Found 2017. Was expecting 2018

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd clean install && mvn -B -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd site

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui,engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  assemblies/static/src/main/resources/ui/trans-toolbar.xul
  engine/src/it/java/org/pentaho/di/trans/safestop/SafeStopTest.java
  engine/src/it/resources/safe-stop-gen-rows.ktr
  engine/src/main/java/org/pentaho/di/trans/Trans.java
  engine/src/main/java/org/pentaho/di/trans/step/BaseStep.java
  engine/src/main/java/org/pentaho/di/trans/step/StepInterface.java
  engine/src/main/java/org/pentaho/di/trans/steps/script/ScriptDummy.java
  engine/src/main/java/org/pentaho/di/trans/steps/scriptvalues_mod/ScriptValuesModDummy.java
  engine/src/main/java/org/pentaho/di/trans/streaming/common/BaseStreamStep.java
  engine/src/main/java/org/pentaho/di/www/StopTransServlet.java
  engine/src/test/java/org/pentaho/di/www/StopTransServletTest.java
  ui/src/main/java/org/pentaho/di/ui/spoon/trans/TransGraph.java
  ui/src/main/resources/org/pentaho/di/ui/spoon/messages/messages_en_US.properties

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: <0.1% (click to expand)
org.pentaho.di.job.entries.ftpsget.JobEntryFTPSGet

Branch Change: -0.5% :small_red_triangle_down:
Complexity Change: -0.6% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.step.BaseStep

Branch Change: -1% :small_red_triangle_down:
Complexity Change: -0.5% :small_red_triangle_down:
Instruction Change: -0.4% :small_red_triangle_down:
Line Change: -0.6% :small_red_triangle_down:
Method Change: -0.7% :small_red_triangle_down:

org.pentaho.di.trans.step.StepStatus

Branch Change: -3.3% :small_red_triangle_down:
Complexity Change: -1.6% :small_red_triangle_down:
Instruction Change: -1.4% :small_red_triangle_down:

org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Branch Change: -1.2% :small_red_triangle_down:
Complexity Change: -0.7% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change: -1.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.streaming.common.BaseStreamStep

Complexity Change: -0.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:
Line Change: -0.1% :small_red_triangle_down:
Method Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.Trans

Branch Change: -0.1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:
Method Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceupdate.SalesforceUpdateMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.ui.spoon.trans.TransGraph

Instruction Change: -0.1% :small_red_triangle_down:

:new: org.pentaho.di.ui.spoon.trans.TransGraph.13.new SelectionAdapter() {...}

Coverage: 0% :exclamation:

Note: The list of offending coverage changes extends beyond the presented results and was truncated to prevent reaching the comment size limit.

@pentaho/ackbar ready for review


clang is not supported?

When I try to use ctpg with clang13, clang fails to build.
It works correctly in gcc11.
Is clang not supported?
include/ctpg.hpp:1466:18: error: function 'create_regex_parser<ctpg::regex::dfa_size_analyzer>' with deduced return type cannot be used before it is defined
        auto p = create_regex_parser(a);
                 ^
include/ctpg.hpp:1460:20: note: 'create_regex_parser<ctpg::regex::dfa_size_analyzer>' declared here
    constexpr auto create_regex_parser(Builder& b);
                   ^
include/ctpg.hpp:1463:24: error: no return statement in constexpr function
    constexpr size32_t analyze_dfa_size(const char (&pattern)[N])
                       ^
include/ctpg.hpp:1612:25: error: function 'create_regex_parser<ctpg::regex::dfa_size_analyzer>' with deduced return type cannot be used before it is defined
        auto p = regex::create_regex_parser(a);
                        ^
include/ctpg.hpp:1460:20: note: 'create_regex_parser<ctpg::regex::dfa_size_analyzer>' declared here
    constexpr auto create_regex_parser(Builder& b);
                   ^
include/ctpg.hpp:1641:29: error: function 'create_regex_parser<ctpg::regex::dfa_size_analyzer>' with deduced return type cannot be used before it is defined
            auto p = regex::create_regex_parser(a);
                            ^
include/ctpg.hpp:1460:20: note: 'create_regex_parser<ctpg::regex::dfa_size_analyzer>' declared here
    constexpr auto create_regex_parser(Builder& b);
                   ^
include/ctpg.hpp:831:36: error: in-class initializer for static data member is not a constant expression
    static const size_t dfa_size = regex::analyze_dfa_size(Pattern);
                                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Unfortuanately not yet. But this is high on my priority list so stay tuned.

Thank you for quick response!
I'm waiting for it.

I have some bad news. Unfortunately it is a much bigger issue than I thought.
After the errors you reported, clang seems to have a problem to compile internal regex parser for ctpg lexer.
The regex parser is written in ctpg itself (how cool is that!) and this somehow breaks clang, not sure why.

Ok, it turns out that increasing -fconstexpr-steps solves the issue. The error however did not suggest this solution. It complained about static const class member being initialized by a non-const.

Ok. I think #17 solved it. Due to massive compilation time optimization clang now does not have any issues with examples.
Keep in mind however, that the clang bug still exists, so when grammar gets too complicated you probably won't get an apropriate message about constexpr calculations exceeding a limit, but a weird error instead.
I'll try to prepare a simple code snipped and raise an issue for clang.


rename a file

deployment-batch.md
Just a quick thing - to rename the file to "batch-deployment".

fixed.


Unable to add users with API

Describe the bug
Whenever I try to use the API to create new users, I receive an error:
{
    "error": "null value in column \"role_id\" of relation \"users\" violates not-null constraint"
}

To Reproduce
Steps to reproduce the behavior:

Send POST api request to /api/users
Include a proper payload in the body:

{
    "email"<EMAIL_ADDRESS>    "first_name": "John",
    "last_name": "Smith",
    "role_id": "80"
}

Receive error

Expected behavior
A new user is created, ideally onInsert Triggers are fired
Screenshots

Just to be clear, the same error is experienced with integer values and string values for role_id:

I think this is not possible ar the moment.
This link give a first explanation:
[https://github.com/saltcorn/saltcorn/blob/master/packages%2Fserver%2Froutes%2Fapi.js]

Ah. Thank you. Yes, that does seem to be what that says.


ToolTip hides when you try to use the slider.or ToolTip hides when clicked anywhere on the page.

Reproduction link
https://kje2qh--run.stackblitz.io
Steps to reproduce
1- Use <nz-slider [nzTooltipVisible]="'always'">
2- click anywhere near the tooltip. or try to click/use/drag the slider.
optional:
Go to this documentation page ! and scroll to "Control visibility of Tooltip" .
What is expected?
the tooltip shouldn't be hidden when clicked near it.
The tooltip shouldn't be hidden when the slider is dragged.
What is actually happening?
The Tooltip gets hidden every time you click near the slider, or try to use/drag the slider button.

Environment
Info

ng-zorro-antd
11.2.0

Browser
Opera 73

@vthinkxie the issue isn't resolved . Can you please re open the issue ?
Please find the .gif attached to the comment with the reported issue.


chore: bdd-sbhg-1586220809 to 0.0.1

chore: Promote bdd-sbhg-1586220809 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Promote spi/remote-secret from stage to prod

https://github.com/redhat-appstudio/service-provider-integration-operator/pull/644
https://github.com/redhat-appstudio/service-provider-integration-operator/pull/655
https://github.com/redhat-appstudio/remote-secret/pull/51
https://github.com/redhat-appstudio/remote-secret/pull/50
https://github.com/redhat-appstudio/remote-secret/pull/55

/retest


auto-refresh option if the user is using GM or TM

Pull from wchill fork.
Adding an auto-refresh option to the options to allow users to auto-refresh the page to 'fix' the memory leak without a third-party extension. Default time is 30 minutes. This defaults to 'enabled' for users of GM/TM, and defaults to 'disabled' for copy/paste scripts, as well as not showing the checkbox to enable, as refreshing the page would wipe their script.

This has a lot of unrelated commits, won't be merged at current state.
Do not change the version.

I will squash and repull, I forgot to do that, my fault.


MountVolume.SetUp failed for volume "cert" : secret "webhook-server-cert" not found

when I execute command, see below error, want to know where is the "webhook-server-cert"?
kubectl  apply -f https://raw.githubusercontent.com/rancher/opni/main/deploy/manifests/10_operator.yaml
MountVolume.SetUp failed for volume "cert" : secret "webhook-server-cert" not found

The cert secret should be created by Cert Manager, and this error should resolve after a short wait.  Is cert-manager installed in your k8s environment?
You can install it with a command like the following:
kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.5.3/cert-manager.yaml

@dbason it works for me now, thanks a lot


/home/runner/go/bin/staticcheck: No such file or directory

Hi folks, given this Actions step:
    - name: Run Staticcheck
      uses<EMAIL_ADDRESS>      with:
        version: 2023.1.5
        install-go: false

My job produces:
Run<EMAIL_ADDRESS>Run actions/cache@v3
Cache not found for input keys: staticcheck-Linux--3166c0793d31ad4de97784f1bba57d497ec[58](https://github.com/gebn/tflcycles_exporter/actions/runs/5957462012/job/16160160346#step:4:61)1bc, staticcheck-Linux--
Run export STATICCHECK_CACHE="/home/runner/work/_temp/staticcheck"
go: downloading honnef.co/go/tools v0.4.5
go: downloading golang.org/x/tools v0.9.4-0.20230[60](https://github.com/gebn/tflcycles_exporter/actions/runs/5957462012/job/16160160346#step:4:63)1214343-86c93e8732cc
go: downloading golang.org/x/exp/typeparams v0.0.0-20221208152030-732eee02a75a
go: downloading golang.org/x/sys v0.8.0
go: downloading github.com/BurntSushi/toml v1.2.1
go: downloading golang.org/x/mod v0.10.0
/home/runner/work/_temp/54b11b8f-c246-4f6a-b5d2-9b7211[62](https://github.com/gebn/tflcycles_exporter/actions/runs/5957462012/job/16160160346#step:4:65)39b0.sh: line 12: /home/runner/go/bin/staticcheck: No such file or directory
Error: Process completed with exit code 127.

I've tried manually go installing<EMAIL_ADDRESS>which works normally.
The full CI config can be found here.
What am I doing wrong? Happy to contribute a docs improvement to stop others falling into the same trap.

My hypothesis is that it's caused by you setting GOOS and GOARCH. That'll affect the building of the staticcheck binary; the CI runner is Linux on x86, and it won't be able to run binaries built for ARM, or Windows.

Thanks @dominikh! Adding if: env.GOOS == 'linux' && env.GOARCH == 'amd64' to the step has fixed it. I'm surprised the error was "file not found" rather than something like "cannot execute binary file: Exec format error".


Download the latest version of chromedriver

With #10 done, the next step is to use the browser version info to fetch the correct LATEST_RELEASE_<version> file.

With #10 done, the next step is to use the browser version info to fetch the correct LATEST_RELEASE_<version> file.

Now that #13 is done, the next step is to use the chromedriver version info to build the URL where the driver can be downloaded.

Now that #13 is done, the next step is to use the chromedriver version info to build the URL where the driver can be downloaded.

Done with #14

Done with #14


Add a file to GIN containing the size of each atlas

It would be helpful to have a file in the GIN repository containing the sizes of each atlas. This file could be queried to get the total download size when necessary.

https://github.com/brainglobe/bg-atlasapi/issues/121#issuecomment-1770962778 for reference

These are the sizes of the current atlases. Would need to be double checked if we're going to use it as ground truth.
atlas_file_size.csv
This could also be useful for #170


Azure job store should retry on server busy errors

We got ServerBusy error during a test run. Probably in the stats aggregator thread/process.
http://jenkins.cgcloud.info/job/toil-pull-requests/885/testReport/junit/src.toil.test.sort.sortTest/SortTest/testAzureSingle/

this is a case where a retry is necessary


make setting of title optional since current Firefox Inspector might not put one in the saved har file

Some time prior to Firefox 67.0.4 [currently using 68.0.1 (64-bit)], using the Inspector Network pane to record a session and save it as a HAR file stopped including a "title" element in the "pages" section.  Make setting of title in the haralyzer data first check for existence of the "title" item before trying to set it to avert a "KeyError: 'title'" failure.

Coverage increased (+0.007%) to 97.701% when pulling aa92308ec80b1baf29392e1e275b979bfd08886e on pckizer:master into 5ef38b8cfc044d2dfeacf2dd4d1efb810228309d on mrname:master.

Coverage increased (+0.007%) to 97.701% when pulling aa92308ec80b1baf29392e1e275b979bfd08886e on pckizer:master into 5ef38b8cfc044d2dfeacf2dd4d1efb810228309d on mrname:master.


Server shuts down when using / hd movehere

Let me explain briefly,
I have a survival server, which has 4 worlds:

Survival
Nether
Means
End

Nether, Resources, and End are worlds that restart every 7 days. These worlds, it has a hologram in the lobby, and every reboot I have to move it to the new lobby, when using / hd movehere , the server breaks, a lot of errors start jumping, and after that ... it goes off.
When I turn it on again, and use the same command, it works perfectly.
By the way, a suggestion: It would be nice if the plugin supports JSON format for announcements.

Doesn't seem to be related to this plugin. An error with HolographicDisplays instead?
Also, without any kind of exception stacktraces I'm not able to help.

By the way, a suggestion: It would be nice if the plugin supports JSON format for announcements.

Please elaborate.

Hahaha it's true, forgive me. It was that I was going to report errors, and everything got mixed up.
Forgive me, it was my mistake.
I wanted to make the suggestion here, since I didn't know where to do it.
With JSON Format / Text, I mean this:
["", {"text": "Hello, i'am"}, {"text": "JSON", "clickEvent": {"action": "open_url", "value": "https: // github .com / axelrindle / Broadcaster-Plugin / issues / 20 "}}, {" text ":" text "}]
https://minecraft.tools/en/json_text.php?json=Hello%2C i%26%2339%3Bam <a data-openurl%3D"https%3A%2F%2Fgithub.com%2Faxelrindle%2FBroadcaster-Plugin%2Fissues%2F20" class%3D"openurl" href%3D"https%3A%2F%2Fgithub.com%2Faxelrindle%2FBroadcaster-Plugin%2Fissues%2F20">JSON <%2Fa>text%26nbsp%3B

Interesting feature. Will definitely put this on my TODO list.
Thanks for the suggestion :+1:


correctly set model_name of subclasses of non-abstract resources

The _model_name of the superclass was being carried over its subclass (and overriding its _model_name) if the superclass wasn't abstract (as is the case with STI classes).

Thanks!


added reqCallback to use this callback to edit request before sending

Coverage decreased (-0.9%) to 99.145% when pulling c970e5e5ece1d09bb79712c1e3395edf95c455de on RavilKalimullin:master into 528ad7109fa55bdde8055dd035bb16140a29c336 on Rob--W:master.

What's the purpose of this?

To edit request before sending

Use case we needed in our project was to change values of some headers (not to remove or add, but to change it).

Thanks for the explanation.
I have just pushed a commit with tested functionality that you can use for the same purpose: https://github.com/Rob--W/cors-anywhere/commit/9f1af8243463ab71b63b889fff5606bd908f36cc
That should address the needs from this PR, so I'll close it.


aspect ratio 16:9 preview size and picture coming different.

When I am using aspect ratio 16:9, picture size coming bigger that preview size, getting extra bottom area but 4:3 is coming fine.

#20


EVOLVE_POKEMON request sent for every Pokémon at every tick

Since I'm using it, I noticed the bot was really slow but blamed this on his "human" behavior.
Out of curiosity, I thought running it in debug would be fun and noticed something really strange. Looks like the bot is sending an EVOLVE_POKEMON request for every Pokémon at every tick (when using tasks, maybe this was the case even before using tasks).
I tried to disable the EvolveAll task and now the bot is running way faster.
Expected Behavior
I don't think trying to evolve Pokémon involves sending an EVOLVE_POKEMON request for each and every Pokémon.
Maybe there is another way of knowing if a particular Pokémon can be evolved ?
Actual Behavior
There's an EVOLVE_POKEMON request sent for every Pokémon at every tick. That's time consuming and probably explains why the bot is so slow.
Steps to Reproduce

Enable the EvolveAll task in the configuration file.
Enable debug mode.
Notice all the EVOLVE_POKEMON requests made at each bot tick.

Other Information
OS: Arch Linux x86_64 (kernel 4.6.4-1)
Git Commit: b0a7b7cc4ffb5d23d671640965bad7b5446b2409

I guess evolve should trigger at start if opted in and only when candies are received (when pokemon is caught/transfered) and only for the evolution chain the candy is for


Sockeye failure with MXNet

Description
Install sockeye and run python setup.py test.
Change line in requirements.txt and requirements.gpu-cu100.txt and change mxnet version to nightly after commit at or after 09202f7f261954383aa387144524d38f83f18d06.
Run the following from inside sockeye directory.
python3 setup.py test

@anirudh2290 thanks for the issue.
Could you help to take a quick try for the fix of #15298 ?

Hi @anirudh2290 @ptrendx
I m still not able to reproduce the crash. My steps are below, could you help point out what's wrong?
Machine: AWS Deeplearning Base AMI, P3.8xLarge, Ubuntu 16.05
MXNet:
pip3 list | grep mxnet
mxnet-cu100mkl      1.5.0b20190621

Sockeye:
sudo pip3 install sockeye --no-deps

changed requirements
git diff
diff --git a/setup.py b/setup.py
index ffa2a7b..4d0741d 100644
--- a/setup.py
+++ b/setup.py
@@ -116,7 +116,7 @@ args = dict(

     extras_require={
         'optional': ['mxboard', 'matplotlib'],
-        'dev': get_requirements(os.path.join('requirements', 'requirements.dev.txt'))
+        'dev': get_requirements(os.path.join('requirements', 'requirements.gpu-cu100.txt'))
     },

run:
python3 setup.py test -r requirements/requirements.gpu-cu100.txt

result:
sockeye/output_handler.py                          139     36    74%
sockeye/prepare_data.py                             39      1    97%
sockeye/rerank.py                                   59     25    58%
sockeye/rnn.py                                     217      2    99%
sockeye/rnn_attention.py                           221      7    97%
sockeye/score.py                                    53      3    94%
sockeye/scoring.py                                 110      6    95%
sockeye/train.py                                   379     90    76%
sockeye/training.py                                682    180    74%
sockeye/transformer.py                             130      4    97%
sockeye/translate.py                               112     13    88%
sockeye/utils.py                                   483    151    69%
sockeye/vocab.py                                   137     25    82%
--------------------------------------------------------------------
TOTAL                                             8935   1363    85%

================================================== 542 passed in 39.93 seconds ===================================================

did you modify the mxnet version in requirements file ?

@pengzhao-intel @roywei I am currently building with @ZhennanQin and will try it out.

With the PR : #15298 also it segfaults and core dumps.

Thanks, we are trying to reproduce the crash (we can't reproduce till now).

@pengzhao-intel were you able to reproduce. Did you make sure you modified requirements file ?

I was able to reproduce the failure at test_constraints_int.py and test_seq_copy_int.py
https://github.com/awslabs/sockeye/tree/master/test/integration
@fhieber could you help take a look and convert this to a MXNet unit test?

@anirudh2290 yes, we can reproduce the issue and WIP to fix it :)

Confirmed that this can be reproduced. Need more time to investigate.

@mxnet-label-bot add [Build, Bug]

https://github.com/apache/incubator-mxnet/pull/15298 can fix sockeye failure on my machine. @anirudh2290 @roywei Please have a try.

Hi @ZhennanQin, could you give a small explanation of the issue and the fix? I see 2 changes in that PR - one related to converting older models and 1 that looks like no-op (moving from arrays to arrays_with_in_out). Which one fixes the segfault?

@ptrendx They worked together to fix the segfault. moving from arrays to arrays_with_in_out is a MKLDNN backend specific fix, to address https://github.com/apache/incubator-mxnet/issues/15281. Sockeye will also have problem without this fix. But sockeye have more problems, which is about the legacy op state. I've explained the reason here: https://github.com/apache/incubator-mxnet/pull/15298


cooldown description

Hi,
The cooldown definition is unclear. Which of the below scenario occurs?
Is it recording metrics during the cool down? So if the cool down is 10mins and the duration is 10min is the min time between scale outs 10mins or 20mins? Does it give the system the 10mins to cool down and then start to assess if it meets the rule to require another scale out (begins the duration) or does it immediately scale out?_
Thanks,

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

ID: 5b555a28-bc6e-6234-eae1-56f83b073c1b
Version Independent ID: 7dc075c1-3912-d119-5564-1acb5c0ea459
Content: Understand autoscale settings in Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/autoscale/autoscale-understanding-settings.md
Service: azure-monitor
Sub-service: autoscale
GitHub Login: @EdB-MSFT
Microsoft Alias: edbaynash

@olivierragain
Thanks for your feedback! We will investigate and update as appropriate.

@olivierragain The cooldown period in the context of scaling typically refers to a period of time during which further scaling actions are temporarily suspended after a previous scaling action has occurred. It is intended to prevent rapid and potentially disruptive changes to the system by allowing it some time to stabilize after a scaling event.
Let's clarify with an example:
Suppose you have an auto-scaling rule that triggers a scale-out event when some metric crosses a certain threshold. Additionally, you have a cooldown period of 10 minutes.
If the cooldown is set to 10 minutes and a scaling event occurs, the system will wait for 10 minutes before it considers triggering another scaling event based on the same rule.
During this cooldown period, the system typically does not actively assess whether it should scale out again. It gives the system time to stabilize and ensures that it doesn't make additional scaling decisions based on potentially fluctuating metrics immediately after a previous action.
So, in your example:
If the cooldown is 10 minutes and the duration is also 10 minutes, the minimum time between scale-outs would be 10 minutes. The system waits for the cooldown period before it starts assessing whether it should scale out again based on the rule.
It does not immediately scale out after the cooldown period ends; instead, it starts evaluating the conditions to see if another scaling event is warranted.
This cooldown mechanism helps to avoid unnecessary or overly aggressive scaling, providing a more stable and predictable behavior for the system.

@olivierragain The cooldown period is the amount of time that Autoscale waits after a scale operation before scaling again. For example, if cooldown = "PT10M", Autoscale doesn't attempt to scale again for another 10 minutes. The cooldown is to allow the metrics to stabilize after the addition or removal of instances. During the cooldown period, Autoscale does not record any metrics. Therefore, if the cooldown is 10 minutes and the duration is 10 minutes, the minimum time between scale-outs is 20 minutes. Autoscale waits for the cooldown period to end before it starts to assess if it meets the rule to require another scale-out. It does not immediately scale out. I hope this helps! Let me know if you have any other questions.

Thanks for the clarification. It would be great if this made it into the documentation because this is one of the question on the AZ-104 measureup practice test.
I would also point out, from my emails, that this also confuses MSFT people as I got both answers. I am guessing that the one currently in the comment is the correct one.

Assigning to content author @EdB-MSFT for updating the article.

The statement "During the cooldown period, Autoscale does not record any metrics. Therefore, if the cooldown is 10 minutes and the duration is 10 minutes, the minimum time between scale-outs is 20 minutes." is not 100% accurate.  Autoscale does record metrics, however there are no scale events during that time.
#please-close

So, can Autoscale happen every 10 minutes or every 20 minutes in the example provided?


Compatibility with podman

Hi, this is rather a question or a feature request.
Are there plans to be podman compliant too? dockerode basically works with podman, except the port exposing of spawned containers. While using docker the containers have their ports open, in podman they don't (when creating using dockerode).
Best

Interesting do you any more details?

@apocas Sure. Let me provide some additional Information. I was using dockerode for quite a long time in a JS + docker-based web application to create and interact with containers. I basically used dockerode to do things like create, start, stop, delete containers, but also to expose ports (so that docker/podman auto-allocate the port on the host, thus dynamic bindings) and configure environment variables, volume mappings and such during container creation.
According to redhat, podman should be API compatible with docker, thus I tried creating containers via dockerode on a podman backend. I noticed that it works in general, except the issue, that no port is exposed on the created podman container. Thus it looks like some incompatibility at some point. Unfortunately I could not debug deeper. This might also be just one incompatibility with podman.

There are multiple projects using dockerode with podman, example: https://github.com/containers/podman-desktop/blob/main/package.json#L151
Not sure if this exact issue still exist nowadays :)

Also couldn't manage to enable gpu support with podman through the docker api, as it seems to not do anything with DeviceRequests.. anyone know how to enable gpu support through dockerode/docker api?


[AUTOPATCHER-CORE] Patched rust to address CVE-2023-22466 -

[AUTOPATCHER-CORE] Patched rust to address CVE-2023-22466
Upgrade pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=293599&view=results
AMD64 build -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=293688&view=results
ARM64 build -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=293689&view=results

Disputed: this CVE is against "tokio" which is used for Windows servers
https://microsoft.visualstudio.com/OS/_workitems/edit/42938366


[Sui] emit event when burn Movescription

Add a message when burn Movescription

Option<vector> as input parameters?

Option<vector> as input parameters?

yes

Maybe we need to give the burner an NFT receipt for the burn.


New version: DavidRios.Remindr version 2.1.2

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: Open in CodeFlow


[2263] adding versioning property to pipeline yaml configuration

Description
Adding data prepper version as part of the pipeline configuration file. This PR creates a new DataPrepperVersion model in the API that is used in the PipelinesDataFlowModel. Added support for validating the current version is compatible with the current version of data prepper. Updated the documentation.
Issues Resolved

resolves #2263

Check List

[x] New functionality includes testing.
[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #2292 (48832d7) into main (6284795) will increase coverage by 0.05%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main    #2292      +/-   ##
============================================
+ Coverage     93.86%   93.92%   +0.05%
- Complexity     1933     1961      +28
============================================
  Files           225      226       +1
  Lines          5415     5461      +46
  Branches        430      436       +6
============================================
+ Hits           5083     5129      +46
  Misses          224      224
  Partials        108      108

Impacted Files
Coverage Δ

...repper/model/configuration/DataPrepperVersion.java
100.00% <100.00%> (ø)

...er/model/configuration/PipelinesDataFlowModel.java
100.00% <100.00%> (ø)

.../opensearch/dataprepper/parser/PipelineParser.java
87.50% <100.00%> (+0.54%)
:arrow_up:

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

@dlvenable - one follow up. I just want to clarify. Should Data Prepper version 2.0  be comparable with 1.5? I think I missed this in the original issue and want to understand if we truly want to support this. Is the intention here to ease migration to the latest version?

@dlvenable - one follow up. I just want to clarify. Should Data Prepper version 2.0 be comparable with 1.5? I think I missed this in the original issue and want to understand if we truly want to support this. Is the intention here to ease migration to the latest version?

Yes, I think it should be compatible. In any major version we should have migration fields to help with migrations. So a pipeline created for 1.5 could be compatible for 2.0. But, not always. I think more importantly, a 3.0 pipeline should not run on 2.x.


CPU temperature sensor not working

Describe the issue
OpenHardwareMonitor is no longer reading the temperature sensor for my cpu (intel 9600k).
I did recently switch to the developer build of TTController in order to test the new ScheduleTrigger, but I also recently had to reinstall Windows 10 on my system. Either of these changes could have caused the issue.
As far as I can tell, my cpu is only supported in the latest alpha build of OpenHardwareMonitor. See here:  https://github.com/openhardwaremonitor/openhardwaremonitor/issues/1156
Unfortunately I lack the technical skills to recompile TTController with the alpha build of OpenHardwareMonitor.

We are using LibreHardwareMonitor which is a fork of OpenHardwareMonitor. It has support for Coffee Lake processors so that is not the issue.
Can you post output of Main Menu -> Debug -> Sensors and your configuration?
Also, which develop version did you download? Latest build on AppVeyor is for netcore3.0 port which should work but can have issues. Latest develop download is this. (I should start linking to specific builds rather than posting a link to the latest build)

Ah, roger that.
The netcore version didn't run for me at all, so I used develop-45-a3788fe. When I noticed the cpu sensors weren't working, I also tried develop-36-7e5f95b, which is the version where you added the ScheduleTrigger. The cpu sensor issue was also present in that build.
Just now I tested the latest release build and my cpu sensors are reading correctly with that one.
Sensors (develop-45-a3788fe):
Intel Core i5-9600K:
»        Load:
»                CPU Core #1 (/intelcpu/0/load/1): 8.3 %
»                CPU Core #2 (/intelcpu/0/load/2): 2.8 %
»                CPU Core #3 (/intelcpu/0/load/3): 11.1 %
»                CPU Core #4 (/intelcpu/0/load/4): 23.6 %
»                CPU Core #5 (/intelcpu/0/load/5): 4.2 %
»                CPU Core #6 (/intelcpu/0/load/6): 5.6 %
»                CPU Total (/intelcpu/0/load/0): 9.3 %
»        Temperature:
»                CPU Core #1 (/intelcpu/0/temperature/0): NaN °C
»                CPU Core #2 (/intelcpu/0/temperature/1): NaN °C
»                CPU Core #3 (/intelcpu/0/temperature/2): NaN °C
»                CPU Core #4 (/intelcpu/0/temperature/3): NaN °C
»                CPU Core #5 (/intelcpu/0/temperature/4): NaN °C
»                CPU Core #6 (/intelcpu/0/temperature/5): NaN °C
»                CPU Package (/intelcpu/0/temperature/6): NaN °C
»                CPU Core #1 Distance to TjMax (/intelcpu/0/temperature/7): NaN °C
»                CPU Core #2 Distance to TjMax (/intelcpu/0/temperature/8): NaN °C
»                CPU Core #3 Distance to TjMax (/intelcpu/0/temperature/9): NaN °C
»                CPU Core #4 Distance to TjMax (/intelcpu/0/temperature/10): NaN °C
»                CPU Core #5 Distance to TjMax (/intelcpu/0/temperature/11): NaN °C
»                CPU Core #6 Distance to TjMax (/intelcpu/0/temperature/12): NaN °C
»                Core Max (/intelcpu/0/temperature/13): NaN °C
»                Core Average (/intelcpu/0/temperature/14): NaN °C
»        Clock:
»                CPU Core #1 (/intelcpu/0/clock/1): NaN MHz
»                CPU Core #2 (/intelcpu/0/clock/2): NaN MHz
»                CPU Core #3 (/intelcpu/0/clock/3): NaN MHz
»                CPU Core #4 (/intelcpu/0/clock/4): NaN MHz
»                CPU Core #5 (/intelcpu/0/clock/5): NaN MHz
»                CPU Core #6 (/intelcpu/0/clock/6): NaN MHz
»
»  NVIDIA GeForce RTX 2080 Ti:
»        Temperature:
»                GPU Core (/nvidiagpu/0/temperature/0): 26.0 °C
»        Clock:
»                GPU Core (/nvidiagpu/0/clock/0): 300 MHz
»                GPU Memory (/nvidiagpu/0/clock/1): 405 MHz
»                GPU Shader (/nvidiagpu/0/clock/2): 0 MHz
»        Load:
»                GPU Core (/nvidiagpu/0/load/0): 0.0 %
»                GPU Memory Controller (/nvidiagpu/0/load/1): 7.0 %
»                GPU Video Engine (/nvidiagpu/0/load/2): 0.0 %
»                GPU Memory (/nvidiagpu/0/load/3): 7.1 %
»        SmallData:
»                GPU Memory Total (/nvidiagpu/0/smalldata/3): 11264.0 MB
»                GPU Memory Used (/nvidiagpu/0/smalldata/2): 802.4 MB
»                GPU Memory Free (/nvidiagpu/0/smalldata/1): 10461.6 MB
»
»  Samsung SSD 860 EVO M.2 500GB:
»        Temperature:
»                Temperature (/hdd/0/temperature/0): 30.0 °C
»        Data:
»                Total Bytes Written (/hdd/0/data/0): 5329 GB
»        Load:
»                Used Space (/hdd/0/load/0): 63.3 %
»
»  TOSHIBA MQ01ABC150:
»        Temperature:
»                Temperature (/hdd/1/temperature/0): 24.0 °C
»        Load:
»                Used Space (/hdd/1/load/0): 24.7 %
Config:
{
"Profiles": [
{
"Name": "Side",
"Guid": "9365b812-b40d-4ae8-84ba-7d8025e66f88",
"Ports": [
[9802, 8102, 1],
[9802, 8102, 2],
[9802, 8102, 3]
],
"SpeedControllers": [
{
"Type": "PwmSpeedController",
"Config": {
"CurvePoints": [
[30, 30],
[50, 50],
[70, 90],
[85, 100]
],
"Sensors": ["/intelcpu/0/temperature/6"],
"Trigger": {
"Type": "AlwaysTrigger"
}
}
}
	],
	"Effects": [
    {
      "Type": "FullColorEffect",
      "Config": {
        "Color": [0, 0, 0],
        "Trigger": {
          "Type": "ScheduleTrigger",
          "Config": {
            "Scope": "Day",
            "Schedule": [
              "00:00 -> 10:00",
              "20:00 -> 23:59"
            ],
          }
        }
      }
    },
    {
      "Type": "FullColorEffect",
      "Config": {
        "Color": [0, 255, 0],
        "Trigger": {
          "Type": "AlwaysTrigger"
        }
      }
    }
  ]
},
{
	"Name": "Top",
	"Guid": "7ae0f543-4a26-4001-a34c-f7208005b961",
	"Ports": [
		[9802, 8101, 1],
		[9802, 8101, 2],
		[9802, 8101, 3]
	],
	"SpeedControllers": [
		{
			"Type": "PwmSpeedController",
			"Config": {
				"CurvePoints": [
					[30, 30],
					[50, 75],
					[70, 100]
				],
				"Sensors": ["/intelcpu/0/temperature/6"],
				"Trigger": {
					"Type": "AlwaysTrigger"
				}
			}
		}

	],
	"Effects": [
    {
      "Type": "FullColorEffect",
      "Config": {
        "Color": [0, 0, 0],
        "Trigger": {
          "Type": "ScheduleTrigger",
          "Config": {
            "Scope": "Day",
            "Schedule": [
              "00:00 -> 10:00",
              "20:00 -> 23:59"
            ],
          }
        }
      }
    },
    {
      "Type": "FullColorEffect",
      "Config": {
        "Color": [0, 255, 0],
        "Trigger": {
          "Type": "AlwaysTrigger"
        }
      }
    }
  ]
},
{
	"Name": "Bottom",
	"Guid": "a853f557-20de-478e-84db-8053573e11f8",
	"Ports": [
		[9802, 8103, 1],
		[9802, 8103, 2],
		[9802, 8103, 3]
	],
	"SpeedControllers": [
		{
			"Type": "PwmSpeedController",
			"Config": {
				"CurvePoints": [
					[30, 30],
					[50, 50],
					[70, 90],
					[85, 100]
				],
				"Sensors": ["/nvidiagpu/0/temperature/0"],
				"Trigger": {
					"Type": "AlwaysTrigger"
				}
			}
		}

	],
	"Effects": [
    {
      "Type": "FullColorEffect",
      "Config": {
        "Color": [0, 0, 0],
        "Trigger": {
          "Type": "ScheduleTrigger",
          "Config": {
            "Scope": "Day",
            "Schedule": [
              "00:00 -> 10:00",
              "20:00 -> 23:59"
            ],
          }
        }
      }
    },
    {
      "Type": "FullColorEffect",
      "Config": {
        "Color": [0, 255, 0],
        "Trigger": {
          "Type": "AlwaysTrigger"
        }
      }
    }
  ]
}

]
}

Huh, ok somehow I did not notice that. There seems to be a bug in LibreHardwareMonitor.
For now you should be able to just copy the OpenHardwareMonitorLib.dll from the latest release and paste it to the develop build.

Beautiful, that fixed it. Thank you!!

This bug is now fixed in LibreHardwareMonitor.
You can try this develop build which has the updated LibreHardwareMonitor.
Thanks for reporting!

Ok, I tested the develop build you linked. LibreHardwareMonitor is indeed working again. But the build throws an error when I try to run in console:
12:15:43.8092: ================================================================
12:15:43.8292: Initializing...
12:15:44.0639: Loading plugin assembly: TTController.Plugin.BlinkEffect [<IP_ADDRESS>]
12:15:44.0639: Loading plugin assembly: TTController.Plugin.FlowEffect [<IP_ADDRESS>]
12:15:44.0639: Loading plugin assembly: TTController.Plugin.FullColorEffect [<IP_ADDRESS>]
12:15:44.0639: Loading plugin assembly: TTController.Plugin.PerLedColorEffect [<IP_ADDRESS>]
12:15:44.0639: Loading plugin assembly: TTController.Plugin.PingPongEffect [<IP_ADDRESS>]
12:15:44.0639: Loading plugin assembly: TTController.Plugin.PulseEffect [<IP_ADDRESS>]
12:15:44.0784: Loading plugin assembly: TTController.Plugin.RawEffect [<IP_ADDRESS>]
12:15:44.0784: Loading plugin assembly: TTController.Plugin.RazerConnectEffect [<IP_ADDRESS>]
12:15:44.0784: Loading plugin assembly: TTController.Plugin.RippleEffect [<IP_ADDRESS>]
12:15:44.0784: Loading plugin assembly: TTController.Plugin.SensorEffect [<IP_ADDRESS>]
12:15:44.0784: Loading plugin assembly: TTController.Plugin.SoundEffect [<IP_ADDRESS>]
12:15:44.0784: Loading plugin assembly: TTController.Plugin.SpectrumEffect [<IP_ADDRESS>]
12:15:44.0939: Loading plugin assembly: TTController.Plugin.WaveEffect [<IP_ADDRESS>]
12:15:44.0939: Loading plugin assembly: TTController.Plugin.CopySpeedController [<IP_ADDRESS>]
12:15:44.0939: Loading plugin assembly: TTController.Plugin.DpsgSpeedController [<IP_ADDRESS>]
12:15:44.0939: Loading plugin assembly: TTController.Plugin.PwmSpeedController [<IP_ADDRESS>]
12:15:44.0939: Loading plugin assembly: TTController.Plugin.StaticSpeedController [<IP_ADDRESS>]
12:15:44.0939: Loading plugin assembly: TTController.Plugin.AlwaysTrigger [<IP_ADDRESS>]
12:15:44.1089: Loading plugin assembly: TTController.Plugin.LogicTrigger [<IP_ADDRESS>]
12:15:44.1089: Loading plugin assembly: TTController.Plugin.OneTimeTrigger [<IP_ADDRESS>]
12:15:44.1089: Loading plugin assembly: TTController.Plugin.ProcessTrigger [<IP_ADDRESS>]
12:15:44.1089: Loading plugin assembly: TTController.Plugin.PulseTrigger [<IP_ADDRESS>]
12:15:44.1089: Loading plugin assembly: TTController.Plugin.ScheduleTrigger [<IP_ADDRESS>]
12:15:44.1089: Loading plugin assembly: TTController.Plugin.SensorTrigger [<IP_ADDRESS>]
12:15:44.1089: Loading plugin assembly: TTController.Plugin.DpsgController [<IP_ADDRESS>]
12:15:44.1089: Loading plugin assembly: TTController.Plugin.RiingController [<IP_ADDRESS>]
12:15:44.1089: Loading plugin assembly: TTController.Plugin.RiingPlusController [<IP_ADDRESS>]
12:15:44.1089: Loading plugin assembly: TTController.Plugin.RiingTrioController [<IP_ADDRESS>]
12:15:44.1240: Creating Config Manager...
12:15:44.3038: Loading config...
12:15:44.4638: Creating DataCache...
12:15:44.4688: Creating Sensor Manager...
12:15:44.4688: Initializing Open Hardware Monitor...
12:15:45.5340: Detected 57 sensors
12:15:45.5340: Creating Effect Manager...
12:15:45.5440: Creating Speed Controller Manager...
12:15:45.5440: Creating Device Manager...
12:15:45.6488: Searching for "Dpsg" controllers
12:15:45.9611: Searching for "Riing" controllers
12:15:45.9806: Searching for "Riing Plus" controllers
12:15:45.9989: Initialized "Riing Plus" controller [0x264A, 0x1FA5]
12:15:45.9989: Initialized "Riing Plus" controller [0x264A, 0x1FA7]
12:15:45.9989: Initialized "Riing Plus" controller [0x264A, 0x1FA6]
12:15:45.9989: Searching for "Riing Trio" controllers
12:15:46.0128: Adding effect: FullColorEffect [9365b812-b40d-4ae8-84ba-7d8025e66f88]
12:15:46.0128: Adding effect: FullColorEffect [9365b812-b40d-4ae8-84ba-7d8025e66f88]
12:15:46.0128: Adding speed controller: PwmSpeedController [9365b812-b40d-4ae8-84ba-7d8025e66f88]
Process is terminated due to StackOverflowException.

Yes, another bug in LibreHardwareMonitor...
Sorry about that, there was a big update there recently and it seems that it was not checked enough.
Just keep using the the previous develop build with release dll.
I'll reopen this and update when hopefully fixed.

No apology necessary, my friend! I'll stay ready to test the next build.

Ok, I've fixed the bug and done some LibreHardwareMonitor testing and I think it will be fine now.
Try this build: https://ci.appveyor.com/project/MoshiMoshi0/ttcontroller/builds/27713665/artifacts

Closing as the latest LibreHardwareMonitor seems to work fine.
Feel free to comment here if anything else breaks.


Replace react-window and its helper libraries with dicty-hooks

Currently useIntersectionObserver and useVirtualList are available, the latter of which could be used for displaying the plasmid catalog. Search result pages like the list of strains with a given phenotype could use useIntersectionObserver.
The strain catalog will need to use a hybrid of both due to its increased amount of data.

This will be addressed when #378 is implemented


WebSocketError 1006(PusherError) with load balancer

I am trying to run Slanger node with load balancer. Willing to use haproxy as my load balancer(tried Nginx as well but still the same error).
Slanger node worked fine  and connection was established successfully but after 60 to 100 sec it stopped working with the error below.
Pusher : Error : {"type":"WebSocketError","error":{"type":"PusherError","data":{"code":1006}}}
It works perfectly for 60 sec approx and then dies with the above error. In Slanger logs its showing unbind of connection with [[:error, #<EventMachine::WebSocket::HandshakeError: Not an upgrade request>]].
If I use it without Load balancer it works fine but with load balancer same error persists.
Here is my haproxy file
/etc/haproxy/haproxy.cfg file:-
 ulimit-n 12000
 maxconn 60000
 log <IP_ADDRESS> local2 debug
 tune.bufsize 102400

defaults
 mode http
 log global
 option httplog
 option  http-server-close
 option  dontlognull
 option  redispatch
 option  contstats
 retries 3
 backlog 10000
 timeout client          25s
 timeout connect          5s
 timeout server          25s
 timeout http-keep-alive  1s
 timeout http-request    15s
 timeout queue           30s
 timeout tarpit          60s
 default-server inter 3s rise 2 fall 2

frontend ws
 maxconn 50000
 bind *:8080 name ws
 default_backend ws

frontend api
 maxconn 50000
 bind *:4567 name api
 default_backend api

backend ws
 http-check expect rstatus 10[01]
 server sock1 <IP_ADDRESS>:8001 check

backend api
 server web1 <IP_ADDRESS>:4501 check

Finally solved it, Issue was with my haproxy configuration.
The reason for the issue was I didn't had the timeout tunnel        3600s in my haproxy.cfg. It is there in example file but I was using 1.4 haproxy and with that version timeout tunnel was getting errors so I commented it.
So to get haproxy with Slanger we need atleast 1.5-dev or 1.6. Haproxy Setup Guide
Comment from the blog:-timeout tunnel available in ALOHA 5.5 or HAProxy 1.5-dev10 and higher
@stevegraham if possibly we can add this thing to our example folder :)


Add decorator for Clock.create_trigger()

This PR adds the decorator @triggered to Clock. It schedules the given function through Clock.create_trigger(), the same way that @mainthread uses Clock.schedule_once(), but with the ability to set the timeout and interval parameters.
It simplifies the use of triggered events on regular methods, without complicating the code using dt, lambda, partial, etc. The decorated method can be called several times within the timeout, even with different arguments, but only the last one will be triggered.
It can be very helpful when in a complex system, you have several events or functions calling an expensive method with an updating parameter, but only the last one is needed.

Quoting from the docs in PR:

A new call to the function before the timeout will interrupt the previous call and restart the timeout, so only one call is executed during this timeout.

This seems inaccurate to me - calls to an already-scheduled trigger does not restart the timer, it will execute when the timeout has elapsed from the initial call. It doesn't seem like there is any code in the PR that does this.
It would be a nice feature to add, I've needed it from time to time, for example to keep a menu open for N seconds after the most recent interaction. It's trivial to implement of course, but it would be nice to have something like Clock.create_trigger(retrig=True) or a retriggered decorator

@tshirtman Sure! I'll commit the default timeout=0 right away to have it done. I will need some time to come with a proper test since I do not know well the test engine, but I'm on it.
About the @bionoid proposition, I have to say that I though that the timeout was indeed reset on retriggers, but I think it is a matter of another PR and discussion between main devs. If such behaviour is added to the create_trigger() functionality it will be trivial to add it to the decorator too.

I found no test cases for create_trigger() itself, so I added some along with the decorator function.
I couldn't figure it out how to deal with tests involving timeouts, such as triggering some callback twice inside or outside the timeout, but I hope it is enough for now.

Thank you!


TypeError: Cannot read property 'x' of undefined at BindableProperty.initialize

Problem since latest version. Steps to reproduce:
//page1.html
<template>
      ${msg}
</template>

//page1.js
import {bindable} from 'aurelia-framework';
export class Page1 {
  @bindable msg = 'Bindable message';
}

Gets error:
ERROR [app-router] TypeError: Cannot read property 'msg' of undefined
    at BindableProperty.initialize (http://localhost:9000/jspm_packages/github/aurelia/templating@0.15.0/aurelia-templating.js:2706:33)
    at new BehaviorInstance (http://localhost:9000/jspm_packages/github/aurelia/templating@0.15.0/aurelia-templating.js:2457:23)
    at HtmlBehaviorResource.create (http://localhost:9000/jspm_packages/github/aurelia/templating@0.15.0/aurelia-templating.js:3085:30)
    at http://localhost:9000/jspm_packages/github/aurelia/templating-router@0.16.0/router-view.js:44:49
    at f (http://localhost:9000/jspm_packages/npm/core-js@0.9.18/client/shim.min.js:1415:56)
    at http://localhost:9000/jspm_packages/npm/core-js@0.9.18/client/shim.min.js:1423:13
    at b.exports (http://localhost:9000/jspm_packages/npm/core-js@0.9.18/client/shim.min.js:453:24)
    at b.(anonymous function) (http://localhost:9000/jspm_packages/npm/core-js@0.9.18/client/shim.min.js:1625:11)
    at Number.f (http://localhost:9000/jspm_packages/npm/core-js@0.9.18/client/shim.min.js:1596:24)
    at q (http://localhost:9000/jspm_packages/npm/core-js@0.9.18/client/shim.min.js:1600:11)

Appears to be caused by:  https://github.com/aurelia/templating/blob/master/src/bindable-property.js#l133
Changing to:
  if (!!attributes) {

seems to fix things.

I have copied your code exactly into the navigation skeleton project. Then, in the welcome.html file Ihave used it like this:
<template>
  <require from ="page1"></require>

  <page1></page1>

</template>

Everything works perfectly. There are no errors. Is there some other piece of information you have neglected to provide about this? Is this the way you are using it?

<template>
      ${msg}
</template>

That is the full contents of my page1.html.  A single binding to the @bindable msg property in the page1.js file. This is a contrived example to show the bug.

possibly related to https://github.com/aurelia/templating/issues/152

In the latest skeleton nav - if you change welcome.html to make '@bindable heading' -
import {computedFrom, bindable} from 'aurelia-framework';

export class Welcome{
  @bindable heading = 'Welcome to the Aurelia Navigation App!';
  ...

Then it will break in the way I describe.

Ok, I can reproduce it with that. I'll investigate. Thanks!

Ok, it was a bug in templating-router. It's all fixed now. If you run jspm update you should get the latest patch. Version for templating-router would be 0.16.1 with the fix. Sorry about the regression.


Restrict Firewall Port on my Cloud Server to MSBot Server

Hi,
I opened a port on my cloud server to talk to MS Bot Framework.
Can I restrict incoming request to a given IP Address to avoid atacks / port scanner, etc ... ?
What IP address should I set ?

see my response on #1318

Responded on the related issue that @brandonh-msft linked. Closing this issue so we have a single thread.


java.lang.OutOfMemoryError: Java heap space error

The distribution of variants are:
76410
15354
13084
226854
17616
47908
6115
326934
3399
324668
55294
49259
268895
123123
889
35805
10275
2122

Some of these are combinations of VCFs, but the largest MAF is 326934 rows.  I am currently using a t3.medium instance which is 2CPU and 4GB mem.

👍 thanks for the report

Initial testing shows that for a MAF with 379772 records, the memory usage seen (on dashi-dev) was 37652044 bytes virtual memory (~37GB) and 6463572 bytes resident memory (~6.2G)

@sheridancbio @thomasyu888 is this issue okay to close for now since Tom will be increasing his node size or is there still work to do?

t3.medium node was insufficient for mskimpact maf
not sure if a success has happened yet and what size node was used.

Follow up question - did anyone attempt to run the annotator with the jvm argument to increase the heap size?

I just encountered this error with a mutation file that is 240 MB, and 226870 rows.   How do I increase the heap size?
I am now on a t3.xlarge machine.  4 cores and 16 GB ram.

Adding java -Xmx48g resolved this issue.

Prolly good to add this to the documentation somewhere


[Feature] Cache with Redis, Memcache etc

Hi all,
Will ballerina support caching mechanism with Redis, Memcache etc. ?
Thanks

We can support this as separate Ballerina libraries which can be pushed and shared via Ballerina Central.


Compiler & Version or Executable

Where is the hello_world.exe for chapter 1? You compile with gcc and give no instructions on how to get gcc or which version you’re using. I use VS, but I don’t think the executable would be very similar. I'm also wondering if there will be differences between CodeBlock gcc and Mingw gcc. I wouldn't have to compile it to follow the exercise if the executable you're using could be downloaded as advertised. After all, the focus should be on reversing; not jumping through hoops in a circus ring to set up a different compiling environment.

Hi @KenAhern. There are Code in Action videos for each chapter of this book that shows how to run the code files in them. I think you may be able to locate the helloworld.exe file by referring to this video here https://youtu.be/6SSX32BmMgI
Hope this helps!


Update version in workflow actions and enable 3.13

This PR changes the following:

Updates the CI workflow with newer action versions
Drops deadsnakes action in favor for action/setup-python's allow-prereleases (introduced in v4.6.0)
Enable python 3.13 tests, and add its classifier to pyproject.toml
Adds concurrency rule in workflow to prevent more than on workflow run for the same commit or commit hash (inspired in packaging.python.org)

Run


Merkle inputs

With a limited amount of memory in a ledger device, we cannot have more than some small number of inputs. In testing, a Nano S will only allow us to have 14 UTXOS in a transaction.
To support more UTXOs (an arbitrary number, so we're only limited by mass limit), use Merkle Trees.
Reference: https://www.youtube.com/watch?v=n6nEPaE7KZ8
Change in sign_tx APDU:

First APDU will receive the version, output length, input length and merkle root
For {0...input_length}: ask the client to give provide the input along with the merkle proof. Verify the merkle proof to legitimize the input.
Request approval from user to continue with signing
After all inputs are verified this way, For {0..input_length}: ask the client to give provide the input along with the merkle proof. This time, sign them then ask for the next input.

This can be deferred since the input limit looks to only apply to a Nano S.
A Nano SP and Nano X can take up to 128 inputs.


Max value not shown for all series

Checklist

[x] I updated the card to the latest version available
[x] I cleared the cache of my browser
[x] I verified that I'm really running the lastest version in my browser console
[x] I checked if there is another issue opened with the same problem

Describe the bug
When using extremas: max in combination with data_generator (?) the max value is not shown for all series
Version of the card
Version: 2.0.1
To Reproduce
This is the configuration I use:

type: custom:apexcharts-card
graph_span: 23h
header:
  show: true
  title: Nordpool
span:
  start: day
now:
  show: true
  color: 357DA7
yaxis:
  - decimals: 0
    align_to: 10
apex_config:
  stroke:
    curve: stepline
  markers:
    size: 4
    strokeWidth: 0
    hover:
      sizeOffset: 2
  grid:
    show: true
    strokeDashArray: 0
    position: back
    xaxis:
      lines:
        show: true
all_series_config:
  stroke_width: 3
  show:
    legend_value: false
    extremas: max
    offset_in_name: false
series:
  - entity: sensor.nordpool_kwh_se3_sek_2_10_0
    name: Today
    color: 357DA7
    data_generator: |
      return entity.attributes.raw_today.map((entry) => {
        return [new Date(entry.start), entry.value * 100];
      });
  - entity: sensor.nordpool_kwh_se3_sek_2_10_0
    name: Tomorrow
    color: DD4B39
    offset: +1d
    data_generator: |
      return entity.attributes.raw_tomorrow.map((entry) => {
        return [new Date(entry.start), entry.value * 100];
      });

Screenshots

Expected behavior
Max value shown on the blue "Today" curve just like on the red "Tomorrow" curve
Desktop (please complete the following information):

Browser [Chrome]
Version [103.0.5060.114]

Smartphone (please complete the following information):

Device: [iPhone 12]
OS: [iOS 15.5]
Browser [Safari]

Additional context
When using regular entities (i.e not data_generator ones) the max value is shown for all series.

I found a workaround for this now. If I set a dummy offset value of -0.1s on the first entity the max value shows up on both curves and the time stamps are still ok due to rounding I guess.

Just ran into this issue with a single series where no extrema values were displayed at all. I am using extremas: time in the series show options
Workaround for me was to add offset: +0.0000000000001s to the series and offset_in_name: false to the series show options.
Now this is not a solution, but a workaround and I would really appreciate it if this issue can be looked at so the workaround is no longer needed.


REFPLTB-1574: Don't call hostapd_cli when AP is down

https://jenkins.code.rdkcentral.com/job/github-triggered/13326/ started

https://jenkins.code.rdkcentral.com/job/build-component-rdk-next/46115/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/8261/ started

Smoke tests for ['build-rpi-broadband'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/108804/

Smoke tests for ['build-tur-bb'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/108805/


Flop/Memory Evaluation Code

Thanks for your contribution!
Could you also share FLOP/mem evaluation code about the transformer based model? It seems that there is not a common and standardlized measurement library for that.
Best

Hi, thanks for your questions.
FLOPs:
https://github.com/uncbiag/SimpleClick/blob/v1.0/notebooks/analyze_effiency.ipynb
Mem: https://github.com/uncbiag/SimpleClick/blob/4099621fcfa99f2cc8a4409ea61420e016ec7920/scripts/evaluate_model.py#L142


i can not run it coreactly

log error is
Material doesn't have a texture property '5f4d61696e546578' UnityEngine.Material:GetTexture(Int32) Es.InkPainter.InkCanvas:SetTexture() (at Assets/InkPainter/Script/Core/InkCanvas.cs:283) Es.InkPainter.InkCanvas:Awake() (at Assets/InkPainter/Script/Core/InkCanvas.cs:199)
my unity version is 5.5.2f1

It seems that the texture name set for InkCanvas is incorrect.
please refer the review of Asset Store and my blog post.
https://www.assetstore.unity3d.com/jp/#!/content/86210
http://esprog.hatenablog.com/entry/2017/04/12/231850

it is helpful, thanks


'eDistantObject/EDORemoteVariable.h' file not found

#import "AppFramework/Action/GREYActions.h"
^
/Users/yongjuwa/Desktop/cbdmobile/ios/../../shared/Earlgrey/AppFramework/Action/GREYActions.h:23:9: error: 'eDistantObject/EDORemoteVariable.h' file not found
#import <eDistantObject/EDORemoteVariable.h>
^
1 error generated.
:0: error: failed to emit precompiled header '/Users/yongjuwa/Library/Developer/Xcode/DerivedData/CBDMobile-gfssoqseupovomajrakqibbecrgu/Build/Intermediates.noindex/PrecompiledHeaders/EG2Header-swift_57OHYXJF0H8J-clang_219ISBKZ2L257.pch' for bridging header '/Users/yongjuwa/Desktop/cbdmobile/ios/CBDMobileUITests/EG2Header.h'
/Users/yongjuwa/Desktop/cbdmobile/ios/CBDMobileUITests/EG2Header.h:3:9: note: in file included from /Users/yongjuwa/Desktop/cbdmobile/ios/CBDMobileUITests/EG2Header.h:3:
#import "AppFramework/Action/GREYActions.h"
^
2 errors generated.

This is a bug that breaks setting up Earlgrey using this method https://github.com/google/EarlGrey/blob/earlgrey2/docs/setup.md. The problem here is that Earlgrey now is expecting Earlgrey setup via cocopods from the macros if statement. however if we are not using cocopods then our setup will fail with above error message. if you are not using cocopods, then workaround can be editing those files that gives error by commenting out the cocopods if statement and leave only the direct EDORemoteVariable.h import like below:
//#if COCOAPODS
//#import <eDistantObject/EDORemoteVariable.h>
//#else
#import "EDORemoteVariable.h"
//#endif  // COCOAPODS
and then you should be able to compile your project fine. Hopefully this gets fixed.


RFC: Bring graph store to llama index

Dear Jerry/llama_index community!
May I propose changes to bring scalable graph capabilities to llama_index?
I had been watching llama_index for some time (impressed by how it's well abstracted, evaluated, and maintained) and would like to contribute. As one working around the graph, I had been thinking of similar things done by William(#433) and Logan(#487), and your discussions(around the embedding search of KG) in the tread.

Due to the basic abstractions and PoC already designed and implemented, I could bring graph store on top of it, just like simple vector store v.s. other vector_stores. What do you think, please? If it's OK, I will prepare PR in this week, with the first graph_store implementation using NebulaGraph, the project I had been working on.

Also, in the future, I am willing to discuss/contribute more around:

support KG + Vector index, multiple indices query as llama query context
NebulaGraph loader on llama hub(kg to doc)
Support indexing existing external graph store(i.e. adding an knowledge graph as index, create embedding to its entities and relationships)
vector store as KG embedding

The motivation is there are some cases in which we already have KG built from different sources(not just some docs), we could build smart services making use the most of the KG and LLAMA(index), and maybe we could leverage the (multiple hops)graph query to enable some knowledge not limited to the chunks of documents by adding the extra context on top of what embedding-vector search based magic could push this work to.
Thanks!
BR//Wey

Dear @jerryjliu
I prepared an initial draft design that brings graph stores to the llama index to potentially leverage knowledge extracted during index creating && consuming existing external KGs.
The draft is on #2581 as it was started before the refactoring in 0.6.0, some of the rebase was not properly done, but the current design was put so as to be discussed, what do you think of this, please?
Thanks a lot!
BR//Wey

I posted a blog around this topic today: https://siwei.io/en/graph-enabled-llama-index/


Is there a way to access the header in the response?

I am making my request just fine, using TRON (w/Alamofire) and SwiftyJSON.  I get the response body and it is parsed into the response model class I made for it, all working great.  What I need to do now is to get some fields from the response HEADER.  Is there any way to do that?  Thanks for any help in advance.  (BTW, I have searched for the past 2 hours, stackoverflow, github, google, asked co-worker).  I'm stumped.

Well, you could make a plugin and attach it to request you wan't to get header from, however it would only work if header is needed separately from response.
If you need to parse both model and header together, than you need to create a custom response serializer. Response serializer is defined as a typealias:
typealias ResponseParser = (_ request: URLRequest?, _ response: HTTPURLResponse?, _ data: Data?, _ error: Error?) -> Result<Model>

You can see an example of response serializer implementation in SwiftyJSONDecodable, for example.

I am such a Noob, that I don't know how to do either of those options.  I think I do want the header separately from the response, but I don't know how to make a plugin.  I will go search for info on how to create a plugin.  Thanks for your help.

You can take a look at how currently available plugins are implemented - https://github.com/MLSDev/TRON/blob/master/Source/NetworkLoggerPlugin.swift
Or take a look at plugin ideas section in Docs - https://github.com/MLSDev/TRON/blob/master/Docs/PluginConcepts.md
Adding local plugin to your request is very simple, just call
request.plugins.append(YourPlugin())

As for custom response serializer, there is a dedicated doc for custom response serializers - https://github.com/MLSDev/TRON/blob/master/Docs/Response serializers.md
Hopefully this answers your question.

Ah, yes, thank you for that info.
On Sep 27, 2017, 9:26 AM -0500, Denys Telezhkin<EMAIL_ADDRESS>wrote:

You can take a look at how currently available plugins are implemented - https://github.com/MLSDev/TRON/blob/master/Source/NetworkLoggerPlugin.swift
Or take a look at plugin ideas section in Docs - https://github.com/MLSDev/TRON/blob/master/Docs/PluginConcepts.md
Adding local plugin to your request is very simple, just call
request.plugins.append(YourPlugin())
As for custom response serializer, there is a dedicated doc for custom response serializers - https://github.com/MLSDev/TRON/blob/master/Docs/Response serializers.md
Hopefully this answers your question.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


shortcodes: Add start parameter for youtube

Thanks for reviewing the PR!
Since communicating with contributors does not seem to be something that Hugo prioritizes in any capacity whatsoever, I will, sadly, have to make some guesses and try to piece together a picture of the current state of affairs and the reasoning behind some of the decisions.
Still, any corrections to my theory would be welcome!
I assume my PR got rejected, because, as stated in the guidelines,

Any non-trivial code change needs to update an open issue. A non-trivial code change without an issue reference with one of the labels bug or enhancement will not be merged.

and, I have to assume, the changes proposed in this PR were deemed to be non-trivial (probably should also have been labeled as enhancement) but had no referenced issue.
Looking at the issues, I seem to have found one that was already opened 11 months ago: #10520.
Moreover, it had received a PR on the exact same day: #10521, but just 3 days later it got rejected in favor of two even smaller PRs: #10575 & #10576. Which have been inactive ever since. (Aside from getting a label 3 months after the creation).
The reason behind this inactivity is, unfortunately, not something I can make an accurate guess on, but my best bet is that they are of a low priority, and hence have been ignored for nearly a year now.
Unfortunately, I am not familiar with the usual review process for such things in Hugo, so I have no clue on when any progress on those issues can be expected, whether it can be expected at all, what needs to happen for it to take place, and whether there is anything I can personally do to aid it in any way. So if anyone could clarify this to me, it would be very appreciated!
Thank you in advance!

Thanks for taking your time with the response, but I would still appreciate if I could hear back about the review process (to maybe get a hint of why such a trivial change takes months to approve review)?


Optimise tests

Tests are taking an excessively long time to run, especially when testing anything to do with managed policies.
See if there is a way to optimise this.

#65 went a significant way towards this, closing for now.

#65 went a significant way towards this, closing for now.


Let's dockerize the CLI!

We discussed having the CLI in a docker container.
Here are the Dockerfiles.
Disclaimer:

My laptop is an M1, so I had to create a linux-arm image. I never did multi-arch in docker before, so.. suggestions are welcomed!
We already identified potential issues with interactive prompts: asking for an email/otp token, and entering a master password may require you to run the container interactively. I wish to not address this in this MR
I tried to only copy the binary in the Dockerfile... and I got stuck with https://github.com/Dashlane/dashlane-cli/issues/198.  Building the binary and running it from the same image made it work

Please open an issue before opening a PR so we can frame and discuss the work needed. Thanks.


Can we have ACTIONABLE toast?

Is that possible to have some cations say (accept, reject), (undo) kinda actions for the toast

This issue is exactly the same as https://github.com/FezVrasta/snackbarjs/issues/19


Fixes #327. Disable pointer events on snackbar container

This just disables pointer events on the invisible snackbar container so clicks can pass through.

That's great. Thanks!


🐞 Bug - Circuit State Resets on Switching Between SubCircuits and Waiting after Constant Change

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
The state of a subcircuit is reset when you switch away to another subcircuit and then switch back. Also, by doing some zoom/pan fiddling, it can also reset.
Steps To Reproduce
Steps to reproduce are in text below, and also in the video below. Example project is linked.
Reproduction 1:

Create a project with multiple subcircuits (or try posted one)
Switch between subcircuits and see state lost

Reproduction 2:

Create a project with multiple subcircuits (or try posted one)
While on one of the subcircuits, change a constant value
~Zoom in and out and pan~ Wait a few seconds
See state lost on currently viewed subcircuit

https://github.com/CircuitVerse/CircuitVerse/assets/19422826/a5d555a0-0e6b-4fd0-ace8-effa84996db3
https://circuitverse.org/users/191705/projects/dflipfloptest-80dfc9a8-f1d4-4b4a-87ad-4f72ca4c8062
Expected Behavior
Expected behavior is that the state of a subcircuit is not reset between viewing different subcircuits, and also that it is not reset by waiting a few seconds ~zooming in and out and panning~ after changing a constant.
However, it may expected that if one of the dependent subcircuits changed, that the state of the subcircuit using it may be reset.
Screenshots
No response
Device Information [optional]
- OS: Arch Linux
- Browser: Firefox 121.0
- version: CircuitVerse Public Site on 2024-01-10

Additional context
No response
Are you working on this issue?
No

After messing with it some more, the scrolling may be a red herring. I think that even just waiting a few seconds after changing a constant, the state resets.

cc @Arnabdaz @Prerna-0202

If approved I interested to work on

I would like to work on this issue.

hi @nametable @tanmoysrt  can you assign this issue to  me

Just jumping in here to confirm this behavior, and that it also happens after updating inputs for certain circuits, with a random-seeming delay.
A reliable way that I can reproduce it on both Firefox and Chrome (on Windows) plus probably 5-6 of my students ran into it:
hw_isa.json

Load the attached circuit, and select the "Program Counter" sub-circuit.
Toggle the "Advance" input on the left to 1 and then back to 0, which updates the PC.
Wait a few seconds, and the address output will reset back to 0. It seems to do this no matter what other inputs to the circuit are doing.

I found similar resetting behavior with a few different sub-circuits here, but some were more stable than others. For example, the Register File and Register sub-circuits sometimes reset during my testing, but don't seem to be doing it now (unless I go to another tab and back, which is also bad but more tolerable). There may be some correlation with how long the browser tab has been running, although I'm not confident on that.
My guess might be that sequential sub-circuits are implicated somehow, but that's not a very educated guess. The circuit I have here builds up from a NOR-based D latch to almost a full CPU, and the Program Counter sub-circuit where the reset is the most reliable contains a Register which contains 16 D flip-flops which each contain 2 D latches, so there's a lot of nesting there...