Where I can find the glTF Metallic Roughness node of Blender?

In the data of KhronosGroup/glTF-Blender-Exporter,
It's link the glTF Metallic Roughness node & glTF Specular Glossiness node,
but I can't find these nodes to link,
So...Can anyone help me?

In your master scene, just use File > Link, and go to the gltf blend file you want, for example C:\Users\USERNAME\Documents\GitHub\glTF-Blender-Exporter\pbr_node\glTF2_Principled.blend\Material\ or C:\Users\AXEON\Documents\GitHub\glTF-Blender-Exporter\pbr_node\glTF2_Principled.blend\NodeTree\, that's it.
Personnaly, I prefer link or append the material instead of the node group, more convenient to use.

I think this issue can be closed isn'it?

Thanks @Vinc3r.


Error Duplication declaration "ViewPropTypes" at Touchable.js

import {   ViewPropTypes,   TouchableOpacity,   TouchableNativeFeedback,   ViewPropTypes } from 'react-native';

Hi! Why was this closed? I have same issue too.

Hi,  Please view pull request #14


Run book has wrong password

While Creation :
alter system set vector_memory_size=512M scope=spfile;
alter session set container=FREEPDB1;
CREATE USER "WALKTHROUGH" IDENTIFIED BY OrA_41_M_SANDBOX
DEFAULT TABLESPACE "USERS"
TEMPORARY TABLESPACE "TEMP";
GRANT "DB_DEVELOPER_ROLE" TO "WALKTHROUGH";
ALTER USER "WALKTHROUGH" DEFAULT ROLE ALL;
ALTER USER "WALKTHROUGH" QUOTA UNLIMITED ON USERS;
EXIT;
While logging :
Enter the Database Username: WALKTHROUGH
Enter the Database Password for WALKTHROUGH: ORA_41_M_SANDBOX
Enter the Database Connection String: //localhost:1521/FREEPDB1
Save
podman exec -it oaim-db sqlplus 'WALKTHROUGH/ORA_41_M_SANDBOX@FREEPDB1'
Please make sure passwords are consistent throughout

ref : https://oracle-samples.github.io/oaim-sandbox/walkthrough/index.html


Missing main entrypoint can confuse linting

The package.json is missing a main entrypoint that points to dist/index.js. Doesn't seem to affect general ESM imports but custom eslint configs can't parse the modules correctly without it. Any particular reason for it's omission?

Hey @TerryMooreII , thanks for the quick action on this. Any idea/word of when to expect a release?

btw, adding main to package.json fixes #17


Problem with mapping of Primary Title

I expected to see:
Untitled (See America First XI)
but instead I saw:
[no title]
The current query was:
PREFIX owl: <http://www.w3.org/2002/07/owl#>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX crm: <http://www.cidoc-crm.org/cidoc-crm/>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
PREFIX foaf: <http://xmlns.com/foaf/0.1/>
PREFIX dct: <http://purl.org/dc/terms/>
PREFIX dc: <http://purl.org/dc/elements/1.1/>
PREFIX schema: <http://schema.org/>

SELECT ?primary_title_text ?primary_title_class ?primary_title_id ?primary_title_id_class
WHERE {
<http://data.americanartcollaborative.org/npg/object/49748> a crm:E22_Man-Made_Object ;
  crm:P102_has_title ?primary_title_class .
?primary_title_class a crm:E35_Title ;
  rdf:value ?primary_title_text ;
  crm:P2_has_type <http://vocab.getty.edu/aat/300404670> .
OPTIONAL {
  ?primary_title_class crm:P1_is_identified_by ?primary_title_id_class.
  ?primary_title_id_class a crm:E42_Identifier;
    crm:P2_has_type <http://vocab.getty.edu/aat/300404012> ;
    rdf:value ?primary_title_id .
}

}

Hi @KatherineMoloney, awesome work on proofing these objects! I am going to close issues 67-70 and leave issue 71 as a generalized example of the problem that is indeed affecting many object instances. Save yourself the extra headache! Posting one example of an issue is easier for all, rather than re-posting the issue each time it repeats on an object.

Here are URIs to objects missing titles in the review.americanartcollaborative.org tool.
http://data.americanartcollaborative.org/acm/object/090_lc_s59 -- has credit line and homepage only
http://data.americanartcollaborative.org/acm/object/015_lc_s611 --has credit line and homepage only
http://data.americanartcollaborative.org/acm/object/011_lc_s68
I can't find these objects in the source data, but I'm asking for someone to corroborate that I didn't just miss them. The first two have some minimal data about them, so they must exist somewhere?
I'm stumped :(

@caknoblock: can you help figure out where these are coming from?


Add files via upload

@PelegBN gmail.com does not belong to a university, nor a college. I have to close the request without merging. Please ensure you are familiar with this repository rules located at the bottom of this page before submitting a new request. Thank you for the understanding!


Closes #155 - Adds Social Topbar with Icons & Dropdown Menus

Closes #155
PS: Please update preview image if needed (best i could provide)

@IamManchanda Great job with this! I should have mentioned this in the Issue but can this BB include a responsive menu on small?

Ohk will do it!  @canterberrie

@canterberrie i added responsive top bar ... but its not working as expected as it currently have a bug with flexbox
I partially fixed this ... thanks to https://github.com/zurb/foundation-sites/issues/9871
but this doesn't work as expected in mobile
Here is the issue ( top bar right is hidden )
=> https://i.imgur.com/iP9qFzV.png
cc / @rafibomb @kball

@IamManchanda That's odd! I can check it out from your branch and see the issue - I've wanted to refactor topbar for flexbox anyways so I'll see what up with this issue

Ohk @rafibomb ... assigned you with the orignal thread! Hope that's ohk

@IamManchanda Looking into this - there is a lot of Sass nesting (4-5 levels deep) It would be best to flatten this out after I figure out the flex issue.
This raises a question for @kball If we hotpatch a Builiding Blocks to cover up a Foundation bug,
A. should we?
B. if we do, how do we go back and update it after?
C. How are Building Block version maintained? Will we test them on each new release?

Ok - decision is that yes we should hotfix the Building Blocks so it supports the older version for which the fix is intended. It would not require updating then (unless there was a breaking change).
It would be best to test these BB's on each release - alt least anything has migrations.

Ohk great @rafibomb .... anything do i need to do here ??


Allow testcontainer to wait for a specific port

Motivation
A container might expose multiple ports for different purposes. for example, it can have a port for http endpoint,
while having another port for grpc endpoint. So when doing a liveness check, it would be better to allow configuring
checking a specific port, rather than checking the first exposed port.
Modification
Modify the HttpWaitStrategy to allow configuring the liveness port.

@sijie merged, thanks! 👍

thank you @bsideup


Podscribe destination docs

Proposed changes
Podscribe destination docs
Merge timing
once approved

@pitronalldak - I'm re-opening this as PR #5668 so that we have edit access


Getting opentracing: Invalid Inject/Extract carrier error when serializing spanContext

When I am trying to serialize the spanContext to wire based on the example I am getting this opentracing: Invalid Inject/Extract carrier error

@yolossn , how did you resolve it?

Hey, I don't remember the exact solution also I don't have access to the workaround which we used. From what I remember this go-amqp is outdated and using the opentracing-go client to propagate the trace info in amqp headers was the workaround.
Also, I would suggest having a look at opentelemetry

Hey, I don't remember the exact solution also I don't have access to the workaround which we used. From what I remember this go-amqp is outdated and using the opentracing-go client to propagate the trace info in amqp headers was the workaround.
Also, I would suggest having a look at opentelemetry


pod failed: open /var/lib/docker/image/overlay2/layerdb/mounts/containerd://.../mount-id: no such file or directory

I am trying to run kubectl flame on a new k8s cluster and it fails to launch
% kubectl flame `kubectl get pods -n dev-load| grep sharding | awk '{print $1}'` -n=dev-load -t 10s -f ./flamegraph.svg --lang java
Verifying target pod ... ✔
Launching profiler ... ❌
2022/01/12 12:32:20 pod failed

% kubectl version

Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T21:16:14Z", GoVersion:"go1.16.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.5", GitCommit:"5c99e2ac2ff9a3c549d9ca665e7bc05a3e18f07e", GitTreeState:"clean", BuildDate:"2021-12-16T08:32:32Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}

flame pod contains error message like this:
{"type":"progress","data":{"time":"2022-01-12T10:32:43.529897521Z","stage":"started"}}
{"type":"error","data":{"reason":"open /var/lib/docker/image/overlay2/layerdb/mounts/containerd://166013c88125d0123a7d957165e87ca0d3cb28ee6c42327d8b905e1c8796e58c/mount-id: no such file or directory"}}

everything works just fine with older versions of k8s
% kubectl flame `kubectl get pods -n jenkins| grep hub-list | awk '{print $1}'` -n=jenkins -t 10s -f ./flamegraph.svg --lang java
Verifying target pod ... ✔
Launching profiler ... ✔
Profiling ... ✔
FlameGraph saved to: ./flamegraph.svg 🔥
√
% kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T21:16:14Z", GoVersion:"go1.16.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.4", GitCommit:"3cce4a82b44f032d0cd1a1790e6d2f5a55d20aae", GitTreeState:"clean", BuildDate:"2021-08-11T18:10:22Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"linux/amd64"}

% kubectl flame `kubectl get pods -n solid| grep sharding | awk '{print $1}'` -n=solid -t 10s -f ./flamegraph.svg --lang java
Verifying target pod ... ✔
Launching profiler ... ✔
Profiling ... ✔
FlameGraph saved to: ./flamegraph.svg 🔥
√
% kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T21:16:14Z", GoVersion:"go1.16.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.3", GitCommit:"b3cbbae08ec52a7fc73d334838e18d17e8512749", GitTreeState:"clean", BuildDate:"2019-11-13T11:13:49Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

QUESTION:
Is there a workaround or some special security or filesystem settings in k8s cluster I need to check?

Looks like your new cluster uses containerd, not docker.

@azlev yes, you are right, have just checked - new cluster uses containerd runtime, old ones use docker.
Are there any plans to adjust flame plugin for containerd or it will be impossible to use flame on newer k8s versions?

+1

+1
Any plans to support containerd soon, as containerd will be the default runtime in k8s moving forward, making this tool impossible to leverage.

Any updates on this issue?  As containerd becomes the default runtime, this makes this issue critical for this project.

+1

+1

Any updates on this issue?


New version: Ryujinx.Ryujinx.Ava version 1.1.1160

Pull request has been created with komac v2.0.3 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

No errors to post.

(Automated response - build 695.)

@wingetbot waivers Add Validation-Executable-Error

@wingetbot waivers Add Validation-Executable-Error


React apexcharts not allow to set borderRadius on both sides of bar (timeline chart, type:rangeBar)

Summary
It needs to be borderRadius for both sides on rangeBar
"apexcharts": "^3.29.0", "react-apexcharts": "^1.3.9",
When i'm trying to set border radius, it works only on one side
plotOptions: {         bar: {           horizontal: true,           borderRadius: 4,         },       }
Result:

你可以使用数组替代字符串，就可以解决这个问题
you could use Array instead of String, like this:
borderRadius: [8, 8]

Thanks for your comment, @nanhaibo. Using an array didn't seem to work for me. Still only the ends of the timeline bars are rounded. Not the beginning. Any suggestions are highly appreciated.

Hi ,
I want border radius top bar and bottom bar radius with that in Apex chart .how i am found that? Please tell me

This is still not resolved, any sugggestions?

@jellederijke hey, were you able to figure it out?


Improving "Go to definition" in GDScript

