Allow using labels for nodeSelector

Allow using labels for nodeSelector.
This then allows deploying resources to several nodes

/verified

/verified


sdk/state: refactor validations to check against the channel state

WHAT
changes the validations for checking if the channel is open to use the Channel State instead of checking the openAgreement is empty or not
WHY
the channel state better reflects if the channel is actually open based off of ingested transactions. And more accurately gives the state of the channel.
closes https://github.com/stellar/experimental-payment-channels/issues/261

note: moved the test improvements to this PR: https://github.com/stellar/experimental-payment-channels/pull/277
to use the channel.State for validations it looks like we'll need to add more state values, to ensure we're validating at a granular enough level. Closing this PR for now as that will take some additional thought and possible refactoring


Build fails on OS X

$ cargo build
    Updating registry `https://github.com/rust-lang/crates.io-index`
   Compiling winapi v0.2.6
   Compiling bitflags v0.3.3
   Compiling winapi-build v0.1.1
   Compiling ole32-sys v0.1.0
   Compiling lazy_static v0.1.15
   Compiling pkg-config v0.3.8
   Compiling gcc v0.3.25
   Compiling hound v1.1.0
   Compiling libc v0.2.8
   Compiling kernel32-sys v0.2.1
   Compiling time v0.1.34
   Compiling coreaudio-sys v0.1.2
   Compiling ogg-sys v0.0.9
   Compiling vorbis-sys v0.0.8
   Compiling vorbisfile-sys v0.0.8
/Users/yupferris/.cargo/registry/src/github.com-88ac128001ac3a9a/coreaudio-sys-0.1.2/src/lib.rs:5:10: 5:28 warning: lint raw_pointer_derive has been removed: using derive with raw pointers is ok
/Users/yupferris/.cargo/registry/src/github.com-88ac128001ac3a9a/coreaudio-sys-0.1.2/src/lib.rs:5 #![allow(raw_pointer_derive)]
                                                                                ^~~~~~~~~~~~~~~~~~
   Compiling coreaudio-rs v0.4.0
   Compiling cpal v0.2.9
   Compiling vorbis v0.0.13
/Users/yupferris/.cargo/registry/src/github.com-88ac128001ac3a9a/cpal-0.2.9/src/lib.rs:334:20: 334:30 error: no method named `get_period` found for type `cpal_impl::Voice` in the current scope
/Users/yupferris/.cargo/registry/src/github.com-88ac128001ac3a9a/cpal-0.2.9/src/lib.rs:334         self.voice.get_period()
                                                                                ^~~~~~~~~~
error: aborting due to previous error
Build failed, waiting for other jobs to finish...
Could not compile `cpal`.

To learn more, run the command again with --verbose.

This applies to both the latest version of this repo and also the published version on crates.io (0.3.1).

I'm on OS X using Rust stable 1.7. I have yet to test on any other OS', but I will test on Windows as well shortly.

Tested on Windows, and cargo build works, but trying to run any examples or link against the library fails with the error I reported previously in #63 .

Looking more into the error, it looks like it's specific to cpal on OS X. Will test further.

Indeed, cpal doesn't build on its own either. Will file a ticket there.

Ah ofc it doesn't, that's still not supported yet. I apologize for the spam :)

Closing this as it's irrelevant until https://github.com/tomaka/cpal/issues/104 is resolved.


Update networking.md

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
For 1.11 Features: set Milestone to 1.11 and Base Branch to release-1.11
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
NOTE: After opening the PR, please un-check and re-check the "Allow edits from maintainers" box so that maintainers can work on your patch and speed up the review process. This is a temporary workaround to address a known issue with GitHub.>
Please delete this note before submitting the pull request.

@scott-cumulus, we can only accept a pull request from you after you have signed the contributor license agreement. Please follow the instructions in the comment above.

@scott-cumulus Please feel free to re-open this PR after signing the CLA.


Adding alpha sort to file set list

Restoring the sorted file set name that was lost in this commit: https://github.com/concrete5/concrete5/commit/ea0092092d57ad38a739977f35e0b520cc582824

Thanks @tylerryan


Typo in "Speech Service API Documentation"

The bug
There's a typo on one of the pages in the "Speech Service Documentation"
To Reproduce
Steps to reproduce the behavior:

Go to https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/
Scroll down to '10-Minute Quickstarts - New SDKs'
See the text just below the heading

Expected behavior
The line under the heading reads "Learn how to install and use the Speeck SDK with our quickstarts" where as it should be "Learn how to install and use the Speech SDK with our quickstarts" (presumably).
Screenshots
Please see attached screenshot.

@wiazur can you please help here?

Thanks for letting us know @dend !

This is fixed now


Update TextSequence.pm

Changed 'variations' to 'variants' in messages sections. Also wonder if we can do this on line 1297 but didn't want to without creating a sandbox.

Please wait for another 4 commits to come in from me.

These are all in now (even if there aren't 4)


Multiple assets emit different content to the same filename

Bug report

What is the current behavior?
webpack shows a warning when rebuild:

Multiple assets emit different content to the same filename app.js.map

If the current behavior is a bug, please provide the steps to reproduce.
webpack.config.js
const path = require('path')
const webpack = require('webpack')

module.exports = {
  mode: 'development',
  entry: {
    app: './entry.js'
  },
  output: {
    path: path.resolve(__dirname, './dist'),
    filename: '[name].js'
  },
  devtool: false,
  plugins: [
    new webpack.SourceMapDevToolPlugin({
      filename: '[name].js.map'
    }),

    new webpack.HotModuleReplacementPlugin() // !!!!!!! remove this line, the warning will not display
  ]
}

entry.js
console.log(`
  modify this module, then webpack shows warning:
  WARNING in Conflict: Multiple assets emit different content to the same filename app.js.map
`)

reproduction steps:

use SourceMapDevToolPlugin and HotModuleReplacementPlugin (refer to webpack.config.js)
npx webpack --watch
modify content of entry.js, then save
webpack shows a warning: Multiple assets emit different content to the same filename app.js.map

webpack doesn't show this warning if i remove the line new webpack.HotModuleReplacementPlugin()
What is the expected behavior?
webpack should not show a warning

Other relevant information:
webpack version:  4.41.0
Node.js version: v10.15.3
Operating System: win10

I have the same warning. I am using devServer and webpack.SourceMapDevToolPlugin. The file names are static.

Please create reproducible test repo

@evilebottnawi
https://github.com/donotlb/webpack-iss-9732

@dolymood WIP

@donotlb Please use filename: '[file].map[query]' for SourceMapDevToolPlugin, you can't use [name] because hmr emit updates for example using app.3d0af954e7d8c1e90af5.hot-update.js file and you have two files before source map:

3d0af954e7d8c1e90af5.hot-update.json
app.js - [name] is app
app.3d0af954e7d8c1e90af5.hot-update.js - [name] is app

then you generate source map using [name].js.map for second asset and third asset and get two assets with the same name app.js.map

The problem is resolved, feel free to feedback, thanks for issue

Please help to solve this warnings after angular 9 and primeng 9 migration
WARNING in ./src/assets/css/style.css
Module Warning (from ./node_modules/postcss-loader/src/index.js):
Warning
(146:3) start value has mixed support, consider using flex-start instead
WARNING in Conflict: Multiple assets emit different content to the same filename loading.gif
WARNING in Conflict: Multiple assets emit different content to the same filename password-meter.png

If you're facing this problem with Quasar, be sure to set gzip to false in quasar.conf.js within the build object.

For me using Quasar v1 this problem caused because I placed different images with same name in different folders, and then I import them.
Files tree:
- foo
	- index.ts
	- assets
		-  image.png
 - bar
	- index.ts
	- assets
		-  image.png

foo/index.ts:
import image from './assets/image.png`

bar/index.ts:
import image from './assets/image.png`

And then I get error in build console when I run quasar dev:
Error: Conflict: Multiple assets emit different content to the same filename img/image.png

But I do not get this error when I run quasar build.
It's because Webpack config in Quasar uses image hash only on build mode, not dev.
When I look into this image in browser, it's /img/image.png for both images from both folders. But I don't want to name images differently since they in different folders already, and I cannot guarantee that every image in my project have unique name.
So I added this to quasar.conf.js:
chainWebpack(chain) {
	chain.module.rule('images')
		.use('url-loader')
		.loader('url-loader')
		.options({ esModule: false, limit: 0, name: 'img/[hash].[ext]' })
},

Now every image has hash in filename.

@Grawl you saved me a lot of time 👏🏻

@alexander-akait
Sorry to bother you but I don't understand what's going on here. I had this simple config in a webpack 3 project:
const path = require('path')
const webpack = require('webpack')

module.exports = {
  mode: 'development',
  entry: {
    app: './entry.js'
  },
  output: {
    path: path.resolve(__dirname, './dist'),
    filename: '[name].js',
    sourceMapFilename: '[name].js.map'
  },
  devtool: 'source-map'
}

After upgrading to webpack 5, I encountered the error mentionned in this issue:

Multiple assets emit different content to the same filename app.js.map

Commenting sourceMapFilename config solves the issue. The app.3d0af954e7d8c1e90af5.hot-update.js was not existing in webpack 3?

Do you update webpack-dev-server, and why don't use the default '[file].map[query]' value for sourceMapFilename? Try to add [query]

@alexander-akait Hi Alexander, I think it would be helpful if the documentation at https://webpack.js.org/plugins/source-map-dev-tool-plugin/ could be updated to remind users of using correct sourceMapFilename.
Specifically the examples there use '[name].js.map' which is likely why so many people make this mistake. (The example may work due to its simplicity, but you know our first attempt is copy & paste the example ;-) )

:+1:


DX w/ monorepo tooling

Story
As a developer who just started working on projects, I stumbled upon a bump while bootstrapping the app. The repository seems to be monorepo, but lacks appropriate tooling (e.g. lerna, pnpm). There is no instruction for a developer to run npm i in every folder you're going to work in, and default npm i in root folder didn't help much. Combining with wild-card module declaration (which is in my belief smelly code by itself) it caused me to dig for some time why every module in project is broken and linked to wildcard module declaration.
Proposals

add monorepo tooling (probably later, it takes more than just a couple of steps)
add bootstrap instructions in every sub-repo
be more developer-friendly, even if a developer came from non-nodejs world (to fix something pretty trivial, for example)

There are just two subprojects (backend and frontend), so it felt like an overkill to introduce extra tooling for that. My plan was to use docker-compose as the way to document how to run the project altogether.
P.S. cli folder should be removed: https://github.com/near/near-explorer/pull/804

As of my experience, in this kind of setup (just client and server) package.json is usually shared.
Anyway, I believe a little extra documentation won't hurt anyone

Meh, I don't think it is a good idea to mix client and server dependencies / commands since that may cause various unexpected issues.

This might do it.


introduce verify-attached-operators

