While generating pdf, landscape option doesn't work

Steps to reproduce
Tell us about your environment:
We are trying to generate pdf using puppeteer. Previously we had the landscape option working on Puppeteer 1.5.0 and node 8.9.4. But, after we moved around the code and updated the node and puppeteer versions to 8.15.0 and 1.11.1 respectively, the landscape option tends to generate a portrait instead of a landscape.

Puppeteer version: 1.11.1
Platform / OS version: ubuntu
URLs (if applicable):
Node.js version: 8.15.0

Please include code that reproduces the issue.
function generatePDF(html, options) { // options has landscape param set to true or false
browser = await puppeteer.launch({ args: this.puppeteerArgs });
page = await browser.newPage();
const session = await page.target().createCDPSession();
  await session.send('DOM.enable');
  await session.send('CSS.enable');
  await page.goto(`data:text/html,${html}`, { waitUntil: 'networkidle2' });

  this.logger.debug('generatePDF - creating pdf buffer..');
  const buffer = await page.pdf(options);
  await page.close();
  await browser.close();
  return buffer;

}
What is the expected result?
generates a landscape view
What happens instead?
generates a portrait view

Have you tried altering the CSS rule @page?
@page {
    size: auto;
}

I'm having the same issue. I've tried suggestions here and in #4505 and many variations and combinations thereof. Even tried explicitly setting width and height options. I cannot get puppeteer to render a PDF in landscape format.
Puppeteer v1.17.0
Node v8.11.4
Simplest code is below, but please note that I did try the suggestions suggested by @toix and in #4505
      ...
      page = await this.createPage(url, { timeout, waitUntil, cookies });
      const opts = {
        landscape: true,
      };
      const buffer = await page.pdf(opts);

I'm having the same issue with:

Puppeteer version: 1.19.0
Platform / OS version: Linux (Fedora 30)
Node.js version: 10.16.0

Even if I set the landscape option to true, page.pdf still generates a portrait oriented PDF.

The same problem here, landscape: true is not working...

+1 same here... landscape: true not working...

+1 same here, landscape not working.

+1 same issue for me. A workaround that works for me right now is to omit the landscape parameter entirely and just set width and height. Only then can I get a landscape orientation to work.

I'm using PuppeteerSharp v1.20.0. I confirm that landscape option doesn't work. Explicitly setting page width & height didn't work also. However,  using page.addStyleTag worked for me. You can try
page.addStyleTag(
{'content': '@page { size: A4 landscape; }'}
)

Thanks @JandosKh! This worked for me.
Just to add to the solution, in case someone run into the same issue, at first it was not working for me because I was running the command before loading the page. Make sure you run the addStyleTag command after loading the page.
Thanks

We had that issue today, but we got it working by calling await page.emulateMedia('screen'); before generating the PDF. After that, landscape : true was working.

Seems to be working fine for me:
const browser = await puppeteer.launch();
const page = await browser.newPage();
const options = {
  path: 'pdf/filename.pdf',
  format: 'A0',
  printBackground: true,
  landscape: true,
};

await page.goto('https://somewebsite.com', { waitUntil: 'networkidle2' });
await page.pdf(options);
await browser.close();

This generates a landscape oriented PDF for me. If I leave out the landscape: true in the options const, I get a portrait oriented PDF.

什么时候fixed it ??????

Worked:
def to_pdf
url = request.url.remove("/to_pdf.pdf")
Grover.new(url, format: 'A3', emulate_media: 'screen', landscape: true ).to_pdf

Good morning, everyone
CSS
@page {
    size: A4 landscape !important;
}

Node.js
const browser = await Puppeteer.launch({ headless: 'new' });
const page = await browser.newPage();
await page.setContent(HTML, { waitUntil: 'domcontentloaded' });
await page.emulateMediaType('screen');
const pdf = await page.pdf({
    path: pdf_filename,
    margin: { top: '0px', right: '0px', bottom: '0px', left: '0px' },
    printBackground: true,
    format: 'A4',
    landscape: true
});
await browser.close();

I hope this helps.


[assemble] java-archive generates JAVA_OPTS with wrong format

Task List

[x] Steps to reproduce provided
[ ] Stacktrace (if present) provided
[ ] Example that reproduces the problem (link to git repository is ideal)
[x] Full description of the issue provided (see below)

Steps to Reproduce

git clone https://github.com/jreleaser/helloworld-java-bin.git
Modify assembler configuration to look like this

assemble:
  javaArchive:
    helloworld:
      active: ALWAYS
      formats: [ ZIP ]
      fileSets:
        - input: '.'
          includes: [ 'LICENSE' ]
      mainJar:
        path: target/{{distributionName}}-{{projectVersion}}.jar
      java:
        options:
          - -Dfoo=foo
          - -Dbar=bar

jreleaser assemble

Expected Behaviour
Generated launcher should contain
 JAVA_OPTS="-Dfoo=foo -Dbar=bar"

Actual Behaviour
Generated launches contains
JAVA_OPTS="[-Dfoo=foo, -Dbar=bar]"

Environment Information

Operating System: N/A
JReleaser Version: 1.5.0
JDK Version: N/A

cc: @bmarwell

🎉 This issue has been resolved in v1.5.1 (Release Notes)


Select JavaScript framework

Hey Bret, as promised, here are the frameworks/libraries we've recently considered for some of our own apps at Mann Library. We haven't fully evaluated all of these, an any that we did were done so under the context of supplementing/extending a Rails app, so not sure how helpful this will be.

Angular 2
Bacon
Cycle
Koa
Meteor
Mithril
React
Sails
Vue

Express based:

Keystone
Kraken
MEAN

I hope this doesn't only add to the madness :)

Hi Nick,
Thanks a bunch for the links, I'm tossing a few comparison articles here as well.
Bret
http://blog.backand.com/angular-2-vs-react/
<EMAIL_ADDRESS>http://www.ociweb.com/resources/publications/sett/comparison-of-angular-2-and-react/

Some more reading: http://www.sitepoint.com/react-alternatives-preact-virtualdom-deku/

Angular 2 Release Candidate notes: https://github.com/angular/angular/blob/master/CHANGELOG.md

Going with Angular 2!


Cannot iterate children at proper order

Nodes order is important sometimes. I think, it is need to add _children array for proper order iterating, something like this:
--- xmlToJSON.js-orig   2016-05-05 13:37:23.096356807 +0700
+++ xmlToJSON.js        2016-05-05 17:39:14.599282243 +0700
@@ -156,7 +156,9 @@
                     }

                     vContent = xmlToJSON.parseXML(oNode);
