Map.of(KVKVKV) #1608

Current coverage is 95.43% (diff: 26.82%)

Merging #1624 into master will decrease coverage by 0.73%

@@             master      #1624   diff @@
==========================================
  Files            89         89
  Lines         10889      10965    +76
  Methods           0          0
  Messages          0          0
  Branches       1830       1830
==========================================
- Hits          10472      10464     -8
- Misses          274        358    +84
  Partials        143        143

Powered by Codecov. Last update abe2a28...4068b31

reproduced:
[WARNING] /home/travis/build/javaslang/javaslang/javaslang/src/main/java/javaslang/collection/TreeMap.java:[151,40]
<K,V>of(java.util.Comparator<? super K>,java.lang.Object...) in javaslang.collection.TreeMap is potentially ambiguous with
<K,V>of(java.util.Comparator<? super K>,K,V,K,V,K,V,K,V,K,V,K,V,K,V,K,V,K,V,K,V) in javaslang.collection.TreeMap

I see. I tested it only in IntelliJ, which does not break the build on warnings. There are also other ambiguities:

Note: In this example my impl of the deprecated methods throws in order to double-check at runtime which method was really called.
Now we have three choices:

disable the build error on compiler warnings in the pom --> No.
don't ship this change with a minor release (e.g. 2.1.0) --> Don't want to do that because of safety.
remove the deprecated method(s) and break compatibility --> Maybe this :-/

remove the deprecated method(s) and break compatibility --> Maybe this :-/

maybe there is only one possibility

Please remove all of(Object...) and of(Comparator, Object...) methods. And I mean all!
If we break, then the right way. These methods are unsafe. Having them, even if deprecated, is a risk for our users.

If we break, then the right way.

OK, now all is clear for me.
I'll do the same for of(Entry...), of(Tuple2) and for all methods in all multimaps

@ruslansennov don't do that. what would be the minimal-invasive solution? just removing the ambiguous TreeMap.of(Comparator, Object...) method, right?

Yes, removing all factory methods with Object... argument and replacing with KVKV

Yes, removing all factory methods with Object... argument and replacing with KVKV

@ruslansennov I'm torn back and forth - but I think you are right.  Keeping them as @Deprecated would not prevent from using them. We need to remove the methods containing Object... args also from the Multimap*.Builder classes.

@ruslansennov, @danieldietrich, @valery1707, we should add these possibilities to the aliases also and provide a convenient way of extending it to more than 10 elements.
I suggest making merge a vararg, to allow comfortable concatenation :)

@paplorinc

I suggest making merge a vararg, to allow comfortable concatenation :)

It would blow up the API too much. For more than 10 args the ofEntries method is used (e.g. in conjunction with the Tuple(K, V) alias). It is evil enough that we now have all these *Map.of(KVKVKVKV...) methods.
Let's not throw in too much new API when we do not know how frequently it is used at all...
/cc @ruslansennov @valery1707

@danieldietrich please leave this PR unmerged for a while

please leave this PR unmerged for a while

Ok, will do!

public static <K, V> LinkedHashMap<K, V> ofEntries(Tuple2<? extends K, ? extends V> e1, Tuple2<? extends K, ? extends V> e2, Tuple2<? extends K, ? extends V> e3, Tuple2<? extends K, ? extends V> e4, Tuple2<? extends K, ? extends V> e5, Tuple2<? extends K, ? extends V> e6, Tuple2<? extends K, ? extends V> e7, Tuple2<? extends K, ? extends V> e8) {
    final HashMap<K, V> map = HashMap.ofEntries(e1, e2, e3, e4, e5, e6, e7, e8);
    final Queue<Tuple2<K, V>> list = Queue.of((Tuple2<K, V>) e1, (Tuple2<K, V>) e2, (Tuple2<K, V>) e3, (Tuple2<K, V>) e4, (Tuple2<K, V>) e5, (Tuple2<K, V>) e6, (Tuple2<K, V>) e7, (Tuple2<K, V>) e8);

hmm, these casts are ugly, but I could't come up with a better solution (except for chaining the methods, as I suggested earlier ... @ruslansennov, could you please react to that?)

Can't find your comment directly (do you removed it?)
@danieldietrich proposed to remove this methods, let's wait his comment

Sorry guys
I'm totally confused. I have to close this PR and open new #1664 with Map.of(KVKVKV) only.

@ruslansennov, what' the source of confusion?

@ruslansennov, what' the source of confusion?

Huge PR, a lot of comments, different opinions about ofEntries(Tuple/Entry/KV)...
I prefer small PRs which is more observable (this is only my personally sight)


Unable to start dhcpcd on all interfaces

"Unable to start dhcpcd on all interfaces" error shown while the pi starts. Its expected since one of the interfaces is configured statically in /etc/network/interfaces file.
Need to make sure this error is not shown.

Not important enough and time can be better spent on other issues.


Skia builds from stable release

Skia now builds from a specified stable release and not from master

Woo!


dfx: asset media type identification: fall back to check contents

Rather than immediately falling back to application/octet-stream, use the magic library or something like it to try to determine the media type.
The magic library requires a database, which would have to be distributed with dfx.  In earlier testing, without a database, it misidentified our new project .js files as application/x-perl.

Closing this as stale. @ericswanson-dfinity if this is still a thing to do, please re-file this as a Jira ticket.


Graph Querying

We're building a collective intelligence social network which needs to be able to scale to a large userbase and enable complex relational search and filtering queries across the entire database of posts, spaces, and users.
Would love to intergrate noosphere into the backend to contribute to private, group and public knowledge graphs.

Thank you for filing this feature request! This is something that would be really nice to have for a lot of reasons.
As discussed in Discord, Noosphere is a very young library. At this time the only thing it will offer is basic, file-system-like access to content in the graph.
Additionally, I mentioned:

You may be interested to look into some of the ground breaking work Fission is taking on in this area. In time, I suspect that Noosphere can benefit from their work to enable complex graph queries and conflict-free sync across peers with various access levels to data.

Fission (https://fission.codes/) has a nascent effort called Dialog that they first detailed here: https://fission.codes/blog/fission-reactor-dialog-first-look/. As Dialog matures, there may be opportunities for us to integrate it in part or in whole to Noosphere to enable rich graph querying.


Could not find any usage for restRequestError , if not used can be removed

line details : https://github.com/libuparayil/networking-huawei/blob/3fff4cf843d2ebcad0286ab9df4cda0755840794/networking_huawei/plugins/ml2/ac/driver.py#L631

done

ok


Errormessage does now include tagname

Describe the PR
Improved error message, when a markdown file is missing. It does now include the tag name.

Codecov Report

Merging #413 into master will not change coverage.
The diff coverage is 0%.

@@          Coverage Diff           @@
##           master    #413   +/-   ##
======================================
  Coverage    83.1%   83.1%
======================================
  Files           7       7
  Lines        1385    1385
======================================
  Hits         1151    1151
  Misses        135     135
  Partials       99      99

Impacted Files
Coverage Δ

parser.go
81.46% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@Nerzal it's a while sicen you started this PR , so in order to fix this I'm going to another PR for this.

thx @ubogdan


Refactor Part 1 Exercise 7 for Java and Kotlin

rework the description of the task
make the expected outcome more obvious
add hints for solving the exercise

Java part in main: fa8a7c5f967b34594065604002c0c01a0a0a85e5

Kotlin part in main: eff173cba6a8ae6a8899df57c6e8550a78c2591e


Proposed implementation

Suggested plan of attack:

Create new style instances for light and dark themes (depends on #1)
Use the RtfFormatter for output

I think this is a reasonable approach.


ODatepicker not shown as expected when used on a small modal

Overview of the problem
Oruga version: 0.9.0-pre.2
Vuejs version: 3.5.6
OS/Browser: do not depend of browser
Description
When using ODatepicker is does not shown correctly when used with a small modal, it gets covevered by the modal instead of been displayed over the modal.
Steps to reproduce
With this code it can be reproduced:
<template>

    <OModal v-model:active="isImportaRegistrosSIIActive"
            :cancelable="false"
            width="33rem"
    >

            Importa registros de CV desde SII

          <button class="delete" aria-label="close" @click="cierraModal" />

              <OField label="Período" class="column is-5">
                <ODatepicker v-model="periodo_rcv" type="month" :date-formatter="formatoPeriodo" expanded />
              </OField>
              <OField label="Tipo de registro" class="column is-5">
                <OSelect v-model="tipo_registro" expanded>
                  <option value="1">Compras</option>
                  <option value="2">Ventas</option>
                </OSelect>
              </OField>

            <OButton @click="cierraModal" class="mr-2">
              Cancelar
            </OButton>
            <OButton :disabled="en_proceso" variant="link" @click="importarRegistros">
              Importar
            </OButton>

    </OModal>

</template>

This code shows the following modal:

When doing a click over the comboboxs it is displayed over de modal, as can be seen here:

When doing click over the Datepicker, it is shown inside the modal, as can be seen here:

Expected behavior
It is espected that the Datepicker is shown over the modal, as is the case with the combobox.
Actual behavior
As shown on problem description.

With theme-bulma 0.4.2

It can maybe be related to #107.
However, have you tried adding teleport to the Datepicker component?
While adding teleport you might entcounter a bug with the datepicket teleport wrapper. If so, try to add this to you theme config:
datepicker: {
    dropdownClasses: {
          teleportClass: "datepicker",
     }
}

I have tryed your sugestion, but obtained the same results described on las comment of issue #373 on oruga-ui/oruga, unfortunately it looks that this is a more complex bug.

I have found that the z-index is in 20 for --bulma-dropdown-content-z whe displaying the datepicker, this value can be related to the problem of datepick.

I have found that the z-index is in 20 for --bulma-dropdown-content-z whe displaying the datepicker, this value can be related to the problem of datepick.
It seems that part of your issue lies in the structure. The overflow: visible you're applying should be placed on the container. Additionally, assign a higher z-index to the container as well. You can use the scrollbar that's being generated as a reference to identify which element is causing it and apply the appropriate styles.

      <OField label="Period" class="column is-5">
        <ODatepicker v-model="periodo_rcv" type="month" :date-formatter="formatPeriod" expanded />
      </OField>
      <OField label="Record Type" class="column is-5">
        <OSelect v-model="record_type" expanded>
          <option value="1">Purchases</option>
          <option value="2">Sales</option>
        </OSelect>
      </OField>

Check which element is generating the scrollbar and apply the necessary styles accordingly.

Remove the
 ...
  as it is not necessary and can cause confusion when arranging elements. As for why the component is not being displayed, it’s not related to z-index issues; it’s related to overflow. You can modify it by accessing the element’s classes using ::deep.
In the
...
, change overflow: auto to overflow: visible

In the
...
, for some reason, there's a conflict; the original looks like this:
.modal-card {
    display: flex;
    flex-direction: column;
    max-height: calc(100vh - var(--bulma-modal-card-spacing));
    overflow:  hidden;
    overflow-y: visible;
   }

In that declaration, the overflow-y should be visible, but as you can see, there’s still a scroll on the y-axis. However, if you remove the overflow: hidden, the component appears as follows:

I tried changing overflow: hidden to overflow-x: hidden, but for some reason, it causes conflicts and doesn't display correctly. It might be a good idea to test with other browsers to get more context.
   <OModal
                v-model:active="isImportaRegistrosSIIActive"
                :cancelable="false"
                width="33rem"
            >

                            Importa registros de CV desde SII

                        <button class="delete" aria-label="close" />

                            <OField label="Período" class="column is-5">
                                <ODatepicker type="month" expanded />
                            </OField>
                            <OField
                                label="Tipo de registro"
                                class="column is-5"
                            >
                                <OSelect expanded>
                                    <option value="1">Compras</option>
                                    <option value="2">Ventas</option>
                                </OSelect>
                            </OField>

                            <OButton class="mr-2"> Cancelar </OButton>
                            <OButton variant="link"> Importar </OButton>

            </OModal>

cc: @pflirae

@dylanson25 , thanks for your comments, just  question, what version of oruga an theme are you using ? since I have not been able to reproduce your results, I am usin orugo 0.9.0-pre.2 and theme-bulma 0.4.3.

Thanks @dylanson25, this is working great, it looks more a problem of oruga than a problem wiht the theme, it is a temporary fix that helps a lot.

Anyone have problems to get auth to SII using token? i got this {"id":"0","descripcion":"Data.TokenRecaptcha no puede estar vacio"} for last 5 days


version a couple more things, remove antd from PACKAGE since it's a

bowtie dependency

Codecov Report

Merging #95 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #95   +/-   ##
=======================================
  Coverage   67.47%   67.47%
=======================================
  Files          12       12
  Lines         658      658
=======================================
  Hits          444      444
  Misses        214      214

Impacted Files
Coverage Δ

bowtie/control.py
62.82% <100%> (ø)
:white_check_mark:

bowtie/visual.py
57.69% <100%> (ø)
:white_check_mark:

bowtie/_progress.py
71.42% <100%> (ø)
:white_check_mark:

Continue to review full report at Codecov.

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


✨ Raw results for dangerous workflow

Raw results for dangerous workflow
no breaking changes
Note: need to finalize the unit tests
Raw results for dangerous workflow

friendly ping

temporarily disabling build-proto pre-submit to merge, because it's failing on protbuf


add cloudfront CDN for retrieval service

add alias provider for us-east-1 because cloudfront requires the cert in us-east-1
create a retrieval.{app_domain} certificate in us-east-1
create cloudfront distribution for retrieval.{app_domain}

TODO:

[x] test cache behaviour
[x] switch retrieval.{app_domain} CNAME to point to cloudfront distribution

Currently cloudfront just passes request straight through to retrieval service and doesn't cache. Will need to modify headers in the service itself and test querystring cache busting.


babel-plugin-react-error-catcher

Nice work with redbox-react so far.  :)
Funny timing though.  This has been on my todo list for a while and literally the day after you create redbox-react, I start working on babel-plugin-react-error-catcher.  I had actually considered building on top of redbox-react for my use-cases but decided it would be easier to just make a Babel plugin.
No idea which direction you're headed with this repo, and I am definitely not trying to steal your thunder or anything!  But I figure I should probably let you know about what I've put together and maybe we could put forth some kind of collective effort and/or pull code from each other's repos or something.  :)

@timbur Great to see that many people are working on dev tools any making the dev experience better. I will clarify the goal of this project / repo in the Readme, but the short version on top of my head is:
What this project does
redbox-react is a UI React Component that renders an error and it's stack using StackFrames in a big red box. There might be customisations to the look of it coming in the future.
What this project does not
redbox-react will not catch errors for you. It does not dictate or care where in your code and how you catch an error.
Where will this project be useful?
Of course, feel free to use it how and where ever you like. One thing I'm personally trying to push is optional error catching in the react-hot-loader currently discussed here. redbox-react may be used to render an error caught  by the hot loader.

@timbur I just realised we might work together on this quite effectively. Do you think it would be possible to make your babel plugin configurable as to what error component it renders? If so, your babel plugin is the decorator to wrap a component's render function, but my (and any other people's) component actually decides how do render the error. Does that sound reasonable?
Please check out the discussion on react-hot-loader. I think this is exactly what @syranide is asking for there.

If so, your babel plugin is the decorator to wrap a component's render function, but my (and any other people's) component actually decides how do render the error. Does that sound reasonable?

