Move contrib to its own repository

Once non-core modules have been moved to contrib, it should be moved to its own repository, oauth2client-contrib.
This would require these changes, in this order:

A new github repository, google/oauth2client-contrib will need to be created.
oauth2client-contrib will be published on pypi as oauth2client-contrib and will depend on oauth2client>=2.0.0.
oauth2client will need to add the code necessary to enable it to be used as a namespace package.
oauth2client will add an extra that installs contrib.
oauth2client.contrib and associated tests will be removed from the source tree.
Version 2.0.0 of oauth2client will need to be released.

Users will then be able to install oauth2client and contrib at once using:
pip install oauth2client[contrib]

The following bugs/PRs must be closed/merged before the move:

#353 / #352 - move non-core modules into contrib.
#351 - DictionaryStorage and storage locking.

:+1:  (e.g. https://pythonhosted.org/Flask-OAuth/)

@nathanielmanistaatgoogle let us know your thoughts.

"it should be moved to its own repository" caught me off-guard. Why? This issue talks about how to go about separating the code but doesn't describe the benefit of doing so. What need is a contrib directory in this repository unable to fulfill?

It isn't a core part of the implementation. It is an add-on and the release cycles don't need to be tied together.

I guess, sure, but... it still seems like an awful lot of fuss. Are there situations today in which someone would want to use the core part of oauth2client but can't because the presence of contrib introduces some encumberance? Does contrib drag in a lot of heavy dependencies, or particularly problematic dependencies?
I'm not saying that separating out contrib is the wrong thing to do; I'm just not yet seeing it motivated by a strong and pressing user need. Fill in for me the parts of the picture that I'm missing?

The Flask users don't have a strong and pressing need for Django helpers
The Django users don't have a strong and pressing need for App Engine helpers
The App Engine users don't have a strong and pressing need for file system helpers

and so on.
The main reason this came up is that @jonparrott and I were discussing de-coupling the release cycles of the core library and the extensions (which are really just mini-libraries all on their own).

I'm feeling more and more like this isn't worth doing, but I promise I won't stop you from doing it.
There are lots of modules in the Python standard library for which I don't have a strong and pressing need, but there's installed on my system along with the rest of Python because their presence isn't a significant burden on me and the library is less work for the maintainers if everything is in one larger package rather than many smaller packages.
Of course "Flask users don't have a strong and pressing need for Django helpers", but how large a cost are they paying if the Django helpers get installed along with the Flask helpers"? And is it a reasonable proposition that publishing two smaller libraries is more work than publishing one larger library?
When you were talking about decoupling the release cycles, is that so that contrib can release more frequently or less frequently than oauth2client?

When you were talking about decoupling the release cycles, is that so that contrib can release more frequently or less frequently than oauth2client?

More frequently.

Are there situations today in which someone would want to use the core part of oauth2client but can't because the presence of contrib introduces some encumberance?

No.

Does contrib drag in a lot of heavy dependencies, or particularly problematic dependencies?

Contrib is all optional dependencies, so no here as well.
There are two real motivating factors here, and I can totally be talked out of this:

Splitting core from contrib makes a bit of sense. For example, libraries such as gcloud-python should need only depend only on the core, considering we're recommending the use of GoogleCredentials exclusively in that use case.
Although contrib is not large now, we could encourage more activity there. This could lead to the need for faster releases. Really, there isn't much more I feel core needs in terms of functionality. So, core could remain relatively stable compared to the rapid release cycle of contrib.

I actually wasn't thinking of splitting it beyond two packages, @dhermes. All of the helpers would still live in the same place - at least until things get large enough to break up further.

:+1:

I remain reluctantly okay with this; feel free to now proceed with carrying this out.

I won't be able to get to this until January, so we can all think on it for a while. :)

SGTM

I no longer want to split contrib into its own repository, I will revisit this concept another time.


#400: Ignore preceding whitespace check for ( in closure signatures

Fixes #400.

👍

👍

[Current coverage][cc-pull] is 90.30%

Merging [#402][cc-pull] into [master][cc-base-branch] will increase coverage by +<.01%

@@             master       #402   diff @@
==========================================
  Files            60         60
  Lines          2256       2258     +2
  Methods           0          0
  Messages          0          0
  Branches        328        329     +1
==========================================
+ Hits           2037       2039     +2
  Misses          135        135
  Partials         84         84

[][cc-pull]

Powered by Codecov. Last updated by c1e6629
[cc-base-branch]: https://codecov.io/gh/sleekbyte/tailor/branch/master?src=pr
[cc-pull]: https://codecov.io/gh/sleekbyte/tailor/pull/402?src=pr


pull request for e2e test at 01/28/2017 16:56:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Search & Results Page

Value proposition
As a user,
I want to search the whole page
so that I can find the information I need.
Description

Acceptance criteria

[ ] Input field for text search
[ ] search by tag (click on button)
[ ] search results are displayed with a short description
[ ] back button

Complexity
Small | Medium | Large
Tasks

[ ] Create branch search
[ ] add search page (routes)
[ ] add search results page (nested route)
[ ] search form (onChange, onSubmit handlers)
[ ] filter function (videoEntries and blogEntries data)
[ ] component Result (Headline, 2 lines of description)
[ ] back button - SVG instead of text (new component)
[ ] hide search by tag if search form is active

Hi Stephan,
looks good!
A few questions:

How do I get to this search page, via the menu or somehow else? Is the arrow in the right lower corner the back button? Why is it missing on the second wireframe?
I am confused from the tags "Audio", "Schnitt" and "Kamera" displayed three times; I guess you mean different tag names in line two and three? Let's use real-world tags ;)
What happens if I choose one of the search results via keyboard + enter: Does the search starts immediately or do I have to click the search button afterwards?
What is exactly displayed when the search is done?
What happens if I enter a keyword for which there is no result?

Hi Paul - thanks for your feedback. It is really very helpful. I hope everything is easier to understand now. The design was a bit outdated. The search results page by keyword is already in use (see my latest PR). I plan to reuse some of the components. The back button (the blue one on the last image) could replace the SVG on the first image. This is a question of UX - I like the SVG better, but the blue button is already used everywhere.
Best
Stefan


📝 add docusaurus documentation

Category
Documentation
Overview

Add docs/ directory for Docusaurus documentation
Migrate documentation from Wiki to https://homarr-docs.vercel.app/

Issue Number (if applicable)
none
New Vars (if applicable)
none
Screenshot (if applicable)

Don't forget to click this button 😅😂

) We'll probably want to be self-hosting docosaurus as we've had issues with vercel before (also suggesting docs.ajnart.fr or similar).
) I've made some requested changes where moving a file is necessary, don't forget to change hotlinks to those pages 👀
) Very good job on migrating the entire docs so fast! 🚀

We've tested vercel and it works perfectly. It can only deploy when changes to docs are made and make previews for PRs that modify docs
Other than that I agree

) We'll probably want to be self-hosting docosaurus as we've had issues with vercel before (also suggesting docs.ajnart.fr or similar).
) I've made some requested changes where moving a file is necessary, don't forget to change hotlinks to those pages 👀
) Very good job on migrating the entire docs so fast! 🚀

We've tested vercel and it works perfectly. It can only deploy when changes to docs are made and make previews for PRs that modify docs Other than that I agree

Can we add a custom domain to the vercel instance?

GitHub won't let me batch commit the requested changes 🙄

Sorry to the people that had notifications on for this PR 🤠

Can we make docosaurus use darkmode by default btw?

Btw, won't the docs get added to the docker image?

Btw, won't the docs get added to the docker image?

No, because there is no COPY in Dockerfile

Btw, won't the docs get added to the docker image?

No, because there is no COPY in Dockerfile

I've updated the docker ignore file anyways 🙈

@walkxcode do you want me to squash? Right now we have a mess of changes and commits in history.

@walkxcode do you want me to squash? Right now we have a mess of changes and commits in history.

Squash would be a good idea

@walkxcode do you want me to squash? Right now we have a mess of changes and commits in history.

Squash would be a good idea

Ok, is the original (and first) commit message fine?
Btw; Vercel supports custom domains. Perhaps a subdomain, like https://homarr.ajnart.fr/ would be an idea?

Ok, is the original (and first) commit message fine?

Maybe something like 🚚 Migrate to Docosaurus

Can we get a preview deployment running for this PR?

Just to see if all changes look good.

Vercel actually tried to deploy, but build failed because it detected broken links. I'll fix them and squash all commits later.

Can we get a preview deployment running for this PR?

Now up and running on https://homarr-docs.vercel.app/

Dark mode should not be by default. Please revert this

Why not? It defaults to the devices color scheme now anyways

Can we get a preview deployment running for this PR?

Now up and running on https://homarr-docs.vercel.app/

The getting started link takes mw to a 404

Dark mode should not be by default. Please revert this

Why not? It defaults to the devices color scheme now anyways

Ok that makes more sense

Can we get a preview deployment running for this PR?

Now up and running on https://homarr-docs.vercel.app/

The getting started link takes me to a 404

You must go to the root path, since I renamed the file and the path is now invalid.

Also if someone could edit docs/README.md to explain how to contribute to the docs or set them up locally it would be great

The other changes it'd like to see are :

[ ] Switch to Typescript
[ ]  Yarn install installs all packages for Homarrr and Docs
[ ] Yarn dev:docs stars the docs in dev mode
[ ] Yarn build:docs / yarn start:docs
[ ] There is no version to upgrade for the sub package

note : the yarn commands should work from the root of the project *

The other changes it'd like to see are :
* [ ]  Switch to Typescript

* [ ]   Yarn install installs all packages for Homarrr and Docs

* [ ]  Yarn dev:docs stars the docs in dev mode

* [ ]  Yarn build:docs / yarn start:docs

* [ ]  There is no version to upgrade for the sub package

* note : the yarn commands should work from the root of the project *

All of these are not possible, you have to see docs as a whole different project rooted into Homarr. Most repos use a docs branch just containing docosaurus because of this reason.

The other changes it'd like to see are :

[ ]  Switch to Typescript

[ ]   Yarn install installs all packages for Homarrr and Docs

[ ]  Yarn dev:docs stars the docs in dev mode

[ ]  Yarn build:docs / yarn start:docs

[ ]  There is no version to upgrade for the sub package

note : the yarn commands should work from the root of the project *

Upgrading should be fairly simple. Project is already set up for TS. Simply rename the extension.
Perhaps @walkxcode or @ajnart should do this, because I don't know your coding conventions.