-
+                    if(!vResult['_children']) vResult._children=[];
+                    vResult._children.push(vContent);
+                    vContent._tagname = sProp;
                     if (vResult.hasOwnProperty(sProp)) {
                         if (vResult[sProp].constructor !== Array) {
                             vResult[sProp] = [vResult[sProp]];

PS Sorry for my english

Have you tries setting childrenAsArray: true in the config options?  This should preserve the order.  If I have misunderstood your concern, can you post a sample?  Thanks.

copy((xmlToJSON.parseString("<root><a-two /><z-one /><a-two /></root>", {childrenAsArray: true})));
{
  "_children": [ /* Skip document top-level children tree */  ],
  "root": [
    {
      "_children": [
        {          "_tagname": "a-two"  /* Right order */        },
        {          "_tagname": "z-one"  /* Right order */        },
        {          "_tagname": "a-two"  /* Right order */        }
      ],
      "a-two": [ /* <------- Two elements are putted to list */
        {          "_tagname": "a-two"        },
        {          "_tagname": "a-two"        }
      ],
      "z-one": [  /* And here was one? */
        {          "_tagname": "z-one"        }
      ],
      "_tagname": "root"
    }
  ]
}

Also, JS doesnt guarantee key order in the dict (but all current realization yes).

This is the intent of setting 'childrenAsArray: true' in the options.  Have you tried this approach?

As you may see in my last post, "childrenAsArray: true". It causes joining same named tags into array, but tag order was losted. Once more example (original lib, w/o patch):

copy((xmlToJSON.parseString("", {childrenAsArray: true})));
{
"root": [
{
"a-two": [
{          "_text": [            null          ]        },
{          "_text": [            null          ]        }
],
"z-one": [
{          "_text": [            null          ]        }
]
}
]
}

Compare tags order in the source xml and result object

I see.  If you don't mind, go ahead and push a patch and I will review and
test it. I am traveling this week, but am planning on publishing a new
release sometime next week.
Thanks.
On Aug 15, 2016 9:46 PM, "eliseevmikhail"<EMAIL_ADDRESS>wrote:

As you may see in my last post, "childrenAsArray: true". It causes joining
same named tags into array, but tag order was losted. Once more example
(original lib, w/o patch):
copy((xmlToJSON.parseString("", {childrenAsArray: true})));
{
"root": [
{
"a-two": [
{ "_text": [ null ] },
{ "_text": [ null ] }
],
"z-one": [
{ "_text": [ null ] }
]
}
]
}
Compare tags order in the source xml and result object
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/metatribal/xmlToJSON/issues/21#issuecomment-240000030,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFAjfGC99BjEKr1q_Pz96c6ofLQwqn-fks5qgUCQgaJpZM4IXzU3
.

This will require a significant change to the format of the JSON representation; possibly something like
[
 {nodetype, tag, namespace , attr [], children []},
 {nodetype, tag, namespace , attr [], children [
    {nodetype, tag, namespace , attr [], children []},
    {nodetype, tag, namespace , attr [], children []},
    {nodetype, tag, namespace , attr [], children []},
 ]},
 {nodetype, tag, namespace , attr [], children []},
]

This will require a new way of searching/walking the nodes as well.

I dont like losing the tag names as keys and will have to rethink this approach.  The current grouping methodology meets the original intent and I am worried about a find() or match() style api for walking the object array.


Move some cop options to config/default.yml

This commit is a change similar to #5271.
This commit unifies the setting place by moving those settings of Rails/Blank cop and Rails/Present cop from config/enabled.yml to config/default.yml.
Related PR #5854.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[ ] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Run rake default or rake parallel. It executes all tests and RuboCop for itself, and generates the documentation.

👍


Model::offsetExists calls getAttribute and may result in double calls

Laravel Version: 7,30.2, 8.23.1, dev-master
PHP Version: 7.4, would apply to others as well
Database Driver & Version: not related to database

Description:
This is the current implementation of Model::offsetExists():
    /**
     * Determine if the given attribute exists.
     *
     * @param  mixed  $offset
     * @return bool
     */
    public function offsetExists($offset)
    {
        return ! is_null($this->getAttribute($offset));
    }

It calls getAttribute(), which may call actual functions as in the case of accessors. This is a problem when there's a combination of checking/getting:
if (isset($model['myattribute'])) {
   $myvar = $model['myattribute'];
}

For normal fields this is ok, but when you have an accessor, which may not be pure, it's a problem. It may call a database, and you have a performance hit. It can generate logs or other write operations that are now doubled.
This issue is affecting users and has been reported as a side effect in other projects: https://github.com/webonyx/graphql-php/issues/759 and https://github.com/nuwave/lighthouse/issues/1671.
Steps To Reproduce:
Outlined above.
Fix suggestion:
I suggest a hasAttribute method on Eloquent/Concerns/HasAttributes.php that mirrors getAttribute() but doesn't actually call anything:
    /**
     * Determine if the given attribute exists.
     *
     * @param  mixed  $key
     * @return bool
     */
    public function hasAttribute($key)
    {
        if (!$key) {
            return false;
        }

        // If the attribute exists in the attribute array or has a "get" mutator we will
        // get the attribute's value. Otherwise, we will proceed as if the developers
        // are asking for a relationship's value. This covers both types of values.
        if (array_key_exists($key, $this->attributes) ||
            array_key_exists($key, $this->casts) ||
            $this->hasGetMutator($key) ||
            $this->isClassCastable($key)) {
            return true;
        }

        // Here we will determine if the model base class itself contains this given key
        // since we don't want to treat any of those methods as relationships because
        // they are all intended as helper methods and none of these are relations.
        if (method_exists(self::class, $key)) {
            return false;
        }
        return $this->hasRelationValue();
    }

    /**
     * Get a relationship.
     *
     * @param  string  $key
     * @return mixed
     */
    public function hasRelationValue($key)
    {
        // If the key already exists in the relationships array, it just means the
        // relationship has already been loaded, so we'll just return it out of
        // here because there is no need to query within the relations twice.
        if ($this->relationLoaded($key)) {
            return true;
        }

        // If the "attribute" exists as a method on the model, we will just assume
        // it is a relationship and will load and return results from the query
        // and hydrate the relationship's value on the "relationships" array.
        if (method_exists($this, $key) ||
            (static::$relationResolvers[get_class($this)][$key] ?? null)) {
            return true; // TODO: see below
        }
    }

If you agree to it I can send a PR.
The only questionable point is the last if in hasRelationValue(). It assumes that the relation exists from the class data, but it may throw on getRelationshipFromMethod(). There seems to be no more reliable way to do it. The current implementation can throw on isset(), while my suggestion would only throw in offsetGet.
I consider this issue is relatively important, as it doubles operations on non-trivial model accessors for all users.

We likely won't be changing this behavior on a patch release. If your accessor does computationally expensive operations - consider caching or memoizing those results.

We likely won't be changing this behavior on a patch release. If your accessor does computationally expensive operations - consider caching or memoizing those results.

Yes, I can patch my code for this bug, thanks. That'snot the point.
This is not a good behaviour that is likely affecting a lot of people out there. There's absolutely no reason to actually call the accessor on offsetExists(). It should be a pure function and the way it's implemented has side-effects for no good reason.
The implementation is unsound and should at least be considered for the next release. Closing the issue will sweep it under the carpet.

Yes, I can patch my code for this bug, thanks. That'snot the point.
This is not a good behaviour that is likely affecting a lot of people out there. There's absolutely no reason to actually call the accessor on offsetExists(). It should be a pure function and the way it's implemented has side-effects for no good reason.
The implementation is unsound and should at least be considered for the next release. Closing the issue will sweep it under the carpet.

I think there is very little potential for harm in fixing this, it would only affect users who are somehow reliant on having isset() calls on their models produce some sort of side effect. Very unlikely.
The implementation looks simple enough, we could try a PR and see how the test suite copes and how well that is received. Let's just target the next major version to be totally safe.

I think there is very little potential for harm in fixing this, it would only affect users who are somehow reliant on having isset() calls on their models produce some sort of side effect. Very unlikely.
The implementation looks simple enough, we could try a PR and see how the test suite copes and how well that is received. Let's just target the next major version to be totally safe.

hey @spawnia. Is there any repo that I use that you are not a maintainer? I feel I owe you a beer. Or perhaps you owe me one :D
I'll post a PR tomorrow to get this started. Thanks for the support.

hey @spawnia. Is there any repo that I use that you are not a maintainer? I feel I owe you a beer. Or perhaps you owe me one :D
I'll post a PR tomorrow to get this started. Thanks for the support.

I tried my hand at implementing your proposed changes in master, looks like the test suite is still passing. Here is the git diff: model-has-attribute-diff.txt

I tried my hand at implementing your proposed changes in master, looks like the test suite is still passing. Here is the git diff: model-has-attribute-diff.txt

On a side note, I am not a maintainer of Laravel yet, although i have contributed some small stuff in the past.

On a side note, I am not a maintainer of Laravel yet, although i have contributed some small stuff in the past.


Connector Contracts

This PR will contain only the interfaces and entities for the Connectors API. We can discuss it and come to an agreement here.

go-cover-view


 It needs to be updated.

Good find. Thank you.

All merit to our docs feedback form, I'm just monitorizing it https://docs.google.com/forms/d/1oQ_Fy7K4pRmC83cap-AwRGO3bRbSDZc0DuL5kfJ3JJo


Applying policies on istio-system pods while working with knative

Bug description
I am working on applying authorization policies while working with knative, and for one of the red flag I am required to put a policy on a pod cluster-local-gateway running on ns istio-system to only accept traffic from some particular namespaces or service accounts [for my case - only the default ns]. I have applied this policy for the same purpose:
apiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
  name: ingress-policy
  namespace: istio-system
spec:
  selector:
    matchLabels:
      app: cluster-local-gateway
  action: ALLOW
  rules:
  - from:
    - source:
        namespaces: ["default" ]

But after applying this, traffic is blocked from everywhere on the cluster-gateway-pod, I can't even send traffic from default ns.
I understand that for this, I need to enable the mTLS, which I did on the istio-system ns.
I notice that ns istio-system is labeled as istio-injection=disabled. So I guess while being a bug, it is more of a question too - Is this even possible, applying such policy?
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[X] Policies and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
I should be able to block the traffic and allow it from only particular namespaces and serviceaccounts.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
1.6.2
How was Istio installed?
Using IstioOperator and istioctl
Environment where bug was observed (cloud vendor, OS, etc)
Kubernetes, CentOS

@incfly  A customer question :
while istio-system is labeled as istio-injection=disabled, Is this even possible, applying such policy?

I understand that for this, I need to enable the mTLS, which I did on the istio-system ns.

How did you do this? You will need to ensure that pods in default are sending traffic using mTLS to  cluster-local-gateway. Which may not be happening

@howardjohn there is one problem with a knative deployment running as a mesh pod in the default ns, I'll reach out to knative folks for this. Other than that, I wanted to know can I enable mTLS on the istio-system ns with it having this label istio-injection=disabled? Or do I need to change the label?

I mean simply put, in order to block certain namespaces to reach cluster-local-gateway I need to ensure that mTLS is enabled on said namespaces and this policy should work?
apiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
  name: ingress-policy
  namespace: istio-system
spec:
  selector:
    matchLabels:
      app: cluster-local-gateway
  action: ALLOW
  rules:
  - from:
    - source:
        namespaces: ["default" ]

or do i need to enable mTLS on istio-system ns as well?


(fix) Set ebean transaction level to be repeatable read

The current implementation of aspect versioning relies on the transactions to be with the isolation level of repeatable read in order to avoid lost updates (as discussed in https://datahubproject.io/docs/advanced/aspect-versioning/#transaction-isolation-1 and illustrated in https://github.com/linkedin/datahub/issues/3231).
Although the default isolation level is repeatable read for MySQL, ebean sets the default transaction isolation to be read committed (https://github.com/ebean-orm/ebean-datasource/blob/master/ebean-datasource-api/src/main/java/io/ebean/datasource/DataSourceConfig.java#L38); this PR ensures that the transactions use the repeatable read isolation level.
Another option would be to set it as the default/make it configurable (e.g. in https://github.com/linkedin/datahub/blob/master/metadata-service/factories/src/main/java/com/linkedin/gms/factory/common/LocalEbeanServerConfigFactory.java) - regardless, @dexter-mh-lee should run some performance regression testing before merging in.

Overall this looks good to me, but I haven't done any performance testing. My expectation is that this doesn't change MySQL performance.


Add MatadataChangeEvent processor to call seperate APIs

The MatadataChangeEvent processor checks for the changed items and calls the corresponding APIs with the Event avro record transferred JSON.
If there are several change event including schema change, the schema change will be called first, since it can possibly insert new dataset so the other changes can use this dataset id.

LGTM


Fixup scripts

The default script are using sed, awk, cat, ps, pgrep, dmenu and notify-send which leads to failure if they are not present in the environment. This commits pins them to a specific nixpkgs version.
Alternatively, we could start wrapping them.

Thanks! The scripts commands seem to work now.


Options

Make features like "duration" and "progress" optional. Their absence should not make the code fail.

Resolved in v2.


Quick fix action to create class, method etc.

Environment data

VS Code version: 1.27.2
Extension version (available under the Extensions sidebar): 2018.8.0
OS and version: Arch Linux
Python version (& distribution if applicable, e.g. Anaconda): 3.6.6
Type of virtual environment used: venv

Actual behavior
Pops up with "No code actions available".
Expected  behavior
Equivalent behaviour to IntelliJ IDEA: suggest creating a method bar in class Foo. Based on the property reference string this could then be extended to create other properties:

Foo.bar would suggest creating a field (or possibly @property method).
Foo.Bar would suggest creating an inner class.

Steps to reproduce:

Create a Python file:
class Foo:
    pass

Foo.bar()

Focus bar on line 5

Press Ctrl-.

Related to this, there should also be a quick fix for adding import <word> to the top of the file.
This is available in PyCharm, as documented here

I recently switched from pyCharm to VSCode, and this is a feature I was using a lot to fix error/warning in the code.
Is there any ETA for this function to work ?
Thanks

Another one I would love would clean up all unused imports in one step.

I'm on version September 2019 (version 1.39) and this is still a problem. VS Code successfully recognizes No space allowed around keyword argument assignmentpylint(bad-whitespace) but at the same the it displays "No quick fixes available".
Is this still expected or is something wrong in my setup?

Hey folks, glad everyone is interested in this feature. It's marked as needs spec, so it means it needs some design work before we're ready to work on it or mark it as "needs PR" so external contributors can work on it as well.
We're tracking auto imports here and unused imports cleaning here.

@luabud Thanks for the Update.

Any news on this?
The auto imports and imports cleaning are working fine but the "create class/function/property" quick actions for unresolved reference are still missing.
As @emmanueld said, this really disrupts the workflow when switching from pyCharm to vscode.

@altabe no updates on this issue so far AFAIK, but we definitely appreciate the feedback!

any updates please? plugin or anything else? This is easily one of the most used and useful features I used in PyCharm, would love to see it in vscode

We have been discussing about solving this in Pylance: https://github.com/microsoft/pylance-release/discussions/3600

Closing in favour of the Discussion over on Pylance.


Add video capture support

Adds video capture support to the file picker.  The file input's accept parameter will be used to determine which intent(s) to enable, with the following options:

accept="image/*" to enable photo capture
accept="video/*" to enable video capture
accept="*/*", accept="image/*, video/*" to enable both
If no accept parameter is specified, both will be enabled

I haven't added a new config variable for this (it's tied in with ASWP_CAMUPLOAD), which does mean that behaviour may change unexpectedly (especially for anyone who doesn't specify an accept parameter on their file inputs).  I think that it's a positive change though - especially for those who are specifying appropriate accept attributes - so I'm not sure whether you think it needs its own config variable.

thanks for the update!


[Incoming resources] Remove button doesn't work

Nothing happened by pressing Remove button.
Perform investigation and fix the issue

@svasylenko Where is the REMOVE button referenced here?

@KellyeDC Kellye, you have to press ... and Remove option is shown

Task is fixed.

After pressing Remove

Issue resolved


scriptCode support in gen_localizations and strip scriptCodes for date l10n.

I will add tests for this script.


Posts have a visible list of forward and backlinks

Somewhere on each post page there's a list of linked posts.
I think we can just group forward and backlinks together. I'm unconvinced there's much value in differentiating them.
But maybe to play it safe we should have some metadata on the links that says whether it's a front or backlink and then we could distinguish them with icons or something else subtle.

Forward links would exclude external links, right?

Yeah, only internal forward links


Wrong type of interface in mongodb  bootstrap_cluster.js template

There is wrong type of interface specified in ansible/roles/mongodb/templates/bootstrap_cluster.js.j2
both in:

https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/mongodb/templates/bootstrap_cluster.js.j2
https://github.com/openstack/kolla/blob/stable/newton/ansible/roles/mongodb/templates/bootstrap_cluster.js.j2

This wasn't picked earlier probably because of allinone deployments without customizing interfaces. Which basically means = api_interface==storage_interface==network_interface. Most docker containers including mongodb bind to api_interface. This template is used during task "Bootstraping the mongodb replication set" whenever api_interface!=storage_interface it fails because mongodb container doesn't listen on this address.
Fixes https://bugs.launchpad.net/kolla/+bug/1663128

Thank you for contributing to openstack/kolla!
openstack/kolla uses Gerrit for code review.
If you have never contributed to OpenStack before make sure you have read the
getting started documentation:
http://docs.openstack.org/infra/manual/developers.html#getting-started
Otherwise please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


#291 dotnetcore support feature

Added directory for dotnet core output file _Layout.cshtml to take it out of the root.
Created project build tasks for build.mvc.dev & build.mvc.prod to output the required files to the linking path set in tools/config/project.config APP_MVC_DEST which are notated in the /tools/tasks/project directory with a .mvc.
Consumer of the seed wishing to use dotnet core would simply setup the project as stated in the readme.md then set the path in the project.config to the root of their mvc application and the tasks will do the rest.
Since the production build of the seed includes the dependencies in the build process, a build.mvc.dev, other than the normal mvc angular 2 code, will require one addition to the startup.cs in the project and that is to map out the node_modules directory of the seed via a PhysicalFileProvider in the request pipeline, but this is only available with a "Development" environment variable. With a production build and environment variable the node_modules isnt supplied.
Example:
app.UseStaticFiles();
            //prod build includes deps
            if (env.IsDevelopment())
            {
            app.UseStaticFiles(new StaticFileOptions
                {
                    FileProvider = new PhysicalFileProvider(Path.Combine(env.ContentRootPath, "../angular-seed-advanced/node_modules/" )),
                    RequestPath = "/node_modules"
                });
            }

@Kaffiend Thanks for this. I think this would make more sense on a fork or different seed based off this seed that you could curate. It's quite a number of files that creates more to maintain on master which applies to a subset of users, therefore would require many seed users to delete that directory and tasks right from the start.
It's enough of a direction that would make for a great companion seed for that purpose which you could advocate and we could put a link to reference it in the README here.

This is a neat idea. Any thoughts on code generation from c#->ts? I could see automatic API generation a huge benefit for quick development (services, models, enums, etc).

@NathanWalker Im inclined to agree on a different seed, after getting deeper into it I realized how much needed to be done to accommodate the MVC pattern. But on another note, with a completely different seed based off this one I could include the dotnet core application in the repo and it be a more complete solution instead of an integration guide. Which i like.

Starter Seed can be found here. With a lot of work to come.

@Kaffiend good, that is what i want . thank you.


Vina environment installation error in Conda "Invalid specifier: '>=3.5.*'"

Hello
Been trying to get the 'vina' env set up (Anaconda 2.4.0/Windows10/Ubuntu 20.04 on WSL) per instructions but keep erroring out with the following message:
Version found 1.2.3 (from init.py)
error in vina setup command: 'python_requires' must be a string containing valid version specifiers; Invalid specifier: '>=3.5.*'
The executable is fine (can get response with '--version') but can't get the Python package going. In a different package installation I had edited the '>=3.5*' for 'python_requires' to '>=3.5' (multiple scripts) and the installation went fine.
I downloaded the vina-1.2.3-py311hac087fc_2.tar.bz2 archive (that 'pip install' does not process anyway) to try to edit out the offending '>=3.5*' but there is no 'setup.py' file, and no occurrence of '>=3.5*' in any of the included Python scripts. Apparently, this may not be a fix.
Is there something else I need, or to can be done by editing the archive contents? I wouldn't know how to fix problematic scripts beside mere text editing.
Thanks much!

I have the same problem with Google Colab, and Mint 20. Two weeks ago it did work, so maybe it is possible to fix it by downgrading.

This seems to be related to Python version. For me, it installed easily in Python 3.9 but I got this similar error while trying to install vina on Python 3.10 or 3.11. After I downgraded the python to 3.9, it got installed properly.

Fixed by #167


Slow Performance with Llama2 on a Dual-GPU System - Seeking Advice

Hello ollama Community,
I'm encountering extremely slow performance while running ollama on my PC, specifically with models like Llama2 13B. The issue isn't just the slow output speed (around 1 token/min), but I'm also concerned that my GPUs might not be utilized properly. Below are my PC specs:

CPU: Intel Core i7 12650H
Memory: 32GB
GPU0: Intel UHD Graphics
GPU1: NVIDIA GeForce RTX 4060 with 8GB VRAM

When running models such as the Llama2 13B, the performance drastically slows down. Interestingly, out of the 8GB VRAM, only about 6.1GB is being used, and the GPU utilization rate is close to 0%.
For comparison, I've also tried running larger models like Llama2 70B on a different PC equipped with a GeForce RTX 4060ti with 16GB VRAM. In this case, almost all of the VRAM is utilized, and the GPU utilization rate reaches about 10%.
I'm wondering if the issue with the first PC might be related to it having two GPUs, which could be causing incorrect GPU utilization, or if it's simply a matter of insufficient VRAM.
Could anyone please advise on whether this is an issue with GPU utilization due to the dual-GPU setup or if the VRAM is indeed insufficient? Any insights or suggestions would be greatly appreciated.
Thank you!

Can you share your server log so we can see how much of the model is being loaded in VRAM vs. running on the CPU?
Are you on Windows or Linux?

@dhiltgen thank you for your reply.
Here is my server.log
server.log

I use Windows 11 Pro.

I see a few different scenarios in your logs.  gemma seems to be fully loading offloaded 29/29 layers to GPU while the llama model you're loading is about 2/3's in GPU with offloaded 27/41 layers to GPU   I would expect the gemma token rate to be good, and the llama rate to be fairly slow.
The Intel GPU isn't supported, so only the 4060 is being used.

@dhiltgen
Thank you for answering.
I understood that it was simply not enough VRAM for the llama2 13B model.
Decreasing the value of the num_ctx parameter will improve the speed, so I will do that.

1

1

@dhiltgen
Thank you for answering.
I understood that it was simply not enough VRAM for the llama2 13B model.
Decreasing the value of the num_ctx parameter will improve the speed, so I will do that.


[Issue]SpawnStrategy

You cannot change where the landmines spawn no matter what I input, even with lethal config, it just won't accept any other string

The names are case sensitive so it has to be one of: MainAndFireExit, MainEntranceOnly or FireExitsOnly.
When the mod is loaded, it is trying to parse these names and if it fails, it goes back to the default.
Also make sure to reload the game after changing the settings in LethalConfig.
I just tried a new profile with only this mod in the latest version, Imperium for debugging and the FireExitsOnly strategy:
(Note how the main entrance on the top left does not have any hazards close by)

If the issue persists, can you try to create a new profile only with this mod and see if it works?
This would rule out any other mod interfering with the config loading.

Does this mod have any known conflicts?

There are currently none. Feel free to report any you might encounter though!
Did you manage to change the config values?


how  can Gobblin run on storm or spark?

how  can Gobblin run on storm or spark?     Is there some plugable access to do that?

@superwood Gobblin currently is not able to run on Spark or Storm. It's possible to make Gobblin run on Spark by wrapping Gobblin Source and Extractor into something like a GobblinInputFormat and GobblinInputSplit and additionally other Gobblin operators into Spark operators.


[BUG]: Fatal error if null value passed to .seek() on iOS

Version
6.0.0
What platforms are you having the problem on?
iOS
Architecture
Old architecture
What happened?
If null is passed as a value to .seek(), it causes a fatal error due to a dynamic casting failure.
This was not done intentionally - if you try and pass null as a value to .seek() it is caught by type checks. The bug arose when a startVideoTimestamp value was returned as null instead of undefined from our GraphQL API and we couldn't figure out why the app was crashing every time we tried to open a video.
Stack trace below:
Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Triggered by Thread:  0

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	       0x105e793b0 __pthread_kill + 8
1   libsystem_pthread.dylib       	       0x106a2f124 pthread_kill + 256
2   libsystem_c.dylib             	       0x1801655c0 abort + 104
3   libswiftCore.dylib            	       0x1932a10cc swift::fatalErrorv(unsigned int, char const*, char*) + 132
4   libswiftCore.dylib            	       0x1932a10e8 swift::fatalError(unsigned int, char const*, ...) + 28
5   libswiftCore.dylib            	       0x193297f04 swift::swift_dynamicCastFailure(void const*, char const*, void const*, char const*, char const*) + 76
6   libswiftCore.dylib            	       0x193297f7c swift::swift_dynamicCastFailure(swift::TargetMetadata<swift::InProcess> const*, swift::TargetMetadata<swift::InProcess> const*, char const*) + 120
7   libswiftCore.dylib            	       0x19329c378 swift_dynamicCast + 280
8   superfeelapp                  	       0x102f23f88 RCTVideo.setSeek(_:) + 748 (RCTVideo.swift:745)
9   superfeelapp                  	       0x102f43da8 closure #1 in RCTVideoManager.seek(info:reactTag:) + 128 (RCTVideoManager.swift:41)

Reproduction
No response
Reproduction

Pass null to videoRef.seek();
App crashes

Easy to fix: https://github.com/TheWidlarzGroup/react-native-video/pull/3802
Thank you for the report !


Update nixOS and add new PostgreSQL versions

Add PostgreSQL version 15 and 16 to run tests on. Remove 11 since it's not
supported by nixOS 23.11 anymore.

No worries. I kept it at 11+ since I assumed it meant the minimum version this should work on, which hasn't changed, just isn't automatically tested anymore. I updated it to 12 now.


buyData method not returning data

Hello, nice implementation of the NodeJS wrapper for VTPass API, but it seems the auth token for a development environment is hardcoded. Is that normal, or the auth header should also follow the username and password configuration as it is for a production environment?
Willing to open a new PR for that little fix. Cheers @Chibuokem
if(environment == 'production'){             const token =  new Buffer.from(username + ":" + password).toString("base64");             this.auth =Basic ${token};         }else{             this.auth = "Basic ${token}"; //This is the change         }

Thank you @jobafash , it was done that way because the values needed for the development environment is fixed already, so it will be nice that someone should come and be able to use the wrapper on the development environment without having to start researching for the development username and password again, as that can be a blocker

https://github.com/Chibuokem/vtpassnodejs/blob/main/services/data/data.js

Good day @Chibuokem , and thank you for your swift response! Was looking at implementing the buyData method, but it seems the serviceID in lines 35-37 of this file(https://github.com/Chibuokem/vtpassnodejs/blob/main/services/data/data.js) isn't passed to the axios POST. Would you mind looking at that?

Hello, i have checked again and i can notice that the service id is passed there, on line 43,  const buyData = await this.axios.post(
/pay,
{ request_id, serviceID, billersCode, variation_code, phone },
{headers: {'Authorization' : this.auth} }
);


feat request: Built-in UDC contract

If this goes through: https://github.com/OpenZeppelin/cairo-contracts/pull/467,
it would amazing to have a UDC pre-deployed as part of Devnet for the purpose of deploying the first factory contract.
Then, all the rest of the deploys in the test suite can be from the factory contract. \

https://github.com/OpenZeppelin/cairo-contracts/pull/467 UDC PR is about to be merged as it is: https://twitter.com/martriay/status/1578496057813528576
@FabijanC or @Nathan-SL could we have this in devnet as part of the 0.10.1 support release later this month?

Once these contracts are officially released (which will be any moment now), we can start working on support for it


Made config printable in debug log

This is to log the config in debug mode. Currently, it is empty because the Config fails to Marshal to JSON.
Example:
2019/12/01 21:01:00 config=

Coverage increased (+0.02%) to 67.4% when pulling 71bc8ecb1162a14e2bf48e91e8c1676131096a3d on h7kanna:debug_config into 245075c199b6b32b9ba3e8bfe1f0e9f76b797253 on uber:master.

Needs further testing.


Ensure we remove consumed_timestep for update notification decisions

Closes #456

Coverage: 87.526%. Remained the same when pulling 09c67c0427ae7adafe77fb9d348d8ba2b454a04c on bug/456 into eaf927ea6c798009d24ac659666af11101fedb2f on main.


Support for providing configs to an annotation using a file without explicitly specifying each config

Currently, to provide configs to an annotation (e.g., the ServiceConfig annotation in HTTP), one needs to call the relevant functions in the config API for each of the attributes in the annotation one wants to configure.
It would be great instead of having to call the functions explicitly, the user just provides a config file with configurations for the attributes which need to be configured and automatically map and populate the attributes using these configurations.

This module is deprecated and is not maintained in Ballerina now. Hence closing the issue.


Add new function drop dataset

Hi 👋,
What's the purpose of using your function over the naive query for dataset deletion? Can you add some description of what this commit does and how it's different from the DROP SCHEMA IF EXISTS datasetname?

Agree @shivam221098. Thanks for your comment.
With @Jihene-cherif we did not see that drop schema adds a cascade parameter and this function as intended to do that.
I close this PR.
If you are interested in contributing @shivam221098, I will be happy to take you onboard if the README is not good enough.
Slack can also help: https://join.slack.com/t/bigfunctions/shared_invite/zt-1gbv491mu-cs03EJbQ1fsHdQMcFN7E1Q

Sure. Thanks. :+1:


v2ray无法统计用户流量

你正在使用哪个版本的 V2Ray？（如果服务器和客户端使用了不同版本，请注明）
V2Ray 4.22.1
你的使用场景是什么？比如使用 Chrome 通过 Socks/VMess 代理观看 YouTube 视频。
需要统计共享用户的流量消耗情况
你看到的不正常的现象是什么？（请描述具体现象，比如访问超时，TLS 证书错误等）
v2ray 访问日志已正确显示用户邮箱，但统计脚本仍然只能显示Inbound的流量，无法显示用户的流量
你期待看到的正确表现是怎样的？
User下能显示用户流量
请附上你的配置（提交 Issue 前请隐藏服务器端IP地址）。

服务器端配置:
    // 在这里附上客户端配置
{
	"log": {
		"access": "/var/log/v2ray/access.log",
		"error": "/var/log/v2ray/error.log",
		"loglevel": "warning"
	},
	"stats":{},
	"api":{
		"tag":"api",
		"services":[ "StatsService",
			    "LoggerService" ]
	},
	"policy":{
		"leveles":{
			"1":{
				"bufferSize":1024,
				"statsUserUplink": true,
				"statsUserDownlink": true
			},
			"2":{
				"statsUserUplink": true,
				"statsUserDownlink": true
			}
		},
		"system":{
			"statsInboundUplink": true,
			"statsInboundDownlink": true
		}
	},
	"inbounds": [
		{
			"port": 80,
			"tag":"tcp_http",
			"protocol": "vmess",
			"settings": {
				"clients": [
					{
						"id": "不告诉你",
						"level": 1,
						"email": "kaban",
						"alterId": 23
					},
					{
						"id":"不告诉你",
						"level":2,
						"email": "none",
						"alterId":10
					}
				]
			},
			"streamSettings": {
				"network": "tcp",
				"tcpSettings": {
					"header": {
						"type": "http",
						"response": {
							"version": "1.1",
							"status": "200",
							"reason": "OK",
							"headers": {
								"Content-encoding": [
									"gzip"
								],
								"Content-Type": [
									"text/html; charset=utf-8"
								],
								"Cache-Control": [
									"no-cache"
								],
								"Vary": [
									"Accept-Encoding"
								],
								"X-Frame-Options": [
									"deny"
								],
								"X-XSS-Protection": [
									"1; mode=block"
								],
								"X-content-type-options": [
									"nosniff"
								]
							}
						}
					}
				}
			},
			"sniffing": {
				"enabled": true,
				"destOverride": [
					"http",
					"tls"
				]
			}
		},
		{
			"listen": "<IP_ADDRESS>",
			"port": 10085,
			"protocol": "dokodemo-door",
			"settings": {
				"address": "<IP_ADDRESS>"
			},
			"tag": "api"
		}
	],
	"outbounds": [
		{
			"protocol": "freedom",
			"settings": {
				"domainStrategy": "UseIP"
			},
			"tag": "direct"
		},
		{
			"protocol": "blackhole",
			"settings": {},
			"tag": "blocked"
        },
		{
			"protocol": "mtproto",
			"settings": {},
			"tag": "tg-out"
		},
		{
			"protocol":"http",
			"settings":{
				"servers":[
					{
						"address":"<IP_ADDRESS>",
						"port":8888
					}
				]
			},
			"tag":"gohome"
		}
	],
	"dns": {
		"servers": [
			"<IP_ADDRESS>",
			"<IP_ADDRESS>",
			"<IP_ADDRESS>",
			"<IP_ADDRESS>",
			"localhost"
		]
	},
	"routing": {
		"domainStrategy": "IPOnDemand",
		"rules": [
			{
				"inboundTag": ["api"],
				"outboundTag": "api",
				"type": "field"
			},
			{
				"type": "field",
				"ip": [
					"<IP_ADDRESS>/8",
					"<IP_ADDRESS>/8",
					"<IP_ADDRESS>/10",
					"<IP_ADDRESS>/16",
					"<IP_ADDRESS>/12",
					"<IP_ADDRESS>/24",
					"<IP_ADDRESS>/24",
					"<IP_ADDRESS>/16",
					"<IP_ADDRESS>/15",
					"<IP_ADDRESS>/24",
					"<IP_ADDRESS>/24",
					"::1/128",
					"fc00::/7",
					"fe80::/10"
				],
				"outboundTag": "blocked"
			},
			{
				"type": "field",
				"inboundTag": ["tg-in"],
				"outboundTag": "tg-out"
			},
                {
                    "type": "field",
                    "domain": [
                        "full:api.bilibili.com",
			"full:www.bilibili.com",
			"163.net",
			"126.net"
		    ],
                    "outboundTag": "gohome"
                },
		{
			"type":"field",
			"ip":[
				"<IP_ADDRESS>/32",
				"<IP_ADDRESS>/32"
			],
			"outboundTag":"gohome"
		}
		]
	},
	"transport": {
		"kcpSettings": {
            "uplinkCapacity": 100,
            "downlinkCapacity": 100,
            "congestion": true
        }
	}
}

请附上出错时软件输出的错误日志。在 Linux 中，日志通常在 /var/log/v2ray/error.log 文件中。

服务器端错误日志:
 2020/02/12 23:39:07 [Warning] [2357524755] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:39:07 [Warning] [2963210239] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:39:07 [Warning] [2963210239] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:39:08 [Warning] [2963210239] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] v2ray.com/core/app/router: resolve ip for https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] v2ray.com/core/app/router: resolve ip for https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] [2017658041] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] [2017658041] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] v2ray.com/core/app/router: resolve ip for https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] v2ray.com/core/app/router: resolve ip for https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] [1991170087] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] [1991170087] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] [2017658041] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] [1991170087] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] [2017658041] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] [1991170087] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] [2017658041] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] [1991170087] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] v2ray.com/core/app/router: resolve ip for https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] v2ray.com/core/app/router: resolve ip for https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] [1915616913] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] [1915616913] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:21 [Warning] [1915616913] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:22 [Warning] [1915616913] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:22 [Warning] [1915616913] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:23 [Warning] v2ray.com/core/app/router: resolve ip for https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:23 [Warning] v2ray.com/core/app/router: resolve ip for https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:23 [Warning] [4127258495] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:23 [Warning] v2ray.com/core/app/router: resolve ip for https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:23 [Warning] v2ray.com/core/app/router: resolve ip for https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:23 [Warning] [3019546417] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:23 [Warning] [3019546417] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:23 [Warning] [4127258495] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:23 [Warning] [3019546417] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:23 [Warning] [4127258495] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:24 [Warning] [3019546417] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:24 [Warning] [4127258495] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:24 [Warning] [3019546417] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:24 [Warning] [4127258495] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:24 [Warning] v2ray.com/core/app/router: resolve ip for https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:24 [Warning] v2ray.com/core/app/router: resolve ip for https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:24 [Warning] [3886856460] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:24 [Warning] [3886856460] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:24 [Warning] [3886856460] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:24 [Warning] [3886856460] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/12 23:43:25 [Warning] [3886856460] v2ray.com/core/proxy/freedom: failed to get IP address for domain https > v2ray.com/core/app/dns: invalid domain name
