Property for value displayed by snippet

Codecov Report

Merging #12 into master will decrease coverage by 0.23%.
The diff coverage is 84.21%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
- Coverage   95.16%   94.92%   -0.24%
==========================================
  Files           5        5
  Lines         124      138      +14
==========================================
+ Hits          118      131      +13
- Misses          6        7       +1

Impacted Files
Coverage Δ

packages/rdf-editor/src/RdfEditor.js
92.94% <60.00%> (-0.97%)
:arrow_down:

packages/rdf-snippet/src/RdfSnippet.js
97.61% <92.85%> (+0.84%)
:arrow_up:

Continue to review full report at Codecov.

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


Better support for schema changes in transactions

Background: https://airtable.com/tblD3oZPLJgGhCmch/viw5Jsp2TrY3it9Yr/reci8v1XFZBL8aVU8
PM: @awoods187
Eng: @vivekmenezes

@vivekmenezes I tried running all of the Examples of statements that fail due to the no schema changes within txns limitation and they all still fail in CRDB version v19.1.0-beta.20190304.
Therefore it seems like there is no additional documentation work needed here.  Do you agree?

@vivekmenezes why do these still fail?

Yes those still fail and for good reasons. We don't expect to fix them
anytime soon. In fact we can't fix them because they involve updating the
schema cache and the schema store in the same txn.
On Thu, Mar 7, 2019 at 3:00 PM Andy Woods<EMAIL_ADDRESS>wrote:

@vivekmenezes https://github.com/vivekmenezes why do these still fail?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cockroachdb/docs/issues/4017#issuecomment-470672149,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALOpBCKkYgJ0UKND_Sm24wQHp9m1t9ZPks5vUW_NgaJpZM4YOdxN
.

--
"I've never found understanding CockroachDB to be a problem. Understanding
the architecture is easy, the difficulty comes when I immerse myself in it.
It's not the understanding that's hard, getting inside it and finding
myself rocking in the deep is when I find myself circling around something
that I want to wrestle with. It is often swimming back from such a
challenge when I feel fulfilled--the pleasure in reacquainting myself with
bors r+"

@vivekmenezes and @awoods187 based on:

