Error in traction calculation for 2D triangle elements

I was trying solve the simple 2D problem (see diagram) of a bar in pure extension when I encountered a problem with how the tractions are calculated.

The problem can be reproduced with the following script.
from tacs import TACS, elements, constitutive, functions

import numpy as np
from mpi4py import MPI
'''
Mesh used in the demonstration:

    v2                 v3
       + • • • • • • +
       • •           •
       •   •         •
       •     •   f1  •
       •  f0   •     •
       •         •   •
       •           • •
       + • • • • • • +
    v0                 v1

Reference triangle element:

      v2
       +
       • •
       •   • e1
    e2 •     •
       •       •
       + • • • • +
      v0   e0    v1
'''
# Define two connectivities, one in which the right-facing edge of element f1
# maps to a leg of the reference triangle (e0 or e2) and one in which it maps
# to the hypotenuse of the reference triangle (e1). Note: the only difference
# in the connectivities is that the face-vertex list for element f1 is
# cyclically permuted. The relative orientation of the elements is preserved.
# So orientation is not at issue.
conn0 = np.array(
    [
        0, 1, 2,  # f0
        1, 3, 2   # f1
    ],
    dtype=np.intc
)

conn1 = np.array(
    [
        0, 1, 2,  # f0
        2, 1, 3   # f1
    ],
    dtype=np.intc
)

# The traction is applied on element f2. But the index of the face on which it
# is applied changes depending on the connectivity.
trac_face_index0 = 0
trac_face_index1 = 1

# Define function that prints nodal forces given the connectivity and traction
# face index
comm = MPI.COMM_WORLD
def print_nodal_forces(conn, trac_face_index):
    #props = constitutive.MaterialProperties(rho=1.0, E=1.0, nu=0.3, ys=1.0e2)
    props = constitutive.MaterialProperties(rho=2570.0, E=1.0, nu=0.3, ys=350e6)
    stiff = constitutive.PlaneStressConstitutive(props)
    model = elements.LinearElasticity2D(stiff)
    basis = elements.LinearTriangleBasis()
    elem = elements.Element2D(model, basis)

    vars_per_node = model.getVarsPerNode()
    creator = TACS.Creator(comm, vars_per_node)

    num_nodes = 4
    ptr = np.array([0, 3, 6], dtype=np.intc)
    comp_ids = np.zeros(2, dtype=np.intc)
    creator.setGlobalConnectivity(num_nodes, ptr, conn, comp_ids)

    node_coords = np.array(
        [
            0.0, 0.0, 0.0,  # v0
            1.0, 0.0, 0.0,  # v1
            0.0, 1.0, 0.0,  # v2
            1.0, 1.0, 0.0   # v3
        ]
    )
    creator.setNodes(node_coords)

    bcnodes = np.array([0, 2], dtype=np.intc)
    bcptr = np.array([0, 2, 3], dtype=np.intc)
    bcdofs = np.array([0, 1, 0], dtype=np.intc)
    creator.setBoundaryConditions(bcnodes, bcptr, bcdofs)

    element_list = [elem]
    creator.setElements(element_list)
    assembler = creator.createTACS()

    trac_vec = np.array([0.1, 0.0], dtype=np.double)
    aux_elems = TACS.AuxElements()
    traction = elem.createElementTraction(trac_face_index, trac_vec)
    aux_elems.addElement(1, traction)
    assembler.setAuxElements(aux_elems)

    res = assembler.createVec()
    ans = assembler.createVec()
    mat = assembler.createSchurMat()
    alpha = 1.0
    beta = 0.0
    gamma = 0.0
    assembler.zeroVariables()
    assembler.assembleJacobian(alpha, beta, gamma, res, mat)
    res.scale(-1.0)
    print('forces:')
    print(res.getArray().reshape(-1,vars_per_node))
    print()

    node_vec = assembler.createNodeVec()
    assembler.getNodes(node_vec)
    print('nodes:')
    print(node_vec.getArray().reshape(-1,3))
    print()

# Print the nodal forces for the two difference cases (connectivities)
print_nodal_forces(conn0, trac_face_index0)
print_nodal_forces(conn1, trac_face_index1)

The script assumes that the right-hand side has a height of 1 and the distributed load has value 0.1. Thus, the nodal forces on the right-hand side should sum up to a net force of 1 * 0.1 = 0.1. These are the results for the two different (but valid) connectivities defined in the script.
Case 1
------
forces:
[[-0.   -0.  ]
 [ 0.05 -0.  ]
 [-0.   -0.  ]
 [ 0.05 -0.  ]]

nodes:
[[0. 0. 0.]
 [1. 0. 0.]
 [0. 1. 0.]
 [1. 1. 0.]]

Case 2
------
forces:
[[-0.         -0.        ]
 [ 0.07071068 -0.        ]
 [-0.         -0.        ]
 [ 0.07071068 -0.        ]]

nodes:
[[0. 0. 0.]
 [1. 0. 0.]
 [0. 1. 0.]
 [1. 1. 0.]]

In the second case, the net force is larger than 0.1. The forces appear to have been scaled by sqrt(2), the length of the hypotenuse of the reference triangle. The upshot is that, unless the mesh is prepared so that the tractions are only applied to the legs of the reference triangle element, TACS cannot correctly solve the simple problem 2D problem I illustrated above.

More importantly, it looks like something similar happens with tractions and tetrahedral elements. I recreated the analogous problem in 3D. And, again, applying the tractions to the "slanted" face of a reference tetrahedral element (the analogy of the hypotenuse for a reference triangular element) causes some unwanted scaling of the resultant nodal forces.
Here's the script I wrote.
from tacs import TACS, elements, constitutive

import numpy as np
from mpi4py import MPI
# Define two connectivities for a 12-element tetrahedral mesh of a cube. All
# that changes between the connectivities is the cell-to-vertex lists for the
# pair of tetrahedral cells that make up the right face of the cube (where the
# traction is applied). In the second connectivity, the idea (as before) is to
# permute these lists so, for each of these tetrahedral cells, the right-facing
# faces map to the larger face of the reference tetrahedral element (analogous
# to the hypotenuse of the reference triangle).
conn0 = np.array(
    [
        # bottom face
        0, 1, 3, 8,  # c0
        0, 8, 3, 2,  # c1
        # top face
        6, 7, 5, 8,  # c2
        6, 8, 5, 4,  # c3
        # front face
        4, 5, 1, 8,  # c4
        4, 8, 1, 0,  # c5
        # back face
        7, 6, 2, 8,  # c6
        7, 8, 2, 3,  # c7
        # left face
        6, 4, 0, 8,  # c8
        6, 8, 0, 2,  # c9
        # right face
        5, 7, 3, 8,  # c10
        5, 8, 3, 1   # c11
    ],
    dtype=np.intc
)

conn1 = np.array(
    [
        # bottom face
        0, 1, 3, 8,  # c0
        0, 8, 3, 2,  # c1
        # top face
        6, 7, 5, 8,  # c2
        6, 8, 5, 4,  # c3
        # front face
        4, 5, 1, 8,  # c4
        4, 8, 1, 0,  # c5
        # back face
        7, 6, 2, 8,  # c6
        7, 8, 2, 3,  # c7
        # left face
        6, 4, 0, 8,  # c8
        6, 8, 0, 2,  # c9
        # right face
        8, 1, 3, 5,  # c10
        8, 3, 7, 5   # c11
    ],
    dtype=np.intc
)

# The tractions are applied on elements c10 and c11. But the indices of the
# faces on which they are applied changes depending on the connectivity.
trac_face_indices0 = (0, 3)  # in-plane faces
trac_face_indices1 = (2, 2)  # "slanted" faces

# Define function that prints nodal forces given the connectivity and traction
# face index
comm = MPI.COMM_WORLD
def print_nodal_forces(conn, trac_face_indices):
    props = constitutive.MaterialProperties(rho=1.0, E=1.0, nu=0.3, ys=1e2)
    stiff = constitutive.SolidConstitutive(props, t=1.0, tNum=0)
    model = elements.LinearElasticity3D(stiff)
    basis = elements.LinearTetrahedralBasis()
    elem = elements.Element3D(model, basis)

    vars_per_node = model.getVarsPerNode()
    creator = TACS.Creator(comm, vars_per_node)

    num_nodes = 9
    ptr = np.arange(0, 4*(12+1), 4, dtype=np.intc)
    comp_ids = np.zeros(12, dtype=np.intc)
    creator.setGlobalConnectivity(num_nodes, ptr, conn, comp_ids)

    node_coords = np.array(
        [
            0.0, 0.0, 0.0,  # v0
            1.0, 0.0, 0.0,  # v1
            0.0, 1.0, 0.0,  # v2
            1.0, 1.0, 0.0,  # v3
            0.0, 0.0, 1.0,  # v4
            1.0, 0.0, 1.0,  # v5
            0.0, 1.0, 1.0,  # v6
            1.0, 1.0, 1.0,  # v7
            0.5, 0.5, 0.5   # v8
        ]
    )
    creator.setNodes(node_coords)

    bcnodes = np.array([0, 2, 4, 6], dtype=np.intc)
    bcdofs = np.array([0, 1, 2, 0, 1, 2, 0, 1, 0, 1], dtype=np.intc)
    bcptr = np.array([0, 3, 6, 8, 10], dtype=np.intc)
    creator.setBoundaryConditions(bcnodes, bcptr, bcdofs)

    element_list = [elem]
    creator.setElements(element_list)
    assembler = creator.createTACS()

    trac_vec = np.array([0.1, 0.0, 0.0], dtype=np.double)
    aux_elems = TACS.AuxElements()
    traction0 = elem.createElementTraction(trac_face_indices[0], trac_vec)
    traction1 = elem.createElementTraction(trac_face_indices[1], trac_vec)
    aux_elems.addElement(10, traction0)
    aux_elems.addElement(11, traction1)
    assembler.setAuxElements(aux_elems)

    res = assembler.createVec()
    ans = assembler.createVec()
    mat = assembler.createSchurMat()
    alpha = 1.0
    beta = 0.0
    gamma = 0.0
    assembler.zeroVariables()
    assembler.assembleJacobian(alpha, beta, gamma, res, mat)
    res.scale(-1.0)
    print('forces:')
    print(res.getArray().reshape(-1,vars_per_node))
    print('sum:')
    print(np.sum(res.getArray()))
    print()

    node_vec = assembler.createNodeVec()
    assembler.getNodes(node_vec)
    print('nodes:')
    print(node_vec.getArray().reshape(-1,3))
    print()

