Mac Lens desktop does not run.

From Lens-2.0.5.dmg
Got email invite to install.
Also link to support is broken
https://account.kontena.io/support

Same, takes a kill to actually stop it too :(

It's being developed solely on macs so it seems strange. Which version of MacOS?

@nevalla can you take a look at this support link issue

same here. stalls on loading dialog
Lens 2.0.7 (<IP_ADDRESS>91002.30)
Mac os 10.14.4 (18E226)

Try to start Lens via terminal using command: /Applications/Lens.app/Contents/MacOS/Lens
Does it show any errors?

These are the errors I'm seeing
UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'certData' of null
at e.caData (/Applications/Lens.app/Contents/Resources/app.asar/webpack:/src/main/context-handler.ts:49:50)
at /Applications/Lens.app/Contents/Resources/app.asar/main.js:1:271925
at Object.next (/Applications/Lens.app/Contents/Resources/app.asar/main.js:1:272030)
at o (/Applications/Lens.app/Contents/Resources/app.asar/main.js:1:270776)
at processTicksAndRejections (internal/process/task_queues.js:89:5)
(node:7755) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'certData' of null
at e.caData (/Applications/Lens.app/Contents/Resources/app.asar/webpack:/src/main/context-handler.ts:49:50)
at /Applications/Lens.app/Contents/Resources/app.asar/main.js:1:271925
at Object.next (/Applications/Lens.app/Contents/Resources/app.asar/main.js:1:272030)
at o (/Applications/Lens.app/Contents/Resources/app.asar/main.js:1:270776)
at processTicksAndRejections (internal/process/task_queues.js:89:5)
(node:7755) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:7755) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:7755) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:7755) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@amigold that implies that Lens app cannot properly parse & use the kubeconfig. Could you post what kind of kubeconfig you are using, especialy the user part. Rip out any sensitive data naturally. :)
And yes, we need to handle those kind of errors better.

hopefully this helps?
users:
- name: NAME HERE
  user:
    client-certificate-data: CERTIFICATE DATA HERE
    client-key-data: CLIENT KEY DATA HERE
    password: PASSWORD HERE
    username: admin
- name: NAME HERE
  user:
    password: PASS HERE
    username: USER HERE

@amigold thanks. having both client certs and basic auth defined, sounds wrong, not 100% sure that might break things.
Mind pasting the whole kubeconfig with sensitive data ripped out just to inspect which config might cause this.
Oh, and I'm assuming the your kubectl works fine with this config?

`apiVersion: v1
clusters:

cluster:
certificate-authority-data: CA DATA
server: URL
name: NAME
contexts:
context:
cluster: NAME
user: USER NAME
name: USER NAME AGAIN
current-context: CLUSTER NAME
kind: Config
preferences: {}
users:
name: NAME HERE
user:
client-certificate-data: CERTIFICATE DATA HERE
client-key-data: CLIENT KEY DATA HERE
password: PASSWORD HERE
username: admin
name: NAME HERE
user:
password: PASS HERE
username: USER HERE`

@amigold the only way we've been able to reproduce this is by having malformed kubeconfig where your context config points to non-existing user info
We are building up a fix where we better validate the info and do not try to load such clusters at all

2.0.8 is out with fixes.

I've juste updated to 2.0.8, and the app is not running. Here's the error :
info: Set kubectl version 1.16.1 for cluster version v1.15.3 using version map
error: server https://c1.kubesail.com:6443 stderr: (node:11646) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'method' of undefined
    at axios_1.default.then.catch (/snapshot/kontena-k8s-dashboard/build/server/api/kube-request.js:0:0)
    at <anonymous>
(node:11646) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 19)
(node:11646) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Same for me.
I have upgraded to Lens 2.0.8 (Mac) and does not run (same as previous version).
Jeremy

On 4 Oct 2019, at 12:08 am, Zegorax<EMAIL_ADDRESS>wrote:
I've juste updated to 2.0.8, and the app is not running. Here's the error :
info: Set kubectl version 1.16.1 for cluster version v1.15.3 using version map
error: server https://c1.kubesail.com:6443 stderr: (node:11646) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'method' of undefined
at axios_1.default.then.catch (/snapshot/kontena-k8s-dashboard/build/server/api/kube-request.js:0:0)
at
(node:11646) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 19)
(node:11646) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/kontena/lens/issues/33?email_source=notifications&email_token=ABU7XQ3DSDDKZHZXDTWXOS3QMX4HFA5CNFSM4I4P5DMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAIKMOQ#issuecomment-537962042, or mute the thread https://github.com/notifications/unsubscribe-auth/ABU7XQYOH6YZMWWBZCVY3VLQMX4HFANCNFSM4I4P5DMA.

Could this problem persist because the lens cluster store still has some pieces of the broken kubeconfig? Clearing the store could help.
rm -rf $HOME/Library/Application\ Support/Lens will wipe it clean.

After doing that, I get a colour wheel and title bar "Lens" but then nothing happens. not responding.

I tried to wipe the Lens directory, but it did not solve the problem.

Yeah doesn't work on OSX, just says cluster is offline, it's definitely not.

Yeah doesn't work on OSX, just says cluster is offline, it's definitely not.

This cluster is offline might also indicate that Lens app is unable to authenticate to the Kubernetes API with given kubeconfig. Please could you tell what authentication method is used with the cluster?

@nevalla @jeremy-moore Could you please try to connect to a Kubesail cluster on MacOS ? The issue should normally happen.

@Zegorax @jeremy-moore does this still happen with Lens v2.1.3?

I now get a menu and the app does not crash.
But there is no main window and nothing useful I can do.
BTW kube config context is now a DigitalOcean K8s cluster.
$ kubectl cluster-info
Kubernetes master is running at https://e9534cbc-8dbf-4349-b03f-1d4acef7dd4f.k8s.ondigitalocean.com
CoreDNS is running at https://e9534cbc-8dbf-4349-b03f-1d4acef7dd4f.k8s.ondigitalocean.com/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

Are there any requirements for the cluster or config?
Are there any assumptions of the MacOS system? eg. versions of things

@jeremy-moore try following:

quit the app (make sure it's really stopped)
remove the internal cluster config: rm ~/Library/Application\ Support/Lens/lens-cluster-store.json
start the app

Yep already did that.

Are there any requirements for the cluster or config?

Token and cert based kubeconfigs should work ootb (we have tested also DO). Anyway you should see the app window even if you have exotic configs.

Are there any assumptions of the MacOS system? eg. versions of things

Any recent 64bit MacOS version should work.
Are you still seeing the same errors with the latest Lens version if you run: /Applications/Lens.app/Contents/MacOS/Lens ?

I just tried with https://kuber.host. There is no error in the Terminal but no UI is displayed. The cluster is seen as online in the settings.
Now, for an unknown reason, a Kubesail cluster won't even pass the verification.
Invalid kubeconfig context kubesail-zegorax: cannot access cluster (kubesail-zegorax)

I just tried with https://kuber.host. There is no error in the Terminal but no UI is displayed. The cluster is seen as online in the settings.

Issue with Kuber is that user has only limited access to cluster. Lens UI tries to resolve allowed namespaces, but fails since user has no right to list namespaces. However, we could use namespace defined in kubeconfig and assume that user has access to that namespace and display only that namespace in UI.
Issue with Kubesail kubeconfig seems to be that there's totally redundant client-key-data under user section. By removing that, it makes possible to add the cluster. However, since the access to the cluster is very limited it has the same issue as Kuber.

Kuber should work with v2.1.4.

I think this issue needs some more clarity. The title "Mac Lens desktop does not run" is not reflecting (anymore) issues we are discussing in here. I'd suggest a) we close this issue and create new one with some focus; or b) update the title of this issue to reflect what is the actual issue that must be solved.
Tl;dr; This issue is not anymore about "Mac Lens desktop does not run". @jeremy-moore can you confirm. If you feel this is still issue, please let us know (after trying with the latest version).

I still have the original issue "Mac Lens desktop does not run".
Although it now shows the title bar, but no main window.
It does not work either with an on-premise cluster or one on DigitalOcean.
Version 2.2.1 (<IP_ADDRESS>91023.10)
$ rm -rf $HOME/Library/Application\ Support/Lens
$ /Applications/Lens.app/Contents/MacOS/Lens
CLUSTER STORE, MIGRATION: 2.0.0-beta.2
Store data now: {"_options":{"configName":"lens-cluster-store","fileExtension":"json","projectSuffix":"nodejs","clearInvalidConfig":true,"accessPropertiesByDotNotation":false,"projectVersion":"2.2.1","migrations":{},"cwd":"/Users/jere/Library/Application Support/Lens"},"events":{"_events":{},"_eventsCount":0},"path":"/Users/jere/Library/Application Support/Lens/lens-cluster-store.json"}
GVA info: Successfully connected to the Intel plugin, offline Gen9

I still have the original issue "Mac Lens desktop does not run".
Version 3.1

@jeremy-moore if you run the latest version from command line: DEBUG=true /Applications/Lens.app/Contents/MacOS/Lens (or correct path to lens app), do you see any errors in output?

Some result.
$ rm -rf $HOME/Library/Application\ Support/Lens
$ DEBUG=true /Applications/Lens.app/Contents/MacOS/Lens
CLUSTER STORE, MIGRATION: 2.0.0-beta.2
Store data now: {"_options":{"configName":"lens-cluster-store","fileExtension":"json","projectSuffix":"nodejs","clearInvalidConfig":true,"accessPropertiesByDotNotation":false,"projectVersion":"2.4.1","migrations":{},"cwd":"/Users/jere/Library/Application Support/Lens"},"events":{"_events":{},"_eventsCount":0},"path":"/Users/jere/Library/Application Support/Lens/lens-cluster-store.json"}
CLUSTER STORE, MIGRATION: 2.4.1
GVA info: Successfully connected to the Intel plugin, offline Gen9

This is a bit mystery to me now.  I don't see the following line in my output (MacBook PRO / Mojave), but it does not look error either
GVA info: Successfully connected to the Intel plugin, offline Gen9

Please could you tell more about your Mac/OS X environment, if I'm able to reproduce this on some other machine.

Sure. What environment details are you interested in?

Is there any update on this issue? I'd suggest downloading and installing a fresh new version and let's see how it'll go.  I can see from the discussion thread that the version we are trying to install here is very old version and many improvements have been made since then.

I am on the latest version. And running into the "cannot parse kubeconfig" error. For me the app was working just fine, until deleting a workspace caused the app to crash and then upon restarting all my configuration was lost and I was back to the screen that would ask me add a new cluster. And when I try to do that, I keep getting slapped with the "cannot parse kubeconfig" error. The Kubeconfig works outside of the app though. Any suggestions?

I've tried reinstalling Lens and re-acquiring my kubeconfig files as well. Nothing seems to help with the issue.

I'm facing the exact same issues. The output of the log isn't very useful and Kubectl works just fine, as does the K9S project which is similar.
The following output is with version 3.5.1 and version 1.8.6 of Kubectl on a Mac running 10.15.3
╭─darren.thiessen@DTHIESSEN-MBP ~/Applications/Lens.app/Contents/MacOS
╰─➤  $ rm -rf ~/Library/Application\ Support/Lens
╭─darren.thiessen@DTHIESSEN-MBP ~/Applications/Lens.app/Contents/MacOS
╰─➤  $ DEBUG=true ./Lens

debug: Set kubectl version 1.17.4 for cluster version 1.17.4 using version map
CLUSTER STORE, MIGRATION: 2.0.0-beta.2
CLUSTER STORE, MIGRATION: 2.4.1
CLUSTER STORE, MIGRATION: 2.6.0-beta.2
CLUSTER STORE, MIGRATION: 2.6.0-beta.3
CLUSTER STORE, MIGRATION: 2.7.0-beta.0
CLUSTER STORE, MIGRATION: 2.7.0-beta.1
(node:96393) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'split' of undefined
    at parseEnv (/Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/node_modules/shell-env/index.js:15:35)
    at AsyncFunction.module.exports.sync (/Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/node_modules/shell-env/index.js:47:10)
    at Object.t.shellSync (/Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/webpack:/src/main/shell-sync.ts:15:1)
    at App.<anonymous> (/Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/main.js:1:323139)
    at /Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/main.js:1:322433
    at Object.next (/Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/main.js:1:322538)
    at /Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/main.js:1:321451
    at new Promise (<anonymous>)
    at n (/Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/main.js:1:321199)
    at App.protocol (/Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/webpack:/src/main/index.ts:32:3)
    at App.emit (events.js:205:15)
(node:96393) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'split' of undefined
    at parseEnv (/Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/node_modules/shell-env/index.js:15:35)
    at AsyncFunction.module.exports.sync (/Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/node_modules/shell-env/index.js:47:10)
    at Object.t.shellSync (/Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/webpack:/src/main/shell-sync.ts:15:1)
    at App.<anonymous> (/Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/main.js:1:323139)
    at /Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/main.js:1:322433
    at Object.next (/Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/main.js:1:322538)
    at /Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/main.js:1:321451
    at new Promise (<anonymous>)
    at n (/Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/main.js:1:321199)
    at App.protocol (/Users/darren.thiessen/Applications/Lens.app/Contents/Resources/app.asar/webpack:/src/main/index.ts:32:3)
    at App.emit (events.js:205:15)
(node:96393) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:96393) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:96393) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:96393) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Is this still a problem?

