Value error when [bug report] uses [autocomplete] to clear the input content

Element UI version
2.13.1
OS/Browsers version
70.0.3538.102
Vue version
3.0.0-beta.9
Reproduction Link
https://codepen.io/rsenhuang/pen/JjYMgOx?editable=true%3Dhttps%3A%2F%2Felement.eleme.cn%2F
Steps to reproduce
https://codepen.io/rsenhuang/pen/JjYMgOx?editable=true%3Dhttps%3A%2F%2Felement.eleme.cn%2F
What is Expected?
there should not have any error when you clear what you inputed in autocomple
What is actually happening?
throw error: Cannot read property 'value' of undefined, which causes by inner input module emit change event with empty string but the autocomple module treats arguments[0] as an Object like 'event.target.value'.

Duplicate of #19382


fix: #1530 support discriminator with multiple mappings of same schema

This is an improved version of @jKiler's #1534. Credit to them for getting this started.
My main addition is getting the codegen for FromFoo and MergeFoo to work better in this situation.

thanks a lot! that PR supersedes #1745 and works better 👍

Maintainers / @mgabeler-lee-6rs what is the plan for this PR?

I've been using this PR in my production app for some time now with good results. It's not perfect, it's vulnerable to GIGO if you have an invalid OAS spec, but no worse than the released code.
Contribution guidelines explicitly request not tagging maintainers directly :man_shrugging:


Document how to build using Cloud 9

Customer requested instructions on how to build the solution using Cloud9. Include region-specific instructions.

This seems out-of-scope. Closing for now.


Fix http authentication with proxy

*) fixes #4195
*) resolve discrepancies between Hop documentation and behaviour w.r.t. empty/null usernames and password in case of HTTP basic auth

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Run mvn clean install apache-rat:check to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If you have a group of commits related to the same change, please squash your commits into one and force push your branch using git rebase -i.
[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable.

To make clear that you license your contribution under the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

[x] I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004
[ ] In any other case, please file an Apache Individual Contributor License Agreement.

@hansva do you have any questions or wishes for changes w.r.t. this pull request?

@rramthun It looks good on first sight, just haven't had the time to test yet. Will get to it shortly.

Thanks for the work @rramthun !


Device goes to sleep, Meeting interrupted

Describe the bug
If I dont touch my phone every 2 Minutes the screen saver causes the meeting to be interrupted
Android 11
Samsung S10
Samsung Smart Cover
Chrome Browser (latest)
Andriid Web View latest
BBB server could be supplied later if needed
To Reproduce
Steps to reproduce the behavior:
Set Screen Timeout to 5 Min on device settings
start meeting
talk for 5 min and dont use the phones touch screen or buttons
if you have smart cover, close the cover
after 5 min latest meeting gets interrupted
we would need to reconnect to the meeting from entering tbe URL again.
Expected behavior
Continue the meeting until end of meeting without breaking the connection by OS (deep) sleep
Thank you
I am happy to help testing

https://forum.developer.samsung.com/t/unable-to-add-app-to-never-sleeping-apps-list/11663/16?u=ada1591182046

Hi,
Thanks for reporting this! Currently all of the developers of this app are working on their respective thesis. We will definitely get back to it after those is done and rewrite the app using the newest version of flutter as well.
We will keep this issue in mind during the rewrite!


Refactor Rocchio to save unnecessary neg feedback

Add a param to Rocchio reranker to avoid unnecessary neg feedback
Change file name of Rocchio neg feedback from rocchio* to rocchio-neg to resolve the 'trec_eval.get_results: Cannot read results file' error

Codecov Report

Merging #1906 (94cedd2) into master (94bbb44) will decrease coverage by 0.04%.
The diff coverage is 33.33%.

:exclamation: Current head 94cedd2 differs from pull request most recent head 5510d37. Consider uploading reports for the commit 5510d37 to get more accurate results

@@             Coverage Diff              @@
##             master    #1906      +/-   ##
============================================
- Coverage     58.57%   58.52%   -0.05%
+ Complexity     1080     1079       -1
============================================
  Files           180      180
  Lines         10379    10382       +3
  Branches       1428     1429       +1
============================================
- Hits           6079     6076       -3
- Misses         3782     3786       +4
- Partials        518      520       +2

Impacted Files
Coverage Δ

...main/java/io/anserini/search/SearchCollection.java
41.88% <0.00%> (ø)

...n/java/io/anserini/rerank/lib/RocchioReranker.java
57.79% <30.00%> (-4.47%)
:arrow_down:

...c/main/java/io/anserini/search/SimpleSearcher.java
63.92% <100.00%> (ø)

Continue to review full report at Codecov.

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


TransportCachingIT fills up disk with infinite loop of log messages

Saw this in Jenkins for 2.0. TransportCachingIT fills up the disk (first it filled up a 32GB disk, then when I moved the output to a 240GB disk, it filled that up) with tons of WARNINGs:
2018-08-13 17:44:37,310 [test.TransportCachingIT] WARN : Failed to obtain transport to []
2018-08-13 17:44:37,310 [test.TransportCachingIT] WARN : Failed to obtain transport to []
2018-08-13 17:44:37,310 [test.TransportCachingIT] WARN : Failed to obtain transport to []
2018-08-13 17:44:37,310 [test.TransportCachingIT] WARN : Failed to obtain transport to []

I'm having a hard time reproducing this when running the test by itself (can't reproduce locally at all). However, I'd like to keep the issue open until I'm sure it's not a problem with our test code.

I saw this again and it filled up a 240GB partition with a 96GB file repeating that same message. I've attempted to capture some of the logs to figure out what the server processes were doing at the time. At the very least, this test needs a timeout so it doesn't run forever... and maybe we need to fix the log4j configuration so it collapses repeated messages.

I will get working on this.


Please explain the reason for disabling orderId in IdentityMgtEventListener

In [1] there is a statement to disable orderId. But the reason for the disabling is not given. Please provide an explanation to why the disabling is needed
[1] https://docs.wso2.com/display/IS540/Username+Recovery

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


TypeError: HelloSignSDK.SignatureRequestApi is not a constructor

import * as HelloSignSDK from "hellosign-sdk";

const api = new HelloSignSDK.SignatureRequestApi();

// Configure HTTP basic authorization: api_key
api.username = "YOUR_API_KEY";

// or, configure Bearer (JWT) authorization: oauth2
// $config->setAccessToken("YOUR_ACCESS_TOKEN");

const signatureRequestId = "fa5c8a0b0f492d768749333ad6fcc214c111e967";

const result = api.signatureRequestFiles(signatureRequestId);
result.then(response => {
  console.log(response.body);
}).catch(error => {
  console.log("Exception when calling HelloSign API:");
  console.log(error.body);
});

I am copying the code from the Hellosign docs exactly. Node v18.8.0.
And getting this error:
TypeError: HelloSignSDK.SignatureRequestApi is not a constructor
    at file:///home/ronald/Projects/hellosign-microservice/test.js:3:13
    at ModuleJob.run (internal/modules/esm/module_job.js:183:25)
    at async Loader.import (internal/modules/esm/loader.js:178:24)
    at async Object.loadESM (internal/process/esm_loader.js:68:5)
    at async handleMainPromise (internal/modules/run_main.js:59:12)

Same problem here, none of the examples work

I ended up having to move to a different e-signature company unfortunately. @JS1209

Can I ask which company? And how are your experiences with the new company? Tech support is horrible here as well… planned a meeting twice, only the salesperson showed up and techt support guy just points me to dev support via email :P

Howdy!
I just tested this locally in an empty directory:
package.json:
{
  "name": "npm-test",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "type": "module",
  "dependencies": {
    "hellosign-sdk": "^6.0.0-beta"
  }
}

test.js:
import * as HelloSignSDK from "hellosign-sdk";

const api = new HelloSignSDK.SignatureRequestApi();

// Configure HTTP basic authorization: api_key
api.username = "YOUR_API_KEY";

// or, configure Bearer (JWT) authorization: oauth2
// $config->setAccessToken("YOUR_ACCESS_TOKEN");

const signatureRequestId = "fa5c8a0b0f492d768749333ad6fcc214c111e967";

const result = api.signatureRequestFiles(signatureRequestId);
result.then(response => {
  console.log(response.body);
}).catch(error => {
  console.log("Exception when calling HelloSign API:");
  console.log(error.body);
});

$ node -v
v16.13.2

$ node test.js
Exception when calling HelloSign API:
_ErrorResponse {
  error: _ErrorResponseError {
    errorMsg: 'Unauthorized api key',
    errorName: 'unauthorized',
    errorPath: undefined
  }
}

Note that this version of the SDK is still marked as Beta and not yet suitable for production usage (although it is very close!).

Hi @ronaldlong46, @JS1209
The samples in the docs are for the new beta SDK. The errors you're running into could be due to using the legacy Node SDK, but referencing the beta.
Use this to get the beta:
npm install<EMAIL_ADDRESS>Hope this helps!

Hi!
Sorry about the samples and differences in SDK versions. I manage the docs and should have made it more clear that the samples are using the beta SDKs. Thanks for posting the issue, though! I'm working on a PR for the docs right now to address that. Additionally, our new SDKs should be out of beta soon!
Closing this issue but please re open as needed.

Hi @TaylorKrusen Thanks for the reply! Are the new SDKs out of beta?


Got Error dependency PMAlertController is not used in any concrete target with pod 1.0.0

Why did I get this error when running pod install command?
The dependency PMAlertController is not used in any concrete target.
I'm using xcode 7.3 with objective-c project and pod version 1.0.0
Thanks in advance.

Hi @afiq90. Please, update to pod version 1.0.3.
Objective-C is supported from the version 1.0.2.
Let me know.

I tried to uninstall and install my pod but it still give me version 1.0.0, how can I update version 1.0.3?

In your podfile, don't specify the version, like this:
pod 'PMAlertController'
then, call
pod update in Terminal.
Let me know.

thank  you, after i ran pod update command, I tried pod install again and now it's successfully installed.


python311Packages.model-checker: 0.4.12 -> 0.5.6

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 335264 run on x86_64-linux 1

4 packages built:

python311Packages.model-checker
python311Packages.model-checker.dist
python312Packages.model-checker
python312Packages.model-checker.dist


build: improve gradle and github workflows for rust and elixir

Debug
Rust
cd implementations/rust
../../gradlew build

Elixir
Depends on Rust
cd implementations/elixir
../../gradlew build