I would bet this would has been asked already, but I cannot find an issue about this.
It would be a great time saver if we could go to the definition of something in GDScript with a right-click menu + a shortcut.

On a file name: open the file
On a class name: jump to the position in that file where the class is
On a function, var or const: jump to the thing, or open the file and go where the thing is defined
On an API element: open the docs
If all else fails... open global find :)

All this, of course, using the existing information the editor has / can get when parsing the file.
I've surprised myself too many times trying to right-click on something to "go to definition", noticing it's not there, and trying to remember where the thing is and open files manually and scroll :p
I apologize if this has been asked already but I can't find an existing issue :s
Edit: I renamed the issue since this already exists and supports some of the features

Have you tried Ctrl+Click? Doesn't work very well, but it's a problem with GDScript inference in general.

Hmm it doesn't works in 2.1, even on obvious cases, is this a recent feature?

Yes, it's relatively recent.

It was introduced in September: 37f1e86

Oh, that's great :)
Indeed it is limited to what the parser can infer (which could be improved). It doesn't open filenames though :3

First of all thank you for your report and sorry for the delay.
We released Godot 3.0 in January 2018 after 18 months of work, fixing many old issues either directly, or by obsoleting/replacing the features they were referring to.
We still have hundreds of issues whose relevance/reproducibility needs to be checked against the current stable version, and that's where you can help us.
Could you check if the issue that you described initially is still relevant/reproducible in Godot 3.0 or any newer version, and comment about it here?
For bug reports, please also make sure that the issue contains detailed steps to reproduce the bug and, if possible, a zipped project that can be used to reproduce it right away. This greatly speeds up debugging and bugfixing tasks for our contributors.
Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.
Thanks in advance.
Note: This message is being copy-pasted to many "stale" issues (90+ days without activity). It might happen that it is not meaningful for this specific issue or appears oblivious of the issue's context, if so please comment to notify the Bugsquad about it.

Ctrl+click in Godot 3.0.2:

On a file name: open the file:
it works, except when the path is relative. For example, on a preload("thing.gd"), the editor will fail opening it. A fix would be to take the path of the current script into account.

On a class name: jump to the position in that file where the class is:
Doesn't work on nested classes (declared with class keyword).
If the class has been "imported" with const Thing = preload("thing.gd"), the cursor will jump to the import, but maybe it would be better to jump to thing.gd directly if the import can be resolved statically (like it's the case with const preloads).

On a function, var or const: jump to the thing, or open the file and go where the thing is defined
Works on member vars,
Works on member functions,
Doesn't work on static functions,
Doesn't work on static functions that are imported using const preload (which can be resolved statically)

On an API element: open the docs
Works on classes,
Doesn't work on class constants (but should be partly fixed by https://github.com/godotengine/godot/pull/17865)

If all else fails... open global find :)
Would need this https://github.com/godotengine/godot/pull/16571

I think the situation is already a bit better in the current master branch, but some of the above mentioned issues might still be relevant.

Some of those issues are apparently fixed by #31843, it would be good to review this issue and see what is still relevant.

Some update:

On a file name: open the file:
it works, except when the path is relative

The problem is that relative paths aren't even recognized as paths. IMO it's fine that it supports only "res://", I don't remember using non-res:// paths ever (or at least since I discovered filename drag and drop).

If the class has been "imported" with const Thing = preload("thing.gd"), the cursor will jump to the import,

Only in this case:
var b = THE_SCIRPT.new()

Here it won't jump:
var a: THE_SCIRPT

Doesn't work well on class constants

This is fixed now.
I think it would be better to make a tracker listing each case, because it's a bit chaotic here.

So as I said in previous comment, this issue is very old and confusing, so closing it in favor of #33898


Documentation could acknowledge that it's OK to use this in conjunction with shelljs

I get why you'd not use this in production in a traditional node server app, but a production shell script replacement is another story. Folks use shelljs synchronously all the time in those, and are probably even using it to invoke curl for lack of this module (: It might be worth mentioning in the README's warning that it's acceptable in that context.

(Thanks for the module!)

Perhaps you could submit a pull request with a proposed clarification. The wording in the readme is as forceful as it is because I know a large number of people do abuse this module by using it directly in production node.js apps.


Improved JWT handling, validation and error messages

Closes #54
Notable general changes:

Community conventions suggest using uppercase for acronyms, so what we would've called Rig.Jwt is called RIG.JWT instead. I've adopted the convention here, but I'm open to discuss it of course. If we decide to go with it, I'll update the rest of the code base in another PR.
There is a new Result module (on purpose not scoped to RIG), meant to be used all over the code base when handling ok/error tuples. We deal with such tuples all the time and I felt it would be nice to have a library like that. It's almost a re-implementation of Rust's Result type, in case you're familiar with it. I hope it will make a lot of our code easier to write and understand.
I've disabled a Credo check 'cause I think it's nuts.
I've broken with the configuration style. Somehow, it made more sense to me to not scope the variable to a specific module, but, again, I'm open to discussion.
Rig.Subscription should go into the subscriptions folder, but so should some (most?) of the subscription related code in RigInboundGateway. This is something I'd like to do in a dedicated PR.

As for websockets, this works
via create subscription call: examples/ws-demo-jwt-extractors.html
this doesn't:
via initial connection: examples/ws-demo-jwt-extractors-conn.html

Seems like these 2 examples don't work, something changed?
## basic public SSE with constraints & JWT

via create subscription call: examples/sse-demo-jwt-extractors.html
via initial connection: examples/sse-demo-jwt-extractors-conn.html

examples/jwt-extractor.json

```bash
EXTRACTORS=examples/jwt-extractor.json \
JWT_SECRET_KEY=secret \
mix phx.server

Hi @mmacai : It seems like the example don't work in master as well... Doesn't like this is an issue related to this PR

Hmm strange, then we should create separate issue for that and this one should be fine.


Incompatible with Epic Fight Mod

The armor appears to be heavily deformed possible due to the custom animations from EFM, while I did just only showed the soul hood and armor items, most of the armors seem to be experiencing the same problem

Patched Dungeon Gear mod here: https://www.planetminecraft.com/data-pack/epic-fight-dungeon-gear-patch/


Autodetect failed installation and recover from it

There are instances where csharpier is partially installed and if fails to run. This is the output from VSCode
["WARN" - 5:05:10 PM] Exception while running 'dotnet csharpier --version' in C:\Users\<WITHHELD>\AppData\Local\CSharpier\0.20.0
"Cannot use file stream for [C:\\Users\\<WITHHELD>\\AppData\\Local\\CSharpier\\0.20.0\\.store\\csharpier\\0.20.0\\csharpier\\0.20.0\\tools\\net6.0\\any\\dotnet-csharpier.deps.json]: No such file or directory\r\nA fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in 'C:\\Program Files\\dotnet\\'.\r\nFailed to run as a self-contained app.\r\n  - The application was run as a self-contained app because 'C:\\Users\\<WITHHELD>\\AppData\\Local\\CSharpier\\0.20.0\\.store\\csharpier\\0.20.0\\csharpier\\0.20.0\\tools\\net6.0\\any\\dotnet-csharpier.runtimeconfig.json' was not found.\r\n  - If this should be a framework-dependent app, add the 'C:\\Users\\<WITHHELD>\\AppData\\Local\\CSharpier\\0.20.0\\.store\\csharpier\\0.20.0\\csharpier\\0.20.0\\tools\\net6.0\\any\\dotnet-csharpier.runtimeconfig.json' file and specify the appropriate framework.\r\n"
["ERROR" - 5:05:10 PM] ,,Tool 'csharpier' is already installed.

["DEBUG" - 5:05:10 PM] returning NullCSharpierProcess because of the previous error when trying to set up a csharpier process

The extensions install csharpier to a custom directory because they keep the dotnet tool running in the background. If they kept csharpier running from the default location then a user will run into issues if they run commands to update csharpier.
Testing the install can be done with the following command
C:\Users\[USER]\AppData\Local\CSharpier\[Version]\dotnet-csharpier --version`

Deleting that directory and restarting VSCode would get the extension to reinstall csharpier in the custom location.
It should be possible for the extensions to detect this and attempt to delete and reinstall csharpier.

I did this a while ago and forgot to close the issue


using stateful set for data

this is an example of using stateful set for the data volumes, for reference

I'm using something very close to this version of the data node stateful set in GKE.
Using a volumeClaimTemplate with a storage-class annotation allows GKE to allocate a persistent disk associated with each pod in the set:
  volumeClaimTemplates:
  - metadata:
      name: storage
      annotations:
        volume.beta.kubernetes.io/storage-class: standard
    spec:
      accessModes: [ "ReadWriteOnce" ]
      resources:
        requests:
          storage: 12Gi

Then adding an appropriate StorageClass object tells kubernetes how to create a the disk:
kind: StorageClass
apiVersion: storage.k8s.io/v1beta1
metadata:
  name: standard
provisioner: kubernetes.io/gce-pd
parameters:
  type: pd-standard
  zone: us-west1-b

@pires I can submit a pull request if you like. How should I structure the files? Maybe under a GKE sub-directory?

@wfhartford yes, a separate folder and proper documentation would work.

Closed by #80.


Missing imageStream, improve docs

I followed instructions here: https://github.com/openshift/cakephp-ex and at step 4 I got an error:
Error from server: imageStream "php" not found
There aren't any image streams. I had to create them. Previous step should be something like:
You have to create php image stream first.
$ oc create -f /data/src/github.com/openshift/origin/examples/image-streams/image-streams-centos7.json -n openshift

