Fatal: wrong password or no key found - Even after init

Output of restic version
restic 0.10.0 (v0.10.0-38-ge9943e86) compiled with go1.14 on linux/amd64

How did you run restic exactly?
export AWS_ACCESS_KEY_ID="xxxxxxxxxx"
export AWS_SECRET_ACCESS_KEY="yyyyyyyyyy"
export AWS_DEFAULT_REGION="fr-par"
export RESTIC_REPOSITORY="s3:bucket-name.s3.fr-par.scw.cloud/restic"

restic -p ~/.restic-repo-password init
created restic repository f02eff4faa at s3:bucket-name.s3.fr-par.scw.cloud/restic

restic -p ~/.restic-repo-password backup Music/
Fatal: wrong password or no key found

What backend/server/service did you use to store the repository?
S3 Scaleway Object Storage - https://www.scaleway.com/en/object-storage/
Expected behavior
Data backuped
Actual behavior
Fatal: wrong password or no key found

Steps to reproduce the behavior
Every command fail after init:
restic -p ~/.restic-repo-password check
Fatal: wrong password or no key found

Do you have any idea what may have caused this?
No
Do you have an idea how to solve the issue?
No
Did restic help you today? Did it make you happy in any way?
Yes, of course, like every backup systems ;-)

I never used restic with Scaleway, but could this be caused by some eventual consistency (whereby restic doesn't see e.g. the key files right away after the init command)? Otherwise, what about permissions?

Not sure permissions are involved. I can list bucket files with s3cmd and same credentials.
s3cmd ls s3://bucket-name/restic/
                       DIR   s3://bucket-name/restic/keys/
2020-10-02 17:57       150   s3://bucket-name/restic/
2020-10-02 17:57       155   s3://bucket-name/restic/config

It works If I change RESTIC_REPOSITORY to:
export RESTIC_REPOSITORY="s3:s3.fr-par.scw.cloud/bucket-name/restic"

Dont know why the init worked but not check !!

Thanks for getting back on this. I suppose the "new" URL you use is more proper so if that solves the problem I too am all fine with closing this issue, as you did. Thanks!

For me, it still does not work, even after appending /restic to the repository URL - init works fine, but for the backup command, it always gives me a Fatal: wrong password or no key found error. The keys directory exists in the storage though.

@nxb303  Please open a new issue, there's not enough information on your setup for us to help. Please refer back to this issue if you think it is the same one.

I had a very similar fault with another S3 provider (non-AWS). The bucket URL is provided in two different formats, one is the endpoint URL https://s3.location.provider.com/ the other format is called Virtual Hosted-Style https://bucketname.s3.location.provider.com/.
I tried the Virtual Hosted-Style at first, I had set RESTIC_REPOSITORY to https://bucketname.s3.location.provider.com/repositoryname.
Restic seems to accept the virtual hosted style for the init command, but any attempt to connect immediately after creating the repo doesn't work. The error is Fatal: wrong password or no key found. Everything seems to work now after I defined the RESTIC_REPOSITORY in the format: https://s3.location.provider.com/bucketname/repositoryname


Impose a 60 requests/ 60 sec limits for osu! Commands

Will add in next version (0.3.0) with rewrite of command handler to use as an opportunity to clean up code in the process.

0.3.0
already released
ovypls


Green lines in the clothes during the stage 1 evaluation

It is my first try on this work!. I just trained the model in the stage 1 using python train.py -s data/m4c_processed -m output/m4c_processed --train_stage 1. However， when I evaluate the performance, it occurs obvious green lines in the character's chothes. What is the problem.  Thank you in advance!

Hi, sorry for the late reply!
The green line is due to inaccurate masks in the dataset, which we also mentioned in the supplementary materials of the article.


Cost models: move the dollar sign in price list

Describe the bug
Displaying price list, in the text: "X.YZ$ for every Rate-Unit" the dollar sign should be before the rate itself: "$X.YZ for every Rate-Unit"
To Reproduce
Steps to reproduce the behavior:

Go to 'Cost models'
Click on any cost model with rates.
See error

Expected behavior
the dollar sign should be before the rate itself: "$X.YZ for every Rate-Unit"

Just realized this is our 1000th issue!


Avoid a collision with Wagtail's initial home page slug

This PR matches the change in 17239da0459dbf4bc9098cb3909731097d5846c8 to initial_test_data.py. Wagtail's migrations create an initial page with the slug "home". When running ./setup.sh (or ./backend.sh or ./initial-data.sh) this will cause an error because the slug "home" already exists at the time when ./cfgov/scripts/initial_data.py is run.
Changes

Change the initial home page slug to "home-page" from "home"

Testing

Run ./initial-data.sh on a clean database.

Review

@cfpb/cfgov-backends

Notes
To ensure that our setup scripts aren’t regularly broken, I will also set up a periodic Jenkins job that runs them and reports any failures.
Checklist

[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[x] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

Note: It's likely Travis will fail for unrelated reasons. This is documented in #2236 and #2254.

$ ./drop-db.sh
$ ./initial-data.sh
$ ./runserver.sh
$ curl -s http://localhost:8000 | grep CFPB

👍


Don't show custom hover under context menu

@roblourens is this on desktop VS Code on Mac?

Yes

I can't repro on Windows. be820b8f425aa07a3514933e766666b022c6df35 may have fixed this issue. Are you still seeing it?

Yes

@roblourens do you still see this?


Support targeted Patches in the PostRenderer specification

This PR adds support for the target selector for strategic merge Kustomize patches, similarly as it's supported for the JSON6902 patches.
If the strategic merge patch have following form:
- target:
    group: apps
    version: v1
    kind: Deployment
    name: nginx
  patch:
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: nginx
    spec:
      template:
        spec:
          containers:
            - name: nginx
              image: nignx:latest

it'll be translated into appropriate targeted Patch in the effective Kustomize configuration.
Of course, the non-targeted form of the strategic merge patch is still supported:
- apiVersion: apps/v1
  kind: Deployment
  metadata:
    name: nginx
  spec:
    template:
      spec:
        containers:
          - name: nginx
            image: nignx:latest

The rationale behind it is a case in which certain Deployments or other K8s resources can be enabled or disabled with a Helm property. Now if we want to patch such a Deployment with the strategic merge patch (e.g. in order to add an env variable), the reconciliation will fail if the Deployment doesn't exist - this means we can't have a universal postRenderer configuration which will work regardless of the Helm values configuration.
The JSON6902 patches, with the explicit "target" section will work, as they'll simply ignore the missing targets. However, manipulating env variables with the JSON6902 patches is much harder than with the strategic merge patches and sometimes may not be possible. This is also true for other properties nested inside arrays, indexed by their "name" property (containers, envs, volumes, etc.)

Thanks for the review @hiddeco! I applied your suggestions and adjusted the tests. Should I rebase/squash the commits to have a clean commit history for this feature?

Yes, please rebase and squash :smile:

@hiddeco - done.

That was quick. Thanks for the feedback and merging it so fast, much appreciated!

The release will take a bit longer I am afraid, due to some extensive changes to the source-controller we are currently working on to finalize (which need to be taken into account on this side). If your patch is business critical, I can provide you with a RC build which needs to be combined with the updated CRD.

There's no need to create a RC build, but thanks for the offer @hiddeco!


Observe changes to value whit multiple selection

When multi is set (to true) the value property is an Array. In order to
let the value of the component be set by "the other side" of the value
binding, changes on the Array must be observed.

+1

Can you please show me an example (or even a test case) where this change makes sense?

Suppose that I push some item in the property which is bind to the value of an ember-select2, by observing changes on value.[], the select2 value will be updated, otherwise it will not.

+1


codeblocks: fix builds

Motivation for this change
This pull request allows codeblocks to be built on all four platforms.
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

I'm afraid this is not enough anymore since the gcc11 bump. Do you want to take another look?
https://hydra.nixos.org/build/174836160/nixlog/1

@Mindavi Setting -std=c++14 suffices. I'm checking if applying this patch also works.

cc @linquize (long shot since they don't seem to be active in nixpkgs anymore).

please submit the patches upstream and fetchpatch them

@Artturin The commit now uses patches from an unofficial mirror. The upstream is on SourceForge SVN, and I don't know of any way to fetch patches from it.


Get-PCCustomerUser - Return more than 500 users / paging?

Feature Request
I'll start by saying that I really appreciate your work with this module.
Is your feature request related to a problem? Please describe.
I'm trying to get all users of a customer of ours, but Get-PCCustomerUser can only return maximum of 500 users. How do I get the rest? I can't specify page, or a bigger size.
Describe the solution you would like
I'd like to either:

Specify a bigger ResultSize
Specify page, so that I can get pages until the result I receive is less than max page size (which would be the normal way of handling this I believe)

Describe alternatives you have considered
None so far, should be a easy fix/ addition. I'll write my own module if I have to.
Additional context

Maximum for ResultSize (500) is not listed in the documentation BTW
Get-Help -Name 'Get-PCCustomerUser' -Full

IMO it should be called "PageSize", and there should be a parameter "Page".

Hi Olav,
We have developed a new PowerShell module that leverages the Partner Center .NET SDK. This new module has this functionality and numerous others. You can find more information about this module at https://github.com/Microsoft/Partner-Center-PowerShell
Please let me know if you have any issues with the new module.

Thanks, I'll have a look tomorrow.

Got it working, thanks.
So PartnerCenterModule is/ will be deprecated?


Using on Client side (with Webpack)

How can I use Dialogflow V2 from my client, with Webpack?

+1

@Knowledge91 Did you already figure this one out? If so, could you please share some links to more details? :)

I outsourced Dialogflow V2 to a serverless lambda function, which is reachable over an API.
I launched a Serverless AWS Lambda, which I use to make calls to Dialogflow. The Lambda can then be called over AWS API-Gateway and communicate to the client.

Do you happen to know if there's a version of dialogflow-javascript-client for v2? https://github.com/dialogflow/dialogflow-javascript-client

@Knowledge91 ,
You might have some luck with the implementation in googleapis as they use axios which is client side and are REST only, try this code below:
'use strict';

const {google} = require('googleapis');
const path = require('path');

async function runSample () {

  const client = await google.auth.getClient({
    keyFile: path.join(__dirname, 'key.json'),
    scopes: 'https://www.googleapis.com/auth/cloud-platform'
  });

  const dialogflow = google.dialogflow({
    version: 'v2',
    auth: client
  });

  const result = await dialogflow.projects.getAgent({
    parent: 'projects/<your-project-id>'
  });

  console.log(result.data);

}

if (module === require.main) {
  runSample().catch(console.error);
}

// Exports for unit testing purposes
module.exports = { runSample };

I've been looking for this solution for 2 weeks...really poorly documented.

I've been trying to bundle this into Webpack, and getting a whole bunch of unresolved module errors. Agree that it's pretty poorly integrated.
I guess for now I'll stick to V1 of the API which is relatively simple to implement in comparison, but would love to hear what other way there is around this?

Greetings!  Tracking this over in #16.


[Task]: Extract Go Beam symbols for Playground

What needs to happen?
Parse symbols so they can be suggested by the editor autocompletion.
See https://github.com/apache/beam/issues/23304 as a model.
Issue Priority
Priority: 3
Issue Component
Component: beam-playground

.take-issue


[Feature Request] Convert array into single fragment

Hello, thank for this wonderful library.
I was wondering if you can add a utility which can convert array into single fragment, so you can ignore key prop.
I've implemented by myself.
import React, { Fragment } from 'react';
export default arr => React.createElement(Fragment, null, ...arr);

Don't know if it is useful enough to add to your library.

Just wondering why would someone want to avoid key prop? Are there any benefits of using Fragment over array with key?


Different rendering of absolutely the same text

Steps to reproduce
Tell us about your environment:

Puppeteer version: 5.0.0
Platform / OS version: I tried with this docker image, I guess it's Debian 9
URLs (if applicable): NA
Node.js version: 12.18.2

What steps will reproduce the problem?
I'm not sure whether this problem related to the puppeteer itself, but maybe I've missed something in the configuration. We have a test, which opens 2 pages, do something on that pages and takes screenshots, then compare them (screenshots tests).
Currently we got a strange result - there is very small difference between rendering the same text with the same font at the same coordinate, which cause test to fail.
Below you can see results for the same page opened twice:

1st run
2nd run
Diff

Here you can see the gif with the difference
Such kind of difference makes impossible to write screenshot-based tests with puppeteer. It's really floating issue with high rate of reproduction.
Quite possible I missed something and there is something I can configure to avoid this, but I didn't find it in the docs.
It's strange also because we already have similar tests in https://github.com/tradingview/lightweight-charts, and they works fine.
The issue looks related to https://github.com/puppeteer/puppeteer/issues/2410, but we don't compare headless and headful modes - it's all headless.
If you need any additional information, please tell me. It's a bit hard to prepare a repro for this (because it's non-public code atm and it takes some time to make it available without our internal stuff), but if it's important, I can do it.

We also got issues when upgrading puppeteer to latest version (which uses chromium 87). Our screenshot tests failed due to different text rendering in local machine, github actions or inside a docker containers...
We are using --font-render-hinting=none in all environments.
I spent an afternoon trying to workaround this and I finally gave up and reverted to v3.3.0 (chromium 83)


Linting Standards:

What linting standards and tools should be followed for code consistency? Pylint or Flake? Which one would you prefer?

Well, i have been using pylint in VS code. This woks fine.

Which ever.

I have used pylint till now.


How to retrieve the full edit history of the content (ipfs://) field?

This can't be done with my library, try looking at a profile's tx history of setText


Openings timeout not working

I have configured the openings like this:
  openings:
    - entity_id: binary_sensor.bedroom_door
      timeout: 00:00:59
    - entity_id: binary_sensor.terrace_door
      timeout: 00:00:59
    - entity_id: binary_sensor.terrace_window
      timeout: 00:00:59

However as soon as I open one of the doors/windows the AC is turned off (there may be a delay of a few seconds but that is probably a delay of the sensor reading itself). The delay of 59 seconds is not taken into account.
Have I configured it wrong or is this a bug?

I just ran into this same issue:
I have configured the openings with a 1 minute delay:
    openings:
    - entity_id: binary_sensor.openclose_11
      timeout: 00:01:00
    - entity_id: binary_sensor.openclose_13
      timeout: 00:01:00
    - entity_id: binary_sensor.openclose_14
      timeout: 00:01:00
    - entity_id: binary_sensor.openclose_15
      timeout: 00:01:00

However as soon as I open one of the doors/windows the AC is turned off. As per the documentation it says that the opening will need to remain open for however long the timeout parameter is configured before it turns off, but thats not how its working for me.
Any ideas?

Same issue for me

I am experiencing the same and came across this issue. I believe this was working previously in my case and seem to have been introduced recently

Could you please install the latest beta and chack if the issue still exists?

@nlindblo , @image82 Could you please install the latest beta and chack if the issue still exists?

Hi,
I tried it last night and it seemed to work;
at first I had the impression that a second event (on/off/on) of the contact was necessary but in subsequent tests everything seems OK.
it would be nice if in the future I could add the window status among the things visible in the cards;
and perhaps even if the recorded event indicated the cause of the thermostat change (at the moment a "generic" off/on is indicated).
thx so much for your job 🔝

@serlinGi I installed the Beta and in seems to have been fixed and working now. +1 for the indication of openings on the card itself.

@nlindblo , @image82 Could you please install the latest beta and chack if the issue still exists?

Issue was fixed! Thank you


Update .travis.yml

Add support for architecture ppc64le.  This is part of the Ubuntu distribution for ppc64le.
This helps us simplify testing later when distributions are re-building and re-releasing.
The build and test results are available at the below location.
https://travis-ci.com/github/nageshlop/azure-storage-python

Hi,
Could you review this request.

Thanks for the pull request! It looks great

Hi @xiafu-msft
Thanks for considering the request. Could you help to merge changes.


ja: Make docs/concepts/security/overview.md follow v1.19 of the original text

This is a Feature Request

What would you like to be added
Update docs/concepts/security/overview.md to follow v1.19 of the original (English) text.
Why is this needed
content/ja/docs/concepts/security/overview.md is outdated.
Comments
/language ja
/good-first-issue
File to update
https://github.com/kubernetes/website/tree/dev-1.19-ja.1/content/ja/docs/concepts/security/overview.md
Original
https://github.com/kubernetes/website/tree/release-1.19/content/en/docs/concepts/security/overview.md
diff between translated and v1.19
https://gist.github.com/ad26160f953d6a6e8c9e9305efbbd5c8
Note
Currently, we use dev-1.19-ja.1 branch. Please open a PR targeting the branch.
ref
https://kubernetes.io/ja/docs/contribute/localization/
If you have a question, feel free to ask us at slack.k8s.io #kubernetes-docs-ja channel.

/triage accepted

/assign

/close


crypto/tls: GetCertificate called on resumed sessions

GetCertificate is called just before checking the client session ticket. If the ticket is valid and the session is resumed, that call is probably pointless.
Off the top of my head, I can't remember why the server would need to know its own certificate in a resumed session, but there might be something I'm forgetting around renegotiation. Look into it, and if possible move the GetCertificate call after checkForResumption.

TLS 1.3 already has this behavior.
In TLS 1.2 during resumption there is a check that the ciphersuite from the resumed session is still acceptable. That check relies on the certificate private key type in order to determine if the suite uses an acceptable key exchange.
Presumably since the key exchange has already happened as long as the cipher is otherwise acceptable it's fine to just ignore whether it contains an acceptable key exchange since the shared secret has already been established and we don't need the cert key for another kex.


buil: Add MarkdownLint GitHub Action

This is the same setup from the dotnet/docs repo, which a slight change to ignore the TOC.md files.

https://github.com/MicrosoftDocs/cpp-docs/pull/1996 should probably land first, since otherwise the build will be red

@corob-msft Do you know what you'd like to do with this PR? Thanks.

@nschonni , @ktoliver
The reason I'm sitting on this PR is because it's in conflict with some experimental workflows we're using internally. That's why the workflows folder is currently listed in the .gitignore file. It lets us experiment with workflows independently of what gets picked up for shipping. This PR strips that protection and might let out workflows in progress that aren't ready for prime time. However, the workflow in this PR is also quite useful and something we want to provide to contributors in some form. So, no action just yet. But definitely a thumbs up and it's on the radar.

@corob-msft I've updated the .gitignore so that other workflows are ignored, but this one will be included.
Alternately, I could just force add the file and not touch the gitignore, but then any further changes will need to be manually force added as well

@corob-msft Something in PRMerger automation is causing this PR to appear as updated several times a day (although no change shows in the UI or conversation history). It seems to be associated with a label that's applied automatically; we are troubleshooting. Meanwhile, PR reviewers have to wade through a handful of PRs that are in the same unchanged but "updated" state as we process recently updated PRs throughout the day. I'm going to try adding hold-off and see if that stops the continual updating and floating the PR to the top as recently updated. It might not work, but that's the reason for this #hold-off. If it works, I will hold off on PR https://github.com/MicrosoftDocs/cpp-docs/pull/1996 also. Thanks!

@ktoliver Good to know, thanks!

@corob-msft There's a technical issue in PRMerger in which this PR continually floats to the top of the PR reviewer's to-do queue. Assigning different labels and hold-off have had no effect. Because this PR might be open for an indefinite length of time, would it be OK with you if we close it, and you can reopen it when you are ready to take action on the proposed updates? Please advise. Thanks.

Closing temporarily for reviewer assistance.

Thank you @corob-msft


[Don't merge] contracts: Run benchmarks

Run the benchmarks against master in order to check whether additional storage accesses where introduced by #7879. The changes here are necessary in order to run the benchmarks.

/benchmark runtime pallet pallet_contracts

/benchmark runtime pallet pallet_contracts


Explore passing actions in Connector and @connect decorator?

It would be more convenient to not have to call bindActionCreators directly inside the component, so I was thinking that we might able to add something to Connector and the @connect decorator to make this nicer? In addition, that would prevent calling bindActionCreators in render every time (which would provide an extremely slight performance benefit :)).
It seems like the idea of "connecting" could mean connecting to stores AND/OR connecting to actions, if the user wanted. Seems like Connector is perfect to just mean..."hey, connect this component (or child component) to Redux".
Thoughts?

We could also continue to pass dispatch...no real reason NOT to do that I don't think.

See https://github.com/gaearon/redux/pull/59#issuecomment-111214797

Oh cool! Didn't see that. Yah that's exactly what I'm talking about.

:+1: :)

So, even though I think this is still a good idea, I think that even if we abstract binding of action creators into Connector...we're still going to have to bind on every render due to the fact that dispatch is passed through props. Am I right about @acdlite ?

we're still going to have to bind on every render due to the fact that dispatch is passed through props.

Yeah..
Maybe we can introduce some binding mechanism closer to the root, so all actions end up in this.props.actionCreators?
import * as actionCreators from './actions/index';
<Provider redux={redux} actionCreators={actionCreators}>

Decorator version:
@connect(state => ({
  blog: state.blog
}))
export default class BlogDetailApp {
  render() {
    return <PostDetail {...this.props.actionCreators.BlogActions} {...this.props} />;
  }
}

Container version:
<Connector select={select}>
  {({ someState, actionCreators }) => <PostDetail {...actionCreators.BlogActions} {...this.props} />}
</Connector>

The dispatch function would also be available (and also passed from the top).

Is there any bad thing about binding them higher up? In the current version, did you purposely choose not to do that? Or was it just something you hadn't gotten to yet?
I have a working version of a modified Connector and @connect that you can pass actions to...seems like a decent API and keeps actions modularized and localized to the components that need them, but has a downside of still binding in render all the time (though that's not a huge performance hit, obviously).
But I can see the benefits of the approach of binding higher up.

I have a working version of a modified Connector and @connect that you can pass actions to

That's what we had but I was disappointed by the apparent complication of @connect. It felt too magical and tried to do many things (select data and bind actions) instead of just one.

but has a downside of still binding in render all the time (though that's not a huge performance hit, obviously).

It's not per se, but this makes it impossible for the contained component to implement shouldComponentUpdate efficiently. It'll get new functions every time. This is why I decided to remove that API.
Let'c continue the discussion in #86

Good call. I'll explore in #86 doing your suggestion.

Superseded by https://github.com/gaearon/react-redux/issues/1.

This is now done in https://github.com/gaearon/react-redux/releases/tag/v0.5.0.


feat(virtualizedRenderer): allow to pass content grid ref as property

allow to call grid methods by passing content gridref as vritualizedRenderer props

:tada: This PR is included in version 5.10.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add other architectures to Syncthing.Syncthing 1.23.3

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run

I'm not able to find the cause for this error. It installs and runs normally on a Windows 11 VM.

@stephengillie, I'm not sure how to do it, but on my branch the PATH variable is updated to C:\Users\myusername\AppData\Local\Microsoft\WinGet\Packages\Syncthing.Syncthing__DefaultSource, when it should be C:\Users\Ben\AppData\Local\Microsoft\WinGet\Packages\Syncthing.Syncthing__DefaultSource\syncthing-windows-amd64-v1.23.4. Even though the PATH is updated, PowerShell can't find the executable
Perhaps that's the source of the error you're talking about?

@torculus That is a known issue which appears in non-developer mode / user-context shells in Windows and I'm not sure if it's related to https://github.com/microsoft/winget-pkgs/labels/Validation-Executable-Error. Fortunately, the fix for the mentioned PATH issue was merged in https://github.com/microsoft/winget-cli/pull/3002 and will appear in the next release of WinGet

@stephengillie , is there anything else blocking this merge request? Once it goes through, I can rebase my other one to update to 1.23.4

/azp run

@stephengillie , is there anything else blocking this merge request? Once it goes through, I can rebase my other one to update to 1.23.4

@torculus,
Thanks for your patience.


Prebuilt binaries weren't released in GitHub Releases

Prebuilt binaries weren't released at v1.3.0 and v1.3.1.

It seems that the release step was removed.

https://github.com/omegion/ssh-manager/compare/v1.2.0...v1.3.0
https://github.com/omegion/ssh-manager/commit/f7b2ef42782f01832dcd51a3e8385334ce5ead5f

Could you release prebuilt binaries in GitHub Releases?

It is fixed now: https://github.com/omegion/ssh-manager/commit/96a3a9e868c7c2ceaffc80980e90da6bd15f7ced

Thank you!


Fix link error problem in MemPerfTest (#4)

If you have the latest version of googletest, you will get link errors when building the MemPerfTests project. This problem is caused by the ColoredPrintf function becoming a static function. This revision fixes it.

Close PR to change the code logic.


Avoid the need of into_binary

The contract changes make sense to me. However, I don't like the into_binary signature because:

The name sounds like it refers to Into but then it behaves very differently
Taking an owned data as an argument has no advantage in the implementation

This diff shows how to utilize the existing API.
What you can also do is just
    match msg {
        QueryMsg::Verifier {} => to_binary(&query_verifier(deps)?),
        QueryMsg::OtherBalance { address } => to_binary(&query_other_balance(deps, address)?),
    }

I love the code in the description and this is definitely better. However, the diff shows:
QueryMsg::Verifier {} => query_verifier(deps).and_then(|r| to_binary(&r)),
(Which is just reverting one commit)

If you make the PR match
    match msg {
        QueryMsg::Verifier {} => to_binary(&query_verifier(deps)?),
        QueryMsg::OtherBalance { address } => to_binary(&query_other_balance(deps, address)?),
    }

I'm very happy to merge (or I can make that change)

QueryMsg::Verifier {} => query_verifier(deps).and_then(|r| to_binary(&r)), comes from me as a way to adapt your code such that only a reference is used. Before your PR, the Binary was created in query_verifier already.
I will add the alternative version from the description now.

haha okay, I see it in your commit history now: https://github.com/CosmWasm/cosmwasm/pull/446/commits/05c66ae76f4ac1c802f8e095533bb182cd5b2930

With this merged, shall I finish migrating all the other contracts to this new format? (At least those in cosmwasm repo)

This is indeed a cleaner way than me trying to shove everything into map, and_then, ...

The issue is there is no API in Result that gives you a reference to the OK value but an owned error. .as_ref().and_then(to_binary) works for the value but not the error.

With this merged, shall I finish migrating all the other contracts to this new format? (At least those in cosmwasm repo)

Feel free to do so at any time. This is completely contract internal now and at the end of the day, it does not matter much at which point the conversion is done. I agree it is better type safety and readability.


Unable to copy files when using gcloud compute scp

Describe the Bug
Based on the example in #3069 I am attempting to use the "native" gcloud compute ssh functionality. Command execution works following the example, but file copies fail as the username for the ssh connection is unknown by the host running bolt. This results in a destination of @hostname:/dest/file/path passed to gcloud compute scp resulting in an error message as scp sees this as a local file location.
Expected Behavior
Files are copied to the remote computer.
Steps to Reproduce
Steps to reproduce the behavior:

Create an inventory that references a GCP instance and set options to use gcloud compute ssh

config:
  transport: ssh
    ssh:
    native-ssh: true
    ssh-command: [gcloud, compute, ssh]
    copy-command: [gcloud, compute, scp, --recurse]

Run a plan containing apply_prep($targets, '_run_as' => 'root')

Environment

Version 3.23.1
Platform Ubuntu Jammy (22.04) container host, Mac host
Centos 8 destination

Additional Context
I'm running this in a docker container due to other problems I've had with bolt on my mac.

Any ideas or workarounds for this issue? Not having this features severely limits our ability to use Bolt in our cloud environments.


ncaught TypeError: Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'

Same issue here
Home Assistant 0.110.1
installation_type: Home Assistant Core on Docker
Custom header version: 1.4.1
Browser: Chrome Version 81.0.4044.138 (Official Build) (64-bit)
ERROR (MainThread) [frontend.js.latest.202005191] http://8123/hacsfiles/custom-header/custom-header.js:1:15255 Uncaught TypeError: Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'.
resources:
  - type: module
    url: /hacsfiles/custom-header/custom-header.js

custom_header:
  compact_mode: true
  background: var(--app-header-background-color)
  elements_color: var(--app-header-text-color)
  active_tab_color: var(--state-icon-active-color)
  tab_indicator_color: var(--state-icon-active-color)
custom_header:
  background: 'rgba(155, 155, 155, 0.25)'
  button_text:
    options: '{{ date }} {{ hours24 }}:{{ minutesLZ }}'
  compact_mode: true
  swipe_animate: fade
  swipe_prevent_default: true

Is this 2 different dashboard's config? Just want to make sure you don't have custom_header in there twice. Also swipe navigation isn't included in custom header anymore. See here
So remove these from your CH config:
  swipe_animate: fade
  swipe_prevent_default: true

Looking into the error now

This has been addressed in the latest releases. Current release is 1.4.5. Close if this has been resolved, share any additional info if it has not.

Fixed. Thanks


cmake: Don't test whether the installed west is the bootstrapper

Of the 1.7s or so that CMake spends in Configure-time there is 0.1s
spent to determine whether west can flash or not. This is significant
compared to the usefulness of flash-check.
AFAICT when installing west there is no longer a two-step procedure
where first a bootstrapper that can't flash is installed, and then a
proper west is installed, so the risk of having installed the
bootstrapper is no longer something we should spend 100ms testing for.
This patch removes the check, thereby speeding up CMake by 100ms.
Signed-off-by: Sebastian Bøe<EMAIL_ADDRESS>

@galak : This is ready to be merged.


Build failure after adding webview2 crate

Thanks for making this crate, it's really nice.
When I initially installed it in my application, it broke the build. I can fix it by adding a dev-dependency to my application, but is there a way to avoid this?
Cargo.toml:
[package]
name = "my-app"
version = "0.1.0"
authors = ["waf"]
edition = "2018"

[dependencies]
webview2 = "0.1.0-alpha.6"

Build error:
C:\Projects\my-app› cargo build
   Compiling webview2 v0.1.0-alpha.6
error[E0432]: unresolved import `winapi::shared::winerror`
  --> ~\.cargo\registry\src\github.com-1ecc6299db9ec823\webview2-0.1.0-alpha.6\src\lib.rs:47:21
   |
47 | use winapi::shared::winerror::{
   |                     ^^^^^^^^ could not find `winerror` in `shared`

error: aborting due to previous error

I can build my application again after adding the following dev-dependency to my-app:
[dev-dependencies]
winit = "0.20.0"

If this is hard to fix, I think adding a note to the readme is fine!

It's because the winerror feature of winapi is missing in our dependencies. Should be easy to fix.
To workaround the problem, you don't need winit as a dev-dependency, just add winapi with the winerror feature as a dependency:

[dependencies]
winapi = { version = "0.3.8", features = ["winerror"] }

https://github.com/rust-lang/cargo/issues/1796

Fixed in 0.1.0-alpha.7.

Wow, fast turnaround! I can confirm that updating to 0.1.0-alpha.7 resolves the issue. Thanks!


perf(backend): only read similarityMeasure once

Hi, really cool project. I was just perusing the files when I noticed that this getSimilarityMeasure function is reading from the toml file on each invocation.
I would not imagine that this needs to be something that is modifiable at runtime, so I made it only ever check the file once on startup, and each successive invocation re-uses the cached value.
Totally minor performance optimization

Hi thanks for the PR! It reads the config each time as we planned to add a settings option for that in the settings page. This will be implemented when we switch from a settings menu to an entire settings page so there's more space for things like that. Some people might want to change how the similarity is calculated.


"NodeMenuItemAction.Custom"

@ctolene Please, provide a bit more details

@rychkog My apologies, this published when I pressed enter trying to enter a new paragraph.

@ctolene No worries. Thanks for the issue - will fix this approximately on weekends

Submitted a fix
#218

@ctolene Thanks! Merged

Will release with a bunch of other fixes


remove beyond the echo

I actually kinda like this thing... but it is just marketing for a computer game so I am not sure it really fits.

duplicate, see #399
Also, issue 400!


Feature hierarchy view and json data files

What
There are few changed introduced

I have moved data out of handlers into JSON files. Those now live inside of stub/data folder. Following front-end-renderer approach we generate source code returning (byte arrays) from static files allowing compile all of it into single binary.
Additionally there are two new endpoints /hierarchies and /hierarchies/{hierarchyId}
dimension data now comes with the hierarchical bool type field
/dataset/{datasetId}/dimensions/{dimensionId} now returns flat list of dimension options, if dimension is hierarchical: true you can than pass query param  /dataset/{datasetId}/dimensions/{dimensionId}?view=hierarchy to  return hierarchical view.
note: there is some hardcoding going on https://github.com/ONSdigital/dp-dd-api-stub/commit/1f723357e230d552ed7041bde2e9a4d0132b8ddb#diff-22f7c2e8169453d8cd5d06db8c4e0018R21

How to test
No unit tests yet! Might look into those next sprint.
Pull and run make debug. Take a look at following endpoints
http://localhost:20099/datasets/CPI15/

added  hierarchical and url for dimension

http://localhost:20099/datasets/CPI15/dimensions

added  hierarchical and url for dimension

http://localhost:20099/datasets/CPI15/dimensions/SP00001

added  hierarchical and url for dimension

http://localhost:20099/datasets/CPI15/dimensions/SP00001?view=hierarchy

added hasData: true if it is an endpoint, currently iterating through existing hierarchy adding hasData flag to every single item

http://localhost:20099/hierarchies/

list of available hierarchies

http://localhost:20099/hierarchies/CI_000641
http://localhost:20099/hierarchies/TIME_001

It might be good idea to simplify levelType into a single field if possible (another pull request perhaps)

Reviewers
Code @ian-kent please
Returned data @fenallen || @NeilMadded || @YetAnotherMatt
Sorry for large PR but there has been quite few changes introduced. Thought one PR will save you all reviewing time

every handler seems to unmarshal then marshal the data from assets? other than where we need to modify the data from the .json file, it can just return the bytes directly


Skip "." and ".." for ROMFS and LittleFS

Summary
just like other file system(e.g. SPIFFS and SmartFS): https://github.com/apache/incubator-nuttx/pull/1537
Impact
Testing

just like other file system(e.g. SPIFFS and SmartFS)

Not like all other file systems.  As I recall, ROMFS supports . and ..
I think we should not not remove support for . and .. but we should, instead, ADD support for . and .. to other file system.  What is the justification form removing . and .. here?  So solve a bug introduced by your other PR?  Not a good enough reason.

Closing... removing support for . and .. from ROMFS is not desirable.

The correct fix for consistencies would be to add support for the standard Unix . and .. entries to SPIFFS and SmartFS and NOT to remove the standard functionality from other file systems.  I created Issue #1539 to address this.


add: omitDataPath option to ajv.errorsText for ajv-errors custom …

var Ajv = require('ajv')
var ajv = new Ajv({ allErrors: true })
require('ajv-errors')(ajv)

var validate = ajv.compile({
  type: 'object',
  properties: {
    name: {
      type: 'string',
      minLength: 6,
      errorMessage: 'Your name should more than 6 characters'
    }
  }
})

validate({ name: 'xxx' })

console.log(ajv.errorsText(validate.errors))
// data/name Your name should more than 6 characters

But i want get raw errorMessage.
console.log(ajv.errorsText(validate.errors, { omitDataPath: true }))
// Your name should more than 6 characters

Thank you for the PR. I do not understand the problem that it solves though - what is the use case?

I don't want to return dataPath(eg: data/name) to user.
console.log(ajv.errorsText(validate.errors))
// data/name Your name should more than 6 characters

to
console.log(ajv.errorsText(validate.errors, { omitDataPath: true }))
// Your name should more than 6 characters

In this case the best approach is not to just errorsText method and process errors in your code to format the output for the users.
errorsText is a simple convenience method to simplify logging all errors in one line - it’s target audience is developers, not users.

@epoberezkin Thanks for your proposal, i was busy with my business, sorry for not have the time to complete this pr. closed for any other people could make a new pr.


How do I update a type on the fly using lodash.set?

🍩 Feature Request
Is your feature request related to a problem?
I have a function that updates the type of an object. It turns milliseconds into date objects.
Here's the idea:
const object = {
  lastUpdated:<PHONE_NUMBER>036,
  createdAt:<PHONE_NUMBER>019
}

const objectWithDates = msToDates(object, ['lastUpdated'])

typeof objectWithDates.lastUpdated // this should be Date

typeof objectWithDates.createdAt // should be number, since I didn't pass it in the array

Describe the solution you'd like
A way to change the type of each field in the object, dynamically, based on the array of paths I pass.
Describe alternatives you've considered
This is my code currently:
import set from 'lodash.set'
import get from 'lodash.get'
import type { F } from 'ts-toolbelt'

function msToDates<
  Obj extends object,
  Path extends string
>(obj: Obj, paths: F.AutoPath<Obj, Path>[]) {
  const next: Obj = { ...obj }

  paths.forEach((path) => {
    const ms = get(obj, path)
    set(next, path, new Date(ms))
  })

  return next
}

This works well. However, the ReturnType of the ms values I pass to paths is still a number, not a Date.
Teachability, Documentation, Adoption, Migration Strategy
This might already be possible, curious if you have an idea how to do it @millsp. Thank you!

Hey @nandorojo , that is because set is mutating and TS cannot keep track of mutations. Instead of a foreach, you should look into returning something like https://lodash.com/docs/4.17.15#mapValues. However, I'm not sure how the types work there. If your object is going to contain other fields than numbers, you might want to implement your own mapped type.

Is there a way to map a type from one to another, where certain fields are changed from number to Date?
type NumToDate<O, Paths> something like that?

Yes, I'll post the solution in a few minutes

Sweet, I figure I can use that as the return type of my function

Sorry, but I realized that the O.P utilities are behaving in a dissociative way (ie. on par with unions). So, I am not able to make the example work right now. It should have been as simple as this:
/* eslint-disable */

import type { S, F, O } from "ts-toolbelt";

declare function msToDates<O extends object, P extends string>(
  obj: O,
  paths: F.AutoPath<O, P>[]
): O.P.Update<O, S.Split<P, ".">, Date>;

const object = {
  lastUpdated:<PHONE_NUMBER>036,
  createdAt:<PHONE_NUMBER>019,
  subProperty: {
    milliseconds:<PHONE_NUMBER>221
  }
};

const objectWithDates = msToDates(object, [
  "lastUpdated",
  "subProperty.milliseconds"
]);

typeof objectWithDates.lastUpdated;
typeof objectWithDates.createdAt;

I'm going to mark this issue as a bug, because I think most people will want the O.P tools to be associative instead. Associativity is much harder to accomplish, while dissociation could just be done by distributing the path before hand. If you run the example, you will see that unions are produced (dissociative), it defeats the purpose in your use-case and probably any other use-case. Sorry about this!


Twitter taking a long time to load tweets

Is anyone else having this issue? I have this feed running on a few sites and all of them which use twitter are taking a long time to load (about 10 seconds). This is affecting the styling of some sites.
This seems to be consistent on all my sites but doesn't seem to have been raised by anyone else yet. It has been happening for about a week now.

same problem for me :(

yeah, me too, having same issue.

Problem seems to be again with the Codebird token at https://api.jublo.net/codebird/oauth2/token.

seems to be back up to speed again....hmmm


Passing through subscript and superscript (sub, sup) tags

... and ... should be passed through to Markdown.

@DmitriR can you please provide an example page/article/website so I can test on? Thanks!


Use separate RuboCop configs for formulae and core code.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

Lint/NestedMethodDefinition seems to be bugged, as it is the only cop that is not inherited from the .rubocop_todo.yml, at least on my machine. Let's see if CI has the same problem.

This looks good. Do you use an editor with Rubocop integration? If so, can you try to open a single Library/Taps/**/*.rb file and see if it uses the correct file?

I'm wondering if that'd be fixed by having the core file live in Library/Homebrew.

Do you use an editor with Rubocop integration?

No, @DomT4 could you test this? I guess the RuboCop integration probably expects to find a .rubocop.yml instead of .rubocop_formula and .rubocop_core.yml. In this case we could probably have Library/Homebrew/.rubocop.yml and Library/Taps/.rubocop.yml.

Sure, I'll yank it down locally and test it in the next hour or so.

I guess the RuboCop integration probably expects to find a .rubocop.yml instead of .rubocop_formula and .rubocop_core.yml.

I agree with your suspicion here though. Seems likely.

In this case we could probably have Library/Homebrew/.rubocop.yml and Library/Taps/.rubocop.yml.

Yup, that would be ideal I think. It's also how RuboCop itself expects configs to be structured, regardless of editor integrations.

Sorry for the massive delay, one of those days. One of those months really 😕.
This seems to have wildly confused Atom's Rubocop integration, heh. I now see messages about the class having too many lines, Ruby 1.9 hash syntax & even reverting double quotes to single quotes (which I'm not sure where that's coming from).
The plugin I use is this one, which you can't pass configurations to explicitly, it "sniffs" them, so I guess this somehow upset that sniffing. The same thing happens with Rubocop as well though, so perhaps a Rubocop issue rather than a linter issue (?). if I do:
cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-x11
rubocop --auto-correct

It changes all the double quotes to single. If I:
cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-x11
rubocop --auto-correct --config /usr/local/Homebrew/Library/.rubocop_formula.yml

It does behave as expected.

I now see messages about the class having too many lines, Ruby 1.9 hash syntax & even reverting double quotes to single quotes (which I'm not sure where that's coming from).

This is the default config of RuboCop, so it just doesn't pick up the _core.yml and _formula.yml files.

In this case we could probably have Library/Homebrew/.rubocop.yml and Library/Taps/.rubocop.yml.

Agreed this sounds ideal 👍

Ok, I renamed/moved the separate configs. @DomT4, you wanna test this again?

Seem to be back where we started 😢. Atom now nags me to change to the 1.9 hash syntax, and nags about guard clauses. Rubocop concurs:
cd /usr/local/Homebrew && rubocop --auto-correct --config /usr/local/Homebrew/Library/.rubocop.yml /usr/local/Homebrew/Library/Taps/homebrew/homebrew-x11

diff --git a/clusterit.rb b/clusterit.rb
index 5a9d544..25bf9d9 100644
--- a/clusterit.rb
+++ b/clusterit.rb
@@ -13,8 +13,8 @@ class Clusterit < Formula

   depends_on :x11

-  conflicts_with "couchdb-lucene", :because => "both install a `run` binary"
-  conflicts_with "pdsh", :because => "both install `dshbak`"
+  conflicts_with "couchdb-lucene", because: "both install a `run` binary"
+  conflicts_with "pdsh", because: "both install `dshbak`"

etc. Same thing if I cd into the tap directory and run a simple rubocop --auto-correct.

What if you rename /usr/local/Homebrew/Library/.rubocop.yml to something else that rubocop won't pick up, since this is not a complete config, but shared between core and formulae? (You'll need to update the other two to inherit_from the new name.)

I've updated this so that:

Library/.rubocop.yml is the file that's then inherited and overridden by Library/Homebrew/.rubocop.yml. This means it'll work for all taps by default without needing to create Library/Taps in Git (which I'm slightly 😨 of for no real reason).
Homebrew/core passes brew style and also editing a random file uses the Library/.rubocop.yml rules.
Disabled the rules that were stopping Homebrew/core from passing. We can iterate on more rules in a future PR.

Going to merge this when 💚 to avoid more Rubocop weirdness creeping into core CC @ilovezfs @DomT4

Thanks, @DomT4, for confirming. Merging this then.

😄 Lots of green, but not the right green. Could be a while, CI queue is kind of... intense at the moment. Thanks for working on this @reitermarkus, very much appreciate you taking the time.


Unique Number - III #988

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Code for Unique Number - III in C
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#988

@atarax665 Requested changes are done.


vdk-control-cli: allow cli users to explicitly set the user agent tag

Why
Users are looking to be able to determine where requests originated from when browsing the data.
How
We are going to let cli users explicitly set the user-agent header.
How has this been tested
TODO
Signed-off-by: murphp15<EMAIL_ADDRESS>

I've created corresponding issue in Github for the work explaining the problem and the solution - #1404

For the purposes of this change, you can use a local server with telemetry endpoint like https://webhook.site/ or https://requestbin.com/
Thought it is a good point. Our CICD deployment uses vcsa.vmware.com currently for telemetry - https://github.com/vmware/versatile-data-kit/blob/main/projects/control-service/cicd/deploy-testing-pipelines-service.sh#L97
It might be nice to extend vdk-heartbeat to check telemetry as well also


Implementation of ClearRect with masking support

Note: the second iteration is the change from the last CR.
The implementation was correct, it was the way how tests were that caused some failures, which are fixed now.
@DHowett-MSFT please take a look at the new heart art :)

Looks like git lfs is failing on build machines

so on the build machine, the generated image for one of the tests differ by a pixel :(
making it such that we check if the pixel is present.

Verbal extra sign off by @DHowett-MSFT  merging .


Fix git history on Releases/v2.x.x

Change Summary
Fix git history on Releases/v2.x.x
Reverted squash merge from release/v2.x.x (PR#860)
Cherry-picked each change contained in the squash-merge one-by-one.
This should remove conflicts with devel.

just a test


SHA256 mismatch

Release: https://github.com/armosec/kubescape/releases/download/v1.0.136/kubescape-macos-latest
Real SHA 256 sum is: c37c8b93b81e905cdc0ce1aed8b467296748e12991ffbb2ea80892b09dfd2db3
where the existing one: 3bb1e237b99d785e8303d7df6afe5d6b25bdd16363b81177b6f747f485ca7965
And why there is latest tag an all versions?
If i took for example: https://github.com/armosec/kubescape/releases/tag/v1.0.127, it is also latest?

Thank you.
Has been update since :)


Cannot install extension from source

following the instructions with the addition of installing typescript globally:
git clone https://github.com/joaompinto/asciidoctor-vscode
cd asciidoctor-vscode
npm install
sudo npm install -g vsce typescript
vsce package
code --install-extension *.vsix

I get an error when running vsce package:
vsce package
Executing prepublish script 'npm run vscode:prepublish'...
Error: Command failed: /bin/sh -c npm run vscode:prepublish

npm ERR! Linux 4.13.4-041304-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "vscode:prepublish"
npm ERR! node v4.7.2
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>vscode:prepublish: `tsc -p ./`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>vscode:prepublish script 'tsc -p ./'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the asciidoctor-vscode package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     tsc -p ./
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs asciidoctor-vscode
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls asciidoctor-vscode
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     vstest/asciidoctor-vscode/npm-debug.log

Running this command standalone in the shell:
tsc -p ./
src/AsciiDocProvider.ts(129,23): error TS2559: Type '(error: Error, stdout: Buffer, stderr: Buffer) => void' has no properties in common with type 'ExecOptions'.

A node version problem? My system:
vstest/asciidoctor-vscode$ uname -a
Linux XPS-13-9360 4.13.4-041304-generic #201709270931 SMP Wed Sep 27 13:35:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
vstest/asciidoctor-vscode$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 17.04
Release:        17.04
Codename:       zesty

Any assistance appreciated

The problem appears to be caused by explicit declaration of types:
In src/AsciiDocProvider.ts if I replace:
exec(cmd, (error: Error, stdout: Buffer, stderr: Buffer) => {

with the following, it functions correctly and the extension installs:
exec(cmd, (error, stdout, stderr) => {

I don't really know much Javascript and the documentation doesn't enlighten me -- perhaps strings are being passed instead of buffers for stdout/stderr?


Python-LinkedIn - Project Available on PyPI

Hello dear friends,
@ozgur @marshalllusher @abraham @ptwobrussell @SamuelMarks @EmlynC @ivankravets @devinbarry @joshowen @iacxc @yprez @jayzeng @Darune @adrian-sgn @johnfraney @lucavandro @mclate @scottydelta @mblakele @ismix @lyroge @marshyang @ikudriavtsev @kitsunde @ayyar @b3nelof0n
I would like to inform you that I have forked and mirrored the project python-linkedin which was originally created by @ozgur and converted to Python3 mainly by @marshalllusher.
I needed this library to work for a personal project and took the initiative to republish it to the PyPI Service : https://pypi.python.org/pypi/python3-linkedin
I hope you will appreciate this move, I have added quite some functionalities and tried to improve a little the documentation.
You all have been cited as contributors, and the contributions have been kept as yours during the mirroring process. I had to mirror and not fork due to the necessity of having "issues" enabled for the library.
Please feel free if you disagree with anything I've done. I really intended to make it more easily accessible for anyone.
Have a great week,
Best Regards,
Jonathan DEKHTIAR

Awesome! Thank you!

Glad to see this!


bug(mat-autocomplete): mat-autocomplete panel to be open by default without requiring user interaction

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
In my angular project, I wanted the mat-autocomplete panel to be open by default without requiring user interaction, I tried to open programmatically, opening the autocomplete panel seem not to be working
Additionally, I wanted the input to be in the block of mat-autocomplete and with autofocus.
The template looks like
<mat-autocomplete #auto="matAutocomplete">
 <input matInput  #inputField  placeholder="search text" />
  <mat-option *ngFor="let option of filteredOptions | async" [value]="option">
      {{ option }}
    </mat-option>
</mat-autocomplete>

Any help would be greatly appreciated.
Reproduction
StackBlitz link:
Steps to reproduce:
1.
2.
Expected Behavior
programmatically open the mat-autocomplete panel when the component is initialized.
Actual Behavior
not working, I don't see the panel opening
Environment

Angular:
CDK/Material:
chrome
macOS

Can you add your example to a StackBlitz to help debug the first part on why openPanel() isn't working in you case?
Why does the input need to be inside the mat-autocomplete in your case? Typically the structure is input is wrapped within a mat-form-field like in this example.

It is working regarding opening the openPanel and thank you @amysorto
The reason I needed the input to be inside is that I was experimenting for below issue
I tried to create a seamless and integrated look between an input and autocomplete dropdown by adjusting the box-shadow and other styling. But achieving a completely seamless appearance challenging due to the way Angular Material components are structured
Then I was trying a different workaround: what if I wrapped the input field in mat-autocomplete and made mat-autocomplete open it automatically?
I will close this issue, but if you have any idea or suggestions for second inquiry, I will appreciate it. thanks


20 paddingTop in header

Current Behavior
A gap (paddingTop: 20) appears just above the header when using StackNavigator. It appears between the statusbar and the header. The cause is a paddingTop: 20 style applied to SafeAreaView and can be seen in the Inspector of the react native debug tool. It only appears in portrait mode and not in landscape. I was testing on Android 5.1.1 (a nexus 7 tablet)
Expected Behavior
There should be no paddingTop: 20
Your Environment

software
version

react-navigation
1.0.0-beta.15

react-native
0.49.5

node
8.6.0

npm or yarn
5.5.1

I guess you mean you are using beta.16 ;)
Anyway this issue is a duplicate of https://github.com/react-community/react-navigation/issues/2854, we have already fixed it on master and we'll release a new version soon. In the meantime, by pointing at master you should not see this issue.

Ok, thanks!

@kelset I'm pointing at master but still have this issue (emulator Iphone 6, iOS 11.1). Is there a new property to set or it is a bug ?


[feature request] codemirror hints in dataset view

Context
add same codemirror hints in dataset view as we have in data tab for map view
Steps to Reproduce

go to dataset url
toggle switch from metadata to sql in bottom left
start writing sql

Current Result
there are no sql hits, no table name, no column names, no sql commands

Expected result
the hint dialog should appear with the autocomplete suggestions

investigating further, this is already working


NOT WORKING

Direct link kaanunnilla manh

OPEN TERMUX APP AND TYPE THIS
COMMAND
apt install wget && apt install git && wget https://bin.equinox.io/c/4VmDzA7iaHb/ngrok-stable-linux-arm.zip && unzip ngrok-stable-linux-arm.zip && ./ngrok http 80

AND AFTER THAT TYPE
cd CamHack
bash CamHack.sh
the direct link will appear

Still not working

Direct link kaanunnilla manh

Malayali😇 enikum kittika🙂


how can I use fastlane to build for different teams?

Question Checklist

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

Question Subject

I am automating builds for apps in various teams. match is a great effing tool to manage certs/profiles 👍 👍 👍 (three thumbs up for match). I know that match sets the provisioning profile but it seems like it doesn't set the distribution certificate for gym.

Question Description

anyone knows what xcode configuration should I use and what parameters should I pass to gym for making this possible? I have tried various various combinations, nothing worked. Tried both automatic and manual code signing..
xcode v9.2
fastlane v2.96

thank you for your reply.. but i am not having issues with profile selection. match is doing that perfectly and gym is picking it up.. issue is coming in selection of correct distrubution certificate.

@salmanasiddiqui Ohhhh, sorry! I must have misunderstood 😊 As long as your build setting for CODE_SIGN_IDENTITY is set to iOS Distribution and DEVELOPMENT_TEAM is set to the same team as what your profile/cert belong to, gym should pick up the correct one.
Do you have some output gym that you could paste here that show the build errors? That always helps when trying to debug from my end otherwise I'm just kind of blindly stabbing 😊

hmm so I have to modify the DEVELOPMENT_TEAM in xcode project settings?
I was looking for a way so that I can set DEVELOPMENT_TEAM="", and then just by using gym I would pass it on the fly.
yeah i will add information to this issue in few hours, sorry for not providing it already, but its like spending 10 mins on build lane to get that error.. and then I also want to share the output of some different combinations i tried.. So it will take me some time to upload all the relevant logs with redacted sensitive info

@salmanasiddiqui No problem at all! I know how things go 😊 You could also try setting the export_team_id option in gym to see if that does it for you? Its optional but it looks like it might work in your case

Thanks alot @joshdholtz I will give that a try. But before I do that, I would like to confirm export_team_id takes iTunesConnect team id or Dev Portal team id?

@salmanasiddiqui This should be the Dev Portal team id 💪

oh god man, thank you so much.. by using export_team_id I have successfully build ipa for different teams. Going to upload one just to confirm it is signed correctly.
I was trying to make use of codesigning_identity parameter of gym to resolve my problem but it introduced some more.
Can you explain me the use of codesigning_identity parameter? I know its not the right thread to ask this, but if you can just give a one liner explanation in your next response, i'd appreciate.

@salmanasiddiqui TBH, I don't know if I have ever used that myself 🙃 But I'm pretty sure its just for dynamically overriding the CODE_SIGN_IDENTITY in your build settings 🤔


Ring memory logging

Added support for logging of ring metadata (space, alignment, size, etc.) and updated several of the tools to use the new information.  This includes:

a new ring directory under /dev/shm/bifrost/<pid> where the metadata is stored
per-ring ProcLog metadata indexed by the ring name that includes:

space - where the ring is allocated
binding - NUMA binding, if applicable
alignment - allocation alignment, in bytes
ghost - size of the ghost region, in bytes
span - size of a span, in bytes
stride - stride size, in bytes
nringlet - the number of ringlets in use

updates to like_ps.py and like_top.py to work with the new structure in /dev/shm
a new script called like_pmap.py that provides some insight into memory usage in a pipeline
update to bifrost.ring.SpanBase.data_view() to support non-NumPy data types, i.e., 'ci4'
small changes to some of the "like" script to help suppress VMA messages
added a core keyword to the bifrost.ring[2].Ring.__init__() to set the NUMA binding for a ring

I'm not sure where the travis errors are coming from.  Do they look familiar to anyone?

The ctypesgen step failed (visible in the hidden build log), but it doesn't stop the build (I'll try to fix this soon).
Can't include string in memory.h (it has to be pure C).

Coverage increased (+0.1%) to 65.725% when pulling 4a67c8127b883b6cbe91ca624dfad1413a36f083 on jaycedowell:ring-info into 84891770f905b786d8c302695ad4928e80ee7a3a on ledatelescope:master.

Codecov Report

Merging #100 into master will increase coverage by 0.11%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #100      +/-   ##
==========================================
+ Coverage   67.17%   67.29%   +0.11%
==========================================
  Files          39       39
  Lines        3555     3568      +13
==========================================
+ Hits         2388     2401      +13
  Misses       1167     1167

Impacted Files
Coverage Δ

python/bifrost/proclog.py
27.27% <ø> (ø)
:arrow_up:

python/bifrost/ring.py
93% <100%> (+0.25%)
:arrow_up:

python/bifrost/ring2.py
88.67% <100%> (+0.21%)
:arrow_up:

Continue to review full report at Codecov.

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

Coverage increased (+0.1%) to 65.725% when pulling 2d2ef06a960c7b0ef32893c08d2733c600ed6853 on jaycedowell:ring-info into 84891770f905b786d8c302695ad4928e80ee7a3a on ledatelescope:master.

Coverage increased (+0.1%) to 65.725% when pulling 2d2ef06a960c7b0ef32893c08d2733c600ed6853 on jaycedowell:ring-info into 84891770f905b786d8c302695ad4928e80ee7a3a on ledatelescope:master.

Coverage increased (+0.3%) to 65.941% when pulling e2da49c6f641675b3b00cc0b4414cda5be7f5eed on jaycedowell:ring-info into 84891770f905b786d8c302695ad4928e80ee7a3a on ledatelescope:master.

Coverage increased (+0.3%) to 65.941% when pulling e2da49c6f641675b3b00cc0b4414cda5be7f5eed on jaycedowell:ring-info into 84891770f905b786d8c302695ad4928e80ee7a3a on ledatelescope:master.

Coverage decreased (-3.4%) to 62.195% when pulling 81427a08ce501a0f4b563d85ac45f21af9f99015 on jaycedowell:ring-info into 84891770f905b786d8c302695ad4928e80ee7a3a on ledatelescope:master.

Coverage decreased (-3.4%) to 62.195% when pulling 81427a08ce501a0f4b563d85ac45f21af9f99015 on jaycedowell:ring-info into 84891770f905b786d8c302695ad4928e80ee7a3a on ledatelescope:master.


Update specifying version pins version

This is a question rather than an issue.
While updating, when you specify the version, that version is pinned in paket.dependencies.
Is this correct? I couldn't find anything related to it in the docs.
I don't want to pin the version, I just want to update to that specific version and that's it.
I'm willing to send a PR either to fix this behavior or to introduce a parameter to the update command.
What do you think?

that is actually a very good question. @agross what do you think?

I think you are right. We should not add the version as a permanent requirement to the deps file. PRs welcome.

Sorry guys, I had little time during the last days. Does this mean paket modified the dependency file? If so, I think we should revert that decision. The depfile is the user's responsibility. Only the lockfile should be modified by us.
Alex
Alexander Groß
Tiny phone, tiny mail
On Thu, Aug 13, 2015 at 9:56 AM, Steffen Forkmann
<EMAIL_ADDRESS>wrote:

I think you are right. We should not add the version as a permanent requirement to the deps file. PRs welcome.
Reply to this email directly or view it on GitHub:
https://github.com/fsprojects/Paket/issues/973#issuecomment-130568527


Update Alpha to February 2020

Update alpha to February 2020, as that is the current alpha version. And it's also what the link points to.

@thomasclaudiushuber : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


refine markdown symbols

heading: using symbol of macro

list item: using symbol of enum

demo

Looks much better this way. Included in symbols-tree-nav.

Thank for noticing this PR.
Really hope this package would have more markdown syntax support.
If I had time I like to study how to parse list item and include them inside heading symbol
(like building TOC but for content inside each headings)
@nicolashainaux What are the features you like to add up for markdown?

@nicolashainaux What are the features you like to add up for markdown?

Well, no precise ideas, so far.
But including list item for inclusion inside heading symbols sounds really interesting. Only problem, I am pretty sure such a parsing feature relies only on the external parser.
Nevertheless, as the Linux binary parser provided with symbols-tree-view, I added an option in symbols-tree-nav to change the parser that is used. If you would like to try another parser, you can use this option for development.
I could also add another option or tweak the existing one in order to let the user define different parsers, depending on the file's scope (python/C/coffee-script/markdown etc.). If such an option would help you, I'd certainly add it.

Of course, if reworking the regex in the ctags file is enough, it would be good.
Something else: it could be nice too to add icons dedicated to markdown tags.
Anyway, don't hesitate to create a PR in symbols-tree-nav.

... If you would like to try another parser, you can use this option for development.

Thanks for pointing out s.t.nav supports custom syntax parser. I will have a try.

... Anyway, don't hesitate to create a PR in symbols-tree-nav.

Now I don't understand s.t.view architecture and I need more investigation to create PR.
IMO we can move to symbol-tree-nav for more discussion (maybe in a new issue page).

@liuderchi just created a new issue in symbols-tree-nav here, to continue the discussion.


Add polyfill and custom browser list

To avoid further issues like #102, we should add react-app-polyfill and also add a list of browsers to support using browserList. Then if a user visits our site using an unsupported browser version, we display a notice and send a link for them to find a modern browser.
Further reading:

https://create-react-app.dev/docs/supported-browsers-features/
https://github.com/browserslist/browserslist-useragent
https://github.com/browserslist/browserslist-useragent-regexp
https://github.com/browserslist/browserslist

This is something that could be added to dicty-hooks as useSupportedBrowsers or something similar.

react-app-polyfill is already bundled with react-scripts

react-app-polyfill is already bundled with react-scripts

Further thoughts:

browserslist-useragent is meant for server side use
browserslist-useragent-regexp has a bundle size of 53kb -- way too much for our apps

We are already using the bowser library to detect for IE. An optimal solution here is to use that inside of a custom hook.

Further thoughts:

browserslist-useragent is meant for server side use
browserslist-useragent-regexp has a bundle size of 53kb -- way too much for our apps

We are already using the bowser library to detect for IE. An optimal solution here is to use that inside of a custom hook.

I looked at the data for browsers used by our users from the last six months.
Chrome - 62%
Safari - 19%
Firefox - 6%
Edge - 3%
IE - 2.5%
Even though such a small percentage use IE, we should still support it where possible. For DSC, we will need to add a polyfill for the intersection observer API and also redefine the browserslist config.

I looked at the data for browsers used by our users from the last six months.
Chrome - 62%
Safari - 19%
Firefox - 6%
Edge - 3%
IE - 2.5%
Even though such a small percentage use IE, we should still support it where possible. For DSC, we will need to add a polyfill for the intersection observer API and also redefine the browserslist config.

The intersection-observer polyfill from W3C was added and the browserlist config was updated. I also removed the browser warnings and hardcoded browser versions.

The intersection-observer polyfill from W3C was added and the browserlist config was updated. I also removed the browser warnings and hardcoded browser versions.


fix typo

Hi @zqzzq - thanks for your contribution!
There are some standard format and submission rules the Kata community use that will be required to satisfy the CI system. Please see https://github.com/kata-containers/community/blob/master/CONTRIBUTING.md for more details - particularly on how to format the commits, such as:

signed off by
'Fixes' reference
format of commit message.

You can re-edit and re-push to this PR. Examples of the relevant git commands can be found in the above document.

Hello @zqzzq.  You may find it helpful to review this revised version of CONTRIBUTING.md, which @grahamwhaley references above.  The link above is a PR that is still under review.
When reviewing the link above, pay close attention to the Patch format and Pull request format for help with re-formatting your PR so it conforms to the CI requirements.  Reach out if you have questions.


Accepting any PR's from TDE's with full working examples e.g. full application

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[x ] feature request
[ ] support request => Please do not submit support request here, instead see use [gitter](https://gitter.im/mgechev/angular2-seed) or [stackoverflow](https://stackoverflow.com/questions/tagged/angular2)

Current behavior
n/a
Expected behavior
Have full blown samples  e.g. OData, Northwind, Grids with full CRUD, etc. , seed project can be modules, each module illustrating a real world dev use case
Minimal reproduction of the problem with instructions
n/a
What is the motivation / use case for changing the behavior?
No real world examples with full implementation
Please tell us about your environment:
Windows, etc.

Angular Seed Version: aaaaf75
Current

Node: node --version =
v6.11.2

Please let us know if we anyone or TDE's can start submitting PR's that illustrate real world dev use cases, thanks, something like this: e.g. https://github.com/OData/ODataSamples/tree/master/WebApi/v4

How is this related to Angular Seed?


tmaster exits with GLIB errors after intalling on Centos

Error I see in heron-executor-0.stdout:
01/11/2017 01:39:41 +0000:INFO: heron-tmaster stderr: ./heron-core/bin/heron-tmaster: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.18' not found (required by ./heron-core/bin/heron-tmaster)
./heron-core/bin/heron-tmaster: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by ./heron-core/bin/heron-tmaster)
./heron-core/bin/heron-tmaster: /usr/lib64/libstdc++.so.6: version `CXXABI_1.3.5' not found (required by ./heron-core/bin/heron-tmaster)
./heron-core/bin/heron-tmaster: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by ./heron-core/bin/heron-tmaster)
./heron-core/bin/heron-tmaster: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.19' not found (required by ./heron-core/bin/heron-tmaster)
./heron-core/bin/heron-tmaster: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./heron-core/bin/heron-tmaster)

What I did to get there:

Downloaded & ran the heron-client-install-0.14.5-centos.sh and heron-tools-install-0.14.5-centos.sh scripts, installing into /opt/heron
Submitted my topology jar with: heron submit local my-jar.jar com.my-org.MyTopo MyTopo

System information:
centos-release-6-8.el6.centos.12.3.x86_64
Steps I attempted to remedy:
sudo yum install libstdc++  glibc-devel
Normally I would not report this as an "issue" with the software itself, but I am beginning to suspect something could be wrong with the installation script rather than with my system.

we've seen similar issues when we were doing some internal experiments. will investigate.
cc @congwang

@objmagic okay, thanks. I noticed after filing this issue that the compilation instructions for Heron (which I hadn't looked at before since I was just installing with the script) mention it can only be compiled on CentOS 7. I'm on CentOS 6. Could that be the source of the issue?

@thomas4g that is very possible. The dynamically linked libstdc++ on your machine probably doesn't have the version heron-tmaster requires.

Yes - we provide the binaries for only centos 7 only. If you want to run on centos 6, you need to compile and install. Please follow the instructions in the web page.

On Jan 10, 2017, at 9:06 AM, Thomas Shields<EMAIL_ADDRESS>wrote:
@objmagic okay, thanks. I noticed after filing this issue that the compilation instructions for Heron (which I hadn't looked at before since I was just installing with the script) mention it can only be compiled on CentOS 7. I'm on CentOS 6. Could that be the source of the issue?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@kramasamy @objmagic OK, thanks very much.


Navigate by swiping the space bar

this is duplicate of #14. Will close this, as #14 has more detail.


[Access Request] table 36 "Sales Header" - GetContactAsCompany

Could you please change the access scope of the procedure  GetContactAsCompany to protected?
   //+Change
    //-local procedure GetContactAsCompany(Contact: Record Contact; var SearchContact: Record Contact): Boolean;
    protected procedure GetContactAsCompany(Contact: Record Contact; var SearchContact: Record Contact): Boolean;
   //-Change
    var
        IsHandled: Boolean;
    begin
        OnBeforeGetContactAsCompany(Contact, SearchContact, IsHandled);
        if not IsHandled then
            if Contact."Company No." <> '' then
                exit(SearchContact.Get(Contact."Company No."));
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11415.


Merge dev into master

Coverage remained the same at 90.22% when pulling 50b5d99420d0205819af3a55701de888391158ee on dev into 8846f34b3ed57d284cd1d9e24cdf958fc803330d on master.


Guidance for running the example in FederatedScope/scripts/

Although FederatedScope provides different kinds of scripts in FederatedScope/scripts/,  it is a little hard for users to understand these scripts without some guidance, such as which example is running for a certain script and how to use these scripts for customized tasks.
Maybe some detailed guidance on the scripts should be provided for users. Thanks :)

I have moved gfl-related scripts to gfl, and provided a README in this PR. Some config keys change for some reason, in other words, lots of scripts are outdated and unavailable. I suggest a hotfix to fix this problem.

We can add hyperlinks and docs in scripts as #305

The documents have been provided in FederatedScope/scripts/, many thanks for your contributions!


Superscript not work correctly for $^{87}$

L"$^{87}$Rb"

In Makie:

while this one L"$0^{87}$Rb" works correctly but I don't need 0 here.

Fixed by #90


Binary tree one

check this out

let me resolve the possible conflicts

conflicts solved: ready to merge the new updates now.


OpenFiles context provider does not work when folder is opened over Remote-SSH

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: Windwos 11 => Ubuntu 22.04.5 LTS
- Continue: v0.9.214 (pre-release)
- IDE: Visual Studio Code 1.93.1
- Model: Same with GPT-4o and Clause 3.5 Sonnet
- config.json:

{
  "models": [
    {
      "title": "OpenAI GPT-4o",
      "provider": "openai",
      "model": "gpt-4o",
      "apiKey": "<REDACTER>",
      "contextLength": 128000,
      "maxTokens": 4095
    },
    {
      "model": "claude-3-5-sonnet-20240620",
      "provider": "anthropic",
      "cacheSystemMessage": true,
      "apiKey": "<REDACTER>",
      "title": "Claude 3.5 Sonnet",
      "contextLength": 128000,
      "maxTokens": 4095
    }
  ],
  "slashCommands": [
    {
      "name": "edit",
      "description": "Edit selected code"
    },
    {
      "name": "comment",
      "description": "Write comments for the selected code"
    },
    {
      "name": "share",
      "description": "Export this session as markdown"
    },
    {
      "name": "cmd",
      "description": "Generate a shell command"
    }
  ],
  "contextProviders": [
    {
      "name": "code",
      "params": {}
    },
    {
      "name": "docs",
      "params": {}
    },
    {
      "name": "diff",
      "params": {}
    },
    {
      "name": "open",
      "params": {
        "onlyPinned": false
      }
    },
    {
      "name": "url"
    },
    {
      "name": "terminal",
      "params": {}
    },
    {
      "name": "problems",
      "params": {}
    },
    {
      "name": "folder",
      "params": {
        "nRetrieve": 150,
        "nFinal": 20,
        "useReranking": true
      }
    },
    {
      "name": "codebase",
      "params": {
        "nRetrieve": 150,
        "nFinal": 20,
        "useReranking": true
      }
    },
    {
      "name": "repo-map"
    },
    {
      "name": "tree"
    }
  ],
  "completionOptions": {
    "maxTokens": 4095
  },
  "tabAutocompleteModel": {
    "title": "Codestral",
    "provider": "mistral",
    "model": "codestral-latest",
    "apiKey": "<REDACTER>",
    "contextLength": 32000
  },
  "tabAutocompleteOptions": {
    "useCopyBuffer": true,
    "useFileSuffix": true,
    "multilineCompletions": "auto",
    "useOtherFiles": true,
    "useCache": true
  },
  "allowAnonymousTelemetry": true,
  "embeddingsProvider": {
    "provider": "openai",
    "model": "voyage-code-2",
    "apiBase": "https://api.voyageai.com/v1/",
    "apiKey": "<REDACTER>"
  },
  "reranker": {
    "name": "voyage",
    "params": {
      "apiKey": "<REDACTER>"
    }
  },
  "docs": []
}

Description
When using the Remote-SSH feature to edit a repo on a Ubuntu machine from my Windows machine, the OpenFiles context provider does not include any of the open files in the prompt. Manually including the same files using Files provider works fine. I have verified this by looking at the output in Output > Continue - LLM Prompt/Completion. When using Files the file shows up in prompt. When opening the file and using OpenFiles the file does not.
I've included the log output for both a prompt using Files and a prompt using OpenFiles.
To reproduce

Use Remote-SSH to open a folder on a remote computer
Open a file on the remote computer
Use the OpenFiles context provider to ask an AI model something
Check the output logs and see that the files contents were not included in the prompt

Log output
==========================================================================
==========================================================================
##### Completion options #####
{
  "contextLength": 128000,
  "maxTokens": 4095,
  "model": "gpt-4o"
}

##### Request options #####
{}

##### Prompt #####
<user>
\home\johan\ai-assist-dm\test.js
function foo() {
  console.log("Hello World")
}

test.js What does the function foo log?
==========================================================================
Completion:
The function foo logs the string "Hello World" to the console. When the function is called, it will execute the console.log statement, displaying the text "Hello World" in the console.
==========================================================================
Completion options
{
"contextLength": 128000,
"maxTokens": 4095,
"model": "gpt-4o"
}
Request options
{}
Prompt

What does the function foo log?
==========================================================================
Completion:
To determine what the function foo logs, we first need to see the implementation or at least a description of the foo function. Please provide the code or description, and I'll help explain what it logs.

@johansigfrids it looks like this has been solved by the PR linked above—can you verify that this is working in 0.9.215?

Yes this is fixed in v0.9.215 (pre-release) 🎉

@sestinj
Hello, when is this fix expected to be in the release version?
I use v0.8.54 and the problem still occurs there. I do not want to switch to pre-release though

@tobiajung We released 0.8.55 on Friday, so this should now be ready

@sestinj Yes it works, thanks a lot!


Update Glutin

This version of glutin doesn't compile on Windows 10:
[dependencies.glutin]
git = "https://github.com/jwilm/glutin"
rev = "af7fe340bd4a2af53ea521defcb4f377cdc588cf"

Upstream glutin 0.7.1 compiles fine:
glutin = "0.7.1"

This is blocking windows support.

Have you tried compiling alacritty with glutin 0.7.1? I'm curious what your results are

Have you tried compiling alacritty with glutin 0.7.1? I'm curious what your results are

This will not work. Alacritty is on a fork of glutin that has a very different Event::KeyboardInput variant:

Includes Mods which are the modifier keys as provided by the XEvent or equivalent on other platforms
Includes the UTF-8 string generated by the input sequence. This is normally provided in a separate event, but Alacritty needs both at once to either run a key binding or forward the string to the pty.

@jwilm Does it make sense to upstream your changes to glutin?

Very much so. I was hoping to make these changes for windows and wayland before opening a PR, but maybe they would be accepted separately.

Renamed this issue to suggest an action. We need to reapply my patches on top of what's now two projects (winit + glutin), upstream them, and then update Alacritty's dependencies.

Opened this issue https://github.com/tomaka/winit/issues/108 to see if upstream is willing to accept these improvements.

Submitted PR https://github.com/tomaka/winit/pull/112 to add keyboard modifiers to winit keyboard event.

https://github.com/tomaka/winit/pull/112 has been merged

@emersion Now we need to update glutin to this newer version of winit

Looks like with the merge of https://github.com/tomaka/glutin/pull/864 glutin's master branch is now using the latest winit. One step closer!

Linking a related PR: #554

I wonder if this would also fix #148...

It might; there's been a lot of work in this area in winit lately. There's also someone waiting to contribute some fixes for IME support which might be the fix needed for compose key.

Glutin/winit API churn is really high right now, and the latest candidate branch has some bugs. There's a new WIP to update current Glutin API to winit 0.7.1, and hopefully we can get on that.


Modify visibility changed slot to only update title if the object is visible

The visibilitychanged slot currently updates the title regardless of the visibility. We are seeing a crash when the viewer is shut down and a signal is sent to the visibilitychanged slot.  That executes some code which causes a segfault in the python process[1].  This PR changes the visibility changed slot to only update the title bar if the widget is visible.
[1]
  * frame #0: 0x0000000115cc96e4 QtWidgets`QWidgetPrivate::reparentFocusWidgets(QWidget*) + 356
    frame #1: 0x0000000115cb99cf QtWidgets`QWidget::setParent(QWidget*, QFlags<Qt::WindowType>) + 911
    frame #2: 0x0000000115cb82c0 QtWidgets`QWidgetPrivate::init(QWidget*, QFlags<Qt::WindowType>) + 688
    frame #3: 0x0000000115d73e5e QtWidgets`QFrame::QFrame(QFramePrivate&, QWidget*, QFlags<Qt::WindowType>) + 14
    frame #4: 0x0000000115dc3705 QtWidgets`QLabel::QLabel(QWidget*, QFlags<Qt::WindowType>) + 277
    frame #5: 0x0000000116503189 QtWidgets.abi3.so`Sbk_QLabel_Init(_object*, _object*, _object*) + 1497
    frame #6: 0x000000010015f84d Python`wrap_init + 12
    frame #7: 0x0000000100113e64 Python`_PyObject_FastCallDict + 143
    frame #8: 0x00000001001b17a2 Python`call_function + 439
    frame #9: 0x00000001001aa46b Python`_PyEval_EvalFrameDefault + 3078
    frame #10: 0x00000001001b1ee2 Python`_PyEval_EvalCodeWithName + 1638
    frame #11: 0x00000001001b281b Python`_PyFunction_FastCallDict + 447
    frame #12: 0x0000000100113e99 Python`_PyObject_FastCallDict + 196
    frame #13: 0x0000000100113fa3 Python`_PyObject_Call_Prepend + 131
    frame #14: 0x0000000100113d1e Python`PyObject_Call + 101
    frame #15: 0x000000010015f7d1 Python`slot_tp_init + 57
    frame #16: 0x000000010015c782 Python`type_call + 178
    frame #17: 0x0000000100113e64 Python`_PyObject_FastCallDict + 143
    frame #18: 0x00000001001141fa Python`_PyObject_FastCallKeywords + 97
    frame #19: 0x00000001001b17a2 Python`call_function + 439
    frame #20: 0x00000001001aa4fb Python`_PyEval_EvalFrameDefault + 3222
    frame #21: 0x00000001001b28e0 Python`_PyFunction_FastCall + 110
    frame #22: 0x0000000100113e99 Python`_PyObject_FastCallDict + 196
    frame #23: 0x0000000100113fa3 Python`_PyObject_Call_Prepend + 131
    frame #24: 0x0000000100113d1e Python`PyObject_Call + 101
    frame #25: 0x000000011126f146 libpyside2.abi3.5.14.dylib`PySide::SignalManager::callPythonMetaMethod(QMetaMethod const&, void**, _object*, bool) + 534
    frame #26: 0x000000011126eb77 libpyside2.abi3.5.14.dylib`PySide::SignalManager::qt_metacall(QObject*, QMetaObject::Call, int, void**) + 519

Description

Type of change

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

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

since we're not already getting this error in our tests, it seems like testing for it might be tough. If, for instance, we try to force send the signal after the viewer is closed, I think we'll just get an object does not exist error, and not a segfault (or we'd be seeing one already).   @ttung, any ideas?

merging.  Really not sure how to create this bug to fail a test.  We can come back to it in a future PR if it ever comes up again (but I doubt it will).


Minidlna: Allow more configuration options

Motivation for this change
"As a minidlna user", i'd like to have more setup option choices.

At the moment, we have the choice between:

having a subset of options
override completely the full configuration ("losing" the existing minimal subset)

This PR allows to:

configure some other options
configure the ones not yet disclosed in nix (extending the
existing minimal subset). This matches what is done for example in the sshd service.

Things done

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

Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions (debian with nix)

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)

Added test on that service.
I followed the doc about tests [1] though which i think is a better link
https://nixos.org/nixos/manual/index.html#sec-nixos-tests

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"

I'm still not sure what that does but it seems to have worked:
$ git reset --soft origin/master  # now there is wip
$ nix-shell -p nox --run "nox-review wip"
...
Result in /run/user/1000/nox-review-1xmyktwu
total 0
lrwxrwxrwx 1 tony tony 67 Mar  8 18:36 result -> /nix/store/l7lzfp2i0yizm7grylcrmkikm96hmx82-nixos-system-nixos-test

[x] Determined the impact on package closure size (by running nix path-info -S before and after)

Not sure i did this correctly:
$ git checkout master
$ nix-build -A minidlna
$ nix path-info -S ./result
/nix/store/1283pa3i7yyjpz7aana2rncq41qjwkxd-minidlna-1.2.1        141423736
$ git checkout minidlna-update-configuration
$ nix-build -A minidlna
$ nix path-info -S ./result
/nix/store/1283pa3i7yyjpz7aana2rncq41qjwkxd-minidlna-1.2.1        141423736

[x] Assured whether relevant documentation is up to date
~> every new option opened has the docstring updated as well

[x] Fits CONTRIBUTING.md.
as far as i could tell ;)

[x] Tested execution of all binary files (usually in ./result/bin/)

It's a service, i don't know how to test that without actually
installing it...  Any pointer on that is very welcome, thanks.  (I
searched quite some time at nixpkgs, nixos, and nix manuals without
quite the answer i hoped for)
So, i settled on testing it with my rpi3 (aarch64), so:

[x] disabled the mainstream service
[x] import this patched version
[x] define what i wanted as setup

Excerpt:
  ...
  disabledModules = [ "services/networking/minidlna.nix" ];
  imports = [
    ./override-minidlna.nix  # <- the pr's patch
  ];
  services.minidlna = {
    enable = true;
    mediaDirs = [
      "PV,${path}/family"
      "V,${path}/judo"
      "V,${path}/courses"
    ];
    friendlyName = "rpi3";
    rootContainer = "B";
    extraConfig = ''
      album_art_names=Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg
      album_art_names=AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg
      album_art_names=Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg
      notify_interval=60
    '';
  };

[x] built
[x] installed
[x] runs fine with the new configuration \m/

tony@kids> cat $(systemctl status minidlna.service  | grep minidlna.conf | awk '{print $7}')                                                                                ~
port=8200
friendly_name=rpi3
db_dir=/var/cache/minidlna
log_level=warn
inotify=yes
root_container=B
media_dir=PV,/family
media_dir=V,/judo
media_dir=V,/courses

album_art_names=Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg
album_art_names=AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg
album_art_names=Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg
notify_interval=60

Cheers,

Fixed mixed tab/spaces characters.

@Infinisil would be real nice to be able to point someone to an RFC regarding module options and config files right now... 😃

@ardumont how do you feel about something like this? https://github.com/NixOS/nixpkgs/compare/master...aanderse:minidlna
See https://github.com/Infinisil/rfcs/blob/config-option/rfcs/0042-config-option.md by @Infinisil for reference.

@ardumont how do you feel about something like this?
master...aanderse:minidlna See
https://github.com/Infinisil/rfcs/blob/config-option/rfcs/0042-config-option.md
by @Infinisil for reference.

That sounds about right and way more sustainable in the long run indeed.
Thanks for the pointer, I understand the current limitations. I'm not
sure i understood all the points described in the document referred to
though (i'd need another pass ;).
In any case, one remark in the current context, the mediaDirs option
could be dropped altogether.  That'd simplify a lot the derivation
(well the let configFile definition at least).
To demonstrate that this specific option can be repeated, i suppose
adding 2 media dirs in the literal examples would help.
I imagine you kept it for backward compabibility ;)

I specifically kept mediaDirs because the service won't effectively operate without specifying media directories. Generally speaking any option for which there cannot be a default value and the user must specify for the service to run probably deserves a NixOS option with documentation.
I like to see the new config option as something which usually shouldn't be required to get a service up and running in a usable state.
The loglevel was kept for backwards compatibility, though. In a release or two it should probably be removed.

Right, that sounds like sane choices indeed.

@Infinisil do you feel like reviewing https://github.com/NixOS/nixpkgs/compare/master...aanderse:minidlna as an alternative to the code in this PR? I'd like to hear your thoughts on the proposed code because the goal of this code is to spread the word of your new RFC :smile:
Bonus points if you write something really cool to replace my horrible toKeyValue implementation :wink:

@grahamcofborg test minidlna

ping (triage)

ping (triage)

pong?
;)

@ardumont: Can you squash fixup commit(s?) and prefix commits with "nixos/minidlna:"?

@ardumont: Can you squash fixup commit(s?) and prefix commits with "nixos/minidlna:"?

done