The conversation in this issue
Re-reading the current Online Schema Changes docs and re-running the various SQL statements described there with CockroachDB CCL v19.1.0-beta.20190318 and getting the same results
Re-reading and testing SQL from the CockroachDB issue linked from the AirTable entry (https://github.com/cockroachdb/cockroach/issues/24919)

I don't think there is additional documentation work needed here, and this issue can be closed.  Do you agree with that assessment?

I agree


port: [#6588][#4482] UserId not being passed to AzureDiagnostics

#minor
Description
This PR allows adding the userId property which was empty when displaying the AzureDiagnostics table in the Log Analytics workspace resource.
Specific Changes

Added userId property to the queryKnowledgebaseRaw request in the LanguageServiceUtils file.
Added userId property to the QnAMakerOptions interface.
Updated parameter sending of queryKnowledgebaseRaw, allowing to send the userId to the QnAMakerOptions using the context activity

Testing
The following image shows the AzureDiagnostics log with the userId value.

/promoted 4493


[ALLUXIO-2989] [ALLUXIO-2990] Extend the validateEnv command to check max user processes

https://alluxio.atlassian.net/browse/ALLUXIO-2989
https://alluxio.atlassian.net/browse/ALLUXIO-2990
Added extensions for validateEnv command to check user limits for number of open files and number of processes.

@yupeng9 PTAL.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16426/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16438/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16447/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16462/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16464/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.master.file.FileSystemMasterIntegrationTest.concurrentFree
Test FAILed.

Jenkins, test this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16467/
Test PASSed.


Support AutoCloseable in Closeables

Support AutoCloseable in Closeables

Updated. Thanks for the review!

What about letting JVM do the heavy lifting with exception handling?
public static void closeQuietly(AutoCloseable... closeables)
        throws Exception
{
    if (closeables == null) {
        return;
    }
    closeQuietly(closeables, 0);
}

private static void closeQuietly(AutoCloseable[] closeables, int currentIndex)
        throws Exception
{
    if (currentIndex >= closeables.length) {
        return;
    }
    try (AutoCloseable current = closeables[currentIndex]) {
        closeQuietly(closeables, currentIndex + 1);
    }
}


Update language configuration

I propose the following two small changes:

make $...$ auto closing. IMHO, this is not something, that users should be actively discouraged from using (in contrast to $$...$$).
add { to autoclosebefore. This is useful for adding optional parameters to already existing code, in particular for adding parameters to \usepackage{...}

Cheers and keep up the good work!

I agree with adding { to autoclosebefore.  I am more reserved with auto closing $ as there have been a lot of discussions in LaTeX-Workshop on this, see for instance https://github.com/James-Yu/LaTeX-Workshop/issues/365. Fiddling with auto closing for $ requires a lot of care and needs heavy testing. You should rather define a snippet to insert $ ... $ with the cursor between the $.

Because of microsoft/vscode#143187, it is very difficult to test change in the language definition reliably. In particular, I want to make sure it does harm LaTeX-Workshop. I will until microsoft/vscode#143187 is closed to deal with this PR.


This is really cool package. But please see my textarea

How can people use this package if this not solved soon. You know what.
This is happened in my browser console when I click the browse button (Search Folder)
Uncaught SyntaxError: Unexpected token )
bootstrap.min.js:6 Uncaught Error: Bootstrap's JavaScript requires jQuery
    at bootstrap.min.js:6
(anonymous) @ bootstrap.min.js:6
jquery-ui.min.js:6 Uncaught ReferenceError: jQuery is not defined
    at jquery-ui.min.js:6
    at jquery-ui.min.js:6
(anonymous) @ jquery-ui.min.js:6
(anonymous) @ jquery-ui.min.js:6
cropper.min.js:10 Uncaught ReferenceError: jQuery is not defined
    at cropper.min.js:10
    at cropper.min.js:10
(anonymous) @ cropper.min.js:10
(anonymous) @ cropper.min.js:10
jquery.form.min.js:11 Uncaught TypeError: e is not a function
    at jquery.form.min.js:11
    at jquery.form.min.js:11
    at jquery.form.min.js:11
(anonymous) @ jquery.form.min.js:11
(anonymous) @ jquery.form.min.js:11
(anonymous) @ jquery.form.min.js:11
script.js:3 Uncaught ReferenceError: $ is not defined
    at script.js:3
(anonymous) @ script.js:3

Solve. I change the jQuery version to be latest


show vault namespace option for cluster-wide (SA auth)

When kubernetes authentication method is selected, we disabled the Vault Enterprise Namespace field in PR: https://github.com/openshift/console/pull/10998
Need to enable it again for cluster-wide encryption.

/test odf-console-e2e-aws

/lgtm

/cherrypick release-4.11

/cherrypick release-4.11-compatibility

/cherrypick release-4.11-compatibility


XLM-R failing 'omegaconf._utils' has no attribute 'is_primitive_type'

we are noticing a new failure:
Traceback (most recent call last):
  File "xlmr/ootb/xlmr.py", line 178, in <module>
    run()
  File "xlmr/ootb/xlmr.py", line 142, in run
    xlmr = get_model()
  File "xlmr/ootb/xlmr.py", line 29, in get_model
    fairseq_xlmr_large = torch.hub.load('pytorch/fairseq:main', 'xlmr.large')
  File "/opt/conda/lib/python3.7/site-packages/torch/hub.py", line 399, in load
    model = _load_local(repo_or_dir, model, *args, **kwargs)
  File "/opt/conda/lib/python3.7/site-packages/torch/hub.py", line 428, in _load_local
    model = entry(*args, **kwargs)
  File "/root/.cache/torch/hub/pytorch_fairseq_main/fairseq/models/roberta/model_xlmr.py", line 44, in from_pretrained
    **kwargs,
  File "/root/.cache/torch/hub/pytorch_fairseq_main/fairseq/hub_utils.py", line 75, in from_pretrained
    arg_overrides=kwargs,
  File "/root/.cache/torch/hub/pytorch_fairseq_main/fairseq/checkpoint_utils.py", line 421, in load_model_ensemble_and_task
    state = load_checkpoint_to_cpu(filename, arg_overrides)
  File "/root/.cache/torch/hub/pytorch_fairseq_main/fairseq/checkpoint_utils.py", line 339, in load_checkpoint_to_cpu
    state = _upgrade_state_dict(state)
  File "/root/.cache/torch/hub/pytorch_fairseq_main/fairseq/checkpoint_utils.py", line 677, in _upgrade_state_dict
    state["cfg"] = convert_namespace_to_omegaconf(state["args"])
  File "/root/.cache/torch/hub/pytorch_fairseq_main/fairseq/dataclass/utils.py", line 405, in convert_namespace_to_omegaconf
    with omegaconf_no_object_check():
  File "/root/.cache/torch/hub/pytorch_fairseq_main/fairseq/dataclass/utils.py", line 367, in __init__
    self.old_is_primitive = _utils.is_primitive_type
AttributeError: module 'omegaconf._utils' has no attribute 'is_primitive_type'

This is because omegaconf recently upgraded and changed its API, see upstream fix: https://github.com/facebookresearch/fairseq/pull/4440

@amathews-amd just reminder that upstream hasn't merged the fix yet. So maybe it is better to pin omegaconf version to an older version.

@amathews-amd Yes, I'd suggest pinning omegaconf version for now. With my current bandwidth it'll take me a while to shift from pulling the model from torch hub to switching to fairseq.

fixed by pinning hydracore
pip install hydra-core==1.1.2


Lens derive and lens_wrap!()

I'd love input on everything, of course, but I'm especially hoping for some suggestions on the lens_wrap!() macro. For instance, right now it can parse this:
    let label = DynLabel::new(|data: &String, _env| data.clone());
    let display = lens_wrap!(label, CalcState::value);

but not this:
    let display = lens_wrap!(DynLabel::new(|data: &String, _env| data.clone()), CalcState::value);

Also, the CalcState::value syntax itself might need some bikeshedding. Not exactly sure how discoverable it is outside of copy / pasting from existing examples.
Additionally, the folder pollution bugs me, especially for something this small. Maybe there's somewhere better to hide all this other than the root level?

After a long slumber I'm finally revisiting this! Borrowing from the structure of the Data derive macro was helpful, and I'm sure there are ways this could be cleaned up further by someone with a stronger understanding.
Sorry for the discontinuity between the commits... I did a bit too aggressive of a rebase and the files needed to be in new locations anyways.
I'm dropping the LensWrap macro for now for simplicity's sake (and because @cmyr raises some good points about ergonomics!)

Cool! I'll open an issue for further Lens work.
Afaik the only failure states here are at compile time. Am I misunderstanding?

Oops yea I wasn't clear: allowing lenses to get items from collections is fallible, because you might have an invalid index.


sample pipeline jupyter notebook on binder errors-out

Describe the bug
sample pipeline jupyter notebook errors out due to undefined variable
To Reproduce
Steps to reproduce the behavior:

Go to binder
Click on sample pipeline jupyter notebook
Run

Expected behavior
Jupyter notebook on binder should run without exception
Additional context
error while executing cell:
pipeline_output = rt.execute_pipeline(pipeline, ExecutionType.FIT, pipeline_input)
node_0_output = pipeline_output.get_xyrefs(node_0)

In [74]:

outputs[0]

---------------------------------------------------------------------------
NameError                                 Traceback (most recent call last)
<ipython-input-74-a45df8d4a457> in <module>
----> 1 outputs[0]

NameError: name 'outputs' is not defined

@asm582 this issue was fixed with commit db883ecf6a43708dcfec264387d79ea8ef795d87. Can you pull the latest and retry?

Interestingly, I thought the binder service always pulls the latest code and runs it. Maybe my service was using stale code from the morning.
Anyways it works now, closing the issue, thanks.


Admin Console

Precondition:

As a game admin
Not currently logged in
Actions:

start the game
start the admin console
query the list of available commands
Postcondition:

I can now select and execute an available command or close the admin console

Started the /admin endpoint, assuming the preconditions for now.

Got a cli call to endpoint working. Going to break into subtasks for the individual interactive feaures


feat: Add support for "json" bindings

We've had support for "json" bindings for a long time, but never added them to wrangler1.. oops! This is nice because you can include complex values, and you don't need to use things like parseInteger(env.variable) in your code.
# wrangler.toml
[vars]
text = "plain ol' string"
count = 1
complex = { enabled = true, id = 123 }

/cc @mrbbot Since you probably didn't know this existed! 😅

^ This was my experience with wrangler 1 too, which threw me for a loop.


[WIP] Some minor changes to HDFS and to docs about globs

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
For changelog. Remove if this is non-significant change.
Category (leave one):

Minor improvement

For #5371 issue.

This PR moved to  #7016


Chrome 85 has trouble to display the migration tool

Steps to reproduce
Just for fun, I tried to convert this old code but the web UI became completely unresponsive when trying to display the single 3486 lines long file. After a while I saw some code, but as soon as a started scrolling, the display of lines stopped after a 300+ lines before becoming unresponsive again and then spitting out a few more lines. I'm using Chrome 85, latest dev build.
I also tested Firefox <IP_ADDRESS> and while that Browser complained about "starting slow" it managed to display the file.
What did you expect to happen?
It should also work in Chrome, I guess.
What actually happened?
Screenshots are appreciated

Dart SDK version: 2.9.0-21.0.dev
Thanks for filing!

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


ion-calendar is not a known element outside of src/app

Ionic version:  (check one with "x")
[ ] 2.x
[ X] 3.x
[ ] 4.x
Ion2-calendar mode:  (check one with "x")
[X ] components mode
[ X] modal mode
I'm submitting a ...  (check one with "x")
[ ] bug report
[ ] feature request
[X ] help me
Current behavior:

Hello.
I've installed the plugin and imported it on app.modules as described.
The problem is I'm only able to use  component in the app/app.html file. If I try using it anywhere else, like in pages/*.html, the component tag is highlighted in red as an error and the message says:

[Angular]
'ion-calendar' is not a known element:

If 'ion-calendar' is an Angular component, then verify that it is part of this module.
If 'ion-calendar' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message.

Expected behavior:
Being able to use the calendar component anywhere.
Steps to reproduce:
I simply followed the instructions.
ionic info

cli packages: (/usr/local/lib/node_modules)

    @ionic/cli-utils  : 1.19.1
    ionic (Ionic CLI) : 3.19.1

global packages:

    cordova (Cordova CLI) : 8.0.0

local packages:

    @ionic/app-scripts : 3.1.8
    Cordova Platforms  : browser 5.0.3
    Ionic Framework    : ionic-angular 3.9.2

System:

    Android SDK Tools : 26.0.2
    ios-deploy        : 1.9.2
    Node              : v8.9.1
    npm               : 5.6.0
    OS                : macOS High Sierra
    Xcode             : Xcode 9.2 Build version 9C40b

Environment Variables:

    ANDROID_HOME : /Users/jhonatasrosendo/Library/Android/sdk

Misc:

    backend : legacy

Lazy loading? need import to your submodule

Same here...


new dataset

i am trying to create dataset for peace sign. But new threshold images are not saved in my PeaceTest folder even after i changed code in line 103
problem sloved

So you have solved your problem it seems..Cool.. Do tell me if you find this repository interesting and useful :).. @ashReal


PHASE II: Implement a flexible Raven instead of pre-defined Raven model setups

Description
To do in maintenance phase as added feature
At the moment, we are using RAVEN to generate 4 hydrological models, thus neglecting the main feature of Raven, i.e. the capacity to mix-and-match submodules to create new hydrological models.
We should provide a way for users to select modules to combine and make a fully-flexible Raven model instead of those four fixed models.

We will close this as it seems that this is too complex and dangerous for unassuming users. Therefore we will provide more fixed model configs instead.


[stable/mongodb-replicaset] control restart procedure

FEATURE REQUEST
After spending a day with a MongoDB consultant, there are some best practices that are hard to achieve with mongodb in this chart:

When restarting the members of a replicaset, it is best to restart all the secondaries first. Before restarting the primary it is a good idea to execute rs.stepDown() to force the primary to step down and initiate the election of a new primary. See https://docs.mongodb.com/manual/reference/method/rs.stepDown/index.html

After restarting a mongo replicaset node, it's a good idea to allow the replication to catch up before shutting down the next node. rs.status() gives this information in JSON format. See https://docs.mongodb.com/manual/reference/method/rs.status/#rs.status

My understanding is that blindly restarting the primary node on a heavily loaded mongodb replicaset could lead to data loss as there may be in-memory writes which have not been flushed to the oplog yet.
I don't know that StatefulSets will allow any control over the order of restarting, however a preStop container hook could run a command to check if it is primary and if so run the rs.stepDown() command.
On starting up, a readinessProbe could run the rs.status() command and only return when the replication lag is below a given threshold.
Version of Helm and Kubernetes:
$ k version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:17:39Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.9", GitCommit:"57729ea3d9a1b75f3fc7bbbadc597ba707d47c8a", GitTreeState:"clean", BuildDate:"2018-06-29T01:07:01Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

$ helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

Which chart:
stable/mongodb-replicaset

can rs.stepDown be called on a secondary? Because the preStop command will be ran on all instances. StatefulSets are by design have a specific order of startup and shutdown, but any replica in the StatefulSet can become primary at any time (for example, due to a network partition). I've thought before about increasing the first replica priority so he's more likely to be primary.

This functionality is already present.

These charts are entirely community supported, so PRs welcome if you have specific changes you want.

rs.stepDown() will fail on secondaries:

The method is only valid against the primary and throws an error if run on a non-primary member.

so maybe some JS to only run if the node is primary? Something like if (db.isMaster()) rs.stepDown(). I don't know JS though so add correct syntax....


Add post-processing callback for initial condition

This feature request references https://github.com/PrincetonUniversity/athena-public-version/commit/20145fef7ead1f47d95293e14e140c4167c5005f.
According to the wiki, MeshBlock::ProblemGenerator() describes the initial condition mesh block by mesh block. However, mesh blocks (or their owning processes) can't communicate with one another at this stage. This is inconvenient if the initial condition must satisfy some global constraint. A fix is to introduce a post-processing stage for the initial condition.
For example, we may want the total mass in the simulation domain to match some target value. If the total mass isn't analytic, we must calculate the total mass from the output, and start a new run with different parameters. This approach is very error-prone.
The proposed diff is as follows; the naming of the callback is up to the code maintainers. The callback is an "epilogue" to the initial condition, so it is in some sense the opposite of Mesh::InitUserMeshData(), which is the prelude:
diff --git a/src/mesh/mesh.cpp b/src/mesh/mesh.cpp
index 70f2ef1..a018d5b 100644
--- a/src/mesh/mesh.cpp
+++ b/src/mesh/mesh.cpp
@@ -1380,6 +1381,10 @@ void Mesh::Initialize(int res_flag, ParameterInput *pin) {
       for (int i=0; i<nblocal; ++i) {
         MeshBlock *pmb = my_blocks(i);
         pmb->ProblemGenerator(pin);
+      }
+      Mesh::ProblemGeneratorEpilogue();
+      for (int i=0; i<nblocal; ++i) {
+        MeshBlock *pmb = my_blocks(i);
         pmb->pbval->CheckUserBoundaries();
       }
     }

It is an interesting idea. I would like to see a full implementation of this before offering my opinion one way or the other. And also some more use cases that would really motivate this new feature (in your example there are likely multiple less intrusive alternatives to getting the same initial condition).
Also, what does 20145fe have to do with this?

@felker Thanks for the reply. I'm offering this up as an idea; I'd be interested to see what you guys think would be the best way to implement it.
For what it's worth, my use case is I want to scale the magnetic field so that the volume-integrated plasma beta matches some specified value. Because I have multiple magnetic-field topologies, changing topology would mean manually changing the magnetic field strength as well, which is a disaster waiting to happen.
 For example, issues at matplotlib have started requiring detailed version information, so I'm trying to do something similar.

I have the same issue with tuning plasma beta in every simulation I run, so I definitely understand the situation.
Fortunately, this particular problem converges very quickly with the workflow of dump initial conditions -> measure beta -> adjust field strength parameter.
One thing that occurs to me, though, is there might well be cases where the tuning amounts to some nonlinear root find requiring multiple iterations, with the initial conditions depending in a complicated way on the outcome of some analysis. If the Epilogue function determines convergence has not been attained, will it have to signal the code to retry ProblemGenerator with new parameters? This could rapidly get complicated.
I'll also add the one can add (and people have done this hack) MPI calls to ProblemGenerator, with care. If you have 1 block / rank, it will just work. With more than that, you have to make sure only 1 block per rank is directly involved in communication.

Manual iteration is certainly doable, but it's always a good idea to take the human factor out of mechanical operations.
Regarding initial conditions that need iteration, one could make MeshBlock::ProblemGenerator() a no-op and have all the iterations done in the epilogue. The user could define, for example, setup_trial_ic(MeshBlock *mb, T params) and call it in the iteration. In the worst case, the epilogue could fail fast and exit, inviting user intervention.


Update SNS.swift

Received SNS object has uppercased "URL" coding keys.
Motivation:
The received SNS object has uppercased "URL" coding keys. The object can not be decoded otherwise. Currently, the coding keys contain a lower case "Url", for example "SigningCertUrl" but should be "SigningCertURL".
{
  "Timestamp": "2021-10-08T11:18:40.043Z",
  "SigningCertURL": "https://sns.eu ****",
  "MessageId": "776e6308-8c44-5ee ****",
  "Type": "Notification",
  "SignatureVersion": "1",
  "Signature": "s71McLg8d9OP86E4a *****",
  "TopicArn": "arn:aws:sns:eu-west-1:06 *****",
  "UnsubscribeURL": "https://sns.eu-w****",
  "Message": "{\"action\":\"upload_document_version\",\"entityId\":\"1633691914791-1796da229943***aace80d5e023f3***c\",\"entityType\":\"DocumentVersion\",\"organizationId\":\"d-9367073c36\",\"parentEntityId\":\"516d7ab0537aff5d39a469439c*****2d0d4\",\"parentEntityType\":\"Document\"}"
}

Modifications:
The coding keys string value has been changed.
Result:
We can now use the decoded object with dot notation.

@swift-server-bot test this please

closed since this is has been outstanding for so long


capi: replaced bounds() api with the latest.

The next api of c++ version has been deprecated
Tvg_Result tvg_paint_get_bounds(const Tvg_Paint* paint, float* x, float* y, float* w, float* h);
instead, we introduce the next one under the beta.
Tvg_Result tvg_paint_get_bounds(const Tvg_Paint* paint, float* x, float* y, float* w, float* h, bool transformed);

@hermet. Probably old API is used in capiPaint.cpp. You plan to modify test in separated commit ?

@mihashco yep, i added in this patch thread.


expose handlebars template in the app.js

We had setup with browserify where we had different offerings having same handlebars templates with some changes. We used to expose a template and make a different build for each offerings and then require it from app.js
{
src: path.join('hsn-common/assets', customer, 'receipts/shop.hbs'),
expose: 'receiptTemplates/shop'
}
and in a commonjs file we were requiring the shop as
require(receiptTemplates/shop)
app.js used to be common. I guess it was called browserify external require.
Is it possible to get this setup work with webpack ?

Could you re-open at Stack Overflow? Thanks.


Pydantic boolean settings cached

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
class Settings(BaseSettings):
    """Load environment variables to python objects using pydantic."""

    logging_enabled: bool = False
    logging_config_filename: str = "./logs/error.log"
    logging_config_level: str = "ERROR"
    training_data_enabled: bool = False
    api_docs_username: Optional[str]
    api_docs_password: Optional[str]
    api_docs_auth_enabled: bool = False
    testing: bool = False

    class Config:
        env_file = ".env"

Description
Generally FastAPI is able to read data from the .env file but it is then somehow cached. Restarting the server does not re-read the .env values. Adding a new or renaming an setting works as expected. However, changing a value of a previously read setting has no effect. Even when removing the env_file = “.env” bit.
The issue seems to affect boolean values only. However, it does handle False vs. True properly, both via .env as well as via proper env variables.
Operating System
Linux, macOS
Operating System Details
No response
FastAPI Version
0.68.2
Python Version
3.9
Additional Context
No response

I couldn't reproduce this.
I used your file as a config.py, this main.py:
from fastapi import FastAPI
from config import Settings

app = FastAPI()
settings = Settings()

@app.get("/")
async def root():
    return settings

and this .env:
<EMAIL_ADDRESS>TESTING=false

Changing either API_DOCS_USERNAME's string or TESTING boolean on my .env works upon reloading the server. The values in these settings are updated as expected.

thank you for checking. but sorry, by now I am pretty sure its caused by VSCode and forgot to close this ticket.
https://github.com/microsoft/vscode-python/issues/18203


Support different authentication types for a REST API

So, I have used amplify api add and now have GraphQL and REST API in my project, but the auth for my REST API is using Cognito. How can I change that? I would like to use API Key authentication for my REST API and keep using Cognito for the rest. I can not find any reference in the doc and by running amplify auth add again I get the message:

Auth has already been added to this project. To update run amplify update auth.

If this is currently not supported going through some amplify-cli command or by editing some CloudFormation template, then it can be a candidate for a feature request.

@kstro21 The API Gateway service doesn't have API Keys as one of their authentication methods I beleive. As a part of the CLI we support Cognito for auth/unauth access which you could probably use.

@kaustavghosh06 thanks for the response. I'm currently using Cognito for auth/unauth and it works OK, but I'm trying to switch to API Keys and Usage Plans as described here https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-usage-plans.html
Here is an example that describes the process using de AWS API Gateway console https://medium.com/@zeebaig/protect-aws-api-gateway-endpoints-using-api-keys-5d8c066c5a5d
If it can be configured using the console, it can be configured using CloudFormation too, right?

+1 for this feature! It would be really nice to have different authentication methods for a REST API

how i have set code API Keys in  SAM deploy template. Please help me

This is an awesome project and I was wondering as to why the CLI doesn't support adding API keys as auth type for REST APIs?

+1

So I have found that you cannot do this via the amplify-cli. However for anyone searching for a way to do this and not have amplify blow out your api-key on every deploy I have this solution.
You need to modify the file amplify/backend/api/<your_api_name>/<your_api_name>-cloudformation-template.json.
In the section labeled "x-amazon-apigateway-any-method" you need to add the following snippet. If you have multiple resources you will need to add the section to each defined "x-amazon-apigateway-any-method" section.
 "security": [
     {
          "api_key": []
     }
],

Note if you are doing other auth methods in addition to api-key you will need to add the api_key to the security section that is already there.
 "security": [
     {
          "api_key": []
     },
    {
        "sigv4": []
    }
],

Additionally, you need to add the "api_key" to the "securityDefinitions" section.
"api_key": {
    "type": "apiKey",
     "name": "x-api-key",
      "in": "header"
}

Larger Example:
"x-amazon-apigateway-any-method": {
  "consumes": [
    "application/json"
  ],
  "produces": [
    "application/json"
  ],
  "parameters": [
    {
      "in": "body",
      "name": "RequestSchema",
      "required": false,
      "schema": {
        "$ref": "#/definitions/RequestSchema"
      }
    }
  ],
  "responses": {
    "200": {
      "description": "200 response",
      "schema": {
        "$ref": "#/definitions/ResponseSchema"
      }
    }
  },
  "security": [
    {
      "api_key": []
    }
  ],

  "x-amazon-apigateway-integration": {
    "responses": {
      "default": {
        "statusCode": "200"
      }
    },
    "uri": {
        "Fn::Join": [
          "",
          [
            "arn:aws:apigateway:",
            {
              "Ref": "AWS::Region"
            },
            ":lambda:path/2015-03-31/functions/",

            {

                "Ref": "functionnumberlookupArn"
            },

            "/invocations"
          ]
        ]
      },
    "passthroughBehavior": "when_no_match",
    "httpMethod": "POST",
    "type": "aws_proxy"
  }
}

"securityDefinitions": {
  "sigv4": {
    "type": "apiKey",
    "name": "Authorization",
    "in": "header",
    "x-amazon-apigateway-authtype": "awsSigv4"
  },
  "api_key": {
    "type": "apiKey",
    "name": "x-api-key",
    "in": "header"
  }
},

I hope this helps some people.

@egreenmachine thanks for sharing. ^ This works!

This solution is not working in the latest amplify version.
Since now there is only cli-inputs.json file, and the cloud formation are generating during the amplify push we can't make custom changes in the cloud-formation file.
Is there any way we can do it in amplify version after 7 ?

yea, I am wondering about the same thing as @iOrcohen. :/

I need this also...

I just open #10085, where I'm trying to override security for methods, something similar to @egreenmachine suggests


Refactor repository controller

Description of your changes

Fixes and improvements:

Prevent the controller from unnecessarily updating the live repository CR spec
Move BlockCreations under BranchProtectionRestrictions to avoid infinite reconciliation loops when it's set to true while BranchProtectionRestrictions are disabled
Improve error handling of nil pointers
Improve code DRYness
Follow Kubernetes SIG-ARCHITECTURE guidelines for optional CRD fields
Reduce the number of optional fields to reduce code complexity
Improve code comments
Update examples

I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Thank you again for this great contribution @iul1an !


Unicode

See #114
@dirks I'm trying to reproduce and fix the bug here. Please comment :-)

Codecov Report

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

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


Update server Dockerfile build kit

DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
            Install the buildx component to build images with BuildKit:
            https://docs.docker.com/go/buildx/

Duplicate with https://github.com/florian-glombik/workplace-reservation/issues/46


bug: virtual_network_enabled = false

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Versions

Please paste the output of terraform version command from within the initialized directory:
Terraform v1.5.6
on linux_arm64

Please enter the module version that you are using:
module "lz_vending_
  source  = "Azure/
  version = "4.1.0"

Description
When I have  virtual_network_enabled = false and have a vnets section initalised in tfvars, it still creates the vnets.
The expected behaviour is to ignore the vents.
Resource groups work as expected.
Steps to Reproduce

Define tfvars with vnets
virtual_network_enabled = false
Terraform plan will still want to create vnets

I propose:
main.virtualnetwork.tf
`
module "virtualnetwork" {
source           = "./modules/virtualnetwork"
subscription_id  = local.subscription_id
virtual_networks = var.virtual_network_enabled ? var.virtual_networks : {}
location         = var.location
depends_on = [
module.resourcegroup_networkwatcherrg,
]
}
`

Hi this is a bug in the telemetry logic, thanks for reporting.


Fix build errors with -Wstrict-aliasing

Building with the -Wstrict-aliasing C-flag resulted in build errors
in src/cmsplugin.c.
Using memcpy resolves this, as it is a correct way for
type punning in C.
Part of a fix for issue #303

You may want to consider putting the a reference to the downstream Gentoo bug, i.e. https://bugs.gentoo.org/855020, in the commit message.

Many tanks. I sincerely appreciate your collaboration. Unfortunately I will not merge your PR for following reasons:

line 185 memcpy(&n, &tmp, sizeof tmp); is wrong, n already is a pointer.
static_assert() is not part of C99.
as its names hints, cmsFloat32Number and cmsUInt32Number have both 32 bits, if this is not the case the testbed detects it (see checkbasetypes function in testcms2.c) So the whole assert is not needed at all, because if sizes are not same whole library fails earlier.
memcpy may not be implemented as intrinsic on some compilers, like those for PICs, therefore adding a stack frame and breaking atomicity may change behavior on threaded environments. Testing that is not trivial.
-And more importantly, there is nothing wrong on original lines, the punned pointer is temporary and should be discarded by gcc.  I suspect this is a compiler bug, and as a proof of that I have fixed the warning message by  introducing a temporary pointer, that is, adding a true aliasing. This oddly seems to make gcc happy. Visual studio was not issuing any warning at all.

In general I'm pretty reluctant to add code to make compilers happy, specially when the offending code seems OK, but in this case was easy and hopefully harmless. See the changes on:
https://github.com/mm2/Little-CMS/commit/c3d7f491e2daebda2413fb3d2935c51df1c50ac7#diff-b6710fb02050a438b53b59a1a4a0e52b9a887b3b20b4188dc4f274df7cb73750

@mm2 whether the punned pointer is temporary or not is immaterial. You cannot dereference a pointer to a type not compatible with the original object, temporary or not.
As a compromise solution, I would suggest going with a write-read through a union, with is generally easier to optimize, even for embedded and PIC compilers (and implementation-defined behaviour in C). Adding more type punning to try and trick GCC into accepting this code will just cause issues down the road.

Superseded by #324

Superseded by https://github.com/mm2/Little-CMS/pull/324


removing oauth parameters from request sent to App Service Auth

This caused some providers to not login properly from Swagger (MS, Google didn't work but others did). Issue was that we were sending an empty scope which App Service Auth passed along rather than using the server-side-specified scopes. Some providers could handle empty scopes and others couldn't. We should just leave all that off and let the server handle it.

Looks good.


CI/CD: add rune kill before test completes

You can refer to this commit to add rune kill before test completes


Update flyway-core to 7.11.0

Updates org.flywaydb:flyway-core from 7.9.2 to 7.11.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.flywaydb", artifactId = "flyway-core" } ]

labels: library-update, semver-minor

Superseded by #297.


Access blocked: This app’s request is invalid

I am getting the following error when I click on the URL for authorization. OAuth 2.0 Client Application type Web Application
{"web":{"client_id":"{}","project_id":"{}","auth_uri":"https://accounts.google.com/o/oauth2/auth","token_uri":"https://oauth2.googleapis.com/token","auth_provider_x509_cert_url":"https://www.googleapis.com/oauth2/v1/certs","client_secret":"{}","redirect_uris":["http://localhost/authorize/"]}}
Access blocked: This app’s request is invalid
You can’t sign in because this app sent an invalid request. You can try again later, or contact the developer about this issue. Learn more about this error
If you are a developer of this app, see error details.
Error 400: redirect_uri_mismatch
Error 400: redirect_uri_mismatch
The redirect URI in the request, urn:ietf:wg:oauth:2.0:oob, can only be used by a Client ID for native application. It is not allowed for the WEB client type. You can create a Client ID for native application at https://console.developers.google.com/apis/credentials/oauthclient
Request details: flowName=GeneralOAuthFlow
Related developer documentation

And get the following error when I click on the URL for authorization. OAuth 2.0 Client Application type Desktop App
{"installed":{"client_id":"{}","project_id":"{}","auth_uri":"https://accounts.google.com/o/oauth2/auth","token_uri":"https://oauth2.googleapis.com/token","auth_provider_x509_cert_url":"https://www.googleapis.com/oauth2/v1/certs","client_secret":"{}","redirect_uris":["http://localhost/authorize/"]}}
Error 400: invalid_request
The out-of-band (OOB) flow has been blocked in order to keep users secure. Follow the Out-of-Band (OOB) flow migration guide linked in the developer docs below to migrate your app to an alternative method.
Request details: redirect_uri=urn:ietf:wg:oauth:2.0:oob flowName=GeneralOAuthFlow

There's no "Other" type in the available options for Oauth client id credential.


Images size - beta version

What happened?
With beta version images doesn't follow the same rule defined by Obsidian to scale image according to its aspect ratio.
In general, if we want to scale the image retaining the ratio we omit the height:
![[image.jpg|200]]

However, dataview seems to not follow this rule. For example:
image1:: ![[Freud.jpg]]

image2:: ![[Nietzsche.jpg|200]]

image3:: ![[Marx.jpg|200]]

image4:: ![[Weimar.jpg|100]]

Output in dataview table:

Removing image4:

I didn't find any "rule" in the behavior of images with defined size.
DQL
TABLE image1, image2, image3, image4
WHERE file.path = this.file.path

JS
No response
Dataview Version
0.5.18
Obsidian Version
0.14.6
OS
MacOS

I wonder what the root cause of this issue is.

Maybe Freud has the answer! :)

I treat [[image|100]] as "set both width and height to 100" instead of "set width to 100 and then scale height". I'll fix this for the next beta release.

Fixed in upcoming release.

Thank you.


Mockpopen multiple processes

This will fix #90 but still to do:

fix mock.call: https://bugs.python.org/issue35226 - which will mean a fix in testfixtures in the meantime.
fix PRs to testfixtures so that coverage checks work as required.
update MockPopen docs to recommend using all_calls or a process' calls when checking what was called.

@asqui @foobacca @nebulans - I'd appreciate your thoughts on this, I think this is 100% backwards compatible, but as you guys are the big users of it, I'd like to know what you think :-)

Coverage remained the same at 100.0% when pulling ee25a3e1e8c8eb6fdc1be2eaec8b6b731ce2440e on cjw296:mockpopen_multiple_processes into 16d02d7e9e29bd8f5b9620b1332f750bfa7fa637 on Simplistix:master.


Beetle coverage changes to match climate protection meaning of data

This PR makes the changes required to match the beetle coverage data's meaning of climate protection from spruce beetles. This includes returning new fields in CSVs and the definitions being high climate protection, minimal climate protection, and no climate protection.
This PR is required for the changes to the NCR application for the beetle coverage portion of the report.

@cstephen Thanks for catching those! It's hard to ensure you've caught all of the places where this was a thing due to how the wording changed for describing just about everything :) Please review again when you have the opportunity.


