Testing changes before merging

Opening this as a issue for visibility and to discuss the current process and perhaps find actionable improvements.
I would like to understand what is the current process for merging changes to this repo and what measures are in place to verify the changes before they affect people working on other repos that depend on the Jenkins jobs.
In the last couple of weeks I've seen errors in merge jobs of openshift-ansible:

introduction of a job (tox) that didn't install all dependencies and failed
job tries to run a file that doesn't exist, because of changes in the branch structure (https://github.com/openshift/origin/issues/13833)
others that I did not keep record

Since bugs here affect a number of developers and PRs, I believe it is worth having a process to reduce the risk of human errors.

I assume you are talking about the sjb/ jobs. The current process is manual and described in #201. When we move to a Jenkinsfile process (eta: one or two sprints) we have aim to introduce a process. This is not a simple problem to solve but it is clearly on our radar and I don't think you'll find anyone who disagrees that a process would be helpful.

@stevekuznetsov thanks. We're on the same team/boat/whatever-we-call it. Understanding that yes this is already in the radar, with the best open source intentions, I'd like to bring the discussion upstream. This way we have more transparency and allow for contribution from a broader audience.
I meant the repo as a whole, not only jobs that affect openshift-ansible.
From #201:

In order to test a job, it is necessary to copy a configuation file under sjb/config/ to a new YAML file with a different name, then re-generate XML and use sjb/push-update.sh to push only the test job up to the server. Cleanup of these jobs post-test is still manual.

While other PRs merge quite fast, I wonder why is this still open? It's hard for someone landing on the repo homepage to figure out there will be some docs coming up in a PR :)
Assuming those steps are being followed (though I haven't seen e.g. a link to a successful job execution in the PRs I've seen here), have anyone done a post-mortem analysis to understand why the recent bugs were introduced?
Is there any initial plan for the 'inception', automating the verification of changes to this repo itself?

While other PRs merge quite fast, I wonder why is this still open? It's hard for someone landing on the repo homepage to figure out there will be some docs coming up in a PR :)

Sorry, now I see it was created only 38 min ago.

While other PRs merge quite fast, I wonder why is this still open? It's hard for someone landing on the repo homepage to figure out there will be some docs coming up in a PR :)

I made this in the morning and I don't think Justin has been in yet to look at it.

Assuming those steps are being followed (though I haven't seen e.g. a link to a successful job execution in the PRs I've seen here), have anyone done a post-mortem analysis to understand why the recent bugs were introduced?

Yes, it's a mix of the process not being followed, being followed poorly, differences between "test" jobs and "real" jobs (when something has been tested in isolation but broke in the middle of a larger job) or simple mistakes or oversight.

Is there any initial plan for the 'inception', automating the verification of changes to this repo itself?

It is a tricky question. From my understanding, no current system supports testing for the CI underpinnings. Historically Origin and AOS have not had a suite of tests for many of the tools that underpin the CI and definitely not for the jobs. I was actually the first to add or attempt to add automated or semi-automated testing to tools like test-pull-requests and vagrant-openshift.
From what I can tell, there is not really a first-class concept of testing in the JJB sphere either, other than simply running verification steps to ensure that the syntax has been followed. Even in the Groovy Jenkins pipeline/library ecosystem on large projects there is no CI.
It's just not a very common thing to do, testing the libraries that underpin CI.
I don't think it will be reasonable to have per-PR CI on the changes that make it into the job definitions, therefore. Instead, we will feed two servers with our jobs. Changes land in master branch and go live immediately on a testing server that mirrors some small representative portion of the workload hitting the production service and we promote changes into other branches (versioned with the branch of origin/openshift-ansible they support, so like integration, staging, enterprise-3.5, etc) once they have proven themselves in the test master.

@rhcarvalho @stevekuznetsov would you guys be ok if I close this issue? Is so old, a lot has changed since then (i guess)


Remove python upper-bound

This is not needed, as Python doesn't follow SemVer, and breaks users using ipynbname with other package managers, like poetry. See also https://twitter.com/codewithanthony/status/1362181541191766017
Cheers!

Will release update this weekend


📎 Update Getting Started docs to clarify local installation usage

We recommend that Rome be installed locally with npm install rome or yarn add rome.
We should clarify that people will need to run rome commands prefixed with npx or yarn if they don't have node_modules/.bin in their PATH. (e.g. npx rome init or yarn rome init)

Can I take this up?

Definitely @SanketDG! Please feel free to submit an associated pull request and we'll be sure to get it reviewed quickly.

I don't if this is necessarily a good first task. If we're going to recommend the usage of npx rome init then we also need to install it locally to package.json which would be a non-trivial amount of work to support.

then we also need to install it locally to package.json

Would there be any reasons to enforce this?

I was struggling to find the right place to put this so I just checked out how create-react-app does it. Can we do something like this in our Getting Started?
Let me know what you guys think.

I wonder if we can provide a command that creates a file that can run rome with the shebang? Kinda like we are doing at the moment internally inside our repo.

My opinion is that we should still recommend people install Rome with npm install rome or yarn add rome and then npx rome <command> or yarn rome <command> will just use the rome in node_modules without installing anything new.
While it's technically possible to have npx rome init also install Rome into a project on its own, I'm not in favor of it.

Automatically installing is the behaviour of create-react-app and other generators. My fear is that it wont be obvious to many that rome has not actually been installed and that it's running in a magic cache somewhere that isn't fixed to a specific version. This also means it wont work with LSP out of the box unless we can find it locally.
The only reason we need to recommend npx is because it seems that a significant amount of people do not have node_modules/.bin in their $PATH, which is something I thought nvm and the Windows installer do for you already, but I guess there are many ways to install Node. In an ideal world, the installation instructions would just be:
npm install rome
rome init

Which is what we currently have in the docs. If we change them to use npx then it's still the same amount of commands:
npx rome init
npm install rome

We could ideally make it a single command that needed to be ran:
npx rome init

The only thing we'd need to do is when running rome init, we check if you have rome in your package.json dependencies, if you do not, then we add it for you with the same version that is used by npx rome.
This would reduce it to a single command, we wouldn't need to explain the intricacies of how npx works and when you need to run the install command. And we wouldn't do anything if you decided to locally install it and then invoke rome init yourself so it would just support both.

The only thing we'd need to do is when running rome init, we check if you have rome in your package.json dependencies, if you do not, then we add it for you with the same version that is used by npx rome.

Sounds good to me!
Do we reach a consensus here so that I can start working on this?

The only reason we need to recommend npx is because it seems that a significant amount of people do not have node_modules/.bin in their $PATH, which is something I thought nvm and the Windows installer do for you already, but I guess there are many ways to install Node.

As far as I know, nvm, n and the installer add node_modules/.bin to the global $PATH but only for packages that will be installed globally (when using npm install -g). We suggest to install rome locally to a project (or set of projects), the only way to run is using a npx or yarn.
npx, when run inside a project that has a package.json, will try to run the binary inside project/node_modules/.bin. If not there, it will download the package and run the command. (as we already know).

The only thing we'd need to do is when running rome init, we check if you have rome in your package.json dependencies, if you do not, then we add it for you with the same version that is used by npx rome.

I like this proposal!

I thought I had already put up a PR but I have the automatic installation implemented in a branch.

I also have seem to put up a PR, do I continue on this?

Merged #1135 which when ran in a folder with package.json that doesn't have rome specified as a dependency, will add it, and if a yarn.lock or package-lock.json exists, will run it.
Neither open PRs address how we would actually want to document this new behaviour.
If you are using npm, all you need to do is run:
npx rome init

And if you're using yarn:
yarn add rome
yarn rome init

Then any future commands would use one of either:
npx rome check
yarn rome check

@SanketDG will you send a PR?


Mirror https://invent.kde.org/packaging/yocto-meta-kf5.git

It's on GH too: https://github.com/KDE/yocto-meta-kf5


Several references found to deprecated helm/charts repo

Describe the bug
The weave-gitops codebase makes a couple references to the helm/charts repository. This repository is deprecated. The canonical source for Helm charts is the Artifact Hub.
I would simply offer this as a fix, however you all might want to point somewhere else. So, this is just a docs Issue. 🙂
Environment
n/a
To Reproduce
https://github.com/weaveworks/weave-gitops/search?q="https%3A%2F%2Fgithub.com%2Fhelm%2Fcharts"
Expected behavior
Links reflect currently maintained repositories for Helm charts.
Actual Behavior
Links reflect deprecated previous repository for Helm charts.
Additional Context (screenshots, logs, etc)
I think that's it. 🙂

Thanks for the fix!


Please add NTK

It seems impossible to sign a transaction offline for a token (eg NTK) that is not already in the list of default tokens?
ie "add a custom token" and "send offline" cant be combined?
If so, can you please  add NTK as a default token asap, as I want to move it (offline).
Many thanks in Advance.
https://etherscan.io/token/0x69beab403438253f13b6e92db91f7fb849258263

#59

Thank you

@Azarielle  @dec1
You're going to want to follow our instructions here to get this added as a default token: https://support.mycrypto.com/tokens/token-creators-add-your-token-to-mycrypto.html
We pull from the ethereum-lists repository ( https://github.com/ethereum-lists/tokens/ ) to get our tokens now. Let me know if you need any help :)

I dont get it. It seems the pull request was merged into the master branch on Mar 26
https://github.com/MyCryptoHQ/mycrypto.com/pull/59/files
And the current release (apparently 12 days old)  is 3.15.0 according to
https://github.com/MyCryptoHQ/mycrypto.com/releases.
And https://mycrypto.com/   reports the version to be 3.15.1
So why isnt NTK in the current release if it was merged into master before the release?
(And why does mycrypto.com release version differ from github?)


1.20.2

It appears that 'minecraft-data' and 'minecraft-protocol' do not yet support version 1.20.2.
https://github.com/PrismarineJS/minecraft-data/issues/779
https://github.com/PrismarineJS/node-minecraft-protocol/issues/1258

What about now?


fix display of units in repr html

Subunits were displayed as string in rich html disply of Jupyter. Changed to display lists as one-column table. Make whole unit display a <details> for more compactness

@GRPlan FYI


Update for Foundry latest version

Hello,
Do you plan on updating this module for the latests FoundryVTT versions ? I'm actually on version 0.8.9 and I think v9 is the actual up-to-date version. Thank you

Well i tryed updating it myself, but i never developped anything for foundry, plus switching from v6 to v9 is to big of a gap for me


Add Seoul Cyber University

Website: www.iscu.ac.kr

@limitless Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


Model update

Major version bump. WIP
breaking changes

namespaces are now enforced more strictly
models now only accept a single argument
the namespace key was introduced inside of models (was prior the leading
string in models)
namespaced models can now only operate within themselves
state.location is now namespaced under state.app.location

Additions

a whole lotta docs

Closes #4

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

Merging [#8][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master         #8   diff @@
==========================================
  Files             1          1
  Lines            88         88
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits             42         42
  Misses           46         46
  Partials          0          0

Powered by Codecov. Last updated by [23a104c...61f6236][cc-compare]
[cc-base-branch]: https://codecov.io/gh/yoshuawuyts/choo/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/yoshuawuyts/choo/compare/23a104cd7e43077280a6c3223b2f8357044ac784...61f6236c465a6711c507ee17dd577c5ff9ca3241
[cc-pull]: https://codecov.io/gh/yoshuawuyts/choo/pull/8?src=pr

Damn it, looks like the "http" example falls through - incorrect "http" responses must be able to set an "error" property somewhere to signal something went wrong - that breaks the whole idea of namespaces.
So I think what's best is if reducers and state only operate within the local namespace, but any type of action can be called. Bit more complex, but necessary. Should update the docs to discourage heavy cross-domain action calling though.

We could of course special case the "error" keyword, but I don't wanna mess with peoples naming schemes - don't wanna tread into frameworkism land haha

Welp, all examples work and I don't think there are any holes in the new namespacing code. Work is done, here. Merging!


Hello, can you provide the ASOCA dataset?

I am interested in this challenge, but i got nothing from the organizer. It would be greatly helpful if you can provide the dataset. My email is<EMAIL_ADDRESS>

please reach out to the data organizers. I'm not allowed to share datasets.


ReSharper 2016.1 - incompatible?!

Installed the new version of ReSharper (2016.1) and tried to use the plugin but nothing happens.
At the moment I am using VS 2013.
Could it be that this plugin is not compatible with the new version of ReSharper?

same problem with VS 2015 and R# 2016.01

ReSharper_SilentCleanupCode has to be changed to ReSharper.ReSharper_SilentCleanupCode
...that's all

where do you do this changes? (ReSharper_SilentCleanupCode)

ReSharper.AutoFormatOnSavePackage.cs line 47

oh okay i haven't viewd the source code yet, just installed the extension

I just issued a pull request( #21 ) that solved the issue with Resharper 2016.1 and is still compatible with the previous versions

@PombeirP: Any update on this?

The new 1.2.4 version should fix it.

It works for me, thanks!


Temperature Sensor Aggregation is not working right

I currently only have 1 sensor in each location that has temperature. Every single one of the aggregation sensors is showing way higher than it should.
Examples would be
livingroom:

kitchen:

I have the 1.1.0 version installed

Might be related to calcius to farenheit conversion, can you check for that?

Might be related to Celsius to Fahrenheit conversion, can you check for that?

Not sure how I would check that. Home assistant shows both as Fahrenheit as shown in the images above.
On that note it looks like the aggregation temp is converting my Fahrenheit temp as if it is Celsius to Fahrenheit as if it is Celsius, At least that is what math shows, but I have no idea how to figure out why Magic Areas is doing that.

May be a duplicate, look at closed issues.

It might be the same issue as a closed one, since it looks the same, but not sure how it would be a home assistant thing. Although not sure how it all works, so I guess it is possible.
https://github.com/jseidl/hass-magic_areas/issues/9

I was just looking through some things. Does the aggregat sensor not set a Type of temperature? Another words it does not set it as F or C. If that is the case it looks like there is a chance Home Assistant converts it. Pasted a link below to something that could be the answer, but not a way to fix it.
https://github.com/home-assistant/core/issues/29595#issuecomment-562984205

This is a weird issue since Magic Areas does set the unit_of_measurement property to the same of the sensors it reads from. Can you see on developer tools if unit_of_measurement is set?

Not sure what you mean by developer tools.

It's on the UI menu. Where you can see all the information about an entity. https://www.home-assistant.io/docs/tools/dev-tools/

Yeah, I checked it shows it set to F also, so I am not sure where this is all happening, but the problem is I don't know what is going on in the backend. All I can see is the final result that is shown in HA, so even though it shows as F in HA that is because HA converts everything to F, so looking at the value in the Dev tool actually doesn't help.
Thanks, for an idea on something to check.

Also seeing this issue. Could be related to #53? I suspect Deconz is doing some unit conversion under the hood and may lead to problems similar to not following customize. I've notice that some of my sensors were showing up in history graphs as Celsius despite the unit_of_measurement showing Farenheight in developer tools.

Also seeing this issue. Could be related to #53? I suspect Deconz is doing some unit conversion under the hood and may lead to problems similar to not following customize. I've notice that some of my sensors were showing up in history graphs as Celsius despite the unit_of_measurement showing Farenheight in developer tools.

That could be related.

That could be related.

Possibly being fixed with the rework on #74. Will circle back after 2.0.0 is out to see if this is actually fixed.

Possibly being fixed with the rework on #74. Will circle back after 2.0.0 is out to see if this is actually fixed.

Possibly fixed by #74, released on 2.0.0.
Please test it out and let me know if that solves it

Possibly fixed by #74, released on 2.0.0.
Please test it out and let me know if that solves it

This does appear to work fine now. I have 2.0.4 installed


Remove the screenshot with "Restore Files" option

In "Steps" section, the first screenshot shows the option "Restore Files" while this is option is not available yet (roadmap). This brings confusion and customers think they have something wrong in their ANF backup settings since they only have the option "Restore to new volume". Please remove this screenshot and replace by another one showing what is currently available: "Restore to new volume" and "Delete".

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

ID: 94fc9233-406c-0d19-b88e-c060169f6f5e
Version Independent ID: 9185bf79-8080-7aad-6864-156947b3d374
Content: Restore a backup to a new Azure NetApp Files volume
Content Source: articles/azure-netapp-files/backup-restore-new-volume.md
Service: azure-netapp-files
GitHub Login: @b-hchen
Microsoft Alias: anfdocs

Thanks @y-halim -- We are consulting our technical stakeholders about this issue.

Thank you.
Issue fixed in https://github.com/MicrosoftDocs/azure-docs-pr/pull/256012
#please-close


example needed for multiMatch searchableType query

Which Category is your question related to?
graphQl
Amplify CLI Version
3.15
What AWS Services are you utilizing?
dynamo,  cognito,  elastasearch  s3
Provide additional details e.g. code snippets
I cannot get a multiMatch query to work.   I have tried:
const filterDescriptionBrand = {multiMatch:{query: searchString, fields: ["description", "brand", "category", "scanCode"]}};
and
const filterDescriptionBrand = {multiMatch:{query: searchString, fields: "description brand category scanCode"}};
Both return values but no filtering occurs
Item aws-amplify/amplify-cli#970 also asks thios question but was closed with no answer

This seems to be coming from 2019:  https://github.com/aws-amplify/amplify-cli/issues/970
It would be really nice to update documentation.

As best I can tell multiMatch does not work at all.  Which is fine (I can do "or" queries to get the same result), but perhaps it should be removed from the docs?


Suggestion Backlog Slog, 2/29/2016

Leap Day Edition :tada:

Typing Work

#7156 Library include directives
#7125 UMD module definitions

Salsa-supporting work

#6992 Use smarter type fallbacks in error cases

Suggestions

#7279 Trailing commas in argument lists
#7209 Add a "force strict mode" option
#7077 Duplicate identifiers in namespace emit
#7011 Apply interface types to implicit-any-declared class properties
#6864 Disallow implicitly duplicated enum values
#185 Non-nullable: confirm that this is committed?
#471 Permit an implementing class to ignore private methods of the implementee class
#3812 Type guards on property access
#6758 Allow --name=value commandline switch format
#7256 Disallow void in truthyness positions
#7071 require of .json file
#6808 Start a deprecation path for module

Library include (#7156)

Two folders called “library” only one has a .d.ts, use that
What if we found two different files for the same declaration file (e.g. node v2),
We should show an error if both have dependency on the same library but the files are different
It should be an error when importing a package with ///?
Modules should not use /// <reference path=“..” /> or ///<reference library=”..” />
Add the compiler library folder to the search path,  e.g. ///<reference library=”es6.promise.d.ts” />
Should I specify the path, or just the name of the library?
The library name seems much better
Guidance for package authors:
What about typing dependencies for a package
Ship package without types, and ship a @typings\package separately
Ship types with package, and add “dependencies” on all your typings dependencies

UMD (#7125)

More bike shedding  :bike: :house:  on the syntax, #7125
new syntax options:
export as namespace $;

The rest: out of :clock11:


Branch 162842890

Investigating GPU build failure: https://ci.tensorflow.org/job/tensorflow-pull-requests-gpu/5878/

@tensorflow-jenkins test this please

@tensorflow-jenkins test this please

@tensorflow-jenkins test this please


[Firefox addon] Stop bundling src/core/network.js into the FIREFOX/MOXCENTRAL builds (PR 7322 follow-up)

PR #7322 added the PdfJsNetwork.jsm file, instead of the general src/core/network.js file for the Firefox addon. However, make.js wasn't updated to actually stop including the now obsolete network file.

/botio-linux preview


upgrade pb to v3

Hrm, not sure how I generated so many conflicts..

Closing, will repull and retry.


Static OPENAI API KEY assigned.

I have the issue that there seems to be a static OPENAI API KEY used, the key referenced is not mine:
{'error': {'message': 'Incorrect API key provided: sk-proj-********************************************ygNW
I have also following issue, but now I have this static key assigned issue.
https://discord.com/channels/1222935860639563850/1226175438833844285/threads/1254603317120729219
          Made some progress, I didn't have ```llamma-index-embeddings-huggingface``` installed.

Now I've arrived at the frontend page, but when given a prompt I receive this error:
EDIT: This was after I input a response on the frontend page. This error below was being repeated as a response from the bot in the chat.
Oops. Something went wrong: OpenAIException - Error code: 401 - {'error': {'message': 'Incorrect API key provided:
hf_wZdQE*************************FdyQ. You can find your API key at https://platform.openai.com/account/api-keys.',
'type': 'invalid_request_error', 'param': None, 'code': 'invalid_api_key'}}

I have LLM_MODEL, LLM_API_KEY, and LLM_EMBEDDING_MODEL all set. I also have set and unset OPENAI_API_KEY and it appears to make no difference. Perhaps a logical error with handling huggingface litellm models?
Also, I was reading memory.py and it seems like on line 25 that its referencing a static HuggingFace model rather than taking in LLM_MODEL. Maybe a design feature, but thought it was worth mentioning.
Originally posted by @Solonce in https://github.com/OpenDevin/OpenDevin/issues/228#issuecomment-2022658511

Hey @doc1024, please use the bottom down Settings wheel in the frontend to set the model and key. Save and it should work. You don't need the vars for model and key, use the frontend settings window.
The post you reposted is from 3 months ago, a lot has changed since then. Have you used opendevin before? Do you share the computer with someone else?

@doc1024 are you still running into this issue after setting the API key through the settings UI?

I stopped using the latest code, it usually breaks. I'm not sharing the computer. Do you plan to release a stable version?

Yes the issue persised at the build I did at that time. I need to build with latest to check if it is still in issue. In the moment I try to use 0.62. But it has an issue with certificate handling in my environment. I opened an issue for that too.

There is no static API key coming from OpenDevin: it is either an environment variable (maybe even set in .bashrc), or in the config.toml file. Go to your OpenAI account page and generate a new key and enter that in the UI and click Save.

Issue solved with the latest build today.


Doorbird D21 series - second Lock

Hi,
I've just got a D2101v intercom from Doorbird.
I used the Homebridge-doorbird plugin (Homebridge working on Synology NAS) and almost everything works fine.
The issue for me is that I cannot control the second Lock (this intercom model has 2 locks).
I tried to modify the plugin from brownad with out success till now.
Anyone has the same issue?
Thanks in advance for the support.

I think it would need to be configurable to add a second lock for these kind of devices, I would welcome a PR from anyone that is interested
Sent from my iPhone

On 13 Dec 2018, at 15:40, Alcor72<EMAIL_ADDRESS>wrote:
Hi,
I've just got a D2101v intercom from Doorbird.
I used the Homebridge-doorbird plugin (Homebridge working on Synology NAS) and almost everything works fine.
The issue for me is that I cannot control the second Lock (this intercom model has 2 locks).
I tried to modify the plugin from brownad with out success till now.
Anyone has the same issue?
Thanks in advance for the support.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi Alcor72,
I had the same issue.
I implemented a workaround using "Homebridge Webhooks". Create a virtual Push Button that calls the  Doorbird API to trigger the second relay.
Regards

This could be added in as a second door lock but better to be optional in config
I’ll look at it sometime - PRs welcome though
Sent from my iPhone

On 29 Dec 2018, at 08:42, thevangogh<EMAIL_ADDRESS>wrote:
Hi Alcor72,
I had the same issue.
I implemented a workaround using "Homebridge Webhooks". Create a virtual Push Button that calls the Doorbird API to trigger the second relay.
Regards
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi thevangogh,
I worked on it today but could not work out the correct way of using the Push Button.
Got the following error  (see attach).
My config.json is :
{
"platforms": [
{
"platform": "HttpWebHooks",
"webhook_port": "51828",
"pushbuttons": [
{
"id": "pushbutton1",
"name": "Push button name 1",
"push_url": "http://192.168.86.XXX/bha-api/open-door.cgi?r=2&http-user=USERNAME&http-password=USERPASS",
"push_method": "GET"
}
]
}
]
}
Could you help?
Thanks in advance

/usr/local/lib/node_modules/homebridge/lib/api.js:108
stdout

/usr/local/lib/node_modules/homebridge/lib/api.js:108
stdout

RenergiseBackup - Synology DiskStation.pdf

Might be easier to get help on the plugin issue board
But have you tried to run the plugin without the push button configured, then tested out the URL request separately (assume that works)?
Then introduce the push button one config at a time.
Sent from my iPhone

On 4 Jan 2019, at 15:31, Alcor72<EMAIL_ADDRESS>wrote:
Hi thevangogh,
I worked on it today but could not work out the correct way of using the Push Button.
Got the following error (see attach).
My config.json is :
{
"platforms": [
{
"platform": "HttpWebHooks",
"webhook_port": "51828",
"pushbuttons": [
{
"id": "pushbutton1",
"name": "Push button name 1",
"push_url": "http://192.168.86.XXX/bha-api/open-door.cgi?r=2&http-user=USERNAME&http-password=USERPASS",
"push_method": "GET"
}
]
}
]
}
Could you help?
Thanks in advance

/usr/local/lib/node_modules/homebridge/lib/api.js:108
stdout

/usr/local/lib/node_modules/homebridge/lib/api.js:108	stdout
RenergiseBackup - Synology DiskStation.pdf
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Alcor,
The Doorbird URL looks correct. Have you tested it directly using a browser?
re: HttpWebHooks, based on the output error, I suspect it's the HttpWebHooks plugin issue. As Brownad suggested, were you able to get HttpWebHooks plugin up on itself?
I do have an extra entry after webhook port
"cache_directory": "./.node-persist/storage",
Not sure if that will help you.
Regards,

Did anyone get this working?  I actually have 3 doors running off my DoorBird ( I have the IO unit) and would value being able to select different locks to expose to HomeKit.

+1
This would be so helpful for me too. I can currently only control one of the two gates.
Would very much appreciate this addition.

+1

Httpwebhooks definitely works. Try it out independently from the doorbird plug-in first.


🧑💻:  Adding BEM Naming convention to all classes

:red_circle: Title : Adding BEM Naming convention
:red_circle: Enhancement Aim : It will help new users to understand the use of the css and their block elements in html
:red_circle: Changes : I just want to change the classes names in both css and html or js file .
Screenshots 📷

:white_check_mark: To be Mentioned while taking the issue :

Full name : Ayushmaan Agarwal
What is your participant role? GSSOC

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

@Ayushmaanagarwal1211 can you show me, any such changes in the repository?

yes like you can see that in your mainpage.jsx

the classes name has been written but i will change these classes name to like

{`${getName(category)} Projects`}

 handleTagClick('Basic')}
    >
      Easy

 handleTagClick('Intermediate')}
    >
      Medium

 handleTagClick('Advanced')}
    >
      Hard

 handleTagClick('All')}
    >
      All

You can see that you can easily understand the elements used for by directly seeing the classes and i also change its corresponsding css so that designing doesn't changes .

@Ayushmaanagarwal1211 no leave it for the beginner to contribute in the enhancement of this project.
Not required.


As A User,  I WANT to see a heading at the top of the window that display the title/logo of the application.

Header html and CSS added.


[sub-issue] item_rv_my_dashboard change to ConstraintLayout

Change item_rv_my_dashboard to ConstraintLayout

Change item_rv_my_dashboard layout to ConstraintLayout

Would you like to work on the issue?
Yes

@ujjwalagrawal17  I have fixed the issue please review the PR #198


standard gates in qiskit in its own inc file

Fixes #4312
The qiskit/qasm/libs/qelib1.inc library is defined in the OpenQASM specification (p.10). The file qiskit/qasm/libs/standard_gates.inc is created with the gates in Qiskit.
Because u is not part of the original qelib1.inc, the trick if aliasing U to u from https://github.com/Qiskit/qiskit-terra/pull/6077 had to be readjusted. Also swap is not part of the original qelib1.inc, so many tests need include "standard_gates.inc"; instead.

@1ucian0 is this a breaking change? If a user had something like:
from qiskit import QuantumCircuit
qasm = """
OPENQASM 2.0;
include "qelib1.inc";

qreg q[3];

p(pi/2) q[0];

"""
circuit = QuantumCircuit.from_qasm_str(qasm)

would this break in the next version?
If so, in addition to Qiskit users this would also be a breaking change for the IBM Quantum Composer, old previous saved circuits will stop working. The composer is relying in the qelib1.inc provided in Qiskit. The same would happen for users of the ibm-quantum-widgets.
I'm wondering, does it make sense to introduce this breaking change now that the new version of OpenQasm 3.0 is already out?

There are two paths:

qelib1.inc is static: therefore this PR should be merged to fix the fact it was not static.
qelib1.inc is not static: therefore IBM Quantum Experience should have keep a copy or a version of the file with the Qasm source, since the source.

If "qelib1.inc is static" (which I think it should), the answer to "would this break in the next version?" is yes, since the previous code was based on the wrong assumptions. We can think in a way to solve that in IBM Quantum Composer and ibm-quantum-widgets in their own issue trackers.

We can think in a way to solve that in IBM Quantum Composer and ibm-quantum-widgets in their own issue trackers.

both are Qiskit users (Qiskit services in the cloud) so it would be a breaking change the same it would be for regular Qiskit users with the snippet above.

okey... let's dump the summary of the off-the-band discussion:

qelib1.inc needs to go back to the paper state, no more additions. Same for the QASM3 equivalent stdgates.inc.
No need for a standard_gates.inc. If Qiskit serialilzes a circuit with a gate out of the standard library, the dumper needs to add the gate declaration based on the gate definition.
As a consequence of the previous point, all gates in Qiskit should have definition.
The way the parser is going to handle current QASM2 code with gates out of the qelib1.inc is by raising a warning to tell the user to change the include line with qiskitlib.inc. In the beginning, we can do that implicit change at parsing time. After some unspecified period of time, the warning will be removed and the parse will fail.
qiskitlib.inc, following the same criteria than the other inc files, is immutable.
We thought about using stdgates.inc instead of qiskitlib.inc. However, stdgates.inc is not QASM2 compatible (ctrl in the definitions, for example. And unicode!)

The ToDo for this PR is implementing the warning with the implicit include change and renaming standard_gates.inc as qiskitlib.inc. Am I missing something @francabrera @ajavadia ?

deprecation warning added in 79907ee

I think this can be closed for now, in the light of the discussion in https://github.com/Qiskit/qiskit/issues/10737


📖 Added overlooked dollar sign in example-scenarios.md

Summary
This PR fixes an oversight in docs/content/direct/example-scenarios.md: a dollar sign was missing.
Preview at https://mikespreitzer.github.io/kcp-edge-mc/doc-update-802/direct/example-scenarios/#scenario-6-multi-cluster-workload-deployment-of-app-with-serviceaccount-with-argocd
Related issue(s)
Fixes #

/cc @KPRoche
/cc @eaepstein
/cc @clubanderson

LGTM
and thanks Mike

/approve


Nav2 action node

ROS2 Action ad Service Wrappers with test examples @facontidavide

sorry but no.
I am not adding dependencies to this repo


On Click of "Get Started" button in Facebook Messenger, Composer code is throwing exception

FB messenger have "Get Started" button which helps the user to initiate the conversation with the bot. When we published the code, on click of Get Started button, we are getting exception.
Version
I'm using the latest version of Composer.
To Reproduce
Steps to reproduce the behavior:

Create a messenger bot using MS Bot framework
Configure a get started button using the REST API to FB Graph API Explorer
Go to the messenger and delete the conversation if you have any existing . And try to start conversation by clicking on the error
See error

Additional context
**Observation: ** The channel data for normal messages and the get started button is different.
ChannelData for normal messages:
{{"sender": {"id": " "},"recipient": {"id": ""},"timestamp":<PHONE_NUMBER>263,"message": {"mid": "m_TmBzHQTfb1dxzAncC0thLmSH6DRNDyon4k8nJX8fclpZ0OBv4nCfubgtJvAhivh_awmq9kZ7SlXfh-JPTzcdlA","seq": 0,"quick_reply": {"payload": "Analyse my skin"},"text": "Analyse my skin","is_echo": false}}}
ChannelData for GetStarted button:
{{"sender": {"id": ""},"recipient": {"id": ""},"timestamp":<PHONE_NUMBER>592,"postback": {"payload": "Get Started","title": "Get Started"}}}
Exception message: Object serialized to String. JObject instance expected.

@vidyakdil Not certain if its related or not but we had a similar situation. Bot worked fine in webchannel but failed with a serialization error in Messenger and the Issue was related to the fact that Facebook invokes authentication by default while the webchat does not. Thus the user gets serialized and deserialized.
see: https://stackoverflow.com/questions/60400935/why-does-my-azure-web-app-bot-work-fine-in-some-channels-but-not-in-facebook-or/60400936#60400936

Maybe you can just add the message value into channelData, So ChannelData for normal messages:
{"mid": "m_TmBzHQTfb1dxzAncC0thLmSH6DRNDyon4k8nJX8fclpZ0OBv4nCfubgtJvAhivh_awmq9kZ7SlXfh-JPTzcdlA","seq": 0,"quick_reply": {"payload": "Analyse my skin"},"text": "Analyse my skin","is_echo": false}

@vidyakdil can you try suggestion from @Danieladu and comment here if you continue to see the issue?


Updated the code signing identities for the frameworks and targets

In order to properly support Carthage and CocoaPods at the same time with cross-platform targets, the code signing identities need to be modified a bit to make sure everyone can build Alamofire using Carthage. Thankfully, CocoaPods handles all this independently.
To properly support Carthage, iOS targets and tests need to code sign as iPhone Developer. This is due to the fact that Xcode requires them to be code signed. Mac OS X targets and tests are different altogether. They don't require code signing at all. Therefore, it should be disabled to allow users without a Mac Developer account to build Alamofire on OS X and run the tests as well as those without an iPhone Developer account who are simply trying to build Alamofire through Carthage. All frameworks will get resigned anyways when embedded within a final app target.
This will make creating cross-platform libraries ontop of Alamofire much easier for all those involved. You can find more information here and here.

Thanks for looking into this, @cnoon. I'm just about to cut Alamofire 1.1.5. When that's released, can you please verify that things are working as expected?

Will do @mattt.

Looks good @mattt. All the tests are passing on both targets on 1.1.5 and the Carthage builds are all good as well.
cnoon:~/Desktop/AlamofireCarthage$ carthage update
*** Fetching Alamofire
*** Checking out Alamofire at "1.1.5"
*** xcodebuild output can be found in /var/folders/mc/9x8d6r415qxgyxry1y8vm9h0jj7n1m/T/carthage-xcodebuild.9jtd3m.log
*** Building scheme "Alamofire iOS" in Alamofire.xcworkspace
*** Building scheme "Alamofire OSX" in Alamofire.xcworkspace

Thanks as always!


tntracker

I would like to invite you to https://tntracker.org, so you can make IMDB-Scout für search in this Tracker.

Sure, send it to purfview at protonmail com

done

Search be ID doesn't work for me. Does it work for you?
https://tntracker.org/browse?imdb=7126948
or
https://tntracker.org/search/?perPage=75&page=1&onlyup=1&cats=1,2,4,5,6,7,8,10,12,13,14,16,17,18,19,20,22,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46&search=tt7126948

Search works just with Film/Serial title name.
https://tntracker.org/search/?perPage=75&page=1&onlyup=1&cats=1,2,4,5,6,7,8,10,12,13,14,16,17,18,19,20,22,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46&search=Wonder Woman 1984

Added to v10.2.
For search to work the site needs authorization token. Get it with Developer Tools in browser, look at request headers where they have "Authorization:", copy and paste it to the script's settings.

Developer Tools? How in Firefox?

Try "F12" key -> Network


generate versioned documentation from the library code

manual updates to reference documentation is not very robust, and can lead to problems such as #28.
we should migrate to tsdoc to document code, and possibly typedoc to generate reference material to be incorporated into uniswap.org

Copying them over is not ideal since we still only represent a single version, ideally there is a documentation site for each NPM package version that fully documents the classes and methods available in the SDK


chore(deps): update all non-major dependencies

This PR contains the following updates:

Package
Type
Update
Change

@antfu/eslint-config
devDependencies
patch
^2.23.1 -> ^2.25.0

@commitlint/cli (source)
devDependencies
patch
^19.3.0 -> ^19.4.0

@types/node (source)
devDependencies
patch
^22.1.0 -> ^22.2.0

eslint (source)
devDependencies
patch
^9.7.0 -> ^9.9.0

pnpm (source)
engines
minor
>=9.0.0 -> >=9.7.0

Release Notes

pnpm/pnpm (pnpm)
v9.7.0: pnpm 9.7
Compare Source
Minor Changes

Added pnpm version management. If the manage-package-manager-versions setting is set to true, pnpm will switch to the version specified in the packageManager field of package.json #8363. This is the same field used by Corepack. Example:
{
  "packageManager"<EMAIL_ADDRESS>}

Added the ability to apply patch to all versions #8337.
If the key of pnpm.patchedDependencies is a package name without a version (e.g. pkg), pnpm will attempt to apply the patch to all versions of the package. Failures will be skipped. If there's only one version of pkg installed, pnpm patch pkg and subsequent pnpm patch-commit $edit_dir will create an entry named pkg in pnpm.patchedDependencies. And pnpm will attempt to apply this patch to other versions of pkg in the future.

Change the default edit dir location when running pnpm patch from a temporary directory to node_modules/.pnpm_patches/pkg[@version] to allow the code editor to open the edit dir in the same file tree as the main project #8379.

Substitute environment variables in config keys #6679.

Patch Changes

pnpm install should run node-gyp rebuild if the project has a binding.gyp file even if the project doesn't have an install script #8293.
Print warnings to stderr #8342.
Peer dependencies of optional peer dependencies should be automatically installed #8323.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.6.0: pnpm 9.6
Compare Source
Minor Changes

Support specifying node version (via pnpm.executionEnv.nodeVersion in package.json) for running lifecycle scripts per each package in a workspace #6720.
Overrides now support the catalogs: protocol #8303.

Patch Changes

The pnpm deploy command now supports the catalog: protocol #8298.
The pnpm outdated command now supports the catalog: protocol #8304.
Correct the error message when trying to run pnpm patch without node_modules/.modules.yaml #8257.
Silent reporting fixed with the pnpm exec command #7608.
Add registries information to the calculation of dlx cache hash #8299.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.5.0: pnpm 9.5
Compare Source
Minor Changes

Added support for catalogs #8122.
Catalogs may be declared in the pnpm-workspace.yaml file. For example:

Default catalogs
catalog:
  chalk: ^4.1.2

Named catalogs
catalogs:
  react16:
    react: ^16.7.0
    react-dom: ^16.7.0
  react17:
    react: ^17.10.0
    react-dom: ^17.10.0
```

Then, in `package.json` files, use the `catalog:` protocol to reference a "default" or "named" catalog:

```json
{
  "dependencies": {
    "chalk": "catalog:",
    "react": "catalog:react16",
    "react-dom": "catalog:react16"
  }
}
```

Shout out to @gluxon for implementing it!

Bundled pnpm setup now creates the pnpx script #8230.

Patch Changes

Read authentication information from .npmrc in the current directory when running dlx #7996.
Updated @pnpm/tabtab to v0.5.4, enabling zsh autocomplete lazy loading #8236.
Installation with filtering will now work, when dedupe-peer-dependents is set to true #6300.
Fixed dlx not actually using the Node.js version specified by --use-node-version.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.4.0
Compare Source
Minor Changes

Some registries allow the exact same content to be published under different package names and/or versions. This breaks the validity checks of packages in the store. To avoid errors when verifying the names and versions of such packages in the store, you may now set the strict-store-pkg-content-check setting to false #4724.

Patch Changes

Fix package-manager-strict-version missing in config #8195.
If install is performed on a subset of workspace projects, always create an up-to-date lockfile first. So, a partial install can be performed only on a fully resolved (non-partial) lockfile #8165.
Handle workspace protocol with any semver range specifier, when used in peer dependencies #7578.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.3.0
Compare Source
Minor Changes

Semi-breaking. Dependency key names in the lockfile are shortened if they are longer than 1000 characters. We don't expect this change to affect many users. Affected users most probably can't run install successfully at the moment. This change is required to fix some edge cases in which installation fails with an out-of-memory error or "Invalid string length (RangeError: Invalid string length)" error. The max allowed length of the dependency key can be controlled with the peers-suffix-max-length setting #8177.

Patch Changes

Set reporter-hide-prefix to true by default for pnpm exec. In order to show prefix, the user now has to explicitly set reporter-hide-prefix=false #8174.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.2.0
Compare Source
Minor Changes

If package-manager-strict-version is set to true, pnpm will fail if its version doesn't exactly match the version in the "packageManager" field of package.json.

Patch Changes

Update @yarnpkg/pnp to the latest version, fixing issue with node: imports #8161.
Deduplicate bin names to prevent race condition and corrupted bin scripts #7833.
pnpm doesn't fail if its version doesn't match the one specified in the "packageManager" field of package.json #8087.
exec now also streams prefixed output when --recursive or --parallel is specified just as run does #8065.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.1.4
Compare Source
Patch Changes

Improved the performance of the resolution stage by changing how missing peer dependencies are detected #8144.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Hywax Assistant.

👋 @hywax-assistant
💖 Thanks for opening this pull request!
We use semantic commit messages to streamline the release process.
Examples of commit messages with semantic prefixes:

fix: interval for sending a request in the base service
feat: add new NAME service
docs: example of using the NAME service

👋 @hywax-assistant Congrats on merging your first pull request! 🎉


🐞 - v4 BadgedContent: icon is positioned incorrectly when it's shown with a delay

Playground Link
https://stackblitz.com/edit/angular-phczdh?file=src%2Fapp%2Fapp.template.html,src%2Fapp%2Fapp.component.ts
Description
tui-icon added to tui-badged-content with a delay is positioned incorrectly.

Angular version
18.2
Taiga UI version
4.5.0
Which browsers have you used?

[X] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[ ] macOS
[X] Windows
[ ] Linux
[ ] iOS
[ ] Android

Looks like resize observer is triggered without change detection since it's not patched by zone.


bower install angularfire 2

When I run $ bower install angularfire#2.0 --save no angular.min.js file is checked out.
If I run $ bower install angularfire --save it installs the 1.2.0 version.
Any ideas of why this is happening?

Dupe of #724.


Add Sublime Text 3 Build 3083

It is basically a copy of the Sublime Text 2 cask but adapted to the current stable Beta release.

Betas belong in caskroom/versions. This cask is already there.


[HUDI-3158] Reduce warn logs in Spark SQL INSERT OVERWRITE

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@xushiyan @nsivabalan hello, can you please take a review?

@dongkelun the warn log comes from clustering planning. can you help clarify how would this change avoid the repeated warn logs?

@dongkelun the warn log comes from clustering planning. can you help clarify how would this change avoid the repeated warn logs?

Hello, the reason for the warning is that the content of replaceCommitRequestedInstantinstant is empty,There are many places to call this method, such as HoodieSparkTable.create:
    if (refreshTimeline) {
      hoodieSparkTable.getHoodieView().sync();
    }

There are also many places to call  HoodieSparkTable.create,Therefore, it is not easy to reduce the warning log. It is better to avoid this warning directly from the source.INSERT_OVERWRITE's commitActionType is REPLACE_COMMIT_ACTION,It creates an empty replaceCommitRequestedInstantinstant   in the startCommitWithTime method,We can avoid this warning from the source by changing it to non empty

@codope : Can you review this PR. May be there could be some follow ups in other places where we do create similar empty replace commit instants. I

I would vote to remote the log.warn msg only(ClusteringUtils L 93)) using a diff patch which we can pull into 0.10.1. we can continue discussions in this patch as to whats the right fix is.

https://github.com/apache/hudi/pull/4553

@dongkelun Rather than introduce a behavior change, I would prefer to remove the warn log itself. Is there any reason we still want to keep it? Also, while you're at it, can you make the method getRequestedReplaceMetadata private? I don't see it being used anywhere other than the same class.

OK, I have made the method getRequestedReplaceMetadata in classes MetadataConversionUtils and ClusteringUtils  private

@nsivabalan @codope
I found a previous issuse:HUDI-1739  in 'MetadataConversionUtils. getRequestedReplaceMetadata ` is the same as this issuse

@xushiyan @codope : if you folks don't have any other comments, I can go ahead and land this.

@dongkelun @nsivabalan @codope this PR has pivoted and it's mostly not about warn log any more. Can we file a different ticket tailored to this PR and link to it?

@dongkelun @nsivabalan @codope this PR has pivoted and it's mostly not about warn log any more. Can we file a different ticket tailored to this PR and link to it?

I have created a new issue HUDI-3252 and modified the PR link to it. Do you think this description is accurate？

looks good to me. I have closed the previous ticket btw.


Pinch in (zoom out) is being registered only after pinch out (zoom in)

As the title says, pinching out an element does nothing. Only after a pinch in I can then normally pinch out.
You can reproduce this here: https://biodiv.github.io/contactjs/
Try to pinch out the square without pinching in, it won't shrink.
I did a bit of debugging and pinchstart doesn't fire in this case.

thanks for reporting. Please try the updated version v2.1.3

Perfect! Now it works as expected.
Thanks!


cage: 0.1.5 -> 0.1.5-unstable-2024-07-29; wlroots_0_16: drop

Description of changes
Includes support for wlroots 0.17 and a fix for disabling XWayland.
Issue asking for a release: https://github.com/cage-kiosk/cage/issues/337
Diff: https://github.com/cage-kiosk/cage/compare/v0.1.5...d3fb99d6654325ec46277cfdb589f89316bed701
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

2 packages built:

cage
wio


php7.1; tests; travis

To solve project issues and merge PRs we need to have small bunch of tests.
Changes:

up composer php verison to 7.1
add phpunit dev dependency
add travis.yaml to run tests
small bunch of tests with SimpleTests.php

Added:

Table::pickRecord method allows to get record by index

Fixed:

#35 Record:getNum not returns false if value is '0' (zero char)

@luads Can you review and approve this PR. I'm going to solve project issues soon and release v1.1

@luads You need to enable travis CI for this project


[CT-989] Support insert_overwrite strategy with delta

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
Previously, delta didn't have support for dynamic partition overwrite which prevented it to be used with the insert_overwrite strategy.
The recent 2.0 release of delta added support for dynamic partition overwrite mode for partitioned tables.
So, it would be great if dbt could allow insert_overwrite when file_format is delta.
Describe alternatives you've considered
No response
Who will this benefit?
No response
Are you interested in contributing this feature?
No response
Anything else?
No response

Hey @flvndh, welcome back! I remember you were working on this last year: https://github.com/dbt-labs/dbt-spark/pull/186

The recent 2.0 release of delta added support for dynamic partition overwrite mode for partitioned tables.

Huzzah! That's great news. The only change we'll need to make is removing the validation logic here:
https://github.com/dbt-labs/dbt-spark/blob/7f6cffecf38b7c41aa441eb020d464ba1e20bf9e/dbt/include/spark/macros/materializations/incremental/validate.sql#L50-L52
I'm going to transfer this one to dbt-spark, and mark it a good first issue :)


Do something about the --skip-numeric-underscore-normalization option

Hey! As I understand, this option was added to keep the possibility to write 'localized' code, respecting the developers' regional numeric format.
Localized code formatting
I disagree with the premise that this is something to be considered. Even though my local date format is not ISO, I'm using YYYY-MM-DD in code. Even though my local format marks decimal places with a comma, I'm fine with writing 3.14 instead of 3,14.
The black philosophy
The README makes some promises:

Black is the uncompromising Python code formatter. By using it, you agree to cede control over minutiae of hand-formatting. In return, Black gives you speed, determinism, […]. You will save time and mental energy for more important matters.

Blackened code looks the same regardless of the project you're reading. Formatting becomes transparent after a while and you can focus on the content instead.

Adding options like this, while having only a minor effect, goes directly against these promises. Each option is a new discussion to have. Each option is something new to discover: consider if I want to make a quick edit to a constant in someone's blackened open source project on the github.com in-browser editor. I know how to write black-compliant code, so I can risk not cloning the project and committing something without running black. But now that this option is there, I either need to look for the project's config first to see their preference for literals, or guess and risk a CI failure wasting my time.
And yes, I honestly believe this is a slippery slope.
You might say, well, that's okay, everyone using black would just use the defaults unless they are in an aforementioned non-three digit grouping region, right? Well…
Developers are a lost cause
We had a team at my company bump the black version a couple days ago. I glanced at their project today and was horrified to find skip-numeric-underscore-normalization = true in their config. Apparently they saw the option in the changelog and

held a poll on whether to keep this on or off
got a 50-50% split for/against in the results
said 'we may remove the option if there is consensus between our developers'

Really, developers are a lost cause when it comes to code style arguments. Just don't let them have them, please.
Possible fixes

Remove the --skip-numeric-underscore-normalization option.

Remove the whole feature of numeric-underscore-normalization; if it's not a universally enforceable standard, maybe it has no right to be a part of black.

Rewrite the style of documentation of these options. Mention restrictive rules on when you as a developer are allowed to use it. Something like this:

Configuring black
Some special circumstances might require project specific configuration. But if you're using black, to not undermine all the benefits black gives you and the community, you must agree to only use these options if we permit it here.
--skip-numeric-underscore-normalization
You may use this if: Your codebase is worked on only by developers from regions where the local number format does not group by three digits.
Effect: Numbers can be written both like 100_000_000 and 1_0000_0000
--skip-string-normalization
You may use this if: Your codebase predates black with pre-existing string conventions, and adoption would be unreasonably difficult if all strings had to instantly be reformatted.
Effect: Strings can be written both like 'hello' and "hello"

Just as a changelog for this issue: I've changed the title and provided alternative solutions (added the 'Possible fixes' section.)

I suspect I may have missed the original issue where this would have been more appropriate to bring up, but if this is being considered for reversal or modification, I'd like to point out that not all numbers have the same, shall we say, texture.
For example, there's nothing locale-specific about this number:
actually_a_date = 2018_05_01

which black by default now helpfully "fixes" to
actually_a_date = 20_180_501

Another example of not all numbers having the same texture: Inserting underscores into integers feels odd to me at times when the integer in question is a hardcoded ID.
For example, I'd prefer to see Issue(issue_id=1142395) in my code than to see Issue(issue_id=1_142_395), because the former makes it easier to grep for 1142395 and because the latter causes me to mentally read out "issue id one million one hundred forty two thousand ..." which feels not quite right.

I think in corner cases (this is not happening too often, or I'm not aware of something?) such as actually_a_date = 2018_05_01 we can just disable formatting for particular line.
I would argue removal  of numeric-underscore-normalization is the best course of action. It still is a very fresh Python feature, so I assume we have yet to explore how useful (or troublesome) it is and thus we shouldn't force it on anyone. The inability to search on number is especially worrying to me.
And to make a case against that it is given that black has to have some opinion, I would like to say, that even with things like line length, the issue always was not if we should limit it, just a particular number. Here we do not even know if we want to use underscores at all anywhere in the code.
Anyway, even as an "opponent" of this normalization, if it stays I still think it shouldn't be optional because of the reasons stated by @underyx .

Here is a link to discussion which happened when the option was first introduced: https://github.com/ambv/black/pull/529

I like fix option 2 - "Remove the whole feature of numeric-underscore-normalization; if it's not a universally enforceable standard, maybe it has no right to be a part of black."  There are clear examples documented above where numeric underscores not only don't make sense but obfuscate the intent of the code.
The first time Black reformatted some code with them I pushed the PR & saw the underscores in the numeric literals and was confused where they'd come from.  It wasn't until a couple days later I had even heard that underscores in numeric literals were allowed now in Python 3.6 so at first I thought it was a syntax error.
I see them as being much like automatic string concatenation, these two lines are equivalent:
x = "this is a really really  really realllllllllly looooooooooooooooooooooooooooooooooooooooooong line"
x = (
    "this is a really really  really realllllllllly "
    "looooooooooooooooooooooooooooooooooooooooooong line"
)

If I add the parenthesis & split a string literal into multiple lines Black is absolutely permitted to rearrange the surrounding whitespace for consistency.  However, It'd be rather invasive of Black to break the literal up in the first place even though it violates the 88 char line rule.
Similarly for numeric literals, if I choose to put underscores in them then I'd expect Black to respect that & leave them alone because changing them likely changes what I'm intending to express by putting them in.  If I leave underscores out, then it's probable that's because my intent is to not make the numeric literal look like a western-style value with commas every 3 digits because of what the value represents (ex: a user id, or a date, etc)

I also agree with option 2: "Remove the whole feature of numeric-underscore-normalization; if it's not a universally enforceable standard, maybe it has no right to be a part of black."
While the philosophy of Black is to be uncompromising on the things it decides to enforce, that doesn't mean that it has to enforce all aspects of your code. With most decisions it chooses to make are neither here nor there, the feature as it stands can make it much harder for teams to read the code: either because of the poor date format support (and what about telephone numbers literals??) or because of localisation. I can see that being a barrier to adoption for Black.

I mentioned earlier, but not in this thread: I consider altering numeric literals to be the same as altering a quoted string. Why would you do it? Even if one could determine the correct context (date? locale?) which one can't, one can't determine the human intent.

Is this option still available? I don't see it in the command line options section of the docs. I'm getting used to using black for formatting and I have gone all in on one project, but I just noticed the underscores in the numbers and wow, that's weird. It's the first time I've seen this, and I'd like to omit this formatting if possible. My understanding is that you can configure black's formatting behavior by adding entries into the black section of the pyproject.toml file, and I have added skip-numeric-underscore-normalization = true. However, now that the underscores are present is there a way I can easily (non-manually) remove them? That option doesn't seem to back out the previous formatting, i.e. the additional underscores within numeric literals.
Thanks in advance for any suggestions, and/or feel free to change my mind.

It's weird because it detracts from readability, IMHO. It breaks things like when I have numbers that are meaningful such as 20180711 (for July 11th, 2018), it turns that into 201_807_11 (and I'd expect the grouping to start from the other end, i.e. 20_180_711, since that's more akin to 20,180,711). I can see how this may provide benefit in some cases, but in my opinion, it's taking things a bit too far. (Of course you can get used to anything with enough exposure, it just took me aback when I first saw it, I wasn't aware of PEP515.) It's not my call, I'm just glad that this is one of the few options where users have discretion, hence my comment in support of keeping this option available and for confirmation that it's still in play.

Black does format 20180711 as 20_180_711; if you see something else, please report this as a bug.

Thanks for the follow up/clarification. You're right, I was mistaken. The grouping by three goes in the opposite direction to the right of the decimal point, and logically so. I shouldn't have commented about the behavior from a (mistaken) extrapolation.

nor are the cases where it's not the sole purpose, obscure.

It would be love to see a source for this statement.
How many hard coded number literals that are not "natural" numbers are in the code base? We have listed issue numbers (which personally I have never seen as python literals), unix timestamps (but how often we hardcode these?), and dates as a number (do we have some examples where this used in the wild?).
Links to some opensource projects which have examples of these would be great help, at least then we can try to estimate how common these practices are.

At the doctor so no links. But the place I’ve personally ran into this has been primarily in tests, where I have specific ID, dates, time stamps, etc written as hardcoded literals.
I use hardcoded literals in tests way more often than anywhere else tbh.
Sent from my iPhone

On Nov 19, 2018, at 2:08 PM, rooterkyberian<EMAIL_ADDRESS>wrote:
nor are the cases where it's not the sole purpose, obscure.
It would be love to see a source for this statement.
How many hard coded number literals that are not "natural" numbers are in the code base? We have listed issue numbers (which personally I have never seen as python literals), unix timestamps (but how often we hardcode these?), and dates as a number (do we have some examples where this used in the wild?).
Links to some opensource projects which have examples of these would be great help, at least then we can try to estimate how common these practices are.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Great points all around. I think it's safe to say we have overwhelming support of removal of the feature, so I have updated my issue title and description to reflect this.

I don't understand the logic behind the feature.
Number without underscore will not  be formatted by black, while number with pre-defined underscore will be formatted.
num = 100000000  ----black---> num=100000000
package_version = 2018_11 ----black--->  package_version = 201_811
What I expected was the opposite situation.

@yech1990 what you have mentioned here is due py36 support detection. If you had both lines in the same file, both of them would get formatted with underscores.
You can force black to assume py36 features are available by adding --py36 as a command line argument.

Both are in the same file.
I use python 3.7


Dyson Pure Hot+Cool auto discovered but only adds Climate entity, fan is missing (error: No module named 'homeassistant.util.percentage')

hi,
I was using the homeassistant built in dyson integration uptil a couple of months ago when it stopped working. I have removed that configuration from my configuration.yaml file.
I used the Dyson CLoud and Dyson local configuration to detect my Pure Hot+Cool dyson fan and it was auto discovered.
When I added the device it only added the climate entity, and I am missing the fan controls to set the fanspeed.
I checked and the below error shows up for Dyson.local when setting up the fan entity:
Logger: homeassistant.setup
Source: setup.py:280
First occurred: 9:24:05 (1 occurrences)
Last logged: 9:24:05

Unable to prepare setup for platform dyson_local.fan: Platform not found (No module named 'homeassistant.util.percentage').

I am running homeassistant in a docker and the version is:
Home Assistant 2021.1.5

found this existing issue.
https://github.com/shenxn/ha-dyson/issues/13
Based on this closing the current one, will try updating my HA instance to see if it is resolved.


Remove broken links to insider builds from readme

Given that #25718 notes that insider builds will no longer be available, this commit updates README.md to reflect this.

@microsoft-github-policy-service agree


[feature]: expose tlv data for gossip messages in DescribeGraph

TLV extensions for gossip messages are received by lnd and stored on disk, but there is no way to retrieve that data through the api. This issue is about extending DescribeGraph and other relevant graph calls with a tlv_records field.
Example application: https://github.com/mempool/mempool/issues/2658

would also be cool to broadcast arbitrary tlv values here


Modification in section #import-the-database for better meaning

On section #import-the-database there is a paragraph that reads:
"To ensure the best performance, copy the *.bacpac file to the local computer that you're importing from."
It's a bit confusing to me, so not sure if I'm right about the meaning of the sentence, but I feel like it should say:
"To ensure the best performance, copy the *.bacpac file to the local computer that you're importing to."
Changing "importing from" to "importing to"

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

ID: 7c5e8701-e1d4-25f8-d76a-ee7870b915e1
Version Independent ID: 624211c7-2eb4-7154-d38f-236dc6f8f7a9
Content: Export a copy of the standard user acceptance testing (UAT) database - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/database/dbmovement-scenario-exportuat.md
Service: dynamics-365-cross-app
Product: ****
Technology: ****
GitHub Login: @laneswenka
Microsoft Alias: laswenka

Bug 775102 has been logged to address this issue.

Thanks for your feedback. We are closing this issue because we are either unable to find relevant information or reproduce this. If you're still experiencing the issue described here, please reopen or create a new issue.


feat:  add a setting within Obsidian to enable/disable aliases

need to update renaming setting description for consistency in text copy


[Bug] Graph Node consumes 6 GB of memory during local dev in docker compose

Bug report
I'm running graph node in a docker compose set up as part of larger infrastructure I'm building. I'm finding that when I deploy subgraphs to the graph node it starts eating up memory and eventually gets killed when it reaches ~6GB of usage.
Here's my full config file:
[store]
[store.primary]
connection = "postgresql://graph-node:let-me-in@postgres:5432/client__dev"
pool_size = 10

[deployment]
[[deployment.rule]]
shard = "primary"
indexers = [ "default" ]

[chains]
ingestor = "default"
[chains.mainnet]
shard = "primary"
provider = [
    { label = "mainnet-default", transport = "rpc", url = "http://host.docker.internal:3000/mainnet/default", features = [] },
    { label = "mainnet-archive", transport = "rpc", url = "http://host.docker.internal:3000/mainnet/archive", features = ["archive"] },
    { label = "mainnet-archive-traces", transport = "rpc", url = "http://host.docker.internal:3000/mainnet/archiveAndTraces", features = ["traces", "archive"] },
    { label = "streamingfast-firehose-mainnet", details = { type = "firehose", url = "https://mainnet.eth.streamingfast.io", features = [ "filters" ], token = "<token>" }},
]
[chains.avalanche]
shard = "primary"
provider = [
    { label = "avalanche-default", transport = "rpc", url = "http://host.docker.internal:3000/avalanche/default", features = [] },
]

Here are are the env vars I set when I start up the graph node container:
    environment:
      GRAPH_NODE_CONFIG: /etc/graphnode.toml
      ipfs: "ipfs:5001"
      GRAPH_LOG: debug
      node_role: "combined-node"

I'm running graphprotocol/graph-node:v0.31.0-rc.0 in my docker compose set up and I'm seeing this issue with older images like 0.27.0 as well.
One thing I notice is that if I deploy ~5 eth blocks subgraphs against mainnet and then they catch up, every new block causes graph node to consume ~100-200MB more memory. This happens even though the graph node never receives any queries so I'm fairly sure it's not the query cache that's eating up all the memory.
Are there environment variables I can use to tune how much memory this graph node consumes?
Relevant log output
No response
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out

[ ] Tick this box if this bug is caused by a regression found in the latest release.
[ ] Tick this box if this bug is specific to the hosted service.
[X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information
macOS

are you using a Mac M1? And what version of Docker Desktop are you running?

Yup, using a M1. Running docker desktop 4.12.
I decided to build and host a multiarch image of graph node myself and when I switched to using that image memory usage dropped to 200MB - it was definitely the emulation which was causing the crazy memory usage.


Reject requests via kept alive connections after close

Problem
After a graceful server is stopped, kept alive connections are left hanging. Each of them allow one more request to be processed, after that they are closed thanks to  SetKeepAlivesEnabled(false). But that one request (per connection) can still screw things up if e.g. it sends to a channel that you already closed since supposedly the http server has stopped gracefully.
Solution
Graceful server should ignore requests received via kept alive connections after server shutdown.

@lionelbarrow could you please take a look and let me know what you think. Thank you.

@horkhe Yep, I'll try to take a look this weekend.

This looks good to me. Thanks!


Ability to set more environment variables

Would it be possible to add the ability to set a few more environment variables?
I do not keep my cache directory in my home folder.  My scripts use the environment variable to set it to another location...
Can you add that capability?
Awesome project!
Thanks

What we could do is to allow this in the config file.
Just to let any option to pass through.
Something like
create: {
  compression: 'whatever'
...
}

Would you like to submit a PR?

I think that would be a good solution.
I would like to help out with coding, but I would have no idea how to...I saw your project on the Borg Github page and gave it a shot...It looks great!
Is this something that you would want to implement?
Thanks!

Yep, no worries.
I'll implement it in the next release.

Awesome!  Thanks...I look forward to it!

Besides this, have you tried the lib?
Is it working for you?
I'd love to hear from you, also about your setup for backups.

The lib? Not sure what that is...is it a precompiled way to run borgjs?
I installed Borgjs on an Unraid server using the command:  npm i -g borgjs
I have not had it run successfully yet though...When I tried it yesterday it errors out with an error about the lock file and another instance of Borgjs running.
As for Borg, I am using the Borg precomplied linux 64 file on 2 unraid servers...primary and backup.
Nightly, I call a script that I wrote which calls borg and pushes all my backup archives via ssh from my primary server to my backup.
Idealy, there would be a way to run Borgjs the same way I run the Borg binary...precompiled executable file for Linux...
I love your idea of using a config file to pass the info to your script...rather than borgmatic (https://torsion.org/borgmatic/), because I can keep that backed up an available on any machine...

which version of borgjs are you running?
I fixed a couple issues related to the file locking system.
Can you please check if you are running the latest?

I was running the previous version...

The latest version works...However it will not use my current cache location which I have declared with an environment variable...so it will have to rebuild cache which is what I am trying to avoid.

If it's set in aa env variable, borg should use it.
A quick way to solve is to set the env variable while running the script
YOUR_ENV_VARIABLE=value borgjs -c ~/config.j

passing the cache environment variable seems to have worked that way...thanks!
It still woudl be nice to pass it through with the config file though...

I also need to be able to add the flag ignore inodes...
I pass that flag in my script so it does not add all files again in an archive...borg seems to need this flag when I backup to  my remote server...
Sounds like a lot of work to make those changes to your script..
If you have the time and desire that would be awesome, but I completely understand if you do not see the value.
Thank you!

I see the value of what you proposed.
My tool is meant to enable people to use borg with ease, but it should not prevent customization.
Your idea of allowing borg flags to pass through the config file is valid.
I will think about a sane way to implement this, and keep you posted in this thread.
Thanks for the feedback

Understood...
Thank you for looking into being able to cusomize the options of your script!
I look forward to what you are able to make happen.
Thanks!

Release 2.0.0 has been shipped.
It supports custom environment variables and custom arbitrary borg options.
npm i -g borgjs
Please see the readme, you will have to adapt the config file.
let me know how it goes

Awesome job!!!
Tested it out and all env variables and options pass through correctly!
Thanks a lot...this will greatly simplify my back up script.
I really appreciate your work!!
Thanks again

Cheers


_fixtures: Removed testvariables2 and testvariables4

Moved the code in testvariables2 and testvariables4 into
testvariables3, renamed testvariables3 into testvariables2
Just some housekeeping.

Merged.


Fix wrapping groups when >=2 cards in favorites in Dashboard

I have several solutions on my mind:

decrease the width of each GroupCard
make it responsive to the size of content

I stick to the second option right now. Do you have any other ideas?

We can just set max-width of the columns

I've set 40% and 50% for them, so they don't wrap. But it also needs additional tuning for small screen sizes

This issue is fixed and will be closed by merging #29.


An approach to unblocking UK and US?

Hi,
I installed netflix-proxy on a Digital Ocean Droplet in the UK.  That's "closest" to me and I also thought it would help me access iPlayer.
I followed the setup README and therefore have a native IPv4 address that is in the UK and then an ipv6 address via the tunnel.
This works for Netflix - I didn't look in detail but I assume that sniproxy is proxying to/from Netflix via the ipv6 tunnel.
It work for iPlayer too - using tcpdump I see the media traffic coming from Akamai's CDN to my Droplet and then out to my client.
But Amazon isn't convinced - and I feel like I'm missing something....  I guess Amazon Video doesn't use ipv6 so they are seeing my ipv4 address which is geolocated in the UK.  So I'm not surprised that they block me.
Do I need a further ipv4 tunnel to the US in order to also have a US ipv4 address?  What do you suggest?
Thanks,
Elbow

Yes, you've done everything correctly for Netflix and iPlayer. If you wanted to proxy other services, like Amazon, which don't use IPv6, you will need to have a second netflix-proxy instance deployed to a US server. This one can just be IPv4 only, although if you set it up for IPv6 (with a second tunnel), you'll have backup in case the UK one goes down.

Hi,  Thanks for the reply.
I made a US Droplet and installed netflix-proxy.
As I see it now I have to configure the zone files on the US instance to point proxy iPlayer via the sniproxy in the UK, and the zone files on the UK instance to use the US sniproxy.
Looks like I need to split db.override into two files on each box - one for domains that must use the US proxy and one for those needing the UK proxy.
Am I on the right track?
Do I need to do something special to allow my home IP to access both proxies, or is that just a matter of authorising on both installs?
Thanks,
Elbow

Well - seems to work great.
I made a db.override.uk and db.override.us and modified the zones.override to use the zone file that seemed appropriate for the domain.  Synced up the changes on both droplets.
Thanks for the code and the assistance.
Elbow

No problem, great work!
Cheers,
-- ab1


Remove deprecated Windows Terminal Universal project

Remove deprecated Windows Terminal Universal project
PR Checklist

[x] Closes #12118
[x] I work here

You may want to grep the codebase for WindowsTerminalUniversal. There's a few in the pipelines!

HOW DID I MISS YOU DOING THAT sorry

You may want to grep the codebase for WindowsTerminalUniversal. There's a few in the pipelines!

I did something significantly less slick than "grep" and did Ctrl+Shift+F in vscode... but yeah.


Add: Nova TV Star

Channel Name
Nova TV Star
Alternative Names (optional)
No response
Network (optional)
No response
Owners (optional)
No response
Country
PE
Subdivision (optional)
PE-LOR
City (optional)
Yurimaguas
Broadcast Area
s/PE-LOR
Languages
spa
Categories (optional)
No response
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
http://radionovastar.com/tv-en-vivo/
Logo
https://i.imgur.com/OpSiFBP.png
Notes
No response

Please update your request:

the size of the logo should not exceed 512x512px

https://github.com/iptv-org/database/blob/master/CONTRIBUTING.md#channels

Updated.


Add Cinematic Mode Plugin

Add a "cinematic mode" for taking pictures without the ui and runelite overlays. The plugin only works in resizable mode.

Isn't this what the orb of occulus is for? (aside from our own overlays)

The orb isn't freely available in OSRS

^You can more or less recreate the orb of occulus using this and the detached camera dev tool


Tests fail on maint/0.22

After backporting #8874, various tests now fail. I suspect that because we now use testing 0.116 (previously it was 0.112), several test files other than the one I added in 0.116 changed, and tests have been adapted in main only.
Is there an easy way to find out which additional changes need to be backported? Otherwise, I'd revert my last 3 commits...
@larsoner @hoechenberger any suggestions?

Oh that's super unfortunate! I would say, just revert it.... and we should push out 0.23 sooner than later 😎

One option would be to remove the test that needs the 0.116 data, revert the testing data uptick, but keep the actual fix in the EEGLAB code. We don't usually do this but it seems okay in this case as a workaround to keep the fix (especially knowing the fix was not overly complicated)

Good idea, I'll try that @larsoner.

Let's see if this works: https://github.com/mne-tools/mne-python/commit/535c11093ae5dcecd2e33032e428fe4c77dcfb3c

Looks like you reverted the number but not the hash

🤦

https://github.com/mne-tools/mne-python/commit/b77d479ed6c0020d83e2fe36f3eb39ae8da0ebdd

@larsoner Windows 3.8 pip fails big time with a bunch of FutureWarnings in numpy...

Yes after a while after release the pip pre builds inevitably have errors, we can ignore them in this case at least

Uhm - why? After an MNE release you mean? I don't get it.
In any case, I guess this means that maint/0.22 is OK again?

Uhm - why? After an MNE release you mean? I don't get it.

The pip pre builds test against prelease versions of libraries like NumPy dev and SciPy dev etc. Usually:

Their changes require updates to our code once or twice a month to comply properly, which means inevitably our release falls behind and starts failing. It is fixable (we fix them in main after all) but...
Those libraries have long enough release cycles, we have fast enough releasy cycles, and people have slow enough upgrade patterns that it's often not worth the effort to avoid what is usually a harmless DeprecationWarning someone might hit.


⚠ Bofrost.com has degraded performance

In fc256c5, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 480 ms

Resolved: Bofrost.com performance has improved in ad83940.


Collection not required, but if present, subfield required

Is it possible to define a rule where a collection is not required, but if it exists (eg a user chooses to add an item to the collection) then subfield(s) are required?
I tried setting up a rule like this but got "TypeError: Cannot convert undefined or null to object" in console when the collection did not exist on certain records.

My way around it was to set minlength to 1 and just include a default item with values "None" for string subfields and 0 for number subfields.

You could potentially use a functional validations and define the validation for given field only if it's value is nonempty. Something along those lines
validations () {
  const def = {
    alwaysPresentField: { required }
  }

  if (this.myObject) {
    def.myObject = {
      name: { required }
    }
  }

  return def
}

Thanks.
When I changed my validations: {...} to validations() { return {...} } $v became undefined.
I was using version 0.2.0 so I thought maybe it doesn't have dynamic validations so I updated to the latest (version 0.4.2)
However the error I get now is TypeError: Cannot read property 'proxy' of undefined
Vuelidate was working fine when it was just an attribute/property instead of a function so I have no idea.

That's weird. It's true you have to update it, but the proxy error is not normal. Can you post an example on jsfiddle?

Too tricky to repro on jsfiddle as it's part of an app with lots of moving parts (and I'm guessing it's one of those parts interfering).
My best guess is that it could be caused by me using Firebase, and perhaps the validation creation is kicking in before the data is actually ready, causing it to not create $v -- again this is a wild guess, and you probably already have safeguards/procedures for handling setup of validation for async data yeah?

I found what was causing this error -- turns out it was some of the $trackBy: rules.
I commented-out all my trackBy lines which stopped the error, then uncommented them one by one to figure out which ones were causing the problem.
I can't see a pattern/reason as to why some validations can use trackBy while others throw that proxy error mentioned above, but if I work it out I'll update this thread.

I'm having the same error: TypeError: Cannot read property 'proxy' of undefined
After updating Vuelidate from 0.3.1 to 0.4.2
Using Vue and Nuxt, latest versions.

I'm also getting this error. It's caused by this line: https://github.com/monterail/vuelidate/blob/e60afe4941fe2de3683f2e4173b879fe0ec299e7/src/index.js#L247

I'd really like to get my hands on a repro. It has to be testable in the end anyway.
@Youdaman I suspect something like that could happen, thought he "creation of $v" i supposed to be a solved problem as it's created on demand, only in requested parts, as getters are evaluated. Can you check the data re you tracking with trackBy? Also the commented out trackers are a very big clue, if you could only extract that from your app.

I have the same issues too.
I use the vue-router for pushing the route by clicking button and sometime it throw out
Cannot read property 'proxy' of undefined

I think there are some funky precise lifecycle stuff going on and a hack biting back. I noticed a reliable way to trigger similar issue is to use a validation state inside a watcher created by watch object. I'm in the process of ditching the existing hacks out to make SSR work again, and it potentially can fix this issue too.

Yeah sorry for not coming back with a repro @Frizi but glad others have chimed in.

@Youdaman can you please check it in your code against ssr branch? I'm planning to release it soon, but first I want to know if it actually fixed the issue (among other ones).

I haven't had the error since, and I'm using $trackBy: 'index where index is a unique ID I generated for each item in array properties of my data.
My only guess was I was using a field that was either not unique or didn't exist (maybe I had a typo) and the code for $trackBy wasn't dealing with that edge case? Sorry I can't confirm/check further but I will let you know if I encounter the issue again! Perhaps @vip30 might be able to test for you.

Error "Cannot read property 'proxy' of undefined" seems to be caused by vuex-router-sync in my code. Can confirm it someone?

@masterix21 I don't use vuex-router-sync but I had the error so it might not be specifically that.

I'm suffering the same issue here saying that "Cannot read property 'proxy' of undefined'", using a boilerplate vue-webpack-plus.

I was suffering the same problem ("Cannot read property 'proxy' of undefined") and I agree with @masterix21. If I dont use vue-router-sync there is no problem.

I was also experiencing the error Cannot read property 'proxy' of undefined triggered by https://github.com/monterail/vuelidate/blob/e60afe4941fe2de3683f2e4173b879fe0ec299e7/src/index.js#L247. I am not using vue-router-sync. I am using nuxt.
Switching to the ssr branch seems to have fixed the issue.

@creativecoder that's great news! I'm going to soon work on it a little and release is it as next version.

I'm also seeing the Cannot read property 'proxy' of undefined error randomly pop up in our production logs after updating to Vuelidate 0.4.2. I haven't been able to reproduce it in development environment.
I'm using vue-router 2.2.0. The error is always triggered after user leaves the route.
Looking forward for the new version! Also it would be good to change the title of the issue or create new issue.

@Frizi  can confirm that using the SSR branch fixes the proxy issue for me.  On vue 2.3.2
Do you have a timeline for a release for that branch?

@Austio I just released that. Closing then. Thanks for confirmation!

this really needs a proper fix, a conditional check or at least prevent the 'Cannot convert undefined or null to object' error from happening.
my validators are as such:
validations: {
	array1: {
		$each: {
			name: {
				required: required
			},
			array2: {
				$each: {
					name: {
						required: required
					}
				}
			}
		}
	}
},

where array2 is an optional collection of each object in array 1


[stable/kiam] Better control of server host in agent CLI argument

What this PR does / why we need it:
Allow overriding server host in agent command line argument and connect directly via localhost when server is using host network.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[*] DCO signed
[*] Chart Version bumped
[*] Variables are documented in the README.md

@ewbankkit: I have addressed your comments. Does this look ok?

Bump

/assign @cpanato


Add Charles Freeborn to interested technical writers

What else do I need to do to make the file valid?

Hi -- please follow our instructions to add a single markdown file for your information. Do not edit existing files in this repository. Thank you!


Dev/sep actions

Dev/sep actions

#6

refactor: separate build job into 'pr_build' and 'push_build' - message Edit


Improve UI of navigation bar and add footer to the website

I will beautify the navigation bar of the website and add a footer section to it.
Do assign this issue under gssoc'22.

I would like to Improve UI of navigation bar and add footer to the website by adding animation using CSS some hover effects and in footer will also add social media icons with attractive images.
Kindly request u to assign this issue to me under GSSOC22.

I would like to improve the UI of the navigation bar and add a footer to the website by adding animation using CSS some hover effects in the footer. I can fix the bug in the navigation bar.
Kindly request u to assign this issue to me under GSSOC22.

I would like to More social media icons in the footer. Would also like to increase the font and size of icons to make it look better by increasing font size and and icon size. Footer section links are also not visible I will fix this bug too.
Please assign this issue to me under GSSOC 22.


HTTP Error 404: Not Found (caused by HTTPError());

[x] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2021.06.06
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log
[debug] System config: []
[debug] User config: ['--no-check-certificate']
[debug] Custom config: []
[debug] Command-line args: ['-u', 'PRIVATE', '-p', 'PRIVATE', 'https://study-for-fe-electrical.usefedora.com/courses/743489/lectures/13558322', '--verbose']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2021.06.06
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.17763
[debug] exe versions: ffmpeg 4.1, ffprobe 4.1
[debug] Proxy map: {}
[generic] 13558322: Requesting header
WARNING: Falling back on generic information extractor.
[generic] 13558322: Downloading webpage
[generic] 13558322: Extracting information
[Teachable] Downloading study-for-fe-electrical.usefedora.com login page
[Teachable] Logging in to study-for-fe-electrical.usefedora.com
ERROR: Unable to download webpage: HTTP Error 403: Forbidden (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpkqxnwl31\build\youtube_dl\extractor\common.py", line 634, in _request_webpage
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpkqxnwl31\build\youtube_dl\YoutubeDL.py", line 2288, in urlopen
  File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
  File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
  File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
  File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
  File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default

Description
Trying to download videos from a course and receiving this error:
ERROR: Unable to download webpage: HTTP Error 404: Not Found (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
I've tried:
-clearing cache,
-passing a cookies.txt file
-attaching header
-forcing ipv4
youtube-dl works fine if I try it on the videos that do not require a login by the way, it is JUST the paid videos that will not work even though I am passing the correct user account info.
Thanks

The Teachable login using username and pw is failing, and that breaks the extraction. Omit the username and pw and just pass a cookies file for a logged in session.
Someone with valid authentication details could try to debug the login. It's trying post the login form to a URL and it's being rejected. Maybe it's not finding the right URL in the page; maybe the login protocol has changed. --print-traffic could clarify the failure.

The Teachable login using username and pw is failing, and that breaks the extraction. Omit the username and pw and just pass a cookies file for a logged in session.

This worked - I thought I tried this previously but must've made a mistake somehow
Thank you


Generation of the End and the Nether normal

Is it possible to put so that I try the Nether and the End to generate the normal world? Because even if I put Default true, they still continue to generate nothing.
`"Dimensions": {
"End": {

  // Should end generate as in default world type? [default: false]
  "Default": true,

  // Should the main island be generated as normal? [default: true]
  "mainIsland": true
},

"Nether": {

  // Should nether generate as in default world type? [default: false]
  "Default": true
},

"Overworld": {

  // Should overworld generate as in default world type? [default: false]
  "Default": false
}

},`

Please use the bug report template to submit this issue, I need these information.