Model not found exception should not display exception message

Seeing this for a ModelNotFoundException:
{
    "errors": [
        {
            "detail": "No query results for model [CloudCreativity\\DanceCloud\\Models\\DanceEvent].",
            "status": "404",
            "title": "Not Found"
        }
    ],
    "jsonapi": {
        "version": "1.0"
    }
}

Need to remove the detail member as displaying the class name is not correct.

Unfortunately nothing can be done about this, because the Laravel exception handler calls prepareException before passing the exception to the rendering stack:
https://github.com/laravel/framework/blob/5f75dea32bae39f03aed82d6986026fcd4ca7d61/src/Illuminate/Foundation/Exceptions/Handler.php#L317
The prepare method converts a model exception to a HTTP exception with the exception message passed in:
https://github.com/laravel/framework/blob/5f75dea32bae39f03aed82d6986026fcd4ca7d61/src/Illuminate/Foundation/Exceptions/Handler.php#L367-L368


fixFix show mtmv time should wrapped in double quotation mark…

pick: https://github.com/apache/doris/pull/41419

run buildall


How do you Compare to JetBrains MPL, Rascal MPL and Spoofax?

How do you Compare to MPL, Rascal MPL and Spoofax?

Closing. If you still want an answer, reopen and we will try to respond. I am really sorry we didn't do so before, but the project ops structure was in a very bad state and we are only now going through everything and trying to set up a system to make sure all questions are answered.


MJST-35 get wsl distributions as power shell object array

Correct naming would be: 'object table'.

Task linked: MJST-35 Get wsl distributions as PowerShell object array


Transition not applied to absolutely positioned child elements.

Inside a modal-component, I have a <router-view></router-view> which displays various states of the application. If the template of a state contains an absolutely positioned element with a relatively positioned parent, the transition will not apply to its children. i.e. absolutely positioned elements will remain in full view during the transition-period, while relatively positioned elements are faded out.

Thanks for filing the issue. Please follow the Issue Reporting Guidelines and provide a minimal JSFiddle or JSBin containing a set of reproducible steps that can lead to the behavior you described.
Why is this required?

Closing due to inactivity. Please open a new issue with a reference to this one if you can follow up with more information.


[cake] fix cake

Changes proposed in this pull request:

while trying to move vp to subgraph, here to fix at least make cake works

Hi @chef-jojo these changes can affect the voting power? or will it return the same as before?

Hi @chef-jojo these changes can affect the voting power? or will it return the same as before?

Hi @ChaituVR
these changes currently missing pool voting power https://github.com/snapshot-labs/snapshot-strategies/pull/480
We will update it once subgraph sync is completed


Fix discrepancy in tableEntries #275

https://github.com/nodebox/opentype.js/issues/275
Description
An error was being thrown in parseBuffer(...) when calling parseShortList(...) due to a discrepancy in how parseOpenTypeTableEntries(...) & parseWOFFTableEntries(...) returns values. This ended up throwing an error when parsing any WOFF font that includes a cvt table.
Motivation and Context
parseShortList(tableEntry.length / 2) was expecting tableEntry to have a length, but the WOFF parser only returns the values compressedLength and originalLength so tableEntry.length ends up equalling undefined. This ends up throwing an error when new Array(count) is being called in parseShortList(...)
How Has This Been Tested?
I ran through npm test run. I tested again previously failing fonts.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I did npm run test and all tests passed green (including code styling checks).
[ ] I have added tests to cover my changes.
[ ] My change requires a change to the documentation.
[ ] I have updated the README accordingly.
[ ] I have read the CONTRIBUTING document.

Can we please merge this PR and publish the result to NPM? I have many fonts that load fine using version 0.6.9 but won't using 0.7.1 because of this bug.

+1, I'm also working on a project that could benefit from this fix (for now my workaround is to use default fonts only)

Thanks for the PR. I just merged it and release 0.7.2.


Media services v3

I am trying to use Media services v3 to get keys for a Content-Key Policy I created to encrypt content on premise. I can't find any documentation for it. It's there for v2 APIs but not for v3.
Maximum I could find was how to get the Secret Token Signing key, methods and classes exist, but where do I get the Key Ids to get the actual key to encrypt my video on premise and the url for player to fetch the corresponding license

@ashutoshsingh0223 -
Thank you for your question.
Can you please share with us the URL of the document that you are having issues with?
Please note that we scope issues on this repo to feedback related to the docs. If you have a product question, please post it on Microsoft QnA or Stack Overflow. Thank you for your understanding.

@ashutoshsingh0223 - Can you please share with us the URL of the document that you are having issues with?
Please note that we scope issues on this repo to feedback related to the docs. If you have a product question, please post it on Microsoft QnA or Stack Overflow. Thank you for your understanding.

My question was more product related. Closing this issue now.

@ashutoshsingh0223 - Thank your comments.  If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Support PostgreSQL schemas

Feature Request
What feature are you missing?
It would be nice for the PostgreSQL connector to support schemas, so we can create a GraphQL API from an existing database with multiple schemas. This is the only missing feature for me to move forward with Prisma. If such a feature already exists, please excuse me for the mistake but I can't find any docs about it.
How could this feature look like in detail? Tradeoffs?
This could look like this:
type User @pgTable(name: "mySchema.users") {
  id: ID! @unique
  email: String! @unique
  name: String!
}

Or like this:
type User @pgSchema(name: "mySchema") @pgTable(name: "users") {
  id: ID! @unique
  email: String! @unique
  name: String!
}

Or something like this:
type User @pgTable(schema: "mySchema", name: "users") {
  id: ID! @unique
  email: String! @unique
  name: String!
}

Maybe to support this feature we'd also need some requirements in the environment? Since I don't know the internals of Prisma I don't know if it's needed or not.
version: "3.1"

services:
  #...
  prisma:
    image: "prismagraphql/prisma:1.8"
    restart: "unless-stopped"
    environment:
      PRISMA_CONFIG: |
        port: 4466
        databases:
          default:
            connector: "postgres"
            host: "database"
            port: 5432
            user: "user"
            password: "password"
            migrations: false
            database: "mydatabase"
            schemas:
              - "mySchema"
    ports:
      - "4466:4466"

volumes:
  postgres:

Prevision ?

+1 .
For Shared Database SAAS applications this is a must have.Also resolving Schemas at runtime is critical. Ideally CRUD should point to the Database-> Schema -> Table .


Upgrade to text/template in Go 1.6

The text/template package now supports whitespace trimming.
https://golang.org/doc/go1.6#template

This will require a bump of the major version, e.g. for inclusion in v3.

v3 seems reasonable. Would you mind sending a PR again against the v3 branch, and remove the old Go versions from the Travis config?


Lag before CLI prompt comes back

Observed when running CLI against local single-node Presto:
presto:default> set session hive.collect_column_statistics_on_write = false;
SET SESSION                                                                        // it takes 1s to show that
presto:default>                                                                    // it takes another 2s to show that

Should be resolved by #2022 (at least for the second gap noted here). I'm not sure about the first gap, the first execution is about 1s guessing just due to class loading/first initialization of things. Subsequent statements come back quickly but could maybe be snappier? I pulled up an old version from a few months ago and seemed about the same.

@ryanrupp thank you for fixing the regression!
it's definitely responsive now. I am not pasting long SET SESSION sequences, so the remaining delay doesn't matter to me.
Thanks!


Task - Filter Nomenclature - with/without identifiers

Adriano wants to filter for taxa with or without identifiers.

@proceps -- Thanks. I think such a filter would be useful. We are employing various kinds of identifiers in our project.  Which taxa have LSID...
And, thinking beyond, not only for taxa. For example, which sources have DOI or LSID.

@adrik29 added local and global identifiers with/without facets to Filter nomenclature.
Filter source already have them

@jlpereira Fantastic! Thanks a lot -- I'll be alert.


question about TCP socket connect and EINPROGRESS

AFAIK,  kernel with IORING_FEAT_FAST_POLL should not return EINPROGRESS error for IORING_OP_CONNECT calls.
And it never did until now, but recently we encounter cases where we receive EINPROGRESS (still not sure how to reproduce).
I've looked up for related issues and found this  https://github.com/axboe/liburing/issues/671 .
Could it change the iouring behavior and return EINPROGRESS in some cases for IORING_OP_CONNECT?

Fixed in newer and stable kernels.

A few more details -
We're sending a IORING_OP_CONNECT on a non blocking socket and try to set a timeout with a previous IORING_OP_LINK_TIMEOUT request.
Then the connect request completes almost immediately with EINPROGRESS, but it only happens sometimes and under specific conditions that we're not sure how to reproduce.
Is this expected behavior? From looking at tests/connect.cc it looks like it might be, but we're not sure why we're seeing this only now and why.