Verify attached operator manifest references are shipping or already shipped.
Takes a list of advisories that may contain operator metadata/bundle builds or image builds that are shipping alongside. Then determines whether the operator manifests refer only to images that have shipped in the past or are shipping in these advisories. An error is raised if there are no manifest builds attached, or if any references are missing.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@9287447). Click here to learn what that means.
The diff coverage is 1.96%.

@@            Coverage Diff            @@
##             master     #161   +/-   ##
=========================================
  Coverage          ?   24.17%
=========================================
  Files             ?       39
  Lines             ?     3285
  Branches          ?      637
=========================================
  Hits              ?      794
  Misses            ?     2466
  Partials          ?       25

Impacted Files
Coverage Δ

elliottlib/cli/__main__.py
0.00% <0.00%> (ø)

elliottlib/cli/verify_attached_operators_cli.py
0.00% <0.00%> (ø)

elliottlib/brew.py
61.63% <25.00%> (ø)

elliottlib/constants.py
100.00% <100.00%> (ø)

elliottlib/cli/cli_opts.py
100.00% <0.00%> (ø)

elliottlib/exectools.py
89.39% <0.00%> (ø)

elliottlib/cli/advisory_impetus_cli.py
0.00% <0.00%> (ø)

elliottlib/util.py
40.50% <0.00%> (ø)

elliottlib/cli/rpmdiff_cli.py
0.00% <0.00%> (ø)

elliottlib/assertion.py
80.00% <0.00%> (ø)

... and 33 more

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 9287447...eb1c847. Read the comment docs.


bulk-create for members (for track)

description:
when enabling bulk-create for members,  neutron_lbaas/drivers/f5/driver_v2.py  needs to add:
def create_bulk(self, context, members):
self.driver.f5.member.create_bulk(context, members)

OPENSTACK-2177 for this issue.


Info: Jekyll version of tufte-css

I have just finished modifying my tufte-jekyll repo to incorporate all the recent changes in the tufte-css.
This Jekyll blog version allows a content creator to get all this yummy tufte-css look without having to write a bunch of complicated html. Instead, content is created using Markdown and some custom Liquid tags for the cool Tufte stuff.
There is a demo version here if anyone would like to compare. I have made some modifications to the CSS to bring the typography into more of a Bringhurst-ian vertical scale.
Any suggestions or help are welcome.

:+1: good work!!

Yes, It makes the whole thing usable using Markdown and a few special Liquid tags. For instance:
## Some H2 Heading

Some content with [links](http://somewhere.com) and *emphasis* and **Strong**....
{% marginnote 'mn-id-1'  'Some Marginnote content *with* all the markdown goodness' %}

etc..

Is how content is created.

I have made some modifications to the CSS to bring the typography into more of a Bringhurst-ian vertical scale.

I looked through your documentation but could find no explanation of what you mean by this. I'm somewhat familiar with Bringhurst's work, but am curious what changes you made to achieve a "Bringhurst-ian" vertical scale.

I have adjusted line heights on text elements using the techniques outline on Web Typography so that all text elements have the same vertical rhythm. It amounted to small differences in headings and paragraphs, but where you really notice it is when you look at the longer sidenotes on both versions. You can slap a screen ruler between the paragraph text and the sidenote text, and the baselines on mine will align over multiple lines, where the tufte.css has tighter line spacing.
tufte.css:

versus tufte-jekyll:

Thanks for the explanation, and the image, that's helpful to see the difference. Do you think it would be good to pull your changes back into tufte-css?

Personally, I think it looks a little cleaner that way. I'm not sure who the maintainer is now, but they of course are welcome to incorporate any changes that they feel are improvements.  I started with the tufte.css and scrubbed through all the text elements including table elements, list elements and blockquotes to put them all on the same vertical measure.
On Oct 7, 2015, at 3:31 PM, Nic<EMAIL_ADDRESS>wrote:

Thanks for the explanation, and the image, that's helpful to see the difference. Do you think it would be good to pull your changes back into tufte-css?
—
Reply to this email directly or view it on GitHub.

Cool. @daveliepmann is still the maintainer.

Great thing, :+1: for pulling changes into tufte-css, but not 'as is'. Looks like tufte.css can adopt this nice top navigation, credits footer and other blocks.

The tufte-jekyll theme looks great! I'm working on a template/theme for hugo (another en vogue static-site generator written in go).
However, I think the large leading on the sidenotes looks a bit off-putting. If you insist on maintaining vertical rhythm you could still do so with a more proportional leading: take a look at Mark Boulton's approach (he aligns every 5th sidenote line with a main column line instead of aligning every line).

@crmackay Thank you for working on hugo templates. Looking forward to seeing your work!

I'll take a look at making that sidenote leading an option in the scss file. Thanks for that link.
-Clay
On Oct 15, 2015, at 8:45 AM, Chris MacKay<EMAIL_ADDRESS>wrote:

The tufte-jekyll theme looks great! I'm working on a template/theme for hugo (another en vogue static-site generator written in go).
However, I think the large leading on the sidenotes looks a bit off-putting. If you insist on maintaining vertical rhythm you could still do so with a more proportional leading: take a look at Mark Boulton's approach (he aligns every 5th sidenote line with a main column line instead of aligning every line).
—
Reply to this email directly or view it on GitHub.

Wow, this is awesome! Going to convert my existing jekyll site to this over the weekend.

See https://github.com/edwardtufte/tufte-css/issues/31 for links to other applications.
Since there's nothing actionable on this ticket, I will close it. The information will remain for anyone who looks or asks for Jekyll applications. Thanks.


feat: add connection popover

General description: This pull request is mostly an UI/UX improvement to the connection functionality.
Description: When we want to connect the dashboard to an endpoint it needs some configuration. If some of the configuration setup are wrong the system will shows a popup to reconnect or to go to the documentation. This is not very user friendly as we will need to read the whole documentation to understand that we need to go to the settings to setup the whole config, then go back to the log stream and try again.
Proposal: We can setup basic connection configs from the same connection component (host and port)

It would be nice, if you open an issue before implementing a feature and then linking it to that issue. There are infos on that in the contributing guidelines:
https://github.com/jina-ai/jina/blob/master/CONTRIBUTING.md
It would also be good to write a describtion into your pull request.
What does this pull request do, why does it make sense, etc.

Hello, @BastinJafari
Thx for the replay.
About to create an issue related to the feature. I didn't see any info in the contributing doc and for my understanding not always a feature is resolving an issue. In this case is more an improvement as the system can work without it. It will be more an UI/UX improvement that will make easy for users to use the system. What do think?
About the description I totally agree. I will do it. Thx again.

It would be nice, if you open an issue before implementing a feature and then linking it to that issue. There are infos on that in the contributing guidelines:
https://github.com/jina-ai/jina/blob/master/CONTRIBUTING.md
It would also be good to write a describtion into your pull request.
What does this pull request do, why does it make sense, etc.

Hello, @BastinJafari
Thx for the replay.
About to create an issue related to the feature. I didn't see any info in the contributing doc and for my understanding not always a feature is resolving an issue. In this case is more an improvement as the system can work without it. It will be more an UI/UX improvement that will make easy for users to use the system. What do think?
About the description I totally agree. I will do it. Thx again.

Hey Pablo, could you rebase your PR?
We had to get rid of some broken checks.

Hey Pablo, could you rebase your PR?
We had to get rid of some broken checks.

Hey Pablo, could you rebase your PR?
We had to get rid of some broken checks.

Hey @BastinJafari,
The sync with master is done but still a falling case. Caused by redux it seems.
11:02:16 AM: /opt/build/repo/src/redux/index.ts 11:02:16 AM: TypeScript error in /opt/build/repo/src/redux/index.ts(1,10): 11:02:16 AM: Module '"."' has no exported member 'combineReducers'. Did you mean to use 'import combineReducers from "."' instead?  TS2614

Hey Pablo, could you rebase your PR?
We had to get rid of some broken checks.

Hey @BastinJafari,
The sync with master is done but still a falling case. Caused by redux it seems.
11:02:16 AM: /opt/build/repo/src/redux/index.ts 11:02:16 AM: TypeScript error in /opt/build/repo/src/redux/index.ts(1,10): 11:02:16 AM: Module '"."' has no exported member 'combineReducers'. Did you mean to use 'import combineReducers from "."' instead?  TS2614

Hey @PabloRN, we are currently transitioning from flux to redux. Could you update your implementation to that? You can see a reference in my newest PR

Hey @PabloRN, we are currently transitioning from flux to redux. Could you update your implementation to that? You can see a reference in my newest PR

Hey @PabloRN, we are currently transitioning from flux to redux. Could you update your implementation to that? You can see a reference in my newest PR

Sure! Let me give a quick look and I will back to you

Hey @PabloRN, we are currently transitioning from flux to redux. Could you update your implementation to that? You can see a reference in my newest PR

Sure!


Error whitout user meaning when run kubectl kudo get instances before init

What happened:
After install, I run kubectl kudo get instances
$ kubectl kudo get instances
Error: creating kudo client: operators: customresourcedefinitions.apiextensions.k8s.io "operators.kudo.dev" not found

What you expected to happen:
Not show an error without user meaning. It could provide a friendly message telling that I should run kubectl kudo init in order to have instances.
How to reproduce it (as minimally and precisely as possible):

New installation, and then run the command.

What I see as a solution here is to do some validation before actually creating a client and make sure that the cluster is initialized. Potentially we would want to have that check before many other commands because most of them expect the server to be initialized.

great feedback!!  thanks @camilamacedo86 !


Fixed Dockerfile

I modified the Dockerfile so it can work with the current latest Ubuntu image (16.04).

It seems just better than it was. Thanks!
I do not have writing access on this repo (even if I wrote the original code :D) but I would vote for merging this PR


Add support for linuxParameters

/codefresh run test

@mickdekkers can you please address the comments

@aknysh sorry, I must've missed your earlier messages. I just rebuilt the readme as requested 👍

/codefresh run test

/codefresh run test


Create attributes to nicely describe tests that only work on certain runtimes

Right now we have categories for failing tests, and some tests where the [Fact] attribute is conditionally compiled, but before The Merge we should have a concise, descriptive way to specify that.

Maybe something like
[FullFrameworkFact("Requires GAC")]

Removing this from the great-merge milestone because it's not strictly required (most things I worked around this by using #if around the Fact attribute).

We have this now with [ConditionalFact]/[PlatformSpecific].


Property Identification and Versioning

We need a more robust way to identify properties. So far, just have the property name. This is just a string, and there is no strict requirement of uniqueness. We need a way to attach a unique identifier to properties that remains constant over time.
On a related point, we need a mechanism to version properties. This will be additional metadata that is stored in the Property base class. This mechanism will also include a pre-commit (or pre-push?) hook that denies merges when a modified property does not have its version bumped.

Update: The version information should include a way to recover the commit hash for a version of the source that includes the referenced version of the property (measurement).

I do not think this is needed anymore. Properties are currently seen as more static entities that just define the name and definition of a property. As currently defined, there will not be "versions" of a Property, so no ids, no versions, and no metadata.
These requirements may have moved over to Results or some other entity, but they do not seem valid anymore.


wg-dashboard behind reverse proxy

Heya, was anyone able to set up an nginx reverse proxy for the application?
Furthermore I'd like to change the default port. However when I change them in the two source files I get, the application doesn't seem to respect that.
Any pointers/suggestions? Thanks in advance!

Change the port in dataManager.js server.js and server_config.json

Hey @flying-sausages , sadly we recently decided to deprecate the project due to lack of time :(

THIS PROJECT IS UNMAINTAINED
If you want to take over development please contact us. In the meantime we recommend having a look at:

https://github.com/tailscale/tailscale
https://github.com/subspacecommunity/subspace
https://github.com/EmbarkStudios/wg-ui


Update Samsung Mobile (A35 5G & A55 5G)

Adding the missing A35 & A55 models of Samsung which unfortunately won't have the new seven-year support.


feat: add Admin API TLS client verification support

What this PR does / why we need it:
To make the connection between the controller and the gateways secure, we should allow configuring client verification.
Which issue this PR fixes
Part of https://github.com/Kong/kubernetes-ingress-controller/issues/3833.
Special notes for your reviewer:
I tried to follow a similar pattern that we use for webhook certs.
The modified examples were tested locally. I also verified that providing the caBundle as a blob works as well.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] PR is based off the current tip of the main branch.
[x] Changes are documented under the "Unreleased" header in CHANGELOG.md
[x] New or modified sections of values.yaml are documented in the README.md
[x] Commits follow the Kong commit message guidelines

@rainest I ran two manual tests, let me post them as two separate comments below.

@rainest I ran two tests scenarios, please find the logs/procedure below.
Defaults - no certs provided by the users
# Gateway's values.yaml

admin:
  enabled: true
  type: ClusterIP
  clusterIP: None
  tls:
    client:
      secretName: "admin-api-ca-cert"

ingressController:
  enabled: false

replicaCount: 3

# Controller's values.yaml

deployment:
  kong:
    enabled: false

proxy:
  ## This must match the gateway release's proxy Service name.
  ## The Service name uses the pattern "<release name>-kong-proxy".
  ## In this example, the companion gateway release is named "gw"
  nameOverride: gw-kong-proxy

ingressController:
  enabled: true

  gatewayDiscovery:
    enabled: true
    adminApiService:
      ## This must match the gateway release's admin Service name.
      ## The Service name uses the pattern "<release name>-kong-admin".
      ## In this example, the companion gateway release is named "gw"
      name: gw-kong-admin

  adminApi:
    tls:
      client:
        # Enable TLS client authentication for the Admin API.
        enabled: true
        # We're specifying the name of the secret to have a static name that we
        # will use in the gateway release.
        caSecretName: "admin-api-ca-cert"

  env:
    # This must match the gateway release's proxy Service HTTPs port name.
    kong_admin_svc_port_names: "kong-admin-tls"

# Controller release installation
$ helm upgrade --install controller . -n kong --version 2.17.0 --values ./example-values/minimal-kong-gd-controller.yaml

# Secrets get created
$ k get secrets -n kong
 NAME                                                         TYPE                 DATA   AGE
admin-api-ca-cert                                            kubernetes.io/tls    2      34s
controller-kong-admin-api-keypair                            kubernetes.io/tls    2      34s

# Controller deployment waits for Gateways to be discovered
$ k get deployments -n kong
NAME              READY   UP-TO-DATE   AVAILABLE   AGE
controller-kong   0/1     1            0           2m3s

# Gateway release installation
$ helm upgrade --install gw . -n kong --version 2.17.0 --values ./example-values/minimal-kong-gd-gateway.yaml

# Gateways and Controller become ready
$ k get deployments -n kong
NAME              READY   UP-TO-DATE   AVAILABLE   AGE
controller-kong   1/1     1            1           3m22s
gw-kong           3/3     3            3           33s

# Controller synced config with all Gateways
$ k logs controller-kong-5c5d6f697d-8vpbc -n kong
time="2023-04-07T12:31:11Z" level=info msg="successfully synced configuration to kong" kong_url="https://<IP_ADDRESS>:8444"
time="2023-04-07T12:31:11Z" level=info msg="successfully synced configuration to kong" kong_url="https://<IP_ADDRESS>:8444"
time="2023-04-07T12:31:11Z" level=info msg="successfully synced configuration to kong" kong_url="https://<IP_ADDRESS>:8444"

# Port forward the same port that KIC us
$ kubectl port-forward -n kong deploy/gw-kong 8444:8444

# Calling the endpoint without certs gives 400
$ http --verify=no https://localhost:8444
HTTP/1.1 400 Bad Request
Connection: close
Content-Length: 202
Content-Type: text/html; charset=UTF-8
Date: Fri, 07 Apr 2023 12:35:58 GMT

<title>400 No required SSL certificate was sent</title>

400 Bad Request

No required SSL certificate was sent

# Calling the endpoint with certs gives 200
$ k get secret -n kong controller-kong-admin-api-keypair -o json | jq -r '.data."tls.crt"' | base64 -d > tls.crt
$ k get secret -n kong controller-kong-admin-api-keypair -o json | jq -r '.data."tls.key"' | base64 -d > tls.key
$ http --verify=no https://localhost:8444 --cert tls.crt --cert-key tls.key
HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Connection: keep-alive
Content-Length: 13061
Content-Type: application/json; charset=utf-8
Date: Fri, 07 Apr 2023 12:40:53 GMT
Server: kong/3.2.2
X-Kong-Admin-Latency: 322

Certs provided by the user
# Create a self-signed CA
$ openssl req -x509 -sha256 -days 1825 -newkey rsa:2048 -keyout rootCA.key -out rootCA.crt

# Create client's key
$ openssl genrsa -out tls.key 4096

# Generate CSR
$ openssl req -new -key tls.key -out csr.pem

# Sign the CSR with CA
$ openssl x509 -req -days 9999 -in csr.pem -CA rootCA.crt -CAkey rootCA.key -CAcreateserial -out tls.crt

# Verify client cert with CA
$ openssl verify -CAfile rootCA.crt tls.crt
tls.crt: OK

# Create a secret for Controller
$ k create secret tls --key tls.key --cert tls.crt -n kong admin-api-client-tls-keypair
secret/admin-api-client-tls-keypair created

# Controller's values.yaml

deployment:
  kong:
    enabled: false

proxy:
  ## This must match the gateway release's proxy Service name.
  ## The Service name uses the pattern "<release name>-kong-proxy".
  ## In this example, the companion gateway release is named "gw"
  nameOverride: gw-kong-proxy

ingressController:
  enabled: true

  gatewayDiscovery:
    enabled: true
    adminApiService:
      ## This must match the gateway release's admin Service name.
      ## The Service name uses the pattern "<release name>-kong-admin".
      ## In this example, the companion gateway release is named "gw"
      name: gw-kong-admin

  adminApi:
    tls:
      client:
        # Enable TLS client authentication for the Admin API.
        enabled: true

        # We're providing client certificates in the secret below.
        certProvided: true
        secretName: "admin-api-client-tls-keypair"

  env:
    # This must match the gateway release's proxy Service HTTPs port name.
    kong_admin_svc_port_names: "kong-admin-tls"

# Install Controller
$ helm upgrade --install gw . -n kong --version 2.17.0 --values ./example-values/minimal-kong-gd-gateway.yaml

# Gateway's values.yaml
admin:
  enabled: true
  type: ClusterIP
  clusterIP: None
  tls:
    client:
      # Copy-pasted rootCA.crt contents
      caBundle: |
        -----BEGIN CERTIFICATE-----
        MIICpjCCAY4CCQDDyWXN1NMsSzANBgkqhkiG9w0BAQsFADAVMRMwEQYDVQQDDApr
        b25naHEuY29tMB4XDTIzMDQwNzEyNDUxM1oXDTI4MDQwNTEyNDUxM1owFTETMBEG
        A1UEAwwKa29uZ2hxLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
        AN1Vbedqbq0v4BVPeuKKnk1hDYNpar3ApoLALm3acO71WdZStDcvDTzd+zvRJeqo
        4YFZYFptdfuDaP2PKMeVmWVeKTFntV7n8zkMfx0heQb6kdO3QwtPMwk+krDRTSxI
        3dR6OIitqUYamsqnlu/1vBpNg2xeJR5yLwPpnEoqemJMi42VpOmoz7E3u1slrPGz
        IJsiEizq1dhP8k9VKU6V3QUSkOi9zEfjGVKryjjTP1CdJFHsbopgZEsIDdURvig6
        uC9DTrxMIRVii4k1Fe1BX224nKNPy+XSUO9ORVP/hPwrQBwr8UTxZgxZ6/Hd0Zf1
        RQJRuD+Q35Wk6ivySaWrickCAwEAATANBgkqhkiG9w0BAQsFAAOCAQEAmG3vrY2H
        iGhoK0xZBJORECWQ8zdFSn7JV/bbfC+Dc99HW7VMSNkGwUTY5czz7iEfwuJn+rvX
        2mr/hqBROlor+DsA+V1Qcxt9jpWPlFnloRsayMnarVAzEPXut7nUjvH+p7D+3g7p
        Tl6KRkycYSGSE/dPE2V+/AHLtFQTVhhKzR4nd1ktKFa6hf2iZwfpJnVi/lOr2YFk
        Fm20qz93sMVmB/vVquGsbUAPYixc8bHLENnDznYweSUvg9CFIz9cPW9FbOI80WtI
        Uu1xxtJAQjAB2GyD6QlvM6gLAMu7LdP9ht94xi/0UtkOghumrrdqyEw6qoiOojAJ
        7xxqjJgL8WOvGg==
        -----END CERTIFICATE-----

ingressController:
  enabled: false

replicaCount: 3

# Install Gateway
$ helm upgrade --install gw . -n kong --version 2.17.0 --values ./example-values/minimal-kong-gd-gateway.yaml

# Both deployments become ready
$ k get deployments -n kong
NAME              READY   UP-TO-DATE   AVAILABLE   AGE
controller-kong   1/1     1            1           6m5s
gw-kong           3/3     3            3           2m59s

# Controller synced config with all Gateways
$ k logs -n kong controller-kong-544f5bcb75-bsgp5
time="2023-04-07T13:08:39Z" level=info msg="successfully synced configuration to kong" kong_url="https://<IP_ADDRESS>:8444"
time="2023-04-07T13:08:39Z" level=info msg="successfully synced configuration to kong" kong_url="https://<IP_ADDRESS>:8444"
time="2023-04-07T13:08:39Z" level=info msg="successfully synced configuration to kong" kong_url="https://<IP_ADDRESS>:8444"

# Port forward the same port that KIC uses
$ kubectl port-forward -n kong deploy/gw-kong 8444:8444

# Calling the endpoint without certs gives 400
$ http --verify=no https://localhost:8444
HTTP/1.1 400 Bad Request
Connection: close
Content-Length: 202
Content-Type: text/html; charset=UTF-8
Date: Fri, 07 Apr 2023 13:09:54 GMT

<title>400 No required SSL certificate was sent</title>

400 Bad Request

No required SSL certificate was sent

# Calling the endpoint with certs gives 200
$ http --verify=no https://localhost:8444 --cert tls.crt --cert-key tls.key
HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Connection: keep-alive
Content-Length: 13061
Content-Type: application/json; charset=utf-8
Date: Fri, 07 Apr 2023 13:10:21 GMT
Server: kong/3.2.2
X-Kong-Admin-Latency: 15


Support publishing and loading node presets

Changelog Description
Fixes https://github.com/ynput/ayon-houdini/issues/68, This PR Implements publishing and loading node presets.
A node preset is simple serialization of subset of values on ROP node
There are still some edge cases to handle (e.g. animated parameters) and some code improvements, but that doesn't affect reviewing the suggested workflow, shown in the demo video below.
Additional info
Render setups in Houdini can be

a collection of nodes (you can call it: a scene fragment, or a part of a node graph)
This is partially solved by publishing HDAs as we can publish HDAs from different Houdini contexts.
Also, we can use CPIO  which should work in a similar manner as publishing node presets.
a node preset of my render rop node. (which is solved by this PR)

Additional info 2
The new recopies system is an alternative solution to creating the node preset json file ourselves.
But, this is a topic for the future as it's only supported in Hou 20.5
https://www.sidefx.com/docs/houdini/network/recipes.html
Demo
https://github.com/user-attachments/assets/df1ee571-07c4-4351-b5ca-a86b64a475d1
Testing notes:
Publishing:

Create a node preset
Update Source node parameter
Publish
Loading:
Load a preset through the loader
Mange its version via inventory
Update target node parameter
Click Apply Preset

Just noting there that this started from a client request but was put on hold for now - potentially in favor of Houdini 20.5+ Recipes in the future.

After some discussion, we decided to close this PR in favor of Houdini 20.5+ Recipes.


Failed to archive link: UnicodeEncodeError: 'gbk' codec can't encode character '\u25be' in position  9443: illegal multibyte sequence

similar with #32, but it happens when archiving the site:

I think this is a different issue, can you share what the URL is that you tried to archive?
Also please post the full output of archivebox --version.

I think it's due to windows not defaulting to UTF-8 for file writes.
There's a PEP to fix it, but it's not proposed to land until 3.10: https://discuss.python.org/t/pep-597-enable-utf-8-mode-by-default-on-windows/3122
In the meantime can you try setting the PYTHONLEGACYWINDOWSSTDIO=utf-8 environment variable and running it again.
Related issue: https://github.com/ArchiveBox/ArchiveBox/issues/678


Transcript window should have option to be hidden

There should be an option to hide the transcript reader.

@caseyedavis12. Screenshots below. Let me know if you'd like to tweak anything! If not, I can submit a PR.
Open (default open)

Closed

@jasoncorum this looks great to me!

What's the bit about...

Translates to br in html: self closing tags can be parse problems.

...?


fix: improve watching experience for generated files

Types of changes

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

Description
Nuxt has a frustrating DX issue when a page file is deleted or renamed. Webpack starts to rebuild as soon as the file is changed while still generated files (like .nuxt/router.js) are referring to the old file. This is happening because we debounce generateRoutesAndFiles function (also there is a little generation/fs process time) but webpack rebuilds as soon as possible. Causing a failing intermediate build like this:

This PR set a longer default for aggregateTimeout (200ms + ~800ms of generating process). That fixes the problem in normal cases when generation takes less than 800ms: (previously deadline was ~100ms)

Webpack watch will be also suspended during generate files and resumed/invalidated thanks to pausing/resume introduced webpack/webpack#9214 (@jkzing :heart:)
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Codecov Report

Merging #6257 into dev will decrease coverage by 0.07%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##              dev    #6257      +/-   ##
==========================================
- Coverage   95.72%   95.65%   -0.08%
==========================================
  Files          80       80
  Lines        2666     2668       +2
  Branches      687      687
==========================================
  Hits         2552     2552
- Misses         98      100       +2
  Partials       16       16

Flag
Coverage Δ

#e2e
100% <ø> (ø)
:arrow_up:

#fixtures
50.59% <0%> (-0.04%)
:arrow_down:

#unit
92.35% <0%> (-0.07%)
:arrow_down:

Impacted Files
Coverage Δ

packages/config/src/config/_common.js
100% <ø> (ø)
:arrow_up:

packages/webpack/src/builder.js
90.62% <0%> (-1.93%)
:arrow_down:

Continue to review full report at Codecov.

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

Expecting the strange failing test 🤔
Awesome PR :)