not sure if your issue pre-dated the current state of the readme, but it now says this immediately before the steps:
These steps assume your OpenShift deployment has the default set of ImageStreams defined.  Instructions for installing the default ImageStreams are available [here](http://docs.openshift.org/latest/admin_guide/install/first_steps.html).  If you are defining the set of ImageStreams now, remember to pass in the proper cluster-admin credentials and to create the ImageStreams in the 'openshift' namespace.

so closing this.


Xcode8.3.3 compiler error with PromiseKit 4.4.0

PromiseKit version: 4.4.0
Xcode version: 8.3.3
CocoaPods version: 1.3.1

Promisekit 4.4.0 builds fine on Xcode9 beta6, but when building/archiving with Xcode8.3.3 I get the following error:
.../Pods/PromiseKit/Extensions/UIKit/Sources/UIViewController+AnyPromise.m:45:34: No known class method for selector 'cancelledError'

I suggest a fresh pod install as the function it cannot find is absolutely part of PromiseKit 4.4.0:
https://github.com/mxcl/PromiseKit/blob/6b18b8826ea46f970d4c580614c492cb30a3f314/Sources/Error.swift#L110-L113

Notably this is a function that the compiler generates the header for, so it seems like the compiler failed to generate the header.

So I would clean and try again.
Like always, if you don't actually use any of PromiseKit’s UIKit extensions then you can remove them from your Podfile:
pod 'PromiseKit', subspecs: ['CorePromise']

i had to clean out my derived data, etc.. and then it all worked fine thx @mxcl


add spin 3 interfaces and bump version number

This PR does a few things:

Adds the Spin 3 postgres interface along with bindings
Adds wasi-kv and wasi-runtime-config to the wit definition so that user can import it directly. For importing the get method in the config interface, one can do - import { get } from<EMAIL_ADDRESS>This PR also bumps ComponentizeJS to allow for multi package single file wit definitions.
Also bumps knitwit to the latest release.
Bumps to an RC version.

What this PR does not do:

update the templates so as to disturb users until a stable release is done.

I assume you're looking into the linter  and tests failing.

Yep @radu-matei , the knitwit release is broken and I have opened a PR to fix that.

Okay the tests have been fixed, The templates needed fixing as they were pointing at a git reference that did not have the build artifacts. I will retag the templates for 2.7 once this PR is merged. cc: @radu-matei


Use Dask to run the cell simulations in parallel

This isn't really an issue but more of a feature request or enhancement. Would it be possible to use Dask to run the cell simulations in parallel? I created a basic example (see below) of running the SPMe model for several discharges in parallel using Dask. Compare elapsed time with and without Dask by commenting out the appropriate section in main(). Elapsed times are given in the table below when running on an 8-core CPU.
Dask is made for massive parallelization and it's fairly easy to setup for CPU and GPU clusters. If it can be used with liionpack then it could provide a huge performance boost for large pack simulations. I haven't tried Casadi's parallel features beyond running on a single CPU but I don't think it will be easy to scale compared to using Dask.

Example
Elapsed time

No Dask
8.57 seconds

Dask
3.83 seconds

import matplotlib.pyplot as plt
import pybamm
import time
from dask.distributed import Client

def generate_plots(discharge, t, capacity, current, voltage):

    def styleplot(ax):
        ax.legend(loc='best')
        ax.grid(color='0.9')
        ax.set_frame_on(False)
        ax.tick_params(color='0.9')

    _, ax = plt.subplots(tight_layout=True)
    for i in range(len(discharge)):
        ax.plot(t[i], current[i], label=f'{discharge[i]} A')
    ax.set_xlabel('Time [s]')
    ax.set_ylabel('Current [A]')
    styleplot(ax)

    _, ax = plt.subplots(tight_layout=True)
    for i in range(len(discharge)):
        ax.plot(t[i], voltage[i], label=f'{discharge[i]} A')
    ax.set_xlabel('Time [s]')
    ax.set_ylabel('Terminal voltage [V]')
    styleplot(ax)

    _, ax = plt.subplots(tight_layout=True)
    for i in range(len(discharge)):
        ax.plot(capacity[i], voltage[i], label=f'{discharge[i]} A')
    ax.set_xlabel('Discharge capacity [Ah]')
    ax.set_ylabel('Terminal voltage [V]')
    styleplot(ax)

    plt.show()

def run_simulation(dis, t_eval):

    model = pybamm.lithium_ion.SPMe()

    param = model.default_parameter_values
    param['Current function [A]'] = '[input]'

    sim = pybamm.Simulation(model, parameter_values=param)
    sim.solve(t_eval, inputs={'Current function [A]': dis})

    return sim.solution

def main(client):
    tic = time.perf_counter()

    discharge = [4, 3.5, 3, 2.5, 2, 1.8, 1.5, 1]  # discharge currents [A]
    t_eval = [0, 4000]                            # evaluation time [s]

    # No Dask
    # ------------------------------------------------------------------------

    # label = 'no Dask'

    # sols = []
    # for dis in discharge:
    #     sol = run_simulation(dis, t_eval)
    #     sols.append(sol)

    # Dask
    # ------------------------------------------------------------------------

    label = 'Dask'

    lazy_sols = client.map(run_simulation, discharge, t_eval=t_eval)
    sols = client.gather(lazy_sols)

    # ------------------------------------------------------------------------

    t = []
    capacity = []
    current = []
    voltage = []

    for sol in sols:
        t.append(sol['Time [s]'].entries)
        capacity.append(sol['Discharge capacity [A.h]'].entries)
        current.append(sol['Current [A]'].entries)
        voltage.append(sol["Terminal voltage [V]"].entries)

    toc = time.perf_counter()
    print(f'Elapsed time ({label}) = {toc - tic:.2f} s')

    generate_plots(discharge, t, capacity, current, voltage)

if __name__ == '__main__':
    client = Client()
    print(client)
    main(client)

@TomTranter, could you elaborate some more on data dependencies between threads. Is it because we are doing a coupled solve with thermal ? Also, what was the library you used for shared memory parallel process ? Adaptive time stepping is important and will definitely help us accelerate.

This would be a good first issue to tackle for understanding memory requirements https://github.com/pybamm-team/PyBaMM/issues/1442

The way initial conditions are handled, especially when there are input parameters in the initial conditions, is also not perfect https://github.com/pybamm-team/PyBaMM/blob/6ccce9f817db8e5df69e6a3de90587b62e20180a/pybamm/solvers/base_solver.py#L1261-L1294
This might cause some difficulties with creating a single model and solving multiple times. That part of the code could do with a fresh pair of eyes tbh

Hey so I pushed some changes and I think basically you wanna try and put as much of the code in the for loop in _serial_step into a dask process

@TomTranter Dask is complaining that some of the variable types are DM. It looks like these are types returned from Casadi. Can you edit _serial_step_dask and solve_dask so there are no Casadi objects? I don't know how to support non-standard Python objects with Dask. I'm still learning how to use it.

Apparently objects must be able to be serialized for use with Dask. This may be causing the issues I'm having with passing Casadi and PyBaMM objects to the mapped Dask function. http://distributed.dask.org/en/latest/serialization.html

I think the integrator will work is you pass numpy arrays... but I'm not sure

@TomTranter I rebased the dask branch with main so everything is up-to-date with main. If you need to work on the dask branch make sure you pull (or force pull) the latest version to your local dask branch.

I'm getting issues again - maybe as I use sourcetree but I pulled down some changes in the dask branch and it's saying I have merge conflicts
I really really would prefer it if you didn't rebase

I just did a hard reset on my local machine to fix the issue
git reset --hard origin/dask

@wigging I made a little progress on this. I added a self contained script called dask debug with the bare minimal integrator functionality getting mapped. If you look at the dashboard there is a lot of waiting with nothing happening which I guess is data transfer in between steps. Maybe turning all the states into one big dask array and indexing into it would speed things up if dask handles these things efficiently in memory. If not we can try sharedarray

I'm getting close to a Dask solution. I ran the example using Python's from concurrent.futures import ProcessPoolExecutor  and chunked arrays which is giving good speed improvements. So now I'm adapting that approach for use with Dask. To be continued...

We now have a solution in the dask PR #66 but it's slower than just running the casadi integrator. I don't know how that mapped integrator works as the docs are very patchy and you can only get so far with debug but they must be doing something clever because it's pretty instantaneous to kick off. It looked like dask actors were going to be useful and might still be but are quite experimental. The idea is to persist an actor class on a cpu process which holds it's own state variables. This is basically an array of solutions for that actors chunk of batteries. It then steps through them individually and updates the solution but only passes back the output. This is more efficient for data transfer but it means keeping a lot of data in memory. So a new actor is created for each process and I guess there's some overhead with this. It doesn't seem to scale as well as casadi (about twice as slow to step solve excluding the extra time to set up the client and instantiate the actors). There is another package called ray which does something similar but their actor functionality is a bit more developed than dask and they also talk about ways to use shared memory between processes which may speed up sending inputs and outputs about. It's hard to profile the dask actors too as all their tasks are hidden from the task stream. I will check out Ray but perhaps going forward we should think about writing our own parallel wrapper to sundials... Maybe @martinjrobins has some thoughts on how long this would take?

Keep in mind that the reason to use Dask is to be able to scale to multi-node clusters (CPUs and GPUs). Can Casadi, Ray, etc. take advantage of such hardware or are they limited to a single machine?

Ray certainly can. We need to find out how the casadi map works. No answer from them on the forum yet

Addressed in pr #66


oddgen integration (optional)

Implement the oddgen interface to support sophisticated test generation. It is similar to #10 but the oddgen integration should support file based generation (a file for each package specification and package body) and multiselection. Naming conventions may be handled through parameter settings. Finally all suite paths in a should be evaluated and presented in a tree to just run the tests based on the suite path and not only based on schema/package/procedure paths.
Implementing the oddgen interface does not have an effect if the oddgen extension is not installed. This means it is not necessary to install oddgen. However, if it is installed, oddgen will automatically detect the implementation and provide the generator in its Generators navigator tree.

In this issue two enhancements are defined:

Bulk generating utPLSQL test packages
Bulk running utPLSQL tests

In this issue I handle just the first enhancement (bulk generating).
For the second enhancement (bulk running) I open a new issue.


Why does thaliMobile.getMethodByNetworkType have a networktype argument?

We don't use the argument adn given how target works it doesn't seem like we need it. But all the calls we have to it pass in networkType.
The only reason I can think for it to be there is if it was intended as a validation check to make sure that the target is appropriate given the networktype.
Can you please clarify and either finish the code or remove the argument?

@yaronyg I agreed with you. It's a heritage of refactoring
It's fixed in #1175


edk2/OVMF: add hooks for building for IA32 on 64bit stdenv

Currently, building for IA32 via pkgsi686Linux stdenv is broken.
This nominally fixes #118985 by allowing you to specify crossIa32, which
overrides targetArch, projectDscPath, buildType.
nix-build -E 'with import <nixpkgs> {}; pkgs.OVMF.override { crossIa32 = true; }'
This also moves all the logic for targetArch, projectDscPath, and builtType
into OVMF since that is not used within edk2/default.nix itself

Motivation for this change
OVMF 32 bit does not build on 64bit nixos standard environment.s
Things done
hooked into my own system:
packageOverrides = pkgs: rec {
  edk2 = (pkgs.callPackage ./pkgs/edk2.nix {});
  OVMF = (pkgs.callPackage ./pkgs/OVMF.nix {
    util-linux = pkgs.utillinux;
  });

64 bit:
% nix-build -E 'with import <nixpkgs> {}; pkgs.OVMF'
/nix/store/ivc0c7xsqgv5sixcbslfn93gcpzxwrvw-OVMF-202011
~ talos % dir /nix/store/ivc0c7xsqgv5sixcbslfn93gcpzxwrvw-OVMF-202011
AutoGen  BuildOptions  FV  GlobalVar_5a9e7754-d81b-49ea-85ad-69eaa7b1539b_X64.bin  Ovmf.map  PcdTokenNumber  X64

64 bit stdenv on 32bit:
% nix-build -E 'with import <nixpkgs> {}; pkgs.OVMF.override { crossIa32 = true; }'
/nix/store/xcsjqddprha1ykk8v58sjbq80s1rwbwh-OVMF-202011
% dir /nix/store/xcsjqddprha1ykk8v58sjbq80s1rwbwh-OVMF-202011
AutoGen  BuildOptions  FV  GlobalVar_5a9e7754-d81b-49ea-85ad-69eaa7b1539b_IA32.bin  IA32  Ovmf.map  PcdTokenNumber

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

assert crossIa32 == false || (stdenv.isi686 || stdenv.isx86_64); could just be assert crossIa32 == false || stdenv.isx86_64; but I'll leave it for now.

I'm going to close this given its age. If the functionality hasn't been fixed in the meantime, please feel free to rebase/reopen or open a new PR.


Added option to CMakeLists.txt to disable VST plugin compilation.

This allows coders to disable the VST plugin compilation completely.

This looks good, but I don't like the double-negative - can we make a default-truthy BUILD_VST_PLUGINS variable instead? (same with #96)

Also needs conflict resolution after merging #93.

Rebased and removed double negation.

cheers!


Error when making slug field hidden

Uncaught Exception: ContextErrorException .
ContextErrorException in FieldFactory.php line 94:
contenttype.yml:
 hidefield:
        type: hidden
        fields:
            slug:
                type: slug
                uses: title_et

That construction doesn't make sense to me.
A hidden field is just:
 hidefield:
        type: hidden

and everything under fields is ignored. Unless I'm missing something?

https://docs.bolt.cm/3.3/fields/hidden

I want to hide slug filed, which type is slug

You want to hide it in the CMS? Then that's not a JSONAPI issue.
If you want to hide it from the JSONAPI output, then configure that in the configuration file jsonapi.bolt.yml:
list-fields: [ ... ]
item-fields: [ ... ]
allowed-fields: [ ... ]

See https://github.com/xiaohutai/jsonapi/blob/master/config/config.yml.dist#L7-L16

Yes I want to hide it in the CMS

If you need a hidden field, then it should be something like:
some_field:
    type: hidden

But then it won't act as a slug anymore (something that you see in the URL), which is probably not what you want.
Alternatively, you can add a custom extension that adds an asset (CSS/JavaScript) that then hides the slug field for that contenttype. See https://docs.bolt.cm/3.3/extensions/bundled/introduction for making your own extensions.
From what I understand, this is not a JSONAPI issue.


Updating springboot, graphql-java and graphql-springboot libraries

Updated all to the latest published version.
@donbeave - keen for your take :)

@setchy thank you!

@donbeave do you have a date in mind for releasing to jcenter / mavencentral?

@setchy yes, now )
Sorry, I forgot to release it before. )

