Setting initial angle and center

@peterLaurence, could you help me again, please?
I got that I can use MapViewConfiguration.setStartScale to initiate the scale. But how to initiate angle and center for map properly?
p.s. I'm storing angle, scale & center between launching and also want a feature to open map positioned properly on the certain map's zone.

After the MapView has been laid out, you can do like so:
with(mapView) {
    angle = 15f
    val centerX = scrollX + halfWidth
    val centerY = scrollY + helfHeight
    post {
        scrollToAndCenter(centerX, centerY)
    }
}

I'm trying to apply ReferentialData:
with(mapView) {
    post {
        scale = data.scale
        setAngle(data.angle)
        scrollToAndCenter(data.centerX.toInt(), data.centerY.toInt())
    }
}

It rotates, scales, but not scrolls...

And it seems that it also moves to the top-left corner

I would check the values you have for data.centerX and data.centerY.
Typically, if those values are too small, it scrolls to the top left corner.

I found out that in:
override fun scrollTo(x: Int, y: Int) {
    val (constrainedX, constrainedY) = gestureController.setConstrainedScroll(x, y)
    super.scrollTo(constrainedX, constrainedY)
}

I got zeros in constrainedX, constrainedY.

Can you also explain when you're trying to restore the state of MapView? Is it on device rotation (and activity re-create?)

Ah, yes, the are small. Less than 1. It seems that they are between 0 an 1

I'm trying to restore ReferentialData just after configure.

I'm just trying to save it and restore to open map on a previous location.

Do you know that the MapView has an automatic feature of state restore (angle, scale and scroll) on device rotation?

I'm trying to share the ReferentialData between three MapView's to save the cache. To able fast switching between maps without reloading.

If you look at the doc of ReferentialData:

You can see that those values you have are in percent of the full width/height of your map.

I can't unde

Should I also ally scale to the formula?

That works incorrect...

You shouldn't use width and height, which might be 0 at the time you call
your function.
Instead, use the fullWidth and fullHeight you set at the configuration of
the MapView.
Le lun. 1 juin 2020 à 17:13, c0dd3vi11<EMAIL_ADDRESS>a écrit :

[image: Screenshot 2020-06-01 at 18 12 54]
https://user-images.githubusercontent.com/60510579/83423365-87643480-a433-11ea-9458-ff8d6ed6d117.png
That works incorrect...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/peterLaurence/MapView/issues/18#issuecomment-636915279,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADXKCCXPAKI74BA5OKIKNYTRUPARXANCNFSM4NPYMH2Q
.

Oh... this is so unobvious. I tried fullWidth/fullHeight and got the opposite situation, when viewport sticks to the right-bottom.

I did the combo! ^_^
fun TiledMapView.applyReferentialData(data: ReferentialData) {
    post {
        scale = data.scale
        setAngle(data.angle)
        val centerX = fullWidth * data.scale * data.centerX
        val centerY = fullHeight * data.scale * data.centerY
        scrollToAndCenter(centerX.toInt(), centerY.toInt())
    }
}


Implement Unregister Functionality in Iroha Client CLI

Objective:
To enable asset migration tests from Rust tests to client CLI tests, we need to implement the unregister functionality within the client CLI.
Requirements:

Implement a new CLI command, possibly named unregister, that will allow users to remove anything

I'm migrating unregister tests using json file processing with isi instructions for the client cli pytest framework.


Option to define an allow list for generating declaration/declarationMap

Suggestion

🔍 Search Terms

build mode, declarations, d.ts
✅ Viability Checklist

My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

It would be great tsconfig.json can expose a set of keys to say, "these are the only types that will be exported" from this module, and don't generate .d.ts for the rest.
📃 Motivating Example

When building under --build, TSC emits .d.ts for every single TS file in the module, but intuitively it only needs to
generate declaration files for the ones that's cross module boundary (so that other modules when referencing it),
which is likely a very small subset of types defined in the entire module.
💻 Use Cases

We have this problem where trying to switch build mode, TSC generates huge type declarations for files who are not
even referenced by other modules at all. The emit time is extremely high and incremental build is barely usable.
Sometimes it's not even possible to build-ify a project, if I have a module that,
export const thirdPartyLib = await import("3rd-party")

If this thirdPartyLib export a type that exposes an unimported type in its shape, we'll hit this error
error TS4023: Exported variable 'deps' has or is using name 'ElementsProps' from external module "node_modules/@stripe/react-stripe-js/dist/react-stripe" but cannot be named.

Concrete example: https://github.com/stripe/react-stripe-js/blob/master/src/components/Elements.tsx#L72

This is an interesting idea, especially since in principle we know if we're going to emit an import reference to another type

Right exactly, also this would probably reduce the emitter's job by a lot, and this change will only affect typescript, has no runtime behavior at all. Maybe we could even leverage the package.json new export map (https://github.com/jkrems/proposal-pkg-exports/)?

Bump this - given now the support for package.json export map is rolled out, seems a perfect time to add this feature on top.


InvalidCharacterError in Microsoft Edge

Iteration through an HTML element's attributes causes InvalidCharacterError exception in Microsoft Edge, starting from the version 41.16299.15.0 (Microsoft EdgeHTML 16.16299). The issue is not reproducible in older versions and in other browsers.
The root cause of the issue is enforced validation in EdgeHTML for attribute names. If provided value is not correct, InvalidCharacterError is thrown. The sample below fails to get an enumerator for NamedNodeMap (see bridge.js).
Steps To Reproduce
https://deck.net/9792d8735b8bbd70e032022410de0603
public class Program
{
    public static void Main()
    {
        var el = Document.CreateElement("input");
        el.SetAttribute("name", "test name");
        el.SetAttribute("value", "test val");

        foreach (var attr in el.Attributes)
        {
            Console.WriteLine(attr.NodeName);
        }
    }
}

Expected Result
Console output:
name
value

Actual Result
Console output:
System.Exception: InvalidCharacterError

See Also

[Forums]: InvalidCharacterError in Edge

Merged! The fix will make it to next Bridge version indicated by the milestone attached to this issue (currently 16.6.1).


fix(tabs): update Tabs to match style specs

Tickets:
https://app.shortcut.com/sci-design-system/story/152077/update-tabs-component-for-sds
https://app.shortcut.com/sci-design-system/story/167635/update-stories-for-tabs-to-csf-format

Updates Tabs to match style specs
Update story book stories to follow CSF format
Add simple tests

PTAL thank you 😄 🙏

Hurray! Thanks so much, @mdjmoore 🤩 🙏
@clarsen-czi PTAL too, just in case I missed any style specs 😆 Thank you!!

Thanks so much for the review, @clarsen-czi 🎉 !
Yeah I think other variants will be created later, since the ticket's scope is just the large tab, underline, no counter one, I believe?
https://app.shortcut.com/sci-design-system/story/152077/update-tabs-component-for-sds

Thanks again!

Oops my bad! Sorry for missing that—I see that we have other tickets made for implementing the other variants, so we should be good. I'll move the details for the Live Preview to a new ticket since that live preview needs to encapsulate all of the tab variants.

No worries! Thanks so much for taking care of the Live Preview ticket shuffling 🤩 🙏 !
Will merge this one now!


 Feel free to dig into it if its urgent for you.

This is fixed in v1.2.3


Export additional columns from requests collection

🗣 Description
In order to keep cyhy data in sync with the mini data lake we need to pull additional fields. This PR adds additional fields to the projection from the requests table.
💭 Motivation and context
This will allow the mini data lake to keep in sync with the cyhy database, and it will also allow the ASM Visibility Dashboard to use these additional fields when generating dashboards and creating reports
🧪 Testing
Verified all added projections are fields in the requests collection
✅ Pre-approval checklist

[X] This PR has an informative and human-readable title.
[X] Changes are limited to a single goal - eschew scope creep!
[X] All future TODOs are captured in issues, which are referenced
in code comments.
[X] All relevant type-of-change labels have been added.
[X] I have read the CONTRIBUTING document.
[X] These code changes follow cisagov code standards.
[X] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[ ] Tests have been added and/or modified to cover the changes in this PR.
[ ] All new and existing tests pass.

✅ Pre-merge checklist

[ ] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Create a release.

@dav3r Here is the PR with the updated projection

I believe with this pull request the projection becomes everything per the schema. If that is the case we should consider using an empty projection.

I agree that makes more sense, just wasn't sure if we wanted to be explicit in stating all fields, but this commit removes the projections: e1f73a9

@DJensen94 - You needn't run the linter manually.  See the instructions for setting up pre-commit locally.

@DJensen94 Please update the PR description to clearly specify which new fields and collections are being added in this PR, as well as the reason(s) why they are now required.  Thanks!

Regarding https://github.com/cisagov/cyhy-feeds/pull/52/commits/9b4879ee4e3c58299b6528689f64d25d5ac8ebff, why are you putting the snapshots change in a separate PR?

Regarding 9b4879e, why are you putting the snapshots change in a separate PR?

I was asked to move this to a separate pull request since we are still awaiting approval for the key and contacts and the snapshots pull is more time sensitive.

@DJensen94 @climber-girl @jessiebeals - Is this PR still needed?


TranslationKey pagination

Codecov Report

Merging #163 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           develop    #163   +/-   ##
=======================================
  Coverage     42.3%   42.3%
=======================================
  Files           11      11
  Lines           78      78
  Branches         7       7
=======================================
  Hits            33      33
  Misses          44      44
  Partials         1       1

Impacted Files
Coverage Δ

src/models/Project/index.js
0% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


New package: OpenSSL v1.0.0

Registering package: OpenSSL
Repository: https://github.com/JuliaWeb/OpenSSL.jl
Created by: @quinnj
Version: v1.0.0
Commit: a4dba328b9e497348ebd603fc9ba884ddcce3ec0
Reviewed by: @quinnj
Reference: https://github.com/JuliaWeb/OpenSSL.jl/commit/a4dba328b9e497348ebd603fc9ba884ddcce3ec0#commitcomment-82554168
Description: OpenSSL Julia bindings

OpenSSL is arguably the more widely known amongst OpenSSL, OpenCL, and OpenML. It also seems visually distinct enough to not cause confusion.

@quinnj Can you ping me in 3 days?

Friendly 3-day ping!


User-modifiable code lists in exported files

“User-Modifiable” code lists like PopulationServed should only export unique instances that the user has added, i.e. that are not provided from the server. If the user, in Airtable, modifies the properties (other than @id) of a “non-modifiable” code list item their changes to that list item should be overwritten in the export by the data from the server.