# Print the nodal forces for the two difference cases (connectivities)
print('Case 1:')
print('-------')
print_nodal_forces(conn0, trac_face_indices0)
print('Case 2:')
print('-------')
print_nodal_forces(conn1, trac_face_indices1)

And here are the results.
Case 1:
-------
forces:
[[-0.         -0.         -0.        ]
 [ 0.01666667 -0.         -0.        ]
 [ 0.03333333 -0.         -0.        ]
 [-0.         -0.         -0.        ]
 [-0.         -0.         -0.        ]
 [-0.         -0.         -0.        ]
 [ 0.01666667 -0.         -0.        ]
 [ 0.03333333 -0.         -0.        ]
 [-0.         -0.         -0.        ]]
sum:
0.09999999999999999

nodes:
[[0.  0.  0. ]
 [1.  0.  0. ]
 [1.  1.  0. ]
 [0.5 0.5 0.5]
 [0.  1.  0. ]
 [0.  1.  1. ]
 [1.  1.  1. ]
 [1.  0.  1. ]
 [0.  0.  1. ]]

Case 2:
-------
forces:
[[-0.00000000e+00 -0.00000000e+00 -0.00000000e+00]
 [ 2.88675135e-02 -0.00000000e+00 -0.00000000e+00]
 [ 5.77350269e-02 -0.00000000e+00 -0.00000000e+00]
 [ 1.44222201e-17 -0.00000000e+00 -0.00000000e+00]
 [-0.00000000e+00 -0.00000000e+00 -0.00000000e+00]
 [-0.00000000e+00 -0.00000000e+00 -0.00000000e+00]
 [ 2.88675135e-02 -0.00000000e+00 -0.00000000e+00]
 [ 5.77350269e-02 -0.00000000e+00 -0.00000000e+00]
 [-0.00000000e+00 -0.00000000e+00 -0.00000000e+00]]
sum:
0.17320508075688776

nodes:
[[0.  0.  0. ]
 [1.  0.  0. ]
 [1.  1.  0. ]
 [0.5 0.5 0.5]
 [0.  1.  0. ]
 [0.  1.  1. ]
 [1.  1.  1. ]
 [1.  0.  1. ]
 [0.  0.  1. ]]

Again, the net force is higher than it ought to be.


Add schema spy templates

@WadeBarnes I've added in a stage to the Jenkinsfile but I have some questions.
I was using the other schema-spy projects as reference but they seemed to have a slightly different approach to the jenkins config. Those projects were using the OpenshiftDSL plugin, but this project wasn't. Does using it here make sense even though it it not used in any of the other stages? If not, how do we set up?
On top of that we know that we don't want to be running schema-spy on PROD. The other projects were using build lists to determine which apps get run. This project didn't have that infrastructure but it also seemed to only mention -dev in the ENV set up. I'm not sure if that means we are only running this for DEV and don't need to worry about separating the PROD apps, or if those references are just a means to get some other information. Do we need to set up something similar to the other schema-spy projects in terms of separating PROD and DEV?


Optimize tenant, flavor and template selection

Completely eliminates the n+1 query problem in optimizer.select_tmpl_and_flavor_and_tenant, thus fixing a nasty performance bug in PL-Grid Atmosphere deployment.

@mkasztelnik Can you help out with this? It's quite urgent (btw., we probably need an "Urgent" label -- perhaps you could define one).

Can you describe how can I help with it? What is missing? Only review or something more?

@mkasztelnik I just need a code review.

First of all can you squash all commits into one with meaningful name? Commits like "Interim commit." or "Woof." say nothing about what was changed and why.

I believe I'm done with all requested changes.

:+1: from me. Please merge all commits into one before merge.


Form Builder

how can i able to get the json data and stored in to a data base

use this php code:
$json_data = file_get_contents('php://input');


LA-436 Update test resource generation process

deploy-rpc-playbooks.sh changes:

calling generate-resources.yml is added to allow the resources to be
set up before Telegraf is deployed.
the rpc-maas var telegraf_plugin_ping_urls is set with the floating
IP addresses of the generated resources so they can be monitored
during the upgrade.

generate-resources.yml changes:

to accommodate the requirement to run this playbook in
deploy-rpc-playbook.sh it is moved to rpcd/playbooks
os-tempest-install.yml added to removing the need for rpc-gating to
manage this requirement.
checks for existing instances created by this playbook and skips if
there are any given that they only need to be created at the beginning
of an upgrade.

generate_resources.py changes:

updated to make use of the OpenStack Python SDK, this simplifies the
code
floating IP addresses are now assigned to the created servers
a security group is created to ensure the servers can be pinged

maas_release is updated to a SHA that includes support for the
Telegraf ping plugin.

Receiving objects:   0% (1/3596)
Receiving objects:   1% (36/3596)
Receiving objects:   2% (72/3596)
Receiving objects:   3% (108/3596)
Receiving objects:   4% (144/3596)
Receiving objects:   5% (180/3596)
Receiving objects:   6% (216/3596)
Receiving objects:   7% (252/3596)
Receiving objects:   8% (288/3596)
Receiving objects:   9% (324/3596)
Receiving objects:  10% (360/3596)
Receiving objects:  11% (396/3596)
Receiving objects:  12% (432/3596)
Receiving objects:  13% (468/3596)
Receiving objects:  14% (504/3596)
Receiving objects:  15% (540/3596)
Receiving objects:  16% (576/3596)
Receiving objects:  17% (612/3596)
Receiving objects:  18% (648/3596)
Receiving objects:  19% (684/3596)
Receiving objects:  20% (720/3596)
error: RPC failed; curl 56 GnuTLS recv error (-54): Error in the pull function.
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1924)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1643)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:71)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:352)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:559)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
	at hudson.remoting.UserRequest.perform(UserRequest.java:153)
	at hudson.remoting.UserRequest.perform(UserRequest.java:50)
	at hudson.remoting.Request$2.run(Request.java:336)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
	at ......remote call to long-running-slave-17-48bd(Native Method)
	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537)
	at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
	at hudson.remoting.Channel.call(Channel.java:822)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
	at sun.reflect.GeneratedMethodAccessor602.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
	at com.sun.proxy.$Proxy96.execute(Unknown Source)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1075)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1115)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:73)
	at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
	at hudson.security.ACL.impersonate(ACL.java:221)
	at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

recheck_cit_trusty_deploy_swift

recheck_cit_xenial_deploy_swift

recheck_cit_xenial_deploy_swift
recheck_cit_trusty_deploy_swift


color variables for checkbox/radio inset styles

Adds brand colors for the checkbox/radio button Design Manual updates.
See cf-forms PR for details:
https://github.com/cfpb/cf-forms/pull/41

:+1: Thanks @cfarm!


Devs can format their code without installing formatters getting in the way

Oh, and let's reset the yarn.lock file.

Find a solution

References:
https://github.com/Jille/dockpin