For me it was/is. I think I was able to resolve it. After switching OSX's default shell from ZSH to BASH it's now working. I was getting the following error which lead me to believe it might be an issue with the default shell:
error: shellEnv: Error: Command failed: /bin/bash -ilc echo -n "_SHELL_ENV_DELIMITER_"; env; echo -n "_SHELL_ENV_DELIMITER_"; exit
bash: no job control in this shell

Today I ran into the same problem: It seems Lens is running some shell commands and actually runs this shell in interactive mode which seems to be a bug imho. In my case a script (zsh-abbr) came to an halt and blocked the opening of the main window.
After removing zsh-abbr from my zsh plugins everything worked again. Nevertheless IMHO this is a bug of lens as a non-interactive shell should be used for scripts.

After removing zsh-abbr from my zsh plugins everything worked again. Nevertheless IMHO this is a bug of lens as a non-interactive shell should be used for scripts.

Lens needs to fake an interactive shell for the terminal so it can set the PATH to kubectl and KUBECONFIG. For this to work properly, it needs to figure out the env of an interactive shell so that it can duplicate it on a non-login shell. Also I think it may want the KUBECONFIG of a login shell on startup.
There may be some better way to do it.

Quit Lens then delete the folder
 ~/Library/Application Support/Lens
After just open again.
I'm using macOS.

This is related to an unsupported version of Lens. Please open a new issue if this continues to happen with the latest (4.1.4) version.

It works via sudo: sudo /Applications/Lens.app/Contents/MacOS/Lens


Allow detecting archived or disabled repos

This allows listing just "active" repositories in an organization. Right now, we have to manually exclude any such repository.

Huh, I don't understand those Travis errors... "uninitialized constant Faraday::Error::ClientError" ... ? Is this something caused by my PR, or a wider problem with the Travis tests?

I don't understand those Travis errors

Please don't worry about the errors. It is caused by a second-order dependency (octokit > faraday) of this plugin. The error will resolve automatically once a new version of octokit gets released..

@fingolfin The unrelated Faraday errors have been removed from this branch. The current failures are related to this PR. When possible, please look into getting those tests to pass again.

I had to fix script/webmock-repopulate and re-run it to get up-to-date webmocks. Let's see if that helps CI.

OK, that causes tons of errors in spec files.
Not sure how best to proceed. I could update those spec files of course (arguably, it would make sense to use up-to-date version of that JSON data). Or I could revert that part of the PR, and just hand-edit the webmock files to have the right keys in them. But I wonder if basing the tests on ancient versions of the JSON produced by GitHub is a good idea?

I would suggest that you revert all changes that affect tests outside the scope of this pull request first and then tackle the failing tests incrementally..

That is the second option I listed: I could hand-edit the relevant JSON files to insert the required keys. That's easy enough to do, but seems rather... brittle to me. Is that really what you want?
I could also only update those webmock JSON files (by running script/webmock-repopulate) which are "needed" for testing the archived and disabled repos; but that doesn't substantially simplify the issue, I am afraid.

@fingolfin You had two two options and asked for the best way to proceed.
I pointed you to the option that results in the most minimal diff for this PR which has a greater chance of being accepted for merge.
Now if you want to debate on or counter that suggestion, all that's going to lead to is noise and a stalemate...
IMO, the best way out is still to revert changes outside the scope of this PR and attempt to get the tests passing by manually editing spec/spec_helpers/integration_helper.rb

I did not want to debate, I just wanted to verify I understood what you were suggesting, to make sure I don't waste time on an approach that then is rejected later on shrug

All tests passed now except for one one AppVeyor, which I don't understand, as it complains about a mismatch for latest_release, but I didn't touch that.. It says:
...
Failures:

  1) integration into a jekyll site contains the correct latest_release
     Failure/Error: expect(subject[key].to_s).to match value

       expected "false" to match /assets_url/
       Diff:
       @@ -1,2 +1,2 @@
       -/assets_url/
       +"false"
     # ./spec/integration_spec.rb:30:in `block (3 levels) in <top (required)>'


Implement intrinsic matching semantics of TransmuteFrom::transmute

TransmuteFrom models 'union transmute', which permits extensions of the trailing padding bytes of Src during the transmutation to Dst. This model is implemented by TransmuteFrom::transmute, which uses a union to perform the transmutation. Essentially:
pub unsafe fn transmute_via_union<Src, Dst>(src: Src) -> Dst {
    use core::mem::ManuallyDrop;

    #[repr(C)]
    union Transmute<Src, Dst> {
        src: ManuallyDrop<Src>,
        dst: ManuallyDrop<Dst>,
    }

    let transmute = Transmute {
        src: ManuallyDrop::new(src),
    };

    let dst = transmute.dst;

    ManuallyDrop::into_inner(dst)
}

Unfortunately, this long-form implementation might be quite heavy on the optimizer. For example, using ManuallyDrop can cause memcpys and allocas that LLVM cannot remove: https://github.com/rust-lang/rust/issues/79914
It would therefore be nice to have a intrinsic version of this that wasn't so dependent on the optimizer. We could either, as @scottmcm suggests, modify transmute_unchecked to provide these semantics, or we could provide a new intrinsic (e.g., transmute_union) that provides these semantics.

it immediately occurs to me that the point of a ManuallyDrop is to prevent dropping, but it does that by being a union, so you're just sticking a union into a union... so you can just remove the ManuallyDrop layer

@Lokathor no ManuallyDrop is not a union, and it is requires for any non-Copy fields of unions.
https://doc.rust-lang.org/std/mem/struct.ManuallyDrop.html

Oh my bad I'm thinking of MaybeUninit.


Add support for lazy NoSpamLogger argument evaluation

NoSpamLogger is use in hot logging paths.  To get the greatest benefit
calling should be as cheap as possible.  This patch adds a variant to
NoSpamLogger.log and friends to lazily supply the formatting parameters.
It also introduces a params() helper function to make constructing the
parameter array supplier cleaner.
Fixed up existing call sites to use params where it made sense and
altered the logging for org.apache.cassandra.net.InboundSink#accept
so that log statements for tombstones and indices would be output
correctly. The previous getMessage format string included info on
keys, tables and queries that would vary between calls.
Patch by Jon Meredith; reviewed by ? for CASSANDRA-15766.

alternate version merged


Native TF operations drop Keras tensor metadata

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
**OS Platform and Distribution: Ubuntu 16.04
Mobile device: N/A
TensorFlow installed from: from pip
TensorFlow version: ('v1.9.0-0-g25c197e023', '1.9.0')
Python version: 2.7.12
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: CUDA-9.0/cuDNN-7.1.4
GPU model and memory: N/A
Exact command to reproduce:

$ python
import tensorflow as tf
from tensorflow.keras.layers import Input

x = Input((28, 28, 3))
y = Input((28, 28, 3))
z = x + y

model = tf.keras.Model([x, y], z)

Description
The code mentioned above throws the error (see logs). As it turned out, almost all native tf operations , such padding, convolution, etc., drop tensor metadata.
I do understand that these operations can be replaced with similar Keras layers or wrapped with Lambda. However, since Keras is officially moved to tensorflow package, it would be nice to preserve tensor compatibility between tf and Keras.
Source code / logs
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/oleg/tf/venv/local/lib/python2.7/site-packages/tensorflow/python/keras/engine/training.py", line 111, in __init__
    super(Model, self).__init__(*args, **kwargs)
  File "/home/oleg/tf/venv/local/lib/python2.7/site-packages/tensorflow/python/keras/engine/network.py", line 78, in __init__
    self._init_graph_network(*args, **kwargs)
  File "/home/oleg/tf/venv/local/lib/python2.7/site-packages/tensorflow/python/keras/engine/network.py", line 201, in _init_graph_network
    '(thus holding past layer metadata). Found: ' + str(x))
ValueError: Output tensors to a Model must be the output of a TensorFlow `Layer` (thus holding past layer metadata). Found: Tensor("add:0", shape=(?, 28, 28, 3), dtype=float32)

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Bazel version
GPU model and memory
Mobile device

Mobile device: N/A
Bazel version (if compiling from source): N/A (installed from pip)
GCC/Compiler version (if compiling from source): N/A (installed from pip)
GPU model and memory: N/A (Irrelevant, sample code is for CPU)

Nagging Assignee @bignamehyp: It has been 18 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Keras is a higher level API. It doesn't mean naive ops need to support higher level meta-data.


Nested schemas

Codecov Report

Merging #27 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@           Coverage Diff            @@
##           master    #27      +/-   ##
========================================
- Coverage     0.3%   0.3%   -0.01%
========================================
  Files          36     35       -1
  Lines         650    652       +2
========================================
  Hits            2      2
- Misses        648    650       +2

Impacted Files
Coverage Δ

snow/resource/fields/__init__.py
0% <ø> (ø)
:arrow_up:

snow/resource/schema.py
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Heroku click deploy

https://devcenter.heroku.com/articles/heroku-button
Recommended by @renatodex

https://github.com/prest/prest/issues/258


Feature Request: Read Accounts & Roles from config file

~/.aws/config
[profile iam]
 region = eu-central-1

[profile production]
source_profile = iam
role_arn = arn:aws:iam::1234567890:role/Administrator
region = eu-central-1

This would be a good feature to have, though there is no roadmap for us including it, so I am leaving this issue open.
Please feel free to submit a PR if you would like this feature sooner. Cheers.


Remove Final Blockers to CloudFlare Workers Support

Closes https://github.com/gadicc/node-yahoo-finance2/issues/719 .
Changes

Remove support for Node 16
Remove node-fetch in favour of native Node 18 fetch
Use URLSearchParams global instead of import
Remove process.env usage in main code path

Removes support for YF_QUERY_HOST env var

Type

[ ] New Module
[ ] Other New Feature
[ ] Validation Fix
[ ] Other Bugfix
[ ] Docs
[x] Chore/other

Comments/notes
Final tweaks to the library needed for support for CloudFlare Workers (and possibly alternate runtimes 🤷 ), more discussion here
Working in miniflare locally:

Looks good, @eddie-atkinson :pray:
Replying to your individual comments inline.

Ok so re process.env, here's what I'm thinking.

We could consolidate all the vars we actually use into one file that we can import as needed.  That would make it easier to handle any additional imports / logic for different environments and also keep track of all supported environment variables.  Seems like a good design decision.

We don't need to support process.env on the browser ourselves directly.  The expectation is that the developer's bundler will handle this.  e.g. on NextJS at least, it uses the relevant webpack options to export just process.env to the browser.  I think that also covers node:process imports but maybe needs a deeper check.

We may need a to supply a getEnv function based on environment, as from my quick skim of process in Cloudflare workers it seems you also get environment variables per request?  That might also give us more flexibility for other environments in the future.

As a small side note, I think giving into the pressure to support running in the browser was probably a mistake, initially because of all the CORS hassles which I've never managed to emphasize clearly enough, and more recently, I need to actually see if any of the new cookie code even works in the browser at all because without getSetCookie().  However, it did give us a running start into supporting non-node environments, which is a plus.  Something else for me to think about re the next major version release.
Lastly, definite advantage to having a single default import, but if there's no avoiding it, we could also have a particular import path for e.g. CloudFlare workers.  But let's save that as a last resort if we don't manage to solve it any other way.
Re all the above, I'm happy to take it on and experiment a bit.  You could just revert / add back in the relevant lines and I'll implement the above, commit to dev, and you can see if its workable for CloudFlare?

Otherwise yeah, all looks good.  Very exciting to finally move this forward.  Never used Cloudflare workers but I've always wanted to support them (and Vercel Edge functions).  So thanks - once again! - for your passion and efforts here :pray: :grin:

As a small side note, I think giving into the pressure to support running in the browser was probably a mistake

Live and learn I guess, on the getSetCookie thing I think you should be fine, it's included in the MDN docs for fetch. Bearing in mind it only got mainstream browser support last year.

We don't need to support process.env on the browser ourselves directly. The expectation is that the developer's bundler will handle this. e.g. on NextJS at least, it uses the relevant webpack options to export just process.env to the browser. I think that also covers node:process imports but maybe needs a deeper check.

I can't believe this didn't occur to me 🤦. Looking at the various other runtimes it seems like we could almost just get away with process.env:

CloudFlare: process.envwould work, just wouldn't provide any useful configuration. That being said there is the escape hatch where callers can just copy the relevant env vars in the process.env scope before calling the library. That feels pretty defensible to me. (ref)
Bun: process.env would work as a first class citizen (ref)
Deno: No process.env, instead Deno.env (ref)
Node: process.env (obviously)

We may need a to supply a getEnv function based on environment, as from my quick skim of process in Cloudflare workers it seems you also get environment variables per request? That might also give us more flexibility for other environments in the future

Based on the above I think an option which has legs is to create a getEnv function which interrogates the navigator.userAgent property (which is standardised) to take different code paths depending on the runtime. Browsers, as you say will just bundle themselves into whatever state is needed to work. This does mean the code has become "runtime aware", but that's ok provided it doesn't leak.

Re all the above, I'm happy to take it on and experiment a bit. You could just revert / add back in the relevant lines and I'll implement the above, commit to dev, and you can see if its workable for CloudFlare?

Yep that works for me, happy to be pragmatic. Also happy to have a hack, but it seems like you've got an idea for how this should work, so also happy to defer to that 👍

Live and learn I guess, on the getSetCookie thing I think you should be fine, it's included in the MDN docs for fetch. Bearing in mind it only got mainstream browser support last year.

No, I think it's a no-go.  That page looks a lot clearer than the last time I read it, and from my understanding, getSetCookie() in a browser won't return anything as the browser is required to filter out set-cookie which is a "forbidden" header (see the the second paragraph and first example).  I'm starting an issue for breaking changes for v3 and I think I'd like to drop browser support, although, provide helpful tools to relay via a server while maintaining type-safety.  Anyway, that's a discussion for another day :)

process.env

Ooh, thanks for checking up on all the different environments!  Super helpful and very encouraging.  So if I understood correctly then, the user should implement such env copying logic themselves at the start of the worker handler?  I guess once we have all the variables consolidated in one place we could also quite easily provide a function to do this for them, that they could call with 1 line at the beginning of the handler, which I'm sure would be quite welcome.  (Forgive any mislabled terms, never touched Cloudflare workers before).

Yep that works for me, happy to be pragmatic. Also happy to have a hack, but it seems like you've got an idea for how this should work, so also happy to defer to that 👍

If you're happy to do it, I'll be very happy for the help :)  Was a little worried that you once again took on something small that become big; glad that's not the case.  I currently have family visiting abroad so this will definitely all happen much more quickly with your help.  So thanks again :pray:

Based on the above I think an option which has legs is to create a getEnv function which interrogates the navigator.userAgent property (which is standardised) to take different code paths depending on the runtime. Browsers, as you say will just bundle themselves into whatever state is needed to work. This does mean the code has become "runtime aware", but that's ok provided it doesn't leak.

Ok great, let's go the getEnv route.  But, I wouldn't interrogate navigator.userAgent - standardised as it may be.  I'd prefer something that inspects the environment itself, e.g. if (typeof Deno === "object").  It maybe matters a bit less in this specific case, but in general, this way you can avoid complicated version ranges and sometimes one runtime might adopt an API from another, so it's a better long term strategy in the general case.  But yeah, any such logic would be once-off in the new lib/env.ts or wherever we put it, and anything importing it would be blissfully unaware of any such abstraction.
This also opens the the door to a more generalized way to deal with the Cloudflare env problem, which getEnv could take into account, along the lines of:
export default {
  fetch(req, env) {
    yahooFinance.setGlobalConfig({ mergeEnv: env });
  }
};

although I haven't thought about it too deeply yet.  How does that look to you as someone more experienced with Cloudflare workers?  We could also check on first getEnv call if the user is in a CloudFlare environment but hasn't set this, in which case we could give a helpful warning.  In any case, let's not jump the gun on settling on anything final yet... you can get started and see what makes sense, works, and feels right; vs what doesn't.  And of course, I'll be around to assist & discuss.  So thanks again, and good luck ;)

Hi, thanks all of you for your wonderful contributions. Really appreciated. 😊🙏🏻
When can we merge this PR and finalize this for CF use?

Hey, @ManasMadrecha.  This is on our radar but unfortunately the PR isn't complete yet.  We're almost there but need a bit more time to finish this up.  Watch this space :)

Right, well that was annoying. I synced the fork and everything got removed 🫠
The fork was pretty far behind, so I'll recreate the PR. I might get the less tricky bits in first then I can noodle more on the env issue

Hey @ManasMadrecha, I have opened a follow up here, with some discussion about the remaining blockers to CF support.
Thankfully the list is shorter than last time I opened this PR 😄


Unexpected type hint required for Date member

It seems from the tests that members of Date type should be automatically deserialized without type hint. However, it didn't deserialize as Date but Object which turns out be something like
new Object('2016-07-29')

Without type hint: deserialize as object
@JsonObject
export class Team {
  @JsonMember
  public createdAt: Date;
}

