No pricing available on the pricing page?

Perhaps a note to the effect that "pricing will be available --->here when the service GAs" would be worth adding.

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

ID: 45a084d7-acb6-9893-b6d1-6fef01e0bd07
Version Independent ID: c9c8b4b2-d080-f8a8-85e2-24f9d66df8c3
Content: Pricing and limits - Custom Vision Service
Content Source: articles/cognitive-services/Custom-Vision-Service/limits-and-quotas.md
Service: cognitive-services
GitHub Login: @anrothMSFT
Microsoft Alias: anroth

Good catch. This page is never going to contain pricing, which sits on the azure.com page.
It looks like the title was changed in Oct. I have submitted a PR to our internal msft repo to have this fixed.
Thanks!!

@anrothMSFT Thanks for submitting the change. @tescales We will now proceed to close this thread. If there are further questions regarding this matter, please tag @RohitMungi-MSFT in your reply. We will gladly continue the discussion and we will reopen the issue.


Curators want to publish a private collection

Story
Curators want to publish a private collection on the portal to make it available for other scientists to explore.
This should be available in the collections page. It is only possible to set private to public. The reverse operation (public-> private)  is unavailable.
Note from August 19 Trust session:
Shawn recommends that publishers be reminded of the terms of service related to derivative works when publishing a private collection. However, this is not required for curator scenarios.

UX Design
Figma

#875 potentially has relevant information

Happy Monday, @brianraymor @hthomas-czi 🤩 Hope you had a great weekend!
Just wondering if we will have a copy for the text in the modal soon 😊
Another user flow question, do we want to allow publishers/curators to make a collection public while a dataset is still being processed? (e.g., conversion is in WIP) What about if one format of a dataset conversion failed?
Thank you so much!

Happy Monday, @brianraymor @hthomas-czi 🤩 Hope you had a great weekend!
Just wondering if we will have a copy for the text in the modal soon 😊
Another user flow question, do we want to allow publishers/curators to make a collection public while a dataset is still being processed? (e.g., conversion is in WIP) What about if one format of a dataset conversion failed?
Thank you so much!

do we want to allow publishers/curators to make a collection public while a dataset is still being processed?
Good question. Publishing must be disabled if a private collection is in an error or in progress state.

do we want to allow publishers/curators to make a collection public while a dataset is still being processed?
Good question. Publishing must be disabled if a private collection is in an error or in progress state.

Perfect thank you! I think one FE ticket should be enough. Will create it now!
@brianraymor are you working with @hthomas-czi on the modal text content? Thanks!

Perfect thank you! I think one FE ticket should be enough. Will create it now!
@brianraymor are you working with @hthomas-czi on the modal text content? Thanks!


deepEqual doesn't handle negative zeroes

Consider the following assertion:
t.equal(0, -0);

It passes because JavaScript defines strict equality between signed zeroes (0 === -0). However, the following scenario unexpectedly fails:
t.same([0], [-0]);

not ok 1 should be equivalent
  ---
    operator: deepEqual
    expected: |-
      [ -0 ]
    actual: |-
      [ 0 ]

Discovered this while switching from tap to tape — the latter had a failing case where tap passed because of this inconsistency. cc @ljharb

tap and tape aren’t precisely equivalent, so some differences are expected.
t.same, in tape, is an alias for deepEqual, not equal.
Separately, tape v4 uses deep-equal v1; tape@5 uses deep-equal v2 which more closely matches node’s assert. If you install tape@next, what happens?

t.same, in tape, is an alias for deepEqual, not equal.

Yes. However, it is expected that deepEqual/same compares leaf values with the same semantics as equal. Node's assert behaves correctly in this regard:
const assert = require('assert');
assert.deepEqual([0], [-0]); // passes

Upgrading to tape@next doesn't resolve the issue.
It looks like the problem stems from using strict: true for deepEqual across the code (e.g. here). Is there any reason for using that option? It was added in this ancient commit, but there's no explanation for it.
In deep-equal, the only difference when passing strict: true is using Object.is instead of ===, which means 0 and -0 are different, and so are NaN and Number.NaN.
I think this is a bug — deepEqual should semantically be consistent with equal for basic values.

deepEqual should match assert; tape should as well.
“same” is just an alias, a convenience; it has no direct expectations.
I very recently updated deep-equal and tape, and that involved changes to -0 handling, so I’m quite convinced there’s not a bug here, but if you’d like to submit a PR with failing test cases, I’d be happy to look into it.

@ljharb I think there's a misunderstanding there — I know same is an alias for deepEqual, and this bug concerns both.

deepEqual should match assert; tape should as well.

That's exactly what I'm saying — it should, but currently tape does not match assert because of {strict: true}, which seems to be a mistake.
An additional argument (beyond incompatibility with Node's assert) is that it doesn't make sense for the following two lines to have different results:
t.equal(0, -0); // ok
t.deepEqual(0, -0); // fail

They often have different results; try 3 and '3', for example.
There’s a bug if assert.equal doesn’t match t.equal, and assert.deepEqual doesn’t match t.deepEqual. The strict option should match assert.deepStrictEqual.

Ah, yeah, you're right, although the fact equal and deepEqual use different equality semantics (Object.is vs ===) feels very counter-intuitive, inconsistent, and also doesn't match the docs. In summary:

Tape's equal and strictEqual use === , but deepEqual uses Object.is, not ===.
Node's strictEqual and deepStrictEqual both use Object.is.

So, if tape and deep-equal are both consistent with node's assert - then the place to file an issue requesting a change is in node itself. If they're not consistent, I will absolutely fix them to be so.

@ljharb sorry if I'm not expressing myself clearly enough — see my comment above, which shows how tape itself is inconsistent, while Node assert and deep-equal are fine. The way to fix this would be to change === to Object.is for strict equality checks in tape.

 This is something I can definitely fix in v5, which is still in prerelease.

@ljharb exactly! Thank you very much!

@ljharb thanks a lot for addressing this! Thinking about this further, if equal semantics are changing to be non-strict, is there any reason not to fully match assert behavior in deepEqual too? I mean, now the behavior is:

tape
assert
type

equal
equal
loose

looseDeepEqual
deepEqual
loose

strictEqual
strictEqual
strict

deepEqual
strictDeepEqual
strict

As a part of semver-major change which you're doing anyway, would it makes sense to do:

tape
assert
type

equal
equal
loose

deepEqual / looseDeepEqual
deepEqual
loose

strictEqual
strictEqual
strict

strictDeepEqual
strictDeepEqual
strict

I think that it's generally an improvement for tape to default to strictDeepEqual, and make "loose" opt-in. If anything, it'd be reasonable to swap .equal and .strictEqual, but that adds a lot of churn for arguable value.

Added 24240e2 as well, to ensure all the inverse functions were consistent.

@ljharb it still seems weird to me that equal defaults to "loose" and deepEqual to "strict" — is there a reason not to either 1) go all the way with consistency with assert (equal and deepEqual are loose), or 2) go all the way with defaulting to strict comparisons (equal and deepEqual use is)?

I don't know the history; I think this is just the way it's been for awhile - but basically this is a question of tradeoffs: is the consistency worth the breakage and churn? I'm not convinced it is.

@ljharb if we're worried about breakage and churn, why should we introduce the big change of equals === to ==? If we're doing it now before v5, we could do the deepEquals change as well.
On the other hand, if we want to keep things mostly as they were before but improve consistency, why not revert the equals loosening and instead switch it to is, while keeping deepEquals as it was? This will be both consistent and almost unnoticeable to users.

That won't break anything - currently passing tests will continue to pass.
That's also a reasonable alternative, true - making equal and deepEqual both strict, and looseEqual and looseDeepEqual non-strict.

@ljharb 🎉 excellent! I like this way much more too. Thanks a lot for your patience bearing through all my comments, and generally really great work maintaining this awesome project.


Issue #1458 support scrolling to last message

Pull request checklist

[X] All tests pass. Demo project builds and runs.
[X] I have resolved any merge conflicts.
[X] I have squashed my commits into 1 commit.
[X] I have followed the coding style, and reviewed the contributing guidelines. Confirmation: ____

This fixes issue #1458 .
What's in this pull request?

An implementation of issue #1458 that enables the user of JSQMessagesViewController to respond to a delegate whether the view should scroll to the end or not on startup and when a new message arrives.

:tada: Thanks @lbanders ! :+1:
Looks like the commit history is still really dirty:
https://github.com/jessesquires/JSQMessagesViewController/pull/1489/commits
We'll need to patch this up: rebase on release_8.0 and squash to a single commit.

@jessesquires I actually had managed to have it all into one commit, but it ended up being merged with what I had already pushed to GitHub. Anyway, I believe I have got that in order now, by moving that commit to the top. Alternatively I believe its creating a new branch.

hey @lbanders -- sorry this got closed automatically because release_8.0 was deleted after merging into develop
would you still like to support this PR? 😄
if so, would you mind opening a new PR on develop after resolving conflicts?


XEP-0280 Message Carbons

This is a very simple extension, but I needed it, it's on the standards so I thought it'd be useful to have out of the box.
Thank you for continuing development on this excellent XMPP binding!
Sincerely, Ignacio.//

Hi,
Sorry for the delay, but I was away during the last 2 weeks.
I will make a review on the pull request, thanks for your contribution!
Regards,
pgstath

Contribution merged, and release notes were updated. Thanks again for your contribution!

:) Sweet. Thanks for keeping a great library live!


Cant Use the xSQLServerSetup module from the azure automation Powershell Gallery

I found this very weird that I cant see the xSQLserversetup module in the Azure automation account, this module is required so that I can install the SQL Server instance onto the node, but since I cant see this configuration inside the xSQLserver module, how can I use this module, I tried importing this but it didnt got imported as well, Is anyone having this kind of issue??
Please How can I use the module for the installation of the module, or tell me how can I run the script so that I generate the .mof file locally and then install this onto my machine.

Hi @dead8171, this is a known bug that is in the process of being resolved in PR #851. See the following issues for some more details:

#310
#705
#713
#716

The known workarounds are listed here.

The workaround for this is use the xSQLserver <IP_ADDRESS> module, I have imported this but couldnt able to see the xSqlserversetup module in there please let me know about this, also How can I run the script locally, I mean I have to pass the credentials in the DSC to make it to work but I dont know how to do that.

I want to make sure we're using the same terminology here. xSQLServerSetup is a DSC resource that is a part of the xSQLServer module. Can you see the xSQLServerSetup resource when you execute Get-DscResource -Module xSQLServer -Name xSQLServerSetup?

@randomnote1 Where should I execute this command since I am using Powershell of automation account. I know thats the part of the xSQLServer module but I cant seem to find that module in the Automation Account Powershell gallery.

You should be able to navigate to the module version you wish to deploy in the PowerShell Gallery and click the "Deploy to Azure Automation" button. From my limited testing, it will walk you through the steps to download the module into your automation account.

Hi
@johlju and @randomnote1
I am still having issue with xSQLSetup resource being loaded in AA account, I have followed the work around of deleting xSQLServerAlwaysOnAvailabilityGroupDatabaseMembership, and zipping up the file. it loads successfully into AA, however I still cannot see the xSQLSetup resource, tried version <IP_ADDRESS>, <IP_ADDRESS> and <IP_ADDRESS>. Is there a fix?

@randomnote1 I have tried that, and it did deploy to the Automation Account, but I still cant see the xSQLServerSetup module inside the Automation Account, I have screenshot that shows this. But How to upload them here.