Should also address rate limiting/other ci nonsense like
yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.npmjs.org/@zkochan/js-yaml/-/js-yaml-0.0.[6](https://github.com/ChainSafe/forest/actions/runs/4979290978/jobs/8910701002?pr=2846#step:3:7).tgz: Request failed \"404 Not Found\"".
info If you think this is a bug, please open a bug report with the information provided in "/home/runner/work/forest/forest/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

https://github.com/ChainSafe/forest/actions/runs/4979290978/jobs/8910701002?pr=2846

The simplest solution would be to create a Docker image with all the tools installed and host it on GHCR.

If we were to do this, I'd be worried about a couple of things:

multiarch
non-reproducible builds (e.g ci uses forest-devcontainer:1.0.1) but when we git checkout 1.0.1 && docker build we get an error :/

I don't really see an issue. We could lock the tooling image tag in the repo. Not sure about GH Actions integration, it's just running a docker command so it's doable, no? Multiarch may be painful but we were able to provide multiarch images for Forest so unless there's some strange binary we manually download, we should be good there as well.
I'm open to other suggestions.

(I've fleshed out some comments above)

different version of clippy in CI to local: https://github.com/ChainSafe/forest/actions/runs/5154069457/jobs/9282067031?pr=2893

@aatifsyed what do we do with this?


[BEAM-5674] Add withKeyType to DataflowRunner.Deduplicate internals

This fixes the attached JIRA by explicitly typing the key as integer.

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.

R: @lukecwik


404 error on link in page

In the topic 'Related Links' is a link to SwitchDemo (sample), this link isn't working anymore (404 error).

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

ID: 06362667-c374-dfc5-ea7a-77023492065b
Version Independent ID: 62931423-8168-8df7-23fb-ad48f2029c4c
Content: Switch - Xamarin
Content Source: docs/android/user-interface/controls/switch.md
Product: xamarin
GitHub Login: @mgmclemore
Microsoft Alias: mamcle

Hi @PhenoNL, thank you for the feedback! This topic has been updated and the changes should be published soon.


fix(fullpage): add full page only optionally for some previews

Deploy preview for pf-next ready!
Built with commit c9bdc925448d7b2bd065a6f61288895abf32260c
https://deploy-preview-284--pf-next.netlify.com

Exactly what I needed so that full page things like backdrop don't obscure the workspace. 👍 Thank you!


Forbid easily misused HashSet and HashMap constructors

Fixes #8423

Description

This PR adds constructors for HashMap, HashSet, and LinkedHashSet that specify an initial size parameter to the forbiddenapi list. It replaces all usage of these constructors with Guava helper methods that take the users parameter for size and create a more optimally sized object for them compared to what they get from the native constructors.
HashMap, HashSet and LinkedHashSet objects are often created in an inefficient way when the creator specifies a size. Guava has created utilities to take the size desired by the creator and come up with a proper initial size for the underlying object for them. It is explained more clearly here. The same is also true for LinkedHashMap, but unfortunately we are still using Guava 16, and the Guava implementation for LinkedHashMaps did not come about until Guava 19.
I had to add an ignores item in the pom.xml file for SomeAvroDatum.class because it is generated at build time so it can't have a suppression annotation inline. If there is a better way to exclude that I'm not thinking of, please let me know.

This PR has:

[X] been self-reviewed
[x] been tested in a test Druid cluster.

Key changed/added classes in this PR
Many classes were modified, but the changes are all transparent. Just changing the way Map and Set objects are created in some specific cases.

The travis-ci logs for the failed build steps all appear to be a 5XX error pulling external resources. Any way to get the build restarted short of pushing a dummy commit?

@capistrant I restarted the failed runs earlier, was going to comment but got pulled away for a moment


Full Offline Dev Project

I'm traying to install ng2-admin in windows10 , after downloading the zip and extract it ,
i run "npm install" , i have multiple warnings :

when i run "ng serve" it doesn't works !
i'm looking for a full offline dev version ( with node_modules included) if possible !

Installation works now with yarn with some warnings :
$ yarn
yarn install v0.23.4
[1/4] Resolving packages...
warning There appears to be trouble with your network connection. Retrying...
[2/4] Fetching packages...
warning<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check.                                                     Excluding it from installation.
[3/4] Linking dependencies...
warning<EMAIL_ADDRESS>has incorrect peer dependency "@angular/core@                                                    ^2.0.0".
warning<EMAIL_ADDRESS>has incorrect peer dependency "@angular/commo  <EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has incorrect peer dependency "@angular/platf  <EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>                                                  ".
warning<EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>                                                   0".
warning<EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>                                                  .0".
warning<EMAIL_ADDRESS>has incorrect peer dependency "@angular/common                                                    @^2.3.1".
warning<EMAIL_ADDRESS>has incorrect peer dependency "@angular/compil  <EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has incorrect peer dependency "@angular/core@^                                                    2.3.1".
warning<EMAIL_ADDRESS>has incorrect peer dependency "@angular/forms@                                                    ^2.3.1".
[4/4] Building fresh packages...
success Saved lockfile.
Done in 408.27s.


what does ngx_proc.c file do?

In nginx, i could not find ngx_proc.c,ngx_proc.h
In tengine, what is the role of ngx_proc??

@chunhodong Ngx_proc module is used to start a signal process which is different from worker process but controlled by master.
It's pretty useful when you want do some task that takes a long time and you do not want to run it   in worker process.
See proc for more information

https://github.com/alibaba/tengine/commits/master/src/proc/ngx_proc.h
http://tengine.taobao.org/document/proc.html
provides a mechanism to support standalone processes
you can find the sample at http://tengine.taobao.org/examples/ngx_proc_daytime_module

Thank you for your answer. I understand the answer.


Adicionando mais um exemplo de uso

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

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

@kmmelcher Thank you for  creating this PR.  However, since it was created, the underlying document has changed.  Can you please review and resolve the current merge conflicts?  It could be the changes to the underlying document are so significant that your changes are no longer relevant.  If the latter is the case, it might be easier to just close this PR and create a new PR with any changes you still feel are important to make.
If you need any assistance or have questions about resolving the merge conflicts, please reply back or contact someone in the Contributors Room on Gitter.
Thank you.

We are restructuring a lot of the code and learning resources referenced in your pull request, so for now I am going to go ahead and close this pull request. Thanks again for opening this pull request and for contributing to the community.


Compatibility with Cordova 6.0.0, Cordova iOS 4.0.1 and Cordova Android 5.1.0

Hi! I'm trying to integrate this into a Meteor application. I'm using a beta of their new 1.3 release which has upgraded their implementation to only support the versions of Cordova listed in the description.
When I try to add this plugin to a Meteor 1.3 app, I get a fatal error:
$ meteor run ios --port 4000
[[[[[ ~/dev/meteor/test-app ]]]]]

=> Started proxy.
% Failed to install 'cordova-plugin-ace':TypeError: Uh oh!
Object [object Object] has no method 'parse'
    at handlers.js-module.install (/home/dir/dev/meteor/test-app/.meteor/local/cordova-build/platforms/android/cordova/lib/pluginHandlers.js:142:66)
    at Object.ActionStack.process (/home/dir/dev/meteor/test-app/.meteor/local/cordova-build/platforms/android/cordova/node_modules/cordova-common/src/ActionStack.js:56:25)
    at Api.addPlugin (/home/dir/dev/meteor/test-app/.meteor/local/cordova-build/platforms/android/cordova/Api.js:205:20)
    at handleInstall (/home/dir/.meteor/packages/meteor-tool/.1.1.13-beta.11.1dw6vym++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/cordova-lib/src/plugman/install.js:601:6)
    at /home/dir/.meteor/packages/meteor-tool/.1.1.13-beta.11.1dw6vym++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/cordova-lib/src/plugman/install.js:385:28
    at _fulfilled (/home/dir/.meteor/packages/meteor-tool/.1.1.13-beta.11.1dw6vym++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/q/q.js:787:54)
    at self.promiseDispatch.done (/home/dir/.meteor/packages/meteor-tool/.1.1.13-beta.11.1dw6vym++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/q/q.js:816:30)
    at Promise.promise.promiseDispatch (/home/dir/.meteor/packages/meteor-tool/.1.1.13-beta.11.1dw6vym++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/q/q.js:749:13)
    at /home/dir/.meteor/packages/meteor-tool/.1.1.13-beta.11.1dw6vym++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/q/q.js:509:49
    at flush (/home/dir/.meteor/packages/meteor-tool/.1.1.13-beta.11.1dw6vym++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/q/q.js:108:17)
    at process._tickCallback (node.js:448:13)
=> Errors executing Cordova commands:

   While adding plugin<EMAIL_ADDRESS>to Cordova project:
   TypeError: Uh oh!
   Object [object Object] has no method 'parse'
   at handlers.js-module.install
   (/home/dir/dev/meteor/test-app/.meteor/local/cordova-build/platforms/android/cordova/lib/pluginHandlers.js:142:66)
   at Object.ActionStack.process
   (/home/dir/dev/meteor/test-app/.meteor/local/cordova-build/platforms/android/cordova/node_modules/cordova-common/src/ActionStack.js:56:25)
   at Api.addPlugin
   (/home/dir/dev/meteor/test-app/.meteor/local/cordova-build/platforms/android/cordova/Api.js:205:20)
   at handleInstall
   (/home/dir/.meteor/packages/meteor-tool/.1.1.13-beta.11.1dw6vym++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/cordova-lib/src/plugman/install.js:601:6)
   at
   /home/dir/.meteor/packages/meteor-tool/.1.1.13-beta.11.1dw6vym++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/cordova-lib/src/plugman/install.js:385:28
   at _fulfilled
   (/home/dir/.meteor/packages/meteor-tool/.1.1.13-beta.11.1dw6vym++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/q/q.js:787:54)
   at self.promiseDispatch.done
   (/home/dir/.meteor/packages/meteor-tool/.1.1.13-beta.11.1dw6vym++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/q/q.js:816:30)
   at Promise.promise.promiseDispatch
   (/home/dir/.meteor/packages/meteor-tool/.1.1.13-beta.11.1dw6vym++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/q/q.js:749:13)
   at
   /home/dir/.meteor/packages/meteor-tool/.1.1.13-beta.11.1dw6vym++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/q/q.js:509:49
   at flush
   (/home/dir/.meteor/packages/meteor-tool/.1.1.13-beta.11.1dw6vym++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/q/q.js:108:17)
   at process._tickCallback (node.js:448:13)

Are these versions of Cordova unsupported right now?

I've now used Ace + Cordova 6.0 successfully (at least iOS). Sorry for the dumb question, but do you have instructions on how to install the 1.3 release of Meteor?
I'm not familiar with Meteor, but the error looks like something that wouldn't be specific to one plugin. Have you had success with this version of Meteor and a different plugin?
Thanks for any info you can provide!

No, thank you sir. To install Meteor:
curl https://install.meteor.com/ | sh

To create a new (latest beta) project (note this may change to 1.3-beta.12 later tonight):
meteor create --release 1.3-beta.11 my-meteor-app

To add this plugin ass a cordova plugin:
meteor add<EMAIL_ADDRESS>
This may take extra setup on your machine, but to add ios as a platform and run the app as a cordova app on xcode's ios simulator:
meteor add-platform ios
meteor run ios-device

Probably good reference for this issue is that this is in reference to meteor/meteor#6356. Martijn Walraven is Meteor's cordova guru, so his comments could probably shed some light

+1

from other thread:
"I looked into this some more, and the issue seems to occur because cordova-plugin-ace uses path.parse(), which was only added in Node 0.12. Because Meteor runs in Node 0.10, this won't work until we upgrade the included Node version (which is next on the roadmap).
Until then, running cordova plugin add cordova-plugin-ace manually in the cordova-build directory is the only workaround, but you may have to do this again when the project is regenerated or when Meteor reinstalls the plugins (which happens every time you add/remove another plugin)." -Martijn Walraven

Yep, this is an issue with Meteor. Going to close this. Thanks!


Enable docker, #18

@Nek- I fixed your comments + update README.md file in order to add Docker step

@Awkan thanks this work is awesome. :)


fix [GreasyFork] 404 bug

refs #9611

Can you explain the relationship between greasyfork and sleazyfork for someone who doesn't use either?
It is clear they are closely related services, but my instinct is that it would make more sense to add sleazyfork as its own service, rather than treating it as a fallback for greasyfork.

You're right, I have made the necessary changes to the code.


pydocstyle version 2 compatibility

WARNING:root:Linter `pydocstyle` not found.
This is happening since pydocstyle 2.0.0 released in 2017-04-18.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

https://github.com/PyCQA/pydocstyle/commit/13159ede09bc67c939493b150a8e3ecfa525b6fc#diff-2031238ddd3b79ef5acbb2277c140700L6

Diff (of pylama/lint/pylama_pydocstyle.py) required to make it work, with no backwards compatibility:
3c3
< from pydocstyle import PEP257Checker
---
> from pydocstyle import ConventionChecker
25c25
<         } for e in PEP257Checker().check_source(code, path)]
---
>         } for e in ConventionChecker().check_source(code, path, ignore_decorators=None)]