Capacity Type Distribution

Some application deployments would like the benefits of using Spot capacity, but would also like somewhat of a stability guarantee for the application. I propose a capacity-type percentage distribution of the k8s Deployment resource.  Since Capacity-Type is likely to be implemented at the cloud-provider level, this too would need to be at the cloud-provider layer.
For example:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: inflate
spec:
  replicas: 10
  template:
    metadata:
      labels:
        app: inflate
        node.k8s.aws/capacity-type-distribution/spot-percentage: 90
    spec:
      containers:
      - image: public.ecr.aws/eks-distro/kubernetes/pause:3.2
        name: inflate
        resources:
          requests:
            cpu: "100m"

The above deployment spec would result in the deployment controller creating Pods for the 10 replicas. Karpenter would register a mutating admission webhook which would check if the pod's deployment spec has these labels and then check any current pods belonging to the deployment to determine which capacity-type label to apply. The pod resource after the admission webhook would look like this:
apiVersion: v1
kind: Pod
metadata:
  labels:
    app: inflate
    pod-template-hash: 8567cd588
  name: inflate-8567cd588-bjqzf
  namespace: default
  ownerReferences:
  - apiVersion: apps/v1
    kind: ReplicaSet
    name: inflate-8567cd588
spec:
  containers:
  - image: public.ecr.aws/eks-distro/kubernetes/pause:3.2
    name: inflate
    resources:
      requests:
        cpu: "100m"
  schedulerName: default-scheduler
  nodeSelector:
      node.k8s.aws/capacity-type: spot

^^ duplicated 8 more times, and then:
apiVersion: v1
kind: Pod
metadata:
  labels:
    app: inflate
    pod-template-hash: 4567dc765
  name: inflate-4567dc765-asdf
  namespace: default
  ownerReferences:
  - apiVersion: apps/v1
    kind: ReplicaSet
    name: inflate-4567dc765
spec:
  containers:
  - image: public.ecr.aws/eks-distro/kubernetes/pause:3.2
    name: inflate
    resources:
      requests:
        cpu: "100m"
  schedulerName: default-scheduler
  nodeSelector:
      node.k8s.aws/capacity-type: on-demand

My first thought is that this webhook should be decoupled from Karpenter's core controller. Maybe something plugged into aws cloud provider once we break it apart?

My first thought is that this webhook should be decoupled from Karpenter's core controller. Maybe something plugged into aws cloud provider once we break it apart?

Yeah, I think that makes the most sense.

We have one application that has been testing this out using ASGs with mixed purchasing options(on-demand and spot). This one application is using this:
https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-mixed-instances-groups.html
In the future it would be great to find a mechanism to migrate this ASG to karpenter.

Two (maybe random) questions.
Should node.k8s.aws/capacity-type-distribution/spot-percentage be an annotation instead of a label?
Now that we'd have 2 separate deployments how would that work with HPA? How would it know which deployment to scale and keep the total application deployment balanced?

+1

We may also think how to leverage the current topology constraints instead of new annotations

We've discussed expanding the topologyspreadconstraints concept to include percent based spread. I think this is a perfect fit.

+1

Any updates please

+1

Hey folks, just a reminder to 👍 the original issue, rather than +1 in the comments, since it's easier for us to sort issues by most upvoted.

Any update please.

I've documented another method for this at https://karpenter.sh/preview/tasks/scheduling/#on-demandspot-ratio-split that may work for some.

👍

+1

@tzneal
This is the correct link for on-demand x spot ratio split
https://karpenter.sh/preview/concepts/scheduling/#on-demandspot-ratio-split


Feature request: Turn-Rate Control (Flight Mode)

Some gliding vehicles, particularly steerable parachutes, offer only yaw and pitch control for steering, rather than the roll and pitch provided by fixed-wing aircraft. Furthermore, the response of a parafoil to braking (yaw) inputs is highly nonlinear with altitude and airspeed, and generally under-actuated. As a result, steering a parachute according to target roll and pitch angles doesn't really work.
A simpler solution is to ignore roll and pitch angles altogether, and just actuate to a target turn rate. An outer loop must then "plan ahead" to request a turn at a rate that can be supported by the vehicle, that also intercepts the waypoint.
There are two use cases where fixed-wing aircraft can also benefit from actively-controlled turn rates: the dreaded, "two-minute hold" loiter, and the maneuvering seen in controlled approaches for landing. In both of these cases the heading change is rate-controlled, but the radius of the resulting turn depends upon the airspeed of the vehicle.
FEATURE DESCRIPTION: a flight mode where the strategy is "do whatever actuator output is necessary to maintain a N-degree/sec heading change".
Note that this feature is NOT Acro mode, because roll and pitch are determined by the requested heading change rate; in Acro mode, roll and pitch rates ARE the targets.
Respectfully submitted,
Bill Gatliff
<EMAIL_ADDRESS>

Bonus points for "achieve a heading of M-deg at a rate of N-deg/sec".

@bgat We're implementing right now "task flight modes" which is essentially an abstract interface which let's you run an instance of a custom class completely take over control, while still taking care of all the system complexity in entering and exiting the mode. So this is entirely possible - what is the timeline you'd like to see that in?

My test vehicle won't be ready for a month, but probably will want to do some test flying shortly after that. In the meantime, if the opportunity arises I have a Flyzone Calypso on hot-standby. :-)
Where can I track the progress of your development?
Finally, I'm assuming that what you're talking about delivering near-term is the task flight-mode capability, but I'd need to provide the custom class that uses it to do controlled-rate turns?

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 30 days. Feel free to reopen this issue if you deem it appropriate.
(This is an automated comment from GitMate.io.)


Hello, how to get the entropy_list? Is the entropy_get code open source?

Currently, I do not have the code that calculates entropy.
Basically, I calculated an entropy value for an example using the Shannon's entropy:
the negative value of the summation of p_i * log(p_i), where p_i is a single logit value within a logit vector obtained by model forward process and i is iterated from 0 to the number of classes - 1.


Enhancement request: Add ability to order templates alphabetically

Our libraries are using three sizes of labels and for each size there are several template variants, We prefix our templates with L, M and S (for Large, Medium and Small label size) and every now and then we need to add a new template to address some need at one of the libraries.
When creating an new template, Spineomatic appends the new layout to the list of available layouts, it would be great if we could order the list alphabetically so that e.g. all L templates are grouped together, all S templates grouped together etc.
Regards,
Helgi

Alphabetically templates/layouts available in the v1.3.7-beta version. To try the beta, click the "i" (information) icon on the SpineOMatic tile in the "Cloud App Center" in Alma, then click the "Try v1.3.7-beta" link.
Please add feedback/comments to this issue. Thank you.

Available in v1.3.7.


[stable/redmine] add user defined env to redmine deployment

It's helpful to pass env vars, to enable debugging of bitnami tools.

@scottrigby you got it

/ok-to-test


Hardware back button doesn't close drawer menu

Expected behaviour
I would like to close drawer menu (left sidebar) after tap on hardware back button.
Actual behaviour
After tap hardware back button is called only Actions.pop and I see previous scene, but menu drawer component is still visible.

For me It works for expected on version
"react-native-router-flux": "^4.0.0-beta.15",
"react-native": "0.46.4",

Where may I find the solution for this issue?

Please check latest beta.17, it should work.


Unable to auto update since 3.15.3

Hi,
Good day! Great app there! 🙏 Thank you.
Since the above version, auto update doesnot happen. I get the following errors. Hope this helps.

I am Windows 10 Pro 64 bit (21H2 19044.2006) if that helps. Assuming an issue with that particular version, I fully installed 3.15.5 and today when I saw the update, tried auto updating and again saw the above errors. Hence reporting.

Hi @reddyshyam,
Thank you for reporting.  I don't have a Win 10 machine but I will setup a VM to try to replicate the issue.  However, I did try a new install of v3.15.3 and v3.15.5 on my Windows 11 and macOS machines.   Both updated to latest version without issues.
Are you behind a proxy server or a VPN by any chance?  I haven't run into this issue before so I am thinking if it is a network issue on your end.

OK.  Let me dig a little deeper into it.  It takes me a few minutes to setup a VM so not a big deal for me. Hopefully I can replicate the issue and find the root cause.