We should be good now. The extension will correct every import or export operation if the user changes the default code list values. In addition, we only export the custom values in the table. With this, we assume each software will be responsible for keeping the default code lists.


feature: Use QuickJS instead of V8

Migrate from the current JS implementation to use QuickJS.
Technical Requirements

Use https://docs.rs/rquickjs/latest/rquickjs/
Ensure all existing tests pass
Perform a benchmark to compare differences in performance

Additional Details

Here are the existing benchmarks https://bellard.org/quickjs/bench.html

/bounty 350$

/attempt
I will try.

/attempt #1690

@abhishek818
I will try first, if no pr from me by tomorrow.
it is up for grabs.

On the queue. As my main focus is Node, it'd be very fun to work on this :smile:

@abhishek818
@ologbonowiwi
i am dropping.

this might be helpful.
https://github.com/DelSkayn/rquickjs/issues/97

@tusharmath, why not use a node-compatible runtime?
Having non-V8-based/backward compatibility can bring issues for users, as everyone is already used to V8 and knows how it works.
If we move forward in getting something non-V8 compatible, we need extensive examples/docs from the users. If I were using JS with tailcall and suddenly my stuff stopped working because of a different runtime, I'd think deeply about dropping from tailcall.

as the doc says
http filter feature is for only simple
https://tailcall.run/docs/guides/http-filters/https://tailcall.run/docs/guides/http-filters/
Any example for diff where it breaks?

I don't have any examples @webbdays, nor I'm sure it'll break 😅
Only adding this concern to the discussion 🚀

@tusharmath, why not use a node-compatible runtime?

Node is an independent runtime, nothing is truly node compatible, not even deno or bunjs. Tailcall doesn't need to be a full-fledged JS runtime because JS is just used to write light weight logic to modify requests and responses.

Having non-V8-based/backward compatibility can bring issues for users, as everyone is already used to V8 and knows how it works.

V8 and QuickJS might not be all that different. Here is the feature comparison https://test262.fyi/#|v8,qjs

If we move forward in getting something non-V8 compatible, we need extensive examples/docs from the users. If I were using JS with tailcall and suddenly my stuff stopped working because of a different runtime, I'd think deeply about dropping from tailcall.

I don't think users even know if they are on v8 or not. QuickJS has a reasonable coverage of features, so I don't things will just stop working.
Also checkout what AWS is doing in their LLRT https://github.com/awslabs/llrt/blob/main/Cargo.toml#L21

/attempt


Grid View hover

Decrease brightness on hovered items in grid view. Temp solution to #228

I looked at the Android code, and it is using "ButtonSelectedColor" when the user is mouseDown over a tile.

This would be the way that you would have reactive hover color defined from the theme colors:
$: buttonSelectedColor = $themeColors['ButtonSelectedColor'];

Tried to implement and did not work. Used on:touch and on:mouseover to try to replicate hover which is recognized by both mobile and web but does not work either despite touch/mouse events being registered. Needs alternative solution. Somehow bg color is hard stuck and isn't reactive.

Recognized the problem with the new solution:
<span
    on:click={() => handleClick(cell.id)}
    class="dy-btn dy-btn-square dy-btn-ghost normal-case truncate text-clip"
    style={cellStyle}
    style:background-color={hovered === cell ? 'red' : 'blue'}
>
    {cell.label}
</span>

hovered is an event target/span being compared to a cell object.

No touchenter and touchleave events exist. Only touchstart, touchend, touchmove, and touchcancel are availible.

Here is a solution but on my testing it responds slowly

@jakedcolbert It seems to solve the problem.  However, there are issues with moving the touch around with the app in general.  I will try to address that.

I fixed the issues.


type=playbook - question for outputformatset usage

Describe the bug
Output file generated by outputformatset seems buggy, sometimes 0 byte size or not-working commands
Expected behavior
I run the following command and playbook :
Command:
pan-os-php type=playbook json=pb_cleanup_unused-objects.json in=Export_Exped_2023-07-11.xml stagename=stages/stage- outputformatset=set-commands.txt out=cleanconfig.xml
Playbook:
{
"command": [
{
"type": "address",
"location": "location=any",
"actions": "actions=exporttoexcel:addresses_unused.html",
"filter": "filter=(object is.unused.recursive )",
"shadow-ignoreinvalidaddressobjects": "shadow-ignoreinvalidaddressobjects"
},
{
"type": "service",
"location": "location=any",
"actions": "actions=exporttoexcel:services_unused.html",
"filter": "filter=(object is.unused.recursive )"
},
{
"type": "tag",
"location": "location=any",
"actions": "actions=exporttoexcel:tags_unused.html",
"filter": "filter=(object is.unused )"
}
]
}
I would expect that the file set-commands.txt contains all necessary set commands in the correct order to delete all unused objects (addresses, services, tags).
Current behavior
For some playbooks like the above the created set-commands.txt file is empty.
For other playbooks, among correct commands, I also get commands in that file like this:
delete Ton-Contractor_192.168.20.x
delete Ton-Contractor_192.168.20.x
delete Ton-Contractor_192.168.20.x
So not only does the command exist several times, it would obviously also not work without device group etc.
Possible solution
I think that the created set file was correct with previous pan-os-php versions.
Steps to reproduce
I ran the script several times with both develop and latest.
docker pull swaschkut/pan-os-php:develop
docker run -it -v /home/expedition/:/share swaschkut/pan-os-php:develop
docker pull swaschkut/pan-os-php:latest
docker run -it -v /home/expedition/:/share swaschkut/pan-os-php:latest
Screenshots

Context

Your Environment
Azure Ubuntu VM, running on our Expedition server
$ uname -a
Linux servername 5.15.0-1038-azure #45~20.04.1-Ubuntu SMP Tue Apr 25 18:45:15 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
$ pan-os-php version

PAN-OS-PHP version: 2.1.9 [UNIX]
/tools/pan-os-php/utils
PHP version: 8.1.2-1ubuntu2.13

thanks for reaching out and sharing your findings with me.
Please allow me to check this in the next coming two weeks

please allow me to re-ask:
for all three playbook task you are looking for unused objects to generate a HTML spreadsheet.
What is your expectation for the set commands, if you are not manipulating the config file at all?
all these three HTML files I assume are available, and the set-command file, must be empty;
as it is not empty, the reason is that playbook file is adding this to existing file if available;
it is also empty as you defined NOT to delete any unused object, you only create spreadsheets;
please change your JSON playbook file to e.g. actions=delete
so that the set-command.txt file is creating lines which you can send.
{
"command": [
{
"type": "address",
"location": "location=any",
"actions": "actions=delete",
"filter": "filter=(object is.unused.recursive )",
"shadow-ignoreinvalidaddressobjects": "shadow-ignoreinvalidaddressobjects"
},
{
"type": "service",
"location": "location=any",
"actions": "actions=delete",
"filter": "filter=(object is.unused.recursive )"
},
{
"type": "tag",
"location": "location=any",
"actions": "actions=delete",
"filter": "filter=(object is.unused )"
}
]
}
please re-run your playbook command with a JSON playbook file, which is manipulating your configuration file

OMG, you made my day, your playbook works, thank you so much!
I totally misunderstood how that script works, sorry to waste your time. I was under the assumption that the set-commands file would always be created when using the outputformatset parameter.
If I may ask one last question, I wanted to use this for merging our duplicate address objects:
{
"type": "address-merger",
"location": "location=any",
"filter": "filter=!(object is.fqdn)",
"DupAlgorithm": "DupAlgorithm=SameAddress",
"exportcsv": "exportcsv=addresses_tomerge.html",
"allowmergingwithupperlevel": "allowmergingwithupperlevel",
"shadow-ignoreinvalidaddressobjects": "shadow-ignoreinvalidaddressobjects"
}
Now I am unsure what would be the correct mechanism to create the set-commands file...?
Is there maybe some website with examples?

Awesome, thank you very much for your quick help. :-)

yw;
based on your GitHub name, I assume best greetings from Germany to Germany :-)

Da hast du absolut recht. :-)
Beste Grüße,
Carsten

Hallo Michael,
bitte schreibe mich kurz via
swaschkut [at] paloaltonetworks.com
vieles lässt sich ueber nicht oeffentliche Wege einfacher klären :-)


need "Approve and run" when first-time contributors submit a PR

Actual Behaviour

First-time contributor needs approve and run to check what's the status of CI
Expected Behaviour
PR could run CI automatically, so developers could see what happened to that PR. We need to ask help from ASF Infra.

cc @lxm to know this.

I've got a workaround for limited cases.
1. fork the project
2. enabled the actions (actions is disabled by default for fork repos)
3. create pr both to upsteam repo and personal forked repo
4. actions will be triggered  in personal repo

this can be a workaround for actions with out secrets

Good!

Is this still a issue? I've forgotten my original PR.

No, this is enabled by the ASF.


Build notifications (sendgrid)

For admins
For users (confirmation of request, other?)

Email to start with, maybe text?

Moved to miro (as outstanding question).


add SF_LOGIN_URL to ecars-pwa

What does this PR do?
Adds support to SF_LOGIN_URL env variable for ecars-pwa
What issues does this PR fix or reference?
https://github.com/trailheadapps/ecars/issues/180
The PR fulfills these requirements:
[ ] Tests for the proposed changes have been added/updated.
[x] Code linting and formatting was performed.
Functionality Before
No SF_LOGIN_URL support, just https://test.salesforce.com
Functionality After
SF_LOGIN_URL support, defaulting to https://test.salesforce.com on the deploy script

⚠ CodeTour Watch
Changed files with possible CodeTour impact:

README.md
apps/ecars-pwa/src/server/api.js

Impacted CodeTour files:

.tours/1---overview.tour - ⚠ Missing from PR

Not affected.

.tours/2---progressive-web-app-and-lead-generation.tour

Make sure to review CodeTour files and update line numbers accordingly.


[BUG]:

Contact Details [Optional]
No response
System Information
NA
What happened?
In generative-chat example, the readme docs contains instructions specifying slack token as env variable, shouldnt the env var name be SLACK_BOT_TOKEN instead of SLACK_API_TOKEN as in the code that is what is used.
https://github.com/zenml-io/zenml/blob/df95a26558622de294bd4ea6cc74808e3e10633a/examples/generative_chat/steps/slack_loader.py#L51
Reproduction steps
No response
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I think a lot of that code was taken from Slack docs, but we'd take a PR on that, for sure!

This has now been merged. Thanks!


Azure management cluster E2E tests failing