@klen Do you want me to create a PR? With or without backwards compatibility?

@not-raspberry I've made a PR to fix this (and also considering backwards compatibility), but it raised lots of new errors on the CI. I'm not sure if these errors are related to the new pydocstyle version.
It may also have some problem related to the new version of pylint, since that a similar warning was raised after fixing the pydocstyle warning (pylama/config.py WARNING:root:Linter pylint not found).
Any tips on how to fix this things?
Should I fix pydocstyle and pycodestyle  erros on test_pylama.py or dummy.py?

This seems to be an open issue still for Pylama 7.3.3. Is there a workaround for this issue to get pydocstyle to work in Pylama? If there is no workaround can the version of pydocstyle be pinned to a compatible version rather than using >=2.0.0 in requirements.txt?

@colinmcintosh I've made a PR (#97) that may fix this issue. But, for that PR to work (pass on tests), pylama needs to drop python2.6 support (as seen on #98).

I'm going to ping @klen in case he doesn't automatically get notifications of issues on this repo. @klen - pylama has been incompatible with the current version of pydocstyle for over a month now.

@diraol I saw that PR but until someone has time to make the changes needed for it we would appreciate a bugfix release of Pylama that is pinned to version 1.1.1 of pydocstyle.

@colinmcintosh My PR solves the problem (off course it drop python 2.6 compatibility, but I think there is no much sense to keep it anymore).
I could also have sent another PR just pinning pydocstile to 1.1.1, but the problem is that we depend on a feedback from the project owner, no matter the solution or the PR. So our hands are tied over here.


[WIP] Try to convert build to Win

Current status: I/O error. Ideas?

Hi - I tried it and it seems like it isn't expanding the *.erl wildcard and tries to compile it as  single file. not sure if that is and erlc issue or what. you could work around by listing src/*.erl and pipe each into erlc perhaps.
Thanks for looking at this btw :)

This may be relevant: http://erlang.org/pipermail/erlang-questions/2011-January/056066.html

ok that works.
Next issue: I have no idea what to do  with the fezc now!?

creating a cmd? like in @eb188b9 ?

fezc is a mess and I just realised it is also buggy. :)
What is needed is basically a script that takes a bunch of files as arguments, dotnet run src/fez/fez.fproj <args> to generate the .core files then erlc all the .core files into the same directory. What the current script doesn't take into account is the fact that an .fs file could generate multiple .core files (one for the main module then one for each nested module).

how about letting this be done directly by the dotnet project?
It could automate erlc right?

Ideally I'd like to keep fez as and fsharp to core erlang compiler as I suspect that would play nicer with other erlang build tools but perhaps we could have it as an option?
Alternatively maybe fez should output a list of the .core files it generates then we could just pipe that into erlc

yes fine. also it should not output the core file on stdout.  what a waste of runtime ;-)

it may print the fsharp ast atm if I forgot to comment that line out :)
I meant output the paths to the .core files rather than the file contents. it should definitely write that as current is done.

cool. I'd then rebase on your changes ;-)

ok my cmd is now building the basics.fs just fine to beam. How can I run it?

Run-tests.sh uses the output of basic.fs. Alternatively you could do erl -pa ebin test to open a shell with the appropriate search paths.

wow!

I know right! ;)

Ok removed the AST printing

printing OUTFILEs instead

ok my cmd file is captering the files and send it to erlc. That's nice!

That's so sweet 💯 !!!

Fantastic. Ready to merge?

@kjnilsson you would need to patch the unix side I'm afraid

but apart from that yes.

That's fine. It might still work.


Missing stuff for reindeerGames

Readme.md is missing for the reindeerGames sample. Additionally, it looks like there should be a customSlotTypes folder with a file for LIST_OF_ANSWERS.

Hey there! Thanks for filing an issue - please be advised that we're no-longer providing support for this project and so instead, please check out the replacement Alexa Skills Kit SDK for Node.js:
https://github.com/alexa/alexa-skills-kit-sdk-for-nodejs
Also, we have a number of sample skills based on this newer SDK, under here:
https://github.com/alexa


Fixed typo predicter -> predictor

Describe changes
I fixed a small typo that was breaking the post_execution.ipynb
Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[x] If my change requires a change to docs, I have updated the documentation accordingly.
[x] If I have added an integration, I have updated the integrations table.
[x ] I have added tests to cover my changes.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for catching that, @MateusGheorghe! Much appreciated. We'll get that merged as soon as you're able to sign the contribution agreement. Thanks again!

Thanks for the contribution @MateusGheorghe!


Warnings after upgrading to React 16.9: componentWillMount and componentWillReceiveProps renamed

After upgrading to React 16.9.0 I get the following two warnings:
Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

and
Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

The warning suggests to rename these methods to *_UNSAFE, but this is a workaround and I can imagine you might want a better solution?

Thanks. I will start working on a new version for it.

Thanks @dlin-me! It's a great package!

any word on this.  my log is now swamped with warnings. :\

v1.5.2 addressed these warnings.


Protocol details layout

Add a basic layout of documentation for protocol details.

More than this? https://docs.nearprotocol.com/details

More than this? https://docs.nearprotocol.com/details

This link is deprecated. Protocol details will be updated when Nightshade goes live.

Adding protocol details back in using Nightshade paper.

fixed: https://github.com/nearprotocol/docs/commit/c2ca7d1359bda66efa7c68a54d2af524775d8ba4


Escaping / in path

I use the newest moya.
And I've got we weird problem setting up the proper path.
The problem is that id you the object has / inside which has to be escaped.
But it can't really be passed as param because it's in the middle of the path:
Typical object id: lci80MzY2NDQwODU4NDI/a2V5PTE0MjNmMmN
var path: String {
        switch self {
        case let .trackObject(objectId):
            return "/objects/\(objectId)/track"
        }
    }

Slash is a valid sign so it won't be escaped.
But when I do this:
return "/objects/\(objectId.addingPercentEncoding(withAllowedCharacters: .urlHostAllowed) ?? "")/track"

The % sign will be escaped afterwards.
I tried playing with parameter encoding, no luck.
Any suggestions?