Add setting to disable instances of "Run Python File In Terminal"

I'd like to reopen #6921 as I believe there is still a need to remove the "Run Python File In Terminal" option as an icon in the toolbar. To add on to that previous request, if possible I'd also like to disable it from the right click menu in the file editor as well as the menu shown when right clicking a python file in the explorer pane (and any other obvious locations I might not be thinking of, though those stated are the only ones I'm having issues with).
In my case, my team uses VSCode for development of our PyTest repository. Running tests is required to be done via command line, the inline "Run Test" option that appears when a test is discovered, or the test discovery pane. Executing one of our test files without doing so via one of those methods results in an exception, and therefore these "Run Python File In Terminal" execution options are completely unnecessary and confusing to new members of our team.
An option in .vscode/settings.json to disable/hide these options would be much appreciated.

Thank you for the suggestion! We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.

This is slightly tangental, but "Run Python File In Terminal" is confusing for my son trying to learn programming because it opens a bash terminal and then runs some mysterious commands etc, rather than just runs the python. It also doesn't clear the previous run when you run it again.
So for some code to print a smiley face, after running it twice, currently I see:
/usr/local/bin/python3 /Users/rjmunro/personal_projects/python/face.py
rjmunro:python $ /usr/local/bin/python3 /Users/rjmunro/personal_projects/python/face.py
~     ~
o     o
   "
\_____/

rjmunro:python $ /usr/local/bin/python3 /Users/rjmunro/personal_projects/python/face.py
~     ~
o     o
   "
\_____/

rjmunro:python $

I want to see:
~     ~
o     o
   "
\_____/

and nothing else. It's relevant to this ticket because if the feature to just run the script (in a terminal, but without a bash session) was added, it would have to be configurable to turn off the old behaviour so he didn't get it by mistake.

@rjmunro that is a separate feature request regarding "Run Python File In Terminal" so please open a separate issue.

As an instructor that uses python in introductory college courses I would also really like this feature. It would allow me to control how quickly students gain exposure to the higher level features of VS Code by forcing them to run via the command line earlier on.

We've consolidated multiple play buttons into one, and test explorer is also better now which has its own play button. Closing this issue as outdated. Feel free to open this as a new feature request rn if need be and we might consider doing it based on upvotes.


Tenant Tokens (Multi-Tenant indexes)

This issue is tightly linked to this WIP spec: https://github.com/meilisearch/specifications/pull/89

The tasks and steps are currently WIP and will be updated as soon as the spec will be definitive and the work will start.

Sorry, I forgot to ping both teams: @meilisearch/integration-team and @meilisearch/docs-team


build: make qr-creator available only in the browser

Motivation
The library leads to issues (es modules import error, segmentation fault, blocking tests etc.) in jest tests of NNS-dapp when use explicitly or imported implicitly.
Therefore, the simplest way to avoid these problems is to skip it globally in jest tests.
It remains tested in e2e tests.
P.S.: Mocking it would probably be possible but that way no one using the library as to care about this issue.
This PR solves both npm run test and npm run build of NNS-dapp.
Changes

lazy load the qr-creator library for the browser only

This will happen with any library we try to use, right?

Most probably not. It's particular.

Thanks for the review!


Including a build without jar task to composite build

It is not listed in the documentation as not-supported or configuration needed use-case, so I guess and hope it is a bug.
If you want to look at the included project, look at Vampire/Javacord on GitHub in the v_3 branch.
It is a main project with two subprojects.
The subprojects produce a JAR artifact each.
The main project depends on both subprojects, one as api, the other as implementation so that it is on the correct classpaths for the consumer.
The main projects sole purpose is to be able to declare one dependency and have both artifacts and have them on the correct classpaths.
Because of that there is no jar task in the main project.
Now I have a consuming project where I define includeBuild('../Javacord/') in the settings.gradle and implementation 'org.javacord:javacord:3.0.0-SNAPSHOT' as dependency.
If I now try to do ./gradlew run or any other task that needs to resolve the artifacts, the build errors out with Task 'jar' not found in project ':javacord'.
The message is correct but also how the build is designed.
There is no jar artifact and also task, only dependency metadata and that is how it is supposed to be.
But that makes it hard to include it as composite build part.
A work-around is to define the binary dependency with wrong coordinates and then map the coordinates to the two subprojects manually, this way the main dependency is resolved and used from the maven repository.
Another work-around is to have a disabled jar task instead of none.
org.gradle.execution.TaskSelectionException: Task 'jar' not found in project ':javacord'.
        at org.gradle.execution.TaskSelector.getSelection(TaskSelector.java:116)
        at org.gradle.execution.TaskSelector.getSelection(TaskSelector.java:81)
        at org.gradle.execution.commandline.CommandLineTaskParser.parseTasks(CommandLineTaskParser.java:42)
        at org.gradle.execution.TaskNameResolvingBuildConfigurationAction.configure(TaskNameResolvingBuildConfigurationAction.java:44)
        at org.gradle.execution.DefaultBuildConfigurationActionExecuter.configure(DefaultBuildConfigurationActionExecuter.java:48)
        at org.gradle.execution.DefaultBuildConfigurationActionExecuter.access$000(DefaultBuildConfigurationActionExecuter.java:25)
        at org.gradle.execution.DefaultBuildConfigurationActionExecuter$1.proceed(DefaultBuildConfigurationActionExecuter.java:54)
        at org.gradle.execution.DefaultTasksBuildExecutionAction.configure(DefaultTasksBuildExecutionAction.java:44)
        at org.gradle.execution.DefaultBuildConfigurationActionExecuter.configure(DefaultBuildConfigurationActionExecuter.java:48)
        at org.gradle.execution.DefaultBuildConfigurationActionExecuter.access$000(DefaultBuildConfigurationActionExecuter.java:25)
        at org.gradle.execution.DefaultBuildConfigurationActionExecuter$1.proceed(DefaultBuildConfigurationActionExecuter.java:54)
        at org.gradle.execution.ExcludedTaskFilteringBuildConfigurationAction.configure(ExcludedTaskFilteringBuildConfigurationAction.java:47)
        at org.gradle.execution.DefaultBuildConfigurationActionExecuter.configure(DefaultBuildConfigurationActionExecuter.java:48)
        at org.gradle.execution.DefaultBuildConfigurationActionExecuter.select(DefaultBuildConfigurationActionExecuter.java:36)
        at org.gradle.initialization.DefaultGradleLauncher$CalculateTaskGraph.run(DefaultGradleLauncher.java:287)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:317)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:309)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:185)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:97)
        at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
        at org.gradle.initialization.DefaultGradleLauncher.constructTaskGraph(DefaultGradleLauncher.java:183)
        at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:136)
        at org.gradle.initialization.DefaultGradleLauncher.scheduleTasks(DefaultGradleLauncher.java:204)
        at org.gradle.composite.internal.DefaultIncludedBuild.addTasks(DefaultIncludedBuild.java:188)
        at org.gradle.composite.internal.DefaultIncludedBuildController.populateTaskGraph(DefaultIncludedBuildController.java:80)
        at org.gradle.composite.internal.DefaultIncludedBuildControllers.populateTaskGraphs(DefaultIncludedBuildControllers.java:75)
        at org.gradle.initialization.DefaultGradleLauncher$CalculateTaskGraph.run(DefaultGradleLauncher.java:298)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:317)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:309)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:185)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:97)
        at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
        at org.gradle.initialization.DefaultGradleLauncher.constructTaskGraph(DefaultGradleLauncher.java:183)
        at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:136)
        at org.gradle.initialization.DefaultGradleLauncher.executeTasks(DefaultGradleLauncher.java:115)
        at org.gradle.internal.invocation.GradleBuildController$1.call(GradleBuildController.java:77)
        at org.gradle.internal.invocation.GradleBuildController$1.call(GradleBuildController.java:74)
        at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:152)
        at org.gradle.internal.work.StopShieldingWorkerLeaseService.withLocks(StopShieldingWorkerLeaseService.java:38)
        at org.gradle.internal.invocation.GradleBuildController.doBuild(GradleBuildController.java:96)
        at org.gradle.internal.invocation.GradleBuildController.run(GradleBuildController.java:74)
        at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)
        at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
        at org.gradle.tooling.internal.provider.ValidatingBuildActionRunner.run(ValidatingBuildActionRunner.java:32)
        at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner$3.run(RunAsBuildOperationBuildActionRunner.java:47)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:317)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:309)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:185)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:97)
        at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
        at org.gradle.launcher.exec.RunAsBuildOperationBuildActionRunner.run(RunAsBuildOperationBuildActionRunner.java:43)
        at org.gradle.tooling.internal.provider.SubscribableBuildActionRunner.run(SubscribableBuildActionRunner.java:51)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter$1.transform(InProcessBuildActionExecuter.java:50)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter$1.transform(InProcessBuildActionExecuter.java:46)
        at org.gradle.composite.internal.DefaultRootBuildState.run(DefaultRootBuildState.java:65)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:46)
        at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:32)
        at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:39)
        at org.gradle.launcher.exec.BuildTreeScopeBuildActionExecuter.execute(BuildTreeScopeBuildActionExecuter.java:25)
        at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:80)
        at org.gradle.tooling.internal.provider.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:53)
        at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:62)
        at org.gradle.tooling.internal.provider.ServicesSetupBuildActionExecuter.execute(ServicesSetupBuildActionExecuter.java:34)
        at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:36)
        at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:25)
        at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:43)
        at org.gradle.tooling.internal.provider.ParallelismConfigurationBuildActionExecuter.execute(ParallelismConfigurationBuildActionExecuter.java:29)
        at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:59)
        at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:31)
        at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:59)
        at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:44)
        at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:46)
        at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:30)
        at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:67)
        at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
        at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:37)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
        at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:26)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
        at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:34)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
        at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:74)
        at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:72)
        at org.gradle.util.Swapper.swap(Swapper.java:38)
        at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:72)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
        at org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:55)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
        at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:62)
        at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
        at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:82)
        at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
        at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
        at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:50)
        at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:295)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
        at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)