Bug Report
Azure management cluster E2E test seems to be failing since Tanzu Framework bump
https://github.com/vmware-tanzu/community-edition/actions/workflows/e2e-azure-management-and-workload-cluster.yaml
https://github.com/vmware-tanzu/community-edition/runs/4217019212?check_suite_focus=true#step:5:2026
Error: unable to set up management cluster: unable to wait for cluster and get the cluster kubeconfig: error waiting for cluster to be provisioned (this may take a few minutes): timed out waiting for cluster creation to complete: cluster control plane is still being initialized: ScalingUp

https://github.com/vmware-tanzu/community-edition/runs/4217728775?check_suite_focus=true#step:5:2022
 Error: unable to set up management cluster: unable to wait for cluster and get the cluster kubeconfig: error waiting for cluster to be provisioned (this may take a few minutes): timed out waiting for cluster creation to complete: cluster control plane is still being initialized: ScalingUp

https://github.com/vmware-tanzu/community-edition/runs/4231869877?check_suite_focus=true#step:5:2034
Error: unable to set up management cluster: unable to wait for cluster and get the cluster kubeconfig: error waiting for cluster to be provisioned (this may take a few minutes): timed out waiting for cluster creation to complete: cluster control plane is still being initialized: WaitingForBootstrapData @ Machine/test-mc-9299-control-plane-kjf5z

Expected Behavior
Azure management cluster E2E tests to pass
Steps to Reproduce the Bug
Run Azure management cluster using TCE v0.10.0-rc.1 or from any commit since https://github.com/vmware-tanzu/community-edition/commit/dccd271d08c092c69415d8e2dbcfa8cafe017c69
Screenshots or additional information and context
--
Environment Details

Build version (tanzu version): https://github.com/vmware-tanzu/community-edition/commit/dccd271d08c092c69415d8e2dbcfa8cafe017c69 or beyond
Deployment (Managed/Standalone cluster): Manged cluster
Infrastructure Provider (Docker/AWS/Azure/vSphere): Azure
Operating System (client): Linux

Diagnostics and log bundle
Unfortunately I don't have them 😞

Attaching the tanzu diagnostics run logs when hit the same issue in local run
bootstrap.tkg-kind-c6bme0l94819us7vnong.diagnostics.tar.gz

Attaching the kind logs that is collected on the same cluster to get the capz controller logs
kind-logs-azure-managment-cluster.tar.gz
r

We found out that the issue was that the Azure VM image license was not accepted, causing the issue.
2021-11-19T09:07:47.8166081Z stderr F E1119 09:07:47.816382       1 controller.go:257] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create AzureMachineService: failed to create virtual machine: failed to create VM mgmt10-control-plane-mqhdc in resource group az10: compute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code=\"ResourcePurchaseValidationFailed\" Message=\"User failed validation to purchase resources. Error message: 'You have not accepted the legal terms on this subscription: '3acb4fa4-4486-4bb9-9168-9c9cab47ddb3' for this plan. Before the subscription can be used, you need to accept the legal terms of the image. To read and accept legal terms, use the Azure CLI commands described at https://go.microsoft.com/fwlink/?linkid=2110637 or the PowerShell commands available at https://go.microsoft.com/fwlink/?linkid=862451. Alternatively, deploying via the Azure portal provides a UI experience for reading and accepting the legal terms. Offer details: publisher='vmware-inc' offer = 'tkg-capi', sku = 'k8s-1dot21dot5-ubuntu-2004', Correlation Id: '54d67095-0e6d-4ed4-afdc-c2cac8a81ac1'.'\"" "controller"="azuremachine" "name"="mgmt10-control-plane-mqhdc" "namespace"="tkg-system"

This is due to E2E test script hard coding the VM image ID here
https://github.com/vmware-tanzu/community-edition/blob/438ba11825108fc5281d10d2c198c9085c6e641b/test/azure/deploy-management-and-workload-cluster.sh#L53
Causing the E2E test automation to accept VM image license for an older VM image but not for the latest VM image referred in the latest TKr BOM file - tkr-bom-v1.21.5+vmware.1-tkg.1-tf-v0.10.0.yaml from projects-stg.registry.vmware.com/tkg/tkr-bom:v1.21.5_vmware.1-tkg.1-tf-v0.10.0. Azure Standalone cluster E2E tests don't have an issue though, since they still use an older version of tanzu-framework and the same old TKr BOM files and Azure VM images which is the same one referred to in the Azure standalone cluster E2E test script
https://github.com/vmware-tanzu/community-edition/blob/438ba11825108fc5281d10d2c198c9085c6e641b/test/azure/deploy-standalone-cluster.sh#L52
I'll raise a PR to fix this. For now I have manually accepted the VM image license by using the TCE E2E test pipeline's Azure subscription. I did this from my local using a temp secret created for the tce-pipeline Azure application which I deleted later. I used the same set of commands to accept the Azure VM image license as mentioned in the E2E test script code. I did this to re-run the existing jobs. The latest jobs would work fine once the PR is merged, and VM image licenses would always be accepted automatically in the E2E test though just once is fine
I'll also create an issue to fix the hard coding of the Azure VM image. The solution would be something around finding the TKr BOM that's going to be used by the tanzu command and then use it to accept the Azure VM image license. Finding the TKr BOM that's going to be used can be tricky though 😅


migrations not working

I'm having several problems in a row in the migration part using Prisma.
running the deploymend part commands in readme.md
pnpm migrate
I get errors in some tables stating the following:

when removing these tables from the script, others are highlighted. And eventually, removing all that have errors means the site just won't open.
I'm also trying to run it through docker.
But the tests I did were local on Debian Linux.
I will attach my docker configurations
[Dockerfile.site.txt](https://github.com/luan/slenderaac/files/12775300/Dockerfile.sit
docker-compose.yaml.txt
e.txt)
schema.sql.txt

Docker configuration files:
schema.sql.txt
Dockerfile.site.txt
docker-compose.yaml.txt
.env FILE:
Mariadb
MYSQL_DATABASE=otservbr-global
MYSQL_USER=canary
MYSQL_PASSWORD=canary
MYSQL_ROOT_PASSWORD=root
Login
LOGIN_HTTP_PORT=80
LOGIN_GRPC_PORT=9090
MYSQL_HOST=database
MYSQL_PORT=3306
MYSQL_DBNAME=otservbr-global
MYSQL_USER=canary
MYSQL_PASS=canary
SERVER_NAME=OTServBR-Global
SERVER_IP=<IP_ADDRESS>
SERVER_PORT=7172
SERVER_LOCATION=BRA
RATE_LIMITER_RATE=2
RATE_LIMITER_BURST=5
Server
toggleDownloadMap=false
statusProtocolPort=7171
gameProtocolPort=7172
start_migrate.sh.txt

I'm sorry I took so long to reply/fix. This should be ok now after recent updates.


ManagerClientThread Object Streams could not initialize

Any idea what may be causing the following Java exception when running the TM?
    at server.ServerClientThread.setupConnectionStreams(ServerClientThread.java:76)
   at server.ServerClientThread.run(ServerClientThread.java:44)

java.io.StreamCorruptedException: invalid stream header: 0300002F
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:857)
at java.io.ObjectInputStream.(ObjectInputStream.java:349)
at server.ServerClientThread.setupConnectionStreams(ServerClientThread.java:71)
at server.ServerClientThread.run(ServerClientThread.java:44)

It's turned out that some Ukrainian IP was bruteforcing the protocol (and opening occasional connections to the TM server). The Linux firewall (iptables) has solved the issue.

Thanks for updating! Glad you fixed it
On Feb 26, 2018 3:14 PM, "krasi0"<EMAIL_ADDRESS>wrote:
It's turned out that some Ukrainian IP was bruteforcing the protocol (and
opening occasional connections to the TM server). The Linux firewall
(iptables) has solved the issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/davechurchill/StarcraftAITournamentManager/issues/25#issuecomment-368605259,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABIkqBJDvPgkFMJFHdA5P3AjTrZuSYqrks5tYvujgaJpZM4STc_u
.


Unable to edit a new translation (at least in Elixir)

No "Save", "Publish" or "Run" buttons. Impossible to write or paste into the frames "Solution", etc... Same thing in "Preview".

In fact it seems that happens only (?) in this kata: https://www.codewars.com/kata/565abd876ed46506d600000d/translation/new

Still unable to edit a new Elixir translation:
https://www.codewars.com/kata/565abd876ed46506d600000d/translation/new

It happens in a lot of kata and lots of language.

@g964 I noticed you are starting to create translations again. have your problems gone away or are you still getting them?

Still the same with Elixir. I tried to translate a few kata to Elixir but the fields are all UN-editable. No way to write or paste in them. Sometimes the description itself doesn't appear.

Yeah its odd. All of these work fine for me.
Can you try again and this time open up your web console. Perhaps some errors are reported there which would help me debug.

With:
https://www.codewars.com/kata/56fcc393c5957c666900024d/translation/new
what I got with Google Chrome:
Subscribed to model_update
application-08d1549….js:32 Objectid: "545207bac8e60b30fc000942"updates: Objecthonor: 34126__proto__: Object__defineGetter__: __defineGetter__()__defineSetter__: __defineSetter__()__lookupGetter__: __lookupGetter__()__lookupSetter__: __lookupSetter__()constructor: Object()hasOwnProperty: hasOwnProperty()isPrototypeOf: isPrototypeOf()propertyIsEnumerable: propertyIsEnumerable()toLocaleString: toLocaleString()toString: toString()valueOf: valueOf()get __proto__: __proto__()set __proto__: __proto__()__proto__: Object__defineGetter__: __defineGetter__()__defineSetter__: __defineSetter__()__lookupGetter__: __lookupGetter__()__lookupSetter__: __lookupSetter__()constructor: Object()hasOwnProperty: hasOwnProperty()isPrototypeOf: isPrototypeOf()propertyIsEnumerable: propertyIsEnumerable()toLocaleString: toLocaleString()toString: toString()valueOf: valueOf()get __proto__: __proto__()set __proto__: __proto__()
application-08d1549….js:32 Loading /assets/bundles/code_snippets-2cf0a6c83aed77dfd9414a52178a639c.js
application-08d1549….js:32 Loaded /assets/bundles/code_snippets-2cf0a6c83aed77dfd9414a52178a639c.js
3application-08d1549….js:23 Uncaught TypeError: Cannot read property 'prev' of undefined
VM52 56fcc39…:188 Uncaught TypeError: Cannot read property 'prev' of undefined
application-08d1549….js:23 Uncaught TypeError: Cannot read property 'prev' of undefined

