feat: allow exposure of ports on internal service only

What does this PR do?
Allow exposing ports to the internal service, while not exposing them on the default service at the same time.
Motivation
Currently the exposed ports of the internal service always match those of the default service. However, it may be useful to expose certain ports to the internal service (e.g. the metrics or traefik port created by default), as the internal service primary usage is most likely some kind of exposure of endpoints to more trusted clients only.
More

[x] Yes, I updated the tests accordingly
[x] Yes, I ran make test and all the tests passed

In the current form of this PR, it looks like an hidden feature. Wdyt about adding an example in either EXAMPLE.md or in values.yaml ?

Added them to values.yaml to make them more visible to make them more visible! Adding them to the examples is possible, but might be slightly too much given that I think this is a very niche feature that won't be that relevant to much people.


publishing the code

Hello,
Thank you for your paper and I am really interested in your work.
When will you publish the code?

Hi, thank you for your interest! I am cleaning the code (and at the same time busy with another work). The inference code can be released in 1~2 weeks, and then the training may come in one month.  If you drop me an email, I would be happy to email you when the code is released.

Hi, thank you for your interest! I am cleaning the code (and at the same time busy with another work). I plan to release the inference code within the next 1-2 weeks, and the training within one month. If you'd like to be notified when the code is available, please feel free to send me an email (jundanluo22@gmail.com), and I'll be happy to update you as soon as it's released.

Thanks!


Using scipy's genetic algorithm for initial parameter estimation in gradient descent

I see you are writing Python code for optimization on GitHub. A general problem for gradient descent and other non-linear algorithms - particularly for more complex equations - is the choice of initial parameters to start the "descent" in error space. Without good starting parameters, the algorithm will stop in a local error minimum. For this reason the authors of scipy have added a genetic algorithm for initial parameter estimation for use in gradient descent. The module is named scipy.optimize.differential_evolution.
I have used scipy's Differential Evolution genetic algorithm to determine initial parameters for fitting a double Lorentzian peak equation to Raman spectroscopy of carbon nanotubes and found that the results were excellent. The GitHub project, with a test spectroscopy data file, is:
https://github.com/zunzun/RamanSpectroscopyFit
If you have any questions, please let me know. My background is in nuclear engineering and industrial radiation physics, and I love Python, so I will be glad to help.

Thanks for bringing this to my attention.
So far, I have used Python library only for linear and logistic regression (binary classification) but I used the scikit-learn's default model fitting algorithm, so it is not in my hand.
The gradient descent code I wrote for linear regression is not in Python but Octave/MATLAB. I could definitely use a better initialization. However, because I used it for linear regression only where gradient descent with sufficiently small learning rate is almost guaranteed to find global minima, I did not pay too much attention to initialization.
I will focus on the initialization problem again when I use Python or MATLAB for back-propagation algorithm in multi-layer neural networks. I'll write to you later then.

OK.


TGCF App version issue

I have installed TGCF app version on Digital Ocean cloud. I'm seeing under Run tgcf is running latest version 1.1.8 but under advanced tab version and Platform is showing Running tgcf 1.1.7.post1. Also, tgcf is forwarding same message multiple time even no new message on group.
Also, I have noticed below error message  on advanced tab configuration.
AttributeError: 'LiveSettings' object has no attribute 'sequential_updates'
Traceback:
File "/venv/lib/python3.10/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 564, in _run_script
exec(code, module.dict)
File "/venv/lib/python3.10/site-packages/tgcf/web_ui/pages/6_🔬_Advanced.py", line 37, in
"Enforce sequential updates", value=CONFIG.live.sequential_updates

this was fixed in tgcf 1.1.8

@aahnik How you instal 1.1.8 version on DigitalOcean?
Thanks


adding pre panel rendering to tabs

Description

Implementing a new render fragment is placed between the toolbar and panels. This is comparable to the address line in modern browsers where there is a space between tabs and the actual content.

How Has This Been Tested?

I've created a unit test to validate the base functionality and all other unit tests pass. Currently, there is no example for the docs, but the visual implications are zero, If the RenderFragment is not set, there is no change in the DOM for the existing tabs.
Types of changes

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

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

10/10 illustration, insta approve!

Just a reminder: the commit message format we agreed on is: Tabs: add pre panel rendering


fail to use the kubefedctl tool to join clusters vie GKE

What happened:
kubefedctl join cluster3 --cluster-context cluster3  --host-cluster-context cluster3 --v=2
I0528 12:33:03.979080   32537 join.go:161] Args and flags: name cluster3, host: cluster3, host-system-namespace: federation-system, kubeconfig: , cluster-context: cluster3, secret-name: , dry-run: false
F0528 12:33:04.056096   32537 join.go:128] Error: Error retrieving FederationConfig "federation-system/federation-v2": no matches for kind "FederationConfig" in version "core.federation.k8s.io/v1alpha1"

What you expected to happen:
Join sucessfully
How to reproduce it (as minimally and precisely as possible):
1 Create a GKE cluster with version 1.12.7-gke.10
2 Follow the kubefed guide via gke
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version)
K8s:

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b
08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:23:09Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:
"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.7-gke.10", GitCommit:"8d9b8641e72cf7c96efa61
421e87f96387242ba1", GitTreeState:"clean", BuildDate:"2019-04-12T22:59:24Z", GoVersion:"go1.10.8b4", Compiler:"gc",
 Platform:"linux/amd64"}

helm version (use helm version)
helm:

Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}

kubefed version
0.1.0-rc2
Install method (helm vs script)
helm

/kind bug

@yongzhedamaoxian Previous pre-release versions of kubefed are not supportable.  Please reopen this bug if you can reproduce it against v0.1.0-rc2 or greater.

@yongzhedamaoxian Previous pre-release versions of kubefed are not supportable. Please reopen this bug if you can reproduce it against v0.1.0-rc2 or greater.

I have changed.Please reopen

@yongzhedamaoxian Ah, now the error is clear to me. It appears that you are using an outdated version of kubefedctl.  Please use the version of kubefectl corresponding to the release you are targeting (i.e. v0.1.0-rc2).

@yongzhedamaoxian Ah, now the error is clear to me. It appears that you are using an outdated version of kubefedctl. Please use the version of kubefectl corresponding to the release you are targeting (i.e. v0.1.0-rc2).

ok.Let me try

@yongzhedamaoxian Ah, now the error is clear to me. It appears that you are using an outdated version of kubefedctl. Please use the version of kubefectl corresponding to the release you are targeting (i.e. v0.1.0-rc2).

ok.Let me try

thank you.I have made it

@yongzhedamaoxian Glad to hear!  Does that mean this issue can be closed?

@yongzhedamaoxian Glad to hear! Does that mean this issue can be closed?

Yes!!


fix: new message type added in solidity

Description:
Commit Message
feat: solidity implemention of new message flow

see the guidelines for commit messages.
Changelog Entry
version: <log entry>

Checklist:

[x] I have performed a self-review of my own code
[ ] I have documented my code in accordance with the documentation guidelines
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have run the unit tests
[ ] I only have one commit (if not, squash them into one commit).
[ ] I have a descriptive commit message that adheres to the commit message guidelines

Please review the CONTRIBUTING.md file for detailed contributing guidelines.

A lot of non needed console logs are left in the PR.< Otherwise just one minor comment.
Is there anything we can add to types to make creating these messages more like Java Otherwise we can leaves this for later. But eventually we might want functions to aid dapp developers in creating these messages.

I don't think, It would be efficient, creating messages like java in contract, but we can add functions for the dapp developers!


gitqlient: 1.4.3 -> 1.5.0

Description of changes
Update to version 1.5.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 179616 run on x86_64-linux 1

1 package built:

gitqlient

