python3Packages.angr: 9.0.7491 -> 9.0.7833

Motivation for this change
Update to the whole angr stack to 9.0.7833
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.

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

14 packages built:

python38Packages.ailment
python38Packages.angr
python38Packages.angrop
python38Packages.archinfo
python38Packages.claripy
python38Packages.cle
python38Packages.pyvex
python39Packages.ailment
python39Packages.angr
python39Packages.angrop
python39Packages.archinfo
python39Packages.claripy
python39Packages.cle
python39Packages.pyvex

Result of nixpkgs-review pr 125348 at 251ee3d7 run on aarch64-linux 1

10 packages failed to build:

python38Packages.ailment
python38Packages.angr
python38Packages.angrop
python38Packages.cle
python38Packages.pyvex
python39Packages.ailment
python39Packages.angr
python39Packages.angrop
python39Packages.cle
python39Packages.pyvex

4 packages built successfully:

python38Packages.archinfo
python38Packages.claripy
python39Packages.archinfo
python39Packages.claripy

1 suggestion:

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/ailment/default.nix:27:0:
   |
27 |     description = "The angr Intermediate Language";
   | ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.


everytime i open or try to create a skill in visual studio code v1.47.3 i get error Skill clone failed. Reason: Git folder setup failed Reason: Failed to execute git {   "exitCode": 1,   "gitCommand": "checkout",   "stdout": "",   "stderr": "error: pathspec 'prod' did not match any file(s) known to git\n" }

Describe the bug

To Reproduce

Extension Logs

Expected behavior

Screenshots

Desktop (please complete the following information):

OS:
Visual Studio Code Version:
Alexa Skill Toolkit Version:

Additional context

Hey @doctor-iksterog , thanks for raising the issue. It would be really helpful if you can fill up the issue template with additional details (like OS, toolkit version etc.) and provide some more details about the workspace/skill being opened. Also, can you try opening a new vscode session, without any skill folder and try to check if the extension is working as expected?

Hey @doctor-iksterog , any updates?

amzn1.ask.skill.35f7722e-89ad-46ce-b5a9-054850a3d6d6
tried opening on clean open , nothing else open and same error. macos 10.15.6. happens on any existing skill i have. i have git 2.4.1

@doctor-iksterog Please see issue #59. We discovered a workaround. I even posted instructions with screenshots. Should be able to fix on Mac as well.

Please find the fix and the corresponding discussion regarding this issue on #59 . Closing this since the latest extension release v2.2.0 fixes this. Please update your extension and let us know if you still face issues. Thanks.


Mavic mini2 compability?

Just finished my PoC.
needs to run with frida as gadget (added to jnilibs and loadlibrary on the connect screen, so it works without root)
Confirmed its all working tho DJI SDK Codec Manager has issues on my device, unrelated to the patch.
Use it on your own risk.
Fwiw made a little KML parser that pushes waypoints from groundstation export via do_set_motion_absolute :)
Works sweet!
I plan to release the scripts after a bit more ironing out.
@The1only Since DJI has no plan to support it in SDK v4, would you be interested in adding my script? It would have quite big deps tho (20MB per arch, frida's libgadget).
Maybe we can figure something, or is it too hot for you?
Also would you be interested in adding my KML stuff (tho i plan to do a translation layer between WaypointMission stuff later).
Also fixed a bunch of smaller bugs related to GCS taking images etc. when f.e wrong mode is selected

Great work,
Send push requests and I will diff and add.
Some times I rework it a bit to fitt the bigger picture and all other stuff thats beeing added, we too have been working on image taking, but mostly mission work lately.
If you go beyond Rosettadrone strategy I simply reject the push, no problem.
Best regard
Terje Nilsen
9Tek AS
Norway

On May 6, 2021, at 21:21, m4xw @.***> wrote:

Just finished my PoC.
needs to run with frida as gadget (added to jnilibs and loadlibrary on the connect screen, so it works without root)
Confirmed its all working tho DJI SDK Codec Manager has issues on my device, unrelated to the patch.
Use it on your own risk.
Fwiw made a little KML parser that pushes waypoints from groundstation export via do_set_motion_absolute :)
Works sweet!
I plan to release the scripts after a bit more ironing out.
@The1only Since DJI has no plan to support it in SDK v4, would you be interested in adding my script? It would have quite big deps tho (20MB per arch, frida's libgadget).
Maybe we can figure something, or is it too hot for you?
Also would you be interested in adding my KML stuff (tho i plan to do a translation layer between WaypointMission stuff later).
Also fixed a bunch of smaller bugs related to GCS taking images etc. when f.e wrong mode is selected
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@The1only Frida is required because we need to hook DJI SDK internals and tell it its a Mavic Air 2 with a Mavic Mini Camera (Mavic Air 2 as Camera works but the UXSDK fails to detect the SD with it so you can't take pics/vid through it, its working via the API calls tho). Its the only stuff really required.

I will probably still need a few weeks to get all properly sorted and tested to make sure theres no additional risk involved, but so far its working splendid to be honest, my dayjob is keeping me busy tho.
Fwiw if DJI ever adds support for Mini 2, we could simply drop the hooks (pretty much remove 2 lines and the jniLib include)
Whats primarily left for me is having it not impact other drone models (thats quite a easy fix tho)
Would you prefer stuff like a "execute/load KML mission" as a Menu entry like the waypoint stuff or directly on screen?
Right now I just hijack the button on the left that opens the store with a dummy.
I could make this a seperate PR as well, tho I can only test on Mini 2.

Note tho, the KML stuff is just a stopgap until i got translation layer for the waypoint code in, I want to avoid having to rewrite all the mavlink stuff for it.

Impressive,
That’s what I would call hacking, but in a positive sens.
Keep working and we will be first to support Mini2.
Best regard
Terje Nilsen
9Tek AS
Norway

On May 6, 2021, at 21:47, m4xw @.***> wrote:

Note tho, the KML stuff is just a stopgap until i got translation layer for the waypoint code in, I want to avoid having to rewrite all the mavlink stuff for it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Impressive, That’s what I would call hacking, but in a positive sens. Keep working and we will be first to support Mini2. Best regard Terje Nilsen 9Tek AS Norway
…
On May 6, 2021, at 21:47, m4xw @.***> wrote:  Note tho, the KML stuff is just a stopgap until i got translation layer for the waypoint code in, I want to avoid having to rewrite all the mavlink stuff for it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

It is, by all means ;)
I have a strong background in both PC and Console hacking as well professional pentesting, so this is a small feat for me.
The most time i wasted was with the Video feed but that turned out to work on my S6 (vs not working on S21).
Exynos video decoder shits itself, I wonder if a MediaDecoder impl would work tho.
They refactored all that in the DJI SDK v5 dumped from the dji.go.v5 app and CodecManager doesnt actually exist anymore (and that works on my S21).
I am happy to hear you are not strictly against it, I prefer to avoid forks whenever possible.
Also thank you for developing such a nice base, most mistakes/design oversights I found are pretty trivial (like the wrong ack in takePhoto for groundstation, i guess it has a legacy background tho?) and not having a photoTaken event to sync up the success with a worker thread (but that one i guess would be slightly out of scope for base rosettadrone). I had it take small movements with a smaller dist margin in  in the MoveTo task and it would end up failing to queue all the takephotos up. Oh and also not switching to RECORD_VIDEO mode if currently in photo mode or whatever when mavlink stuff comes in.
Easy to work with ;)

@m4xw please check latest version and stay up to date.
DJI MINI 2 is now officially suported.


zh-translation: /intro/arch_overview/upstream/load_balancing/load_balancing.rst

ref: https://github.com/cloudnativeto/envoy/issues/40

/LGTM


Can't run the site locally from IDE

In the wiki it said "Create a new run configuration with the class sagan.SiteApplication. " . Well, How?
(It would be most appreciated if someone could provide "step by step" guide on this)

What IDE are you using?
Usually it's just a matter of running the public static void main() method in that class, by right-clicking on the method or class and selecting "run".

I am using Spring Tool Suite.
When I right click on this and select Run As it only shows run configuration

Which one of the following should I choose?

I tried Spring boot app. But it threw a nullpointerexception.

I am facing the same problem. M not able to create new run config as there is no main class selected.

https://cloud.githubusercontent.com/assets/6715793/12790368/f1606146-cac7-11e5-85c1-4ce60d832c31.jpg

Maybe the project facet was the cause. When I created the sample spring boot app, there's small 'S' on the icon of java files. But in sagan app there's no 'S' and icon is somewhat different.

Well, At last I was I able to run it on Intellij IDEA. @Sudip7

Import it into Intellij IDEA
Click on Run from the top menu. (Edit configuration button will appear)
Get into Edit configuration
Choose Spring Boot from the left side menu (Click on Defaults to collapse it)
Set Main class as sagan.SiteApplication
Choose sagan-site folder as working directory
Use sagan-site_main as classpath of module
Then Run!


[BUG] Not possible to disable coredns

What did you do

How was the cluster created?

k3d cluster create test -p '80:80@loadbalancer' -p '443:443@loadbalancer' --k3s-server-arg 'k3s server --disable=coredns'

What did you do afterwards?

kubectl get pods -n kube-system

What did you expect to happen
I would expect that coredns pod wouldn't be created.
Screenshots or terminal output
$ k3d cluster create test -p '80:80@loadbalancer' -p '443:443@loadbalancer' --k3s-server-arg 'k3s server --disable=coredns'
INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-test' (4cfe4530ee710afc91dd918d0b8923255f963b938b9906c1a40d65cd4a9b2ff7)
INFO[0000] Created volume 'k3d-test-images'
INFO[0001] Creating node 'k3d-test-server-0'
INFO[0001] Creating LoadBalancer 'k3d-test-serverlb'
INFO[0001] Starting cluster 'test'
INFO[0001] Starting servers...
INFO[0001] Starting Node 'k3d-test-server-0'
INFO[0008] Starting agents...
INFO[0008] Starting helpers...
INFO[0008] Starting Node 'k3d-test-serverlb'
INFO[0009] (Optional) Trying to get IP of the docker host and inject it into the cluster as 'host.k3d.internal' for easy access
INFO[0013] Successfully added host record to /etc/hosts in 2/2 nodes and to the CoreDNS ConfigMap
INFO[0013] Cluster 'test' created successfully!
INFO[0013] --kubeconfig-update-default=false --> sets --kubeconfig-switch-context=false
INFO[0013] You can now use it like this:
kubectl config use-context k3d-test
kubectl cluster-info