@maciejburda You can use the parameters in task like this:
swift```
public var task: Task {
switch self {
case .youCase, return .requestParameters(parameters: parameters, encoding: URLEncoding.queryString)
}
where parameters manually created property(or create dictionary here):

typealias Parameters = [String: Any]
    var parameters: Parameters {
        switch self {
        case let .login(username: name, password: pass): return ["username": name, "password": pass]
        }
    }


Dockerize updates

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 5 committers have signed the CLA.:x: Rahul Ramakrishnan:x: roryhubbard:x: smartag-raven-travisci:x: alexhaislip:x: aalibasicRahul Ramakrishnan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Askign about other version

hi do you have confuserEx version 2 or is it closed source code i also tried downloading the source code for AntiTamperKiller but i cant download from the website do you have a link too it please

?


GAL-2689 Search Mobile

Changes

Add search screen in navigation
Only have curater and gallery
Only available for list result. The result its not clickable.

Demo
https://user-images.githubusercontent.com/4480258/229768248-da67088c-1b72-4ed8-a981-0344baa60ebd.mp4

lfg!!!!! gonna leave some design comments
There's a delay to show results after tapping a pill - do you know why that is? on desktop the results display almost instantly after clicking the pill
https://user-images.githubusercontent.com/80802871/229836457-9ffc7440-84a5-41a5-a59c-a3a573e4daaa.mp4
Can we change "Nothing Found" to "No Results" for the empty state? and can we position closer to vertically center of the screen and not just the Search component?

Can we add the "Search for anything..." placeholder text if the Search input is empty?

let's update the active state of the pill to match desktop
this PR

desktop


Bump jxl version and remove workaround for enc memory usage.

Code lgtm! Not sure why there are conflicts? @veluca93 can you make sure your branch is rebased against dev?

Code lgtm! Not sure why there are conflicts? @veluca93 can you make sure your branch is rebased against dev?

I was apparently using an older version of dev - it should be OK now.


fixes #2473 - Tooltip is shown for indentation

fixes #2473 - Tooltip is shown for indentation
Reverse expression parser "fix" (in quotes due to my own uncertainty) to attempt and catch whitespace-strings identified for type hover over.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Add CI for disabling detail logging.

This way we won't have to worry about problems popping up if/when
someone tries to do that.
For now assuming no one really plans to disable error logging.
Problem
#8135 had to happen because we have no CI for the "detail logging disabled" configuration that is used by scripts/build_python.sh by default.
Change overview
Add basic CI for a build in this configuration.
Testing
Verified that this CI fails without the change from #8135 and passes on tip.

@saurabhst @msandstedt @jmartinez-silabs @jepenven-silabs Please take a look?


Consul start script parameters

Expected Behavior
When start consul with brew services start consul the consul key-value storage should be persist.
Actual Behavior
Consul KV stores is not persist because brew services start consul run with -dev parameter default in homebrew.mxcl.consul.plist file.
Could you please remove the -dev parameter from default ?

Could you please remove the -dev parameter from default ?

Please submit a PR to homebrew-core to do that. Thanks!


object VCRUNTIME140_1 . dll. not found try to install program again

any solution for this?

yes, read the instructions.
https://github.com/a1xd/rawaccel/blob/master/doc/Guide.md


Remove python-dateutil check

Changes made to upstream in PR263 make these changes unnecessary. I had previously merged those changes in here premature, but that creates a breaking change in this fork.
So, here's a fix for that problem I caused. Sorry!

As mentioned earlier, you can also just fetch our upstream master branch to take in the new changes instead. Accept this PR as an apology only if you want to maintain your own fork separate from ours. :)


put file path in quotes when call "system()"

"system()" called by "get_git_untrack" and "get_hg_untrack" fails. It report error "Can't open file /tmp/***".
The root cause is that the file path for system() contains some unordinary character and lacks quotes.
The bug happens in both windows and linux:

shouldn't we use shellescape() instead?

yes. shellescape() will be better.

okay, please update your commit and I'll merge. Thanks.

chrisbra, I have updated the commit. Please take a review. Thanks.

thanks.


make connect function compatible with NextJS

Thanks! Glad to help! I personally like using this library over redux, because it is less complex.


use gpt-4 turbo for 16x more context and it's cheaper and faster

I also didn't test this one but it should work unless not everyone has access to gpt-4 turbo plus

GPT-4 Turbo is more capable and has knowledge of world events up to April 2023. It has a 128k context window so it can fit the equivalent of more than 300 pages of text in a single prompt. We also optimized its performance so we are able to offer GPT-4 Turbo at a 3x cheaper price for input tokens and a 2x cheaper price for output tokens compared to GPT-4.

I'm holding off on this because gpt-4 turbo isn't widely available yet, it was rolled out super recently so would rather release this with a more stable version of GPT4. But people should certainly upgrade to gpt-4-turbo if they have access to it and know what they're doing


Fix: typo atleast -> at least

Typo found in source string, reported by linux-man on weblate

Thanks!


Revealing cards should trigger a sharing bonus

It should also count as a game state change for The Big Bang.
"A change is one or more cards being revealed, or moved from one location to another" from the rulebook

After checking with Chris, I learned that in the next printing:
You will need to reveal your hand to verify for effects like Clothing, Classification, etc. The revelation of information will NOT trigger sharing draws for dogma effects. The "Did something happen" will refer strictly to whether cards moved from one location to another, or were splayed.
For this reason, I don't think we should trigger a sharing bonus, even now.


Broken links on rubygems.org

On https://rubygems.org/gems/cri, the links to "Documentation" and to "Homepage" both still point to README.md and result in 404's.

Fixed, thanks for reporting! Both of them now point to http://rubydoc.info/gems/cri.


Random: The antiforgery token could not be decrypted.

Issue Title
Hello,
We are getting random: The antiforgery token could not be decrypted.
Site is running on IIS on Windows 2016, the authentication is Azure AD, Application in running on NET CORE 2.1.4.  No error generated on the development site.
I am not too sure where to start...
Thank's
fail: Microsoft.AspNetCore.Antiforgery.Internal.DefaultAntiforgery[7]
An exception was thrown while deserializing the token.
Microsoft.AspNetCore.Antiforgery.AntiforgeryValidationException: The antiforgery token could not be decrypted. ---> System.Security.Cryptography.CryptographicException: The key {9009f561-0974-426e-8d3a-00fb5ce76e95} was not found in the key ring.
at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.UnprotectCore(Byte[] protectedData, Boolean allowOperationsOnRevokedKeys, UnprotectStatus& status)
at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.DangerousUnprotect(Byte[] protectedData, Boolean ignoreRevocationErrors, Boolean& requiresMigration, Boolean& wasRevoked)
at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.Unprotect(Byte[] protectedData)
at Microsoft.AspNetCore.Antiforgery.Internal.DefaultAntiforgeryTokenSerializer.Deserialize(String serializedToken)
--- End of inner exception stack trace ---
at Microsoft.AspNetCore.Antiforgery.Internal.DefaultAntiforgeryTokenSerializer.Deserialize(String serializedToken)
at Microsoft.AspNetCore.Antiforgery.Internal.DefaultAntiforgery.GetCookieTokenDoesNotThrow(HttpContext httpContext)

@Eilon

This issue was moved to aspnet/Home#3540


Create wireframes

Mock up wireframes for the frontend to help with frontend dev.

Kellen Drafted up the initial wireframes in Miro: https://miro.com/app/board/uXjVK-MTpqE=/?share_link_id=390813905477
Currently holding an internal vote between option 1 and option 2


Storage migration to MMKV from Async storage

New Storage Mechanism :

All the Application Config Details, Settings Details and Meta Entries will be moved from Async Storage to MMKV
Storage of all the VC has been Moved from Async Storage to FS Storage and stored as separate Files in the below path:

iOS: /var/mobile/Containers/Data/Application/196A05AD-6B11-403D-BA2D-6DC1F30075E1/Documents/<filename>
Android: /data/user/0/io.mosip.residentapp/files/<filename>
The filename is the key against which the VC was being stored.

Only The Storage is Updated and Encryption / Decryption mechanism stays unchanged.
The Objective of the Migrating From AsyncStorage

MMKV has better Performance than the Async Storage.
VC's are stored as separate Files to improve the overall Security.

The feedback for this PR addressed as part of this PR which was merged into Hotfix release branch for internal Hotfix release.


extHostSearchTest.ts: some skipped tests

This is to report that skipped tests should either be deleted or fixed:
https://github.com/microsoft/vscode/blob/1927f9b6e07ad66d4ee06ee794d2a2ab92fa3fd2/src/vs/workbench/test/electron-browser/api/extHostSearch.test.ts#L464-L464
https://github.com/microsoft/vscode/blob/1927f9b6e07ad66d4ee06ee794d2a2ab92fa3fd2/src/vs/workbench/test/electron-browser/api/extHostSearch.test.ts#L500-L500
https://github.com/microsoft/vscode/blob/1927f9b6e07ad66d4ee06ee794d2a2ab92fa3fd2/src/vs/workbench/test/electron-browser/api/extHostSearch.test.ts#L536-L536

Not sure why I skipped them, they seem fine

Not sure why I skipped them, they seem fine


Users connecting/disconnecting doesn't get updated in Nostalgia and Obsession

Hi!
Happy holidays :)
I recently noticed that users connecting and disconnecting didn't get updated properly when using Nostalgia and Obsession.
It works when using hxd and the official Hotline server, so I'm thinking this probably is a Mobius issue.
People disconnecting keep being in the user list on Nostalgia and Obsession and only a disconnect and reconnect to the server updates the user list to display the correct amount of connected users.

Hi there, happy holidays! ☃
I'll take a look in the next few days.

Hi, I've released v0.10.12 with a fix for the  Obsession client.
I wasn't able to reproduce the problem in the Nostalgia client, at least in version 0.991.

I have installed 0.10.12 and it seems to fix the problem, but I have observed it on other clients as well.
Maybe they are a bit odd in terms of how many people actually use them, but they are still a bit incompatible with Mobius.
Tested with Pitbull Pro 2.4.4 on Mac OS Classic and with Heidrun on Mac OS X Tiger and they have the same issue as Obsession had. Is there any other way to determine client compatibility?
I also noticed that the threaded news section doesn't display what's actually in the news item when using Frogblast, but that's for another ticket :)
Thanks for working on this wonderful piece of software! :)

I believe this issue should be fixed in all clients now in v0.10.15.
Thanks as always for reporting these issues!


Develop

Main functional changes are standardised stats names and dropping DCS requests that don't have an actual commit (that currently lead to failed jobs down the chain).
Callback code is added, but nothing in the prodn chain shouldn't call it yet.
Lots of minor documentation and some minor code cleanups including nicer logging.

Pull Request Test Coverage Report for Build 62

27 of 119 (22.69%)  changed or added relevant lines in 2 files are covered.
16 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-56.2%) to 30.189%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

enqueue/check_posted_payload.py
27
34
79.41%

enqueue/enqueueMain.py
0
85
0.0%

Files with Coverage Reduction
New Missed Lines
%

enqueue/check_posted_payload.py
1
85.71%

enqueue/enqueueMain.py
15
0.0%

Totals

Change from base Build 56:
-56.2%

Covered Lines:
48

Relevant Lines:
159

💛  - Coveralls

Pull Request Test Coverage Report for Build 62

27 of 119 (22.69%)  changed or added relevant lines in 2 files are covered.
16 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-56.2%) to 30.189%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

enqueue/check_posted_payload.py
27
34
79.41%

enqueue/enqueueMain.py
0
85
0.0%

Files with Coverage Reduction
New Missed Lines
%

enqueue/check_posted_payload.py
1
85.71%

enqueue/enqueueMain.py
15
0.0%

Totals

Change from base Build 56:
-56.2%

Covered Lines:
48

Relevant Lines:
159

💛  - Coveralls

Looks good @RobH123 .  Have you tested the dev pipeline with these changes?


Azurecore:  Fixes upgrading azure core dependency to 1.44.1

Azure.Core:  Fixed upgrading azure core dependency to 1.44.1
Changes

ResourceType: Conflict between Azure.Core and Microsoft.Azure.Cosmos.Documents
Microsoft.Bcl.AsyncInterfaces: Azure.Core needs at-least 6.0.0 (as Azure core upgraded part of minor version, we are good as well)
Microsoft.Azure.Cosmos.Encryption.Custom: Direct dependency on Azure.Core removed (now its transitive)
Microsoft.Azure.Cosmos.Encryption.Custom.Performance.Tests: NU1903 added Newtonsoft.Json dependency
Performance project: NU1903 Newtonsoft dependency upgraded

Just curious: What are benefits we are getting with this upgrade? and did we evaluate "breaking changes" because here we are making big jump (from 19 to 44 version)?

Just curious: What are benefits we are getting with this upgrade? and did we evaluate "breaking changes" because here we are making big jump (from 19 to 44 version)?

It's a minor version upgrade (not major). Benefits

Transient dependencies vulnerabilities (we are patching them in our code which is unnecessary)


KAFKA-3937: Kafka Clients Leak Native Memory For Longer Than Needed With Compressed Messages

@ijuma - Creating this PR against 0.9.0 as this is what we're using in prod. I can modify this for trunk if the logic solution looks good.
I modified the record iterator to inherit from closable and implemented the method to call streams.close(). The stream will now be closed when we are done traversing the inner iterator. I had to move the try {} catch{} out of the if portion to deal with IOException coming from innerDone().

I suggest doing this on trunk where we can follow the same ideas we did for the server. That is, we remove the special-case for V0 below and close the stream in a finally.
if (entry.record().magic() > Record.MAGIC_VALUE_V0) {
                this.logEntries = new ArrayDeque<>();
                long wrapperRecordTimestamp = entry.record().timestamp();
                while (true) {
                    try {
                        LogEntry logEntry = getNextEntryFromStream();
                        Record recordWithTimestamp = new Record(logEntry.record().buffer(),
                                                                wrapperRecordTimestamp,
                                                                entry.record().timestampType());
                        logEntries.add(new LogEntry(logEntry.offset(), recordWithTimestamp));
                    } catch (EOFException e) {
                        break;
                    } catch (IOException e) {
                        throw new KafkaException(e);
                    }
                }
                this.absoluteBaseOffset = wrapperRecordOffset - logEntries.getLast().offset();

@ijuma sure, I can do that, but how would the change go back into 0.9.0 or is it no longer updated?  Do I need to self patch and release my application with the forked changes?
Is this what you had in mind about the change about ignoring the V0 and using finally?
            try {
                if ( entry.record().magic() > Record.MAGIC_VALUE_V0 ) {
                    this.logEntries = new ArrayDeque<>();
                    long wrapperRecordTimestamp = entry.record().timestamp();
                    while ( true ) {
                        try {
                            LogEntry logEntry = getNextEntryFromStream();
                            Record recordWithTimestamp = new Record(
                                logEntry.record().buffer(),
                                wrapperRecordTimestamp,
                                entry.record().timestampType()
                            );
                            logEntries.add(new LogEntry(logEntry.offset(), recordWithTimestamp));
                        }
                        catch (EOFException e) {
                            break;
                        }
                        catch (IOException e) {
                            throw new KafkaException(e);
                        }
                    }
                    this.absoluteBaseOffset = wrapperRecordOffset - logEntries.getLast().offset();
                }
                else {
                    this.logEntries = null;
                    this.absoluteBaseOffset = -1;
                }
            } finally {
                try {
                    stream.close();
                } catch (IOException e) {
                    throw new KafkaException(e);
                }
            }

@wiyu, if we want to make the changes to 0.9.0, then they will have to be different as you suggested. The reason why I prefer the approach I suggested is that it handles the case where the iterator is not consumed fully as well. But I haven't looked in detail, so if it's possible for the same solution to handle that in 0.9.0, 0.10.0 and trunk, then we can consider that.
With regards to what I meant, here's the equivalent for the server code:
https://github.com/apache/kafka/pull/1660/files

Closing, will open a new PR.


Implement ast_builder for ADD_MONTH function

resolved in https://github.com/gluesql/gluesql/pull/1341


Add 2 TS4231 support using DIFFERENT cores

one sensor per core

no changes needed for the library.
just the main file.

note that when 2 pulses arrive at the same time. demodulate_ligth() only shows one pulse. But it is processing both


Fix enum type to use int64_t instead of int in GDScript

Fix https://github.com/godotengine/godot/issues/67824

Thanks!


Issue with the cropper (dark mode)

          Issue with the cropper as well @g123k

Originally posted by @teolemon in https://github.com/openfoodfacts/smooth-app/issues/6084#issuecomment-2564805789

Probably a very recent issue: doesn't appear in my local version.

I have the same in
BuildNumber: 1412
But disappeared in playstore internal
1415

(Also Congrats @monsieurtanuki 🎉)


If/else statement in bracketless while loop complains about indentation

Describe the bug
When creating a while loop containing just one if/else, if the brackets are on the else, norminette will complain you've indented those lines too much. If you put the brackets around just the if, norminette will additionally complain about multiple instructions in a single line control structure.
Erroneous code
This example complains about indentation on else and the 4 lines after
int	main(void)
{
	int	var;

	var = 0;
	while (true)
		if (true)
			function();
		else
		{
			function();
			var++;
		}
}

Additional infos

OS: Manjaro 5.13.19-2
python --version: 3.10.4
norminette -v: 3.3.51

Hey there
I've been doing tests on my own and I believe I (may) know why.
If you keep aside the logic/functionality of the code, we have the following:
while without curly brackets
    if statement
    else statement

On the compiler side, the if and the else work together. However, due to the lack of curly brackets in the while, norminette believes that the code is something like:
while without curly brackets
    control structure inside the while loop
control structure out of the while loop

Therefore, the indentation "is not correct" (according to my interpretation of norminette's thought). Furthermore, if you test with the else like code below, nominette output is OK.
/* ************************************************************************** */
/*                                                                            */
/*                                                        :::      ::::::::   */
/*   aaaaa.c                                            :+:      :+:    :+:   */
/*                                                    +:+ +:+         +:+     */
/*   By: jre-gonz<EMAIL_ADDRESS> +#+  +:+       +#+        */
/*                                                +#+#+#+#+#+   +#+           */
/*   Created: 2022/08/16 13:02:10 by jre-gonz          #+#    #+#             */
/*   Updated: 2022/08/16 13:02:12 by jre-gonz         ###   ########.fr       */
/*                                                                            */
/* ************************************************************************** */

#include <stdio.h>

int	main(void)
{
	int	var;

	var = 0;
	while (1)
		if (var++ % 2)
			printf("hi\n");
	else
	{
		printf("hi else\n");
	}
}


Scss variables

There is any way to change sass variables without copy and paste from node_modules? Another doubt, can we follow the Shopify colors principles to make changes in styles?

@murilolopes
Currently we are not displaying those variables anywhere in documentation, but we would do it in future update.
And yes we are currently focusing on Shopify colors changes, we may have covered 90% of Shopify's color styles.
Feel free to post any component which is not showing proper color standards with Shopify.

Closing this issue.


Unable to send address bytes

No idea where in the scheme of things this fits, but trying here first
Last night, went to Bed and Alexa ‘Everything Off ‘. Worked perfectly
This morning... no response to my commands
so i try via ‘Terminus’ app on the phone to get the Cmd line on my Pi that’s running HA Bridge/ Heyu
type in ‘heyu On A1’ or any command and just eventually get an ‘Unable to send address bytes’ response.
‘Heyu Monitor’   just sits there and shows no ‘traffic’ when the normal X-10 controller or TIP10RF device sends signals .
Nothing changed in the system, it was all exactly the same as it has been for many years.
I had a thought of what it could be, but thought I’d get confirmation here, I won’t plant seeds by saying what I thought.... anyone else seen this ?

I think this issue was accidentally posted here instead of the heyu git issues?

Still, this is for habridge items. If there are no answers in a few days, I will close this as it is already posted in the heyu issues.

Yep, no problem
No answers on there either
With the constant Alexa discovery issues, and now the CM11 hardware failure and inability to buy a new one, might be time for me to scrap the entire HA-Bridge / X-10 / heyu system and move in to the modern age with newer devices !   Keeping all this vintage kit running with hacks like heyu/ HA-Bridge is getting harder all the time !

FYI. I switched to OpenHAB to control the CM11 and also if you can get a CM15, mochad works great as well.

Think the issue is the CM11 has died,
Can’t see any other reason for it to suddenly stop working.
I do have a CM15 but know that will not work in place of the CM11
Could you elaborate on how you set up the CM15 to drive the X-10 devices with Alexa... am using an RPi 3 B+

google "mochad" as that is the CM15 controller for linux

Thanks
found one article but it is a bit beyond my understanding .  I did the original build by following a tutorial ...Do this type that ..et ..
not yet found one for mochad
Looks like the Cm11 I need is actually a CM12U ..that seems to be the british one.

looks like it could well be a filesystem corruption issue on the Rasp Pi SD card.
just done a clown of the card and the problem persists.
Yet writing an old img of the sd card from a while ago...it works correctly.

solved.
2gb SD card was full ..so tempted field that get written as commands are sent ..had no space to be written
Clone and expand FS  to 16GB card and all working again


Add CreateScriptInstance

Adds a function that converts entities to SQObjects to the SquirrelManagers.

Ok, genuinely, how can this be even tested?

Ok, genuinely, how can this be even tested?

Usually the approach is to have a small PoC script mod that highlights the change. I don't understand enough atm to tell you whether that would make sense in this case ^^"

Ok, genuinely, how can this be even tested?

Usually the approach is to have a small PoC script mod that highlights the change. I don't understand enough atm to tell you whether that would make sense in this case ^^"

Unfortunately, no known part of the codebase (outside of #691) uses pushobject/createscriptinstance. My guess is that #691 will test this by proxy?

I did test the server offsets in a plugin :p

Maybe we just merge without further testing ig?

Maybe we just merge without further testing ig?

Yeah, just merge it.

Aight consider it merged. I might just gonna put a few more fixes in front to reduce the amount of cherry-picking I have to do ^^

Wow this got finally merged


Popular tab should have a time period option

If I click popular I should be able to specify a time period, e.g. today, this week, this month, this year, all time.

Maybe have the periods of time be more adjustable and dynamic, this is just a general idea. The All Time one could become its own tab and the rest could go under "Hottest" too, just throwing ideas around.

Button could work like the "All"  button on the right currently does with the arrows


Automatically renames actors in combat (to generic "PC" and "NPC" slots)

Is there any way to turn off this feature, or is there a way to save the character names and art so that when I add them to the combat tracker it does not lose their art and name?

Yes, it is "auto-rename combat actors" in the settings.

thank you!


Don't crash if we find empty lcov.info (#150)

Sometimes we may encounter an empty lcov.info file. Since we know
that an empty file can't contain valid coverage data, we simply
ignore it rather than unsuccessfully trying to load.

This change is

@ermshiperete Thanks for the support and quick fix on this! I think make a dev release (2.4.0) and see if this fixes #150 for the other person as well.

How can I run the unit tests?

@ermshiperete if you mean run the CI tests they auto run with every branch and are visible in azure pipeline https://ryanluker.visualstudio.com/vscode-coverage-gutters/_build/results?buildId=147
if you mean how to you locally run them, you can use  "test-unit": "cross-env MOCHA_GREP=@unit npm test --silent", as per the package.json


Provide debug information files with the built libraries

From https://github.com/SoftEtherVPN/SoftEtherVPN/pull/498#issue-182874641:

The LNK4099 warnings happen because the static libraries we have in the repository should have dedicated PDB files, but they are missing.
@dnobori Could you add these files to the repository, please?

The path for the debug information file in the projects is:
$(SolutionDir)DebugFiles\pdb\$(PlatformName)_$(ConfigurationName)\$(ProjectName).pdb
Which would be, for example:
src/DebugFiles/pdb/x64_Release/zlib.pdb

Fixed in #741.


Add checkbox for annotation selection displaying segmentation

This PR addresses issues #425 and #432 by adding a checkbox to annotation layers that, when checked, will display any associated segments of an annotation when that annotation is selected. It also saves this new checkbox and the "bracket shortcuts show segmentation" checkboxes in the state as requested.

So good thing is it seems to work with all annotations including collections. Problem is that it seems that unless I actually select the segment before hand, going through annotations only displays super voxels instead of the whole segment.
Additionally, seeing the notification for selected/deselect segment is very annoying and it actually stacks so it ends up obscuring a lot of the bottom.
See here:
http://localhost:8080/?json_url=https://globalv1.flywire-daf.com/nglstate/4904906188128256

also I just realized I posted a localhost url, but just use the JSON_URL= part


Add handling of .skip_lint file(s)

that allows to list linters to be skipped. A skip file in the repo root and in the tool dir are allowed (and joined).
TODO:

[x] add test

Lets release this together with https://github.com/galaxyproject/planemo-ci-action/pull/59?


Improve audio quality

See if the opus codec settings can be tweaked to improve the audio quality.

Solved in 3195d23acc16c1c55b6b3f1267ede3323e538dec


Simultaneous Activation of 'Designer' and 'Cloud Engineering' Dropdowns

The issue involves the unintended behavior of the dropdown menus in the skills section. Specifically, when clicking the dropdown toggle next to "Cloud Engineering", the "Designer" dropdown also activates and vice versa. The expected behavior is that only the dropdown clicked should expand or collapse, without affecting the other.

Issue is fixed now.


[analyzer] implicit_super_initializer_missing_arguments fix for super_parameters

class A {
  final int a;
  A(this.a);
}

class B extends A {
  B();
}

There is an offered fix for implicit_super_initializer_missing_arguments to be
B() : super(0);

But I guess another fix should also be offered to
B(super.a);

(when super_parameters  is enabled, of course).

https://dart-review.googlesource.com/c/sdk/+/266742


How to escape / not parse asterisk char in output?

Hi there, I just noticed that we'll lost the asterisk char in output, and then the context may have highlight/bold style, wonder if can prevent it been parsed? It'll be very useful, thanks!

I think this isn't a problem in vows 1.x, so I'm going to close it.

Thanks! Would v1.x be available on npm soon? I see the latest stable is v0.8.1 there.

It is on npm, just under the next dist-tag. You can try it out with npm install<EMAIL_ADDRESS>or npm install vows@next!

Yes, I noticed the alpha version and seems v0.8.1 is the latest "stable" release.


fix(config):  wrong rocksdb config name max_sub_compactions

Configuration item rocksdb.max_sub_compactions should be rocksdb.max_subcompactions.
Try set rocksdb.max_sub_compactions:

Fix it as rocksdb.max_subcompactions, try again:

LGTM. But seems no regression tests to guard this manner ..

Unit tests can cover this scenario. The reason why unit test was ineffective before is that callback was not registered for the item, which means config set command did not actually execute in rocksdb. See

We can first checkin, and adding a cfg testing, and everyone we add a new config, a go-side cfg test should be added to cover the case?


got error:TypeError: Descriptors cannot be created directly.

here is the error log.
running with exmple workflow

This is a SentencePiece issue. Please refer to Issue with sentencepiece tokenizer - 🤗Transformers. Could you confirm the version of protobuf? The SentencePiece installed on your system requires a compatible protobuf version.

protobuf -5.28.3


Adds links to ActiveRecordExtended and to maintained fork

I spent a long time looking for gem which would make jsonb queries easier. I almost did not find ActiveRecordExtended, but I ended up in this repo. Just linking to it so someone else may find it as well.


label at bottom of triptic

Per Florida Keys National Marine Sanctuary Integrated Ecosystem Assessment Conceptual Model.docx - Google Docs:

This could be done in at least a couple ways:

table with 3 cells
div tags with Bootstrap 4 layout

See also https://github.com/marinebon/fk-esr-info/issues/11#issuecomment-789142509

Infographic.html now contains the labels, as you can see below, contained within a html table.

You will notice that the triptych labels are slightly offset to the left of the image. This is due to some complexity in the css layout that I am unable as yet to sort out.
Similarly, the attribution on the last line is also way to the right, for the same reason.
Perhaps this is good enough, but if not, more css hacking is needed.

The layout is now fixed

My slight preference is for these to be above rather than below infographic, but closing because this is what Kelly M requested.


in multiplayer actor the motion controller is missing

pawn is compeletly working in 4.26. but in 27. it will work when it access to the camera the other time it is not working.

the motion controller is working on the server but it is not working on the client-side.

How are you setting up the network replication for your pawn?
You may need to replicate the motion controller transforms, then set those transforms manually for non-locally-controlled players.
Some example code:
MotionControllerLeft/Right are MotionController components in the player pawn and Left/RightHandTransform are local Transform variables that are set to replicate.


About cgraph.py

what does this file do?

It's an incomplete feature. We are working on a major refactorization so story tuned:)


Permission error in Payout contract.

Please refer to https://github.com/crypto-meetup-dev/cryptomeetup-contracts/issues/34 for detail.

done. #14


lastUpdate property return Invalid Date even though it's not invoked

Describe the bug
lastUpdate property return Invalid Date even though it's not invoked
Reproduction
First of all thank you for sharing your job,
The text "LastUpdate at : " is always rendered even though i dont use the property.
You can reproduce the problem with the code of this repo => https://github.com/slozano54/sveltepressTests
and temporarily in live => https://sandboxlaravel.webfac.fr/pv.html
The code of the +page.md is :
---
title: PetitVert
---
## some subtitle
some text

I can use the property but if i don't i would like the text "Last update at : ..." was not rendered, actualy i get "Last update at : Invalid Date"
Curiously, it seems to be the expected behavior as i can see in your component  here

Logs
No response
Screenshots
No response
Severity
annoyance

It is wirtten in the docs:
https://sveltepress.site/guide/default-theme/frontmatter/#lastUpdate
lastUpdate would auto use the git commit date of the +page file
If you don't want to use it. You can config lastUpdate frontmatter to false:
---
title: Your title
lastUpdate: false
---

Sorry about the noise !
The screenshot was online but infact the github url wasn't updated, I left "https://github.com/Blackman99/sveltepress" , so confused ! As soon as I changed the url in the vite.config.ts file, the date was rendered correctly.
Thanks and sorry for you wasted time


Add utils module for initial conditions and other things

PR moves initial conditions to new Utils module. Also reorganizes regression tests so that they can be called individually. Also condenses integration and regression tests into one section to speed up testing.

bors try

bors r+


travis: elasticsearch v5 support

@lnielsen FYI, I pushed a fix for the failing builds (the bulk index queue needed to be initialized before sending records for bulk indexing)


Screen space quad doesn't render

When I open Shadered, I remove cube and add ScreenQuad.
I change pixel shader to output red:
#version 330

in vec4 color;
out vec4 outColor;

void main() {
   outColor = vec4(1.0f, 0.0f, 0, 1.0f);
}

but preview is black. If I add any other geometry, it renders fine(red). I checked that ScreenQuad position is 0,0,0 and scale is 1.0, 1.0, 1.0. What am I missing? I found 2dexample.zip  and screenquad works fine there.
Thanks!

You have to use orthographic matrix instead of projection matrix when using ScreenQuad.


Fixed FAQ section

Hello @codervivek5 ,
I have fixed the issue regarding the FAQ section.
Here is the Video :
Screencast from 04-07-23 12:21:03 AM IST.webm

@codervivek5

kindly mention Issue number

#553


Workflow panic to fail decision task

undo activity panic .
panic to timeout decision task.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


ReadMe files

@okonor ReadMe file contains a copy-paste from another repo: "InteractiveSideMenu is available under the Apache License, Version 2.0. See the LICENSE file for more info."

Thanks Alex,
Fixed.


Provide a temporary implementation for array_api.compat.torch.unique_all instead of raising NotImplementedError

The first snippet provided in this comment https://github.com/pytorch/pytorch/issues/36748#issuecomment-1474368922 might help smooth support for torch in Array API consuming libraries such as scikit-learn without them having to maintain their own hacks while waiting upstream PyTorch to address https://github.com/pytorch/pytorch/issues/70920.

This sounds reasonable. Based on the code comments, the workarounds there didn't work because they used non-deterministic scatter. But if those workarounds you referenced don't have that issue, we can implement them.


Increasing IMU noise does not destabilize the controller

I took the example case and added a copy of the given IMU with 100x the given noise, initial bias and random walk set at 1 on all axis. The simulation did not change a single bit, although the drone should have been completely destabilized.
I applied the parameters in the init function:
    def __init__(self, accelerometer_params={'initial_bias': np.array([1., 1., 1.]), # m/s^2
                                             'noise_density': ((0.38*100)**2)*np.ones(3,), # m/s^2 / sqrt(Hz)
                                             'random_walk': np.ones(3,) # m/s^2 * sqrt(Hz)
                                             },
                gyroscope_params={'initial_bias': np.array([1.,1.,1.]), # m/s^2
                                  'noise_density': ((0.01*100)**2)*np.ones(3,), # rad/s / sqrt(Hz)
                                  'random_walk': np.ones(3,) # rad/s * sqrt(Hz)
                                  },
                R_BS = np.eye(3),
                p_BS = np.zeros(3,),
                sampling_rate=500,
                gravity_vector=np.array([0,0,-9.81])):

This signalizes that something is seriously off in the way the simulation works.

Hi @sebreens, thank you for bringing this to my attention. The reason this does not affect the controller is that the current controller implementation does not actually use the IMU measurements for operation. The original purpose of the IMU measurement was to be for state estimation purposes or studying lumped parameter models of aerodynamic drag.
You can see what information is used by the included controller in quadrotor_control.py. It uses direct observations of the full state (position, velocity, attitude) to produce actions, which abstracts away the attitude estimate you might get from the IMU.
If you want to implement a controller that uses information from the IMU, you'll need to create a new controller object. You can start with a template like this.
The key difference is that you'll need to supply the controller with the IMU measurement, which will require modifying simulate() to make sure the simulator passes this information to the controller. If you develop such implementation, feel free to submit a pull request to merge it to the main branch.
I'm reworking simulate() to be more flexible for different controllers but haven't had the time to make serious progress, so anything you can contribute would be valuable.


Landingpage

https://festive-davinci-741c16.netlify.com/?x=8&y=15
here is the link

landing page

https://optimistic-wing-754495.netlify.com/
fixed the problem
working now

@arnav181104  Hey, if you are going to continue doing this task, I'd advise you to fix the prettier style violation and put indentation spaces between parent and child tags


rxjs version 6 compatibility

I guess angular2-redux is not compatible with angular v6
Is this correct?

Correct. I got a note from someone who is going to upgrade it soon.

Version 5.0.5 should fix this. Thanks to @Greentea1204 for that.


Updated limit0 views queries to use different view names so they won'…

…t clash with original views suite
Hi Chun,
Can you please review.
Thanks,
Krystal

some of the files with extension .orig meant to be deleted, right? if yes, use git rm to delete them. other than that, LGTM. +1

Ah, I removed them from the plan folder but forgot to remove them from data folder.  I'll remove them in the next commit. These files are harmless.
Thanks,
Krystal


Request explanation about two permissions

I don't understand these permissions.
Why your app should installing apps "without user interaction" ?

About it I haven't nothing against the app store "competition" for an update.

Well. Let's assume you have an App foo (appid is com.example.foo). This app is available as flavour left in Accrescent (versionCode 25) and flavour right on IzzyOnDroid (from GitHub Release) with versionCode 1025 and same signing key. You install this app from Accrescent. Then version 26/1026 gets release and your f-droid client wins the "competition" (the update is successful because it is a higher versionCode and has the same appid with same signing key). Now 27/1027 gets releases. A new feature added a huge dependency and it is now to big for IzzyOnDroid repo so it gets removed from there. Then 28/1028 gets releases which fixes an critical vulnerability. You won't get this update.

Of course you can reinstall (if the app provides export/import feature). But how do you notice that you have to do this?
Summary (from me):  A "primary source" for an app avoids some trouble.
And manual switching is always possible.


Avoid apt/dpkg lock contention

Occasionally, on a fresh install, the auto-updater and Ansible will run at the same time and trip over each other. Perhaps there's a way to avoid this.

Can we do this with a delay and retries? That's not really avoidance but rather just working around the issue. Not sure what other options may exist

Tracking upstream: https://github.com/linuxmint/mintupdate/issues/552
https://forums.linuxmint.com/viewtopic.php?t=296589

This has been abandoned upstream, so I don't see much chance of making progress.

Ugh I mean as long as we don't expect many more Tessa installs before we release Tina, I guess accepting the upstream decision is probably best.
If we expect any installs, we should release some documentation.


Missing main label in conda-forge for 2018.12.12

The current package (as of #4) isn't labelled with main (see https://anaconda.org/conda-forge/lammps/files). Is this intentional? This means that when I run conda search -c conda-forge lammps, I only see the old packages:
(dev):~ dwhs$ conda search --override -c conda-forge lammps
Loading channels: done
# Name                  Version           Build  Channel
lammps               2018.03.16         mpich_0  conda-forge
lammps               2018.03.16       openmpi_0  conda-forge
lammps               2018.03.16    py27_mpich_0  conda-forge
lammps               2018.03.16  py27_openmpi_0  conda-forge
lammps               2018.03.16    py35_mpich_0  conda-forge
lammps               2018.03.16  py35_openmpi_0  conda-forge
lammps               2018.03.16    py36_mpich_0  conda-forge
lammps               2018.03.16  py36_openmpi_0  conda-forge

I'll see the new packages if I look in the gcc7 label:
(dev):~ dwhs$ conda search --override -c conda-forge/label/gcc7 lammps
Loading channels: done
# Name                  Version           Build  Channel
lammps               2018.12.12    py27_mpich_0  conda-forge/label/gcc7
lammps               2018.12.12    py36_mpich_0  conda-forge/label/gcc7
lammps               2018.12.12    py37_mpich_0  conda-forge/label/gcc7

Workaround: The following installation should work:
conda install -c conda-forge/label/gcc7 lammps

(However, after doing that I have the same problem as #2)

@dwhswenson - Thanks for testing.
I have to admit I am still learning about the conda-forge build system and in particular the pinning of mpi. I opened another pull request to move the gcc version to the main label https://github.com/conda-forge/lammps-feedstock/pull/6 as @scopatz pointed out that toolchain is no longer the main compiler and using gcc instead is fine https://github.com/conda-forge/conda-forge.github.io/issues/699 .
I still have to figure out why the library version for Mac Os is not copied.

Seems like an issue with the lammps copying not being operation system independent:
https://github.com/lammps/lammps/blob/master/python/install.py#L39 - but we should be able to patch that.

The main label is added and the Mac Os libraries are now also included, so I am going to close this issue.


Weblogs

Add a new weblog service to omg.lol.

😊

@zsoltsandor Sorry for the confusion — my hasty issue description didn’t do a very good job of explaining what I’m working on. I’m actually building a new (very basic) weblog service tied to omg.lol that will live at weblog.lol. 🎉

@newbold free to close this?

Heh, I guess so!

rude


When there is an index.html in the root, the backend loads it.

Winter CMS Build
1.1
PHP Version
7.4
Database engine
MySQL/MariaDB
Plugins installed
No response
Issue description
I just installed a totally new WinterCMS via the Web-Installer on a Hetzner Wehost server for a client.
The webspace initially only had an index.html file in its root (A "Welcome, this webspace is under construction"-like).
Now after going through the whole installatin process, the packend shows me said index.html in the main window part of the Winter CMS backend.
I can see the whole backend top menu but when i click on dashboard, the page loaded beneath the menu is the index.html from the webhost.
When i click on "CMS", the side panel with Pages, Partials, Layouts etc. appears, but to its right i get the index.html
Steps to replicate

Create an index.html with whatever content you want and put it into your root.
Upload the Winter CMS web installer index.php and its sub folder to the root.
Install Winter CMS
After finishing go to the backend and log in
You should see your index.html in the main window of the admin backend.

Workaround
I simply deleted the index.html and everything works fine.

That's very bizarre, sounds like a server configuration issue that prefers index.html over index.php. Will close for now but if anyone can reproduce it on other hosts / environments feel free to ping me

The web server would do this by the host's configuration. I has nothing to do with Winter's backend.


Better user experience on tablet/phone

Looks terrible. Unresponsive. etc.

Ok, made an attempt at it.
With bootstrap it's mostly just
<meta name="viewport" content="width=device-width, initial-scale=1">

Some logic needed to deal with the YT iframe and roomday grid. Don't have a tablet to test with, but phone experience feels acceptable....
https://github.com/socallinuxexpo/scale-av-cutter/commit/5fc1ce284ea50547e2c1c5ee25169d6cd6a7e95a


wasmi_wasi cannot be built on Windows

Thanks for #563 solving the problem, but a degraded wiggle introduces an old cap-primitives, which introduces more problems:
error[E0277]: the trait bound `file_type::FileType: std::sealed::Sealed` is not satisfied
   --> C:\Users\Straw\.cargo\registry\src\github.com-1ecc6299db9ec823\cap-primitives-0.25.3\src\fs\file_type.rs:134:6
    |
134 | impl std::os::windows::fs::FileTypeExt for FileType {
    |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `std::sealed::Sealed` is not implemented for `file_type::FileType`
    |
    = help: the following other types implement trait `std::sealed::Sealed`:
              Child
              Command
              ExitCode
              ExitStatus
              ExitStatusError
              File
              OsStr
              OsString
            and 11 others
note: required by a bound in `std::os::windows::fs::FileTypeExt`
   --> D:\Straw\.rustup\toolchains\nightly-x86_64-pc-windows-msvc\lib/rustlib/src/rust\library\std\src\os\windows\fs.rs:507:24
    |
507 | pub trait FileTypeExt: Sealed {
    |                        ^^^^^^ required by this bound in `std::os::windows::fs::FileTypeExt`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `cap-primitives` due to previous error

This WASI support is slowly turning into a can of worms ... :upside_down_face:

Can you give instructions on how to replicate this? I am a bit confused since our GitHub Actions CI did not report this Windows build issue even though we test our workspace on Linux, MacOS and Windows.

It seems like a change on rust 1.65.
https://github.com/rust-lang/rust/commit/a4cb0b90c049fd8bc6a4a13edad69d34b98627f0
The FileTypeExt is marked as Sealed to make 3rd-party types cannot impl it.

Thanks for the info. Still strange, I was under the impression that our CI was using the current stable versions of Rust which should be 1.65 at the moment.

Well, currently I'm using nightly, but as the commit is marked as 1.65, I think the stable should report the same error...

Ah look what I found:
Windows (Sealed): https://doc.rust-lang.org/std/os/windows/fs/trait.FileTypeExt.html
WASI (not Sealed): https://doc.rust-lang.org/std/os/wasi/fs/trait.FileTypeExt.html
So maybe you need to compile for WASI target which makes sense imo.

Well, currently I'm using nightly, but as the commit is marked as 1.65, I think the stable should report the same error...

Can you try using stable and see if the problem still persists?

Can you try using stable and see if the problem still persists?

I see. The stable toolchain compiles with no error. Maybe it is still a nightly-specific issue.

This issue has been solved in recent versions, but I don't think they will fix for an old version:)

This issue has been solved in cap-primitives 1.0, but wiggle 1.0 depends on cap-primitive 0.25. Now the Wasmtime team is developing wiggle 2.x, and I don't think they will fix this issue for 1.0 releases.

One could this ask nicely. :blush: