feat: use uv if installed

What I did
add setuptools and pip to base requirements so that uv can install everything correctly.
fixes: #1999
fixes: #
How I did it
edited the setup.cfg
How to verify it

uv venv .venv -p 3.10
source .venv/bin/activate
uv pip install -e ../newape
uv pip install -e ../ape-alchemy
ape plugins list
Installed Plugins
alchemy    0.7.1.dev11+gad25ef2.d20240411
ape --version
0.7.14
ape networks list
ethereum  (default)
├── goerli
│   ├── alchemy
│   └── geth  (default)
├── local  (default)
│   ├── geth
│   └── test  (default)
├── mainnet
│   ├── alchemy
│   └── geth  (default)
└── sepolia
├── alchemy
└── geth  (default)
python ../testape/steth.py
alchemy through ape took 1.13 seconds for 1076 events (events per second: 953.32)

Checklist

[ ] Consider eliminating pip dependency in favor of pkg_resources
[ ] All changes are completed
[ ] New test cases have been added
[ ] Documentation has been updated

I think I made uv a fallback replacement for pip
saw some warnings along the way:
.venv/lib/python3.10/site-packages/eth/__init__.py:1
  /code/newape/.venv/lib/python3.10/site-packages/eth/__init__.py:1: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
    import pkg_resources

.venv/lib/python3.10/site-packages/_pytest/config/__init__.py:1373
  /code/newape/.venv/lib/python3.10/site-packages/_pytest/config/__init__.py:1373: PytestConfigWarning: Unknown config option: timeout

    self._warn_or_fail_if_strict(f"Unknown config option: {key}\n")

evm-trace has a capped dependency on py-evm versions which use pkg_resources. I remove it here: https://github.com/ApeWorX/evm-trace/pull/62

uncapping python-dateutil, eth-account, eth-utils, web3[tester], and eip712 points to the culprit:
uv pip install -e . --prerelease=allow
   Built file:///code/newape                                                                                Built 1 editable in 676ms
Updating https://github.com/wakamex/evm-trace.git (HEAD)
⠙ rich==13.7.1                                                                                × No solution found when resolving dependencies:
  ╰─▶ Because eip712>=0.2.3 depends on eth-account>=0.10.0,<0.11 and only the following versions of eip712 are
      available:
          eip712<=0.2.3
          eip712==0.2.4
          eip712==0.2.5
      we can conclude that eip712>=0.2.3 depends on eth-account>=0.10.0,<0.11.
      And because eth-ape==0.7.15.dev5+gdbe67d70.d20240415 depends on eth-account>=0.11.2, we can conclude that
      eip712>=0.2.3 and eth-ape==0.7.15.dev5+gdbe67d70.d20240415 are incompatible.
      And because eth-ape==0.7.15.dev5+gdbe67d70.d20240415 depends on eip712>=0.2.3 and you require

uv has really nice dependency errors :)

uncapping and bumping pandas to >=2 lets uv pick 2.2.2 instead of 1.5.3 (why that one? i dunno)
1.5.3 results in a hecking weird error:
ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject

got it installed with eth_account==0.11.2 by uncapping eth-account in ape and eip712. also ape plugins list doesn't error on missing pkg_resources.

Re-ran failed test case for Python 3.9
I'm okay with the move of the PluginManager but curious what @antazoey thinks

I like the change but am worried if it's breaking.

Re-ran failed test case for Python 3.9
I'm okay with the move of the PluginManager but curious what @antazoey thinks

I like the change but am worried if it's breaking.

It lifts PluginManager from ape.plugins (which tbh should have been private e.g. ape._plugins) to the ape.managers namespace, which is also still not typically widely used except for typing maybe
The expectation is that singletons from ape.managers end up in top level namespace, and also injected via ManagerAccessMixin

She may have been referring to it failing 1 test. It seemed really random. Only MacOS Python 3.9 failed. Looks like after that someone may have re-run it and it now passes.

rebased. tests pass. gonna do another commit to update dependencies from main.

(which tbh should have been private e.g. ape._plugins)

The registration function needs to be public for plugins: https://github.com/ApeWorX/ape-solidity/blob/main/ape_solidity/init.py#L1

looks like github runners only support darwin-arm64 down to python 3.10.11 according to the CI error
   Error: The version '3.8' with architecture 'arm64' was not found for macOS 14.4.1.
  The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json

looks like github runners only support darwin-arm64 down to python 3.10.11 according to the CI error
   Error: The version '3.8' with architecture 'arm64' was not found for macOS 14.4.1.
  The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json

Yes we are tracking to fix with #2020

awesome. let me know if this PR is missing anything. maybe we can revisit after #2020.

during testing I ran into an issue but fixed it here: https://github.com/ApeWorX/ape/pull/2021

issues: tests fail when uv is installed. it seems like we need to test that case more anyway.

issue: pkg_resources shows up on trie 2.2.0, which is "installable" in current conditions (ran into this). Lucky, I think we can bump it to 3.0 and it will still work.

[ ] bump peer dependency trie to >=3.0.0,<4/

just tested installation speeds between uv and pip, on latest 0.7.23 26bec8b75eb4d6b489c8585458697d97052f24e9:

tool
no cache
cached
uncached unpinned pandas

uv
2:09.43
1.411
5.202

pip
2:29.40
8.867
9.192

speedup (s)
19.97
7.456
3.99

speedup (%)
13.37%
84.07%
43%

no fucking way

also, big speedup comes from loosening the pandas pin, which requires building numpy on my machine (Fedora 40)

Yeah, we actually want to remove the pandas pin eventually, it's not quite state of the art and end users might have a couple of different options they may want to choose from


Close host on SF service stop

Stoping generic host when SF service is closing should speed up service shutdown and make services update more responsive.

Good point I'll close the PR


package.json is missing some dev dependencies

full deps should be as below:
"devDependencies": {
    "arrify": "*",
    "bluebird": "*",
    "blueimp-tmpl": "*",
    "colors": "^1.1.2",
    "copy-webpack-plugin": "^0.3.3",
    "css-loader": "^0.23.0",
    "enhanced-resolve": "0.9.1",
    "exports-loader": "0.6.2",
    "expose-loader": "^0.7.1",
    "file-loader": "^0.8.4",
    "findup-sync": "^0.3.0",
    "html-webpack-plugin": "^1.7.0",
    "http-server": "^0.8.5",
    "imports-loader": "^0.6.4",
    "inflight": "^1.0.4",
    "inherits": "^2.0.1",
    "istanbul-instrumenter-loader": "^0.1.3",
    "json-loader": "^0.5.3",
    "json5": "^0.4.0",
    "karma": "^0.13.15",
    "karma-chrome-launcher": "^0.2.1",
    "karma-coverage": "^0.5.3",
    "karma-jasmine": "^0.3.6",
    "karma-phantomjs-launcher": "^0.2.1",
    "karma-sourcemap-loader": "^0.3.6",
    "karma-webpack": "1.7.0",
    "loader-utils": "*",
    "lodash": "3.10.1",
    "minimatch": "*",
    "node-dir": "*",
    "object-assign": "*",
    "once": "^1.3.3",
    "path-is-absolute": "^1.0.0",
    "phantomjs": "^1.9.18",
    "phantomjs-polyfill": "0.0.1",
    "protractor": "^3.0.0",
    "raw-loader": "0.5.1",
    "reflect-metadata": "0.1.2",
    "remap-istanbul": "^0.5.1",
    "rimraf": "^2.4.4",
    "semver": "*",
    "style-loader": "^0.13.0",
    "ts-helper": "0.0.1",
    "ts-loader": "^0.7.2",
    "tsconfig-lint": "^0.4.3",
    "tslint": "^3.2.0",
    "tslint-loader": "^2.1.0",
    "typedoc": "^0.3.12",
    "typescript": "^1.7.3",
    "typings": "^0.6.1",
    "underscore": "^1.8.3",
    "underscore.string": "^3.2.2",
    "url-loader": "^0.5.6",
    "webpack": "^1.12.9",
    "webpack-dev-server": "^1.12.1",
    "webpack-md5-hash": "0.0.4"
  },

can you make a pull-request

PR created: patched with full dev deps #228

apistack is another accout of<EMAIL_ADDRESS>

@ApiStack so did you run into an error without these are were these mentioned as hidden modules or something?

@gdi2290
Just tested under OSX, the webpack runs without any error. But don't know why it fails on windows.

it could also be the version of node/npm

@gdi2290, the vendor bundle is too big for use, any idea to make it succinct?
compiled against webpack.prod.config.js with ENV=production
Bruce@Bruces-MacBook ~/w/a/angular2-webpack-starter> ls -ltrh dist/vendor*.js
-rw-r--r--  1 Bruce  staff   1.1M Jan 15 10:52 dist/vendor.a3669eee36a1d0c22dbc.bundle.js

The Angular team is working on better ways to lower the bundle size. For example, the compiler could be removed from the bundle as well Rx modules that aren't used. Because the framework is still in beta the problem was pushed back until now so I'm sure every new release will be improving the bundle size.


Could not find the drag and drop manager

I've created a basic DnD setup with a table and rows (MyRow) that should be draggable (for re-ordering). I'm getting this error message when rendering my top-level component (Sandbox):

Invariant Violation: Could not find the drag and drop manager in the context of MyRow. Make sure to wrap the top-level component of your app with DragDropContext.

I've decorated Sandbox with DragDropContext for the module export and feel pretty sure I'm using the API correctly. Am I using it wrong or could there be some other problem?
[package.json]
...
"react": "^0.13.3",
"react-dnd": "^1.1.3"
[Sandbox.jsx]
var React = require('react');
var ReactDnD = require('react-dnd');
var HTML5Backend = require('react-dnd/modules/backends/HTML5');

/**
 * Implements the drag source contract.
 */
var cardSource = {
    beginDrag: function (props) {
        return {
            text: props.customText
        };
    }
};

/**
 * Specifies the props to inject into your component.
 */
function collect(connect, monitor) {
    return {
        connectDragSource: connect.dragSource(),
        isDragging: monitor.isDragging()
    };
}

var MyRow = React.createClass({
    render: function () {
        return this.props.connectDragSource(

                {this.props.children}

        );
    }
});

var MyDragRow = ReactDnD.DragSource("MyDragRow", cardSource, collect)(MyRow);