I think, the connect test has been written before iouring has implemented
the fast_poll feature that handles io polling on behalf of a user app. So,
this code path should only be triggered for older kernels before 5.7
On Tue, Apr 11, 2023, 12:16 Roy Jacobson @.***> wrote:

A few more details -
We're sending a IORING_OP_CONNECT on a non blocking socket and try to set
a timeout with a previous IORING_OP_LINK_TIMEOUT request.
Then the connect request completes almost immediately with EINPROGRESS,
but it only happens sometimes and under specific conditions that we're not
sure how to reproduce.
Is this expected behavior? From looking at tests/connect.cc
https://github.com/axboe/liburing/blob/4fed79510a189cc7997f6d04855ebf7fb66cc323/test/connect.c#L159
it looks like it might be, but we're not sure why we're seeing this only
now and why.
—
Reply to this email directly, view it on GitHub
https://github.com/axboe/liburing/issues/841#issuecomment-1502970645,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4BFCC5ZITINJMEZ6ZVVZLXAUOP3ANCNFSM6AAAAAAWZWUYEE
.
You are receiving this because you authored the thread.Message ID:
@.***>


CPU boost by ignoring node_modules in dev server config

I managed getting a huge cpu boost by adding the ignored prop in the dev server config,
and much faster compile times for css. (working with Vagrant and polling is 1)
watchOptions: {
  poll: !!parseInt(settings.devServerConfig.poll()),
  ignored: /node_modules/
},

see my pull request here #4

Oh wow, I totally should have had that in, thank you!

Hi, thanks for the great code. Have u experienced this problem with absolute imports (or is it mostly a create-react-app Windows-compatibility thing)?
https://github.com/facebook/create-react-app/blob/30ee52cf3b2cbb6ac70999c02b1196bcaba8d4ca/packages/react-scripts/config/webpackDevServer.config.js#L77


Sheetal chouhan

🛠 Fixes Issue
Close #172

👨💻 Changes proposed

Added Django Course in CodingEasy which includes different sections.
These different sections are Basic, Environment, Models, Projects, Views, Templates, Authentication, URLs with their respective Html templates.
✔ Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

@SheetalChouhan12
there are conflicts in files. Please resolve this issue.

Hey, I tried to resolve the conflict files but it's showing already up to date with the Master branch. Don't know what to do next. Can someone tell me?

Are you using the correct upstream? Did you try pulling the latest code

Hey, I tried to resolve the conflict files but it's showing already up to date with the Master branch. Don't know what to do next. Can someone tell me?

Are you using the correct upstream? Did you try pulling the latest code

I did when I first setup code in local system back then It was showing up to date but now I pull latest code . It has changes , I will do it and then make a PR again .

@SheetalChouhan12 resolve merge conflicts or make a new PR

@SheetalChouhan12 resolve merge conflicts or make a new PR

Okay . Will make new PR


Trading page header: Disputing/Reporting

This design has changed. This task needs to move to the condensed trading page effort.
https://www.figma.com/file/aAzKHh4cA6OT2t7WFv2BQ7fB/Reporting-and-Disputing?node-id=796%3A2099
This section of trading page combines existing components, the button takes the user to the dispute/report form. The button is unique in that no outcome is selected by default.

this effort will be done when the trading page condense occurs. changing this to not block reporting form

this is done, closing


Dropdown search does not work

Steps To Reproduce
create a dropdown with some options from a sql query. observe that search does not work. this is with latest version (34)
Environment

Node version (node -v): v20.12.2
npm version (npm -v): 10.5.2
OS: archlinux
Browser: firefox (but unrelated)
Database: csv (but unrelated)

Expected Behavior
search should filter the options
Actual Behaviour
it does either nothing or removes all options
Workarounds
none found so far, just straight up broken

This is likely fixed by #1980; I haven't been able to get a repro, if there is one available would love to dig into it

Dropdown search "works" at 34.0.1, but there is definitely room for improvement.

Search has no effect on manually added DropdownOptions
Keeping selected items at the top of the list while searching is counterintuitive, especially in a multi-select where you might have many items sitting at the top
The actual search function seems far too permissive, I think we need to more aggressively eliminate options. For example, the search Blargghhh should not yield a list of options with Larry Gaish at the top, it should yield no options.

This was resolved by #2096


Add ability to construct service via environment variables

This adds the ability to construction the ionq.Service from environment variables.  By setting IONQ_REMOTE_HOST and IONQ_API_KEY one can avoid storing the API key in code (and potentially checking it into a public version control system).

Part of #3479


Could this plugin support the webdav and S3 service ?

Could this plugin support the webdav and S3 service like tencent cloud & ali cloud ?
tencent cloud :
cloud.tencent.com
ali cloud:
www.aliyun.com

Thank you for asking me! But I'm afraid I should give you this reply.
This plugin only supports the database that has compatibility with CouchDB.


long decimal replacements of fractions

> echo 'x=1/30' | shrinko8 - - --format lua --minify --focus-chars
a=.03333

This is 2 chars longer!
(this also happens without --focus-chars)

Fixed (under --focus-chars only, of course) - LMK if you see any issues.


Ensure goroutines dump is not truncated

Currently the goroutines dump printed in the logs when a SIGUSR1 is sent to the docker process have a great chance of being truncated.
Calling runtime.Stack requires the buffer to be big enough to fit the goroutines dump. If it's not big enough the dump will be truncated and the value returned will be the same size as the buffer.
This PR change the code responsible for dumping the goroutines to handle this situation and try again with a bigger buffer. Each time the dump doesn't fit in the buffer its size is doubled.

LGTM

LGTM


[Feature request] Different exit methods use different exit codes.

I'm making an nvim plugin for yazi.
plugin:
yazi.nvim
However, what puzzles me is that both the normal exit of yazi and the exit after selecting a file using the --chooser-file parameter have a return code of 0, which makes it impossible for me to distinguish whether yazi exited with or without selecting a file.
Can you help return different exit codes for different exit methods?

i find another way

I think you only need to check the /tmp/test.txt file (in your example).
BTW, this plugin looks pretty cool.


Example not working with Ubuntu 22.04 LTS

Hi there,
I've problems with running the example code in the file: https://github.com/karask/python-bitcoin-utils/blob/b1bc4ebdade5521f3d60b7acea1b99ac94d18635/examples/keys_addresses.py
     hashripemd160 = hashlib.new('ripemd160')
  File "/usr/lib/python3.10/hashlib.py", line 166, in __hash_new
    return __get_builtin_constructor(name)(data)
  File "/usr/lib/python3.10/hashlib.py", line 123, in __get_builtin_constructor
    raise ValueError('unsupported hash type ' + name)
ValueError: unsupported hash type ripemd160

What should I do?
I'm using Ubuntu 22.04 LTS

Hi! I was very recently made aware of this (new version of the library).
A workaround can be found here:
https://stackoverflow.com/questions/72409563/unsupported-hash-type-ripemd160-with-hashlib-in-python
However, I will try find some time to fix this properly asap.

Fixed in v0.5.8 in accordance to https://github.com/bitcoin/bitcoin/issues/23710


Added labels and reference to the counters file

Added counter labels for all counters, and added a reference to the EventSource file where the counters are maintained.
The table ends up being rather "ugly" with the long counter names, so I force a line break in the counter name cell. Not sure this is the right approach for controlling the style, let me know if you want if changed.
This should solve #3234

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: esbenbach sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Any chance this is going to get approved? Otherwise I can just abandon it.

@esbenbach sorry this didn't receive any attention - it came just as the 6.0 release was being prepared. I'll review this in the coming days.

/azp run


netserver: don't change permissions on /dev/null

the (now default) suppress_debug=1 changes permissions on /dev/null
to 0644. Don't do this.

the (now default) suppress_debug=1 changes permissions on /dev/null
to 0644. Don't do this.

Randomly ended up here but this is real reason to worry,... so many things would be broken due to this.

This relates to #26


Question: Build Items are not vanilla compatible?

Are the build Items vanilla compatible? I am asking because I would like to have an item non-colliding (so you fall through them) but it should work on vanilla clients - it is not possible right? and I should go back to using rugs?
Thanks for clarifying,
Stefan

Thanks for clarifying that.


enable vdbench scale

This PR enables vdbench scale for pod/kata/vm
The scale is 2, meaning running 2 pod/kata/vm per worker node (3 workers), total 6 pod/kata/vm
Update botocore and boto3 for latest stable

Clarified in discussion that the change is in fact correct; vdbench_pod_scale is processed by the CI script and vdbench_pod is what's actually passed to benchmark_runner.

/lgtm


Add PARAFACM code

Ok, good. Sounds like the line search may end up being helpful to include. Merging.