@setchy released!

Awesome thank you sir

You are welcome!
Sorry for the delay.


Account Sync Notifications Icon Bubble

First of all, thank you for implementing this feature natively in VS Code.  Currently the Accounts icon, at the bottom of the left bar, displays a number inside a blue bubble over the icon that indicates the number of available services. In my mind, this is silly and should not be. The only way to make that go away would be to sync your settings over every available service, but this would make no sense. Rather, please only show a notification bubble on this icon if there is some issue with the current account being used to sync the settings. This, to me, seems a more sensible notification rather than showing one for each available unused service.

Can you share what things are in your Account list that are causing the account bubbles? They are marked with a (1) next to them.
From that list, which ones do you expect and which ones do you want to go away?

As requested:

I want all of them to go away, or at the very least permanently dismissible or hidable. This is a notification bubble, which should only be used for alerting the user to an issue or new information, and should ALWAYS be dismissible. A notification should NOT be used to merely bring attention to a static thing. They should be dynamic, not static. I don't mean to be rude, but isn't this an elementary design concept?

/extLiveShare


[Feature request] Take into account location information in paths when following them in the terminal

rustc produces error messages with paths formatted like src\librustc\ty\instance.rs:61:31. Currently I can Ctrl+Click to go to the file. It would be nice if it could also go to line 61, column 31.

Backtraces due to panics in Rust has the form .\src\librustc\infer\mod.rs:532. That should also go to line 532.

Support for this will be in 1.12. Duplicate of #21472. Fixed in #24832.


Light effect does not align with cursor when page is scrolled

After the page loads the light source is always at the tip of the cursor. However after scrolling down to the mailing list the light source seems to be off towards the top of the screen.
Is this behaviour intended?

No it's not @anoff, I'm working on this and a few other changes I'm yet to document.

The new site seems to be a narrower implementation which significantly reduces the impact of this phenomenon.


💡 Cool Cards + section Improvement

[ x] I am from GSSoC23.
[ x] I would like to be assigned this task.

fill [x] to check the boxes.

I want to create cool cards so that the ui looks catchy and attractive.
I want to work on this issue, Please assign it to me under gssoc'23

Code of Conduct
By submitting this issue, you agree to follow our Code of Conduct.

[ x] I follow the Contributing Guidelines of this project.
[ x] I have checked the current issues for duplicate problems.
[ x] I have read the readme of this repository.

Hi @akanksha984, whatever you are trying to change it should match the website theme, can you please provide a sample example how your idea would look like?

Please provide the screenshots of your design idea by making changes locally and submit the screenshots here.

ya sure

I want to add these hovers so that it looks stylish
@Alkaison

Hi @akanksha984, the images you provided are actually already under working face by another contributor. However, you can work on creating the UI design for the following image I have attached below. Let me know, if you agree with that. 🙂

Hi @akanksha984, the images you provided are actually already under working face by another contributor. However, you can work on creating the UI design for the following image I have attached below. Let me know, if you agree with that. 🙂

Hi @akanksha984, the images you provided are actually already under working face by another contributor. However, you can work on creating the UI design for the following image I have attached below. Let me know, if you agree with that. 🙂

ok sure, I have already improved it and other sections too. So should I create pr for this edit?

Hi @akanksha984, the images you provided are actually already under working face by another contributor. However, you can work on creating the UI design for the following image I have attached below. Let me know, if you agree with that. 🙂

Yes of course, also revert the changes for other edits.

https://github.com/ZeroOctave/resource-gallery/pull/236 Please check @Alkaison


chore(node): run tests against multiple package managers

This changes how lavamoat runs its tests.
To prepare the tests, test/prepare.js is run.  This invokes corepack to switch between package managers and performs a clean install and setup using each.  The package manager can be changed via environment variable.
Motivation:  After changing from Yarn to npm, we were concerned about breaking compat.  This should ease our nerves a bit!
Notes:

a new policy file was created in project 2 for atob; I'm not sure what caused this change.
corepack is seemingly broken in Node.js v14 (segfaults); if this is the case, we just try to use the system package manager

chore(core,node): add some types for scenarios and options

Current dependencies on/for this PR:

boneskull/policy-schema

PR #648   👈

This comment was auto-generated by Graphite.

Closes #625 (possibly)

@legobeat I suppose we could also add yarn berry, but I know it won't be so easy.  I would like to better understand how exactly this package is consumed by yarn berry users.

Current dependencies on/for this PR:

main

PR #629

PR #643

PR #648   👈
PR #620

PR #632
PR #631
PR #630
PR #627

PR #639
PR #617

This comment was auto-generated by Graphite.

@naugtur Please let me know if you still have concerns here.

@legobeat I'll try to separate this; I was using some of the types I made in #620.

@legobeat This now targets main

now that we're no longer supporting node 14 this should be smooth

This now targets #729 and I removed the terrible garbage I had to add for v14.


Make contract addresses in data sources optional

Resolves #616 (together with https://github.com/graphprotocol/graph-cli/pull/240).
To not leave out data sources without contract addresses in our eth_getLogs requests, we need to exclude contract addresses from the logs filter if there is even a single data source without an address. That makes the scan broader and thus less efficient but doesn't break our processing. We still have matches_log_address() checks in place to direct events to the right data sources and filter out false positives from the bloom filter.

Tested locally using our example subgraph. If you remove the contract address in the main data sources, it still indexes all the same events + 2 more from two other Gravity smart contracts.
For making extra sure that it worked, I added a contract: Bytes! field to the Gravatar type in the schema, then used gravatar.contract = event.address in handleNewGravatar to store the contract the gravatar came from. The following screenshot shows that there are two gravatars from different contracts, followed by all the gravatars from the contract that we explicitly pointed to before:

@leodasvacas I believe I've addressed all your comments.


[Question] How are each of the kprobe programs getting access to the sk_buff

I noticed in the section of the code below, that there are 5 kprobe programs and each of them are reading the sk_buff for the intercepted data from different params 1-5 respectively.
The question is, what is the significance of PT_REG_PARMx and also why do we need 5 kprobe programs?
https://github.com/cilium/pwru/blob/master/bpf/kprobe_pwru.c#L359-L392

pwru attaches to kernel functions that take a sk_buff as a parameter. Depending on which parameter hold the sk_buff, a different kprobe program needs to be used. For example, if the sk_buff is the second parameter, kprobe/skb-2 will be used since PT_REGS_PARM2 retrieves the second parameter from the CPU registers. If it's the fourth parameter, then kprobe/skb-4 is used, etc.

pwru attaches to kernel functions that take a sk_buff as a parameter. Depending on which parameter hold the sk_buff, a different kprobe program needs to be used. For example, if the sk_buff is the second parameter, kprobe/skb-2 will be used since PT_REGS_PARM2 retrieves the second parameter from the CPU registers. If it's the fourth parameter, then kprobe/skb-4 is used, etc.

Makes sense. However, I am having trouble understanding some parts of the userspace code. How do you decide what these functions are?

It extracts from the kernel BTF: https://github.com/cilium/pwru/blob/master/internal/pwru/utils.go#L15


v1.5 backports 2019-06-21 v2

Supersedes #8369. Thanks @joestringer and @aanm for crafting this backport.

#8328 -- fqdn: correctly populate Source IP and Port in notifyOnDNSMsg (@ianvernon)

Had to make minor fixups because the function was refactored out

#8350 -- CI: Report last seen error in CiliumPreFlightCheck (@raybejjani)
#8352 -- CI: Cleanup VMs and reclaim disk on job completion (@raybejjani)
#8361 -- pkg/metrics: re-register newStatusCollector function (@aanm)
#8366 -- docs: Clarify about legacy services enabled by default (@brb)
#8280 -- Add support for k8s 1.15 (@aanm)
#8351 -- Workaround for systemd 242 assigning MAC addr for virtual devices (@brb)

[ Round 2, added CI fixes]

#7911

This was partially backported before in f7a1bd149a40f237850c91baa9b6987de6c67061, so I went back and backported the other half.

#8148
#8341
#8355

Once this PR is merged, you can update the PR labels via:
$ for pr in 7911 8148 8328 8341 8350 8352 8355 8361 8366 8280 8351; do contrib/backporting/set-labels.py $pr done 1.5; done

This change is

never-tell-me-the-odds

test-me-please

test-missed-k8s

never-tell-me-the-odds

From k8s upstream tests:
https://jenkins.cilium.io/job/Cilium-PR-Kubernetes-Upstream/1355/execution/node/42/log/
18:53:33      k8s1-1.15: docker build \
18:53:33      k8s1-1.15: 	--build-arg LOCKDEBUG=1 \
18:53:33      k8s1-1.15: 	--build-arg V= \
18:53:33      k8s1-1.15: 	--build-arg LIBNETWORK_PLUGIN= \
18:53:33      k8s1-1.15: 	-t "cilium/cilium:"latest"" .
18:59:49      k8s1-1.15: Sending build context to Docker daemon  9.247GB
18:59:49      k8s1-1.15: Step 1/19 : FROM quay.io/cilium/cilium-envoy:68c49eeb8241867829c5eab4dff13a316c71c355 as cilium-envoy
18:59:49      k8s1-1.15: 68c49eeb8241867829c5eab4dff13a316c71c355: Pulling from cilium/cilium-envoy
18:59:49      k8s1-1.15: 59fc10cbb750: Pulling fs layer
18:59:49      k8s1-1.15: 59fc10cbb750: Verifying Checksum
18:59:49      k8s1-1.15: 59fc10cbb750: Download complete
18:59:49      k8s1-1.15: 59fc10cbb750: Pull complete
18:59:49      k8s1-1.15: Digest: sha256:6579ea6d0c6ab19e07e6c07f52f1633846eadd0842db06ffe335f0cfd846c9a4
18:59:49      k8s1-1.15: Status: Downloaded newer image for quay.io/cilium/cilium-envoy:68c49eeb8241867829c5eab4dff13a316c71c355
18:59:49      k8s1-1.15:  ---> d6de2e5e111c
18:59:49      k8s1-1.15: Step 2/19 : FROM quay.io/cilium/cilium-builder:2019-05-08 as builder
18:59:49      k8s1-1.15:  ---> 9e0b4d2d855c
18:59:49      k8s1-1.15: Step 3/19 : LABEL<EMAIL_ADDRESS>18:59:49      k8s1-1.15:  ---> Running in 19c94a3aac23
18:59:49      k8s1-1.15: Removing intermediate container 19c94a3aac23
18:59:49      k8s1-1.15:  ---> fbd37d6ac480
18:59:49      k8s1-1.15: Step 4/19 : WORKDIR /go/src/github.com/cilium/cilium
18:59:49      k8s1-1.15:  ---> Running in a845fcf7e887
18:59:49      k8s1-1.15: Removing intermediate container a845fcf7e887
18:59:49      k8s1-1.15:  ---> 844ef5a62190
18:59:49      k8s1-1.15: Step 5/19 : COPY . ./
19:11:57      k8s1-1.15: failed to export image: failed to set parent sha256:844ef5a62190361566480fcf029251e4eedb451737eb3238d8b51bda6e8d4859: unknown parent image ID sha256:844ef5a62190361566480fcf029251e4eedb451737eb3238d8b51bda6e8d4859
19:11:57      k8s1-1.15: Makefile:169: recipe for target 'docker-image-no-clean' failed
19:11:57      k8s1-1.15: make: *** [docker-image-no-clean] Error 1

test-missed-k8s

test-upstream-k8s


CI: Build Python 3.10 wheels for Windows and macOS

Add Python 3.10 to the Windows and macOS wheel build matrix.

Seems like something is broken with macOS :thinking:

Awesome, thanks for getting this in and fixing the macOS issue.
Could you tag a new release so that the Python 3.10 wheels will be available on PyPi?

I uploaded them manually


Remove version: Redisant.DataAssistant version <IP_ADDRESS>

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://object.redisant.com/DATA_ASSISTANT/DA-<IP_ADDRESS>.zip
Response Error: The remote server returned an error: (403) Forbidden.
(Automated message - build 911)

Hi @Exorcism0666,
This manifest has the highest version number for this package. Is it available from another location? (This might be in error if the version is switching from semantic to string, or string to semantic.)
(Automated response - build 886.)

URL: https://object.redisant.com/DATA_ASSISTANT/DA-<IP_ADDRESS>.zip
No such host is known. (object.redisant.com:443)
(Automated message - build 886)

For moderators or/and anyone else

[!Caution]
As a result of several personal problems I've had over the last few months + my final exams coming up very soon, I'm currently unable to look at my GitHub notifications every day and maintain my executions correctly.
If you detect a certain problem on a certain pul request:

Either you can close the pull request directly without mentioning me.
Or you can send me a message on X (Twitter): @Exorcism0666

Thank you for your understanding, and I'm sorry if some pull requests can't be approved due to the situation I'm in.

This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

URL: https://object.redisant.com/DATA_ASSISTANT/DA-<IP_ADDRESS>.zip
Response status code does not indicate success: 403 (Forbidden).
(Automated message - build 886)

URL: https://object.redisant.com/DATA_ASSISTANT/DA-<IP_ADDRESS>.zip
No such host is known. (object.redisant.com:443)
(Automated message - build 886)

URL: https://object.redisant.com/DATA_ASSISTANT/DA-<IP_ADDRESS>.zip
Response status code does not indicate success: 403 (Forbidden).
(Automated message - build 886)


Allow SPA pipeline triggering

Perform required data collection inserts etc and send Zocalo message to start processing

Resolved by #148


How do ppo & acktr compare in terms of wall-clock time?

ACKTR paper says that ACKTR paper processes ~25% less steps per minute compared to A2C.
What percent less steps per minute does PPO process compared to A2C?

On my machine I can barely notice any difference. PPO is slower, it depends on the epoch parameter.

PPO is slower than ACKTR (or just slower than A2C)?

PPO performs multiple updates for the same data sample. It's slower than ACKTR and A2C. But my experience that running environments is the main bottleneck anyway.


Implement zip() operator

https://doc.rust-lang.org/std/option/enum.Option.html#method.zip
TODO

[ ] Implement zip() operator for Maybe
[ ] Implement zip() operator for Nullable
[ ] Implement zip() operator for Undefinable
[x] #1601

Implemented by https://github.com/option-t/option-t/pull/1798


[TODO] Some of the app has missing styling

The page that loads at when the app starts in the development server needs some better styling.
Same with the other pages that have routes.
Most of the included style css files
Wherever possible use the sx property from MUI @mui v5

can I work with this?

@kennito29
Are you still planning on working on this?
Thanks


XGO-Core

This PR should be merged when we decide to release the (beta) .NET client.

@Marton6 or @edif2008 could we add a "Roadmap" section to the README?
Roadmap

[ ] Java
[ ] NodeJS
[ ] PHP
[ ] Python
[ ] Ruby

@Marton6 or @edif2008 could we add a "Roadmap" section to the README?
Roadmap

[ ]  Java
[ ]  NodeJS
[ ]  PHP
[ ]  Python
[ ]  Ruby

Added

This should be merged before we release the beta version of the SecretHub .NET client.


Zoom to waypoint

This was a very handy feature in the old frontend to fine tune the location of waypoints without scroll dancing.

@planemad - The waypoint input is intimately tied to the LRM plugin we are using. This is is an upstream issue, probably better suited as a feature request for that project.

tracking on https://github.com/perliedman/leaflet-routing-machine/issues/156

thanks @planemad. re-opened...

@amyleew flagging this as important. We would waste significant time if we had to manually zoom into each point without this feature.

@planemad - I've started this on the zoom branch here. I won't be able to implement this feature, but please feel free to pick it up...


Project Page - When there is not any todo the message showing No Query Available...

Describe the bug

When there is not any todo message showing No Query Available... it should be No Todo Available...

https://www.berrycast.com/conversations/ddfae46a-8d29-500e-9fd5-6aab41450cd9


yt-dlp视频使用方法

能做一个视频的详细使用方法吗？我看不懂

https://github-com.translate.goog/ytdl-org/youtube-dl?_x_tr_sl=en&_x_tr_tl=zh-CN&_x_tr_hl=en&_x_tr_pto=wapp

翻译手册页面是否有帮助？
否则，张贴您问题的更多细节。
不幸的是，我必须依靠谷歌翻译。
(This is what Google does to ...

Does the translated manual page help?

Otherwise, post more details of your problem.

Unfortunately, I must rely on Google Translate.
)

DeepL better:

Can you make a video with details on how to use it? I can't see it.

此外，可以用 https://github.com/soimort/you-get，这有中文翻译。

I hope that solves your problem. We don't have translations for yt-dl.
Or, according to Google:
我希望解决你的问题。 我们没有YT-DL的翻译。


[Android][Image] tintColor in style is ignored

https://rnplay.org/apps/r9L8dQ
tintColor works as documented for iOS, but for Android it is ignored and images are rendered the same as their source. This happens for both local and remote images.

Closing as duplicate of #3657


R200: cpp-config-ui crash when set R200_DEPTH_CLAMP_MIN and R200_DEPTH_CLAMP_MAX

Required Info

Camera Model
R200

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 14.04.4 LTS

Kernel Version (Linux Only)
4.4.0-040400-generic

Build System
Makefile

In cpp-config-ui, before start capture, I could set R200_DEPTH_CLAMP_MIN and R200_DEPTH_CLAMP_MAX values, but when I set the R200_DEPTH_CLAMP_MIN value higher than R200_DEPTH_CLAMP_MAX, or set R200_DEPTH_CLAMP_MAX value lower than R200_DEPTH_CLAMP_MIN, the tool will be crashed.
It makes sense that R200_DEPTH_CLAMP_MAX value never be lower than R200_DEPTH_CLAMP_MIN, and R200_DEPTH_CLAMP_MIN value never be higher than R200_DEPTH_CLAMP_MAX, but no crash should be.

config.ui is sample code, not a product. If you have different expectations you can use it as a baseline for you personal projects.
All librealsense demos exit on first encountered error, this is the expected behavior.

Thank you for quickly response.


Using Basic/Digest Auth with http-proxy

Hi,
Thanks for the very useful addition. I am trying to get the following to work. Any ideas on how to use http-auth and http-proxy together.
httpProxy.createServer(function (req, res, proxy) {
console.log("Here");

digest.apply(req, res, function() {
	res.end("Welcome to private area!");
});

proxy.proxyRequest(req, res, {
	host: 'localhost',
	port: 5984
});

}).listen(8000);
I get the following:
Express server listening on port 8081 in development mode
Here
http.js:573
throw new Error("Can't render headers after they are sent to the client.")
^
Error: Can't render headers after they are sent to the client.
at ServerResponse. (http.js:573:11)
at ServerResponse._renderHeaders (/opt/maxwell/admin/node_modules/express/node_modules/connect/lib/patch.js:76:25)
at ServerResponse.writeHead (http.js:816:20)
at ClientRequest. (/opt/maxwell/admin/node_modules/http-proxy/lib/node-http-proxy/http-proxy.js:214:9)
at ClientRequest.emit (events.js:67:17)
at HTTPParser.onIncoming (http.js:1217:11)
at HTTPParser.onHeadersComplete (http.js:102:31)
at Socket.ondata (http.js:1116:24)
at TCP.onread (net.js:314:27)

Thanks I tried it and it works. I am tryig to put authentication in front of Futon on port 5984.  Futon is external and I am trying not to start a bunch of different servers.  I don't think I can use this approach. I have dones something like this using hoxy which doesn't have basic authentication either but it does have some code to modify the headers. Thanks again and I will check back later.  I am going to have to try something else.

Hi,
Issue resolved, correct usage may be found in following gist: https://gist.github.com/1367654 .
Gevorg.

Note that fix is available under NPM and Git.


document config trimming with MTP

Description
Let's document the new feature in perf section

xrel: https://github.com/kumahq/kuma/pull/8084


Versioning broken when deploying to multiple clusters with same artifact

It seems Spinnaker versioning is broken when deploying to multiple clusters that have the same artifact attached. If the number of versioned resources of a given artifact do not match across clusters, then the artifact attached to subsequent deployments will bind the versioned artifact found for the first deployment which might not exist.

To reproduce this issue you will need to deploy to two Kubernetes clusters which will be referred to as cluster-a and cluster-b.

Deploy to ONLY cluster-a a ConfigMap and Deployment that references this ConfigMap.

ConfigMap can be very simple:
apiVersion: v1
data:
  test.json: |
    {"test":"test"}
kind: ConfigMap
metadata:
  name: test-config

Deployment should reference this ConfigMap at .spec.template.spec.volumes:
spec:
  template:
    spec:
      volumes:
      - configMap:
          name: test-config
        name: test-config

The container used shouldn't matter, it can be any basic container like nginx, but you should mount the ConfigMap at .spec.template.spec.containers[0].volumeMounts like so:
spec:
  template:
    spec:
      containers:
      - volumeMounts:
        - mountPath: /etc/test
           name: test-config

This will version the ConfigMap to test-config-v000 and attach it to the Deployment.

Deploy the same ConfigMap and Deployment now to both clusters, cluster-a first then cluster-b, in the same pipeline. The Deploy (Manifest) stages should be run serially not parallel. This will create new versioned ConfigMaps named test-config-v001 in cluster-a and test-config-v000 in cluster-b, however at deploy time to cluster-b it will attempt to mount test-config-v001 which does not exist in cluster-b and the deployment will fail with a timeout.

It looks like artifacts in Spinnaker have some metadata for the account provider name (cluster a or b), so we should probably just reference this during the Deploy (Manifest) task and only attach artifacts that have the same .metadata.account.
{
  "reference": "test-config-v001",
  "metadata": {
    "account": "cluster-a"
  },
  "name": "test-config"
}