Edit fields are NOT editable.
Hope that helps.

That gives me something to go on, though doing a search there are no properties called prev in the codebase so thats a doozy. I'll keep digging. Thanks.

Same kata:
https://www.codewars.com/kata/56fcc393c5957c666900024d/translation/new
With Edge (still unable to paste or write into my Elixir "Solution") I get:
SCRIPT5007: Unable to get property 'prev' of undefined or null reference
application-08d1549bf5945ff6f83f89cbc1e0ad4a.js (22,32696)

When I can't paste in Google Chrome, in Console "Source" a line is underlined (I only copy a part of it) for : application-08d1549bf5945ff6f83f89cbc1e0ad4a.js
&&t.context.prev&&(t.context=t.context.prev),p==="->"?t.inArrowBlock?t.context=t.context.prev:t.inArrowBlock=!0:t.inArrowBlock&&p==="end"

It could indicate where the error is?

I tried today after re-writing and re-saving my code and it succeeded. The first program file was saved in the ordinary way and I didn't see any weird char in it.  Puzzling but most important it worked! Later I will try with another kata. For the time being I think you can close this issue. Anyway thanks for your great work!


Enable any app (including Docker) to run under ANCM with access to the IIS user identity

ANCM is architected as a generic reverse proxy (owing to its HttpPlatformHandler origins), but a couple of implementation choices limit its full potential to ASP.NET Core apps.
This PR enables a few new options (all opt-in) that enable a wider range of apps to use IIS and ANCM (v2 out-of-process) with access the IIS authenticated user identity.
A more detailed write-up is available at https://github.com/nil4/ANCM-AnyApp/blob/master/ancmv2_extra/Readme.md.
The same repository includes a few demo apps that use the features in this PR; the repo Readme file contains a walk-through of the demo apps.
Background
When IIS is configured to use Windows authentication, ANCM passes the identity of the user to the backend application, as a forwarded request header (MS-ASPNETCORE-WINAUTHTOKEN). The header value is a hex number (e.g. 39E), representing the Windows handle for the user identity.
The backend app reads the user token/handle value on every request, and creates a WindowsIdentity from the handle value, which is used for the duration of the request.
This method of passing the IIS authentication information has a few downsides:

it only works for handles of Windows-authentication users, while IIS supports multiple authentication schemes (see the Remarks section);

it does not work for applications that cannot (or are not willing to) call Win32 APIs to recreate a Windows identity from the handle value; examples include apps running in Docker containers, or cross-platform applications that run on Windows, but are designed to also run on other web servers, e.g. expecting a REMOTE_USER header (like many NodeJS, Java, Ruby or Python apps do.)

PR description
The first commit adds new ANCM settings to allow passing the IIS authenticated user name to the backend application. These settings are complementary to the existing forwardWindowsAuthToken setting, which is enabled by default today, but applicable to only ASP.NET Core apps.
The forwardUserName setting (default value: false), when enabled, instructs ANCM to pass the IIS authenticated user name in a request header to the backend app, regardless of the IIS authentication method. If IIS anonymous authentication is used, an empty value will be forwarded. When this option is enabled, forwardWindowsAuthToken should be disabled, as the backend app cannot be expected to close the Windows user handle; this is not currently enforced.
The forwardDomainName setting (default value: true) specifies whether the domain name (if any) of the authenticated IIS user is forwarded to the backend app. When set to true, the forwarded user name is MyDomain\MyUserName; when false, only MyUserName will be sent.
The forwardUserNameHeader setting instructs ANCM which header to use when forwarding the IIS user name to the backend app. The default value, MS-ASPNETCORE-USER, is used for consistency with other forwarded headers, and to ensure the value cannot be tampered by a malicious user (see security considerations). It can be set to another value (e.g. REMOTE_USER) if the implications are well-understood.
The second commit adds one setting (disableProcessIdCheck, default value: false) specifically for backend applications running in Docker containers.
ANCM v2 currently expects the process it launches (or one of its child processes) to own the listening port configured by the ASPNETCORE_PORT environment variable. That does not match what Docker does: the user-mode docker.exe program triggers the container launch, but the Docker system/daemon service (com.docker.service) actually hosts the running container and the ports it listens to.
Since there is no parent-child relationship between the two Docker processes in this case, ANCM times-out trying to match the port to the docker.exe process it launched. The disableProcessIdCheck setting makes the ANCM test less strict: it still verifies that some process listens on the expected port, but it no longer requires that process to be directly related to the one it starts.
The third commit re-enables replacing %ASPNETCORE_PORT% placeholders in the ANCM process arguments. This feature used to be available in earlier ANCM versions, but regressed during a refactoring.
This restores feature parity with HttpPlatformHandler, which is documented to performs a similar replacement:

%HTTP_PLATFORM_PORT% is a special placeholder that must be specified as part of the arguments attribute or the httpPlatformEnvironmentVariables list.
HttpPlatformHandler dynamically replaces this variable with a port so that the HTTP listener can listen on this port.

Alternatives
IIS Application Request Routing and HttpPlatformHandler enable a variety of web applications to be hosted under IIS on Windows.
However there is still no native IIS solution for providing the proxied application with the identity of the IIS user, despite clear user demand (1, 2, 3, 4, 5, 6, 7).
HttpPlaformHandler, in particular, would arguably be a better fit for the options added in this PR. But it is not open source; and while support for the forwardWindowsAuthToken setting was added in v1.2 for DNX, requests to enable REMOTE_USER header remain unanswered to this day.
Final remarks
With version 2.2, ANCM will gain a fantastic new capability: running ASP.NET Core apps in-process. This ensures ASP.NET Core apps will have an edge over anything else running on Windows/IIS in terms of performance.
To quote @shanselman from his blog post a few years back:

Why is HttpPlatformHandler interesting? Check this from the docs...it means IIS can host anything that runs on Windows now, easily. These things were possible before, but with all kinds of hacks and FastCGI this and that. What's great about HttpPlatformHandler is that it isn't about Rails. It's about any process that's listening on a port. You get all the value of IIS and total control of your self-hosting scenario.

The same is true of ANCM today. And with this PR, it would enable any out-of-process app (regardless of underlying technology) to really leverage the full value of IIS, including access to authenticated user information.
Another example would be an application running in a Windows Docker container. Such an app can be configured to run under a Group Managed Service Account identity, enabling it to use integrated Windows authentication against SQL Server and other networked services and resources.
However, to my knowledge, there is currently no integrated auth solution for the users accessing this application. If the containerized application were proxied by IIS, then integrated authentication can be used, and ANCM could forward the IIS user name to the app.
What do you think?

Added a third commit that re-enables replacing %ASPNETCORE_PORT% placeholder in the ANCM process arguments.
This restores feature parity with HttpPlatformHandler, which performs a similar replacement:

%HTTP_PLATFORM_PORT% is a special placeholder that must be specified as part of the arguments attribute or the httpPlatformEnvironmentVariables list.
HttpPlatformHandler dynamically replaces this variable with a port so that the HTTP listener can listen on this port.

The argument replacement used to be available in earlier ANCM versions, but apparently
regressed during a refactoring.
Hopefully fixes aspnet/AspNetCoreModule#117 and SuaveIO/Suave.IIS#6

@Tratcher I presume that is because HttpSys can already do many of the same things that ANCM is used for: URL reservation, HTTPS certificate binding, Windows authentication etc. Other than easier administration, I'm not sure ANCM brings much value to that scenario.
The use cases I see are centered around hosting non-native Windows apps (and lately, Dockerized apps) under IIS. Intranet users expect integrated authentication everywhere, and there are no good solutions today for those use cases.
I hope this PR improves things a bit at least in that direction. And I'm glad if it helps with other scenarios I haven't thought of 👍. It goes both ways:

/cc @guardrex

Rebased on top of the latest release/2.2 changes (and for once all builds succeeded).

@nil4 We appreciate the contribution but we are unable to accept this PR at this moment. This stems from the fact that we don't have enough hands on deck to deal with the long tail of issues from folks attempting to use this in a myriad of ways. The biggest burden here would be ensuring compatibility as we presently only test with ASP.NET Core.

ANCM is architected as a generic reverse proxy (owing to its HttpPlatformHandler origins), but a couple of implementation choices limit its full potential to ASP.NET Core apps.

This is intentional decision to not build a generic reverse proxy, but limit ourselves to just ASP.NET Core workloads.
That being said, we'd happy to help in whatever limited capacity we have to answer any questions you have that may arise from your fork.


Matrix.hackage.haskell.org badges

ping @hvr
Note: backjump limit doesn't have a space on screenshots,  but that's fixed in the code.

Hi, thanks for this contribution. It would be great to get this merged. I'm sorry for the long delay. We're working through a large backlog of PRs.
Would you be willing to clean up the diff a bit and add tests?
index.html has been removed from master, so you can just remove that when you merge master into your branch.

If anyone would like to adopt this PR, please feel free to do so: grab the branch, add more commits addressing the comments, and open a new PR referencing this one.


64-bit required to run mogno (see the desc)

<IP_ADDRESS> - - [15/May/2015 15:49:38] "POST /v10/ping/ HTTP/1.1" 500 -
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1836, in call
return self.wsgi_app(environ, start_response)
File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1820, in wsgi_app
response = self.make_response(self.handle_exception(e))
File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1403, in handle_exception
reraise(exc_type, exc_value, tb)
File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1817, in wsgi_app
response = self.full_dispatch_request()
File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1477, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1381, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1475, in full_dispatch_request
rv = self.dispatch_request()
File "/usr/local/lib/python2.7/dist-packages/flask/app.py", line 1461, in dispatch_request
return self.view_functionsrule.endpoint
File "/home/cloudly/cloudly/api.py", line 161, in ping
networking_.insert( networking_metrics )
File "/usr/local/lib/python2.7/dist-packages/pymongo/collection.py", line 1908, in insert
check_keys, manipulate, write_concern)
File "/usr/local/lib/python2.7/dist-packages/pymongo/collection.py", line 436, in _insert
self.codec_options, sock_info)
File "/usr/local/lib/python2.7/dist-packages/pymongo/pool.py", line 237, in legacy_write
return helpers._check_gle_response(response)
File "/usr/local/lib/python2.7/dist-packages/pymongo/helpers.py", line 228, in _check_gle_response
raise OperationFailure(details["err"], code, result)
OperationFailure: can't map file memory - mongo requires 64 bit build for larger datasets
^C^CError in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "/usr/local/lib/python2.7/dist-packages/pymongo/periodic_executor.py", line 139, in _shutdown_executors
executor.join(10)
File "/usr/local/lib/python2.7/dist-packages/pymongo/periodic_executor.py", line 80, in join
self._thread.join(timeout)
File "/usr/lib/python2.7/threading.py", line 679, in join
self.__block.wait(delay)
File "/usr/lib/python2.7/threading.py", line 263, in wait
_sleep(delay)
KeyboardInterrupt
Error in sys.exitfunc:
Traceback (most recent call last):
File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "/usr/local/lib/python2.7/dist-packages/pymongo/periodic_executor.py", line 139, in _shutdown_executors
executor.join(10)
File "/usr/local/lib/python2.7/dist-packages/pymongo/periodic_executor.py", line 80, in join
self._thread.join(timeout)
File "/usr/lib/python2.7/threading.py", line 679, in join
self.__block.wait(delay)
File "/usr/lib/python2.7/threading.py", line 263, in wait
_sleep(delay)
KeyboardInterrupt