Allow loading configs from files

In addition to loading configs from the environment it can be handy to load configs from files as well, especially with something like Kubernetes making it easy to map a config to a file.  I was looking at the source last night and I had a few ideas on how to implement it.  I saw there are some changes in the config branch that I haven't had a chance to look at yet so this might be wrong given those changes.
I would be able to implement this feature if you're ok with my proposal in general:
A new bootstrap option would be created called something like WithConfigLoader or something like that which would allow you to pass in a Config to use while bootstrapping.  In addition to this, three new Config types would be created: DefaultConfig which would just load the default values into the config struct, FileConfig which would handle loading configs from files and (I don't know a good name for this atm) PrioritizedConfig that would take an array of Configs and would attempt to load configs in the order they're passed in to the constructor, giving lowest priority to the first one on down.  This would allow something like first loading defaults, then loading FileConfig, finally loading EnvConfig so files override defaults and env overrides files.
FileConfig would work by having a few options that can be passed in to the constructor.  The first being just a ConfigFilePath(path string) that would load the config from a specific path and not try anything else fancy.  Next would be a ConfigFileName(name string) that would take just the base of a config name, such as config. Last would be a ConfigFileDirectory(path string) that would take a "search directory" where FileConfig would look for config files. ConfigFileDirectory could be provided multiple times to include multiple search paths and would search in the order the options are provided.
FileConfig would initially support loading configs from json, yaml and toml files. It would use the ConfigFileName as the root of the filename, ConfigFileDirectory as the directory to search in and one of the standard file extensions for the various supported file types to construct a path. For example if ConfigFileName("config") and ConfigFileDirectory("/etc/") were passed in, FileConfig would try to find /etc/config.json, /etc/config.yaml, /etc/config.yml and so on.  If it finds a file match it will load that file and prepare to populate the config struct with the values.
As far as loading FileConfig values into a config struct, I'm planning on using the struct tag file to contain a dot-delimited path to the value in a config file.  For example, if the file tag value is "foo.bar", the value would attempt to be loaded from the bar property of the foo object and on down the line.  If a provided path doesn't exist in the config it will be ignored but if the path does exist and the types don't match it will be considered an error.
I think I covered all my thoughts on this, let me know what you think!

Would you want a Sourcer for each file type or just a FileSourcer that can determine what it is based on the file extension (with the option of hinting at what it is in a config)?

Ok, I'll take a crack at it and we can talk about it in the PR

Ok, added a more complete draft in the config-sources branch. Now we have:

load from map[string]interface{}
load from JSON file
load from YAML file
load from TOML file
load from multiple sourcers (in registered order)
read from a configmap directory

Right now I plan to keep the env tag as-is so the only behavioral change to the entire package is the addition of a source. This may require that you tag things like env:"foo.bar.baz" for configmap mounts, which will load the content from the mounted "foo.bar.baz" file and try to use it as a raw string or parse it as a JSON value.
I'm against the idea of adding additional struct tags that will behave differently across sources. Right now, env, default, required, and mask work the same regardless of sources. I think this is the correct design. Maybe the env tag name could be changed as we're not strictly pulling from the environment anymore, but I don't think that's a huge issue (we could also make that particular tag configurable at boot).
Could you actually try out the configmap loader to see if this will work for your purposes tomorrow? I'm not 100% sure what the config map volume looks like and don't have a k8s cluster set up at home. If there's something that doesn't quite work could you add some more tests?

That makes more sense. If you have a MWE of a app manifest/config map that mounts in a volume could you show me what the mounted volume actually looks like? I've read conflicting things.
I'd prefer the implementation to be tweaked a bit so that files are handled transparently:
type Config struct {
SomeString string env:"STRING" context:"some" default:"my_default"
SomeInt int env:"INT" file:"context" default:"1234"
}
Then this will work for the file with context you describe as well as loading directly from the environment with export SOME='{"string": "foo","int":4321}'. This will also keep backwards compatibility with existing applications.
What do you think about that? Then all the changes (besides replacing the configmap sourcer with a directory sourcer) are in the config struct and apply to all sourcers equally.

Let me try the context thing real quick.

Ok what of you think of this right now? See test and [config object](https://github.com/efritz/nacelle/blob/c19877ba5804a5e63254ff5e03bdfb5d1a8c71c6/config/mock_objects_test.go#L15]
Let me know if this is a good direction for you.

I think I see what you're going for but I'm wondering why you don't want to have a specific tag per loader? If you have a tag that's specific to a type of loader it allows more flexibility in how you name/access something.  I think that trying to make something that's trying to reuse concepts for all cases is either going to be confusing to use or won't allow projects to implement things the way they want. I wouldn't have a problem with ENV being the only way things can be loaded by default and if you want things to be loaded from a file you have to set some preferred values in the bootstrap.
As far as the app manifest/config map it would be something like this:
For a yaml config:
apiVersion: v1
kind: ConfigMap
metadata:
  name: my-app-config
  namespace: my-app
data:
  config.yml: |
    foo:
      bar: 1
      baz: "qux"
    blah: false

For the same thing as a json config:
apiVersion: v1
kind: ConfigMap
metadata:
  name: my-app-config
  namespace: my-app
data:
  config.yml: |
    {
        "foo": {
            "bar": 1,
            "baz": "qux"
        },
        "blah": false
    }

Then the pod manifest could be something like:
apiVersion: v1
kind: Pod
metadata:
  name: my-app-pod
  namespace: my-app
spec:
  containers:
    - name: app
      image: my-app:latest
      volumeMounts:
        - mountPath: /app/config
          name: config-volume
  volumes:
    - name: config-volume
      configMap:
        name: my-app-config

In the case of the yaml file example this would create the file /app/config/config.yml with the contents:
foo:
  bar: 1
  baz: "qux"
blah: false

With the json file example it would be similar except with the json file contents in the file /app/config/config.json.
Was that what you were wondering about wrt configmaps and app manifests?

I just thought of more stuff...
In the above example I think the config struct would look like:
type Config struct {
    Bar int `env:"bar" context:"foo"`
    Baz string `env:"baz" context:foo"`
    Blah string `env:"blah"`
}

I would prefer something like:
type Config struct {
    Bar int `env:"foo_bar" file:"foo.bar"`
    Baz string `env:"foo_baz" file:"foo.bar"`
    Blah string `env:"blah" file:"blah"`
}

I feel like it's more explicit this way and it's easier for someone who's unfamiliar with the code to grok where the values come from in different cases.

I’m very hesitant to introduce source-specific flags because when you
aren’t locked in to reading from a specific source outside of your main
function. I think what is in that branch now is flexible enough for what
you want (as I understand it) and works pretty well with all sources so
far. If you add tags that work only in specific cases you changing not only
the source but also the struct population behavior in non obvious ways.
I could otherwise be convinced with a PR to that branch. Maybe I’m not
seeing some benefit I might see with a sample implementation or full use
case.
On Sun, Sep 30, 2018 at 7:42 PM Erik Davidson<EMAIL_ADDRESS>wrote:

I think I see what you're going for but I'm wondering why you don't want
to have a specific tag per loader? If you have a tag that's specific to a
type of loader it allows more flexibility in how you name/access something.
I think that trying to make something that's trying to reuse concepts for
all cases is either going to be confusing to use or won't allow projects to
implement things the way they want. I wouldn't have a problem with ENV
being the only way things can be loaded by default and if you want things
to be loaded from a file you have to set some preferred values in the
bootstrap.
As far as the app manifest/config map it would be something like this:
For a yaml config:
apiVersion: v1kind: ConfigMapmetadata:
name: my-app-config
namespace: my-appdata:
config.yml: |    foo:      bar: 1      baz: "qux"    blah: false
For the same thing as a json config:
apiVersion: v1kind: ConfigMapmetadata:
name: my-app-config
namespace: my-appdata:
config.yml: |    {        "foo": {            "bar": 1,            "baz": "qux"        },        "blah": false    }
Then the pod manifest could be something like:
apiVersion: v1kind: Podmetadata:
name: my-app-pod
namespace: my-appspec:
containers:
- name: app
image: my-app:latest
volumeMounts:
- mountPath: /app/config
name: config-volume
volumes:
- name: config-volume
configMap:
name: my-app-config
In the case of the yaml file example this would create the file
/app/config/config.yml with the contents:
foo:
bar: 1
baz: "qux"blah: false
With the json file example it would be similar except with the json file
contents in the file /app/config/config.json.
Was that what you were wondering about wrt configmaps and app manifests?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/efritz/nacelle/issues/28#issuecomment-425764681, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGSr56z78NiGuyS3ONTqQKmsXiqUqr3ks5ugWUQgaJpZM4W-s1Q
.

--

Eric Fritz

From your last comment I see a bit more clearly now. This assumes that: (1) loaders know what tags they want to read, (2) they only read a single "source" tag (env or file), and (3) they don't read both tags in a strange way, then we can do the following:

revert the context stuff
find a way to have the sourcer communicate what tags should be read for each source (this is trickier for multi-sourcer which may need to ask for multiple tags)
take the first valid value that's found and try to coerce it into the correct type for the struct

Does that sound ok? If so, could you make a PR to the branch if you have time?

I think those 3 assumptions you listed are some that I was operating under. I haven't had a chance to look through the loader/sourcer code yet because I've been busier this weekend than I anticipated but if you don't mind I would like to take a crack at what I was thinking in that PR.  If it's not something that works we can just throw it out, np.  I do think it might be the best way to explain what I'm thinking though and help me understand how the code works now.

Awesome. Fork from the branch I started because there's some additional refactoring there.

It early-returns on the first one found (not that it will necessarily coerce to the correct type, only that there exists the valid path in that source). Are you suggesting that these values merge multiple sources, or that you just take the last one (so that the sourcer list is low->high priority)?

I was thinking it would take the last one.  This would allow you to have a multi sourcer that would do something like: file (one or more), env. This would allow files to override each other and then have the environment override that.

Right now there's only a file sourcer that takes a direct path, not a directory or anything. There's also no sourcer that silently exits on a missing file, so you must explicitly know the file path (and that it exists).
Both of these things can change. Could you lay out your ideas or how you would like to deal with files (a directory sourcer, or possible file list/glob paths)?

I wrote out the previous part without remembering this part.  So having multiple files wouldn't work in the example i put above.  I'll put together some thoughts on a DirectorySourcer tonight. My keyboard is being a turd and I can't type long thoughts on it due to missed keystrokes, and duplicated keystrokes everywhere. =/

This would allow you to have a multi sourcer that would do something like: file (one or more), env.

You can do that just by putting env first and listing your files in priority order.
Will wait for your thoughts on DirectorySourcer.

For the MultiSourcer I just thought it felt better for the order to be lowest to highest priority but I'm not super stuck on either option.
For the DirectorySourcer, I guess what are your ideas for a DirectorySourcer? I think I see it as a way to load a single file from a directory (without recursion) with one or more base names in order of priority which would then have standard file extensions added to it to find a file. Maybe something like this:
sourcer := NewDirectorySourcer(
    "/etc/myapp", // Directory to search in
    []string{"config"}, // Base filenames
)

This would create a sourcer that would try to find the files:

/etc/myapp/config.json
/etc/myapp/config.yml
/etc/myapp/config.yaml
/etc/myapp/config.toml

Once it found one of them it would load the file with the associated file type sourcer and would be treated as a FileSourcer after that.
This is similar to how viper and the nodejs "config" packages work with slightly less features.  In the case of nodejs the files are named based on the environment and/or host and I'm not sure it should go that far (take a look at this for more info on how that works).
I'm pretty open on the DirectorySourcer and I'm actually OK with how the file sourcers work atm but I'm trying to think of ways to make the config accessible and familiar (and less friction) to people who are coming from other options.

Ok I've updated a few things. Priority order for MultiSourcer has been reversed. There is now only one FileSourcer which takes a parser function as an optional second argument. If the parser is not supplied one will be chosen based on extension. The file MUST exist for the file parser.
I'm not sold on the directory sourcer, though. At least not that API. What's the use case of having such a restrictive input (no recursive search) that only cycles through extensions? I think possible just to have something like a OptionalFileSourcer that just no-ops when it can't open the file.
Thoughts on that?

I like that idea!

Done! Anything else you want?

I think that covers everything I was thinking about, I'd have to implement something with it to see if there's anything else. Thanks for working on that so quickly. :)


[Pagination] Add new component

We need the new Pagination component like this https://react.semantic-ui.com/addons/pagination/

Related to https://github.com/szmslab/material-ui-flat-pagination/issues/12#issuecomment-527202335

How about something like this? https://github.com/vim-labs/materialui-pagination-component

@iRyanBell Thanks for sharing. We will need to provide a built-in solution in Material-UI in the near future. I hope we can deliver it by Q1 2020. Would you be interested in this effort? I can guide you into this. I would need to run a benchmark in order to better understand how we can move forward. It would likely require a new effort, taking the good parts from everybody, your project included.

@oliviertassinari Count me in.

@iRyanBell Awesome, I will try to quick that off tomorrow.

in case you are interested. this lib is used by react-bootsrap

Benchmark
I have used the following sources to benchmark:

https://a11y-style-guide.com/style-guide/section-navigation.html#kssref-navigation-pagination
https://www.a11ymatters.com/pattern/pagination/
https://getbootstrap.com/docs/4.3/components/pagination/#disabled-and-active-states
https://ant.design/components/pagination/#header
https://elastic.github.io/eui/#/navigation/pagination
https://garden.zendesk.com/react-components/pagination/
https://www.carbondesignsystem.com/components/pagination/code
https://element.eleme.io/#/en-US/component/pagination#pagination
https://react-bootstrap.netlify.com/components/pagination/#pagination
https://react.semantic-ui.com/addons/pagination/
https://quasar.dev/vue-components/pagination
https://baseweb.design/components/pagination/
https://kiwicom.github.io/orbit-components/?path=/story/pagination--default
https://atlaskit.atlassian.com/packages/core/pagination#/
https://vuetifyjs.com/en/components/paginations#paginations
https://mdbootstrap.com/docs/jquery/components/pagination/
https://bulma.io/documentation/components/pagination/
https://rsuitejs.com/en/components/pagination
https://opensource.adobe.com/spectrum-css/components/pagination-listing/#
https://demos.creative-tim.com/bs3/material-dashboard-pro/examples/tables/datatables.net.html
https://dribbble.com/tags/pagination
https://github.com/vim-labs/materialui-pagination-component
https://github.com/szmslab/material-ui-flat-pagination

Proposal
I would recommend the following:

I would propose this API

Pagination.propTypes = {
  /**
   * If `true`, all links  will be disabled.
   */
  disabled: PropTypes.bool,
  /**
   * The size.
   *
   * default 'medium'
   */
  size: PropTypes.oneOf(['small', 'medium']),
  /**
   * The active color.
   */
  color: PropTypes.oneOf(['primary', 'secondary']),
  /**
   * Callback fired when the page is changed.
   *
   * @param {object} event The event source of the callback.
   * @param {number} page The page selected.
   */
  onChange: PropTypes.func,
  /**
   * The zero-based index of the current page.
   */
  page: PropTypes.number.isRequired,
  /**
   * The total number of pages.
   */
  count: PropTypes.number.isRequired,
  /**
   * Number of always visible pages at the beginning and end.
   */
  boundaryRange: PropTypes.number,
  /**
   * Number of always visible pages before and after the current one.
   */
  siblingRange: PropTypes.number,
  /**
   * If `true`, show the first page item.
   */
  displayFirstItem: PropTypes.bool,
  /**
   * Render the item.
   *
   * @param {object} params
   * @returns {ReactNode}
   */
  renderItem: PropTypes.func,
  /**
   * Text label for the first page item.
   *
   * default First page
   */
  firstItemText: PropTypes.string,
  /**
   * Text label for the next page item.
   *
   * default Next page
   */
  nextItemText: PropTypes.string,
  /**
   * Text label for the next page item.
   *
   * default Last page
   */
  lastItemText: PropTypes.string,
  /**
   * Text label for the next page item.
   *
   * default Previous page
   */
  previousItemText: PropTypes.string,
  /**
   * If `true`, hide the next page item.
   */
  hideNextItem: PropTypes.bool,
  /**
   * If `true`, hide the previous page item.
   */
  hidePreviousItem: PropTypes.bool,
  /**
   * If `true`, show the last page item.
   */
  displayLastItem: PropTypes.bool,
};

We translate the xText props.
Add integration demo with react-router.
Not to use the Paper component.
Render links, not buttons.
We might want to expose a PaginationItem so people can compose it in the renderItem prop.
What about we only expose one style of the pagination?

References

React Router example: https://atlaskit.atlassian.com/packages/core/pagination#/)
boundaryRange and siblingRange behavior example: https://react.semantic-ui.com/addons/pagination/#types-compact
Variants ideas, I prefer the 1.

https://atlaskit.atlassian.com/packages/core/pagination#/about

https://github.com/vim-labs/materialui-pagination-component

https://dribbble.com/shots/6726286-DailyUI085-Pagination

I'm surprised to see so few other examples using a select box for page selection. I found this to be very intuitive and fastest way to move between specific pages. Personally, disabled buttons with "..." feels a bit unnecessary, but it is a very common design trend.

I share the same observation. I have seen one select based pagination (baseui). An input field seems more frequent. For instance https://www.shutterstock.com/fr/search/tree.

On Bing.com, they only use the ellipsis on the left edge.

Actually, I think that bondaryPageRange=0 should lead to no ellipses.

I had another thought, what if we expose the Pagination DOM structure. Something like this (1)?
import React from 'react';
import { Link } from '@material-ui/core';
import { Link as RouterLink } from 'react-router-dom';
import { usePagination, Pagination, PaginationItem } from '@material-ui/lab';

// The use of React.forwardRef will no longer be required for react-router-dom v6.
// See https://github.com/ReactTraining/react-router/issues/6056
const Link1 = React.forwardRef<HTMLAnchorElement, RouterLinkProps>((props, ref) => (
  <RouterLink innerRef={ref} {...props} />
));

function MyPagination() {
  const items = usePagination({
    page: 2,
    count: 10,
  });

  return (
    <Pagination>
      {items.map(item =>
        <PaginationItem
          to={`/cars${item.page === 1 ? '' : `?page=${item.page}`}`}
          component={Link1}
          {...item}
        />
      )}
    </Pagination>
  )
}

Instead of (2)
import React from 'react';
import { Link } from '@material-ui/core';
import { Link as RouterLink } from 'react-router-dom';
import { Pagination, PaginationItem } from '@material-ui/lab';

// The use of React.forwardRef will no longer be required for react-router-dom v6.
// See https://github.com/ReactTraining/react-router/issues/6056
const Link1 = React.forwardRef<HTMLAnchorElement, RouterLinkProps>((props, ref) => (
  <RouterLink innerRef={ref} {...props} />
));

function MyPagination() {
  return (
    <Pagination
      page={2}
      count={10}
      renderItem={(item => (
        <PaginationItem
          to={`/cars${item.page === 1 ? '' : `?page=${item.page}`}`}
          component={Link1}
          {...item}
        />
      )}
    />
  )
}

But maybe we can support both.


--no-playlist cul-de-sac

how do you switch playlist on when --no-playlist is in config file (default)? there is no --playlist as far as i can see.

Thank you for the report. Since youtube-dl 2015.02.28, you can pass in --yes-playlist. See our FAQ if you have trouble updating.

thanks, feel free to close this.

Already is ;)


Add cronit

Add a link to Cronit, a new online cronjob scheduling system

Hi @aclarembeau
Thanks for your contribution ;)
We have some problems with Public APIs, so we won't be able to review/add this improvement right now.
Read this issue for more information, please: https://github.com/public-apis/public-apis/issues/3104


