python: wire() and cell() methods of Module segfault when wire/cell doesn't exist

Module::wire() and Module::cell() look up a wire or cell by IdString, and return nullptr if not found. The associated python wrappers don't account for the nullptr case and immediately dereference the returned pointer, resulting in a segfault.
Steps to reproduce the issue
cd yosys/examples/python-api
python3 -i script.py
module.wire(ys.IdString('\\not_a_wire'))

Expected behavior
Not a segfault. Aside from that, I'm not really sure. From a python perspective the ideal behavior would be to return None, but I don't see a way to shoehorn that in with boost::python. Maybe the wrapper classes need to be updated to tolerate a null ref_obj, with a function exposed to python to query whether it is null.
If the methods are removed from the python interface, then we need some other way to cheaply check for the existence of a wire. Module.wires_ is accessible through python, but requires copying the entire dictionary.
Actual behavior
Segmentation fault (core dumped)

If this helps, this is how I approached a similar problem with the nextpnr Python bindings:
https://github.com/YosysHQ/nextpnr/blob/master/common/pywrappers.h#L132-L137
https://github.com/YosysHQ/nextpnr/blob/master/common/pywrappers.h#L158-L167
The idea is to check for a nullptr before de-referencing, and throw an exception if null. This is then caught by the final layer of wrapping which returns an empty boost::python::object (this becomes a Python None) instead of the derefenced entity.

cc @btut

Sorry for the long delay. This should fix your issue.
Thanks for the suggestion @daveshah1. Unfortunately, the conversion to the actual boost::python::object is done by the library itself. I just convert to the wrapped yosys classes. Therefore, I cannot return a None object.
Nevertheless I now introduced that same check and a runtime exception will be thrown, however this exception is not caught in my code (as you did for nextpnr) but will be converted to a python exception and forwarded for the user to handle.


Update rb-sys to 0.9.102 for ruby 3.4 compatibility

Otherwise it fails with:
LoadError: /tmp/bundle/ruby/3.4.0+0/gems/tiktoken_ruby-0.0.8/lib/tiktoken_ruby/tiktoken_ruby.so:
undefined symbol: ruby_abi_version - ruby_abi_version (LoadError)

However compilation is now failing with:
error[E0609]: no field `len` on type `RString__bindgen_ty_1__bindgen_ty_1`
   --> /Users/byroot/.cargo/registry/src/index.crates.io-6f17d22bba15001f/magnus-0.4.4/src/r_string.rs:366:57
    |
366 |             slice::from_raw_parts(h.ptr as *const u8, h.len as usize)
    |                                                         ^^^ unknown field
    |
    = note: available fields are: `ptr`, `aux`

error[E0609]: no field `len` on type `RString__bindgen_ty_1__bindgen_ty_1`
   --> /Users/byroot/.cargo/registry/src/index.crates.io-6f17d22bba15001f/magnus-0.4.4/src/r_string.rs:954:19
    |
954 |                 h.len as usize
    |                   ^^^ unknown field
    |
    = note: available fields are: `ptr`, `aux`

error[E0609]: no field `len` on type `RString__bindgen_ty_1__bindgen_ty_2`
   --> /Users/byroot/.cargo/registry/src/index.crates.io-6f17d22bba15001f/magnus-0.4.4/src/r_string.rs:996:44
    |
996 |     value.as_internal().as_ref().as_.embed.len
    |                                            ^^^ unknown field
    |
    = note: available field is: `ary`

For more information about this error, try `rustc --explain E0609`.

Which I don't know how to fix. @ianks could you lend me a hand here?

Nevermind, the compilation failure was because I forgot to rebase my fork 🤦

Hum, seems like there's no version of rb-sys compatible with both 3.4 and 2.7?

Hum, seems like there's no version of rb-sys compatible with both 3.4 and 2.7?

rb-sys is (painfully) compatible down to 2.6
I think this error is a bundler issue?
  	There are no versions of bundler (= 2.5.18) compatible with your Ruby & RubyGems
  	bundler requires Ruby version >= 3.0.0. The current ruby version is <IP_ADDRESS>.

Anyway, @IAPark we should probably drop 2.7 support since it's EOL and rb-sys will

@IAPark just saw you are looking for maintainership help. Happy to lend a hand here if you send inv ❤

Thanks y'all.


snet: fix panic in Listen

Add more checks to avoid the panix and also provide a default value if
the address has no L4 information.
In such case, the default value would be UDP port 0, meaning that the
application wants a random port.
Fixes #1803

This change is

go/lib/snet/snet.go, line 206 at r1 (raw file):
Previously, kormat (Stephen Shirley) wrote…
I'd prefer to have a switch statement here based on the network param, so we avoid further hard-coding of the "udp4" assumption.

So basically, do the switch now, with default unsupported and add later case statements when we support other L4 protocols versus leave it as is then implement the switch when we support other L4 protocols.
Either way changes would be required, why not leave it like this?


Is it possible that Jiocinema can be supported

https://www.jiocinema.com/ -  i am not able to download videos from jiocinema , though i couldnt find the reason behind this , i suspect they may be suing DRM protection , can anyone comment on the same and if possible , add the support for Jiocinema too

Hi,
My started topic is closed, can you suggest what modifications should i
make to the post that
it meet the guidelines?
Regards,
Amit
On Sun, Sep 15, 2019 at 1:48 PM Sergey M<EMAIL_ADDRESS>wrote:

Closed #22406 https://github.com/ytdl-org/youtube-dl/issues/22406.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ytdl-org/youtube-dl/issues/22406?email_source=notifications&email_token=ANGCCDIDMBMJXZEPPMU4I73QJXVWRA5CNFSM4IWZU6J2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOTUD3YIY#event-2634529827,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANGCCDIGAZJRUYNF7UTAIEDQJXVWRANCNFSM4IWZU6JQ
.


Hiding objects from schema generation.

I may have missed this, but is there a way to hide objects from appearing in the schema?
I tried revoking privelages on individual tables, but I imagine the schema generation is taking place through reading postgress schemas.
Any hints?

@angelosarto There's no blacklist functionality yet, but how I do it is moving things that I wish to be accessible into a specific schema for postgraphql.

This is actually a great answer and will do exactly what I need.
Plus, since you can specify multiple schemas to introspect it is possible to have this arrangement.

Server
Parameters

graphql_external_unauth
--schema unauth_api

graphql_external_auth
--schema unauth_api auth_api

graphql_internal
--schema unauth_api auth_api private

So each server can show different apis but be the same underneath.

@angelosarto that’s a pretty cool use case 😊


Create solution3.cpp

First this code has very less lines :)
I have used bitwise operators here to determine if the given number is power of two or not n&(n-1) this expression returns 0 if the given number is power of 2

Cool 😎


Change the default behaviour of the mode

Running the dev script launches a demo of the component with the error status. Even if the behaviour is prefectly normal and intends to demonstrate the component error management, it may make think it doesn't work properly.
We should provide a working status as default behaviour.

:tada: This issue has been resolved in version 1.4.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Timeouts error when opening noflo-browser project [git master]

Happens for instance after creating a new noflo-browser project.
Fails very fast, almost like it does not even try.

Bumped the timeout as a quick fix in eaa176bc22a311b048c9d44dd6614fdc1e093f38.
For proper fix, we need to deal with noflo/noflo-browser#90


Cold start increased significantly by enabling powertools-logging

What were you trying to accomplish?
While testing in my sample (cold start optimized) application I can measure up to 20%+ increase by enable powertools-logging instead of lambda-logging (SLF4J + Logback)
The tests are executed by leveraging lumigo-cli measure-lambda-cold-starts.
Expected Behavior
Cold starts timings shouldn't become much worse by switching out another logging framework for powertools-logging
Current Behavior
lambda-logging (baseline)
 {
      "functionName": "client-service-dev-create-client",
      "memorySize": 3008,
      "coldStarts": 40,
      "min": 1142.29,
      "p25": 1192.22,
      "median": 1213.9,
      "p75": 1223.73,
      "p95": 1261.69,
      "max": 1276.78,
      "stddev": 29.0004
}

powertools-logging
{
      "functionName": "client-service-dev-create-client",
      "memorySize": 3008,
      "coldStarts": 71,
      "min": 1787.6,
      "p25": 1952.06,
      "median": 1981.9,
      "p75": 2004.21,
      "p95": 2063.38,
      "max": 2149.03,
      "stddev": 53.575
}

Possible Solution
/
Steps to Reproduce (for bugs)

git clone https://github.com/drissamri/powertools-coldstart-issue
mvn clean package
sls deploy --region eu-central-1
npm install -g lumigo-cli
lumigo-cli measure-lambda-cold-starts -p dev -n client-service-dev-create-client -r eu-central-1 -f src/test/resources/create-client-event.json

This gives you the baseline results, now we enable powertools:

Switch to powertools git branch
mvn clean package
sls deploy --region eu-central-1
lumigo-cli measure-lambda-cold-starts -p dev -n client-service-dev-create-client -r eu-central-1 -f

Environment

Powertools version used: 0.4.0-beta
Packaging format (Layers, Maven/Gradle): maven (zip)
AWS Lambda function runtime: java11

Hey @drissamri Thanks for opening the issue. I quickly looked at different branches, and its interesting to see this behaviour.
While as far I can see difference between branches, you have not actually use any Powertools logging feature, but rather just changed to use log4j2 instead which you offcourse get as a dependency via logging module from powertools. We actually did a performance test before releasing the module and found log4j2 performing much faster compared to logback/slf4j instead. We in fact specifically tested via lambda-logging itself.
Even if you look at this article on performance benchmark for different logging library we see the same results.
Nevertheless, since you have concrete examples to show the difference, I will be diving a bit deep later this week to check what might be leading to the observation you have in the example above.

After I posted this ticket I tested a few more things and saw a mistake in the implementation too (not too logging itself), if I didn't add the @Powertools annotation I must've forgot it on that branch after my tests again.
Going to circle back on the tests results later tonight. There was still a big difference after my last run, but will update the branches so you have a correct view.

There was a bug in the lumigo-cli that made the invocation not complete succesfully, so the invocation timings weren't always correct. Thanks to @theburningmonk that's fixed now.
@pankajagrawal16 I created two branches baseline (lambda-logging) and powertoolslogging and updated the full statistics for both in the README.md.
baseline: p95 of 200 cold start iterations: 1400-1435ms
powertoolslogging: p95 of 200 cold start iterations: 1990ms
In the powertoolslogging you do get to see these messages, so not sure if they cause for an extra delay:
2020-10-06T00:18:26.585+02:00 | SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
-- | --
  | 2020-10-06T00:18:26.585+02:00 | SLF4J: Defaulting to no-operation (NOP) logger implementation
  | 2020-10-06T00:18:26.585+02:00 | SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

If I'm still doing anything wrong or if I can help in any way, let me know!

There was a bug in the lumigo-cli that made the invocation not complete succesfully, so the invocation timings weren't always correct.
Aha, This makes sense, coz I tried replicating yesterday and found the same issue that function was failing in logs. I just ended up changing lambda function contract to work with String and just measure it based on that in both implementation.

The findings for me were bit similar as well what you have posted above. I still have to dive a bit deep to see why this might be happening.
When it come to warning is concerned, I too noticed that and also fixed it by adding:
           <dependency>
                <groupId>org.apache.logging.log4j</groupId>
                <artifactId>log4j-slf4j-impl</artifactId>
                <version>${log4j.version}</version>
            </dependency>

I will look at you branches and dive a bit more into details some time this week.

After a discussion with @theburningmonk today, I realized the lumigo-cli only prints out initDuration (Initialization in X-Ray) and not Duration. This will be changed by him later on.
I don't think it matters for the statistics I posted before since the clear distinction is there in both in the Initialization alone already, but end to end should be measured to make sure one of both is not losing more time during execution.

After a discussion with @theburningmonk today, I realized the lumigo-cli only prints out initDuration (Initialization in X-Ray) and not (execution) Duration. This will be changed by him later on.
I don't think it matters for the statistics I posted before since the clear distinction is there in both in the Initialization alone already, but end to end should be measured to make sure one of both is not losing more time during execution.

Yeah I have been looing at logic of cloudwatch insights query that the cli executes and I could see just looks for Init time in lambda logs.
I do agree, regardless it gives some indication anyways.

FYI: I worked together with Yan and now the measure coldstarts CLI measures both initDuration and duration time.

Hi @drissamri and @pankajagrawal16, may I ask if there is any update on this issue? Is it still a problem in v1.5.0? The reported version seems to be in a beta version a while ago. Many thanks!

hi @qtdzz There was some optimizations done before going GA to the logging module, not specifically targeting this specific issue.

I went ahead and tried it again with the latest version of the powertools (1.7.1) . I had to add jackson-core and jackson-annotations which wasn't the case before? Was it considered to use jackson-jr instead of jackson? (as recommended by docs)
Sadly, the results are worse than before :(
baseline
    {
      "functionName": "client-service-dev-create-client",
      "memorySize": 3008,
      "coldStarts": 78,
      "min": 1482.33,
      "p25": 1579.68,
      "median": 1601.91,
      "p75": 1636.67,
      "p95": 1688.14,
      "max": 1730.54,
      "stddev": 42.1809
    }

powertools:
   {
      "functionName": "client-service-dev-create-client",
      "memorySize": 3008,
      "coldStarts": 85,
      "min": 2329.65,
      "p25": 2399.04,
      "median": 2430.01,
      "p75": 2542.72,
      "p95": 2780.87,
      "max": 3133.66,
      "stddev": 140.8058
    }

Hi @drissamri Thanks for following up on this again.
I have taken some time again today to understand what's going on between different implementations.
Starting with your question on jackson-core and annotation missing. This has not changed. Reason why this is failing in your sample project is because jackson-jr-objects is bringing inn older version of jackson core with it and that confilcts with latest version of jackson core and log4j2 which needs JacksonFeature and has been added in 2.12.x.  So that is why in order to remove this dependency conflict, you might have needed to add those explicitly.
Now for performance with slf4j and logback, we need to compare similar feature set. Which means powertools-loggging by default provides support for structured logging whereas comparison made above is not doing any structured logging.
Therefore, I enabled json logging with logback with lambda-logging and results showed increased latency with cold start as well.
{
  "note": "The values include both DURATION as well as INIT DURATION",
  "result": [
    {
      "functionName": "powertools-baseline-dev-create-client",
      "memorySize": 3008,
      "coldStarts": 78,
      "min": 1752.49,
      "p25": 1798.27,
      "median": 1835.61,
      "p75": 1871.94,
      "p95": 1950.44,
      "max": 2083.6,
      "stddev": 55.9915
    }
  ]
}

{
  "note": "The values include both DURATION and INIT DURATION",
  "result": [
    {
      "functionName": "powertools-baseline-dev-create-client",
      "memorySize": 3008,
      "coldStarts": 72,
      "min": 1722.84,
      "p25": 1798.01,
      "median": 1831.7,
      "p75": 1865.05,
      "p95": 1941.07,
      "max": 2031.49,
      "stddev": 54.8105
    }
  ]
}

Other aspect is that powertools-logging provides several best practices on top of logging and that will definitely contribute to bit more processing and init time and thus contributing a bit more latency during init. Using jackson-jr wont be helpful since log4j2 internally using jackson anyways to perform structured logging.
I performed another test on latest powertools and results:
{
  "note": "The values include both DURATION as well as INIT DURATION",
  "result": [
    {
      "functionName": "powertools-issue-dev-create-client",
      "memorySize": 3008,
      "coldStarts": 92,
      "min": 2122.98,
      "p25": 2379.61,
      "median": 2411.51,
      "p75": 2450.12,
      "p95": 2515,
      "max": 2659.88,
      "stddev": 64.3841
    }
  ]
}

{
  "note": "The values include both DURATION as well as INIT DURATION",
  "result": [
    {
      "functionName": "powertools-issue-dev-create-client",
      "memorySize": 3008,
      "coldStarts": 93,
      "min": 2199.08,
      "p25": 2376.12,
      "median": 2404.99,
      "p75": 2447.05,
      "p95": 2529.61,
      "max": 2717.16,
      "stddev": 68.1443
    }
  ]
}

That being said, I will spend some more time in this week to find the possibility of optimising jackson object mapper initialisation for structured logs

Done minor tweaks to logging utility as well https://github.com/awslabs/aws-lambda-powertools-java/pull/484. Based on comparison and also difference in number of cold starts in metrics, I feel comfortable not doing anything more.
I have had a look at default log4j2 config and it is optimal for the lambda workload already. Users always have ability to configure log4j2 the way they need like using asynchronous logging, etc.
cc @drissamri I will be interested in hearing your thoughts on observations above.

Some improvements shipped in https://github.com/awslabs/aws-lambda-powertools-java/releases/tag/v1.7.2 as well. I will wait for @drissamri thoughts before closing it.

@drissamri Let me know if you have any thoughts on above findings ? Or else i will close this issue for now.


Video component: when in fullscreen mode, the expand button should allow users to exit full screen

Noting that the functional aspect of this bug only occurs in the React package; in the Twig package, this already works.
In both packages, a new icon need to be designed and added for the fullscreen state of the button.

Once the video is in full screen, the icon should change so it's clear to the user that clicking it will exit full screen mode. @inesdgomes to provide the icon and @GGKapanadze to implement.

@inesdgomes Included a new version of the Video component, where we can see the full screen mode. Check here

Hi @beatrizmartinmartins I think we talked about: a) removing the cross icon from full-screen and b) adding a new icon that allows users to exist full screen mode. Could you please make those tweaks? Thanks

@inesdgomes changes done in this link. I changed the expanded icon for the reducing icon on the Full-Screen mode

@beatrizmartinmartins I left a few minor comments to resolve in the designs. Thanks

Made the changes of the comments. See here @inesdgomes

Thanks, @beatrizmartinmartins. @justintemps Beatriz added a new icon to the bottom right so users can exit full screen mode. Ready for development.


Fix #239

Fixes #239

I've encountered this too, and changes to .Encode seem to have been made by mistake. I second this PR to undo this backward incompatible change without a major version change.


Update azure_openai.py to use langchain_openai.embeddings

🐛 Describe the bug
Description:
The azure_openai.py file in the embedchain package is using a deprecated class AzureOpenAIEmbeddings from langchain_community.embeddings. This class was deprecated in LangChain 0.0.9 and will be removed in 0.3.0.
The error message indicates that an updated version of the class exists in the langchain-openai package and should be used instead.
Error Message:
/home/codespace/.python/current/lib/python3.10/site-packages/langchain_core/_api/deprecation.py:139: LangChainDeprecationWarning: The class `AzureOpenAIEmbeddings` was deprecated in LangChain 0.0.9 and will be removed in 0.3.0. An updated version of the class exists in the langchain-openai package and should be used instead. To use it run `pip install -U langchain-openai` and import as `from langchain_openai import AzureOpenAIEmbeddings`.
  warn_deprecated(

File Causing the Issue:
https://github.com/mem0ai/mem0/blob/main/embedchain/embedchain/embedder/azure_openai.py
Steps to Reproduce:

Use the embedchain package with an Azure embedding model.
Upgrade the langchain package to a version greater than 0.2 and less than or equal to 0.3.
Observe the error message indicating that the AzureOpenAIEmbeddings class is deprecated.

Background
I’m actually here because I use the CrewAI package in Python, which utilizes the embedchain package. After upgrading the CrewAI package to version 0.41.1, I encountered an error when using an Azure embedding model. The error was caused by a dependency upgrade in the CrewAI package, which included a version of langchain that had deprecated the AzureOpenAIEmbeddings class. I tracked down the dependency chain to the embedchain package, which depends on langchain = “>0.2,<=0.3” and langchain-community = “^0.2.6”. Further investigation led me to the azure_openai.py file in the embedchain package, which was importing the deprecated AzureOpenAIEmbeddings class from langchain_community.embeddings. I found that this issue was almost fixed in a previous PR (#1437), but the azure_openai.py file was missed.
Dependency Chain:

Crew 0.41.1 > Crewaitools 0.4.26 > depends on embedchain = "^0.1.114" > langchain = ">0.2,<=0.3" and langchain-community = "^0.2.6"

Previous PR:
https://github.com/mem0ai/mem0/pull/1437/files (almost fixed the issue, but missed the azure_openai.py file)
Fix:
Update the azure_openai.py file to import the AzureOpenAIEmbeddings class from langchain_openai.embeddings instead of langchain_community.embeddings.
Request:
Please update the azure_openai.py file to use the updated AzureOpenAIEmbeddings class from langchain_openai.embeddings.

this should solve it #1459


Experimental component support

Related Issue
Adaptive Components: https://github.com/microsoft/AdaptiveCards/issues/4761
Description
This PR introduces "Adaptive Components", a new type of Adaptive Card element whose visual layout and schema is encapsulated in a single JSON file and downloaded on the fly.
No code review is required at this time.
Known issues

This is experimental - don't expect things to work flawlessly
Updating component properties in the JSON editor doesn't work
If there are multiple instances of the same component on the card, updating one instance's properties in the Property Sheet updates all instances' properties
When switching the host app or picking a different version in the version picker, the "Component" entry disappears from the toolbox
The service backing the component registry and components themselves in slow
It is not always clear when a component is still loading
If using more than one instance of a component with inputs in the same card, input Ids will collide and Action.Submit will only get the input values of the last instance
Component schemas are currently limited to a flat list of properties of type string or number only, and no constraints can be defined in terms of maximums/minimums etc.

Microsoft Reviewers: Open in CodeFlow

/azp run

/azp run

/azp run

/azp run

/azp run adaptivecards-nodejs-daily

Closing due to age - if this is still needed, please re-open


Multi-select menu element initial_options fail to load options in different option_groups

Reproducible in:
The slack_bolt version
slack-bolt==1.3.2
slack-sdk==3.3.2
Python runtime version
Python 3.7.2
OS info
Microsoft Windows [Version 10.0.19042.685]
Steps to reproduce:
Copy the self-contained example below to a new file and run (i.e. python reproducible_example.py). No additional setup required. As in the Bolt for Python tutorial, set the SLACK_BOT_TOKEN and SLACK_SIGNING_SECRET environment variables for a Slack app that has the home tab and event subscriptions enabled.
The example below responds to the @app.event("app_home_opened") event, so trigger it by switching focus back and forth from the app's home tab to another channel.
# reproducible_example.py

import os

from slack_bolt import App
from slack_sdk.models.blocks.basic_components import Option, OptionGroup
from slack_sdk.models.blocks.block_elements import StaticMultiSelectElement
from slack_sdk.models.blocks.blocks import InputBlock
from slack_sdk.models.views import View

app = App(
    token=os.environ.get("SLACK_BOT_TOKEN"),
    signing_secret=os.environ.get("SLACK_SIGNING_SECRET"),
)

option_1 = Option(label="Option 1", value="option_1")
option_2 = Option(label="Option 2", value="option_2")
option_3 = Option(label="Option 3", value="option_3")

options_without_group = [option_1, option_2]

options_with_groups = [
    OptionGroup(label="Group A", options=[option_1, option_2]),
    OptionGroup(label="Group B", options=[option_3]),
]

# ✔ Works as expected
initial_options_in_no_groups = {
    "options": options_without_group,
    "initial_options": [option_1, option_2],
}

# ✔ Works as expected
initial_options_in_same_group = {
    "option_groups": options_with_groups,
    "initial_options": [option_1, option_2],
}

# ❌ Fails with SlackApiError
# [ERROR] must be one of the provided options
# [json-pointer:view/blocks/0/element/initial_options]
initial_options_not_in_same_group = {
    "option_groups": options_with_groups,
    "initial_options": [option_1, option_3],
}

# inputs = initial_options_in_no_groups
# inputs = initial_options_in_same_group
inputs = initial_options_not_in_same_group

"""
Uncomment the inputs above to test the alternate scenarios

Note that initial_options is type Sequence[Option] so passing
an initial option group is not supported.
This is also consistent with the Block Kit reference:

initial_options: An array of option objects that exactly match
one or more of the options within options or option_groups.
https://api.slack.com/reference/block-kit/block-elements#static_multi_select
"""

home_tab = View(
    type="home",
    blocks=[
        InputBlock(
            label="Static multi select element",
            element=StaticMultiSelectElement(**inputs),
        ),
    ],
)

@app.event("app_home_opened")
def event_app_home_opened(client, event, ack):
    client.views_publish(user_id=event["user"], view=home_tab)
    ack()

if __name__ == "__main__":
    app.start(port=3000)

Expected result:
The expected behaviour is for the static multi-select element in the app home, on loading, to be populated with the provided initial_options arguments, as described at Block Kit > Reference: Block elements > Multi-select menu element > Static options> initial_options.

An array of option objects that exactly match one or more of the options within options or option_groups. These options will be selected when the menu initially loads.

This works as described/expected for options with no groups (in the example, set inputs = initial_options_in_no_groups), or options in the same group (inputs = initial_options_in_same_group, the result of which is shown below).

The expected result for the scenario where inputs = initial_options_not_in_same_group would be as in the image above, except for Option 1 and Option 3 to be ticked. However the actual result for this scenario is as below.
Actual result:
The app fails to load the initial_options and a SlackApiError is raised. This creates an obstacle for apps that depend on stateful multi-select elements that use option groups. Note that this only happens when one or more initial options is in a different group to another initial option, as shown in the alternate scenarios of the example.

slack_sdk.errors.SlackApiError: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'invalid_arguments', 'response_metadata': {'messages': ['[ERROR] must be one of the provided options [json-pointer:view/blocks/0/element/initial_options]']}}

The severity of the impact that this can have on an app might not be clear here, however it is significant in my use case which requires the state of the selected options to be loaded each time the user leaves and returns to the app. In my app initial_options is repopulated dynamically based on the user's choices, which are persisted between visits. At present I have been able to implement this by using  options rather than option_groups , but the quality of the user experience suffers where several options are not grouped in the menu drop-down list.
The issue here is that multi-select element initial options appear not to support multiple options that belong to different groups.
A related question to this issue is: would it be correct to assume that initial_options is the optimal way to load a multi-select element with predefined state (as I had been doing when encountering this issue), or is there another method intended for this?

Hi @tmvy, thanks a lot for taking the time to share the detailed issue! We've been able to reproduce your issue and @seratch also reproduced it using the Block Kit Builder app.
This is a server-side issue and I've escalated it to the Slack Platform team (linking back to this issue).
If you're okay with it, I'd like to close this issue. We're unable to fix the issue with the Bolt Framework and we're unable to estimate when the Slack Platform team will release the fix. The best way to stay informed of an update is to subscribe to the Slack API Changelog - you can even subscribe to the feed inside Slack.

Great, many thanks. Yes, happy to close this issue and await a resolution from the Slack Platform team.


tests/storage-vm: Check volume size rounding

Per Tom's request in https://github.com/canonical/lxd/pull/13470
EDIT: Not clear why tests are passing; they shouldn't. Will look at this more tomorrow.

latest/edge includes your fix now, but other channels tested here do not.
Does this add weight to the idea that it is a recent kernel change not present in in GH runners (yet) that is triggering this issue?

I get the same rounding behavior on:
root@c2d:~# lxc storage volume create default foo --type block size=24000000000
Storage volume foo created
root@c2d:~# zfs get -p volsize default/custom/default_foo
NAME                        PROPERTY  VALUE    SOURCE
default/custom/default_foo  volsize<PHONE_NUMBER>6  local
root@c2d:~# snap list lxd
Name  Version      Rev    Tracking   Publisher   Notes
lxd   git-5d43967  28646  5.21/edge  canonical✓  -
root@c2d:~# uname -a
Linux c2d 6.5.0-35-generic #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May  7 09:00:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

and:
sdeziel@sdeziel-lemur:~$ lxc storage volume create default foo --type block size=24000000000
Storage volume foo created
sdeziel@sdeziel-lemur:~$ zfs get -p volsize default/custom/default_foo
NAME                        PROPERTY  VALUE    SOURCE
default/custom/default_foo  volsize<PHONE_NUMBER>6  local
sdeziel@sdeziel-lemur:~$ snap list lxd
Name  Version      Rev    Tracking     Publisher   Notes
lxd   git-a2426b7  28721  latest/edge  canonical✓  -
sdeziel@sdeziel-lemur:~$ uname -a
Linux sdeziel-lemur 6.5.0-35-generic #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May  7 09:00:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
sdeziel@sdeziel-lemur:~$ modinfo zfs| grep ^version:
version:        2.2.0-0ubuntu1~23.10.2

Lxd previously rounded it to 8k

It's not the kernel...
wesley@jammy-azure-hwe-simple:~$ lxc init ubuntu:noble vtest --vm
Creating vtest
Error: Failed instance creation: Failed creating instance from image: Failed to run: zfs set volsize=13000007680 zfs/virtual-machines/vtest.block: exit status 255 (cannot set property for 'zfs/virtual-machines/vtest.block': 'volsize' must be a multiple of volume block size (16K))
wesley@jammy-azure-hwe-simple:~$ uname -a
Linux jammy-azure-hwe-simple 6.5.0-1021-azure #22~22.04.1-Ubuntu SMP Tue Apr 30 16:08:18 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
wesley@jammy-azure-hwe-simple:~$ sudo lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.4 LTS
Release:	22.04
Codename:	jammy
wesley@jammy-azure-hwe-simple:~$ snap list lxd
Name  Version        Rev    Tracking      Publisher   Notes
lxd   5.0.3-d921d2e  28373  5.0/stable/…  canonical✓  -

Somehow it's an inadequate test:
wesley@jammy-azure-hwe-simple:~$ lxc init ubuntu:noble vtest --vm
Creating vtest
Error: Failed instance creation: Failed creating instance from image: Failed to run: zfs set volsize=13000007680 zfs/virtual-machines/vtest.block: exit status 255 (cannot set property for 'zfs/virtual-machines/vtest.block': 'volsize' must be a multiple of volume block size (16K))
wesley@jammy-azure-hwe-simple:~$ lxc storage volume create zfs rt --type=block size=13GB
Storage volume rt created
wesley@jammy-azure-hwe-simple:~$ lxc storage volume show zfs custom/rt
config:
  size: 13GB
description: ""
name: rt
type: custom
used_by: []
location: none
content_type: block
project: default
created_at: 0001-01-01T00:00:00Z

Will look more on Tuesday.

As much as I'd like to understand why I can only replicate the failure by creating VMs instead of just storage volumes, this is now failing as I expect it to and can be used to ensure the fix is backported.

Thanks!


tests/kernel/sched/schedule_api fails on nrf5* boards

Describe the bug
The test case test_slice_reset in tests/kernel/sched/schedule_api failed on CI run but couldn't reproduce locally.
To Reproduce
Steps to reproduce the behavior:

mkdir build; cd build
cmake -DBOARD=nrf52_pca10040
make flash
See error

Expected behavior
All test cases should pass without any assert failure.
Screenshots or console output
***** Booting Zephyr OS zephyr-v1.13.0-2220-ga0b9e70e10 (delayed boot 1000ms) *****
Running test suite threads_scheduling
===================================================================
starting test - test_priority_cooperative
PASS - test_priority_cooperative
===================================================================
starting test - test_priority_preemptible
PASS - test_priority_preemptible
===================================================================
starting test - test_yield_cooperative
PASS - test_yield_cooperative
===================================================================
starting test - test_sleep_cooperative
PASS - test_sleep_cooperative
===================================================================
starting test - test_sleep_wakeup_preemptible
PASS - test_sleep_wakeup_preemptible
===================================================================
starting test - test_pending_thread_wakeup
PASS - test_pending_thread_wakeup
===================================================================
starting test - test_time_slicing_preemptible
PASS - test_time_slicing_preemptible
===================================================================
starting test - test_time_slicing_disable_preemptible
PASS - test_time_slicing_disable_preemptible
===================================================================
starting test - test_lock_preemptible
PASS - test_lock_preemptible
===================================================================
starting test - test_unlock_preemptible
PASS - test_unlock_preemptible
===================================================================
starting test - test_sched_is_preempt_thread
PASS - test_sched_is_preempt_thread
===================================================================
starting test - test_slice_reset

    Assertion failed at /home/jenkins/workspace/zephyr-master-ci-master/zephyr.git/tests/kernel/sched/schedule_api/src/test_sched_timeslice_reset.c:46: thread_tslice: t <= expected_slice_max is false

    Assertion failed at /home/jenkins/workspace/zephyr-master-ci-master/zephyr.git/tests/kernel/sched/schedule_api/src/test_sched_timeslice_reset.c:45: thread_tslice: t >= expected_slice_min is false

    Assertion failed at /home/jenkins/workspace/zephyr-master-ci-master/zephyr.git/tests/kernel/sched/schedule_api/src/test_sched_timeslice_reset.c:45: thread_tslice: t >= expected_slice_min is false

FAIL - test_slice_reset
===================================================================
starting test - test_slice_scheduling
PASS - test_slice_scheduling
===================================================================
starting test - test_priority_scheduling
ABCDEFGHI
ABCDEFGHI
ABCDEFGHI
ABCDEFGHI
ABCDEFGHI
PASS - test_priority_scheduling
===================================================================
starting test - test_wakeup_expired_timer_thread
PASS - test_wakeup_expired_timer_thread
===================================================================
Test suite threads_scheduling failed.
===================================================================
PROJECT EXECUTION FAILED

Environment (please complete the following information):

OS: Linux
Toolchain: Zephyr SDK 0.9.5
Commit SHA or Version used: ga0b9e70e10 (on which the failure was seen, may not be the first hit)

Since the failure is not seen locally, I couldn't git bisect to find on what commit the failure was first seen.

@inakypg @nashif @kumarvikash1: JFYI

@pizi-nordic can you take a look?

It seems that this failure is caused by the same issue that triggered the https://github.com/zephyrproject-rtos/zephyr/issues/11722.
I was not able to reproduce it on unmodified code, however after altering the nrf_rtc_timer.c which enforced late execution of the z_clock_announce() (few ticks after expected time) the test failed in the same way as described in the bug report.
FYI: @carlescufi, @pdunaj, @andyross

This test is failing very seldom in native_posix too. So I do not think this is a platform specific issue. Neither valgrind or address sanitizer detect the problem.

It seems this issue caused by nrf5* timer delay which will trigger same priority thread time slice schedule. And can we check timer delay issue from platform respective? Actually I do see the difference of system tick between nrf5* board and other Arm boards. Normal Arm boards use Systick interrupt to calculate system tick. And nrf5* board use RTC to do it with IRQ num NRF5_IRQ_RTC1_IRQn = 17, maybe a little lower priority than other arm boards. And from the code I also see that nrf5* boards has some other interrupts(like NRF5_IRQ_POWER_CLOCK_IRQn and NRF5_IRQ_TEMP_IRQn) with higher priority than RTC's.

@wentongwu: Actually it's simpler than that.  The patch @spoorthik and @nashif bisected to was just an emulator workaround.   The original code would spin waiting on a specified number of ticks to pass, which was tickling bugs on x86_64 so I replaced it with a simpler busy wait, which worked everywhere except on nRF.
The difference in behavior is tick alignment: the old code was always exiting the wait loop immediately after a tick had expired, where the new one is exactly N milliseconds[1], and likely to be anywhere between two tick boundaries.  Later code is then checking time deltas in ticks and sees a +/- 1 tick aliasing issue where the aligned code does not.  nRF tends to see these issues more easily because it's underlying clock counter is running at a very different rate than other platforms; it makes a great bug magnet for timer stuff.
In this case I think the right solution is to revert the patch (I just checked and indeed a simple reversion fixes the issue) and come up with a more targetted workaround for x86_64.  We've actually swapped qemu versions in CI since this was added; it's possible the bug isn't visible any more...
[1] "Exact" to the precision of the underlying timer, anyway.


'FirebaseDatabaseUI/FirebaseDatabaseUI.h' file not found

Seems to be similar to #38

In Podfile I have
use_frameworks! :linkage => :static
use_modular_headers!
pod 'FirebaseUI'

The file does exist at that location though:

It seems to be the newer version of FirebaseUI at dependencies. I tried to add these to react-native-firebaseui-auth.podspec and it works now
s.dependency 'FirebaseDatabaseUI'
s.dependency 'FirebaseAuthUI'
s.dependency 'FirebaseFirestoreUI'
s.dependency 'FirebaseOAuthUI'
s.dependency 'FirebasePhoneAuthUI'
s.dependency 'FirebaseAnonymousAuthUI'
s.dependency 'FirebaseEmailAuthUI'
s.dependency 'FirebaseFacebookAuthUI'
s.dependency 'FirebaseGoogleAuthUI'
s.dependency 'FirebaseStorageUI'

@fabyeah You can refer my folk commit at
https://github.com/hunglmtb/react-native-firebaseui-auth/commit/594ed7a1d880d410525cd8ee89680e89b7593db4

Thanks @hunglmtb!
@fabyeah this issue has been fixed, please upgrade to version 1.4.0 that supports iOS FirebaseUI 13


Error to include libmagic

I have an error when I try to package my program, one of the libraries that the executable programm needs is the libmagic.  The executable works in my laptop, but when I try to execute it in a friend's laptop, it shows the following error:
ImportError: failed to find libmagic.  Check your installation.
I try to include python-magic-bin to include the library but that not work, there is another option to makes libmagic work in a Nuitka executable.
I try to use the following command to generate the executable:
python -m nuitka --standalone --include-package=python-magic-bin --include-data-files=./magic_dlls/*=./ --windows-icon-from-ico=.\assets\mictlan_logo_dark.ico .\watcher.py
But i get the following error:
FATAL: Error, failed to locate package 'python-magic-bin' you asked to include.

Nuitka version
python -m nuitka --version shows the below info:
1.9.7
Commercial: None
Python: 3.10.7 (tags/v3.10.7:6cc6b13, Sep  5 2022, 14:08:36) [MSC v.1933 64 bit (AMD64)]
Flavor: CPython Official
Executable: C:\Python310\python.exe
OS: Windows
Arch: x86_64
WindowsRelease: 10
Version C compiler: C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.36.32532\bin\Hostx64\x64\cl.exe (cl 14.3).

How did you install Nuitka and Python -> Using pip

Many times when you get an error from Nuitka, your setup may be special
This error persist over and over again in my friend's laptop.

/

The --include-package takes not distribution names, but package names. Read up on the difference.
Not having a reproducer I cannot really do anything to resolve it in some sort of way. Please provide one, or we will have to close it.

Thanks for your quick response, I assign to --include-package flag the name of the python-magic-bin library that it suppose to install libmagic for windows which is my target OS for running my program.  But when I try to run my program on windows it crashed and show the error message :
ImportError: failed to find libmagic.  Check your installation
But in my code I import magic library.
The interesting here is that in my PC the program works.
I need help to figure out how to install libmagic using python libraries or maybe if someone has solved before.
Give a couple of hour to try to create a minimal example to reproduce the error.
Thanks.

@nachocodexx can you please tell us precisely how you installed libmagic and a minimal reproducer of the code.

Sorry  for taking to long to reply, I made the decision to remove that dependency from my client and send it to the server, it was easier.
Sorry for the inconvenience, I will close this issue.


Git Graph does not show for local repo.

I have created a folder.
open by code  folder name
as I want to integrate with GitHub, on the terminal ->

cd < folder Name>
git init
edited some file and added into the folder.
git add .
git commit -m "message"
git branch

while clicking on git-graph tab not showing git graph

This looks like a problem with the GitGraph extension. Please report the issue here: https://github.com/mhutchie/vscode-git-graph


Mistype  in documentation npm add

Description
If my understanding is correct, I think there is no subcommand of npm add in npm.
Probably mixed with yarn add.
Suggested solution
Replace npm add to npm install in documentation
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

https://docs.npmjs.com/cli/v8/commands/npm-install

npm install [ ...]
aliases: add, i, in, ins, inst, insta, instal, isnt, isnta, isntal, isntall


Dead link in issue template

Hi, related to issue #375, I found another 404 in the issue template.
What version of textlint are you using?
v9.1.1
What file type (Markdown, plain text, etc.) are you using?
N/A
What did you do? Please include the actual source code causing the issue.
Create a new issue. I see the template in the textarea with wrong link.
What did you expect to happen?
Correct link to bug-reporting guide.
What actually happened? Please include the actual, raw output from textlint.
<!--
**Before** Bug Reporting, Please update textlint and try it.
Also see https://github.com/textlint/textlint/blob/master/CONTRIBUTING.md#bug-reporting
-->

The link should be https://github.com/textlint/textlint/blob/master/.github/CONTRIBUTING.md#bug-reporting.

Opps. Thanks for report.
Can you create PR?

@azu Yes I will create PR.


[TablePlus] ...

Extension – TablePlus
Author:

Description

Steps To Reproduce
1.search database
2.open database

The current behavior
The expected behavior
Raycast version

Can I please re-open this bug? It's still occurring for me.
Attempting to open any table via the Raycast extension gives an "Invalid URL" error.
Steps to reproduce:

Open Raycast
Search for 'tableplus'
Move to the Search Databases command
Open any connection

Expect: Database to open.
Actual: Error is presented (as in screenshot above): "Error Invalid URL"
Opening the same connection directly from TablePlus is working as expected.
Raycast v1.49.2
TablePlus Version 5.3.6 (496)
MacOS Ventura 13.3.1 (22E261)
@pernielsentikaer I think you were the original dev? Any ideas?

Ah, looks like it might be related to a custom data directory-
I've set a different directory in Tableplus > Preferences > Locations > Connections.
Copying this directory to the Raycast TablePlus Extension Settings seems to work correctly. 👍🏻

This was created before our new system where the author gets tagged so I didn't notice.
Did you have any items on the list when you opened the extension when the "wrong" path was added?

No worries.
Yeah- the Raycast plugin was showing 2 connections that were in my original data directory before I moved it. (ie. ~/Library/Application Support/com.tinyapp.TablePlus/Data/Connections.plist No worries, I think this issue can be closed.

Thanks for confirming 😊


[Question] Calculating ELBO

First of all I just wanted to say that I found this paper fascinating and thanks for releasing the code!
I have recently been working on implementing the Weight Uncertainty in Neural Networks paper and I noticed that the calculation of the ELBO term is a little different to what you have implemented here.
Equation 2 of the WUINN paper aims to approximate the loss by using the difference between the log probabilities of the prior and posterior distribution whereas your code implements a more direct approach to the KL Divergence by calculating the entropy and cross entropy.
You have noted in the comments that:
entropy = \sum_i log \sigma_i + c
I was wondering how you are able to use this approach rather than sampling from the posterior distribution? Is this a case of using the reparameterization trick?
I'd be grateful for any guidance!
Thanks again.

Hi Daniel,
WUNN does the same thing we do, just with a different approximate posterior. The entropy of the prior distribution is just the expectation of the log probability density function of the prior on the approximate posterior distribution, and cross entropy the expectation of the log probability of the approximate posterior.
Where we calculate the entropy, we know the analytical form of the prior function and the approximate posterior function and in this case we can calculate the exact value, which is given by that equation (full derivation is in the Appendix of the paper, and is pretty involved). For the other term we can't do it analytically and need to sample from the approx posterior.
Hope that helps!

Thank you for your response!
Just to clarify: the entropy is the expected value of the log likelihood of the sample evaluated over the posterior distribution - and the cross entropy is the expected value of the log likelihood of the samples from the posterior under the prior?
Am I right in saying that as this is often intractable (not in this case) one of the standard approaches is to use MFVI to calculate the ELBO term?
I had a look at the Appendix but that derivation was rather daunting - I'll have to set aside some more time to look through that.

Right, specifically we're talking about the entropy of the approximate posterior (under the approximate posterior distribution) and the cross-entropy between the approximate posterior and the prior. If you write it out, this rearranges to just be the KL between the approximate posterior and the prior.
Whether this is analytically tractable depends on your choices for the prior and approximate posterior. When you do MFVI, it is analytically tractable because everything is a Gaussian. In our case, one term is analytically tractable, but the other is not, so we do Monte Carlo integration to estimate the expectation.
Yes the full derivation is daunting. Once the transformation used is clear the rest is just algebra, if complicated algebra.


URI equivalence is not good enough

Trying to setup the 'caldav-tester' test-suite, I've found that I was unable to even really start the tests.
The problem lies in the fact that the caldav tester automatically encodes a url such as:
/~evert/sabre/dav/

into
/%7Eevert/sabre/dav/

While this may not be 100% the preferred URL, sabredav should still properly deal with this situation.

Requires https://github.com/fruux/sabre-uri/pull/1


Feature: Ctrl/Cmd + Enter runs the query

Allow the keyboard shortcut Ctrl/Cmd + Enter to run the query

Added as Shift + (Option|Alt) + Enter


Array Type element constraint, extends(atleast), implements(unique) Union type or | keyof

Well this is pretty simple, the ability to be able to add constraint the an array items element, to ensure that their is only one implementation of a list of items, single unqiue implementations or the other is that their be at least one implementation of each item, were duplicates are allow.
One could things maybe of needing the ability to do compounds, or support multiple with common syntax, which would then allow one to implement pre-joined pairs from two different.
type Keys = string [];

type Kinds = 'object' | 'array' | 'alter'

interface base {
    kind : Kinds
}

type HasKeysIsKind = {keys : Keys, kind : Kinds, childrenKey : string | undefined};

Array, their is at least one and one only implementation of an item, with element that belongs to the key constraint.
Conforming Implementation, unique one implementation for each kind
const UniqueOneImplementationForEachKinds : HasKeysIsKind [kindElement implements Kinds] = [
    {
      keys : ['_inner','children'],
      kindElement : 'object',
      childrenKey : 'schema'
    },
    {
      keys : ['_inner','items'],
      kindElement : 'array',
      childrenKey : undefined
    },
    {
      keys : ['_inner','matches'],
      kindElement : 'alter',
      childrenKey : 'schema'
    }
    ];

MissingKey, their is a missing key, their must be entry for at least every key
const ErrorMissingKey : HasKeysIsKind [kindElement implements Kinds] = [
    {
      keys : ['_inner','children'],
      kindElement : 'object',
      childrenKey : 'schema'
    },
    {
      keys : ['_inner','items'],
      kindElement : 'array',
      childrenKey : undefined
    },
    {
      keys : ['_inner','matches'],
      kindElement : 'error invalid key', // error invalid key.
      childrenKey : 'schema'
    }
    ];

Error Duplicate, their can only be one implementation, duplicate not allowed
const ErrorDuplicateKey : HasKeysIsKind [kindElement implements Kinds] = [
    {
      keys : ['_inner','children'],
      kindElement : 'object',
      childrenKey : 'schema'
    },
    {
      keys : ['_inner','items'],
      kindElement : 'array',
      childrenKey : undefined
    },
    {
      keys : ['_inner','matches'],
      kindElement : 'alter', // error invalid key.
      childrenKey : 'schema'
    }
    {
        keys : ['_inner','matches','children'],
        kindElement : 'object', // error duplicate key
        childrenKey : 'inner'
      }
    ];

Conforming implementation, their is at least on key for each
const UniqueOneImplementationForEachKinds : HasKeysIsKind [kindElement extends Kinds] = [
    {
      keys : ['_inner','children'],
      kindElement : 'object',
      childrenKey : 'schema'
    },
    {
      keys : ['_inner','items'],
      kindElement : 'array',
      childrenKey : undefined
    },
    {
      keys : ['_inner','matches'],
      kindElement : 'alter',
      childrenKey : 'schema'
    }
    ];

Conforming Implementation, at least on key for each, duplicates allowed.
const DuplicateKeyAllGood : HasKeysIsKind [kindElement extends Kinds] = [
    {
      keys : ['_inner','children'],
      kindElement : 'object',
      childrenKey : 'schema'
    },
    {
      keys : ['_inner','items'],
      kindElement : 'array',
      childrenKey : undefined
    },
    {
      keys : ['_inner','matches'],
      kindElement : 'alter', // error invalid key.
      childrenKey : 'schema'
    }
    {
        keys : ['_inner','matches','children'],
        kindElement : 'object', // error duplicate key
        childrenKey : 'inner'
      }
    ];

Error Missing Key, their must be at least one implementation for each key.
    // Missing array key.
    const DuplicateKeyAllGoodMissingKeyError : HasKeysIsKind [kindElement extends Kinds] = [
        {
          keys : ['_inner','children'],
          kindElement : 'object',
          childrenKey : 'schema'
        },
        {
          keys : ['_inner','matches'],
          kindElement : 'alter', // error invalid key.
          childrenKey : 'schema'
        }
        {
            keys : ['_inner','matches','children'],
            kindElement : 'object', // error duplicate key
            childrenKey : 'inner'
          }
        ];

Multiple constraints
this allows allow SQL like statement join patterns for defining paring of elements, which one can use when want to describe how the data is being paired for iteration purposes.
type TableAKinds = 'A1' | 'A2' | 'A3'
type TableBKinds = 'B1' | 'B2' | 'B3'

interface TableA {
    kindElement : string,
    TableAOtherPropA : number
}

interface TableB {
    kindElement : string,
    TableAOtherPropB : number
}

interface JoinPair {
    tableA : TableAKinds,
    tableB : TableBKinds
}

type TableALeftJoinTablB = JoinPair [TableA implements TableAKinds, TableB extends TableBKinds] = [
    {tableA:'A1' , tableB 'B1'}
]
type TableARightJoinJoinedTablB = JoinPair [TableA extends TableAKinds, TableB implements TableBKinds] =..

type TableARInnterJoinTablB = JoinPair [TableA implements TableAKinds, TableB implements TableBKinds] =..

type TableAFullOuterTableB = JoinPair [TableA extends TableAKinds, TableB extends TableBKinds] =..

The other requirement, which is what I would require, is that the array constraints, be extendable,
which means I can write a base accumulator routine, and still have it extendable.
It would probably be best to take a look at this post, to understand and get some context for were this is going: https://github.com/Microsoft/TypeScript/issues/25671

type Keys = string [];
type Kinds = 'object' | 'array' | 'alter'

interface base {
kind : Kinds
}
AppproachA
type ExtendedKinds<T extends string> = Kinds | T;

type HasKeysIsKind = {keys : Keys, kindElement : Kinds, childrenKey : string | undefined};

type KindsExtends = 'Ex1' | 'Ex2' | 'Ex3'

type Extended = [implements KindsExtends] extends HasKeysIsKind [kindElement implements Kinds]

const extended : Extended = Which can now add additional keys mappings, at level were things have been extended or enhanced, outside the base scope implementation.

function SummaryAccumulator<ACC, ACC_KIND extends string, KIND extends ExtendedKinds<ACC_KIND>>(kindIdentityExtraction : HasKeysIsKind [kindElement implements Kinds], initAcc : (kind : KIND) => ACC)
{
    for (let i = 0; i < kindIdentityExtraction.length; i++)
    {
        const type = kindIdentityExtraction[i];
        const newAcc = initAcc(type.kindElement as any as KIND);  // seem to be that the compile is falling over, this constian should work, looks like another bug.
        const newAcc2 = initAcc(type.kindElement);  // expect compile fall over for the base set of constraints implied.
    }
}

@jack-williams With out having to go flesh out a whole bunch of examples, I think the easiest would be to check the following websites, for SQL joins, in which the patterns above are almost the same, hopefully you should see were I was going with things.
https://www.w3schools.com/sql/sql_join.asp
https://www.w3schools.com/sql/sql_join_left.asp

We really don't want to build a complex SQL-like array schema validation system into the language. This is the kind of thing that can be checked very easily, once, at runtime in a much more expressive way than we could reasonably do in a type system.


Fix crashing Android Example

using the same implementation as vision-camera-ocr ensures the example works in android

d

Fixed in https://github.com/jorgebrunetto/vision-camera-code-scanner

Thank @jorgebrunetto, it work for me.

it works for me.

[ ]


Option to skip automatically downloading series

Describe your suggested feature
Downloading new chapters should have an option to filter out series with certain conditions similar to the "Skip updating titles" option.
EX. With unread chapter(s), without downloaded chapter(s), etc.
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version 1.8.5.
[X] I will fill out all of the requested information in this form.

Add those series to a auto-download excluded category


sync-users scripts fails with airflow 2.3.x and 2.4.x with 8.6.1 chart version

Checks

[X] I have checked for existing issues.
[X] This report is about the User-Community Airflow Helm Chart.

Chart Version
8.6.1
Kubernetes Version
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.1", GitCommit:"8f94681cd294aa8cfd3407b8191f6c70214973a4", GitTreeState:"clean", BuildDate:"2023-01-18T15:58:16Z", GoVersion:"go1.19.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.5", GitCommit:"34f89fd3fb1a106e1b23d3454b2f2cbf305602a1", GitTreeState:"clean", BuildDate:"2023-02-10T14:48:59Z", GoVersion:"go1.19.4", Compiler:"gc", Platform:"linux/amd64"}

Helm Version
version.BuildInfo{Version:"v3.8.0", GitCommit:"d14138609b01886f544b2025f5000351c9eb092e", GitTreeState:"clean", GoVersion:"go1.17.5"}

Description
I upgraded airflow with below changes.

Component
Current Version
Target version

Airflow helm chart
8.5.3
8.6.1 (2.2.5-python3.8)

Airflow
2.1.4-python3.8
2.4.3-python3.10

All other pods are working fine. Only 1 container sync-users keep on failing with " Multiple classes found for path "Permission" in the registry of this declarative base. Please use a fully module-qualified path".
other pods e.g. web, db_check and db_migrations also give the same warning message from configuration.py but they do not fail.
I have tried that with 3.9  or 3.8 python version as well and same error. I cannot directly go back airflow version as then db_migrations fails.
I read other issues 607, 592  and 572.  I notice they are specific to 2.3.x but the issue I face seems to be exactly the same as reported by softestplease in issue 607
Is there any work around for that or?
Relevant Logs
/home/airflow/.local/lib/python3.10/site-packages/airflow/configuration.py:545: DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
  option = self._get_environment_variables(deprecated_key, deprecated_section, key, section)
/home/airflow/.local/lib/python3.10/site-packages/airflow/configuration.py:545: DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
  option = self._get_environment_variables(deprecated_key, deprecated_section, key, section)
/home/airflow/.local/lib/python3.10/site-packages/airflow/configuration.py:545 DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
/home/airflow/.local/lib/python3.10/site-packages/airflow/configuration.py:545 DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
/home/airflow/.local/lib/python3.10/site-packages/airflow/configuration.py:545 DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
/home/airflow/.local/lib/python3.10/site-packages/airflow/configuration.py:545 DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
Traceback (most recent call last):
  File "/mnt/scripts/sync_users.py", line 142, in <module>
    flask_app = www_app.create_app()
  File "/home/airflow/.local/lib/python3.10/site-packages/airflow/www/app.py", line 144, in create_app
    init_appbuilder(flask_app)
  File "/home/airflow/.local/lib/python3.10/site-packages/airflow/www/extensions/init_appbuilder.py", line 648, in init_appbuilder
    AirflowAppBuilder(
  File "/home/airflow/.local/lib/python3.10/site-packages/airflow/www/extensions/init_appbuilder.py", line 160, in __init__
    self.init_app(app, session)
  File "/home/airflow/.local/lib/python3.10/site-packages/airflow/www/extensions/init_appbuilder.py", line 206, in init_app
    self.sm = self.security_manager_class(self)
  File "/home/airflow/.local/lib/python3.10/site-packages/airflow/www/security.py", line 193, in __init__
    super().__init__(appbuilder)
  File "/home/airflow/.local/lib/python3.10/site-packages/airflow/www/fab_security/sqla/manager.py", line 68, in __init__
    user_datamodel = SQLAInterface(self.user_model)
  File "/home/airflow/.local/lib/python3.10/site-packages/flask_appbuilder/models/sqla/interface.py", line 68, in __init__
    for prop in class_mapper(obj).iterate_properties:
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/orm/base.py", line 442, in class_mapper
    mapper = _inspect_mapped_class(class_, configure=configure)
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/orm/base.py", line 421, in _inspect_mapped_class
    mapper._check_configure()
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/orm/mapper.py", line 1916, in _check_configure
    _configure_registries({self.registry}, cascade=True)
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/orm/mapper.py", line 3429, in _configure_registries
    _do_configure_registries(registries, cascade)
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/orm/mapper.py", line 3468, in _do_configure_registries
    mapper._post_configure_properties()
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/orm/mapper.py", line 1933, in _post_configure_properties
    prop.init()
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/orm/interfaces.py", line 231, in init
    self.do_init()
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/orm/relationships.py", line 2150, in do_init
    self._process_dependent_arguments()
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/orm/relationships.py", line 2245, in _process_dependent_arguments
    self.target = self.entity.persist_selectable
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 1113, in __get__
    obj.__dict__[self.__name__] = result = self.fget(obj)
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/orm/relationships.py", line 2112, in entity
    argument = self._clsregistry_resolve_name(self.argument)()
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/orm/clsregistry.py", line 393, in _resolve_name
    rval = d[token]
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/util/_collections.py", line 746, in __missing__
    self[key] = val = self.creator(key)
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/orm/clsregistry.py", line 352, in _access_cls
    return _determine_container(key, decl_class_registry[key])
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/orm/clsregistry.py", line 313, in _determine_container
    value = value.attempt_get([], key)
  File "/home/airflow/.local/lib/python3.10/site-packages/sqlalchemy/orm/clsregistry.py", line 144, in attempt_get
    raise exc.InvalidRequestError(
sqlalchemy.exc.InvalidRequestError: Multiple classes found for path "Permission" in the registry of this declarative base. Please use a fully module-qualified path.
Stream closed EOF for elyra-airflow/elyra-airflow-sync-users-5584bb9967-8wfxr (sync-airflow-users)

Custom Helm Values
airflow:
  # enable persistence of logs

  # Custom ingress to enable multiple hosts
  hosts:
    - <hostname>

  # https://github.com/airflow-helm/charts/blob/main/charts/airflow/values.yaml

  ingress:
    enabled: false

  postgresql:
    enabled: false

  externalDatabase:
    host: airflow-db
    database: airflow
    user: airflow
    passwordSecret: elyra-airflow-db-password
    passwordSecretKey: password

  arcticdataDatabase:
    host: arcticdata-db
    database: arcticdata
    passwordSecret: arcticdata-db-password

  pgbouncer:
    enabled: false

  airflow:
    image:
      pullPolicy: IfNotPresent
      repository: apache/airflow
      tag: 2.4.3-python3.10
      gid: 0
    executor: KubernetesExecutor
    config:
      AIRFLOW__KUBERNETES__WORKER_CONTAINER_REPOSITORY: "apache/airflow"
      AIRFLOW__KUBERNETES__WORKER_CONTAINER_TAG: "2.4.3-python3.10"
      AIRFLOW__KUBERNETES__LOGS_VOLUME_CLAIM: "airflow-logs"
      AIRFLOW__KUBERNETES__DAGS_VOLUME_CLAIM: "airflow"
      AIRFLOW__KUBERNETES__NAMESPACE: "airflow" # Deployment namespace
      AIRFLOW__KUBERNETES__DELETE_WORKER_PODS: "True"
      AIRFLOW__CORE__LOAD_EXAMPLES: "False"
      AIRFLOW__SCHEDULER__DAG_DIR_LIST_INTERVAL: "300"
      AIRFLOW__KUBERNETES__GIT_SYNC_ONE_TIME: "False"
      AIRFLOW__LOGGING__REMOTE_LOGGING: "True"
      AIRFLOW__LOGGING__REMOTE_BASE_LOG_FOLDER: "s3://airflow-logs"
      AIRFLOW__LOGGING__REMOTE_LOG_CONN_ID: "minio"
    extraEnv:
      - name: MINIO_ACCESS_KEY
        valueFrom:
          secretKeyRef:
            name: minio-secret
            key: accessKey
      - name: MINIO_SECRET_KEY
        valueFrom:
          secretKeyRef:
            name: minio-secret
            key: secretKey

    connections:
      - id: minio
        type: s3
        description: Minio connection
        host: minio
        port: 9000
        login: ${MINIO_ACCESS_KEY}
        password: ${MINIO_SECRET_KEY}
        extra: |-
          { "aws_access_key_id": "${MINIO_ACCESS_KEY}",
            "aws_secret_access_key": "${MINIO_SECRET_KEY}",
            "host": "http://minio:9000",
            "region_name":"eu-central-1" }
    connectionsTemplates:
      MINIO_ACCESS_KEY:
        kind: secret
        name: minio-secret
        key: accessKey
      MINIO_SECRET_KEY:
        kind: secret
        name: minio-secret
        key: secretKey
    dbMigrations:
      enabled: true

  dags:
    path: /opt/airflow/dags
    gitSync:
      enabled: true #initial stop change it once verification is done
      repo: "git@github.com:<repo path>.git"
      branch: dev
      sshSecret: airflow-dags-ssh-secret
      sshSecretKey: id_rsa

  workers:
    enabled: false

  redis:
    enabled: false

  flower:
    enabled: false

I installed completely new 2.1.4-python3.8 with chart 8.6.1. I then upgraded to 2.3.2 -python3.10 and got the same error.

Continuing further I tried to have fresh install of  2.3.x on chart version 8.6.1. All versions 2.3.1 and above had the same issue. So, this does not seems to be related any db_migrations tasks.
airflow 2.3.0 gives below error for all the pods because check_db container gives below error.
raise AirflowConfigException(f"error: cannot use sqlite with the {self.get('core', '  executor')}")                                                                            airflow.exceptions.AirflowConfigException: error: cannot use sqlite with the KubernetesExecutor

@arundeep78 my thoughts:

The values you provided look incorrectly indented, especially around externalDatabase, and postgres, I highly recommend starting from one of the sample files, for example the sample-values-CeleryExecutor.yaml
Because of 1, you were probably not installing into a clean database (as the embedded postgres PVC will have to be manually deleted from the namespace)
Can you try using a newer version of airflow 2.3, because 2.3.0 has many issues? (The latest is 2.3.4)

@thesuperzapper

The values.yaml may look wrongly indented just in github. These worked fine on the old setup and it works fine for all the pods even on the new version. if you see any specific information in value,yaml that can break a very specific container's i.e. sync-users file sync-users.py file, then that would be helpful.
No, I am not using embedded postgres, this is configured by externalDatabase running postgres:15.2.
I mentioned above that I have tried upgrade to 2.3.x and also completely new installations on 2.3.X. Just that 2.3.0 fails with a different error as I mentioned above about sqllite. and all other fails with same error with sync-users,py file. I even tried 2.5.1 airflow and it has exactly same error.

I also referred to another issue where another user also reported the same issue.
The last airflow version that successfully works for completely new inatallation is 2.2.5-python3.9. I have not tried the upgrade yet.
But, till I get some another direction/hint/solution next steps are.

Try upgrade  to 2.2.5-python3.9
Try official airflow helm chart for 2.3.x and 2.5.1 and see what happens.

Try upgrade  to 2.2.5-python3.9

I install new 2.1.4-python3.8 and upgraded to 2.2.5-python3.9 and it works.
I tried further upgrade to 2.3.4-python3.9 as sometimes 2 step upgrade works (although I was not positive in this case as clean install did not work) . As expected this upgrade failed with same container  failing with sync-users.py with same error message.
sqlalchemy.exc.InvalidRequestError: Multiple classes found for path "Permission" in the registry of this declarative base. Please use a fully module-qualified path.
Which happens as mentioned in the main document in
File "/mnt/scripts/sync_users.py", line 142, in <module>    flask_app = www_app.create_app() File "/home/airflow/.local/lib/python3.9/site-packages/airflow/www/app.py", line 136,  in create_app                                                       init_appbuilder(flask_app)

I currently have another issue with "remote error: tls: bad record MAC" when using helm, so I could not continue the investigation. But, I will report back on new status soon. I may have an error, but cannot verify at the moment due to this tls issue.


Implemented overridable config and functions structure

The pull request allows for overriding variables set in base_config.sh en base_functions.sh by providing a custom config.sh and/or functions.sh in the sub-Dockerfile

:+1:


fix: don't error for Parse

Previously, Parse<Eny> (most often achieved indirectly by allowing calling this with a generic that is constrained to Eny) resulted in the following error: Type instantiation is excessively deep and possibly infinite.
Fixes this by short-circuiting Eny extends T to unknown
Also update lockfile to pnpm 8 and drops node 14 support in CI

Codecov Report

Merging #117 (a6c2ab0) into master (a96dbdf) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff            @@
##            master      #117   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           18        13    -5
  Lines          350       257   -93
  Branches       104        76   -28
=========================================
- Hits           350       257   -93

Flag
Coverage Δ

eslint-plugin-vality
?

vality
100.00% <ø> (ø)

vality-env
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 5 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add overlay video rendering on WKWebView

Based on work by @pererikb in https://github.com/EricssonResearch/bowser/pull/46

Replaced by https://github.com/EricssonResearch/bowser/pull/68.


Exclude hive-exec-1.0.1.jar from gobblin-distribution.tar.gz

The gobblin-distribution-[projectVersion].tar.gz that is generated includes the hive-exec-1.0.1.jar, which fat jars all its dependencies, including guava-11.0.2.jar. This causes a lot of problems because Gobblin is dependent on guava-15.0.jar. This causes problems similar to https://github.com/linkedin/gobblin/issues/804
Hive provides a non-fat jar verison of hive-exec called hive-exec-core-1.0.1.jar, we have explicit dependencies on this non-fat jar version in gobblin-compaction, gobblin-core, and gobblin-hive-registration.
The problem is that gobblin-compaction has an explicit dependency on hive-service-1.0.1.jar which has a transitive dependency on hive-exec-1.01.jar (the Fat Jar version). So ultimately hive-exec-1.0.1.jar and hive-exec-core-1.0.1.jar both end up as in the tar-ball.
It seems that only Hive gobblin-compaction needs the hive-service-1.0.1.jar as a dependency, perhaps we can re-organize the code and create three submodules under gobblin-compaction called gobblin-hive-compaction, gobblin-mr-compaction, and gobblin-compaction-api. This way gobblin-distribution doesn't need to have a dependency on gobblin-hive-compaction - the module can create its own tar-ball (which I think it is doing already).
@zliu41 what do you think?

I'll double check if hive-service is really needed for hive compaction because I doubt it. If it is then we can do what you suggested.

If it possible to just exclude the dependency from hive-service-1.0.1.jar to hive-exec-1.01.jar and explicitly include hive-exec-core-1.0.1.jar?

It may be possible, but I couldn't find a clean way to do it. Excluding the dependency is easy, but I can't find a way to include something that has already been excluded.

Can you do something like: http://stackoverflow.com/questions/30728533/gradle-override-transitive-dependency-by-version-classifier

Yeah that works, I created a PR: https://github.com/linkedin/gobblin/pull/832
My goal was to add the exclusion rule in gobblin-distribution/build.gradle so hive-exec would be excluded regardless of which sub-module pulls it in, but I'm not sure if thats possible.

Fixed in #832


istioctl verify-install not working properly with multiple IstioOperators

Bug Description
The istioctl verify-install command is not checking all the resources created by different Istio Operators, only from the first one it finds.
In our setup we have one IstioOperator installing the controlplane, and then one IstioOperator per ingress gateway using the empty profile.
When running the istioctl verify-install command it only checks the resources from the first istio operator it finds.
List of operators:
➜  ~ istioctl x revision list

REVISION TAG      ISTIO-OPERATOR-CR                  PROFILE REQD-COMPONENTS
default  <no-tag> istio-system/eastwestgateway       empty   ingress:istio-eastwestgateway
                  istio-system/ingress-microservices empty   ingress:istio-ingressgateway-microservices
                  istio-system/istio-controlplane    minimal

Output from the istioctl verify-install command:
➜  ~ istioctl verify-install
3 Istio control planes detected, checking --revision "default" only
✔ HorizontalPodAutoscaler: istio-eastwestgateway.istio-system checked successfully
✔ Deployment: istio-eastwestgateway.istio-system checked successfully
✔ PodDisruptionBudget: istio-eastwestgateway.istio-system checked successfully
✔ Role: istio-eastwestgateway-sds.istio-system checked successfully
✔ RoleBinding: istio-eastwestgateway-sds.istio-system checked successfully
✔ Service: istio-eastwestgateway.istio-system checked successfully
✔ ServiceAccount: istio-eastwestgateway-service-account.istio-system checked successfully
Checked 0 custom resource definitions
Checked 1 Istio Deployments
✔ Istio is installed and verified successfully

Version
➜  ~ istioctl version
client version: 1.16.1
control plane version: 1.16.1

➜  ~ kubectl version --short
Client Version: v1.24.2
Kustomize Version: v4.5.4
Server Version: v1.23.14

Additional Information
No response

not stale


Problem

Every time I run comand "python setup.py" or "sudo python setup.py" or "sudo python3 setup.py" or "python3 setup.py" or "python3 setup.py install" or "sudo python3 setup.py install"
it shows the errorlike
File "setup.py", line 42
chmod +x faitagram && chmod +x setup.py
^
SyntaxError: invalid syntax

This script will not run anymore. but for this you have to go into the setup.py file then change
chmod +x faitagram && chmod +x setup.py
to
os.system("chmod +x faitagram && chmod +x setup.py")

This script will not run anymore. but for this you have to go into the setup.py file then change
chmod +x faitagram && chmod +x setup.py
to
os.system("chmod +x faitagram && chmod +x setup.py")

What do you mean the script will not run anymore? I have it running, albeit unreliably.

I guess I meant they aren’t updating it anymore. I could never get it to connect when running it.


generateSelections is passed incorrect name, error: Could not find id for type User.

I was testing my SDL Converted schema and the create inputs are working just fine, but when I use an input on any kind of query it does not work.
After doing some console.logging in prisma-client-lib in Client.js's generateSelections, I found the cause.
I ran the following mutation with a console log in the following line of code:
mutation ($data:UserCreateInput!) {
  createUser(data:$data) {
    id
    username
    password
  }
}

var inputArg = instruction.field.args.find(function (arg) { return arg.name === name; });
Here is the output of args.name and arg:
arg.name: data and name: data
I ran this query:
query ($where: UserWhereInput!) {
  users(where:$where) {
    id
    username
    password
  }
}

Here is the output for my query.
arg.name: where and name: id
arg.name: orderBy and name: id
arg.name: skip and name: id
arg.name: after and name: id
arg.name: before and name: id
arg.name: first and name: id
arg.name: last and name: id

Here are the variables for my query:
{
  "where": {
    "id": "cjt99apz6000g0920yl6xs3x6"
  }
}

It looks as if id is getting passed into the name argument of generateSelections.
I did some more testing after finding this, the only thing that works on a query currently is:
where:{}
because Object.keys(instructions.args).length is 0 and it bypasses most of instructions.reduceRight's logic completely.

I have a project setup for testing that will always result in this error at https://github.com/jblevins1991/nexus-example.
The steps that are requried are as follows:

run docker-compose on the docker-compose.yml in /packages/prisma
run prisma deploy and prisma generate
run npm i in the /packages/api directory
run npm run start in the /packages/api directory
run the following mutationt to create a user so we can query with actual data (which will work as expected)

mutation ($data:UserCreateInput!) {
  createUser(data:$data) {
    id
    username
    password
  }
}

{
  "data": {
    "username": "adsf",
    "password": "laksdjf"
  }
}

6 use the following query and variables (which won't ever work)
query ($where:UserWhereInput!) {
  users(where:$where) {
    id
    username
    password
  }
}

{
  "where": {
    "id": "cjt97hjd4000d0a973ltz5d36"
  }
}

I figured it out. It was an issue on my end.


Polyglot Notebook: [DevExE2E][Regression]The menus "Execute Above Cells" and "Execute Cell and Below" are missing for "Stop Cell Execution" button.

Describe the bug
Using extension Polyglot Notebook in VS Code insider.
The menus "Execute Above Cells" and "Execute Cell and Below" are missing for "Stop Cell Execution" button.
Detailed Repro Build info: VSCodeSetup-arm64-1.79.0-insider + dotnet-interactive-vscode-1.0.4259021.vsix
VSCode Link: https://code.visualstudio.com/insiders/#
Version: 1.79.0-insider (system setup)
Commit: a7133ae9e21e01ed204b02e17e8fc3e91dcadae7
Date: 2023-05-09T09:49:38.022Z
Electron: 22.5.1
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT arm64 10.0.25331
Sandboxed: Yes
dotnet-interactive-vscode-1.0.4259021.vsix
https://dev.azure.com/dnceng/internal/_build/results?buildId=2177104&view=artifacts&pathAsName=false&type=publishedArtifacts
sdk info: dotnet-sdk-7.0.203-win-arm64
Note:

It's a regression issue. It doesn't repro on VSCode 1.77.3 + dotnet-interactive-vscode-1.0.4219021.vsix.
This issue also repro for VSCodeUserSetup-x64-1.78.1 + dotnet-interactive-vscode-1.0.4259021.vsix.
Repro VM: <IP_ADDRESS>

Steps:
1.Open the notebook from https://github.com/dotnet/interactive/blob/main/NotebookTestScript.dib
2. Execute a cell -> move mouse to "Stop Cell Execution" button
Expected Results:
There're 2 menus "Execute Above Cells" and "Execute Cell and Below" shown for "Stop Cell Execution" button.

Actual Results:
The menus "Execute Above Cells" and "Execute Cell and Below" are missing for "Stop Cell Execution" button.

Please complete the following:
Which version of .NET Interactive are you using? (In a notebook, run the #!about magic command. ):

OS

[√ ] Windows 11
[ ] Windows 10
[ ] macOS
[ ] Linux (Please specify distro)
[ ] iOS
[ ] Android

Browser

[ ] Chrome
[ ] Edge
[ ] Firefox
[ ] Safari

Frontend

[ ] Jupyter Notebook
[ ] Jupyter Lab
[ ] nteract
[√ ] Visual Studio Code
[ √] Visual Studio Code Insiders
[ ] Visual Studio
[ ] Other (please specify)

This looks like a change in the VS Code notebook experience and is not specific to Polyglot Notebooks.


Documentation

A stab at getting some documentation for angular-formly ionic templates.

You're basically a super-hero 👏
I'll let @mhartington accept this one though :-)

WOOT! Thanks @jamesvsshark, much appreciated. All merged in via 5fb8e4f4f155f98c5b390471da1b2ecf2568b105


Badges on player card and profile

Being a nemesis or victim should be reflected as an icon on someone's player card
Tournament winners should earn badges for their win (maybe the tournament creator can choose an image or have it based on an svg icon, e.g. a golden thumbs up for one tournament)

Badge/achievement ideas:

Clutch Performer: Win 5 games by 2 points or less
Heart Breaker: Lose 5 games by 2 points or less
Chicken Dinner: Win a tournament
Sacked: Beat Frank (my personal favourite)
On A Roll: Win 3 games in a row
Unstoppable: Win 5 games in a row
Ascended: Win 10 games in a row
Fatality: Win a game without losing a point (to 11 or more)
Helpless: Lose a game without winning a point (to 11 or more)
Superior: Reach 1300 ELO

I'll add more if I think of any.

LOL at Sacked

I'd love to work on this ticket, maybe tonight/tomorrow??

Rancher: Have a 5 game winning streak against someone
Boar Farmer: Have a 10 game winning streak against someone
It Ain't Much But it's Honest Work: Have a 15 game winning streak against someone
Heartless: Beat your current Victim 5 times in a row

Question: can you get the same achievement twice? E.g. if you get it against 2 different players?

With the amount of calculations required, this'll definitely be a backend thing I think (e.g. checking for triggers and recording the achievement in the DB after a game has been entered)

Question: can you get the same achievement twice? E.g. if you get it against 2 different players?

I think it's probably not worth having it more than once, but that's just my opinion. We can gauge opinions tomorrow I suppose.

Maybe the achievement text can record the player who was involved in triggering it
"Boar Farmer
10 win streak against jjg"

Just While I'm Deploying: Play 50 games
Raise The Bat: Play 100 games
Need A Charge Code: Play 200 games

Cellar Dweller: Drop to 1100 ELO or lower
Drunk On ELO: Gain 100 or more ELO in one happy hour
Mistakes Were Made: Lose 100 or more ELO in one happy hour
Shaking Hands: Win a happy hour game to 11 or more by 2 points
Who Said It Was Happy?: Lose a happy hour game to 11 or more by 2 points
A Little Embarrassing: Lose to a player with an ELO of 200+ less than you
Should Have Put Money On It: Beat a player with an ELO of 200+ more than you

These are amazing

Open Season: be the victim for 5 other players
Try As You Might: be the nemesis for 5 other players

Might work on this tonight

First cut is in via https://github.com/jamesgiu/quick-hit/pull/54
Issues:

match id or data (e.g. scores) isn't stored in the badge so you can't see further match details
since it checks your achievements upon each new entered match, if you have a huge backlog of matches from before this update, they'll be attributed to the next match you play, rather than the historical match

We may have some issues here, at least a couple of these achievements are being granted without having actually achieved them.

Yeah something weird is going on - will have a look tonight if I can (the code where they live is pretty nice to expand on though if you felt like taking a squizz too)

Well, the issue for Cellar Dweller is that is it's checking for an ELO of >= 1100, when it should be <= 1100.

I have no idea how that last comment had "fucking off" instead of "ticking off" - I had to do like 3 takes of it to believe it.


Adjust alpha through SPStorkTransitioningDelegate

This PR adds the ability to adjust the alpha of the controller behind the SPStorkController. I needed to do this recently in my app because I have a few smaller panels and the controller was too visually distracting at the default alpha (51%).
I used the same pattern as adjust cornerRadius, contentHeight, etc. through SPStorkTransitioningDelegate.

@iworkinprogress thanks for your work!
But I think what users don't need it.


Chrome crashes when dragging a react-dnd enabled div containing a material-ui table

Description
When I try to drag a react-dnd enabled div containing a material-ui table in Chrome, then my browser crashes. Sometimes I even get booted out of my Linux desktop as a result (at a guess this is some "infinite loop"-like situation causing chrome to runaway and starve the system of resources).
It does not happen in firefox, which makes me thing it is the webkit issue described at https://github.com/gaearon/react-dnd-html5-backend/issues/18#issuecomment-183770505
However, I have tried the suggested workaround and removed in that ticket but I still get the issue. If I delete the  element and leave the table body and footer in place I do not the issue.
I will try and refine this test case tomorrow, with a basic react-dnd/material-ui example.
Versions

Material-UI: 0.16.6
React: 15.4.1
Browser: Version 52.0.2743.116 (64-bit)

Test case created and moved to https://github.com/gaearon/react-dnd-html5-backend/issues/57
Closing this issue here.

Just in case anyone is reading this in future - it is the tooltips in material-ui that are causing the problem. More detail at https://github.com/gaearon/react-dnd-html5-backend/issues/57


cargo-mutants doesn't work on tarpaulin tree

So tarpaulin tests instrument binaries with breakpoints and do coverage which involves intercepting signals going to the process and handling them in code. There's a possibility I'm intercepting the cargo mutants kill signal and then failing the test because it's got an unexpected termination signal :thinking:

Reproducing is pretty simple, it's just cloning tarpaulin and running cargo mutants on it

git clone --depth 1 https://github.com/xd009642/tarpaulin
cd tarpaulin
cargo mutants --in-place

Originally posted by @xd009642 in https://github.com/sourcefrog/cargo-mutants/issues/348#issuecomment-2090621779

@xd009642 I can reproduce this; I haven't looked into why yet. I see a bunch of test failures during the baseline test. Since it isn't timing out, it should not be getting signaled. I guess something else about the environment where cargo-mutants runs it might be causing a problem?
I will look into it some more when I get a chance, but if you want to investigate then a good place to start would be to get the command that it runs from mutants.out/debug.log and run that yourself, and see if it causes the same failure.


Update to accomodate ShipModul Miniplex

The Shipmodul Miniplex now uses R and C to represent a message being received or sent. This update adds C to each PSMDST message so that the Miniplex will accept the message.
Example: $PSMDST,C,XX,YY,ZZ

Would it make sense to add a new autopilot type Raymarine Seatalk 1 AP (MiniPlex) here?


Add TOSRUS lib to a CDN

Hey,
I want to raise his as an issue. Is there an existing hosted TOSRUS library on any content delivery network like Google Hosted Libraries or cdnjs?
Thanks

Not that I'm aware of.

Anyone can request an addition to cdnjs on https://github.com/cdnjs/cdnjs (preferrably in the form of a pull request).


Support for --env-file

Some of the containers in my project require sensitive data (such as 3rd party API tokens) to be passed as environment variables. I understand that I can enumerate these without values in my fig.yml to be picked up from the host environment, but then I still need some way to get them there, meaning one of:

Passing these on every fig invocation (unacceptable due to the repetition), or
Yet another script to wrap fig and load these environment variables from disk.

Docker already provides support for loading a container environment from disk in the --env-file option to docker run. It would be nice if fig exposed this as environment_file as a parallel to the current environment option.
I'd be happy to submit a PR for this, but in order to do so I would need pointing in the right direction by someone who actually knows Python. I figure the implementation would likely be as easy as extending this constant and that I'd probably need a test similar to this one. Am I on the right track so far?

+1

That won't help, @bobcolner. See my last comment.


Create provanpm.json

Please check your JSON, it doesn't appear to be valid. https://jsonlint.com/

FYI the formatting was taken from the assignment guide https://leach-it3049c.github.io/Material/Assignments/1.Online_Portfolio/ Part 2 bullet 3 which is evidently wrong, containing an extra trailing comma.


Add configurable response code meters

Problem:
Currently we only have top level 1xx/2xx/3xx/4xx/5xx meters at the jetty level. We have many use cases where we care about specific response codes like 401/503 and resort to manually instrumenting responses from every resource. This PR allows users to configure what response code meters to include.
Solution:
With the new release of metrics (since 4.2.16), we can specify what response code meters to include. Exposed the same via AbstractServerFactory. Additionally allowed specifying the metricPrefix to include for jetty metrics
Result:
To maintain backward compatibility the default behavior remains the same with this change. Users will have to explicitly specify the DETAILED/ALL responseMeteredLevel if they want more response code meters.

FYI - @joschi
Hoping this approach is acceptable and can be included in the upcoming release 🙂

@joschi  - Thanks for the review and accepting the changes. Should we be concerned about this - https://github.com/dropwizard/metrics/pull/3179 (Fix potential NPE in InstrumentedResourceMethodApplicationListener)

This PR specifically that bumps the metric version to 4.2.16 which contains the bug - https://github.com/dropwizard/dropwizard/pull/6693
Wanted your thoughts on releasing a new version of the metrics library which should include the fix.

@dennyac We'll wait with a release of Dropwizard 2.1.5 until Dropwizard Metrics has been bumped to https://github.com/dropwizard/metrics/releases/tag/v4.2.17.

Sounds good. Thanks. Was just checking.


Double-export traces to Google Cloud and OTLP endpoints

This adds GCP client auth extension config and the OTLP HTTP exporter to send traces to both Google Cloud Trace and OTLP endpoints.
This PR will not currently work until https://github.com/open-telemetry/opentelemetry-collector-releases/pull/577 merges and we update our manifests to that version of the upstream collector-contrib image. I pushed a custom image to our project's registry and added the option for a custom image to cloudbuild-deploy

@dashpole this works now in my local tests (tested with and without otlp endpoint enabled), ptal


Add a share link to private parts which is hash coded

At first link only for viewing, but later when edit ability exists, then could be used for editing.

Added the hash link for sharing.


deps: bump kubebuilder to 2b857cb37698

Description of the change: bump kubebuilder to https://github.com/kubernetes-sigs/kubebuilder/commit/2b857cb376988c7cd3a8afc54677692efeda23f3
Motivation for the change: k8s 1.20
/area dependency
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[x] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

Closing in favor of #4863


Use pip install .[dev] command in tc_build.sh

This fixes the Team City build.

Coverage remained the same at 98.182% when pulling d249a55023e33815ffa4a233023d141b9d205d54 on biniambekele:patch-1 into f2b1788e90613423502947365fb982eec1bda646 on Points:master.


Not able to build the image

Hi,
I'm following your steps, after installing docker on my Linux Mint (v17.3) I get and error when I build:

$ docker build -t vcfminer .
FATA[0000] Post http:///var/run/docker.sock/v1.18/build?cpusetcpus=&cpushares=0&dockerfile=Dockerfile&memory=0&memswap=0&rm=1&t=vcfminer: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?

Thanks.

Can you verify you have docker configured properly by running docker run hello-world

My Bad! sorry!