You removed the jar task from the task container, but didn't remove the jar artifact from the runtimeElements configuration, so Gradle will still go looking for it. I consider tasks.remove and antipattern. It's so easy to get wrong and still have the task referenced somewhere and there really is no harm in having the task. It'll just have no inputs and so it won't run.

Ah, thanks, makes sense.
Could you tell me how to remove it there even if you consider it an anti-pattern? :-)
Sure, the task does no harm if it has no input or even got disabled.
But I prefer not to have unnecessary tasks in UIs or command output that show the taks.
This only brings confusion to the build user as to why there is a jar task when there is no JAR built.
Sure, there are other tasks like compileTestJava that are also shown though they don't do anything and I didn't bother removing them.
But the important difference is, that most of those are not shown when the tasks are filtered (gradlew tasks) but only if --all is used.
I also e. g. don't want the totally useless knows task of the shadow plugin shown in my build, so I also removed it. But as it is just an "easteregg" task, this should do no harm.
Maybe the jar task is too integrated and I better just disable or ignore it.
Is there at least a way to hide it in the default gradlew tasks output?
Just setting the group to null?

Just setting the group to null?

That's the way to go if you just want to "hide".

Thanks, I'll consider just hiding it then, or maybe I'm just not that picky and just let idle there. :-D


Keris Partisan