Make responsive the toolbar in Write activity

In Sugarizer it's important that whatever could be the screen size the Stop button is always visible to be sure the user will be able to quit the activity. So responsive activities use media queries in CSS file to hide other toolbar buttons depending of the window size. See for example Paint activity behavior:

The Write activity toolbar is not responsive as you could see below:

Working on it!

It looks like this was already implemented.

No it's not, the Stop button disappears like in the video capture above

It only does in my instance when the bar is showing only the Write save icon on the far left and the share icon, at least in my dev instance.
Should it continue to collapse smaller than 274px across, getting rid of the save and share icons?

The problem is not related to the activity icon or to the share icon, the problem is that the Stop button should be visible. As you could see in the screen capture below, the Stop icon is not visible

We have different versions of Sugarizer running then, because this is what I see...

Interesting the issue comes probably from https://github.com/llaske/sugarizer/pull/497 or https://github.com/llaske/sugarizer/pull/505 because it appears in the dev branch.
By the way, it's better if you've got the latest version of the dev branch to be able to reproduce an issue.

Ahhh, sorry, I didn't realize I had become out of date. Thank you!

Fixed in https://github.com/llaske/sugarizer/pull/528


Signing a multisignature transaction

I'm trying to get a given transaction signed. It's a 3 of 4 multisignature transaction, and has 1 sign on it. I want to enter its hex code and a private key and get the returned transaction, but I get the "Signing with the wrong private key" error. I'm sure that they match. What am I doing wrong?
Here's the code:
$myTransaction = TransactionFactory::fromHex($transaction);
$myPrivateKey = PrivateKeyFactory::fromHex($privateKey, $compressed = TRUE);
$txOut = $myTransaction->getOutput(0);
$ec = \BitWasp\Bitcoin\Bitcoin::getEcAdapter();
$signed = (new Signer($myTransaction, $ec))
->sign(0, $myPrivateKey, $txOut)
->get();
Thanks.