$ kubectl get pods -n kube-system
NAME                                      READY   STATUS              RESTARTS   AGE
helm-install-traefik-zdfph                0/1     ContainerCreating   0          14s
metrics-server-86cbb8457f-wgfqj           0/1     ContainerCreating   0          14s
local-path-provisioner-5ff76fc89d-f94qq   0/1     ContainerCreating   0          14s
coredns-854c77959c-68wvq                  0/1     ContainerCreating   0          14s

Which OS & Architecture
Linux
Which version of k3d
k3d version v4.4.3
k3s version v1.20.6-k3s1 (default)

Which version of docker
$ docker version
Client:
 Version:           20.10.6
 API version:       1.41
 Go version:        go1.16.3
 Git commit:        370c28948e
 Built:             Mon Apr 12 14:10:41 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.6
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.3
  Git commit:       8728dd246c
  Built:            Mon Apr 12 14:10:25 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.5.0
  GitCommit:        8c906ff108ac28da23f69cc7b74f8e7a470d1df0.m
 runc:
  Version:          1.0.0-rc93
  GitCommit:        12644e614e25b05da6fd08a38ffa0cfe1903fdec
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

$ docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.5.1-tp-docker)

Server:
 Containers: 14
  Running: 4
  Paused: 0
  Stopped: 10
 Images: 37
 Server Version: 20.10.6
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: false
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8c906ff108ac28da23f69cc7b74f8e7a470d1df0.m
 runc version: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.12.1-arch1-1
 Operating System: Arch Linux
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 7.673GiB
 Name: archdell
 ID: KZB2:U5J3:6VYU:7PRS:KFR6:GKJP:6IJP:R6RV:SHEE:YSA2:P5SI:D5FM
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

Workaround
The only way I have found to disable coredns is this:
k3d cluster create test -p '80:80@loadbalancer' -p '443:443@loadbalancer' --volume /dev/null:/var/lib/rancher/k3s/server/manifests/coredns.yaml

Hi @jtyr , thanks for opening this issue!
You're actually duplicating the entry command k3s server here, which is why k3s server --disable=coredns is passed in as a single argument to k3s server, making it fail.
Try just using the flag/argument that you want to pass in: k3d cluster create test -p '80:80@loadbalancer' -p '443:443@loadbalancer' --k3s-server-arg '--disable=coredns'
Feel free to re-open if this didn't work for you :)


Estimator's argument checking overzealous : model_fn has following not expected args: ['self']

I'm using TensorFlow (1.1) high-level API Estimators to create my neural net. But I'm using it into a class and I have to call an instance of my class to generate the model of the neural network. (Here self.a)
class NeuralNetwork(object):
  def __init__(self):
    """ Create neural net """
    regressor = tf.estimator.Estimator(model_fn=self.my_model_fn,
                                       model_dir="/tmp/data")
    // ...

  def my_model_fn(self, features, labels, mode):
  """ Generate neural net model """
    self.a = a
    predictions = ...
    loss = ...
    train_op = ...
    return tf.estimator.EstimatorSpec(
      mode=mode,
      predictions=predictions,
      loss=loss,
      train_op=train_op)

But I get the error : ValueError: model_fn [...] has following not expected args: ['self']. I tried to remove the self for the args of my model but got another error TypeError: … got multiple values for keyword argument.
Solution for now is to use a lambda function to wrap my function my_model_fn (see below) but it will be nicer without it.
class NeuralNetwork(object):
  def __init__(self):
    """ Create neural net """
    regressor = tf.estimator.Estimator(
        model_fn=lambda features, labels, mode: self.my_model_fn(features, labels, mode),
        model_dir="/tmp/data")
    // ...

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!

This is a feature request (and came from StackOverflow). Assigning @ispirmustafa: I think we just want to special-case member functions?

Yes this is a valid feature request.

+1 to this request, facing the same problem and was advised to open a feature request.

This is a good feature request. Anybody who wants to send a PR, please do. We won't get to this for a few weeks at least.

Can we use a lambda as a workaround in the meantime?

@JulesKzl could you post the stackoverflow link? Thanks.

Yes, the lambda workaround should work fine.

As I wrote and now edited to cite the Stackoverflow topic : Solution for now (as it was suggested on StackOverflow) is to use a lambda function to wrap my function my_model_fn (see below) but it will be nicer without it.


Event when image is being edited?

Is there a way we can know that the original image is being edited regardless of whatever filter, crop, flip, etc.

@allaniftrue Currently not. We'll going to support detailed event handers soon.

ok, cool!


Add goreleaser configuration to push Windows package to Chocolatey

Looks like goreleaser needs a bit more: ```  ⨯ release failed after 2m29s               error=chocolatey requires at least one windows archive

Looks like adding
    # Can be used to change the archive formats for specific GOOSs.
    # Most common use case is to archive as zip on Windows.
    format_overrides:
      - # Which GOOS to override the format for.
        goos: windows

        # The format to use for the given GOOS.
        #
        # Valid options are `tar.gz`, `tgz`, `tar.xz`, `txz`, tar`, `gz`, `zip`, `binary`, and `none`.
        format: zip

should fix it per https://github.com/goreleaser/goreleaser/issues/4450


[FLINK-23686][connector/kafka] Increase counter "commitsSucceeded" per commit instead of per partition

What is the purpose of the change
This pull request fixes a bug that counter "commitsSucceeded" is increased per partition instead of per commit.
Brief change log

Extract recordSucceededCommit as an individual method in KafkaSourceReaderMetrics
Invoke recordSucceededCommit in Kafka consumer commit callback

Verifying this change
This change added tests and can be verified as follows:

Subscribe to two partitions in KafkaSourceReader
Commit offset only once, and "commitsSucceeded" should be 1 instead of 2

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Thanks for the patch LGTM.
Merged to master: 62931a1665e6a6976d088ed49375f9fdf00229d9


Callback not supported when streaming

I see that this has already been mentioned (but closed without comment) in https://github.com/npm/node-tar/issues/162
It would be great if when passed a stream we could have a callback for completion of extraction as well.

+1, a callback for completion and errors.

You can do it this way, using the normal stream interface for detecting when it's done:
input.pipe(tar.x()).on('close', () => console.log('it is done!'))

Is that sufficient, or am I missing something?


Make github login optional

Currently the root of the application requires you to login with github to begin.
We should change it so that it's an optional login to add private repositories.
Otherwise, we should allow to add public repositories.

hey @haroon-sheikh i would like to work on this issue

Please go ahead and let me know if you have any questions.


Change last n version scheme to include all browsers listed on caniuse

As previouly mentioned for autoprefixer usage. Consider including current browsers with large market share such as Opera, UCBrowser etc.. (now classified as minor browser) as supported, by the n version scheme.
e.g. 'last 2 versions' should include Opera Mini, UCBrowser and Firefox for Android, Samsung...

I think we should do it.
But because it is major change, let’s wait for a while.

I think we should do it.
But because it is major change, let’s wait for a while.

@hzoo are you agree with this changes? It will affect to babel-present-env too.

@hzoo are you agree with this changes? It will affect to babel-present-env too.

That seems to be a big (breaking?) change. Opera Mini has a "pick'n'mix" approach to CSS features. Few of us write code with that browser in mind (whether we should or not is a separate discussion). I don't know how this would work in practice

@TCotton sure, it will be a major release for Browserslist and for Autoprefixer.

Done 0e145a6

Just to play devils advocate...
I wonder if https://github.com/ai/browserslist/commit/0e145a618627fefde0b16fc832c1acc9c95da3c6 will have a greater negative impact than a positive one? IOW, tons of people use latest n versions and will continue to do so after a major release. With this change, they're going to be potentially pushing 3-4x more bytes per CSS feature and never realize it. Extrapolating that out to a large CSS file could mean significant delays to first paint and other page load metrics :(
The feature differences between the latest major browsers and all browsers can be large. Would it make more sense to support a (new) opt-in query?

@ebidel prefixes are very easy task for gzip. I think bundle sizes become bigger only in 1-5%.

Very true about gzip. It would be interesting to real numbers from the wild. 26% of the web still doesn't compress responses.
More bytes are more bytes :)

larger responses cause more decompression work, increased memory, cpu time, etc.
larger responses increase issues with browser caching.

Mobile makes all of this worse. I've seen the HTTP cache take anywhere from 50-100ms to return a fresh asset on a Nexus 5 (no network cost). That's also without main thread contention. I'd imagine that number grows with resource size and main thread contention but haven't looked at that closely.

@ebidel maybe real benchmark will be better. Could you take your companies CSS and compare it for current behaviour and new behaviour (you can emulate 2.0 behaviour by last 2 chrome version, …).

I don't really have a meaningful file to test with. Something like a news site might be interesting and representative. I'll try to through in some time, but things are pretty busy between now and prepping for Google I/O.

I compared (minified, no gzip):

last 2 versions of any main browsers: 276,9 KB
last 2 versions of all browsers: 287,8 KB.

Result is 4% extra size. I think it is very good price for Internet which will be ready for any browsers (it is sad that most developers ignores browsers not popular in US, but have big market in other countries like Opera or Chinese browsers).

@ebidel I compared (minified, no gzip):

last 2 versions of any main browsers: 276,9 KB
last 2 versions of all browsers: 287,8 KB.

Result is 4% extra size. I think it is very good price for Internet which will be ready for any browsers (it is sad that most developers ignores browsers not popular in US, but have big market in other countries like Opera or Chinese browsers).

Nice! Thanks for looking into some numbers in a large stylesheet.  I think you're right about the 4%. There are bigger performance bottlenecks on the web. ~10kB is pretty chill in the grand scheme of web bloat :)

Very late comment, but some notes:

babel-preset-env does use browserslist for calculating supported browsers, but it only uses data for a specific list of browsers (https://github.com/babel/babel-preset-env/blob/20ddb722/src/index.js#L49; if it's not in this object, it's ignored).

matching all browsers with last n versions can make some linters like doiuse very angry and possibly impossible to use without restricting the matched set.

Yeap, it is too late 😅

👋 Coming over from https://github.com/postcss/autoprefixer/issues/838, is there a setting we could use to get back the major browsers only that were supported previously? Thanks!

Nope, because previous behavior is a bad practice in general.
In if you want it, write browsers by name.


HubbleStack isn't NIST SCAP Certified

Some certification frameworks require you to use a NIST certified tool for auditing, saddly hubblestack is not on the list:  https://csrc.nist.gov/Projects/scap-validation-program/Validated-Products-and-Modules
We love the Hubble, but are now faced with implementing "something listed" to meet our certification.
Is there any roadmap for getting certified?  or suggestions?

Interesting! I'll have to put aside some time to check out the validation requirements. We definitely want to be on that list.

I have this in my jira backlog but haven't had a chance to look into it yet... >.<

https://jira.corp.adobe.com/browse/CSTTEAM-43504


allow torch 2.0.0

PyTorch dependency has been updated as per your request. Closing this pull request.


import/extensions incorrectly fails an import with extra dots in filename

Given a file:
group.subgroup.js
and a rule:
"import/extensions": ["error", "never"]

and an import statement:
import "./group.subgroup";

It's incorrectly flagged as an error, despite not using the extension on that import.
I also tried this:
"import/extensions": [
      "error",
      {
        js: "never",
      },
    ]

Versions:
eslint v7.32.0
eslint-plugin-import v2.25.4

Oops, this actually doesn't happen with a fresh reproducible project. I guess it's related to something specific to my project. Closing.


edited file ChessGame.py

flipping the board instead of mirroring
highlighting the last move and check on the board

highlighting the board is a must.

Great addition! I'll review the changes and see if it'll work


Hc 944 vm and sql backup

This PR fixes the vm workload policy logic as there were some errors.
then it uses that to configure vm and sql backup for the file server and sql server ibase vms in small services spoke.
It creates a standard vm backup policy and applies it to ibase file server and the ibase sql server vm ( to protect just the os)
it creates a sql workload backup policy and applies it to ibase sql server vm ( to protect the sql database)

Spoke: smss-iBase-backup, Environment: prod and Pipeline Stage: Prod
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # azurerm_backup_policy_vm.policy["daily-backup-policy-1"] will be created
  + resource "azurerm_backup_policy_vm" "policy" {
      + id                             = (known after apply)
      + instant_restore_retention_days = (known after apply)
      + name                           = "daily-backup-policy-1"
      + policy_type                    = "V2"
      + recovery_vault_name            = "rsv-smss-core-001"
      + resource_group_name            = "rg-smss-core-001"
      + timezone                       = "UTC"

      + backup {
          + frequency = "Daily"
          + time      = "20:00"
        }

      + retention_daily {
          + count = 14
        }
    }

  # azurerm_backup_policy_vm_workload.backup_workload_policies["ibasesqlbackup01"] will be created
  + resource "azurerm_backup_policy_vm_workload" "backup_workload_policies" {
      + id                  = (known after apply)
      + name                = "ibasesqlbackup01"
      + recovery_vault_name = "rsv-smss-core-001"
      + resource_group_name = "rg-smss-core-001"
      + workload_type       = "SQLDataBase"

      + protection_policy {
          + policy_type = "Log"

          + backup {
              + frequency_in_minutes = 15
              + weekdays             = []
            }

          + simple_retention {
              + count = 8
            }
        }
      + protection_policy {
          + policy_type = "Full"

          + backup {
              + frequency = "Daily"
              + time      = "22:00"
              + weekdays  = []
            }

          + retention_daily {
              + count = 8
            }
        }

      + settings {
          + compression_enabled = false
          + time_zone           = "UTC"
        }
    }

  # azurerm_backup_protected_vm.vm["vm-ibase-sql1"] will be created
  + resource "azurerm_backup_protected_vm" "vm" {
      + backup_policy_id    = (known after apply)
      + id                  = (known after apply)
      + protection_state    = (known after apply)
      + recovery_vault_name = "rsv-smss-core-001"
      + resource_group_name = "rg-smss-core-001"
      + source_vm_id        = "/subscriptions/becc4bf3-5028-43e4-8008-06e9362d6b86/resourceGroups/RG-SMSS-IBASE-001/providers/Microsoft.Compute/virtualMachines/vm-ibase-sql1"
    }

  # azurerm_backup_protected_vm.vm["vm-ibase-win1"] will be created
  + resource "azurerm_backup_protected_vm" "vm" {
      + backup_policy_id    = (known after apply)
      + id                  = (known after apply)
      + protection_state    = (known after apply)
      + recovery_vault_name = "rsv-smss-core-001"
      + resource_group_name = "rg-smss-core-001"
      + source_vm_id        = "/subscriptions/becc4bf3-5028-43e4-8008-06e9362d6b86/resourceGroups/RG-SMSS-IBASE-001/providers/Microsoft.Compute/virtualMachines/vm-ibase-win1"
    }

  # azurerm_backup_protected_vm.vm-sql["vm-ibase-sql1"] will be created
  + resource "azurerm_backup_protected_vm" "vm-sql" {
      + backup_policy_id    = (known after apply)
      + id                  = (known after apply)
      + protection_state    = (known after apply)
      + recovery_vault_name = "rsv-smss-core-001"
      + resource_group_name = "rg-smss-core-001"
      + source_vm_id        = "/subscriptions/becc4bf3-5028-43e4-8008-06e9362d6b86/resourceGroups/RG-SMSS-IBASE-001/providers/Microsoft.Compute/virtualMachines/vm-ibase-sql1"
    }

Plan: 5 to add, 0 to change, 0 to destroy.


Reworking how ingest_spectrum works using the ORM

This is attempting to rework how ingest_spectrum functions by utilizing the ORM and removing extra checks.
Some of the tests were failing since there are explicit strings that were being checked- they "bad" examples still fail, they just do so for other reasons or the string output is different. Some test cleanup may be needed.
We may also want to consider expanding the cleanup and/or revisit the use of flags

Could also set it to merge into SIMPLE-AstroDB:main but if you wanted to use this for your branch first, this may be one way to do it.

Withdrawn in favor of https://github.com/SIMPLE-AstroDB/SIMPLE-db/pull/501/


[Python BQ] Follow up of #28592: Allow setting a fixed number of Storage API streams

Had to fix some lint checks in #28592 which was reverted in #28613

Run Python_Xlang_Gcp_Dataflow PostCommit

Run Python_Xlang_Gcp_Direct PostCommit

retest this please

Run Python_Xlang_Gcp_Direct PostCommit

Also: Please don't merge with failing GitHub statuses. Kick them to green. And the coverage complaint seems legitimate.

@kennknowles some FhirIO tests are very flaky (maybe perma-failing) on Github workflow #28635


Add 'Show in finder' option in file explorer

@impact27 Thanks for your contribution, however, you must take in account that the open command is not available on other OS like Linux and Windows

This should be of your interest:
def open_file(filename):
    if sys.platform == "win32":
        os.startfile(filename)
    else:
        opener = "open" if sys.platform == "darwin" else "xdg-open"
        subprocess.call([opener, filename])

Sure but then it should not be called "open in finder" but open in file explorer? Anyway I added a verification for the os (OSX is Darwin) so It should only appear on mac.

Maybe open in external file explorer?

I agree that it should be called Open in File Explorer

@impact27 Can you rebase and compare this PR against 3.x branch?

I am unsure what you want me to do. Should I open a new PR with https://github.com/impact27/spyder/tree/3.x?
Regarding window and linux, I am not sure how to "Show in external explorer" and I don't have these OS to test. Maybe the feature can be added for mac and more work can be done later to add Window and Linux compatibility?

@impact27, thanks a lot for your contribution.

Should I open a new PR with https://github.com/impact27/spyder/tree/3.x?

If you want your contribution to be part of Spyder 3.2, yes, you need to reopen your PR against that branch. However, if you don't mind to wait until Spyder 4 for others to use this, then you can leave things as they are.
Note: Spyder 4 is at least 6 months away to be released, it could be more.

@ccordoba12 closing this one?

Yep. @impact27, we'll merge your other PR, and then internally merge it with master.
Thanks a lot for your patience with our internal procedures.


Allow user to disable depth write for a specific mesh

Usually you can make the disabling part of the material, rather than the mesh, maybe that is what you meant.

yep


docs: fix typo

Sorry, there's a typo in the previously merged PR 😭  so bad

this has been addressed in another PR :)

this has been addressed in another PR :)


bug: no images showing

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] support request

Current behavior
No images or icons showing at all. See 404s on start page for example:

> GET http://localhost:5555/favicon.ico 404 (Not Found)
> GET http://localhost:5555/assets/png/noise.png 404 (Not Found)
> GET http://localhost:5555/assets/jpg/gesicht.jpg 404 (Not Found)

Expected behavior
Images should show up.
Minimal reproduction of the problem with instructions
There is no assets directory created and the images are not loaded into assets. Should there be an init script or so doing this? Maybe only because of running locally.

assets script is working (./tools/tasks/project/get.assets.sh) and can be run manually. Images are showing.


Docs/WordPress.WhiteSpace.OperatorSpacing

Adds documentation for the WordPress.WhiteSpace.OperatorSpacing
Related to #1722

Just thinking out loud: you could possibly combine the two "invalid" examples into one with an inline comment to separate them // Too little space, // Too much space and place that one to go with the first Valid example.
For the second Valid example, the same code sample as for the Valid case can be used with some superfluous whitespace after the && on the second line.
What do you think ?

Sounds good to me! I applied the changes as suggested.

@ckanitz Just wondering if you'll have chance to finish this off in the near future.
I'd like to release WPCS 2.2.0 soon and it would be great if this PR could be included.
If you haven't got time or lost interest, please let us know and we'll see if we can find someone to take over.

I've rebased the PR and added one commit to make the last fixes needed. Let's get this merged!
For whomever will merge this: probably squash/merge would be a good idea.


Add a block capable of measuring the quantity of specific items inside the dimensional storage system.