No. The app is built using Electron which includes its own Chromium and Node.js (that's why the app size is 80+ MB).  It does not depend on any external browsers.

No. The app is built using Electron which includes its own Chromium and Node.js (that's why the app size is 80+ MB). It does not depend on any external browsers.

Oh! Any way to clear its cache?

You can try an app reset as shown below.  Reinstalling the app should also clear the cache.  To be sure, you can try uninstalling the app and doing a clean install of v3.16.0 and then see if it auto updates to 3.16.1?

You can try an app reset as shown below. Reinstalling the app should also clear the cache. To be sure, you can try uninstalling the app and doing a clean install of v3.16.0 and then see if it auto updates to 3.16.1?

I can do un-install and re-install but I will lose my settings. Is there any way, I can export and import the settings back?

I tried removing and fresh installation of 3.16 and tried auto update. For some reason update gets really slow, eventually it hit 100% and then this above errors pop up. I cleared then error and surprisingly restart option came up. Finally I could auto update. :)
Not sure why it takes couple of minutes to download an update though. I am on a 100mbps line and 1GB file downloads in less than 5 minutes. So net speeds is not an issue.

Hi @reddyshyam,
I was not able to replicate the issue on Windows 10 VM machine.  However a quick search came up with the following:
https://github.com/electron-userland/electron-builder/issues/4987 for the initial issue you reported. This seems to be rare I think.  I can try to patch it with he solution proposed there but I am hesitant and wonder if it would cause other issues since it has worked pretty well for me and others for a while now.
Slow download issue is here: https://github.com/electron-userland/electron-builder/issues/5537.  Some are suggesting having too many releases slows down the downloads.  Not sure why that could be but I will remove most of the older releases (there are 100 of them) and see if that makes a difference.

Hi @reddyshyam, I was not able to replicate the issue on Windows 10 VM machine. However a quick search came up with the following:
electron-userland/electron-builder#4987 for the initial issue you reported. This seems to be rare I think. I can try to patch it with he solution proposed there but I am hesitant and wonder if it would cause other issues since it has worked pretty well for me and others for a while now.
Slow download issue is here: electron-userland/electron-builder#5537. Some are suggesting having too many releases slows down the downloads. Not sure why that could be but I will remove most of the older releases (there are 100 of them) and see if that makes a difference.

@bornova, that looks like the case with us but please do not do anything or delete the releases. Mine looks like isolatated incident and can always re-install a new update. No point wasting your time on this one.
Thanks again. 👍

Sounds good.  Thanks for the feedback and let me know if you have any other questions.


Add memory_get_offset to simplify data offset constants.

This should not change behavior. I just did not understand the 4 huge constant initializers, and after disassembling the long lines found they were all sharing the exact same logic. I hope this new version is easier to understand.
It is questionable whether it wouldn't be more appropriate to formally declare SIZE, ELEMENT and DATA in some kind of struct, and just let the compiler handle alignment, but this is outside the scope of this PR.

I changed the interface to non-template, instead evaluating address and alignment outside the function. I think this is better because it makes fewer assumptions.

Maybe move it outside the global scope inside the class to call it like Memory::get_offset ?

I had it in the Memory scope at first, it seems like static class functions cannot be truly constexpr. At least it refused to compile as such from my end, with a less than helpful error message:
./core/os/memory.h:63:26: error: constexpr variable 'ELEMENT_OFFSET' must be initialized by a constant expression
   63 |         static constexpr size_t ELEMENT_OFFSET = mem_aligned_address(SIZE_OFFSET + sizeof(uint64_t), alignof(uint64_t));
      |                                 ^                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./core/os/memory.h:63:43: note: undefined function 'mem_aligned_address' cannot be used in a constant expression
   63 |         static constexpr size_t ELEMENT_OFFSET = mem_aligned_address(SIZE_OFFSET + sizeof(uint64_t), alignof(uint64_t));
      |                                                  ^
./core/os/memory.h:57:26: note: declared here
   57 |         static constexpr size_t mem_aligned_address(size_t address, size_t alignment) {
      |                                 ^
./core/os/memory.h:64:26: error: constexpr variable 'DATA_OFFSET' must be initialized by a constant expression
   64 |         static constexpr size_t DATA_OFFSET = mem_aligned_address(ELEMENT_OFFSET + sizeof(uint64_t), alignof(max_align_t));
      |                                 ^             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./core/os/memory.h:64:60: note: initializer of 'ELEMENT_OFFSET' is not a constant expression
   64 |         static constexpr size_t DATA_OFFSET = mem_aligned_address(ELEMENT_OFFSET + sizeof(uint64_t), alignof(max_align_t));
      |                                                                   ^
./core/os/memory.h:63:26: note: declared here
   63 |         static constexpr size_t ELEMENT_OFFSET = mem_aligned_address(SIZE_OFFSET + sizeof(uint64_t), alignof(uint64_t));
      |                                 ^


Top level menu's sub menu disabled

This bug occurs in only multi-content editor.
bug detail

 Tool bar's 'save' and 'save all' item is enabled when editor's some content is changed
 But, Top level menu's 'save' and 'save all' item is not enabled.

bug step

 1. create 'test.svgx' file in IDE
 2. open 'test.svgx' file with 'Multi content example' editor
 3. draw line (make dirty)
 4. check, tool bar's 'save' and 'save all' item enable
 5. check, top level menu's 'save' and 'save all' item enable

 step 5 abnormal behavior('save' and 'save all' item disabled)

analysis

editors/vialble-menu-item.js

if viewer is null then deferred.resolve never called.

bug code...
    function getItemsUnderEdit() {
        logger.info('getItemsUnderEdit()');
        var items = {};
        var deferred = new Deferred();
        var part = _getCurrentEditorPart();
        if (part) {
            var viewer = part.getViewer();
            if (viewer) {
                items = viewer.getMenuItemsUnderEdit(items, menuItems, deferred);
            }
        } else {
            deferred.resolve(items);
        }
        return deferred;
    }

fixed code
https://github.com/webida/webida-client/pull/801

Please refer to #254

Solved in #834


fix group transitive dependency checking

if a group isn't found in the lockfile then its transitive dependencies should be the empty set.

fixes #1476

Very cool. Thanks


[Site-support-request/nate] Add new extractor

Checklist

[ x ] I'm reporting a new site support request
[ x ] I've verified that I'm running youtube-dl version 2021.06.06
[ x ] I've checked that all provided URLs are alive and playable in a browser
[ x ] I've checked that none of provided URLs violate any copyrights
[ x ] I've searched the bugtracker for similar site support requests including closed ones

Example URLs

Single video: https://tv.nate.com/clip/4282848?list=popular&type=ALL
Single video: https://tv.nate.com/clip/4283073?list=popular&type=ALL

Description

This is another NextJS/React site and all the required information is in JSON inside the <script id="__NEXT_DATA__" type="application/json"> element (together with public metadata in the <head>).

Ok, I'll check. Thank you :)

Hi I'm having a look at this site and I could not see any obvious video URL inside the <script id="__NEXT_DATA__" element mentioned above. After poking around a bit with an intercept proxy and React Devtools I found that one can access the video URL through the smcUriList dictionary element but this seems to be generated on the fly with JavaScript.  There doesn't seem to be an obvious JSON that can be extracted to get this URL list.
@dirkf is there a way to run/deal with JavaScript code in Youtube-dl? If there is could you point me to some examples so I can investigate further?

I've figured it out. Opening a PR soon.

Yes, and also the yt-dlp extractor derived from it.


[Exception][iOS] Bug Report

Describe the Bug
Firebase crachlaytics could detect exception EXC_BAD_ACCESS in displayListQueue.
Screenshots

Platform/Framework Info

Device: [iPhone 14 PLus]
OS: [iOS 17.6.1]
Application Framework [Native UIKit-based ]
Clarity Version [1.0.0]

Thanks @ghadeermohameedelmahdy for reporting the issue. Similar crashes were fixed in more recent Clarity versions. Could you please upgrade to Clarity version 2.1.2 and let us know if it eliminates these crashes?

We haven't heard back from you in a while regarding trying the latest version. We'll close this issue for now, but please feel free to reopen it if you have any further questions or need additional assistance.


SelectEntityActionSpace

While working on the PPO implementation, I realized the SelectEntityActionSpace is extra tricky to work with because the number of choices will be different for each entity. This means we cannot easily combine all logits in a single batch into a tensor that can be passed to the torch Categorical. Just looping over all entities turned out to be unusable slow in the case of categorical actions (not entirely sure why but the torch Categorical object seems to have very high overhead). In addition, calculating the logits cannot easily be done in a batched manner either since it requires a ragged outer product operation. I think ultimately we will need to write some triton kernels for ragged outer product and ragged softmax operations. Until then, it would still be good to have a workable solution that's reasonably performant. I can think of two approaches:

Just loop over each observation in a batch and try and make it reasonably efficient somehow. It could be that e.g. just replacing the torch Categorical with our own implementation and computing everything CPU-side would give us acceptable performance.
Pad everything out to a fixed maximum number of selectable entities.

If you have many entities with different action spaces (for example in micro-RTS and some griddly envs) typically you can deal with this by flattening out all the possible actions into a single action space, and then masking off the things that are not possible for specific entities, it means you can send batches to the Categorical rather than iterating over each one per different entity.


Closing out sprint

This documentation is not clear on how the sprints are closed. I'm assuming its automatic, based on the current write up. It would be good to understand what the exact rules are for sprints to close.
[Enter feedback here]

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

ID: fcbeeb04-899a-4915-798f-9d6285c535ca
Version Independent ID: c23d061e-9544-ec2b-c870-6802dbc44fb2
Content: Track progress and individual items on the Taskboard - Azure Boards and TFS
Content Source: docs/boards/sprints/task-board.md
Product: devops
Technology: devops-agile
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@sandeepantony - Thank you for the feedback. You are correct, there is no explicit guidance on closing a sprint. Nothing occurs automatically at the end of a sprint. You must manually update incomplete work items to a new iteration path and archive older sprints if you want to declutter your Iteration Path list as suggested in Define iteration paths (sprints) and configure team iterations, Archive iteration paths.
I will add an item to my backlog to provide more guidance in this area.

@sandeepantony - Thank you for the feedback. You are correct, there is no explicit guidance on closing a sprint. Nothing occurs automatically at the end of a sprint. You must manually update incomplete work items to a new iteration path and archive older sprints if you want to declutter your Iteration Path list as suggested in Define iteration paths (sprints) and configure team iterations, Archive iteration paths.
I will add an item to my backlog to provide more guidance in this area.

Thank you!


⚠ Bofrost.lu has degraded performance

In 712e35b, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1311 ms

Resolved: Bofrost.lu performance has improved in de62c18.


feat(log): allows zero and negativ values

There are problems when using axis of type 'log' with zero and negative values.
This change allow zero and negative values, when useing type 'log' for an axis.
src/coord/axisAlignTicks.ts and src/scale/Log.ts will use log() as mathLog from src/util/math.ts.

Logarithms of zero and negative numbers are not defined in the real numbers. So I don't think it's proper to support this.

I understand this. It was the minimal change to support it.
What about going deeper, and change only the functions where the special handling is needed ?
scale/Log.ts:{setExtent,unionExtent,contain,normalize}
coord/axisAlignTicks.ts:alignScaleTicks
If yes, how should it be done ? create a function ?  programm it out ?
if using a function, how should it be named ?
regards.

After thinking about it ...
What about naming the function in util/math.ts 'symlog' or 'synmetricLog' and use it only where it's  needed in:
scale/Log.ts:{setExtent,unionExtent,contain,normalize}
coord/axisAlignTicks.ts:alignScaleTicks
regards.

Could you be more specific about in what scenerio do you need this feature?

I will prepare an example.

balance.txt
Here the example. The chart is more compact with 'log'.
I found some other problems, so the MR is not so good, I will change it.
regars


[Feature Request] Loading Indicator

I sometimes have the problem that the map doesn't update properly anymore. I then have to relog form time to time. If the app had a visual indicator for updating, I could know when to need to relog.

2nd'd. Maybe a more general 'activity' indicator? Would give nice warm fuzzys that the app is doing something.

The app does have a visual indicator, if you enable Scanned Locations you'll be able to watch the App as it scans the area. if all the circles begin turning red with no new green ones showing up then you know it's stopped scanning.

I've enabled 'scanned locations', but see no difference (no circles anywhere). FWIW, I only have 'pokemon' enabled, not gyms or stops. I also have a number of pokemon excluded.

The green circles are working for me in 0.1.3 too. It's a little to obstructive for my taste.

And... after starting in 0.1.3 -- not seeing the circles, reverting to 0.1.2 -- and seeing them, then progressing back to 0.13 -- and still seeing them now ... I don't really know what to think. Perhaps there was some sort of init code for the circle drawing that was in 0.1.2 and not in 0.1.3? Strange...
In any case, I found my 'visual indicator'.


Logical definition of GO:0099186 ('structural constituent of postsynapse') needs fixing

Currently:
'structural molecule activity' and ('part of' some 'postsynapse organization') and ('occurs in' some 'postsynapse assembly')

should be:
'structural molecule activity' and ('part of' some 'postsynapse organization') and ('part of' some 'postsynapse assembly')

('postsynapse assembly' is a biological process -> occurrent. occurs in has range 'independent continuant')
@cmungall @dosumis

Close ?

I mean, you can close it if you merge the PR https://github.com/geneontology/go-ontology/pull/17677
I am not allowed to do so :P

'postsynapse assembly' is a 'postsynapse organization'
Do we really need 'structural constituent of postsynapse' to be child of both ?
Also, structural constituents should not be involved in assembly, or not necessarily, should they?
'structural constituent of presynapse' only has
'structural molecule activity'
and ('part of' some 'presynapse organization')
While we're at it, can we add a reference for this term ? There are no annotations, so it's hard to tell what it's intended for. Sounds like a CC converted to a MF. Again, comparing with the presynapse term, it seems like we meant 'scaffold', which we have recently merged with 'signaling adaptor activity' (GO:0035591). Would it make sense to move these two terms under there ?
Thanks, Pascale

This is a question for @dosumis
I don’t know any of the biology. Just the ontology police :P

Maybe open a new ticket to go over the structural constituent branch, both
w.r.t. use cases, and having a consistent DP?
On Mon, Aug 5, 2019 at 10:15 AM Nico Matentzoglu<EMAIL_ADDRESS>wrote:

This is a question for @dosumis https://github.com/dosumis
I don’t know any of the biology. Just the ontology police :P
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/geneontology/go-ontology/issues/17676?email_source=notifications&email_token=AAAMMON3KSNCTPR4I2QZSSDQDBM3FA5CNFSM4IJEUFY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3SONVY#issuecomment-518317783,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAMMOPKM2Q27CHRB5U3E33QDBM3FANCNFSM4IJEUFYQ
.

There are no annotations, so it's hard to tell what it's intended for. Sounds like a CC converted to a MF.

IIRC this was one of a set of terms requested by SynGO to annotate proteins required for the structural integrity of synapses and their components.  There are many known structual components of the synapse, so surprising if no annotations. Are the SynGO annotations being kept up to date?
Re patterns:
I'm responsible for the  "'structural molecule activity' and ('part of' some 'fu organization')" pattern.  I think it makese sense and means that the classification automatically tracks the organization branch, which in turn automatically tracks CC.

'postsynapse assembly' is a 'postsynapse organization'
Do we really need 'structural constituent of postsynapse' to be child of both ?

Agree - probably best to just keep it to 'postsynapse organization' and drop the assembly bit.


docs: update readme with injection/version bump

Signed-off-by: Matthew Rose<EMAIL_ADDRESS>

Codecov Report

Merging #41 (ae892a9) into main (ac28626) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #41   +/-   ##
=======================================
  Coverage   98.90%   98.90%
=======================================
  Files           5        5
  Lines         274      274
=======================================
  Hits          271      271
  Misses          2        2
  Partials        1        1

Flag
Coverage Δ

unittests
98.90% <ø> (ø)

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

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 ac28626...ae892a9. Read the comment docs.


feature(zp): fix replay bugs

Description
Related Issue
TODO
Check List

[ ] merge the latest version source branch/repo, and resolve all the conflicts
[ ] pass style check
[ ] pass all the tests

This PR has been merged manually.


New --include-extended-types changes seems to break --additional-symbol-graph-dir

Prior to version 1.2, we were generating our docs using additional-symbol-graph-dir.
This is how we built the symbol graph:
sh("swift",
    "build",
    "--target", "RevenueCat",
    "--configuration", "debug", # Necessary for debug-only symbols
    # Build for iOS instead of the default macOS. This ensures that iOS-only symbols are included in the docs.
    "-Xswiftc", "-sdk", "-Xswiftc", sh("xcrun", "--sdk", "iphonesimulator", "--show-sdk-path").strip!,
    "-Xswiftc", "-target", "-Xswiftc", "x86_64-apple-ios#{ios_version}-simulator",
    "-Xswiftc", "-emit-symbol-graph",
    "-Xswiftc", "-emit-symbol-graph-dir",
    "-Xswiftc", ".build")

I updated the plugin to 1.2 to be able to use --include-extended-types now so that we can document our extensions. However, generating symbols fails now:
[207/229] Emitting module RevenueCat
<unknown>:0: error: error opening '.build/RevenueCat.symbols.json' for output: No such file or directory
<unknown>:0: error: error opening<EMAIL_ADDRESS>for output: No such file or directory
<unknown>:0: error: error opening<EMAIL_ADDRESS>for output: No such file or directory

Checklist

[ ] If possible, I've reproduced the issue using the main branch of this package.
[x] This issue hasn't been addressed in an existing GitHub issue.

Expected behavior
I expected our swift build command to continue working
Actual behavior
Build fails.
Swift-DocC Plugin Version Information
Swift-DocC plugin version: 1.2.0
Swift Compiler version:
swift-driver version: 1.75.2 Apple Swift version 5.8 (swiftlang-<IP_ADDRESS>.2 clang-14<IP_ADDRESS>.100)
Target: arm64-apple-macosx13.0

Actually it appears that was happening because of an invalid reference to SwiftUI in the target. I removed that, and now it seems like I'm close to getting this working.
However it seems like I'm missing something in how I'm creating the symbol graph, since this is what I get when calling swift package preview-documentation:
Error: Mixing symbol graph files with and without extension declarations is not supported.

I couldn't find any documentation on this. Do I need a new argument to the swift build call to add extension declarations?

Did you get any further on this, @NachoSoto? For me it's failing on building documentation for my vapor backend using fluent-kit.

Nope, and no word from Apple

This seems to be relevant?: https://github.com/apple/swift-docc/pull/715
In the mean until Swift 5.10 I found DOCC_EXTRACT_EXTENSION_SYMBOLS set to NO works fine for my project. I don't know about Vapor though.

@NachoSoto did you get anywhere on this? Looks like you're at RevenueCat (?) and I see the docs do seem to be for iOS with support objective-c too. Any tips on how you're generating this?

This was 2 years ago, I barely remember haha


Update setup.py

This fixes the dependancies required for the Webapp

alright, so dbus-python seems to be depricated and is just causing problems for Ubutnu 22.0.4, so i found its replacement, dbus-next, works exactly the same, just with supported install. See if that works with bluez, because I don't have an external dongle. Worked in my vitrual machine though

Again, thanks for taking the time to adjust the PR!
One last thing before merge: It looks like your rebase has affected previous commits in the repo (note how your branch now says that it's 40 commits ahead of master instead of 2). Ideally, a proper squash or rebase will only result in your authored commits changing.
At this point, it may just be easiest for you to copy out the changed files, reset the branch back to parity with master, commit the files back, and force push again so that we get a clean history.

Ok I can't figure out how to do that, so I'm going to copy the changed files, and delete the whole branch, because it's too much of a hassle. Afterwards I'll just open a new pull request. Less commits.


Unexpected display error on tabs with focus mode on

Is the bug present when using the default Obsidian theme?
No
Is the bug present when snippets and plugins are disabled?
Yes
Minimal theme version
6.1.11
Describe the bug

Debug info
SYSTEM INFO:
Obsidian version: v1.0.3
Installer version: v1.0.0
Operating system: Darwin Kernel Version 22.2.0: Mon Nov 14 23:08:10 PST 2022; root:xnu-8792.61.2~6/RELEASE_X86_64 22.2.0
Login status: not logged in
Insider build toggle: off
Live preview: on
Legacy editor: off
Base theme: light
Community theme: Minimal
Snippets enabled: 0
Restricted mode: off
Plugins installed: 3
Plugins enabled: 3
1: Minimal Theme Settings v6.1.0
2: Advanced Tables v0.18.0
3: Mind Map v1.1.0
RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

The right sidebar icon would be hidden mistakenly as well.

I am not able to reproduce this


Cannot autoload iispowershell

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Re
source Statement, Evaluation Error: Error while evaluating a Resource Statement, Could not autoload puppet/type/iis_pool
: Could not autoload puppet/provider/iis_pool/powershell: no such file to load -- puppet/provider/iispowershell at /etc/
puppetlabs/code/environments/production/site/profile/manifests/iisdefault.pp:4:3 on node coolplace-redacted.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

Looks related to https://tickets.puppetlabs.com/browse/PUP-4450
Fix seems is to be to wait for the code to be loaded in the pool (?) or to change the requires like so:
-require 'puppet/provider/iispowershell'
+require File.dirname(__FILE__) + ' /../iispowershell.rb'
 require 'json'

This may have been a false alarm, as I seem to have been running two of the same module somehow? Anyways, closing as I havent been able to reproduce.


Devops 105

This is wrt. https://issues.serokell.io/issue/DEVOPS-105
cc @domenkozar, @int-index

At least if fails now :)

I already did it here: https://github.com/input-output-hk/cardano-sl/pull/330
Now the problem is that Travis fails with Out of Memory while building ether.

@int-index if you're working on one of our issues, please assign yourself and leave a comment so we don't duplicate work :)

Sorry, I'm still new to YouTrack, I thought that an open GitHub pull request would be noticeable enough. Next time I'll leave a comment when I open a PR.

Closing as #330 was merged


Add support for whitelabels

Le problem

Currently, only bookings from "kiwicom" brand are loaded

Le goal:

Fetch bookings according to current brand settings to support whitelabeled partners.

Probably requires update on GraphQL server

Cancelled


Auto population owner even if @key is set to 'owner'

Describe the bug
Similar issue was solved by @yuth on https://github.com/aws-amplify/amplify-cli/pull/4382
I hope this well be fixed too.
Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
To Reproduce
type UserMeta @model @key(fields: ["owner"]) @auth(rules: [
    { allow: public, operations: [read] },
    { allow: owner },
    {
        allow: groups,
        groups: ["Admins"],
        operations: [read, update, delete]
    }
]) {
    avatar: S3Object
    familyName: String
    givenName: String
    description: String
    careers: [Career] @connection(keyName: "byOwner", fields: ["owner"])
    owner: String!
}

type Career @model @key(name: "byOwner", fields: ["owner"]) @auth(rules: [
    { allow: public, operations: [read] },
    { allow: owner },
    {
        allow: groups,
        groups: ["Admins"],
        operations: [read, update, delete]
    }
]) {
    id: ID!
    company: String
    companyUrl: AWSURL
    owner: String!
}

This schema force user to give a value of owner field when creating a UserMeta or Career model, which should be auto generated by the framework.

@yaquawa this seems to be an enhancement to our @key directive as this is not supported today. @akshbhu please make sure to take a look at this for the @key changes.

Is there any way to accomplish this at the moment?
For models declared with @auth(rules: [{ allow: owner }, { allow: groups, groups: ["Admin"] }], I would like to add @key(name: "byOwner", fields: ["owner", "id"]) directives so that the backend code can lookup DDB items by owner. If you don't explicitly declare the owner field then you get an error during amplify push.
The idea on the backend is to have a DDB event stream Lambda where change events on one table can be used to lookup items on other DDB tables using the owner ID. Is there some other approach I could/should be using to accomplish this?

Is there any way to accomplish this at the moment?
For models declared with @auth(rules: [{ allow: owner }, { allow: groups, groups: ["Admin"] }], I would like to add @key(name: "byOwner", fields: ["owner", "id"]) directives so that the backend code can lookup DDB items by owner. If you don't explicitly declare the owner field then you get an error during amplify push.
The idea on the backend is to have a DDB event stream Lambda where change events on one table can be used to lookup items on other DDB tables using the owner ID. Is there some other approach I could/should be using to accomplish this?

@kjones @attilah
Another issue is that if you must define the owner field, that means other user can modify this field, which is not we want.
so you end up with add additional @auth to the owner field, then this will give error....
type Career @model @searchable
    @key(name: "byOwner", fields: ["owner"])
    @auth(rules: [
        { allow: public, operations: [read] },
        { allow: owner },
        {
            allow: groups,
            groups: ["Admins"],
            operations: [read, update, delete]
        }
    ])
{
    id: ID!
    company: String
    companyUrl: AWSURL
    departments: [String]
    occupation: String
    position: String
    employeeCount: String
    start: AWSDate
    end: AWSDate
    showCompany: Boolean
    owner: String! @auth(rules: [{ allow: owner, operations: [read, create] }, { allow: groups, groups: ["Admins"], operations:[read] }])
}

above schema got error when amplify push
Per-field auth on the required field owner is not supported with subscriptions.
Either make the field optional, set auth on the object and not the field, or disable subscriptions for the object (setting level to off or public)

now you have to turn the subscriptions off...

@kjones @attilah
Another issue is that if you must define the owner field, that means other user can modify this field, which is not we want.
so you end up with add additional @auth to the owner field, then this will give error....
type Career @model @searchable
    @key(name: "byOwner", fields: ["owner"])
    @auth(rules: [
        { allow: public, operations: [read] },
        { allow: owner },
        {
            allow: groups,
            groups: ["Admins"],
            operations: [read, update, delete]
        }
    ])
{
    id: ID!
    company: String
    companyUrl: AWSURL
    departments: [String]
    occupation: String
    position: String
    employeeCount: String
    start: AWSDate
    end: AWSDate
    showCompany: Boolean
    owner: String! @auth(rules: [{ allow: owner, operations: [read, create] }, { allow: groups, groups: ["Admins"], operations:[read] }])
}

above schema got error when amplify push
Per-field auth on the required field owner is not supported with subscriptions.
Either make the field optional, set auth on the object and not the field, or disable subscriptions for the object (setting level to off or public)

now you have to turn the subscriptions off...

Hi @attilah @akshbhu
Would you please tell me if this will be fixed?
I have to make a decision to if I can still develop my app with amplify.js, if this security concern is the limitation of amplify.js I'm going to switch to other framework as quick as I can. Thanks.

Hi @attilah @akshbhu
Would you please tell me if this will be fixed?
I have to make a decision to if I can still develop my app with amplify.js, if this security concern is the limitation of amplify.js I'm going to switch to other framework as quick as I can. Thanks.

@yaquawa One work around for this is to override the mutation template to always insert the owner field in Mutation.createCareer.req.vtl and Mutation.updateCareer.req.vtl so even if the values are passed, the resolver sets them back to the right user.
$util.qr($ctx.args.input.put("owner", $ctx.identity.claims.get("username")))

Hi @yuth , thanks for the solution.
Will this fix be added in the next version of amplify cli?
I don't want to add that snippet every time after I have updated my schema...

Any updates regarding this issue?


amdadl-sdk, amdapp-sdk: remove

Motivation for this change
These libraries are obsolete (last upstream 3.0 update happened in 2015 and even this version was not packaged, latest was 2.8 in the nixpkgs).
Nothing in the nixpkgs tree requires them.
The only package requiring them - cgminer - was fixed in https://github.com/NixOS/nixpkgs/pull/61823 to use OpenCL
Let's remove this.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@ofborg eval
Seems stalled; retry.


Doest it still work?

Hi,
When I try to connect I get:
ResponseError: Endpoint deprecated: Please update your App
details: { method: 'post', url: '/oauth/token' },
status: 400

Any clue?

Hey yes sorry Tesla have updated their API - I'm digging up new docs.  This won't work untilI get a new version out.


The first model inherits from base_model for MatchZoo 2.0

Create a sample model to use MatchZoo 2.0 base_model.

Start to work on this issue until base_model settle down.


Only load JSON once

In the index.html file, we're loading status.json twice. Retrieve the file just once, and then feed it to C3.js, instead of having C3.js reload it with its native URL-loading functionality.

Closed with 34702f1.


DeserializeObject doesn't respect Required/ItemRequired

Summary
Hello all.
I am trying to make JSON attributes required but I couldn't make it work with JsonApiSerializer.
Using the regular JsonSerializerSettings (Newtonsoft.Json) I get the expected behavior.
Configuration

TargetFramework: netcoreapp2.2
JsonApiSerialiser: 1.7.3
Newtonsoft.Json: 12.0.2

Scenarios
Model
[JsonObject(ItemRequired = Required.AllowNull)]
class ApiModel {
    public int Id { get; set; }
    public string Name { get; set; }
}

Expected (Newtonsoft.Json): Throws Exception
var json = @"{ ""id"": ""1"" }";
JsonConvert.DeserializeObject<ApiModel>(json, new JsonSerializerSettings());

Newtonsoft.Json.JsonSerializationException: 'Required property 'Name' not found in JSON. Path '', line 1, position 13.'
Not Expected (JsonApiSerializer): Doesn't throw any Exception
var json = @"{ ""data"": { ""id"": ""1"" } }";
JsonConvert.DeserializeObject<ApiModel>(json, new JsonApiSerializerSettings());

JsonApiSerializer overrides a lot of the deserialization process so that it can handle the different structure of JsonApi where the objects properties will likely not be next to each other. This is probably a feature we lose by overriding the deserialization behaviour
However it probably isn't too hard to re-implement the feature in our overridden deserialization process. You are more than welcome to have a go at it and raise a PR, otherwise i will have a look at it when I have some spare capacity in a few weeks.

I would also be interested in this feature, in particular re-instating the behaviour of the MissingMemberHandling.Error setting in newtonsoft that should throw errors like in the example below. Probably needs a fix in ResourceObjectCOnverter somewhere ?


Move to Gesture API introduced with react-native-gesture-handler 2

Changes
Replaced the old gesture handling API of react-native-gesture-handler (RNGH) by the Gesutre API introduced in version 2 of RNGH. This change also required an update of the expo dependency.
Related Issues
This update implements #54 and resolves the issue mentioned therein.
closes #54

Thank you for the PR and the update to Expo!
Let me test it on my computer to see if the example still works, and if it does I will merge it and release a new version :)

It is working on iOS, but is crashing on the Android emulator:
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: Exception in native call
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: java.lang.ClassCastException: java.lang.Double cannot be cast to java.lang.Boolean
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: 	at abi44_0_0.com.facebook.react.bridge.ReadableNativeArray.getBoolean(ReadableNativeArray.java:1)
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: 	at abi44_0_0.com.facebook.react.bridge.JavaMethodWrapper$1.extractArgument(JavaMethodWrapper.java:2)
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: 	at abi44_0_0.com.facebook.react.bridge.JavaMethodWrapper$1.extractArgument(JavaMethodWrapper.java:1)
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: 	at abi44_0_0.com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:16)
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: 	at abi44_0_0.com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:2)
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: 	at abi44_0_0.com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: 	at android.os.Handler.handleCallback(Handler.java:938)
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: 	at android.os.Handler.dispatchMessage(Handler.java:99)
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: 	at abi44_0_0.com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:1)
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: 	at android.os.Looper.loopOnce(Looper.java:201)
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: 	at android.os.Looper.loop(Looper.java:288)
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: 	at abi44_0_0.com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:8)
03-22 15:39:29.087  6572  6788 E unknown:ReactNative: 	at java.lang.Thread.run(Thread.java:920)