By the way this is the transaction, if it's relevant:
https://coinb.in/?verify=01000000014dbd81ef72c3b0177c790eabcb370ff1020f46237d56462c3d51839c11560a8800000000d60047304402207eca346354c4289c4c782fe0507e36e274ef3ab0dd6246df2433f33410ff5b7002203cabd0b54d045cbe20f1a5ea79fe8a8a34e3dcbc24e0aacd707a83f18ad59af2014c8b53210367ba14ca6d26e60b1f1862b6679a2ae86178773661c9f48410b3d6bd97324d64210228b5d0e6a362bee65f6387df2b82dd76003b90fd404e893eea060886a396289721025e915f753f4aa4d137c0e727fe07e613c023e1103fba98ce32e472ecdf06e1a22102cd1c9ae0fcbd9dbe17dec21c2bc56d1486d8b3ca71dbd2be5a8e2bde88effba354aeffffffff0150c30000000000001976a91493cd53fba0f931efd197309ab57fe552d822d06188ac00000000#verify

In this case you need to provide the txOut that you're spending (multsig output), not something from the transaction your creating (a P2PKH output).
You can generate it yourself from the value and the redeemScript:
$scriptChunks = $tx->getInput(0)->getScript()->getScriptParser()->decode();
$redeemScript = new Script($chunks[count($chunks) - 1]->getData());
$txOut = new TransactionOutput($value, ScriptFactory::scriptPubKey()->p2sh($redeemScript)

Thanks, it seems to work. I also had to add this:
$signData = new SignData();
$signData->p2sh($redeemScript);
And added $signData to the signer as follows:
sign(0, $myPrivateKey, $txOut, $signData)
One more question, what is the $value and how did you get it exactly? Sorry if it's a trivial thing, I'm quite a novice in this.

I mightn't have tagged a new version yet.. You shouldn't have to pass SignData if it's already signed or has the redeemScript, let me take a look. I ignored that part of your example thinking it would have been fine.
Oh, the value is the BTC amount you received on your multisig address (in satoshis!) I just made 1 up, since it comes from the API or whatever. Coinbin probably looked up the address and found the txid, vout, value and scriptPubKey when you made the transaction.
The value is actually checked anywhere if your transaction isn't segwit, but don't rely on this behavior in future versions.

What version are you using?

I'm using v<IP_ADDRESS>. When I don't pass SignData to the sign function it raises the error "Redeem script requested but not set".
Sorry if I'm repeating myself, but isn't there a way to get the BTC amount from the transaction hex in PHP using this library? Or is there a way at all?

Ah ok, just the one before! Yeah, SignData became unnecessary if the details in the transaction are enough.
Actually, the amount is only set in the transaction that created the

Thanks for taking the time to explain. I was a bit confused on what a transaction consists of, but I think I'm slowly starting to figure things out :)
And by the way, thanks for creating this library too. It's already helped me enormously!


Long output causes issues writing to console

Might be related to hitting the scroll back limit

I noticed this too.


Request: Support of InheritedWidget

I want to start by expressing my gratitude to the author for excellent work in enabling code push functionality.
The plugin has proven to be incredibly valuable for our Flutter projects, making the app update process smoother and more efficient on design part.
While the eval plugin currently supports the use of BuildContext, I would like to kindly request the addition of support for InheritedWidget.
ChangeNotifier is a widely used mechanism for managing state in Flutter applications. By enabling InheritedWidget support, we can ensure that the ChangeNotifier implemented within the eval plugin can seamlessly communicate state changes to the entire widget tree, simplifying complex state management scenarios.
InheritedWidget is also invaluable for maintaining global configurations or settings within an app. With this support, developers can use eval to dynamically update and distribute these configurations throughout the app.
Looking for any updates or solutions regarded InheritedWidget use through eval.
This will be a significant enhancement that would make the plugin even more versatile and beneficial to the Flutter community.

Hi and thanks for the kind words :)
InheritedWidget is a particularly difficult case since Dart has no mechanism for dynamically specifying type parameters. dependOnInheritedWidgetOfExactType requires specifying the type parameter T and there is no way dart_eval can do that dyamically, outside of having a giant piece of code with every single possible Widget type mapped to that function. As you can imagine, generating that for every single function that takes type parameters is unrealistic. Doing it for that one function only is more doable, but still a far-future project.
Since support for state management packages like Riverpod is much easier, that'll likely happen first.

