Corrected use of deprecated numpy behaviour. Necessary for numpy 1.12.

The behaviour we are depending on is deprecated (and removed) in newer numpy versions...
$ python -c "import numpy as np; print(np.__version__); np.zeros(0.).dtype"
1.7.1

$ python -c "import numpy as np; print(np.__version__); np.zeros(0.)"
1.12.1
Traceback (most recent call last):
  File "<string>", line 1, in <module>
TypeError: 'float' object cannot be interpreted as an index

We will also want to fix this in iris_grib.

Ping @djkirkham

@pelson The documentation for np.zeros states that if the dtype is not given it defaults to np.float64. I suggest we just use that.

The documentation for np.zeros states that if the dtype is not given it defaults to np.float64. I suggest we just use that.

If we go that far, I'd go the whole hog and just use np.float_, or if it isn't designed to be architecture specific np.float64 (I don't know if it is supposed to depend on the arch or not, though I'd guess it does).

@pelson I have been talking to Dan about this change.  Based on our conversation, I think that this fix might be a bit more future-proof than the one in https://github.com/SciTools/iris-grib/pull/75, and I want to merge this into master ready to be bundled into the upcoming v1.13.rc branch.  How do you feel about that?

@pelson Please target this against master so that the changes can be carried forward into v1.13.x

removed from v1.13 milestone
I have created #2550 to get this change into the dask feature branch
the tests are not currently failing, running with numpy 1.12
this could be due to a lack of test coverage, I am not sure
I have also proposed adding this change to master, via #2551

I have also proposed adding this change to master, via #2551

It looks like it's a different commit in #2550 and #2551 (the commit sha's are different). Could you not have cherry picked the commit? I'm just concerned about the merge conflict it will create when it comes time to merge the dask branch back in.

#2551 is merged now.
Also, the commit SHAs must be different when cherry picked because the committer name and date are part of the hash.


Patch 1

Did you mean to open this pull request against 1-0-stable branch instead?

I just followed the "Edit this guide on Github" link on the page to fix a one-word typo. I have no idea why it flagged 400+ additions & deletions.
Maybe your link is broken?

The actual change I made is here:
https://github.com/pcantrell/refinerycms/commit/4ef6505e83141d368cbef6336ac7ee7efb53af5c

No, the difference is that 1-0-stable is not the default branch and GitHub is defaulting to the master branch when it creates the pull request.  You have to click "Change Commits" before you open the pull request to choose the custom branch.  This is actually very common (most pull requests against 1-0-stable are targeting master instead).
Anyhow, I've merged your commit in 4ef6505e83141d368cbef6336ac7ee7efb53af5c so thank you very much!

I see our messages crossed paths. I'll try to remember to switch branches next time I submit a docs patch!
Too bad that the default behavior of that quick edit link is wrong. Must make a headache for you guys.

Yes, but the headache is totally worth it, I love it when we receive contributions :-) Thanks again!

It's nice to be able to actually fix a typo when I find one online! So thanks to you guys to for throwing your docs on github. Very smart.

Yeah, it's awesome huh! I only hope we can improve our documentation in the coming months, it's not the best in the world ;-) but we're getting there.


Update server port to rancher

Use default 30443 port for the Rancher server https://github.com/harvester/harvester/issues/755
Bump k3s to v1.21.3 to with runC v1.0.0 support of https://github.com/harvester/harvester/pull/990

Updated

@bk201 u may need to backport those changes to the newOS if needed, thanks.

@bk201 u may need to backport those changes to the newOS if needed, thanks.

Done in https://github.com/harvester/harvester-installer/pull/93/commits/432b6c78f9ff3e729b42e291446c367134287d0a


GH-44246: [JS] Add a lightweight array view to Table

Rationale for this change
Table.toArray() provides the convenience of using Arrow tables as common object arrays. However it does allocate an array of the size of the table that hold proxies to the table rows. This array can consume a significant amount of memory with large tables.
Providing an array proxy that wraps the table and creates struct row proxies on demand would avoid this and provide a object array view on top of a table at almost zero memory cost.
What changes are included in this PR?
This PR adds a new Table.toArrayView() method that returns an array proxy to the table rows.
It complements Table.toArray() and doesn't replace it for the following reasons:

this is a read-only view, while toArray() returns a plain mutable array. Replacing it would be a breaking change.
the proxy adds some overhead to direct array access. Tests on iterator loops show that access via the array proxy takes 5 more time than direct array access. This can be a concern for some applications, even if it should generally be negligible, and if applications seeking maximum performance should avoid using these convenience wrappers.

Also fixes #30863 by using a singleton proxy handler for StructRowProxyHandler, which further reduces memory usage.
Are these changes tested?
Yes. New tests are added to js/test/unit/table/table-test.ts for both toArrayView() and toArray() that was not tested.
Are there any user-facing changes?
This adds a new Table.toArrayView() method.

GitHub Issue: #44246

Thank @domoritz!

Would you also add this to vectors or if not, why only tables?

That absolutely makes sense. My immediate need was for tables for an application that uses plain objects, and I will add it for vectors.
Also, do you agree that toArrayView() should not replace toArray()? Or would the slight behavior change be acceptable if we replace it?

Also, do you agree that toArrayView() should not replace toArray()? Or would the slight behavior change be acceptable if we replace it?

Good question. I wonder actually whether we need toArrayView at all. Why not use make the vector/table behave like an array view?

Why not use make the vector/table behave like an array view?

Mimicking an array is a bit tricky: it has a lot of methods that are implemented by iterating it (like join, map, find, etc) and we would have to reimplement all of them. Also, Array.isArray() would return false even if we reimplemented all array methods.
This is why toArrayView() creates a proxy to an empty array and passes the table to the proxy handler:
return new Proxy([] as Array<Struct<T>['TValue']>, new TableArrayProxyHandler(this));

That way the proxy handler only has to implement iteration and direct access, and benefits from all other array methods by delegating to the wrapped array.

I see. I'll page @trxcllnt to weigh in on this one.

I did some extensive benchmarks to understand memory usage and performance overhead of toArray() vs toArrayView(). Discussing this with some colleagues, it turns out that there are a number of options when exposing a Table as an array what we may want to choose from depending on the usage context.
There are options for both the array and its elements:

array: early materialization (like in toArray()), lazy caching (creating and retaining row objects as we iterate), no caching (as in toArrayView())
rows/array items: materialization (creating a plain old JS object by copying the row data), lazy caching of properties (what StructRowProxyHandler does), no caching.

All combinations can be valid depending on how the application uses the resulting array-like object.
To account for this, I'd like to add an optional options parameter to toArray() that will allow configuring how we want the collection and rows be handled. Something like:
enum ToArrayBehavior (eager, cache, noCache);

class ToArrayOptions {
  array: ToArrayBehavior,
  rows: ToArrayBehavior
}

function toArray(options? ToArrayOptions) ...

with a default of { array: eager, rows: cache } which is what toArray() does today.
WDYT?

Table itself is already a view... why not just use table.get()?

I'm not sure how I feel about this PR yet, and have a few questions. I'm not saying I disagree with it, just trying to provide some context and discuss general strategies.

Table.toArray() provides the convenience of using Arrow tables as common object arrays. However it does allocate an array of the size of the table that hold proxies to the table rows. This array can consume a significant amount of memory with large tables.

Yeah, this is something we've struggled with since the project's inception. Every "convenience" API we've added is almost always also the least-performant way to interact with the data.
While ergonomic for vanilla JS users, these APIs encourage abuse and lead to performance pitfalls in everyday use. Anybody profiling their code would blame Arrow for "being slow," when in reality all we did was make it easy for users to do slow things.
I personally would rather focus efforts on making it easy for users to do the fastest thing (so-called helping users "fall into the pit of success").
To date, this has manifested in three ways. First, we ensure all data movement (e.g. IPC) is zero copy and provide/encourage users to use zero-copy views of the data at rest. Second, we provide O(1) sequential access and O(log(m)) random access (where m is the number of RecordBatches in a Table). And third, we try to provide utilities for caching or deferring computation (MemoizedVector, MapRow/StructRow proxies).
We have Table.toArray() because it symmetrical to the (zero-copy where available) Vector.toArray(), while using the O(n) sequential iterator, without adding much to the API surface area or bundle size.

the proxy adds some overhead to direct array access. Tests on iterator loops show that access via the array proxy takes 5 more time than direct array access.

Part of this performance deficit is definitely due to the O(log(m)) random accesses for rows in the chunked Table, compared to the O(1) access for the Array.
A while back I had a branch that attempted this approach for Table/Vector. The idea was to use Object.setPrototypeOf() to give the Table/Vector all the Array methods (as well as pass the Array.isArray() check), and then use a Proxy to implement subscript-style accesses. I abandoned the branch after the performance tests showed similar results as you've reported here.
In reference to to my point above, even though our implementation could be the fastest way to implement a JS-Array-style API via Proxies, we'll still get blamed for encouraging users to use it.

With that context out of the way, I have some questions.
First, why/how are users (or you) using table.toArray() vs. using table.get(), table[Symbol.iterator](), or operating on the underlying TypedArrays directly?
Is it to get the table into a form where it can be used with the list alebra (map/filter/reduce/etc.)?
If so, have you considered a library like IxJS, or the stage 3 TC39 iterator-helpers proposal? One of the main reasons the Arrow types implement the ][Async]Iterator spec is to make it easier for users to interoperate with libraries like these, while avoiding the O(n * log(m)) random access pitfalls, and also avoid re-implementing these libraries in Arrow itself.
Second, aside from the Array algebra, what benefit does an Array-like API bring over the existing table.get() method? For example, are there existing 3rd-party APIs that accept Arrays (and do subscript element-accesses) that you'd like to pass a Table?
Or is there a reason that operating directly on the binary data isn't easy/sufficient? For example, is the following insufficient/too inconvenient?
const times2 = table.data.reduce((results, batch) => {
  const [data] = batch.getChild("floats").data;
  return times2.concat(data.values.map((f, i) => data.isNull(i) ? f * 2 : 0));
}, new Float32Array());

Finally, is there any reason this can't live in application code instead (e.g. you create a Proxy from a table that implements the Array-subscript syntax)? I have done this a number of times until I had time to refactor routines handle tables/vectors more efficiently.

I am not intending to come off as obtuse, and I hope my questions make sense in context. I just worry about adding APIs that encourage users to do something convenient at the expense of performance.