The other changes it'd like to see are :
* [ ]  Switch to Typescript

* [ ]   Yarn install installs all packages for Homarrr and Docs

* [ ]  Yarn dev:docs stars the docs in dev mode

* [ ]  Yarn build:docs / yarn start:docs

* [ ]  There is no version to upgrade for the sub package

* note : the yarn commands should work from the root of the project *

All of these (except TS) are not possible, you have to see docs as a whole different project rooted into Homarr. Most repos use a docs branch just containing docosaurus because of this reason.

The lockfile should tell yarn that it is a separate project, correct?

The other changes it'd like to see are :
* [ ]  Switch to Typescript

* [ ]   Yarn install installs all packages for Homarrr and Docs

* [ ]  Yarn dev:docs stars the docs in dev mode

* [ ]  Yarn build:docs / yarn start:docs

* [ ]  There is no version to upgrade for the sub package

* note : the yarn commands should work from the root of the project *

All of these (except TS) are not possible, you have to see docs as a whole different project rooted into Homarr. Most repos use a docs branch just containing docosaurus because of this reason.

Annoying. Should we do that ?

I think it's a good idea, personally

These changes have been manually added in the docs branch. Communication should continue over discussions or on PR's made to the docs branch.


with npm commands are not working

npm init @open-wc testing
is command not working saying unknown command testing..if i am using command
yarn add @open-wc/testing-karma --dev its installed but in my project i am only using npm.Can you help me in this

the @open-wc  generators changed - pls follow the updated info
https://dev.to/open-wc/testing-workflow-for-web-components-g73#lets-get-started
for more info on the generators see https://open-wc.org/init/
yarn add is the same as npm install so you can just write
npm install @open-wc/testing-karma --save-dev

for a manual way of installing testing see https://open-wc.org/testing/


Explore enabling type acquisition for web TS Server

Follow up on #39707
Overview
We now have TSServer running in web environments, but it is currently limited to single file intellisense. It would be nice if we could also offer some IntelliSense for third party packages that are imported in the current file.
If a user is trying out react for example, we should be able to offer IntelliSense for React and ReactDOM:
//@ts-check

import * as React from 'react';
import * as ReactDOM from 'react-dom';

class HelloMessage extends React.Component {
    render() {
        return (
            <div>
                Hello {this.props.name}
            </div>
        );
    }
}

ReactDOM.render(
    <HelloMessage name="Taylor" />,
    document.getElementById('hello-example')
);

Lots of open questions about how this should behave and potential implementations:

Do we try looking in the user's package.json or at their tsconfig when determining which types to use?

Do we handle packages that bundle their own typings?

How far should type acquisition go? If one type package references another, do we pull that in too?

Would this work differently in JS files vs TS files? Type acquisition works differently for the two on desktop, but on web I think we'd want the behavior to be more similar

Could we use a service like unpkg for this? Or could we stand up a more specialized service that just service up a single types file for a given package?

Can the type acquisition be async like it is on desktop?

Having NPM act as a CDN would