Yeah that sounds perfect!  Thanks for the clarification on what redbox-react is for.  I definitely misunderstood the intent.  Our modules will work really well together.  :)

@davidpfahler Did you get a chance to try passing redbox-react to babel-plugin-react-error-catcher?  I actually haven't gotten around to it yet myself but it should work in theory, assuming redbox-react expects an error prop.  :)

@timbur I'm trying, but can't figure out why this example wouldn't work. Maybe you can take a moment and look into it. I'm pretty sure it's a minor mistake.

Awesome!  Works beautifully.
I did have some strange issue where my PC was refusing port 3000 for the socket connection, so I removed 'webpack-dev-server/client?http://localhost:3000' from webpack.config.js and it worked just fine.  It's most likely an issue with my firewall or something though and not your particular config.

For your interest, I'm planning to add props to the component that allow you to specify the behavior. For example, whether the component should fill the entire screen or just the space of the component it is replacing, etc.

Sounds good!  If there's anything I can do to make that easier for you to integrate, let me know.  The rendered function export should hopefully be all you need for any customization based on the target component.  Check same-size-reporter for reference if you haven't already.  :)


Fix the test case that often fails.

Ostracon version (use ostracon version or git rev-parse --verify HEAD if installed from source):
latest
ABCI app (name for built-in, URL for self-written if it's publicly available):
Environment:

OS (e.g. from /etc/os-release):
Install tools:
Others:

What happened:
The following tests often fail in CI tests:
failed test case
--- FAIL: TestByzantinePrevoteEquivocation (30.14s)
    byzantine_test.go:285: Consensus Reactor 0
        ConsensusReactor
    byzantine_test.go:285: Consensus Reactor 1
        ConsensusReactor
    byzantine_test.go:285: Consensus Reactor 2
        ConsensusReactor
    byzantine_test.go:285: Consensus Reactor 3
        ConsensusReactor
    byzantine_test.go:287: Timed out waiting for validators to commit evidence
FAIL
coverage: 71.5% of statements
FAIL	github.com/line/ostracon/consensus	135.075s

--- FAIL: TestStartNextHeightCorrectlyAfterTimeout (0.63s)
panic: Timeout expired while waiting for NewBlockHeader event [recovered]
	panic: Timeout expired while waiting for NewBlockHeader event

goroutine 65933 [running]:
testing.tRunner.func1.2(0x1262940, 0x160d080)
	/opt/hostedtoolcache/go/1.16.7/x64/src/testing/testing.go:1143 +0x49f
testing.tRunner.func1(0xc00d679680)
	/opt/hostedtoolcache/go/1.16.7/x64/src/testing/testing.go:1146 +0x695
panic(0x1262940, 0x160d080)
	/opt/hostedtoolcache/go/1.16.7/x64/src/runtime/panic.go:971 +0x499
github.com/line/ostracon/consensus.ensureNewBlockHeader(0xc00918ea20, 0x1, 0xc0023158e0, 0x20, 0x20)
	/home/runner/work/ostracon/ostracon/consensus/common_test.go:661 +0x2e5
github.com/line/ostracon/consensus.TestStartNextHeightCorrectlyAfterTimeout(0xc00d679680)
	/home/runner/work/ostracon/ostracon/consensus/state_test.go:1760 +0xc7d
testing.tRunner(0xc00d679680, 0x1512310)
	/opt/hostedtoolcache/go/1.16.7/x64/src/testing/testing.go:1193 +0x203
created by testing.(*T).Run
	/opt/hostedtoolcache/go/1.16.7/x64/src/testing/testing.go:1238 +0x5d8
FAIL	github.com/line/ostracon/consensus	78.018s

WARNING: DATA RACE
Write at 0x00c000f085c8 by goroutine 177:
  github.com/line/ostracon/blockchain/v0.TestBadBlockStopsPeer()
      /home/runner/work/ostracon/ostracon/blockchain/v0/reactor_test.go:264 +0xf58
  testing.tRunner()
      /opt/hostedtoolcache/go/1.16.7/x64/src/testing/testing.go:1193 +0x202

Previous read at 0x00c000f085c8 by goroutine 634:
  [failed to restore the stack]

Goroutine 177 (running) created at:
  testing.(*T).Run()
      /opt/hostedtoolcache/go/1.16.7/x64/src/testing/testing.go:1238 +0x5d7
  testing.runTests.func1()
      /opt/hostedtoolcache/go/1.16.7/x64/src/testing/testing.go:1511 +0xa6
  testing.tRunner()
      /opt/hostedtoolcache/go/1.16.7/x64/src/testing/testing.go:1193 +0x202
  testing.runTests()
      /opt/hostedtoolcache/go/1.16.7/x64/src/testing/testing.go:1509 +0x612
  testing.(*M).Run()
      /opt/hostedtoolcache/go/1.16.7/x64/src/testing/testing.go:1417 +0x3b3
  main.main()
      _testmain.go:101 +0x356

Goroutine 634 (running) created at:
  github.com/line/ostracon/blockchain/v0.(*BlockchainReactor).OnStart()
      /home/runner/work/ostracon/ostracon/blockchain/v0/reactor.go:116 +0x175
  github.com/line/ostracon/libs/service.(*BaseService).Start()
      /home/runner/work/ostracon/ostracon/libs/service/service.go:140 +0x55e
  github.com/line/ostracon/blockchain/v0.(*BlockchainReactor).Start()
      <autogenerated>:1 +0x44
  github.com/line/ostracon/p2p.(*Switch).OnStart()
      /home/runner/work/ostracon/ostracon/p2p/switch.go:227 +0x121
  github.com/line/ostracon/libs/service.(*BaseService).Start()
      /home/runner/work/ostracon/ostracon/libs/service/service.go:140 +0x55e
  github.com/line/ostracon/p2p.StartSwitches()
      /home/runner/work/ostracon/ostracon/p2p/test_util.go:168 +0x75
  github.com/line/ostracon/p2p.MakeConnectedSwitches()
      /home/runner/work/ostracon/ostracon/p2p/test_util.go:89 +0x189
  github.com/line/ostracon/blockchain/v0.TestBadBlockStopsPeer()
      /home/runner/work/ostracon/ostracon/blockchain/v0/reactor_test.go:229 +0xd37
  testing.tRunner()
      /opt/hostedtoolcache/go/1.16.7/x64/src/testing/testing.go:1193 +0x202
==================
--- FAIL: TestBadBlockStopsPeer (42.05s)
    testing.go:1092: race detected during execution of test

(Failing tests will continue to be added here.)
What you expected to happen:
Have you tried the latest version: yes/no
How to reproduce it (as minimally and precisely as possible):
Logs (paste a small part showing an error (< 10 lines) or link a pastebin, gist, etc. containing more of the log file):
Config (you can paste only the changes you've made):
node command runtime flags:
Please provide the output from the http://<ip>:<port>/dump_consensus_state RPC endpoint for consensus bugs
Anything else we need to know:

I met the TestByzantinePrevoteEquivocation which is often failing. But I never met the other two. However, I met the TestWALCrash which is often failing.
I've just addressed two test cases(PR:https://github.com/line/ostracon/pull/319):

TestByzantinePrevoteEquivocation
TestWALCrash

Thanks

This test sometimes failed.

TestSwitchAcceptRoutine
TestProposerFrequency
TestStateLockPOLRelock
TestPEXReactorSeedModeFlushStop

Of the above, this failed 2 out of 5 times.

TestSwitchAcceptRoutine
TestProposerFrequency

(accidentally closed by bot😱)

Recent errors:
--- FAIL: TestProposerFrequency (7.64s)
--- FAIL: TestBroadcastTxForPeerStopsWhenReactorStops (10.04s)
--- FAIL: TestStateBadVoterWithSelectedVoter (0.98s)

WARNING: DATA RACE
--- FAIL: TestMempoolRemoteAppConcurrency (0.07s)
    testing.go:1312: race detected during execution of test
--- FAIL: TestBroadcastTxForPeerStopsWhenReactorStops (10.04s)
    leaktest.go:132: leaktest: timed out checking goroutines

panic: BlockStore can only save contiguous blocks. Wanted 149, got 147
FAIL	github.com/line/ostracon/blockchain/v0	42.016s

panic: test timed out after 7m0s
FAIL	github.com/line/ostracon/consensus	420.828s

Recent updates:
--- FAIL: TestLightClientAttackEvidence_Equivocation (1.10s)
    detector_test.go:115: ==> verification sequential
    detector_test.go:181:
        	Error Trace:	/home/runner/work/ostracon/ostracon/light/detector_test.go:181
        	Error:      	Should be true
        	Test:       	TestLightClientAttackEvidence_Equivocation
    detector_test.go:190:
        	Error Trace:	/home/runner/work/ostracon/ostracon/light/detector_test.go:190
        	Error:      	Should be true
        	Test:       	TestLightClientAttackEvidence_Equivocation
    detector_test.go:115: ==> verification skipping
    detector_test.go:181:
        	Error Trace:	/home/runner/work/ostracon/ostracon/light/detector_test.go:181
        	Error:      	Should be true
        	Test:       	TestLightClientAttackEvidence_Equivocation
    detector_test.go:190:
        	Error Trace:	/home/runner/work/ostracon/ostracon/light/detector_test.go:190
        	Error:      	Should be true
        	Test:       	TestLightClientAttackEvidence_Equivocation
FAIL
coverage: 78.2% of statements
FAIL	github.com/Finschia/ostracon/light	63.038s

--- FAIL: TestBroadcastTxForPeerStopsWhenReactorStops (10.03s)
    leaktest.go:132: leaktest: timed out checking goroutines
    leaktest.go:150: leaktest: leaked goroutine: goroutine 2830 [select]:
        github.com/Finschia/ostracon/p2p/conn.(*MConnection).sendRoutine(0xc003312420)
        	/home/runner/work/ostracon/ostracon/p2p/conn/connection.go:438 +0x3ec
        created by github.com/Finschia/ostracon/p2p/conn.(*MConnection).OnStart
        	/home/runner/work/ostracon/ostracon/p2p/conn/connection.go:237 +0x3a5
    leaktest.go:150: leaktest: leaked goroutine: goroutine 2831 [select]:
        net.(*pipe).read(0xc00258e780, {0xc001a7a000, 0x414, 0x7ff2b7bd6d60?})
        	/opt/hostedtoolcache/go/1.18.10/x64/src/net/pipe.go:159 +0x23d
        net.(*pipe).Read(0x414?, {0xc001a7a000, 0x414, 0x800})
        	/opt/hostedtoolcache/go/1.18.10/x64/src/net/pipe.go:142 +0x55
        io.ReadAtLeast({0x7ff2b7bc8d78, 0xc00258e780}, {0xc001a7a000, 0x414, 0x800}, 0x414)
        	/opt/hostedtoolcache/go/1.18.10/x64/src/io/io.go:331 +0xde
        io.ReadFull(...)
        	/opt/hostedtoolcache/go/1.18.10/x64/src/io/io.go:350
        github.com/Finschia/ostracon/p2p/conn.(*SecretConnection).Read(0xc0000d8100, {0xc000255800, 0x400, 0x0?})
        	/home/runner/work/ostracon/ostracon/p2p/conn/secret_connection.go:246 +0x331
        bufio.(*Reader).Read(0xc00253b980, {0xc002aa[76](https://github.com/Finschia/ostracon/actions/runs/4717569416/jobs/8366320906#step:7:77)bf, 0x1, 0x1})
        	/opt/hostedtoolcache/go/1.18.10/x64/src/bufio/bufio.go:236 +0x4db
        github.com/Finschia/ostracon/libs/protoio.(*byteReader).ReadByte(0xc001[79](https://github.com/Finschia/ostracon/actions/runs/4717569416/jobs/8366320906#step:7:80)4d50)
        	/home/runner/work/ostracon/ostracon/libs/protoio/io.go:93 +0x86
        encoding/binary.ReadUvarint({0x1419d80, 0xc001794d50})
        	/opt/hostedtoolcache/go/1.18.10/x64/src/encoding/binary/varint.go:115 +0x8c
        github.com/Finschia/ostracon/libs/protoio.(*varintReader).ReadMsg(0xc002b65f70, {0x14206b8, 0xc002e29140})
        	/home/runner/work/ostracon/ostracon/libs/protoio/reader.go:68 +0x172
        github.com/Finschia/ostracon/p2p/conn.(*MConnection).recvRoutine(0xc003312420)
        	/home/runner/work/ostracon/ostracon/p2p/conn/connection.go:593 +0x26b
        created by github.com/Finschia/ostracon/p2p/conn.(*MConnection).OnStart
        	/home/runner/work/ostracon/ostracon/p2p/conn/connection.go:238 +0x411
    leaktest.go:150: leaktest: leaked goroutine: goroutine 2[83](https://github.com/Finschia/ostracon/actions/runs/4717569416/jobs/8366320906#step:7:84)2 [select]:
        github.com/Finschia/ostracon/p2p.(*peer).metricsReporter(0xc0000dc600)
        	/home/runner/work/ostracon/ostracon/p2p/peer.go:356 +0x196
        created by github.com/Finschia/ostracon/p2p.(*peer).OnStart
        	/home/runner/work/ostracon/ostracon/p2p/peer.go:191 +0xb7
FAIL
coverage: [86](https://github.com/Finschia/ostracon/actions/runs/4717569416/jobs/8366320906#step:7:87).8% of statements
FAIL	github.com/Finschia/ostracon/mempool	1[95](https://github.com/Finschia/ostracon/actions/runs/4717569416/jobs/8366320906#step:7:96).154s


Update config file to point to correct branch for upgrade test framework

Description
This commit updates config file to point to correct branch for upgrade test framework.
Signed-off-by: Sumit Jaiswal<EMAIL_ADDRESS>Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 73.053%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
42276

Relevant Lines:
57870

💛  - Coveralls


[FEAT] Pricing  Page - Implement API Endpoint for Creating Subscription Payments

Description
Develop an API endpoint to create new subscriptions through the payment gateway for the pricing page.
Acceptance Criteria

API Endpoint Implementation:

Create an API endpoint to receive subscription creation requests.
The endpoint should handle the creation of new subscriptions efficiently.

Input Validation:

Implement robust validation for input data, including plan ID and user details.
Ensure all necessary data is present and in the correct format before processing.

Payment Gateway Integration:

Integrate with the chosen payment gateway API to create subscriptions.
Handle various response scenarios from the payment gateway.

Error Handling:

Implement comprehensive error handling for various scenarios.
Provide appropriate and informative error responses.

Purpose
To enable the creation of new subscriptions by integrating with a payment gateway API.
Requirements

Design RESTful API endpoint for subscription creation.
Implement validation middleware for input parameters.
Integrate with the payment gateway API for subscription creation.
Develop error handling strategies and meaningful error messages.

Expected Outcome
A functional API endpoint that can create new subscriptions with robust error handling.
Endpoints
Create Subscription
Description: Create a new subscription through the payment gateway.
POST /api/subscriptions

{
"planId": "String",
"userId": "String",
"paymentDetails": {
}
}

Response (Success)
{
"message": "Subscription created successfully",
"subscriptionId": "String",
"status": "active"
}

Response (Error)
{
"message": "Failed to create subscription",
"error": "Detailed error message",
"statusCode": 400
}

Testing

Write unit tests for the subscription creation endpoint.
Test various scenarios including successful creation, validation errors, and payment gateway errors.
Ensure proper error handling and appropriate responses for different scenarios.
Test the integration with the payment gateway using mock data.

Not correct

closed


more metrics addition (i.e f1score, precision ) in the trainer.evaluate()

was just checking the code and saw only accuracy as a metrics, are we planning to add more metrics?

Hi @snayan06 thanks for your interest in setfit! Although accuracy is the default metric, you can specify a different one when you create the SetFitTrainer, e.g.:
from setfit import SetFitTrainer

trainer = SetFitTrainer(model=model, train_dataset=train_dataset, metric="f1")

Currently, we support any classification metric from the evaluate library: https://huggingface.co/docs/evaluate/index

ok thanks for answering , was just looking to contribute and thought that was not there in setfit, and would have been helpful to add. thanks to pointing to the the library as well.

Is there any way u guys track features and people can contribute to build these features, or it is just in the issues , new to open source but have been using huggingface/sbert models from a long time and thought if i can contribute in some way that would be good.

What if I have multi-label classification problem + I want to evaluate my eval dataset via "f1" + specific average strategy like 'weighted' or 'micro' ? Is it supported ?

Currently, we support any classification metric from the evaluate library: https://huggingface.co/docs/evaluate/index

@lewtun one limitation though seems to be that in case of non binary labels there is no way to pass an average strategy. this would need to happen here
https://github.com/huggingface/setfit/blob/a06be0efae1f71357aa357af8df42175f6adc91e/src/setfit/trainer.py#L303
So in those cases you need to fallback to accuracy or write your own trainer. Would it be in scope to support those evaluations? I am happy to open a PR for this.

shouldn't this line in the same file (and method) handle multi-label though?
https://github.com/huggingface/setfit/blob/a06be0efae1f71357aa357af8df42175f6adc91e/src/setfit/trainer.py#L295

assuming I'm not missing something major, this seems like an easy fix. here's my current implementation that I'm testing. happy to start a formal PR for this if desired @lewtun
https://github.com/huggingface/setfit/compare/main...jmwoloso:setfit:fix_multilabel_metrics?expand=1


Made apk Generator similar to webapp generator

@the-dagger Please add commits you are adding to this branch.

Current coverage is 10.80% (diff: 100%)

No coverage report found for development at 4f846d4.

Powered by Codecov. Last update 4f846d4...7daf1e0


Implement real IsUnix check in the LibUV

This change changes the UVStream.IsUnix property from always returning false to returning
the real thing.

@KrzysztofCwalina, @jkotas  can you take a look please?

Looks fine to me.

looks good! thanks.


Make sure the Tkinter app is working correctly

Make sure the Tkinter app is working correctly

Tkinter app is working correctly


[Feature Request] Ability to seek in a track

You can skip to a certain amount of time in a song.

This is already being addressed in #344. Also, please use the feature request template in the future.


Stripe is getting not so useful information about who is who in the transaction

As you can see from the screenshot of the email received from Stripe, the information from the transaction is gibberish. The only thing I can understand from it is the €9 and the default text from the Striple email template. Other than that, we can't understand anything from that email.
With Go we had proper information, detail about who paid, the proper information was being shared.

It's something that have to do with the Stripe account. Not on the frontend.

An email have been sent to whichost.com about this issue.

Here is the answer from Sharetribe. Having no example how how Go was working, I am unable to answer to this email. @RohrerHope

@lcoenen
I just looked at the previous payments we received through Go platform and they look the same.
That's my bad.
It seems there is no issue here.
My concern was raised because I want to make sure Stripe and Sharetribe are communicating properly.


tube/plate/well validation rules are not working

examples have been moved to the unexpected_pass directory
I think this was working at one point and I suspect that we can get it working agin
see also

https://github.com/microbiomedata/nmdc-schema/issues/919

Regex for plate position not working.
the problem with the regex is that the negative lookahead needs to include the end-of-string marker as well. The correct regex is: ^(?!A1$|A12$|H1$|H12$)(([A-H][1-9])|([A-H]1[0-2]))$
A10 won't validate and B01 won't validate... B1 and B01 should be valid.

See submission c41dfeac-102e-43b2-adae-6a67f25791f0 for an example
@pkalita-lbl

@pkalita-lbl @turbomam
Is this fixed in dev? So ingest to prod is still needed?

Is this fixed in dev?

I believe so but you should test and verify

So ingest to prod is still needed?

Not sure what ingest has anything to do with it? You mean deploy to production? If so, yes, whatever is on dev will go to production with the next release. It's not an change-by-change thing.

Resolved and in prod with most recent ingest.


Properties list

Implemented a function for adding a list of properties to meta-item.

I was to do the same in the afternoon but I had to leave and didn't push.
My question is: why a custom data structure? I'd rather use the old, good approach of whatever supports get<N>. This works out of the box with an std::pair as well as an std::tuple and an std::array or even an std::variant.
Isn't it better than a custom data structure I should use only for this purpose?

I wanted those rvalue references. Not sure if it changes something. On the other hand entt::a_prop despite having an ugly name communicates the intention better than std::pair. I'll look into it.

Forget about data members having type T &&. It looks like an XY-problem. What's your goal exactly?

Just want to pass the rvalues through, no other goal.

The other reason is that it's simpler) I could not get anything meaningful in 10 minutes. The other thing is that I was curious how will parameter packs work when they have different length.

Unfolding doesn't work for me with "anything with std::get()": https://godbolt.org/z/Dc3vhg
Using the recursive version is not fun because of compilation times.

Just want to pass the rvalues through, no other goal.

Ok but... why? This way I cannot pass lvalue references anymore.

Unfolding doesn't work for me with "anything with std::get()

Sure, it does.

Ok but... why?

I guess it's just me being stupid) Right now I see no reasons for doing it this way.

Sure, it does.

I thought about introducing an intermediate function the moment I turned my PC off after sending the previous comment.
There is a subtle point about "using anything compatible with std::get()" - sometimes it will do not what is intended:

An surrounding tuple is required if the user wants to add a key-only property that is of a type that is compatible with std::get() because otherwise, it may be unwrapped into a full property or into a property of a wrong type.

Trying to call std::get() on an std::variant instance that does not contain a value of the type with the provided index causes std::bad_variant_access to be thrown. Yes, it can be fixed during application testing but maybe unexpected for the users.

If you'd like I'll rework the PR to support "anything gettable" though. Of course, I shall remove those rvalue references in any case.

[...] a key-only property that is of a type that is compatible with std::get() [...]

Ok, I won't take in consideration this corner case because it's unlikely you'll use something like that for the properties and a solution exists anyway if you did it.

Trying to call std::get() on an std::variant instance that does not contain a value of the type with the provided index [...]

As above, I cannot even imagine why one should use an std::variant to set up properties to be honest but still a workaround exists for such an extreme case.
You can't stop all possible users from doing all the silly things that come to mind. As long as there is an alternative solution for them, move on and work on something else. :wink:

What about a bargain: make the properties() function support anything "gettable" but have a simple convenience class entt::a_prop that is also gettable? Personally, I would really like not to have to write this class for every project or create a support library with this class alone.
If you say "no" then I accept it and just make it work with anything "gettable" without any new DS's.

Ahaha... we don't have to make a bargain. I'm just trying to understand why you need it. :wink:
I mean, why you prefer to rely on a custom defined class to do that rather than on widely used tools that are designed for the same purpose?
 It just happens that the two members are named key and value rather than first and second. Isn't it? What am I missing?

This small custom class better communicates the intent of creating a property. And the code is the same for both key-value- and key-only properties: entt::a_prop{...}. Having to use std::tuple for creating key-only properties, while all the other properties may be defined with std::pair, does not look beautiful to me. Of course, one may use std::tuple for everything but it only works if all properties are defined by the same person here and now. In legacy code with a team bigger than one person there is a chance of getting both std::pair and std::tuple (and maybe something else "gettable") in the same list. So it's not a problem of "it works" but of "how the code feels".
In fact, it's quite usual for me to overdo things because of this so some third opinion may be viable.

Oh, wait, there is a misunderstanding. I'm not saying I want to use only std::get-table objects. Key only properties shouldn't require to use an std::tuple, I agree. These are the forms I'm thinking of:
.prop(key1, value1)
.prop(key2)
.prop(std::make_pair(key3, value3), std::make_pair(key4, value4), key5, std::make_pair(key6, value6), ...)
.prop<&annotation1, &annotation2, ...>() // function based properties

What do you think about?

I think this I can live with.

The unpack function has made this PR kinda lame and trivial)

A note regarding annotations. I just got a crazy idea: for enabling annotations (if they are used the way you've shown above) adding new properties passing a reference to the factory is required. With a reference for the factory, the annotations can do literally anything including adding new meta-members. That said, just sharing this crazy idea. Adding new meta-members from annotations will break the whole meta-state stack and all the following functions for adding properties will work with the wrong meta-item.

Ahahah... yeah, I think it would be like giving a loaded gun to users, more than C++ already is. :smile:

The unpack function has made this PR kinda lame and trivial)

I commented the issue about annotations to propose a review that fits with the current implementation.
We can safely close this PR probably, let me know. :+1:


Update to new npm org

Description
Update the package name to the new @flowfuse/node-red-dashboard org.
Once this has been merged, I will manually publish 0.7.0 to the new package name. From then on, new releases can be created in the usual way and will be published to the new org.

@knolleary all good to go


Second blog reviewed changes

Making changes to second blog PR

Dear @kraislaik -- please create a new fork from the latest version of the website and commit your second blog post, and create a new pull request. This pull request is based on an out-of-date fork and might overwrite recent website updates if merged. Therefore closing this one. Your pull request should only contain files directly related to your second blog post.


blog: Add Kubernetes-in-Kubernetes and PXE bootable servers farm blog post

Hi there!
This post is transcript of my speech, which took 1st place on Russian DevOpsConf 2020.
I would very love to share it with English speaking community.
In fact, it is a logical continuation of my previous story, published three years ago:
https://kubernetes.io/blog/2018/10/02/building-a-network-bootable-server-farm-for-kubernetes-with-ltsp/
Thank you ❤

/assign @natekartchner
/assign @kbarnard10

/unassign @kbarnard10
/assign @sftim

/retitle blog: Add Kubernetes-in-Kubernetes and PXE bootable servers farm blog post

Thank you for review @sftim
I have SVG's I will attach them soon.

Thank you for review @sftim
I have SVG's I will attach them soon.

@kvaps I don't know if this easy or not but this may help : https://github.com/misc0110/asciicast2vector

I haven't started on the mechanism I mentioned in https://github.com/kubernetes/website/pull/29676/#issuecomment-950642367
Let's skip that part. After publication, SIG Docs can go back and restructure the content to avoid relying on that third party (asciinema).
This needs the blog team to:

review it / informal LGTM
assign a date
formal LGTM
approval

As there are few people participating in the blog team, that work might not happen 'til later in November.

Hi, any news about merging this?
In projects board this issue stuck on "Requires update". Is there anything else what I can do from my side?

We have this as “Ready for review” on the project board as I see it and, yes, SIG Docs needs to get this latest iteration reviewed.

Got it, thanks!

Hi @kvaps. Please could you select a new publication date for this article? I propose the 20th of December, but any later date except the 21st of December is also OK. We prefer to avoid weekend publication.
(you will need to rename the content to match the new date, and also change the page front matter)

@sftim, it seems that images are stooped working due to expiration of deployment preview link.
I just updated date to 20 December, now they are seen:
https://deploy-preview-29676--kubernetes-io-main-staging.netlify.app/blog/2021/12/20/kubernetes-in-kubernetes-and-pxe-bootable-server-farm/

slug updated

@reylejano thanks, all links were corrected

/approve

/lgtm

Thanks @kvaps, this is a really thorough article and you've been patient waiting for our resources to get it published.


deprecation warning in dashboard infra container deployment

the dashboard infra is throwing a deprecation error:
dashboard-1             | deprecation.showPyplotGlobalUse IS DEPRECATED.
dashboard-1             | The support for global pyplot instances is planned to be removed soon.
dashboard-1             |
dashboard-1             | This option will be removed on or after 2024-04-15.
dashboard-1             |
dashboard-1             | Please update <user defined>.

Moving to medium priority since the date passed and nothing broke


storage=storages.MemoryStorage intented behaviour?

Description
I just tried to use tinyflux as an "in-memory time-series database" using the storage=storages.MemoryStorage option but found that my query returns different results then when using a "real" csv file as store.
To reproduce, simple comment/uncomment near method1/method2 to use the different constructors
#!/usr/bin/env python3

from tinyflux import TinyFlux, Point, TagQuery, FieldQuery, MeasurementQuery, TimeQuery, storages
import datetime

# method1
tiny_flux = TinyFlux(storage=storages.MemoryStorage)
# method2
#tiny_flux = TinyFlux("test.csv")

data = {
    "measurement": "sma",
    "tags": {
        "id": "should",
    },
    "time": "0",
    "fields": {
        "value" : 1.0,
    }
}

p1 = Point(time = datetime.datetime.now(), measurement = data["measurement"], fields = data["fields"], tags = data["tags"])
tiny_flux.insert(p1)
data["tags"]["id"] = "not"
p2 = Point(time = datetime.datetime.now(), measurement = data["measurement"], fields = data["fields"], tags = data["tags"])
tiny_flux.insert(p2)

tags = TagQuery()
result = tiny_flux.search(tags.id == "should") # different behaviour with MemoryStorage and CSV?
print(result)

Is this the intended behaviour?

Hi @linecker thanks for the reproducible example.  Hope TinyFlux is working well for you.
To answer your question- no, this is not the intended behavior, the module API should perform the same irrespective of the choice of Storage instance.
There's a couple of things going on here, but basically it boils down to the line data["tags"]["id"] = "not"- you are changing the value of data["tags"]["id"] which is the reference that is stored in p1.tags.  Take a look at the following minimum example:
>>> tf = TinyFlux(storage=storages.MemoryStorage)
>>> tags = {"my_tag_key": "my_tag_value"}
>>> p1 = Point(tags=tags)
>>> p1.tags
{"my_tag_key": "my_tag_value"}
>>> tags["my_tag_key"] = "some_new_value" # this is where you are changing the value of the reference
>>> p1.tags
{'tag_key': 'some_new_value'}

See the issue?  p1.tags is just a reference to the dict pointed to by tags and when you change the value of tags you are also changing what p1.tags evaluates to.  If you are new to programming this can certainly be confusing.
The CSVStorage does not have this issue because the value of tags is written to the CSV file and the dict reference ceases to exist, whereas in the MemoryStorage instance, the dict reference is kept around forever.
To fix, you should not be changing the values of the source data that your Points come from in order to make new Points.  You need to create new source data for each point.  The best way to do this is to just pass the values into the Point constructor directly.  If you can't do that, make a new dict for each point.  Example:
Making new dicts for each Point:
tiny_flux = TinyFlux(storage=storages.MemoryStorage)

data = {
    "measurement": "sma",
    "tags": {
        "id": "should",
    },
    "time": "0",
    "fields": {
        "value": 1.0,
    },
}

p1 = Point(
    time=datetime.datetime.now(),
    measurement=data["measurement"],
    fields=data["fields"],
    tags=data["tags"],
)

tiny_flux.insert(p1)

data2 = {
    "measurement": "sma",
    "tags": {
        "id": "not",
    },
    "time": "0",
    "fields": {
        "value": 1.0,
    },
}

p2 = Point(
    time=datetime.datetime.now(),
    measurement=data2["measurement"],
    fields=data2["fields"],
    tags=data2["tags"],
)
tiny_flux.insert(p2)

tags = TagQuery()
result = tiny_flux.search(tags.id == "should")

print(result)

prints
[Point(time=2023-05-15T19:46:07.812680+00:00, measurement=sma, tags=id:should, fields=value:1.0)]

Or better yet:
tiny_flux = TinyFlux(storage=storages.MemoryStorage)

p1 = Point(
    time=datetime.datetime.now(),
    measurement="sma",
    fields={"value": 1.0},
    tags={"id": "should"},
)

tiny_flux.insert(p1)

p2 = Point(
    time=datetime.datetime.now(),
    measurement="sma",
    fields={"value": 1.0},
    tags={"id": "not"},
)
tiny_flux.insert(p2)

tags = TagQuery()
result = tiny_flux.search(tags.id == "should")

print(result)

prints the same.

Thank you so much for your fast reply and the python lesson - I really tricked myself into this one!


webapp: ensure default browser is used on osx and w/o error on launching

Fix #3608, Fix #3604

[x] The PR has modified HISTORY.rst with an appropriate description of the change (see Modifying change log).

Command Guidelines

[x] Each command and parameter has a meaningful description.
[x] Each new command has a test.

(see Authoring Command Modules)

Codecov Report

Merging #3623 into master will increase coverage by 0.14%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #3623      +/-   ##
==========================================
+ Coverage    71.5%   71.64%   +0.14%
==========================================
  Files         420      420
  Lines       26186    26190       +4
  Branches     3964     3965       +1
==========================================
+ Hits        18723    18764      +41
+ Misses       6291     6251      -40
- Partials     1172     1175       +3

Impacted Files
Coverage Δ

...ice/azure/cli/command_modules/appservice/custom.py
73.3% <0%> (-0.12%)
:arrow_down:

src/azure-cli-core/azure/cli/core/util.py
69.62% <0%> (ø)
:arrow_up:

...nent/azure/cli/command_modules/component/custom.py
16.23% <0%> (ø)
:arrow_up:

...dback/azure/cli/command_modules/feedback/custom.py
31.25% <0%> (ø)
:arrow_up:

src/azure-cli-core/azure/cli/core/prompting.py
19.27% <0%> (ø)
:arrow_up:

src/azure-cli-core/azure/cli/core/_help.py
55.63% <0%> (ø)
:arrow_up:

...ource/azure/cli/command_modules/resource/custom.py
62.31% <0%> (ø)
:arrow_up:

src/azure-cli-core/azure/cli/core/parser.py
82.24% <0%> (ø)
:arrow_up:

...zure-cli-vm/azure/cli/command_modules/vm/custom.py
76.81% <0%> (+0.31%)
:arrow_up:

... and 13 more

Continue to review full report at Codecov.

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


Automated issue for commit: 79cdf863e250739236428014880aacc3511fdcee

This issue was automatically created by the GitHub Action workflow Continuos integration.
The commit hash was: 79cdf863e250739236428014880aacc3511fdcee.

This was due to database being force to reset itself

The database was resetting itself and post were being saved and not added to the db


Sync main and release branches

Description

Sync main and release to have most up to date stable image
How Has This Been Tested?

Merge criteria:

[ ] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

Needs #40 to build succesfully


Don't do anything unusual to build portable or non-portable builds

Currently source-build uses patches and extra properties to be able to build both portable and non-portable SDKs.
Final goal:

[ ] All repos that can change portableness supply one easy way to choose portable or non-portable build.
[ ] Source-build supports both portable and non-portable builds on all applicable platforms.
[ ] It does this uses only the standard build switches for each repository, no extra properties or patches.
[ ] Portableness is specified explicitly in all cases where it applies.
[ ] "No extra properties" includes not specifying RIDs, whether for "which packages to download" or "which packages to produce".

[ ] This means we can eliminate our dependency on RuntimeEnvironment checks to determine a RID before the build runs.

[ ] Source-build can build both portable and non-portable builds using either a portable (probably official) SDK or a non-portable (probably source-built) SDK.

Related: #696, #660, #750.

[Triage] Closing in favor of https://github.com/dotnet/source-build/issues/2932.


Hotfix: Revert all UNSAFE_ lifecycle methods

The addition of the UNSAFE_ lifecycle methods broke React 15 compatibility. Those methods are not intended for libraries still supporting React 15.
The only way to remove the React 16.4+ StrictMode warnings about cWM, cWRP, and cWU in a React 15 compatible way is to migrate these methods to the new lifecycle methods and use react-lifecycles-compat for backwards compatibility. The UNSAFE_ methods were to support application authors with a known target version of React (16.3+) from having to migrate every component before upgrading. Unfortunately we can't do that trick.
Additional Testing
Since the automated tests are all run against React 16, I've confirmed this locally by building my fork, and copying the lib folder to node_modules/redux-form of a download of this sandbox which is against 15.6, and confirming that the initialValues (as per #4069) are now showing. That's the only test I've run.
 I made the same mistake in another library.

I'll fix this immediately.

Published fix in v4.7.1.

Sorry, I should have looked more deeply into the polyfill, they didn't mention on the front page it also supported the UNSAFE_ methods... I should have dug deeper! Thanks Erik!

Wait... it doesn't...

Misunderstanding on my part, apparently. 🤦♂

Published in v7.4.2.


Server start hang with 'FUTEX_WAIT_PRIVATE'

After starting the server', it hangs.
The strace msg as belows:
# strace -p 5790
Process 5790 attached
futex(0x7fff02a894d4, FUTEX_WAIT_PRIVATE, 1, NULL

Found the problem.
I have 3 node: A, B, C.
And I have a basic table named 'table' with MergeTree engine and a distributed table named 'table_all' with distributed engine .
In the test environment, I build a test table named 'xx_test' and 'xx_test_all' on only one node, such as A, and I miss the different engine I should use, so the tables all use the 'distributed' table.
When I insert into table xx_test, the server A hang, as I just posted.
I think this is not a bug, but it should be optimized.

in clickhouse version <IP_ADDRESS>，we encount the same problem .
strace -p 5790
Process 5790 attached
futex(0x7fff02a894d4, FUTEX_WAIT_PRIVATE, 1, NULL
how to solve the problem.

@bookeezhou You are using strace in a wrong way.
The rule of thumb: always add -f flag,
so it should be: strace -f -p $(pidof clickhouse)

thank you share the command .i will try it.
--
Your Sincerely,
Bookee
At 2020-12-19 02:14:42, "alexey-milovidov"<EMAIL_ADDRESS>wrote:
@bookeezhou You are using strace in a wrong way.
The rule of thumb: always add -f flag,
so it should be: strace -f -p $(pidof clickhouse)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Bundles do not work.

Description
I specified an exe file and a folder. But upon clicking either of them the Files throws an "unexpected" error.
Steps To Reproduce

Open the app
Clicka bindle.

Steps to fix
Fix crash that occurs when clicking a bindle.
Files Version
Version: <IP_ADDRESS> OS Version: 10.0.19044.2364
Windows Version
Windows 10 Home edition 21H2
Relevant Assets/Logs

This is fixed in <IP_ADDRESS>.


package.json: stop including docs

Before:
npm notice === Tarball Details ===
npm notice name:          svg-sprite
npm notice version:       2.0.0-beta1
npm notice filename:      svg-sprite-2.0.0-beta1.tgz
npm notice package size:  59.7 kB
npm notice unpacked size: 278.1 kB
npm notice shasum:        b2dbac9ce5d7745b0ed1baf7d40b48519bd7fac7
npm notice integrity:     sha512-ZJ7y5+Jb2Lqir[...]YOQGEGYQ8qF1g==
npm notice total files:   42

After:
npm notice === Tarball Details ===
npm notice name:          svg-sprite
npm notice version:       2.0.0-beta1
npm notice filename:      svg-sprite-2.0.0-beta1.tgz
npm notice package size:  41.4 kB
npm notice unpacked size: 198.6 kB
npm notice shasum:        fd145049422b3c3b2e70766cdb647cc3bfae599e
npm notice integrity:     sha512-h2S37uq2liqrR[...]joQ7WmVJY5BHQ==
npm notice total files:   35

Good!
But why they were included?

There was a time that people included all the stuff in packages :) Docs can be useful, but I think we could go with a slimmer package since an internet connection is needed.


Global options

In a little spike I have:
consul = require("consul")({
  host: "s-consul-server-01"
})

consul.kv.get {key: "tenant/t1", dc: "production"}, (err, r) ->
  console.log "--- err=", err
  console.log "--- r=", r

This works and returns the kv value.
But when I try to move the dc to the global options:
consul = require("consul")({
  host: "s-consul-server-01"
  dc: "production"
})

consul.kv.get {key: "tenant/t1"}, (err, r) ->
  console.log "--- err=", err
  console.log "--- r=", r

Here the callback is invoked with undefined for both 'err' and 'r'.
From the docs it looks like I should be able to do this. Am I missing something here?

Yeah, the common options section should be more explicit, it basically works for everything except the client constructor.

So there is no way to globally define the consul client url to use at the client level? It must be passed to each function/query?

You can define all these options at the client level: https://github.com/silas/node-consul#init
All these options must be defined at the method level: https://github.com/silas/node-consul#common-options
So you can define a host, but not a dc, at the client level.
I expect the reason you're getting undefined in your second example is because the local (default) dc doesn't have the key set.
You could confirm this by printing the actual res:
consul = require("consul")({
  host: "s-consul-server-01"
})

consul.kv.get {key: "tenant/t1"}, (err, r, res) ->
  console.log "--- err=", err
  console.log "--- r=", r
  console.log "--- res=", res.statusCode, res.headers, res.body

It would be really nice to be able to define default options at the client level, especially things like the acl token.

Released to npm in version >= 0.16.0.
Example
var consul = consul({ defaults: { token: '123' } });

You can set these defaults for now: https://github.com/silas/node-consul/blob/e0d183530818af79dd65c498edc4146087839648/lib/constants.js#L11-L19


refactor: graceful handling of getUserPools

What is the purpose of the change
Graceful handling of get user pools to fix "Your Pools" modal
ClickUp Task
ClickUp Task URL
Brief Changelog

Testing and Verifying

Documentation and Release Note

Check this out and LMK what you think:
https://github.com/osmosis-labs/osmosis-frontend/pull/2910

Done in https://github.com/osmosis-labs/osmosis-frontend/pull/2910


Selecting staged diff editors should select the file in Explorer View and Source Control View

Does this issue occur when all extensions are disabled? Yes
VS Code Version: 1.76.2
OS Version: Pop!_OS 22.04 LTS

When you change the contents of files in your repository, those files will appear in the Source Control View under "Changes". If you stage them (eg with git add), they will appear under "Staged changes".
Clicking a file under "Changes" will open a diff editor; its tab will display a name like "foobar.js (Working Tree)". Clicking a file under "Staged changes" will open another diff editor with a name like "foobar.js (Index)".
If you click the tab of the unstaged diff, the matching file will be selected in the Source Control View or in the Explorer View, whichever you're in, as if you had clicked the tab of the baseline file.
However, if you click the tab of the staged diff, nothing happens. The editor doesn't recognize that "foobar.js (Index)" is semantically related to foobar.js. This feels like an oversight.
Steps to Reproduce:

Create an empty project.
Create a file foobar.js, stage it and commit it.
Change the contents of foobar.js.
Stage the change.
Change the contents of foobar.js again.
Open the Source Control View.
foobar.js should appear twice. Double-click both instances to create permanent tabs.
Create another empty tab and select it.
Fold both the "Changes" and the "Staged changes" group.
Click on the foobar.js (Working Tree) tab. This unfolds the "Changes" group. This is the expected behavior.
Click on the foobar.js (Index) tab. This doesn't affect the Source Control View. This is a bug.

Thank you very much for filing this issue and apologies for not getting back to you on this. The behaviour described in the issue is indeed a bug, and let me provide a little bit more context. The files that are being displayed in the Source Control tree use a URI with the file scheme.
When opening a diff editor for a changed file, the primary URI is using the file scheme as it is the file on disk. That is why switching to that diff editor, we are able to find the file in the Source Control tree, expand to it, and select it.
When opening diff editor for a staged file, both side of the diff editor are using a URI with the git scheme as the contents of both editors are being provided by the git file system provider. Since there is a mismatch in scheme (file vs git) we are unable to find the resource in the Source Control tree. Even if there would not be a mismatch in scheme, we would not know which one to select as both the file in the "Staged Changes" and "Changes" group has the same URI.
I cannot think of a tactical fix, as the  only way to address this issue is for the files in the "Staged Changes" group to use the git scheme but that is a more significant undertaking and might have some unforeseen regressions. I will go ahead and close the issue as won't fix for now. Thanks for your understanding.


fix Insulet pumpSettings time

A property renaming from dt -> deviceTime slipped by us, and we were passing undefined to generate the timestamp for the pumpSettings object from sundial. Since the pumpSettings timestamp is by definition the most recent timestamp in Insulet data, it is used as the starting point for BtUTC, so this bug had hugely cascading effects o_O
See also sundial #26 which this depends on (recommend using npm link locally to try it out).

 [uploader] [OmniPod] fix incorrect time on pumpSettings object (which also is the kick-off for BtUTC)

LGTM. Merging.


added more scenarios

More scenarios:

bank fraud report
bank balance
trip directions
weather
trivia
schedule
hotel service request

Note: I haven't been able to test these yet due to issues with my server. I've made changes to the API for a lot of them, so I suggest not merging yet. For tomorrow's meeting @JEM-Mosig perhaps you could checkout my branch and run the code from there?

These are all the tasks we had planned, with the following removed due to redundancy/simplicity:

shopping search
shopping order item
shopping order status
movie search (replaced with trivia, although not strictly movie related)
trip traffic (only difference between this and trip directions is in the API)

We can discuss whether there's any more potential tasks tomorrow.

Thanks for submitting a pull request 🚀 @amn41 will take a look at it as soon as possible ✨


Conversion from English to Nepali is off by one day.

When I convert a date like this
           $nepaliCurrentDate = NepaliDate::create(Carbon::now())->toBS();
and the current date is August 5, it is giving me Shrawan 22 even though it should be Shrawan 21.

This problem is solved in the latest release. Please update the package.


Fix performance bug in to_ddf for shuffle=True

After #201, when writing shuffled output data, the partitions of the original ddf will be reordered.  The approach introduced in #200 (using a to_delayed call) only required a few lines of code, but dramatically increases the size of the Dask graph for large datasets.  This PR removes the problematic approach.  Instead of re-ordering delayed partitions, we just construct a new high-level graph to produce a new Dask DataFrame with the new keys mapping to random indices of the original dataframe.

rerun tests

rerun tests

rerun tests

Thanks @benfred !


Rework bytecode VM tables to shrink binary size by using dense opcodes.

Currently the opcode tables are sparse and each (core, i64, f32) has 256 slots. Since each slot is a full pointer this means 1-2KB (32/64-bit) per table in the final binary. It'd be better to densely pack opcodes such that the tables only needed to be as large as needed based on the opcode count.
This would drop the VM bytecode dispatch rodata size from 6KB to potentially 1KB.

Fixed in #9138.


Update electra types for devnet-1

The electra branch was out of date with respect to master, I have rebased it so please could you rework this commit against the now current electra?  Thanks.


Add Dockerfile for docker-support

Implements #33

I changed the destination branch to a different branch in order to continue work.
Thanks for your contribution on the pluploader!

Sure, anytime, happy to help!


Build error caused by XCode SDK

Hello everyone,
I am having a compile error between openssl and Xcode SDK :

In file included from /usr/local/Cellar/openssl@1.1/1.1.1g/include/openssl/crypto.h:415:
/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/pthread.h:332:5: error:
declaration of built-in function 'pthread_create' requires inclusion of the
header <pthread.h> [-Werror,-Wbuiltin-requires-header]
int pthread_create(pthread_t _Nullable * _Nonnull __restrict,
^
1 error generated.

I am compiling on a macOS Catalina.
Could you please help me with this problem ?
Thanks in advance

Use GCC instead of clang for compiler, its an issue with gcc

Thank you very much :-)


Turn some lambdas into defs

pep8 apparently doesn't like it if you assign a lambda function
to a variable, things you should define the function using a def.

Coverage increased (+0.0%) to 95.93% when pulling 600f938afd1b35c904ce5eb7369474e4796ea5c1 on pep8s into bb319009e2b2d41c2c1d6dbd43bcfc8a67c9e4ea on master.


A7670 suddenly switches off

Hi,
I am finding some difficulties with the operation of the A7670E module.  I list the operations I perform;
I set I/O 25 to a high level to turn on the voltage regulator on the T-PCIE board, I wait a few seconds.
I set I/O 4 to a high level for a minimum time of 500mS then i set it high, wait 12 seconds, then I initialise the uart and after 2 seconds I send an “AT” command to which I receive a reply.
If I try to power the T-PCIE board from a USB 3.0 to the “AT” command and the subsequent “ATDXXXXXXXXX” I get a response and the call starts, if I try with a different usb port it works sporadically. The improssion is that the board with A7670E shuts down.
I checked the voltages and they are stable at 4.2V. the PowerKey is high as is the Reset. The “STATUS” and “NETLIGHT” LEDs go off and the module no longer responds to commands via UART. What could be the problem ?
I use esp- idf and c as programming language.
Thank you for your support.

This situation is usually caused by unstable power supply current. Plug in the battery as a backup power source and plug in the USB-C at the same time.

This was our main doubt, we tried to externally power vbus pins with a 12V and 2A max. power supply, regulated to 5V and occasionally the same problem occurred

12V? Are you using a PCIE board? The maximum VBUS input is 5V. Try connecting a battery. A momentary power loss on VBUS will cause the PMU to shut down for protection.

It is connected to the mains with 12V, but we have a regulator before we enter the T-PCIE, so we enter at 5V. can the back-up battery still be useful ? entering directly on the bipolar connector of the T-PCIE ?

Connect to the battery holder of the PCIE motherboard.

What voltage should the battery have?

4.2V standard lithium-ion battery


Don't panic when not using manganis

This is good in theory but magnanis can't really be disabled when running with the CLI - it seems like there's a bug in the magnanis-cli-support crate that's causing it to crash and/or not make that output file. We shouldn't be unwrapping there, but we also shouldn't be panicking upstream. This really isn't the right fix for that issue - can you do some sleuthing to figure out what's actually causing the MG json file to not exist?

I dug into manganis, and have fixed the issue: https://github.com/DioxusLabs/manganis/pull/46.
Just a classic NixOS issue :)
This explains why the optimizing assets step was taking so long, I'm guessing the CLI is timing out after the script failed. Now it completes instantly!


Update README.md

@GeethOnion your DCO sign is missing. Please sign your commit.
Take a look at https://github.com/openebs/maya/blob/master/CONTRIBUTING.md#sign-your-work

Addressed this change. Thank you for your PR.


Add route authorization

https://trello.com/c/7zZHCnY1/681-lisää-route-authorization
RequireRole and requirePermission can be used in roadmap routes to require a certain role or permission in order to access the route. If the condition is not met, user is redirected to 404 page.

Changed the names to more descriptive ones and removed mistakenly added requirement in time estimation -route. Thanks for the review 👍


[LIVY-749] Remove explicitly adding datanucleus jars

What changes were proposed in this pull request?
https://issues.apache.org/jira/browse/LIVY-749
If we start any Livy session with hive support (livy.repl.enable-hive-context=true), we see that 3 datanucleus jars are uploaded to HDFS and downloaded to drivers/executors:
Uploading resource file:/opt/spark/jars/datanucleus-api-jdo-3.2.6.jar -> hdfs://namenode/user/test1/.sparkStaging/application_1581024490249_0002/datanucleus-api-jdo-3.2.6.jar
...
These 3 datanucleus jars are not needed bacause they are already included in Spark 2.x jars folder.
The reason is because in InteractiveSession.scala, method mergeHiveSiteAndHiveDeps(), we merged datanucleus jars to spark.jars list with method datanucleusJars(). We should remove datanucleusJars() function.
How was this patch tested?
existing unit/integration tests, and manual tests.
Please review https://livy.incubator.apache.org/community/ before opening a pull request.

Codecov Report

Merging #280 into master will decrease coverage by 0.13%.
The diff coverage is 59.86%.

@@             Coverage Diff             @@
##             master    #280      +/-   ##
===========================================
- Coverage     68.54%   68.4%   -0.14%
- Complexity      906     964      +58
===========================================
  Files           100     104       +4
  Lines          5674    5934     +260
  Branches        854     895      +41
===========================================
+ Hits           3889    4059     +170
- Misses         1228    1295      +67
- Partials        557     580      +23

Impacted Files
Coverage Δ
Complexity Δ

...ain/java/org/apache/livy/rsc/driver/Statement.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...in/scala/org/apache/livy/server/ui/UIServlet.scala
4.49% <0%> (ø)
1 <0> (ø)
:arrow_down:

...a/org/apache/livy/utils/LivyUncaughtException.java
0% <0%> (ø)
0 <0> (?)

...rver/src/main/scala/org/apache/livy/LivyConf.scala
96.13% <100%> (+0.28%)
21 <0> (ø)
:arrow_down:

...che/livy/server/recovery/ZooKeeperStateStore.scala
100% <100%> (+20.93%)
8 <8> (-9)
:arrow_down:

rsc/src/main/java/org/apache/livy/rsc/Utils.java
81.57% <100%> (-1.35%)
14 <1> (-1)

.../src/main/scala/org/apache/livy/repl/Session.scala
67.69% <100%> (+0.5%)
37 <0> (ø)
:arrow_down:

rsc/src/main/java/org/apache/livy/rsc/RSCConf.java
87.85% <100%> (+2%)
8 <0> (+1)
:arrow_up:

...main/scala/org/apache/livy/server/LivyServer.scala
33.03% <13.63%> (-2.44%)
11 <0> (ø)

...c/src/main/java/org/apache/livy/rsc/RSCClient.java
73.49% <16.66%> (-1.67%)
20 <1> (ø)

... and 32 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #280 into master will increase coverage by 0.19%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #280      +/-   ##
============================================
+ Coverage     68.20%   68.40%   +0.19%
+ Complexity      965      964       -1
============================================
  Files           104      104
  Lines          5951     5934      -17
  Branches        900      895       -5
============================================
  Hits           4059     4059
+ Misses         1314     1295      -19
- Partials        578      580       +2

Impacted Files
Coverage Δ
Complexity Δ

...e/livy/server/interactive/InteractiveSession.scala
73.84% <ø> (+3.67%)
51.00 <0.00> (ø)

...cala/org/apache/livy/scalaapi/ScalaJobHandle.scala
52.94% <0.00%> (-2.95%)
7.00% <0.00%> (ø%)

...ain/java/org/apache/livy/rsc/driver/RSCDriver.java
80.00% <0.00%> (-0.84%)
45.00% <0.00%> (-1.00%)

...ain/scala/org/apache/livy/utils/SparkYarnApp.scala
73.75% <0.00%> (+1.87%)
40.00% <0.00%> (ø%)

Continue to review full report at Codecov.

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


selinux: expand the selinuxpolicy status subresource to include error messages

What would you like to be added:

expand the status subresource of the selinuxpolicy object with an error message
populate it on errors
add an e2e test that tries loading a broken policy

Why is this needed:
the selinux controller already reads errors from selinuxd, but only displays them in the logs. It would be more user-friendly if the error was displayed in the status subresource.

/remove-lifecycle stale
I'll get to this soon


Safe I/O memory leak

Original note:
side-note: this causes a leak? when a file is added to the map, it's never removed.
no idea how to fix this - because we have no way to check if there are other threads waiting to use this file(?)
tried to use m.try_lock(), but it's unreliable, it seems.

Supposedly to fix this we would have to implement stuff ourselves, and it's not that bad of a leak really, only affecting each new file that is read/written.
With that being said, I'm happy to approve regardless of this leak. If it turns out to be a larger issue than anticipated, someone else can make a PR to fix it.
Originally posted by @ASpoonPlaysGames in https://github.com/R2Northstar/NorthstarLauncher/pull/404#discussion_r1131061781

basically we'd have to make a custom mutex class with a use_count variable that tracks how many threads are waiting.

irrelevant, no longer an issue.

Did we fix this in a PR? Or was it never an issue in the first place?


HTTP basic auth example probably should not have scopes

Description
I am fairly new to OpenAPI, so I apologize if I got this wrong.
In the HTTP basic auth example it says:

openapi: 3.0.0
[...]
      security:
        - basic: ['secret']
components:
  securitySchemes:
    basic:
      type: http
      scheme: basic

Doesn't this violate the OAS 3.0.0 which states: If the security scheme is of type "oauth2" or "openIdConnect", then the value is a list of scope names required for the execution. For other security scheme types, the array MUST be empty.
Expected behaviour
        - basic: []

Actual behaviour
        - basic: ['secret']

Thanks for the report, @vilarion . Indeed, the list of scopes should be empty for this type of security


peatio-2.4.7/config/application.rb:40:in `fetch': key not found: "TIMEZONE" (KeyError)

/bin/bash -c "/usr/share/rvm/bin/rvm ruby-2.6.5 do /usr/share/rvm/rubies/ruby-2.6.5/bin/ruby /home/jeff/repo/peatio-2.4.7/bin/rails server -b <IP_ADDRESS> -p 3000 -e development"
Traceback (most recent call last):
	29: from /home/jeff/repo/peatio-2.4.7/bin/rails:8:in `'
	28: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `require'
	27: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:257:in `load_dependency'
	26: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `block in require'
	25: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
	24: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
	23: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
	22: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
	21: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
	20: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/railties-<IP_ADDRESS>/lib/rails/commands.rb:18:in `'
	19: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/railties-<IP_ADDRESS>/lib/rails/command.rb:46:in `invoke'
	18: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/railties-<IP_ADDRESS>/lib/rails/command/base.rb:69:in `perform'
	17: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'
	16: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'
	15: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'
	14: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/railties-<IP_ADDRESS>/lib/rails/commands/server/server_command.rb:142:in `perform'
	13: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/railties-<IP_ADDRESS>/lib/rails/commands/server/server_command.rb:142:in `tap'
	12: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/railties-<IP_ADDRESS>/lib/rails/commands/server/server_command.rb:145:in `block in perform'
	11: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `require'
	10: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:257:in `load_dependency'
	 9: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `block in require'
	 8: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
	 7: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
	 6: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
	 5: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
	 4: from /home/jeff/.rvm/gems/ruby-2.6.5/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
	 3: from /home/jeff/repo/peatio-2.4.7/config/application.rb:14:in `'
	 2: from /home/jeff/repo/peatio-2.4.7/config/application.rb:15:in `'
	 1: from /home/jeff/repo/peatio-2.4.7/config/application.rb:40:in `'
/home/jeff/repo/peatio-2.4.7/config/application.rb:40:in `fetch': key not found: "TIMEZONE" (KeyError)

i am using 2.4.7 release.

I also have the same problem. Did you resolve your issue? @shamart

I also have the same problem. Did you resolve your issue? @shamart

u need run init script first


Ask some doubts about datasets config

Dear author:
When I look at the following part of the code in "config/default.py":
_c.dataset.feature_path = "/home/data/activity-c3d"
_c.dataset.vocab_path = "/home/glove_model.bin"
_c.dataset.audio_path = "/home/data/wavs_16k"
c.dataset.data_path_template = "/home/new{}_data.json",
I'm not sure where the gloe_model.bin file is,could you tell me some details about this file?
note:I have downloaded the glove.42B.300d.zip file,but it does not match the file name mentioned in the code.

The glove_bin file can be downloaded from here: https://drive.google.com/file/d/19mokq1Cx3Q2XjaefiA4D7gnwxaIFA6qs/view?usp=sharing

Thank you very much!


(CC refactor 7) recovery: move detect acked packets logic to epoch

Merged as https://github.com/cloudflare/quiche/commit/70b67f9da0abef84a78112ce6e1571a3261bd515.


Accept valid checksum or CRC for device responses

This PR allows a response through if either a CRC or checksum matches. Some devices appear to protect the response payload with a 2nd checksum instead of a CRC8. See issue #9 for related reports.
Additionally this PR

Add some unit tests for response parsing
Fixes an uncaught exception when trying to access the response ID field after failing to parse
Fixes some lint issues with the response classes
Restructures the response parsing.

Close #9  and close mill1000/midea-ac-py#11

Waiting to confirm this PR functions on my own system.


Implement "bootstrap" script

Although the git repositories established on babelfish so far appear to work well enough for our development model, it is rather complicated to set up a build from a clean slate using them.  In order to do so you need to clone (at least) 5 repos and also make sure you get compatible versions/branches from all 5, then set up your build, which may involve copying some files around, which then have to go into the mission-specific version control.
I suspect that real missions/users would not want to keep these repos separate even though they are distributed separately; it is much more effort to manage it when each subdirectory comes from a different repo and it is very easy to "break" the build by grabbing incompatible branches.
Instead, a project using these would probably want to set up a single git repo for their mission that has everything included.  There are a couple ways to do this in git such that compatibility with the "upstream" repo is retained, but it does require some of the more esoteric git features to do this right.
A script could do most of this work to simplify deployment and make sure it is done right.

Imported from trac issue 17.  Created by jphickey on 2015-01-05T11:32:15, last modified: 2016-04-20T12:59:33

Trac comment by abrown4 on 2016-04-20 12:45:45:
Opened ticket under cfe_tools: https://babelfish.arc.nasa.gov/trac/cfs_tools/ticket/35


many enchantments not work

(sorry for my bad english)
if I put many enchantments, the texture doesn't work and I get warns in the console about "Invalid path in datapack"
(work on optifine)
example:
   type=item
   items=netherite_sword
   texture=fire1
   nbt.Enchantments=regex:.*(?=.*fire_aspect)(?=.*looting)(?=.*sharpness).*
   enchantmentLevels=5
   weight=4

warn message: "Invalid path in datapack: minecraft:optifine/cit/netherite/sword/!firesharploot/fire1.properties, ignoring"

The invalid path is because of the ! that's in the folder name. Fix the broken paths prior to making an issue.
I'd need the full logs to help further.

latest.log


completed binning on freq, indels and mismatches

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/104/
Test PASSed.


Loop strength reduction

Loop strength reduction
https://github.com/llvm/llvm-project/blob/main/llvm/lib/Transforms/Scalar/LoopStrengthReduce.cpp

https://en.wikipedia.org/wiki/Strength_reduction

Completed by #153


Need help with quantity purchase

Hi,
I just wanted to know if its possible to add price per quantity basis.
Example: For each product if user purchase 2 per quantity price will be less than normal price.
If there's a discount on 2 qty purchase & user purchase 3 in a row, this way price will be calculated as discount for 2 & 1 with normal price.
I know there's way to update price using update method but how to calculate product sub-total this way?
I hope you understand the problem.
Please let me know if this is possible with current version?
Thanks a lot.

This is not possible with the current version of the package I'm afraid. So you'll have to write your own logic for this.

Just one more question please.
Let me know if its possible to update/set each product sub-total?
I know we can update each product price but is there anyway we can update product sub-total as well?
Thanks a lot.


Add question about "Secure transfer required" feature

I add an answer about the ability to serve files on http only. In fact, if "Secure transfer required" feature is enabled, the static hosting feature only serves files in https which can be confusing.

@MCKLMT : Thanks for your contribution! The author, @tamram, has been notified to review your proposed change.

@MCKLMT - Thanks for making this contribution!
#sign-off

@Jak-MS : Thanks for your contribution! The author, @tamram, has been notified to review your proposed change.


ZINC v3.0 support

New types:
XStr: Type("value")
List: [1, 2, 3]
Dict: {dis:"Building" site area:35000ft²}
Grid: <<ver:"3.0" ... >>

http://www.project-haystack.org/doc/Zinc

Okay, so what's done:

XStr data type
Parsing of XStr, Dict, List and Grid in ZINC
Parsing of Dict, List and Grid in JSON
Dumping of Lists for JSON and ZINC (part of WC-1173)
Unit tests relating to lists (WC-1173)

TO DO:

Parsing of XStr in JSON
Dumping of all of the above except lists
Unit tests for dumping and parsing

Hello!  I am working with the pyHaystack module and SkySpark for a load forecasting project.  I need to parse a result grid containing Dicts and this is throwing parse errors.  This is with hszinc 1.2.2 and pyHaystack 0.92.7.  I can provide additional details but it looks like this may be as straightforward as accessing the changes referenced above.  I'd appreciate advice on how to approach this.
Thank you!

Well, right now the code is far from complete, so there's no changes really to access.  I think there have been some changes since this work started, so the code will need rebasing off current develop at best.
It's a TO-DO item, but basically it'll wait on the back-log until I get some spare time (a scarce resource lately -- practically working two jobs means I get almost no personal time to work on this stuff), or until my workplace has a need for it which would require WideSky to support these data types.

Thanks for the quick response @sjlongland.  I'm going to hack something together on our end to get a MVP deployed w/out Dicts in the next week or so.  (My colleague will be presenting this at Haystack Connect in May if you'll be there.)
Longer term, we do need Dicts. Are you interested in contributions? I can definitely justify spending a little time on this as the alternatives are to roll my own Python API wrapper or to jump out of Python for the API communication.

On 30/3/19 8:45 am, Anya Petersen wrote:

Thanks for the quick response @sjlongland
https://github.com/sjlongland. I'm going to hack something together on
our end to get a MVP deployed w/out Dicts in the next week or so. (My
colleague will be presenting this at Haystack Connect in May if you'll
be there.)

Yeah, no I don't do air travel (various reasons) so won't be at Haystack
Connect.

Longer term, we do need Dicts. Are you interested in contributions? I
can definitely justify spending a little time on this as the
alternatives are to roll my own Python API wrapper or to jump out of
Python for the API communication.

We certainly can take contributions.  It's best if there's some test
cases with them, but we'd be happy to review an implementation.

Sounds good. i'll reach back out assuming i can carve out the time to put together a respectable PR.


Fix failure to process coverage reports for parallel builds

This is a workaround for #364. Eventually this code should be updated to avoid the state sharing altogether.

@sharwell Can you please look into the test failures?

fixing in https://github.com/tonerdo/coverlet/pull/393

Fixed in #409


Report plagiarism

A company copied your tool and made a charging tool at the address: https://www.apowersoft.com.cn/make-gif?bd_vid=8762156119853365115

Yes, I'm aware.
Share with others that it's a copy of ScreenToGif, a free and pen source app.

我觉得这是对原创的不尊重，至少应该做点什么

I think this is a disrespect for originality, at least something should be done

See issue #501

something should be done

To the extent possible, there are some sites that are attacking their reputation: https://www.portablefreeware.com/forums/viewtopic.php?p=91446#p91446


Ideas of interaction design collection

Ideas on Pinterest

css web
geometric abstraction

CSS animation

https://css-tricks.com/css-animation-libraries/
https://wowjs.uk/
https://animejs.com/
https://dixonandmoe.com/rellax/
https://scroll-out.github.io/
wave effect https://codepen.io/tedmcdo/pen/PqxKXg
text animation http://cssanimation.io/getting-started.html

Will be applying rellax + scroll-out + animejs

Page transition demo
https://codepen.io/mburakerman/pen/roJmaZ
https://codepen.io/firestar300/pen/zLKZVZ
https://codepen.io/ktsn/pen/wrxymV
https://codepen.io/marcelo-ribeiro/pen/xOOKpO
others
Resize Header on Scroll
https://www.w3schools.com/howto/tryit.asp?filename=tryhow_js_shrink_header_scroll
https://codepen.io/osublake/pen/NdEONL
Transitions Only After Page Load
https://css-tricks.com/transitions-only-after-page-load/
Card hover effects
https://tympanus.net/Development/HoverEffectIdeas/
Css effects tutorial and reference
https://tympanus.net/codrops/
photo effect
https://tympanus.net/Tutorials/MotionHoverEffects/index3.html
https://tympanus.net/Development/FlowmapDeformation/index2.html
mouse trails effect
https://tympanus.net/codrops/2019/09/24/crafting-stylised-mouse-trails-with-ogl/
plugin
https://github.com/oframe/ogl
svg animation
https://github.com/maxwellito/vivus
In-view
when scrolling down to element will be running the event.
https://github.com/camwiegert/in-view
https://pudding.cool/process/how-to-implement-scrollytelling/#inview

checked then all.

the plugin, others, page transition demos, css animation look great once we know design concept for our page.
i checked all the ideas on pinterest and added some of them to: https://www.pinterest.de/serapath/play3/

Demo concept for landing page

very nice. i love this iteration. i talked with nina too and we were thinking:

maybe we could iterate on the "Smart Contract UI" font
maybe try without or an alternative to the unicorn
use the first header and try different birds to match the low poly style

everything else (clouds, trees, etc..., colors, ...) are amazing to me :-)

Alright - maybe we can use all of the above ideas and combine them into "floating islands"

see https://pinterest.com/serapath/play4

The good thing is, that this gives us a lot of modularity and flexibility, because we can change the background: in space, under water, night sky, gradient/fantasy?/rainbow? ... or any combination
and each island can have a different topic and/or color scheme. It is easy to switch the background or an island for some other island without the need to create an entire new page.
Usually when you change a significant chunk of a landing page, maybe the whole page concept does not make sense anymore, but with the island, individual parts become more independent :-)

Updated Jan. 7 2019

For completeness and archival reasons:

for completeness and archival reasons:

elements to be used on the page

low poly trees
low poly nature
low poly nature2
low poly world
low poly world2

Updated 1.14.2020

Update: 2.12.2020
For Tablet

For PC

2.19.20 Play meeting note
put all assets for Playproject to BRAND repo

Assets
Landing page
Logo
Stickers
in the landing page repo
Assets (all landing page assets here)

Logo:
try how it will look in black & white version too

updated: 2.28.20
Footer redesign
Footer demo1

Footer demo2

Footer demo3

The design of twitter profile
Banner1

Banner2

Banner3

Banner4

Demos

Twitter profile
Banner

Avatar
Avatar1

Avatar2

Avatar3


Create Italian Translation

We have i18n coverage for many languages, but one we are missing is Italian.   Would be great to get some help with this!  There is an updated guide to translation in the locales directory
https://github.com/helpyio/helpy/blob/master/config/locales/translating.md

it's far from perfect, but i did spend a lot of time on it. Moreover, it's probably an old version, so I hope it still is of some use.
it.zip
(zipped it, because github doesn't support yml files...)

@bmoree could you create a pull request to add that file to config/locales

@CGA1123 I have no Idea how to do that, that's why I've added the file to my comment.
Plus, it probably needs some work to fit with the current language file: we've customized our copy of helpy a few times, so it's probably gonna break when we update (still on v0.8.1-14-gb936447).

@bmoree I created a pull request to add your translations.
However, the new strings that have been added since the version you are currently using are not yet translated (I don't know Italian, sadly).

Thanks @bmoree for contributing this!


Tag a new release for v0.11.2 that doesn't require nim < 2.0.0

The main branch's nimble file specifies that Nim 2.0.0+ is ok, but a release has not been tagged. Running nimble install glob or nimble install https://github.com/haltcase/glob still tries to pull the old version, requiring manual updating to point to #head.

@haltcase any chance you could tag a new release?

This should be resolved with v0.11.3, thanks for your patience.
FYI, since I haven't been particularly active, I'd be open to adding another collaborator if there's anyone willing to help maintain the project.

Thank you, works perfectly :)


Add script to quickly switch to development mode

Nevermind go generate siteservice/website/website.go will do the trick.

Cool, kunt ge dat ook even in de contributing.md documenteren?

@robvanmieghem added it to the docs and clarified the diffrence between development mode and production a bit more.

Thanks!


enh: add command-line interface

Add command-line interface.

The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #20      +/-   ##
==========================================
+ Coverage    91.2%   91.25%   +0.05%
==========================================
  Files          18       20       +2
  Lines         750      881     +131
  Branches       53       66      +13
==========================================
+ Hits          684      804     +120
- Misses         45       58      +13
+ Partials       21       19       -2

Impacted Files
Coverage Δ

setup.py
0% <ø> (ø)
:arrow_up:

neurodocker/main.py
100% <100%> (ø)

neurodocker/docker_api.py
91.87% <100%> (-0.06%)
:arrow_down:

neurodocker/interfaces/fsl.py
63.63% <100%> (+1.13%)
:arrow_up:

neurodocker/parser.py
100% <100%> (ø)
:arrow_up:

neurodocker/tests/test_main.py
100% <100%> (ø)

neurodocker/interfaces/tests/test_spm.py
35.71% <0%> (-64.29%)
:arrow_down:

neurodocker/interfaces/tests/test_fsl.py
41.17% <0%> (-29.42%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

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


Some Readme Changes...

I have done changes in the Readme File, Hope you like them...
Please Review my changes...

Hey @ImagineZero0, thank you for creating this pull request! Have a wonderful day...