var Sandbox = React.createClass({
    render: function () {
        return (

                <MyDragRow customText="row 1">
                    hello
                    world
                </MyDragRow>
                <MyDragRow customText="row 2">
                    hello
                    world
                </MyDragRow>

        );
    }
});

module.exports = ReactDnD.DragDropContext(HTML5Backend)(Sandbox);

Can you check if you have two copies of React in node_modules by chance? This sometimes causes that problem.

I didn't find another copy of React in node_modules. I also tried removing node_modules and npm install from scratch, same error.

PS C:\Projects\MyProject> npm list react
...
└──<EMAIL_ADDRESS>

Can you prepare a reproducible sample project?

I've created a sample project which doesn't reproduce the issue (although the React-code is the same). I suppose my build system could be causing trouble (browserify)?

The problem turned out to be multiple React imports after all. We are loading React from a CDN so loading it from NPM as well (bundled via browserify) caused problems. We fixed it by loading React-DnD from a CDN as well. Thanks for your help.

:+1: Thanks for getting in touch and telling what the issue was!


Variable name is a shadow variable

Rename name to name_ like you do on;
ERC20Upgradeable.sol#L55

Hello @eugenioclrc
The contracts in this repo are transpiled (automatically translated) from the non-upgradeable version in openzeppelin/openzeppelin
In particular, the initializer parameters (in the upgradeable version) are a copy of the constructor parameters (in the non upgradeable version). That is were the change should happen


fetch passed to load function in +page.server.js implements CORS

Describe the bug
Even though it will only ever run on the server, the fetch implementation that is passed to load in +server.page.js is checking for CORS, behaving as if it were called in a browser.
I assumed this might be an oversight from when page.server routed were introduced, since obviously you'd very much want this behavior in non-server page.js load function, but it doesn't really make any sense in the new environment.
I hope I didn't overlook an issue where this was discussed already and kept for technical reasons, but even then we'd probably want this documented.
Reproduction

Logs
No response
System Info
-

Severity
annoyance
Additional Information
No response

Some discussion here for additional context: https://discord.com/channels/457912077277855764/1035096174014771231/1035096174014771231


In case of Testing Farm infra failure show pipeline.log

In case of Testing Farm infra failure, we have to show pipeline.log

Fixed by #47


Unable to run Tekton pipelines locally since move away from InitContainers