Thanks for the extensive explanation @trxcllnt. I totally agree that providing helpers like toArray() that provide the comfort of "classic" data structures but come with some inevitable overhead cause some "it's slow compared to my objects" reactions, and I actually experienced this. So let me elaborate on my use case.
I work at Elastic where we're in the process of adding support for Arrow. The products currently use a JSON array-of-objects representation to exchange data, and have done so for more than a decade, even if deep inside Elasticsearch there is some column-oriented data processing happening. We recently added support for Arrow on the Elasticsearch server side and are now considering to consume it from Kibana, the UI front-end to manage and display data. There is a lot of existing code in Kibana based on array-of-objects and refactoring it to use Arrow vectors will take some time, and every iteration needs to bring some benefits in some area to foster adoption.
So the idea is to start from the edge (data exchange) where we can have significant gains on payload size, memory usage and eliminate parsing time, and then progressively use it more deeply in the rest of the code base. Hence the use of toArray(). That's the extent of the first iteration, and the overhead of toArray() has to be acceptable to not outweight the benefits of data transfer and zero copy.
Now I agree that toArray() and similar helpers are really a double-edged sword that may fool people into thinking that this is the way to use Arrow, and in the end be deceptive because of their overhead. But they are necessary nevertheless for transition scenarios in large code bases like the one I described.
So what about providing helpers as what they are, helpers and not primary features, and make this clear by moving them to a different location, like a TableConversionHelper or something similar? That way we don't expose Table.toArray() as something that looks like a nominal feature (and would then be deprecated), while still having room to provide useful utilities for transition scenarios, with the proper warnings saying that this isn't "the real Arrow way".
I hope this makes sense.

Thanks for the additional context. I really appreciate the effort you put into preparing this pull request and hope that you send more in the future as you find wants to improve the library. Maybe for this specific feature it makes sense to just leave arrow as is (with the iterators and toArray as a compatibility method with all the limitations it comes with) and you can use your array view code in your application (or a separate package)? I think that adding it to this repo just adds to the confusion people experience. Thoughts? @swallez @trxcllnt

Good point on the examples in the introduction. We should first show how to iterate instead.

I took a stab at encouraging more effective APIs. How's https://github.com/apache/arrow/pull/44292?


N+1 queries on admin

The admin page does one query per user rendered, which could result in more than 100 queries per page.
Adding list_select_related = ['user'] to SessionAdmin stops this.
I could do a pull request if you want

Closing since this was fixed in #107. Thank you!


Add a log exporter for tracing.

Description
Adds an open census exporter that exports to logs.
see https://opencensus.io/exporters/custom-exporter/go/trace/
Issue reference
Please reference the issue this PR will close: #1720
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Unit tests passing
[x] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

@brendandburns ,  we decided on #1720 to increase the logs in debug level and not to have stdout exporter due to much noise on the console.
On a side note,  we first put exporter components in https://github.com/dapr/components-contrib/tree/master/exporters and then register in Dapr runtime.

/ok-to-test


Setting Page

https://github.com/nathanbuchar/electron-settings

Check out the will-quit signal. https://github.com/electron/electron/blob/master/docs/api/app.md

https://github.com/hackjutsu/Lepton/pull/87
We decide to use <home>/.leptonrc other than a setting page.


[common/buf] Add bytespools ownership for buf.Buffer

V2Ray has a powerful tool that's seldom used (only 2 references in whole project): bytespool.
bytespool has built in 4 pools of size 2048, 8192, 32768 and 131072. The most frequently used buf.Buffer only use the first 2048 byte pool. The other three pools are actually very suitable for payload of variable length that may exceed default 2048 bytes.
bytespool uses Alloc() and Free() pair to manage the bytes buffers. This PR extends buf.Buffer to:

introduce a new bytespools ownership, to make use of this two functions to provide a Buffer that can hold more size than 2048
provide a new function NewWithSize(size int32), to return a buffer with capacity having at least the given size (Under the hood it will choose one of the four pools to provide a bytes buffer).

Codecov Report
Base: 39.21% // Head: 39.19% // Decreases project coverage by -0.03% :warning:

Coverage data is based on head (ddb8530) compared to base (83ea1ba).
Patch coverage: 33.33% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2336      +/-   ##
==========================================
- Coverage   39.21%   39.19%   -0.03%
==========================================
  Files         617      617
  Lines       36859    36871      +12
==========================================
- Hits        14454    14451       -3
- Misses      20816    20829      +13
- Partials     1589     1591       +2

Impacted Files
Coverage Δ

common/buf/buffer.go
80.46% <33.33%> (-6.61%)
:arrow_down:

app/router/command/errors.generated.go
0.00% <0.00%> (-100.00%)
:arrow_down:

app/router/command/command.go
36.92% <0.00%> (-3.08%)
:arrow_down:

transport/internet/kcp/sending.go
84.15% <0.00%> (-1.00%)
:arrow_down:

common/log/logger.go
82.35% <0.00%> (+1.47%)
:arrow_up:

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

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

@AkinoKaede For your comment in #1919 :

Trojan allows UDP packets up to 4096 bytes, but V2Ray only allows UDP packets up to 2048 bytes, I don't have any opinions about how to deal this problem.

We can construct a scenario that a UDP packet exceeding 2048 bytes would be problematic:
Trojan (Inbound) -> Trojan (Outbound) --- remote ---> Trojan (Inbound) -> Freedom (Outbound)

V2Ray's UDP worker only accepts UDP payload with a 2048 bytes buffer, so for Socks5 and Dokodemo UDP inbound it would not be an issue. However for Trojan inbound this is not the case.
A trojan inbound is a TCP inbound, which can receive more than 2048 bytes of a single UDP payload through TCP stream from another trojan client (not necessarily v2ray trojan client). In turn, v2ray's trojan inbound will write this large payload through dispatched link to the outbound. Let's see how current trojan inbound deals with it:

The author recognizes that a trojan UDP payload may exceed a buf.New() buffer (2048 bytes), so a buf.MultiBuffer is used to store the trojan UDP payload:
https://github.com/v2fly/v2ray-core/blob/83ea1ba3ba94c944d99cb063bc6c5f42d6cf2fff/proxy/trojan/protocol.go#L262-L278

However, when writing the multi buffer payload to the dispatched link, the buffers in trojan UDP payload is written one by one to the outbound link:
https://github.com/v2fly/v2ray-core/blob/83ea1ba3ba94c944d99cb063bc6c5f42d6cf2fff/proxy/trojan/server.go#L238-L240
In V2Ray, a UDP packet payload is represented by a buf.Buffer, not buf.MultiBuffer, so writing the buffer one by one essentially means the large UDP packet is split into multiple small UDP packet to the outbound. At least for freedom outbound it will send the payload in multiple UDP packets, causing misbehavior.

In fact, the author made attempt to deal with the issue mentioned above in trojan outbound:
https://github.com/v2fly/v2ray-core/blob/83ea1ba3ba94c944d99cb063bc6c5f42d6cf2fff/proxy/trojan/protocol.go#L102-L114
It 1) Creates a buffer of length 8192 (maxLength = 8192); 2) Read the MultiBuffer 8192 bytes by 8192 bytes, then encode each (at most 8192 bytes) buffer into trojan UDP payloads.
This in a sense fixes the problem that trojan inbound writes the UDP payload 2048 bytes by 2048 bytes. Since a UDP payload will not exceed 8192 bytes (max 4096 bytes as you mentioned), the split UDP packet in trojan inbound will be reunited in trojan outbound.
However, even if scoped in trojan inbound -> trojan outbound, this solution is still problematic. How to ensure that the passed mb buf.MultiBuffer only contains payload of 1 UDP packet? In fact this is not guaranteed, so the UDP packet in outbound may contains payload of more than 1 UDP packets from inbound, causing misbehavior.

So how to solve this problem? A good solution would be to respect the semantic that a UDP packet is represented as a buf.Buffer. So, when the UDP packet is larger than 2048 bytes, we just provides a buffer large enough for it.
This functionality is exactly what this PR provides. By using buf.NewWithSize(), we can easily create a managed buffer with capacity big enough for this large UDP packet. So, after this PR merged, it may be used to fix the trojan inbound and outbound UDP processing, as well as possibly your code in packetaddr for trojan.


Fbe.who, Fbe.issue, and Fbe.sec

@rultor release, tag is 0.0.16

@rultor release, tag is 0.0.16

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.0.16

@yegor256 Done! FYI, the full log is here (took me 8min)


[SPARK-20601][ML] Python API for Constrained Logistic Regression

What changes were proposed in this pull request?
Python API for Constrained Logistic Regression based on #17922 , thanks for the original contribution from @zero323 .
How was this patch tested?
Unit tests.

Test build #80019 has started for PR 18759 at commit 9ea5238.

Test build #80019 has finished for PR 18759 at commit 9ea5238.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/80019/
Test PASSed.

Test build #80024 has started for PR 18759 at commit 54759c4.

Test build #80024 has finished for PR 18759 at commit 54759c4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test PASSed.

Merged into master, thanks for reviewing.

@yanboliang , I'm not sure why but this PR did not make it onto the JIRA.  I've noticed it has happened a couple times elsewhere too, maybe some script is broken?  Just fyi, if you want to add a link manually.

@BryanCutler I linked this PR to the JIRA manually. Thanks for remind.

Thanks @yanboliang


donejs init fails with no compatible version of donejs-cli

Projects git:(master) ✗ donejs init djschat
npm ERR! Darwin 14.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "donejs-cli"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! code ETARGET

npm ERR! notarget No compatible version found: donejs-cli@'*'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.5.0-beta.1","0.5.0-beta.2"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/matthew/Projects/djschat/npm-debug.log
Error: Command `npm` did not complete successfully
    at ChildProcess.<anonymous> (/usr/local/lib/node_modules/donejs/lib/utils.js:45:23)
    at ChildProcess.emit (events.js:110:17)
    at Process.ChildProcess._handle.onexit (child_process.js:1074:12)

The issue was donejs-cli was in a prerelease, so once it was released as 0.5.0 it started working.


Add a general Djot benchmark for Haskell, JavaScript, and Rust.

Partially implements #7.

Why is it failing when it is not trying to build bench/general:
Run cargo build -p jotdown
    Updating crates.io index
error: failed to select a version for the requirement `reqwest = "=0.12.9"`
candidate versions found which didn't match: 0.11.23, 0.11.22, 0.11.21, ...
location searched: crates.io index
required by package `bench-general v0.1.0 (/home/runner/work/jotdown/jotdown/bench/general)`
Error: Process completed with exit code 101.

 cargo test -p test-html-ut
    Updating crates.io index
error: failed to select a version for the requirement `reqwest = "=0.12.9"`
candidate versions found which didn't match: 0.11.23, 0.11.22, 0.11.21, ...
location searched: crates.io index
required by package `bench-general v0.1.0 (/home/runner/work/jotdown/jotdown/bench/general)`
make: *** [Makefile:32: test_html_ut] Error 101
Error: Process completed with exit code 2.

Why is it failing when it is not trying to build bench/general:

Cargo seems to try to resolve all dependencies in the whole workspace regardless of what crate is being built. Seems like there is a problem with building this crate on 1.56, causing it to fail on the two 1.56 steps. This crate doesnt have to be compatible with 1.56 so might be better to exclude it from the main workspace and let it become standalone.
Since this benchmark is only testing implementations via separate commands, there might not be much of a benefit to use Rust here. Also, it currently only performs a single run for each implementation, it might be better to use a benchmarking tool, e.g. something like hyperfine to get a better statistical result. So I'm thinking that this could be solved with e.g. a simple Makefile or shell script that uses curl to fetch the input and hyperfine to perform the benchmark and maybe produce some plot.
Also, to get the most benefit of this, it would be useful if the whole process was automated, including the retrieval of the implementations. This would allow us to run it in the CI job to make sure it doesnt break, and make it easier for anyone to quickly run on their machine. In that case it might be easier to fetch their repositories and compile them (in release mode), e.g. similar to how it is done for the html-ref tests which runs the reference implementation from a submodule in ext/djot.js.
Also, this is quite independent of jotdown, it could potentially reside in a completely separate repo. Maintaining it independently rather than here might also give it more credibility to not be biased toward this specific implementation.

Okay, I made a pull request against djot. It is currently WIP, and I don't know how you test CI. When I figure out how to test, I can update to grab the repositories instead of the bin. I will look more into how html-ref is doing things. (I used wget instead of curl, because curl was grabbing an empty file.)

I figured out how to test CI setups.

I going to close this as discussion can continue in https://github.com/jgm/djot/pull/326.


Image upload to Imgur is broken with v2.12

This issue should be fixed with the next release.
If you need to use this feature, stay with v2.11.

Done.


An error occurred while rendering.  Rendering has stopped

After adding multiple CZML files, then I got an issue when trying to remove the added data sources. Below are some details:

The Cesium version I am using is 1.84.0.

When multiple datasources have been added, if I try to remove one of them using line below, the issue occurs:
  viewer.dataSources.remove(czml);

The datasources, i.e., czml files, have been added earlier via code:

      czmlDatasetPromise.then((czmlDataset) => {
                    viewer.dataSources.add(czmlDataset);
                     . . .
                });

Below is the error message on the Console:

CesiumWidget.js:724 An error occurred while rendering.  Rendering has stopped.
DeveloperError: This object was destroyed, i.e., destroy() was called.
Error
    at new DeveloperError (webpack:///../../../node_modules/cesium/Source/Core/DeveloperError.js?:44:11)
    at PolylineCollection.throwOnDestroyed (webpack:///../../../node_modules/cesium/Source/Core/destroyObject.js?:49:11)
    at PrimitiveCollection.update (webpack:///../../../node_modules/cesium/Source/Scene/PrimitiveCollection.js?:386:19)
    at PrimitiveCollection.update (webpack:///../../../node_modules/cesium/Source/Scene/PrimitiveCollection.js?:386:19)
    at PrimitiveCollection.update (webpack:///../../../node_modules/cesium/Source/Scene/PrimitiveCollection.js?:386:19)
    at updateAndRenderPrimitives (webpack:///../../../node_modules/cesium/Source/Scene/Scene.js?:3505:21)
    at executeCommandsInViewport (webpack:///../../../node_modules/cesium/Source/Scene/Scene.js?:3280:5)
    at Scene.updateAndExecuteCommands (webpack:///../../../node_modules/cesium/Source/Scene/Scene.js?:3023:5)
    at render (webpack:///../../../node_modules/cesium/Source/Scene/Scene.js?:3907:9)
    at tryAndCatchError (webpack:///../../../node_modules/cesium/Source/Scene/Scene.js?:3926:5)

(This question is also asked at: https://community.cesium.com/t/load-multiple-czml-files/8353/6)

I did more tests by using more datasets. Then I realized only two datasets caused the issue when they both were added onto the viewer. Of the two datasets, one czml file was copied from the other czml file (then manually removed some features). I guess the root cause could be feature ID's conflicts.
So I think it is a dataset issue, not Cesium API's issue.


Tag selected images using Clarifai (Jan 2019)

[ ] Refactor and test code (to accommodate recent changes to their API)

[ ] Identify unprocessed image urls

[ ] Process image urls using Clarifai API

[ ] Update images with their respective tags

[ ] Create a new table to log images that were rejected by their API

Assigning this to until we have more clarity on the number of operations we've been whitelisted for.

Provider
Total images
# Prev. tagged

Met Museum
447,308
190, 332

Cleveland Museum*
29,073
0

McCord
109,160
0

Museums Victoria
71,706
20,947

Nypl
168,550
168,332

Rijksmuseum
30,000
30,000

Digitalt Museum
122,335
79,574

Thingiverse
22,146
0

Animal Diversity
16,152
0

Science Museum
55,788
10,498

EOL
523,384
56,680

Behance
5,569,434
1,213,281

*do we want to wait until reprocessing their data to tag them

Provider
Success
Error

Met Museum
255,392
1,584

Cleveland Museum
29,073
0

McCord
109,073
87

Museums Victoria
50,756
3

NYPL
1
217

Rijksmuseum
--
--

Digitalt Museum
42,758
3

Thingiverse
21,916
230

Animal Diversity
15,538
614

Science Museum
45,290
0

EOL
6,760
459,944

Behance
957,017
42,951


Setup supabase database

We're trying Postgres first, if Postgres does not work, we will use supabase


WIP Incident Redis Refactoring Madness

[x] alerts run
[x] dashboard renders
[x] unknowns trigger
[x] incident view working
[ ] alert counts reporting
[ ] restore historical incidents
[x] action notifications working again
[ ] tests passing
[x] dependency function working.

Bug: Dashboard shows alert key now instead of subject:
Master:

Branch:

Bug: Full History links on dashboard don't work anymore:
Link:

View:

Bug: Dashboard alert expands that show the template body no longer work:
Master:

Branch:

Bug: Silence doesn't show alert will be silenced when using test on the silence page:
Master:

Branch:

Bug? Stuff still gets written to bold when stopping bosun:
2016/01/08 10:19:15 info: bolt.go:100: save to db complete```

Bug? Migrating state runs on a second run, not just the first according to the log:
2016/01/08 10:21:21 info: bolt.go:487: migrating state

Bug: New template erros on many alerts that we don't see on prod:
2016/01/08 10:22:08 info: check.go:253: hardware{host=nyhq-fs01}: template: header:10:19: executing "header" at <.Group.host>: Group is not a field of struct type *sched.Context
2016/01/08 10:22:08 info: check.go:266: hardware{host=nyhq-fs01}: template: header:10:19: executing "header" at <.Group.host>: Group is not a field of struct type *sched.Context
2016/01/08 10:22:08 info: check.go:279: hardware{host=nyhq-fs01}: template: hardware:1:65: executing "hardware" at <.Group.host>: Group is not a field of struct type *sched.Context```

Multiple migrations fixed. May need to flush redis to avoid duplicate data.

Bug: Historical testing doesn't seem to work:
Master:

Branch:

2016/01/19 09:44:27 info: check.go:269: hardware{host=ny-sql04}: template: header:22:48: executing "header" at <.Last.IncidentId>: IncidentId is not a field of struct type models.Event```


Issue with hotfix for w3c chromeOptions

What are you trying to achieve? (Expected behavior)
Adapt acceptance testing with Codeception for ChromeDriver v75, using webdriver v1.7.0.
What do you get instead? (Actual behavior)
In the code of the hotfix for w3c I get an error toArray() called on Array for Facebook\WebDriver\Remote\RemoteWebDriver line 112.
if (!isset($chromeOptions->toArray()['w3c'])) {
How could the issue be reproduced? (Steps to reproduce)

Using Codeception pass capabilities to chromeOptions
modules:
  enabled:
    - WebDriver:
        url: http://localhost:8000
        browser: chrome
        port: 9515
        restart: true
        capabilities:
          chromeOptions:
            args: ["--headless", "--disable-gpu", "--no-sandbox"]

Details

Php-webdriver version: 1.7.0
PHP version: 7.3
Operating system: Linux
Browser used + version: ChromeDriver v75

I believe the cause is that the hotfix assumes the class Facebook\WebDriver\Chrome\ChromeOptions is always used, but before the hotfix it allowed passing an array instead.

Ah, nevermind I see now it is fixed in main branch, just not released yet.

Yes, fixed in 1.7.1.
Ref. #642 .

Still no substance


Train recognizer to detect long lines

Hi,
this is a question and not an issue: I'm trying to retrain the recognizer on a custom alphabet, so that he is able to recognize chars in an image with a width of 512px and up to 60 chars.
My idea is to first train the recognizer with generated images and only the fonts I need. In the second step I would like to load the weights of the first step and fine tune it with real images.
Now I'm running into the issue that I'm not able to change the size of the model. As soon as I set the width to 512 and try to load the 'kurapan' weights I'm getting a shape error:
ValueError: Shapes (28672, 64) and (11200, 64) are incompatible
If I set the weights to None (no pre-trained weights) my loss stays consistency above 20.
Next issue could be the max length of the model, which seems to be 48 chars due to the length of the CTC func. I can't figure out how to change that.
Could you guide me into the right direction to solve this issue?

The length of the predicted sequence is always equal to input_width/(pool_size**2) - rnn_steps_to_discard. You are getting a model weights shape error because the Kurapan weights use a Spatial Transformer Network (STN) that is not invariant to the input width. Incidentally, I've had problems training the STN from scratch. You might want to try training from scratch with that disabled, which also allows you to change the input width (and therefore the predicted sequence length) later on without any problems. See example below.
recognizer = keras_ocr.recognition.Recognizer(
    weights=None,
    alphabet=keras_ocr.recognition.DEFAULT_ALPHABET,
    build_params={**keras_ocr.recognition.DEFAULT_BUILD_PARAMS, 'width': 400, 'stn': False}
)


Terminal is blank

Issue Type: Bug
the Terminal is blank.  Just blinking and I can not type anything inside
VS Code version: Code 1.43.0 (78a4c91400152c0f27ba4d363eb56d2835f9903a, 2020-03-09T19:47:57.235Z)
OS version: Windows_NT x64 6.2.9200

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-4030U CPU @ 1.90GHz (4 x 1896)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.92GB (1.95GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.1.1

vscode-npm-source
dku
1.0.0

EditorConfig
Edi
0.14.4

vsc-material-theme
Equ
32.5.0

vsc-material-theme-icons
equ
1.1.4

vscode-npm
fkn
3.3.0

terminal
for
0.0.10

start-git-bash
McC
1.2.1

vscode-exec-node
mir
0.5.1

LiveServer
rit
5.6.1

(1 theme extensions excluded)

This looks like an issue with our old terminal backend "winpty", going forward we are focusing our efforts on the new backend "conpty" which is build by the Console team at Microsoft and should fix many issues with the terminal under Windows. You can read more about getting ConPTY here.
/duplicate https://github.com/Microsoft/vscode/issues/45693


[IA-2938] Clean up Azure IPs

First pass at adding Janitor support for Azure resources. Currently just cleans up PublicIp, but if we find this approach works we can start adding other resources.
As part of this I also updated Janitor to pull Azure creds from vault. It currently works for local/integration testing; we'll probably need to update terra-helm to pull the new vault secrets for this to go live.

Updated this with the latest CRL and tested end to end. I think this is good to go but I'll hold off from merging until next week -- I still need to create the terra-helm PR for the 'live' deploy..

Couple updates here:

I synced with DevOps and they are looking at adding Terraform support for Azure envs (see https://broadworkbench.atlassian.net/browse/DDO-1772).
In the meantime I manually inserted a vault secret for the managed app publisher and updated the crljanitor chart in terra-helm to use it: https://github.com/broadinstitute/terra-helm/pull/645

So I think once the above terra-helm change is in, then this PR can be merged. I will then make a separate Janitor PR to support other Azure resources (disk, network, vm).


feat: replace search functionality with flexsearch

resolve #147

[x] fix the search result style
[x] apply more search scope including tags and descriptions
[x] migrate markdown raw content search result to rendered html string

/unlabel wip


update v0.6.0 chart

Codecov Report

Merging #179 (4a1f250) into main (fbb18e9) will decrease coverage by 0.34%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #179      +/-   ##
==========================================
- Coverage   23.28%   22.93%   -0.35%
==========================================
  Files          38       38
  Lines        6007     6007
==========================================
- Hits         1399     1378      -21
- Misses       4438     4459      +21
  Partials      170      170

Flag
Coverage Δ

unittests
22.93% <ø> (-0.35%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/controller/controller.go
39.87% <0.00%> (-6.55%)
:arrow_down:

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


REP corrupts some Unicode characters (emoji)

Windows Terminal version
1.18.1462.0
Windows build number
10.0.25300.1000
Other Software
No response
Steps to reproduce
Repeating some emoji with an escape sequence results in mojibake. In WSL or any Linux:
$ printf '\e[6n💓\e[1b\e[6n\n';cat
💓�
^[[4;1R^[[4;4R^C

Expected Behavior
On a recent xterm (run with xterm -fa Mono -fs 14, to get TrueType fonts) the output is:
$ printf '\e[6n💓\e[1b\e[6n\n';cat
💓💓
^[[4;1R^[[4;5R^C

Windows Terminal also behaves as expected for ✅, this only affects some emoji characters.
Actual Behavior
As above, the second character is corrupted, see screenshot too.

Hey! This issue is a duplicate of #15390. 🙂 I believe #15541 made it possible to fix the issue for this particular escape sequence. I'm not entirely sure which part in our code base doesn't handle surrogate pairs, etc., but I suspect it can be discovered by setting a breakpoint on AdeptDispatch::_FillRect.
/dup #15390


Primordial Goo

ANOTHER goo type, but this one feels like it deserves a place among the ranks as the true "rarity" goo.
Diamonds and Netherite scrap have a sort of problem, they're relatively easy to acquire through conventional means.
You can construct obsidian fairly easily, you can get metal by decomposing regal, and you can get crystal fairly commonly in the world in the form of quartz, diorite, granite, ghast tears (a little less easy) and emeralds from villager trades are by far the most abusable vector.
The means of producing the two best materials in the game is, in a sense, more direct than I intended.
Primordial Goo is a goo type themed around being very old and, sort of directly, very rare.
You'll be able to obtain it from snails, once they exist, and that's the only way to get it, unless you're willing to sacrifice netherite scrap and diamonds.
Primordial goo's effect in world is intended to be very unique.
When primordial goo resolves on a splat, it dematerializes the world around it, forming what I'm calling a Glorb. Glorbs are big heterogeneous blobs that do not splat, and do not resolve. Intended as a sort of late game mechanic for the Goomancer to travel to exotic locations and directly dematerialize the world into the goo they need rather than relying strictly on machines.

Is there some easy source of regal? The regal -> metal recipe doesn't seem that helpful in making scrap.
I'm not sure I agree with this as a solution to diamonds and scrap. Making diorite and granite not contain crystal and lowering the amount of crystal in emeralds seems like a good enough fix for diamonds, and adding royal and/or a large amount of decay to scrap would complicate the recipe enough to make it harder. I don't love the idea of having to hunt a rare mob to be able to get the goo for these, because they're already rare, so I'd rather just hunt for them directly. So balancing the rarity and the amount of goo such a mob would give sounds tricky.
I'm trying to automate crystal production in my survival world, and right now it's mostly waiting for honeycombs for gaskets, because it needs a lot of goo machines. For reference as to current balance, it'll take me 576 cobble, 8 ice, 12 slime, 20 netherwart to make 1 diamond. Most of these are made a lot easier by automation from other mods, but it still doesn't feel like it's going to be too easy.

Bees make regal. Have a look at honeycomb.
Granite and diorite contain quartz and quartz is crystal.
I'm not opposed to giving a mixer recipe for primordial at an extremely lossy rate as a direct answer to your concern about it being difficult to acquire. The point is to increase the complexity with something specific to the rarity of those materials.
Crystal doesn't do that, adjusting numbers by itself doesn't change complexity, and the point isn't that you can make diorite into diamonds. It's that you can make diamonds from diorite alone. Or lapis alone. or quartz alone. Taking crystal out of things that legitimately contain it isn't an answer I'm receptive to.

So, proposal:
Mix 32 weird and 32 crystal for 1 primordial.
My intended primordial gating on scrap and diamonds is, perhaps surprisingly, to put 1 mB of primordial on them.
So if you're not willing to play the mob game, you can still access these things in a way that's automatic.

Alternatively drop those exchange rates to 8, 8 : 1
And put 4 mB of primordial on them. That way the price in weird and crystal is proportionally the same but the numbers don't feel quite as weird.

@jackhardwareltd The goal is that the mob spawns rarely, because once you get it, you have it from then on, the whole production chain Xeno has in his head (With feedback from me and others on discord) is designed so that primordial goo is tier 4 in the goo crafting tiers, locking the 2 most valuable resources in vanilla at tier 4 of a mods crafting progression is more then reasonable, especially when you take into account that they are currently accessible at tier 1 without much effort.
Right now, Xeno has to be incredibly specific with what items can have Crystal goo, and how much - just adding 1mb of Primordial to diamonds means that Xeno no longer has to be that careful, because primordial is, by design, a tier 4 material in goo, and thus not something you can get in large quantities before having a big goo setup.
A lot of discussion has gone into how this should happen, and even then the idea has not been implemented yet
Once Xeno does implement it, he may find that the existing spawn chances for the mob, or their Primoridial production do not match his intent, and then he can simply make them more or less rare, and drop more or less Primordial.
The goal of primordial is allowing Xeno to be more free with the Crystal, Metal and Regal goo types, which currently, by necessity, he has to be incredibly strict about to ensure that MC's most end-game materials remain end-game materials.

This is done


Fix link to base blog tags template

The previous link 404s after this commit https://github.com/11ty/eleventy-base-blog/commit/216a9de439076b96b2b4e98f8414ba617b279487. This PR updates the link to the correct page.

Thank you!


LANG-1248 FastDatePrinter Memory allocation regression

When the code was migrated from StringBuffer to Appendable in LANG-1152.
We've lost the ability to modify the buffer (setCharAt)
The new implementation of appendFullDigits allocate a temporary char
array to work around that limitation.
This is a major source of memory allocation which is not present in
version 3.4.
Test case :
Single fastdateformat instance
100000 format of long
pattern : yyyy-MM-dd'T'HH:mm:ss.SSSZ
lang 3.4 : ~30 MB allocated
lang 3.5-snapshot : ~40 MB allocated
-> ~9.3 MB are coming from appendFullDigits called from
PaddedNumberField
This commit add a fast path for 1 to 4 digits which avoid the memory
allocation from the temporary work array.

Coverage decreased (-0.03%) to 93.417% when pulling d201ad32af1e71140539fbd7efe701f6b2e89ffe on benbenw:LANG-1248 into ce0c082898e3551d313fb5b73763f399232b3fd5 on apache:master.

Are you OK with using this alternative implementation?

Discussion was done on the jira
https://issues.apache.org/jira/browse/LANG-1248


[WIP] HugeCTR raw format support

https://github.com/NVIDIA/NVTabular/issues/255

@albert17  I'll run some tests but can you also run the end2end workflow with binary format using this PR please?

rerun tests

rerun tests

This is actually still a WIP PR. So, we'll need to check couple of things. Also, seems like HugeCTR team needs to update couple of things as well.

I tested for the whole Criteo dataset, and I run out of disk space when generating the output files (593G) with NVT.
I tested for 2 Criteo days (1 day for training, 1 day for validation) and NVT run successfully, roughly it looks like it is ~3x slower than writing parquet files. After that, I have tried to run HugeCTR for DLRM: It looks like the data format is read properly, but when the training starts I get a core dump (I have updated the config file for Raw format following the HugeCTR samples). This is the output;
[0.001, init_start, ]
HugeCTR Version: 2.2.1
Config file: dlrm_fp32_16k.json
[01d17h44m16s][HUGECTR][INFO]: algorithm_search is not specified using default: 1
[01d17h44m16s][HUGECTR][INFO]: Algorithm search: ON
Device 0: Tesla V100-DGXS-16GB
Device 1: Tesla V100-DGXS-16GB
[01d17h44m22s][HUGECTR][INFO]: Initial seed is<PHONE_NUMBER>
[01d17h44m22s][HUGECTR][INFO]: cache_eval_data is not specified using default: 0
[01d17h44m22s][HUGECTR][INFO]: num_internal_buffers 1
[01d17h44m22s][HUGECTR][INFO]: num_internal_buffers 1
[01d17h44m22s][HUGECTR][INFO]: Vocabulary size: 2116453
[01d17h44m22s][HUGECTR][INFO]: max_vocabulary_size_per_gpu_=15500000
[01d17h44m22s][HUGECTR][INFO]: All2All Warmup Start
[01d17h44m22s][HUGECTR][INFO]: All2All Warmup End
[01d17h44m46s][HUGECTR][INFO]: gpu0 start to init embedding
[01d17h44m46s][HUGECTR][INFO]: gpu1 start to init embedding
[01d17h44m48s][HUGECTR][INFO]: gpu0 init embedding done
[01d17h44m48s][HUGECTR][INFO]: gpu1 init embedding done
[33128.3, init_end, ]
[33128.3, run_start, ]
HugeCTR training start:
[33128.4, train_epoch_start, 0, ]
Bus error (core dumped)
CPU times: user 708 ms, sys: 302 ms, total: 1.01 s
Wall time: 34.6 s

@albert17 Did you also add the “float_label_dense”: true into data layer?

Funny but we also need to set the number of samples in the data to num_samples parameter in data layer.

It's working for me now using 2 days of criteo data.
I saw is the data size of binary file is 2.5x of original data (don't know why) and parquet writer is almost 3x faster.

I added the num_samples parameter as the sum of every file num_rows (for training and validation respectively). Is this the correct way to calculate it?
I didn't add the  “float_label_dense”: true, but I have just added and I still get the same error.


Terms of Use Per Session

Is there a way to enforce the acceptance of "Terms Of Use" per login? Currently users only need to accept the "Terms Of Use" once but certain government organizations require the acceptance of them per login session.

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

ID: 618ca851-56c8-5ba1-35de-a7b8e7af8aa2
Version Independent ID: 5facc663-2e29-65ad-f208-982150351b22
Content: Azure Active Directory Terms of use
Content Source: articles/active-directory/governance/active-directory-tou.md
Service: active-directory
GitHub Login: @rolyon
Microsoft Alias: rolyon

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

I just reproduced this in my own account and created a conditional access policy. At present this sort of configuration does not seem to be supported based on the controls available in the blade.
CC @rolyon for confirmation.

Your best bet would probably be to hard code this in instead.

@KehindeOwens We will now proceed to close this thread. If you have further questions, please tag me or @rolyon in the comments and we will gladly continue the conversation.


@dnd-kit/modifiers package code seems incorrect.

Hi @clauderic Saw the latest release has snapCenterToCursor. Nice one!
I've updated dnd-kit packages in my project. However they don't seem to work. Looked into the package and don't see any code from the master branch in it. This is what I see

Not sure how do I go about using this. Would appreciate some help, thanks.

What do you mean by "they don't seem to work"?
The code for this modifier is here https://github.com/clauderic/dnd-kit/blob/master/packages/modifiers/src/index.ts#L7
If you updated to the latest version of @dnd-kit/modifiers, make sure you also upgrade all your other @dnd-kit packages too because there are breaking changes. Refer to the changelog of each package fo more details on the changes.


Vulcan + Storybook Discussion

Problem
Storybook does not understand how to parse the meteor npm imports.
Possible Solution
After some playing around I managed to get it to work if I extract all Vulcan packages and higher order components that contain queries into a container component and the 'dumb' components just contain the UI. This component has no UI components inside it and it passes the Vulcan components to its children. This allows you to import the non-container components into Storybook and pass it mock functions and Components that are not from Vulcan as props into your dumb components.
The container components will not be imported into your stories. It gets a little more complicated with nested components as you need to mock even more components and then pass them through.
Thoughts
Components have to be more verbose and have separate files for each. Must avoid imports from Meteor/Vulcan in your storybook tested components. However promotes better testing practice as all testable components needs to be pure(ish), they can't even have a single Meteor import, so promotes separation of concerns of your components to container vs UI components.
Vulcan's registerComponent makes it quite easy to mock the components as all of the components you need to pass as prop are contained under one object. Makes me think about keeping components pure by using the recompose library to map props and not directly import them in to make it easier to mock them out.
Jest allows you to setup mocks for certain paths. I'm not that experienced with Storybook, so maybe there is a way to mock out modules such as Meteor in the way Jest mocks it out.
Things that need to be worked out
I haven't figured out how to import css in yet such as bootstrap, but that isn't Vulcan specific so should be worked out easily.
Code
// ClientItem.js

import React from 'react'

const ClientsItem = ({ client, currentUser, check, columns, Components }) => (

    {columns.map((column, i) => (

        <column.component document={client} />

    ))}

      {check(currentUser, client) ? (
        <Components.ModalTrigger label="Edit Client">
          <Components.ClientsEditForm
            currentUser={currentUser}
            documentId={client._id}
          />
        </Components.ModalTrigger>
      ) : null}

)

export default ClientsItem

// ClientsItemContainer.js
import React, { PropTypes, Component } from 'react'
import { registerComponent, Components } from 'meteor/vulcan:core'
import { withProps, compose } from 'recompose'
import { Link } from 'react-router'

import Clients from '../../modules/clients/collection.js'
import ClientsItem from './ClientsItem'

const enhance = compose(
  withProps(ownerProps => ({
    check: Clients.options.mutations.edit.check,
    Components
  }))
)

const ClientsItemContainer = enhance(ClientsItem)

registerComponent('ClientsItem', ClientsItemContainer)

export default ClientsItemContainer

// clientItem.stories.js

import React from 'react'

import { storiesOf } from '@storybook/react'
import { action } from '@storybook/addon-actions'
import { linkTo } from '@storybook/addon-links'

import { Button, Welcome } from '@storybook/react/demo'
import ClientsItem from '../components/clients/ClientsItem'
import { Link } from 'react-router'
import moment from 'moment'

const columns = [
  {
    label: 'Name',
    field: 'firstName',
    order: 10,
    component: ({ document: d }) => (
      <Link to={`/client/${d._id}`}>{`${d.firstName} ${d.lastName}`}</Link>
    ),
    sort: true
  },
  {
    label: 'Last Interaction',
    field: 'lastInteraction',
    order: 10,
    component: ({ document: d }) =>
      d.lastInteraction ? (

          {moment(d.lastInteraction).format('dddd, MMMM Do YYYY, hh:mm:ss')}

      ) : (
        'N/A'
      ),
    sort: true
  }
]

const ComponentsMocks = {
  ModalTrigger: () =>
Edit Client
,
  EditForm: () =>

}

storiesOf('Client Single', module).add('with Text', () => (
  <ClientsItem
    check={() => true}
    Components={ComponentsMocks}
    columns={columns}
    client={{
      _id: 123,
      firstName: 'Jeff',
      lastName: 'Lau',
      lastInteraction: new Date()
    }}
  />
))

The part where you have to mock out the child component that are referenced via Component.* seems worst to me. For my codebase, this would make refactoring components a giant pain, and generally require massive amount of mocking (and make it hard to actually test the UI, because you can't really see a single full Post or a Comment or a Toolbar, because they all have subcomponents).

@Discordius Hey thanks for the feedback. I ran into this issue and what I did was to import the subcomponents (the non-container versions of them). It was a reasonable amount of mocking, but not much more than i'd have to do if I was testing it with a normal test framework anyway.
In my normal app, my <ClientItem /> is wrapped like above, but in the mock test I'm not composing it and just mocking the data. This is the best solution I could come up with yesterday. There might be a better a way.
import React from 'react'

import { storiesOf } from '@storybook/react'
import { action } from '@storybook/addon-actions'
import { linkTo } from '@storybook/addon-links'

import { Button, Welcome } from '@storybook/react/demo'
import ClientsList from '../components/clients/ClientsList'
import ClientsItem from '../components/clients/ClientsItem'
import { Link } from 'react-router'
import moment from 'moment'

const columns = [
  {
    label: 'Name',
    field: 'firstName',
    order: 10,
    component: ({ document: d }) => (
      <Link to={`/client/${d._id}`}>{`${d.firstName} ${d.lastName}`}</Link>
    ),
    sort: true
  },
  {
    label: 'Last Interaction',
    field: 'lastInteraction',
    order: 10,
    component: ({ document: d }) =>
      d.lastInteraction ? (

          {moment(d.lastInteraction).format('dddd, MMMM Do YYYY, hh:mm:ss')}

      ) : (
        'N/A'
      ),
    sort: true
  }
]

const mockData = [
  {
    //...
  }
]

const ComponentsMocks = {
  ModalTrigger: () =>
Edit Client
,
  EditForm: () =>
,
  ClientsItem: ({ client }) => (
    <ClientsItem
      check={() => true}
      Components={ComponentsMocks}
      columns={columns}
      client={client}
    />
  ),
  ClientsNewForm: () =>

}

storiesOf('Clients List', module).add('with Text', () => (
  <ClientsList
    results={mockData}
    currentUser={{}}
    loading={false}
    loadMore={() => true}
    count={mockData.length}
    totalCount={mockData.length}
    terms={{}}
    setTerms={() => true}
    Components={ComponentsMocks}
  />
))

For style import I use a main decorator that imports all needed libs.
import jquery from 'jquery';
global.$ = jquery
global.jQuery = jquery
require('bootstrap/dist/js/bootstrap');
import 'bootstrap/dist/css/bootstrap.min.css';
import React from 'react'
import { Grid } from 'react-bootstrap'
import styled, { ThemeProvider } from 'styled-components';

export const MainDecorator = (story) => (
  <Grid>
    {story()}
  </Grid>
)
export default MainDecorator

Then in your storybook config.js simply write addDecorator(MainDecorator).
Concerning Meteor + Storybook, another direction would be to replace Node by Meteor as the runtime executable.
I don't know if it is possible, but it would be far easier than trying to mock the whole world.
Right now I avoid Meteor stuffs in my React components too but that can be annoying. This is especially true in Vulcan, that exploits cleverly the Meteor features even for purely frontend stuffs, like registerComponent.
Also, Storybook should not be only a unit development interface, it should also enable people to test fully integrated components, including Meteor/React components. In other projects I use it with full fledged containers, and even allow API calls. That makes me gain an infinite amount of time and that is the desirable goal.
I think forking/modifying Storybook so that we get a real Meteor support is still the best direction here.

Storybook does not understand how to parse the meteor npm imports.

Can you please elaborate this part?

@Hypnosphi a sample Meteor import might be:
import { Components } from 'meteor/vulcan:core

So what's the error when you try to do that?

I think we can close this :) Storybook install is documented here: https://github.com/VulcanJS/vulcan-docs/blob/master/source/storybook.md


feauture(eos_designs/eos_cli_config_gen):RFC5549

Change Summary

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Code style update (formatting, renaming)
[x] Refactoring (no functional changes)
[x] Documentation content changes
[ ] Other (please describe):

Component(s) name
arista.avd.eos_designs
eos_cli_config_gen
Proposed changes

Add support for rfc5549.
Refactor eos_cli_config_gen router_bgp documentation template.
Fix issue with router_general leak routes.
Add description to bgp peers in eos_designs.

How to test
See molecule scenario evpn_underlay_rfc5549_overlay_ebgp and testing performed by @mpergament .
Checklist:

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have updated molecule CI testing accordingly
[x] All new and existing tests passed (pre-commit, make linting and make sanity-lint).

Waiting for a commit to fix ip routing ipv6 interfaces documentation


[Feature Request] Popup when X commits behind on open

Hi,
Thank you for this amazing extensions, we are using it a lot here in my company.
We work in team usually and due to fast switching from a project to another, sometimes we start to write code without pulling the latest commits.
Actually, we should check the GitLens Explorer, where i can easily see if there are commits behind in local branch:

...but, a really nice to have feature would be a UI Notification on workplace open and only if the current local branch repo has commits behind the remote one...and a button ("Yes"/"No", or "Pull"...or whatever) to execute the git pull command.
A flag to enable this check and the notification should be enough.
What do you think about it?

I think this request would be best served by the built-in vscode git extension. Since it would go along with the status bar indication of the current branch's sync status. So I would recommend opening a feature request on the vscode repo. Thanks!


Streamline workflows.Rmd

Streamline workflows.Rmd. Aims:

Make maximally friendly to first time users
Make code maximally elegant and succinct
Present a small selection of visually appealing, self-explanatory plots

Tasks:

[ ] Simplify code to transform data and generate plots
[ ] Make plots visually appealing and self-explanatory
[ ] Walk through a simple example of finding & filtering data to plot
[ ] Add limitations section (here or elsewhere)

Related: https://github.com/elpaco-escience/talkr/issues/111

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Example of an issue that needs fixing: quality_plot() output in vignette doesn't look good, should be less high, the three plots should be square-shaped.


You can set your character's age to a negative number during creation

It's probably a LineEdit not a SpinBox

Fixed by #1836


"Getting code actions" pop-up doesn't specify which extension is slow

VSCode Version: 1.45.0-insider c12bd56a8886f31e353a45f5846f0a35a52f908e x64
Is there a way to make it clear to the user which extension is causing the slow saves? We've been getting a lot of bug reports in https://github.com/microsoft/vscode-go about this, but in a majority of cases, users have found that another extension they've installed is actually causing the problem. One user debugged and discovered that the Spell Right extension was actually causing the issue, and when I tried to reproduce it, I saw the following pop up:

From this image, it's not obvious that Spell Right is the issue, but the problem disappears once it's disabled.

We don't know because everything is still in-flight. We cannot know that A waits for B or that B waits for A because nothing has finished yet and because this is a progress notification. However, the extension host log files will reveal which provider took how long.

I have pushed a change that makes sure extension names are only shown once, that's all we can do. To get to the number after things have settled, use "F1 > Log Level > Trace" and then "F1 > Show Log > Extension Host Log"


Make chart scrollable vs movable with cursor?

Currently your able to use the cursor to move the graph in different locations. Was wondering if its possible to make the graph scrollable vs movable with the cursor?
On a separate note: how would I turn off the graph from being able to move with the cursor for graphs that fit in the boundaries of the screen?

Was wondering if its possible to make the graph scrollable vs movable with the cursor

Do you mean make the graph scrollable with the scroll wheel (instead of zoomable)? If so, you can override the default zoom handler to pan. I can share code if that's what you mean.

@schindld Yes I believe thats what i mean!
Instead of the zoomable default feature I would love for it to scroll instead. This would need to support non macOS laptops as well tho, would a scrollbar end up at the bottom and sides?

@marcellino-ornelas Here's how I did something similar (I still wanted to the zoom-on-scroll feature, but wanted to pan-on-scroll if shift or ctrl were held):
let zoom; // cache for the current zoom transform parameters, x, y, and k
// Custom zoom handler to allow for panning with the mousewheel (shift scroll to pan horizontally, and ctrl scroll to pan vertically)
const zoomHandler = (e) => {
	const transform = e.transform; // new transform from zoom event
	// If the ctrl key was held, pan vertically (y) instead of zooming (k)
	if (e.sourceEvent.type == 'wheel' && e.sourceEvent.ctrlKey) {
		transform.k > zoom.k ? (zoom.y += 20 / zoom.k) : (zoom.y -= 20 / zoom.k);
		transform.k = zoom.k;
		transform.x = zoom.x;
		transform.y = zoom.y;
	// If the shift key was held, pan horizontally (x) instead of zooming (k)
	} else if (e.sourceEvent.type == 'wheel' && e.sourceEvent.shiftKey) {
		transform.k > zoom.k ? (zoom.x += 20 / zoom.k) : (zoom.x -= 20 / zoom.k);
		transform.k = zoom.k;
		transform.x = zoom.x;
		transform.y = zoom.y;
	}
	// cache this transform for next time the event occurs
	zoom = transform;
	// If no key was held, just let the transform happen without modification
	return d3.select('.chart').attr('transform', transform);
};

Then somewhere after the call to render(), attach the zoom handler function to the rendered svg:
// Attach our custom zoom event handler to add horizontal/vertical panning with the scroll wheel and modifier keys
d3.select('svg').call(d3.zoom().on('zoom', zoomHandler));

And we also have to initialize zoom with the current values of the chart's zoomTransform (x, y, and k values), so put this code right after the previous line that attaches the zoomHandler:
// Using a timeout here because the render and fit functions have an animation that has to finish before we get the real
// transform parameters from d3.zoomTransform
setTimeout(() => {
	zoom = d3.zoomTransform(d3.select('.chart').node()); // get a copy of the default zoom parameters x, y, and k
}, chart.getChartState().duration + 10);

To get the behavior you want, you can change the zoom handler to something like this:
const zoomHandler = (e) => {
	const transform = e.transform; // new transform from zoom event
	// If the shift key was held, pan horizontally (x) instead of zooming (k)
	if (e.sourceEvent.type == 'wheel' && e.sourceEvent.shiftKey) {
		transform.k > zoom.k ? (zoom.x += 20 / zoom.k) : (zoom.x -= 20 / zoom.k);
		transform.k = zoom.k;
		transform.x = zoom.x;
		transform.y = zoom.y;
	// If the scroll wheel is scrolled without a modifier key, scroll vertically (y) instead of zooming (k)
	} else if (e.sourceEvent.type === 'wheel') {
		transform.k > zoom.k ? (zoom.y += 20 / zoom.k) : (zoom.y -= 20 / zoom.k);
		transform.k = zoom.k;
		transform.x = zoom.x;
		transform.y = zoom.y;
	}
	// cache this transform for next time the event occurs
	zoom = transform;
	// If no key was held, just let the transform happen without modification
	return d3.select('.chart').attr('transform', transform);
};

But it's missing logic to zoom back out, so you'll have to add it yourself....Maybe add an else if for ctrl+scroll, or use a button to trigger it.

@marcellino-ornelas Here's how I did something similar (I still wanted the zoom-on-scroll feature, but wanted to pan-on-scroll if shift or ctrl were held):
// Custom zoom handler to allow for panning with the mousewheel (shift scroll to pan horizontally, and ctrl scroll to pan vertically)
const zoomHandler = (e) => {
	const zoom = chart.getChartState().lastTransform; // previous transform before zoom event
	const transform = e.transform; // new transform from zoom event
	// If the ctrl key was held, pan vertically (y) instead of zooming (k)
	if (e.sourceEvent.type === 'wheel' && e.sourceEvent.ctrlKey) {
		transform.k > zoom.k ? (zoom.y += 20) : (zoom.y -= 20);
		transform.k = zoom.k;
		transform.x = zoom.x;
		transform.y = zoom.y;
		// If the shift key was held, pan horizontally (x) instead of zooming (k)
	} else if (e.sourceEvent.type === 'wheel' && e.sourceEvent.shiftKey) {
		transform.k > zoom.k ? (zoom.x += 20) : (zoom.x -= 20);
		transform.k = zoom.k;
		transform.x = zoom.x;
		transform.y = zoom.y;
	}
	// cache this transform for next time the event occurs
	chart.getChartState().lastTransform = transform;
	// If no key was held, just let the transform happen without modification
	return d3.select('.chart').attr('transform', transform);
};

Then somewhere after the call to render(), attach the zoom handler function to the rendered svg:
// Attach our custom zoom event handler to add horizontal/vertical panning with the scroll wheel and modifier keys
d3.select('svg').call(d3.zoom().on('zoom', zoomHandler));

To get the behavior you want, you can change the zoom handler to something like this:
const zoomHandler = (e) => {
	const zoom = chart.getChartState().lastTransform; // previous transform before zoom event
	const transform = e.transform; // new transform from zoom event
	// If the shift key was held, pan horizontally (x) instead of zooming (k)
	if (e.sourceEvent.type === 'wheel' && e.sourceEvent.shiftKey) {
		transform.k > zoom.k ? (zoom.x += 20) : (zoom.x -= 20);
		transform.k = zoom.k;
		transform.x = zoom.x;
		transform.y = zoom.y;
	// If the scroll wheel is scrolled without a modifier key, scroll vertically (y) instead of zooming (k)
	} else if (e.sourceEvent.type === 'wheel') {
		transform.k > zoom.k ? (zoom.y += 20) : (zoom.y -= 20);
		transform.k = zoom.k;
		transform.x = zoom.x;
		transform.y = zoom.y;
	}
	// cache this transform for next time the event occurs
	chart.getChartState().lastTransform = transform;
	// If no key was held or it was some other event like clicking, just let the transform happen without modification
	return d3.select('.chart').attr('transform', transform);
};

But it's missing logic to zoom back out, so you'll have to add it yourself....Maybe add an else if for ctrl+scroll, or use a button to trigger it.

When I use this code in angular, zoomHandler is not receiving event object, it receives string 'svg-chart-container' and hence there are no properties. Any ideas how we could get this to work in angular.


shjs utility will also infer the extension of filenames ending in a '.'

shjs can now infer the file extension if the file ends in .. So the following code now works:
$ cat input.js
require('shelljs/global');
echo('Hello world');

$ shjs input.js
Hello world

$ shjs input
Hello world

$ shjs input. # this was previously an error
Hello world

This is useful in the case of tab completion. If there's another file (say, input.sh), then tab completion will result in "input.". This is an often enough scenario that, if we're going to do file extension inference at all, we should probably do it here. Since inference is already supported, I see no reason to not support it in this scenario as well.
This fixes #278

Hmm... I don't really think that this is a good idea, it would be a little confusing.

I think the file extension inference is a little confusing in general. This would just make that already-existing-feature more useful (in my opinion). It's not a big concern though, so I'm fine if it doesn't get merged.

Hmm... Anyone else have any opinions on this?

Closing this, since there doesn't seem to be much interest (and it wasn't a big concern of mine anyway)


Add FormModel.allFields getter

Returns FieldModel[] - convenient and jsdoc typed way to get a reference to all owned FieldModels.
Useful on its own in a case I have, but might also help to clarify that FormModel.fields is an object (despite ctor taking them as an []), simply by providing a contrasting public getter.

Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[x] Caught up with develop branch as of last change.
[x] Added CHANGELOG entry, or determined not required.
[x] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[x] Updated doc comments / prop-types, or determined not required.
[x] Reviewed and tested on Mobile, or determined not required.
[x] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

I think I would prefer fieldList, as allFields somehow implies that the
fields getter is just providing some filtered sub-set.
On Mon, Mar 30, 2020 at 5:58 AM Anselm McClain<EMAIL_ADDRESS>wrote:

@amcclain commented on this pull request.
In cmp/form/FormModel.js
https://github.com/xh/hoist-react/pull/1802#discussion_r400068487:

@@ -44,6 +43,9 @@ export class FormModel {
/** @member {Object} - container object for FieldModel instances, keyed by field name. */
@observable.ref fields = {};

/** @return {FieldModel[]} - all FieldModel instances, as an array. */
get allFields() {return values(this.fields)}

Open of course to other suggestions on the name here, if you think the
overall addition is worth it. E.g. fieldList?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/xh/hoist-react/pull/1802#pullrequestreview-383701249,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARTL2ML5P7OKFYHO6SDV6LRKBUMXANCNFSM4LWOI7XQ
.

Great, thank you for merging Lee and agree re. the name - good to be as clear as possible!


The save-state command is deprecated

https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Is this still an issue?

Closed due to issue been solved


added pagination

Description
(Write your answer here.)
Checklist

[ ] I am making a proper pull request, not spam.
[ ] I've checked the issue list before deciding what to submit.

Related Issues or Pull Requests
(Write your answer here.)
Add relevant screenshot or video (if any)
(Add here)

@wasimreja sir but this is unfair for me as you assigned this task to me and i have also made a PR for this

@wasimreja
I have updated it. Please review.

@Awesomeasma pagination is not working and the button is overlapping. fix this. add padding to the bottom. you have put .vscode file to css. delete this.

I apologize sir, I have updated the css & other components, I am fixing the functionality of the pagination buttons, I'll get it done, soon.

@Awesomeasma pagination is not working and the button is overlapping. fix this. add padding to the bottom. you have put .vscode file to css. delete this.

Please check once..

@Awesomeasma fix the functionality of the pagination. your branch has conflicts. resolve this. rest is okay.

@Awesomeasma fix the functionality of the pagination. your branch has conflicts. resolve this. rest is okay.

Please tell me how do i fix it, I am trying to do so, but i am not able to.

@Awesomeasma fix the functionality of the pagination. your branch has conflicts. resolve this. rest is okay.

Please tell me how do i fix it, I am trying to do so, but i am not able to.

dm me on discord.


#1073: Remove guava

Per #1073

Remove guava as a test dependency

@baudoliver7 Forgot to remove todo, please take a look again.

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 9min)

@0crat status

@0crat status

@0crat status

@0crat status


Create page for listing videos

Our public videos are starting to come online.

Dedicate a page to listing them and describing what they are about so people can find them.

All our videos are hosted here: https://enable.cx.sap.com/tag/tagid/spartacus
but appear in random order or order in which they were added (most recent first).

Created PR https://github.com/SAP/cloud-commerce-spartacus-storefront-docs/pull/18

Can now be viewed here: https://sap.github.io/cloud-commerce-spartacus-storefront-docs/spartacus-videos/


question: How to set the callback and redirect URI?

This is probably already answered or at least discussed in https://github.com/greenpau/caddy-auth-portal/issues/193 however, the issues are no longer visible.
I'd like to change the callback URL in this plugin to avoid changing it in the provider as in enterprises this is often a process which takes time and approvals to get through.
Example:
Instead of /auth/oauth2/example/authorization-code-callback just /callback
Is this possible or does it need to be implemented?
There are two parts that would need to cooperate here:
The redirect_uri parameter when redirecting to the provider as well as the route in Caddy to listen on /callback (or any other custom URL).

@simaotwx , thank you for the question! 👍 it needs to be implemented.

Thank you for the quick respond. Looking forward to it!

I'm running into this as well. My use-case is when running caddy behind another reverse-proxy for and the "localhost" of the caddy binding is being injected as the redirect_uri, rather than the indented public uri. I've tried various trick and look through the code to see if there is a workaround via Host headers; but no luck yet.

I was also getting the Google OAuth2 "request_uri mismatch" error due to the request_uri passing http instead of https.
I'm noting the solution that worked for me, aas suggested by @tomberek above.  Simply adding the 'X-Forwarded-Proto: https' header on my upstream reverse proxy, which happens to be opnsense, made everything work.


Driver doesnt support Windows 10 Creators Update

The driver starts with the status 0xC00000BB. Is there any information about the new SSDT?

I'll update driver when ntoskrnl symbols become available.

https://download.microsoft.com/download/6/9/C/69C86A1F-C8E9-4F28-B6FC-9FA2BCE98BC0/Windows_Rs2.15063.0.170317-1834.x64FRE.Symbols.msi
15063.0 - i dont think many chance in .11

Okay, i parsed it from windbg. If you need tables or any other data - you can write to me
pData->KExecOpt = 0x1BF;
pData->Protection = 0x6CA;
pData->ObjTable = 0x418;
pData->VadRoot = 0x628;
pData->NtProtectIndex = 0x50;
pData->NtCreateThdIndex = 0xB9;
pData->NtTermThdIndex = 0x53;
pData->PrevMode = 0x232;
pData->ExitStatus = 0x6F8;

thankyou


graph issue with small Y numbers

Hi,
I'm facing an issue with drawing the line chart graph with small number in Y axis (less than 90), I've described the issue in this Plunker
I'm stuck with this for couple of days now :-(
I'll be so thankful if you could help me,
thanks in advance,
sRockx

The only thing you need is to convert y-values to numbers:
y: function(d){ return +d.y; }

That worked, THANKS a lot :)


Forward class attribute to table components

Ran into this while trying to hide table columns on a small screen. It's possible to hide <td> elements but it didn't
work for <th>. This patch makes sure to forward the class assign to every component in PetalComponenets.Table.

Thanks for that. Merged.


Backing Services

I want to deploy a application with backing services support such as Redis, logstash, RabbitMQ and SMTP. I managed to install Redis by following instruction in "https://gist.github.com/lmars/fca0f18b4ecd507fb39a". Is there a standard way to install rest of backing services in flynn environment.

@sukitha the approach in the linked gist is currently the standard way to deploy non-buildpack based services using Docker images from a Docker registry.
For reference, here are URIs to Docker images for some of the services you mentioned:
Logstash 1.4.2:
https://registry.hub.docker.com?name=logstash&id=98a09aa3e8b23e0edd447287feae70c833a8cc10253fa179cb7594c847482603

RabbitMQ 3.5.0:
https://registry.hub.docker.com?name=rabbitmq&id=571751cd6dddb556d8d256f7f6a652595974e49bc2ab0c0de89765d5c220a82a

We know this isn't a simple way to deploy these services, and we have plans to improve the workflow for deploying generic images in the future (see for example #1085).
In the long term, we aim to support these services out-of-the-box (e.g. flynn resource add rabbitmq).


chore: update axios peer dependency to >=0.26.0

Think it is time to bump Axios and also allow more versions.

Hi @palmithor !
That's a good idea, however as axis is still 0.x I'd prefer to keep the semver range to ^0.26.0 to avoid breaking changes from their side.
Can you do that change please ?

Hey @sybers .. ^0.26.0 or ^0.27.0?

Huh I guess it will be easier to maintain with your semver range, otherwise I'll have to update the version too frequently. I'll merge your PR as is. Thanks :)

Hey @sybers , any plans to release a new version with this update? We have peer dependency issue and it'd be very nice to get this in.


Codecov setup

@tisnik Your image is available in the registry: docker pull MISSING_REGISTRY_NAME/MISSING_IMAGE_NAME:SNAPSHOT-PR-20


Search by account on Recommendations table

Context
When looking to make changes for carbon reduction, users will likely want to target certain accounts. To do that, we would like to allow them to search for accounts.
Can we manage multiple account search?
^ As a stop gap solution we will add a quick search on the table that only handles one value. In the future, a solution might be to add a search to our account filter which will solve for ease of use and for multiselect.
A/C's

[x] When I view the recommendations table, I see a search bar below the 'Recommendations' title
[x] When I enter a correct account name in the table, I see all results for that account
[x] When I enter a correct account id in the table, I see all results for that account
[x] When I begin to type in the search bar, it filters out results as each letter is added

[x] If it comes for free, support search on other attributes

[kickback] Noticed certain values match on results even though they do not appear in the table.
We think it may be because the search happens before rounding


Cardano explorer -> not showing key deposit refunds

Summary
The Cardano explorer does not show refunds, in particular, when you deregister a stake key or stake pool, the deposit for that registration is refunded. So upon initial analysis of inputs and outputs, some transactions look unbalanced.
Steps to reproduce
De-register a stake pool key and check the cardano-explorer
Expected results
All key deposit refunds received from staking should be seen and included in the UTXO distribution and marked accordingly, a field representing in the transaction structure, something to verify that it’s a legal transaction.
Actual results
At the moment there is no indication of any refund transaction or otherwise. Instead, we only see a balance increase.
Conclusion
The explorer should also report refunds.

Duplicate of #353


launch.json does not pickup a seondary launchConfigurationId from Properties/launchSettings.JSON

Trying to debug an application using different environment variables for the use use of appSettings.env.json i.e.:
"environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development"
}

does not pick up a secondary profile. So I can have a Development env and a UAT env but it only picks up the first one when I hit debug. Same thing happens on Compounds:
launch.json sample:
{
"version": "0.2.0",
    "configurations": [
      {
        "name": "MyAppDev",
        "type": "dotnet",
        "request": "launch",
        "projectPath": "${workspaceFolder}/MyApp/MyApp.csproj",
        "launchConfigurationId": "TargetFramework=;MyAppDev"
      },
      {
        "name": "MyAppUAT",
        "type": "dotnet",
        "request": "launch",
        "projectPath": "${workspaceFolder}/MyApp/MyApp.csproj",
        "launchConfigurationId": "TargetFramework=;MyAppUAT"
      },
]
}

LaunchSettings.Json sample:
{
  "$schema": "http://json.schemastore.org/launchsettings.json",
  "profiles": {
    "MyAppDev": {
      "commandName": "Project",
      "launchBrowser": true,
      "launchUrl": "clients",
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development",
      },
      "applicationUrl": "https://localhost:44334"
    }
    "MyAppUAT": {
      "commandName": "Project",
      "launchBrowser": true,
      "launchUrl": "clients",
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "UAT",
      },
      "applicationUrl": "https://localhost:44334"
    }
  }
}

If the CSharp: Report an issue command doesn't appear, make sure that you have C# extension version 1.17.0 or newer installed.
Environment data
VS Code version: 1.93.1 (Universal)
C# Extension version: current latest and Pre-release versions
Steps to reproduce

go to Debug
select profile 1, run, it loads c# app on development.
select profile 2, run, it loads c# app still on development instead of UAT

Expected  behavior
the UI will pick the correct profile to launch
Additional context
This was working on a few versions ago, but I didnt had to use vscode on this project for a while until recently that realized it was not picking up my other environments.

@patoJamriska Do you have C# Dev Kit installed?
launchConfigurationId was not intended to really be saved in a launch.json but was supposed to be used by the dynamic configuration provider which is used internally by the resolver in C# Dev Kit.
The dotnet debug type only supports using projectPath if you are using launch.json

@WardenGnaw I had a similar issue to OP because the documentation isn't very clear on this. Is launchSettingsProfile property on a launch configuration in .vscode/launch.json the expected way to provide which launchSettings profile to use?
When I tried (this was ~2mo back at this point) it just ignored everything and would always pick the first profile in launchSettings.json anyways. This was true of manually configured launch profiles or the dynamic configuration.
I also found applicationUrls of the selected profile is ignored; workaround was setting ASPNETCORE_URLS as an env variable.

@patoJamriska Do you have C# Dev Kit installed?
launchConfigurationId was not intended to really be saved in a launch.json but was supposed to be used by the dynamic configuration provider which is used internally by the resolver in C# Dev Kit.
The dotnet debug type only supports using projectPath if you are using launch.json

Yes, I am using the C# developer extension

@WardenGnaw I had a similar issue to @patoJamriska because the documentation isn't very clear on this. Is launchSettingsProfile property on a launch configuration in .vscode/launch.json the expected way to provide which launchSettings profile to use?
When I tried (this was ~2mo back at this point) it just ignored everything and would always pick the first profile in launchSettings.json anyways. This was true of manually configured launch profiles or the dynamic configuration.
I also found applicationUrls of the selected profile is ignored; workaround was setting ASPNETCORE_URLS as an env variable.
Anyways about the documentation

It should make clear in which file launchSettingsProfile should be configured
It would be helpful if the     "launchSettingsProfile": "ProfileNameGoesHere" example showed a few lines above/below.
If launchSettingsProfile is a valid option for launch.json, it should appear in the launch profile schema/autocomplete suggestions (today it does not)
If launchConfigurationId is internal, it should be removed from autocomplete suggestions and documented as such so users don't try to manually configure what the VSCode generates for them and have nothing happen as a result.

applicationUrls actually instead I use the launchUrl which is also in the properties/launchSettings. And I agree it is not clear that it is dependent on this file but it looks like the plugin is definetly trying to emulate how Visual studio works in that regards, but it is incomplete.

I have still being doing research on this Because of other issues arising on the work I am doing, and run into this on the MS documentation. https://learn.microsoft.com/en-us/aspnet/core/fundamentals/environments?view=aspnetcore-8.0#development-and-launchsettingsjson
This section actually shows how to use the coreclr to pass environment variables at the launch.json level, but obviosuly that is not an option since we are using the c# plugin and the launch is "type": "dotnet". Not sure if there has been anyone looking into this besides what has been shared by now?

Did something changed or update?
I had problem that launching any configuration in launch.json leads to loading first config from launchSettings.json which screw my environment variables, and I got here, but projectPath and launchConfigurationId are not allowed as properties in configuration (anymore?)
I check docs

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/environments?view=aspnetcore-8.0#development-and-launchsettingsjson

and setting launchSettingsProfile property in launch.json config solved my issue and it's even better that config is shared, so is this issue resolved?

Did something changed or update? I had problem that launching any configuration in launch.json leads to loading first config from launchSettings.json which screw my environment variables, and I got here, but projectPath and launchConfigurationId are not allowed as properties in configuration (anymore?)
I check docs

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/environments?view=aspnetcore-8.0#development-and-launchsettingsjson

and setting launchSettingsProfile property in launch.json config solved my issue and it's even better that config is shared, so is this issue resolved?

Can you show us an example of how you have your files for this? I just tested myself and the same exact behaviour is still happening. I have to coment out the other profiles to be able to launch the one I need.

@patoJamriska
this is my launchSettings.json from VS 2022

And that's VS Code launch.json

As you see I define name of profile in launchSettingsProfile and it catches environment variables from there (thats all I needed personally)

@patoJamriska this is my launchSettings.json from VS 2022  And that's VS Code launch.json
As you see I define name of profile in launchSettingsProfile and it catches environment variables from there (thats all I needed personally)

Correct, but you are using the "type": "coreclr", in your launch.json. If you use the documented version of "type": "dotnet", this is where it is not working and only picks one configuration from launchSettings.json.


Improve unit test coverage a bit

@tisnik Your image is available in the registry: docker pull registry.devshift.net/MISSING_IMAGE_NAME:SNAPSHOT-PR-13


Fixed QUnit tests -  api select and content-editable api-actions (part of #471)

\cc @AlexanderMoskovkin, @helen-dikareva

@testcafe-build-bot \retest

@VasilyStrelyaev

also, we should run the tests for 4-5 times to ensure we've fixed the problem

/r-

You've created a feature-branch in the main repo, not in your fork. As a result we have some unexpected testing behavior. So, I close the PR, please create it again from your fork


Instead of stats_to_csv, use pandas for csv export

Per @ozak s comment on #34

This is easy enough to do manually with pandas, no need to add an abstraction or dependencies to rasterstats.


[Issue]: .NET nightly NuGet feeds do not appear to provide daily builds

Describe the issue
I have set up my NuGet.config source for "https://www.myget.org/F/agentchat/api/v3/index.json" and the latest version is 0.0.15-nightly-9735721869 Published June 30, 2024.
Today is July 11, 2024.
The release before that was published on June 10, 2024.
What other approaches could I use to work with the latest builds of .NET AutoGen?
In addition, when I tried to use the GitHub feed https://nuget.pkg.github.com/microsoft/index.json when installing the AutoGen package, I would get an error for some of the AutoGen dependency packages "not found".
Steps to reproduce
Configure a NuGet.config or source with one of the feeds.
Review the metadata for the AutoGen package.
Screenshots and logs

Additional Information
No response

pushed


Add basic CI pipeline

Implement a basic Continuous Integration pipeline using Github Actions.

[x] Make basic configuration file for the project
[x] Install package dependencies stage
[x] Run tests stage
[X] ~Build stage~ Try Compile
[ ] ~Update pipeline badge in README~ moved to #10

Closed by #8


The padding around the box looks odd

v131.0.3
I'm not a dev, but just tried including this in my userChrome.css file. I am also having Firefox-UI-Fix, so unsure if there is some kind of clash.

Hi! 😊
I notice your close button has been moved to the the left of the other controls.
Refined findbar adds a padding-inline-start to the findbar, but not a padding-inline–end, because the close button has it's own margin that spaces it out. The fix would probably be to remove the individual margins from immediate children of the findbar and space them out using gap, like how the controls are spaced out already. I'm unable to work on & test this immediately, but will over the next couple weeks.
For an interim fix, you should be able to add a padding-inline-end: math.div($space-unit, 3); after the -start rule and copy it over again 🤔. Here's a playground link; let me know if it works? Thanks!

It still looks the same to me, actually. I do want to highlight that I'm not a developer and solely copied that code. Either way, thank you for your help, mate.

I'm unable to work on & test this immediately, but will over the next couple weeks.
I'm glad you responded and tried helping me with an interim fix.

Thank you for the support @ravindUwU.
This solved my issue. I just wanted to let you know that the close button is on the left of other controls, even after the update. I'm unsure if that was the intended goal.
I'm also using Firefox-UI-Fix.

Yup! The close button on the left the other controls seems to be part of Firefox-UI-Fix 🤔, whereas the fix for this issue simply "resets" the horizontal spacing in between & on either side of those controls, and they seem to work together just fine.
Thanks for confirming! 😄


Fix #2578: suppress HTTP response header X-Application-Context (master)

see #2578

Why was this closed?

huh? I did not close it either

Argh, force push closes it...

It did not merge?

Sorry for the trouble, a new PR is submitted


Embedding Audio to Nodes - Development Merge

Hello! This is to follow-up on this PR: https://github.com/adityamukho/hivemind/pull/21.
As instructed (https://github.com/adityamukho/hivemind/pull/21#issuecomment-987632589), I implemented the suggestions and rebased my commits against the development branch in my fork.

Merged. Please see hivemind-git-development-adityamukho.vercel.app for changes introduced by this PR. Will be merged to master shortly.
Thank you for your contribution!

Merge to master.


Font don't support Japanese characters.

This is little screenshot of my nickname on profile. There is a chance to add support for this characters?

Just use your own font.


Schema Query/Mutation Description Ignored

Currently these descriptions of the queryType and mutationType seem to be completely ignored during documentation generation:
{
    "data": {
        "__schema": {
            "queryType": {
                "name": "ApiRequestQuery",
                "description": "Description of query endpoint here.",
                "kind": "OBJECT"
            },
            "mutationType": {
                "name": "ApiRequestMutation",
                "description": "Description of mutation endpoint here.",
                "kind": "OBJECT"
            },
[...]

It would be great if these descriptions could be included below the Queries and Mutations headlines in the documentation.

Fixed in 0.9.4

Much appreciated, @newhouse, works great now! :-)