let json = { createdAt: '2016-07-29' };
let str = JSON.stringify(json);
TypedJSON.parse(str, Team);

With type hint: deserialize as Date
@JsonObject
export class Team {
  @JsonMember({ type: Date })
  public createdAt: Date;
}

Unless I'm missing something, this seems like an issue with TypeScript itself. A string in JSON should deserialize as a Date object if that's the expected type, in which case the Date constructor will be called with the string present in the JSON -- so unless a bug is lurking somewhere affecting this behavior, the problem is caused by TypeScript by not emitting the correct type metadata. I should really add an extensive test-suite for all possible setups, including native types -- something for which I'll have time soon.

Using the type: Date hint on the JsonMember annotation for attributes of type Date causes TypedJSON to emit the following warning in the console:
@JsonMember: 'type' specified for 'MyClass.date_joined' does not match detected type.
The date value from the input JSON is still correctly deserialized into a proper Date instance.
Would there be a way to prevent that warning from being output?

It looks like that behaviour could be related to the use of awesome-typescript-loader for webpack but not to TypeScript itself:
https://github.com/s-panferov/awesome-typescript-loader/issues/214

Well that explains a few things. Thank you for taking the time to look around.

Knowing the above, it would be nice to be able to suppress that warning from being output on the console when the type declared in metadata does not match the user-declared type.
Maybe this warning isn't needed?
https://github.com/JohnWhiteTB/TypedJSON/blob/master/src/typed-json.ts#L825
I believe an acceptable behaviour would be to assume the user is correct when explicitly declaring a type using the type attribute on @JsonMember annotation, and use the declared type's constructor anyways... like it's doing right now.

The new version will once again display warnings, but only if the set type option is not a subtype of the detected type. This should never warn about false positives, as everything is a subtype of Object.

I would be useful to be able to somehow set global type hints or global type converters.
For example when I'm using the following generic class, sometimes I'd like to use MinMax<number> and sometimes MinMax<Date>, but at the moment I don't know how I can use the Date one as there's no way for me to add @JsonMember({type:Date}).
@JsonObject
export class MinMax<T> {
  @JsonMember
  public min: T;
  @JsonMember
  public max: T;

  constructor(min?: T, max?: T) {
    this.min = min;
    this.max = max;
  }
}

@timfish Generic class support is something that's completely impossible to achieve without having to manually specify the constructor of the generic type as well.
As such, this is not currently planned to be available in TypedJSON 1.0.0, although it is likely to appear in the future, if the type-metadata system in TypeScript remains as rudimentary and primitive as it is today.

@timfish However, constraining the generic type to a base-class should work, if the possible sub-types are also specified through the knownTypes setting.


CI on your own account

@jonesmz , if you set up your own CI environment, the process might become faster.
See https://github.com/redboltz/mqtt_cpp/wiki/CI-rule#setup-ci-on-your-account
That means your branch test on CI that is corresponding to your account before sending a PR.

I activated travis ci on my account.
We'll need to make a modification to the .travis file to support having travis build branches though.

You can close this issue now :-)


Command 'MJML: Screenshot' resulted in an error (command 'mjml.screenshot' not found)

When attempting to take a screenshot of the file via Command Pallet (Ctrl-Shift-P), the above error pops up. No biggie as can take manual screen but looks like a bug.

Specifications
VS Code version: 1.51.1
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-10T23:31:29.624Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 4.15.0-123-generic

MJML extension version: 1.0.1
Operating system and version: Linux x64 4.15.0-123-generic

Installed via extensions UI bog-standard way, little popup said it was updating mjml and completed without issue, everything else seems to work.

My bad,
I looked through the code and can see that the message which says MJML needs to be rebuilt for your current platform. Please wait for the installation to finish... is actually just installing phantom-js and once its done the following shows JML's been updated. Please restart VSCode in order to continue using MJML. - I/one would presume from them messages that its an update and is unrelated to screenshots when it actually works afterwards.
I restarted vs-code and it works fine after some initial boot time the screen size prompt pops up.
My suggestion would be to simply tell the user your installing phantom-js vs saying doing an update, then specifically tell them to restart to enable screenshot functionality, though as long as one actually reads the message and restarts It should be fine.
Did you know phantom-js is deprecated?

It's a fork of first "community" extension here so we've never really looked that part of the extension. PhantomJS is just archived not really deprecated, i'm not sure we really want to re-do that part just for this ?

np, sorry I just saw on npm that it says its deprecated https://www.npmjs.com/package/phantomjs-prebuilt


Consider renaming simulate to semantics

Upon reflection, the word simulate is perhaps not the best choice and maybe we should revert to semantics or some other name that causes less confusion.

I agree that the name is a bit confusing, but semantics is currently what we call our Cava instances when defining circuits, so that particular replacement might cause name collisions. I'm struggling to think of other ideas -- run and interp both seem like they would cause just as much confusion.

Good point. Let's noodle on this a bit: it's not urgent.


[stable/chart/jenkins] Update README.md

What this PR does / why we need it:
fix little issue in readme.
Which issue this PR fixes
/
Special notes for your reviewer:
see/compare value rbac.create

assign @viglesiasce

@jbuettnerbild Thanks for your PR. Looks good to me, but you need to fix DCO before it can be merged.

@torstenwalter
i try to fix DCO but every time i will force push i to remote i got a 403.
if you can cherry pick d9d697d and 8dd8f8a or force push this pr without f5b3fa1 that would very nice.

@jbuettnerbild I can't force push to your branch. You can check if branch protection is enabled for your repository which prevents force pushes. If it doesn't work you can also push to a new branch, close this Or and raise another one. Please check if you need to bump the chart version as I think the version in master increased in the meantime.


Support variable length inputs for crf1d

I fixed crf1d function to support variable length inputs same as #1209. Users need to sort inputs sequences by length.

Hmm... Could you explain the meaning of this extension?
As far as I know, the main reason of supporting variable length inputs for LSTM is to fit specifications and requirements of CuDNN. This PR would be meaningful if such extension is useful for any tasks, however, I have no idea why it is useful.

When I applied the crf1d to POS-tagging task, input sequences (I mean word sequences) has different lengths, and I couldn't apply it (#1375).

Ah I partially understand the motivation, but I felt it is unhelpful due to the lack of documentation.
Please describe about the detail of the specification (shape, type, etc) of an input xs and ys to the documents. Adding a simple sample code to the document would be better.

Thank you. It's a good idea. I'll make a small example in the document to describe the detail.

I updated the document.

Thank you for review. I update it.

Thank you! LGTM 👍


Kotlin version

Why is the kotlin version set at 1.9.22?
The jetified binary version gives a lot of issues that are only solvable if the Kotlin version is updated in the flutter generated android project, although it doesn't seem that you need such kotlin version? (ex of the issue: The binary version of its metadata is 1.9.0, expected version is 1.7.1)
Kotlin version 1.7.10 is more than enough (fits the newest version on the flutter sdk 3.22.0).
If the idea of having a Kotlin version without justification, then it should be lowered to support as much as possible.
If it's some internal google best practice, then it should be reviewed.
If there is some other justification, then correct me please.
https://mvnrepository.com/artifact/com.google.android.recaptcha/recaptcha/18.5.1
in mvn, the kotlin stdlib used is 1.7.0, so I still don't get why the Jars have been compiled with a new kotlin version, making it impossible to include this in .aar generated by flutter without hacking it in.

@naj147 thanks for opening the issue. Unfortunately this is a Google policy and it's not something that we can solve easily internally. Some work is being done to change that behavior but we don't have an idea of the ETA for it yet. In the meantime the Android SDK for recaptcha follows the most recent versions of Kotlin. Sorry if this is causing you trouble we are working as best as possible to support the maximum versions we can.

We have taken this under advisement and there is some internal work going on to use somewhat older kotlin versions.  Keep an eye out for future releases.


[Dataflow Streaming] Enabled Heartbeat by Default

This sets heartbeat work by default and will rollout along next beam release. This CL also refactors and fixed some unit test issues.

assign set of reviewers


[Feature Request] Get affinity with friends

Hello,
First of all, thanks for this interesting project.
I'm wondering if there's a way to get affinity with friends ? If we can use this syntax and get a metric with affinity percentage of each friend that would be great i think. Maybe this issue can be flagged with improvement flag if it's not available right now.
Target code :
# friends info
myfriends = jikan.user(username='Guts__', request='friends')
But anyway great project.

This project is just a Pintos wrapper for the Jikan API, which can be found at https://github.com/jikan-me/jikan. I recommend you make a feature request there, and if it gets implemented I'll add to this wrapper.

Thanks @abhinavk99 , you're right.

Closing since I can't do anything about this.


Fix YTDL from crashing when the query returns a channel.

Some queries only return channels instead of videos, which shouldn't happen.  What should happen is it should search only for videos and return only videos.  as of right now it will only staticaly search for the top result.

#6


Add cucumber support for violating individual constraints

Feature Request
Description of Problem:
With the work in #402 we will be able to choose which constraints/rules within a profile to violate on each execution. We need additional steps in Cucumber to facilitate testing of this.
Potential Solutions:

Introduce new steps for "When I violate 'this rule'" and "When I enforce 'this rule'"

Acceptance Criteria