But is it possible to make bridge to exact one component? If we don't want to build a universal solution, but some strongly typed solution for exact one native plugin?

@nosovk Of course yes, there is no restrictions on what you can do with bridging.

@bgoncharuck could we make bridge to webview only? Not a universal solution, but exactly one that required?


Plotting functions now are able to take in axes

Plotting functions now are able to take in axes where the figures can be drawn. Useful for when you want to customize the plots manually outside the function as well as making subplots.

Looks like you have flake8 issues


Like or Dislike unavailable when connecting to Spotify Connect

 Issue by Kia0ra
Wednesday Sep 27, 2017 at 06:02 GMT
Originally opened as https://github.com/plietar/librespot/issues/254

The Like or Dislike commands disappear from the player as soon as the Spotify Connect (using librespot/raspotify) device is chosen to play audio. Instead the Random / Repeat commands appear.

This behaviour no longer occurs.

This issue is there again, build with latest commits. Exactly the same behaviour as in first post.


Update Vagrantfile to include a Requirements.txt

As a Service
I need to have all required libraries installed when the VM is created
So that all developers will be working with the appropriate libraries
Assumptions:

Create a Requirements.txt that includes the current stable release of Flask

Acceptance Criteria:
When I start the Vagrant VM with `vagrant up && vagrant ssh`
And I run a python file referencing Flask using `from flask import Flask`
I should not get any compile issues.

A good starting point for a Requirements file:
https://github.com/nyu-devops/lab-restful-flask/blob/master/requirements.txt
This file contains more libraries than we need know but it is a good example.


Layer style in Demo

I'm trying the demo: The bar chart is displaying with no visual properties, and the line chart displays as an objectless clear line. I'm going to try and sell my boss on getting this for our team if I can show him something good.

Hi! Apologies for the late response. Good catch! Looks like a compatibility issue. I will be fixing this ASAP.


Added russian language

Does it written in февраль of February ?

it's witten as 'Декабрь' but should be written as 'Февраль'

right, it's witten as 'Декабрь' but should be written as 'Февраль'

It was fixed here
In master it is ok. Try to pull updates


feat!: use @grpc/grpc-js instead of grpc

BREAKING CHANGE
Make all client libraries use @grpc/grpc-js by default. The libraries that still want to use legacy grpc should pass the instance of grpc to client library constructor.

[x] Tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Something wrong with authentication - investigating...

So, the authentication problem is caused by incorrect service account key (which just stopped working for some reason). I think at this point it's OK to remove the client library test (pub/sub, video intelligence, and speech), since we have an end-to-end test with a local gRPC server and it's much less fragile. When we are done will all these upgrades and semver major releases, we can put the client library system test back, but right now it will just prevent us from doing releases.


Use Weaviate's readiness endpoint

Currently, Testcontainers Weaviate implementation relies on port availability.
This commit switch to Weaviate's readiness endpoint.

Thanks @eddumelendez . Lets see how would this play.


5/24/2022 Publish

Docs Build status updates of commit 1aa012d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-autogen/microsoft-cognitiveservices-speech-sdk/index.yml
:warning:Warning
View (azure-node-latest)
Details

docs-ref-autogen/toc.yml
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/arm-appplatform-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/arm-changes-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/arm-network-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/arm-servicelinker-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/latest/core-paging-readme.md
:warning:Warning
View (azure-node-latest)
Details

docs-ref-services/preview/ai-text-analytics-readme.md
:warning:Warning
View (azure-node-preview)
Details

docs-ref-services/preview/arm-containerservice-readme.md
:warning:Warning
View (azure-node-preview)
Details

docs-ref-services/preview/arm-eventgrid-readme.md
:warning:Warning
View (azure-node-preview)
Details

docs-ref-services/preview/arm-securityinsight-readme.md
:warning:Warning
View (azure-node-preview)
Details

docs-ref-services/preview/communication-email-readme.md
:warning:Warning
View (azure-node-preview)
Details

docs-ref-services/preview/core-lro-readme.md
:warning:Warning
View (azure-node-preview)
Details

docs-ref-services/preview/service-bus-readme.md
:warning:Warning
View (azure-node-preview)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-preview)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-preview)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-preview)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-preview)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-preview)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-preview)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-preview)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-preview)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-preview)
Details

<EMAIL_ADDRESS>:warning:Warning
View (azure-node-preview)
Details

<EMAIL_ADDRESS>:bulb:Suggestion
View (azure-node-preview)
Details

This comment lists only the first 25 files in the pull request.

docs-ref-autogen/microsoft-cognitiveservices-speech-sdk/index.yml

Line 8, Column 5: [Warning: xref-not-found] Cross reference not found: 'microsoft-cognitiveservices-speech-sdk.request'.

docs-ref-autogen/toc.yml

Line 65535, Column 12: [Warning: xref-not-found] Cross reference not found: 'microsoft-cognitiveservices-speech-sdk.request'.
Line 65535, Column 12: [Warning: xref-not-found] Cross reference not found<EMAIL_ADDRESS>

docs-ref-services/latest/arm-appplatform-readme.md

Line 9, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'appplatform'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

docs-ref-services/latest/arm-changes-readme.md

Line 9, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'changes'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

docs-ref-services/latest/arm-network-readme.md

Line 9, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'network'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

docs-ref-services/latest/arm-servicelinker-readme.md

Line 9, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'servicelinker'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

docs-ref-services/latest/core-paging-readme.md

Line 9, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'core'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

docs-ref-services/preview/ai-text-analytics-readme.md

Line 9, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'textanalytics'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

docs-ref-services/preview/arm-containerservice-readme.md

Line 9, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'containerservice'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 20, Column 1: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /javascript/api/@azure/arm-containerservice?view=azure-node-preview. Otherwise, remove the view parameter.

docs-ref-services/preview/arm-eventgrid-readme.md

Line 9, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'eventgrid'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.
Line 20, Column 1: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /javascript/api/@azure/arm-eventgrid?view=azure-node-preview. Otherwise, remove the view parameter.

docs-ref-services/preview/arm-securityinsight-readme.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Azure Service client library for JavaScript' is duplicated in: 'docs-ref-services/preview/arm-analysisservices-readme.md(2,8), docs-ref-services/preview/arm-deploymentmanager-readme.md(2,8), docs-ref-services/preview/arm-managementgroups-readme.md(2,8), docs-ref-services/preview/arm-orbital-readme.md(2,8), docs-ref-services/preview/arm-portal-readme.md(2,8),...'. Titles must be unique within a docset.
Line 9, Column 13: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.service': 'securityinsight'.
Line 11, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Azure Service client library for JavaScript - Version 1.0.0-beta.3' is duplicated with other articles: 'docs-ref-services/preview/arm-orbital-readme.md(11,1), docs-ref-services/preview/arm-portal-readme.md(11,1), docs-ref-services/preview/arm-securityinsight-readme.md(11,1)'. First level headings must be unique within a docset.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Bevy wayland window name is "Unknown"

Bevy version
Current main branch
25b62f95773f6da46143772f86b8198937507f95
Operating system & version
Fedora 35
What you did
cargo run --example 3d_scene --features bevy/wayland
What you expected to happen
Name should be the same as executable. It's correct with feature bevy/x11

What actually happened
Application name is "Unknown". Apart from that, title bar is not native and doesn't change after "Set title" is called.

Additional information
I updated the code of 3d_scene example to change the title. It's correct in x11, but not in wayland:
    let window = windows.get_primary_mut().expect("Window should be present");
    window.set_title("3D Scene".to_string());

Suggestion
Do we need to include more examples with set_title? I found only 1 usage in window_settings example.

This seems like a winit issue, as we're not doing any native handling of this.

Looks like winit doesn't handle window names properly. I believe that it doesn't have proper functionality to setup "appid", I think that this should be handled by bevy at this point. Someone from maintainers could look at anvil/src/winit.rs, and see how they handle window name for Compositor under winit backend.

I'd be very surprised if we decided it was our job to fix winit not handling a platform properly, although I might be missing some context here. I'd certainly be inclined to push back against any PR which added a fix which linked into platform specific code in this codebase.
Winit supports setting the window title - https://docs.rs/winit/0.26.0/winit/window/struct.Window.html#method.set_title, and doesn't list wayland as unsupported there.
I had a quick look at winit's issue tracker, and it doesn't seem like this is tracked, although @HeavyRain266 it seems like you have more knowledge of how wayland works to report it.

This is almost certainly because Wayland requires CSDs (client side decorations). Winit literally choose how / where to draw the window decorations, and probably doesn't have code written (or enabled) to render a title.