Is your feature request related to a problem? Please describe.
I want to be able to measure the quantities of specific items inside the Dimensional Storage System for use in redstone and automation.
Describe the solution you'd like
Bare bones concept: A “dimensional storage observer” block that would enable a comparator to measure the quantity of a specific item within the dimensional storage system.
Fleshed out concept: The Dimensional Storage Observer (DSO) is a foliot infused Observer block that, once attuned to a dimensional storage actuator, can be read by a comparator which will output a redstone signal with a strength dependent on the quantity of a specific item in the dimensional storage system. (i.e. the same way comparators work with standard containers, but only measuring a specific item)
The DSO would have an interface with a slot in which you place the item that you wish to measure the quantity of.
To determine the “size” of the container, I have two possible methods you could use:
Method 1: Add another slot in the interface which only accepts items from an approved list. As the items get more valuable, the size of the container increases. So for example the items might go: Dirt, Stone, Copper Ingot, Iron Ingot, Silver Ingot, Gold Ingot, Lapis, Emerald, Diamond.
Method 2: Use chalk to write a rune on the DSO, the size of the container is determined by the quality of the chalk used. This is simpler and easier to describe, but less configurable than method 1.
Additional context
This feature solves the same problem as my previous feature request (https://github.com/klikli-dev/occultism/issues/193) but does so in what I believe would be a much easier way to implement.
Currently I’m using Create mod Stockpile Switches to achieve the same functionality to a degree, however they don’t scale properly once you have significant capacity in your storage actuator.
You could have the block output the redstone signal directly instead of having to rely on a comparator (this is what Create’s Stockpile Switch does). I included the comparator in my request because I think it might be easier to implement.
The minecraft wiki page on comparators has the formula for calculating signal strength: https://minecraft.fandom.com/wiki/Redstone_Comparator#Containers
Thanks for considering this feature request!

Botania's Corporea Crystal cubes work wonderfully for this purpose (you just need to disable the stack combining in Occultism config to get them to display the right stack count - which has a performance impact). I recommend having a look at how those work if you want some alternate ideas for how to implement this

Someone mentioned in discord that the corporea crystals now count the real stack size (even above the vanilla maximum) and accurately display the amount - can anyone confirm this?

Someone mentioned in discord that the corporea crystals now count the real stack size (even above the vanilla maximum) and accurately display the amount - can anyone confirm this?

I used Corporea + Dimensional storage as my defacto storage in a recent playthrough (which ended two weeks ago). I cannot confirm if it's still the case now because I've injured my eye and cannot play games until it heals, but for my playthrough I had to disable the stack combining in dimensional storage for the Crystal Cube to report the correct stack counts.

Someone mentioned in discord that the corporea crystals now count the real stack size (even above the vanilla maximum) and accurately display the amount - can anyone confirm this?

I'm going to investigate this when I get a chance to play this evening.

Someone mentioned in discord that the corporea crystals now count the real stack size (even above the vanilla maximum) and accurately display the amount - can anyone confirm this?

Just checked with the most recent version of Botania, Corporea crystal doesn't count correctly.

External counting measures can be used by setting overrideItemStackSizes=false in the occultism server config.
The storage system will then behave like a very large chest and leave stack sizes untouched.


Swagger docs /books/v1/{book_title} wrong response body schema

Link to code: https://github.com/erev0s/VAmPI/blob/master/openapi_specs/openapi3.yml#L562
I think response body for this endpoint should be just object not array of objects

Maybe you are referring to an older version? not sure.
Currently it is an object.


Reorganize repo where the SSF prototype is front and center

Right now the SSF is under kubernetes/ and various pieces and helpers are under it at scripts/ and tekton-resources/demo.
It should be cleaned up so the installation and configuration scripts are front and center with specific example projects and pipelines existing under a examples/ or tests/ directory with adequate documentation explaining the purpose of a specific example or test.

This has been completed


Add Footer and Change Font Family Of Texts

Please Assign This tasks to me

Hi please assign this to me


CI socket timeout occured

This error periodically happens on CI
https://circleci.com/gh/ethereum/source-verify/442

Circleci discuss currently not working properly.
https://discuss.circleci.com/t/maximum-build-time-for-builds/18383


Import slowdown after v1

After upgrading to v1, I've noticed that it takes almost double the time to import Pydantic.  Observe:
$ python3 -m pip install -U 'pydantic<1'
[...]
Successfully installed pydantic-0.32.2

$ seq 2 | xargs -I -- python3 -X importtime -c '
  import pydantic
  print("pydantic version:", pydantic.VERSION)
  ' 2>&1 | begin
      head -n 1
      tail -n 2
  end
import time: self [us] | cumulative | imported package
import time:      1058 |      70730 | pydantic
pydantic version: 0.32.2

$ python3 -m pip install -U pydantic
[...]
Successfully installed pydantic-1.3

$ seq 2 | xargs -I -- python3 -X importtime -c '
  import pydantic
  print("pydantic version:", pydantic.VERSION)
  ' 2>&1 | begin
      head -n 1
      tail -n 2
  end
import time: self [us] | cumulative | imported package
import time:       802 |     128663 | pydantic
pydantic version: 1.3

v0.32.2 takes approximately 70ms to import on my MBP; v1.3 takes 130ms.
attrs for comparison takes 36ms:
$ seq 2 | xargs -I -- python3 -X importtime -c '
  import attr
  print("attrs version:", attr.__version__)
  ' 2>&1 | begin
      head -n 1
      tail -n 2
  end
import time: self [us] | cumulative | imported package
import time:       882 |      35659 | attr
attrs version: 19.3.0

I can understand that this might not be something you'd want to spend time on, depending on what your direction for Pydantic is; but slow warmups have been plaguing Python CLIs for a very long time.  If you'd like to investigate this further, tuna can help you visualise your dependency tree.  Here's what it's showing me for tuna (python3 -X importtime -c 'import pydantic' 2>| psub):

There is the unfortunate practice in Python of importing the entire package's contents in __init__ and (unfortunately) once you've done that, there's no going back - not without a breaking release anyway.
As always, thanks for all your work on Pydantic.

(I think the label was added automatically because I selected the 'bug' option when I was opening the issue.)

See #1124, we can move more things out of __init__.py in v2.
Very weird that network.py takes so long to load. Can we get any more details on why that is?

It appears to be caused, in no small part, by the pre-compilation of this particular regex with a range containing 262,057 characters:
_domain_ending = r'(?P<tld>\.[a-z]{2,63})?\.?'
_int_chunk = r'[_0-9a-\U00040000](?:[-_0-9a-\U00040000]{0,61}[_0-9a-\U00040000])?'
int_domain_regex = re.compile(fr'(?:{_int_chunk}\.)*?{_int_chunk}{_domain_ending}', re.IGNORECASE)

Just out of curiosity, I tried to compile it using regex and it only took 1ms, compared to 84ms for re.  I wonder if this should be reported upstream.

Yes probably, though I doubt you'll get a very helpful response.
I think the solution for us is to compile this regex in a lazy way. Eg, only create it when a field using it is used.

Regexes are compiled and cached on first use by the re module.  The issue is that regex flags aren't part of the regex itself in Python so people are drawn to re.compile as a means to attach flags to their regexes.

I agree, but I think better to explicitly generate and cache, I'll create a PR and let you check.

thanks for letting me know about tuna, very useful.
See #1132 for a fix on most things.
We could also move compiled to utils and wrap it in a function is_compiled() to have improve things a bit more, but won't make a massive difference.

The improvement isn't as dramatic for me - it's shaved off about 40ms - but it's definitely noticeable.  Thanks for working on this.

Are you comparing it to current master uncompiled?
Could you show me tuna images (or import logs) for before and after #1132?

I'm comparing it against 1.3:

import-speedup:

These tend to vary by +/-20 ms.

Okay, but is v1.3 compiled or sime python? You can check with utils.version_info()

python -c "import pydantic.utils; print(pydantic.utils.version_info())"

Ah right, no, it wasn't compiled.  I installed Cython and built 1.3 from sdist and it doesn't look it's made much of a difference - still measuring at about 140 ms and 80 ms respectively.
             pydantic version: 1.3
            pydantic compiled: True
                 install path: [...]
               python version: 3.8.0 (default, Dec 12 2019, 11:47:45)  [Clang 7.1.0 (tags/RELEASE_710/final)]
                     platform: macOS-10.14.6-x86_64-i386-64bit
     optional deps. installed: ['typing-extensions']

Okay weird, I got a bigger difference.

see my comments on #1132, comment there with any suggestions on how to improve the change, otherwise I'll merge that.


Add xamira networks to training and support page

Signed-off-by: Fabian Thorns<EMAIL_ADDRESS>

@RichiH Sorry for bugging you about one of the less important PRs, I saw this one pending for a while and was wondering if there is anything I forgot or if there is anything I could do to help getting this one merged. Thank you :)

Thank you for this. I think the current rule is that the "courses" are limited to online trainings.

Hi @roidelapluie , thanks for the explanation and sorry for the late response. We do actually delivery training online, although it is instructor lead. I assume you're referring to self-paces training only, right? In that case, I could adjust the pull request to only add us to the commercial support section; although I think that the ability to collect instructor led training might be helpful, too. But that is probably another topic. Let me know how you'd like to proceed, if we have a chance to make it at least to the commercial support section I'll make the necessary changes. Thanks! :)

Yeah, Courses is just for self-paced online courses so far, but in general I support the idea of making this page more useful. Frequently people also ask me who could help them with some consulting aspect (since I'm doing less consulting with PromLabs now). If we knew what kinds of services each company offered (hosted service, consulting, self-paced training, live training, software engineering, commercial additional software, ...), then we could add tags and/or make things searchable / filterable somehow. Of course that would require reaching out to the various companies to get better information on what they offer, because it's often not 100% clear to us as well.

Yep, that's a larger project...
Thanks for the adjustment! :+1:


How do I undo 'remember my choice'?

It seems to be literally "once and for all". related to #1

Hi @jan-glx, you can use the Tablr: Clear Csv Choice command for that purpose. I'll update the docs with a mention about since I forgot to add one.

Thanks!


path/filepath: go test fails when GOROOT isn't writeable

What version of Go are you using (go version)?
$ go version
go version go1.10 darwin/amd64

Does this issue reproduce with the latest release?
Yes, with Go 1.10 (final).
What operating system and processor architecture are you using (go env)?

GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/Dmitri/Library/Caches/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/Dmitri/Dropbox/Work/2013/GoLanding:/Users/Dmitri/Dropbox/Work/2013/GoLand"
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/tw/kgz4v2kn4n7d7ryg5k_z3dk40000gn/T/go-build654935185=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

Install Go 1.10 via go1.10.darwin-amd64.pkg installer on a Mac.
Observe that GOROOT isn't writeable by normal user. (I'm happy about this, it helps me avoid accidentally changing its contents.)
Run go test path/filepath.

What did you expect to see?
$ go test path/filepath
ok  	path/filepath	0.027s

What did you see instead?
~ $ go test path/filepath
--- FAIL: TestWalk (0.00s)
	path_test.go:367: makeTree: open testdata/a: no such file or directory
	path_test.go:367: makeTree: open testdata/c: no such file or directory
	path_test.go:367: makeTree: open testdata/d/x: no such file or directory
	path_test.go:367: makeTree: open testdata/d/z/u: no such file or directory
	path_test.go:367: makeTree: open testdata/d/z/v: no such file or directory
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x10f69c6]

goroutine 17 [running]:
testing.tRunner.func1(0xc4200acc30)
	/usr/local/go/src/testing/testing.go:742 +0x29d
panic(0x11247e0, 0x11fdfd0)
	/usr/local/go/src/runtime/panic.go:505 +0x229