Test
Rust
cd implementations/rust
../../gradlew test

Elixir
cd implementations/elixir
../../gradlew test

Release
Rust
cd implementations/rust
../../gradlew build -Pmode=release

Elixir
cd implementations/elixir
../../gradlew build -Pmode=release

Clean
Rust
cd implementations/rust
../../gradlew clean

Elixir
cd implementations/elixir
../../gradlew clean

VeryClean
Rust
cd implementations/rust
../../gradlew veryClean

Elixir
cd implementations/elixir
../../gradlew veryClean

From the repo root
./gradlew build

./gradlew test

./gradlew clean

./gradlew veryClean

@thomcc @metaclips @hairyhum this PR is work in progress ... could I get a prelim review of it.
I'm not happy with the 8minute and 16minute build times for Rust and Elixir workflows in Github Runners. I'm hoping some caching will tackle that better than going back to lots of parallel workflows

Build time for elixir is affected by the dialyzer, I believe. Unfortunately dialyxr doesn't to a best job verifying the cached PLT files and uses old files even when the code change (for dependencies), this means we need to rebuild them more often than actually needed.

@jared-s @thomcc @metaclips @hairyhum @SanjoDeundiak could you try the changes from this PR and if no one notices any major issues with this beyond the speed in CI, let's rebase and merge this. We can improve CI speed in later increments.

The rust tests and lint in gradle are very thorough but certainly do tons of redundant work for various reasons.
I've been meaning to get to it but haven't found time. I'll take a peek on Friday. The problem is that gradle still performs the tasks as if it's not in a workspace, and so we lose most of of the benefits of running in a workspace.
For example, by cding into each directory and performing the build, the feature selection algorithm is rerun from that crate — this means we end up changing the feature set of e.g. tokio (or something else used by everything), and then all dependents get rebuilt. This happens over and over again; An acquaintance of mine published  https://crates.io/crates/cargo-hakari to help solve this problem, which I'll look into for us.
In the mean time, I suspect for CI we should just cargo test --workspace and such, which will be much faster, should hit the same test (AFAIK?) and should also hit the GHA cache far more reliably.


New

Fixes: #[issue number that will be closed through this PR]
Are you a part of GSSOC' 21?

[x] Yes
[ ] No

Describe the changes you've made
A clear and concise description of what you have done to successfully close your assigned issue. Any new files? or anything you feel to let us know!

[change 1]
[change 2]

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] New and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.

Screenshots (if required)

Original
Updated

original screenshot
updated screenshot

i have attached the updated screenshots and screen shot before updation and i also make a pr from feature branch thanks for helping me plzz check it .
Also rename the drawable
Sorry The screenshot are not on their right place but the first one was before updating and the second one was after made code changes

Please don't create a new PR for each change after review. Edit the last PR to insert screenshots.


Allow Xcode version to by specified with ios_xc_test_args

Hey @powerivq  do you think you can take a look and move this PR along? :) It addresses https://github.com/fastlane/fastlane-plugin-firebase_test_lab/issues/64 :D

@LukeDurrant Hi, thanks for your first contribution! I think this is going to be useful. I left some comments for the PR.

Hey @LukeDurrant there are some comments on this PR that need to be addressed before it can be merged :)


LDAP inbound appears to max at 1000 records

Environment DC=gsmtest should have 70,513 users and 71,046 groups.
The LDAP inbound appears to only grab 1000 records from each.

This is happening due to a server-side config in TMO Ldap. Our options are:

Adjust the value of 'dSHeuristic' in Active Directory. This could result in unstable behavior by allowing excessive queries to interfere with other AD traffic on the network.
Implement paging on the ldap client. The precondition for this feature is that paging is enabled in TMO AD. I have reached out to @chrisspanton for confirmation and am adjusting our script to use paging now.

References:
https://stackoverflow.com/questions/2073574/how-get-get-more-search-results-than-the-servers-sizelimit-with-python-ldap
https://stackoverflow.com/questions/24252803/ldap-query-only-returning-1000-users-yes-i-am-using-paging#24512928
https://support.microsoft.com/en-us/help/2009267/windows-server-2008-and-newer-domain-controller-returns-only-5000-valu


Accessing custom classes with uproot

First of all, THANK YOU for you quick reply on my stackoverflow question :)
Can you please tell me how uproot can handle the class features in : Evt, AAObject, TObject and t?
My goal: open data in my root file into pandas DataFrame.
When I try to loop over data in ['Evt'] tree, I get the following error for the following branches AAObject, TObject and  t
ValueError: cannot interpret branch b'AAObject' as a Python typein file: /myfile.root

ValueError: cannot interpret branch b't' as a Python type in file: /myfile.root

ValueError: cannot interpret branch b'TObject' as a Python type in file: /myfile.root