One solution is to depend on a library that can render the decorations (like GTK3) but I appreciate that winit doesn't depend on that. Maybe ultimately we should just draw our own :smile:

This is almost certainly because Wayland requires CSDs (client side decorations).

Wayland requires the client to support CSD. There is an extension for server side decorations implemented by (pretty much) everyone except gnome as they really want client side decorations only for some reason despite people complaining.

One solution is to depend on a library that can render the decorations (like GTK3) but I appreciate that winit doesn't depend on that. Maybe ultimately we should just draw our own :smile:

For Wayland there is protocol for creating surfaces (there is native rust implementation), it's called xdg-shell, which Compositors as renderers connected to headless Display Servers are using for compositing surfaces (images) into window.

This is almost certainly because Wayland requires CSDs (client side decorations).

Wayland requires the client to support CSD. There is an extension for server side decorations implemented by (pretty much) everyone except gnome as they really want client side decorations only for some reason despite people complaining.

GNOME is most problematic Wayland DE to support, they don't follow any existing standards used by almost every software/server author, many programs which are adding HUDs and Overlays for Wayland doesn't work in GNOME because they don't want to support popular Layershell protocol which adds z-index to renderer as "layers" where author choose layer to render his software i.e on top of everything or most bottom layer for wallpaper image/gif/shader.

Investigation