Keris Partisan (no gem) does not trigger melee gear highlight.
Is it just me?

It's such a niche issue that I don't feel it's worth debugging, feel free to open a PR.

Happens to me too. Annoying if you're killing something like KQ for some reason


Only display packet links if a packet is available, fixes #756

Overview
This PR updates the conditional determining whether to display a packet link or fall back to a link to the board report to use the is_ready method of a packet. Using url will always show the packet link, because url is set on save(). By contrast, is_ready() will only show the packet if it actually exists.
Checklist

[x] PR has a descriptive enough title to be useful in changelogs

Testing Instructions
@hancush will do this after getting PR approval.

Deploy to staging
View a recent event with an agenda, e.g., https://lametro-upgrade.datamade.us/event/planning-and-programming-committee-44279664d25e/, and confirm the "View" link in the related board reports listing downloads the board report

Handles #756

Whoops, @fatima3558, good catch – Download is the link that should download the report! View should go to the board report detail page. My bad.


[BUG] Crash on start-up with latest version

Version of Advanced Rocketry
AdvancedRocketry 1.12.2-1.6.0-163-UNSTABLE build -163 for 1.12.2
Have you verified this is an issue in the latest unstable build
Yes
Version of LibVulpes
LibVulpes 1.12.2-0.4.1-1-UNSTABLE build -1 for 1.12.2
Version of Minecraft
1.12.2
Does this occur without other mods installed
Did not test yet
Crash report or log or visualVM (if applicable)
https://paste.dimdev.org/yixapahiwa.mccrash
Description of the problem
Crash on startup with latest version. Works fine with previous version.