2020/02/13 11:55:44 [Warning] v2ray.com/core: V2Ray 4.22.1 started

请附上访问日志。在 Linux 中，日志通常在 /var/log/v2ray/access.log 文件中。

    2020/02/12 20:25:06 <IP_ADDRESS>:33737 accepted tcp:res.wx.qq.com:443 [direct] email:kaban
2020/02/12 20:25:10 <IP_ADDRESS>:33738 accepted tcp:mp.weixin.qq.com:443 [direct] email:kaban
2020/02/12 20:25:10 <IP_ADDRESS>:33740 accepted tcp:mp.weixin.qq.com:443 [direct] email:kaban
2020/02/12 20:25:10 <IP_ADDRESS>:33739 accepted tcp:mp.weixin.qq.com:443 [direct] email:kaban
2020/02/12 20:25:11 <IP_ADDRESS>:33741 accepted tcp:mp.weixin.qq.com:443 [direct] email:kaban
2020/02/12 20:25:11 <IP_ADDRESS>:33742 accepted tcp:mmbiz.qpic.cn:443 [direct] email:kaban
2020/02/12 20:25:12 <IP_ADDRESS>:33743 accepted tcp:mp.weixin.qq.com:443 [direct] email:kaban
2020/02/12 20:25:12 <IP_ADDRESS>:33744 accepted udp:<IP_ADDRESS>:53 [direct] email:kaban
2020/02/12 20:25:12 <IP_ADDRESS>:33747 accepted udp:<IP_ADDRESS>:53 [direct] email:kaban