I recently re-wrote the ATA for the Playground ( https://github.com/microsoft/TypeScript-Website/pull/1997 ) what I think is a pretty good conceptual pattern:

TypeScript can probably already give you a list of dependencies it knows about from the package.json, and the source files it has read (in the playground I don't have this, so I use ts.preprocessFile to extract that)
You make an API call which gets a list of all the files in each module tarball (I used jsDelivr's) from which you can figure out the list of .d.ts files you need to download, or that you need to check DT.
If you need to check for @types/module and grab the .d.ts files for that module
Loop through all the downloaded .d.ts files and recurse grabbing their modules etc

It's not exactly like that in practice (you need the version number before you can make that API call to jsdelivr) - but that's good enough and you can read the implementation linked above for more details. The implementation of the TypeScript Playground ATA is built for third parties, so you could be a consumer of @typescript/ata when that PR lands.
An ideal state for VS Code which would keep this entirely first-party, is that the npm registry adds two APIs like:

https://registry.npmjs.org/npm/:version_or_tag/contents which returns some sort of file list
https://registry.npmjs.org/npm/:version_or_tag/file/package.json which returns a CDN'd file from the tarball (in this case the package.json)

Or vscode creates an API which proxies these APIs to jsdelivr (they're real nice folks, I can make an intro if needed)

We are already watching - ping me any time if needed 😄

#46862 Adds a draft implementation of this but I definitely need some help from the TS team to get it into a shippable state

After discussion, we'd like to move the core auto import implementation to VS Code
@orta I looked into using preProcessFile to get all the imports but it looks like this isn't currently exposed over the TSServer protocol? Is that correct?
After thinking about this more, I am also wondering if using preProcessFile is too low level. We can debounce how often we end up calling preProcessFile to avoid calling it on every key stroke, but it feels like it would make more sense if TS could tell us what auto imports it needs and then VS Code could then go and resolve them

@orta @amcasey  I have a basic prototype now running on the VS Code side and can use this to load global typings such as jquery
The problem I'm running into now though is telling TS that jquery in import 'jquery' maps to a given file the VS Code has opened against the TypeScript server
Here's how the files are currently opened after at a has completed (I'm using the paths that TS server sees):
^/memfs/sample-folder/file.js — This is the file that the user has opened up
import * as $ from 'jquery'

Then we have a list of jQuery d.ts files that VS Code has opened up with the correct content:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
All of these are in-memory files so TS Server cannot read them directly. I believe we also have to keep the different scheme (memfs vs ts-typings) as part of the implementation on the VS Code side
What type of API do you think we need to get typescript to understand that import 'jquery' should resolve to<EMAIL_ADDRESS>

There's a similar tension in doing the full TypeScript compile in the ts-vscode playground - I wonder if a reasonable strategy lays in making the TypeScript web server smarter, and keeping some of the file content inside that. As it exists, there is no way to influence what is available to that TSServer:
    function createWebSystem(args: string[]) {
        Debug.assert(ts.sys === undefined);
        const webHost: WebHost = {
            readFile: webPath => {
                const request = new XMLHttpRequest();
                request.open("GET", webPath, /* asynchronous */ false);
                request.send();
                return request.status === 200 ? request.responseText : undefined;
            },
            fileExists: webPath => {
                const request = new XMLHttpRequest();
                request.open("HEAD", webPath, /* asynchronous */ false);
                request.send();
                return request.status === 200;
            },
            writeMessage,
        };

I think somewhere there needs to be a vfs map which the tsserver prioritises for sys lookups for dirs/files and it might need to be insider the web server. That could be controlled via additional tsserver actions/events.

What type of API do you think we need to get typescript to understand that import 'jquery' should resolve to<EMAIL_ADDRESS>
I think that might get tricky with the schema change, I think you'd need to hardcode that somehow into the TS web server code somehow (for examples it is kinda safe that all paths with @types could be treated that way)

My current proposal would be a new TS Server api that let a client explicitly pass global typings files to the TypeScript Server. This could be used both to implement ATA, and also for applications like Office Scripts where you have a VS Code extension that wants to augment the global typings in JS files
Some of this discussion also gets into our discussions around virtual file system support for vscode.dev
One idea: could a client for example tell TS Server about a type root directory and then the server would simply treat any files opened under this directory as typings
From a protocol point of view, this would look something like:

Client passes a root directory for typings to TS Server: configure { typeRoots: ['^/ts-typings'] }

Client then opens files under this types root: updateOpen { path: '^/ts-typings/jquery/jquery.d.ts' }

When resolving imports, the server then looks in the types root.
Since the server only has an in-memory representation of these read files/folders, the server may have to construct its own little virtual file system representation to implement this

(sorry, been a busy few weeks)
I'm not sure that you need to special case the vfs as only being typings specifically, for the playground ATA we emulated having files in<EMAIL_ADDRESS>which meant it was picked up by the default behavior in TypeScript
If you have a generic system to put vfs files into the web tsserver's sys then you can put files into the right place and it would automatically be respected by the rest of the tsserver

Opened #47600 to continue discussion of generic virtual file system support for TS Server. Using this, I believe we could implement ATA by writing the acquired typings to the correct location in the virtual file system

is the intellisense between typescript files also in scope? like will I get intellisense for a hello function declared in a different file when I import it?


Better document StyleGuide's initialization options

It's not clear to the user using pep8 as a library how to replicate pep8's command-line behavior of loading settings from config files like tox.ini.
The doc on advanced usage gives a good start to using pep8 as a library, but more details are hard to come by.
help(pep8.StyleGuide) is also unhelpful:
class StyleGuide(builtins.object)
 |  Initialize a PEP-8 instance with few options.
 |
 |  Methods defined here:
 |
 |  __init__(self, *args, **kwargs)
 |      Initialize self.  See help(type(self)) for accurate signature.

I can't get any variation of help(pep8.StyleGuide) or help(type(...)) to give me an "accurate signature". I think that's because the class doesn't actually offer one.
A few questions:

What is the correct way to initialize StyleGuide so that pep8 loads settings from tox.ini or other config files?
Is there any reason StyleGuide's initialization signature shouldn't be updated to something more documentation-friendly?

For example:
def __init__(
      self,
      checker_class=Checker,
      parse_argv=False,
      config_file=False,
      parser=None,
      *args, **kwargs)

Would it be appropriate to add some additional detail to the advanced usage docs on how to load settings from config files? Users making the transition from command-line to library use will typically be looking for that behavior.

I just realized that this line should probably read:
config_file = kwargs.pop('config_file', None)

It's functionally equivalent to the current line, but better communicates that config_file is a thing and not a flag.

OK, so I figured out that the invocation I'm looking for is this:
pep8.StyleGuide(config_file='tox.ini')

That answers question 1.
I came across a related documentation/discovery problem to what I described for StyleGuide, but this time for BaseReport.
help(pep8.BaseReport) doesn't show all the properties that you would be interested in accessing for a report. For example, if total_errors was not mentioned in passing in this docs, I would not know to access it without reading the source.
The fix in this case is to change BaseReport's declaration:
class BaseReport(object):
    """Collect the results of the checks."""

    print_filename = False
    total_errors = 0
    # Properties here are shown by help().

    def __init__(self, options):
        self._benchmark_keys = options.benchmark_keys
        self._ignore_code = options.ignore_code
        # Results
        self.elapsed = 0
        self.total_errors = 0
        self.counters = dict.fromkeys(self._benchmark_keys, 0)
        self.messages = {}

If all the suggestions provided here sound good, I would be happy to open a PR to implement them.

Partly addressed by #500.


Updated links

Howdy!
I just updated some links to use https instead of http.
Thank you! ^ _ ^

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Have you checked that the sites in question actually works over https?


webpage or its components should not attempt to message an extension directly

In the requestAutoSignin implementation in polaris-web (used by https://github.com/WebOfTrust/signify-browser-extension/blob/909803e6ad0a1038aa8d4ffea914767d98ea2894/example-web/my-app/src/App.js#L74),
https://github.com/WebOfTrust/polaris-web/blob/697eb6ad276fa6c48ed351c6d5be170514a9d333/index.js#L81,
it attempts to contact the extension directly via chrome.runtime.sendMessage().  It should always communicate via the extension's ContentScript.  The webpage and a compliant ContentScript should have a "contract" of message types.  The ContentScript and its Extension (service-worker) must have a completely independent contract of message types and ways of communicating. The web page and polaris-web should know nothing about the latter.  For example, in the case of KERI Auth extension, it will use chrome ports, not messages, and will ignore all messages.

why not have both options? the direct way of communication may be more performance for some use cases.

The performance overhead of forwarding a message is negligible, right?  If an extension service-worker is required to listen to messages from anywhere, it wouldn't know which sources to trust.  The servicw-worker should only be required to listen to messages from its own ContentScript (and the extension's other app content).  The design of an extension shouldn't be otherwise constrained.  The protocol and messages between a page and an extension should only concern the messages (and maybe other content but hopefully not) between the page and the ContentScript.

I'm not sure that the performance is negligible and  you get the benefit of inline response. The service worker only needs to listen to trusted web pages that were authorized by the users. I still don't get your point of restricting messages only from content script. I think that content script exists primarily to allow the service worker to directly interact with the DOM of the web page.

Well, I've stated most of my case already.  Among other things, my implementation for KERI Auth doesn't use messaging, but uses ports, so that means I'd need to change that or not implement AutoSignin until needed.
It is also confusing to me why this interaction for handleRequestAutoSignin is gated depending on result of canCallAsync, which returns true for Brave or Chrome. So, that means another execution path for others like Firefox.  You mentioned "why not have both options?" By that did you mean based on browser type, or a configuration?

that's because chrome implements the externally_connectable feature that allow the service worker to receive messages in a specific listener chrome.runtime.onMessageExternal.addListener

The ideal case is that the user grant permission at runtime as with optional_permissions

See refactoring proposal at https://github.com/WebOfTrust/polaris-web/discussions/31


Failed to resolve: com.github.Ilhasoft:data-binding-validator:1.0.0

Hey there, I found that a same issue has been raised before and he only forgot to add the maven repository link.
I have them both
    maven { url 'https://jitpack.io' }
    maven { url 'https://maven.fabric.io/public' }

Well the problem is I have 2 maven repository.
May I know where do you think the problem is here's my implementation
repositories {
google()
jcenter()
mavenCentral()
maven { url 'https://jitpack.io' }
maven { url 'https://maven.fabric.io/public' }
}
and
implementation 'com.github.Ilhasoft:data-binding-validator:1.0.0'

Cheers!

The build is failing hence why it can't be used: https://jitpack.io/#Ilhasoft/data-binding-validator

ERROR: Failed to resolve: com.github.Ilhasoft:data-binding-validator:1.0.0
I am getting  above error. However earlier my project was running fine.

I think it is because of either upgrading android studio or gradle version. Am still in search of solution.
However Can I use this library by migrating my project to androidX?

@ntn-santos
In Project.gradle
gradle version is
classpath "com.android.tools.build:gradle:3.4.0"
Dependency for Ilhasoft is added like following
def data_binding_validator = [:]
data_binding_validator.core = "com.github.Ilhasoft:data-binding-validator:$versions.arch"
deps.data_binding_validator = data_binding_validator
where version is 1.0.0(also the use of master-SNAPSHOT in place of version did not help)
my compilesdkversion and targetsdkversion is 26
in gradle-wrapper.properties
distributionUrl=https://services.gradle.org/distributions/gradle-5.1.1-all.zip

The version 1.0.0 was rebuilt.
https://jitpack.io/com/github/Ilhasoft/data-binding-validator/1.0.0/build.log

Thank a ton @allancslima  I am able to build my project. :)


Document how to set up an app on your custom domain

We give some instructions in the foo medical docs (https://github.com/medplum/medplum/tree/main/examples/foomedical) on how to setup your application on your own domain, but we have nothing in the public docs.
TBD where this doc will go (either self-hosting or tutorials).
Steps to be shown:

Set up the site settings for a given ClientApplication
Set up your site settings in Google Console (if using google login) and recaptcha
Launching your app on Vercel

Doing this as a tutorial follow up to Medplum Hello World makes sesne

@drdalessandro we would love your support. Do you have any written material that @ksmith94 could refer to when writing the official doc?
Alternatively, if you'd just like to copy any thoughts / wisdom into a comment in this issue, go right ahead! He can use that to inform his document

Link Doc
https://docs.google.com/document/d/1KFY4ABOmZwlDNwG93mmysIXE1fxaqwIRmecTu-jWoAU/edit?usp=sharing

Google Client Id
Google Client Secret

Link Doc
https://docs.google.com/document/d/1YLStxe7DTUdWfPprFe2_NsAjMnRLVl1BZLAOMHiiO5I/edit?usp=sharing

Recaptcha Site Key
Recaptcha Secret Key


src: unit test for create json function

Coverage increased (+1.2%) to 79.841% when pulling<PHONE_NUMBER>a0b388cb0b5da99ce7c3519f458238 on helio-frota:pr into 61a04c3c441a820c2a51521d59ffb1c937b49318 on bucharest-gold:master.


Automation_ACC-264.3 (Level A)Kyma-dashboard_Combo Box Ensure ARIA roles, states, and properties are valid.

1.1 Internal Message Details
Internal Message:
Test Plan:	ACC SAP Kyma runtime 2024
Message Priority:	Medium
Affected Check Point:	ACC-264.3
Affected UI:	Combo Box
Short text:	Automation_ACC-264.3 (Level A)Kyma-dashboard_Combo Box Ensure ARIA roles, states, and properties are valid
1.2 Application Details
Application Name	Kyma-dashboard
Application URL:	https://canary.cockpit.btp.int.sap/cockpit#/globalaccount/7304343e-1ce0-412b-a955-5948bab9d2c8/subaccount/e0ec1134-2770-40a2-910b-2b8e32ec8f60/subaccountoverview
User:	SSO
Technology:	SAP UI5
UI5 Version:	1.124.1
1.3 Test Environment Details:
GitHub	https://github.com/kyma-project/busola/issues
Web browser:	Google Chrome - Version 127.0.6533.73 (Official Build) (64-bit)
Operating System:	Windows 11 Enterprise Version 22H2
Screen Reader:	JAWS 2024.2405.83 ILM 64 bit for Windows
2. Screen Flow
•	Login into the application using the URL provided.
•	URL: https://canary.cockpit.btp.int.sap/cockpit#/globalaccount/7304343e-1ce0-412b-a955-5948bab9d2c8/subaccount/e0ec1134-2770-40a2-910b-2b8e32ec8f60/subaccountoverview.
•	Activate ‘Extension’ item.
•	Activate ‘Create’ button.
3. Issue
Synopsis: Ensure ARIA roles, states, and properties are valid.
Observed Behavior:
‘Resource’ INPUT (role=combobox) field in ‘Extensions’ page, must have all of the following attributes: aria-controls | aria-expanded.
Code Snippet:

Expected Behavior:
Developers must use valid markup and follow the rules of the ARIA specification.

Kindly refer to attached error and issue processing document for more details.
Regards,
Huda

Automation_ACC-264.3 (Level A)Kyma-dashboard_Combo Box Ensure ARIA roles, states, and properties are valid.docx
Issue processing-09.2021 (1).docx


fix the comments in a previous PR

Fix the unsolved comments.
https://github.com/ldbc/finbench-acid/pull/1

fixed


fixes bug 1263146 - Tear-out when using JWPlayer 7

Coverage remained the same at 84.787% when pulling 1f807f7d45a7b2c20dc50c57841172dd91b507db on peterbe:bug-1263146-tear-out-when-using-jwplayer-7 into d7079666e347cf4f4bdb784cd3c5f8d73227ea66 on mozilla:master.


upgrade protobuf-java dependency

Fixes https://github.com/MobilityData/gtfs-realtime-bindings/issues/75

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks @chadselph!


fix: Navbar carets should never appear on a separate line

fixed the alignment issue.webm
fixed the "Navbar carets should never appear on a separate line #369", now everything's working fine.
You can also see in the video.
fixed #369

@erickzhao @erikian @malept @Kilian @molant @VerteDinde @dsanders11 @ckerr @MarshallOfSound @BlackHole1
can anyone give it a review.

@MoazMirza-13, please do not tag maintainers like that, it is not productive. The PR will be reviewed in due time.

Superseded by #530.


Set encoding to utf-8 for windows compatibility

That's not really the right way to fix it, but keeping it open so I can take another crack at it.


Bug when importing

First I install the packages like stated in the examples:
install required packages
!pip install swig
!pip install wrds
!pip install pyportfolioopt
install finrl library
!pip install -q condacolab
import condacolab
condacolab.install()
!apt-get update -y -qq && apt-get install -y -qq cmake libopenmpi-dev python3-dev zlib1g-dev libgl1-mesa-glx swig
!pip install git+https://github.com/AI4Finance-Foundation/FinRL.git
Then I import the packages:
import pandas as pd
import numpy as np
import matplotlib
import matplotlib.pyplot as plt
matplotlib.use('Agg')
import datetime
%matplotlib inline
from finrl.meta.preprocessor.yahoodownloader import YahooDownloader
from finrl.meta.preprocessor.preprocessors import FeatureEngineer, data_split
from finrl.meta.env_stock_trading.env_stocktrading import StockTradingEnv
from finrl.agents.stablebaselines3.models import DRLAgent
from stable_baselines3.common.logger import configure
from finrl.meta.data_processor import DataProcessor
from finrl.plot import backtest_stats, backtest_plot, get_daily_return, get_baseline
from pprint import pprint
import sys
sys.path.append("../FinRL")
import itertools
However, since today I get the following error:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/IPython/core/interactiveshell.py", line 3553, in run_code
exec(code_obj, self.user_global_ns, self.user_ns)
File "", line 9, in <cell line: 9>
from finrl.plot import backtest_stats, backtest_plot, get_daily_return, get_baseline
File "/usr/local/lib/python3.10/site-packages/finrl/init.py", line 5, in
from finrl.train import train
File "/usr/local/lib/python3.10/site-packages/finrl/train.py", line 10, in
from finrl.meta.data_processor import DataProcessor
File "/usr/local/lib/python3.10/site-packages/finrl/meta/data_processor.py", line 8, in
from finrl.meta.data_processors.processor_yahoofinance import (
File "/usr/local/lib/python3.10/site-packages/finrl/meta/data_processors/processor_yahoofinance.py", line 21, in
import yfinance as yf
File "/usr/local/lib/python3.10/site-packages/yfinance/init.py", line 23, in
from .ticker import Ticker
File "/usr/local/lib/python3.10/site-packages/yfinance/ticker.py", line 28, in
from .base import TickerBase
File "/usr/local/lib/python3.10/site-packages/yfinance/base.py", line 40, in
from .scrapers.history import PriceHistory
File "/usr/local/lib/python3.10/site-packages/yfinance/scrapers/history.py", line 1207
logger.debug(f'price-repair-split: Splits: {str(df['Stock Splits'][split_f].to_dict())}')
^
SyntaxError: f-string: unmatched '['
You get this error for almost all packages I import from the finrl library. Has there been an update?

I have the same issue ..


Adding resolving logic to abstract types

There are abstract types in GraphQL:

GraphQLInterfaceType
GraphQLUnionType

I suggest discussing which option (there are two options for implementation) is preferable and whether I took everything into account when adding this method.
Existing solutions
Webonyx
namespace GraphQL\Type\Definition;

interface AbstractType
{
    public function resolveType($objectValue, $context, ResolveInfo $info);
}

Digiaonline
namespace Digia\GraphQL\Type\Definition;

interface AbstractTypeInterface
/// ...some other methods
    public function resolveType(...$args);
    public function hasResolveTypeCallback(): bool;
}

Youshido
namespace Youshido\GraphQL\Type;

interface AbstractInterfaceTypeInterface
{
    public function resolveType($object);
}

Result
namespace GraphQL\Contracts\TypeSystem\Type;

interface AbstractTypeInterface extends NamedTypeInterface
{
    public function resolveType($objectValue, $context, ...$args): ?NamedTypeInterface;
}

Youshido will need to add $context, otherwise the interface is fully compatible.
Digiaonline will require combining the two methods into one, where null will mean the absence of a resolver method.

Some notes

Because the implementation of ResolveInfo class is different for everyone, it was decided to make the third argument arbitrary. It will suit every decision.
The method should return an object or interface type (https://github.com/graphql/graphql-js/pull/2084) therefore, it was decided to specify the NamedTypeInterface common interface as a return typehint.

Alternative solution
namespace GraphQL\Contracts\TypeSystem\Type;

interface AbstractTypeInterface extends NamedTypeInterface
{
    public function resolveType($objectValue, ...$args): ?NamedTypeInterface;
}

Removing the second argument will simplify integration into Youshido.

I thought a lot about it and I think that the type system at the moment should be done by analogy with the SDL representation.
Since SDL does not contain absolutely any logic responsible for type resolving, so interfaces should not contain it either:
union Example =
    | ObjectType
    | AnotherObjectType

In those cases when some separate implementations are required - it makes sense to implement the factory (as example):
$dto = new ExampleType(...); // Implementation of GraphQL Contracts

$interface = InterfaceType::create($dto, function ($value) {
    // resolve type
});

// Or like this

$scalar = ScalarType::create($dto, [
    'parse' => function () { ... },
    'parseLiteral' => function () { ... },
    'serialize' => function () { ... }
]);

Now this, I think, will be enough.
@Jalle19 What do you think?


basestring and python3

Look at what fonttools does.

Note: this happened in the tests, just be sure to use:
from fontTools.misc.py23 import basestring
in tests

Fixed in: https://github.com/robofab-developers/fontParts/commit/f98d750aa6e2167b31e079cbe1ccd788885f436b


ZeroPal is down.

It seems that ZeroPal is down.

Hello, the repair will be completed in the next few weeks. Thank you for your attention!

Hello, the previous issue occurred because our OpenAI API key exceeded the usage limit, which caused access problems. We have now updated the key for the base model, and access is functioning normally. Thank you for your attention!

Great! Closing the issue :)


CI for Node

Sets the current player to be whoever it is not
Starts the game with a random player
Initializes with two players

Sets the current player to be whoever it is not
Starts the game with a random player
Initializes with two players


webm-wasm missing video duration

Description
After installing and setting webm-wasm as the video engine, recorded video missing duration. Is there a way to set this with options [ or any other solutions in general ] ?
Input #0, matroska,webm, from '.\calibration_ff_rt.webm':
  Metadata:
    encoder         : libwebm-<IP_ADDRESS> but in wasm
  Duration: N/A, start: 0.000000, bitrate: N/A
  Stream #0:0(eng): Video: vp8, yuv420p(progressive), 640x480, SAR 1:1 DAR 4:3, 20 fps, 20 tbr, 1k tbn (default)

recorder options are:
plugins: {
      record: {
          audio: false,
          video: { frameRate: { ideal: 20, max: 30 }, width: 640, height: 480, facingMode: 'user' },
          videoEngine: 'webm-wasm',
          videoWorkerURL: 'webm-worker.js',
          videoWebAssemblyURL: 'webm-wasm.wasm',
          videoBitRate: 1200,
          videoFrameRate: 20,
          debug: true,
          frameWidth: width,
          frameHeight: height,
          convertEngine: 'ts-ebml',
          autoMuteDevice: true,
      }
  }

Additional Information
versions
"ts-ebml": "^2.0.2",
"video.js": "^7.5.4",
"videojs-record": "^4.3.0",
"webm-wasm": "^0.4.1",

browsers
Firefox, Chrome

I don't think using a combination of a video and convert plugin in the same application is supported, it's been a while but I don't think I ever tested it.
When only using the webm-wasm plugin, does it properly inject the duration?

no feedback, closing.


Proper authentication

[x] Some way to sign up, ideally not just a single oauth provider and ideally something we can connect to ticket purchases. Bonus points if it's PlayFab, still bonus points if it's Azure, extra bonus points if I don't need to roll my own
[x] Lock down HTTP endpoints based on authentication. If you want to do private actions based on your account (e.g. set your profile info), we should know it's you based on authentication

See https://docs.microsoft.com/en-us/azure/azure-signalr/signalr-tutorial-authenticate-azure-functions.
As long as we're okay with only third-party providers (I'm thinking Twitter + Google + maybe MS), everything will Just Work™, including authing all Functions calls, and doesn't require any custom code.

This 100% works!
...with the caveat that we currently only support Twitter auth. Opening up more issues for little things.


libp2p faster than light again

Fix for thix exists in ipfs-webui v2.16.0, which updated geoip dataset, but we are unable to switch to latest webui because of this bug: https://github.com/ipfs/ipfs-webui/issues/1984

This should no longer be an issue, and we've updated to the latest webui a while ago


Missing properties

I just moved from flutter_contact_picker package and I'm missing multiple properties:

@erperejildo Please share more detail
flutter version, plugin version, and error.

I'm no longer using this package


Change refs prop to ref

React default is ref, not refs.

It is a breaking change, so please move the release accordingly with semver.org.


WIP: Angular 6 support

Fixes #1384

I think you should also migrate calls to Observable.create into new Observable()
https://github.com/ReactiveX/rxjs/issues/3635

Any updates on this? Benefits of upgrading the package are huge

Hopefully the build is green. Then I have to make some tests. When all tests passes, we're ready to go

Argh, build failing.... I better switch to ts-loader

Ok, build is green. I'll check the compatibility now

Seems to work fine with Angular 5 but the dynamic importstatement does not work for snazzy-info-window. There's also an unresolved CLI issue: https://github.com/angular/angular-cli/issues/9825

what about dummy check
if(elems[0].default) {   this._nativeSnazzyInfoWindow = new elems[0].default(options); } else {   this._nativeSnazzyInfoWindow = new elems[0](options); }

@john-hi this doesn't solve the issue completely. I think the best way is to create a script tag on the page (if it does not exist yet)

Have no more time today. Will try to solve it tomorrow and rollout the new releases for all packages.

Ok, we'll use require for now as this is the only working option for all situations

OK, all test are passing. Will be compatible with Angular 5 and 6


Fix basempuri

Summary
Fixes template copying which before caused all images to contain the same information.

rebase when other PRs are merged

@orviz it seems the jenkins is still running out of free space: https://jenkins.egi.ifca.es/blue/organizations/jenkins/Pipeline-as-Code%2Fcloud-info-provider/detail/PR-132/2/pipeline#step-18-log-105
Is this related to the build itself or is it due to some other concurent stuff?


Add stop method in PinotLLCRealtimeSegmentManager

Commit segment metadata happens in 3 zk updates 1) consuming segment metadata update 2) new segment metadata creation 3) ideal state update. If the controller shuts down after 1 and before 3, we will end up in a state where the partition will not consume. The validation manager will fix this when it runs (currently runs every 1 hour), but this delay might not be acceptable for certain scenarios.
Adding a stop method to the PinotLLCRealtimeSegmentManager, which will wait 30 seconds before stopping. This time will allow any segment metadata commits which were in progress, to complete. We will also prevent any new segment metadata commits once the shutdown has been invoked.