@dead8171 Hi, deleted xSQLServerAlwaysOnAvailabilityGroupDatabaseMembership, zipped the file and  version <IP_ADDRESS>. Although I cannot see xSQLServerSetup, I recompiled my SQL DSC config in AA and it completed successfully. Applied the config to one of my VMs and it worked. Try it out.

Version 9+ of SqlServerDsc resolve this issue.  While you will not see SqlSetup listed in the extracted activities for the module (yet), configurations that use the resource will now compile successfully.  I believe we can mark the issue as resolved?

@mgreenegit I'm using version <IP_ADDRESS> of xSQLServer and I'm still facing the same issue with the complication job failing with the same errors.

@mattpound808 It should be version <IP_ADDRESS> which has not yet been release, and will be release as SqlServerDsc. It is currently the one in the Dev branch, so you could try manually upload the dev branch until we can release the new version (soon I hope).

@mattpound808 and please read the change log since all the resources has been renamed.

Actually, even if I download <IP_ADDRESS> from GitHub, package and upload it to the gallery, I still can't use SQLSetup. The import stops at the SQLServiceAccount resource no matter what. If I remove this resource from the module, then it stops at SQLServerRole. I believe the issue is therefore in the SQLSetup resource.
If I remove the SQLSetup from the module, then everything loads fine all the way down to SQLWindowsFirewall. So this proves that the culprit is SQLServerSetup. The issue is related to the fact that the SQLSetup resource contains culture sub-folders, which Azure Automation doesn't like. @mgreenegit any idea what may be causing this? We don't seem to have any logs on our end.

@NikCharlebois In my tests even if you don't see the resource in the list, you are able to compile using the resource. Are you not able to compile?

Not able. If I import from the gallery, then the compilation job complains about the Resource not found. If I remove the 2 culture folders from the SQLSetup resource, then zip and manually upload to the Modules assets in Azure Automation then it works

I took the latest dev version.
Make sure everything was in the root of the SqlServerDsc folder
Zipped it.
Uploaded the zipped archive to the Modules section of Azure Automation.
Clicked on the imported resource module.

Compiled a simple SqlSetup configuration.

It looks okay to me. How come it doesn't work for you? 🤔

Btw. I usually don't see all the resources but for some reason I see all now. Tried uploaded it twice and it showed all resources as it should. But even if I don't see all resources in the modules view, compiling works.
Can just hope that a fix is rolling out for the bug that existed that made resources not show.

Did the exact same thing. Grabbed the content from the Dev branch on GitHub, and only got 27 resources loaded:

The size (kb wise) seems to differ from yours as well

@NikCharlebois the size difference is my bad, I took the folder from a working branch where the CHANGELOG.md and README.md had more information in it.
Tested more this morning. I took all files in the downloaded zip file from the dev version on GutHub. I did not remove any files. Did you do the same?
When uploading this to an Azure Automation which is in the location West Europe I get all 30 resources (three times in a row). When uploading this to an Azure Automation which is in the location West US 2 I get only 27 resource. But even so I am able to compile SqlSetup, even if it is not shown in the list (see second image).
Azure Automation in East US 2:

Able to compile a configuration with the SqlSetup resource:

I was just thinking about the different regions issue. Glad you tested. Several people managed to replicate my exact issue when using East US. I will try with West EU later today to see.

I can reproduce it even if I create an Azure Automation account in the West EU region. The resource doesn't show in the list (it stops at SQLServiceAcount), and my configuration don't compile. Not sure if this is caused by the blob storage it is uploaded to in the background or what. As mentioned, I managed to get it replicated by several colleagues as well. It seems like SQLServer (xSQLServer) is the only module affected at the moment.