path/filepath_test.mark(0x0, 0x0, 0x1165a00, 0xc420088720, 0xc42000a320, 0x1, 0x1165a00, 0xc420088720)
	/usr/local/go/src/path/filepath/path_test.go:392 +0x26
path/filepath_test.TestWalk.func1(0x114b64f, 0x8, 0x0, 0x0, 0x1165a00, 0xc420088720, 0x20, 0x112eee0)
	/usr/local/go/src/path/filepath/path_test.go:440 +0x5d
path/filepath.Walk(0x114b64f, 0x8, 0xc42000a340, 0xc4200ca000, 0x0)
	/usr/local/go/src/path/filepath/path.go:401 +0x6c
path/filepath_test.TestWalk(0xc4200acc30)
	/usr/local/go/src/path/filepath/path_test.go:443 +0x136
testing.tRunner(0xc4200acc30, 0x11545c8)
	/usr/local/go/src/testing/testing.go:777 +0xd0
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:824 +0x2e0
FAIL	path/filepath	0.012s

However, adding sudo, it works okay:
$ sudo go test path/filepath
ok  	path/filepath	0.027s

This happens because TestWalk calls makeTree, which tries to create new files in GOROOT/src/path/filepath directory. Since the GOROOT directory isn't writeable by normal user, creating the test tree fails. Then, trying to walk the tree results in a nil pointer dereference panic.
I'm not sure why TestWalk tries to write in GOROOT at all. Shouldn't it create a temporary directory and use that?

I wonder if there should be a "read-only builder"? If we're committed to supporting a RO GOROOT maybe?

For what it's worth, I think it's fine if such an issue comes up occasionally because of no "read-only builder". If it comes up, it can be reported, and then fixed. If no one notices for some time, there's no harm.
This is assuming that all such issues are trivial to resolve by writing to a temporary directory rather than GOROOT.


How to override the ID scalar?

I am trying to implement an ID scalar according to the GraphQL Global Object Identification Specification.
codegen.ts
import { defineConfig } from "@eddeee888/gcg-typescript-resolver-files";
import type { CodegenConfig } from "@graphql-codegen/cli";

const config: CodegenConfig = {
  schema: "internal/schema/**/*.graphql",
  generates: {
    "internal/schema": defineConfig({
      scalarsOverrides: {
        ID: {
          resolver: "base/resolvers/ID#IDResolver",
        },
      },
    }),
  },
};

export default config;

base/resolvers/ID.ts
export const IDResolver = {};

No resolver is generated in resolvers.generated.ts.

Hi @Colt45s ,
It looks like you can't override default scalars like ID at runtime: https://github.com/graphql/graphql-js/issues/917
Since it cannot be done at that level, I don't think we can support it at codegen level 🙂
Unless you are able to override the default scalar somehow?

Closing this as overriding default scalar is not currently supported at GraphQL level. Thanks for reaching out!


Merge 7.0.0 to dev

Merging code from main branch (6.16.0 release) to dev.

Resolved 123 merge conflicts.

nit: end of file new lines
LGTM otherwise.

Yep, the end of file problems came straight out of the internal repo.  I'm working on a CL to push buid fixes made here back into the internal repo.  I'll be sure to add new lines to these files.  Thanks!

@googlebot I fixed it.


error: Disabling module "alsa" (reason: No built-in support for 'internal/alsa')