oops .. wrong cp&paste but for real, you need 64 bit to store larger collection of data on mongo. full stop.

acknowledged :+1:


Open source Vespa Docker image no longer built by Docker Hub

Docker Hub stopped recently stopped automatic building of Docker images for the free plan (https://www.docker.com/blog/changes-to-docker-hub-autobuilds/). Our open-source Vespa Docker image is no longer built and distributed. We need to either apply for the Docker Open Source program or build the image somewhere else (e.g Screwdriver).

@johans1 Is there a plan to upload Vespa docker image to other public registries such as Amazon ECR public gallery or Github container registry? There is an issue with hitting DockerHub rate limits, while the mentioned two don't have this problem.

@olgaakrekhovetska I will look into these alternatives.

@olgaakrekhovetska We are now publishing the Vespa container image to GitHub Container registry as well:
$ docker pull ghcr.io/vespa-engine/vespa:latest

Documented in https://docs.vespa.ai/en/build-install-vespa.html .

Nice! Thanks a lot @aressem!

Thank you @aressem for the quick turnaround!


Update README

More example usage
Installation

This change is

Where should we publish the documentation?
@peter50216 @david942j

http://www.rubydoc.info/github/peter50216/pwntools-ruby/master/frames ?

What happened to the url of documentation  ...?

Suggestion:
Add check list of supported features in readme
Ex.
Architectures:

[X] i386
[X] amd64
[ ] arm

Modules:

[X] asm
[X] disasm
[X] shellcraft

Review status: 0 of 1 files reviewed at latest revision, 6 unresolved discussions.

README.md, line 34 at r1 (raw file):
Previously, david942j wrote…
Change example to a real challenge
The easiest problem on pwnable.kr or pwnable.tw

Done.

README.md, line 70 at r2 (raw file):
Previously, peter50216 (Peter Shih) wrote…
"can" and "be able to" are duplicated.

Done.

README.md, line 28 at r5 (raw file):
Previously, david942j wrote…
set context.arch = 'i386'

Done.

README.md, line 19 at r6 (raw file):
Previously, david942j wrote…
change pwnable.tw to pwnable.tw

Done.

README.md, line 93 at r6 (raw file):
Previously, david942j wrote…
I think list arm and thumb in unchecked items is enough

Done.

README.md, line 108 at r6 (raw file):
Previously, david942j wrote…

[x] context
[x] asm
[x] disasm
[x] shellcraft
[x] elf
[x] dynelf
[x] logger
[ ] tube

[x] sock
[ ] process

[ ] fmtstr
[x] util

[x] pack
[x] cyclic
[x] fiddling

Done.

Comments from Reviewable

LGTM

Reviewed 1 of 1 files at r7.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

LGTM


Add features from skiers keystrokes

Have an option to display sneaking, fps, ping, add custom keys, etc. Mostly the option display sneaking would be nice.

Firstly, it's not likely that I will add displays for fps and ping as I don't feel like these things are something that belongs in this mod, you could use something like MiniHUD instead.
As for the custom keys that is currently in the works, this would also mean you can select sneaking. I'm hesitant to add sneaking as a default because it's already quite visible in-game and many users will probably want it off.
You can follow #12 for progress on this feature.


token creation error (login)

got a error when launched login in hearthstone folder
libsoup-ERROR **: 04:10:15.215: libsoup3 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.
pacman -Q | grep libsoup outputs: libsoup 2.74.3-1 libsoup3 3.6.1-1
i tried to delete one of the libsoup libraries, but it's impossible since webkit2gtk can't work with only libsoup2 or with only libsoup3 (i tested it)
i tried to reinstall all dependencies, also did pacman -Syu
i tried to compile login.c with libsoup2, got only a black screen
i'm using Arch Linux with KDE Plasma

just now i found a workaround
cd into hearthstone-linux/token/, build an exe with make, you'll get an Token.exe in this dir
now install mono sudo pacman -S mono
open your browser, authorize in battle net, then open dev console in a new tab, select network and go to https://eu.battle.net/login/en/?app=wtcg, in request headers find cookie and find gs-hs= (first row), copy your token after equals sign until ;
then again cd into hearthstone-linux/token/ and execute token encryption mono Token.exe <YOUR-TOKEN>, it'll create a token file
finally, move token file from hearthstone-linux/token/ to hearthstone-linux/hearthstone/

I'm not really sure what works wrong with libsoup2 and libsoup3, it still works fine on Ubuntu 24.04. as before and I dont know what changed elsewhere.
You can use the token tool instead as @waterfox22 suggested, this was actually the method to store the token before the login tool was contributed.


Test discovery crashes if some test files try to import unavailable packages

If some test files import packages that are not available on the developer's machine, an import error results that crashes the entire test discovery.
This is not a niche issue! Many projects that support different host environment configurations have test specific for each of their targets.
Example: projects that can accelerate computations on GPU if available but fall back to CPU.
Environment data

VS Code version: 1.42.0
Extension version (available under the Extensions sidebar): 2020.3.62207-dev
OS and version: Windows 10
Python version (& distribution if applicable, e.g. Anaconda): 3.8.1
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Relevant/affected Python packages and their versions: pytest
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): Jedi
Value of the python.languageServer setting: Microsoft

Expected behaviour
Discover tests.
Actual behaviour
Test discovery crashes. No tests discovered in GUI.
Steps to reproduce:

clone numba

run test discovery

Logs
Python test log output after running test discovery with pytest:
<... snipped ...>
________________ ERROR collecting numba/tests/test_runtests.py ________________
ImportError while importing test module 'C:\Users\My User\Documents\numba\numba\tests\test_runtests.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
numba\tests\test_runtests.py:4: in <module>
    from numba import cuda
numba\cuda\__init__.py:7: in <module>
    from .device_init import *
numba\cuda\device_init.py:14: in <module>
    from .decorators import jit, autojit, declare_device