Code to inspect will be anything that references the function kubernetes.BindArtifact(...): https://github.com/search?q=repo%3Ahomedepot%2Fgo-clouddriver bindartifacts&type=code. I will leave implementation up to the code owners, you could filter or pass in the account name for validation or maybe find a better way to manage artifacts before deployment.

@abe21412 @guido9j, shouldn't we close this issue since https://github.com/homedepot/go-clouddriver/pull/169 fixed it?


unity 2019 says--->>   The type or namespace name 'PrefabStage' does not exist in the namespace 'UnityEditor.SceneManagement' (are you missing an assembly reference?)

unity 2019 says--->>   The type or namespace name 'PrefabStage' does not exist in the namespace 'UnityEditor.SceneManagement' (are you missing an assembly reference?)
In this file PrefabSavingUtil
Please tell me how to solve please

I use Unity 2021, maybe the problem comes from your version. If not, I don't know how to help you sorry.


linting not working for me

Not sure what I am doing wrong but basically I just want to lint a chart.
Getting this error for some odd reason
* What went wrong:
A problem was found with the configuration of task 'my-tool:helmLintMy-toolChart'.
> Directory '/Users/*****/.helm
  ' specified for property '$1' does not exist.

I just ran
./gradlew helmLintMy-toolChart
Am trying to do step by step
lint , package, deploy

I'm getting the same thing with the helmPackage task. When I run gradle helmPackage --debug i see the helm home command run and finish with exit code 0.
I can see the directory, seems to have the correct permissions, and it is empty.
14:57:16.130 [INFO] [org.unbrokendome.gradle.plugins.helm.command.HelmExecProviderSupport] Executing: [helm, home] 14:57:16.130 [INFO] [org.gradle.process.internal.DefaultExecHandle] Starting process 'command 'helm''. Working directory: /Users/chris/Documents/git/images/mms-activemq Command: helm home 14:57:16.130 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Environment for process 'command 'helm'': {PATH=/Users/chris/bin: <removed some paths for clarity>... SHLVL=1, HOME=/Users/chris, APP_NAME_44546=Gradle} 14:57:16.130 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTING 14:57:16.130 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Waiting until process started: command 'helm'. 14:57:16.135 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTED 14:57:16.135 [DEBUG] [org.gradle.process.internal.ExecHandleRunner] waiting until streams are handled... 14:57:16.135 [INFO] [org.gradle.process.internal.DefaultExecHandle] Successfully started process 'command 'helm'' 14:57:16.193 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: SUCCEEDED 14:57:16.193 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Process 'command 'helm'' finished with exit value 0 (state: SUCCEEDED)
After that I see the exception.
14:57:16.196 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] FAILURE: Build failed with an exception. 14:57:16.196 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]  14:57:16.196 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * What went wrong: 14:57:16.196 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] A problem was found with the configuration of task ':mms-activemq:helmLintMainChart'. 14:57:16.196 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] > Directory '/Users/chris/.helm 14:57:16.196 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   ' specified for property '$1' does not exist.
Just starting out with helm charts and this plugin so I guess I am missing some required configuration. If there is something I can do to help debug this issue let me know.

adding
helm {     home = file("$buildDir/helm/home") }
I see the error message adjust accordingly to show this path.
`* What went wrong:
A problem was found with the configuration of task ':mms-activemq:helmLintMainChart'.

Directory '/helm/home' specified for property '$1' does not exist.
`

As soon as I manually created $buildDir/helm/home I am able to move onto my next issue.

Thanks I'll give it a try.

Helm lint/package now works for me too. My dir structure was bit different but it works now.
Thank you for help @kozchris
This is what I had in my test gradle for that project
import org.unbrokendome.gradle.plugins.helm.command.tasks.*

plugins {
    id("org.unbroken-dome.helm")
}
plugins {
    id ('org.unbroken-dome.helm-commands')
}
helm {
    charts {
        create("myappname") {
            chartName.set("myappname")
            chartVersion.set("1.2.3")
            sourceDir.set(file("src/main/helm"))
        }
    }
}

helm { home = file("$buildDir/helm/home") }

Hi! Glad you figured out a solution.
I think the problem is that the helmLint<Chart> task did not have a dependency on helmInitClient, so if your helm home directory was missing, then it would fail because that directory is created by helmInitClient.
It should be fixed in the next release.


Create an automatic workflow to sync up the Suave library.

Create a Github actions workflow with suave-geth that whenever the Suave library is updated in the source (suave-geth) a PR is generated on this repository with the update.

the suave-geth side: https://github.com/flashbots/suave-geth/pull/140


Auto-Args to main in Azure function App are not generated at new bindings

Package Name:  Azure func core tools
Package Version: 2.7.2254
Operating System: Windows
Python Version:  3.6

Describe the bug
Have followed this URL: https://docs.microsoft.com/en-us/azure/python/tutorial-vs-code-serverless-python-07 to get the auto bindings generated. But, still after following the steps, I couldn’t get the auto generated arguments
To Reproduce
Steps to reproduce the behavior:

Follow the Steps as per URL above for Cosmos DB in binding with HTTPTrigger

Expected behavior
After Adding the new in binding to HTTPTrigger Azure function, expect SDK to auto-generate Args to access the data from Cosmos Graph/SQL inside function's main

Additional context
Any suggestions to get the data from grapgh DB using Gremlin API are most welcome

Issue moved to Azure/azure-functions-python-library #60 via ZenHub


Fixed fix, allow Mux of different binary points and widths

Resolves #557
The implementation is ugly, but I can't think of a better way and this is a feature that makes sense. The larger problem seems to be that Chisel is duplicating width inferencing work with FIRRTL, but without all the information. The larger discussion might be whether that is a good practice, as removing width propagation in Chisel can remove a lot of complexity and special cases.

@ducky it removes a lot of complexity, but it's still extremely useful to do getWidth on signals whose width are known for certain functions.


Dependency to SLF4J

Please add a dependency block to the Maven POM.xml for the SLF4J. Without I do get a runtim error.
Dependency block for pow.xml:

org.slf4j
slf4j-simple
1.6.2

@dhedden I don't see a runtime error when I run DevLoginExample. How can I reproduce? Thanks.

My laptop is not used for regular Java-development, therefore I might have missed the right version of the library. The additional dependency entry in the pom file enforces filling this optional gap.
Rgds,
Dietmar

Closing this.


AEPCore 5.0.0, AEPAnalytics 5.0.0 crashes

Prerequisites

[X] This is not a Security Disclosure, otherwise please follow the guidelines in Security Policy.
[X] I have searched in this repository's issues to see if it has already been reported.
[X] I have updated to the latest released version of the SDK and the issue still persists.

Bug summary
We observe around 6000 crashes on Firebase Crashlytics that are marked as issue with AEPCode and other latest versions of Adobe Analytics.
These are the examples of stack traces:
Crashed: com.adobe.eventHub.queue
0  libsystem_kernel.dylib         0xa974 __pthread_kill + 8
1  libsystem_pthread.dylib        0x60ec pthread_kill + 268
2  libsystem_c.dylib              0x75b80 abort + 180
3  libsystem_malloc.dylib         0x2bc68 malloc_vreport + 896
4  libsystem_malloc.dylib         0x2bf10 malloc_zone_error + 104
5  libsystem_malloc.dylib         0x21a44 nanov2_guard_corruption_detected + 44
6  libsystem_malloc.dylib         0x7f84 nanov2_find_block_and_allocate + 402
7  libswiftCore.dylib             0x3a71ec swift::swift_slowAllocTyped(unsigned long, unsigned long, unsigned long long) + 48
8  libswiftCore.dylib             0x3a7684 _swift_allocObject_ + 1112
9  libswiftDispatch.dylib         0x24f0 OS_dispatch_queue._syncHelper<A>(fn:execute:rescue:) + 324
10 libswiftDispatch.dylib         0x237c OS_dispatch_queue.asyncAndWait<A>(execute:) + 140
11 libswiftDispatch.dylib         0x22e8 OS_dispatch_queue.sync<A>(execute:) + 64
12 AEPCore                        0x456f0 block_destroy_helper + 25540
13 AEPCore                        0x357ac block_destroy_helper + 104
14 AEPCore                        0x35784 block_destroy_helper + 64
15 libswiftDispatch.dylib         0x1d4c partial apply for thunk for @callee_guaranteed () -> (@out A, @error @owned Error) + 28
16 libswiftDispatch.dylib         0x9ea0 thunk for @callee_guaranteed () -> (@out A, @error @owned Error)partial apply + 16
17 libswiftDispatch.dylib         0x1c80 closure #1 in closure #1 in OS_dispatch_queue._syncHelper<A>(fn:execute:rescue:) + 192
18 libswiftDispatch.dylib         0x1bb4 partial apply for thunk for @callee_guaranteed () -> () + 28
19 libswiftDispatch.dylib         0x1b8c thunk for @escaping @callee_guaranteed () -> () + 28
20 libdispatch.dylib              0x3dd4 _dispatch_client_callout + 20
21 libdispatch.dylib              0x136f8 _dispatch_sync_invoke_and_complete_recurse + 64
22 libdispatch.dylib              0x13178 _dispatch_sync_f_slow + 176
23 libswiftDispatch.dylib         0x2788 implicit closure #2 in implicit closure #1 in OS_dispatch_queue.asyncAndWait<A>(execute:) + 192
24 libswiftDispatch.dylib         0x26c0 partial apply for implicit closure #2 in implicit closure #1 in OS_dispatch_queue.sync<A>(execute:) + 76
25 libswiftDispatch.dylib         0x2540 OS_dispatch_queue._syncHelper<A>(fn:execute:rescue:) + 404
26 libswiftDispatch.dylib         0x237c OS_dispatch_queue.asyncAndWait<A>(execute:) + 140
27 libswiftDispatch.dylib         0x22e8 OS_dispatch_queue.sync<A>(execute:) + 64
28 AEPCore                        0x353f0 __swift_destroy_boxed_opaque_existential_1Tm + 4988
29 AEPCore                        0x3f430 block_destroy_helper + 260
30 AEPAnalytics                   0xb288 __swift_noop_void_return + 3692
31 AEPAnalytics                   0x10fc4 __swift_noop_void_return + 27560
32 AEPCore                        0x347c4 __swift_destroy_boxed_opaque_existential_1Tm + 1872
33 AEPCore                        0x3598c block_destroy_helper + 584
34 AEPServices                    0x177fc __swift_destroy_boxed_opaque_existential_1Tm + 3596
35 AEPServices                    0x74c4 __swift_project_boxed_opaque_existential_1 + 808
36 libdispatch.dylib              0x3dd4 _dispatch_client_callout + 20
37 libdispatch.dylib              0x72d8 _dispatch_continuation_pop + 600
38 libdispatch.dylib              0x1b1c8 _dispatch_source_latch_and_call + 420
39 libdispatch.dylib              0x19d8c _dispatch_source_invoke + 832
40 libdispatch.dylib              0xb284 _dispatch_lane_serial_drain + 368
41 libdispatch.dylib              0xbf30 _dispatch_lane_invoke + 380
42 libdispatch.dylib              0x16cb4 _dispatch_root_queue_drain_deferred_wlh + 288
43 libdispatch.dylib              0x16528 _dispatch_workloop_worker_thread + 404
44 libsystem_pthread.dylib        0x1f20 _pthread_wqthread + 288
45 libsystem_pthread.dylib        0x1fc0 start_wqthread + 8