Codecov Report

Merging #3591 into master will increase coverage by 0.01%.
The diff coverage is 77.77%.

@@             Coverage Diff              @@
##             master    #3591      +/-   ##
============================================
+ Coverage     70.86%   70.88%   +0.01%
  Complexity        4        4
============================================
  Files          1009     1009
  Lines         46255    46264       +9
  Branches       6209     6209
============================================
+ Hits          32780    32795      +15
+ Misses        11315    11295      -20
- Partials       2160     2174      +14

Impacted Files
Coverage Δ
Complexity Δ

...m/linkedin/pinot/controller/ControllerStarter.java
62.28% <100%> (+0.43%)
0 <0> (ø)
:arrow_down:

.../core/realtime/PinotLLCRealtimeSegmentManager.java
73.05% <71.42%> (-0.02%)
0 <0> (ø)

...a/manager/realtime/RealtimeSegmentDataManager.java
75% <0%> (-25%)
0% <0%> (ø)

...e/impl/dictionary/LongOnHeapMutableDictionary.java
82.22% <0%> (-13.34%)
0% <0%> (ø)

...impl/dictionary/DoubleOnHeapMutableDictionary.java
68.88% <0%> (-13.34%)
0% <0%> (ø)

...m/linkedin/pinot/broker/queryquota/HitCounter.java
92.3% <0%> (-7.7%)
0% <0%> (ø)

...kedin/pinot/core/util/SortedRangeIntersection.java
83.82% <0%> (-7.36%)
0% <0%> (ø)

...impl/dictionary/FloatOffHeapMutableDictionary.java
87.27% <0%> (-5.46%)
0% <0%> (ø)

...e/operator/dociditerators/SortedDocIdIterator.java
54.05% <0%> (-5.41%)
0% <0%> (ø)

...mpl/dictionary/DoubleOffHeapMutableDictionary.java
74.54% <0%> (-3.64%)
0% <0%> (ø)

... and 24 more

Continue to review full report at Codecov.

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


Reduce Metrics/MethodLength Max to 14

Several method extractions and some minor cleanup.
Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] All tests are passing.
[x] The new code doesn't generate RuboCop offenses.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.

Out of curiosity, is there an end goal number for the Metrics improvements that have been going on?

@rrosenblum Personally I've kept the RuboCop defaults in config/default.yml as the targets but I don't know if we're ever going to reach them. While interesting, it takes increasingly more time and gives less benefit as we're getting closer.


Slave-only spot instances

Flintrock supports launching clusters using spot instances. However, when doing so, all the cluster instances are launched as spot instances.
 You want it to stick around even if various slaves are dropped so that your job can still chug along (though at a slower pace) and so that you can re-add slaves to the cluster at a later time.
We should change our support for launching clusters on spot instances such that only the slaves are spot instances.
This work (kinda) depends on #16.

@nchammas would this solve the problem that occurs when launching a spot instance cluster and one of the nodes ends up getting terminated which ends in the launch command just hanging forever? Or should I submit a new issue for that case?

@engrean - Have you seen this issue since d5b086c81952aaf78dd7febfedc6b424e63e3697 made it in? Flintrock should now immediately error out as soon as a spot request fails.
You'll need to be running on master to get this fix.

Would love to have this feature. It would be great to be able to specify a different instance type for the master as well.

Would it make sense to separate the add-slaves logic from launch? In other words, the workflow would be to create a master instance only first and then add all the slaves of any type you want to it with a second call.

Seconding the "would love this feature", and even more so, being able to specify different master and slave instance types.

@nchammas is there any progress on this?

@mblack20 - Nope. The current workaround, I believe, is to launch a regular cluster with no slaves, and then add spot slaves separately using add-slaves.


add name to ActiveRelationTrait

it usable for operation with relation as object
example:
public function __construct($relation, $relationName)
{
    $this->relation = $relation;
    $this->relationName = $relationName;
    ...
}
public function init()
{
    $this->relationName
    ...
}

vs
public function __construct($relation)
{
    $this->relation = $relation;
...
}
public function init()
{
    $this->relation->name
    ...
}

relation should have name, when inverseOff not required?

@lynicidn Can this be closed?


Enable finer control of who may, or may not, read repositories

Our company makes use of external contractors from time to time who require access to our GitBlit instance. Regrettably we are only able to remove their read permissions from unrelated repositories on a per-repository basis (i.e., we have to exclude them from each repository in turn. There are many!)
GitBlit seems to ignore the Team- or User-level X (exclude) permissions when it comes to read access.

This is a non-issue. Closing as the affected repositories were not set up with the correct access policy.


Compatibility with NEO4J 4.0.4 enterprise

I can't connect to my neo4j 4.0.4 enterprise server .
It works with python's driver.
I had trace connection process and it freeze in socket.connect .
Do you have any idea about this compatibility.
Client on Mac OSX: 10.15 , Theo 5.0.0 ,  xcode 11.5 , swift 5

Hi, you are right, the master branch only supports up to Neo4j 3.x. I was alerted to this around three week ago (if memory serves) and have been working on a new branch, dev/bolt-v3. In short, Neo4j 4.x has dropped support for Bolt v1 and v2, requiring v3 or v4. The "spec" I have, though, is the Python implementation, and that one has me confused at the moment. I'll get in touch with the driver team with my questions so we can get some progress on that again. If by chance you're interested in giving it a hand, I'd be very grateful for the help :-)

Hi, I've just pushed an version to the dev/non-blocking branch, that together with the dev/bolt-v3 branch of Bolt-swift connect well to 4.0.x and 4.1.x. If you have the ability to check it out already, that'd be awesome. If not, it should percolate to the release version soon.

Thanks for this great project.
I have the same problem (cannot connect) to the neo4j community 4.1.0 using BoltClient.
Works well with 3.5.19. Couldn't get the SPM to accept (through xcode) the "dev/bolt-v3" of Bolt-swift.
So look forward to the new release.

@workingDog Have you tried the branch mentioned above?

I'm using xcode 12-beta, macos 10.15.5, target mac catalyst app. Using xcode to load repos.
I first load https://github.com/Neo4j-Swift/Bolt-swift.git branch: dev/bolt-v3.
That is accepted by xcode.
I get the following error when loading
https://github.com/Neo4j-Swift/Neo4j-Swift.git branch: dev/non-blocking
package 'Neo4j-Swift' is required using a revision-based requirement and it depends on local package 'Bolt-swift', which is not supported
So I could not test the setup.

Voila, I just updated Theo to version 5.2, should have fixed those dependencies. Would you mind trying it out?

thanks for these new library versions. Unfortunately I could not connect to Neo4j Community Edition 4.1.0 server.
I have created a test at:
https://github.com/workingDog/NeoTest
The test works well with the new version of Neo4j-Swift-5.2.0 and Bolt-swift-5.2.0 on server neo4j-3.5.19, but not on neo4j-4.1.0.
I cannot understand why, any ideas?

Running your code on Xcode12-beta2 gave me:
---> NeoTester init boltClient is: Optional(Theo.BoltClient)
---> NeoTester trying to connect ...
-------------------> connected <-------------------
-----------------> is connected
So my guess is that your Neo4j 4 instance isn’t configured to allow Bolt with SSL.
Have you set
dbms.connector.bolt.listen_address=<IP_ADDRESS>:7687
?
Also, for good measure, try <IP_ADDRESS> instead of localhost, that forces IPv4. I didn’t have the opportunity to test your project with IPv6.
If that is all in place and still failing, look over the SSL part of the Bolt configuration in Neo4j settings
Cheers
Niklas

On 15 Jul 2020, at 03.09, workingDog<EMAIL_ADDRESS>wrote:
thanks for these new library versions. Unfortunately I could not connect to Neo4j Community Edition 4.1.0 server.
I have created a test at:
https://github.com/workingDog/NeoTest https://github.com/workingDog/NeoTest
The test works well with the new version of Neo4j-Swift-5.2.0 and Bolt-swift-5.2.0 on server neo4j-3.5.19, but not on neo4j-4.1.0.
I cannot understand why, any ideas?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/Neo4j-Swift/Neo4j-Swift/issues/7#issuecomment-658488017, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABATZ3VQ3RZ2I53CPIMXN3R3T6TTANCNFSM4NNGYV2A.

Niklas,
thanks for your reply. I'm glad the test can work, however it does not for me, even after I tried your recommended settings. It must be the configs, but there are a lot of them, and I cannot find the ones that I need to switch on or off or default or whatever.
The problem could be in the way I install neo4j. This is what I do:
I install a fresh copy of neo4j in a directory, and set the path to it in my .zprofile/.bash_profile. Start neo4j using "neo4j console". All seems good at that stage.
I use the browser on localhost:7474 and change the password. I use that password in the test app.
I don't understand how to set the ssl thing, it seems very complicated.
Is there something I'm missing, something else I need to do?

Hi,
so by default Neo4j 3.x came with encryption out-of-the-box whereas in 4.x you need to configure it yourself. 5.2.0 assumed you had configured it. I've created a branch for 5.2.1 https://github.com/Neo4j-Swift/Neo4j-Swift/tree/dev/5.2.1 which makes it easier to select encryption as either non-encrypted, encrypted with self-signed certificate (like in 3.x), encrypted with self-signed certificate but having the key to verify it with, and encrypted with a certificate signed by a root authority. I've so far tested the unencrypted and self-signed versions, would you mind trying out the unencrypted one and see if it suits you?
Having it available, though, I still would recommend using an encrypted connection in most cases
Cheers
Niklas

Hi Niklas,
thanks for all your efforts. I've tested the dev/5.2.1 branch with "encryption: .unencrypted" and it works so well.
After all the troubles I've had, to see it work like this is great. Thanks again.
Ringo

On Jul 21, 2020, at 6:44, Niklas Saers<EMAIL_ADDRESS>wrote:
Hi,
so by default Neo4j 3.x came with encryption out-of-the-box whereas in 4.x you need to configure it yourself. 5.2.0 assumed you had configured it. I've created a branch for 5.2.1 https://github.com/Neo4j-Swift/Neo4j-Swift/tree/dev/5.2.1 https://github.com/Neo4j-Swift/Neo4j-Swift/tree/dev/5.2.1 which makes it easier to select encryption as either non-encrypted, encrypted with self-signed certificate (like in 3.x), encrypted with self-signed certificate but having the key to verify it with, and encrypted with a certificate signed by a root authority. I've so far tested the unencrypted and self-signed versions, would you mind trying out the unencrypted one and see if it suits you?
Having it available, though, I still would recommend using an encrypted connection in most cases
Cheers
Niklas
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Neo4j-Swift/Neo4j-Swift/issues/7#issuecomment-661349513, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZ6GDBAKZCW75TBWYWL263R4S3DZANCNFSM4NNGYV2A.

Wonderful :-)


undefined field 'tags'

Thanks for the info. tags was missing in the type definition. I added them to the latest release.


Use upstream ManagedBass packages again and update to 3.1.0

Fulfills the second point in https://github.com/ppy/osu-framework/issues/4677 ("Testing of new bass library version")

Also resolves visible ManagedBass reference conflicts in iOS projects:

Tested this update to work on macOS and iOS, would appreciate testing on other platforms just in case.

Tested linux briefly, looks to work, although again, I haven't tested very much.

Tested on windows, looks to work correctly.


Labels behind the points in a Scatter chart

I noticed something was up with my Scatter plot in my react project, and I was wondering if it was possible to remove the data values behind the actual points themselves? I haven't been able to find an answer or anyone with the same issue.