I've had similar errors on Android before and it was fixed by using Expo specific versions of dependencies. The latest commit fixes that error, although I still can seem to draw on Android for some reason and can't seem to figure out why it's not working correctly.
https://user-images.githubusercontent.com/22248828/159597180-1c7b47c4-8a8a-4af3-aa61-741bfb66adf6.mov

Indeed this change does not work for Android. I investigated the issue today, without much success.
I only realized that none of the callback functions onChange, onBegin, or onEnd are called.

Unsure why circleci is not being triggered - will merge it


Error about 'sudo apt-get install libgraphicsmagick1-dev'

When i install libgraphicsmagick1-dev,it tells me 'dependence: liblcms2-dev but it won't be installed' and 'dependence: libexif-dev but it won't be installed'. How can i deal with this problem?

Try sudo apt-get update first.


about target_sources(tgt PUBLIC ...)

Hello,
You got me interested about the use for target_sources(tgt PUBLIC ...):

https://github.com/google/cctz/pull/83/files/6cd878965d04595624f512546f59682b165ccd00#r224360174

I have some hard time seeing how it can be useful to specify public headers with it, and I started to do some research on what it can be good for.
I found some discussion about it here:

https://www.reddit.com/r/cpp/comments/65iyxv/embracing_modern_cmake