No longer crashes with1.12.2-1.6.0-164


https_proxy doesn't work for skywalking-oap-server:8.5.0-es7

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question
i set https_proxy  in docker-compose for skywalking-oap-server,but it can't send message using dingtalk
by the way, i am running skywalking-oap-server in a net which   can't rich internet,so i have to use proxy to rich outside,but sadly it didn't work for me.

This is not the community's responsibility.


Moved toastService into copy directive

Previously what happened was ng-click -> called copyToClipBoard which always showed a successful toast message.
Passed in the toastService into the copy directive, so now what happens is the toast service will show the correct response.
Partially inspired by a reddit post where the user stated that it would say copied to clipboard but then would not be able to past it.

@ckhatri Do you know how to replicate the error toast? I can confirm success is working which is great. If not I will still merge, I just thought I'd test if you did know how to replicate.

I'm not sure how to force the copy command to fail, but I just changed the code so it would throw, which it then caught and showed the 'fail to copy' toast.

As we have no true way to test a failure for copy & paste, I will go ahead and merge. Copy was still working for me
+5! 👍


Skia crash in GrContext::setResourceCacheLimits on Genymotion (android_x86)

Stack from https://github.com/flutter/flutter/issues/490#issuecomment-226021171
Symbolicated by me in https://github.com/flutter/flutter/issues/490#issuecomment-226814876
/src/engine/src/out/android_debug_x86/../../third_party/skia/src/gpu/GrContext.cpp:766
/src/engine/src/out/android_debug_x86/../../sky/shell/gpu/direct/ganesh_canvas.cc:37 (discriminator 1)
/src/engine/src/out/android_debug_x86/../../sky/shell/gpu/direct/rasterizer_direct.cc:161 (discriminator 1)
/src/engine/src/out/android_debug_x86/../../sky/shell/gpu/direct/rasterizer_direct.cc:64
/src/engine/src/out/android_debug_x86/../../base/bind_internal.h:176 (discriminator 5)
/src/engine/src/out/android_debug_x86/../../base/callback.h:396 (discriminator 1)