Any chances we could get a prereleased version (https://blogs.msdn.microsoft.com/powershell/2017/12/05/prerelease-versioning-added-to-powershellget-and-powershell-gallery/) in the gallery to make sure we are both trying out the same package and compare results. This is currently a major show stopper for many clients that used to be able to automate their full deployments via ARM and DSC.

Folks on this thread. SQLServerDSC (v10) just got published to the gallery today. Please give it a go. The resource still doesn't show in the list of imported resources, but it seems like the configurations now compile just fine. Make sure you do use the new resources name (e.g. SQLSetup instead of xSQLServerSetup)

Labeled this as external and closing this as this is nothing we can resolve from our end.


Changing #include for MPI parcelport

Merging this as the errors are unrelated but the #include needs fixing.


Fix for mod_manager.c,opening files in children processes and shared memory creation [MODCLUSTER-726][MODCLUSTER-725]

mod_manager.c had an issue where it would try to open some .lock files in the manager_child_init function, it wouldn't find them and try to create them but it didn't have the permissions since it was a child process.
I just created the .lock files in the manager_init function so all the child processes could inherit the file descriptors.
EDIT**
Also fixed some problems that mod_manager.c has with shared memories.
It would create a shared memory with apr_shm_create, which if httpd didn't shut down properly was never clean up, as a result when httpd would be started again it would try to apr_shm_create the same file and get file exists error.
Now it tries to create an anonymous shared memory, if the system doesn't support anonymous shared memories it removes the old named shared memory if it exists and creates a new one.

Can one of the admins verify this patch? If it is not dangerous to our systems, juts tell me to "run_tests".  ( without the underscore and quotes :smiley: )

@kimonides  Please merge the 4 commits into a single one.

@kimonides Please merge the 4 commits into a single one.

Just finished merging the 4 commits into a single one.

run tests

@jfclere The w2k12 box is dead until I can go to office and do something about it.  I have 2k19 up and running, although it is not fully geared for building openssl (missing perl). It should build httpd and mod_cluster just fine though. Lemme try...


Undefined symbols for architecture x86_64 when using ios_unit_test

I'm running XCode 13.3, Bazel 5.1.1, and rules_apple 1.0.0
I'm running into an issue where I'm building a swift_library that has an spm_pkg as a dep. I'm then specifying that swift library as a dep for an ios_unit_test. When I try to build that target I get this error. Seems like it's not finding the Foundation module?
https://github.com/bazelbuild/rules_apple/issues/1656

I am curious to know how your example differs from the ios_sim example. Can you post  your BUILD file?

Seems to be pretty similar
load("@build_bazel_rules_apple//apple:ios.bzl", "ios_application", "ios_unit_test")
load("@build_bazel_rules_swift//swift:swift.bzl", "swift_library")

swift_library(
    name = "build_source",
    srcs = glob([
        "Project/**/*.swift",
    ]),
    deps = [
        "@swift_pkgs//SQLite.swift:SQLite",
        "@swift_pkgs//swift-composable-architecture:ComposableArchitecture",
        "@swift_pkgs//Bow:Bow",
        "@swift_pkgs//Bow:BowEffects",
        "@swift_pkgs//Cache:Cache",
        "//protos:grpc_swift",
        "//protos:grpc_stubs_swift"
    ],
    module_name = "ProjectApp"
)

swift_library(
    name = "build_tests",
    srcs = glob([
        "TestProject/**/*.swift",
    ]),
    deps = [
        ":build_source",
        "@swift_pkgs//Fakery:Fakery",
    ],
    module_name = "ProjectTests",
)

ios_unit_test(
    name = "test_unit",
    data = glob([
        "TestProject/**/*.swift",
    ]),
    deps = [
        ":build_tests",
    ],
    minimum_os_version = "15.0",
    visibility = ["//visibility:public"],
)

ios_application(
    name = "build_app",
    bundle_name = "project",
    bundle_id = "co.name.ProjectApp",
    families = [
        "iphone",
        "ipad",
    ],
    minimum_os_version = "15.0",
    infoplists = [":Project/Info.plist"],
    visibility = ["//visibility:public"],
    deps = [":build_source"],
)


Preview pane - horizontal splitter

Hi,
Would it be possible to make the preview pane configurable between a horizontal and vertical split? You might want to do this if you have for example an excel table with many columns or wide screenshots in your folder.

@FreHu
this suggestion seems more indicated for the Windows Feedback Hub, since doing this in PowerToys would require to implement preview handles for all the supported files, something that is out of scope for PowerToys.


Address failing Gosec G601

What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind bug
What does does this PR do / why we need it:
The G601 check in gosec started failing today with the following:
/go/bin/gosec
gosec -severity medium -confidence medium -exclude G304,G204 -quiet  ./...
Results:

[�[30;43m/go/src/github.com/openshift/odo/pkg/odo/util/completion/completionhandlers.go:123�[0m] - G601 (CWE-): Implicit memory aliasing in for loop. (Confidence: MEDIUM, Severity: MEDIUM)
  > &servicePlan

[�[30;43m/go/src/github.com/openshift/odo/pkg/storage/storage.go:218�[0m] - G601 (CWE-): Implicit memory aliasing in for loop. (Confidence: MEDIUM, Severity: MEDIUM)
  > &pvc

[�[30;43m/go/src/github.com/openshift/odo/pkg/storage/storage.go:175�[0m] - G601 (CWE-): Implicit memory aliasing in for loop. (Confidence: MEDIUM, Severity: MEDIUM)
  > &pvc

[�[30;43m/go/src/github.com/openshift/odo/pkg/storage/storage.go:173�[0m] - G601 (CWE-): Implicit memory aliasing in for loop. (Confidence: MEDIUM, Severity: MEDIUM)
  > &pvc

�[1;36mSummary:�[0m
   Files: 210
   Lines: 34936
   Nosec: 9
  Issues: �[1;31m4�[0m

make[1]: *** [sec] Error 1
make[1]: Leaving directory `/go/src/github.com/openshift/odo'
make: *** [openshiftci-presubmit-unittests] Error 2
---

I noticed that the following was not failing:
https://github.com/openshift/odo/blob/master/pkg/storage/storage.go#L130
So it seems that if we assign the current value in the for loop to a variable, we're fine.
Which issue(s) this PR fixes:
Fixes https://github.com/openshift/odo/issues/2987
How to test changes / Special notes to the reviewer:

Ran gosec before and after making the change and can confirm it goes away

/lgtm

/retest


Added the Career Support page

Description
Added the Career Support page
Fixes #794
Screenshots

Checklist

[x] Tests have been added or updated to cover the changes
[x] Documentation has been updated to reflect the changes
[x] Code follows the established coding style guidelines
[x] All tests are passing

@thestarsahil check this

Working Fine but fil the color according to project theme colors !

Working Fine but fil the color according to project theme colors !

Ohhh ok, the deep bluish colour??

@thestarsahil

check


[NOTICE] Open Source version deprecated

For anyone looking into this project, the open source version has ceased development.
If I could, I would archive this project but I'm no longer with PayPal and therefore no longer have any way of asking for this project to be archived.

cc @lenhattan86 or @misho-kr, I'd be super grateful if you could ask for this project to be archived.

Closing this issue for Archive workflow


Add support for elasticsearch async requests

When you don't have narrow filters you can often get pretty big & heavy requests that take a long time to fully load in the PLB, this could maybe be used to alleviate that.

A classic scroll is already performed today and from what I understand the async one is just a different kind of way of retrieving results partially.
But either way that is not going to speed up things if I understand what you are after. The problem is how the query pipeline works in PLB (and other query engines too).
Take this query for example (which is really heavy):
select *
from _doc
where _someField = 'someValue'    (assuming that _someField is indexed in elastic ang queryable)

The query plan for that query will be a simple scan operator with a predicate pushed down to Elastic catalog
  scan: _doc (query: "{ "term": { "_someField": "someValue" } }" )

.. and that operator must wait for the result to come back before returning it back to PLB, so no matther if you use sync/async query against ES it will take as long as it takes for Elasic to return it, and that is per batch of the scroll/async result.
To show even more why it must be this way let's extend the query above with a join:

select *
from _doc d
inner join _doc d1
  on d1._someOtherField = d._someOtherFieldTwo
where d._someField = 'someValue'

.. we are ending up with an plan like this:
  join:                   (some join algo. nested loop, hash join, etc.)
    scan: _doc (d)
    scan: _doc (d1)

And the way a join works is that we need all rows from both inputs before we can start to match rows, so even if we used an async call we would have to wait until the result comes back so that basically means that we would wrap the async call with a sync that waits until the async call returns :)


nsenter: failed to unshare namespaces: Invalid argument  script returned exit code 20

I was excited to see this sentence in the README and figured I give it ago having not tried the last couple of releases:

Since img v0.5.7, you don't need to specify any securityContext for running img as a Kubernetes container.

Pod:
apiVersion: v1
kind: Pod
spec:
  containers:
  - name: jnlp
    image: jenkins/jnlp-slave:3.29-1-alpine
  - name: img
    image: jess/img:v0.5.7
    command:
    - cat
    tty: true

Dockerfile used to test:
➜ cat Dockerfile
FROM alpine
RUN date

Output:
img build -t foo:latest .
nsenter: failed to unshare namespaces: Invalid argument
script returned exit code 20

you might need to disable seccomp and apparmor, and enable unpriv userns

Needs more info from me?

yes, e.g. kernel, kube distribution

Let me know if you need anything else!
OpenShift Master: v3.10.83
Kubernetes Master: v1.10.0+b81c8f8
OpenShift Web Console: v3.10.83

cat [root@xoshiftmp1 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.5 (Maipo)
[root@xoshiftmp1 ~]# uname -a
Linux xoshiftmp1 3.10.0-862.9.1.el7.x86_64 #1 SMP Wed Jun 27 04:30:39 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux

sudo sh -c "echo 28633 > /proc/sys/user/max_user_namespaces"

@AkihiroSuda inside the container or on the host?

host


Restructuring the repository

Is your feature request related to a problem? Please describe.
Navigating through the repository is difficult due to repetitive codes to the same problem in one folder.
Describe the solution you'd like
Arranging the codes as:
CodeChef:
|- C
|- C++
|- Java
|-Python
Hackerrank:
|- C
|- C++
|- Java
|-Python
and so on for all the websites.
Additional context
LGM-SoC'21 participant

@Amit366

As a participant and a fellow problem solver, I feel the Algorithms or Problem solving parts can be skipped being classified into Languages.
However, for HackerRank, if it is a language based problem, then it would help being organised into individual languages.

Hey @AtrikGit6174, I get your point but I already discussed this with the mentor before raising an issue. I thought of classifying the code into languages so that it will be easier for contributors to check before making issues and also for further maintaining the project.
Let's please wait for the mentors and PA to respond.
Some classification is needed is what we both agree upon right?

@tanvi355 it would be better if it is sorted according to language

@tanvi355 it would be better if it is sorted according to language

Yes, so should I start working on this?

Yes


Update the Screenshot of the Main Program

Describe the documentation
Update the screenshot of the pet image classification system program.

git fetch origin
git checkout 13-update-the-screenshot-of-the-main-program


Server behind Istio Gateway

Pre-requisites

[X] I have double-checked my configuration
[X] I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
[X] I have searched existing issues and could not find a match for this bug
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened? What did you expect to happen?
Downloaded, installed Argo Workflows 3.5.10, with secure=false and BASE_HREF=/ behind Istio, gives errors of:
upstream connect error or disconnect/reset before headers. retried and the latest reset reason: connection failure
Or, it just loads a blank page
Version(s)
3.5.10
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
No workflows yet being that I wasn't even able to get to that part
What I can tell you is that, I have set:
--secure false with BASE_HREF=/.
On Istio Gateway:
apiVersion: networking.istio.io/v1beta1
kind: Gateway
metadata:
  name: dev-gateway
spec:
  selector:
    istio: dev-ingressgateway
  servers:
  - hosts:
    - workflows.mycompany.com
    port:
      name: https
      number: 443
      protocol: HTTPS
    tls:
      credentialName: istio-ingress-server-tls
      mode: SIMPLE

VirtualService:
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  name: argo-vs
  namespace: argo
spec:
  gateways:
  - default/dev-gateway
  hosts:
  - workflows.mycompany.com
  http:
  - match:
    - uri:
        prefix: /
    rewrite:
      uri: /
    route:
    - destination:
        host: my-argo-workflows-server
        port:
          number: 2746

Kubernetes Service:
apiVersion: v1
kind: Service
metadata:
  labels:
    app: server
    app.kubernetes.io/component: server
    app.kubernetes.io/instance: my-argo-workflows
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: argo-workflows-server
    app.kubernetes.io/part-of: argo-workflows
    app.kubernetes.io/version: v3.5.10
    helm.sh/chart: argo-workflows-0.41.14
  name: my-argo-workflows-server
  namespace: argo
spec:
  clusterIP: <IP_ADDRESS>
  clusterIPs:
  - <IP_ADDRESS>
  internalTrafficPolicy: Cluster
  ipFamilies:
  - IPv4
  ipFamilyPolicy: SingleStack
  ports:
  - port: 2746
    protocol: TCP
    targetPort: 2746
  type: ClusterIP
status:
  loadBalancer: {}

Logs from the workflow controller
I haven't ran any workflows yet

Logs from in your workflow's wait container
I haven't ran any workflows yet

I also took a look and did some searching and saw something similar here: https://github.com/argoproj/argo-workflows/issues/3080#issuecomment-1278072332
from @arnoldrw and @agilgur5 , I tried that but to no avail.

You filed this as a bug, but this doesn't have to do with Argo and is not an Argo bug. The Server works and has E2E tests on CI, is used during dev, and many people have it working, including in the Ingress examples you linked.
You also had it working yourself on Slack. So this is an Ingress/Gateway configuration issue and not an Argo bug.


Update scala-library to 2.13.10

Updates org.scala-lang:scala-library from 2.13.8 to 2.13.10.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (2.13.8).
You might want to review and update them manually.
.github/workflows/ci.yaml
.github/workflows/release.yaml
.mergify.yml

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-lang", artifactId = "scala-library" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Codecov Report

Merging #675 (00c7334) into master (3cc837d) will increase coverage by 0.33%.
The diff coverage is n/a.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[Select] Fix custom font size centering arrow

Modifying the calc in order to center the select arrow vertically when the font size is changed [#26401}

[x] I have followed (at least) the PR section of the contributing guide.

Fixes #26401

@sarahannnicholson It's a great first pull request on Material-UI. Thank you for working on it!


SocketLite throws exception on start with UWP Net Native Toolchain compilation

Issue:
I'm attempting to use the SocketLite libraries for a Xamarin Forms UWP application. Everything works fine in the Debug/Release builds of the application with the 'Compile with .NET Native tool chain' setting turned off, but when the setting is turned on, an exception is thrown by the TcpSocketListener on the call to CreateObservableListener.

.NET Native tool chain setting (UWP Project -> Properties -> Build)

Exceptions (unfortunately I don't have a more helpful exception message):
Unhandled exception at 0x75D364A1 (combase.dll) in XF.TestApp.UWP.exe: 0xC000027B: An application-internal exception has occurred (parameters: 0x15065888, 0x00000001).
Unhandled exception at 0x75C7A2B9 (combase.dll) in XF.TestApp.UWP.exe: Stack cookie instrumentation code detected a stack-based buffer overrun.
Steps to reproduce:

Create a test Xamarin Forms project containing a UWP project
Install the SocketLite Nuget package in the Portable and UWP Projects
Add code to the portable implementation to start a TcpSocketListener.
Switch to release mode ('Compile with .NET Native tool chain' setting is on by default) and start the app => exception is thrown on CreateObservableListener
Uncheck 'Compile with .NET Native tool chain' setting and redeploy the app => no exception

Versions used:

SocketLite: 5.0.1
Microsoft.NetCore.UniversalWindowsPlatform: 6.1.7
System.Reactive...: 4.0.0
Xamarin.Forms: <IP_ADDRESS>7273
Portable projects using Net Standard 2.0

Have you tried with the updated version 5.1.1?

More info I found in the build output from building with 5.0.1:
C:\Program Files (x86)\Microsoft SDKs\UWPNuGetPackages\microsoft.net.native.compiler\2.1.8\tools\Microsoft.NetNative.targets(788,5): warning :       MCG : warning MCG0007: Unresolved P/Invoke method 'iphlpapi.dll!GetAdaptersInfo' for method 'System.Int32 SocketLite.Helper.AdapterInfo.GetAdaptersInfo(System.IntPtr, System.Int64)'. Calling this method would throw exception at runtime. Please make sure the P/Invoke either points to a Windows API allowed in UWP applications, or a native DLL that is part of the package. If for some reason your P/Invoke does not satisfy those requirements, please use [DllImport(ExactSpelling=true) to indicate that you understand the implications of using non-UWP APIs.
I tried updating SocketLite to 5.1.1 along with the required System.Reactive update to 4.1.0, and the build of the UWP app seems to hang indefinitely. I tried with SocketLite 5.1.1 and System.Reactive 4.0.0 and then I still got the same exception behavior as in 5.0.1.
I think System.Reactive 4.1.0 has some significant issues, would it be possible to also revert back to 4.0.0?
Thanks for your help!

If you use v5.0.1 then you will be using System.Reactive 4.0.0. There are not other differences between 5.1.1 and 5.0.1 than the move to System.Reative 4.1.0.
Let me know if this helps?
Also, I'll do some more research on System.Reactive 4.1.0.

Using 5.0.1 avoids the System.Reactive issue, but still has the issue with the exception being thrown at runtime when compiled with NET Native toolchain.
Thanks!

I was able to reproduce the issue in the SocketLite UWP test app run in Release mode with the following modification to MainPage.xaml.cs:
      public MainPage()
      {
        this.InitializeComponent();
        Start();
      }

      public async void Start()
      {
        var test = new TcpSocketListener();
        var temp = await test.CreateObservableListener(8004);
        temp.Subscribe(x => { });
      }


Site doesn't work correctly

Reproduction link
https://stackblitz.com/run?file=src%2Fstyles.css,src%2Fapp%2Fapp.component.ts
Steps to reproduce

open site https://ng.ant.design/
try to open next pages:

components -> Select
components -> Dropdown
components -> Tooltip
... a lot of places

open console in any page

Error in console:
chunk-NOKK6CHT.js:7 ERROR TypeError: t.hasAttribute is not a function
at u7 (chunk-NOKK6CHT.js:7:28447)
at FC (chunk-NOKK6CHT.js:7:48131)
at RC (chunk-NOKK6CHT.js:7:48094)
at NC (chunk-NOKK6CHT.js:7:48071)
at Mo.create (chunk-NOKK6CHT.js:7:70206)
at bf.createComponent (chunk-NOKK6CHT.js:7:73895)
at new e (chunk-NOKK6CHT.js:13:247232)
at e.ɵfac [as factory] (chunk-NOKK6CHT.js:13:247459)
at fr (chunk-NOKK6CHT.js:7:23904)
at WC (chunk-NOKK6CHT.js:7:51361)

Scripts on pages do not work.

What is expected?

No errors in console.
Scripts on pages do work.

What is actually happening?
https://ng.ant.design/
Error in console.
Scripts on pages do not work.

Environment
Info

ng-zorro-antd
17.4.0

Browser
chrome

It's not resolved.
I can't see the code examples of many components, and the error in the console didn't dissapear :(

none of the code block cant be toggle.

same here. cannot open code blocks and many other things

@ng-zorro-bot The site https://ng.ant.design/ is experiencing persistent script errors, impairing its functionality across multiple pages. Despite the passage of considerable time, the support team has not addressed this critical issue. This lack of responsiveness is highly unsatisfactory, underscoring the importance of promptly diagnosing and resolving the root cause of the site's malfunction


Fix coverage test for Babel 7

Summary
Opening this up separately to keep it focused. I think this is a bug?
Essentially https://github.com/facebook/jest/blob/ed671678796d4ceb7a6744e36490316ceedff5c2/e2e/coverage-report/notRequiredInTestSuite.js#L8-L11 is not reported as not covered. This is how the generated html report looks:

So the throw is no longer counted as a statement, which is wrong. (right?)
@bcoe any idea what's going on here? Help would be greatly appreciated 🙂 Background is that we're moving to Babel 7 (dropping 6). I'm not sure if it's a difference in the last versions of the babel istanbul plugin or if we're doing something odd.
Full diff against master can be seen in #7016.
Relevant istanbul dependnecy changes:

Test plan
I'd like for this PR to have 0 diff in the coverage snapshots, while still passing those tests (others will fail). Then I'll merge it into #7016.
The relevant test is e2e/__tests__/coverage_report.test.js

@coreyfarrell @JaKXz thoughts on this one?

I just copied notRequiredInTestSuite.js to a local folder, ran:
npx nyc --all --reporter html --reporter text ls.
This produced the report I expected.  It reported 0/5 statements and 0/5 lines covered.  The same 2 branches and 1 function not covered as your report.  I'm also seeing the expected transformation when I run npx nyc instrument notRequiredInTestSuite.js.
From grep it looks like jest instruments the source here:
https://github.com/facebook/jest/blob/7be2a8ef3f4d17b3ca139ba1a3dab72134306b50/packages/jest-cli/src/generateEmptyCoverage.js#L37-L38
If so can you post the value of transformResult.code for notRequriedInTestSuite.js?  If not please point me to how jest instruments notRequiredInTestSuite.js in this failing case.

Just want to mention I downloaded PR 7016 when I was looking at the jest sources locally.  I notice now that the link I gave to is not that PR's revision but those two lines don't appear to be different.
Also when testing your file with nyc I tried removing all options from our call to createInstrumenter and still got the expected result.

Instrumented code is:
"use strict";

/**
 * Copyright (c) 2014-present, Facebook, Inc. All rights reserved.
 *
 * This source code is licensed under the MIT license found in the
 * LICENSE file in the root directory of this source tree.
 */
throw new Error(`this error should not be a problem because` + `this file is never required or executed`); // Flow annotations to make sure istanbul can instrument non ES6 source

/* eslint-disable no-unreachable */

module.exports = function (j, d) {
  if (j) {
    return d;
  } else {
    return j + d;
  }
};
//# sourceMappingURL=data:application/json;charset=utf-8;base64,eyJ2ZXJzaW9uIjozLCJzb3VyY2VzIjpbIm5vdFJlcXVpcmVkSW5UZXN0U3VpdGUuanMiXSwibmFtZXMiOlsiRXJyb3IiLCJtb2R1bGUiLCJleHBvcnRzIiwiaiIsImQiXSwibWFwcGluZ3MiOiI7O0FBQUE7Ozs7OztBQU9BLE1BQU0sSUFBSUEsS0FBSixDQUNILDRDQUFELEdBQ0cseUNBRkMsQ0FBTixDLENBS0E7O0FBQ0E7O0FBQ0FDLE1BQU0sQ0FBQ0MsT0FBUCxHQUFpQixVQUFTQyxDQUFULEVBQW9CQyxDQUFwQixFQUF1QztBQUN0RCxNQUFJRCxDQUFKLEVBQU87QUFDTCxXQUFPQyxDQUFQO0FBQ0QsR0FGRCxNQUVPO0FBQ0wsV0FBT0QsQ0FBQyxHQUFHQyxDQUFYO0FBQ0Q7QUFDRixDQU5EIiwic291cmNlc0NvbnRlbnQiOlsiLyoqXG4gKiBDb3B5cmlnaHQgKGMpIDIwMTQtcHJlc2VudCwgRmFjZWJvb2ssIEluYy4gQWxsIHJpZ2h0cyByZXNlcnZlZC5cbiAqXG4gKiBUaGlzIHNvdXJjZSBjb2RlIGlzIGxpY2Vuc2VkIHVuZGVyIHRoZSBNSVQgbGljZW5zZSBmb3VuZCBpbiB0aGVcbiAqIExJQ0VOU0UgZmlsZSBpbiB0aGUgcm9vdCBkaXJlY3Rvcnkgb2YgdGhpcyBzb3VyY2UgdHJlZS5cbiAqL1xuXG50aHJvdyBuZXcgRXJyb3IoXG4gIGB0aGlzIGVycm9yIHNob3VsZCBub3QgYmUgYSBwcm9ibGVtIGJlY2F1c2VgICtcbiAgICBgdGhpcyBmaWxlIGlzIG5ldmVyIHJlcXVpcmVkIG9yIGV4ZWN1dGVkYFxuKTtcblxuLy8gRmxvdyBhbm5vdGF0aW9ucyB0byBtYWtlIHN1cmUgaXN0YW5idWwgY2FuIGluc3RydW1lbnQgbm9uIEVTNiBzb3VyY2Vcbi8qIGVzbGludC1kaXNhYmxlIG5vLXVucmVhY2hhYmxlICovXG5tb2R1bGUuZXhwb3J0cyA9IGZ1bmN0aW9uKGo6IHN0cmluZywgZDogc3RyaW5nKTogc3RyaW5nIHtcbiAgaWYgKGopIHtcbiAgICByZXR1cm4gZDtcbiAgfSBlbHNlIHtcbiAgICByZXR1cm4gaiArIGQ7XG4gIH1cbn07XG4iXX0=

Sorry to ask such a simple question but how can I run e2e/__tests__/coverage_report.test.js only?
One thing I noticed in the code you just linked is babelrc: false.  This does not block use of options from babel.config.js, it's possible you need configFile: false instead.  I point this out since it looks like #7016 renames .babelrc files to babel.config.js.

It appears the loss occurs in istanbul-lib-source-maps.
https://github.com/facebook/jest/blob/9d5ead81bd5ad067544da8fc655f672a232445ff/packages/jest-cli/src/reporters/coverage_reporter.js#L86-L88
After this map.data contains 4 statements for notRequiredInTestSuite.js, this._coverageMap correctly contains the 5 statements.  This is as far as I can troubleshoot right now.

To isolate things, I've set up a repository with 3 commits:

using babel 6 and the old istanbul module
upgrading istanbul to latest
upgrading to babel 7

Interestingly, the report is correct after step 2, it's only after changing to Babel 7 for the transpilation that we get the error. Could this be a babel bug instead?
See https://github.com/SimenB/weird-coverage-babel7

I'll have to take a look at this after I wake up some more (it's 6:30AM here and I'm just starting my coffee).  Before reporting to babel I'd like to take a look at the instrumented source and source-map from commits 2 and 3.  This way we can see what differences in source & source-map, determine if babel 7 is actually doing something wrong, or simply doing something different that istanbul-lib-source-maps doesn't properly handle.  Would probably help to use createInstrumenter({compact:false}) so that the instrument step doesn't produce compact code and it'll be easier to diff the results.
Interesting thing about your 3 step test<EMAIL_ADDRESS>uses babel 7 to translate the source.

I've collected some additional data though my knowledge of source maps is limited.
https://github.com/coreyfarrell/weird-coverage-babel7/tree/working patched index.js to save sources/source-maps after babel and istanbul.  Unfortunately I really don't what I'm looking at with the source maps.  They're different but I think that's expected since the babel output is different.

Oh that's interesting! Thanks for digging into it.
Removing that comment indeed fixes it! Or, "fixes" it I guess. Is this something that's possible to fix in babel? From the outside, it seems like a bug to not properly map back to where a statement ends, no? Or do you think Istanbul shouldn't care that it doesn't know where the statement ends?

Btw, what tool do you use to look at the source maps? Seems useful 🙂

@SimenB @loganfsmyth if there's a reasonable simple fix to the logic to make Istanbul more forgiving, I'd happily fix it on our end -- haven't had a chance to dig yet.

Wow, sorry my comment got posted so many times. With the Github issue yesterday it kept saying it hadn't gone through.
@bcoe Yeah I'd have to dig into it more to see how it might approach it. I'm not realistically sure I'll have time any time soon though, so I'm hesitant to make any promises. I'd probably be field questions from someone else if they wanted to try to tackle it though.

Rebased this, FWIW. @bcoe @loganfsmyth you wouldn't by any chance have the bandwidth to handle this now? 🙏
@jwbay maybe you know? (see the last few comments, identifying how the current approach in Istanbul is a bit brittle)

@SimenB with the long weekend coming up, I can try to carve out some time for this 👍 (have been pretty heads down with my on going scheme to help move coverage to v8 and Node.js core).
From your digging @loganfsmyth, it sounds like the problem is in the instrumenter potentially not being permissive enough when remapping lines of code from instrumented code back to the original?
@SimenB if we can figure out a reproduction here, it would make it easier or me to turn around a fix quickly.

@bcoe Awesome, thank you!
Regarding a reprodcuction, there is https://github.com/SimenB/weird-coverage-babel7, which is relatively minimal, just using @babel/core and 4 istanbul packages.

@loganfsmyth I've dug into this a bit further, and I'm confused. Looking at the example:

Isn't character 126 = ;, this is the end of the statement as reported by babel. I'm trying to figure out how Istanbul could end up in a scenario where it's trying to remap an empty space. The logic for recording statement ranges is as follows:
insertStatementCounter(path) {
        /* istanbul ignore if: paranoid check */
        if (!(path.node && path.node.loc)) {
            return;
        }
        const index = this.cov.newStatement(path.node.loc);
        const increment = this.increase('s', index, null);
        this.insertCounter(path, increment);
    }

to me it looks like Istanbul is doing the right thing and recording the range of just the original ThrowStatement:
SourceLocation {
  start: Position { line: 7, column: 0 },
  end: Position { line: 7, column: 106 } } Node {
  type: 'ThrowStatement',
  start: 204,
  end: 310,
  loc:
   SourceLocation {
     start: Position { line: 7, column: 0 },
     end: Position { line: 7, column: 106 } }```

any idea how we then end up in a position where it can't be mapped back to the same Node?

@bcoe The core thing is that the text ranges are inclusive on both sides, so conceptually the end position of the statement is just after the ;, which in this context ends up being equivalent to the position of the  . When you ask for that location to be mapped back to an original location, there's no real guarantee that it would exist since the space doesn't have a position in the original source file.

@loganfsmyth if I understand correctly though, these are the start and end positions being reported by babel itself for a ThrowStatement that has been observed during the parsing process:
https://github.com/istanbuljs/istanbuljs/blob/master/packages/istanbul-lib-instrument/src/visitor.js#L300
It feels like a bug to me that babel would report a position that can't be mapped back to a location, and I think this behavior is new to Babel 7; since it sounds like this worked historically?
I'm happy to implement a workaround based on any recommendations you have; but nothing jumps out at me immediately, how am I to know that the terminal position for a statement being parsed by babel doesn't map to anything?

@bcoe

it sounds like this worked historically?

This is popping up now because we happen to be putting comments in a few places we didn't before, meaning the file is more likely to have a space after the semicolon that doesn't map anywhere.

It feels like a bug to me that babel would report a position that can't be mapped back to a location

The locations in the AST are just character offsets in the parsed source. It doesn't even know that the map exists at that point. There can be many parts of an output file that have no local location. Babel's injected helpers for instance don't have a logical position in the original file. In this case, space between the comment and the semicolon also has no logical original location.

it feels presumptuous to assume, as an example, that I should -1 from the terminal position, what if this source position maps to a completely different statement?

Totally agree with you there.

I'm happy to implement a workaround based on any recommendations you have; but nothing jumps out at me immediately, how am I to know that the terminal position for a statement being parsed by babel doesn't map to anything?

In my opinion the core issue is that originalPositionFor isn't something that can be safely called with the end location of an AST node.
Unfortunately, I'm not sure the source-map module exposes a nice API for doing what you're doing in this context. Essentially, you want to compute the generated spans with computeColumnSpans and then find the span that includes the end position. As-is though, the only way to do that search would be to compute the spans, get all the mappings with .eachMapping and then do the binary search yourself. Workable, but certainly complicates things.

@loganfsmyth it feels like the computeColumnSpans approach could potentially have a performance impact as well, we'd only need to use this approach if the terminal position doesn't map back appropriately?
If I'm understanding correctly does the ThrowStatement's range include: ; ? so it's something like this:
throw new Error(`this error should not be a problem because` + `this file is never required or executed`); <space>```?

What I find slightly odd, is it claims that the original code is the range from `0 - 106`, which doesn't include the `<space>`; which would be a 107 characters -- edge-cases around remapping aside, we're sure we're not bumping into an off by one issue somewhere here?

I realize I mispoke earlier, the start location is inclusive and the end location is exclusive, so the behavior is the same for something like
const start = 1;
const end = 5;
"123456".slice(start, end) // "2345"
"123456"[end] // "6"

where the "6" isn't actually part of the content of the range, but is present at the actual end index. The end location of the AST node is essentially pointing at the space between the ; and the space, but the actual character offset of the end is the index of the space itself.
The current logic in Istanbul essentially treats both the start and end locations the same way and doesn't take this into account.

we'd only need to use this approach if the terminal position doesn't map back appropriately?

In most cases that is probably likely, but it's not really guaranteed. If someone were using compact: true in their Babel config, the space could also be the start of some other statement that does have an original position, just not one that corresponds to the end of the previous statement, e.g.
throw new Error();if(foo) {}

in that context the end position of the throw and the start position of the if are the same location, so it is important to know whether the position being mapped should be treated as a start or an end.

@loganfsmyth would this algorithm work:

for start position const start = sourceMap.originalPositionFor(location.start).
fetch all ranges for location.end.line: const ranges = sourceMap.allGeneratedPositionsFor({line: location.end.line, source: start.source}).
store the largestColumnValue, where it's equal to the largest value that's <= location.end.column .
run sourceMap.originalPositionFor({location.end.line, largestColumnValue}).

☝ will this work in the general case? I was a little unclear on how to pick the appropriate column value to remap.

Alright, I decided to sit down and work this out, since it's pretty hairy. I've tried to add as many comments as I can to try to help clarify it:
/**
 * AST ranges are inclusive for start positions and exlusive for end positions.
 * Source maps are also logically ranges over text, though interacting with
 * them is generally achieved by working with explicit positions.
 *
 * When finding the _end_ location of an AST item, the range behavior is
 * important because what we're asking for is the _end_ of whatever range
 * corresponds to the end location we seek.
 *
 * This boils down to the following steps, conceptually, though the source-map
 * library doesn't expose primitives to do this nicely:
 *
 * 1. Find the range on the generated file that ends at, or exclusively
 *    contains the end position of the AST node.
 * 2. Find the range on the original file that corresponds to
 *    that generated range.
 * 3. Find the _end_ location of that original range.
 */
function originalEndPositionFor(sourceMap, generatedEnd) {
    // Given the generated location, find the original location of the mapping
    // that corresponds to a range on the generated file that overlaps the
    // generated file end location. Note however that this position on its
    // own is not useful because it is the position of the _start_ of the range
    // on the original file, and we want the _end_ of the range.
    var beforeEndMapping = sourceMap.originalPositionFor({
        line: generatedEnd.line,
        column: generatedEnd.column - 1,
    });
    if (beforeEndMapping.source === null) return null;

    // Convert that original position back to a generated one, with a bump
    // to the right, and a rightward bias. Since 'generatedPositionFor' searches
    // for mappings in the original-order sorted list, this will find the
    // mapping that corresponds to the one immediately after the
    // beforeEndMapping mapping.
    const afterEndMapping = sourceMap.generatedPositionFor({
        source: beforeEndMapping.source,
        line: beforeEndMapping.line,
        column: beforeEndMapping.column + 1,
        bias: 2
    });
    if (
        // If this is null, it means that we've hit the end of the file,
        // so we can use Infinity as the end column.
        afterEndMapping.line === null ||

        // If these don't match, it means that the call to
        // 'generatedPositionFor' didn't find any other original mappings on
        // the line we gave, so consider the binding to extend to infinity.
        sourceMap.originalPositionFor(afterEndMapping).line !== beforeEndMapping.line
    ) {
        return {
            source: beforeEndMapping.source,
            line: beforeEndMapping.line,
            column: Infinity,
        };
    }

    // Convert the end mapping into the real original position.
    return sourceMap.originalPositionFor(afterEndMapping);
}

function getMapping(sourceMap, generatedLocation, origFile) {
    var start = sourceMap.originalPositionFor(generatedLocation.start),
        end = originalEndPositionFor(sourceMap, generatedLocation.end);

@loganfsmyth thank you so much! I can confirm that works for Jest's test and my reproduction. Any plans to open up a PR with it? 🙂

@loganfsmyth thank you for the reference implementation; @SimenB I'll see if I can't port it to an actual pull tonight.

@bcoe did you find some time to take a look? Wonder if there are any blockers

Opened up https://github.com/istanbuljs/istanbuljs/pull/254

@loganfsmyth @SimenB please see https://github.com/istanbuljs/istanbuljs/pull/255

We'll land Babel 7 with the slightly buggy coverage. Hopefully the alpha doesn't break too many people. But I think we should wait for the fix to land in istanbul (especially as it seems it'll be released as a major) before making Jest 24 stable

@SimenB @thymikee please give:
Successfully published:
 -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS>
a shot, the more we test the better since it's a relatively major change to what coverage JSON output looks like.

Awesome, thanks @bcoe! I updated, and will merge when CI is happy (the coverage tests passed locally, so no reason for it not to be happy).
We'll be releasing a new alpha today, hopefully it'll be without issue for folks 🙂

Node 8:
ReferenceError: location is not defined
    at getMapping (/home/circleci/jest/node_modules/istanbul-lib-source-maps/lib/transformer.js:121:19)

I'll restart to see if it's something flaky

Hmm, we got a failure in our coverage run:
ReferenceError: location is not defined
    at getMapping (/home/circleci/jest/node_modules/istanbul-lib-source-maps/lib/transformer.js:121:19)
    at /home/circleci/jest/node_modules/istanbul-lib-source-maps/lib/transformer.js:155:23
    at Array.forEach (<anonymous>)
    at SourceMapTransformer.processFile (/home/circleci/jest/node_modules/istanbul-lib-source-maps/lib/transformer.js:152:34)
    at /home/circleci/jest/node_modules/istanbul-lib-source-maps/lib/transformer.js:233:24
    at Array.forEach (<anonymous>)
    at SourceMapTransformer.transform (/home/circleci/jest/node_modules/istanbul-lib-source-maps/lib/transformer.js:223:25)
    at MapStore.transformCoverage (/home/circleci/jest/node_modules/istanbul-lib-source-maps/lib/map-store.js:143:8)
    at /home/circleci/jest/packages/jest-cli/build/reporters/coverage_reporter.js:172:59
    at Generator.next (<anonymous>)

You can reproduce by doing yarn jest init --coverage on this branch.

Just a typo, I'll send a PR!

@SimenB @thymikee please give this a shot:
Successfully published:
 -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS>
happy holidays, 🎄 🌴 🕎

Perfect, thanks @bcoe!

Oh, and thank you @loganfsmyth and @coreyfarrell!


fixed the way to hold http.Client

The Client's Transport typically has internal state (cached TCP connections), so Clients should be reused instead of created as needed. Clients are safe for concurrent use by multiple goroutines.
https://golang.org/pkg/net/http/#Client

@googlebot I signed it!

/ok-to-test

/approve

/lgtm
/approve


Naming

I'm not sure that dignified.js is the best name for this module, if it is to be accepted widely.

It comes off to me (as a native English speaker) that you're trying to give this tool respect by naming it something respectful. But you have to gain respect, not just name it, so it sounds a bit haughty. I think we should name it something else.
Ideally, the name would reflect the function. Naming is hard.  But what does this actually do?

Automated JavaScript project management.

That's really broad. Can we have a more concise definition to work with?

I had a very good discussion with @RichardLitt, and we came to the conclusion that because of the close association with my username and the possible misinterpretation of the word dignified I will rename the project to AEgir after the planet


communication error when using the PTZ module with companion 3.0

Hi,
I would like to use the canon PTC module for a canon cn500 camera but if I add the connection and fill in the correct IP address
the status goes to error and control of the camera is obviously not possible.
If I do the same on the version 2.2 of companion everything works fine.
is there some compatibility issue?
regards,
Ron

exactly the same for me. error is show, but the buttons do what they have to do (with a orange square on the top right). here is what is happening when I press a button a the streamdeck :
23.06.08 16:45:34 Surface/Handler/streamdeck:CL43J1A00852: Button 47.12 pressed
23.06.08 16:45:34 Instance/Wrapper/canon-500: failed


Add render_views to all controller specs

Currently, views do not get evaluated by our tests at all. Invoking render_views means that whenever we invoke a controller action, RSpec attempts to render the view template as well, rather than mocking it. At the cost of some slow-down, this means that template code gets executed and thus tested for syntax errors, which - in absence of view specs, which we don't plan to write - is a bare minimum we can do.

Now that integration tests are working and we've got a bunch of them set up (see #1219), I don't think we need the overhead of testing views in the controller specs. We should just work on expanding our integration test suite.


Create a Boto factory

Should credentials be reused from the Storage config? Via environment variables or explicit passing?
https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html

Won't fix. s3-file-field is now able to get S3 clients via the Storage instance, without needing to explicitly access credentials. Overwise, I'm not sure it's in scope or a good practice to steal AWS credentials from S3Boto3Storage (only when it's being used) to provide a general-purpose Boto instance.


Update/#165 remove pre attack domain

Description of what has changed

Removed the PRE-ATT&CK domain, including its matrix, techniques/tactics listings, and references to the domain on other pages.
Issues addressed by pull request

Closes #165

This branch name and pull request references the wrong issue. Closing this issue and creating a new one with the correct issue referenced.


XxdTest:test_compare_to_xxd failed

Describe the bug:
I try to run unit tests
build/env/bin/hue test fast

But I got this error.
======================================================================
ERROR: Runs xxd on some random text, and compares output with our xxd.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/deploy/hadoopeng/hue/apps/filebrowser/src/filebrowser/lib/xxd_test.py", line 98, in test_compare_to_xxd
    (stdin, stderr) = p.communicate(random_text)
  File "/usr/lib64/python2.7/subprocess.py", line 800, in communicate
    return self._communicate(input)
  File "/usr/lib64/python2.7/subprocess.py", line 1401, in _communicate
    stdout, stderr = self._communicate_with_poll(input)
  File "/usr/lib64/python2.7/subprocess.py", line 1465, in _communicate_with_poll
    input_offset += os.write(fd, chunk)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 0: ordinal not in range(128)

Steps to reproduce it?
./build/env/bin/hue test specific filebrowser.lib.xxd_test:XxdTest.test_compare_to_xxd

Hue version or source? (e.g. open source 4.5, CDH 5.16, CDP 1.0...). System info (e.g. OS, Browser...).
open source 4.7.0
CentOS Linux release 7.7.1908
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_242-b08)
(python 2.7.5)

Note on Python 3.8, xdd not installed:
./build/env/bin/hue test specific filebrowser.lib.xxd_test:XxdTest.test_compare_to_xxd
`======================================================================
ERROR: Runs xxd on some random text, and compares output with our xxd.
Traceback (most recent call last):
File "/home/romain/projects/hue/apps/filebrowser/src/filebrowser/lib/xxd_test.py", line 98, in test_compare_to_xxd
(stdin, stderr) = p.communicate(random_text)
File "/usr/lib/python3.8/subprocess.py", line 1024, in communicate
stdout, stderr = self._communicate(input, endtime, timeout)
File "/usr/lib/python3.8/subprocess.py", line 1846, in _communicate
input_view = memoryview(self._input)
TypeError: memoryview: a bytes-like object is required, not 'str'

Ran 1 test in 0.012s
FAILED (errors=1)`


Can't define new project

alited 1.0.6b13 on Lunux with Tcl/Tk 8.6.11
I start the program for the first time, specify a config location, define a new project in the projects window by editing the "Project name:" and "Root directory:" fields, and when I click the "Select" button, the error below appears. The project is not saved after the error window is closed.
ERROR file::DisplayFile:
() .alwin.fra.fra.pan.panR.fraTop.panTop.frAText.text !=
Please, notify alited's authors!
while executing

"alited::file::DisplayFile $TID $curfile $wtxt $doreload"
(procedure "GetText" line 72)
invoked from within
"GetText $TID yes"
(procedure "alited::main::ShowText" line 6)
invoked from within
"alited::main::ShowText"
("after" script)

I can define a project if after providing the name and root directory I hit the button to the left with the green plus icon.  The error only comes when I hit the "Select" button on the right.

If after defining a project I quit and restart alited, when I open the project window, click on the project I just created, and click the "Select" button, the same error as above appears.

This error seems to occur because when I defined the project, I hit the "Add" button or the "Substitute" button in the "Add a project" window.
If I define a new project, and hit the "Don't change" button, the project is created.
Sorry about the stream of consciousness reports.  I'm trying to work through learning the program.

Sorry again about the confused reporting.  The error always appears when I hit the "Select" button in the Projects window.  No other steps seem relevant.  If I dismiss the error and continue, the new project is opened and the program seems to work as expected.

If I create a project, then click on the default project in the Projects window, then click on my new project and click the Select button, the new project will open without an error.

I should simplify this thing.
Really, too much choices at the project creation, all those change/not change etc. For now, the best way to create a new project is:

enter a project name
enter a path to its root directory
hit [+] button
hit "Not change" at the follow-up question

The button "Select" makes sense only after these steps. I should check if a user tries enter a new project and hit "Select" before saving it.
If you can choose between Windows and Linux for a work with alited, I would recommend Linux. The Windows version of alited is raw yet, namely some e_menu stuff not working.
Also, alited is updated first in its fossil repo. The github one is for more or less "stable" versions. I.e. to get the fresh version, use this chiselapp link:
https://chiselapp.com/user/aplsimple/repository/alited/zip/trunk/alited.zip

The changes made:

introducing message at entering "Projects" (to be hidden)
Add / Change / Delete without superfluous warnings
Select button barks at a non-existing project
tiny-ups for notes / reminders

Changes available at
https://chiselapp.com/user/aplsimple/repository/alited/zip/trunk/alited.zip

The new version is much improved, thanks.  There's still one place where I get an error.  I take the following steps:

Start alited
open the Projects window
type in a new project name and project root.
Click Select button.  The warning that the project doesn't exist yet appears.
Click the + button.  Message that project has been created appears.
Click Select button.  The project appears to be selected correctly, but the following error pops up:

ERROR file::DisplayFile:
() .alwin.fra.fra.pan.panR.fraTop.panTop.frAText.text !=
Please, notify alited's authors!
while executing

"alited::file::DisplayFile $TID $curfile $wtxt $doreload"
(procedure "GetText" line 72)
invoked from within
"GetText $TID yes"
(procedure "alited::main::ShowText" line 6)
invoked from within
"alited::main::ShowText"
("after" script)

It's all about the importance of asserts. "That's impossible to appear but that appears". I should look into this issue closer. And try assert of tcllib instead of home-made checks. There are other places waiting for it.
Thanks for your scrutinizing notes!

I've made changes (project.tcl) to solve this problem. Pitifully I should decline control::assert because of control package isn't in basic tclkits with Tk. I use tclkits (e.g. made by BAWT) as sort of "core Tcl/Tk set of packages". By the way, this was the reason for using treeview instead of tablelist, everywhere in alited's appropriate places.
Changes available at
https://chiselapp.com/user/aplsimple/repository/alited/zip/trunk/alited.zip

Assert no longer appears in v1.0.6b26


Tech/travis snapshot

i'm not sure i'm doing the correct thing in the after_success block of the travis file.  "The goal you specified requires a project to execute but there is no POM in this directory "

@jaredsburrows mind lending a hand?

It looks like using travis command line tool changed the spacing. Why use mvn when this project is using gradle?

Can we just run gradlew upload archive from the after success?

See this blog: https://benlimmer.com/2014/01/04/automatically-publish-to-sonatype-with-gradle-and-travis-ci/.  Just use gradlew uploadArchives. As long as there is -SNAPSHOT it should go to the snapshot's repo here: https://oss.sonatype.org/content/repositories/snapshots/.

Thank you sir!

Check out @JakeWharton's project here: https://github.com/JakeWharton/RxBinding/blob/master/.travis.yml#L28. He does exactly what I am talking about. after_success calls gradlew uploadArchives here https://github.com/JakeWharton/RxBinding/blob/master/.buildscript/deploy_snapshot.sh#L24.

👍

The build passes but the upload fails: https://travis-ci.org/friendlyrobotnyc/TinyDancer/builds/171853376#L1499.

Do you need access for snapshots. Alternatively did you add keys to proper place?

When making changes to the maven-push.gradle file, I left these variables the same: https://github.com/friendlyrobotnyc/TinyDancer/blob/master/gradle/maven-push.gradle#L19.
According to the build, https://travis-ci.org/friendlyrobotnyc/TinyDancer/builds/171854936#L147, you all are using SONATYPE_USERNAME and SONATYPE_PASSWORD.
RxBinding has a similar naming: https://github.com/JakeWharton/RxBinding/blob/master/gradle/gradle-mvn-push.gradle#L25.
I suggest jus changing the variables in maven-push.gradle from NEXUS_USERNAME  and NEXUS_PASSWORD  to SONATYPE_USERNAME and SONATYPE_PASSWORD, respectively.

makes sense! trying that now!

Have you all tried publishing locally to test this out? Are you using the correct user/pass combo? Did you encode the correct user/pass? I am not sure why it is still failing :/.

Still failing: https://travis-ci.org/friendlyrobotnyc/TinyDancer#L1518.
Can you try uploading a snapshot locally?

yeah, it's not working locally.  I'll dig into it.

@digitalbuddha You can just delete those build.gradle versionCode and versionName. See https://github.com/JakeWharton/RxBinding/blob/master/rxbinding-design/build.gradle#L27. The versions are specified here: https://github.com/friendlyrobotnyc/TinyDancer/blob/master/build.gradle#L39 which is used here: https://github.com/friendlyrobotnyc/TinyDancer/blob/master/gradle/maven-push.gradle#L34. You can test all this out using gradlew installArchives here: https://github.com/friendlyrobotnyc/TinyDancer/blob/master/gradle/maven-push.gradle#L109.

thanks for the hand holding will try again at lunch.
On Mon, Oct 31, 2016 at 10:27 AM, Jared Burrows<EMAIL_ADDRESS>wrote:

@digitalbuddha https://github.com/digitalbuddha You can just delete
those build.gradle versionCode and versionName. See https://github.com/
JakeWharton/RxBinding/blob/master/rxbinding-design/build.gradle#L27. The
versions are specified here: https://github.com/
friendlyrobotnyc/TinyDancer/blob/master/build.gradle#L39 which is used
here: https://github.com/friendlyrobotnyc/TinyDancer/
blob/master/gradle/maven-push.gradle#L34. You can test all this out using gradlew
installArchives here: https://github.com/friendlyrobotnyc/TinyDancer/
blob/master/gradle/maven-push.gradle#L109.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/friendlyrobotnyc/TinyDancer/pull/46#issuecomment-257307819,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEUX3Bm93cBiqiGhpMw2caGitah2t8SZks5q5fq-gaJpZM4KkhT_
.

@brianPlummer @digitalbuddha Just test locally first! I think it may have to do with the travis ci setup and encrypting the username/password.

I'm going to merge. Im OK not having snapshot deploy work for now. We can revisit later.  Merging to get some other changes in

@digitalbuddha Can you at least release a new version?


add domains

Unfortunately, I do not know what service they are from, but I have experienced many registrations from these domains:
onlcool.com
mixinghphw.com

If I believe the verifymail.io (https://verifymail.io/domain/mixinghphw.com), they are from temp-mail.org

As you know fakefilter automates things, we have captures the seconddomain already by one of our watched providers... About the first one we really have to look. We do not add domains manually. We watch providers and remove them automatically after 1 year and wait until they enter our loop again.


Update eslint 3.14.1

This PR updates the eslint and eslint-plugin-react packages to newest release.
This makes the linting work properly with the extension of the Airbnb base rules.
Note: all let -> const have been done using --fix the useless escapes have only been removed as pointed out by the linter.

Run unit tests

Run integration tests

Nice work @mlunoe!


Misspell fix

Changed enabled to enable in line 9 (comment part)

This is just a simple fix of spelling in the example.lua file. Nothing else.


Update webpack.dev.js

Fix wrong config file, missing commas.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Other information:

https://github.com/AngularClass/angular2-webpack-starter/pull/1467


reconcile csiaddons subscription first

CSIAddons has no dependencies and it provides
VR and VRC CRDs which will be required by
ocs-operator csv, hence reconcile first.
Signed-off-by: Rakshith R<EMAIL_ADDRESS>

We do not need this PR, Changing the order is not going to help us at all at this point. We will already be having the subscription installed via OLM as we also use OLM pkg dependencies.


sync timestamps to binance server time

There is an issue when using this library on different platforms. It doesn't sync to the server properly causing any api calls to fail since the epoch seconds are more than a second apart. This implementation attempts to sync the server and the api client as much as possible. There will be some small time between the return of the server time call and setting the offset for the synced time.

I don't get/like getInstance() taking an input value, and why it's equal to -1.

You need it to be loaded after the binanceApiService is instantiated in both clients. I used a singleton because the entire library should use one time and should never differ.
So the only options I can think is to have the getInstance take an argument, have 2 getInstance methods (One with an argument and one without one), or let the server api clients configure and use their own. I don't care for the 2nd option since it could be used instantiated without using the server time. The 3rd option will potentially allow a different offset than the first SynchedTime object.
It's equal to -1 for all the calls that don't matter. The first call set in the constructor of the Api Clients uses SynchedTime.getInstance(serverTime). All the other call arguments don't matter so I used -1. (could have been anything)
Let me know what you think.

Can we please get this PR merged?


Config.json Error

Hello,
I am currently facing an issue where I cannot use the model, as the model_type field in the config.json is "multi_modality". Transformers then throws a ValueError, stating that Transformers does not recognize that architecture. I have tried uninstalling and reinstalling Transformers again before running as well as installing from source rather than pip, but nothing has seemed to work. I was wondering if there is a change or different model_type that should be used here?

Sorry for the late reply. It sounds like an issue with the runtime environment. You can set up the environment using the commands provided in the README.


AddPhysics on planet allows it to be deorbited #194

Minor features

AddPhysics on Base module for planets allows a planet to be pushed out of orbit. Intended for satellites or small props floating in orbit. Implements #194


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Corrected spanish translation of submit button to a  form challenge

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Can you please close this PR and open on a branch of your on fork?
Thank you.


replace root as the main user

I know that root is the default user when you create a droplet on DO (it was a thing I wanted DO to change), but let's be better, and create an user that have sudo access. I don't think it's critical, but I don't want people new to DO think we operate with root as our main user :)

Closing in favor of https://github.com/meilisearch/meilisearch-cloud/issues/1

Closing in favor of https://github.com/meilisearch/meilisearch-cloud/issues/1


jQuery 1.7.1 compatibility

Any word on whether this plugin still works now that were 3 versions of jQuery later?

This plugin actually doesn't even use jQuery.

I'm using 1.1 - 3/7/2010 fine with jquery 1.7.1


Update sky ssh runner

#1117  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @carolineechen and the rest of your teammates on  Graphite


Error handling on api-server unstable

Hi, tekton team.
Recently I find a case in my cluser: some TaskRun occasionally stopped with status TaskRunResolutionFailed. and the reason is the api servers is unavaiable, such as 'connection refused' or 'the server is currently unable to handle the request'. in tekton, this TaskRun's status will be set to TaskRunResolutionFailed.
This produce a very strange behaver,  for example, one of my pipeline has completed, and the status was Succeed, and later on a new Reconcile occuried, and the staus of this task became to TaskRunResolutionFailed.  and no matter how many Reconcile event occures, the status will nerver be Succeed again.

Expected Behavior
A task run would never change it's status once it has reached a final status
Actual Behavior
A task run changed form success status to failed status
Steps to Reproduce the Problem
this problem only happens when the cluster is not stable.

run an tekton pipeline
apiserver unavilable

Additional Info

Kubernetes version:  v1.19.11+k3s1
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.2", GitCommit:"5835544ca568b757a8ecae5c153f317e5736700e", GitTreeState:"clean", BuildDate:"2022-09-21T14:33:49Z", GoVersion:"go1.19.1", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.9+k3s1", GitCommit:"bead080d5e564206c23dcfbea3e6cf6f316e7f6c", GitTreeState:"clean", BuildDate:"2021-03-31T05:51:05Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.25) and server (1.19) exceeds the supported minor version skew of +/-1

Tekton Pipeline version:
v0.17.3

I wonder should we add a status check when we change the staus of Taskrun, maybe this could provent this problem

v0.17.3 is a very old release, over 2 years old now. There have been many changes and improvements to Tekton Pipelines since. Do you see the same behaviour with a recent release?

after updated to 0.43.0 version, the TaskRunResolutionFailed status has never appeared again. thx
/close


Unable to view TeamCity project builds

Hi
I'm trying to get your code running and for some the build configs are not displaying on the web page.
I have debugged the code and the TeamCityService seems to be pulling back the metadata from teh REST service but it is not being displayed in the view.
Would you be able to help me troubleshoot?
Many thanks
Ben

Hi Ben,
I'm on holidays with a very slow connectivity, i'll try to help you out when i'm back in a few days.
Meanwhile, can you detail if the build configs not showing up have something different from the ones showing correctly? Things like permissions, a build step that adds strange metadata to the result, anything odd you also spot on TeamCity page.
Cheers
Carlos Camacho

Hi
Thanks for your help.
I can't see any build configs in the view.  But metadata looks like it's
coming back. We're testing on TC 9.0.3 I think...
Cheers
Ben
On 21 July 2015 at 21:55, Carlos Camacho<EMAIL_ADDRESS>wrote:

Hi Ben,
I'm on holidays with a very slow connectivity, i'll try to help you out
when i'm back in a few days.
Meanwhile, can you detail if the build configs not showing up have
something different from the ones showing correctly? Things like
permissions, a build step that adds strange metadata to the result,
anything odd you also spot on TeamCity page.
Cheers
Carlos Camacho
—
Reply to this email directly or view it on GitHub
https://github.com/cmvcamacho/continuous-integration-dashboard/issues/1#issuecomment-123281137
.


electron-compiler

0.2.0-beta1

    --compile                               compile with babel
    --compile-opts <path>                   path of compile options

electron-compiler is not ready for this use case https://github.com/electron/electron-compile/issues/230


Create Documentation and README for BackupTully

documentation method is empty right now, implement it and provide a README with the help of it.

Maybe sample photos from interpreter can be provided later.


Define process for making closure-compiler future plans visible to the Open Source community

I'm proposing that we, the closure-compiler team, update our planning process to include some form of publication of those plans where they can be easily seen by the Open Source community.
I expect this increased visibility will make people much more comfortable using closure-compiler.
At the moment, I'm thinking this would include:
For each quarter:

New features we're actively working to add.
Limitations and bugs we're actively working to eliminate.
Use-cases we're actively working to enable.

In some general place, but reviewed for possible update each quarter.

A general statement of our goals for closure-compiler.
A gneral statement of use-cases we actively support (or don't).

Internal issue http://b/124249394 created for this


token : how tu use it

Hello
I'am interresting to using token for upload.
How can we use it for permit upload file on self hosted server ?
Thx

Hi, in your configuration file, just add a key named token like so:
token: mysupersecrettoken

This will automatically enable token usage, meaning all uploads will need to transmit this token before it is allowed to upload content to your self-hosted instance. Does this help?


[SPARK-44150][PYTHON][FOLLOW-UP] Fix ArrowStreamPandasSerializer to set arguments properly

What changes were proposed in this pull request?
This is a follow-up of #41503.
Fix ArrowStreamPandasSerializer to set type argument properly.
Why are the changes needed?
To fix CI.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing tests.

Thanks for the fix!

Thank you for the quick fix! :)

oh, wait. This might not be enough.. Let me continue taking a look.


Only getting 1 second of recording

When I attempt to record an environment, it only records 1 second worth of video.  What am I doing wrong?
import gym

env = gym.make("LunarLander-v2")
env.action_space.seed(42)

env = Recorder(env, './video')

observatio = env.reset()

# img = plt.imshow(env.render('rgb_array'))

observation = env.reset()
for _ in range(10000):
  # img.set_data(env.render('rgb_array'))
  # display.display(plt.gcf())
  # display.clear_output(wait=True)
  observation, reward, done, info = env.step(env.action_space.sample())

  if done:
      observation = env.reset()

env.release()
env.play()
env.close()

Take a look at the source code. When you call env.reset(), recording restarts, so what seems to be happening is you have some termination around iteration 9900 or so. From there, you call env.reset(), and the final video is only the last episode (or whatever has been made of it so far). I think you are under the assumption that videos are concatenated after env.reset(), which is not true. Instead, recording resets and begins a new video on env.reset().

@ryanrudes Apologies and thank you for your clarification. This all makes sense!


Immediate coredump

Arch Linux, qt6ct 0.6-2. Application is unable to be launched at all, immediately core dumping.
The core dump: https://envs.sh/QzN.core
The coredump info:
           PID: 6243 (qt6ct)
           UID: 1000 (rensenware)
           GID: 998 (wheel)
        Signal: 11 (SEGV)
     Timestamp: Thu 2022-10-06 00:27:25 EDT (2min 39s ago)
  Command Line: qt6ct
    Executable: /usr/bin/qt6ct
 Control Group<EMAIL_ADDRESS>          Unit<EMAIL_ADDRESS>     User Unit: vte-spawn-26fcd03d-5baa-44b9-b6df-a2fcb76add11.scope
         Slice: user-1000.slice
     Owner UID: 1000 (rensenware)
       Boot ID: edda17bcabaf4254944c8e2a18e29a74
    Machine ID: fe86cd201ca345bfbbaa51d5eb43c909
      Hostname: t480-arch
       Storage: /var/lib/systemd/coredump/core.qt6ct.1000.edda17bcabaf4254944c8e2a18e29a74.6243.1665030445000000.zst (present)
     Disk Size: 470.3K
       Message: Process 6243 (qt6ct) of user 1000 dumped core.

                Module linux-vdso.so.1 with build-id 5be7b2f03b3bbc1efefa813e8d744334e2b67b34
                Module libqt6ct.so with build-id f2fcb06511256a7438b9143075a998217df45b5f
                Module libffi.so.8 with build-id fb5dba105458f179a9153659f3ccd8e1056a2f35
                Module libwayland-cursor.so.0 with build-id 46a637dbcbb02d6712a201f177377b66598b9121
                Module libwayland-client.so.0 with build-id 515c72111400d7bdbfbdfcec78d597e4986a5943
                Module libQt6WaylandClient.so.6 with build-id 23696013e6a99f05a335ed7c92452f1b3245043a
                Module libqwayland-generic.so with build-id 1a065f1a8ac86178d1bc6133fd6f75db2c7dcc7d
                Module libgpg-error.so.0 with build-id 4738b8a9478177c202cccd64e0eb65d3dea2bfae
                Module libbrotlicommon.so.1 with build-id acfd597a977c8087bb6184383daae2e828a9ce42
                Module libXdmcp.so.6 with build-id d864159ab0008415667db8d5f251696d75c90df2
                Module libXau.so.6 with build-id d9d5e8277140f1a86d3a07d9b52b1703c0a2f9a8
                Module libgomp.so.1 with build-id 117ab7458eb756ac0e9e4791c510ae72fe710bd5
                Module liblz4.so.1 with build-id 84ea95d811dad359e94e100ebe6a746294ffe8a7
                Module liblzma.so.5 with build-id 8a7334fec02fef6a82ff641a68b3e3200a44a702
                Module libgcrypt.so.20 with build-id 8bf3cb884124273640de797a3e77d86c98434ea4
                Module libcap.so.2 with build-id 9b38b08de708f439a9d0a4f8b9914151bc8d4b50
                Module libicudata.so.71 with build-id 4fef196388e678deb881978139e125e20ee2d94d
                Module libbrotlidec.so.1 with build-id 66c54e9301f7e102ecc1d88547e5f0e8a056fe22
                Module libbz2.so.1.0 with build-id 919597c477c9b2cb9cdbb7745ed6494ac0e6da60
                Module libgraphite2.so.3 with build-id ce58945ebb55b86d3a4e717b6eae29efc4720d8e
                Module libdbus-1.so.3 with build-id 6dece245a58f1549ed98431e1242f487e8ebf9a2
                Module libpcre2-8.so.0 with build-id 917fc43d2c9f8539a3e324555c6c73886e8000a8
                Module libxcb.so.1 with build-id 13d677412a71468381b11092915d231f664d18d3
                Module libexpat.so.1 with build-id 52f685635e8711c1164d20a1ef8acd3840312094
                Module libGLdispatch.so.0 with build-id 7879a881271650eff97c35aff7a8674859c5ae94
                Module libzstd.so.1 with build-id ab54c2881f53ab314e134f3e08c76d504376dd5d
                Module libpcre2-16.so.0 with build-id 8ad49680a3f743a5241632a400d0de30aeaa54dd
                Module libb2.so.1 with build-id e39ae9514401c72c0e5cafa1abe0741360c22e87
                Module libdouble-conversion.so.3 with build-id 74bfa78f70f9ae1f759f0ae383fbc7f6f7faf6f8
                Module libsystemd.so.0 with build-id 63caa6a43422a3b88218d35317cf7611aa9f51ef
                Module libicuuc.so.71 with build-id 633fdc0c5385d916571f6140e7a978ad0630ef55
                Module libicui18n.so.71 with build-id 6fd5c97fd2808ee29958bf809656d5885e7e8963
                Module libz.so.1 with build-id fefe3219a96d682ec98fcfb78866b8594298b5a2
                Module libfreetype.so.6 with build-id f89dd5502e75aca28fb5c3ccd0dbd26fe822bfef
                Module libmd4c.so.0 with build-id 2151dba72cdc9960097e6e960a58a2f03c8bb96e
                Module libharfbuzz.so.0 with build-id 0083e085bcb9cb3869e5cb05fbcd9736c41434ab
                Module libpng16.so.16 with build-id 14d3b3cc9d61ec1b7c1f86bdf108218a99364945
                Module libOpenGL.so.0 with build-id 3df533822644f44fa89abdb75b9f89220dfdee56
                Module libGLX.so.0 with build-id d2c37fb8ec3bc53c67c013b0c6ac63ec086c8883
                Module libxkbcommon.so.0 with build-id 6cf66eead3fcc20fe5df10162bfbcdcdc8b2a183
                Module libQt6DBus.so.6 with build-id cd5a01c0313f99f4d1009205cddccff5d860bd6c
                Module libglib-2.0.so.0 with build-id 3ef8f9239c93af698703b12c5c6738fe0129eaa7
                Module libX11.so.6 with build-id 21e886e968772b7964d646f54c1faecc56734de9
                Module libfontconfig.so.1 with build-id 36be6951b8c1e42a7dd05684a37400fc8ef9147c
                Module libEGL.so.1 with build-id<PHONE_NUMBER>5bb4a3a44e794e2466e31bf0834209
                Module libm.so.6 with build-id 8a4929d22ebcbb96a075a378918a2804f49ca28f
                Module ld-linux-x86-64.so.2 with build-id 44db3ccb9e01b83c9cff0216f36e26d90c1ba85d
                Module libc.so.6 with build-id 21a9a7f001414ad7fce50b6aeb125889f39499d0
                Module libgcc_s.so.1 with build-id 85db482c4585a328d95ec41124337a967bb24d8f
                Module libstdc++.so.6 with build-id 735a3d0cc7699fd69337361cba4aedb644b2a7ed
                Module libQt6Core.so.6 with build-id 58691aace71818944994ca8feaf835e774031d59
                Module libQt6Gui.so.6 with build-id fc60e808c0e0f8caef00cfdb1f0feae4b6702759
                Module libQt6Widgets.so.6 with build-id fb5fb1f09b6a1ddefd2c330d68dc538a75bbfa91
                Module qt6ct with build-id 6114e2bce433d0cf298dbee6a084060205c92306
                Stack trace of thread 6243:
                #0  0x00007fa46e38547c _ZNK5QFonteqERKS_ (libQt6Gui.so.6 + 0x38547c)
                #1  0x00007fa46e38586e _ZNK5QFontneERKS_ (libQt6Gui.so.6 + 0x38586e)
                #2  0x00007fa46e1a40a2 _ZN15QGuiApplication7setFontERK5QFont (libQt6Gui.so.6 + 0x1a40a2)
                #3  0x00007fa46a7adaad _ZN18Qt6CTPlatformThemeC2Ev (libqt6ct.so + 0xaaad)
                #4  0x00007fa46a7a9f5b _ZN24Qt6CTPlatformThemePlugin6createERK7QStringRK5QListIS0_E (libqt6ct.so + 0x6f5b)
                #5  0x00007fa46e1cfd0d _ZN21QPlatformThemeFactory6createERK7QStringS2_ (libQt6Gui.so.6 + 0x1cfd0d)
                #6  0x00007fa46e1960b0 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt6Gui.so.6 + 0x1960b0)
                #7  0x00007fa46e197bc9 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt6Gui.so.6 + 0x197bc9)
                #8  0x00007fa46db2f28c _ZN23QCoreApplicationPrivate4initEv (libQt6Core.so.6 + 0x12f28c)
                #9  0x00007fa46e197c51 _ZN22QGuiApplicationPrivate4initEv (libQt6Gui.so.6 + 0x197c51)
                #10 0x00007fa46e96cade _ZN19QApplicationPrivate4initEv (libQt6Widgets.so.6 + 0x16cade)
                #11 0x0000564f34006994 main (qt6ct + 0x13994)
                #12 0x00007fa46d43d290 n/a (libc.so.6 + 0x23290)
                #13 0x00007fa46d43d34a __libc_start_main (libc.so.6 + 0x2334a)
                #14 0x0000564f34006fe5 _start (qt6ct + 0x13fe5)
                ELF object binary architecture: AMD x86-64

GNOME 42 on Wayland. I've tried messing around with running on xorg, making sure everything in the xorg group is installed, etc. Nothing works.
The gdb bt:
#0  0x00007fa46e38547c in QFont::operator==(QFont const&) const () from /usr/lib/libQt6Gui.so.6
#1  0x00007fa46e38586e in QFont::operator!=(QFont const&) const () from /usr/lib/libQt6Gui.so.6
#2  0x00007fa46e1a40a2 in QGuiApplication::setFont(QFont const&) () from /usr/lib/libQt6Gui.so.6
#3  0x00007fa46a7adaad in Qt6CTPlatformTheme::Qt6CTPlatformTheme (this=this@entry=0x564f359ffe90) at /usr/src/debug/qt6ct-0.6/src/qt6ct-qtplugin/qt6ctplatformtheme.cpp:69
#4  0x00007fa46a7a9f5b in Qt6CTPlatformThemePlugin::create (this=<optimized out>, key=..., params=...) at /usr/src/debug/qt6ct-0.6/src/qt6ct-qtplugin/main.cpp:54
#5  0x00007fa46e1cfd0d in QPlatformThemeFactory::create(QString const&, QString const&) () from /usr/lib/libQt6Gui.so.6
#6  0x00007fa46e1960b0 in QGuiApplicationPrivate::createPlatformIntegration() () from /usr/lib/libQt6Gui.so.6
#7  0x00007fa46e197bc9 in QGuiApplicationPrivate::createEventDispatcher() () from /usr/lib/libQt6Gui.so.6
#8  0x00007fa46db2f28c in QCoreApplicationPrivate::init() () from /usr/lib/libQt6Core.so.6
#9  0x00007fa46e197c51 in QGuiApplicationPrivate::init() () from /usr/lib/libQt6Gui.so.6
#10 0x00007fa46e96cade in QApplicationPrivate::init() () from /usr/lib/libQt6Widgets.so.6
#11 0x0000564f34006994 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/qt6ct-0.6/src/qt6ct/main.cpp:40

It only does it if I have the proper QT_QPA_PLATFORMTHEME=qt6ct variable set. All qt6 applications also crash in the same way if I have the variable set.

Rebuilding the program using the PKGBUILD the arch linux package uses also does not work.

So I was having the same issue, and it seems to have something to do with the fonts. I ran qt6ct with the platform theme variable unset and I changed the fonts, and then I was able to start qt6ct and other qt apps with the platform theme variable set; I'm guessing you could do this by editing the config file directly too, but I'm not too familiar with its format.

Another workaround is to downgrade to 0.5, configure fonts there and then upgrade again.

I had the same problem and I did what ernestoittig wrote to solve it (thanks!):

Remove QT platform theme variable in config files (~/.profile ; /etc/environment)
Reboot
Run qt6ct tool (which does not crash with a segmentation fault now) and configure fonts
Add platform theme variable again in config files
Reboot
QT6 applications no longer crash with a segmentation fault during start

How could one downgrade as antonio-rojas wrote?

The solution works for me. Won't close as the actual bug isn't yet solved.

Try latest version from git.

I can't try the latest git version by myself, but I noticed by running qt5ct and qt6ct from the terminal, that both tools crash with a segmentation fault when closing the tool now (after applying the workaround above).
Segmentation fault (core dumped)
I can provide details if needed. Other qt based applications seem to work without problems.

Try latest version from git.

This fixes the problem. To any other arch users, here's a pkgbuild for the git version of this. Copy into a PKGBUILD file in an empty directory and run makepkg -sir.
# Maintainer: Antonio Rojas<EMAIL_ADDRESS># Contributor: Martchus<EMAIL_ADDRESS># Contributor: Elliott Seymour<EMAIL_ADDRESS>
pkgname=qt6ct-git
_pkgname=qt6ct
pkgver=0.6.r2.g9e77604
pkgrel=1
pkgdesc='Qt 6 Configuration Utility'
arch=(x86_64)
url='https://github.com/trialuser02/qt6ct'
license=(BSD)
depends=(qt6-svg)
makedepends=(cmake qt6-tools)
source=('git+https://github.com/trialuser02/qt6ct.git')
sha256sums=('SKIP')
provides=('qt6ct')
conflicts=('qt6ct')

pkgver() {
  cd $_pkgname
  git describe --long | sed 's/-/.r/;s/-/./'
}

build() {
  cmake -B build -S $_pkgname \
    -DCMAKE_INSTALL_PREFIX=/usr
  cmake --build build
}

package() {
  DESTDIR="$pkgdir" cmake --install build
  install -Dm644 $_pkgname/COPYING "$pkgdir"/usr/share/licenses/$_pkgname/LICENSE
}

I can't try the latest git version by myself, but I noticed by running qt5ct and qt6ct from the terminal, that both tools crash with a segmentation fault when closing the tool now (after applying the workaround above). Segmentation fault (core dumped) I can provide details if needed. Other qt based applications seem to work without problems.

Please, provide backtrace here https://github.com/trialuser02/qt6ct/issues/15


extend DI: add possibility to register a factory function

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.005%) to 99.601%

Totals

Change from base Build<PHONE_NUMBER>:
0.005%

Covered Lines:
12292

Relevant Lines:
12294

💛  - Coveralls