3 posts that got my attention:

https://www.reddit.com/r/cpp/comments/65iyxv/embracing_modern_cmake/dgaq9xu/
https://www.reddit.com/r/cpp/comments/65iyxv/embracing_modern_cmake/dgbsutp/
https://www.reddit.com/r/cpp/comments/65iyxv/embracing_modern_cmake/dgnbvjo/

And some other information here, on slide 76 (77 on video):

https://steveire.wordpress.com/2017/11/05/embracing-modern-cmake/

So I guess, my take on this is that it is mostly for niche situations, and it's not useful for declaring public headers.

Agree target_sources(tgt PUBLIC ...) is not intended to expose/list your public header (equivalent to bazel hrds list)

Indeed, for that it's possible that I will start using PUBLIC_HEADERS when the project is structured as a merged layout for sources + private and public headers + unit tests.
For target_sources(tgt PUBLIC ...), maybe people will surprise me in the future with smart use cases.

Seems the CMake 3.23 FILE_SET is the new way...
ref: https://discourse.cmake.org/t/installing-headers-the-modern-way-regurgitated-and-revisited/3238/2

Thanks for the follow up!


Add env files support

devrc already are parsing env_files options from devrcfile, but not loading variables. devrc must read environment variables before loading file environment variables, but after global variables evaluation.

done


adding titanic example

Signed-off-by: Arvind Gautam<EMAIL_ADDRESS>What changes are proposed in this pull request?
Adding a simple example with explanations API for Captum interpretability of the model on the titanic data set.
How is this patch tested?
Tested on the local machine. and all the unit test got passed
Release Notes
Is this a user-facing change?

[x] No. You can skip the rest of this section.
[ ] Yes. Give a description of this change to be included in the release notes for MLflow TorchServe Deployment Plugin users.

(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
What component(s) does this PR affect?
Components

[ ] area/deploy: Main deployment plugin logic
[ ] area/build: Build and test infrastructure for MLflow TorchServe Deployment Plugin
[ ] area/docs: MLflow TorchServe Deployment Plugin documentation pages
[x] area/examples: Example code

How should the PR be classified in the release notes? Choose one:

[ ] rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
[x] rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
[ ] rn/feature - A new user-facing feature worth mentioning in the release notes
[ ] rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
[ ] rn/documentation - A user-facing documentation change worth mentioning in the release notes

@HamidShojanazeri I have addressed the comments and pushed the updated PR, Please review it whenever you get time.

@HamidShojanazeri  I have addressed your latest comments,  all the checks are also passed. Please review it.

@Arvind-Ideas2IT Thanks LGTM, just please add a note in the README to modify/pass the path to the csv file in the input.json.

@Arvind-Ideas2IT Thanks LGTM, just please add a note in the README to modify/pass the path to the csv file in the input.json.

@HamidShojanazeri  Sure, I will do that. Thanks.

@HamidShojanazeri  I have updated the READ.md as you suggested, removed the absolute path of the CSV in the input.json


could not branch Ubuntu repository

clair logs
Feb 19 11:25:46 <IP_ADDRESS> clair[509]: {"Event":"could not branch Ubuntu repository","Level":"error","Location":"ubuntu.go:177","Time":"2018-02-19 11:25:46.924706","error":"exit status 3","output":"bzr: ERROR: Invalid http response for http://bazaar.launchpad.net/~ubuntu-security/ubuntu-cve-tracker/master/.bzr/repository/packs/269638fd93f179ceafe5d289f42db0c1.pack: Missing the Content-Range header in a 206 range response\n"}
Feb 19 11:25:46 <IP_ADDRESS> clair[509]: {"Event":"an error occured when fetching update","Level":"error","Location":"updater.go:220","Time":"2018-02-19 11:25:46.924851","error":"could not download requested resource","updater name":"ubuntu"}
a manual download using bzr Fails either
with
bzr branch lp:ubuntu-cve-tracker
or with
bzr branch https://launchpad.net/ubuntu-cve-tracker
with the same error in the final step
Invalid http response for http://bazaar.launchpad.net/~ubuntu-security/ubuntu-cve-tracker/master/.bzr/repository/packs/16c916fc513b214fbddf8bfb4c8f1e61.pack: Missing the Content-Range header in a 206 range Response
If I use curl the file is downloaded correctly.
.
Environment:

vmware/Harbor with clair:
Clair client name/version: clair2.0.1
Host OS:  photonos v1.0
Network/Firewall setup: docker Container behind nginx and corporate firewall

It seems like an issue with bzr.
btw, did you curl with range header?

No. I used curl without the range header.

the failure is due to kubernetes kiling the bazaar process with OOM
you will need to increase the memory and CPU limits in the deployment for the pod to at lease 1500Mi and 200m respectively.
see the following PR : https://github.com/coreos/clair/pull/537

Getting #562 merged would be very helpful! Clair sits in a 1 minute loop updating vulnerability data from all sources because of that error.

Fixed in #568. Please open a new issue if you're still experiencing this bug on a non-bzr Clair.


Disallow additionalProperties for terraform_addons (#951)

Can you run ./scripts/regen.sh and confirm that there are no errors raised?

Can you run ./scripts/regen.sh and confirm that there are no errors raised?

just ran this and it prompted me this:

(root).terraform_addons: Additional property providers is not allowed
(root).terraform_addons: Additional property raw_config is not allowed

Can you run ./scripts/regen.sh and confirm that there are no errors raised?

just ran this and it prompted me this:

(root).terraform_addons: Additional property providers is not allowed
(root).terraform_addons: Additional property raw_config is not allowed

probably because I need to add those to the project recipe as it now supersedes the depolyment recipe it references

That's something I was worried about as well. By setting allow additional properties to false in the project.hcl, it will not allow any attributes to be specified in the terraform_addon block. And I don't think we want to duplicate the same schema for terraform_addon in project.hcl, it should just use the schema specified in the deployment.hcl. project.hcl references deployment.hcl.

I suspect the errors are just because no properties have been configured for terraform_addons. We should probably define it as an object and define properties it can accept.

I guess the reason we're seeing this behaviour is because project.hcl lets it be anything, but if you put an extra property, it doesn't get passed directly to deployment.hcl.
Could we try that, passing terraform_addons directly to deployment.hcl in line 158?

Another solution I can think of is listing the properties but letting them be anything and letting them be validated in deployment.hcl

Does this fix the issue?

Does this fix the issue?

yes It now catches exceptional attributes as expected and let pass those specified

/gcbrun

Does add additionalProperties = false here do anything?

Does add additionalProperties = false here do anything?

I tried it, and no, it doesn't help because the properties in project.hcl aren't directly passed to deployment.hcl, they are inherited.

Does add additionalProperties = false here do anything?

just tried, it doesn't work with that unfortunately

Does add additionalProperties = false here do anything?

I tried it, and no, it doesn't help because the properties in project.hcl aren't directly passed to deployment.hcl, they are inherited.

Hmm ok. But these checks for inner attributes work as expected?

Does add additionalProperties = false here do anything?

I tried it, and no, it doesn't help because the properties in project.hcl aren't directly passed to deployment.hcl, they are inherited.

Hmm ok. But these checks for inner attributes work as expected?

Just tried that and they don't work as expected, the enforcement is effective on the immediate properties of terraform_addons but not their children

In that case we should see if the fields can be passed directly to deployment.hcl i.e. with a data block.

it should all be working as expected now after wrapping all terraform_addons into deployment and loading flattened 'depolyment' field into its recipe

it should all be working as expected now after wrapping all terraform_addons into deployment and loading flattened 'depolyment' field into its recipe

should've said running ./scripts/regen.sh and manually checking random fields against validations are all working well on my end. Since I don't have access to view the unit-tests, I'm not sure why it's not letting me pass

The unit tests ask that you
Please run the following command from the repo root and check in the changes:
./scripts/regen.sh

/gcbrun

FYI I think we're proceeding with https://github.com/GoogleCloudPlatform/healthcare-data-protection-suite/pull/1003 instead.