numba\cuda\decorators.py:3: in <module>
    from .compiler import (compile_kernel, compile_device, declare_device_function,
numba\cuda\compiler.py:16: in <module>
    from .cudadrv.devices import get_context
numba\cuda\cudadrv\devices.py:17: in <module>
    from .driver import driver
numba\cuda\cudadrv\driver.py:30: in <module>
    from numba import mviewbuf
E   ImportError: cannot import name 'mviewbuf' from 'numba' (C:\Users\My User\Documents\numba\numba\__init__.py)
!!!!!!!!!!!!!!!!!! Interrupted: 113 errors during collection !!!!!!!!!!!!!!!!!!
============================ 113 errors in 32.63s =============================

Traceback (most recent call last):
  File "c:\Users\My User\.vscode\extensions\ms-python.python-2020.3.62207-dev\pythonFiles\testing_tools\run_adapter.py", line 15, in <module>
    main(tool, cmd, subargs, toolargs)
  File "c:\Users\My User\.vscode\extensions\ms-python.python-2020.3.62207-dev\pythonFiles\testing_tools\adapter\__main__.py", line 87, in main
    parents, result = run(toolargs, **subargs)
  File "c:\Users\My User\.vscode\extensions\ms-python.python-2020.3.62207-dev\pythonFiles\testing_tools\adapter\pytest\_discovery.py", line 39, in discover
    raise Exception("pytest discovery failed (exit code {})".format(ec))
Exception: pytest discovery failed (exit code 2)

Indeed this fails as well. Going to speak to the project directly. Thanks for the help.


Push in afterSave Function return success But never send out !

Well I am back again with same issue i had 3 days ago  !
i tried both syntax for push notification ,The function Keep return success , But server never send the push notification ! I am on Parse -server 2.1.16

my verbose have no POST /parse/push pops up  , So can we this time digging little bit more before we blame on the type of syntax or style we writing ??? Please

Ites funny that if i  set time out , some times it may work

Solved ,  ITs my local test machine

@lifeisfunny please close the issue if it's solved


Replacing kernel in with FBK: ucp on i.MX 8MQ

Hi,
I try to update kernel in i.MX 8MQ based SoC with UUU. But when I try to do that, I cannot copy the image at the specified location.

See UUU error log

U-Boot SPL 2020.04-5.4.24-2.1.0+g3e4708a941 (Jan 29 2021 - 05:35:14 +0000)
PMIC:  PFUZE100 ID=0x10
DDRINFO: start DRAM init
DDRINFO: DRAM rate 3200MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Loading 4GB Config
Normal Boot
Trying to boot from USB SDP
SDP: initialize...
SDP: handle requests...
Downloading file of size 923824 to 0x40400000... done
Jumping to header at 0x40400000
Header Tag is not an IMX image
Found header at 0x40407da0
hab fuse not enabled

Authenticate image from DDR location 0x401fcdc0...

U-Boot 2020.04-5.4.24-2.1.0+g3e4708a941 (Jan 29 2021 - 05:35:14 +0000)

CPU:   i.MX8MQ rev2.1 1300 MHz (running at 800 MHz)
CPU:   Industrial temperature grade (-40C to 105C) at 30C
Reset cause: POR
Model: WINSYSTEMS i.MX8MQ ITX-P-C444
DRAM:  4 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment

[*]-Video Link 0imx8m_hdmi_probe
cdn_api_checkalive: keep-alive counter did not increment for 10us...
HDMI enable failed, ret -1!
 (1280 x 720)
	[0] display-controller@32e00000, video
	[1] hdmi@32c00000, display
In:    serial
Out:   serial
Err:   serial

 BuildInfo:
  - ATF b0a00f2
  - U-Boot 2020.04-5.4.24-2.1.0+g3e4708a941

switch to partitions #0, OK
mmc0(part 0) is current device
Detect USB boot. Will enter fastboot mode!
Net:   Could not get PHY for FEC0: addr 0
Could not get PHY for FEC0: addr 0
No ethernet found.

Fastboot: Normal
Boot from USB for mfgtools
*** Warning - Use default environment for 				 mfgtools
, using default environment

Run bootcmd_mfg: run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else booti ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fas
tboot ..."; fastboot 0; fi;
Hit any key to stop autoboot:  0

## Checking Image at 43800000 ...
Unknown image format!
Run fastboot ...
Detect USB boot. Will enter fastboot mode!
flash target is MMC:0
request 00000000fe130200 was not queued to ep1in-bulk
Detect USB boot. Will enter fastboot mode!
request 00000000fe130200 was not queued to ep1in-bulk
switch to partitions #0, OK
mmc0(part 0) is current device
Detect USB boot. Will enter fastboot mode!
request 00000000fe130200 was not queued to ep1in-bulk

I tried adding CONFIG_USB_F_FS=y following this issue: https://github.com/NXPmicro/mfgtools/issues/42#issuecomment-408021687. Yet it's not working as expected.
The script I used is given as follows,
uuu_version 1.2.39

SDP: boot -f >/signed_flash.bin

SDPS: boot -f >/signed_flash.bin

SDPV: delay 1000
SDPV: write -f >/signed_flash.bin -skipspl
SDPV: jump

FB: ucmd setenv fastboot_dev mmc
FB: ucmd setenv mmcdev 0
FB: ucmd mmc dev 0

FBK: ucp t:/boot/Image file.txt

FB: Done

You need download linux kernel image and initramfs before using FBK.
our release package have example_kernel_emmc.uuu.
https://github.com/NXPmicro/mfgtools/wiki/Sample-script
section:
Burn yocto image to eMMC by linux kernel

Thanks @nxpfrankli
Do you have any idea on generating .initramfs file in Yocto?

I have not built it by myself.
looking for our bsp yocto document.
try bitbake core-image-minimal-initramfs


Misattribution of import errors

A failure to import IPython and matplotlib is falsely attributed to a a failure to import ipywidgets. Matplotlib is not a requirement for fastprogress and so this is an easy error to cause but requires source-code delving to debug.
https://github.com/fastai/fastprogress/blob/e7d108f5906ed9ab8d90502ec8b6d0253bd0e3db/fastprogress/fastprogress.py#L97-L103

Just ran into this as well. In my case I was missing matplotlib. A simple fix would be to reword the error message. Nicer would be to enable as much functionality as possible without matplotlib if it doesn't exist. Not sure how much work that would need though.


refactor(@embarkjs/web3): make web3 connector an internal plugin like the other embarkjs-* packages

Effectively deprecate the embarkjs-connector-web3 package but don't introduce a breaking change by simply not loading the plugin if it's specified in a DApp's embark.json. If the deprecated plugin is specified, display a message indicating the plugin was ignored and suggesting it be removed from the project's embark.json and package.json.

There is a race condition involving embarkArtifacts code and symlink generation. This PR is not the cause of the race but it does seem to increase the frequency of the race causing errors to be displayed starting/during embark run.
A way I've found to reproduce it is, in a DApp:

embark blockchain
embark run --nobrowser ... quit and repeat if you don't see red before the dashboard takes over the screen

We need to find a way to allow code and symlink generation to be completed before any service attempts to make use of the artifacts directly or indirectly. However, I believe solving this problem is beyond the scope of this PR, which accomplishes what was intended: making the web3 connector an internal plugin similar to embarkjs-ipfs, embarkjs-whisper, etc.

Docs will need to be updated re: embarkjs-connector-web3 no longer being necessary and the recommendation to remove it if it's already part of a DApp. @PascalPrecht thoughts on a best approach?

Few thoughts on this:

Just to refresh my mind... we're doing this because... some embarkjs-* packages are now required to be listed as dependencies explicitly, which is a breaking change because previously users only needed to list embarkjs-connector-web3, correct? However, they also only need to be listed explicitly when embark itself isn't a local dependency of the application, right? And since we want users to install embark as a local dependency, it'd be more consistent if embarkjs-connector-web3 would also not be needed to be listed. I hope I'm making sense and getting the motivation here right.

Given the information above, and assuming that's the reason we're doing this, I'd wonder, why are we deprecating embarkjs-connector-web3 ? I see you're introducing a new embark-web3 and embarkjs-web3 package, but couldn't we still use embarkjs-connector-web3 ?

In the long term, we actually do want to have people list all of their embarkjs dependencies explicitly, so given that, it's a little bit of a step backwards, but I see that this is primarily to not introduce a breaking change and really only a temporary thing. With that in mind, I wouldn't actually bother changing the docs. People that still have the embarkjs-connector-web3 installed will be fine. Maybe we don't even show a warning and have them not actually know that we're ignoring the package (for the time being). But again, here I'd also like to know what embarkjs-web3 over embarkjs-connector-web3

Hope this makes sense.

@PascalPrecht

Just to refresh my mind... we're doing this because... some embarkjs-* packages are now required to be listed as dependencies explicitly, which is a breaking change because previously users only needed to list embarkjs-connector-web3, correct?

Not quite.  I'll give my understanding of how we got here; @jrainville may offer some additional perspective and he can let me know if I'm wrong on some points.
embarkArtifacts was/is our first step at turning .embark/ inside out so that generated code can be used with any front-end framework, while remaining compatible with our legacy pipeline. Also, at least for now, embarkArtifacts needs to work whether the embark package is installed globally or locally.
While @jrainville was working on the embarkArtifacts implementation he discovered that the generated code could have problems resolving packages it relied upon; this was especially a problem when using global embark and loading the artifacts in CRA as opposed to the legacy pipeline.  The solution was in two parts:

Some modules needed to be symlinked from embarkArtifacts/modules/ to the corresponding package in the embark package's own node_modules, wherever that happens to be. Then, in the generated code, the module is resolved via symlink instead of the bare package name, e.g. require('./modules/web3') vs. require('web3').

It seemed code for generating web3 connector code (which was the first code-gen module to be split out in the monorepo) needed to live in a plugin installed in a dapp instead of being part of embark.  I believe part of the difficulty was that when embarkjs-connector-web3 was created we hadn't sorted out a number of the difficult monorepo puzzles (e.g. dappPath, embarkPath) that eventually got solved in embark-core, embark-utils, etc.

So that's how we got embarkjs-connector-web3.  More recently, when embark[js]-* (ens, ipfs, etc.) were being worked on, we started having module resolution problems again. In #1632, which aimed to solve a related but different problem, @andremedeiros and I found a way to avoid needing those packages to become dapp plugins, i.e. they could remain internal plugins.  When implementing those changes, I realized we could do the same thing with embarkjs-connector-web3, eliminating the need to have it be a dapp plugin.
Is there additional motivation, i.e. besides it being possible to make this change?
Yes, I'll give the various reasons I thought of; feel free to explain if/how you think the reasoning is flawed.

embarkjs-connector-web3 is an oddball, born of temporary necessity, as explained above. There are not presently any technical advantages to having it be a dapp plugin, and it's one more thing dapp developers have to keep up with (or add in the first place), e.g. making sure they have the correct version when we bump embark from pre-release to release (or vice versa), given how caret ranges work.

embarkjs-connector-web3 makes dapp installations (e.g. embark demo) much "heavier" because the connector depends on embark-utils, which in turn has a lot of dependencies, making template instantiation take noticeably longer. Given that we can avoid this situation and that there are no advantages to having the additional local dependencies, for the remaining 4.x series it makes sense to have all the embarkjs-* packages work the same way as internal plugins.

And since we want users to install embark as a local dependency, it'd be more consistent if embarkjs-connector-web3 would also not be needed to be listed.

Correct, with the 5.x series we'll (hopefully) move to a setup where the bulk of embark is installed locally in a dapp. I think it will still be possible to (optionally) globally install embark, but I think we can reduce that package to a very, very thin one that knows how to connect the command-line to the various embark packages inside the dapp's node_modules.

Given the information above, and assuming that's the reason we're doing this, I'd wonder, why are we deprecating embarkjs-connector-web3? I see you're introducing a new embark-web3 and embarkjs-web3 package, but couldn't we still use embarkjs-connector-web3?

There are a few aspects to consider.
For each of ens, swarm, ipfs, whisper, there are embark- and embarkjs- packages. The embark- ones are responsible for code-gen, and the embarkjs- ones contain the code that hooks up to the gen'd code.  I went with -web3 for the name of the refactored connector, but also considered -ethereum.  I think -web3 is the correct choice because the code those packages contain is so web3-specific.
The reason for ignoring embarkjs-connector-web3 is that we don't want to double-generate the connector code. We also need to be able to distinguish the dapp plugin from the internal packages that are replacing it. It would be possible to do that by checking a version number in package.json, but the other embark[js]-* packages come in pairs and it seemed cleaner to create two new packages and effectively deprecate the old one.

In the long term, we actually do want to have people list all of their embarkjs dependencies explicitly, so given that, it's a little bit of a step backwards...

I think it's more of a step sideways. Without intending to criticize the hard work that went into embarkjs-connector-web3, I firmly believe the setup we have now with artifacts generation and the EmbarkJS codebase needs to be completely rethought. It's bug prone and has horrendously complex control flow. Moreover, as explained above, the web3 connector became a dapp plugin more because of technical difficulties than it being the beginnings of a shift toward favoring local installs.
While it does seem we'll be moving to a local-install and peer dependency model in the near future (based on team discussions) — and I'm really enthusiastic about that! — I hope and expect that the embarkjs-* / EmbarkJS setup we have now will likewise get overhauled (and possibly renamed). For that reason, I don't think it makes sense to preserve embarkjs-connector-web3, i.e. I don't expect it to make a reappearance in dapps; rather, a different set of packages would serve a somewhat related role but work quite differently.

Thank you @michaelsbradleyjr for writing down your thoughts here, this has been very helpful in understanding the reasoning again 👏

It seemed code for generating web3 connector code (which was the first code-gen module to be split out in the monorepo) needed to live in a plugin installed in a dapp instead of being a dep of embark. I believe part of the difficulty was that when embarkjs-connector-web3 was created we hadn't sorted out a number of the tricky monorepo puzzles that eventually got solved in embark-core, embark-utils, etc

I believe the reason it couldn't be a dep of embark was because the original issue of not being able to resolve certain modules occured when embark was used globally. In order to get the connector functionality squeezed between DApp and Embark ( considering it's installed/used globally ) a plugin seems the only possible way...