[ ] The cucumber testing framework will have a new step that allows for violating an individual constraint
[ ] At least one feature with at least one scenario will be written (once #426 has been completed) to assert correct behaviour.

@pdaulbyscottlogic / @MattCline-SL is this task complete?

This issue is no longer correct as it talks about testing selectively violating rules/constraints - this is currently not supported. The testing work for the future selective rule violation will happen in conjunction with the new development.


what‘s the difference of funding address and primary address in wallet.json？

if i want to mint, what adderss should I deposit? does the fund address provide gas for mint and i will receive things i minted in primary adderss?    tks a lot

if you want to mint, you should transfer some bitcoion to the funding address. if you minted, run npm run cli balances. you can find your minted FT or other Atomical items in primary address.

thanks!!


fix(ux): Missing fontFamily setting on new  components

Issue: In some of the new UI - like the <FileItemView /> used in search and diagnostics, and the symbol view - a fontFamily wasn't set, so this would fall back to a default system font in those new pieces of UI, which isn't desirable - which can either cause a mismatching font to show, or not display at all.
Defect: Missed setting the fontFamily parameter on these new elements.
Fix: Set the missing properties.
As a next step, it may make sense to have an <OniText font /> component, that takes a UiFont.t as a required parameter, so it isn't missed elsewhere.

Could this be causing https://github.com/onivim/oni2/issues/2535?

I think it could be, @CrossR !
Although it is surprising that the default font we pick up in Revery wouldn't render. I need to try and see if I can reproduce this to be sure - but given other elements seem to render OK from the screenshot, I suspect this will fix #2535


Http stream

Hello,
let me first thank for an excellent integration to Home Assistant.
I have a small feature request. Based on what I have found, (at least my RLC410) Reolink cameras allow for streaming via http, the url is of the form
http://192.168.x.y/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=USER&password=PASSWORD
Could this be added into the integration? My motivation for this is the ability to play the stream on my TV (Samsung "Smart" TV). While the rtsp and rtmp streams seem not to be compatible, the http stream is.
Thanks in advance.
M.

WebRTC is what you're looking for. This would be hard to implement as an integration as there needs to be a server running to encode/re-encapsulate the stream. Check out this repo. [(https://github.com/vladmandic/stream-rtsp)]
Disable mDNS in Chrome if you have issues.

Thanks for the suggestion, I may try that. I just wanted to point out that the http (FLV) stream is already available out of the box (so hopefully no server-side manipulation needed).
M.


Implements design changes to tags

Implementes the design changes to the tags in app description, fixes #53

Niceee, gj gj gj!! But could we use the right colors for the tags? So if it is [category name] -> gets the right color for the label?


No resources exist on https://storage.googleapis.com/

I'm follow the documentation to install kubeadm,but prompt me “The specified key does not exist.”
run command:
DOWNLOAD_DIR=/usr/local/bin
sudo mkdir -p $DOWNLOAD_DIR
RELEASE="$(curl -sSL https://dl.k8s.io/release/stable.txt)"
cd $DOWNLOAD_DIR
sudo curl -L --remote-name-all https://storage.googleapis.com/kubernetes-release/release/${RELEASE}/bin/linux/${ARCH}/{kubeadm,kubelet,kubectl}
sudo chmod +x {kubeadm,kubelet,kubectl}
documentation:https://kubernetes.io/zh-cn/docs/setup/production-environment/tools/kubeadm/install-kubeadm/

/kind support
@SunsetFeng
it seems that among the command list you listed, the command ARCH="amd64" is missing.
Please try:
run ARCH="amd64" before running sudo curl -L --remote-name-all https://storage.googleapis.com/kubernetes-release/release/${RELEASE}/bin/linux/${ARCH}/{kubeadm,kubelet,kubectl}

/remove-kind bug

thanks,I can get it

It seems that the documentation itself is correct as it has the instruction mentioned above.
/retitle "The specified key does not exist" error while installing kubeadm
/close

From https://github.com/kubernetes/website/issues/36212#issuecomment-1259014457:
/retitle "The specified key does not exist" error while installing kubeadm
/close


Implement watchdog

Should watch for file activity in modules directory and bounce bot process on changes.

Not the solution I wanted, but until bots can delete their own messages, it's what I'm stuck with.

Wrong commit!


[FEATURE] Update Driver to existing Binary of specified GUID

Is your feature request related to a problem? Please describe.
UEFI Firmware build time could take from 15 minutes to 25 minutes (or may be even more) based on the computing capability of the system. Eventually, Iteration to validate changes are slowed down because of the
Describe the solution you'd like

Delete Existing Driver
For Updating Check if Driver can fit in to existing contiguous free space after executing above step or not, Reject update if driver can not fit in to free space
Driver would only updated if and only if below condition met:

same GUID
same Name
Size of New Driver <= Size of Existing Driver + contagious free space

Describe alternatives you've considered
https://github.com/linuxboot/fiano

Can you elaborate more on this issue.
My understanding is it is like a firmware update like capsule update, and my questions further are as follows:

here the variables as GUID should be same as previous driver which is to be deleted to update new one?
since we are new to xmcli so can you please let us know about code related to firmware update already implemented one or this is new feature?
In Uefi we used to use Firmware Management protocol so it will go through GetImage for loading the new image,
CheckImage for Checking if image version/data is correct or not, then SetImage for flashing the firmware. So similar formation or different?


Larger area for light clicks

Checklist:

[ x ] I updated to the latest version available
[ x ] I cleared the cache of my browser

Release with the issue:
Latest
Last working release (if known):
NA
Browser and Operating System:
macOS 12.2 - Safari

Description of problem:
Is there any way to create a large area in order to turn the light in a room on / off? For instance, most of the lights in SweetHome3D are relatively small and getting an exact click with a mouse can be tough. An example would be clicking roughly the middle of the room to make it work.
Things I have tried:

Creating a hidden box in the middle of the room, however the object is not exported
Creating a box in the middle of the room with a transparent png texture, however the box now shows up as a black square in Home Assistant

Javascript errors shown in the web inspector (if applicable):

Additional information:

So I may have found a little workaround. I created two entity's for the same light. One was a tiny square object on the ceiling and the other is the room itself. I set the lumens of the room light to 0, so that the only light showing is from the ceiling.
With that setup, I can click anywhere on the floor in the room to turn on the light. Not sure if this is the best option, but at least it works!
`

entity: light.office_light
action: default
type3d: light
object_id: Office_Light_2
light:
lumens: '2000'
decay: '1'
distance: '300'
shadow: 'yes'
vertical_alignment: top
- entity: light.office_light
action: default
type3d: light
object_id: room_4_1
light:
lumens: '0'
color: white
decay: '2'
distance: '0'
shadow: 'no'
`

Hello @dtjohnson90, you also have the gesture entity that can do the same as what you have done but consuming one less light (you know that the number of light is limited).
an example of gesture for your office light can be:
  -  entity: light.office_light
     type3d: gesture
     object_id: room_4_1
     gesture:
        domain: light
        service: toggle

That's exactly what I was looking for! Thank you!


Lingering Alerts

It seems that Spell Alerts may stay for longer than expected if an aura fades during a loading screen.
There are several ways to fix this:

implement #57 (maybe with a shorter duration e.g., 20-30 seconds after leaving combat)
register events triggered by loading screen, and check if buffs are lost
upon activation, each aura starts a ticker (e.g. every 2 seconds) and check if aura is still here

The first solution is arguably the best one, because it fixes naturally the issue, without a dedicated code to maintain.

Fixed in #76.
The chosen solution was mostly the second one:

register events triggered by loading screen, and check if buffs are lost

Please read the Pull Request details or more information.
The first solution was insufficient, because it would only cover issues with SAOs, not issues with GABs.
The third solution would have probably caused a lot of trouble, cf. PR details which showcases some major issues.


flutter add-to-app module aar build failure exit code not propagated

we are building a flutter add-to-app module on our CI server but when the flutter build fails, it does not fail the aar build. So the CI server says the build has succeeded while it actually failed.
Steps to Reproduce

create add-to-app module
make sure the build fails (introduce compile error in dart code)
build the android artifact for add-to-app module

Expected results:
I expected to build to fail , i.e. return a non-zero exit code
Actual results:
The output tells me the build has failed but the exit code is 0 (see logs)

Logs
C:\system9\flutter\kwsc_flutter_module>flutter build aar  --no-profile --no-release
Running Gradle task 'assembleAarDebug'...
Running Gradle task 'assembleAarDebug'... Done                     12,0s

lib/injection_container.dart:104:9: Error: No named parameter with the name 'registrationFingerprint'.
        registrationFingerprint: credentials['secret'],
        ^^^^^^^^^^^^^^^^^^^^^^^
../auth_classic/lib/domain/entities/classic_credentials.dart:19:3: Context: Found this candidate, but the arguments don't match.
  ClassicCredentials({
  ^^^^^^^^^^^^^^^^^^

FAILURE: Build failed with an exception.

* Where:
Script 'C:\programs\flutter\packages\flutter_tools\gradle\flutter.gradle' line: 904

* What went wrong:
Execution failed for task ':flutter:compileFlutterBuildDebug'.
> Process 'command 'C:\programs\flutter\bin\flutter.bat'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 11s

Gradle task assembleAarDebug failed with exit code 0.

Flutter 1.22.4 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 1aafb3a8b9 (3 weeks ago) • 2020-11-13 09:59:28 -0800
Engine • revision 2c956a31c0
Tools • Dart 2.10.4

C:\system9\flutter\kwsc_flutter_module>flutter doctor -v
[√] Flutter (Channel stable, 1.22.4, on Microsoft Windows [Version 10.0.18363.1198], locale nl-BE)
    • Flutter version 1.22.4 at C:\programs\flutter
    • Framework revision 1aafb3a8b9 (3 weeks ago), 2020-11-13 09:59:28 -0800
    • Engine revision 2c956a31c0
    • Dart version 2.10.4
    • Pub download mirror http://droid:4000

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\programs\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_SDK_ROOT = C:\programs\Android\sdk
    • Java binary at: C:\programs\Java\jdk8u162_64bit\bin\java
    • Java version Java(TM) SE Runtime Environment (build 1.8.0_162-b12)
    • All Android licenses accepted.

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.

I can't seem to reproduce
> flutter build aar
Running Gradle task 'assembleAarDebug'...
Running Gradle task 'assembleAarDebug'... Done                     24.8s

lib/main.dart:16:1: Error: 'make' isn't a type.
make it crash
^^^^
lib/main.dart:16:6: Error: Expected ';' after this.
make it crash
     ^^
lib/main.dart:16:9: Error: 'crash' isn't a type.
make it crash
        ^^^^^
lib/main.dart:17:3: Error: Expected ';' after this.
  runApp(
  ^^^^^^
lib/main.dart:21:6: Error: Expected ')' before this.
    ),
     ^

Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /Users/xster/.pub-cache/hosted/pub.dartlang.org/espresso-0.0.1+7/android/src/main/java/androidx/test/espresso/flutter/EspressoFlutter.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

FAILURE: Build failed with an exception.

* Where:
Script '/Users/xster/development/flutter/packages/flutter_tools/gradle/flutter.gradle' line: 900

* What went wrong:
Execution failed for task ':flutter:compileFlutterBuildDebug'.
> Process 'command '/Users/xster/development/flutter/bin/flutter'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 23s

Gradle task assembleAarDebug failed with exit code 0.

[✓] Flutter (Channel master, 1.24.0-8.0.pre.373, on Mac OS X 10.15.7 19H15 darwin-x64, locale en)
    • Flutter version 1.24.0-8.0.pre.373 at /Users/xster/development/flutter
    • Framework revision 8de72126e9 (6 days ago), 2020-11-26 07:48:03 +0800
    • Engine revision 20caf54969
    • Dart version 2.12.0 (build 2.12.0-76.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/xster/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/xster/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.2, Build version 12B45b
    • CocoaPods version 1.10.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio
    • Android Studio at /Applications/Android Studio 4.2 Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.51.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (5 available)
    • Pixel 3 (mobile) • 8AXX11BS6                                • android-arm64  • Android 11 (API 30)
    • iPhone (mobile)  • cdcd493527f1f25a0ac91106540cf58186f2b4f0 • ios            • iOS 14.2
    • macOS (desktop)  • macos                                    • darwin-x64     • Mac OS X 10.15.7 19H15 darwin-x64
    • Web Server (web) • web-server                               • web-javascript • Flutter Tools
    • Chrome (web)     • chrome                                   • web-javascript • Google Chrome 87.0.4280.67

• No issues found!

Hi @xster , thanks for the fast response.
I think you did manage to reproduce the problem.
Here you have the flutter build failing:
> Process 'command '/Users/xster/development/flutter/bin/flutter'' finished with non-zero exit value 1
and here you have the gradle build succeeding (last line):
Gradle task assembleAarDebug failed with exit code 0.
although the message says "failed", it does return with exit code 0 which indicates success. I would expect the gradle build to return with a non-zero exit value or in case of the flutter build failure, maybe even the exit value from the flutter build.

ah 🤦♂ right. I understand now

Looks like the tool exit at https://github.com/flutter/flutter/blob/25986102c141513939fac49c824568c478610b52/packages/flutter_tools/lib/src/android/gradle.dart#L669 didn't propagate further than the try catch here https://github.com/flutter/flutter/blob/25986102c141513939fac49c824568c478610b52/packages/flutter_tools/lib/src/android/android_builder.dart#L61 and still got a success at https://github.com/flutter/flutter/blob/25986102c141513939fac49c824568c478610b52/packages/flutter_tools/lib/src/commands/build_aar.dart#L132

Seems like a side-effect of https://github.com/flutter/flutter/pull/41946. This needs a test.
PRs welcome :) Otherwise we'll get to it at some point.

thanks for the tips @xster . i think it was a simple bug, see my PR#71582 . I am not sure how to begin writing a test for this. Would you have some pointers for me? thanks


chore: bdd-nh-1592559574 to 0.0.1

chore: Promote bdd-nh-1592559574 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


ERROR    Warning: Cannot update a component from inside the function body of a different component.

this error show if i used onchange function to update state, im used hooks component for with this

It's not an error but a warning:
https://reactjs.org/blog/2020/02/26/react-v16.13.0.html#warnings-for-some-updates-during-render
Anyway this shouldn't happen with a proper onChange function, because it doesn't get called on the first render, but only when menu is opened or closed...
What are you passing to onChange prop?


Add Craig Rautenbach to Contributors list

My first contribution to open source software, hello open source!

Hi  @craig8two, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

Hey @Roshanjossey , thank you for merging my commit. This is my very first contribution after reading your post on Medium. The tutorial was easy and straight forward and I am elated that I have taken the first step to contributing to open source projects.
Can you explain what the following means:
You’re all set—the craig8two:add-craig8two branch can be safely deleted.
Thanks so much!

@craig8two, you can delete branches you create once it's purpose is complete
I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://goo.gl/PM1Jdh


Fix db name and config

#206
Summary of changes:
- Modified code to use `mlpipeline` database name as before.
- Added type to config file pushed.

CI is failing due to Grafana charm issue


ERROR: XHR failed. Technical details: {"name":"Error","message":"XHR failed"}

File Downloader extension now active.
Starting download from https://*****.bz2
ERROR: XHR failed. Technical details: {"name":"Error","message":"XHR failed"}

Thanks @alan-wr for reporting this issue. As of today, from what we've seen, this error seems to be related to network issues and the VS Code API we rely on doesn't provide us much more information.
Here is the issue we logged on their side to investigate this: https://github.com/microsoft/vscode/issues/108760
In parallel, we're considering moving to another API to bypass these errors in the future.
Could you please provide more context about this from your side? When do you get this error?

Thanks @daniv-msft for reply it.
About
const progressCallback = (downloadedBytes: number, totalBytes: number | undefined)
I found the variable totalBytes does not get real number.
How can I improve it?

@alan-wr Yes, this is unfortunately a known issue while we move to the other API I was mentioning above. The present API, provided by VS Code, doesn't give us this information. I expect that we'll switch to the new API in the coming weeks, but that has other implications we are reviewing carefully.

Many Thanks @daniv-msft for reply it.
So I hope I can get new API ASAP some day.
Thanks your hard work.

Use file-download to download same URL, does not get XHR failed.
But it not support progress and unzip.
https://www.npmjs.com/package/file-download

  var request = req.get(file, function(response) {

    if (response.statusCode === 200) {

      mkdirp(options.directory, function(err) {
        if (err) throw err
        var file = fs.createWriteStream(path)
        response.pipe(file)
      })

    } else {

      if (callback) callback(response.statusCode)

    }

    response.on("end", function(){
      if (callback) callback(false, path)
    })

    request.setTimeout(options.timeout, function () {
      request.abort()
      callback("Timeout")
    })

  }).on('error', function(e) {

    if (callback) callback(e)

  })

@alan-wr We just got an update on the issue logged on VS Code side. Getting the network logs would help investigating this further.
Would it be possible for you to:

Close all VS Code windows.
Open a command prompt.
Run code --log-net-log=<some-absolute-path>/netlog.json to start VS Code and asking it to record network logs.
Reproduce the XHR issue you see with our extension.
Attach your logs to this issue.

That would be helpful to understand more of what goes wrong in this case.

What do you replace  with?
I am having this problem as well. Fresh install on Ubuntu 20


Tracks memory pool stats (eden, survivor, tenured, etc.)

This, along with https://github.com/etsy/statsd-jvm-profiler/pull/18 closes https://github.com/etsy/statsd-jvm-profiler/issues/17

Question about this. There is also a type field to denote on/off heap. I wasn't sure how to best add that to the metric name. Ideally you could graph all heap pools together on one graph.

What do you think of having the metrics like heap.total, heap.eden, etc and group them that way?
Doing this would require some changes to the dashboard, but that should be pretty straightforward.

Additionally I believe there might be spaces in the pool names. Is it best to replace them with a hyphen?

Yeah, replacing the spaces with hyphens is good.

Ah so you mean like:
heap.total.{init, used, committed, max}
heap.eden.{init, used, committed, max}
I like that.

Yeah, those metric names look good.

Ok I updated the metric names and I took a crack at fixing the visualizer. Let me know if I missed anything.

Looks great, thanks again for this!


Timestamp is from filebeat processing, not actual mail.log

Hello,
I managed to set things up following the README file, but I realized today that the timestamp inserted in Elasticsearch is not the one from the mail.log file, it's from Filebeat's time of precessing.
Is there something extra to do to prevent filebeat / logstash from overwriting the original timestamp?

You might look at https://github.com/whyscream/postfix-grok-patterns/blob/54618d75501d1e98c227f4d18b5b75891a459d65/ALTERNATIVE-INPUTS.md.
Are you sure the timestamp isn't correct?

Thanks, I didn't spot the extra 'timestamp' in the link you provided (compared to the README instruction of this repo).
I guess it should work, it appears to achieve the same than what I ended up doing in my 48-beats-postfix-prepare.conf (while being more simple):
filter {
  if [postfix] {
    grok {
      match => { "message" => "%{SYSLOGTIMESTAMP:syslog_timestamp} %{SYSLOGHOST} %{DATA:program}(?:\[%{POSINT}\])?: %{GREEDYDATA:message}" }
      overwrite => "message"
    }
    date {
      match => [ "syslog_timestamp" , "MMM dd HH:mm:ss" , "MMM  d HH:mm:ss" ]
      remove_field => [ "syslog_timestamp" ]
    }
  }
}

Closing this.


implementaton of 1.0.0-rc1 shows error

Trying to implement react-router in my project and i am getting following errors:

Warning: React.createElement: type should not be null or undefined. It should be a string (for DOM elements) or a ReactClass (for composite components).
Warning: Only functions or strings can be mounted as React components.
Uncaught TypeError: Cannot read property 'toUpperCase' of undefined

routes.js file:
var React = require('react');
var ReactRouter = require('react-router');
var Router = ReactRouter.Router;
var Route = ReactRouter.Route;

var Home = require('./components/home.js');
var Jobs = require('./components/jobs.js');
var JobDetail = require('./components/jobDetail');
var App = require('./components/app.js');
var About = require('./components/about.js');
var NotFoundPage = require('./components/notfoundpage.js');

var routes = (<Router>
    	<Route path="/" component={App}>
    		<Route path="jobs" component={Jobs}>
    			<Route path="jobs-detail" component={JobDetail} />
    		</Route>
    		<Route path="*" component={NotFoundPage} />
    	</Route>
  	</Router>);

module.exports = routes;

app.js file:
var React = require('react');
var ReactRouter = require('react-router');
var Router = ReactRouter.Router;
var routes = require('./routes');

React.render(<Router>{routes}</Router>, document.body);

+1

You should not put nested <Router> in your <Router>:
<Router>
    <Router>
       <Route>
    </Router>
</Router>

Must remove <Router> from your routes

I encountered the same issue with this:
import React from 'react'
import { Router, Route, IndexRoute } from 'react-router'
import createBrowserHistory from 'react-router/node_modules/history/lib/createBrowserHistory'
export class App extends React.Component {
	render() {
        let history = createBrowserHistory()
        return (
            <Router history={history}>
                <Route path="/" component={Index}>
                    <Route path="" component={Home} />
                    <Route path="indeks-permohonan" component={TableRequest} />
                    <Route path="indeks-work-order" component={TableEngineer} />
                    <Route path="*" component={NotFound} />
                </Route>
            </Router>
            )
	}
}

@rosnk as @chentsulin mentioned you wrapped Router inside Router which is not correct.
@cliche7 first of all use the History (how to use it). The second thing is, your route: <Route path="" component={Home} /> has no path, you should use IndexRoute.

I has the same issue

@datnq201088 ,I finally manage to make it work. If you are still facing this problem this might help beside this post:
http://stackoverflow.com/questions/32730518/basic-implementaton-of-react-router-1-0-0-rc1-shows-error/32779523#32779523


数据集支持多轮对话反馈吗

Feature request
PPO, does the dataset support multi-turn dialogue feedback, such as I have a multi-turn dialogue dataset, and at different steps, the model's responses are all rated
Motivation
Does the dataset support multi-turn dialogue feedback?
Your Contribution
PPO, does the dataset support multi-turn dialogue feedback, such as I have a multi-turn dialogue dataset, and at different steps, the model's responses are all rated

Please use english only

Probably linked to #2127. Closing as the title is not in English and the question isn't clear enough for us to help you. Feel free to open a clearer issue the complies with our guidelines


Rebase to version 10.3.20 from Fedora 31

Keep extra SST method wsrep_sst_rsync_tunnel

Note: I haven't test building it yet locally (and I don't have CBS credentials either).

Note: I haven't test building it yet locally (and I don't have CBS credentials either).

doesn't build yet with mock, I'll push an update shortly

OK I can build that version of the PR locally with mock -r epel-7-x86_64.
We can start reviewing it for merge.
Next I'd like to use those generated package in a kolla build to make sure it generates mariadb container images properly. Trying to figure out how to mimick what RDO does.

@dciabrin do we want to skip this update for EL7 and do it only for EL8 ?
CentOS8 RDO Trunk is now available and we plan to switch master to EL8 only.
CC @amoralej

actually, for EL8 there might be new enough mariadb module?

@apevec @amoralej if we plan to still run some jobs on centos7 I'd like to push this update because it contains a fix for galera on ipv6.
Otherwise the version of mariadb that ships with centos8 might be enough already.

if we plan to still run some jobs on centos7 I'd like to push this update because it contains a fix for galera on ipv6.

centos7 says for RDO releases older than Train, which releases are you targeting this?

@dciabrin @apevec for centos8 we should keep using the mariadb packages included in the centos module. For centos7, it'd be good to switch to newer mariadb in master (until removed), train and previous versions as we'll keep running ci on centos7 for stable/train and older.
Also this will allow to unpin puppet-mysql and having a version which supports both centos7 and centos8 (currently we are forced to have different puppetfiles in packstack and p-o-i for centos7 and centos8 upstream.

if we plan to still run some jobs on centos7 I'd like to push this update because it contains a fix for galera on ipv6.

centos7 says for RDO releases older than Train, which releases are you targeting this?

If memory serves, I personally want this for Stein because we needed to generate a galera config that listens to ::* when ipv6 is enabled, otherwise the version of mariadb/galera we use errors out.
Looking at @amoralej 's comment, we might want to deploy it on older release to improve the situation with puppet-mysql as well.


Fix query with lots of nullable columns creating stack overflow

This is a test for https://github.com/cmeeren/Facil/issues/9

I think there could be some other places let getItem is rendered so I'll update them

@cmeeren I have run the code gen on my project that was that was throwing the stack overflow and it now works :)

Thanks a lot!


digitalocean: Add RBAC policies

Fix: #572

Tested by @lloeki (role.yaml was slight changed from verbs: ["create", "get", "delete"] to verbs: ["get"])
/area digitalocean

/lgtm


Support for V1 of the Jira API

Right now we support V2, which was released in the beginning of 2012. V1 support would be :+1:

Looks like I don't need v1 support! It actually works perfectly for me when I make the request myself (I redacted some bits with ????):
POST https://developer.????.org/jira/rest/api/2/issue
Accept: */*
Content-Type: application/json
Authorization: Basic ????==
Accept-Language: en-us
Accept-Encoding: gzip, deflate

{
    "fields": {
       "project":
       {
          "key": “????”
       },
       "summary": "ARGHHHHHH",
       "issuetype": {
          "name": "Task"
       }
   }
}

Content-Type: application/json;charset=UTF-8
X-Seraph-LoginReason: OK
Set-Cookie: JSESSIONID=????; Path=/jira; HttpOnly, atlassian.xsrf.token=????; Path=/jira
Server: nginx/1.0.0
X-AREQUESTID: 998x106518x1
X-ASEN: SEN-2000971
Transfer-Encoding: Identity
Content-Encoding: gzip
Cache-Control: no-cache, no-store, no-transform
Date: Mon, 10 Aug 2015 23:38:10 GMT
X-AUSERNAME: aarko
Connection: keep-alive
X-ASESSIONID: artmlu
X-Content-Type-Options: nosniff
Vary: User-Agent

{"id":"27945","key”:”????-113","self":"https://developer.????.org/jira/rest/api/2/issue/27945"}

Seems like the Jira plugin doesn't actually work:
$ coffee plugins/jira/index.coffee --host='https://developer.????.org/jira' --projectKey=???? --issueType="Task" --username=aarko --password='????'
Error firing notification
 { status: 404, message: undefined, body: {} }

Somewhat related, when I tried to use the global-tunnel npm package to redirect the HTTP request through a debugging proxy, I got this exception:
TypeError: Request path contains unescaped characters.
  at new ClientRequest (_http_client.js:73:11)
  at TunnelingAgent.exports.request (http.js:49:10)
  at TunnelingAgent.createSocket (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/global-tunnel/node_modules/tunnel/lib/tunnel.js:116:25)
  at TunnelingAgent.createSecureSocket [as createSocket] (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/global-tunnel/node_modules/tunnel/lib/tunnel.js:188:41)
  at TunnelingAgent.addRequest (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/global-tunnel/node_modules/tunnel/lib/tunnel.js:80:8)
  at new ClientRequest (_http_client.js:154:16)
  at Object.exports.request (http.js:49:10)
  at Object.globalTunnel._defaultedAgentRequest (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/global-tunnel/index.js:211:38)
  at Object.exports.request (https.js:136:15)
  at Object.globalTunnel._defaultedAgentRequest (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/global-tunnel/index.js:211:38)
  at Request.request (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/superagent/lib/node/index.js:541:28)
  at Request.set (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/superagent/lib/node/index.js:215:8)
  at Request.auth (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/superagent/lib/node/index.js:494:15)
  at Function.Jira.jiraRequest (/Users/andre/src/bugsnag/bugsnag-notification-plugins/plugins/jira/index.coffee:46:8)
  at Function.Jira.openIssue (/Users/andre/src/bugsnag/bugsnag-notification-plugins/plugins/jira/index.coffee:103:6)
  at Function.Jira.receiveEvent (/Users/andre/src/bugsnag/bugsnag-notification-plugins/plugins/jira/index.coffee:124:8)
  at Function.module.exports.NotificationPlugin.fireTestEvent (/Users/andre/src/bugsnag/bugsnag-notification-plugins/notification-plugin.coffee:158:6)
  at Object.<anonymous> (/Users/andre/src/bugsnag/bugsnag-notification-plugins/notification-plugin.coffee:239:10)
  at Object.<anonymous> (/Users/andre/src/bugsnag/bugsnag-notification-plugins/notification-plugin.coffee:1:1)
  at Module._compile (module.js:460:26)
  at Object.loadFile (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/coffee-script/lib/coffee-script/register.js:16:19)
  at Module.load (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:310:12)
  at Module.require (module.js:365:17)
  at require (module.js:384:17)
  at Object.<anonymous> (/Users/andre/src/bugsnag/bugsnag-notification-plugins/plugins/jira/index.coffee:1:22)
  at Object.<anonymous> (/Users/andre/src/bugsnag/bugsnag-notification-plugins/plugins/jira/index.coffee:1:1)
  at Module._compile (module.js:460:26)
  at Object.exports.run (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/coffee-script/lib/coffee-script/coffee-script.js:119:23)
  at compileScript (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/coffee-script/lib/coffee-script/command.js:207:29)
  at compilePath (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/coffee-script/lib/coffee-script/command.js:160:14)
  at Object.exports.run (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/coffee-script/lib/coffee-script/command.js:95:21)
  at Object.<anonymous> (/Users/andre/src/bugsnag/bugsnag-notification-plugins/node_modules/coffee-script/bin/coffee:7:41)
  at Module._compile (module.js:460:26)
  at Object.Module._extensions..js (module.js:478:10)
  at Module.load (module.js:355:32)
  at Function.Module._load (module.js:310:12)
  at Function.Module.runMain (module.js:501:10)
  at startup (node.js:129:16)
  at node.js:814:3

If that's true, maybe Jira is returning a 404 because the plugin isn't escaping the URL correctly?

We've rewritten our JIRA plugin so I'm hopeful this is fixed. If its not and you're having issues can you ping a support request to us and we can take a look!


Multiple Components in same file

Hi, I have several small Modal components defined in the same .ts file, this works fine in 0.0.23. but when I upgraded to 0.0.30 I noticed that any components after the first one are not getting template inlined etc. The src remains templateUrl: "home-modal.html" and the app fails to load the template.
I was just wondering if this is expected behaviour. I can just separate these into individual files if need be.

No this is a bug, we'll get it fixed up in the next release. Thanks for creating the issue.


DSPy.Suggest halts execution instead of continuing

Reproduction
import dspy

class Repro(dspy.Signature):
    """Product some text that includes numbers. Be sure to include numbers from 1 to 10."""

    input = dspy.InputField()
    body = dspy.OutputField(format=str)

def contains_a_number(output):
    contains = []
    for x in range(0,10,2):
        if str(x) in output:
            contains.append(str(x))

    return contains

class SectionWriter(dspy.Module):
    def __init__(self):
        super().__init__()
        self.prog = dspy.ChainOfThought(Repro)

    def forward(self, input):
        result = self.prog(input=input)
        body = result.body

        nums = contains_a_number(body)
        message = "Avoid these numbers: " + ", ".join(
            nums
        )
        as_bool = len(nums) <= 1

        dspy.Suggest(as_bool, message)
        return dspy.Prediction(body=body)

gpt3 = dspy.OpenAI(
    model="gpt-3.5-turbo",
    max_tokens=4000,
    model_type="chat",
    api_base="http://<IP_ADDRESS>:4000/",
)
with dspy.context(lm=gpt3):
    SectionWriter().forward(input="something")

Result
ERROR:dspy.primitives.assertions:2024-05-04T04:17:51.517685Z [error    ] SuggestionFailed: Avoid these numbers: 0, 2, 4, 6, 8 [dspy.primitives.assertions] filename=assertions.py lineno=111

    111         dspy.logger.error(f"SuggestionFailed: {self.msg}")
--> 112         raise DSPySuggestionError(
    113             id=self.id,
    114             msg=self.msg,
    115             target_module=self.target_module,
    116             state=dsp.settings.trace,
    117             is_metric=self.is_metric,
    118         )
    119 else:
    120     raise ValueError("Suggestion function should always return [bool]")

DSPySuggestionError: Avoid these numbers: 0, 2, 4, 6, 8

Expectation
That it continues executing. I expect it to (a) find the numbers and (b) complain about them. But shouldn't it just continue executing? I get the same error if I am trying to run an optimization as well.
Thoughts
I think there might be a bug in the implementation of Suggestions but I'm not sure.
I followed the docs quite closely and have the simplest example - shouldn't this just keep executing?

Hi @bllchmbrs , thanks for raising this. Activating DSPy Assertions/Suggestions actually requires wrapping the SectionWriter class with the backtracking/Retry logic. This will ensure that when the Suggestion is flagged with a failure in the validation function, this will trigger the corresponding Retry logic.
Feel free to reference this part of the documentation and let me know if this helps!
from dspy.primitives.assertions import assert_transform_module, backtrack_handler

baleen_with_assertions = assert_transform_module(SimplifiedBaleenAssertions(), backtrack_handler)

# backtrack_handler is parameterized over a few settings for the backtracking mechanism
# To change the number of max retry attempts, you can do
baleen_with_assertions_retry_once = assert_transform_module(SimplifiedBaleenAssertions(),
    functools.partial(backtrack_handler, max_backtracks=1))

Alternatively, you can also directly call activate_assertions on the program with dspy.Assert/Suggest statements using the default backtracking mechanism (max_backtracks=2):
baleen_with_assertions = SimplifiedBaleenAssertions().activate_assertions()

In your case, you could do:
from dspy.primitives.assertions import assert_transform_module, backtrack_handler

section_writer_with_assertions = assert_transform_module(SectionWriter(), backtrack_handler)
section_writer_with_assertions(input="something"))

There also some relevant Assertions FAQs that you may find relevant (and that I will update in the documentation soon to make it more clear!).

Thank you! Will give this a try and will open a PR for the docs too.
Appreciate your help!
On Sat, May 4, 2024 at 15:20 arnavsinghvi11 @.***>
wrote:

Hi @bllchmbrs https://github.com/bllchmbrs , thanks for raising this.
Activating DSPy Assertions/Suggestions actually requires wrapping the
SectionWriter class with the backtracking/Retry logic. This will ensure
that when the Suggestion is flagged with a failure in the validation
function, this will trigger the corresponding Retry logic.
Feel free to reference this part of the documentation and let me know if
this helps!
from dspy.primitives.assertions import assert_transform_module, backtrack_handler
baleen_with_assertions = assert_transform_module(SimplifiedBaleenAssertions(), backtrack_handler)
backtrack_handler is parameterized over a few settings for the backtracking mechanism
To change the number of max retry attempts, you can do
baleen_with_assertions_retry_once = assert_transform_module(SimplifiedBaleenAssertions(),
functools.partial(backtrack_handler, max_backtracks=1))
Alternatively, you can also directly call activate_assertions on the
program with dspy.Assert/Suggest statements using the default backtracking
mechanism (max_backtracks=2):
baleen_with_assertions = SimplifiedBaleenAssertions().activate_assertions()
In your case, you could do:
from dspy.primitives.assertions import assert_transform_module, backtrack_handler
section_writer_with_assertions = assert_transform_module(SectionWriter(), backtrack_handler)
section_writer_with_assertions(input="something"))
There also some relevant Assertions FAQs
https://github.com/stanfordnlp/dspy/issues/434 that you may find
relevant (and that I will update in the documentation soon to make it more
clear!).
—
Reply to this email directly, view it on GitHub
https://github.com/stanfordnlp/dspy/issues/965#issuecomment-2094462501,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMRAB3ODZ7TNQMIUUUCTC3ZAVNJHAVCNFSM6AAAAABHGP5NEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJUGQ3DENJQGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Ok, this is much clearer to me.
As I mentioned, I am happy to help out with the docs. May I make a proposal here that includes some of the suggestions in #434 ?
I think that Assertions/Suggestions are an exciting aspect of DSPy and want as many people as possible to understand and use them.

This has been a very helpful thread.  It made several things click for me.
I'm still a little confused with the functools.partial
I'm probably just importing something correctly.

The functools partial just changes the backtracker function so that you can modify the number of retries. That's just a python thing. You don't need to set it otherwise.

Hey all, is this complete or pending something?

This is complete
On Mon, May 20, 2024 at 03:23 Omar Khattab @.***> wrote:

Hey all, is this complete or pending something?
—
Reply to this email directly, view it on GitHub
https://github.com/stanfordnlp/dspy/issues/965#issuecomment-2120149078,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMRAB3BPWGTE4GDOYJVM5LZDHFKFAVCNFSM6AAAAABHGP5NEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGE2DSMBXHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Here: baleen_with_assertions = SimplifiedBaleenAssertions().activate_assertions(),
can I pass the max_backtracks=n like that: SimplifiedBaleenAssertions().activate_assertions(max_backtracks=n)?


Try using jax.random.binomial

Following https://github.com/google/jax/pull/18228
But the jax.random.binomial can only be used in the jax version equal to or higher than 0.4.21. So the CUDA 11 should still use numpyro's _binomial_dispatch.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

23 of 38 (60.53%)  changed or added relevant lines in 1 file are covered.
26 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 84.805%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

appletree/randgen.py
23
38
60.53%

Files with Coverage Reduction
New Missed Lines
%

appletree/randgen.py
26
71.5%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
2266

Relevant Lines:
2672

💛  - Coveralls


Schedule refreshdata.py to run daily and deploy changes automatically

Once the missing data are added and refreshdata.py is able to update all the data sources without any manual intervention, it'd be nice to have it run automatically daily without any user input.
Since the Dokku server has no persistent storage (it is overwritten on every new deploy), I was thinking we could maybe use github actions to do this (e.g. using https://jasonet.co/posts/scheduled-actions/). We'd setup a schedule event to run refreshdata.py daily and commit the updated data files back to the repo.
I've set up a workflow that will automatically deploy the deploy branch to the Dokku server (https://github.com/jeremymoreau/covid19mtl/blob/master/.github/workflows/main.yml)

Totally agree.
Cool, didn't know such things were possible with GitHub actions. I was going to offer to run this with a cronjob on my server or Raspberry Pi. But something independent could be better to avoid relying on someone specific.
I am currently running this on my Raspberry Pi every day at 23:00. Currently, requests from certain networks seem to be blocked (see https://github.com/jeanpaulrsoucy/covid-19-canada-gov-data/issues/61) so this might also affect GitHub actions. I notified Santé Montreal about this.

Sounds good, seems like we'd have to test whether github actions' servers are being blocked. Another (maybe simpler) possibility is adding a worker processes to the Procfile to have it run on the dokku server (which is hosted on a DigitalOcean VM in Toronto, so maybe less likely to be blocked).
Procfile format
https://devcenter.heroku.com/articles/procfile
A Procfile declares its process types on individual lines, each with the following format:
<process type> : <command>
<process type> is an alphanumeric name for your command, such as web, worker, urgentworker, clock, and so on.
<command> indicates the command that every dyno of the process type should execute on startup, such as rake jobs:work.


Add a GNAP authorization request and a ZCAP response for the operations in the spec

We need someone to provide a PR that adds a GNAP authorization request and a ZCAP response for the operations in the spec.

specially JSON for each operation request and capability... for example:
As a user I can request the ability to create a resource with GNAP.
AS a system I can grant the ability to create resources with a ZCAP.


Use update_column instead of update_attribute to prevent callbacks

As the title already indicates, I prefer using update_column instead of update_attribute to prevent additional callbacks in the model. This could of course be a breaking change for some users so it is good to think about this carefully. On the other hand I do not really see a situation where you want the changing counter cache to perform some additional actions through callbacks.
In addition to skipping callbacks, this change also prevents the objects to be touched (set updated_at). More information can be found in this blog.
Looking forward to hear other opinions on this.

@StefSchenkelaars Hey, thanks for the pull request. I guess I'm not sure exactly why callbacks need to be altogether avoided here. Having the Counter#updated_at column touched seems like a good thing to me and is pretty much the only reason that column is there. If you don't want it updated, then why not just remove the column? Triggering callbacks also allows people to add them if they need to, but not triggering them at all would pretty much remove that option for anyone using the gem. Perhaps I'm overlooking something, but would be happy to hear your reasoning here.

I see a counter cache purely as a tool to prevent N+1 queries. It only has caching purposes and thus should not affect the app otherwise which is similar to how the rails' counter caches and counter_culture work. If you want to update the updated_at column if you update a child model, you should use the touch: true option on the belongs_to relation.


update test to handle django-1.10 change in FileField storage

in django < 1.10 the file_field.name starts with a ./ whereas in 1.10 it is the basename. Hence the idea to make the test pass on both situations.

How about adding a comment indicating that basename can be removed when support for Django <= 1.9 is dropped?

Merged (with comment added as suggested) in 865841eedfa09e5c64b76046e71049f4a731e934. Thanks!