This is what I type to explore my file
data = uproot.open("myfile.root")["E"]
data.show()
data_branch_Evt['Evt']['AAObject'].basket(0)
data_branch_Evt['t'].basket(0)`

Here is the result of data.show()
Evt                        TStreamerInfo              None
AAObject                   TStreamerInfo              None
TObject                    TStreamerInfo              None
fUniqueID                  TStreamerBasicType         asdtype('>u4')
fBits                      TStreamerBasicType         asdtype('>u4')

usr                        TStreamerSTL  asjagged(asdtype('>f8'), 10)
usr_names                  TStreamerSTL asgenobj(STLVector(STLString()))

id                         TStreamerBasicType         asdtype('>i4')
det_id                     TStreamerBasicType         asdtype('>i4')
mc_id                      TStreamerBasicType         asdtype('>i4')
run_id                     TStreamerBasicType         asdtype('>i4')
mc_run_id                  TStreamerBasicType         asdtype('>i4')
frame_index                TStreamerBasicType         asdtype('>i4')
trigger_mask               TStreamerBasicType         asdtype('>u8')
trigger_counter            TStreamerBasicType         asdtype('>u8')
overlays                   TStreamerBasicType         asdtype('>u4')
t                          TStreamerObjectAny         None
t.fSec                     TStreamerBasicType         asdtype('>i4')
t.fNanoSec                 TStreamerBasicType         asdtype('>i4')

hits                       TStreamerSTL               asdtype('>i4')

Thank you for your time and consideration
dummy.root.zip
@tamasgal

AAObject is what I call a "fake branch"—it exists to help define the class structure, but it contains no data. Looking at its streamer,
>>> file._context.streamerinfosmap[b"AAObject"].show()
StreamerInfo for class: AAObject, version=5, checksum=0x307c73ad
  TObject         BASE            offset=  0 type=66 Basic ROOT object
  usr_data        vector<AAny>    offset=  0 type=500 dox: storage place for any user data values (AAny)
  usr_names       vector<string>  offset=  0 type=500 dox: user data keys

You see the usr_data and usr_names as separate branches—they've already been split out. All the usr_names you wanted, for example, can be obtained through
tree.array("usr_names")

Stepping back to your original problem, you want to load these into Pandas DataFrames—multiple DataFrames because they have different cardinalities: the number of hits is not equal to the number of tracks, and Pandas does not/cannot deal with different numbers of object in a DataFrame (that's not what a DataFrame is about). So you're going to have to select branches anyway. This is how you would get the hits as a DataFrame:
>>> tree.pandas.df("hits.*")

                hits.id  hits.dom_id  hits.channel_id  hits.tdc  ...  hits.pure_a  hits.type  hits.origin  hits.pattern_flags
entry subentry                                                   ...
0     0               0    806451572                8         0  ...          0.0          0            0                   0
      1               0    806451572                9         0  ...          0.0          0            0                   0
      2               0    806451572               14         0  ...          0.0          0            0                   0
      3               0    806451572               18         0  ...          0.0          0            0                   0
      4               0    806455814                8         0  ...          0.0          0            0                   0
...                 ...          ...              ...       ...  ...          ...        ...          ...                 ...
9     100             0    809524432               10         0  ...          0.0          0            0                   0
      101             0    809544058                9         0  ...          0.0          0            0                   0
      102             0    809544058               10         0  ...          0.0          0            0                   0
      103             0    809544058               11         0  ...          0.0          0            0                   0
      104             0    809544061                0         0  ...          0.0          0            0                   0

[1434 rows x 20 columns]

When investigating the trks, I found a bug—unrelated to what you were asking about, but something to fix anyway. (It was the newly added std::vector handling inside of a class; if that class is itself inside of a vector, the result should be a doubly jagged array, not singly jagged.) So I'm going to fix that in a PR, making it possible to read the "trks.*" the same way as "hits.*".

PR #391.

That was quick, as always ;)
A question regarding the tree.pandas.df("hits.*") where you already pointed out that Pandas dataframe is not well-suited: is there a built-in/easy way to do the grouping efficiently, for example for iteration? As far as I can see the entry column is used to indicate which rows belong together.
When we convert such files to HDF5, we basically do the same as this tree.pandas.df method and also save an index table which maps the number of items and the starting index, so we can easily pick a single event without reading the whole table.
So I am wondering how you would access all the hits of the 6th event (including all parameters).
In [1]: import uproot

In [2]: f = uproot.open("dummy.root")

In [3]: f["E/hits.channel_id"].array()[5]
Out[3]:
array([17, 22,  4,  3,  1,  0,  4,  6,  7,  8,  9,  3, 24, 14,  5,  6, 19,
        6, 25, 29,  3, 28,  7,  9,  2, 28, 14,  6,  3,  7, 14,  2, 11, 30,
       30, 20, 12,  9, 29, 19, 16, 15, 22, 19,  5, 23,  1, 15, 10, 26,  3,
       23,  4,  8,  8, 10, 15, 15,  1,  9], dtype=uint32)

In [4]: f["E/hits"].arrays(["channel_id", "dom_id"])[5]
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-4-bcf125a067ed> in <module>
----> 1 f["E/hits"].arrays(["channel_id", "dom_id"])[5]

AttributeError: 'TBranchElement' object has no attribute 'arrays'

This is more or less similar to what @zinebaly aims for (sorry, not meant to hijack this issue, but we are colleagues ;)

If you want to get, for instance, the 6th hit of every event, your problem may not be well-suited to Pandas. However, awkward-array was made for this sort of thing. If you extract the data with arrays instead of pandas.df, you'll get unflattened jagged arrays from the awkward-array library, and you can select the 6th hit of every event like this:
jagged_hits[:, 5]

which is now a non-jagged array. There's a lot more, so see that library's documentation.
Also, some of the data in your file is doubly nested, which ROOT does not store in the same way as a doubly jagged array. To turn the ObjectArrays you get out of ROOT into true doubly jagged arrays (for slicing like the above), pass then through awkward.fromiter. (That function is not automatically called because the awkward 0.x version of it involves a Python for loop, something to be avoided without explicitly knowing what you're getting into, performance-wise, but awkward 1.x does that loop in C++ and so uproot 4.x, which will be based on awkward 1.x, will automatically call awkward.fromiter. I'll be taking about that this week at CHEP.)

Ah, I was probably unclear, I meant getting the hits for the 6th event (it was not really related to pandas), which I did not yet manage to do easily, other than grabbing all sub-arrays manually (like f["E/hits.channel_id"].array()[5] etc.)
How do you actually obtain that jagged_hits? I am playing around with it and f["E/hits"] has no arrays() method since it's a TBranchElement and f["E"].array("hits") gives some weird numbers:
In [182]: f = uproot.open("dummy.root")

In [183]: f["E"].array("hits")
Out[183]: array([176, 125, 318, 157,  83,  60,  71,  84, 255, 105], dtype=int32)

Anyways, your explanations are still very enlightening! I need to dive much deeper into the docs I guess.

For example,
jagged_hits_x = tree.array("hits.pos.x")

And work with jagged arrays for each column individually, or maybe
jagged_hits = awkward.JaggedArray.zip(tree.arrays("hits.*"))

But the disadvantage of this is that it loads all columns whether you need them or not. There's yet another alternative:
everything = tree.lazyarrays()
jagged_hits = everything["hits"]

The lazy arrays load what you ask for when you ask for it, but then you get less control. Some of the complaints that I've gotten about laser eyes well down to not having as much control.
Picking the 6th event, rather than the 6th hit of every event, is this:
jagged_hits[5]

It's not quite as easy to do that in Pandas because the numbers in a DataFrame are less object-like. (There are a few different ways, and they're not super hard, but not nearly as easy as just [5].)

Hm I got a bit stuck actually. Also with the lazyarrays() I only get flat array of integers instead of a real jagged array with the actual content:
In [54]: tree.lazyarrays()   # tree is f["E"]
Out[54]: <Table [<Row 0> <Row 1> <Row 2> ... <Row 7> <Row 8> <Row 9>] at 0x7f06413cd890>

In [55]: tree.lazyarrays()["hits"]
Out[55]: <ChunkedArray [176 125 318 ... 84 255 105] at 0x7f0640dd7bd0>

In [56]: tree.lazyarrays()["hits"][5]
Out[56]: 60

maybe I misunderstood something...
But this one works (yes, all 0 is ok, since it's not calibrated):
In [58]: tree = f["E"]

In [59]: tree.array("hits.pos.x")
Out[59]: <JaggedArray [[0.0 0.0 0.0 ... 0.0 0.0 0.0] [0.0 0.0 0.0 ... 0.0 0.0 0.0] [0.0 0.0 0.0 ... 0.0 0.0 0.0] ... [0.0 0.0 0.0 ... 0.0 0.0 0.0] [0.0 0.0 0.0 ... 0.0 0.0 0.0] [0.0 0.0 0.0 ... 0.0 0.0 0.0]] at 0x7f0640b3f7d0>

Btw. the (not recommended) zip solution fails due to a Python 3 incompatibility in awkward (I also tried with bytes instead of strings), I have not traced that down yet, I am still a bit sick and my brain is too slow:
In [60]: awkward.JaggedArray.zip(tree.arrays("hits.*"))
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-60-2f86d433acff> in <module>
----> 1 awkward.JaggedArray.zip(tree.arrays("hits.*"))

/pbs/throng/km3net/software/python/3.7.5/lib/python3.7/site-packages/awkward/util.py in <lambda>(*args, **kwargs)
     46     def __get__(self, ins, typ):
     47         if ins is None:
---> 48             return lambda *args, **kwargs: self.fcn(True, typ, *args, **kwargs)
     49         else:
     50             return lambda *args, **kwargs: self.fcn(False, ins, *args, **kwargs)

/pbs/throng/km3net/software/python/3.7.5/lib/python3.7/site-packages/awkward/array/jagged.py in zip(isclassmethod, cls_or_self, columns1, *columns2, **columns3)
   1821         if isclassmethod:
   1822             if isinstance(columns1, dict) or len(columns3) > 0:
-> 1823                 table = cls.Table.fget(None)(columns1, *columns2, **columns3)
   1824             else:
   1825                 table = cls.Table.fget(None).named("tuple", columns1, *columns2)

/pbs/throng/km3net/software/python/3.7.5/lib/python3.7/site-packages/awkward/array/table.py in __init__(self, columns1, *columns2, **columns3)
    222                 seen.add(n)
    223
--> 224                 self[n] = x
    225
    226             if len(columns2) != 0:

/pbs/throng/km3net/software/python/3.7.5/lib/python3.7/site-packages/awkward/array/table.py in __setitem__(self, where, what)
    640             self._contents[where] = self._util_toarray(what, self.DEFAULTTYPE)
    641
--> 642         elif self._util_isstringslice(where):
    643             what = what.unzip()
    644             if len(where) != len(what):

/pbs/throng/km3net/software/python/3.7.5/lib/python3.7/site-packages/awkward/array/base.py in _util_isstringslice(cls, where)
    613             return True
    614         elif isinstance(where, bytes):
--> 615             raise TypeError("column selection must be str, not bytes, in Python 3")
    616         elif isinstance(where, tuple):
    617             return False

TypeError: column selection must be str, not bytes, in Python 3

This is because I'm trying to give suggestions on my phone without testing them. The "hits" in your file is both a so-called "fake branch" for structure and also happens to store the number of hits per event. That's why it's a flat array of numbers. It'll be hard for me to give suggestions non-interactively, but hopefully I'll given you enough pointers?

I understand, thanks! I'll explore and report back tomorrow.
Btw. have a nice time at CHEP in Australia! A bummer that I could not go there...

I think the original issue is done and the subsequent bug-fixes are okay, so I'm going to close this and merge the PR. If you find additional bugs, open new GitHub issues, and if you have other usage questions, ask on StackOverflow.
Thanks! (And bummer about not being able to meet up at CHEP.)


When Perfetto fails to parse Catapult json it needs to provide a line number

The current dialog pops up with a generic message like it couldn't parse a key for a value.
Failure parsing JSON: encountered fatal error while parsing key for value.
This provides no info to the caller a to where or what to fix in the json to get the parsing to work.

Makes sense but this is just very low priority I'm afraid. As ever the JSON format is supported best effort
Generally you can debug these issues by parsing with any other tool (e.g. jq) and they'll be able to find the problem for you very quickly.

Found the issue, it was a json key without quotes around it.   So looked valid, until I dropped it onto a json validator.

https://r.android.com/3241120 fixes this issue.


Include path to tag file in run report

To make life easier for future archeologists, it would be helpful to include the path to the tag file in run_report.yaml, so that this file can be located more easily.

Good idea! I'll make that change in 2.0!


Missing notebook plots

After upgrading Bokeh, sometimes plots are 'missing' from notebook output cells.  It looks like this:

The web console shows the following error message when running the Tutorial 1 notebook:
Error rendering Bokeh items: Error: LinearAxis(p2299).major_label_overrides given invalid value: {"1":"0","2":"3 - 4","3":"4 - 5","4":"5 - 6","5":"6 - 7","6":"7 - 8","7":"8 - 9","8":"9 - 10","9":"10 - 11","10":"11 - 12","11":"12 - 13"}

I couldn't find anything obvious in the Bokeh docs about changes to major_label_overrides, and this previously worked with Bokeh 2.
It affects Bokeh 3.1 to 3.3 (3.0 fails for a different reason) and requiring Bokeh >=3.4 resolves it.
Output of pip freeze for a breaking environment.

Fixed on #133 (never affected main)


Update to WebdriverIO v7

Currently this package can't be used with the latest version of WebdriverIO v7, due to this line: https://github.com/atti187/wdio-chromedriver-service/blob/master/package.json#L36. The hooks haven't changed much (only the Cucumber ones). It would be great if we could update.

Check out https://www.npmjs.com/package/wdio-chromedriver-service/v/7.0.0... ping me if it's not working!

Thanks for the quick fix 🙏


Build Failure on Linux

Getting the following:
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Linux 4.4.39-1-MANJARO
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--loglevel=http" "--module=/home/phil/src/swa-dashboard/node_modules/libxmljs/build/Release/xmljs.node" "--module_name=xmljs" "--module_path=/home/phil/src/swa-dashboard/node_modules/libxmljs/build/Release"
gyp ERR! cwd /home/phil/src/swa-dashboard/node_modules/libxmljs
gyp ERR! node -v v7.3.0
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --loglevel=http --module=/home/phil/src/swa-dashboard/node_modules/libxmljs/build/Release/xmljs.node --module_name=xmljs --module_path=/home/phil/src/swa-dashboard/node_modules/libxmljs/build/Release' (1)
node-pre-gyp ERR! stack     at ChildProcess. (/home/phil/src/swa-dashboard/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:106:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:885:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
node-pre-gyp ERR! System Linux 4.4.39-1-MANJARO
node-pre-gyp ERR! command "/usr/bin/node" "/home/phil/src/swa-dashboard/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" "--loglevel" "http"
node-pre-gyp ERR! cwd /home/phil/src/swa-dashboard/node_modules/libxmljs
node-pre-gyp ERR! node -v v7.3.0
node-pre-gyp ERR! node-pre-gyp -v v0.6.32
node-pre-gyp ERR! not ok
Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --loglevel=http --module=/home/phil/src/swa-dashboard/node_modules/libxmljs/build/Release/xmljs.node --module_name=xmljs --module_path=/home/phil/src/swa-dashboard/node_modules/libxmljs/build/Release' (1)
npm ERR! Linux 4.4.39-1-MANJARO
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "link"
npm ERR! node v7.3.0
npm ERR! npm  v4.1.1
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build --loglevel http
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --fallback-to-build --loglevel http'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the libxmljs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build --loglevel http

Got the same issue here, any solution?

Same error here!
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Linux 3.10.0-514.6.1.el7.x86_64
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/miguel/mlpbarreiro/excell-to-json/node_modules/libxmljs
gyp ERR! node -v v6.9.5
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
npm ERR! Linux 3.10.0-514.6.1.el7.x86_64
npm ERR! argv "/usr/bin/node" "/bin/npm" "install"<EMAIL_ADDRESS>npm ERR! node v6.9.5
npm ERR! npm  v2.15.11
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the libxmljs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs libxmljs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls libxmljs
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/miguel/mlpbarreiro/excell-to-json/npm-debug.log

@SpyroZeppeli and @miguelBarreiro85, are you guys also running an arch based distro?

Please run node-gyp --loglevel=silly rebuild and post the output

I get something similar, when I try to npm install lime server's node component, which depends on libxmljs:
><EMAIL_ADDRESS>install /home/currentusername/lime2/aknservices/node_modules/libxmljs
> node-gyp rebuild

/bin/sh: 1: node: not found
gyp: Call to 'node -e "require('nan')"' returned exit status 127 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:354:16)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 4.4.0-31-generic
gyp ERR! command "/usr/bin/nodejs" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /home/jmar150/lime2/aknservices/node_modules/libxmljs
gyp ERR! node -v v4.2.6
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok

and then finally:
npm ERR! Linux 4.4.0-31-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the libxmljs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs libxmljs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls libxmljs
npm ERR! There is likely additional logging output above.

I am on Ubuntu Xenial Xerus.
I had similar problems building on Arch, but I don't have that VM anymore to test this on.

Could be related to a similar issue with gyp shown here: https://github.com/websockets/ws/issues/458 ?

After taking the advice in that issue (namely sudo ln -s /usr/bin/nodejs /usr/bin/node), npm install now works for me.

Internally node-gyp calls node command. See https://github.com/npm/npm/issues/9253

Got the same issue here, any solution?

Solved! remved centOS installed ubuntu 16!|
2017-02-12 16:48 GMT+00:00 Weipeng Kuang<EMAIL_ADDRESS>
Got the same issue here, any solution?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/libxmljs/libxmljs/issues/456#issuecomment-279231005,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYZmd72DvxuIrAvMbkCgqnMZV9nqSMvFks5rbzfNgaJpZM4LuPkH
.

Same issue.  Tried to download(404): https://github.com/libxmljs/libxmljs/releases/download/v0.18.4/node-v11-linux-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v11 ABI) (falling back to source compile with node-gyp)
node-pre-gyp http 404 status code downloading tarball https://github.com/libxmljs/libxmljs/releases/download/v0.18.4/node-v11-linux-x64.tar.gz
gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/0.10.37"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/home/user/genieacs/node_modules/libxmljs/.node-gyp"
gyp http GET https://nodejs.org/dist/v0.10.37/node-v0.10.37.tar.gz
gyp http 200 https://nodejs.org/dist/v0.10.37/node-v0.10.37.tar.gz
gyp http GET https://nodejs.org/dist/v0.10.37/SHASUMS256.txt
gyp http 200 https://nodejs.org/dist/v0.10.37/SHASUMS256.txt
make: Entering directory /home/user/genieacs/node_modules/libxmljs/build' make: *** No rule to make target ../.node-gyp/0.10.37/common.gypi', needed by Makefile'.  Stop. make: Leaving directory /home/user/genieacs/node_modules/libxmljs/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/user/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:820:12)
gyp ERR! System Linux 4.4.0-31-generic
gyp ERR! command "/usr/bin/nodejs" "/home/user/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--loglevel=http" "--module=/home/user/genieacs/node_modules/libxmljs/build/Release/xmljs.node" "--module_name=xmljs" "--module_path=/home/user/genieacs/node_modules/libxmljs/build/Release"
gyp ERR! cwd /home/user/genieacs/node_modules/libxmljs
gyp ERR! node -v v0.10.37
gyp ERR! node-gyp -v v3.5.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/nodejs /home/user/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --loglevel=http --module=/home/user/genieacs/node_modules/libxmljs/build/Release/xmljs.node --module_name=xmljs --module_path=/home/user/genieacs/node_modules/libxmljs/build/Release' (1)
node-pre-gyp ERR! stack     at ChildProcess. (/home/user/genieacs/node_modules/libxmljs/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
node-pre-gyp ERR! stack     at maybeClose (child_process.js:766:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:833:5)
node-pre-gyp ERR! System Linux 4.4.0-31-generic
node-pre-gyp ERR! command "node" "/home/user/genieacs/node_modules/libxmljs/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" "--loglevel" "http"
node-pre-gyp ERR! cwd /home/user/genieacs/node_modules/libxmljs
node-pre-gyp ERR! node -v v0.10.37
node-pre-gyp ERR! node-pre-gyp -v v0.6.33
node-pre-gyp ERR! not ok
Failed to execute '/usr/bin/nodejs /home/user/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --loglevel=http --module=/home/user/genieacs/node_modules/libxmljs/build/Release/xmljs.node --module_name=xmljs --module_path=/home/user/genieacs/node_modules/libxmljs/build/Release' (1)
npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build --loglevel http
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is most likely a problem with the libxmljs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build --loglevel http
npm ERR! You can get their info via:
npm ERR!     npm owner ls libxmljs
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 4.4.0-31-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "libxmljs"
npm ERR! cwd /home/user/genieacs/node_modules
npm ERR! node -v v0.10.37
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR! not ok code 0
root@TR-069:/home/user/genieacs/node_modules#

I ran into this when installing libxmljs from an Amazon Linux instance's startup script.
The common theme here is that the installation runs as root, both in my startup script and in the reported errors above. It all starts here:
gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/6.9.5"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/lib/node_modules/libxmljs/.node-gyp"

Then, later, when you get
make: *** No rule to make target `../.node-gyp/6.9.5/include/node/common.gypi', needed by `Makefile'.  Stop.