Given that we can avoid this situation and that there are presently no advantages to having the additional local dapp dependencies, for the remaining 4.x series it makes sense to have all the embarkjs-* packages work the same way as internal plugins.

Yes this makes sense.

I think it's more of a step sideways. Without intending to criticize the hard work that went into embarkjs-connector-web3, I firmly believe the setup we have now with artifacts generation and the EmbarkJS codebase needs to be completely rethought. It's bug prone and has horrendously complex control flow. Moreover, as explained above, the web3 connector became a dapp plugin more because of technical difficulties than it being the beginnings of a shift toward promoting local installs.

So just to clarify: The overall idea is indeed that, you'd go ahead and installed EmbarkJS and you'd also install all other extensions you'd be interested in, one of them being a blockchain connector, because EmbarkJS tries to not be tied to any of them.
In other words, blockchain-connector-web3 is the default connector that EmbarkJS comes with and there's probably going to be blockchain-connector-ethersjs etc in the future. If you're primarily referring to the fact that this thing is a plugin then I guess I agree here. But it'll still be a package once we managed to come up with an EmbarkJS that is entirely decoupled from embark.

For that reason, I don't think it makes sense to preserve embarkjs-connector-web3, i.e. I don't expect that package specifically to make a reappearance in dapps; rather, a different set of packages would serve somewhat related roles but work quite differently.

As long as we're in 4.x where we've introduce the connector package, we'll have to keep it. Deprecating is fine. The package will make a reappearance in DApps just not as a plugin for embark, but an extension for embarkjs, so in that sense, yes, it'll be a different package with related roles (just want to make sure we're on the same side here)

@PascalPrecht thanks for the great follow-up.

So just to clarify: The overall idea is indeed that, you'd go ahead and installed EmbarkJS and you'd also install all other extensions you'd be interested in, one of them being a blockchain connector, because EmbarkJS tries to not be tied to any of them... As long as we're in 4.x where we've introduce the connector package, we'll have to keep it. Deprecating is fine.

I'll try to clarify a few things that I have in mind.
On the practical side of things:
I don't think we should officially deprecate embarkjs-connector-web3, i.e. with npm deprecate because users with globally-installed embark >=4.0.0 <4.1.0 || >=4.1.0-beta.0 <=4.1.0.beta.3 need to have it installed in their dapps node_modules and spec'd in embark.json.
On the other hand I think we can effectively deprecated it as of embark >=4.1.0 || >=4.1.0-beta.4 with the deprecation-list and warning I came up with in this PR and intent to no longer maintain it going forward.
On the speculative side of things:
I do think we'll need a suite of EmbarkJS connectors / extensions. I think embark init with prompts or defaults (init -y) will be the principal mechanism by which dapp authors will get setup w/ the corrector connectors, i.e. init can install them on their behalf and can also take care of installing variou peer dependencies of embark- packages installed in the dapp.

The package will make a reappearance in DApps just not as a plugin for embark, but an extension for embarkjs, so in that sense, yes, it'll be a different package with related roles (just want to make sure we're on the same side here)

Always on the same side 😄 just slightly different ways of seeing and expressing all this stuff. And yes, embarkjs extensions (w/ embarkjs renamed to something cool, I hope) will definitely make a reappearance in dapps as they'll play a critical role in gluing embark and our dapp-config system to an individual dapp and its choices of decentralized technologies.

Closing in favor of #1680.


html_style works locally but not on ReadTheDocs

I use readthedocs theme both locally and on ReadTheDocs. However, html_style has no effect when docs are compiled on the service.
By the way, I am just trying to add some custom CSS. Here is my conf.py - https://github.com/Suor/funcy/blob/master/docs/conf.py

I'm running into the same situation here.

We are now displaying the actually used conf.py in the build process. You can have a look and see in which cases we override the html_style configuration. You can override the value properly when setting html_theme = "sphinx_rtd_theme".

doesnt make any difference to me. html_style is still being ignored.

There is a pattern for this in our docs now:
http://docs.readthedocs.io/en/latest/guides/adding-custom-css.html
Closing this here as I don't think we'll change this


implement "manifest_runner" dialect

"manifest_runner" dialect is an incremental version of "manifest" that supports custom runners on top of built-in runner types.
closes #2
closes #5

TODO:

[ ] Remove tasks.script, instead, properly support dictionary and list version of task.args:

# dict version
runners:
  julia:
    runner: shell
    run:
      command: julia --project=${{ tasks.args.project_dir }} ${{ tasks.args.script }}

tasks:
  - name: "julia"
    id: julia
    runner: julia
    args:
      project_dir: examples
      script: main.jl

# list version
runners:
  julia:
    runner: shell
    run:
      command: julia --project=${{ tasks.args[1] }} ${{ tasks.args[2] }}

tasks:
  - name: "julia"
    id: julia
    runner: julia
    args:
      - examples
      - main.jl


Relax the restrictions on rubocop to allow for upgrading to > rubocop…

… 1.0.
So this is quite gross, but the tests pass.  I think we need to decide if the tests are worth keeping though.

For reference: https://github.com/prontolabs/pronto-rubocop/pull/56#issuecomment-770462395

I think #60 is much closer to merging as tests pass on that PR, and I also fixed compatibility with older RuboCop versions on master which was discovered there.

I'm planning to merge the other PR and cut a release this weekend. Thanks for the contribution anyway 🎉

@ashkulz Not a problem.  I'm glad to see this kept moving in #60. 😄

pronto-rubocop 0.11.1 has been released, which supports RuboCop >= 1.0 🎉


Improve error/debug info for custom CsvBulkLoader

Affected Version
4.2.3
Description
I am building a custom CsvBulkLoader and it's been quite hard to debug the message "Nothing to import". Found someone with a similar issue on the forum but he never got an answer.
I have not yet been able to fix it, but have at least found what I believe is the issue. I noticed that when I pass $preview=true to processAll, then it DOES work ("84 entries imported" it says), but when I leave it as default (i.e. to actually execute the import) it says "Nothing to import".
The issue is in CsvBulkLoader::processRecord around line 367 when it actually tries to write the record:
        // write record
        if (!$preview) {
            $obj->write();
        }

I guess it fails, because the method does not manage to go beyond that point. If I place debug calls after it, it never gets called.
I'm assuming the problem is that it is a complicated Object. Just like the issue on the forum, I too am trying to import a PageType. Which fails. I was hoping it would just automatically handle whatever is required to save a SiteTree item, but I guess I'll have to write a custom processRecord to make that happen?
Anyway, the main reason for creating this issue is that we really should get something more descriptive than "Nothing to import" when the issue is actually is that the write method failed to return.

My particular issue was that the Page could not be saved because it needed a Parent. So I assigned the parent in a method that didn't really have something to do with it (->extractImage in the CsvBulkLoader) because I couldn't figure out where else to put that.
Note that this doesn't solve this issue, but a solution could be as simple as wrapping the write() call in a try/catch showing the Exception, at least when in Dev mode.


jib:build Remaining allocation units less than 0

Description of the issue:
The jib-maven-plugin failed with this error message:
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.google.cloud.tools:jib-maven-plugin:1.0.1:build (default-cli) on project backend: Remaining allocation units less than 0 for 'pull container configuration sha256:0ea51d9f12788eb9ab2fad601aeda6fd2d444fde75b1cfb853994913ed88243d': -1
I use Nexus 3 as a local Docker repository for my images, and as a proxy to Docker Hub.
In front of Nexus, I have a Traefik, which setup itself from Docker labels.
The docker labels of the Nexus repository:

traefik.docker.network=public
traefik.frontend.entryPoints=http,https
traefik.app.port=8081
traefik.app.frontend.rule=Host:nexus.<IP_ADDRESS>.nip.io
traefik.registry_pull.port=5055
traefik.registry_pull.frontend.rule=Host:nexus.<IP_ADDRESS>.nip.io;PathPrefix:/v2;Method: GET
traefik.registry_pull.priority=30
traefik.registry_push_1.port=5050
traefik.registry_push_1.frontend.rule=Host:nexus.<IP_ADDRESS>.nip.io; PathPrefix:/v2
traefik.registry_push_1.priority=20
traefik.registry_push_2.port=5050
traefik.registry_push_2.frontend.rule=Host:nexus.<IP_ADDRESS>.nip.io; PathPrefix:^/(v1|v2)/[^/]+/?[^/]+/blobs/;Method: POST, PUT, PATCH, DELETE, HEAD
traefik.registry_push_2.priority=40

With this configuration, the docker pull nexus.<IP_ADDRESS>.nip.io/alpine:latest and others work as expected, but jib cannot pull docker layers.
If a publish the port 5050, 5055, and configure jib to pull and push from/to these ports, then jib works as expected.
Environment:
Build from Jenkins Pipeline with Docker Maven container (maven:3-jdk-11-slim)
jib-maven-plugin Configuration (relevant section):
<plugin>
	<groupId>com.google.cloud.tools</groupId>
	<artifactId>jib-maven-plugin</artifactId>
	<version>1.0.1</version>
	<configuration>
		<allowInsecureRegistries>true</allowInsecureRegistries>
		<from>
			<!--suppress UnresolvedMavenProperty -->
			<image>${nexus.location}/adoptopenjdk/openjdk11:alpine</image>
		</from>
		<to>
			<!--suppress UnresolvedMavenProperty -->
			<image>${nexus.location}/mekh/phonebook-backend:${project.version}</image>
		</to>
		<container>
			<ports>
				<port>8080</port>
			</ports>
		</container>
	</configuration>
</plugin>

Additional Information:
The jib-maven-plugin:1.0.0 can use HTTP, but the jib-maven-plugin:1.0.1 works with only HTTPS connection.

Traefik is completely new to us. I'm curious to check a few things.
What if you 1) remove ;Method: GET from registry_pull; and 2) remove traefik.registry_push_2 altogether so that the config looks like this?
traefik.docker.network=public
traefik.frontend.entryPoints=http,https
traefik.app.port=8081
traefik.app.frontend.rule=Host:nexus.<IP_ADDRESS>.nip.io
traefik.registry_pull.port=5055
traefik.registry_pull.frontend.rule=Host:nexus.<IP_ADDRESS>.nip.io;PathPrefix:/v2
traefik.registry_pull.priority=30
traefik.registry_push_1.port=5050
traefik.registry_push_1.frontend.rule=Host:nexus.<IP_ADDRESS>.nip.io; PathPrefix:/v2
traefik.registry_push_1.priority=20