For full context see https://knative.slack.com/archives/CDCQ72D0R/p1551956671118100
Caveat: we are doing this locally and our pipeline involves resources. We're creating the PipelineRun and the resources through Go code - something we plan to contribute as an example, based on receiving a webhook from a repository. I don't know if this is a problem with our own code or with Knative itself, just that since the move away from InitContainers we have the problem. Am I missing something?
Expected Behavior
Follow the docs for local development here and you should be able to create PipelineRuns that run successfully locally, using images from your local Docker registry. Pipelines and all associated tasks should run perfectly.
Actual Behavior
PipelineRuns fail citing tasks are not found:
adams-mbp:build-pipeline aroberts$ k get pipelinerun -o json
{
    "apiVersion": "v1",
    "items": [
        {
            "apiVersion": "tekton.dev/v1alpha1",
            "kind": "PipelineRun",
            "metadata": {
                "creationTimestamp": "2019-03-07T10:56:32Z",
                "generation": 1,
                "labels": {
                    "app": "devops-knative"
                },
                "name": "devops-pipeline-run-1551956192",
                "namespace": "default",
                "resourceVersion": "215773",
                "selfLink": "/apis/tekton.dev/v1alpha1/namespaces/default/pipelineruns/devops-pipeline-run-1551956192",
                "uid": "ab1967c6-40c7-11e9-9495-025000000001"
            },
            "spec": {
                "Status": "",
                "params": null,
                "pipelineRef": {
                    "name": "simple-pipeline"
                },
                "resources": [
                    {
                        "name": "docker-image",
                        "resourceRef": {
                            "name": "docker-image-1551956192"
                        }
                    },
                    {
                        "name": "git-source",
                        "resourceRef": {
                            "name": "git-source-1551956192"
                        }
                    }
                ],
                "serviceAccount": "default",
                "timeout": "1h0m0s",
                "trigger": {
                    "type": "manual"
                }
            },
            "status": {
                "conditions": [
                    {
                        "lastTransitionTime": "2019-03-07T10:56:32Z",
                        "message": "TaskRun devops-pipeline-run-1551956192-build-simple-6wlst has failed",
                        "reason": "Failed",
                        "status": "False",
                        "type": "Succeeded"
                    }
                ],
                "startTime": "2019-03-07T10:56:32Z",
                "taskRuns": {
                    "devops-pipeline-run-1551956192-build-simple-6wlst": {
                        "pipelineTaskName": "build-simple",
                        "status": {
                            "conditions": [
                                {
                                    "lastTransitionTime": "2019-03-07T10:56:32Z",
                                    "message": "References a Task default/build-push that doesn't exist:  couldn't create redirected Build: failed to add entrypoint to steps of TaskRun devops-pipeline-run-1551956192-build-simple-6wlst: failed to fetch remote image localhost:5000/knative/git-init-afd2a379df7ac007f1e3a5fc75688a50@sha256:6bf4f67a86fa3e8fc9066835231b853bda76df92fd76b06e72227b7a1c23d39e: couldn't get container image info from registry localhost:5000/knative/git-init-afd2a379df7ac007f1e3a5fc75688a50@sha256:6bf4f67a86fa3e8fc9066835231b853bda76df92fd76b06e72227b7a1c23d39e: Get http://localhost:5000/v2/: dial tcp <IP_ADDRESS>:5000: connect: connection refused",
                                    "reason": "CouldntGetTask",
                                    "status": "False",
                                    "type": "Succeeded"
                                }
                            ],
                            "podName": "",
                            "startTime": "2019-03-07T10:56:32Z"
                        }
                    },
                    "devops-pipeline-run-1551956192-deploy-simple-9t7n4": {
                        "pipelineTaskName": "deploy-simple",
                        "status": {
                            "conditions": [
                                {
                                    "lastTransitionTime": "2019-03-07T10:56:32Z",
                                    "message": "References a Task default/deploy-simple-kubectl-task that doesn't exist:  couldn't create redirected Build: failed to add entrypoint to steps of TaskRun devops-pipeline-run-1551956192-deploy-simple-9t7n4: failed to fetch remote image localhost:5000/knative/git-init-afd2a379df7ac007f1e3a5fc75688a50@sha256:6bf4f67a86fa3e8fc9066835231b853bda76df92fd76b06e72227b7a1c23d39e: couldn't get container image info from registrylocalhost:5000/knative/git-init-afd2a379df7ac007f1e3a5fc75688a50@sha256:6bf4f67a86fa3e8fc9066835231b853bda76df92fd76b06e72227b7a1c23d39e: Get http://localhost:5000/v2/: dial tcp <IP_ADDRESS>:5000: connect: connection refused",
                                    "reason": "CouldntGetTask",
                                    "status": "False",
                                    "type": "Succeeded"
                                }
                            ],
                            "podName": "",
                            "startTime": "2019-03-07T10:56:32Z"
                        }
                    }
                }
            }
        }
    ],

Tasks exist in the Kube sense but not in the images sense (If I do kubectl get tasks, I do see my tasks).
Steps to Reproduce the Problem

Follow docs here so that knative is installed locally https://github.com/knative/build-pipeline/blob/master/docs/tutorial.md#local-development. Follow any example to create a PipelineRun with tasks.

Todo: I'm gonna add the noddiest reproduce with tiny tasks and a tiny PipelineRun.
Additional Info
If you git checkout any commit prior to c0285b30e9720ea4f1a0666c97db424362b411b5, there are no problems. The PipelineRun progresses to completion.
I believe the tasks should now be containers/images that are pushed to the local registry and we should be able to pull from them. I think the images do exist but they can't be pulled.
I've never had to use pull secrets locally and we're using the default service account (there wouldn't be any credentials anyway for my insecure lil registry).
We have a couple theories involving changes in entrypoint.go regarding authorization and another involving the use of ko.
Hopefully we just need to add to the docs again or it's a minor config issue on my end.
@abayer @pivotal-nader-ziada FYI
Here are the task definitions:
build-task.yaml:
apiVersion: tekton.dev/v1alpha1
kind: Task
metadata:
  name: build-push
spec:
  inputs:
    resources:
      - name: git-source
        type: git
    params:
    - name: pathToDockerFile
      description: The path to the dockerfile to build
      default: /workspace/git-source/Dockerfile
    - name: pathToContext
      description: The build context used by Kaniko (https://github.com/GoogleContainerTools/kaniko#kaniko-build-contexts)
      default: /workspace/git-source
  outputs:
    resources:
      - name: builtImage
        type: image
  steps:
  - name: build
    image: docker
    command:
    - docker
    args:
    - 'build'
    - '-f'
    - ${inputs.params.pathToDockerFile}
    - '-t'
    - ${outputs.resources.builtImage.url}
    - ${inputs.params.pathToContext}
    volumeMounts:
    - name: docker-socket
      mountPath: /var/run/docker.sock
  - name: push
    image: docker
    command:
    - docker
    args:
    - 'push'
    - ${outputs.resources.builtImage.url}
    volumeMounts:
    - name: docker-socket
      mountPath: /var/run/docker.sock
  volumes:
    - name: docker-socket
      hostPath:
        path: /var/run/docker.sock
        type: Socket

deploy-task.yaml:
apiVersion: tekton.dev/v1alpha1
kind: Task
metadata:
  name: deploy-simple-kubectl-task
spec:
  inputs:
    resources:
    - name: git-source
      type: git
    - name: image-out
      type: image
  steps:
  - name: modify-yaml
    image: ubuntu
    command: ['/bin/bash']
    args: ['-c', 'find /workspace/git-source/config -type f -exec sed -i -e s!"image: PIPELINE_REPLACE:latest"!"image: ${IMG}"!g {} \;']
    env:
      - name: IMG
        value: ${inputs.resources.image-out.url}
  - name: install-new
    image: lachlanevenson/k8s-kubectl
    command: ['kubectl']
    args:
    - 'apply'
    - '-f'
    - '/workspace/git-source/config'

(we replace the needle here with the commit ID so you can build and push your latest code)
pipeline.yaml:
apiVersion: tekton.dev/v1alpha1
kind: Pipeline
metadata:
  name: simple-pipeline
spec:
  resources:
  - name: git-source
    type: git
  - name: docker-image
    type: image
  tasks:
  - name: build-simple
    taskRef:
      name: build-push
    resources:
      inputs:
      - name: git-source
        resource: git-source
      outputs:
      - name: builtImage
        resource: docker-image
  - name: deploy-simple
    #runAfter: [build-simple]
    taskRef:
      name: deploy-simple-kubectl-task
    resources:
      inputs:
      - name: git-source
        resource: git-source
      - name: image-out
        resource: docker-image

Whoops, looks like a bug for sure, sorry for the hassle!! We'll get on this right away
btw awesome issue write up @a-roberts thanks so much :pray:

Blech, my internet connection is terrible and I've never actually used Docker for Mac in a meaningful way, so I don't think I can get this reproduced locally. If someone else can tackle it, that'd probably be for the best.

/assign

To complete a bit the bug decription, it's also the case on minikube with a simple case like that (because of git-init containers that do no specify command)
apiVersion: tekton.dev/v1alpha1
kind: PipelineResource
metadata:
  name: skaffold-git
spec:
  type: git
  params:
  - name: revision
    value: master
  - name: url
    value: https://github.com/GoogleContainerTools/skaffold
---
#Builds an image via kaniko and pushes it to registry.
apiVersion: tekton.dev/v1alpha1
kind: Task
metadata:
  name: build-simple
spec:
  inputs:
    resources:
    - name: workspace
      type: git
    params:
    - name: pathToDockerFile
      description: The path to the dockerfile to build
      default: /workspace/workspace/Dockerfile
    - name: pathToContext
      description: The build context used by Kaniko (https://github.com/GoogleContainerTools/kaniko#kaniko-build-contexts)
      default: /workspace/workspace
  steps:
  - name: build-simple
    image: docker.io/library/busybox
    command:
    - /bin/sh
    args:
    - -c
    - "ls -l ${pathToDockerFile} ${pathToContext}"
---
apiVersion: tekton.dev/v1alpha1
kind: TaskRun
metadata:
  name: build-simple
spec:
  taskRef:
    name: build-simple
  trigger:
    type: manual
  inputs:
    resources:
    - name: workspace
      resourceRef:
        name: skaffold-git
    params:
    - name: pathToDockerFile
      value: Dockerfile
    - name: pathToContext
      value: /workspace/workspace/examples/microservices/leeroy-web

Thinking outloud of possible fixes and workaround :

As we do remote lookup only when the command is not specified, we can, for internal containers (copy, git-init, creds-init, …) provide command and thus make it work. This is the easiest mitigation step.
For actually steps provided by the user, we may try to handle some edge/special cases, like ko.local or localhost:* remote parts, where we should be able to look directly into the cri-* image store (using go-containerregistry. That said, it means we need to add support for those in go-containerregistry and we're gonna need to get access to those cri-* implementation from the controller… it feels like a lot to do… (and as soon as a new cri-* implementation pops up we may need to add support for it in go-containerregistry)

I'm gonna go ahead and fix 1., but we're gonna need to discuss if 2. is worth the work or if we should just document that images in steps have to reference to registries that are accessible from the cluster (docker.io, quay.io,gcr.io, …, ip that containers from the cluster can access to, …)


Prototype doNotCacheConfigurationIf

@bot-gradle test ACC

OK, I've already triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build


test(cors) check that it works with 404 responses

Checks that CORS properly works with 404 responses.
Created to check https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/konglayer/FMXgLOFaHcQ/DIYh0Fr_CQAJ

This is ready

Just want to have the tests run (rebasing on next for that)


Include ".Generated" in the file names?

As these are partials and like to be added to, it would make sense to include ".generated" in the file name so that the custom additions to the partial class can have the "core" class name. For example, MyClass.Generated.cs".
Since I can see this being something that not everyone wants, maybe this could be exposed as an option flag?

It makes sense to me. So far, we've been recommending naming the additional partial classes ***Partial.cs. What you're proposing is much better.
To maintain backwards compatibility it should be definitely exposed as a flag which would be turned off by default.
I'd also name it in a generic way "--transformfilenames" (or similar) with a default transformation being the ".Generated" suffix.
We could introduce another option for adjusting the transformation if the default suffix wouldn't suffice.

I don't disagree with backwards compatibility, but this is getting more and more complicated to use with a ton of extra flags to add.
This is obviously a topic for another issue, but I'm wondering if it would make sense to allow all these flags to be set via a config of some kind in order to allow people to more easily save the options they want. I've opened a new issue with this suggestion (#22).

agreed

Further to this, if you're going to generate a *.Generated.cs then you should generate the empty *.cs partial class to go with it if one doesn't already exist.

I've added a pull-request to address the main request here.  My comment above could be considered an enhancement later if required.

thanks @hades200082 ! it's merged now


Retrieve a Feature Flag   allow Update Value

Hi , Is there a plan to add UpdateFeatureFlagConfiguration?
I am hoping to update users programmatically in featureflag using targeting?
perhaps overload ongetfeatureflagconfiguration that takes Value string
All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:
  `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

Can you, please open an issue with details of your scenario at https://github.com/Azure/azure-sdk-for-net/issues/new?assignees=&labels=&template=question.md&title=[QUERY]
Closing the pull request for now.


People can access any vendor anywhere

To clarify: if someone successes a vendor and then walks away, the "Vendor" tab or "Shuttle Console" tab or whatever will still stick in the top right no matter where you are, and in-turn stacks to the side of any previously accessed items. Trying to dispense anything from a far distance will get rid of the tab and respective UI, but the cluttered bug is still a bit of a headache.
Steps:
1.) Access a vendor/console/autolathe/anything that puts up a drop-down UI in the top right.
2.) Walk away.
3.) See results.
Examples:

No there. Open issue on unitystation/unitystation


Add errorSource prop to errors propagated through EventEmitterWithErrorHandling

Fixes #7763
Note that there will be ongoing follow-up work to instrument more and more errors with this property.
For now, not making changes to IFluidErrorBase and normalizeError, but rather instrumenting via props. First write wins if an error is annotated (via normalizeError) twice. Still want to think about how to properly model this on our errors, but don't want to block on it.

@vladsud - anything else before I merge?

Upon some discussion offline with @anthony-murphy and @vladsud, it's not clear that this is the best first step in this direction.  Closing for now.


Fix empty trailing lines in extra_params

Tested with: https://ci.suse.de/blue/organizations/jenkins/cloud-crowbar9-job-upgrade-x86_64/detail/cloud-crowbar9-job-upgrade-x86_64/152/pipeline/


Implement migrator that populates replaces field on workflow_chain_set documents

This migrator is still in early development. At this point, it is only a "skeleton" of the final migrator. The associated schema changes are under discussion/construction in https://github.com/microbiomedata/berkeley-schema-fy24/pull/193/.

I don't think this migrator is necessary anymore (at least for now). See: https://github.com/microbiomedata/nmdc-schema/issues/2063

@eecavanna  agree, please close the PR and delete the branch w/o a merge.


SocketTimeoutException while fetching test plans via xray plugin

When trying to fetch a test plan with the Xray Plug-In I get a 'java.net.SocketTimeoutException'.

Please, try to use a higher timeout before you start to fetch a testplan.
You can use an argument with -DARGUMENT_NAME .
`Optional Information

com.atlassian.httpclient.options.connectionTimeout = connectionTimeout in seconds, Default is 5
com.atlassian.httpclient.options.socketTimeout = socketTimeout in seconds, Default is 20
com.atlassian.httpclient.options.requestTimeout = requestTimeout in seconds, Default is 30


Add Event Section

Added an "Events" section that makes a component for listing out past and future events for CFD

@natesabrown Looks great! It just might be a little disorienting for the images to shrink so much on hover. Do you think we should make it a bit less drastic? Thanks.

@natesabrown Looks great! It just might be a little disorienting for the images to shrink so much on hover. Do you think we should make it a bit less drastic? Thanks.
Edit: another option would be to make the images grow larger on hover.

Yeah, I made them shrink so that if the user wants to see stuff that is hidden by the graphic they could have the option. I'll change the degree of shrinkage and if that's still disorienting we can switch to another approach

What graphics are you referring to? I'm not sure I understand what's getting hidden.

The text of some of the images being hidden upon browser resize (as can be seen in the gif above). I thought a fixed-height image would be a better sacrifice than making the height variable and leaving empty space in the card, so I wanted the users to be able to size the image down on hover so they could intuitively see the full image without too much of a hassle.

Oh I see. Is there any way to just make the card height automatically match the content within it? That way there would be no empty space and it'd be responsive too.

To make the card height automatically match the content would change the current design aesthetic from fixed-height cards to variable-height cards, if I’m understanding what you’re suggesting. Personally, I feel like that adds more mental overhead/cognitive load to the user, as it increases the unpredictability of the element (see Google Keep layout vs. Google Docs document preview). Given that images have a large variability in height, that would almost definitely leave an overhang at the end of the grid when there are more than 1 items per row. I attached a drawing meant to illustrate what I’m talking about.
A possible solution for this is to add variable height cards but make a fixed-height background (extending past the width of the sub-container, similar to the “We are code for dallas” introduction component), which would imply containerization but allow for variable height cards.
I prefer the fixed-height cards with media-queries/size decrease/increase to account for the images because I think that design is more mature. Obviously this comes down to personal preference, and a website should not be torn in two between two aesthetic preferences, so I would appreciate a decision between the three options (fixed-height variable images, variable-height according to images, or variable-height with shaded background) and I’ll implement it.
On Jun 8, 2020, 4:38 PM -0500, Anthony Zhou<EMAIL_ADDRESS>wrote:

Oh I see. Is there any way to just make the card height automatically match the content within it? That way there would be no empty space and it'd be responsive too.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

To make the card height automatically match the content would change the current design aesthetic from fixed-height cards to variable-height cards, if I’m understanding what you’re suggesting. Personally, I feel like that adds more mental overhead/cognitive load to the user, as it increases the unpredictability of the element (see Google Keep layout vs. Google Docs document preview). Given that images have a large variability in height, that would almost definitely leave an overhang at the end of the grid when there are more than 1 items per row. I attached a drawing meant to illustrate what I’m talking about. A possible solution for this is to add variable height cards but make a fixed-height background (extending past the width of the sub-container, similar to the “We are code for dallas” introduction component), which would imply containerization but allow for variable height cards. I prefer the fixed-height cards with media-queries/size decrease/increase to account for the images because I think that design is more mature. Obviously this comes down to personal preference, and a website should not be torn in two between two aesthetic preferences, so I would appreciate a decision between the three options (fixed-height variable images, variable-height according to images, or variable-height with shaded background) and I’ll implement it.
…
On Jun 8, 2020, 4:38 PM -0500, Anthony Zhou @.***>, wrote: Oh I see. Is there any way to just make the card height automatically match the content within it? That way there would be no empty space and it'd be responsive too. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks so much for the thorough explanation. What you're saying makes a lot of sense. I agree we should use fixed-height cards, but I wonder if we could just make the cards fixed-dimensions in general. Then at a certain width they would switch from side-by-side to one on top of the other. What do you think of doing that?

Sure. So does side-by-side mean a carousel? And I’m also assuming that the cards scroll from side-to-side (in a carousel) when the device is small, and transform into the traditional grid view when the device is larger, to take advantage of the increased capacity of the computer screen. I think the breakpoint could be phones/small tablets have the carousel and large tablets/PCs have the grid view. If I’m not correctly understanding you, please let me know.
I’m assuming you are envisioning a carousel because the grid nature of the component already enables it to switch from “side by side” in a sense to directly on top of each other.
On Jun 8, 2020, 5:57 PM -0500, Anthony Zhou<EMAIL_ADDRESS>wrote:

Thanks so much for the thorough explanation. What you're saying makes a lot of sense. I agree we should use fixed-height cards, but I wonder if we could just make the cards fixed-dimensions in general. Then at a certain width they would switch from side-by-side to one on top of the other. What do you think of doing that?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

Wait actually I see what you're saying. Just make a well-defined component size and use the grid to change the way they stack while maintaining the same dimensions. That way we can maintain the image consistently and parts of it don't get cut off.


Please build for mro-base>=3.5

It would be great to have a version compatible with the latest mro-base=3.5.1.
In particular r-rjava is a dependency of rstudio so this currently prevents running rstudio with an R 3.5 environment.

On the advice of mingwandroid I've moved to the non-mro R builds


Please freeze the code (GPUFIT and CPUFIT)

so that I can continue making the final performance evaluations

I think the branching mechanism is perfectly suited for that. I created a branch called "publication" for this purpose. It will not get any code changes anymore but only documentation changes and maybe code to produce binaries. Please use this branch!
https://github.com/gpufit/GPUfit/tree/publication
Please all note that we continue working on the master branch and suitable commits and then applied also on the publication branch. This requires that we appropriately separate code changes from other changes in the commits. You'll have to be a bit more careful how you commit.

Bjorn should do this after his final commits are made

waiting for Bjorn and Adrian on this.

I also need to change a small thing in the Python binding.

I deleted the unused new branch. It should only be created at the moment of the code freeze. I updated python bindings and tests. Now I will only update documentation.

See branch https://github.com/gpufit/GPUfit/tree/publication

So much for the code freeze. We changed the code at least two times quite a lot. That's why I will delete the publication branch (it's useless) and tag the master branch upon submission instead.


⚠ Bofrost.at has degraded performance

In b9f9a32, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 9337 ms

Resolved: Bofrost.at performance has improved in 1a7564a after 12 minutes.


feature Decouple rowset id generator and local rowsets gc implementation

Proposed changes
Decouple rowset id generator and local rowsets garbage collection implementation. Instead, use pending rowset to implement local rowsets gc. Pending rowsets refer to those rowsets that are under construction, and have not been added to the tablet. BE storage engine will skip these pending rowsets during garbage collection.
Developers must create PendingRowsetGuard before writing first row data to a local rowset, and hold this PendingRowsetGuard during rowset construction before adding the rowset to tablet.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall


[ENH] Adds cluster submodule

With some fun new functions for working with different clustering partitions!
Also includes some light refactoring of nntools.modularity to use the new find_consensus() function.
To do:

[ ] Finish writing tests for match_assignments(), reorder_assignments(), and find_consensus()
[ ] Add some examples! These are functions that really need context to showcase their utility, so adding some Sphinx gallery-type example docs would be awesome

Codecov Report

Merging #30 into master will increase coverage by 1.31%.
The diff coverage is 58.25%.

@@            Coverage Diff             @@
##           master      #30      +/-   ##
==========================================
+ Coverage   49.77%   51.08%   +1.31%
==========================================
  Files          17       19       +2
  Lines         870      965      +95
==========================================
+ Hits          433      493      +60
- Misses        437      472      +35

Impacted Files
Coverage Δ

netneurotools/modularity.py
64.04% <25%> (+3.82%)
:arrow_up:

netneurotools/cluster.py
56.32% <56.32%> (ø)

netneurotools/tests/test_cluster.py
83.33% <83.33%> (ø)

Continue to review full report at Codecov.

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


release v1.0.0

@JuliaRegistrator register
Release notes:

change source tree structure
change some APIs

for example, param["Lattice"] is a String, not a Function

generalize how to definite lattice
added some lattice
added some models

Registration pull request created: JuliaRegistries/General/4703
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 7730b020d03c6873745f9688cc5062e8bc61e25c
git push origin v1.0.0

@JuliaRegistrator register
Release notes:

change source tree structure
change some APIs

for example, param["Lattice"] is a String, not a Function

generalize how to definite lattice
added some lattice
added some models

Registration pull request updated: JuliaRegistries/General/4703
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 297e9c00aff1a9d4ac3a3bb207141a0f05fcc5da
git push origin v1.0.0

v1.0.0 released and registered into General registry.


Added conditions

Codecov Report

Merging #8 (4a7c807) into main (4123aa7) will increase coverage by 0.13%.
The diff coverage is 100.00%.

:exclamation: Current head 4a7c807 differs from pull request most recent head 0e3c8c6. Consider uploading reports for the commit 0e3c8c6 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main       #8      +/-   ##
==========================================
+ Coverage   90.71%   90.84%   +0.13%
==========================================
  Files          18       18
  Lines         883      896      +13
==========================================
+ Hits          801      814      +13
  Misses         56       56
  Partials       26       26

Impacted Files
Coverage Δ

condition.go
100.00% <100.00%> (ø)

curweather.go
92.90% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Collect all Location Maps Overlay

Relates to issue #21
The refinement of the UI will lead to a new method of viewing Pokemon Locations, which includes overlays to a base map of the region in order to increase efficiency. This task is, therefore, two-fold:

Collect all of the Location Highlighted Maps from a source such as Bulbapedia
Use image processing to extract the Difference/XOR to obtain an overlay

By conducting a special search on the Bulbapedia Archive Wiki, I've managed to wrangle most of the Image Maps in the URL below
http://archives.bulbagarden.net/w/index.php?title=Special:Search&limit=500&offset=0&profile=images&search=*Map.png
So it seems this is easily scrape-able and we can extract the assets from here to then do Image Processing on them.

This issue supersedes/replaces issue #4


Skip tests

Testing public build - skip tests as it seems to fail on resolving dependencies...
Checklist

[ ] Documentation (if applicable)
[ ] Changelog

/sem-approve


document blame & history

Representing the contents of a file as an event log allows conflict resolution to happen in a nicer way.
This could be a breaking change and we would need infrastructure in place for modeling versions

Must have: @steverusso
Nice to have: @mahakanakala


Uncaught errors when trying to edit other users as a maintainer

Tried to solve it but a bit lost at the new directories. Problem lies at EditUser.js line 13, user is undefined when maintainer is editing.


remove releasability

@rhuss what's the reason for removing this file -- is it because we're not part of the official release train?

Yes, it adds some noise to the release channel and had been excluded by the knobot configuration already, but it seems like that an existing file still needs to be removed manually
When you decide to join the usual Knative release cadence, it would be enabled again.

Cool, thanks for clarifying!
/lgtm
/approve


Is there any early adopter program / community for Coco Framework?

I would love to join if any.

Count me in as well.

I think everybody would love to :P

I'd love to join

ditto

Weird, @triconic  i haven't heard anything from MS , no mention at all at Build
unless I had missed it.

@jeveloper you didn't - it was nothing at Build about Coco Framework.
So I am wondering when we will be able to string #BUIDL-ing using Coco Framework :)

Ahh
@dmitry-pavlov  Spasibo :)

I think we can assume - for near-term purposes - that it's dead at this point. There has been no news in almost a year and the company has been unresponsive. Even if they make a release, other providers have had their solutions out in the open for a long period of time - and it would take a year or more for enough people to dig in and validate their work before it could be trusted adequately.

Thanks for posting this graphic. I did miss this mention in Build 2018.

Thanks @moodmosaic !

This is amazing

While we are waiting, check the post Microsoft Introduces Blockchain Based Products by Mahesh Chand on Oct 14 2018

Silence for almost a year. I guess this is a dead project. Leaving it.


Critical Issue: normalize-where-clause strips out incorrect juncts/disjuncts

Hey Guys,
It looks to me like the following loop is incorrect and will remove the incorrect elements from an array if the array has more than one element slated for removal:
https://github.com/balderdashy/waterline/blob/master/lib/waterline/utils/query/private/normalize-where-clause.js#L602-L608 <- broken loop
I ran into this issue recently in an application where my queries seemed to get gobbled up and spit out incorrectly after the where clause was normalized.
Essentially, I think the indexes referenced in the indexesToRemove array change (in the target array) after the first call to conjunctsOrDisjuncts.splice(indexToRemove, 1);
Additionally, the numRemovedSoFar variable seems to serve no purpose.
I can refactor this block and issue a pull request, do you concur with this assessment?
This issue seems urgent as it completely destroys a valid query
Thanks,
-Mike

Waterline version: 0.13.0-rc11
Node version: 6.2.0
NPM version: 3.6.0
Operating system: All

Thanks again sailsbot!

^ @mikermcneil , @particlebanana

BUMP!

I don't believe a repo is necessary.
Here is a JSBin that clearly shows the loop is flawed:
http://jsbin.com/diwoconaho/edit?html,js,output
This bin should remove objects "B", "D", and "F", but the loop instead removes "B", "E", and "H"
What this means is that any queries that have more than one index slated for removal become invalid queries and this actually interferes with app level code.
Additionally, you cannot reassign conjunctsOrDisjuncts because of this line:
https://github.com/balderdashy/waterline/blob/master/lib/waterline/utils/query/private/normalize-where-clause.js#L526
This is why my pull modifies the conjunctsOrDisjuncts the way it does.  The array must be mutated in place because of how pointers work in javascript.  If you reassign conjunctsOrDisjuncts it has no impact on branch[soleBranchKey] which is actually the larger object structure representing the query.
See crafty array mutation here:
https://github.com/balderdashy/waterline/pull/1494/commits/475f1d10b99e9adebc4515a0a4769d1956926aba

@mdconaway thanks for the work on this.  A couple of things:

You're right that that loop is flawed, for two reasons: it should be - numRemovedSoFar, not +, and more importantly, numRemovedSoFar is never incremented!  And really, it doesn't need to exist at all; you can just use i.  See http://jsbin.com/midico/1/edit?html,js,output
My request for a repro wasn't to prove that the code was broken, but to demonstrate the practical implications.  I can put in a patch for that loop, but I'd like to be able to reproduce your specific issue so that I can check that the patch fixes that issue.

Specifically:

I ran into this issue recently in an application where my queries seemed to get gobbled up and spit out incorrectly after the where clause was normalized.

Give me some code that results in gobbled up queries, so that I can make sure that the patch un-gobbles them! 🦃

See the waterline demo app here:
https://github.com/mdconaway/waterline-bug-1493
To run the test, just do a git clone of the project, followed by npm install and npm start

Anything else I can do to get this patched into mainline @sgress454 ?

@mdconaway Sorry for the delay -- discussed this with @mikermcneil and expect to have that patch out tomorrow.

@mdconaway @sgress454 thanks guys!

This is fixed as of v0.13.1-1.


Time Picker: Circle does not fit on small screen

Environment
I had this issue on a Redmi Note 3, but I am quite sure it is not the only device affected.

Tech
Version

@material-ui/pickers
3.1.2

material-ui
4.0.2

React
16.8.6

Browser
Chrome mobile

Peer library
moment.js 22.2.2

Steps to reproduce
Without knowing what device you have available, the easiest way to reproduce this behaviour is probably in a desktop browser.

Go to https://material-ui-pickers.dev/demo/timepicker
Simulate a device viewport (Firefox, Chrome)
Select a small viewport, e.g. iPhone 6/7/8, landscape
Click on the first example ("Basic Example")

Expected behavior
The circle is scaled, so it fits into the dialog
Actual behavior
The circle is larger than the dialog; the user has to scroll.

Live example
See steps to reproduce

I think that we could have the size of the Clock to fit the size available.


Create application that exposes REST endpoint and returns JSON payload

This can be written in any language just have to return:
{
 “message”: “Automate all the things!”,
 “timestamp”:<PHONE_NUMBER>
}

Tasks:

[x] Create rest API
[x] Ensure timestamp is current time
[x] Create tests
[x]  Document application

[x]  build
[x]  run
[x]  deploy
[x]  test

This should be good now maybe.


Added Select stories

Closes #535

Remaining scenarios:

Test value change of colour when is searchable and the list is opened (for both single and multiple selections).

Test value colour when is searchable and the list is closed (should be the regular one).

In the second scenario, I think we should mix it with an existing example.


Create a view of Resources

As we instrument resources (sockets, files, timers, etc) (#39), we want a view to visualize them, seeing related attributes and states, such as what task they currently "belong" to.

I was playing with some fake data and came up with this potential mock-up:

One important detail/goal here is that in an ideal world, a user would be able to distinguish "Task A is waiting on Resource" from "Task B currently using Resource", and that in turn from "Task C is responsible for eventually replenishing Resource."

Agreed, this will be especially useful for things like channels or locks, where we know one task is doing something that will affect another waker.

I believe this was implemented in #188.


First minter is now account that brings token on chain

Upgrade premint lib to gracefully handle zero preminter
Set firstMinter only in the case of a delegatedMint (aka premint) from the user that initiated the request.
Fix tests

** added benefit of setting first minter only in the case of a premint is upgrades do not cause issues with the storage flows with this premint reward.
See: https://github.com/ourzora/protocol-rewards/pull/20
Need to confirm with product (alan/joe) if this is what we want to do
Contract size:
| ZoraCreator1155Impl               | 24.459    | 0.117       |

@oveddan rebased and added changeset

great change, much simpler now. thank you @iainnash


Clean up / Improve the list of collectors

Currently, the enabled collectors for a system lives in a static list called PLATFORM in main.rs. This is probably not the best way to gather which collectors should be run, as it would require recompilation to configure which collectors should be run.
There likely should be some kind of hybrid solution: a compile-time method to gather all the collectors available for the target arch this is compiled for (that is, perhaps an automatic way that would not require maintaining a list), and then also a run-time method to filter appropriate collectors.

better detailed in #20


[bugfix] chart legend verbose name

Cherry-pick the following commit(s):

SHA
Time
Log
Author

5a377322
Fri Nov 9 11:06:30 2018 -0800
change to camelcase (#6354)
Krist Wongsuphasawat

8bf9a5b9
Fri Nov 9 11:15:42 2018 -0800
[dashboard] fix save/save-as flow (#6350)
Chris Williams

@john-bodley @conglei @graceguo-supercat @kristw @michellethomas @timifasubaa @williaster

Codecov Report

Merging #126 into airbnb-master will not change coverage.
The diff coverage is 100%.

@@              Coverage Diff               @@
##           airbnb-master     #126   +/-   ##
==============================================
  Coverage          76.91%   76.91%
==============================================
  Files                 47       47
  Lines               9373     9373
==============================================
  Hits                7209     7209
  Misses              2164     2164

Impacted Files
Coverage Δ

superset/views/core.py
74.12% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


go version 1.18.3,panic: in net/netip.AddrFromSlice: cannot convert *t0 ([]byte) to *[4]byte

go version 1.18.3,panic: in net/netip.AddrFromSlice: cannot convert *t0 ([]byte) to *[4]byte

I am getting the same error，go version 1.20

try as what this say,good luck https://github.com/ofabry/go-callvis/pull/121


Dev kmr

@atheurer  After starting with your initial list this is what I'm left with at this point on the TODO list:
package manager: apt, zypper

cpu information: IOMMU info.

openvswitch if present: all bridges and ports

disk: all device-driver parameters (io-depth, etc).

list of all containers running from cri-o or docker

-if found: /etc/kubelet.conf, /etc/nova.conf (and many other openshift and openstack config files)

Can you expand on what you were looking for with regards to the IOMMU and the device-driver parameters?  I found some IOMMU stuff in /sys/class/iommu but I didn't find it all that interesting...

@atheurer After starting with your initial list this is what I'm left with at this point on the TODO list:
package manager: apt, zypper

cpu information: IOMMU info.

openvswitch if present: all bridges and ports

disk: all device-driver parameters (io-depth, etc).

list of all containers running from cri-o or docker

-if found: /etc/kubelet.conf, /etc/nova.conf (and many other openshift and openstack config files)

Can you expand on what you were looking for with regards to the IOMMU and the device-driver parameters? I found some IOMMU stuff in /sys/class/iommu but I didn't find it all that interesting...

I suppose a lot of the info will already be in dmesg, but I think there's something in /sys about iommu groups.


vagrant and ansible first stab at using galaxy

DO NOT MERGE - JUST REVIEW
@kave @kurtw @rosskarchner @marcesher
Please see PR. This is a starter example of utilizing ansible's role's path and ansible galaxy in an attempt to minimize code duplication across our projects as well as follow and define a few new best practices.
Note 'ansible/vars/db.yml' contains some plain text passwords that will be vault-ified in a later PR but they are placeholders for now.
instructions - after installing ansible
$ ansible-galaxy install -r ansible/requirements.yml
$ vagrant up

Note that 2 playbooks are taken from the most popular open source repos.
Note that 1 playbook is taken from a popular open source repo and customized for our needs (and a PR was placed against the main open source repo for elasticsearch)
Note that our requirements for those roles are described in a versioned requirements.yml file instead of being included inside the project directory.
Note that those roles are downloaded from github, github enterprises, etc, and placed into your local roles path (for me it is /Users/cabralv/homebrew/bin/ansible/roles) but this is configurable.
Obviously there is a ton of work to do to get this ready for even local vagrant but part of this is asking for your ideas to contribute to the way we create ansible playbooks as opposed to how we are creating this playbook. Feel free to give feedback and thanks!

cool looks good. i forgot to mention we'll also need pdfReactor installed within the box. location doesn't matter we currently have it installed in the /opt/ location.
you'll also need to add it to the python path export PYTHONPATH="${PYTHONPATH}:/opt/PDFreactor/wrappers/python/lib"
start server: /opt/PDFreactor/bin/pdfreactorwebservice start
tip : i ran into an issue being able to connect the server within unitybox incase you have the same issue you'll need to:

Edit the PDFReactor/jetty/etc/jetty.xml to use the host name <IP_ADDRESS>.

There are some license global vars to consider but we talk about that offline

@kave thanks for the feedback. I have PDFreactor -> zip written down in my notes so I'm glad you reminded me so we can include that in this config.

https://github.cfpb.gov/ConsumerResponse/complaint-analytics-search-tool-box/tree/master/provisioners/roles/elasticsearch @mehtad wrote a pretty great elasticsearch role that, on first inspection, seems better than the open source playbook I stole.

@vccabral it seems to be trying to write to /etc on my mac?
- downloading role from https://github.com/geerlingguy/ansible-role-mysql/archive/1.9.1.tar.gz
- extracting geerlingguy.mysql to /etc/ansible/roles/geerlingguy.mysql
- error: you do not have permission to modify files in /etc/ansible/roles/geerlingguy.mysql
- geerlingguy.mysql was NOT installed successfully.

@rosskarchner it writes to your ansible roles_path directory. Mine defaulted to my brew install directory but you can customize it a few ways.
http://docs.ansible.com/ansible/intro_configuration.html#roles-path

Aha-- that's probably a difference of note, for installing via homebrew or pip.

@kave & @kurtw I'd love to sit down with one of you for a few minutes to go over extra details of getting PDFReactor working.

@kave can you please run a test locally?
$ git clone git@github.com:vccabral/cfgov-refresh.git
$ cd cfgov-refresh
$ ansible-galaxy install -r ansible/requirements.yml
$ vagrant up

After you get the box up, use the setup scripts and then we can dry run the site to make sure it is working.

@rosskarchner any thoughts  on the initial design?

@vccabral I just tried this out, and id died at:
TASK: [Add environment variables to bashrc] ***********************************
changed: [default] => {"backup": "", "changed": true, "msg": "line added"}

TASK: [Migrate django db to match application state] **************************
fatal: [default] => failed to transfer file to /home/vagrant/.ansible/tmp/ansible-tmp-1456340115.46-34486355913313/command:

Received message too long<PHONE_NUMBER>

FATAL: all hosts have already failed -- aborting

PLAY RECAP ********************************************************************
           to retry, use: --limit @/Users/karchnerr/cfgov_refresh_setup.retry

default                    : ok=65   changed=45   unreachable=1    failed=0

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

@rosskarchner please remove any echo in the .env script to solve your error.

@kave can you close this pr?
it's addressed as part of : https://github.com/cfpb/cfgov-refresh/pull/1534


Fix/dependancy updates

Mainly dependancy fixes

oh oh, "This branch has conflicts that must be resolved" :crying_cat_face:

Messed up this branch and cba cherry-picking


Pinged users with almost the same username won't display properly

As you can see in the picture above, the plugin doesn't seem to render the pinged users properly even though I have saved the two different pinged users in the database and send it as data to the ajax calls.
// I'm not using the function below:

/*
            var saveComment = function (data) {
                // Convert pings to human readable format
                $(Object.keys(data.pings)).each(function (index, userId) {
                    var fullname = data.pings[userId];
                    var pingText = '@' + fullname;
                    data.content = data.content.replace(new RegExp('@' + userId, 'g'), pingText);
                });
                return data;
            };
            */
$commentsContainer.comments({
    // User
    currentUserId: 460,
    profilePictureURL: 'https://storage.googleapis.com/topanimecharacters.com/validated/images/profile/default',
    currentUserIsAdmin: false,
    // Functionalities
    textareaRows: 1,
    highlightColor: '#007bff',
    textareaMaxRows: 7,
    maxRepliesVisible: 3,
    enableDeletingCommentWithReplies: true,
    defaultNavigationSortKey: 'newest',
    readOnly: false,
    enablePinging: true,
    enableHashtags: true,
    searchUsers: function(term, success, error) {
        $.ajax({
            type: 'GET',
            url: '/character/get_comment_users/pXMqXq/' + pageNumber,
            timeout: 0,
            success: function(usersArray) {
                success(usersArray.filter(function(user) {
                    var containsSearchTerm = user.fullname.toLowerCase().indexOf(term.toLowerCase()) != -1;
                    var isNotSelf = user.id != 460;
                    return containsSearchTerm && isNotSelf;
                }));
            },
            error: function(data) {
                alert("Something went wrong while loading users to ping, sorry :(");
                return error;
            }
        });
    },
    getComments: function(success, error) {
        $.ajax({
            type: 'GET',
            url: '/character/get_comments/pXMqXq/' + pageNumber,
            timeout: 0,
            success: function(commentsArray) {
                if (!commentsArray[1]['more_comments']) {
                    $loadMore.css('display', 'none');
                } else {
                    $loadMore.css('display', 'block');
                    $loadMore.removeAttr('disabled', false).html("Load more");
                }
                success(commentsArray[0]);
            },
            error: function(data) {
                $loadMore.hide();
                alert("Something went wrong while loading the comments, sorry :(");
                return error;
            }
        });
    },
    postComment: function(data, success, error) {
        $.ajax({
            type: 'POST',
            dataType: "json",
            contentType: "application/json",
            url: '/character/add_comment/pXMqXq',
            timeout: 0,
            data: JSON.stringify(data),
            success: function(comment) {
                console.log(comment);
                success(comment);
            },
            error: function(data) {
                alert("Couldn't process your request, can't have a comment longer than 10.000 letters/characters and a max of 25 newlines, have you confirmed your email?");
                return error;
            }
        });
    },
    putComment: function(data, success, error) {
        $.ajax({
            type: 'PUT',
            dataType: "json",
            contentType: "application/json",
            url: '/character/update_comment/' + data.id,
            timeout: 0,
            data: JSON.stringify(data),
            success: function(comment) {
                console.log(comment);
                success(comment);
            },
            error: function(data) {
                alert("Couldn't process your request, can't have a comment longer than 10.000 letters/characters and a max of 25 newlines, have you confirmed your email?");
                return error;
            }
        });
    },
    deleteComment: function(data, success, error) {
        $.ajax({
            type: 'DELETE',
            url: '/character/delete_comment/' + data.id,
            success: success,
            error: function(data) {
                alert("Couldn't process your request, please don't spam the request, have you confirmed your email?");
                return error;
            }
        });
    },
    upvoteComment: function(data, success, error) {
        if (data.user_has_upvoted) {
            $.ajax({
                type: 'POST',
                url: '/character/upvote_comment/' + data.id,
                error: function(data) {
                    alert("Couldn't process your request, please don't spam the button, have you confirmed your email?");
                    return error;
                },
            });
        } else {
            $.ajax({
                type: 'POST',
                url: '/character/downvote_comment/' + data.id,
                error: function(data) {
                    alert("Couldn't process your request, please don't spam the button, have you confirmed your email?");
                    return error;
                },
            });
        }
    },
    timeFormatter: function(time) {
        return new Date(time).toLocaleDateString('en-US');
    },
    hashtagClicked: function(hashtag) {
        window.open('https://www.google.com/search?q=' + hashtag);
    },
    pingClicked: function(ping) {
        window.open('https://www.google.com/search?q=' + ping);
    },
});

Yes, the reason why I'm not using the saveComment function is that I'm replacing the user ids with the usernames on the server side instead.

Okay this is quite sad, haven't received a response in a long time, now gonna close this


package_name argument on nargo new is ignored

Aim
I should be able to set the name of a new package independently of it's path.
Expected Behavior
nargo new ./foo bar should create a new package with the name bar in directory foo.
Bug
bar is ignored and the new package has the name foo.

We should also change this to be an optional flag rather than a positional argument.


UI changes for the baseball cards

Modified how the buttons look and made some minor adjustments to the cards' appearance.

Committed on foa_ui as 61f7e17a437e1bf2401988ad922f68b3c28b2c16.


Fix job scheduling on restart after partially failed DAGs

If a job in a DAG fails and there is another path to its child, the child is run in the restart irrespective of the status of the previously failed parent in the new run.
@arkal will write a test to prove this behaviour and wither @cket or @benedictpaten will probably write the fix.

Likely related to #1100


Trigger docs deployment for release-20 branch

Description of changes:
Trigger docs deployment for release-20 branch
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/override govulncheck


Documentation .env credentials seems to be wrong

To enforce authentication, the documentation states that the following entries should be made in the .env file: USERNAME=<your_username> and PASSWORD="<your_password>". This absolutely did not work for me. Only when I changed the entries to MONGOGUI_USERNAME="username"
MONGOGUI_PASSWORD="password" the authentication also worked.

Thanks, worked for me!

does that work within the docker image? what path should I create .env file in "/app"?


feat: Migration of LCEVC DIL (Decoder Integration Layer) to LCEVC Dec (Decoder)

Migration of LCEVC DIL (Decoder Integration layer) to LCEVC Dec (Decoder)
Description
We are in the process of deprecating LCEVC DIL and migrating Integrations to LCEVC Dec. We also have a new library for the LCEVCDec on  NPM
The new LCEVCDec has bug fixes for sync issues with VOD contents, and LCEVC Decode functionality for LIVE contents. There are new features to handle different streaming formats with timestamp offsets being passed to the Decoder.
The integration itself is very similar to the existing integration with some added parameters to existing functions and a new extern to handle additional features.
We have also added a quick start guide in the documentation and updated more LCEVC contents with different combination of containers and streaming formats.
Documentation
All integration related documentation is available at docs/design/lcevc-integration.md
Quick Start guide is available at docs/tutorials/lcevc.md
Executed Tasks

[ ]  Signed Google CLA
[ ]  Builds build/all.py successfully
[ ]  Runs build/test.py successfully

Hi @avelad @joeyparrish is this PR ready to be merged, or will you guys be checking and merging the PR on your side?

Hi @v-nova-vinod, for me it's ready to merge, but @joeyparrish 's review is still necessary... sorry!

Thanks @v-nova-vinod !


background from 'background" type instead of "features"

with the evolution of the dnd5e module on vtt,
and the dndbeyond importer,
backgrounds can be imported but they use the "background" type.
I would be nice for the hero creation tool to be able to accept input from that new type.

I totally missed this new issue, but it's almost done already.. just behind the scenes! 👀 I need to finish some parts but it should be releasing soon

Just wondering the status on this? I know that it's being worked on - but unfortunately it's holding things up with getting my server up and running (manually importing doesn't work for everything).

backgrounds seem to be already working most of the way, I'm being a little halted by the advancement API so that they are reversible (with the provided Acolyte background, when you drag it into a character sheet, it will add the feature, but also will remove the feature if you remove the Background; that part needs a little wiring that I haven't had time to work on yet)
Worst-case scenario, I aim to deliver something this weekend, even if it's sadly half-baked; which would mean that if you remove a background added through the Creation Tool, it will not remove the feature and/or probably throw an error on the console, but you should be able to then remove the backgrounf feature manually. Same thing with Class Features (they basically rely on the same mechanism that I haven't tackled yet)


which image version for the Log4j Vulnerability in confluent platform

Hi Team,
Did someone know below images for Log4j Vulnerability(Log4j v2.17) on confluent platform? I'm not found the log4j jar inside the images.
image:
confluentinc/cp-zookeeper: 6.0.1
confluentinc/cp-enterprise-kafka: 6.0.1
confluentinc/cp-schema-registry: 6. 0.1
confluentinc/cp-kafka-rest: 6.0.1
confluentinc/cp-kafka-connect: 6.0.1
confluentinc/cp-ksqldb-server: 6.0.1
Thanks In Advance!
Levi

I have found this jar relate to log4j inside  cp-kafka-connect: 6.0.1
cd /usr/share/java/kafka
-rw-r--r-- 1 root root    12211 Nov 20  2020 slf4j-log4j12-1.7.30.jar
-rw-r--r-- 1 root root    41472 Nov 20  2020 slf4j-api-1.7.30.jar
-rw-r--r-- 1 root root   491849 Nov 20  2020 confluent-log4j-1.2.17-cp2.jar

Please see https://support.confluent.io/hc/en-us/articles/4412615410580-December-2021-Log4j-Vulnerabilities-Advisory

Hi @andrewegel
It's very helpful. Thanks!


[C++][Python] installing pyarrow breaks the conda environment

I am working with pyarrow for parquet and feather IO. My environment has the following requirements python=3.8, pandas, geopandas, pyarrow, matplotlib, seaborn, jupyter
You can reproduce the env using

$ conda create -n testpyarrow python=3.8 pandas geopandas matplotlib seaborn jupyter notebook pyarrow

$ conda activate testpyarrow

you can skip pyarrow in the above command and then install it separately from conda-forge as instructed in the pyarrow github (doesn't make a difference) page using

$ conda install -c conda-forge pyarrow

After the env is created and activated, opening a python terminal and try importing to import anything

$ python
>>>import pandas

yields

Illegal instruction (core dumped)

If you uninstall pyarrow, all the imports start working. So I have zeroed down that pyarrow is breaking the imports.
As it is core dumped I can't trace the issue further. Illegal instruction is raised irrespective of the library I try to import  (i.e. seaborn, matplotlib, geopandas, pandas, etc)
Environment: Conda version: conda 4.10.3
The issue occurs on RedHat Linux Server running on AMD Opteron Processor 4180. (Works with intel processor)
Reporter: Naman
Related issues:

[C++] Provide an initialization and/or compatibility check function (is related to)

Note: This issue was originally created as ARROW-14526. Please see the migration documentation for further details.

Going to close this issue, as I don't think there is anything actionable left (https://github.com/apache/arrow/issues/22437 was opened to provide a better error).


chart.update() do not update xLabels

We have to manually update labels after changing the point:
_.each(data, function (row, idx) {
  var label = row[0],
      value = row[1];

  chart.datasets[0].points[idx].label = label;
  chart.datasets[0].points[idx].value = value;

  chart.scale.xLabels[idx] = label;
});

chart.update();

Otherwise the xLabels didn't get updated.

In V1 the library doesn't handle this. In v2, this is handled as you can replace the entire data object if necessary and then call update(). V2 docs can be found at http://nnnick.github.io/Chart.js/docs-v2/


Fastlane should declare a maximum ruby version of 3.1

New Issue Checklist

[ ] Updated fastlane to the latest version
[ ] I read the Contribution Guidelines
[ ] I read docs.fastlane.tools
[ ] I searched for existing GitHub issues

Issue Description
Some of the dependencies don't work with ruby 3.2 (https://github.com/SlatherOrg/slather/issues/529) so fastlane shouldn't be installable with this ruby version
Command executed
fastlane anything with slather
Complete output when running fastlane, including the stack trace and command used

[09:53:21]: ------------------------------
[09:53:21]: Driving the lane 'ios metrics' 🚀
[09:53:21]: ---------------------
[09:53:21]: --- Step: slather ---
[09:53:21]: ---------------------
[09:53:21]: $ slather coverage --jenkins --sonarqube-xml --build-directory outputdata --output-directory ./sonar-reports --scheme **redacted**.xcodeproj
[09:53:21]: ▸ Slathering...
[09:53:21]: ▸ /opt/homebrew/Cellar/fastlane/2.211.0_1/libexec/gems/slather-2.7.3/lib/slather/project.rb:506:in `find_binary_files': undefined method `exists?' for File:Class (NoMethodError)
[09:53:21]: ▸ raise StandardError, "No scheme named '#{self.scheme}' found in #{self.path}" unless File.exists? xcscheme_path
[09:53:21]: ▸ ^^^^^^^^
[09:53:21]: ▸ Did you mean?  exist?
[09:53:21]: ▸ from /opt/homebrew/Cellar/fastlane/2.211.0_1/libexec/gems/slather-2.7.3/lib/slather/project.rb:456:in `configure_binary_file'
[09:53:21]: ▸ from /opt/homebrew/Cellar/fastlane/2.211.0_1/libexec/gems/slather-2.7.3/lib/slather/project.rb:336:in `configure'
[09:53:21]: ▸ from /opt/homebrew/Cellar/fastlane/2.211.0_1/libexec/gems/slather-2.7.3/lib/slather/command/coverage_command.rb:59:in `execute'
[09:53:21]: ▸ from /opt/homebrew/Cellar/fastlane/2.211.0_1/libexec/gems/clamp-1.3.2/lib/clamp/command.rb:66:in `run'
[09:53:21]: ▸ from /opt/homebrew/Cellar/fastlane/2.211.0_1/libexec/gems/clamp-1.3.2/lib/clamp/subcommand/execution.rb:18:in `execute'
[09:53:21]: ▸ from /opt/homebrew/Cellar/fastlane/2.211.0_1/libexec/gems/clamp-1.3.2/lib/clamp/command.rb:66:in `run'
[09:53:21]: ▸ from /opt/homebrew/Cellar/fastlane/2.211.0_1/libexec/gems/clamp-1.3.2/lib/clamp/command.rb:140:in `run'
[09:53:21]: ▸ from /opt/homebrew/Cellar/fastlane/2.211.0_1/libexec/gems/slather-2.7.3/bin/slather:17:in `'
[09:53:21]: ▸ from /opt/homebrew/Cellar/fastlane/2.211.0_1/libexec/bin/slather:25:in `load'
[09:53:21]: ▸ from /opt/homebrew/Cellar/fastlane/2.211.0_1/libexec/bin/slather:25:in `'
[09:53:21]: ▸ undefined method `exists?' for File:Class
[09:53:21]: ▸ Are you sure your project is generating coverage? Make sure you enable code coverage in the Test section of your Xcode scheme.
[09:53:21]: ▸ Did you specify your Xcode scheme? (--scheme or 'scheme' in .slather.yml)
[09:53:21]: ▸ If you're using a workspace, did you specify it? (--workspace or 'workspace' in .slather.yml)
[09:53:21]: ▸ If you use a different Xcode configuration, did you specify it? (--configuration or 'configuration' in .slather.yml)

Environment
[⠋] 🚀 Ignoring racc-1.6.2 because its extensions are not built. Try: gem pristine racc --version 1.6.2
[✔] 🚀
[10:17:11]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[10:17:11]: Generating fastlane environment output, this might take a few seconds...
swift-driver version: 1.62.15 ✅ fastlane environment ✅
Stack

Key
Value

OS
13.1

Ruby
3.2.0

Bundler?
false

Git
git version 2.39.0

Installation Source
/opt/homebrew/Cellar/fastlane/2.211.0_1/libexec/bin/fastlane

Host
macOS 13.1 (22C65)

Ruby Lib Dir
/opt/homebrew/Cellar/ruby/3.2.0/lib

OpenSSL Version
OpenSSL 1.1.1s  1 Nov 2022

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode_14.2.app/Contents/Developer/

Xcode Version
14.2

Swift Version
5.7.2

System Locale

Variable
Value

LANG

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.211.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

error_highlight
0.5.1

did_you_mean
1.6.3

syntax_suggest
1.0.2

atomos
0.1.3

rexml
3.2.5

CFPropertyList
3.0.5

claide
1.1.0

colored2
3.1.2

nanaimo
0.3.0

xcodeproj
1.22.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.8.0

terminal-table
1.8.0

plist
3.6.0

public_suffix
5.0.1

addressable
2.8.1

multipart-post
2.0.0

word_wrap
1.0.0

optparse
0.1.1

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

artifactory
3.0.15

babosa
1.0.4

colored
1.2

highline
2.0.3

commander
4.6.0

excon
0.96.0

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

faraday-multipart
1.0.4

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.10.2

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.5

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.6

gh_inspector
1.1.3

json
2.6.3

mini_magick
4.12.0

naturally
2.2.1

rubyzip
2.3.2

security
0.1.3

xcpretty-travis-formatter
1.0.1

dotenv
2.8.1

bundler
2.4.2

simctl
1.6.8

jwt
2.6.0

uber
0.1.0

declarative
0.0.20

trailblazer-option
0.1.2

representable
3.2.0

retriable
3.1.2

mini_mime
1.1.2

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.17.0

googleauth
1.3.0

httpclient
2.8.3

webrick
1.7.0

google-apis-core
0.9.3

google-apis-playcustomapp_v1
0.12.0

google-apis-androidpublisher_v3
0.32.0

google-cloud-env
1.6.0

google-cloud-errors
1.3.0

google-cloud-core
1.6.0

google-apis-iamcredentials_v1
0.16.0

google-apis-storage_v1
0.19.0

rake
13.0.6

digest-crc
0.6.4

google-cloud-storage
1.44.0

emoji_regex
3.2.3

jmespath
1.6.2

aws-partitions
1.688.0

aws-eventstream
1.2.0

aws-sigv4
1.5.2

aws-sdk-core
3.168.4

aws-sdk-kms
1.61.0

aws-sdk-s3
1.117.2

set
1.0.3

forwardable
1.3.3

logger
1.5.3

pathname
0.2.1

shellwords
0.1.0

cgi
0.3.6

date
3.3.3

timeout
0.3.1

securerandom
0.2.2

uri
0.12.0

openssl
3.1.0

digest
3.1.1

ipaddr
1.2.5

resolv
0.2.2

time
0.2.1

stringio
3.0.4

open-uri
0.3.0

mutex_m
0.1.2

net-http
0.3.2

net-protocol
0.2.1

ostruct
0.5.5

english
0.7.2

erb
4.0.2

abbrev
0.1.1

tempfile
0.1.3

delegate
0.3.0

fileutils
1.7.0

tmpdir
0.1.3

base64
0.1.1

singleton
0.1.1

open3
0.1.2

nkf
0.1.2

mini_portile2
2.8.1

racc
1.6.2

nokogiri
1.13.10

prettyprint
0.1.1

pp
0.4.0

find
0.1.1

yaml
0.2.1

psych
5.0.1

slather has new release, there should not be any issue now. closing it https://github.com/SlatherOrg/slather/pull/532#issuecomment-1380710532

Thanks, this help me cut through a wall of confusion about Ruby 3.2.2. The fastlane docs say it's okay but use 2.7 as an example. Rvm doesn't have a binary at the ready for any 3.x versions. So after seeing this thread, I installed 3.2.2 via brew and it runs perfectly with Fastlane.
Which is not the point of this thread, but... isn't it?
Thanks!


Tweak GUI to emphasize active components #48

Fixes #48

Now we can put the command box above the status message? BTW, shall we call it Result Display? That way, there's no confusion between it and the Status Bar at the bottom.

@damithc Done.

Looks good.  Result display seems to be abit too short for my Windows, probably need some adjustments.

Yes, a little bit cut off in my office comp.

Probably depends on resolution. May be make the height adjustable? Having a scroll bar is useful too, because we never know how long the result can be e.g. if it was an error message with a stack trace.

@damithc Did a quick change on master to a non-editable text area to allow for scrolling.


Integrate an SAP Fiori App into Your Portal Site (Cloud Foundry)

Tutorial URL: https://developers.sap.com/tutorials/cp-portal-cloud-foundry-sapui5-app.html
Step 4: system is missing when creating a new app.
The console shows that a POST request is sent to a GraphQL endpoint to get the destinations (https://trial.dt.cpp.cfapps.eu10.hana.ondemand.com/bff/graphql) but the response is 404 Not Found: Requested route ('portal-service.cfapps.eu10.hana.ondemand.com') does not exist.

Hi
There was a defect that our devops solved
Please close this issue
Thanks
Iris.
From: Daniel Wroblewski<EMAIL_ADDRESS>Sent: Sunday, October 6, 2019 8:19 AM
To: SAPDocuments/Tutorials<EMAIL_ADDRESS>Cc: Sasson, Iris<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [SAPDocuments/Tutorials] Integrate an SAP Fiori App into Your Portal Site (Cloud Foundry) (#4015)
Assigned #4015https://github.com/SAPDocuments/Tutorials/issues/4015 to @IrisSassonhttps://github.com/IrisSasson.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/SAPDocuments/Tutorials/issues/4015?email_source=notifications&email_token=AIAX5ZADWHRTZ3TBURAEEGLQNFYMPA5CNFSM4I5ITKH2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUBIWIDI#event-2689688589, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIAX5ZH4EKLDM2ERIVCJ7EDQNFYMPANCNFSM4I5ITKHQ.


fix memory leak for hnsw and add function test

@inabao please create a issue to describe these possible memory leak, and ref it in this pull request


repository: needs full documentation update (and new binary instructions)

Now that the repository has a new golang binary tool to update the new kernels, documentation should be updated. Other documentation tasks needed:

Update all documentation files (check examples, distro versions, etc)
Update BPF/BTF internals documentation (btfgen was moved to bpftool)
Bring examples directory back with simple example on how to use this

Im still missing bringing the example back to the repository.


Add My projects feature

A new feature for logged-in users
Logged-in users can now bookmark their favorite projects on bestof.js.org.
User's bookmarked project list is store in Auth0 user's profile, see issue #41 for more details.
This feature is still experimental, we wait for user's feedback.
Refactoring
In addition of the feature, a lot of refactoring has been done to avoid duplication of data in the Redux state.
The state should be the single source of truth.
Anything that can be computed from the state should not be in the state.
As much as possible, we use selectors from Reselect library to access computed values.
Linting
From now, we use a combination of ESLint and Prettier to format the JavaScript code.
Using Prettier makes coding experience far much better, especially if the IDE is setup to automatically format the code when saving.
No need to worry about spacing, semi-columns and so many things...
The Slack channel
Also, a new Slack channel has been created by @sradevski ,  a link has been inserted in the project's README.md
Join us on https://bestofjs.slack.com/

Click here if you want to create eslint's auto-correct Pull Request

See the documentation if you want to get more information about auto-correct.
Document


copy animation on my keys

Location
/mykeys
Expected behavior
Get an animation when clicking "copy private key" or "copy public key"
Actual behavior
Doesn't do the animation when clicking
Steps to reproduce the problem
create account > make backup > my keys

On page 'make-backup', I'm replacing the link to the page 'my-keys' with the display-show-keys. The page 'my-keys' I will delete after this, but first I will copy the code of the QR-stuff to solve issue #573

After discussing trying to make this work and discussing this with @kikipluche , we came to following conclusion:
Following our design-philosophy, we don't want the user to be visually overwhelmed and we want to confronted a user with as little messages/actions (preferabbly one) per view. That's why we're moving the whole keys-stuff to a separate page, not a display. All the instances of display-show-keys will be replaced by links to page 'my-keys'. On this page you will be able to show your private key, copy each key and show a QRcode of each key.

@faffydee since we are putting the rework on hold for now, we can do this little improvement to make the user experience consistant.


README.md and mysmb.py are updated

TL;DR
In README.md the code is suggested run as follows python eternalblue_checker.py <TARGET-IP> however the file name is eternal_checker.py. So I updated README.md according to the requirement.
The second one is related to the try-exception block in mysmb.py to create SMBSERVER_DIR. If the code runs with python3.x, can't be compiled because of the syntax is not fit to Python3.x format. So I fix that line as well and it runs with both Python3.x and Python2.x in this way.

You're welcome. Happy to contribute a tool I'm using by myself either. 🎉


firebase remote config error "Application name is not set"

Hello,
I'm trying to integrate firebase remote config in a flutter app.
But when running the application, i've got this error :
Application name is not set. Call Builder#setApplicationName.
Library :
https://pub.dartlang.org/packages/firebase_remote_config
Following this example :
https://github.com/flutter/plugins/tree/master/packages/firebase_remote_config/example
Package flutter used:
firebase_remote_config: ^0.1.0+2
app/build.gradle:
implementation 'com.google.firebase:firebase-config:16.4.0'
Full error logs:

W/zze     (25659): Application name is not set. Call Builder#setApplicationName.
I/FirebaseRemoteConfig(25659): Fetch succeeded!
W/zze     (25659): Application name is not set. Call Builder#setApplicationName.
W/zze     (25659): Application name is not set. Call Builder#setApplicationName.
W/FirebaseRemoteConfig(25659): No value of type 'FirebaseRemoteConfigValue' exists for parameter key 'hello'.
W/FirebaseRemoteConfig(25659): No value of type 'FirebaseRemoteConfigValue' exists for parameter key 'test'.

@sebastienchouan Hey. Were you able to figure this out. Am facing the same issue.

Hello @dheeraj2dj
In my case it was due to the fact i was using a wrong google account connexion :

I configure firebase parameter with a google account
I was using the file google-services.json from another google account

Be sure that in the firebase console, you've got the parameter you want to use.
Did it help ?

this is working for me.
adding       await remoteConfig.fetch(expiration: const Duration(seconds: 0)); and await remoteConfig.activateFetched();
  void _adminValidate() async {
    try{
      final RemoteConfig remoteConfig = await RemoteConfig.instance;
      await remoteConfig.fetch(expiration: const Duration(seconds: 0));
      await remoteConfig.activateFetched();
      print(remoteConfig.getString('admin'));
    }catch (e){
      print(e);
    }
  }


Images not loading

The images will not load

You might want to try clearing your cache and reload the page.
Sent over the interblag from a GUI.
https://github.com/theusaf
https://shortr.github.io/?llorkcir

On Nov 18, 2020, at 4:25 PM, Virusnest<EMAIL_ADDRESS>wrote:

The images will not load
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


OTP mechanism for TC

Contacts without phone-number/email should be visible in the contact list
Deep links for such contacts, when added as trusted contacts, should be OTP encrypted.

Contacts without phone-number/email should be visible in the contact list
This issue resolved in Address Book #1079 bug

Does not allow access to the alphabets.


Perl variables are not detected in 9.4.0

I can't seem to get perl variables to be detected properly.  This small example should put an hljs-variable span around $scalar, @array, %hash and $k but it doesn't.  I looked at the source and the VAR definition seems like it should be right, but I don't really know a lot about how the internals work.
I totally didn't expect that it would know that in foo =>, "foo" is a string but it does. Cool!

        <link rel="stylesheet" href="http://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.4.0/styles/default.min.css">

my $scalar = "string";
my @array  = qw{ foo bar baz };
my %hash   = ( foo => q{ bar baz } );

sub subroutine {
    for my $k (sort keys %hash) {
        print $k;
        $scalar .= " $k: " . $hash{$k};
    }
}

subroutine();

@afresh1 we decided not to highlight each variable since 9.0 release.

Ahh, I see.  I didn't realize that since the bash config does.  Thank you.

To elaborate on that, here's my answer for a similar problem raised for PHP: https://github.com/isagalaev/highlight.js/issues/1142#issuecomment-209557477

Would it make sense to highlight perl's special variables then?


dm+d search results need better title/description for Google

An (artificial) search for paracetamol finds two pages but the titles/descriptions are not very good.

Also I was wondering if it is possible for google to find the dmd browser when you search by a product code like [Pfizer Atorvastatin 20mg] ?(https://openprescribing.net/dmd/ampp/1339011000001102/)


fix: Use Lang module for new card and use the current date

Squash and merge is recommended
Fixes #50

Thank you for your awesome contributions to this project!


Re-enables consumer tools and ed resources

Changes

Re-enables Consumer Tools and Education Resources links in the mega menu.
Temporarily hides the overview pages at desktop sizes for those two sections. (Note: there are still there, but disabled links at mobile.)

Testing

gulp build and check the first two menu items.

Review

@jimmynotjim
@KimberlyMunoz
@sebworks
@schaferjh (please double-check link URLs in _vars-mega-menu.html below)

Screenshots

Todos

The disabling link feature for the overview links needs to be updated because the fallback menu still only has a # URL for the top-level links that have disabled overview pages.

Part of DFJR-1095

:+1:

:+1:


Make seed backup notification row clickable

Resolve #505
This PR allows:

Make backup warning row clickable
Make add account row clickable

Testing out this PR, i noticed that i have tried creating 3 different account is my 3 different wallets, and only one account showed up (the last wallet). and that happened after i exited and restarted the application. I have fully synced my wallets, yet the other two are still not displayed.

Also, when i click the backup section and try navigating back, the application crashes (NB: this can also be noticed in master will open an issue for this).

Not so sure about the approach you used to implement the clickable row though, however, i think a better approach would have been to use the approach used in the settings page.
https://github.com/planetdecred/godcr/blob/c31798a81ccd2943430f24e7e491edc4a3cd8f1a/ui/page/settings_page.go#L337
You may need to extend the clickable row method so it can be used across multiple pages.

Testing out this PR, i noticed that i have tried creating 3 different account is my 3 different wallets, and only one account showed up (the last wallet). and that happened after i exited and restarted the application. I have fully synced my wallets, yet the other two are still not displayed.
Tested this on master and the accounts where created, however only displayed when i restart the application. What it should be is to have the accounts displayed in the UI after they are created.

Kindly list out the steps to reproduce the error you're experiencing. If the error isn't peculiar to this PR, kindly create an issue for it also listing out the steps to reproduce the error and it would be fixed on another PR.

When an account is created, they are only displayed after the application is restarted.
I will be creating an issue for this.