Gnome forced Wayland apps to implement CSD,  whether on their own or using some libraries like Gnome's official solution libdecor. Many Linux apps do this with libdecor, like blender, kitty... I think it's not comfortable for Bevy to fix this problem this way.
Winit has support for CSD on wayland(https://github.com/rust-windowing/winit/blob/8bb004a1d9ec1b40cbb9831a6dea774d4b6d6d7b/Cargo.toml#L42), but Bevy disabled Winit's default features, thus no winit's wayland-csd-adwaita feature. And Bevy's wayland feature doesn't include winit's wayland-csd-adwaita feature so users can't get window decorations on Wayland even with Bevy's wayland feature enabled.
Many rust UI toolkit, like iced, doesn't disable winit's wayland-csd-adwaita feature.

Conclusion and one Possible solution
Bevy disabled winit's default features in order to decrease package size. But I think it's acceptable to add winit's wayland-csd-adwaita feature to Bevy's wayland feature gate to fix this issue easily for this only add on crate: sctk-adwaita.


When running locally is there any plan to save progress?

For example in rustlings we can keep track of the completion of every exercise

Thank you for your great suggestion, you are right, this feature is really good and helpful. But just for now,  Rust By Practice is more like a exercise Book, you  have to record the progress yourself :-P
In future,  we will support it, but probably in a way that is different from what rustlings is doing now.

For example in rustlings we can keep track of the completion of every exercise

For now, one hack that works is - launch the site locally using mdbook, go to en/src/<topic name>.md, edit it in-place, and refresh the page in the browser, and check the code using the run button. Once it passes, commit the changes to the md file.


feat(pkg/trafficpolicy) : updating merge logic for inbound and outbound traffic policies

Description:
This commit allows partial hostname matches while merging both inbound
and outbound traffic policies. This change is necessary to support host
headers that users will specify as a part of the TrafficSpec and as this
will be a single host, so can only partially match to an existing
traffic policy and if that is the case the two policies should be
merged.
The commit also improves the logic of the 'subset` function in this
package. It checks is either slice is a subset of the other and returns a union of them
This is part of #2369
Signed-off-by: Sneha Chhabria<EMAIL_ADDRESS>Affected area:

New Functionality      [ ]
Documentation          [ ]
Install                [ ]
Control Plane          [ ]
CLI Tool               [ ]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests                  [ ]
CI System              [ ]
Demo                   [ ]
Performance            [ ]
Other                  [ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution? no

@draychev and @michelleN  thanks for the review, I have updated the PR to improve naming/comments. PTAL


Make whole model application type stable

Currently, @inferred test fails for ProductNodes.

Fixed in https://github.com/CTUAvastLab/Mill.jl/commit/5b028aecd8460d2f80becfbc6e6215b0f1a87716


Wrong variable name in query-evaluation-model-in-detail.md

https://github.com/rust-lang/rustc-guide/blob/9b3803d35d0e9ee80c0b42ee58ed472b16f06ea8/src/queries/query-evaluation-model-in-detail.md#L117-L123
let list_of_items should be let list_of_hir_items
or
for item_def_id in list_of_hir_items {  should be for item_def_id in list_of_items {

@SarthakSingh31 Thanks for the report :)
Would you mind opening a PR to fix this? The compiler is constantly under development, so things become outdated sometimes.

@mark-i-m I created a pull request.


cannot deploy application using poetry

Currently trying to follow your tutorial and which i run the command poetry run -- deploy -f test-assembly.yaml   if get the error below.

[FileNotFoundError]
[Errno 2] No such file or directory

Not entirely sure why this is happening and all the fixes around this error and poetry are not working. have you run into this issue before ?

Hi, I am having this same issue. Did you find a solution for it? @setswei

Hi Guys, sorry for the late answer and thank you for reporting the error. This is due to the flag separator -- that was necessary in beta versions of poetry.
If you have a recent version of poetry (1.0.5), you can do the following (without the --):
poetry install # to install the dependencies
poetry run deploy -f test-assembly.yaml # to deploy

I also noticed an error in the template for the configuration file (in the blog post). Please use the following (no https:// prefix for CognitoUserPool.DomainName):
StacksPrefix: TestBarrier
CookieName: TestBarrier
Environment:
  AWSProfile: <<<profile-name>>>
  Region: us-east-1
Packaging:
  S3Buckets:
    us-east-1: <<<S3 bucket name>>>
  S3Prefix: TestBarrier
Cloudfront:
  DomainName: <<<cloudfront domain name>>>
CognitoUserPool:
  UserPoolId: <<<user pool id>>>
  DomainName: <<<user pool domain prefix>>>.auth.us-east-1.amazoncognito.com
  UserPoolClientProperties:
    ReadAttributes:
      - email
    WriteAttributes:
      - email
    SupportedIdentityProviders:
      - COGNITO

done: https://codesmith.ch/blog/2019-11-05-cogcf-barrier/


Add sort-package-json tool

coverage: 93.864%. remained the same when pulling 547332758ce6601d490e582380737f762310245a on cody-sort-package-json into 7e572aeef1fe7973f5c7d5b4edbad20062c1bc03 on main.


fix: divergence from std go and minimal args check

This pull request resolves issue https://github.com/d5/tengo/issues/352 and additionally adds a minimum args check.

👍

Thanks for the reminder @iFrozenPhoenix
I’ve been meaning to create a branch for v3. I’ll try to do it sometime this week.


Please add Dark Mode support to the Outlook Mac Insights plugin.

@anthonyjhicks -Thanks for your feedback. I'll pass your request on to the team.


Create golangci-lint.yml

Issues associated with this PR
Your PR should present related issues you want to solve.
Solutions
You should show your solutions about the issues in your PR, including the overall solutions, details and the changes. At this time, Chinese is allowed to describe these.
UT result
Unit Test is needed if the code is changed, your unit test should cover boundary cases, corner cases, and some exceptional cases. And you need to show the UT result.
Benchmark
If your code involves the processing of every request, you should give the Benchmark Result.
Code Style

Make sure Goimports has run
Show Golint result

Codecov Report

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

@@            Coverage Diff             @@
##           master    #1250      +/-   ##
==========================================
+ Coverage   54.92%   54.95%   +0.02%
==========================================
  Files         312      312
  Lines       28182    28182
==========================================
+ Hits        15479    15487       +8
+ Misses      11229    11221       -8
  Partials     1474     1474

Impacted Files
Coverage Δ

pkg/module/http2/frame.go
84.17% <0.00%> (-0.31%)
:arrow_down:

pkg/module/http2/transport.go
78.91% <0.00%> (+0.28%)
:arrow_up:

pkg/network/connection.go
35.34% <0.00%> (+0.37%)
:arrow_up:

pkg/stream/stream.go
46.66% <0.00%> (+13.33%)
:arrow_up:

Continue to review full report at Codecov.

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


Set environment variable LOGNAME to RUNNER_USER on linux runner

Fix #39
Signed-off-by: Sophia Guo<EMAIL_ADDRESS>

Tests:
https://github.com/sophia-guo/runaqaTest/actions/runs/415759548


NumberBox: Add expression calculation

This changes add the AcceptsCalculations property back to NumberBox, as well as the parser for parsing expressions. Essentially, the parser takes an input string, tokenizes it into alternating numerical and operator tokens, rearranges the tokens into postfix notation, and then computes the value from there.
The only issue I'm currently aware of is that "-(2 + 3)" doesn't evaluate -- a negative indicator before parenthesis isn't handled. It's on the list of bugs.
In addition, I discovered that .NET's default double-to-string parser truncates doubles at 12 significant digits, so I simplified our parser to do the same.

OK @StephenLPeters, pushed updates for you :)


Don't error on Get-ChildNode if LeafNode

return a warning (rather than an error) when Get-ChildNode is a leaf node

Resolved in 0.0.20


Add init.py

I added __init__.py to ssspy/utils to import this module.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@b3615ee). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop      #49   +/-   ##
==========================================
  Coverage           ?   91.33%
==========================================
  Files              ?       16
  Lines              ?     1212
  Branches           ?        0
==========================================
  Hits               ?     1107
  Misses             ?      105
  Partials           ?        0

Continue to review full report at Codecov.

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


Translate ConcurrentSeqNoVersioningIT

Summary of the changes / Why this improves CrateDB
Checklist

[ ] User relevant changes are recorded in CHANGES.txt
[ ] Touched code is covered by tests
[ ] Documentation has been updated if necessary
[ ] CLA is signed
[ ] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Closing this as we'll revise it once we have support for RETURNING


DF Active Lights: Not working in v9

Light animation isn't working properly in v9.  animData is still in the v8 format. Most light-specific properties have been moved to data.config from data:
data.dim -> data.config.dim
data.bright -> data.config.bright
data.angle -> data.config.angle
data.tintAlpha -> data.config.alpha
data.tintColor -> data.config.color

data.rotation is still data.rotation.
Another thing I noticed: Why isn't the normal updateSource called? This bypasses other modules that wrap updateSource. I recommend to remove _updateSource and replace LightAnimator._updateSource.bind(light)(); by light.updateSource(), which schedules lighting/sight refreshes, and then we don't need to do it in _LightingLayer_animateSource, where lighting/sight refreshes are permanently spammed even if no DF animated lights are in the scene, which impacts the performance significantly.

DF Active Lights has already been updated for V9 compatibility, this particular issue is covered by #267.
As for the question about using the core updateSource function, the problem is this bit of code here:

If the light radius drops to 0 at any given point, the light be automatically deleted from the lighting layer by Foundry. This is obviously not great if anyone is  attempting to create a pulsing light. Unfortunately that cannot be correct by a simple wrapper, but must be overridden entirely, so I decided to create my own function that had less code and improved performance.

It's definitely not working (v1.2.0). Video:
https://user-images.githubusercontent.com/31905376/147977458-8c05228f-4e61-4a7a-a070-67285b839026.mp4
And look at those uniforms: see exposure is -0.5, colorBright is black, etc.

If the light radius drops to 0 at any given point, the light be automatically deleted from the lighting layer by Foundry. This is obviously not great if anyone is attempting to create a pulsing light. Unfortunately that cannot be correct by a simple wrapper, but must be overridden entirely, so I decided to create my own function that had less code and improved performance.

That shouldn't be an issue, right? It would be added right back to the sources of the lighting layer once the radius is greater than zero. You could also simply add something like Math.max(bright, 0.001) / Math.max(dim, 0.001) to your animData if deletion is undesirable.
What is important though is that _LightingLayer_animateSource must not request lighting/sight updates unless it is strictly required. Even if no DF animated lights are in the scene, lighting and sight are constantly refreshed.
https://github.com/flamewave000/dragonflagon-fvtt/blob/68eb4dbae5a7db28a5ebf136891cfda830a00ccf/df-active-lights/src/LightAnimator.ts#L60-L67

I'm not sure why your light is not working, it is working in my test V9 environment. Maybe a module conflict?
I ran into an issue where if a light was deleted from the lighting layer, it had to receive an actual data "update" in order for the LightingLayer to re-add it to the canvas. Simply calling the updateSource does not re-add it to the Canvas. Though, I could look at adding a "buffer zone" where the light radius snaps to to prevent == 0 failure.
As for the the concern of too many updates, the module only animates and updates each light IF there is an animated light source in the scene. This is checked for at df-active-lights/src/LightAnimator.ts:75. If there is no anim data, or the anim data is empty, it is ignored and the function immediately returns for that light. But I do see what you mean that for each render frame, the sight layer is scheduled for a refresh. I can add boolean return on each _PointSource_animate to say if the light animated or not and prevent a sight layer update if no animation occurred.

I double checked: no other are modules active. I uninstalled/reinstalled Active Light, CTRL+F5 and devtools disabled cache, new scene, new light. Same results.

I ran into an issue where if a light was deleted from the lighting layer, it had to receive an actual data "update" in order for the LightingLayer to re-add it to the canvas.

Hm, that's definitely odd.

I can add boolean return on each _PointSource_animate to say if the light animated or not and prevent a sight layer update if no animation occurred.

That would be great.

Hm, that's definitely odd.
Yeah it was very frustrating that there wasn't a simpler method to re-add the light to the CanvasLayer. But that might be moot if I do the min/max buffer 🤷🏽♂

the sounds folder disappeared on the zip?

my module folder after updating today

@irbian you're issue is unrelated to this ticket. Please open a separate ticket for DF User Logger.


Add a cache of MediaType objects

@rsvoboda I know full eviction of the cache is unfair and looks simplistic; in facts it's really just the most straightforward safety belt for avoiding explosion of the cache. A LRU approach would be better, assuming it's efficiently implemented. Let's see the benefits of the current solution first and then evaluate improvements, ok?

+1 for simple solution now + evaluate improvements

Closing for now as it looks like the improvements are not as great as expected. Might re-evaluate in future.


Release tag request

Hello,
I'm with Azure's AI/HPC engineering organization and we are currently evaluating this tool to replace our current perf-test loopback checks. We would like to integrate this into our VM health check test suite.
Would it be possible to have tagged releases for ngc_multinode_perf? We like to manage our dependencies by release tag versions.

Hi @rafsalas19 , it is indeed planned. I'll try to expedite it. Thanks.

@rafsalas19 , please use this to download the latest stable tag: https://github.com/Mellanox/ngc_multinode_perf?tab=readme-ov-file#download-the-latest-stable-version
We will put stable tags from time to time, when there are major changes, after they were tested.


Add new methods for List and fix #11616

Add two new methods for get storage data(maybe this kind of methods has existed)
Close #11616

Hi, I've leaved comments on the code.
Also the min max calculation is already in the https://github.com/apache/incubator-echarts/pull/11617/files#diff-ed976f176ba3ed927f196407ddc456a0L68 . I think the fix should be in the function numCalculate. And there is no need to copy all the data out of the List module.

@pissang I think numCalculate has no logical problem, only the parameter. When the chart is stacked, it returns max or min of the stacked data, and then using indicesOfNearest to get data index. So just set dimension to target dimension will fix this.


feat(deps): [Manual Review Required] Update stack definition member versions

Update stack definition member versions. Major version update detected. Please review the changes.

/run pipeline

/run pipeline

/run pipeline

I think this got stuck again and I can't figure out how to get pipeline going again, it is stuck on this step:

tests.go:457: [Projects] Deploying group 5/X

I tried to find the project and do a config-sync but its either not working or I have the wrong projects.

I'm going to make one small change to this branch, I'm going to use the new feature to selectively not deploy cluster to a management vpc

/run pipeline

/run pipeline

Daniel is running this locally through the newer test framework to identify the issue

Looks like when the updater automation runs and detects and already open PR with the branch stack-update it closes the existing PR and opens a new one. Thats what happened to this PR. It created new one: https://github.com/terraform-ibm-modules/dev-rag/pull/52
I'll push Todds commit to that branch now since it contains all the latest version locators


Create bam index

This creates indices in STAR and HISAT2 processes.

Should solve: https://github.com/nf-core/rnaseq/issues/71

Ah, wait - tests failing.
ERROR ~ Error executing process > 'star (SRR4238355_subsamp)'
Caused by:
  Missing output file(s) `*.bai` expected by process `star (SRR4238355_subsamp)`


Updated find an issue with new labels

Fixes #16156
Signed-off-by: Lynda O'Leary<EMAIL_ADDRESS>

Terribly sorry for the delay here, @lyndaoleary, I thought I already commented on this one.
This PR looks to need a rebase (GitHub says there are merge conflicts). I like the things you did here, but I want @moxiegirl to have a look at them as well, because it's possible some things were written the way they were for a specific reason.
Thanks so much for doing this!

These files have moved to https://github.com/docker/opensource/tree/master/docs can you reopen your PR there please.  (Also when I attempt to make them I'm getting a sphinx error.)


updated spelling of somelabel

@TravisCragg-MSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@vhorne based on #32936, can you approve?

confirm typo fix