Just trying to by-pass with minimal restrictions. I also think there should be some log on the Traefik side when Jib requests don't go through to reach the Nexus registry?

Another possibility we've been thinking is that traefik is somehow manipulating/ignoring/tampering transferring correct Content-Length header value when routing requests/responses.
Could you obtain a network trace and upload the full log?

(Don't forget to add -DjibSerialize=true to serialize network calls.)

https://github.com/GoogleContainerTools/jib/issues/1512#issuecomment-467954766
I can't delete anything from configuration, because the Nexus can't handle push actions for a group, and Traefik use first match based on priority.
More information about that:
Traefik Configuration for Nexus Docker
Nexus Docker Group (grouping handle pull requests only)
Traefik priority
https://github.com/GoogleContainerTools/jib/issues/1512#issuecomment-468000999
https://github.com/GoogleContainerTools/jib/issues/1512#issuecomment-468001277
I attached the output of the logs (only copied the right step output from Jenkins Pipeline).
I figured out that the JIB throws an exception if I enable Traefik compression.
Without compression, the JIB v1.0.0 can handle the HTTP and HTTPS connection, but v1.0.1 can handle the HTTPS connection only (it only tries at HTTPS)
All test case made with enabled compression:
jib-1.0.0.http.log
jib-1.0.0.https.log
jib-1.0.1.http.log
jib-1.0.1.https.log
Traefik Compression
So, the JIB cannot handle this situtation, but Docker can pull/push with enabled compression, and the JIB v1.0.1 don't connect to HTTP with -DsendCredentialsOverHttp=true property and enabled allowInsecureRegistries configuration.

@mecseid you log did not capture network traces. When effective, the log should capture HTTP all requests/responses as shown in this example trace such as
Feb 26, 2019 10:46:54 AM com.google.api.client.http.HttpRequest execute
CONFIG: -------------- REQUEST  --------------
GET https://myregistry:5000/v2/
Accept:
Accept-Encoding: gzip
User-Agent: jib 1.0.0 Google-HTTP-Java-Client/1.23.0 (gzip)

Feb 26, 2019 10:46:54 AM com.google.api.client.http.HttpRequest execute
CONFIG: curl -v --compressed -H 'Accept: ' -H 'Accept-Encoding: gzip' -H 'User-Agent: jib 1.0.0 Google-HTTP-Java-Client/1.23.0 (gzip)' -- 'https://myregistry:5000/v2/'
Feb 26, 2019 10:46:54 AM com.google.api.client.http.HttpResponse <init>
CONFIG: -------------- RESPONSE --------------
HTTP/1.1 403 Forbidden
Server: squid
Mime-Version: 1.0
Date: Tue, 26 Feb 2019 09:52:45 GMT
Content-Type: text/html;charset=utf-8
Content-Length: 3414
X-Squid-Error: ERR_ACCESS_DENIED 0
X-Cache: MISS from synnefo-proxy
X-Cache-Lookup: NONE from synnefo-proxy:3128
Connection: keep-alive

Please set the network configuration in a logging.properites file and make the system property java.util.logging.config.file to point to the file.
Anyways, now you mentioned that this happens only when turning on Traefik compression, I think it further supports our conjecture that Traefik routing results in dropping or messing with Content-Length in responses, because, understandably, I expect compression to happen on the fly with streaming, and Traefik would have no way to know in advance the exact Content-Length. I'd like to confirm this with a network trace.
And I see jib-1.0.1-https is able to communicate over HTTPS (albeit insecure HTTP). Why do you want to use HTTP for what?

the JIB v1.0.0 can handle the HTTP and HTTPS connection, but v1.0.1 can handle the HTTPS connection only (it only tries at HTTPS)

For this, we've upgrade the Google HTTP Client in v1.0.1, and this seems to be the cause. Filed #1517. This issue will be fixed separately.

Sorry for wrong log files, I created another two:
one with compression (which is failed), and another one without it (which is successful)
jib-1.0.1-with-compression.log
jib-1.0.1-without-compression.log
I don't want to use HTTP connection at all (I was happy about that v1.0.1 don't accept HTTP connections), but we have some very awful policy about ingress network and communication (I hope we will delete these).
Thanks for #1517 .

Thanks for the logs. (In hindsight, Traefik is completely invisible as a proxy, of course.) In any case, it is obvious that Jib crashed on inaccurate/incomplete progress usage, and I think this is a likely cause of the issue. #1521 should fix it, and hopefully, your issue will be gone.

I think we know why compression is causing this issue. This shouldn't be specific to Traefik. The root cause of the inaccurate/incomplete progress usage is probably #1522, which seems tricky to get it right.
Anyways, #1521 will make Jib proceed normally with inaccurate/incomplete progress usage, so I expect #1521 will unblock you.


COVID-19 Mobile app for South Africa.

https://github.com/shaunsaker/covid-19-south-africa-app
Notifies users of the latest confirmed cases and displays the stats (confirmed cases, recoveries, tests and deaths) in a graph view.
Thanks for your list :)

@shaunsaker
Read the contribution guidelines and then add your project under Open Source Projects/Applications and Bots.
Recommendation
Add some screenshot of the app in the repository's readme!

@soroushchehresa Aha, thanks so much, will do.


store-0.7.6 test suite fails to compile

I think it's due to a newer smallcheck than expected.
/Users/dan/scratch/store-0.7.6/test/Data/StoreSpec.hs:96:3: error:
    Duplicate instance declarations:
      instance Monad m => Serial m CBool
        -- Defined at test/Data/StoreSpec.hs:96:3
      instance [safe] Monad m => Serial m CBool
        -- Defined in ‘Test.SmallCheck.Series’
   |
96 | $(do let ns = [ ''CWchar, ''CUShort, ''CULong, ''CULLong, ''CIntMax
   |   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^...

Etc for many similar errors.
I was able to reproduce this locally like so:
stack unpack store-0.7.6 && cd store-0.7.6
edit stack.yaml # add the following stack.yaml
stack build --test --bench --no-run-benchmarks --fast

# stack.yaml
resolver: nightly-2020-08-27
extra-deps:
- store-core-<IP_ADDRESS>@sha256:50b3ef13ab5f82cccf665bd29edf37f69ef1e94c22802c2c94d0f74ce8808f09,1430
- th-utilities-<IP_ADDRESS>@sha256:ba19cd8441aa43dbaed40e9055bb5a7cbd7cf9e154f5253c6bf9293af8b1f96b,1869

Thanks for reporting!  Fixed in store-0.7.7 and removed from expected test failures in https://github.com/commercialhaskell/stackage/pull/5629


ios 13 b4 gg

ios 13 b4 gg

More details ,please!!!

Received an unexpected URL from the web process: 'file:///var/containers/Bundle/Application/E16B2481-92BA-47A4-A43B-BEDBAED1EA36/%E4%BA%91Home.app/Frameworks/AAChartKit.framework/AAChartKitLib.bundle/AAJSFiles.bundle/AAChartView.html'
[Process] 0x14a22b818 - WebPageProxy::Ignoring request to load this main resource because it is outside the sandbox

Hi, I've got the same issue with a different app ("Ignoring request to load this main resource because it is outside the sandbox"). All apps using WkWebView with a local web page appear to be affected.

Hi again, it appears to work with loadFileURL instead of load.

hola, iOS13 b5 can show the chart

but pie chart ui confusion

I'm going to keep watching on iOS13

都给我说中文

Y?

哈哈哈 hahaha ははは 하하하 Ха-ха-ха jajaja

Hola,my project only use UIWebViewkit in your opensource.when I upload my app to the itc,apple show this message for me.
ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs . See https://developer.apple.com/documentation/uikit/uiwebview for more information.


SVT-play http error 400

C:\ffmpeg\Youtube-dl>youtube-dl.exe https://www.svtplay.se/video/21529782/kara-dagbok/kara-dagbok-sasong-1-avsnitt-3-1?start=auto --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://www.svtplay.se/video/21529782/kara-dagbok/kara-dagbok-sasong-1-avsnitt-3-1?start=auto', '--verbose']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2019.03.18
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.17763
[debug] exe versions: ffmpeg 4.0, ffprobe 4.0
[debug] Proxy map: {}
[debug] Using fake IP <IP_ADDRESS> (SE) as X-Forwarded-For.
[SVTPlay] 21529782: Downloading webpage
[SVTPlay] e72J16A: Downloading JSON metadata
ERROR: Unable to download JSON metadata: HTTP Error 400: Bad Request (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpcs52imf5\build\youtube_dl\extractor\common.py", line 626, in _request_webpage
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpcs52imf5\build\youtube_dl\YoutubeDL.py", line 2225, in urlopen
File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default

Also seeing this since a few days. Something must've changed on the site. Back-porting youtube-dl doesn't help.


Error detected while processing /usr/share/vim/vim82/syntax/doxygen.vim

Instructions: Replace the template text and remove irrelevant text (including this line)
Describe the bug
When open cpp file with:
 // vim: syntax=cpp.doxygen

An error occurs:
Error detected while processing /usr/share/vim/vim82/syntax/doxygen.vim:
line  497:
E12: Command not allowed from exrc/vimrc in current dir or tag search:     aug doxygengroup
Error detected while processing function <SNR>4_SynSet:
line   25:
E171: Missing :endif

And when I delete content in /usr/share/vim/vim82/syntax/doxygen.vim:
 " This is still a proposal, but won't do any harm.
 aug doxygengroup
 au!
 au Syntax UserColor_reset nested call s:Doxygen_Hilights_Base()
 au Syntax UserColor_{on,reset,enable} nested call s:Doxygen_Hilights()
 aug END

The problem is resolved.
To Reproduce
Detailed steps to reproduce the behavior:

Run vim --clean test.cpp

Expected behavior
No error occurs.
Screenshots

Environment (please complete the following information):

version:

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Jun 27 2020 11:58:03)
Included patches: 1-1067
Modified by<EMAIL_ADDRESS>Compiled by<EMAIL_ADDRESS>Huge version with GTK2 GUI.

OS: Ubuntu 18.04
Terminal: zsh shell

Additional context

please contact the maintainer of the file.

Only 2 of the default syntax plugins install autocmds: dircolors (which wrongly omits to wrap them in a self-clearing augroup) and doxygen.
You can also reproduce the issue with the dircolors syntax plugin:
vim --clean <(echo '# vim: syntax=dircolors')

In any cause, this is caused by 5958f95a4.  It seems that starting from this commit, :autocmd and :augroup are disallowed.  I guess it's to prevent a malicious script to run arbitrary code...