Hash is mismatching again. (On a new host. I moved from computer.) Maybe because of 'fetchSubmodules := true;'. Is that really required? (I haven't tested. Just reporting the output of nixpkgs-review.)

Now it builds for me, no errors.

Hash is mismatching again. (Tested on a new host. I moved computers.) Maybe it is because of 'fetchSubmodules := true;'. Is that really required? (I haven't tested. Just reporting the output of nixpkgs-review.) I'm not sure why it shows this way to me in two different hosts. I'll have a new look into this when I'm free.

With release 1.5.0, the source code includes 4 submodules (from the same author). It seems that enabling fetchSubmodules is not enough to use the module revision at the moment of the release, and the most recent revision is used.
Instead of enabling fetchSubmodules, I am going to download each submodule directly, using the revision linked to in the main source code at the released tag.


adding a locking test case

the test case passes, but it shouldn't as the lock is still acquired? Reading more into how mortice works, maybe the test is not running in the WebWorker context.
:thinking-face:

I haven't run this test but from what I can see this passes because getFirstEntry breaks out of the await for..of which ends the generator and causes the lock to be released.
I think you might be able to create a deadlock by trying to acquire a write lock during a read lock:
// getMany opens a (shared) read lock
for await (const block of helia.blockstore.getMany(someAsyncCIDEmitter)) {
  // gc opens a (exclusive) write lock, but needs to wait for the read lock to be released
  await helia.gc()
}

To break the deadlock there should be some sort of timeout mechanism used while trying to acquire a lock - passing a AbortSignal.timeout for example.

Again, I haven't run it but awaiting gc before getFirstEntry is called might do the same thing:
const retrieved = await storage.getMany(cidsGenerator())
await helia.gc() // might cause deadlock?
const firstEntryFromRetrieved = await getFirstEntry(retrieved)

@whizzzkid : what is motivating this work?  I'm not seeing any discussion in the PR or to a linked issue.  I'm not saying we shouldn't do the work, but it would be good to have the context on why we're prioritizing this currently.

Is this still relevant to keep open given 4 months in draft?

I'm going to close this because there's been no movement in almost a year.  I think yes, if you mis-use async generators you can get yourself into trouble but this is a bug in the consumer's code, not the internal implementation.


Probably unnecessary function calls in expanded form

If I understand correctly, this code wraps type in a vector and does a call to expanded-form to make it be processed by code in this cond case.
If what I wrote is correct, then I think these two calls are unnecessary, because process-properties and process-items of result is already performed in recursive call to expanded-form here.

Sorry, the links are not pointing to the right lines anymore.
Would you mind linking the original commit.
Thanks.

Updated issue description. Below are code snippets, maybe this will help.

      (map? type)                             ;; simple inheritance
                                              (let [result (expanded-form-inner (assoc type-node :type [type]) context)]
                                                (-> result
                                                    (process-properties context)
                                                    (process-items context)
                                                    (assoc :type (first (:type result)))))

      ;; Multiple inheritance
      (and (not (map? type))
              (coll? type))

                                                    (process-properties context)
                                                    (process-items context)


Invalid xref

1 invalid cross reference(s) ""<xref:microsoft.quantum.canon.multim>"".

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

ID: f4b49265-01d4-14a7-6f5a-e9ba694eb84f
Version Independent ID: a3f1f416-68eb-0f14-78b4-086ef74bdbb6
Content: Q# standard libraries - prelude
Content Source: articles/libraries/standard/prelude.md
Product: quantum
GitHub Login: @QuantumWriter
Microsoft Alias<EMAIL_ADDRESS>

This has been fixed in #525. Thank you for reporting it!


Add new web3modal, Reuse active websocket  connection for sign v2

Description
Replaces legacy qrcode-modal with standalone version of new web3modal. Added guard to not create / initiate new WalletConnect provider every time connect method is called in v2, as same socket can be reused.
Additional Information

[x] I read the contributing docs (if this is your first contribution)

Your ENS/address: asimetriq.eth

@jxom I addressed your comments, plus ran the tests, everything seems to be ok, however I'll keep this in draft for now until I can figure out how to test everything properly in wagmi docs site (questions in our chat). Gancho also added some new changes to universal-provider that clean up and optimise websocket subscriptions, will be adding that new version in latter on as well during docs site tests.

@jxom This one should be ready for review now. Updated universal-provider and managed to set up example docs to test everything. New modal is now in place for v2 (still using old one for v1 as it is pre bundled into ethereum-provider).
I attempted to refactor that getProvider method, but didn't end up with anything cleaner to be fair, however made it less nested in terms of if statements. Will return to this once we deprecate v1, as a lot can be removed then.

@jake as per our chat on improving loading times, I added these changes
Main issue was actually with that initial loading of universal-provider, so what I did is start loading / initialising it in constructor. Similarly, we start loading / initialising web3modal there as well. This gives chance to start importing associated files before user clicks on a "connect button".
I added few utils that check for readiness of everything just in case user manages to click on "connect button" before everything is loaded up (i.e. 3g networks).
In terms of preloading data within modal, it is already relatively optimised i.e we use cloudflare workers to deliver it at the edge / cache is in place / we only fetch first few wallets that are needed for initial display. While we are also preloading images, these are non-blocking in terms of opening modal. Loading ui here is usually on a "connect button" itself.


[MINOR]: Generate empty column at placeholder exec

Which issue does this PR close?

Closes #.
Rationale for this change
Currently, if there is no column at the place holder exec, it generates at least one dummy column. This causes inconsistency in the subsequent schemas for some edge cases. (Where schema of the PlaceHolderExec itself has 0 columns, but generated RecordBatch from this schema has single column.) Thanks @comphead for bringing this to my attention.

What changes are included in this PR?
This PR fixes above mentioned problem.

Are these changes tested?
Yes new test is added. Which is the test in the discussion

Are there any user-facing changes?

Thanks @mustafasrepo  and @Dandandan


Add throwing support to MultipartFormData builders

[x] I've read, understood, and done my best to follow the *CONTRIBUTING guidelines.

Problem
When creating a multipart form data request, there is no place for custom encoding errors using Alamofire's APIs. Sometimes we need to convert images into data which can potentially return nil. In these scenarios it would be convenient to throw an error at this layer rather than wrapping AFError to use our own custom error type.
Feature Request
Add throws to MultipartFormData building closures on the session's upload functions. This also requires adding a case customEncodingFailed(error: Error) to MultipartEncodingFailureReason for capturing any errors that are thrown via the closure.
Value to Alamofire
I think this is something missing from Alamofire, as the other request / upload functions support throws via ParameterEncoder's encode function. However, there is no equivalent mechanism for MultipartFormData.

I misunderstood this feature request initially, as pointed out in #3512. If you want to handle errors while producing a MultpartFormData value, don't use the builder closure, just produce the value directly while handling errors and upload it using .upload(multipartFormData:) directly.

You correctly understood the feature request. The contributor implementing a fix for this misunderstood the feature request. Can I re-open this?

Before reopening, can you provide an example of the APIs you'd like to see added?


autoscroll does not work

why not auto scroll when I type and finish line? How do I fix this error?

What do you mean by "finish line"? When you press enter? Does this only happen after 5 lines?

eg: http://stackoverflow.com/questions/22315755/ios-7-1-uitextview-still-not-scrolling-to-cursor-caret-after-new-line

Can't reproduce.


Allow none for host field of OTUSequence

Changes:

When host is None converts it to instead return an empty string

Please add a test for this behaviour.
Done!

Does this definitely not work? host: str | None = Field(default="")

Yeah that works. Wrote the first one assuming that mongo would return host: None when no host is null. But I think mongo will just leave the field undefined


Update Calico Ubuntu guide to use v1.3.0

Updates the Calico ubuntu / systemd guide to use Kubernetes v1.3.0 (when it is released) and adds NetworkPolicy support.

@caseydavenport would you assign a tech reviewer who has the domain knowledge to review this?

@matchstick Assigned to you for triage.  Is this something the cluster team should look at?

Going to close this for now - will be revisiting soon.

@caseydavenport I apologize for missing this. Do you still need a reviewer?


Questions about dataset

Hello, I want to know overall organization of your dataset.
For example, there are 50 files with a filename starting with 0_0_ and 25 files with a filename starting with 0_2_.
Why they are different?
Also, I couldn't understand why there are  275 files with a filename starting with 11_15_.
What does the gesture ID 11 mean in your dataset?
I thought you considered 11 different gestures so that the gesture ID value is between 0 and 10.
Thank you.

I Update the readme and add a few lines about the dataset arrangement.
In short, the 2 in file name like 0_2_* means the gesture collection session ID. It could be a session collected by different people or different session of a same people. Different session could have different number of files.
Gesture ID 11 is background class. I suggest you collect your own background class for proper training.


Not able to bootstrap the project

Hi,
I'm trying to bootstrap this project but I have some issues:

I downloaded the zipped project https://github.com/Nethereum/Unity3dSimpleSampleNet461
I opened it with Unity 2020.3.20f1 (few versions ahead of 2020.3.15f1) so I upgraded the project
During this process Unity told me there are errors so I entered in Safe mode and I have this log

I tried to download https://github.com/JamesNK/Newtonsoft.Json/releases/tag/13.0.1
and kept the net45 folder

Now I have these new errors

Then I stopped looking for some help :)
I'm not sure if I'm doing something wrong, any kind of help is very welcome, thanks!

@giggioz Hello there! Did you manage to find a solition for this issue?

Hi, no, I've found two solutions for Unity:
https://chainsafe.github.io/game-docs/
or Moralis (there are several tutorials on youtube)
https://www.youtube.com/watch?v=wjqDSH29ZKk

Hi, no, I've found two solutions for Unity: https://chainsafe.github.io/game-docs/ or Moralis (there are several tutorials on youtube) https://www.youtube.com/watch?v=wjqDSH29ZKk

Thank you very much for sharing!


Completed UI Testing for 2 features

UI Testing completed for Search and Detail feature.
Further service abstraction required for OAuth token in said features.
Further testing will be added to other features later in the project if time permits.
Files and stubs added for recommendations feature

Codecov Report

Merging #24 into develop will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           develop     #24   +/-   ##
=======================================
  Coverage     11.8%   11.8%
=======================================
  Files           22      22
  Lines         1347    1347
=======================================
  Hits           159     159
  Misses        1188    1188

Ignoring codecov


⚠ Turnos 24x7 has degraded performance

In 99370c0, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 814 ms

Resolved: Turnos 24x7 performance has improved in f294ae4.


add Tesla K80 benchmarks

This seems to be by far the most commonly allocated GPU for a free-tier Google Colab user at the current time.

Yep, looks good to me.


| 01D9FE327X6PFAKDNA0PZ5B6P8 | 27-04-2019 10:00:00 | 27-04-2019 12:00:00 | 2h0m0s   | 38h0m0s    | 213,612    | 29,592,910    | 332,990    | 1          | false       | prometheus=monitoring/k8s,prometheus_replica=prometheus-k8s-0 | 0s         | sidecar   |
| 01D9FMYSEKPAX4MX4BMBH4MB7S | 27-04-2019 12:00:00 | 27-04-2019 14:00:00 | 2h0m0s   | 38h0m0s    | 212,585    | 30,700,681    | 336,785    | 1          | false       | prometheus=monitoring/k8s,prometheus_replica=prometheus-k8s-1 | 0s         | sidecar   |
| 01D9FMYSFWNNQZ5RGNWBMKSRJA | 27-04-2019 12:00:00 | 27-04-2019 14:00:00 | 2h0m0s   | 38h0m0s    | 216,861    | 30,707,278    | 341,060    | 1          | false       | prometheus=monitoring/k8s,prometheus_replica=prometheus-k8s-0 | 0s         | sidecar   |
| 01D9FVTGPK193J313FSVF63KSG | 27-04-2019 14:00:00 | 27-04-2019 16:00:00 | 2h0m0s   | 38h0m0s    | 211,739    | 31,016,908    | 338,579    | 1          | false       | prometheus=monitoring/k8s,prometheus_replica=prometheus-k8s-1 | 0s         | sidecar   |
| 01D9FVTGQWSHE6HTGMA1SY5QHZ | 27-04-2019 14:00:00 | 27-04-2019 16:00:00 | 2h0m0s   | 38h0m0s    | 216,422    | 31,025,516    | 343,263    | 1          | false       | prometheus=monitoring/k8s,prometheus_replica=prometheus-k8s-0 | 0s         | sidecar   |
level=info ts=2019-04-27T18:12:23.459985189Z caller=main.go:185 msg=exiting
```

This looks to me like the simplest configuration error - All Prometheus sources uploading blocks from Prometheus instances that has exactly the same label (wrong - labels has to be unique). Is that the case?

Interesting...yes I see that now.  I've deleted all the duplicate blocks that I could find and the compactor appears to be running smoothly again.  I'll continue to monitor it over the next few days and make sure it doesn't start writing multiple blocks again.
Can you think of any reason Thanos would be writing out two blocks from each replica?  At this point its hard to determine whether it was a Thanos issue or a configuration issue since the prometheus-operator obfiscates a lot of the specific configuration of the resources.

Did you set TSDB min block time to be equal to the TSDB max block time? Perhaps local compaction wasn't off. We do check this now in the newer versions if Sidecar is configured to upload blocks.

So I cleared out all of the duplicate blocks and the compactor ran fine for a day, but when I checked again the following day there were a bunch of duplicates again.  I cleared them all out again and changed the image to version 0.4.0-rc.1 and it's been running fine ever since.  I think it may have been due to something in the older version.  The compactor has been running fine for the last few days now, so I'll close this ticket.  Thanks for everyone's help!

Also I met the same problem, my compactor image improbable/thanos:v0.5.0 , below is my thanos compactor yaml in k8s,  i delete the conflict chunks in S3, but it only works temporarily.
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: thanos-compactor
  namespace: monitoring
spec:
  replicas: 1
  selector:
    matchLabels:
      app: thanos-compactor
  serviceName: thanos-compactor
  template:
    metadata:
      labels:
        app: thanos-compactor
    spec:
      containers:
      - args:
        - compact
        - --log.level=debug
        - --data-dir=/var/thanos/store
        - --objstore.config=$(OBJSTORE_CONFIG)
        - --wait
        env:
        - name: OBJSTORE_CONFIG
          valueFrom:
            secretKeyRef:
              key: thanos.yaml
              name: thanos-objstore-config
        image: improbable/thanos:v0.5.0
        name: thanos-compactor
        ports:
        - containerPort: 10902
          name: http
        volumeMounts:
        - mountPath: /var/thanos/store
          name: data
          readOnly: false
      volumes:
      - emptyDir: {}
        name: data
  volumeClaimTemplates: []

@chrisghill In your message where you pasted the output of thanos bucket inspect, do you mind pointing out where you see duplicate blocks of data due to the Prometheus instances having the same labels?
I'm having the same problem but I cannot figure it out. My labels look unique:
cluster=azure-production,prometheus=monitoring/prometheus-operator-prometheus,prometheus_replica=prometheus-prometheus-operator-prometheus-0

cluster=azure-production,prometheus=monitoring/prometheus-operator-prometheus,prometheus_replica=prometheus-prometheus-operator-prometheus-1


 As passed by Accept header the expected reponse body type is application/vnd.abiquo.acceptedrequest+json; version=3.8

The edit VM responses work as follow:

If the VM is deployed, the response will be the task to track this action (202 with task)
If the VM is not deployed, there is no task and no response will be retrieved (204).

Support for different responses (204 with no content; 202 with task) in UpdateVirtualMachine operation implemented (see 64e6085550eabb8b195cb03781cb7e25fa315a25)


Swift install instructions?

Would be super awesome :)

Swift implementation can be seen on my Fork: https://github.com/mccannmax/Touchpose
Pull requested

@toddreed this issue has been merged in #15 can you close?


Fix logging in operator

Fixes https://github.com/istio/istio/issues/26411
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ff253640c4cfaa3fea287a5649016097270ab8e4
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ff253640c4cfaa3fea287a5649016097270ab8e4
link
/test release-notes_istio

release-test_istio
ff253640c4cfaa3fea287a5649016097270ab8e4
link
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

In response to a cherrypick label: new pull request created: #27933


Add appplatform samples

Thanks for your contribution! Please let us know what problems this PR addresses or what functionality it adds. Please link to other related issues and PRs to speed up review. Thank you!

/azp where

/azp where

/asp list

/azp list


Feature Request: Give all possible type information.

Right now we either have this:
julia> # exercise the codepath in searchsorted* methods for ranges that check for zero step range

julia> immutable ConstantRange{T} <: Range{T}
          val::T
          len::Int
       end

help?> ConstantRange
search: ConstantRange

DataType   : ConstantRange{T}
  supertype: Range{T}
  fields   : [:val,:len]

Or this:
julia> @doc """
       # `ConstantRange`

       Exercise the codepath in `searchsorted*` methods for
       ranges that check for **zero** step range.
       """ ->
       immutable ConstantRange{T} <: Range{T}
          val::T
          len::Int
       end

help?> ConstantRange
search: ConstantRange

     ConstantRange

  Exercise the codepath in searchsorted* methods for ranges that check for zero step range.

It would be nice if we could have both of these type definitions help info by default:
julia> @doc """
       # `ConstantRange`

       Exercise the codepath in `searchsorted*` methods for
       ranges that check for **zero** step range.
       """ ->
       immutable ConstantRange{T} <: Range{T}
          val::T
          len::Int
       end

help?> ConstantRange
search: ConstantRange

     ConstantRange

  Exercise the codepath in searchsorted* methods for ranges that check for zero step range.

DataType   : ConstantRange{T}
  supertype: Range{T}
  fields   : [:val,:len]

Yes, we can definitely add more information automatically. Though we shouldn't completely overload a user with too many details all at once.
This is probably most relevant to Lexicon though, particularly the 0.2 planning issue https://github.com/MichaelHatherly/Lexicon.jl/issues/109 and the display planning issue https://github.com/MichaelHatherly/Lexicon.jl/issues/118.
Docile already collects all the information necessary, it's just a matter displaying it nicely.

For documenting things in base people have been using bare docstrings in places, which Docile can already handle:
julia> import Lexicon

help?> Base.checkstring

checkstring (generic function with 3 methods)
Docile: updating package list...
Docile: caching 73 modules from 'Base'.

[function]

Base.checkstring

  Validates and calculates number of characters in a UTF-8,UTF-16 or UTF-32
  encoded vector/string
  ...

I'm not sure what the policy is currently though, whether to using @doc or bare docstrings.

That is awesome! I agree that overloading the user is not the way to go, but it would be useful to have both API and implementation details, just not too much of both at the same time:

Virtue lies in the Middle Way


Error installing plugs in Git Bash

All mah :PlugInstall's fail in Command Prompt, with errors about missing find, and cd having too many arguments. Could the :PlugInstall implementation be refactored to not rely so much on GNU coreutils, but use Vim capabilities instead? That would help improve cross-compatibility with Windows environments.
.vimrc: https://github.com/mcandre/dotfiles/blob/224cc2109d95d3fd53e95d83a8b664623f9caf93/.vimrc
System:
vim --version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Apr 23 2017 19:48:19)
MS-Windows 32-bit console version
Included patches: 1-586
Compiled by mool@tororo
Huge version without GUI.  Features included (+) or not (-):
+acl             +ex_extra        -mouseshape      +tag_old_static
+arabic          +extra_search    +multi_byte      -tag_any_white
+autocmd         +farsi           +multi_lang      -tcl
-balloon_eval    +file_in_path    -mzscheme        +termguicolors
-browse          +find_in_path    -netbeans_intg   -tgetent
++builtin_terms  +float           +num64           -termresponse
+byte_offset     +folding         +packages        +textobjects
+channel         -footer          +path_extra      +timers
+cindent         +gettext/dyn     -perl            +title
+clientserver    -hangul_input    +persistent_undo -toolbar
+clipboard       +iconv/dyn       -postscript      +user_commands
+cmdline_compl   +insert_expand   +printer         +vertsplit
+cmdline_hist    +job             +profile         +virtualedit
+cmdline_info    +jumplist        -python          +visual
+comments        +keymap          -python3         +visualextra
+conceal         +lambda          +quickfix        +viminfo
+cryptv          +langmap         +reltime         +vreplace
+cscope          +libcall         +rightleft       +wildignore
+cursorbind      +linebreak       -ruby            +wildmenu
+cursorshape     +lispindent      +scrollbind      +windows
+dialog_con      +listcmds        +signs           +writebackup
+diff            +localmap        +smartindent     -xfontset
+digraphs        -lua             +startuptime     -xim
-dnd             +menu            +statusline      -xpm_w32
-ebcdic          +mksession       -sun_workshop    -xterm_save
+emacs_tags      +modify_fname    +syntax
+eval            +mouse           +tag_binary
   system vimrc file: "$VIM\vimrc"
     user vimrc file: "$HOME\_vimrc"
 2nd user vimrc file: "$HOME\vimfiles\vimrc"
 3rd user vimrc file: "$VIM\_vimrc"
      user exrc file: "$HOME\_exrc"
  2nd user exrc file: "$VIM\_exrc"
       defaults file: "$VIMRUNTIME\defaults.vim"
Compilation: cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32  -DFEAT_CSCOPE  -DFEAT_JOB_CHANNEL      -DWINVER=0x0501 -D_WIN32_WINNT=0x0501  /Fo.\ObjCi386/ /Ox /GL -DNDEBUG  /Zl /MT -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_HUGE /Fd.\ObjCi386/ /Zi
Linking: link /RELEASE /nologo /subsystem:console /LTCG:STATUS oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib  comdlg32.lib ole32.lib uuid.lib /machine:i386  /nodefaultlib libcmt.lib  user32.lib          WSock32.lib  /PDB:vim.pdb -debug

with errors about missing find, and cd having too many arguments.

vim-plug does not internally use find command, so I'm not really sure how you got the error. What were the exact error messages?

Why use set shell=bash\ -i unconditionally, even in Windows?

https://github.com/junegunn/vim-plug/pull/860 is merged which should resolve this issue (assuming that git bash is installed correctly and %PATH% is updated correctly). Use scoop to install git and busybox (for bash and Unix utils) if the situation persists.


Send payment receipt exactly once

Fix #2598

Idk if it's 100% correct, the docs are light on details. But i think it's close enough at least.


How to get error message from onError

Hi,
If I return an error respond from server for example this one
 return Response::json(['error' => 'Error msg'], 404); // Status code here
The above code is a response using Laravel, anyway how can I get error message from onError Calback?
I don't know how to get it from args ,Is it even possible?
thanks

All arguments provided to fail handler by your ajax call will be as an array in args field as it's stated in the docs http://js-grid.com/docs/#onerror.
onError: function(e) {
    console.log("Error message: " + e.args[0]);
}


conflicts with PostCSS plugins

For some reason adding this module prevents the styles from being processed by PostCSS.

Sorry for the long delay. Other PostCSS options should now be left intact. Thanks for the report.


For Kernel to Client connectivity for things like observers - we should support a load balancing system

When we call back to the client for observers, it should be supporting a load balancing system with the endpoints registered for the client (identified by MicroserviceId). It should then have a configurable strategy for calling back:

Round robin
Random

Going away in v10. We’re going gRPC.


Version 0.6.5 - IndexError: list index out of range

Hi,
I am using the 0.6.5 version on my Raspberry Pi 3 running Home Assistant 0.108.3 on docker.
In some occasions, the temperature sensor stops working and I usually restart my Pi to fix the problem.
Overnight here is the issue that I found in the logs. After that time the temp sensor has stopped updating.
2020-04-17 00:00:00 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/mitemp_bt/sensor.py", line 689, in update_ble
    discover_ble_devices(config, aeskeys)
  File "/config/custom_components/mitemp_bt/sensor.py", line 670, in discover_ble_devices
    sensors[f_i], mac, config, formaldehyde_m_data[mac], fdec=3
IndexError: list index out of range

I'm happy to provide additional inputs if required.

Hello! Thanks for reporting.
What sensors do you use? Is there a formaldehyde sensor among them?

Please also show the contents of the file <HA folder>/custom_components/mitemp_bt/const.py and try to reinstall component.

Hi! I have in my apartment 1 temp/humidity sensor LYWSDCGQ and 3 Mi Flora HHCCJCY01, but those 3 plant sensors are still using the default miflora integration in Home Assistant (and they are actually still updating the values now even if LYWSDCGQ stopped after the error).
Here is  the content of const.py:
"""Constants for the Xiaomi passive BLE monitor sensor integration."""

# Configuration options
CONF_ROUNDING = "rounding"
CONF_DECIMALS = "decimals"
CONF_PERIOD = "period"
CONF_LOG_SPIKES = "log_spikes"
CONF_USE_MEDIAN = "use_median"
CONF_ACTIVE_SCAN = "active_scan"
CONF_HCI_INTERFACE = "hci_interface"
CONF_BATT_ENTITIES = "batt_entities"
CONF_ENCRYPTORS = "encryptors"
CONF_REPORT_UNKNOWN = "report_unknown"

# Default values for configuration options
DEFAULT_ROUNDING = True
DEFAULT_DECIMALS = 1
DEFAULT_PERIOD = 60
DEFAULT_LOG_SPIKES = False
DEFAULT_USE_MEDIAN = False
DEFAULT_ACTIVE_SCAN = False
DEFAULT_HCI_INTERFACE = 0
DEFAULT_BATT_ENTITIES = False
DEFAULT_REPORT_UNKNOWN = False

"""Fixed constants."""

# Sensor measurement limits to exclude erroneous spikes from the results
CONF_TMIN = -40.0
CONF_TMAX = 60.0
CONF_HMIN = 0.0
CONF_HMAX = 99.9

# Xiaomi sensor types dictionary for adv parser
XIAOMI_TYPE_DICT = {
    b'\x98\x00': "HHCCJCY01",
    b'\xAA\x01': "LYWSDCGQ",
    b'\x5B\x04': "LYWSD02",
    b'\x47\x03': "CGG1",
    b'\x5D\x01': "HHCCPOT002",
    b'\xBC\x03': "GCLS002",
    b'\x5B\x05': "LYWSD03MMC",
    b'\x76\x05': "CGD1",
    b'\xDF\x02': "JQJCY01YM"
}

# Sensor type indexes dictionary
# Temperature, Humidity, Moisture, Conductivity, Illuminance, Formaldehyde, Battery
# Measurement type T  H  M  C  I  F  B   9 - no measurement
MMTS_DICT = {
    'HHCCJCY01' : [0, 9, 1, 2, 3, 9, 9],
    'GCLS002'   : [0, 9, 1, 2, 3, 9, 9],
    'HHCCPOT002': [9, 9, 0, 1, 9, 9, 9],
    'LYWSDCGQ'  : [0, 1, 9, 9, 9, 9, 2],
    'LYWSD02'   : [0, 1, 9, 9, 9, 9, 9],
    'CGG1'      : [0, 1, 9, 9, 9, 9, 2],
    'LYWSD03MMC': [0, 1, 9, 9, 9, 9, 2],
    'CGD1'      : [0, 1, 9, 9, 9, 9, 2],
    'JQJCY01YM' : [0, 1, 9, 9, 9, 2, 3]
}

I'll delete the component from HACS and reinstall it as well.

Hmm... I have no explanation yet. I can’t imagine a situation that could lead to this error...
If reinstalling the component did not help, then replace the contents of the sensor.py file with the contents of the attached file:
sensor.py.txt
reboot HA, wait for the error in the log with the text "IndexError!", and show the next entry after it.

I just restarted HA and it's working again. It usually takes a few hours or even days to before it fails but I will keep you posted if it happens again, and I'll try your new sensor file then.

OK, thank you.

I found where I remembered your nickname from - it was a strange problem with malformed/corrupted messages. I suspect that now we could run into something similar.
Then the issue was resolved by tightening the verification of messages for validity, and it is likely that now we are faced with something that passed through this verification.
Now I have a deep night. Tomorrow I will prepare the code for deeper debugging because I suspect that the code from my previous post will not clarify the situation...

It just failed again after only being up for 2 hours. The error is the exact same.
I am going to try with the code you provided earlier and see if there is more details coming up in the logs.

@camfrout I forgot to mention that the code from this file will no longer drop out with an error - it will just write to the log, so if you wait for the component to fail, then do not wait, just look from time to time in the log...

OK. It hasn't failed yet and there is no error in the logs so far, but I'll keep you posted.

Hi! The error showed twice in the past 6 hours. Here is the output.
First one:
2020-04-18 14:22:05 ERROR (SyncWorker_15) [custom_components.mitemp_bt.sensor] IndexError!
2020-04-18 14:22:05 ERROR (SyncWorker_15) [custom_components.mitemp_bt.sensor] f_i = 9, data = [4.92]

Second one:
2020-04-18 16:48:30 ERROR (SyncWorker_10) [custom_components.mitemp_bt.sensor] IndexError!
2020-04-18 16:48:30 ERROR (SyncWorker_10) [custom_components.mitemp_bt.sensor] f_i = 9, data = [5.28]

I don't own any Formaldehyde sensor but I live in a building with many units and sometimes can see Bluetooth devices from my neighbours.

OK. Thank you.
I prepared a new debugging code for your situation:
sensor.py.txt
As before, it should not fail, but there will be more detailed messages in the log. Please try it.

Hi! The new version is failing though, unfortunately. I got the following error in the logs and the component stopped working after.
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/mitemp_bt/sensor.py", line 697, in update_ble
    discover_ble_devices(config, aeskeys)
  File "/config/custom_components/mitemp_bt/sensor.py", line 508, in discover_ble_devices
    data = parse_raw_message(msg, aeskeyslist, report_unknown)
  File "/config/custom_components/mitemp_bt/sensor.py", line 329, in parse_raw_message
    res, mblogged = parse_xiaomi_value(xvalue, xvalue_typecode)
TypeError: cannot unpack non-iterable NoneType object

Oh, yes, I see...
Please, try this one:
sensor.py.txt

Hi again. Here is the error:
2020-04-19 13:29:40 ERROR (SyncWorker_19) [custom_components.mitemp_bt.sensor] Formaldehyde message: 043e23020100003e79d8a8654c17020106131695fe5020aa01443e79d8a8654c1000023102b3
2020-04-19 13:29:40 ERROR (SyncWorker_19) [custom_components.mitemp_bt.sensor] Current result dict: {'rssi': -77, 'mac': '4C65A8D8793E', 'type': 'LYWSDCGQ', 'packet': 68, 'formaldehyde': 5.61}
2020-04-19 13:29:40 ERROR (SyncWorker_19) [custom_components.mitemp_bt.sensor] Parsed formaldehyde data: {'rssi': -77, 'mac': '4C65A8D8793E', 'type': 'LYWSDCGQ', 'packet': 68, 'formaldehyde': 5.61}

Unless you need more debug log I might go back to the previous version that was not breaking the component when there was an error. With today's version the component broke after the error.

Your last log is enough for now. Give me some time - I'll try to figure out what's going on here...

OK. I published 0.6.6-beta, designed to solve your problem.
Please try it.
You can install using HACS by turning on betas:

Thanks! I'll give it a go and will let you know.

Quick update to let you know that the component has been working with no issue for 2 days now. Thanks for the fix in the beta! 👍

OK. Thank you. I think that this weekend I will release.

0.6.6 released. Feel free to reopen this issue, if needed.


UTY-1106: replace entity index with entity

Contributions: We are not currently taking public contributions - see our contributions policy. However, we are accepting issues and we do want your feedback.

Description
We have been using the entity index instead of the entity to identify entities in our game object representation module. This is not unique (you need the index and the version) and caused some interesting bugs.
Tests
Ran it locally and checked whether the error still appeared. Now you can build out the gamelogic worker and connect/disconnect the client as often as you want without it throwing errors.
Documentation
internal implementation
Primary reviewers
@JonasImprobable @zeroZshadow

Whoops, looks like I commented after this was merged. The concerns I made are all nits so things are fine the way they are right now.


WIP: Remove support for servicemanager v2

zend-servicemanager v2 support is dropped in v3 so we can remove tone of code...

... and also zend-eventmanager v2.


Update Minecraft steps

Changed wording to point out that a transaction id is required in all cases (mojang accounts)
Added process for profiles linked to microsoft accounts

Thanks for your contribution!


Add web support

Very simple change to support react-native-web

I think it would be better to expose a different entry point for react-native-web, but I don't know that much about it.

Happy to move it to an index.web.js if that makes it better, but with the fallback code already around it felt like it made sense to keep it together.

What is the current status of this? Is the browser compatibility attained?

Is this library under maintaining? Hope this feature to be merged...

@dehypnosis Yes, I hope this pull request to be merged.
I have some project use this pull request (using patch-package for patch original react-native-fast-image with this pull request) and is still work correctly.

@ri7nz patch-package tool seems good to me, but i already patched so many broken react-native libs in web platform by myself. should have know this tool earlier. anyway thanks.

@dehypnosis you're welcome

Any updates? :)

@tberman @DylanVann I agree it should have a different entry point for the web

I don't think we need this necessary in react-native-fast-image itself, as it doesn't really yield any benefits.
If you want to have a fallback for web today, create these two files.
image.web.tsx
import { Image as ImageNative } from "react-native";
export default ImageNative;

image.tsx
import FastImage from "react-native-fast-image";
export default FastImage;

Then simply include via import Image from "./image";, and it will automatically use the image.web.tsx file for web.

@sreuter I don't agree, you're going to have the benefit of supporting the web platform without extra effort from the developer. Many other libraries have it already, too.

This would be awesome. :)

Works!

Any update?

any update?

Any updates to accept this feature?


[Party List] Gendered party invite limits

Adding fields to the db to limit the number of invites by gender
Addresses #259

You will also likely need to edit the create guest API


Does this work with server-side rendering?

Reading through the code, it doesn't seem like it would.  By not making use of Context, we are effectively assigning the stores as global variables (actually the stores are local properties of the providers, but the providers are assigned statically to the components).
This means that for server-side rendering, there is no good way to use different stores for different requests.  It seems like we really need to differentiate between assigning the static assignment of the providers (which implement all of the actions,reducers,selectors), and rendering the components with a specific set of stores those providers would access.
Am I misunderstanding something here?

Server rendering and different stores for different requests should work, but not the way you're used to.    I'll try a few things with this when I get a chance and get back to you.  :)

Hey sorry for the delay in getting back to you.  Been busy, holidays, etc.  v5.0.0 should allow you to easily render things on the server.  If you can wait another day or two though I'm going to release another package to make that portion of it extremely simple.
But for now the API is roughly the same except that assignProviders has been removed so that you no longer have to do that, everything gets assigned automatically as the components are instantiated.  All you have to do now is basically:
import { renderToString } from 'react-dom/server';
import { App } from './components/index';
import providers from './providers/index';
import getProvidedState from './yourOwn/getProvidedState';
import wrapWithDocument from './yourOwn/wrapWithDocument';

// let's export some middleware for Express
export default function middleware(request, response, next) {
  getProvidedState(request, function(err, providedState) {
    const context = { providers, providedState };
    const appHtml = renderToString(<App { ...context } />);
    const documentHtml = wrapWithDocument(appHtml);

    response.send(documentHtml);
  });
}

I don't really like what I had to do internally to make this work the way I wanted as I'm now "abusing" context, but maybe when the React team improves upon the whole context paradigm a bit more, it will seem less hacky to me.  I think what we have here now is close to an optimal design, so I'll try to give them some feedback in that area after I've dug into it further.
That said, v5 should work perfectly now with SSR, plus I like the new API (everything is assigned automatically, plus a couple of other cool benefits) much better than what we had for v4.  Check the changes to the main README updates for more details.  :smile:

Yeah that looks better.  Thanks.
I don't have a problem with the way react-redux provides access to the
store via a wrapper component.  I mean there's nothing wrong with something
like:
const appHtml = renderToString(<Provider providers={providers}
state={state}><App /></Provider>);
...

It seems like it provides a nice entry point to put the pieces into React
context without "abusing" it...
Anyway, thanks for your work.

react-redux's Provider component seems a bit unnecessary to me, adding logic that could have been easily included with connect, and I believe it's limited to one store which can't be changed and probably won't play well will multiple contexts.  I could be wrong about that last part, but in any case, I prefer a more decoupled (and automatic!) design without all of the extra boilerplate (more directories to manage, containers, more code, etc.) added by Provider and connect.  :+1:
Please LMK if you have anymore concerns/questions!

Hey check out provide-page and bloggur for how to automatically use server-side rendering (among some other pretty useful stuff)!


[TF API] Comparison operator overhaul

Background

Operators like Tensor.<=(_:_:) today do not return Bool, but return Tensor<Bool> instead. Having comparison operators in Swift have element-wise semantics is highly inconsistent with 1) the mental model of comparison operators in Swift, 2) the established convention (see C++ relational operators) and 3) the Comparable protocol that comparison operators should be associated with.

The existing VectorNumeric protocol overlaps with Numeric in that they both require arithmetic operators. The only reason VectorNumeric does not refine Numeric is the lack of Comparable conformance.

A couple of months ago, we changed Tensor.==(_:_:) from returning Tensor<Bool> to returning Bool and added a elementsEqual(_:) for element-wise comparison. Tensor was then made Equatable.

Solution
As such, we do a three-step overhaul:

Rename existing element-wise comparison operators to well-named functions.
Make Tensor conform to Comparable. Comparison operators are lexicographical.
Make VectorNumeric refine Numeric and remove arithmetic operators with type (Self, Self) -> Self from VectorNumeric.

This patch

1 and 2 described in "Solution" are included.
Add API elementsApproximatelyEqual(_:tolerance:) for the corresponding TensorFlow op ApproximateEqual, since it is nice to have.

Note: I haven't added tests, so please do not trigger CI yet.

@lattner Sure, I can remove ≈(_:_:) for now.

@swift-ci please test tensorflow

@swift-ci please test tensorflow

Actually, it's not possible to make Tensor conform to Numeric today because Tensor cannot be ExpressibleByIntegerLiteral for complicated reasons.

Got it, glad to know it's precedented ... :)

@rxwei Can you expand a little bit on the issues with conforming to ExpressibleByIntegerLiteral (email would be fine if you don't want to put all the gory details in this PR).

@stephentyrone Yes, the issue is with type checking ambiguity.
Tensor has tensor+tensor, scalar+tensor, and tensor+scalar arithmetic operators.
  static func + (lhs: Tensor, rhs: Scalar) -> Tensor
  static func + (lhs: Tensor, rhs: Tensor) -> Tensor

When Tensor is ExpressibleByIntegerLiteral, then expression x + 2 cannot be resolved because it can be either tensor+tensor or tensor+scalar.


Alexa Voice support for McLighting

Hi Using Openhab skill on alexa  & google home Power On off functionality is working good .
but color is only working on google home . Color Item is not working with alexa .
Hey google turn on / switch on  LED   -- working
Alexa Switch on LED -- working
Hey google set LED to red / blue / green / auqa etc working
But
Alexa LED to red / blue / green / aqua etc...  not working
Any suggestion ?

Hi @sujitrp,
I have no experience with openhab. How is McLighting connected? Is this problem related to McL or more to openhab? I this latter is true, this might not be the best place to get help.
Regards
Tobias

Great! This seems to work quite good.
Regards
Tobias

Now the next target is to remove Raspberry Pi and Openhab from set up setup something like

Hi Need help
in above approach I am facing following raised issue .
https://github.com/toblum/McLighting/issues/185#issuecomment-424026531

Hi Finally i am connected to Io.adafruit.com by changing
line 352 to 'strcpy(mqtt_port, custom_mqtt_port.getValue());'
now next issue MQTT connection gets disconnected frequently .. Please find the log
MQTT active: io.adafruit.com:1883
Open http://<IP_ADDRESS>/ to open McLighting.
Use http://openhab/feeds.local/ when you have Bonjour installed.
New users: Open http://<IP_ADDRESS>/upload to upload the webpages first.
Couldn't find "/stripstate.json"
Failure!
readEEPROM(): STA| 1| 11|196|196|255| 0| 0
Found saved state: STA| 1| 11|196|196|255| 0| 0
ws2812fx_mode: 11
ws2812fx_speed: 196
brightness: 196
main_color.red: 255
main_color.green: 0
main_color.blue: 0
*WM: freeing allocated params!
MQTT disconnected, reconnecting!
Attempting MQTT connection 1 / 4 ...
MQTT connected!
MQTT topic in: openhab/feeds/in
MQTT topic out: openhab/feeds/out
MQTT: Message arrived [0100]
MQTT: Message arrived [0100]
MQTT: Message arrived [off]
MQTT: Message arrived [/red]
MQTT: Set WS2812 mode: [/red]
SET_MODE: 0 0
Saving cfg: {"mode":1,"strip_mode":0,"brightness":196,"speed":196,"red":255,"green":0,"blue":0} Success!
MQTT: Send [home/openhab/feeds_ha/state/out]: {"state":"ON","color":{"r":255,"g":0,"b":0},"brightness":196,"color_temp":327,"speed":196,"effect":"Static"}
Heap size: 25264
writeEEPROM(): STA| 1| 0|196|196|255| 0| 0
MQTT disconnected, reconnecting!
Attempting MQTT connection 2 / 4 ...
MQTT connected!
MQTT topic in: openhab/feeds/in
MQTT topic out: openhab/feeds/out
MQTT: Message arrived [=ff0000]
MQTT: Activated mode [1]!
Saving cfg: {"mode":1,"strip_mode":0,"brightness":196,"speed":196,"red":255,"green":0,"blue":0} Success!
MQTT: Send [home/openhab/feeds_ha/state/out]: {"state":"ON","color":{"r":255,"g":0,"b":0},"brightness":196,"color_temp":327,"speed":196,"effect":"Static"}
Heap size: 24888
MQTT disconnected, reconnecting!
Attempting MQTT connection 3 / 4 ...
MQTT connected!
MQTT topic in: openhab/feeds/in
MQTT topic out: openhab/feeds/out
MQTT: Message arrived [#ff0000]
MQTT: Set main color to: R: [255] G: [0] B: [0]
Saving cfg: {"mode":1,"strip_mode":0,"brightness":196,"speed":196,"red":255,"green":0,"blue":0} Success!
MQTT: Send [home/openhab/feeds_ha/state/out]: {"state":"ON","color":{"r":255,"g":0,"b":0},"brightness":196,"color_temp":327,"speed":196,"effect":"Static"}
Heap size: 24848
MQTT disconnected, reconnecting!
Attempting MQTT connection 4 / 4 ...
MQTT connected!
MQTT topic in: openhab/feeds/in
MQTT topic out: openhab/feeds/out
MQTT connection failed, giving up after 4 tries ...
sd

@sujitrp I dont think this is a McLighting related issue, is it? Its your very specific case where you are trying to communicate with Adafruit.io which needs a special code and there are limitations on bandwidth and number of messages you can send to adafruit.io. I suggest running your own broker like mosquitto or buying cloud instances of mosquitto broker.

@sujitrp I agree with @debsahu
Adafruit.io MQTT seems to behave different than other MQTT implementations. There are a lot of issues out there that are related to this (e.g. https://github.com/knolleary/pubsubclient/issues/291). I'm afraid this isn't supported with McLighting at the moment.

I am almost close to achive this . For me adafruit mqtt connected using pubsublib.  It passing on message in & out both.
Adafruit is updating its dashboard  as per MCL output (e.g. ok 139%).
Now next step colour code conversion to her. E.g. red  to #ff0000.
Being not a programmer it is taking time for me to read try and do.
One of my friend created colour code change  web service on Google cloud for me.
Target is to open voice control .


types.db for usage with logstash or influxdb

Hi,
if you could add a types.db with the custom types it would be possible to use logstash or influxdb as backend. Plus the possibility of adding custom conf files. That would be great.

PRs are welcome

Can you accomplish this with a docker volume mount?


Flash inoperable

Not sure if I'm in the right forum here, but here goes:
A couple days ago I performed the usual sudo startlxde to start up Ubuntu on my Chromebook, except I accidentally typed sudo startunity out of habit. (I was using Unity before and wanted to switch it up to a lighter DE, which I installed without much of a problem a while back) The result: a black screen. Because I couldn't do anything, I exited out to Chrome OS and tried again with 'sudo startlxde', which worked fine.
After this happened I wanted to check some Youtube vids and it occured to me Flash was acting up. I ran Synaptic update, no results. Manually apt-get update, it did find some things, but no result for Flash acting up. Removed flash, reinstalled through USC; apt-get purged it, even tried checking if Chromium would work with pepperflash-nonfree, and it stunningly showed the exact same behavior:
It loads at 0:00 and freezes. On the Twitch website (twitch.tv) it shows a similar behavior, freeze into crash 30 seconds later and an error report window comes up. Sometimes it plays a couple of seconds of choppy video, then freezes once more. Did the usual cleared cache, uninstall/reinstall add-ons, tried a different Firefox profile, to no avail. Because Chromium was a fresh installation, I'm led to believe it's something more serious outside the two browsers.
On Chrome OS (I believe that's the OS that the Chromebook comes with?) I can watch videos, no problem. They load instantaneously, showing no indication anything has changed on that end. There is no UpArrow icon in the tray bar signaling updates for Chrome OS.
When this freezing occurs, the CPU Resource Monitor doesn't show 100% use, instead it's either around 30% (normal for a medium quality stream or 480p Youtube video) or near idle. Htop in terminal mirrors this result. The browser itself will sometimes also spit out a generic "app is unresponsive" error when a Flash required-page is loaded.
I'm not 100% sure this is happening because of the accidental wrong target I used (unity instead of lxde) or if it's something else I'm overlooking, but I'm running on fumes here when it comes to solutions. I asked around, nobody seems to know what's up.
Does anyone know what I should do to fix this problem?
PS it would also seem the task bar is a blank bar for about 15-20 seconds until it finally loads - this didn't occur before.
tl;dr Adobe Flash freezes up on both Firefox and Chromium (pepperflash-nonfree) after an accidental wrong desktop environment was loaded. The two may or may not be related.

Update: I solved this with a simple
sudo sh -e ~/Downloads/crouton -n trusty -u
Still not sure what caused it, but it seems to be working now. Sharing this in case others bump into the same problem. (HTML5 video was also affected, btw)


Black Formatter v2022.6.0 fails to fall back to bundled version

Black Formatter v2022.6.0 fails to fall back to bundled version when "black-formatter.importStrategy": "fromEnvironment".
Here are my settings related to Black Formatter.
   "[python]": {
        "editor.defaultFormatter": "ms-python.black-formatter"
    },
    "black-formatter.importStrategy": "fromEnvironment",
    "black-formatter.showNotifications": "always"

Note that I have don't have black in my environment. However, Black Formatter works fine if I set "black-formatter.importStrategy": "useBundled",
Here is the error which I see when "black-formatter.importStrategy": "fromEnvironment":
Traceback (most recent call last):
File "/Users/mski/.vscode/extensions/ms-python.black-formatter-2022.6.0/bundled/tool/runner.py", line 57, in <module> result = utils.run_module( ^^^^^^^^^^^^^^^^^
File "/Users/mski/.vscode/extensions/ms-python.black-formatter-2022.6.0/bundled/tool/utils.py", line 141, in run_module return _run_module(module, argv, use_stdin, source) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/mski/.vscode/extensions/ms-python.black-formatter-2022.6.0/bundled/tool/utils.py", line 126, in _run_module runpy.run_module(module, run_name="__main__")
File "<frozen runpy>", line 222, in run_module File "<frozen runpy>", line 142, in _get_module_details ImportError: No module named black

@muranski Can you provide the full logs. The initial part of the logs should have sys.path info that should detail where python will look for black.


use signaling instead of polling in thpool_wait

Removed exponential polling in thpool_wait and replaced it with waiting on a pthreads condition variable. When a thread goes into idle, it signals if num_threads_working becomes 0.
Tested on basic, pause/resume, and wait test cases.
I might in the near future look into cleaning up the job queue synchronization (esp. regarding the bsem) but it would be a bigger refactoring.

Thanks for the contribution dweymouth. Took me a while to test it but it seems all fine now.


The TypeScript Vue Plugin (Volar)

The TypeScript Vue Plugin (Volar) is deprecated. After you uninstall it, install Vue-official，Always prompt
“Do you want to install the recommended "TypeScript Vue Plugin (Volar)" extension from Vue for this repository?”

Remove vue.vscode-typescript-vue-plugin from .vscode/extensions.json.


Proposal: refactor Hello-World quickstart into /node and /python subfolders

Today, the /hello-world quickstart is a "flat folder" that contains Node.js files (app.js) and Python files (app.py) in the same folder. This makes devops a pain, e.g. building clean or writing a single Dockerfile for each of the services.
Describe the proposal
The proposal is to lightly refactor the node.js code into \node and python code into \python subfolders.  The README will need to be updated guiding the dev to build and run those services out of those folders.
The benefits are:

separation of services and concerns (like distributed calculator or any other microservice repo)
repo / environment realism
ability to create unique devops assets like Dockerfiles or GH actions for each folder

I will be happy to make the PR.

This makes sense to me. Many of the other quickstart are also factored like this (e.g. pub/sub), so it would be better to apply this to all of them. If not, then this only actually applies to those where you want to include the dockerfiles, which are the quickstart deployed to K8s.

Actually I looked at the PR and realize that I did not look at this closely enough and though this was just adding folders for the apps to be consistent. Adding dockerfiles to the hello world quickstart is not needed, only in the K8s version where you have to have containers.

@msfussell ok I agree it makes sense to split out deployment matters including docker into separate folders and work.  I revised PR based on this feedback.


fix: Remove incorrectly filtering VS Code cargo task execution resolution by scope

This fixes #9093 introduced by #8995.
A filter was present on the function that adds the execution definition to Cargo tasks. This would mean Cargo tasks defined in workspaces (i.e. .code-workspace files) would not be given an execution, leading to a There is no task provider registered for tasks of type "cargo". error as descibed in #9093. I have made a minimum reproduction setup here.
This PR essentially removes that check. The if (scope) { ... } is to handle the case where task.scope === undefined using a deprecated constructor. I'm not sure if that is ever likely to occur and can remove if not needed.
There is some discussion about whether it's necessary to filter the tasks before building them. From my understanding, it shouldn't be needed as we should provide an execution for all cargo tasks; but I'm not overly familiar with VS Code internals so I could be wrong. For more info please see the discussion on #8995

r? @SomeoneToIgnore

It's worth noting that I've never touched VS Code extensions before; so take these changes with an huge grain of salt. There's definitely an issue, but maybe isWorkspaceFolder just needs to account for workspace scopes instead? I'm not familiar enough to know.

I've tried to elaborate more on the changes that caused this: https://github.com/rust-analyzer/rust-analyzer/pull/8995#issuecomment-909040741
So looks like VSCode pushes everybody to explicitly specify the workspace folder for every task the plugins create (as it seems from the constructor deprecation mentioned above).
With this requirement, for user defined rust tasks and multiworkspace project, we have to default to some workspace folder, either picking the first (which effectively negates part of the https://github.com/rust-analyzer/rust-analyzer/pull/8995 reason behind described in https://github.com/rust-analyzer/rust-analyzer/pull/8955#discussion_r637848017) or find a better way to get that folder somehow.

Any further thoughts on this one? Happy to modify to skip tasks that have an undefined scope if that's the right path?

Not dug deep into this, but here's what I'd do:

return undefined if the scope is undefined, as per resolveTask docs
if that causes real problems, raise vscode issue asking why VS Code calls us with undefined scopes at all.

Alternatively, why we are returning a new task here? Can't we just set the fields of the task we are given?

My intention with using the deprecated constructor was to essentially just modify the task as is.
That's a great point though, there's no reason the function can't just set the exec on the existing task to my eyes. Can change it to do that if in agreement.

We definitely should not call deprecated functions. Other than that —
whatever gets the job done!
On Tuesday, 7 September 2021, Oliver Cooper @.***>
wrote:

My intention with using the deprecated constructor was to essentially just
modify the task as is.
That's a great point though, there's no reason the function can't just set
the exec on the existing task to my eyes. Can change it to do that if in
agreement.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rust-analyzer/rust-analyzer/pull/10093#issuecomment-913867522,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANB3M4UQ2542WQQ3EGWZHLUAU3FNANCNFSM5DDTL6AA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Setting task.execution clears the scope and results in the same error.
The official docs on the subject explicitly make a new task rather and use task.scope ?? vscode.TaskScope.Workspace to compensate for an undefined scope. I've implemented this in the above commit and from my testing works correctly without needing deprecated functions.
So this should be good for a final check I believe.

So, looks like we've ended up with pretty much what was suggested in https://github.com/rust-analyzer/rust-analyzer/pull/10093#discussion_r699140675 , great that it was as simple as expected.
Thank you for looking into that.
One last thing, if you want to: we can add a comment somewhere around buildCargoTask function to explain what is happening with the scope and why we set it so (your case may not so clear for people who had never dealt with predefined configs, better warn them before they twist the logic on the next refactoring)
But this is minor, feel free to r+ and merge the current changes if you've had enough of this already.
bors d+

bors r+

changelog fix (first contribution) fix cargo task filtering in Code workspaces


Error when running with v1.4.0 of octodns

Dependabot opened a PR updating octodns from v1.0.0 to v1.4.0 and now when octodns runs I get an error which is included below.
I have another project that's using v1.4.0 with the latest Azure (0.0.7) & Cloudflare (0.0.3) providers which is running just fine, it seems to be just this provider causing an issue.
I'm running via https://github.com/solvaholic/octodns-sync but I don't think that has anything to do with the error.
requirements.txt
octodns==1.4.0
octodns_rackspace==0.0.1

production.yaml
---
providers:
  config:
    class: octodns.provider.yaml.YamlProvider
    directory: zones
    default_ttl: 300
  rackspace:
    class: octodns.provider.rackspace.RackspaceProvider
    username: env/RACKSPACE_API_USERNAME
    api_key: env/RACKSPACE_API_KEY
manager:
  max_workers: 2
  plan_outputs:
    html:
      class: octodns.provider.plan.PlanHtml
zones:
  # ...

Run log

2024-02-09T00:47:55  [139722632227904] INFO  Manager __init__: config_file=production.yaml, (octoDNS 1.4.0)
2024-02-09T00:47:55  [139722632227904] INFO  Manager _config_executor: max_workers=2
2024-02-09T00:47:55  [139722632227904] INFO  Manager _config_include_meta: include_meta=False
2024-02-09T00:47:55  [139722632227904] INFO  Manager _config_auto_arpa: auto_arpa=False
2024-02-09T00:47:55  [139722632227904] INFO  Manager __init__: global_processors=[]
2024-02-09T00:47:55  [139722632227904] INFO  Manager __init__: global_post_processors=[]
2024-02-09T00:47:55  [139722632227904] INFO  Manager __init__: provider=config (octodns.provider.yaml 1.4.0)
2024-02-09T00:47:55  [139722632227904] ERROR Manager _get_{}_class: Unable to import module octodns.provider.rackspace.RackspaceProvider
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.10.13/x64/lib/python3.10/site-packages/octodns/manager.py", line 333, in _get_named_class
    module, version = self._import_module(module_name)
  File "/opt/hostedtoolcache/Python/3.10.13/x64/lib/python3.10/site-packages/octodns/manager.py", line 319, in _import_module
    module = import_module(current)
  File "/opt/hostedtoolcache/Python/3.10.13/x64/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1050, in _gcd_import
  File "", line 1027, in _find_and_load
  File "", line 1004, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'octodns.provider.rackspace'
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.10.13/x64/lib/python3.10/site-packages/octodns/manager.py", line 333, in _get_named_class
    module, version = self._import_module(module_name)
  File "/opt/hostedtoolcache/Python/3.10.13/x64/lib/python3.10/site-packages/octodns/manager.py", line 319, in _import_module
    module = import_module(current)
  File "/opt/hostedtoolcache/Python/3.10.13/x64/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1050, in _gcd_import
  File "", line 1027, in _find_and_load
  File "", line 1004, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'octodns.provider.rackspace'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.10.13/x64/bin/octodns-sync", line 8, in
    sys.exit(main())
  File "/opt/hostedtoolcache/Python/3.10.13/x64/lib/python3.10/site-packages/octodns/cmds/sync.py", line 56, in main
    manager = Manager(args.config_file)
  File "/opt/hostedtoolcache/Python/3.10.13/x64/lib/python3.10/site-packages/octodns/manager.py", line 123, in __init__
    self.providers = self._config_providers(providers_config)
  File "/opt/hostedtoolcache/Python/3.10.13/x64/lib/python3.10/site-packages/octodns/manager.py", line 215, in _config_providers
    _class, module, version = self._get_named_class(
  File "/opt/hostedtoolcache/Python/3.10.13/x64/lib/python3.10/site-packages/octodns/manager.py", line 3[38](https://github.com/paramax/dns/actions/runs/7838025325/job/21388786004?pr=92#step:5:40), in _get_named_class
    raise ManagerException(
octodns.manager.ManagerException: Unknown provider class: octodns.provider.rackspace.RackspaceProvider, production.yaml, line 8, column 5

The providers got broken out to separate repos, so the provider configuration you have now is no longer valid
You can view the new one here: https://github.com/octodns/octodns-rackspace?tab=readme-ov-file#configuration
Just need to change class: octodns.provider.rackspace.RackspaceProvider to class: octodns_rackspace.RackspaceProvider

Well that's embarrassing. After checking my other project that one had the class names updated 2 years ago but I missed it in this one. Renamed the class and it's working again. Thanks for the help.


Use Bugzilla webhooks to react to bug openings/changes

It would make sense especially for scripts such as the spam one or the component one, where we want to act as quickly as possible.
The UI to enable webhooks is located at https://bugzilla.mozilla.org/userprefs.cgi?tab=webhooks.
There is some simple documentation located at https://bugzilla.mozilla.org/page.cgi?id=webhooks.html.

This will also need to listen for changes to a bug's groups, so if an invalid bug is just made public it'll be handled by the bot.

can you please tell where is webhook in 5.0.6, I am not able to find it in the preferences tag

can you please tell where is webhook in 5.0.6, I am not able to find it in the preferences tag

This feature is only on bugzilla.mozilla.org, which is running a highly customised version of Bugzilla.

Can I setup webhook in Bugzilla 5.0.6. Because while I am tring to set it up I am facing Issue  Can't locate Bugzilla/Extension/Webhooks/Webhook.pm in @INC  whereas this file is there.

Sorry, but there's no guarantees that taking parts of bugzilla.mozilla.org and trying to make them work in any other Bugzilla installation will work.
While bugzilla.mozilla.org started off as a version of Bugzilla, it's best to consider it a different product with the same origins designed specifically for Mozilla's workflow.
https://www.bugzilla.org/support/ is a better place to ask for help with Bugzilla.


Crashes

App crashes when launched without internet

@Glaverd Thanks for the feedback, network handling is needed there in the app, unfortunately I'm swarmed in other work, so I'll look at this sometime in the future, but any bugfixes or other PRs are welcomed ! :)


Sentence. Easier polymer registration

I have an idea. I think a such registration more convenient.
Polymer('my-element-id')
.properties({
...
})
.ready(function() {
...
});

I have another idea.
When I use a hyphen in Id's name I can't access to dom element using this way: this.$.my-element. The only way: this.$['my-element'].
It would be good if $ array contains second reference on element, but with name: my_element. Then I would be able to use the first way: this.$.my_element.

Since Polymer elements are based on custom elements, the provided lifecycle callbacks and properties/observers are on the class. Since this issue has been opened, the Polymer legacy syntax has been replaced by the custom element native syntax. Therefore I am closing this issue, thank you for your suggestion!


added numberfact command

Added the numberfact command
Used the numbers api to fetch the fact
Added the axios http library to the project to interact with the web and for making api calls.

Thanks @CH1NRU5T! Although normal commands would work, Discord prefers Slash commands, is there any chance you could convert it to a slash command?
No worries if not, happy to merge and add it to myself!

Sorry, I don't know how to achieve that :(

No worries at all! Ill merge and add it then if youd like you can see the small differences between them!
Thanks a ton! @CH1NRU5T

Sure, will see the differences and get to learn it, thank you so much :)

@CH1NRU5T So it turns out this command just lists ping? Is this correct?
Also the url is not defined within the command so this command would fail, I may have to revert unless you want to make a fix?

It was working in my local machine.
I will check it first thing in the morning.
Will make the fix, don't worry

I kept the embed template as it was, orange, gives ping and shows the uptime, do I have to modify it?

Feel free to set the title as 'Number Fact' and the description as response.data then you can get rid of the Add field

Solved the issue
The new embed looks like this

it this okay?


Binary file incompatibility?

Hi, thank you for great work.  It runs faster than original torch on Xeon.
However, I'm having one trouble while trying to load trained .t7 files.  These .t7 files are trained on GPGPU torch but converted for CPU.  Original torch on CPU (without GPGPU) works well with these .t7 files.  However, Intel torch shows following error message.
$ th ...
| loading model file...
/home/.../torch/inteltorch/install/bin/lua: .../torch/inteltorch/install/share/lua/5.2/torch/
File.lua:301: Failed to load function from bytecode: binary string: not a precompiled chunk
stack traceback:
        [C]: in function 'error'
        .../torch/inteltorch/install/share/lua/5.2/torch/File.lua:301: in function 'readObject'
        .../torch/inteltorch/install/share/lua/5.2/torch/File.lua:369: in function 'readObject'

Any idea?  Thanks.

hi kmarukawa
Thanks for your feedback. When runing imagenet classification, we could load the snapshot files(.t7 files) without any error.
From your log ,the luajit version you installed is 5.2. Could you please install luajit2.1(the default version) and try again?
xhzhao

Hi xhzhao,
Thank you for the suggestion.  You are right.  I unfortunately compiled it with lua 5.2 while I was trying to port GPGPU program into this Intel Torch.  I recompiled Intel torch from scratch again.  It works fine.  Thanks.
kazushi


The suggestions were getting split at character level and not at sentence level

When loading the historical suggestions, it was getting loaded as
["Historical Data:\n['e', 'u', '.', 'T', 'n', 'c', 'y', ',', 'v', 't', 'h', 'S', 'A', 'I', 'b', 'f', 'l', 'g', 'd', '-', ' ', '\n', 's', 'a', 'w', 'x', 'p', 'i', 'r', 'k', 'm', 'o']", '', '']
This was happening because the suggestions were split at character level. This fix will not make it at sentence level

great catch! amazing <3


Ensure excel reader closes file if it is passed as path

What do these changes do?
openpyxl has either a long-standing bug or a design decision that, when opening a file in read-only mode, it does not close the file handle (maybe it does so for caching purposes, no idea).
They have introduced a new .close() method, but people say it does not fully close all the handles.
So what I instead did was open the file if passed in a string and close it explicitly.
Also I've optimized the code a little bit by effectively inlining load_workbook() function which allowed to eliminate creation of two ExcelReader() objects for a single read.
I've also decorated all the excel-reading tests with the checker from Pandas test utils which they introduced in https://github.com/pandas-dev/pandas/pull/30096 when they were fixing this exact issue :)

[x] commit message follows format outlined here
[x] passes flake8 modin
[x] passes black --check modin
[x] signed commit with git commit -s
[x] Resolves #2465
[x] tests added and passing

Note: if you take only first commit (where test decorators were added but no fix implemented), the test that fails for me is test_io.py::test_from_excel_sheet_name (it passes again after the fix).


npm install --save firebase fails with projects created with vue cli 3

Version
3.0.5
Node and OS info
Node 11.0.0, Npm 6.4.1, Mac OS High Sierra 10.13.6
Steps to reproduce

create a new project with vue cli 3
try to add firebase with npm install --save firebase

What is expected?
Firebase should be installed.
What is actually happening?
Error on npm install
Snapshot of logs:
2336 verbose stack Error<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build --library=static_library`
2336 verbose stack Exit status 1
2336 verbose stack     at EventEmitter.<anonymous> (/Users/anas/.nvm/versions/node/v11.0.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
2336 verbose stack     at EventEmitter.emit (events.js:182:13)
2336 verbose stack     at ChildProcess.<anonymous> (/Users/anas/.nvm/versions/node/v11.0.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
2336 verbose stack     at ChildProcess.emit (events.js:182:13)
2336 verbose stack     at maybeClose (internal/child_process.js:962:16)
2336 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
2337 verbose pkgid<EMAIL_ADDRESS>2338 verbose cwd /Users/anas/Development/other/tmp/tmp-project
2339 verbose Darwin 17.7.0
2340 verbose argv "/Users/anas/.nvm/versions/node/v11.0.0/bin/node" "/Users/anas/.nvm/versions/node/v11.0.0/bin/npm" "install" "--save" "firebase"
2341 verbose node v11.0.0
2342 verbose npm  v6.4.1
2343 error code ELIFECYCLE
2344 error errno 1
2345 error<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build --library=static_library`
2345 error Exit status 1
2346 error Failed at the<EMAIL_ADDRESS>install script.
2346 error This is probably not a problem with npm. There is likely additional logging output above.
2347 verbose exit [ 1, true ]

I tried to install Firebase in a non vue project, with the same node/npm versions and it works.
When trying to add Firebase to a Vue project created with vue cli 3, after a vue create my-project command, Firebase installation failed. I've put a snapshot of npm logs. I can share the full logs in private if required.

Same issue here, but this isn't relevant to vue-cli, but rather grpc & firebase - try posting it there?

Hi @vpiskunov !
I was thinking to put it in firebase, but as I said in the comment, that does not appear when I run an npm install --save firebase on a non vue cli 3 project.

See: https://github.com/grpc/grpc-node/issues/594

IMO it's not related to vue-cli but a grpc & node v11 issue. So I'm closing this issue for now.

It is a grpc & node v11 issue indeed. I had the same problem. Since I have nvm, I switched to node v8.5.0 and I was able to install firebase. Just give it a try.