const state = {
datasets:[
{
label: "S11 Polar Graph",
pointBackgroundColor: '#ffffff',
pointBorderWidth: 1,
pointHoverRadius: 5,
pointRadius: 3,
pointHitRadius: 10,
data: [
{ x: 5, y: 6 },
{ x: 6, y: 8 },
{ x: 4, y: 5 },
{ x: 2, y: 9 },
{ x: 1, y: 3 },
]
}
]
}

<Scatter
data={state}
options={{
maintainAspectRatio: true,
}}
/>

I'm gonna close this issue now, since I found a way around the issue, by using Chartjs-plugin-datalabels. By using Formatter, then I can force the label to be " " so as to display nothing.


Image size

Hi there, great plugin, thanks for the work.
Is there a way to specify image size (widthXheight)?
thanks in advance

That's not a part of CM spec. You can try to search third party plugins.

Duplicate of #80


fix checksum bug

Looks like this was causing a checksum error. If I'm understanding this correctly, this reads a correct checksum if that missing bit is zero, and an incorrect checksum if that bit is one.

Thanks!


Error on run: Could not find files for the given pattern(s)

Description
I have pulled the most recent and I do see six lines of this error when I do the npm run start:
INFO: Could not find files for the given pattern(s).
INFO: Could not find files for the given pattern(s).
INFO: Could not find files for the given pattern(s).
INFO: Could not find files for the given pattern(s).
INFO: Could not find files for the given pattern(s).
INFO: Could not find files for the given pattern(s).
Screenshot attached.

https://github.com/jef/nvidia-snatcher/issues/191

Whooops!!! Sorry. This is a real error. Going to work on fix now. Thanks!

Thanks.

I would let it run a little longer as well, because EVGA is pretty slow right now.

If your problem is now could not find files for given patterns, this is most definitely a duplicate and has been resolved through other issues.
https://github.com/jef/nvidia-snatcher/issues/191

I'm sorry to bother you, but I have this error log too, I'm trying my best to see how it was resolved.

Hi! For me it was missing a notification.mo3 file in the root folder of the
bot. I believe the latest version now has one included, try pulling the
latest release.
On Sat, Sep 26, 2020 at 10:24 PM rambosbff<EMAIL_ADDRESS>wrote:

I'm sorry to bother you, but I have this error log too, I'm trying my best
to see how it was resolved.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jef/nvidia-snatcher/issues/246#issuecomment-699587791,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZN74YOWQCFJ7VSFLOON73SH3D7FANCNFSM4RXNYKIQ
.

Hi! For me it was missing a notification.mo3 file in the root folder of the bot. I believe the latest version now has one included, try pulling the latest release.
…
On Sat, Sep 26, 2020 at 10:24 PM rambosbff @.***> wrote: I'm sorry to bother you, but I have this error log too, I'm trying my best to see how it was resolved. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#246 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZN74YOWQCFJ7VSFLOON73SH3D7FANCNFSM4RXNYKIQ .

Thanks for your help, I really appreciate it. I'm still trying to figure stuff out. Do you mean pull from the main, or the 1.5 release?

No wait! Sorry my reply was thinking of a different bot. For
nVidia-snatcher you need to add the no3 file yourself.
Or, you can go to
https://github.com/Hari-Nagarajan/nvidia-bot, grab the notify.more from
there and rename it for nVidia-snatcher.
I was trying nvidia-bot because it has support for auto-purchase for
Amazon, but so far no luck. This one is sort of dangerous because right now
you can’t set a limit, so if a scalper lists a 3080 for $3000 or other
ridiculous price, of the model you set it to look for. the bot in theory
will buy it.
On Sat, Sep 26, 2020 at 10:30 PM rambosbff<EMAIL_ADDRESS>wrote:

Hi! For me it was missing a notification.mo3 file in the root folder of
the bot. I believe the latest version now has one included, try pulling the
latest release.
… <#m_7120256572567778415_>
On Sat, Sep 26, 2020 at 10:24 PM rambosbff @.***> wrote: I'm sorry to
bother you, but I have this error log too, I'm trying my best to see how it
was resolved. — You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#246 (comment)
https://github.com/jef/nvidia-snatcher/issues/246#issuecomment-699587791>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZN74YOWQCFJ7VSFLOON73SH3D7FANCNFSM4RXNYKIQ
.
Thanks for your help, I really appreciate it. I'm still trying to figure
stuff out. Do you mean pull from the main, or the 1.5 release?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jef/nvidia-snatcher/issues/246#issuecomment-699588268,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZN745SFBICOKJN6CO56HTSH3EXJANCNFSM4RXNYKIQ
.

Okay and another thing I had to do for nvidia-snatcher is, it doesn't come
with an actual command-line .mp3 player, so I also had to install
mplayer.exe in the root. I grabbed my copy from here:
https://sourceforge.net/projects/mplayerwin/files/MPlayer-MEncoder/r38151/mplayer-svn-38151-x86_64.7z/download
On Sat, Sep 26, 2020 at 10:43 PM Ryan<EMAIL_ADDRESS>wrote:

No wait! Sorry my reply was thinking of a different bot. For
nVidia-snatcher you need to add the no3 file yourself.
Or, you can go to
https://github.com/Hari-Nagarajan/nvidia-bot, grab the notify.more from
there and rename it for nVidia-snatcher.
I was trying nvidia-bot because it has support for auto-purchase for
Amazon, but so far no luck. This one is sort of dangerous because right now
you can’t set a limit, so if a scalper lists a 3080 for $3000 or other
ridiculous price, of the model you set it to look for. the bot in theory
will buy it.
On Sat, Sep 26, 2020 at 10:30 PM rambosbff<EMAIL_ADDRESS>wrote:

Hi! For me it was missing a notification.mo3 file in the root folder of
the bot. I believe the latest version now has one included, try pulling the
latest release. Definitely practice all cautionary steps and virus scan the
downloaded file off virustotal.com or your local scanner, but so far I
haven't had any issues with it.
… <#m_-5161789460240895530_m_7120256572567778415_>
On Sat, Sep 26, 2020 at 10:24 PM rambosbff @.***> wrote: I'm sorry to
bother you, but I have this error log too, I'm trying my best to see how it
was resolved. — You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#246 (comment)
https://github.com/jef/nvidia-snatcher/issues/246#issuecomment-699587791>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZN74YOWQCFJ7VSFLOON73SH3D7FANCNFSM4RXNYKIQ
.
Thanks for your help, I really appreciate it. I'm still trying to figure
stuff out. Do you mean pull from the main, or the 1.5 release?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jef/nvidia-snatcher/issues/246#issuecomment-699588268,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZN745SFBICOKJN6CO56HTSH3EXJANCNFSM4RXNYKIQ
.

So my folder looks like this:
[image: image.png]
The notification.mp3 I grabbed notify.mp3 from the nvidia-bot repo, and
renamed it to notification.mp3 and dropped it in this folder. Then I
downloaded that mplayer archive and just copied mplayer.exe to the
nvidia-snatcher folder also. I think it automatically creates that mplayer
folder when it first runs.
Keep in mind if you don't care for audio notifications on your PC, and
assuming nothing else is wrong/missing then those errors you see can be
considered purely cosmetic.
On Sat, Sep 26, 2020 at 10:51 PM Ryan<EMAIL_ADDRESS>wrote:

Okay and another thing I had to do for nvidia-snatcher is, it doesn't come
with an actual command-line .mp3 player, so I also had to install
mplayer.exe in the root. I grabbed my copy from here:
https://sourceforge.net/projects/mplayerwin/files/MPlayer-MEncoder/r38151/mplayer-svn-38151-x86_64.7z/download
On Sat, Sep 26, 2020 at 10:43 PM Ryan<EMAIL_ADDRESS>wrote:

No wait! Sorry my reply was thinking of a different bot. For
nVidia-snatcher you need to add the no3 file yourself.
Or, you can go to
https://github.com/Hari-Nagarajan/nvidia-bot, grab the notify.more from
there and rename it for nVidia-snatcher.
I was trying nvidia-bot because it has support for auto-purchase for
Amazon, but so far no luck. This one is sort of dangerous because right now
you can’t set a limit, so if a scalper lists a 3080 for $3000 or other
ridiculous price, of the model you set it to look for. the bot in theory
will buy it.
On Sat, Sep 26, 2020 at 10:30 PM rambosbff<EMAIL_ADDRESS>wrote:

Hi! For me it was missing a notification.mo3 file in the root folder of
the bot. I believe the latest version now has one included, try pulling the
latest release. Definitely practice all cautionary steps and virus scan the
downloaded file off virustotal.com or your local scanner, but so far I
haven't had any issues with it.
…
<#m_-6327372175595081243_m_-5161789460240895530_m_7120256572567778415_>
On Sat, Sep 26, 2020 at 10:24 PM rambosbff @.***> wrote: I'm sorry to
bother you, but I have this error log too, I'm trying my best to see how it
was resolved. — You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#246 (comment)
https://github.com/jef/nvidia-snatcher/issues/246#issuecomment-699587791>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZN74YOWQCFJ7VSFLOON73SH3D7FANCNFSM4RXNYKIQ
.
Thanks for your help, I really appreciate it. I'm still trying to figure
stuff out. Do you mean pull from the main, or the 1.5 release?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jef/nvidia-snatcher/issues/246#issuecomment-699588268,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZN745SFBICOKJN6CO56HTSH3EXJANCNFSM4RXNYKIQ
.

Thank you man, it was the sound that was causing the issue. I downloaded from you link and that fixed it. Yeah, I was just tired of seeing the errors and wanted the sound haha. The files from the wiki here didn't work, but your solution did, so thank you much! I'll have to check out that other bot, but instabuying scalped cards is not ideal,  heh.

No problem, glad you got it working! I guess we should be glad we haven't
snagged a card yet, now with this SP-CAP vs MLCC drama is showing that the
ASUS TUF/STRIX and EVGA (all) cards don't have crashing issues, we can
avoid the other ones for now. Who knows how it will all fall out. Odds are
the cards with the "suboptimal design" will get a firmware update to limit
how high they can boost/overclock to prevent the crashes.
I actually haven't had much luck with any of these bots either. The
farthest I got was they'd throw one into a cart for me, then I won't be
able to check out for an hour until they remove it from my cart because
they went Out Of Stock.
Best of luck to you, I hope you get one!
On Sun, Sep 27, 2020 at 12:07 AM rambosbff<EMAIL_ADDRESS>wrote:

Thank you man, it was the sound that was causing the issue. I downloaded
from you link and that fixed it. Yeah, I was just tired of seeing the
errors and wanted the sound haha. The files from the wiki here didn't work,
but your solution did, so thank you much! I'll have to check out that other
bot, but instabuying scalped cards is not ideal, heh.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jef/nvidia-snatcher/issues/246#issuecomment-699595911,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZN745PMXB2H476VHYJ66TSH3QCFANCNFSM4RXNYKIQ
.


Desktop View

I created the following:

A navbar section of the desktop view with media queries
A project section
An about me section with a footer

@danmainah Please I do not understand the "whitespace issue" you are referring to as my project is not overflowing.

@danmainah Please I do not understand the "whitespace issue" you are referring to as my project is not overflowing.

Kindly check the image below, it outlines the section requested by the previous reviewer which still exist

Thank you,
It has been fixed.


New version: sigoden.Dufs version 0.40.0

Created by 🥟 Dumplings in Run #3371.
Microsoft Reviewers: Open in CodeFlow

Hi @SpecterShell,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 729.)

Automatic Validation ended with:

Installation failed with exit code -1978335187 2024-02-12 22:54:05.594 [FAIL] Installer failed security check. Url: https://github.com/sigoden/dufs/releases/download/v0.40.0/dufs-v0.40.0-x86_64-pc-windows-msvc.zip Result: 0x80004005 MSI (s) (20:D8) [22:53:53:365]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X64 Minimum Runtime - 14.38.33135. Product Version: 14.38.33135. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. MSI (s) (20:68) [22:53:54:474]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.38.33135. Product Version: 14.38.33135. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. [0A3C:0AB0][2024-02-12T22:53:51]w363: Could not create system restore point, error: 0x80070422. Continuing... Installation failed with exit code -1978334972

(Automated response - build 729.)

@wingetbot run

Hi @SpecterShell,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 757.)

Automatic Validation ended with:

Installation failed with exit code -1978335187 2024-02-15 10:21:49.441 [FAIL] Installer failed security check. Url: https://github.com/OpenGMK/GM8Decompiler/releases/download/v2.2.0/gm8decompiler-v2.2.0-x86_64-pc-windows-msvc.zip Result: 0x80004005 MSI (s) (8C:14) [10:21:39:176]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X64 Minimum Runtime - 14.38.33135. Product Version: 14.38.33135. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. MSI (s) (8C:10) [10:21:40:005]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.38.33135. Product Version: 14.38.33135. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. [1EF8:1654][2024-02-15T10:21:37]w363: Could not create system restore point, error: 0x80070422. Continuing... 2024-02-15 10:21:24.674 [FAIL] Installer failed security check. Url: https://github.com/OpenGMK/GM8Decompiler/releases/download/v2.2.0/gm8decompiler-v2.2.0-i686-pc-windows-msvc.zip Result: 0x80004005 MSI (s) (BC:14) [10:21:11:132]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Minimum Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. MSI (s) (BC:78) [10:21:11:898]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Additional Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. [1DE8:1DAC][2024-02-15T10:21:09]w363: Could not create system restore point, error: 0x80070422. Continuing...

(Automated response - build 757.)

@wingetbot run

Automatic Validation ended with:

2024-02-19 13:13:54.998 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.015 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.031 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.053 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.143 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.169 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.256 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.276 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.296 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.376 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.398 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.486 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.563 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.637 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.662 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.686 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.709 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.729 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.750 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.826 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.848 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.873 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.896 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.919 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.941 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.966 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:55.986 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:56.014 [CLI ] Installer [X64,burn,Machine,en-US] not applicable: Machine is not compatible with X64 2024-02-19 13:13:56.106 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:56.126 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:56.204 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:56.227 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:13:56.227 [CLI ] Terminating context: 0x8a150010 at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8 2024-02-19 13:14:01.649 [CLI ] Installer [X64,portable,Unknown,] not applicable: Machine is not compatible with X64 2024-02-19 13:14:01.649 [CLI ] Installer [Arm64,portable,Unknown,] not applicable: Machine is not compatible with Arm64 2024-02-19 13:14:03.403 [CLI ] Installer [X64,burn,Machine,] not applicable: Machine is not compatible with X64 2024-02-19 13:14:03.404 [CLI ] No suitable installer found for manifest Microsoft.VCRedist.2015+.x64 with version 14.38.33135.0 2024-02-19 13:14:03.404 [CLI ] Terminating context: 0x8a150104 at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\DependenciesFlow.cpp:11a

(Automated response - build 788.)

No suitable installer found for manifest Microsoft.VCRedist.2015+.x64 with version 14.38.33135.0

This appears to be a dependency mismatch.

[Policy] Needs-Author-Feedback


Remove space make Sub-Process to small

See screencast:

(My screen capturing tool placed the mouse at the wrong position)

There are a few options here.

Prevent removing space entirely if layout would break
Only prevent removing space from subprocesses of which layout would break
Not preventing resize but instead adding an orange preview like the one that other shapes have that would visualize that the layout is going to break

What is the behaviour you would expect?
In general making the space tool smarter would also make it less predictable. Right now you can break the layout using the space tool in various ways like

If we fix the issue regarding the layout of subprocesses being broken but don't fix other issues too the space tool will become more and more unpredictable. At the end it's a question of how smart we expect the user to be and how smart the user expects the space tool to be. Do we allow literally everything and expect the user to know what he's doing or do we prevent the user from breaking something from the beginning even he may know what he's doing.

We decided that we're definitely going to add a preview for resizing using the space tool since this feature should exist regardless of this ticket. I've created a ticket for this: https://github.com/bpmn-io/bpmn-js/issues/586

We won't do anything here any time soon. As part of the next Camunda Modeler release we improved the space-tool resize preview instead. This should give users a bit more assistance.

That's fine with me, since any heuristic will never be perfect. The
preview is already very helpful for such situations.

Closing this for now as we did substantial improvements on the preview.


[FLINK-19247][docs-zh] Update Chinese documentation after removal of Kafka 0.10 and 0.11

What is the purpose of the change
Update Chinese documentation after removal of Kafka 0.10 and 0.11.
Brief change log

Update Chinese documentation according to FLINK-19152.
Make the Chinese documentation to keep sync with the newest Apache Kafka Connector documentation.

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

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

Documentation

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

Hi, @klion26
This PR is ready to be reviewed. Could you help to review it at your convenience?
Thanks~

Hi, @klion26
Thanks for your good suggestions !
I have make some changes according to your advice. Please take a look.

Hi, @klion26 .
I have made changes according to your advice. Please take a look.
Thanks~


Cannot get token on Version 0.6.17

I am getting the cannot get token error while setting up google-drive-ocamlfuse. Attached is the debug log.
[0.000661] TID=0: Setting up default filesystem... [0.000702] TID=0: BEGIN: Saving configuration in /home/zhehao/.gdfuse/default/config [0.000962] TID=0: END: Saving configuration in /home/zhehao/.gdfuse/default/config [0.001067] TID=0: Loading application state from /home/zhehao/.gdfuse/default/state...done Current version: 0.6.17 Setting up cache db...done Setting up CURL...done [0.002298] TID=0: BEGIN: Saving application state in /home/zhehao/.gdfuse/default/state [0.002514] TID=0: END: Saving application state in /home/zhehao/.gdfuse/default/state [0.002570] TID=0: BEGIN: Starting web browser with command: xdg-open "https://accounts.google.com/o/oauth2/auth?client_id=564921029129.apps.googleusercontent.com&redirect_uri=https%3A%2F%2Fgd-ocaml-auth.appspot.com%2Foauth2callback&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fdrive&response_type=code&access_type=offline&approval_prompt=force&state=MgcPL7s8s8fznXWB4sYmhbbD0xjab1hPPmFzBmxrbzE" [0.029791] TID=0: END: Starting web browser with command: xdg-open "https://accounts.google.com/o/oauth2/auth?client_id=564921029129.apps.googleusercontent.com&redirect_uri=https%3A%2F%2Fgd-ocaml-auth.appspot.com%2Foauth2callback&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fdrive&response_type=code&access_type=offline&approval_prompt=force&state=MgcPL7s8s8fznXWB4sYmhbbD0xjab1hPPmFzBmxrbzE" [0.029806] TID=0: BEGIN: Getting tokens from GAE proxy [0.588758] TID=0: END: gettokens not found, retrying [0.597427] TID=0: Retrying (1/8) get_tokens after exception: Not_found [2.567434] TID=0: END: gettokens not found, retrying [2.591650] TID=0: Retrying (2/8) get_tokens after exception: Not_found [5.264531] TID=0: END: gettokens not found, retrying [5.288209] TID=0: Retrying (3/8) get_tokens after exception: Not_found [10.624207] TID=0: END: gettokens not found, retrying [10.635929] TID=0: Retrying (4/8) get_tokens after exception: Not_found [19.636252] TID=0: END: gettokens not found, retrying [19.660904] TID=0: Retrying (5/8) get_tokens after exception: Not_found [36.430270] TID=0: END: gettokens not found, retrying [36.442370] TID=0: Retrying (6/8) get_tokens after exception: Not_found [69.198998] TID=0: END: gettokens not found, retrying [69.223379] TID=0: Retrying (7/8) get_tokens after exception: Not_found [134.019448] TID=0: END: gettokens not found, retrying [134.043263] TID=0: Retrying (8/8) get_tokens after exception: Not_found [263.120114] TID=0: END: gettokens not found, retrying [263.144411] TID=0: Error during get_tokens after 8 attempts: Not_found

You should have authorized the application in the web page that should have been opened. If not please retry (if it still doesn't work, please remove the content of your ~/.gdfuse/default directory).

I've run into the same problem, web page says, "Cannot get authorization tokens, please try again." rm -rf ~/.gdfuse/default is accordingly joyless.

I checked the logs of the oauth endpoint. From about 2 am to 3 am of February 11, there are several exceptions like this one type=InternalTransientError message=Temporary error in fetching URL: https://accounts.google.com/o/oauth2/token. It looks like it was a Google temporary error.


TestEventsContainerFilterBeforeCreate

From #20526 https://jenkins.dockerproject.org/job/Docker-PRs-experimental/15218/console
01:40:53 ----------------------------------------------------------------------
01:40:53 FAIL: docker_cli_events_unix_test.go:125: DockerSuite.TestEventsContainerFilterBeforeCreate
01:40:53
01:40:53 docker_cli_events_unix_test.go:152:
01:40:53     c.Assert(out, checker.Contains, cID, check.Commentf("Missing event of container (foo)"))
01:40:53 ... obtained string = "" +
01:40:53 ...     "2016-02-20T01:40:29.587977244Z container create a9af1eda63b3b20240c46ccb4760454189f0c9e53b8e797209b42fd4580da20d (image=busybox, name=foo)\n" +
01:40:53 ...     "2016-02-20T01:40:29.633116042Z container start a9af1eda63b3b20240c46ccb4760454189f0c9e53b8e797209b42fd4580da20d (image=busybox, name=foo)\n" +
01:40:53 ...     "2016-02-20T01:40:29.926971940Z container kill a9af1eda63b3b20240c46ccb4760454189f0c9e53b8e797209b42fd4580da20d (image=busybox, name=foo)\n" +
01:40:53 ...     "2016-02-20T01:40:29.954202675Z container die a9af1eda63b3b20240c46ccb4760454189f0c9e53b8e797209b42fd4580da20d (image=busybox, name=foo)\n" +
01:40:53 ...     "2016-02-20T01:40:30.064539462Z container destroy a9af1eda63b3b20240c46ccb4760454189f0c9e53b8e797209b42fd4580da20d (image=busybox, name=foo)\n"
01:40:53 ... substring string = "af77ab8d69cd5267b64aac268c332c50c6bb0ef30ba3602410384e237379685f"
01:40:53 ... Missing event of container (foo)
01:40:53
01:40:55
01:40:55 ----------------------------------------------------------------------

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see CONTRIBUTING.md.
You don't have to include this information if this is a feature request
(This is an automated, informational response)

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

This test works fine on my 1.11 docker build. Anyone else seeing this test failing?


Upgrading flask package loses transitive dependencies

Upgrading flask package removes also transitive dependencies.
Environment Versions

OS Type: KDE Neon (Ubuntu 18.04)
Python version: 3.7.2
pip version:  19.1.1
pip-tools version: 3.8.0

Steps to replicate
$ echo "flask==0.12.2" > requirements.in
$ pip-compile --no-header --no-index
click==7.0                # via flask
flask==0.12.2
itsdangerous==1.1.0       # via flask
jinja2==2.10.1            # via flask
markupsafe==1.1.1         # via jinja2
werkzeug==0.15.4          # via flask
$ echo "flask" > requirements.in
$ pip-compile --no-header --no-index -P flask
flask==1.0.3

So... upgrading flask package removed all transitive dependencies (for that package). 1.0.3 version still depends on Jinja2 etc so they should be there.
Doesn't happen always, for example:
$ echo "pylint==2.0.0" > requirements.in
$ pip-compile --no-header --no-index
astroid==2.2.5            # via pylint
isort==4.3.20             # via pylint
lazy-object-proxy==1.4.1  # via astroid
mccabe==0.6.1             # via pylint
pylint==2.0.0
six==1.12.0               # via astroid
typed-ast==1.4.0          # via astroid
wrapt==1.11.2             # via astroid
$ echo "pylint" > requirements.in
$ pip-compile --no-header --no-index -P pylint
astroid==2.2.5            # via pylint
isort==4.3.20             # via pylint
lazy-object-proxy==1.4.1  # via astroid
mccabe==0.6.1             # via pylint
pylint==2.3.1
six==1.12.0               # via astroid
typed-ast==1.4.0          # via astroid
wrapt==1.11.2             # via astroid

Here, pylint upgrades and transitive dependencies are kept just fine.

Actually, looks like flask>=1.0.0 changed something as transitive dependencies never resolve via pip-compile:
$ echo "flask==0.12.4" > requirements.in
$ pip-compile --no-header --no-index
click==7.0                # via flask
flask==0.12.4
itsdangerous==1.1.0       # via flask
jinja2==2.10.1            # via flask
markupsafe==1.1.1         # via jinja2
werkzeug==0.15.4          # via flask
$ rm requirements.txt
$ echo "flask==1.0.0" > requirements.in
$ pip-compile --no-header --no-index
flask==1.0.0

If you just pip install flask==1.0.0 it installs transitive dependencies just fine:
...
Successfully installed Jinja2-2.10.1 MarkupSafe-1.1.1 Werkzeug-0.15.4 click-7.0 flask-1.0 itsdangerous-1.1.0

Hello @tuukkamustonen,
Thanks for the report! I've tried to repeat the bug with the flask locally, but i couldn't confirm it. I'd suggest to try pip-compile --rebuild at first. Also would be nice to attach a log from pip-compile --verbose command.

@atugushev --rebuild fixed the issue, thanks! Unfortunately, I ran it first, before doing --verbose, so the details on the faulty run are now lost :|
Anyway, what does it mean? Corrupted data? How did I end up with such?

@tuukkamustonen

Anyway, what does it mean? Corrupted data? How did I end up with such?

Yes that's because the cache was somehow corrupted. Can't tell for sure why was that happened.  Probably by unknown bug.


[Issue]: llama-index-core (0.10.65) depends on nltk (>=3.8.2) and tenacity (>=8.2.0,<8.4.0 || >8.4.0,<9.0.0)

Is there an existing issue for this?

[ ] I have searched the existing issues
[ ] I have checked #657 to validate if my issue is covered by community support

Describe the issue
Because no versions of graphrag match >0.2.1,<0.2.2 || >0.2.2,<0.3.0
and graphrag (0.2.1) depends on nltk (3.8.1), graphrag (>=0.2.1,<0.2.2 || >0.2.2,<0.3.0) requires nltk (3.8.1).
And because graphrag (0.2.2) depends on tenacity (>=9.0.0,<10.0.0)
and llama-index-core (0.10.65) depends on nltk (>=3.8.2), if graphrag (>=0.2.1,<0.3.0) and llama-index-core (0.10.65) then tenacity (>=9.0.0,<10.0.0).
And because llama-index-core (0.10.65) depends on tenacity (>=8.2.0,<8.4.0 || >8.4.0,<9.0.0)
and no versions of llama-index-core match >0.10.65,<0.11.0, graphrag (>=0.2.1,<0.3.0) is incompatible with llama-index-core (>=0.10.65,<0.11.0).
Steps to reproduce
No response
GraphRAG Config Used
# Paste your config here

Logs and screenshots
No response
Additional Information

GraphRAG Version: v0.2.2 v0.3.0
Operating System: MACOS
Python Version: 3.11
Related Issues:

Thanks for the issue! I have the same issue with langchain.


Required manual select components do not expand

Hi,
I have copied-pasted the manual select component into my code.
Adding required="true" to it prevents it to expand.
<x-bladewind::select name="gender" placeholder="Select Gender" data="manual">
     <x-bladewind::select-item label="Male" value="male" />
     <x-bladewind::select-item label="Female" value="female" />
     <x-bladewind::select-item label="Prefer not to say" value="other" />
</x-bladewind::select>
<x-bladewind::select name="gender" required="true" placeholder="Select Gender" data="manual">
     <x-bladewind::select-item label="Male" value="male" />
     <x-bladewind::select-item label="Female" value="female" />
     <x-bladewind::select-item label="Prefer not to say" value="other" />
</x-bladewind::select>

The first one works, the second does not.
Any way to fix this?

@BeBel42
If you have two selects with the same name in the same page, the second will not work.
However, if you only provided the two select codes to make your point, I'll look into this and fix.

@BeBel42 Can you try making this dynamic let me know if it works?
<?php
$gender = [
    [ 'label' => 'Male','value' => 'male' ],
    [ 'label' => 'Female','value' => 'female' ],
    [ 'label' => 'Prefer not to say',       'value' => 'other' ],
];
?>

<x-bladewind::select name="gender" :data="$gender" />

Hi,
I apologize. The two names being the same was indeed the issue.
So it's a mistake on my part for this one :sweat:
I'll close the issue. Again, sorry for the false alert.


Update 04-sdk-connect.md

The final code snippet does not compile
Module: 04
Lab/Demo: 04
Fixes:

The code snippet does not compile, using lines should be all together, should be:

using System;
using System.Linq;
using Microsoft.Azure.Cosmos;

I just tried this out with a blank line and couldn't reproduce your issue.
using System;
using System.Linq;

using Microsoft.Azure.Cosmos;

Console.WriteLine("Testing!");

// Emulator credentials
string endpoint = "https://localhost:8081";
string key = "C2y6yDjf5/R+ob0N8A7Cgv30VRDJIWEHLM+4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw/Jw==";

CosmosClient client = new (endpoint, key);

AccountProperties props = await client.ReadAccountAsync();

Console.WriteLine($"Identifier:\t{props.Id}");

I tested this in the /learn module using .NET version 6.0.100.
It was able to compile successfully.

@seesharprun I tested this inside the Lab VM that is provisioned, the error description was from there (as you can see in the error path) and the content of the file was the suggestion (I copy/pasted the entire content). The only way for the error to go away was to remove the line between the using statements.

That's super weird. I have seen that error before when the project has using statements and no actual executable lines of code. For a top-level statement[s] (script) app, it cannot compile with just using statements since the compiler doesn't know where to start the Main method, it needs at least one statement that can be executed.

@seesharprun  I ran the lab again just to make sure and I get the error:

If I remove the line inbetween using:

From the screenshot, you can see it is the same Lab machine, same folder (the one for this snippet, 04-sdk-connect)
Code with dotnet build error:
using System;
using System.Linq;

using Microsoft.Azure.Cosmos;

string endpoint = "<cosmos-endpoint>";
string key = "<cosmos-key>";

CosmosClient client = new (endpoint, key);

AccountProperties account = await client.ReadAccountAsync();

Console.WriteLine($"Account Name:\t{account.Id}");
Console.WriteLine($"Primary Region:\t{account.WritableRegions.FirstOrDefault()?.Name}");

Code that builds:
using System;
using System.Linq;
using Microsoft.Azure.Cosmos;

string endpoint = "<cosmos-endpoint>";
string key = "<cosmos-key>";

CosmosClient client = new (endpoint, key);

AccountProperties account = await client.ReadAccountAsync();

Console.WriteLine($"Account Name:\t{account.Id}");
Console.WriteLine($"Primary Region:\t{account.WritableRegions.FirstOrDefault()?.Name}");

I think the problem is when the code is pasted from the Instructions, I was able to repro only when doing that. If I manually type the entire code, then it does not happen. I don't know if it's because of some line break?

Since the repro is very flimsy, I will close the issue. It could be because of a line break character

I still think tracking that copying the code creates line breaks is a worthwhile endeavor. Would it be better as an issue?
We had some wonky stuff go on when testing the labs around line breaks when copied from the LODS interface.