Crashing line is:
void GrContext::setResourceCacheLimits(int maxTextures, size_t maxTextureBytes) {
    ASSERT_SINGLE_OWNER
    fResourceCache->setLimits(maxTextures, maxTextureBytes); // line 766
}

The above code is from google/skia@8cc209111876b7c78b5ec577c9221d8ed5e21024
I don't know what the crash point is.
@spierce7 could you upload a tombstone file or post a gist of the full crash stack?  Would be nice to know what the crash point is (i.e. is this that fResourceCache is null).
This crash was reported with flutter/flutter@6d2d495369 and flutter/engine@a943c732d5
https://github.com/flutter/flutter/issues/490#issuecomment-226031078

@abarth or @chinmaygarde, suggestions for next steps here?

This happens very early in GL startup.  Maybe we're failing to bring up the GL driver?

@eseidel I'm not sure what a tombstone file is. Also I believe I pasted the entire log that was displayed for the crash. If you give me some instructions, I'd be happy to help.

@ScottPierce when android apps crash, they typically write out crash logs called "tombstones":
https://source.android.com/devices/tech/debug/
In this case it may say in the log where it wrote it, or likely in /data/tombstones, and a adb pull /data/tombstones/tombstone_01 might work to pull it?  It's just a slightly more complete version of the above log since adb can trim long logs.