presumably, that's because the Makefile expects a certain path, and because gyp fell back to another path, it doesn't exist.
In my case, (manually) installing as a non-privileged user worked fine. Alternatively, as suggested in nodejs/node-gyp#454, you can also add --unsafe-perm to npm i to allow gyp to access the path.

Relevant sections from npm config:

unsafe-perm
Default: false if running as root, true otherwise
Type: Boolean
Set to true to suppress the UID/GID switching when running package scripts. If set explicitly to false, then installing as a non-root user will fail.

user
Default: "nobody"
Type: String or Number
The UID to set to when running package scripts as root.

Thanks Tim, in my case it was the node version. i upgraded to 6.9.x and it worked. Now it gives an error about rails :(

I have the same issue on the Linux Subsystem for Windows. I have Node V 6.10.2 and NPM v.3.10.10. The Linux subsystem is the Ubuntu 16.04 operating system. Upon closely looking at the logs I figured that it was trying to run make command and run make: cc and make: g++. These were not found on my Linux subsystem and hence it failed to install.
I installed build-essentials, gcc, g++ packages and the error went away. apt-get install build-essentials gcc g++

Should be fixed in v0.18.5

I am seeing similar error with Node8,
Cannot read property 'version' of null
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build --loglevel http`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Try installing the latest version

Still the same error:
gyp info it worked if it ends with ok gyp verb cli [ '/usr/local/litle-home/shande/.nvm/versions/node/v9.4.0/bin/node', gyp verb cli   '/usr/local/litle-home/shande/.nvm/versions/node/v9.4.0/bin/node-gyp', gyp verb cli   '--loglevel=silly', gyp verb cli   'rebuild' ] gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| linux | x64 gyp verb command rebuild [] gyp verb command clean [] gyp verb clean removing "build" directory gyp verb command configure [] gyp verb check python checking for Python executable "python2" in the PATH gyp verbwhichsucceeded python2 /usr/bin/python2 gyp verb check python version/usr/bin/python2 -c "import platform; print(platform.python_version());"returned: "2.6.6\n" gyp verb get node dir no --target version specified, falling back to host node version: 9.4.0 gyp verb command install [ '9.4.0' ] gyp verb install input version string "9.4.0" gyp verb install installing version: 9.4.0 gyp verb install --ensure was passed, so won't reinstall if already installed gyp verb install version is already installed, need to check "installVersion" gyp verb got "installVersion" 9 gyp verb needs "installVersion" 9 gyp verb install version is good gyp verb get node dir target node version installed: 9.4.0 gyp verb build dir attempting to create "build" dir: /usr/local/litle-home/shande/build gyp verb build dir "build" dir needed to be created? /usr/local/litle-home/shande/build gyp verb build/config.gypi creating config file gyp sill build/config.gypi { target_defaults:  gyp sill build/config.gypi    { cflags: [], gyp sill build/config.gypi      default_configuration: 'Release', gyp sill build/config.gypi      defines: [], gyp sill build/config.gypi      include_dirs: [], gyp sill build/config.gypi      libraries: [] }, gyp sill build/config.gypi   variables:  gyp sill build/config.gypi    { asan: 0, gyp sill build/config.gypi      coverage: false, gyp sill build/config.gypi      debug_devtools: 'node', gyp sill build/config.gypi      debug_http2: false, gyp sill build/config.gypi      debug_nghttp2: false, gyp sill build/config.gypi      force_dynamic_crt: 0, gyp sill build/config.gypi      gas_version: '2.23', gyp sill build/config.gypi      host_arch: 'x64', gyp sill build/config.gypi      icu_data_file: 'icudt60l.dat', gyp sill build/config.gypi      icu_data_in: '../../deps/icu-small/source/data/in/icudt60l.dat', gyp sill build/config.gypi      icu_endianness: 'l', gyp sill build/config.gypi      icu_gyp_path: 'tools/icu/icu-generic.gyp', gyp sill build/config.gypi      icu_locales: 'en,root', gyp sill build/config.gypi      icu_path: 'deps/icu-small', gyp sill build/config.gypi      icu_small: true, gyp sill build/config.gypi      icu_ver_major: '60', gyp sill build/config.gypi      llvm_version: 0, gyp sill build/config.gypi      node_byteorder: 'little', gyp sill build/config.gypi      node_enable_d8: false, gyp sill build/config.gypi      node_enable_v8_vtunejit: false, gyp sill build/config.gypi      node_install_npm: true, gyp sill build/config.gypi      node_module_version: 59, gyp sill build/config.gypi      node_no_browser_globals: false, gyp sill build/config.gypi      node_prefix: '/', gyp sill build/config.gypi      node_release_urlbase: 'https://nodejs.org/download/release/', gyp sill build/config.gypi      node_shared: false, gyp sill build/config.gypi      node_shared_cares: false, gyp sill build/config.gypi      node_shared_http_parser: false, gyp sill build/config.gypi      node_shared_libuv: false, gyp sill build/config.gypi      node_shared_nghttp2: false, gyp sill build/config.gypi      node_shared_openssl: false, gyp sill build/config.gypi      node_shared_zlib: false, gyp sill build/config.gypi      node_tag: '', gyp sill build/config.gypi      node_use_bundled_v8: true, gyp sill build/config.gypi      node_use_dtrace: false, gyp sill build/config.gypi      node_use_etw: false, gyp sill build/config.gypi      node_use_lttng: false, gyp sill build/config.gypi      node_use_openssl: true, gyp sill build/config.gypi      node_use_perfctr: false, gyp sill build/config.gypi      node_use_v8_platform: true, gyp sill build/config.gypi      node_without_node_options: false, gyp sill build/config.gypi      openssl_fips: '', gyp sill build/config.gypi      openssl_no_asm: 0, gyp sill build/config.gypi      shlib_suffix: 'so.59', gyp sill build/config.gypi      target_arch: 'x64', gyp sill build/config.gypi      uv_parent_path: '/deps/uv/', gyp sill build/config.gypi      uv_use_dtrace: false, gyp sill build/config.gypi      v8_enable_gdbjit: 0, gyp sill build/config.gypi      v8_enable_i18n_support: 1, gyp sill build/config.gypi      v8_enable_inspector: 1, gyp sill build/config.gypi      v8_no_strict_aliasing: 1, gyp sill build/config.gypi      v8_optimized_debug: 0, gyp sill build/config.gypi      v8_promise_internal_field_count: 1, gyp sill build/config.gypi      v8_random_seed: 0, gyp sill build/config.gypi      v8_trace_maps: 0, gyp sill build/config.gypi      v8_use_snapshot: true, gyp sill build/config.gypi      want_separate_host_toolset: 0, gyp sill build/config.gypi      nodedir: '/usr/local/litle-home/shande/.node-gyp/9.4.0', gyp sill build/config.gypi      standalone_static_library: 1 } } gyp verb build/config.gypi writing out config file: /usr/local/litle-home/shande/build/config.gypi gyp verb config.gypi checking for gypi file: /usr/local/litle-home/shande/config.gypi gyp verb common.gypi checking for gypi file: /usr/local/litle-home/shande/common.gypi gyp verb gyp gyp format was not specified; forcing "make" gyp info spawn /usr/bin/python2 gyp info spawn args [ '/usr/local/litle-home/shande/.nvm/versions/node/v9.4.0/lib/node_modules/node-gyp/gyp/gyp_main.py', gyp info spawn args   'binding.gyp', gyp info spawn args   '-f', gyp info spawn args   'make', gyp info spawn args   '-I', gyp info spawn args   '/usr/local/litle-home/shande/build/config.gypi', gyp info spawn args   '-I', gyp info spawn args   '/usr/local/litle-home/shande/.nvm/versions/node/v9.4.0/lib/node_modules/node-gyp/addon.gypi', gyp info spawn args   '-I', gyp info spawn args   '/usr/local/litle-home/shande/.node-gyp/9.4.0/include/node/common.gypi', gyp info spawn args   '-Dlibrary=shared_library', gyp info spawn args   '-Dvisibility=default', gyp info spawn args   '-Dnode_root_dir=/usr/local/litle-home/shande/.node-gyp/9.4.0', gyp info spawn args   '-Dnode_gyp_dir=/usr/local/litle-home/shande/.nvm/versions/node/v9.4.0/lib/node_modules/node-gyp', gyp info spawn args   '-Dnode_lib_file=/usr/local/litle-home/shande/.node-gyp/9.4.0/<(target_arch)/node.lib', gyp info spawn args   '-Dmodule_root_dir=/usr/local/litle-home/shande', gyp info spawn args   '-Dnode_engine=v8', gyp info spawn args   '--depth=.', gyp info spawn args   '--no-parallel', gyp info spawn args   '--generator-output', gyp info spawn args   'build', gyp info spawn args   '-Goutput_dir=.' ] 'import sitecustomize' failed; use -v for traceback gyp: binding.gyp not found (cwd: /usr/local/litle-home/shande) while trying to load binding.gyp gyp ERR! configure error  gyp ERR! stack Error:gypfailed with exit code: 1 gyp ERR! stack     at ChildProcess.onCpExit (/usr/local/litle-home/shande/.nvm/versions/node/v9.4.0/lib/node_modules/node-gyp/lib/configure.js:336:16) gyp ERR! stack     at ChildProcess.emit (events.js:160:13) gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:12) gyp ERR! System Linux 2.6.32-696.23.1.el6.x86_64 gyp ERR! command "/usr/local/litle-home/shande/.nvm/versions/node/v9.4.0/bin/node" "/usr/local/litle-home/shande/.nvm/versions/node/v9.4.0/bin/node-gyp" "--loglevel=silly" "rebuild" gyp ERR! cwd /usr/local/litle-home/shande gyp ERR! node -v v9.4.0 gyp ERR! node-gyp -v v3.6.2 gyp ERR! not ok

I'm still getting this error in 2020. Can someone please help. I have bee stuck for hours now :cry:

I've tried to use nvm to switch between node versions 8, 10 and 12


Invalid date 'February 29' as '1925' is not a leap year

Describe the bug
If now date is a leap year, for example 2024.02.29, throws exception java.time.DateTimeException
Invalid date 'February 29' as '1925' is not a leap year
To Reproduce
// Current date must be February 29 and  leap year
Faker faker = new Faker();
faker.date().birthday(18, 99)
Expected behavior
Generates valid date
Versions:

OS: any
JDK: any
Faker Version: 1.8.1

Additional context
Need to add if here:

something like:
if (dayOfMonth == 29){
dayOfMonth = dayOfMonth-1;
}

same here!

me too

This has already been fixed in later versions
https://github.com/datafaker-net/datafaker/pull/954
please use the latest version e.g. 2.1.0

2.0.2 also has this fix
do you have the same issue while upgrading to 2.0.2?

I found the solution for my build.gradle.kts. May be it someone helps:
configurations.forEach { it.exclude("org.yaml", "snakeyaml") }
dependencies {
    implementation("org.yaml:snakeyaml:1.26")
    implementation("net.datafaker:datafaker:2.1.0")
}

@Arroheim why are you excluding Snakeyaml, and what issues are you running into? The snakeyaml you hav mentioned above is full of security issues, don't use that one; Datafaker comes with Snakeyaml 2.2 which, as far as we know, doesn't have CVEs, so when you say: "Update to 2.1.0 has some difficults with snakeYaml", does that mean you might have a version conflict or so? Either way, I wouldn't recommend your above approach.

I tend to think that introduction of module-info is the reason...
Ideally it shouldn't happen since snakeyaml is shaded
@Arroheim could you please double check whether datafaker 2.0.2 works without that hack?

We've encountered this problem, too. This issue should still be open.
Updating to 2.1.0 in Java throws this when using Locality
java.lang.RuntimeException: java.lang.NullPointerException: Cannot invoke "java.nio.file.Path.toString()" because the return value of "java.nio.file.Path.getFileName()" is null
	at net.datafaker.providers.base.Locality.allSupportedLocales(Locality.java:103)
	at net.datafaker.providers.base.Locality.allSupportedLocales(Locality.java:49)
	at net.datafaker.providers.base.Locality.<init>(Locality.java:39)
	at net.datafaker.providers.base.BaseFaker.getProvider(BaseFaker.java:329)
	at net.datafaker.providers.base.ProviderRegistration.getProvider(ProviderRegistration.java:21)

We are instantiating a default Faker instance: new Faker()
Tried fixing snakeyaml, too. Doesn't work either...

@gdonoso94 this is another issue and it is not clear how to reproduce it
please open a new issue and provide steps to reproduce

@Arroheim thanks for checking, then not clear why it is happening... need to debug
I do notuse gradle... in maven projects i do not see this issue...


Bump version bound

QC 2.12 is out now - nothing in it conflicts with qc-instances, it seems.

Thanks for the ping. I made a revision http://hackage.haskell.org/package/quickcheck-instances-0.3.18/revisions/


cleanup morphologyHDF5

make which datasets belong to which versions more clear
don't use try/catch to detect if datasets exist
try and clarify where member variables are read & saved

removed member variables _points, _pointsDims, _sections,
since their locality can be kept local

fix version numbering in tests/data/h5/v1/endoplasmic-reticulum.h5
mitochondria.h5
remove unnecessary morphio::

I made the changes I proposed in :
https://github.com/BlueBrain/MorphIO/pull/288
it also fixed the no soma problem.
If you are ok with this PR above we can merge both.

Currently I have problems with hdf morphologies that have its soma points split among several offsets in structure:
HDF5 "scripts/three-point-soma-two-offset.h5" {
GROUP "/" {
   DATASET "points" {
      DATATYPE  H5T_IEEE_F32LE
      DATASPACE  SIMPLE { ( 8, 4 ) / ( 8, 4 ) }
      DATA {
      (0,0): -2, 0, 0, 1,
      (1,0): 0, 0, 0, 1,
      (2,0): 0, 0, 0, 1,
      (3,0): 2, 0, 0, 1,
      (4,0): 2, 0, 0, 1,
      (5,0): 3, 3, 0, 1,
      (6,0): 2, 0, 0, 1,
      (7,0): 4, 0, 4, 1
      }
   }
   DATASET "structure" {
      DATATYPE  H5T_STD_I32LE
      DATASPACE  SIMPLE { ( 4, 3 ) / ( 4, 3 ) }
      DATA {
      (0,0): 0, 1, -1,
      (1,0): 2, 1, -1,
      (2,0): 4, 3, 0,
      (3,0): 6, 2, 0
      }
   }
}
}

The 2nd half of soma is skipped and soma type is undefined.
three-point-soma-two-offset.h5
SomaType.SOMA_UNDEFINED
[[-2.  0.  0.]
 [ 0.  0.  0.]]
section points:
	 [2. 0. 0.]
	 [3. 3. 0.]
	 [2. 0. 0.]
	 [4. 0. 4.]

Should I be worried about this case when soma is represented by multiple offsets?

Do we have specs on that ?
Having unifurcation on Neurites --> why not, but on Somas...
To me without more specs (like we can have only one soma), this is an undefined behavior an we should raise because we cannot figure out if this is double soma morphology (one single point soma and one cylinder soma) or if this is a poorly formatted 3 points soma.

Do we have specs on that ?

There is something: "Soma: there is only one soma section, however, different tools interpret them differently:" (c). I propose to throw en exception for this case as we don't throw currently on the latest master branch.

Ok so we throw. I will update the code

Added a check here to ensure a single section soma and a the soma being the first section:
https://github.com/BlueBrain/MorphIO/pull/288/commits/f7c1c6ac359199f43d764361ceb751dbf9c09ca5

I put you as a reviewer but this is more to know if you have something to add or comment @asanin-epfl

From my side looks fine. I'm working on docs update currently, so it's good for me. Also a question, should be a similar PR for the ASC reader?

I also tested it w/ NeuroM d177237, as cross check.


Handle async functions in depends with watch=True

Required for https://github.com/holoviz/panel/issues/3262 to work

Codecov Report

Merging #611 (59ae7ea) into master (fb6f4d9) will decrease coverage by 0.56%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master     #611      +/-   ##
==========================================
- Coverage   81.95%   81.38%   -0.57%
==========================================
  Files           4        4
  Lines        3020     2950      -70
==========================================
- Hits         2475     2401      -74
- Misses        545      549       +4

Impacted Files
Coverage Δ

param/parameterized.py
81.38% <50.00%> (-0.80%)
:arrow_down:

param/serializer.py
86.48% <0.00%> (-0.48%)
:arrow_down:

numbergen/__init__.py
79.62% <0.00%> (-0.30%)
:arrow_down:

Continue to review full report at Codecov.

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


[Feature Request] Add an option to disable session overwrite check?

First of all, I should thank you for your helpful work! The vim-startify plugin saves me a lot of time.
Could it possible to add an option to disable the session overwrite check, so vim-startify won't prompt me Session already exists. Overwrite?  each time I update the session? Or is there a better way to update the existent session?

thank you for your helpful work!

Thank you for using it!

Could it possible to add an option to disable the session overwrite check, so vim-startify won't prompt me Session already exists. Overwrite? each time I update the session? Or is there a better way to update the existent session?

Using ! after a command is a typical Vim idiom. It already worked for :SDelete! and I now added support for :SSave! as well.
Does this work for you?

@mhinz
It works as expected! Thank you so much!

Thank you for bringing this up!


EVIABM Simulation

[ ] Check if the probability is reset after charging.

Optimize the model

Start the simulation later.
End it sooner.

[ ] Fix the in-shade (charger behind another charger) charger utilization.


Fix searchable select width

Fixes https://github.com/laravel-filament/filament/issues/1734
The fix here was to add min-w-0 to the select's wrapper div. Flex items have min-width: auto by default, which is based on the content width and doesn't play nice with long values that should be truncated.
This PR also addresses a separate issue with the internal search label/input. Both the label and input have w-full so are each given 50% of the width, which looks odd when you have long values:

Simplest fix I could think of was to allow the label to take up all of the space by collapsing the input with w-0, but allow that to expand when the search is open with grow. Then adding cursor-text to the label.

I also removed the redundant whitespace-nowrap.

Thanks


New release please?

The last release 0.8.1 available on crates.io is two years old at this point, and it's missing important features such as static linking (not really though, but you'd have to directly declare hdf5-sys as a dependency).
It is okay to use git dependency in some cases, but per crates.io policy, it's not allowed to publish a crate like this. Anyways, you get the point.

@aldanor Any movement on this? There are a lot of unreleased features (+ compatibility for currently-shipping versions of hdf5).

Hello @aldanor what is the recommended way of installing this crate?
Should we not be using crates.io?


bug(form-field): matTextSuffix/matTextPrefix not vertically aligned with label

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
The label of a mat-form-field is not vertically aligned with the matTextSuffix or matTextPrefix.

Notice how the suffix and prefix are a couple or so pixels above the label
Reproduction
StackBlitz link: https://stackblitz.com/edit/t9161j?file=src%2Fexample%2Fform-field-prefix-suffix-example.html
Expected Behavior
Label to be vertically aligned with both matTextSuffix and matTextPrefix
Actual Behavior
Label is not vertically aligned with both matTextSuffix and matTextPrefix
Environment

Angular: 16
CDK/Material: ^16.2.7
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): macOS

It looks like you're using Angular Material's mat-form-field with matTextSuffix and matTextPrefix, and you're facing an issue with the vertical alignment of the label.
To vertically align the label with the matTextSuffix and matTextPrefix, you can apply some custom styles. Here's an example of how you might adjust the styles to achieve better alignment:
/* In your component's styles or global styles.css /
.example-container {
display: flex;
gap: 16px; / Adjust the gap according to your layout */
}
.mat-form-field {
display: flex;
flex-direction: column;
align-items: baseline;
}
.mat-form-field-wrapper {
display: flex;
align-items: baseline;
}
.mat-form-field-label-wrapper {
display: flex;
align-items: baseline;
}
.example-right-align {
margin-left: auto;
}
This example assumes that your mat-form-field is wrapped in a container with the class example-container. The key part here is to set the align-items property to baseline for the relevant elements to ensure vertical alignment.
Please adjust the styles based on your specific layout requirements. If you are still facing issues, you may need to experiment further or consider reaching out to the Angular Material community for additional guidance.

It looks like you're using Angular Material's mat-form-field with matTextSuffix and matTextPrefix, and you're facing an issue with the vertical alignment of the label.
To vertically align the label with the matTextSuffix and matTextPrefix, you can apply some custom styles. Here's an example of how you might adjust the styles to achieve better alignment: /* In your component's styles or global styles.css / .example-container { display: flex; gap: 16px; / Adjust the gap according to your layout */ }
.mat-form-field { display: flex; flex-direction: column; align-items: baseline; }
.mat-form-field-wrapper { display: flex; align-items: baseline; }
.mat-form-field-label-wrapper { display: flex; align-items: baseline; }
.example-right-align { margin-left: auto; }
This example assumes that your mat-form-field is wrapped in a container with the class example-container. The key part here is to set the align-items property to baseline for the relevant elements to ensure vertical alignment.
Please adjust the styles based on your specific layout requirements. If you are still facing issues, you may need to experiment further or consider reaching out to the Angular Material community for additional guidance.

Appreciate the help @topdev658 😃. While this is an apt solution, I feel custom css shouldn't be used to fix core component styling. It shouldn't have to look like this in the first place unless it was intentional (in which case css patch like yours would be appropriate).
If I replace the matTextPrefix/Suffix with a larger character like the $ sign, the alignment works decent. I guess that's what the angular team was going for. But it's matTextPrefix/Suffix. Any text, or at least ascii characters, should work no? Not just special symbols.

I think I found a simpler alternative workaround. Setting the --mat-form-field-subscript-text-line-height to 26px or greater levels the label with the prefix/suffix
Stackblitz (forked from the one above with the only change being the css): https://stackblitz.com/edit/t9161j-kpt1gh?file=src%2Fexample%2Fform-field-prefix-suffix-example.css


Add test for issue #92

Well, this doesn't actually test the issue - if a handler raises a keyerror like this it will be a status 500 - internal server error. The issue that should be tested is declaring a query parameter in the arguments, and then not passing it. If I understand you correctly this should return a 404, which is wrong.

In my testing a KeyError gives a 404 even though it should be 500 so I used that is the final reduction. I'm not sure if this depends on the query parameter but that's how I found it; I can do further testing.

Without a query parameter the issue still occurs, so it's independent of parameters:
class ApiV1Controller(Controller):
    path = "/api/v1"

    @get(path="/product/{isin:str}/rawdata")
    async def product_rawdata(self, isin: str) -> Any:
        raise KeyError("Test")

with create_test_client(ApiV1Controller) as client:
        resp = client.get("/api/v1/product/test/rawdata")
        print(resp.text, resp.status_code)

Ouput (1.2.0):
{"detail":"Not Found","extra":null} 404


DataFrame::cache errors with Plan("Mismatch between schema and batches") but query works when not cached

Describe the bug
Dataframe::cache gives an error where an execution that doesn't first cache results succeeds.
I would have expected caching to have no effect on success/failure.
To Reproduce
use datafusion::prelude::SessionContext;

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
    let sql = "SELECT CASE WHEN true THEN NULL ELSE 1 END;";
    let ctx = SessionContext::new();
    let plan = ctx.state().create_logical_plan(sql).await?;
    let df = ctx.execute_logical_plan(plan).await?;
    // Comment out the next line to make the error go away.
    let df = df.cache().await?;
    let batches = df.collect().await?;
    let display = datafusion::arrow::util::pretty::pretty_format_batches(&batches).unwrap();
    println!("{}", display);
    Ok(())
}

Expected behavior
Behavior with and without let df = df.cache().await? to be functionally same, only changing performance and memory use.
Additional context
No response

The reason is that schema comparison：
https://github.com/apache/arrow-datafusion/blob/d091b55be6a4ce552023ef162b5d081136d3ff6d/datafusion/core/src/datasource/memory.rs#L68
schema：
Field { name: "CASE WHEN Boolean(true) THEN NULL ELSE Int64(1) END", data_type: Null, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: {} }

batches_schema：
Field { name: "CASE WHEN Boolean(true) THEN NULL ELSE Int64(1) END", data_type: Int64, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: {} }

data_type：Null & Int64
Can we use the optimized schema to compare，like：
before：
    pub async fn cache(self) -> Result<DataFrame> {
        let context = SessionContext::new_with_state(self.session_state.clone());
        let mem_table = MemTable::try_new(
            SchemaRef::from(self.schema().clone()),
            self.collect_partitioned().await?,
        )?;

        context.read_table(Arc::new(mem_table))
    }

after:
    pub async fn cache(self) -> Result<DataFrame> {
        let context = SessionContext::new_with_state(self.session_state.clone());
        let physical_plan = self.create_physical_plan().await?;
        let mem_table = MemTable::try_new(
            physical_plan.schema(),
            self.collect_partitioned().await?,
        )?;

        context.read_table(Arc::new(mem_table))
    }

In general, DataType::Null is normally resolved (via Coercion) to an actual type of the target schema
Maybe we could apply the same approach here


Add payload to mint, burn, transfer app credit functions.

Related: https://bitbucket.org/comcomai/nft-server/pull-requests/98/feature-liayoo-credit-api-payload

Thanks for the review!


I am using Dahua's NVR to connect to RTSP streams, but the connection keeps dropping and then reconnecting.

Which version are you using?
0.23.8
Which operating system are you using?
Linux arm64 standard
Describe how to replicate the issue

start the server
publish with ...
read with ...

Server logs
[session 09e7656b] destroyed (torn down by <IP_ADDRESS>:44746)
Network dump
No response

Upgrade to the latest version and try again?


Collaboration openinapp refactor

Description
Simplify OpenInApp method. This contains:

Custom sublogger to compact log calls
Simplify and move the code to get the appURL
Move the code to generate the query params for the appURL

We've also temporarily removed the HostViewURL and HostEditURL for 2 reasons:

Current values are wrong. The values are expected to point to an ocis URL, not to Collabora (or other WOPI app)
It keeps the OpenInApp code simpler

Those values might can back with https://github.com/owncloud/ocis/pull/9686
Related Issue
No opened issue
Motivation and Context
Code is simpler and easier to follow
How Has This Been Tested?

test environment:
test case 1:
test case 2:
...

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

[ ] Code changes
[ ] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

Rebased. Minor changes to fix conflict in "services/collaboration/pkg/service/grpc/v0/service.go"


GUVNOR-2554: Improve behavior of context popup

See https://issues.jboss.org/browse/GUVNOR-2554

+1 Nice short tests.


name 'TransformerEncoder' is not defined

I have adopted your work to my distributed environment using HDFS and Horovod, but I am getting the error name 'TransformerEncoder' is not defined, which relates to the OrthogonalRegularizer class and line config = super(TransformerEncoder, self).get_config() in the get_config function. Obviously, as you can check, the name TransformerEncoder is nowhere to be found in your work. What should be the value of this object or from where should I import this class?
I appreciate your work, and I find this example very useful. Thank you in advance for your help.

Could you please provide a link to the line that has TransformerEncoder?

I just found out I was using an outdated version of your model. You have fixed that issue in one of the commits. I just had to upgrade my model to the latest version. If you have access to the keras.io example you should consider updating that code too.
Thanks for the replay and keep up the great work!

Thanks!
@soumik12345 could you update the example? It's in the OrthogonalRegularizer layer.
class OrthogonalRegularizer(keras.regularizers.Regularizer):
    """Reference: https://keras.io/examples/vision/pointnet/#build-a-model"""

    def __init__(self, num_features, l2reg=0.001):
        self.num_features = num_features
        self.l2reg = l2reg
        self.identity = tf.eye(num_features)

    def __call__(self, x):
        x = tf.reshape(x, (-1, self.num_features, self.num_features))
        xxt = tf.tensordot(x, x, axes=(2, 2))
        xxt = tf.reshape(xxt, (-1, self.num_features, self.num_features))
        return tf.reduce_sum(self.l2reg * tf.square(xxt - self.identity))

    def get_config(self):
        config = super(TransformerEncoder, self).get_config()
        config.update({"num_features": self.num_features, "l2reg_strength": self.l2reg})
        return config


latest  deps

just cloning and running gave below error
~/t/react-ava-workshop ❯❯❯ npm test                                                                                ⏎ master

><EMAIL_ADDRESS>test /Users/bsr/tmp/react-ava-workshop
> ava "app/**/*.test.js" --verbose

Uncaught Exception: /Users/bsr/tmp/react-ava-workshop/app/components/Toggle.test.js
  TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at Object.dirname (path.js:1324:5)
    at /Users/bsr/tmp/react-ava-workshop/node_modules/babel-core/lib/transformation/file/options/option-manager.js:353:36
    at /Users/bsr/tmp/react-ava-workshop/node_modules/babel-core/lib/transformation/file/options/option-manager.js:375:22
    at Array.map (native)
    at OptionManager.resolvePresets (/Users/bsr/tmp/react-ava-workshop/node_modules/babel-core/lib/transformation/file/options/option-manager.js:364:20)
    at OptionManager.mergePresets (/Users/bsr/tmp/react-ava-workshop/node_modules/babel-core/lib/transformation/file/options/option-manager.js:348:10)
    at OptionManager.mergeOptions (/Users/bsr/tmp/react-ava-workshop/node_modules/babel-core/lib/transformation/file/options/option-manager.js:307:14)
npm ERR! Test failed.  See above for more details.

which has been solved by updating deps to latest.

Cool! Let me give this a look, thanks!

LGTM!


Compatibility v10

The first three commits seems to come from somethink we already merged : Refresh button + category sort
I don't know why it is back in this PR :(
The rest is V10 compliance + entry pages for new Journal management
13-08-2022:
I recently added some additionnal changes du to another change in WA API.
And while doing it, I added a new buttion for shrinking categories in the journal.
(When you have a big WA world, it become difficult to navigate without it)

Conflict seems to come from the fact I didn't retrieve all the changes that has been done during reviews.
I will try to see today how to do it with githubDesktop

We may need to discuss what we want in term of pages for this v10
For now, I have :

On main page called Article / Character with the main WA Article content
Some additional pages named Portrait / Cover / Image. (It's what was previously in journal.img)
Two pages named Side content and Secrets for other sections.  (Only section with id seeded is for now inside Secrets page)
On last one for Relations. (this one is not totally ok for now)

There will also be a question on which one should be displayed first : Article or Image

I like what you've done here to allocate the sections of the source WA article to different pages. I am not really sold on the idea of having a bunch of settings, do you think that users will really care to configure this? Could we simplify things and make this the default behavior?

I don't really remember why I choose to put them as parameters.

Perhaps, to allow people who only import characters to hand the page named Character instead of Article ?
Or Perhaps to allow peaple using another language to use the module "as it is" without having to get a whole module translation file.  (The GM seeing english text inside WAJournalBrowser is ok. But players seeing text in english when opening a Journal can tend to be a little anticlimatic)

I'm french myself.
Until now, I didn't see the need to add a fr.json file to the project, since it was mainly for GM.
I'm lucky : Article, Portrait, and Secrets are spelled the same in french, so I won't have the need. But it will be different for german people

Thanks! I'll merge this in and cut a V10 compatible release :)


Unnecessary execution of Vue watchers

There seems to be an issue with the Vue watchers, especially if a component is used multiple times. Then multiple executions occur - but interestingly not in every case.

Is this issue still on?
If yes, please report which components are used multiple times.


Normalization of channel streams to same out level

Hey all!
In regular Teamspeak client, there is an option to specify the volume per each client. It's helpful when speakers use different microphones.
I'm curious how it's possible to achieve some normalization to a specified level across all clients in the channel. I know that each client is a separate stream, and we pass relevant data to AudioHandler::handle_packet. But currently have no idea how to normalize this data. Do you have some ideas? Thanks!

Hi,
I’d say loudness normalization is out of scope for tsclientlib itself.
One way this can probably be implemented is by measuring the loudness of each stream with something like ebur128 and then setting the volume in the AudioHandler accordingly (AudioHandler::fill_buffer_with_proc can be used to get each stream on its own) so that everything ends up with the same loudness.

Thank you, @Flakebi! I'll check it out!


Hide tab from TabBar

this enables an individual tab to show or hide in the tabbar
const TabBar = TabNavigator( {

  Catalogue: {
		screen: Catalog,
		navigationOptions: {
          tabBarLabel:"Catalog",
          tabBarIcon: ({ tintColor }) => <Image source={require('./img/icon.png')} style={[styles.icon, {tintColor: tintColor}]} />
		}
	},
  Library: {
		screen: Library,
		navigationOptions: {
          tabBarLabel:"Library",
          tabBarIcon: ({ tintColor }) => <Image source={require('./img/icon.png')} style={[styles.icon, {tintColor: tintColor}]} />
		}
	}

	},{
    key: 'Catalogue',
    initialRouteName: 'Catalogue',
    tabBarComponent: TabBarBottom,
    tabBarPosition: 'bottom',
    tabBarOptions: {
        hideIndex : [ 1 ], // << == this option hides Library from the tab, but content still persists
        showLabel: true,
        showIcon: true
    },
})

usefull to have an instance running without lost of state or instance, and also still show its content by navigate

A few things in regards to this

Working based off of indexes is confusing. I think there could be a better way to implement this. Perhaps it's an option in navigationOptions instead?
Make sure to make any changes to TabBarTop as well
Documentation for new features is required.

I'm not sure such feature is worth complicating the API of TabNavigator. What exactly is your use case? Does this solve a common problem?

Hi, actually i was proposing this at first in order to have a hidden view ( no tab ) , but instance will be kept through cycles ( no unmount etc ).
i finally ended by implementing my own logic in stackNavigator to retain instances, so this pull request can be closed.

Check my answer here:
https://stackoverflow.com/questions/52362166/react-navigation-hide-one-tab/57515137#57515137


TypeScript check should fail the build if errors

Should typeChecker.check fail the build (or prevent the JS application from loading in dev) if there are errors?

It is deliberate to not error the build on type-checking errors, but I can see how it might be correct for e.g. production builds. Perhaps I should add a 'strict' mode which throws on error?

I have made a change so that if you use typeCheck: "strict", then the build will fail if there are compiler errors. Let me know if you have any issues, thanks. It's included in 2.1.0.


Tutorials: Adding new tutorial and some updates

Docs for<PHONE_NUMBER>8ad2c72cce927ca6ce484ef086dc28 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/509/docs/artifacts/html/index.html

Docs for 915accb40d5bb3ae968502d543280c9875c0afc3 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/515/docs/artifacts/html/index.html


[stable/traefik] Improve kubernetes section in values.yaml.

The values.yaml had the kubernetes section under the ingress section, which is not correct. This would've saved me a few minutes of searching and reading the source.

CLA procedure fulfilled.

Not sure if and how I should restart CircleCI testing, sorry.

I agree that the indentation is wrong and should be corrected, however, I would discourage the change wherein you've assigned kubernetes a default value of {} instead of just commenting it out. That is a nice thing to do in that it alleviates the need for extra nil checks in the chart's templates, but it's harder to explain to users that to configure any of the subordinate settings in that section, they must also delete the {}. It's easier and more intuitive for people to just uncomment stuff.

I'm happy to change that, didn't know what the default was and noticed some charts that to it that way (particularly stable/prometheus and stable/redis) and it's also used for the nodeSelector within this values.yaml. But I'll change it.

Yep. That change wasn't wrong, per se, but as it stands this chart is fine and easy to work with without that change. Of course the indentation issue is still a grrat catch. Thank you so much for noticing it and taking the initiative to fix it.

What is the status with this?

/ok-to-test

/test pull-charts-e2e


Fixup openshift versions

Description

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

LGTM

Deploy preview for calico ready!
Built with commit d5b606945ea19886ed99ff3c4b28d6fe29f46ad9
https://deploy-preview-2361--calico.netlify.com

Deploy preview for calico ready!
Built with commit e4ebbc584ae36fce39ec38ad9ec96f9febcd4553
https://deploy-preview-2361--calico.netlify.com


vs2022 mlgen

There is no mlgen that supports visual studio 2022. Currently, only vs 2017 and vs 2019

Thanks for posting. We currently have this in our backlog and are looking into it


Change/customize the shape of cursor when drawing?

I'm using a pen tablet to draw on excalidraw.  Anyway to change or customize the shape and size of the cursor? Or just don't change the cursor when drawing? Consider adding this function?
Also refer to https://www.reddit.com/r/ObsidianMD/comments/zfrn0d/configuring_pen_buttons_and_cursor_in_excalidraw/

I'd love to have the option to completely hide the cursor, since it has almost no use when using the pen on a touchscreen. The current UX is quite distracting because of the cursor.


Clarification for how to use SetApplicationAutoLaunch

I was wondering how get a built Unity app to auto launch with SteamVR. I can see other apps when I go to Settings -> Startup / Shutdown -> Choose Startup Overlay Apps.
I've found that I have to call AddApplicationManifest() and then SetApplicationAutoLaunch() to add it to the list, though I can't seem to make it work. I also see that at the root directory of my Unity project there is the .vrmanifest file, but when I build it I can't find a manifest file anywhere to add.
It would be really nice if there was an example of this somewhere though I couldn't find one.
Thanks!

Figured it out


force update repo when having git conflict

Problem Statement
Hi, as a Databricks platform engineer, I want to create update or replace repo
the current RepoAPI.update() calls fails due to a) merge conflicts b) repo does not exist
Proposed Solution
add a create update or replace repo
if repo has merge conflicts, deletes old repo and creates a new one from scratch
if repo does not exist, create new repo
I can make a PR if you'd like :)

Thanks for raising this. Generally speaking, if this functionality is useful for all users of Repos, then we can consider adding to the SDK. If not, we'd probably prefer not to include in the SDK. However, such a function should be relatively easy to implement using the SDK as a combination of those three API calls.

it is useful, I use it at work, my question is do you think it is useful for this project and I can make a PR?


Windows build fails to sign the application

What should we do?
Update our Certificates we use to sign the application during the build process. The windows certs expired on Apr 11.
cf. https://github.com/camunda/camunda-modeler/actions/runs/8681071392

[ ] Migrate https://github.com/camunda/camunda-modeler/blob/develop/.github/workflows/BUILD_ON_DEMAND.yml
[ ] Migrate https://github.com/camunda/camunda-modeler/blob/develop/.github/workflows/RELEASE.yml
[ ] Migrate https://github.com/camunda/camunda-modeler/blob/develop/.github/workflows/NIGHTLY.yml

Why should we do it?
To ensure we can release the camunda modeler on windows

As part of this change we want to migrate the certificate handling over to vault (cf. https://github.com/bpmn-io/internal-docs/issues/802).

Reached out to internally (IT) for further investigation.

Shared updated certificate with @marstamm; you should now be unblocked to work on this issue.

Cross-posting from internal Slack:

The main problem we are facing is the increased security standards for storing the private keys. We will move to a cloud based certificate provider (DigiCert) and kicked of the purchasing process
Until then and as fallback, signing is a manual step using the hardware token on a local machine

[Update] We disabled Code signing on Windows for now. @philippfromme has the physical token for backup signing. DigiCert purchase is still in progress

I just asked @KerstinHebel for update on https://helpdesk.camunda.com/support/tickets/14320. What is the status of "DigiCert purchase"? I know that we are forced right now to use a hardware key, but I believe it's unhealthy to require from @philippfromme signing the executable.


Add hyperlink pointing to a heading

Is there any way a block of text can be hyperlinked to a heading? Similar to the navigation in docx. Clicking the hyperlink will take you to the heading.

you mean like inserting a reference somewhere in the document and clicking on it would take you to some other place in the document?

Yes, that would be the aim. I am specifically looking to link to a heading that is generated by add_heading() function, but a generic solution would also work.

once I was working on something similar
first, you have to add a bookmark to the paragraph (heading paragraph in your case)
def add_bookmarkStart(paragraph, _id):     name = '_Ref_id_num_' + _id     start = OxmlElement('w:bookmarkStart')     start.set(qn('w:name'), name)     start.set(qn('w:id'), str(_id))     paragraph._p.append(start)     return name
then you should create another paragraph in a way like this
def append_ref_to_paragraph(paragraph, refName, text = ''):     # run 1     run = paragraph.add_run(text)     r = run._r     fldChar = OxmlElement('w:fldChar')     fldChar.set(qn('w:fldCharType'), 'begin')     r.append(fldChar)     # run 2     run = paragraph.add_run()     r = run._r     instrText = OxmlElement('w:instrText')     instrText.text = 'REF ' + refName + ' \h'     r.append(instrText)     # run 3     run = paragraph.add_run()     r = run._r     fldChar = OxmlElement('w:fldChar')     fldChar.set(qn('w:fldCharType'), 'end')     r.append(fldChar)
you can give this paragraph any style you like (hyperlink, etc..)
and when you ctr+right click on this paragraph it should take you to the heading paragraph

Can i have an example of this? i am creating a document, where on click on heading number the document to should display the the paragrah. I have been looking for this since months


Fixes a couple of test related issues for debezium-core

fixes a java.sql.Date conversion test to take into account zone offsets
makes sure the ZK DB is closed during testing, otherwise file handles may leak and cause test failures

Excellent. Thanks, @hchiorean.

Merged onto the 'master' branch and cherry-picked onto the 0.3.x branch. This latter branch is new, as the initial candidate for 0.3.0 was created yesterday and is currently undergoing tests.


See issue #60

We had other code that we ported into Praxis that was using TerminalTable already, so I ended up moving the routes task to it as well in #105.


Reduce the verbosity install and update commands

Reduce the verbosity of install and update command and show it only when the --log-level is set to debug or on failures.
Expected behavior
✔ ~ gauge install ruby
.......................
Successfully installed ruby plugin

Actual behavior
✔ ~ gauge install ruby
Gathering metadata for ruby

Downloading gauge-ruby-0.4.1-linux.x86_64.zip
.......................
Installing plugin ruby 0.4.1
Successfully installed plugin 'ruby'.

Gauge version
Gauge version: 0.9.0.nightly-2017-07-07

Modify the update command too.

related #696

Fixed via #724, should be available in nightly >= 18/7/2017

Previously during installation I got the version currently installed. That is useful.
Change the message to
Successfully installed plugin  .


action get should offer a delete button

we have this for kubectl get

this is so far in the backlog right now that i will close it. future: this is not to say it wouldn't be good to have.


Simplify APIs

I feel there is some boilerplate code that can be deleted by exposing the objects directly. For instance, in graphics.hpp

 void set_speed(const Magnum::Vector2& speed) { _magnum_app->camera().set_speed(speed); }
                void set_near_plane(double near_plane) { _magnum_app->camera().set_near_plane(near_plane); }
                void set_far_plane(double far_plane) { _magnum_app->camera().set_far_plane(far_plane); }
                void set_fov(double fov) { _magnum_app->camera().set_fov(fov); }
                void set_camera_params(double near_plane, double far_plane, double fov, size_t width, size_t height) { _magnum_app->camera().set_camera_params(near_plane, far_plane, fov, width, height); }

                Magnum::Vector2 speed() const { return _magnum_app->camera().speed(); }
                double near_plane() const { return _magnum_app->camera().near_plane(); }
                double far_plane() const { return _magnum_app->camera().far_plane(); }
                double fov() const { return _magnum_app->camera().fov(); }

=> this can easily be replaced by a camera() accessor (then we can call fov, far_plane(), etc on the camera)

What is the convention: should we return a gs::Camera& or a gs::Camera*` ? I see both in the code (for instance, a pointer to the magnum_app but a reference to the lights)

should we do the same for magnum_app?

  void set_recording(bool recording, bool recording_depth = false) { _magnum_app->record(recording, recording_depth); }
                bool recording() { return _magnum_app->recording(); }
                bool recording_depth() { return _magnum_app->recording_depth(); }

                bool shadowed() const { return _magnum_app->shadowed(); }
                bool transparent_shadows() const { return _magnum_app->transparent_shadows(); }
                void enable_shadows(bool enable = true, bool transparent = true) { _magnum_app->enable_shadows(enable, transparent); }

... or you want to hide this app?

What is the convention: should we return a gs::Camera& or a gs::Camera* ? I see both in the code (for instance, a pointer to the magnum_app but a reference to the lights)

This is true. We should only keep one of them. I would say that I prefer references. A small care should be taken with references and the python bindings, but I can be checking this.

should we do the same for magnum_app?

I do not remember the reason why I decided to re-write those functions. I mean I am giving the magnum_app pointer so one could use this. I think that initially I wanted to hide magnum_app, but then I needed it. Let me check if we can hide it. I think that we should hide it if possible, because this can change and it should not affect the public API.

Yes, I agree that the Magnum_app is not as intuitive as accessing a camera or a light.
At the same time, we could merge Graphics and BaseApplication quite easily.


chore: cleanup unused i18n MFE pattern

Description
Standard MFE pattern cannot be used in paragon since it would introduce circular dependency between paragon and @edx/frontend-platform.
This PR cleans up some unused variables in Makefile.
Refs: FC-0012 OEP-58
Merge Checklist

[ ] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[ ] Does your change adhere to the documented style conventions?
[ ] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[ ] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[ ] Were your changes tested in the example app?
[ ] Is there adequate test coverage for your changes?
[ ] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

Thanks for the pull request, @OmarIthawi!  Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

Hi @OmarIthawi - is this ready for review?

Yes @mphilbrick211. This is ready.

Hi @adamstankiewicz - would you mind taking a look at this and merging if all looks good? Thanks!

@OmarIthawi Even though your pull request wasn’t merged, please take a moment  to answer a two question survey so we can improve your experience in the future.