Hey,
I have some trouble running alsa volume control on polybar i get this message when I try to run it on my Logitech Headset :
error: Disabling module "alsa" (reason: No built-in support for 'internal/alsa')
This my trouble shooting state :
polybar --version output :
polybar 3.3.0
Features: -alsa +curl +i3 -mpd -network(wireless-tools) -pulseaudio +xkeyboard
amixer scontrols output :
Simple mixer control 'Master',0
Simple mixer control 'Capture',0
amixer -c 1 scontrols normaly my headphone headset :
Simple mixer control 'Headphone',0
Simple mixer control 'Mic',0
cat /proc/asound/cards output :
0 [PCH            ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xdf240000 irq 133
1 [Headset        ]: USB-Audio - Logitech G430 Gaming Headset
Logitech Logitech G430 Gaming Headset at usb-0000:03:00.0-2, full speed
My alsa configuration :
[module/alsa]
type = internal/alsa
master-soundcard = hw:1
format-volume = <label-volume> <bar-volume>
label-volume = VOL
label-volume-foreground = ${root.foreground}
format-muted-prefix = " "
format-muted-foreground = ${colors.foreground-alt}
label-muted = sound muted
bar-volume-width = 10
bar-volume-foreground-0 = #55aa55
bar-volume-foreground-1 = #55aa55
bar-volume-foreground-2 = #55aa55
bar-volume-foreground-3 = #55aa55
bar-volume-foreground-4 = #55aa55
bar-volume-foreground-5 = #f5a70a
bar-volume-foreground-6 = #ff5555
bar-volume-gradient = false
bar-volume-indicator = |
bar-volume-indicator-font = 2
bar-volume-fill = ─
bar-volume-fill-font = 2
bar-volume-empty = ─
bar-volume-empty-font = 2
bar-volume-empty-foreground = ${colors.foreground-alt}`

polybar --version output :
polybar 3.3.0
Features: -alsa +curl +i3 -mpd -network(wireless-tools) -pulseaudio +xkeyboard

-alsa signifies you forgot to install alsa-lib before compiling polybar.
See https://github.com/jaagr/polybar/wiki/Compiling#optional-dependencies

There are already install :
alsa-utils-1.1.8-2.fc29.x86_64
alsa-lib-1.1.8-1.fc29.x86_64
alsa-plugins-pulseaudio-1.1.8-1.fc29.x86_64
qemu-audio-alsa-3.0.0-3.fc29.x86_64
alsa-ucm-1.1.8-1.fc29.noarch
alsa-lib-devel-1.1.8-1.fc29.x86_64

It's ok now I had to recompile polybar with cmake -DENABLE_ALSA=ON and make install.
Now it's OK :
`Features: +alsa +curl +i3 -mpd -network(wireless-tools) +pulseaudio +xkeyboard


Invoking segment on a fragment URI gives RangeError: Maximum call stack size exceeded

Failure case here. Am I even using this properly? It took me a while to grok this (I initially thought I could perform all the operations in that gist without breaking the chain), but I believe fragment( true ) returns a new subclass of URI that operates on the fragment (?) – which should be able to take a subsection of URI's mutation and query API?

i've found the same issue using add/removeSearch using fragment:
http://requirebin.com/?gist=6baf515391cda14d4564
however i think that fragment plugin shouldn't be removed since it's very usefull for single page apps

A workaround for this problem to me was to create a new fragment every time I update it. e.g.
uri.fragment(true).setSearch(...);
uri.fragment(true).removeSearch(...);

Reusing the fragment seems to cause stack overflow:
var fragment = uri.fragment(true);
fragment.setSearch(...); // OK
fragment.removeSearch(...); // Stack overflow


React 19: createContext requires an argument

What will this achieve?
Similar to https://github.com/carbon-design-system/ibm-products/issues/5038, this issue is specific to updating all usage of createContext in order to become compatible with React 19.

How will success be measured?

Additional information

Designs
Existing code
etc

### Components using `createContext` without an argument
- [ ] `Coachmark/utils/context.js`
- [ ] `ConditionBuilder/ConditionBuilderContext/DataTreeContext.js`
- [ ] `Datagrid/addons/Filtering/FilterProvider.js`
- [ ] `Datagrid/addons/InlineEdit/InlineEditContext.js`
- [ ] `WebTerminal/hooks/index.js`
- [ ] `scripts/example-gallery-builder/update-example/templates/src/ThemeSelector/ThemeContext.jsx`

@matthewgallo Have we added all the affected components, and is this ready for backlog?

Yes it should be ready for backlog now. Sorry, I missed your comment here!


[stable/airflow] add option for airflow initdb

Signed-off-by: Marcin Szymanski<EMAIL_ADDRESS>What this PR does / why we need it:
Which issue this PR fixes
Running airflow initdb on after the database was initialised recreates some example objects as connections, so it should be possible to disable it
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @maver1ck

/assign @gsemet


[MINOR][R] Deduplicate RStudio setup documentation

What changes were proposed in this pull request?
This PR targets to deduplicate RStudio setup for SparkR.
How was this patch tested?
N/A

cc @felixcheung and @shivaram

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/6531/
Test PASSed.

Test build #100605 has started for PR 23421 at commit 072dbbf.

Test build #100605 has finished for PR 23421 at commit 072dbbf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100605/
Test PASSed.

Merged to master.
Thanks @dongjoon-hyun


Attempt conditioning using internal method first, then use partial if it fails

At the moment we always use functools partial if we partially evaluate a callable function in Distribution conditioning. However, if we want to maintain structural information, then we should attempt to use the buit-in method of the class first.
The suggestion is, in the case of partial evaluation of a conditonal distribution, to allow the underlying attribute to be responbile for the partial evaluation when possible.
For example:
x = Gaussian(0 1).rv # Random variable for x
z = Gaussian(0,1).rv # Random variable for z
A = Linearmodel(mat)

y = Gaussian(A@x+z, 1) # Distribution for y, now depending on both x and z, e.g. it is condiotional on x an z.

# Previous conditioning on z yields:
y(z=1).mean # this results in a partial function defined as lambda x: A@x+1

# New conditioning on z yields (when supported by objects like random variables or e.g. a JointModel):
y(z=1).mean # This results in an AffineModel x -> Ax+1

# When not supported by the unnderlying object the behavior should be the same as before using partial functions

DoD

[x] Impact of change is investigated
[ ] Potential unit tests added
[ ] Change is implemented
[ ] Change is reviewed.

@jakobsj DoD

@nabriis I think this sounds like a sensible fix, but I cannot immediately see what consequences it might have. For DoD, I think we should include some evidence of exploring potential consequences and ensuring nothing breaks. For example which relevant unit tests are in place - should any be modified or new ones added? So I'd think at least a DoD item capturing what to do in terms of unit tests, and possibly another DoD item on ensuring there aren't any other undesired consequences.

Ok let us discuss next time we meet.


Fix removal of quotes from property names

See: https://github.com/babel/babili/pull/543/files

@rwjblue You need to update the babel-preset-babili dependency in broccoli-babili to fix this.

Updated, and released as 0.2.0.
Thank you!

@rwjblue tried v0.2.0 and the problem still occurs, will open up the issue with the babili repo


linter crash from :: bind operator in JSX

Migrated from https://github.com/babel/babel-eslint/issues/472
I'm using this syntax:
::this.foo()
However, eslint crashes in this case:
The prop value with an expression type of BindExpression could not be resolved.
  Please file issue to get this fixed immediately.
Error: The prop value with an expression type of BindExpression could not be resolved.
  Please file issue to get this fixed immediately.
    at Object.extract [as JSXExpressionContainer] (/Users/tsheaff/Code/private/calm/www/node_modules/jsx-ast-utils/lib/values/expressions/index.js:173:11)
    at getValue (/Users/tsheaff/Code/private/calm/www/node_modules/jsx-ast-utils/lib/values/index.js:48:27)
    at extractValue (/Users/tsheaff/Code/private/calm/www/node_modules/jsx-ast-utils/lib/getPropValue.js:24:12)
    at getPropValue (/Users/tsheaff/Code/private/calm/www/node_modules/jsx-ast-utils/lib/getPropValue.js:41:10)
    at /Users/tsheaff/Code/private/calm/www/node_modules/eslint-plugin-jsx-a11y/lib/rules/no-static-element-interactions.js:76:95
    at Array.some (native)
    at EventEmitter.JSXOpeningElement (/Users/tsheaff/Code/private/calm/www/node_modules/eslint-plugin-jsx-a11y/lib/rules/no-static-element-interactions.js:75:52)
    at emitOne (events.js:101:20)
    at EventEmitter.emit (events.js:191:7)
    at NodeEventGenerator.applySelector (/Users/tsheaff/Code/private/calm/www/node_modules/eslint/lib/util/node-event-generator.js:265:26)
    at NodeEventGenerator.applySelectors (/Users/tsheaff/Code/private/calm/www/node_modules/eslint/lib/util/node-event-generator.js:294:22)

Here is my .eslintrc:
module.exports = {
  'env': {
    'browser': true,
    'node': true,
  },
  'plugins': [ 'react' ],
  'parser': 'babel-eslint',
  'extends': 'airbnb', /* see https://github.com/airbnb/javascript */
  'rules': {
    /* override a few airbnb rules */
    'strict': 0,
    'space-before-function-paren': ['error', 'never'],
    'func-names': 'off',
    'no-console': 'error',
    'max-len': 'off',
    'global-require': 'error',
    'consistent-return': 'off',
    'class-methods-use-this': 'off',
    'object-shorthand': ['error', 'never'],
    'no-param-reassign': ['error', {
      'props': false
    }],
    'brace-style': ['error', '1tbs', { allowSingleLine: false }],
    'arrow-parens': ['error', 'always'],
    'arrow-body-style': 'off',
    'import/prefer-default-export': 'off',
    'import/extensions': ['error', {
      'js': 'never',
      'json': 'always'
    }],
  },
}

Here are my dependencies:
    "babel-eslint": "^7.2.3",
    "eslint": "^3.19.0",
    "eslint-config-airbnb": "^15.0.1",

When I remove the 'parser': 'babel-eslint', line from the config, this crash goes away.  However in that case native eslint doesn't recognize the :: and says Parsing error: Unexpected token : (Fatal) It also goes away if the file I'm linting does not use the :: syntax
This mini-repo recreates the error: https://gist.github.com/tsheaff/003685ca6a163fb467a29fb7c70fbf10
The :: operator on line this line is the offending one. If I remove that or switch to .bind(this) syntax I don't get the error.  I also don't get the error if the :: is not in JSX

the reason is that it doesn't account for :: because it's using acorn-jsx instead of babylon. the rule would need to update it's version of that util

Duplicate of #33.


Oauth/Social backends - very minor cleanup

As explained in the commits, there is a bit of a weird juggling of "social backend" / "oauth backend" concepts in the code, where we're better served just thinking of "social backends".
Otherwise, when we add SAML, we would have to add some additional logic dealing with the fact that it's a "social" backend, but not an oauth backend and things would just get more confusing, for no benefit.

These are great, merged, thanks @mateuszmandera!
Effectively cleanups we should have done after we integrated the python-social-auth Google auth backend (which removed the only oauth, non-"social", backend).


sdrangel: 7.8.6 -> 7.9.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/f4exb/sdrangel/releases.
meta.description for sdrangel is: Software defined radio (SDR) software
meta.homepage for sdrangel is: https://github.com/f4exb/sdrangel
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 7.9.0 with grep in /nix/store/771m8d6vfnw7qfk6p89bdaiv8m79irrk-sdrangel-7.9.0
found 7.9.0 in filename of file in /nix/store/771m8d6vfnw7qfk6p89bdaiv8m79irrk-sdrangel-7.9.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
sdrangel

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/771m8d6vfnw7qfk6p89bdaiv8m79irrk-sdrangel-7.9.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sdrangel https://github.com/r-ryantm/nixpkgs/archive/ed0538b68519d897562dd1d7efa5f1b5a83e6b85.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/771m8d6vfnw7qfk6p89bdaiv8m79irrk-sdrangel-7.9.0
ls -la /nix/store/771m8d6vfnw7qfk6p89bdaiv8m79irrk-sdrangel-7.9.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

sdrangel

Maintainer pings
cc @alkeryn for testing.

Binary working, lgtm
Result of nixpkgs-review pr 214492 run on x86_64-linux 1

1 package built:

sdrangel


Merge develop into master

Do you know why the build is failing?

@codysoyland I think https://s3.amazonaws.com/build.pilosa.com/pilosa-master-linux-amd64.tar.gz is not up-to-date. The tests fail against that, but they pass when run against git master.

@yuce ah, good find. I did some digging and the binary prereleases are indeed not being uploaded. I put my notes in this ticket: https://github.com/pilosa/pilosa/issues/1497
Will try to resolve this tomorrow.

Thanks @cody
On Thu, Jul 12, 2018, 04:29 Cody Soyland<EMAIL_ADDRESS>wrote:

@yuce https://github.com/yuce ah, good find. I did some digging and the
binary prereleases are indeed not being uploaded. I put my notes in this
ticket: pilosa/pilosa#1497 https://github.com/pilosa/pilosa/issues/1497
Will try to resolve this tomorrow.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pilosa/python-pilosa/pull/108#issuecomment-404360711,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAfUWlDD9k5wFTsn9z1JujNJl1BQ-lsrks5uFqZngaJpZM4VGPgy
.

ping! ping!


Removed const-ness from Reporter interface methods

I shot myself in the foot when I made them so. It limits implementing classes too much.

Green (Travis-wise)

LGTM, but  I want a heads up from @nicolasnoble before merging since I don't exactly know the rules in the Jenkins world.

Jenkin's green now too :)

So there's still a red line for "unstable & flaky tests" - what to do about that?

Ignore it. Nico is working on making it not red.
On Fri, Jun 19, 2015, 9:16 PM Vijay Pai<EMAIL_ADDRESS>wrote:

So there's still a red line for "unstable & flaky tests" - what to do
about that?
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/2136#issuecomment-113706734.


How to install a package globally (for all users)

Is there a way to perform a system-wide package installation using vcpkg?

Can you give an example of the scenario you need?

@AdelCraftZ ping for response.

We don't have enough information to solve this issue, unfortunately; if you have any more information to help us solve this, please reopen!


Testing staged-release artifacts

https://maven.apache.org/guides/development/guide-testing-releases.html

see https://github.com/j143/systemds


Watch mode

CSS map changes doesn't apply, if module was changed.
It's due all modules in node js exposed as cached objects.
All reference saved in require.cache.
This tiny helper, that we use for clear require.cache:
  /**
   * Clears node.js require cache by key.
   * @param {string} key Cache key.
   */
  function clearCacheKey (key) {
    delete require.cache[key];
  }

Yeah, that's true. Node.js caches all the require calls by default.
I assume you use this feature for the development needs only.
I think, I can add a check for the environment variable NODE_ENV and if it's equal to development, then clean cache from the require calls. Something similar to this: https://github.com/reactjs/express-react-views/blob/master/index.js#L59-L66

Yes, it's for development workaround. env var is good idea.

@sullenor When you can fix it?

@markuplab I'll try tomorrow

done, 2.1.0

Hey, everybody.
Thx, for great module!
I have some minor problem. Actually it`s not a problem at the moment, but think it could make some in future.
I'm talking about this https://github.com/reactjs/express-react-views/blob/master/index.js#L59-L66
Think NODE_ENV = "development" is very wide thing. And I would prefer something like this
var initHooks = require('css-modules-require-hook');
initHooks({
	generateScopedName: generateScopedName(config),
	extensions: config.extensions.styles,
	preprocessCss,
	processCss,
	debug: true // <------------------
});

to make cache cleaning sort of isolated. Just for that module. Without any influence to some other.
And this debug: true will make all that things that now are made by NODE_ENV="development"
Is that possible?

#56 add pr

Looks like you have a slightly different name of the option in the pr :)
I don't mind to have a stronger option to control environment and I think its a good enhancement.
Sorry for the late call, I'll make the new version soon.

oops, my bad :)

I'll make the new version soon.

Wait for it. Good luck!

@yazonnile should be available for now. Check out 2.1.1

Great! Thx!


Enable app test on desktop browser - problem with AngularJs version

I'm developing a SPA and I would like to be able to test my app on my desktop browser. Even with the improvement Steroids brings to the table when it comes to upload, view and debug the app on a mobile device, it is faster still to do it on the desktop browser. I have seen that I can access the app in my desktop browser through http://localhost:4567/... but, the AngularJs version available there is not the one I set on my files. The angular I'm working with is 1.3.10 and the angular I'm getting from http://localhost:4567/ is - oddly - 1.2.27. As I'm using angular-route - and for that component the version available is the one I set (the same as the angular version) - the very basic ng-view directive does not work. Well it is a very strange issue, and it seems, at first, something easy to fix... On my mobile everyting works fine, since I'm getting the right version of angular there.

It might be faster to develop on the desktop browser, until you want to use the native features which are only available in the device (or simulator).
We used to have an experimental WebBridge which imitated eg. Tab Bar with a set of iframes. That didn't work in the end so we dropped support for that.
In case you have found a bug, please clarify your issue with the problem details and how it affects the project which is executed on the device / simulator. The current problem description is too vague.

PS You might have experienced this issue: https://github.com/AppGyver/steroids/issues/746 -- it's now fixed.


clib, apply: Add apply feature to clib

Implment apply operation at clib also refactor the clib integration tests using acutest header as test framework

@cathay4t CI is happy now, I was using an old rust version from fedora.


Correct POST url

Just 'searchTrashPages', doesn't do it. The correct URL is '/api/v3/searchTrashPages'.

@axyyu Is this still active?


Using namespace with ndb-orm

I need to setup multi tenancy using the namespace concept of the Cloud DataStore.
Inspecting the code, I'm not sure this is fully implemented within the current version of the library.
Can you help me understand what is missing to support that ? Thanks

It would be interesting to  add the below assertion into the test suite.
Assertion: Validate that the constraint of a namespace is properly enforced

Write an object with specified key "abc" using namespace "ns1"
Change namespace to "ns2"
Try to load object with key "abc" within namespace "ns2"

Should return none.

So far, from my test, looks like specifying and changing the namespace within the datastore.Client() object has no effect into validating the above assertion.

I have made some small fixes and added a test to show that namespaces basically work. Though I think the current implementation could be improved...
Have a look here:
https://github.com/berlincode/ndb-orm/blob/master/tests/tests_namespace.py
I hope this helps.


[7.x] Add missing imports.

Add missing imports.

The ones on the encrypt functions are for security.

See https://github.com/laravel/framework/pull/32276/commits/e9f23a399bc7234cab0e7fb5dc97ca6ef51b9334 Taylor


AttributeError: 'Tensor' object has no attribute 'shape'

Environment info
Operating System:  BashOn Windows
Installed version of CUDA and cuDNN:
(doesnt matter CPU version only)
If installed from binary pip package, provide:
0.9.0
If installed from sources, provide the commit hash:
Steps to reproduce
    def create_classifier(self):
        hiddenLayers = [self.num_points, self.num_points * 2, 10]
        self.classifier = tf.contrib.learn.DNNClassifier(hidden_units=hiddenLayers)

label is a string
point list is a list of an array of x, y values
ex:
[[1,2],[2,3],[3,4],...]

    def train(self, label, point_list):
        points = self.resample(point_list, self.num_points)
        utils.strip_ids_from_points(points)
        value_class = 1 if label == self.label else 0
        target = tf.reshape(tf.constant(value_class), [1])
        print 'training classifier to recognize value as: [' + str(value_class) + '] label is ' + label + ' class is ' + self.label
        point_tensor = tf.convert_to_tensor(points, dtype=tf.float32)
        reshaped_tensor = tf.reshape(point_tensor, [1, self.num_points * 2])
        print reshaped_tensor
        print target
        self.classifier.fit(x=reshaped_tensor, y=target, steps=1)

What have you tried?
googling why a tensor would not have a shape attribute
Logs or other output that would be helpful
Tensor("Reshape_1:0", shape=(1, 64), dtype=float32)
Tensor("Reshape:0", shape=(1,), dtype=int32)
Traceback (most recent call last):
  File "main.py", line 6, in <module>
    connection.start_socket(8089, callback=handler.message_processor)
  File "/mnt/d/workspace/SketchRecognitionWithTensorFlow/src/main/python/connection/python_socket_server.py", line 13, in start_socket
    process_message(connection, callback=callback)
  File "/mnt/d/workspace/SketchRecognitionWithTensorFlow/src/main/python/connection/python_socket_server.py", line 38, in process_message
    result = callback(general_proto)
  File "/mnt/d/workspace/SketchRecognitionWithTensorFlow/src/main/python/recognition/proto_handler.py", line 39, in message_processor
    return train_shape(general_proto.template)
  File "/mnt/d/workspace/SketchRecognitionWithTensorFlow/src/main/python/recognition/proto_handler.py", line 23, in train_shape
    rec.add_training_data(recognition_template.interpretation.label, recognition_template.shape)
  File "/mnt/d/workspace/SketchRecognitionWithTensorFlow/src/main/python/recognition/recognition_manager.py", line 98, in add_training_data
    self.recognizers[label].train(label, points)
  File "/mnt/d/workspace/SketchRecognitionWithTensorFlow/src/main/python/recognition/simple/recognizer.py", line 78, in train
    self.classifier.fit(x=reshaped_tensor, y=target, steps=1)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/learn/python/learn/estimators/estimator.py", line 173, in fit
    input_fn, feed_fn = _get_input_fn(x, y, batch_size)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/learn/python/learn/estimators/estimator.py", line 67, in _get_input_fn
    x, y, n_classes=None, batch_size=batch_size)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/learn/python/learn/io/data_feeder.py", line 117, in setup_train_data_feeder
    X, y, n_classes, batch_size, shuffle=shuffle, epochs=epochs)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/learn/python/learn/io/data_feeder.py", line 239, in __init__
    self.X.shape, None if self.y is None else self.y.shape, n_classes,
AttributeError: 'Tensor' object has no attribute 'shape'

Okay figured it out.  Fit can not take a tensor as an input.  (it would be helpful if that was the error message instead)

Actually there is a bug in data_feeder.py it should use get_shape() instead .shape.

I'm also having this issue. I'm using LinearClassifier. I tried passing the X argument as a tensor, Pandas dataframe, and NumPy matrix. None work and all attempts result in the same AttributeError.
Is there any progress with this? Thanks!

Have you tried at head? We know there's a bug in 0.9, but it should work at head.

Closing for now since @martinwicke says this is fixed.


[BUG] JsonConverterAttribute is ignored on polymorphic base class properties

Describe the bug
A class serialized with PolymorphicSerializeJsonConverter does not apply JsonConverterAttribute declared on instance properties during serialization.
Expected behavior
JsonConverterAttribute is applied during serialization whether or not the class is serialized using PolymorphicSerializeJsonConverter.
Actual behavior (include Exception or Stack Trace)
JsonConverterAttribute is only applied for properties of classes which don't use PolymorphicSerializeJsonConverter.
To Reproduce
using System;
using Microsoft.Rest.Serialization;
using Newtonsoft.Json;

[JsonObject("animal")]
class Animal
{
    [JsonConverter(typeof(DateJsonConverter))]
    [JsonProperty("birthday")]
    public DateTime Birthday { get; set; }
}

class Program
{
    static void Main()
    {
	var animal = new Animal
	{
	    Birthday = new DateTime(2020, 2, 29),
	};

	var serializeSettings = new JsonSerializerSettings();
	serializeSettings.Converters.Add(new PolymorphicSerializeJsonConverter<Animal>("dType"));
        Console.WriteLine(JsonConvert.SerializeObject(animal, Formatting.Indented, serializeSettings));
    }
}

produces
{
  "dType": "animal",
  "birthday": "2020-02-29T00:00:00"
}

(Note that birthday was not converted using DateJsonConverter.) If serializeSettings.Converters.Add is removed, it produces:
{
  "birthday": "2020-02-29"
}

(Note that birthday was converted using DateJsonConverter.)
Environment:

Name and version of the Library package used: Microsoft.Rest.ClientRuntime 3.0.3 with Newtonsoft.Json 12.0.3
Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): .NET Core SDK 3.1.300

Discussion:
The problem is that JsonConverterHelper.SerializeProperties doesn't consider the JsonProperty.PropertyConverter when serializing.
After a bit of poking around, I don't see an easy fix without copying a lot more logic from JsonSerializerInternalWriter.  I also suspect there may be a lot more differences in serialization behavior due to the differences with JsonSerializerInternalWriter.SerializeObject, not to mention potential future divergence as features are added to Json.NET.
An alternative approach would be to use a proxy JsonWriter which doesn't pass the opening WriteStartObject or closing WriteEndObject and removes the "properties." prefix from names.  A potential issue with this approach is that I don't see a foolproof way to recognize additional properties (from JsonExtensionDataAttribute) to avoid removing "properties.".  (I don't understand why this is done, so I'm not sure how much of an issue this is.)
Thoughts?

I don't see an easy fix without copying a lot more logic from JsonSerializerInternalWriter

Scratch that.  Using JsonProperty.Converter should be easy.  It won't fix the other potential current and future divergence from JsonSerializerInternalWriter, but it would fix this issue.  If that's sufficient, I can work up a PR (or I'd be happy to let someone else take it).

Fixed by #12943

Thanks to the kindness of @kevinoid, this comes with an associated PR (#12493).   Assigning this over to @pakrym for bookkeeping, as he's likely to be the final approval for the associated PR.
//cc: @AlexGhiondea


Add handling of tuples in type subscriptions

Fixes #162.
Initial implementation and tests added, and project lints fixed.
There are some significant questions to be resolved before merging. Prime among them is whether introducing nptyping as a test/dev dependency is a good idea.
Also, input on whether this implementation is sufficiently general, and whether additional/different test cases should be added/used would be good.

Prime among them is whether introducing nptyping as a test/dev dependency is a good idea.

I see it's a pure wheel so I'm ok with this.

Also, input on whether this implementation is sufficiently general, and whether additional/different test cases should be added/used would be good.

Can be a good starting place. We can add additional tests if users report bugs, no?

Prime among them is whether introducing nptyping as a test/dev dependency is a good idea.

I see it's a pure wheel so I'm ok with this.

The main thing I was thinking of is, currently my test cases depend on some internal type transformations that nptyping does. If nptyping changes these transformations, that will cause this project's test suite to fail. I realized: I can just change the test examples so that nptyping does not transform them. That should remove the brittleness, at least most of the way. I'll make this change.

Also, input on whether this implementation is sufficiently general, and whether additional/different test cases should be added/used would be good.

Can be a good starting place. We can add additional tests if users report bugs, no?

Yep. That's what I was thinking.

That should remove the brittleness, at least most of the way. I'll make this change.

Sounds good on this.

For my reference:

[ ] De-fold comment
[ ] Re-work iterable/non-iterable check
[ ] Fix typing problem
[ ] Rewrite tests to avoid nptyping brittleness

b279611 removes as much of the brittleness from the nptyping dependency as is possible with the current assert result == expected_result check.
If nptyping restructures/refactors their internals, these test cases will break.
It would be possible to reduce/eliminate this risk of breakage by loosening the assert, perhaps only for the nptyping cases; e.g.,:

if "nptyping" in result:
    # Looser check that matches e.g. re.search(expected_regex, result)
    # where expected_regex has things in it like r"~nptyping\..+\.NDArray"
else:
    assert result == expected_result

That would make the test function messy, though.
I guess another alternative would be to make a new test function for the nptyping cases, with the above selective-matching behavior.

TLDR; are you okay with accepting this possibility for breakage from nptyping for now, and we'll see what happens? Or, would you prefer to try to mitigate it now?

Please add a changelog with 1.16.0
https://github.com/tox-dev/sphinx-autodoc-typehints/blob/main/CHANGELOG.md

Done!


EL-1833 (part 2) add data_migration

Jira ticket
What changed and why
added a new gem to handle data_migrations.
This is our first data_migration and although we don't expect to have many of these, they have a way of sneaking up on you as the db is modified. So it makes sense to add this now as you cant retrospectively move migrations.
The migration runs on my machine ;)
I tested it on early_eligibility_selection does not exist, is gross and is continue_check
It will not do anything on UAT as the branch is new and will have no data. it will work on main UAT when it is merged. As such I have added 2 approval steps, one for STG and one for PROD. This way we can merge to main and then test each namespace before and after the migration.
The data_migration uses :with_data to do the data migrations after the migrations are run. I have added this where I think it needs to be, but this is the bit I am least confident about. So the pipeline will again be the test bed for this.
Guidance to review

Checklist
Before you ask people to review this PR:

Tests and rubocop should be passing
Branch is generally up to date with main Github - definitely no conflicts
No unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
PR description says what changed and why, with a link to the JIRA story.
Diff has been checked for unexpected changes being included.
Commit messages say why the change was made.

the rollback in this case would be to set the new field to null for all rows. we don't touch any of the other data in the table.


[Issue-2965] Update withdraw for Acala liquid staking

🚀 Deployed on https://pr-3168--sw-web-runner.netlify.app


Interface stops working after chunks unloaded in 1.10.2 (FTB Beyond 1.8.1)

Issue description:
Unloading chunks stops the interface from processing items; I have to break it and place it again for it to start working again.
What happens:
Interface works -> disconnect from server -> come back -> interface no work (does accept items, just doesn't process them).
Steps to reproduce:
no idea lol worked fine when i tried it in ssp
Version (make sure you are on the latest version before reporting):

Minecraft: 1.10.2
Forge: <IP_ADDRESS>7 for Minecraft 1.10.2
Refined Storage: 1.2.25

Does this issue occur on a server?
Yes.

#370

right, sorry


VTS L1 Enhancement - Header file 3.0.0 updates - Device Setting - FP

This task is to consider the latest header file updates and consider if there are any changes in L1 concerning the newest header files available at tag 3.0.0

The issue addressed in PR: https://github.com/rdkcentral/rdk-halif-test-device_settings/pull/92

all changes are now available in tag 3.1.0


缺少game.json/project.config.json的目录

It was intended for hiding the appid. No big changes made to that file so you can copy that directly from the sample game codes.


Running functional tests in container

This PR closes the following bug: 1804
NOTE THAT the PR is currently open in comparison to feature/pypi-publish and not master!
the following changes are suggested:

Running golang based  functional tests in a container. the main goal is to avoid having to run "dep ensure" on a local machine (or build agent). in CI this change saved ~4 minutes.

Adding a dockerfile to functional tests. this dockerfile runs "go test" so it need the entire dev env. output from the test is sent to a mounted volume where it can be read by the host machine.

Change name of folder tests to functional_tests to align with the way containers are built (name of folder = name of container).

In Makefile's functional tests, run all containers in parallel and wait only for analyzer (the biggest container). this saves time.

publish functional tests to ADO

/azp run


Document no prefix for create

/domain @samandmoore for testtrack v1.0 - we ready?
/domain @rnackman @joejansen for the doc fixes - does this work? I wanted to keep the parameter documentation tight, so i put existing in there to prompt doubt, and then put the full details in the --help documentation for both experiment and feature_flag creation commands.
fixes #37

/no-platform there's no code here. :)

<<domainlgtm
Works for me. I think 1.0 makes sense.

@aburgel notes that we don't have compatibility with the latest alpha of the rails client because there's no v2/split_registry endpoint in the fake. So I'm going to walk back calling this 1.0. We should have those in place by the end of the week and be good to go then.

<< domain lgtm -- one wording suggestion that you can take or leave for the parameter doc!

Y'know what, since @aburgel's planning on adding v2 endpoint support this week, I'm not even going to bump version or release this standalone. No need for the churn. We'll sweep this in with 1.0 when that is ready to go. Going to merge this. Thanks all!


support collector image

Coverage remained the same at 17.58% when pulling e5195e689e71f745060c7f0c09d25a080857e79e on ascrutae:zhangxin/feature/collector-image into dae5c6921a54953f37fe421668a790d66a4e816f on wu-sheng:master.

Coverage remained the same at 17.58% when pulling d50a9f2c29344c6ce452daf35b544dd438d63350 on ascrutae:zhangxin/feature/collector-image into dae5c6921a54953f37fe421668a790d66a4e816f on wu-sheng:master.


Update scalatest to 3.2.17

About this PR
📦 Updates org.scalatest:scalatest from 3.0.9 to 3.2.17
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

💡 Applied Scalafix Migrations

org.scalatest:scalatest:3.1.0 (created no change)

https://raw.githubusercontent.com/scalatest/autofix/e4de53fa40fac423bd64d165ff36bde38ce52388/3.1.x/rules/src/main/scala/org/scalatest/autofix/v3_1_x/RewriteDeprecatedNames.scala
Documentation: https://github.com/scalatest/autofix/blob/master/3.1.x/README.md

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalatest", artifactId = "scalatest" }
}]

labels: test-library-update, early-semver-minor, semver-spec-minor, scalafix-migrations, commit-count:1

Superseded by #443.


github actions compile far, far too much rust

customer:
performer:
deadline:
estimated:
started:
actual:
completed:
confirmed:
dependencies:

[ ]
supersedes:

Additionally, caches don't work properly. Github's fault but worth looking into.

Fixed by #1484


https://www.koroonakaart.ee/data.json is redirecting to the site

https://www.koroonakaart.ee/data.json is not serving the json file

Thanks for raising this issue. The URL you mentioned should be serving data.json correctly now. Do let us know if you notice anything else that isn't working as advertised.


Debugging is not working on MacOS Catalina

Using 'CMake Tools' from vector-of-bool
Expected Behavior:
Pause on breakpoint
Actual Behavior:
Ignores breakpoint
Note: lldb via command line works
launch.json
    "version": "2.0.0",
    "configurations": [
        {
            "name": "(lldb) Launch Program",
            "type": "cppdbg",
            "request": "launch",
            "program": "${command:cmake.launchTargetPath}",
            "args": [],
            "stopAtEntry": false,
            "cwd": "${workspaceFolder}/build",
            "targetArchitecture": "x64",
            "environment": [],
            "internalConsoleOptions": "openOnSessionStart",
            "externalConsole": false,
            "MIMode": "lldb"
        }
    ]
}

Same configuration worked on Mojave
VS Code Info
Version: 1.38.1
Commit: b37e54c98e1a74ba89e03073e5a3761284e3ffb0
Date: 2019-09-11T13:31:32.854Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 19.0.0

Please file against cppdbg extension https://github.com/microsoft/vscode-cpptools . Thank you


Cobertura reports

This PR implements cobertura reports compatible at least with the Jenkins cobertura plugin. It is based on work from #214.
I have verified that all the tests succeed merging either #204 or #201

Coverage increased (+1.3%) to 90.363% when pulling 8246be02fe4344a236eadc5270f001fc9f7b6cc9 on javiplx:cobertura_ready into 8c1913b2697ee4a60db65607967fbb73226c8bd6 on rodjek:master.


Arena stats being calculated incorrectly

cf. https://github.com/stevschmid/track-o-bot/issues/66

@stevschmid did you manage to reproduce the issue?

I experience a version of this bug where all averages are "0.0".

The "Runs" column is accurate, as well as the histogram in the bottom. I expected to see data in other columns, though.
This isn't a template issue, since the JSON representation of this endpoint also reports most numbers as "0":

```json
{
    "stats": {
        "as_hero": {
            "Druid": {
                "losses": 0,
                "runs": 6,
                "total": 0,
                "wins": 0
            },
            "Hunter": {
                "losses": 0,
                "total": 0,
                "wins": 0
            },
            "Mage": {
                "losses": 0,
                "runs": 17,
                "total": 0,
                "wins": 0
            },
            "Paladin": {
                "losses": 0,
                "runs": 12,
                "total": 0,
                "wins": 0
            },
            "Priest": {
                "losses": 0,
                "runs": 1,
                "total": 0,
                "wins": 0
            },
            "Rogue": {
                "losses": 0,
                "runs": 13,
                "total": 0,
                "wins": 0
            },
            "Shaman": {
                "losses": 0,
                "runs": 3,
                "total": 0,
                "wins": 0
            },
            "Warlock": {
                "losses": 0,
                "runs": 6,
                "total": 0,
                "wins": 0
            },
            "Warrior": {
                "losses": 0,
                "runs": 2,
                "total": 0,
                "wins": 0
            }
        },
        "count_by_wins": [
            2,
            8,
            9,
            8,
            5,
            5,
            13,
            3,
            3,
            0,
            0,
            1,
            3
        ],
        "overall": {
            "losses": 0,
            "runs": 60,
            "total": 0,
            "wins": 0
        }
    }
}
```

I couldn't reproduce locally in development. But, it's interesting that the numbers which are valid all come from user_arenas scope, while all numbers that are zero come from user_results.arena. I would presume that the user_results.arena scope is somehow busted in production mode, although looking at the code I can't imagine how.
The historical data about Arena runs is displayed correctly in the "History" and "Arena" tabs.

I was encountering the exact same bug as @mislav. Looking through the code, I noticed that the read_params action in the Stats module was pulling stuff from cookies that could have potentially messed with the user_results query. So I cleared my cookies just to be sure, and the bug went away! 👯
Unfortunately, I didn't check to see what was in my cookies before doing this. If I can get the bug to happen again I'll save that data to see if there is an easy way to catch it from the Stats module. But for now, clearing cookies seems to fix the problem.

Hot damn, @coleww. That totally did it! 🏆
I checked the cookies before 🔥ing them. There was the Google Analytics cookie (irrelevant, I suppose, the mode cookie set to "ranked", the time_range cookie set to last 3 days, and the main _webtracker_session cookie (encrypted).
I think the culprit was the mode cookie. Steps to break your Arena stats again:

Go to Stats > Arena. The data looks fine.
Go to Stats > Classes.
Choose "Ranked" from the modes drop-down.
Go to Stats > Arena. The data is now all messed up because of the mode=ranked cookie being persisted in the previous step.

To unbreak your cookie, however, just reset the mode with Stats > Classes: All Modes.

The 0.0 bug is fixed! Thanks for the help guys.

For posterity: 041c753f9c27c28d942865d90866fddbc05defaf


big cardboard box improvements

About the PR

makes big cardboard boxes always choose the person closing them as their controller
if closer is not in box, an entity inside is chosen as the controller
stealth boxes no longer cause the effect or the sound upon being opened
probably needs balance discussion as this is a rather considerable buff to stealth boxes

Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

tweak: Big cardboard boxes no longer choose their driver randomly
tweak: Stealth boxes are now quiet

made stealthbox no longer quiet but kept the functionality of making boxes quiet