Crashed: com.adobe.eventHub.queue
0  libsystem_kernel.dylib         0x9fbc __pthread_kill + 8
1  libsystem_pthread.dylib        0x5680 pthread_kill + 268
2  libsystem_c.dylib              0x75b90 abort + 180
3  libsystem_malloc.dylib         0x26200 malloc_vreport + 908
4  libsystem_malloc.dylib         0x264a8 malloc_zone_error + 104
5  libsystem_malloc.dylib         0x1dac8 nanov2_guard_corruption_detected + 44
6  libsystem_malloc.dylib         0x7e78 nanov2_find_block_and_allocate + 402
7  libsystem_blocks.dylib         0x1a14 _Block_copy + 76
8  libswiftDispatch.dylib         0x2050 implicit closure #2 in implicit closure #1 in OS_dispatch_queue.asyncAndWait<A>(execute:) + 152
9  libswiftDispatch.dylib         0x1fb0 partial apply for implicit closure #2 in implicit closure #1 in OS_dispatch_queue.sync<A>(execute:) + 76
10 libswiftDispatch.dylib         0x1e30 OS_dispatch_queue._syncHelper<A>(fn:execute:rescue:) + 396
11 libswiftDispatch.dylib         0x1c74 OS_dispatch_queue.asyncAndWait<A>(execute:) + 140
12 libswiftDispatch.dylib         0x1be0 OS_dispatch_queue.sync<A>(execute:) + 64
13 AEPCore                        0x456f0 block_destroy_helper + 25540
14 AEPCore                        0x357ac block_destroy_helper + 104
15 AEPCore                        0x35784 block_destroy_helper + 64
16 libswiftDispatch.dylib         0x1594 partial apply for thunk for @callee_guaranteed () -> (@out A, @error @owned Error) + 28
17 libswiftDispatch.dylib         0x1570 thunk for @callee_guaranteed () -> (@out A, @error @owned Error)partial apply + 16
18 libswiftDispatch.dylib         0x14b0 closure #1 in closure #1 in OS_dispatch_queue._syncHelper<A>(fn:execute:rescue:) + 188
19 libswiftDispatch.dylib         0x13e8 partial apply for thunk for @callee_guaranteed () -> () + 28
20 libswiftDispatch.dylib         0x13c0 thunk for @escaping @callee_guaranteed () -> () + 28
21 libdispatch.dylib              0x4300 _dispatch_client_callout + 20
22 libdispatch.dylib              0x136b4 _dispatch_lane_barrier_sync_invoke_and_complete + 56
23 libswiftDispatch.dylib         0x2078 implicit closure #2 in implicit closure #1 in OS_dispatch_queue.asyncAndWait<A>(execute:) + 192
24 libswiftDispatch.dylib         0x1fb0 partial apply for implicit closure #2 in implicit closure #1 in OS_dispatch_queue.sync<A>(execute:) + 76
25 libswiftDispatch.dylib         0x1e30 OS_dispatch_queue._syncHelper<A>(fn:execute:rescue:) + 396
26 libswiftDispatch.dylib         0x1c74 OS_dispatch_queue.asyncAndWait<A>(execute:) + 140
27 libswiftDispatch.dylib         0x1be0 OS_dispatch_queue.sync<A>(execute:) + 64
28 AEPCore                        0x353f0 __swift_destroy_boxed_opaque_existential_1Tm + 4988
29 AEPAnalytics                   0xb3d8 __swift_noop_void_return + 4028
30 AEPAnalytics                   0xc124 __swift_noop_void_return + 7432
31 AEPAnalytics                   0x11084 __swift_noop_void_return + 27752
32 AEPAnalytics                   0xa644 __swift_noop_void_return + 552
33 libdispatch.dylib              0x26a8 _dispatch_call_block_and_release + 32
34 libdispatch.dylib              0x4300 _dispatch_client_callout + 20
35 libdispatch.dylib              0xb894 _dispatch_lane_serial_drain + 748
36 libdispatch.dylib              0xc3c4 _dispatch_lane_invoke + 380
37 libdispatch.dylib              0x17004 _dispatch_root_queue_drain_deferred_wlh + 288
38 libdispatch.dylib              0x16878 _dispatch_workloop_worker_thread + 404
39 libsystem_pthread.dylib        0x1964 _pthread_wqthread + 288
40 libsystem_pthread.dylib        0x1a04 start_wqthread + 8

Crashed: com.adobe.eventHub.queue
0  libsystem_kernel.dylib         0x69e8 __pthread_kill + 8
1  libsystem_pthread.dylib        0x10824 pthread_kill + 208
2  libsystem_c.dylib              0x1f0b4 abort + 120
3  libsystem_malloc.dylib         0x1a9dc _malloc_put + 546
4  libsystem_malloc.dylib         0x1ac48 malloc_zone_error + 100
5  libsystem_malloc.dylib         0x40bc nanov2_allocate_from_block$VARIANT$armv81 + 520
6  libsystem_malloc.dylib         0x10f0 nanov2_allocate$VARIANT$armv81 + 124
7  libsystem_malloc.dylib         0x59d4 nanov2_malloc$VARIANT$armv81 + 60
8  libsystem_malloc.dylib         0x515c _malloc_zone_malloc + 148
9  libsystem_blocks.dylib         0x16f0 _Block_copy + 144
10 libswiftDispatch.dylib         0x20ac implicit closure #2 in implicit closure #1 in OS_dispatch_queue.sync<A>(execute:) + 116
11 libswiftDispatch.dylib         0x137c partial apply for implicit closure #2 in implicit closure #1 in OS_dispatch_queue.sync<A>(execute:) + 40
12 libswiftDispatch.dylib         0x1eb8 OS_dispatch_queue._syncHelper<A>(fn:execute:rescue:) + 256
13 libswiftDispatch.dylib         0x1410 OS_dispatch_queue.sync<A>(execute:) + 140
14 AEPCore                        0x43ecc block_destroy_helper + 25516
15 AEPCore                        0x32e94 keypath_set.2Tm + 6240
16 AEPCore                        0x33828 block_copy_helper.45 + 104
17 libswiftDispatch.dylib         0x1b44 partial apply for thunk for @callee_guaranteed () -> (@out A, @error @owned Error) + 20
18 libswiftDispatch.dylib         0x1b5c thunk for @callee_guaranteed () -> (@out A, @error @owned Error)partial apply + 12
19 libswiftDispatch.dylib         0x2c24 closure #1 in closure #1 in OS_dispatch_queue._syncHelper<A>(fn:execute:rescue:) + 120
20 libswiftDispatch.dylib         0x2cd4 partial apply for thunk for @callee_guaranteed () -> () + 20
21 libswiftDispatch.dylib         0x26dc thunk for @escaping @callee_guaranteed () -> () + 20
22 libdispatch.dylib              0x641a8 _dispatch_client_callout + 16
23 libdispatch.dylib              0x464ac _dispatch_sync_invoke_and_complete_recurse + 60
24 libdispatch.dylib              0x45f9c _dispatch_sync_f_slow + 164
25 libswiftDispatch.dylib         0x20d0 implicit closure #2 in implicit closure #1 in OS_dispatch_queue.sync<A>(execute:) + 152
26 libswiftDispatch.dylib         0x137c partial apply for implicit closure #2 in implicit closure #1 in OS_dispatch_queue.sync<A>(execute:) + 40
27 libswiftDispatch.dylib         0x1eb8 OS_dispatch_queue._syncHelper<A>(fn:execute:rescue:) + 256
28 libswiftDispatch.dylib         0x1410 OS_dispatch_queue.sync<A>(execute:) + 140
29 AEPCore                        0x33414 keypath_set.2Tm + 7648
30 AEPCore                        0x32ac4 keypath_set.2Tm + 5264
31 AEPCore                        0x3dc80 block_destroy_helper + 352
32 AEPIdentity                    0x12410 __swift_memcpy88_8 + 25432
33 AEPIdentity                    0x12504 __swift_memcpy88_8 + 25676
34 AEPCore                        0x31e50 keypath_set.2Tm + 2076
35 AEPCore                        0x336a8 block_destroy_helper + 572
36 AEPServices                    0x19b90 __swift_allocate_boxed_opaque_existential_0 + 2784
37 AEPServices                    0x1fac4 block_destroy_helper + 4188
38 libdispatch.dylib              0x641a8 _dispatch_client_callout + 16
39 libdispatch.dylib              0x3b724 _dispatch_continuation_pop$VARIANT$armv81 + 436
40 libdispatch.dylib              0x4ccf4 _dispatch_source_invoke$VARIANT$armv81 + 1320
41 libdispatch.dylib              0x3f024 _dispatch_lane_serial_drain$VARIANT$armv81 + 308
42 libdispatch.dylib              0x3fc04 _dispatch_lane_invoke$VARIANT$armv81 + 388
43 libdispatch.dylib              0x495dc _dispatch_workloop_worker_thread + 616
44 libsystem_pthread.dylib        0x4e84 _pthread_wqthread + 284
45 libsystem_pthread.dylib        0x49f0 start_wqthread + 8

Crashed: com.adobe.eventHub.queue
0  libsystem_kernel.dylib         0xa974 __pthread_kill + 8
1  libsystem_pthread.dylib        0x60ec pthread_kill + 268
2  libsystem_c.dylib              0x75b80 abort + 180
3  libsystem_malloc.dylib         0x2bc68 malloc_vreport + 896
4  libsystem_malloc.dylib         0x2bf10 malloc_zone_error + 104
5  libsystem_malloc.dylib         0x21a44 nanov2_guard_corruption_detected + 44
6  libsystem_malloc.dylib         0x7f84 nanov2_find_block_and_allocate + 402
7  libsystem_blocks.dylib         0x1a14 _Block_copy + 76
8  libswiftDispatch.dylib         0x2760 implicit closure #2 in implicit closure #1 in OS_dispatch_queue.asyncAndWait<A>(execute:) + 152
9  libswiftDispatch.dylib         0x26c0 partial apply for implicit closure #2 in implicit closure #1 in OS_dispatch_queue.sync<A>(execute:) + 76
10 libswiftDispatch.dylib         0x2540 OS_dispatch_queue._syncHelper<A>(fn:execute:rescue:) + 404
11 libswiftDispatch.dylib         0x237c OS_dispatch_queue.asyncAndWait<A>(execute:) + 140
12 libswiftDispatch.dylib         0x22e8 OS_dispatch_queue.sync<A>(execute:) + 64
13 AEPCore                        0x456f0 block_destroy_helper + 25540
14 AEPCore                        0x357ac block_destroy_helper + 104
15 AEPCore                        0x35770 block_destroy_helper + 44
16 libswiftDispatch.dylib         0x1d4c partial apply for thunk for @callee_guaranteed () -> (@out A, @error @owned Error) + 28
17 libswiftDispatch.dylib         0x9ea0 thunk for @callee_guaranteed () -> (@out A, @error @owned Error)partial apply + 16
18 libswiftDispatch.dylib         0x1c80 closure #1 in closure #1 in OS_dispatch_queue._syncHelper<A>(fn:execute:rescue:) + 192
19 libswiftDispatch.dylib         0x1bb4 partial apply for thunk for @callee_guaranteed () -> () + 28
20 libswiftDispatch.dylib         0x1b8c thunk for @escaping @callee_guaranteed () -> () + 28
21 libdispatch.dylib              0x3dd4 _dispatch_client_callout + 20
22 libdispatch.dylib              0x132c4 _dispatch_lane_barrier_sync_invoke_and_complete + 56
23 libswiftDispatch.dylib         0x2788 implicit closure #2 in implicit closure #1 in OS_dispatch_queue.asyncAndWait<A>(execute:) + 192
24 libswiftDispatch.dylib         0x26c0 partial apply for implicit closure #2 in implicit closure #1 in OS_dispatch_queue.sync<A>(execute:) + 76
25 libswiftDispatch.dylib         0x2540 OS_dispatch_queue._syncHelper<A>(fn:execute:rescue:) + 404
26 libswiftDispatch.dylib         0x237c OS_dispatch_queue.asyncAndWait<A>(execute:) + 140
27 libswiftDispatch.dylib         0x22e8 OS_dispatch_queue.sync<A>(execute:) + 64
28 AEPCore                        0x35548 __swift_destroy_boxed_opaque_existential_1Tm + 5332
29 AEPCore                        0x3f6b8 block_destroy_helper + 908
30 AEPIdentity                    0x121a4 __swift_destroy_boxed_opaque_existential_0 + 8444
31 AEPIdentity                    0x124e0 __swift_destroy_boxed_opaque_existential_0 + 9272
32 AEPCore                        0x347c4 __swift_destroy_boxed_opaque_existential_1Tm + 1872
33 AEPCore                        0x3598c block_destroy_helper + 584
34 AEPServices                    0x177fc __swift_destroy_boxed_opaque_existential_1Tm + 3596
35 AEPServices                    0x74c4 __swift_project_boxed_opaque_existential_1 + 808
36 libdispatch.dylib              0x3dd4 _dispatch_client_callout + 20
37 libdispatch.dylib              0x72d8 _dispatch_continuation_pop + 600
38 libdispatch.dylib              0x1b1c8 _dispatch_source_latch_and_call + 420
39 libdispatch.dylib              0x19d8c _dispatch_source_invoke + 832
40 libdispatch.dylib              0xb284 _dispatch_lane_serial_drain + 368
41 libdispatch.dylib              0xbf30 _dispatch_lane_invoke + 380
42 libdispatch.dylib              0x16cb4 _dispatch_root_queue_drain_deferred_wlh + 288
43 libdispatch.dylib              0x16528 _dispatch_workloop_worker_thread + 404
44 libsystem_pthread.dylib        0x1f20 _pthread_wqthread + 288
45 libsystem_pthread.dylib        0x1fc0 start_wqthread + 8