@eseidelGoogle I've been trying to get you what you want, but I've been having issues building apps with flutter recently. I've reported https://github.com/flutter/flutter/issues/4681, but I'm still getting ADB errors. At first I thought ADB was just getting itself into weird states as it sometimes does, but after numerous restarts I've been unable to fix the issue.
I'm getting another build error that seems to only be happening with genymotion. I downloaded some updates for Android a few days ago. I'm assuming that must be somewhat related.
Below is the build error I'm getting. Flutter is having difficulty talking to ADB. This only happens with genymotion emulator, as flutter can build for my nexus 5x. Android studio has no issue pushing non-flutter builds to my genymotion emulator. How would you like to proceed?
command
flutter run
exception
Exit code 1 from: /Users/spierce7/Android/sdk/platform-tools/adb -s adb shell pm list packages com.yourcompany.myapp3
package:flutter_tools/src/base/process.dart 144                   _runWithLoggingSync
package:flutter_tools/src/base/process.dart 81                    runCheckedSync
package:flutter_tools/src/android/android_device.dart 204         AndroidDevice.isAppInstalled
package:flutter_tools/src/commands/install.dart 37                installApp
package:flutter_tools/src/commands/run.dart 210                   startApp.<async>
===== asynchronous gap ===========================
dart:async                                                        _Completer.completeError
package:flutter_tools/src/commands/run.dart 252                   startApp.<async>
===== asynchronous gap ===========================
dart:async                                                        _asyncThenWrapperHelper
package:flutter_tools/src/commands/run.dart                       startApp
package:flutter_tools/src/commands/run.dart 129                   RunCommand.runInProject.<async>
===== asynchronous gap ===========================
dart:async                                                        Future.Future.microtask
package:flutter_tools/src/commands/run.dart                       RunCommand.runInProject
package:flutter_tools/src/runner/flutter_command.dart 172         FlutterCommand._run.<async>
dart:async                                                        _SyncCompleter.complete
package:flutter_tools/src/cache.dart 121                          Cache.updateAll.<async>
===== asynchronous gap ===========================
dart:async                                                        _asyncThenWrapperHelper
package:flutter_tools/src/runner/flutter_command.dart             FlutterCommand._run
package:flutter_tools/src/runner/flutter_command.dart 103         FlutterCommand.run
package:args/command_runner.dart 176                              CommandRunner.runCommand.<fn>
dart:async                                                        Future.Future.sync
package:args/command_runner.dart 129                              CommandRunner.runCommand
package:flutter_tools/src/runner/flutter_command_runner.dart 180  FlutterCommandRunner.runCommand
package:args/command_runner.dart 103                              CommandRunner.run.<fn>
dart:async                                                        Future.Future.sync
package:args/command_runner.dart 103                              CommandRunner.run
package:flutter_tools/src/runner/flutter_command_runner.dart 123  FlutterCommandRunner.run
package:flutter_tools/executable.dart 88                          main.<async>.<fn>.<async>
===== asynchronous gap ===========================
package:stack_trace                                               Chain.capture
package:flutter_tools/executable.dart 82                          main.<async>

flutter doctor
[✓] Flutter (on Mac OS, channel alpha)
    • Flutter at /Users/spierce7/frameworks/flutter
    • Framework revision 6d2d495369 (2 weeks ago), engine revision a943c732d5

[✓] Android toolchain - develop for Android devices (Android SDK 23.0.3)
    • Android SDK at /Users/spierce7/Android/sdk
    • Platform android-N, build-tools 23.0.3
    • Java(TM) SE Runtime Environment (build 1.7.0_80-b15)

[✓] iOS toolchain - develop for iOS devices (Xcode 7.3.1)
    • XCode at /Applications/Xcode.app/Contents/Developer
    • Xcode 7.3.1, Build version 7D1014

[✓] Atom - a lightweight development environment for Flutter
    • flutter plugin version 0.2.2
    • dartlang plugin version 0.6.22

Thanks for the report @ScottPierce!  What API version is your emulator running?  It's likely included in the name of the emulator shown in adb devices or flutter devices.

@eseidelGoogle This error was reproduced with 2 Genymotion emulators:

Google Nexus 5 - 5.1.0 - API 22
Google Nexus 5X - 6.0.0 - API 23

Also, here is the result of me running flutter devices. It appears to be having an error:
spierce7$ flutter devices
1 connected device:

Error retrieving device properties for ro.product.cpu.abi.
adb • adb • android-arm

@ScottPierce, can you run adb shell getprop ro.product.cpu.abi?
Also /Users/spierce7/Android/sdk/platform-tools/adb -s adb shell pm list packages com.yourcompany.myapp3 - perhaps the format changed a bit from what we're expecting.
It'd be great to have the stdout/stderr as well as the exit code (echo $?). Thanks!

I was able to resolve the adb issue. Genymotion defaults to using it's own ADB instance, and with the update to adb that I recently downloaded, they were out of sync. I was seeing adb server version (32) doesn't match this client (36); killing... in the logs all over the place, even while running normal adb commands like adb devices.
I was able to resolve this by telling Genymotion to use my adb that I downloaded from google, instead of it's own version:

I'm back to getting the error this thread was originally about. I'll try to comply with the original request again.

@eseidelGoogle The tombstone you requested:
tombstone_00.txt

Thank you very much!  @ScottPierce to confirm before we forget: what's the flutter version which generated that tombstone? :)  I'll get symbols for you shortly!

This crash is over a year old, we've rolled skia many times since then.  I suspect this bug is no longer useful.  I just tested in genymotion on my MacBook Pro just now and no crashes (there were other bugs):
Google Nexus 6, 7 0 0, API 24, 1440x2560 • <IP_ADDRESS>:5555 • android-x86 • Android 7.0 (API 24)


hitTolerance option not works in WebGLPointsLayerRenderer.forEachFeatureAtCoordinate

hitTolerance not used in WebGLPointsLayerRenderer.forEachFeatureAtCoordinate method code,
because of this, the select component does not work correctly for WebGLPointsLayer

@jahow, could you take a look at this please?

Support for hitTolerance was never implemented with this renderer unfortunately. I'm going to mark this as "PR accepted", if anyone has the resources/time for it.

Solution:
 forEachFeatureAtCoordinate(
        coordinate,
        frameState,
        hitTolerance,
        callback,
        matches) {
        assert(this.hitDetectionEnabled_, 66);
        if (!this.hitRenderInstructions_) {
            return undefined;
        }

        const pixel = applyTransform(
            frameState.coordinateToPixelTransform,
            coordinate.slice()
        );
        if (hitTolerance && hitTolerance > 0) {
            this.calculatePixelsInArea(pixel, hitTolerance).forEach(pixel => {
                this.forEachFeatureAtPixel(pixel, frameState, callback);
            });
        } else {
            this.forEachFeatureAtPixel(pixel, frameState, callback);
        }
        return undefined;
    }

    calculatePixelsInArea(pixel, hitTolerance = 5) {
        const result = [];
        const maxDistanceSq = hitTolerance * hitTolerance;
        for (let r = 0; r < hitTolerance; r++) {

            for (let x = -r; x <= r; x++) {
                const x2 = x * x;
                for (let y = -r; y <= r; y++) {
                    const y2 = y * y;
                    const distanceSq = x2 + y2;
                    if (maxDistanceSq >= distanceSq) {
                        const npx = [Math.floor(pixel[0]) + x, Math.floor(pixel[1] + y)];
                        result.push(npx);
                    }
                }
            }
        }
        return result;
    }

    forEachFeatureAtPixel(
        pixel,
        frameState,
        callback
    ) {
        const data = this.hitRenderTarget_.readPixel(pixel[0] / 2, pixel[1] / 2);
        const color = [data[0] / 255, data[1] / 255, data[2] / 255, data[3] / 255];
        const index = colorDecodeId(color);
        const opacity = this.hitRenderInstructions_[index];
        const uid = Math.floor(opacity).toString();

        const source = this.getLayer().getSource();
        const feature = source.getFeatureByUid(uid);
        if (feature) {
            return callback(feature, this.getLayer(), null);
        }
        return undefined;
    }


Unhandled exception when filtering Enum column

Using version 1.12.0  (downgrading to version 1.11.1 fixed this issue)
When I filter a column with an Enum value (Caf.Midden.Utils.Models.Zones) I get the following error:
Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: The binary operator NotEqual is not defined for the types 'Caf.Midden.Utils.Models.Zones' and 'System.Object'.
System.InvalidOperationException: The binary operator NotEqual is not defined for the types 'Caf.Midden.Utils.Models.Zones' and 'System.Object'.
  at (wrapper managed-to-native) System.Reflection.RuntimeMethodInfo.InternalInvoke(System.Reflection.RuntimeMethodInfo,object,object[],System.Exception&)
  at System.Reflection.RuntimeMethodInfo.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) <0x262b9e8 + 0x000ce> in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---

Relevant Razor code:
 <Column TableItem="Dataset" Title="Zone" Field="@(d => d.Zone)" Sortable="true" Filterable="true" Width="5%" />

Great component, btw. Thanks!

Hey,
Can you please create a page that fully reproduces this issue?
See Example

Thanks for the repro, this issue is fixed in 1.12.1