其它相关的配置文件（如 Nginx）和相关日志。
`#!/bin/bash

_APISERVER=<IP_ADDRESS>:10085
_V2CTL=/usr/bin/v2ray/v2ctl
apidata () {
local ARGS=
if [[ $1 == "reset" ]]; then
ARGS="reset: true"
fi
$_V2CTL api --server=$_APISERVER StatsService.QueryStats "${ARGS}"
| awk '{
if (match($1, /name:/)) {
f=1; gsub(/^"|link"$/, "", $2);
split($2, p,  ">>>");
printf "%s:%s->%s\t", p[1],p[2],p[4];
}
else if (match($1, /value:/) && f){ f = 0; printf "%.0f\n", $2; }
else if (match($0, /^>$/) && f) { f = 0; print 0; }
}'
}
print_sum() {
local DATA="$1"
local PREFIX="$2"
local SORTED=$(echo "$DATA" | grep "^${PREFIX}" | sort -r)
local SUM=$(echo "$SORTED" | awk '
/->up/{us+=$2}
/->down/{ds+=$2}
END{
printf "SUM->up:\t%.0f\nSUM->down:\t%.0f\nSUM->TOTAL:\t%.0f\n", us, ds, us+ds;
}')
echo -e "${SORTED}\n${SUM}"
| numfmt --field=2 --suffix=B --to=iec
| column -t
}
DATA=$(apidata $1)
echo "------------Inbound----------"
print_sum "$DATA" "inbound"
echo "-----------------------------"
echo
echo "-------------User------------"
print_sum "$DATA" "user"
echo "-----------------------------"`
10) 如果 V2Ray 服务运行不正常，请附上 journal 日志。
通常的命令为 journalctl -u v2ray。
请预览一下你填的内容再提交。

https://guide.v2fly.org/advanced/traffic.html#流量信息的处理

https://guide.v2fly.org/advanced/traffic.html#流量信息的处理

按照设置后，会报错，开启不了。
v2ray.com/core/infra/control: failed to dial <IP_ADDRESS>:10085 > context deadline exceeded
v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled


backstretch not working with bootstrap

I believe there is something conflicting between the two js codes that prohibits the backstretch to work at all any ideas, workarounds?

Hi, a little late... but i have the same problem.


allow aws healthchecks

The healthchecks from the aws elb set the host header to the local ip, since that's not in ALLOWED_HOSTS we get an error that goes to sentry, this happens so frequently that it's exhausted the free tier allowances there over just a few days.

Not ready for merge, currently only works for ec2 hosting, ecs metadata is a little different: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-metadata-endpoint-v3.html


Mention sass alternative to node-sass

There are valid reasons to prefer sass over node-sass.
It would be informative to the users to know that they can use this alternative.
Thanks to the package resolution node-sass@npm:sass a Create React App doesn't have to be ejected to support sass library. It will work transparently without any additional steps from a user.

Actually, you can simply run npm install sass --save and it works fine with latest create-react-app.

Hi everyone! Today I came across problems with node-sass. Apparently it is not supported anymore and therefore I received an error saying that my OS is not supported (but it is according to documentation). The fix was to use sass instead of node-nass.
So +1 for switching the documentation to sass as well.


interrupts, framebuffer, and some code refactoring has been done

This is a lot of changes, and I am well aware, if there is any problem or questions, feel free to contact me on discord.

Thats very good.


random vs uniform sampling

What is the reasoning behind randomly sampling contour points? My initial thought would be uniform sampling.
Great work btw!

The main reason is that random sampling allows to define the number of used points after the sparse viewpoint model is generated (as long as the number is smaller than the number of sampled points). For uniform sampling, the model would have to be generated every time the number of points is changed. However, in general, uniform sampling is also be possible.

Ok thanks!


Update documentation related to appcallback versioning (#657)

Thank you for helping make the Dapr documentation better!
If you are a new contributor, please see the this contribution guidance which helps keep the Dapr documentation readable, consistent and useful for Dapr users.
If you are contributing a new authored "How To" article, this template was created to assist you.
In addition, please fill out the following to help reviewers understand this pull request:
Description
Please explain the changes you've made
Issue reference
_Please reference the issue this PR will close: #657

Team decided to no add versioning on app callbacks.


[Metrics] - Enable micrometer and annotate every API call

Enabling micrometer and add annotations to gather multiple metrics for diff APIs
Run a loop of experiments and at the end of it, we should be able to do a curl from prometheus which can pull these metrics

Fixed as part of #829


Concurrent connection QPS is too low, which should not be the performance of go.

[meaningless picture deleted]

Can you please describe the issue, what you did, what happed, what was expected, provide all the details on how to reliably reproduce it (including operating system, versions and configuration)?
Thanks in advance.

I didn't do anything. I want to test the concurrent QPS capability of dnscrypt-proxy with queryperf. Has anyone ever done any tests?

In order to do performance testing on a proxy, you need to set up a dedicated server simulating the  protocol. Nothing like this exists for encrypted DNS as far as I know.
The local proxy, the transport layer, the remote proxy, its infrastructure, and upstream servers have their own limitations and restrictions. A test involving round trips through the whole chain can only estimate the performance of the whole chain. It cannot provide any indications on individual components. This requires simulation in a controlled environment.
As a practical example, my DNSCrypt proxy servers will immediately rate limit and eventually block your IP if a spike of traffic coming from the same source is detected, Google will ignore your queries after 100 queries per second, and Cloudflare enforces a low limit of in-flight queries per client. This doesn't let you measure anything about the proxy running on your end.


Selection of columns to display not working correctly

System information:

OSX Mojave
DBeaver version 21.2.4
Java version 8
Additional extensions None

Connection specification:

Database name and version MariaDB 10.5
Driver name
Do you use tunnels or proxies (SSH, SOCKS, etc)? SSH

Describe the problem you're observing:
When I open a table and click on the
"Resultset/Order filter settings" to select the columns to view, some of the fields, usually close to the last columns, refuse to be shown. When I try again, the selection is still unticked, even though I definitely ticked it. I can repeat this many times but it refuses to stick and the column does not show.
Also, the new way of ticking is incredibly frustrating. Why was it changed? The old way worker very well. The new way needs at least 3 clicks before the tick registers - sometimes a lot more. I wish I never upgarded DBeaver and I am beginnign to seriously look at alternatives.
Include any warning/errors/backtraces from the logs

@wynandcoetzer Could you please provide some screenshots of the issue for a more clear understanding? Also a DDL of the table would be great to reproduce it.

The problem I have is purely with the UI of DBeaver. It is a problem for every table on every database. My issue is that when I want to select a set of columns to display, it has become extremely difficult. It worked very well until this last release. For the last release the tick boxes in selecting the columns to display have been changed. I experience the following problems:

I have to click from 3 to more than 10 times before I manage to get a tick mark.
The last tick is always ignored - I have to add an extra tick mark anywhere to actually display the columns I want
Previous selections display as if still selected but it ignores any change in selection

Let me reiterate - until the last vserion of DBeaver this worked so well and then for no rhyme ort reason it was changed. Why change a perfectly working piece of code? And then to utterly destroy usability in the process? It is horrible!
To confirm my utter frustration with a feature that I loved in DBeaver to a totally unusable feature, I am now evaluating TablePlus and I am willing to pay for the license becauase I cannot live with the current abortion.
Please, please change it back to the way it ws and through this piece of junk code away.

@wynandcoetzer Thank you for the report. We will work on that.
Reproducible only on MacOS


Missing information on configuring Issuer URL for multi-tenant scenarios

This page does not contain adequate information for configuring an App Service app for multi-tenanted use (i.e. users being able to sign in from multiple Azure AD tenants)
The following section needs to be amended:
"Enable Azure Active Directory in your App Service app", Point no 5, Issuer URL
This should contain instructions to clear the "Issuer URL" field if you plan on using the app/function in a multi-tenanted scenario. If the Issuer URL field contains a value the function will return 401 errors whenever a user from a different tenant tries to access it.

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

ID: 6f1c454d-73bc-5a73-5d3f-1b1ca7625044
Version Independent ID: 552b3f09-6650-e7f7-01f2-a702005b83e9
Content: Configure Azure AD authentication - Azure App Service
Content Source: articles/app-service/configure-authentication-provider-aad.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@chrolivier Thanks for the feedback! We are currently investigating and will update you shortly.

Thanks again for the feedback! If I have understood right, you are configuring an App Service app for multi-tenanted use. Just to confirm when setting Expose an API for multi-tenant app have you pasted in the URL which is based on one of the tenant verified domains?
Referring this section: Creating an app registration in Azure AD for your App Service app:
Step 9: “Select Expose an API > Set. For single-tenant app, paste in the URL of your App Service app and select Save and for multi-tenant app, paste in the URL which is based on one of tenant verified domains and then select Save.”
Let us know if you have further question on this.

@SnehaAgrawal-MSFT Thanks for the follow up.
Yes, I did do that. I still had to delete the contents of the Issuer URL field otherwise users from other Azure AD instances would not be able to call an API.

@chrolivier Thanks for reply! You may want to investigate this doc Update your code to handle multiple issuer values  As its mentioned "A multi-tenant application can’t validate tokens just by matching the issuer value in the metadata with the issuer value in the token. A multi-tenant application needs logic to decide which issuer values are valid and which are not based on the tenant ID portion of the issuer value.
For example, if a multi-tenant application only allows sign-in from specific tenants who have signed up for their service, then it must check either the issuer value or the tid claim value in the token to make sure that tenant is in their list of subscribers. If a multi-tenant application only deals with individuals and doesn’t make any access decisions based on tenants, then it can ignore the issuer value altogether. "
Let me know.

@chrolivier Since we didn't here from you we will now proceed to close this thread. If there are further questions regarding this matter, Please Let us know.

@SnehaAgrawal-MSFT :  while configuring authentication for app service, you require to provide issuer url

This url is in the form : "//v2.0" --> for eg. "https://login.microsoft.com/de7b297a-c7aa-4b34-8a1c-2fdda8e11fe3/v2.0". Where "de7b297a-c7aa-4b34-8a1c-2fdda8e11fe3" is tenantid.
This configuration works fine for a single tenant application where only users from tenant "de7b297a-c7aa-4b34-8a1c-2fdda8e11fe3" is going to login to the application.
However, this configuration will not work if you are hosting multi-tenant application.
For multi-tenant application, "issuer url" shown in the above screenshot requires to be left blank. This instruction is not clear in the documentation.

Thank you for this feedback @chrolivier and @jogikalpesh. We are currently in the process of working on substantial documentation and Azure Portal UX improvements, using this issue as well as feedback we've heard from other customers (both internal and external) for guidance. As part of that work, we will also provide more clear documentation and guidance for enabling multi-tenant applications for Azure AD (I think it may even end up being a simple checkbox in the portal). Stay tuned.
/cc @mattchenderson

@jogikalpesh you can also use the common endpoint for multi tenant applications. That way it will use the V2 authentication endpoint and you also get Graph Tokens.
See my blog post for more info


BE: Remove players from grid on disconnect

I've hopefully fixed the issues. Don't know if there's any logic bugs still left in, but it compiles.

LGTM


(WIP) Support regex in matchers

Describe your idea
Support regular expression in Detox matchers
Specifically in by.text(), by.label().
This can be useful since text and labels may include dynamic content (e.g. date).
Also, I suggest to change the current API, from:
https://github.com/wix/Detox/blob/246317d3ee5b7587bb966c78204b5def5b72dfaf/detox/index.d.ts#L804
To:
text(text: string | RegExp): NativeMatcher;

Usage example
This code will find an element with the text "The year is 2023", if exists:
const someElement = element(by.text(/The year is: \d{4}/));

While this code won't:
const someElement = element(by.text('The year is: \d{4}'));

Why not dynamically recognize instanceof Regexp versus string?

Why not dynamically recognize instanceof RegExp versus string?

Sounds great, let's do it this way.

@asafkorem the only pitfall I see is that we might need to standardize RegExp mechanisms between iOS/Android/JS...

@noomorph that is spot on. We've somehow manged to overcome that in the context of the URL's blacklist - we could revisit and hopefully replicate.

Nevertheless I'd like this kind of any API to come with a warning of some sort, that would explains that ideally, whichever text we trying to match should be deterministic to the point it can be predetermined down to the character.
Of course, this is not always the case in unmocked tests, but generally this should be the preferred situation.

This is super useful when working with iOS elements because you can't seem to expose testIDs (or equivalent) so I'm using accessibilityLabel to perform the function of both an identifier and additional state.

Is someone working on this issue?

Not really, @asafkorem 's been busy last months trying to release Detox 21 with XCUITest.
@asafkorem would you mind to take this issue to the final mile? Looks like there is demand for it, 10*👍 already

Side note (because I couldn't find it easily beforehand): The work that's been put into see is available in this old branch

This feature was released in version 20.11.0, thanks to @andrius-girdzius!


Destroy multi backend on display destroy

That allows to remove the wlr_backend_destroy call in main.c, because everything is cleaned up by the display destroy.

Thanks!


Remove sorting since the lods are generated from closest to furthest.

Multiple bugs show the wrong lod level. The lods seem to be decimated too quickly
Neither the distance or the index comparator make sense to sort lods.
They're generated from most detail to the least detail already. The only operation I can see is maybe a reverse list and definitely not a sort in any other order.
If this is an optimization it should have no visible lod effect. So the removal is valid because it has an unexpected visual effect.

Discussed with Detox on the discord server.
Fixes: https://github.com/godotengine/godot/issues/67891

@reduz @JFonS does anyone remember the original reason?

Discussed that this was the wrong implementation.


Is it possible to draw DOM content to canvas?

See this introduction how to convert DOM content to canvas: http://robert.ocallahan.org/2011/11/drawing-dom-content-to-canvas.html
Seems rather tricky and limited at first glance.

Probably the best way to render HTML DOM to pixels is via a headless browser like Phantom or Electron.


added climate monitor exporter

Signed-off-by: Brant Taylor<EMAIL_ADDRESS>@brian-brazil
Added a Prometheus exporter to the docs that I wrote for some climate monitors that I have here at my house.

Thanks!
Some suggestions to improve your exporter:
If this is multi-threaded then it is racy, as you generally shouldn't be resetting metrics on every scrape as a concurrent scrape will see partial data.
The deviceName label on all metrics is really a target label, which it is the responsibility of service discovery/relabelling on the Prometheus side to handle. If you wish to expose this do so as a single info metric. In general the same label pair should never appear on all metrics from a target.
These metrics have missing and/or non-base units. Celcius is the base unit for temperature, the unit of humidity is unclear (it should be a ratio), and I've no idea what the units are for airflow, light, or sound are here. Cubic metres per second, candelas, and bels? Make sure the unit is part of the metric name so it's clear to anyone using the metrics.

Thank you, @brian-brazil ! Great suggestions, I will work on improving it.


New-BcAuthContext error authenticating in Partner Center submission API

Describe the issue
I'm getting an error (refresh_token property does not exist) when I run the New-BcAuthContext command with the scope "https://api.partner.microsoft.com/.default" following the instructions in Automatic AppSource Submission of Business Central apps to publish our apps via PowerShell in the AppSource with the User Impersonation way.
Scripts used to create container and cause the issue
New-BcAuthContext `
   -includeDeviceLogin `
   -scopes "https://api.partner.microsoft.com/.default" `
   -tenantID "my-azure-aad-tenant-id"

Full output of scripts
Attempting authentication to https://api.partner.microsoft.com/.default using device login...
To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code DEVCODE to authenticate.
Waiting for authentication...
Authenticated from xxx.xxx.xxx..xxx as user My User Name<EMAIL_ADDRESS>New-BcAuthContext Telemetry Correlation Id: e66877e6-b032-417c-9a2a-dabbafe116f3
No se encuentra la propiedad 'refresh_token' en este objeto. Compruebe que existe.
En C:\Users\jlloret\Documents\WindowsPowerShell\Modules\BcContainerHelper\4.0.5\BcSaaS\New-BcAuthContext.ps1: 307 Carácter: 17
+                 $authContext += @{
+                 ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : PropertyNotFoundStrict
...

Additional context
This is the line with the error:
                $authContext += @{
                    "AccessToken"  = $accessToken
                    "UtcExpiresOn" = [Datetime]::UtcNow.AddSeconds($TokenRequest.expires_in)
                    "RefreshToken" = $TokenRequest.refresh_token
                    "Credential"   = $null
                    "ClientSecret" = $null
                    "appid"        = ""
                    "name"         = $jwtToken.name
                    "upn"          = $jwtToken.unique_name
                }

And this is the value of the $TokenRequest variable while debugging the script:
$TokenRequest :
    token_type: "Bearer"
    scope: "https://api.partner.microsoft.com/user_impersonation https://api.partner.microsoft.com/.default"
    expires_in: 3891
    ext_expires_in: 3891
    access_token: "eyJ....vA"
    foci:1

There is a copy/paste error in the blog post:-(
Have fixed that.
the New-BcAuthContext with refreshtoken should be:
$authcontext = New-BcAuthContext `
    -refreshToken $refreshtoken `
    -Scopes "https://api.partner.microsoft.com/user_impersonation offline_access" `
    -tenantID "<your AAD tenant>"

Thanks Freddy!
Now it's working properly.

Hi Freddy,
Adding the refresh token  doesn't work for me
Script:
$authcontext = New-BcAuthContext
-refreshToken $refreshtoken     -includeDeviceLogin
-Scopes "https://api.partner.microsoft.com/.default"      -tenantID "My AAD Tenant"
Output:
`New-BcAuthContext Telemetry Correlation Id: 3ddfb436-8478-4ab3-a60e-2d3a482da9d3
The property 'refresh_token' cannot be found on this object. Verify that the property exists.
At C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\4.0.6\BcSaaS\New-BcAuthContext.ps1:307 char:17

            $authContext += @{

            ~~~~~~~~~~~~~~~~~~`

Debugging:

Please advice

great, thanks


pulumi: 3.90.1 -> 3.91.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/pulumi/pulumi/releases.
meta.description for pulumi is: Pulumi is a cloud development platform that makes creating cloud programs easy and productive
meta.homepage for pulumi is: https://pulumi.io/
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.91.1 with grep in /nix/store/0zbjy95wnz7hs5rw6k7dzwq5scm5wai0-pulumi-3.91.1
found 3.91.1 in filename of file in /nix/store/0zbjy95wnz7hs5rw6k7dzwq5scm5wai0-pulumi-3.91.1

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

12 total rebuild path(s)

12 package rebuild(s)

First fifty rebuilds by attrpath
pulumi
pulumiPackages.pulumi-language-go
pulumiPackages.pulumi-language-nodejs
pulumiPackages.pulumi-language-python
python310Packages.pulumi
python310Packages.pulumi-aws
python311Packages.pulumi
python311Packages.pulumi-aws
python311Packages.pulumi-aws-native
python311Packages.pulumi-azure-native
python311Packages.pulumi-command
python311Packages.pulumi-random

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/6569352f6f94cc5f9849f1781cf4de5f76d69d16#pulumi

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0zbjy95wnz7hs5rw6k7dzwq5scm5wai0-pulumi-3.91.1
ls -la /nix/store/0zbjy95wnz7hs5rw6k7dzwq5scm5wai0-pulumi-3.91.1/bin

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

11 packages failed to build:

pulumiPackages.pulumi-language-go
pulumiPackages.pulumi-language-nodejs
pulumiPackages.pulumi-language-python
python310Packages.pulumi
python310Packages.pulumi-aws
python311Packages.pulumi
python311Packages.pulumi-aws
python311Packages.pulumi-aws-native
python311Packages.pulumi-azure-native
python311Packages.pulumi-command
python311Packages.pulumi-random

1 package built:

pulumi

Maintainer pings
cc @Trundle @veehaitch for testing.

Superseded by #267316


Consider including openssl_probe

While rust-native-tls will work very consistently on MacOS and Windows, on Linux it can be a little finicky thanks to different distros using different locations for storing root certificates. This means that a Rust binary compiled on one distribution might not be able to correctly make requests through reqwest until SSL_CERT_DIR is set, so it can find standard root CAs without adding them manually.
Since reqwest is taking a batteries included approach it might be a good idea to include something like openssl_probe to make it easier for users to make SSL requests on Linux, i.e. without having to set SSL_CERT_DIR themselves.

It looks like native-tls includes openssl-probe by default now.


Specified that bootstrap_servers are Kafka instances

Some people (like me) might think that this needs to point to Zookeeper at first.

LGTM


Change cache location on Mac/Windows

Currently, the base image cache is located at:

Mac: $HOME/Library/Application Support/google-cloud-tools-java/jib/
Win: %LOCALAPPDATA/google-cloud-tools-java/jib/

It may be a good idea to change these to:

Mac: $HOME/Library/Caches/Google/Jib/
Win: %LOCALAPPDATA/Google/Jib/

We may need to come up with a migration strategy so we don't break users who rely heavily on the cache (e.g. offline users).

The Win cache should be in %LOCALAPPDATA%/Google/Jib/Cache just to be clear that it can be removed without affecting other possible configuration files.

We may need to come up with a migration strategy so we don't break users who rely heavily on the cache (e.g. offline users).

I'm leaning toward documentation rather than adding code to do automatic migration for a number of reasons.

Gonna reopen this until the documentation is updated

Alos, does it make sense to update CHANGELOG to describe the changes to the base image cache directory on some platforms by #2218?

Oh right, was gonna do that but forgot.


All Login Attempts Suddenly Fail With Error: Signature verification failed

This just started happening out of nowhere really. It was working fine until today. I haven't made any changes or installed any updates since last week. All login attempts redirect to a page with this error:
There was a problem with your log in Error: There was an issue decoding the token, please review the Auth0 Plugin Error Log.

The logs in my Auth0 Dashboard show that the login was successful. There are no log messages from Auth0 plugin in my PHP logs or WP debug log. Please let me know what information you need that would help identify the problem. Thanks!
Edit:
Got this out of my wp database:
[
  {
    "section":"redirect_login\/decode",
    "code":"N\/A",
    "message":"Signature verification failed, disabling \"Settings \\ Basic \\ Client Secret Base64 Encoded\" may resolve this issue.",
    "date":1497967999
  },

cc: @glena @cocojoe

@lots0logs

So to confirm this error is not displayed in the Auth0 Plugin Log screen?
Also to confirm you upgraded to the latest version last week but this is the first time this error has appeared?
Have you changed any of your Auth0 client settings?

Thx

@cocojoe

I can't access the dashboard because I have my wp-login.php page redirecting to a custom login page that has Auth0 Widget on it :man_facepalming:
I dont remember exactly when it was I last updated. I can see that the current version of the plugin that is installed is 3.2.21. That's from my automated weekly backup that ran about 10 hours ago. I assume that the issue didn't immediately present itself because my login session was valid (I logged in fine day before yesterday so my session must have expired since then).
No. Haven't touched anything on Auth0 Dashboard nor on the Auth0 wp plugin settings.

Thanks!

@lots0logs can you try adding ?wp to the admin login url and it should hopefully fallback to wp login.

@cocojoe Nah that doesnt help because like I said, I have my site configured to redirect the default login page to a custom one where I am using the Auth0 Lock. I see the most recent release of the plugin included changes that appear to be related to error I'm getting now when trying to log into my site. Do you know what the problem is?

There was an issue that in the Auth0 dashboard, new clients do not have a base64 encoded secret, so the default options was changed to set this flag to false.  The error was there to help anyone who may have an issue that their flag is enabled when it should be disabled.
The only real change is:
https://github.com/auth0/wp-auth0/pull/313/files#diff-894052ccee58b2c7d7f46aca8335a672L61

My site has been using the plugin almost since its 1.0 version. Does that mean my secret is base64 encoded? That could explain the problem I'm having, right?

Well this setting should be stored in the database, so the change in defaults shouldn't matter.  Can you check the wp-auth0 client settings in the Auth0 Dashboard, in particular under Client Secret it tells you if it's encoded or not. Thx

I know you have the redirect but also try
https://auth0.com/docs/cms/wordpress/troubleshoot#my-configuration-is-wrong-and-i-can-t-authenticate-using-auth0-is-there-another-way-to-access-the-plugin-

I had actually tried that before opening this issue. I'm going to try downgrading the plugin and see if the issue remains afterwards.

@cocojoe I downgraded the plugin manually to the previous version and I can log in again. Is there thing I can provide that would help to identify and fix the bug?

That would be great thanks, first step, what is the version of the plugin you are using now?
In the Plugin basic settings, is the base 64 encoded option enabled or disbled?

@lots0logs it would be helpful if you could tell me the version of the plugin you are currently on that works fine. Thx

@cocojoe

Plugin Version: 3.2.20
In Auth0 Dashboard I see: The Client Secret is base64 encoded.
In WP Auth0 Plugin Settings this option is enabled: Client Secret Base64 Encoded

Let me know if that helps track down the issue. Cheers!

@lots0logs I believe I've got to the bottom of this and patched this for next release https://github.com/auth0/wp-auth0/pull/324
It would be great if you could have a look at the settings stored in the database, in wp_options / wp_auth0_configuration (something like that).
Don't paste it here, but I'm wondering if it contains the key client_secret_b64_encoded and if it does the value.
Thanks for your help.

@cocojoe I think I may have found the problem while digging in the database. I have a multisite with two sites. That means I actually have three wp-auth0 configs total (though I dont think the network-level one ever gets used..its leftover from when I first installed the plugin a couple years ago). Anyway, the serialized data of my main site's wp-auth0 config was somehow corrupt. Not sure how it happened but I use the exact same config for both sites so I just copied the other site's config over to the site where the data was corrupt (I saved the corrupted data) Do you have an email I can send the data to privately?
I am about to perform a back up and try updating the plugin again unless you think I should hold off on that?

@lots0logs sure martin dot   walsh   at    auth0.com
don't upgrade just yet, lets check that config first.

Done :smiley:

Thanks I had a look at your configs, so I think you will be fine to upgrade to the upcoming release of 3.2.22 which we'll be releasing today.

@lots0logs Did you have a chance to update?

No, not yet. TBH, I didn't realize the update was released already :sweat_smile: I will try and get to it today and let you know how it goes!

No rush, never update on a Friday 😄

I can confirm the update went smoothly and the issue no longer occurs :confetti_ball:  Thanks!!


This look so promise, waiting for it :D

Hello, not sure what you're excited about. Can u provide more info?

Oh, sorry forgot node it. It's about @tailwindcssinjs/tailwind-data (WIP)

I have added some examples of possible use cases to the @tailwindcssinjs/tailwind-data package.
Still more work to do mostly documentation of the API's.
Do you plan on using @tailwindcssinjs/tailwind-data for a project?

I have added some examples of possible use cases to the @tailwindcssinjs/tailwind-data package.
Still more work to do mostly documentation of the API's.
Do you plan on using @tailwindcssinjs/tailwind-data for a project?

I want to test it but I don't know how to config, must wait for that... I am using Nextjs. I hope can shorten class name of Tw. I don't want use CSS in JS.

https://codesandbox.io/s/tailwindcssinjscss-example-kwuke 😉


Delete unnecessary spaces

When copying from the web page, there is an unnecessary space after the code.

@changeworld : Thanks for your contribution! The author, @mikejo5000, has been notified to review your proposed change.

@changeworld @Mikejo5000 Mike Jones (DEVUE) FTE - We're in the process of pulling these commits to the private repo, so we can verify the content on staging. We'll post a new PR # shortly and then close this PR.

@changeworld @Mikejo5000 - The commits in this PR were moved to the private repo (PR 3890) for validation and staging. We'll close this PR now.


Does it support Google IMA SDK?

May I know whether it supports Google IMA SDK and how to implement into MediaElements?

No currently mediaelements does not support IMA SDK.
The ads plugin listed in only support html5 ads and flash ads it self...  I developed one in the past and use slightly modified version of it currently on my own website(s)


[Vue warn]: Error in mounted hook: "TypeError: Cannot read property 'editor' of undefined"

[Vue warn]: Error in mounted hook: "TypeError: Cannot read property 'editor' of undefined"
按照文档的描述引入 报错

are you sure window.monaco is available in your page? please provide a minimal repo too

我不太理解第一个步骤 You need to include monaco-editor first.  这个monaco-editor 是引入到哪里？

add to your html


React step 4

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

Closing - duplicate PR of https://github.com/carbon-design-system/carbon-tutorial/pull/1299


Use version-less Key Vault secret identifier to reference the certificates

Hello,
Following section of documentation:
https://learn.microsoft.com/en-us/azure/application-gateway/key-vault-certs#key-vault-azure-role-based-access-control-permission-model
There is a code example to create version independent SSL certificate in AppGW:
$secretId = $secret.Id.Replace($secret.Version, "") # Remove the secret version so AppGW will use the latest version in future syncs
The code leads to following two Azure Advisor High Impact recommendations:
"Use version-less Key Vault secret identifier to reference the certificates", and
"Resolve Certificate Update issue for your Application Gateway"
i.e. the code is wrong (or the Advisor)
This is output from the code:
https://my-kv.vault.azure.net:443/secrets/mycert/
This is correct solution resolving issue in the Azure Advisor:
https://my-kv.vault.azure.net:443/secrets/mycert
I.e., the / at the end should be removed.
The wrong code line:
$secretId = $secret.Id.Replace($secret.Version, "") # Remove the secret version so AppGW will use the latest version in future syncs
can be corrected for example like this:
$secretId = $secret.Id.Replace("/"+$secret.Version, "") # Remove the secret version so AppGW will use the latest version in future syncs
Thank you for updating the documentation.

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

ID: 4c416d5e-5bfd-c641-e9bb-324dcb921acc
Version Independent ID: 8739a044-d471-c432-3ed1-503539408ae8
Content: TLS termination with Azure Key Vault certificates
Content Source: articles/application-gateway/key-vault-certs.md
Service: application-gateway
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

@frenky29a , thank you for your feedback. We have assigned this to the content owner/author for review.
@greg-lindsay , for your review.

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/d365community/forum/79b1327d-d925-ec11-b6e6-000d3a4f06a4.

Closing this request and moving to internal work item 91174
#please-close


Add missing HTML tags

Fixes Microsoft/TypeScript#17828

Hi @saschanaz. Thanks for following up this issue and for finally resolving the problem with ElementTagNameMap. Nevertheless, please do use the more specific interfaces for the newly added elements, such as HTMLMainElement and the others.

please do use the more specific interfaces for the newly added elements, such as HTMLMainElement and the others.

There is no HTMLMainElement in the standard. The interface in current lib.d.ts should be removed instead.

From: Daniel M<EMAIL_ADDRESS>Sent: Monday, February 4, 2019 2:03:20 AM
To: Microsoft/TSJS-lib-generator
Cc: Kagami Sascha Rosylight; Mention
Subject: Re: [Microsoft/TSJS-lib-generator] Add missing HTML tags (#609)
Hi @saschanazhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsaschanaz&data=02|01||d29ee8c35ecd4a0ef93c08d689f98017|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636848102013559901&sdata=74Hu4pvrO%2FqISgDO%2BRLa6cORgcImzSzrQOL%2Fk2%2FR%2FuI%3D&reserved=0. Thanks for following up this issue and for finally resolving the problem with ElementTagNameMap. Nevertheless, please do use the more specific interfaces for the newly added elements, such as HTMLMainElement and the others.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FTSJS-lib-generator%2Fpull%2F609%23issuecomment-460068875&data=02|01||d29ee8c35ecd4a0ef93c08d689f98017|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636848102013569912&sdata=YMFwUu7ixUKqQDIVrXvdUpU%2BTx9mceFGYQWoKNqkfQU%3D&reserved=0, or mute the threadhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADPUTnPeTICoxCllEQSPa5vkP-3L300qks5vJxZYgaJpZM4YWedO&data=02|01||d29ee8c35ecd4a0ef93c08d689f98017|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636848102013579917&sdata=Xc0PqB0FLs9MNQcaM9SlARATULsQZyb0cUzEZDdxsF4%3D&reserved=0.

Great then! Sorry for the inconvenience caused.


{Core} Disable random_config_dir when record test

Description

As mentioned in https://github.com/Azure/azure-cli/pull/26273#issuecomment-1551174298, the login info can't be retrieved when enable random_config_dir,
This PR disable it if AZURE_TEST_RUN_LIVE is defined.
Testing Guide

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Core


PDB Sort

Script that sorts chains in a PDB file. Considers ATOM and HETATM coordinate lines. Accepts piping.

Would it be possible for it to sort the entire PDB file? Maybe we could have flags for sorting only some parts, but it would be useful for it to sort models, chains, residues, and atoms within those residues, place HETATM at the end, etc. Special attention should be taken care for alternate locations, and insertions, etc.

The current version already sorts the whole PDB. If the PDB has several chains, say B-A-D-C-Z the output will be A-B-C-D-Z without TER lines.
I can make it have those three options, but is it coherent with the 1 script 1 functionality idea of pdb-tools? Or should there be 3 scripts instead (sortchains.py, sortres.py and sortatoms.py) ?
Personally, and after you have implemented in me the philosophy of pdb-tools, I prefer 3 scripts instead of 1 with 3 options, because in that way users will only have to look to the list of scripts to search for what they want without the need to look for implicit options that each script may or may not have (remember the reres.py case).
Insertions is not a problem (to my understanding). Because new key in dictionary is created by .setdefault() which means that if the keys exists it won't alter the state of the dictionary. So if a ATOM or HETATM from a previous chain appears it will be placed together with the same chain identifier. It is up to the user to previously change chain names in case there are chains with the same identifier in the PDB file.
Let me know your final decision.

I can make it have those three options, but is it coherent with the 1 script 1 functionality idea of pdb-tools?

I think so. The idea of the script is to sort, and there is a canonical way of doing so. The options just offer a finer degree of control over what is sorted. Honestly, I doubt we will use these options at all, but since the code is probably there, why not offer the choice. It's like what I did in pdb_wc. It counts a bunch of things, but you can make it return only a part of the counts.

Insertions is not a problem (to my understanding)

I meant residue insertions, which is a field in the PDB file itself (character 27)
Thanks!