Crashed: com.adobe.eventHub.queue
0  libsystem_kernel.dylib         0xa974 __pthread_kill + 8
1  libsystem_pthread.dylib        0x60ec pthread_kill + 268
2  libsystem_c.dylib              0x75b80 abort + 180
3  libsystem_malloc.dylib         0x2bc68 malloc_vreport + 896
4  libsystem_malloc.dylib         0x2bf10 malloc_zone_error + 104
5  libsystem_malloc.dylib         0x21a44 nanov2_guard_corruption_detected + 44
6  libsystem_malloc.dylib         0x7f84 nanov2_find_block_and_allocate + 402
7  libsystem_blocks.dylib         0x1a14 _Block_copy + 76
8  libswiftCore.dylib             0xc4acc @objc _SwiftDeferredNSDictionary.enumerateKeysAndObjects(options:using:) + 28
9  Foundation                     0x233a0 +[_NSJSONReader validForJSON:depth:allowFragments:] + 192
10 AEPServices                    0x121d4 block_destroy_helper + 200
11 AEPCore                        0x2eeac block_destroy_helper + 30280
12 AEPCore                        0x2eb9c block_destroy_helper + 29496
13 AEPCore                        0x41bf4 block_destroy_helper + 16596
14 AEPCore                        0x23918 block_destroy_helper.5 + 8036
15 libdispatch.dylib              0x213c _dispatch_call_block_and_release + 32
16 libdispatch.dylib              0x3dd4 _dispatch_client_callout + 20
17 libdispatch.dylib              0xb400 _dispatch_lane_serial_drain + 748
18 libdispatch.dylib              0xbf30 _dispatch_lane_invoke + 380
19 libdispatch.dylib              0x16cb4 _dispatch_root_queue_drain_deferred_wlh + 288
20 libdispatch.dylib              0x16528 _dispatch_workloop_worker_thread + 404
21 libsystem_pthread.dylib        0x1f20 _pthread_wqthread + 288
22 libsystem_pthread.dylib        0x1fc0 start_wqthread + 8

Environment
iOS: 79% iOS 17, 18% iOS 16, 2% iOS 15
SDK: AEPCore 5.0.0 (21E210), AEPAnalytics 5.0.0 (21E210)
IDE: Xcode 15.3.0
Steps to reproduce
Unable to reproduce - around 6000 crashes catched on Firebase Crashlytics.
Current behavior
It crashes.
Expected behavior
To not crash.
Anything else?
No response

@niorko Can you share the full crash reports for all of these different crashes? We need to see the full stack trace (all threads) to have a better idea of whats going on considering you don't have steps to reproduce. Thanks.

crashpoints.zip
Hello, I can't download full stack crash report from Crashlytics, but I gathered few crashpoints from Xcode Organizer from the past two weeks. I hope it helps.
Thank you

@niorko Looking at all the crash logs, it seems to be some kind of memory corruption. I can't conclusively pinpoint where the actual corruption happens. Do you see similar crashes outside of AEP SDK? Can you also turn on memory management diagnostics for your app and see if you can catch any errors?

@praveek I haven't seen any leaks nor corruption and I can't induce the situation,  because it does not happen regularly. The only thing that I have in regards with crashes are these crashes from Firebase Crashlytics and crashes in Xcode Organizer. :(

@cdhoffmann is there any progress? I am being asked constantly on this issue. Thank you.

@niorko Hey, we have not been able to reproduce this issue, and we don't have any definitive information. Just as @praveek mentioned, this appears to be a memory corruption issue in the app. If you can get us steps to reproduce, we can look into it further.


Running tests for different OS

Running tests for different OS with GH Actions

"Services" (need for postgresql) supported only by linux systems. For this reason, the tests were carried out only for two versions ubuntu.


How to update a custom Flatcar machine ?

I built a custom Flatcar image following the instructions in document https://www.flatcar.org/docs/latest/reference/developer-guides/sdk-modifying-flatcar/#making-changes

board: amd64-user
version:  3033.2.2+2022-02-14-1145

I use flatcar-install to install Flatcar to disk with this image (in __build__/images/images/amd64-usr/developer-3033.2.2+2022-02-14-1145-a1/flatcar_production_image.bin , use bzip2 to compress it) . Reboot from the disk, and OS is running...
In the future I might add some packages and build another custom image using the same method. How can I use this new image to update the Flatcar machine ?
Thanks!

The end of this section shows how to use the flatcar-update script for that:
https://www.flatcar.org/docs/latest/migrating-from-coreos/update-from-container-linux/#the-migration-script
In your case you would use --force-dev-key instead of --force-flatcar-key.

(If you want your machine to follow the regular Flatcar updates you would need to use an other way of customization: https://www.flatcar.org/docs/latest/installing/customizing-the-image/customize-the-image/)

Oh I see, thanks for your advice!

The flow is like for airgapped updates, I guess we should add a new docs section for that

Created a docs PR here: https://github.com/flatcar-linux/flatcar-docs/pull/211


fix(repository): exclude hidden properties in response body

Description
Added lacking support of hidden option in model properties which is used to exclude the specified property from response body.
Fixes #3

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Implement user profiles/memberships

Model
A user can be a member of one or more games. Most profile information should be a part of this membership - a user gives a particular game only what information they want, so each game membership has its own profile data, though later we might add a feature to copy data between your profiles or otherwise keep them in sync.
Create a Membership model in the camp.accounts app with references to both a Game and a User.
Profile data to track initially. Note that while we might want to force users to populate these fields, allowing them to be initially blank makes it easier to onboard a user to a game.

Nickname: While there will initially be no "social" features, this might show up on your character sheet printouts instead of your full name. Can be blank. Not necessarily unique.
Pronouns: Free-form field, can be blank. The edit page might have some suggestions for convenience, but people can enter whatever they want.
Birthday: Date field. If you're feeling ambitious, add a validator to confirm that it's a date in the past. Let it be blank - games that have age requirements will prompt the user to provide an age when needed, and then it can be saved.
Joined: Date field. Set this to automatically populate when the membership is created, and don't let the user edit it. Might be used to produce a chart of new memberships over time, or provide staff with a list of recently joined members.

Views
Game membership details should be displayed on the /accounts/profile page along with their basic user details. Put a create page under /accounts/profile/create, and similar for edit. The basic profile page should have a prompt to create a profile only if the game is currently marked "open", but the edit option should be available as long as the user is already a member.
Later on, we can automatically create a membership for a user if they try to create a character or sign up for an event or something, but for now managing it on the profile page is enough.

Check out https://docs.djangoproject.com/en/4.2/ref/django-admin/#makemigrations and note this line:

To add migrations to an app that doesn’t have a migrations directory, run makemigrations with the app’s app_label.

Add accounts to the end of the makemigrations command. For some reason, the default is not to make migrations for an app that doesn't have any yet.


[3.x] TileMap Fix trying to get data for tile not existing in attached TileSet

Probably fixes (not sure as there's no minimal reproduction projects there): #29715, #43306.
I assume it's 3.x only because of the TileMap rework.
Cherry-pickable 3.3.
Example of fixed error:

Initial setup:

After removing tile from TileSet:

Painting a single cell next to a cell with tile id non-existant in attached TileSet:

3.4.beta2:

this PR:

Thanks!

Cherry-picked for 3.3.3.


The Pipeline does not fail with 'fail_on_error: true'

I added yml configuration according to the guideline.
name: "Run Java Checkstyle"

on: pull_request

jobs:
  checkstyle_job:
    runs-on: ubuntu-latest
    name: Checkstyle job
    steps:
      - name: Checkout
        uses: actions/checkout@v2
      - name: Run check style
        uses: nikitasavinov/checkstyle-action@master
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          reporter: 'github-pr-check'
          checkstyle_config: 'codestyle/checkstyle.xml'
          checkstyle_version: '8.42'
          fail_on_error: true

Even that fail_on_error is set to true, the checkstyle pipeline finishes successfully.
Here is the link to PR: SimonHarmonicMinor/Java-Useful-Utils#72

We're seeing the same behaviour here with fail_on_error: true . The action still passes.

Hi @SimonHarmonicMinor ,
There are no code issues in the PR you attached (https://github.com/SimonHarmonicMinor/Java-Useful-Utils/actions/runs/954371421) as there is no Java code. Do you have another example maybe?
In the sample PR I see that fail_on_error option works: https://github.com/nikitasavinov/checkstyle-action/pull/6/files, so I need some help to reproduce

Hi @nikitasavinov .
Here it is https://github.com/SimonHarmonicMinor/Java-Useful-Utils/pull/133.
The plugin reported an error, but the job finished successfully.

Ok, I see: you need to provide an extra level flag in your build definition:
level: error

In that case all reviewdog messages will become errors and build will fail (reference: https://github.com/reviewdog/reviewdog#exit-codes).
The current default value is info.

@nikitasavinov thanks, that did work. I think this should be mentioned in README.md

@nikitasavinov
Hi, I think it is an inappropriate way to fail as soon as encountering an error.
Is there any way to find all errors (and comment on PR) then fail the workflow? It is a nightmare to fix error one by one.


Remove encrypted secrets files and hardcode values

Everything in there ends up accessible in the deployed source anyway if I'm not mistaken. Is there any objection to simplifying this?

Having the Alchemy key checked in to github could expose us to a lot more abuse since it becomes trivial to search for it.

How about we just base64 encode it so it's obfuscated for searching?

Yes, obfuscating the env var name and its value sgtm.


Android needs first (v0.1.0?) release

Going through all the old issues and cleaning up.
Lambda was the first release.
Next release coming soon.